9153 OMC-R Installation PDF

Alcatel-Lucent GSM
9153 OMC-R Installation
OMC Document
Installation & Dismantling Document
Release B11
3BK 17438 4011 RJZZA Ed.09

BLANK PAGE BREAK
Status RELEASED
Short title Commissioning Manual

All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel-Lucent.
2 / 64 3BK 17438 4011 RJZZA Ed.09

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Principles of the Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 Procedure Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.3 Sequence of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2.4 Necessary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.5 Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.6 Impact on Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.7 Supplies, Tools and Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2.8 Applicable Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1 PI01 9153 OMC-R Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.1 Operating System Installation for All Supported Machines Except M4000 . . . . 24
2.1.2 Operating System Installation for M4000/M3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.1.3 Install X.25, OSI and CMIP Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.1.4 Third Party and System Patches Installation (DVD2) . . . . . . . . . . . . . . . . . . . . . . . 38
2.1.5 Manual PROM Patches Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.1.6 Prepare X.25 Template for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.1.7 SAN Filesystem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.1.8 OMC3 Installation (DVD3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.1.9 Reboot the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.2 PI 02 Mandatory Customization Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.2.1 Parameters Customization on the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.2.2 OSI Interface Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.2.3 Setting the ID Range for the BSCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.2.4 X.25 Links Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.2.5 Reboot the Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.2.6 Install the License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.2.7 Setup Rights of “known_hosts” File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.2.8 SSH Key Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.2.9 Startup the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.2.10 Generic Documentation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.3 PI 03 Declaration of an 9153 OMC-R Machine in the 9153 OMC-R Network . . . . . . . . . . . . . 55
2.3.1 Declaration of the Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.3.2 Startup the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.4 PI 04 Optional Customization Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.1 Password Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.2 Remote Inventory Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.3 Q3 Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.4.4 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.4.5 Configuration of Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.6 Install NPO embedded/MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.4.7 Toolchain Related Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.4.8 Declaration of BSS/MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.4.9 Install Citrix XenApp (Presentation Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.4.10 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Appendix A : DVD1 Installation from Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3BK 17438 4011 RJZZA Ed.09 3 / 64

Tables
Tables
Table 1: Hardware classification and configurations supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2: OMC-R single-host hardware configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 3: OMC-R X-Large/XX-Large host hardware configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 4: The Scenario for the Installation of a Machine from CD-ROM/DVD-ROM . . . . . . . . . . . . . . . . . . . . . . 15
Table 5: PI’s for Machines to be Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 6: Needed Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 7: Schedule for 9153 OMC-R Machine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 8: Supplies at OMC-R Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 9: Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4 / 64 3BK 17438 4011 RJZZA Ed.09

Preface
Preface
Purpose This method describes the installation from scratch and customization of
B11 9153 OMC-R machines.
The OMC-R installation is performed from a local CD-ROM/DVD-ROM.
The following software is installed during the operations:
Solaris 10 operating system
Third party software and Solaris patches
ALMAP generic components

9153 OMC-R software.
This method covers the following types of 9153 OMC-R machines:

Master (XXLarge, XLarge, Large, Medium and Small)
Agent (XLarge, XXLarge)
HMI Server
Remote HMI Server
Document Pertinence This document applies to Release B11 OMC-R.
What’s New In Edition 09

The following sections were upated:
Supplies, Tools and Documentation (Section 1.2.7)
Install the License Files (Section 2.2.6)
Principles of the Operation (Section 1.1).
3BK 17438 4011 RJZZA Ed.09 5 / 64

Preface
In Edition 08
The following sections were upated:
Operating System Installation for All Supported Machines Except M4000

(Section 2.1.1)
DVD1 installation on M4000/M3000 (Section 2.1.2.5)
Third Party and System Patches Installation (DVD2) (Section 2.1.4)
OMC3 Installation (DVD3) (Section 2.1.8).
In Edition 07
The section Startup the Master (Section 2.2.9) was updated.
In Edition 06
Description improvement in Prerequisites (Section 2.1.2.1).
In Edition 05
The following sections were updated:
DVD1 installation on M4000/M3000 (Section 2.1.2.5)
Setup Rights of “known_hosts” File (Section 2.2.7)
In Edition 04
The following section were updated:
Startup the Master (Section 2.2.9)
SSH Key Synchronization (Section 2.2.8).
In Edition 03
The following sections were updated:
Principles of the Operation (Section 1.1)
Schedule (Section 1.2.5)
Scenario (Section 2)
Operating System Installation for M4000/M3000 (Section 2.1.2)
Prerequisites (Section 2.1.2.1)

SAN Filesystem Configuration (Section 2.1.7)
Startup the Master (Section 2.2.9)
In Edition 02
The following sections were improved:
PI01 9153 OMC-R Installation Tasks (Section 2.1)

SAN Filesystem Configuration (Section 2.1.7)
PI 02 Mandatory Customization Tasks (Section 2.2)
6 / 64 3BK 17438 4011 RJZZA Ed.09

Preface
PI 03 Declaration of an 9153 OMC-R Machine in the 9153 OMC-R Network

(Section 2.3).
Install Citrix XenApp (Presentation Server) (Section 2.4.9)
Backup (Section 2.4.10)

Principles of the Operation (Section 1.1)
In Edition 01
First official release of document in B11.
This document contains information about the following new features:
Centralized Licence Server and Time Validity for Optional Features

New SUN HW Platform for OMC-R
OMC-R Compatible with SAN Architecture in Scenario (Section 2)
3BK 17438 4011 RJZZA Ed.09 7 / 64

Preface
Audience This document is intended for:

Site administrators
Project managers
Field service technician
System support engineers (specialists)
Occasional users (e.g. subcontractors).
Assumed Knowledge You must have a basic understanding of the following:
Alcatel-Lucent operations and maintenance concepts for BSS

OMC-R operations
Unix operating system and Solaris system installation
Installation tools and materials.
8 / 64 3BK 17438 4011 RJZZA Ed.09

1 General Information
This chapter provides general information about the principle of the operations
and requirements for the procedure.
3BK 17438 4011 RJZZA Ed.09 9 / 64

1.1 Principles of the Operation

This method describes the installation and commissioning of 9153 OMC-R
platform.
The following types of machines exist in a 9153 OMC-R configuration:
Master
Agent
HMI Server (Remote HMI)
The number of the machines depends on the hardware configuration and the
capacity (in BSCeq) needed by the customer.
The following configurations are available:
Small
Medium
Large
XLarge
XXLarge
The Master host is present in all the configurations.

The Agent is present only in case of an XLarge and XXLarge configuration:
M4000 machines - one Agent is connected to the Master in case of

XLarge configuration and two Agents are connected to the Master in case
of XXLarge configuration.
Sun Fire V490 machines - one Agent is connected to the Master in case of
XLarge configuration and two Agents are connected to the Master in case
of XXLarge configuration.
Sun Fire V880 machines - one Agent is connected to the Master in

a XLarge configuration.
In a multiple host OMC-R configuration (XLarge or XXLarge), the Master and

Agent host servers must be the same hardware model. Mixing V880, V490 or
M4000 servers in a multiple host OMC-R configuration is not supported.
For HMI, the number and the type of the machine (small, standard, large)
depends of the configuration.
In case of SMALL and STANDARD configuration the Master Host based on SF

V880 (Sun Fire V880 with two processors provided with 4G of memory) is
not able to support the USM applications. The USM applications are allowed
only on the HMI hosts declared on the OMC-R.
10 / 64 3BK 17438 4011 RJZZA Ed.09

Master Host + Agent HMI Workstation
SFV880 SFV490 M4000 Sun Blade Ultra 25 M3000 U5 or Sun Blade Sun Ultra
(*) (**) 150 U10 100 or 150 25
SFV440
SF280R SUN Ultra
Netra 440
24
Sun Ultra
(*) : Starting from Large configuration, External Disk Bay SE3510 will be used. 27
(**) : Starting from Large Configuration, External Storage ST2540 will be used.
Table 1: Hardware classification and configurations supported
3BK 17438 4011 RJZZA Ed.09 11 / 64

OMC-R SUN Model Processor(s) RAM Disks SAN Minimum

config. Partitions
Requirements
Small SunFire V880 2x900 MHz 4 GB (or 6x73 GB /alcatel 67 GB

with or (or higher) more) internal disks
/alcatel/oracle 67 GB
without US III
NPOe
SunFire V490 2x1350 MHz 8 GB (or 2x146 GB /alcatel 96 GB
(or higher) more) internal disks
US IV
Sun Enterprise 2x2.4 GHz 8 GB 2x146GB /alcatel 100GB

M4000 Sparc64 VII internal disks
Standard SunFire V880 2x900 MHz 4 GB (or 6x73GB internal /alcatel 67GB
(or higher) more) disks
/alcatel/oracle 67GB
US III
SunFire V490 2x1350 MHz 8GB (or 2x146GB /alcatel 96GB

US IV
Sun Enterprise 2x2.4GHz 8GB 2x146GB /alcatel 100GB

Large-1 SunFire V880 6x900MHz 12GB (or 12x73GB /alcatel 135GB

and (or more) internal disks
/alcatel/oracle 202 GB
Large-2 8x750Mhz)
(or higher)
US III
SunFire V490 4x1350MHz 16GB (or 2x146GB /alcatel 140GB

(or higher) more) internal disks +
US IV 6 x 73GB EDB
SE3510 (*)
Sun Enterprise 2x2.4GHz 16GB 2x146GB /alcatel 204GB

+ 6x146GB
ST2540 2
Ctrl(**)
(*) : External Disk Bay SE3510 Fiber Channel with one HW RAID controller.
(**) : External Disk Bay ST2540 Fiber Channel with two HW RAID controllers.
Table 2: OMC-R single-host hardware configurations
12 / 64 3BK 17438 4011 RJZZA Ed.09

OMC-R SUN Model Processor(s) RAM Disks SAN Minimum

config. Partitions
Requirements
X-Large SunFire V880 8x900 MHz 16 GB (or 12x73 GB /alcatel 135 GB

Master (or higher) more) internal disks
/alcatel/oracle
US III
202GB

/alcatel/oracle
US IV + 12x73GB EDB
135GB
SE3510 (*)
Sun Enterprise 2x2.4 GHz 16 GB 2x146GB /alcatel 408 GB

+ 12x146GB
ST2540 2 Ctrl
(**)
X-Large SunFire V880 6x900MHz 12 GB (or 6x73 GB internal /alcatel 135 GB

Agent (or higher) more) disks
US III

US IV + 6x73GB EDB
SE3510 (*)
Sun Enterprise 2x2.4GHz 16 GB 2x146 GB /alcatel 204 GB

+ 6x146GB
ST2540 2 Ctrl
(**)
XX-Large SunFire V490 4x1350MHz 16 GB (or 2x146 GB /alcatel 135 GB

Master (or higher) more) internal disks
/alcatel/oracle
US IV + 12x73GB EDB
135GB
SE3510 (*)
Sun Enterprise 2x2.4GHz 16 GB 2x146 GB /alcatel 408 GB

+ 12x146GB
ST2540 2 Ctrl
(**)
XX-Large SunFire V490 4x1350MHz 16 GB (or 2x146 GB /alcatel 135 GB

Agent (or higher) more) internal disks
US IV + 6x73GB EDB
SE3510 (*)
Sun Enterprise 2x2.4GHz 16 GB 2x146GB internal /alcatel 204 GB

M4000 Sparc64 VII disks + 6x146GB
ST2540 2 Ctrl (**)
(*) : External Disk Bay SE3510 Fiber Channel with one HW RAID controller.
3BK 17438 4011 RJZZA Ed.09 13 / 64

(**) : External Disk Bay ST2540 Fiber Channel with two HW RAID controllers.
Table 3: OMC-R X-Large/XX-Large host hardware configurations
1.2 Procedure Information

1.2.1 Prerequisites
The following prerequisites apply:
Respect the safety rules. Refer to the applicable document [1] 9153 OMC-R
Methods Handbook.
Inform the operator. Ask for an operator’s representative to be on site.
SPS and TSI fulfilled.
All the inputs listed in paragraph Necessary Information must be available

(Included the licenses).
Hardware machine to install is cabled.
For users default password and available network services refer to the
applicable document [1] 9153 OMC-R Methods Handbook.
The DVDs used in the B11 1353-OMC-R installation are available.
In case of Storage Area Network (SAN), the Fibre Channel Switch

is configured.
During DVD1 installation for SAN, FC cables are not plugged in Host
Bus Adapter (HBA) card.
For M4000 the Storage TEK 2540 is used if necessary.

For M4000 OMC-R first installation, it is mandatory to have a workstation
connected to the M4000 XSCF serial port.
For M3000 HMI first installation, it is mandatory to have a workstation

connected to the M3000 XSCF serial port.
If some patches from the Delivery Server must be installed, install them
according to their Delivery Notes, after DVD1/DVD2/DVD3.
1.2.2 Restrictions
None.
14 / 64 3BK 17438 4011 RJZZA Ed.09

1.2.3 Sequence of Operations
PI No Procedure name Type
PI 01 9153 OMC-R Installation Tasks Mandatory
PI 02 Mandatory Customization Tasks Mandatory
PI 03 Declaration of the 9153 OMC-R Machine in the 9153 Mandatory *

OMC-R Network
PI 04 Optional Customization Tasks Optional
(*) : PI 03 is mandatory only if Agent, HMI Server or Remote HMI Server is installed.
Table 4: The Scenario for the Installation of a Machine from CD-ROM/DVD-ROM
The following table gives the scenarios to be applied for each machine.
Machine Type Steps to be performed
Master (*) PI 01, PI 02, PI 04
Agent (*) PI 01, PI 02, PI 03, PI 04
HMI Server, Remote HMI Server PI 01, PI 03
Back-Office Machine (*) PI 01, PI 02
(*) : M4000 is used only for Master, Agent and BOM.

Table 5: PI’s for Machines to be Installed
The machines are installed in the following order: Master, Agent, HMI.
PI 01 “ 9153 OMC-R Installation Tasks” can be performed in parallel on the
concerned machines if more copies of the CD/DVD used in installation are
available.
3BK 17438 4011 RJZZA Ed.09 15 / 64

1.2.4 Necessary Information
PI 01 Master and Agent: IP address
Hostname
Netmask
Default router
Time Zone
Two X.25 addresses for the links (at OMC3 side)

Note: The X.25 addresses are not needed if the network
doesn’t include 9120 BSCs.
Licenses files for: X.25, OSI

Note: If the network doesn’t include 9120 BSCs only the OSI
license is needed.
License files for Master: CMIP (only if Q3 communication
protocol is activated)
X.25 template name (according to the routing solution chosen

by the customer - is optional)
Note: The X.25 template name is not needed if the network
Optional feature files saved on a media support (only for

Master).
HMI Server, remote HMI IP address

Server
Hostname
Netmask
Default router
Time Zone.
PI 02 for Master MNC (Mobile Network Code)
MCC (Mobile Country Code)
PLMN_FREQ_BANDS
License file for NPO embedded/MPM
for CLM IP address
user
password
16 / 64 3BK 17438 4011 RJZZA Ed.09

PI 03 for HMI Server, Remote HMI IP address

Server, Agent:
Hostname
Type of the machine (HMI, Agent).
Netmask
Default router
PI 04 BSC parameters BSC Label (name of the BSC)
Hostname of machine on which the BSS software will run
BSC release (B10 or B11)
X.25 addresses of BSC

Note: The X.25 addresses are not needed if the network
Security Oad (if it is used).
MFS Parameters MFS Name
MFS IP address
MFS Identifier
HOST (hostname of machine on which the MFS is connected)
MFS Oad.
Users Name of the users
Password of each user
User ID (optional)
Users Profiles (list of OAD and FAD for each user).
Printers IP address
Hostname
Spool server hostname
Table 6: Needed Information.
All these information are located in Site Preparation Sheet (3BK 17438
4002 RJZZA).
3BK 17438 4011 RJZZA Ed.09 17 / 64

1.2.5 Schedule
PI PI titles Total Time Comments
PI 01 Installation of an 9153 OMC-R 1h 40min. - 4h Depending on machine type

machine
+ 45 min. (first
configuration
M4000/M3000)
+ 20 min. - 1h 15 min.
(for SAN)
PI 02 Mandatory Customization Tasks 40 min. Time recorded for Master or

Agent.
PI 03 Declaration of an 9153 OMC-R 10 min

Machine in the 9153 OMC-R
Network
PI 04 Optional Customization Tasks 1h 40 min This is an average time (4 BSS),

it depends on the number of
+ 30 min. - 3h (for
elements (BSS, printers, users).
backup)
TOTAL 4h 10 min - 6h 30 + 45 min. (first configuration

min. M4000/M3000)
+ 20 min. - 1h 15 min. (for
SAN)
+ 30 min. - 3h (for backup)
Table 7: Schedule for 9153 OMC-R Machine Installation
In case of an M4000 XLarge installation this time is valid if PI01 is executed

in parallel on the Master and the Agent, else to the TOTAL time must be
added 2h 40min.
The HMI installation (only PI01) can be executed in parallel with the Master,
else to the TOTAL time must be added 2h 30 min.
1.2.6 Impact on Service

No impact.
18 / 64 3BK 17438 4011 RJZZA Ed.09

1.2.7 Supplies, Tools and Documentation

Supplies
Designation Contents
DVD1 Solaris 10
DVD2 3PP
Solaris Patches
DVD3 ALMAP
OMC3
CD with Generic Customer Documentation Customer’s generic documentation
Optional features files oflcf.in

limits.in (if the OMC-R is used as CLM)
LKDI license.lic (if the OMC-R is used as CLM)
fulfilled TSI (Technical Status Information )
fulfilled SPS (Site Preparation Sheet )
Blank CCL (Completion Check List)
CD/DVD containing SDP Package
Floppy disk containing CDE Table*
OMC-R add-on
(*) : The CDE Table can be on the CD/DVD with the SDP Package, in this case the floppy disk is not needed.
Table 8: Supplies at OMC-R Site
The number of the DVD (DVD1, DVD2 and DVD3) is at least 1. To perform in
parallel PI01 more copies of each DVD-ROM must be available.
The OMC-R add-on are the patches taken from the Delivery Server.
Tools
Empty tapes 1, 2 or 3, depending on the OMC configuration

(XLarge or not)
Table 9: Tools
3BK 17438 4011 RJZZA Ed.09 19 / 64

1.2.8 Applicable Documentation

You must have the following documents or have electronic access to the
following documents:
9153 OMC-R Methods Handbook

3BK 17438 4004 PCZZA
TSI (Technical Status Information)

3BK 17438 0003 PCZZA
Generic Completion Check List

3BK 17438 0010 QZZZA
9153 OMC-R Network Administration Handbook

3BK 21603 AAAA PCZZA
Optional Features Activation on Running 9153 OMC-R
3BK 17438 4041 RJZZA
SPS (Site Preparation Sheet)

3BK 17438 4002 RJZZA
NPO Administration Guide

BSS Configuration Handbook

20 / 64 3BK 17438 4011 RJZZA Ed.09

1.3 Conventions
The following conventions are used in the document:
When switching from an Unix user to another in a terminal window, use the
command su - <new user>. Never use simply su (without ’-’) because
the environment of the new user is not loaded.
Keyboard keys are indicated in the text as [ XX ]. For example, Press

[ Enter ] means press the [ Enter ] key.
System messages appear in Courier font:

system message
Operator input is shown after a double right-oriented arrow, in Courier font.

The UNIX prompt of the user is also displayed. For root user the prompt is
’#’ and for axadmin user ’$’.
For:
root user the input looks like the following:
# operator_input
axadmin user the input looks like the following:
$ operator_input
Software buttons on a terminal screen are also indicated in the text as [ XX ].
To describe a menu path chain, the menu entries are chained with a ’->’.
Example:
Tools -> Options -> Printer -> ...
3BK 17438 4011 RJZZA Ed.09 21 / 64

22 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2 Scenario
This section describes all the tasks to be performed for 9153-OMC-R

installation.
3BK 17438 4011 RJZZA Ed.09 23 / 64

2 Scenario
2.1 PI01 9153 OMC-R Installation Tasks

This chapter describes how to install an 9153 OMC-R machine.
2.1.1 Operating System Installation for All Supported Machines Except

M4000
Task Description OMC-R Configuration Duration
Operating System Installation for - 30 min. - 1h

All Supported Machines Except
M4000
Apply this paragraph on Master, Agentand HMI Server / Remote HMI

Server and BOM.
All the commands must be given from the system console directly (not
remotely).
The SUN StorEdge 3510FC Array connected to SF V490 must have only one
LUN mapped (this is the status delivered by SUN). If the 3510FC Array was
installed before with Alcatel-Lucent CD/DVDs, refer to 9153 OMC-R Network
Administration Handbook section “Prepare SUN StorEdge 3510FC Array”.
1. Press Stop + A simultaneously to get the ok prompt on your screen.

2. Insert Solaris 10 DVD1 and type:
boot cdrom - install
If the installation from the DVD-ROM drive is not possible (ex. Fatal SCSI
error at script adress 8 - Illegal instruction), refer to DVD1 Installation
from Network (Section A).
3. Type the appropriate information to configure the network interface:
Enter a name for this workstation :

Type the hostname of the machine. This name must be unique for each
OMC-R connected to the network and can have up to 19 characters.
Enter an IP address for <hostname>:
Enter the netmask for <hostname>:
Enter default router IP address [just Enter for none]:
Refer to SPS for OMC-R hostname, IP address, netmask and default router.
In case one or several LAN interfaces are not physically connected to the
machine, answer with yes at the question regarding the route.
4. The "Welcome" window is displayed. To continue press [ Next ] .
5. The "Specify time zone by :" window is displayed with the following menus:
Geographic Continent/Country/Region
Offset from GMT
Time zone files
Select your location and press [ Next ].
24 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
6. The "Date and time" window is displayed:

Select data and time
Press [ Next ].
7. The "Confirm information" window is displayed. Confirm and press [ Next ].

8. A message like the following appears:
Enter WS type (GSM-AGENT GSM-HMI GSM-MASTER) :
Choose the machine type to be installed:

GSM-MASTER for Master and BOM installation
GSM-AGENT for Agent installation
GSM-HMI for HMI installation
GSM-MASTERs in case of SAN filesystem configuration for Master.
GSM-AGENTs in case of SAN filesystem configuration for Agent.
Type the corresponding machine, then press [ Enter ].
In case of SAN, if a message like the following appears depending on the

machine used:
Do you want to install this MASTER machine using:
0 : JumpStart profile
profile.v490-gsm-master-standard-2x144gb.SAN
profile.v490-gsm-master-xlarge-2x144gb.SAN
2 : dynamic partitionning
Type the appropriate option (0 for Standard configuration and 1 for
XLarge/XXLarge configuration) and press [ Enter ].
A summary of the selections is displayed. Confirm with [ y ]

The configuration scripts are started automatically.
In case of hard disks without label, ignore the following messages:
Warning : /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@
XXXXXXXXXXXXXXXXXX ( ssd0 ) corrupt label, wrong magic
number
number
If the SOLARIS 10 DVD1 was installed from network , at the end of the
first part of installation, the system reboots automatically.
If the system does not reboot automatically, perform the manual reboot
as root user
init 6
After the reboot, the system resumes automatic installation until it is
configured. During the installation procedure part, some reboots are
automatically launched.
After installation of the SOLARIS 10 DVD1, perform from the remote
machine step DVD1 Installation from Network (Section A) . From the
machine to be installed, log in as root in the CDE.
3BK 17438 4011 RJZZA Ed.09 25 / 64

2 Scenario
After installation the system will reboot automatically.
according to their Delivery Notes.
9. When the system configuration is finished, a menu with 3 options is

displayed:
1) Insert DVD2 and continue with installation
2) Exit to shell in order to get/install the licenses
3) Resume system initialization
Type the following:
[ 1 ] in case of HMI or BOM installation. No licences are needed in

case of HMI or BOM installation.
Continue with item (3)Third Party and System Patches Installation
(DVD2)
This task takes somewhere about 30–90 minutes on HMI Sun Fire 280R,
depending which 9153 OMC-R software you want to install.
[ 2 ] for Master/Agent host installation.

A shell console opens.
Continue with Install X.25, OSI and CMIP Licenses
10. Update the Completion Check List (CCL).
2.1.2 Operating System Installation for M4000/M3000

These activities install the Solaris 10 operating system.
Apply this paragraph on Master, Agent, HMI and BOM.

All the commands must be given from the system console directly (not
remotely).
2.1.2.1 Prerequisites
The following prerequisites are needed:
U24 / U27 Workstation for serial connection to M4000/M3000 machine
USB to serial adaptor for U24 / U27
Connect the serial cable between workstation and XSCF

Five IP addresses reserved for M4000 machine:
one for bge0 port as the ethernet interface (Ethernet#0) of M4000 for IP
network connection. The IP address for bge0 port must not belong to
192.168.128.0/24 network which is reserved for communication between
Storage TEK 2540 and M4000
one for nxge3 port as a ethernet interface link 3 of Quad Gigabit
Ethernet card (connection with Storage TEK 2540). The IP address
192.168.128.100 is automatically assigned to nxge3 port during M4000
installation
26 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
one for nxge2 port as a ethernet interface link 2 of Quad Gigabit

Ethernet card (connection with Storage TEK 2540). The IP address
192.168.128.99 is assigned to nxge2 port when the ST2540 Controller
firmware is updated.
one for XSCF lan#0 port as the ethernet interface (Ethernet#0) for
IP network connection
one for workstation IP network.
Three IP addresses reserved for M3000 machine:

one for XSCF lan#0 port as the ethernet interface (LAN#0) for the
IP network connection
one for M3000 WS glan#0 port as the ethernet interface (GLAN#0)
for the IP network.
one for workstation the IP network.
2.1.2.2 Ultra 24/Ultra 27 Workstation Configuration
Ultra 24/Ultra 27 Workstation Workstation 15 min.

Configuration
To configure the Ultra 24/Ultra 27 workstation for the first time:

1. Power ON the Ultra 24/Ultra 27 workstation.
Only for Ultra 24 2. Wait until the"Select a Language" window appears:
Type the corresponding language ( e.g 0 for English) then press [ Enter ].
Only for Ultra 24 3. The "Select a Locale" window appears:
Type the corresponding language ( e.g 0) then press [ Enter ].
4. The "Configure Keyboard Layout" window appears:
Select the corresponding keyboard layout ( e.g US-English) then press
[ F2 ] or [ Esc ] + [ 2 ].
Only for Ultra 27 5. Configuring network interface addresses:

Type the corresponding address (e.g. e1000g0) then press [ Enter ].
6. The "Network Conectivity " window appears with the following menus:
Networked
[x] Yes
[ ] No
Select Yes , then press [ F2 ] or [ ESC ] + [ 2 ].
To make a selection, use the arrow keys to highlith the option and press
[ Return ] to mark it [ X ]
7. The "DHCP for e1000g0" window appears with the following menus:
Use DHCP for e1000g0
[ ] Yes
3BK 17438 4011 RJZZA Ed.09 27 / 64

2 Scenario
[x] No
Select No , then press [ F2 ] or [ ESC ] + [ 2 ].
8. The "Host Name for e1000g0" window appears.
Replace <unknown> with the Ultra 24/Ultra 27 hostname according to SPS
and press [ F2 ]or [ ESC ] + [ 2 ].
9. The "IP Address for e1000g0" window appears.
Type the IP address for Ultra 24/Ultra 27 workstation according to SPS
and press [ F2 ] or [ ESC ] + [ 2 ].
10. The "Subnet for e1000g0" window appears with the following menus:
System part of a subnet
[x] Yes
[ ] No
Select Yes , then press [ F2 ] or [ ESC ] + [ 2 ].
11. The "Netmask for e1000g0" window appears.
Type the netmask for Ultra 24/Ultra 27 workstation according to SPS and
press [ F2 ] or [ ESC ] + [ 2 ].
12. The "IPv6 for e1000g0" window appears with the following menus:
Enable IPv6 for e1000g0
[ ] Yes
[x] No
Select No , then press [ F2 ]or [ ESC ] + [ 2 ].
The following message: appears.
Configuring parameters, xx seconds left to complete.
Wait until the next window appears.
13. The "Set the Default Route for e1000g0" window appears with the following
menus:
Default Route for e1000g0
[ ] Detect one upon reboot
[x] Specify one
[ ] None
In the "Default Route IP Address for e1000g0" window enter the default
router IP address, then press [ F2 ] or [ ESC ] + [ 2 ].
14. The "Confirm Information for e1000g0" window appears.
If the information displayed is correct, press [ F2 ] or [ ESC ] + [ 2 ].
If it is necessary to change any information, press [ F4 ] or [ ESC ] + [ 4 ] and
perform again the previous configuration steps.
After pressing [ F2 ] or [ ESC ] + [ 2 ] the Configuring parameters, xx
seconds left to complete. message appears. Wait until the next
window is displayed.
15. The "Configure Security Policy" window appears with the following menus:
Configure Kerberos Security
[ ] Yes
[x] No
Select No , then press [ F2 ] or [ ESC ] + [ 2 ].
16. The "Confirm Information" window appears.
Press [ F2 ] or [ ESC ] + [ 2 ] to confirm the selection.
17. The "Name Service" window appears with the following menus:
Name service
[ ] NIS+
28 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
[ ] NIS
[ ] DNS
[ ] LDAP
[x] None
Select None , then press [ F2 ] or [ ESC ] + [ 2 ].
19. The "NFSv4 Domain Name" window appears with the following menus:
NFSv4 Domain Configuration
[x] Use the NFSv4 domain derived by the system
[ ] Specify a diffrent NFSv4 domain
Select Use the NFSv4 domain derived by the system and press [ F2 ]
or [ ESC ] + [ 2 ].
20. The "Confirm Information for NFSv4 Domain" window appears.
21. The "Time Zone" window appears.
From ’Continents and Oceans’ field select the appropriate continent and
press [ F2 ] or [ ESC ] + [ 2 ].
22. The "Country or Region" window appears.
From ’Countries and Regions’ field select the appropriate country and region
and press [ F2 ] or [ ESC ] + [ 2 ].
23. The "Date and Time" window appears.
Set the date and time , then press [ F2 ] or [ ESC ] + [ 2 ].
25. The "Root Password" window appears with the following message:
Root password:
Type the root password, then press [ Return ].
Root password:
Retype the root password, then press [ F2 ] or [ ESC ] + [ 2 ].
The workstation machine automatically reboots.
26. After the reboot is finished, log into graphical interface as root user.
2.1.2.3 XSCF Configuration for M4000/M3000
XSCF Configuration for - 30 min.

M4000/M3000
Perform the following steps only if the XSCF board is not already configured.
1. Perform serial connection between the workstation and the XSCF board.Use
the followings:
Ethernet straight cable
3BK 17438 4011 RJZZA Ed.09 29 / 64

2 Scenario
RJ45 to DB9 adaptor

USB to serial (DB9) converter.
2. Set the key on the operator panel to the Service position.

3. Open a terminal asroot user on the workstation and type:
tip -9600 /dev/cua/0
connected
Press [ Enter ].
4. Confirm that the XSCF STANDBY LED (green) on the operator panel is lit.
Note: Step 6 must be performed within a minute of Step 5 or the login
certificate will time out.
5. When the login promt appears, enter default for the login name:
login:default
6. Set the key on the operator panel to the Locked position.
7. Press the [ RETURN ] key.
Wait at least five seconds before continuing to step 8.
8. Set the key on the operator panel to the Service position and press the
[ RETURN ] key.
Note: If step 8 is not performed within 1 minute the login certificate will
expire.
9. Confirm that the XSCF Shell prompt is displayed on the administration
console.
XSCF>
Configure Internal DSCP 10. From the XSCF Shell, type:

Network XSCF>setdscp
DSCP network [0.0.0.0] >
10.0.0.0
DSCP netmask [0.0.0.0] >
255.255.255.0
XSCF address [10.0.0.1] >
Press [ Enter ]
Domain #00 address [10.0.0.2] >
Press [ Enter ]
The following message is displayed only for M4000
machine.
Domain #01 address [10.0.0.3] >
Press [ Enter ]
If some values are changed the following message is displayed:
Commit these changes to the database? [y|n]:
Type [ y ] , then press [ Enter ].
Create XSCF User To create the user admxscf for remote administration perform the following
commands form XSCF prompt:
1. From XSCF prompt type the following command , then press [ Enter ].
adduser admxscf
2. Set the privileges for the admxscf user account.
setprivileges admxscf domainmgr@0 domainadm@0 useradm
platadm
30 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
3. Set the password for the admxscf user account.

password admxscf
Enter the password when you are asked and confirm.
The password must be at least 8 characters long and must contains digits,
special characters, upper and lower case characters.
4. To enable the secure shell, type:

setssh -c enable
Continue? [y|n]:
Type [ y ] , then press [ Enter ].
In order to reduce the outage please perform a reboot of the XSCF when all
the XSCF configurations were done.
Set the XSCF Host Name 1. To set the host name or the domain name for the XSCF unit log in to the
XSCF console and perform the following command:
sethostname xscf#0 <hostname>
Where <hostname> is the host name to be set for XSCF Unit.
2. Set the domain name:
sethostname -d <domainname>
Where <domainname> is the new name of the XSCF domain.
Configure the XSCF To change the network configuration perform the following from XSCF console:
Network 1. To modify the IP address and netmask.
setnetwork -m <x.x.x.x> xscf#0-lan#0 <y.y.y.y>
Where <x.x.x.x> is the netmask and <y.y.y.y> is the IP address.
2. Change the default router address-command example for XSCF Unit 0.
setroute -c add -n 0.0.0.0 -m 0.0.0.0 -g <z.z.z.z>
xscf#0-lan#0
Where <z.z.z.z> is the IP address of the default router.
3. Apply the changes with the following command:
applynetwork
Continue? [y|n]:
y
Set the XSCF Time Zone 1. To see the availlable time zones type:
settimezone -c settz -a
To see all time zones in the terminal, set the scrolling of the terminal on Ultra
24/Ultra 27 workstation to scroll back 1000 lines:
In the terminal follow the menu path Edit —>Profiles.... In the "Profiles"
window click on Edit then click on Scrolling. In the Scrollback field write 1000
and then click on Close on both windows.
2. To set the time zone type:

settimezone -c settz -s <timezone>
3BK 17438 4011 RJZZA Ed.09 31 / 64

2 Scenario
E.g: settimezone -c settz -s Europe/Bucharest

Set the XSCF Date 1. To display the current date and time type:
and Time showdate
2. To set the date and time type:
setdate -s <mmddhhMMyyyy.ss>
Where <mmddhhMMyyyy.ss> is:
mm – month
dd – day
hh – hour
MM – minutes
yyyy – year
ss – seconds
E.g: setdate –s 012716592008.00

The XSCF will be reset. Continue? [y|n]:
y
Wait until the login prompt is available after the reboot is finished.
If it is necessary to exit from the XSCF Shell and return to workstation
prompt type:
~.
Check the XSCF Settings 1. Check the settings after a reboot of the XSCF board if the reboot was
not done in the previous section.
rebootxscf
The XSCF will be reset. Continue? [y|n] :
Type [ y ] then press [ Enter ].
Wait for the XSCF to restart.
2. Check that the secure shell is enabled:
showssh
SSH status: enabled
...
3. Check that the hostname is the right one:
showhostname -a
xscf#0:<hostname>.<domainname>
4. Check the network configuration settings:
shownetwork -a
Check the configured route:
showroute -a
5. Check the time zone:
showtimezone -c tz
6. Check the date and time:
showdate
If it is necessary to exit from the XSCF Shell and return to workstation
prompt type:
~.
32 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.1.2.4 Connection to M4000/M3000

The following connection types are used during the OMC-R installation
for M4000/M3000.
The Ultra 24/Ultra 27 workstation and XSCF board are configured and
connected to IPnetwork.
Only one active connection to M4000/M3000 through XSCF is possible.
Secure Connection To perform a secure connection to M4000/M3000 through XSCF interface:

through XSCF 1. Open a terminal from the Ultra 24/Ultra 27 workstation, then type:
ssh -l admxscf <z.z.z.z>
password:
Type the coresponding password, then press [ Enter ].Where <z.z.z.z> is:
the IP address of the XSCF (M4000) ’Ethernet#0’ interface.
the IP address of the XSCF (M3000) ’LAN#0’ interface.
2. To access M4000/M3000 console perform the following command from

XSCF prompt:
console -d 0
Connect to DomainID 0? [y|n]:
y
<hostname> console login:
root
Type the coresponding password, then press [ Enter ].
export TERM=vt100
Note: If it is necessary to exit the M4000/M3000 console and return
to XSCF prompt type:
#.
The secure shell connection to M4000/M3000 is availlable only after DVD3

installation.
Secure Connection as Use the following steps to export display as axadmin user from M4000/M3000
axadmin User to Ultra 24/Ultra 27 workstation.
1. Open a terminal from the Ultra 24/Ultra 27 workstation, then type:
xhost + <x.x.x.x>
ssh axadmin@<x.x.x.x>
password:
Enter the password for axadmin user.Where <x.x.x.x> is:
the IP address of the M4000 machine on ’Ethernet#0’ interface.
the IP address of the M3000 machine on ’GLAN#0’ interface.
2. Export display from M4000/M3000 to Ultra 24/Ultra 27 workstation.

export DISPLAY=<y.y.y.y>:0.0
Where <y.y.y.y> is the IP address of the Ultra 24/Ultra 27 workstation.
3BK 17438 4011 RJZZA Ed.09 33 / 64

2 Scenario
Secure Connection as Use the following steps to export display as root user from M4000/M3000 to
root User Ultra 24/Ultra 27 workstation.
xhost + <x.x.x.x>
ssh axadmin@<x.x.x.x>
password:
Enter axadmin password and then press [ Enter ].Where <x.x.x.x> is:
the IP address of the M4000 machine on ’Ethernet#0’ interface.
the IP address of the M3000 machine on ’GLAN#0’ interface.
2. Switch to root user.

su -
password:
Enter the password for the root user and then press [ Enter ].
3. Export display from M4000/M3000 to Ultra 24/Ultra 27 workstation.
export DISPLAY=<y.y.y.y>:0.0
Where <y.y.y.y> is the IP address of the Ultra 24/Ultra 27 workstation.
2.1.2.5 DVD1 installation on M4000/M3000
DVD1 installation on - 40 min. - 1h

M4000/M3000
Perform the following steps for Master, Agent, BOM and HMI, to install the
Solaris OS on M4000/M3000.
To perform a secure connection to M4000/M3000 through XSCF interface:
ssh -l admxscf <z.z.z.z>
password:
Type the coresponding password, then press [ Enter ].Where <z.z.z.z> is:
the IP address of the XSCF (M4000) ’Ethernet#0’ interface.
the IP address of the XSCF (M3000) ’LAN#0’ interface.
2. Power ON the M4000/M3000 machine:

XSCF> poweron -d 0
DomainIDs to power on:00
Continue? [y|n]:
y
Wait until the “Power LED” is permanently lit.
To exit from OMC-R console, type quickly:

#.
The command ( #. ) must be executed within 1 second.
3. From the XSCF Shell, type:

XSCF>sendbreak -d 0
Send break signal to domainID 0? [y|n]:
34 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
y
Then press [ Enter ]
4. To access the M4000/M3000 console type the following command from
the XSCF prompt:
XSCF> console -d 0
Connect to domainID 0? [y|n]:
y
Then press [ Enter ] twice.
5. Insert Solaris 10 DVD1 in the M4000/M3000 CD-ROM drive and type:
boot cdrom - install
Note: If warnings related to corrupt label appear, please ignore them.
If you are asked Do you want to erase the disk array
configuration [y|n]? Type [ y ] and press [ Enter ]
6. Type the appropriate information to configure the network interface:
Enter a name for this workstation:
Type the hostname of the machine. This name must be unique for each
OMC-R connected to the network and can have up to 19 characters.
Note: The network 192.168.128.0 is reserved for disk array configuration
and cannot be used for other purposes.
Enter an IP address for <hostname>:
Enter the netmask for <hostname>:
Enter default router IP address [just ENTER for
none]:
Refer to SPS for OMC-R hostname, IP address, netmask and default router.
In case one or several LAN interfaces are not physically connected to the
machine, answer with yes at the question regarding the route.
7. When you are asked What type of terminal are you using?
Type the number for DEC VT100 terminal.
3
Completing system identification...
Starting remote procedure call (RPC) services: done.
Note: On M4000/M3000 machine, if messages like Could not open
device: :Error: No such file or directory appear, ignore
them.
8. When The Solaris Installation Program appears, press [ F2 ] or
[ Esc ] + [ 2 ].
To begin identifying this system, pres F2. Press [ F2 ] or [ Esc ]
+ [ 2 ] to continue.
9. "Time zone" window is displayed with the following menus:
Continents and Oceans Select and then press [ F2 ] or [ Esc ] + [ 2 ]
Country or Region Select and then press [ F2 ] or [ Esc ] + [ 2 ]
Date and Time Select and then press [ F2 ] or [ Esc ] + [ 2 ]
10. The "Confirm information" window is displayed. Confirm and press [ F2 ]

[ ESC ] + [ 2 ].
11. A message like the following appears:
Enter WS type (GSM-AGENT GSM-HMI GSM-MASTER) :
Type the machine role to be installed and then press [ Enter ]:
3BK 17438 4011 RJZZA Ed.09 35 / 64

2 Scenario
GSM-MASTER for Master and BOM installation

GSM-AGENT for Agent installation
GSM-MASTERs in case of SAN filesystem configuration for Master.
GSM-AGENTs in case of SAN filesystem configuration for Agent.
GSM-HMI for HMI installation
In case of SAN, if a message like the following appears depending on the

machine used:
Do you want to install this MASTER machine using:
profile.v490-gsm-master-standard-2x144gb.SAN
profile.v490-gsm-master-xlarge-2x144gb.SAN
2 : dynamic partitionning
Type the appropriate option (0 for Standard configuration and 1 for
XLarge/XXLarge configuration) and press [ Enter ].
Do you confirm these installation parameters [y]/n

:
Confirm with [ Enter ].
If "Configure keyboard layout" window appears. Press [ F2 ] or [ ESC ] +

[2]
Note: When M4000/M3000 console login appears, the operator has
nothing to do because scripts are running the installation.
The configuration scripts are started automatically.

The installation of DVD1 takes about:
60 minutes on standard Master SPARC Enterprise M4000
45 minutes on M3000 HMI.

number
number
After installation the system automatically reboots.
12. When the system configuration is finished, a menu with 3 options is displayed:
36 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
13. Type the following:

Type [ 1 ] in case of HMI or BOM installation. No licences are needed in
case of HMI or BOM installation.
Continue with item (3)Third Party and System Patches Installation
(DVD2)
This task takes somewhere about 30–90 minutes on HMI Sun Fire 280R,
depending which 9153 OMC-R software you want to install.
Type [ 2 ] for Master/Agent host installation.
A shell console opens.
Only for M4000/M3000 machine, type:
export TERM=vt100
Check that there are no errors in the DVD1 installation log files.
The log files directory is /var/sadm/system/logs .
Continue with Install X.25, OSI and CMIP Licenses
2.1.3 Install X.25, OSI and CMIP Licenses
Install X.25, OSI and CMIP Master/Agent 2 min. - 5 min.

Licenses
Apply this paragraph on Master and Agent.

All needed license keys have to be available before starting this step. Do not
continue if the license keys are not available.
In case the licenses are saved on another machine from the network, get
them using ftp.
1. Install the X.25 license only if 9120 BSCs are foreseen in the network.
Copy the X.25 license file in /install/data directory with the following
name: <hostname>_X25_9.2.lic
Content of <hostname>_X25_9.2.lic file has to be as below:
#
# Product : Solstice X.25/SPARC, 9.2
# Date : 09-Sep-2006
#
SERVER hostname hostid 1726
DAEMON lic.SUNW /etc/opt/licenses/lic.SUNW
INCREMENT solstice_x.25 lic.SUNW 9.100 01-jan-0 1
5F5D69A17D8D3BC09D04 "0"
#LICENSE_FILE solstice_x.25 9.100 x25_9.1 1
2. Install the OSI license.
Copy the OSI license file in /install/data directory with the following
name: <hostname>_OSI_9.0.lic
3BK 17438 4011 RJZZA Ed.09 37 / 64

2 Scenario
Content of <hostname>_OSI_9.0.lic file has to be as below:

#
# Product : Solstice OSI/SPARC, 9.0
# Date : 09-Sep-2006
#
INCREMENT STACK lic.SUNW 9.000 01-jan-0 1 ABCDD021234D2F7E4109
"0"
#LICENSE_FILE STACK 9.000 osistk9.0 1
3. If the Q3 optional feature is activated, install the CMIP license (only for
Master).
Copy the CMIP license in /install/data directory with the following
name: <hostname>_CMIP_9.0.lic
Content of <hostname>_CMIP_9.0.lic file has to be as below:
#
# Product : Solstice CMIP RT, 9.0
# Date : 09-Sep-2006
#
INCREMENT CMIP lic.SUNW 9.000 30-nov-2002 1
1ABBD1D1FF8A07B25EDC "0"
#LICENSE_FILE CMIP 9.000 osinmg9.0 1
2.1.4 Third Party and System Patches Installation (DVD2)
Third Party and System Patches - 35 min. - 1h 30 min.

Installation (DVD2)
For M4000/M3000 machine use the already opened connection during the
DVD1 installation.
If the active connection was closed use Secure Connection through XSCF (in
section 2.1.2.4) to open it again and resume the installation.
1. Only if the SOLARIS 10 DVD1 was installed from network, insert DVD2 (in
the local CD-ROM/DVD-ROM) and run as root the following command:
# install_mng -s
Continue with step (4)
38 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2. When the licenses are installed, only for Master

and Agent, type exit to close the shell.
The menu with 3 options is displayed:

Type [ 1 ] in order to start the DVD2 installation.

3. Insert DVD2 and click on [ Enter ].
Only the needed patches are installed. Ignore the messages :
WARNING: Skipping patch

WARNING: /opt/CTXSmf/data/C/ctxlarge.ico <no longer a regular file>
WARNING: /opt/CTXSmf/data/C/ctxsmall.ico <no longer a regular file>
XXXXXXXXXXXXXXXXXX ( ssd0 ) corrupt label, wrong magic number
XXXXXXXXXXXXXXXXXX ( ssd2 ) corrupt label, wrong magic number
4. The machine will reboot automatically at the end of the installation. After
reboot log in as root.
Only for M4000/M3000 machine, type:
export TERM=vt100
The log files for DVD2 installation are:
/var/omc3/install/install_mng.log
/var/omc3/install/install_PATCHES.log
5. In case of a Master or Agent installation check if the OSI daemon is running:

# ps -ef | grep osinetd
A message like the following is displayed:
root 1357 1 0 Aug 29 ? 0:00 /usr/sbin/osinetd
If it is not the case, do not continue with the installation. Check the log
files and the OSI license.
If the DVD2 was installed with errors, restart the installation.
3BK 17438 4011 RJZZA Ed.09 39 / 64

2 Scenario
2.1.5 Manual PROM Patches Installation
Manual PROM Patches - 5 min. - 40 min.

Installation
For M4000/M3000 machine use the already opened connection through XSCF.
1. Refer to 9153 OMC-R Methods Handbook, chapter Manual PROM Patches

Installation.
2.1.6 Prepare X.25 Template for Installation
Prepare X.25 Template for Master/Agent 10 min.

Installation
Apply this paragraph on Master and Agent. This paragraph has to be applied
only if the X.25 template is indicated into SPS document. Else the X.25 link
configuration will be done in X.25 Links Customization (Section 2.2.4).
For M4000 machine use the already opened connection connection through
XSCF.
1. Create the configuration file for the first X.25 link in the /install/data
directory:
# vi <hostname>_X25_9.2_00.cfg
and write down the following line:
0000:<device>:<X25address>:<comment>:<CVs>:<extension>:<X25template>
where:
<device> is: /dev/hihp0
<X25address> refer to the SPS to get the first X.25 address
<comment> a comment about the link
<CVs> are the virtual channels (default ’1-32’)
40 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
<extension> default ’ext_none’
<X25template> refer to the SPS to get the used X.25 template.

This field can have the following values:
DIRECTG2
ciscox25
SWITCH
LRG1
LRG2
Small
XLRGA
XLRGM
Example :
grenade_X25_9.2_00.cfg file is composed of the following line:
0000:/dev/hihp0:7212345:interface0:1-32:ext_none:ciscox25
2. Create the configuration file for the second X.25 link in the /install/data
directory:
# vi <hostname>_X25_9.2_01.cfg
and write down the following line:
0001:<device>:<X25address>:<comment>:<CVs>:<extension>:<X25template>
where:
<device> is: /dev/hihp1
<X25address> refer to the SPS to get the second X.25 address
<comment> a comment about the link
<CVs> are the virtual channels (default ’1-32’)
<extension> default ’ext_none’
<X25template> refer to the SPS to get the used X.25 template.

This field can have the following values:
DIRECTG2
ciscox25
SWITCH
LRG1
LRG2
Small
XLRGA
XLRGM
Example:
grenade_X25_9.2_01.cfg file is composed of the following line :
0001:/dev/hihp1:7212346:interface1:1-32:ext_none:ciscox25
3BK 17438 4011 RJZZA Ed.09 41 / 64

2 Scenario
2.1.7 SAN Filesystem Configuration
SAN Filesystem Configuration Master/Agent 20 min. - 1h 15 min.
Before proceeding with SAN filesystem configuration tasks, consult Principles

of the Operation (Section 1.1) and Prerequisites (Section 1.2.1) sections of
this document.
For M4000 machine use Secure Connection through XSCF (in section 2.1.2.4).
Apply this section only for Storage Area Network connected through a Fibre
Channel switch. FC HBA 2GB PCI is necessary to permit the usage of SAN
architecture.
During DVD1 installation the FC cables were not connected to the HBA card.
Connect the FC cables to the Host Bus Adapter (HBA) card.
1. Insert Solaris 10 DVD1 and as root user type:
cd /cdrom/cdrom0/.SAN
./move_on_SAN
This script has to be run in single user mode
Proceed to single user (y/n)?
y
System will remain in single user mode as request
of SAN procedure...
After login, please go to /SAN directory and run
again move_on_SAN script.
Root password for system maintenance (control-d to
bypass):
Enter the root password and press [ Enter ].
cd /SAN
./move_on_SAN
2. If the following messages appear, perform the following steps to enable
MPxIO (multipathing):
Found HBA FC without MPxIO enabled.System needs
reboot
In order to continue, solaris MPxIO has to be
activated for all HBA FC ports "
Do you agree with modifications (y/n) ?
y
After reboot launch again this script from /SAN directory:
cd /SAN
./move_on_SAN
3. If the following messages appear:
Force device detection on fibre channel paths
The posibilities are:
1. Check SAN/SWITCH configuration and let only the
right FC disk visible on the system
2. Edit the file fc_disks and let only the line with
the right FC disk inside (or uncommented)
If the option 2 was chosen, then launch again the
script with fc_disks as first parameter, as bellow
42 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
#./move_on_SAN fc_disks
Press any key to exit ...
Press [ Enter ] to exit the script.
Perform one of the following actions according to the
SAN configuration:
Configure the SAN/SWITCH to let only the necessary FC disks visible

on the system.
Lauch again the move_on_SAN script:
./move_on_SAN
Edit the fc_disks file to let only the appropriate lines uncommented:
vi /SAN/fc_disks
Remove or comment with the # symbol the inadequate lines.
Let only the appropriate line inside the file.
Launch again the script to create the needed partitions on SAN:
./move_on_SAN fc_disks
4. The following messages are displayed:

Move /alcatel and /alcatel/oracle on candidate FC
disk (y/n)?
ANY EXISTING FC DISK INFORMATION WILL BE LOST !!!
y
Wait until the following message appears:
Operation successfully. The system will be brought
to run level 3
To enter the graphical environment type:
exit
5. Eject the DVD1.
2.1.8 OMC3 Installation (DVD3)
OMC3 Installation (DVD3) - 15 min. - 30 min.
Apply this paragraph for Master, Agent, HMI Server, Remote HMI Server
and BOM.
For M4000/M3000 machine use Secure Connection through XSCF (in section
2.1.2.4) .
1. As root edit the file: /install/data/<hostname>.soft

Replace "3PP" by "OMC3"
2. Eject the previous DVD-ROM and insert the DVD3.
3. Launch the installation script locally (remote connection is lost during
DVD3 installation):
# install_mng -s
3BK 17438 4011 RJZZA Ed.09 43 / 64

2 Scenario
Ignore the message command is respawning too rapidly for

run_dsmlpc or run_dsmim, if it is displayed.
4. Check that there are no errors in the log files.The log files for DVD3
installation are:
/var/sadm/install/logs/install.log
5. Check that there are no errors in the log files for HMI.The log files for
DVD3 HMI installation are:
/var/sadm/install/logs/install.log
6. Launch the following script as root user on Master, Agent and HMI:
cd /usr/local/etc/
./sslCertificate.sh
7. On the Master perform as root user:
cd /etc/rc3.d
./S50apache restart
8. Eject DVD3 DVD-ROM.
9. Reboot the machines Master, Agent and BOM:

init 6
2.1.9 Reboot the HMI
Reboot the HMI HMI 3 min.
Apply this paragraph for HMI Server and Remote HMI Server.
For M3000 machine, if the active connection was closed use Secure Connection
through XSCF (in section 2.1.2.4) to open it again and resume the installation.
1. As root user reboot the HMI:

# init 6
44 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.2 PI 02 Mandatory Customization Tasks

Refer to the SPS and TSI for all information needed for the customization tasks.
2.2.1 Parameters Customization on the Master
Parameters Customization on the Master/BOM 5 min.

Master
Apply this paragraph only for Master and BOM as axadmin user.
The PLMNs declared on BOM must be the same as the ones from the Master
to be migrated.
For M4000 machines use Secure Connection as axadmin User (in section
2.1.2.4) to export the display.
1. Only for M4000 machines run the following script:

/alcatel/omc3/script/opcode.sh
2. The Input network and country codes window is displayed.Perform the
following steps and refer to the TSI for the needed information:
In the ’Own PLMN’ pannel fill in the parameters of the PLMN (present
in the TSI):
Name1, MCC and MNC
Name2, MCC and MNC
Name3, MCC and MNC
Name4, MCC and MNC
In the ’Foreign PLMN’ pannel fill in the parameters of the PLMN (present
in the TSI):
Name5, MCC and MNC
Name6, MCC and MNC
Name7, MCC and MNC
Name8, MCC and MNC
From ’PLMN_FREQ_BANDS’ field select the frequencies band:

0: GSM900 and DCS1800 bands
It is mandatory to set at least one own PLMN at step 2.

The Input network and country codes window can be activated by starting as
axadmin user the script: /alcatel/omc3/script/opcode.sh
3BK 17438 4011 RJZZA Ed.09 45 / 64

2 Scenario
The update of PLMNs must be done before the first start of the OMC-R.
When all the PLMNs are inserted click on OK button.

3. Edit the file /alcatel/omc3/osm/conf/param.cfg .To update by default
with the following values:
LOCATION from Site address found in TSI document
CUSTOMER_REF from hostname of machine found in SPS document
ORGANIZATION from Customer found in TSI document
2.2.2 OSI Interface Customization
OSI Interface Customization Master/Agent 2 min.
Apply this paragraph for the Master and Agent hosts.

Refer to the SPS to get the X.25 address.
For M4000 machine use Secure Connection as root User (in section 2.1.2.4) to
open a graphical interface as root user from workstation.
1. As root user launch the OSI tool:

# ositool&
2. In the "OSI Administration Tool" window, apply the following steps:
Click on [ Stack Manager ]
In the "Stack Manager" window select: Configuration -> Devices

In the "Device Configuration" window, select X.25 from the list
Enter the SNPA Address (OMC primary X.25 address). Click on [ Apply ]
and [ Save ]
For TCP OSI parameter configuration, in the "Device Configuration"
window, select RFC1006 from the list
Modify the Connection Pool parameter to 200. Click on [ Apply ] and

[ Save ]
3. Close all the OSI tool windows.

46 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.2.3 Setting the ID Range for the BSCs
Setting the ID Range for the BSCs Master/Agent 10 min.
In case of a concentration from 2 LARGE Host to an XLarge configuration, the

BSCs connected to the impacted OMC-Rs must have different IDs. To avoid the
need to change BSC Ids at the moment of concentration, the ranges must be
set distinct at the OMC-R installation.
Apply this paragraph for Master in LARGE configuration and BOM.
For M4000 machine use Secure Connection through XSCF (in section 2.1.2.4) .
1. Refer to the SPS to get the values for the upper and lower ID of BSCs
2. Edit as axadmin the file /alcatel/omc3/rn/im/conf/param.cfg. In this
file search for the 2 parameters:
BSC_LOWER_ID [ number1 ] (default 1)
BSC_UPPER_ID [ number2 ] (default 255)
Modify these values according to the SPS.

3BK 17438 4011 RJZZA Ed.09 47 / 64

2 Scenario
2.2.4 X.25 Links Customization
X.25 Links Customization Master/Agent 5 min.
Apply this paragraph for Master and Agent. This paragraph has to be applied
only if the X.25 links have not been configured using the adequate X.25
template, in the paragraph Prepare X.25 Template for Installation (Section
2.1.6).
For M4000 machine use:
Secure Connection as axadmin User (in section 2.1.2.4) to open a graphical

interface as axadmin user
Secure Connection as root User (in section 2.1.2.4) to open connection
as root user.
1. Refer to the applicable document [1] 9153 OMC-R Methods Handbook

section "X.25 Link Configuration", to customize the X.25 links.
2.2.5 Reboot the Machine
Reboot the Machine Master/Agent 4 min.
Apply this paragraph for Master and Agent.

For M4000 machine use Secure Connection as root User (in section 2.1.2.4)
1. Log in as root and reboot the machine, by applying the following command:
# init 6
If after log in, the following message is diplayed on Master and Agent:
The Common Desktop Environment (aka CDE) has been
deprecated and will be removed in a future release of
Solaris. Please move to the Java Desktop System (aka
JDS).
Perform the following:
Check on the box for "Do not show this message again."
Click on [ OK ].
48 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.2.6 Install the License Files
Install the License Files Master/BOM 2 min. - 5 min.
Apply this paragraph only for Master and BOM.

For BOM only the new optional feature file oflcf.in must be installed.
For M4000 machines use Secure Connection as root User (in section 2.1.2.4) .
In B11 one Centralized License Manager server (CLM) is used to license all
the OMC-Rs in the network.
Configure the OMC-R If the OMC-R is used as CLM, perform the following steps:
as CLM 1. Open a terminal window as root user
2. Run the following script:
# /alcatel/omc3/clm/script/configure_omc_for_clm.pl
3. As axadmin user copy the limits.in file from the delivered media, containing
the license in the following location: /alcatel/var/share/netconf
4. Check the presence of the new file:
cd /alcatel/var/share/netconf
ls -l limits.in
5. The output of this command must be:
-rw-r--r-- 1 axadmin gadmin <size> <date> <time>
limits.in
Pay attention to the owner and access rights of the file.
6. Check the file:
cd /alcatel/var/share/netconf
more limits.in
Check that the last line prefixed by the keyword TAG is filled with digits
composing the calculated key.
The hostid contained in limits.in file must be the same as the hostid of the
machine running the CLM.
7. If a LKDI license.lic file is provided, install it as axadmin user:

Copy the license.lic file to /var/tmp directory.
Check the owner and access rights of the file:
cd /var/tmp
ls -l license.lic
The output must be:
license.lic
Activate the license.lic file:
/alcatel/omc3/clm/script/clm_hmi.pl
[ CLM CLI ]# replaceKey /var/tmp/license.lic
3BK 17438 4011 RJZZA Ed.09 49 / 64

2 Scenario
Updating the new Record !!!!

After this command is executed, the file
/alcatel/var/share/netconf/LKDI.lic is overwritten by the new license.
Generate the key activation report:
[ CLM CLI ]# replaceKeyReport /var/tmp/
As a result the KeyReport.tar.gz file is created in /var/tmp .
This report must be copied and sent to an Alcatel-Lucent representative to
validate the LKDI.lic license activation.
Close the CLM prompt:
[ CLM CLI ]# exit
Remove the license.lic file form /var/tmp directory:
rm /var/tmp/license.lic
Declare the OMC-R It is mandatory to declare the OMC-R to a CLM. If the CLM is running on
to CLM another machine the operator must have acces to the OMC-R where the
CLM is running.
1. Open a terminal window as axadmin user on the machine running the CLM
2. Run the following script:
$ /alcatel/omc3/clm/script/clm_hmi.pl
Type the following command in the CLM prompt opened:
addomc <HOSTNAME> <IP ADDRESS>
where:
<HOSTNAME> is the hostname of the OMC-R to be added
<IP ADDRESS> is the IP address of the OMC-R to be added
3. If the following message appears:

Are you sure you want to continue connecting
(yes/no)?
Answer with yes and press [ Enter ].
4. If a password is requested:
Password:
Type the axadmin password of the added OMC-R and press [ Enter ].
5. If the following message appears:
*** -I- : Please update the /etc/hosts of <HOSTNAME>
<IP ADDRESS> machine with information about
<CLM_HOSTNAME>
Edit as root user the /etc/hosts file of the added OMC-R and add the
following line:
<CLM_IP> <CLM_HOSTNAME>
where:
<HOSTNAME> is the host name of the added OMC-R

<IP ADDRESS> is the IP address of the added OMC-R
<CLM_IP> is the IP address of the CLM server.
<CLM_ HOSTNAME> is the host name of the CLM server.
50 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
If the added OMC-R is the one running the CLM server, it is not necessary
to update his /etc/hosts file because it already contains the own IP address
and host name.
6. To list all the OMC-Rs declared on a CLM, type:

showomc
7. Close the CLM prompt:
exit
8. If the following message appeared:
-I- Please execute the command
"/alcatel/omc3/rn/im/script/updateSocks.sh
-a <CLM_HOSTNAME> in the <OMC-R_IP_ADDRESS> machine
to restore consistency
Execute the following comand as axadmin user on the added OMC-R:
$ /alcatel/omc3/rn/im/script/updateSocks.sh -a
<CLM_HOSTNAME>
where:
<CLM_HOSTNAME> is the host name of the machine running the CLM.

<OMC-R_IP_ADDRESS> is the IP address of the added OMC-R.
Perform the following task on Master and BOM.
Install New Optional Update the optional features file:

Feature File oflcf.in 1. As the axadmin user, copy the optional features file from the delivered media
to the /alcatel/var/share/netconf directory
The file containing the optional features description, with enabled or
disabled options, according to the Technical Status Information (TSI), and
the encryption of the file is prepared at Alcatel-Lucent home base.
Activated features and time validity in the oflcf.in file for BOM must be the
same as for the Master.
The encoded file is copied on a floppy or tape at Alcatel-Lucent home base,
or even sent by mail and must be installed on the new customer.
2. Check the presence of the new file:
$ cd /alcatel/var/share/netconf
$ ls -l oflcf.in
3. The output of this command must be:
oflcf.in
Pay attention to the owner and access rights of the file.
4. Check the file:
$ more oflcf.in
Check that the last line, prefixed by the TAG keyword, is filled with digits,
composing the calculated key.
3BK 17438 4011 RJZZA Ed.09 51 / 64

2 Scenario
2.2.7 Setup Rights of “known_hosts” File
Setup Rights of “known_hosts” Master 1 min.

File
This operation has to be done only on the Master.

Perform this section only if you want to change the rights of “known_hosts”
immediately after installation and not only at next start of the script
change_knownhosts_perm.pl (i.e at 3 AM).
For M4000 machine use Secure Connection as axadmin User (in section
2.1.2.4) to open it again.
Perform this section only if you want to change the rights of “known_hosts”
immediately after migration and not only at next start of the script
change_knownhosts_perm.pl (i.e at 3 AM).
Log in as root only on Master, launch the following script:

cd /alcatel/omc3/osm/script
./change_knownhosts_perm.pl
Update the Completion Check List (CCL).
2.2.8 SSH Key Synchronization
SSH Key Synchronization Master/BOM 1 min.
This operation has to be done on the Master and BOM.
For M4000 machine use Secure Connection through XSCF (in section 2.1.2.4)
1. As root launch synchronization script locally:

# /alcatel/omc3/osm/script/MF-sync_ws_ssh
52 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.2.9 Startup the Master
Startup the Master Master/BOM 5 min.
This operation has to be done only once, on Master and BOM.
2.1.2.4) to export the display.
As axadmin perform the following:

1. Start the OMC-R:
For Master run the script:
$ sudo /alcatel/omc3/osm/script/MF-start
For BOM run the script:
$ sudo /alcatel/omc3/osm/script/MF-startBOM
Check that the sec server is started:
$ ps -ef | grep -i Dsecserver | grep -v grep
Check that the obsal is started:
ps -ef | grep obsal | grep -v grep
2. Only for M4000 machines launch as axadmin user the following script:
/alcatel/omc3/script/run_omc3 -f
3. In 9153 OMC-R application click on [ DSM ] from the Icon Box:
The "DSMUSM" window is open.
4. In the [ DSM ] main window, check the color of the processes:
green color, if all is Ok
yellow color, when the process is charging.

Wait for the green color of the process.
red color if problems occur.
If any processes remain in red, call Alcatel–Lucent support. Do not continue

before solving these problems.
The http process will not start on BOM, this is normal behaviour.
5. From the OMC-R Iconbox open Current Alarms (FM). If a "Warning -

Security" window opens:
Check the ’Always trust content from this publisher.’ field
Click on [ Yes ] button.
Repeat the same settings if the window opens again.

The "FM Current Alarms Management" window opens.
3BK 17438 4011 RJZZA Ed.09 53 / 64

2 Scenario
Verify the OMC-R alarms from Current Alarms (FM) application. To check what
type of alarm and the corrective action, refer to 3BK 21605 AAAA PCZZA -
9153 OMC-R Alarm Dictionary.
2.2.10 Generic Documentation Installation
Generic Documentation Master 5 min.

Installation
Apply this paragraph only for Master. Refer to the SPS for all needed
information.
For M4000 machine use:
Secure Connection as axadmin User (in section 2.1.2.4) to open a graphical

interface as axadmin user
Secure Connection as root User (in section 2.1.2.4) to open a connection

as root user.
Refer to applicable document: 3BK 17438 4004 PCZZA 9153 OMC-R Methods
Handbook, section Generic Documentation Installation.
54 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.3 PI 03 Declaration of an 9153 OMC-R Machine in the 9153

OMC-R Network
To continue with the declaration of the 9153 OMC-R machines, the Master must
be already installed and running.
For M4000/M3000 machines use Secure Connection as axadmin User (in

section 2.1.2.4) .
2.3.1 Declaration of the Machine
Declaration of the Machine Agent/HMI 5 min.
Apply this paragraph for Agent, HMI Server and Remote HMI Server.
For a Remote HMI Server, the routing solution must be operational.
The machine to be declared must be reachable through network.

Refer to the SPS for all needed data.
1. The operations to be performed are described in the applicable document[4]
9153 OMC-R Network Administration Handbook - 3BK 21603 AAAA
PCZZA, section "Day-To-Day Administration Tasks" paragraph "Device
Management".
For Agent, HMI and Remote HMI apply "Add Workstation".
During the operations, click always on [ Continue Submission ], if this
window is displayed.
3BK 17438 4011 RJZZA Ed.09 55 / 64

2 Scenario
2.3.2 Startup the Agent
Startup the Agent Agent 5 min.
To start the declared Agent perform the following actions on the Master:
1. Click on [ DSM ] icon. In the new window will be also the Agent displayed. If
the process is not green select it and click the right mouse button. In the
pop-up menu select Start
2. The process will turn from blue color to:
green color, if all is Ok.
red color if problems occur:
If any processes remain in red, call Alcatel–Lucent support level 2. Do not

continue before solving these problems.
The http process is not started by MF-start. It must be started manually
from DSM. In the "DSMUSM" main window expand all processes, right click
on the http, select Start. Confirm with Yes when the "Confirmation Panel"
window appears.
56 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
2.4 PI 04 Optional Customization Tasks
This Customization tasks can be done from any 9153 OMC-R machine
already known by the 9153 OMC-R network except the Agent. The 9153
OMC-R menu can not be activated on the Agent.
All the following tasks have to be done only if the corresponding data are
located either in the TSI (and/or) in the SPS.
2.4.1 Password Constraints
Password Constraints Master/HMI 2 min.
For M4000 machine use Secure Connection as axadmin User (in section
2.1.2.4)
1. Default values for password rules can be modified.

Refer to TSI document to see if there are values to be modified.
If yes, as axadmin user, edit the file /alcatel/omc3/osm/conf/param.cfg
and modify the values from the section Password constraints.
2.4.2 Remote Inventory Activation
Remote Inventory Activation Master 10 min.
Apply this paragraph only for Master. This action has to be done only if the
optional feature remote inventory is enabled. Refer to the TSI to know if the
optional feature is enabled.
2.1.2.4) .
1. Refer to applicable document [5] Optional Features Activation on Running

9153 OMC-R - 3BK 17438 4041 RJZZA, chapter Install ENS".
2. To have MFS RI files, perform on demand RI for all appropriate MFSs.
Refer to document [9] BSS Configuration Handbook, chapter Perform
On Demand MFS RI from OMC-R.
3BK 17438 4011 RJZZA Ed.09 57 / 64

2 Scenario
2.4.3 Q3 Activation
Q3 Activation Master 5 min.
2.1.2.4) .
To start the Iconbox, type:
1. The Q3 activation is described in applicable document [5] Optional Features

Activation on Running 9153 OMC-R - 3BK 17438 4041 RJZZA.
Perform one of the given scenarios from 3 to 6 in the applicable document
[5]. These scenarios are also including NMC declaration(s).
2.4.4 Access Rights
Access Rights Master/HMI 10 min. - 20 min.
2.1.2.4) .
Access Rights Management

Access rights management covers:
Password Policy
User Management
OAD Management.
Operator Profile Management
FAD Management
FTP Users
1. Refer to the applicable document [4] 9153 OMC-R Network Administration

Handbook - 3BK 21603 AAAA PCZZA, chapter "Access Rights
Management".
Add Secure External Users
58 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
1. To declare external workstations and users, refer to 9153 OMC-R Network

Administration Handbook, section Add Secure External Workstation&User.
2.4.5 Configuration of Printers
Configuration of Printers Master/HMI 5 min.
2.1.2.4) .

chapter "Manual Printers Operations".
3BK 17438 4011 RJZZA Ed.09 59 / 64

2 Scenario
2.4.6 Install NPO embedded/MPM
Install NPO embedded/MPM Master 45 min
1. To install NPO embedded/MPM on OMC-R master and the connected

HMIs, apply Install NPO embedded/MPM paragraph from 9153 OMC-R
Methods Handbook document.
2.4.7 Toolchain Related Tasks

NPO Tuning Browser Installation
Toolchain Related Tasks Master 10 min.
1. To install NPO Tuning Browser (on OMC-R and all the connected HMIs) refer
to 9153 OMC-R Methods Handbook - 3BK 17438 4004 PCZZA, chapter
“Installation of NPO Tuning Browser on OMC-R”.
OMC-R declaration at NPO standalone machine
1. To install OMC-R declaration at NPO standalone machine refer to document
MS-OMC Portal/9159 NPO Platform Administration Guide, chapter “Data
Source Management”.
2.4.8 Declaration of BSS/MFS
2.1.2.4) .
Declaration of BSS
1. To declare the BSS refer to the applicable document [10] BSS Configuration
Handbook chapter "Software and Hardware Management Tasks", paragraph
"Declare BSS".
BSS Customization
chapter "SDP Packages and CDE Tables", to install B11 SDP Packages
and the CDE Tables.
60 / 64 3BK 17438 4011 RJZZA Ed.09

2 Scenario
Declaration of MFS
1. To declare the MFS refer to the applicable document [10] BSS Configuration
Handbook chapter "Software and Hardware Management Tasks", paragraph
"Declare MFS".
2.4.9 Install Citrix XenApp (Presentation Server)
Install Citrix XenApp (Presentation Master/HMI 5 min.

Server)
1. Install the Citrix XenApp Server on Master Host and/or HMI.

Refer to applicable document: 3BK 17438 4014 RJZZA, Citrix XenApp
Server/Client Installation .
2.4.10 Backup
Backup Master 30 min. - 3h
1. The backup is described in applicable document [4] 9153 OMC-R Network

Administration Handbook - 3BK 21603 AAAA PCZZA, section "Backup
and Restore of OMC-R".
3BK 17438 4011 RJZZA Ed.09 61 / 64

2 Scenario
62 / 64 3BK 17438 4011 RJZZA Ed.09

Appendix A : DVD1 Installation from Network
Appendix A: DVD1 Installation from Network
DVD1 Installation from Network - 35 min. - 1h 5 min.
This Appendix must be applied only if DVD1 installation does not start,
from the internal DVD-ROM drive.
1. Insert DVD1 in the drive of another machine (same IP subnetwork) To
perform the following actions, as root:
Check the status of AUTOMOUNT and BOOTPARAMD services.

If they are disabled, enable them. Refer to [4] 9153 OMC-R Network
Administration Handbook, 3BK 21603 AAAA PCZZA, Security Impact on
the 9153 OMC-R Remote Installation section.
Modify the file /etc/hosts by adding the line (if not already added):
<IP address> <hostname>
Where <IP address> and <hostname> are from the machine to be
installed.
Create the file /etc/ethers having the line:

<Ethernet address> <hostname>
Where <Ethernet address> and <hostname> are from the machine to be
installed (Ethernet address is a 6 bytes format, ex: 8:0:20:8f:2a:3)
Run the command (in one single line):

/cdrom/cdrom0/Solaris_<OS>/Tools/add_install_client
<hostname> sun4u
Where <OS> is the operating system version, <hostname> is from the
machine to be installed.
2. On the machine to be installed, to get the ok prompt, press Stop + A

simultaneously.
In the prompt window type:

ok> boot net - install
Wait for the graphical interface to open.
Continue with Operating System Installation for All Supported Machines

Except M4000 (Section 2.1.1) step (3)
3. After SOLARIS 10 DVD1 installation, from the remote machine perform

as root the following commands:
# cd /cdrom/cdrom0/Solaris_<OS>/Tools
# ./rm_install_client
# unshare /cdrom/cdrom0/
where <OS> is the operating system version.
If AUTOMOUNT and BOOTPARAMD services were disabled before
starting the installation, disable them. Refer to [4] 9153 OMC-R Network
Administration Handbook, 3BK 21603 AAAA PCZZA, Security Impact on
the 9153 OMC-R Remote Installation section.
3BK 17438 4011 RJZZA Ed.09 63 / 64

Appendix A : DVD1 Installation from Network
BLANK PAGE BREAK
64 / 64 3BK 17438 4011 RJZZA Ed.09

9153 OMC-R Installation PDF

Uploaded by

Copyright:

Available Formats

9153 OMC-R Installation PDF

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

9153 OMC-R Installation PDF

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent GSM

9153 OMC-R Installation

3BK 17438 4011 RJZZA Ed.09

Short title Commissioning Manual

2 / 64 3BK 17438 4011 RJZZA Ed.09

3BK 17438 4011 RJZZA Ed.09 3 / 64

4 / 64 3BK 17438 4011 RJZZA Ed.09

Solaris 10 operating system

Third party software and Solaris patches

ALMAP generic components

This method covers the following types of 9153 OMC-R machines:

Agent (XLarge, XXLarge)

Remote HMI Server

Document Pertinence This document applies to Release B11 OMC-R.

What’s New In Edition 09

Install the License Files (Section 2.2.6)

Principles of the Operation (Section 1.1).

3BK 17438 4011 RJZZA Ed.09 5 / 64

Operating System Installation for All Supported Machines Except M4000

Third Party and System Patches Installation (DVD2) (Section 2.1.4)

OMC3 Installation (DVD3) (Section 2.1.8).

DVD1 installation on M4000/M3000 (Section 2.1.2.5)

Setup Rights of “known_hosts” File (Section 2.2.7)

Setup Rights of “known_hosts” File (Section 2.2.7)

SSH Key Synchronization (Section 2.2.8).

Schedule (Section 1.2.5)

Operating System Installation for M4000/M3000 (Section 2.1.2)

Prerequisites (Section 2.1.2.1)

Startup the Master (Section 2.2.9)

PI01 9153 OMC-R Installation Tasks (Section 2.1)

PI 02 Mandatory Customization Tasks (Section 2.2)

6 / 64 3BK 17438 4011 RJZZA Ed.09

PI 03 Declaration of an 9153 OMC-R Machine in the 9153 OMC-R Network

Install Citrix XenApp (Presentation Server) (Section 2.4.9)

Backup (Section 2.4.10)

Principles of the Operation (Section 1.1)

Centralized Licence Server and Time Validity for Optional Features

OMC-R Compatible with SAN Architecture in Scenario (Section 2)

3BK 17438 4011 RJZZA Ed.09 7 / 64

Audience This document is intended for:

Field service technician

System support engineers (specialists)

Occasional users (e.g. subcontractors).

Assumed Knowledge You must have a basic understanding of the following:

Alcatel-Lucent operations and maintenance concepts for BSS

Unix operating system and Solaris system installation

Installation tools and materials.

8 / 64 3BK 17438 4011 RJZZA Ed.09

3BK 17438 4011 RJZZA Ed.09 9 / 64

1.1 Principles of the Operation

The Master host is present in all the configurations.

M4000 machines - one Agent is connected to the Master in case of

Sun Fire V880 machines - one Agent is connected to the Master in

In a multiple host OMC-R configuration (XLarge or XXLarge), the Master and

In case of SMALL and STANDARD configuration the Master Host based on SF

10 / 64 3BK 17438 4011 RJZZA Ed.09

Master Host + Agent HMI Workstation

3BK 17438 4011 RJZZA Ed.09 11 / 64

OMC-R SUN Model Processor(s) RAM Disks SAN Minimum