Cisco CRS-1 - Carrier Routing System Router Api Guide

5-70
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 5 Cisco CRS-1 Series XML and Native Data Access Techniques
Available Set of Native Data Access Techniques
<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)
Use the Match attribute for “wildcarding” of object class naming information. Note that only
all-wildcarded node IDs are supported for the first customer shipping of the Cisco CRS-1 Series XML
API.
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.
Note The Match attribute is supported only for table entries. Furthermore, “*” is the only value currently
supported for Match. Other wildcarding or matching specifications may be supported in future releases.
The following example shows how to use the Match attribute to get the <RemoteAS> value for all
configured BGP neighbors:
Sample XML Client Request Using the Match Attribute Wildcarding
<?xml version="1.0" encoding="UTF-8"?>

Cisco CRS-1 - Carrier Routing System Router Specifications

General

Brand	Cisco
Model	CRS-1 - Carrier Routing System Router
Category	Network Router
Language	English