CISCO-UNIFIED-COMPUTING-VNIC-MIB :: cucsVnicIScsiLCPConfigState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-VNIC-MIBcucsVnicIScsiLCPConfigState

cucsVnicIScsiLCPConfigState

Module: CISCO-UNIFIED-COMPUTING-VNIC-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiLCPConfigState

OID (numeric): 1.3.6.1.4.1.9.9.719.1.53.52.1.9

Node type: OBJECT-TYPE

Type: CucsLsConfigState

Access: read-only

Description: Cisco UCS vnic:IScsiLCP:configState managed object property

What is cucsVnicIScsiLCPConfigState?

This OID reports the FSM lifecycle/configuration state (CucsLsConfigState) of the launched, deployed instance of an iSCSI vNIC as it actually runs on a server, as opposed to the vNIC's policy-level definition (IScsiLCP) — where this deployed iSCSI vNIC instance currently sits in UCS Manager's apply/config workflow (for example applying, applied, or failed-to-apply). An admin cares because a stuck or failed configState here means the iSCSI vNIC's settings have not actually taken effect on the server, even though the desired configuration looks correct in the service profile. For example, after pushing a service profile change, an admin would poll this configState value on the IScsiLCP object to confirm the new iSCSI settings finished applying rather than silently failing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.52.1.9
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiLCPConfigState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.52.1.9.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiLCPConfigState.1

Start monitoring Cisco UCS blade/rack servers and fabric interconnects (vNIC/vHBA) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiLCPConfigState OID value, configure state conditions and alerts, and monitor any Cisco UCS blade/rack servers and fabric interconnects (vNIC/vHBA) from a single console.

OID Breakdown

Upper-level ancestors (10 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
1.3.6.1.4.1.9.9.719ciscoUnifiedComputingMIBCISCO-UNIFIED-COMPUTING-MIB
1.3.6.1.4.1.9.9.719.1ciscoUnifiedComputingMIBObjectsCISCO-UNIFIED-COMPUTING-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.9.719.1.53cucsVnicObjectsCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.52cucsVnicIScsiLCPTableCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.52.1cucsVnicIScsiLCPEntryCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.52.1.9cucsVnicIScsiLCPConfigStateCISCO-UNIFIED-COMPUTING-VNIC-MIB