All MIBs › RFC1382-MIB › x25ClearedCircuitEntriesRequested
x25ClearedCircuitEntriesRequested
Module: RFC1382-MIB
OID (symbolic): RFC1382-MIB::x25ClearedCircuitEntriesRequested
OID (numeric): 1.3.6.1.2.1.10.5.6
Node type: OBJECT-TYPE
Type: PositiveInteger
Access: read-write
Description: The requested number of entries for the agent to keep in the x25ClearedCircuit table.
What is x25ClearedCircuitEntriesRequested?
Lets an admin request how many entries the agent should retain in the cleared-circuit history table; the agent may grant a different number, reported in x25ClearedCircuitEntriesGranted.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.5.6 snmpwalk -v2c -c public <target> RFC1382-MIB::x25ClearedCircuitEntriesRequested
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.10.5.6.1 snmpget -v2c -c public <target> RFC1382-MIB::x25ClearedCircuitEntriesRequested.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.10.5.6.1 i <value>
Start monitoring vendor-neutral, standards-based MIB, routers/devices supporting X.25 packet-switching protocol with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1382-MIB::x25ClearedCircuitEntriesRequested OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, routers/devices supporting X.25 packet-switching protocol from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.10.5 | x25 | ITOUCHHUB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.5.6 | x25ClearedCircuitEntriesRequested | RFC1382-MIB |