TIGER :: tigClearStats

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIGER › tigClearStats

tigClearStats

Module: TIGER

OID (symbolic): TIGER::tigClearStats

OID (numeric): 1.3.6.1.4.1.1978.2.1.2.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: When set to 'clear' all of TIGERs statistics are cleared to zero. It will affect each of the ports statistics herarcially, and also AUTIF statistics.

When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as:

1/ all of the statistics have actually been zeroed, and 2/ tigClearStatsTime has been updated with the correct time.

Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request.

Normal operation would be:

NMS Agent

set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' <-- . clearing complete, set to 'cleared' . read --> . 'cleared' <-- set to 'cleared-confirmed' . read --> . 'cleared-confirmed' <-- .

Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'.

What is tigClearStats?

Setting this object to clear(1) resets all of the Tiger's statistics counters to zero, including per-port statistics and AUTIF statistics, hierarchically across the device. After the clear completes the agent sets it to cleared(2), and once an NMS has read that cleared value, the agent moves it to cleared-confirmed(3) to acknowledge the round trip. Admins follow the documented read/set sequence (confirm cleared-confirmed before issuing a new clear, then read cleared and cleared-confirmed after) so a missed clear command isn't mistaken for a completed one.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.2.8
snmpwalk -v2c -c public <target> TIGER::tigClearStats

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1978.2.1.2.8.1
snmpget -v2c -c public <target> TIGER::tigClearStats.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1978.2.1.2.8.1 i <value>

Start monitoring Northrop Grumman-Canada, Ltd. Tiger system equipment (interface-stack/hardware configuration status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIGER::tigClearStats OID value, configure state conditions and alerts, and monitor any Northrop Grumman-Canada, Ltd. Tiger system equipment (interface-stack/hardware configuration status) from a single console.

OID Breakdown

Upper-level ancestors (8 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.1978ngcanALC-MIB
1.3.6.1.4.1.1978.2tigerALC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1978.2.1generalTigerTIGER
1.3.6.1.4.1.1978.2.1.2tsystemTIGER
1.3.6.1.4.1.1978.2.1.2.8tigClearStatsTIGER