Cisco SPA2102-AU Provisioning Guide - Page 38

URL Syntax, Optional Resync Arguments, key - firmware 5 2 12

Get Cisco SPA2102-AU PDF manuals and user guides View all Cisco SPA2102-AU manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

Proprietary Plain-Text Configuration File Chapter 2 Creating Provisioning Scripts Any parameter can be assigned a new value in this way, and macro-expansion applies. For example, the following is a valid assignment expression: ( User_ID_1_ = "uid$B" ; GPP_C = "" ; GPP_D = "$MA" ; )! For conciseness, the general purpose parameters GPP_A through GPP_P can also be referred to by the single lowercase letters a through p. The example above is equivalent to the following: ( User_ID_1_ = "uid$B" ; c = "" ; d = "$MA" ; )! White space can optionally be used for readability. URL Syntax Standard URL syntax is used to specify how to retrieve configuration files and firmware loads in Profile_Rule* and Upgrade_Rule parameters, respectively. The syntax is as follows: [ scheme:// ] [ server [:port]] filepath Where scheme is one of the following values: • tftp • http • http If scheme is omitted, tftp is assumed. The server can be a DNS-recognized host name or a numeric IP address. The port is the destination UDP or TCP port number. The filepath must begin with the root directory (/). In other words, it must be an absolute path. If server is missing, then the tftp server specified through DHCP (option 66) is used instead. If port is missing, then the standard port for the specified scheme is used instead (tftp uses UDP port 69, http uses TCP port 80, https uses TCP port 443). A filepath must be present. It need not necessarily refer to a static file, but can indicate dynamic content obtained through CGI. Macro expansion applies within URLs. The following are examples of valid URLs: /$MA.cfg /Linksys/spa021025.bin 192.168.1.130/profiles/init.cfg tftp://prov.call.com/cpe/Linksys$MA.cfg http://neptune.speak.net:8080/prov/$D/$E.cfg https://secure.me.com/profile?Linksys Optional Resync Arguments The URLs entered in Profile_Rule* parameters may be preceded by optional arguments, collectively enclosed by square brackets. The recognized options are key, post, and alias. key The key option is used to specify an encryption key. It is required to decrypt profiles which have been encrypted with an explicit key. The key itself is specified as a (possibly quoted) string following the term --key. 2-12 Linksys SPA Provisioning Guide Version 3.0

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
2-12
Linksys SPA Provisioning Guide
Version 3.0
Chapter 2
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Any parameter can be assigned a new value in this way, and macro-expansion applies. For example, the
following is a valid assignment expression:
( User_ID_1_ = “uid$B” ; GPP_C = “” ; GPP_D = “$MA” ; )!
For conciseness, the general purpose parameters GPP_A through GPP_P can also be referred to by the
single lowercase letters a through p. The example above is equivalent to the following:
( User_ID_1_ = “uid$B” ; c = “” ; d = “$MA” ; )!
White space can optionally be used for readability.
URL Syntax
Standard URL syntax is used to specify how to retrieve configuration files and firmware loads in
Profile_Rule* and Upgrade_Rule parameters, respectively. The syntax is as follows:
[ scheme:// ] [ server [:port]] filepath
Where scheme is one of the following values:
•
tftp
•
http
•
http
If scheme is omitted, tftp is assumed. The server can be a DNS-recognized host name or a numeric IP
address. The port is the destination UDP or TCP port number. The filepath must begin with the root
directory (/). In other words, it must be an absolute path.
If server is missing, then the tftp server specified through DHCP (option 66) is used instead.
If port is missing, then the standard port for the specified scheme is used instead (tftp uses UDP port 69,
http uses TCP port 80, https uses TCP port 443). A filepath must be present. It need not necessarily refer
to a static file, but can indicate dynamic content obtained through CGI.
Macro expansion applies within URLs. The following are examples of valid URLs:
/$MA.cfg
/Linksys/spa021025.bin
192.168.1.130/profiles/init.cfg
Optional Resync Arguments
The URLs entered in Profile_Rule* parameters may be preceded by optional arguments, collectively
enclosed by square brackets. The recognized options are key, post, and alias.
key
The
key
option is used to specify an encryption key. It is required to decrypt profiles which have been
encrypted with an explicit key. The key itself is specified as a (possibly quoted) string following the term
--key
.