1350NM Rel.7.0 Installation Guide

Installation Guide
Alcatel 1350
Management Suite
1350 Rel.7.0
Network Release
3AL 88888 AAAA Ed.02

1350 NR7.0 INSTALLATION GUIDE
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 PRELIMINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.2 NR 7.0 Related Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Registered Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1 OS–Conf Installation Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1.1 Operating system installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1.2 Predispose for NMS installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 OPERATING SYSTEM INSTALLATION EXECUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 Preparatory activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.1 Check HP9000t Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.2 Check the cable connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1.3 Initialize the Virtual Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 Installing HP–UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.1 Installing HP–UX 11i from Bootable Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Virtual Array Command Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.4 Create Depots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5 OS–Conf 7.0.5 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.5.1 OS–Conf 7.0.5 P03 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.5.2 OS–Conf 7.0.5 P04 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.6 Node Name Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.6.1 Network configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.7 Synchronize the Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.7.1 Configure hostb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
02 040824 SC04091401 F.Casasole B.Bosisio

M.Occhietti
01 040511 F.Casasole B.Bosisio
M.Occhietti
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 – ALICE 04.10
1350 NR7.0
Installation Guide
with OS–Conf 7.0.5 P04
ED 02
3AL 88888 AAAA 1 / 190
190
3.7.2 Initial Clock Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4 INSTALLING AND CUSTOMIZING NR7 NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4.1 Before Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4.1.1 Requested Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4.1.2 Requested Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.2 Pre–Installation Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.1 Host declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.2 Authorize Network Loop–back Access for CD installation . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.3 Authorize the Retrieval from Depot Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.3 Install NMS Description and NR7 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.1 Install NR7 Installation Procedure and NMS Description from CD . . . . . . . . . . . . . . . . . . 70
4.3.2 Install NR7 Installation Procedure and NMS Description from Network Depot . . . . . . . 70
4.4 Predispose for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.1 Start the SWP Manager Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.2 Predispose for OS–Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.3 Predispose for 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.4.4 Predispose for NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.4.5 Leave the Script and Execute the predisposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.5 Install and Customize OS–Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.6 Install and Customize 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.6.1 Install 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.6.2 Installing 1353NM Core Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.6.3 Installing 1353NM EMLIM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.6.4 Installing 1353NM EMLUSM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.6.5 Installing 1353NM Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.6.6 Installing 1353SH BKW NR5/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4.6.7 Automatic Post Installation Script Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.8 Customize 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6.9 How to Proceed with More Than One 1353NM Instance . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.6.10 Customize 1353SH BacKWard Compatibility Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.7 Install and Customize a Generic NMS and NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.7.1 Install NMS or NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.8 Customize NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5 FINAL INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

5.1 Final Integration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.2 Alarm Surveillance Federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.1 Identify a Failure Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.2 Failure installing a HP–UXt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.3 Recoverable Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.3.1 Recoverable Faults Installing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.3.2 Recoverable Faults Managing SWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.4 Kerberos Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.4.1 Kerberos kdcd Process Not Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.4.2 Kerberos kdcd High CPU Consuming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.5 Device Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.5.1 Devise Full on /var Mounted File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.5.2 Device full on /usr and /home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1AA 00014 0004 (9007) A4 – ALICE 04.10
6.6 Inittab Process Not restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
APPENDIX A NMS/NMC SPECIFIC DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

A.1 NMS Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
ED 02
3AL 88888 AAAA 2 / 190
190
A.2 NMC Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
A.3 Disk Requirement Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A.4 Alcatel CD Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
APPENDIX B GOGLOBAL–UX INSTALLATION AND CONFIGURATION . . . . . . . . . . . . . . . . . . . . 127

B.1 GoGlobal–UX Installation on HP–UX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

B.2 GoGlobal–UX Installation on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
B.2.1 Automatic Removal of GoGlobal–UX/Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
B.3 GoGlobal–UX license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
B.3.1 License servers definition rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
B.3.2 Retrieve License Servers Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
B.3.3 Permanent License Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
B.3.4 GoGlobal–UX authorization procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
B.3.5 Add a new license(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
APPENDIX C HOW TO CREATE A NETWORK DEPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
APPENDIX D PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

D.1 Configure a Printer Queue within Local Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
D.1.1 Start the System Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
D.2 Configure Printer Booting from Local System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
APPENDIX E BACKUP AND RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

E.1 Full disks backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
E.1.1 Full Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
E.2 Single Volume Group Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
E.2.1 Single Volume Group Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
E.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
E.3.1 Ignite Recovery tape restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
E.3.2 1359HA OS Cluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.3.3 Mirror Disk configuration rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.3.4 Restriction on Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.3.5 Required disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.3.6 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.3.7 Restriction on Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
E.4 FULL BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
E.4.1 Start the “scbackup” script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
E.4.2 Create the IRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
E.4.3 Backup the entire disks contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
E.5 FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
E.5.1 Restore of IRT Tape Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
E.5.2 Restore from Fbackup Tape Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
E.5.3 Restore MIrror Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
E.5.4 Restore Warning and/or Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
APPENDIX F LAN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 3 / 190
190
LIST OF FIGURES AND TABLES
FIGURES

Figure 1. Rear view of server with two disk cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 2. Rear view of server with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 3. Example of K server cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 4. Rear view of server R with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 5. Front view of L Server (without cover panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 6. Rear view of L Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 7. Rear view of N/RP74xx Server with SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 8. RP7400 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 9. RP4440 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 10. RP4440 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 11. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 12. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 13. Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 14. NTP Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 15. Alcatel NMS Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 16. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 17. 1353NM Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 18. 1353NM Customize Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 19. 1353NM Custom Product Selection N.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 20. 1353NM Custom Product Selection N.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 21. 1353NM Custom Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 22. 1353SHBKW 7.0 Custom System Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 23. 1353SHBKW 7.0 Custom Parameters Set–up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 24. 1353SHBKW 7.0 Custom Execution window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 25. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 26. 1354RM Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 27. NMS Customize trace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 28. GoGlobal–UX Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 29. GraphOn License WEB Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 30. GraphOn License WEB Page – Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 31. GraphOn License WEB Page – Software Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 32. GraphOn License WEB Page – License Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 33. GraphOn License WEB Page – License Output Example . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 34. Printer Characteriscs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 35. System Administrator Management Window (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 36. System Administrator Management Window (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 37. Networking and Communications Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 38. Configure LAN Card Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 39. Add Host Name Aliases Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 40. Networking and Communications Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
TABLES
Table 1. List of supported hardware components: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2. OS–Conf 7.0.5 P04 Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 3. Involved IP Network Node table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 4. IP Network Description example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 5. 1353NM Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 6. NR7.0 NMS/NMC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 7. Disk requirements for NMS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
1AA 00014 0004 (9007) A4 – ALICE 04.10
Table 8. Disk Requirements for NMS Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Table 9. Alcatel CD codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 10. Printer Configuration Data Requested. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Table 11. Bus types required for DLT to be recognized as a bootable media . . . . . . . . . . . . . . . . . . . 160
ED 02
3AL 88888 AAAA 4 / 190
190
HISTORY
Edition Date Notes

Ed. 01 May, 2004 First released version of NR7.0 Installation Guide

– Alligned to OS–Conf 7.0 Edition 4
Ed. 02 August, 2004 Included the support for HP Server equipped with
PA8800 processors (OS–Conf 7.0.5 P04)
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 5 / 190
190
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
190
3AL 88888 AAAA
6 / 190
1 PRELIMINARY
1.1 General Information

WARNING
ALCATEL 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. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or spe-
cial, 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.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, repro-
duced or disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N

1350 3AL 88852 AAAA
PRODUCT RELEASE VERSION (N.B.) ANV P/N

1350 7.0 –– 3AL 88851 AAAA
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operator’s Handbooks) are not mod-
ified unless the new software ”version” distributed to Customers implies man–machine interface
changes or in case of slight modifications not affecting the understanding of the explained pro-
cedures.
Moreover, should the screen prints included in the handbook contain the product-release’s ”ver-
sion” marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 7 / 190
190
1.3 Product-release handbooks
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-re-
lease-version is stated in para.1.2 on page 7 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application
THIS
REF HANDBOOK ANV Part No.
HANDBOOK
1350 Rel7.0
[1] 3AL 88888 AAAA
Installation Guide
1.3.2 NR 7.0 Related Handbooks
THIS
REF HANDBOOK ANV Part No. HANDBOOK
or note
1353NM 7.0
[2] 3AL 89061 BAAA
Administration Guide
1354RM 7.0
[3] 3AL 61342 BAAA
1354BM 7.0 ATM

[4] 3AL 23912 BAAAA
1355VPM V3.2
[5] 3AL 72164 BAAA
1359ISN V2.2
[6] 3AL 88230 AAAA
1359IOO 5.0
[7] 3AL 88337 AAAA
1359HA 7.0 OS–Cluster

[8] 3AL 88120 BAAA
Installation & Administration Guide
1AA 00014 0004 (9007) A4 – ALICE 04.10
1359HA 7.0 OS–Resilience

[9] 3AL 88121 BAAA
ED 02
3AL 88888 AAAA 8 / 190
190
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 and HP–UX are trademarks of Hewlett–Packard Corporation.
– HP OpenView and HP OpenView Window are trademarks of Hewlett–Packard.
– ORACLE is a registered trademark of Oracle Corporation.
1.5 Overview
This document describes how to install and configure the HP 9000 computer systems in order to allow the
correct usage of 1350NM 7.0 applications.
1.6 Conventions
The following conventions are used in this manual:
[Enter] A key name is shown between square brackets to indicate that you press a
named key on the keyboard.
courier Courier type is uses to indicate the output produced by the system or data that
you can find.
bold italic Bold italic letters indicate informations that you must enter from the keyboard.
<data> Data shown between angle brackets means that these data depending by the
particular instance of the system. It must be substituted with the correct data.
# Actions must be performed as root.
..,sys,root # Actions must be performed as root.
..,$ Actions must be performed as normal user (not as root).
..,oracle> Actions must be performed as oracle user.
SQL> Actions must be performed in SQL utility.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 9 / 190
190
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
190
3AL 88888 AAAA
10 / 190
2 INTRODUCTION
This document describes how to install HP–UX and the third part software requested by an Alcatel Net-
work Manager Subsystem (NMS) with the Operating System Configuration tool (OS–Conf).
The OS–Conf foresees the incremental approach to the installation. It is possible to distinguish two main
activities: Operating System Installation (OSI) and Software Package Predisposal (SPP).
The OSI allows to install on clean machine the HP–UX 11i operating system with the defined set of
patches, including Mirror Disk/UX and CommandView SDM to be able to manage disk mirror function-
ality and Virtual Array hardware.
SPP allows to predispose a HP–UX system for Alcatel software installation and run, in terms of: kernel
parameter, file system space, and software layer products. The Software Packages (SWP) requirements
must be provided with a description. SPP allows to install the multi–version and multi–instance software
as required by OS–Kernel, to do it the SPP activities foresees to have two different action to predispose
the system for the binary code installation and to create a new instance for an already installed binary code.
OS–Conf allows to predispose the system for installing different version of the same software, and different
data instances for each one of them, but it does not allows duplication on their identities.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 11 / 190
190
2.1 OS–Conf Installation Schema
To better explain the OS–Conf behavior the following schema shows the sequence of actions requested
to install a system from scratched disks. These activities can be divided in two main sections:

– HP–UX Installation including patches, and basic system feature such as Mirror Disk/UX, Com-
mand View SDM, GoGlobal–UX and OS–Conf.
– System predisposal for the NMS installation.
2.1.1 Operating system installation
The HP–UX Operating system installation is an activity executed once, to make the system operational.
A new execution of this activity deletes the entire contents of the hard disk, loosing the previous data and
programs.
To be able to carry out the operation system installation you have to know some information. The following
form can be helpful to prepare this data in advance:
The Hostname must contain only numbers and alphabetic characters in lower case,
starting with an alphabetic character.
Upper case and special characters are FORBIDDEN!
OPERATING SYSTEM BASIC DATA
IP Address:_____._____._____._____ Hostname:____________________________
TimeZone:_______________________
Gateway Address:_____._____._____._____ Subnet Mask:_____._____._____.______
Domain Name System Yes No (Not yet supported with NR7.0)
Domain name:_____________________ DNS Server Address:_____._____._____.______
Search Domain Name(s) 1._________________________ 2.________________________
3._________________________ 4.________________________
5._________________________ 6.________________________
Core Memory Size:________________ Source Device:/dev/dsk/________________
Mirror Disk Option: Yes No Command View SDM: Yes No
System Boot disk: /dev/dsk/___________ Alternate Boot Disk: /dev/dsk/___________
N.B. The items shown in bold are required.
IP Address,Gateway Address, Subnetmask and Hostname must be defined in agreement with the Cus-
tomer TCP/IP addressing plan. Be careful with IP Address and Hostname, because it can be some times
1AA 00014 0004 (9007) A4 – ALICE 04.10
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.
ED 02
3AL 88888 AAAA 12 / 190
190
For Core Memory Size it is intended the amount of RAM equipped on the system, it is automatically de-
tected by the procedure and shown as default choice, you have just to confirm if the shown value is correct.
Mirror Disk/UX and The CommandView SDM are HP software that can be installed on demand. Both
of them are available only for 64bit processor and can be installed only if the Customer had bought the
license.The installation of these software is forbidden on system where there is no evidence of the
related license royalties to HP.
Source Device means the CD–ROM device will be used to retrieve the software. It is automatically de-
tected by the procedure.
The last information requested is related to the disks. The System Boot disk is the hard disk on which HP–
UX will be installed on, the required space is 8 Gbytes(1), and the minimum disk size allowed is 4 Gbytes.
If the Mirror Disk/UX as been requested, the procedure will issue also the request for the altenate boot
disk.
(*) with 512 Mbyte of core memory.
The following list summarizes the actions performed during the operating system installation:
1) Boot from CDROM bootable disk.

2) HP–UX Basic configuration information data entry in the order:
– Time zone of the system via selection menu.
– Hostname
– IP address
– Subnetmask [Optional]
– Gateway [Optional]
– Domain Name [Optional]
– Domain Server Address [Optional]
– DNS Server IP Address [Optional]
– Search Domain Name(s) [Optional]
– Core memory size
– Source device
– Mirror/Disk UX Software installation option
– Command View Software installation option
– System Boot disk selection.
– Alternate Boot disk selection (2)
3) The Boot disk(s) will be initialized.
4) All the file systems and swap areas will be created
5) The Operating System will be installed on the selected boot disk.
6) The optional software will be automatically installed, if any.
7) The Mirror Disk/UX will be configured, if selected.
8) The GoGlobal–UX and OS–Conf software will be installed.
(1) HP–UX 11i required at least eigth giga bytes with a machine with up to one giga byte of RAM, the
operating system can be stored in two four giga bytes disks.
(2)The Alternate Boot disk is asked only when the Mirror/Disk UX has been selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 13 / 190
190
2.1.2 Predispose for NMS installation
Starting with OS–Conf 7.0.5 the predisposal of all software components can be done in one shot. This
means that just calling the “scmanageswp” one time you can predispose many software and related

instances. The procedure does not have to be splitted any more in different steps. In the following the new

procedure schema.
1) Login as “root” user on the system

2) Install the SWP description provided with the application
3) Run the SWP management procedure.
4) Predispose the system for one or more NMS installation
5) Predispose the system for new NMS instance(s).
6) System reboot to configure HP–UX kernel and file systems.
7) Install in the usual way the application software.
8) Customize the NMS data in the usual way.
Each time the system is predisposed for the installation of one or more NMS, that NMS’s
have to be really installed before a new predisposition can be done.
2.2 Restriction
The OS–Conf 7.0 has the following restrictions:
– The minimum hard disk space supported is height Gbyte.
N.B. this configuration is allowed only for machine with up to 512 Mbyte of core memory, for
larger amount of memory the minimum disk requirement is higher.
– The boot disk size has to be larger than double of the core memory size.
– The machine configuration not included in the “List of supported hardware” Table 1. at page 15 are
not guarantee.
– The usage of the Virtual Array LUN for booting is forbidden.
– The usage of hard disk larger than 150 GB is not allowed for booting.
– Only one Virtual Array unit is allowed.
– The usage of dual access disks with mirror disk option is not allowed for booting.
– OS–Conf use /etc/lvmpvg to correcly manage the Mirror Disk/UX configuration and file system ex-
tension. Manual changes of this file are forbibben!
The OS–Conf V7.0.1 and later versions remove the restrictions present for DS2405 double access disks
and automatically manages the Logical Units (LUN) on the Virtual Array Storage VA7110.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 14 / 190
190
3 OPERATING SYSTEM INSTALLATION EXECUTION
This chapter explains how to perform a HP–UX 11i Operating System installation. Within NR7.0 scope
there are two media useful to perfom Operaring System installation. The former is SWP–OSCONF–V7.0.5
P03 (Alcatel Code: 3AL 72881 AAAA 01) useful for any macine except for RP3410, RP3440 and RP4440,
and the latter is SWP–OSCONF–V7.0.5 P04 (Alcatel Code: 3AL 72881 AAAA 02) useful on any server
or 64bit workstation, and madatory on RP3410, RP3440 and RP4440.
3.1 Preparatory activities
Before proceeding in the HP–UX 11i installation it is advisable to prepare all the hardware and software
components for the installation.
– Check the system hardware configuration
– Check the cable connections
– Initialize the Virtual Array
3.1.1 Check HP9000 Hardware Configuration
This paragraph shows the HP hardware where the OS–Conf has been validated. The correct behavior of
the procedure on different hardware is not guarantee.
Table 1. List of supported hardware components:
HP9000 Model Optional Cards
Workstation B2000 B5509BA 100BaseT PCI LAN Adapter

A4974A PCI Single Ended SCSI
C6362A Stand alone DDS–2 4GB native DAT driver
Workstation B2600 B5509BA 100BaseT PCI LAN Adapter

A4974A PCI Single Ended SCSI
C6362A Stand alone DDS–2 4GB native DAT driver
Server R380 – R390 A5220A HP 9000 DVD ROM Device

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

A4107A FWD SCSI–2 Controller
J3516A HSC FF 100BaseX Dual Port LAN Adptr
A3312AZ HA Factory Racked Storage Enclosure
28696A HP–PB FWD SCSI–2 host adapter
Server RP2430 A5230A PCI 100Base–T LAN Adapter

C4314A SMART Desktop DVD–ROM module
C6364A SMART Desktop SE DDS3 DAT module
C5687B HP SureStore DAT40e 40GB Ext UNIX comp
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 15 / 190
190
HP9000 Model Optional Cards
Server L1000 – L2000 A5557A DVD ROM Device for L–Class systems
A5230A PCI 100Base–T LAN Adapter

C5708A DDS 3 Data Cartridge, 24GB/125m
Server RP3410(*) C5687C HP DAT 40 External Tape Drive

A9919A HP server DVD–ROM drive, Slimline
Server RP3440(*) C5687C HP DAT 40 External Tape Drive

A9919A HP server DVD–ROM drive, Slimline
Server RP5430 A5557A DVD ROM Device for HP Svr rp54X0 systems
A5230A PCI 10/100Base–T LAN Adptr for rp24X0

A5557A DVD ROM Device for HP Svr rp54X0 systems
C5687B HP SureStore DAT40e 40GB Ext UNIX comp

A6795A PCI 2GB FIber Channel Adapter
A6250AZ Disk System 2405 Factory Rack
A7295AZ VA 7110 Dual Cntl,512MB Cache Fact Inst
Server N4000 A5838A PCI 2 Port 100Base–T 2 Port Ultra2 SCSI

A5272AZ SureStore E Disk System SC10
C4318SZ SMART Family Full Height Enclosure
Opt. 108 DVD–ROM Drive Factory Racked
C6365A SMART SE DDS–3 DAT Drive, field racked
A4800A PCI FWD SCSI–2 card for HP 9000 Server
C6379A SMART Field Integrated DLT 8000 module
Server RP7400 A5838A PCI 2 Port 100Base–T 2 Port Ultra2 SCSI

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

A5272AZ SureStore E Disk Sys SC10 Factory Rack
C7498A HP DAT 24m Array Module
C7456A HP DLT 80m Array Module
C7499A HP SureStore DVD–ROM Array Module
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 16 / 190
190
Server RP4440(*) A7163A DVD drive (read only) for 4U chassis
A5230A PCI 10/100Base–T LAN Adptr

(*) This servers can be installed only with OS–Conf 7.0.5 P04 Code: 3AL 72881 AAAA 02
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 17 / 190
190
3.1.2 Check the cable connections
This paragraph 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.

3.1.2.1 HP9000 K Class
The K Class server foreseen are: K360, K370 and k380.
To guarantee the higher performance level, the FWSCSI buses located on HSC board have to be used.
In the HAS disk cabinet there are two different buses (BusA and BusB), able to connect 4 disks unit each
one.
We can now focus on the FWSCSI connections for this kind of server:
a) In the first kind of server (with two disk enclosures) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS0. The connector 2 of the BusB is connected to the connector 2 of the BusA.
The connector 1 of the BusA is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusB in the HAS1. The connector 2 of the
BusB is connected to the connector 2 of the BusA. The connector 1 of the BusA is closed with a SCSI
terminator.
HSC
CPU FWSCSI 1 : FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS0
1 1
Bus B Bus A
2 2
HAS1
1 1
Bus B Bus A
2 2
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 1. Rear view of server with two disk cabinets
ED 02
3AL 88888 AAAA 18 / 190
190
b) In the second kind of server (with one disk cabinet) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS, and the connector 2 of the BusB is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusA and the connector 2 of the BusA is
closed with a SCSI terminator.
HSC
CPU FWSCSI 1
: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS
1 1
Bus B Bus A
2 2
Figure 2. Rear view of server with one disk cabinet
c) The last configuration is just an example of K Class server cluster, with three nodes.
: FWSCSI connector : FWSCSI terminator : FWSCSI cable
FWSCSI 1 FWSCSI 1 FWSCSI 1
FWSCSI 2 FWSCSI 2 FWSCSI 2
1 1 1 1 1 1
Bus BBus A Bus BBus A Bus BBus A

2 2 2 2 2 2
1 1
Bus BBus A
2 2
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 3. Example of K server cluster
ED 02
3AL 88888 AAAA 19 / 190
190
3.1.2.2 HP 9000 R Class
This paragraph shows the suggested SCSI connections for the R Class servers.

N.B. For the server R the recommended configuration of the HSC and Lan boards is indicated in

Figure 4. :
The HSC boards should be placed in position 1 and TURBO.
If you have a supplementary Lan board it should be placed in position 3.
CPU
: SCSI cable
FWSCSI 1
: SCSI terminator
FWSCSI 2
: FWSCSI connector
TURBO 3 2 1 0 HSC
HAS
1 1
Bus B Bus A
2 2
Figure 4. Rear view of server R with one disk cabinet

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 20 / 190
190
3.1.2.3 HP9000 L Class and RP5430
The HP9000 server L class and RP5430 are provided without any disk cabinet. These servers have all
the disks inside the CPU cabinet accessible from the front.
In the following schematic picture the location of the disk on the right side of the cabinet, their role in the
mirroring configuration and their hardware path (and device file names) are shown.
Copy disks
/0/0/2/0.0.0 /0/0/2/0.2.0
(c2t0d0) (c2t2d0)
DVD
/0/0/1/0.0.0 /0/0/1/0.2.0
(c1t0d0) (c1t2d0)
Main disks
Figure 5. Front view of L Server (without cover panel)
PCI Slots
Lan RJ45
Connector
Console/UPS Connector (connect the Web console to

the connector labeled CONSOLE)
VHDCI Connector useful for DAT (using cable VHDCI to 50 pin).
Figure 6. Rear view of L Server
If a DLT tape driver is present in this configuration, an extra SCSI adapter will be provided (A4800A). It
has be place in one of the slots: from 7 to 12. Then connect the connect the DLT tape driver via FWSCSI
68 pin cable.
N.B. Install the additional PCI cards starting from the top of PCI Slots.
N.B. Before connect the DLT tape to the SCSI bus check the SCSI ID switch placed on the rear is
set to value 3.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 21 / 190
190
3.1.2.4 HP9000 N Class and RP7400
The HP disk technology innovation trend brought us to introduce new disk storage in the high–end class
server, the supported server/disk storage configuration are:

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

on the bottom controller
I I I I
: VHDCI SCSI terminator O : HD SCSI terminator
5 4 3 2 1 : HD SCSI cable 68pin
: VHDCI SCSI connector O
SC10
A
DAT DVD
12 6
11 The two internal5
PCI Slots 10 disks are place PCI Slots
in this location4
9 3
8 2
7 1
Figure 7. Rear view of N/RP74xx Server with SC10
N.B. The position of the components in the rack is not predictable, so the N4000 server can be placed
on top of SC10.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. It is advisable to install the PCI cards balancing them in the right and left slots, starting from the
bottom.
ED 02
3AL 88888 AAAA 22 / 190
190
3.1.2.4.2 HP9000 RP7400 with DS2405
This paragraph provides the instructions for the configuration of the HP HP9000 RP7400 server config-
ured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in
dual–access mode, that means the disks can be accessed by two ways, the side effect of this
cable connection is that the hard disks are shown twice.
: VHDCI SCSI cable Fiber Channel Connector

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 23 / 190
190
3.1.2.5 HP9000 RP4440
RP4440 are the high end computer equipped with PA8800 processor and require the SWP–64THP610C
bootable edition to be installed. It is expandable up to eight CPU and foreseen up to sixteen GB of RAM.

The typical configuration foreseen an external disk storage with up to eight 36GB hard disks. In the follow-
ing figures is shown how to connect them each other.
DS2405 Disk System – Front view

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Figure 9. RP4440 Front View
Figure 10. RP4440 Rear View

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 24 / 190
190
3.1.2.5.1 HP9000 RP7410 with DS2405
ured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in
: VHDCI SCSI cable Fiber Channel Connector

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 25 / 190
190
3.1.2.5.2 HP9000 RP7410 Cluster with VA7110
ured with the VA7110 external disk cabinet connected via fiber channel swicth.

To implement the disk mirroring on DS2405 Disk Storage, the cabinets have to be connected in
: VHDCI SCSI cable Fiber Channel Connecto

: HD SCSI cable 68pin
: VHDCI SCSI connector
DAT DAT
RP7410 DVD RP7410 DVD
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8 1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
Å Å
DAT
RP7410 DVD
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
Å
Å
FC Switch FC Switch
Virtual Array VA7110

Rear view
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 12. Rear view of RP7410 Server with DS2405
ED 02
3AL 88888 AAAA 26 / 190
190
3.1.3 Initialize the Virtual Array
When a Virtual Array is powered on for the first time it is possible that you have to format disks to be able
to access it.
To proceed with the Virtual Array format you must connect the console terminal to the RS232 port of either
array controller (refer to HP Virtual Array Installation Guide for more information).
As soon as you have connected the console press [Enter] key, and the VA have to replay with the prompt.
The prompt shows the VA status followed by major sign “>”, you have to check if the status value is “ready”,
if it is not, wait up to ten minutes,to allow the start up termination. If after ten minutes the status is still differ-
ent than “ready” , you have to try the “full reset” of the VA by entering:
...> vfpmgr –r full [Enter]
Do not perform the Virtual Array format on a system already operational, the format com-
mand destroys all the data present on the system!
When the reset is completed, check again the VA status, if the status is still “Not Ready” and especially
if the status is “No map” you have to format it by entering the command:
No map> vfpfmt [Enter]
The command will also reset the VA, if also with the format the status do not change to “Ready”, call the
hardware support.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 27 / 190
190
3.2 Installing HP–UX 11i
The HP–UX operating system is the first software installed on a new system, this task is performed by
using the OS–Conf bootable CD.

3.2.1 Installing HP–UX 11i from Bootable Medium
This chapter describes how to manage with the bootable media interface with the different configurations
that it allows.
3.2.1.1 Boot the machine
Power on the HP 9000 system. If your system is active, simply power off and power on it again.
The machine automatically starts up, issuing some messages. 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 CD–ROM device, entering the “search” command:
Main Menu: Enter command or menu > search [Enter]
You have to identify the medium driver that you want to use in the provided device list.
This is an example for workstations:
Path Number Device Path Device Type
P0 SESCSI.2.0 TOSHIBA CD–ROM

P1 FWSCSI.6.0 SEAGATE ST34572WS
P2 FWSCSI.5.0 SEAGATE ST32171W
N.B. For HP9000 B2000 workstation the CD it is usually on IDE.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 28 / 190
190
This is an example for server:
Path Number Device Path Device Path(mnem) Device Type

P0 10/0.6 SESCSI.2.0 Random access media

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

P2 8/16/5.6 Random access media
P3 8/16/5.2 Random access media
P4 8/16/6.0 Lan Module
N.B. In this case, the CD–ROM is connected to SCSI Single Ended Target 2 (8/16/5.2).
You have now in insert the OS–Conf 7.0.5 bootable CD–ROM identified by UX64 in the CD device drive.
If you have to install RP3410, RP3440 or RP4440 server you have to use only SWP–OSCONF–
7.0.5 P04 Alcatel Part number 3AL 72881 AAAA 02.
When the LED of the CD–ROM device stops blinking, boot by entering the “boot” command:
Main Menu: Enter command or menu > boot P<n> [Enter]
where “P<n>“ is the path number corresponding at the CDROM.
The system asks you if you want to perform an interactive boot, reply as shown below:
Interact with IPL (Y, N, Q) > n [Enter]
Booting...
ISL Revision A.00.43 Apr 12, 2000
ISL booting hpux (;0): INSTALL
Boot
...
The system shows you the start of boot with the following message:
_ ALCATEL INSTALLATION PROCEDURE

OS–CONF Technology
1AA 00014 0004 (9007) A4 – ALICE 04.10
__________________________________________________________________________
__________________________________________________________________________
ED 02
3AL 88888 AAAA 29 / 190
190
3.2.1.2 Keyboard selection
The first question issued is related to the keyboard selection, this is relevant only for hp 9000 worksta-
tions, if you are installing a hp 9000 server via console, the procedure will skip it and you have to go to

paragraph 3.2.1.3 “Time ZOne Selection”.

The script explains how to declare the type of keyboard. It asks you if the keyboard that it has been set
is right:
The keyboardmap has been set to PS2_DIN_US_English (QWERTY)

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

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

Please confirm your choice by pressing RETURN or enter a new number :
[Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 30 / 190
190
3.2.1.3 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 ma-
chine will be operative.

In the following an example shows how to set the Middle European Time – Daylight Saving Time (MET–
DST), if you are not in the middle European area you have to choose your timezone:
At the first question you have to enter the number of the seven areas of the world:
__________________________________________________________________________
__________________________________________________________________________
The following procedure enables you to set the time zone.
Select your location from the following list:
1) North America or Hawaii
2) Central America
3) South America
4) Europe
5) Africa
6) Asia
7) Australia, New Zealand
___________________________________________________________________________
Enter the number for your location (1–7) then press [Enter] 4 [Enter]
The items of the next question depends by the area chosen in the previous one, for Europe these will be
the following:
___________________________________________________________________________
Select your time zone from the following list:
1) Greenwich Mean Time – British Summer Time
2) Portuguese Winter Time – Portuguese Summer Time
3) Western European Time – Western European Summer Time
4) Middle European Time – Middle European Summer Time
5) Iceland time
6) Turkey, Finland, Romania, Greece, Bulgaria / Summer Time
7) Western Russia (Moscow) – Western Russia Summer Time
8) Unlisted time zone
9) Previous menu
___________________________________________________________________________
Enter the number for your time zone (1 – 9), then press [Enter] 4 [Enter]
The last time zone selection question is the final confirmation:
___________________________________________________________________________
You have selected:
Middle European Time/Summer Time (MET–1METDST).
___________________________________________________________________________
Is this correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
It the choice is correct enter y [Enter], to confirm your selection an go on with the next section.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 31 / 190
190
3.2.1.4 Time Adjusting
After the time zone definition, it is opportune to review also the machine time and date, for this reason the
program foreseen to issue the following confirmation question:

___________________________________________________________________________
This section enables you to set the system clock.
___________________________________________________________________________
The current system time is Tue Jan 20 10:55:34 MET 2004
Is this correct?
Press [y] for yes or [n] for no, then press [Enter]
If you confirm the time and date, the procedure will proceed with the “Hostname Definition” paragraph
3.2.1.5 at page 33. Otherwise it will ask you to enter the new date and time issuing the following questions:
___________________________________________________________________________
You will be prompted for the date and time.

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

This time will be used to reset the system clock.
Is this value correct?
If you confirm the procedure will go on, otherwise it will go back asking again for the date and time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 32 / 190
190
3.2.1.5 Hostname Definition
This section of the program ask you to enter the mnemonic name of the machine also known as hostname.
Enter the hostname foreseen for machine following the guide line shown in the instruction:
The Hostname must contain only numbers and alphabetic characters in lower case,
starting with an alphabetic character.
Upper case and special characters are FORBIDDEN!
This section enables you to enter Hostname.

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

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

for compatibility with HP–UX ‘uname’.
The current hostname is unknown. You cannot configure networking

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

Is this correct?
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 33 / 190
190
3.2.1.6 IP Address Set–up
The most important information to be able to connect your system to the Local Area Network (LAN) is the
Internet Protocol (IP) address, you must take care of this information because it is not allowed to have two

nodes on the network with the same IP address. The IP address have to be in agreement with the LAN

administration rules.
This section enables you to enter ip_address.

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

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

Is this correct?
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 34 / 190
190
3.2.1.7 SubNetwork Mask and GateWay set–up
This section allows to define the subnetwork mask and the gateway, these two information are fundamen-
tal 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 infor-
mation 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?
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” 3.2.1.9 at page 41, otherwise enter y[Enter]
and proceed with the following:
___________________________________________________________________________
Enter the subnetwork mask and default gateway information.
Example:
Subnetwork mask: 255.255.255.0
Gateway IP address: 192.200.49.1
Current Settings:
–> Subnetwork mask: 255.255.255.0 (default)

Gateway IP address: 192.200.49.1 (default)
___________________________________________________________________________
Enter the new subnetwork mask, [255.255.255.0]:
The default netmask foreseen for the IP address previously assigned to the system, press [Enter] if it is
the right one, or enter a new one followed by [Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 35 / 190
190
The procedure will update the window contents (Current Setting) with new value and it will prompt you for
the gateway address:
___________________________________________________________________________


Example:

Current Settings:

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

Current Settings:

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

___________________________________________________________________________
ED 02
3AL 88888 AAAA 36 / 190
190
3.2.1.8 Domain Name System (DNS)
Do not configure DNS, it is not supported by NR7.0.

This section allows to configure the Domain Name System for HP–UX. You can configure the DNS only
on customer specific request, he has to provide you all the information shown hereafter:
a) Domain Name System server IP address.
b) Domain Name.
c) Up to six other domain names for searching.
When the DNS server is not reachable hp–ux can loose time trying to connect the server each
time it is opening a new connection.
___________________________________________________________________________
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
___________________________________________________________________________
If you have the DNS server enter “y” followed by [Enter], otherwise enter “n” [Enter] and skip the remaining
part of this paragraph and go to “Core Memory and Swap/Dump Sizing” 3.2.1.9 at page 41.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 37 / 190
190
3.2.1.8.1 DNS Server and Domain Name
If you choose to define the DNS server the procedure will ask you to enter the Domain Name and the DNS
Server address; both of them have to be provided by the customer. An example of a Domain Name and

DNS server address is provided.

___________________________________________________________________________
Enter the domain name and DNS name server information.
Example:
Domain name: lab.alcatel.com

DNS server address: 192.200.49.1
Current Settings:
–> Domain name: (not set)

DNS server address: (not set)
___________________________________________________________________________
Enter the domain name, then press [Enter]:
Enter the Domain Name in dot notation form followed by [Enter]. The Domain Name in conjunction with
hostname will be used to identify this node in Internet and/or Intranet networks.
The entered name will be shown close at “Current Setting:” “Domain name:” , and the procedure will ask
you for the DNS Server address:
___________________________________________________________________________
Example:

Current Settings:
Domain name: alcatel.it

–> DNS server address: (not set)
___________________________________________________________________________
Enter the DNS server address, then press [Enter]
Enter the DNS Server IP address followed by [Enter], then it will be shown close at “Current Setting:” “DNS
Server address” to ask you to confirm your choice.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 38 / 190
190
__________________________________________________________________________


Example:

Current Settings:
Domain name: alcatel.it

___________________________________________________________________________
Are the parameters above correct?
If the data entered are correct, reply “y[Eenter]” and proceed, otherwise enter “n[Enter]” and repeat. Be-
fore proceeding, the installation procedure will check if the provided IP address is reachable. If the DNS
server is reachable the DNS will be configured immediately, and a message like this will be shown:
..... Waiting, ping system 192.200.49.244

__________________________________________________________________________
Note: DNS has been successfully configured on your system.

___________________________________________________________________________
If the IP address is not reachable, the message will be:
..... Waiting, ping system 192.200.49.244

__________________________________________________________________________
___________________________________________________________________________
Unable to contact DNS Server at 192.200.49.244.

The DNS system may be down or there may be a network disruction.
Verify that the address 192.200.49.244 is correct.
__________________________________________________________________________
___________________________________________________________________________
Is the DNS IP address correct?
Double check the DNS server IP address, if it is correct enter “y[Enter]” to proceed, otherwise enter “n[En-
ter]” to go back to the DNS server and Doamin Name data entry.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 39 / 190
190
3.2.1.8.2 Search Domain Name(s)
The Search Domain Name(s) allows to search for a node in more than one Domain. Of course the Search
Domain Name(s) have to be entered in agreement with the customer naming rules.

___________________________________________________________________________
Additional DNS Parameters: Search Domain Name(s) List
This section enables you to configure list of Domain Name searched

when you query a host name in DNS, search order is equal to next
input sequence.
___________________________________________________________________________
If you do not have any Domain Name other than the Local Domain (already entered defining the DNS Ser-
ver), you have to enter “n[Enter]” and skip to the next paragraph.
Entring “y[Enter]” the installation procedure will issie the request for the second Domain Name for the list
and so on, until you do not enter an empty Domain Name to interrupt the data entry.
Enter the search Domain Name then press [Enter], to end just press [Enter]
Second Domain Name: alcatel.ft [Enter]
Third Domain Name: alcatel.nl [Enter]
Fourth Domain Name:[Enter]
___________________________________________________________________________
Note: DNS has been successfully configured on your system.
___________________________________________________________________________
Press [Enter] to continue...

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 40 / 190
190
3.2.1.9 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 OS–Conf 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 Core Memory.

___________________________________________________________________________
___________________________________________________________________________
The primary ”SWAP/DUMP” size will be computed as the double of Core Memory
size. The Core Memory size is: 512 Mbyte
Just pressing [Enter] will keep this memory size

___________________________________________________________________________
Enter Core Memory size in Mbyte [512]:
Press [Enter] to confirm.
3.2.1.10 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 = 6

Total CDRoms found = 1
Then the procedure will ask you to confirm the source media as the CD–ROM drive.
This section enables you to enter default Source media (CdRom).

___________________________________________________________________________
CdRom Selection
___________________________________________________________________________
Device MByte Hardware Path Usage Type VolGroup

___________________________________________________________________________
c3t2d0 594 0/0/2/1.2.0

___________________________________________________________________________
Please enter the Device Name of source media [c3t2d0]:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 41 / 190
190
3.2.1.11 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. 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 ?
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/UX software without license is not allowed
WARNING
To be able to install and configure mirror software the following
requirements must be matched:
– You MUST have evidence of HP Disk Mirror/UX software license
customer ownership
– The hardware configuration MUST have a spare hard disk for each
one in use
Are both requirements satisfied ?
If you have the required items just replay with y[Enter].
Choosing the Disk Mirror/UX installation the procedure automatically configures the mirror feature on any
Volume Group you’ll create in the system by using the feature of OS–Conf. To perform this activity the
installation will take 30 minutes more and the machine will be rebooted twice.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 42 / 190
190
3.2.1.12 Virtual Array Software Selection
The Alcatel NM application will supportn with OS–Cluster environment the virtual array disk storage
VA7100 or VA7110, these hardwares require a specific management software that can be installed auto-
matically by answering y [Enter] to the following question:

N.B. The installation of the virtual array disk storage software is not allowed if the hardware
is not present!
_This section enables you to select Virtual Array Manager Software.

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

hardware configuration ?
3.2.1.13 Disk Selection
The configuration criteria has been defined, 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.
3.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 in the following format:
This section enables you to select the boot disk device.

___________________________________________________________________________
Disks Selection
___________________________________________________________________________

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

c2t2d0 8672 0/0/2/0.2.0 _(free)_ ______ ________
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
Enter the disk device that will be used as boot device then press [Enter].
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. A ”D” character is shown before the device name in the “Device” column to advice the disk is
accessible via two different disk controllers. This configuration is typically used with Fiber Chan-
nel device.
ED 02
3AL 88888 AAAA 43 / 190
190
3.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 con-

nected to the same SCSI bus of the Main Boot Disk, this choice allows the system to survive also to a SCSI

bus failure. It is also advisable to choose a disk with the same size.
This section enables you to select the alternate boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

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

c2t2d0 8672 0/0/2/0.2.0 _(free)_ ______ ________
D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________
___________________________________________________________________________
Select Alternate BOOT Disk device Name :
If the size difference between the main and alternate boot disk is bigger then one Gbyte the procedure
will issue a warning message, and it will ask you to confirm your choice.
WARNING: Difference between Primary & Alternate Boot disk size is too big
difference is:”1024 MegaByte”, please check your selection Is this correct?
Replay y[Enter] to confirm, or n[Enter] to change your choice.
3.2.1.13.3 Multiple Disk Request
To install minimum HP–UX configuration on a machine with 512 Mbyte, 8 Gbyte of hard disk are required.
If you provide 4 Gbyte or smaller hard disks, the procedure will prompt you again until the requested
amount of disk space will be reached.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 44 / 190
190
3.2.1.13.4 Disk Selection Confirmation
When all the disk selection will be completed, the program will ask you to confirm your choice.
After this confirm question the contents of the selected disk will be lost.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________

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

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 45 / 190
190
3.2.1.14 Execution Phase
The procedure is now entering the execution phase, it will be performed unattended.
This phase takes 45 minutes on a HP9000 L1000 server, with Fast/Wide differential hard disks. If you had

chosen the disk mirroring option the procedure will reboot two times and will take 35 minutes more.

In the following the activities performed:
– To create the physical volume on the main boot disk.
– To set the primary boot path.
– To create the physical volume on the alternate boot disk (only for mirror disk configuration).
– To set the alternate boot path (only for mirror disk configuration).
– To create the Logical Volumes.
– To create a new file system into the Logical Volume
– To restore the HP–UX dumps.
– To update the configuration files
– To reboot the system to activate the HP–UX installed on the hard disks.
– To install the Mirror/Disk UX and related patches (only for mirror disk configuration).
– To configure the mirror for all the Logical Volumes (only for mirror disk configuration).
– To install the Virtual Array Management software (only on demand).
– To install OS–Conf configuration procedure.
3.2.1.14.1 CD Request During Execution
During the execution phase the following message will be issued on console:
PLEASE INSERT CD–ROM : SWP–OSCONF–V7.0.* Vol 1/*
When the it appear, you have to remove the CD currently present in the driver, and insert the one with label
“SWP–OSCONF–V7.0.5 Volume 1/4. The execution restart automatically.
3.2.1.15 Login Message During the Execution
Whoever is logging the system during the executing will be alert the installation is in progress by the follow-
ing 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.
3.2.1.16 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
***************************************************************************
1AA 00014 0004 (9007) A4 – ALICE 04.10
The procedure it is not able to recover the error by itself, look at the log file to have more information about
the error.
ED 02
3AL 88888 AAAA 46 / 190
190
3.3 Virtual Array Command Authorization
Starting with CommandView SDM version A.01.07.00, to prevent unauthorized access to the Virtual Array
configuration, an Array Security Database (ASD) has been introduced. This means that starting from
OS–Conf 7.0.5 to be able to configure the VA7110 it is mandatory to create an array security ac-
count. In fact the ASD is provided with a default user already defined, that allows to perform the first con-
nection to ASD to define your own user, and it will be automatically deleted at first user definition.
Do not forget the Array Security Database user and password, otherwise no more confi-
guration via SAM will be possible.
This is the procedure to set up the user account:
a) Login as superuser “root”
b) Start ASD administration tool:

...,sys,root # secadmin –host <hostname>[Enter]
Where <hostname> is the name of the local host. For 1359HA–OS Cluster configuration it is recom-
mended to enter the physical hostname.
c) Secadmin will prompt you asking for username, you have to replay with: Administrator
N.B. Be careful the username and password are case sensitive.
d) Then it will ask you for password, enter: administrator
e) secadmin will prompt you with: <secadmin on <hostname> >: . At this prompt you have to enter
the user definition commad:
<secadmin on ... >: add –user <username> –group Administrator –host <hostname> [Enter]
Where:
<username> means the user you whant to create.
<hostname> is the same hostmane entered staring “secadmin”.
f) secadmin will prompt you to enter the password twice without echo of input by issuing the following
two prompts:
password:
re–enter password:
N.B. Do not leave the password empty, an emply password does not allow the correct login to
CommandView Java interface.
g) Check the just defined user entering the command: list
h) Exit the secadmin tool entering exit.
Example:
...,sys,root# secadmin –host ipb083
username: Administrator
password:
<secadmin on ipb083>:add –user root –group administrator –host ipb083
password:
re–enter password:
<secadmin on ipb083>:list
1AA 00014 0004 (9007) A4 – ALICE 04.10
Username Group Host

––––––––––––––––––––––––––––––
root Administrator ipb083
<secadmin on ipb083>:exit
ED 02
3AL 88888 AAAA 47 / 190
190
3.4 Create Depots
The installation can be executed retrieving the software from a local CD or from a network depot. In case
you choose to install from depot you have to define a system with enough disk space available, where up

to two depots can be created, one for the third party software, that we will call “OS_Conf Depot”; where

you can store all the software layer distributed by OS_Conf itself, and one for the Alcatel TNM software,
that we will call “Alcatel NMS Depot”.
To setup the depot you need 2.2 Gbyte for OS_Conf Depot, while the size of Alcatel TNM depends by the
different NMS you plan to install.
The following paragraphs provide the instructions to create the depots.
3.4.1 Create “OS_Conf Depot”
OS–Conf Depot can be useful when you have to instal more then one system, because it allows to execute
simultaneously and unattended installations. The detailed procedure to create the OS_Conf Depot, is de-
scribes by Appendix C “How to create a Network Depot” at page 143.
3.4.1.1 Create “Alcatel NMS Depot”
This paragraph shows how to create the depot for Alcatel software. The depot size depends by the soft-
ware you have to store on the disk, the Table 7. column “Depot Package Size” at page 125 summarizes
the space required in M bytes.
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 /alcatel to allow the storage of Alcatel software by entering the command:
...,sys,root # scextendfs /alcatel/DEPOT <required disk size> [Enter]
2) Change the default directory on the depot one:

...,sys,root # cd /alcatel/DEPOT [Enter]
3) For each distribution CD Rom that contains the software you have to install:
a) Insert the CD into the driver.

b) Mount the CD at /SD_CDROM directory:
...,sys,root # mount –r /dev/dsk/<cdrom device file> /SD_CDROM[Enter[
c) Copy the entire CD contents to /alcatel/DEPOT directory by entering the command:
...,sys,root # cp –p /SD_CDROM/* /alcatel/DEPOT [Enter]
d) Dismount the CD:
...,sys,root # umount /SD_CDROM[Enter]
e) Remove the CD from the device.
4) Add SWP description to /alcatel/DEPOT:

...,sys,root # swcopy –s /alcatel/DEPOT/SWPDESCV205.sdpkg \* @ /alcatel/DEPOT [En-
ter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 48 / 190
190
3.5 OS–Conf 7.0.5 Patch Installation
The patch applicability depends by the OS–Conf edition you have, it you have SWP–OSCONF–V7.0.5
3AL 72881 AAAA 01 refer to paragraph 3.5.1 at page 49 , otherwise with SWP–OSCONF–V7.0.5 3AL
72881 AAAA 02 refer to paragraph 3.5.2 at page 52.
3.5.1 OS–Conf 7.0.5 P03 Patch Installation
In the following you find the procedure to install the OS–Conf 7.0.5 P03 patch, provided on the CD with
label SWP–OSCONF–V7.0.5 Volume ADD1.
OS–Conf upgrade does not require the system shutdown, but it requires the removal of the previous ver-
sion.
3.5.1.1 Patch Installation from CD
This paragraph shows how to install OS–Conf 7.0.5 P03 from CD,
a) Login as root.
b) Insert SWP–OSCONF–V7.0.5 Volume ADD1 (Iteration2) CD into the driver.
c) Mount the CD at /SD_CDROM directory:

...,sys,root # mount –r /dev/dsk/<cdrom device file> /SD_CDROM [Enter[
d) Remove the OS–Conf 7.0.5 by entering the command:

...,sys,root # swremove OS–CONF [Enter]
e) Install the new OS–Conf 7.0.5 package:

...,sys,root # swinstall –s /SD_CDROM OS–CONF,r=7.0.5.P03 [Enter]
f) Dismount the CD Rom by enter the command, then remove it:

...,sys,root # umount /SD_CDROM [Enter]
g) Proceed with the “OS–Conf 7.0.5 P03 Platform Upgrade” paragraph 3.5.2.2 at page 53.
3.5.1.2 Patch Installation from Depot
This paragraph shows how to install CO–Conf 7.0.5 P03 from a depot machine previously created by exe-
cuting the instructions provided by Appendix C “How to create a Network Depot” at page 143.
a) Login as root.
b) Remove the OS–Conf 7.0.5 by entering the command:

c) Install the new OS–Conf 7.0.5 package:

...,sys,root # swinstall –s <depot IP address>:/alcatel/SCDEPOT OS–CONF,r=7.0.5.P03
[Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 49 / 190
190
3.5.1.3 OS–Conf 7.0.5 P03 Platform Upgrade
OS–Conf 7.0.5 P03 includes some two hp–ux patches, this patches have to be installed by executing
a specific script. If the script is executed in a fresh installed system, it requires just a little disk space in /var

file system (les then three mega bytes), but if you have to install it on an already predisposed system, refer

the patch delivery notes for more information.
Hereafter the procedure to perform the upgrade:
1) Logging the system as “root”.
2) Set the defalt directory as “/”, by entering the command:

...,sys,root # cd /[Enter]
3) Start the OS–Conf 7.0.5 P03 upgrade procedure by entering:

...,sys,root # /SCINSTALL/etc/scupgrade[Enter]
4) The script will issue the following menu, replay with “1[Enter]” to perform the installation from
CD, or “2[Enter]” to choose the depot.
OS–Conf 7.0.5 P03 Upgrade Procedure
––––––––––––––– LAYERED PRODUCTS Repository –––––––––––––
1 – CDROM
2 – DEPOT
Insert choice and press [Enter]:
3.5.1.3.1 OS–Conf 7.0.5 P03 Upgrade from CD
If you choose the installation from CD, the procedure will ask you to confirm the source device by issuing
the following message:
Enter ’q’ to Quit or the CD device [def=<CD Rom device>]:
The default provided is the driver used to install the hp–ux, if it is the right one just press [Enter] key to
confirm, otherwise enter another CD Rom driver reference file.
The next message issue shows you the current disk space available on /opt and /var file systems, if you
are installing from scratch, just reply “y[Enter]” to proceed:
Is the disks free space complying with these patch delivery notes?
Filesystem bytes used avail %used Mounted on
/dev/vg00/lvol5 1540096 614128 868122 41% /opt
/dev/vg00/lvol8 491520 133077 336084 28% /var
Do you confirm the upgrade request?
The procedure will start issuing the following output:
Executing Upgrade starting on Thu Apr 15 08:54:20 METDST 2004

Alcatel Installation : Processing GoGlobal–UX 2.1.1_646
Alcatel Installation : Processing T1457AA 1.4.2.02.00
Alcatel Installation : Upgrade Patches to OS–Conf 7.0.5.P03
1AA 00014 0004 (9007) A4 – ALICE 04.10
Alcatel Installation : END: Upgrade OS–Conf NR7.0.x to NR7.0.5

Executing Upgrade complete on Thu Apr 15 08:55:03 METDST 2004
Then “scupgrade” teminates, it is advisable to check in “/SCINSTALL/scinstall.log” for any error.
ED 02
3AL 88888 AAAA 50 / 190
190
3.5.1.3.2 OS–Conf 7.0.5 P03 Upgrade from DEPOT
If you choose to install from depot, enter “2[Enter]”, and the procedure will ask you to specify the depot
location by issuing the message:
––– Depot selection for LAYERED Products installation ––––
Enter ’q’ to Quit or the Depot absolute path name:
You have to enter the depot location with one of the following two notations:
For local depot: /alcatel/SCDEPOT
For remote depot: <depot hostname or IP address>:/alcatel/SCDEPOT
are installing from scratch, just reply “y[Enter]” to proceed:
/dev/vg00/lvol5 1540096 614128 868122 41% /opt
/dev/vg00/lvol8 491520 133077 336084 28% /var

3.5.1.4 OS–CONF Manual Workaround
Meningfull for installing 1354BMATM and 1355VPN
In order to prevent error predisposing the system for 1354BM ATM and 1355VPN the following line have
to be added at the end of file /SCINSTALL/SCINSTALL.lib :
alias swinstall=”swinstall –x allow_multiple_versions=true –x allow_downdate=true ”

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 51 / 190
190
3.5.2 OS–Conf 7.0.5 P04 Patch Installation
In the following you find the procedure to install the OS–Conf 7.0.5 P04 patch, provided on the CD with
label SWP–OSCONF–V7.0.5 Volume ADD1 (Code: 3AL 72881 AAAA 02).

The followig table show the amount of disk space requested to perform the patch installation.
OS–CONF Version Disk Space Installaed Software
V7.0.5 fresh installed None Install patches to align to OS–Conf

7.0.5 P04
V7.0.5 already predisposed /opt 50 MBytes Upgrade GoGlobal UX & install

without 1354BM ETH patches to align to OS–Conf 7.0.5
P04
V7.0.5 already predisposed /opt 266 MBytes Upgrade GoGlobal UX & install TAO
with 1354BM ETH 1.3.1.3 and patches to align to OS–
Conf 7.0.5 P04
Table 2. OS–Conf 7.0.5 P04 Disk Space Requirements.
3.5.2.1 Patch 04 Installation from CD
This paragraph shows how to install OS–Conf 7.0.5 P04 from CD,
a) Login as root.
b) Insert SWP–OSCONF–V7.0.5 Volume ADD1 (Code: 3AL 72881 AAAA 02) CD into the driver.

...,sys,root # mount –r /dev/dsk/<cdrom device file> /SD_CDROM [Enter[
d) Remove the OS–Conf 7.0.5 by entering the command:

e) Install the new OS–Conf 7.0.5 package:

...,sys,root # swinstall –s /SD_CDROM OS–CONF,r=7.0.5.P04 [Enter]
f) Dismount the CD Rom by enter the command, then remove it:

...,sys,root # umount /SD_CDROM [Enter]
g) Proceed with the “OS–Conf 7.0.5 P04 Platform Upgrade” paragraph 3.5.2.2 at page 53.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 52 / 190
190
3.5.2.1.1 Patch 04 Installation from Depot
This paragraph shows how to install CO–Conf 7.0.5 P04 from a depot machine previously created by exe-
cuting the instructions provided by Appendix C “How to create a Network Depot” at page 143.
a) Login as root.
b) Remove the OS–Conf 7.0.5 by entering the command:

c) Install the new OS–Conf 7.0.5 package:

...,sys,root # swinstall –s <depot IP address>:/alcatel/SCDEPOT OS–CONF,r=7.0.5.P04
[Enter]
3.5.2.2 OS–Conf 7.0.5 P04 Platform Upgrade
OS–Conf 7.0.5 P04 includes the OS–Conf 7.0.5 P03 one, some two hp–ux patches, this patches have
to be installed by executing a specific script. If the script is executed in a fresh installed system, it requires
just a little disk space in /var file system (les then three mega bytes), but if you have to install it on an already
predisposed system, refer the patch delivery notes for more information.
Hereafter the procedure to perform the upgrade:
1) Logging the system as “root”.
2) Set the defalt directory as “/”, by entering the command:

...,sys,root # cd /[Enter]
3) Start the OS–Conf 7.0.5 P03 upgrade procedure by entering:

...,sys,root # /SCINSTALL/etc/scupgrade[Enter]
4) The script will issue the following menu, replay with “1[Enter]” to perform the installation from
CD, or “2[Enter]” to choose the depot.
OS–Conf 7.0.5 P04 Upgrade Procedure
––––––––––––––– LAYERED PRODUCTS Repository –––––––––––––

1 – CDROM
2 – DEPOT

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 53 / 190
190
3.5.2.2.1 OS–Conf 7.0.5 P04 Upgrade from CD
If you choose the installation from CD, the procedure will ask you to confirm the source device by issuing
the following message:

Enter ’q’ to Quit or the CD device [def=<CD Rom device>]:

The default provided is the driver used to install the hp–ux, if it is the right one just press [Enter] key to
confirm, otherwise enter another CD Rom driver reference file.
are installing from scratch, just reply “y[Enter]” to proceed, othervise check the available space with values
shown at Table 2. . If there is enoth free space enter “y[Enter]” if not extend the file system with “scex-
tendfs” command, reboot and start again the upgrade script.
/dev/vg00/lvol5 1540096 614128 868122 41% /opt
/dev/vg00/lvol8 491520 133077 336084 28% /var
The procedure will start issuing messagese like the following:


1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 54 / 190
190
3.5.2.2.2 OS–Conf 7.0.5 P04 Upgrade from DEPOT
If you choose to install from depot, enter “2[Enter]”, and the procedure will ask you to specify the depot
location by issuing the message:
––– Depot selection for LAYERED Products installation ––––
Enter ’q’ to Quit or the Depot absolute path name:
You have to enter the depot location with one of the following two notations:
For local depot: /alcatel/SCDEPOT
For remote depot: <depot hostname or IP address>:/alcatel/SCDEPOT
are installing from scratch, just reply “y[Enter]” to proceed, othervise check the available space with values
shown at Table 2. . If there is enoth free space enter “y[Enter]” if not extend the file system with “scex-
tendfs” command, reboot and start again the upgrade script.
/dev/vg00/lvol5 1540096 614128 868122 41% /opt
/dev/vg00/lvol8 491520 133077 336084 28% /var


1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 55 / 190
190
3.6 Node Name Management
Before proceeding in the installation and customization it is necessary to declare all the IP network nodes
involved. The involved nodes means all the IP are defined in the following table:

Type Description
Alcatel TNM system Any HP 9000 server and/or workstation with Alcatel TNM on board, that have
to communicate with the machine you are installing.
Printers Any network printer that have to be used by the machine you are installing.
Virtual IP Address Only for 1359HA OS–Cluster: the virtual IP address of the packages.
Time synchonization Any Time synchonization equipment reachabe via IP network.

systems
Table 3. Involved IP Network Node table
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.
3.6.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 1354RM Client
– hostb 1353NM Master
– hostc 1354RM Client
– hostd 1354RM Master
– hostd 1353SH Master
There are other network equipments, such as rooters, printers (local and network), personal computer,
and time synchronization equipments. You have to identify the equipmet specified by Table 3. at page 56,
in the example:
– gpsrec1 Time syncrhonization system via Global Position System.
– lp1 Network line printer.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 56 / 190
190
gpsrec1 (GPS time receiver)
lp1 (network printer)
IP 192.202.21.51
192.202.22.6
WAN WAN
hosta hostc
IP 192.200.49.1 hostb IP 192.202.21.8 hostd hoste
IP 192.202.21.7 IP 192.202.22.4 IP 192.202.22.5
Figure 13. Network Example
In this example all the machines work togheter; 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 syncrhinization system (gpsrec1) has to be used by the entire network manage-
ment 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.
hosta hostb hostc hostd hoste
192.200.49.1 hosta Present To insert To insert To insert To insert
192.202.21.7 hostb To insert Present To insert To insert To insert
192.202.21.8 hostc To insert To insert Present To insert To insert
192.202.22.4 hostd To insert To insert To insert Present To insert
192.202.22.5 hoste To insert To insert To insert To insert Present
192.202.21.51 gpsrec1 To insert To insert To insert To insert To insert
192.202.22.6 lp1 To insert To insert
Table 4. IP Network Description example.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 57 / 190
190
3.7 Synchronize the Clocks
The clock synchronization is mandatory for system working together with Kerberos authentica-
tion tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305 has to be configured by follow-

ing the instructions shown in this paragraph.

If NTP is not configured you have to check the time difference among all the systems and
guarantee that it doesn’t exceed five minutes.
Before proceeding with the NTP configuration you must have a clear picture of the configuration among
the involved machines, it is advisable to prepare a ”time distribution plan” taking into account the following
rules:
a) The primary time sources have to be reliable ones, such as a Global Position System (GPS) receiver
time source.
b) Define two or three time–server machines. Each time–server should be a peer with of the other time–
servers.
c) If possible, do not synchronize multiple time–servers to the same outside source.
d) If you choose to use an hp server as time source, it must be configured to be synchronized with
its internal clock.
For example in a network with two GPS receivers and five nodes, with the following roles:
– host and hosted configured with: 1353NM and 1354RM co–hosted with 1359HA OS–Resilience.
– 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 58 / 190
190
GPS
GPS Receiver 1 GPS Receiver 2

IP 192.202.21.51 IP 192.202.22.20
WAN WAN
hosta hostc
IP 192.200.49.1 hostb IP 192.202.21.8 hostd hoste
IP 192.202.21.7 IP 192.202.22.4 IP 192.202.22.5
Figure 14. NTP Configuration Example
To obtain such a configuration the three servers host, host and hosted have to declare the two GSP Receiv-
ers as NTP servers, moreover they can declare the other ones as peers; the resulting configuration will
be:
host
server gpsrec1 prefer
server gpsrec2
peer hostc
peer hostd
hostc
server gpsrec2
peer hostb
peer hostd
hostd
server gpsrec1
peer hostb
peer hostc
The “prefer” attribute distinguishes as the preferred source, this source it is usually the most reliable and
also the nearest one.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 59 / 190
190
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, loggin the system as root user and enter: scxntp [Enter]
========================================================================
OS–Conf xntp Protocol Configuration
========================================================================
1 – Add new NTP server
2 – Add new NTP peer
3 – Remove NTP server
4 – Remove NTP peer
5 – Configure NTP on local clock
6 – Show NTP configuration
7 – Show NTP status
8 – Start/Stop NTP server
9 – Align the time to server
e or q – for exit
To simplify the explanation, the procedure shows how to configure the server hostb and hosta of
Figure 14. at page 59. Note, the configuration order is relevant for the system behavior, it is better to start
configuring the nodes more close to the Timeservers.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 60 / 190
190
3.7.1 Configure hostb
This is the procedure using scxntp script to configure the hostb of Figure 14. at page 59.
a) Login hostb as root user.

b) Start the scxntp script by entering: scxntp [Enter]
c) 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 ...
d) Define the secondary timeserver:

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

NOTE: Updating /etc/ntp.conf adding peer 192.202.21.8 ...
f) Check the NTP configuration:

NTP configuration
server 192.202.21.51 version 3 prefer

server 192.202.22.20 version 3
peer 192.202.21.8 version 3
peer 192.202.22.4 version 3
g) Start the NTP Daemon, set–up the daemon automatic start at system startup, and synchronize the
hostb clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automati-
cally
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
1AA 00014 0004 (9007) A4 – ALICE 04.10
Would you like to start it (y/n) ?y
ED 02
3AL 88888 AAAA 61 / 190
190
NOTE: Temporary setup xntpd autostart...
NOTE: Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 off-
set –0.026898 sec

xntpd NOTE: Reset the setup xntpd autostart...

h) Leave script by entering “e” or “q”.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 62 / 190
190
3.7.1.1 Configure hosta
This is the procedure using scxntp script to configure the hosta of Figure 14. at page 59.
a) Login hosta as root user.

b) Start the scxntp script by entering: scxntp [Enter]
c) Define the preferred timeserver:

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

e) Check the NTP configuration:

NTP configuration
server 192.202.21.7 version 3 prefer

f) Start the NTP Daemon, set–up the daemon automatic start at system startup, and synchronize the
hosta clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automati-
cally
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 off-
set –0.026898 sec
xntpd NOTE: Reset the setup xntpd autostart...
1AA 00014 0004 (9007) A4 – ALICE 04.10
g) Leave script by entering “e” or “q”.
ED 02
3AL 88888 AAAA 63 / 190
190
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.
3.7.2 Initial Clock Alignment
When a machine is installed for the first time, the clock is not synchronized with any reference, the easiest
way to synchronize it with the other is by running “scxntp” script selecting the option N.9 “Align the time
to server”.
N.B. The time alignment is forbidden when NTP daemon is running.
To align the time you have to login the system as root user and start the script “scxntp” by entering:
...,sys,root# scxntp[Enter]
========================================================================
OS–Conf xntp Protocol Configuration
========================================================================
1 – Add new NTP server
2 – Add new NTP peer
3 – Remove NTP server
4 – Remove NTP peer
5 – Configure NTP on local clock
6 – Show NTP configuration
7 – Show NTP status
8 – Start/Stop NTP server
9 – Align the time to server
e or q – for exit
At the prompt enter “9[Enter]”
Enter server hostname or IP address or q for Quit :
The procedure will ask you to enter the IP address or Hostname of the timeserver, enter it and press [Enter]
key. The time will be aligned and shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 64 / 190
190
4 INSTALLING AND CUSTOMIZING NR7 NMS
This chapter describes the actions required to install and customize OS–Kernel and Alcatel Network Ma-
nagement Subsystem.
4.1 Before Starting
Before starting with the installation, it is advisable to have a clear picture of the software architecture; it
is also advisable to prepare a schema of the system you are going to install. This allows you to prepare
a list of materials and data that will be required during the installation.
The Alcatel network management system application architectures are generally provided with two func-
tionalities:
a) Master function
b) Client function
The Master function provides the set of software programs that allows the machine to perform the network
management, and the Client function to provide the man–machine interface. The two functionalities can
be installed on the same system or on a different one. Where system navigation is foreseen, it is mandatory
to install the NMS Client on the system that has to perform the navigation. Just to clarify the concept look
at the following example: considering system with three machines, the first is installed with both 1354RM
Master and 1353NM clients, where two 1353NM instances have been created with the same identifier of
the two 1353NM master located on the other two systems. In this case it is possible to have 1353NM func-
tionalities at 1354RM level (Navigation).
1353NM Master
1353NM
Client 1354RM
1353NM Instan. 2 Master+
Client Client 1353NM
Instan. 3 Instan.1 Master+
Client
Instan.2
OS–Kernel
OS–Kernel
1354RM Master with two 1353NM Clients
1353NM Master
1353NM
Master+
Client
Instan.3
OS–Kernel
Figure 15. Alcatel NMS Architecture.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Moreover some other software can be installed as component, they are qualified as NMC.
ED 02
3AL 88888 AAAA 65 / 190
190
4.1.1 Requested Data
To be able to complete the installation you have to know in advance the answer to the following questions:

a) Which is/are the NMS you want to install ?

b) Which is/are the NMS versions ?
c) How many instances are foreseen ?
d) Which is/are the instance identifiers ?
e) Which is the size and role of the instances ?
f) Is there any NMC to be installed?
g) Is it foreseen the 1359HA OS–Cluster protection?
Fill in the lists of NMS and NMC in APPENDIX A at page 123 where all the foreseen items are shown.
4.1.2 Requested Hardware
The supporter HP9000 hardware configuration is specified in the paragraph 3.1.1 “Check HP9000
Hardware Configuration” at page 15. To completely define the HP9000 server or workstation configura-
tion you have to compute the amount of disk space requested by the Alcatel NMS you plan to install.
Then add the items shown in the following paragraphs.
4.1.2.1 Requested Network Equipments
The installation of a HP–UX can not be carried on without connecting the server or workstation to a Local
Area Network (LAN), because of this the minimum equipment required are:
1) Two BT LAN cables.
2) Two Local Area Network plug or a stand alone Ethernet Hub.
The installation can not be performed if the LAN card it is not connected to the LAN plug or a
stand alone Ethernet Hub.
4.1.2.2 Requested PC
The installation of Alcatel TMN systems can be carried out only with a Graphical User Interface (GUI), be-
cause of this to be able to install on a HP9000 Servers you must have a MS Windows personal comput-
er where you have to install GoGlobal–UX software (see the appendix B at page 127 for more information).
4.1.2.3 Required Go–Global UX License
Go–Global UX needs a permanent or temporary license to be able to run (see paragraph “Go–Global UX
License” B.3 at page 131 for more information).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 66 / 190
190
4.1.2.4 Requested Hard Disks
The hard disk requirements within NR7.0 are strictly related to the NMS you are installing, and the size
of the instances of them.
Another specific behavior of OS–Conf is related to the primary SWAP/DUMP management, in fact the de-
fault 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–UX installation depends by the machine core memory
size, and can be summarize in the following:
8 G byte for machine with up to 1 G bytes of core memory
18 G byte for machine with of core memory up size between 1 and 4 G bytes
36 G bytes for machine with of core memory up size between 5 and 8 G bytes
To compute the required space total amount use the following formulas:
For single volume systems:

<Unix>+<Software>+<Data>=<amount of disk space>
For multiple volume systems, there are two formulas: one for computing the amount of space required on
system volume group (vg00), and another one for the data:
System volume formula:
<Unix>+(<Software>+<Not protected Data>)*115/100=<amount of disk space>
Data volume formula:
<Data>*115/100=<amount of disk space>
N.B. The system can not share the same physical hardware, that means to implement a
multiple volume system you need al least one hard disk drive for each data volume.
Where:
<Unix> Means the amount of disk space requested by HP–UX operating system, it
can be assumed as up to 6 Gbyte for programs (HP and 3PP), where you have
to add the disk space devoted to store swap and crash areas. The amount of
swap space can be computed as the higher value between the RAM size multi-
plied per two and the sum of swap size required by each NMS you have to instal
and NMS–Instance you have to create, refer to Table 7. (page 125) and
Table 8. (page 125) for the NMS swap requirements. The size of crash area
within /var/adm/crash directory, it corresponds to half of core memory size.
<Software> Means the amount of requested disk space for storing the software. Its value
can be computed by summing the code size defined by each NMS you have to
install, refer to Table 7. (page 125).
NOTE: OS–Kernel has to be always installed.
<Data> Means the amount of requested for data storage. If you are computing the value
for a single volume system, you sum the data size defined by each NMS–
instance you have to create, refer to Table 8. (page 125).
For the multiple volume group each NMS instance defines the data size for the
volume group.
1AA 00014 0004 (9007) A4 – ALICE 04.10
<Non protected Data> Means the amount of requested for data storage defined not protected by
1359HA OS–Cluster. For this kind of data there is no difference in management
between single or multiple volume system, you sum the data size defined by
each NMS–instance you have to install.
ED 02
3AL 88888 AAAA 67 / 190
190
N.B. Independently by the results of the computation the minimum disk requirement are specified
at the beginning of this paragraph.
Example: To install a 1354RM 7.0 with one Master Large instance and 1353NM 7.0 with two Presentation

instances on a HP9000 server equipped with 3Gbyte RAM.

Single volume:
The size of primary swap/dump area will be 3*2*1024 Mbyte=6144 Mbyte, the amount of requested
swap will be: (500+7500)+(500+2*300) Mbyte=9100 Mbyte, so 9100 Mbyte is the higher value, and
it will be used. So the total a mount of operating system you have to add: 6114 Mbyte for HP and
3PP software, 9100 Mbyte for swap areas, and 1536 Mbyte for crash area. The result will be: 16780
The you have to add: 1800 Mbyte for OS–Kernel, 3600 Mbyte for 1353NM , 1000 Mbyte for 1354RM
to compute the disk space amount for Alcatel Software. Total 6400 Mbyte.
The last the value for the data instances: 8000 Mbyte for 1354RM, 2*100 Mbyte for 1353NM. Total
8200 Mbyte.
16870+(6400+8200)115/100=33660
You need 4x9Gbyte or 2x18Gbyte or 1x36Gbyte. Moreover, if you want to use this system as depot
machine, you have also to add other disks.
Multi Volume:
The difference with the previous is only related to the 1354RM data instance, that will be place in a
different volume group. So the system volume group will need:
16870+(6400+200)115/100=24460
Data volume group:
8000*115/100=9200
For the multiple volume group configuration you need 3x9Gbyte or 2x18Gbyte or 1x36Gbyte for sy-
stem volume group, and one 9Gbyte or 18Gbyte or 36 Gbyte for the data.
N.B. IF YOU CONFIGURE THE MIRROR DISK/UX FEATURE, YOU MUST PROVIDE THE
DOUBLE OF THE HARD DISK SIZE COMPUTED.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 68 / 190
190
4.2 Pre–Installation Actions
Hereafter there are some actions that have to be done before installing.
4.2.1 Host declaration
The network node description have to be filled in manually, for each host you have to communicate to, you
must add a line with the IP Address followed by the host name in the /etc/hosts file (see “Node Name Mana-
gement” paragraph 3.6 at page 56).
4.2.2 Authorize Network Loop–back Access for CD installation
Even if the installation is performed locally there are some activities that need the network access to per-
form their tasks, this is the reason why to be able to install from CD it is necessary to add a line in the /.rhost
file (creating it when it doesn’t t exist) with the local host name followed by “root” keyword.
4.2.3 Authorize the Retrieval from Depot Machine
This paragraph explains how to authorize the file retrieval from the depot machine, if you do not use any
depot machine skip it.
To be able to retrieve the Alcatel software packages from the depot machine, the access to these files have
to be granted to all the root users of all the machines that have to be installed. This can be obtained by
writing in the /.rhosts file the hostname and the keyword “root” for each machine, and add a line for each
of them in the /etc/hosts file.
Example: you have to install the following three systems: hosta, hostb and hostc (the depot machine itself).
You have to write /.rhosts this way:
hosta root
hostb root
hostc root
N.B. All the host included in .rhosts file have to be defined in /etc/hosts one.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 69 / 190
190
4.3 Install NMS Description and NR7 Installation Procedure
Before starting with the NMS predispose action, you have to install the NR7 Installation Procedure and
NMS description. This can be done from CD or from network depot. The following paragraphs show how

to perform the activity from both sources.

4.3.1 Install NR7 Installation Procedure and NMS Description from CD
To install NR7 installation procedure from CD you have to execute the following procedure:
a) Login the system as root user.
b) Insert the “SWP–OS_KERNEL–V7.0” CD in the CD drive.

...,sys,root # mount –r /dev/dsk/<cdrom device file> /SD_CDROM[Enter]
d) Retrieve and install NR7 installation procedure:

...,sys,root # tar xvf /SD_CDROM/Install_NR7–R7.0.9.tar [Enter]
e) Dismount the CD:

...,sys,root # umount /SD_CDROM[Enter[
f) Insert the “SWP–NRV7.0_ADD01” CD in the CD drive.
g) Mount the CD at /SD_CDROM directory:

h) Retrieve and install NR7 installation procedure:

...,sys,root # tar xvf /SD_CDROM/Install_NR7–R7.0.11.tar [Enter]
i) Install the NMS description by entering the command:

...,sys,root # swinstall –s /SD_CDROM/SWPDESCV205.sdpkg \* [Enter]
j) Dismount the CD:

...,sys,root # umount /SD_CDROM[Enter]
4.3.2 Install NR7 Installation Procedure and NMS Description from Network Depot
To install NR7 installation procedure from network depot you have to execute the following procedure:
a) Login the system as root user.
b) Retrieve and install NR7 installation procedure:

...,sys,root # remsh <depot Host> \ [Enter]
dd if=/alcatel/DEPOT/Install_NR7–R7.0.9.tar | tar xvf – [Enter]
c) Retrieve and install NR7 installation procedure:

...,sys,root # remsh <depot Host> \ [Enter]
dd if=/alcatel/DEPOT/Install_NR7–R7.0.11.tar | tar xvf – [Enter]
d) Install the NMS description by entering the command:

...,sys,root # swinstall –s <depot Host>:/alcatel/DEPOT SWPDESC,r=2.0.5 [Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. If the remote shell (remsh) fails with error: remshd: Login incorrect. check the
depot machine access authorization (see paragraph 4.2.3 at page 69)
ED 02
3AL 88888 AAAA 70 / 190
190
4.4 Predispose for Installation
The OS–Kernel modular approach allows to predispose the machine after the hp–ux Operating System
installation, this is performed on demand by a specific script. In this paragraph will be shown: how to predis-
pose the system to be able to run OS–Kernel, because it has to be always installed. Then it will provided
an example of 1353NM, and a generic example for all the other NMS.
4.4.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 ac-
tion. This means you have to predispose all the NMS and NMS instances in one shot. This
allows to save time and to do not meet problems in disk space computation. If you have
to interrupt the predisposal in the middle of the selection, exit the procedure choosing
“Exit” to abort the procedure itself.
The following menu‘ will be shown on the screen:
–––––––––––––––– SWP MAIN MENU ––––––––––––––––
1 – Predispose new SWP

2 – View predisposed SWP
3 – Remove SWP
4 – Create new SWP INSTANCE
5 – View created SWP INSTANCES
6 – Remove SWP INSTANCES
7 – Install 3PP Optional software
a – Apply
e – Exit
Select option 1 in order to predispose for a new SWP installation. First of all you have to predispose for
the OS_Kernel.
4.4.2 Predispose for OS–Kernel
First of all you have to predispose the system for OS–Kernel, in fact it has always to be installed as first.
The script proposes the capability to retrieve new SWP description files, enter: 3 [Enter] to keep the de-
scription installed at paragraph 4.3 at page 70.
–––––––––––––––––– Predispose new SWP ––––––––––––––––––

1 – Predispose from CDROM
2 – Predispose from Depot
3 – Predispose from Descriptors installed on System
q – Quit
1AA 00014 0004 (9007) A4 – ALICE 04.10
Insert choice and press [Enter]: 3 [Enter]
ED 02
3AL 88888 AAAA 71 / 190
190
Then the SWP description defined on system will be shown.
Predispose new SWP

Item SWP Name SWP Version

–––– ––––––––––––––– –––––––––––

1 1353NM 7.0
2 1353NM 7.1
3 1353SH 7.0
4 1353SH 7.1
5 1354BM_ATM 7.0
6 1354BM_ATM 7.1
7 1354BM_ETH 7.0
8 1354BM_ETH 7.1
9 1354RM 7.0
10 1354RM 7.1
11 1354SY 7.0
12 1354SY 7.1
13 1355VPN 3.2
14 1355VPN 4.0
15 1359HA_OSCLS 7.0
16 1359HA_OSCLS 7.1
17 1359HA_OSRES 7.0
Press [Enter] to show other items ...
Press [Enter] to see the remaining items.
18 1359HA_OSRES 7.1
19 OS_KERNEL 7.0
20 OS_KERNEL 7.1
Enter ’q’ to Quit, ’d’ to Display again or the Item Number: 19[Enter]
Enter the OS_Kernel 7.0 item (19 in the example) to select it for the predisposition. The procedure will ask
you to confirm the choice.
Selected SWP ’OS_KERNEL 7.0’
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 ...

Analysing Product Alcatel–OVDL
Analysing Product Apache20
.
.
.
Analysing Product unzip
Analysing Product xloadimage
TRANSLATOR procedure was successful.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Press [Enter] to continue.
The OS–Kernel is now stored for the predisposal that will be done leaving the script.
ED 02
3AL 88888 AAAA 72 / 190
190
4.4.3 Predispose for 1353NM
This section describes the 1353NM predisposal, it is provided to better clarify the procedure behavior, but
you have to execute it only if you need the 1353NM functionality, otherwise go to next paragraph “Pre-
dispose for NMS” 4.4.4 at page 79.

1353NM subsystems is organized in two components: the software code and instance. You have to predis-
pose the software code once, but you can create one or more instances. Because of this there are two
different actions, where the second can be iterated more than once.
IF YOUR INSTALLATION PLAN INCLUDES 1353SH BACKWARD COMPATIBILITY TOOL,

YOU HAVE TO INCLUDE 1353SH 7.0 ITEM IN THE PREDISPOSE ACTIVITY, DEFINING AN
INSTANCE FOR EACH 1353SH 5 or 1353SH 6 THAT HAVE TO BE MANAGED.
4.4.3.1 Predispose for 1353NM Software
Proceeding in the script execution, after the OS–Kernel predisposal the script prompt you again for choos-
ing the next software package, you have in any case to install something of 1353NM, so enter: 1[Enter]
to select the 1353NM 7.0.
Predispose new SWP

–––– ––––––––––––––– –––––––––––
1 1353NM 7.0
2 1353NM 7.1
3 1353SH 7.0
4 1353SH 7.1
5 1354BMATM 7.0
6 1354BMATM 7.1
7 1354BMETH 7.0
8 1354BMETH 7.1
9 1354RM 7.0
10 1354RM 7.1
11 1354SY 7.0
12 1354SY 7.1
13 1355VPN 3.2
14 1355VPN 4.0
15 1359HA_OSCLS 7.0
16 1359HA_OSCLS 7.1
17 1359HA_OSRES 7.0
18 1359HA_OSRES 7.1
19 OS_KERNEL 7.1
Enter ’q’ to Quit, ’d’ to Display again or the Item Number : 1[Enter]
The selected product is shown to check the right choice:

1AA 00014 0004 (9007) A4 – ALICE 04.10
Selected SWP ’1353NM 7.0’
ED 02
3AL 88888 AAAA 73 / 190
190
After the confirm action the procedure analyzes the description showing all the software layers required:

Analysing Product Alcatel–OVDL

.

.
.
Analysing Product xloadimage
Press [Enter] to proceed, then, exit to the Software predisposal by entering “q[Enter]” twice to came back
to the “SWP MAIN MENU” and be able to create the instance:
Predispose new SWP

–––– ––––––––––––––– –––––––––––
1 1353NM 7.1
2 1353SH 7.0
3 1353SH 7.1
4 1354BMATM 7.0
5 1354BMATM 7.1
6 1354BMETH 7.0
7 1354BMETH 7.1
8 1354RM 7.0
9 1354RM 7.1
10 1354SY 7.0
11 1354SY 7.1
12 1355VPN 3.2
13 1355VPN 4.0
14 1359HA_OSCLS 7.0
15 1359HA_OSCLS 7.1
16 1359HA_OSRES 7.0
17 1359HA_OSRES 7.1
18 OS_KERNEL 7.1
Enter ’q’ to Quit, ’d’ to Display again or the Item Number : q[Enter]
The script will go back to the previous menu level:

q – Quit
1AA 00014 0004 (9007) A4 – ALICE 04.10
Insert choice and press [Enter]: q[Enter]

Enter “q” again to go to the initial menu level.
ED 02
3AL 88888 AAAA 74 / 190
190
4.4.3.2 Predispose for 1353NM Instance
The 1353NM Instance define the behavior of the application, you have three possibilities:
1) Predispose for a 1353NM Information Manager (IM), if you want to install a 1353NM stand alone
or 1354RM cohosted system.
2) Predispose for a 1353NM Spare IM, if you are installing the spare system in a 1359HA OS–Clus-
ter environment.
3) Predispose for a 1353NM Client, if you just want to have the 1353NM Presentation function on
1354RM subsystem. In this case you have to create an instance for each 1353NM IM and the
Instance Identification number must be the same of the referred IM.
Here after the sequence of actions you have to perform to carry out the job.
At “SWP MAIN MENU” prompt you have to enter “4[Enter]” to get in the “Create new SWP INSTANCE”:
–––––––––––––––– SWP MAIN MENU ––––––––––––––––

5 – View created SWP INSTANCE
a – Apply
e – Exit
The already predisposed NMS will be shown in a list, enter the item of 1353NM (alias 1353SH):
Create new INSTANCE
Item SWP Name SWP Version Session

–––– ––––––––––––––– ––––––––––– –––––––
1 1353NM 7.0 YES
Enter ’q’ to Quit, ’d’ to Display again or the Item Number : 1 [Enter]
The list of the 1353NM possible instances foreseen for the specific machine model is provided.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 75 / 190
190
For the 64 bit processor machine the list will be:
List of available INSTANCE dimension for SWP: 1353NM 7.0

Item INSTANCE Dimension INSTANCE Description

––– –––––––––––––––––––– ––––––––––––––––––––––––––––––––––––––––––––––

1 1353NM_IM_Test 1353NM Master (IM) System Small Configuration
2 1353NM_IM_Small 1353NM Master (IM) System Small Configuration
3 1353NM_IM_Medium 1353NM Master (IM) System Medium Configuration
4 1353NM_IM_Large 1353NM Master (IM) System Large Configuration
5 1353NM_US 1353NM Client (US)
6 1353NM_IM_S_CLSSpare 1353NM Master (IM) Small System for OS–Cluster
7 1353NM_IM_M_CLSSpare 1353NM Master (IM) Medium System for OS–Clu...
8 1353NM_IM_L_CLSSpare 1353NM Master (IM) Large System for OS–Cluster
Enter ’q’ to Quit, ’d’ to Display again or the Item Number :
For the 32 bit ones, it will be:

––– –––––––––––––––––––– –––––––––––––––––––––––––––––––––––––––––––
1 1353NM_US 1353NM Client (US)
Before entering the instance item number for the selection, read carefully the meaningful of each item in
the following table:
Instance type item Description
1353NM_IM_Test Test instance, not useful for field deployment
1353NM_IM_Small Entry level configuration
1353NM_IM_Medium Middle range configuration
1353NM_IM_Large High end configuration
1353NM_US Client User Interface
1353NM_IM_S_CLSSpare Entry level configuration for Spare system within 1359HA OS–Cluster
1353NM_IM_M_CLSSpare Middle range configuration for Spare system within 1359HA OS–Cluster
1353NM_IM_L_CLSSpare High end configuration for Spare system within 1359HA OS–Cluster
Table 5. 1353NM Instances
N.B. The 1353NM_US instance is not defined for 1359HA OS–Cluster protection
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 76 / 190
190
The typical configurations are:
– 1353NM Information Manager – System is completely devoted to 1353NM function.

– 1353NM Presentation – System is completely devoted to 1353NM man–machine

interface.
– 1354RM Information Manager – The system performs the 1354RM function. The 1353NM
software can be installed to allow the 1354RM to communicate
and control the 1353NM. For each controlled 1353NM IM
system a related 1353NM Client (US) instance has
to be created. This 1353NM Client must be configured
with the same instance number identifier (ID) of the
controlled 1353NM IM.
– 1353NM/1354RM CoHosted – The 1353NM Information manager and 1354RM one on the
same machine.
– 1354BM Information Manager – The system performs the 1354BM function. The 1353NM
software can be installed to allow the 1354BM to
communicate and control the 1353NM.
For each controlled 1353NM IM system a related 1353NM
Client (US) instance has to be created. This 1353NM Client
must be configured with the same instance number
identifier (ID) of the controlled 1353NM IM.
Enter the instance item number followed by [Enter] to make your choice.
For each instance the procedure asks for two information: the instance number identifier and the multiple
volume group. The instance number identifier assigned to a 1353NM IM instance has to be unique for ev-
ery 1354RM/BM domain, the best is unique on the whole network.
Insert the Instance Number for ’1353NM_IM_Small’:
The multiple volume group option is mandatory for the 1359HA OS–Cluster protected instances. You can
also choose to use the multiple volume group configuration without the 1359HA OS–Cluster, but you have
to devote specific hard disks for each new instance of data.
Do you like a Multi–Volume group configuration ? (y/n)
After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:
Selected INSTANCE:
Dimension 1353NM_IM_Small
Number 3
Multi–Volume NO

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 77 / 190
190
Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the re-
quired software:

NOTE: the volume group defined in the file /alcatel/Conf/

SWP/1353NM/7.0/descriptor.cfg will not take in account, because
multi_volume_group option is not set.
Volume group vg00 will be used.
Analysing Product DBD–MySQL
Analysing Product DBI–1.32
Analysing Product MySQL
The procedure shows again the list of possible instance for the next choice, if you need to create another
instance repeat the procedure shown in this paragraph, otherwise enter “q[Enter]” twice as shown hereaf-
ter and proceed with the other NMS predisposal if it is the case.

–––– –––––––––––––––––––– –––––––––––––––––––––––––––––––––––––––––––
........
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]”
to go back to the previous menu level.
Create new INSTANCE

–––– ––––––––––––––– ––––––––––– –––––––
1 1353NM 7.0 YES
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 78 / 190
190
4.4.4 Predispose for NMS
Any other NMS predisposal has a similar behavior, the only differences are related to the possible
instances available. This activity has to be performed only if you plan to have any other functionality on
the machine you are installing.

NMS has the same organization of 1353NM, software code and data areas; hereafter the predisposal
script behavior is shown.
4.4.4.1 Predispose for NMS Software
In both cases, if you have to start “scmanageswp” or proceeding from the 1353NM predisposal, you have
the “SWP MAIN MENU” on the screen, enter: 1[Enter] to get on the next menu:
–––––––––––––––– SWP MAIN MENU ––––––––––––––––

a – Apply
e – Exit
The script proposes the capability to retrieve new SWP description files, enter: 3 [Enter] to skip it.

q – Quit
Then the SWP description defined on system will be shown.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 79 / 190
190
Select a NMS of NR7.0 you want to predispose among: 1353SH 7.0, 1354RM 7.0, 1355VPN
3.2,1359HA_OSCLS 7.0 and 1359HA_OSRES 7.0. Enter the item number shown in the first column of
the menu, then press [Enter] :

N.B. The item belonging to NR7.0 are shown in bold, do not choose the other ones.

Predispose new SWP

–––– ––––––––––––––– –––––––––––
1 1353NM 7.1
2 1353SH 7.0
3 1353SH 7.1
4 1354BMATM 7.0
5 1354BMATM 7.1
6 1354BMETH 7.0
7 1354BMETH 7.1
8 1354RM 7.0
9 1354RM 7.1
10 1354SY 7.0
11 1354SY 7.1
12 1355VPN 3.2
13 1355VPN 4.0
14 1359HA_OSCLS 7.0
15 1359HA_OSCLS 7.1
16 1359HA_OSRES 7.0
17 1359HA_OSRES 7.1
18 OS_KERNEL 7.1
Then it asks you to confirm your choice, by showing you the selected NMS, enter “y[Enter]” if it is correct:
Selected SWP ’1354RM 7.0’
Please confirm your selection ? (y/n) y[Enter]
The procedure start the description analysis issuing the following messages:

.
The output depends by the chosen NMS
.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 80 / 190
190
Press [Enter] to proceed, then, exit from the Software predisposal by entering “q[Enter]” twice to come
back to the “SWP MAIN MENU” and be able to create the instance:
Predispose new SWP


–––– ––––––––––––––– –––––––––––
.
.
Choose any other NMS you have to predispose, or enter “q[Enter]” to complete the NMS software selec-
tion. When you enter “q[Enter]” the procedure will show you the previous menu level.

q – Quit
Insert choice and press [Enter]: q[Enter]
Enter “q[Enter]” again to go to the SWP MAIN MENU.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 81 / 190
190
4.4.4.2 Create NMS Instance
This paragraph shows how to create a NMS instance for the specific data storage.

N.B. Check on NMS delivery notes if the NMS supports multiple instances.

To start the instance creation enter “4 [Enter]”:
–––––––––––––––– SWP MAIN MENU ––––––––––––––––

a – Apply
e – Exit
The installed software list is shown, you have to choose the item related to the NMS you has predisposed
in the previous step (2 in the example):
Create new INSTANCE

–––– ––––––––––––––– ––––––––––– –––––––
1 1353NM 7.0 YES
2 <NMS name> <NMS version> YES
Select the item corresponding to the instance you want to create, enter it followed by [Enter]. The list of
allowed instances for that NMS will be shown.
The procedure will ask you for two information: the instance number identifier and the multiple volume
group. The instance number identifier to be assigned has to be unique for that NMS in the whole network,
if you are creating a NMS Client the instance number has to be the same of the related master.
Enter the instance number followed by [Enter] to proceed:
Insert the Instance Number for ’<NMS Instance Type>’:
The multiple volume group option is mandatory for the OS–Cluster protected instances. You can also
choose to use the multiple volume group configuration without the 1359HA OS–Cluster, but you have to
devote specific hard disks for each one.
Do you like a Multi–Volume group configuration ? (y/n)

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 82 / 190
190
After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:
Selected INSTANCE:
Dimension <NMS Instance Type>

Number <NMS Instance Identifier>
Multi–Volume NO
Confirm or refute the selection. If you confirm the procedure will predispose for the installation of the even-
tual required software:

.
.
The procedure shows again the list of possible instance for the next choice, enter “q[Enter]” to go back
to the previous menu level.
List of available INSTANCE dimension for SWP: 1354RM 7.0
–––– –––––––––––––––––––– –––––––––––––––––––––––––––––––––––––––––––––

....
Enter “q[Enter]” again to go back to SWP MAIN MENU.
Create new INSTANCE

–––– ––––––––––––––– ––––––––––– –––––––
1 1353NM 7.0 YES
2 <NMS name> <NMS version> YES

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 83 / 190
190
4.4.5 Leave the Script and Execute the predisposal
To speed–up the predisposal execution and reduce the disk fragmentation, the predisposal is executed
when leaving the script. To execute the predisposal for all the software you have to exit the “SWP MAIN

MENU” by entering “a[Enter]”:

–––––––––––––––– SWP MAIN MENU ––––––––––––––––

5 – View create SWP INSTANCES
a – Apply
e – Exit
Insert choice and press [Enter]: a [Enter]
All the item requested will be shown (example of a 1353NM and 1354RM cohosted), confirm your choice
by entering “a[Enter]” (as apply) or cancel:
Items SELECTED for the CONFIGURATION
Item Type SWP Name SWP Version INSTANCE Number INSTANCE Dimen.. Opt
––––––––– –––––––––––– ––––––––––– ––––––––––––––– ––––––––––––––––––––
SWP OS_KERNEL 7.0
SWP 1353NM 7.0
INSTANCE 1353NM 7.0 2 1353NM_IM_Small
SWP 1354RM 7.0
INSTANCE 1354RM 7.0 4 1354RM_IM_Small
Enter ’a’ to Apply, ’c’ to Cancel or ’d’ to Display again: a [Enter]
Then procedure start executing the requested predispositions.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 84 / 190
190
4.4.5.1 Disk Configuration
The first activity is related to the hard disk configuration, during this activity 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 re-
quested at least one hard disk is requested for each instance of software.
The procedure shows its execution trace:
DISKS configuration activated ...

____________________________________________________________________
Analize Mount Point:”/alcatel/7.0”

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

....
Press [Enter] to continue....
When a new disk is requested, the procedure issues a menu with all the disks present in the configuration,
marking the unused disk with the label “(free)” in the “Usage” column.
N.B. If you are implementing the disk mirroring, to reach the highest availability level, it is advisable
to choose a disk not connected to the same SCSI bus of the Main Boot Disk, this choice allow
the system to survive also to a SCSI bus failure.
N.B. If you are implementing the disk mirroring, it is advisable to keep the two disk chains balanced.
If them are unbalanced the useful disk space amount is the minimum size of them.
If you are installing a machine in 1359HA OS–Cluster configuration some disk unused by
local system (free) can be used by another one, double check the configuration also of
the other systems!
_______________________________________________________________________
Disks Selection
Mount Point need 5632 MBytes on Volume Group: “/dev/vg00” (pvg0)
_______________________________________________________________________

_______________________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 _(free)_ ______ __________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __________
D c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __________
D c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ __________
1AA 00014 0004 (9007) A4 – ALICE 04.10
_______________________________________________________________________
Select Data Area (Main instance) dev name or [q] to quit:
ED 02
3AL 88888 AAAA 85 / 190
190
Enter the name of a “free” disk.
_______________________________________________________________________
Disks Selection

_______________________________________________________________________

_______________________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 _(free)_ ______ __________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __________
D c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __________
D c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __________
c5t13d0 8680 0/7/0/0.13.0 __Data__ _Main_ vg00
_______________________________________________________________________
Confirm selection of device ”c5t13d0”
After your confirmation, the disk contents will be irremediably lost!!
The script will require you to confirm your choice before use it, and the
Physical volume ”/dev/rdsk/c5t13d0” has been successfully created.

Volume group ”/dev/vg00” has been successfully extended.
Physical volume group ”pvg0” has been successfully extended.
.
.
Activate SWAP area /dev/vg00/lvol13 ...
______________________________________________________________________
System need reboot x complete extension of file system current in use
_______________________________________________________________________
DISKS configuration was successful..
It is possible that more then one disk is requested to reach the amount of disk required space. The ex-
pected disk amount depends by the number of NMS and NMS instances requested, its size can be com-
puted following the instructions shown in the paragraph “Requested Hard DIsks” 4.1.2.4 at page 67.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 86 / 190
190
4.4.5.2 Kernel Configuration
The next execution phase regards the HP–UX 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 ...

Building a new kernel based on template file ”/stand/ALL.system”
Generating module: krm...
Compiling conf.c...
Loading the kernel...
Generating kernel symbol table...
Kernel update request is scheduled.
Default kernel /stand/vmunix will be updated by

newly built kernel /stand/build/vmunix_test
at next system shutdown or startup time.
KERNEL configuration was successful.
4.4.5.3 Software Layer Installation Predisposal
The last execution phase is related to the software layer, first of all identify the source depot where to find
all the software packages.
SOFTWARE predisposition activated ...
Now you have to specify where are stored the LAYERED PRODUCTS.
––––––––––––– LAYERED PRODUCTS Repository –––––––––––
1 – CDROM
2 – DEPOT
Insert choice and press [Enter]:[Enter]
You can choose between CD–ROM or network depot, here only the network depot choice is shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 87 / 190
190
4.4.5.3.1 Software Layer Installation Predisposal from Depot
Here the network depot choice is shown, enter “2[Enter]”, then the procedure requires you to specify the
depot, enter:

<depot hostname>:/alcatel/SCDEPOT[Enter]
Where you have to replace “<depot hostname>” with the name of the depot machine (see at paragraph
“Create the Depot Machine” 3.4 at page 48)
––––––––––––– Depot specification for LP ––––––––––––
Enter ’q’ to Quit or the path of the Depot: 192.202.21.8:/alcatel/SCDE-

POT
Checking Depot presence ...

Predisposed installation for product: Perl5005_3
Predisposed installation for product: tcl
Predisposed installation for product: tk
Predisposed installation for product: a2ps
.
.
.
Predisposed installation for product: Apache20
Predisposed installation for product: xemacs
Predisposed installation for product: TAO
Predisposed installation for product: MySQL
SOFTWARE predisposition was successful.
scmanageswp SESSION was successful.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 88 / 190
190
4.4.5.3.2 Software Layer Installation Predisposal from CD
Here the CDROM choice is shown, enter “1Enter]”, then the procedure requires you to specify the CD driv-
er, enter:
––––––––––– Device selection for LAYERED Products installation ––––––––––––
Enter ’q’ to Quit or the CD driver [default /dev/dsk/cxtxdx]:
Checking CD presence ...

Predisposed installation for product: Perl5005_3
Predisposed installation for product: tcl
Predisposed installation for product: tk
Predisposed installation for product: a2ps
.
.
.
Predisposed installation for product: Apache20
Predisposed installation for product: xemacs
Predisposed installation for product: TAO
Predisposed installation for product: MySQL
SOFTWARE predisposition was successful.
SESSION Predisposition was successful.
4.4.5.4 Software Layer Installation
The last message issued before starting the software package installation is:
=>>> WARNING: Now SCINSTALL will be invoked to activate the modifications.

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

Console Login:
Instead on the hp 9000 workstation the CDE login screen will be shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Before proceed to the next activities you have to login hp–ux system check for any error occurred during
the predisposition. Usually a specific message (see paragraph 3.2.1.16) immediately advise you that a
fault is occurred, but it also useful verify the contents of file:
/SCINSTALL/scinstall.log
ED 02
3AL 88888 AAAA 89 / 190
190
4.5 Install and Customize OS–Kernel
The Alcatel OS–Kernel is the operational platform, so it must be the first software installed.
To install OS–Kernel “install_NR7.sh” procedure requires:

• A depot machine or distribution CD available.

• The installing system must be authorized to retrieve the files from itself or from depot machine.
• When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
N.B. In order to prevent error messages during the OS–KERNEL customize it is advisable to
configure the GoGlobal–UX license as shown in APPENDIX B.3 at page 131.
GoGlobal–UX will be stopped by OS–KERNEL configuration script. DO NOT start the in-
stall_NR7 with OS–KERNEL option from any window open via GoGlobal–UX 2.0, be-
cause all the GoGlobal–UX windows will be closed, and the configuration aborted!
If the mentioned requirement are matched, the installation and customization can be started by entering:
...,sys,root # cd /alcatel/INSTALL_NR7 [Enter]
Cancel the TZ zone variable by entering:

...,sys,root # unset TZ [Enter]
The “uset TZ” command causes that all the date and time shown on the current terminal
window will be shown with default hp–ux timezone, Greenwich time –4 hours, but the
system Time Zone will be not changed. Because of this it is suggested to close this termi-
nal window as soon as the OS–Kernel installation and customization will be terminated.
For installation from CD:
1) insert the “SWP–NR7.0_ADD01” CD in the CD driver.
2) Mount the CD at /SD_CDROM directory:

3) Start the installation script entering:

...,sys,root# ./install_NR7.sh OS–KERNEL –cdrom [Enter]
4) The script issues the following question to require you to confirm the CD driver:
You have to reply with [Enter] to confirm, or enter e different CD device file name.
5) During the installation a message like this can be issued to advise you to replace the current
CD with a new one, just replace the CD in the driver, the procedure will go on automatically:
PLEASE INSERT CD–ROM : ”SWP–OS–KERNEL–V7.0 Vol 1/1”
For installation from Depot Machine:

...,sys,root# ./install_NR7.sh OS–KERNEL [Enter]
For both installation method:
The script start issuing the following mask:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 90 / 190
190
..........
........
......
....
..
XX XX XXXX XX XXXXXX XXXXX XX

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

Tue Apr 6 20:34:44 METDST 2004
===========================================================================

Then the procedure will ask you the software location by issuing the following to questions:
NOTE: Provide DEPOT hostname or address ?

NOTE: Provide DEPOT PATHNAME [/alcatel/DEPOT] ?
You have to replay the first with the hostname or IP address of the machine where the software depot has
been stored in, and the second with the software depot directory followed by [Enter] or just [Enter] key if
it is located in “/alcatel/DEPOT”.
N.B. The report shown in this paragraph is just an example, thak into account that the installa-
tion from CD issues the CD request with a message like this:
PLEASE INSERT CD–ROM : ”SWP–OS_KERNEL–V7.0 Vol 1/1”
The installation is executed by INSTALLER that shows you the contents of the package :
NOTE: Preparing to install ...

NOTE: Preparing to INSTALLER 7.0.5 ...
***********************************************************************
NOTE: [ –d ${INSTALL_ROOT}/Kernel/data ] && ${INSTALL_ROOT}/Kernel/
script/KernelServices stop
NOTE: Tue Apr 6 21:15:22 METDST 2004 – Executing OS–KERNEL pre_in-
stall_wa ...
NOTE: Tue Apr 6 21:15:22 METDST 2004 – OS–KERNEL pre_install_wa
completed ...
***********************************************************************
NOTE: ${INSTALL_ROOT}/INSTALLER/Install OS–KERNEL ${DEPOT_HOST}
file=${DEPOT_PATH}/OS–KERNEL_7.0.5.tar.gz interactive=no
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 91 / 190
190
NOTE: Tue Apr 6 21:15:22 METDST 2004 – Executing OS–KERNEL in-
stall_cmd ...
––––––––––––––––––––––––––––––––––––––
Install Tool: INSTALLER 7.0.5 [ Supporting NR7.0 ]

––––––––––––––––––––––––––––––––––––––

NOTE: NO CONFIGURATION provides by OS–KERNEL for the package installa-
tion, using
the default one .
Image Installation requested for:
Product OS–KERNEL
Format zip
Host tlvhgq
File /SD_CDROM//OS–KERNEL_7.0.5.tar.gz
Keep_data no
Check_sum ’NOT APPLICABLE’
Interactive no
PLEASE ENSURE LOCAL OS–KERNEL SYSTEM IS NOT RUNNING

.
.
.
The installation start automatically, this step will take up to 15 minutes.
The last question is related to the OS–Kernel customization; you have to reply also this question with
“y[Enter]”
Do you want to execute OS–KERNEL Custom? [y|n|q]y[Enter]
Then the OS–Kernel customization will be executed showing the trace on the terminal.
*******************************************************************
NOTE: ${INSTALL_ROOT}/Kernel/script/KernelCustomize
NOTE: Tue Apr 6 21:23:22 METDST 2004 – Executing OS–KERNEL

custom_cmd ...
.
.
.
NOTE: Reapplying PLT registrations.
NOTE: Check Go–Global 2 configuration ...
The procedure will stop 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, de-

fault=no)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Reply the question with “yes[Enter]” to allow Go–Global UX customization.
ED 02
3AL 88888 AAAA 92 / 190
190
NOTE: Starting Go–Global 2 configuration ...
NOTE: Stopping GoGlobal 2 server ...
NOTE: Restoring database ...
NOTE: Restore Go–Global 2 database Terminated
NOTE: Starting Go–Global 2 server ...

NOTE: Start Go–Global 2 terminated with ERROR

NOTE: Tue Apr 6 21:43:32 METDST 2004 – OS–KERNEL custom_cmd
completed ...
NOTE: OS–KERNEL installation completed

===================================================================
NOTE: Session finished on: Tue Apr 6 21:43:32 METDST 2004
The OS–Kernel installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occured by check the contents of the following file:
/alcatel/INSTALL_NR7/log/install_NR7_OS–KERNEL_*.log
N.B. If you doen’t have already configure the GoGlobal License server, it could be displayed
an error message like:
INFORMATION: No server defined in /opt/graphon/etc/license_serv...
Local license file /opt/graphon/etc/license.dat wi...
Starting the database: FAILED.
See /opt/graphon/etc/gdbi.err for more information.
Starting the GraphOn Login Daemon: FAILED.
A likely cause is that another program is listening on TCP port ...
791. Look for the message ”startup: unable to create any listening
sockets” in /var//opt/graphon/log/gold.log, then either free the...
ports 491 and 791 or specify a different value for GOLD_PORT and
GOLD_SSL_PORT in /opt/graphon/etc/goglobalux.
Another likely cause is that the gold daemon could not connect t...
database. Look for the message ”startup: cannot open database” in
/var//opt/graphon/log/gold.log, then check /opt/graphon/etc/gdb...
Dont’ care of it, and configure the GoGlobal License Server.
It is also suggested to close the current terminal window and open a new one to continue the installetion
with the right time zone.
1) Dismont the CD by entering:

...,sys,root# umount /SD_CDROM[Enter]
2) Remove the CD from the driver.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 93 / 190
190
4.6 Install and Customize 1353NM
This chapter explains how to install and customize the 1353NM on the server. This activity is performed
by the “install_NR7.sh” script in one shot, the distinction is introduced to better explain the actions required

by 1353NM, in fact this software can be installed with two different kind of clients. its own and another one

to permit navigation to server with NR5 and NR61353SH.
4.6.1 Install 1353NM
To install 1353NM “install_NR7.sh” procedure requires:

• A depot machine or distribution CD have to be available.
• The installing system must be authorized to retrieve the files from itself or from the depot ma-
chine.
• When installing from depot machine: The hostname of the depot machine correctly defined in
the /etc/hosts file.
• You have to be able to login the system via GUI, in case of HP server the GoGlobal–UX have
to be authorized with the license code (see Appendix B.3 at page 131).
If the mentioned requirement are matched, the installation and customization can be started by:
a) Login the system via Graphical User Interface CDE as “root” user.
N.B. IF THE INSTALL NR7 IS STARTED FROM A SHELL WITHOUT A USEFUL DISPLAY
VARIABLE SET THE 1353NM CUSTOM WILL FAIL.
b) Open a dtterm window.
c) Entering the following commands at dtterm prompt:

...,sys,root # cd /alcatel/INSTALL_NR7[Enter]


...,sys,root# ./install_NR7.sh 1353NM –cdrom [Enter]
4) The script issues the following question to require you to confirm the CD driver:
You have to reply with [Enter] to confirm, or enter e different CD device file name.
5) During the installation a message like this can be issued to advise you to replace the current
CD with a new one, just replace the CD in the driver, the procedure will go on automatically:
PLEASE INSERT CD–ROM : ”SWP–1353NM_APP–V7.0 Vol ...”
For installation from Depot machine:

...,sys,root# ./install_NR7.sh 1353NM [Enter]
For both installation methods:

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. To allow the recovery of errors it is possible to start “install_NR7” with option “–confirm”, the
option causes the issues of confirm request message before executing each step in the instal-
lation and configuration. Replying “no” to these questions you can skip the step.
ED 02
3AL 88888 AAAA 94 / 190
190
N.B. The output provided are just an example of the procedure behavior. THE INSTALLATION
CAN ISSUE DIFFERENT MESSAGES!
The script start issuing the Alcatel mask, then it will ask you some questions.
..........
........
......
....
..

Installing 1353NM package

Wed Apr 7 09:53:18 METDST 2004
===========================================================================
Install NR7 tool asks you where to find the depot area for the OS–Kernel software distribution kits. You
have to reply providing the host name or IP address of the depot machine (see paragraph 3.4.1.1 “Create
Alcatel NMS Depot” at page 48)

Enter the name of the depot host, and the depot directory when different then /alcatel/DEPOT.
For both installation methods:
N.B. The report shown in this paragraph is just an example, thak into account that the installa-
tion from CD issues the CD request with a message like this:
PLEASE INSERT CD–ROM : ”SWP–1353NM_APP–V7.0 Vol ...”
***********************************************************************
NOTE: ${INSTALL_ROOT}/INSTALLER/Install 1353NM ${DEPOT_HOST}
file=${DEPOT_PATH}/1353NM_7010_CORE_MAR19.tar.gz interactive=no
NOTE: Wed Apr 7 09:53:26 METDST 2004 – Executing 1353NM in-

stall_cmd ...
––––––––––––––––––––––––––––––––––––––
1AA 00014 0004 (9007) A4 – ALICE 04.10
––––––––––––––––––––––––––––––––––––––
ED 02
3AL 88888 AAAA 95 / 190
190
4.6.2 Installing 1353NM Core Software

Product 1353NM

Format zip
Host tlvhgq
File /SD_CDROM//1353NM_7010_CORE_MAR19.tar.gz
Keep_data no
Interactive no
PLEASE ENSURE LOCAL 1353NM SYSTEM IS NOT RUNNING
....
....
....
If you had started “install_NR7.sh” with –confirm option, you have to confirm by entering “yes[Enter]”
User Id: NM–Lab

DATE: 2004 March Friday 19 18:37:06 MET
Product: 1353NM
Products list :
None
Freezing identifier confirmed: date Wed Apr 7 09:53:28 METDST 2004..

NOTE: Cleaning temporary areas ...
....
....
....>
The installation of the first package will take few minutes, the next one will be shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 96 / 190
190
4.6.3 Installing 1353NM EMLIM Software
––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––
Product 1353NM
Format zip
Host tlvhgq
File /SD_CDROM//1353NM_7010_IM_MAR19.tar.gz
Keep_data no
Interactive no

AND THE RELATED SEC SUBSYSTEM IS NOT RUNNING.
N.B.: IT IS RECOMMENDED TO AVOID THE STOP OF

THE IMAGE INSTALLATION PROCESS. >
Installation confirmed: date Wed Apr 7 09:54:19 METDST 2004.

User Id: NM–Lab
Product: 1353NM
Products list :>
Freezing identifier confirmed: date Wed Apr 7 09:54:19 METDST 2004.

NOTE: Cleaning temporary areas
....
....
....>
The installation of the 1353NM EMLIM package will take about10 minutes, the next one will be shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 97 / 190
190
4.6.4 Installing 1353NM EMLUSM Software
Now install_NR7 script will install the EMLUSM software.

–––––––––––––––––––––––––––––––––––––

––––––––––––––––––––––––––––––––––––––
Product 1353NM
Format zip
Host tlvhgq
File /SD_CDROM//1353NM_7010_USM_MAR19.tar.gz
Keep_data no
Interactive no>
Installation confirmed: date Wed Apr 7 09:58:49 METDST 2004.

User Id: NM–Lab
Product: 1353NM
Products list :
None>

....
....
.....
The installation of the 1353NM EMLIM package will take about15 minutes, the next one will be shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 98 / 190
190
4.6.5 Installing 1353NM Patches
The following step can be executed more than once, it depends by the number of patches.
––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––
Product 1353NM
Format zip
Host tlvhgq
File /SD_CDROM//1353NM_7010P1_MAR25.tar.gz
Keep_data no
Interactive no

AND THE RELATED SEC SUBSYSTEM IS NOT RUNNING.
>
User Id: NM–Lab

DATE: 2004 March Thursday 25 14:46:47 MET
Product: 1353NM
Products list :
None

....
....
.....
The software installation is now completed.
4.6.6 Installing 1353SH BKW NR5/6
When the 1353NM installation is completed, “install_NR7” will prompt you the following question:
NOTE: Do you want to execute 1353NM Install package to manage NR5/6

1353SH? [y|n|q]
1353SH patch must be installed to that system to be able to integrate it with the 1353NM
(see the 1353SH 5 and 1353SH 6 release notes).
1AA 00014 0004 (9007) A4 – ALICE 04.10
If you have any NR5 or NR6 1353SH that have to provide the navigation feature from the installing system,
you have to reply with “y[Enter]” to this question.
ED 02
3AL 88888 AAAA 99 / 190
190
4.6.7 Automatic Post Installation Script Execution
Some post installation activities are automatically executed before starting the 1353NM Custom.

4.6.8 Customize 1353NM
1353NM customization executes the minimum configuration of the software, it is performed in two steps
by “install_NR7.sh” script: pre–custom workaround and custom. Both of them are started replying “y[En-
ter]” the following question issued by “install_NR7.sh”:
Do you want to execute 1353NM Custom ? [y|n] y [Enter]
The procedure starts tracing the custom execution:
======================================================================
NOTE: Executing 1353NM custom_cmd...
NOTE: runing </alcatel/Kernel/script/Custom>
NOTE: Executing 1353NM custom_cmd ...
NOTE: Basic Kernel Services (Connection Manager, Action Polling) Run-
ning. .......... .
The “System, Instances,List” window will be shown on the screen after a few seconds, it allows you to se-
lect the instance that you want customize:
Figure 16. List of existing instances
Select “Choose_one” and then “New–Instance” to define and customize 1353NM–7.0. Then select “Apply
& exit” in the Actions menu.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 100 / 190
190
The custom “Parameters Definition” window will be shown on the screen after a few seconds, it allows you
to set the relevant custom variables:
Figure 17. 1353NM Customize Window
N.B. To select the value for the following items you have to move the pointer on the box under the
label, then press the selection button of the mouse, a popup menu will be shown with the pos-
sible choices, moving the pointer choose one of them and release the mouse button: Sy-
stem_Version, System_Instance_Rule, Master Kernel_Type and Driver_Version.
To customize the 1353NM you have to set the “System_Version” on 1353NM–7.0, then enter the Instance
identification number defined at predisposal time (see “Predispose 135NM Instance” paragraph 4.4.3.2
at page 75) in the input area under the label “System_Instance_Id”.
If the Instance identification number does not correspond to the predisposed one, the
customization script will create the data in a wrong place, and the /usr file system can get
in overflow.
Set the “System_Instance_Rule” depending by the rule of the specific instance identification number.
You have to set it to “Master” when the instance is an Information Manager (IM), but “Client” when the
instance is a User Service (US).
When you customize a 1353NM Client the related Master hostname have to be defined in
1AA 00014 0004 (9007) A4 – ALICE 04.10
/etc/host file.
ED 02
3AL 88888 AAAA 101 / 190
190
The input fields identified by “System_Instance_Name” allows to define the name of the system within
the TMN–OS application.
N.B. Do not supply the hostname as System_Instance_Name

For the Client instances “System_Instance_name” MUST be the same than the Master one. If
you choose a name different than the default for the master instance, don’t forget to enter it
again for the client.
The “Master_HostName” is meaningful only for Client instances. For client machine with1359HA OS–
Cluster you have to specify the Virtual Hostname.
The “System_Instance_Name” and “Master_HostName” must be different.
Leave “Master_Kernel_Type“ and “Driver_Version” at default setting.
Then pulldown the menu “Action” (in the left upper corner), select “Apply & exit” to start the customizing
procedure.
A trace window will be open on the screen showing the customization progress.
Figure 18. 1353NM Customize Trace
The 1353NM Custom script will show the “Custom Product Selection 1353NM <instance number>” win-
dow. This window allows to reduce the time spent to perform the custom by specifying a subset of the Net-
work Element, but the Element Managers of the Network Element families not configured can not be used
in the 1353NM. If you want to configure all the Element Managers simply leave the “CUST_TYPE” equal
to “FULL”, otherwise change it to “PARTIAL”, and select in the list the Network Element family you want
to configure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 102 / 190
190
Figure 19. 1353NM Custom Product Selection N.1
Figure 20. 1353NM Custom Product Selection N.2

1AA 00014 0004 (9007) A4 – ALICE 04.10
procedure.
ED 02
3AL 88888 AAAA 103 / 190
190
Please, ignore the warning messages shown in the following picture.

Figure 21. 1353NM Custom Warning
The procedure will complete its task in about 40 minutes on a L1000 server, issuing some foreseen warn-
ing messages shown in the Figure 21. Please ignore them.
If your planning foresees more than one 1353NM Retix Stack, it is suggested to configure
now all the lan cards needed with an IP Address (see APPENDIX F “Lan Configuration” at
page 187 for more information).
The 1353NM installation and customization is now completed, before continue installation it is advisable
/alcatel/INSTALL_NR7/log/install_NR7_1353NM_*.log
1) Dismount the CD by entering:

4.6.9 How to Proceed with More Than One 1353NM Instance
The 1353NM foresees to have more than one client instance on board of 1354RM, the reason is: the
1354RM must have a 1353NM client for each 1353NM Master it has to supervise. In this case you have
to install the 1353NM software once and customize any predisposed instance. The “install_NR7.sh” al-
lows to custom the first one, if you have more than one, you have to start the OS–Kernel Custom procedure
for each one of the instance but the first.
To run OS–Kernel Custom procedure:
– Login the system as root with CDE GUI.
– Open a graphical “terminal” .
– Enter the command: /alcatel/Kernel/script/Custom[Enter]
A window like Figure 17. will be open, enter next instance identification data as shown in the paragraph
“Customize 1353NM” 4.6.8 at page 100, and proceed customizing the next 1353NM.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Execute the Custom for all instances.
ED 02
3AL 88888 AAAA 104 / 190
190
4.6.10 Customize 1353SH BacKWard Compatibility Tool
The 1353SHBKW tool is useful to perform navigation from NR7.0 Network Managers (1354) on NR5 or
NR6 Element Managers. It is an optional package installed together 1353NM replying “y[Enter]” to the fol-
lowing question also shown at paragraph 4.6.6“Installing 1353SH BKW NR5/6” at page 99:
NOTE: Do you want to execute 1353NM Install package to manage NR5/6

1353SH? [y|n|q]
The 1353SH BKW need some data to be able to perform its tasks, this data have to be created as a
1353SH 7.0 instances, this argument had been already introduced during 1353NM predisposal at para-
graph 4.4.3 page 73. For each the created1353SH 7.0 instance you have to perform the data custom script
as shown in this paragraph:
To run OS–Kernel Custom procedure:
– Login the system as root with CDE GUI.
– Open a graphical “terminal” .
– Enter the command: /alcatel/Kernel/script/Custom[Enter]
Figure 22. 1353SHBKW 7.0 Custom System Selection.
Select “Choose_one” and then “New–Instance”, then select “Apple &exit” in the Actions menu.
The custom “Parameters Definition” window will be shown on the screen after a few seconds, it allows you
to set the relevant custom variables:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 105 / 190
190
Figure 23. 1353SHBKW 7.0 Custom Parameters Set–up.
To customize the 1353NM you have to set the “System_Version” on 1353SH–7.0, then enter the Instance
identification number defined at predisposal time (see “Predispose 135NM Instance” paragraph 4.4.3.2
at page 75) in the input area under the label “System_Instance_Id”.
If the Instance identification number does not correspond to the predisposed the custo-
mization script will create the data in a wrong place, and the /usr file system can get in
overflow.
You have to set it to “Client” .
N.B. Do not supply the hostname as System_Instance_Name
For the Client instances it must be the same than the 1353SH 5 or 6 Master one.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 106 / 190
190
The “Master_HostName” must be specified, and it must be declared in /etc/hosts file, and the
host have to be reachable.
The “System_Instance_Name” and “Master_HostName” must be different.

Set the “Master_Kernel_Type“ to “EXTERNAL” and “Driver_Version” at default setting.
procedure.
Figure 24. 1353SHBKW 7.0 Custom Execution window.
The procedure will complete its task in about 10 minutes on a L1000 server, issuing some foreseen warn-
ing messages shown in the Figure 24. Please ignore them.
The 1353SH installation and customization is now completed, before continue installation it is advisable
/alcatel/INSTALL_NR7/log/install_NR7_1353SH_*.log
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 107 / 190
190
4.7 Install and Customize a Generic NMS and NMC
This chapter explains how to install and customize a generic NMS or NMC. This activity is performed by
the “install_NR7.sh” script in one shot.

In the following table the NMS and NMC foreseen for NR7.0:
NMS/NMC Name Version Description
1353NM 7.0 Network Element Manager (*)
1353SH 7.0 1353SH Client allow the navigation from Network Manager
Layer to 1353SH of NR5 and NR6.
1354BMATM 7.0 Broadband ATM Network Manager
1354RM 7.0 Regional Manager
1355VPN 3.2 Virtual Private Network
1359HA_OSRES 7.0 High Availability O.S. Resilience
1359HA_OSCLS 7.0 High Availability O.S. Cluster
1359IOO 5.0 Generic O.S. – O.S. Interface
1359ISN 2.2 ISN Open Interface
Table 6. NR7.0 NMS/NMC table
(*) The installation of this item has been already shown in an other paragraph.
4.7.1 Install NMS or NMC
To install any kind NMS or NMC shown at Table 6. (except 1353NM) with “install_NR7.sh” procedure re-
quires:
• A depot machine or CD distribution set available.
• The installing system must be authorized to retrieve the files from itself or from the depot ma-
chine.
• 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.
If the mentioned requirement are matched, the installation and customization can be started by entering:
a) Login the system via Graphical User interface CDE as “root” user.
N.B. IF THE INSTALL NR7 IS STARTED FROM A SHELL WITHOUT A USEFUL DISPLAY
VARIABLE SET THE NMS CUSTOM WILL FAIL.
b) Open a dtterm window.

1AA 00014 0004 (9007) A4 – ALICE 04.10
c) Entering the following commands at dtterm prompt:

...,sys,root # cd /alcatel/INSTALL_NR7 [Enter]
ED 02
3AL 88888 AAAA 108 / 190
190



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

...,sys,root# ./install_NR7.sh <NMS/NMC name> [Enter]
N.B. To allow the recovery of errors it is possible toe start “install_NR7” 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 mask, then it will ask you some questions.
........
......
....
..

Installing <NMS/NMC name> package

Mon Feb 2 11:53:06 MET 2004
===========================================================================
Install NR7 tool asks you where to find the depot area for the OS–Kernel software distribution kits. You
have to reply providing the host name or IP address of the depot machine (see paragraph 3.4.1.1 “Create
Alcatel NMS Depot” at page 48)
Enter the name of the depot host, and the depot directory when different then /alcatel/DEPOT.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
.
The output depends by the chosen NMS or NMC
.
Do you want to execute <NMS/NMC name> Custom? [y|n|q] )
1AA 00014 0004 (9007) A4 – ALICE 04.10
NOTE:
If you had started “install_NR7.sh” with –confirm option, you have to confirm by entering “y[Enter]”
The time spent for installation of package depends by NMS.
ED 02
3AL 88888 AAAA 109 / 190
190
4.8 Customize NMS
NMS customization execute the minimum configuration of the software, it is performed in two steps by
“install_NR7.sh” script: pre–custom workaround and custom.

NOTE: /alcatel/Kernel/script/Custom
NOTE: Mon Feb 2 14:44:39 MET 2004 – Executing <NMS/NMC name> custom_cmd
...
NOTE: /alcatel/Kernel/script/Custom
Figure 25. List of existing instances
Select “Choose_one” and then “New–Instance” , then select “Apple &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:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 110 / 190
190
Figure 26. 1354RM Customize Window
To customize the 1354RM you have to set the “System_Version” on new NMS/NMC (including version),
then enter the Instance identification number defined at predisposal time (see “Create NMS Instance”
paragraph 4.4.4.2 at page 82) in the input area under the label “System_Instance_Id”.
If the Instance identification number does not correspond to the predisposed the custo-
mization script will create the data in a wrong place, and the /alcatel file system can get in
overflow.
You have to set it to “Master” when the instance is an Information Manager (IM), but “Client” when the
instance is a User Service (US).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 111 / 190
190
For the Client instances it must be the same than the Master one. If you choose a name different
then the default customizing the master instance, don’t you forget to enter it again for the client.

When you customize a NMS Client the related Master hostname have to be defined in

/etc/host file.
The “Master_HostName” is meningeal only for Client instances. For 1359HA OS–Cluster you have to
specify the Virtual Hostname.
Leave “Master_Kernel_Type“ and “Driver_Version” at default setting.
Then pulldown the menu “Action” (in the left upper corner), select “Apply & exit” to start the custom proce-
dure.
Figure 27. NMS Customize trace window
The procedure will complete when the [Dismiss] button will be enabled.
The NMS/NMC installation and customization is now completed, before continue installation it is advisable
/alcatel/INSTALL_NR7/log/install_NR7_<NMS/NMC name>_*.log
1) Dismount the CD by entering:

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 112 / 190
190
5 FINAL INTEGRATION
Now the installation is completed, but the installed NMS still need to be configured to be able to start, the
activity is performed by “System Configuration” tool of each application, because this you have to refer
to the Administration Guide of each NMS installed to know how to perform the specific NMS process confi-
guration.
VERY IMPORTANT!!
When all the TNM machines have been configured singularly, you have to run on each
one of them the final integration script!
5.1 Final Integration Script
On each just installed machine:
1) Before start, you must be sure that all systems involved are already installed, customized and
configured by system configuration tool. To easy identify the potential involved system opening
the “TMN OS” tool available on display front panel of any Alcatel NMS operator session.
2) Login as root user.
3) Start the global integration script by entering /alcatel/Kernel/script/UpdateNetworkConnection-

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

NOTE: Updating Required Client Instances...
NOTE: Starting Required Inter–System Integrations...
NOTE: 1353NM_1: No Integratable System defined. Skipping 1353NM_1.
NOTE: 1354RM_3: Detected the following integrated Systems: 1353NM_1
NOTE: 1354RM_3: 1353NM_1 Already integrated. Re–Applying Integration.
...
...
For each system that have to be integrated the following question can be issued:
1354RM_3: Run the Integration of 1353NM_1? [y/n]
If you reply “y” the system will be integrated, and the procedure will issue also these other questions:
1354RM_3: Run the PLT Integration of 1353NM_1? [y/n]
1354RM_3: Run the Backup/Restore Integration of [y/n]
1354RM_3: Run the Navigation Integration of 1353NM_1? [y/n]
Reply “y” to all of them.
Warning and error messages will advice you that the remote system is not reachable or not properly config-
ured, and the machine will be not integrated. If such kind of message are issued, identify the problem, fix
it, and run again the integration script.
Example:
WARNING: 1353RM_3: Connection problems with <hostname>. Skipping Update.
1AA 00014 0004 (9007) A4 – ALICE 04.10
When the procedure will be successfully executed, you will be able to use all the Network Management
System features.
ED 02
3AL 88888 AAAA 113 / 190
190
5.2 Alarm Surveillance Federation
The Alarm Surveillance federation is an OS–Kernel optional feature that allows to see the alarms of all
NMS client installed on system in a single Alarm Surveillance graphical interface.

To be able to perform the AS federation you must have two or more Client and/or Master instance of one
of following NMS: 1353NM, 1354RM and 1354BM.
The command syntax is:
AS–USMFederation.pl –name <ASF Name> –sec <Sec Instance> <NMS Instance List>
Where:
<ASF Name> Specifies the AS Federation name, that will be shown by “TMN OS” tool
and AS USM Window title.
N.B. No special characters are allowed in the AS USM Window title.
<Sec Instance> Specifies the NMS Instance that provides the Alcatel security (SEC)
feature. Because just one SEC can be used, you have to choose which
one of the NMS belonging to AS federation has to provide this feature. The
choice has to be done by following these roles:
• Specify the 1354RM instance, if any.
• If the previous role is not verified, specify the 1354BM ATM instance, if any.
• If the previous roles are not verified, arbitrary specify one of the 1353NM
instances.
• If no one of the previous roles is verified, the federation can not be done.
<NMS Instance List> Specifies the list of the NMS that be configured in the federation.
You can create different AS Federations, by running the command with different ASF names.
The command must be executed by “root” user, and the file is located in “/usr/Systems/Global_Instance/
AS/script/”, so to start the command you have to logging the system as “root” and enter:
...,sys,root # /usr/Systems/Global_Instance/AS/script/AS–USMFederation.pl \[Enter]
–name <ASF Name> –sec <Sec Instance> <NMS Instance List>
This is an example of two AS federation performed on a system equipped with: 1354RM Master instance
number 2, three 1353NM Client instance number 1, 2 and 3. The latter will be call “RegionEst” involving
the 1354RM and 1353NM instance number 1, and the former will be call “RegionWest” involving the
1354RM and 1353NM instance number 2 and 3.

–name RegionEst –sec 1354RM_2 1354RM_2 1353NM_1

–name RegionWest –sec 1354RM_2 1354RM_2 1353NM_2 1353NM_3
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 114 / 190
190
6 TROUBLESHOOTING
Here after is shown how to solve some trouble can occur during the installation, and how to proceed when
possible.
6.1 Identify a Failure Condition
Before proceed with the troubleshooting it is suggested to identify the problem. It also important to distin-
guish between messages issued during the normal behavior and real error messages.
These is a messages issued at login time to advise the operator that an installation activity is in progress:
********************* WAIT – INSTALLATION IN PROGRESS *******************
Do not alter environment, check log file in /SCINSTALL/scinstall.log
***************************************************************************
This is not an error message, it just advise you that an installation activity is in progress, in this case it is
better wait until the activity will be terminated.
The following message will be issued when an error is met during the automatic software installation.
**************** THIS SYSTEM IS NOT CORRECTLY INSTALLED *****************
***************************************************************************
N.B. Some system reboot are foreseen to correctly carry on the installation, that means don’t worry
if the system reboot automatically.
6.2 Failure installing a HP–UX
HP–UX 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–UX installation can not be recovered the
installation have to be started from the beginning.
The HP–UX installation will be completed when the following message will be shown on the console:
******* The HP–UX software has been successfully restored *******
But the error recovery will be possible only after the first reboot of the system performed just after the mes-
sage:
***** The System reboots automatically, please wait *****

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 115 / 190
190
6.3 Recoverable Faults
6.3.1 Recoverable Faults Installing Software

Recoverable are the faults occurred before the start of installation, or during the analysis.
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 proce-
dure:
– Logging the system as “root” user.
– Change the default directory on “/SCINSTALL/execution”:

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

...,sys,root # ls *.in_progress [Enter]
...,sys,root # mv <file_name>.in_progress <file_name> [Enter]
• for example:
...,sys,root # ls *.in_progress [Enter]
01001SC.SCstdinstall.in_progress
...,sys,root # mv 01001SC.SCstdinstall.in_progress 01001SC.SCstdinstall [Enter]
– Reboot the system to allow the correct
The procedure will try again the installation of the failed package.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 116 / 190
190
6.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

**************************************************************************
Look at the “/SCINSTALL/scinstall.log” file to know which is the meet problem and how to fix it before pro-
ceed.
When the error has been recovered remove the file “/SCINSTALL/scextendfs.error_msg“ to remove the
message to remove the message at login time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 117 / 190
190
6.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.
– The procedure has been abnormally terminated.
6.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.
6.3.2.2 scmanageswp Abnormally Terminated
“scmanageswp“ uses a flag directory to prevent multiple execution from different shells, if you start the
script when another it is already running it will terminate issuing the message:
=>>> ERROR : SCMANAGESWP procedure already running on system.

Multi activation is not allowed !!!
=>>> ERROR : Current program terminated.
May occurs the flag directory it is not removed, for example when it is executed via telnet and a 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 pa-
rameter can not be checked.
If “ps” command does not issue any line you can proceed with the manual unlock by entering the com-
mand:
...,sys,root # rm –r /tmp/.scswpsession [Enter]
Then start again “scmanageswp”.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 118 / 190
190
6.4 Kerberos Problems
There are two Kerberos known problems with possible troubleshooting.

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

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

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

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

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

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 119 / 190
190
6.5 Device Full
Sometimes a file systems can get full, this situation can occurr because different reasons, hereafter some
of them are explane.

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

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

...,sys,root # cleanup –s [Enter]
6.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 sug-
gested 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 “vgdisplay vg00” can be used to check how many free mega–bytes are still available on
the current volume group configuration. Multiplying the Physical extent size (PE Size) with the number of
free PE (Free PE) you can know the amount of not allocated space.
––– Volume groups –––

VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 15
Open LV 15
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 5372
VGDA 6
PE Size (Mbytes) 32
Total PE 813
Alloc PE 682
Free PE 131
1AA 00014 0004 (9007) A4 – ALICE 04.10
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0
ED 02
3AL 88888 AAAA 120 / 190
190
If it is too small, you can check the availability of hard disk by entering the command:
...,sys,root # scextendfs –i [Enter]
The command output will be like the following:

___________________________________________________________________________
Disks Selection
___________________________________________________________________________

___________________________________________________________________________
c2t2d0 8680 0/0/2/0.2.0 __Data__ _Main_ vg00
c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __________
c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __________
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ __________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ __________
c5t14d0 8680 0/7/0/0.14.0 __Data__ _Main_ vg00
___________________________________________________________________________
N.B. If you have a disk mirror protection, the file system extension can ask for more than one
disk.
Before proceed within a 1359HA OS–Cluster 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”


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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 121 / 190
190
6.6 Inittab Process Not restarting
Sometimes the processes specified in “/etc/inittab” file whit option “respawn” are not re–spawned correct-
ly, it this case can be useful perform the following procedure:

a) Login the system as “root” user,
b) Replace the keyword “respawn” with “once” in the line corresponding to the not started process.
c) Ask init to re–read the configuration file by entering:

...,sys,root # init q [Enter]
d) Restore back the keyword “respawn” instead of “once” just modified.
e) Ask again init to re–read the configuration file by entering:

...,sys,root # init q [Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 122 / 190
190
APPENDIX A NMS/NMC SPECIFIC DATA
Alcatel Application Software is divided in two classes: Network Management Subsystem (NMS) and Net-
work Management Components (NMC). The former class identifies systems that allow the Element Mana-
gement (1353) or the Network Management (1354/1355), the latter one identifies optional functionalities
separately sold.
A.1 NMS Class
NMS are the basic items for installation purpose, them have a specific predisposal activity that allow them
the correct behavior, in the following list the NMS that can be predisposed by OS–Conf for NR7.0:
OS_KERNEL V7.0
This is the base platform for all the Alcatel TNM Applications. No instance is foreseen, but it has to
be always installed.
1353NM V7.0
Instance Definition: Identifier N ______ 1359HA OS–Cluster Protection
type: Master Client Spare system ( only for 1359HA OS–Cluster )
Size(*):Small Medium Large



N.B. You must install 1353NM on 1354 subsystem, and you have to create a 1353NM
instance for each 1353NM system under control of 1354 one.
1354RM V7.0
1354BMATM V7.0
1355VPN V3.2
Instance Definition: Identifier N ______
(*) Not useful for Client

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 123 / 190
190
A.2 NMC Class
The NMC are software components, them are usually install only to provide additional feature to an already
installed NMS. That means the NMC have to be installed only when the NMS them depends to are also

installed (or planned to be installed).

1359HA_OSRES and 1353SHBKW require the system predispose before installing them,
but the 1353SHBKW installation is done inside the 1353NM one
1355IOO and 1359ISN does not require any system predisposal
NMC Name NMS Dependencies.
1359IOO V5.0 1353NM 7.0 and 1354RM
1359ISN V2.2 1354RM
1359HA_OSRES V7.0 1353NM 7.0, 1354BM and 1354RM

type: Master
2 Client
4 Client
8 Client
1359HA_OSCLS V7.0 1353NM 7.0, 1354BM and 1354RM
1353SH V7.0 (1353SHBKW) 1353NM 7.0

type: Client

type: Client

type: Client

type: Client
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 124 / 190
190
A.3 Disk Requirement Tables
The following table shows the disk space requested for swap, program installation, and depot packages.
The value are specified in M bytes
NMS Swap Required Software Size Depot Package Size
OS–Kernel 100 1800 600
1353NM(*) 500 3000 1200
1354RM 500 1000 450
1354BMATM 500 1000 110
1355VPN 500 500 40
1359ISN N.A. N.A. 70
1355IOO N.A. N.A. 20
NR7.0 ADD1 N.A. N.A. 230
Table 7. Disk requirements for NMS Software
NMS Master Small Master Medium Master Large Presentation(*)
Swap Data Swap Data Swap Data Swap Data
1353NM 500 2000 1500 4000 2500 8000 250 150
1354RM 1500 2000 3500 4000 7500 8000 2000 400
1354BMATM 1500 2000 3500 4000 7500 8000 2000 200
1355VPN N.A. N.A. 500 2000 N.A. N.A. N.A. N.A.
Table 8. Disk Requirements for NMS Instances.
(*) The presentation does not foreseen the 1359HA OS–Cluster protection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 125 / 190
190
A.4 Alcatel CD Codes
The following table provides the Alcatel CD codes of all media provided with NR7.0.

CD Label CD Code Description
SWP–OSCONF–V7.0.5 3AL 72881 AAAA 01 hp–ux 11i installation tool. Six CD with
the following labels forms it: UX64, 1/4,
2/4, 2/4 4/4 and ADD1.
SWP–OSCONF–V7.0.5 3AL 72881 AAAA 02 hp–ux 11i installation tool. Six CD with
the following labels forms it: UX64 (Dec
N.B. IThis edition is man- 03), 1/4, 2/4, 2/4 4/4 and ADD1.
datory for rp3410,
rp3440 and rp4440
HP servers.
SWP–OS_KERNEL–V7.0 3AL 88872 AAAA 01 Alcatel OS–Kernel and installation tools.
SWP–1353NM_APP–V7.0 3AL 89055 AAAA 01 Alcatel 1353NM NMS Software. Three CD

forms it.
SWP–1354RM_APP–V7.0 3AL 61339 AAAA 01 Alcatel 1354RM NMS Software.
SWP–1354BM_ATM_APP–V7.0 3AG 23908 AAAA 01 Alcatel 1354BM ATM NMS Software.
SWP–1355VPN_APP–V3.2 3AL 72162 AAAA 01 Alcatel 1355VPN Software.
SWP–1359HA_OSCLS–V7.0 3AL 88115 AAAA 01 Alcatel 1359HA OS Cluster Software.
SWP–1359HA_OSRES–V7.0 3AL 88118 AAAA 01 Alcatel 1359HA OS Resilience Software.
SWP–1359IOO_APP–V5.0 3AL 88332 AAAA 01 Alcatel 1359IOO Generic OS–OS inter-

face Software.
SWP–1359ISN_APP–V2.2 3AL 88225 AAAA 01 Alcatel 1359ISN Open Interface Software.
SWP–NR7.0_ADD01 3AL 88889 AAAA 01 NR7.0 Addendum 01 with mandatory

patches.
Table 9. Alcatel CD codes

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 126 / 190
190
APPENDIX B GOGLOBAL–UX INSTALLATION AND CONFIGURATION
B.1 GoGlobal–UX Installation on HP–UX System

The GoGlobal–UX software is already installed on the HP–UX system foreseen for Alcatel TMN applica-
tion.
B.2 GoGlobal–UX Installation on PC
To install the software, perform the following steps:
a) Open a DOS window on PC and type the following commands:

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

ftp> bin [Enter]
ftp> get go_setup_2*.exe [Enter]
ftp> quit [Enter]
b) Double click on the executable.
c) The “Install Shield Wizard” window will be opened:
Figure 28. 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/Pre-
vious Version” B.2.1 at page 130 , otherwise proceed with the next point.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 127 / 190
190
d) The next window will be opened showing the welcome message:

Click on Next to go on. Wait a few seconds the install procedure.
e) The “License Agreement” window will be opened:
Click on Yes to go on.
f) The “Destination Location” window will be opened:

1AA 00014 0004 (9007) A4 – ALICE 04.10
Choose your destination location and click on Next to go on. Wait a few seconds the install procedure.
ED 02
3AL 88888 AAAA 128 / 190
190
g) The “Install Shield Wizard Complete ” window will be opened:
Click on Finish to go on.
h) The “Connection” window will be opened
You have to insert the Server Address of the machine that you want to be connected to.
Click on Connect. The “Authentication” window will be opened
You have to insert:
Username
Password
Click on OK. GoGlobal–UX will open a connection with the configured machine.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 129 / 190
190
B.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 re-
move 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 stating again the installation application.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 130 / 190
190
B.3 GoGlobal–UX license
The GoGlobal–UX X–Emulator for Microsoft 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.
B.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” configu-
ration, 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
B.3.3.
B.3.2 Retrieve License Servers Identity
Meaningful only for the license server machine(s).
When you have selected the license server machine(s), for each of them you have to retrieve the machine
identity by executing the following commands:
a) Log in as root on the machine.
b) Get the hostname of the current machine:
..,sys,root # uname –n [Enter]
c) Get the FLEXlm host ID of the current machine:
..,sys,root # /opt/graphon/bin/lmhostid [Enter]
The obtained data will be used in a successive phase of the license request activity.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 131 / 190
190
B.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 the following URL:
http://www.graphon.com/support/license.shtml
The following window will appear:
Figure 29. GraphOn License WEB Page
Click on “Go–Global Permanent Licenses” and the following registration form will appear:
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 30. GraphOn License WEB Page – Registration
ED 02
3AL 88888 AAAA 132 / 190
190
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 31. 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:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 133 / 190
190
Figure 32. GraphOn License WEB Page – License Data Entry
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 ALCA-
TEL USE FOR RESALE” document if present)
– Host Name (see the paragraph B.3.2)
– Host ID (see the paragraph B.3.2)
Now if you have the “Three Redundant License Servers” configuration you have to set “YES” in the box
close to the label “Are you using redundant servers?”, and fill in the three couple of information: Host-
name and Hostid with the data of each license server.
and click on Get License button to continue.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 134 / 190
190
Figure 33. GraphOn License WEB Page – License Output Example
Put the showed data in the license file of the license server machine (see the paragraph B.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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 135 / 190
190
B.3.4 GoGlobal–UX authorization procedure
GraphOn Corp. provides both permanent or demo license, hereafter some information to help you to con-
figure the GoGlobal–UX license files and daemons.

B.3.4.1Permanent License
GoGlobal–UX permanent licenses are provided as network floating point, that meas you have to pro-
mote one or three machines a License Server and all the other will be License Client.
To be able to use them you have to perform the following actions:
1) Store the authorization key in the license file.

2) Configure the license servers machine(s).
3) Start the license server daemons.
4) Configure license client system(s) (if any)
B.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
B.3.3 at page 132) 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:
1AA 00014 0004 (9007) A4 – ALICE 04.10
SERVER host_c 839dc26

to:
SERVER host_c 839dc26 27001
ED 02
3AL 88888 AAAA 136 / 190
190
B.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 li-
cense on the network.
B.3.4.1.2.1 Configure license_server.dat file
An Alcatel 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, includ-
ing 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 Go-
Global–UX stat–up.
To declare the license server machines you have to create the file “/opt/graphon/etc/license_servers.dat”
and fill in it with the following syntax:
SERVER <host> <port>
Where: SERVER is a keyword
<host> means the hostname or the IP address of the license server
<port> is the IP port number stored in the license.dat file as fourth field of the line
starting with SERVER, if that field is blank 27000 have to be used.
Example: Use the command (as root):
..,sys,root # vi /opt/graphon/etc/license_server.dat [Enter]
create the file so that it contains the following data:
SERVER host_c 27001

SERVER host_d 27001
SERVER host_e 27001
Save typing :x! and [Enter].
B.3.4.2Start License Server and GraphOn Daemons
When both license.dat and license_server.dat files have been properly configured on all the License Ser-
ver machine(s) you can proceed with the daemon start–up.
Because hp–ux start–up launch both License and GraphOn Daemons, it is advisable to execute the dae-
mon stop before. The entire procedure will be:
...,sys,root # /sbin/init.d/goglobalux stop [Enter]

...,sys,root # /sbin/init.d/goglobalux start [Enter]
When the daemons will be started on the single license server on at least two license server nodes for the
three redundant configuration, you will be able to open a GoGlobal–UX 2.0 session from any PC to the
1AA 00014 0004 (9007) A4 – ALICE 04.10
license server machine.
ED 02
3AL 88888 AAAA 137 / 190
190
B.3.4.3Configure License Client System(s)
To be able to access the hp–ux 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–ux 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.
B.3.4.3.1 Verify License Server Connectivity
Before starting the client machine configuration you have to verify the license server machine(s) connec-
tivity, the easiest way to do it is try a telnet to any license server host name:
..,sys,root # telnet <Hostname> [Enter]
where <Hostname> is the name of the remote license server machine(s).
– If the server answer with the login request, well that means the license server name is registered in
the host name repository, and the system is active and reachable through network. Press CTRL–D
and exit. The following message will be displayed:
Connection closed by foreign host
– Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
• <Hostname>: Unknown host

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 by using scNMmng
(see paragraph 3.6 at page 56 for more information). When the license server hostname will
be present in the host name repository retry telnet command.
• telnet: Unable to connect to remote host: Network is unreachable

Means the Default Gateway is not defined or is not able to route to destination. If you do not know
name and IP address of the network default gateway refer to the network administrator if any.
Otherwise If you know them, you can try to solve this problem checking and modifying with Sy-
stem AdMinistration tool (SAM) the system configuration:
..,sys,root # sam [Enter]
– Double–click on “Network and Communications” then “Hosts” and “Local Hosts File”
icons.
– In the upper left corner at label “Default Gateway:” is show the current default gateway set.
• If “None Specified” is shown, that means no default gateway is set.
• If IP address and the name are shown, check it them are referring the right machine.
If the configuration is not correct you can change it by:
• Select on the top–down menu “Actions” –> “Configure Default Gateway”
• Fill the “Configure Default Gateway (<hostname>)” window fields with your default
gateway IP address and (optionally) its name. Then click on the “OK” button to start
the configuration.
– At the end, select on the top–down menu “File” –> “Exit”.
– Then select on the top–down menu “File” –> “Exit SAM” to finish.
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
telnet: Unable to connect to remote host: Connection timed out

Means the license server is down or any network problem does not allow the communication
with it. Refer to the network administrator.
ED 02
3AL 88888 AAAA 138 / 190
190
B.3.4.3.2 Verify License Daemon on Server
When the license server machine(s) are reachable, you can also verify on each one of them if the license
daemons are running on these machine(s). this can be done with the following procedure:
N.B. This check can be done only if the license server machine(s) are already configured.
..,sys,root # export LM_LICENSE_FILE=27001@<Hostname> [Enter]

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

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

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

host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges: (Total of 2 licenses available)
N.B. The shown output is related to a three redundant server configuration, if you have a single li-
cense 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 ser-
ver them selves.
B.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 ma-
chine 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 139 / 190
190
B.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)
B.3.4.3.4 Re–Start the GraphOn Daemons
Because hp–ux 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.0 session from any PC to the this machine until
at least one license is available on the servers.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 140 / 190
190
B.3.5 Add a new license(s)
Sometimes in the system live it is necessary to increase the number of users, that means also the number
of concurrent session have to be increased. To add a new license on a running the license server machine
without close the current open interfaces, you have to proceed this way:
Do not mix permanent floating authorization key with demo one in the same file!
a) Buy the GraphOn license(s).
a) 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 authori-
zation key requested for the license servers already see in the paragraph B.3.4.1.1 at page 136. You
can see the server lines have the same values in the third field that means the same host ID.
#
#
#
# port 27001.
#
#
#
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
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 141 / 190
190
b) 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 in-

cluded.

..,sys,root # vi /opt/graphon/etc/license.dat [Enter]
1) Move to last line in file and insert the INCREMENT line(s). For example, if you have the authori-
zation key shown at page 136 active on the system, and receive from GraphOn the one shown
at page 141, the resulting file will be:
#
#
#
# port 27001.
#
#
#
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
2) Save and exit vi file pressing [Esc] and typing :x! and [Enter].
c) 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.
B.3.5.1Demo Licenses
GoGlobal–UX 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 142 / 190
190
APPENDIX C HOW TO CREATE A NETWORK DEPOT
After the HP–UX11i installation it is possible to performed the rest of installation of software layered
products in unattended mode. This can be done devoting 2.2 Gbyte of a machine installed with OS–Conf
7.0.5 to create a depot with all the software included in the CD’s, then when the predispose script will ask
you for the source you, have to reply with the following depot address: <depot host>:/alcatel/SCDEPOT.
In fact OS–Conf 7.0.5 includes “scbuilddepot“ script that drives the depot building.
Login the devoted depot system as root user and enter the command:
...,sys,root # scbuilddepot [Enter]
The procedure will ask you to confirm your request by issuing the message:
========================================================================
OS–Conf Depot Builder
========================================================================
The depot copy requires 2 Gbytes extra space on disks
* Do you have enough space available [Y/N] :
If you have enough large disks replay with “y” , and the activity will start asking for the source media, the
only media supported is the CD–ROM, you can just change the default with another one. The default pro-
vided is the CD–ROM device used to install HP–UX.
* Enter the CDROM device [ /dev/dsk/c1t2d0 ] :
NOTE: Checking/Extending /alcatel for depot creation
If the current size of the partition mounted at /alcatel is not enough, new disk resources will be required
until reach the requested size. Here an example of the extension:
Analyze Mount Point:”/alcatel”

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


1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 143 / 190
190
Mount Point need 1536MB on /dev/vg00 (PVG0)
___________________________________________________________________________
Disks Selection
Mount Point: /alcatel

___________________________________________________________________________

___________________________________________________________________________
c0t5d0 4088 8/12.5.0 Pri_Boot _Main_ vg00
c0t6d0 2048 8/12.6.0 __Data__ _Main_ vg00
c1t4d0 2048 8/16/5.4.0 _(free)_ ______ __________
c1t5d0 2048 8/16/5.5.0 _(free)_ ______ __________
___________________________________________________________________________
Select Data Area (Main instance) dev name or [q] to quit: c1t4d0
When finally the file system mounted at /alcatel will be large to contain the depot the procedure will ask
you to introduce the first disk of the set:
* Please insert CD SWP–OSCONF–V7.0.5 – 1/4 into the drive

and press [Enter] when ready
Insert the CD and press return when the CD–ROM driver led will stop blinking. The procedure will ask you
again for all the disks of the set.
When scbuildepot had finished to copy, you have to add the contents of SWP–OSCONF–V7.0 ADD1 CD,
by follow this procedure:
a) Check the available space on /alcatel/SCDEPOT by entering the command:

...,sys,root # bdf /alcatel/SCDEPOT[Enter]
b) If the value shown in the “avail” column is lower then 310000, you have to enlarge the file system.
Be careful because the command can ask you to reboot the system, in this case: shutdown
all the running application and enter the command “reboot”, at the end of scextendfs execu-
tion.
...,sys,root # scextendfs /alcatel 330[Enter]
c) Insert SWP–OSCONF–V7.0 ADD1 in the driver and mount it by entering:

d) Copy the software from CD to the depot entering:

...,sys,root # swcopy –x enforce_dependencies=false \
–s /SD_CDROM \* @ /alcatel/SCDEPOT[Enter]
When the depot construction will be completed, you can predispose any Network Management System
in you local area network by choosing entering: <depot hostname>:/alcatel/SCDEPOT as shown in the
“Software Layered Installation Predisposal” paragraph 4.4.5.3 at page 87.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 144 / 190
190
APPENDIX D PRINTER CONFIGURATION
To configure the printer you have to use hp hppi script. This script configures the printer on the system
in order to allow the download of the software through the network, and also configures the spooler and
the printer queues on all the system declared.
This instaction is useful only for HP Printers.
In this chapter two printer configuration aspects are considered. First case how to configure a printer spool
queue within the local spooler. The second one how to configure a printer to retrieve its configuration from
local machine.
To be able to perform the printer configuration you must know some information
Item Data Description Queue Boot
Name Name is the up to 8 charac-

ters string assigned to
printer by Customer Net-
work administrator(1).
IP Address IP Address is the IP net-

work address assigned to
printer by Customer Net-
work administrator.
Default Queue Yes No Is this the system default

queue? (it is suggested to
set the first defined queue
as default)
Banner Page Yes No Would you like to issue the

banner page at the begin-
ning of any print job?
LAN Hardware Address LAN HA is the card hard-

ware address also known
as MAC(2).
Table 10. Printer Configuration Data Requested.
Notes:
1) It is advisable to declare the printer name as external node with scNMmng.
2) The LAN hardware addres have to be retrieved from the printer itself. Refer to the printer instal-
lation guide and/or operator handbook to know how to get the hardware address. It is usually
shown as six couple of hexadecimal figures column separted like: 00:30:6E:08:AF:6F
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 145 / 190
190
D.1 Configure a Printer Queue within Local Spooler
This section shows how to configure a HP printer already active in you network. This is the most useful
hint to configure a network printer. The printer availble today can be configure from the font panel, and you

just need to create a spool queue.

To create the printer spool queue you have to log the system as root user. and enter “hppi” command:
..,sys,root # hppi [Enter]

****************************************************************
*****] ****
**** ] **** JetDirect Printer Installer for UNIX
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** M A I N M E N U
***** ] ****
****** ] **** User: (root) OS: (HP–UX B.11.11)
I N V E N T
****************************************************************
1) Spooler Administration (super–user only)
2) JetDirect Configuration (super–user only)

– TCP/IP configurable parameters
3) Diagnostics:
– diagnose printing problems
?) Help q) Quit
Please enter a selection (q – quit):

Enter “1[Enter]” to select the “Spooler Administration item”.
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** Spooler Administration
***** ] ****
I N V E N T
****************************************************************
Spooler:
1) Add printer to local spooler
2) Delete printer from local spooler
3) Modify existing spooler queue(s)
4) Install New Model Script
5) Remove Model Script
?) Help q) Quit
1AA 00014 0004 (9007) A4 – ALICE 04.10
Please enter selection:

Enter “1[Enter]” to add the printer to the local spooler.
ED 02
3AL 88888 AAAA 146 / 190
190
If you have already declare the printer name in the /etc/hosts file, directly of via scNMmng you can enter
the printer node name, otherwise you have to enter the IP address. This second choice has the disadvan-
tage that you have to review the printer configuration in case of printer IP address changes:
Enter the network printer name or IP address (q – quit): <name>|<IP Ad.>[Enter]

The latest model script can be downloaded from the web before creating
any queue. This can be done by enabling Realtime Model Script Update. The
Realtime Model Script Update can be Enabled/Disabled from the diagnostics
menu.
Do not enable the Realtime Model Script Update by replying just [Enter] to the next question:
Do you want to Enable Realtime Model Script Update(0–Enable, default–Dis-

able): [Enter]
In any case, the procedure continue as follow:
The following is a list of suggested parameter values for this

queue. You may change any settings by selecting the corresponding
non–zero numbers. The values will be used to configure this queue
when ’0’ is selected.
To abort this configuration operation, press ’q’.
Configurable Parameters: Current Settings

–––––––––––––––––––––––– ––––––––––––––––
1) Lp destination (queue) name: [<Printername>_1]

2) Status Log [(No Log)]
3) Queue Class [(Not assigned)]
4) Default Queue [NO]
5) Additional printer configuration...
Figure 34. Printer Characteriscs Menu
Select an item for change, or ’0’ to configure (q – quit): 1 [Enter]
Enter “1[Enter]” to change the LP queue name:
Currently used names:

––––––––––––––––––––
(no queues are configured)
Enter the lp destination name (default=<Printername>_1, q – quit):
Enter the name you want to assing to the queue followed by [Enter], usually is the printer name itsef.
The item shown in the “Current Settings” column will be updated and “Printer Characteriscs Menu”
(Figure 34. ) will be issued again.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 147 / 190
190
If you are configuring the first printer queue or you want to define this one as the new default queue, enter
“4[Enter]

If you want to set the banner page issue, at the next “Printer Characteriscs Menu” (Figure 34. ) prompt
enter “5[Enter]”.
The following submenu will be shown on the dispaly, enter “5[Enter]” again:
The following is a list of suggested parameter values for this printer.
To abort this operation, press ’q’.
Configurable Parameters: Current Settings

–––––––––––––––––––––––– ––––––––––––––––
1) Model Script: [net_lj4x]

2) Default Printing Language [AUTO]
3) Job Recovery [ON]
4) True End–of–Job [ON]
5) Banner Page [OFF]
6) PostScript Level [Level 1]
Select an item for change, or q when done: 5 [Enter]
The “Banner Page” current setting will be change from [OFF] to [ON] and the submenu issued again. Enter
“q[Enter]” to leave the submenu.
Select an item for change, or q when done: q [Enter]
The “Printer Characteriscs Menu” (Figure 34. ) will be proposed again, enter “0[Enter]” to finally create the
printer queue.
Depending by the “System Spooler” status one of the one of the following messages will be issued:
When the spooler is not running:

The spooler is already not running in the system!
It will not be switched on after the configuration
When the spooler is running:

Ready to shut down the spooler and configure the new print queue.
The spooler will be running again after the configuration is done.
WARNING: If there are jobs currently being printed, and the page count is
enabled (i.e. when True End–of–Job is turned on), this shutdown and rerun
of the spooler may result in incorrect page count.
If the spooler is running before enter “y[Enter]” check with “lpstat –t” command that there is no print job
1AA 00014 0004 (9007) A4 – ALICE 04.10
queued.
OK to continue? (y/n/q, default=y) y [Enter]
ED 02
3AL 88888 AAAA 148 / 190
190
If the spooler is not running the following message will be issued to remind you to start–up the spooler
to have the print queue operational (see D.1.1 at page 150).
WARNING : The spooler is not running!

To print, turn on the spooler (lpsched)

hppi returns to the “Spooler Adminstration menu”, enter “q[Enter]” two times to exit the procedure.
Finished adding ”<Printername>” to the spooler.
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** Spooler Administration
***** ] ****
I N V E N T
****************************************************************
Spooler:
1) Add printer to local spooler
2) Delete printer from local spooler
3) Modify existing spooler queue(s)
4) Install New Model Script
5) Remove Model Script
?) Help q) Quit
Please enter selection: q [Enter]
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** M A I N M E N U
***** ] ****
I N V E N T
****************************************************************

3) Diagnostics:
1AA 00014 0004 (9007) A4 – ALICE 04.10
?) Help q) Quit
Please enter a selection (q – quit): q [Enter]
ED 02
3AL 88888 AAAA 149 / 190
190
D.1.1 Start the System Spooler
The hp–ux system spooler is automatically started during at system start–up time only when there is at
list a print queue defined. When you define the first queue it is usually not running, so to allow the correct

print activities you have to munually start it by entering the follwoing command as “root” user:

..,sys,root # lpsched[Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 150 / 190
190
D.2 Configure Printer Booting from Local System
This printer configuration allow to remotely load the printer configuration at printer power–on time. If you
decide to use this method it is advisable to choose two hp–ux system configured to set–up the printers,
and keep the two system database alligned.

To perform this job you have to log in the system as root and enter the command:
..,sys,root # hppi [Enter]
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** M A I N M E N U
***** ] ****
I N V E N T
****************************************************************

3) Diagnostics:
?) Help q) Quit
Please enter a selection (q – quit):
Enter “2[Enter]” to select the JetDirect configuration.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 151 / 190
190
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18

**** ] ] ] ] ****

**** ] ] ]]]]] **** JetDirect Configuration Menu
***** ] ****
I N V E N T
****************************************************************
Printer Network Interface:
1) Create printer configuration in BOOTP/TFTP database
2) Remove printer configuration from BOOTP/TFTP
3) Check Bootp and TFTP operation (super–user only)
– OR –
Telnet Configure JetDirect:

4) Set IP Address locally
(within your local subnet – router)
5) Open Telnet Session to JetDirect Card
?) Help Me Decide q) Quit
Please enter selection:
Enter “1[Enter]” to create configure the printer for booting from this node.
You will be asked a series of questions. After all of the questions have been answered, the responses are
used to create an /etc/bootptab entry, and an optional configuration file. This configuration file is retrieved
by the network printer with TFTP after it receives the BOOTP response.
These responses apply to all questions:

”q” – returns you to the next higher level menu
”?” – prints help text
<return> – skips optional parameters or selects the default value
Enter the printer’s LAN hardware address: <Mac Address> [Enter]
Enter the network printer name (q – quit): <Printer Name> [Enter]
Enter IP address: <IP Address> [Enter]
Add <Printer Name> and <IP Address> to /etc/hosts? (y/n/q, default=y): y

[Enter]
Printer name and IP address have been added to /etc/hosts. If your /etc/
hosts file is updated automatically from a master source, add the name and
IP address to your master source after the configuration is complete.
Following are optional parameters you may set for JetDirect. Select any
1AA 00014 0004 (9007) A4 – ALICE 04.10
non–zero numbers to make the changes. The settings are used to create a
BOOTP/TFTP database when ’0’ is selected. To abort the operation, press
’q’
ED 02
3AL 88888 AAAA 152 / 190
190
Other optional parameters:
–––––––––––––––––––––––––
1) Set printer location (uses tftp)
2) Set printer contact (uses tftp)
3) Set subnetmask
4) Set gateway
5) Set syslog (uses tftp)
6) Change idle timeout (uses tftp)
7) Create access list (up to 10 names). (Default: all allowed).
(uses tftp)
8) Other SNMP parameters: (uses tftp)
(GET/SET community name, trap and community name, authentication
trap)
9) Set HP JetDirect lpd banner page
Enter the printer location (q – quit): <Location name> [Enter]
...

(configuring) ...
Completed creating BOOTP/TFTP configuration database for <Printer Name>.
Tftp service is also used to boot up JetDirect. Make sure /var/adm/in-

etd.sec allows JetDirect’s IP to accesstftp service on this node.
Please wait...
(testing, please wait) ...
Testing BOOTP with 080009000000...:
RESULT: Passed BOOTP test 1 with 080009000000.
......
BOOTP/TFTP has been verified functional.
Configuration data is now in place. The next test is to ping the

printer for the IP name you just assigned it. To continue the test,
you MUST do the following so that the printer can configure itself
with the configuration data:
Power cycle the printer. (operator must do a power cycle : power off – power on)
Wait until the printer finishes the self test.
(Note: It may take 20 sec to 1 min for a token ring HP
JetDirect interface to finish the configuration.)
Press the return key to continue the test.
If you are not ready for the next test (for example, the IP name has
not taken affect in your DNS server), press ’q’ to return to the confi-
guration menu now.
Do you want to send test file(s) to this printer (y/n, default=n)? y [Enter]
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 153 / 190
190
This test is using test files to demonstrate that data bytes can be
transmitted across the HP JetDirect interface setup. As long as a few
characters print out, the test is successful.
The printer must be ready, i.e. online and not printing anything.

The following types of test files can be sent to the printer:

1) text file (if printer is in PCL or AUTO mode)
2) PostScript file (if printer is in PS or AUTO mode)
3) HP–GL/2 file (if it is a HPGL/2 plotter)
4) User supplied file
Which one should be transmitted? (1/2/3/q, default=1) 2 [Enter]
===============================================================
Sending a test file to <Printer Name> ...
Result: The file has been successfully sent to <Printer Name>. Check
output!
===============================================================
Press the return key to continue ... [Enter]
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** JetDirect Configuration Menu
***** ] ****
I N V E N T
****************************************************************
Printer Network Interface:

1) Create printer configuration in BOOTP/TFTP database
2) Remove printer configuration from BOOTP/TFTP
3) Check Bootp and TFTP operation (super–user only)
– OR –
Telnet Configure JetDirect:

4) Set IP Address locally
(within your local subnet – router)
5) Open Telnet Session to JetDirect Card
?) Help Me Decide q) Quit
Please enter selection: q [Enter]

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 154 / 190
190
****************************************************************
*****] ****
**** ]]]]] ]]]]] **** Version E.10.18
**** ] ] ] ] ****
**** ] ] ]]]]] **** M A I N M E N U

***** ] ****
I N V E N T
****************************************************************

3) Diagnostics:
?) Help q) Quit
Please enter a selection (q – quit): q [Enter]
..,sys,root #
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 155 / 190
190
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
190
3AL 88888 AAAA
156 / 190
APPENDIX E BACKUP AND RESTORE
The OS–Conf includes a backup/restore function. This function allows to make a security archive tape set
of the entire system, or a specified volume group, reducing the down time of the system where it is possible.
The backup function can be executed in two ways:
– Full backup of the entire system.
– Single volume group back.
Both of them allow the on–line execution, and are integrated with the other OS–Conf feature such as disk
mirror management.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 157 / 190
190
E.1 Full disks backup/restore
The target of the procedure is: provide an easy tool to allow the backup and restore of the complete disks
contents (including the disk partitioning), to allow the system recovery in case of disk failure or data corrup-

tion that does not allow the HP–UX to boot again from disk.

Basically the procedure use three HP–UX tools:
1) fbackup – Backup tool included in the HP–UX 11.11 Core

2) frecover – Recover tool included in the HP–UX 11.11 Core
3) Ignite UX – Add on HP tool for installation and recovery
The tools reference versions are:

HP–UX 11i 11.11
Ignite UX B.3.6.82 for HP–UX 11.11
This means the scbackup behavior is not guarantee with different version.
E.1.1 Full Backup Strategy
The system backup is always done using two tape cassette sets:
a) The fist tape set is the Ignite Recovery Tape (IRT). It is created on–line by Ignite UX with a reduced
HP–UX and allows the boot from tape. Usually the IRT is done using just one 4 Gbyte tape.
The contents of IRT depends also by the Logical Volume Management (LVM) configuration, it the
Physical Volume Group (PVG) are defined, only the disk beloging to PVG0 will be stored in the IRT,
this is done this way because Ignite does not manage mirror disk nor PVG. This approach has been
implemented to be able to build again the same configuration in the restore.
b) The second tape set is created by “fbackup” tool with the entire disk contents. This activity can be
carried out on–line or off–line depending by the system configuration and status. These are the condi-
tions to be able to perform the on–line full backup:
1) If entire file system is mirrored.

2) If there are no stale phisycal extent.
3) If there is no Virtual Array in configuration.
This tape set can be require more than one tape.
N.B. If you have both DAT and DLT tape device, it is allowed to create the two tape sets using different
type of tape cassettes, such as DAT tape for IRT and DLT for fbackup.
But it is NOT allowed to mix different type tape cassettes in the same tape set.
The procedure manages both volume group configuration provided for Alcatel TNM Applications:
– Single Volume Group

Multiple Volume Group
The Single Volume Group configuration has all disks in configuration defined in the same HP Logical Vol-
ume Manager (LVM) volume group (VG), where there are also the HP–UX system partitions.
The Multiple Volume Group configuration foreseen a different VG for each disk (vg01, vg02, vg03, etc.)
with the exception of the Mirror UX configuration where each VG must contains two disks.
Within the Alcatel TNM environment it is RECOMMENDED to use this tool in together with the Alcatel Ap-
1AA 00014 0004 (9007) A4 – ALICE 04.10
plication Backup feature, because often there is application data on different systems that have to be con-
sistent each other.
N.B. The full backup usage is forbidden with 1359HA OS–Cluster environment.
ED 02
3AL 88888 AAAA 158 / 190
190
E.2 Single Volume Group Backup
The single volume group backup has been introduced to allow the backup when there are 1359HA OS–
Cluster System configuration.
The 1359HA OS–Cluster specific volume group management does not allow to perform the full backup
in the usual way, because them are shared between two systems, and their Logical Volume Manager
(LVM) configuration must be managed by 1359HA OS–Cluster scripts.
Single volume group backup feature is also due to the Virtual Array (VA7110) backup method, in fact there
is a specific feature of VA7110 to make an on–line copy of any Logical Unit (LUN), this mechanism allow
the on–line backup of any information stored with the VA7110, but require an extra space on device equal
to the amount of space that have to be backup at once.
Basically the procedure uses the following HP–UX tools:
1) fbackup – Backup tool included in the HP–UX 11.11 Core

2) frecover – Recover tool included in the HP–UX 11.11 Core
3) Ignite UX – Add on HP tool for installation and recovery
4) CommandView SDM – Virtual Array Command
The tools reference versions are:
HP–UX 11i 11.11

Ignite UX B.3.6.82 for HP–UX 11.11
CommandView SDM V1.06.00
This means the scbackup behavior is not guarantee with different version.
E.2.1 Single Volume Group Backup Strategy
The behavior of the single volume group backup is more flexible, but more complex than the full backup
one. Within the single VG backup it is possible to distinguish two different VG types:
1) hp–ux system volume group (vg00).
2) Data volume group (different than vg00)
The backup of the system volume group (vg00) is perform with the full backup approach, it is done with
two tapes (IRT and fbackup) to be able to rebuitd a minimum hp–ux system and the data stored inside.
Instead the data volume group backup is related only the data.
As result of this policy is the single volume group backup require a number of tapes equal to the number
of volume group plus one, and all of them have to be properly labeled to prevent misusage.
N.B. The manual Single Volume Group Backup usage is forbidden. It must be integrated with-
in 1359HA OS–Claster Backup feature.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 159 / 190
190
E.3 Restrictions
E.3.1 Ignite Recovery tape restrictions

The Ignite Recovery Tape (IRT) has some restrictions with using the DLT tape driver.
– DLT MUST BE attached to HP 9000 Enterprise servers via Fast–Wide Differential interface cards.
– DLT boot WILL NOT work when attached via single–ended SCSI.
– DLT boot IS NOT supported for systems that use NIO Fast–Wide Differential SCSI cards (Part num-
ber 28696A).
The matrix below explains systems (by class) along with the bus types required for DLT to be recognized
as a bootable media device.
Table 11. Bus types required for DLT to be recognized as a bootable media
BUS SCSI Interface Card DLT boot support Notes

CLASS
?
HSC A2969A FWD yes see 1 ) and 2 )

K–Class
NIO A28655A SE, A28696A FWD no
HSC A4107A FWD yes see 2 )

D–Class Core no
EISA no
HSC A3644A FWD no

T–Class
NIO A28655A SE no
N–Class PCI FWD yes
L–Class PCI FWD yes
V–Class PCI A4800A FWD yes see 4 )
E–Class NIO A28655A SE, A28696A FWD no see 3 )
G–Class NIO A28655A SE, A28696A FWD no see 3 )
H–Class NIO A28655A SE, A28696A FWD no see 3 )
I–Class NIO A28655A SE, A28696A FWD no see 3 )
Notes:
1) This class system has two internal bus types, HSC and NIO. DLT is only bootable from the HSC
bus.
2) The HSC and GSC busses are the same busses. These terms are used interchangeably.
3) NIO and HP–PB refer to the same bus.
4) IPR (Independent Peripheral Release). A firmware upgrade (at least 4.3, product number
1AA 00014 0004 (9007) A4 – ALICE 04.10
B6044AA) is required to enable tape boot for the V–Class. The release date for firmware upgra-
de version 4.3 is September 1998. Contact your HP representative about required firmware
upgrades.
ED 02
3AL 88888 AAAA 160 / 190
190
E.3.2 1359HA OS Cluster Support
The OS Cluster environment is supported only with Single Volume Group in conjunction with 1359HA OS–
Cluster backup feature.
E.3.3 Mirror Disk configuration rebuild
The restore procedure after restoring the data it will inform the user if the system was mirrored at the bac-
kup time, the mirror rebuild is not managed directly by the restore procedure, but it must activated sepa-
rately.
For systems protected with Mirror/Disk UX, it is possible to proceed with the full online disk backup by using
the “scbackup” script, after the disk restore via “screstore” script the “scmirrorfs“ script can be invoked to
rebuild the mirror configuration, this script will require to specify the mirror disks to be used (refer to appen-
dix E.5.3 at page 180).
E.3.4 Restriction on Console
The fbackup is executed in single user mode during the HP–UX boot phase, but it is VERY IMPORTANT
to know that switching off the console terminal or disconnecting the Web console during the fbackup
execution, the fbackup itself will be interrupt, and the backup will be not completed.
E.3.5 Required disk space
The Ignite UX tool require 32Mbyte free in the file system where /var directory is located.
E.3.6 Compatibility
The ’scbackup–screstore’ version 2.0 in not compatible with the previous version of the Alcatel
backup–restore software, so the tapes produced with old versions cannot be managed by the new one.
Pay attention to label correctly the new tapes and to keep them separated from the previous.
E.3.7 Restriction on Backup
The system you want to backup may have volume groups not active or logical volumes not mounted; these
will not be managed by the procedure and you will be informed by warning messages.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 161 / 190
190
E.4 FULL BACKUP
This chapter shows how to perform the backup of the entire disk structure and contents by using the
scbackup procedure.

The script is design to be executed in following the phases showed below:
a) Create the Ignite recovery tape (IRT).
b) Perform backup
On line:
1) Split the mirror disk, creating a off–line copy of the entire system.
2) Perform the backup of the off line copy
3) Merge back the off–line copy in the mirror disk configuration.
Off line:
1) Prepare HP–UX system to execute standard backup at HP–UX Run Level 2.

2) Perform the backup during the HP–UX system reboot.
3) Reboot the system to restore it in service.
E.4.1 Start the “scbackup” script
To activate the scbackup script and execute the backup of your environment you have to proceed as follow:
a) Login as root.
b) Insert the tape cassette into the tape device.
c) Start the procedure by entering:
..,sys,root # scbackup [Enter]
The scriot foreseen a timeout on the tape cassete request, the default value is 60 minutes, if you want
to have a different timeout period or inibit any timeout you have to use the “–t“ option.:
....sys,root # scbackup –t 180 To increase the timeout to three hours.

...,sys,root # scbackup –t 0 To disable the timeout.
d) The script will ask you to enter the HP–UX device file for the IRT to be able to identify the tape driver
you want to use by issuing the request:
Enter tape device for Ignite <default=<tape_device>>:
Enter the HP–UX file associated to the tape device (i.e.: /dev/rmt/0m) you want to use for the IRT tape
set and press [Enter], or just press [Enter] to select the shown file (<tape_device>).
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 162 / 190
190
E.4.2 Create the IRT
Now we get into the IRT creation phase. The script issues the following message to ask you to insert a
tape cassette into the tape driver.
Please load Tape with label Ignite on device: </dev/rmt/0m>

and press Enter when READY
You have now to insert an unprotected tape cassette waiting until the drive light stops blinking.
The tape cassette MUST NOT BE write–protect !
When the device light will be stable on, press [Enter] key to start the activities on the tape.
The IRT creation can take up to 40 minutes. (20 minutes with a HP9000 R380 Server with a DDS2 tape
driver).
The output of the execution will shown on the terminal.
Any error detected will abort the execution.
When the IRT will be completed without errors, the following message will be shown:
**************************************************
Remove Tape media and recommended label is:
hosta – Ignite Bootable – 01–Dec–2003 14:04
Please label the tape as suggested by the message.
ATTENTION: The root password saved into IRT has to be used at the recovery time. Do
not forget it!
E.4.2.1IRT Integration Data
To have a better view of the backuped system configuration it is required to printout some information and
attach them to IRT.
The required information are issued by the following command:

• ...,sys,root # vgdisplay –v [Enter]
• ...,sys,root # scextendfs –i [Enter]
Print the output of these two commands and store it with the IRT, them can be useful in case of disk failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 163 / 190
190
E.4.3 Backup the entire disks contents
When the IRT creation is completed, the scbackup goes to the next query require entering the HP–UX
device file for the fbackup, by issuing the message:

Enter tape device for Fbackup <default=<tape_device>>:
Enter the HP–UX file associated to the tape device (i.e.: /dev/rmt/0m) you want to use for backup the
entire disk contents and press [Enter], or just press [Enter] to select the shown file (<tape_device>).
After this question it determinate if there are the condition to perform the on–line backup.
E.4.3.1Online full backup
This procedure checks if the mirror software is installed on the system, in case of positive result it evaluates
if a full mirrored/stable disks configuration is present and activates the split of the logical volumes to pre-
pare the data for the online backup from the mirrored disks.
**************************************************
Verificaton of FULL MIRROR
Checking correct configuration of Logical Volumes mirror ...
In case of compatible system configuration, It is suggested to stop the Alcatel TNM applications before
to continue as reported at follows:
During the splitting phase, in order to preserve the data integrity, it is required to shut-
down of the Alcatel TNM applications.
MIRROR verificaton End Successfully
*****************************************************************************
To preserve data integrity and avoid problems you should:
STOP ALL APPLICATIONS
before start backup.
*****************************************************************************
*****************************************************************************
NOTE: If you need to stop anything, do it before answer ’YES’ to
the next question.
*****************************************************************************
Do you want continue with backup operation (y|n) ? : y
When you answer “y” the logical volumes split will be executed.
If the split succeeds the following message will inform you to reactivate the Alcatel TMN applications and
the full backup will be started.
*****************************************************************************
ATTENTION: NOW you can RESTART APPLICATIONS !!!
*****************************************************************************
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 164 / 190
190
It is necessary to attend the fbackup execution, because of it can ask for more tape cassettes, and when
it requires a new cassette you have to remove the current tape and insert a new unprotected one. The
fbackup by default will wait up to 1 hour for the new tape cassette after issuing the message:
Please MOUNT TAPE Volume <x>

where <x> means the tape cassette number.
If the cassette will be not replaced in 1 hour or you insert a wrong tape the fbackup will fail.
N.B. The default timeout can be changed using the –t option on scbackup commad.
N.B. Fbackup DOES NOT CHECK if you are inserting the IRT one, in this case the IRT will be de-
stroyed.
If everything goes well you will recevive the following output:
**************************************************
SPLIT procedure
Start split operation for Logical Volume /dev/vg00/lvol3
Check FS on splitted Logical Volume
Mount FS on backup directory /sconlinebackup
...
SPLIT End Successfully
*****************************************************************************
ATTENTION: NOW you can RESTART APPLICATIONS !!!
*****************************************************************************
**************************************************
ONLINE BACKUP process
**************************************************
Preparation Tape media for BACKUP
Fbackup tape devices /SCINSTALL/data/backup/fbackup_tape
Backup Tape check : Please MOUNT TAPE Volume 1
01–Dec–2003 14:28
Execute Backup : Start Backup ...
Execute Backup : End Successfully
*****************************************************************************
DATA ARE SUCCESSFULLY BACKUPED
*****************************************************************************
**************************************************
hosta – Fbackup Volume x of n

1AA 00014 0004 (9007) A4 – ALICE 04.10
01–Dec–2003 14:26 – Content: Full backup
**************************************************
ED 02
3AL 88888 AAAA 165 / 190
190
After the full online backup the backup logical volumes will be reduced.
**************************************************
REDUCE process

REDUCE process activated on backup Logical Volumes
This operation takes a while, please wait ...
REDUCE End Successfully
*****************************************************************************
ONLINE BACKUP End Successfully
*****************************************************************************
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 166 / 190
190
E.4.3.1.1 Online Full Backup Error Management
If problems occour during execution of sconlinebackup, the disks configuration will be automatically re-
stored. In case of errors during the logical volumes split operation, the user can decide to continue with
standard backup or to stop the procedure in order to analyse the problem, make the corrections and run
again the command sconlinebackup (refer to paragraph E.4.3.1.1.4 for an example).
The sconlinebackup procedure can also run alone just if a new IRT is not required. In this case it will show
the following output:
**************************************************
sconlinebackup (Backup–Restore Ver. 2.0)
**************************************************
Environment verification
*****************************************************************************
ATTENTION: ’sconlinebackup’ procedure can be invoked directly
just if your SYSTEM IS NOT CHANGED since the last
creation of the IRT (Ignite Recovery Tape).
*****************************************************************************
*****************************************************************************
If you have doubt or if you need to create a new IRT,
answer ’NO’ to the next question and use the ’scbackup’
command instead of ’sconlinebackup’.
*****************************************************************************
Do you want continue with backup operation (y|n) ? : y
*****************************************************************************
NOTE: You choose to proceed with backup.
The last produced IRT MUST BE VALID.
*****************************************************************************
If the user decides to proceed, the script will work as previously described in this chapter.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 167 / 190
190
E.4.3.1.1.1 Full Mirror faults
The check on the system full mirror can fails for two main reasons:

– logical volumes are not mirrored, in this case a message like the one at follows will be shown:

*****************************************************************************
WARNING: Logical Volume /dev/vg00/lvol13 not mirrored.
ALL Significant Logical Volumes must be mirrored.

*****************************************************************************
– logical volumes have the “stale” status, a message like the following will be shown:
*****************************************************************************
WARNING: Logical Volume /dev/vg00/lvol13 has status available/stale
This indicates problems in mirroring synchronization.

*****************************************************************************
The procedure skips the full online backup when it finds the first logical volume who doesn’t meet the re-
quirements and before continue with standard backup it will show the message:
*****************************************************************************
WARNING: MIRROR verificaton End with warnings
*****************************************************************************
*****************************************************************************
NOTE: ONLINE BACKUP NOT SUPPORTED by this system
*****************************************************************************
E.4.3.1.1.2 System crash
As you can realize this process is quite critical because in case of crash during the online backup there
is the necessity to recover the original disks’ configuration. For this purpose an automatic recover proce-
dure will be activated at the system startup in case of failure (sconlinebackup_recover).
E.4.3.1.1.3 Logs
There are three log files where you can check in case of errors to identify the reason of the fault:
– /var/adm/syslog/sconlinebackup.log records information related to the SPLIT phase.
– /var/adm/syslog/sconlinebackup_recover.log contains info about the REDUCE/RECOVER phase.
– /var/adm/syslog/fbackup.log keeps the full online FBACKUP information.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 168 / 190
190
E.4.3.1.1.4 Split problems
Problems should appear during the splitting operation, if the applications have not stopped, because a file
system check is activated on the splitted logical volume and it could find inconsistent state and uncorrect-
able errors. In this condition the backup procedure ends as reported at follows:
...
Start split operation for Logical Volume /dev/vg00/lvol7
Check FS on splitted Logical Volume
*****************************************************************************
ERROR: exit status 36 for command
’fsck –F vxfs /dev/vg00/lvol7backup’

*****************************************************************************
*****************************************************************************
ATTENTION: Recover process activated due to ERROR.
Error during data copy phase see:

/var/adm/syslog/sconlinebackup.log
*****************************************************************************
**************************************************
RECOVER process
RECOVER process activated on backup Logical Volumes

RECOVER End Successfully
*****************************************************************************
ERROR: during data COPY phase.
*****************************************************************************
Do you want continue with standard backup (y|n) ? : n
*****************************************************************************
ERROR: during data COPY phase
See ONLINE backup log: /var/adm/syslog/sconlinebackup.log
After correction run again procedure ’sconlinebackup’.
*****************************************************************************
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 169 / 190
190
E.4.3.1.1.5 Timeout expiration
If the user forget to mount the tape and the mount timeout expires, the process terminates with the mes-
sage at follows:

**************************************************
ONLINE BACKUP process
**************************************************
Preparation Tape media for BACKUP
Fbackup tape devices /SCINSTALL/data/backup/fbackup_tape
Execute Backup : ERROR: timeout expired for Mount Tape
*****************************************************************************
ERROR: DATA ARE NOT CORRECTLY BACKUPED
*****************************************************************************
02–Dec–2003 09:40 ERROR: timeout expired and Tape media was not mounted
**************************************************
**************************************************
REDUCE process
Start REDUCE process on backup Logical Volumes

REDUCE End Successfully
*****************************************************************************
ERROR: Online Backup ends with errors.
See FBACKUP log: /var/adm/syslog/fbackup.log
After correction run again procedure ’sconlinebackup’.
*****************************************************************************
The user shuold mount the tape and run again the sconlinebackup command.
E.4.3.1.2 Reduce problems
Normally the merge of the logical volumes works fine, but if it fails the disks mirroring will be faulty, to solve
this kind of problem you must check the log file for errors and run manually the sconlinebackup_merge
command.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 170 / 190
190
E.4.3.2Standard Full backup
Proceding with the standard full backup, in order to guarantee the contents of the files it is required to shut-
down of the Alcatel TNM applications and reboot the HP–UX system. Because of this it is necessary to
carefully schedule this activity.

The time required full backup depends by:
– Amount of the disk space used by files.
– Type of tape device.
– I/0 system.
The scbackup require to perform the shutdown–reboot immediately.
The procedure shows the messages at follows and it asks if the system is ready for the shutdown, if you
answer with “y” the system will reboot, if you answer “n” the backup will be aborted.
*****************************************************************************
ATTENTION: you can continue with standard system backup, but
this requires the system SHUTDOWN–REBOOT.
*****************************************************************************
*****************************************************************************
Applications is better already stopped before start shutdown,
do it before answer ’YES’ at the next question.
*****************************************************************************
*****************************************************************************
NOTE: If you answer ’NO’ at the question the backup will be aborted.
*****************************************************************************
Is system READY for execute standard backup with SHUTDOWN & REBOOT (y|n) ? :
If you decide to answer “y”, it is better to shutdown the Alcatel Application, also if the procedure will stop
the system with “shutdown –r” command.
If you decide to proceed the procedure asks to insert an unprotected tape cassette in the tape driver speci-
fied for the full backup issuing the following message:
**************************************************
Preparation Tape media for FBACKUP tool
Please load Tape with label Fbackup on device: </dev/rmt/0m>

You have to insert the tape cassette in the requested tape drive and press [Enter] when the drive will be
ready.
The following message will be issued by scbackup invites you to enter the grace time to allow the user
to logout.
Enter time for users to log off, before shutdown

1AA 00014 0004 (9007) A4 – ALICE 04.10
Enter time in SECONDS [decimal integer or ”now”] >
N.B. If you are performing the backup of a 1353SH Master, 1354RM IM, 1354NN IM, or the main Co-
Hosted system, it is advisable to ask also the user logged on the presentation to exit.
ED 02
3AL 88888 AAAA 171 / 190
190
After the specified time the system will be shouted down and rebooted.
During the HP–UX start–up the fbackup will be automatically started.

N.B. The fbackup foreseen to have the tape drive ready to write.

It is necessary to attend the fbackup execution, because of it can ask for more tape cassettes, and when
it require a new cassette you have to remove the current tape and insert a new unprotected one.
The fbackup by default will wait up to 1 hour for the new tape cassette issuing the message:
Please MOUNT TAPE Volume <x>
where <x> means the tape cassette number.
If the cassette will be not replaced in 1 hour or you insert a wrong tape the fbackup will fail.
N.B. The default timeout can be defined using the –t option on scbackup commad.
N.B. Fbackup DOES NOT CHECK if you are inserting the IRT one, in this case the IRT will be de-
stroyed.
At the end of the fbackup the system will proceed with the start–up as usual, and the result of the activity
will be available in the file /var/adm/syslog/fbackup.log.
Moreover a message with the backup result will be shown at any login.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 172 / 190
190
E.4.3.2.1 Login messages
At the end of full backup you will find one of the following messages:
– Full backup successfully executed. The message will be removed automatically removed at the first
root user login:
**************** THIS WORKSTATION IS SUCCESSFULLY BACKUPED ****************

02–Dec–2003 10:30 – Content: Full backup
*****************************************************************************
N.B. The login of user different then root can receive an error message.
– Full backup issues a warning. You have to check in the file /var/adm/syslog/fbackup.log, ignoring
warning messages related to the volume header:
WARNING: unable to read a volume header
****************** THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************
02–Dec–2003 10:30 – Warning: during Fbackup see /var/adm/syslog/fbackup.log
To fix the problem, check the log file
*****************************************************************************
Note: If you remove file: ”/var/adm/syslog/fbackup.msg” cancel this message
then delete the file /var/adm/syslog/fbackup.msg to remove the login message:

– Full backup issues an error. You have to check in the file /var/adm/syslog/fbackup.log to identify the
reason of the fault, but the backup it is not useful. Delete the file /var/adm/syslog/fbackup.msg to re-
move the login message:
****************** THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************
02–Dec–2003 10:30 ERROR : during Fbackup see /var/adm/syslog/fbackup.log
To fix the problem, check the log file
*****************************************************************************

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 173 / 190
190
E.5 FULL RESTORE
The full backup and restore tool is design to restore on the same physical system the complete contenst
of the hard disks in use with Logical Volume Manager (LVM), the restore on a different hardware it is not

guarantee, also if the Ignite UX tool allows such kind of stuff.

The restore is divided in two phases. The first one is done using the IRT tape set and re–creates the LVM
disk configuration existing at backup time, that means the current contents of the disk will be de-
stroyed. The second phase recovers the contents of the backup file systems.
E.5.1 Restore of IRT Tape Set
The first step in the recovery process consists in:
– Reconfiguring all the hard disks in use at backup time exactly as them was.
– Restoring a minimum set of HP–UX operating system on the hard disks, to be able to operate with
“frecover” tool.
These two activities are perform by booting the HP9000 system from IRT.
E.5.1.1Boot from IRT Tape
To boot the HP9000 system from tape you have to:
a) Switch off the machine.
b) Switch on the machine.
c) Wait the message:
To discontinue, press any key within 10 seconds
Press any key to get the console main menu.
d) Insert IRT in the tape driver, and wait for ready condition of the tape.
e) Enter the command: sea to identify the tape device in a list like:
To discontinue search, press any key (temination may not be immediate).

Path Number Device Path (dec) Device Type
P1 8/4.3 Sequential access media
f) Boot from tape by enter the command:
boot p<x>
where: p<x> is the path number corresponding to tape drive (P1 in the example).
g) Do not interact with IPL by entering “n” at query:
Interact with IPL (Y, N or C) >

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 174 / 190
190
h) Now the machine have to boot from tape by issuing messages like:
HARD Booted
ISL Revision ......
ISL Booting hpux (;0) INSTALL

Boot
...: tape (...
i) If the boot is correctly started you do not get the ISL prompt after three minutes.
j) The Ignite will perform the recovery of the LVM disk structure and the HP–UX in minimum configura-
tion. You do not need to enter any command, just check for any error message.
N.B. The IRT recovery reboots the system twice.
The recovery of IRT can take up to 90 minutes, it depend by the model of the system.
in case of error the Ignite will give a message like the one at follows:
ERROR: The disk at HW path: 0/0/1/1.2.0 was specified in the configuration

files but does not exist on the system. And since
allow_disk_remap=false, no attempt to find a substitute will be made.
Because of the error(s) above, the user–interface must be

used to correct them... Non–interactive install canceled.
Press Return to continue:
When you press “Enter” the Ignite prompt you a window like:
Hardware Summary: System Model: 9000/800/rp7400

+––––––––––––––––––––+–––––––––––––––+––––––––––––––––––+ [Scan Again]
| Disks: 10 (113.9GB)| Floppies: 0 | LAN cards: 3 |
| CD/DVDs: 1 | Tapes: 1 | Memory: 2040Mb|
| Graphics Ports: 0 | IO Buses: 8 | CPUs: 4 | [H/W Details]
+––––––––––––––––––––+–––––––––––––––+––––––––––––––––––+
[ Install HP–UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Read Sys–Admin Message ]

[ Reboot ] [ Help ]
That means there is some thing different in the system configuration that prevents Ignite to perform
the automatic recovery, in this case you hove to drive Ignite manually to bypass the problem.
k) Wait until the end of second reboot.
Some time the machine does not reboot automatically, it stop for a long time (more then
20 minutes) just after issue the message:
1AA 00014 0004 (9007) A4 – ALICE 04.10
NOTE: tlinstall is searching filesystem – please be patient

In this case you can force it to proceed by typing [ctrl]c
ED 02
3AL 88888 AAAA 175 / 190
190
l) When the system will start again from the restored disks, you can see on the console one or more
messages like the following one:
INIT: Command is respawning too rapidly.
Will try again in 5 minutes.

Check for possible errors.

id: .....
Do not worry about them in this phase, in fact they are due to the partial restore of performed by Ignite,
and to the temporary inconsistency between the restored files and /etc/inittab contents.
The messages have to disappear after the restore of fbackup set shown at paragraph E.5.2 page
177.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 176 / 190
190
E.5.2 Restore from Fbackup Tape Set
At the end of the recovery of IRT you can proceed with the recovery of the fbackup tape set:
Do not execute any restore action using GoGlobal–UX tool connection.

a) Login as root.
N.B. You have to enter the same password which was active when the backup was done!
b) This is an optional step. If some preliminary actions are required on the system before to activate the
restore, it is possible to create a commands procedure named “screstore_init” in the directory
“SCINSTALL/etc” that will be executed before to activate the frecover command.
c) Start the screstore script by entering:
..,sys,root # screstore [Enter]
d) screstore asks you to enter the tape device file that have to be used for the restore by issuing the
following request message:
**************************************************
Selection of Tape device
Enter tape device for Frecover <default=<tape device>
Enter the HP–UX file associated to the tape device (ex: /dev/rmt/0m) you want to use for the fbackup
tape set and press [Enter], or just press [Enter] to select the shown file (<tape device>).
e) Now the procedure asks you to insert the first tape of fbackup tape set. You have to insert the first
cassette into the shown tape device, wait the tape device is ready, and press [Enter] to start.
Preparation Tape media for RECOVER

Please load Tape with label Fbackup on device: </dev/rmt/0m>
f) The recovery will start showing you the label that you should have on the Fbackup tape:
**************************************************
Execution of RECOVER
**************************************************
Mounted Tape media should have this label:
01–Dec–2003 14:26 – Full Backup
**************************************************
Press Enter to continue

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 177 / 190
190
g) After you press [Enter] a check on the tape data is made to verify if it is consistent with the current
system configuration. First of all a report is provided regarding the list of saved volume groups:
**************************************************

Tape data compared with the system

*****************************************************************************
Backup tape contains the volume groups:
vg00
*****************************************************************************
h) Then the some more information are checked, refer to paragraph E.5.4.1 at page 183 to see the fore-
seen warning message and the tips for check them.
i) The script issue the following message to ask you the authorisation to change the HP–UX run level
to level three:
*****************************************************************************
Now all Application must be stopped, system go to run level 3
*****************************************************************************
Are you ready, system go to run level 3 (y|n) ? :
Just enter “y” and press [Enter] to proceed.
j) The recovery will start, but it is necessary to attend the frecover execution, because it can ask for
more tape cassettes, and when it require a new cassette you have to remove the current tape and
insert the next one.
Mount the next tape when the request message “Please MOUNT next TAPE Volume” appears,
and press “ENTER” after the message:
frecover(5404): Press return when the next volume is ready on /dev/rmt/0m:
N.B. Don’t warry for the messages like the following:

frecover(1075): moved emsagent to emsagent.2510 since it was executing. Remove em-
sagent.2510 when done.
k) If you insert the wrong tape the frecover will return some messages and questions like the ones
reported at follows, you have to answer as indicated in the example.
frecover(5423): incorrect volume mounted;

frecover(5424): expected volume 1, and got 2
frecover(5433): Do you wish to continue using this volume?([yY]/[nN]) n
frecover(5412): Do you wish to try to salvage this volume?([yY]/[nN]) n
frecover(5411): Do you wish to try a different volume? ([yY]/[nN]) y
PLEASE MOUNT next TAPE Volume
Mount the correct tape when the previous message appears, and then press “ENTER” at the
request.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The frecover can take 150% of the backup time.
l) At the end of the restore, if the system was mirrored at the backup time, the procedure will ask if you
want to rebulid the mirror.
ED 02
3AL 88888 AAAA 178 / 190
190
**************************************************
Frecover end successfully
*****************************************************************************
NOTE: The restored data was mirrored at the backup time.

*****************************************************************************
Do you like to rebuild the mirror (y|n) ? : n[Enter]
You have to answer “n[Enter]” olso if the mirror function was configured in the backuped sysem.
m ) When the restore is completed the system must be reboot again to perform the HP–UX start–up with
the complete environment available on disks.
*****************************************************************************
Now you must execute SHUTDOWN and REBOOT for go to Production
*****************************************************************************
Is system READY for execute SHUTDOWN & REBOOT (y|n) ? :
Just enter “y” and press [Enter] to proceed.
n) screstore asks for the time to reboot:
Enter time for users to log off, before shutdown

Enter time in SECONDS [decimal integer or ”now”] >
Enter “now” and press [Enter] to proceed.
o) When the system will be ready again you can perform the Alcatel TNM application data restore follow-
ing the appropriate recovery procedure (if any), and then start–up again the application too.
If the backuped machine was configured with mirror configuration you have to proceed with “Restore Mir-
ror Condifuration” paragraph E.5.3 at page 180.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 179 / 190
190
E.5.3 Restore MIrror Configuration
The full restore function does not cover mirror disk configuration, it restores the entire file system, including
Disk Mirror/UX but it does not configure the mirror. The reasons of this choice are two:

1) hp Ignite–UX recovery procedure does not support the mirror disk recovery.
2) Perform the mirror configuration during the restore phase increases the down time of the TMN
Applications.
To make easier the mirror configuration OS–Conf provides a specific script “scmirrorfs” to set–up the mirror
configuration again.
To be able to set–up again the mirror configuration, it is advisable that all the disks previously present in
the configuration are available. Really “scmirrorfs” does not completely know the mirror disk configuration
present during the backup, so you have to assign again the mirror copy disks.
N.B. Assigning the disks is possible to change the previous configuration.
The procedure will show you the current disk usage asking you to enter the device name of the disk that
have to be used to store the mirror copy of the data. It is not mandatory that disks belonging to the mirror
copy disk set have to be physically identical to the main disk set, but the amount of space have to be
enough to store all the logical volume currently defined, and it is advisable that disks belonging to mirror
copy disk set do not share the same SCSI chain of the main disk ones. When the configuration script recog-
nize that the disk you are adding to the mirror copy is connected to a SCSI chain already in use for the
main disk set the following warning message is issued:
WARNING: Controller disk already used in “Main path (pvg0)”

Do you want to choose another disk ?
If you have to guarantee the machine functionality also in case of failure of the disk controller, you must
to choose another disk belonging to another chain.
This is an example of the input required and the output produced by ’scmirrorfs’ script.
=>Tue Dec 2 16:29:05 MET 2003

=>START: OSConf File(s) System Mirroring
Hardware detection in progress, please wait ........


_______________________________________________________________________________
Disks Selection
Mirroring need Alternate Boot disk on Volume Group:”vg00”
_______________________________________________________________________________

1AA 00014 0004 (9007) A4 – ALICE 04.10
_______________________________________________________________________________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ _____________
ED 02
3AL 88888 AAAA 180 / 190
190
c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ _____________
c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ _____________
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ _____________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ _____________
_______________________________________________________________________________
Select Alternate BOOT dev name or [q] to quit: c4t8d0
_______________________________________________________________________________
Disks Selection
_______________________________________________________________________________

_______________________________________________________________________________
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ _____________
c4t8d0 8680 0/4/0/0.8.0 Alt_Boot Mirror vg00
c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ _____________
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ _____________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ _____________
_______________________________________________________________________________
Confirm selection of device ”c4t8d0”
Press [y] for yes, [n] for no or [q] to quit, then press [Enter] y
NOTE: Updating of LVM physical volume group information file
NOTE: Set Logical Vol allocation policy to ”PVG–strict” x select Volume Group
NOTE: Preparation of Mirroring Volume Group: ”vg00”
NOTE: Mirroring all Logical Volume of Volume Group: ”vg00”
=>Tue Dec 2 16:31:27 MET 2003

....... Mirroring Logical Volume:”/dev/vg00/lvol1”,
with Allocation policy ”contiguous”
=>Tue Dec 2 16:31:40 MET 2003

=>Tue Dec 2 16:33:13 MET 2003

1AA 00014 0004 (9007) A4 – ALICE 04.10
=>Tue Dec 2 16:33:37 MET 2003

....... Mirroring Logical Volume:”/dev/vg00/lvol4”
=>Tue Dec 2 16:33:44 MET 2003
ED 02
3AL 88888 AAAA 181 / 190
190
=>Tue Dec 2 16:36:01 MET 2003


=>Tue Dec 2 16:36:19 MET 2003
=>Tue Dec 2 16:38:09 MET 2003

=>Tue Dec 2 16:38:53 MET 2003

=>Tue Dec 2 16:39:19 MET 2003

NOTE: Check /etc/lvmrc .....
=>Tue Dec 2 16:42:30 MET 2003

NOTE: Set Alternate Boot Hardware Path to disk:”c4t8d0”
=>Tue Dec 2 16:42:30 MET 2003

=>END: OSConf File(s) System Mirroring
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 182 / 190
190
E.5.4 Restore Warning and/or Error Messages
In order to prevent errors due to tape labeling mistake, or simple tape swap, screstore procedure foreseen
to perform some checks before start the file system(s) restore. This paragraph summarize the possible
warning messages and provides information to support who is operating to decide when proceed and
when stop.
In case of inconsistency between the data present on tape and the system configuration, you will receive
error or warning message. Normally this should happen for three main reasons:
a) The IRT and Fbackup tape was not produced on the same system, tapes coming from different sys-
tems have been mixed.
b) The IRT and Fbackup tape have been produced at different time and with different system configura-
tion. That means you are trying to restore a Fbackup tape over a system where the disk configuration
is so different that the target file system is not available or not enough large to perform the restore.
c) The tape set is the correct one, but something has been modified during the Ignite recover process
(interactive restore installation), or after the successful Ignite recover and before the scretore pro-
cess.
For the first two possibilities you should check the tapes validity and the last one obviously should create
problems.
If an inconsistency occurs it is advisable to stop the restore process in order to investigate on the problem
and after the correction you can run again the ’screstore’ procedure.
At follows are reported some examples listed in category order, where it is possible a corrective action is
described:
E.5.4.1/alcatel File System Not Empty
Each time the backup involves the system volume group (vg00) the following message is shown:
*****************************************************************************
NOTE: If you have activated the ’screstore’ procedure after the system
recover from the Ignite tape, do NOT take into account the
message at follows related to the ’/alcatel’ directory
*****************************************************************************
*****************************************************************************
WARNING: Mount Point: ”/alcatel”
is not an empty directory
*****************************************************************************
The message is shown because the file system mount on to /alcatel directory is not empty, but this case
can occur very often, because every NMS instance can create a directory in /alcatel one. So the best way
to proceed is: ignore this warning message if you have just restore hp–ux from IRT. Otherwise it is better
to not go on.
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 183 / 190
190
E.5.4.2Host inconsitency
*****************************************************************************
ATTENTION: Current host is different from the one backuped.

Current host –> hosta Backuped host –> hostb

*****************************************************************************
N.B. This message can be ignored when you are restoring on a 1359HA OS–Cluster system.
E.5.4.3Volume Group Configuration Mismatch
*****************************************************************************
ERROR: Volume group name ”1353NM_1”
present on tape but not defined on system
*****************************************************************************
Verify the IRT and Fbackup tape consistency.
*****************************************************************************
ERROR: Volume group name ”1353NM_1”
present on tape but not activated on system
*****************************************************************************
Try to activate the volume group you can use the command: vgchange –a y <Volume Group>, and look
at the error messages issued by the activation command, if any.
E.5.4.4Logical Volume Configuration Mismatch
*****************************************************************************
ERROR: Logical volume ”/dev/vg00/lvol11”
present on tape but not defined on system
*****************************************************************************
*****************************************************************************
ERROR: Logical volume ”/dev/vg00/lvol11”
present on tape but not mounted on system
*****************************************************************************
Try to mount the logical volume with the command: mount <Logical Volume Device>
If the command succeded just run again “screstore”, otherwise if the error issued looks like:
mount: /dev/vg00/lvol11 was either ignored or not found in /etc/fstab
verify the IRT and Fbackup tape consistency.
*****************************************************************************
WARNING: Logical volume ”/dev/vg00/lvol4”
references different mount point.
Tape mount point –> ”/user”
System mount point –> ”/home”
*****************************************************************************

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 184 / 190
190
E.5.4.5Mount Point Directory Mismatch
*****************************************************************************
ERROR: Mount Point: ”/alcatel/Kernel/SystemInstances/1353NM_1_7.0_Master”
is not a directory
*****************************************************************************
*****************************************************************************
WARNING: Mount Point: ”/alcatel/Kernel/SystemInstances/1353NM_1_7.0_Master”
is not an empty directory
*****************************************************************************
This message can be issued in case of mount point directory nesting, in this case you should have one
or more empty directory, it it is the case you can proceed, otherwise check the contents.
E.5.4.6File System Configuration Mismatch
The disk size is erroneously shown in Kilo byte instead of Mega bytes.
*****************************************************************************
WARNING: There is not enough space available on file system:
”/alcatel”
required space –> 500 Kb free allocated space –> 400 Kb
*****************************************************************************
Extend the file system using the command: scextendfs <File System> <Free Mega Bytes>
*****************************************************************************
WARNING: The dimension of the file system:
”/alcatel”
is smaller than the required
required space –> 600 Kb total allocated space –> 550 Kb
*****************************************************************************
Extend the file system using the command: scextendfs <File System> <Free Mega Bytes>
E.5.4.7How to proceed
Each time a waring message is issued the following messages are shown:
*****************************************************************************
NOTE: Are you sure the CORRECT TAPE HAS BEEN MOUNTED ?
*****************************************************************************
*****************************************************************************
WARNING: If you proceed you should have data or system problems.
*****************************************************************************
Do you want continue the restore (y|n) ? :
If the warning messages have been analyzed and the warning condition are not present, enter “y[Enter]”
1AA 00014 0004 (9007) A4 – ALICE 04.10
to proceed.
ED 02
3AL 88888 AAAA 185 / 190
190
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
190
3AL 88888 AAAA
186 / 190
APPENDIX F LAN CONFIGURATION
For configure with HP “System Administration Manager” (SAM) all the LAN interface planned to be used
by perform the following actions:

a) Login as root and activate the sam utility:
..,sys,root # sam [Enter]
Figure 35. System Administrator Management Window (1)
b) Select “Networking and Communications“.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 36. System Administrator Management Window (2)
ED 02
3AL 88888 AAAA 187 / 190
190
c) Select “Network Interface Cards“.

Figure 37. Networking and Communications Window
d) Select the line of Lan to be configure then select “Action“ menu and click on “Configure“.
Figure 38. Configure LAN Card Window
e) For each lan to be configure, insert the internet address and click on “Add Host Name Aliases...”:
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 188 / 190
190
Figure 39. Add Host Name Aliases Window
f) Insert the aliases name and click on “Add”, thne, click twice on the [OK] button.
Figure 40. Networking and Communications Window
g) Select “Action” menu and click on “Exit” twice.

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02
3AL 88888 AAAA 189 / 190
190
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
END OF DOCUMENT
190
3AL 88888 AAAA
190 / 190
LABELS AND ASSEMBLY INSTRUCTIONS
TARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 3AL 88888 AAAA Ed.02
1350
1350 Rel.7.0
INSTALLATION GUIDE
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
– No PAGINE TOTALI PER ARCHIVIAZIONE: 192+4=196
– DIMENSIONE BINDER SORGENTE (du –ks): 80.086 Kbytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 5 BUSTE TRASPARENTI (Es.Cod.854.010.051 H)

FIVE TRANSPARENT PLASTIC ENVELOPES ARE NECESSARY
No pagine numerate
(facciate) numbered
No pages da from a to
TARGHETTE - LABELS
frontespizio
2
front
3AL 88888 AAAA Ed.02 manuale
190 1/190 190/190
manual
INSERIRE LE 5 BUSTE TRASPARENTI

INSERT FIVE TRANSPARENT PLASTIC ENVELOPES
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 192
TOTALE FOGLI A4 TOTAL A4 SHEETS: 86
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.

1AA 00014 0004 (9007) A4 – ALICE 04.10
• Source files: ALICE 6.10 ARCHIVED BY GAPI 4.1
ED 02 RELEASED
3AL 88888 CAAA TQZZA Y 1/ 4
4
QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

Site
FCG
Originators 1350 7.0

M.Occhietti
VERSION V7.0
INSTALLATION GUIDE
Domain : OND
Division : NM
Rubric : 1350NM
Type : 1350 REL.7.0 INSTALLATION GUIDE
Distribution Codes Internal : External :
Approvals
Name B.Bosisio F.Casasole

App.
Name
App.
INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10

• sistemazione ’figlist’
3AL 88888 AAAA

Ed.02
1350
1350 Rel.7.0
Network Release
INSTALLATION GUIDE
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02 RELEASED
4
1350
1350 Rel.7.0
Network Release
INSTALLATION GUIDE
VOL.1/1
1350
1350 Rel.7.0
Network Release
INSTALLATION GUIDE
VOL.1/1
1350
1350 Rel.7.0
Network Release
3AL 88888 AAAA Ed.02 INSTALLATION GUIDE VOL.1/1
1350 1350 Rel.7.0

Network Release
1350
1350 Rel.7.0
Network Release

1AA 00014 0004 (9007) A4 – ALICE 04.10
ED 02 RELEASED
4
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
02
RELEASED
4
3AL 88888 CAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT
4/ 4

1350NM Rel.7.0 Installation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1350NM Rel.7.0 Installation Guide

Uploaded by

Copyright:

Available Formats

Installation Guide

3AL 88888 AAAA Ed.02

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 OPERATING SYSTEM INSTALLATION EXECUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

02 040824 SC04091401 F.Casasole B.Bosisio

3AL 88888 AAAA 1 / 190

4 INSTALLING AND CUSTOMIZING NR7 NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

5 FINAL INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

6.6 Inittab Process Not restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

APPENDIX A NMS/NMC SPECIFIC DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

3AL 88888 AAAA 2 / 190

APPENDIX B GOGLOBAL–UX INSTALLATION AND CONFIGURATION . . . . . . . . . . . . . . . . . . . . 127

B.1 GoGlobal–UX Installation on HP–UX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

APPENDIX C HOW TO CREATE A NETWORK DEPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

APPENDIX D PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

APPENDIX E BACKUP AND RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

APPENDIX F LAN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

3AL 88888 AAAA 3 / 190

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

Table 8. Disk Requirements for NMS Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

3AL 88888 AAAA 4 / 190

Edition Date Notes

Ed. 01 May, 2004 First released version of NR7.0 Installation Guide

3AL 88888 AAAA 5 / 190

1.1 General Information

1.2 Handbook applicability

This handbook applies to the following product-releases:

PRODUCT ANV P/N

PRODUCT RELEASE VERSION (N.B.) ANV P/N

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

3AL 88888 AAAA 7 / 190

not permitted without written authorization from Alcatel.

1.3.1 Handbooks related to the specific software application

1.3.2 NR 7.0 Related Handbooks

1354BM 7.0 ATM

1359HA 7.0 OS–Cluster

1359HA 7.0 OS–Resilience

3AL 88888 AAAA 8 / 190

– OSF/Motif is a trademark of the Open Software Foundation.

– HP is a registered trademark of Hewlett–Packard Corporation.

– HP9000/700 and HP–UX are trademarks of Hewlett–Packard Corporation.

– HP OpenView and HP OpenView Window are trademarks of Hewlett–Packard.

– ORACLE is a registered trademark of Oracle Corporation.

The following conventions are used in this manual:

# Actions must be performed as root.

..,sys,root # Actions must be performed as root.

..,$ Actions must be performed as normal user (not as root).

..,oracle> Actions must be performed as oracle user.

SQL> Actions must be performed in SQL utility.

3AL 88888 AAAA 9 / 190

3AL 88888 AAAA 11 / 190

not permitted without written authorization from Alcatel.

– System predisposal for the NMS installation.

2.1.1 Operating system installation

OPERATING SYSTEM BASIC DATA

Gateway Address:_____._____._____._____ Subnet Mask:_____._____._____.______

Domain Name System Yes No (Not yet supported with NR7.0)

Domain name:_____________________ DNS Server Address:_____._____._____.______

Search Domain Name(s) 1._________________________ 2.________________________

Core Memory Size:________________ Source Device:/dev/dsk/________________

Mirror Disk Option: Yes No Command View SDM: Yes No

Gateway Address:___._._._ Subnet Mask:_._._.____

Domain name:___________________ DNS Server Address:_._._.____

Search Domain Name(s) 1._ 2.

Core Memory Size: Source Device:/dev/dsk/

System Boot disk: /dev/dsk/_ Alternate Boot Disk: /dev/dsk/_