Resync Url - Cisco WRP400-G1 - Wireless Router Administration Manual

Product Overview and Deployment Guidelines
Remote Provisioning
NOTE
Cisco Small Business WRP400 Administration Guide
Both HTTP and TFTP are supported for the upgrade operation.
protocol
If no is specified, TFTP is assumed. If no
host that requests the URL is used as
If no port specified, the default port of the protocol is used. (69 for TFTP or 80 for
HTTP)
firmware-pathname
The
directory on the TFTP or HTTP server. If no
spa.bin
is assumed, as in the following example:
http://192.168.2.217/admin/upgrade?tftp://192.168.2.251/
spa.bin

Resync URL

The WRP400 can be configured to automatically resync its internal configuration
state to a remote profile periodically and on power up. The automatic resyncs are
controlled by configuring the desired profile URL into the device.
The Resync URL lets you force the WRP400 to do a resync to a profile specified in
the URL, which can identify either a TFTP, HTTP, or HTTPS server. The syntax of
the Resync URL is as follows:
http://WRP400_ip_address/admin/resync?[[protocol://][server-
name[:port]]/profile-pathname]
The WRP400 resyncs only when it is idle.
If no parameter follows
page is used.
protocol
If no is specified, TFTP is assumed. If no
host that requests the URL is used as
If no port is specified, the default port is used (69 for TFTP, 80 for HTTP, and 443
for HTTPS).
The profile-path is the path to the new profile with which to resync, for example:
http://192.168.2.217/admin/resync?tftp://192.168.2.251/
spaconf.cfg
server-name
is typically the file name of the binary located in a
firmware-pathname
/resync?,
the Profile Rule setting from the Provisioning
server-name
server-name
is specified, the
.
is specified,
server-name
is specified, the
.
1
/
18