User`s manual

H.323 User's Manual 7. Using BootP / DHCP
Version 5.0 255 December 2006
7.3 Using BootP
7.3.1 Upgrading the Mediant 1000
When upgrading the Mediant 1000 (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 184).
Note: To save the cmp file to non-volatile memory, use the -fb command line
switch. 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 C.11.6 on page 390.
7.3.2 Vendor Specific Information Field
The Mediant 1000 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 C-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 (Section 6.5.2 on page 217) or use
the -be command line switch (refer to Table C-1 on page 391).