HiPath Xpressions Compact V3.0 DLI Administrator Manual

HP3K-DLI Admin Documentation_en.
fm
Central Administration of IP Workpoints via the System
1 Central Administration of IP Workpoints via the

System
From V6.0 in conjunction with HiPath Xpressions Compact, HiPath 3000 supports the central
administration of IP workpoints connected to the system. For this purpose a deployment tool
(DLS Interface DLI) has been implemented on the HiPath Xpressions Compact boards men-
tioned below. In conjunction with the DHCP and FTP server integrated in the DLI, it is possible
to
● centrally configure the parameters of all connected IP workpoints and they can therefore
be initialized in plug-’n-play mode.
● centrally perform software updates on all connected IP workpoints.
A31003-H1060-M100-1-76A9, 2006-10-09
DLI, Administrator Documentation 1-1
HP3K-DLI Admin Documentation_en.fm

DLI Web Based Management
1.1 DLI Web Based Management
1.1.1 Start Screen and Login Page

The login page is accessed by entering the URL https://<IP of Xpressions Compact>/dli/. It will
display a login mask.
Figure 1: Login Page
By entering the username “dli” and password “dli” the user is forwarded to the start page. Oth-
erwise if a user is already logged in or the user enters incorrect account information an appro-
priate error message is displayed.
A31003-H1060-M100-1-76A9, 2006-10-09
1-2 DLI, Administrator Documentation
1.1.2 Navigation
Navigation is done by clicking on the required item on menu bar on the left side. This will display
the corresponding HTML page. If the previous HTML page contains unsaved changes a dialog
box with an appropriate message will be opened with two choices. (“Ok” and “Cancel”). By
pressing “Ok” the changes are lost and the new page will be displayed. Otherwise moving to a
new page is aborted.
Figure 2: Left Menu Bar
A31003-H1060-M100-1-76A9, 2006-10-09

1.1.3 Configuration
1.1.3.1 DHCP Server

This dialog is used to switch the DHCP server on/off, setup or modify the parameters for the
DHCP server. This is required to provide the DLI address in a specific parameter block during
the DHCP request.
Figure 3: DHCP Server
Note:
All the parameters that are already configured by the HiPath Manager E are read only (filled by
default) and cannot be administered here.
a DHCP server is needed to inform the workpoint where the relevant information originates.
The address of the DLI (DLS) server is transferred to the phones in its vendor information.
A31003-H1060-M100-1-76A9, 2006-10-09
On an activated internal DLI server an appropriate warning message will be displayed if the
user deactivates the DHCP server. Also if the address ranges overlap or are not in the same
segment a message is also generated.
Note:
Only one subnet is supported.
Static IP Address Overview

By pressing the button “Administrate Static Addresses” the following screen as shown in the
following figure is opened in the content frame of the browser.
It gives an overview of all currently administrated IP address/MAC ID assignments. It is possible
to delete entries, to add new ones and modify existing ones.
Figure 4: Static IP Address Overview
A31003-H1060-M100-1-76A9, 2006-10-09

Static IP Address Configuration

In the following screen all the parameters for one special IP address mapped to a MAC-ID can
be administered – if an existing record is modified, the attributes IP address and “Client Identi-
fier” will be pre-filled and cannot be changed.
Leaving this page with the button “Apply” will return to the DHCP Static Address overview and
show the new/modified record in the table.
Note that default values are provided for common fields (like in general DHCP section).
Figure 5: Static IP Address Configuration
Note that there will be done some checks to avoid that same IP addresses are used multiple
times or one MAC-Address is assigned to only one IP address.
A31003-H1060-M100-1-76A9, 2006-10-09
1.1.3.2 DLI Server

This dialog is used to enable/disable the DLI (daemon) and shows the necessary information
where the HG1500 gateway can be found.
If the internal DHCP server is deactivated and the user wants to activate the DLI a warning is
displayed.
The address and the port of the external server can be specified to enable to working with a
different DLI (DLS). In this case the use of the internal DLI must be unchecked.
If the internal DHCP is activated, the address and the port settings will be retrieved – otherwise
these parameters must be set in the vendor information of the external DHCP server.
If the internal DLI is switched off, the DLI daemon stops listening for workpoint requests.
Internal DLI Server
Figure 6: DLI Server (internal)
A31003-H1060-M100-1-76A9, 2006-10-09

The Gatekeeper IP address is obtained from the system by DLI. So this field will be read-only
on the WBM.
External DLI Server
Figure 7: DLI Server (external DLS)
If the internal DLI server is not used, DLS address and port settings can be entered:
A31003-H1060-M100-1-76A9, 2006-10-09
1.1.4 Explorer Menu
1.1.4.1 System Clients

This dialog (more an information page) is used to display the information of the connected
workpoints (especially the installed SW version and the deployment status). This HTML page
is refreshed automatically every 30 seconds.
Figure 8: System Clients
Note that all the fields in all columns are read-only.

To get an overview of the registered phones this mask can be used. This may be needed after
an (un-)successful deployment of software or after setting up an external DHCP server, to
check whether and which phones have been registered. The device information might be rele-
vant for setting up own templates. Values of column Deployment Status can be seen in the fol-
lowing table:
A31003-H1060-M100-1-76A9, 2006-10-09

Status Meaning What to do

Pending A deployment is sched- Wait (note that a sched-
uled, that has not yet uled deployment cannot
started. be re-scheduled or can-
celed by the user). The
only way to do so is to
start a deployment once
again giving a different
time – in that case the old
pending deployment job
will be overwritten with
the new one.
Running A deployment has been Wait. No new deployment
initiated by the DLI. jobs are accepted for that
workpoint until there is
some result.
Aborted by system A scheduled deployment A new deployment job
(status Pending) could not can be triggered for the
be started since there workpoint.
was a re-boot (or failure)
of the system.
Aborted no answer A deployment could not Check, whether this work-
be started successfully, point still exists or can be
since the workpoint did reached via WBM.
not respond.
None There was never a de- A new deployment job
ployment done for that can be triggered for the
phone (this is the initial workpoint.
status after first registra-
tion).
OK The last deployment was A new deployment job
successful. can be triggered for the
workpoint.
A31003-H1060-M100-1-76A9, 2006-10-09
Failure message This is delivered from the From the content of error
phone (shows different er- message details of the
ror cases). There can be failure can be seen. Fix
a couple of different spe- the error (e.g. check FTP
cific errors (e.g. FTP serv- settings) and re-try by
er not found, triggering a new deploy-
ment job.
1.1.4.2 Software Image

This dialog is used upload/remove the SW images to the HiPath 3000. Each image can be dis-
tributed manually or setup up to distribute automatically to each corresponding workpoint.
Figure 9: Software Images
The file can be selected via a browser window or directly by entering the path and name in the
field. Then an upload must be initiated. In this phase the image is transferred to HiPath 3000
and analyzed by the “dli”. It reads out out the information like device type, software version etc.
A31003-H1060-M100-1-76A9, 2006-10-09

If the file cannot be analyzed or there is no valid image this will be indicated by the message
“Unknown device type” in table column “Device Type”. The column “Version” will then be empty.
For the 2nd step, there are different scenarios for the distribution of the files to the phone:
● For an immediately distribution to all attached phones of the same type the button “distrib-
ute” is designed for. It causes a re-registration of all these phones and deployment of the
software (regardless whether the current software is newer or older).
● For a scheduled distribution, an exact time must be set to a value in order to postpone the
deployment to this time.
● For an auto deployment the image must be set to the default (for this device). In this case
the software is only distributed after the telephone itself re-registers to the “dli” (which is
done periodically) and if the current phone software version is older than the default one.
● In both cases the status of the deployment (and the current running version) can be veri-
fied.
Normally after an update of the phones, the software is not needed any longer and can be de-
leted from the list (which removes the file on the HiPath 3000).
Deployment of large number of workpoints

When an administrator/service technician starts a manual deployment job related to more than
30 workpoints a warning message will be displayed: “Attention: You are starting a job for more
than 30 phones. This might influence the performance and business of your system. Please
schedule the job. Cancel the job? Yes/ No". Then according to your choice this job will be can-
celed or not.
Since an FTP server only accepts 10 connections simultaneously, DLI will use a mechanism
not to exceed this number. Deployment jobs for more than 5 workpoints will be divided into
groups with 5 workpoints and deployment jobs will be sent to the workpoints group by group.
A31003-H1060-M100-1-76A9, 2006-10-09
1.1.4.3 Active Leases

This dialog only contains information if the DHCP server is activated. It allows the assignment
of workpoints and DHCP provided IP addresses to be displayed.
Figure 10: Active Leases
A31003-H1060-M100-1-76A9, 2006-10-09

1.1.4.4 Template Files

This dialog is used to display, download and upload XML template files for default parameter
configuration of workpoints.
Figure 11: Template Files
Note:
The filename must have a special format in the form <Type of Device><space><HFA>.xml. The
name is also case sensitive. Otherwise it will not be recognized by the “dli” daemon.
If the workpoints should be (pre)configured for use (by setting some standards i.e. key layout)
these templates can be used (each for a specific type of a phones). An initial installation proi-
vides a standard set of templates for various devices.
For modification purposes, each template can be downloaded locally by clicking the file name
link and choosing “Download” in the web browser dialog.
The content of the XML file is always a list of attribute/value pairs. The values can be adapted
according to individual needs. Take care with the format and the value range!
A31003-H1060-M100-1-76A9, 2006-10-09
After modifying the file it can be uploaded back by either browsing or by manually entering the
path and filename. Each workpoint of the same type, which registers afterwards, will be provid-
ed with the new values.
If the files are not needed they can be removed by selecting the desired entries and pressing
“Delete”.
Note:
Updating the templates will not lead to an immediately update of the workpoints. In fact the pa-
rameters are written only if the phone itself re-registers (like auto deployment) on the DLI.
Editing Template Files

In Template Files dialog, when the “Edit” button is pressed, Editing Template Files dialog will be
opened, and in this dialog, a user can edit a set of parameters for selected files. If selected pa-
rameter files have the same value for any parameter, this value will be displayed in the dialog.
If not, the field will be left empty.
According to the selection in the Template Files dialog, the dialog will contain either optiPoint
or optiClient parameters. If both optiPoint and optiClient files types are selected in Template
Files dialog, an error message will be displayed and the Editing Template Files Dialog will not
be opened.
The following figure (new screenshot) is different to the Winword template
A31003-H1060-M100-1-76A9, 2006-10-09

1.1.5 Maintenance
1.1.5.1 Backing up date
Figure 12: Backup and Restore
Data and Files to be backed up

● XML template files (only the changed files have to be backed up)
● hcpd.conf file (and maybe dhcpd.leases – see below).
● DLI relevant database content (logical backup)
● Status of the DLI and the DHCP server (running or not)
Note log files are not saved!
Note phone software images are not saved.
A31003-H1060-M100-1-76A9, 2006-10-09
Backup mechanism
The backup can be triggered by the user with the DLI WBM.
The following steps are to be performed by appropriate DLI scripts:
● Shut down the DLI daemon
● Unload the database content to one file (or a couple of files) – note that the tables storing
the content of SW images are not to be saved
● Tar and compress all the mentioned files to one backup file and store it in a defined place
in the dli directory (naming convention: DLI-Backup.tgz). Note that this file will overwrite a
previous backup file.
● This file will be visible after a short while at the DLI WBM (screen “Backup Restore”) and
can be downloaded from there (or will be automatically presented for download if support-
ed by the browser).
● Restart the DLI daemon
Restore mechanism
The restore can be performed by the user by using the DLI WBM.
The following steps are done:
● The user uploads a saved backup file to the server – this action will automatically start the
restore process.
● The user will get an info message that the restore has been started and is running.
● The DLI daemon is shut down.
● All the files stored in the backup are extracted and overwrite the current files (if there is a
problem this will be reported to the user).
● Load the DLI database content with the extracted logical database backup file(s).
● Re-start the DLI daemon
● Re-start the DHCP server
● Delete the downloaded backup file
A31003-H1060-M100-1-76A9, 2006-10-09

1.1.5.2 Change Password

This dialog is used assign a new password for the WBM user.
Figure 13: Change Password
If the standard password is not secure enough, a new password can be assigned for the user
“dli”. For security reasons the new password must be reentered and is displayed with „*“. Like
other password menus, the old password must also be entered. Changing of the username is
not possible.
A31003-H1060-M100-1-76A9, 2006-10-09
1.1.5.3 Trace Configuration

This dialog sets up the maintenance setting for the DLI daemon. In addition to enabling/dis-
abling the trace, the trace level can also be adjusted.
Figure 14: Trace Configuration
In case of problems during execution of the “dli” daemon, like missing registration of phones or
problems of updating the software, in this screen the user has first to enable the tracing of the
dli component. To control the depth of the output the proper trace level may be set. The trace
levels are additive – that means if “Warning” is set also “Errors” are logged, too. So on the “De-
bug” level the maximum info is traced. It must be considered that the tracing slows down the
machine and should be normally switched off.
A31003-H1060-M100-1-76A9, 2006-10-09

1.1.5.4 Trace Log

This dialog (information) page is used to display the data logged by the DLI daemon.
Figure 15: Trace Log
After enabling the trace, the dli daemon begins immediately to log (add) each event (which is
below or equal the desired level) into a trace file. To allow easier handling of the trace file, which
is stored in the file system of the HiPath 3000 this menu is created. It automatically takes a cur-
rent snapshot and shows the content of the current trace file. Each entry has at least a time
stamp and additional location information. The snapshot can be manually refreshed by press-
ing the appropriate button. You are recommended to clear the trace file before enabling the
trace to limit the lines and allow faster analysis.
A31003-H1060-M100-1-76A9, 2006-10-09
Factory Reset
1.1.6 Help
1.1.6.1 About the WBM

This dialog (information) page is used to display the summarized version (data) of the installed
WBM. It is also used as the start screen after successful login
Figure 16: About (Startup) Screen
In this dialog the version of the currently installed DLI is also displayed.
1.2 Factory Reset

A factory reset of the Xpressions Compact board (also called IVM Reload) is performed by
manually pressing a designated button at the front panel of the board. This is to bring the board
and all of its software back to the delivery point of time, if something is really completely wrong
with the software (emergency case).
A31003-H1060-M100-1-76A9, 2006-10-09

Factory Reset
Note that the factory reset will not load old software (doing a downgrade of the software). It just
refers to the data.
The DLI performs the following steps, during a factory reset:
● Stop the DLI daemon and remove automatic starting scripts for it (plus delete it from pro-
cess supervision).
● Stop the DHCP process and remove automatic starting scripts for it (plus delete it from pro-
cess supervision).
● Remove all entries from database.
● Delete all software images.
● Delete all log files
● Restore all changed XML template files to the delivery version (the delivery version must
be stored somewhere).
● Restore the original DHCP configuration file
A31003-H1060-M100-1-76A9, 2006-10-09

HiPath Xpressions Compact V3.0 DLI Administrator Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

HiPath Xpressions Compact V3.0 DLI Administrator Manual

Загружено:

Авторское право:

Доступные форматы

HP3K-DLI Admin Documentation_en.

1 Central Administration of IP Workpoints via the

Central Administration of IP Workpoints via the System

1.1 DLI Web Based Management

1.1.1 Start Screen and Login Page

Figure 1: Login Page

Figure 2: Left Menu Bar

Central Administration of IP Workpoints via the System

1.1.3.1 DHCP Server

Figure 3: DHCP Server

Static IP Address Overview

Figure 4: Static IP Address Overview

Central Administration of IP Workpoints via the System

Static IP Address Configuration

Figure 5: Static IP Address Configuration

1.1.3.2 DLI Server

Internal DLI Server

Figure 6: DLI Server (internal)

Central Administration of IP Workpoints via the System

External DLI Server

Figure 7: DLI Server (external DLS)

1.1.4 Explorer Menu

1.1.4.1 System Clients

Figure 8: System Clients

Note that all the fields in all columns are read-only.

Central Administration of IP Workpoints via the System

Status Meaning What to do

1.1.4.2 Software Image

Figure 9: Software Images

Central Administration of IP Workpoints via the System

Deployment of large number of workpoints

1.1.4.3 Active Leases

Figure 10: Active Leases

Central Administration of IP Workpoints via the System

1.1.4.4 Template Files

Figure 11: Template Files

Editing Template Files

Central Administration of IP Workpoints via the System

1.1.5.1 Backing up date

Figure 12: Backup and Restore

Data and Files to be backed up

Central Administration of IP Workpoints via the System

1.1.5.2 Change Password

Figure 13: Change Password

1.1.5.3 Trace Configuration

Figure 14: Trace Configuration

Central Administration of IP Workpoints via the System

1.1.5.4 Trace Log

Figure 15: Trace Log

1.1.6.1 About the WBM

Figure 16: About (Startup) Screen

1.2 Factory Reset

Central Administration of IP Workpoints via the System

Вам также может понравиться