Cisco SRP521W User manual

Cisco Small Business Managed Router Feature Configuration Guide
Initial SRP500 Configuration using XML

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

All contents are Copyright © 1992-2011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 3 of 4
specific requirement. It is recommended that configuration files are written to include only those
parameters that need to be changed.
Adding Service Provider Default Configurations
It is possible to define a subset of configuration that will be maintained across user initiated factory resets –
either using the device reset button, or the User role web page option.
The SP Defaults feature is enabled through the use of the <Load_SP_Default> tag, or alternatively, the
Administration > Backup & Restore > Default Configuration GUI option. By default, the SRP does not use
Service Provider default configurations.
To define a set of default configurations, use standard XML configuration tags embedded within the
<SP_Default> tag. See below for an example. When creating an initial provisioning script, add all
configuration tags to the main section to configure the device and add them again to the <SP_Default> tag
to define the configuration after reset. Note that the <Load_SP_Default> tag must be included in both the
main section and the <SP_Defaults> section to ensure consistent behaviour across resets.
<?xml version="1.0"?>
<flat-profile>
<!-- Voice configuration tags -->
<router-configuration>
<!-- Router configuration tags -->
</router-configuration>
<Load_SP_Default>1</Load_SP_Default>
<SP_Default>
<!-- Voice configuration tags -->
<router-configuration>
<!-- Router configuration tags -->
<Load_SP_Default>1</Load_SP_Default>
</router-configuration>
</SP_Default>
</flat-profile>
The method described above will configure the default behaviour following reset. Note that the
<SP_Default> tag is not included in the config.xml configuration export.
If the <SP_Default> tag is updated at any point in the future, the new tag definition will replace the old one
in its entirety. The tag does not use incremental configuration, as is the case with the rest of the
configuration script. If you wish to remove all default settings, simply apply an empty tag as follows:
<?xml version="1.0"?>
<flat-profile>
<SP_Default/>
</flat-profile>
Applying the configuration to an SRP500
Having created an XML configuration script, it must be passed to the SRP500 for application.
A number of processes are available to achieve this, chose the preferred method from the following
options:

All contents are Copyright © 1992-2011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 4 of 4
TFTP and the Resync URL:
a. Connect your PC to the SRP500 LAN (we’ll assume that the PC IP address is 192.168.15.100)
b. Run a TFTP server application on the PC and make sure that the configuration file is available in the
TFTP root directory.
c. From a Internet Browser, craft and enter the following URL:
http://<SRP_IP_Address>/admin/resync?tftp://<PC_IP_Address>/<file_name>&
xuser=admin&xpassword=<password>
For example:
http://192.168.15.1/admin/resync?tftp://192.168.15.100/my_config.xml&xuser=admin&
xpassword=admin
Direct HTTP Post using cURL:
a. Connect your PC to the SRP500 LAN
b. Post the configuration file to the SRP using the following cURL command (on one line):
curl –d @my_config.xml
“http://192.168.15.1/admin/config.xml&xuser=admin&xpassword=admin”
Note: cURL may be obtained from http://curl.haxx.se/download.html
USB Day Zero Configuration (currently SRP540 only)
a. Copy the configuration file to the root directory of a USB memory card.
b. Ensure that the file is named using either the product code, or its MAC address. If using the product
code, use the following naming convention: SRP54xW-r-K9.cfg, where x is 1, 6 or 7 and r is E or A. If
using the device MAC address, use capitals and no spaces, for example: 001234ABCDEF.cfg.
c. Connect the memory card to the SRP540, and then apply power.
d. The configuration file will be applied during the boot process. At this time, the SRP500 will first
search for and use a file with its MAC address. If one is not present, it will search for and use a file
with its product code. If neither search is satisfied, the boot process will continue without
configuration.
Further details of this process are posted at: https://supportforums.cisco.com/docs/DOC-14176