2-36
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 2 Cisco CRS-1 Series XML Router Configuration and Management
Configuration Operations
Commit Errors
If any configuration entered into the target configuration fails to makes its way to the running
configuration as the result of a <Commit> operation (for example, the configuration contains a semantic
error and is therefore rejected by a back-end application’s verifier function), then all of the failed
configuration will be returned in the <Commit> response along with the appropriate ErrorCode and
ErrrorMsg attributes indicating the cause of each failure.
The OperationType attribute is used to indicate whether the failure was a result of a requested <Set> or
<Delete> operation. In the case of a <Set> operation failure, the value to be set is included in the commit
response.
The following example shows <Set> and <Delete> operations to modify the BGP configuration followed
by a <Commit> request resulting in failures for both requested operations. This request corresponds to
the following CLI commands:
router bgp 4
default-metric 10
exit
commit
Sample XML Client Request to Modify the Target Configuration
<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
<Set>
<Configuration>
<BGP MajorVersion=”1” MinorVersion=”0”>
<AS>
<Naming>
<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">
To Next Page
Loading...
Need help?
General
