135 OMSSUITE81 DPL2 Installation

1350MSUITE
Network Management Suite
Rel 8.1 PL2
Installation Guide
3AL 89041 BAAA
Edition 04
December 2008
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no

responsibility for inaccuracies contained herein.
Copyright © 2007 Alcatel-Lucent
3AL 89041 BAAA

Edition 04
Status: RELEASED
All rights reserved.

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel-Lucent.
TABLE OF CONTENTS
LIST OF FIGURES ......................................................................................................................... 5
LIST OF TABLES ........................................................................................................................... 7
PREFACE......................................................................................................................................... 9
Preliminary Information.............................................................................................................. 9
Applicability................................................................................................................................. 10
Scope ........................................................................................................................................... 10
History.......................................................................................................................................... 11
Related Documents .................................................................................................................... 11
Handbook Structure ................................................................................................................... 13
General on Customer Documentation ...................................................................................... 14
1 INTRODUCTION .......................................................................................................................... 19
1.1 Installation Requirements ................................................................................................... 19
1.1.1 Requested Hardware ...................................................................................................... 19
1.2 Initial Installation.................................................................................................................. 23
1.2.1 HP-UX Operating System Installation & Configuration ................................................... 24
1.2.2 Predispose...................................................................................................................... 24
1.2.3 Instance creation ............................................................................................................ 24
1.2.4 Software copy ................................................................................................................. 24
1.2.5 Customization ................................................................................................................. 24
1.2.6 Integration ....................................................................................................................... 25
1.2.7 Network Management Sub-Systems Fuctional Dependencies....................................... 25
1.2.8 Optional Network Management Sub-Systems ................................................................ 26
1.3 Restriction for HP9000 System........................................................................................... 27
1.4 Restriction for HP Integrity System ................................................................................... 27
1.5 Registered Trademarks ....................................................................................................... 28
1.6 Conventions ......................................................................................................................... 28
2 INSTALLATION AND CUSTOMIZATION .................................................................................... 29

2.1 Quick Installation ................................................................................................................. 30
2.1.1 HP-UX Operating System Installation............................................................................. 30
2.1.2 System Predisposal ........................................................................................................ 31
2.1.3 HP-UX Operating System Configuration ........................................................................ 35
2.1.4 Install and Customize Alcatel-Lucent Software............................................................... 38
2.1.5 Proceed in the Process Configuration ............................................................................ 42
2.1.6 Final Integration .............................................................................................................. 42
2.2 Operating System Installation ............................................................................................ 44
2.2.1 Preparatory activities ...................................................................................................... 44
2.2.2 Installing HP-UX 11i ........................................................................................................ 48
2.2.3 Boot the machine............................................................................................................ 49
2.2.4 Time Zone Selection ....................................................................................................... 57
2.2.5 Time Adjusting ................................................................................................................ 58
2.2.6 Hostname Definition ....................................................................................................... 59
2.2.7 IP Address Set-up........................................................................................................... 60
2.2.8 SubNetwork Mask and GateWay set-up......................................................................... 61
2.2.9 DNS Configuration .......................................................................................................... 63
2.2.10 Core Memory and Swap/Dump Sizing.......................................................................... 64
2.2.11 Hardware Scanning....................................................................................................... 65
2.2.12 Mirror/Disk UX Selection............................................................................................... 66
2.2.13 Virtual Array Software Selection ................................................................................... 67
2.2.14 Disk Selection ............................................................................................................... 68
Installation Guide 1350MSUITE Rel 8.1 PL2

Table of Contents 3AL 89041 BAAA Edition 04 1/200
2.2.15 Keyboard selection ....................................................................................................... 72
2.2.16 Execution Phase ........................................................................................................... 73
2.2.17 Login Message During the Execution ........................................................................... 74
2.3 Software Package Predispose............................................................................................ 75
2.3.1 OS-Conf Installation on HP9000..................................................................................... 75
2.3.2 OS-Conf Installation on HP Integrity ............................................................................... 77
2.3.3 Create Depots................................................................................................................. 79
2.3.4 Before Starting ................................................................................................................ 80
2.3.5 Pre-Installation Actions ................................................................................................... 82
2.3.6 Install NMS Description and NR8 PL2 Installation Procedure ........................................ 83
2.3.7 Predispose for Installation .............................................................................................. 84
2.3.8 1359HA Post Predisposal ............................................................................................... 100
2.4 Operating System Configuration........................................................................................ 102
2.4.1 Node Name Management............................................................................................... 102
2.4.2 Synchronize the Clocks .................................................................................................. 104
2.4.3 Poseidon License Management Configuration ............................................................... 109
2.5 Install and Customize Alcatel-Lucent Software ................................................................ 113
2.5.1 Install and Customize OS-Kernel.................................................................................... 113
2.5.2 Install and Customize NMS and NMC ............................................................................ 116
2.5.3 Install and Customize 1353NM ....................................................................................... 121
2.5.4 Install and Customize 1353NM 7.3 ................................................................................. 133
2.6 Mandatory Installation Changes......................................................................................... 135
2.6.1 .ariesrc Installation Changes........................................................................................... 135
2.6.2 1354RM Installation Changes......................................................................................... 136
2.7 Final Integration ................................................................................................................... 137
2.7.1 Final Integration Script .................................................................................................... 137
2.7.2 Alarm Surveillance Federation........................................................................................ 139
3 TROUBLESHOOTING.................................................................................................................. 141
3.1 Identify a Failure Condition................................................................................................. 141
3.2 Failure installing a HP-UX ................................................................................................... 141
3.3 Recoverable Faults .............................................................................................................. 142
3.3.1 Recoverable Faults Installing Software........................................................................... 142
3.3.2 Recoverable Faults Managing SWP ............................................................................... 145
3.4 Kerberos Problems.............................................................................................................. 147
3.4.1 Kerberos kdcd Process Not Running.............................................................................. 147
3.4.2 Kerberos kdcd High CPU Consuming ............................................................................ 147
3.5 Device Full ............................................................................................................................ 148
3.5.1 Devise Full on /var Mounted File System ....................................................................... 148
3.5.2 Device full on /usr and /home ......................................................................................... 148
3.6 Inittab Process Not restarting............................................................................................. 150
3.7 Installing and Configuring Mirror Disk/UX ........................................................................ 151
3.7.1 Mirror Disk/UX Installation Prerequisite. ......................................................................... 151
3.7.2 Mirror Disk/UX Configuration Prerequisite ...................................................................... 151
3.7.3 Mirror Disk/UX Installation .............................................................................................. 151
4 ADD NEW NMS/NMC................................................................................................................... 153

4.1 Prerequisites ........................................................................................................................ 153
4.1.1 Previous installation status. ............................................................................................ 153
4.1.2 Network Release Compatibility ....................................................................................... 153
4.1.3 Disk space requirements ................................................................................................ 153
4.1.4 Reboot Planning ............................................................................................................. 153
4.2 Install a new NMS/NMC ....................................................................................................... 154
4.2.1 Customize NMS Instance ............................................................................................... 154
4.2.2 NMC Special Insertions .................................................................................................. 155
1350MSUITE Rel 8.1 PL2 Installation Guide

2/200 3AL 89041 BAAA Edition 04 Table of Contents
4.2.3 1359HA Specific Instructions .......................................................................................... 156
APPENDIX A SYSTEM TIPS .......................................................................................................... 161

A.1 Find the CD-ROM/DVD-ROM Device File........................................................................... 161
A.2 System Shutdown ............................................................................................................... 162
A.2.1 System Shutdown with Reboot....................................................................................... 162
A.2.2 System Halt .................................................................................................................... 162
APPENDIX B NMS/NMC SPECIFIC DATA .................................................................................... 163

B.1 NMS Class............................................................................................................................ 163
B.2 NMC Class............................................................................................................................ 164
B.3 Disk Requirement Tables.................................................................................................... 165
B.4 Alcatel-Lucent CD Codes ................................................................................................... 166
APPENDIX C GOGLOBAL-UX INSTALLATION AND CONFIGURATION.................................... 167

C.1 GoGlobal-UX Installation on HP-UX System..................................................................... 167
C.2 GoGlobal-UX Installation on PC......................................................................................... 167
C.2.1 Automatic Removal of GoGlobal-UX/Previous Version................................................. 170
C.3 GoGlobal-UX license........................................................................................................... 171
C.3.1 License servers definition rules ...................................................................................... 171
C.3.2 Retrieve License Servers Identity .................................................................................. 171
C.3.3 Permanent License Request .......................................................................................... 172
C.3.4 GoGlobal-UX authorization procedure ........................................................................... 175
C.3.5 Add a new license(s) ...................................................................................................... 181
APPENDIX D HP9000 SERVER CABLE CONNECTION............................................................... 183

D.1 HP9000 L Class and RP5430 .............................................................................................. 183
D.2 HP9000 A Class and RP2430.............................................................................................. 185
D.3 HP9000 RP3410 and RP3440 .............................................................................................. 185
D.4 HP9000 RP4440 ................................................................................................................... 186
D.4.1 RP4440 with DS2405 ..................................................................................................... 186
D.4.2 RP4440 with MSA30 ...................................................................................................... 187
D.5 HP9000 N Class and RP7400.............................................................................................. 188
D.5.1 HP9000 N Class and RP7400 with SC10 ...................................................................... 188
D.5.2 HP9000 RP7400 with DS2405 ....................................................................................... 189
D.5.3 HP9000 RP7410 with DS2405 ....................................................................................... 190
APPENDIX E HP INTEGRITY SERVER CABLE CONNECTION................................................... 191

E.1 HP Integrity RX2660 ............................................................................................................ 191
E.2 HP Integrity RX6600 ............................................................................................................ 192
E.3 HP Integrity RX7640 ............................................................................................................ 193
ABBREVIATIONS ............................................................................................................................ 195
INDEX ............................................................................................................................................... 197
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 199

Table of Contents 3AL 89041 BAAA Edition 04 3/200
4/200 3AL 89041 BAAA Edition 04 Table of Contents
LIST OF FIGURES
Figure 1. GPS/MP to W-cable connecion. ........................................................................................ 20
Figure 2. F/F adaptor cable to connect PC to HP GSP/MP .............................................................. 20
Figure 3. Installation Phases on a server. ......................................................................................... 23
Figure 4. Example of TMN configuration .......................................................................................... 25
Figure 5. NMS functional dependency.............................................................................................. 26
Figure 6. GoGlobal-UX Logo ............................................................................................................ 39
Figure 7. Smart Array Main Menu Configuration window ................................................................. 53
Figure 8. Smart Array View Configuration window ........................................................................... 54
Figure 9. Smart Array Create window - 1.......................................................................................... 55
Figure 10. Smart Array Create window - 2........................................................................................ 55
Figure 11. Smart Array Delete window - 1 ........................................................................................ 56
Figure 12. Smart Array Delete window - 2 ........................................................................................ 56
Figure 13. Example of disk configuration.......................................................................................... 69
Figure 14. Alcatel-Lucent NMS Architecture..................................................................................... 80
Figure 15. 1359HA communication example. ................................................................................... 100
Figure 16. Network Example............................................................................................................. 103
Figure 17. NTP Configuration Example ............................................................................................ 104
Figure 18. List of existing instances .................................................................................................. 118
Figure 19. NMS Customize Window ................................................................................................. 119
Figure 20. NMS Customize trace window......................................................................................... 120
Figure 21. List of existing instances .................................................................................................. 125
Figure 22. 1353NM Customize Window ........................................................................................... 125
Figure 23. 1353NM Customize Trace ............................................................................................... 127
Figure 24. 1353NM Custom Product Selection N.1 .......................................................................... 127
Figure 25. 1353NM Custom Product Selection N.2 .......................................................................... 128
Figure 26. 1353NM Custom Warning................................................................................................ 128
Figure 27. 1353SHBKW 7.0 Custom System Selection. .................................................................. 130
Figure 28. 1353SHBKW 7.0 Custom Parameters Set-up. ................................................................ 131
Figure 29. 1353SHBKW 7.0 Custom Execution window................................................................... 132
Figure 30. Add 1359HA Starting configuration Example................................................................... 156
Figure 31. Add 1359HA Final configuration Example ....................................................................... 157
Figure 32. GoGlobal-UX Logo .......................................................................................................... 167
Figure 33. GraphOn License WEB Page .......................................................................................... 172
Figure 34. GraphOn License WEB Page - Software Agreement ...................................................... 173
Figure 35. GraphOn Info request window for Single server.............................................................. 173
Figure 36. GraphOn Info request window for Three Redundant servers .......................................... 174
Figure 37. GraphOn License WEB Page - License Output Example................................................ 175
Figure 38. Front view of L Server (without cover panel) ................................................................... 183
Figure 39. Rear view of L Server ...................................................................................................... 184
Figure 40. Front view of A Class and RP2430 Servers (without cover panel) .................................. 185
Figure 41. RP3410 and RP3440 Server Front.................................................................................. 185
Figure 42. RP4440 Front View without front panel. .......................................................................... 186
Figure 43. RP4440 Rear View .......................................................................................................... 186
Figure 44. RP4440 Front View without front panel ........................................................................... 187
Figure 45. RP4440 Rear View .......................................................................................................... 187
Figure 46. Rear view of N/RP74xx Server with SC10....................................................................... 188
Figure 47. RP7400 Server with DS2405........................................................................................... 189
Figure 48. Rear view of RP7410 Server with DS2405...................................................................... 190
Figure 49. RX2660 Front Panel ........................................................................................................ 191
Figure 50. RX2660 Rear Panel......................................................................................................... 191
Figure 51. RX6600 Front Panel ........................................................................................................ 192
Figure 52. RX6600 Rear Panel......................................................................................................... 192

List of Figures 3AL 89041 BAAA Edition 04 5/200
Figure 53. rx7640 Front view ............................................................................................................ 193
Figure 54. rx7640 Rear View ............................................................................................................ 193

6/200 3AL 89041 BAAA Edition 04 List of Figures
LIST OF TABLES
Table 1. Handbooks related to the specific software application ...................................................... 11
Table 2. Referred External Documents ............................................................................................. 12
Table 3. Related Handbooks............................................................................................................. 12
Table 4. Optional Network Management Sub-system Applicability Table ......................................... 26
Table 5. NR8.1 PL2 NMS/NMC table ................................................................................................ 40
Table 6. List of supported hardware components: ............................................................................ 44
Table 7. List of supported hardware components: ............................................................................ 46
Table 8. 1353NM Instances .............................................................................................................. 89
Table 9. Involved IP Network Node table .......................................................................................... 102
Table 10. IP Network Description example. ...................................................................................... 103
Table 11. Three Server Redundant License Form ............................................................................ 109
Table 12. Single License Form.......................................................................................................... 109
Table 13. Disk requirements for NMS Software for NR8.1 PL2 ........................................................ 165
Table 14. Disk Requirements for NMS Instances for NR8.1 PL2...................................................... 165
Table 15. Alcatel-Lucent NR8.1 PL2-DR4 Media codes ................................................................... 166

List of Tables 3AL 89041 BAAA Edition 04 7/200
8/200 3AL 89041 BAAA Edition 04 List of Tables
PREFACE
Preliminary Information
WARNING
ALCATEL-LUCENT makes no warranty of any kind with regards to this manual, and specifically dis-
claims the implied warranties of merchantability and fitness for a particular purpose. ALCATEL-
LUCENT will not be liable for errors contained herein or for damages, whether direct, indirect, con-
sequential, incidental, or special, in connection with the furnishing, performance, or use of this mate-
rial.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL-LUCENT.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL-LUCENT and must not be cop-
ied, reproduced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel-Lucent Technical Assistance Center for questions reffered to the
information contained in this document.
To send your comments about this handbook please follow the indication on Customer Documen-
tation Feedback.

Preface 3AL 89041 BAAA Edition 04 9/200
Applicability
This handbook applies to following product–releases:
PRODUCT Part Number
1350 3AL 88852 AAAA
PRODUCT RELEASE VERSION (N.B.) Part Number
1350 8.1 8.1 PL2 3AL 89038 AAAA
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operator's Handbooks) are not mod-
ified unless the new software “version” distributed to Customers implies man-machine interface
changes or in case of slight modifications not affecting the understanding of the explained pro-
cedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Scope
This document describes how to install and configure an HP9000 or an HP Integrity computer systems
in order to allow the correct usage of the Alcatel-Lucent NMS application Software.

10/200 3AL 89041 BAAA Edition 04 Preface
History
EDITION DATE DESCRIPTIONS
Ed. 01 May 2008 NR8.1 PL2 Installation Guide
Ed. 02 August 2008 NR8.1 PL2 Installation Guide

Aligned 1350MS 8.1 PL2-SP1 DR4
Ed. 03 October 2008 NR8.1 PL2 Installation Guide

Aligned 1350MS 8.1 PL2-DR4
Ed. 04 December 2008 NR8.1 PL2 Installation Guide

Modify mandatory installation changes description
Related Documents
The list of handbooks given here below is valid on the issue date of this
Handbook and can be changed without any obligation for ALCATEL-
LUCENT to update it in this Handbook.
Some of the handbooks listed here below may not be available on the
issue date of this Handbook.
The standard Customer Documentation in the English language for the equipment whose product–
release–version is stated in “Applicability” on page 10 consists of the following handbooks:
Table 1. Handbooks related to the specific software application
REF HANDBOOK Part Number Notes
[1] 1350Rel8.1 PL2 THIS

3AL 89041 BAAA
Installation Guide HANDBOOK
[2] 1350Rel8.1 PL2

3AL 89041 AAAA
Administration Guide

Table 2. Referred External Documents
[3] 1350 Management Suite Upgrade Guide 8.1
Table 3. Related Handbooks
[4] 1353NM 7.4D

3AL 89142 BAAA
[5] 1354RM 7.4F

3AL 61269 CAAA
[6] 1354BM ETH 8.1D

3AL 86563 BAAA
ETH Administration Guide
[7] 1354BM PR 8.1F

3AL 86562 BAAA
Operator Handbook
[8] 1359HA 8.0

3AL 88119 BAAA
Installation & Administration Handbook
[9] 1359IOO 5.4

3AL 88356 AAAA
[10] 1359ISN 5.1D

3AL 88259 AAAA
[11] 1354SY 8.0.A

3AL 70968 BAAA

Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized “drawing-up guides" com-
plying with such suggestion.
This handbook is divided into the main topics described in the table of contents:
The technical contents of the document is mainly divided into two parts.
PREFACE: It contains general information as preliminary information, safety

recommendation, handbook scope, history, related documents.
Furthermore, it describes the handbook structure and the customer
documentation.
Introduction The requirements, initial and restriction are briefly described.
Installation & Customization This chapter shows how to install and customize Alcatel-Lucent
Network Management Subsystems on a HP9000 or on a HP Integ-
rity system.
Add new NMS/NMC This chapter describes how to add a new NMS, a new NMC or a new
NMS instance to an existing Alcatel-Lucent TMN system.
Troubleshooting This chapter shown how to solve some trouble can occur during the
installation, and how to proceed when possible.
Appendix A In this appendix some system tips are show.
Appendix B In this appendix NMS and NMC specific data are described.
Appendix C In this appendix GOGLOBAL-UX installation and configuration is
described .
Appendix D This appendix shows the suggested connections for the SCSI and
Fibre Channel cable for the HP servers foreseen.
ABBREVIATIONS: Not applicable
INDEX Not applicable
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
TION FEEDBACK documentation.

General on Customer Documentation
Note: when Network Management Operator’s Handbook is made, other handbooks can refer to it.
A "product" is defined by the network hierarchical level where it can be inserted and by the whole of per-
formance and services for which it is meant.
A "product" evolves through successive "product–releases" which are the real products marketed for
their delivery at a certain "product–release" availability date.
So, a "product-release" defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific "product–
release" has been designed, engineered and marketed for.
In some cases a "product–release" has further development steps, named "versions", that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A "product–release" has its own standard Customer Documentation, composed by one or more hand-
books.
A new "version" of a "product–release" may or may not produce a change in the status of the Customer
Documentation set, as described in “Handbook Updating” following part.
Handbook supply to Customers
Handbooks are not automatically delivered together with the equipment they refer to.
The number of handbooks per type to be supplied must be decided at contract level.
Aims of standard Customer Documentation
Standard Customer Documentation, referred to hereafter, must be always meant as plant–independent.

Plant–dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far
as contents, formats and supply conditions are concerned (plant–dependent documentation is not
described here).
Standard hardware and software documentation is meant to give the Customer personnel the possibility
and the information necessary for installing, commissioning, operating and maintaining the equipment
according to Alcatel-Lucent Laboratory design choices.
In particular: the contents of the handbooks associated to the software applications focus on the expla-
nation of the man–machine interface and of the operating procedures allowed by it; maintenance is
described down to faulty PCB location and replacement.
Consequently, no supply to the Customers of design documentation (like PCB hardware design and pro-
duction documents and files, software source programs, programming tools, etc.) is envisaged.
The handbooks concerning hardware (usually the "Technical Handbook") and software (usually the
"Operator's Handbook") are kept separate in that any product changes do not necessarily concern their
contents.
For example, only the Technical Handbook might be revised because of hardware configuration
changes (e.g., replacing a unit with one having different P/N but the same function).
On the other hand, the Operator's Handbook is updated because of a new software version but which
does not concern the Technical Handbook as long as it does not imply hardware modifications.
However, both types of handbooks can be updated to improve contents, correct mistakes, etc..

Handbook Updating
The handbooks associated to the "product-release" are listed in “Related Documents” on page 11.
Each handbook is identified by:

– the name of the "product–release" (and "version" when the handbook is applicable to the versions
starting from it, but not to the previous ones),
– the handbook name,
– the handbook Part Number,
– the handbook edition (usually first edition=01),
– the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
Changes introduced in the same product–release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
– only the date changes (pointed out in the Table of Contents) when modifications are made to the edi-
torial system not changing the technical contents of the handbook.
– the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
• the changes with respect to the previous edition are listed in History on page 11.;
• in affected chapters, revision bars on the left of the page indicate modifications in text and draw-
ings.
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A). Version character can be used for draft or proposal edi-
tions.
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operator's Handbooks)
are not modified unless the new software "version" distributed to Customers
implies man-machine interface changes or in case of slight modifications not
affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue (sup-
plying errata-corrige sheets is not envisaged).
Changes due to new product version
A new product version changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.

Customer documentation on CD-ROM
In the following by 'CD-ROM' it is meant 'Customer Documentation on CD-ROM'
Contents, creation and production of a CD-ROM
In most cases, a CD-ROM contains in read-only eletronic format the documentation of one product-
release(-version) and for a certain language.
In some other cases, the same CD-ROM can contain the documentation of different product-release(-ver-
sion)s for a certain language.
As a general rule:
– CD-ROMs for Network Management products do not contain:
• the Installation Guides
• the documentation of system optional features that Customers could not buy from Alcatel-
Lucent together with the main applicative SW.
– CD-ROMs for Network Elements products do not contain:
• the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel-Lucent together with the main equipment).
A CD-ROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and
hyperlinks make the navigation easier. No additional information is added to each handbook, so that the
documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CD-ROM
is recorded.
Suitable checks are made in order to have a virus-free product.
After a complete functional check, the CD-ROM image is electronically transferred to the archive of the
Production Department, so that the CD-ROM can be produced and delivered to Customers.
Use of the CD-ROM
The CD-ROM can be used both in PC and Unix WS environments.
The CD-ROM starts automatically with autorun and hyperlinks from the opened “Index" document permit
to visualize the .pdf handbooks
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been
installed on the platform.
The CD-ROM doesn't contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CD-ROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and
zooming tools included in the tool, and to print selected parts of the documentation through a local printer.

CD-ROM identification
Each CD-ROM is identified:
1) by external identifiers, that are printed on the CD-ROM upper surface:

– the name of the "product-release(s)" (and "version" if applicable)
– a writing indicating the language(s),
– the CD-ROM Part Number),
– the CD-ROM edition (usually first edition=01)
2) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by
whose collection and processing the CD-ROM itself has been created.
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in previous para. point 2) , in association
with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-Lucent-Information-System as a struc-
tured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel-Lucent archive
system, a check in the Alcatel-Lucent-Information-System is made to identify the list of CD-ROMs that
must be updated to include the new editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks com-
posing the collection

1 Introduction
This document describes how to install Alcatel-Lucent Network Management Subsystem (NMS) on a
HP9000 or HP Integrity system devoted to this purpose. The initial installation is foreseen for machine
where the operating system is not installed, it includes HP-UXTM 11i V1 for PA-RISCTM, HP-UXTM 11i V2
for ITANIUMTM, and the third party software requested by an NMS and NMC.
If you have HP9000 or HP Integrity system already installed for NR8.1 PL2, you can use this document
for installing a new NMS, new NMC or create new NMS instance (refer to chapter 4 “Add New NMS/NMC"
at page 153).
If the machine has been installed with previous NR7 platform, it is suggested to evaluate the opportunity
to upgrade the current installation to NR8.1 following the 1350 Upgrade guidelines [3].
1.1 Installation Requirements

Hereafter the bill of materials requested to be able to carry on installation.
1.1.1 Requested Hardware
The supporter HP9000TM and HP IntegrityTM hardware configuration is specified respectively in the para-
graph 2.2.1.1 “Check HP9000 Hardware Configuration" at page 44 and in the paragraph 2.2.1.2 “Check
HP Integrity Hardware Configuration" at page 46. To completely define the HP9000 or HP Integrity con-
figuration you have to compute the amount of disk space requested by the Alcatel-Lucent NMS you plan
to install.
Then add the items shown in the following paragraphs.
1.1.1.1 Requested Network Equipments
The installation of a HP-UXTM can not be carried on without connecting the server to a Local Area Network
(LAN), because of this the minimum equipment required are:
1) Two BT LAN cables.
2) Two Local Area Network plug or a stand alone Ethernet Hub.
The installation can not be performed if the LAN card it is not connected to the LAN plug or a stand
alone Ethernet Hub.

Introduction 3AL 89041 BAAA Edition 04 19/200
1.1.1.2 Requested PC
To be able to perform Alcatel-Lucent TMN systems installation, you have to be able to perform some
actions by using HP9000 or HP Integrity server console, and some other have to done via Graphical User
Interface (GUI), for these reasones the personal computer must be equipped with one RS232 and one
Local Area Network (LAN) ports. The RS232 port have to be connected with the server console (see the
HP server specific documentation to know how to find it).
Hereafter an example that shows how to connect HP9000 L1000 server console to a PC. HP9000 server
class L, A, N and RP are equipped with a specific processor that allows the system remote control. This
processor name can be Guardian Service Processor (GSP) or Managenet Processor (MP) depending by
model. In both cases it has a RS232 port where a A5191-63001 cable has to be connected to. The A5191-
63001 is call W cable, because you have just a 25 pins RS232 connector splitted in three 9 pins connec-
tors, and one of them is mark with “Console":
Lan Connector RS232 Connector
GSP/MP Connector
A5191-63001 Console connector.

W-Cable
Figure 1. GPS/MP to W-cable connecion.

A F/F “Adapter" cable have to be used to connect the PC RSR 232 port with the A5191-63001 W-cable
console. The cable schema is shown in Figure 2.
3 Tx Tx 3
2 Rx Rx 2
7 RTS RTS 7
8 CTS CTS 8
6 DSR DSR 6
5 S.G. S.G. 5
1 DCD DCD 1
4 DTR DTR 4
9 RI RI 9
Figure 2. F/F adaptor cable to connect PC to HP GSP/MP

The GUI acces to HP9000 server in provided by installing GoGlobal-UX software (see “1350 Adminis-
tration Guide" [2] for more information) and connecting the PC to Local Area Network where the HP9000
server is connected to.

20/200 3AL 89041 BAAA Edition 04 Introduction
1.1.1.3 Required Go-Global UX License
Go-Global UX needs a permanent or temporary license to be able to run (see “1350 Administration Guide"
[2] for more information).
1.1.1.4 Requested Hard Disks
The hard disk requirements within NR8.1 PL2 are strictly related to the NMS you are installing, and the
size of the instances of them.
Another specific behavior of OS-Conf is related to the primary SWAP/DUMP management, in fact the
default size of this fundamental system area is defined as the double of the core memory size. Because
of this the minimum disk space requirement for HP-UXTM installation depends by the machine core mem-
ory size, and can be summarize in the following:
8 G byte for machine with of core memory up size up to 4 G byte
36 G byte for machine with of core memory up size between 5 and 8 G byte
72 G byte for machine with of core memory up size between 9 and 16 G byte
To compute the required space total amount use the following formulas:
For single volume systems:

<Unix>+<Software>+<Data>=<amount of disk space>
For multiple volume systems, there are two formulas: one for computing the amount of space required
on system volume group (vg00), and another one for the data:
System volume formula:
<Unix>+(<Software>+<Not protected Data>)*115/100=<amount of disk space>
Data volume formula:
<Data>*115/100=<amount of disk space>
N.B. The system can not share the same physical hardware, that means to implement a
multiple volume system you need al least one hard disk drive for each data volume.
Where:
<Unix> Means the amount of disk space requested by HP-UXTM operating system, it
can be assumed as up to 6 Gbyte for HP9000 servers, and up to 10 Gbyte for
HP Integrity, where you have to add the disk space devoted to store swap and
crash areas. The amount of swap space can be computed as the higher value
between the RAM size multiplied per two and the sum of swap size required by
each NMS you have to instal and NMS-Instance you have to create, refer to
Table 13.(page 165) and Table 14. (page 165) for the NMS swap requirements.
The size of crash area within /var/adm/crash directory, it corresponds to half
of core memory size.
<Software> Means the amount of requested disk space for storing the software. Its value
can be computed by summing the code size defined by each NMS you have
to install, refer to Table 13.(page 165).
N.B. OS-Kernel has to be always installed.

<Data> Means the amount of requested for data storage. If you are computing the value
for a single volume system, you sum the data size defined by each NMS-
instance you have to create, refer to Table 14. (page 165).
For the multiple volume group each NMS instance defines the data size for the
volume group.
<Non protected Data> Means the amount of requested for data storage defined not protected by
1359HA Data Sharing. For this kind of data there is no difference in manage-
ment between single or multiple volume system, you sum the data size defined
by each NMS-instance you have to install.
N.B. Independently by the results of the computation the minimum disk requirement are specified
at the beginning of this paragraph.
Example: To install a 1354RM 7.4 with one Master Large instance and 1353NM 7.4 with two Presentation
instances on a HP9000TM server equipped with 3Gbyte RAM.
Single volume:
The size of primary swap/dump area will be 3*2*1024 Mbyte=6144 Mbyte, the amount of requested
swap will be: (500+7500)+(500+2*250) Mbyte=9000 Mbyte, so 9000 Mbyte is the higher value, and
it will be used. So the total a mount of operating system you have to add: 6114 Mbyte for HPTM and
3PP software, 9000 Mbyte for swap areas, and 1536 Mbyte for crash area. The result will be: 16650
Then you have to add: 1800 Mbyte for OS-Kernel, 3600 Mbyte for 1353NM , 1000 Mbyte for 1354RM
to compute the disk space amount for Alcatel-Lucent Software. Total 6400 Mbyte.
The last the value for the data instances: 8000 Mbyte for 1354RM, 2*100 Mbyte for 1353NM. Total
8200 Mbyte.
16650+(6400+8200)115/100=33440
You need 4x9Gbyte or 2x18Gbyte or 1x36Gbyte. Moreover, if you want to use this system as depot
machine, you have also to add other disks.
Multi Volume:
The difference with the previous is only related to the 1354RM data instance, that will be place in a
different volume group. So the system volume group will need:
16650+(6400+200)115/100=24240
Data volume group:
8000*115/100=9200
For the multiple volume group configuration you need 3x9Gbyte or 2x18Gbyte or 1x36Gbyte for sys-
tem volume group, and one 9Gbyte or 18Gbyte or 36 Gbyte for the data.
N.B. IF YOU CONFIGURE THE MIRROR DISK/UX FEATURE, YOU MUST PROVIDE THE DOU-
BLE OF THE HARD DISK SIZE COMPUTED.

1.2 Initial Installation
The NR8 initial installation approach allow to distinguish six main activities:
1) HP-UXTM Operating System Installation & Configuration

2) Predispose
3) Instance creation
4) Software copy
5) Customization
6) Integration
The following picture shows the NR8 installation process on a server, starting from an empty system up
to an operational one. Each step adds a something new in term of areas, software or references.
HP-UX Predispose Instance

Creation
HP-UX 11i HP-UX 11i HP-UX 11i
NMS2_1_Vx_Master NMS2_1_Vx_Master
NMS2_2_Vx_Master NMS2_2_Vx_Master SW copy
NMS1_1_Vx_Master
NMS1_1_Vx_Master
NMS2_2_Vx_Client
NMS2_1_Vx_Client
NMS2_2_Vx_Client
NMS2_1_Vx_Client
Integration Customize
OS-Kernel, NMS OS-Kernel, NMS OS-Kernel, NMS
HP-UX 11i HP-UX 11i HP-UX 11i
File system Internal data reference Exterenal data reference Integration reference
Figure 3. Installation Phases on a server.

1.2.1 HP-UX Operating System Installation & Configuration
The HP-UX 11i operating system installation is performed to set-up a new system or recicle an old one,
that is not installed with the right operating system version. The previous hard disk contents will be lost.
1.2.2 Predispose
Predispose allows predisposing HP-UX for Alcatel-Lucent software installation and execution, in terms
of: kernel parameter, file system (size, location), and software layer products. These data have to be pro-
vided with a Software Packages Description (). A specific set of program will prerare the system as
requested.
N.B. This activity can require the system reboot.
1.2.3 Instance creation

Instance creation allows to predispose HP-UX for Alcatel-Lucent data instances is a process like predis-
pose, but related to the data. Also the data instance requiremensts have to defined in the Software Pack-
ages Description.
N.B. This activity can require the system reboot and can be combined with predispose.
1.2.4 Software copy

The software copy is the most important installation phase, when the entire Alcatel-Lucent Network Man-
agement software is copied from the distribution media to the installation target.
1.2.5 Customization
The customization phase adapts the data instance to target system performing the following actions:
– Creates empty data structure.
– Makes links with the installed management software.
– Compiles parameter files by setting the values relevant for instance configuration.

1.2.6 Integration
Integration phase allows to join together feature of different NMS's when it is foreseen.
1354RM 1354RM
Presentation Master
1353NM_1_Vx_C
1353NM_2_Vx_C
1353NM_1_Vx_C
1353NM_2_Vx_C
1354RM_1_Vy_C
1354RM_1_Vy_M
OS-Kernel, 1353NM Vx OS-Kernel, 1353NM Vx
1354RM Vy Software 1354RM Vy Software
HP-UX 11i HP-UX 11i
1353NM_1_Vx_M 1353NM_2_Vx_M
OS-Kernel, OS-Kernel,
1353NM Vx Software 1353NM Vx Software
HP-UX 11i HP-UX 11i
1353NM 1353NM
Master Master
Figure 4. Example of TMN configuration
1.2.7 Network Management Sub-Systems Fuctional Dependencies

The 1350 Management Suite is a multi-layer architecture where NMS (Network Management Sub-Sys-
tems) can require functionalities provided by other NMSs. This implies dependencies in the system isn-
tallation.

The following figure summarizes the dependencies among the NMSs: NMSs shown in the upper level
require the installation of NMS located in the lower layers.
N.B. OS-Kernel is required for all NMSs.
1354SY 1354BM 1354BM

ATM ETH
1354BM
PR
Mediator
1354RM
1353NM
OS-KERNEL
Figure 5. NMS functional dependency
Some NMS foresees two configurations: master and client. In this case client instances have to be
installed whenever the master is located in different host (distributed configuration).
N.B. 1353NM only foresees multiple client instances on the same host.
1.2.8 Optional Network Management Sub-Systems

Alcatel-Lucent Networks Management Suite foresees optional Sub-systems such as: 1359ISN, 1359IOO,
and 1359HA. These sub-systems enhance other NMS feature, adding interfaces and high availability.
Here after the optional NMS applicabilty table.
Table 4. Optional Network Management Sub-system Applicability Table
Optional NMS Applicable NMS
1359ISN 1354RM
1359IOO 1353NM 1354BM-ETH 1354BM-PR 1354RM 1354SY
1359HA 1353NM 1354BM-ETH 1354BM-PR 1354RM

1.3 Restriction for HP9000 System
The OS-Conf 7.1.2 has the following restrictions:
– The minimum hard disk space supported is 9 Gbyte.
N.B. this configuration is allowed only for machine with up to 512 Mbyte of core memory, for
larger amount of memory the minimum disk requirement is higher.
– The boot disk size has to be larger than core memory size.
– The machine configuration not included in the “List of supported hardware" Table 6. at page 44 are
not guarantee.
– The usage of the Virtual Array LUN for booting is forbidden.
– The usage of dual access disk as boot disk in conjunction with mirror disk protection can be done
only in case installation of HP-UX does not require more than 1+1 disk unit. If more than two disk
are used a problem can rise configuring the boot area.
– DBD-MySQL 2.1026 and 3.0004 can not be installed at the same time, the second overwrites the
first one. The access to MySQL 3.23.56 database via DBD-MySQL 3.0004 has been not verified.
– OS-Conf use /etc/lvmpvg to correcly manage the Mirror Disk/UXTM configuration and file system
extension. Manual changes of this file are forbibben!
1.4 Restriction for HP Integrity System

The OS-Conf 8.1.2 has the following restrictions:
– The minimum hard disk space supported is 18 Gbyte.
N.B. This configuration is allowed only for machine with up to 4 GB of core memory.
– The boot disk size has to be larger than core memory size.
N.B. For system equipped with Serial Attached SCSI (SAS) controller the minimum boot disk
size is: 13 GB+RAM size.
– The machine configuration not included in the “List of supported hardware" Table 7. at page 46 are
not guarantee.
– The usage of the Storage Area Network (SAN) for booting is forbidden.
– The usage of hard disk larger than 350 GB is not supported.
– A volume group cannot contain both hard disks and SAN Logical Units.

1.5 Registered Trademarks
– UNIX® is a registered trademark of UNIX System Laboratories in the U.S.A. and other countries.
– OSF/Motif® is a trademark of the Open Software Foundation.
– HP® is a registered trademark of Hewlett-Packard Corporation.
– HP9000/700®, HP Integrity and HP-UX® are trademarks of Hewlett-Packard Corporation.
– Itanium is a trademarks of Intel Corporation
– HP OpenView® and HP OpenView Window® are trademarks of Hewlett-Packard.
– ORACLE® is a registered trademark of Oracle Corporation.
1.6 Conventions
The following conventions are used in this manual:
[Enter] A key name is shown between square brackets to indicate that you press a
named key on the keyboard.
courier Courier type is uses to indicate the output produced by the system or data that
you can find.
bold italic Bold italic letters indicate informations that you must enter from the keyboard.
<data> Data shown between angle brackets means that these data depending by the
particular instance of the system. It must be substituted with the correct data.
# Actions must be performed as root.
..,sys,root # Actions must be performed as root.
..,$ Actions must be performed as normal user (not as root).
..,oracle> Actions must be performed as oracle user.
SQL> Actions must be performed in SQL utility.

2 Installation and Customization
This chapter shows how to install and customize Alcatel-Lucent Network Management Subsystems on
a HP9000 or HP Integrity system included in the supported hardware configurations defined respectively
in paragraph 2.2.1.1 “Check HP9000TM Hardware Configuration" at page 44 and in the paragraph 2.2.1.2
“Check HP Integrity Hardware Configuration" at page 46.
For upgrade or migration refer to 1350 Management Suite Upgrade Guide 8.1 [3]
VERY IMPORTANT!!
Before proceed in the installation, upgrade or migration you have to visit the OND Tech-
nical Excellence Center WEB site (http://tec.ond.alcatel.it/), looking for additional instal-
lation notes. This notes are available within “Network Release" section, selecting:
NR8.1_PL2 -> - installation_notes.
The installation done by following the information provided by this chapter causes the complete removal
of hard disks involved.
The chapter contents:
– Quick Installation - Complete and fast installation.
– Operating System InstallationHP-UXTM 11i for PA-RISC or ITANIUM processors.
– Software Package Predispose- Operating system and third party software predisposal for Alcatel-
Lucent Software installations.
– Operating System Configuration Configure HP-UXTM 11i for communication.
– Install and Customize Alcatel-Lucent Software related data
– Mandatory Installation Changes

Installation and Customization 3AL 89041 BAAA Edition 04 29/200
2.1 Quick Installation
A quick installation guide for speed up the installation task. The current edition of the document provides
information useful for installing the Alcatel-Lucent NMS/NMC HP-UX based software.
Before start with installation it is strong recommended to read the software release notes and
check on the related Product Support Center WEB site for any warning and known problems!
2.1.1 HP-UX Operating System Installation

The HP-UX O.S. installation is requested for new machine or systems installed before NR8.
NOTE: The HP-UX installation delete the entire disk contents.
NOTE: For HP Integrity servers equipped with P400 Smart Array it is MANDATORY execute
the ”P400 SmartArray Configuration” 2.2.3.2.1 page 53.
– Insert media:
• “SWP-OSCONF_BOOT-V7.1.2” (1/1 for DVD, 1/2 for CD media) for PA-RISC architecture
• “SWP-OSCONFUX_BOOT-V8.1.2” DVD for ITANIUM architecture
in the driver.
– Boot or reboot the system from CD/DVD.
– Reply the question issued:
• Enter the timezone of your geographic area.
• Check the current system time and change it when needed.
• Enter the hostname
NOTE: it is strongly recommended to use ONLY alphabetical lowercase characters
and numerical digits - do NOT use uppercase or special characters.
• Enter IP address
• Enter the default gateway and subnetwork mask when they are present.
NOTE: the procedure check default gateway executing a ping
• Enter the memory size to be used for swap area configuration, you can leave the default value.
• Enter CD-ROM device to be used as default source media, you can leave the default value
• Choose to install and configure mirrored disks only if there is the related license.
• Choose primary boot disk in the provided list,
NOTE: In some cases more than one disk can be required.
• When the mirror disk has been selected, also the alternate boot disk will be required.
• Keyboard type choosing from the shown list.
The system will perform the requested activities in unattended mode. Wait the end of installation, it can
take from 30 up to 90 minutes. When the system will prompt you for logging, log in as “root" and check
in /SCINSTALL/scinstall.log for any error before proceed.
For more information see at Chapter 2.2 at page 44.

30/200 3AL 89041 BAAA Edition 04 Installation and Customization
2.1.2 System Predisposal
When the HP-UX operating system installation is completed proceed with the system predisposal as
shown in the following.
2.1.2.1 OS-Conf Engine and 3PP Description installation from Medium.
First of all you have to install OS-Conf Engine and 3PP description.
– Insert:
• In case of HP9000 PA-RISC system:
SWP-OSCONF_ADD-V7.1.2_P03 volume 1/1
• In case of HP Integrity ITANIUM system:
SWP-OSCONFUX_ADD-V8.1.2_P01 volume 1/2
in the driver.
– Mount it by entering the command:
...,sys,root # mount -o rr /dev/dsk/<device name> /SD_CDROM [Enter]
– Install the OS-CONF engine and 3PP description by executing:
...,sys,root # swinstall -s /SD_CDROM OS-CONF OSC-3PP [Enter]
...,sys,root # swinstall -s /SD_CDROM OS-CONF OSC-3PP-UXIA [Enter]
2.1.2.2 OS-Conf Engine and 3PP Description installation from Depot.
First of all you have to install OS-Conf Engine and 3PP description.
– Install the OS-CONF engine and 3PP description by executing:

...,sys,root # swinstall -s <depot hostname>:/alcatel/SCDEPOT \
OS-CONF,r=7.1.2.P03 \
OSC-3PP,r=7.1.2.P03 [Enter]
OS-CONF,r=8.1.2.P01 \
OSC-3PP-UXIA,r=8.1.2.P01 [Enter]
2.1.2.3 Update Platform
Keeping the CD mounted perform the software platform upgrade.
– Start the upgrade procedure by entering:

...,sys,root # /SCINSTALL/etc/scupgrade [Enter]
– The procedure will ask you if the platform upgrade must be perform by CD/DVD (In this case must
be available all the CD’s set) or network depot (In this case must be available a DEPOT already
updated to the correct patch level)
– The procedure will check the amount of free space on the file system, and enlarge them when
needed. Execute the system reboot, if needed.
For more information see at Chapter 2.3.1.3 at page 75.
N.B. In case of installation in upgrade from NR8.1 or previuos, execute, as root, the following com-
mand:
...,sys,root # /SCINSTALL/etc/scJacORBupg OFF [Enter]

2.1.2.4 Install Alcatel-Lucent NMS Software Description and Install Wizard from medium
Then install Alcatel-Lucent NMS Software Description.
– Insert the SWP-1350MS_NR8.1PL2-DR4 volume 1/3 in the driver.

– Mount it by entering the command:
...,sys,root # scmountcd /dev/dsk/<device name> /SD_CDROM[Enter]
=>END: device c0t0d0 mounted on /SD_CDROM, CD/DVD format is cdfs
Install the Alcatel-Lucent NMS Description by executing:
...,sys,root # swinstall -s /SD_CDROM/SWPDESC_V8159.sdpkg \* [Enter]
– Install the Alcatel-Lucent Install Wizard:
...,sys,root # cd /SD_CDROM [Enter]
...,sys,root # sh ./Install_Wizard-R8.4.2 [Enter]
...,sys,root # sh ./Install_Wizard_CMD-R8.4.9 [Enter]
...,sys,root # cd [Enter]
– Dismount the CD and remove it from CD or DVD drive:
...,sys,root # umount /SD_CDROM [Enter]
2.1.2.5 Install NR8 PL2 Installation Procedure and NMS Description from Network Depot
To install NR8 installation procedure from network depot you have to execute the following procedure:
a) Login the system as root user.

b) Install the “Install_Wizard.sh" software from depot machine:
...,sys,root # mkdir -p /alcatel/DEPOT [Enter]
...,sys,root # cd /alcatel/DEPOT [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/Install_Wizard-R8.4.2 . [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/Install_Wizard_CMD-R8.4.9 . [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/SWPDESC_V8159.sdpkg . [Enter]
c) Install the “Install_Wizard" software entering the command:
d) Remove the temporary file:
...,sys,root # rm /alcatel/DEPOT/Install_Wizard-R8.4.2 [Enter]
...,sys,root # rm /alcatel/DEPOT/Install_Wizard_CMD-R8.4.9 [Enter]
e) Install the NMS description by entering the command:
...,sys,root # swinstall -s /alcatel/DEPOT/SWPDESC_V8159.sdpkg \* [Enter]
2.1.2.6 Mandatory Install Wizard W/A
Apply the following W/A, by executing (as root) the commands listed above:
...,sys,root # cd /alcatel/Install_Wizard/products/OS-KERNEL [Enter]

...,sys,root # cd OS-KERNEL_7.1.2-P19.5/data/TSDnm58636 [Enter]
...,sys,root # cp -p crdb_phase3 crdb_phase3.orig [Enter]
...,sys,root # dos2ux crdb_phase3.orig > crdb_phase3 [Enter]
2.1.2.7 Create Software Depot
If you have to install many systems, you have now the opportunity to create a software depot that allow
you to proceed in the installation without swap CD from a machine to the other, refer to paragraph 2.3.3
at page 79 and 1350 Rel 8.1 Administration Guide [2]

2.1.2.8 Run System Predisposal
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.
Now you can start the predisposal by running “scmanageswp" as shown hereafter:
– Login the system as “root"
– Enter the command:
...,sys,root # scmanageswp
• On the "SWP MAIN MENU" choose: 1 [Enter]Predispose new SWP

• On the next one: 2 Predispose from Descriptors installed on the system.
• The list of software available for predispose will be shown, select the item you want to predis-
pose for by referring the column identified by <Product> S.
• When all of them have been selected, enter “q[Enter]" until you do not get to the “SWP MAIN
MENU".
• On the “SWP MAIN MENU" choose:4 [Enter]Create new SWP INSTANCE.
A list will be shown with the software that foreseen an instance.
• You have now to create the data instance for the software by choosing the items from the list,
but considering the following rules:
– Create the OS-Kernel Global Instance.
– Create the NMS Instances Master and/or Presentation, taking also into account the func-
tional dependencies shown in paragraphs 1.2.7 and 1.2.8 at page 26.
• For each instance selected, a set of questions will be issued (for more info refer to paragraph
“Predispose for Installing" 2.3.7 at page 84):
– Choose one of the possible instance foreseen for the software show as a list.
– Enter the Instance number for identification.
NOTE: The instance identifier have to be defined in a plan, and be unique for the
Master instances.
NOTE: The presentation instance number must be equal to the related master!
NOTE: The spare instance number must be equal to related Master (1359HA Data
Sharing only).
NOTE: Remember the instance number, because it has to be entered again later.
NOTE: For NMS Cohosted with 1359HA, create the client file system for the NMS
lower layers (refer to “Network Management Sub-System Functional Dependen-
cies" paragraph 1.2.7 at page 25 for architecture, and to “1359HA Post Predisposal"
paragraph 2.3.8 page 100 for more information).
– Enter “no" at the question related to the multiple volume group configuration.
– Confirm your choice only if the data enter is correct.
• When all the foreseen software data instance have been declared, enter “q[Enter]" until you do
not get to the “SWP MAIN MENU".
• At the “SWP MAIN MENU" prompt enter:a [Enter] Apply
• The list of the pending action will be shown, if everything is correct enter: a [Enter] to start the
predisposal.
• The procedure will compute the system requirements in terms of disk space, and it can ask you
for add unused available disks to the current configuration (see paragraph 2.3.7.6.3 at page 96
for more info).
• Then, it will ask you for the third party software, you can choose to retrieve it from depot (if any)
or from CD ( see paragraph 2.3.7.6.1 at page 95 for more information).
• Enter your choice and provide:
– The CD device file or simply confirm the default.

– The depot location <hostname>:/<depot directory>
• Then the procedure will show you just some trace, asking you sometimes to press enter to con-
tinue.
• After the following message you have to press [Enter] key to perform the system reboot:
=>>> WARNING: Now SCINSTALL will be invoked to activate the mod...
The installation will run unattended !!!
Press [Enter] to continue.
***** The system reboots automatically, please wait *****

• If you are installing from depot the procedure will proceed unattended. If you are installing with
CD, the request of the medium will be issued in console issuing a message that reports the CD
label.

2.1.3 HP-UX Operating System Configuration
At this step you have to perform these system configurations:
– Configure the /etc/hosts.
– Configure NTP protocol.
– Configure license manager.
2.1.3.1 Configure /etc/hosts

You have to enter in /etc/hosts file two information for any machine this system have to communicate with:
IP address and name. The machine you have to include are:
– Hosts involved in TNM application.
– Printers
– Licences management systems.
– Time synchronization systems.
Refer to paragraph 2.4.1 at page 102 for more information.
2.1.3.2 Configure NTP

The NTP configuration foresees to know the time reference systems in the network, because the NTP con-
figuration foresees many possible scenarios see at paragraph 2.4.2 at page 104 for more information.
Hereafter are shown the two most useful configurations for the current system, it can receive (client) or
distribute (server) time reference clock.
2.1.3.2.1 Configure as NTP Client

To configure your machine as NTP client, login the system as “root" user and execute “scxntp" this way:
a) Enter “1" at “OS-Conf xntp Protocol Configuration" menu prompt to “Add a new NTP server".
b) Enter the time server host name (if defined in /etc/hosts) or IP address.
c) Set it as preferred.
If you have more than one time server, execute again a) and b), but do not set the second as preferred.
d) Enter “9" at “OS-Conf xntp Protocol Configuration" menu prompt to “Align the time to server".
e) Enter “8" at “OS-Conf xntp Protocol Configuration" menu prompt to “Start/Stop NTP server".
f) If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter “y“ to configure NTP daemon to start automatically at system start-up.
g) Start the NTP daemon replaying with “y[Enter]" to message:
NTP server is stop
Would you like to start it (y/n) ?
h) Exit by entering “e[Enter]" at “OS-Conf xntp Protocol Configuration" menu prompt.
2.1.3.2.2 Configure as NTP Server

If you do not have any external time source, you can configure your machine as NTP server, login the sys-
tem as “root" user and execute “scxntp" this way:
a) Enter “5" at “OS-Conf xntp Protocol Configuration" menu prompt to “Configure NTP on local clock".
b) Enter “y[Enter]" at the question:
Would you like to set Local Clock as preferred source (y/n) ?
c) Enter “8" at “OS-Conf xntp Protocol Configuration" menu prompt to “Start/Stop NTP server".
d) If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter “y“ to configure NTP daemon to start automatically at system start-up.
e) Start the NTP daemon replaying with “y[Enter]" to message:
NTP server is stop
Would you like to start it (y/n) ?
f) Exit by entering “e[Enter]" at “OS-Conf xntp Protocol Configuration" menu prompt.

2.1.3.3 Configure License
To be able to run software you have to authorize the execution by registering licence keys. There are two
kind of license: Alcatel-Lucent for network management software and GraphOn X emulation.
Both license keys have the same two phases approach: the license request and the license set up. The
former have to be done for the entire network management system. The latter for every machine.
2.1.3.3.1 License request
To be able to configure the licence you have to define the license server machines by following these rules:
– If you have a network management with up to two HP9000 or HP Integrity systems, you have to
define one of them as license server, and ask for a single node license.
– If you have three or more systems, you have to choose three of them and ask for a three server
redundant license.
N.B. The licenses have to be requested for the entire system.
N.B. The licenses have to refer to the license server host identifier and NOT to the server
where the application have to be run on.
For each license server you have to retrieve the system host identifier by entering:
For Alcatel-Lucent license: ...,sys,root # /opt/poseidon/bin/lmhostid [Enter]

For GraphOn license: ...,sys,root # /opt/graphon/bin/lmhostid [Enter]
The shown “host id" have to be provided during the license request, for the three server redundant con-
figuration all three “host id" have to be provided at once.
For TMN the request must be performed by Alcatel-Lucent personal to http://nmfactory.ond.alcatel.it/

For GOGlobal-UX can be requested to http://www.graphon.com/
Retrieve the license file, and edit it by adding the port number 27000 at the end of each “SERVER" line
in the Alcatel-Lucent license file, instead 27001 in the GraphOn GoGlobal-UX one.
2.1.3.3.2 Alcatel-Lucent License Set-up
Store the license file into the file /opt/poseidon/etc/license.dat of any machine.
Verify the license server are correctly declared within /etc/hosts file.
Start the license daemon on any machine by entering the command:
...,sys,root # /sbin/init.d/poseidon stop [Enter]

...,sys,root # /sbin/init.d/poseidon start [Enter]
2.1.3.3.3 GraphOn GoGlobal-UX License Set-up
Store the license file into the file /opt/graphon/etc/license.dat of license server machines, create
file /opt/graphon/etc/license.dat with a line like the following for each license server:
SERVER <hostname> 27001
Copy this file in the same location of each NMS machine.

Verify the license server are correctly declared within /etc/hosts file.
Start the license daemon on any machine by entering the command, on each machine.
...,sys,root # /sbin/init.d/goglobalux stop [Enter]

...,sys,root # /sbin/init.d/goglobalux start [Enter]

2.1.3.3.4 Check the license server
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat [Enter]

2.1.4 Install and Customize Alcatel-Lucent Software
Finally you are ready to install and customize the Alcatel-Lucent software on the target system. This activ-
ity is performed by the Alcatel-Lucent Install Wizard.
Install Wizard tool supports the full Network Management software installation on one machine, by per-
forming automatically the following steps:
- detection of the SWP instances currently predisposed;

- installation of all the software related to the SWP instances detected during the previous step;
- customization for all the SWP instances detected during the previous step.
N.B. Before start check if you have the necessary CD/DVD or software depot with the entire soft-
ware.
N.B. Check if local system is correctly authorized to access the files (see 2.3.5.2 and 2.3.5.3 for more
informations).
2.1.4.1 Automatic Install and Customize NMS and NMC
Automatic Install MUST NOT used if the system has also the 1359HA protection.
– Login the system as root user with a graphical session.
...,sys,root # cd /alcatel/Install_Wizard [Enter]
– Start the automatic installation procedure by executing:
• From CD/DVD-Rom:
Insert DVD “SWP-1350MS_NR8.1PL2-DR4" volume 1/3 in the driver.
N.B. If a different media is present in the drive the installation can fail!
Mount media at /SD_CDROM directory:

...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM [Enter]
...,sys,root # ./Install.sh -Install_All -cdrom [Enter]
• From DEPOT:
...,sys,root # ./Install.sh -Install_All -fast [Enter]
N.B. -fast and -cdrom option are not compatible..
N.B. Automatically NMC install is NOT supported if installing from CDROM. If you have, you
must install it manually.
The parameter (-fast) is optional and, if present, will cause the procedure to install and to customize
different software (e.g.: OS-KERNEL, 1353NM, 1354RM, ...) in parallel, in order to have a fast instal-
lation. Therefore, this option is useful when:
– more than one product must be installed on the same machine;

– more than one instance must be customized on the same machine.

The procedure will ask you for Depot hostname and address. A different installation shell will be auto-
matically started, one for NMS predisposed, with different colours like showing in the following window:
Figure 6. GoGlobal-UX Logo
The procedure will ask you for the all NMC that you want install (1359HA, 1359IOO,1359ISN, ETH-
MEDIATOR). Select for those ones are present in your system.
The procedure start the installation.
During the procedure execution, the Custom GUI will be automatically started, already loaded with
default data related to the instance(s) being customized: Apply and Exit the data on the window(s).
At the end of the procedure, you will be asked to press Enter in order to update the GO-Global UX
configuration: once Enter will be pressed, all the GO-Global UX sessions will be stopped
(included the one running the procedure).
Then complete the GO-Global UX configuration by executing:
– Login the system as root user but do not execute this instruction using GO-Global UX interface:
...,sys,root # . /alcatel/Kernel/env/Kernel [Enter]

...,sys,root # /alcatel/Kernel/script/XTEmulatorConfigure.pl KernelCustomize [Enter]
The procedure will ask you to authorize the Go-Global UX environment shutdown.
GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no)
Reply the question with “yes[Enter]".
N.B. Do not interrupt the procedure!

– When the procedure will be terminated, verify that no error are shown (warnings can be ignored)
by examining the following files:
/alcatel/Install_Wizard/log/Installation_Install_All_#.log
/alcatel/Install_Wizard/log/Installation_<NMS/NMC>_#.log
/alcatel/Kernel/maintenance/trace/Custom.trace
/alcatel/Kernel/maintenance/log/Custom.log
At the end of the procedure, you will be execute the System Configuration (for all customized Master
instances) and then integrate instances (see paragraph 2.1.5 and 2.1.6 in the following).
2.1.4.2 Manual Install and Customize NMS and NMC

The product installation and customization process has been unified in NR8, with some little differences
mentioned when needed. For more detailed information refer to paragraphs: 2.5.3 at page 121 and 2.5.2.1
at page 116.
Hereafter the product list manageable this way.
Table 5. NR8.1 PL2 NMS/NMC table
NMS/NMC Name Version Description
1353NM 7.4.5.3 Network Element Manager
1354BM ATM 7.1.4.2 ATM Manager
1354BM ETH 8.1.5.3 Broadband Ethernet Manager
1354BM PR 8.1.6.44 Broadband Packet Ring Manager
1354RM 7.5.0.1 Regional Manager
1354SY 8.0.0.2 Synchronization Manager
1355VPN 6.1.2.2 VPN Virtual Protector Network
1359HA 8.0.0.13 High Availability Operating System
1359IOO 5.4.0.4 Generic O.S. - O.S. Interface
1359ISN 5.1.3.9 ISN Open Interface
ETH-MEDIATOR 1.2.8.1.2.S75 1354BM Ethernet to 1354RM Mediator Function
1353NM (*) 7.3 (7.3.6) Network Element Manager
(*) The 1353NM 7.3 can be install only on PA-RISC Machine.

N.B. The NMS and NMC installation and customization have to be executed with graphical
interface.
– Login the system with graphical interface as root user.

– Change directory: ...,sys,root # cd /alcatel/Install_Wizard [Enter]
– Install and customize the designed software package (NMS/NMC) by entering:
• From CDROM:
– Insert DVD “SWP-1350MS_NR8.1PL2-DR4" volume 1/3 in the driver.

...,sys,root # ./Install.sh <NMS/NMC Name> -cdrom [Enter]
– Provide the CD on demand.
• From depot:
...,sys,root # ./Install.sh <NMS/NMC Name> [Enter]
– Provide the host name or IP Address of the depot system:
NOTE: Provide DEPOT hostname or address ?
– Provide the directory where the depot is located on depot system:
NOTE: Provide DEPOT PATHNAME [/alcatel/DEPOT] ?
N.B. Do not interrupt the procedure!
– 1353NM Only: The 1353NM installation will require you to confirm the installation of the 1353SH 5
and 6 interface feature (see paragraph 2.5.3 at page 121 for more information):
NOTE: Do you want to execute 1353NM Install package to manage NR5/6

1353SH? [y|n|q]
– Once installation phase will be completed, the procedure will request a confirm for the execution of
the customization tool, confirm the operation.
– The Custom interface will show you the “System Instances List" window, you have to select
“Choose_one" button and set it to “New-Instance", then “Apply & exit" in the Actions menu.
– The custom “Parameters Definition" window will be shown on the screen, it allows you to set the rel-
evant NMS/NMC variables.
– Set the value, then “Apply & exit" in the Actions menu to start the execution.
– 1353NM Only: An additional window will be shown to select an Element Manager subset (see
2.5.3.2 a page 124 for more information).
– When the procedure will be terminated, verify that no error are shown (warnings can be ignored).
– Check also /alcatel/Install_Wizard/log/Installation_<NMS/NMC Name>_*.log trace file.
2.1.4.2.1 Customize Multiple NMS Instance
The installation procedure is combined with the first instance customization of just installed software, this
usually covers the installation process. Some NMS/NMC foresees to have more than one instance, in this
case you have to execute again the Customization process for each of them without the first one.
– Start customize process entering the command:

...,sys,root # cd /alcatel/Install_Wizard[Enter]
...,sys,root # ./Install.sh -custom <NMS/NMC Name> [Enter]
– Then at the “System Instances List" window, you have to select “Choose_one" button and set it to
“New-Instance, then “Apply & exit" in the Actions menu.
– The custom “Parameters Definition" window will be shown on the screen, set the relevant for the
next instance of NMS/NMC.
– “Apply & exit" in the Actions menu to start the execution.
Repeat these steps for each instance.

2.1.5 Proceed in the Process Configuration
Now you have to proceed with the specific NMS/NMC configuration, refer to the NMS/NMC specific
administration guide.
When the configuration of the current system will be performed, you can proceed with the installation, cus-
tomization and configuration of the next machine.
When all TMN systems will be installed, customized, configured, and connected via TCP/IP, you can pro-
ceed with the integration.
2.1.6 Final Integration

When all TNM machines have been configured in stand-alone, you have to run on each one of them the
final integration script.
...,sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl [Enter]
For each system that have to be integrated the following question can be issued (for example):
1354RM_3-7.4.9: Run the Integration of 1353NM_1-7.4.5? [y/n]
If you reply “y" the system will be integrated, and the procedure will issue also these other questions:
1354RM_3-7.4.9: Run the PLT Integration of 1353NM_1-7.4.5? [y/n]

1354RM_3-7.4.9: Run the Backup/Restore Integration of [y/n]
1354RM_3-7.4.9: Run the Navigation Integration of 1353NM_1-7.4.5 [y/n]
Reply “y" to all of them.
Warning and error messages will advice you that the remote system is not reachable or not properly con-
figured, and the machine will be not integrated. If such kind of message are issued, identify the problem,
fix it, and run again the integration script.
Example:
WARNING: 1354RM_3-7.4.9: Connection problems with <hostname>. Skipping Update.
When the procedure will be successfully executed, you will be able to use all the Network Management
System features.
2.1.6.1 Integration when there is a 1354BM ETH Master
In case of a 1354BM-ETH Master that has to be integrated with a 1354RM, do not integrate PLT and
Backup/Restore (SMF) when requested.
Here is an example :
...
NOTE: 1354RM_1-7.4.9: Master-Master Communication Integration (PLT) of 1354BMETH_1-8.1.5 can be
performed...
1354RM_1-7.4.9: Run the PLT Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]
NOTE: 1354RM_1-7.4.9: Backup/Restore Integration (SMF) of 1354BMETH_1-8.1.5 can be performed...
1354RM_1-7.4.9: Run the Backup/Restore Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]

2.1.6.2 Integration when there is a 1354BM PR Master
In case of a 1354BM-PR Master that has to be integrated with a 1354RM or 1353NM, do not integrate
PLT and Backup/Restore (SMF) when requested. Here is an example:
...
NOTE: 1354RM_1-7.4.9: Master-Master Communication Integration (PLT) of 1354BMPR_1-8.1.6 can be
performed...
1354RM_1-7.4.9: Run the PLT Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]
NOTE: 1354RM_1-7.4.9: Backup/Restore Integration (SMF) of 1354BMPR_1-8.1.6 can be performed...
1354RM_1-7.4.9: Run the Backup/Restore Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]
...
NOTE: 1353NM_1-7.4.5: Master-Master Communication Integration (PLT) of 1354BMPR_1-8.1.6 can be
performed...
1353NM_1-7.4.5: Run the PLT Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]
NOTE: 1353NM_1-7.4.5: Backup/Restore Integration (SMF) of 1354BMPR_1-8.1.6 can be performed...
1353NM_1-7.4.5: Run the Backup/Restore Integration of 1354BMETH_1-8.1.5? [y/n] n [Enter]

2.2 Operating System Installation
This chapter describes the first part of initial installation, it explains how to perform a HP-UX 11i Operating
System installation.
N.B. NEVER EXECUTE IT ON A SYSTEM IN SERVICE.

The activity deletes the entire contents of the hard disk involved.
Before start with installation it is strong recommended to read the software release notes and check
on the related Product Support Center WEB site for any warning and known problems!
2.2.1 Preparatory activities

Before proceeding in the HP-UX 11i installation it is advisable to prepare all the hardware and software
components for the installation.
– Check the system hardware configuration

– Check the cable connections
– Operating System Configuration data
2.2.1.1 Check HP9000TM Hardware Configuration
This paragraph shows the HP hardware where the OS-Conf has been validated. The correct behavior of
the procedure on different hardware is not guarantee.
Table 6. List of supported hardware components:
HP9000 Model Optional Cards
Server R380 - R390 A5220A HP9000 DVD ROM Device

A4107A FWD SCSI-2 Controller
J3516A HSC FF 100BaseX Dual Port LAN Adptr
A3312AZ HA Factory Racked Storage Enclosure
Server K360 - K370 - K380 A5220A HP9000 DVD ROM Device

A4107A FWD SCSI-2 Controller
J3516A HSC FF 100BaseX Dual Port LAN Adptr
A3312AZ HA Factory Racked Storage Enclosure
28696A HP-PB FWD SCSI-2 host adapter
Server L1000 - L2000 A5557A DVD ROM Device for L-Class systems
A5230A PCI 100Base-T LAN Adapter
C6364A SMART Desktop SE DDS3 DAT module
C5708A DDS 3 Data Cartridge, 24GB/125m
Server RP2430 A5230A PCI 100Base-T LAN Adapter

C4314A SMART Desktop DVD-ROM module

HP9000 Model Optional Cards
Server N4000 A5838A PCI 2 Port 100Base-T 2 Port Ultra2 SCSI

A5272AZ SureStore E Disk System SC10
C4318SZ SMART Family Full Height Enclosure
Opt. 108DVD-ROM Drive Factory Racked
C6365A SMART SE DDS-3 DAT Drive, field racked
A4800A PCI FWD SCSI-2 card for HP9000 Server
C6379A SMART Field Integrated DLT 8000 module
A6795A PCI 2GB FIber Channel Adapter
A6250AZ Disk System 2405 Factory Rack
A7295AZ VA 7110 Dual Cntl,512MB Cache Fact Inst
Server RP5430 A5557A DVD ROM Device for HP Svr rp54X0 systems
A5230A PCI 10/100Base-T LAN Adptr for rp24X0
A5557A DVD ROM Device for HP Svr rp54X0 systems
C5687B HP SureStore DAT40e 40GB Ext UNIX comp
Server RP7400 A5838A PCI 2 Port 100Base-T 2 Port Ultra2 SCSI

A5272AZ SureStore E Disk Sys SC10 Factory Rack
C7508AZ HP SureStore Tape Array 5300 (factory)
C7499A HP SureStore DVD-ROM Array Module
Server RP7410 A5838A PCI 2 Port 100Base-T 2 Port Ultra2 SCSI

A5272AZ SureStore E Disk Sys SC10 Factory Rack
C7498A HP DAT 24m Array Module
C7456A HP DLT 80m Array Module
C7499A HP SureStore DVD-ROM Array Module
Server RP3410 C5687C HP DAT 40 External Tape Drive

A9919A HP server DVD-ROM drive, Slimline
Server RP3440 C5687C HP DAT 40 External Tape Drive

A9919A HP server DVD-ROM drive, Slimline
Server RP4440 A7163A DVD drive (read only) for 4U chassis

A5230A PCI 10/100Base-T LAN Adptr
The HP9000 server cable connections are shown in APPENDIX Appendix D at page 183.

2.2.1.2 Check HP IntegrityTM Hardware Configuration
This paragraph shows the HP hardware where the OS-Conf has been validated. The correct behavior of
the procedure on different hardware is not guarantee.
N.B. HP IntegrityTM equipped with Itanium 2© Montvale family must be installed using OS-
ConfUX 8.1.2.
Table 7. List of supported hardware components:
HP Integrity Model Server Optional Cards
rx2660 AB545A HP PCI-X 4-port 1000Base-T Gigabit Adapter

A7173A HP Dual Channel Ultra320 SCSI Adapter
Q1522B HP StorageWorks DAT 72 Internal Drive
C5687D HP StorageWorks DAT 40 Ext Tape Drive
AB290A HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr
AD248A HP rx2660 Internal RAID1 Controller

A7012A PCI-X 2 port 1000Base-T Gigabit Adptr
AB036B HP Core IO Smart Array Control (P400) RAID1

A7012A PCI-X 2 port 1000Base-T Gigabit Adptr

2.2.1.3 Operating System Configuration Data
To be able to carry out the operation system installation you have to know some information. The following
form can be helpful to prepare this data in advance:
The Hostname must contain only numbers and alphabetic characters in lower case,
starting with an alphabetic character.
Upper case and special characters are FORBIDDEN!
OPERATING SYSTEM BASIC DATA
IP Address:_____._____._____._____Hostname:____________________________
TimeZone:_______________________
Gateway Address:_____._____._____._____Subnet Mask:_____._____._____.______
Core Memory Size:________________Source Device:/dev/dsk/________________
Mirror Disk Option: - Yes - No (Choose no when on HP Integrity equipped with P400 Smart Array)
Command View SDM: - Yes - No
System Boot disk: /dev/dsk/___________Alternate Boot Disk: /dev/dsk/___________
N.B. The items shown in bold are required.
IP Address, Gateway Address, Subnetmask and Hostname must be defined in agreement with the Cus-
tomer TCP/IP addressing plan. Be careful with IP Address and Hostname, because it can be some times
impossible to change them later.
Timezone is usually the time zone where the system is located and the definition is simplified by the menu
that shows you the possible areas. Do not define the local time with GMT0 time zone, except if the
system is really located in Greenwich time zone area.
For Core Memory Size it is intended the amount of RAM equipped on the system, it is automatically
detected by the procedure and shown as default choice, you have just to confirm if the shown value is
correct.
Mirror Disk/UXTM and The CommandView SDMTM are HP software that can be installed on demand. Both
of them are available only for 64bit processor and can be installed only if the Customer had bought the
license. The installation of these software is forbidden on system where there is no evidence of the
related license royalties to HPTM.
Source Device means the CD-ROM or DVD-ROM device will be used to retrieve the software. It is auto-
matically detected by the procedure.
The last information requested is related to the disks. The System Boot disk is the hard disk on which HP-
UXTM will be installed on. If the Mirror Disk/UXTM as been requested, the procedure will issue also the
request for the alternate boot disk.
HP-UXTM 11i required at least eight Gbyte with a machine with up to one Gbyte of RAM, the operating
system can be stored in two four Gbyte disks.

2.2.2 Installing HP-UX 11i
The HP-UX operating system is the first software installed on a new system, this task is performed by using
the appropriate OS-Conf bootable CD/DVD for HP 9000 or HP Integrity processor. The operations of
installation of the two systems are pratically identical, are only different for few details.
The following list summarizes the actions performed during the operating system installation:
1) Boot from bootable disk (different approach).

2) SmartArray P400 configuration (only with HP Integrity machine)
3) HP-UXTM Basic configuration information data entry in the order:
– Time zone of the system via selection menu.
– Hostname
– IP address
– Subnetmask & Gateway
– DNS Server IP address installation option (only with HP Integrity machine)
– Core memory size
– Hardware scanning
– Mirror/Disk UXTM Software installation option
– Virtual Array Command installation option (only with HP 9000 machine)
– System Boot disk selection.
– Alternate Boot disk selection (2)
– Keyboard selection (only with HP Integrity)
4) The Boot disk(s) will be initialized.
5) All the file systems and swap areas will be created
6) The Operating System will be installed on the selected boot disk.
7) The optional software will be automatically installed, if any.
8) The Mirror Disk/UXTM will be configured, if selected.
9) The GoGlobal-UXTM and OS-Conf software will be installed.
(2)The Alternate Boot disk is asked only when the Mirror/Disk UXTM has been selected.
In the following always will specify difference between HP 9000 and HP Integrity, otherwise the paragraph
is valid for both.

2.2.3 Boot the machine
Power on the HP system. If your system is active, simply power off and power on it again.
The machine automatically starts up, issuing some different messages in case HP 9000 and HP Integrity.
2.2.3.1 Boot with HP 9000 PA-RISC processor
Wait until the following message appears on the screen:
To discontinue, press any key within 10 seconds
and press any key to interrupt the boot sequence.
The "Main Menu" menu will be shown on the display.
Find the id of the driver, entering the “search" command:
Main Menu: Enter command or menu > search [Enter]
You have to identify the medium driver that you want to use in the provided device list.
This is an example for server:
Path NumberDevice PathDevice Path(mnem)Device Type
P0 10/0.6 SESCSI.2.0Random access media

P1 10/12/5.3 FWSCSI.6.0Random access media
P2 10/12/6.0 FWSCSI.5.0Lan Module
N.B. The driver is usually connected to SCSI Single Ended Target 2 (SESCSI.2.0).
This is an example of another modality to display the devices for the 64bit series server:
Path Number Device Path(dec)Device Type
P0 8/4.9 Random access media

P1 8/4.8 Random access media
P2 8/16/5.6 Random access media
P3 8/16/5.2 Random access media
P4 8/16/6.0 Lan Module
N.B. In this case, the driver is connected to SCSI Single Ended Target 2 (8/16/5.2).
Insert the bootable SWP-OSCONF_BOOT-V7.1.2 (1/1 for DVD or 1/2 for CD-ROM) into the driver.
When the LED of the CD-ROM device stops blinking, boot by entering the “boot" command:
Main Menu: Enter command or menu > boot P<n> [Enter]
where “P<n>“ is the path number corresponding at the driver.

The system asks you if you want to perform an interactive boot, reply as shown below:
Interact with IPL (Y, N, or Cancel)?> n [Enter]
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
ISL Revision A.00.43 Apr 12, 2000
ISL booting hpux (;0): INSTALL
Boot
...
The system shows you the start of boot with the following message:
_ ALCATEL INSTALLATION PROCEDURE

OS-CONF Technology
__________________________________________________________________________
__________________________________________________________________________

2.2.3.2 Boot with HP Integrity processor
HP Integrity servers rx2660 and rx6600 can be equipped with a P400 Smart Array disk
controller. This controller MUST BE PROPERLY CONFIGURED for 1350OMS through
ORCA (Option ROM Configuration for Array) utility during boot sequence.
Wait until the following message appears on the screen:
_______________________________________________________________________________
EFI Boot Manager ver 2.00 [14.62]
OS might use inly the primary console set via boot manager or concongif command
/----------------------------------\
/----------------------------------\ | System Overview |
| Boot Menu | | hp server rx2660 |
| HP-UX Primary Boot: 0/1/1/0.... | | Serial #: DEH473324X |
| iLO Virtual Media | | |
| Core LAN A | | System Firmware: 1.05 [4645] |
| Core LAN B | | BMC Version: 5.06 |
| EFI Shell [Built-in] | | MP Version: F.01.58 |
| Internal Bootable DVD | | Installed Memory: 8192 MB |
| -------------------------------- | | |
| Boot Configuration | | CPU Logical |
| System Configuration | | Module CPUs Speed Status |
| Security Configuration | | 0 2 1.6GHz Active |
| | | |
\----------------------------------/ | |
| |
| |
\----------------------------------/
Use ^ and v to change option(s). Use Enter to select an option
Insert the bootable: DVD SWP-OSCONFUX_BOOT-V8.1.2 into the driver.
Select the “Internal Bootable DVD” option and press [Enter]
If a P400 Smart Array is present the following messagge will show:
HP Smart Array P400 Controller (version 2.08) 4 Logical Drives
Press <F8> to run the Option ROM Configuration for Arrays Utility
Press <ESC> to skip configuration and continue
It is very important to be ready to press <ESC>+8 (or <F8>) to be able to configure the
Smart Array, you have just 10 seconds before the message disappears.
Execute the actions describe in the paragraph 2.2.3.2.1.

After Smart Array Configuration the boot sequence continue. The system shows you the start of boot with
the following message:
Loading.: Internal Bootable DVD

Starting: Internal Bootable DVD
(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.028

Press Any Key to interrupt Autoboot
\EFI\BOOT\AUTO ==> boot :IINSTALL
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 16363 MB
loading section 0
............................
............................
ALCATEL BOOTMEDIUM (24-Jan-03) for HP-UX B.11.23 ia64
(c) Copyright 2003 Alcatel-Lucent
Alcatel-Lucent INSTALLATION PROCEDURE

OS-CONF Technology
_______________________________________________________________________________
_______________________________________________________________________________

2.2.3.2.1 P400 SmartArray Configuration
HP Smart Array controller implements many RAID disk protections at controller level, the suggested con-
figuration for 1350OMS is: RAID 1 using available hard disks in couple (bay: 8 and 7, 6 and 5, ect.).
The Smart Array disk configuration MUST be done before proceed in the hp-ux instal-
lation. It doesn’t allow chages without loosing the disk contents!
To configure you can use “Smart Array Option ROM Configuration for Array” (ORCA) during the server
boot. You have to wait until the following message appear in console:
HP Smart Array P400 Controller (version 2.08) 4 Logical Drives
Press <F8> to run the Option ROM Configuration for Arrays Utility
Press <ESC> to skip configuration and continue
And press <F8> button in 5 seconds.

ORCA utility allows configuring the physical disks into logical drive with RAID 1 protection level.
The following window will be show:
N.B. The terminal size must be set at least 25 rows and 80 colums otherwise the informations
are not correctly displayed.
Figure 7. Smart Array Main Menu Configuration window
First of all check the current configuration moving the cursor on "View Logical Drive" and press [Enter].
The recommended configuration foreseens three or four logical drive, where possible in RAID 1 config-
uration.

The following picture shows the expected configuration for a system with 6x146GB hard disks:
Figure 8. Smart Array View Configuration window
The configuration with 8x146GB will have one more line.

If you don’t have one of the reccomanded logical drive configuration, you have to remove any existing con-
figuration (see “How to delete a Smart Array Logical Drive”), and set-up one corresponding to the available
hard disk number.
2.2.3.2.1.1 Smart Array Configuration Rule
Hereafter the rules for Smart Array configuration:
a) Create logical drive in RAID 1+0 configuration made up two physical drive.
b) Start the logical drive creation from the higher bay numbers.
2.2.3.2.1.2 Create RAID 1+0 Logical Drive
To create new Logical Drive, staring from ORCA main menu shown at Figure 7., you have to select “Create
Logical Drive” and press [Enter].

The following window will be display:
Figure 9. Smart Array Create window - 1
You have deselect all drive but disk pair candidate to be configured in the logical volume you are creating,
so you have to move the cursor on the disks that have to be excluded, and press <Space bar> each time
(removing the X mark from the selection box), the RAID will be automatically moved to RAID 1+0.
Be careful, there is no way to force the Logical Drive number, it will be assigned automatically
as the lowest available.
Press [Enter] to confirm. The following window will be display:
Figure 10. Smart Array Create window - 2
Press <Esc>+3 (or <F3>) to confirm, then press [Enter] to return to main menu.
Repeat all the same operations to configure all disks equippe. Then press <Esc> to exit to Smart Array
configuration, the system will return to the BOOT sequence.

2.2.3.2.1.3 How to delete a Smart Array Logical Drive
Starting from the menu show at Figure 7., move the cursor on "Delete Logical Drive" and press [Enter].
Do not execute this paragraph instructions if you are not sure that the sistem have to
be installed from scratch.
The logical drive deletion destrois the entore disk contents.
The list of available Logical Drive will be shown:
Figure 11. Smart Array Delete window - 1
Move the cursor on the Logical Drive you want to delete and press <Esc>+8 (or <F8>) to start the delete
action. The following window will show:
Figure 12. Smart Array Delete window - 2
Press <Esc>+3 (or <F3>) to confirm, then press [Enter] to return to main menu.

2.2.4 Time Zone Selection
To allow the set up of time zone and time of the system related to the geographical location of the machine
the program issues a sequence of menu, choose the time zone appropriate for the country where the
machine will be operative.
In the following an example shows how to set the Middle European Time - Daylight Saving Time (MET-
DST), if you are not in the middle European area you have to choose your timezone:
At the first question you have to enter the number of the seven areas of the world:
__________________________________________________________________________
__________________________________________________________________________
The following procedure enables you to set the time zone.
Select your location from the following list:
1) North America or Hawaii
2) Central America
3) South America
4) Europe
5) Africa
6) Asia
7) Australia, New Zealand
___________________________________________________________________________
Enter the number for your location (1-7) then press [Enter] 4 [Enter]
The items of the next question depends by the area chosen in the previous one, for Europe these will be
the following:
___________________________________________________________________________
Select your time zone from the following list:
1) Greenwich Mean Time - British Summer Time
2) Portuguese Winter Time - Portuguese Summer Time
3) Western European Time - Western European Summer Time
4) Middle European Time - Middle European Summer Time
5) Iceland time
6) Turkey, Finland, Romania, Greece, Bulgaria / Summer Time
7) Western Russia (Moscow) - Western Russia Summer Time
8) Unlisted time zone
9) Previous menu
___________________________________________________________________________
Enter the number for your time zone (1 - 9), then press [Enter] 4 [Enter]
The last time zone selection question is the final confirmation:
___________________________________________________________________________
You have selected:
Middle European Time/Summer Time (MET-1METDST).
___________________________________________________________________________
Is this correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
It the choice is correct enter y [Enter], to confirm your selection an go on with the next section.

2.2.5 Time Adjusting
After the time zone definition, it is opportune to review also the machine time and date, for this reason the
program foreseen to issue the following confirmation question:
___________________________________________________________________________
This section enables you to set the system clock.
___________________________________________________________________________
The current system time is Tue Jan 20 10:55:34 MET 2004
Is this correct?
Press [y] for yes or [n] for no, then press [Enter]
If you confirm the time and date, the procedure will proceed with the “Hostname Definition" paragraph
2.2.6 at page 59. Otherwise it will ask you to enter the new date and time issuing the following questions:
___________________________________________________________________________
You will be prompted for the date and time.

Please enter numerically values of month, for example January is 1 or 01.
The values in the parentheses give the acceptable range of responses.
__________________________________________________________________________
Please enter the year (1970-2037) or last two digit, then press [Enter]
Please enter the month (1-12), then press [Enter]
Please enter the date of the month (1-31), then press [Enter]
Please enter the hour (using 24 hour time) (0-23), then press [Enter]
Please enter the minute (0-59), then press [Enter]
Then the new date and time will be shown for another confirmation:
You have entered: Apr 8 10:30:00 MET-1METDST 2003.

This time will be used to reset the system clock.
Is this value correct?
If you confirm the procedure will go on, otherwise it will go back asking again for the date and time.

2.2.6 Hostname Definition
This section of the program ask you to enter the mnemonic name of the machine also known as hostname.
Enter the hostname foreseen for machine following the guide line shown in the instruction:
The Hostname must contain only numbers and alphabetic characters in lower case,
starting with an alphabetic character.
Upper case and special characters are FORBIDDEN!
This section enables you to enter Hostname.

___________________________________________________________________________
For the system to operate correctly, you must assign it a unique
system name or "hostname". The hostname can be a simple name (example: widget)
A simple name must:
* Start and end with a letter or number.
* Contain no more than 8 characters.
* Contain only letters, numbers, underscore (_), or dash (-).

The underscore (_) is not recommended.
NOTE: The hostname should contain 8 characters or less

for compatibility with HP-UX `uname'.
The current hostname is unknown. You cannot configure networking

or run HP-CDE if the hostname is unknown. Please choose another name.
___________________________________________________________________________
Just pressing [Enter] will keep the (not recommended) name "unknown"
Enter the system name [unknown]: hosta[Enter]
Enter the hostname and press [Enter] key, then procedure will ask you to confirm your choice, if you enter
the right name confirm it by entering y [Enter].
You have chosen "hosta" as the name for this system.

Is this correct?

2.2.7 IP Address Set-up
The most important information to be able to connect your system to the Local Area Network (LAN) is the
Internet Protocol (IP) address, you must take care of this information because it is not allowed to have
two nodes on the network with the same IP address. The IP address have to be in agreement with the
LAN administration rules.
This section enables you to enter ip_address.

___________________________________________________________________________
If you wish networking to operate correctly, you must assign the

system a unique Internet Protocol (IP) address. The IP address must:
* Contain 4 numeric components.
* Have a period (.) separating each numeric component.
* Contain numbers between 0 and 255.
For example: 134.32.3.10
Warning: Leading zeros within a component signify an octal number!
If you have not yet obtained an IP address from your local system
administrator, you may use the default address of 127.0.0.1 by
pressing [Enter].
___________________________________________________________________________
Enter your IP address, [127.0.0.1]:
The installation procedure will show you the entered IP address, double check it before confirming it!
You have chosen 192.200.49.3 as the IP address for this system.

Is this correct?

2.2.8 SubNetwork Mask and GateWay set-up
This section allows to define the subnetwork mask and the gateway, these two information are funda-
mental to allow your system to access machines place by outside of your LAN. If your system does not
need to communicate with machines outside your LAN you can skip this section by answering “n" to the
next question. It's also suggested to skip this section if you do not have the subnetwork mask and gateway
information or simply your machine is stand alone.
Even in case your machine is stand alone, it is mandatory to connect the primary lan card to a net-
work hub or switch.
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
This section enables you to specify the subnetwork mask and default
network gateway. This information is necessary if your network has
gateways and you wish to communicate beyond your local subnetwork.
You will need to know the following information:
* Subnetwork mask
* Default gateway IP address

___________________________________________________________________________
Do you wish to specify this information?
In case you do not have the subnet mask and default gateway information available skip this section by
entering n [Enter] and go to paragraph “Swap/Dump Sizing" 2.2.10 at page 64, otherwise enter y[Enter]
and proceed with the following:
___________________________________________________________________________
Enter the subnetwork mask and default gateway information.
Example:
Subnetwork mask: 255.255.255.0
Gateway IP address: 192.200.49.1
Current Settings:
-> Subnetwork mask: 255.255.255.0 (default)

Gateway IP address: 192.200.49.1(default)
___________________________________________________________________________
Enter the new subnetwork mask, [255.255.255.0]:
The default netmask foreseen for the IP address previously assigned to the system, press [Enter] if it is
the right one, or enter a new one followed by [Enter]

The procedure will update the window contents (Current Setting) with new value and it will prompt you
for the gateway address:
___________________________________________________________________________
Example:

Current Settings:

-> Gateway IP address: 192.200.49.1(default)
___________________________________________________________________________
Enter the gateway address [192.200.49.1]:
The procedure shows you a default IP address for the gateway, if it corresponds to the right one, just con-
firm it by pressing [Enter], otherwise enter the correct one and [Enter]
___________________________________________________________________________
Example:

Current Settings:

___________________________________________________________________________
Are the parameters above correct?
Before proceeding with the next step the program shows the entered data asking to confirm them. If you
do not confirm, the procedure goes back to subnetmask data entry.
A ping to the provided gateway is also attempted to verify the correct configuration of both local and gate-
way IP address, and in the mean time the correct subnet mask. If the ping fails the operator will be required
to confirm his/her data entry
.... Waiting, ping system 192.200.49.1

___________________________________________________________________________

2.2.9 DNS Configuration
Meaningful only for HP Integrity machine
Do not configure DNS.
This section allows to configure the Domain Name System for HP–UX_. But the DNS configuration it is
not validated, so it is recommanded to reply no to the following request:
Additional Network Parameters: Domain Name System (DNS)
This section enables you to configure the Domain Name System

or DNS (also known as BIND), which enables this system to query
a DNS server for names and/or addresses of other network systems.
To configure DNS you will need to know the:
* Local domain name
* DNS server IP address
___________________________________________________________________________
Do you wish to specify this information?
You have to enter “n” [Enter].

2.2.10 Core Memory and Swap/Dump Sizing
The HP-UX swap dimensioning rule foresees to create a swap area large as the double of the core mem-
ory, this rule is also followed by the OS-Conf installation script, but to allow different approaches the capa-
bility to define different size of the core memory is provided.
This step in the procedure shows you the amount of core memory detected and ask you to confirm.
This section enables you to enter size of primary "SWAP/DUMP" area.

___________________________________________________________________________
___________________________________________________________________________
The primary "SWAP/DUMP" area is: 2048 Mbyte
Just pressing [Enter] will keep this primary "SWAP/DUMP" size,

enter new value if you wish to change size.
___________________________________________________________________________
Enter primary "SWAP/DUMP" size in MByte [2048]:
Press [Enter] to confirm the default value.
The shown value is the primary SWAP/DUMP disk area size, it corresponds to the current amount of RAM
Core memory.To change it, enter a different value in order to increase on reduce the disk space used for
primary SWAP/DUMP. The total amount of swap space requested will be adjusted if needed.
N.B. Do not enter a value less then 50% of RAM size, it can prevent the DUMP creation.

2.2.11 Hardware Scanning
Now the program is scanning the hardware looking for the present hard disks, it will take a few seconds.
Hardware detection in progress, please wait ...
Total disk(s) found = 2

Total CDRoms found = 1
Press [Enter] to continue...
Then the procedure will ask you to confirm the source media as the CD-ROM drive.
This section enables you to enter default Source media (CD/DVD).

___________________________________________________________________________
Source media (CD/DVD) Selection
___________________________________________________________________________
Device MByte Hardware Path Usage Type VolGroup

___________________________________________________________________________
c3t2d0 4482 0/0/2/1.2.0
___________________________________________________________________________
Please enter the Device Name of source media [c3t2d0]:

2.2.12 Mirror/Disk UX Selection
Before proceeding in the hard disk assignment rules it is mandatory to define if there is any high availability
feature or device in the system.
Do not configure the mirror disk on HP Integrity servers equipped with P400 Smart
Array controller.
First of all, if the disk mirroring has to be implemented by procedure you have to reply y to the next ques-
tion:
This section enables you to choose for Mirror Software option.

___________________________________________________________________________
The Mirror/Disk UX software allow to create a copy of the data stored on the
disks, to prevent system down time due to disk failure, but requires the license
of use and the double of the disk space requested without the mirror option.
Have you to install a machine with Mirror Disk capability ?
To implement the disk mirroring you need to have the HP Disk Mirror/UX licence and double of the disk
space requested without the feature, for these reasons the procedure issues the following confirmation
question:
N.B. The installation of the HP Disk Mirror/UXTM software without license is not allowed
WARNING
To be able to install and configure mirror software the following
requirements must be matched:
- You MUST have evidence of HP Disk Mirror/UX software license
customer ownership
- The hardware configuration MUST have a spare hard disk for each
one in use
Are both requirements satisfied ?
If you have the required items just replay with y[Enter].
Choosing the Disk Mirror/UX installation the procedure automatically configures the mirror feature on any
Volume Group you'll create in the system by using the feature of OS-Conf. To perform this activity the
installation will take 30 minutes more and the machine will be rebooted twice.

2.2.13 Virtual Array Software Selection
Meaningful only for HP 9000 machine.
The Alcatel-Lucent NM application will support with Data Sharing environment the virtual array disk stor-
age VA7100 or VA7110, these hardwares require a specific management software that can be installed
automatically by answering y [Enter] to the following question:
N.B. The installation of the virtual array disk storage software is not allowed if the hardware
is not present!
_This section enables you to select Virtual Array Manager Software.

___________________________________________________________________________
The Virtual Array Manager Software is requested just in case there is any HP
Storage Work Virtual Array hardware equipped in your system.
There is any HP Storage Work Virtual Array (VA7xxx) in the system

hardware configuration ?

2.2.14 Disk Selection
The next phase in the procedure bring you to define the disk configuration. The request issued by this
activity depends by the previous answer. That means if you had chosen to have the disk mirror capability
the procedure will ask you disk drive to be able to make a copy of all the data. To obtain the higher avail-
ability level is suggested to choose disk connected to different controllers. For a correct disk management
it is advisable to define the disk usage policy in advance.
2.2.14.1 Disk Mirror Configuration Policy
Do not execute this paragraph if there is a Smart Array P400.
The disk mirror capability is used for two main purposes:
1) Allow system to survive in case of a single disk failure.
2) Allow system to survive in case of a single disk controller failure.
3) The system is not equipped with Smart Array controller that provide this feature.
It is possible to obtain the better high availability goal only with a correct configuration of the disk resources
available on the system. HP-UXTM Mirror Disk/UXTM allows to reach the first target without specific con-
figuration, but to be able to reach the second one you must have an appropriate system configuration in
terms of hardware and software. The hardware suggested by Alcatel-Lucent are design to allow mirror
configuration that allow system to survive to disk controller failure, but the software configuration has to
be done as shown in this paragraph to do not loose this capability.
First of all you have to be able to identify the hard disk present in the configuration, them are usually iden-
tified by their file name. In particular the file name can be very helpful to identify the disk - controller rela-
tionship. Any disk in the configuration is identified by the following name: c#t#d#
c[0-15]SCSI of Fiber Channel card instance of disk controller to which the disk is attached to.
t[0-15]SCSI of Fiber channel address of the device on the interface.
Using the c# of disk file name is possible to identify the relationship between disks and controllers.
HP-UXTM allows to connect a single disk to two different controller (Dual-Access), in this case the system
command can show two device file for the same disk units, but the installation script manage this con-
figuration by showing just one device with a “D" on the first column of the related line, hereafter an example
of the selection menu shown by installation scripts:

This section enables you to select the boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________
c1t2d0 8672 0/0/1/1.2.0 _(free)_ ______ ________

c2t2d0 8672 0/0/2/0.2.0 _(free)_ ______ ________
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c6t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c6t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
Now you have to define two disk group (physical volume group) with the following characteristics:
1) The sum of disk space amount of the two group have to be the same.
2) The Dual-Access disks can be assigned to any group.
3) The non Dual-Access disks connected to the same controller MUST belong to the same group.
N.B. It is important to follow this rules starting from boot disk definition 2.2.14.2 at page 70.
The following picture is a schematic example of disk configuration that can produce the output shown
before. This is not a typical system, but provided all the case that can occur in field.
c1t2d0
c2t2d0
c4t8d0 c4t9d0
c6t12d0 c6t13d0
Figure 13. Example of disk configuration
With this configuration the best one are:

group 1 with c1t2d0, c4t8d0 and c4t9d0, group 2 with c2t2d0, c6t12d0 and c6t13d0.
Because the I/O channel are balanced.
Allowed configuration can be:
group 1 with c4t8d0, c1t2d0, and c2t2d0, group c4t9d0, c6t12d0 and c6t13d0.
Wrong configuration:
Because the two non dual-access disks have been assigned to the two groups, and the controller
failure gets the system in failure too.

2.2.14.2 Main Boot Disk Selection
The first disk you have to select is the main boot disk for the system, the list of the available disk will be
shown in the window in the following format:
This section enables you to select the boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________
c1t2d0 8672 0/0/1/1.2.0 _(free)_ ______ ________

c2t2d0 8672 0/0/2/0.2.0 _(free)_ ______ ________
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
Enter the disk device that will be used as boot device then press [Enter].
N.B. A "D" character is shown before the device name in the “Device" column to advice the disk is
accessible via two different disk controllers. This configuration is typically used with Fiber Chan-
nel device.
2.2.14.3 Alternate Boot Disk Selection
This question will be issued only if you had selected the mirror disk option; enter the device that will be
used as alternate boot disk. To reach the highest availability level, it is advisable to choose a disk not con-
nected to the same SCSI bus of the Main Boot Disk, this choice allows the system to survive also to a
SCSI bus failure. It is also advisable to choose a disk with the same size.
This section enables you to select the alternate boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________
c1t2d0 8672 0/0/1/1.2.0 Pri_Boot _Main_ vg00

c2t2d0 8672 0/0/2/0.2.0 _(free)_ ______ ________
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
Select Alternate BOOT Disk device Name :

If the size difference between the main and alternate boot disk is bigger then one Gbyte the procedure
will issue a warning message, and it will ask you to confirm your choice.
WARNING: Difference between Primary & Alternate Boot disk size is too big
difference is:"1024 MegaByte", please check your selection Is this correct?
Replay y[Enter] to confirm, or n[Enter] to change your choice.
2.2.14.4 Multiple Disk Request
To install minimum HP-UX configuration on a machine with 512 Mbyte, 8 Gbyte of hard disk are required.
If you provide 4 Gbyte or smaller hard disks, the procedure will prompt you again until the requested
amount of disk space will be reached.
2.2.14.5 Disk Selection Confirmation
When all the disk selection will be completed, the program will ask you to confirm your choice.
After this confirm question the contents of the selected disk will be lost.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________

c2t2d0 8672 0/0/2/0.2.0 Alt_Boot Mirror vg00
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
These are your Disks Selection x HPUX installation on this system.

ATTENTION: The contents of selected disks will be permanent lost
Do you want CONTINUE?
If you are sure of your choice enter y[Enter], then the procedure will start the execution phase.
This is the last question issued by the procedure, after your reply the pro-
cedure will operate unattended.
The procedure executed by a HP9000 L1000 server will take:
20 minutes for operating system
+30 minutes to install and configure mirror
Don't worry if the machine reboots automatically.

2.2.15 Keyboard selection
This question is related to the keyboard selection.
Meaningful only for HP Integrity machine.
The script explains how to declare the type of keyboard. It asks you if the keyboard that it has been set
is right:
The keyboardmap has been set to PS2_DIN_US_English (QWERTY)

Is this correct?
Press [y] for yes, [n] for no or [q] to quit, then press [Enter]
Enter y if the keyboard is right, otherwise enter n and the system prompts you:
A USB interface has been detected on this system.

In order to use a keyboard on this interface, you must specify
a language mapping which will be used by X windows and
the Internal Terminal Emulator (ITE).
The characters "1234567890" will appear as "!@#$^&*()"
on keyboards that use the shift key to type a number.
Your choice will be stored in the file /etc/kbdlang
1) USB_PS2_DIN_Belgian 2) USB_PS2_DIN_Belgian_Euro
3) USB_PS2_DIN_Danish 4) USB_PS2_DIN_Danish_Euro
5) USB_PS2_DIN_Euro_Spanish 6) USB_PS2_DIN_Euro_Spanish_Euro
7) USB_PS2_DIN_French 8) USB_PS2_DIN_French_Euro
9) USB_PS2_DIN_German 10) USB_PS2_DIN_German_Euro
11) USB_PS2_DIN_Italian 12) USB_PS2_DIN_Italian_Euro
13) USB_PS2_DIN_JIS_109 14) USB_PS2_DIN_Korean
15) USB_PS2_DIN_Norwegian 16) USB_PS2_DIN_Norwegian_Euro
17) USB_PS2_DIN_S_Chinese 18) USB_PS2_DIN_Swedish
19) USB_PS2_DIN_Swedish_Euro 20) USB_PS2_DIN_Swiss_French2_Euro
21) USB_PS2_DIN_Swiss_German2 22) USB_PS2_DIN_Swiss_German2_Euro
23) USB_PS2_DIN_T_Chinese 24) USB_PS2_DIN_UK_English
25) USB_PS2_DIN_UK_English_Euro 26) USB_PS2_DIN_US_English
27) USB_PS2_DIN_US_English_Euro
Enter the number of the language you want: <language_number> [Enter]
You have selected the keyboard language PS2_DIN_xxxxx

Please confirm your choice by pressing RETURN or enter a new number : [Enter]

2.2.16 Execution Phase
The procedure is now entering the execution phase, it will be performed unattended.
This phase takes 45 minutes on a HP9000 L1000 server, with Fast/Wide differential hard disks. If you had
chosen the disk mirroring option the procedure will reboot two times and will take 35 minutes more.
In the following the activities performed:
– To create the physical volume on the main boot disk.
– To set the primary boot path.
– To create the physical volume on the alternate boot disk (only for mirror disk configuration).
– To set the alternate boot path (only for mirror disk configuration).
– To create the Logical Volumes.
– To create a new file system into the Logical Volume
– To restore the HP-UX dumps.
– To update the configuration files
– To reboot the system to activate the HP-UX installed on the hard disks.
– To install the Mirror/Disk UX and related patches (only for mirror disk configuration).
– To configure the mirror for all the Logical Volumes (only for mirror disk configuration).
Don't worry if the system reboots, it is requested by some software, to be able to configure HP-UX kernel
and configure driver.
If required, replace the first installation medium, when it will be required with a specific message on the
console.
When procedure complete its task on the console you'll see the message:
The system is ready.
GenericSysName [HP Release B.11.11] (see /etc/issue)

Console Login:
Before proceed with the next step, you have to check the execution log to verify no error has been
occurred, you have to login the system a super-user root and check that no error message is shown has
explain, hereafter the messages shown at login time to advice you the installation is still in progress or
when it was failed.

2.2.17 Login Message During the Execution
Whoever is logging the system during the executing will be alert the installation is in progress by the fol-
lowing message:
******************** WAITING INSTALLATION IS IN PROGRESS *****************
Do not alter environment, check log file in /SCINSTALL/scinstall.log
***************************************************************************
Any action on the system or depot may compromise the installation.
2.2.17.1 Login Message when Installation Fails
In case any error is met during the execution phase, the procedure stops and the following message is
issued:
******************* THIS SYSTEM IS NOT CORRECTLY INSTALLED ****************
To fix the problem, check the log file in /SCINSTALL/scinstall.log
***************************************************************************
The procedure it is not able to recover the error by itself, look at the log file to have more information about
the error.

2.3 Software Package Predispose
When the HP-UX 11i operating system installation is completed, the system is not yet ready for Alcatel-
Lucent NMS installation; in fact NMS needs some layer software, that are usually called software platform,
to be able to perform their tasks.
2.3.1 OS-Conf Installation on HP9000

The OS-Conf packages have to be installed by following this procedure:
a) Login the just installed system as “root" user.
b) Identify the device driver (see “Find the CD-ROM/DVD-ROM Device File" appendix A.1 at page 161).
c) Insert the medium with label “SWP-OSCONF_ADD-V7.1.2_P03" volume 1/1 in the driver.
d) Mount the medium by entering the command:

...,sys,root # mount -o rr /dev/dsk/<device file> /SD_CDROM [Enter]
e) Install the OS-Conf packages by enter the command:

...,sys,root # swinstall -s /SD_CDROM OS-CONF OSC-3PP [Enter]
If the procedure is carried out without error, the system is ready to be predisposed.
b) Install the OS-Conf packages by enter the command:

OS-CONF,r=7.1.2.P03 \
OSC-3PP,r=7.1.2.P03 [Enter]
Keeping the CD mounted perform the software platform upgrade to OS-Conf 7.1.2.
a) Start the upgrade procedure by entering:

b) The procedure will ask you if the software platform upgrade must be perform by CD/DVD or network
depot.
--------------- LAYERED PRODUCTS Repository -------------

1 - CD-ROM or DVD media
2 - Software Depot
q - quit
Insert choice and press [Enter]:

Update Platform from CD/DVD
1) Reply the previous question by entering “1 [Enter]":

Insert choice and press [Enter]: 1 [Enter]
N.B. In this case must be available all the CD's set.
2) The procedure asks you to enter the CD driver file name, usually the proposed default is correct.
Enter 'q' to Quit or the CD device [def=/dev/dsk/c2t2d0]:
Update Platform from Network Depot

N.B. In this case must be available a DEPOT already updated.
c) The procedure will check the amount of free space on the file system, and enlarge them when
needed. If any enlarged file system is in use, the extension can not be complete, a reboot will be
required by issuing the following message:
N.B. The file system extension can ask for new hard disk, refer to paragraph 2.2.14.1
“Disk Mirror Configuration Policy" at page 68 the rule for the hard disk choice.
___________________________________________________________________
System need reboot x complete extension of file system current ...

___________________________________________________________________
d) If one or more file system will require the system reboot the following message will be displayed:
----------------------- ATTENTION ------------------------------

Upgrade OSC-3PP install product(s) and/or Patches
System could automaticaly reboot
All Application must be stopped (example: RM, NM, Resilience, etc...)
Do you want continue ?
Stop all the activity, if any, and reply with “y[Enter]".
e) The procedure will ask you if the software platform upgrade must be perform by CD/DVD or network
depot.

2 - Software Depot
q - quit
Insert choice and press [Enter]: [Enter]
N.B. In case of installation in upgrade from NR8.1 or previuos, execute the (as root) the following
command:
...,sys,root # /SCINSTALL/etc/scJacORBupg OFF [Enter]

2.3.2 OS-Conf Installation on HP Integrity
The OS-Conf packages have to be installed by following this procedure:
b) Identify the device driver (see “Find the CD-ROM/DVD-ROM Device File" appendix A.1 at page 161).
c) Insert the medium with label “SWP-OSCONFUX_ADD-V8.1.2_P01" volume 1/2 in the driver.
d) Mount the medium by entering the command:

...,sys,root # mount -o rr /dev/dsk/<device file> /SD_CDROM [Enter]
e) Install the OS-Conf packages by enter the command:

...,sys,root # swinstall -s /SD_CDROM OS-CONF OSC-3PP-UXIA [Enter]
b) Install the OS-Conf packages by enter the command:

OS-CONF,r=8.1.2.P01 \
OSC-3PP-UXIA,r=8.1.2.P01 [Enter]
Keeping the CD mounted perform the software platform upgrade.
a) Start the upgrade procedure by entering:

b) The procedure will ask you if the software platform upgrade must be perform by CD/DVD or network
depot.

2 - Software Depot
q - quit
Insert choice and press [Enter]: [Enter]
Update Platform from CD/DVD

N.B. In this case must be available all the CD's set.
2) The procedure asks you to enter the CD driver file name, usually the proposed default is correct.
Enter 'q' to Quit or the CD device [def=/dev/dsk/c2t2d0]:

Update Platform from Network Depot

N.B. In this case must be available a DEPOT already updated.
c) The procedure will check the amount of free space on the file system, and enlarge them when
needed. If any enlarged file system is in use, the extension can not be complete, a reboot will be
required by issuing the following message:
N.B. The file system extension can ask for new hard disk, refer to paragraph 2.2.14.1
“Disk Mirror Configuration Policy" at page 68 the rule for the hard disk choice.
___________________________________________________________________
System need reboot x complete extension of file system current ...

___________________________________________________________________
d) If one or more file system will require the system reboot the following message will be displayed:
----------------------- ATTENTION ------------------------------

Upgrade OSC-3PP install product(s) and/or Patches
System could automaticaly reboot
All Application must be stopped (example: RM, NM, Resilience, etc...)
Do you want continue ?
Stop all the activity, if any, and reply with “y[Enter]".

2.3.3 Create Depots
The installation can be executed retrieving the software from a local CD or from a network depot. In case
you choose to install from depot you have to define a system with enough disk space available, where
two depots can be created, one for the third party software, that we will call “OS_Conf Depot"; where you
can store all the software layer distributed by OS_Conf itself, and one for the Alcatel-Lucent TNM software,
that we will call “Alcatel-Lucent NMS Depot".
To setup the depot you need 2.3 Gbyte for OS_Conf Depot, while the size of Alcatel-Lucent TNM depends
by the different NMS you plan to install.
The following paragraphs provide the instructions to create the depots.
2.3.3.1 Create “OS_Conf Depot"
OS-Conf Depot can be useful when you have to install more than one system, because it allows to execute
simultaneously and unattended installations. The detailed procedure to create the OS_Conf Depot (see
“1350 Administration Guide" [2] “How to create a Network Depot").
2.3.3.2 Create “Alcatel-Lucent NMS Depot"
This paragraph shows how to create the depot for Alcatel-Lucent software. The depot size depends by
the software you have to store on the disk, the Table 13. column “Depot Package Size" at page 165 sum-
marizes the space required in Mbytes.
The following actions must be executed on the depot machine; preferably it should be a machine in the
network. It may be the same machine that you are installing, if you have sufficient free disks space.
You have to login to the alcatel-lucent depot machine as “root" user, and execute the following command:
1) Extend /alcatel to allow the storage of Alcatel-Lucent software by entering the command:
...,sys,root # scextendfs /alcatel/DEPOT <required disk size> [Enter]
2) Change the default directory on the depot one:

3) For each distribution CD Rom that contains the software you have to install:
a) Insert the CD into the driver.

b) Mount the CD at /SD_CDROM directory:
...,sys,root # mount -o rr /dev/dsk/<cdrom device file> /SD_CDROM[Enter]
N.B. For more informations about the CD-ROM software contents, refer the Table
15. at page 166.
c) Copy the entire CD contents to /alcatel/DEPOT directory by entering the command:

...,sys,root # cp -p /SD_CDROM/* /alcatel/DEPOT [Enter]
d) Dismount the CD:
...,sys,root # umount /SD_CDROM[Enter]
e) Remove the CD from the device.

2.3.4 Before Starting
Before starting with the system predispose, it is advisable to have a clear picture of the software archi-
tecture; it is also advisable to prepare a schema of the system you are going to install. This allows you
to prepare a list of materials and data that will be required during the installation.
The Alcatel-Lucent network management system application architectures are generally provided with
two functionalities:
a) Master function
b) Client function
The Master function provides the set of software programs that allows the machine to perform the network
management, and the Client function to provide the man-machine interface. The two functionalities can
be installed on the same system or on a different one. Where system navigation is foreseen, it is man-
datory to install the NMS Client on the system that has to perform the navigation. Just to clarify the concept
look at the following example: considering system with three machines, the first is installed with both
1354RM Master and 1353NM clients, where two 1353NM instances have been created with the same
identifier of the two 1353NM master located on the other two systems. In this case it is possible to have
1353NM functionalities at 1354RM level (Navigation).
1353NM Master
1353NM
Client 1354RM
1353NM Instan. 2 Master+
Client Client 1353NM
Instan. 3 Instan.1 Master+
Client
Instan.2
OS-Kernel
OS-Kernel
1354RM Master with two 1353NM Clients
1353NM Master
1353NM
Master+
Client
Instan.3
OS-Kernel
Figure 14. Alcatel-Lucent NMS Architecture.
Moreover some other software can be installed as component, they are qualified as NMC.
2.3.4.1 Requested Data
To be able to complete the installation you have to know in advance the answer to the following questions:
a) Which is/are the NMS you want to install ?

b) Which is/are the NMS versions ?
c) How many instances are foreseen ?
d) Which is/are the instance identifiers ?

e) Which is the size and role of the instances ?
f) Is there any NMC to be installed?
g) Is it foreseen the 1359HA Data Sharing?
Fill in the lists of NMS and NMC in APPENDIX Appendix B at page 163 where all the foreseen items are
shown.

2.3.5 Pre-Installation Actions
Hereafter there are some actions that have to be done before installing.
2.3.5.1 Host declaration
The network node description have to be filled in manually, for each host you have to communicate to,
you must add a line with the IP Address followed by the host name in the /etc/hosts file (see “Node Name
Management" paragraph 2.4.1 at page 102).
2.3.5.2 Authorize Network Loop-back Access for CD/DVD installation
Even if the installation is performed locally there are some activities that need the network access to per-
form their tasks, this is the reason why, to be able to install from CD (or DVD), it is necessary to add a
line in the /.rhosts file (creating it when it doesn't t exist) with the local host name followed by “root" key-
word.
2.3.5.3 Authorize the Retrieval from Depot Machine
This paragraph explains how to authorize the file retrieval from the depot machine, if you do not use any
depot machine skip it.
To be able to retrieve the Alcatel-Lucent software packages from the depot machine, the access to these
files have to be granted to all the root users of all the machines that have to be installed. This can be
obtained by writing in the /.rhosts file the hostname and the keyword “root" for each machine, and add a
line for each of them in the /etc/hosts file.
Example: you have to install the following three systems: hosta, hostb and hostc (the depot machine itself).
You have to write /.rhosts this way:
hosta root
hostb root
hostc root
N.B. All the host included in .rhosts file have to be defined in /etc/hosts one.

2.3.6 Install NMS Description and NR8 PL2 Installation Procedure
Before starting with the NMS predispose action, you have to install the NR8 PL2 Installation Procedure
and NMS description. This can be done from CD/DVD or from network depot. The following paragraphs
show how to perform the activity from both sources.
2.3.6.1 Install NR8 PL2 Installation Procedure and NMS Description from medium
To install the NMS description and installation procedure from medium insert “SWP-1350MS_NR8.1PL2-
DR4" volume 1/3 in the driver and execute the following procedure:

b) Mount the medium at /SD_CDROM directory:
c) Install the NMS description by entering the command:
...,sys,root # swinstall -s /SD_CDROM/SWPDESC_V8159.sdpkg \* [Enter]
d) Install the “Install_Wizard" software from medium by entering the command:
...,sys,root # cd /SD_CDROM [Enter]
e) Set the default directory as “/", by entering the command:
...,sys,root # cd / [Enter]
f) Dismount the medium:
...,sys,root # umount /SD_CDROM [Enter[
2.3.6.2 Install NR8 PL2 Installation Procedure and NMS Description from Network Depot
To install NR8 installation procedure from network depot you have to execute the following procedure:

b) Install the “Install_Wizard.sh" software from depot machine:
...,sys,root # mkdir -p /alcatel/DEPOT [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/Install_Wizard-R8.4.2 . [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/Install_Wizard_CMD-R8.4.9 . [Enter]
...,sys,root # rcp -p <depot IP addr.>:/alcatel/DEPOT/SWPDESC_V8159.sdpkg . [Enter]
c) Install the “Install_Wizard" software entering the command:
d) Remove the temporary file:
...,sys,root # rm /alcatel/DEPOT/Install_Wizard-R8.4.2 [Enter]
...,sys,root # rm /alcatel/DEPOT/Install_Wizard_CMD-R8.4.9 [Enter]
e) Install the NMS description by entering the command:
...,sys,root # swinstall -s /alcatel/DEPOT/SWPDESC_V8159.sdpkg \* [Enter]
N.B. If the remote shell (remsh) fails with error: remshd: Login incorrect. check the
depot machine access authorization (see paragraph 2.3.5.3 at page 82)
2.3.6.3 Mandatory Install Wizard W/A
Apply the following W/A, by executing (as root) the commands listed above:
...,sys,root # cd /alcatel/Install_Wizard/products/OS-KERNEL [Enter]

...,sys,root # cd OS-KERNEL_7.1.2-P19.5/data/TSDnm58636 [Enter]
...,sys,root # cp -p crdb_phase3 crdb_phase3.orig [Enter]
...,sys,root # dos2ux crdb_phase3.orig > crdb_phase3 [Enter]

2.3.7 Predispose for Installation
The OS-Kernel 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 pre-
dispose the system to be able to run OS-Kernel, because it has to be always installed. Then it will be pro-
vided an example of 1353NM, and a generic example for all the other NMS.
2.3.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 OS_Kernel.

2.3.7.2 Predispose for OS-Kernel
First of all you have to predispose the system for OS-Kernel, 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 1353NM 7.3 (only if PA-RISC Machine)
2 1353NM 7.4.5
3 1353SH 7.0 (only if PA-RISC Machine)
4 1354BMATM 7.1.4
5 1354BMETH 8.1.5
6 1354BMPR 8.1.6
7 1354RM 7.4.9
8 1354SY 8.0
9 1355VPN 6.1
10 1359HA 8.0
11 OS_KERNEL 7.1.7
Enter 'q' to Quit, 'd' to Display again or the Item Number: 11 [Enter]
Enter the OS_Kernel 7.1.7 item (11 in the example) to select it for the predisposition. The procedure
will ask you to confirm the choice.
Selected SWP 'OS_KERNEL 7.1.7'
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 ...... .....

.....
.....
OPTIONAL Product: HP-APA

Product Description: Auto-Port Aggregation Software B.....
Do you like to install it ? (y/n)
Choose to install and configure HP-APA product only if there is the related license.
.....
Analysing Product ...................
.....
TRANSLATOR procedure was successful.
The OS-Kernel is now stored for the predisposal that will be done leaving the script.

Starting from NR7.4 OS-Kernel Global Instance have to be created with a specific predisposal action, that
means you have to drive back the “scmanageswp" tool to the “SWP MAIN MENU" entering “q[Enter]"
2.3.7.3 Predispose for OS-Kernel Global Instance
Enter “4[Enter]" to select “Create new SWP INSTANCE".

The following menu will be shown to you:
Create new INSTANCE
Item SWP Name SWP Version Session

---- --------------- ----------- -------
1 OS_KERNEL 7.1.7 NEW
Enter 'q' to Quit, 'd' to Display again or the Item Number :
Enter “1[Enter]" to select the OS-KERNEL, and the possible instance will be shown with:
List of available INSTANCE dimension for SWP: OS_KERNEL 7.1.7
Item INSTANCE Dimension INSTANCE Description

---- -------------------- ---------------------------------------------
1 OSKERNEL OS-Kernel 7.1.2 for NR8.1 PL2 Global Instance
Enter “1[Enter]" to select the OS-KERNEL the OS-Kernel Global Instance. Then the tool will ask you to
“Insert the Instance Number for 'OSKERNEL' ", also if this value is not relevant we suggest
you to enter “1[Enter]".
Reply with “n[Enter]" to the “ Do you like a Multi-Volume group configuration ? (y/n)“,
and confirm you choice if the shown values are correct:
Selected INSTANCE:
Dimension OSKERNEL
Number 1
Multi-Volume NO
Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the
required software:

Note: There aren't kernel parameters defined.
Note: There aren't additional components defined.
The procedure shows again the list of possible instance for the next choice, enter “q [Enter]" twice as
shown hereafter and proceed with the NMS predisposal.

2.3.7.4 Predispose for 1353NM
This section describes the 1353NM predisposal, it is provided to better clarify the procedure behavior, but
you have to execute it only if you need the 1353NM functionality, otherwise go to next paragraph “Pre-
dispose for NMS" 2.3.7.5 at page 91.
1353NM subsystems is organized in two components: the software code and instance. You have to pre-
dispose 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.
IF YOUR INSTALLATION PLAN INCLUDES 1353SH BACKWARD COMPATIBILITY

TOOL, YOU HAVE TO INCLUDE 1353SH 7.0 ITEM IN THE PREDISPOSE ACTIVITY,
DEFINING AN INSTANCE FOR EACH 1353SH 5 or 1353SH 6 THAT HAVE TO BE MAN-
AGED. THE INSTANCE NUMBER MUST BE THE SAME OF RELATED 1353SH 5 OR 6
2.3.7.4.1 Predispose for 1353NM Software
Proceeding in the script execution, after the OS-Kernel predisposal the script prompt you again for choos-
ing the next software package, you have in any case to install something of 1353NM, so enter: 2[Enter]
to select the 1353NM 7.4.5
Predispose new SWP

---- --------------- -----------
2 1353NM 7.4.5
4 1354BMATM 7.1.4
5 1354BMETH 8.1.5
6 1354BMPR 8.1.6
7 1354RM 7.4.9
8 1354SY 8.0
9 1355VPN 6.1
10 1359HA 8.0
Enter 'q' to Quit, 'd' to Display again or the Item Number :2 [Enter]
The selected product is shown to check the right choice:
Selected SWP '1353NM 7.4.5'

After the confirm action the procedure analyzes the description showing all the software layers required:
Analysing Product Alcatel-OVDL 2.1

Analysing Product Expect 5.31
.
.
.
Analysing Product xemacs 21.1.14.2001-06-12
Analysing Product xloadimage 4.1
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.3.7.4.2 Predispose for 1353NM Instance
The 1353NM Instance define the behavior of the application, you have three possibilities:
1) Predispose for a 1353NM Information Manager (IM), if you want to install a 1353NM stand alone
or 1354RM cohosted system.
2) Predispose for a 1353NM Spare IM, if you are installing the spare system in a 1359HA Data
Sharing environment.
3) Predispose for a 1353NM Client, if you just want to have the 1353NM Presentation function on
any other NMS. In this case you have to create an instance for each 1353NM IM and the
Instance Identification number must be the same of the referred IM.
Here after 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 ----------------

2 - View predisposed and managed SWP
5 - View created and managed SWP INSTANCE
a - Apply
e - Exit

The already predisposed NMS will be shown in a list, enter the item of 1353NM (alias 1353SH):
Create new INSTANCE

---- --------------- ----------- -------
1 1353NM 7.4.5 NEW
2 OS_KERNEL 7.1.7 NEW
Enter 'q' to Quit, 'd' to Display again or the Item Number : 1 [Enter]
The list of the 1353NM possible instances foreseen for the specific machine model is provided.
List of available INSTANCE dimension for SWP: 1353NM 7.4.5

--- -------------------- ----------------------------------------------
1 1353NM_IM_Small 1353NM Master (IM) System Small Configuration
2 1353NM_IM_Medium 1353NM Master (IM) System Medium Configuration
3 1353NM_IM_Large 1353NM Master (IM) System Large Configuration
4 1353NM_US 1353NM Client (US)
5 1353NM_IM_S_DS_Spare 1353NM Master (IM) Small System for 1359HA ...
6 1353NM_IM_M_DS_Spare 1353NM Master (IM) Medium System for 1359HA ...
7 1353NM_IM_L_DS_Spare 1353NM Master (IM) Large System for 1359HA ...
Before entering the instance item number for the selection, read carefully the meaningful of each item in
the following table:
Table 8. 1353NM Instances
Instance type item Description
1353NM_IM_Small Entry level configuration
1353NM_IM_Medium Middle range configuration
1353NM_IM_Large High end configuration
1353NM_US Client User Interface
1353NM_IM_S_DS_Spare Entry level configuration for Spare system within 1359HA Data Sharing
1353NM_IM_M_DS_Spare Middle range configuration for Spare system within 1359HA Data Sharing
1353NM_IM_L_DS_Spare High end configuration for Spare system within 1359HA Data Sharing
N.B. The 1353NM_US instance is not defined for 1359HA protection

The typical configurations are:
– 1353NM Information Manager-System is completely devoted to 1353NM function.
– 1353NM Presentation-System is completely devoted to 1353NM man-machine

interface.
– 1354RM Information Manager-The system performs the 1354RM function. The 1353NM
software can be installed to allow the 1354RM to communicate
and control the 1353NM. For each controlled 1353NM IM
system a related 1353NM Client (US) instance has
to be created. This 1353NM Client must be configured
with the same instance number identifier (ID) of the
controlled 1353NM IM.
– 1353NM/1354RM CoHosted-The 1353NM Information manager and 1354RM one on the

same machine.
– 1354BM Information Manager-The system performs the 1354BM function. The 1353NM
software can be installed to allow the 1354BM to
communicate and control the 1353NM.
For each controlled 1353NM IM system a related 1353NM
Client (US) instance has to be created. This 1353NM Client
must be configured with the same instance number
identifier (ID) of the controlled 1353NM IM.
Enter the instance item number followed by [Enter] to make your choice.
For each instance the procedure asks for two information: the instance number identifier and the multiple
volume group.
The instance number identifier have to be assigned following these rules:
– The master instance identifier has to be unique in the whole network.

– The presentation instance identifier must be equal to the related master.
– The spare instance identifier must be equal to the related master.
Insert the Instance Number for '1353NM_IM_Small':
The multiple volume group option is mandatory for the 1359HA Data Sharing protected instances. You
can also choose to use the multiple volume group configuration without the 1359HA Data sharing, but you
have to devote specific hard disks for each new instance of data.
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 1353NM_IM_Small
Number 3
Multi-Volume NO

Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the
required software:

Note: the volume group defined in the "1353NM 7.4.5" descriptor will
not take in account, because multi_volume_group option is not set.
Volume group vg00 will be used.
Analysing Product DBD-MySQL 2.1026

Analysing Product DBD-MySQL 3.0004
Analysing Product DBI-1.32 1.32
Analysing Product MySQL 5.1
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.3.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 1353NM, software code and data areas; hereafter the predisposal
script behavior is shown.
2.3.7.5.1 Predispose for NMS Software
In both cases, if you have to start “scmanageswp" or proceeding from the 1353NM predisposal, you have
the “SWP MAIN MENU" on the screen, enter: 1 [Enter] to get on the next menu:
---------------- SWP MAIN MENU ----------------

a - Apply
e - Exit
The remaining NMS descriptions will be shown.

Predispose new SWP

---- --------------- -----------
3 1354BMATM 7.1.4
4 1354BMETH 8.1.5
5 1354BMPR 8.1.6
6 1354RM 7.4.9
7 1354SY 8.0
8 1355VPN 6.1
9 1359HA 8.0
Enter 'q' to Quit, 'd' to Display again or the Item Number:
Select a NMS of NR8.1 PL2 you want to predispose among: 1354BMETH 8.1.5, 1354BMPR 8.1.6,
1354RM 7.4.9, 1359HA 8.0 or 1355VPN 6.1. Enter the item number shown in the first column of the menu,
then press [Enter] :
To allow the correct behavior of 1359HA with cohosted NMS refer to “1359HA Post Predisposal"
paragraph 2.3.8 at page 100.
If you predispose the system for 1359HA you have to remind to predispose a 1359HA instance for
each NMS subjected to protection (see “Create NMS instance" paragraph 2.3.7.5.2 at page 93).
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>'
Please confirm your selection ? (y/n) y[Enter]
The procedure start the description analysis issuing the following messages:

.
The output depends by the chosen NMS
.
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

---- --------------- -----------
.
.
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.3.7.5.2 Create NMS Instance
This paragraph shows how to create a NMS instance for the specific data storage.
Check on NMS delivery notes if the NMS supports multiple instances.
---------------- SWP MAIN MENU ----------------

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

---- -------------------------- -------
1 1353NM 7.4.5 YES
2 <NMS name> <NMS version>YES
4 OS_KERNEL 7.1.7 YES
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 1359HA you have to predispose a 1359HA instance for each NMS subjected to pro-
tection. Moreover the 1359HA instance number can be arbitrary assigned, without relation with the
protected NMS.
The procedure will ask you for two information: the instance number identifier and the multiple volume
group. The instance number identifier to be assigned has to be unique for that NMS in the whole network,
if you are creating a NMS Client the instance number has to be the same of the related master.
Enter the instance number followed by [Enter] to proceed:
Insert the Instance Number for '<NMS Instance Type>':
The multiple volume group option is mandatory for the Data Sharing protected instances. You can also
choose to use the multiple volume group configuration without the 1359HA Data Sharing, but you have
to devote specific hard disks for each one.
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 NO
Confirm or refute the selection. If you confirm the procedure will predispose for the installation of the even-
tual required software:

.
.
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: .....

---- -------------------- ---------------------------------------------
....
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.
Create new INSTANCE

---- -------------------------- -------
1 1353NM 7.4.5 YES
2 <NMS name> <NMS version>YES
2.3.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 ----------------

a - Apply
e - Exit
Insert choice and press [Enter]: a [Enter]
All the item requested will be shown (example of a 1353NM and 1354RM cohosted)
Items SELECTED for the CONFIGURATION
Item Type SWP Name SWP Version INSTANCE Number INSTANCE Dimension Opt
--------- -------- ----------- --------------- ------------------ ---
SWP OS_KERNEL 7.1.7
INSTANCE OS_KERNEL 7.1.7 1 OSKERNEL
SWP <NMS name> <NMS ver.>
INSTANCE <NMS name> <NMS ver.> n <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.3.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.
------------- LAYERED PRODUCTS Repository -----------

2 - Software Depot
q - quit
You can choose between media or network depot, here only the network depot choice is shown.
2.3.7.6.1.1 Software Layer Installation Predisposal from Depot
Here the network depot choice is shown, enter “2[Enter]", then the procedure requires you to specify the
depot, enter:
<depot hostname>:/alcatel/SCDEPOT[Enter]

Where you have to replace “<depot hostname>" with the name of the depot machine (see at paragraph
”Create Depots” 2.3.3 at page 79)
--- Depot selection for LAYERED Products installation ----
Enter 'q' to Quit or the Depot absolute path name: 192.202.21.8:/alcatel/SCDE-

POT
Checking Depot presence ...

Predisposed installation for product: Perl5005_3
.
.
Predisposed installation for product: MySQL
SOFTWARE predisposition was successful.
2.3.7.6.1.2 Software Layer Installation Predisposal from medium
Here the CD/DVD choice is shown, enter “1Enter]", then the procedure requires you to specify the driver,
enter:
--------- Device selection for LAYERED Products installation ----------
Enter 'q' to Quit or the CD driver [default /dev/dsk/cxtxdx]:
2.3.7.6.2 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 ...

This operation takes a while, please wait ...
KERNEL configuration was successful.l
2.3.7.6.3 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.3.7.6.3.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" have following nested Mount Point(s):

/opt/tao1.4l_p7
Press:
[T] = Try again (but after you have attempt to umount FileSystem(s) )
[A] = Abort (DANGEROUS - operation is aborted)
[R] = Reboot (RECOMMENDED - operation will be completed after next reboot)
then press [Enter]
When such a message occurs during the predispose, replay with "R[Enter]" to postpone the file system
extension to the next reboot.
2.3.7.6.3.2 New Hard Disk Allocation
During the file system extension it may occur that the initial disk configuration it is not enough to store the
entire software, data and swap areas. In this case the procedure will require to add some more hard disk
to the system volume group. If the multiple volume group is requested at least one hard disk is requested
for each instance of software.
The procedure shows its execution trace (example):
DISKS configuration activated ...

____________________________________________________________________
Analize Mount Point:"/alcatel/7.1"

Request free MegaByte(s): 5800
Evaluate size MegaByte(s): 6848
Hardware detection in progress, please wait .......

....
Press [Enter] to continue....
When a new disk is requested, the procedure issues a menu with all the disks present in the configuration,
marking the unused disk with the label “(free)" in the “Usage" column.
N.B. If you are implementing the disk mirroring, to reach the highest availability level, it is advisable
to choose a disk not connected to the same SCSI bus of the Main Boot Disk, this choice allow
the system to survive also to a SCSI bus failure.

N.B. If you are implementing the disk mirroring, it is advisable to keep the two disk chains balanced.
If them are unbalanced the useful disk space amount is the minimum size of them.
If you are installing a machine in 1359HA Data Sharing configuration some disk unused by local sys-
tem (free) can be used by another one, double check the configuration also of the other systems!
_______________________________________________________________________
Disks Selection
Mount Point need 5632 MBytes on Volume Group: “/dev/vg00" (pvg0)
_______________________________________________________________________

_______________________________________________________________________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __________
D c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __________
D c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __________
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ __________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ __________
_______________________________________________________________________
Select Data Area (Main instance) dev name or [q] to quit:
Enter the name of a “free" disk.
_______________________________________________________________________
Disks Selection
_______________________________________________________________________

_______________________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 _(free)_ ______ __________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __________
D c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __________
D c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __________
c5t13d0 8680 0/7/0/0.13.0 __Data__ _Main_ vg00
_______________________________________________________________________
Confirm selection of device "c5t13d0"
Press [y] for yes, [n] for no or [q] to quit, then press [Enter]
After your confirmation, the disk contents will be irremediably lost!!

The script will require you to confirm your choice before use it, and the
Physical volume "/dev/rdsk/c5t13d0" has been successfully created.

Volume group "/dev/vg00" has been successfully extended.
Physical volume group "pvg0" has been successfully extended.
.
.
Activate SWAP area /dev/vg00/lvol13 ...
______________________________________________________________________
System need reboot x complete extension of file system current in use
_______________________________________________________________________
DISKS configuration was successful..
It is possible that more than one disk is requested to reach the amount of disk required space. The
expected disk amount depends by the number of NMS and NMS instances requested, its size can be com-
puted following the instructions shown in the paragraph “Requested Hard Disks" 1.1.1.4 at page 21.
2.3.7.6.4 Software Layer Installation
The last message issued before starting the software package installation is:
ATTENTION: now to complete the configuration Shutdown-Reboot will be exe...

***** The System reboots automatically, please wait *****
Reply by pressing [Enter], the machine will be automatically rebooted and software components
installed. If you are installing with CD/DVD, the request of the medium will be issued in console issuing
a message that reports the medium label.
N.B. Don't worry if the procedure does not require to insert all media, nether if it does not ask
media in ascending order.
2.3.7.6.5 End of Software Installation
When the installation will be completed on server console the following prompt will be shown:
The system is ready
GenericSysName [HP Release B.11.11] (see /etc/issue)

Console Login:
Before proceed to the next activities you have to login hp-uxTM system check for any error occurred during
the predisposition. Usually a specific message (see paragraph 2.2.17.1 ) immediately advise you that a
fault is occurred, but it also useful verify the contents of file:
/SCINSTALL/scinstall.log

2.3.8 1359HA Post Predisposal
When there are two or more cohosted NMS Master instances and the system has also the 1359HA failure
protection, some additional action are required after the system predisposal and before custom-
izing the software. In this conditions 1359HA maximizes system performance allowing to use both mas-
ter and spare servers for performing the normal operations, recovering the faulty application on a single
server.
The following figure shows how the 1359HA manages these faulty conditions, it is important to note in the
example how 1354RM is communicating with 1353NM in the two cases:
– When both machine are operational, 1354RM and 1353NM communication occurs via 1353NM Cli-
ent instance on board of 1354RM machine.
– When one of the two systems is out of service, the communication are direct
The software component shown in Figure 15.in gray color are not operational, them can be the stand-by
instances created by 1359HA.
Server hosta Server hostb
1354RM 1354RM
Master Master
Active Stand-By
Normal system
Operation 1353NM Client 1353NM Client
1353NM 1353NM
Master Master
Stand-By Active
Server hosta Server hostb
1354RM
Master
System failure
example. Active
FAULT
1353NM Client
1353NM
Master
Active
Figure 15. 1359HA communication example.
In this scenario 1353NM provide services to 1354RM through its client instance or directly, depending by
the situation. The same approach can be operated by 1354RM when cohosts with both1354BM ATM and
ETH.
Now you have to create manually the NMS Client to allow inter-NMS communication has shown in the
following paragraphs.

2.3.8.1 Manage 1353NM cohosted with any 1354 NMS
N.B. Do not configure for OS-Resilience it is NOT YET AVAILABLE!!!!
When a 1353NM is cohosted with any 1354 NMS (1354RM, 1354BM ATM, and 1354BM ETH), you have
to create the NMS client data instance file system manually, by entering the following command:
...,sys, root # scextendfs /usr/Systems/1353NM_<NMSInstance>_7.4.5_Presentation 500 [Enter]
Where:
<NMS Instance> has to be replaced by the NMS Instance identified associated to the 1353NM master.
2.3.8.2 Manage 1354RM cohosted with any 1354BM NMS
N.B. Do not configure for OS-Resilience it is NOT YET AVAILABLE!!!!
When a 1354RM is cohosted with 1354BM ATM, and/OR 1354BM ETH, you have to create the NMS client
data instance file system manually, by entering the following command:
...,sys, root # scextendfs /usr/Systems/1354RM_<NMS Instance>_7.4.9_Presentation 500 [Enter]

...,sys, root # scextendfs /usr/Systems/1354BMETH_<NMS Instance>_8.1.5_Presentation 500 [Enter]
and/or
...,sys, root # scextendfs /usr/Systems/1354BMATM_<NMS Instance>_7.1.4_Presentation 500 [Enter]
Where:
<NMS Instance> has to be replaced by the NMS Instance identified associated to the 1354RM/BM mas-
ter.

2.4 Operating System Configuration
This chapter shows the minimum operating system and platform configuration required to allow TMN
machine interworking.
2.4.1 Node Name Management

Before proceeding in the installation and customization it is necessary to declare all the IP network nodes
involved. The involved nodes means all the IP are defined in the following table:
Table 9. Involved IP Network Node table
Type Description
Alcatel-Lucent TNM sys- Any HP9000 server with Alcatel-Lucent TNM on board, that have to commu-
tem nicate with the machine you are installing.
Printers Any network printer that have to be used by the machine you are installing.
Virtual IP Address Only for 1359HA Data Sharing: the virtual IP address of the packages.
Time synchronization Any Time synchronization equipment reachable via IP network.

systems
For each machine that can be classify in the previous table, you have to check that a line exists in the file
/etc/hosts with Internet address and official host name (see hp-ux man page hosts for more information).
If the line exists check the data is corresponding with your addressing plan. If it doesn't exist you have
to add a new line with Internet address and official host name.
The official host name MUST be defined by using only alphabetic numbers and lower case
characters.
The /etc/hosts file must be manually updated each time a new machine will be installed.
2.4.1.1 Network configuration example.
This paragraph provides an example of a complex network management system, where there are five
servers working together. These are their roles in the TNM.
– hosta1354RM Client
– hostb1353NM Master
– hostc1354RM Client
– hostd1354RM Master
– hoste1353SH Master

There are other network equipments, such as rooters, printers (local and network), personal computer,
and time synchronization equipments. You have to identify the equipment specified by Table 9.at page
102, in the example:
– gpsrec1Time synchronization system via Global Position System.

– lp1 Network line printer.
gpsrec1 (GPS time receiver)

IP 192.202.21.51 lp1 (network printer)
WAN 192.202.22.6
WAN
hosta hostc
IP 192.200.49.1 hostb IP 192.202.21.8 hostd hoste
IP 192.202.21.7 IP 192.202.22.4 IP 192.202.22.5
Figure 16. Network Example
In this example all the machines work together; you have to define their IP address and official host names
in the /etc/hosts of the five servers.
This is mandatory, because it allows the machines to communicate each other.
Supposing that GPS time synchronization system (gpsrec1) has to be used by the entire network man-
agement system, it has also to be defined into the /etc/hosts of all servers.
The network printer (lp1) can be defined only on the server on the same local area network.
Table 10. IP Network Description example.
hosta hostb hostc hostd hoste
192.200.49.1hosta Present To insert To insert To insert To insert
192.202.21.7hostb To insert Present To insert To insert To insert
192.202.21.8 hostc To insert To insert Present To insert To insert
192.202.22.4hostd To insert To insert To insert Present To insert
192.202.22.5hoste To insert To insert To insert To insert Present
192.202.21.51gpsrec1 To insert To insert To insert To insert To insert
192.202.22.6lp1 To insert To insert

2.4.2 Synchronize the Clocks
The clock synchronization is mandatory for system working together with Kerberos authentica-
tion tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305 has to be configured by fol-
lowing the instructions shown in this paragraph.
If NTP is not configured you have to check the time difference among all the systems and
guarantee that it doesn't exceed five minutes.
Before proceeding with the NTP configuration you must have a clear picture of the configuration among
the involved machines, it is advisable to prepare a "time distribution plan" taking into account the following
rules:
a) The primary time sources have to be reliable ones, such as a Global Position System (GPS) receiver
time source.
b) Define two or three time-server machines. Each time-server should be a peer with of the other time-
servers.
c) If possible, do not synchronize multiple time-servers to the same outside source.
d) If you choose to use an HPTM server as time source, it must be configured to be synchronized with
its internal clock.
For example in a network with two GPS receivers and five nodes, with the following roles:
– host and hosted configured with: 1353NM and 1354RM co-hosted with 1359HA.
– hostly, host and hostel preform the presentation function for the resilient servers.
The resilient hosts plus a presentation (host) can be configured to receive the time from the GPS receives,
and swap the time among themselves. All the other servers in the network (hostly and hostel) have to be
configured to receive the time from the host, host e hosted.
GPS
GPS Receiver 1 GPS Receiver 2

IP 192.202.21.51 IP 192.202.22.20
WAN WAN
hosta hostc
IP 192.200.49.1 hostb IP 192.202.21.8 hostd hoste
IP 192.202.21.7 IP 192.202.22.4 IP 192.202.22.5
Figure 17. NTP Configuration Example

To obtain such a configuration the three time servers you have to declare the two GSP Receivers as NTP
servers, moreover they can declare the other ones as peers; the resulting configuration will be:
hosta
server gpsrec1 prefer
server gpsrec2
peer hostc
peer hostd
hostc
server gpsrec2
peer hosta
peer hostd
hostd
server gpsrec1
peer hosta
peer hostc
The “prefer" attribute distinguishes as the preferred source, this source it is usually the most reliable and
also the nearest one.
The remaining servers can retrieve the time from the other ones, here after the configuration:
hosta
server hostb prefer
server hostc
server hostd
hoste
server hostb
server hostc
server hostd prefer
To make easier the NTP configuration the “scxntp" script is provided.
To start “scxntp" script, login the system as root user and enter: scxntp [Enter]
========================================================================
OS-Conf xntp Protocol Configuration
========================================================================
1 - Add new NTP server
2 - Add new NTP peer
3 - Remove NTP server
4 - Remove NTP peer
5 - Configure NTP on local clock
6 - Show NTP configuration
7 - Show NTP status
8 - Start/Stop NTP server
9 - Align the time to server
e or q - for exit

To simplify the explanation, the procedure shows how to configure the server hostb and hosta of Figure
17.at page 104. Note, the configuration order is relevant for the system behavior, it is better to start con-
figuring the nodes more close to the Timeservers.
2.4.2.1 Configure hostb
This is the procedure using scxntp script to configure the hostb of Figure 17.at page 104.
a) Login hostb as root user.
b) Start the scxntp script by entering: scxntp [Enter]
c) Define the preferred timeserver:

Enter server hostname or IP address or q for Quit : 192.202.21.51
NOTE: Checking the configuration ...
Would you like to set 192.202.21.51 as preferred (y/n) ? y
NOTE: Updating /etc/ntp.conf adding server 192.202.21.51 ...
NOTE: Setting 192.202.21.51 timeserver for synchronize at boot time
Press return to continue ...
d) Define the secondary timeserver:

Would you like to set 192.202.22.20 as preferred (y/n) ? n
e) For each peer hosts enter:

NOTE: Updating /etc/ntp.conf adding peer 192.202.21.8 ...
f) Start the NTP Daemon, set-up the daemon automatic start at system startup, and synchronize the
hostb clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automat...
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE: Temporary setup xntpd autostart...
NOTE: Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset
-0.026898 sec
xntpd NOTE: Reset the setup xntpd autostart...
g) Leave script by entering “e" or “q".

2.4.2.1.1 Configure hosta
This is the procedure using scxntp script to configure the hosta of Figure 17.at page 104.
a) Login hosta as root user.
b) Start the scxntp script by entering: scxntp [Enter]
c) Define the preferred timeserver:

Would you like to set 192.202.21.51 as preferred (y/n) ? y
NOTE: Setting 192.202.21.51 timeserver for synchronize at boot time
d) Define the other two timeserver:

e) Start the NTP Daemon, set-up the daemon automatic start at system startup, and synchronize the
hosta clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automatically
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE: Temporary setup xntpd autostart...
NOTE: Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset
-0.026898 sec
xntpd NOTE: Reset the setup xntpd autostart...
f) Leave script by entering “e" or “q".
The script allows to easily manage the NTP configuration, you can add or/and delete servers and/or peers,
show the configuration, stop and start the NTP daemon, or align in one shot your system time to a specific
server.
Defining a NTP server the management script allows to specify the preferred one, it is not recommended
to define more than one preferred server.
The NTP mechanism takes a long time to synchronize the machine with server. The NTP dae-
mon has to be stopped and started each time the configuration changes. Usually the NTP
daemon is not running.

2.4.2.2 Initial Clock Alignment
When a machine is installed for the first time, the clock is not synchronized with any reference, the easiest
way to synchronize it with the other is by running “scxntp" script selecting the option N.9 “Align the time
to server".
N.B. The time alignment is forbidden when NTP daemon is running.
To align the time you have to login the system as root user and start the script “scxntp" by entering:
...,sys,root# scxntp[Enter]
========================================================================
OS-Conf xntp Protocol Configuration
========================================================================
1 - Add new NTP server
2 - Add new NTP peer
3 - Remove NTP server
4 - Remove NTP peer
5 - Configure NTP on local clock
6 - Show NTP configuration
7 - Show NTP status
8 - Start/Stop NTP server
9 - Align the time to server
e or q - for exit
At the prompt enter “9 [Enter]"
Enter server hostname or IP address or q for Quit :
The procedure will ask you to enter the IP address or Hostname of the timeserver, enter it and press [Enter]
key. The time will be aligned and shown.

2.4.3 Poseidon License Management Configuration
Poseidon is the license software manager used to authorize the Alcatel-Lucent Software execution.
N.B. THE AUTHORIZATION LICENSE REQUEST CAN BE EXECUTED ONLY BY AUTHORIZED

ALCATEL-LUCENT PERSONAL.
The package foreseen to manage network floating license, that means you must define one or more sys-
tem in your network to perform the license server task.
– If you have three or more machines, you have to setup a “Three Redundant License Servers" con-
figuration, in accordance with the following rules:.
• The three license server machines should be located physically close to each other (if possi-
ble).
• Never configure redundant servers with slow communications or dial-up links.
• The three server have to be reliable.
With three-server redundancy, only one of the three servers is 'master', capable of issuing licenses.
Since all clients must contact the 'master', all clients must have reliable networking to a single node.
– if in your network there are less than three nodes, you have to define a the license server, and all
the required licenses have to be loaded on that server.
The license have to be required providing the host identifier of the license server(s). Do not provide the
host identifier of the machine where the application is planned to be run.
2.4.3.1 Retrieve License Servers Host Identifier
When you have selected the license server machine(s), for each of them you have to retrieve the host
identifier by executing the following commands:
a) Log in as root on the machine.
b) Get the hostname of the current machine:

..,sys,root # uname -n [Enter]
c) Get the host identifier of the current machine:

..,sys,root # /opt/poseidon/bin/lmhostid [Enter]
Then fillin this one of these forms:
Table 11. Three Server Redundant License Form
Host Name Host Identifier
Table 12. Single License Form
Host Name Host Identifier

2.4.3.2 Require the Authorization License
The license can be require via Alcatel-Lucent Intranet Web, by authorized Alcatel-Lucent personal only
to http://nmfactory.ond.alcatel.it/.
2.4.3.3 Store the Authorization Key in the License File.
When you receive the license authorization key, you have to edit it by adding 27000 as port number at
the end of each “SERVER" line as show in the following example:
From: SERVER host_c 839dc26
To: SERVER host_c 839dc26 27000
Then store the resulting file in the following file of any machine that have to execute Alcatel-Lucent TNM
software:
/opt/poseidon/etc/license.dat
Then start the Poseidon software on it, by entering the command:

...,sys,root # /sbin/init.d/poseidon stopEnter]
...,sys,root # /sbin/init.d/poseidon start[Enter]
Don't worry if no daemon is started on the machines that are license client.
2.4.3.4 Check the License Status
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat[Enter]
Hereafter an example of the command output. It is divided in four sections: title, server status, vendor dae-
mon status, and feature usage.
The title just shows the version of the license manager.

lmstat - Copyright (c) 1989-2003 by Macrovision Corporation. All rig...
Flexible License Manager status on Tue 7/20/2004 18:15
The server status shows the license server names, which is the current license server master and
License server status: 27000@hosta,27000@hostc,27000@hostd
License file(s) on hosta: /opt/poseidon/etc/license.dat:
hosta: license server UP (MASTER) v9.2

hostc: license server UP v9.2
hostd: license server UP v9.2
The vendor daemon show the status of the software used to control the license, it must contain “alcatel":
Vendor daemon status (on hosta):
alcatel: UP v9.2
Then the feature usage list, with the list of all the authorized feature, and for each one of them the user,
the host and the start date of usage:
Feature usage info:
Users of 1353NM_POINT: (Uncounted, node-locked)

alcatel hostb /dev/tty (v7.1) (hosta/27000 4406), start Tue 7/20 16:34

2.4.3.5 Add a New License
Sometimes in the system live it is necessary to increase the number of license. To add a new license on
a running license server machine without interrupt the serice, you have to proceed this way:
Do not mix permanent floating authorization key with demo one in the same file!
a) Retrieve the new license key from Alcatel-Lucent web, asking for the same host identifier of the first
one.
b) Login a Poseidon license server system.
c) Save the current license file in a security copy by entering:

...,sys,root # cd /opt/poseidon/etc/ Enter]
...,sys,root # cp -p license.dat license.save Enter]
d) Add the “INCREMENT" line from the just obtained license file, to the /opt/poseidon/etc/license.dat
file.
The INCREMENT line can be split in two or more ones, because of the length. If the “INCRE-
MENT" line terminated with back slash ( \ ), that means also the next one have to be consid-
ered as part of “INCREMENT".
e) If you have the three host redundant configuration, copy the license file on other two license servers.
f) Force the license server daemon to reread the license file by entering:
...,sys,root # /sbin/init.d/poseidon reread [Enter]
g) Check again with “lmstat" (see paragraph 2.4.3.4) if the number of point has been increased.
2.4.3.6 Poseidon License Server Troubleshooting
Some problem has been experienced configuring the three redundant Poseidon license servers. This
paragraph summarizes these problems and show a possible solution way.
2.4.3.6.1 Redundant Connectivity
The three redundant servers work properly only if each server is able to communicate with the other two.
This is the reason why it is better check the server configuration and connectivity. The easiest way to do
it is try a network “ping" from each license server to any other one:
..,sys,root # ping <Hostname> [Enter]
where <Hostname> is the name of the remote license server machine(s).
– If the server replies the “ping" request an output like the following will be provided:
,sys,root # ping hostc 64 2

PING hostc: 64 byte packets
64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms
----hostc PING Statistics----

2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0

– Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
• ping: Unknown host <Hostname>

Means the license serve <Hostname> is not defined in the host name repository, if you know
also license server IP address you can add it to the host name repository (see paragraph 2.4
at page 102 for more information). When the license server hostname will be present in the host
name repository retry ping command.
• 2 packets transmitted, 0 packets received, 100% packet loss

If no one of the "ping" request is replayed, the are three know possibility:
a) The remote server is down.

b) The remote server is not reachable because the IP address is wrong.
c) The remote server is not reachable because there is no known route on the network
First of all it is better to verify that the server is running. It the server is running check on the /
etc/hosts file if the IP address defined for the specified server is correct. If also the IP address
is correct, the reason can depend by the Default Gateway, check is adefault gateway si defined
and reachable. If you do not know name and IP address of the network default gateway refer
to the network administrator.
2.4.3.6.2 Two licence servers down
The three redundant license server fails when more than two servers are down or are unreachabe, in order
to reduce the risk of license failure is suggested to peridiacally check the license servers entering:
...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat[Enter]

2.5 Install and Customize Alcatel-Lucent Software
Install and Customize Alcatel-Lucent Software is the most important installation phase, when the entire
Alcatel-Lucent Network Management software is copied from the distribution media to the installation tar-
get, and then adapted to the target host by the customization phase.
2.5.1 Install and Customize OS-Kernel

The Alcatel-Lucent OS-Kernel is the operational platform, so it must be the first software installed.
To install OS-Kernel “Install.sh" procedure requires:
• The depot machine or distribution CD are available, and the local system is correctly
authorized to access the files (see 2.3.5.2 and 2.3.5.3 at page 82 for more informations).
• The installing system must be authorized to retrieve the files from itself or from depot machine.
• When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
N.B. In order to prevent error messages during the OS-KERNEL customize it is advisable to
configure the GoGlobal-UX license as shown in “1350 Administration Guide" [2] .
GoGlobal-UX will be stopped by OS-KERNEL configuration script. DO NOT start the

Install.sh with OS-KERNEL option from any window open via GoGlobal-UX, because
all the GoGlobal-UX windows will be closed, and the configuration aborted!
If the mentioned requirement are matched, the installation and customization can be started by entering:
For installation from CD:
1) Insert the “SWP-1350MS_NR8.1PL2-DR4" volume 1/3 in the driver.
2) Mount media at /SD_CDROM directory:

3) Start the installation script entering:

...,sys,root# ./Install.sh OS-KERNEL -cdrom [Enter]
4) The script issues the following question to require you to confirm the CD driver:
You have to reply with [Enter] to confirm, or enter e different CD device file name.
For installation from Depot Machine:

...,sys,root# ./Install.sh OS-KERNEL <hostname> <directory> [Enter]
Where:
<hostname> means the depot machine hostname
<directory>means directory path on depot machine where depot is located.
(usually /alcatel/DEPOT)

For installation from Depot machine:
The script start issuing the following mask:

..........
........
......
....
..
XX XX XXXX XX XXXXXX XXXXX XX

XX XX XX XX XX XX XX XX
XXXX XX XX XXXX XX XX XX
X X XX XX XXXX XX XXXX XX
XX XX XX XX XXXXXX XX XX XX
XXXXXX XX XX XX XXXXXX XX XX XX
XX XX XXXXX XXXX XXXXXXXX XX XXXXX XXXX
Installing OS-KERNEL package

===========================================================================
LOADING: #################################################################.
N.B. The report shown in this paragraph is just an example.
NOTE: Preparing to install ...

NOTE: Preparing to INSTALLER 7.1.4.5 ...
===========================================================================
Installation OS-KERNEL package
===========================================================================
***************************************************************************
NOTE: ${INSTALL_ROOT}/INSTALLER/Install OS-KERNEL ${DEPOT_HOST} file=${DEPOT
_PATH}/OS-KERNEL_7.1.2.tar.gz interactive=no
NOTE: ${INSTALL_ROOT}/INSTALLER/InstallOS-KERNEL ${DEPOT_HOST} file=${DEPOT_
PATH}/OS-KERNEL_7.1.2.tar.gz interactive=no
NOTE: 09/26/05 14:11:35 - Executing OS-KERNEL install_cmd ...
***************************************************************************
The installation is executed by INSTALLER that shows you the contents of the package :
--------------------------------------
Install Tool: INSTALLER 7.1.4.5 [ Supporting HP-UX & LINUX ]
--------------------------------------
Image Installation requested for:
Product OS-KERNEL
Format zip
Host 151.98.42.32
File /SD_CDROM//OS-KERNEL_7.1.2.tar.gz
Keep_data no
Check_sum 'NOT APPLICABLE'
Interactive no
PLEASE ENSURE LOCAL OS-KERNEL SYSTEM IS NOT RUNNING
.

The installation start automatically, this step will take up to 20 minutes.
The last question is related to the OS-Kernel customization; you have to reply also this question with
“y[Enter]"
Do you want to execute OS-KERNEL Custom? [y|n|q] y [Enter]
Then the OS-Kernel customization will be executed showing the trace on the terminal.
*******************************************************************
NOTE: ${INSTALL_ROOT}/Kernel/script/KernelCustomize
NOTE: ${INSTALL_ROOT}/Kernel/script/KernelCustomize
NOTE: 09/13/06 16:34:05 - Executing OS-KERNEL custom_cmd ...

.
.
.
NOTE: Reapplying PLT registrations.
NOTE: Check Go-Global 2 configuration ...
The procedure will stop after up to 12 minutes, asking you to authorize the Go-Global UX environment
shutdown. Ask all users logged in with Go-Global UX to log out the system.
GoGlobal 2 server will be stopped. Do you want continue ? (yes/no,

default=no)
Reply the question with “yes[Enter]" to allow Go-Global UX customization, and then the procedure will
be completed in a couple of minutes issuing:
NOTE: OS-KERNEL installation completed successfully.

===================================================================
NOTE: Session finished on: Mon Sep 26 14:38:37 METDST 2005
The OS-Kernel installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_OS-KERNEL_*.log
N.B. If you doesn't have already configure the GoGlobal License server, it could be displayed
an error message.
Don't' care of it, and configure the GoGlobal License Server.
Dismount the CD by entering:
...,sys,root# umount /SD_CDROM[Enter]
Remove the CD from the driver.

2.5.2 Install and Customize NMS and NMC
This section explains how to install and customize a Network Management Subsystem and/or Network
Management Component.
N.B. Very important: For the first installation it is mandatory to install the NMC software before cus-
tomize NMS instance. For installation performed later please refer to chapter 4 “Add New NMS/
NMC" at page 153.
For the list of NMS and NMC foreseen for NR8.1 PL2, refer to Table 5. at page 40 :
2.5.2.1 Install NMS or NMC
This paragraph shows how to install the Alcatel-Lucent TNM software optimizing the time need to adapt
it to this specific environment.
To be able to curry out this section the following items are required:
• A depot machine or CD distribution set available.
• The installing system must be authorized to retrieve the files from itself or from the depot
machine.
• When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
• You have to be able to login the system via GUI, in case of HP server the GoGlobal-UX have
to be authorized with the license code.
Then you can proceed with NMS and/or NMC shown at Table 5. at page 40 as summarized hereafter:
a) Install all software on the system.
N.B. ETH-MEDIATOR must be installed after 1354RM!
b) Customize all NMS.

c) When ETH-MEDIATOR is present, you have to customize 1354RM again .
Then complete the installation and customization with integrating the systems among themselves.
2.5.2.1.1 NMS or NMC Installation Procedure
If the mentioned requirement are matched, the installation and customization can be started by entering:
a) Login the system via Graphical User interface CDE as “root" user.
N.B. IF THE INSTALL NR8 IS STARTED FROM A SHELL WITHOUT A USEFUL DISPLAY
VARIABLE SET THE NMS CUSTOM WILL FAIL.
b) Open a dtterm window.

c) Entering the following commands at dtterm prompt:
1) Insert DVD “SWP-1350MS_NR8.1PL2-DR4" volume 1/3 in the driver.
2) Mount the CD at /SD_CDROM directory:

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

5) During the installation a message like this can be issued to advise you to replace the current
CD with another one, just replace the CD in the driver, the procedure will go on automatically.
Example:
PLEASE INSERT CD-ROM : "SWP-............ Vol ..."
For installation from Depot Machine:
...,sys,root# ./Install.sh -install <NMS/NMC name> <hostname> <directory>[Enter]

Where:
<NMS/NMC name>NMS or NMC name (including ETH-MEDIATOR).
<directory> means directory path on depot machine where depot is located.
N.B. To allow the recovery of errors it is possible to start “install.sh" with option “-confirm", the
option causes the issues of confirm request message before execute each step in the
installation and configuration. Replying “no" to these questions you can skip the step.The
script start issuing the Alcatel-Lucent mask, then it will ask you some questions.
........
......
....
..

XX XXXX XX XX XX XX XX
XXXX XX
XX XXXX XX XX XX
X X XX
XX XXXX XX XXXX XX
XX XX XX
XX XXXXXX XX XX XX
XXXXXX XXXX XX XXXXXX XX XX XX
XX XX XXXXX
XXXX XXXXXXXX XX XXXXX XXXX
Installing <NMS/NMC name> package
===========================================================================
--------------------------------------------------------------------------
.
The output depends by the chosen NMS or NMC
.
.
If you had started “Install.sh" with -confirm option, you have to confirm by entering “y [Enter]"
The time spent for installation of package depends by NMS.
The installation script can issues a message asking you for inserting a specific CD-ROM medium, just
replace CD in the driver with the requested one and the procedure will go on automatically.
Dismount the CD by entering:


2.5.2.2 Customize NMS
Meaningful for NMS Only
Now customize the NMS instances created in the system predisposal. It is not necessary to customize
the NMC because them are automatically performed together NMS.
For each NMS instance execute the following command procedure:

...,sys,root# cd /alcatel//Install_Wizard [Enter]
...,sys,root# ./Install.sh -custom <NMS name> [Enter]
Where: <NMS name> has to be replaced by NMS name to be customized.
........
......
....
..

Customization <NMS/NMC name> package
===========================================================================
LOADING: #################################################################
...
NOTE: Check processes running ...
=========================================================================
Customization <NMS/NMC name> package
=========================================================================
NOTE: Do you want to execute <NMS/NMC name> Custom? [y|n|q]
Reply “y[Enter]" to proceed in the NMS customization.
The “System, Instances,List" window will be shown on the screen after a few seconds, it allows you to
select the instance that you want customize:
Figure 18. List of existing instances
Select “Choose_one" and then “New-Instance" , then select “Apply & exit" in the Actions menu.
Then custom “Parameters Definition" window will be shown on the screen after a few seconds, it allows
you to set the relevant custom variables:

Figure 19. NMS Customize Window
N.B. To select the value for the following items you have to move the pointer on the box under the
label, then press the selection button of the mouse, a popup menu will be shown with the pos-
sible choices, moving the pointer choose one of them and release the mouse button:
System_Version, System_Instance_Rule, Master Kernel_Type and Driver_Version.
To customize the 1354RM you have to set the “System_Version" on new NMS/NMC (including version),
then enter the Instance identification number defined at predisposal time (see “Create NMS Instance"
paragraph 2.3.7.5.2 at page 93) in the input area under the label “System_Instance_Id".
If the Instance identification number does not correspond to the predisposed the customi-
zation script will create the data in a wrong place, and the /alcatel file system can get in over-
flow.
Set the “System_Instance_Rule" depending by the rule of the specific instance identification number.
You have to set it to “Master" when the instance is an Information Manager (IM), “Client" when the instance
is a User Service (US). “Master-Client" has to be set only with1359HA protection, when a client file system
has been manually created for 1353NM and 1354RM as shown in “1359HA Post Predisposal" 2.3.8 at
page 100.

The input fields identified by “System_Instance_Name" allows to define the name of the system within
the TMN-OS application.
For the Client instances it must be the same than the Master one. If you choose a name different
then the default customizing the master instance, don't you forget to enter it again for the client.
When you customize a NMS Client the related Master hostname have to be defined in /etc/
host file.
The “Master_HostName" is meningeal for “Client" and “Master-Client" instances. For the “Client" it must
be set with the hostname of the corresponding master instance, instead “Master-Client" is useful only for
1359HA, and it must refer the companion hostname (refer “1359HA Administration Guide" for more infor-
mation about companion concept).
For 1359HA Data Sharing you have to specify the Virtual Hostname.
Leave “Master_Kernel_Type“ and “Driver_Version" at default setting.
Then pulldown the menu “Action" (in the left upper corner), select “Apply & exit" to start the custom pro-
cedure.
A trace window will be open on the screen showing the customization progress.
Figure 20. NMS Customize trace window
The procedure will complete when the [Dismiss] button will be enabled.
The NMS installation and customization is now completed, before continue installation it is advisable to
check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_<NMS name>_*.log

2.5.3 Install and Customize 1353NM
This chapter explains how to install and customize the 1353NM on the server. This activity is performed
by the “Install.sh" script, the distinction is introduced to better explain the actions required by 1353NM,
in fact this software can be installed with two different kind of clients. its own and another one to permit
navigation to server with NR5 and NR6 1353SH.
This chapter shows in detail the 1353NM as example of an NMS installation and customiza-
tion, because it is the most complex of them.
2.5.3.1 Install 1353NM
To install 1353NM “Install.sh" procedure requires:

• A depot machine or distribution CD have to be available.
• The installing system must be authorized to retrieve the files from itself or from the depot
machine.
• When installing from depot machine: The hostname of the depot machine correctly defined in
the /etc/hosts file.
• You have to be able to login the system via GUI, in case of HP server the GoGlobal-UX have
to be authorized with the license code(see “1350 Administration Guide" [2] for more informa-
tion).
If the mentioned requirement are matched, the installation and customization can be started by:
a) Login the system via Graphical User Interface CDE as “root" user.
N.B. 1353NM CUSTOMIZATION WILL FAIL, IF THE INSTALL PROCEDURE IS STARTED

FROM A SHELL WHERE THE DISPLAY VARIABLE IS NOT SET.
b) Open a dtterm window.
c) Entering the following commands at dtterm prompt:

1) Insert the “SWP-1350MS_NR8.1PL2-DR4" volume 1/3 in the driver.
...,sys,root# ./Install.sh -install 1353NM -cdrom [Enter]

...,sys,root# ./Install.sh -install 1353NM [Enter]
Where:

For both installation methods:
N.B. To allow the recovery of errors it is possible to start “install" with option “-confirm", the
option causes the issues of confirm request message before executing each step in the
installation and configuration. Replying “no" to these questions you can skip the step.
d) The script start issuing the Alcatel-Lucent mask, then it will ask you some questions.
N.B. The output provided are just an example of the procedure behavior. THE INSTAL-
LATION CAN ISSUE DIFFERENT MESSAGES!
..........
........
......
....
..

XXXX XXXX XXXX XX XX XX
X X XXXX XXXX XX XXXX XX
XX XX XXXX XXXXXX XX XX XX
XX XX XXXXXXXXX XXXXXXXX XX XXXXX XXXX
Installing 1353NM package
===========================================================================
LOADING: ##################################################################
NOTE: Session started on: Thu Apr 20 14:30:40 METDST 2006
NOTE: Setting language to: C.iso88591 ...
===========================================================================
Installation 1353NM package
===========================================================================
***************************************************************************
NOTE: ${INSTALL_ROOT}/INSTALLER/Install 1353NM ${DEPOT_HOST}

file=${DEPOT_PATH}/1353NM_736_CORE_20SEP2005.tar.gz interactive=no

2.5.3.1.1 Installing 1353NM Software
Then the 1353NM distribution files will be insalled issiung a list of information like the following:
Image Installation requested for:
Product 1353NM
Format zip
Host hosta
File <file name>
Keep_data no
Check_sum 'NOT APPLICABLE'
Interactive no
PLEASE ENSURE LOCAL 1353NM SYSTEM IS NOT RUNNING
....
....
....
If you had started “Install.sh" with -confirm option, you have to confirm by entering “yes [Enter]"
The entire installation will require up to 80 minutes on a RP3410 server.
2.5.3.1.2 Installing 1353SH BKW NR5/6
When the 1353NM installation is completed, “Install" will prompt you the following question:

1353SH?[y|n|q]
1353SH 6.3 specific patch must be installed onto the 1353SH system to allow the inte-
gration with the 1354RM (see the 1353SH 5 and 1353SH 6 release notes).
If you have any NR5 or NR6 1353SH that have to provide the navigation feature from the installing system,
you have to reply with “y [Enter]" to this question.
N.B. This package is significant only if you have predispose a 1354RM item too.
2.5.3.1.3 Automatic Post Installation Script Execution
Some post installation activities are automatically executed before starting the 1353NM Custom.

2.5.3.2 Customize 1353NM
1353NM customization adapt software to the specific machine context, it is performed in two steps by
“Install.sh" script:
– Pre-custom Activities
– Custom.
To execute the 1353NM custom enter:

...,sys,root# ./Install.sh -custom 1353NM [Enter]
The script start issuing the Alcatel-Lucent mask, then it will execute the Pre-custom activities.
..........
........
......
....
..

Customization 1353NM package

===========================================================================
LOADING:
######################################################################
NOTE: Session started on: Tue Jul 19 15:11:54 METDST 2005

NOTE: Setting language to: C.iso88591 ...
===========================================================================
Customization 1353NM package

===========================================================================
Reply “y [Enter]" the following question issued by “Install.sh":

Do you want to execute 1353NM Custom ? [y|n] y [Enter]
The procedure starts tracing the custom execution:
======================================================================
NOTE: Executing 1353NM custom_cmd...
NOTE: runing </alcatel/Kernel/script/Custom>
NOTE: Executing 1353NM custom_cmd ...
NOTE: Basic Kernel Services (Connection Manager, Action Polling) Running.
.......... .

The “System, Instances,List" window will be shown on the screen after a few seconds. It allows you to
Figure 21. List of existing instances
You have to chose the instance you want to customize:
– if you are performing an installation from scratch: select “Choose_one" and then “New-Instance" to
define and customize 1353NM-7.4.5.
– if you are performing an upgrade: select “Choose_one" and then the instance you are upgrading,
identified during the software upgrade procedure.
Then select “Apply & exit" in the Actions menu.
The custom “Parameters Definition" window will be shown on the screen after a few seconds, it allows
Figure 22. 1353NM Customize Window

To customize the 1353NM you have to set the “System_Version" on 1353NM-7.4.5, then enter the
Instance identification number defined at predisposal time (see “Predispose for 1353NM Instance" para-
graph 2.3.7.4.2 at page 88) in the input area under the label “System_Instance_Id".
If the Instance identification number does not correspond to the predisposed one, the
customization script will create the data in a wrong place, and the /usr file system can
get in overflow.
You have to set it to “Master" when the instance is an Information Manager (IM), “Client" when the instance
is a User Service (US). “Master-Client" has to be set only with1359HA protection, when a client file system
has been manually created for 1353NM as shown in “1359HA Post Predisposal" 2.3.8 at page 100.
When you customize a 1353NM Client the related Master hostname have to be defined
in /etc/host file.
The Client Instance Identifier must be equal to the related Master!
N.B. Do not supply the hostname as System_Instance_Name
For the Client instances “System_Instance_name" MUST be the same than the Master
one. If you choose a name different than the default for the master instance, don't for-
get to enter it again for the client.
The “Master_HostName" is meningeal for “Client" and “Master-Client" instances. For the “Client" it must
be set with the hostname of the corresponding master instance, instead “Master-Client" is useful only for
1359HA, and it must refer the companion hostname (refer “1359HA Administration Guide" for more infor-
mation about companion concept).
For 1359HA Data Sharing you have to specify the Virtual Hostname.
The “System_Instance_Name" and “Master_HostName" must be different.
Leave “Master_Kernel_Type“ and “Driver_Version" at default setting.
Then pulldown the menu “Action" (in the left upper corner), select “Apply & exit" to start the customizing
procedure.

Figure 23. 1353NM Customize Trace
The 1353NM Custom script will show the “Custom Product Selection 1353NM <instance number>" win-
dow. This window allows to reduce the time spent to perform the custom by specifying a subset of the Net-
work Element, but the Element Managers of the Network Element families not configured can not be used
in the 1353NM. If you want to configure all the Element Managers simply leave the “CUST_TYPE" equal
to “FULL", otherwise change it to “PARTIAL", and select in the list the Network Element family you want
to configure.
Figure 24. 1353NM Custom Product Selection N.1

Figure 25. 1353NM Custom Product Selection N.2
procedure.
Please, ignore the warning messages shown in the following picture.
Figure 26. 1353NM Custom Warning
There are also some error messages that can rise that have also to be ignored, hereafter an example of
them:
NOTE: 07/07/06 14:14:27 - Executing 1353NM pre_custom_wa ...

ERROR: Software "MySQL" was not found on host "ipb022:/".
NOTE: 07/07/06 14:14:28 - 1353NM pre_custom_wa completed ...

and:
NOTE: Importing EmlUsm.....import definitions ...
Importing from file:/usr/Systems/1353NM_.../SEC/repository/secim-im...
ERROR: , line #494: Name Already Used.
Import problem: Name Already Used.
If your planning foresees more than one 1353NM Retix Stack, it is suggested to con-
figure now all the lan cards needed with SAM (for more information reference the offi-
cial HP documentation about the HP-UX product).
The 1353NM installation and customization is now completed, before continue installation it is advisable
/alcatel/Install_Wizard/log/Installation_1353NM_*.log
1) Dismount the CD by entering:

2) Remove the CD from the driver.
2.5.3.3 How to Proceed with More Than One 1353NM Instance
The 1353NM foresees to have more than one client instance on board of 1354RM, the reason is: the
1354RM must have a 1353NM client for each 1353NM Master it has to supervise. In this case you have
to install the 1353NM software once and customize any predisposed instance. The “Install.sh" allows to
custom the first one, if you have more than one, you have to start the OS-Kernel Custom procedure for
each one of the instance but the first.
To run OS-Kernel Custom procedure:

– Login the system as root with CDE GUI.
– Open a graphical “terminal" .
A window like Figure 22.will be open, enter next instance identification data as shown in the paragraph
“Customize 1353NM" 2.5.3.2 at page 124, and proceed customizing the next 1353NM.
Execute the Custom for all instances.
– Enter the commands:

...,sys,root # ./Install.sh -custom 1353NM [Enter]

2.5.3.4 Customize 1353SH BacKWard Compatibility Tool
The 1353SHBKW tool is useful to perform navigation from NR7.0 Network Managers (1354) on NR5 or
NR6 Element Managers. It is an optional package installed together 1353NM replying “y[Enter]" to the fol-
lowing question also shown at paragraph 2.5.3.1.2“Installing 1353SH BKW NR5/6" at page 123:

1353SH? [y|n|q]
The 1353SH BKW need some data to be able to perform its tasks, this data have to be created as a
1353SH 7.0 instances, this argument had been already introduced during 1353NM predisposal at para-
graph 2.3.7.4 page 87. For each the created 1353SH 7.0 instance you have to perform the data custom
script as shown in this paragraph:
To run OS-Kernel Custom procedure:
– Login the system as root with CDE GUI.
– Open a graphical “terminal" .
– Enter the commands:

...,sys,root # ./Install.sh -custom 1353NM [Enter]
The “System, Instances,List" window will be shown on the screen after a few seconds, it allows you to
Figure 27. 1353SHBKW 7.0 Custom System Selection.
Select “Choose_one" and then “New-Instance", then select “Apply &exit" in the Actions menu.
The custom “Parameters Definition" window will be shown on the screen after a few seconds, it allows

Figure 28. 1353SHBKW 7.0 Custom Parameters Set-up.
To customize the 1353NM you have to set the “System_Version" on 1353SH-7.0, then enter the Instance
identification number defined at predisposal time (see “Predispose for 1353NM Instance" paragraph
2.3.7.4.2 at page 88) in the input area under the label “System_Instance_Id".
If the Instance identification number does not correspond to the predisposed the cus-
tomization script will create the data in a wrong place, and the /usr file system can get
in overflow.
You have to set it to “Client" .

N.B. The “System_Instance_Name" must not be equal to the hostname.
The “System_Instance_Name" must be the same than the 1353SH 5 or 6 Master one.
The “Master_HostName" must be specified, and it must be declared in /etc/hosts file, and
the host have to be reachable.
The “System_Instance_Name" and “Master_HostName" must be different.
Set the “Master_Kernel_Type“ to “EXTERNAL" and “Driver_Version" at default setting.
procedure.
Figure 29. 1353SHBKW 7.0 Custom Execution window.
The procedure will complete its task in about 10 minutes on a L1000 server, issuing some foreseen warn-
ing messages shown in the Figure 29.Please ignore them.
The 1353SH installation and customization is now completed, before continue installation it is advisable
/alcatel/Kernel/maintenance/log/Custom.log`

2.5.4 Install and Customize 1353NM 7.3
Meaningful only for HP 9000 machine.
This chapter explains how to install and customize the 1353NM 7.3 on the server. This installation has
to be performed only in case of 1353NM / 1353NM 7.4 cohosted configuration, in order to manage QB3*
network elements. This activity is performed by the “Install.sh" script.
2.5.4.1 Install and Customize 1353NM 7.3
Install and customize 1353NM by executing:
a) Login the system via Graphical User Interface CDE as “root" user.
N.B. 1353NM CUSTOMIZATION WILL FAIL, IF THE INSTALL PROCEDURE IS STARTED

FROM A SHELL WHERE THE DISPLAY VARIABLE IS NOT SET.
b) Entering the following commands at dtterm prompt:

For installation from DVD:
1) Insert the “SWP-1350MS_NR8.1PL2-DR4 " volume 1/3 in the CD/DVD driver.

...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM[Enter[
...,sys,root# ./Install.sh -reveal 1353NM -cdrom [Enter]

...,sys,root# ./Install.sh -reveal 1353NM [Enter]
Where:
The procedure will start the packages installation.
Whenever requested to select between 1353NM 7.4 and 1353NM 7.3 versions, select 7.3.
The script start issuing the Alcatel-Lucent mask, then it will ask you some questions.
Then the procedure proceed like for the 1353NM 7.4 installation, so the procedure will request a confirm
for the execution of the customization tool (Custom): confirm the operation and supply all the data required
by the Custom GUI and apply the customizations, configuring the required 1353NM instance.

Check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_1353NM_*.log

2.6 Mandatory Installation Changes
In case you are installing 1354RM and/or 1354BM ETH master instance (IM), the following configuration
changes are mandatory.
2.6.1 .ariesrc Installation Changes

This action must be performed on HP Integrity Itanium 2 server hp-ux 11i V2.
This activity will require the system reboot to be completed.
2.6.1.1 1354RM .ariesrc creation
If the 1354RM Master istance is present in your configuration you must create .ariesrc in “root” user home
directory and “snml” user home directory by entering the hereafter command:
...,sys,root # echo “/ -heap_ssz 402664” > ~snml/.ariesrc [Enter]

...,sys,root # echo “/ -heap_ssz 402664” > /.ariesrc [Enter]
2.6.1.2 1354BM ETH .ariesrs creation
If the 1354BM ETH Master istance is present in your configuration you must create .ariesrc in “bmml” user
home directory by entering the hereafter command:
...,sys,root # echo “/ -heap_ssz 300000” > ~bmml/.ariesrc [Enter]
2.6.1.3 hp-ux kernel review
Both 1354RM and 1354BM ETH requires to increase the amount of memory space allowed to Aries PA-
Risc emulator, and the number of allowed thread at process and system level, this can be done by entering
the hereafter commands:
...,sys,root # kctune pa_maxssiz_32bit=468713472 [Enter]
NOTE: The configuration being loaded contains the following change(s)

that cannot be applied immediately and which will be held for
the next boot:
-- The tunable pa_maxssiz_32bit cannot be changed in a dynamic
fashion.
WARNING: The automatic 'backup' configuration currently contains the
configuration that was in use before the last reboot of this
system.
==> Do you wish to update it to contain the current configuration
before making the requested change? yes
* The automatic 'backup' configuration has been updated.
* The requested changes have been saved, and will take effect at
next boot.
Tunable Value Expression
pa_maxssiz_32bit (now) 83648512 Default
(next boot) 468713472 468713472

...,sys,root # kctune nkthread=60000 [Enter]

* The requested changes have been applied to the currently
running system.
Tunable Value Expression Changes
nkthread (before) 30000 30000 Immed
(now) 60000 60000
...,sys,root # kctune max_thread_proc=2048 [Enter]

running system.
max_thread_proc (before) 1500 1500 Immed
(now) 2048 2048
...,sys,root # shutdown -r now [Enter]
2.6.2 1354RM Installation Changes
This activity must be performe on both server hp-ux 11i V2, Itanium and Pa-risc.
A 1354RM installation, in LARGE configuration, requires to increase the “shmmax” parameter. This can
be done by entering the hereafter commands:
...,sys,root # kctune shmmax=4294967296 [Enter]
WARNING: The automatic 'backup' configuration currently contains the

configuration that was in use before the last reboot of this
system.
==> Do you wish to update it to contain the current configuration
before making the requested change?
Answer y:

running system.
shmmax (before) 1073741824 Default Immed
(now) 4294967296 4294967296

2.7 Final Integration
Now the installation is completed, but the installed NMS still need to be configured to be able to start, the
activity is performed by “System Configuration" tool of each application, because this you have to refer
to the Administration Guide of each NMS installed to know how to perform the specific NMS process con-
figuration.
N.B. 1359HA requires it's own system configuration, refer to “1359HA Administration Guide"
for more information.
VERY IMPORTANT!!
When all the TNM machines have been configured in stand-alone, you have to run on
each one of them the final integration script!
2.7.1 Final Integration Script

On each just installed machine:
1) Before start, you must be sure that all systems involved are already installed, customized and
configured by system configuration tool. To easy identify the potential involved system opening
the “TMN OS" tool available on display front panel of any Alcatel-Lucent NMS operator session.
2) Login as root user.
3) Start the global integration script by entering /alcatel/Kernel/script/UpdateNetworkConnec-

tions.pl and answer to the questions:
...,sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl [Enter]
The procedure starts tracing the integration execution issuing an output like the following:
NOTE: Started in Interactive mode on ALL TMN Systems locally defined

NOTE: Updating Required Client Instances...
NOTE: Starting Required Inter-System Integrations...
NOTE: 1353NM_1: No Integratable System defined. Skipping 1353NM_1.
NOTE: 1354RM_3: Detected the following integrated Systems: 1353NM_1
NOTE: 1354RM_3: 1353NM_1 Already integrated. Re-Applying Integration.
...
...
For each system that have to be integrated the following question can be issued (for example):
1354RM_1-7.4.9: Run the Integration of 1353NM_1-7.4.5? [y/n]
If you reply “y" the system will be integrated, and the procedure will issue also these other questions:
1354RM_3-7.4.9: Run the PLT Integration of 1353NM_1-7.4.5? [y/n]

1354RM_3-7.4.9: Run the Backup/Restore Integration of [y/n]
1354RM_3-7.4.9: Run the Navigation Integration of 1353NM_1-7.4.5? [y/n]

Generally you have to reply “y" to all of them, with the following exception:
– when procedure asks you to authorize the integration between a 1354RM and 1354BM ETH,
where you MUST reply NO to PLT and Backup/Restore integration, like the following example:
1354RM_1-7.4.7: Run the PLT Integration of 1354BMETH_1-8.1.4? [y/n] n

1354RM_1-7.4.7: Run the Backup/Restore Integration of 1354BMETH_1-8.1.4? [y/n] n
1354RM_1-7.4.7: Run the Navigation Integration of 1354BMETH_1-8.1.4? [y/n] y
– and, when procedure asks you to authorize the integration between a 1354RM and 1354BM PR,
where you MUST reply NO to PLT and Backup/Restore integration, like the following example:
1354RM_3-7.4.7: Run the PLT Integration of 1354BMPR_1-8.1? [y/n] n

1354RM_3-7.4.7: Run the Backup/Restore Integration of 1354BMPR_1-8.1 [y/n] n
1354RM_3-7.4.7: Run the Navigation Integration of 1354BMPR_1-8.1? [y/n] y
Warning and error messages will advise you that the remote system is not reachable or not properly con-
figured, and the machine will be not integrated. If such kind of messages are issued, identify the problem,
fix it, and run again the integration script.
Example:
WARNING: 1354RM_3-7.4.9: Connection problems with <hostname>. Skipping Update.
When the procedure will be successfully executed, you will be able to use all the Network Management
System features.

2.7.2 Alarm Surveillance Federation
The Alarm Surveillance federation is an OS-Kernel optional feature that allows to see the alarms of all
NMS client installed on system in a single Alarm Surveillance graphical interface.
To be able to perform the AS federation you must have two or more NMS Client and/or Master instances.
The command syntax is:
AS-USMFederation.pl -name <ASFN> [-sec <Sec Inst>] <NMS Inst List>
Where:
- name <ASFN>Specifies the AS Federation Name, that will be shown by “TMN OS" tool
and AS USM Window title.
N.B. No special characters are allowed in the AS USM Window title.
-s <Sec Inst>(optional)This option allows to specify the NMS instance will be referred by AS-USM
for granting network object access permission (SEC). This feature was
mandatory until NR7.1T, when AS did not support the multiple SEC. With
NR7.1D/7.2 specifying this option you force AS to refer just one SEC,
reducing the AS federation access authorization to the operators defined
in the indicated NMS instance.
<NMS Inst List>Specifies the NMS instance list that will be part of federation. with the
followong syntax:
<NMS_NAME>_<NMS_INSTANCE>-<NMS_VERSION>
Example:
1354RM_2_7.4.9
You can create different AS Federations, by running the command with different ASF names.
The command must be executed by “root" user, and the file is located in “/usr/Systems/Global_Instance/
AS/script/", so to start the command you have to logging the system as “root" and enter:
...,sys,root # /usr/Systems/Global_Instance/AS/script/AS-USMFederation.pl \ Enter]

-name <ASF Name> <NMS Instance List>[Enter]
This is an example of two AS federation performed on a system equipped with: 1354RM Master instance
number 2, three 1353NM Client instance number 1, 2 and 3. The latter will be call “RegionEst" involving
the 1354RM and 1353NM instance number 1, and the former will be call “RegionWest" involving the
1354RM and 1353NM instance number 2 and 3.
...,sys,root # /usr/Systems/Global_Instance/AS/script/AS-USMFederation.pl \[Enter]
-name RegionEst 1354RM_2_7.4.9 1353NM_1_7.4.5 [Enter]
...,sys,root # /usr/Systems/Global_Instance/AS/script/AS-USMFederation.pl \[Enter]
-name RegionWest 1354RM_2_7.4.9 1353NM_2_7.4.5 [Enter]

3 TroubleShooting
Here after is shown how to solve some trouble can occur during the installation, and how to proceed when
possible.
3.1 Identify a Failure Condition

Before proceed with the troubleshooting it is suggested to identify the problem. It also important to dis-
tinguish between messages issued during the normal behavior and real error messages.
These is a messages issued at login time to advise the operator that an installation activity is in progress:
********************* WAIT - INSTALLATION IN PROGRESS *******************
Do not alter environment, check log file in /SCINSTALL/scinstall.log
***************************************************************************
This is not an error message, it just advise you that an installation activity is in progress, in this case it is
better wait until the activity will be terminated.
The following message will be issued when an error is met during the automatic software installation.
**************** THIS SYSTEM IS NOT CORRECTLY INSTALLED *****************
***************************************************************************
N.B. Some system reboot are foreseen to correctly carry on the installation, that means don't worry
if the system reboot automatically.
3.2 Failure installing a HP-UX

HP-UXTM Operating System is the first software installed, it is stored in some “dump" files automatically
restored by the installation procedure. A fault during the HP-UXTM installation can not be recovered the
installation have to be started from the beginning.
The HP-UXTM installation will be completed when the following message will be shown on the console:
******* The HP-UX software has been successfully restored *******
But the error recovery will be possible only after the first reboot of the system performed just after the mes-
sage:
***** The System reboots automatically, please wait *****

TroubleShooting 3AL 89041 BAAA Edition 04 141/200
3.3 Recoverable Faults
Hereafter some example of recoverable error that can occur during platform software installation.
If no one of them help you to fix the problem, do not attempt fix the error in different ways, but refer to Alca-
tel-Lucent Technical Excelence Center.
3.3.1 Recoverable Faults Installing Software

Recoverable are the faults occurred before the start of installation, or during the analysis, in this case the
following message will be shown at login time:
******************* THIS SYSTEM IS NOT CORRECTLY INSTALLED *******************
***************************************************************************
An example is the following messages in the /SCINSTALL/scinstall.log file:
======= 08/05/03 16:41:44 METDST BEGIN swinstall SESSION

(non-interactive) (jobid=tlvhhx-0027)
* Session started for user "root@tlvhhx".
* Beginning Selection
ERROR: "tlvhhx:/": This target or source is already in use either
within this same session or by another session. A read or
write lock was denied.
* Target connection failed for "tlvhhx:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is tlvhhx:/var/adm/sw/swagentd.log).
* Selection had errors.
======= 08/05/03 16:41:44 METDST END swinstall SESSION

(non-interactive) (jobid=tlvhhx-0027)
EXIT CODE: 1
SCinstall: Error end SCINSTALL
In this case you have to identify the reason of the fault (example: cd-rom switched of, action on the target
depot, etc.), remove it, then recover the fault trying to preform again the failed action following this pro-
cedure:
– Logging the system as “root" user.
– Change the default directory on “/SCINSTALL/execution":

...,sys,root # cd /SCINSTALL/execution [Enter]
– Locate the file “*.in_progress" and rename it removing extension “.in_progress" :

...,sys,root # ls *.in_progress [Enter]
...,sys,root # mv <file_name>.in_progress <file_name> [Enter]
• for example:
...,sys,root # ls *.in_progress [Enter]

142/200 3AL 89041 BAAA Edition 04 TroubleShooting
01001SC.SCstdinstall.in_progress
...,sys,root # mv 01001SC.SCstdinstall.in_progress 01001SC.SCstdinstall [Enter]
– If choosen software location is no more available, you can change it using scChangeSource script,
that allows to review your previous choice.
– Reboot the system to allow the correct
The procedure will try again the installation of the failed package.

3.3.1.1 Failure in File System Extension
If an error occurs extending a file system, the installation is interrupted and the following message is
issued each time you login the system:
Error during execution of scextendfs.reboot

**************************************************************************
Look at the “/SCINSTALL/scinstall.log" file to know which is the meet problem and how to fix it before pro-
ceed.
When the error has been recovered remove the following files:
– /SCINSTALL/scextendfs.error_msg to remove the message to remove the message at login time.
– /SCINSTALL/data/scextendfs.env to prevent the extension retry at the next reboot.
– /sbin/rc1.d/S099scextendfs.reboot to prevent the extension retry at the next reboot.
3.3.1.2 Failure in File System Deletion
If an error occurs deleting a file system, the installation is interrupted and the following message is issued
each time you login the system:
Error during execution of scextendfs.reboot

**************************************************************************
Look at the “/SCINSTALL/scinstall.log" file to know which is the meet problem and how to fix it before pro-
ceed.
When the error has been recovered remove the following files:
– /SCINSTALL/scdeletefs.error_msg to remove the message to remove the message at login time.
– /SCINSTALL/data/scdeletefs.env to prevent the deletion retry at the next reboot.
– /sbin/rc3.d/S999scdeletefs.reboot to prevent the deletion retry at the next reboot.

3.3.2 Recoverable Faults Managing SWP
“scmanageswp" script can exit for some reason, the situation in which is possible to operate to exit from
the error are the following:
• The procedure exit with error because there is a pending installation process in progress, see
paragraph 3.3.2.1.
• The procedure has been abnormally terminated, see paragraph 3.3.2.2.
3.3.2.1 Pending Installation Process
At start-up time “scmanageswp" checks if there is any pending installation process,
=>>> ERROR : SCINSTALL System startup script file detected.

This indicate a pending installation process !!!
=>>> ERROR : Current program terminated.
Execute the workaround describes on paragraph 3.3.1 at page 142,for recover the mistake.
3.3.2.2 scmanageswp Abnormally Terminated
“scmanageswp“ uses a flag directory to prevent multiple execution from different shells, if you start the
script when another it is already running it will terminate issuing the message:
=>>> ERROR : SCMANAGESWP procedure already running on system.

Multi activation is not allowed !!!
=>>> ERROR : Current program terminated.
May occurs the flag directory it is not removed, for example when it is executed via telnet and a3 network
failure abnormally terminated the connection, in this case you have to manually unlock the synchroniza-
tion mechanism. Before proceed with the unlock you have to check there are no other “scmanageswp"
running instance by entering the commands:
...,sys,root # export UNIX95=true [Enter]
...,sys,root # ps -fC scmanageswp [Enter]
N.B. Be careful, double check the command before press [Enter], because the “ps" command
parameter can not be checked.
If “ps" command does not issue any line you can proceed with the manual unlock by entering the com-
mand:
...,sys,root # rm -r /tmp/.scswpsession [Enter]
Then start again “scmanageswp".

3.3.2.3 Install.sh Abnormally Terminated
Meaningful during an installation from CD only.
Using the command "Install.sh <NMS/MNC name> -cdrom" to install a generic NMS/NMC Software
(1353NM, 1354RM, etc. - see table in parag. 2.1.4.2 at page 40) from CD, could be displayed the following
error message:
ERROR: cd label is blank (environment variable $SCI_KIT_LAB)
In this case, is necessary to execute the following commands:
a) Dismount the CD currently mounted by entering:

...,sys,root# umount /SD_CDROM [Enter]
b) Remove the CD from the driver.
c) Insert the Software Distribution CD in the CD driver.
d) Mount the CD at /SD_CDROM directory:

...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM[Enter[
e) Execute the following W/A in order to manage the installation from DVD:
...,sys,root# export SCI_KIT_TYP=ANY [Enter]
f) Start again the installation script entering:

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

3.4 Kerberos Problems
There are two Kerberos known problems with possible troubleshooting.
3.4.1 Kerberos kdcd Process Not Running

It has been experienced the failure of Kerberos kdcd daemon process, the result of this failure is that no
activities can be performed on the system. To check if the kdcd process is running you can enter the com-
mand:
...,sys,root # ps -edf | grep kdcd[Enter]
The output have to be like:

,sys,root # ps -edf | grep kdcd
root 573 1 0 12:20:23 ? 0:01 /opt/krb5/sbin/kdcd -l /dev/null
root 916 573 0 12:20:27 ? 0:04 /opt/krb5/sbin/kdcd -l /dev/null
root 9416 9363 0 16:21:30 pts/ta 0:00 grep kdcd
The first workaround applicable is try to start it again by entering the command:
...,sys,root # /sbin/init.d/krbsrv start [Enter]
If after the manual re-start the process is not able to stay running, check the size of the file “/opt/krb5/tmp/
pf/kdcd.pid" . If it is zero byte length you have to delete it and the file “/vat/tmp/rc_krbkdcd“ one:
...,sys,root # rm /opt/krb5/tmp/pf/kdcd.pid [Enter]
...,sys,root #rm /var/tmp/rc_krbkdcd [Enter]
Then try again to start kdcd.

3.4.2 Kerberos kdcd High CPU Consuming

Has been observed that some times the kdcd process spends a long time to startup at CPU bound, the
resulting behavior is like the kdcd fail show in the previous paragraph, but the kdcd process is running CPU
bound (with top command it is shown with a CPU percent usage higher than 90%). in this case you have
to check the size of the file “/vat/tmp/rc_krbkdcd", if it is larger than 10Mbyte you have to:
a) Login as root user.
b) Stop the kdcd process by entering the command:

...,sys,root # /sbin/init.d/krbsrv stop [Enter]
c) Remove the “/vat/tmp/rc_kbrkdcd" file:

...,sys,root #rm /var/tmp/rc_krbkdcd [Enter]
d) Start the kdcd process by entering the command:


3.5 Device Full
Sometimes a file systems can get full, this situation can occur because different reasons, hereafter some
of them are explain.
3.5.1 Devise Full on /var Mounted File System

If the space on /var mounted file system is over, you can get same extra space by removing the patch
saved files.
N.B. If you remove the patch saved files, no one of these patches could be removed any more.
To remove these files you have to:
a) Login the system as “root" user,
b) Remove the files by entering:

...,sys,root # rm -r /var/adm/sw/save/*[Enter]
c) Cleanup the patch status by entering:

...,sys,root # cleanup -s [Enter]
3.5.2 Device full on /usr and /home

These two file systems can get full because of core file created by program termination, in this case is
suggested to remove or copy in a different location the core files.
If the core file removal is not enough to reach an appreciable amount of free space, it is possible to extend
the file system. The file system extension can be executed when there are not allocated physical extent
on the logical volume or there are unused hard disks, and it is possible to perform a reboot of the system.
The command “scextendfs -i" can be used to check how many free Mbyte are still available on the current
volume group configuration.
...,sys,root # scextendfs -i [Enter]
The command output will be like the following:
___________________________________________________________________________
Volume Group Free Space
vg00 FreePE 172 (MBytes 11008) (pvg0=172)

___________________________________________________________________________
Hardware detection in progress, please wait ........


___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________
c2t1d0 34720 0/1/1/0.1.0 _(free)_ ______ __________
___________________________________________________________________________
N.B. If you have a disk mirror protection, the file system extension can ask for more than one
disk.
Before proceed within a 1359HA Data Sharing environment you have to check that the disks
you want to use are not already in use from a different system.
If all precondition are met, you can enlarge the file system by entering the command:
...,sys,root # scextendfs <file system mount point> <desired free space> [Enter]
Analyze Mount Point:"/usr"

Request free MegaByte(s): 100
Evaluate size MegaByte(s): 1248

Extend Mount Point "/usr" to 1248 MByte
"/usr" successfully extended, new size will be available on next reboot
___________________________________________________________________________
System need reboot x complete extension of file system current in use

___________________________________________________________________________
The message “System need reboot x complete extension of file system current in use" means that the
extension will not available until system reboot.

3.6 Inittab Process Not restarting
Sometimes the processes specified in “/etc/inittab" file whit option “respawn" are not re-spawned cor-
rectly, it this case can be useful perform the following procedure:
a) Login the system as “root" user,

b) Replace the keyword “respawn" with “once" in the line corresponding to the not started process.
c) Ask init to re-read the configuration file by entering:
...,sys,root # init q [Enter]
d) Restore back the keyword “respawn" instead of “once" just modified.
e) Ask again init to re-read the configuration file by entering:
...,sys,root # init q [Enter]

3.7 Installing and Configuring Mirror Disk/UX
Sometimes the Mirror Disk/UXTM is not chosen at HP-UX installation time, and someone decide to install
it later, in this case you can apply this procedure.
3.7.1 Mirror Disk/UX Installation Prerequisite.
The Mirror Disk/UXTM requires the appropriate HP license to authorize the its usage, and the system shut-
down due to two reboots.
3.7.2 Mirror Disk/UX Configuration Prerequisite
To be able to properly configure Mirror Disk/UXTM you must be sure to have enough hard disk available
to store another copy o the entire file system. The highest level of availability is reached by assigning hard
disks belonging to different SCSI chains. Refer to paragraph 2.2.14.1 “Disk Mirror Configuration Policy"
at page 68.
3.7.3 Mirror Disk/UX Installation
When you not choose the mirror configuration, the Mirror Disk/UXTM is not installed. Here the procedure
to manually install it:
a) Login the system as root and ask all the user to log out the system.
b) Insert media:
• “SWP-OSCONF_BOOT-V7.1.2” (1/1 for DVD, 1/2 for CD media) for PA-RISC architecture
• “SWP-OSCONFUX_BOOT-V8.1.2” DVD for ITANIUM architecture
in the device driver and mount it by entering:
...,sys,root # mount -o rr /dev/dsk/<cdrom device file> /SD_CDROM [Enter]
c) To install the Mirror DIsk/UXTM and Mirror Disk/UXTM patches, you have to enter the following com-
mand, but be careful because the machine will be automatically rebooted:
...,sys,root # swinstall -s /SD_CDROM/MirrorDisk.sd -x autoreboot=true LVM [Enter]
When the system will prompt you for login check in /var/adm/sw/swagent.log for any error met in the soft-
ware of patch installation.

4 Add New NMS/NMC
This chapter describes how to add a new NMS, a new NMC or a new NMS instance to an existing Alcatel-
Lucent TMN system.
4.1 Prerequisites
Before proceed in new software installation can be operate only if the prerequisite shown in this paragraph
are met. The prerequisite evaluation is require to do not compromise an existing system with an incom-
patible software or simply get in trouble during the installation.
4.1.1 Previous installation status.

The entire installation process is based in two step, predisposal and installation. These two actions must
be execute in the order, when the machine is predisposed for a specific software, this software have to
be installed before proceed with a new predispose action. If this sequence is not respected, the installation
process is not guarantee. That means, before proceed in the predisposal for the new NMS or NMC, you
have to check that there are no predisposed NMS and NMC not yet installed. If any of them is present,
please install them or delete the related Software Package (SWP) predisposal with scmanageswp tool.
4.1.2 Network Release Compatibility

You can install any NMS or NMC of the same Network Release level.
For installation of NMS of different network release refer to the specific release notes.
4.1.3 Disk space requirements

Disk space requirements are specified in paragraph B.3 at page 165.
4.1.4 Reboot Planning

The installation of a new NMS or a new NMS instance creation requires the system reboot, the only excep-
tion to this role is 1353NM client, that means before start the system predispose you have to plan a system
reboot.

Add New NMS/NMC 3AL 89041 BAAA Edition 04 153/200
4.2 Install a new NMS/NMC
This paragraph describes which paragraphs of the previous chapters you have to follow to install a new
NMS on an existing TMN machine.
The 1359HA NMC has specific instructions
a) Predispose the system for both software package and instance for new NMS/NMC using “scman-
ageswp" tool has shown in paragraph: “Start the SWP Manager Script" 2.3.7.1 at page 84, when
needed “Predispose for 1353NM" 2.3.7.4 at page 87, and “Predispose for other NMS/NMC" 2.3.7.5
at page 91.
N.B. The system predispose can require the re-boot of hp-uxTM.
b) Add the NMS/NMC related license in the Poseidon license file of the license server machine.
c) Force the license server machine to load the new license by entering the following command on one
of them:
...,sys,root # /sbin/init.d/poseidon reread [Enter]
d) Install the Alcatel-Lucent software following instruction shown in paragraphs: “Install NMS or NMC"
2.5.2.1 at page 116.
e) Execute the custom for each NMS instance and/or for each NMC just installed following paragraph
“Customize NMS Instance or NMC" 4.2.1 at page 154.
f) Then proceed in the process configuration as described in the specific administration guide.
g) Perform the TMN system “Final Integration" shown in the paragraph 2.7 at page 137.
4.2.1 Customize NMS Instance

The customization of additional software instances or optional components on operational system are
risky actions, because mistake can compromise running processes, for this reason the procedure has to
follow with the maximum attention.
Within the additional software and instances it is possible to distinguish three different cases:
1) Customize a new just created NMS instance.

2) Customize 1354RM to integrate ETH-Mediator.
3) NMS upgrade instance for 1359IOO and 1359ISN

154/200 3AL 89041 BAAA Edition 04 Add New NMS/NMC
4.2.1.1 Customize NMS Instance
This activity can be carried on without interference with other NMS on the system, just following this
instruction shown in “Customize NMS" paragraph 2.5.2.2 at page 118.
4.2.1.2 Customize 1354RM to integrate ETH-Mediator.
When you install the ETH-Mediator function on a system where the 1354RM Master is already present,
to integrate this new component you have to:
1) Login system as 1354RM administrator and shutdown the application via PMC.
2) Execute the application data backup of 1359ISN, when 1359ISN is present.
3) Log out 1354RM administrator session, and login as root.
4) Execute the 1354RM Master customizing following this instruction shown in “Customize NMS"
paragraph 2.5.2.2 at page 118.
5) Log out root session, and login as 1354RM administrator.
6) Restore 1359ISN saved data, when needed.
7) Login system as 1354RM administrator and start-up the application via PMC.
4.2.1.3 NMS upgrade instance for 1359IOO and 1359ISN
When 1359IOO and 1359ISN are installed on already operating system, it is required to update also the
NMS instances that have to be able to integrate these NMC, by executing this procedure:
1) Login system as root.
2) Enter the following commands:

...,sys, root # cd /alcatel/Install_Wizard[Enter]
...,sys, root # ./Install.sh -custom <NMC Name>[Enter]
3) Verify that no errors are displayed on standard output (warnings can be ignored).
4) In case of errors, after upgrade instance completion, you can check the following trace files:
/alcatel/Install_Wizard/log/Installation_ <NMC Name>_#.log
/alcatel/Kernel/maintenance/trace/updateInstance.trace
This activity can be execute on a running system.
4.2.2 NMC Special Insertions

The Network Management Components has no instances, but they are plugged in existing NMS, this
activity is automatically performed by NMS customization when the NMC is present on the installation
tree, or by Install.sh procedure specifying “-custom".
4.2.2.1 For 1359ISN
1359ISN customize script revert the configuration data to the default ones, because this action can be
executed automatically by 1354RM custom or system configuration, to prevent loosing any configuration
change, it is advisable to perform a 1359ISN data backup each time you change the data, to be able to
restore them in case of reset.

4.2.3 1359HA Specific Instructions
The 1359HA 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 addi-
tion.
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 30.
hosta
1354RM Client
1353NM Client
hostb hostc
1354RM Master 1353NM Master
1353NM Client
Figure 30. Add 1359HA 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 1359HA you have to identify the machine that has to be subjected
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 30.the suggested 1359HA configuration is shown
by Figure 31.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-mas-
ter relationship when the NOC is operational, the striped ones when the DRC takes the control.

hosta
1359HA
1354RM Client
1353NM Client
hostb hostb1
1359HA
1359HA
1354RM Master 1354RM Master
1353NM Client 1353NM Client
hostc hostc1
1359HA
1359HA
1353NM Master 1353NM Master
Network Operation Centre Disaster Recovery Centre
Figure 31. Add 1359HA Final configuration Example

4.2.3.1 How to install 1359HA
This paragraph provides the guidelines for installing 1359HA on an existing TMN system referring the pre-
vious 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 1359HA 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 1359HA SWP and create a 1359HA IM instance for each local NMS
IM instance subjected to resilience protection, and 1359HA US instance for each client referring
a resilient IM.
3) Install 1359HA following the instruction shown by paragraph 2.5.2.1 “Install NMS or NMC" at
page 116.
4) Execute any foreseen pre-customization actions for 1359HA following the instruction of para-
graph “Customize NMS" 2.5.2.2 at page 118, 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 1359HA in distributed configuration.
Customize and Configure 1359HA in cohosted configuration.
Customize and Configure 1359HA in Presentation only configuration.
4.2.3.2 Customize and Configure 1359HA in distributed configuration.
This paragraph is applicable to Alcatel-Lucent TMN system where there is just one NMS Master installed
on the system or 1354BM ATM and 1354BM ETH cohosted.
For each NMS Master subjected to resilience protection:
1) Update instance data description including 1359HA by entering:

...,sys,root # /alcatel/Kernel/script/updateInstance.pl \[Enter]
-sys <NMS_SYSTEM> -inst <NMS_INSTANCE> -type NMC \[Enter]
-comp HA -skipconfig[Enter]
2) Configure 1359HA subsystem in the scope of instance process configuration for each NMS IM
subjected to resilience protection (refer to “1359HA Administration Guide" for more informa-
tion).

4.2.3.3 Customize and Configure 1359HA in cohosted configuration.
This paragraph is applicable to Alcatel-Lucent TMN system where:

– A 1353NM Master is installed with one of the following NMS Master: 1354RM, 1354BM ATM or
1354BM ETH
– A 1354RM Master is installed with one of the following NMS Master: 1354BM ATM or 1354BM ETH
a) For each 1354BM Master subjected to resilience protection, execute the procedure described at
paragraph 4.2.3.2 “Customize and Configure 1359HA in distributed configuration" .
b) For each 1354RM Master subjected to resilience protection, when there is no 1354BM Master
cohosted, execute the procedure described at paragraph 4.2.3.2 “Customize and Configure 1359HA
in distributed configuration" .
c) For each 1354RM Master subjected to resilience protection, when any 1354BM Master is cohosted,
execute the following procedure:
1) Create an additional 1354RM Client instance file system as shown at paragraph 2.3.8.2 “Man-
age 1354RM cohosted with any 1354BM NMS“ at page 101.
2) Customize again the 1354RM specifying “Master-Client" as “System_Instance_Rule" (see

2.5.2.2 at page 118 for more information).
3) Create an additional 1354BM Client instance file system as shown at paragraph 2.3.8.2 “Man-
age 1354RM cohosted with any 1354BM NMS“ at page 101.
4) Customize again the 1354BM specifying “Master-Client" as “System_Instance_Rule" (see

2.5.2.2 at page 118 for more information).
tion).
d) For each 1353NM Master subjected to resilience protection, when any 1354 Master is cohosted,
execute the following procedure:
1) Create an additional 1353NM Client instance file system as shown at paragraph 2.3.8.1 “Man-
age 1353NM cohosted with any 1354 NMS“ at page 101.
2) Customize again the 1353NM specifying “Master-Client" as “System_Instance_Rule" (see at

2.5.3.2 page 124 for more information).
tion).

4.2.3.4 Customize and Configure 1359HA 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 1359HA by entering:

...,sys,root # /alcatel/Kernel/script/updateInstance.pl \ [Enter]
-sys <NMS_SYSTEM> -inst <NMS_INSTANCE> -type NMC \ [Enter]
-comp HA -skipconfig [Enter]
2) Configure the 1359HA within the NMS instance by entering:

...,sys,root # /usr/System/<NMS Instance>/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: 1353NM).
<NMS Instance ID>means the instance ID number.
<NMS Version>means the NMS version (example: 7.0)
Example:
...,sys,root # /usr/System/1353NM_3-7.0/HA/etc/OSResSystemConfig [Enter]

Appendix A System Tips
In this appendix some system tips are show.
A.1 Find the CD-ROM/DVD-ROM Device File

Some activities require to know with is the CD-ROM/DVD-ROM device drive, hereafter the procedure to
know it.
First of all you have to login the system as root user, and enter the following ioscan command:
...sys,root# ioscan -fnC disk [Enter]
The ioscan command output will be like this one:
,sys,root # ioscan -fnkCdisk

Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST39204LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
disk 7 0/7/0/0.14.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
You have to identify a CD-ROM or a DVD-ROM device in the description column. Then you can double
check the device file by entering the diskinfo command with the raw device associate to it.
...,sys,root # diskinfo /dev/rdsk/<device file>
The diskinfo command related to the previous example will be:

,sys,root # diskinfo /dev/rdsk/c3t2d0
SCSI describe of /dev/rdsk/c3t2d0:
vendor: HP
product id: DVD-ROM 305
type: CD-ROM
size: 584768 Kbytes
bytes per sector: 2048:

System Tips 3AL 89041 BAAA Edition 04 161/200
The correct device type have to be CD-ROM.
A.2 System Shutdown

To safety stop the system it is suggested to perform the system shutdown. This activity allows to stop the
entire system by executing the shutdown procedure of each software component. The shutdown com-
mand is allowed only by root user and foresees many switches, the most used are “-r" and “-h" . The first
one performs the automatic reboot, and the second have to be used when you have to switch off the sys-
tem power supply, because it halts the system.
A.2.1 System Shutdown with Reboot

The system shutdown command allows to perform the system reboot, by entering:
...,sys,root # shutdown -r now [Enter]
A.2.2 System Halt

The system shutdown command allows to perform the system switch off, by entering:
...,sys,root # shutdown -h now [Enter]
N.B. Wait until the “RUN" lamp is switched off or the system status gets in “SHUT" on the front display
before switch off the power supply.

162/200 3AL 89041 BAAA Edition 04 System Tips
Appendix B NMS/NMC Specific Data
Alcatel-Lucent Application Software is divided in two classes: Network Management Subsystem (NMS)
and Network Management Components (NMC). The former class identifies systems that allow the Ele-
ment Management (1353) or the Network Management (1354/1355), the latter one identifies optional
functionalities separately sold.
B.1 NMS Class

NMS are the basic items for installation purpose, them have a specific predisposal activity that allow them
the correct behavior, in the following list the NMS that can be predisposed by OS-Conf for NR81 PL2:
OS_KERNELV7.1.2 (Predispose 7.1.7)

This is the base platform for all the Alcatel-Lucent TNM Applications. No instance is foreseen, but
it has to be always installed.
1353NMV7.4.5 / 1353NM V7.3

Instance Definition: Identifier N_ ______ 1359HA Data Sharing Protection -
type: Master Client Spare system ( only for 1359HA Data Sharing )
Size(*):Small Medium Large



N.B. You must install 1353NM on 1354 subsystem, and you have to create a 1353NM
instance for each 1353NM system under control of 1354 one.
1354RMV7.5.0
1354BMETHV8.1.5

NMS/NMC Specific Data 3AL 89041 BAAA Edition 04 163/200
(*) Not useful for Client
1354SYV8.0
Instance Definition: Identifier N_ ______
type: Master Client
B.2 NMC Class

The NMC are software components, usually installed to provide additional feature only on an already
installed NMS (or planned to be installed).
1359HA and 1353SHBKW require the system predispose before installing them, but
the 1353SHBKW installation is done inside the 1353NM one
Only 1359HA requires a system predisposal.
NMC Name NMS Dependencies.
1359IOOV5.4 1353NM and 1354RM
1359ISNV5.1 1354RM
1359HAV8.0 1353NM, 1354BM and 1354RM

type: Master
2 Client
4 Client
8 Client
1353SHV7.0 (1353SHBKW) 1353NM 7.3

type: Client

type: Client

type: Client

type: Client
1354BM ETH MEDIATOR 1354RM

164/200 3AL 89041 BAAA Edition 04 NMS/NMC Specific Data
B.3 Disk Requirement Tables
The following table shows the disk space requested for swap, program installation, and depot packages.
The value are specified in M bytes
Table 13. Disk requirements for NMS Software for NR8.1 PL2
NMS Swap Required Software Size Depot Package Size
OS-Kernel 100 3600 1390
1353NM 500 7500 3210
1354BM ATM 500 1120 100
1354BM ETH 500 1120 285
1354BM PR 200 100 41
1354RM 500 1320 1250
1354SY 500 1000 105
1359HA N.A. 10 3
1359IOO N.A. N.A. 15
1359ISN N.A. N.A. 42
Table 14. Disk Requirements for NMS Instances for NR8.1 PL2
NMS Master Small Master Medium Master Large Presentation
Swap Data Swap Data Swap Data Swap Data
OS-Kernel 0 200 N.A. N.A. N.A. N.A. N.A. N.A.
1353NM 1500 3000 2000 5000 3000 9000 250 250
1354BM ATM 1500 3000 3500 5000 7500 9000 2000 200
1354BM ETH 2000 3000 3500 5000 7500 9000 2000 200
1354BM PR 3500 2700 3500 4000 3500 6000 3000 500
1354RM 8000 3500 12500 5000 21000 9000 2000 400
1354SN 1000 1000 1500 2000 2500 5000 300 300
1354SY 1500 3000 3500 5000 7500 9000 2000 400
1359HA 100 600 200 1500 500 3000 400(*) 160(*)
(*) This is the maximun size managed.

NMS/NMC Specific Data 3AL 89041 BAAA Edition 04 165/200
B.4 Alcatel-Lucent CD Codes
The following table provides the Alcatel-Lucent CD codes of all media provided with NR8.1 PL2
Table 15. Alcatel-Lucent NR8.1 PL2-DR4 Media codes
CD Label CD Code Description
SWP-OSCONFUX_BOOT-V8.1.2 3AL 88966 ACAA 01 hp-uxTM 11i for ITANIUM processor

installation tool. One DVD 1/1.
SWP-OSCONFUX_PLT-V8.1.2 3AL 88966 BCAA 01 OS-Conf and 3PP software for ITA-
NIUM processor. Two DVDs 1/2, 2/2
SWP-OSCONFUX_ADD- 3AL 88966 DAAA 01 OS-Conf and 3PP software Addendum

V8.1.2_P01 and Patches for ITANIUM processor.
Two DVDs 1/2, 2/2.
SWP-OSCONF_BOOT-V7.1.2 DVD 3AL 89039 AAAA 01 hp-uxTM 11i for PA-RISC processor
installation tool. One DVD 1/1.
SWP-OSCONF_PLT-V7.1.2 DVD 3AL 89039 BAAA 01 OS-Conf and 3PP software for PA-RISC
processor. Two DVD 1/2, 2/2.
SWP-OSCONF_ADD-V7.1.2_P03 3AL 89039 DCAA 01 OS-Conf and 3PP software Addendum

and Patches for PA-RISC processor.
One DVD 1/1.
SWP-1350MS_NR8.1PL2-DR4 3AL 89051 DAAA 01 Alcatel-Lucent NR81 Patch Level 02-

DR4 delivery package.
Three DVDs 1/3, 2/3 3/3

166/200 3AL 89041 BAAA Edition 04 NMS/NMC Specific Data
Appendix C GoGlobal-UX Installation and
Configuration
C.1 GoGlobal-UX Installation on HP-UX System

The GoGlobal-UX software is already installed on the HP-UX system foreseen for Alcatel-Lucent TMN
application.
C.2 GoGlobal-UX Installation on PC

To install the software, perform the following steps:
a) Open a DOS window on PC and type the following commands:

c:\> ftp <host_IP> [Enter]
user : <username> [Enter]
password : <password> [Enter]
where:
<host_IP>= is the IP address of the Unix machine where GO-Global is installed;
<username>= is the username of UNIX operator;
<password>= is the password relative to the <username> indicated.
Continue with:
ftp> cd /opt/graphon/pc [Enter]

ftp> bin [Enter]
ftp> get go_setup_2*.exe [Enter]
ftp> quit [Enter]
b) Double click on the executable.
c) The “Install Shield Wizard" window will be opened:
Figure 32. GoGlobal-UX Logo

GoGlobal-UX Installation and Configuration 3AL 89041 BAAA Edition 04 167/200
The installation application checks if there is a previous version installed. If a previous version is
found remove it by follow the instruction in paragraph “Automatic Removal of GoGlobal-UX/Previous
Version" C.2.1 at page 170 , otherwise proceed with the next point.
d) The next window will be opened showing the welcome message:
Click on Next to go on. Wait a few seconds the install procedure.
e) The “License Agreement" window will be opened:
Click on Yes to go on.
f) The “Destination Location" window will be opened:

168/200 3AL 89041 BAAA Edition 04 GoGlobal-UX Installation and Configuration
Choose your destination location and click on Next to go on. Wait a few seconds the install proce-
dure.
g) The “Install Shield Wizard Complete " window will be opened:
Click on Finish to go on.
h) The “Connection" window will be opened
You have to insert the Server Address of the machine that you want to be connected to.
Click on Connect. The “Authentication" window will be opened
You have to insert:
Username
Password
Click on OK. GoGlobal-UX will open a connection with the configured machine.

C.2.1 Automatic Removal of GoGlobal-UX/Previous Version
If installing GoGlobal-UX a previous version in installed the application asks you the authorization to
remove it by issuing the window:
To upgrade the software press the “O.K." button.
Then the script ask you to remove also the GoGlobal user setting, if you want to maintain the connection
descriptions press “NO" button.
The the previous GoGlobal-UX will be removed from the PC.
When the removal will be completed the following window will be shown on the screen.
You can now install the new version of the software by starting again the installation application.

C.3 GoGlobal-UX license
The GoGlobal-UX X-Emulator for MicrosoftTM Windows personal computers requires to be authorized
with a license key. The permanent licenses provided are network floating, that means you need one or
more “license server machine" in your network.
The Bridges 1.1 license are still useful for running GoGlobal-UX 2.
C.3.1 License servers definition rules

Before to require the GoGlobal-UX license(s), you have to decide how many and what will be the license
server machine(s) in your network, in accordance with the following rules:
– If you have three or more machines, you have to setup a “Three Redundant License Servers" con-
figuration, in accordance with the following rules:.
• the three license server machines should be located physically close to each other (if possible).
• never configure redundant servers with slow communications or dial-up links.
With three-server redundancy,only one of the three servers is 'master', capable of issuing licenses.
Since all clients must contact the 'master', all clients must have reliable networking to a single node.
– if in your network there are less than three nodes, you have to define a the license server, and all
the required licenses have to be loaded on that server.
On the license server machine(s) will be loaded the license(s) data obtained as showed in the paragraph
C.3.3.
C.3.2 Retrieve License Servers Identity

Meaningful only for the license server machine(s).
When you have selected the license server machine(s), for each of them you have to retrieve the
machine identity by executing the following commands:
a) Log in as root on the machine.
b) Get the hostname of the current machine:
..,sys,root # uname -n [Enter]
c) Get the FLEXlm host ID of the current machine:
..,sys,root # /opt/graphon/bin/lmhostid [Enter]
The obtained data will be used in a successive phase of the license request activity.

C.3.3 Permanent License Request
Meaningful only for the license server machine(s).
After that, you can to require the necessary license(s) to activate GoGlobal-UX on your machine(s) visiting
the GraphOn Licensing web site through your web browser, by typing one of following URLs:
For three reducndant: http://license.graphon.com/user/redundant_pcode.cgi
For single node: http://license.graphon.com/user/
The following window will appear:
Figure 33. GraphOn License WEB Page
Scroll down along the window using the scroll bar and fill the following fields about the required registration
information:
– Name (1)
– Company (1)
– Address & Address2(1)
– City (1)
– State/Province (2)
– Country (1)
– Postal Code (1)
– Phone (1)
– Email Address (1)
(1) Introduce the data of the reference person near the customer or the your own ones.
(2) Leave it as “Not Specified" when the system is located outside of U.S.A..
Fill in the data, then click on Next> button to continue with the next window.

The “Software Agreement" window will appear
Figure 34. GraphOn License WEB Page - Software Agreement
Scroll down until the bottom of the window using the scroll bar and click on I Accept button to continue.
The “License Information" window will appear dependig from the initial URL used to connect GraphOn
WEB site:
Figure 35. GraphOn Info request window for Single server

Figure 36. GraphOn Info request window for Three Redundant servers
N.B. If you have one or more “PURCHASED GraphOn LICENSE FOR ALCATEL-LUCENT USE OR
RESALE" document, you have to repeat the following operations for each “Product Code" value
indicated.
Like this, you will obtain one or more NOT demo licenses.
Scroll down along the window using the scroll bar and fill the following fields:
– Product Code (see the “Product Code" value on the “PURCHASED GraphOn LICENSE FOR ALCA-
TEL-LUCENT USE FOR RESALE" document if present)
– Host Name (see the paragraph C.3.2)
– Host ID (see the paragraph C.3.2)
Now if you have the “Three Redundant License Servers" configuration you have to set “YES" in the box
close to the label “Are you using redundant servers?", and fill in the three couple of information: Host-
name and Hostid with the data of each license server.
and click on Get License button to continue.

Figure 37. GraphOn License WEB Page - License Output Example
Put the showed data in the license file of the license server machine (see the paragraph C.3.4.1.1) and
click on the Back button to come back to the “Product Code" window to require (eventually) another license
otherwise, if you are terminated, click on File and Close option to exit from the web browser.
C.3.4 GoGlobal-UX authorization procedure

GraphOn Corp. provides both permanent or demo license, hereafter some information to help you to con-
figure the GoGlobal-UXTM license files and daemons.
C.3.4.1 Permanent License
GoGlobal-UXTM permanent licenses are provided as network floating point, that meas you have to pro-
mote one or three machines a License Server and all the other will be License Client.
To be able to use them you have to perform the following actions:
1) Store the authorization key in the license file.

2) Configure the license servers machine(s).
3) Start the license server daemons.
4) Configure license client system(s) (if any)

C.3.4.1.1 Store the Authorization Key in the License File.
The first activity is to store the license authorization key previously obtained by GraphOn WEB page (see
C.3.3 at page 172) in the /opt/graphon/etc/license.dat file of any the license server machine. To create
this file, use the command (as root):
..,sys,root # vi /opt/graphon/etc/license.dat [Enter]
N.B. During the insertion of the license data, you have to modify the line of SERVER definition adding
the port number 27001 at the end-of-line (see example below).
After that, save and quit the file pressing [Esc] and typing :x! and [Enter].
Example of /opt/graphon/etc/license.dat file with three servers and two licenses ("INCREMENT" options)
defined:
# NOTE: You can change the hostname on the "SERVER" line.
# You can also add a port number after the hostid on
# the "SERVER" line, like:
# SERVER hostname.domain.com 00HOSTID0 27001
# which will make the lmgrd managing this file use
# port 27001.
# Most other changes will invalidate this file.
# ISSUED_DATE=23-jan-2002
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
Add TCP port number (27001) at any line beginning with SERVER:
Example from:
SERVER host_c 839dc26
to:
SERVER host_c 839dc26 27001
Copy this file on each license server when the three redundant configuration is foreseen.
C.3.4.1.2 Configure License Server(s)
Now you have to configure License Server machine(s) that need to provide the GoGlobal-UX floating
license on the network.

C.3.4.1.2.1 Configure license_server.dat file
An Alcatel-Lucent extension to the GraphOn license management is the license_server.dat file. This file
has to declare all the license servers useful for retrieving license from any host need to use them licenses,
including the license servers hosts themselves.
The easy to proceed is create these files on the license server(s) and them distribute them to the client
when configuring it.
Each time you change the license_server.dat file the changes will be recognize only at next
GoGlobal-UX stat-up.
To declare the license server machines you have to create the file “/opt/graphon/etc/license_servers.dat"
and fill in it with the following syntax:
SERVER <host> <port>
Where:SERVER is a keyword
<host> means the hostname or the IP address of the license server
<port> is the IP port number stored in the license.dat file as fourth field of the line starting
with SERVER, if that field is blank 27001 have to be used.
Example: Use the command (as root):
..,sys,root # vi /opt/graphon/etc/license_server.dat [Enter]
create the file so that it contains the following data:
SERVER host_c 27001

SERVER host_d 27001
SERVER host_e 27001
Save typing :x! and [Enter].
Copy this file on each HP-UX system that have to be able to run GO-Global UX graphical interface, to allow
it the GO-Global UX licence retrieval.
C.3.4.2 Start License Server and GraphOn Daemons
When both license.dat and license_server.dat files have been properly configured on all the License
Server machine(s) you can proceed with the daemon start-up.
Because hp-uxTM start-up launch both License and GraphOn Daemons, it is advisable to execute the dae-
mon stop before. The entire procedure will be:
...,sys,root # /sbin/init.d/goglobalux stop [Enter]

...,sys,root # /sbin/init.d/goglobalux start [Enter]
When the daemons will be started on the single license server on at least two license server nodes for
the three redundant configuration, you will be able to open a GoGlobal-UX 2.0 session from any PC to
the license server machine.

C.3.4.3 Configure License Client System(s)
To be able to access the hp-uxTM machine via GoGlobal-UX you need to get a license, this license will
be granted by the license server(s) via network, that means any hp-uxTM system (license client) have to
be able to connect the license server(s) via network. Moreover the license server(s) have to be referred
by name.
C.3.4.3.1 Verify License Server Connectivity
Before starting the client machine configuration you have to verify the license server machine(s) connec-
tivity, the easiest way to do it is try a ping to any license server host name:
..,sys,root # ping <Hostname> [Enter]
where <Hostname> is the name of the remote license server machine(s).
– If the server replies the “ping" request an output like the following will be provided:
,sys,root # ping hostc 64 2

PING hostc: 64 byte packets
----hostc PING Statistics----

2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
– Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
• ping: Unknown host <Hostname>

Means the license serve <Hostname> is not defined in the host name repository, if you know
also license server IP address you can add it to the host name repository (see paragraph 2.4
at page 102 for more information). When the license server hostname will be present in the host
name repository retry ping command.
• 2 packets transmitted, 0 packets received, 100% packet loss

If no one of the "ping" request is replayed, the are three know possibility:
a) The remote server is down.

b) The remote server is not reachable because the IP address is wrong.
c) The remote server is not reachable because there is no known route on the network
First of all it is better to verify that the server is running. It the server is running check on the /
etc/host file if the IP address defined for the specified server is correct. If also the IP address
is correct, the reason can depend by the Default Gateway, check is adefault gateway si defined
and reachable. If you do not know name and IP address of the network default gateway refer
to the network administrator.

C.3.4.3.2 Verify License Daemon on Server
When the license server machine(s) are reachable, you can also verify on each one of them if the license
daemons are running on these machine(s). this can be done with the following procedure:
N.B. This check can be done only if the license server machine(s) are already configured.
..,sys,root # export LM_LICENSE_FILE=27001@<Hostname> [Enter]

..,sys,root # /opt/graphon/bin/lmstat -a [Enter]
If the file license daemons are active, an output like the following will be displayed:
lmstat - Copyright (C) 1989-2002 Globetrotter Software, Inc.

Flexible License Manager status on Fri 12/5/2003 10:07
License server status: 27001@host_c,27001@host_d,27001@host_e

License file(s) on host_c: /opt/graphon/etc/license.dat:
host_c: license server UP (MASTER) v8.2

host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges: (Total of 2 licenses available)
N.B. The shown output is related to a three redundant server configuration, if you have a single
license server, the data shown with italic font will be not shown.
Otherwise an error message advise you of a problem, check the status of the daemons on the license
server them selves.
C.3.4.3.3 Copy the license_server.dat File from a License Server
All the configuration precondition are now verified, it is possible to configure the license client machine,
the configuration consists only in creating a copy of the license_server.dat file from a license server
machine to this one. Like for servers, when the license_server.dat file is created or modified the daemons
have to be stopped and started to catch the changes.

C.3.4.3.3.1 Check the License Server
In order to check the correct definition of the license server in the license_server.dat file you can execute
the script /opt/graphon/etc/check_server.
..,sys,root # /opt/graphon/etc/check_server [Enter]
If the configuration is correct the output have to contain one set of line for each server defined, like the
following example:
lmstat - Copyright (C) 1989-2002 Globetrotter Software, Inc.

Flexible License Manager status on Fri 12/5/2003 10:20
License server status: 27001@host_c,27001@host_d,27001@host_e

License file(s) on host_c: /opt/graphon/etc/license.dat://:
host_c: license server UP (MASTER) v8.2

host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges: (Total of 5 licenses available)
C.3.4.3.4 Re-Start the GraphOn Daemons
Because hp-uxTM start-up launch GraphOn Daemons, it is advisable to execute the daemon stop before.
The entire procedure will be:
...,sys,root # /sbin/init.d/goglobalux stop[Enter]

...,sys,root # /sbin/init.d/goglobalux start[Enter]
Now the system ready, you can open a GoGlobal-UX 2.1 session from any PC to the this machine until
at least one license is available on the servers.

C.3.5 Add a new license(s)
Sometimes in the system live it is necessary to increase the number of users, that means also the number
of concurrent session have to be increased. To add a new license on a running the license server machine
without close the current open interfaces, you have to proceed this way:
Do not mix permanent floating authorization key with demo one in the same file!
a) Buy the GraphOn license(s).
b) Require the authorization key via GraphOn WEB Page providing the same host ID of the already
requested keys (the host id are related to the license servers!). Hereby an example of a new autho-
rization key requested for the license servers already see in the paragraph C.3.4.1.1 at page 176.
You can see the server lines have the same values in the third field that means the same host ID.
#
# the "SERVER" line, like:
.
.
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info="Paolo Rossi\
[email protected]" ISSUER="GrapOn \
Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \
1996-2002 GraphOn Corporation. All Rights Reserved" ck=45
c) You have to copy the INCREMENT line(s) from the just received authorization key a the end of the
/opt/graphon/etc/license.dat file:
N.B. When a back slash “\" is present at the end of line, also the next line have to be included.
..,sys,root # vi /opt/graphon/etc/license.dat [Enter]

1) Move to last line in file and insert the INCREMENT line(s). For example, if you have the autho-
rization key shown at page 176 active on the system, and receive from GraphOn the one shown
at page 181, the resulting file will be:
#
.
.
#
#
SERVER host_c 77fd17fe 27001
SERVER host_d 77df65d1 27001
SERVER host_e 7751b870 27001
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info="Paolo Rossi\
[email protected]" ISSUER="GrapOn \
Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \
1996-2002 GraphOn Corporation. All Rights Reserved" ck=45
2) Save and exit vi file pressing [Esc] and typing :x! and [Enter].
d) Then ask license daemon to re-read the license.dat file:

..,sys,root # cd /opt/graphon/bin [Enter]
..,sys,root # ./lmreread -c ../etc/license.dat [Enter]
After completing these steps, the new GoGlobal-UX licenses will be available.
C.3.5.1 Demo Licenses
GoGlobal-UXTM demo license can be retrieve from the GraphOn Web server. The demo license are node
locked, and to use them you have just to copy the authorization key into the license.dat file, and delete
license_server.dat if exists.

Appendix D HP9000 Server Cable
Connection
This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP servers
foreseen, an example picture is provided for each server model.
D.1 HP9000 L Class and RP5430

The HP9000 server L class and RP5430 are provided without any disk cabinet. These servers have all
the disks inside the CPU cabinet accessible from the front.
In the following schematic picture the location of the disk on the right side of the cabinet, their role in the
mirroring configuration and their hardware path (and device file names) are shown.
Copy disks
/0/0/2/0.0.0 /0/0/2/0.2.0
(c2t0d0) (c2t2d0)
DVD
/0/0/1/0.0.0 /0/0/1/0.2.0
(c1t0d0) (c1t2d0)
Main disks
Figure 38. Front view of L Server (without cover panel)
PCI Slots
Lan RJ45
Connector
Console/UPS Connector (connect the Web console to

the connector labeled CONSOLE)
VHDCI Connector useful for DAT (using cable VHDCI to 50 pin).

HP9000 Server Cable Connection 3AL 89041 BAAA Edition 04 183/200
Figure 39. Rear view of L Server
If a DLT tape driver is present in this configuration, an extra SCSI adapter will be provided (A4800A). It
has be place in one of the slots: from 7 to 12. Then connect the connect the DLT tape driver via FWSCSI
68 pin cable.
N.B. Install the additional PCI cards starting from the top of PCI Slots.
N.B. Before connect the DLT tape to the SCSI bus check the SCSI ID switch placed on the rear is
set to value 3.

184/200 3AL 89041 BAAA Edition 04 HP9000 Server Cable Connection
D.2 HP9000 A Class and RP2430
The A Class and RP2430 are the HP9000 server entry levels, them are not provided with external disks
and can equip up to two hard disk units. These hard disks are located in the server front, behind a little
door located on the left side.
Each disk is connected to a different SCSI bus, that guarantee the high availability.
Disks Location
Figure 40. Front view of A Class and RP2430 Servers (without cover panel)
D.3 HP9000 RP3410 and RP3440

RP3410 and RP3440 are the HP9000 system based on PA8800 processors, them requires the OS-Conf
7.0.5 P04 (Dec 03) bootable edition to be installed. The difference between the two system is related to
the number of CPUs, RP3410 is foreseen with just one, instead RP3440 with two.
Two system looks is the same from outside, the most relevant characteristic is the disk bay, it foreseen
up to three hard disk slots, but just two SCSI busses. Because of this the machine are provided with two
hard disks, that have to be placed in the slots: HDD 1 and HDD 3.
HDD 1
HDD 2
HDD 3
Figure 41. RP3410 and RP3440 Server Front

D.4 HP9000 RP4440
RP4440 are the high end computer equipped with PA8800 processor and require the OS-Conf 7.0.5 P04
(Dec 03) bootable edition to be installed. It is expandable up to eight CPU and foreseen up to sixteen GB
of RAM.
The typical configuration foreseen an external disk storage. In the following figures is shown how to con-
nect rp4440 to DS2405 Fiber Channel and to MSA30 Ultra320 SCSI disk storages.
D.4.1 RP4440 with DS2405
DS2405 Disk System - Front view

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Figure 42. RP4440 Front View without front panel.
DS2405 Disk System -Rear view
Figure 43. RP4440 Rear View

D.4.2 RP4440 with MSA30
MSA30 Disk System - Front view

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Figure 44. RP4440 Front View without front panel
MSA30 Disk Storage - Rear View
: VHDCI SCSI connector : VHDCI SCSI cable
Figure 45. RP4440 Rear View

D.5 HP9000 N Class and RP7400
The HP disk technology innovation trend brought us to introduce new disk storage in the high-end class
server, the supported server/disk storage configuration are:
Server Model Disk Storage
N4000 SC10
RP7400 SC10, DS2405
D.5.1 HP9000 N Class and RP7400 with SC10

This paragraph provides the instructions for the configuration of the HP HP9000 N Class and RP7400
server configured with the SC10 external disk cabinet. This disk cabinet needs to be configured to cor-
rectly support the disk mirroring, in fact the SC10 issued by HP is usually configured in a different way.
The configuration is related to the dip switch located on the two bus control cards (BCCs). All the SCSI
connectors provided by N4000 server are Very High Density Cable Interconnect (VHDCI) connectors
: VHDCI SCSI cable NOTE: Dip switchorientation is reverted

I on the bottom controller
I I I I
: VHDCI SCSI terminator
O : HD SCSI terminator
5 4 3 2 1 : HD SCSI cable 68pin
: VHDCI SCSI connector O
SC10
A
DAT DVD
12 6
11 The two internal5
PCI Slots 10 disks are place4 PCI Slots
in this location
9 3
8 2
7 1
Figure 46. Rear view of N/RP74xx Server with SC10
N.B. The position of the components in the rack is not predictable, so the N4000 server can be placed
on top of SC10.

N.B. It is advisable to install the PCI cards balancing them in the right and left slots, starting from the
bottom.
D.5.2 HP9000 RP7400 with DS2405

This paragraph provides the instructions for the configuration of the HP HP9000 RP7400 server config-
ured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in dual-
access mode, that means the disks can be accessed by two ways, the side effect of this cable con-
nection is that the hard disks are shown twice.
: VHDCI SCSI cable Fiber Channel Connector

: VHDCI SCSI terminator : HD SCSI terminator
: VHDCI SCSI connector : HD SCSI cable 68pin
DAT DVD
12 6
11 The two internal 5
PCI Slots PCI Slots
10 disks are place
in this location 4
9 3
8 2
7 1
Figure 47. RP7400 Server with DS2405

D.5.3 HP9000 RP7410 with DS2405
This paragraph provides the instructions for the configuration of the HP HP9000 RP7410 server config-
ured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in dual-
access mode, that means the disks can be accessed by two ways, the side effect of this cable con-
nection is that the hard disks are shown twice.
: VHDCI SCSI cable Fiber Channel Connector

: HD SCSI cable 68pin
: VHDCI SCSI connector
DAT
DVD
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Figure 48. Rear view of RP7410 Server with DS2405

Appendix E HP Integrity Server Cable
Connection
This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP servers
foreseen, an example picture is provided for each server model.
E.1 HP Integrity RX2660
Figure 49. RX2660 Front Panel
Figure 50. RX2660 Rear Panel

HP Integrity Server Cable Connection 3AL 89041 BAAA Edition 04 191/200
Figure 51. RX6600 Front Panel
Figure 52. RX6600 Rear Panel

192/200 3AL 89041 BAAA Edition 04 HP Integrity Server Cable Connection
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Figure 53. rx7640 Front view
: VHDCI SCSI cable

: HD SCSI cable 68pin
: VHDCI SCSI connector
DAT
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Figure 54. rx7640 Rear View

HP Integrity Server Cable Connection 3AL 89041 BAAA Edition 04 193/200
194/200 3AL 89041 BAAA Edition 04 HP Integrity Server Cable Connection
ABBREVIATIONS

Abbreviations 3AL 89041 BAAA Edition 04 195/200
196/200 3AL 89041 BAAA Edition 04 Abbreviations
INDEX

Index 3AL 89041 BAAA Edition 04 197/200
198/200 3AL 89041 BAAA Edition 04 Index
CUSTOMER DOCUMENTATION FEEDBACK

Customer Documentation Feedback 3AL 89041 BAAA Edition 04 199/200
200 1350MSUITE Rel 8.1 PL2 Installation Guide
200/200 3AL 89041 BAAA Edition 04 Customer Documentation Feedback
3AL 89041 BAAA
Edition 04
All rights reserved.
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel -Lucent.
www.alcatel-lucent.com
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
ASSEMBLY INSTRUCTIONS
Total Pages: 200 + 6
NOTES: ---
COVER LABELS
(according to Alcatel-Lucent Italy binder format)
1350MSUITE
Rel 8.1 PL2
Installation Guide
3AL 89041 BAAA - Ed. 04
1350MSUITE
Rel 8.1 PL2
Installation Guide - 3AL 89041 BAAA - Ed. 04
1350MSUITE
Rel 8.1 PL2
1350MSUITE
Rel 8.1 PL2

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
HANDBOOK EDITORIAL INFORMATION
Installation Guide
1350MSUITE Rel 8.1 PL2
3AL 89041 BAAA Ed. 04 RELEASED Change Note: Iteration 1
Unit: Wireline Optics NM Vimercate December 2008
Author: B. Bosisio
Appraisal: F. Casasole

135 OMSSUITE81 DPL2 Installation

Uploaded by

Copyright:

Available Formats

135 OMSSUITE81 DPL2 Installation

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

135 OMSSUITE81 DPL2 Installation

Uploaded by

Copyright:

Available Formats

1350MSUITE

Network Management Suite

Rel 8.1 PL2

All other trademarks are the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no

Copyright © 2007 Alcatel-Lucent

3AL 89041 BAAA

All rights reserved.

LIST OF TABLES ........................................................................................................................... 7

2 INSTALLATION AND CUSTOMIZATION .................................................................................... 29

Installation Guide 1350MSUITE Rel 8.1 PL2

4 ADD NEW NMS/NMC................................................................................................................... 153

1350MSUITE Rel 8.1 PL2 Installation Guide

APPENDIX A SYSTEM TIPS .......................................................................................................... 161

APPENDIX B NMS/NMC SPECIFIC DATA .................................................................................... 163

APPENDIX C GOGLOBAL-UX INSTALLATION AND CONFIGURATION.................................... 167

APPENDIX D HP9000 SERVER CABLE CONNECTION............................................................... 183

APPENDIX E HP INTEGRITY SERVER CABLE CONNECTION................................................... 191

ABBREVIATIONS ............................................................................................................................ 195

INDEX ............................................................................................................................................... 197

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 199

Installation Guide 1350MSUITE Rel 8.1 PL2

Installation Guide 1350MSUITE Rel 8.1 PL2

1350MSUITE Rel 8.1 PL2 Installation Guide

Installation Guide 1350MSUITE Rel 8.1 PL2

Installation Guide 1350MSUITE Rel 8.1 PL2

PRODUCT Part Number

1350 3AL 88852 AAAA

PRODUCT RELEASE VERSION (N.B.) Part Number

1350 8.1 8.1 PL2 3AL 89038 AAAA

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

1350MSUITE Rel 8.1 PL2 Installation Guide

EDITION DATE DESCRIPTIONS

Ed. 01 May 2008 NR8.1 PL2 Installation Guide

Ed. 02 August 2008 NR8.1 PL2 Installation Guide

Ed. 03 October 2008 NR8.1 PL2 Installation Guide

Ed. 04 December 2008 NR8.1 PL2 Installation Guide

Table 1. Handbooks related to the specific software application

REF HANDBOOK Part Number Notes

[1] 1350Rel8.1 PL2 THIS

[2] 1350Rel8.1 PL2

Installation Guide 1350MSUITE Rel 8.1 PL2

REF HANDBOOK Part Number Notes

[3] 1350 Management Suite Upgrade Guide 8.1

Table 3. Related Handbooks

REF HANDBOOK Part Number Notes

[4] 1353NM 7.4D

[5] 1354RM 7.4F

[6] 1354BM ETH 8.1D

[7] 1354BM PR 8.1F

[8] 1359HA 8.0

[9] 1359IOO 5.4

[10] 1359ISN 5.1D

[11] 1354SY 8.0.A

1350MSUITE Rel 8.1 PL2 Installation Guide

PREFACE: It contains general information as preliminary information, safety

Installation Guide 1350MSUITE Rel 8.1 PL2

Handbook supply to Customers

Aims of standard Customer Documentation