All MIBs › XYLANPNNI-MIB › xPnniRtstFlags
xPnniRtstFlags
Module: XYLANPNNI-MIB
OID (symbolic): XYLANPNNI-MIB::xPnniRtstFlags
OID (numeric): 1.3.6.1.4.1.800.3.2.1.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 xPnniRtstOutboundPort, xPnniRtstHopCount, xPnniRtstDTL, and xPnniRtstCurPointer 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 xPnniRtstOutboundPort 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 xPnniNodeIndex) returned a successful match of myself as the destination. In this case, the xPnniRtstOutboundPort 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 xPnniRtstOutboundPort 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 xPnniRtstVPI and xPnniRtstE164 fields will also be present.
What is xPnniRtstFlags?
When a route test succeeds, this reports how the route was resolved: dtlAdded means a full Designated Transit List was computed, direct means the destination is reachable out a directly attached port, myself means the destination matches this node's own address, and directEreach means a static E.164 external-reachability route was used. Admins use it together with xPnniRtstOutboundPort to understand exactly how PNNI would route a call to the tested destination.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.5 snmpwalk -v2c -c public <target> XYLANPNNI-MIB::xPnniRtstFlags
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.5.1 snmpget -v2c -c public <target> XYLANPNNI-MIB::xPnniRtstFlags.1
Start monitoring Xylan/Alcatel OmniSwitch ATM switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XYLANPNNI-MIB::xPnniRtstFlags OID value, configure state conditions and alerts, and monitor any Xylan/Alcatel OmniSwitch ATM switches 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.2 | xylanPnniMIB | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1 | xylanPnniMIBExtens | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1 | xylanPnniMIBObjs | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1.4 | xPnniTestMIBObjects | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1 | xPnniRtstMIBGroup | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1 | xPnniRtstTable | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1 | xPnniRtstEntry | XYLANPNNI-MIB |
| 1.3.6.1.4.1.800.3.2.1.2.1.1.4.1.1.1.5 | xPnniRtstFlags | XYLANPNNI-MIB |