Cisco SPA2102-SF Administration Guide - Page 44

Resync URL, Reboot URL, protocol, server-name, firmware-pathname, spa.bin, resync?

Page 44 highlights

Basic Administration and Configuration Upgrading, Rebooting, and Resyncing Your ATA Device 2 If no protocol is specified, TFTP is assumed. If no server-name is specified, the host that requests the URL is used as server-name. If no port specified, the default port of the protocol is used. (69 for TFTP or 80 for HTTP) The firmware-pathname is typically the file name of the binary located in a directory on the TFTP or HTTP server. If no firmware-pathname is specified, / 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 Resync URL lets you force the ATA device 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://spa-ip-addr/admin/resync?[[protocol://][server-name[:port]]/profilepathname] NOTE The SPA resyncs only when it is idle. If no parameter follows /resync?, the Profile Rule setting from the Provisioning page is used. If no protocol is specified, TFTP is assumed. If no server-name is specified, the host that requests the URL is used as server-name. 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.217admin/resync?tftp://192.168.2.251/spaconf.cfg Reboot URL The Reboot URL lets you reboot the ATA device. The Reboot URL is as follows: http://spa-ip-addr/admin/reboot NOTE The ATA device reboots only when it is idle. Cisco Small Business ATA Administration Guide 44

  • 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
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239

Basic Administration and Configuration
Upgrading, Rebooting, and Resyncing Your ATA Device
Cisco Small Business ATA Administration Guide
44
2
If no
protocol
is specified, TFTP is assumed. If no
server-name
is specified, the
host that requests the URL is used as
server-name
.
If no port specified, the default port of the protocol is used. (69 for TFTP or 80 for
HTTP)
The
firmware-pathname
is typically the file name of the binary located in a
directory on the TFTP or HTTP server. If no
firmware-pathname
is specified,
/
spa.bin
is assumed, as in the following example:
Resync URL
The Resync URL lets you force the ATA device 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://spa-ip-addr/admin/resync?[[protocol://][server-name[:port]]/profile-
pathname]
NOTE
The SPA resyncs only when it is idle.
If no parameter follows
/resync?,
the Profile Rule setting from the Provisioning
page is used.
If no
protocol
is specified, TFTP is assumed. If no
server-name
is specified, the
host that requests the URL is used as
server-name
.
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:
Reboot URL
The Reboot URL lets you reboot the ATA device. The Reboot URL is as follows:
http://spa-ip-addr/admin/reboot
NOTE
The ATA device reboots only when it is idle.