TIMETRA-IF-GROUP-HANDLER-MIB :: tmnxIfGroupHdlrProtoStatus

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-IF-GROUP-HANDLER-MIB › tmnxIfGroupHdlrProtoStatus

tmnxIfGroupHdlrProtoStatus

Module: TIMETRA-IF-GROUP-HANDLER-MIB

OID (symbolic): TIMETRA-IF-GROUP-HANDLER-MIB::tmnxIfGroupHdlrProtoStatus

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.69.1.2.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The tmnxIfGroupHdlrProtoStatus indicates the operational state of the protocol for the Interface Group Handler.

The valid states are: none (0) -- Initializing state. All member within the group are in state 'none (0)' for the given tmnxIfGroupHdlrProtoIndex. blocked (1) -- Administratively disabled. inhibited (2) -- Administratively enabled but tmnxIfGroupHandlerThreshold is not met for enough links that have tmnxIfGroupHdlrMemberProtoStatus set to 'ready (2)'. waiting (3) -- Administratively enabled but tmnxIfGroupHandlerThreshold is not met for enough links that have tmnxIfGroupHdlrMemberProtoStatus set to 'operational (4)' or better. pending (4) -- Administratively enabled but tmnxIfGroupHandlerThreshold is not met for enough links that have tmnxIfGroupHdlrMemberProtoStatus set to 'up (5)'. up (5) -- Administratively enabled but tmnxIfGroupHandlerThreshold is met with enough links that have tmnxIfGroupHdlrMemberProtoStatus set to 'up (5)'.

What is tmnxIfGroupHdlrProtoStatus?

This read-only enumerated value reports the operational state of the protocol for the Interface Group Handler as a whole: none(0), blocked(1), inhibited(2), waiting(3), pending(4), or up(5), each tied to whether enough member links have reached specific status thresholds. Admins read this to see the group's aggregate readiness state at a glance rather than checking each member individually. For example, a group stuck at inhibited(2) means it is administratively enabled but not enough member links have reached 'ready' status to satisfy tmnxIfGroupHandlerThreshold.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.69.1.2.1.2
snmpwalk -v2c -c public <target> TIMETRA-IF-GROUP-HANDLER-MIB::tmnxIfGroupHdlrProtoStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.69.1.2.1.2.1
snmpget -v2c -c public <target> TIMETRA-IF-GROUP-HANDLER-MIB::tmnxIfGroupHdlrProtoStatus.1

Start monitoring Nokia/Alcatel-Lucent 7750 SR/7450 ESS routers (interface-group threshold-triggered admin-control status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-IF-GROUP-HANDLER-MIB::tmnxIfGroupHdlrProtoStatus OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR/7450 ESS routers (interface-group threshold-triggered admin-control status) from a single console.

How to Use in IPNetwork Monitor

Select a Nokia/Alcatel-Lucent 7750 SR/7450 ESS router (interface-group threshold-triggered admin-control status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tmnxIfGroupHdlrProtoStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The tmnxIfGroupHdlrProtoStatus indicates the operational state of the protocol for the Interface Group Handler. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'up', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

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.69tmnxIfGroupObjsTIMETRA-IF-GROUP-HANDLER-MIB
1.3.6.1.4.1.6527.3.1.2.69.1tmnxIfGroupConfigurationsTIMETRA-IF-GROUP-HANDLER-MIB
1.3.6.1.4.1.6527.3.1.2.69.1.2tmnxIfGroupHandlerProtoTableTIMETRA-IF-GROUP-HANDLER-MIB
1.3.6.1.4.1.6527.3.1.2.69.1.2.1tmnxIfGroupHandlerProtoEntryTIMETRA-IF-GROUP-HANDLER-MIB
1.3.6.1.4.1.6527.3.1.2.69.1.2.1.2tmnxIfGroupHdlrProtoStatusTIMETRA-IF-GROUP-HANDLER-MIB

Module

This MIB depends on