Optical Management System
Alcatel-Lucent 1350OMS
1350OMS
9.6.11
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.
8DG 42227 MAAA
Edition 01
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.
LIST OF CONTENTS
LIST OF FIGURES ... 5 LIST OF TABLES ... 7 PREFACE... 9 Preliminary Information... 9 Applicability... 10 Scope ... 10 History... 11 Related Documents ... 12 Handbook Structure ... 13General on Customer Documentation ... 14
1 INTRODUCTION ... 19
1.1 Installation Requirements ... 19
1.1.1 Requested Hardware... 19
1.2 Initial Installation... 22
1.2.1 HP-UX Operating System Installation & Configuration ... 23
1.2.2 Predispose... 23
1.2.3 Instance creation ... 23
1.2.4 Software copy ... 23
1.2.5 Custom ... 23
1.2.6 Integration & Federation ... 24
1.2.7 Network Management Sub-Systems Functional Dependencies... 24
1.2.8 Optional Network Management Sub-Systems... 25
1.3 Restrictions ... 26
1.4 Registered Trademarks ... 26
1.5 Conventions ... 26
2 INSTALL AND CUSTOMIZE 1350OMS... 27
2.1 Operating System Installation ... 28
2.1.1 Preparatory activities ... 28
2.1.2 Installing HP-UX 11iV3... 31
2.1.3 Boot the machine... 32
2.1.4 Time Zone Selection ... 37
2.1.5 Time Adjusting ... 38
2.1.6 Hostname Definition ... 39
2.1.7 IP Address Set-up... 40
2.1.8 SubNetwork Mask and GateWay set-up... 41
2.1.9 DNS Configuration... 43
2.1.10 Core Memory and Swap/Dump Sizing... 44
2.1.11 Hardware Scanning... 45
2.1.12 Mirror/Disk UX Selection... 46
2.1.13 Disk Selection ... 47
2.1.14 Execution Phase... 52
2.1.15 End execution phase ... 54
2.2 Software Package Predispose... 56
2.2.1 1350OMS-MW_OS Installation... 56
2.2.7 Predispose for Installation ... 63
2.2.8 1350OMS-HA Post Predisposal ... 80
2.3 Operating System Configuration... 82
2.3.1 Node Name Management... 82
2.3.2 Synchronize the Clocks ... 84
2.3.3 Configure License Manager... 89
2.3.4 Enable GoGlobal Connection ... 89
2.4 Install and Customize Alcatel-Lucent Software ... 90
2.4.1 Automatic Install and Customize NMS and NMC ... 90
2.4.2 Manual Install and Customize NMS and NMC... 93
2.5 System Configuration... 102
2.5.1 System Configuration trouble shutting... 104
2.5.2 LAN Assignment ... 105
2.6 NMS Special Installation Instruction ... 106
2.6.1 Special Instruction for SDH, NPR ... 106
2.6.2 Special Instruction for HA ... 107
2.7 Stop/Start Kernel Services ... 111
2.8 Integration & Federation ... 111
2.8.1 Final Integration&Federation Script ... 111
2.9 Mandatory W/A... 111
2.10 Disable network root access ... 112
2.11 Mandatory W/A for Application Start-up ... 112
2.11.1 EML RetixStack... 112
2.11.2 GUI servers... 112
3 WEB DESKTOP AND CLIENT PC... 113
3.1 Web Desktop ... 113
3.1.1 Connection to Web Desktop ... 113
3.2 Client PC ... 115
3.2.1 Pagefile configuration review... 115
3.2.2 Host Configuration ... 117
3.3 Troubleshooting... 118
3.3.1 WebEnabler cache... 118
4 TROUBLE SHOOTING... 119
4.1 Identify a Failure Condition... 119
4.2 Failure installing a HP-UX ... 119
4.3 Recoverable Faults ... 120
4.3.1 Recoverable Faults Installing Software... 120
4.3.2 Recoverable Faults Managing SWP ... 122
4.4 Kerberos Problems... 124
4.4.1 Kerberos kdcd Process Not Running... 124
4.4.2 Kerberos kdcd High CPU Consuming ... 124
4.5 Device Full ... 125
4.5.1 Device Full on /var Mounted File System ... 125
4.5.2 Device full on /usr and /home ... 125
4.6 Inittab Process Not restarting... 127
APPENDIX A SYSTEM TIPS ... 129
A.1 Find the CD-ROM/DVD-ROM Device File... 129
A.2 System Shutdown ... 130
A.2.1 System Shutdown with Reboot... 130
A.2.2 System Halt ... 130
A.3.2 Activate ORCA on rx2800 ... 132
A.3.3 Smart Array Configuration Rule ... 134
A.3.4 Create RAID 1+0 Logical Drive ... 135
A.3.5 How to delete a Smart Array Logical Drive ... 136
A.4 Installing and Configuring Mirror Disk/UX... 138
A.4.1 Mirror Disk/UX Installation Prerequisite... 138
A.4.2 Mirror Disk/UX Configuration Prerequisite ... 138
A.4.3 Mirror Disk/UX Installation ... 138
APPENDIX B SPECIFIC DATA... 139
B.1 1350OMS Network Management composition table ... 139
B.2 Alcatel-Lucent DVD Codes ... 141
B.3 NMS/NMC Specific Data... 142
B.3.1 NMS Class ... 142
B.3.2 NMC Class ... 142
APPENDIX C GOGLOBAL-UX INSTALLATION AND CONFIGURATION... 143
C.1 GoGlobal-UX Installation on HP-UX System... 143
C.2 GoGlobal-UX Installation on PC... 143
C.2.1 Automatic Removal of GoGlobal-UX/Previous Version... 146
C.3 GoGlobal-UX license... 147
C.3.1 License servers definition rules... 147
C.3.2 Retrieve License Servers Identity ... 147
C.3.3 Permanent License Request... 148
C.3.4 GoGlobal-UX authorization procedure ... 151
C.3.5 Add a new license(s)... 157
APPENDIX D POSEIDON INSTALLATION AND CONFIGURATION... 159
D.1 Poseidon License Management Configuration ... 159
D.2 Retrieve License Servers Host Identifier ... 159
D.3 Require the Authorization License ... 160
D.4 Check the License Status ... 160
D.5 Add a New License... 162
D.6 Poseidon License Server Troubleshooting ... 162
D.6.1 Redundant Connectivity ... 162
D.6.2 Two licence servers down ... 163
APPENDIX E HP9000 SERVER CABLE CONNECTION... 165
E.1 HP9000 RP3410 and RP3440 ... 165
E.2 HP9000 RP4440... 166
E.2.1 RP4440 with MSA30 ... 166
APPENDIX F HP INTEGRITY SERVER CABLE CONNECTION... 167
F.1 HP Integrity RX2660 ... 167
F.2 HP Integrity RX6600 ... 168
F.3 HP Integrity RX7640 ... 169
ABBREVIATIONS ... 171
INDEX ... 173
LIST OF FIGURES
Figure 1. MP to W-cable connection... 20
Figure 2. F/F adaptor cable to connect PC to HP MP... 21
Figure 3. Installation Phases on a server... 22
Figure 4. Example of TMN configuration ... 24
Figure 5. NMS functional dependency... 24
Figure 6. Example of disk configuration... 49
Figure 7. 1350OMS-HA communication example... 80
Figure 8. Network Example... 83
Figure 9. NTP Configuration Example ... 84
Figure 10. Automatic and Fast Install and Customize ... 91
Figure 11. Automatic and Fast Install and Customize... 92
Figure 12. List of existing instances... 99
Figure 13. NMS Customize Window ... 99
Figure 14. NMS Customize Window ... 100
Figure 15. NMS Customize trace window... 101
Figure 16. Add 1350OMS-HA Starting configuration Example ... 107
Figure 17. Add 1350OMS-HA Final configuration Example... 108
Figure 18. Web Desktop Login ... 114
Figure 19. Web Desktop password ... 114
Figure 20. Smart Array P400 Main Menu ... 131
Figure 21. Smart Array View Configuration window ... 132
Figure 22. rx2800 Boot Primary Menu ... 132
Figure 23. rx2800 UEFI shell prompt ... 133
Figure 24. UEFI drvcfg command examples... 133
Figure 25. Smart Array P410i Main Menu... 134
Figure 26. Smart Array Create window - 1... 135
Figure 27. Smart Array Create window - 2... 135
Figure 28. Smart Array Delete window - 1 ... 136
Figure 29. Smart Array Delete window - 2 ... 136
Figure 30. GoGlobal-UX Logo ... 143
Figure 31. GraphOn License WEB Page ... 148
Figure 32. GraphOn License WEB Page - Software Agreement ... 149
Figure 33. GraphOn Info request window for Single server... 149
Figure 34. GraphOn Info request window for Three Redundant servers ... 150
Figure 35. GraphOn License WEB Page - License Output Example... 151
Figure 36. RP3410 and RP3440 Server Front... 165
Figure 37. RP4440 Front View without front panel ... 166
Figure 38. RP4440 Rear View ... 166
Figure 39. rx2660 Server Front view... 167
Figure 40. rx2620Server Rear view ... 167
Figure 41. RX6600 Front Panel ... 168
Figure 42. RX6600 Rear Panel... 168
Figure 43. rx7640 Front view ... 169
LIST OF TABLES
Table 1. Handbooks related to the specific software application ... 12
Table 2. Related Handbooks... 12
Table 3. Optional Network Management Sub-system Applicability... 25
Table 4. List of HP9000 supported hardware components ... 28
Table 5. List of HP Integrity supported hardware components ... 29
Table 6. EML Instances... 68
Table 7. Involved IP Network Node table ... 82
Table 8. Lan card configuration... 105
Table 9. Lan card configuration 1350OMS Rel 9.6 ... 105
Table 10. 1350OMS Network Management composition table ... 139
Table 11. Alcatel-Lucent 1350OMS 9.6.11 Media codes... 141
Table 12. Three Server Redundant License Form ... 159
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.
Applicability
This handbook applies to following product–releases:
PRODUCT Part Number
1350OMS 8DG 41764 AAAA
PRODUCT RELEASE VERSION (N.B.) Part Number
1350OMS 9.6 9.6.11 8DG 42204 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.
History
EDITION DATE DESCRIPTIONS
Ed. 01 August 2012 1350OMS 9.6 Installation Guide
Aligned to 9.6.11 DR4
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 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] 1350OMS R9.6
Installation Guide 8DG 42227 MAAA
THIS HANDBOOK [2] 1350OMS R9.6
Administration Guide 8DG 42227 LAAA
Table 2. Related Handbooks
REF HANDBOOK Part Number Notes
[3] 1350OMS 9.6 GETTING STARTED GUIDE 8DG 42227 AAAA
[4] 1350OMS 9.6 EML User Guide 8DG 42227 BAAA
[5] 1350OMS 9.6 SDH User Guide 8DG 42227 CAAA
[6] 1350OMS 9.6 PKT Guide 8DG 42227 DAAA
[7] 1350OMS 9.5 SY Guide 8DG 42227 EAAA
[8] 1350OMS 9.6 Service Assurance Guide 8DG 42227 FAAA
[9] 1350OMS 9.6 HA Guide 8DG 42227 GAAA
[10] 1350OMS 9.6 OI Guide 8DG 42227 HAAA
[11] 1350OMS 9.6 CLI Reference 8DG 42227 KAAA
[12] 1350OMS 9.6 SONET Guide 8DG 42227 PAAA
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.
ClientPCConfig This chapter describes a personal computer minimum and recom-mended machine requirements.
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 In this appendix Poseidon installation and configuration is described.
Appendix E This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP 9000 servers foreseen.
Appendix F This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP Integrity servers foreseen.
ABBREVIATIONS: Not applicable
INDEX Not applicable
CUSTOMER DOCUMENTA-TION FEEDBACK
It contains info regarding customer opinions collection about this 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 “” 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 of Contents) when modifications are made to the editorial
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.
Sui 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-Information-System as a structured list. Whenever a new edition of any of such handbooks/documents is released in the Alcatel-Lucent archive system, a check in the Alcatel-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 1350OMS 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 11iV3, and the third party software requested by an NMS and NMC.
This document doesn’t provide information to migration machine installed with previous 1350OMS.
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.1.1.1 “Check HP9000 Hardware Configuration" at page 28 and in the parapara-graph 2.1.1.2 “Check HP Integrity Hardware Configuration" at page 29. 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 Equipment
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.
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 reasons the PC must have RS232 (or equivalent USB adapter) and LAN (Local Area Network) 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 rp3440 server console to a PC. HP9000 rp serv-ers are equipped with a Management Processor (MP) that allows the systems remote control. 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 split in three 9 pins connectors, and one of them is mark with “Console":
Console connector.
Figure 1. MP to W-cable connection.
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.
Tx Rx RTS CTS DSR S.G. DCD DTR RI 3 2 7 8 6 5 1 4 9 Tx Rx RTS CTS DSR S.G. DCD DTR RI 3 2 7 8 6 5 1 4 9
Figure 2. F/F adaptor cable to connect PC to HP MP
The GUI access to HP9000 server in provided by installing GoGlobal-UX software (see “1350OMS 9.6 NMS Admin Guide" [2] for more information) and connecting the PC to Local Area Network where the HP9000 server is connected to.
1.1.1.3 Required Go-Global UX License
Go-Global UX needs a permanent or temporary license to be able to run (see “Appendix C“ at page 143 for more information).
1.1.1.4 Requested Hard Disks
The hard disk requirements within 1350OMS 9.6 are strictly related to the NMS you are installing, and the size of their instances.
Another specific behavior of 1350OMS-MW_OS 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 memory size, and can be summarize in the following:
One 146GB disk for machine with core memory size up 36 GB N.B. A single 146 GB disk can contain just the operating system! Refer configuration guide for more info.
1.2 Initial Installation
The 1350OMS 9.6 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) Custom
6) Integration & federation
The following picture shows the 1350OMS 9.6 installation process on a server, starting from an empty sys-tem up to an operational one. Each step adds a something new in term of areas, software or references.
HP-UX 11iV3 HP-UX 11iV3 HP-UX 11iV3 HP-UX 11iV3 MW_INT, NMS NMS 2_1_ Vx_Clien t NMS 1_1_V x_Maste r NMS 2_2_ Vx_Clien t
HP-UX Predispose Instance
Customize HP-UX 11iV3 MW_INT, NMS NMS2 _1_V x_ Clien t NMS1_ 1_V x_ M ast er NMS2 _2_V x_ C lient NMS2_1_Vx_Master NMS2_2_Vx_Master Integration Creation HP-UX 11iV3 SW copy MW_INT, NMS NMS2_1_Vx_Master NMS2_2_Vx_Master
File system Internal data reference External data reference Integration reference
1.2.1 HP-UX Operating System Installation & Configuration
The HP-UX 11iV3 operating system installation is performed to set-up a new system or recycle 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 prepare 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 requirements 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 Custom
The custom phase adapts the data instance to target system performing the following actions: – Creates empty data structure.
– Makes links with the installed management software.
1.2.6 Integration & Federation
Integration and federation phases allow to join together feature of different NMS's when it is foreseen. SDH
Presentation SDHMaster
EML
Master EMLMaster
HP-UX 11iV3 EM L_1 _V x_C EM L_2 _V x_C S DH_ 1_ V y_C MW_INT, EML Vx SDH Vy Software HP-UX 11iV3 EM L_1 _V x_C EM L_2 _V x_C S DH_ 1_ V y_M MW_INT, EML Vx SDH Vy Software MW_INT, EML Vx Software HP-UX 11iV3 EML_1_Vx_M MW_INT, EML Vx Software HP-UX 11iV3 EML_2_Vx_M
Figure 4. Example of TMN configuration
1.2.7 Network Management Sub-Systems Functional Dependencies
The 1350 Management Suite is a multi-layer architecture where NMS (Network Management Sub-Sys-tems) can require functionalists provided by other NMSs. This implies dependencies in the system instal-lation.
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. 1350OMS-MW-INT is required for all NMSs.
SDH SONET WDM PKT
EML
eOMS
MW (OS & INT)
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).
1.2.8 Optional Network Management Sub-Systems
Alcatel-Lucent Networks Management Suite foresees optional Sub-systems such as: 1350OMS-IOO, 1350OMS-HA. These sub-systems enhance other NMS feature, adding interfaces and high availability. Here after the optional NMS applicability .
Table 3. Optional Network Management Sub-system Applicability
Optional NMS Applicable NMS HA EML PKT SDH/NPR WDM IOO(1) EML PKT SDH/NPR WDM SY MED PKT SDH/NPR CPB(2) EML WDM MTMNTMF SDH/NPR
(1) N.B. IOO needs a valid IOO license.
1.3 Restrictions
The 1350OMS-MW_OSUX 9.6 has the following restrictions:
– The minimum hard disk space supported is 20 Gbyte + RAM size.
– The machine configuration not included in the “List of HP9000 supported hardware components" Table 4. at page 28 and “List of HP Integrity supported hardware components” Table 5. at page 29 are not guarantee.
1.4 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.
– MySQL®is a registered trademark of MySQL AB.
1.5 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.
2 Install and Customize 1350OMS
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.1.1.1 “Check HP9000TM Hardware Configuration" at page 28 and in the paragraph 2.1.1.2
“Check HP Integrity Hardware Configuration" at page 29.
VERY IMPORTANT!!
Before proceed in the installation, upgrade or migration you have to visit the Optics Technical Excellence Center WEB site (http://tec-optics.web.alcatel-lucent.com/) and Patch Centre for Navistm Optical Management System (http://tms.uk.lucent.com/PS), looking for additional installation notes.
The installation done by following the information provided by this chapter causes the complete removal of hard disks involved.
It is recommended install Alcatel-Lucent Software related data through the Auto-matic Installation procedure.
The chapter contents:
– Operating System InstallationHP-UXTM 11iV3 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 11iV3 for communication.
2.1 Operating System Installation
This chapter describes the first part of initial installation, it explains how to perform a HP-UX 11iV3 Oper-ating System installation.
N.B. NEVER EXECUTE IT ON AN IN SERVICE SYSTEM.
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 TEC WEB site for any warning and known problems!
2.1.1 Preparatory activities
Before proceeding in the HP-UX 11iV3 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.1.1.1 Check HP9000TM Hardware Configuration
This paragraph shows the HP hardware (PA-Risc processor) where the 1350OMS-MW_OS has been val-idated. The correct behavior of the procedure on different hardware is not guarantee.
HP9000 Model Optional Cards
Server RP3410 C5687C HP DAT 40 External Tape Drive
A9919A HP server DVD-ROM drive, Slimline A5230A PCI 10/100Basr-T LAN Adapter
AB290A HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr
Server RP3440 C5687C HP DAT 40 External Tape Drive
A9919A HP server DVD-ROM drive, Slimline A5230A PCI 10/100Basr-T LAN Adapter
A9784A PCI-X 2Gb Fibre Channel, 1000Base-T HBA AB290A HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr Server RP4440 A7163A DVD drive (read only) for 4U chassis
A6795A PCI 2GB FIber Channel Adapter A6250AZ Disk System 2405 Factory Rack A5230A PCI 10/100Base-T LAN Adptr
A9784A PCI-X 2Gb Fibre Channel, 1000Base-T HBA AB290A HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr Table 4. List of HP9000 supported hardware components
2.1.1.2 Check HP IntegrityTM Hardware Configuration
This paragraph shows the HP hardware (Itanium Processor) where the 1350OMS-MW_OS has been val-idated. The correct behavior of the procedure on different hardware is not guarantee.
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
rx6600 AB545A HP PCI-X 4-port 1000Base-T Gigabit Adapter
A7173A HP Dual Channel Ultra320 SCSI Adapter C5687D HP StorageWorks DAT 40 Ext Tape Drive Q1522B HP StorageWorks DAT 72 Internal Drive A7012A PCI-X 2 port 1000Base-T Gigabit Adptr AB290A HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr AB036B HP Core IO Smart Array Control (P400) RAID1
rx7640 AB545A HP PCI-X 4-port 1000Base-T Gigabit Adapter
A7173A HP Dual Channel Ultra320 SCSI Adapter C5687D HP StorageWorks DAT 40 Ext Tape Drive A7012A PCI-X 2 port 1000Base-T Gigabit Adptr 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
rx2800 AD377A HP PCIe 2-port 1000BT Card
2.1.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 these 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:____________________________ Time Zone:_______________________
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) 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.
Source Device means the DVD-ROM device will be used to retrieve the software. It is automatically detected by the procedure.
Mirror Disk/UXTM is 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.
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 11iV3 required at least eight Gbyte with a machine with up to one Gbyte of RAM, the operating
2.1.2 Installing HP-UX 11iV3
The HP-UX operating system is the first software installed on a new system, this task is performed by using the appropriate 1350OMS-MW_OS bootable DVD for HP 9000 or HP Integrity processor. The operations of installation of the two systems are practically 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) Smart Array P400 or P410i 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 1350OMS-MW_OS software will be installed.
(2)The Alternate Boot disk is asked only when the Mirror/Disk UXTM has been selected.
In the following will be always specify the difference between HP 9000 and HP Integrity, otherwise the paragraph is valid for both.
2.1.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 server.
N.B. For HP Integrity servers equipped with P400 or P410i Smart Array it is MANDATORY execute the “P400 and P410i Smart Arrays Configuration” A.3 page 131.
2.1.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:
IODC Path# Device Path (dec) Device Path (mnem) Device Type Rev - - -- --- P0 0/0/2/0.0 ide.0 Random access media 1 P1 0/1/1/0.1 intscsia.1 Random access media 1 P2 0/1/1/0.0 intscsia.0 Random access media 1 P3 0/1/1/1.2 intscsib.2 Random access media 1 Insert the bootable DVD: “1350OMS-MW_OS-Boot-V9.6.0.0.1-UX_PA” 1/1 into the driver. When the LED of the DVD-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.44 Mar 12, 2003 ISL booting hpux (;0): INSTALL Boot
...
2.1.3.2 Boot HP Integrity processor
HP Integrity sever boot have a differenr behavior depeding by processor, Montvale and Montecito are pro-vided in rx2660, rx6600, or Tukvila on rx2800.
2.1.3.2.1 Installing HP Integrity with Montecito and Montvale
HP Integrity servers rx2660 and rx6600 can be equipped with a P400 Smart Array disk controller. This controllers 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 only the primary console set via boot manager or concongif command /---\ /---\ | System Overview | | Boot Menu | | hp server rx2660 | | HP-UX Primary Boot: 0/3/0/0.... | | Serial #: DEH473324X | | HP-UX HA Alternate Boot: 0/3... | | | | HP-UX Alternate Boot: 0/3/0/... | | System Firmware: 3.01 [4739] | | Core LAN B | | BMC Version: 5.21 | | EFI Shell [Built-in] | | MP Version: F.02.17 | | Internal Bootable DVD | | Installed Memory: 8192 MB | | Core LAN A | | | | iLO Virtual Media | | CPU Logical | | Tape drive | | Module CPUs Speed Status | | --- | | 0 4 1.66 GHz Active | | Boot Configuration | | | | System Configuration | | | | Security Configuration | | | | | | | \---/ | | \---/ Use ^ and v to change option(s). Use Enter to select an option
HP-UX HA Alternate Boot: 0/3/0/0/0/0.0x0.0x4000000000000003
Select the “Internal Bootable DVD” option, insert the bootable DVD: “1350OMS-MW_OS-Boot-V9.6.0.0.1-UX_IA” 1/1 into the driver, and press [Enter]
If a P400 Smart Array is present the following message will show:
Loading.: Internal Bootable DVD Searching for devices
Broadcom NetXtrem Gigabi Ethernet (BCM5704) is detected (PCI-X) Broadcom NetXtrem Gigabi Ethernet (BCM5704) is detected (PCI-X) HP Smart Array P400 Controller (version 5.20) 7 Logical Drives
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 A.3. 2.1.3.2.2 Installing HP Integrity with Tukwila
HP Integrity servers rx2800 are equipped with a P410i Smart Array disk controller. This controllers 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:
(C) Copyright 1996-2010 Hewlett-Packard Develoment Company, L.P.
Note, menu interface might only display on the primary console device. The current primary console device is:
Seria; PcieRoot(0x30304352)/Pci(0x1C,0x5)
The primary console can be changed via the ‘conconfig’UEFI shell command. Press: ENTER - Start boot entry execution
B / b - Launch Boot Manager (menu interface) D / d - Launch Device Manager (menu interface)
M / m - Launch Boot Maintenance Manager (menu interface) S / s - Launch UEFI Shell (command line interface)
I / i - Launch iLO Setup Tool (command line interface) *** User input can now be provied ***
Waiting for user input.
Enter “B” for lauching “Boot Manager” before count down end, and a menu like next will be shown: /---\ | Boot Manager | \---/ 0/0/0/1/0/0/0.0x0.0x4000000000000001 Device Path:
HP-UX HA Alternate Boot: PcieRoot(0x30304352/Pci( 0/0/0/1/0/0/0.0x0.0x4000000000000000 0x1F,0x2)/Sata(0x0,0x0.0x HP-UX Alternate Boot: 0)
0/0/0/1/0/0/0.0x0.0x4000000000000000 USB Device
[PcieRoot(0x30304352)/Pci(0x1A,0x7)/USB(0x0,0x0) Core LAN Port 1
Core LAN Port 2 Core LAN Port 3 Core LAN Port 4
Internal Bootable DVD iLO Virtual Flash iLO Virtual DVD
/---\ | | | ^v=Move Highlight <Enter>=Select Entry X/x=Exit this Menu | \---/ Move highlighted line on “Internal Bootable DVD” and press [Enter]
2.1.3.2.3 After DVD boot.
The system shows you the start of boot with the following message: Starting: Internal Bootable DVD
(C) Copyright 1999-2009 Hewlett-Packard Development Company, L.P. All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.039 Press Any Key to interrupt Autoboot
\EFI\BOOT\AUTO ==> boot :IINSTALL Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 8168 MB loading section 0
...(complete) loading section 1
...(complete) loading symbol table
... ...
ALCATEL BOOTMEDIUM (17-Jan-11) for HP-UX B.11.31 ia64 (c) Copyright 2010 Alcatel-Lucent
Alcatel-Lucent INSTALLATION PROCEDURE MW_OS Technology
2.1.3.2.4 Know boot issue
Before ask for Time Zone selection, the system may show the following message: * Preparing to execute init...
======= 11/27/08 09:42:05 EST HP-UX Installation Initialization. (Thu Nov 27 09:42:05 EST 2008)
@(#)Ignite-UX Revision C.7.5.142 @(#)ignite/launch (opt) Revision:
/branches/IUX_RA0803/ignite/src@72866 Last Modified: 2008-02-06 15:49:50 -0700 (Wed, 06 Feb 2008)
* Configuring RAM filesystems... * Scanning system for IO devices... * Boot device is: 0/0/2/2.0x1.0x10
WARNING: Could not find Q_BOOT device. Cannot determine what the boot device was.
WARNING: Could not find source device in ioscan output. You must select from the list of devices below to use for the source device:
index HW-path Class description 0) 120 processor Processor 1) 0/0/2/0 OO USB_OHCI_Interface 2) 0/0/2/0.0x0 OO USB_Composite_Device 3) 0/0/2/0.0x0.0x0 OO Virtual_Keyboard 4) 0/0/2/1 OO USB_OHCI_Interface 5) 0/0/2/2 OO USB_EHCI_Interface 6) 0/0/2/2.0x1 OO USB_Composite_Device 7) 0/0/2/2.0x1.0x0 OO USB_Bulk_Only 8) 0/1/1/0 escsi_ctlr HP_PCI/PCI-X_SAS_MPT_Adapter 9) 0/3/0/0/0/0 ext_bus PCIe_SAS_SmartArray_P400_RAID_Controller 10) 0/3/0/0/0/0.0x0.0x4000000000000000 disk HP_LOGICAL_VOLUME 11) 0/3/0/0/0/0.0x0.0x4000000000000001 disk HP_LOGICAL_VOLUME 12) 0/3/0/0/0/0.0x0.0x4000000000000002 disk HP_LOGICAL_VOLUME 13) 0/3/0/0/0/0.0x0.0x4000000000000003 disk HP_LOGICAL_VOLUME 14) 0/3/0/0/0/0.0x0.0x4000000000000004 disk HP_LOGICAL_VOLUME 15) 0/5/1/0/4/0 ext_bus HP_AB290-60001_PCI/PCI-X_U320_SCSI_2-port_U320_SCSI/2-port_1000B-T_Combo_Adapter 16) 0/5/1/0/4/1 ext_bus HP_AB290-60001_PCI/PCI-X_U320_SCSI_2-port_U320_SCSI/2-port_1000B-T_Combo_Adapter 17) 0/1/2/0 lan HP_PCI-X_1000Base-T_Dual-port_Built-in 18) 0/1/2/1 lan HP_PCI-X_1000Base-T_Dual-port_Built-in 19) 0/5/1/0/6/0 lan HP_AB290-60001_PCI/PCI-X_1000Base-T_2-port_U320_SCSI/2-port_1000B-T_Combo_Adapter 20) 0/5/1/0/6/1 lan HP_AB290-60001_PCI/PCI-X_1000Base-T_2-port_U320_SCSI/2-port_1000B-T_Combo_Adapter 21) 0/0/3/0 graphics PCI_Display_(1002515e) Enter the index corresponding to the device to use
as the installation source, 'r' to rescan, or 'q' to reboot:
2.1.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: Alcatel-Lucent INSTALLATION PROCEDURE MW_OS Technology
__________________________________________________________________________ __________________________________________________________________________ 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?
2.1.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, [n] for no or [q] to quit, then press [Enter]
If you confirm the time and date, the procedure will proceed with the “Hostname Definition" paragraph 2.1.6 at page 39. 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?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
2.1.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 with a letter and end with a letter or number. * Contain no more than 20 characters.
NOTE: The hostname should contain 20 characters or less for compatibility with HP-UX `uname'.
The current hostname is unknow. You cannot configure networking or tun HP-CDEif the hostname is unknown. Please choose another name.
___________________________________________________________________________ Just pressing [Enter] will keep the (not recommended) name "unknown"
Enter the system name [unknown]:
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.1.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 134.32.3.10 as the IP address for this system.
Is this correct?
2.1.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?
Press [y] for yes or [n] for no, then press [Enter]
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.1.10 at page 44, otherwise enter y[Enter] and proceed with the following:
___________________________________________________________________________ Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information. Example:
Subnetwork mask: 255.255.0.0 Gateway IP address: 151.98.41.1 Current Settings:
-> Subnetwork mask: 255.255.0.0 (default) Gateway IP address: 134.32.3.10 (default)
___________________________________________________________________________ Enter the new subnetwork mask, [255.255.0.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:
___________________________________________________________________________ Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information. Example:
Subnetwork mask: 255.255.0.0 Gateway IP address: 151.98.41.1 Current Settings:
Subnetwork mask: 255.255.255.0
-> Gateway IP address: 134.32.3.10 (default)
___________________________________________________________________________ Enter the gateway address [134.32.3.10]:
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]
___________________________________________________________________________ Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information. Example: Subnetwork mask: 255.255.0.0 Gateway IP address: 151.98.41.1 Current Settings: Subnetwork mask: 255.255.255.0 Gateway IP address: 134.32.3.10 ___________________________________________________________________________ Are the parameters above correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
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 134.32.3.10
2.1.9 DNS Configuration
DNS is not supported, do not configure it.
This section allows to configure the Domain Name System for HP–UX_. But the DNS configuration it is not validated, so it is recommended 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?
Press [y] for yes or [n] for no, then press [Enter] You have to enter “n” [Enter].
2.1.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 1350OMS-MW_OS installation script, but to allow different approaches the capability 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: 8168 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 [8168]: 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.
2.1.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 = 8 Total CDRoms found = 1 Press [Enter] to continue...
Then the procedure will ask you to confirm the source media as the DVD drive.
This section enables you to enter default Source media (CD/DVD).
___________________________________________________________________________ Source media (CD-ROM/DVD-ROM) Selection
___________________________________________________________________________ Device MByte Hardware Path
_______________ ____________________________________________________________ disk17 3503 255/1/0.0.0
___________________________________________________________________________ Please enter the Device Name of source media [disk17]:
or:
___________________________________________________________________________ Source media (CD-ROM/DVD-ROM) Selection
___________________________________________________________________________ Device MByte Hardware Path
___________________________________________________________________________ c0t0d0 3546 0/0/2/0.0.0.0
___________________________________________________________________________ Please enter the Device Name of source media [c0t0d0]:
2.1.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 ? Press [y] for yes or [n] for no, then press [Enter]
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 ?
Press [y] for yes, [n] for no or [q] to quit then press [Enter] 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 1350OMS-MW_OS. To perform this activ-ity the installation will take 30 minutes more and the machine will be rebooted twice.