CNTAU-MIB :: cntHwReset2Why

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCNTAU-MIBcntHwReset2Why

cntHwReset2Why

Module: CNTAU-MIB

OID (symbolic): CNTAU-MIB::cntHwReset2Why

OID (numeric): 1.3.6.1.4.1.333.1.1.4.10

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-only

Description: The reason for the second-to-last reset.

What is cntHwReset2Why?

This read-only DisplayString reports the reason recorded for the second-to-last reset of this node, one step further back in reset history than cntHwReset1Why. An admin investigating a pattern of repeated instability would compare this against the most recent reset reason to see whether the same root cause keeps recurring. For example, finding the same 'watchdog timeout' reason in both this and the most recent reset slot would indicate a persistent, unresolved problem rather than a one-off event.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.333.1.1.4.10
snmpwalk -v2c -c public <target> CNTAU-MIB::cntHwReset2Why

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.333.1.1.4.10.1
snmpget -v2c -c public <target> CNTAU-MIB::cntHwReset2Why.1

Start monitoring CNT Fibre Channel access-unit/channel-extension device (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CNTAU-MIB::cntHwReset2Why OID value, configure state conditions and alerts, and monitor any CNT Fibre Channel access-unit/channel-extension device (legacy) from a single console.

OID Breakdown

Upper-level ancestors (7 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.333cntCNT2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.333.1cntauCNTAU-MIB
1.3.6.1.4.1.333.1.1cntsystemCNTAU-MIB
1.3.6.1.4.1.333.1.1.4cntSysHardwareCNTAU-MIB
1.3.6.1.4.1.333.1.1.4.10cntHwReset2WhyCNTAU-MIB