All MIBs › NOKIA-HWM-MIB › ntcHWAvailabilityStatus
ntcHWAvailabilityStatus
Module: NOKIA-HWM-MIB
OID (symbolic): NOKIA-HWM-MIB::ntcHWAvailabilityStatus
OID (numeric): 1.3.6.1.4.1.94.1.16.7.1.1.1.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Provides more specific information on the state of the unit in this conceptual row. The status column has eleven defined values: inCharge = the unit is fully operational and ready to perform its desired tasks; applicationStarting = the application software is starting up; applicationShutdown = the application software is shutting down; platformStarting = Basic platform software is starting up; resetting = the disk files are closed and hardware reset is forced; separated = Only basic OS software is running. The unit can start application software on request; unconfigured = The administrative state of the unit is 'missing', disk files are closed and only basic OS software is running. The unit refuses to start application software; testing = Selftests can be performed, only basic OS are running; standby = The unit is redundant and is fully operational but not in charge of operations. It is ready to move to 'inCharge' state when necessary; dormant = All connections are physically inactive to enable removal of the unit without electric disturbance in the backplane. Only watchdog software is running for a short duration of time; unavailable = The unit is not physically present or cannot be contacted.
What is ntcHWAvailabilityStatus?
This read-only integer gives fine-grained detail on a unit's operating state, one of eleven defined values such as inCharge, standby, resetting, testing, or unavailable. It lets an admin distinguish cases the simpler ntcHWOperState can't, such as a redundant unit that's fully operational but not currently in charge (standby) versus one actively performing its role (inCharge). For example, seeing ntcHWAvailabilityStatus report unavailable(11) for a slot tells the admin the unit is either physically missing or unreachable, distinct from separated(6) where basic OS software is still running.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.94.1.16.7.1.1.1.1.3 snmpwalk -v2c -c public <target> NOKIA-HWM-MIB::ntcHWAvailabilityStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.94.1.16.7.1.1.1.1.3.1 snmpget -v2c -c public <target> NOKIA-HWM-MIB::ntcHWAvailabilityStatus.1
Start monitoring Nokia network element (router/optical/IP-MPLS hardware modules) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NOKIA-HWM-MIB::ntcHWAvailabilityStatus OID value, configure state conditions and alerts, and monitor any Nokia network element (router/optical/IP-MPLS hardware modules) from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.94 | nokia | NOKIA-AZC-REGISTRATION-MIB |
| 1.3.6.1.4.1.94.1 | nokiaProducts | NOKIA-AZC-REGISTRATION-MIB |
| 1.3.6.1.4.1.94.1.16 | ntcCommon | NOKIA-COMMON-ALARM-REPORTING-MIB |
| 1.3.6.1.4.1.94.1.16.7 | ntcCommonMibs | NOKIA-COMMON-MIB-OID-REGISTRATION-MIB |
| 1.3.6.1.4.1.94.1.16.7.1 | ntcHWMibs | NOKIA-COMMON-MIB-OID-REGISTRATION-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.94.1.16.7.1.1 | ntcHWObjs | NOKIA-HWM-MIB |
| 1.3.6.1.4.1.94.1.16.7.1.1.1 | ntcHWUnitTable | NOKIA-HWM-MIB |
| 1.3.6.1.4.1.94.1.16.7.1.1.1.1 | ntcHWUnitEntry | NOKIA-HWM-MIB |
| 1.3.6.1.4.1.94.1.16.7.1.1.1.1.3 | ntcHWAvailabilityStatus | NOKIA-HWM-MIB |