Professional Documents
Culture Documents
1350OMS
11.2
Installation Guide
8DG 42778 NAAA
Edition 01
April 2014
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.
TABLE OF CONTENTS
TABLE OF CONTENTS ...................................................................................................................
PREFACE.........................................................................................................................................
Preliminary Information..............................................................................................................
Applicability.................................................................................................................................
Scope ...........................................................................................................................................
History..........................................................................................................................................
Related Documents ....................................................................................................................
Handbook Structure ...................................................................................................................
General on Customer Documentation ......................................................................................
3
3
4
4
5
6
8
9
1 INTRODUCTION ..........................................................................................................................
1.1 Installation Steps .................................................................................................................
1.1.1 Red Hat Enterprise Linux Server installation ..................................................................
1.1.2 1350OMS Application Virtual Machine Deployment. ......................................................
1.2 Registered Trademarks .......................................................................................................
1.3 Conventions .........................................................................................................................
13
13
13
13
14
14
15
15
16
16
16
16
17
17
18
18
19
19
20
23
30
31
32
34
35
37
40
44
63
63
63
63
64
64
64
64
Installation Guide
TABLE OF CONTENTS
1/126
65
65
65
66
69
69
69
71
71
73
74
74
74
74
74
74
74
74
75
77
77
78
78
78
78
79
79
79
80
80
80
81
82
6 TROUBLESHOOTING..................................................................................................................
6.1 Identify a Failure Condition.................................................................................................
6.2 Recoverable Faults ..............................................................................................................
6.3 Device Full ............................................................................................................................
6.3.1 Device full .......................................................................................................................
6.4 Generating a SOSReport.....................................................................................................
83
83
83
84
84
85
Installation Guide
TABLE OF CONTENTS
LIST OF FIGURES
Figure 1. RHEL 6 initial boot from local DVD....................................................................................
Figure 2. RHEL 6 Boot options (example) ........................................................................................
Figure 3. RHEL 6 Manual disk configuration. ...................................................................................
Figure 4. RHEL 6 File system review window...................................................................................
Figure 5. RHEL 6 Operating System installation starting..................................................................
Figure 6. RHEL Configuration - Accept the License Agreement.......................................................
Figure 7. RHEL Configuration - Keyboard Selection ........................................................................
Figure 8. RHEL Configuration - Root Password definition................................................................
Figure 9. RHEL Configuration - Timezone selection.........................................................................
Figure 10. Setting Date, Time and Timezone ...................................................................................
Figure 11. RHEL Configuration - Kdump configuration .....................................................................
Figure 12. RHEL Configuration - Kdump required reboot confirmation ............................................
Figure 13. RHEL Configuration - Final reboot...................................................................................
Figure 14. Red Hat root Login warning message .............................................................................
Figure 15. Date and Time properties dialog......................................................................................
Figure 16. NTP server list tab ...........................................................................................................
Figure 17. Adding a NTP server .......................................................................................................
Figure 18. RHEL NTP server confirmation .......................................................................................
Figure 19. RHEL NTP using local time source .................................................................................
Figure 20. Connection warning message .........................................................................................
Figure 21. Instances configuration entry page ..................................................................................
Figure 22. Version selection screen..................................................................................................
Figure 23. Setup procedure main menu ...........................................................................................
Figure 24. Virtual Bridge administration main page ..........................................................................
Figure 25. Virtual Bridge Creation successful ...................................................................................
Figure 26. Virtual Bridge Administration page with one bridge created ............................................
Figure 27. Virtual Bridge administration: Delete bridge confirm request...........................................
Figure 28. Virtual bridge administration - Modifying existing bridge..................................................
Figure 29. Setup procedure main menu ...........................................................................................
Figure 30. Newly created empty bench - initial view.........................................................................
Figure 31. Add new Linux host .........................................................................................................
Figure 32. Import configuration from file (define configuration name) ..............................................
Figure 33. Import configuration from file (upload configuration file) ..................................................
Figure 34. Import configuration from file (upload configuration file - green arrow button) ................
Figure 35. Import configuration from file (define configuration name) ..............................................
Figure 36. Import configuration from file (upload configuration file) ..................................................
Figure 37. Import configuration from file (upload configuration file - green arrow button) ................
Figure 38. Adding a Master instance to the installation scheme.......................................................
Figure 39. Master instance: Specifying Options and networking informations..................................
Figure 40. EML-specific networking settings ....................................................................................
Figure 41. EML-specific networking settings with two supervision areas defined ............................
Figure 42. managed NE type/release selection: initial view..............................................................
Figure 43. managed NE type/release selection: selection procedure...............................................
Figure 44. NE type/releases selected, Set NE qty button enabled ...................................................
Figure 45. specifying NE quantities ..................................................................................................
Figure 46. Master Instance configured (in this figure EML master instance configured). .................
Figure 47. Master Instance configured (in this figure a EML master instance fully configured)........
Figure 48. HA configuration: Creating a SDH master HA pair ..........................................................
Figure 49. HA configuration: EML master HA pair created ...............................................................
Figure 50. Editing EML master HA spare instance: step 1 ...............................................................
Figure 51. Editing EML master HA spare instance: step 2 ...............................................................
Installation Guide
List of Figures
20
21
22
22
23
24
24
25
25
26
26
27
27
28
29
29
29
30
30
35
36
36
36
38
38
39
39
40
40
41
42
43
43
43
43
44
44
45
45
46
47
47
48
48
49
49
50
51
52
53
53
1/126
Figure 52. Bench with non-HA EML master instance and a HA pair for EML master (details) .........
Figure 53. Bench with non-HA EML master instance and a HA pair for EML master (bench view) .
Figure 54. Adding a Presentation instance to the installation scheme..............................................
Figure 55. example of bench with Presentation (orange icon) configured ........................................
Figure 56. example of bench with Presentation (orange icon) and EML Master configured ...........
Figure 57. Creating a Presentation instance in HA context ..............................................................
Figure 58. Bench with HA Presentation instances pair created ........................................................
Figure 59. Bench with HA Presentation instances pair created (details) ..........................................
Figure 60. Global settings section.....................................................................................................
Figure 61. Initial SSH VMs password rules.......................................................................................
Figure 62. Configuration completed - configuration writing...............................................................
Figure 63. Web Desktop Login .........................................................................................................
Figure 64. Web Desktop password ...................................................................................................
Figure 65. Connecting keyboard, monitor and mouse for ILO configuration. ...................................
Figure 66. Server start-up screen. ....................................................................................................
Figure 67. Initial ILO Screen .............................................................................................................
Figure 68. ILO Setup: Network menu ...............................................................................................
Figure 69. ILO Setup: NIC Setup ......................................................................................................
Figure 70. ILO Setup: User menu .....................................................................................................
Figure 71. ILO Setup: User list..........................................................................................................
Figure 72. ILO Setup: editing user details.........................................................................................
Figure 73. ILO Setup: exiting the procedure and completing configuration ......................................
Figure 74. ILO Setup: ILO reset after configuration save .................................................................
Figure 75. Pull-out sticker with factory-preset ILO password............................................................
Figure 76. Typical Main Menu of the Smart Array Configuration Utility ............................................
Figure 77. GoGlobal-UX Logo ..........................................................................................................
Figure 78. GraphOn License WEB Page ..........................................................................................
Figure 79. GraphOn License WEB Page - Software Agreement ......................................................
Figure 80. GraphOn Info request window for Single server..............................................................
Figure 81. GraphOn Info request window for Three Redundant servers ..........................................
Figure 82. GraphOn License WEB Page - License Output Example................................................
54
55
55
56
57
58
58
59
60
61
62
70
70
88
89
90
91
91
92
93
94
94
95
96
98
101
106
107
107
108
109
Installation Guide
List of Figures
LIST OF TABLES
Table 1. Handbooks related to the specific software application ......................................................
6
Table 2. Related Handbooks.............................................................................................................
7
Table 3. List of HP ProLiantTM supported hardware components.................................................... 16
Table 4. 1350OMS Network Management composition table ........................................................... 99
Table 5. Three Server Redundant License Form .............................................................................. 117
Table 6. Single License Form............................................................................................................ 118
Installation Guide
List of Tables
1/126
Installation Guide
List of Tables
PREFACE
Preliminary Information
WARNING
ALCATEL-LUCENT makes no warranty of any kind with regards to this manual, and specifically disclaims the implied warranties of merchantability and fitness for a particular purpose. ALCATELLUCENT will not be liable for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection with the furnishing, performance, or use of this material.
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 copied, 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 Documentation Feedback.
Installation Guide
Preface
3/126
Applicability
This handbook applies to following productreleases:
PRODUCT
Part Number
1350OMS
PRODUCT
RELEASE
VERSION (N.B.)
Part Number
1350OMS
11.2
11.2
N.B.
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.
Installation Guide
Preface
History
EDITION
DATE
DESCRIPTIONS
Ed. 01
April 2014
Installation Guide
Preface
5/126
Related Documents
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.
The standard Customer Documentation in the English language for the equipment whose product
releaseversion is stated in Applicability on page 4 consists of the following handbooks:
Table 1. Handbooks related to the specific software application
REF
Part Number
Notes
THIS
HANDBOOK
[2]
[3]
[4]
[1]
HANDBOOK
Installation Guide
Preface
REF
HANDBOOK
Part Number
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]
Installation Guide
Preface
Notes
7/126
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized drawing-up guides" complying 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:
Introduction
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 recommended machine requirements.
Troubleshooting
This chapter shown how to solve some trouble can occur during the
installation, and how to proceed when possible.
Appendix A
Appendix B
Appendix C
Appendix D
ABBREVIATIONS:
Not applicable
INDEX
Not applicable
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
documentation.
TION FEEDBACK
Installation Guide
Preface
Installation Guide
Preface
9/126
Handbook Updating
The handbooks associated to the "product-release" are listed in on page 5.
Each handbook is identified by:
the name of the "productrelease" (and "version" when the handbook is applicable to the versions
starting from it, but not to the previous ones),
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 productrelease (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 drawings.
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 editions.
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks 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 productrelease'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 (supplying 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
the documentation of system optional features that Customers could not buy from AlcatelLucent together with the main applicative SW.
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 handbooks
Other 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
11/126
CD-ROM identification
Each CD-ROM is identified:
1)
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 composing 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.
Installation Guide
Introduction
13/126
Red Hat, Red Hat Enterprise Linux are trademarks of Red Hat, Inc.
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.
..,sys,root #
..,$
..,oracle>
SQL>
Installation Guide
Introduction
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.
Preparatory Activity
Red Hat Enterprise LinuxTM Operating System Installation for Virtual Machine support.
Red Hat Enterprise LinuxTM Configuration
Installation Guide
Install Virtual Machine Host server
15/126
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.
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)
Installation Guide
Install Virtual Machine Host server
Host name
Keyboard selection
Time-zone
NTP servers
During virtual machine deployment the following informantion will be required:
At server level:
DVD Label
SWP-1350OMS-MW_OS-BH-V11.0.0.1.0-LX
SWP-1350OMS-MW_OS-VD-V11.2.0-LX
SWP-1350OMS-V11.2.0-LX
Installation Guide
Install Virtual Machine Host server
17/126
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
Install Virtual Machine Host server
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 problems!
Local disks
All 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-specified at the beginning of the host installation procedure (recommended), otherwise the procedure will
assign a 8-character random string.
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
Install Virtual Machine Host server
19/126
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.
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.
Installation Guide
Install Virtual Machine Host server
N.B.
If you press [Tab] on a wrong choice, it is possible to return to menu by pressing [Esc].
Installation Guide
Install Virtual Machine Host server
21/126
In case you do not select Review and modality partitions layout you must review the file system 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.
Installation Guide
Install Virtual Machine Host server
Installation Guide
Install Virtual Machine Host server
23/126
Installation Guide
Install Virtual Machine Host server
Installation Guide
Install Virtual Machine Host server
25/126
Installation Guide
Install Virtual Machine Host server
Installation Guide
Install Virtual Machine Host server
27/126
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
Install Virtual Machine Host server
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.
Installation Guide
Install Virtual Machine Host server
29/126
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 Source
To 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.
Installation Guide
Install Virtual Machine Host server
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-1350OMSMW_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:
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
Install Virtual Machine Host server
31/126
a)
First, on the host you have to install licenses keys for both Alcatel-Lucent (Poseidon) and for GoGlobal. 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 Management 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]
Installation Guide
Install Virtual Machine Host server
N.B.
The entire path to the directory chosen for the depot must be traversable (read and execute [traversal] 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.
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 >> VDMW_OS-11_0.1-1.qcow2.img
Now you should check the MD5 checksum of the files in the repository directory against the expected values. 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 VDMW_OS-11_0.1-1.qcow2.img01)
Installation Guide
Install Virtual Machine Host server
33/126
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.
WDMNBI NMA / UNBI NMA configuration (to configure run, after the autoinstall, a new System Config (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 (taking into account that the limit includes the 20 characters as maximun lenght for the hostname).
Installation Guide
1350OMS Virtual Machine Setup
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.
Installation Guide
1350OMS Virtual Machine Setup
35/126
Installation Guide
1350OMS Virtual Machine Setup
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 connection 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 netmask, which were previously set and which must obviously be compatible with the subnet netmask applicable 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 network 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.
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.
Installation Guide
1350OMS Virtual Machine Setup
37/126
Installation Guide
1350OMS Virtual Machine Setup
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).
Installation Guide
1350OMS Virtual Machine Setup
39/126
Installation Guide
1350OMS Virtual Machine Setup
N.B.
The Create new R11.2 configuration from file and Create new R11.2 configuration from Hostbased file, can be used in HW replacement context, please refer to the Hardware Replacement / 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 different 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.
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
1350OMS Virtual Machine Setup
41/126
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.
Installation Guide
1350OMS Virtual Machine Setup
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).
Installation Guide
1350OMS Virtual Machine Setup
43/126
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)
At least a Presentation VM, a SDH/NPR Master instance VM and an EML Master instance VM
must be defined.
Installation Guide
1350OMS Virtual Machine Setup
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 product will not be installed.
A configuration with only 1350OMS-EML instance(s) is not supported, al least a 1350OMSSDH or a 1350OMS-NPR instance is required to manage physical connections and maps.
Installation Guide
1350OMS Virtual Machine Setup
45/126
If selected, the ISN and the HA components will be installed and configured (for HA configuration 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) .
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.
Installation Guide
1350OMS Virtual Machine Setup
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:
Installation Guide
1350OMS Virtual Machine Setup
47/126
Installation Guide
1350OMS Virtual Machine Setup
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
1350OMS Virtual Machine Setup
49/126
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, networking 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 component and to configure it.
Installation Guide
1350OMS Virtual Machine Setup
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
1350OMS Virtual Machine Setup
51/126
Installation Guide
1350OMS Virtual Machine Setup
Installation Guide
1350OMS Virtual Machine Setup
53/126
Figure 52. Bench with non-HA EML master instance and a HA pair for EML master (details)
Installation Guide
1350OMS Virtual Machine Setup
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 Presentation instances with HA (3.1.3.4.1).
Installation Guide
1350OMS Virtual Machine Setup
55/126
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.
Installation Guide
1350OMS Virtual Machine Setup
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
1350OMS Virtual Machine Setup
57/126
The two VMs must have different IP addresses and hostnames. Press OK to confirm.
Installation Guide
1350OMS Virtual Machine Setup
Installation Guide
1350OMS Virtual Machine Setup
59/126
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
1350OMS Virtual Machine Setup
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 necessary 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
1350OMS Virtual Machine Setup
61/126
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:
<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.
Installation Guide
1350OMS Virtual Machine Setup
N.B.
All the Automatic Installation logs are located on the HOST server in the following directory:
/var/autoinstall/R11.2/trace/<HOST IP ADDRESS>
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]
[Enter]
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
1350OMS Virtual Machine Setup
63/126
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]
Please avoid to execute in installation phase any of the actions described in this chapter if not
expressly requested by a workaround.
NOTE: Please move the System config splash window in order to accelerate the load of the items.
Installation Guide
1350OMS Virtual Machine Setup
[Enter]
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 following commands:
...,root,root #
...,root,root #
...,root,root #
...,root,root #
cd /var/autoinstall/R11.2/ [Enter]
./utilities/allowHP_To_Remote.sh <source IP address> [Enter]
cd export_DIR [Enter]
./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.
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.
EMLIM id
The processes instantiated on the source server are NOT exported; the processes
to instantiate will be automatically "calculated" by the configurator.
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
1350OMS Virtual Machine Setup
65/126
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.
Copy generated NMS_parameter files on target_host in /var/autoinstall/Rxx.y/export_DIR/ ensuring 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
1350OMS Virtual Machine Setup
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 configuration and run the installation.
Installation Guide
1350OMS Virtual Machine Setup
67/126
Installation Guide
1350OMS Virtual Machine Setup
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.: provisioning, alarms supervision, ...).
N.B.
If hostname is specified (instead of IP address), some application could not behave correctly.
N.B.
If the PC was previously used to connect to other 1350OMS machines remember to cleanup 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 completed.
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
69/126
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 minutes)
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.
Installation Guide
Web Desktop and Client PC
4.2 Client PC
The minimum HW configuration for PCs is defined as follows:
Processor:
Intel Dual Core processor - 1.8 GHz clock
Memory:
Minimum: 2GB RAM Suggested: 3GB RAM
Hard Disk available space:
10GB
Software requirements:
Operating System:
Pre-installed SW:
b)
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
Web Desktop and Client PC
71/126
e)
In Virtual Memory window change both initial and maximum size to 4092.
Installation Guide
Web Desktop and Client PC
N.B.
If shown recommended value is higher than 4092, set the recommended value instead.
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 consider that java applications started by Internet will no more run by the proxy.
Installation Guide
Web Desktop and Client PC
73/126
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.
Installation Guide
Web Desktop and Client PC
Installation Guide
Web Desktop and Client PC
75/126
Installation Guide
Web Desktop and Client PC
5 Post Installation
This chapter describes some actions that may be required after the initial installation was completed successfully.
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 Master VM or a new 1350OMS Presentation VM.
Access the 1350OMS configuration Tool on the host server (3.1), select the release of the 1350OMS (Figure 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.
b)
c)
d)
Add the new EML clients on existing VMs (except the other EMLs) and run integration/federation
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
77/126
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)
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
configure the hosts in addition to "main" noc and drc servers (also the hosts previously defined and
different from noc and drc servers)
Both actions are managed by trough manageHosts.sh utility described in Multi Host configuration
(3.3.2).
Installation Guide
Post Installation
[Enter]
[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.
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]
[Enter]
Installation Guide
Post Installation
79/126
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
Installation Guide
Post Installation
...,root,root #
...,root,root #
...,root,root #
...,root,root #
cd /var/autoinstall/R11.2 [Enter]
utilities/changeHostName.sh prefix=<bench-name> HA=drc [Enter]
utilities/execOnBench.sh <bench_config>.noc complete stop [Enter]
utilities/execOnBench.sh <bench_config>.drc complete start-force [Enter]
Start the 1350OMS-HA on DRC and on NOC executing the commands described in 1350OMS HA startup 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:
EML
ISN
IOO
CPB
SDH/NPR
PKT
WDM
The first installation of an optional component, on a system already confiigured, requires the following
main steps :
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]
Installation Guide
Post Installation
81/126
Select y to execute, the System, Instances List" window will be shown on the screen after a few seconds, 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.
Installation Guide
Post Installation
6 Troubleshooting
Here after is shown how to solve some trouble can occur during the installation, and how to proceed when
possible.
Some system reboot are foreseen to correctly carry on the installation, that means don't worry
if the system reboot automatically.
Installation Guide
Troubleshooting
83/126
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
Installation Guide
Troubleshooting
85/126
Installation Guide
Troubleshooting
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
87/126
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
Installation Guide
System Tips
89/126
Installation Guide
System Tips
Installation Guide
System Tips
91/126
Installation Guide
System Tips
Installation Guide
System Tips
93/126
Figure 73. ILO Setup: exiting the procedure and completing configuration
ILO setup utility will close and ILO will reset.
Installation Guide
System Tips
Installation Guide
System Tips
95/126
Installation Guide
System Tips
The Smart Array disk configuration MUST be done BEFORE proceeding with host
installation and VM installations. Subsequent changes are not possible without loosing 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 depending 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, confirm 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
97/126
Figure 76. Typical Main Menu of the Smart Array Configuration Utility
Installation Guide
System Tips
checksum
size
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
checksum
size
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
name
1350OMS-LX_11.2.0.79_on_top.tar.gz
name
99/126
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
When you have retrieved go_setup on you PC install it by follow hereafter procedure:
a)
b)
Installation Guide
GoGlobal-UX Installation and Configuration
101/126
Choose your destination location and click on Next to go on. Wait a few seconds the install procedure.
f)
Installation Guide
GoGlobal-UX Installation and Configuration
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
Installation Guide
GoGlobal-UX Installation and Configuration
103/126
You can now install the new version of the software by starting again the installation application.
Installation Guide
GoGlobal-UX Installation and Configuration
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).
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.
b)
c)
-n
[Enter]
[Enter]
The obtained data will be used in a successive phase of the license request activity.
Installation Guide
GoGlobal-UX Installation and Configuration
105/126
http://license.graphon.com/user/
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
GoGlobal-UX Installation and Configuration
Installation Guide
GoGlobal-UX Installation and Configuration
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 ALCATEL 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: Hostname and Hostid with the data of each license server.
and click on Get License button to continue.
Installation Guide
GoGlobal-UX Installation and Configuration
Installation Guide
GoGlobal-UX Installation and Configuration
109/126
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 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
Add TCP port number (27001) at any line beginning with SERVER:
Example from:
SERVER host_c 839dc26
to:
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
GoGlobal-UX Installation and Configuration
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>
<port>
is the IP port number stored in the license.dat file as fourth field of the line
starting with SERVER, if that field is blank 27001 have to be used.
[Enter]
Installation Guide
GoGlobal-UX Installation and Configuration
111/126
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.
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
GoGlobal-UX Installation and Configuration
This check can be done only if the license server machine(s) are already configured.
..,sys,root # export LM_LICENSE_FILE=27001@<Hostname>
..,sys,root # /opt/graphon/bin/lmstat -a [Enter]
[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:
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
GoGlobal-UX Installation and Configuration
113/126
[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:
Installation Guide
GoGlobal-UX Installation and Configuration
a)
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 authorization 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 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info="Paolo Rossi\
paolo.rossi@alcatel.it" 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
Installation Guide
GoGlobal-UX Installation and Configuration
[Enter]
115/126
d)
1)
Move to last line in file and insert the INCREMENT line(s). For example, if you have the authorization 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 27001
SERVER host_d 77df65d1 27001
SERVER host_e 7751b870 27001
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info="Paolo Rossi\
paolo.rossi@alcatel.it" 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].
[Enter]
After completing these steps, the new GoGlobal-UX licenses will be available.
Installation Guide
GoGlobal-UX Installation and Configuration
The package foreseen to manage network floating license, that means you must define one or more system in your network to perform the license server task.
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).
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.
b)
c)
[Enter]
Installation Guide
Poseidon Installation and Configuration
117/126
Host Name
Host Identifier
Host Identifier
Installation Guide
Poseidon Installation and Configuration
Installation Guide
Poseidon Installation and Configuration
119/126
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)
c)
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 INCREMENT" line terminated with back slash ( \ ), that means also the next one have to be considered 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.
If the server replies the ping" request an output like the following will be provided:
Installation Guide
Poseidon Installation and Configuration
Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
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.
Installation Guide
Poseidon Installation and Configuration
121/126
Installation Guide
Poseidon Installation and Configuration
ABBREVIATIONS
Installation Guide
Abbreviations
VM
Virtual Machine
VD
Virtual Disk
NTP
123/126
Installation Guide
Abbreviations
copying the example form, filling it and sending it to your Local Alcatel-Lucent Technical Assistance 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.
Installation Guide
Customer Documentation Feedback
125/126
126
1 (min)
1(min)
How to deepen:
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
Installation Guide
Customer Documentation Feedback
ASSEMBLY INSTRUCTIONS
Total Pages: 126 + 6
NOTES: ---
COVER LABELS
(according to Alcatel-Lucent Italy binder format)
Alcatel-Lucent 1350OMS
1350OMS
11.2
Optical Management System
Installation Guide
8DG 42778 NAAA - Ed. 01
Alcatel-Lucent 1350OMS
1350OMS
11.2
Alcatel-Lucent 1350OMS
1350OMS 11.2
Optical Management System
Installation Guide - 8DG 42778 NAAA - Ed. 01
Alcatel-Lucent 1350OMS
1350OMS
11.2
HANDBOOK
EDITORIAL
INFORMATION
Optical
Management System
Alcatel-Lucent 1350OMS 1350OMS
8DG 42778 NAAA
Ed. 01
11.2
Released
Change Note:
April 2014
www.alcatel-lucent.com