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 Ericssonväg 30 S-12736 Hägersten 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:

ProCurve# show version <CR> Image stamp: ... <date, time> K.13.XX ... Boot Image: Primary

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 blade’s slot number in the chassis and the current Service OS.

ProCurve(services-module-B:HD)# Service OS (on the Hard Disk) ProCurve(services-module-B:CF)# Service OS (on the Compact Flash) ProCurve(services-module-B:PR)# Service OS agent (on the Product partition)

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.

ProCurve Switch 5406zl(services-module-B:PR)# boot service <CR> Changing boot from Product OS to Service OS. System will be rebooted. Do you want to continue [y/n]? y Rebooting… ProCurve Switch 5406zl# service b 1 <CR> ProCurve Switch 5406zl(services-module-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:

/images/MX-ONE_J9464A_XXXXXX_XXXX/

6

Type "services" to list the services installed on the Services zl Module:

ProCurve> services <CR> Installed Services Slot Index Description 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:

ProCurve# service b 1 <CR> ProCurve(services-module-B:HD)#

or

ProCurve# service b name services-module <CR> ProCurve(services-module-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:

ProCurve(services-module-B:HD)# usb mount <CR>

ProCurve(services-module-B:HD)# usb copyfrom MX-ONE_J9464A_XXXXXX_XXXX <CR>

ProCurve(services-module-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.

ProCurve Switch 5406zl(services-module-B:HD)# ip help Usage: [no] ip [dhcp|IP-ADDR/MASK-LENGTH] Description: Set IP parameters for communication within an IP network by configuring a static IP address or attempting to get a dynamically-assigned IP address configuration. Using the 'no' form of this command will remove any assigned IP address.

7

For this example we will use a static IP address.

ProCurve Switch 5406zl(services-module-B:HD)# ip address 10.1.1.20/24 ProCurve Switch 5406zl(services-module-B:HD)# ip default-gateway 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-root/MX-ONE_J9464A_XXXXXX_XXXX/

Type "services" to list the services installed on the Services zl Module:

ProCurve> services <CR> Installed Services Slot Index Description 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:

ProCurve# service b 1 <CR> ProCurve(services-module-B:HD)#

or

ProCurve# service b name services-module <CR> ProCurve(services-module-B:HD)#

Next, type the following command to initiate FTP file transfer:

ProCurve(services-module-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 it’s 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:

ProCurve# services b 1 <CR> ProCurve(services-module-B:HD)# uninstall product <CR> ProCurve(services-module-B:HD)# install product MX-ONE_J9464A_XXXXXX_XXXX <CR>

At this point the software image is installed and ready to be activated.

4. Activate 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:

ProCurve# services b 1 <CR> ProCurve(services-module-B:HD)# licenses hardware-id activation <CR> The hardware Id for package "activation" is 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:

ProCurve# services b 1 <CR> ProCurve(services-module-B:HD)# licenses install activation SG0000GG000-A-0123456-ABCDEFG-0123456-ABCDEFG <CR> ProCurve(services-module-B:HD)# boot product <CR> Changing boot from Service OS to Product OS. System will be rebooted. Do you want to continue [y/n]? y Rebooting

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):

ProCurve# show services b <CR> Status and Counters - Services Module A Status HP Services zl Module J9154A Versions : A.01.06, B.01.03 Status : not responding For more information, use the show commands in services context ProCurve# 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:

ProCurve# show vlans <CR> Status and Counters – VLAN Information Maximum VLANs to support : 256 Primary VLAN : DEFAULT_VLAN Management VLAN : VLAN ID Name | Status Voice Jumbo ------- -------------------- + ---------- ----- ----- 1 DEFAULT_VLAN | Port-based No No 123 VLAN_123 | Port-based No No

For this example, the ports assigned to the default VLAN can be seen using:

ProCurve# show vlan 1 <CR> Status and Counters – VLAN Information – VLAN 1 VLAN ID : 1 Name : DEFAULT_VLAN Status: Port-based Voice : No Jumbo : No Port Information Mode Unknown VLAN Status ---------------- -------- ------------ ------ B1 Untagged Learn Up B2 Untagged Learn 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:

ProCurve# configure <CR> ProCurve(config)# vlan 123 <CR> ProCurve(vlan-123)# tagged B1,B2 <CR>

or else as untagged using:

ProCurve# configure <CR> ProCurve(config)# vlan 123 <CR> ProCurve(vlan-123)# untagged 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:

ProCurve Switch 5406zl(config)# show services Installed Services Slot Index Description Name D 1. Services zl Module services-module D 2. Aastra MX-ONE application. 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:

ProCurve Switch 5406zl# services d 2 <CR> ProCurve Switch 5406zl(mxone-D)#

Or

ProCurve Switch 5406zl# services d name mxone <CR> ProCurve Switch 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:

ProCurve Switch 5406zl# services d 2 <CR> ProCurve Switch 5406zl(mxone-D)# ? install Aastra MX-ONE Installation. configure Aastra MX-ONE Configure basic network parameters. startup Aastra MX-ONE Configure and start MX-ONE application. service Other services administration. reboot Reboot zl Module. show Show module operational information. log View log files. exit Return to the switch command context.

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.

ProCurve Switch 5406zl(mxone-D)# install Install of MX-ONE starts Unpacking files for HP Procurve One Service module ... This might take some time, please wait... Turnkey installation complete. You need to run configure and startup before you can use the application. ProCurve Switch 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.

ProCurve Switch 5406zl(mxone-D)# configure Network configuration

14

You must reboot the server before continuing with MX-ONE application installation.

ProCurve Switch 5406zl(mxone-D)# reboot

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.

Only 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 JAVA 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:

ProCurve Switch 5406zl(mxone-D)# startup

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.

Getting LIM data... Do you want to validate the system_conf.xml, Y/N: n Setting up ssh communication... Valid keys exists on the Host Copying script files... Verify the user's group...... 10.105.64.19 Checking Memory size in system 10.105.64.19 4136244 Kb RAM Checking and Stopping novell-zmd... 10.105.64.19Configuring of NTP Server... 10.105.64.19 Checking setting of clock source on ESU... Checking the status of syslog... 10.105.64.19 logrotate /var/log/localmessages... 10.105.64.19 Change directory permisson on var/tmp/ ... 10.105.64.19 Creating install_tmp_files directory... Disabling UseDNS in sshd config... 10.105.64.19 Starting SSH Communication in all the LIMs Turning off nscd (Name Server Cache Daemon)... 10.105.64.19 Checking IP ports... 10.105.64.19 IP Address Hostname /etc/hosts Checking /etc/sysconfig/named... 10.105.64.19 10.105.64.19 Activating local dns... 10.105.64.19 cat: /var/tmp/tmpfile: No such file or directory Start of named daemon OK Checking Dns Names... Installing heartbeat on 10.105.64.19... done Checking heartbeat... 10.105.64.19 Securing sctp module... Modifying kernel parameters... Setting Server Speed... 10.105.64.19 Checking Boot configuration... 10.105.64.19 Stopping ldap server... 10.105.64.19 Stopping Service Nodes... 10.105.64.19 LIM :10.105.64.19 is properly terminated.

24

RPMs not included in the telephony system Copying RPMs on the LIM(s) Copying RPM files... Installing RPMs... In place: 10.105.64.19:Xerces-c-2.6.0-5 Checking xinetd... 10.105.64.19 RPMs comprising the telephony system Copying RPMs on the LIM(s) Copying RPM files... Stopping Aastra OM Daemon... Installing RPMs... In place: 10.105.64.19:eri_sn-13.64-MR In place: 10.105.64.19:eri_om-9.56-1 In place: 10.105.64.19:egx_rfs-2.0-1 In place: 10.105.64.19:egx_sw-10.18-1 In place: 10.105.64.19:lsue_sw-1.4_5-1 Checking SSH communication between LIMs Stopping nfs server... 10.105.64.19 Disabling tftp... 10.105.64.19 Checking files... xml document can be used for installation Getting LIM data... Prepare for ldap installation... Prepare for ldap installation... Validating Configuration files... Copying files... 10.105.64.19 Replacing with MX-ONE 4.0 trial licenses Initiating ldap... Run ldap script on 10.105.64.19 Starting LDAP on 10.105.64.19 Starting ldap server... 10.105.64.19 Checking ldap status on all LIMs... Checking for LDAP status Inserting Configuration data into LDAP... Inserting Alarm Configuration into LDAP... Synchronizing file system... Checking for LDAP replication. This may go on for several minutes........... Removing old data... 10.105.64.19 Synchronizing file system... Checking for LDAP replication. This may go on for several minutes........... Backing up routes file... 10.105.64.19 Setting up routes... 10.105.64.19 Setting up supervision of default gateways... 10.105.64.19 Cannot start supervision of default gateways on 10.105.64.19 Starting Service Nodes... 10.105.64.19 Checking LIMs... (Please Wait... It may take few minutes)

25

Waiting for LIMs in 1 minutes of max 30 minutes. Waiting for LIMs in 2 minutes of max 30 minutes. LIM 1 is running. Adding cert_check to /etc/cron.daily/ directory 10.105.64.19 Backing up data... ICT application server is shutdown now. Activating Daemons... Creating mirror of configuration... Configuration files for the complete multilim system system are mirrored on LIM 1. This will proceed as a background job. The result will be reported by mail to root. ######################################################### NOTE: the configuration files are only mirrored to LIM 1 see config_mirror -help for more information ######################################################### Starting Aastra OM Daemon... Installing hardening... 10.105.64.19 Hardening is not fully functional, it will be installed. Hardening: 10.105.64.19 Done: 10.105.64.19 Shutting down SSH daemon..done Starting SSH daemon..done root prevented to connect through ssh. Applying iptables firewall rules: Done Manage Device service not configured iptables installed Hardening finished successfully. Setting check_core_files as crontab... 10.105.64.19 The installation has finished successfully! Replicating Configuration file ...

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.

ProCurve Switch 5406zl(mxone-D)# show config

26

IP configuration on the Aastra 5000 zl Module /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 ONBOOT=no BOOTPROTO=dhcp HWADDR=00:1b:21:06:d5:6e /etc/sysconfig/network-scripts/ifcfg-eth1: DEVICE=eth1 ONBOOT=no BOOTPROTO=dhcp HWADDR=00:1b:21:06:d5:6f

If necessary, you should configure your parameters using the “ip” command.

ProCurve Switch 5406zl(mxone-D)# ip help Usage: ip [eth(i)] default (to use default configuration) ip [eth(i)] dhcp (to use dhcp) ip eth(i) [address/subnet mask] (mask in quad-dotted notation) ip eth(i) gateway default (to use default gateway x.x.x.1) ip eth(i) gateway delete (to delete current gateway) ip eth(i) gateway [address] Description: Enter the ip address. ip eth0 10.101.0.10/255.255.255.0 Enter the gateway address. ip eth0 gateway 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:

ProCurve# service b 1 ProCurve(services-module-B:PR)# boot <CR> System will be rebooted, do you want to continue [y/n]? y

or

ProCurve# service b name services-module ProCurve(services-module-B:PR)# boot <CR> System will be rebooted, do you want to continue [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