CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB :: cucsEquipmentAdaptorConnDefPolicyOwner

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIBcucsEquipmentAdaptorConnDefPolicyOwner

cucsEquipmentAdaptorConnDefPolicyOwner

Module: CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentAdaptorConnDefPolicyOwner

OID (numeric): 1.3.6.1.4.1.9.9.719.1.15.95.1.10

Node type: OBJECT-TYPE

Type: CucsPolicyPolicyOwner

Access: read-only

Description: Cisco UCS equipment:AdaptorConnDef:policyOwner managed object property

What is cucsEquipmentAdaptorConnDefPolicyOwner?

This records who owns (and can therefore modify) the policy governing this object: the local UCS domain itself, or a higher-level manager such as UCS Central. This comes from Cisco's equipment capability catalog, not live telemetry — it tells UCS Manager how a specific mezzanine/VIC card model's port physically maps to an IOM or motherboard adaptor endpoint, which is what lets UCS Manager validate a hardware configuration before it's even installed. A value of 'local' means the setting can be changed from UCS Manager directly; a value of 'pending-policy' or 'policy' pointing at UCS Central means an admin has to go there instead, which explains why a field sometimes looks greyed out in the local GUI.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.95.1.10
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentAdaptorConnDefPolicyOwner

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.95.1.10.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentAdaptorConnDefPolicyOwner.1

Start monitoring Cisco UCS chassis, blade/rack servers, fabric interconnects with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentAdaptorConnDefPolicyOwner OID value, configure state conditions and alerts, and monitor any Cisco UCS chassis, blade/rack servers, fabric interconnects 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.15cucsEquipmentObjectsCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.95cucsEquipmentAdaptorConnDefTableCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.95.1cucsEquipmentAdaptorConnDefEntryCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.95.1.10cucsEquipmentAdaptorConnDefPolicyOwnerCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB