Specifications

ManualsBrandsCisco ManualsComputer equipmentCRS-1 - Carrier Routing System Router

101

102

103

104

105

106

107

108

109

110

10-102

Cisco CRS-1 Series Carrier Routing System XML API Guide

OL-4596-02

Chapter 10 Error Reporting in Cisco CRS-1 Series XML Responses

Types of Reported Errors

These error categories are described in the following sections:

• Error Attributes, page 10-102

• Transport Errors, page 10-102

• XML Parse Errors, page 10-102

• XML Schema Errors, page 10-103

• Operation Processing Errors, page 10-105

• Error Codes and Messages, page 10-105

Error Attributes

If one or more errors occur during the processing of a requested operation, the corresponding XML

response includes error information for each element or object class in error. The error information is

included in the form of ErrorCode and ErrorMsg attributes providing a relevant error code and error

message respectively.

If one or more errors occur during the processing of an operation, error information is included for each

error at the appropriate point in the response. In addition, error attributes are added at the operation

element level. As a result, the client application does not have to search through the entire response to

determine if an error has occurred. However, the client can still search through the response to identify

each of the specific error conditions.

Transport Errors

Transport-specific errors, including failed authentication attempts, are handled by the appropriate XML

agent.

XML Parse Errors

This general category of errors includes those resulting from malformed XML and mismatched XML

tags.

The Cisco CRS-1 Series router checks each XML request, but does not validate the request against an

XML schema. If the XML contains invalid syntax and thus fails the well-formedness check, the error

indication is returned in the form of error attributes placed at the appropriate point in the response. In

such cases, the response may not contain the same XML as was received in the request, but just the

portions to the point where the syntax error was encountered.

In the following example, the client application sends a request to the Cisco CRS-1 Series router that

contains mismatched tags, that is, the opening <BGPEntity> tag is not paired with a closing

</BGPEntity> tag. This example illustrates the format and placement of the error attributes.

Note The actual error codes and messages might be different than what is shown in this example. Also, the

actual error attributes does not contain new line characters.

Sample XML Client Request Containing Mismatched Tags

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