Installation Guide - Tecnomen NGM 5.1.3 - IG - 6000700_11

ISO

90

01

No

. F

S 2

81

17

Installation Guide

Tecnotree NGM 5.1.3

Installation Guide

6000700/11

Installation Guide

Copyright

Copyright Tecnomen Lifetree Corporation 2009. All rights reserved. No part of this document may be reproduced, distributed, stored in a retrieval system or translated into any language, in any form or by any means, electronic, mechanical, magnetic, optical, photocopying, manual or otherwise, without the prior written permission of Tecnomen Lifetree (“Tecnotree”). For additional copies of the document, please contact Tecnotree by e-mail: [email protected].

Disclaimer

Tecnotree makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, Tecnotree reserves the right to revise this publication and to make changes from time to time in the contents hereof without obligation to notify any person of such revision or changes.

Feedback

Tecnotree endeavours to provide accurate and useful documentation for all Tecnotree products. To achieve this goal, the documentation group welcomes your comments and suggestions regarding any aspect of Tecnotree user documentation. Send your comments by e-mail to: [email protected].

Trademarks and Registered Trademarks

Products and product names mentioned in this document may be trademarks or registered trademarks of their respective owners.

Revision History

Version Issued Description

1 14.04.2008 First version for Tecnomen NGM 5.1.3.

O&M and troubleshooting instructions have been moved to other documents.

2 16.05.2008 Updated the instructions for installing the customer-specific .tar package.

Corrections in upgrade instructions.

Added instructions for installing the CoS script.

3 27.05.2008 Added instructions for configuring fibre switches and initialising Sun StorageTek storage.

Document 6000700/11 Author Lelde Sermone

Status Draft Editor Katja Temonen

Issue date - Acceptor Pertti Rantala

Installation Guide

Version Issued Description

4 17.09.2008 Updated references to TSS documentation.

Removed instructions to remove the RAID controller when RMS2126F servers are used for System Gateway.

Added instructions to remove one fibre card when RMS2126F servers are used for Infra Server.

5 25.09.2008 Added instructions for reinstalling Application Server and Infra Server nodes manually.

6 03.12.2008 Added instructions for removing the IPMI card on RMS2126F NGM nodes.

7 08.12.2008 Minor corrections.

8 17.12.2008 Added instructions for enbaling saving of greetings in the Mini Trial system.

9 14.01.2009 Minor updates.

10 03.03.2009 Section Selecting fencing method added.

11 16.04.2009 Installation instructions updated.

Copyright Tecnomen Lifetree Corporation 2009 6000700/11

Installation Guide

Preface

About This Document

This document describes the Tecnomen NGM installation process.

Note: When performing the installation with this document, make sure you have the necessary documents at hand. For example, the referred user guides provide NGM operation instructions needed during the installation. Moreover, this document only covers the NGM software installation, and the referred installation guides provide instructions for installing other necessary elements. For a complete list of documents referred to in this document, see section References.

In addition, make sure you have all the required information for the installation, for example, the required preconfigured configuration files. For more information, see section 2.2 Software Requirements.

Audience

This document is for Tecnotree personnel doing NGM installations.

This document assumes familiarity with the following subjects:

Linux

basic SQL

basic knowledge of server hardware

general usage of disk subsystems

IP networking

Copyright Tecnomen Lifetree Corporation 2009 6000700/11

Contents i

Contents1. INTRODUCTION..............................................................................................................................1

1.1. NGM Platform Overview.........................................................................................................1

1.2. Installation Phases....................................................................................................................5

2. PREREQUISITES FOR INSTALLATION.......................................................................................7

2.1. Hardware Requirements...........................................................................................................7

2.1.1. Hardware Requirements for System Gateways on RMS2126F Servers.......................7

2.1.1.1. Removing IPMI Cards on RMS2126F System Gateways................................7

2.1.1.2. Disabling PXE Booting on RMS2126F System Gateways..............................8

2.1.1.3. Checking Network Cables on RMS2126F System Gateways..........................9

2.1.2. Hardware Requirements for System Gateways on Sun Fire X4100 M2 Servers.......10

2.1.2.1. Checking IPMI NET MGT Port on Sun Fire X4100 M2 System Gateways. .10

2.1.2.2. Disabling PXE Booting on Sun Fire X4100 M2 System Gateways...............11

2.1.2.3. Checking Network Cables on Sun Fire X4100 M2 System Gateways...........11

2.1.2.4. Configuring Hardware RAID on Sun Fire X4100 M2 System Gateways......13

2.1.3. Hardware Requirements for NGM Nodes..................................................................14

2.1.3.1. Removing Fibre Cards on RMS2126F Infra Servers......................................15

2.1.3.2. Removing IPMI Cards on RMS2126F NGM Nodes......................................15

2.1.3.3. Enabling PXE Booting on NGM Nodes.........................................................16

2.1.3.4. Disabling Nvidia NICs on Sun Fire X4100M2 NGM Nodes.........................17

2.1.3.5. Configuring BIOS to Only Use USB 1.1 on Sun Fire X4100M2 NGM nodes17

2.2. Software Requirements...........................................................................................................17

2.2.1. Software Requirements for System Gateway.............................................................18

2.2.1.1. Uploading Cisco Catalyst 4948 Switch Configuration Files..........................18

2.2.2. Software Requirements for NGM Nodes....................................................................19

3. INSTALLING NGM........................................................................................................................20

3.1. Installing System Gateways....................................................................................................20

3.1.1. Installing Base OS Package........................................................................................21

3.1.1.1. Installing Base OS Package from CD-ROM...................................................22

3.1.1.2. Installing Base OS Package from Network.....................................................23

3.1.2. Installing Master Configuration File...........................................................................25

3.1.2.1. Installing Master Configuration File from CD-ROM.....................................25

3.1.2.2. Installing Master Configuration File from Network.......................................27

3.1.3. Verifying System Gateway Installation......................................................................29

3.1.4. Defining Local User Passwords in System Gateway..................................................29

Copyright Tecnomen Lifetree Corporation 2009 Installation Guide6000700/11

Contents ii

3.2. Installing System Servers.......................................................................................................30

3.2.1. Installing First System Server.....................................................................................30

3.2.2. Installing Second System Server................................................................................38

3.2.3. Importing nodes.properties and variable.properties Files...............38

3.3. Installing Application Servers, Infra Servers, IVR-Application Servers and Proxy Servers. 39

3.4. Configuring Fibre Switches....................................................................................................40

3.4.1. Configuring Fibre Switch using Serial Port................................................................41

3.4.2. Configuring Fibre Switch using Ethernet Port............................................................41

3.5. Initialising Storage..................................................................................................................42

3.5.1. Selecting Fencing Method..........................................................................................44

3.5.2. Initialising Storage with DotHill SANnet II 200 or Sun StorEdge 3510....................44

3.5.3. Initialising Storage with Sun StorageTek 2540 or 6140.............................................46

3.5.3.1. Configuring Dual Disk Pack...........................................................................46

3.5.3.2. Installing CAM Software................................................................................46

3.5.3.3. Configuring Sun StorageTek and Creating Data Volumes.............................47

3.5.3.4. Create File Systems and Database Files.........................................................48

3.6. Installing Data Set...................................................................................................................49

3.7. Installing TUI resources and End User Web Interface to Infra Server...................................51

3.8. Installing Prompts to Infra Server...........................................................................................51

3.9. Installing Terminal Server (Optional)....................................................................................52

3.9.1. Connecting to Terminal Server...................................................................................52

3.9.2. Configuring Basic Terminal Server Settings..............................................................53

3.9.3. Configuring Serial Port on Sun Servers......................................................................54

3.9.4. Configuring Terminal Server Ports.............................................................................55

3.9.5. Testing Terminal Server Connections........................................................................56

3.10. Adding hugemem Kernel to Server........................................................................................57

4. VERIFYING NGM INSTALLATION............................................................................................58

4.1. Check System Gateway Operations and High Availability....................................................58

4.2. Verifying NGM Node Installation..........................................................................................58

5. UPGRADING NGM SYSTEM.......................................................................................................59

5.1. Upgrading System Gateway...................................................................................................59

5.2. Upgrading NGM Nodes..........................................................................................................60

5.2.1. Upgrading System Server...........................................................................................60

5.2.1.1. Rolling Back System Server from Backup RPM Packages............................62

5.2.2. Upgrading Application Server and Infra Server.........................................................63

5.2.2.1. Rolling Back Application Server and Infra Server.........................................65

5.2.2.2. Installing CoS Script.......................................................................................65

5.2.3. Updating TUI Resources, End User Web Interface and Prompts...............................65

DEFINITIONS AND REFERENCES....................................................................................................67


Contents iii

APPENDIX A: NGM MINI TRIAL INSTALLATION.........................................................................69

APPENDIX B: SYSTEM GATEWAY INSTALLATION DETAILS...................................................75

APPENDIX C: USING SCT...................................................................................................................78

APPENDIX D: DUAL DISKPACK INSTALLATION.........................................................................92

APPENDIX E: CONFIGURING IP ADDRESSES FOR SUN STORAGETEK CONTROLLERS (SERIAL CONNECTION)..............................................................................................................94

APPENDIX F: NGM NODE INSTALLATION CHECKLIST.............................................................97

Appendix G: CAM Software Installation Procedure............................................................................103


3. Installing NGM 1

1. IntroductionThis chapter gives an overview of the Tecnomen Next Generation Messaging (NGM) system elements and the NGM installation phases covered in this document.

Ideally, the installation does not require any configuration tasks. However, in reality, changes are often required during and after the installation. This may be because not all the necessary data has been received from the customer before the installation, or because the customer has requested changes, for example, to the TUI.

This means that during the installation, you may need to do some manual configuration, for example, modify the node configuration using System Configurator Tool (SCT). It also means you may need to update the system with new customised packages after the installation, for example, to install customised TUI resources and prompts.

This document provides instructions both for installing the NGM system and updating it. For information about the configuration and customisation tasks, see ref. /1/ Configuration and Customisation, Customisation Guide.

1.1. NGM Platform Overview

The Tecnomen NGM platform consists of the following system elements:

System Gateways (SyGWs)

SyGW is a firewall and router between the NGM system and the operator’s network(s).

NGM units:

System Servers (SyS)

The System Servers hold information about the system (for example, configuration information, alarms and statistics). The NGM system element installation is also done from the System Servers.

Proxy Servers (PS) (optional)

The Proxy Servers act as a proxy between end subscribers and the NGM system. They are needed if the system offers services where end subscribers can connect to NGM through the Internet (that is, when the End User Web Interface is in use).

Application Servers (AS)

The Application Servers contain software to run all the defined services. The services are described in VoiceXML format. The


3. Installing NGM 2

interface between the Telco Server system and the Application Servers uses VoiceXML over HTTP.

Interactive Voice Response Application Server (IVR-AS)

The Application Server cluster hosts the IVR services by providing the runtime execution environment. The service endpoints are exposed to the VoiceXML browser as HTTP URLs at a virtual address that is load-balanced to the whole cluster. The configuration and media content reside on the Application Servers. The IVR-AS server is usually in its own network.

Infra Servers (IS)

The Infra Servers handle the storage of all other data except for system-related information. In other words, all message, subscriber and service data is stored and fetched through the Infra Servers.

Centralised Message Storage (CMS)

The CMS is the physical storage for all the data handled by the Infra Servers. It contains two different types of storage: a Courier mail storage and a database storage. The CMS is a fully redundant disk system with double power supplies and double RAID controllers.

Terminal Server (optional)

The Terminal Server gives a ‘local’ connection directly to the serial ports of the servers and switches. This makes it easier to manage and configure all the servers and switches in the NGM system.

Telco Server Units (TSU)

TSS200

In TSS200, each TSU consists of two Voice Browser Units (VBU). One VBU consists of one Central Processing Card (CPC) and from 1 to 4 IO Processing (IOP) cards.

CPC is a ‘master’ card, because it has disks, and all the call controlling software (for example, the SS7 stack and VoIP stacks) run on CPC. CPC acts as a disk server for all IOPs in a VBU. The CPCs are set to work as a redundant cluster pair, so that one of the CPCs is in active mode and the other in backup mode.

The IOP cards are diskless units. The Pulse Code Modulation (PCM) trunks are terminated into the IOP cards, and the Digital Signal Processor (DSP) is also connected to the IOP. This means the IOP cards handle the actual media (voice or video) and communicate with the Application Servers.

TSS100

In TSS100, the maximum setup consists of two call control units (often called CPC) and eight media processing units (often called IOP). Each TSS100 unit has its own hard disks.


3. Installing NGM 3

The minimum setup consists of two TSS100 servers (also called ‘TSS100 all-in-one’ servers), which both have a Digital Signal Processor (DSP) card. Both servers function as call control units and as media processing units, but as in the TSS200 environment, the units are in High Availability (HA) mode so that only one of the servers is in active mode for call control and the other is in backup mode.

Video Gateway (optional)

The Video Gateway acts as a gateway between the IP network and the circuit-switched Public Switched Telephone Network (PSTN) or Public Land Mobile Network (PLMN). Video calls from 3G mobile phones come in as circuit-switched calls, and they are terminated into the Video Gateway (over H.324M protocol). From the Video Gateway, the call continues as a video-over-IP call towards the Telco Server (over SIP).

If there are no video services or if the operator already has a Video Gateway elsewhere in their network, the Video Gateway is optional. If the operator already has a Video Gateway, the calls come in as video-over-IP calls through the operator’s IP network.

This document gives instructions for installing all of the above system elements except for the Telco Server and the Video Gateway.

For instructions on how to install the Telco Servers, see ref. /2/ TSS200 Operation, User Guide and /3/ TSS100 Operation, User Guide.

For instructions on how to install the Video Gateway and integrate it with NGM, see ref. /4/ Dilithium documentation and ref. /5/ Video Gateway Integration, Interface Description.


3. Installing NGM 4

The following diagram shows the overall picture of the Tecnomen NGM system:

Figure 1 Overview of the Tecnomen NGM level platform

Note: Physically, the System Gateways are in the NGM cabin.


3. Installing NGM 5

1.2. Installation Phases

There is no strict sequence in which the NGM system elements must be installed, but some recommendations must still be observed. Figure 2 illustrates the recommended installation phases followed in this document.

Figure 2 NGM installation phases

The recommended order for the installation phases is as follows:

1. As the System Gateways are connected with data transmission and IP operations, they must be installed first.

2. Install and configure the System Servers.

3. Install the rest of the NGM nodes: the Application Server, Infra Server and IVR-Application Server.

4. Initialise the storage and install the data set using the data XML files.

5. Install the TUI resources, prompts and the End User Web Interface.


3. Installing NGM 6

Note: The installation of the NGM Mini trial system differs from the normal installation procedure in some respects. For more information, see appendix A: NGM Mini Trial Installation.


3. Installing NGM 7

2. Prerequisites for InstallationBefore starting with the installation, make sure the hardware and software prerequisites described in this chapter are met.

2.1. Hardware Requirements

Make sure all the necessary hardware has been installed as instructed in the applicable Hardware Installation Manual. See ref.:

/6/ TMSFB Hardware, Hardware Installation Manual

/7/ Telco Application Server (TAS) Hardware, Hardware Installation Manual

/8/ Application Server (AS) Hardware, Hardware Installation Manual

In addition, make sure the System Gateway and NGM node hardware prerequisites described in the following sections are met.

2.1.1. Hardware Requirements for System Gateways on RMS2126F Servers

To install a System Gateway or a pair of them on RMS2126F servers, you need the following:

1 or 2 RMS2126F-AC or RMS2126F-DC model servers with quad Ethernet cards

Cat-5 network cables with RJ-45 connectors for each interface on the System Gateways

A short (about 10 cm) Cat-5 cable with RJ-45 connectors to interconnect two System Gateways in a paired configuration

Prepare the hardware for the System Gateway installation as instructed in the following subsections.

2.1.1.1. Removing IPMI Cards on RMS2126F System Gateways

Before starting the NGM installation, verify that there are no IP management (IPMI) cards installed on the System Gateway machines. IPMI bypasses the operating system (OS), and especially all OS firewalling rules, which is why there must not be any installed on the firewalls.

Remove the IPMI card before the machine is mounted to a cabinet.


3. Installing NGM 8

Figure 3 shows the IPMI card’s location in the machine:

Figure 3 IPMI card in the machine

2.1.1.2. Disabling PXE Booting on RMS2126F System Gateways

All the System Gateway hosts must have Preboot Execution Environment (PXE) booting disabled. Because the hardware is common to all system components and the other components need PXE booting, it must be disabled manually only on the System Gateways.

For more information about PXE, see ref. /9/ Preboot Execution Environment (PXE) Specification.

To disable PXE booting:

1. Power up the machine with the keyboard and monitor connected.

2. To enter the BIOS setup, press Delete during the boot process. The setup launches when all the connected hardware has been initialised. This may take a while.

3. Select the Advanced menu using the cursor keys.

4. Select PCI/PnP Configuration.

5. Select Onboard G-LAN1 OPROM Configure and set it to Disabled.

6. To save the settings and reboot, press F10 and select Yes.


3. Installing NGM 9

2.1.1.3. Checking Network Cables on RMS2126F System Gateways

Find out how the physical network connections of the System Gateways will be set up. Normally one of the System Gateway interfaces is reserved for synchronisation between the System Gateways, and two or more interfaces are connected to routed networks (at least the external and internal network, sometimes more).

The network configuration information, like all other settings for the System Gateways, is contained in the master site network description file in Unified Network Configuration Language (UNCL).

The System Gateway RMS hardware contains six Ethernet interfaces: two on the motherboard and four on the quad Ethernet PCI card (see Figure 4).

Figure 4 SyGW hardware connectors

The Ethernet interfaces are used as follows (their order is as indicated in Figure4):

The interfaces em0 to em3 (quad card) are used for connecting to external networks: the demilitarised (DMZ) network (that is, the Proxy Servers), the operator’s network and the IVR network.

The em4 interface (motherboard) is reserved for connecting to the NGM network, which contains the System Server, Application Server, Infra Server and Telco Server nodes.

The em5 interface (motherboard) is reserved for the PFSYNC network (the synchronisation traffic between the two System Gateways).

Note: Make sure that em5 is only connected with a cross-over cable between the


3. Installing NGM 10

gateways. For security reasons, the synchronisation interface must never be connected into a switch or other network equipment. For more information about PFSYNC, see ref. /10/ NGM Operation by Tecnomen, User Guide.

Because it cannot be guaranteed that the OS numbers the interfaces in the same way on every host, you must check the numbering for every System Gateway. It is especially important to confirm that the numbering of the secondary System Gateway is correct, because mistakes in its configuration may not be immediately evident.

Fill in Table 1 based on your information on the network interfaces of the System Gateways and the network layout, and then connect the network cables accordingly.

Interface name

Connected Network Notes

em0

em1

em2

em3

em4 Reserved for the NGM network.

em5 Reserved for the PFsync network.

Table 1 System Gateway network interfaces

2.1.2. Hardware Requirements for System Gateways on Sun Fire X4100 M2 Servers

To install a System Gateway or a pair of them on Sun Fire X4100 M2 servers, you need the following:

1 or 2 Sun Fire X4100 M2 model servers with Sun Dual Gigabit Ethernet Adapters

Cat-5 network cables with RJ-45 connectors for each interface on the System Gateways

A short (about 10 cm) Cat-5 cable with RJ-45 connectors to interconnect two System Gateways in a paired configuration

Prepare the hardware for the System Gateway installation as instructed in the following subsections.

2.1.2.1. Checking IPMI NET MGT Port on Sun Fire X4100 M2 System Gateways

Before starting the NGM installation, verify that there is no network cable connected to the IP management (IPMI) port on the System Gateway machines. IPMI bypasses the OS, and especially all OS firewalling rules, which is why there must not be any network cable connected to the NET MGT Ethernet port (see Figure 5 in section 2.1.2.3 Checking Network Cables on Sun).



2.1.2.2. Disabling PXE Booting on Sun Fire X4100 M2 System Gateways

All the System Gateway hosts must have Preboot Execution Environment (PXE) booting disabled. Because the hardware is common to all system components and the other components need PXE booting, it must be disabled manually only on the System Gateways.

For more information about PXE, see ref. /9/ Preboot Execution Environment (PXE) Specification.

To disable PXE booting:


2. To enter the BIOS setup, press F2 during the boot process.

3. Select the PCIPnP menu using the cursor keys.

4. Select Scanning onboard NIC OPROM and set it to Disable.

5. Select Scanning OPROM on Slot PCIE0 and set it to Disable.

6. Select Scanning OPROM on Slot PCIE1 and set it to Disable.


2.1.2.3. Checking Network Cables on Sun Fire X4100 M2 System Gateways

Find out how the physical network connections of the System Gateways will be set up. Normally one of the System Gateway interfaces is reserved for synchronisation between the System Gateways, and two or more interfaces are connected to routed networks (at least the external and internal network, sometimes more).

The network configuration information, like all other settings for the System Gateways, is contained in the master site network description file in Unified Network Configuration Language (UNCL).



The System Gateway Sun hardware contains six Ethernet interfaces: four on the motherboard and four on the Sun Dual Gigabit Ethernet Adapter PCI cards (see Figure 5).

Gigabit Ethernet ports (4)NET0: Nvidia CK8-04 NICNET1: Nvidia IO-04 NICNET2: Intel NICNET3: Intel NIC

USB connectors (2)

Gigabit Ethernet ports (2)Intel NICs

SERIAL MGT port

Video connector

Ethernet port NET MGT

AC power connectors (2)

BACK PANEL

FRONT PANEL

DVD-ROM drive

Hard disk drives

USB port

Power button

Power/OK LED

Locate button/LED

Service action required LED

Front fan fault LEDPower supply/rear fan tray fault LED

System overheat fault LED

Hard Disk Drive Status LEDsTop LED (blue): Reserved for future use.Middle LED (amber): Hard disk drive failed.Bottom LED (green): Hard disk drive is OK.

Gigabit Ethernet ports (2)Intel NICs

Figure 5 System Gateway hardware connectors for Sun Fire X4100 M2 server

In Figure 5, the network interfaces on the motherboard are named from NET0 to NET3 on the back panel. Connect the LAN cables to NET2, NET3 and to the Sun Dual Gigabit Ethernet Adapters on the PCIX0 and PCIX1 slots. These NIC ports are equipped with Intel’s NICs. In addition, you must disable Nvidia NICs.

To disable the Nvidia NICs completely:

1. While the Sun Fire X4100 M2 server is booting up, press F2 to enter the BIOS setup.

2. Select Chipset -> SouthBridge Configuration.

3. Select MAC Interface -> Disable.

4. Select IO4 MAC interface -> Disable.

5. Press ESC, and select Exit -> Save Changes and Exit.



The interfaces em0 to em5 are used as follows:

The interfaces em0 to em3 are used for connecting to external networks: the demilitarised (DMZ) network (that is, the Proxy Servers), the operator’s network and the IVR network.

The em4 interface is reserved for connecting to the NGM network, which contains the System Server, Application Server, Infra Server and Telco Server nodes.

The em5 interface is reserved for the PFSYNC network (the synchronisation traffic between the two System Gateways).

Note: Make sure that em5 is only connected with a cross-over cable between the gateways. For security reasons, the synchronisation interface must never be connected into a switch or other network equipment. For more information about PFSYNC, see ref. /10/ NGM Operation by Tecnomen, User Guide.

Because it cannot be guaranteed that the OS numbers the interfaces in the same way on every host, you must check the numbering for every System Gateway. It is especially important to confirm that the numbering of the secondary System Gateway is correct, because mistakes in its configuration may not be immediately evident.

Fill in Table 2 based on your information on the network interfaces of the System Gateways and the network layout, and then connect the network cables accordingly.

Interface name

Connected Network Notes

em0

em1

em2

em3

em4 Reserved for the NGM network.

em5 Reserved for the PFsync network.

Table 2 System Gateway network interfaces

2.1.2.4. Configuring Hardware RAID on Sun Fire X4100 M2 System Gateways

The Sun Fire X4100 M2 model server comes with two hard disk drives and with a hardware RAID. By default, the hardware RAID is switched off, and you must switch it on before installing any software.

To enable the hardware RAID:

1. While the server is booting and the LSI Logic Corp. text is displayed, press Ctrl+C.

2. Select Adapter SAS1064.



3. Go to RAID Properties, and select Create RAID1 (or IM) Volume.

4. Go to the RAID Disk column for the first disk, and press Space.

5. Select Delete (D).

6. To confirm the deletion, press Enter.

7. Go to the RAID Disk column for the second disk, and press Space.

8. Press C for Create the array.

9. Select Save changes then exit this menu and press Enter.

10. Press Esc twice, and select Exit the Configuration Utility and Reboot.

2.1.3. Hardware Requirements for NGM Nodes

Make sure the following hardware requirements are met for the NGM nodes:

Make sure all the hardware for the System Server, Application Server, IVR-Application Server and Mass Storage has been installed into the cabinet, and all the connections have been set up. For more information, see ref. /11/ Telco Application Server (TAS), Hardware Description and ref. /12/ Application Server and Storage System, Hardware Description.

There must be at least 36 GB of disk space available.

The installation server (System Server) must be equipped with a DVD drive.

When RMS2126F hardware is used, prepare it for the node installation as instructed in the following subsections.



2.1.3.1. Removing Fibre Cards on RMS2126F Infra Servers

RMS2126F Infra Servers come with two fibre cards. If Infra Servers are connected directly to the storage array, you must remove one of the fibre cards before the installation (see Figure 6).

Figure 6 Removing the fibre card

2.1.3.2. Removing IPMI Cards on RMS2126F NGM Nodes

Before starting the NGM installation, verify that there are no IP management (IPMI) cards installed on the NGM nodes. The nodes use an older version of BIOS, which is not compatible with the IPMI card and causes network problems.

Remove the IPMI card before the machine is mounted to a cabinet.



Figure 3 shows the IPMI card’s location in the machine:

Figure 7 IPMI card in the machine

2.1.3.3. Enabling PXE Booting on NGM Nodes

Make sure that PXE booting (booting from the network) is enabled for all NGM nodes. The nodes use PXE booting to fetch the installation image from the System Server. The System Server identifies the unit based on the MAC address, and sends the correct installation image for the type of node (for example, an Infra Server).

2.1.3.3.1. Enabling PXE Booting on RMS2126F NGM Nodes

To enable PXE booting (with RMS2126F servers):


2. To enter BIOS setup, press Delete during the boot process. The setup launches when all the connected hardware has been initialised. This may take a while.


4. Select PCI/PnP Configuration.

5. Select Onboard G-LAN1 OPROM Configure and set it to Enabled.




2.1.3.3.2. Enabling PXE Booting on Sun Fire X4100 M2 NGM Nodes

On Sun Fire X4100M2 servers, PXE booting is enabled as default. If you need to enable PXE booting:


2. To enter the BIOS setup, press F2 during the boot process.

3. Select the PCIPnP menu using the cursor keys.

4. Select Scanning onboard NIC OPROM and set it to Enable.

5. Select Scanning OPROM on Slot PCIE0 and set it to Enable.

6. Select Scanning OPROM on Slot PCIE1 and set it to Enable.


2.1.3.4. Disabling Nvidia NICs on Sun Fire X4100M2 NGM Nodes

The network interfaces on the motherboard are named from NET0 to NET3 on the back panel. Connect the LAN cables to NET2 and NET3. These NIC ports are equipped with Intel’s NICs. In addition, you must disable Nvidia NICs.

To disable the Nvidia NICs:

1. While the Sun Fire X4100 M2 server is booting up, press F2 to enter the BIOS setup.

2. Select Chipset -> SouthBridge Configuration.

3. Select MAC Interface -> Disable.

4. Select IO4 MAC interface -> Disable.

Do not exit BIOS yet.

2.1.3.5. Configuring BIOS to Only Use USB 1.1 on Sun Fire X4100M2 NGM nodes

Before installing the OS, configure the BIOS to only use USB 1.1 as follows:


2. Select USB Configuration.

3. Select USB Mass Storage Device Configuration.

4. Set USB Controller Support to USB1.1 only.

5. Press ESC, and select Exit -> Save Changes and Exit.

2.2. Software Requirements

Make sure the System Gateway and NGM node software prerequisites described in the following sections are met.



2.2.1. Software Requirements for System Gateway

To install the System Gateway software, you need the following:

The master site network description file in UNCL. The file is used to configure almost all settings on the System Gateways. The file also defines the NGM nodes, their roles and their IP network settings, and is used in configuring the nodes.

To get a preconfigured UNCL file for the installation, contact the Tecnotree platform team. For more information about the network description files, see ref. /13/ Unified Network Configuration Language Reference Guide, Configuration Manual.

Note: Make sure you have a user account defined in the UNCL configuration file. Otherwise you are not able to configure the system.

The installation CD-ROM from the software dispatcher.

Information on the System Gateway setup and network connections. For more details, see appendix B: System Gateway Installation Details and section 2.1.1.3 Checking Network Cables.

Cisco Catalyst 4948 switch configuration files, configured during the customisation phase based on templates using customer-specific data. To get the preconfigured switch configuration files for the installation, contact the Tecnotree platform team.

For more information about the switch configuration, see ref. /1/ Configuration and Customisation, Customisation Guide.

2.2.1.1. Uploading Cisco Catalyst 4948 Switch Configuration Files

Before installing the System Gateway, upload the appropriately configured Cisco Catalyst 4948 switch configuration files to the switches.

To upload the configuration files:

1. Use the Cisco management cable to connect the management port on the switch to your PC COM port.

2. Open a terminal software (for example, Putty) and connect using baud rate 9600.

3. Log in to the switch. On the first login, no user name and password are needed.

After the configuration has been loaded, the user name is tecnoadm and the password is tecnomen.

4. If prompted, quit the automatic setup.

5. To enter the EXEC mode, select enable.

6. To enter the configuration mode, select configure terminal.

7. Paste in the content of the switch configuration file.



8. To save the configuration to the switch memory, use the following command:write conf

9. To exit the configuration mode, select exit.

2.2.2. Software Requirements for NGM Nodes

To install the System Server, Application Server, IVR-Application Server and Mass Storage software, you need the following:

All IP network information defined in the UNCL file, and the IP Network Configuration Description document generated based on the file (see ref. /18/).

During the installation, you use the UNCL file to generate a nodes.xml file, which you then load to the System Configurator Tool (SCT) and create the unit configuration files for the nodes. For more information about the node and role configurations and about SCT, see appendix C: Using SCT.

The installation DVD from the software dispatcher.

The customer-specific .tar file from the maintenance project manager, containing the database XML files, TUI resources and the (optional) End User Web Interface. The file is named, for example, using the following format:<project>-<customer>-<project>-<customer>-<revision>.tar

The prompt package (either the generic or a customised one)



3. Installing NGMThis chapter gives instructions for installing the NGM system elements. Follow the instructions in the given order.

Before starting the installation, make sure the prerequisites described in chapter 2 Prerequisites for Installation have been met.

For an overview of the installation phases, see section 1.2 Installation Phases.

3.1. Installing System Gateways

Install the System Gateways and verify the installation according to the instructions in the following sections.

To install the System Gateway:

1. Boot the system with the installation CD-ROM.

If you are restoring a backup to the system, you can use the backup CD-ROM as the installation CD-ROM during the whole installation process.

The system boots from the CD-ROM, and the installation script starts automatically.

The script prints out the following:Tecnomen NGM System Gateway Install(I)nstall a new NGM System Gateway(S)hell for debugging

2. To start the installation, enter I and press Enter.

3. When the script prompts you to select the terminal type, press Enter to accept the default terminal type vt220.Terminal type? [vt220]

4. When the script sets the keyboard layout, do one of the following:

If you have US/UK layout keyboard, press Enter to keep the default setting:The default keyboard encoding is the US layoutDo you wish to select a different keyboard encoding table? [no]

If you have some other type of keyboard, first enter yes to select the keyboard type and press Enter.

After this, the script prompts you to select the keyboard type. Enter P or U, depending on the type of the connected keyboard, and press Enter:Select your keyboard type: (P)C-AT/XT, (U)SB or 'done' [P]



After this, the script prompts you enter the correct keyboard layout and press Enter:Table name? (or 'done') [us]

For a list of keyboard layout, see the summary table in appendix B: System Gateway Installation Details.

Note: When you proceed with the installation from this step, the installation completely overwrites the contents of the disk.

5. When the script prompts you to continue with the installation, enter yes:Proceed with install? [no]

The script now partitions the disk and creates the file systems. This may take a while, depending on the disk interface type.

6. When the script prompts you to set the identity of the host, enter the host name and press Enter:System hostname? (short form, e.g. 'foo') <host_name>

Warning!

Make sure the host name is correct; there is no way to reliably change it without a complete reinstallation.

It is vital that the host name matches the host name in the UNCL master configuration file exactly, because all configuration settings are made by using the host name as a key.

To find the host name (FQDN in the format p1-sygw01.telecom-operator.com), see ref. /18/ IP Network Configuration Description, section 2.1 NGM System Internal Network.

7. Define the root password by entering it twice:Password for root account? (will not echo) <goodpassword>Password for root account? (again) <goodpassword>

It is recommended that you use the same root password for both System Gateways in the cluster.

3.1.1. Installing Base OS Package

Next, install the base OS package on the System Gateway. Two installation methods are supported:

To install from a CD-ROM, follow the instructions in section 3.1.1.1 Installing Base OS Package from CD-ROM.

To install from the network using HTTP, follow the instructions in section 3.1.1.2 Installing Base OS Package from Network. Network installation is usually used to replicate the System Gateway installation from one unit to another.



Other methods listed by the installation script should work, but they are not officially supported.

3.1.1.1. Installing Base OS Package from CD-ROM

To install the base OS package from the installation (or backup) CD-ROM:

1. When the installation script prompts you to select the installation method, enter c and press Enter:Where are the install sets? (or ‘done’)

2. When the script prompts you to select the CD-ROM drive to install from, press Enter to select the default setting (cd0):Available CD-ROMs are: cd0Which one contains the install media? (or 'done') [cd0]

3. When the script prompts you to define the directory path to the packages, press Enter to select the default path (sgw/inst):Pathname to the sets? (or 'done') [sgw/inst]

Now the source of the packages has been set. The script lists the available packages, all marked with X to indicate they are selected for installation:[X] version[X] bsd[X] bsd.mp[ ] comp40.tgz...[X] site40.tgzFile name? (or 'done') [done]

If no packages are found, the script returns to the installation method selection, which can be redone (step 1).

4. To accept the package selection, press Enter.

5. When the script prompts you to start the installation, press Enter:Ready to install sets? [yes]

The script now installs all the selected packages. This takes about two minutes.

When the packages have been successfully installed, the script returns to the prompt for the installation method. Enter done and press Enter:Where are the install sets? (or 'done')

If there are error messages, redo the procedure from step 1 to retry the installation.

6. If the installation was successful, enter done and press Enter to proceed to the system configuration (see section 3.1.2 Installing Master Configuration File).



3.1.1.2. Installing Base OS Package from Network

You can use the network installation, for example, to replicate the System Gateway installation from one unit to another. All running System Gateways provide their installation packages and the master configuration file for their own configuration in the synchronisation network over HTTP.

To install the base OS package through the network:

1. When the installation script prompts you to select the installation method, enter h and press Enter.Where are the install sets? (or ‘done’)

The script now prompts you to define the network settings for HTTP installation. These settings are only used during the installation, and the operative networking settings are defined later. This means it is safe to use temporary settings here to install the packages from the laptop’s HTTP server or from some other temporary location.

2. The script prompts you to select the Ethernet interface:Available interfaces are: em0 em1 em2 em3 em4 em5.Which one you wish to initialize? (or 'done') [em0]

Do one of the following:

If you are installing from the other System Gateway, enter em5 and press Enter.

If you are using an ad hoc installation server, select an interface from em0 to em3.

3. To select the default values for the host name and media questions, press Enter for each question:Select the interface through which the installation server can be reached.Symbolic (host) name for em0? [p1-sgw01]The default media for em0 is media: Ethernet autoselectDo you wish to change the default media? [no]

4. Enter the IP address to be used by this machine during the installation, and the correct netmask (defined in the UNCL, see ref. /18/ IP Network Configuration Description, section 2.1 NGM System Internal Network).

If installing through the synchronisation interface from the other System Gateway, use the IP address and netmask of the synchronisation interface.

IP address for em0? (or 'dhcp') Netmask? [255.255.255.0]

5. If any other interfaces are needed during the installation, set them up. You may need two interfaces if you plan to fetch the configuration file later from some other network than the one where the installation packages are located in.



Usually, you can just enter done to end the interface setup.Available interfaces are: em1 em2 em3 em4 em5.Which one you wish to initialize? (or 'done') [em1]

6. When the script prompts you for information about the networking environment to be used during the installation, select the default values by pressing Enter (unless you need DNS during the installation):DNS domain name? (e.g. 'bar.com') [test.domain]DNS nameserver? (IP address or 'none') [none]

7. The script prompts you to enter the default route:Default route? (IP address, 'dhcp', or 'none')


If you are installing from the other System Gateway or some other HTTP server in the local network, enter none.

If a remote network is needed for installation, enter the IP address of the default gateway to the network.

8. At the following three prompts, select the default values by pressing Enter for each:Edit hosts with ed? [no]Do you want to do any manual network configuration? [no]HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none]

9. The script prompts you for the IP address or host name of the server where the packages are located:Server? (IP address, hostname or 'done')


If you are installing from the other System Gateway, enter the IP address of the other System Gateway in its synchronisation interface.

If you are using DNS for the installation, enter the IP address or host name of the installation HTTP server.

10. The script prompts you to enter the directory path to the packages on the server:Server directory? [sgw/inst]


If you are installing from the other System Gateway, select the default path (sgw/inst) by pressing Enter.

If you are using an ad hoc installation server, enter the server directory containing the installation packages.



When the packages have been successfully installed, the script returns to the prompt for the installation method. Enter done and press Enter:Where are the install sets? (or 'done')

If there are error messages, redo the procedure from step 1 to retry the installation.

When the installation has completed, proceed to the system configuration (see section 3.1.2 Installing Master Configuration File).

3.1.2. Installing Master Configuration File

Next, install the UNCL master configuration file for the system.

The same configuration file is used on all the System Gateways, as the file defines the configuration separately for each System Gateway. When the configuration file is processed during the installation, the host name you enter for a System Gateway is used as a key when creating the settings for it in the file.

Two installation methods are supported:

To install from a CD-ROM (it is always available on backup CD-ROMs), follow the instructions in section 3.1.2.1 Installing Master Configuration File from CD-ROM.

To install from the network using HTTP, follow the instructions in section 3.1.2.2 Installing Master Configuration File from Network. Network installation is usually used to replicate the System Gateway configuration from one unit to another.

3.1.2.1. Installing Master Configuration File from CD-ROM

To install the master UNCL configuration file to the System Gateway from the installation (or backup) CD-ROM:

1. When the installation script prompts you for the location of the configuration file, enter c for CD-ROM:Where is the master configuration file?

2. When the script prompts you to select the CD-ROM drive to install from, press Enter to select the default setting (cd0):Available CD-ROMs are: cd0Which one contains the configuration file? (or 'done') [cd0]

3. When the script prompts you to define the directory path to the configuration file, press Enter to select the default path (sgw/inst):Pathname to the config file? (or 'done') [sgw/inst]

4. The script prompts you to enter the configuration file name:Configuration filename? [config.uncl]



Do the following:

To select the default file name, press Enter.

If the CD-ROM has been prepared to be used on multiple sites and the file name is different for each site, enter the file name.

If the file fetching fails, the fetching process is automatically restarted from the configuration source question (step 1).

When the file has been fetched, the script performs a complete system configuration. It sets the networking settings, firewall rules, users and permissions automatically according to the configuration file. This process takes about one minute.

If the configuration system finds the given configuration file invalid, an error message is printed with the following prompt:The installed master configuration UNCL file is invalid. Either reboot the machine and reinstall with a valid file or press ENTER to open the configuration for editing in 'vi'.

Note the errors printed above the prompt, and press Enter to open the configuration file in the vi editor. Correct the error in the configuration, and save and exit (ZZ) the editor. The script automatically retries the configuration with the edited configuration file.

If the configuration was successful, the script prints the following message:Your NGM System Gateway install has been successfully completed!

A root shell prompt appears (#).

5. Remove the CD-ROM from the drive.

6. Enter halt and press Enter.

7. When the following message appears, power off the machine using the power switch:The operating system has halted.Press any key to reboot.

8. Power up the system.

9. Verify that the system boots and the following prompt is displayed (this takes a couple of minutes):OpenBSD/i386 (hostname.domainname) (ttyC0)login:

The installation is now complete. When both the master and backup System Gateway have been installed (if this is a redundant configuration), proceed to verifying the System Gateway installation (see section 3.1.3 Verifying System Gateway Installation).



3.1.2.2. Installing Master Configuration File from Network

You can use network installation to replicate the installation of a master or backup System Gateway to the other System Gateway. All active System Gateways provide their current configuration file with HTTP in the synchronisation network.

To install the master UNCL configuration file to the System Gateway from the network:

1. When the installation script prompts you for the location of the configuration file, enter h for HTTP server (or the other gateway):Where is the master configuration file?

2. If you wish to install the file from some other server than the one you installed the base OS packages from, you need to redefine the network settings. Otherwise, accept the values you defined previously. For more information, see steps 2-7 in section 3.1.1.2 Installing Base OS Package from Network.

3. After network settings, the script prompts you to enter the IP address or host name of the server where the configuration file is located:Server? (IP address, hostname or 'done')


If you are installing from the other System Gateway, enter the IP address of the other System Gateway in its synchronisation interface.

If you are using DNS for the installation, enter the IP address or host name of the installation HTTP server.

4. The script prompts you to enter the directory path to the configuration file on the server:Server directory? [sgw/inst]


If you are installing from the other System Gateway, select the default path (sgw/inst) by pressing Enter.

If you are using an ad hoc installation server, enter the server directory containing the installation packages.

5. The script prompts you to enter the configuration file name:Configuration filename? [config.uncl]

Do the following:

If you are installing from the other System Gateway, select the default file name by pressing Enter.

If you are using an ad hoc installation server, enter the file name.

If the file fetching fails, the fetching process is automatically restarted from the configuration source question (step 1).



When the file has been fetched, the script performs a complete system configuration. It sets the networking settings, firewall rules, users and permissions automatically according to the configuration file. This process takes about one minute.

If the configuration system finds the given configuration file invalid, an error message is printed with the following prompt:The installed master configuration UNCL file is invalid. Either reboot the machine and reinstall with a valid file or press ENTER to open the configuration for editing in 'vi'.

Note the errors printed above the prompt, and press Enter to open the configuration file in the vi editor. Correct the error in the configuration, and save and exit (ZZ) the editor. The script automatically retries the configuration with the edited configuration file.

If the configuration was successful, the script prints the following message:Your NGM System Gateway install has been successfully completed!

A root shell prompt appears (#).

6. Enter halt and press Enter.

7. When the following message appears, power off the machine using the power switch:The operating system has halted.Press any key to reboot.

8. Power up the system.

9. Verify that the system boots and the following prompt is displayed (this takes a couple of minutes):OpenBSD/i386 (hostname.domainname) (ttyC0)login:

The installation is now complete. When both the master and backup System Gateway have been installed (if this is a redundant configuration), proceed to verifying the System Gateway installation (see section 3.1.3 Verifying System Gateway Installation).

3.1.3. Verifying System Gateway Installation

Check the System Gateway status report to verify that the interfaces are up and running, the connections are active, and the state of one node is active and the other one is backup.

To check the short status report, use the following command:$ sgwctl status [n]

where [n] is an optional argument that defines the interval (in seconds) for how often the command refreshes the displayed status.



To stop the report printout, press CTRL+C.

For more information about System Gateway status reports, see ref. /10/ NGM Operation by Tecnomen, User Guide.

If there a problems with the System Gateway, map the physical Ethernet connectors to the names used by the OS. For more information, see Appendix B: System Gateway Installation Details.

3.1.4. Defining Local User Passwords in System Gateway

During the installation, you defined a local password for the root user. However, when the installation generated the personal user accounts based on the UNCL file, no local passwords were generated. At this point, the users can only log in to the System Gateways remotely using SSH (with SSH keys).

If there are users who need to access the System Gateways using a local console instead of SSH connections, you must set up passwords for the users.

Note: After the installation, it is strongly recommended that all operations (except setting the local user passwords) are done using personal user accounts.

The control scripts take care of the permissions, and all actions that need root access cause the user to be prompted for the root password. Because of this, there is no need to operate the system as root user. Many operations do not even work with the root account.

To set up local user passwords in a System Gateway:

1. If you want to view a list of users on the System Gateway, use the following command:# sgwctl show <hostname>

where <hostname> is the host name of the System Gateway.

The printout shows all the configuration details of the host. The users are listed at the end of the printout.

2. Log in as root user.

3. To set a local access password for a user, use the following command:# sgwctl passwd <username>

4. When prompted, enter the new password and press Enter.

Note: The local password cannot be used to log in remotely. Only SSH keys can be used for remote logins.

After verifying the System Gateway installation and creating the necessary local user passwords, proceed to installing the NGM nodes according to the instructions in the following sections. This includes installing the System Servers, Applications Servers, Infra Servers and IVR-Application Servers,



initialising the storage and installing the data set, and installing the TUI resources, prompts and End User Web Interface.

If you are familiar with the installation process, you can also use the check list in appendix F: NGM Node Installation Checklist.

3.2. Installing System Servers

Install the System Servers using the instructions in the following sections.

3.2.1. Installing First System Server

To install the first System Server:

1. Connect a keyboard and monitor to the System Server.

2. To access the BIOS, press Delete or F2 during the boot process.

3. Ensure that the primary boot drive is a CD-ROM drive as shown in the following figure (BIOS setting for System Server drives). You can change the device order by pressing ‘+’ or ‘-’. Remember to save the configuration.

4. Insert the installation DVD.



5. To boot the System Server, use the following command:linux ks=cdrom

The following figure shows the boot prompt:

Wait for the automatic installation to finish. It takes about 10 minutes.

6. When the installation has finished, remove the installation DVD.

7. Log in as root user with the password tecnomen.

8. To set the preliminary IP configuration, use the following command:ss-ipconf <system_server_1_name>

where <system_server_1_name> is the name of the first System Server according to the naming conventions, for example:p1-ss01.ngm.tecnomen.com

The System Server name (FQDN) is defined in the UNCL. For more information, see ref. /18/ IP Network Configuration Description, section 2.1 NGM System Internal Network.



9. In the Configure TCP/ IP window that appears, define the following:

In IP address and Netmask, enter the IP address and netmask of the System Server.

In Default gateway, enter the IP address of the System Gateway.

Warning!

1. The Primary nameserver must be left empty.

2. Make sure you enter the correct settings, or the installation will be unsuccessful.

The following figure shows an example of how the IP configuration is set for the System Server.

10. Check the date and time of the installation System Server, and if necessary, adjust them using the date command:date –u MMDDhhmmYYYY

Note: The node time zone must be set to UTC.

The next phase is creating the repository.

11. Insert the installation DVD in the proper disk drive and ensure there is enough disk space.

12. Copy the customer-specific <project>-<customer>-<project>-<customer>-<revision>.tar files to the System Server to the /root directory.

13. To initialise the repository, use the following command:repo-tool init <custom_tar_file>



The command uses the contents of the .tar file to create the repository based on which the Application Server, Infra Server and IVR-Application Server are installed. When creating the repository, the command prefers rpm packages found in the .tar file over rpm packages found on the installation DVD.

For slower machines, copying files and creating the repository can take up to half an hour.

Note! If you have .tar files to add to the repo, follow the instructions in 5.2.1 Upgrading System Server from step 6 onwards.

14. When the repository creation has finished, remove the installation DVD.

15. To generate the nodes.xml configuration file on the System Gateway based on the UNCL file, log in to the System Gateway and do one of the following:

If you have proxy servers in the setup, use the following command:sgwctl createnodes tecnomen-net dmz-net

If the setup does not have proxy servers, use the following command:sgwctl createnodes tecnomen-net

The nodes.xml file is created to the directory where you run the command.

If the nodes.xml file cannot be generated (for example, if the installation does not contain a System Gateway), or the file does not contain a complete and correct node configuration, use the System Configurator Tool (SCT) to configure the nodes. For more information, see appendix C: Using SCT.

16. To copy the nodes.xml file to the System Server, use the following command:scp nodes.xml pX-ss01:/var/lib/sconf/snapshots/

The next phase is retrieving the Machine Address Code (MAC) addresses of all the other nodes (Application Servers, Infra Servers, IVR Application Servers, Proxy Servers and the CMS).

A unit’s MAC address identifies the interface through which the System Server sends the correct installation image to the unit. If necessary, two MAC addresses can be used to provide a backup interface in case one interface is down.


To retrieve one MAC address per unit, follow steps 17-19.

OR:



To retrieve two MAC addresses per unit, boot each unit and write down both the displayed MAC addresses. After this, add the MAC addresses in the nodes.xml file (in the applicable role sections, in host.mac values).

For example:

<role name="p19-as01Role" type="noderole" parent="as-role"> <assign key="host.ip"> <value>192.168.19.238</value> </assign> <assign key="host.ipmiip"> <value>192.168.19.246</value> </assign> <assign key="host.mac"> <value index="0">00:50:56:10:00:10</value> <value index="1">00:50:56:10:00:11</value> </assign> <assign key="host.name"> <value>p19-as01</value> </assign>  </role>

If you used this second option, continue from step 20.

17. Ensure that all other node machines (except for the System Gateway) are powered off.

18. To retrieve the MAC addresses from the nodes, use the following command: scan-nodes /var/lib/sconf/snapshots/nodes.xml /var/lib/sconf/snapshots/macs.xml

19. For each node, do the following:

When the system asks to boot up the node, power up the corresponding physical machine.

When the system displays the Got MAC message, power off the corresponding machine.

Make sure that only the first Ethernet interface’s MAC address is taken.

The next phase is to load the initial site network description information (that is, nodes.xml and macs.xml) using SCT. This creates the node roles and the role tree.

20. To start the SCT, use the following command:sconf

21. Log in with an empty userid and password.

22. To load the configuration, select the Snapshot menu:



For more information about working with snapshots, see appendix C: Using SCT, Working with Snapshots.

23. At Restore the configuration from a snapshot file, select nodes.xml and Load.

Note: The system may display the warning Version information missing from snapshot. In this case, select Load Anyway.

24. Select macs.xml and Load.



25. To create the configuration files, go to the Unit configurations menu.

26. In Target nodes selection that lists all the nodes, make sure all nodes are selected.

27. To create the unit configuration files, select Create selected.

The unit configuration files are created and stored into a dedicated directory (/var/lib/sconf/output/).

28. To log out of the SCT, press SHIFT+Q.

29. To update the local configuration, use the following command:update-local-conf

This command creates the nodes.properties and variable.properties files based on the nodes.xml configuration file.



30. To reboot the machine, use the following command:reboot

Note: If you made changes to the nodes.xml file manually at the site, make sure you provide the modified file to Tecnotree product development.

3.2.2. Installing Second System Server

To install the second System Server:

1. Follow the instructions in steps 1-9 in section 3.2.1 Installing First System Server.

Note that in step 8, you must enter a proper name for the second System Server, for example:p1-ss02.ngm.tecnomen.com

2. To copy the configuration information from the first System Server, use the following command:ss-fetch-config <IP_address_system_server_1>

where <IP_address_system_server_1> is the IP address of the first System Server.

3. To reboot the machine, use the following command:reboot

The System Server is rebooted and a login prompt is shown. Log in as root user with the password tecnomen.

3.2.3. Importing nodes.properties and variable.properties Files

During the System Server installation, the nodes.properties and variable.properties files were created and stored in the /etc directory on the System Servers.

To copy the data in the files to the System Server databases, you must import the files to the System Servers. The data is needed for the alarms and statistics to work correctly.

When the System Servers have been started, import the files using the Java Management Extensions (JMX) console on the System Servers. You can use the JMX console through a web browser or on the command line. For more information about using the JMX Console, see ref. /14/ NGM Operation, User Guide.



To import the files:

1. On the System Server (ss-vip), verify that the node and role definitions in the /etc/nodes.properties file are correct.

2. To open the JMX console, do one of the following:

In a web browser, enter the following URL in the address field:http://<ss-vip>:8080/jmx-console/

On the command line, use the following command:jmxconsole

3. In the JMX console, locate and select Tecnomen:service=systemServerPropertiesDataInit.

4. Locate the resetNodesAndVariablesBasedOnProperties method and click Invoke to invoke it.

5. On both System Servers, restart Jboss using the following command:service xjboss restart

3.3. Installing Application Servers, Infra Servers, IVR-Application Servers and Proxy Servers

Install the Application Server, Infra Server, IVR-Application Server and Proxy Server nodes with the following instructions.

To install a node:

1. Connect a keyboard and monitor to the node.

2. Power up the corresponding machine.

To enter the BIOS menu, press F2.

3. Verify that the boot drive order is set in the same way as for the System Server, that is:

Boot from CDROM

Boot from HD

Boot from network

By default, the machine boots from the network using the PXE protocol.

The machine finds the IP address and starts the installation. Redhat’s Anaconda installer performs a fully automated installation for the node.

When the installation has been completed, the machine is rebooted and the login prompt is shown.



3.4. Configuring Fibre Switches

NGM uses QLoqic SANbox 5000 series fibre switches.

Note: Fibre switches are required for storage access when using Sun StorageTek 2540 or 6140 disk packs and when using machines with more than one fibre card/machine.

The nodes.xml file generated based on the UNCL file defines the IP addresses and host names for the fibre switches. Modify the nodes.xml file manually to define applicable entries for the fibre switches and deploy the unit configuration files. Based on nodes.xml, the fibre switch names are generated to the /etc/hosts file as san-fc-switch1 and san-fc-switch2.

Note: The fibre switch names in the /etc/hosts file must not be changed manually.

To define entries for the fibre switches in the nodes.xml file:

1. For the cms-role role in the nodes.xml file, verify that there are two entries for the switch that define the IP address as follows:

<role name="cms-role" type="static" parent="is-role"> <assign key="service.san.fc.switch1"> <value>10.0.0.10</value> </assign> <assign key="service.san.fc.switch2"> <value>10.0.0.11</value> </assign> </role>

2. For each Infra Server node with a CMS role in the nodes.xml file, define entries for switch port allocation.

For example:

<role name="p20-is04Role" type="noderole" parent="cms-role"> <assign key="host.ip"> <value>192.168.20.134</value> </assign> ... <assign key="fc.switch1.port"> <value>4</value> </assign> <assign key="fc.switch2.port"> <value>4</value> </assign></role>

In the example above, fc.switch1.port with value 4 defines that this Infra Server node is connected to fibre switch port 4 on the switch whose IP address is identified with the key service.san.fc.switch1 (see step 1).

After this, you need to log in to each fibre switch using either a serial port or an Ethernet port, and define the fibre switch’s IP address. Sections 3.4.1 Configuring Fibre Switch using Serial Port or 3.4.2 Configuring Fibre Switch



using Ethernet Port provide high-level instructions on how to do this. For detailed instructions, see the SANbox 5000 fibre channel switch installation quide that is shipped with the switches.

3.4.1. Configuring Fibre Switch using Serial Port

The serial port settings must be set to the following values:

Bits per second: 9600

Data Bits: 8

Parity: None

Stop Bits: 1

Flow Control: None

To configure the fibre switch using a serial port:

1. Use a null-modem F/F DB9 cable to connect to the RS-232 port on the switch with the default user name admin and password password.

2. When the connection has been made, use the following commands to enter the configuration mode:admin beginset setup system

3. Define the fibre switch IP addressing, and set the NTP server and remote log host to point to the System Server VIP address (ss-vip).

EthNetworkDiscovery (1=Static, 2=Bootp, 3=Dhcp, 4=Rarp) [Static ]EthNetworkAddress (dot-notated IP Address) [10.0.0.1 ] <switch IP address>EthNetworkMask (dot-notated IP Address) [255.255.255.0] <switch netmask>EthGatewayAddress (dot-notated IP Address) [10.0.0.254 ] <default gateway>AdminTimeout (dec value 0-1440 minutes, 0=never) [30 ]InactivityTimeout (dec value 0-1440 minutes, 0=never) [0 ]LocalLogEnabled (True / False) [True ]RemoteLogEnabled (True / False) [False ]RemoteLogHostAddress (dot-notated IP Address) [10.0.0.254 ] <ss-vip>NTPClientEnabled (True / False) [False ]NTPServerAddress (dot-notated IP Address) [10.0.0.254 ] <ss-vip>EmbeddedGUIEnabled (True / False) [True ]

4. To save and activate the settings, enter y and press Enter.

5. Repeat the procedure for the other fibre switch (using a different IP address for the fibre switch in step 3).

3.4.2. Configuring Fibre Switch using Ethernet Port

When the switch is powered up for the first time, it uses the default IP address 10.0.0.1. To connect to the switch and set the correct IP network settings, you can create a temporary interface on the System Server.



To configure the fibre switches using an Ethernet port:

1. Log in to System Server and use the following command to set up the temporary interface:ifconfig bond0:5 ipaddress 10.0.0.2 netmask 255.255.255.0 up

2. Use Telnet to connect to the address 10.0.0.1 with the default user name admin and password password.

3. When the connection has been made, use the following commands to enter the configuration mode:admin beginset setup system

4. Define the fibre switch IP addressing, and set the NTP server and remote log host to point to the System Server VIP address (ss-vip).

EthNetworkDiscovery (1=Static, 2=Bootp, 3=Dhcp, 4=Rarp) [Static ]EthNetworkAddress (dot-notated IP Address) [10.0.0.1 ] <switch IP address>EthNetworkMask (dot-notated IP Address) [255.255.255.0] <switch netmask>EthGatewayAddress (dot-notated IP Address) [10.0.0.254 ] <default gateway>AdminTimeout (dec value 0-1440 minutes, 0=never) [30 ]InactivityTimeout (dec value 0-1440 minutes, 0=never) [0 ]LocalLogEnabled (True / False) [True ]RemoteLogEnabled (True / False) [False ]RemoteLogHostAddress (dot-notated IP Address) [10.0.0.254 ] <ss-vip>NTPClientEnabled (True / False) [False ]NTPServerAddress (dot-notated IP Address) [10.0.0.254 ] <ss-vip>EmbeddedGUIEnabled (True / False) [True ]

5. To save and activate the settings, enter y and press Enter.

6. Repeat the procedure for the other fibre switch (using a different IP address for the fibre switch in step 2).

3.5. Initialising Storage

NGM supports the following storage types:

DotHill SANNet II 200 with direct fibre connections (see Figure 8 and Figure 9)

A storage accessed through a fibre switch



Figure 8 Direct fibre connections with DotHill disk pack and four Infra Server nodes (pre NGM 5.2)

Figure 9 Direct fibre connections with a DotHill disk pack and four Infra Server nodes

With direct fibre connections, GFS-related fencing is done by configuring the disk pack automatically during every reboot. If fibre switches are used between the storage and the nodes, the CMS nodes command the fibre switch ports to activate and deactivate host connections. A dual fibre switch configuration provides a fully redundant storage path.

Initialising the storage creates the mail and data storage partitions on the CMS using the data XML files provided in the customer-specific .tar file.



3.5.1. Selecting Fencing Method

Before initialising the storage, select the fencing method using SCT.

To select the fencing method:

1. Log in to SCT. For more information about using SCT, see appendix C: Using SCT, Operating SCT.

2. In the Roles menu, click cms-role. In fencing.method, select a value as follows:

If Dothill disk arrays are used, select Dothill(dothill) (default).

If fibre switches are being used with StorageTek, select Fibre switch fencing(fibre).

If you want to activate SCSI-3 persistent registration and reservation based fencing, select SCSI-3 persistent reservation(scsi3). Not in generic use.

1. Click Save to save the changes.

3.5.2. Initialising Storage with DotHill SANnet II 200 or Sun StorEdge 3510

This type of storage has been used in previous NGM releases and it is still supported with the same configuration. Only one fibre connection per machine is allowed. For example connections, see Figure 8.

HA requires that systems with the same role are connected to different controllers (upper and lower). Service provided by a nodes is available as long as one node (with the same role) is up and has a working storage connection.

For example, both nodes with a database role have an identical MySQL database, which is available to Application Servers as long as one of the nodes is up.

Configurations with two Infra Server machines and four Infra Server machines are allowed.

Warning!

When you initialise the storage according to these instructions, all the persistent data is deleted (subscriber and service settings, voice mails, greetings, and so on).

To initialise the shared storage with DotHill SANnet II 200 or Sun StorEdge 3510:

1. On the System Server, log in to cms-vip using SSH and use the su - command to change to root user.

2. To configure the disks and create the logical drives, do one of the following:

On an RMS server, use the following command:initstorage –c dothill



On a Sun server, use the following command:initstorage –c sun

3. When the system prompts you for a confirmation, enter yes and press Enter.

4. To log out of cms-vip, use the following command:exit

5. Use SSH to log in to db-vip and use the su - command to change to root user.

6. To create the file systems for MySQL and insert the initial data into the database tables, use the following command:initstorage –i mysql


8. When the system prompts you to deploy the initial database, enter y and press Enter.

The script creates the logical names, volume groups and file system for the disks MySQL is using. This operation can take around 20 minutes.

9. To log out of db-vip, use the following command:exit

10. Use SSH to log in to cms-vip and use the su - command to change to root user.

11. To create the file systems for the Courier mail server, use the following command:initstorage –i mail


The script creates the logical names, volume groups and file system for the disks the Courier mail server is using.

13. Reboot all Infra Servers using the following command:reboot

14. When the Infra Servers are up, reboot all Applications Servers using the following command:reboot

3.5.3. Initialising Storage with Sun StorageTek 2540 or 6140

The Sun StorageTek 2540 storage array (or Sun StorageTek 6140 that is used for data replication in the cold standby solution) requires a pair of working



fibre switches. The controllers on the disk pack have two fibre ports. Connect both controllers to both switches so that there is no single point of failure.

Note: Remember to configure the fibre switch IP addressing and physical FC switch port assignment in the nodes.xml file. For more information, see section 3.4 Configuring Fibre Switches. IP address information and port numbers are used for fencing nodes from GFS volumes. If this is not done correctly, you risk losing GFS file system content.

3.5.3.1. Configuring Dual Disk Pack

Systems with fibre switches allows using two disk packs for more IO performance. In this type of installation, the message storage load is divided between two different disk packs.

Note: This type of installation is not typical. For installation instructions, see appendix D: Dual Diskpack Installation.

3.5.3.2. Installing CAM Software

Sun StorageTek disk packs are managed using Common Array Manager (CAM) software, which you must first install on the System Server. The installation package is located in the /usr/share/cam directory. Version 6.4.1.5 or later of CAM is required.

This procedure applies to both single and dual disk pack setups.

Note: Even if the disk pack is shipped with CAM on the CD-ROM, do not use it. Installing CAM from the CD-ROM is tricky, because the CD-ROM also includes JRE and CAM has strict JRE dependencies.

To install the CAM software:

1. Log in to the active System Server (ss-vip) and use the su - command to change to root user.

2. Go to the /usr/share/cam directory.

3. To run the CAM installation script, use the following command and follow the instructions on the screen:./install-cam.sh

4. Accept the license agreement.

5. Select Typical installation.

6. Accept full installation. For an example of the installation procedure and screen output, see Appendix G.

The installation script prints a lot of output on the screen. When the installation is complete, it displays that CAM is listening at port 6789.

When you have installed the CAM software, access the management software in the URL https://<system server IP>:6789, and log in with user name root and password Tecnomen. CAM prompts you to enter general



information of the site, for example, the site address, city and phone number. If you do not have Internet connectivity during the registration, CAM bypasses the registration when starting up.

3.5.3.3. Configuring Sun StorageTek and Creating Data Volumes

Note: If needed, you can reset the IP address of a controller using the serial port. For more information, see Appendix E: Configuring IP Addresses for Sun StorageTek Controllers (Serial Connection).

Warning!

When you initialise the storage according to the following instructions, all the persistent data is deleted (subscriber and service settings, voice mails, greetings, and so on).

Creating the data volumes and file system takes a long time.

To configure Sun StorageTek and create the data volumes for Sun StorageTek:

1. To configure the Sun StorageTek and create the volumes, use the following command:/usr/share/cam/config-2450 –n <name> –a <IP a> –b <IP b> –g <gateway> –m <netmask>

where:

-n <name> defines the storage array’s name (must be unique), for example, p20-san1

-a <IP a> defines controller A’s net IP address

-b <IP b> defines controller B’s net IP address

-g <gateway> defines the default gateway for both controllers

-m <netmask> defines the netmask for both controllers

This command assumes that the disk packs have default IP addresses and a default name. The factory default IP addresses are 192.168.128.101/24 for controller A and 192.168.128.102/24 for controller B. The default name is "unnamed". If this is not the case, reset the name of the storage using the CAM software and reset the controllers to factory default values using the serial port. For more information, see Appendix E: Configuring IP Addresses for Sun StorageTek Controllers (Serial Connection).

When the script has finished, the storage pack starts creating the volumes. Creating the three columes takes approximately 3,5 hours. To view the status of the volumes, log in to the CAM software and check the job status. For information about logging in, see section 3.5.3.2 Installing CAM Software.

There is no need to wait for the disk packs to complete the creation of the volumes. The disk system is fully functional but slow until the RAID-1 and RAID-5 volume sync is complete.



2. Reboot all Infra Server nodes.

3. Log in to the active Infra Server (cms-vip) and use the su - command to change to root user.

4. To verify that the system sees all the volumes on the storage array that will be used, use the following command:ls /dev/mapper/

The following is an example output:/dev/mapper/3600a0b8000388ceb00000317474bbb73/dev/mapper/3600a0b800038a36600000335474bbafc/dev/mapper/3600a0b800038a3660000033f474bbbc6

This shows that the system sees three volumes: one for the message storage and two for the MySQL databases.

After this, proceed to configuring the file system.

3.5.3.4. Create File Systems and Database Files

When using a single disk pack, create the file systems and database files according to the following instructions. When using a dual disk pack, see instructions in appendix D: Dual Diskpack Installation.

To create the file systems and database files:

1. To create the file systems and database files, use the following commands:

On cms-vip:/usr/sbin/create-lvm-2450

After this, reboot all Infra Server nodes.

On cms-vip:/usr/sbin/create-mail-2450

On db-vip:/usr/sbin/create-mysql-2450

2. To verify that the created volumes and file systems are visible on Infra Server nodes, use the following command:ls /dev/mapper/

The following is an example output:3600a0b800032f4440000079747ff2076 control mail1vg-mail13600a0b800032f4440000079947ff20a2 db1vg-db13600a0b800032fe24000006fc47ff2091 db2vg-db1

Alternatively, you can verify the volumes using the CAM software.




3.6. Installing Data Set

Install the data set on the Infra Servers. The files are included in the customer-specific .tar file.

Because the Infra Servers use a shared storage, you only need to install the data set on one Infra Server.

To install the data XML files:

1. On the System Server, copy the customer-specific .tar file to the Infra Server /root directory, for example, as follows:scp <custom_tar_file> <IP address of IS>:.

2. Log in to the Infra Server (db-vip) to which you copied the .tar file.

3. In the root directory, create a temporary directory:mkdir <temp_dir>

4. Go to the temporary directory:cd <temp_dir>

5. Untar the customer-specific .tar file using the following command:tar –xvf /root/<custom_tar_file>

The .tar contents are unpacked into the temporary directory. The contents include the dbinit package for installing the data set, as well as a .zip file with the TUI resources and End User Web Interface, which are installed later.

6. Verify the dbinit package installed on the Infra Server using the following command:rpm -qa |grep dbinit

7. Uninstall the existing dbinit package using either one of the following commands:

rpm -e dbinit-<version number>-<build number>.i386.rpm

yum remove dbinit

8. Install the new dbinit package using either one of the following commands:

rpm -i dbinit-<version number>-<build number>.i386.rpm

yum install dbinit-<version number>-<build number>.i386.rpm

9. On the same Infra Server, remove the initial data from all the unit databases using the following commands:cd /usr/share/dbinitant nuke -Dhosts=<comma-separated list of host names>



For example:cd /usr/share/dbinitant nuke -Dhosts=p18-ss02,p18-is01,p18-is02,p18-ss01

10. To create the initial database schema, use the following command (for multiple hosts):ant schema -Dhosts=<comma-separated list of host names>

For example:ant schema -Dhosts=p18-ss02,p18-is01,p18-is02,p18-ss01

Note: The ant schema command can be used for only one host using the ant schema –Dhost= option or for multiple hosts using the ant schema –Dhosts= option.

11. To insert the initial data into the tables, use the following command:ant data -Dhosts=<comma-separated list of host names>

For example:ant data -Dhosts=p18-ss02,p18-is01,p18-is02,p18-ss01

12. Reboot all Application Servers one by one using the following command:reboot

13. On the System Server (ss-vip), verify that the node and role definitions in the /etc/nodes.properties file are correct.

14. Open the JMX console on the System Server by doing one of the following:

In a web browser, enter the following URL in the address field:http://<ss-vip>:8080/jmx-console/

On the command line, use the following command:jmxconsole

15. In the JMX console, locate and select Tecnomen:service=systemServerPropertiesDataInit.

16. Locate the resetNodesAndVariablesBasedOnProperties method and click Invoke to invoke it.

17. On both System Servers, restart Jboss using the following command:service xjboss restart



3.7. Installing TUI resources and End User Web Interface to Infra Server

Install the customer’s TUI resources (the VoiceXMLs) and the (optional) End User Web Interface to the Infra Server (that is, the CMS). They are located in the .zip file in the temporary directory where you unpacked the customer-specific .tar file. The End User Web Interface can be either the generic one or a customised one.

Because the Infra Servers use a shared storage, you only need to install the TUI resources and the End User Web Interface on one Infra Server.

To install the TUI resources and the End User Web Interface:

1. Go to the Infra Server to which you copied the .tar file.

2. Go to the repository:cd /usr/db/mail/repository

3. Unzip the .zip file to the repository from the temporary directory you created earlier:unzip /root/<temp_dir>/<zip_file>

The TUI resources and the End User Web Interface contents are unzipped to Class of Service (CoS) specific /usr/db/mail/repository/<CoS> subdirectories.

4. Go to the /usr/db/mail directory:cd ..

5. Change ownership for the whole repository:chown –R jboss:jboss repository

3.8. Installing Prompts to Infra Server

Install the prompts to the Infra Server (that is, the CMS) in the appropriate /usr/db/mail/repository/<CoS> directories. The prompts are in service-specific .tar.gz packages.

Because the Infra Servers use a shared storage, you only need to install the prompts on one Infra Server.

To install a prompt package:

1. Copy the package <service>_<language>_prompts.tar.gz to the /root/ directory on the Infra Server. This can be either the generic package or a customised one.

2. Go to the repository:cd /usr/db/mail/repository/<CoS>

3. Untar the .tar.gz file to the repository:



tar –xvf /root/<tar_file>

4. Go to the /usr/db/mail directory:cd ..

5. Change ownership for the whole repository:chown –R jboss:jboss repository

3.9. Installing Terminal Server (Optional)

The Terminal Server gives a local connection directly to the servers’ and switches’ serial ports, making it easier to manage and configure all the servers and switches in the NGM system.

3.9.1. Connecting to Terminal Server

Connect a PC or a terminal to the Terminal Server using the console cable. If you are using a PC, the Procomm, TeraTerm or HyperTerminal can be used in the Windows OS. In the Unix OS, Kermit or Minicom can be used.

The terminal parameters must be set as follows:

Parameter Value

Serial speed 9600 bps

Data length 8 bits

Parity None

Stop bits 1

Flow control None

Proceed as follows:

1. Power up the Terminal Server.

2. When the Terminal Server boots properly, a login banner appears.

3. Login as root user. The default password is tslinux.

3.9.2. Configuring Basic Terminal Server Settings

To make the Terminal Server available in the network, do the basic configuration using the configuration wizard. The configuration wizard edits four files: /etc/hostname, /etc/hosts, /etc/resolv.conf and /etc/network/st_routes.

To configure the basic settings for the Terminal Server:

1. To start the configuration wizard, use the following command: wiz

2. When the wizard prompts you to select whether or not to use the default settings, enter n and press Enter:



Set to defaults? (y/n) [N]: n

3. Enter a host name for the Terminal Server and press Enter:Hostname[CAS] : p1-ts01

4. To disable DHCP, enter n to specify a static IP address for the Terminal Server:Do you want to use dhcp to automatically assign an IP for your system? (y/n) [y] : n

5. Enter the IP address for the Terminal Server and press Enter:System IP[] : 192.168.18.121

6. Enter the domain name and press Enter:Domain name[cyclades.de] : lab.tec

7. Enter the IP address for DNS and press Enter:Primary DNS Server[192.168.10.3] :

8. Enter the IP address for the default gateway in the network (usually the System Gateway management network vip), and press Enter:Gateway IP[eth0] : 192.168.18.100

9. Enter the netmask, for example, 255.0.0.0, and press Enter:Network Mask[#] : 255.255.255.128

The system prints a summary of the defined information, for example:Current configuration:

Hostname : p1-ts01DHCP : disabledSystem IP : 192.168.18.121Domain name : lab.tecPrimary DNS Server : 192.168.10.3Gateway IP : 192.168.18.100Network Mask : 255.255.255.128

Are all these parameters correct? (y/n) [n] : y

10. Verify that all the defined information is correct.

If the information is correct, confirm it by entering y and pressing Enter.

If the information is false, enter n and press Enter, and restart the configuration from step 2.

11. To activate the configuration, press Enter:Do you want to activate your configurations now? (y/n) [y] : y

12. To save the configuration, press Enter:



Do you want to save your configurations to flash? (y/n) [n] : y

If Sun Fire X4100 M2 servers are used, continue to setting the Terminal Server serial port (see section 3.9.3 Configuring Serial Port on Sun Servers).

With RMS servers, continue to configuring the Terminal Server ports (see section 3.9.4 Configuring Terminal Server Ports).

3.9.3. Configuring Serial Port on Sun Servers

If Sun Fire X4100 M2 servers are used, you need to set the serial port for the Terminal Server before you configure the terminal server ports.

1. Connect to the Sun machine serial MGT port and set the connection parameters:

Baud Rate (Kbps) to 9600

Flow Control to None

Data Size to 8

Parity to None

Stop Bits to 1

2. To log in to the Sun ILOM CLI and change the host baud rate, use the following command:set /SP/serial/host/pendingspeed=38400

3. To commit the changes, use the following command:set /SP/serial/host/commitpending=true

4. To exit the CLI, use the following command:exit

3.9.4. Configuring Terminal Server Ports

Use the Web Manager to configure the Terminal Server ports for NGM servers and Telco Server units.

To configure the Terminal Server ports:

1. Connect to the Terminal Server using a Web browser:http://<ts-ip>/

where <ts-ip> is the IP address of the Terminal Server.

2. Log in to the Terminal Server as root user with the default password tslinux.

The Terminal Server web interface opens.

3. Click Wizard.



4. To select the security level, click Moderate and Next.

5. When the previously defined network parameters are displayed, verify they are correct and click Next.

The Console Access Server profile parameters are displayed.

6. Set the parameters for the default port profile:

Select Enable all ports

Connection Protocol to Console (SSH)

Baud Rate (Kbps) to 38400

Flow Control to Hardware

Data Size to 8

Parity to None

Stop Bits to 1

Do not select Authentication Required

7. Click Next.

The list of defined users is displayed.

8. Change the root user’s password as follows:

Select root on the list and click Change Password.

Enter the new password twice and click OK.

9. Optionally, add users as follows:

Click Add.

Define the user details: the user name and password, the group (that is, the access level) and select NonBio. You can leave the shell and comments empty.

10. Click Next.

11. In Enable Data Buffering, leave the check box unselected.

12. Set the syslog parameters:

Facility Number to Local 7

Add a new syslog server by entering the System Server VIP address in New Syslog Server and click Add.

13. Click Next and apply changes.

14. To change into manual configuration, click Expert.

To configure the individual port settings:

1. In the menu on the left, select Physical Ports.

2. Select port number 1 on the list, click Modify Selected Ports.

3. Set the following parameters:



In Alias, enter the host name of the machine where the port is connected.

In case of Telco Server units, also set Baud Rate (Kbps) to 9600.

4. Click Done.

5. Repeat steps 2-4 for all connected ports.

6. To save and apply the changes, click apply changes.

3.9.5. Testing Terminal Server Connections

When you have configured the Terminal Server, test that the connections to all the NGM servers and the Telco Server units are working.

To test a connection:

1. Connect, for example, through the first System Server using the following command:ssh <ss01-ip>

where <ss01-ip> is the IP address of the first System Server.

2. Use ssh to connect to the machine (for example, an Infra Server) that is connected to Terminal Server port 1:ssh :7001@<ts-ip>

where <ts-ip> is the IP address of the Terminal Server.

Make sure that you can connect to the machine.

3. To log out of the Terminal Server, use the following command:~.

(Enter AltGr ~ followed by a space, and a period ‘.’)

4. Repeat steps 2-3 for all ports that NGM machines are connected to, and verify that the connection is working.

3.10. Adding hugemem Kernel to Server

Note! This is not mandatory step, it is needed only in a System Server and Application Server, that have more than 2GB RAM available (e.g. RMS-F HW). Hugemem kernel allows more memory to be allocated to JBoss JVM (Java Virtual Machine), thus increasing the capacity of an individual server.

If MAS is nuke-installed later, these steps must be performed again. The JBoss startup script /usr/java/jboss-4.0.4.GA/server/jboss-clustered/scripts/run.sh has memory settings. After a new kernel is in place, these settings can be modified and increased.



To add the hugemem kernel to the server, complete the following steps:

1. Add hugemem RPM to Server using the following commands:

yum install kernel-hugemem

2. Set the hugemem kernel as the default to boot:

vi /boot/grub/grub.conf

#boot=/dev/sda

default=0



4. Verifying NGM InstallationThis chapter gives instructions for verifying the NGM installation.

4.1. Check System Gateway Operations and High Availability

To verify that the System Gateway connections and high availability are configured correctly:

1. Make a TCP connection (for example, using SSH) from the external network through the System Gateway to the NGM network. Keep the connection alive and verify that it works.

The connection must be one of those allowed by the master configuration file; otherwise the firewall rules block it.

2. On the active System Gateway, disconnect one Ethernet cable at a time (em0-3 and em4, but not em5), and verify that the connection to the NGM network is still active (that is, that the other System Gateway takes over).

Note: You must keep the cables connected at least for 10 seconds before disconnecting the next one.

4.2. Verifying NGM Node Installation

To verify that the installation of the NGM nodes was successful, you can do the following:

1. Verify that all the necessary processes are running. For more information, see instructions for operating Application Servers and Infra Servers in ref. /14/ NGM Operation, User Guide.

2. Open the log files, and verify that they do not contain any error messages. For more information about accessing log files, see ref. /14/ NGM Operation, User Guide.

3. For the Application Servers and Infra Servers, you can use the ipvsadm command to verify that the server clusters are configured correctly. For more information, see instructions for operating Application Servers and Infra Servers in ref. /14/ NGM Operation, User Guide.

4. Verify that you can connect to the Operation and Maintenance Tool. For more information, see ref. /16/ Operation and Maintenance Tool, User Guide.



5. Upgrading NGM SystemThis chapter gives instructions for upgrading the NGM system in the installation or testing phase, for example, with updated features or fixes.

Warning!

These instructions are not valid for upgrading NGM in a live environment.

The instructions for upgrading a live system need to be produced per case.

5.1. Upgrading System Gateway

Note: Because the HA protocols have changed in System Gateway version 1.6, it is not possible to perform an upgrade in a live system from version 1.5 (or earlier) to version 1.6 (or later). To view the version, use the following command on the System Gateway:$ sgwctl status

This kind of an upgrade can be done using the normal upgrade instructions below, but a scheduled downtime period is always needed because there will be network breaks during the upgrade.

In principle, you can upgrade a live System Gateway as follows:

1. Check that both System Gateways are operating normally (sgwctl status). System Gateway number 1 should be MASTER for all interfaces, and System Gateway number 2 should be BACKUP. All interface links should be ‘active’.

2. Make a backup CD-ROM of either System Gateway using the sgwctl backup command.

3. Reinstall the secondary System Gateway using the normal installation instructions (see section 3.1 Installing System Gateway).

However, note the following:

To boot and install software, use the new version’s installation CD-ROM.

When installing the master configuration file (see section 3.1 InstallingSystem Gateways), use the backup CD-ROM you generated in step 2 as the source disk.

4. When the installed secondary System Gateway comes up, wait for two minutes. After this, deattach all the networking cables from the primary System Gateway.



If networking complications arise, attach the cables again and roll back by restoring the secondary System Gateway (by installing from the backup CD-ROM).

5. Install the primary System Gateway with the new software release as in step 3.

6. After the installation, right before doing the reboot in step 6 (halt) in section 3.1.2.1 Installing Master Configuration File from CD-ROM, attach the network cables back.

5.2. Upgrading NGM Nodes

All the operations are done as root user.

To get the information on the platform software version running on servers, use the following command.rpm –q –i tecnomen-base

5.2.1. Upgrading System Server

You can upgrade the System Servers with the following instructions.

If something goes wrong with the upgrade, you can roll back to the previous System Server version using backed up RPM packages of the previous version. To enable the backup of the RPM packages, verify that the /etc/yum.conf file contains the following line:tsflags=repackage

If this line is defined, the old RPM packages are automatically backed up during the upgrade, and stored in the /var/spool/repackage directory.

To upgrade the System Server:

1. Log in as root user to the active System Server (ss-vip).

2. To save the existing packages, use the following command:repo-tool backup <version_tag>

where <version_tag> is the name you give to the current version.

3. To save the existing configuration, start the SCT:sconf

4. To make the copy of the current configuration, use the Snapshot menu. For more information, see appendix C: Using SCT.

5. Either make a backup of the System Server database or verify that the nightly backup is recent enough. Move this backup to a safe location. For more information about making backups, see ref. /14/ NGM Operation, User Guide.



Note: Do not leave the backup on the System Server’s hard drive.

6. Update the repository. Depending of the distribution media (separate tar packages or the complete DVD), do one of the following:

To update from tar packages, use the following command:repo-tool update <source> <destination>

where <source> is the tar file name of the update source (for example, NGMPLAT-trunk-15083.tar or NGMMAS-trunk-15083.tar) and <destination> is the update destination name (for example, NGMPLAT or NGMMAS).

The currently supported destinations are listed in the following table:

Destination Description

NGMMAS MAS packages

NGMPLAT Platform packages

NGIVR IVR packages

TSS Telco Server packages

updates Redhat’s official OS updates

To copy the new software from the DVD, use the following command on the active System Server:repo-tool dvdupdate

When updating from the DVD, you do not need to specify the source and the destination.

7. If you updated from the DVD in step 6, skip this step.

If you updated the repository from tar files, create an installation image using the following command:create-instimg

8. To update the System Server role package configuration, use the following command:yum groupupdate 'SS Role'

9. To upgrade the local package, use the following command:yum update

The command marks the packages for upgrading. To upgrade packages, enter y and press Enter.

The next phase is upgrading the database schema.

10. Stop Jboss on both System Servers:service xjboss stop

11. On the first System Server, update the database schema using the following commands:



cd /usr/share/dbinitant schema –Dhosts=P<pool number>-ss01,P<pool number>-ss02

Note: The ant schema command can be used for only one host using the ant schema –Dhost= option or for multiple hosts using the ant schema –Dhosts= option.

12. Verify that there are no errors.

13. To start Jboss, use the following command:service xjboss start

Wait for one minute for Jboss to start.

You may need to check the logs. For information on accessing log files, see ref. /14/ NGM Operation, User Guide.

The next phase is recreating the configuration using the SCT.

14. To save the configuration, use the Write configuration command.

15. To log out from the tool, press SHIFT+Q.

16. To update the local packages, use the following command:update-local-conf

17. Reboot the machine.

On the second (backup) System Server, proceed as follows:

1. To upgrade the local package, use the following commands:yum groupupdate 'SS Role'yum update

The command marks the packages for upgrading. To upgrade the packages, enter y and press Enter.

2. To update the local packages, use the following command:update-local-conf

3. Reboot the machine.

5.2.1.1. Rolling Back System Server from Backup RPM Packages

If the RPM packages were backed up during the System Server upgrade, you can roll back to the state before the upgrade. For information about enabling the RPM backup for the upgrade, see section 5.2.1 Upgrading System Server.

Note: You cannot use yum for the rollback. You must use the rpm command line utility, and it must be performed on every system requiring the rollback.



To roll the system back to a previous state, use the following type of command:rpm -Uvh --rollback 'yesterday'

The above example rolls back all RPMs that were installed after yesterday. Other examples of the time format accepted by RPM rollback are ‘2 days ago’, ‘1 hours ago’ and ‘december 25’.

Note: When you are absolutely sure you do not need the backed up RPMs for rollback, remove them from the /var/spool/repackage directory.

5.2.2. Upgrading Application Server and Infra Server

If you want to upgrade the Application Server or Infra Server before first upgrading the System Server, you must start by upgrading the installation repository (steps 1-7 and 17-18 in section 3.2.1 Installing First System Server).

To install upgraded software to the NGM nodes:

1. Either make a backup of the Infra Server database or verify that the nightly backup is recent enough. Move this backup to a safe location.

Note: Do not leave the backup on the Infra Server’s hard drive.

For more information about making backups, see ref. /15/ System Backup and Restore, Technical Description.

2. To shut down Jboss on the Application Servers, log in to each Application Server and use the following command:service xjboss stop

3. Log in as root user on the active System Server.

The first phase is upgrading the Infra Servers.

4. From the active System Server, use the following command to reinstall the first Infra Server node:nuke-em-clean <node>

For example:nuke-em-clean p1-is01

You may also be prompted to log in to the Infra Server nodes as root user with the password tecnomen.

The reinstallation script logs in to the listed node, deletes the boot sectors, and reboots the node. The script retrieves the installation packages and unit configuration files from the System Server, and reinstalls the node.

If the connection between the System Server and the node is not working, you cannot use the nuke-em-clean command. In this case, you need to manually reinstall the node:



First remove the old public keys for this node from the System Server. If you do not remove them, the node is not installed correctly, for example, the network devices are not configured and the node is inaccessible. On the System Server, give the following command:rm /var/cfengine/ppkeys/root-<node name>*

After this, give the disable-bootsector command on the node to be reinstalled, and reboot the node.

5. Log in to the Infra Server you reinstalled and verify that it comes up.

6. Repeat steps 4-5 for each Infra Server.

7. On both Infra Servers, change ownership for the MySQL directories and the repository using the following commands:chown -R mysql:mysql /var/lib/mysqlchown -R jboss:jboss /usr/db/mail/repository

8. When the Infra Servers have been reinstalled, log in to both Infra Server nodes with the database role (usually numbers 01 and 02), and update the database schema using the following commands:cd /usr/share/dbinitant schema

The next phase is upgrading the Application Servers.

9. From the active System Server, reinstall the Application Servers in the same way as you installed the Infra Servers (steps 4-5).

First reinstall the first Application Server, and when it is up and running, you can reinstall the other Application Servers at the same time using the following command:nuke-em-clean <node_list>

For example:nuke-em-clean p1-as02 p1-as03 p1-as04

10. To verify that the Application Servers and Infra Servers have been upgraded:

Check that all the processes are running and that each node’s Weight value is 1:ipvsadm –l

Note: The ipvsadm command displays only resources managed by the current server. The ipvsadm command on cms-vip may not display all services if the database resource is on another server.

Check that all the RPM packages have been installed:rpm –q –a



5.2.2.1. Rolling Back Application Server and Infra Server

You can roll back the Application Server and Infra Server nodes to an earlier software version if needed. The nodes are cleaned completely during a reinstallation.

The recommended method for rolling back an Application Server or Infra Server node is as follows:

1. Reinitialise the repository from a System Server installation DVD that contains the older software version. Follow steps 1-7 and 17-18 in section 3.2.1 Installing First System Server.

2. Reinstall the node from the repository following the instructions in section 5.2.2 Upgrading Application Server and Infra Server.

An alternative, non-recommended method is to roll back the node using a backup .tar file created from the System Server repository.

5.2.2.2. Installing CoS Script

For licencing purposes, NGM provides a script for viewing the total number and the number of active subscriptions per Class of Service (CoS).

This script is automatically installed on the Infra Server as part of the NGM installation. If necessary, you can also get the script from the software dispatcher and install it manually.

To install the CoS script:

1. Copy the getCos.sh script to the /usr/sbin/ directory on the Infra Server.

2. To change the permissions for the script, use the following command:chmod 755 /usr/sbin/getCos.sh

For more information about the script and instructions on running it, see ref. /10/ NGM Operation by Tecnomen, User Guide.

5.2.3. Updating TUI Resources, End User Web Interface and Prompts

The TUI resources, End User Web Interface contents and prompts are stored in CoS-specific /usr/db/mail/repository/<CoS> directories on the Infra Servers. To update these, you need the new customised installation packages.

To update customised content:

1. Log in to the active Infra Server (ss-vip) as root user.

2. In the /usr/db/mail/repository directory, create a .tar backup file of the subdirectory of the service you want to update.

Note: Do not store the .tar file in the subdirectory you backed up, move it to some other location.



3. Extract the new .tar or .tar.gz package(s) to the /usr/db/mail/repository directory according to the instructions in sections 3.7 Installing TUI resources and End User Web Interface to Infra Server and 3.8 Installing Prompts to Infra Server.

Depending on the customisation work done, the new contents either replace the old contents (if the subdirectory name is the same in the .tar or .tar.gz file) or they are extracted into a new subdirectory.

If you upgrade the TUI resources or prompts but the new files are not taken into use, the Telco Server may still be using the old files from cache. In this case, go to the Infra Server directory where you stored the new files, and update the timestamp of all files to the current time using the following command:touch *


Appendix G: CAM Software Installation Procedure 66

Definitions and References

DefinitionsAS Application ServerCAM Common Array ManagerCARP Common Address Redundancy ProtocolCPC Card PC, Central Processing CardDSP Digital Signalling ProcessorGW GatewayIOP IO –Processing cardIP Internet ProtocolIS Infra ServerIVR-AS Interactive Voice Response Application ServerNGM Next Generation MessagingOMC Operation and Maintenance CentrePCM Pulse Code ModulationPFSYNC Packet Filter SynchronizationPLMN Public Local Mobile NetworkPSTN Public Switched Telephone NetworkPXE Preboot Execution EnvironmentRAID Redundant Array of Independent DisksSCP Secure CopySSH Secure ShellSCT System Configurator ToolSyGW System GatewaySyS System ServerTCP Transmission Control ProtocolTSU Telco Server UnitUDP User Datagram ProtocolUNCL Unified Network Configuration LanguageVBU Voice Browser UnitVLAN Virtual Local Area Network VoiceXML Voice Extensible Markup Language



References /1/ Configuration and Customisation, Customisation Guide, 6000688/2/ Telco Server 2.1.1 TSS200 Operation, User Guide, 6000438/3/ Telco Server 2.1.1 TSS100 Operation, User Guide, 6000360/4/ Dilithium documentation, http://www.dilithiumnetworks.com//5/ Video Gateway Integration, Interface Description, 054135/6/ TMSFB Hardware, Hardware Installation Manual, 050231/7/ Telco Application Server (TAS) Hardware, Hardware Installation Manual,

6000159/8/ Application Server (AS) Hardware, Hardware Installation Manual, 047661/9/ PXE, http://www.pix.net/software/pxeboot/archive/pxespec.pdf, 17.10.2003/10/ NGM Operation by Tecnomen, User Guide, 6000748/11/ Telco Application Server (TAS), Hardware Description, 052525/12/ Application Server and Storage System, Hardware Description, 054228/13/ Unified Network Configuration Language Reference Guide, Configuration

Manual, 051119/14/ NGM Operation, User Guide, 6000730/15/ System Backup and Restore, Technical Description, 6000869/16/ Operation and Maintenance Tool, User Guide, 6000484/17/ NGM Mini Trial System, Technical Description, 6000589/18/ Customer-specific IP Network Configuration Description/19/ Sun StorageTek Common Array Manager Software, Installation Guide###


http://www.pix.net/software/pxeboot/archive/pxespec.pdf

http://www.dilithiumnetworks.com/


Appendix A: NGM Mini Trial InstallationThe NGM Mini Trial system is a non-redundant system configuration with a minimum set of hardware components required for executing services:

Telco Server

Video Gateway (optional)

System Server as one physical machine

Application Server and Infra Server integrated into a single physical machine

For more information about the system architecture and elements, see ref. /17/ NGM Mini Trial System, Technical Description.

For instructions on how to install the Telco Servers, see ref. /2/ TSS200 Operation, User Guide and /3/ TSS100 Operation, User Guide.

For instructions on how to install the Video Gateway and integrate it with NGM, see ref. /4/ Dilithium documentation and ref. /5/ Video Gateway Integration, Interface Description.

Prerequisites for Mini Trial Installation

Before installing the NGM Mini trial system, make sure the following prerequisites are met

At least two machines are available: one for the System Server and the other for the AS and IS

Prerequisites for the System Server:

There must be at least 36 GB of disk space available.

The installation server (System Server) must be equipped with a DVD drive.

The NGM release installation DVD from the software dispatcher.

Prerequisites for the Application Server and Infra Server:

If PXE booting is not available, the machine must be equipped with a DVD drive.

The customer-specific .tar file from the maintenance project manager, containing the database XML files, TUI resources and the (optional) End User Web Interface. The file is named, for example, using the following format:<project>-<customer>-<project>-<customer>-<revision>.tar



The prompt package (either the generic or a customised one)

Installing System Server for Mini Trial

To install the System Server for the Mini Trial system:

1. Install the System Server as normal using the installation DVD. For more information, see steps 1-14 in section 3.2 Installing System Server.

2. Retrieve the MAC addresses of the Application Server and Infra Server node. For more information, see steps 17-19 in section 3.2 Installing System Server.

3. Define the node configuration as instructed in section mini-trial.xml file for Mini Trial Installation. Later in this procedure, you copy this node configuration to an XML file on the System Server.

4. Log in to the System Server using SSH.

5. Go to the snapshots directory:cd /var/lib/sconf/snapshots

6. To create a mini-trial.xml file in the directory, use the following command:vi mini-trial.xml

7. Copy-paste the node configuration to the mini-trial.xml file, and save the file.

8. Start SCT, load the mini-trial.xml file and create the node configuration files. For more information, see steps 20-30 in section 3.2 Installing System Server.

The MAC addresses are defined in the mini-trial.xml file, which means you do not load the macs.xml file as in the complete installation.

Installing Application Server and Infra Server for Mini Trial

If the mini trial system’s BIOS does not support the PXE boot option, you can use the NGM installation DVD to install the Application Server and Infra Server node.



To install the Application Server and Infra Server node:

1. Install the node as instructed in section 3.3 Installing Application Servers, Infra Servers, IVR-Application Servers and Proxy Servers.

Note: If you boot the node from the DVD, give Redhat’s installation program the following boot option:linux ks=http://<System_Server_IP_address>/sconf/get/etc/ks.cfg

2. When the machine has rebooted, log in to the node VIP using SSH.

3. To create the initial database schema, use the following commands:cd /usr/share/dbinitant schema

4. To insert the initial data into the tables, use the following command:ant data

5. To reboot the node, use the following command:reboot

Installing TUI Resources, End User Web Interface and Prompts for Mini Trial

Install the TUI resources, prompts and the (optional) End User Web Interface in the same way as in the complete installation.

For more information, see sections 3.7 Installing TUI resources and End User Web Interface to Infra Server and 3.8 Installing Prompts to Infra Server.

mini-trial.xml file for Mini Trial Installation

The following is the ngm-mini-nodes.xml file used in the NGM Mini Trial installation.

You must define the node configuration by modifying the values marked in bold. Replace XX with the pool number.

<?xml version="1.0" encoding="UTF-8"?><snapshot scope="full"> <meta> <user>sconf</user> <comment>This is a nodes.xml template for NGM Mini (aka. Cooper) installations.</comment> </meta> <role name="systemconfigurator-base" type="static"> </role> <role name="external-role" type="static" parent="systemconfigurator-base"> </role>



<role name="signalling-base" type="static" parent="systemconfigurator-base"> </role> <role name="tecnomen-base" type="static"> <assign key="network.domain"> <value>training.tecnomen.com</value> </assign> <assign key="network.gateway"> <value>Default gateway IP</value> </assign> <assign key="network.netmask"> <value>Subnet mask</value> </assign> <assign key="service.ntp.server"> <value index="0">System server VIP</value> </assign> <assign key="service.dns.server">  <value index="0"/> </assign> </role>

<role name="ss-role" type="static"> <assign key="host.vip"> <value>System Server VIP</value> </assign> </role>

<role name="as-role" type="static"> <assign key="host.vip"> <value>Application Server/Infra Server VIP</value> </assign> </role>

<role name="is-role" type="static"> <assign key="host.cms.vip"> <value>Infra Server CMS-VIP</value> </assign> <assign key="host.db.vip"> <value>Infra Server DB-VIP</value> </assign> </role>

<role name="as-role@pXX-as01" type="noderole" parent="as-role"> <assign key="host.ip"> <value>Application Server/Infra Server IP Address</value> </assign> <assign key="host.mac"> <value>00:00:00:00:00:00</value> </assign> <assign key="host.name"> <value>pXX-as01</value> </assign> </role>

<role name="as-role@pXX-as02" type="noderole" parent="as-role"> <assign key="host.ip"> <value>Dummy node IP Address, must be in the same subnet as the Application Server/Infra Server node</value> </assign> <assign key="host.mac">



<value>00:00:00:00:00:00</value> </assign> <assign key="host.name"> <value>pXX-as02</value> </assign> </role>

<role name="ss-role@pXX-ss01" type="noderole" parent="ss-role"> <assign key="host.ip"> <value>System Server IP address</value> </assign> <assign key="host.mac"> <value /> </assign> <assign key="host.name"> <value>pXX-ss01</value> </assign> </role>

<role name="cms-role@pXX-as01" type="dynamic" parent="cms-role"> </role> <role name="cms-role@pXX-as02" type="dynamic" parent="cms-role"> </role> <role name="db-role@pXX-as01" type="dynamic" parent="db-role"> </role> <role name="db-role@pXX-as02" type="dynamic" parent="db-role"> </role> <node name="pXX-as01"> <node-role name="as-role@pXX-as01" /> <add-role name="cms-role@pXX-as01" /> <add-role name="db-role@pXX-as01" /> </node> <node name="pXX-as02"> <node-role name="as-role@pXX-as02" /> <add-role name="cms-role@pXX-as02" /> <add-role name="db-role@pXX-as02" /> </node> <node name="pXX-ss01"> <node-role name="ss-role@pXX-ss01" /> </node></snapshot>

HTTPD Configuration Changes to Enable Saving of Greetings

To be able to save greetings, the configuration for httpd should be modified. All lines with the keyword PREFERRED_HOST need to be commented out in the configuration file.

The httpd configuration is defined in the following file: /etc/httpd/conf.d/webdav.conf

To modify the httpd configuration:

1. Go to /etc/httpd/conf.d.

2. Comment out the lines which include the keyword PREFERRED_HOST lines, in other words, the following lines:

[root@p1-minicooper-as01 conf.d]# pwd



/etc/httpd/conf.d[root@p1-minicooper-as01 conf.d]# cat webdav.conf | grep PREFERRED_HOST

# RewriteRule (.*) - [E=PREFERRED_HOST:${preferred:$1}]# RewriteCond %{ENV:PREFERRED_HOST} !^localhost$# RewriteRule (.*) http://%{ENV:PREFERRED_HOST}%{REQUEST_URI} [L,P]

[root@p1-minicooper-as01 conf.d]#

3. Restart the HTTPD daemon using the following commands: /etc/init.d/httpd stop and /etc/init.d/httpd start.



Appendix B: System Gateway Installation Details

System Gateway Setup Questions

The following table lists the System Gateway setup questions. The default settings are shown in bold.

Question Answer

Number of System Gateways?

( ) One (Demo or test system)

( ) Two (Production System with HA)

Hostname for the Primary System Gateway?

Hostname for the Backup System Gateway if included in the configuration?

Installation Source? ( ) CD-ROM

( ) Network with HTTP

If CD-ROM: Is this a custom installation CD?

( ) Yes (ask layout from disk producer)

( ) No (you can use the defaults for the installation)

If Network: Installation server?

If Network: Installation directory?

( ) Default

( ) Custom:

Configuration file location? ( ) CD-ROM

( ) Network with HTTP

If CD-ROM: If custom CD, specify configuration file directory

( ) Default

( ) Custom:

If CD-ROM: If custom CD, specify configuration file name

( ) Default

( ) Custom:

If Network: Configuration server IP?



Question Answer

If Network: Configuration server directory?

( ) Default

( ) Custom:

If Network: Configuration file name?

( ) Default

( ) Custom:

Keyboard layout? ( ) be, Belgium French

( ) br, Brazilian

( ) de, German

( ) dk, Danish

( ) es, Spanish

( ) fr, French

( ) hu, Hungarian

( ) it, Italian

( ) jp, Japanese

( ) la, Latin-American

( ) lt, Lithuanian

( ) no, Norwegian

( ) pl, Polish

( ) pt, Portuguese

( ) ru, Russian

( ) sf, Swiss French

( ) sg, Swiss German

( ) si, Slovenian

( ) sv, Swedish, Finnish

( ) tr, Turkish

( ) ua, Ukrainian

( ) uk, British

( ) us, US English

root password for the System Gateways?

Decide the password, but do not write it here.



Mapping Ethernet Connectors to Interface Names on System Gateway

If necessary (for example, when troubleshooting the System Gateway), you can map the physical Ethernet connectors into the names used by the OS.

To map the connectors to their OS names:

1. Disconnect all Ethernet cables except one.

2. Use the following command:$ ifconfig em

3. Find which of the interfaces shows Status: active. This is the one with the cable connected.

4. Change the Ethernet cable to the next interface, and repeat steps 2-3.



Appendix C: Using SCTThe System Configurator Tool (SCT) is used for managing the NGM units and their configurations (see Figure 10). You use the SCT during the installation to create the unit configurations, but you can also use it later, for example, to add new NGM nodes (or units) or change the unit configurations.

Figure 10 Configuration process



The configuration process is as follows:

1. The nodes’ description information is loaded into the system using the nodes.xml file. It is done automatically when SCT is started.

2. Information about the configuration key properties and packages-to-roles mappings is loaded into the system from the comps.xml file and configuration RPM packages.

3. If necessary, you can manually update the configuration using SCT. After making the changes, you need to make a snapshot of the configuration.

4. You create the unit configuration files using the SCT Unit Configurations -> Create selected operation.

Main Configuration Concepts

This chapter gives an overview of the main concepts in SCT:

Configuration parameters

Nodes

Roles (static and dynamic) and the role tree

Mapping RPM packages to roles

Inheriting parameters in the role tree

Configuration Parameters

All the node configuration data is stored in parameters in the nodes.xml file. The parameters have the following:

Configuration key

Data type

Domain of legal values

Default values

Assigned values (only these values can be set by the user)

Assigning a parameter sets the value for the already existing configuration key. Parameters are always assigned in the context of a role.

Table 3 describes the supported data types of the configuration parameters.

Data type Content example Legal values Global default value

Primitive

String Plain text, single row Regular expressions ““; an empty string

Text Plain text, multiple rows Regular expressions ““; an empty text



Data type Content example Legal values Global default value

Numeric Integer and decimal Minimum and maximum value range

0; the zero integer

Boolean True or false false

IP address IP address range 0.0.0.0; an invalid address

Enumerated List of options List of selectable options, each given as a pair of strings (label and value)

The first value specified in the list of selectable options declared for the parameter.

Reference Reference to another role using the target role name

Existing role ““; null reference

Vector

All primitive data types

Variable length

Zero, one or more values The global default is an empty list of zero values. Different values can be specified when declaring the parameter.

All primitive data types

Fixed length

Two or more values All values will be set to the global default of its primitive type unless otherwise specified in the declaration.

Table 3 Supported parameter data types

Roles

All configuration parameters are associated with roles so that each role has a list of parameters. SCT makes these associations by combining the parameters from all the packages with packages-to-roles mappings (see a later section for more information).

Nodes

A node represents a single host machine that has a specified function in the system hardware cluster. The node itself does not contain any configuration information. The node is simply an identifier (a unique name) linked to roles.

A node can be linked to one or more roles, and the first (and often the only) role on that list is the node role of that particular node. The rest of the roles (if there are any) are generic additional roles for the node.

The configuration information specific to a node is stored in the node’s node role. The configuration information for a cluster of nodes is stored in roles at a higher level in the ‘role tree’ (for a description of the role tree, see below).



Role Tree

Roles are organised into a hierarchical tree, where each role has exactly one parent role. The only role that does not have a parent is the root of the role tree.

The tree always retains a hierarchical form. This means that the chain of ancestors starting from any role must always end at the root: circular paths are not allowed.

In theory, the role tree can have as many hierarchical levels as needed. In practice, only three levels are normally used:

1. The highest level is the root role alone. It is called tecnomen-base.

2. The middle level (or levels) is a set of generic roles named according to their functional purpose, for example, ss-role, as-role and netbackup-role.

3. The lowest level is a set of node roles, each specified for an individual node in the system hardware cluster. The node roles are named according to the nodes (normally by appending the word Role to the name of the node). Node roles are usually created by loading the nodes.xml file. It is done automatically whenever SCT is started. Node roles can be created manually by adding children to the existing roles.



Figure 11 shows a role tree with four role levels: the root role and the mid-level generic roles are static (that is, predefined), and the roles at the lowest level are dynamic (for a description of static and dynamic roles, see below).

Nodes are associated with the role tree through the roles they are linked to. The node displayed in Figure 11 is linked to three nodes, one of which is its node role.

Figure 11 Role tree

Static and Dynamic Roles

Roles can be of the following two types:

Dynamic roles can be added and removed with SCT.

Static roles are fixed in the system: they cannot be added or removed with SCT.

In the role tree, the root role is always static, and the node roles at the lowest level are always dynamic.

The generic roles in the middle levels in the role tree can be either static or dynamic. Currently, all the defined generic roles are static (they are defined before the installation phase). However, more dynamic roles may be used in



future. As a convention, the role suffix is used in generic role names and the Role suffix in node role names.

Packages-to-Roles Mappings

The packages-to-roles mappings are stored in the comps.xml configuration file (a standard file that comes with Red Hat Linux). The file specifies the static roles and the packages mapped to them.

The file must not be modified. You can edit the parameter values of the static roles (stored in nodes.xml) using SCT.

Inheriting Configuration Parameters

Each role inherits all the configuration parameters from its parent. If a role and its parent both have a parameter assigned with an identical configuration key, the parameter values of the child role override the values of the parent role.

Figure 12 Assigning parameter values vs inheriting parameter values

A parameter always has a value. If no value is defined in the role itself, the role inherits the value from an ancestor role. If no value is defined in any of the ancestor role, the global default value is used.

For simplicity, all the values of a variable width vector (a list) are assigned or inherited as a whole: either all the values are inherited, or all the values are assigned to the role. If you assign one value for a child role, the rest of the inherited values are also changed as assigned to that role, and they are no longer inherited from the parent role. In other words, if you later change one of these values in the parent role, they do not change for the child role.

On the other hand, each value of a fixed length vector (‘an array’) can be assigned or inherited separately. So, it is possible to assign any value of a fixed width array for a role while other values are inherited from its ancestor role.



Operating SCT

This section gives instructions for operating SCT.

Starting SCT

There are two ways to use SCT:

Using an SSH client, for example, PuTTy (for Windows) or the ssh command (for Linux)

Using HTTP or HTTPS access

To start SCT using an SHH client:

1. Start an SSH client with the IP address (for example, 192.168.10.210) that is the System Server virtual address (ss-vip). The IP address depends on the installation site. For more information, see the customer-specific ref. /18/ IP Network Configuration Description.

2. Log in as root user with the password tecnomen.

3. To start SCT, use the following command:sconf

This starts an ELinks browser at the specified address, and opens the login window.

To start SCT using HTTP(S), start a web browser and enter the following URL:http://<ss-vip:8080>/system-configurator/login.htm

In the login window that opens, leave the user name and password fields empty and select Logon. The SCT window opens, displaying the Roles menu.

Table 4 describes the SCT menus.

Menu Main functionality

Roles Provides the following functions:

Viewing main role parameters

Assigning new values to role parameters

Creating and deleting (dynamic) child roles

Creating new nodes

Deleting roles (only applies to dynamic roles)

Nodes Provides the following functions:

Viewing main node parameters

Linking roles to a node

Creating sibling nodes



Menu Main functionality

Unit configurations Provides the following functions:

Creating unit configuration files

Deploying configuration files

Signalling Used for signalling, not relevant for NGM.

Snapshot Provides the following functions:

Creating a snapshot

Restoring a configuration from a snapshot file

Importing or exporting a snapshot file

Log out Used for exiting SCT.

Table 4 SCT menus

Navigating and Selecting in SCT

When using SCT with a web browser, you can navigate and select items using the mouse and the keyboard as usual.

When using SCT with an ELinks browser, you can navigate and select items as follows:

Use the up and down arrow keys to navigate through menus, fields, or parameters.

To select and accept, use the right arrow key.

To return to the previous operation or status, use the left arrow key.

Tip: You may be able to use ELinks with a mouse if your SSH client supports it.

Exiting SCT

To exit SCT, select Logout and press SHIFT+Q.

Maintaining Roles

Through the Roles menu, you can do the following:

View information on roles, such as their parent role, their child roles, the nodes linked to them, the role parameters and the software packages

Assign new values to role parameters

Create new child roles

Create new nodes



Delete dynamic roles (static ones cannot be deleted)

Viewing Parameters

To save space on the screen, only the most important parameters are shown. To view a full list of parameters, select Show all keys.

Assigning Role Parameters

By default, role parameters are inherited from the parent role (or ancestor).

To assign a parameter explicitly to this role:

1. In the Roles menu, select the role whose parameters you want to modify.

2. Enter a value in the parameter field. For vector values, click Edit to enter the values.

You can filter the parameters displayed by entering the search criteria and selecting Filter. To display all the parameters, select Default.

3. Select Save.

Creating New Roles

In the role tree, you can create new generic roles (in the middle levels of the tree) and node roles (associated with nodes).

When you have created a role, you cannot modify the its name or its parent role.

To create a new (dynamic) role in the role tree:

1. In the Roles menu, select the parent role (the role under which you want to create the new role).

2. Select New Child.

3. Enter a name for the role. As a convention, the role suffix is used in generic role names and the Role suffix in node role names.

4. Select Save.

After creating a role, you can modify its parameters, create child roles for it, or associate nodes with it.

Deleting Roles

You can only delete dynamic roles.

Note: If you delete a role, all its child roles and all nodes associated with the deleted roles are also deleted.

To delete a role:



1. In the Roles menu, select the role you want to delete.

2. Select Delete role.

Creating New Nodes

You can create nodes and associate them with node roles in the role tree. You can create a node in two ways:

Select a role and create a node for it. The role changes into a node role.

Select a node and create a sibling node for it. A node role is created automatically for the new node.

After you have created a node, you cannot change its node role.

To create a new node for a role:

1. In the Roles menu, select the node role under which you want to create the new node.

2. Select New node.

3. Enter a name, IP address and MAC address for the new node.

4. If necessary, link the node to additional roles by selecting the respective role name. You can also link additional roles to the node later through the Nodes menu.

5. Select Save.

To create a new sibling node:

1. In the Nodes menu, select the node for which you want to create a sibling node.

2. Select New Sibling.

3. Enter a name, IP address and MAC address for the new node.

4. If necessary, link the node to additional roles by selecting the respective role name. You can also link additional roles to the node later through the Nodes menu.

5. Select Save.

Maintaining Nodes

Through the Nodes menu, you can do the following:

View the node parameters

Link additional roles to a node



Linking Additional Roles to a Node

To link additional roles to a node:

1. In the Nodes menu, select the node that you want to link additional roles to.

2. Select the check box(es) for the respective role. To clear the changes, select Reset.

3. Select Save.

Creating and Deploying Unit Configurations

The unit configurations are created based on the nodes.xml file, the role tree and the parameters.

You can create the unit configurations using the Create and Deploy operations in SCT:

The Create selected operation creates the unit configuration files and stores them to a dedicated directory (/var/lib/sconf/output/). This can be used, for example, if you want to view the files before deploying them to the units (through the Unit configurations menu).

The Deploy selected operation creates the unit configuration files and stores them to the dedicated directory, creates a snapshot of the previous configuration, and deploys the configuration files to the units.

If the directory contains earlier versions of the unit configuration files, the newly created files replace them. However, the replacing is only done if the whole writing process is completed successfully. Otherwise the unfinished files remain in a temporary working directory.

To create or deploy the configuration:

1. In the Unit configurations menu, select the nodes for which you want to create or deploy the configuration. By default, all the nodes are selected.

In most cases, there is no need to write the configuration for the whole system, but only for those nodes to which you have made modifications.

2. In the Unit configurations menu, select Create selected or Deploy selected.

When the operation has been completed, a list of the nodes is displayed, indicating for each node if generating the configuration (and deploying it, in the case of Deploy selected) was successful.

To view a log of the writing process for the Deploy selected operation, select View deployment log file.



Another way of deploying the configuration is to reinstall the nodes using the nuke-em-clean command. For more information, see section 5.2.2 Upgrading Application Server and Infra Server.

Working with Snapshots

The snapshot is a saved configuration status that contains the parameter values (in a nodes.xml file) and the role tree. Software versions and configuration templates are included.

If necessary, the configuration can be restored from the snapshot. You can create snapshots separately, and a snapshot is also created during the Deploy selected operation.

Creating a Snapshot

A snapshot includes the unit configuration files, so they must be written out successfully each time before a snapshot is created.

The snapshot file is created from a directory using a packaging tool (tar). This means a single snapshot file actually consists of several files in a directory tree.

Snapshot files are stored in the /var/lib/sconf/snapshot/ directory. The file name consists of an scfg_ prefix, followed by the site name, the UTC timestamp and the user name. For example:scfg_tecnoHKI_20051215T142425Z_sam.tgz

To create a snapshot:

1. In the Snapshot menu, enter a comment for the snapshot in the Comment field.

2. Select Save.

Restoring a Configuration from a Snapshot File

Caution: Restoring the configuration from the snapshot file overwrites the current configuration, including the IP addresses and MAC addresses.

To restore a configuration from a snapshot file:

1. In the Snapshot menu, select the snapshot file on the list.

2. Select Load. When the restoring has completed, the name of the restored snapshot is displayed at the top of the window.



Importing and Exporting a Snapshot File

You can import snapshot files from your own PC to the snapshot directory on the System Configurator host machine (the System Server), or export snapshot files from the snapshot directory to your PC.

To import a snapshot file:

1. In the Snapshot menu, select Browse and select the file you want to import.

2. Select Upload.

To export a snapshot file:

1. In the Snapshot menu, select a snapshot file.

2. Select Download and download the file locally.



Appendix D: Dual Diskpack InstallationThe dual diskpack installation divides the message storage IO load to two different disk packs (see Figure 13). This type of installation requires fibre switches.

When connecting fibre cables, connect every node to every fibre switch and every disk pack controller to every fibre switch. This eliminates a single point of failure.

Figure 13 Physical fibre connections and volumes with two disk packs

The dual diskpack installation currently requires two Sun StorageTek 2450 disk packs and fible switches.

The installation procedure is almost same as with single StorageTek 2450 disk pack. To install two disk packs:

1. Install the CAM software. For instructions, see 3.5.3.2 Installing CAM Software.

2. Configure both disk packs with unique names and IP addresses, and create the data volumes. For instructions, see (see section 3.5.3.3 Configuring Sun StorageTek and Creating Data Volumes.

Note: The factory defaults are the same on both disk packs, so only one new disk pack can be connected to the network.



3. To create the file systems and database files, use the following commands:

On cms-vip:/usr/sbin/create-lvm-2450-dual-pack

After this, reboot all Infra Server nodes.

On cms-vip:/usr/sbin/create-mail-2450

On db-vip:/usr/sbin/create-mysql-2450

4. To verify that the created volumes and file systems are visible on Infra Server nodes, use the following command:ls /dev/mapper/

The following is an example output:3600a0b8000388c6d0000086448364bfd 3600a0b800038a36600000697483648b03600a0b8000388ceb000006674836489f control3600a0b8000388d340000089b48364a78 db1vg-db13600a0b8000388d340000089d48364aa4 db2vg-db13600a0b800038a3660000069548364888 mail1vg-mail1

Alternatively, you can verify the volumes using the CAM software.




Appendix E: Configuring IP Addresses for Sun StorageTek Controllers (Serial Connection)

As opposed to in-band communication that uses the fabric (fibre), the CAM software uses out-of-band communication for controlling the disk pack, that is, a TCP/IP stack instead of the fibre.

Both controllers on the disk pack must be connected to the network and on the same segment where the System Servers are. The factory default IP addresses are 192.168.128.101/24 for controller A and 192.168.128.102/24 for controller B.

Use terminal emulation to verify and configure the IP addresses for the controllers.

To verify and configure the IP addresses for the controllers:

1. To set up a terminal emulation program to connect to the serial port, select VT100 emulation.

2. Remove any modem strings from the connection profile.

3. Set up the connection profile with the following communication settings:

Data Rate: 38400

Data Bits: 8

Parity: None

Stop Bits: 1

Flow Control: None

4. To establish a connection with the serial port and access the Service Interface menu, send Break.

Note: The array serial port requires that a break is sent. Use the appropriate escape sequence for your terminal setup to send a break to the array controller. For example, on some terminals, you generate a break by pressing the Control and Break keys simultaneously.

5. When the serial port requests to synchronise with the baud rate of the terminal, press the space bar within five seconds.

The serial port confirms the established baud rate for the connection:Baud rate set to 38400



6. Send Break.

7. To access the Service Interface menu, press S.

8. Send Break to synchronise the serial port to a different terminal port rate 1.

9. When prompted, enter the serial port password (kra16wen) to access the Service Interface menu and press Enter. There is a 60 second timeout.

10. To modify the IP address configuration, enter 2 and press Enter.

11. To configure IP addressing for Ethernet port 1 on each controller, enter 1 and press Enter.

Note: The 2540 storage array only has one Ethernet port. In the 6140 storage array, Ethernet port 2 is reserved for future use.

12. To specify that you do not want use dynamic IP addressing with a DHCP server for this port, enter n and press Enter.

The current or the default IP configuration for Ethernet port 1 is displayed.

13. Enter the static IP address and optionally a subnet mask for the Ethernet port (to move to the next value, press the tab or down arrow key).

14. Enter ^D to quit the configuration and keep the changes.

Note: If you are not using DHCP IP addressing and have previously changed the gateway IP address, you must also specify a gateway IP address for the Ethernet port.

15. When prompted, confirm the specified IP addressing. The Service Interface menu is displayed.

16. To confirm the IP address configuration, enter 1 and press Enter.

17. To view the IP addressing for Ethernet port 1, enter 1 and press Enter.

The IP address configuration of Ethernet port 1 is displayed, and the Service Interface menu is displayed.

18. To quit the Service Interface menu, enter Q and press Enter.

19. If necessary, repeat the procedure for Ethernet port 2 on the controller. This is only required if, for example, port 1 is connected to one Ethernet switch and port 2 is connected to another one.

20. Repeat the procedure for the other controller.

When you have completed the IP address configuration for the Ethernet ports on both array controllers, register and configure the array. For instructions, see ref. /19/ Sun StorageTek Common Array Manager Software, Installation Guide.



Appendix F: NGM Node Installation Checklist

The full node installation instructions are given in the applicable sections of chapter 3 Installing NGM. However, if you are familiar with the installation procedure, you can use the following check list to install the nodes.

Note: The following only provides an overview of the installation for experienced users; it does not provide detailed instructions and complete commands.

Step Task Done

Install first System Server

1 Connect a keyboard and monitor to the System Server.

2 In BIOS, verify that the primary boot drive is a CD-ROM drive.

3 Insert the installation DVD.

4 Boot the System Server.

5 When the automatic installation has finished, remove the installation DVD.

6 Log in as root user with the password tecnomen.

7 Set the preliminary IP configuration using the ss-ipconf command.

In the Configure TCP/ IP window, define the IP address, Netmask and Default gateway parameters. Make sure you enter the correct settings, or the installation will be unsuccessful. Leave Primary nameserver empty.

8 Check the date and time of the System server, and if necessary, adjust them using the date command.

The node time zone must be set to UTC.

9 Create the RPM repository:

1. Insert the installation DVD and ensure there is enough disk space.

2. Copy the customer-specific .tar files to the System Server /root directory.

3. Initialise the repository using the repo-tool init command. For slower machines, this can take up to half an hour.

4. When the repository creation has finished, remove the installation DVD.

10 Log in to the System Gateway, and generate the nodes.xml file using the sgwctl createnodes command.

If necessary, use SCT to configure the nodes. For more information, see appendix C: Using SCT.

11 Copy the nodes.xml configuration file to the System Server.



Step Task Done

12 Retrieve the MAC addresses of all the other nodes (Application Servers, Infra Servers, IVR-Application Servers and Proxy Servers).

Alternative 1:

To retrieve one MAC address per unit:

1. Ensure that all other machines are powered off.

2. Retrieve the MAC addresses using the scan-nodes command.

3. For each node:

a. When prompted to boot up, power up the corresponding physical machine.

b. When the system displays the Got MAC message, power off the corresponding machine.

c. Make sure that only the first interface’s MAC address is taken.

Alternative 2:

To retrieve two MAC addresses per unit:

1. Boot each unit and write down both of the displayed MAC addresses.

2. Add the MAC addresses in the nodes.xml file in the applicable role sections as host.mac values.

13 Load the initial site network description information (nodes.xml and macs.xml) using SCT:

1. Start SCT and log in (with empty credentials).

2. In Snapshot > Restore the configuration from a snapshot file, load first the nodes.xml and then the macs.xml file.

3. In Unit configurations > Target nodes selection, make sure all nodes are selected.

4. To create the unit configuration files, select Create selected.

5. To log out, press SHIFT+Q.

14 Update the local configuration using the update-local-conf command.

15 Reboot the machine.

Note: If you made changes to the nodes.xml file manually at the site, make sure you provide the modified file to Tecnotree product development.

Install second System Server

1 Follow the instructions in steps 1-7 above.

2 Copy the configuration information from the first System Server using the ss-fetch-config command.

3 Reboot the machine.

Import node.properties and variable.properties to System Servers

1 On the System Server (ss-vip), verify that the node and role definitions in the /etc/nodes/nodes.properties are correct.



Step Task Done

2 Open the JMX console, and locate and select Tecnomen:service=systemServerPropertiesDataInit.

3 Locate the resetNodesAndVariablesBasedOnProperties method and click Invoke.

4 Restart Jboss on both System Servers.

Install Application Servers, Infra Servers, IVR- Application Servers and Proxy Servers

For each node:

1 Connect a keyboard and monitor to the node.

2 Power up the corresponding machine.

3 In BIOS, verify that the boot drive order is set in the same way as for System Server (CD-ROM, HD and network). By default, the machine boots from the network using the PXE protocol.

The machine finds the IP address and starts a fully automated installation. When the installation has been completed, the machine is rebooted.

Configure fibre switches

1 Define entries for the fibre switches in the nodes.xml file:

1. For the cms-role role, verify that there are two entries for the switch that define the IP address.

2. For each Infra Server node with a CMS role, define entries for switch port allocation.

2 Log in to each fibre switch using either a) a serial port or b) an Ethernet port.

a) 1. Verify that the serial port values are correct.

2. Use a null-modem F/F DB9 cable to connect to the RS-232 port on the switch (admin/password).

3. To define the fibre switch’s IP address, go to step 3 below.

b) 1. Log in to System Server and set up the temporary interface:ifconfig bond0:5 ipaddress 10.0.0.2 netmask 255.255.255.0 up

2. Use Telnet to connect to the address 10.0.0.1 (admin/password).

3. To define the fibre switch’s IP address, go to step 3 below.

3 Enter the configuration mode:admin beginset setup system

4 Define the fibre switch IP addressing, and set the NTP server and remote log host to point to the System Server VIP address (ss-vip).

5 To save and activate the settings, enter y and press Enter.

6 Repeat the procedure for the other fibre switch (using a different IP address).



Step Task Done

Initialise storage

Warning! All the persistent data will be destroyed (subscriber and service settings, voice mails, greetings, and so on).

Initialise Storage with DotHill SANnet II 200 or Sun StorEdge 3510

1 On the System Server, log in to cms-vip.

2 Configure the disks and create the logical drives:

On an RMS server, use the initstorage –c dothill command.

On a Sun server, use the initstorage –c sun command.

3 Log out of cms-vip, and log in to db-vip.

4 To create the file systems and insert the initial data in the database tables, use the initstorage –i mysql command. Deploying the database can take around 20 minutes.

5 Log out of db-vip, and log in to cms-vip.

6 To create the file systems for the Courier mail server, use the initstorage –i mail command.

7 Reboot all Infra Servers.

8 When the Infra Servers are up, reboot all Application Servers.

Initialise Storage with Sun StorageTek 2540 or 6140

Note: For a dual pack installation, see instructions in appendix D: Dual Diskpack Installation.

1 Install CAM software:

1. Log in to ss-vip.

2. In /usr/share/cam, run the CAM installation script:./install_cam.sh

You can access CAM in https://<system server IP>:6789 (root/Tecnomen).

2 Configure Sun StorageTek and create the data volumes:

1. Configure the Sun StorageTek and create the volumes:/usr/share/cam/config-2450 –n <name> –a <IP a> –b <IP b> –g <gateway> –m <netmask>

2. Reboot all Infra Server nodes, and log in to cms-vip.

3. Verify that the system sees all the volumes on the storage array:ls /dev/mapper/



Step Task Done

3 Create the file systems and the database files:

1. Create the file systems and database files:

On cms-vip: /usr/sbin/create-lvm-2450. After this, reboot all Infra Server nodes.

On cms-vip: /usr/sbin/create-mail-2450

On db-vip: /usr/sbin/create-mysql-2450

2. Verify that the system sees all the volumes on the storage array:ls /dev/mapper/


Install data set

1 On the System Server, copy the the customer-specific .tar file to the Infra Server /root directory.

2 Log in to the Infra Server where you copied the .tar file.

3 Create a temporary directory in the /root directory on the Infra Server.

4 Go to the temporary directory, and untar the .tar file to that directory.

5 To verify the dbinit package installed on the Infra Server, use the following command:rpm -qa |grep dbinit

6 Uninstall the existing dbinit package using, for example, the yum remove dbinit command.

7 Install the new dbinit package using, for example, the following command:yum install dbinit-<version number>-<build number>.i386.rpm

8 On the same Infra Server, remove the initial data from all the unit databases using the following commands:cd /usr/share/dbinitant nuke -Dhosts=<comma-separated list of hosts>

9 To create the initial database schema and insert the initial data into the tables, use the following commands (for multiple hosts):ant schema -Dhosts=<comma-separated list of hosts>ant data -Dhosts=<comma-separated list of hosts>

10 Reboot all Application Servers one by one.

11 On the System Server (ss-vip), verify that the node and role definitions in the /etc/nodes/nodes.properties are correct.

12 Open the JMX console, and locate and select Tecnomen:service=systemServerPropertiesDataInit.

13 Locate the resetNodesAndVariablesBasedOnProperties method and click Invoke.

14 Restart Jboss on both System Servers.



Step Task Done

Install TUI resources and End User Web Interface to Infra Server

1 Go to the Infra Server to which you copied the .tar file.

2 Go to the repository, and unzip the .zip file to the repository from the temporary directory you created earlier.

The contents are unzipped to CoS-specific subdirectories.

5 Go to the /usr/db/mail directory, and change ownership for the whole repository.

Install prompts to Infra Server

1 Copy the prompt .tar.gz package to the Infra Server /root/ directory.

2 Go to the repository, and untar the .tar.gz file to the repository.

3 Go to the /usr/db/mail directory, and change ownership for the whole repository.



Appendix G: CAM Software Installation Procedure

The following is an example of the CAM installation procedure as instructed in section 3.5.3.2 Installing CAM Software:Extracting installation files...

Initializing Wizard........ Launching InstallShield Wizard........

------------------------------------------------------------------------------- Sun StorageTek(TM) Common Array Manager 6.4.1

The InstallShield Wizard will install Sun StorageTek(TM) Common Array Manager on your computer.

To continue, choose Next.

Sun StorageTek(TM) Common Array Manager 6.4.1 Sun Microsystems, Inc. http://www.sun.com

Press 1 for Next, 3 to Cancel or 5 to Redisplay [1]


Please read the following license agreement carefully.

Sun StorageTek(TM) Common Array Manager

Copyright (C) 2009 Sun Microsystems, Inc. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and


http://www.sun.com/


without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. This distribution may include materials developed by third parties. Portions may be derived from Berkeley BSD systems, licensed from U. of CA. Sun, Sun Microsystems, the Sun logo, Java, Solaris and Sun StorageTek Common Array Manager are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Please choose from the following options: [ ] 1 - I accept the terms of the license agreement. [X] 2 - I do not accept the terms of the license agreement.

To select an item enter its number, or 0 when you are finished: [0] 1

[X] 1 - I accept the terms of the license agreement. [ ] 2 - I do not accept the terms of the license agreement.

To select an item enter its number, or 0 when you are finished: [0]

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]


Choose the installation type that best suits your needs.

[X] 1 - Typical The program will be installed with the suggested configuration. Recommended for most users.


http://www.sun.com/patents


[ ] 2 - Custom The program will be installed with the features you choose. Recommended for advanced users.

Select the number corresponding to the type of install you would like: [0]

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]

------------------------------------------------------------------------------- Checking current system ...

|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||||||||| ------------------------------------------------------------------------------- Sun StorageTek(TM) Common Array Manager 6.4.1

Software To Be Installed: Full Install * Management Host Software * Data Host Proxy Agent * Administrator Host CLI Client

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] Preparing for installation ...

Pre Uninstall Old Action ...

Removing old features ...


Installing Sun StorageTek(TM) Common Array Manager 6.4.1. Please wait...

|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% ||||||||||||||||||||||||||||||||||||||||||||||||||



Installing Java 2 Standard Edition


|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||||||||| ------------------------------------------------------------------------------- Sun StorageTek(TM) Host Software Installation Summary

View results: Info: Installation success. The following have been installed:

Management Host Software, Data Host Proxy Agent, and Administrator Host CLI Client. To access the Browser User Interface point a browser at: https://installation_host:6789 The logs may be found in /var/opt/cam/

Press 3 to Finish or 5 to Redisplay [3]


https://installation_host:6789/

Documents

Installation Guide - Tecnomen NGM 5.1.3 - IG - 6000700_11