All MIBs › XPNNI-MIB › pnnixRtstFlags
pnnixRtstFlags
Module: XPNNI-MIB
OID (symbolic): XPNNI-MIB::pnnixRtstFlags
OID (numeric): 1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: If error is set to success, this flag indicates the nature of the route lookup confirmation.
If this flag is set to dtlAdded, then the route request resulted in a DTL being allocated for this request. In this case, the pnnixRtstOutboundPort, pnnixRtstHopCount, pnnixRtstDTL, and pnnixRtstCurPointer contain useful information. (Also, after this information is conveyed back to the manager, the DTL entry is freed.)
If this flag is set to direct, then the route request is informing the caller to proceed out a directly attached port. In this case, the pnnixRtstOutboundPort is valid and is either 1 (to indicate a match on this node's summary address) or is a reference to the pnni advertised outbound port.
If this flag is set to myself, then the route request is informing the caller that the test call to the node in this switching system (identified by pnnixNodeIndex) returned a successful match of myself as the destination. In this case, the pnnixRtstOutboundPort is valid and is set to 0 (which indicates a match on this node's own address).
If this flag is set to directEreach, then the route request is informing the caller that the test call to the destination resulted in a direct indication. In this case, the pnnixRtstOutboundPort is valid and is set to the static route's pnni advertised port ID. If the user also specified a VPI and E.164 address, then the pnnixRtstVPI and pnnixRtstE164 fields will also be present.
What is pnnixRtstFlags?
Read-only flag describing the nature of a successful route-test result: dtlAdded (a DTL was allocated, freed after being read back), direct (proceed out a directly attached port), myself (destination is this switch itself), or directEreach (a static E.164 route match); an admin uses this to interpret which other Rtst columns are meaningful for a given lookup.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5 snmpwalk -v2c -c public <target> XPNNI-MIB::pnnixRtstFlags
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5.1 snmpget -v2c -c public <target> XPNNI-MIB::pnnixRtstFlags.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> pnnixRtstFlags.1
Start monitoring ATM switch, ATM PNNI routing node (DTL/crankback/alternate-route/route-failure counter status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XPNNI-MIB::pnnixRtstFlags OID value, configure state conditions and alerts, and monitor any ATM switch, ATM PNNI routing node (DTL/crankback/alternate-route/route-failure counter status) from a single console.
OID Breakdown
Upper-level ancestors (10 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.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.800 | xylan | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.3 | xylanProduct | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.3.2 | xylanSoftware | XYLAN-BASE-MIB |
| 1.3.6.1.4.1.800.3.2.1 | xylanPnni | XYLAN-BASE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.800.3.2.1.1 | pnnixMIB | XPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.1.4 | pnniTestMIBObjects | XPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.1.4.1 | pnniRtstMIBGroup | XPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.1.4.1.1 | pnnixRtstTable | XPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.1.4.1.1.1 | pnnixRtstEntry | XPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5 | pnnixRtstFlags | XPNNI-MIB |