EXTREME-MPLS-TE-MIB :: mplsTunnelTransportStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EXTREME-MPLS-TE-MIB › mplsTunnelTransportStatus

mplsTunnelTransportStatus

Module: EXTREME-MPLS-TE-MIB

OID (symbolic): EXTREME-MPLS-TE-MIB::mplsTunnelTransportStatus

OID (numeric): 1.3.6.1.4.1.1916.1.37.2.2.1.1.3

Node type: OBJECT-TYPE

Type: Bits

Access: read-write

Description: Indicates the type of traffic the tunnel group can be used for sending.

When the allowAllIp(0) bit is set, IP traffic destined for all IPv4 routes will be allowed over any tunnel in the group marked active.

When the allowAssignedIpOnly(1) bit is set, IP traffic destined only for IPv4 static routes that have been explicitly configured to use this tunnel group will be allowed.

When the allowAllLayer2Vpn(2) bit is set, layer 2 VPN traffic for all layer 2 VPNs will be allowed over any tunnel in the group marked active.

When the allowAssignedLayer2VpnOnly(3) bit is set, layer 2 VPN traffic destined only for pseudo-wires that have been explicitly configured to use this tunnel group will be allowed.

What is mplsTunnelTransportStatus?

This bitmask controls what categories of traffic -- all IPv4 routes, only explicitly assigned static routes, all Layer-2 VPN traffic, or only explicitly assigned pseudowires -- are permitted to use this tunnel group. An admin sets specific bits here to restrict a tunnel group to carrying only pre-approved traffic instead of acting as a general-purpose transport path, helping control which services depend on that tunnel. Setting only the allowAssignedIpOnly bit would restrict this tunnel group to carrying just the IPv4 static routes an admin has explicitly configured to use it, rather than all IP traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1916.1.37.2.2.1.1.3
snmpwalk -v2c -c public <target> EXTREME-MPLS-TE-MIB::mplsTunnelTransportStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1916.1.37.2.2.1.1.3.1
snmpget -v2c -c public <target> EXTREME-MPLS-TE-MIB::mplsTunnelTransportStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1916.1.37.2.2.1.1.3.1 s <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> mplsTunnelTransportStatus.1

Start monitoring Extreme Networks MPLS-capable router/switch (MPLS-TE tunnel extensions) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EXTREME-MPLS-TE-MIB::mplsTunnelTransportStatus OID value, configure state conditions and alerts, and monitor any Extreme Networks MPLS-capable router/switch (MPLS-TE tunnel extensions) 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.1916extremeA3COM51-SS9000SX
1.3.6.1.4.1.1916.1extremeAgentEXTREME-BASE-MIB
1.3.6.1.4.1.1916.1.37extremeMplsMIBEXTREME-MPLS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.1.37.2extremeMplsTeMIBEXTREME-MPLS-TE-MIB
1.3.6.1.4.1.1916.1.37.2.2extremeMplsTeObjectsEXTREME-MPLS-TE-MIB
1.3.6.1.4.1.1916.1.37.2.2.1extremeMplsTunnelTableEXTREME-MPLS-TE-MIB
1.3.6.1.4.1.1916.1.37.2.2.1.1extremeMplsTunnelEntryEXTREME-MPLS-TE-MIB
1.3.6.1.4.1.1916.1.37.2.2.1.1.3mplsTunnelTransportStatusEXTREME-MPLS-TE-MIB