All MIBs › FECLIENT827x-MIB › fe827xPCIAdapOperStatus
fe827xPCIAdapOperStatus
Module: FECLIENT827x-MIB
OID (symbolic): FECLIENT827x-MIB::fe827xPCIAdapOperStatus
OID (numeric): 1.3.6.1.4.1.2.6.118.4.1.2.2.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The operational status of this PCI adapter for the balde. The variable shall assume a value of unknown(1) if the adapter inserted in the slot cannot be recognized. The variable shall assume a value of notConfigured(2) if the adapter inserted in the slot is recognized but no router configuration exists. The variable shall assume a value of notPresent(3) if the adapter is not inserted in the slot but the router configuration exists. The variable shall assume a value of unavailable(4) if adapter inserted in the slot can not be used nor made ready to be used; for example, a hardware error. The variable shall assume a value of doesNotApply(5) if this adapter does not contain an operational state. The variable shall assume a value of enablePending(6) if commands have been issued to enable the adapter but have not been completed. The variable shall assume a value of enabled(7) if commands have been successfully issued to enable the adapter. The variable shall assume a value of disablePending(8) if commands have been issued to disable the adapter but have not been completed. The variable shall assume a value of disabled(9) if commands have been successfully issued to disable the adapter. The variable shall assume a value of missConfigured(10) if the adapter is inserted in the slot but the router configuration is of a different type. This object would also drive the Unit LED's.
What is fe827xPCIAdapOperStatus?
This object reports the operational lifecycle state of the PCI adapter in the blade, ranging from unknown(1) or notConfigured(2) through enabled(7), disabled(9), or missConfigured(10), and also drives the unit's status LEDs. An admin uses it to determine whether an adapter that was just inserted and configured has actually come into service, or whether it's stuck in an enablePending(6) or missConfigured(10) state needing attention. Seeing missConfigured(10) means the physical adapter type doesn't match what the router was configured to expect in that slot.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.6.118.4.1.2.2.1.5 snmpwalk -v2c -c public <target> FECLIENT827x-MIB::fe827xPCIAdapOperStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.6.118.4.1.2.2.1.5.1 snmpget -v2c -c public <target> FECLIENT827x-MIB::fe827xPCIAdapOperStatus.1
Start monitoring IBM 827x-series blade (legacy, PCI adapter inventory) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FECLIENT827x-MIB::fe827xPCIAdapOperStatus OID value, configure state conditions and alerts, and monitor any IBM 827x-series blade (legacy, PCI adapter inventory) from a single console.
OID Breakdown
Upper-level ancestors (8 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.2 | ibm | ATM-ADAPTER-MIB |
| 1.3.6.1.4.1.2.6 | ibmProd | ATM-ADAPTER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.6.118 | nwaysMSS | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4 | ibmMSSClientMIB | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4.1 | fe827xMIBObjectGroup | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4.1.2 | fe827xPCIAdapterGroup | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4.1.2.2 | fe827xPCIAdapTable | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4.1.2.2.1 | fe827xPCIAdapEntry | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.4.1.2.2.1.5 | fe827xPCIAdapOperStatus | FECLIENT827x-MIB |