All contents are Copyright © 1992-2011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 2 of 4
Introduction
In addition to the web interface, it is also possible to configure the SRP500 using its XML provisioning API.
In simple terms, this allows you to copy an XML configuration file in to the SRP500, rather than using the
Web interface.
This document describes how to use this interface for applying an initial configuration at the time of
installation. Ongoing configuration and monitoring of the SRP500 using the XML interface from a central
provisioning server is out of the scope of this document.
The XML configuration file
XML (Extensible Markup Language) defines a set of rules for encoding documents such that they may be
machine readable and is used by the SRP500 for automated configuration.
In its simplest form, an XML configuration file is a text script that includes a series of tags and values that
represent a series of configuration parameters. Each device uses a schema to define which tags it may use
as it imports a configuration file. Unknown tags are ignored.
For example, a very simple XML configuration file might look like the following.
<?xml version="1.0"?>
<flat-profile>
<!-- This is a sample test configuration -->
<router-configuration>
<WAN_Interface>
<WAN1_PPPoE_User_Name>[email protected]</WAN1_PPPoE_User_Name>
<WAN1_PPPoE_Password>secret-password</WAN1_PPPoE_Password>
</WAN_Interface>
</router-configuration>
</flat-profile>
As this short example illustrates, the XML schema may be hierarchical, allowing characteristics to be
defined for an object. The script may also include comments and indenting to aid the reader, but are
otherwise ignored by the SRP500.
To see a configuration script (and therefore the full device schema) use the following URL in your browser
when connected to an SRP500.
http://192.168.15.1/admin/config.xml&xuser=admin&xpassword=<your_password
>
To aid the development of your own configurations, save this file as a template by right clicking on the
document in your browser and select “View Source”. Save the resulting file, as this will include the XML
header tag and no other display formatting.
Developing an XML configuration
Probably the quickest method of manually building your own configuration file is to copy sections from a
XML file that has been downloaded from a preconfigured device. This may then be tuned to meet the