Contents
- Notes on Using the configConfMo Method
- Defining a Distinguished Name using the configConfMo Method
- Using the Optional inHierarchical Attribute
- Configuring a Single Managed Object
Notes on Using the configConfMo Method
This appendix includes the following topics:
- Defining a Distinguished Name using the configConfMo Method
- Using the Optional inHierarchical Attribute
- Configuring a Single Managed Object
Defining a Distinguished Name using the configConfMo Method
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.
At the Managed Object Level
You can provide a DN at the Managed Object level. In the following example, the DN "sys/rack-unit-1/sol-if" is defined within the "solIf" MO.
<configConfMo cookie="<real_cookie>"><inConfig><solIf dn="sys/rack-unit-1/sol-if" adminState="enable"> </solIf> </inConfig> </configConfMo>
At the Method and Managed Object Level
You can provide a DN at the Method and Managed Object level. In the following example, the DN "sys/rack-unit-1/sol-if" is defined at the configConfMo method level and within the "solIf" MO.
<configConfMo cookie="<real_cookie>" dn="sys/rack-unit-1/sol-if"> <inConfig> <solIf dn="sys/rack-unit-1/sol-if" adminState="enable"> </solIf> </inConfig> </configConfMo>
 Note | Specifying a DN at the Method level is optional, and is supported in the Cisco CIMC XML API implementation to be consistent with the Cisco UCS Manager XML API implementation. |
Using the Optional inHierarchical Attribute
When a configConfMo request is sent to CIMC, 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="1357578468/de622490-d2b5-12b5-8009-f289f4c42400" inHierarchical="true" dn="sys/rack-unit-1/sol-if"> <inConfig> <solIf dn="sys/rack-unit-1/sol-if" adminState="enable"> </solIf> </inConfig> </configConfMo>
Response:
<configConfMo dn="sys/rack-unit-1/sol-if" cookie="1357578468/de622490-d2b5-12b5-8009-f289f4c42400" response="yes"> <outConfig> <solIf dn="sys/rack-unit-1/sol-if" adminState="enable" name="SoLInterface" speed="115200" comport="com0" status="modified" childAction="deleteNonPresent"> </solIf> </outConfig> </configConfMo>
Configuring a Single Managed Object
The Cisco 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 CIMC 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 "solIf" MO is a child object of the "computeRackUnit" MO in the management information tree. The Cisco CIMC 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">
<solIf <== Child MO
dn="sys/rack-unit-1/solif"
adminState="enable"
speed="9600"/>
</computeRackUnit>
</inConfig>
</configConfMo>
Response:
XML PARSING ERROR: Element 'solif': This element is not expected.
Note | This method is not supported in the Cisco CIMC XML API implementation but is valid in Cisco UCS Manager XML API implementation. |