CISCO-UNIFIED-COMPUTING-LS-MIB :: cucsLsRequirementOperName

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-LS-MIBcucsLsRequirementOperName

cucsLsRequirementOperName

Module: CISCO-UNIFIED-COMPUTING-LS-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementOperName

OID (numeric): 1.3.6.1.4.1.9.9.719.1.26.4.1.13

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS ls:Requirement:operName managed object property

What is cucsLsRequirementOperName?

The MIB's DESCRIPTION for cucsLsRequirementOperName is only the auto-generated stub 'Cisco UCS ls:Requirement:operName managed object property', but the 'operName' property name together with its SnmpAdminString type tell us this column, on a service profile's server-pool requirement (the qualifier UCS Manager uses to auto-pick a blade from a pool), holds the operName as UCS Manager's data model defines it, exposed here as a read-only SNMP value (read-only). The operName is the name UCS Manager actually operationally assigned for this requirement's resolved server binding, which can differ from any name an admin manually configured if the pool auto-generated it. This would surface whatever effective name ended up applying to the pool-assigned server for this profile.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.26.4.1.13
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementOperName

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.26.4.1.13.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementOperName.1

Start monitoring Cisco UCS Manager managed service profiles (logical servers) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementOperName OID value, configure state conditions and alerts, and monitor any Cisco UCS Manager managed service profiles (logical servers) 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.26cucsLsObjectsCISCO-UNIFIED-COMPUTING-LS-MIB
1.3.6.1.4.1.9.9.719.1.26.4cucsLsRequirementTableCISCO-UNIFIED-COMPUTING-LS-MIB
1.3.6.1.4.1.9.9.719.1.26.4.1cucsLsRequirementEntryCISCO-UNIFIED-COMPUTING-LS-MIB
1.3.6.1.4.1.9.9.719.1.26.4.1.13cucsLsRequirementOperNameCISCO-UNIFIED-COMPUTING-LS-MIB