• No results found

Manual Install and Customize NMS and NMC

In document 1350OMS_IG_9 6 11HPUX (Page 95-104)

2 INSTALL AND CUSTOMIZE 1350OMS

2.4 Install and Customize Alcatel-Lucent Software

2.4.2 Manual Install and Customize NMS and NMC

2.4.2.1 Manual Install and Customize 1350OMS-MW-INT

The Alcatel-Lucent 1350OMS-MW-INT is the operational platform, so it must be the first software installed. To install 1350OMS-MW-INT “Install.sh" procedure requires:

The depot machine is available, and the local system is correctly authorized to access the files (see 2.2.2.2 at page 58 for more informations).

• The installing system must be authorized to retrieve the files from itself or from depot machine. • When depot machine is used: The hostname of the depot machine correctly defined in the /etc/

hosts file.

N.B. In order to prevent error messages during the 1350OMS-MW-INT customize it is advis- able to configure the GoGlobal-UX license as shown in “1350 Administration Guide" [2]. GoGlobal-UX will be stopped by 1350OMS-MW-INT configuration script. DO NOT start the Install.sh with 1350OMS-MW-INT option from any window open via GoGlobal-UX, because all the GoGlobal-UX windows will be closed, and the configuration aborted! If the mentioned requirement are matched, the installation and custom can be started by entering:

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

1) Start the installation script entering:

...,sys,root# ./Install.sh MW-INT <hostname> <directory> [Enter]

Where:

<hostname> means the depot machine hostname

<directory>means directory path on depot machine where depot is located. (usually /alu/DEPOT)

The script start issuing the following mask:

########## ################# ################ ## ########### ## ### ########### ## ### ## ########## ### ###### ## ########## #### ####### ## ######### #### ######### ## ######## ##### ############## ####### #### ############### ###### ##### ############### ##### ###### ############### ##### ####### ############### ############## ############### ############# ###### ######## ############ #### ######## ########## ####### ######### #########

__ _ ___ __ ____ ___ _ _ _ _ __ ___ _ _ ____ / | || / _| / | |_ _| |___| || || || || / _| |___| | \| | |_ _| //|| || || //|| || ||_ || __ || || || || ||_ | \| | || // || || || // || || | _| |||__||| || || || | _| ||\ | || // || ||_ ||_ // || || ||__ ||_ ||_ ||_|| ||_ ||__ || \ | || / || |__| \__| // || || |___| |__| |__| \___/ \__| |___| || \| || Installation MW-INT package

=========================================================================== LOADING:

###################################################################### NOTE: Session started on: Fri Nov 30 17:22:25 MET 2007

NOTE: Set HP-UX environment ...

NOTE: Setting language to: C.iso88591 ... NOTE: Hardware 9000/800 supported ... NOTE: Check installation ongoing ...

NOTE: Please enter the Device Name of source media [c0t0d0]: Confirm or change the suggested source media.

NOTE: Preparing to install ...

NOTE: Check pkg INSTALLER_7.1.4.11.tar ... NOTE: Preparing to INSTALLER 7.1.4.11 ...

=========================================================================== The installation is executed by INSTALLER that shows you the contents of the package :

=========================================================================== Installation MW-INT package

=========================================================================== *************************************************************************** NOTE: rm -rf /home/*/.WebEnabler

NOTE: 11/30/07 17:22:33 - Executing MW-INT pre_install_wa ... NOTE: 11/30/07 17:22:33 - MW-INT pre_install_wa completed ... ....

The installation start automatically, this step will take up to 20 minutes.

The last question is related to the MW-INT custom; you have to reply also this question with “y[Enter]" Do you want to execute MW-INT Custom? [y|n|q] y [Enter]

Then the MW-INT custom will be executed showing the trace on the terminal.

******************************************************************* NOTE: ${INSTALL_ROOT}/Kernel/script/KernelCustomize

NOTE: 12/01/07 08:07:48 - Executing MW-INT custom_cmd ... .

.

NOTE: Kernel Customization Complete. NOTE: Reapplying PLT registrations.

The procedure will stop after up to 10 minutes, asking you to authorize the Go-Global UX environment shutdown. Ask all users logged in with Go-Global UX to log out the system.

GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no) Reply the question with “yes[Enter]" to allow Go-Global UX custom, and then the procedure will be com- pleted in a couple of minutes issuing:

======================================================================= NOTE: Session finished on: Sat Dec 1 08:16:58 2007

NOTE: Installation MW-INT completed successfully.

The MW-INT installation and custom is now completed, before continue installation it is advisable to check for any error that may have occurred by check the contents of the following file:

/alu/Install_Wizard/log/Installation_MW-INT_*.log

N.B. If you doesn't have already configure the GoGlobal License server, it could be displayed an error message.

2.4.2.2 Install and Customize NMS and NMC

This section explains how to install and customize a Network Management Subsystem and/or Network Management Component.

N.B. Very important: For the first installation it is mandatory to install the NMC software before cus- tomize NMS instance.

2.4.2.2.1 Install NMS or NMC

This paragraph shows how to install the Alcatel-Lucent TNM software optimizing the time need to adapt it to this specific environment. To be able to curry out this section the following items are required:

• A depot machine available.

• The installing system must be authorized to retrieve the files from itself or from the depot machine.

• When depot machine is used: The hostname of the depot machine correctly defined in the /etc/ hosts file.

• You have to be able to login the system via GUI, in case of HP server the GoGlobal-UX have to be authorized with the license code.

Then you can proceed with NMS and/or NMC as summarized hereafter: a) Install all software on the system.

b) Customize all NMS.

Then complete the installation and custom with integrating the systems among themselves. 2.4.2.2.1.1 NMS or NMC Installation Procedure

If the mentioned requirement are matched, the installation and custom can be started by entering: a) Login the system via Graphical User interface CDE as “root" user.

N.B. IF THE INSTALLATION SCRIPT IS STARTED FROM A SHELL WITHOUT A USEFUL DISPLAY VARIABLE SET THE NMS CUSTOM WILL FAIL.

b) Open a dtterm window.

c) Entering the following commands at dtterm prompt:

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

...,sys,root# ./Install.sh -install <NMS/NMC name> <hostname> <directory>[Enter]

Where:

<NMS/NMC name> NMS or NMC name (including ETH-MEDIATOR). <hostname> means the depot machine hostname

<directory> means directory path on depot machine where depot is located. (usually /alu/DEPOT)

N.B. To allow the recovery of errors it is possible to start “install.sh" with option “-confirm", the option causes the issues of confirm request message before execute each step in the installation and configuration. Replying “no" to these questions you can skip the step.The script start issuing the Alcatel-Lucent mask, then it will ask you some questions.

########## ################# ################ ## ########### ## ### ########### ## ### ## ########## ### ###### ## ########## #### ####### ## ######### #### ######### ## ######## ##### ############## ####### #### ############### ###### ##### ############### ##### ###### ############### ##### ####### ############### ############## ############### ############# ###### ######## ############ #### ######## ########## ####### ######### ######### ################# ########## __ _ ___ __ ____ ___ _ _ _ _ __ ___ _ _ ____ / | || / _| / | |_ _| |___| || || || || / _| |___| | \| | |_ _| //|| || || //|| || ||_ || __ || || || || ||_ | \| | || // || || || // || || | _| |||__||| || || || | _| ||\ | || // || ||_ ||_ // || || ||__ ||_ ||_ ||_|| ||_ ||__ || \ | || / || |__| \__| // || || |___| |__| |__| \___/ \__| |___| || \| || Installing <NMS/NMC name> package

=========================================================================== --- NOTE: Preparing to install ...

.

The output depends by the chosen NMS or NMC

. .

If you had started “Install.sh" with -confirm option, you have to confirm by entering “y [Enter]" The time spent for installation of package depends by NMS.

2.4.2.2.2 Customize NMS

Meaningful for NMS Only

Now customize the NMS instances created in the system predisposal. It is not necessary to customize the NMC because them are automatically performed together NMS.

For each NMS instance execute the following command procedure:

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

...,sys,root# ./Install.sh -custom <NMS name> [Enter]

Where: <NMS name> has to be replaced by NMS name to be customized. ########## ################# ################ ## ########### ## ### ########### ## ### ## ########## ### ###### ## ########## #### ####### ## ######### #### ######### ## ######## ##### ############## ####### #### ############### ###### ##### ############### ##### ###### ############### ##### ####### ############### ############## ############### ############# ###### ######## ############ #### ######## ########## ####### ######### ######### ################# ########## __ _ ___ __ ____ ___ _ _ _ _ __ ___ _ _ ____ / | || / _| / | |_ _| |___| || || || || / _| |___| | \| | |_ _| //|| || || //|| || ||_ || __ || || || || ||_ | \| | || // || || || // || || | _| |||__||| || || || | _| ||\ | || // || ||_ ||_ // || || ||__ ||_ ||_ ||_|| ||_ ||__ || \ | || / || |__| \__| // || || |___| |__| |__| \___/ \__| |___| || \| || Customization <NMS/NMC name> package

========================================================================== LOADING: ################################################################ ...

NOTE: Check processes running ...

========================================================================= Customization <NMS/NMC name> package

========================================================================= NOTE: Do you want to execute <NMS/NMC name> Custom? [y|n|q]

The “System, Instances List" window will be shown on the screen after a few seconds, it allows you to select the instance that you want customize:

Figure 12. List of existing instances

Select “Choose_one" and then “New-Instance" , then select “Apply & exit" in the Actions menu.

Then custom “Parameters Definition" window will be shown on the screen after a few seconds, it allows you to set the relevant custom variables.

In case of EML, the “Custom Product Selection EML <Instance Id>" window will be shown on the screen after a few seconds.

Figure 14. NMS Customize Window Select in the list the Network Element family you want to configure:

N.B. When customizing a Client instance be sure to select all the NE selected on the Master Instance.

Then pull-down the menu “Action" (in the left upper corner), select “Apply & exit" to start the custom pro- cedure.

A trace window will be open on the screen showing the customization progress.

Figure 15. NMS Customize trace window The procedure will complete when the [Dismiss] button will be enabled. Warning message, if displayed during EML customization, can be ignored.

The NMS installation and customization is now completed, before continue installation it is advisable to check for any error that may have occurred by check the contents of the following file:

In document 1350OMS_IG_9 6 11HPUX (Page 95-104)