All MIBs › TMS-L3-MIB › tmsL3IpRouteFlags
tmsL3IpRouteFlags
Module: TMS-L3-MIB
OID (symbolic): TMS-L3-MIB::tmsL3IpRouteFlags
OID (numeric): 1.3.6.1.4.1.731.2.2.2.5.4.1.12
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: Not implemented. Returns '0'.
Contains the information required for a netstat-like 'Flags' field.
The flags field represents a decimal value of the flags specified for a given route. The following is a list of currently available flag values: 0x1 | - route is usable (that is, 'up') 0x2 | - destination is a gateway 0x4 | - host specific routing entry 0x8 | - host or net unreachable 0x10 | - created dynamically (by redirect) 0x20 | - modified dynamically (by redirect) 0x40 | - message confirmed 0x80 | - subnet mask present 0x100 | - generate new routes on use 0x200 | - external daemon resolves name 0x400 | - generated by ARP 0x800 | - manually added (static) 0x1000 | - just discard packets (during updates) 0x2000 | - modified by management protocol 0x4000 | - protocol specific routing flag 0x8000 | - protocol specific routing flag
For example, if the entry in the Routing Table has a flag value of decimal 5, (0x1 OR'ed with 0x4), then this route is 'up' and usable and is host-specific.
What is tmsL3IpRouteFlags?
Intended to hold netstat-style route flag bits (such as 'up', 'gateway', or 'host-specific'), but this object is not implemented on TMS switches and always returns 0.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.731.2.2.2.5.4.1.12 snmpwalk -v2c -c public <target> TMS-L3-MIB::tmsL3IpRouteFlags
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.731.2.2.2.5.4.1.12.1 snmpget -v2c -c public <target> TMS-L3-MIB::tmsL3IpRouteFlags.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> tmsL3IpRouteFlags.1
Start monitoring embedded network device/appliance built on Wind River TMS networking stack (Layer 3 IP routing config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TMS-L3-MIB::tmsL3IpRouteFlags OID value, configure state conditions and alerts, and monitor any embedded network device/appliance built on Wind River TMS networking stack (Layer 3 IP routing config status) from a single console.
OID Breakdown
Upper-level ancestors (9 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.731 | wrs | WRS-MASTER-MIB |
| 1.3.6.1.4.1.731.2 | tms | WRS-MASTER-MIB |
| 1.3.6.1.4.1.731.2.2 | tmsGeneric | WRS-MASTER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.731.2.2.2 | tmsL3Mib | TMS-L3-MIB |
| 1.3.6.1.4.1.731.2.2.2.5 | tmsL3IpRoute | TMS-L3-MIB |
| 1.3.6.1.4.1.731.2.2.2.5.4 | tmsL3IpRouteTable | TMS-L3-MIB |
| 1.3.6.1.4.1.731.2.2.2.5.4.1 | tmsL3IpRouteEntry | TMS-L3-MIB |
| 1.3.6.1.4.1.731.2.2.2.5.4.1.12 | tmsL3IpRouteFlags | TMS-L3-MIB |