Specifications

5-70
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
<BGP MajorVersion="1" MinorVersion="0">
<AS>
<Naming>
<AS>3</AS>
</Naming>
<BGPEntity>
<NeighborTable>
<Neighbor>
<Naming>
<IPAddress>
<IPV4Address>10.0.101.6</IPV4Address>
</IPAddress>
</Naming>
<!-- Gets the following two leaf objects for this neighbor -->
<RemoteAS/>
<EBGPMultihopMaxHopCount/>
</Neighbor>
<Neighbor>
<Naming>
<IPAddress>
<!-- Gets all configuration data for this neighbor -->
<IPV4Address>10.0.101.7</IPV4Address>
</IPAddress>
</Naming>
</Neighbor>
</NeighborTable>
</BGPEntity>
</AS>
</Configuration>
</Get>
</Request>
Sample XML Response from the Cisco CRS-1 Series Router
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
<Get>
<Configuration>
.
.
.
response data returned here for both
neighbors
.
.
.
</Configuration>
</Get>
</Response>
XML Request Using Wildcarding (Match Attribute)
Wildcarding of naming information is provided by means of the Match attribute. Match=“*” can be used
on any Naming attribute within a <Get> or <Delete> operation to effectively specify a wildcarded value
for that attribute. The operation applies to all instances of the requested objects.
“*” is the only value supported for Match, though other wildcarding or matching specifications may be
supported in the future. The Match attribute is comprehensively supported for table entries in the
<Configuration> namespace, but in the <Operational> space the limitation currently exists that
nonwildcarded naming information cannot appear in the hierarchy below wildcarded naming
information.