User guide

ZTC Client ZTC
1-77
iMG/RG Software Reference Manual (System Configuration)
Similarly to the static configuration, ZTCCLIENT ENABLE DYNAMIC LISTENINTERFACE command turns on
the ztcclient module forcing the module to query the server to retrieve the unit configuration file.
Note: ZTC client can be enabled dynamically only if the IP interface where it is bind, it's a dynamic IP interface.
Attempting to enable ZTC client module dynamically on a static IP interface results is an error.
1.5.2.1 Storing unit configuration
The configuration file downloaded from ZTC Server is never stored permanently into the unit flash file system.
This solution prevents memory flash failure when too many write requests are executed.
If the unit restarts, it loses the previous downloaded configuration and starts from the bootstrap configuration.
This behavior allows network administrator to control the unit configuration based only on the configuration
file defined by the ZTC Server framework.
When ZTC Client is enabled, the current running configuration is the result of the bootstrap configuration plus
the unit configuration downloaded from ZTC Server. Any action that save permanently the configuration (e.g.
the system configuration save command) could change the bootstrap configuration file and therefore the result-
ing configuration when ZTC Client runs could be unpredictable.
Note: When ZTC client is enabled, any CLI commands that can cause a change in the system configuration are
inhibited. To enter these types of commands, it’s necessary disable the ZTC client with the ZTCCLIENT
DISABLE command.
1.5.2.2 Pull-at-startup
Figure 1-11 shows the Pull-at-startup phase executed by the ZTC client module when the gateway bootstraps.
Considering a scenario where ZTC Client is bind to a dynamic IP interface, during the bootstrap process, the
gateway uses the facilities provided by the DHCP client module to setup the IP interface configuration.
The dynamic IP interface receives the new network configuration and the ZTC Server address in the ‘bootfile-
name’ DHCP option.
As soon the network is configured, the ZTC Client runs.
The ZTC Client contacts the ZTC Server, passing in the parameters list the Residential Gateway's MAC
address, the application filename and a value derived from the current running configuration (that, at bootstrap,
it is null). This information defines the current device status.
The ZTC Server checks if there is a configuration for the gateway looking for the device MAC address into the
LDAP server, and if necessary, it returns the configuration file to the device.
The device executes the configuration file and starts the ZTC Client timeout. The timeout defines the polling
period before ZTC Server will be contacted.
When the timeout expires the Scheduled-pull phase is executed.