8DG43091NAAA - V1 - 1350OMS R12.3 Installation Guide

1350 OMS Installation Guide
1350 OMS | Release 12.3

1350OMS R12.3 Installation Guide
8DG 43091 NAAA
ISSUE 1 | JULY 2015
Alcatel-Lucent — Proprietary
Use pursuant to applicable agreements
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 © 2015 Alcatel-Lucent. All Rights Reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Alcatel-Lucent — Proprietary
Use pursuant to applicable agreements
Contents
About this document 1
Purpose ...................................................................................................................................................... 1
History ....................................................................................................................................................... 1
Related information ................................................................................................................................... 1
Technical support ...................................................................................................................................... 2
How to order ............................................................................................................................................. 2
How to comment ....................................................................................................................................... 2
1 1350 OMS SW Repository and VM Tools 3
Software Media ......................................................................................................................................... 3
Online VDs reassembly – KVM platform ................................................................................................. 4
Install Virtual Machine Tools - KVM platform ........................................................................................ 6
Licences request - KVM platform ............................................................................................................. 8
VDs reassembly – vmware® platform ...................................................................................................... 8
Install Virtual Machine Tools - vmware® platform.................................................................................. 9
Deploy AI-Driver VM ............................................................................................................................... 9
Autoinstall tool installation ..................................................................................................................... 15
2 1350 OMS Virtual Machine Setup 19
Procedure information ............................................................................................................................. 19
Access 1350 OMS configuration Tool .................................................................................................... 20
3 vmware® – SW upload 23
Upload the 1350 OMS Software ............................................................................................................. 23
Uploader Tool for Windows ................................................................................................................... 24
4 Create R12.3 configuration 28
Create empty configuration ..................................................................................................................... 30
Define network bridge(s) – only for KVM platform ............................................................................... 34
Create new configuration from file ......................................................................................................... 37
Create new configuration from Host-based file ...................................................................................... 37
5 Configuration editing 39
Description of the installation structure .................................................................................................. 40
Add Master Instance................................................................................................................................ 41
Add Master Instance: General option...................................................................................................... 42
1350 OMS Installation Guide Alcatel-Lucent — Proprietary iii
8DG 43091 NAAA Use pursuant to applicable agreements
ISSUE 1 JULY 2015
Contents
Add Master Instance: Dimensioning option ............................................................................................ 42

Add Master Instance: Network setting .................................................................................................... 42
Add Master Instance - 1350 OMS HA configuration .............................................................................. 44
Configure 1350 OMS HA in a Master instance ....................................................................................... 44
Add Presentation Instance........................................................................................................................ 46
Add Presentation Instance: General option.............................................................................................. 47
Add Presentation Instance: Dimensioning option.................................................................................... 47
Add Presentation Instance: Network setting ............................................................................................ 47
Bench configuration result ....................................................................................................................... 48
Entering global settings ........................................................................................................................... 49
Final review step ...................................................................................................................................... 51
6 vmware® - Deploy 1350 OMS VMs 57
1350 OMS VMs OVF descriptors ........................................................................................................... 57
Deploy 1350 OMS VMs .......................................................................................................................... 58
Licenses request - vmware® platform .................................................................................................... 64
7 AI-C activity menu 65
activity menu............................................................................................................................................ 66
activity menu: Install ............................................................................................................................... 68
activity menu: Start .................................................................................................................................. 69
activity menu: Stop .................................................................................................................................. 71
activity menu: Utilities............................................................................................................................. 72
activity menu: Transformation ................................................................................................................. 73
activity menu: Backup/Restore ................................................................................................................ 75
activity menu: Migration ......................................................................................................................... 77
A Post Installation 79
Post Installation instructions (execute on VMs) ...................................................................................... 79
Post Installation instructions .................................................................................................................... 80
“Enable” 1350OMS HA .......................................................................................................................... 80
Post Installation Workaround .................................................................................................................. 81
FM and AS EVENTS services down ....................................................................................................... 81
PKT Technology maps not available in MSGUI ..................................................................................... 81
B 1350 OMS NMS composition table 83
C Export/Import procedure 86
Export configuration from bench WITH direct connection with the new host ........................................ 86
iv Alcatel-Lucent — Proprietary 1350 OMS Installation Guide
Use pursuant to applicable agreements 8DG 43091 NAAA
ISSUE 1 JULY 2015
Contents
Export configuration from bench WITHOUT direct connection with the new host ............................... 88
Import exported configuration on target host .......................................................................................... 89
Notes for R9.6 HP-UX Migration ........................................................................................................... 89
D GoGlobal-UX Installation and Configuration 91
GoGlobal-UX Installation on 1350 OMS ............................................................................................... 91
GoGlobal-UX Installation on PC ............................................................................................................ 91
GoGlobal-UX license .............................................................................................................................. 92
License servers definition rules ............................................................................................................... 92
Retrieve License Servers Identity ........................................................................................................... 92
Permanent License Request .................................................................................................................... 93
GoGlobal-UX authorization procedure ................................................................................................... 95
Store the Authorization Key in the License File ..................................................................................... 95
Configure License Server ........................................................................................................................ 96
Start License Server and GraphOn Daemons .......................................................................................... 97
E Poseidon Installation and Configuration 98
Poseidon License Management Configuration........................................................................................ 98
Retrieve License Servers Host Identifier................................................................................................. 99
Require the Authorization License ........................................................................................................ 100
Store the Authorization Key in the License File ................................................................................... 100
Check the License Status....................................................................................................................... 100
Redundant Connectivity ........................................................................................................................ 101
F Install 1350OMS License in HA Configuration 102
Procedure information ........................................................................................................................... 102
Sequence of actions in Red Hat kVM enviroment ................................................................................ 104
Sequence of actions in vmware® environment ..................................................................................... 105
G Certificate requirements for secure SSL communication 108
wildcard SSL certificate requirements .................................................................................................. 108
no custom certificate ............................................................................................................................. 109
H Abbreviations 110
1350 OMS Installation Guide Alcatel-Lucent — Proprietary v

ISSUE 1 JULY 2015
About this document
Purpose
This document describes how to configure and install the Alcatel-Lucent 1350O OMS
Network Manager application Software.
History
The following table shows the history of this document.
Description Issue
1350OMS R12.3 Installation Guide – Based on 12.3.0.52 build Issue 1 - July 2015
Related information
The following table list the related documents.
Document Part Number
1350OMS R12.3 HW and OS Installation Guide 8DG 43091 WAAA
1350OMS R12.3 Migration Scenarios 8DG 43091 KAAA
1350 OMS R12.3 Administration Guide, Vol 1

8DG 43091 LAAA
System Maintenance and Troubleshooting
1350 OMS R12.3 Administration Guide, Vol 2

8DG 43091 MAAA
Common GUI Functions
1350 OMS R12.3 Platform Guide 8DG 43091 BAAA
1350 OMS R12.3 OTN Guide 8DG 43091 QAAA
1350 OMS R12.3 16x6 Photonic Guide 8DG 43091 RAAA
1350 OMS R12.3 OTN Guide - Ethernet Services Manager Guide 8DG 43091 VAAA
1350 OMS R12.3 PKT Guide 8DG 43091 DAAA
1350 OMS R12.3 Service Assurance Guide 8DG 43091 FAAA
1350 OMS R12.3 HA Guide 8DG 43091 GAAA
1350 OMS R12.3 OI Guide 8DG 43091 HAAA
1350 OMS Installation Guide Alcatel-Lucent — Proprietary 1

ISSUE 1 JULY 2015
About this document
1350 OMS R12.3 OI NBI Guide 8DG 43091 JAAA
1350OMS R12.3 User Interface Guide 8DG 43091 EAAA
1350OMS R12.3 SDH Guide 8DG 43091 CAAA
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use the
Online Customer Support Site (OLCS) web site (http://support.alcatel-lucent.com).
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
2 Alcatel-Lucent — Proprietary 1350 OMS Installation Guide

ISSUE 1 JULY 2015
1 1350 OMS SW Repository
and VM Tools
Overview
Purpose
In order to deploy the 1350 OMS the precondition is to have the needed SW accessible by
the host server for the KVM platform or accessible by the operator’s PC for vmware®
platform.
The software is distributed on 4.7GB DVDs and some files are split in more fragments.
Before VMs installation can take place these parts have to be re-assembled to obtain the
original complete Virtual Disk files contents.
Contents
This chapter covers these topics.
Software Media 3
Online VDs reassembly 4
Install Virtual Machine Tools - KVM platform 6
VDs reassembly – vmware® platform 8
Install Virtual Machine Tools - vmware® platform 9
Software Media
Hereafter the Alcatel-Lucent DVD label and part number of requested item to install the
current 1350 OMS release:

ISSUE 1 JULY 2015
1350 OMS SW Repository and VM Tools
DVD Part
DVD Label Disk set description
Number
VD files for Guest OS and

platform, plus RPM
SWP-1350OMS-MW_OS-VD-V12.3.0-LX 8DG 43096 AAAA
packages to enable Virtual
Machine installation
1350 OMS Applications

SWP-1350OMS-V12.3.0-LX 8DG 43098 AAAA
VDs
SWP-1350OMS-AI_Driver-V3.1.5-LX 1350 OMS AI Driver 8DG 43058 ADAA
Online VDs reassembly – KVM platform

The online VD reassembly procedure reads the DVD contents and reassembles virtual
disks from the fragments writing the resulting files directly in a specific directory of the
server host.
Create a repository directory on the host file system, for example:
...,root,root # mkdir -p /DEPOT/<1350OMS build> [Enter]
Note:
Example of repository path /DEPOT/12.3.0.99
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/NR12.x/1350 OMS -

LX_12.x.y.z/ 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.

ISSUE 1 JULY 2015
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:
...,root,root # mkdir /mnt/dvd [Enter]
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).
Copy all files from each DVD to the repository directory: for each DVD of the 1350 OMS
applications disk set execute the following:
(insert disk and allow a few seconds..)
...,root,root # mount /dev/sr0 /mnt/dvd [Enter]

...,root,root # cp -f /mnt/dvd/* /DEPOT/<1350OMS build> [Enter]
...,root,root # umount /mnt/dvd [Enter]
(remove disk..)
Only for KVM platform installation run the following command to rebuild the MW_OS
VD from its fragments:
...,root,root # cat VD-MW_OS-12.x.y_z.vmdk.img00 VD-MW_OS-

12.x.y_z.vmdk.img01 >> VD-MW_OS-12.x.y_z.vmdk.img [Enter]
Then calculate the actual MD5 checksums by executing from within the repository
directory the command:
...,root,root # md5sum * [Enter]
Compare them with each expected value found in the .md5sum file.
If the actual and expected checksum values match, the EML VD file fragments can be
deleted to free disk space.

ISSUE 1 JULY 2015
After the execution of all the described instructions the repository directory contains all
the files needed to proceed with the installation and their integrity has been verified.
Install Virtual Machine Tools - KVM platform

In order to finalize the host installation and to enable the deployment of VMs on it, the
installation of additional software packages for managing Alcatel-Lucent VM is needed.
The software packages are delivered as RPM files listed in “1350 OMS NMS composition
table”.
Note:
In case of multihost installation (i.e. 1350OMS HA) the RPM files installation must
be executed on all the bench hosts.
After mounting the DVD SWP-1350OMS-MW_OS-VD-V12.x.y-LX 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:
Note:
Before to run the 1350OMS-MW_OS-<version> installation on the host, it is

necessary to comment the following lines in /etc/lvm/lvm.conf file:
thin_check_executable = "/usr/sbin/thin_check"
thin_check_options = [ "-q" ]
...,root,root # rpm -i 1350OMS-MW_OS-<version>.el6.x86_64.rpm 1350OMS-

MW_OS-bck-<version>.el6.x86_64.rpm 1350OMS-MW_OS-conv-
<version>.el6.x86_64.rpm 1350OMS-MW_OS-repos-<version>.el6.x86_64.rpm
1350OMS-MW_OS-sec-<version>.el6.x86_64.rpm [Enter]
Note:
The 1350OMS-MW_OS RPMs version to be installed are available in the “1350 OMS
NMS composition table” appendix.
Check, with the following command, the versions of the already available rpm packages:
...,root,root # rpm -q sc-vadeploy [Enter]
The list of the packages version will be displayed (see example below):

ISSUE 1 JULY 2015
sc-vadeploy-4.3-8.el6.noarch
Check the already installed packages version; for every rpm package with different
version execute the following command to update it:
...,root,root # rpm -U <package-package_version> [Enter]

Note:
The <package-package_version> is the rpm -q command output as in previous example
(Example: rpm -U sc-vadeploy-4.2-8.el6.noarch).
After the check/upgrade of above rpm packages proceed with the installation of the
autoinstall tool as follow:
...,root,root # rpm -i autoinstall<version>.noarch.rpm [Enter]
Notes:
 The autoinstall<version>.noarch.rpm to be installed is available in the “1350
OMS NMS composition table” appendix (i.e. autoinstall121-2.0-75.noarch.rpm).
 The message “Starting httpd: httpd: apr_sockaddr_info_get() failed for XXXXX”
can be ignored.
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 # htpasswd /var/autoinstall/.htpasswd alutmn [Enter]
 The autoinstall tool (AI) is delivered for the bench configuration, it MUST be
installed on the HOST Server using a VNC GUI (Go-Global is not supported).
 In case of 1350OMS multihost installation (i.e. 1350OMS HA) all the hosts must
be connectable from AI-Driver , in order to do that allow the SSH connection from
"AI Driver" to other host(s), connect the "AI Driver” as root user and execute:
...,root,root # cd /var/autoinstall/R12.x [Enter]

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

ISSUE 1 JULY 2015
Licences request - KVM platform

Before to proceed with the VMs setup it is necessary to proceed with the licences request.
The licenses must be requested, as described in “GoGlobal-UX Installation and
Configuration” and “Poseidon Installation and Configuration” appendixes, for the host(s)
where the OTN VM(s) will be configured, see description in “Entering global settings”
paragraph.
Note:
If the 1350 OMS HA will be installed/configured the licences must be requested both
for NOC and DRC centers and must be evenly installed (NOC license on host where
the NOC OTN VM will be configured and DRC license on host where the DRC OTN
VM will be configured) .
VDs reassembly – vmware® platform

On a Windows PC create a temporary directory (i.e. \DEPOT) and copy all the files to be
reassembled from the DVDs into it.
Open a command prompt window (Start => cmd <ENTER>)
Change working directory to the disk and path of the created temporary directory where
the file fragments are located.
Reassembly the VD file fragments executing the following command:
<disk>:\<temp_dir_path> copy /B <to_be_reassembled_VD>.vmdk.img00 + /B

<to_be_reassembled_VD >.vmdk.img01 + /B <to_be_reassembled_VD >.vmdk.imgXY
<to_be_reassembled_VD >.vmdk.img [Enter]
Obtain the Hash-Tool free utility (http://download.cnet.com/Hash-Tool/3000-2248_4-

10969531.html) or other equivalent tool to calculate the SHA512 code on Windows PCs,
verify that actual code matches the expected code found in the .SHA512SUMS file and, if
it does, delete the VD file fragments.
Note:
Select the SHA-512 Hash Type to properly check the file(s).

The procedure must be executed for all the VDs fragmented on DVDs media.

ISSUE 1 JULY 2015
Install Virtual Machine Tools - vmware® platform

Deploy AI-Driver VM
In order to be able to deploy the 1350OMS AI-Driver VM on a vmware® infrastructure it
is needed to have a “vmware® infrastructure based on ESXi 5 with vCenter”.
The vmware® infrastructure must be able to host both AI-Driver and 1350 OMS VMs, in
terms of disk, memory and core resources.
Note:
Direct deploy on ESXi is not supported.

The DVD SWP-1350OMS-AI_Driver-Vx.y.z-LX (see Software Media composition table
for the DVD label and part number) contains all the needed file to deploy the AI-Driver
VM: insert the media into the PC disc reader or mount its disc image.
Login the vmware® vCenter or ESXi via vSphere Client and open the “Deploy OVF
Template” tool by open “File” pull down menu and select “Deploy OVF Template”.
The following windows will be shown:

ISSUE 1 JULY 2015
Browse the DVD and select the AI-Driver OVF file then press the “Next” button, a
descriptive window will be shown to allow the check of the appliance characteristics,
press “Next” button to proceed, the “Name and Location” window will be shown:

ISSUE 1 JULY 2015
In this window the AI-Driver VM name must be chosen (a default name is shown in the
“Name:” text box.
In the “Inventory Location:” the data centre for the VM deployment must be chosen.
Press “Next” button to proceed.
Note:
vmware® does not allow two VMs with same name on the same data centre.
The shown windows allow to choose the destination host, the first one allows to choose
between cluster, if any, and host: if the selected target is a cluster an additional window
allows to choose the host inside the cluster; select the target and press “Next” button to
proceed with “Storage” window.

ISSUE 1 JULY 2015
Select one of the data stores listed in the “VM Storage Profile:” then press “Next” button
to continue with the “Disk Format” window.
For the AI-Driver VM is suggested to choose the “Thin Provisioning” format, press
“Next” button to proceed with “Network Mapping” window.
ISSUE 1 JULY 2015
Choose the “Virtual Switch” where connect the appliance, AI-Driver VM foreseen just a
NIC, select the virtual switch and press “Next” button.
Note:
If more than one “Source Networks” are defined, take care to properly associate each
defined “Source Networks” with the desired “Destination Networks”: click on actual
associated “Destination Networks” and choose one entry from the drop-down menu.

ISSUE 1 JULY 2015
The “Properties” window allows to define the appliance network characteristics, such has:
Host name, IP Address, Net Mask and Gateway, fill the text boxes and press “Next”
button.
Note:
The default Web user-id to access the AI-C is alutmn.

The last window summarizes the appliance configuration data; if the data entered are not
correct press “Back” button to go back and change, otherwise press “Finish” button to
complete.
Note:
Take care to select the “Power on after deployment” to automatically execute the first
VM reboot after the deploy in order to properly configure it before the first user login
(in alternative the boot of the deployed VM can be executed by hand).
The deploy of the AI-Driver VM will start immediately.

ISSUE 1 JULY 2015
When the deploy will be complete the AI-Driver VM must be run selecting it in the
vSphere virtual machine inventory and pressing the run button, a light green right arrow
will identify the “power on” of the VM(s).
Autoinstall tool installation

The complete the AI-Driver VM setup it is necessary to install the autoinstall tool; open
an Internet browser and type, as URL, the IP address of the AI-Driver VM (the IP is the
same used for the AI-Driver VM deploy). The 1350 OMS splash windows will be opened.

ISSUE 1 JULY 2015
Click the splash to enter in the AI-C set up windows:
Use the button to browse the autoinstall tool rpm (see Installation Guide 1350 OMS
Composition appendix).
Note:
The autoinstall must be on PC or on external device connected to the PC.

ISSUE 1 JULY 2015
Pressing the OK button the autoinstall toll will be installed on the deployed AI-Driver.
The installation elapsed time depends on network performance.

ISSUE 1 JULY 2015
At the end on the installation press the “Back to main menu” button, then continue with
the “1350 OMS Virtual Machine Setup”.

ISSUE 1 JULY 2015
1350 OMS Virtual Machine Setup
2 1350 OMS Virtual Machine

Setup
Overview
Purpose
A 1350 OMS installation consists of a set of Virtual Machines, each running a NMS
Master instance or a Presentation instance.
Contents
Procedure information 19
Access 1350 OMS configuration Tool 20
Procedure information
Before you begin
Before to proceed with the configuration and the installation steps please take care to read
the AI, Auto Install tool restriction listed here below:
 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 maximum length for the VM Name is 50 characters for the KWM Virtual
Machines Manager (taking into account that the limit includes the 20 characters as
maximum length for the hostname)

ISSUE 1 JULY 2015
Note:
When more than one 1350 OMS -EML managing PSS Network Elements is present in
a LX bench configuration, CPB on Presentation will be associated to only one of the
1350 OMS -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>").
Access 1350 OMS configuration Tool

The access to 1350 OMS configuration tool you have to open an Internet browser and
type, as URL, the IP address of the physical server host, for KVM platform, or of the AI-
Driver VM for the vmware® platform (the IP is the same used for the AI-Driver VM
deploy). 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.
The welcome window will be shown:

ISSUE 1 JULY 2015
Click on the picture to go to AutoInstall configurator (AI-C) main menu.
Select the proper Release to proceed, the following window will be shown.

ISSUE 1 JULY 2015
Type the AI-C credentials to display the windows where is possible to create a new
configuration.

ISSUE 1 JULY 2015
vmware® – SW upload
3 vmware® – SW upload
Overview
Purpose
The AI-Driver is delivered without the 1350OMS SW inside, it must be uploaded via
“Web upload” AI-C option or via the “Uploader Tool for Windows”.
Contents
Upload the 1350 OMS Software 23
Uploader Tool for Windows 24
Upload the 1350 OMS Software

The needed SW can be uploaded using the “Web Upload” or installing on the operator PC
the “Uploader Tool for Windows” (recommended).
To access both the upload methods connect to the access to 1350 OMS configuration tool
as described in “Access 1350 OMS configuration Tool”, enter the the AI-C credentials,
the following windows will be shown:

ISSUE 1 JULY 2015
Follow the “Manage software repository” link to display the “Local Software Repository
administration” window: here it is possible to upload the 1350 OMS SW using the “Web
Upload” option (press the “Upload descriptor for new release” button and follow the
instructions - descriptor file <filename>.descx, see Error! Reference source not found.),
or download on local PC the “Uploader Tool for Windows” (Don’t care about the browser
warning messages, and run the tool).
Uploader Tool for Windows

Run the Uploader.exe tool and select the “Enter AI Driver Address” button to specify its
IP address.
Note:
Take care to properly setup the PC “power options” during the upload in order to do
not lose the network connection between the PC and the AI-Driver VM.

ISSUE 1 JULY 2015
The connection with the AI-Driver VM will be checked.

In the following windows the descriptor file (<filename>.descx, see 1350 OMS NMS
composition table) containing the list of 1350 OMS SW to be uploaded on AI-Driver VM,
must be selected.
The description file will uploaded and parsed by the tool and a check on required and
available space is performed.

ISSUE 1 JULY 2015
If the available space is sufficient press the “Start Upload” button, the upload process will
start.
At the end of the upload the following window will be shown:

ISSUE 1 JULY 2015
At the end of the upload procedure a check of the uploaded SW is suggested following the
link “Manage software repository” as described in “Upload the 1350 OMS Software”, the
Depot content will be shown with the upload status/results for every files:

ISSUE 1 JULY 2015
Create R12.3 configuration
4 Create R12.3 configuration
Overview
Purpose
This chapter shows the option s to create a new configuration.
Contents
Create empty configuration 30
Define network bridge(s) – only for KVM platform 34
Create new configuration from file 37
Create new configuration from Host-based file 37
Authenticate the AI-C tool as already described in “Access 1350 OMS configuration
Tool”, the following window will be displayed, here is possible to create a R12.3
configuration.
Note:
If the autoinstall was updated and the AI-Driver web interface is already opened (it
was used to download the uploader.exe tool), close and reopen it.

ISSUE 1 JULY 2015
The Option menu offers different choices to configure the bench, only the first three are
meaningful for a scratch installation:
 Create empty R12.3 configuration
 Create new R12.3 configuration from file
 Create new R12.3 configuration from Host-based file
Note:
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.

ISSUE 1 JULY 2015
Create empty configuration

The “Create empty R12.3 configuration“ option of the menu must be used to create a
new configuration, enter the configuration name, also known as prefix (i.e. DDr12 in
the image below), then press the OK button.
Note:
The configuration name may only contain uppercase/lowercase letters and digits and
must begin with a letter.
the following window will be shown:

ISSUE 1 JULY 2015
The user must select the platform, KVM or vmware®, before to proceed with the bench
configuration; the selection can be done via the “Target Platform” drop-down list.
Note:
The “Target platform” can only be changed when the configuration contains no hosts
(meaningful only for KVM platform) and no VMs.
If the KVM platform is selected the configuration window appears as follow:

ISSUE 1 JULY 2015
If the vmware® platform is selected the configuration window appears as follow:
Note:
The different background color for “KVM Host(s)”, light yellow, and for “vmware®
infrastructure”, light cyan, clearly identify the chosen platform.

ISSUE 1 JULY 2015
For a KVM platform configuration, at least a new host must be defined, type the host
name, its IP address and the “current” root password in the proper fields, then press the
OK button.
Note:
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.
In case of configuration with 1350 OMS HA at least two hosts must be defined, a pair
of VMs in HA configuration cannot reside in the same host, use the “Move to:” box
to properly address them.
Note:
All the highlighted error (in red), see example image below, must be solved.

ISSUE 1 JULY 2015
Define network bridge(s) – only for KVM platform

Before proceed with the instances configuration it is required to properly configure the
network bridges. This networking setup is required to enable the deployed Virtual
Machines to reach the external LAN(s) through the physical NICs of the host.
To access the Network Bridge definition page you have to click on “Edit” link on right of
the “No network bridges defined” issue marked in red.
Type the new bridge(s) name(s) in the “Define new bridge with name:” box and press the
OK button. . The bridge gets added to a list of "defined" bridges and the page is reloaded.
Repeat the process defining all needed bridges; when done, press “Back to synopsis”.
On top of page the message will say something like "Network bridges defined for the
configuration: br0, br1" (br0 and br1 bridges defined), AI-C knows that you need those
bridges in the configuration.
AI-C will create those bridges, if possible (see "network configuration stage" “Final
review step” for details), on ALL HOSTS in the configuration.

ISSUE 1 JULY 2015
After the Network bridge(s) is/are defined it is also necessary to specify, for EACH HOST
of the configuration, what physical NIC of the host they are connected to, this connection
may be different for each host.
For example, if bridges named br0 and br1 were defined, on host "host1" is planned to
connect br0 to eth0 and br1 to eth1 but, perhaps, on host "host2", with different NIC
situation, is planned to connect br0 to eth3 and br1 to eth2, etc.
The mapping between bridge(s) and NIC(s) can be done using the Edit button of the
“Bridge-physical NIC mapping:” option in the bottom part of the light yellow box
representing the hosts.

ISSUE 1 JULY 2015
A new page in which are presented the bridges on that host will be shown, map a bridge
on a certain NIC by selecting the desired NIC from the selector under the bridge.
It is possible to connect a bridge to multiple NICs if it is needed to set up "NIC bonding".
It is possible to remove the NICs connected to a bridge by clicking on the "X" red link
underneath it.
Note:
A NIC used with a bridge cannot be used with another bridge, so it will disappear
from the selector of all other defined bridges (of that host).
When the desired mapping is completed click "back to synopsis": in the diagram will be
shown, below each bridge, the name of the one or more NICs connected to it.

ISSUE 1 JULY 2015
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 R12.3 configuration from
file” option, browse the files using the related button and then upload it.
As alternative the available configuration file can be uploaded starting from the option
“Create empty R12.3 configuration” 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 one host must be defined
first).
Note:
All the needed updates to an existing bench configuration imported via the just
described options must be executed using the AI-C web GUI as described in this
guide.
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 R12.3 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.

ISSUE 1 JULY 2015
As alternative the available configuration file can be uploaded starting from the option
“Create new R12.3 configuration from file” 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).

ISSUE 1 JULY 2015
Configuration editing
5 Configuration editing
Overview
Purpose
The web-based configuration editor allow to configure the 1350 OMS bench.
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 installation
has to interact 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 files will be generated.
Contents
Description of the installation structure 40
Add Master Instance 41
Add Master Instance - 1350 OMS HA configuration 44
Add Presentation Instance 46
Bench configuration result 48
Entering global settings 49
Final review step 51

ISSUE 1 JULY 2015
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.
Note:
At least a Presentation VM, a OTN Master instance VM and an EML Master instance
VM must be defined.
A configuration with only 1350 OMS -EML instance(s) is not supported, at least a
1350 OMS -OTN instance is required to manage physical connections and maps.
Note:
The image is related to the “KVM platform”, the same icons are available in the
“vmware® platform” configuration.

ISSUE 1 JULY 2015
Add Master Instance

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.
If the 1850TSS NE managed by SNA EMLIM must be configured, also the 1830PSS NE
must be added.
When the blue icon is pressed, the following page appears:
Select the master instance Type, enter the hostname (click on the information button for
naming rules), the instance ID, and select the VM size then press OK.
Note:
The VM size, “Standard” or “Large”, must be selected following the dimensioning

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

ISSUE 1 JULY 2015
Add Master Instance: General option

In this section it is possible to select the optional components to be installed, IOO and
HA.
If selected the 1350 OMS HA and the 1350 OMS IOO components will be installed and
configured.
Refer the “Add Master Instance - 1350 OMS HA configuration” section to properly
configure the 1350 OMS HA.
Add Master Instance: Dimensioning option

Do not alter the default CPU core count value.
Add Master Instance: Network setting

It is possible to define up to 5 virtual NICs for the new Master instance: fill only the first
N rows as needed, leaving no empty rows (i.e. if 2 virtual NICs are defined use the “NIC
eth0 data” and the “NIC eth1 data” rows).
Only for the KVM platform, each virtual NIC is to be associated with a bridge (which
must have been created in advance); specify network information for the instance
selecting the desired bridge, for both the platforms (KVM/vmware® ) the IP and mask
fields must be mandatory filled, optionally you can also specify the address of a gateway.
Note:
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.
Note:
ISSUE 1 JULY 2015
In order to support the GMRE a second virtual NIC must be configured for OTN
Master instance (take care to connect the second NIC to the LAN on which it is
effectively attested the GMRE).
If the second virtual NIC is configured in OTN Master instance, the same must be
done for PKT and Presentation instances.
Press OK to confirm, if the instance is not an EML Master, a blue icon related to the
configured instance is added to the installation structure diagram, otherwise the
“EML-specific networking setting“ window will be opened.
This step is only presented when creating a EML master instance and requires the user to
enter configuration information about the supervision areas.
There may be up to one supervision area per guest NIC (at least one must be defined
overall).
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: most of them are pre-filled with default values,
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).
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.
In the window that appears, first select a NE family from the leftmost list, the Types
selector will be populated accordingly then select one NE type and the Releases selector

ISSUE 1 JULY 2015
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 supervision area.
Press OK when done.
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.
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 configured EML
instance is added to the installation structure diagram.
Note:
Follow the link “Open” on the right of the Hostname to view the “fully configured”
master instance(s).
In the synopsis view of the bench, the instance(s) 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.
Add Master Instance - 1350 OMS HA configuration

If the 1350 OMS HA must be installed select the related check box in “Add Master
Instance: General option”.
Note:
If is needed to configured the 1350 OMS HA for all the VMs of the bench it is
possible to use the button “Create HA pairs” in the “Editing Configuration XXX
(R12.3)” page.
Configure 1350 OMS HA in a Master instance

If the HA check box is selected, a list of mandatory sub-options are displayed (see image
below, light yellow background options):
Autoswitch: select the toggle to enable the function.
Isolation Node: a comma-separated list of addresses that the main and spare VMs will
test for reachability to detect isolation conditions. The list must contain one or more valid
IP addresses and commas, without spaces or any other character.
Site type of this instance: 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.
ISSUE 1 JULY 2015
Hostname of companion instance: the spare (DRC) instance hostname.

IP address of companion instance: the spare (DRC) instance address.
After the configuration of the Master instance(s) with the HA toggle selected the
configurator's main page appears as in the following image; 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 configurator tool highlights the missing parameter. Before proceeding, it is
therefore necessary to visit in Edit mode the spare instance(s) and specify the missing
value.
All the detected/listed errors must be solved, each instance has the total of the issues to
solve listed in a tooltip, fly over the issues’s total to display them.

ISSUE 1 JULY 2015
Note:
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
add/configure the Presentation instances with 1350 OMS HA.
Add Presentation Instance

To add a Presentation instance to the installation structure, press the Orange button. You
are then presented with the following page:

ISSUE 1 JULY 2015
Add Presentation Instance: General option

In this section it is possible to select the installation of the optional 1350 OMS HA
components.
Selecting the HA check box will open a “Site type of this instance” sub-option (light
yellow background) to set the role of the current instance, i.e. NOC.
A partner Presentation instance, with opposite Site type of the already added instance (in
this example DRC), must be added.
If selected the HA component will be installed and configured.
Add Presentation Instance: Dimensioning option

Do not alter the default CPU core count value.
Add Presentation Instance: Network setting

Enter the hostname for the new Presentation instance (click on the information button for
naming rules).
As for the Master Instances it is possible to define up to 5 virtual NICs for the new
Presentation instance: fill only the first N rows as needed, leaving no empty rows (i.e. if 2
virtual NICs are defined use the “NIC eth0 data” and the “NIC eth1 data” rows).
Only for the KVM platform, each virtual NIC is to be associated with a bridge (which
must have been created in advance); specify network information for the instance
selecting the desired bridge, the IP and mask fields must be mandatory filled, optionally
you can also specify the address of a gateway.

ISSUE 1 JULY 2015
Bench configuration result

Here below two example of configured benches with or without the 1350 OMS HA.

ISSUE 1 JULY 2015
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.

ISSUE 1 JULY 2015
The “Create HA pairs” button appears only if no 1350 OMS HA configuration was
done: pressing it the 1350 OMS HA VMs pairs for the already configured VMs will be
created, the configurator tool highlights the missing parameters. Before proceeding it is
therefore necessary to visit in Edit mode the spare instance(s) and update the highlighted
fields value.
In this page you must enter:
 The bench options, select the check box related to the option(s) to be configured for
the bench you are going to install.
 The absolute file path of the repository directory (Depot). 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 (for performance it is recommended to use the local folder).
Note:
In the AI-C for the vmware® platform the depot path is created, as
/DEPOT/<delivery> (i.e. /DEPOT/12.3.0.10), and filled during the SW upload
procedure.

ISSUE 1 JULY 2015
 The initial SSH password for all the VMs (select the link “View Rules” to display
the rules to follow for the password).
 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.
Note:
Refer to “Licences request - KVM platform” paragraph or to“Licenses request -
vmware® platform” paragraphs. For vmware® platform the licenses must be on
1350OMs OTN VM.
 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 1350
OMS license, if no port is specified in the license you have to leave field blank.
Note:
Refer to “Licences request - KVM platform” paragraph or to“Licenses request -
vmware® platform” paragraphs. For vmware® platform the licenses must be on
1350OMs OTN VM.
Note:
In the case of single license server, typically the choice is to specify the host itself
(KVM platform) on top of which the Virtual Machines are running.
 SSL configuration: leave the default value to use the certificates already present in
AI-C or use the “Upload new SSL certificate and key” radio button to upload the SSL
Certificate and key files. The certificates will be installed on all VMs of the
configuration (refer the “Certificate requirements for secure SSL communication”
appendix for details).
Once the described fields are filled, press OK button to proceed.
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 checking whether the
necessary VD files are all present in the specified DEPOT path and generating VM
descriptors for the KVM platform or the VM .ovf files, ready to be deployed, for the
vmware® platform.
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.

ISSUE 1 JULY 2015
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, different between KVM and vmware® platform, will
appear as follows:
 In case of vmware® platform configuration the generated OVF files are available as
link at the bottom of the page (All the OVF generated files are available following the

ISSUE 1 JULY 2015
“Browse OVF generation area” link in the “Main menu” page).

No other configuration actions is needed for vmware® platform.
 In case of KVM platform configuration, three configuration files for each instance of
the bench are generated in /var/autoinstall/R12.3/generated/<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
Note:
The <vm name> is the concatenation of chosen configuration name, hostname, server
type and Instance ID.
Note:
The <bench_prefix> is the chosen configuration name.
Selecting the “Proceed to Network Configuration stage” button a new page will be
shown with the result of the check on the networking setup.
AI-C will compare the bridges and bridge(s) mapping, that are defined, with the available
resources of each host.
AI-C then explains whether:
- the bridges, and their mapping, that are defined are already in place on all hosts of
the configuration so no action is needed.
- the bridges, and their mapping, that you have defined are not in place on all hosts
of the configuration, but they are feasible without conflict with existing
bridges/NICs, so AI-C will automatically carry out all necessary actions to create
them (see example below).

ISSUE 1 JULY 2015
 the bridges, and their mapping, that you have defined are not feasible on one or
more hosts of the configuration (for example a NIC that does not exist is requested
or a NIC to associate with a certain bridge is already busy in another bridge; etc.).
In this case is requested a manually action to free the resources or to solve the
constraints before retrying (see examples below).

ISSUE 1 JULY 2015
Note:
Fly over the "NIC cells" for details on color; use the proposed link to “Modify bridge
mapping configuration” if needed.
When all the issues are solved and the AI-C checks are ok, use the “Align network
bridges” button to execute this action on the configuration host(s).
At the end of the “Align network bridges” process use the available button to go back to
the Network Configuration page.

ISSUE 1 JULY 2015
A button to Deploy the configured bench is now available, press it to start the process: a
new windows will be shown, press the OK button to start the bench installation, the log of
the job will be displayed.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
6 vmware® -
Deploy 1350 OMS VMs
Overview
Purpose
This chapter is meaningful only for vmware® platform and describe all the activities to
be executed to deploy the 1350 OMS VMs on vmware® ESXi infrastructure.
Contents
1350 OMS VMs OVF descriptors 57
Deploy 1350 OMS VMs 58
Licenses request - vmware® platform 64
In order to deploy the defined/configured 1350 OMS VMs open the vSphere client and
connect the target vCenter or ESXi host.
1350 OMS VMs OVF descriptors

The generated OVF descriptor files are available following the “Browse OVF generation
area” link in the AI-C “Main menu” page.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
Deploy 1350 OMS VMs

Login the vmware® vCenter or ESXi via vSphere Client and open the “Deploy OVF
Template” tool by open “File” pull down menu and select “Deploy OVF Template”.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
The following windows will be shown:
For every 1350 OMS VM to be deployed copy the link location from the “OVF
generation area” and insert it in the “Deploy from file or URL” text box then press the
“Next” button, a descriptive window will be shown to allow the check of the appliance
characteristics, press “Next” button to proceed, the “Name and Location” window will be
shown:
ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
In this window the VM name must be chosen (a default name is shown in the “Name:”
text box.
In the “Inventory Location:” the data centre for the VM deployment must be chosen.
Press “Next” button to proceed.
Note:
vmware® does not allow two VMs with same name on the same data centre.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
The shown windows allow to choose the destination host, the first one allows to choose
between cluster, if any, and host: if the selected target is a cluster an additional window
allows to choose the host inside the cluster; select the target and press “Next” button to
proceed with “Storage” window.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
Select one of the data stores listed in the “VM Storage Profile:” then press “Next” button
to continue with the “Disk Format” window.
For the 1350 OMS applications VM is suggested to choose the “Thick Provision Eager
Zeroed” format, press “Next” button to proceed with “Network Mapping” window.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
Choose the “Virtual Switch” where connect the appliance.

Note:
When there are more NICs to be map, them have to be mapped with the right virtual
switch, select the virtual switch and press “Next” button.
The last window summarizes the appliance configuration data; if the data entered are not
correct press “Back” button to go back and change, otherwise press “Finish” button to
complete.
Note:
Take care to select the “Power on after deployment” to automatically execute the first
VM reboot after the deploy in order to properly configure it before the first user login
(in alternative the boot of the deployed VM can be executed by hand).
The deploy of the 1350 OMS VM will start immediately.
When the deploy of a 1350 OMS appliance will be complete, the VM must be run to
allow to perform it auto configuration, at the end of the process the virtual machine will
stop automatically, run it once again, it will be ready for the 1350 OMS NMS installation.
Note:
Power on the deployed VMs selecting it in the vSphere virtual machine inventory and
pressing the run button, a light green right arrow will identify the “power on”.

ISSUE 1 JULY 2015
vmware® -
Deploy 1350 OMS VMs
Licenses request - vmware® platform

Before to proceed with the 1350 OMS installation, after the deploy of the OTN VM(s), it
is necessary to proceed with the licenses request.
The licenses must be requested, as described in “GoGlobal-UX Installation and
Configuration” and “Poseidon Installation and Configuration” appendixes, for the OTN
VM(s) configured in the “Entering global settings” paragraph.
Note:
If the 1350 OMS HA will be installed/configured the licenses must be requested both
for NOC and DRC centers and must be evenly installed (NOC license on NOC OTN
VM and DRC license on DRC OTN VM).
Proceed with the following steps to install the just obtained licenses on OTN VM(s):
 Start the OTN VM via vmware® vCenter or ESXi via vSphere Client
 Log the OTN VM as root and substitute the /opt/poseidon/etc/license.dat license
file with the new one
 Start the Poseidon executing the command:
...,root,root # service poseidon start [Enter]
To check the just installed license log as root user one of the other bench VMs and
execute:
...,root,root # . /etc/Poseidon ; /opt/poseidon/bin/lmstat -a [Enter]

ISSUE 1 JULY 2015
AI-C activity menu
7 AI-C activity menu
Overview
Purpose
This chapter describe all the activities executable accessing the activity menu.
Contents
activity menu 66
activity menu: Install 68
activity menu: Start 69
activity menu: Stop 71
activity menu: Utilities 72
activity menu: Transformation 73
activity menu: Backup/Restore 75
The “activity menu” can be opened both from the main autoinstall windows choosing the
“Actions...” link of the configured system(s) or following the link on top of the bench
configuration schema (see pictures below).

ISSUE 1 JULY 2015
AI-C activity menu
activity menu

ISSUE 1 JULY 2015
AI-C activity menu
A brief description of each job is available flying over its “ name”.

The job executed via “activity menu” open a new windows that show the lines regularly
loaded from the job log; different background colors are used:
 most recently added lines are highlighted in light green (behavior affected by used
browser)
 “Warning:” messages are highlighted in yellow
 “Error:” messages are highlighted in yellow red
Note:
If an error message occur, all the lines are highlighted in orange (see image below as
example).

ISSUE 1 JULY 2015
AI-C activity menu
activity menu: Install
The “Install” option menu propose the following actions:
 Install bench
 the bench configuration will be deployed on the designated target host(s)
ISSUE 1 JULY 2015
AI-C activity menu
Note:
At the end of the installation procedure it is highly recommended to execute a backup

of the just installed VMs following the instruction described in this guide (“activity
menu: Backup/Restore“ procedure); take care to move the backup copy out of the
host(s) to preserve the integrity of the same in case of hardware failure.
If it is needed to configure the ESM, “enhanced security mode”, the backup copy is
mandatory (follow the instruction described in “1350 OMS Administration Guide, Vol
1 -” to configure ESM).
 Configure HA (option available only in HA context)
 If a change is applied in already installed 1350 OMS HA (i.e. switch timer), use
this option to configure the 1350 OMS HA accordingly
 Integration (multiple choices with HA enabled)
 Execute the Integration on selected VM(s)
 Federation (multiple choices with HA enabled)
 Execute the Federation on selected VM(s)
activity menu: Start

ISSUE 1 JULY 2015
AI-C activity menu
The “Start” option menu propose the following actions:
 Start processes (multiple choices with HA enabled)

 this option start the processes on the selected VM(s). Select the NOC or DRC in
case of 1350 OMS HA configuration
 Start VM
 this option start specific VM(s) or on the entire bench, use the drop-down list for
selection
 Start kernel (multiple choices with HA enabled)
 this option start kernel on specific VM(s) or on the entire bench, use the drop-
down list for selection
 Start HA (option available only in HA context)
 this option start the 1350 OMS HA on specific VM(s) or on the entire bench, use
the drop-down list for selection
 Start Control (multiple choices with HA enabled)
 this option start the control on specific VM(s) or on the entire bench, use the drop-

ISSUE 1 JULY 2015
AI-C activity menu
activity menu: Stop
The “Stop” option menu propose the following actions:
 Stop processes (multiple choices with HA enabled)

 this option stop the processes on the selected VM(s). Select the NOC or DRC in
case of 1350 OMS HA configuration
 Stop VM
 this option stop specific VM(s) or on the entire bench, use the drop-down list for
selection
 Stop kernel (multiple choices with HA enabled)
 this option stop kernel on specific VM(s) or on the entire bench, use the drop-
 Stop HA (option available only in HA context)
 this option stop the 1350 OMS HA on specific VM(s) or on the entire bench, use
the drop-down list for selection
 Stop Control (multiple choices with HA enabled)
 this option stop the control on specific VM(s) or on the entire bench, use the drop-

ISSUE 1 JULY 2015
AI-C activity menu
activity menu: Utilities
The “Utilities” option menu propose the following actions:
 Update SSL Certificates

 the new SSL Certificates entered in AI-C GUI will be installed on all VMs of the
configuration
 Processes Status
 this option checks the processes status on the selected VM(s)
 Set Max Trace Level
 Trace Level is set to Maximum in all VMs of the configuration
 Show SW Load
 this option provide the version of 1350 OMS NMS installed on the selected VM(s)

ISSUE 1 JULY 2015
AI-C activity menu
activity menu: Transformation
The “Transformation” option menu propose the following actions:
 Add VMs to bench (meaningful only for KVM platform)

 this option add the “new defined” VMs to the already installed bench; the
configuration of the installed bench must be edited via AI-C in order to add and
configure the new needed VM(s): follow the procedure described in “Add Master
Instance” and in “Add Presentation Instance”.
Note:
 If needed create a new host and assign the added instances to it (only for KVM
platform).
 The Add VMs procedure works only with Presentation, 1340OMS EML and 1350
OMS OIS master instances.
 The already existing VMs continue to be running and operator could be connected
while the “Add VMs to bench” procedure is running.
 If the addition was made in a 1350 OMS HA context it also need to start the 1350
OMS HA on NOC and DRC centers (“activity menu: Start”).
 Add HA to bench (option available only in HA context and meaningful only for
KVM platform)
PRE-CONDITIONS

ISSUE 1 JULY 2015
AI-C activity menu
 Only for KVM platform, the DRC server(s) is/are already installed with operating
system bootable and autoinstall, with sc-vadeploy, is installed (see Related
information for “1350 OMS R12.3 HW and OS Installation Guide”)
 DRC server(s) is/are connectable from AI-Driver.
Allow SSH connection from "AI Driver", NOC for 1350 OMS HA, to other
host(s), DRC for 1350 OMS HA: connect to the "AI Driver" (the VM/host server
on which 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/R12.x [Enter]
...,root, root # utilities/allowToRemote.sh <DRC-host-IP-address> [Enter]
 1350 OMS load is available in all the hosts of the bench in the same directory (as
defined in “Entering global settings”)
In the following instructions to add 1350 OMS HA DRC bench it is assumed:
 NOC (master) becomes active and DRC (spare) becomes the stand-by
 new server(s) (DRC-host) is added in the configuration to host only DRC VMs
this option add the 1350 OMS HA functionality to the already installed bench; the
configuration of the installed bench must be edited via AI-C in order to add the 1350
OMS HA to the already defined VMs and to properly configure the updated bench (refer
to the related chapter of this guide).
At the end of the configuration the following list of actions must be executed:
 Install the DRC server selecting “DRC” from drop-down list in “Install” option of
“activity menu: Install”
 Start the processes on ALL the DRC VMs (see “activity menu: Start”)
 Stop the processes on ALL the DRC VMs (see “activity menu: Stop”)
 Insert the directory/depot of 1350 OMS load into “Path to depot:” box and execute
the “Add HA to bench” on NOC (execute the action in current menu)
 Execute the “Integration” on ALL the DRC VMs (see “activity menu: Install”)
 “Start HA” on ALL the DRC VMs (see “activity menu: Start”)
 “Start HA” on ALL the NOC VMs (see “activity menu: Start”)
 Change hostname(s) (multiple choices with HA enabled - meaningful only for KVM
platform)
The “Change hostname” option menu is meaningful only for KVM platform.
 this option change the hostname(s) of the VM(s) defined in current bench: the
hostname(s) must be updated via the edit option of the AI-C. The “Change
hostname procedure“ is only applicable to VMs and not to the Host.
Note:
If the Change hostname must be executed in 1350 OMS HA context the following list of
actions must be executed:
 execute the “Change hostname” on DRC (execute the action in current menu)

ISSUE 1 JULY 2015
AI-C activity menu
 Stop the processes on ALL the NOC VMs (see “activity menu: Stop”)
 Start the processes on ALL the DRC VMs (see “activity menu: Start”)
 execute the Change hostname on NOC (execute the action in current menu)
 Start 1350 OMS HA on DRC (see “activity menu: Start”)
 Start 1350 OMS HA on NOC (see “activity menu: Start”)
All the actions are described in this guide in the related “activity menu” section.
Note:
If a VMs backup was executed before the execution of the “Change hostname procedure“
a new backup must be performed at the end of that (“activity menu: Backup/Restore”).
 Sync Up NE Adapter Config
 This option extract and import in the AI-C information about NE Adapter from
existing and running EML VM (select from list the EML VM to manage). It is
useful to line-up the AI-C bench configuration if changes was done (add NEs) on
the bench after the first installation (via system configuration).
activity menu: Backup/Restore
The “Backup/Restore” option menu is meaningful only for KVM platform.

The “Backup/Restore” option menu propose the following actions:
 Backup VMs

ISSUE 1 JULY 2015
AI-C activity menu
 this option execute a Backup of the VMs configured in the active bench
Notes:
 Only for KVM platform: if the bench to backup is distributed on more than one
HOST, as prerequisites the MW_OS RPMs and the AI-C must be installed on
ALL the HOST servers.
 At the end of the procedure, the VMs backup will be in /var/lib/libvirt/backup (in
case of Multi Host configuration the backup will be executed and stored on each
host); a directory for each VM of the bench is created containing a log file and
maximum three backup copies (the backups are located in different numbered
directories, the directory “1” contains the last backup copy). If the backup
procedure will find three old backup copies, the oldest will be deleted.
 The backup can be executed on local disk or on an external storage (NFS or USB),
in this case the performance will be lower with a major downtime.
In order to use an external storage mount it on /var/lib/libvirt/backup directory.
 If a backup must be executed, use the following tables to keep note data to be used
in case of restore after an hardware failure.
Hostname Host IP Host netmask
Note:
In order to backup the host ssh keys of the 1350 OMS VMs, save the following
host files on an external support:
/root/.ssh/id_rsa
/root/.ssh/id_rsa.pub
/root/.ssh/id_dsa
/root/.ssh/id_dsa.pub
 Restore VMs
 this option execute the restore of the backup of the VMs belonging to the active
bench
Notes:
 The procedure will restore the most recent backup version of the bench available
in /var/lib/libvirt/backup (see backup procedure for details).
 The backup copy can be stored on local disk or on an external storage (NFS or
USB), in this case the performance will be lower with a major downtime.
In order to use an external storage mount it on /var/lib/libvirt/backup directory.
ISSUE 1 JULY 2015
AI-C activity menu
 The bridge(s) and the NIC(s) must be re-defined as in previous configuration

following the instructions in “Configuring Network Bridges“.
 In case of hardware failure, the restore of the VMs must be run after the re-
installation of the new hardware and after the installation of the (AI-C) software
on the AI-driver host as described in “1350 OMS R12.3 HW and OS
Installation Guide” (see Related information).
The ssh connection between host and VMs must be reset: restore, if available, the
backup of the id_rsa , id_rsa.pub, id_dsa and id_dsa.pub files in /root/.ssh path
or execute the following commands:
...,root,root # cd /var/autoinstall/R12.3 [Enter]

...,root,root # utilities/allowToRemote.sh <all_VM-IP-addresses> [Enter]
activity menu: Migration
The “Migration” option menu propose the following actions:
 Predispose
 this option predispose the source bench for migration-backup
ISSUE 1 JULY 2015
AI-C activity menu
 Save Source Data

 this option save the source configuration and backup data (if any)
 Backup Source Data
 this option Backup the selected source data
 Restore Source Data
 this option Restore the selected source data on current bench
 Source Data Conversion
 this option Convert the selected restored source data on current bench
Notes:
a. The PM data restore is mandatory after NTW data restore in case of “Restore
Source Data” execution including EML subsystem, it can be execute together
selecting the proper menu option.
b. Use the proper menu option to set the “Network Elements Supervision State” at
the end of the process.

ISSUE 1 JULY 2015
AI-C activity menu
A Post Installation
Overview
Purpose
The appendix describe how to execute post installation actions and workaround required
to modify the already performed installation.
Please avoid to execute in installation phase any of the actions if not expressly
requested by a workaround.
Contents
Post Installation instructions (execute on VMs) 79
Post Installation instructions 80
“Enable” 1350OMS HA 80
Post Installation Workaround 81
Post Installation instructions (execute on VMs)

System Configuration
If expressly request by a workaround here below the instructions to execute the System
Configuration procedure.
Login the VM as root and execute the following commands:
...,root,root # chmod a+x /usr/bin/xhost [Enter]
...,root,root # xhost + local: [Enter]
...,root,root # cd /alu/Install_Wizard [Enter]
...,root,root # ./Install.sh –config [Enter]
Note:
ISSUE 1 JULY 2015
AI-C activity menu
Move the “System config” splash window in order to accelerate the load of the items.
At the end of System Configuration execute the following command to disable xhost
(security reasons):
...,root,root # xhost - [Enter]
...,root,root # chmod a-x /usr/bin/xhost [Enter]
Post Installation instructions

Data Backup/Restore
Action to be performed on the operator’s PC in case of data backup/restore; in the
following directory path:
C: System -> Windows -> System32 -> drivers -> etc
add the IP addresses and hostname mapping in the hosts file to establish communication,
example:
151.98.80.105 emlhostname
151.98.80.106 pkthostname
151.98.80.107 otnhostname
151.98.80.108 preshostname
Disable FTP service

At the end of 1350 OMS installation the FTP service is enable on the EML VM(s)
because needed to some NE families; if the network to manage does not have NEs that
needs the service it is possible to disable it executing the following command:
...,root,root # scDisableFTP [Enter]
Note:
If in the future it is needed to update the network with NEs that need the ftp service
execute to following command to enable it:
...,root,root # scEnableFTP [Enter]
“Enable” 1350OMS HA
If the just installed bench have 1350OMS HA configured, the following actions must be
performed in order to enable the HA functionalities.

ISSUE 1 JULY 2015
AI-C activity menu
Start processes on NOC

Execute the “Start processes” command on NOC center from the “Activity Menu =>
Start” menu: select the proper options from the dropdown menus then press the
“Execute” button.
Start 1350OMS HA on DRC

Execute the “Start HA” command on DRC from the “Activity Menu => Start” menu:
select the proper options from the dropdown menus then press the “Execute” button.
Start 1350OMS HA on NOC

Execute the “Start HA” command on NOC from the “Activity Menu => Start” menu:
select the proper options from the dropdown menus then press the “Execute” button.
Post Installation Workaround

FM and AS EVENTS services down
After the installation execute the following command in order to solve the issue.
Log the AI-Driver as root user and execute:
...,root,root # cd /var/autoinstall/Rx.y
...,root,root # ./utilities/execOnBench.sh <bech_prefix>_bench complete start-kernel
PKT Technology maps not available in MSGUI

In order to have PKT Layered Map menu in OMSGUI the described actions must be
performed on OTN master instance; the workaround must be executed before to open the
GUI.
Edit the following files:
<OTN_Master>/MAPIM/script/StartMapIm_1.sh
by adding a line
export NXNL_PKT=$NXNL_DATABASE
after the #AUTO_END comment line then restart the MAPIM executable.
ISSUE 1 JULY 2015
AI-C activity menu
Note:
The workaround has NOT to be applied if PKT NMS is NOT present.

ISSUE 1 JULY 2015
AI-C activity menu
B 1350 OMS NMS

composition table
Overview
Purpose
In this appendix are listed all the files needed to install the 1350 OMS Network Manager.
Contents
1350 OMS Network Management composition tables.
Checksum Size ISO files
2909521306 3997384704 1350OMS-MW_OS-Boot-V6.6-It4_x86_64.iso
3042331477 280442880 1350OMS-MW_OS-NetBoot-V6.6-It4_x86_64.iso
3302791542 4638619648 1350OMS-MW_OS-PLT-V12.3.0-RHEL6.6_x86_64-It4.iso
Checksum Size vmware® AI Driver VM files
1878524825 727580160 AI-Driver-3.1.5-disk1.vmdk
1266573133 380928 AI-Driver-3.1.5-disk2.vmdk
4038378132 221 AI-Driver-3.1.5.mf
335536732 10667 AI-Driver-3.1.5.ovf

ISSUE 1 JULY 2015
AI-C activity menu
Checksum Size Descriptor file
3979088637 2068 1350OMS-LX_12.3.0.52.descx
The descriptor (descx) file contains the Checksum and Size of the following 1350 OMS
Composition files.
Virtual Disk files
1350OMS_EML_12_12.3.0.50.vmdk.img
1350OMS_IW_12_12.3.0.50.vmdk.img
1350OMS_OIS_12_12.3.0.50.vmdk.img
1350OMS_OTN_12_12.3.0.50.vmdk.img
1350OMS_PKT_12_12.3.0.50.vmdk.img
1350OMS_PLT_12_12.3.0.50.vmdk.img
VD-MW_OS-12.3.0_1.vmdk.img
RPM files
1350OMS-MW_OS-repos-12.3.0-10.el6.x86_64.rpm
1350OMS-MW_OS-sec-12.3.0-10.el6.x86_64.rpm
autoinstall123-2.0-251.noarch.rpm
1350OMS-MW_OS-12.3.0-10.el6.x86_64.rpm
1350OMS-MW_OS-bck-12.3.0-10.el6.x86_64.rpm
1350 OMS EML additional packages grouped for NE families
1350OMS-EML_1646_12.3.0.52_on_top.tar.gz

ISSUE 1 JULY 2015
AI-C activity menu
1350 OMS EML additional packages grouped for NE families
1350OMS-EML_3PP_12.3.0.52_on_top.tar.gz
1350OMS-EML_CORE_EXT_12.3.0.52_on_top.tar.gz
1350OMS-EML_DXC_12.3.0.52_on_top.tar.gz
1350OMS-EML_OMSN_12.3.0.52_on_top.tar.gz
1350OMS-EML_RADIO_12.3.0.52_on_top.tar.gz
1350OMS-EML_WDM_12.3.0.52_on_top.tar.gz
patches on top
1350OMS-LX_12.3.0.52_on_top.tar.gz

ISSUE 1 JULY 2015
AI-C activity menu
C Export/Import procedure
Overview
Purpose
The appendix describe the procedure to Export/Import an existing bench configuration; it
can be use, in example, in case of hardware replacement or in case of migration if the
source bench do not use the autoinstall configuration (i.e. R9.6 HPUX).
Contents
Export configuration from bench WITH direct connection with the new 86
host
Export configuration from bench WITHOUT direct connection with the 88

new host
Import exported configuration on target host 89
Notes for R9.6 HP-UX Migration 89
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 at the target bench via AI-C (see Add Presentation Instance).
In order to export the configuration files (with extension .NMS_parameter) from the
source bench, login as root user on the target AI-driver and execute the following
commands to generate the hosts key pair:

ISSUE 1 JULY 2015
AI-C activity menu
...,root,root # cd /var/autoinstall/ Rxx.y [Enter]
In case of HPUX source bench it is needed to install the R9.6 autoinstall tool from
/DEPOT/<1350OMS build>/AI/R9.6 and install the autoinstall96<version>.noarch.rpm
file and the previous command will be “...,root,root # cd /var/autoinstall/R9.6”. Then proceed
executing:
...,root,root # ./utilities/allowHP_To_Remote.sh <source IP address> [Enter]
In case of to the Linux source bench execute:
...,root,root # cd ./utilities/allowToRemote.sh <source IP address> [Enter]
Then, in case of HPUX source bench, execute:
...,root,root # cd /var/autoinstall/ Rxx.y/export_DIR [Enter]

...,root,root # ./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.
Notes:
- 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:
o EMLIM id
o NECOM/Supervision Areas (to be modified via AI-Config after the
import)
o 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/R9.6/export_DIR/*.NMS_parameter
/var/www/html/export [Enter]

ISSUE 1 JULY 2015
AI-C activity menu
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).
Example: https://<AI-driver IP-address>/export/EML_1.NMS_parameter
Export configuration from bench WITHOUT direct connection

with the new host
The following procedure cannot be used for HPUX R9.6 source benches.
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). 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 at the target
bench via AI-C (see Add Presentation Instance).
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]
Notes:
The 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.

ISSUE 1 JULY 2015
AI-C activity menu
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/ ensuring to preserve the right format.
Import exported configuration on target host

We are now ready to access the Access 1350 OMS configuration Tool to configure the
network bridges (only KVM platform) and to create the new configuration (see Create
R12.3 configuration).
The exported configuration files can be imported in the new configuration in two different
ways: via option“Create empty Rxy.z configuration“ and then using the “green arrow”
button or via option “Create new Rxy.z configuration from file“ (see Create R12.3
configuration). The exported configuration files can be provided one by one or as a
compressed file (see AI-C windows for supported compressed format).
Once all the exported files have been uploaded, the configuration will be shown.
The AI-C tool highlights in red the missing/wrong parameters. Before proceeding, it is
therefore necessary to visit in Edit mode each uploaded instance to properly update the
highlighted field before to proceed with configuration editing (see Configuration editing)
or entering the global settings (see Entering global settings) to complete the configuration
steps.
Note:
Furthermore, before proceeding, it is also possible to edit the imported configuration:

for example to add missing Network Elements, new VMs (e.g. 1350OMS WDM if
required to manage added PSS NE or additional 1350OMS EML instances to manage
larger networks).
Notes for R9.6 HP-UX Migration

If the procedure must be used to migrate a R9.6 HP-UX host some actions are needed to
be able to use the autoinstall features. The R9.6 autoinstall, delivered into the target
release software depot, must be installed on target AI-Driver (refer the Migration
Scenarios document for details)

ISSUE 1 JULY 2015
AI-C activity menu
 If the source HP-UX bench have a Presentation instance, after the import of the
NMS_parameter files of the master instances, add tocreated bench the source
Presentation.
 If the source HP-UX bench have NOT a Presentation instance, after the import of
the NMS_parameter files of the master instances, add to created bench a
Presentation with the IP address of the source HPUX host. Configure the target
bench with centralized LDAP.

ISSUE 1 JULY 2015
AI-C activity menu
D GoGlobal-UX Installation
and Configuration
Overview
Purpose
The appendix describe the procedure to install and configure GoGLobal-UX.
Contents
GoGlobal-UX Installation on 1350 OMS 91
GoGlobal-UX Installation on PC 91
GoGlobal-UX license 92
GoGlobal-UX authorization procedure 95
Start License Server and GraphOn Daemons 97
GoGlobal-UX Installation on 1350 OMS

The GoGlobal-UX software is already installed on the system.
GoGlobal-UX Installation on PC
The GOGlobal-UX PC Client software is available as go_setup executable within
/opt/graphon/pc/ directory, to retrieve it a secure SSH connection must be use, this can
be done by installing on PC a tool that allow such a transfer, the suggested one is Filezilla
where is possible to define a SFTP connection to access the host server.

ISSUE 1 JULY 2015
AI-C activity menu
Note:
Be careful that SSH usage can be forbidden to root user.
When the go_setup is present on the PC, execute it to run the installation (if a previous
version was installed will be requested to remove it before to install the current one).
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.
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, if possible, should be located physically close to
each other.
 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 described
in “Permanent License Request” paragraph.
Retrieve License Servers Identity

ISSUE 1 JULY 2015
AI-C activity menu
When you have selected the license server(s), for each of them it is needed to retrieve the
server identity (Meaningful only for the license servers): the data will be used to request
the licenses.
Login the server as root user and execute the following command to retrieve the
“hostname” and the “FLEXlm host ID”:
...,root,root # uname -n [Enter]

...,root,root # /opt/graphon/bin/lmhostid [Enter]
Permanent License Request
This action is meaningful only for the license servers. Visit the GraphOn Licensing web
site to require the license(s) to activate the installed GoGlobal-UX on your server(s).
For three redundant: http://license.graphon.com/user/redundant_pcode.cgi
Fill the field as described below then press the “Obtain License” button and follow the
proposed procedure:
 Name (1)
 Company (1)

ISSUE 1 JULY 2015
AI-C activity menu
 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.
For single node: http://license.graphon.com/user/
Fill the required field and then press the “Obtain License” button and follow the proposed
procedure.
Note:
The license(s) request procedure must be executed for each “Product CodE2 indicated in
“PURCHASED GraphOn LICENSE FOR ALCATEL-LUCENT USE OR RESALE"
document.

ISSUE 1 JULY 2015
AI-C activity menu
GoGlobal-UX authorization procedure

Here below the information to properly configure the GoGlobal-UXTM license files and
daemons; the following action must be performed:
2. Store the authorization key in the license file.
3. Configure the license servers machine(s).
4. Start the license server daemons.
5. Configure license client system(s) (if any)
Store the Authorization Key in the License File
Copy the just obtained GrapON licence in the /opt/graphon/etc/license.dat, this action
must be performed for each license server.
Create the file as root user executing the command:
...,root,root # vi /opt/graphon/etc/license.dat [Enter]
Here below an example of license.dat file, please take care to update the the line with the
SERVER definition adding the 27001 port number at the end-of-line (see the related
example).
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
Example for 27001 port addition (Add TCP port number (27001) at any line beginning
with SERVER); change from:
SERVER host_c 839dc26

ISSUE 1 JULY 2015
AI-C activity menu
to:
SERVER host_c 839dc26 27001
Copy this file on each license server when the three redundant configuration is foreseen.
Configure License Server
An Alcatel-Lucent extension to the GraphOn license management is the

license_server.dat file; it has to declare all the license servers useful for retrieving license
from any host need to use them, including the license servers hosts themselves.
The easy way to proceed is to create these files on the license server(s) and them
distribute them to the client during configuration
Note:
Each time the license_server.dat change, the changes will be recognize only at the next
GoGlobal-UX start-up.
To declare the license servers the file /opt/graphon/etc/license_servers.dat must be
created and filled following the syntax:
SERVER <host> <port>
Where:SERVER is 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 line
starting with SERVER, if that field is empty 27001 port have to be used.
Here below an example (command execute as root user):
...,root,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
Copy the saved license_servers.dat 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.

ISSUE 1 JULY 2015
AI-C activity menu
Start License Server and GraphOn Daemons

When both license.dat and license_server.dat files have been properly configured on all
license server(s), it is possible to start-up the daemon.
Because the start-up launches both License and GraphOn Daemons, it is advisable to
execute the daemon stop before:
...,root,root # service goglobalux stop [Enter]

..,root,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, the user will be able to open a
GoGlobal-UX 2.0 session from any PC to the license server machine.

ISSUE 1 JULY 2015
AI-C activity menu
E Poseidon Installation and

Configuration
Overview
Purpose
The appendix describe the procedure to install and configure Poseidon license, the license
software manager used to authorize the Alcatel-Lucent Software execution. For License in
1350 OMS HA context refer the “Install 1350OMS License in HA Configuration”
appendix of this document.
Note:
THE AUTHORIZATION LICENSE REQUEST CAN BE EXECUTED ONLY BY
AUTHORIZED ALCATEL-LUCENT PERSONAL.
Contents
Poseidon License Management Configuration 98
Retrieve License Servers Host Identifier 99
Require the Authorization License 100
Check the License Status 100
Poseidon License Management Configuration

The package foreseen to manage network floating license, that means it is possible to
define one or more system in the 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:
ISSUE 1 JULY 2015
AI-C activity menu
 the three license server machines, if possible, should be located physically close to
each other.
 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 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.
Retrieve License Servers Host Identifier

When you have selected the license server(s), for each of them you have to retrieve the
host identifier by executing the following commands:
Login the server as root user and execute the following command to retrieve the
“hostname” and the “host identifier”:
...,root,root # uname -n [Enter]

...,root,root # /opt/poseidon/bin/lmhostid [Enter]
Keep the retrieved data using the following form (3 line will be filled for “Three Server
Redundant License” or only the first line for “Single License”):
Hostname Host Identifier

ISSUE 1 JULY 2015
AI-C activity menu
Require the Authorization License

The license can be require via Alcatel-Lucent Intranet Web, by authorized Alcatel-Lucent
personal only to https://nmfactory.web.alcatel-lucent.com/Welcome.aspx/
Store the Authorization Key in the License File
The provided license authorization key must be updated to add the port number at the end
of each “SERVER" line as show in the following example:
From:
SERVER hosta 839dc26
To:
SERVER hosta 839dc26 <port number>
Store the updated license in the /opt/poseidon/etc/license.dat file of any machine that have
to execute Alcatel-Lucent software, then start the Poseidon software on it executing the
following command as root user:
...,root,root # service poseidon stop [Enter]

...,root,root # service poseidon start [Enter]
Check the License Status

Execute the following command as root user oo check the license server availability and
license status:
...,root,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 daemon 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

ISSUE 1 JULY 2015
AI-C activity menu
The server status shows the license server names, which is the current license server
master and License server status: <port number>@hosta,<port number>@hostc,<port
number>@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
Redundant Connectivity
The three redundant servers work properly only if each server is able to communicate
with the other two. Check the server configuration and connectivity executing a network
“ping" from each license server to any other one.
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 executing:
...,root,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat [Enter]

ISSUE 1 JULY 2015
AI-C activity menu
F Install 1350OMS License in

HA Configuration
Overview
Purpose
The appendix how to properly set up the license server in 1350OMS HA configuration .
Note:
THE AUTHORIZATION LICENSE REQUEST CAN BE EXECUTED ONLY BY
AUTHORIZED ALCATEL-LUCENT PERSONAL.
Contents
Sequence of actions in Red Hat kVM enviroment 104
Sequence of actions in vmware® environment 105
The candidate machines to host the license manager must be identified:
 kVM environment: the host should be the server that hosts the OTN VM
 vmware® environment: the OTN VM should be defined as license manager host
The 1350OMS licenses must be requested separately for NOC and DRC, specifying the
host ID of NOC machine for the standard 1350OMS license points ( i.e all application
license point except HA ), and the host ID of DRC machine for the 1350OMS (HA
license points only). Appropriate 3rd party software licenses should be installed on both
NOC and DRC hosts.

ISSUE 1 JULY 2015
AI-C activity menu
The license request will return two files, one for NOC and one for DRC, each one of these
files has to be stored in /opt/poseidon/etc/ directory of the machine defined to be the
license server for the appropriate side of 1350OMS (main and spare).
In both cases, at system definition time the two candidate license managers have to be
specified with hostname, IP Address and Port in the “Poseidon license information”
section of the Auto Install Web tool (see following figure)
If you are deploying 1350OMS on kVM the host ID of the candidate servers can be
obtained as soon as the RHEL is installed on servers , whereas for vmware® the OTN
virtual machine host ID will be available only after initial deployment, so for this reason
the sequence in the procedure is a little different.
Note:
The three redundant configuration is not supported for 1350OMS running an HA
configuration..

ISSUE 1 JULY 2015
AI-C activity menu
Sequence of actions in Red Hat kVM enviroment

1. Install server with RHEL 6.6
2. Log in as “root” user and retrieve the host ID of the server candidate to host OTN
virtual machine, by entering: /opt/Poseidon/bin/lmhostid
Note: If the command issued more than one value, use the first one.
3. Require the license to NMLF, then store license file in /opt/poseidon/etc/ directory of
the machine candidate to be the license servers.
4. Start “Poseidon” service on both servers entering: service poseidon start
5. Define the 1350OMS system specifying the license manager machine in the “Poseidon
license information” of Auto Install Web tool (see Figure 1)
6. Perform the virtual machine deploy and installation.
7. Review license configuration on the NOC VMs entering:
,root,root # cd /var/autoinstall/Rx.y
,root,root # ./utility/execOnBench.sh <bench_file>.noc complete\
“ echo SERVER <NOCLMH> ANY 27000 > /opt/poseidon/etc/license.dat”
Where:
<bench_file> is the name of the 1350OMS bench description file (ex.
NMS_bench)
<NOCLMH> NOC license manager hostname
8. Review license configuration on the DRC VMs entering:

,root,root # ./utilities/execOnBench.sh<bench_file>.drc complete \
“ echo SERVER <DRCLMH> <DRCLMIP> ANY 27000 >
/opt/poseidon/etc/license.dat”
Where:
NMS_bench)
<DRCLMH> DRC license manager hostname
9. Start Poseidon and terminate current PMC2IM daemons on entire system:
,root,root # ./utilities/execOnBench.sh<bench_file> complete “service poseidon
start”
,root,root # ./utilities/execOnBench.sh<bench_file> complete \ “fuser -k
/usr/Systems/*/maintenance/trace/pmc2im.outerr”

ISSUE 1 JULY 2015
AI-C activity menu
Where:

NMS_bench)
10. Perform a check of License configuration on VMs log in one or more VMs on NOC
entering command:
,root,root # . /etc/Poseidon ; /opt/poseidon/bin/lmstat
The output has to be like, where the host name shown in red have to correspond to
NOC host:
lmstat - Copyright (c) 1989-2013 Flexera Software LLC. All Rights Reserved.
Flexible License Manager status on Fri 6/19/2015 16:35
License server status: 27000@hostnoc

License file(s) on hostnoc: /opt/poseidon/etc/license.dat:
achille: license server UP (MASTER) v11.11
Vendor daemon status (on hostnoc):
alcatel: UP v9.5
11. Repeat License configuration check of previous point on DRC VMs, where the host
name shown in red have to correspond to NOC host.
Sequence of actions in vmware® environment

1. Deploy the AI-Driver and Upload the software as described in previous installation
chapters.
2. Define the 1350OMS system specifying the OTN virtual machines in the “Poseidon
license information” of Auto Install Web tool (see Figure above)
3. Perform the 1350OMS VM deploy via vSphere client
4. Start all virtual machines, log in OTN VMs as “root” user and retrieve the host IDs by
entering:
/opt/Poseidon/bin/lmhostid

ISSUE 1 JULY 2015
AI-C activity menu
Note: If the command issued more than one value, use the first one.
5. Create bench information:
,root,root # ./utility/createBenchConfig.sh prefix=<bench name>
Where:
<bench_name> is the name of the 1350OMS bench defined via web.
6. Review license configuration on the NOC VMs entering:
,root,root # ./utilities/execOnBench.sh<bench_file>.noc complete \

“ echo SERVER <NOCLMH> ANY 27000 > /opt/poseidon/etc/license.dat”
Where:
NMS_bench)
<NOCLMH> NOC license manager hostname
7. Review license configuration on the DRC VMs entering:
,root,root # ./utilities/execOnBench.sh<bench_file>.drc complete \
“ echo SERVER <DRCLMH> ANY 27000 > /opt/poseidon/etc/license.dat”
Where:
NMS_bench)
<DRCLMH> DRC license manager hostname
8. Require the license to NMLF, then store license file in /opt/poseidon/etc/ directory of
OTN VMs.
9. Start “Poseidon” service on both servers entering:
service poseidon start
10. Start the 1350OMS installation (refer the previous chapter for details)
11. Perform check of License configuration on VMs log in one or more VMs NOC and
enter command:
,root,root # . /etc/Poseidon ; /opt/poseidon/bin/lmstat
The output has to be like, where the machine name shown in red have to correspond to
ISSUE 1 JULY 2015
AI-C activity menu
OTN VM of NOC:
lmstat - Copyright (c) 1989-2013 Flexera Software LLC. All Rights Reserved.
Flexible License Manager status on Fri 6/19/2015 16:35
License server status: 27000@otnnoc

License file(s) on otnnoc: /opt/poseidon/etc/license.dat:
achille: license server UP (MASTER) v11.11
Vendor daemon status (on otnnoc):
alcatel: UP v9.5
12. Repeat License configuration check of previous point on DRC VMs, where the
machine name shown ing “otnnoc” have to correspond to OTN VM of DRC.

ISSUE 1 JULY 2015
AI-C activity menu
G Certificate requirements
for secure SSL
communication
Overview
Purpose
The appendix describe the requirements to properly enable SSL protected
communications between the PC client and the 1350OMS VMs.
Contents
wildcard SSL certificate requirements 108
no custom certificate 109
In order to enable SSL protected communications between the PC client and the
1350OMS server VMs you will need to obtain a SSL certificate from a trusted Certificate
Authority. The CA is trusted if it is enrolled in the list of root CAs of Internet Explorer
(there are several CAs pre-enrolled, or you can enroll your own to be able to self-produce
of certificate+key).
If the SSL certificate does not come from a trusted CA then SSL communication will still
take place, but at the first connection you will get a warning message about the untrusted
certificate.
If you do not have a wildcard SSL certificate then a default, untrusted SSL certificate will
be automatically installed and used; skip to “no custom certificate” paragrhaph .
wildcard SSL certificate requirements

 1350OMS VMs hostnames shall all belong to the same domain (e.g. mydomain.com)

ISSUE 1 JULY 2015
AI-C activity menu
 The SSL certificate must be a wildcard SSL certificate for that domain (e.g.
*.mydomain.com). Some certificate vendors indicate this as “SSL certificate for
unlimited subdomains”.
 It must be possible for the client PC to resolve the fully qualified hostnames of all
VMs (Example: <emlhostname>.mydomain.com, <otnhostname>.mydomain.com,
<pkthostname>.mydomain.com) either via DNS or using local hosts file.
 (Recommended for better security) the certificate should have a 2048-bit strength.
 Supported certificate encodings: ASCII or DER (automatically detected). Certificate
filename suffix is irrelevant.
 Supported key encodings: PEM or DER (automatically detected). Key filename suffix
is irrelevant.
no custom certificate
 1350OMS VMs hostnames can belong to any domain (or no domain at all)
 A default, untrusted SSL certificate is automatically installed for you

ISSUE 1 JULY 2015
AI-C activity menu
H Abbreviations
3PP
Third Party Product
AI-C
AutoInstall Configurator
C
CA
Certificate Authority
CoT
Contents on Top
ESM
Enhanced Security Mode
G
GUI
Graphical User Interface
IP
Internet Protocol
N
NIC
Network Interface Controller/Card
NE
Network Element

ISSUE 1 JULY 2015
AI-C activity menu
NMS
Network Management System
O
OVF
Open Virtualization Format
PC
Personal Computer
PMC
Process Monitor Control
S
SW
Software
VD
Virtual Disk
VM
Virtual Machine

ISSUE 1 JULY 2015

8DG43091NAAA - V1 - 1350OMS R12.3 Installation Guide

Uploaded by

Copyright:

Available Formats

8DG43091NAAA - V1 - 1350OMS R12.3 Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

8DG43091NAAA - V1 - 1350OMS R12.3 Installation Guide

Uploaded by

Copyright:

Available Formats

1350 OMS Installation Guide

1350 OMS | Release 12.3

Add Master Instance: Dimensioning option ............................................................................................ 42

1350 OMS Installation Guide Alcatel-Lucent — Proprietary v

1350OMS R12.3 HW and OS Installation Guide 8DG 43091 WAAA

1350OMS R12.3 Migration Scenarios 8DG 43091 KAAA

1350 OMS R12.3 Administration Guide, Vol 1

1350 OMS R12.3 Administration Guide, Vol 2

1350 OMS R12.3 Platform Guide 8DG 43091 BAAA

1350 OMS R12.3 OTN Guide 8DG 43091 QAAA

1350 OMS R12.3 16x6 Photonic Guide 8DG 43091 RAAA

1350 OMS R12.3 PKT Guide 8DG 43091 DAAA

1350 OMS R12.3 Service Assurance Guide 8DG 43091 FAAA

1350 OMS R12.3 HA Guide 8DG 43091 GAAA

1350 OMS R12.3 OI Guide 8DG 43091 HAAA

1350 OMS Installation Guide Alcatel-Lucent — Proprietary 1

1350 OMS R12.3 OI NBI Guide 8DG 43091 JAAA

1350OMS R12.3 User Interface Guide 8DG 43091 EAAA

1350OMS R12.3 SDH Guide 8DG 43091 CAAA

2 Alcatel-Lucent — Proprietary 1350 OMS Installation Guide

Online VDs reassembly 4

Install Virtual Machine Tools - KVM platform 6

VDs reassembly – vmware® platform 8

Install Virtual Machine Tools - vmware® platform 9

1350 OMS Installation Guide Alcatel-Lucent — Proprietary 3

VD files for Guest OS and

1350 OMS Applications

SWP-1350OMS-AI_Driver-V3.1.5-LX 1350 OMS AI Driver 8DG 43058 ADAA

Online VDs reassembly – KVM platform

...,root,root # mkdir -p /DEPOT/<1350OMS build> [Enter]

Example of repository path /DEPOT/12.3.0.99

Wrong reference to VD Library base path: /root/DEPOT/NR12.x/1350 OMS -

4 Alcatel-Lucent — Proprietary 1350 OMS Installation Guide

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

...,root,root # mkdir /mnt/dvd [Enter]

(insert disk and allow a few seconds..)

...,root,root # mount /dev/sr0 /mnt/dvd [Enter]

...,root,root # cat VD-MW_OS-12.x.y_z.vmdk.img00 VD-MW_OS-

...,root,root # md5sum * [Enter]

1350 OMS Installation Guide Alcatel-Lucent — Proprietary 5

Install Virtual Machine Tools - KVM platform

After mounting the DVD SWP-1350OMS-MW_OS-VD-V12.x.y-LX under a mount point

Before to run the 1350OMS-MW_OS-<version> installation on the host, it is

...,root,root # rpm -i 1350OMS-MW_OS-<version>.el6.x86_64.rpm 1350OMS-

...,root,root # rpm -q sc-vadeploy [Enter]

6 Alcatel-Lucent — Proprietary 1350 OMS Installation Guide

...,root,root # rpm -U <package-package_version> [Enter]

...,root,root # rpm -i autoinstall<version>.noarch.rpm [Enter]

After the installation of the “autoinstall package” a random password will be

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

...,root,root # cd /var/autoinstall/R12.x [Enter]

1350 OMS Installation Guide Alcatel-Lucent — Proprietary 7

Licences request - KVM platform

VDs reassembly – vmware® platform

<disk>:\<temp_dir_path> copy /B <to_be_reassembled_VD>.vmdk.img00 + /B

Obtain the Hash-Tool free utility (http://download.cnet.com/Hash-Tool/3000-2248_4-

Select the SHA-512 Hash Type to properly check the file(s).

8 Alcatel-Lucent — Proprietary 1350 OMS Installation Guide

Install Virtual Machine Tools - vmware® platform