Cisco CRS-1 - Carrier Routing System Router Dokumentacja Pobierz pdf (Strona 71)

5-71

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

Note Although partial wildcarding of NodeIDs is not available in XML, each element of the NodeID has to

be wildcarded, similar to the support on the CLI of */*/* as the only wildcards supported for locations.

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"?>

<Request MajorVersion="1" MinorVersion="0">

<Get>

<Configuration>

<BGP MajorVersion="1" MinorVersion="0">

<AS>

<Naming>

<AS>3</AS>

</Naming>

<BGPEntity>

<NeighborTable>

<Neighbor>

<Naming>

<IPAddress Match=”*”/>

</Naming>

<RemoteAS/>

</Neighbor>

</NeighborTable>

</BGPEntity>

</AS>

</BGP>

</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>

<BGP MajorVersion="1" MinorVersion="0">

<AS>

<Naming>

<AS>3</AS>

</Naming>

<BGPEntity>

<NeighborTable>

<Neighbor>

<Naming>

<IPAddress>

<IPV4Address>10.0.101.1</IPV4Address>

</IPAddress>

</Naming>

<RemoteAS>1</RemoteAS>

</Neighbor>

<Neighbor>

<Naming>

<IPAddress>

<IPV4Address>10.0.101.2</IPV4Address>

</IPAddress>

</Naming>

<RemoteAS>2</RemoteAS>

1 2 ... 66 67 68 69 70 71 72 73 74 75 76 ... 131 132

Komentarze do niniejszej Instrukcji

Brak uwag