Page 106 / 998 Scroll up to view Page 101 - 105
ZTC
SwUpdate command reference
iMG/RG Software Reference Manual (System Configuration)
1-74
See also
SWUPDATE START
1.4.4.1.11 SWUPDATE STOP TIME
Syntax
SWUPDATE STOP TIME {NONE | MINUTE <minute> HOUR <hour> DAY-OF-MONTH
<day-of-month> MONTH <month> DAY-OF-WEEK <day-of-week> }
Description
This command set the scheduled stop time. See the relative section about the syntax
used for the stop time.
Options
The following table gives the range of values for each option, which can be specified with
this command, and a default value (if applicable).
Example
--> swupdate set stop_time minute 0 hour [21-24] day-of-
month * month * day-of-week *
See also
SWUPDATE SHOW
1.5
ZTC
Wide Area Networks
consist of a lot of components (hubs, switches, routers, residential gateways, set top
boxes, PCs) that need to be configured.
The number of components can be very high and often the configuration of these devices to get them up and
running requires a lot of work for network administrators.
As a result, network administrator operations can be very expensive with in-field configuration taking a lot of
time.
The
Zero Touch Configurator
(ZTC) is a tool designed to enable a network administrator to configure and
manage network devices remotely and automatically without end-user intervention.
The
Zero Touch Configurator
is able to update image software and unit configuration on multiple devices
simultaneously, so administrators can avoid having to connect to each device separately and repeat the same
sequence of actions for each of them.
Option
Description
Default Value
MINUTES
The minute(s) in the hour when swupdate must stop.
N/A
HOUR
The hour(s) in the day when swupdate must stop.
N/A
DAY
-
OF
-
MONTH
The day(s) in the month when swupdate must stop.
N/A
MONTH
The month(s) in the year when swupdate must stop.
N/A
DAY
-
OF
-
WEEK
The day(s) in the week when swupdate must stop.
N/A
Page 107 / 998
Functional blocks
ZTC
1-75
iMG/RG Software Reference Manual (System Configuration)
1.5.1
Functional blocks
The ZTC is a component-based application, which consists of different logical blocks that can be distributed on
independent runtime environments or machines (see
Figure 1-10
).
FIGURE 1-10
ZTC network architecture
1.5.1.1 ZTC network architecture
The ZTC Network Architecture consists of the following parts:
An
LDAP Directory Serv
ice in which data is stored.
The
ZTC Server
, that contains all the application logic for:
User authentication and authorization
Data consistency and syntax checking when requesting to add a new device configuration
Application logic for creating new configuration scripts
Application logic to execute commands on the device
Data Access Object layer to access the data tier
Several protocols for supporting different kind of clients
The
ZTC WEB Interface
. This application lest users interact with the ZTC Server. Through this interface they
can view or update existing configurations, or add new ones.
ZTC Server
WEB Interface
WEB Browser
Residential
Gateway
LDAP Database
TFTP
Server
TFTP
HTTP
RMI
LDAP
Page 108 / 998
ZTC
ZTC Client
iMG/RG Software Reference Manual (System Configuration)
1-76
The
ZTC Embedded Client
. This client is installed on the devices to communicate with the ZTC Server. Typ-
ically, the devices connect to ZTC Server to perform the following operations:
Communicate their actual configuration to ZTC Server
Download, if existing, new configurations from ZTC Server
The components of ZTC are independent, and they can run on different machines and platforms, in a three-
tiered architecture fashion.
The core of the application is the ZTC Server. It manages the dialogue with the directory service backend and
performs all operations on data. The ZTC WEB Interface, used to interact with the ZTC Server, is decoupled
from the ZTC server, and can run on different machines.
1.5.2
ZTC Client
The ZTC Embedded Client, or, shortly, the ZTC Client, is the module running on the gateway in charge to
communicate with the ZTC server.
ZTC client works accordingly to the so-called
Configuration PULL
method. ZTC Client is in charge to con-
tact the ZTC server passing the current configuration, the unit identifier and retrieves the new configuration if
necessary. ZTC server has the responsibility to allow the download only of the correct configuration file
depending on the unit identifier (the unit MAC address) and on the configuration rules defined inside the ZTC
Server.
The following three ZTC Clients – ZTC Server communication phases are possible:
Pull-at-startup
– This phase is executed when the unit startup
Scheduled-pull
- This phase is executed every time the
ztcclient
polling timeout expires
ZTC Client and ZTC Server communicate through TFTP protocol.
The ZTC Server IP address can be configured in the ZTC Client module in two ways: either
statically
or
dynam-
ically
.
When a
static configuration
is used, the ZTC Server IPv4 address is defined explicitly using the
ZTCCLIENT
ENABLE
STATIC
ZTCSERVERADDR
command. This command set the server IP address that will be used by all the
next queries and also turns on the
ztcclient
module forcing the module to query the server to retrieve the unit
configuration file.
When a
dynamic configuration
is used, the ZTC client module is bind to an existing IP interface using the
ZTCCLIENT ENABLE DYNAMIC LISTENINTERFACE command.
In this way the ZTC client module uses the facilities offered by the
dhcpclient
module to force the IP interface to
ask to an external DHCP server the ZTC Server address. When the ZTC Client needs to know the ZTC
Server address, a DHCP request is generated by the IP interface requesting a value for option 67 ‘bootfile-
name’. The ZTC Client module as ZTC Server IP address uses the value returned by the DHCP server for
option 67.
Page 109 / 998
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.
Page 110 / 998
ZTC
ZTC Client
iMG/RG Software Reference Manual (System Configuration)
1-78
FIGURE 1-11
Pull-at-Startup
ZTC phase
1.5.2.3 Scheduled-pull
Figure 1-11
shows the
Scheduled-pull
phase executed by the ZTC client module when the ztcclient polling
timeout expires.
Residential Gateway
LDAP Database
ZTC Server
DHCP Server
Unit
Bootstrap
NULL
ZTC Idle
Setup Dyn
Interface
Start ZTC
Timeout
Run New
Configuration
Start
ZTC Client

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top