PNNIx Route Test Table Flags

1.3.6.1.4.1.800.3.2.1.1.4.1.1.1.5

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.