8DG42778NAAAR11.2_V1_1350 OMS Installation Guide, 11.2, Issue 1

Optical Management System

Alcatel-Lucent 1350OMS

1350OMS11.2

Installation Guide8DG 42778 NAAA

Edition 01April 2014

Status: Released

All rights reserved.Passing on and copying of this document,

use and communication of its contents is not permittedwithout written authorization from Alcatel-Lucent.

8DG 42778 NAAA Edition 01

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.

All other trademarks are the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright ©2013 Alcatel-Lucent

TABLE OF CONTENTS

TABLE OF CONTENTS ................................................................................................................... 1

LIST OF FIGURES ......................................................................................................................... 1

LIST OF TABLES ........................................................................................................................... 1

PREFACE......................................................................................................................................... 3Preliminary Information.............................................................................................................. 3Applicability................................................................................................................................. 4Scope ........................................................................................................................................... 4History.......................................................................................................................................... 5Related Documents .................................................................................................................... 6Handbook Structure ................................................................................................................... 8General on Customer Documentation ...................................................................................... 9

1 INTRODUCTION .......................................................................................................................... 131.1 Installation Steps ................................................................................................................. 13

1.1.1 Red Hat Enterprise Linux Server installation .................................................................. 131.1.2 1350OMS Application Virtual Machine Deployment. ...................................................... 13

1.2 Registered Trademarks ....................................................................................................... 141.3 Conventions ......................................................................................................................... 14

2 INSTALL VIRTUAL MACHINE HOST SERVER.......................................................................... 152.1 Preparatory activities .......................................................................................................... 15

2.1.1 Qualified HP ProLiantTM Hardware Configuration ......................................................... 162.2 Installation Requirements ................................................................................................... 16

2.2.1 Requested Network Equipment ...................................................................................... 162.2.2 Console Required ........................................................................................................... 162.2.3 Configuration info............................................................................................................ 172.2.4 Software Media............................................................................................................... 172.2.5 1350OMS Project Planning ........................................................................................... 182.2.6 1350OMS License .......................................................................................................... 18

2.3 Operating System Installation on Host Server.................................................................. 192.3.1 Disk usage ...................................................................................................................... 192.3.2 Boot HP ProLiant server ................................................................................................. 202.3.3 RHEL Server First Boot and License server set-up........................................................ 232.3.4 Retrieve and install Virtual Machine Tools ...................................................................... 302.3.5 Configuring the host server as the Poseidon and GoGlobal License Server. ................. 312.3.6 Retrieving Virtual Disks and Creating a Repository ........................................................ 32

3 1350OMS VIRTUAL MACHINE SETUP....................................................................................... 343.1 Access 1350OMS configuration Tool................................................................................. 35

3.1.1 Configuring Network Bridges .......................................................................................... 373.1.2 Create the R11.2 configuration ....................................................................................... 403.1.3 Configuration editing....................................................................................................... 44

3.2 Automatic Install Alcatel-Lucent Software ........................................................................ 633.3 Special Installation Instruction........................................................................................... 63

3.3.1 1350OMS-HA configuration............................................................................................ 633.3.2 Multi Host configuration .................................................................................................. 63

3.4 Post Installation instructions (execute on VMs) ............................................................... 643.4.1 System Configuration ..................................................................................................... 64

3.5 Post Installation W/A ........................................................................................................... 643.5.1 1350OMS OIS applications down................................................................................... 64

Installation Guide

TABLE OF CONTENTS

Alcatel-Lucent 1350OMS 11.2

8DG 42778 NAAA Edition 01 1/126

3.5.2 MAP management .......................................................................................................... 653.6 Hardware Replacement / Migration .................................................................................... 65

3.6.1 export configuration from bench WITH direct connection with the new host .................. 653.6.2 export configuration from bench WITHOUT direct connection with the new host .......... 66

4 WEB DESKTOP AND CLIENT PC............................................................................................... 694.1 Web Desktop ........................................................................................................................ 69

4.1.1 Connection to Web Desktop ........................................................................................... 694.2 Client PC............................................................................................................................... 71

4.2.1 Pagefile configuration review.......................................................................................... 714.2.2 Host Configuration .......................................................................................................... 73

4.3 Troubleshooting................................................................................................................... 744.3.1 WebEnabler cache.......................................................................................................... 744.3.2 Manual start of WDM-mediator ....................................................................................... 744.3.3 Manual start of ces-mediator .......................................................................................... 744.3.4 Manual start of 1350OMS PKT CESSDH....................................................................... 744.3.5 EML domains cannot be displayed................................................................................. 744.3.6 hosts file configuration for SMF usage............................................................................ 744.3.7 adjust file format modified on wrong depot transfer........................................................ 744.3.8 Service not starting on Presentation ............................................................................... 75

5 POST INSTALLATION................................................................................................................. 775.1 Add New 1350 OMS “EML Master”/ “OIS Master” / ”Presentation” Virtual Machine ... 775.2 Addition 1350 OMS HA........................................................................................................ 78

5.2.1 Add and configure the DRC instances............................................................................ 785.2.2 Assign the DRC VMs to host .......................................................................................... 785.2.3 Sync bench configuration ............................................................................................... 785.2.4 DRC installation .............................................................................................................. 795.2.5 1350OMS HA installation and configuration on NOC ..................................................... 795.2.6 1350OMS HA startup and checks................................................................................... 79

5.3 Change “hostname” procedure.......................................................................................... 805.3.1 Change “hostname” in a NON 1350OMS HA context .................................................... 805.3.2 Change “hostname” in a 1350OMS HA context ............................................................. 80

5.4 Addition of New 1350 OMS optional components (CPB, ISN, IOO) ................................ 815.5 Integration - Federation....................................................................................................... 82

6 TROUBLESHOOTING.................................................................................................................. 836.1 Identify a Failure Condition................................................................................................. 836.2 Recoverable Faults .............................................................................................................. 836.3 Device Full ............................................................................................................................ 84

6.3.1 Device full ....................................................................................................................... 846.4 Generating a SOSReport..................................................................................................... 85

ABBREVIATIONS ............................................................................................................................ 123

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 125

Installation Guide

TABLE OF CONTENTS


8DG 42778 NAAA Edition 012/126

LIST OF FIGURES

Figure 1. RHEL 6 initial boot from local DVD.................................................................................... 20Figure 2. RHEL 6 Boot options (example) ........................................................................................ 21Figure 3. RHEL 6 Manual disk configuration. ................................................................................... 22Figure 4. RHEL 6 File system review window................................................................................... 22Figure 5. RHEL 6 Operating System installation starting.................................................................. 23Figure 6. RHEL Configuration - Accept the License Agreement....................................................... 24Figure 7. RHEL Configuration - Keyboard Selection ........................................................................ 24Figure 8. RHEL Configuration - Root Password definition................................................................ 25Figure 9. RHEL Configuration - Timezone selection......................................................................... 25Figure 10. Setting Date, Time and Timezone ................................................................................... 26Figure 11. RHEL Configuration - Kdump configuration..................................................................... 26Figure 12. RHEL Configuration - Kdump required reboot confirmation ............................................ 27Figure 13. RHEL Configuration - Final reboot................................................................................... 27Figure 14. Red Hat root Login warning message ............................................................................. 28Figure 15. Date and Time properties dialog...................................................................................... 29Figure 16. NTP server list tab ........................................................................................................... 29Figure 17. Adding a NTP server ....................................................................................................... 29Figure 18. RHEL NTP server confirmation ....................................................................................... 30Figure 19. RHEL NTP using local time source ................................................................................. 30Figure 20. Connection warning message ......................................................................................... 35Figure 21. Instances configuration entry page.................................................................................. 36Figure 22. Version selection screen.................................................................................................. 36Figure 23. Setup procedure main menu ........................................................................................... 36Figure 24. Virtual Bridge administration main page .......................................................................... 38Figure 25. Virtual Bridge Creation successful ................................................................................... 38Figure 26. Virtual Bridge Administration page with one bridge created ............................................ 39Figure 27. Virtual Bridge administration: Delete bridge confirm request........................................... 39Figure 28. Virtual bridge administration - Modifying existing bridge.................................................. 40Figure 29. Setup procedure main menu ........................................................................................... 40Figure 30. Newly created empty bench - initial view......................................................................... 41Figure 31. Add new Linux host ......................................................................................................... 42Figure 32. Import configuration from file (define configuration name) .............................................. 43Figure 33. Import configuration from file (upload configuration file) .................................................. 43Figure 34. Import configuration from file (upload configuration file - green arrow button) ................ 43Figure 35. Import configuration from file (define configuration name) .............................................. 43Figure 36. Import configuration from file (upload configuration file) .................................................. 44Figure 37. Import configuration from file (upload configuration file - green arrow button) ................ 44Figure 38. Adding a Master instance to the installation scheme....................................................... 45Figure 39. Master instance: Specifying Options and networking informations.................................. 45Figure 40. EML-specific networking settings .................................................................................... 46Figure 41. EML-specific networking settings with two supervision areas defined ............................ 47Figure 42. managed NE type/release selection: initial view.............................................................. 47Figure 43. managed NE type/release selection: selection procedure............................................... 48Figure 44. NE type/releases selected, Set NE qty button enabled ................................................... 48Figure 45. specifying NE quantities .................................................................................................. 49Figure 46. Master Instance configured (in this figure EML master instance configured). ................. 49Figure 47. Master Instance configured (in this figure a EML master instance fully configured)........ 50Figure 48. HA configuration: Creating a SDH master HA pair .......................................................... 51Figure 49. HA configuration: EML master HA pair created............................................................... 52Figure 50. Editing EML master HA spare instance: step 1 ............................................................... 53Figure 51. Editing EML master HA spare instance: step 2 ............................................................... 53

Installation Guide

List of Figures



Figure 52. Bench with non-HA EML master instance and a HA pair for EML master (details) ......... 54Figure 53. Bench with non-HA EML master instance and a HA pair for EML master (bench view) . 55Figure 54. Adding a Presentation instance to the installation scheme.............................................. 55Figure 55. example of bench with Presentation (orange icon) configured........................................ 56Figure 56. example of bench with Presentation (orange icon) and EML Master configured ........... 57Figure 57. Creating a Presentation instance in HA context .............................................................. 58Figure 58. Bench with HA Presentation instances pair created ........................................................ 58Figure 59. Bench with HA Presentation instances pair created (details) .......................................... 59Figure 60. Global settings section..................................................................................................... 60Figure 61. Initial SSH VMs password rules....................................................................................... 61Figure 62. Configuration completed - configuration writing............................................................... 62Figure 63. Web Desktop Login ......................................................................................................... 70Figure 64. Web Desktop password ................................................................................................... 70Figure 65. Connecting keyboard, monitor and mouse for ILO configuration. ................................... 88Figure 66. Server start-up screen. .................................................................................................... 89Figure 67. Initial ILO Screen ............................................................................................................. 90Figure 68. ILO Setup: Network menu ............................................................................................... 91Figure 69. ILO Setup: NIC Setup ...................................................................................................... 91Figure 70. ILO Setup: User menu ..................................................................................................... 92Figure 71. ILO Setup: User list.......................................................................................................... 93Figure 72. ILO Setup: editing user details......................................................................................... 94Figure 73. ILO Setup: exiting the procedure and completing configuration ...................................... 94Figure 74. ILO Setup: ILO reset after configuration save ................................................................. 95Figure 75. Pull-out sticker with factory-preset ILO password............................................................ 96Figure 76. Typical Main Menu of the Smart Array Configuration Utility ............................................ 98Figure 77. GoGlobal-UX Logo .......................................................................................................... 101Figure 78. GraphOn License WEB Page .......................................................................................... 106Figure 79. GraphOn License WEB Page - Software Agreement ...................................................... 107Figure 80. GraphOn Info request window for Single server.............................................................. 107Figure 81. GraphOn Info request window for Three Redundant servers .......................................... 108Figure 82. GraphOn License WEB Page - License Output Example................................................ 109

Installation Guide

List of Figures



LIST OF TABLES

Table 1. Handbooks related to the specific software application ...................................................... 6Table 2. Related Handbooks............................................................................................................. 7Table 3. List of HP ProLiantTM supported hardware components.................................................... 16Table 4. 1350OMS Network Management composition table ........................................................... 99Table 5. Three Server Redundant License Form .............................................................................. 117Table 6. Single License Form............................................................................................................ 118

Installation Guide

List of Tables



Installation Guide

List of Tables



PREFACE

Preliminary Information

WARNING

ALCATEL-LUCENT makes no warranty of any kind with regards to this manual, and specifically dis-claims the implied warranties of merchantability and fitness for a particular purpose. ALCATEL-LUCENT will not be liable for errors contained herein or for damages, whether direct, indirect, con-sequential, incidental, or special, in connection with the furnishing, performance, or use of this mate-rial.

NOTICE

The product specification and/or performance levels contained in this document are for information purposes only and are subject to change without notice. They do not represent any obligation on the part of ALCATEL-LUCENT.

COPYRIGHT NOTIFICATION

The technical information of this manual is the property of ALCATEL-LUCENT and must not be cop-ied, reproduced or disclosed to a third party without written consent.

TECHNICAL SUPPORT

Please contact your Local Alcatel-Lucent Technical Assistance Center for questions reffered to the information contained in this document.

To send your comments about this handbook please follow the indication on Customer Documen-tation Feedback.

Installation Guide

Preface



Applicability

This handbook applies to following product–releases:

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONSHandbooks relevant to software applications (typically the Operator's Handbooks) are not mod-ified unless the new software “version” distributed to Customers implies man-machine interface changes or in case of slight modifications not affecting the understanding of the explained pro-cedures.Moreover, should the screen prints included in the handbook contain the product–release's "version" marking, they are not replaced in the handbooks related to a subsequent version, if the screen contents are unchanged.

Scope

This document describes how to install and configure an X86 computer system in order to allow the correct usage of the Alcatel-Lucent 1350OOMS NMS application Software.

PRODUCT Part Number

1350OMS 8DG 41764 AAAA

PRODUCT RELEASE VERSION (N.B.) Part Number

1350OMS 11.2 11.2 8DG 42738 AAAA

Installation Guide

Preface



History

EDITION DATE DESCRIPTIONS

Ed. 01 April 2014 1350OMS 11.2 Installation GuideAligned to 11.2 DR4

Based on 1350 OMS build 11.2.0.79 for Linux Red Hat

Installation Guide

Preface



Related Documents

The standard Customer Documentation in the English language for the equipment whose product–release–version is stated in “Applicability” on page 4 consists of the following handbooks:

Table 1. Handbooks related to the specific software application

The list of handbooks given here below is valid on the issue date of this Handbook and can be changed without any obligation for ALCATEL to update it in this Handbook.

Some of the handbooks listed here below may not be available on the issue date of this Handbook.

REF HANDBOOK Part Number Notes

[1]1350OMS Installation Guide 8DG 42778 NAAA

THISHANDBOOK

[2] 1350OMS Administration Guide #1Common Tools and Processes

8DG 42778 LAAA

[3] 1350OMS Administration Guide #2 Common GUI Functions

8DG 42778 MAAA

[4] 1350OMS Upgrade Installation Guide 8DG 42778 TAAA

Installation Guide

Preface



Table 2. Related Handbooks

REF HANDBOOK Part Number Notes

[5] 1350OMS R11.2 GETTING STARTED Guide 8DG 42778 AAAA

[6] 1350OMS R11.2 Platform Guide 8DG 42778 BAAA

[7] 1350OMS R11.2 SDH Guide 8DG 42778 CAAA

[8] 1350OMS R11.2 PKT Guide 8DG 42778 DAAA

[9] 1350OMS R11.2 Service Assurance Guide 8DG 42778 FAAA

[10] 1350OMS R11.2 HA Guide 8DG 42778 GAAA

[11] 1350OMS R11.2 OI Guide 8DG 42778 HAAA

[12] 1350OMS R11.2 OI NBI Guide 8DG 42778 JAAA

[13] 1350OMS R11.2 CLI Reference 8DG 42778 KAAA

[14] 1350OMS R11.2 OTN Guide 8DG 42778 QAAA

[15] 1350OMS R11.2 Electronic Library 8DG 42778 SAAA

Installation Guide

Preface



Handbook Structure

This handbook has been edited according to the Alcatel-Lucent standardized “drawing-up guides" com-plying with such suggestion.

This handbook is divided into the main topics described in the table of contents:

The technical contents of the document is mainly divided into two parts.

PREFACE: It contains general information as preliminary information, safety recommendation, handbook scope, history, related documents. Furthermore, it describes the handbook structure and the customer documentation.

Introduction The requirements, initial and restriction are briefly described.

Installation & Customization This chapter shows how to install and customize Alcatel-Lucent Network Management Subsystems on a X86 system.

ClientPCConfig This chapter describes a personal computer minimum and recom-mended machine requirements.

Troubleshooting This chapter shown how to solve some trouble can occur during the installation, and how to proceed when possible.

Appendix A In this appendix some system tips are show.

Appendix B In this appendix NMS and NMC specific data are described.

Appendix C In this appendix GOGLOBAL-UX installation and configuration is described.

Appendix D In this appendix Poseidon installation and configuration is described.

ABBREVIATIONS: Not applicable

INDEX Not applicable

CUSTOMER DOCUMENTA-TION FEEDBACK

It contains info regarding customer opinions collection about this documentation.

Installation Guide

Preface



General on Customer Documentation

Note: when Network Management Operator’s Handbook is made, other handbooks can refer to it.

A "product" is defined by the network hierarchical level where it can be inserted and by the whole of per-formance and services for which it is meant.A "product" evolves through successive "product–releases" which are the real products marketed for their delivery at a certain "product–release" availability date.

So, a "product-release" defines a set of hardware components and a software package which, as a whole, identify the possible network applications and the equipment performance which the specific "product–release" has been designed, engineered and marketed for.

In some cases a "product–release" has further development steps, named "versions", that are born to improve or add some performance (mainly software) with respect to the previous version, or for bug fixing purposes.

A "product–release" has its own standard Customer Documentation, composed by one or more hand-books.

A new "version" of a "product–release" may or may not produce a change in the status of the Customer Documentation set, as described in “Handbook Updating” following part.

Handbook supply to Customers

Handbooks are not automatically delivered together with the equipment they refer to.The number of handbooks per type to be supplied must be decided at contract level.

Aims of standard Customer Documentation

Standard Customer Documentation, referred to hereafter, must be always meant as plant–independent.Plant–dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far as contents, formats and supply conditions are concerned (plant–dependent documentation is not described here).

Standard hardware and software documentation is meant to give the Customer personnel the possibility and the information necessary for installing, commissioning, operating and maintaining the equipment according to Alcatel-Lucent Laboratory design choices.In particular: the contents of the handbooks associated to the software applications focus on the expla-nation of the man–machine interface and of the operating procedures allowed by it; maintenance is described down to faulty PCB location and replacement.

Consequently, no supply to the Customers of design documentation (like PCB hardware design and pro-duction documents and files, software source programs, programming tools, etc.) is envisaged.

The handbooks concerning hardware (usually the "Technical Handbook") and software (usually the "Operator's Handbook") are kept separate in that any product changes do not necessarily concern their contents.

For example, only the Technical Handbook might be revised because of hardware configuration changes (e.g., replacing a unit with one having different P/N but the same function).On the other hand, the Operator's Handbook is updated because of a new software version but which does not concern the Technical Handbook as long as it does not imply hardware modifications.However, both types of handbooks can be updated to improve contents, correct mistakes, etc..

Installation Guide

Preface



Handbook Updating

The handbooks associated to the "product-release" are listed in “” on page 5.

Each handbook is identified by: – the name of the "product–release" (and "version" when the handbook is applicable to the versions

starting from it, but not to the previous ones), – the handbook name, – the handbook Part Number, – the handbook edition (usually first edition=01),– the handbook issue date. The date on the handbook does not refer to the date of print but to the date

on which the handbook source file has been completed and released for the production.

Changes introduced in the same product–release (same handbook P/N)

The edition and date of issue might change on future handbook versions for the following reasons:

– only the date changes (pointed out in the of Contents) when modifications are made to the editorial system not changing the technical contents of the handbook.

– the edition, hence the date, is changed because modifications made concern technical contents. In this case:

• the changes with respect to the previous edition are listed in History on page 5.;• in affected chapters, revision bars on the left of the page indicate modifications in text and draw-

ings.

Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of a version character (e.g. from Ed.02 to Ed.02A). Version character can be used for draft or proposal edi-tions.

NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONSHandbooks relevant to software applications (typically the Operator's Handbooks) are not modified unless the new software "version" distributed to Customers implies man-machine interface changes or in case of slight modifications not affecting the understanding of the explained procedures.

Moreover, should the screen prints included in the handbook contain the product–release's "version" marking, they are not replaced in the handbooks related to a subsequent version, if the screen contents are unchanged.

Supplying updated handbooks to Customers

Supplying updated handbooks to Customers who have already received previous issues is submitted to commercial criteria.By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue (sup-plying errata-corrige sheets is not envisaged).

Changes due to new product version

A new product version changes the handbook P/N and the edition starts from 01. In this case the modified parts of the handbook are not listed.

Installation Guide

Preface



Customer documentation on CD-ROM

In the following by 'CD-ROM' it is meant 'Customer Documentation on CD-ROM'

Contents, creation and production of a CD-ROM

In most cases, a CD-ROM contains in read-only eletronic format the documentation of one product-release(-version) and for a certain language.In some other cases, the same CD-ROM can contain the documentation of different product-release(-ver-sion)s for a certain language.

As a general rule:

– CD-ROMs for Network Management products do not contain:

• the Installation Guides

• the documentation of system optional features that Customers could not buy from Alcatel-Lucent together with the main applicative SW.

– CD-ROMs for Network Elements products do not contain:

• the documentation of system optional features (e.g. System Installation Handbooks related to racks that Customers could not buy from Alcatel-Lucent together with the main equipment).

A CD-ROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and hyperlinks make the navigation easier. No additional information is added to each handbook, so that the documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.

The files processed in this way are added to files/images for managing purpose and a master CD-ROM is recorded.

Sui checks are made in order to have a virus-free product.

After a complete functional check, the CD-ROM image is electronically transferred to the archive of the Production Department, so that the CD-ROM can be produced and delivered to Customers.

Use of the CD-ROM

The CD-ROM can be used both in PC and Unix WS environments.

The CD-ROM starts automatically with autorun and hyperlinks from the opened “Index" document permit to visualize the .pdf handbooksOther hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.

In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been installed on the platform.The CD-ROM doesn't contain the Adobe Acrobat Reader program. The Customer is in charge of getting and installing it.ReadMe info is present on the CD-ROM to this purpose.

Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included in the tool, and to print selected parts of the documentation through a local printer.

Installation Guide

Preface



CD-ROM identification

Each CD-ROM is identified:

1) by external identifiers, that are printed on the CD-ROM upper surface:– the name of the "product-release(s)" (and "version" if applicable) – a writing indicating the language(s),– the CD-ROM Part Number), – the CD-ROM edition (usually first edition=01)

2) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose collection and processing the CD-ROM itself has been created.

CD-ROM updating

The list of source handbook/document P/Ns-editions indicated in previous para. point 2) , in association with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-Information-System as a structured list.Whenever a new edition of any of such handbooks/documents is released in the Alcatel-Lucent archive system, a check in the Alcatel-Information-System is made to identify the list of CD-ROMs that must be updated to include the new editions of these handbooks/documents.This causes the planning and creation of a new edition of the CD-ROM.

Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks com-posing the collection

Installation Guide

Preface



1 Introduction

This document describes how to install Alcatel-Lucent 1350OMS on a HP ProLiantTM server system devoted to this purpose. The initial installation is foreseen for machine where the operating system is not installed, it includes Red Hat Enterprise Linux 6 (RHEL6 in the following), the server will host 1350OMS applications running within Virtual Machines.

1.1 Installation Steps

1350OMS 11.2 installation on RHEL consists of two main activities:

1) Red Hat Enterprise Linux Server installation.2) 1350OMS Application Virtual Machine Deployment.

1.1.1 Red Hat Enterprise Linux Server installation

The precondition is that the server is physically installed, that RAID setup is done and (optional but rec-ommended) ILO setup is done. For instructions about these hardware model-dependent phases refer to HP Proliant server documentation. See Appendix A for notes on RAID setup.

RHEL6 operating system installation is done by booting from the installation media and following the on-screen instructions. The hard disk will be automatically formatted to host virtual machines.

At the end of the operating system installation, some packages must be installed to enable virtual machine deployment. Actual Virtual Machine deployment will then require the appropriate set of application virtual disk files.

1.1.2 1350OMS Application Virtual Machine Deployment.

When the RHEL Host will be installed and ready to use, you’ll be able to deploy Alcatel-Lucent 1350OMS application as set of Virtual Appliances, by accessing the Web based deploy procedure, configuring net-work bridges and describing the set of Virtual Appliances to be deployed.

1.1.2.1 What is a 1350OMS Virtual Appliance

A 1350 OMS Virtual Appliance consists in a set of files that contain the XML Virtual Machine description and the Virtual Disk Images that compose the virtual machine. These files are distributed on appropriate removable media.

1.1.2.2 Virtual Machine Deployer

To simplify Virtual Appliances transformation in Virtual Machines Alcatel-Lucent provides a tool. VMDe-ployer tool is a Web interface to easily describe and create virtual machines for 1350OMS applications.

1.1.2.3 Alcatel-Lucent 1350OMS Virtual Appliance

Alcatel-Lucent 1350OMS applications for RHEL will be distributed as Virtual Appliance, that means the installation of this Application will be not performed like a classic server, but both Operating System and Application will be provided as a preinstalled Virtual Machine requiring only final configuration to be ready for operation.

Installation Guide

Introduction



1.2 Registered Trademarks– HP® is a registered trademark of Hewlett-Packard Corporation.

– HP ProLiant® are trademarks of Hewlett-Packard Corporation.

– Red Hat®, Red Hat Enterprise Linux are trademarks of Red Hat, Inc.

– ORACLE® is a registered trademark of Oracle Corporation.

– MySQL®is a registered trademark of Oracle Corporation.

1.3 Conventions

The following conventions are used in this manual:

[Enter] A key name is shown between square brackets to indicate that you press a named key on the keyboard.

courier Courier type is uses to indicate the output produced by the system or data that you can find.

bold italic Bold italic letters indicate informations that you must enter from the keyboard.

<data> Data shown between angle brackets means that these data depending by the particular instance of the system. It must be substituted with the correct data.

# Actions must be performed as root.

..,sys,root # Actions must be performed as root.

..,$ Actions must be performed as normal user (not as root).

..,oracle> Actions must be performed as oracle user.

SQL> Actions must be performed in SQL utility.

Installation Guide

Introduction



2 Install Virtual Machine Host server

This chapter shows how to install Red Hat Enterprise LinuxTM on the server, enabling it to host the virtual appliances containing the Alcatel-Lucent Network Management Subsystems.

VERY IMPORTANT!Before proceed in the installation, upgrade or migration you have to visit the Optics Technical Excellence Center WEB site (http://tec-optics.web.alcatel-lucent.com/) and Patch Centre for NavisTM Optical Management System (http://tms.uk.lucent.com/PS/), looking for additional installation notes.

The installation done by following the information provided by this chapter will cause the complete deletion of involved hard disk contents.

The chapter contents:

– Preparatory Activity

– Red Hat Enterprise LinuxTM Operating System Installation for Virtual Machine support.

– Red Hat Enterprise LinuxTM Configuration

2.1 Preparatory activities

Before proceeding with Red Hat Enterprise LinuxTM installation it is advisable to prepare all the hardware and software components for the installation.

– Check the system hardware configuration– Check the cable connections– Check the availability of Operating System Configuration information

Installation Guide

Install Virtual Machine Host server



2.1.1 Qualified HP ProLiantTM Hardware Configuration

This paragraph shows the HP hardware where the 1350OMS-MW_OS has been validated. The correct behavior of the procedure on different hardware is not guarantee.

Table 3. List of HP ProLiantTM supported hardware components

2.2 Installation Requirements

Hereafter the bill of materials requested to be able to carry on installation.

2.2.1 Requested Network Equipment

The installation of a Red Hat Enterprise LinuxTM can not be carried on without connecting the server to a Local Area Network (LAN). The minimum equipment required on the server is:

1) Three BT LAN cables.2) Three Local Area Network plug or a stand alone Ethernet Hub or Switch with three or more ports

The installation can not be performed if the LAN card it is not connected to the LAN plug or to a stand alone Ethernet Hub.Unstable LAN connectivity can cause serious trouble.

2.2.2 Console Required

To be able to perform Alcatel-Lucent TMN systems installation, you have to be able to perform some

actions by using HP ProLiantTM server console.

The most common way to access the server console is via VGA video, keyboard and mouse (either locally connected or remotized using KVM tools).

The console can be also accessed over the network via Integrated Lights-Out (ILO) on board adminis-tration processor. (In this case, the “ILO Advanced” License is required). ILO in turn can be accessed only after its networking settings are configured. Networking configuration can either occur automatically, with dynamic address assigned via DHCP-DNS, or manually, with static address.

N.B. If ILO is to be used to access the console, and there is no DHCP-DNS facility in the customer network, then ILO networking has to be manually configured using VGA video, keyboard and mouse (or KVM tools) by entering the ILO setup menu during server start-up sequence. This requires to press the appropriate key at the right time (usually F8 but it may depend on the server model; you must check HP server documentation to find out the right procedure for the specific server model used)

HP ProLiant Model

DL380 G7

DL580 G7

DL380 GEN8

Installation Guide




2.2.3 Configuration info

During Red Hat Enterprise LinuxTM installation the following information will be requested:– Host name– Network configuration info (IP Address/Netmask/Gateway)– Keyboard selection– Root password definition– DNS configuration info when foreseen.– Time-zone– NTP servers

During virtual machine deployment the following informantion will be required:– At server level:

• Bridge name definition• Other NIC IP address configuration.

– At virtual machine level:• Virtual machine name prefix• Virtual machine host name• Virtual machine type• Virtual machine IP addresses• GOGlobal License server.• Alcatel-Lucent License server.

It is advisable prepare them in advance for all the server and virtual machine involved.

2.2.4 Software Media

To install a HP ProLiantTM server you must have the software for host operating system and guest appli-cation virtual machines.

Hereafter the list of Alcatel-Lucent DVD label and part numbers of all requested items for this release:

DVD Label Disk set description DVD Part Numbers

SWP-1350OMS-MW_OS-BH-V11.0.0.1.0-LX 1 disk (Bootable for Host OS installation)

8DG 42721 AAAA

SWP-1350OMS-MW_OS-VD-V11.2.0-LX 3 disks (Virtual Disk files for Guest OS and plat-form, plus RPM pack-ages to enable Virtual Machine installation)

8DG 42810 AAAA

SWP-1350OMS-V11.2.0-LX 4 disks (Virtual Disk files for 1350OMS Applica-

tions)

8DG 42812 AAAA

Installation Guide




2.2.5 1350OMS Project Planning

Before proceeding with system deployment it is strongly recommended to define in detail the IP address-ing plan for both server and virtual machines.

All the server host Network Interface Cards (NIC) that have to be used for communication have to be con-figured with an IP address, this IP address will be used as base address for allowing virtual machine access to physical network, the NIC used for allowing virtual machine to reach the physical network have to be configured in a “Bridge”, in this case the Bridge will take the IP address of the host NIC it is built on.

Because each configured NIC of a virtual machine must have an IP address of a subnet compatible with the sub-net of the Bridge it is connected to, it is advisable to fill in the following table:

2.2.6 1350OMS License

To be able to start the 1350OMS TMN Application you mast have license keys for application you have to start. To obtain the license keys the related license point must be bought in advance, with license points the license keys can be obtained from https://nmfactory.web.alcatel-lucent.com/ .

Server bridge0 IP bridge1 IP bridge2 IP bridge3 IP bridge4 IP bridge5 IP

Virtual machine eth0 IP eth1 IP eth2 IP eth3 IP eth4 IP eth5 IP

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

2.3 Operating System Installation on Host Server

This chapter describes installation, it explains how to perform Red Hat Enterprise LinuxTM Operating Sys-tem installation

NEVER EXECUTE THIS PROCEDURE ON A PRODUCTION SYSTEM!

The activity deletes the entire contents of involved hard disk(s).

Before proceeding with installation it is strongly recommended to read the software release notes and check on the related Technical Excellence Center WEB site for any warning and known prob-lems!

2.3.1 Disk usage

The installation procedure applies the following policy regarding disks where install RHEL 6 Operating Systems:

– Local disksAll local disks detected will be initialized again, the first disk in configuration will be partitioned to allow the O.S. boot. The remaining space will be configured with Logical Volume Manager in a volume group. The name of the volume group will be vg_<hostname> in case the hostname is user-spec-ified at the beginning of the host installation procedure (recommended), otherwise the procedure will assign a 8-character random string.

– Removable disks (e.g. USB drives)No USB device will be used for RHEL 6 installation.They will never be affected by the installation procedure.

– Fiber Channel disksThe fiber channel disks will be not included by automatic disk partitioning, to install RHEL on fiber channel disks the “Virtualization Host (manual disk configuration)” option must be used, in the boot menu of the installation procedure (see relevant section).

2.3.1.1 Swap partition

On disk selected from the software installation, A swap partition is created (in a logical volume “lvol_swap” created within the volume group mentioned above) with a size depending on system RAM amount and determined automatically as follows:

– Up to 4GB RAM: 2GB swap– Between 4GB and 16GB RAM: 4GB swap– Between 16GB and 64GB RAM: 8GB swap– Between 64GB and 256GB RAM: 16GB swap– Between 256GB and 512GB RAM: 32GB swap– 512GB RAM and above: 64GB swap

All remaining space in the volume group is then assigned to a second logical volume called “lvol_sys” where a flat file system (ext3) using up all available space is created.

The dimension of the swap partition can be forced manually using, in boot command line, the following option:

swap_space=<integer>

Installation Guide




where <integer> is the number (expressed in GB) to specify the size of the swap file system overriding the above rules. Swap can be fully disabled by specifying “swap_space=0”.

2.3.2 Boot HP ProLiant server

HP ProLiant server can be installed using local DVD drive (also USB drive is supported), or virtual DVD device provided by Integrated Lights-Out (ILO) control processor:

1) installation from DVD is the best option in case if you have physical access to the server; this is also the fastest and most reliable option.

2) installation from virtual DVD configured via ILO is useful for installing server where the DVD drive is not available or if you are far from server room. This option requires a reliable and fast network, otherwise the procedure may fail.

2.3.2.1 Boot from DVD or ILO

To boot the server from DVD you have to insert the bootable DVD label: SWP-1350OMS-MW_OS-BH-V11.0.0.1.0-LX 1/1 into DVD reader or configure ILO Virtual Media and then reset the power on the server.

On power on, server automatically boot following the defined “BIOS” boot order where CD/DVD are usu-ally defined as first choice. In this case server will read the DVD or Virtual Media contents and it will show the following window:

Figure 1. RHEL 6 initial boot from local DVD

IMPORTANT: at the menu screen, do NOT simply select an option and press Enter. Before pressing Enter on the selected option, you must hit the TAB key to get a prompt, and then you have to type in various command-line settings for the installation (see below). Only after this is done the installation process can be started by pressing Enter.

Moreover, the menu screen has an associated inactivity timeout of 60 seconds. You must interrupt the count down by pressing an arrow up or arrow down key on the keyboard, otherwise the server will run the default action, which is to attempt to boot from internal hard disks when the timeout elapses.

You can start the “Virtualization Host” default installation by selecting that choice and pressing [Tab] key, or select “Virtualization Host (manual disk configuration)” if you need special disk configuration, but in any case the [Tab] key must be pressed, and configuration data must be entered, before pressing Enter.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

rentrer la commande option avec hostname, IP et gateway du serveur

ibamba

Texte surligné

N.B. If you press [Tab] on a wrong choice, it is possible to return to menu by pressing [Esc].

2.3.2.1.1 DVD boot additional options

Choosing “Virtualization Host” or “Virtualization Host (manual disk configuration)” and pressing [Tab] allows you to add the following configuration options: IP, netmask, gateway and hostname, for automatic server eth0 configuration.After the [Tab] key press a partially pre-configured line like the following will be displayed:

vmlinuz initrd=initrd.img ks=cdrom:/ks-virt.cfgor:

vmlinuz initrd=initrd.img ks=cdrom:/ks-virt.cfg no-disk-config

You have to add the necessary options by editing the line with the following syntax:

vmlinuz initrd=initrd.img ks=cdrom:/ks-virt.cfg ip=<IP address> netmask=<netmask>gateway=<gateway IP address> hostname=<name>

or:vmlinuz initrd=initrd.img ks=cdrom:/ks-virt.cfg no-disk-config ip=<IP address>

netmask=<netmask> gateway=<gateway IP address> hostname=<name>

Where: <IP address>, <netmask>, <gateway IP address>, and <name> have to be replaced with the appro-priate values.

Example:

Figure 2. RHEL 6 Boot options (example)

After having set out the appropriate boot options, press [Enter] to continue.

2.3.2.1.2 Manual disk configuration

If you have chosen “Virtualization host (manual disk configuration)” some additional specific windows will be displayed.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

Figure 3. RHEL 6 Manual disk configuration.

Select “Review and modality partitions layout” option and then click on “Next” button.

N.B. In case you do not select “Review and modality partitions layout” you must review the file sys-tem configuration manually later, or restart the OS installation from the beginning.

The following window will be shown allowing you to review and modify the file system layout.

Figure 4. RHEL 6 File system review window

When the file system layout review is complete, press “Next” button to go on.

Another window will be shown to allow changing the bootloader device and bootloader password, press “Next” button again to proceed.

Installation Guide




2.3.2.2 Red Hat Operation System installation

After disk configuration, when needed, Red Hat Enterprise Linux 6 software installation will start:

Figure 5. RHEL 6 Operating System installation startingAt the end of installation the server will be automatically rebooted, but the procedure will continue with the host reboot:

You can now remove the DVD from drive or from ILO.

RHEL 6 installation will take about 15 minutes on a HP ProLiant DL380 G7, it can take up to twice when installed using ILO virtual device, depending on network speed.

2.3.3 RHEL Server First Boot and License server set-up

After RHEL completes the installation of the software, at the first boot you will be prompted by some con-figuration windows, divided in five sections. The steps to follow are described in this section.

Moreover, in case the server must also play the role of license server (this is the case when you are install-ing only one physical server running all VMs and there is neither a dedicated pre-existing license server nor an existing three-redundant license scheme) you will have to configure it accordingly at this time (see Section 2.3.5).

First of all, it is necessary to accept the RHEL license terms and conditions. Read the contents of the dis-played window, then select “Yes, I agree to the License Agreement” and press "Forward" button in the right low window corner.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

Figure 6. RHEL Configuration - Accept the License Agreement

2.3.3.1 Configuring default keyboard

Define default console keyboard by selecting your keyboard type in the shown list and press "Forward" button in the bottom right window corner.

Figure 7. RHEL Configuration - Keyboard Selection

Installation Guide




ibamba

Texte surligné

2.3.3.2 Configuring root password

Enter the root password twice in both input text fields and then press "Forward" button to go on.

Figure 8. RHEL Configuration - Root Password definition

2.3.3.3 Configuring Timezone and Time

The next window shown is about “Date Time and Timezone” settings. It is recommended to change the Timezone before, and then go back on date and adjust it as needed.

2.3.3.3.1 Select Time Zone

You can select the server host operation time zone by choosing related reference city form the city selec-tion list from the map.

Figure 9. RHEL Configuration - Timezone selection

Check “System clock uses UTS” and select “Date and Time”.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

2.3.3.3.2 Set Date and Time

Now you have to set the current date and time of your time zone by changing the values shown in selection boxes.

Figure 10. Setting Date, Time and Timezone

Then press “Forward” to proceed with “Configure Kdump”

2.3.3.4 Configure Kdump

Enable the kernel crash dump (Kdump) mechanism, checking “Enable Kdump?” and define the Kdump memory dimension (in MegaByte). Then, press "Finish" button to finish the RHEL configuration.

Figure 11. RHEL Configuration - Kdump configuration

Confirm the Kdump definition and accept the system reboot required from the procedure pressing "Yes" button to go on.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

Figure 12. RHEL Configuration - Kdump required reboot confirmation

2.3.3.5 System Login Prompt

The following window will be displayed:

Figure 13. RHEL Configuration - Final reboot

Clicking on the window, will be required username and password to connect the server:

a) Put “root” in “Username:” field then click on “Log In” button.b) Put the root password in “Password:” field (the same indicated in paragraph 2.3.3.2) then click on

“Log In” button.

The following window will be displayed:

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

Figure 14. Red Hat root Login warning message

Before to proceed with Virtual machine setup you have to configure NTP.

2.3.3.6 Configuring Network Time Protocol (NTP)

For a correct time management, it is required that them all VMs should be configured to be synchronized with a NTP reference server, to prevent mistake and simplify the installation, the NTP configuration is auto-matically provided by the VM deploy tools, that means all VMs will configured to synchronize their clock on the host server ones, but host server must be configured to provide them NTP service.

The host server can be configured in two ways in order to offer NTP service's request:

1) The server host can be configured as an intermediate level of NTP service, which receives the sync from a higher level, and distributes it to the VM.

2) The server host uses its own clock to synchronize the VM.

The first case you do not need to set the server host clock, it will be automatically aligned to reference NTP server, vice versa, it have to be carefully done when the server host uses own internal clock.

N.B. If there are more then one server host and no NTP server available, it is suggested promote one of them as main NTP server referred by the other, this configuration prevents clock drift.

To configure any NTP you have to open “Date and Time Properties” from “System”->”Administration” -> “Date & Time” pull down menu choice.

2.3.3.6.1 Configure Server Host to Reference NTP server

To be able to complete this procedure you must have the address of the server or servers to be defined as references.In the following window should be selected option: “Synchronize date and time over the network”.

Installation Guide




ibamba

Texte surligné

Figure 15. Date and Time properties dialog

The NTP server list will be shown. You have to remove all servers already defined by Red Hat, by selecting them all and pressing the “Delete” button.

Figure 16. NTP server list tab

Then press “Add” button to open a new NTP line, click on it and type the NTP server IP address, then press “Enter” button to complete the data entry.

.

Figure 17. Adding a NTP server

Installation Guide




ibamba

Texte surligné

Repeat previous action for all NTP server you have to configure, then click on triangle close to “Advanced options” to reveal two additional options. Select “Speed up initial synchronization”, then press ‘OK” button to save the configuration change just done.

2.3.3.6.2 Configure NTP on Local Time SourceTo configure NTP (Network Time Protocol) daemon on local time source, like in the previous section you have to select “Synchronize date and time over the network” and then remove all NTP server entries already present (if any), then click on “Add” button and type 127.127.1.0 (localhost address in file /etc/hosts) in the new line that appears, and finally press [Enter] to continue.The following message will be shown. You have to confirm your choice by clicking on “YES” button.

Figure 18. RHEL NTP server confirmation

Click on “Advanced Options”.Mark “Use Local Time Source”.

Figure 19. RHEL NTP using local time source

Click on “OK” button to confirm.

2.3.4 Retrieve and install Virtual Machine Tools

To finalize the host installation and enable deployment of Virtual Machines on it, you must login the server to install additional software packages for managing Alcatel-Lucent Virtual Machine (VM).

2.3.4.1 Retrieve Virtual Machine Tools

The 3 software packages to install are located on the first DVD (DVD 1 of 2) of the SWP-1350OMS-MW_OS-VD-V11.2.0-LX MWOS Bootable disk set.

The software packages are delivered as the following RPM files:

1350OMS-MW_OS-bck-11.1.0.0.0-13.x86_64.rpm

1350OMS-MW_OS-conv-11.1.0.0.0-13.x86_64.rpm

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

1350OMS-MW_OS-repos-11.1.0.0.0-13.x86_64.rpm

1350OMS-MW_OS-sec-11.1.0.0.0-13.x86_64.rpm

autoinstall112-1.9-62.noarch.rpm

mindi-2.1.7-1.el6.alu.x86_64.rpm

mindi-busybox-1.18.5-3.rhel6.x86_64.rpm

mondo-3.0.4-2.el6.alu.x86_64.rpm

Poseidon-1.1.0-1.x86_64.rpm

sc-vadeploy-4.2-1.el6.noarch.rpm

star-1.5-11.el6.x86_64.rpm

vsftpd-2.2.2-11.el6.x86_64.rpm

1350OMS-MW_OS-11.1.0.0.0-13.x86_64.rpm

Assuming that the host installation has been done using MWOS Bootable version SWP-1350OMS-MW_OS-BH-V11.0.0.1.0-LX , all other RPM files found in the first DVD must be ignored.

2.3.4.2 Install Virtual Machine Tools

After mounting the DVD SWP-1350OMS-MW_OS-VD-V11.2.0-LX (DVD 1 of 2) under a mount point directory to access its contents, you must cd to that directory and install VM tools using “rpm” command (as root user) as follows:

...,root,root # rpm -i 1350OMS-MW_OS-11.1.0.0.0-13.x86_64.rpm 1350OMS-MW_OS-bck-11.1.0.0.0-13.x86_64.rpm 1350OMS-MW_OS-conv-11.1.0.0.0-13.x86_64.rpm 1350OMS-MW_OS-repos-11.1.0.0.0-13.x86_64.rpm 1350OMS-MW_OS-sec-11.1.0.0.0-13.x86_64.rpm

...,root,root # rpm -i Poseidon-1.1.0-1.x86_64.rpm

...,root,root # rpm -i sc-vadeploy-4.2-1.el6.noarch.rpm

...,root,root # rpm -i vsftpd-2.2.2-11.el6.x86_64.rpm

..,root,root # rpm -i mindi-busybox-1.18.5-3.rhel6.x86_64.rpm mondo-3.0.4-2.el6.alu.x86_64.rpm mindi-2.1.7-1.el6.alu.x86_64.rpm star-1.5-11.el6.x86_64.rpm

...,root,root # rpm -i autoinstall112-1.9-62.noarch.rpm

After the installation of the “autoinstall package” a random password will be generated for the alutmn user-id, in order to change it execute, as root user, the following command:

...,root,root # /var/autoinstall/.htpasswd alutmn [Enter]

N.B. The autoinstall tool (AI) is delivered for the bench configuration, it MUST be installed on the HOST Server using a VNC gui (GoGlobal is not supported).

2.3.5 Configuring the host server as the Poseidon and GoGlobal License Server.

To be able to run 1350OMS software in the guest VMs, and to use GoGlobal remote access to the host,

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

créer un répertoire VD_LIBRARY

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Sticky Note

htpasswd /var/autoinstall/.htpasswd alutmn

a) First, on the host you have to install licenses keys for both Alcatel-Lucent (Poseidon) and for GoGlo-bal. Both license keys have the same two phases approach: the license request and the license set up. See Appendix C in order to configure GoGlobal license; See Appendix D in order to configure Alcatel-Lucent license.

b) Then, still on the host you have to start the “poseidon” and “goglobalux” services.

N.B. Then, when deploying the guests (see Chapter 3), in the VM Deployer web form you will have to specify that for the Poseidon and GoGlobal license servers the guests should point at the IP address of the host.

N.B. By deafult, GoGlobal-UX is configured so that root connections are NOT allowed. In order to enable root connections by GoGlobal-UX (e.g.: in order to install Alcatel-Lucent Network Man-agement software), it is necessary to execute (logged as root), the following command:

..,root,root # scEnableGoGlobal [Enter]

In order to restore appropriate security level remember to disable GoGlobal root connections executing the following command:

.,root,root # scDisableGoGlobal [Enter]

2.3.6 Retrieving Virtual Disks and Creating a Repository

In order to deploy virtual machines the precondition is that all the Virtual Disk delivered by Alcatel-Lucent are accessible by the host server.

Because the software is distributed on 4.7GB DVDs and two Virtual Disk files (those for MWOS and for EML) are larger than a DVD, such files are delivered split in two or three fragments, respectively, so each fragment can fit the available space on the DVD media.

Before VM installation can take place, however, these parts have to be re-assembled to obtain the original, complete Virtual Disk files.

This activity can be done in two way, “online” or “offline”.

A procedure for online VD reassembly (described in section 2.3.6.1) reads the DVD contents and reas-sembles virtual disks from the fragments, writing the resulting files directly in a specific directory of the server host.

2.3.6.1 Online VD reassembly

Create a repository directory on the host file system, for example:

mkdir /VD_LIBRARY

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

N.B. The entire path to the directory chosen for the depot must be traversable (read and execute [tra-versal] permissions) to all (owner, group, others) users, otherwise the configuration tool will complain about the directory with a message like this: Wrong reference to VD Library base path: /root/DEPOT/NR11.2/1350OMS-LX_11.2.xx.yy.zz/no such directory usually the default umask for the root user is already appropriate, so any directory created by root user will have the right permissions set. However, in case you create the depot directory under an existing directory, you should make sure that the latter has appropriate permissions, as described above.

create a mount point for the DVD disks, for example:

mkdir /mnt/dvd

One DVD at a time, mount the DVD under the mount point and copy all files to the repository directory: for example, assuming the device name corresponding to the DVD drive is /dev/sr0 (you can find out the exact device name on your server by examining the output of the lsscsi command looking for an entry about a “cd/dvd” device), you should execute the following commands for each disk of a disk set.

Begin with the MWOS disk set. Execute the following commands for each DVD of the MWOS disk set:

(insert disk and allow a few seconds..)

mount /dev/sr0 /mnt/dvd

cp -rf /mnt/dvd/* /VD_LIBRARY

umount /mnt/dvd

(remove disk..)

Once all files of all disks of the MWOS disk set have been copied to the repository directory (/VD_LIBRARY in the example), execute the following commands to reassemble the MWOS VD file from its two fragments:

cat VD-MW_OS-11_0.1-1.qcow2.img00 VD-MW_OS-11_0.1-1.qcow2.img01 >> VD-MW_OS-11_0.1-1.qcow2.img

Now you should check the MD5 checksum of the files in the repository directory against the expected val-ues. The expected MD5 checksum values for the files of a disk set are listed in a .md5sum file which is present in each disk of the set.

To calculate the MD5 checksum values for the files in the repository directory, cd to that directory, then execute

md5sum *

and then, for each file listed in the .md5sum file, compare actual values with expected values.

If the actual values match the expected values (in particular for the MWOS VD file), you can free up disk space by deleting the 2 fragments of the MWOS VD file (VD-MW_OS-11_0.1-1.qcow2.img00 and VD-MW_OS-11_0.1-1.qcow2.img01)

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

Now repeat the same procedure for the disks of the 1350OMS disk set (4 DVDs): first of all, copy all files from each DVD to the repository directory: for each DVD of the 1350OMS disk set execute the following:

(insert disk and allow a few seconds..)

mount /dev/sr0 /mnt/dvd

cp -f /mnt/dvd/* /VD_LIBRARY

umount /mnt/dvd

(remove disk..)

then reaggregate the EML VD from its 3 fragments:

cat 1350OMS_EML_11_11.1.2.10.41.qcow2.img00

1350OMS_EML_11_11.1.2.10.41.qcow2.img01 >> 1350OMS_EML_11_11.1.2.10.41.qcow2.img

then calculate the actual MD5 checksums by executing from within the repository directory the following command:

md5sum *

and compare them with each expected value found in the .md5sum file.

If the actual and expected checksum values match (in particular for the EML VD file) then you can free up disk space by deleting the fragments of the EML VD file.

Now your repository directory contains all files needed to proceed with the installation and their integrity has been verified.

3 1350OMS Virtual Machine SetupA 1350OMS/Linux installation consists of a set of Virtual Machines, each running a NMS Master instance or a Presentation instance.

This chapter shows how to create new 1350OMS Virtual Machines on a physical server host previously installed with Alcatel-Lucent 1350OMS MW_OS boot media and configured as “Virtualization Host”.

Before to proceed with the configuration and the installation steps please take care to read the AI, Auto Installation tool restriction listed here below:

– WDMNBI NMA / UNBI NMA configuration (to configure run, after the autoinstall, a new System Con-fig (3.4.1) on WDM VM)

– The VM names cannot be the same of the instance names i.e. Do not use EML hostname if the server has EML_x-yz instance (eml_X-yz can be used) or SDH hostname if the server has SDH_x-yz instance (sdh_X-yz can be used). The maximun lenght for the VM Name is 50 characters for the KWM Virtual Machines Manager (tak-ing into account that the limit includes the 20 characters as maximun lenght for the hostname).

Installation Guide

1350OMS Virtual Machine Setup



ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

N.B. When more then one 1350OMS-EML managing PSS Network Elements is present in a LX bench configuration, CPB on Presentation will be associated to only one of the 1350OMS-EML instances and a warning message will be displayed in red in the configuration editing window. example of warning message: Warning: The configuration includes multiple EML VMs managing PSS NEs. CPB on Presentation will associate with the EML VM with instance ID=<EML_instance-id>, hostname=<EML-VM_hostname> (allocated to server "<Linux-Host_hostname>")

N.B. When configuring 1350OMS-WDM VM via AutoInstall Configurator, configure the same LANs (Configuring Network Bridges) in 1350OMS-WDM corresponding to 1350OMS-SDH. example: - HOST: bridge0 created using eth0, bridge1 created using eth1 - SDH configure eth0 (bridge0), eth1 (bridge1) - WDM configure eth0 (bridge0) AND eth1 (bridge1) i.e. if eth1 is configured in 1350OMS-SDH, also configure eth1 in 1350OMS-WDM.

3.1 Access 1350OMS configuration Tool

The access to 1350OMS configuration tool you have to open an Internet browser and type as URL the IP address of the physical server host. The connection will be changed to http secure protocol, and this can cause a warning message from browser. Ignore the message (depending on the browser used, this may require to “accept a security exception” or similar action) and proceed.

Figure 20. Connection warning message

The welcome window will be shown:

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Note

WDM et SDH utilisent les memes VLAns càd les meme ports Eth et mêmes bridges.

ibamba

Texte surligné

Figure 21. Instances configuration entry page

Click on the picture to go to configurator main menu.

Figure 22. Version selection screen

Select the R11.2 release to proceed, the following window will be shown.

Figure 23. Setup procedure main menu

Installation Guide




ibamba

Texte surligné

3.1.1 Configuring Network Bridges

Before proceed with the instances configuration it is required to properly configure the network bridges. This is a special networking setup which is required to enable the deployed Virtual Machines to reach the external LAN(s) through the physical NICs of the host.

The situation is:

• The host has one or more physical NICs;

• Each Virtual Machine to be deployed on the host can have one or more virtual NICs.

A path from a VM to the external LAN is set up by connecting a virtual NIC with a physical NIC. This con-nection is not direct, but it is done through a logical object called virtual network bridge.

A virtual network bridge is associated with a physical NIC of the host and will take its IP address and net-mask, which were previously set and which must obviously be compatible with the subnet netmask appli-cable to the physical LAN on which the physical NIC is connected.

Once the virtual network bridge exists, one or more virtual NICs can be connected to it at the time a VM is deployed. In this way, a VM will be able to reach the external LAN through the path: virtual NIC – virtual network bridge – physical host NIC.

To access the Network Bridge configuration page you have to click on “Manage or create host-guest net-work bridges” in Alcatel-Lucent 1350OMS/LX Setup window (Figure 23.)You have to create a network bridge for each server host Network Interface Card (NIC) planned to be used by 1350OMS Virtual Machines.

N.B. To have homogeneous environment it is suggested to use bridge<N> as bridge names, and to use for a bridge<N> the same N as the host NIC on which the bridge is created (e.g. bridge0 on eth0, bridge1 on eth1, and so on).

Bridge creation have different behavior depending on whether NIC addresses are already configured or not. The procedure for both situations is given below.

As a reminder: server NICs are identified by Red Hat Linux with the “eth” prefix followed by a number.To identify a physical NIC on the server back panel it is recommended NOT to rely on the labels printed on the panel, but on the shell command:

...,root,root # ethtool --identify <eth#> <seconds>

For the specified number of seconds, the NIC leds will blink enabling detection of the relevant port.

Be aware that network bridge creation requires a restart of the entire host networking services,

therefore this activity should be performed during an appropriate maintenance time window.

3.1.1.1 Create a Bridge using configured NICs

Once in the Virtual bridge administration page, to create a bridge on a configured NIC it is sufficient to enter the desired name of bridge (the name must be a valid identifier, but see above for additional recommen-dations on naming), select the related NIC identified by eth#, and press “Create” button.

Installation Guide




Figure 24. Virtual Bridge administration main page

A new window will show you the creation phase, be aware that bridge creation can take a while and during this period the server can become momentarily unreachable from network.

Figure 25. Virtual Bridge Creation successful

Installation Guide




Figure 26. Virtual Bridge Administration page with one bridge created

N.B. If you make a mistake during the creation of the new bridge, you can delete it using the "Delete" button in the action column in the “Existing bridges” table of the Virtual Administration page (confirmation is requested, see figure below).

Figure 27. Virtual Bridge administration: Delete bridge confirm request

3.1.1.2 Bridge configuration

In order to configure the created bridge(s) press the "Modify" button in the action column in the “Existing bridges” table of the Virtual Bridge Administration page, the following page will be shown.

Installation Guide




Figure 28. Virtual bridge administration - Modifying existing bridge

Here you have to fill in the fields with IP address and related netmask and gateway that have to be assigned to the bridge; then press “Modify” button to update the bridge configuration.

3.1.2 Create the R11.2 configuration

After that the bridge(s) is/are created and configured press the “Back to main menu“ button in the Virtual Bridge Administration window (Figure 26.) to go back to the Setup main page.

Figure 29. Setup procedure main menu

The Option menu offers 4 different choiches to configure the bench, only the first three are meaningful for a scratch installation: “Create empty R11.2 configuration“, “Create new R11.2 configuration from file“and “Create new R11.2 configuration from Host-based file“.

Installation Guide




ibamba

Texte surligné

N.B. The “Create new R11.2 configuration from file“ and “Create new R11.2 configuration from Host-based file“, can be used in HW replacement context, please refer to the “Hardware Replace-ment / Migration” chapter for detailed instructions.

N.B. The “Clone existing configuration” option feature enables the user to create an exact duplicate of an existing configuration description (not meaningful for a scratch installation), under a dif-ferent name. The new configuration can then be modified (for example to avoid IP address duplication issues) and deployed independently from the original configuration. The feature can also be used to create a "backup copy" of a configuration description before making significant changes. Note that the feature works only on configuration descriptions, not on the VMs of a deployed configuration. It does not create any VMs. This requires to proceed with the usual deployment steps after the configuration description is cloned.

3.1.2.1 Create empty configuration (menu option 2)

The “Create new R11.2 configuration from file“ option of the menu must be used to create an empty con-figuration, enter the configuration name (also know as prefix) (i.e. NR111, NR96 in the image below) than press the OK button, the following window will be shown.

Figure 30. Newly created empty bench - initial view

N.B. Configuration name may only contain uppercase/lowercase letters and digits and must begin with a letter.

At least a new Linux host must be defined, type the host name and its IP address in the proper fields, then press the OK button.

Installation Guide




ibamba

Texte surligné

Figure 31. Add new Linux host

N.B. In case of Multi-Hosts configuration ALL the necessary hosts must be added and for each instance that will be defined a “Move to:” box will be displayed in order to be able to move it between the defined HOSTs.

3.1.2.2 Create new configuration from file

If a set of configuration files is available to be used to configure the new bench, type the new configuration name in the dedicated box of “Create new R11.2 configuration from file“ option, browse the files using the related button and then upload it.

Installation Guide




Figure 32. Import configuration from file (define configuration name)

Figure 33. Import configuration from file (upload configuration file)

N.B. As alternative the available configuration file can be uploaded starting from the option “Create new R11.2 configuration from file“ (3.1.2.1) choosing the configuration name and then, from the displayed window of the new empty bench, pressing the "green arrow" button, the selection of the configuration file will be requested (at least an host must be defined first).

Figure 34. Import configuration from file (upload configuration file - green arrow button)

ALL the needed updates to an existing bench configuration imported via the just descrived

options must be executed using the AI-C web gui as described in the following paragraphs. Example: if the support for 1850TSS or 1830PSS NEs must be added, they must be configured via AI-C before the generarion of the new bench to be installed (if not available a new 1350OMS PKT VM must be created to manage the 1850TSS NE and a new 1350OMS WDM VM must be created to manage the 1830PSS NE).

3.1.2.3 Create new configuration from Host-based file

If a set of configuration files is available to be used to configure the new bench, type the new configuration name in the dedicated box of “Create new R11.2 configuration from Host-based file“ option, type the full path and the configuration file to be imported then press the related button to upload it.

Figure 35. Import configuration from file (define configuration name)

Installation Guide




Figure 36. Import configuration from file (upload configuration file)

N.B. As alternative the available configuration file can be uploaded starting from the option “Create new R11.2 configuration from file“ (3.1.2.1) choosing the configuration name and then, from the displayed window of the new empty bench, pressing the "green arrow" button, the selection of the configuration file will be requested (at least an host must be defined first).

Figure 37. Import configuration from file (upload configuration file - green arrow button)

3.1.3 Configuration editing

The web-based configuration editor allow you to configure the 1350OMS Linux bench.

3.1.3.1 Overview

Before you use the procedure to describe the structure of the installation, in terms of type and number of instances to configure, their networking and information. In case the new Linux installation has to inter-act with the Master instances of an existing HPUX or Linux installation, you will also have to specify basic addressing/identification data of those instances, so that they can be properly referenced by the new instances that will be configured.

Once the description of all the instances composing the installation (and of the existing instances to be referenced by it, if any) is complete, you then specify global information such as the path where the VD files can be found, as well as the initial ssh password and licensing information.

Finally, a final check is done on the configuration and the related foiles will be generated.

3.1.3.2 Description of the installation structure

An installation may include a number of instances of two different types: Presentation and Master.

Each Master instance must be configured as one independent Master Virtual Machine. Likewise, each Presentation machine is configured as one independent Presentation Virtual Machine.The orange icon allows you to add a Presentation instance to the installation structure, and the blue one to add a Master instance.

N.B. At least a Presentation VM, a SDH/NPR Master instance VM and an EML Master instance VM must be defined.

Installation Guide




3.1.3.3 Add a Master Instance

N.B. for a correct usage and configuration of MYSQL on the EML Master context the 1830PSS NE must be selected during the Automatic Installation Configuration, otherwise the MYSQL prod-uct will not be installed.

A configuration with only 1350OMS-EML instance(s) is not supported, al least a 1350OMS-

SDH or a 1350OMS-NPR instance is required to manage physical connections and maps.

When the blue icon is pressed, the following page appears:

Figure 38. Adding a Master instance to the installation scheme

Select the server type, enter the hostname (maximun lenght for the VM Name prefix is 20 characters) and instance ID, then press OK.

You are then presented with a second page where general, dimensioning options and networking infor-mation for the new Master instance must be entered.

Figure 39. Master instance: Specifying Options and networking informations

Installation Guide




ibamba

Texte surligné

3.1.3.3.1 Master instance: Option and networking

3.1.3.3.1.1 Master instance: General option

In this section you can select the optional components to be installed, IOO and HA can be selected for all type of instances, ISN can be selected only for SDH/NPR and PKT instances.

N.B. If selected, the ISN and the HA components will be installed and configured (for HA con-figuration option please refer to 3.1.3.3.2), while the IOO component will be only installed and customized in the instance where it is selected but a Post installation graphical system configuration (see 3.4.1) is required after the specific license are available (refer to the IOO user manual) .

3.1.3.3.1.2 Master instance: Dimensioning option

Do not alter the default CPU core count value.

3.1.3.3.1.3 Master instance: Network setting

You can define up to 5 virtual NICs for the new Master instance.

Fill only the first N rows as needed, leaving no empty rows.

Each virtual NIC is to be associated with a bridge (which must have been created in advance using the Manage or create host-guest network bridges procedure, see section 3.1.1). When specifying network information for the instance, by selecting the desired bridge, the IP and mask fields will be partially pre-filled. You need to specify the IP address of this virtual NIC and it must be compatible with address and netmask of the bridge chosen. Optionally you can also specify the address of a gateway.

N.B. Of the up to 5 virtual NICs, be sure to specify no more than ONE gateway, and to specify it on the NIC that is plugged on the bridge whose address/subnet is consistent with the address of the gateway itself.

N.B. In order to support the GMRE a second virtual NIC must be configured for SDH Master instance.

Press OK to confirm, if the instance is not an EML Master, a blue icon related to the configurated instance is added to the installation structure diagram (Figure 46.) otherwise the “EML-specific networking setting“ window will be opened.

Figure 40. EML-specific networking settings

This step is only presented when creating a EML master instance and requires the user to enter config-uration information about the supervision areas.

There may be up to one supervision area per guest NIC (at least one must be defined overall).

Installation Guide




ibamba

Texte surligné

For each supervision area it is necessary to specify its name (must be a valid identified) and the Stack type to be selected between NECOM and TCP; if NECOM is selected, further configuration data is required: System ID (12-digit hexadecimal string) and VLAN enable toggle (boolean). If VLAN toggle is set, then a further set of parameters is required (VLAN name, IP, Gateway and netmask).

Figure 41. EML-specific networking settings with two supervision areas defined

Once the supervision areas are defined, it is necessary to specify the type and release of the NEs to be managed through that supervision area. To do this, press the "Select NEs" button:

Figure 42. managed NE type/release selection: initial view

In the window that appears, first select a NE family from the leftmost list, the Types selector will be pop-ulated accordingly then select one NE type and the Releases selector will be populated accordingly, now select one or more NE releases from the third selector (pres the Ctrl key for multiple selection) and press the "Add>>" button beneath it. The fourth selector will populate with the NE type/releases selected. Repeat the procedure as needed to fully define the set of NE type/releases to be supported on this super-vision area. Press OK when done.

Installation Guide




ibamba

Texte surligné

Figure 43. managed NE type/release selection: selection procedure

After confirming with OK button the set of NE/type releases managed on the selected supervision area, the "Set NE qty" button will appear enabling the user to specify for each configured NE type/release the number of network elements.

Figure 44. NE type/releases selected, Set NE qty button enabled

Press the “Set NE qty” button to display its window:

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

Figure 45. specifying NE quantities

For each NE type/release configured on the selected supervision area, the quantity (number of NEs) can be specified: initially all values are set to 1; The number must be an integer greater than 0. Press OK to confirm, a blue icon related to the configurated EML instance is added to the installation structure diagram.

Figure 46. Master Instance configured (in this figure EML master instance configured).

Follow the link “Open” on the right of the Hostname to view the “fully configurated” master instance(s), in this case only the new added EML master instance will be displayed.

Installation Guide




Figure 47. Master Instance configured (in this figure a EML master instance fully configured)

In the synopsis view of the bench, the instance now appears with a report of all configuration options, net-working settings and, only for EML instance, NE type/release/quantity configured for each supervision area.

3.1.3.3.2 Configure 1350OMS-HA in a Master instance

During the configuration of a Master instance (see 3.1.3.3.1.1) it is possible to select the HA optional com-ponent and to configure it.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

Figure 48. HA configuration: Creating a SDH master HA pair

Fill all necessary settings, enable the HA toggle and also fill the associated sub-options. Press OK to con-firm

Set the HA toggle, fill the HA sub-options (Autoswitch, Companion host IP address, Companion host Host-name and Isolation node), then proceed with NIC setting normally. Press OK to confirm.

N.B. By checking the HA toggle, the instance being configured is assumed to become a Main (NOC) in a HA pair (this is pre-filled in the Site type selector) and a panel of sub-options appears: Companion host IP address: the spare (DRC) instance address Companion host hostname: the spare (DRC) instance hostname The above two settings will be used to pre-configure the network parameters for the partner VM in the HA scheme. Isolation Node: a comma-separated list of addresses that the main and spare VMs will test for reachabiliy to detect isolation conditions. The list must contain one or more valid IP addresses and commas, without spaces or any other character Site type: sets role of the current instance: NOC is automatically set by default: do not change this value. The partner instance Site type will be automatically set to DRC.

After the configuration of the Master instances with the HA toggle selected (in the example a EML master HA pair) the configurator main page appears as follow.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

Figure 49. HA configuration: EML master HA pair created

After creating the EML master instance with HA toggle set, a second instance is automatically created as the partner instance in the HA pair. This spare instance is pre-configured as much as possible based on the "companion" parameters specified in the main instance, or by reversing the siteType role, or by cloning the network settings.

The only parameter that still needs to be specified is the netmask (and optionally the gateway). The con-figurator tool highlights in red the missing parameter. Before proceeding, it is therefore necessary to visit in Edit mode the spare instance and specify the missing value for its netmask.

Installation Guide




Figure 50. Editing EML master HA spare instance: step 1

In this step, instance type and instance ID cannot be changed as they must be consistent across the main-spare HA pair; only the hostname can be edited, and if this is done, then the HA.companionName on the main instances will be automatically updated accordingly to preserve consistency. Press OK to continue.

Figure 51. Editing EML master HA spare instance: step 2

The only mandatory field to edit is the empty netmask field: the gateway setting is optional. Press OK to save. The bench synopsis view now looks like:

Installation Guide




Figure 52. Bench with non-HA EML master instance and a HA pair for EML master (details)

Installation Guide




Figure 53. Bench with non-HA EML master instance and a HA pair for EML master (bench view)

The example bench in Figure 52. and Figure 53. has only EML master instances. The configuration is not accepted because there are no Presentation instances and SDH or NPR master instances.

N.B. When a HA master pair is configure on a bench at least one Presentation instance bound to NOC and one bound to DRC are required. Follow the instruction to properly configure the Pre-sentation instances with HA (3.1.3.4.1).

3.1.3.4 Add a Presentation instance

To add a Presentation instance to the installation structure, press the Orange button.

You are then presented with the following page:

Figure 54. Adding a Presentation instance to the installation scheme

Installation Guide




ibamba

Texte surligné

Specify the hostname and networking information (with the same rules as for a Master instance, see 3.1.3.3.1) then press OK and a orange icon is added to the installation structure diagram.

N.B. If selected, the HA components will be installed and configured (for HA configuration option please refer to 3.1.3.4.1).

Figure 55. example of bench with Presentation (orange icon) configured

Installation Guide




ibamba

Texte surligné

Figure 56. example of bench with Presentation (orange icon) and EML Master configured

After creating the Presentation instance the bench synopsis no longer reports errors and new fields for setting general bench properties appear beneath the bench diagram (3.1.3.5).

3.1.3.4.1 Configure 1350OMS-HA in a Presentation instance

During the configuration of a Presentation instance (see 3.1.3.4) is it possible to select the HA optional component and to configure it.

Installation Guide




ibamba

Texte surligné

Figure 57. Creating a Presentation instance in HA context

Set the HA toggle and specify NOC in the "Site type" setting, then proceed with hostname and NIC setting normally. Press OK to confirm. Repeat the same procedure to create a second Presentation instance bound to DRC.

N.B. The two VMs must have different IP addresses and hostnames. Press OK to confirm.

Figure 58. Bench with HA Presentation instances pair created

Installation Guide




Figure 59. Bench with HA Presentation instances pair created (details)

After creating the pair of NOC-DRC HA presentation instances, the bench synopsis no longer reports errors and new fields for setting general bench properties appear beneath the bench diagram.

3.1.3.5 Entering global settings

Once satisfied with the installation structure diagram and all parameters, scroll down the page to reach the section where global settings must be entered.

Installation Guide




ibamba

Texte surligné

ibamba

Texte surligné

Figure 60. Global settings section

In this page you must enter:

a) The absolute file path of the repository directory on the host file system. The repository directory can be either a local directory containing a copy of the files, or a mount point of a USB device containing the files and plugged in a USB port of the server, or even a mount point of a NFS- or SMB- mounted network shared directory where the files are located.

b) The initial SSH password for all the VMs (select the link “View Rules” to display the rules to follow for the password).

Installation Guide




ibamba

Texte surligné

Figure 61. Initial SSH VMs password rules

c) Go-Global license information allows you to provide the license server references with up to 3. This information depends by the license server which you refer to, including the port number that must be the same specified in the Go-Global license, if no port is specified in the license you have to leave field blank.

d) Poseidon license information allows you to provide the license server references with up to 3. This information depends by the license server which you refer to, including the port number that must be the same specified in the Alcatel-Lucent 1350OMS license, if no port is specified in the license you have to leave field blank.

In the case of single license server, typically the choice is to specify the host itself on top of which the Virtual Machines are running.

Once the described fields are filled, press OK to proceed

3.1.3.6 Final review step

Once the installation structure is specified and global settings are entered, when the OK button is pressed the procedure validates the configuration data, generates VM descriptors and checks whether the nec-essary VD files are all present in the specified VD Library path.

In case one or more required VD files are not found, the procedure will report the relevant errors and it will be not possible to proceed.

Installation Guide




If this happens, go back and either adjust settings, or make sure to make available all necessary VD files in the specified directory.

If no errors are found, the page will appear as follows:

Figure 62. Configuration completed - configuration writing

Three configuration files for each instance of the bench are generated in /var/autoinstall/R11.2/gener-ated/<bench_prefix> :

– <vm name>.xml : configuration data used to deploy the virtual machine

– <vm name>.etchosts : initial /etc/hsosts defined inside the virtual machine once deployed

– <vm name>. NMS_parameter : NMS configuration data used to customize and configure 1350 OMS application

N.B. The <vm name> is the concatenation of choosen configuration name, hostname, server type and Instande ID.

N.B. The <bench_prefix> is the choosen configuration name (see 3.1.2)

Installation Guide




ibamba

Texte surligné

3.2 Automatic Install Alcatel-Lucent Software

At the end of the configuration step we are now ready to run the installation of the 1350OMS.

IMPORTANT: In case of Multi Host configuration, with or without 1350OMS-HA, please refer to the “Spe-cial Installation Instruction” before procedd with the Automatic Installation.

Login as root user on the host serve and execute the following commands:

– ...,root,root # cd /var/autoinstall/R11.2 [Enter] ...,root,root # ./1350OMS_install.sh prefix=<bench_prefix> [Enter]

N.B. The <bench_prefix> is the choosen configuration name (see 3.1.2)

All the Automatic Installation logs are located on the HOST server in the following directory:

/var/autoinstall/R11.2/trace/<HOST IP ADDRESS>

3.3 Special Installation Instruction

3.3.1 1350OMS-HA configuration

In case of installation of 1350OMS-HA installation some actions are required before to proceed with the Automatic Installation as described in the section 3.2 .

– Install the DRC host server as for the NOC host server (see 2 - Install Virtual Machine Host server). NOTE: take care to create the same /VD_LIBRARY directory, it is mandatory to have the 1350OMS LX software in the same place on ALL the hosts, also the AI version installed MUST be the same on each host.

– Allow SSH connection from "AI Driver host", NOC, to other host(s), DRC: connect to the "AI Driver host server" (the host server on wich the bench configuration was executed and the installation will be run) as root user and move on autoinstall root path: ...,root,root # cd /var/autoinstall/R11.2 [Enter] Execute the following command: ...,root,root # utilities/allowToRemote.sh <DRC-host-IP-address> [Enter]

3.3.2 Multi Host configuration

In case of a Multi Host installation some actions are required before to proceed with the Automatic Instal-lation as described in the section 3.2 .

– Install the other host server(s) as for the main host server (see 2 - Install Virtual Machine Host server). NOTE: take care to create the same /VD_LIBRARY directory, it is mandatory to have the 1350OMS LX software in the same place on ALL the hosts, also the AI version installed MUST be the same on each host.

Installation Guide




ibamba

Texte surligné

s'il s'agit d'installer un actif/sby aller au point 3.3 puis revenir sur le 3.2

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

ibamba

Texte surligné

– Allow SSH connection from "AI Driver host" to other hosts: connect to the "AI Driver host server" (the host server on wich the bench configuration was executed and the installation will be run) as root user and move on autoinstall root path: ...,root,root # cd /var/autoinstall/R11.2 [Enter] Execute the following command for each host of the Multi Host configuration: ...,root,root # utilities/allowToRemote.sh <host-IP-address> [Enter]

3.4 Post Installation instructions (execute on VMs)

The following section(s) describe how to execute, post installation, action(s) required to modify the already performed installation: i.e. a System Configuration maybe required by a specific workaround.

Please avoid to execute in installation phase any of the actions described in this chapter if not

expressly requested by a workaround.

3.4.1 System Configuration

– Login the system as root user with a graphical session.

...,root,root # cd /alu/Install_Wizard [Enter]

– Start the automatic installation procedure by executing:

...,root,root # ./Install.sh -config[Enter]

NOTE: Please move the “System config” splash window in order to accelerate the load of the items.

3.5 Post Installation W/A

3.5.1 1350OMS OIS applications down

This action must be applied only if 1350OMS-OIS is installed.

At the end of the 1350OMS installation execute a new 1350OMS-OIS configuration executing, as root user from the AI-driver host to the OIS instance the following commands:

..,root,root # ssh <ois-ip-address> "su - nbi -c \"/alu/Kernel/script/updateProcessConfig.pl -sys OIS -inst <ois-id>-11\"" [Enter]

Then start the system including the 1350OMS-OIS executing:

...,root,root # utilities/execOnBench.sh <prefix>_bench complete start [Enter]

Installation Guide




3.5.2 MAP management

To ensure MAP management, it's necessary to disable OTN Layered Map (managed only transport and physical) and PKT technology Map, before start the system, execute the following step on the SDM mas-ter instance:

Login as root user and execute the following two commands:

...,root,root # cd /usr/Systems/SDH_<id>_11.2_Master/MAPIM/script/ [Enter]

...,root,root # ./ConfigMapIm_light.sh [Enter]

The script writes traces into the file /tmp/ConfigMapIm_light.log.

3.6 Hardware Replacement / Migration

This chapter describe the steps to be executed to perform a “Hardware Replacement” or a “Migration”.

3.6.1 export configuration from bench WITH direct connection with the new host

As prerequisite the autoinstall tool must be already installed (Install Virtual Machine Tools); only the Master instances configuration files will be exported the Presentation instance will be added by the configurator (see “Add a Presentation instance” chapter).

In order to export the configuration files (with extension .NMS_parameter) from the source bench login as root user on the AI-driver server (the host that will replace the current hardware) and execute the fol-lowing commands:

...,root,root # cd /var/autoinstall/R11.2/ [Enter]

...,root,root # ./utilities/allowHP_To_Remote.sh <source IP address> [Enter]

...,root,root # cd export_DIR [Enter]

...,root,root # ./export_DIR/launch_export.sh from=<source IP address> env=master [Enter]

The launch_export.sh command generate the Master instances configuration files of the bench to be replaced in the export_DIR.

N.B. Notes related to the export:– The export script (launch_export.sh) must be executed for ALL the Master instances to

be exported.– The informations of the NEs are the ones in the source DB at the time of export.– The exported informations are:

• EMLIM id• NECOM/Supervision Areas (to be modified via AI-config after the import)• The processes instantiated on the source server are NOT exported; the processes

to instantiate will be automatically "calculated" by the configurator.• NEAD, if needed, must be locally configured.

The generated configuration files must be copied on the PC or on an USB drive, in order to do that perform the following instructions:

...,root,root # mkdir /var/www/html/export [Enter] ...,root,root # cp -f /var/autoinstall/R11.2/export_DIR/*.NMS_parameter /var/www/html/export [Enter]

Open a web browser and upload each generated configuration files typing their URL and saving them as text on the PC or USB drive (see example below).

Installation Guide




ibamba

Texte surligné

Example: https://<AI-driver IP-address>/export/EML_1.NMS_parameter

3.6.2 export configuration from bench WITHOUT direct connection with the new host

Here the procedure to export bench configuration in case do not exist direct connection from the server to be migrated (source_host in the following, it could be both UX/LX) and sever to be installed (target_host, it could be only LX).

As prerequisite the autoinstall tool must be already installed (Install Virtual Machine Tools); only the Master instances configuration files will be exported the Presentation instance will be added by the configurator (see “Add a Presentation instance” chapter).

Copy the following AutoInstall files

/var/autoinstall/Rxx.y/export_DIR/export_NMS.pl /var/autoinstall/Rxx.y/data/NETypeReleaseList.csv

from target_host to source_host(s).

Log as root user on source_host and execute

...,root,root # mkdir -p /alu/DEPOT/export_DIR [Enter]

Copy the export_NMS.pl and NETypeReleaseList.csv autoinstall files in the created /alu/DEPOT/export_DIR directory ensuring to preserve the right format in case a DOS support is used (execute a Dos2UNIX command if needed).

Extract configuration data from source_host(s) executing the following commands:

...,root,root # cd /alu/DEPOT/export_DIR [Enter]

...,root,root # touch master_flag [Enter]

...,root,root # ./export_NMS.pl /alu/DEPOT/export_DIR [Enter]

N.B. export_NMS.pl procedure generates in the /alu/DEPOT/export_DIR directory one NMS_parameter file for each master instance configured in the source_host. e.g. file create for SDH/PKT co-hosted are (source hostname it080083): # ls /alu/DEPOT/export_DIR/*.NMS_parameter it080083_PKT_1.NMS_parameter it080083_SDH_1.NMS_parameter

Copy generated NMS_parameter files on target_host in /var/autoinstall/Rxx.y/export_DIR/ ensur-ing to preserve the right format.

We are now ready to access the AI configuration Tool (3.1) to configure the network bridges (3.1.1) and to create the new configuration (3.1.2).

The exported configuration files can be imported in the new configuration in two different ways: via option“Create empty R11.2 configuration“ and then using the “green arrow” button or via option “Create new R11.2 configuration fron file“, see “3.1.2.2”. The exported configuration files can be provided one by one or as a compressed file (see configurator windows for supported compressed format).

Once all the exported files have been uploaded, the configuration will be shown.

Installation Guide




The configurator tool highlights in red the missing/wrong parameters. Before proceeding, it is therefore necessary to visit in Edit mode each uploaded instance to propertly correct the highlighted field before to proceed with configuration editing (3.1.3) or entering the global settings (3.1.3.5) to complete the config-uration and run the installation.

Installation Guide




Installation Guide




4 Web Desktop and Client PC

4.1 Web Desktop

Web Desktop is the NR9.6 available mechanism to access to 1350OMS Network Management software GUI's by a PC connected in the internet. Therefore, having a PC able to connect to 1350OMS applicationinstalled, it is possible to start a connection in two different ways.

– XT emulation modality: by starting a X terminal emulation using GoGlobal UX.

This modality has to be used for SW installation, customization and configuration and in order to get access to any GUI's which are not compatible to Web Desktop.

– Web Desktop modality: by accessing to Web Desktop starting a web browser and connecting to the server with 1350OMS software installed.

This modality has to be used for normal 1350OMS Network Management software use (e.g.: pro-visioning, alarms supervision, ...).

4.1.1 Connection to Web Desktop

In order to connect to Web Desktop, execute the following steps.

Start the web browser program on the PC and specify in the address field the IP address of the 1350OMS server machine to be connected.

N.B. connection is supported only by supplying IP address of server LAN 0 (zero) port.

N.B. If hostname is specified (instead of IP address), some application could not behave cor-rectly.

N.B. If the PC was previously used to connect to other 1350OMS machines remember to clean-up the Web Desktop cache and runtime directories.

In case of first connection of the PC to a 1350OMS machine, consider that some minutes will be necessary to download on the PC the Java software that must run locally on the PC: wait until the operation is com-pleted.

N.B. This behaviour will be adopted for ALL GUI's that will be started for the first time.

A window will be displayed, asking for directories to be used for Java temporary files and cache: if default locations are changed, then be sure to specify DIFFERENT directories for temporary files and for cache.

A web portal will be displayed, allowing to enter within the web desktop

Installation Guide

Web Desktop and Client PC



Figure 63. Web Desktop Login

N.B. Once the web portal window is displayed on the PC, a popup window will be opened, informing that security initialization is on-going - BEFORE OPENING ANY GUI, please wait until another popup window is opened, informing that security initialization has been completed (~ 1-2 min-utes)

N.B. it is necessary that PC date and time are aligned to the server, so that the differences is no more than 5 minutes, otherwise some applications (e.g.: PMC GUI) will not start and/or will not work correctly.

Click to Enter. Insert Username and Password to enter, at first login, for security reason it will be requested to setup a new password.

N.B. Do not use the " (quotes) character for Web Desktop operator password.

Figure 64. Web Desktop password

Installation Guide




4.2 Client PC

The minimum HW configuration for PCs is defined as follows:Processor: Intel Dual Core processor - 1.8 GHz clockMemory: Minimum: 2GB RAM – Suggested: 3GB RAMHard Disk available space: 10GB

Software requirements:Operating System: Microsoft Windows XP SP2 or higher.Pre-installed SW: Internet Explorer 7

JRE 1.6

4.2.1 Pagefile configuration review

Windows Pagefile must be increased to 4GB following this procedure:

a) Open Windows “Control Panel” and look for “System” icon.

b) Double click on System icon to open “System Properties” window.

c) Locate and select “Advanced” tab and click on “Setting” button in “Performance” section.

d) In “Performance Options” window click on “Change” button shown in “Virtual Memory” section.

Installation Guide




e) In “Virtual Memory” window change both initial and maximum size to 4092.

Installation Guide




N.B. If shown recommended value is higher than 4092, set the recommended value instead.

4.2.2 Host Configuration

In order to have full access to 1350 OMS GUI's via Web Desktop, the PC must be configured so that the server can be identified with hostname. This can be obtained via Distributed Name Service (DNS), whenavailable and configured, or by adding the server hostname / IP address in the following file:

C:\WINDOWS\system32\drivers\etc\hosts

N.B. This requires the MS Windows Administrator rights

In order to have a fast and reliable connection between Java renderer applications running on the PC and the applications running on the server, it is strongly recommended to configure Java so that proxy is not used. In order to do this, open on your PC:

Control Panel -> Java -> Network Settings

Select:

Direct connection

Apply the configuration (clicking on OK button)

N.B. After this configuration, if Internet is configured with navigation by a proxy, then con-sider that java applications started by Internet will no more run by the proxy.

Installation Guide




4.3 Troubleshooting

4.3.1 WebEnabler cache

Before to open a Web Desktop connection from a PC to the upgraded server, it is strongly recommended to cleanup PC Web Desktop cache, runtime and web directories.

N.B. Verify in the file “C:\web\LsmBinder\conf\paramsetting.xml” the correct name of directory.

4.3.1.1 Cleanup Cache Directory

Remove the directory “C\tmp\cacheDir”.

4.3.1.2 Cleanup Runtime Directory

Remove the directory “C\tmp\runtimeDir”.

4.3.2 Manual start of WDM-mediator

Manually restart the process via PMC GUI.

4.3.3 Manual start of ces-mediator


4.3.4 Manual start of 1350OMS PKT CESSDH


4.3.5 EML domains cannot be displayed

It is possible that MSGUI does not display correctly EML domains: this is due to a bad synchronization with Topology Manager. As recovery action restart the Topology Manager-IM via PMC GUI and re-apply the EML domain query.

4.3.6 hosts file configuration for SMF usage

In order to be able to use the SMF the IP addresses of the HOST and of the VMs must be defined into the hosts PC file (C:\WINDOWS\system32\drivers\etc\hosts).

4.3.7 adjust file format modified on wrong depot transfer

Here below an example of the typical errors on wrong file format in delivery:

Error: patch </VD_LIBRARY/PNM-GS/1350OMS_PNM-GS_6.6-1.13.tar.gz> not referred by <PNM-GS> PkgList.txt Error: WA file <rmvOldPkg.sh^M> not existing in FTSGUISVR depot>

Installation Guide




In order to solve it execute, as root user, the following commands:

..,root,root # cd /VD_LIBRARY [Enter]

..,root,root # for file in `find . -type f -name \* | grep -v -e '.tar.gz' -e '.qcow2.img' -e .rpm -e '.iso'` ; do dos2unix $file; done [Enter]

4.3.8 Service not starting on Presentation

The problem is due to a port conflict with other services that request dynamic port assignement, to solve it execute, as root user from the AI-driver host to the Presentation the following commands:

..,root,root # ssh <presentation-ip-address> /alu/Kernel/script/KernelServices stop [Enter]

...,root,root # ssh <presentation-ip-address> /alu/Kernel/script/KernelServices start [Enter]

Installation Guide




Installation Guide




5 Post InstallationThis chapter describes some actions that may be required after the initial installation was completed suc-cessfully.

5.1 Add New 1350 OMS “EML Master”/ “OIS Master” / ”Presentation” Virtual Machine

This section provides a procedure to add a new 1350OMS EML Master VM or a new 1350OMS OIS Mas-ter VM or a new 1350OMS Presentation VM.

Access the 1350OMS configuration Tool on the host server (3.1), select the release of the 1350OMS (Fig-ure 22.) and then the configuration to update (Figure 23.). Add the new EML/OIS Master instance as already described in section 3.1.3.3 or the new Presentation instance as described in section 3.1.3.4 and then save the changes as in 3.1.3.6: three configuration files for each instance of the bench, including the new EMLs/OIS/Presentation, are generated in /var/autoinstall/R11.2/generated/<bench_prefix>.

N.B. If needed create the new host and assign the crested EMLs/OIS/Presentation instances to it. (Figure 31.)

Open a VNC session on to the host server and login as root user:

...,root,root # cd /var/autoinstall/R11.2 [Enter]

In case the a new host has been added for the new instance(s) allows remote access through SSH from "AI Driver host" to the new addes host with the following command:

...,root,root # utilities/allowToRemote.sh <new_HOST-IP-address> [Enter]

Once the host has been added it would be possible to add the VM to the host.

In order to add the new instance(s) and manage custom/configuration on the existing benches execute the following commnad:

...,root,root # ./1350OMS_addVMs.sh prefix=<bench-name> depot=<depot-directory> [Enter]

N.B. The 1350OMS_addVMs command performs the following steps:

a) Deploy the new VM(s)

b) Update /etc/hosts and AI configuration on the existing VMs

c) Run custom/config/integration/federation on the new VM(s) (EML / OIS / Pres)

d) Add the new EML clients on existing VMs (except the other EMLs) and run integration/fed-eration

Thr already existing VMs continue to be running and operator could be connected while 1350OMS_addVMs performs the above steps.

N.B. If the adddition was made in a 1350 OMS HA context you must also start the 1350OMS-HA on DRC and on NOC executing the commands described in “1350OMS HA startup and checks”.

N.B. If a new 1350 OMS “OIS Master” instance is added execute the w/a described in 3.5.1 .

Installation Guide

Post Installation



5.2 Addition 1350 OMS HA

This section provides the procedure to add the 1350 OMS HA.

PRE-CONDITION

– DRC server(s) is(/are) already installed with operating system bootable (2.3) and AI with sc-vadeploy is installed (2.3.4.2)

– DRC server(s) is(/are) connectable from AI-Driver (see 3.3.1) (the AI-driver connected to create the configuration from Web-UI)

– 1350 OMS load is available in all the hosts of the bench in the same directory (see 3.3.1)

In the following instructions to add HA DRC bench it is assumed:

– NOC (master server) becomes active and DRC (spare server) becomes the stand-by

– new server (DRC-host) is added in the configuration to host ONLY DRC VMs

5.2.1 Add and configure the DRC instances

The first step to execute in the configuration of the 1350OMS-HA in the already configured instances of the bench. Access the configuration tool as described in 3.1 then select the release and the configuration to manage, the configurated bench appear.

“Edit” the Master instances in order to configure the HA as described in section 3.1.3.3.2 then “Edit” the Presentation instance in order to configure the HA as described in section 3.1.3.4.1

5.2.2 Assign the DRC VMs to host

The added/configurated DRC instances must be assigned to the DRC host, to do that follow the instruction described in section 3.3.1 .

In case the DRC VMs have to be distributed on multiple host servers (not only on spare-host-address) it is requested to:

– configure the hosts in addition to "main" noc and drc servers (also the hosts previously defined and different from noc and drc servers)

– assign the VMs on the new hosts

Both actions are managed by trough manageHosts.sh utility described in “Multi Host configuration” (3.3.2).

5.2.3 Sync bench configuration

The already run installation procedure (3.2) generate a file (<prefix>_bench) containg the installed bench configuration, this file must be updated adding the new HA configuration, to do that perform the following actions.

Open a VNC session on to the host server and login as root user:

Installation Guide

Post Installation




...,root,root # utilities/createBenchConfig.sh prefix=<bench-name> [Enter]

5.2.4 DRC installation

Execute the following sequence of actions in order to install the DRC.

From the AI-Drive host, as root user, execute the following commands:


...,root,root # ./1350OMS_install.sh prefix=<bench-name>_bench HA=drc [Enter]

If the NE configuration (NE selection) was updated on the 1350OMS EML master instance, the

same changes must be applied on the 1350OMS EML spare instance.

Start processes on DRC:

..,root,root # utilities/execOnBench.sh <bench-name>_bench.drc complete start-force [Enter]

From opened session check if processes are running (PMC) and if emldomains are reachable (MS-GUI).

Stop processes on DRC:

..,root,root # utilities/execOnBench.sh <bench-name>_bench.drc complete stop [Enter]

5.2.5 1350OMS HA installation and configuration on NOC

Execute the following sequence of actions in order to install and configure the NOC.



...,root,root # bin/AutoInstall.sh <bench-name>_bench.noc addHA complete [Enter]

...,root,root # utilities/execOnBench.sh <bench-name>_bench.drc complete integration [Enter]

5.2.6 1350OMS HA startup and checks

Execute the following sequence of actions to properly start the 1350OMS HA and check the functionality.



Start the 1350OMS HA configuration:

...,root,root # utilities/configHA.sh prefix=<bench-name> [Enter]

Start 1350OMS HA on DRC:

...,root,root # utilities/execOnBench.sh <bench-name>_bench.drc complete start-ha [Enter]

Installation Guide

Post Installation



Open a session on the Presentation associated to DRC and check via PMC if 1350OMS HA is correctly starting on DRC. Wait for “To Stanby” transitions on DRC instances on PMC.

Start 1350OMS HA on NOC:

...,root,root # utilities/execOnBench.sh <bench-name>_bench.noc complete start-ha [Enter]

Check on opened session the 1350OMS HA status on PMC and wait for “To Active” transition on NOC instances. Open session on the Presentation associated to DRC and check 1350OMS HA via PMC. Run on both sessions MS-GUI and check if emldomain are reachable.

Start data replication from NOC -> DRC

Switch NOC -> DRC

Check in MS-GUI if emldomain are reachable at the end of the switch on the two sessions.

Start data replication from DRC -> NOC

Switch back DRC -> NOC

Check in MS-GUI if emldomain are reachable at the end of the switch on the two sessions.

Start data replication from NOC -> DRC

5.3 Change “hostname” procedure

5.3.1 Change “hostname” in a NON 1350OMS HA context

Execute the following procedure to change the VMs hostnames of a bench.

Access the 1350OMS configuration tool as described in 3.1 and edit the existing configuration (3.1.3) modifying the VM hostname(s) as needed and then save the updated configuration.



...,root,root # utilities/changeHostName.sh prefix=<bench-name> [Enter]

The system should be up a running at the end of the process. Log on Presentation VM and check if the system is running.

5.3.2 Change “hostname” in a 1350OMS HA context

Execute the following procedure to change the VMs hostnames of a bench.

Access the 1350OMS configuration tool as described in 3.1 and edit the existing configuration (3.1.3) modifying the VM hostname(s) as needed and then save the updated configuration.


Installation Guide

Post Installation




...,root,root # utilities/changeHostName.sh prefix=<bench-name> HA=drc [Enter]

...,root,root # utilities/execOnBench.sh <bench_config>.noc complete stop [Enter]

...,root,root # utilities/execOnBench.sh <bench_config>.drc complete start-force [Enter]

Log on DRC Presentation VM and check if the system is running.



...,root,root # utilities/changeHostName.sh prefix=<bench_name> HA=noc [Enter]

Start the 1350OMS-HA on DRC and on NOC executing the commands described in “1350OMS HA star-tup and checks”.

5.4 Addition of New 1350 OMS optional components (CPB, ISN, IOO)

An optional component can be added later when 1350OMS is already configured.

All systems that will use an optional component (i.e. SDH, NPR, PKT, WDM) must be re-customized and reconfigured according to the following scheme:

The first installation of an optional component, on a system already confiigured, requires the following main steps :

– Login the system as root user with a graphical session.

...,sys,root # cd /alu/Install_Wizard [Enter]

– Start the automatic installation procedure by executing:

...,sys,root # ./Install.sh <optional component> -install [Enter]

The procedure will ask you for Depot hostname (<VM hostname>) or address (<VM address>) and the Depot path ( insert /VDs/IW ).

– Start the System Customization procedure by executing for each System Component (EML, SDH/NPR, PKT, WDM):

...,sys,root # ./Install.sh <system component> -custom [Enter]

The following choice will be displayed:

Do you want to execute <system component> Custom? [y|n|q]

EML SDH/NPR PKT WDM

ISN X X X

IOO X X X X

CPB X

Installation Guide

Post Installation



Select “y” to execute, the “System, Instances List" window will be shown on the screen after a few sec-onds, it allows you to select the instance that you want customize.

Select “Choose_one" and then <system component> , then select “Apply & exit" in the Actions menu.

Then custom “Parameters Definition" window will be shown on the screen after a few seconds, it allows you to set the relevant custom variables, accept the already in values selecting “Apply & exit" in the Actions menu to start the execution.

In case of EML, the “Custom Product Selection EML <Instance Id>" window will be shown on the screen after a few seconds, accept the already in values selecting “Apply & exit" in the Actions menu to start the execution.

In case of SDH, the “Parameters Definition" window will be shown on the screen after a few seconds, accept the already in value “4” for MULTIEPIM CONFIGURATION, then select “Apply & exit" in the Actions menu to start the execution.

In case of PKT and WDM non further action is required.

The procedure will complete when the [Dismiss] button will be enabled.

– Start the System Configuration procedure by executing for each System Component (EML, SDH/NPR, PKT, WDM):

...,sys,root # ./Install.sh -config [Enter]

The “System Configuration" panel will be shown, select the number of the instance for which you have installed one or more additional component(s) and press [Enter]. The operation must be executed for every involved System Component. Refer to the Administration Guide of each <system component> and of every <optional component> installed.

5.5 Integration - Federation

When the previosly described configuration have been successfully completed, for each virtual machine you have to:

1) Login as root user.2) Start the global integration and federation script by executing the following procedure.

...,root,root # /alu/Install_Wizard/etc/1350_Integration-Federation.sh [Enter]

The procedure will apply automatically all the necessary integrations.

Installation Guide

Post Installation



6 TroubleshootingHere after is shown how to solve some trouble can occur during the installation, and how to proceed when possible.

6.1 Identify a Failure Condition

Before proceed with the troubleshooting it is suggested to identify the problem. It also important to dis-tinguish between messages issued during the normal behavior and real error messages.

These is a messages issued at login time to advise the operator that an installation activity is in progress:

********************* WAIT - INSTALLATION IN PROGRESS ******************* Do not alter environment, check log file in /SCINSTALL/scinstall.log ***************************************************************************

This is not an error message, it just advise you that an installation activity is in progress, in this case it is better wait until the activity will be terminated.

The following message will be issued when an error is met during the automatic software installation.

**************** THIS SYSTEM IS NOT CORRECTLY INSTALLED ***************** To fix the problem, check the log file in /SCINSTALL/scinstall.log ***************************************************************************

N.B. Some system reboot are foreseen to correctly carry on the installation, that means don't worry if the system reboot automatically.

6.2 Recoverable Faults

Hereafter some example of recoverable error that can occur during platform software installation.If no one of them help you to fix the problem, do not attempt fix the error in different ways, but refer to Alcatscmanageswp Abnormally Terminated

Installation Guide

Troubleshooting



6.3 Device Full

Sometimes a file systems can get full, this situation can occur because different reasons, hereafter some of them are explain.

6.3.1 Device full

These two file systems can get full because of core file created by program termination, in this case is suggested to remove or copy in a different location the core files.

If the core file removal is not enough to reach an appreciable amount of free space, it is possible to extend the file system. The file system extension can be executed when there are not allocated physical extent on the logical volume or there are unused hard disks, and it is possible to perform a reboot of the system.

The command “scextendfs -i" can be used to check how many free Mbyte are still available on the current volume group configuration.

...,sys,root # scextendfs -i [Enter]

The command output will be like the following:

___________________________________________________________________________ Volume Group Free Space vg00 FreePE 172 (MBytes 11008) (pvg0=172) ___________________________________________________________________________ Hardware detection in progress, please wait ........ Total disk(s) found = 6 Total CDRoms found = 1 Press [Enter] to continue...

___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup ___________________________________________________________________________ c2t0d0 34720 0/1/1/0.0.0 Pri_Boot _Main_ vg00 c2t1d0 34720 0/1/1/0.1.0 _(free)_ ______ __________ ___________________________________________________________________________ Press [Enter] to continue...

N.B. If you have a disk mirror protection, the file system extension can ask for more than one disk.

Before proceed within a 1350OMS-HA Data Sharing environment you have to check that the disks you want to use are not already in use from a different system.

If all precondition are met, you can enlarge the file system by entering the command:...,sys,root # scextendfs <file system mount point> <desired free space> [Enter]

Installation Guide

Troubleshooting



Analyze Mount Point:"/usr" Request free MegaByte(s): 100 Evaluate size MegaByte(s): 1248 Extend Mount Point "/usr" to 1248 MByte "/usr" successfully extended, new size will be available on next reboot ___________________________________________________________________________ System need reboot x complete extension of file system current in use ___________________________________________________________________________

The message “System need reboot x complete extension of file system current in use" means that the extension will not available until system reboot.

6.4 Generating a SOSReport

When investigating bugs, Alcatel-Lucent may require to generate a SOSReport on the affected system and provide the resulting file.

The sosreport command is a tool that collects configuration and diagnostic information from a Red Hat Enterprise Linux system. For instance: the running kernel version, loaded modules, and system and ser-vice configuration files. The command also runs external programs to collect further information and stores this output in the resulting archive.

The sosreport command requires root permissions to run.

The sosreport command can be used both on the host and on the guest. Each invocation will gather diagnostics for the host or guest Linux installation it occurs in.

The command will normally complete within a few moments on the host. On a guest VM it may take a few minutes to complete.

Once completed, sosreport will generate a compressed a file under /tmp. Different versions use different compression schemes (gz, bz2, or xz). The file can then be provided to Alcatel-Lucent support repre-sentative (normally as an attachment to an open case).

The size of the archive varies depending on system configuration.

Installation Guide

Troubleshooting



Installation Guide

Troubleshooting



Appendix A System TipsIn this appendix some system tips are show.

A.1 System Shutdown

To safety stop the system it is suggested to perform the system shutdown. This activity allows to stop the entire system by executing the shutdown procedure of each software component. The shutdown com-mand is allowed only by root user and foresees many switches, the most used are “-r" and “-h" . The first one performs the automatic reboot, and the second have to be used when you have to switch off the sys-tem power supply, because it halts the system.

A.1.1 System Shutdown with Reboot

The system shutdown command allows to perform the system reboot, by entering:...,sys,root # shutdown -r now [Enter]

A.1.2 System Halt

The system shutdown command allows to perform the system switch off, by entering:...,sys,root # shutdown -h now [Enter]

N.B. Wait until the “RUN" lamp is switched off or the system status gets in “SHUT" on the front display before switch off the power supply.

Installation Guide

System Tips



A.2 ILO Configuration

Integrated Lights-Out (ILO) is a remote administration tool providing access over the network to server console, diagnostics and controls such as power on/off switch.

ILO also makes it possible to mount a virtual CD/DVD from a PC over the network from the ISO image of the disk. This can be used to install OS and software on the system even without physical access to the machine.

ILO can only be configured during the boot process. On a production system this would require to stop and reboot the server, with service downtime. Therefore, even if it is not planned to use ILO for the OS and software installation, it is recommended to configure ILO as part of the initial server installation and configuration actions.

Configuring ILO consists in setting up its networking parameters and its list of authorized usernames/passwords.

Although ILO is factory configured to obtain address and to publish its pseudo-random hostname on DNS/DHCP, this requires that DNS/DHCP services on the LAN are active and configured to accept such request, which is normally not the case in production server rooms.

For that reason, normally initial ILO configuration is done either (a) by simply connecting a local keyboard/video/mouse or (b) via serial port. In both cases, physical access to the server is necessary. As a general guidance, below we provide a high level description of procedure (a). You must refer to HP Proliant product documentation for model-specific instructions.

A.2.1 Connections

Start by connecting a local USB keyboard, USB mouse and VGA monitor to front ports (if available) or to back ports.

Figure 65. Connecting keyboard, monitor and mouse for ILO configuration.

Installation Guide

System Tips



A.2.2 Booting the server

Now power up the server. After about 30 seconds with screen completely blank, a start-up screen like this will appear:

Figure 66. Server start-up screen.

On most current Proliant models ILO Setup is accessed by pressing F8. Unfortunately the same key, at a different time of the boot process, is also used to access other setup menus (such as the SmartArray disk controller setup screen), so besides pressing the right key, the time it is pressed is also important. A message should appear for a short time to indicate when F8 should be pressed to access the ILO Setup. Be sure to react quickly.

A.2.3 ILO Configuration utility

If you pressed F8 at the right time, you will reach ILO Setup screen, as follows:

Installation Guide

System Tips



Figure 67. Initial ILO Screen

Move right with arrow keys to the Network menu:

Installation Guide

System Tips



Figure 68. ILO Setup: Network menu

Select NIC Setup and press Enter:

Figure 69. ILO Setup: NIC Setup

Enter desired IP address, netmask and gateway, then press F10 to save.

Now you need to change the default Administrator password for ILO remote access. To do this, move right to the User menu and select Edit, then press ENTER.

Installation Guide

System Tips



Figure 70. ILO Setup: User menu

The list of existing users appears. On a brand new machine the list includes only Administrator and it should already selected.

Installation Guide

System Tips



Figure 71. ILO Setup: User list

Press ENTER to select Administrator for editing.

Installation Guide

System Tips



Figure 72. ILO Setup: editing user details

Move down to the Password field and enter a new password, then move to Verify Password field and re-type the same password. Then press F10 to confirm and save changes.

At the end move left to File menu and select Exit. You may be asked to give several confirmations by press-ing ENTER a few times.

Figure 73. ILO Setup: exiting the procedure and completing configuration

ILO setup utility will close and ILO will reset.

Installation Guide

System Tips



Figure 74. ILO Setup: ILO reset after configuration save

A.2.4 Factory-preset password

Note that on a server still in factory new condition, until you change the ILO Administrator password, a factory-preset random password will remain in effect.

This factory-preset random password is usually printed, along with other identification data, on a sticker that can be pulled out from the front panel of the server (the exact location depends on server model):

Installation Guide

System Tips



Figure 75. Pull-out sticker with factory-preset ILO password

Installation Guide

System Tips



A.3 Smart Array Controller RAID Configuration

HP Smart Array controller implements many RAID disk protections at controller level. The suggested con-figuration for 1350OMS is: RAID 1+0 using available hard disks in pairs.

The Smart Array disk configuration MUST be done BEFORE proceeding with host installation and VM installations. Subsequent changes are not possible without loos-ing all disk contents!

To configure the Smart Array controller you can use “Smart Array Option ROM Configuration for Array” during the server boot, usually accessed by pressing the F8 key at the time a specific prompt appears.

Note that at a different time during the boot process, the same key may be used to access another setup procedure, such as ILO setup, so be sure to follow the onscreen messages and react quickly; in case you missed the right moment there will not be a second opportunity to retry during the current boot sequence, so you should reset the server and try again.

Once the Smart Array configuration screen is entered, the specific procedure to follow may vary depend-ing on the server model. You must therefore refer to HP Proliant model-specific documentation.

For reference, the general procedure (see the typical ILO Setup main menu screen on Figure 76.) is:

a) Use the “View Logical Drive” menu action to inspect the current RAID configuration, with the list of currently defined logical disks (LD).

b) Use the “Delete Logical Drive” menu action to delete, if any, all currently defined LDs. If asked, con-firm the operation.

The logical drive deletion step destroys the entire disk contents! Never execute this step unless you are sure that there is no important data on the server disks.

c) Use the “View Logical Drive” menu action to check again the configuration, in order to make sure the LD deletion operation succeeded.

d) Use the “Create Logical Drive” menu action to create a new LD by selecting all internal physical disks of the server and choosing the RAID 1+0 option. If asked, confirm the operation.

e) Use the “View Logical Drive” menu action to check one final time the configuration, in order to make sure the LD creation operation succeeded.

At the end, exit the Smart Array Configuration procedure by confirming to apply configuration actions if so requested.

Installation Guide

System Tips



Figure 76. Typical Main Menu of the Smart Array Configuration Utility

Installation Guide

System Tips



Appendix B Specific Data

B.1 1350OMS Network Management composition table

Table 4. 1350OMS Network Management composition table

checksum size name

3145274208 5152505856 1350OMS_EML_11_11.2.0.78.qcow2.img

1448059778 1060110336 1350OMS_IW_11_11.2.0.78.qcow2.img

1810560369 390070272 1350OMS_OIS_11_11.2.0.78.qcow2.img

1033856195 643682304 1350OMS_PKT_11_11.2.0.78.qcow2.img

2550733623 2889337856 1350OMS_PLT_11_11.2.0.78.qcow2.img

2031180520 549379584 1350OMS_SDH_11_11.2.0.78.qcow2.img

2712824539 137101312 1350OMS_WDM_11_11.2.0.78.qcow2.img

2949567921 6387039744 VD-MW_OS-11_0.1-1.qcow2.img

659579608 78813808 1350OMS-LX_11.2.0.79_on_top.tar.gz

checksum size name

335706909 26574 1350OMS-MW_OS-bck-11.1.0.0.0-13.x86_64.rpm

611294063 5994 1350OMS-MW_OS-conv-11.1.0.0.0-13.x86_64.rpm

1710076590 20247 1350OMS-MW_OS-repos-11.1.0.0.0-13.x86_64.rpm

2502561514 99718 1350OMS-MW_OS-sec-11.1.0.0.0-13.x86_64.rpm

2634352420 74813991 autoinstall112-1.9-62.noarch.rpm

2120063989 318052 mindi-2.1.7-1.el6.alu.x86_64.rpm

1713977927 313582 mindi-busybox-1.18.5-3.rhel6.x86_64.rpm

2736804811 953708 mondo-3.0.4-2.el6.alu.x86_64.rpm

4286234932 1575996 Poseidon-1.1.0-1.x86_64.rpm

1888442621 235460 sc-vadeploy-4.2-1.el6.noarch.rpm

1562706056 316036 star-1.5-11.el6.x86_64.rpm

278801755 154392 vsftpd-2.2.2-11.el6.x86_64.rpm

2791464683 263481 1350OMS-MW_OS-11.1.0.0.0-13.x86_64.rpm

Installation Guide

Specific Data



checksum size name

3314657921 3797504000 1350OMS-MW_OS-Boot-V11.0.0.1.0-RHEL6.4_x86_64-It3.iso

895061005 249886720 1350OMS-MW_OS-NetBoot-V11.0.0.1.0-RHEL6.4_x86_64-It3.iso

Installation Guide

Specific Data



Appendix C GoGlobal-UX Installation and Configuration

C.1 GoGlobal-UX Installation

The GoGlobal-UX software is already installed on the system.

C.2 GoGlobal-UX Installation on PC

To install the software, perform the following steps:

GOGlobal-UX PC Client software is available as go_setup executable within /opt/graphon/pc/ directory, to retrieve it you must use a secure connection via SSH, this can be done by installing on you PC a tool that allow such a transfer, we suggest Filezilla where is possible to define a SFTP connection to access server.

N.B. Be careful that SSH usage can be forbidden to root user.

When you have retrieved go_setup on you PC install it by follow hereafter procedure:

a) Double click on the executable

b) The “Install Shield Wizard" window will be opened:

Figure 77. GoGlobal-UX LogoThe installation application checks if there is a previous version installed. If a previous version is found remove it by follow the instruction in paragraph “Automatic Removal of GoGlobal-UX/Previous Version" C.2.1 at page 104 , otherwise proceed with the next point.

c) The next window will be opened showing the welcome message:

Installation Guide

GoGlobal-UX Installation and Configuration


8DG 42778 NAAA Edition 01 101/126

Click on Next to go on. Wait a few seconds the install procedure.

d) The “License Agreement" window will be opened:

Click on Yes to go on.

e) The “Destination Location" window will be opened:

Choose your destination location and click on Next to go on. Wait a few seconds the install proce-dure.

f) The “Install Shield Wizard Complete " window will be opened:

Installation Guide




Click on Finish to go on.

g) The “Connection" window will be opened

You have to insert the Server Address of the machine that you want to be connected to.Click on Connect. The “Authentication" window will be opened

You have to insert:

Username Password

Click on OK. GoGlobal-UX will open a connection with the configured machine.

Installation Guide



8DG 42778 NAAA Edition 01 103/126

C.2.1 Automatic Removal of GoGlobal-UX/Previous Version

If when installing GoGlobal-UX the setup procedure detects that a previous version is already installedthe application asks you the authorization to remove it by issuing the window:

To upgrade the software press the “O.K." button.

Then the script ask you to remove also the GoGlobal user setting, if you want to maintain the connection descriptions press “NO" button.

The the previous GoGlobal-UX will be removed from the PC.

When the removal will be completed the following window will be shown on the screen.

You can now install the new version of the software by starting again the installation application.

Installation Guide




C.3 GoGlobal-UX license

The GoGlobal-UX X-Emulator for MicrosoftTM Windows personal computers requires to be authorized with a license key. The permanent licenses provided are network floating, that means you need one or more “license server machine" in your network.

C.3.1 License servers definition rules

Before to require the GoGlobal-UX license(s), you have to decide how many and what will be the license server machine(s) in your network, in accordance with the following rules:

– The license server MUST be a physical server.

– If you have three or more physical servers, you have to setup a “Three Redundant License Servers" configuration, in accordance with the following rules:.• the three license server machines should be located physically close to each other (if possible).• never configure redundant servers with slow communications or dial-up links.With three-server redundancy,only one of the three servers is 'master', capable of issuing licenses. Since all clients must contact the 'master', all clients must have reliable networking to a single node.

– if in your network there are less than three nodes, you have to define a the license server, and all the required licenses have to be loaded on that server.

On the license server machine(s) will be loaded the license(s) data obtained as showed in the paragraph C.3.3.

C.3.2 Retrieve License Servers Identity

Meaningful only for the license server machine(s).

When you have selected the license server machine(s), for each of them you have to retrieve the machine identity by executing the following commands:

a) Log in as root on the machine.

b) Get the hostname of the current machine:

..,sys,root # uname -n [Enter]

c) Get the FLEXlm host ID of the current machine:

..,sys,root # /opt/graphon/bin/lmhostid [Enter]

The obtained data will be used in a successive phase of the license request activity.

Installation Guide



8DG 42778 NAAA Edition 01 105/126

C.3.3 Permanent License Request

Meaningful only for the license server machine(s).

After that, you can to require the necessary license(s) to activate GoGlobal-UX on your machine(s) visiting the GraphOn Licensing web site through your web browser, by typing one of following URLs:

For three redundant: http://license.graphon.com/user/redundant_pcode.cgi

For single node: http://license.graphon.com/user/

The following window will appear:

Figure 78. GraphOn License WEB Page

Scroll down along the window using the scroll bar and fill the following fields about the required registration information:

– Name (1)– Company (1)– Address & Address2(1)– City (1)– State/Province (2)– Country (1)– Postal Code (1)– Phone (1)– Email Address (1)

(1) Introduce the data of the reference person near the customer or the your own ones. (2) Leave it as “Not Specified" when the system is located outside of U.S.A..

Fill in the data, then click on Next> button to continue with the next window.

Installation Guide




The “Software Agreement" window will appear:

Figure 79. GraphOn License WEB Page - Software AgreementScroll down until the bottom of the window using the scroll bar and click on I Accept button to continue.

The “License Information" window will appear dependig from the initial URL used to connect GraphOn WEB site:

Figure 80. GraphOn Info request window for Single server

Installation Guide



8DG 42778 NAAA Edition 01 107/126

Figure 81. GraphOn Info request window for Three Redundant servers

N.B. If you have one or more “PURCHASED GraphOn LICENSE FOR ALCATEL USE OR RESALE" document, you have to repeat the following operations for each “Product Code" value indicated.Like this, you will obtain one or more NOT demo licenses.

Scroll down along the window using the scroll bar and fill the following fields:

– Product Code (see the “Product Code" value on the “PURCHASED GraphOn LICENSE FOR ALCA-TEL USE FOR RESALE" document if present)

– Host Name (see the paragraph C.3.2)– Host ID (see the paragraph C.3.2)

Now if you have the “Three Redundant License Servers" configuration you have to set “YES" in the box close to the label “Are you using redundant servers?", and fill in the three couple of information: Host-name and Hostid with the data of each license server.

and click on Get License button to continue.

Installation Guide




Figure 82. GraphOn License WEB Page - License Output Example

Put the showed data in the license file of the license server machine (see the paragraph C.3.4.1.1) and click on the Back button to come back to the “Product Code" window to require (eventually) another license otherwise, if you are terminated, click on File and Close option to exit from the web browser.

C.3.4 GoGlobal-UX authorization procedure

GraphOn Corp. provides both permanent or demo license, hereafter some information to help you to con-

figure the GoGlobal-UXTM license files and daemons.

C.3.4.1 Permanent License

GoGlobal-UXTM permanent licenses are provided as network floating point, that meas you have to pro-mote one or three machines a License Server and all the other will be License Client.

To be able to use them you have to perform the following actions:

1) Store the authorization key in the license file.2) Configure the license servers machine(s).3) Start the license server daemons.4) Configure license client system(s) (if any)

Installation Guide



8DG 42778 NAAA Edition 01 109/126

C.3.4.1.1 Store the Authorization Key in the License File.

The first activity is to store the license authorization key previously obtained by GraphOn WEB page (see C.3.3 at page 106) in the /opt/graphon/etc/license.dat file of any the license server machine. To create this file, use the command (as root):

..,sys,root # vi /opt/graphon/etc/license.dat [Enter]

N.B. During the insertion of the license data, you have to modify the line of SERVER definition adding the port number 27001 at the end-of-line (see example below).

After that, save and quit the file pressing [Esc] and typing :x! and [Enter].

Example of /opt/graphon/etc/license.dat file with three servers and two licenses ("INCREMENT" options) defined:

# NOTE: You can change the hostname on the "SERVER" line.# You can also add a port number after the hostid on# the "SERVER" line, like:# SERVER hostname.domain.com 00HOSTID0 27001# which will make the lmgrd managing this file use# port 27001.# Most other changes will invalidate this file. # ISSUED_DATE=23-jan-2002#SERVER host_c 77fd17feSERVER host_d 77df65d1SERVER host_e 7751b870VENDOR graphonINCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164

Add TCP port number (27001) at any line beginning with SERVER:Example from:

SERVER host_c 839dc26to:

SERVER host_c 839dc26 27001

Copy this file on each license server when the three redundant configuration is foreseen.

C.3.4.1.2 Configure License Server(s)

Now you have to configure License Server machine(s) that need to provide the GoGlobal-UX floating license on the network.

Installation Guide




C.3.4.1.2.1 Configure license_server.dat file

An Alcatel-Lucent extension to the GraphOn license management is the license_server.dat file. This file has to declare all the license servers useful for retrieving license from any host need to use them licenses, including the license servers hosts themselves.

The easy to proceed is create these files on the license server(s) and them distribute them to the client when configuring it.

Each time you change the license_server.dat file the changes will be recognize only at next GoGlobal-UX start-up.

To declare the license server machines you have to create the file “/opt/graphon/etc/license_servers.dat" and fill in it with the following syntax:

SERVER <host> <port>

Where:SERVERis a keyword

<host> means the hostname or the IP address of the license server

<port> is the IP port number stored in the license.dat file as fourth field of the linestarting with SERVER, if that field is blank 27001 have to be used.

Example: Use the command (as root):

..,sys,root # vi /opt/graphon/etc/license_server.dat [Enter]

create the file so that it contains the following data:

SERVER host_c 27001 SERVER host_d 27001 SERVER host_e 27001

Save typing :x! and [Enter].

Copy this file on each system that have to be able to run GO-Global UX graphical interface, to allow it the GO-Global UX licence retrieval.

C.3.4.2 Start License Server and GraphOn Daemons

When both license.dat and license_server.dat files have been properly configured on all the License Server machine(s) you can proceed with the daemon start-up.

Because start-up launches both License and GraphOn Daemons, it is advisable to execute the daemon stop before. The entire procedure will be:

...,sys,root # service goglobalux stop [Enter]

...,sys,root # service goglobalux start [Enter]

When the daemons will be started on the single license server on at least two license server nodes for the three redundant configuration, you will be able to open a GoGlobal-UX 2.0 session from any PC to the license server machine.

Installation Guide



8DG 42778 NAAA Edition 01 111/126

ibamba

Highlight

ibamba

Highlight

ibamba

Highlight

créer sur chaque VM le fichier license_server.dat avec la liste des serveurs et les ports associés. puis le fgaire de même dans le fichier /etc/hosts

ibamba

Highlight

C.3.4.3 Configure License Client System(s)

To be able to access the server via GoGlobal-UX you need to get a license, this license will be granted by the license server(s) via network, that means any system acting as license client has to be able to con-nect the license server(s) via network. Moreover the license server(s) have to be referred by name.

C.3.4.3.1 Verify License Server Connectivity

Before starting the client machine configuration you have to verify the license server machine(s) connec-tivity, the easiest way to do it is try a ping to any license server host name:

..,sys,root # ping <Hostname> [Enter]where <Hostname> is the name of the remote license server machine(s).

– If the server replies the “ping" request an output like the following will be provided:

,sys,root # ping hostc 64 2 PING hostc: 64 byte packets 64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms 64 bytes from 192.202.21.8: icmp_seq=1. time=0. ms ----hostc PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0

– Otherwise, there is something wrong. From the error message issued by telnet you can have an idea of the problem.

• ping: Unknown host <Hostname>Means the license serve <Hostname> is not defined in the host name repository, if you know also license server IP address you can add it to the host name repository /etc/hosts. When the license server hostname will be present in the host name repository retry ping command.

• 2 packets transmitted, 0 packets received, 100% packet lossIf no one of the "ping" request is replayed, the are three know possibility:

a) The remote server is down.b) The remote server is not reachable because the IP address is wrong.c) The remote server is not reachable because there is no known route on the network

First of all it is better to verify that the server is running. It the server is running check on the /etc/host file if the IP address defined for the specified server is correct. If also the IP address is correct, the reason can depend by the Default Gateway, check is adefault gateway si defined and reachable. If you do not know name and IP address of the network default gateway refer to the network administrator.

Installation Guide




C.3.4.3.2 Verify License Daemon on Server

When the license server machine(s) are reachable, you can also verify on each one of them if the license daemons are running on these machine(s). this can be done with the following procedure:

N.B. This check can be done only if the license server machine(s) are already configured.

..,sys,root # export LM_LICENSE_FILE=27001@<Hostname> [Enter]

..,sys,root # /opt/graphon/bin/lmstat -a [Enter]

If the file license daemons are active, an output like the following will be displayed:

lmstat - Copyright (C) 1989-2002 Globetrotter Software, Inc. Flexible License Manager status on Fri 12/5/2003 10:07

License server status: 27001@host_c,27001@host_d,27001@host_e License file(s) on host_c: /opt/graphon/etc/license.dat:

host_c: license server UP (MASTER) v8.2 host_d: license server UP v8.2 host_e: license server UP v8.2

Vendor daemon status (on host_c):

graphon: UP v8.2

Feature usage info:

Users of bridges: (Total of 2 licenses available)

N.B. The shown output is related to a three redundant server configuration, if you have a single license server, the data shown with italic font will be not shown.

Otherwise an error message advise you of a problem, check the status of the daemons on the license server them selves.

C.3.4.3.3 Copy the license_server.dat File from a License Server

All the configuration precondition are now verified, it is possible to configure the license client machine, the configuration consists only in creating a copy of the license_server.dat file from a license server machine to this one. Like for servers, when the license_server.dat file is created or modified the daemons have to be stopped and started to catch the changes.

Installation Guide



8DG 42778 NAAA Edition 01 113/126

C.3.4.3.3.1 Check the License Server

In order to check the correct definition of the license server in the license_server.dat file you can execute the script /opt/graphon/etc/check_server.

..,sys,root # /opt/graphon/etc/check_server [Enter]

If the configuration is correct the output have to contain one set of line for each server defined, like the following example:

lmstat - Copyright (C) 1989-2002 Globetrotter Software, Inc. Flexible License Manager status on Fri 12/5/2003 10:20 License server status: 27001@host_c,27001@host_d,27001@host_e License file(s) on host_c: /opt/graphon/etc/license.dat://: host_c: license server UP (MASTER) v8.2 host_d: license server UP v8.2 host_e: license server UP v8.2 Vendor daemon status (on host_c): graphon: UP v8.2 Feature usage info: Users of bridges: (Total of 5 licenses available)

C.3.4.3.4 Re-Start the GraphOn Daemons

Because server start-up launch GraphOn Daemons, it is advisable to execute the daemon stop before. The entire procedure will be:

...,sys,root # /sbin/init.d/goglobalux stop[Enter]

...,sys,root # /sbin/init.d/goglobalux start[Enter]

Now the system ready, you can open a GoGlobal-UX 2.1 session from any PC to the this machine until at least one license is available on the servers.

Installation Guide




C.3.5 Add a new license(s)

Sometimes in the system live it is necessary to increase the number of users, that means also the number of concurrent session have to be increased. To add a new license on a running the license server machine without close the current open interfaces, you have to proceed this way:

Do not mix permanent floating authorization key with demo one in the same file!

a) Buy the GraphOn license(s).

b) Require the authorization key via GraphOn WEB Page providing the same host ID of the already requested keys (the host id are related to the license servers!). Hereby an example of a new autho-rization key requested for the license servers already see in the paragraph C.3.4.1.1 at page 110. You can see the server lines have the same values in the third field that means the same host ID.## NOTE: You can change the hostname on the "SERVER" line.# You can also add a port number after the hostid on# the "SERVER" line, like: . .# ISSUED_DATE=23-jan-2002#SERVER host_c 77fd17feSERVER host_d 77df65d1SERVER host_e 7751b870VENDOR graphonINCREMENT UX graphon 2.0 permanent 1BB31C150136 \ user_info="Paolo Rossi\ [email protected]" ISSUER="GrapOn \ Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \ 1996-2002 GraphOn Corporation. All Rights Reserved" ck=45

c) You have to copy the INCREMENT line(s) from the just received authorization key a the end of the /opt/graphon/etc/license.dat file:

N.B. When a back slash “\" is present at the end of line, also the next line have to be included.

..,sys,root # vi /opt/graphon/etc/license.dat [Enter]

Installation Guide



8DG 42778 NAAA Edition 01 115/126

1) Move to last line in file and insert the INCREMENT line(s). For example, if you have the autho-rization key shown at page 110 active on the system, and receive from GraphOn the one shown at page 115, the resulting file will be:## NOTE: You can change the hostname on the "SERVER" line.# You can also add a port number after the hostid on . .## ISSUED_DATE=23-jan-2002#SERVER host_c 77fd17fe 27001SERVER host_d 77df65d1 27001SERVER host_e 7751b870 27001VENDOR graphonINCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164INCREMENT UX graphon 2.0 permanent 1BB31C150136 \ user_info="Paolo Rossi\ [email protected]" ISSUER="GrapOn \ Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \ 1996-2002 GraphOn Corporation. All Rights Reserved" ck=45

2) Save and exit vi file pressing [Esc] and typing :x! and [Enter].

d) Then ask license daemon to re-read the license.dat file:..,sys,root # cd /opt/graphon/bin [Enter]..,sys,root # ./lmreread -c ../etc/license.dat [Enter]

After completing these steps, the new GoGlobal-UX licenses will be available.

C.3.5.1 Demo Licenses

GoGlobal-UXTM demo license can be retrieve from the GraphOn Web server. The demo license are node locked, and to use them you have just to copy the authorization key into the license.dat file, and delete license_server.dat if exists.

Installation Guide




Appendix D Poseidon Installation and Configuration

D.1 Poseidon License Management Configuration

Poseidon is the license software manager used to authorize the Alcatel-Lucent Software execution.

N.B. THE AUTHORIZATION LICENSE REQUEST CAN BE EXECUTED ONLY BY AUTHORIZED ALCATEL PERSONAL.

The package foreseen to manage network floating license, that means you must define one or more sys-tem in your network to perform the license server task.

– The license server MUST be a physical server.

– If you have three or more physical servers, you have to setup a “Three Redundant License Servers" configuration, in accordance with the following rules:.• The three license server machines should be located physically close to each other (if possi-

ble).• Never configure redundant servers with slow communications or dial-up links.• The three servers have to be reliable.With three-server redundancy, only one of the three servers is 'master', capable of issuing licenses. Since all clients must contact the 'master', all clients must have reliable networking to a single node.

– if in your network there are less than three nodes, you have to define a license server, and all the required licenses have to be loaded on that server. As a special case, if you have only one physical host server where all Virtual Machines run, the typical configuration is to define the host server as the license server, and to configure Virtual Machines so that they refer to the host as their license server.

The license have to be required providing the host identifier of the license server(s). Do not provide the host identifier of the machine where the application is planned to be run.

D.2 Retrieve License Servers Host Identifier

When you have selected the license server machine(s), for each of them you have to retrieve the host identifier by executing the following commands:

a) Log in as root on the machine.

b) Get the hostname of the current machine:..,sys,root # uname -n [Enter]

c) Get the host identifier of the current machine:..,sys,root # /opt/poseidon/bin/lmhostid [Enter]

Then fill-in this one of these forms:

Table 5. Three Server Redundant License Form

Installation Guide

Poseidon Installation and Configuration


8DG 42778 NAAA Edition 01 117/126

Table 6. Single License Form

D.3 Require the Authorization License

The license can be require via Alcatel-Lucent Intranet Web, by authorized Alcatel-Lucent personal onlyto https://nmfactory.web.alcatel-lucent.com/Welcome.aspx/.

6.4.0.1 Store the Authorization Key in the License File.

When you receive the license authorization key, you have to edit it by adding the port number as provided in the GoGlobal license at the end of each “SERVER" line as show in the following example:

From: SERVER hosta 839dc26To: SERVER hosta 839dc26 <port number>

Then store the resulting file in the following file of any machine that have to execute Alcatel-Lucent TNM software:

/opt/poseidon/etc/license.dat

Then start the Poseidon software on it, by entering the command:...,sys,root # service poseidon stop Enter]...,sys,root # sevice poseidon start [Enter]

Don't worry if no daemon is started on the machines that are license client.

D.4 Check the License Status

To check the license server availability and license status enter the command:...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat [Enter]

Hereafter an example of the command output. It is divided in four sections: title, server status, vendor dae-mon status, and feature usage.

The title just shows the version of the license manager.lmstat - Copyright (c) 1989-2003 by Macrovision Corporation. All rig... Flexible License Manager status on Tue 7/20/2004 18:15

The server status shows the license server names, which is the current license server master and

Host Name Host Identifier

Host Name Host Identifier

Installation Guide




License server status: <port number>@hosta,<port number>@hostc,<port num-ber>@hostd License file(s) on hosta: /opt/poseidon/etc/license.dat: hosta: license server UP (MASTER) v10.8 hostc: license server UP v10.8 hostd: license server UP v10.8

The vendor daemon show the status of the software used to control the license, it must contain “alcatel":Vendor daemon status (on hosta): alcatel: UP v9.2

Then the feature usage list, with the list of all the authorized feature, and for each one of them the user, the host and the start date of usage:

Feature usage info: Users of EML_POINT: (Uncounted, node-locked) alcatel hostb /dev/tty (v7.1) (hosta/<port number> 4406), start Tue 7/20 16:34

Installation Guide



8DG 42778 NAAA Edition 01 119/126

D.5 Add a New License

Sometimes in the system live it is necessary to increase the number of license. To add a new license on a running license server machine without interrupt the service, you have to proceed this way:

Do not mix permanent floating authorization key with demo one in the same file!

a) Retrieve the new license key from Alcatel-Lucent web, asking for the same host identifier of the first one.

b) Login a Poseidon license server system.

c) Save the current license file in a security copy by entering:...,sys,root # cd /opt/poseidon/etc/ Enter]...,sys,root # cp -p license.dat license.save Enter]

d) Add the “INCREMENT" line from the just obtained license file, to the /opt/poseidon/etc/license.dat file.

The INCREMENT line can be split in two or more ones, because of the length. If the “INCRE-MENT" line terminated with back slash ( \ ), that means also the next one have to be consid-ered as part of “INCREMENT".

e) If you have the three host redundant configuration, copy the license file on other two license servers.

f) Force the license server daemon to reread the license file by entering:...,sys,root # /sbin/init.d/poseidon reread [Enter]

g) Check again with “lmstat" (see paragraph D.4) if the number of point has been increased.

D.6 Poseidon License Server Troubleshooting

Some problem has been experienced configuring the three redundant Poseidon license servers. This paragraph summarizes these problems and show a possible solution way.

D.6.1 Redundant Connectivity

The three redundant servers work properly only if each server is able to communicate with the other two. This is the reason why it is better check the server configuration and connectivity. The easiest way to do it is try a network “ping" from each license server to any other one:

..,sys,root # ping <Hostname> [Enter]where <Hostname> is the name of the remote license server machine(s).

– If the server replies the “ping" request an output like the following will be provided:

Installation Guide




ibamba

Highlight

,sys,root # ping hostc 64 2 PING hostc: 64 byte packets 64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms 64 bytes from 192.202.21.8: icmp_seq=1. time=0. ms ----hostc PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0

– Otherwise, there is something wrong. From the error message issued by telnet you can have an idea of the problem.

• ping: Unknown host <Hostname>Means the license serve <Hostname> is not defined in the host name repository, if you know also license server IP address you can add it to the host name repository. When the license server hostname will be present in the host name repository retry ping command.

• 2 packets transmitted, 0 packets received, 100% packet lossIf no one of the "ping" request is replayed, the are three know possibility:

a) The remote server is down.b) The remote server is not reachable because the IP address is wrong.c) The remote server is not reachable because there is no known route on the network

First of all it is better to verify that the server is running. It the server is running check on the /etc/hosts file if the IP address defined for the specified server is correct. If also the IP address is correct, the reason can depend by the Default Gateway, check if default gateway is defined and reachable. If you do not know name and IP address of the network default gateway refer to the network administrator.

D.6.2 Two licence servers down

The three redundant license server fails when more than two servers are down or are unreachable, in order to reduce the risk of license failure is suggested to periodically check the license servers entering:

...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat [Enter]

Installation Guide



8DG 42778 NAAA Edition 01 121/126

Installation Guide




ABBREVIATIONS

VM Virtual Machine

VD Virtual Disk

NTP Network Time Protocol

Installation Guide

Abbreviations


8DG 42778 NAAA Edition 01 123/126

Installation Guide

Abbreviations



CUSTOMER DOCUMENTATION FEEDBACK

The meaning of this section is to collect customer feedback about this handbook.

Scope of this activity is the improvement and innovation of customer documentation through the under-standing of customer needs.

Your comments are welcome.

Please send your comment also if you appreciate the handbook.

You can send them to your Local Alcatel-Lucent Technical Assistance Center.

They will be addressed to the team in charge of the relevant manual.

The following form supplies an example only of useful info, as a guide of the type of expected feedback.

It is possible fill part of the form, add other data and so on.

How to send feedback:

• copying the example form, filling it and sending it to your Local Alcatel-Lucent Technical Assis-tance Center. In this case handbook data are already available at the page bottom.

• using the same form available as a file in the relevant documentation CD-ROM, saving, filling and sending it by e-mail to your Local Alcatel-Lucent Technical Assistance Center.

• creating a dedicated form on paper or file and sending it to your Local Alcatel-Lucent Technical Assistance Center.

We’ll take your suggestion in account.

We reserve to modify consequently the handbook according to the corretness and congruence of the sug-gestion and requests.

Installation Guide

Customer Documentation Feedback


8DG 42778 NAAA Edition 01 125/126

126

CUSTOMER DOCUMENTATION FEEDBACK

Handbook DataHandbook title, release,version:Handbook type:Handbook part number and edition:

General Feedback EvaluationSUBJECT 5(max) 4 3 2 1 (min)

Total evaluationInfo quantityInfo qualityInfo structureConsulting facilityLayout

Chapters Feedback EvaluationHANDBOOK PARTS 5(max) 4 3 2 1(min)

PREFACECHAPTER 1CHAPTER 2CHAPTER 3CHAPTER 4APPENDICESYour Comments (stricltly necessary when value is less than 3):

Suggestion for ImprovementWhich subject to deepen:

How to deepen:

Subject to eliminate or reduce

Other comments/suggestions

Errors Identified

Reader InfoName:Company:Address:E-mail:Phone:

Installation Guide

Customer Documentation Feedback



THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

ASSEMBLY INSTRUCTIONS

Total Pages: 126 + 6

NOTES: ---

COVER LABELS(according to Alcatel-Lucent Italy binder format)

Alcatel-Lucent 1350OMS1350OMS

11.2


Installation Guide

8DG 42778 NAAA - Ed. 01

Alcatel-Lucent 1350OMS1350OMS 11.2


Installation Guide - 8DG 42778 NAAA - Ed. 01

Alcatel-Lucent 1350OMS 1350OMS 11.2

Optical Management SystemInstallation Guide - 8DG 42778 NAAA - Ed. 01

Alcatel-Lucent 1350OMS1350OMS 11.2

Optical Management SystemInstallation Guide - 8DG 42778 NAAA - Ed. 01

Appr

Auth

Unit:

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

HANDBOOK EDITORIAL INFORMATIONInstallation Guide

Ed. 01

April 2014

Change Note:

aisal: M. Mussini - F. Casasole

or: M. Mantegazza - B. Bosisio - M. Mussini - G. Lodi

Released8DG 42778 NAAA

Alcatel-Lucent 1350OMS 1350OMS


Wireline Optics NM Vimercate

11.2

8DG 42778 NAAA Edition 01

w

All rights reserved.Passing on and copying of this document,

use and communication of its contents is not permittedwithout written authorization from Alcatel -Lucent.

ww.alcatel-lucent.com