Allied Telesis AT-iMG634 - R2 User's Guide Page 108

  • Download
  • Add to my manuals
  • Print
  • Page
    / 998
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 107
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 view 107
1 2 ... 103 104 105 106 107 108 109 110 111 112 113 ... 997 998

Comments to this Manuals

No comments