Request Type Tag And Namespaces; Object Class Hierarchy - Cisco CRS-1 - Carrier Routing System Router Api Manual

Native Data Operation Content
</Operation>
</Request>
Sample XML Response from the Cisco CRS-1 Series Router
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
<Operation>
</Operation>
</Response>

Request Type Tag and Namespaces

The request type tag must follow the operation type tag within a native data operation request.
The type of the request must be specified as applying to one of the namespaces listed in
Table 4-1
Namespace
<Configuration>
<Operational>
<Action>
<AdminOperational>
<AdminAction>

Object Class Hierarchy

A hierarchy of elements is included to specify the items to get, set, or delete, and so on, after the request
type tag is specified. The precise hierarchy is defined by the Cisco CRS-1 Series XML component
schemas.
The Cisco CRS-1 Series XML schema information is mapped to the XML instance.
Cisco CRS-1 Series Carrier Routing System XML API Guide
4-52
.
</Request Type>
<Request Type>
.
.
.
response content returned here
.
.
.
</Request Type>
Namespace Descriptions
Chapter 4 Cisco CRS-1 Series XML and Native Data Operations
Description
Provides access to the router configuration data analogous to
command-line interface (CLI) configuration commands. The
allowed operations on configuration data are <Get>, <Set>, and
<Delete>.
Provides access to the router operational data and is analogous to
CLI show commands. The only operation allowed on operational
data is <Get>.
Provides access to the action data, for example, the clear
commands. The only allowed operation on action data is <Set>.
Provides access to the router administration operational data. The
only operation allowed on administration operational data is <Get>.
Provides access to the router administration action data, for
example, the clear commands. The only allowed operation on
administration action data is <Set>.
Table 4-1.
OL-4596-01