Siemens HiPath 3000 Series, Service Documentation

Page: 900 / 1302

Workpoint Clients
Nur für den internen Gebrauch
A31003-H3590-S100-7-7620, 06/2012
10-76
HiPath 3000/5000 V9, Service documentation
wclient.fm
Central Administration of IP Workpoints via the System
– optiPoint 410 economy V5.0 and later
– optiPoint 410 economy plus V5.0 and later
– optiPoint 410 standard V5.0 and later
– optiPoint 410 advance V5.0 and later
– optiPoint 420 economy V5.0 and later
– optiPoint 420 economy plus V5.0 and later
– optiPoint 420 standard V5.0 and later
– optiPoint 420 advance V5.0 and later
Refer to the Release Notes and Sales Release for information on the latest software ver-
sions.
10.3.1 Plug&Play Startup of IP Workpoints
Procedure
1. When you connect an IP workpoint, it receives both it’s own IP address as well as that of
the DLI by contacting the DHCP server implemented on the HiPath Xpressions Compact
board.
2. The IP workpoint registers with the Deployment service (DLI) within HiPath Xpressions
Compact.
3. The Deployment Service checks whether it is necessary to configure the default values for
the IP workpoint (for example, if this is the first startup).
Note: For IP workpoint configuration, a template in XML format is defined for each IP work-
point type and stored in the HiPath Xpressions Compact file system. There is exactly one
template per supported IP workpoint type, regardless of the software version.
The first time that an IP workpoint is started, the Deployment Service checks whether there
is a suitable template for this type. If a template exists, the IP workpoint is supported and
the configuration data from the template and the plug&play data (such as, the gatekeeper
address) are supplied to the IP workpoint.
If this is an IP workpoint type for which no template is available, a general template is pro-
vided.
Each additional logon with the Deployment service results in a plug&play-only configura-
tion (supply of gatekeeping address, etc.). In this way, the attributes assigned by template
and changed locally on the IP workpoint are not overwritten by the Deployment service with
each new logon.
4. The Deployment Service sends configuration data from the matching template together
with the plug&play data to the IP workpoint.