1350oms - Ig - 9 6 11hpux

Alcatel-Lucent 1350OMS
Optical Management System
1350OMS
9.6.11
Installation Guide - Volume 1: HPUX

8DG 42227 MAAA Edition 01 August 2012
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 2011 Alcatel-Lucent
8DG 42227 MAAA Edition 01 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.
LIST OF CONTENTS
LIST OF FIGURES ......................................................................................................................... LIST OF TABLES ........................................................................................................................... PREFACE......................................................................................................................................... Preliminary Information.............................................................................................................. Applicability................................................................................................................................. Scope ........................................................................................................................................... History.......................................................................................................................................... Related Documents .................................................................................................................... Handbook Structure ................................................................................................................... General on Customer Documentation ...................................................................................... 1 INTRODUCTION .......................................................................................................................... 1.1 Installation Requirements ................................................................................................... 1.1.1 Requested Hardware ...................................................................................................... 1.2 Initial Installation.................................................................................................................. 1.2.1 HP-UX Operating System Installation & Configuration ................................................... 1.2.2 Predispose...................................................................................................................... 1.2.3 Instance creation ............................................................................................................ 1.2.4 Software copy ................................................................................................................. 1.2.5 Custom ........................................................................................................................... 1.2.6 Integration & Federation ................................................................................................. 1.2.7 Network Management Sub-Systems Functional Dependencies..................................... 1.2.8 Optional Network Management Sub-Systems ................................................................ 1.3 Restrictions .......................................................................................................................... 1.4 Registered Trademarks ....................................................................................................... 1.5 Conventions ......................................................................................................................... 2 INSTALL AND CUSTOMIZE 1350OMS....................................................................................... 2.1 Operating System Installation ............................................................................................ 2.1.1 Preparatory activities ...................................................................................................... 2.1.2 Installing HP-UX 11iV3.................................................................................................... 2.1.3 Boot the machine............................................................................................................ 2.1.4 Time Zone Selection ....................................................................................................... 2.1.5 Time Adjusting ................................................................................................................ 2.1.6 Hostname Definition ....................................................................................................... 2.1.7 IP Address Set-up........................................................................................................... 2.1.8 SubNetwork Mask and GateWay set-up......................................................................... 2.1.9 DNS Configuration .......................................................................................................... 2.1.10 Core Memory and Swap/Dump Sizing.......................................................................... 2.1.11 Hardware Scanning....................................................................................................... 2.1.12 Mirror/Disk UX Selection............................................................................................... 2.1.13 Disk Selection ............................................................................................................... 2.1.14 Execution Phase ........................................................................................................... 2.1.15 End execution phase .................................................................................................... 2.2 Software Package Predispose............................................................................................ 2.2.1 1350OMS-MW_OS Installation....................................................................................... 2.2.2 Pre-Installation Actions ................................................................................................... 2.2.3 Create local alu/DEPOT ................................................................................................. 2.2.4 1350OMS-MW_OS ScBackup cumulative raw patch ..................................................... 2.2.5 Upgrade Platform............................................................................................................ 2.2.6 Install NMS Description and 1350OMS 9.6.11 Installation Procedure ............................ Installation Guide - Volume 1: HPUX List of Contents 5 7 9 9 10 10 11 12 13 14 19 19 19 22 23 23 23 23 23 24 24 25 26 26 26 27 28 28 31 32 37 38 39 40 41 43 44 45 46 47 52 54 56 56 57 59 59 60 62
Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 1/176
2.2.7 Predispose for Installation .............................................................................................. 2.2.8 1350OMS-HA Post Predisposal ..................................................................................... 2.3 Operating System Configuration........................................................................................ 2.3.1 Node Name Management............................................................................................... 2.3.2 Synchronize the Clocks .................................................................................................. 2.3.3 Configure License Manager............................................................................................ 2.3.4 Enable GoGlobal Connection ......................................................................................... 2.4 Install and Customize Alcatel-Lucent Software ................................................................ 2.4.1 Automatic Install and Customize NMS and NMC ........................................................... 2.4.2 Manual Install and Customize NMS and NMC................................................................ 2.5 System Configuration.......................................................................................................... 2.5.1 System Configuration trouble shutting ............................................................................ 2.5.2 LAN Assignment ............................................................................................................. 2.6 NMS Special Installation Instruction .................................................................................. 2.6.1 Special Instruction for SDH, NPR ................................................................................... 2.6.2 Special Instruction for HA ............................................................................................... 2.7 Stop/Start Kernel Services .................................................................................................. 2.8 Integration & Federation ..................................................................................................... 2.8.1 Final Integration&Federation Script ................................................................................ 2.9 Mandatory W/A..................................................................................................................... 2.10 Disable network root access ............................................................................................ 2.11 Mandatory W/A for Application Start-up .......................................................................... 2.11.1 EML RetixStack............................................................................................................. 2.11.2 GUI servers ................................................................................................................... 3 WEB DESKTOP AND CLIENT PC............................................................................................... 3.1 Web Desktop ........................................................................................................................ 3.1.1 Connection to Web Desktop ........................................................................................... 3.2 Client PC ............................................................................................................................... 3.2.1 Pagefile configuration review .......................................................................................... 3.2.2 Host Configuration .......................................................................................................... 3.3 Troubleshooting................................................................................................................... 3.3.1 WebEnabler cache.......................................................................................................... 4 TROUBLE SHOOTING................................................................................................................. 4.1 Identify a Failure Condition................................................................................................. 4.2 Failure installing a HP-UX ................................................................................................... 4.3 Recoverable Faults .............................................................................................................. 4.3.1 Recoverable Faults Installing Software........................................................................... 4.3.2 Recoverable Faults Managing SWP ............................................................................... 4.4 Kerberos Problems.............................................................................................................. 4.4.1 Kerberos kdcd Process Not Running.............................................................................. 4.4.2 Kerberos kdcd High CPU Consuming ............................................................................ 4.5 Device Full ............................................................................................................................ 4.5.1 Device Full on /var Mounted File System ....................................................................... 4.5.2 Device full on /usr and /home ......................................................................................... 4.6 Inittab Process Not restarting............................................................................................. APPENDIX A SYSTEM TIPS .......................................................................................................... A.1 Find the CD-ROM/DVD-ROM Device File........................................................................... A.2 System Shutdown ............................................................................................................... A.2.1 System Shutdown with Reboot....................................................................................... A.2.2 System Halt .................................................................................................................... A.3 P400 and P410i Smart Arrays Configuration .................................................................... A.3.1 Activate ORCA on rx2660 and rx6600 ........................................................................... Alcatel-Lucent 1350OMS 9.6.11 2/176 8DG 42227 MAAA Edition 01
63 80 82 82 84 89 89 90 90 93 102 104 105 106 106 107 111 111 111 111 112 112 112 112 113 113 113 115 115 117 118 118 119 119 119 120 120 122 124 124 124 125 125 125 127 129 129 130 130 130 131 131
Installation Guide - Volume 1: HPUX List of Contents
A.3.2 Activate ORCA on rx2800 .............................................................................................. A.3.3 Smart Array Configuration Rule ..................................................................................... A.3.4 Create RAID 1+0 Logical Drive ...................................................................................... A.3.5 How to delete a Smart Array Logical Drive .................................................................... A.4 Installing and Configuring Mirror Disk/UX ........................................................................ A.4.1 Mirror Disk/UX Installation Prerequisite.......................................................................... A.4.2 Mirror Disk/UX Configuration Prerequisite ..................................................................... A.4.3 Mirror Disk/UX Installation .............................................................................................. APPENDIX B SPECIFIC DATA....................................................................................................... B.1 1350OMS Network Management composition table ........................................................ B.2 Alcatel-Lucent DVD Codes ................................................................................................. B.3 NMS/NMC Specific Data...................................................................................................... B.3.1 NMS Class ..................................................................................................................... B.3.2 NMC Class ..................................................................................................................... APPENDIX C GOGLOBAL-UX INSTALLATION AND CONFIGURATION.................................... C.1 GoGlobal-UX Installation on HP-UX System..................................................................... C.2 GoGlobal-UX Installation on PC......................................................................................... C.2.1 Automatic Removal of GoGlobal-UX/Previous Version................................................. C.3 GoGlobal-UX license........................................................................................................... C.3.1 License servers definition rules ...................................................................................... C.3.2 Retrieve License Servers Identity .................................................................................. C.3.3 Permanent License Request .......................................................................................... C.3.4 GoGlobal-UX authorization procedure ........................................................................... C.3.5 Add a new license(s) ...................................................................................................... APPENDIX D POSEIDON INSTALLATION AND CONFIGURATION............................................ D.1 Poseidon License Management Configuration ................................................................ D.2 Retrieve License Servers Host Identifier .......................................................................... D.3 Require the Authorization License .................................................................................... D.4 Check the License Status ................................................................................................... D.5 Add a New License.............................................................................................................. D.6 Poseidon License Server Troubleshooting ...................................................................... D.6.1 Redundant Connectivity ................................................................................................. D.6.2 Two licence servers down .............................................................................................. APPENDIX E HP9000 SERVER CABLE CONNECTION ............................................................... E.1 HP9000 RP3410 and RP3440 .............................................................................................. E.2 HP9000 RP4440.................................................................................................................... E.2.1 RP4440 with MSA30 ...................................................................................................... APPENDIX F HP INTEGRITY SERVER CABLE CONNECTION................................................... F.1 HP Integrity RX2660 ............................................................................................................. F.2 HP Integrity RX6600 ............................................................................................................. F.3 HP Integrity RX7640 .............................................................................................................
132 134 135 136 138 138 138 138 139 139 141 142 142 142 143 143 143 146 147 147 147 148 151 157 159 159 159 160 160 162 162 162 163 165 165 166 166 167 167 168 169
ABBREVIATIONS ............................................................................................................................ 171 INDEX ............................................................................................................................................... 173 CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 175
Alcatel-Lucent 1350OMS 9.6.11 4/176 8DG 42227 MAAA Edition 01
LIST OF FIGURES
Figure 1. MP to W-cable connection. ................................................................................................ Figure 2. F/F adaptor cable to connect PC to HP MP....................................................................... Figure 3. Installation Phases on a server. ......................................................................................... Figure 4. Example of TMN configuration .......................................................................................... Figure 5. NMS functional dependency.............................................................................................. Figure 6. Example of disk configuration............................................................................................ Figure 7. 1350OMS-HA communication example............................................................................. Figure 8. Network Example............................................................................................................... Figure 9. NTP Configuration Example .............................................................................................. Figure 10. Automatic and Fast Install and Customize ...................................................................... Figure 11. Automatic and Fast Install and Customize....................................................................... Figure 12. List of existing instances .................................................................................................. Figure 13. NMS Customize Window ................................................................................................. Figure 14. NMS Customize Window ................................................................................................. Figure 15. NMS Customize trace window......................................................................................... Figure 16. Add 1350OMS-HA Starting configuration Example ......................................................... Figure 17. Add 1350OMS-HA Final configuration Example.............................................................. Figure 18. Web Desktop Login ......................................................................................................... Figure 19. Web Desktop password ................................................................................................... Figure 20. Smart Array P400 Main Menu ......................................................................................... Figure 21. Smart Array View Configuration window ......................................................................... Figure 22. rx2800 Boot Primary Menu .............................................................................................. Figure 23. rx2800 UEFI shell prompt ................................................................................................ Figure 24. UEFI drvcfg command examples..................................................................................... Figure 25. Smart Array P410i Main Menu......................................................................................... Figure 26. Smart Array Create window - 1....................................................................................... Figure 27. Smart Array Create window - 2....................................................................................... Figure 28. Smart Array Delete window - 1 ........................................................................................ Figure 29. Smart Array Delete window - 2 ........................................................................................ Figure 30. GoGlobal-UX Logo .......................................................................................................... Figure 31. GraphOn License WEB Page .......................................................................................... Figure 32. GraphOn License WEB Page - Software Agreement ...................................................... Figure 33. GraphOn Info request window for Single server.............................................................. Figure 34. GraphOn Info request window for Three Redundant servers .......................................... Figure 35. GraphOn License WEB Page - License Output Example................................................ Figure 36. RP3410 and RP3440 Server Front.................................................................................. Figure 37. RP4440 Front View without front panel ........................................................................... Figure 38. RP4440 Rear View .......................................................................................................... Figure 39. rx2660 Server Front view................................................................................................. Figure 40. rx2620Server Rear view .................................................................................................. Figure 41. RX6600 Front Panel ........................................................................................................ Figure 42. RX6600 Rear Panel......................................................................................................... Figure 43. rx7640 Front view ............................................................................................................ Figure 44. rx7640 Rear View ............................................................................................................ 20 21 22 24 24 49 80 83 84 91 92 99 99 100 101 107 108 114 114 131 132 132 133 133 134 135 135 136 136 143 148 149 149 150 151 165 166 166 167 167 168 168 169 169
Installation Guide - Volume 1: HPUX List of Figures
Installation Guide - Volume 1: HPUX List of Figures
LIST OF TABLES
Table 1. Handbooks related to the specific software application ...................................................... Table 2. Related Handbooks............................................................................................................. Table 3. Optional Network Management Sub-system Applicability................................................... Table 4. List of HP9000 supported hardware components ............................................................... Table 5. List of HP Integrity supported hardware components ......................................................... Table 6. EML Instances..................................................................................................................... Table 7. Involved IP Network Node table .......................................................................................... Table 8. Lan card configuration......................................................................................................... Table 9. Lan card configuration 1350OMS Rel 9.6 ........................................................................... Table 10. 1350OMS Network Management composition table ......................................................... Table 11. Alcatel-Lucent 1350OMS 9.6.11 Media codes................................................................... Table 12. Three Server Redundant License Form ............................................................................ Table 13. Single License Form.......................................................................................................... 12 12 25 28 29 68 82 105 105 139 141 159 160
Installation Guide - Volume 1: HPUX List of Tables
Installation Guide - Volume 1: HPUX List of Tables
PREFACE
Preliminary Information
WARNING ALCATEL-LUCENT makes no warranty of any kind with regards to this manual, and specifically disclaims the implied warranties of merchantability and fitness for a particular purpose. ALCATELLUCENT will not be liable for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection with the furnishing, performance, or use of this material. 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 copied, 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 Documentation Feedback.
Installation Guide - Volume 1: HPUX Preface
Applicability
This handbook applies to following productreleases:
PRODUCT 1350OMS PRODUCT 1350OMS N.B. RELEASE 9.6 VERSION (N.B.) 9.6.11
Part Number 8DG 41764 AAAA Part Number 8DG 42204 AAAA
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 productrelease'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 Ed. 01 DATE August 2012 DESCRIPTIONS 1350OMS 9.6 Installation Guide Aligned to 9.6.11 DR4 Based on 1350 OMS build 9.6.1.1.0 for HP-UX
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 releaseversion is stated in Applicability on page 10 consists of the following handbooks: Table 1. Handbooks related to the specific software application
REF [1] [2] 1350OMS R9.6 Installation Guide
HANDBOOK
Part Number 8DG 42227 MAAA 8DG 42227 LAAA
Notes THIS HANDBOOK
1350OMS R9.6 Administration Guide
Table 2. Related Handbooks
REF [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
HANDBOOK 1350OMS 9.6 GETTING STARTED GUIDE 1350OMS 9.6 EML User Guide 1350OMS 9.6 SDH User Guide 1350OMS 9.6 PKT Guide 1350OMS 9.5 SY Guide 1350OMS 9.6 Service Assurance Guide 1350OMS 9.6 HA Guide 1350OMS 9.6 OI Guide 1350OMS 9.6 CLI Reference 1350OMS 9.6 SONET Guide 1350OMS 9.6 WDM Guide
Part Number 8DG 42227 AAAA 8DG 42227 BAAA 8DG 42227 CAAA 8DG 42227 DAAA 8DG 42227 EAAA 8DG 42227 FAAA 8DG 42227 GAAA 8DG 42227 HAAA 8DG 42227 KAAA 8DG 42227 PAAA 8DG 42227 QAAA
Notes
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized drawing-up guides" complying 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. The requirements, initial and restriction are briefly described.
Introduction
Installation & Customization This chapter shows how to install and customize Alcatel-Lucent Network Management Subsystems on a HP9000 or on a HP Integrity system. ClientPCConfig Troubleshooting Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F ABBREVIATIONS: INDEX This chapter describes a personal computer minimum and recommended machine requirements. This chapter shown how to solve some trouble can occur during the installation, and how to proceed when possible. In this appendix some system tips are show. In this appendix NMS and NMC specific data are described. In this appendix GOGLOBAL-UX installation and configuration is described. In this appendix Poseidon installation and configuration is described. This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP 9000 servers foreseen. This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP Integrity servers foreseen. Not applicable Not applicable
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this documentation. TION FEEDBACK
General on Customer Documentation

Note: when Network Management Operators 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 performance and services for which it is meant. A "product" evolves through successive "productreleases" which are the real products marketed for their delivery at a certain "productrelease" 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 "productrelease" 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 "productrelease" has its own standard Customer Documentation, composed by one or more handbooks. A new "version" of a "productrelease" 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 plantindependent. Plantdependent documentation, if envisaged by the contract, is subjected to commercial criteria as far as contents, formats and supply conditions are concerned (plantdependent 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 explanation of the manmachine 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 production 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 "productrelease" (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 productrelease (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 drawings.
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 editions. 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 productrelease'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 (supplying 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 productrelease(-version) and for a certain language. In some other cases, the same CD-ROM can contain the documentation of different product-release(-version)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 AlcatelLucent 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) 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.
2)
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 composing 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 doesnt 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 paragraph 2.1.1.1 Check HP9000 Hardware Configuration" at page 28 and in the paragraph 2.1.1.2 Check HP Integrity Hardware Configuration" at page 29. To completely define the HP9000 or HP Integrity configuration 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) 2) Two BT LAN cables. 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. Unstable LAN connectivity can cause serious trouble.
Installation Guide - Volume 1: HPUX Introduction
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 servers 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.
3 2 7 8 6 5 1 4 9
Tx Rx RTS CTS DSR S.G. DCD DTR RI
Tx
Rx 2 RTS 7 CTS 8 DSR 6 S.G. 5 DCD 1 DTR 4 RI 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) 2) 3) 4) 5) 6) HP-UXTM Operating System Installation & Configuration Predispose Instance creation Software copy Custom Integration & federation
The following picture shows the 1350OMS 9.6 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 11iV3 HP-UX 11iV3
HP-UX 11iV3
NMS2_1_Vx_Master NMS2_2_Vx_Master NMS1_1_Vx_Master NMS2_2_Vx_Client File system NMS2_1_Vx_Client MW_INT, NMS
NMS2_1_Vx_Master NMS2_2_Vx_Master NMS1_1_Vx_Master
SW copy
NMS2_2_Vx_Client
NMS2_1_Vx_Client
Integration
MW_INT, NMS
Customize
MW_INT, NMS
HP-UX 11iV3
HP-UX 11iV3
HP-UX 11iV3
Internal data reference
External data reference
Integration reference
Figure 3. Installation Phases on a server.
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 provided 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 predispose, but related to the data. Also the data instance requirements have to defined in the Software Packages 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 Management 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. Compiles parameter files by setting the values relevant for instance configuration.
1.2.6 Integration & Federation

Integration and federation phases allow to join together feature of different NMS's when it is foreseen. SDH SDH Presentation Master
EML_1_Vx_C EML_2_Vx_C MW_INT, EML Vx SDH Vy Software EML_1_Vx_C EML_2_Vx_C SDH_1_Vy_C EML_1_Vx_M MW_INT, EML Vx Software SDH_1_Vy_M
MW_INT, EML Vx SDH Vy Software
HP-UX 11iV3
HP-UX 11iV3
EML_2_Vx_M MW_INT, EML Vx Software
HP-UX 11iV3 EML Master
HP-UX 11iV3 EML Master
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-Systems) can require functionalists provided by other NMSs. This implies dependencies in the system installation. 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 EML
WDM
PKT 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). N.B. EML 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: 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 HA IOO(1) MED CPB(2) MTMNTMF
(1) (2)
Applicable NMS EML PKT SDH/NPR WDM EML PKT SDH/NPR WDM SY PKT SDH/NPR EML WDM SDH/NPR
N.B. IOO needs a valid IOO license. N.B. CPB is available only for Itanium platform. For PA-Risc architecture, CPB is not available.
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. MySQLis a registered trademark of MySQL AB.
1.5 Conventions
The following conventions are used in this manual: [Enter] courier bold italic <data> # ..,sys,root # ..,$ ..,oracle> SQL> A key name is shown between square brackets to indicate that you press a named key on the keyboard. Courier type is uses to indicate the output produced by the system or data that you can find. Bold italic letters indicate informations that you must enter from the keyboard. 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. Actions must be performed as root. Actions must be performed as normal user (not as root). Actions must be performed as oracle user. Actions must be performed in SQL utility.
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 Automatic 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. Install and Customize Alcatel-Lucent Software related data
Installation Guide - Volume 1: HPUX Install and Customize 1350OMS
2.1 Operating System Installation

This chapter describes the first part of initial installation, it explains how to perform a HP-UX 11iV3 Operating 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 validated. The correct behavior of the procedure on different hardware is not guarantee. HP9000 Model Server RP3410 Optional Cards 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 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 A7163A A6795A A6250AZ A5230A A9784A AB290A DVD drive (read only) for 4U chassis PCI 2GB FIber Channel Adapter Disk System 2405 Factory Rack PCI 10/100Base-T LAN Adptr PCI-X 2Gb Fibre Channel, 1000Base-T HBA HP PCI-X 2p 1000BT, 2p U320 SCSI Adptr
Server RP3440
Server RP4440
Table 4. List of HP9000 supported hardware components The HP9000 server cable connections are shown in Appendix E at page 165.
2.1.1.2 Check HP IntegrityTM Hardware Configuration This paragraph shows the HP hardware (Itanium Processor) where the 1350OMS-MW_OS has been validated. The correct behavior of the procedure on different hardware is not guarantee. HP Integrity Model Server rx2660 Optional Cards 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
Table 5. List of HP Integrity supported hardware components
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 Customer 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 HPUXTM 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 system can be stored in two four Gbyte disks.
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) 2) 3) Boot from bootable disk (different approach). Smart Array P400 or P410i configuration (only with HP Integrity machine) 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) The Boot disk(s) will be initialized. All the file systems and swap areas will be created The Operating System will be installed on the selected boot disk. The optional software will be automatically installed, if any. The Mirror Disk/UXTM will be configured, if selected. The GoGlobal-UXTM and 1350OMS-MW_OS software will be installed.
4) 5) 6) 7) 8) 9)
(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:
Path# ----P0 P1 P2 P3
Device Path (dec) Device Path (mnem) Device Type ----------------- ------------------ ----------0/0/2/0.0 ide.0 Random access 0/1/1/0.1 intscsia.1 Random access 0/1/1/0.0 intscsia.0 Random access 0/1/1/1.2 intscsib.2 Random access
media media media media
IODC Rev ---1 1 1 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 ... The system shows you the start of boot with the Time zone selection menu.
2.1.3.2 Boot HP Integrity processor HP Integrity sever boot have a differenr behavior depeding by processor, Montvale and Montecito are provided 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 /----------------------------------\ | Boot Menu | | HP-UX Primary Boot: 0/3/0/0.... | | HP-UX HA Alternate Boot: 0/3... | | HP-UX Alternate Boot: 0/3/0/... | | Core LAN B | | EFI Shell [Built-in] | | Internal Bootable DVD | | Core LAN A | | iLO Virtual Media | | Tape drive | | -------------------------------- | | Boot Configuration | | System Configuration | | Security Configuration | | | \----------------------------------/ /----------------------------------\ | System Overview | | hp server rx2660 | | Serial #: DEH473324X | | | | System Firmware: 3.01 [4739] | | BMC Version: 5.21 | | MP Version: F.02.17 | | Installed Memory: 8192 MB | | | | CPU Logical | | Module CPUs Speed Status | | 0 4 1.66 GHz Active | | | | | | | | | | | \----------------------------------/
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-BootV9.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 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 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 conconfigUEFI shell command. Press: ENTER B / b D / d M / m S / s I / i Start boot entry execution Launch Boot Manager (menu interface) Launch Device Manager (menu interface) Launch Boot Maintenance Manager (menu interface) Launch UEFI Shell (command line interface) 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_2port_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_2port_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_2port_U320_SCSI/2-port_1000B-T_Combo_Adapter 20) 0/5/1/0/6/1 lan HP_AB290-60001_PCI/PCI-X_1000Base-T_2port_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:
Dont worry about it, wait for 10 second then enter r to continue.
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 (METDST), 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? 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.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] If you confirm the procedure will go on, otherwise it will go back asking again for the date and time.
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? Press [y] for yes, [n] for no or [q] to quit then press [Enter]
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? Press [y] for yes, [n] for no or [q] to quit then press [Enter]
2.1.8 SubNetwork Mask and GateWay set-up

This section allows to define the subnetwork mask and the gateway, these two information are fundamental 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 network 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 confirm 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 gateway 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 HPUX_. 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 memory, 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. N.B. Do not enter a value less then 50% of RAM size, it can prevent the DUMP creation.
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 = Total CDRoms found = 8 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 question: 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 activity the installation will take 30 minutes more and the machine will be rebooted twice.
2.1.13 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 availability 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.1.13.1 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 using Legacy format, in case of PA-Risc system: This section enables you to select the boot disk device. ___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ c2t1d0 139968 0/1/1/0.1.0 _(free)_ ______ ______________ c2t0d0 34688 0/1/1/0.0.0 _(free)_ ______ ______________ c3t2d0 34688 0/1/1/1.2.0 _(free)_ ______ ______________ ___________________________________________________________________________ Select Primary BOOT dev name or [q] to quit: Using Agile Format, in case of Itanium system: This section enables you to select the boot disk device. ___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ disk0 139968 0/3/0/0/0/0.0.0 _(free)_ ______ ______________ disk1 139968 0/3/0/0/0/0.0.1 _(free)_ ______ ______________ disk9 139968 0/3/0/0/0/0.0.2 _(free)_ ______ ______________ disk10 69952 0/3/0/0/0/0.0.3 _(free)_ ______ ______________ disk11 139968 0/3/0/0/0/0.0.4 _(free)_ ______ ______________ ___________________________________________________________________________ Select Primary BOOT dev name or [q] to quit: Enter the disk device that will be used as boot device then press [Enter]. N.B. "D" character shown before the device name in the Device" column advice the disk is accessible via two different disk controllers. This configuration is typically used with Fiber Channel device. S character shown before the device name in the Device column advise the disk is a Logical Unit provided by a Storage Area Network.
N.B.
2.1.13.2 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 connected 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 ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ disk0 139968 0/3/0/0/0/0.0.0 _(free)_ ______ ______________ disk1 139968 0/3/0/0/0/0.0.1 _(free)_ ______ ______________ disk9 139968 0/3/0/0/0/0.0.2 _(free)_ ______ ______________ disk10 69952 0/3/0/0/0/0.0.3 _(free)_ ______ ______________ disk11 139968 0/3/0/0/0/0.0.4 _(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.1.13.3 Disk Mirror Configuration Policy The disk mirror capability is used for two main purposes: 1) 2) 3) Allow system to survive in case of a single disk failure. Allow system to survive in case of a single disk controller failure. 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 configuration, 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 identified by their file name. In particular the file name can be very helpful to identify the disk - controller relationship. Any disk in the configuration is identified by the following name: disk# 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 configuration 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 ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ disk0 139968 0/3/0/0/0/0.0.0 _(free)_ ______ ______________ disk1 139968 0/3/0/0/0/0.0.1 _(free)_ ______ ______________ disk9 139968 0/3/0/0/0/0.0.2 _(free)_ ______ ______________ disk10 69952 0/3/0/0/0/0.0.3 _(free)_ ______ ______________ disk11 139968 0/3/0/0/0/0.0.4 _(free)_ ______ ______________ ___________________________________________________________________________ Select Primary BOOT dev name or [q] to quit: Now you have to define two disk group (physical volume group) with the following characteristics: 1) 2) 3) N.B. The sum of disk space amount of the two group have to be the same. The Dual-Access disks can be assigned to any group. The non Dual-Access disks connected to the same controller MUST belong to the same group. It is important to follow this rules starting from boot disk definition 2.1.13.1 at page 47.
The following picture is a schematic example of disk configuration (in case of PA-Risc system) 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 6. 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. group 1 with c2t2d0, c4t8d0 and c4t9d0, group 2 with c1t2d0, 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: Installation Guide - Volume 1: HPUX Install and Customize 1350OMS Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 49/176
group 1 with c1t2d0, c4t8d0 and c6t12d0, group 2 with c2t2d0, c4t9d0 and c6t13d0. 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.1.13.4 Multiple Disk Request To install minimum HP-UX configuration on a machine with small hard disk are required, the procedure will prompt you again until the requested amount of disk space will be reached. 2.1.13.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. This section enables you to select the boot disk device. ___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ c2t1d0 139968 0/1/1/0.1.0 Pri_Boot _Main_ vg00 c2t0d0 34688 0/1/1/0.0.0 _(free)_ ______ ____________ c3t2d0 34688 0/1/1/1.2.0 _(free)_ ______ ____________ ___________________________________________________________________________ Select Primary BOOT dev name or [q] to quit: or: ___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Legacy Harware Path Usage Type VolGroup ___________________________________________________________________________ disk0 139968 0/3/0/0/0/0.0.0 Pri_Boot _Main_ vg00 disk1 139968 0/3/0/0/0/0.0.1 _(free)_ ______ ______________ disk9 139968 0/3/0/0/0/0.0.2 _(free)_ ______ ______________ disk10 69952 0/3/0/0/0/0.0.3 _(free)_ ______ ______________ disk11 139968 0/3/0/0/0/0.0.4 _(free)_ ______ ______________ ___________________________________________________________________________
These are your Disks Selection to install HPUX on this system. ATTENTION: The contents of selected disks will be permanent lost Do you want CONTINUE? Press [y] for yes, [n] for no or [q] to quit then press [Enter] If you are sure of your choice enter y[Enter], then the procedure will start the execution phase. The procedure will operate unattended. The procedure executed by a Itanium ia64 hp server rx2660 will take: 25 minutes for operating system +35 minutes to install and configure mirror Don't worry if the machine reboots automatically. Alcatel-Lucent 1350OMS 9.6.11 50/176 8DG 42227 MAAA Edition 01 Installation Guide - Volume 1: HPUX Install and Customize 1350OMS
or: The procedure will operate unattended. The procedure executed by a PA-Risc RP3410 will take: 30 minutes for operating system +40 minutes to install and configure mirror Don't worry if the machine reboots automatically.
2.1.14 Execution Phase

The procedure is now entering the execution phase, it will be performed unattended. This phase takes 15 minutes on a HP9000 or 70 minutes on HP Integrity. 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. 2.1.14.1 Keyboard selection Meaningful only for HP Integrity machine. This question is related to the keyboard selection. This question is issued before MirrorDisk/UX installation! When MirrorDisk/UX is foreseen, do not connect the system via network during the installation, because the MirrorDisk/UX installation causes two reboots.
The script explains how to declare the type of keyboard, 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) 3) 5) 7) 9) 11) 13) 15) 17) 19) 21) 23) 25) 27)
USB_PS2_DIN_Belgian USB_PS2_DIN_Danish USB_PS2_DIN_Euro_Spanish USB_PS2_DIN_French USB_PS2_DIN_German USB_PS2_DIN_Italian USB_PS2_DIN_JIS_109 USB_PS2_DIN_Norwegian USB_PS2_DIN_S_Chinese USB_PS2_DIN_Swedish_Euro USB_PS2_DIN_Swiss_German2 USB_PS2_DIN_T_Chinese USB_PS2_DIN_UK_English_Euro USB_PS2_DIN_US_English_Euro
2) 4) 6) 8) 10) 12) 14) 16) 18) 20) 22) 24) 26)
USB_PS2_DIN_Belgian_Euro USB_PS2_DIN_Danish_Euro USB_PS2_DIN_Euro_Spanish_Euro USB_PS2_DIN_French_Euro USB_PS2_DIN_German_Euro USB_PS2_DIN_Italian_Euro USB_PS2_DIN_Korean USB_PS2_DIN_Norwegian_Euro USB_PS2_DIN_Swedish USB_PS2_DIN_Swiss_French2_Euro USB_PS2_DIN_Swiss_German2_Euro USB_PS2_DIN_UK_English USB_PS2_DIN_US_English
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.1.15 End execution phase

When procedure complete its task on the console you'll see the message: GenericSysName [HP Release B.11.31] (see /etc/issue) Console Login: *********************************************************************** * * Starting Desktop Login on display hosta:0... * * Wait for the Desktop Login screen before logging in. * *********************************************************************** GenericSysName [HP Release B.11.31] (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 that the installation is ok, is still in progress or when it was failed. 2.1.15.1 Login Message ok If the procedure is complete ok the following message is dispalyed at the login: 1350OMS-MW_OS Boot 9.6.0.0.1 hp-ux 11i V3 (23-Dec-11)
WARNING! THE SUPERUSER ACCESS IS ENABLE FROM NETWORK VIA SSH Changing password for root New password:
2.1.15.2 Login Message During the Execution Whoever is logging the system during the executing will be alert the installation is in progress by the following 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.1.15.3 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.2 Software Package Predispose

When the HP-UX 11iV3 operating system installation is completed, the system is not yet ready for AlcatelLucent NMS installation; in fact NMS needs some layer software, that are usually called software platform, to be able to perform their tasks.
2.2.1 1350OMS-MW_OS Installation

The 1350OMS-MW_OS packages have to be installed, you can do it using local DVD or network depot when available, hereafter the two alternatives: a) Login the just installed system as root" user.
2.2.1.1 From Medium a) b) c) Identify the device driver (see Find the CD-ROM/DVD-ROM Device File" appendix A.1 at page 129). Insert the medium with label 1350OMS-MW_OS-PLT-V9.6.0.0.4-UX" volume 1/1 in the driver. Mount the medium by entering the command: ...,sys,root # mount -o rr /dev/scdvd /SD_CDROM [Enter] Install the 1350OMS-MW_OS packages by enter the command: ...,sys,root # swinstall -s /SD_CDROM 1350OMS-MW_OS [Enter] Dismount the DVD and remove it from DVD drive: ...,sys,root # umount /SD_CDROM [Enter]
d)
e)
2.2.1.2 From DEPOT Meaningful only if a network depot is already available. a) Install the 1350OMS-MW_OS packages by enter the command: ...,sys,root # swinstall -s <depot hostname>:/alu/SCDEPOT \ 1350OMS-MW_OS,r=9.6.0.0.4 [Enter]
If the procedure is carried out without error, the system is ready to be predisposed.
2.2.2 Pre-Installation Actions

Hereafter there are some actions that have to be done before installing. 2.2.2.1 Create Software Depots The installation can be executed retrieving the software from a local DVD 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 1350OMS-MW_OS Depot"; where you can store all the software layer distributed within 1350OMS-MW_OS, and one for the AlcatelLucent TNM software, that we will call Alcatel-Lucent NMS Depot". To setup the depot you need 15 Gbyte for 1350OMS-MW_OS Depot, and 19Gbyte for Alcatel-Lucent TNM. The following paragraphs provide the instructions to create the depots. 2.2.2.1.1 Create 1350OMS-MW_OS Depot 1350OMS-MW_OS 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 1350OMSMW_OS Depot (see 1350OMS 9.6 NMS Admin Guide" [2] How to create a Network Depot"). 2.2.2.1.2 Create Alcatel-Lucent NMS Depot This paragraph shows how to create the depot for Alcatel-Lucent software. 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 depot machine as root" user, and execute the following command: 1) Extend /alu to allow the storage of Alcatel-Lucent software by entering the command: ...,sys,root # scextendfs /alu/DEPOT 19000 [Enter] Change the default directory on the depot one: ...,sys,root # cd /alu/DEPOT [Enter]
2)
You have to download all packages into /alu/DEPOT directory. You can retrieve the packages from: A dedicated ftp site Optics Technical Excellence Center WEB A set of distribution DVD
If you have a set of distribution DVD, for each distribution DVD ROM that contains the software you have to install (refer to Table 11. at page 141 for media references): 1) 2) 3) 4) 5) Insert the DVD into the driver. Mount the DVD at /SD_CDROM directory: ...,sys,root # scmount /SD_CDROM [Enter] Copy the entire DVD contents to /alu/DEPOT directory by entering the command: ...,sys,root # cp -p /SD_CDROM/* /alu/DEPOT [Enter] Unmount the DVD: ...,sys,root # umount /SD_CDROM [Enter] Remove the DVD from the driver.
2.2.2.2 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.3.1 at page 82). The machine you have to include are: Hosts involved in TNM application. Printers Licences management systems. Time synchronization systems.
2.2.2.3 Authorize the Retrieval from Remote Depot Machine This paragraph explains how to authorize the file retrieval from the remote depot machine, if you do not use a remote depot machine, or, if the depot machine is, at the same time, the target machine, skip it. For safety reasons, Remote Shell is configured so that any connections are NOT allowed, then, you must enable the rsh daemon. Login the system as root user. Modify the file /etc/inetd.conf so that it changes from: #shell to: shell stream tcp6 nowait root /usr/lbin/remshd remshd stream tcp6 nowait root /usr/lbin/remshd remshd
execute the following command: ....,sys,root # inetd -c [Enter]
If the file /etc/securetty exists, then rename it in /etc/securetty.disabled: ....,sys,root # mv /etc/securetty /etc/securetty.disabled [Enter]
Furthermore, 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. Then the file ~root/.rhosts located on the DEPOT machine must be created/modified so that it will contain a line with the hostname and the keyword root" for each machine. N.B. All the host included in ~root/.rhosts file have to be defined in /etc/hosts one. Example: you have to install the following three systems: hosta, hostb and hostc (the depot machine itself). You have to write ~root/.rhosts file (in Depot machine) in this way: hosta root hostb root hostc root After your installation, remove the corresponding line from the file ~root/.rhosts, if it is the last (the file ~root/.rhost is empty) delete it.
VERY IMPORTANT!!
When you've installed all the machines, you MUST restore the files /etc/inetd.conf and /etc/securetty as were at the beginning.
2.2.3 Create local alu/DEPOT

If you're not the Network depot machine, then you must create the local DEPOT area to storage the Software Package Descriptors, Install Wizard tool and eventually manually patches, which must be present on the local machine. Login the system as root user and then execute the following procedure ....,sys,root # scextendfs /alu/DEPOT 3000 [Enter] ...,sys,root # cd /alu/DEPOT [Enter] ...,sys,root # rcp -p <HOST>:/alu/DEPOT/Install_Wizard-R9.6.1.1.0UX . [Enter] ...,sys,root # rcp -p <HOST>:/alu/DEPOT/Install_Wizard_CMD-R9.6.1.1.0UX . [Enter] ...,sys,root # rcp -p <HOST>:/alu/DEPOT/1350OMS-MW_OS-SWPDESC-9.6.0.0.09.sdpkg . [Enter] ...,sys,root # rcp -p <FROM>:/alu/DEPOT/1350OMS-MW_OS-SCBackup327.sd . [Enter] Where <HOST> is equal to Network Depot machine IP address
2.2.4 1350OMS-MW_OS ScBackup cumulative raw patch

Install MW_OS ScBackup raw patch: ...,sys,root # swinstall -s /alu/DEPOT/1350OMS-MW_OS-SCBackup327.sd \* [Enter]
2.2.5 Upgrade Platform

Logout the root session (the next commands listed below must be executed by opening another session), then complete the MW_OS patch installation phase by executing (logged as root on the console or by a ssh remote connection) the following commands: a) Start the upgrade procedure by entering: ...,sys,root # /SCINSTALL/etc/scupgrade [Enter] b) The procedure will ask you if the software platform upgrade must be perform by DVD (In this case must be available all the DVDs set and the DVD whit correct patche level upgrade must be mounted) or network depot (In this case must be available a DEPOT already updated to the correct patch level. --------------- LAYERED PRODUCTS Repository ------------1 - CD-ROM or DVD media 2 - Software Depot q - quit Insert choice and press [Enter]: Update Platform from DVD 1) Reply the previous question by entering 1 [Enter]": Insert choice and press [Enter]: 1 [Enter] N.B. 2) In this case must be available all the DVD's set.
The procedure asks you to enter the DVD driver file name, usually the proposed default is correct. Enter 'q' to Quit or the CD device [def=/dev/dsk/c0t0d0]:
Update Platform from Network Depot 1) Reply the previous question by entering 2 [Enter]": Insert choice and press [Enter]: 2 [Enter] N.B. c) In this case must be a DEPOT available.
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.1.13.3 Disk Mirror Configuration Policy" at page 48 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 1350OMS-MW_OS install product(s) and/or Patches System could automaticaly reboot The entire 1350OMS Application must be stopped. Do you want continue ? Press [y] for yes or [n] for no, then press [Enter] Stop all the activity, if any, and reply with y[Enter]".
e)
If the system is configured with the "standard" security level, it will be automatically reconfigured and only the following message will be displayed: NOTE: Check security level
Otherwise if the "trusted-base" or "trusted-advanced" security level is defined, it will be asked to confirm the reconfiguration. NOTE: Check security level The security level configured on system is trusted-base. Do you want to reapply it at the end of upgrade [y/n]?:
Reply with y[Enter]".. f) The following message will be displayed and the upgrade procedure starts. NOTE: ..... g) Executing Upgrade starting on Tue Jul 21 16:05:56 METDST 2009
Wait the end of procedure.
2.2.6 Install NMS Description and 1350OMS 9.6.11 Installation Procedure

Before starting with the NMS predispose action, you have to install the 1350OMS 9.6.11 Installation Procedure and NMS description. To install 1350OMS 9.6.11 installation procedure you have to execute the following procedure: a) b) c) Login the system as root user. ...,sys,root # cd /alu/DEPOT [Enter] Install the NMS description by entering the command: ...,sys,root # swinstall -s /alu/DEPOT/1350OMS-MW_OS-SWPDESC-9.6.0.0.09.sdpkg \* [Enter] Install the Install_Wizard" software from medium by entering the command: ...,sys,root # sh ./Install_Wizard-R9.6.1.1.0UX [Enter] ...,sys,root # sh ./Install_Wizard_CMD-R9.6.1.1.0UX [Enter] If the remote shell (remsh) fails with error: remshd: Login incorrect. check the depot machine access authorization (see paragraph 2.2.2.2 at page 58)
N.B.
2.2.7 Predispose for Installation

Now you have to predispose in one shot the entire system, that means you must know which system configuration you have to create, in term of software and data. Because there are some possible AlcatelLucent NMS/NMC combinations, it is advisable to identify the software and the data instances you have to predispose for before starting. The 1350OMS-MW-INT modular approach allows to predispose the machine after the hp-ux Operating System installation, this is performed on demand by a specific script. In this paragraph will be shown: how to predispose the system to be able to run 1350OMS-MW-INT, because it has to be always installed. Then it will be provided an example of EML, and a generic example for all the other NMS. 2.2.7.1 Start the SWP Manager Script To be able to start the Software Package predispose script you have to login as root user and enter the command: ...,sys,root # scmanageswp [Enter] N.B. VERY IMPORTANT: The whole installation has been described as a single predispose action. This means you have to predispose all the NMS and NMS instances in one shot. This allows to save time and to do not meet problems in disk space computation. If you have to interrupt the predisposal in the middle of the selection, exit the procedure choosing Exit" to abort the procedure itself.
The following menu` will be shown on the screen: ---------------SWP MAIN MENU 1 2 3 4 5 6 7 8 a e -
----------------
Predispose new SWP View predisposed and manage SWP Remove SWP Create new SWP INSTANCE View created and manage SWP INSTANCE Remove SWP INSTANCE Convert SWP INSTANCE Install 3PP Optional software Apply Exit
Insert choice and press [Enter]: 1 Select option 1 in order to predispose for a new SWP installation. First of all you have to predispose for the MW_INT.
2.2.7.2 Predispose for 1350OMS-MW-INT First of all you have to predispose the system for 1350OMS-MW-INT, in fact it has always to be installed as first. The SWP description defined on system will be shown. Predispose new SWP Item ---1 2 3 4 5 6 7 8 SWP Name --------------EML EOMS HA MW_INT NPR PKT SDH WDM SWP Version ----------9.6 9.6 9.6 9.6 9.6 9.6 9.6 9.6
Enter 'q' to Quit, 'd' to Display again or the Item Number : [Enter] Enter the MW_INT item number to select it for the predisposition. The procedure will ask you to confirm the choice. Selected SWP 'MW_INT 9.6' Please confirm your selection ? (y/n) Confirm by entering: y [Enter] All the layered software selected to the SWP predisposal will be shown: TRANSLATOR procedure activated ... Product Name Analysing Product Analysing Product ..... Analysing Product Analysing Product ..... ..... Analysing Product TRANSLATOR procedure Alcatel-OVDL Apache2 GoGlobal-UX IlogViews50 Product Version 2.1 B.2.2 2.2 5.0
unzip was successful.
5.52
Press [Enter] to continue. The 1350OMS-MW-INT is now stored for the predisposal that will be done leaving the script. Drive back the scmanageswp" tool to the SWP MAIN MENU" entering q to predispose for Global Instance .
2.2.7.3 Predispose for 1350OMS-MW-INT Global Instance At SWP MAIN MENU" enter 4" to select Create new SWP INSTANCE". The following menu will be shown: Create new INSTANCE Item SWP Name SWP Version Session ---- --------------- ----------- ------1 MW_INT 9.6 NEW Enter 'q' to Quit, 'd' to Display again or the Item Number : Enter 1[Enter]" to select the 1350OMS-MW-INT, and the possible instance will be shown with: List of available INSTANCE dimension for SWP: MW_INT 9.6 Item INSTANCE Dimension INSTANCE Description ---- -------------------- -------------------------------------------------1 MWINT 1350OMS-MW-INT 8.2 Global Instance Enter 'q' to Quit, 'd' to Display again or the Item Number : Enter 1 [Enter]" to select MWINT Global Instance. Then the tool will ask you to: Insert the Instance Number for 'MWINT' Enter 1 [Enter]". Do you like a Multi-Volume group configuration ? (y/n) Reply with n [Enter]". Then the selection will be shown: Selected INSTANCE: Dimension Number Multi-Volume MWINT 1 NO
Please confirm your selection ? (y/n) Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the required software: TRANSLATOR procedure activated ... Note: There aren't kernel parameters defined. Note: There aren't additional components defined. TRANSLATOR procedure was successful. Press [Enter] to continue. 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. Installation Guide - Volume 1: HPUX Install and Customize 1350OMS Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 65/176
2.2.7.4 Predispose for EML This section describes the EML predisposal, it is provided to better clarify the procedure behavior, but you have to execute it only if you need the EML functionality, otherwise go to next paragraph Predispose for NMS" 2.2.7.5 at page 70. 2.2.7.4.1 Predispose for EML Software EML subsystems is organized in two components: the software code and instance. You have to predispose the software code once, but you can create one or more instances. Because of this there are two different actions, where the second can be iterated more than once. Proceeding in the script execution, after the 1350OMS-MW-INT predisposal the script prompt you again for choosing the next software package, you have in any case to install something of EML, so enter: 1 [Enter] to predispose new SWP, the SWP description defined on system will be shown again: Predispose new SWP Item SWP Name SWP Version ---- --------------- ----------1 EML 9.6 2 HA 9.6 3 NPR 9.6 4 PKT 9.6 5 SDH 9.6 6 WDM 9.6 Enter 'q' to Quit, 'd' to Display again or the Item Number : Enter the EML item number to procede, the selected product is shown to check the right choice: Selected SWP 'EML 9.6' Please confirm your selection ? (y/n) After the confirm action the procedure analyzes the description showing all the software layers required:
Product Name Analysing Product Analysing Product Analysing Product . . . Analysing Product TRANSLATOR procedure Alcatel-OVDL Ant Commons
Product Version 2.1 1.7 0.0
xercesj was successful.
2.7
Press [Enter] to continue. Press [Enter] to proceed, then, exit to the Software predisposal by entering q[Enter]" to came back to the SWP MAIN MENU" and be able to create the instance.
2.2.7.4.2 Predispose for EML Instance The EML Instance define the behavior of the application, you have three possibilities: 1) Predispose for a EML Information Manager (IM), if you want to install a EML stand alone or SDH cohosted system. Predispose for a EML Spare IM, if you are installing the spare system in a 1350OMS-HA configuration. Predispose for a EML Client, if you just want to have the EML Presentation function on any other NMS. In this case you have to create an instance for each EML IM and the Instance Identification number must be the same of the referred IM.
2)
3)
Hereafter the sequence of actions you have to perform to carry out the job. At SWP MAIN MENU" prompt you have to enter 4" to get in the Create new SWP INSTANCE": ---------------1 2 4 5 8 a e SWP MAIN MENU ----------------
Predispose new SWP View predisposed and managed SWP Create new SWP INSTANCE View created and managed SWP INSTANCE Install 3PP Optional software Apply Exit
Insert choice and press [Enter]: 4 [Enter] The already predisposed NMS will be shown in a list, enter the item of EML: Create new INSTANCE Item SWP Name ---- --------------1 EML 2 MW_INT
SWP Version ----------9.6 9.6
Session ------NEW NEW 1 [Enter]
Enter 'q' to Quit, 'd' to Display again or the Item Number :
The list of the EML possible instances foreseen for the specific machine model is provided. List of available INSTANCE dimension for SWP: EML 9.6 Item INSTANCE Dimension INSTANCE Description --- -------------------- ---------------------------------------------1 EML_IM_Small EML Master (IM) System Small Configuration 2 EML_IM_Medium EML Master (IM) System Medium Configuration 3 EML_IM_Large EML Master (IM) System Large Configuration 4 EML_US EML Client (US) Enter 'q' to Quit, 'd' to Display again or the Item Number :
Before entering the instance item number for the selection, read carefully the meaningful of each item in the following table: Table 6. EML Instances Instance type item EML_IM_Small EML_IM_Medium EML_IM_Large EML_US N.B. Entry level configuration Middle range configuration High end configuration EML Client (US) The EML_US instance is not defined for 1350OMS-HA protection Description
Then define the instance identifier: Insert the Instance Number for 'EML_IM_Small': The multiple volume group is not foreseen for 1350OMS 9.6, so reply n to the following question: Do you like a Multi-Volume group configuration ? (y/n) After the volume group configuration, the procedure summarize the information asking you to confirm your choice: Selected INSTANCE: Dimension Number Multi-Volume EML_IM_Small 3 NO
Please confirm your selection ? (y/n) Confirm or refuse the selection.
If you confirm the procedure will predispose for the installation of the required software:
TRANSLATOR procedure activated ... Note: the volume group defined in the "EML 9.6" descriptor will not take in account, because multi_volume_group option is not set. Volume group vg00 will be used for mount point: /usr/Systems/EML_3_9.6_Master Note: the volume group defined in the "EML 9.6" descriptor will not take in account, because multi_volume_group option is not set. Volume group vg00 will be used for mount point: /usr/Systems/EML_3_9.6_Master/ maintenance
Product Name Analysing Analysing Analysing Analysing Analysing Analysing Analysing Analysing Product Product Product Product Product Product Product Product DBD-MySQL DBD-MySQL DBD-Oracle580 DBD-Oracle588 DBI-1.32 MySQL Oracle10g_Client Oracle10g
Product Version 2.1026 3.0004 1.17 1.17 1.32 5.1 1.0 11.2.0
OPTIONAL Product: Oracle11g

Product Description: Oracle 11g (Version 11.2.0.2 + Patches) for HP-UX 11.31 ia64 64Bit
Do you like to install it ? (y/n) Reply y only if you have to configure in your system SNA or TNA elements. Remember: in this case, you must have ORACLE license. N.B. In the future will be determined whether, how and when, to install one, the other or both. Analysing Product Analysing Product Analysing Product Analysing Product Analysing Product TRANSLATOR procedure Snmp4j Snmp4j Snmp4j jsch jta was successful. 1.11 1.7 1.9 0.1 2.6
Press [Enter] to continue. If you have to create more than one instance, enter the item number of the menu that corresponds to the type you want to create, enter the instance number and multiple volume option. Otherwise enter q [Enter]" twice to go back to the previous menu level.
2.2.7.5 Predispose for other NMS/NMC Any other NMS predisposal has a similar behavior, the only differences are related to the possible instances available. This activity has to be performed only if you plan to have any other functionality on the machine you are installing. NMS has the same organization of EML, software code and data areas; hereafter the predisposal script behavior is shown. Do NOT predispose SDH and NPR altogether on the same machine (SDH includes all NPR functionalities). NPR must be installed only when/if SDH is not installed.
2.2.7.5.1 Predispose for NMS Software In both cases, if you have to start scmanageswp" or proceeding from the EML predisposal, you have the SWP MAIN MENU" on the screen, enter: 1 [Enter] to get on the next menu: ---------------1 2 4 5 8 a e SWP MAIN MENU ----------------
Insert choice and press [Enter]: 1 [Enter] The remaining NMS descriptions will be shown. Predispose new SWP Item SWP Name SWP Version ---- --------------- ----------1 HA 9.6 2 NPR 9.6 3 PKT 9.6 4 SDH 9.6 5 WDM 9.6 Enter 'q' to Quit, 'd' to Display again or the Item Number : Select a NMS of 1350OMS 9.6.11 you want to predispose among: HA 9.6, PTK 9.6, SDH 9.6, NPR 9.6 (remember do NOT predispose SDH and NPR together), WDM 9.6. Enter the item number shown in the first column of the menu, then press [Enter] : Then it asks you to confirm your choice, by showing you the selected NMS, enter y [Enter]" if it is correct: Selected SWP '<NMS name>' Please confirm your selection ? (y/n) y[Enter]
The procedure start the description analysis issuing the following messages: TRANSLATOR procedure activated ... . The output depends by the chosen NMS . TRANSLATOR procedure was successful. Press [Enter] to continue. Press [Enter] to proceed, then, exit from the Software predisposal by entering q [Enter]" twice to come back to the SWP MAIN MENU" and be able to create the instance: Predispose new SWP Item SWP Name SWP Version ---- --------------- ----------. The output depends by the chosen NMS . Enter 'q' to Quit, 'd' to Display again or the Item Number : Choose any other NMS you have to predispose, or enter q [Enter]" to complete the NMS software selection. Enter q [Enter]" again to go to the SWP MAIN MENU. 2.2.7.5.2 Create NMS Instance This paragraph shows how to create a NMS instance for the specific data storage. Create the NMS Instances, taking also into account the functional dependencies shown in paragraphs 1.2.7 and 1.2.8 at page 24-25. ---------------1 2 4 5 8 a e SWP MAIN MENU ----------------
Insert choice and press [Enter]: 4 [Enter]
The installed software list is shown, you have to choose the item related to the NMS you has predisposed in the previous step (2 in the example): Create new INSTANCE Item ---1 2 3 SWP Name SWP Version -------------------------EML 9.6 <NMS name> <NMS version> MW_INT 9.6 Session ------YES YES YES
Enter 'q' to Quit, 'd' to Display again or the Item Number : Select the item corresponding to the instance you want to create, enter it followed by [Enter]. The list of allowed instances for that NMS will be shown. For system with HA you have to predispose a HA instance for each NMS subjected to protection. Moreover the HA instance number must be assigned, by the following rules: HA_IM Instance Number >= NMS Master Instance Number HA_US Instance Number >= NMS Presentation Instance Number The procedure will ask you for two information: the instance number identifier and the multiple volume group. N.B. N.B. N.B. N.B. The instance identifier have to be defined in a plan, and be unique for the Master instances in the whole network. The instance number must be equal between Master-Spare systems. Remember the instance number, because it has to be entered again later. For NMS Cohosted with 1350OMS-HA, create the client file system for the NMS lower layers (refer to Network Management Sub-Systems Functional Dependencies" paragraph 1.2.7 at page 24 for architecture, and to 1350OMS-HA Post Predisposal" paragraph 2.2.8 page 80 for more information). Due of a restriction of the NMS PKT, instances of NMS SDH and WDM CAN NOT BE DEFINED with the same identification number. Although it is not expected to be installed PKT, it is strictly advised not to award the SDH and WDM applications the same identifier. Enter the instance number followed by [Enter] to proceed: Insert the Instance Number for '<NMS Instance Type>': Do you like a Multi-Volume group configuration ? (y/n) After the volume group configuration, the procedure summarize the information asking you to confirm your choice: Selected INSTANCE: Dimension Number Multi-Volume <NMS Instance Type> <NMS Instance Identifier> <NMS Instance rule>
Please confirm your selection ? (y/n)
Confirm or refute the selection. If you confirm the procedure will predispose for the installation of the eventual required software: TRANSLATOR procedure activated ... . The output depends by the chosen NMS . TRANSLATOR procedure was successful. Press [Enter] to continue. The procedure shows again the list of possible instance for the next choice, enter q [Enter]" to go back to the previous menu level. List of available INSTANCE dimension for SWP: <NMS name> 9.6 Item INSTANCE Dimension INSTANCE Description ---- -------------------- --------------------------------------------.... Enter 'q' to Quit, 'd' to Display again or the Item Number : q [Enter] Enter q [Enter]" again to go back to SWP MAIN MENU.
2.2.7.6 Leave the Script and Execute the predisposal To speed-up the predisposal execution and reduce the disk fragmentation, the predisposal is executed when leaving the script. To execute the predisposal for all the software you have to exit the SWP MAIN MENU" by entering a[Enter]": ---------------1 2 4 5 8 a e SWP MAIN MENU ----------------
Insert choice and press [Enter]: a [Enter] The list of the pending action will be shown: Items SELECTED for the CONFIGURATION Item Type SWP Name SWP Version INSTANCE Number INSTANCE Dimension --------- -------- ----------- --------------- -----------------SWP MW_INT 9.6 INSTANCE MW_INT 9.6 1 MWINT SWP <NMS name> <NMS ver.> INSTANCE <NMS name> <NMS ver.> 1 <NMS name>_IM_Small Enter 'a' to Apply, 'c' to Cancel or 'd' to Display again: Confirm your choice by entering a[Enter]" (as apply) or cancel. Then procedure start executing the requested predispositions. 2.2.7.6.1 Software Layer Installation Predisposal Before start the procedure will ask you where to find all the software packages, by issuing the following message: SOFTWARE 3PP predisposition activated ... Now you have to specify where are stored the LAYERED PRODUCTS. Press [Enter] to continue. ------------LAYERED PRODUCTS Repository ----------Opt ---
1 - CD-ROM or DVD media 2 - Software Depot 3 - ISO Image Directory q - quit Insert choice and press [Enter]: You can choose between media, network depot or ISO Image.
2.2.7.6.1.1 Software Layer Installation Predisposal from media Here the DVD choice is shown, enter 1 [Enter]" --- Device selection for LAYERED Products installation ---Enter 'q' to Quit or the CD device [def=/dev/dsk/cxtxdx]: The procedure requires you to specify the driver. Press enter to default. 2.2.7.6.1.2 Software Layer Installation Predisposal from Depot Here the network depot choice is shown, enter 2 [Enter]" --- Depot selection for LAYERED Products installation Enter 'q' to Quit or the Depot absolute path name: The procedure requires you to specify the depot, enter: <depot hostname>:/alu/SCDEPOT [Enter] Where you have to replace <depot hostname>" with the name of the depot machine (see at paragraph Create Software Depots 2.2.2.1 at page 57) 2.2.7.6.1.3 Software Layer Installation Predisposal from ISO Image Directory Here the ISO Image choice is shown, enter 3 [Enter]" --- ISO image directory selection for LAYERED Products installation ---Enter 'q' to Quit or the Directory absolute path name: The procedure requires you to specify the Directory. 2.2.7.6.2 Disk Configuration Now the procedure check the space available inside the existing file systems and creates the new requested ones. The entire activity is carried out automatically, but not unattended. In fact there are two cases where the operator attention is required. File system busy New hard disk allocation ----
2.2.7.6.2.1 File system Busy The operator attention is required when predispose requires a file system extension and there are one or more open files in it. In this case the file system is busy, and the extension it is not allowed. A message like the following is issued. ___________________________________________________________________________ Analyze Mount Point:"/opt" Request Current Current Current free: size: used: free: 1072 MegaByte(s) 1536 MegaByte(s) 512 MegaByte(s) 960 MegaByte(s)
Evaluate size: 1792 MegaByte(s) File System:"/dev/vg00/lvol5" is busy, check process with pid(s): 1780 2070 1366 1758 1785 2069 2059 2067 2052 2096 3719 When such a message occurs during the predispose, replay with "R[Enter]" to postpone the file system extension to the next reboot. Press: [T] = Try again (but after you have attempt to close all pid(s) ) [A] = Abort (DANGEROUS - operation is aborted) [R] = Reboot (RECOMMENDED - operation will be completed after next reboot) then press [Enter] 2.2.7.6.3 Kernel Configuration The next execution phase regards the HP-UXTM Kernel configuration. The kernel resources have to be increased to allow the machine to run the application. This phase does not require any human intervention. KERNEL configuration activated ... WARNING: FORCE operator defined for variable 'filecache_max' removing others operators. Creating new kernel configuration ... .... .... .... KERNEL configuration was successful. Dont worry if the system shows error message like following, on condition that the configurations ends with success: ERROR: The requested changes could not be applied to the currently running system, for the following reasons: - The tunable 'ksi_send_max' cannot be changed without a reboot. - The tunable 'semmns' cannot be changed without a reboot. * The configuration 'sck_new' has been marked for use at next boot.
2.2.7.6.3.1 New Hard Disk Allocation During the file system extension it may occur that the initial disk configuration it is not enough to store the 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 ... ____________________________________________________________________ Analyze Mount Point:"/alu/1350OMS9.6" Request free: 11100 MegaByte(s)
Evaluate size: 13056 MegaByte(s) Hardware detection in progress, please wait ....... .... Total disk(s) found = 6 Total CDRoms found = 1 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. 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. _______________________________________________________________________ Disks Selection Mount Point need 5632 MBytes on Volume Group: /dev/vg00" (pvg0) _______________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup _______________________________________________________________________ c1t2d0 139968 0/0/1/1.2.0 Pri_Boot _Main_ vg00 c2t2d0 139968 0/0/2/0.2.0 Alt_Boot Mirror vg00 SD c4t8d0 139968 0/4/0/0.8.0 _(free)_ ______ _____ SD c4t9d0 139968 0/4/0/0.9.0 _(free)_ ______ _____ c6t12d0 139968 0/6/0/0.12.0 _(free)_ ______ _____ c6t13d0 139968 0/6/0/0.13.0 _(free)_ ______ _____ _______________________________________________________________________ Select Data Area (Main instance) dev name or [q] to quit: Enter the name of a free" disk.
N.B.
_______________________________________________________________________ Disks Selection _______________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup _______________________________________________________________________ c1t2d0 139968 0/0/1/1.2.0 Pri_Boot _Main_ vg00 c2t2d0 139968 0/0/2/0.2.0 Alt_Boot Mirror vg00 D c4t8d0 139968 0/4/0/0.8.0 _(free)_ ______ _____ D c4t9d0 139968 0/4/0/0.9.0 _(free)_ ______ _____ c6t12d0 139968 0/6/0/0.12.0 _(free)_ ______ _____ c6t13d0 139968 0/6/0/0.13.0 _(free)_ ______ _____ _______________________________________________________________________ Confirm selection of device "c6t12d0" Press [y] for yes, [n] for no or [q] to quit, then press [Enter] After your confirmation, the disk contents will be irremediably lost!! When a new volume group is created and the mirror disk is enabled, the procedure will ask to configure the mirror disk function also on the new volume group, you have to replay with y for yes, if your system is mirror protected via software, or with n for no, if your data is protected by Smart Array or any other hardware equipment. Do you want use Mirror on current Volume Group: "/dev/disk2" Press [y] for yes or [n] for no, then press [Enter] If you reply y or the new hard disk is requested by a mirrored volume group the procedure can ask you for an additional hard disk. When the hard disk space requirement will be meet, the procedure will continue its job. Physical volume "/dev/rdsk/c6t12d0" 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 computed following the instructions shown in the paragraph Requested Hard Disks" 1.1.1.4 at page 21.
2.2.7.6.4 Software Layer Installation The last message issued before starting the software package installation is: =>>> WARNING: The 3PP software will be installed during the reboot. =>>> NOTE : Attend the installation if you choose to install from the CD|DVD, media substitution could be required. ATTENTION: now to complete the configuration Shutdown-Reboot will be executed. Press [Enter] to continue. Reply by pressing [Enter], the machine will be automatically rebooted and software components installed. If you are installing with 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.2.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.31] (see /etc/issue) Console Login:
2.2.8 1350OMS-HA Post Predisposal

When there are two or more cohosted NMS Master instances and the system has also the 1350OMSHA failure protection, some additional action are required after the system predisposal and before customizing the software. In this conditions 1350OMS-HA maximizes system performance allowing to use both master and spare servers for performing the normal operations, recovering the faulty application on a single server. The following figure shows how the 1350OMS-HA manages these faulty conditions, it is important to note in the example how SDH is communicating with EML in the two cases: When both machine are operational, SDH and EML communication occurs via EML Client instance on board of SDH machine. When one of the two systems is out of service, the communication are direct
The software component shown in Figure 7.in gray color are not operational, them can be the stand-by instances created by 1350OMS-HA. Server hosta SDH Master Active Normal system Operation EML Client EML Master Stand-By Server hostb SDH Master Stand-By EML Client EML Master Active
Server hosta SDH Master Active EML Client EML Master Active
Server hostb
System failure example.
FAULT
Figure 7. 1350OMS-HA communication example. In this scenario EML provide services to SDH through its client instance or directly, depending by the situation. The same approach can be operated by SDH when cohosts with PKT. Now you have to create manually the NMS Client to allow inter-NMS communication has shown in the following paragraphs.
2.2.8.1 Manage NMS Master-Client cohosted When a NMS Master -Client cohosting on same node, you have to create the NMS client data instance file system manually, by entering the following command:
...,sys, root # scextendfs /usr/Systems/<NMS>_<NMS_INSTANCE>_9.6_Presentation <size> [Enter]
Where: <NMS> has to be replaced by the NMS <NMS Instance> has to be replaced by the NMS Instance identified associated. <size> has to be replaced by the value
2.3 Operating System Configuration

This chapter shows the minimum operating system and platform configuration required to allow TMN machine inter-working.
2.3.1 Node Name Management

Before proceeding in installing and customizing 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 7. Involved IP Network Node table Type Alcatel-Lucent TNM system Printers Time synchronization systems Description Any HP server with Alcatel-Lucent TNM on board, that have to communicate with the machine you are installing. Any network printer that have to be used by the machine you are installing. Any Time synchronization equipment reachable via IP network.
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.3.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. hosta Printer GPS synchronization system
There are other network equipment, such as rooters, printers (local and network), personal computer, and time synchronization equipment. You have to identify the equipment specified by Table 7.at page 82, 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) 192.202.21.6
hosta IP 192.202.21.8
Figure 8. 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 management 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.
2.3.2 Synchronize the Clocks

The clock synchronization is mandatory for system working together with Kerberos authentication tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305 has to be configured by following 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) b) c) d) The primary time sources have to be reliable ones, such as a Global Position System (GPS) receiver time source. Define two or three time-server machines. Each time-server should be a peer with of the other timeservers. If possible, do not synchronize multiple time-servers to the same outside source. 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: EML and SDH co-hosted with HA. 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
WAN
GPS Receiver 1 IP 192.202.21.51 WAN
GPS Receiver 2 IP 192.202.22.20
hosta IP 192.200.49.1
hostb IP 192.202.21.7
hostc IP 192.202.21.8
hostd IP 192.202.22.4
hoste IP 192.202.22.5
Figure 9. NTP Configuration Example
To obtain such a configuration the three time servers you have to declare the two 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 gpsrec1 prefer server gpsrec2 peer hosta peer hostd hostd server gpsrec1 server gpsrec2 prefer 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 Insert choice and press [Enter]:
to simplify the explanation, the procedure shows how to configure the server hostb and hosta of Figure 9.at page 84. Note, the configuration order is relevant for the system behavior, it is better to start configuring the nodes more close to the Timeservers. 2.3.2.1 Configure hostb This is the procedure using scxntp script to configure the hostb of Figure 9.at page 84. a) b) c) Login hostb as root user. Start the scxntp script by entering: scxntp [Enter] Define the preferred timeserver: Insert choice and press [Enter]: 1 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 ... Define the secondary timeserver: Insert choice and press [Enter]: 1 Enter server hostname or IP address or q for Quit : 192.202.22.20 NOTE: Checking the configuration ... Would you like to set 192.202.22.20 as preferred (y/n) ? n NOTE: Updating /etc/ntp.conf adding server 192.202.22.20 ... Press return to continue ... For each peer hosts enter: Enter server hostname or IP address or q for Quit : 192.202.21.8 NOTE: Checking the configuration ... Would you like to set 192.202.21.8 as preferred (y/n) ? n NOTE: Updating /etc/ntp.conf adding peer 192.202.21.8 ... Press return to continue ... 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: Insert choice and press [Enter]: 8 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... Press return to continue ... Leave script by entering e" or q".
d)
e)
f)
g)
2.3.2.2 Configure host This is the procedure using scxntp script to configure the hosta of Figure 9.at page 84. a) b) c) Login hosta as root user. Start the scxntp script by entering: scxntp [Enter] Define the preferred timeserver: Insert choice and press [Enter]: 1 Enter server hostname or IP address or q for Quit : 192.202.21.7 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 ... Define the other two timeserver: Insert choice and press [Enter]: 1 Enter server hostname or IP address or q for Quit : 192.202.21.8 NOTE: Checking the configuration ... Would you like to set 192.202.22.20 as preferred (y/n) ? n NOTE: Updating /etc/ntp.conf adding server 192.202.22.20 ... Press return to continue ... 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: Insert choice and press [Enter]: 8 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... Press return to continue ... Leave script by entering e" or q".
d)
e)
f)
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 daemon has to be stopped and started each time the configuration changes. Usually the NTP daemon is not running.
2.3.2.3 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 Insert choice and press [Enter]: 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.3.3 Configure License Manager

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 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.3.3.1 Alcatel-Lucent license (Poseidon) See Appendix D at page 159 in order to configure Alcatel -Lucent license. 2.3.3.2 GoGlobal license See Appendix C at page 143 in order to configure GoGlobal license.
2.3.4 Enable GoGlobal Connection

By deafult, GoGlobal-UX is configured so that root connections are NOT allowed. In order to enable root connections by GoGlobal-UX (e.g.: in order to install Alcatel-Lucent Network Management software), it is necessary to execute (logged as root), the following command: ...,sys,root # scEnableGoGlobal [Enter] DATE: Mon Nov 23 16:58:52 MET 2009 PAM configured with Default Goglobal root access enable WARNING: The network access via GOGLOBAL has been enabled for root. This can be a security weakness.
2.4 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 target, and then adapted to the target host by the customizing phase.
Before start check if you have the necessary DVD, a software depot with the entire software, or all the necessary information to download it.
Check if local system is correctly authorized to access the files (see 2.2.2.3 for more informations).
2.4.1 Automatic Install and Customize NMS and NMC

Installing "from scratch", it is suggested to apply the Automatic Installation procedure.
Install Wizard tool supports the full Network Management software installation on one machine, by performing 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; - customize all the SWP instances detected during the previous step. NOTE: For this version, the installation from CDROM is NOT supported, then you should create a Alcatel software depot as described at paragraph Create AlcatelLucent NMS Depot on page 57. Moreover is required to use the -fast parameter. 2.4.1.1 Automatic Install NMS and NMC Login the system as root user with a graphical session. ...,sys,root # cd /alu/Install_Wizard [Enter] Start the automatic installation procedure by executing: ...,sys,root # ./Install.sh -fast_install [Enter] The procedure will ask you for Depot hostname and address or for Device name, according to previous choice. In case of fast installation, a different installation shell will be automatically started, one for NMS predisposed, with different colors like showing in the following window:
Figure 10. Automatic and Fast Install and Customize The procedure starts installing all the software previously predispose. The installation tool asks for optional element (HA , IOO, MED, CPB), select for those ones are present in your system. N.B. In order to have SDH correctly integrated with PKT, it is MANDATORY to install and configure, on SDH Master machine, the MED component. In order to have EML correctly integrated with WDM, it is MANDATORY to install and configure, on EML Master machine, the CPB component.
N.B.
2.4.1.2 Automatic Custom NMS Now start the automatic customize procedure by executing ...,sys,root # cd /alu/Install_Wizard [Enter] ...,sys,root # ./Install.sh -fast_custom [Enter] The Custom GUI for MW-INT package will be automatically started, after that, the System, Instances List" window will be shown on the screen. Select Choose_one" and then New-Instance" , then select Apply & exit" in the Actions menu. In case of EML, the Custom Product Selection EML <Instance Id>" window will be shown on the screen after a few seconds. Select the Network Element family you want to configure, then apply and Exit the data on the window(s). At the end of customization phase, the procedure ask for configured of all NMS. Take into account the notes described at paragraph System Configuration at page 102
Figure 11. Automatic and Fast Install and Customize 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 # . /alu/Kernel/env/Kernel [Enter] ...,sys,root # /alu/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: /alu/Install_Wizard/log/Installation_All_#.log /alu/Install_Wizard/log/Installation_<NMS/NMC>_#.log /alu/Kernel/maintenance/trace/Custom.trace /alu/Kernel/maintenance/log/Custom.log After the Installation completion restart MW-INT services by executing (logged as root): ...,sys,root # /alu/Kernel/script/KernelServices stop [Enter] ...,sys,root # /alu/Kernel/script/KernelServices start [Enter] Continue the procedure with paragraph NMS Special Installation Instruction at page 106.
2.4.2 Manual Install and Customize NMS and NMC

2.4.2.1 Manual Install and Customize 1350OMS-MW-INT The Alcatel-Lucent 1350OMS-MW-INT is the operational platform, so it must be the first software installed. To install 1350OMS-MW-INT Install.sh" procedure requires: The depot machine is available, and the local system is correctly authorized to access the files (see 2.2.2.2 at page 58 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. In order to prevent error messages during the 1350OMS-MW-INT customize it is advisable to configure the GoGlobal-UX license as shown in 1350 Administration Guide" [2]. GoGlobal-UX will be stopped by 1350OMS-MW-INT configuration script. DO NOT start the Install.sh with 1350OMS-MW-INT option from any window open via GoGlobal-UX, because all the GoGlobal-UX windows will be closed, and the configuration aborted!
N.B.
If the mentioned requirement are matched, the installation and custom can be started by entering: ...,sys,root # cd /alu/Install_Wizard [Enter] 1) Start the installation script entering: ...,sys,root# ./Install.sh MW-INT <hostname> <directory> [Enter] Where: <hostname> means the depot machine hostname <directory>means directory path on depot machine where depot is located. (usually /alu/DEPOT)
The script start issuing the following mask: ########## ################# ################ ## ########### ## ### ########### ## ### ## ########## ### ###### ## ########## #### ####### ## ######### #### ######### ## ######## ##### ############## ####### #### ############### ###### ##### ############### ##### ###### ############### ##### ####### ############### ############## ############### ############# ###### ######## ############ #### ######## ########## ####### ######### ######### ################# ##########
__ / | //|| // || // || / ||
_ ___ __ ____ ___ _ _ _ _ || / _| / | |_ _| |___| || || || || / || || //|| || ||_ || __ || || || || || // || || | _| |||__||| || || ||_ ||_ // || || ||__ ||_ ||_ ||_|| |__| \__| // || || |___| |__| |__| \___/
__ ___ _| |___| | || ||_ || | _| ||_ ||__ \__| |___|
_ _ ____ \| | |_ _| | \| | || ||\ | || || \ | || || \| ||
Installation MW-INT package =========================================================================== LOADING: ###################################################################### NOTE: Session started on: Fri Nov 30 17:22:25 MET 2007 NOTE: Set HP-UX environment ... NOTE: Setting language to: C.iso88591 ... NOTE: Hardware 9000/800 supported ... NOTE: Check installation ongoing ... NOTE: Please enter the Device Name of source media [c0t0d0]: Confirm or change the suggested source media. NOTE: Preparing to install ... NOTE: Check pkg INSTALLER_7.1.4.11.tar ... NOTE: Preparing to INSTALLER 7.1.4.11 ... =========================================================================== The installation is executed by INSTALLER that shows you the contents of the package : =========================================================================== Installation MW-INT package =========================================================================== *************************************************************************** NOTE: rm -rf /home/*/.WebEnabler NOTE: NOTE: .... 11/30/07 17:22:33 - Executing MW-INT pre_install_wa ... 11/30/07 17:22:33 - MW-INT pre_install_wa completed ...
The installation start automatically, this step will take up to 20 minutes. The last question is related to the MW-INT custom; you have to reply also this question with y[Enter]" Do you want to execute MW-INT Custom? [y|n|q] y [Enter] Then the MW-INT custom will be executed showing the trace on the terminal. ******************************************************************* NOTE: ${INSTALL_ROOT}/Kernel/script/KernelCustomize NOTE: . . NOTE: NOTE: NOTE: 12/01/07 08:07:48 - Executing MW-INT custom_cmd ...
Kernel Customization Complete. Reapplying PLT registrations. Check Go-Global 2 configuration ...
The procedure will stop after up to 10 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 custom, and then the procedure will be completed in a couple of minutes issuing: ======================================================================= NOTE: Session finished on: Sat Dec 1 08:16:58 2007 NOTE: Installation MW-INT completed successfully. The MW-INT installation and custom 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: /alu/Install_Wizard/log/Installation_MW-INT_*.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.
2.4.2.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 customize NMS instance.
2.4.2.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 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 as summarized hereafter: a) b) Install all software on the system. Customize all NMS.
Then complete the installation and custom with integrating the systems among themselves. 2.4.2.2.1.1 NMS or NMC Installation Procedure If the mentioned requirement are matched, the installation and custom can be started by entering: a) Login the system via Graphical User interface CDE as root" user. N.B. IF THE INSTALLATION SCRIPT IS STARTED FROM A SHELL WITHOUT A USEFUL DISPLAY VARIABLE SET THE NMS CUSTOM WILL FAIL.
b) c)
Open a dtterm window. Entering the following commands at dtterm prompt: ...,sys,root # cd /alu/Install_Wizard [Enter] ...,sys,root# ./Install.sh -install <NMS/NMC name> <hostname> <directory>[Enter] Where: <NMS/NMC name> NMS or NMC name (including ETH-MEDIATOR). <hostname> means the depot machine hostname <directory> means directory path on depot machine where depot is located. (usually /alu/DEPOT) 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.
########## ################# ################ ## ########### ## ### ########### ## ### ## ########## ### ###### ## ########## #### ####### ## ######### #### ######### ## ######## ##### ############## ####### #### ############### ###### ##### ############### ##### ###### ############### ##### ####### ############### ############## ############### ############# ###### ######## ############ #### ######## ########## ####### ######### ######### ################# ########## __ _ ___ __ ____ ___ _ _ _ _ __ ___ / | || / _| / | |_ _| |___| || || || || / _| |___| | //|| || || //|| || ||_ || __ || || || || ||_ // || || || // || || | _| |||__||| || || || | _| // || ||_ ||_ // || || ||__ ||_ ||_ ||_|| ||_ ||__ / || |__| \__| // || || |___| |__| |__| \___/ \__| |___|
_ _ ____ \| | |_ _| | \| | || ||\ | || || \ | || || \| ||
Installing <NMS/NMC name> package =========================================================================== -------------------------------------------------------------------------NOTE: Preparing to install ... . 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.
2.4.2.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 /alu//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 custom.
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 12. 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. Set the value, then Apply & exit" in the Actions menu to start the execution:
Figure 13. NMS Customize Window Installation Guide - Volume 1: HPUX Install and Customize 1350OMS Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 99/176
In case of EML, the Custom Product Selection EML <Instance Id>" window will be shown on the screen after a few seconds.
Figure 14. NMS Customize Window Select in the list the Network Element family you want to configure: N.B. When customizing a Client instance be sure to select all the NE selected on the Master Instance.
Then pull-down the menu Action" (in the left upper corner), select Apply & exit" to start the custom procedure.
A trace window will be open on the screen showing the customization progress.
Figure 15. NMS Customize trace window The procedure will complete when the [Dismiss] button will be enabled. Warning message, if displayed during EML customization, can be ignored. 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: /alu/Install_Wizard/log/Installation_<NMS name>_*.log
2.5 System Configuration

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 configuration and any restriction used. N.B. On ALL NMS applications (SDH/NPR, PKT, WDM):
The following manual work around for the Database must be applied on all configured NMS applications, after each execution of System Config that generates the database (this occurs both the very first time the System Config is executed, and in subsequent executions in case explicit request is given to regenerate the database). ...,<nms>,<nmsuser> # su - <NMS_USER> \[Enter] ...,<nms>,<nmsuser> # cd <ORACLE_PHYSICAL_INSTANCE_DIR>/script \[Enter] ...,<nms>,<nmsuser> # echo "ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;" > /tmp/script.$$.sql ; ./ExecCommand.sh -t SQL -u sys -r sysdba /tmp/ script.$$.sql ; rm /tmp/script.$$.sql \[Enter] Example: ...,<nms>,<nmsuser> # su - snml \[Enter] ...,<nms>,<nmsuser> # cd /usr/Systems/SDH_3_9.6_Master/ORACLE/script \[Enter] ...,<nms>,<nmsuser> # echo "ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;" > /tmp/script.$$.sql ; ./ExecCommand.sh -t SQL -u sys -r sysdba /tmp/ script.$$.sql ; rm /tmp/script.$$.sql \[Enter]
N.B.
On EML System Configuration: It is mandatory to select MySQL for SNA database. The following error can be ignored: Ignore error like ERROR: 1235 (42000) at ....This version of MySQL doesn't yet support multiple triggers
ERROR 1235 (42000) at line 2: This version of MySQL doesn't yet support 'multiple triggers with the same action time and event for one table' N.B. On EML, PKT, WDM System Configuration: Update_Integration Subsystem must not be selected for configuration (don't mind any warnings about that).
N.B.
On SDH, NPR System Configuration: Update_Integration Subsystem is mandatory and must be selected for configuration .
N.B.
On PKT System Configuration: Remember to assign the instance id of SDH in the field TMP_CESSDHIDENT of 1354BM_CORE_IM parameter window.
N.B.
On SDH/NPR, PKT, WDM System Configuration:
Remember to assign the value NEW to MAPIM database configuration if you have already assing the value NEW to the ORACLE database configuration.
N.B.
1350OMS-HA requires it's own system configuration, refer to 1350OMS-HA User Guide" for more information.
2.5.1 System Configuration trouble shutting

2.5.1.1 SDH / WDM error During SDH and/or WDM System Configuration, an error like the following one could appear : ERROR: : RETURN CODE.: 1 ERROR: : ....ORACLE-configORACLE completed with error DB_CREATE - ORACLE-DB In this case, if the file OracleInt.log contains the following error message: REVOKE EXECUTE ON UTL_HTTP FROM PUBLIC * ERROR at line 1: ORA-00060: deadlock detected while waiting for resource Redo System Configuration with DATABASE parameter set to OLD.
,executing
2.5.2 LAN Assignment

All LAN adapters that have to be used by Alcatel-Lucent 1350OMS must be properly configured with HP System Administration Manager (SAM). After the LAN adapter configuration, for the LAN adapter different than lan0, you have to edit /etc/hosts and remove the hostname. Moreover, each LAN adapter rule has to be defined depending by the NMS that have to be installed and the available LAN adapters. The hereafter table summarizes some rules. Table 8. Lan card configuration Adapter Stack Protocols Constrains
Necom/Q3 OSI
Q3 CMISE Necom can not share the LAN with other OSI NA RFC1006 GRE (= Ip over OSI tunnel support) TL1, SNMP, CLI OSI stack available only on eOMS, OSI LAN not sharable CNA can not share the LAN with other OSI NA
SNA TNA (*) CNA
IP
IP, OSI TL1 OSI CMISE
(*) TNA with TL1/OSI available only on eOMS N.B. LAN card configurable for all the NA
Table 9. Lan card configuration 1350OMS Rel 9.6 Adapter/LAN LAN01 LAN1 LAN2 LAN32 LAN4 LAN5 LAN6 LAN73 Necom/Q3 SNA TNA CNA-EML4 1. 2. 3. 4. N.B. Free LAN assignment. CNA-EML, TNA-OSI and Necom are mutually exclusive. IP stack available on all LANs
Generally reserved for communication with other servers First set of (4) LAN ports (in bundle) Second set of (4) LAN ports, additional (with exceptions of OMS Duplex ones where MSAs do not allow such expansions) could run on same machine with a CNA-EML, single instance
No specific constraint for LAN assignement (LAN1 to LANn). CNA doesnt support multiinstance
2.6 NMS Special Installation Instruction

Some NMS require some more action after the install and custom execution, hereafter the detailed description divided by NMS.
2.6.1 Special Instruction for SDH, NPR

SDH/NPR support only Oracle configuration.
2.6.2 Special Instruction for HA

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

Before starting NMS components processes, it is recommended to stop then start Kernel Services by exewcuting, by root, the following commands: ...,sys,root # /alu/Kernel/script/KernelServices stop [Enter] ...,sys,root # /alu/Kernel/script/KernelServices start [Enter]
2.8 Integration & Federation
VERY IMPORTANT!!
When all the TNM machines have been installed and configured in stand-alone, and before START them, you have to perform the special instructions and run final integration&federation script!
2.8.1 Final Integration&Federation 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. Login as root user. Start the global integration&federation script by executing the following procedure. ...,sys,root # /alu/Install_Wizard/etc/1350_Integration-Federation.sh [Enter] The procedure will apply automatically all the necessary integrations.
2) 3)
2.9 Mandatory W/A

Meaningful only for server where PKT is installed. EVT GUI has External Applications menu grayed, execute the following W/A in order to make menu correct. Login the system as root user and modify the file /usr/Systems/Global_Instance-9.6/WebDesktop/ FMCOMMON/conf/externalNavigation.xml so that it change from: <value>PKT_<id>_9.6</value> to <value>Global_Instance_9.6</value>
2.10 Disable network root access

In order to restore appropriate security level you have now to disable root connections via network by executing the following procedure: a) Login system a root user. ...,sys,root # scDisableGoGlobal [Enter] ...,sys,root # scDisableSSH [Enter]
2.11 Mandatory W/A for Application Start-up

2.11.1 EML RetixStack
If EML RetixStack cant bring up, execute the following commands: a) Login system a root user. ...,sys,root # cd /usr/Systems/EML_<id>/NECOM/script [Enter] ...,sys,root # ./config_NECOM.pl EML <id> /usr/Systems/EML_<id>/Kernel/data/ProcessList.cfg [Enter]
2.11.2 GUI servers

If GUI servers arent connected perform the following action: a) Select from the menu bar Tools => Servers => Connect and start the not connected servers.
3 Web Desktop and Client PC

3.1 Web Desktop
Web Desktop is the NR9.6 available mechanism to access to 1350OMS Network Management software GUI's by a PC connected in the internet. Therefore, having a PC able to connect to a HP-UX server with 1350OMS-HPUX software installed, it is possible to start a connection in two different ways. XT emulation modality: by starting a X terminal emulation using GoGlobal UX. This modality has to be used for SW installation, customization and configuration and in order to get access to any GUI's which are not compatible to Web Desktop. Web Desktop modality: by accessing to Web Desktop starting a web browser and connecting to the HP-UX server with 1350OMS-HPUX software installed. This modality has to be used for normal 1350OMS Network Management software use (e.g.: provisioning, alarms supervision, ...).
3.1.1 Connection to Web Desktop

In order to connect to Web Desktop, execute the following steps. Start the web browser program on the PC and specify in the address field the IP address of the 1350OMS HP-UX server machine to be connected. N.B. N.B. connection is supported only by supplying IP address of server LAN 0 (zero) port. If hostname is specified (instead of IP address), some application could not behave correctly. If the PC was previously used to connect to other 1350OMS machines remember to cleanup the Web Desktop cache and runtime directories..
N.B.
In case of first connection of the PC to a 1350OMS machine, consider that some minutes will be necessary to download on the PC the Java software that must run locally on the PC: wait until the operation is completed. N.B. This behaviour will be adopted for ALL GUI's that will be started for the first time. A window will be displayed, asking for directories to be used for Java temporary files and cache: if default locations are changed, then be sure to specify DIFFERENT directories for temporary files and for cache. A web portal will be displayed, allowing to enter within the web desktop
Installation Guide - Volume 1: HPUX Web Desktop and Client PC
Figure 18. Web Desktop Login N.B. Once the web portal window is displayed on the PC, a popup window will be opened, informing that security initialization is on-going - BEFORE OPENING ANY GUI, please wait until another popup window is opened, informing that security initialization has been completed (~ 1-2 minutes) it is necessary that PC date and time are aligned to the HP-UX server, so that the differences is no more than 5 minutes, otherwise some applications (e.g.: PMC GUI) will not start and/or will not work correctly.
N.B.
Click to Enter. Insert Username and Password to enter, at first login, for security reason it will be requested to setup a new password. N.B. Do not use the " (quotes) character for Web Desktop operator password.
Figure 19. Web Desktop password
3.2 Client PC
The minimum HW configuration for PCs is defined as follows: Processor: Intel Dual Core processor - 1.8 GHz clock Memory: Minimum: 2GB RAM Suggested: 3GB RAM Hard Disk available space: 10GB Software requirements: Operating System: Pre-installed SW:
Microsoft Windows XP SP2 or higher. Internet Explorer 7 JRE 1.6
3.2.1 Pagefile configuration review

Windows Pagefile must be increased to 4GB following this procedure: a) b) Open Windows Control Panel and look for System icon. Double click on System icon to open System Properties window.
c) d)
Locate and select Advanced tab and click on Setting button in Performance section. In Performance Options window click on Change button shown in Virtual Memory section.
e)
In Virtual Memory window change both initial and maximum size to 4092.
N.B.
If shown recommended value is higher then 4092, set the reccomanded value instead.
3.2.2 Host Configuration

In order to have full access to 1350 OMS GUI's via Web Desktop, the PC must be configured so that the HP-UX server can be identified with hostname. This can be obtain via Distributed Name Service (DNS) when configured, or adding the HP-UX server hostname / IP address in the following file: C:\WINDOWS\system32\drivers\etc\hosts N.B. This requires the MS Windows Administrator rights
In order to have a fast and reliable connection between Java renderer applications running on the PC and the applications running on the HP-UX server, it is strongly recommended to configure Java so that proxy is not used. In order to do this, open on your PC: Control Panel -> Java -> Network Settings Select: Direct connection Apply the configuration (clicking on OK button) N.B. After this configuration, if Internet is configured with navigation by a proxy, then consider that java applications started by Internet will no more run by the proxy.
3.3 Troubleshooting
3.3.1 WebEnabler cache
Before to open a Web Desktop connection from a PC to the upgraded server, it is strongly recommended to cleanup PC Web Desktop cache, runtime and web directories. N.B. Verify in the file C:\web\LsmBinder\conf\paramsetting.xml the correct name of directory.
3.3.1.1 Cleanup Cache Directory Remove the directory C\tmp\cacheDir. 3.3.1.2 Cleanup Runtime Directory Remove the directory C\tmp\runtimeDir.
4 Trouble Shooting
Here after is shown how to solve some trouble can occur during the installation, and how to proceed when possible.
4.1 Identify a Failure Condition

Before proceed with the troubleshooting it is suggested to identify the problem. It also important to distinguish 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 ***************** To fix the problem, check the log file in /SCINSTALL/scinstall.log *************************************************************************** N.B. Some system reboot are foreseen to correctly carry on the installation, that means don't worry if the system reboot automatically.
4.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 message: ***** The System reboots automatically, please wait ***** Installation Guide - Volume 1: HPUX Trouble Shooting Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 119/176
4.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 Alcatel-Lucent Technical Excelence Center.
4.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 ******************* To fix the problem, check the log file in /SCINSTALL/scinstall.log *************************************************************************** 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 procedure: 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]
Installation Guide - Volume 1: HPUX Trouble Shooting
for example: ...,sys,root # ls *.in_progress [Enter] 01001SC.SCstdinstall.in_progress ...,sys,root # mv 01001SC.SCstdinstall.in_progress 01001SC.SCstdinstall [Enter]
If chosen 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. 4.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: **************** THIS SYSTEM IS NOT CORRECTLY INSTALLED ***************** Error during execution of scextendfs.reboot To fix the problem, check the log file in /SCINSTALL/scinstall.log ************************************************************************** Look at the /SCINSTALL/scinstall.log" file to know which is the meet problem and how to fix it before proceed. 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.
4.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: **************** THIS SYSTEM IS NOT CORRECTLY INSTALLED ***************** Error during execution of scextendfs.reboot To fix the problem, check the log file in /SCINSTALL/scinstall.log ************************************************************************** Look at the /SCINSTALL/scinstall.log" file to know which is the meet problem and how to fix it before proceed. 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.
4.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 4.3.2.1. The procedure has been abnormally terminated, see paragraph 4.3.2.2.
4.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 work-around describes on paragraph 4.3.1 at page 120,for recover the mistake. 4.3.2.2 scmanageswp Abnormally Terminated scmanageswpuses 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 synchronization 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 command: ...,sys,root # rm -r /tmp/.scswpsession [Enter] Then start again scmanageswp".
4.3.2.3 Install.sh Abnormally Terminated Meaningful during an installation from DVD only. Using the command "Install.sh <NMS/MNC name> -cdrom" to install a generic NMS/NMC Software (1350OMS-EML, 1350OMS-SDH, etc.) from DVD, 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 DVD currently mounted by entering: ...,sys,root# umount /SD_CDROM [Enter] Remove the DVD from the driver. Insert the Software Distribution DVD in the DVD driver. Mount the DVD at /SD_CDROM directory: ...,sys,root # mount -o rr /dev/scdvd /SD_CDROM [Enter] Start again the installation script entering: ...,sys,root# ./Install.sh <NMS/MNC name> -cdrom [Enter]
b) c) d)
e)
4.4 Kerberos Problems

There are two Kerberos known problems with possible troubleshooting.
4.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 command: ...,sys,root # ps -edf | grep kdcd[Enter] The output have to be like: ,sys,root # ps -edf root 573 1 root 916 573 root 9416 9363
| 0 0 0
grep kdcd 12:20:23 ? 0:01 /opt/krb5/sbin/kdcd -l /dev/null 12:20:27 ? 0:04 /opt/krb5/sbin/kdcd -l /dev/null 16:21:30 pts/ta 0:00 grep kdcd
The first work-around 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. ...,sys,root # /sbin/init.d/krbsrv start [Enter]
4.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) b) Login as root user. Stop the kdcd process by entering the command: ...,sys,root # /sbin/init.d/krbsrv stop [Enter] Remove the /vat/tmp/rc_kbrkdcd" file: ...,sys,root #rm /var/tmp/rc_krbkdcd [Enter] Start the kdcd process by entering the command: ...,sys,root # /sbin/init.d/krbsrv start [Enter]
c)
d)
4.5 Device Full

Sometimes a file systems can get full, this situation can occur because different reasons, hereafter some of them are explain.
4.5.1 Device 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) b) Login the system as root" user, Remove the files by entering: ...,sys,root # rm -r /var/adm/sw/save/*[Enter] Cleanup the patch status by entering: ...,sys,root # cleanup -s [Enter]
c)
4.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 ........ Total disk(s) found = 6 Total CDRoms found = 1 Press [Enter] to continue...
___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup ___________________________________________________________________________ c2t0d0 34720 0/1/1/0.0.0 Pri_Boot _Main_ vg00 c2t1d0 34720 0/1/1/0.1.0 _(free)_ ______ __________ ___________________________________________________________________________ Press [Enter] to continue... N.B. If you have a disk mirror protection, the file system extension can ask for more than one disk.
Before proceed within a 1350OMS-HA 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.
4.6 Inittab Process Not restarting

Sometimes the processes specified in /etc/inittab" file whit option respawn" are not re-spawned correctly, it this case can be useful perform the following procedure: a) b) c) d) e) Login the system as root" user, Replace the keyword respawn" with once" in the line corresponding to the not started process. Ask init to re-read the configuration file by entering: ...,sys,root # init q [Enter] Restore back the keyword respawn" instead of once" just modified. Ask again init to re-read the configuration file by entering: ...,sys,root # init q [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 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST39204LC /dev/dsk/c2t2d0 /dev/rdsk/c2t2d0 disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305 /dev/dsk/c3t2d0 /dev/rdsk/c3t2d0 disk 3 0/4/0/0.8.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC /dev/dsk/c4t8d0 /dev/rdsk/c4t8d0 disk 4 0/4/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC /dev/dsk/c4t9d0 /dev/rdsk/c4t9d0 disk 5 0/7/0/0.12.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC /dev/dsk/c5t12d0 /dev/rdsk/c5t12d0 disk 6 0/7/0/0.13.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC /dev/dsk/c5t13d0 /dev/rdsk/c5t13d0 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: The correct device type have to be CD-ROM.
Installation Guide - Volume 1: HPUX System Tips
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 command 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 system 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.
A.3 P400 and P410i Smart Arrays Configuration

HP Smart Array controller implements many RAID disk protections at controller level, the suggested configuration for 1350OMS is: RAID 1 using available hard disks in couple (bay: 8 and 7, 6 and 5, etc.). The Smart Array disk configuration MUST be done before proceed in the hp-ux installation. It doesnt allow changes without loosing the disk contents! To configure you can use Smart Array Option ROM Configuration for Array (ORCA) during the server boot. Unfortunately, ORCA activation procedure depends by server model.
A.3.1 Activate ORCA on rx2660 and rx6600

During server boot sequece, 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. In case you loose the first message, it is possible to have a new one by accessing EFI shell and entring command: reconnect -r 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 columns otherwise the last bottom line will be hidden.
Figure 20. Smart Array P400 Main Menu First of all check the current configuration moving the cursor on "View Logical Drive" and press [Enter]. The recommended configuration foreseen three or four logical drive, where possible in RAID 1 configuration. The following picture shows the expected configuration for a system with 6x146GB hard disks:
Figure 21. Smart Array View Configuration window If you dont have one of the recommended logical drive configuration, you have to remove any existing configuration (see How to delete a Smart Array Logical Drive), and set-up one corresponding to the available hard disk number.
A.3.2 Activate ORCA on rx2800

Hereafter the procedure to activate ORCA on rx2800 server. a) b) Switch on the server with the console connected. Wait anti the following message will be displayed:
Figure 22. rx2800 Boot Primary Menu
c)
Enter S to access UEFI shell.
Figure 23. rx2800 UEFI shell prompt d) e) At UEFI shell prompt entrer command: drivers In the shown list identify the Smart Array SAS Driver line, look at the line begin to read the device identifier shown in the first field. To see decice controller identifier, enter command: drvcfg <device id>
f)
Figure 24. UEFI drvcfg command examples. g) Activate ORCA utiltiy by entering: drvcfg -s <device ID> <controller ID>
Figure 25. Smart Array P410i Main Menu
A.3.3 Smart Array Configuration Rule

Hereafter the rules for Smart Array configuration: a) b) Create logical drive in RAID 1+0 configuration made up two physical drive. Start the logical drive creation from the higher bay numbers.
A.3.4 Create RAID 1+0 Logical Drive

To create new Logical Drive, staring from ORCA main menu shown at Figure 20., you have to select Create Logical Drive and press [Enter]. The following window will be display:
Figure 26. 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 27. Smart Array Create window - 2
Press <Esc>+8 (or <F8>) to confirm, then press [Enter] to return to main menu. Repeat all the same operations to configure all disks equipped. Then press <Esc> to exit to Smart Array configuration, the system will return to the BOOT sequence.
A.3.5 How to delete a Smart Array Logical Drive

starting from the menu show at Figure 20., move the cursor on "Delete Logical Drive" and press [Enter]. Do not execute this paragraph instructions if you are not sure that the system have to be installed from scratch. The logical drive deletion destroys the entire disk contents. The list of available Logical Drive will be shown:
Figure 28. 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 29. Smart Array Delete window - 2 Press <Esc>+3 (or <F3>) to confirm, then press [Enter] to return to main menu. Alcatel-Lucent 1350OMS 9.6.11 136/176 8DG 42227 MAAA Edition 01 Installation Guide - Volume 1: HPUX System Tips
A.4 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.
A.4.1 Mirror Disk/UX Installation Prerequisite.

The Mirror Disk/UXTM requires the appropriate HP license to authorize the its usage, and the system shutdown due to two reboots.
A.4.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.1.13.3 Disk Mirror Configuration Policy" at page 48.
A.4.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) b) c) Login the system as root and ask all the user to log out the system. Insert the Bootable DVD in the device driver end mount it by entering: ...,sys,root # mount -r /dev/scdvd /SD_CDROM [Enter] To Install the Mirror DIsk/UXTM you have to enter the following command, but be careful because the machine will be automatically rebooted: ...,sys,root # swinstall -s /SD_CDROM/MirrorDisk.sd \* [Enter]
When the system will prompt you for login check in /var/adm/sw/swagent.log for any error met in the software of patch installation.
Appendix B Specific Data

B.1 1350OMS Network Management composition table
Table 10. 1350OMS Network Management composition table
Component / Application CFM CLI CLOG COMMONSVR CPB CPM-EML CPM-GS CPM-NML CSW EML
Version 9.6_UX_D6, P01, P02, P03, P04_B1 9.6.1.0P25 9.6_UX_D6, P01, P02, P03, P04, P05_B1 9.5.0.0 P07 9.6.0.0.13 9.6.0.10 9.6.0.14 9.6.0.1, P01, P02, P03, P04, P05, P06, P07, P08, P09 9.6_UX_D6, P01, P02, P03_B1 9.6.0.0P01, 9.6.0.0P02, 9.6.0.0P03, IRP324, IRP328, IRP332, IRP339, IRP340, IRP342, IRP347, IRP348, IRP355, IRP359, IRP360, IRP364, IRP369, IRP377, IRP384, IRP385, IRP387, IRP388, IRP393, IRP394, IRP397, IRP402, IRP405, IRP410, IRP411, IRP416, IRP419, IRP420, IRP423, IRP428, IRP429, IRP434, IRP435, IRP436, IRP437, IRP439, TEMPLATEDB_9.6.0.0P3+IRP364, xNA_9.6.0.0.2, xNA_9.6.0.0.4, DevBundle_020 9.6.1.0.0, DevBundle_004 9.6.0.0.2 9.6.020 9.5.0.2.15 7.1.4.12 9.5.0.0, RP01, RP02, RP03, RP04, RP05
EOMS ETH-MEDIATOR FTSGUISVR HA INSTALLER IOO
Installation Guide - Volume 1: HPUX Specific Data
Component / Application ISN MAPIM MSGUI MW-INT NBI OLH PKT PNM-GS, (_INT) SDH/NPR SWPDESC SY TOPOGUISVR WDM Platform / Install_Wizard MW_OS SCBackup INSTALL_WIZARD INSTALL_WIZARD_CMD 9.6.0.0.4 3.2.7 9.6.1.1.0 9.6.1.1.0UX
Version 9.1.1.6.1, RP01, RP02, RP03, RP04, RP05, RP06 9.5.0.0P22 9.6.0.35P01 8.2.0.5, P01, P02, P03, P04, P05, P06, P07, P08, P15, P16, P17, P19, P20, P21, P22, P23, P24, P25, P26, P27, P27-RP01 1.0.0.5, 1.6.2.1, 1.6.2.2, 2.0.1.3 9.6.4 9.6.0.0P13, -RP01, -RP02, TEMPLATEDB_9.6.0.0P12+RP1+RP2+RP3+RP4+RP5 6.6-1.8, (6.6.21.18) 9.6_UX_D6, P01, P02, P04, P05, P06, P07-RP01_B1, P07_B1, SDH_TEMPLATEDB_9.6.0.5.P10.RP1.B1 9.6.0.0.09 9.1.1.80, P01, P02, P03, P04, P05 9.5.0.0 P10 9.6.1.0.2, DevBundle_016, TEMPLATEDB_9.6.1.0.2-12Q-DB001
B.2 Alcatel-Lucent DVD Codes

The following provides the Alcatel-Lucent DVD codes of all media provided with 1350OMS 9.6.11 Table 11. Alcatel-Lucent 1350OMS 9.6.11 Media codes DVD Label 1350OMS-MW_OS-Boot-V9.6.0.0.1-UX_IA1 8DG 42207 ABAA 01 1350OMS-MW_OS-Boot-V9.6.0.0.1-UX_PA2 8DG 42234 AAAA 01 1350OMS-MW_OS-PLT-V9.6.0.0.1-UX3 8DG 42209 ABAA 01 1350OMS-MW_OS-PLT-V9.6.0.0.4-UX4 8DG 42209 AEAA 01 No DVD is foreseen. The software is available for download from: - technical Excellance Center: http://tec.ond.alcatel.it - Dedicated FTP site 1. 2. 3. 4. This item is used by ALU technical ordered from Alcatel-Lucent This item is used by ALU technical ordered from Alcatel-Lucent This item is used by ALU technical ordered from Alcatel-Lucent This item is used by ALU technical ordered from Alcatel-Lucent Description hp-uxTM 11iV3 servers installation tool for Itanium Processor. One DVD 1/1. hp-uxTM 11iV3 servers installation tool for PARisc Processor. One DVD 1/1. Software Platform. Three DVD 1/3, 2/3, 3/3 Software Platform. One DVD 1/1 1350OMS Applications.
support in performing the installation; it is not an item support in performing the installation; it is not an item support in performing the installation; it is not an item support in performing the installation; it is not an item
B.3 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 Element Management (EML) or the Network Management (SDH,PKT), the latter one identifies optional functionality separately sold.
B.3.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 for 1350OMS 9.6: MW_INTV9.6 This is the base platform for all the Alcatel-Lucent TNM Applications. No instance is foreseen, but it has to be always installed. 1350OMS-EML V9.6 Instance Definition: Identifier N_ ______ type: Master Size: Small Medium Large 1350OMS-PKT V9.6 Instance Definition: Identifier N_ ______ type: Master Size: Small Medium Large 1350OMS-SDH V9.6 Instance Definition: Identifier N_ ______ type: Master Size: Small Medium Large
B.3.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). 1350OMS-HA require the system predispose before installing them. NMC Name NMS Dependencies.
1350OMS-HAV9.6 EML, PKT, SDH Instance Definition: Identifier N_ ______ type: Master 2 Client 4 Client 8 Client 1350OMS-IOO V9.6
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: GOGlobal-UX PC Client software is available as go_setup executable within /opt/graphon/pc/ directory, to retrieve it you must use a secure connection via SSH, this can be done by installing on you PC a tool that allow such a transfer, we suggest Filezilla where is possible to define a SFTP connection to access server. N.B. Be careful that SSH usage can be forbidden to root user.
When you have retrieved go_setup on you PC install it by follow hereafter procedure: a) b) Double click on the executable The Install Shield Wizard" window will be opened:
Figure 30. GoGlobal-UX Logo 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 146 , otherwise proceed with the next point. c) The next window will be opened showing the welcome message:
Installation Guide - Volume 1: HPUX GoGlobal-UX Installation and Configuration
Click on Next to go on. Wait a few seconds the install procedure. d) The License Agreement" window will be opened:
Click on Yes to go on. e) The Destination Location" window will be opened:
Choose your destination location and click on Next to go on. Wait a few seconds the install procedure. f) The Install Shield Wizard Complete " window will be opened:
Click on Finish to go on. g) 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" configuration, 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) b) Log in as root on the machine. Get the hostname of the current machine: ..,sys,root # uname c) -n [Enter]
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 redundant: http://license.graphon.com/user/redundant_pcode.cgi For single node: http://license.graphon.com/user/
The following window will appear:
Figure 31. 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 32. 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 33. GraphOn Info request window for Single server
Figure 34. GraphOn Info request window for Three Redundant servers N.B. If you have one or more PURCHASED GraphOn LICENSE FOR ALCATEL 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 ALCATEL 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: Hostname and Hostid with the data of each license server. and click on Get License button to continue.
Figure 35. 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 configure 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 promote 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) 2) 3) 4) Store the authorization key in the license file. Configure the license servers machine(s). Start the license server daemons. 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 148) 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:SERVERis a keyword <host> <port> means the hostname or the IP address of the license server 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 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. [Enter]
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 daemon 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) connectivity, 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 64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms 64 bytes from 192.202.21.8: icmp_seq=1. 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.3 at page 82 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) b) c) The remote server is down. The remote server is not reachable because the IP address is wrong. 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> ..,sys,root # /opt/graphon/bin/lmstat -a [Enter] [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: N.B. (Total of 2 licenses available)
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) b)
Buy the GraphOn license(s). 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 authorization key requested for the license servers already see in the paragraph C.3.4.1.1 at page 152. You can see the server lines have the same values in the third field that means the same host ID. # # 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: . . # 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 1BB31C150136 \ user_info="Paolo Rossi\ paolo.rossi@alcatel.it" ISSUER="GrapOn \ Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \ 1996-2002 GraphOn Corporation. All Rights Reserved" ck=45 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]
c)
1)
Move to last line in file and insert the INCREMENT line(s). For example, if you have the authorization key shown at page 152 active on the system, and receive from GraphOn the one shown at page 157, the resulting file will be: # # NOTE: You can change the hostname on the "SERVER" line. # You can also add a port number after the hostid on . . # # ISSUED_DATE=23-jan-2002 # 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\ paolo.rossi@alcatel.it" ISSUER="GrapOn \ Corporation" ISSUED=08-jan-2002 NOTICE="Copyright (C) \ 1996-2002 GraphOn Corporation. All Rights Reserved" ck=45 Save and exit vi file pressing [Esc] and typing :x! and [Enter].
2) 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 Configuration
Poseidon Installation and
D.1 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 PERSONAL.
The package foreseen to manage network floating license, that means you must define one or more system 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" configuration, 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. 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.
D.2 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) b) Log in as root on the machine. Get the hostname of the current machine: ..,sys,root # uname -n [Enter] Get the host identifier of the current machine: ..,sys,root # /opt/poseidon/bin/lmhostid
c)
[Enter]
Then fill-in this one of these forms: Table 12. Three Server Redundant License Form
Installation Guide - Volume 1: HPUX Poseidon Installation and Configuration
Host Name
Host Identifier
Table 13. Single License Form Host Name Host Identifier
D.3 Require the Authorization License

The license can be require via Alcatel-Lucent Intranet Web, by authorized Alcatel-Lucent personal onlyto http://nmfactory.ond.alcatel.it/. 4.6.0.1 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 hosta 839dc26 To: SERVER hosta 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 stop Enter] ...,sys,root # /sbin/init.d/poseidon start [Enter] Don't worry if no daemon is started on the machines that are license client.
D.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 daemon 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) v10.8 hostc: license server UP v10.8 hostd: license server UP v10.8 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 EML_POINT: (Uncounted, node-locked) alcatel hostb /dev/tty (v7.1) (hosta/27000 4406), start Tue 7/20 16:34
D.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 service, 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. Login a Poseidon license server system. 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] 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 INCREMENT" line terminated with back slash ( \ ), that means also the next one have to be considered as part of INCREMENT".
b) c)
d)
e) f)
If you have the three host redundant configuration, copy the license file on other two license servers. Force the license server daemon to reread the license file by entering: ...,sys,root # /sbin/init.d/poseidon reread [Enter] Check again with lmstat" (see paragraph D.4) if the number of point has been increased.
g)
D.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.
D.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 64 bytes from 192.202.21.8: icmp_seq=1. 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.3 at page 82 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) b) c) The remote server is down. The remote server is not reachable because the IP address is wrong. 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 if default gateway is defined and reachable. If you do not know name and IP address of the network default gateway refer to the network administrator.
D.6.2 Two licence servers down

The three redundant license server fails when more than two servers are down or are unreachable, in order to reduce the risk of license failure is suggested to periodically check the license servers entering: ...,sys,root # /opt/poseidon/bin/lmstat -a -c /opt/poseidon/etc/license.dat [Enter]
Appendix E Connection
HP9000
Server
Cable
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 HP9000 RP3410 and RP3440

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
10 11 12 13 14
Figure 36. RP3410 and RP3440 Server Front
Installation Guide - Volume 1: HPUX HP9000 Server Cable Connection
E.2 HP9000 RP4440

The typical configuration foreseen an external disk storage. In the following figures is shown how to connect rp4440 to MSA30 Ultra320 SCSI disk storages.
E.2.1 RP4440 with MSA30

MSA30 Disk System - Front view 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Figure 37. RP4440 Front View without front panel
MSA30 Disk Storage - Rear View
: VHDCI SCSI connector
: VHDCI SCSI cable
Figure 38. RP4440 Rear View
Installation Guide - Volume 1: HPUX HP9000 Server Cable Connection
Appendix F Connection
HP Integrity Server Cable
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.
F.1 HP Integrity RX2660
Figure 39. rx2660 Server Front view
Figure 40. rx2620Server Rear view
Installation Guide - Volume 1: HPUX HP Integrity Server Cable Connection
Figure 41. RX6600 Front Panel
Figure 42. RX6600 Rear Panel
10 11 12 13 14
Figure 43. rx7640 Front view : VHDCI SCSI cable : VHDCI SCSI terminator : VHDCI SCSI connector DAT : HD SCSI terminator : HD SCSI cable 68pin
Figure 44. rx7640 Rear View
ABBREVIATIONS
Not Applicable.
Installation Guide - Volume 1: HPUX Abbreviations
Installation Guide - Volume 1: HPUX Abbreviations
INDEX
Not Applicable.
Installation Guide - Volume 1: HPUX Index
Installation Guide - Volume 1: HPUX Index
CUSTOMER DOCUMENTATION FEEDBACK

The meaning of this section is to collect customer feedback about this handbook. Scope of this activity is the improvement and innovation of customer documentation through the understanding of customer needs. Your comments are welcome. Please send your comment also if you appreciate the handbook. You can send them to your Local Alcatel-Lucent Technical Assistance Center. They will be addressed to the team in charge of the relevant manual. The following form supplies an example only of useful info, as a guide of the type of expected feedback. It is possible fill part of the form, add other data and so on. How to send feedback: copying the example form, filling it and sending it to your Local Alcatel-Lucent Technical Assistance Center. In this case handbook data are already available at the page bottom. using the same form available as a file in the relevant documentation CD-ROM, saving, filling and sending it by e-mail to your Local Alcatel-Lucent Technical Assistance Center. creating a dedicated form on paper or file and sending it to your Local Alcatel-Lucent Technical Assistance Center.
Well take your suggestion in account. We reserve to modify consequently the handbook according to the corretness and congruence of the suggestion and requests.
Installation Guide - Volume 1: HPUX Customer Documentation Feedback
CUSTOMER DOCUMENTATION FEEDBACK Handbook Data Handbook title, release,version: Handbook type: Handbook part number and edition: General Feedback Evaluation SUBJECT 5(max) 4 3 Total evaluation Info quantity Info quality Info structure Consulting facility Layout Chapters Feedback Evaluation HANDBOOK PARTS 5(max) 4 3 PREFACE CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 APPENDICES Your Comments (stricltly necessary when value is less than 3):
1 (min)
1(min)
Suggestion for Improvement Which subject to deepen:
How to deepen:
Subject to eliminate or reduce
Other comments/suggestions
Errors Identified
Reader Info Name: Company: Address: E-mail: Phone:
176
Installation Guide - Volume 1: HPUX Customer Documentation Feedback
8DG 42227 MAAA Edition 01
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: 176 + 6 NOTES: ---
COVER LABELS
(according to Alcatel-Lucent Italy binder format)
1350OMS 9.6.11 Optical Management System Installation Guide - Volume 1: HPUX 8DG 42227 MAAA - Ed. 01
1350OMS 9.6.11
Optical Management System Installation Guide - Volume 1: HPUX - 8DG 42227 MAAA - Ed. 01
1350OMS 9.6.11 Optical Management System Installation Guide - Volume 1: HPUX - 8DG 42227 MAAA - Ed. 01
1350OMS 9.6.11 Optical Management System Installation Guide - Volume 1: HPUX - 8DG 42227 MAAA - Ed. 01
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
HANDBOOK EDITORIAL INFORMATION

Installation Guide - Volume 1: HPUX
Optical Management System Alcatel-Lucent 1350OMS 1350OMS 8DG 42227 MAAA Ed. 01 Unit: Wireline Optics NM Vimercate Author: B. Bosisio - G. Lodi Appraisal: M. Mussini - F. Casasole 9.6.11 Released Change Note: August 2012

1350oms - Ig - 9 6 11hpux

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1350oms - Ig - 9 6 11hpux

Încărcat de

Drepturi de autor:

Formate disponibile

Alcatel-Lucent 1350OMS

Optical Management System

Installation Guide - Volume 1: HPUX

Copyright 2011 Alcatel-Lucent

8DG 42227 MAAA Edition 01 Status: Released

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 1/176

Installation Guide - Volume 1: HPUX List of Contents

Installation Guide - Volume 1: HPUX List of Contents

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 3/176

Alcatel-Lucent 1350OMS 9.6.11 4/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX List of Contents

Installation Guide - Volume 1: HPUX List of Figures

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 5/176

Alcatel-Lucent 1350OMS 9.6.11 6/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX List of Figures

Installation Guide - Volume 1: HPUX List of Tables

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 7/176

Alcatel-Lucent 1350OMS 9.6.11 8/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX List of Tables

Installation Guide - Volume 1: HPUX Preface

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 9/176

Alcatel-Lucent 1350OMS 9.6.11 10/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Preface

Installation Guide - Volume 1: HPUX Preface

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 11/176

REF [1] [2] 1350OMS R9.6 Installation Guide

Part Number 8DG 42227 MAAA 8DG 42227 LAAA

Notes THIS HANDBOOK

1350OMS R9.6 Administration Guide

Table 2. Related Handbooks

Alcatel-Lucent 1350OMS 9.6.11 12/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Preface

Installation Guide - Volume 1: HPUX Preface

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 13/176

General on Customer Documentation

Alcatel-Lucent 1350OMS 9.6.11 14/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Preface

Installation Guide - Volume 1: HPUX Preface

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 15/176

Alcatel-Lucent 1350OMS 9.6.11 16/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Preface

Installation Guide - Volume 1: HPUX Preface

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 17/176

Alcatel-Lucent 1350OMS 9.6.11 18/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Preface

1.1 Installation Requirements

1.1.1 Requested Hardware

Installation Guide - Volume 1: HPUX Introduction

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 19/176

Alcatel-Lucent 1350OMS 9.6.11 20/176 8DG 42227 MAAA Edition 01

Installation Guide - Volume 1: HPUX Introduction

Tx Rx RTS CTS DSR S.G. DCD DTR RI

Rx 2 RTS 7 CTS 8 DSR 6 S.G. 5 DCD 1 DTR 4 RI 9

Refer configuration guide for more info.

Installation Guide - Volume 1: HPUX Introduction

Alcatel-Lucent 1350OMS 9.6.11 8DG 42227 MAAA Edition 01 21/176

1.2 Initial Installation

Instance Creation HP-UX 11iV3 HP-UX 11iV3

NMS2_1_Vx_Master NMS2_2_Vx_Master NMS1_1_Vx_Master NMS2_2_Vx_Client File system NMS2_1_Vx_Client MW_INT, NMS

NMS2_1_Vx_Master NMS2_2_Vx_Master NMS1_1_Vx_Master

Internal data reference

External data reference