Error Attributes; Transport Errors; Xml Parse Errors - Cisco CRS-1 - Carrier Routing System Router Api Manual

Carrier routing system xml api guide
Hide thumbs Also See for CRS-1 - Carrier Routing System Router:
Table of Contents

Advertisement

Types of Reported Errors
These error categories are described in the following sections:

Error Attributes

If one or more errors occur during the processing of a requested operation, the corresponding XML
response will include 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 will be included for
each error at the appropriate point in the response. In addition, error attributes will be added at the
operation element level. As a result, the client application will not have to search through the entire
response to determine if an error has occurred. However, the client will still have to search through the
response in order 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 will check each XML request for well-formedness, but will not validate
the request against an XML schema. If the XML contains invalid syntax and thus fails the
well-formedness check, the error indication will be 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 may be different than what is shown in this example. Note also that
the actual error attributes will not contain new line characters.
Sample XML Client Request Containing Mismatched Tags
<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
Cisco CRS-1 Series Carrier Routing System XML API Guide
10-98
"Error Attributes"
"Transport Errors"
"XML Parse Errors"
"XML Schema Errors"
"Operation Processing Errors"
"Error Codes and Messages"
Chapter 10
Error Reporting in Cisco CRS-1 Series XML Responses
OL-4596-01

Advertisement

Table of Contents
loading

This manual is also suitable for:

Crs-1 series

Table of Contents