TIMETRA-DOT3-OAM-MIB :: tmnxDot3OamTunneling

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-DOT3-OAM-MIB › tmnxDot3OamTunneling

tmnxDot3OamTunneling

Module: TIMETRA-DOT3-OAM-MIB

OID (symbolic): TIMETRA-DOT3-OAM-MIB::tmnxDot3OamTunneling

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.42.1.1.1.4

Node type: OBJECT-TYPE

Type: TruthValue

Access: read-write

Description: The value of tmnxDot3OamTunneling specifies if OAMPDUs should be passed transparently through the OAM entity for processing by another OAM entity across the network, or if OAMPDUs should be terminated and processed at the local OAM entity. This object can only be set to 'true' if dot3OamAdminState is set to 'disabled'. Likewise, dot3OamAdminState can only be set to 'enabled' if this object is set to 'false'. It is not valid to try and enable both OAMPDU processing and OAMPDU tunneling on the same OAM entity.

What is tmnxDot3OamTunneling?

This object specifies whether OAMPDUs are passed transparently through this OAM entity for processing elsewhere in the network, or terminated and processed locally; it can only be set true when dot3OamAdminState is disabled, and dot3OamAdminState can only be enabled when this is false, since both OAMPDU processing and tunneling cannot be active together. Admins use it when this device is meant to act as a transparent pass-through for OAM traffic rather than terminate it. Setting tmnxDot3OamTunneling to true on an access node lets customer OAMPDUs tunnel through to the far end rather than being consumed locally.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.42.1.1.1.4
snmpwalk -v2c -c public <target> TIMETRA-DOT3-OAM-MIB::tmnxDot3OamTunneling

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.42.1.1.1.4.1
snmpget -v2c -c public <target> TIMETRA-DOT3-OAM-MIB::tmnxDot3OamTunneling.1

Set instance 1 (SNMPv2c):

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

Start monitoring Alcatel-Lucent/Nokia SROS routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-DOT3-OAM-MIB::tmnxDot3OamTunneling OID value, configure state conditions and alerts, and monitor any Alcatel-Lucent/Nokia SROS routers from a single console.

OID Breakdown

Upper-level ancestors (10 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.42tmnxDot3OamObjsTIMETRA-DOT3-OAM-MIB
1.3.6.1.4.1.6527.3.1.2.42.1tmnxDot3OamEntryObjsTIMETRA-DOT3-OAM-MIB
1.3.6.1.4.1.6527.3.1.2.42.1.1tmnxDot3OamTableTIMETRA-DOT3-OAM-MIB
1.3.6.1.4.1.6527.3.1.2.42.1.1.1tmnxDot3OamEntryTIMETRA-DOT3-OAM-MIB
1.3.6.1.4.1.6527.3.1.2.42.1.1.1.4tmnxDot3OamTunnelingTIMETRA-DOT3-OAM-MIB