TIMETRA-SCHEDULER-MIB :: tTimeRangeTriggers

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-SCHEDULER-MIBtTimeRangeTriggers

tTimeRangeTriggers

Module: TIMETRA-SCHEDULER-MIB

OID (symbolic): TIMETRA-SCHEDULER-MIB::tTimeRangeTriggers

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.37.1.1.2.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The value of the object tTimeRangeTriggers indicates the number of times that the time-range has been active. A time-range is considered to be active each time the current date and time maintained in this managed system (TIMETRA-SYSTEM-MIB::stiDateAndTime) falls within one of the range-entries defined for this time-range.

What is tTimeRangeTriggers?

This counter increments each time the router's clock enters this time-range's window, i.e. each time the time-range becomes active. Admins use it to confirm a scheduled policy (like a business-hours QoS change) is actually firing on the expected cadence.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.37.1.1.2.1.5
snmpwalk -v2c -c public <target> TIMETRA-SCHEDULER-MIB::tTimeRangeTriggers

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.37.1.1.2.1.5.1
snmpget -v2c -c public <target> TIMETRA-SCHEDULER-MIB::tTimeRangeTriggers.1

Start monitoring Nokia/Alcatel-Lucent 7750 SR / 7450 ESS SROS routers (time-based policy scheduler active/trigger status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-SCHEDULER-MIB::tTimeRangeTriggers OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR / 7450 ESS SROS routers (time-based policy scheduler active/trigger status) from a single console.

How to Use in IPNetwork Monitor

Select a Nokia/Alcatel-Lucent 7750 SR / 7450 ESS SROS router (time-based policy scheduler active/trigger 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 tTimeRangeTriggers 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 value of the object tTimeRangeTriggers indicates the number of times that the time-range has been active. 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 a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. 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.37tmnxSchedulerTIMETRA-SCHEDULER-MIB
1.3.6.1.4.1.6527.3.1.2.37.1tmnxTimeOfDayPlcyObjectsTIMETRA-SCHEDULER-MIB
1.3.6.1.4.1.6527.3.1.2.37.1.1tmnxTimeRangeObjectsTIMETRA-SCHEDULER-MIB
1.3.6.1.4.1.6527.3.1.2.37.1.1.2tmnxTimeRangeTableTIMETRA-SCHEDULER-MIB
1.3.6.1.4.1.6527.3.1.2.37.1.1.2.1tmnxTimeRangeEntryTIMETRA-SCHEDULER-MIB
1.3.6.1.4.1.6527.3.1.2.37.1.1.2.1.5tTimeRangeTriggersTIMETRA-SCHEDULER-MIB