3Com VCX V7122, Руководство пользователя, Страница: 298 / 488

298
V7122 GatewayUser Guide
The following example illustrates how to utilize Automatic Updates for deploying devices with
minimum manual configuration.
To use Automatic Updates for deploying the gateway with minimum manual configuration:
3
Set up a Web server (in the following example it is http://www.corp.com / ) where all
configuration files are to be stored.
4
To each device, pre-configure the following parameter (DHCP / DNS are assumed):
IniFileURL = 'http://www.corp.com/master_configuration.ini'
5
Create a file named master_configuration.ini , with the following text:
# Common configuration for all devices
# ------------------------------------
CptFileURL = 'http://www.corp.com/call_progress.dat'
# Check for updates every 60 minutes
AutoUpdateFrequency = 60
# Additional configuration per device
# -----------------------------------
# Each device loads a file named after its MAC address,
# (for example, config_00908F033512.ini)
IniFileURL = 'http://www.corp.com/config_<MAC>.ini'
# Reset the device after configuration is updated.
# The device resets after all of the files are processed.
ResetNow = 1
You can modify the master_configuration.ini file (or any of the config_<MAC>.ini files) at any
time. The gateway queries for the latest version every 60 minutes and applies the new
settings immediately.
ƒ For additional security, use HTTPS or FTPS. The gateway supports HTTPS (RFC 2818)
and FTPS using the AUTH TLS method <draft-murray-auth-ftp-ssl-16> for the Automatic
Update mechanism.
ƒ To load configuration files from an NFS server, the NFS file system parameters should
be defined in the configuration ini file. The following is an example of an ini file for loading
files from NFS servers using NFS version 2.
# Define NFS servers for Automatic Update
[ NFSServers ]
FORMAT NFSServers_Index = NFSServers_HostOrIP, NFSServers_RootPath,
NFSServers_NfsVersion;
NFSServers 1 = 10.31.2.10, /usr/share, 2 ;
NFSServers 2 = 192.168.100.7, /d/shared, 2 ;
[ \NFSServers ]
CptFileUrl = 'file://10.31.2.10/usr/share/public/usa_tones.dat'
Startup Process
The startup process (illustrated in Figure 88 ) begins when the gateway is reset (physically 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.