3-49
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 3 Cisco CRS-1 Series XML Operational Requests and Fault Management
Action Requests
</Set>
</Response>
The following is an additional example showing an action request to clear the peer drop information for
all BGP neighbors. This request is equivalent to the CLI command clear ip bgp peer-drops *.
Sample XML Request to Clear Peer Drop Information for All BGP Neighbors
<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
<Set>
<Action>
<BGP MajorVersion="0" MinorVersion="0">
<ClearDrops>
<All>true</All>
</ClearDrops>
</BGP>
</Action>
</Set>
</Request>
Sample XML Response from the Cisco CRS-1 Series Router
<?xml version="1.0" encoding="UTF-8"?>
<Response MajorVersion="1" MinorVersion="0">
<Set>
<Action/>
</Set>
</Response>
Cisco CRS-1 Series XML and Fault Management
When a client application successfully commits the target configuration to the Cisco CRS-1 Series
router’s running configuration, the configuration manager will write a single configuration change event
to syslog. As a result, a fault management event notification is written to the Cisco CRS-1 Series Alarm
Channel (that is, the Common Object Request Broker Architecture [CORBA] event notification channel
for alarms) and subsequently forwarded to any registered configuration agents.
Configuration Change Notification
Table 3-1 provides event notification for configuration changes information
The following shows an example of a configuration change notification:
RP/0/0/1:Sep 18 09:43:42.747 : %CLIENTLIBCFGMGR-6-CONFIG_CHANGE : A configuration
commit by user root occurred at ’Wed Sep 18 09:43:42 2002 ’. The configuration changes
are saved on the router in file: 010208180943.0
Table 3-1 Event Notifications
Event Notification Description
userid The name of the user who performed the commit operation.
timestamp The date and time of the commit.
commit The unique ID associated with the commit.
To Next Page
Loading...
Need help?
General
