Managed Objects (MO) are abstractions of Cisco UCS domain resources, such as fabric interconnects, chassis, blades, and rack-mounted servers. Managed Objects represent any physical or logical entity that is either configured or managed in the Cisco UCS Central MIT. For example, physical entities, such as servers, chassis, I/O cards, processors, and logical entities, such as resource pools, user roles, service profiles, and policies are represented as managed objects.
Every managed object is identified in the tree with its Distinguished Name (Dn). It can be uniquely identified within the context of its parent with its Relative Name (Rn). The Dn identifies the place of the MO in the MIT. A Dn is a concatenation of all the relative names starting from the root to the MO itself. Essentially, Dn = [Rn]/[Rn]/[Rn]/…/[Rn].
In the following example, Dn provides a fully qualified name for adaptor-1 in the model.
< dn = "compute/sys-1010/chassis-5/blade-2/adaptor-1" />
This Dn is composed of the following Rn:
computeResourceAggrEp MO: rn="compute" computeSystem MO: rn="sys-<id>" equipmentChassis MO:
rn="chassis-<id>" computeBlade MO: rn="blade-<slotId>" adaptorUnit MO: rn="adaptor-<id>"
A Relative Name (Rn) may have the value of one or more of the
MO's properties embedded in it. It enables in differentiating
multiple MOs of the same type within the context of the parent. Any
properties that form part of the Rn as described earlier are
referred to as Naming properties.
instance, multiple blade MOs reside within chassis MO. The blade MO
contains the blade identifier as part of its Rn (blade-[Id]).
Therefore, uniquely identifying each blade MO in the context of a