All MIBs › CISCO-UNIFIED-COMPUTING-LS-MIB › cucsLsRequirementName
cucsLsRequirementName
Module: CISCO-UNIFIED-COMPUTING-LS-MIB
OID (symbolic): CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementName
OID (numeric): 1.3.6.1.4.1.9.9.719.1.26.4.1.5
Node type: OBJECT-TYPE
Type: SnmpAdminString
Access: read-only
Description: Cisco UCS ls:Requirement:name managed object property
What is cucsLsRequirementName?
The MIB's DESCRIPTION for cucsLsRequirementName is only the auto-generated stub 'Cisco UCS ls:Requirement:name managed object property', but the 'name' 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 name as UCS Manager's data model defines it, exposed here as a read-only SNMP value (read-only). On this device it is the human-readable name given to a service profile's server-pool requirement (the qualifier UCS Manager uses to auto-pick a blade from a pool) — the label an administrator typed in (or UCS Manager generated) when the object was created, and it's what shows up in the UCS Manager GUI's name column for that service-profile pool requirement, rather than its Dn. An admin naming things sensibly might see a value like 'DB-License-Pool' or 'Web-Server-01' here depending on the object.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.26.4.1.5 snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementName
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.26.4.1.5.1 snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-LS-MIB::cucsLsRequirementName.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::cucsLsRequirementName 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 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.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | CISCO-UNIFIED-COMPUTING-MIB |
| 1.3.6.1.4.1.9.9.719.1 | ciscoUnifiedComputingMIBObjects | CISCO-UNIFIED-COMPUTING-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.719.1.26 | cucsLsObjects | CISCO-UNIFIED-COMPUTING-LS-MIB |
| 1.3.6.1.4.1.9.9.719.1.26.4 | cucsLsRequirementTable | CISCO-UNIFIED-COMPUTING-LS-MIB |
| 1.3.6.1.4.1.9.9.719.1.26.4.1 | cucsLsRequirementEntry | CISCO-UNIFIED-COMPUTING-LS-MIB |
| 1.3.6.1.4.1.9.9.719.1.26.4.1.5 | cucsLsRequirementName | CISCO-UNIFIED-COMPUTING-LS-MIB |