CME-MIB :: bladeIPv4ConfigPhysicalLinkState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBbladeIPv4ConfigPhysicalLinkState

bladeIPv4ConfigPhysicalLinkState

Module: CME-MIB

OID (symbolic): CME-MIB::bladeIPv4ConfigPhysicalLinkState

OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.1.12.5.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Configuration object for requesting the physical port to be either, down(0), up(1) or loopback(2). To get the current status of a physical port, use the object, bladeIPv4ConfigPhysicalLinkStatus. If this network interface doesn't support up/down/loopback, show 'notApplicable(255)'.

What is bladeIPv4ConfigPhysicalLinkState?

This writable enum lets an admin request that a blade's physical network port be forced down, up, or into loopback mode, distinct from bladeIPv4ConfigPhysicalLinkStatus which only reports the port's current actual state. It's a diagnostic and control tool: an admin can force a port into loopback(2) to test the interface itself in isolation from the rest of the network. An admin isolating a suspected bad NIC on a blade might set bladeIPv4ConfigPhysicalLinkState to loopback(2) to run a self-test before ruling the hardware faulty.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.12.5.1.5
snmpwalk -v2c -c public <target> CME-MIB::bladeIPv4ConfigPhysicalLinkState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.12.5.1.5.1
snmpget -v2c -c public <target> CME-MIB::bladeIPv4ConfigPhysicalLinkState.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::bladeIPv4ConfigPhysicalLinkState OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.

OID Breakdown

Upper-level ancestors (12 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.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
1.3.6.1.4.1.2.3.51.2.22bladeCenterBLADE-MIB
1.3.6.1.4.1.2.3.51.2.22.1processorBladeBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.22.1.12bladeNetworkConfigurationCME-MIB
1.3.6.1.4.1.2.3.51.2.22.1.12.5bladeIPv4ConfigTableCME-MIB
1.3.6.1.4.1.2.3.51.2.22.1.12.5.1bladeIPv4ConfigEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.22.1.12.5.1.5bladeIPv4ConfigPhysicalLinkStateCME-MIB