Http Get Resync - Linksys SPA2102-AU Provisioning Manual

Provisioning guide
Table of Contents

Advertisement

Basic Resync
Also, the configuration profile can be stored in a subdirectory of the server virtual root directory. Again,
this is specified using standard URL notation.
For example, the following is a valid Profile_Rule that requests the file spa2102.cfg, in the server
subdirectory /Linksys/config, for the TFTP server running on host prov.telco.com, which listens for
connection on port 6900.
tftp://prov.telco.com:6900/Linksys/config/spa2102.cfg
Again, macro expansion can be used anywhere in the URL. This can be convenient in organizing a
directory of profiles on the server for the deployed SPA devices. For example, a profile subdirectory
name might be supplied for each SPA in a dedicated general purpose parameter, with its value referred
within a common profile rule via macro expansion.
For example, GPP_B has the following definition:
Dj6Lmp23Q
The Profile_Rule has this value:
tftp://prov.telco.com/Linksys/$B/$MA.cfg
Then, when resyncing, this SPA (assuming a MAC address of 000e08012345) requests the profile at the
following URL:
tftp://prov.telco.com/Linksys/Dj6Lmp23Q/000e08012345.cfg

HTTP GET Resync

HTTP provides a more reliable resync mechanism than TFTP because it is better at establishing a TCP
connection between a SPA client behind a firewall or NAT device and a remote provisioning server on
the Internet. In addition, HTTP servers offer improved filtering and logging features compared to TFTP
servers, which helps to regulate and track connections.
On the SPA client side, using HTTP (with the GET method) simply means changing TFTP to HTTP in
the URL defined in the Profile_Rule parameter.
On the server side, the service provider must install and configure the HTTP server. The SPA does not
require any special configuration setting on the server to be able to resync using HTTP. If a standard web
browser can retrieve a profile from a particular server using HTTP, the SPA should be able to do so as
well.
Exercise
Step 1
Install an HTTP server on the local PC or other accessible host.
The open source Apache server can be downloaded from the Internet.
Step 2
Copy the basic.txt configuration profile from the earlier exercises onto the virtual root directory of the
installed server.
Step 3
Verify proper server installation (and file access of basic.txt) by accessing the profile using a standard
web browser.
Step 4
Modify the Profile_Rule of the test SPA to point to the HTTP server in place of the TFTP server, so as
to download its profile periodically.
For example, assuming the HTTP server is at 192.168.1.300, enter the following value:
Linksys SPA Provisioning Guide
3-6
Chapter 3
Provisioning Tutorial
Version 3.0

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents