HP ProCurve Services zl Module

Aastra MX-ONE Installation and

Getting Started Guide

ASE/MXO/SW/0021





www.procurve.com Version 1.3
www.aastra.com 29.03.2011
2

Copyright 2009 Hewlett-Packard Development Company, L.P.
Copyright 2009 Aastra
Software Credits and Notices
SSL on HP ProCurve Switches is based on the OpenSSL software toolkit. This product
includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.
For more information on OpenSSL, visit www.openssl.org.
Open Source Software Acknowledgement
This software incorporates open source components that are governed by the GNU
General Public License (GPL). In accordance with this license, HP ProCurve
Networking will make available a complete, machine readable copy of the source code
components covered by the GNU GPL upon receipt of a written request. Send a request
to:
Aastra Telecom Sweden AB
LM Ericssonvg 30
S-12736 Hgersten
Sweden

Hewlett-Packard Company, L.P.
ProCurve Services zl Module
GNU GPL Source Code
Attn: ProCurve Networking Support
MS: 5551
Roseville, CA 95747 USA
Disclaimer
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH
REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty
statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or
editorial errors or omissions contained herein.
Hewlett-Packard assumes no responsibility for the use or reliability of its software on
equipment that is not furnished by Hewlett-Packard.
3
Table of Contents
Overview ..................................................................................................................................................... 4
Step-by-step instructions ...................................................................................................................... 4
1. Install the Services zl Module hardware ................................................................................ 4
2. Download the software image onto the Services zl Module ............................................. 5
3. Install the software image on the Services zl Module ........................................................ 8
4. Activate the Aastra MX-ONE product software image ................................................... 8
5. Configure the Services zl Module ports into a specific VLAN ....................................... 10
6. Access the Aastra MX-ONE CLI ......................................................................................... 12
7. Configure Aastra MX-ONE using the CLI ......................................................................... 12
7.1. Aastra MX-ONE installation ............................................................................................. 12
7.2. Network configuration .......................................................................................................... 13
7.3. MX-ONE application configuration and installation ..................................................... 14
8. Access the Aastra MX-ONE Web interface ...................................................................... 26
9. Rebooting the Services zl Module ......................................................................................... 27
10. Technical Support .................................................................................................................. 28
4
Overview
The HP ProCurve Services zl Module is shipped from the factory ready for the Aastra
MX-ONE software image to be downloaded and installed. It does not have any
specific application software or an application-related operating system already
installed. Instead, a resident Service OS provides the ability to download, install and
activate a complete operating system image that includes the Aastra MX-ONE
application.
After the Aastra MX-ONE image is downloaded, installed and activated on the
Services zl Module, it becomes joined to that one particular module. Since Services zl
Module is not shipped with any specific network function or service until a Product OS
image is added, it provides a unique ability to become a dedicated appliance within a
switch after the Aastra MX-ONE image is installed and activated.
This document describes the steps needed to install and activate Aastra MX-ONE on
the Services zl Module. Because the Services zl Module is not a server device, it is
necessary to follow the steps described in this document to successfully complete the
installation.
Before proceeding, register for account at http://my.procurve.com. This account provide
access to product support information, updates, and license keys.
Step-by-step instructions
1. Install the Services zl Module hardware
Before installing the Services zl Module into the switch chassis, access the switch CLI
to verify the switch has the most current module-compatible software installed. The
switch software version should be K.13.51 or later. Use the following command to check
the switch software version:
Pr oCur ve# show version <CR>

I mage st amp: . . .
<dat e, t i me>
K. 13. XX
. . .
Boot I mage: Pr i mar y
If the switch software needs to be updated, follow the directions in the HP ProCurve
Services zl Module Installation and Getting Started Guide to update the software.
Next, install the Services zl Module following directions and safety precautions in the HP
ProCurve Services zl Module Installation and Getting Started Guide.
5
Verify the module is installed successfully. When the module is installed, it undergoes a
self test that takes a few seconds. The LEDs on the front panel of the module help
determine if the module has passed the self test. For more information, see the HP
ProCurve Services zl Module Installation and Getting Started Guide.
2. Download the software image onto the Services zl Module
Contact Aastra for software licensing options and instructions on how to acquire access
to the Aastra MX-ONE product software image.
Once the Aastra MX-ONE product software image is received, it can be downloaded
onto the Services zl Module using either a USB flash drive or using FTP file transfer
through the local network.
How to start the module
When the Services Module is shipped, it includes the ProCurve Service OS. By default,
the system will boot directly into the Service OS and the user can download and install a
Product onto the module.
When you are using a CLI, the prompt command line identifies the blades slot number
in the chassis and the current Service OS.
Pr oCur ve( ser vi ces- modul e- B: HD) # Ser vi ce OS ( on t he Har d Di sk)
Pr oCur ve( ser vi ces- modul e- B: CF) # Ser vi ce OS ( on t he Compact Fl ash)
Pr oCur ve( ser vi ces- modul e- B: PR) # Ser vi ce OS agent ( on t he Pr oduct par t i t i on)
If a Product is already installed, the module will boot to the Product software. Before
starting the installation of a new product, you should boot the module on the ProCurve
Service OS. Use the command boot service on the Product Service OS.
Pr oCur ve Swi t ch 5406zl ( ser vi ces- modul e- B: PR) # boot ser vi ce <CR>
Changi ng boot f r omPr oduct OS t o Ser vi ce OS.
Syst emwi l l be r eboot ed. Do you want t o cont i nue [ y/ n] ? y
Reboot i ng
Pr oCur ve Swi t ch 5406zl # ser vi ce b 1 <CR>
Pr oCur ve Swi t ch 5406zl ( ser vi ces- modul e- B: HD) #
Download Using USB Flash Drive
Copy the image onto a USB flash drive. Make sure the drive is FAT/FAT32 formatted
and can hold all files that will be downloaded. If the software image is provided in the
form of a zip file, first unzip the image directory and copy all files to the following
location on the USB drive:
/ i mages/ MX- ONE_J 9464A_XXXXXX_XXXX/
6
Type "services" to list the services installed on the Services zl Module:
Pr oCur ve> services <CR>

I nst al l ed Ser vi ces
Sl ot I ndex Descr i pt i on Name
B 1. Services Module services-module
The Services zl Module service is in Slot B at index 1 and has the name services-
module. Type either of the following commands to access the Services zl Module CLI:
Pr oCur ve# service b 1 <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) #
or
Pr oCur ve# service b name services-module <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) #
Insert the USB flash drive with the Aastra MX-ONE image into the USB slot on the
front of the Services zl Module.
IMPORTANT: The USB flash drive must be inserted into the USB slot on the front of the
Services zl Module, NOT into the USB slot on the switch chassis.
Type the following commands to copy the image to the image repository on the
Services zl Module:
Pr oCur ve( ser vi ces- modul e- B: HD) # usb mount <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) # usb copyfrom MX-ONE_J9464A_XXXXXX_XXXX <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) # usb unmount <CR>
Download Using FTP File Transfer
First of all, you must configure the Ethernet interface. If your network does not use a
dynamic IP addressing system such as DHCP, you need to set a permanent IP address
manually. Use the ip command from the Service OS. If you need to configure a VLAN,
see chapter 5.
Pr oCur ve Swi t ch 5406zl ( ser vi ces- modul e- B: HD) # i p hel p
Usage: [ no] i p [ dhcp| I P- ADDR/ MASK- LENGTH]

Descr i pt i on: Set I P par amet er s f or communi cat i on wi t hi n an I P net wor k
by conf i gur i ng a st at i c I P addr ess or at t empt i ng t o get a
dynami cal l y- assi gned I P addr ess conf i gur at i on. Usi ng t he ' no'
f or mof t hi s command wi l l r emove any assi gned I P addr ess.
7
For this example we will use a static IP address.
Pr oCur ve Swi t ch 5406zl ( ser vi ces- modul e- B: HD) # i p addr ess 10. 1. 1. 20/ 24
Pr oCur ve Swi t ch 5406zl ( ser vi ces- modul e- B: HD) # i p def aul t - gat eway 10. 1. 1. 1
If the software image is provided in the form of a zip file, first unzip the image directory
and copy it (as a sub-directory) to the root directory of an FTP server:
/ FTP- r oot / MX- ONE_J 9464A_XXXXXX_XXXX/
Type "services" to list the services installed on the Services zl Module:
Pr oCur ve> services <CR>

I nst al l ed Ser vi ces
Sl ot I ndex Descr i pt i on Name
B 1. Services Module services-module
The Services zl Module service is in Slot B at index 1 and has the name services-
module. Type either of the following commands to access the Services zl Module CLI:
Pr oCur ve# service b 1 <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) #
or
Pr oCur ve# service b name services-module <CR>
Pr oCur ve( ser vi ces- modul e- B: HD) #
Next, type the following command to initiate FTP file transfer:
Pr oCur ve( ser vi ces- modul e- B: HD) # download ftp <IP-ADDRESS>
MX-ONE_J9464A_XXXXXX_XXXX user <USERNAME> <CR>
<IP-ADDRESS>is the IP address of the FTP server to which the product image
directory was copied, and <USERNAME>is the optional login ID for the FTP server
(enter this login ID only if its required for FTP server login).

8
3. Install the software image on the Services zl Module
The install command is used for installation. Before a new product can be installed,
the existing product must be removed by using the uninstall command.
After the Aastra MX-ONE software image is downloaded into the Services zl Module
image repository (using either USB file copy or FTP transfer), type the following
commands to install the image:
Pr oCur ve# services b 1 <CR>

Pr oCur ve( ser vi ces- modul e- B: HD) # uninstall product <CR>

Pr oCur ve( ser vi ces- modul e- B: HD) # install product MX-ONE_J9464A_XXXXXX_XXXX
<CR>
At this point the software image is installed and ready to be activated.
4. Acti vate the Aastra MX-ONE product software image
After the software image is installed onto the Services zl Module, it must be registered
and activated before being run for the first time. To do this, first obtain a hardware ID for
the Services zl Module by entering the following commands:
Pr oCur ve# services b 1 <CR>

Pr oCur ve( ser vi ces- modul e- B: HD) # licenses hardware-id activation <CR>
The har dwar e I d f or package " act i vat i on" i s
SG000GG000- A- 0123456- ABCDEFG- 0123456- ABCDEFG

Note: SG000GG000 is the serial number of the Services zl Module.
Detailed instructions to find your activation hardware ID are embedded in the My
ProCurve portal (https://my.procurve.com) registration pages and are also available in
the HP ProCurve Services zl Module Installation and Getting Started Guide.
Use this activation hardware ID to register the Services zl Module through the My
ProCurve portal. Sign in to the portal and then click on My Software and follow the
instructions to complete the registration process. You will be asked to enter the
activation hardware ID as well as the registration ID that was provided along with the
Aastra MX-ONE product software image.
Once the registration process has completed successfully, you should receive a license
key in email and on the screen. This license key must be installed on the Services zl
9
Module. For instructions on how to install the license key, see the HP ProCurve
Services zl Module Installation and Getting Started Guide.
The following commands install the license key on the Services zl Module:
Pr oCur ve# services b 1 <CR>

Pr oCur ve( ser vi ces- modul e- B: HD) # licenses install activation SG0000GG000-A-
0123456-ABCDEFG-0123456-ABCDEFG <CR>

Pr oCur ve( ser vi ces- modul e- B: HD) # boot product <CR>
Changi ng boot f r omSer vi ce OS t o Pr oduct OS.
Syst emwi l l be r eboot ed. Do you want t o cont i nue [ y/ n] ? y
Reboot i ng
Check the boot progress on the Services zl Module until the Product OS is running (you
can use the repeat command to monitor booting progress):
Pr oCur ve# show services b <CR>

St at us and Count er s - Ser vi ces Modul e A St at us

HP Ser vi ces zl Modul e J 9154A

Ver si ons : A. 01. 06, B. 01. 03
St at us : not r espondi ng

For mor e i nf or mat i on, use t he show commands i n ser vi ces cont ext

Pr oCur ve# repeat <CR>

Press any key to exit the repeat command once the Status display shows the module
is running.
IMPORTANT: The USB flash drive must be removed from the USB slot on the front of
the Services zl Module before the module is rebooted. If it is not, the module may
appear to hang instead of rebooting. To recover, simply remove the USB flash drive,
disengage the module from the switch chassis for 5 seconds, then reinsert the module
to restart the boot process.
After the Services zl Module reboots, the Aastra MX-ONE command line interface
(CLI) becomes available.

10
5. Configure the Services zl Module ports into a specific
VLAN
The Services zl Module provides two internal Ethernet port connections into the switch
after installation. By default, both ports are placed in the default VLAN. For example, if
the Services zl Module is installed into slot B of the switch chassis, the internal ports
appear as B1 and B2, and are automatically placed in the default VLAN. Depending on
the VLAN configuration in the switch, one or both of these ports may need to be
reassigned into a different VLAN. This is done by using the switch's management
interface, just like any other port on the switch. The VLAN that the internal ports are
placed in is important when configuring network parameters (e.g. IP address) for the
services on the zl Module. These network parameters need to match the network
configuration of the VLAN they are members of.
11
The VLAN configuration in the switch can be seen using:
Pr oCur ve# show vl ans <CR>

St at us and Count er s VLAN I nf or mat i on

Maxi mumVLANs t o suppor t : 256
Pr i mar y VLAN : DEFAULT_VLAN
Management VLAN :

VLAN I D Name | St at us Voi ce J umbo
- - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - -
1 DEFAULT_VLAN | Por t - based No No
123 VLAN_123 | Por t - based No No
For this example, the ports assigned to the default VLAN can be seen using:
Pr oCur ve# show vl an 1 <CR>

St at us and Count er s VLAN I nf or mat i on VLAN 1

VLAN I D : 1
Name : DEFAULT_VLAN
St at us: Por t - based
Voi ce : No
J umbo : No

Por t I nf or mat i on Mode Unknown VLAN St at us
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
B1 Unt agged Lear n Up
B2 Unt agged Lear n Up
In this example, if all other switch ports are assigned to VLAN 123, the two Services zl
Module ports will also need to be assigned to VLAN 123 in order to be accessible.
These ports can be assigned as tagged using:
Pr oCur ve# conf i gur e <CR>
Pr oCur ve( conf i g) # vl an 123 <CR>
Pr oCur ve( vl an- 123) # t agged B1, B2 <CR>
or else as untagged using:
Pr oCur ve# conf i gur e <CR>
Pr oCur ve( conf i g) # vl an 123 <CR>
Pr oCur ve( vl an- 123) # unt agged B1, B2 <CR>
See the Management and Configuration Guide for the ProCurve Series 3500yl,
6200yl, 5400zl, and 8200zl Switches for more information on VLAN configuration.
12
6. Access the Aastra MX-ONE CLI
Type "services" in the switch CLI to list the services installed on the Services zl Module:
Pr oCur ve Swi t ch 5406zl ( conf i g) # show ser vi ces
I nst al l ed Ser vi ces
Sl ot I ndex Descr i pt i on Name
D 1. Ser vi ces zl Modul e ser vi ces- modul e
D 2. Aast r a MX- ONE appl i cat i on. mxone

The Aastra MX-ONE service is now activated in Slot D at index 2 and has the name
mxone. Type either of the following commands to access the Aastra MX-ONE CLI:
Pr oCur ve Swi t ch 5406zl # ser vi ces d 2 <CR>
Pr oCur ve Swi t ch 5406zl ( mxone- D) #
Or
Pr oCur ve Swi t ch 5406zl # ser vi ces d name mxone <CR>
Pr oCur ve Swi t ch 5406zl ( mxone- D) #
7. Configure Aastra MX-ONE using the CLI
Enter the Aastra MX-ONE CLI. The available commands are listed if you type the ? or
TAB character. As you type a command you can press ? or TAB at any time to see
matching commands or arguments:
Pr oCur ve Swi t ch 5406zl # ser vi ces d 2 <CR>
Pr oCur ve Swi t ch 5406zl ( mxone- D) # ?
i nst al l Aast r a MX- ONE I nst al l at i on.
conf i gur e Aast r a MX- ONE Conf i gur e basi c net wor k par amet er s.
st ar t up Aast r a MX- ONE Conf i gur e and st ar t MX- ONE appl i cat i on.
ser vi ce Ot her ser vi ces admi ni st r at i on.
r eboot Reboot zl Modul e.
show Show modul e oper at i onal i nf or mat i on.
l og Vi ew l og f i l es.
exi t Ret ur n t o t he swi t ch command cont ext .
When entering a command, there may be a delay of a few seconds as the command is
processed - this is normal behavior. Wait for the command prompt before trying to enter
further commands.
Using the Aastra MX-ONE CLI, you should install the application, configure network
settings, and configure remote access to your Linux desktop. You could also start and
stop some Linux services.
7.1. Aastra MX-ONE installation
13
The install command allows you to overwrite the default installation in English. This
installation will erase your configuration.
Pr oCur ve Swi t ch 5406zl ( mxone- D) # i nst al l
I nst al l of MX- ONE st ar t s
Unpacki ng f i l es f or HP Pr ocur ve One Ser vi ce modul e . . .
Thi s mi ght t ake some t i me, pl ease wai t . . .
Tur nkey i nst al l at i on compl et e.
You need t o r un conf i gur e and st ar t up bef or e you can use t he appl i cat i on.

Pr oCur ve Swi t ch 5406zl ( mxone- D) #
7.2. Network configuration
You could verify your configuration using the show command. The show ip command
displays the current state for all interfaces.
Pr oCur ve Swi t ch 5406zl ( mxone- D) # conf i gur e

Net wor k conf i gur at i on



14

You must reboot the server before continuing with MX-ONE application installation.
Pr oCur ve Swi t ch 5406zl ( mxone- D) # r eboot

7.3. MX-ONE application configuration and installation
Before configuring the network and the system, some data must be collected. This data
is used for basic network configuration
Fill in the requirements information in the tabled below
Type of Information Value
Market (country)
Default is Standard

Use inter-LIM Security? (Yes/No) The
recommended limit for inter-LIM
encryption is 10 LIMs.

Manager Telephony System User
Manager Telephony System
Password

System Confirm Password This
password must be the same as the

15
one entered in Manager Telephony
System Password
Use HTTPS? (Yes/No)
Note: Certificate, Security File, and
Password can only be entered if
HTTPS is used.

Web Server Port If HTTPS is used:
This port will be used by any browser
to securely communicate with the
Manager Telephony System. If HTTP
is used: This port will be used by any
browser to communicate with the
Manager Telephony System.

Onl y if HTTPS is
used
Certificate Type Self-signed: A self-
signed certificate is generated during
the installation. Import: a digital
certificate can be obtained from a
commercial supplier and saved on a
USB memory stick or on a floppy
disk, see Chapter 3.3 Obtaining a
Digital Certificate for the Manager
Telephony System on page 10.

The name of and path to the digital
certificate file. When using a
certificate of PKCS12 format, the file
extension must be .pfx or .p12. Other
file types are treated as J AVA
keystore files.

Password Only valid when Import is
selected for the Certificate

Email Address Only valid when self
signed is selected in Certificate. An
email address is required for
generating the certificate

DiffServ Code Point for Media The
Diffserv code point for media is used
to divide the voice part of the IP traffic
into classes. Different classes have
different priorities. The traffic with the
highest priority will be sent first.
Default is Expedited forwarding
(traffic class 101, drop precedence
110) giving DSCP 101110.
Refer to the
description on
DiffServ found, for
example, in the
description for
CONFIGURATION
FILE FOR DBC 42X,
in the chapter Diffserv
settings. See RFC:
2598
DiffServ Code Point for Call Control
The DiffServ code point for call
Refer to the
description on
16
control is used to divide the
connection part of the IP traffic into
classes. The different classes have
different priorities. The traffic with the
highest priority will be sent first.
Default is traffic class 100 and drop
precedence 110 giving DSCP
100110.
DiffServ found, for
example, in the
description for
CONFIGURATION
FILE FOR DBC 42X,
in the chapter Diffserv
settings. See RFC:
2598
NTP Server (Network Time Protocol
Server) If there is no External Time
Server specified, the system relies on
the Local Clock server of LIM1.

Note: It is recommended that the eth0 IP address, which is configured for the default
gateway during the turnkey installation basic. network setup, should be specified as the
first network interface in the system_conf.xml file.
Note: It is recommended to print a separate copy of Table 2 Data for basic network
configuration and LIM configuration on page 15 for each LIM in the system and fill in the
values for easy access to the information during the configuration. Data for the media
gateways is needed after the system configuration.
Type of Information Value
LIM number
Server host name
A unique host name

Use redundant network? (Yes/No)
Default is No.

Media Gateway type Default is EMG-1.
Server type Default is Standard.
Server network interface -
1 (eth0)
IP address
Subnet mask
Default gateway
Server network interface -
2
IP address
Subnet mask
Default gateway (Applicable only in
Redundant Networks)

Media Gateway control
interface
IP address
Network configuration for the complete system is performed from Telephony Server
number 1.
In the Linux system you login as eri_sn_admin and execute the binary installation file.
17
The software will then be unpacked. After installing the software a web server is started.
Now the dialog session to Server 1 is suspended. From a remote web client you run ICT
to generate the configuration data. When this is done you go back to the suspended
dialog and continue the configuration. Now the installed software is distributed to the
whole system.
1. If it is not already on, switch on the Telephony Server and wait while it is starting.
2. If not already done, connect a console (keyboard and monitor) to Telephony
Server number 1.
Note: For example, use a remote SSH application, like puTTY.
From switch console:
Pr oCur ve Swi t ch 5406zl ( mxone- D) # st ar t up

3. The MX-ONE Telephony System Setup dialog is started
4. Then a web server is started on Server 1.
.
5. When the web server is ready it can be accessed remotely from a web client (on
Windows or Linux).

6. The shown URL address is the location of the ICT web application on Server 1
(above in the picture, the address is just an example). Enter the URL address in
a web browser (client). Let the above terminal window be untouched until the ICT
configuration is complete.
18

7. Use the ICT. Enter data in the tabs that are used. The required data on the
General page must be entered before you can move to the Server tab. These
two tabs must always be filled in. Use the data collected in the tables earlier in
this document.
The Cluster tab is just needed when clusters are used The Import/Export tab is
used if you want to import (upload) a configuration file (to the /etc directory) for
modification or if you want to save (download) the generated configuration files
(from /etc) elsewhere.
First enter data in the General tab.
19

When the data in the general tab has been entered select the Server tab. There
select Add.
20

Enter network data for one server at a time.

21
Enter the data for the current server and click Apply.
Checks are done relative the already entered data. If OK then a summary page is
presented.

Clicking Done will bring you back to the Server tab where you can enter data for
the next server.

Now, when you click Apply the configuration files will be generated and a result
page is presented.
22

Clicking Done, on the bottom of the page, will take you back to the General tab,
but now it is time to stop, because the configuration files have been created. You
can check that by opening a new (puTTY) terminal window to Server 1. There
you can verify that the two files /etc/eri_ts.conf and /etc/system_conf.xml have
been created.
8. If you would like to save the generated files, select the Import/Export tab and
select download.

23
9. Now go back to the suspended dialog session on Server 1. See step 7. Press
Enter.
Get t i ng LI M dat a. . .
Do you want t o val i dat e t he syst em_conf . xml , Y/ N: n
Set t i ng up ssh communi cat i on. . .
Val i d keys exi st s on t he Host
Copyi ng scr i pt f i l es. . .
Ver i f y t he user ' s gr oup. . . . . .
10. 105. 64. 19
Checki ng Memor y si ze i n syst em
10. 105. 64. 19 4136244 Kb RAM
Checki ng and St oppi ng novel l - zmd. . .
10. 105. 64. 19Conf i gur i ng of NTP Ser ver . . .
10. 105. 64. 19
Checki ng set t i ng of cl ock sour ce on ESU. . .
Checki ng t he st at us of sysl og. . .
10. 105. 64. 19
l ogr ot at e / var / l og/ l ocal messages. . .
10. 105. 64. 19
Change di r ect or y per mi sson on var / t mp/ . . .
10. 105. 64. 19
Cr eat i ng i nst al l _t mp_f i l es di r ect or y. . .
Di sabl i ng UseDNS i n sshd conf i g. . .
10. 105. 64. 19
St ar t i ng SSH Communi cat i on i n al l t he LI Ms
Tur ni ng of f nscd ( Name Ser ver Cache Daemon) . . .
10. 105. 64. 19
Checki ng I P por t s. . .
10. 105. 64. 19
I P Addr ess
Host name
/ et c/ host s
Checki ng / et c/ sysconf i g/ named. . .
10. 105. 64. 19
10. 105. 64. 19
Act i vat i ng l ocal dns. . .
10. 105. 64. 19
cat : / var / t mp/ t mpf i l e: No such f i l e or di r ect or y
St ar t of named daemon OK
Checki ng Dns Names. . .
I nst al l i ng hear t beat on 10. 105. 64. 19. . .
done
Checki ng hear t beat . . .
10. 105. 64. 19
Secur i ng sct p modul e. . .
Modi f yi ng ker nel par amet er s. . .
Set t i ng Ser ver Speed. . .
10. 105. 64. 19
Checki ng Boot conf i gur at i on. . .
10. 105. 64. 19
St oppi ng l dap ser ver . . .
10. 105. 64. 19
St oppi ng Ser vi ce Nodes. . .
10. 105. 64. 19
LI M : 10. 105. 64. 19 i s pr oper l y t er mi nat ed.
24
RPMs not i ncl uded i n t he t el ephony syst em
Copyi ng RPMs on t he LI M( s)
Copyi ng RPM f i l es. . .
I nst al l i ng RPMs. . .
I n pl ace: 10. 105. 64. 19: Xer ces- c- 2. 6. 0- 5
Checki ng xi net d. . .
10. 105. 64. 19
RPMs compr i si ng t he t el ephony syst em
Copyi ng RPMs on t he LI M( s)
Copyi ng RPM f i l es. . .
St oppi ng Aast r a OM Daemon. . .
I nst al l i ng RPMs. . .
I n pl ace: 10. 105. 64. 19: er i _sn- 13. 64- MR
I n pl ace: 10. 105. 64. 19: er i _om- 9. 56- 1
I n pl ace: 10. 105. 64. 19: egx_r f s- 2. 0- 1
I n pl ace: 10. 105. 64. 19: egx_sw- 10. 18- 1
I n pl ace: 10. 105. 64. 19: l sue_sw- 1. 4_5- 1
Checki ng SSH communi cat i on bet ween LI Ms
St oppi ng nf s ser ver . . .
10. 105. 64. 19
Di sabl i ng t f t p. . .
10. 105. 64. 19
Checki ng f i l es. . .
xml document can be used f or i nst al l at i on
Get t i ng LI M dat a. . .
Pr epar e f or l dap i nst al l at i on. . .
Pr epar e f or l dap i nst al l at i on. . .
Val i dat i ng Conf i gur at i on f i l es. . .
Copyi ng f i l es. . .
10. 105. 64. 19
Repl aci ng wi t h MX- ONE 4. 0 t r i al l i censes
I ni t i at i ng l dap. . .
Run l dap scr i pt on 10. 105. 64. 19
St ar t i ng LDAP on 10. 105. 64. 19
St ar t i ng l dap ser ver . . .
10. 105. 64. 19
Checki ng l dap st at us on al l LI Ms. . .
Checki ng f or LDAP st at us
I nser t i ng Conf i gur at i on dat a i nt o LDAP. . .
I nser t i ng Al ar mConf i gur at i on i nt o LDAP. . .
Synchr oni zi ng f i l e syst em. . .
Checki ng f or LDAP r epl i cat i on. Thi s may go on f or sever al mi nut es. . . . . . . . . . .
Removi ng ol d dat a. . .
10. 105. 64. 19
Synchr oni zi ng f i l e syst em. . .
Checki ng f or LDAP r epl i cat i on. Thi s may go on f or sever al mi nut es. . . . . . . . . . .
Backi ng up r out es f i l e. . .
10. 105. 64. 19
Set t i ng up r out es. . .
10. 105. 64. 19
Set t i ng up super vi si on of def aul t gat eways. . .
10. 105. 64. 19
Cannot st ar t super vi si on of def aul t gat eways on 10. 105. 64. 19
St ar t i ng Ser vi ce Nodes. . .
10. 105. 64. 19
Checki ng LI Ms. . . ( Pl ease Wai t . . . I t may t ake f ew mi nut es)
25
Wai t i ng f or LI Ms i n 1 mi nut es of max 30 mi nut es.
Wai t i ng f or LI Ms i n 2 mi nut es of max 30 mi nut es.
LI M 1 i s r unni ng.
Addi ng cer t _check t o / et c/ cr on. dai l y/ di r ect or y
10. 105. 64. 19
Backi ng up dat a. . .
I CT appl i cat i on ser ver i s shut down now.
Act i vat i ng Daemons. . .
Cr eat i ng mi r r or of conf i gur at i on. . .
Conf i gur at i on f i l es f or t he compl et e mul t i l i msyst em
syst emar e mi r r or ed on LI M 1.
Thi s wi l l pr oceed as a backgr ound j ob.
The r esul t wi l l be r epor t ed by mai l t o r oot .

#########################################################
NOTE: t he conf i gur at i on f i l es ar e onl y mi r r or ed t o LI M 1
see conf i g_mi r r or - hel p f or mor e i nf or mat i on
#########################################################
St ar t i ng Aast r a OM Daemon. . .
I nst al l i ng har deni ng. . .
10. 105. 64. 19 Har deni ng i s not f ul l y f unct i onal , i t wi l l be i nst al l ed.
Har deni ng: 10. 105. 64. 19
Done: 10. 105. 64. 19

Shut t i ng down SSH daemon. . done
St ar t i ng SSH daemon. . done
r oot pr event ed t o connect t hr ough ssh.
Appl yi ng i pt abl es f i r ewal l r ul es: Done
Manage Devi ce ser vi ce not conf i gur ed
i pt abl es i nst al l ed
Har deni ng f i ni shed successf ul l y.
Set t i ng check_cor e_f i l es as cr ont ab. . .
10. 105. 64. 19

The i nst al l at i on has f i ni shed successf ul l y!

Repl i cat i ng Conf i gur at i on f i l e . . .
10. For security reason change the password of the following users:
On all Telephony Servers: root and eri_sn_admin
If a default user was created during the Turnkey installation change
password for that user as well.
11. As root user on Server 1 set the master-server installer password by typing
mxConfig set MASTER_LIM installer_password xxx
where xxxx must be the same password as for eri_sn_admin.
12. Log off and then log on with the user created during the installation.
The show config command displays the configuration files.
Pr oCur ve Swi t ch 5406zl ( mxone- D) # show conf i g
26
I P conf i gur at i on on t he Aast r a 5000 zl Modul e
/ et c/ sysconf i g/ net wor k- scr i pt s/ i f cf g- et h0:
DEVI CE=et h0
ONBOOT=no
BOOTPROTO=dhcp
HWADDR=00: 1b: 21: 06: d5: 6e

/ et c/ sysconf i g/ net wor k- scr i pt s/ i f cf g- et h1:
DEVI CE=et h1
ONBOOT=no
BOOTPROTO=dhcp
HWADDR=00: 1b: 21: 06: d5: 6f
If necessary, you should configure your parameters using the ip command.
Pr oCur ve Swi t ch 5406zl ( mxone- D) # i p hel p
Usage: i p [ et h( i ) ] def aul t ( t o use def aul t conf i gur at i on)
i p [ et h( i ) ] dhcp ( t o use dhcp)
i p et h( i ) [ addr ess/ subnet mask] ( mask i n quad- dot t ed not at i on)
i p et h( i ) gat eway def aul t ( t o use def aul t gat eway x. x. x. 1)
i p et h( i ) gat eway del et e ( t o del et e cur r ent gat eway)
i p et h( i ) gat eway [ addr ess]

Descr i pt i on: Ent er t he i p addr ess.
i p et h0 10. 101. 0. 10/ 255. 255. 255. 0
Ent er t he gat eway addr ess.
i p et h0 gat eway 10. 101. 0. 1
8. Access the Aastra MX-ONE Web interface
You can also access the Aastra MX-ONE Web interface by clicking on the [Details]
link associated with the Services zl Module on the Device View of the ProCurve switch
web management interface.
27


9. Rebooting the Services zl Module
Rebooting should not normally be required and can potentially result in data loss. If for
some reason the Services zl Module becomes unresponsive, the following commands
can be used to reboot:
Pr oCur ve# service b 1

Pr oCur ve( ser vi ces- modul e- B: PR) # boot <CR>

Syst emwi l l be r eboot ed, do you want t o cont i nue [ y/ n] ? y
or
Pr oCur ve# service b name services-module

Pr oCur ve( ser vi ces- modul e- B: PR) # boot <CR>

Syst emwi l l be r eboot ed, do you want t o cont i nue [ y/ n] ? y
28
10. Technical Support
The Services zl Module is a hardware platform that allows application vendors to make
minor changes in their existing application software to run in a switch chassis. With a
wide variety of applications available from several vendors, HP is committed to
providing an "initial point of contact" for technical support. During this process, HP will
verify the installation, configuration, activation licensing, and warranty claims on the
Services zl Module. For problems concerning the application software, such as
configuration or licensing of the application from the vendor, HP may have to redirect
technical support to the application vendor to provide the best resources for solving a
support issue. Consequently, if you are confident that the technical support issue
resides within the application, it may be expeditious to contact the application vendor
directly.
For access to HP ProCurve support, go to:
http://www.procurve.com/customercare/support/
For access to Aastra technical support, go to:
http://www.aastra.com