All MIBs › CME-MIB › componentIPv4ConfigPhysicalLinkState
componentIPv4ConfigPhysicalLinkState
Module: CME-MIB
OID (symbolic): CME-MIB::componentIPv4ConfigPhysicalLinkState
OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1.6
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, componentIPv4ConfigPhysicalLinkStatus. If this network interface doesn't support up/down/loopback, show 'notApplicable(255)'.
What is componentIPv4ConfigPhysicalLinkState?
This read-write enumeration lets an admin request that a component's physical port be set down, up, or into loopback mode, distinct from componentIPv4ConfigPhysicalLinkStatus which only reports the current state; notApplicable is returned where the port doesn't support these operations. Admins use loopback mode specifically to test a port's local send/receive path without external cabling. For example, an admin sets this object to loopback(2) on a component's port to run a self-test before ruling out a hardware fault versus a cabling issue.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1.6 snmpwalk -v2c -c public <target> CME-MIB::componentIPv4ConfigPhysicalLinkState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1.6.1 snmpget -v2c -c public <target> CME-MIB::componentIPv4ConfigPhysicalLinkState.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1.6.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::componentIPv4ConfigPhysicalLinkState 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 (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.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.3 | ibmAgents | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51 | netfinitySupportProcessorAgent | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2 | bladeCenterSnmpMIB | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.22 | bladeCenter | BLADE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.3.51.2.22.32 | componentConfiguration | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.32.16 | componentNetworkConfiguration | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.32.16.1 | componentIPv4ConfigTable | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1 | componentIPv4ConfigEntry | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.32.16.1.1.6 | componentIPv4ConfigPhysicalLinkState | CME-MIB |