1-18
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 1 Cisco CRS-1 Series XML API Overview
Cisco CRS-1 Series XML API Tags
Figure 1-1 XML Components and Request/Response Flows
Cisco CRS-1 Series XML API Tags
An external client application can access management data on the Cisco CRS-1 Series router through an
exchange of well structured XML tagged request and response streams. The XML taggest request and
response streams are described in the following sections:
• “Basic XML Request Content”
• “XML Declaration Tag”
• “Operation Type Tags”
• “XML Request Batching”
Basic XML Request Content
This section describes the specific content and format of the XML data exchanged between the client
and the Cisco CRS-1 Series router for the purpose of router configuration and monitoring.
Top-Level Structure
The top level of every request sent by a client application to the Cisco CRS-1 Series router must begin
with an XML declaration tag followed by a request tag and one or more operation type tags. Similarly,
every response returned by the Cisco CRS-1 Series router must begin with an XML declaration tag
followed by a response tag and one or more operation type tags. Each request can contain operation tags
for each supported operation type and the operation type tags can be repeated. The operation type tags
contained in the response will correspond to those contained in the client request.
Sample XML Request from Client Application
<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion=”1” MinorVersion=”0”>
<Operation
1
>
.
.
.
Operation
1
- specific content goes here
...
</Operation
1
>
<Operation
2
>
.
Operation
provider
Operation
provider
Cisco
CRS-1
Series
Operating
System
101398
Operation
provider
Cisco
CRS-1
Series
router
XML
API
library
TTY
XML
agent
XML
req/resp
(
Telnet/ssh
)
XML
req/resp
(
CORBA
)
CORBA
XML
agent
TTY
XML
client
CORBA
client
Native
Operations
Config
services
CLI
access