The GET syntax is a list of attribute names in an XML string. For more information on attributes, see the attribute summary appendices.
Usage Guidelines
To use the GET operation, build an XML string with a list of attributes whose vlaues to be retrieved and invoke the appropriate IDL method on the VCG server (invoke() method).
The XML string with the required attributes looks as follows:
The SET syntax is a list of attribute names and values in an XML string. For more information on attributes, see the attribute summary appendices. Set those attributes that have read/write permission.
Usage Guidelines
To use the SET operation, build and XML string with a list of attributes and values to be set and invoke the appropriate IDL method on the VCG server (invoke() method).
The XML string with the required attributes looks as follows:
The bulk action syntax includes an action name to be carried out on objects of the class identified by attribute "identify" of the <MO> tag. Furthermore, it specifies the action to tbe carried out on specific instances of the class specified by the special attribute name "PATH", in the list of attributes specified. The parameters of the action are those attributes which are not the name "PATH" in the list of attributes specified. The above can be repeated for more than one class; the <MO> tag can be repeated multiple times.
Table 4-1 Bulk Action Attributes
attributeName
attributeValue
Type
PATH
The containment path for the EM object. This attribute is required.
char
EMCtlr:EMCtlr-MIB.SoftwareDownLoadSourceFile
The fully qualified name and path to the software image source file. This attribute is required.
char
EMCtlr:EMCtlr-MIB.SoftwareDownLoadDestFile
The destination file name. This attribute is required. The name of the software image.
This name indicates the card type, major release, minor release, and version, followed by the .fw extension. For example, SCC_R01.02.03.FW indicates SCC software release 1.2.3. The release and version information (R01.02.03) must be 9 characters in length.
char
Usage Guidelines
To use the BULK ACTION operation, build an XML string with list of EMS objects, parameters (attribute names and values, if any). This is an example of the result of a BULKACTION request:
The XML string with the required attributes looks as follows:
The BULKGETREQUEST operation can read attributes from multiple Cisco MGX 8260 Media Gateways. The request XML string has sections for each chassis, each of which contain a list of attribute names for which attribute values are required. The syntax shows how to use the <MO> and <OA> tags for this type of request.
Usage Guidelines
To use the BULKGETREQUEST operation, build an XML file with a list of chassis, attributes and values to retrieve. The following example shows the results of a BULDGETREQUEST argument:
The BULKSETREQUEST operation can read attributes from multiple Cisco MGX 8260 Media Gateways. The request XML string has sections for each chassis, each of which contain a list of attribute names for which attribute values are required. The syntax shows how to use the <MO> and <OA> tags for this type of request.
Usage Guidelines
To use the BULKSETREQUEST operation, build an XML file with a list of chassis, attributes, and values to retrieve. The following example shows the results of a BULDSETREQUEST operation:
The QUERY operation discovers objects in the root path that match the query criteria. The root path is the containment path to search; the query criteria are keywords that identify subchassis objects. This operation facilitates discovering the containment path for all objects of a specific type.
QUERY Operation
This operation searches a root path for child classes.
<QUERY>
<ROOTPATH> cmgm:/</ROOTPATH>
<CHILDCLASS>identity1</CHILDCLASS>
<CHILDCLASS>identity2</CHILDCLASS>
...
</QUERY>
Syntax Description
The XML input specifies the ROOTPATH in the EMS object tree whose children are to be searched for the matching CLASSNAME.
Usage Guidelines
To query for managed objects, construct an XML string with a list of the identities to discover. Query all sites by specifying EM: as the target. Cisco Voice CORBA Gateway discovers and returns the full path to the discovered objects. The root path of EM: searches for all objects that match the specified identity.
The results of a query return the containment path for each child class found. The following example shows the results of a QUERY for BSC cards: