CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB :: cucsMappingsMoContainmentParentDn

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB › cucsMappingsMoContainmentParentDn

cucsMappingsMoContainmentParentDn

Module: CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB::cucsMappingsMoContainmentParentDn

OID (numeric): 1.3.6.1.4.1.9.9.719.3.1.1.3

Node type: OBJECT-TYPE

Type: CucsManagedObjectDn

Access: read-only

Description: Parent distinguished name (Dn).

What is cucsMappingsMoContainmentParentDn?

This is the distinguished name of the parent managed object in a UCS containment relationship, a row in the mappings table that records which object contains which. This table exists specifically so an SNMP manager can reconstruct the hierarchical parent/child structure of the UCS Management Information Tree without already knowing every Dn in advance, which matters for tools that need to walk the tree dynamically. A value like sys/chassis-1/blade-3 as a parent Dn, paired with a child row for that blade's CPU, lets a manager confirm the CPU is contained within blade 3 of chassis 1.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.3.1.1.3
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB::cucsMappingsMoContainmentParentDn

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.3.1.1.3.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB::cucsMappingsMoContainmentParentDn.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsMappingsMoContainmentParentDn.1

Start monitoring Cisco UCS Manager-managed compute platforms with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-MAPPINGS-MIB::cucsMappingsMoContainmentParentDn OID value, configure state conditions and alerts, and monitor any Cisco UCS Manager-managed compute platforms from a single console.

OID Breakdown

Upper-level ancestors (9 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
Numeric OIDNameModule
1.3.6.1.4.1.9.9.719.3cucsMappingsObjectsCISCO-UNIFIED-COMPUTING-MAPPINGS-MIB
1.3.6.1.4.1.9.9.719.3.1cucsMappingsMoContainmentTableCISCO-UNIFIED-COMPUTING-MAPPINGS-MIB
1.3.6.1.4.1.9.9.719.3.1.1cucsMappingsMoContainmentEntryCISCO-UNIFIED-COMPUTING-MAPPINGS-MIB
1.3.6.1.4.1.9.9.719.3.1.1.3cucsMappingsMoContainmentParentDnCISCO-UNIFIED-COMPUTING-MAPPINGS-MIB