All MIBs › TRIP-MIB › tripRouteTRIBMask
tripRouteTRIBMask
Module: TRIP-MIB
OID (symbolic): TRIP-MIB::tripRouteTRIBMask
OID (numeric): 1.3.6.1.2.1.116.1.6.1.5
Node type: OBJECT-TYPE
Type: Bits
Access: read-only
Description: Indicates which Telephony Routing Information Base (TRIB) this entry belongs to. This is a bit-map of possible types. If the bit has a value of 1, then the entry is a member of the corresponding TRIB type. If the bit has a value of 0 then the entry is not a member of the TRIP type. The various bit positions are:
0 adjTribIns The entry is of type adj-TRIBs-ins, stores routing information that has been learned from inbound UPDATE messages. 1 extTrib The entry is of type ext-TRIB, the best route for a given destination. 2 locTrib The entry is of type loc-TRIB contains the local TRIP routing information that the LS has selected. 3 adjTribOut The entry is of type adj-TRIBs-out, stores the information that the local LS has selected for advertisement to its external peers.
What is tripRouteTRIBMask?
This is a bitmap indicating which Telephony Routing Information Bases (TRIBs) this route entry belongs to: adj-TRIBs-ins (learned from inbound updates), ext-TRIB (the best route for a destination), loc-TRIB (the server's own selected routing information), and adj-TRIBs-out (selected for advertisement to external peers). Admins use it to understand a route's role in this server's routing pipeline, since one physical route can appear in multiple TRIBs at once.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.116.1.6.1.5 snmpwalk -v2c -c public <target> TRIP-MIB::tripRouteTRIBMask
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.116.1.6.1.5.1 snmpget -v2c -c public <target> TRIP-MIB::tripRouteTRIBMask.1
Start monitoring vendor-neutral, standards-based IETF MIB (RFC 3872), VoIP gateway/softswitch acting as TRIP Location Server (admin/oper status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TRIP-MIB::tripRouteTRIBMask OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based IETF MIB (RFC 3872), VoIP gateway/softswitch acting as TRIP Location Server (admin/oper status) from a single console.
OID Breakdown
Upper-level ancestors (6 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 | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.116 | tripMIB | TRIP-MIB |
| 1.3.6.1.2.1.116.1 | tripMIBObjects | TRIP-MIB |
| 1.3.6.1.2.1.116.1.6 | tripRouteTable | TRIP-MIB |
| 1.3.6.1.2.1.116.1.6.1 | tripRouteEntry | TRIP-MIB |
| 1.3.6.1.2.1.116.1.6.1.5 | tripRouteTRIBMask | TRIP-MIB |