Startup Process - 3Com VCX v7111 User Manual

NFSServers 2 = 192.168.100.7, /d/shared, 2 ;
[ \NFSServers ]
CptFileUrl = 'file://10.31.2.10/usr/share/public/usa_tones.dat'
VpFileUrl = 'file://192.168.100.7/d/shared/3Com/voiceprompt.dat'

Startup Process

The startup process (illustrated in
or from the Web / SNMP) and ends when the operational software is running. In the startup
process, the network parameters, software and configuration files are obtained.
After the gateway powers up or after it is physically reset, it broadcasts a BootRequest
message to the network. If it receives a reply (from a BootP server), it changes its network
parameters (IP address, subnet mask and default gateway address) to the values provided.
If there is no reply from a BootP server and if DHCP is enabled (DHCPEnable = 1), the
gateway initiates a standard DHCP procedure to configure its network parameters.
After changing the network parameters, the gateway attempts to load the cmp and various
configuration files from the TFTP servers IP address, received from the BootP/DHCP
servers. If a TFTP servers IP address is not received, the gateway attempts to load the
software (cmp) file and / or configuration files from a preconfigured TFTP server (see
Automatic Update Mechanism). Thus, the gateway can obtain its network parameters from
BootP or DHCP servers and its software and configuration files from a different TFTP server
(preconfigured in ini file).
If BootP/DHCP servers are not found or when the gateway is reset from the Web / SNMP, it
retains its network parameters and attempts to load the software (cmp) file and / or
configuration files from a preconfigured TFTP server.
If a preconfigured TFTP server does not exist, the gateway operates using the existing
software and configuration files loaded on its non-volatile memory.
Note that after the operational software runs, if DHCP is configured, the gateway attempts to
renew its lease with the DHCP server.
•
Though DHCP and BootP servers are very similar in operation, the DHCP server
includes some differences that could prevent its operation with BootP clients.
However, many DHCP servers, such as Windows
backward-compatible with BootP protocol and can be used for gateway
configuration.
•
The time duration between BootP/DHCP requests is set to 1 second by default.
This can be changed by the BootPDelay ini file parameter. Also, the number of
requests is 3 by default and can be changed by BootPRetries ini file parameter
(both parameters can also be set using the BootP command line switches).
®
3Com VCX V7111 VoIP Gateway User Guide
Figure 112) begins when the gateway is reset (physically
™
NT DHCP server, are
303