IBMNETU-MIB :: ibmnetuPCIAdapOperStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › IBMNETU-MIB › ibmnetuPCIAdapOperStatus

ibmnetuPCIAdapOperStatus

Module: IBMNETU-MIB

OID (symbolic): IBMNETU-MIB::ibmnetuPCIAdapOperStatus

OID (numeric): 1.3.6.1.4.1.2.6.150.3.1.1.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The operational status of this PCI adapter.

unknown (1) : If there was problem determining the operational status of the adapter.

not-configured (2) : If the adapter inserted in the slot is recognized but no router configuration exists.

not-present (3) : If no adapter is currently inserted.

does-not-apply (4) : If this adapter does not contain an operational state.

enable-pending (5) : If commands have been issued to enable the adapter but have not been completed.

enabled (6) : If commands have been successfully issued to enable the adapter.

disable-pending (7) : If commands have been issued to disable the adapter but have not been completed.

disabled (8) : If commands have been successfully issued to disable the adapter.

not-initialized (9) : If the adapter has not completed its initialization.

unknown-device (10) : If the adapter inserted in the slot can not be recognized.

hardware-error (11) : If the adapter can not be used nor made ready to be used.

not-powered (12) : If the adapter has had a problem obtaining power from its slot.

diagnostics (13) : If the adapter is currently undergoing diagnostics.

wrs-available (14) : If the adapter is currently configured and available for WAN restoral.

mis-configured (15) : If the adapter is inserted in the slot but the router configuration is of a different type.

What is ibmnetuPCIAdapOperStatus?

This read-only INTEGER reports the operational status of a PCI adapter, covering states from not-present and not-configured through enabled, disabled, hardware-error, and mis-configured, among others. Admins check this to diagnose why a specific adapter isn't functioning, distinguishing hardware faults from configuration mismatches. Seeing mis-configured(15) would tell an admin the physical adapter type doesn't match the router's configuration for that slot, while hardware-error(11) points to a defective card.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.6.150.3.1.1.1.3
snmpwalk -v2c -c public <target> IBMNETU-MIB::ibmnetuPCIAdapOperStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.6.150.3.1.1.1.3.1
snmpget -v2c -c public <target> IBMNETU-MIB::ibmnetuPCIAdapOperStatus.1

Start monitoring IBM NetVista U workstation/thin client with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IBMNETU-MIB::ibmnetuPCIAdapOperStatus OID value, configure state conditions and alerts, and monitor any IBM NetVista U workstation/thin client 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.2ibmATM-ADAPTER-MIB
1.3.6.1.4.1.2.6ibmProdATM-ADAPTER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.6.150ibmnetuIBMNETU-MIB
1.3.6.1.4.1.2.6.150.3ibmnetuhardwareIBMNETU-MIB
1.3.6.1.4.1.2.6.150.3.1ibmnetuhardwareGeneralIBMNETU-MIB
1.3.6.1.4.1.2.6.150.3.1.1ibmnetuPCIAdapTableIBMNETU-MIB
1.3.6.1.4.1.2.6.150.3.1.1.1ibmnetuPCIAdapEntryIBMNETU-MIB
1.3.6.1.4.1.2.6.150.3.1.1.1.3ibmnetuPCIAdapOperStatusIBMNETU-MIB