SWITCH-L3-MIB :: rcL3IpRouteFlags

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SWITCH-L3-MIB › rcL3IpRouteFlags

rcL3IpRouteFlags

Module: SWITCH-L3-MIB

OID (symbolic): SWITCH-L3-MIB::rcL3IpRouteFlags

OID (numeric): 1.3.6.1.4.1.8886.6.1.16.3.1.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 rcL3IpRouteFlags?

Intended to hold netstat-style route flag bits such as 0x2 for gateway or 0x800 for manually added static routes, but this object is not implemented on this switch and always returns 0.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.16.3.1.1.12
snmpwalk -v2c -c public <target> SWITCH-L3-MIB::rcL3IpRouteFlags

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.16.3.1.1.12.1
snmpget -v2c -c public <target> SWITCH-L3-MIB::rcL3IpRouteFlags.1

Start monitoring Wind River TMS/ROSE-based switch/router platform (Layer 3 routing config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SWITCH-L3-MIB::rcL3IpRouteFlags OID value, configure state conditions and alerts, and monitor any Wind River TMS/ROSE-based switch/router platform (Layer 3 routing config) from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.8886raisecomRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6iscomSeriesRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6.1iscomSwitchRAISECOM-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.8886.6.1.16rcL3SWITCH-L3-MIB
1.3.6.1.4.1.8886.6.1.16.3rcL3IpRouteSWITCH-L3-MIB
1.3.6.1.4.1.8886.6.1.16.3.1rcL3IpRouteTableSWITCH-L3-MIB
1.3.6.1.4.1.8886.6.1.16.3.1.1rcL3IpRouteEntrySWITCH-L3-MIB
1.3.6.1.4.1.8886.6.1.16.3.1.1.12rcL3IpRouteFlagsSWITCH-L3-MIB