Specifications

5-68

Cisco CRS-1 Series Carrier Routing System XML API Guide

OL-4596-02

Chapter 5 Cisco CRS-1 Series XML and Native Data Access Techniques

Available Set of Native Data Access Techniques

The object class hierarchy may also be compressed into the most “efficient” XML. In other words, it is

not necessary to repeat hierarchies within a request.

Before combining multiple operations inside one <Get> tag, the following limitations should be noted

for Release 3.0. Any operations that request multiple items of data must be sent in a separate XML

request. They include:

• An operation to retrieve all data beneath a container. For more information, see“XML Request for

All Data Within a Container” section on page 5-65.

• An operation to retrieve the list of entries in a table. For more information, see “XML Request Using

Operation Scope (Content Attribute)” section on page 5-74.

• An operation which includes a wildcard. For more information, see “XML Request Using

Wildcarding (Match Attribute)” section on page 5-70.

If an attempt is made to make such an operation followed by another operation within the same request,

the following error will be returned:

XML Service Library detected the ‘fatal’ condition. The XML document which led to

this response contained a request for a potentially large amount of data, which

could return a set of iterators. The document also contained further requests for

data, but these must be sent in a separate XML document, in order to ensure that

they are serviced.

The error indicates that the operations must be separated out into separate XML requests.

The following two examples illustrate two different object class hierarchies that retrieve the same data:

the value of the leaf object <RemoteAS> and <EBGPMultihopMaxHopCount> for the BGP neighbor

with the address 10.0.101.6 and all of the configuration data for the BGP neighbor with the address

10.0.101.7:

Example 1: Verbose Form of a Request Using Duplicated Object Class Hierarchies

Sample XML Client Request for Specific Configuration Data Values

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

<Get>

<AS>

</Naming>

</IPAddress>

</Naming>

</Neighbor>

</NeighborTable>

</BGPEntity>

</AS>

</BGP>

</Configuration>

</Get>