H3C Technologies H3C Intelligent Management Center - Manual (Page 511)

497
<SysOID>1.3.6.1.4.1.2011</SysOID>
</Capability>
</DevCapabilities>
The properties supported by the elements in the file are described as follows:
• DevCapabilities element
The DevCapabilities element is the root node the operation definition file, and does not support any
property.
• Capability element, shown in Figure 90 .
Figure 90 Properties supported by the Capability element
Property
name
Description Required Remarks
name Name Y
ALL is reserved, meaning all devices. The name must be
unique in a file.
• SysOID element
The content of the sysOID element is the device sysOID. sysOID can be a complete sysOID meaning a
specific device model, or part of a sysOID meaning a device series.
Example: specify the capability set to support all 3Com devices and a specific Cisco device.
<Capability name="baseDC">
<!-- support all 3Com devices-->
<SysOID>1.3.6.1.4.1.43</SysOID>
<!--support a specific Cisco device-->
<SysOID>1.3.6.1.4.1.9.1.501</SysOID>
</Capability>
Replaceable variable list
Replaceable variables are used to replace the specified property values in the registration file. For
example, to replace the value property value of the Parameter element or uri property value of the
RestAction element. The replaceable variable is in the format of ${VARIABLE _NAME}, and must start with
${ and end with }.
The replaceable variables include three categories: user-defined replaceable variables, system-level
replaceable variables, and parameter-level replaceable variables. In certain cases, you must enter some
properties or names multiple times. To address this issue, the system allows for user-defined replaceable
variables in registration files; pre-defines some commonly used replaceable variables for you as shown
in the table below; and lets you reference a parameter in the {parameter name} format, which is called
a parameter-level replaceable variable. For the property of an action, only the parameters of the action
are allowed to be used.
The system replaces the user-defined replaceable variables when loading the registration file, replaces
system-level replaceable variables when executing actions, and then replaces the parameter-level
replaceable variables. In the following example, ${vlanId} is a parameter-level replaceable variable.
<RestAction id="addPort2VlanAction" protocol="http" ip="${IMC_SERVER_IP}"
port="${IMC_HTTP_PORT}" uri="/imcrs/vlan/${vlanId}" userName="${IMC_USER_NAME}"
userPassword="${IMC_USER_PWD}" method="2">
<Parameter name="devId" value="${DEVICE_ID}" />
<Parameter name="vlanId" label="%str.vlanId" required="true"
validateRegEx="[2-9]|[1-3]?[0-9]{2,3}|[4][0][0-8][0-9]|[4][0][9][0-4]"