User`s manual

SIP User's Manual 7. Using BootP / DHCP
Version 5.0 205 October 2006
7.3 Using BootP
7.3.1 Upgrading the Gateway
When upgrading the gateway (loading new software onto the gateway) using the
BootP/TFTP configuration utility:
 From version 4.4 to version 4.4 or to any higher version, the device retains its
configuration (ini file). However, the auxiliary files (CPT, logo, etc.) may be erased.
 From version 4.6 to version 4.6 or to any higher version, the device retains its
configuration (ini file) and auxiliary files (CPT, logo, etc.).
You can also use the Software Upgrade wizard, available through the Web Interface (refer
to Section
5.8.1 on page 115).
Note: To save the cmp file to non-volatile memory, use the -fb command line switches. If
the file is not saved, the gateway reverts to the old version of software after the next reset.
For information on using command line switches, refer to Section
D.11.6 on page 362.
7.3.2 Vendor Specific Information Field
The gateway uses the vendor specific information field in the BootP request to provide
device-related initial startup information. The BootP/TFTP configuration utility displays this
information in the ‘Client Info’ column (refer to Figure
D-1).
Note: This option is not available on DHCP servers.
The Vendor Specific Information field is disabled by default. To enable / disable this
feature: set the ini file parameter ‘ExtBootPReqEnable’ (Table
6-2 on page 138) or use the
‘-be’ command line switch (refer to Table
D-1 on page 363).
Table
7-1 details the vendor specific information field according to device types:
Table 7-1: Vendor Specific Information Field
Tag #
Description Value Length
220 Gateway Type
#02 = TP-1610
#05 = TP-260
1
221 Current IP Address XXX.XXX.XXX.XXX 4
222 Burned Boot Software Version X.XX 4
223 Burned cmp Software Version XXXXXXXXXXXX 12
224 Geographical Address
0 – 31
(TP-260 Only)
1
225 Chassis Geographical Address
0 – 31
(TP-260 Only)
1
229 E&M N/A 1