Specifications

2-36

Cisco CRS-1 Series Carrier Routing System XML API Guide

OL-4596-02

Chapter 2 Cisco CRS-1 Series XML Router Configuration and Management

Additional Cisco CRS-1 Series Router Configuration and Management Options Using XML

</Response>

Additional Cisco CRS-1 Series Router Configuration and

Management Options Using XML

The following sections describe the optional configuration and router management tasks available to the

client application:

• Getting Commit Changes, page 2-36

• Clearing a Target Session, page 2-38

• Rolling Back Configuration Changes to a Specified Commit Identifier, page 2-38

• Rolling Back Configuration Changes to a Specified Number of Commits, page 2-39

• Getting Rollback Changes, page 2-40

• Getting Configuration History, page 2-41

• Getting Configuration Session Information, page 2-43

• Replacing the Current Running Configuration, page 2-44

Getting Commit Changes

When a client application successfully commits the target configuration to the running configuration, the

configuration manager writes a single configuration change event to the system message logging

(syslog). As a result, an event notification is written to the Cisco CRS-1 Series Alarm Channel (that is,

the CORBA event notification channel for alarms) and subsequently forwarded to any registered

configuration agents.

Table 2-3 describes the event notification.

The following example shows a configuration change notification:

RP/0/0/0:Jun 18 19:16:42.561 : %CLIENTLIBCFGMGR-6-CONFIG_CHANGE : A configuration commit

by user ’root’ occurred at ’Wed Jun 18 19:16:18 2003 ’. The configuration changes are

saved on the router by commit ID: ’1000000075’.

Upon receiving the configuration change notification, a client application can then use the <Get>

operation to load and browse the changed configuration.

For more information on CORBA-based event notifications and alarms supported by the Cisco CRS-1

Series XML API, see Chapter 11, “XML Transport and Event Notifications.”

Table 2-3 Event Notification

Name 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.