Provisioning Using Configuration Files
77
Back to Contents
VCS754 Administrator and Provisioning Manual
The Provisioning Process
The automatic provisioning process is as follows:
1.
Check for new or updated configuration files. For file-checking options, see
“Resynchronization: configuration file checking” on page 78
. The VCS754 maintains a
list of the last loaded provisioning files. The VCS754 compares its current configuration
against the files it finds on the provisioning server.
Checking for update…
appears
on the VCS754 screen.
If provisioning has been triggered by the resync timer expiring or by remote
check-sync, the VCS754 checks for updated files after one minute of inactivity.
2.
Download the configuration files.
If any file on the provisioning server has changed, the VCS754 treats it as a new file
and downloads it.
If the provisioning URL specifies a path only with no filename, then by default the
VCS754 looks for and retrieves the following two files:
General file:
<model>.cfg
.
MAC-specific file:
<model>_<MAC Address>.cfg
.
The <model> variable is the VTech product model: VCS754, for example.
If the provisioning URL specifies both a path and filename, then the VCS754 retrieves
only the configuration file specified.
3.
The VCS754 restarts after one minute of inactivity.
During provisioning, the VCS754 reads the configuration file and validates each module
and setting. The VCS754 considers a setting valid if it is:
a valid data type
formatted as a valid setting
within a valid data range
part of a module that passes an integrity check. That is, the module's settings are
consistent and logical. For example, in the "network" module, if DHCP is disabled,
but no static IP address is specified, the module will fail the integrity check and
none of the settings will apply.
Invalid modules or invalid settings are skipped and logged as ERROR messages in the
system log, but will not interrupt the provisioning process. The system log will include the
module parameters that have not been applied. A recognized module with unrecognized
settings will cause all other settings in that module to be skipped.
A successful configuration or firmware update is reported as an INFO message in the
system log.
See
“Configuration File Parameter Guide” on page 84
for the options and value ranges
available for each configuration file setting.
