Some NMS require some more action after the install and custom execution, hereafter the detailed description divided by NMS.
2.6.1 Special Instruction for SDH, NPR
2.6.2 Special Instruction for HA
On 1350OMS systems with HA installed or planned in the future, LDAP DB must be distributed. Start replication fails the first time the action is launched after HA bench installation, then repeat start rep- lication, the second time it works correctly.
2.6.2.1 1350OMS-HA Specific Instructions
The 1350OMS-HA NMC installation on board of an existing NMS does not involve only the system itself, but it requires to operate on many machine, including the spare system that are specifically requested in addition.
First of all you have to draw a clear picture of starting and final configurations. Just to better understand the sequence of activity we can considering a common network management configuration shown in Fig- ure 16.
hosta SDH Client EML Client
SDH Master EML Master
EML Client
hostb hostc
Figure 16. Add 1350OMS-HA Starting configuration Example
The figure shows three machines working together, whit the client-master relationship shown by the arrows.
To be able to install and configure the 1350OMS-HA you have to identify the machine that has to be sub- jected to high availability protection, them will be defined as “Network Operation Center" (in the example hostb and hostc), and presentation machines that do not require protection.
Starting from the network management shown in Figure 16. the suggested 1350OMS-HA configuration is shown by Figure 17. The picture distinguishes among “Network Operation Center", “Disaster Recovery Center", and machine that do not belong to them (presentation machines). The white arrows shows the client-master relationship when the NOC is operational, the striped ones when the DRC takes the control.
hosta SDH Client EML Client 1350 OMS- HA SDH Master EML Master EML Client hostb hostc 1350 OMS- HA 135 0OMS-HA SDH Master EML Master EML Client hostb1 hostc1 135 0OMS-HA
Network Operation Centre Disaster Recovery Centre
1350
OMS-
HA
Figure 17. Add 1350OMS-HA Final configuration Example
2.6.2.1.1 How to install 1350OMS-HA
This paragraph provides the guidelines for installing 1350OMS-HA on an existing TMN system referring the previous example.
a) Operate on DRC Machines:
1) Install and customize new DRC machines (hostb1 and hostc1) with the same configuration of the related companions adding the 1350OMS-HA function referring the installation chapter of this document, operating like a new fresh installation.
b) Operate on NOC Machines, on each system proceed this way:
1) Login the system as TMN administrator (alcatel user), and shut down the applications. 2) Predispose the system for 1350OMS-HA SWP and create a 1350OMS-HA IM instance for each
local NMS IM instance subjected to resilience protection, and 1350OMS-HA US instance for each client referring a resilient IM.
3) Install 1350OMS-HA following the instruction shown by paragraph 2.4.2.2.1 “Install NMS or NMC" at page 96.
4) Execute any foreseen pre-customization actions for 1350OMS-HA following the instruction of paragraph “Customize NMS" 2.4.2.2.2 at page 98, with the exception that you have to reply “no[Enter]" at the custom execution question:
NOTE: Do you want to execute <NMS/NMC name> Custom? [y|n|q] 5) Depending by the NMS/NMC instance type present on the machine, execute the procedure
described in one of the following paragraphs:
Customize and Configure 1350OMS-HA in distributed configuration. Customize and Configure 1350OMS-HA in cohosted configuration.
Customize and Configure 1350OMS-HA in Presentation only configuration. 2.6.2.1.2 Customize and Configure 1350OMS-HA in distributed configuration.
This paragraph is applicable to Alcatel-Lucent TMN system where there is just one NMS Master installed on the system or and PKT cohosted.
For each NMS Master subjected to resilience protection:
1) Update instance data description including 1350OMS-HA by entering:
...,sys,root # /alu/Kernel/script/updateInstance.pl \[Enter]
-sys <NMS_SYSTEM> -inst <NMS_INSTANCE> -type NMC \[Enter] -comp HA -skipconfig[Enter]
2) Configure 1350OMS-HA subsystem in the scope of instance process configuration for each NMS IM subjected to resilience protection (refer to “1350OMS-HA Administration Guide" for more information).
2.6.2.1.3 Customize and Configure 1350OMS-HA in cohosted configuration.
This paragraph is applicable to Alcatel-Lucent TMN system where:
– A EML Master is installed with one of the following NMS Master: SDH, or PKT – A SDH Master is installed with one of the following NMS Master: or PKT
a) For each PKT Master subjected to resilience protection, execute the procedure described at para- graph 2.6.2.1.2 “Customize and Configure 1350OMS-HA in distributed configuration" .
b) For each SDH Master subjected to resilience protection, when there is no PKT Master cohosted, execute the procedure described at paragraph 2.6.2.1.2 “Customize and Configure 1350OMS-HA in distributed configuration" .
c) For each SDH Master subjected to resilience protection, when any PKT Master is cohosted, execute the following procedure:
1) Create an additional SDH Client instance file system as shown at paragraph 2.2.8.1 “Manage NMS Master-Client cohosted“ at page 81.
2) Customize again the SDH specifying “Master-Client" as “System_Instance_Rule" (see 2.4.2.2.2 at page 98 for more information).
3) Create an additional PKT Client instance file system as shown at paragraph 2.2.8.1 “Manage NMS Master-Client cohosted“ at page 81.
d) For each EML Master subjected to resilience protection, when any NMS Master is cohosted, execute the following procedure:
1) Create an additional EML Client instance file system as shown at paragraph 2.2.8.1 “Manage NMS Master-Client cohosted“ at page 81.
2) Customize again the EML specifying “Master-Client" as “System_Instance_Rule" (see at 2.4.2.2.2 page 98 for more information).
3) Configure 1350OMS-HA subsystem in the scope of instance process configuration for each NMS IM subjected to resilience protection (refer to “1350OMS-HA Administration Guide" for more information).
2.6.2.1.4 Customize and Configure 1350OMS-HA in Presentation only configuration.
This paragraph is applicable to Alcatel-Lucent TMN system where there is only NMS Client installed.
For each NMS Client referring a NMS Master subjected to resilience protection: 1) Update instance data description including 1350OMS-HA by entering:
...,sys,root # /alu/Kernel/script/updateInstance.pl \ [Enter]
-sys <NMS_SYSTEM> -inst <NMS_INSTANCE> -type NMC \ [Enter] -comp HA -skipconfig [Enter]
2) Configure the 1350OMS-HA within the NMS instance by entering:
...,sys,root # /usr/Systems/<NMS_INSTANCE>_Presentation/HA/etc/OSResSystemConfig [Enter] Where:
<NMS Instance >has to be replace with the NMS instance root directory, that is defined by the following information:
<NMS Name>_<NMS Instance ID>-<NMS Version> Where:
<NMS Name> means the NMS name (example: EML). <NMS Instance ID>means the instance ID number. <NMS Version>means the NMS version (example: 9.6) Example: