Specifications

4-52

Cisco CRS-1 Series Carrier Routing System XML API Guide

OL-4596-02

Chapter 4 Cisco CRS-1 Series XML and Native Data Operations

Native Data Operation Content

</Request Type>

</Operation>

</Request>

Sample XML Response from the Cisco CRS-1 Series Router

<?xml version="1.0" encoding="UTF-8"?>

response content returned here

</Request Type>

</Operation>

</Response>

Request Type Tag and Namespaces

The request type tag must follow the operation type tag within a native data operation request.

Table 4-1 describes the type of the request that must be specified as applying to one of the namespaces.

Object 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.

Table 4-1 Namespace Descriptions

Namespace Description

<Configuration> 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>.

<Operational> Provides access to the router operational data and is analogous to CLI show

commands. The only operation allowed on operational data is <Get>.

<Action> Provides access to the action data, for example, the clear commands. The

only allowed operation on action data is <Set>.

<AdminOperational> Provides access to the router administration operational data. The only

operation allowed on administration operational data is <Get>.

<AdminAction> Provides access to the router administration action data, for example, the

clear commands. The only allowed operation on administration action data

is <Set>.