The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This appendix includes the following topics:
The configConfMo method is used to configure one or more properties in a Managed Object (MO). The MO to be configured is uniquely identified by a Distinguished Name (DN). This chapter shows two ways to provide a DN using the configConfMo method.
You can provide a DN at the Managed Object level. In the following example, the DN "sys/rack-unit-1/locator-led" is defined within the "equipmentLocatorLed" MO.
<configConfMo
cookie="<real_cookie>">
<inConfig>
<equipmentLocatorLed
adminState='on'
dn='sys/rack-unit-1/locator-led'> <== MO level
</equipmentLocatorLed>
</inConfig>
</configConfMo>
You can provide a DN at the Method and Managed Object level. In the following example, the DN "sys/rack-unit-1/locator-led" is defined at the configConfMo method level and within the "equipmentLocatorLed" MO.
<configConfMo cookie="<real_cookie>" dn='sys/rack-unit-1/locator-led'> <== Method level <inConfig> <equipmentLocatorLed adminState='on' dn='sys/rack-unit-1/locator-led'> <== MO Level </equipmentLocatorLed> </inConfig> </configConfMo>
Note | Specifying a DN at the Method level is optional, and is supported in the Cisco IMC XML API implementation to be consistent with the Cisco UCS Manager XML API implementation. |
When a configConfMo request is sent to Cisco IMC, the response contains only the immediate properties of the MO being configured.
When the optional inHierarchical attribute is included in the configConfMo request, the response will be similar to that of the configResolveDn request with the inHierarchical attribute set to true. The response contains the properties for the MO being configured along with the properties of any children MOs.
Request:
<configConfMo cookie="<real_cookie>" inHierarchical="true" dn='sys/rack-unit-1/locator-led'> <inConfig> <equipmentLocatorLed adminState='on' dn='sys/rack-unit-1/locator-led'> </equipmentLocatorLed> </inConfig> </configConfMo>
Response:
<configConfMo dn="sys/rack-unit-1/locator-led" cookie="<real_cookie>" response="yes"> <outConfig> <equipmentLocatorLed dn="sys/rack-unit-1/locator-led" adminState="inactive" color="unknown" id="1" name="" operState="on"> </equipmentLocatorLed> </outConfig> </configConfMo>
The Cisco IMC XML API implementation accepts only configConfMo methods that operate on a single Managed Object (MO). It is invalid to specify a configConfMo method that contains multiple MOs even if they are defined in a containment relationship in the Cisco IMC management information model.
The following example shows a valid configConfMo method to configure a single MO, "lsbootLan." In this example, the host is configured to use PXE Boot as the first boot option:
<configConfMo
cookie="<real_cookie>">
<inConfig>
<lsbootLan <== Single MO
order="1"
status="modified"
dn="sys/rack-unit-1/boot-policy/lan" >
</lsbootLan>
</inConfig>
</configConfMo>
The configConfMo method in the following example is invalid because a Parent and Child MOs are specified at the same time. The "equipmentLocatorLed" and "solIf" MOs are child objects of the "computeRackUnit" MO in the management information tree. The Cisco IMC XML API implementation does not allow a configConfMo method to perform subtree configurations.
Request:
<configConfMo cookie="1313084260/40ea8058-aa3e-1a3e-8004-5e61c2e14388" dn="sys/rack-unit-1" inHierarchical="false"> <inConfig> <computeRackUnit <== Parent MO adminPower="cycle-immediate" usrLbl="Cisco C210 Server" dn="sys/rack-unit-1"> <equipmentLocatorLed <== Child MO adminState="on" dn="sys/rack-unit-1/locator-led"/> <solIf <== Child MO dn="sys/rack-unit-1/solif" adminState="enable" speed="9600"/> </computeRackUnit> </inConfig> </configConfMo>
Response:
XML PARSING ERROR: Element 'equipmentLocatorLed': This element is not expected.
Note | This method is valid in the Cisco UCS Manager XML API implementation but is not supported in the Cisco IMC XML API implementation. |