Linksys RTP300 User Guide - Page 36

Provisioning Capabilities, Configuration Profile, Upgrade_Enable Yes

Get Linksys RTP300 - Broadband Router With 2 Phone Ports PDF manuals and user guides
UPC - 745883565658
View all Linksys RTP300 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 36 highlights

Basic Administration and Configuration of Your Linksys ATA Provisioning Your Linksys ATA Device Provisioning Capabilities The ATA device provides for secure provisioning and remote upgrade. Provisioning is achieved through configuration profiles transferred to the device via TFTP, HTTP, or HTTPS. To configure Provisioning, go to Provisioning tab in the administration web server. The ATA device 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 ATA device accepts profiles in XML format, or alternatively in a proprietary binary format, which is generated by a profile compiler tool available from Linksys. The ATA device supports up to 256-bit symmetric key encryption of profiles. For the initial transfer of the profile encryption key (initial provisioning stage), the ATA device can receive a profile from an encrypted channel (HTTPS), or it can resync to a binary profile generated by the Linksyssupplied profile compiler. In the latter case, the profile compiler can encrypt the profile specifically for the target ATA device, without requiring an explicit key exchange. Remote firmware upgrade is achieved via TFTP or HTTP (firmware upgrades using HTTPS are not supported). Remote upgrades are controlled by configuring the desired firmware image URL into the ATA device via a remote profile resync. For further information about remote provisioning refer to the Linksys SPA Provisioning Guide. Configuration Profile The ATA configuration profile can be either an XML file or a binary file with a proprietary format. The XML file consists of a series of elements (one per configuration parameter), encapsulated within the element tags ... . The encapsulated elements specify values for individual parameters. Here is an example of a valid XML profile: some secret Yes Binary format profiles contain ATA parameter values and user access permissions for the parameters. By convention, the profile uses the extension .cfg (for example, spa2102.cfg). The Linksys Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs into a properly formatted and encrypted .cfg file. The SPC tool is available from Linksys for the Win32 environment and Linux-i386-elf environment. Requests for SPC tools compiled on other platforms are evaluated on a case-by-case basis. Please contact your Linksys sales representative for further information about obtaining the SPC tool. The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value pairs, with the value in double quotes. Each parameter-value pair is followed by a semicolon. Here is an example of a valid text source profile for input to the SPC tool: Admin_Passwd "some secret"; Upgrade_Enable "Yes"; Refer to the Linksys SPA Provisioning Guide for further details. Linksys ATA Administration Guide 36

  • 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
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
Linksys ATA Administration Guide
36
Provisioning Your Linksys ATA Device
Basic Administration and Configuration of Your Linksys ATA
Provisioning Capabilities
The ATA device provides for secure provisioning and remote upgrade. Provisioning is achieved
through configuration profiles transferred to the device via TFTP, HTTP, or HTTPS. To configure
Provisioning, go to Provisioning tab in the administration web server.
The ATA device 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 ATA device accepts profiles in XML format, or alternatively in a proprietary binary format,
which is generated by a profile compiler tool available from Linksys. The ATA device supports
up to 256-bit symmetric key encryption of profiles. For the initial transfer of the profile
encryption key (initial provisioning stage), the ATA device can receive a profile from an
encrypted channel (HTTPS), or it can resync to a binary profile generated by the Linksys-
supplied profile compiler. In the latter case, the profile compiler can encrypt the profile
specifically for the target ATA device, without requiring an explicit key exchange.
Remote firmware upgrade is achieved via TFTP or HTTP (firmware upgrades using HTTPS are
not supported). Remote upgrades are controlled by configuring the desired firmware image
URL into the ATA device via a remote profile resync.
For further information about remote provisioning refer to the
Linksys SPA Provisioning Guide
.
Configuration Profile
The ATA configuration profile can be either an XML file or a binary file with a proprietary format.
The XML file consists of a series of elements (one per configuration parameter), encapsulated
within the element tags <flat-profile> … </flat-profile>. The encapsulated elements specify
values for individual parameters. Here is an example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
Binary format profiles contain ATA parameter values and user access permissions for the
parameters. By convention, the profile uses the extension .cfg (for example, spa2102.cfg). The
Linksys Profile Compiler (SPC) tool compiles a plain-text file containing parameter-value pairs
into a properly formatted and encrypted .cfg file. The SPC tool is available from Linksys for the
Win32 environment and Linux-i386-elf environment. Requests for SPC tools compiled on other
platforms are evaluated on a case-by-case basis. Please contact your Linksys sales
representative for further information about obtaining the SPC tool.
The syntax of the plain-text file accepted by the profile compiler is a series of parameter-value
pairs, with the value in double quotes. Each parameter-value pair is followed by a semicolon.
Here is an example of a valid text source profile for input to the SPC tool:
Admin_Passwd
“some secret”;
Upgrade_Enable “Yes”;
Refer to the
Linksys SPA Provisioning Guide
for further details.