CISCO-UNIFIED-COMPUTING-VNIC-MIB :: cucsVnicIScsiBootVnicOperIqnIdentPoolName

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-VNIC-MIBcucsVnicIScsiBootVnicOperIqnIdentPoolName

cucsVnicIScsiBootVnicOperIqnIdentPoolName

Module: CISCO-UNIFIED-COMPUTING-VNIC-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.53.51.1.11

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS vnic:IScsiBootVnic:operIqnIdentPoolName managed object property

What is cucsVnicIScsiBootVnicOperIqnIdentPoolName?

This OID reports the name of the operationally in-use IQN identifier pool that the underlying data vNIC that an iSCSI boot vNIC rides on for its actual Ethernet path (IScsiBootVnic) draws its iSCSI Qualified Name suffix from. An admin cares because iSCSI targets authenticate and authorize by IQN, so knowing which pool generated this initiator's IQN is key to troubleshooting storage-array access issues. For example, if a storage array rejects a server's iSCSI login, an admin would check this iqnIdentPoolName to confirm the initiator's IQN actually came from the pool the storage team allow-listed.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.51.1.11
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiBootVnicOperIqnIdentPoolName

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.51.1.11.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicIScsiBootVnicOperIqnIdentPoolName.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::cucsVnicIScsiBootVnicOperIqnIdentPoolName 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.51cucsVnicIScsiBootVnicTableCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.51.1cucsVnicIScsiBootVnicEntryCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.51.1.11cucsVnicIScsiBootVnicOperIqnIdentPoolNameCISCO-UNIFIED-COMPUTING-VNIC-MIB