2 INSTALL AND CUSTOMIZE 1350OMS
2.2 Software Package Predispose
2.2.7 Predispose for Installation
Now you have to predispose in one shot the entire system, that means you must know which system con- figuration you have to create, in term of software and data. Because there are some possible Alcatel- Lucent NMS/NMC combinations, it is advisable to identify the software and the data instances you have to predispose for before starting.
The 1350OMS-MW-INT modular approach allows to predispose the machine after the hp-ux Operating System installation, this is performed on demand by a specific script. In this paragraph will be shown: how to predispose the system to be able to run 1350OMS-MW-INT, because it has to be always installed. Then it will be provided an example of EML, and a generic example for all the other NMS.
2.2.7.1 Start the SWP Manager Script
To be able to start the Software Package predispose script you have to login as root user and enter the command:
...,sys,root # scmanageswp [Enter]
N.B. VERY IMPORTANT: The whole installation has been described as a single predispose action. This means you have to predispose all the NMS and NMS instances in one shot. This allows to save time and to do not meet problems in disk space computation. If you have to interrupt the predisposal in the middle of the selection, exit the procedure choosing “Exit" to abort the procedure itself.
The following menu` will be shown on the screen:
--- SWP MAIN MENU --- 1 - Predispose new SWP
2 - View predisposed and manage SWP 3 - Remove SWP
4 - Create new SWP INSTANCE
5 - View created and manage SWP INSTANCE 6 - Remove SWP INSTANCE
7 - Convert SWP INSTANCE
8 - Install 3PP Optional software a - Apply
e - Exit
Insert choice and press [Enter]: 1
Select option 1 in order to predispose for a new SWP installation. First of all you have to predispose for the MW_INT.
2.2.7.2 Predispose for 1350OMS-MW-INT
First of all you have to predispose the system for 1350OMS-MW-INT, in fact it has always to be installed as first. The SWP description defined on system will be shown.
Predispose new SWP
Item SWP Name SWP Version ---- --- --- 1 EML 9.6 2 EOMS 9.6 3 HA 9.6 4 MW_INT 9.6 5 NPR 9.6 6 PKT 9.6 7 SDH 9.6 8 WDM 9.6
Enter 'q' to Quit, 'd' to Display again or the Item Number : [Enter] Enter the MW_INT item number to select it for the predisposition. The procedure will ask you to confirm the choice.
Selected SWP 'MW_INT 9.6'
Please confirm your selection ? (y/n) Confirm by entering: y [Enter]
All the layered software selected to the SWP predisposal will be shown: TRANSLATOR procedure activated ...
Product Name Product Version Analysing Product Alcatel-OVDL 2.1
Analysing Product Apache2 B.2.2 ...
Analysing Product GoGlobal-UX 2.2 Analysing Product IlogViews50 5.0 ...
...
Analysing Product unzip 5.52 TRANSLATOR procedure was successful.
Press [Enter] to continue.
The 1350OMS-MW-INT is now stored for the predisposal that will be done leaving the script.
Drive back the “scmanageswp" tool to the “SWP MAIN MENU" entering “q “ to predispose for Global Instance
2.2.7.3 Predispose for 1350OMS-MW-INT Global Instance
At “SWP MAIN MENU" enter “4" to select “Create new SWP INSTANCE". The following menu will be shown:
Create new INSTANCE
Item SWP Name SWP Version Session ---- --- --- --- 1 MW_INT 9.6 NEW
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Enter “1[Enter]" to select the 1350OMS-MW-INT, and the possible instance will be shown with: List of available INSTANCE dimension for SWP: MW_INT 9.6
Item INSTANCE Dimension INSTANCE Description ---- --- --- 1 MWINT 1350OMS-MW-INT 8.2 Global Instance
Enter 'q' to Quit, 'd' to Display again or the Item Number : Enter “1 [Enter]" to select MWINT Global Instance.
Then the tool will ask you to:
Insert the Instance Number for 'MWINT' Enter “1 [Enter]".
Do you like a Multi-Volume group configuration ? (y/n) Reply with “n [Enter]".
Then the selection will be shown: Selected INSTANCE: Dimension MWINT Number 1 Multi-Volume NO
Please confirm your selection ? (y/n) Confirm or refuse the selection.
If you confirm the procedure will predispose for the installation of the required software: TRANSLATOR procedure activated ...
Note: There aren't kernel parameters defined. Note: There aren't additional components defined. TRANSLATOR procedure was successful.
2.2.7.4 Predispose for EML
This section describes the EML predisposal, it is provided to better clarify the procedure behavior, but you have to execute it only if you need the EML functionality, otherwise go to next paragraph “Predispose for NMS" 2.2.7.5 at page 70.
2.2.7.4.1 Predispose for EML Software
EML subsystems is organized in two components: the software code and instance. You have to predis- pose the software code once, but you can create one or more instances. Because of this there are two different actions, where the second can be iterated more than once.
Proceeding in the script execution, after the 1350OMS-MW-INT predisposal the script prompt you again for choosing the next software package, you have in any case to install something of EML, so enter: 1 [Enter] to predispose new SWP, the SWP description defined on system will be shown again:
Predispose new SWP
Item SWP Name SWP Version ---- --- --- 1 EML 9.6 2 HA 9.6 3 NPR 9.6 4 PKT 9.6 5 SDH 9.6 6 WDM 9.6
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Enter the EML item number to procede, the selected product is shown to check the right choice: Selected SWP 'EML 9.6'
Please confirm your selection ? (y/n)
After the confirm action the procedure analyzes the description showing all the software layers required: Product Name Product Version Analysing Product Alcatel-OVDL 2.1 Analysing Product Ant 1.7 Analysing Product Commons 0.0
. . .
Analysing Product xercesj 2.7 TRANSLATOR procedure was successful.
Press [Enter] to continue.
Press [Enter] to proceed, then, exit to the Software predisposal by entering “q[Enter]" to came back to the “SWP MAIN MENU" and be able to create the instance.
2.2.7.4.2 Predispose for EML Instance
The EML Instance define the behavior of the application, you have three possibilities:
1) Predispose for a EML Information Manager (IM), if you want to install a EML stand alone or SDH cohosted system.
2) Predispose for a EML Spare IM, if you are installing the spare system in a 1350OMS-HA con- figuration.
3) Predispose for a EML Client, if you just want to have the EML Presentation function on any other NMS. In this case you have to create an instance for each EML IM and the Instance Identifi- cation number must be the same of the referred IM.
Hereafter the sequence of actions you have to perform to carry out the job.
At “SWP MAIN MENU" prompt you have to enter “4" to get in the “Create new SWP INSTANCE": --- SWP MAIN MENU ---
1 - Predispose new SWP
2 - View predisposed and managed SWP 4 - Create new SWP INSTANCE
5 - View created and managed SWP INSTANCE 8 - Install 3PP Optional software
a - Apply e - Exit
Insert choice and press [Enter]: 4 [Enter]
The already predisposed NMS will be shown in a list, enter the item of EML: Create new INSTANCE
Item SWP Name SWP Version Session ---- --- --- --- 1 EML 9.6 NEW 2 MW_INT 9.6 NEW
Enter 'q' to Quit, 'd' to Display again or the Item Number : 1 [Enter] The list of the EML possible instances foreseen for the specific machine model is provided.
List of available INSTANCE dimension for SWP: EML 9.6 Item INSTANCE Dimension INSTANCE Description
--- --- --- 1 EML_IM_Small EML Master (IM) System Small Configuration
2 EML_IM_Medium EML Master (IM) System Medium Configuration 3 EML_IM_Large EML Master (IM) System Large Configuration 4 EML_US EML Client (US) Enter 'q' to Quit, 'd' to Display again or the Item Number :
Before entering the instance item number for the selection, read carefully the meaningful of each item in the following table:
Table 6. EML Instances
Instance type item Description
EML_IM_Small Entry level configuration EML_IM_Medium Middle range configuration EML_IM_Large High end configuration
EML_US EML Client (US)
N.B. The EML_US instance is not defined for 1350OMS-HA protection Then define the instance identifier:
Insert the Instance Number for 'EML_IM_Small':
The multiple volume group is not foreseen for 1350OMS 9.6, so reply “n” to the following question: Do you like a Multi-Volume group configuration ? (y/n)
After the volume group configuration, the procedure summarize the information asking you to confirm your choice:
Selected INSTANCE:
Dimension EML_IM_Small Number 3
Multi-Volume NO
Please confirm your selection ? (y/n) Confirm or refuse the selection.
If you confirm the procedure will predispose for the installation of the required software: TRANSLATOR procedure activated ...
Note: the volume group defined in the "EML 9.6" descriptor will not take in account, because multi_volume_group option is not set.
Volume group vg00 will be used for mount point: /usr/Systems/EML_3_9.6_Master Note: the volume group defined in the "EML 9.6" descriptor will not take in account, because multi_volume_group option is not set.
Volume group vg00 will be used for mount point: /usr/Systems/EML_3_9.6_Master/ maintenance
Product Name Product Version Analysing Product DBD-MySQL 2.1026
Analysing Product DBD-MySQL 3.0004
Analysing Product DBD-Oracle580 1.17 Analysing Product DBD-Oracle588 1.17 Analysing Product DBI-1.32 1.32 Analysing Product MySQL 5.1
Analysing Product Oracle10g_Client 1.0 Analysing Product Oracle10g 11.2.0
OPTIONAL Product: Oracle11g
Product Description: Oracle 11g (Version 11.2.0.2 + Patches) for HP-UX 11.31 ia64 64Bit
Do you like to install it ? (y/n)
Reply “y” only if you have to configure in your system SNA or TNA elements. Remember: in this case, you must have ORACLE license.
N.B. In the future will be determined whether, how and when, to install one, the other or both. Analysing Product Snmp4j 1.11 Analysing Product Snmp4j 1.7 Analysing Product Snmp4j 1.9 Analysing Product jsch 0.1 Analysing Product jta 2.6 TRANSLATOR procedure was successful.
Press [Enter] to continue.
If you have to create more than one instance, enter the item number of the menu that corresponds to the type you want to create, enter the instance number and multiple volume option. Otherwise enter “q [Enter]" twice to go back to the previous menu level.
2.2.7.5 Predispose for other NMS/NMC
Any other NMS predisposal has a similar behavior, the only differences are related to the possible instances available. This activity has to be performed only if you plan to have any other functionality on the machine you are installing.
NMS has the same organization of EML, software code and data areas; hereafter the predisposal script behavior is shown.
Do NOT predispose SDH and NPR altogether on the same machine (SDH includes all NPR functionalities). NPR must be installed only when/if SDH is not installed.
2.2.7.5.1 Predispose for NMS Software
In both cases, if you have to start “scmanageswp" or proceeding from the EML predisposal, you have the “SWP MAIN MENU" on the screen, enter: 1 [Enter] to get on the next menu:
--- SWP MAIN MENU --- 1 - Predispose new SWP
2 - View predisposed and managed SWP 4 - Create new SWP INSTANCE
5 - View created and managed SWP INSTANCE 8 - Install 3PP Optional software
a - Apply e - Exit
Insert choice and press [Enter]: 1 [Enter] The remaining NMS descriptions will be shown.
Predispose new SWP
Item SWP Name SWP Version ---- --- --- 1 HA 9.6 2 NPR 9.6 3 PKT 9.6 4 SDH 9.6 5 WDM 9.6
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Select a NMS of 1350OMS 9.6.11 you want to predispose among: HA 9.6, PTK 9.6, SDH 9.6, NPR 9.6 (remember do NOT predispose SDH and NPR together), WDM 9.6.
Enter the item number shown in the first column of the menu, then press [Enter] :
Then it asks you to confirm your choice, by showing you the selected NMS, enter “y [Enter]" if it is correct: Selected SWP '<NMS name>'
The procedure start the description analysis issuing the following messages: TRANSLATOR procedure activated ...
.
The output depends by the chosen NMS
.
TRANSLATOR procedure was successful. Press [Enter] to continue.
Press [Enter] to proceed, then, exit from the Software predisposal by entering “q [Enter]" twice to come back to the “SWP MAIN MENU" and be able to create the instance:
Predispose new SWP
Item SWP Name SWP Version ---- --- ---
.
The output depends by the chosen NMS
.
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Choose any other NMS you have to predispose, or enter “q [Enter]" to complete the NMS software selec- tion. Enter “q [Enter]" again to go to the SWP MAIN MENU.
2.2.7.5.2 Create NMS Instance
This paragraph shows how to create a NMS instance for the specific data storage.
Create the NMS Instances, taking also into account the functional dependencies shown in paragraphs 1.2.7 and 1.2.8 at page 24-25.
--- SWP MAIN MENU --- 1 - Predispose new SWP
2 - View predisposed and managed SWP 4 - Create new SWP INSTANCE
5 - View created and managed SWP INSTANCE 8 - Install 3PP Optional software
a - Apply e - Exit
The installed software list is shown, you have to choose the item related to the NMS you has predisposed in the previous step (2 in the example):
Create new INSTANCE
Item SWP Name SWP Version Session ---- --- --- 1 EML 9.6 YES 2 <NMS name> <NMS version> YES 3 MW_INT 9.6 YES
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Select the item corresponding to the instance you want to create, enter it followed by [Enter]. The list of allowed instances for that NMS will be shown.
For system with HA you have to predispose a HA instance for each NMS subjected to protection. More- over the HA instance number must be assigned, by the following rules:
HA_IM Instance Number >= NMS Master Instance Number HA_US Instance Number >= NMS Presentation Instance Number
The procedure will ask you for two information: the instance number identifier and the multiple volume group.
N.B. The instance identifier have to be defined in a plan, and be unique for the Master instances in the whole network.
N.B. The instance number must be equal between Master-Spare systems. N.B. Remember the instance number, because it has to be entered again later.
N.B. For NMS Cohosted with 1350OMS-HA, create the client file system for the NMS lower lay- ers (refer to “Network Management Sub-Systems Functional Dependencies" paragraph 1.2.7 at page 24 for architecture, and to “1350OMS-HA Post Predisposal" paragraph 2.2.8 page 80 for more information).
Due of a restriction of the NMS PKT, instances of NMS SDH and WDM CAN NOT BE DEFINED with the same identification number. Although it is not expected to be installed PKT, it is strictly advised not to award the SDH and WDM applications the same identifier.
Enter the instance number followed by [Enter] to proceed:
Insert the Instance Number for '<NMS Instance Type>': Do you like a Multi-Volume group configuration ? (y/n)
After the volume group configuration, the procedure summarize the information asking you to confirm your choice:
Selected INSTANCE:
Dimension <NMS Instance Type> Number <NMS Instance Identifier> Multi-Volume <NMS Instance rule> Please confirm your selection ? (y/n)
Confirm or refute the selection. If you confirm the procedure will predispose for the installation of the even- tual required software:
TRANSLATOR procedure activated ... .
The output depends by the chosen NMS
.
TRANSLATOR procedure was successful. Press [Enter] to continue.
The procedure shows again the list of possible instance for the next choice, enter “q [Enter]" to go back to the previous menu level.
List of available INSTANCE dimension for SWP: <NMS name> 9.6 Item INSTANCE Dimension INSTANCE Description ---- --- --- ....
Enter 'q' to Quit, 'd' to Display again or the Item Number : q [Enter] Enter “q [Enter]" again to go back to SWP MAIN MENU.
2.2.7.6 Leave the Script and Execute the predisposal
To speed-up the predisposal execution and reduce the disk fragmentation, the predisposal is executed when leaving the script. To execute the predisposal for all the software you have to exit the “SWP MAIN MENU" by entering “a[Enter]":
--- SWP MAIN MENU --- 1 - Predispose new SWP
2 - View predisposed and managed SWP 4 - Create new SWP INSTANCE
5 - View created and managed SWP INSTANCE 8 - Install 3PP Optional software
a - Apply e - Exit
Insert choice and press [Enter]: a [Enter] The list of the pending action will be shown:
Items SELECTED for the CONFIGURATION
Item Type SWP Name SWP Version INSTANCE Number INSTANCE Dimension Opt --- --- --- --- --- --- SWP MW_INT 9.6
INSTANCE MW_INT 9.6 1 MWINT
SWP <NMS name> <NMS ver.> INSTANCE <NMS name> <NMS ver.> 1 <NMS name>_IM_Small Enter 'a' to Apply, 'c' to Cancel or 'd' to Display again:
Confirm your choice by entering “a[Enter]" (as apply) or cancel. Then procedure start executing the requested predispositions.
2.2.7.6.1 Software Layer Installation Predisposal
Before start the procedure will ask you where to find all the software packages, by issuing the following message:
SOFTWARE 3PP predisposition activated ...
Now you have to specify where are stored the LAYERED PRODUCTS. Press [Enter] to continue.
--- LAYERED PRODUCTS Repository --- 1 - CD-ROM or DVD media
2 - Software Depot 3 - ISO Image Directory q - quit
2.2.7.6.1.1 Software Layer Installation Predisposal from media Here the DVD choice is shown, enter “1 [Enter]"
--- Device selection for LAYERED Products installation ---- Enter 'q' to Quit or the CD device [def=/dev/dsk/cxtxdx]: The procedure requires you to specify the driver. Press enter to default. 2.2.7.6.1.2 Software Layer Installation Predisposal from Depot Here the network depot choice is shown, enter “2 [Enter]"
--- Depot selection for LAYERED Products installation ---- Enter 'q' to Quit or the Depot absolute path name:
The procedure requires you to specify the depot, enter: <depot hostname>:/alu/SCDEPOT [Enter]
Where you have to replace “<depot hostname>" with the name of the depot machine (see at paragraph ”Create Software Depots” 2.2.2.1 at page 57)
2.2.7.6.1.3 Software Layer Installation Predisposal from ISO Image Directory Here the ISO Image choice is shown, enter “3 [Enter]"
--- ISO image directory selection for LAYERED Products installation ---- Enter 'q' to Quit or the Directory absolute path name:
The procedure requires you to specify the Directory. 2.2.7.6.2 Disk Configuration
Now the procedure check the space available inside the existing file systems and creates the new requested ones. The entire activity is carried out automatically, but not unattended. In fact there are two cases where the operator attention is required.
– File system busy – New hard disk allocation
2.2.7.6.2.1 File system Busy
The operator attention is required when predispose requires a file system extension and there are one or more open files in it. In this case the file system is busy, and the extension it is not allowed. A message like the following is issued.
___________________________________________________________________________ Analyze Mount Point:"/opt"
Request free: 1072 MegaByte(s) Current size: 1536 MegaByte(s) Current used: 512 MegaByte(s) Current free: 960 MegaByte(s) Evaluate size: 1792 MegaByte(s)
File System:"/dev/vg00/lvol5" is busy, check process with pid(s): 1780 2070 1366 1758 1785 2069 2059 2067 2052 2096 3719
When such a message occurs during the predispose, replay with "R[Enter]" to postpone the file system extension to the next reboot.
Press:
[T] = Try again (but after you have attempt to close all pid(s) ) [A] = Abort (DANGEROUS - operation is aborted)
[R] = Reboot (RECOMMENDED - operation will be completed after next reboot) then press [Enter]
2.2.7.6.3 Kernel Configuration
The next execution phase regards the HP-UXTM Kernel configuration. The kernel resources have to be
increased to allow the machine to run the application. This phase does not require any human intervention.
KERNEL configuration activated ...
WARNING: FORCE operator defined for variable 'filecache_max' removing oth- ers operators.
Creating new kernel configuration ... ....
.... ....
KERNEL configuration was successful.
Don’t worry if the system shows error message like following, on condition that the configurations ends with success:
ERROR: The requested changes could not be applied to the currently running system, for the following reasons:
- The tunable 'ksi_send_max' cannot be changed without a reboot. - The tunable 'semmns' cannot be changed without a reboot. * The configuration 'sck_new' has been marked for use at next boot.
2.2.7.6.3.1 New Hard Disk Allocation
During the file system extension it may occur that the initial disk configuration it is not enough to store the