Specifications

2-34
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-02
Chapter 2 Cisco CRS-1 Series XML Router Configuration and Management
Configuration Operations
<AS>4</AS>
</Naming>
<Global>
<DefaultMetric>10</DefaultMetric>
</Global>
</AS>
</BGP>
</Configuration>
</Set>
</Request>
Sample XML Response from the Cisco CRS-1 Series Router
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
<Set>
<Configuration/>
</Set>
</Response>
Sample Request to Commit the Target Configuration
<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
<Commit/>
</Request>
Sample XML Response from the Cisco CRS-1 Series Router Showing Failures for Both Requested Operations
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
<Commit ErrorCode="0x40819c00" ErrorMsg="&apos;sysdb&apos; detected the &apos;
warning&apos; condition &apos;One or more sub-operations failed during a best effort
complex operation&apos;">
<Configuration OperationType=”Set”>
<BGP MajorVersion=”1” MinorVersion=”0”>
<AS>
<Naming>
<AS>4</AS>
</Naming>
<Global>
<DefaultMetric ErrorCode="0x409f8c00" ErrorMsg="AS number is wrong -
BGP is already running with AS number 3">10</DefaultMetric>
</Global>
</AS>
</BGP>
</Configuration>
</Commit>
</Response>
For more information, see “Loading a Failed Configuration” section on page 2-34.
Loading a Failed Configuration
The client application uses the <Load> operation along with the <FailedConfig> tag to populate the
target configuration with the failed configuration from the most recent <Commit> operation. Loading
the failed configuration in this way is equivalent to specifying a “true” value for the KeepFailedConfig
attribute in the <Commit> operation.
If the load is successful, the response contains both the <Load> and <FailedConfig> tags. If the load
fails, the response can also contain the ErrorCode and ErrorMsg attributes that indicate the cause of the
load failure.