1350 Installation Guide

Installation Guide
Alcatel 1350
Management Suite
1350 Rel.7.1
Network Release
3AL 88893 BAAA Ed.01
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
1350 NR7.1 INSTALLATION GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 PRELIMINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 NR 7.1 Related Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Registered Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
10
10
10
11
11
2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 HPUXt Operating System Installation & Configuratione . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Predispose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Instance creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 Software copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.7 Most Used Software Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.8 Bill Of Materials (BOM) for Most Used Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
14
14
14
14
14
16
17
18
3 QUICK INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 HPUX Operating System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 System Predisposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 OSConf Engine and 3PP Description installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Install Alcatel NMS Software Description and Install Wizard . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Create Software Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Run System Predisposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 HPUXt Operating System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 Configure /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Warning About ip_pmtu_strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
19
20
20
20
20
21
23
23
23
1AA 00014 0004 (9007) A4 ALICE 04.10
01
ED
DATE
F.Casasole
040923
CHANGE NOTE
B.Bosisio
M.Occhietti
APPRAISAL AUTHORITY
ORIGINATOR
1350 NR7.1
NR7.1 OSConf 7.1.0
INSTALLATION GUIDE
ED
01
3AL 88893 BAAA
226
1 / 226
29
29
29
31
32
34
34
56
5 SOFTWARE PACKAGE PREDISPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 OSConf Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Create Depots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Before Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Requested Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Requested Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 PreInstallation Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Host declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2 Authorize Network Loopback Access for CD installation . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3 Authorize the Retrieval from Depot Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Install NMS Description and NR7 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Install NR7 Installation Procedure and NMS Description from CD . . . . . . . . . . . . . . . . . .
5.5.2 Install NR7 Installation Procedure and NMS Description from Network Depot . . . . . . .
5.6 Predispose for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Start the SWP Manager Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 Predispose for OSKernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.3 Predispose for 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.4 Predispose for NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.5 Leave the Script and Execute the predisposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
57
57
59
60
60
63
63
63
63
64
64
64
65
65
65
67
73
77
6 OPERATING SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Node Name Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Network configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Synchronize the Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 Initial Clock Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Warning About ip_pmtu_strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Poseidon License Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 Retrieve License Servers Host Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.2 Require the Authorization License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.3 Store the Authorization Key in the License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.4 Check the License Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.5 Add a New License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
83
84
85
89
89
90
90
91
91
91
92
7 INSTALL AND CUSTOMIZE ALCATEL SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Install and Customize OSKernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Install and Customize 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Install 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2 Installing 1353NM Core Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
93
97
97
99
ED
01
3AL 88893 BAAA
226
2 / 226

23
24
25
25
26
27
28
4 OPERATING SYSTEM INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Preparatory activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Check HP9000t Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Initialize the Virtual Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Operating System Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Installing HPUX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Installing HPUX 11i from Bootable Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Virtual Array Command Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10
3.3.3 Configure NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.4 Configure License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Install and Customize Alcatel Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Install and Customize OSKernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Install and Customize NMS and NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Proceed in the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Final Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

7.2.3 Installing 1353NM EMLIM and OBS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.4 Installing 1353NM EMLUSM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5 Installing 1353NM Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6 Installing 1353SH BKW NR5/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.7 Automatic Post Installation Script Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.8 Customize 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.9 How to Proceed with More Than One 1353NM Instance . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.10 Customize 1353SH BacKWard Compatibility Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Install and Customize a Generic NMS and NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1 Install NMS or NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 Customize NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100
102
103
104
104
104
108
109
112
113
115
8 FINAL INTEGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Final Integration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Alarm Surveillance Federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
119
120
9 UPGRADE FROM PREVIOUS VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Material requested by Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Identify the Current Software Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Disk requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Shutdown Entire System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Software Platform Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 Starting from OSConf 7.0.5 P03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 Starting from OSConf 7.0.5 P04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Upgrade from NR7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 Shutdown OSKernel Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.2 Save OSKernel data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.3 Remove NR7.0 NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.4 Remove Useless Links to NR7.0 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.5 Remove any NR7.0 SWPDESC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.6 Predispose for NR7.1T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.7 Review the Master Instance areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 Upgrade from NR7.1 1st. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.1 Poseidon Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.2 Shutdown OSKernel Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.3 Remove 1353NM and OSKernel NR7.1 1st. Software . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.4 Extend /alcatel/7.1 file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.5 Upgrade SWPDESC and Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6 Install and Customize OSKernel and 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.1 Install and Customize NR7.1T OSKernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.2 Install and Customize NR7.1T 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7 System configuration and Final Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8 Upgrade Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8.1 Upgrade from OSConf 7.0.5 P03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
121
121
121
122
123
124
125
125
127
129
129
129
129
131
131
131
132
133
133
133
133
134
134
134
134
134
135
136
136
10 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Identify a Failure Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Failure installing a HPUXt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Recoverable Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Recoverable Faults Installing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 Recoverable Faults Managing SWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Kerberos Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4.1 Kerberos kdcd Process Not Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
137
137
137
138
138
140
141
141
ED
01
3AL 88893 BAAA
226
3 / 226
147
147
148
148
148
APPENDIX B NMS/NMC SPECIFIC DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 NMS Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 NMC Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 Disk Requirement Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.4 Alcatel CD Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
149
150
151
152
APPENDIX C GOGLOBALUX INSTALLATION AND CONFIGURATION . . . . . . . . . . . . . . . . . . . .

C.1 GoGlobalUX Installation on HPUX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2 GoGlobalUX Installation on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2.1 Automatic Removal of GoGlobalUX/Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3 GoGlobalUX license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3.1 License servers definition rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3.2 Retrieve License Servers Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3.3 Permanent License Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3.4 GoGlobalUX authorization procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3.5 Add a new license(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
153
153
153
156
157
157
157
158
162
167
APPENDIX D HOW TO CREATE A NETWORK DEPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169
APPENDIX E PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E.1 Configure a Printer Queue within Local Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.1.1 Start the System Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.2 Configure Printer Booting from Local System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
171
172
176
177
APPENDIX F BACKUP AND RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F.1 Full disks backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.1.1 Full Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.2 Single Volume Group Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.2.1 Single Volume Group Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.1 Ignite Recovery tape restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.2 1359HA OS Cluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.3 Mirror Disk configuration rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.4 Restriction on Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.5 Required disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.6 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.3.7 Restriction on Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.4 FULL BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
184
184
185
185
186
186
187
187
187
187
187
187
188
ED
01
3AL 88893 BAAA
226
4 / 226

141
142
142
142
144
145
145
145
145
146
APPENDIX A SYSTEM TIPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 Find the CDROM Device File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 System Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1 System Shutdown with Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.2 System Halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10
10.4.2 Kerberos kdcd High CPU Consuming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.5 Device Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.1 Devise Full on /var Mounted File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.2 Device full on /usr and /home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.6 Inittab Process Not restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7 Installing and Configuring Mirror Disk/UXt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7.1 Mirror Disk/UXt Installation Prerequisite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7.2 Mirror Disk/UXt Configuration Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7.3 Mirror Disk/UXt Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7.4 Mirror Disk/UXt Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

F.4.1 Start the scbackup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

F.4.2 Create the IRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.4.3 Backup the entire disks contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.5 FULL RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.5.1 Restore of IRT Tape Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.5.2 Restore from Fbackup Tape Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.5.3 Restore MIrror Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F.5.4 Restore Warning and/or Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
188
189
190
200
200
203
206
209
APPENDIX G LAN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
APPENDIX H HPT 9000 SERVER CABLE CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

H.1 HP9000 K Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.2 HP 9000 R Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.3 HP9000 L Class and RP5430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.4 HP9000 A Class and RP2430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.5 HP9000 RP3410 and RP3440 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.6 HP9000 RP4440 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.7 HP9000 N Class and RP7400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.7.1 HP9000 N Class and RP7400 with SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.7.2 HP9000 RP7400 with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.7.3 HP9000 RP7410 with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H.7.4 HP9000 RP7410 Cluster with VA7110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
215
215
218
219
220
220
221
222
222
223
224
225
ED
01
3AL 88893 BAAA
226
5 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
FIGURES
Figure 1. Installation Phases on a server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Example of TMN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Example of disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Alcatel NMS Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. NTP Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. 1353NM Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. 1353NM Customize Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. 1353NM Custom Product Selection N.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. 1353NM Custom Product Selection N.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. 1353NM Custom Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. 1353SHBKW 7.0 Custom System Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. 1353SHBKW 7.0 Custom Parameters Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. 1353SHBKW 7.0 Custom Execution window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. 1354RM Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. NMS Customize trace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. GoGlobalUX Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. GraphOn License WEB Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. GraphOn License WEB Page Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. GraphOn License WEB Page Software Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. GraphOn License WEB Page License Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. GraphOn License WEB Page License Output Example . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Printer Characteriscs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. System Administrator Management Window (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. System Administrator Management Window (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Networking and Communications Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Configure LAN Card Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Add Host Name Aliases Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Networking and Communications Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Rear view of server with two disk cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Rear view of server with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Example of K server cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Rear view of server R with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Front view of L Server (without cover panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Rear view of L Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Front view of A Class and RP2430 Servers (without cover panel) . . . . . . . . . . . . . . . . . .
Figure 39. RP3410 and RP3440 Server Front . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. RP4440 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. RP4440 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Rear view of N/RP74xx Server with SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. RP7400 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
15
50
59
84
85
104
105
106
107
107
108
109
110
111
115
116
117
153
158
158
159
160
161
173
213
213
213
214
214
214
215
216
217
218
219
219
220
220
221
221
222
223
224
225
TABLES
Table 1. Most used software configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Most used configuration BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. List of supported hardware components: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
17
29
ED
01
3AL 88893 BAAA
226
6 / 226

LIST OF FIGURES AND TABLES
1AA 00014 0004 (9007) A4 ALICE 04.10

Table 4. 1353NM Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5. Involved IP Network Node table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. IP Network Description example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. Three Server Redundant License Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. Single License Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9. NR7.1 NMS/NMC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10. 1353NM 7.0 Upgrade BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 11. 1353NM 7.0 Upgrade hard disk space requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12. Disk requirements for NMS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13. Disk Requirements for NMS Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 14. Alcatel NR7.1T CD codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 15. Printer Configuration Data Requested. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 16. Bus types required for DLT to be recognized as a bootable media . . . . . . . . . . . . . . . . . . .
ED
70
83
84
90
90
112
121
123
151
151
152
171
186
01
3AL 88893 BAAA
226
7 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
Edition
ED
Date
Notes
Ed. 01
September 2004
NR7.1 Installation Guide
3AL 88893 BAAA
226

HISTORY
01
8 / 226

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 special, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, reproduced 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
Factory P/N
1350
3AL 88852 AAAA
PRODUCT
RELEASE
VERSION (N.B.)
ANV P/N
Factory P/N
1350
7.1
7.1
3AL 88851 ABAA
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

Handbooks relevant to software applications (typically the Operators Handbooks) are not modified unless the new software version distributed to Customers implies manmachine interface
changes or in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases version marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
01
3AL 88893 BAAA
226
9 / 226
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose product-release-version is stated in para.1.2 on page 9 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application
REF
HANDBOOK
1350 Rel7.1
Installation Guide
[1]
ANV Part No.
FACTORY
Part No.
3AL 88893 BAAA
ANV Part No.
FACTORY
Part No.
THIS
HANDBOOK
1.3.2 NR 7.1 Related Handbooks
REF
HANDBOOK
[2]
1353NM 7.0
Administration Guide
3AL 89061 BAAA
[3]
1354RM 7.1
Administration Guide
3AL 61345 BAAA
THIS
HANDBOOK
or note
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 HewlettPackard Corporation.
HP9000/700 and HPUX are trademarks of HewlettPackard Corporation.
HP OpenView and HP OpenView Window are trademarks of HewlettPackard.
1AA 00014 0004 (9007) A4 ALICE 04.10
ORACLE is a registered trademark of Oracle Corporation.
ED
01
3AL 88893 BAAA
226
10 / 226

1.3 Product-release handbooks

1.5 Overview
This document describes how to install and configure the HP 9000 computer systems in order to allow the
correct usage of A1354RM 6.0 application.
1.6 Conventions
The following conventions are used in this manual:
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>
1AA 00014 0004 (9007) A4 ALICE 04.10
[Enter]
Actions must be performed in SQL utility.
ED
01
3AL 88893 BAAA
226
11 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
12 / 226

2 INTRODUCTION
This document describes how to install Alcatel Network Management Subsystem (NMS) on a HP9000 system. There are two different scenarios: initial and upgrade installation.
The initial installation is foreseen for machine where the operating system is not installed. It includes HP
UXt 11i for PARISCt and the third party software requested by an NMS. The upgrade installation can
be executed on machine already installed for Alcatel NMS.
2.1 Initial Installation

The NR7 initial installation approach allow to distinguish six main activities:
1)
2)
3)
4)
5)
6)
HPUXt Operating System Installation & Configuratione

Predispose
Instance creation
Software copy
Customization
Integration
The following picture shows the NR7 installation process on a server, starting from an empty system up
to an operational one. Each step adds a something new in term of areas, software or references.
Predispose
HPUX
Instance
Creation
HPUX 11i
HPUX 11i
HPUX 11i
NMS2_1_Vx_Master
NMS2_1_Vx_Master
SW copy
NMS2_2_Vx_Master
NMS2_2_Vx_Master
NMS1_1_Vx_Master
NMS2_1_Vx_Client
NMS2_2_Vx_Client
NMS1_1_Vx_Master
NMS2_1_Vx_Client
NMS2_2_Vx_Client
Customize
Integration
OSKernel, NMS
1AA 00014 0004 (9007) A4 ALICE 04.10
OSKernel, NMS
HPUX 11i
File system
OSKernel, NMS
HPUX 11i
HPUX 11i
Internal data reference
Exterenal data reference
Integration reference
Figure 1. Installation Phases on a server.
ED
01
3AL 88893 BAAA
226
13 / 226
The HPUX 11i operating system installation is performed to setup a new system or recicle an old one,
tha is not installed with the right operating system version. The previous hard disk contents will be lost.
2.1.2 Predispose
Predispose allows predisposing HPUX for Alcatel software installation and execution, in terms of: kernel
parameter, file system (size, location), and software layer products. These data have to be provieded with
a Software Packages Description (SWPDESC). A specific set of program will prerare the system as requested.
N.B.
This activity can require the system reboot.
2.1.3 Instance creation

Instance creation allows to predispose HPUX for Alcatel data instances is a process like predispose, but
related to the data. Also the data instance requiremensts have to defined in the Software Packages Description.
N.B.
This activity can require the system reboot and can be combined with predispose.
2.1.4 Software copy

The software copy is the most important installation phase, when the entire Alcatel Network Management
software is copied from the distribution media to the installation target.
2.1.5 Customization
The customization phase adapts the data instance to target system performing the following actions:
Creates empty data structure.
Makes links with the installed management software.
Compiles parameter files by setting the values relevant for instance configuration.
2.1.6 Integration
1AA 00014 0004 (9007) A4 ALICE 04.10
Integration phase allows to join together feature of different NMSs when it is foreseen.
ED
01
3AL 88893 BAAA
226
14 / 226

2.1.1 HPUXt Operating System Installation & Configuratione
1354RM
Presentation
HPUX 11i
1354RM_1_Vy_M
OSKernel, 1353NM Vx
1354RM Vy Software
1353NM_2_Vx_C
1353NM_1_Vx_C
1354RM_1_Vy_C
1353NM_2_Vx_C
1353NM_1_Vx_C

1354RM
Master
OSKernel, 1353NM Vx
1354RM Vy Software
HPUX 11i
1353NM_1_Vx_M
1353NM_2_Vx_M
OSKernel,
1353NM Vx Software
OSKernel,
1353NM Vx Software
HPUX 11i
1353NM
Master
HPUX 11i
1353NM
Master
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 2. Example of TMN configuration
ED
01
3AL 88893 BAAA
226
15 / 226
In the following table are shown the most used software configuration for Alcatel TMN systems. In each
row but the first, the configuration the configuration name, in the column the the software packages and
the data instances, in the row/column conjunction how many times the software or the data instance are
foreseen for each configurations.
Table 1. Most used software configuration.
System Configuration
O 1
S- 3
K 5
E 3
R- N
N M
E
L S
S
1
3
5
3
N
M
1
3
5
3
N
M
1
3
5
4
R
M
1
3
5
4
R
M
1
3
5
4
R
M
1
3
5
4
B
M
M P S M
A
P T
M
1
3
5
4
B
M
A
T
M
1
3
5
4
B
M
A
T
M
1
3
5
4
B
M
E
T
H
1
3
5
4
B
M
E
T
H
1
3
5
4
B
M
E
T
H
S M P S M P
1
3
5
5
V
P
N
S
1
3
5
5
V
P
N
1
3
5
9
H
A
O
S
M
R
E
S
S
1 1 1
1353NM Presentation
1 1
1354RM Master
1 1
N 1 1
1354RM Presentation
1 1
N 1
1354BMATM Master
1 1
1 1
1354BMATM Presentation
1 1
1354BMETH Master
1 1
1 1
1354BMETH Presentation
1 1
1355VPN Master
1353NM &1354RM Master CoHosted
1AA 00014 0004 (9007) A4 ALICE 04.10
1353NM Master
1 1 1
O
O
1
O
O
1
O
1 1
1 1
N.B.
OSKernel Software is always present.
Legend:
Columns:
<Product>
S
Means software of the product (script, executable image, etc.).
<Product>
M Means Master instance of the product.
<Product>
P
Means Presentation instance of the product
Cross points:
1
Means you have to install it or create a data instance.
N
Means you can create one or more data instance.
O Means optional.
ED
01
3AL 88893 BAAA
226
16 / 226

2.1.7 Most Used Software Configurations

2.1.8 Bill Of Materials (BOM) for Most Used Configuration

The following table summarizes the list of software materials requested to be able to install the most used
configurations. Each row but the first show you the configuration name, and the columns are representing
a distribution medium kits. Where you find R in the conjunction you must have the related medium.
The list of the distribution kit medium including the Alcatel code are shown in the Table 14. at page 152.
1353NM 7.0.12 foreseen Patch 03, not available on the distribution kit.
Please refer to Intranet PSC WEB for patch retrieval and for installation instruction.
Table 2. Most used configuration BOM
O
S
C
O
N
F
System Configuration
O 1
S 3
5
K 3
E N
R- M
N
E
L
1
3
5
4
R
M
1
3
5
4
B
M
A
T
M
1
3
5
4
B
M
E
T
H
1
3
5
5
V
P
N
1
3
5
9
H
A
O
S
R
E
S
R R R
1353NM Presentation
R R R
1354RM Master
R R R R
1354RM Presentation
R R R R
1354BMATM Master
R R R
1354BMATM Presentation
R R R
1354BMETH Master
R R R
1354BMETH Presentation
R R R
1355VPN Master
R R
1353NM &1354RM Master CoHosted
1AA 00014 0004 (9007) A4 ALICE 04.10
1353NM Master
R R R R
ED
R
O
01
3AL 88893 BAAA
226
17 / 226
2.2 Restriction
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 3. at page 29 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
OSConf use /etc/lvmpvg to correcly manage the Mirror Disk/UXt configuration and file system extension. Manual changes of this file are forbibben!
ED
01
3AL 88893 BAAA
226
18 / 226

The OSConf 7.1 has the following restrictions:

3 QUICK INSTALLATION
This chapter provides a quick installation guide for speed up the installation task. The current edition of
the document provides information useful for installing: 1353NM, 1354BMATM, 1354BMETH, 1354RM,
1355VPN, 1359ISN, 1359IOO,1359HA OSResilience and OSCluster.
3.1 HPUX Operating System Installation

The HPUX O.S. installation is requested for new machine or systems installed before NR7.1.
NOTE: The HPUX installation delete the entire disk contents.
NOTE: It is advisable to execute the Preparatory Activities shown at paragraph 4.1 page 29.
Insert CDROM SWPOSCONFV7.1.0 in the driver.

Boot or reboot the system from CD.
Reply the question issued:
Keyboard type choosing from the shown list (workstation only).
Enter the timezone of your geographic area.
Check the current system time and change it when needed.
Enter the hostname

NOTE: it is strongly recommended to use ONLY alphabetical lowercase characters
and numerical digits do NOT use uppercase or special characters.
Enter IP address
Enter the default gateway and subnetwork mask when them are present
NOTE: the procedure check default gateway executing a ping
Skip DNS configuration.
Enter the memory size to be used for swap area configuration, you can leave the default value.
Enter CDROM device to be used as default source media, you can leave the default value
Choose to install and configure mirrored disks only if there is the related license.
Choose to install and configure Hp Storage Work Virtual Array only when HP VA7110 disk storage is present in the hardware configuration.
Choose primary boot disk in the provided list,

NOTE: In some cases more then on disk can be required.
When the mirror disk has been selected, also the alternate boot disk will be required.
1AA 00014 0004 (9007) A4 ALICE 04.10
The system will perform the requested activities in unattended mode. Wait the end of installation, it can
take from 30 up to 90 minutes. When the system will prompt you for logging, log in as root and check
in /SCINSTALL/scinstall.log for any error before proceed.
For more information see at Chapter 4 at page 29.
ED
01
3AL 88893 BAAA
226
19 / 226
When the HPUX operating system installation is completed proceed with the system predisposal as
shown in the following.
3.2.1 OSConf Engine and 3PP Description installation.
First of all you have to install OSConf Engine and 3PP description.
Insert the SWPOSCONFV7.1.0 volume 1/4 in the CD or DVD driver.

Mount it by entering the command:
...,sys,root # mount r /dev/dsk/<device name> /SD_CDROM[Enter]
Install the OSCONF engine and 3PP description by executing:
...,sys,root # swinstall s /SD_CDROM OSCONF OSC3PP [Enter]
Dismount the CD and remove it from CD or DVD drive:
...,sys,root # umountl /SD_CDROM [Enter]
3.2.2 Install Alcatel NMS Software Description and Install Wizard

Then install Alcatel NMS Software Description.
Insert the SWPOS_KERNELV7.1 volume 1/1 in the CD or DVD driver.

Install the Alcatel NMS Description by executing:
...,sys,root # swinstall s /SD_CDROM/SWPDESCV7112.sdpkg SWPDESC [Enter]
Install the Alcatel Install Wizard:
...,sys,root # cd /SD_CDROM [Enter]
...,sys,root # sh ./Install_WizardR7.1.7_it4 [Enter]
...,sys,root # cd [Enter]
Dismount the CD and remove it from CD or DVD drive:
3.2.3 Create Software Depot
1AA 00014 0004 (9007) A4 ALICE 04.10
If you have to install many systems, you have now the opportunity to create a software depot that allow
you to proceed in the installation without swap CD from a machine to the other, refer to paragraph 5.2 at
page 57 to know how to do it.
ED
01
3AL 88893 BAAA
226
20 / 226

3.2 System Predisposal
1AA 00014 0004 (9007) A4 ALICE 04.10

3.2.4 Run System Predisposal

Now you have to predispose in one shot the entire system, that means you must know which system configuration you have to create, in term of software and data. In the following table the most used system configuration. Refer to Table 1. at page 16 for the most used software configurations.
Now you can start the predisposal by running scamageswp has show hereafter:
Login the system as root
Enter the command:

...,sys,root # scmanageswp
On the SWP MAIN MENU choose:

1 [Enter]
Predispose new SWP
On the next one:

3
Predispose from Descriptors installed on the system.
The list of software available for predispose will be shown, select the item you want to predispose for by referring the column identified by <Product> S.
When all of them have been selected, enter q[Enter] until you do not get to the SWP MAIN
MENU.
On the SWP MAIN MENU choose:

4 [Enter] Create new SWP INSTANCE.
A list will be shown with the software that foreseen an instance.
You have now to create the data instance for the software by choosing the items from the list,
but considering the following rules:
For the Instances (Master and/or Presentation) shown in Table 1. with 1 at the cross
point, just one instance can be created.
For the Instances (Master and/or Presentation) shown in Table 1. with N at the cross
point, you can create one or more instance. You can also create no one.
For each instance selected, a set of questions will be issued (for more info refer to paragraph
Predispose for Installing 5.6 ant page 65):
Choose one of the possible instance foreseen for the software show as a list.
Enter the Instance number for identification.

NOTE: The instance identifier have to be defined in a plan, and be unique for the
Master instances.
NOTE: The presentation instance number must be equal to the related master!
NOTE: The spare instance number mast be equal to related Master (1359HA OS
Cluster only).
NOTE: Remember the instance number, because it has to be entered again later.
Enter no at the question related to the multiple volume group configuration.
Confirm your choice only if the data enter is correct.
When all the foreseen software data instance have been declared, enter q[Enter] until you do
not get to the SWP MAIN MENU.
At the SWP MAIN MENU prompt enter:

a[Enter] Apply
The list of the pending action will be shown, if everything is correct enter: a [Enter] to start the
predisposal.
The procedure will compute the system requirements in terms of disk space, and it can ask you
for add unused available disks to the current configuration (see paragraph 5.6.5.3 at page 80
for more info).
The it will ask you for the third party software, you can choose to retrieve it from depot (f any)
or from CD ( see paragraph 5.6.5.1 at page 78 for more information).
Enter your choice and provide:
The CD device file or simply confirm the default.
The depot location <hostname>:/<depot directory>
Then the procedure will show you just some trace, asking you sometimes to press enter to continue.
After the following message you have to press [Enter] key to perform the system reboot:
ED
01
3AL 88893 BAAA
226
21 / 226
***** The system reboots automatically, please wait *****

If you are installing from depot the procedure will proceed unattended. If you are installing with
CD, the request of the medium will be issued in console issuing a message that reports the CD
label.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
22 / 226

=>>> WARNING: Now SCINSTALL will be invoked to activate the mod...

The installation will run unattended !!!
Press [Enter] to continue.

3.3 HPUXt
Operating System Configuration
At this step you have to perform these system configurations:
Configure the /etc/hosts.
Configure NTP protocol.
Configure license manager.

3.3.1 Configure /etc/hosts
You have to enter in /etc/hosts file these two information for any machine you this system have to communicate: IP address and name.
The machine you have to include are:
Hosts involved in TNM application.
Printers
Licences management systems.
Time synchronization systems.

Refer to paragraph 6 at page 6 for more information.
3.3.2 Warning About ip_pmtu_strategy
If you plan to install any 1353NM it is MANDATORY set the ip_pmtu_strategy network tuning parameter
to zero, refer to 1353NM 7.0 Administration Guide [2] for more information.
3.3.3 Configure NTP
The NTP configuration foresees to to know the time reference systems in the network, because the NTP
configuration foresees many possible scenarios see at paragraph 6.2 at page 85 for more information.
Hereafter are shown the two most useful configurations for the current system, it can receive (client) or
distribute (server) time reference clock.
3.3.3.1 Configure as NTP Client
To configure your machine as NTP client, login the system as root user and execute scxntp this way:
a)
b)
c)
Enter 1 at OSConf xntp Protocol Configuration menu prompt to Add a new NTP server.
Enter the time server host name (if defined in /etc/hosts) or IP address.
Set it as preferred.
If you have more than one time server, execute again a ) and b ), but do not set the second as preferred.
d)
e)
f)
g)
1AA 00014 0004 (9007) A4 ALICE 04.10
h)
ED
Enter 9 at OSConf xntp Protocol Configuration menu prompt to Align the time to server.
Enter 8 at OSConf xntp Protocol Configuration menu prompt to Start/Stop NTP server.
If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter y to configure NTP daemon to start automatically at system startup.
Start the NTP daemon replaying with y[Enter] to message:
NTP server is stop
Would you like to start it (y/n) ?
Exit by entering e[Enter] at OSConf xntp Protocol Configuration menu prompt.
01
3AL 88893 BAAA
226
23 / 226
a)
b)
c)
d)
e)
f)
Enter 5 at OSConf xntp Protocol Configuration menu prompt to Configure NTP on local clock.
Enter y[Enter] at the question:
Would you like to set Local Clock as preferred source (y/n) ?
Enter 8 at OSConf xntp Protocol Configuration menu prompt to Start/Stop NTP server.
If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter y to configure NTP daemon to start automatically at system startup.
Start the NTP daemon replaying with y[Enter] to message:
NTP server is stop
Would you like to start it (y/n) ?
Exit by entering e[Enter] at OSConf xntp Protocol Configuration menu prompt.
3.3.4 Configure License

The license management can be divide in two phases: the license request and the license set up. The
former have to be done for the entire network management system. The latter for every machine.
3.3.4.1 License request
To be able to configure the licence you have to define the license server machines by following these rules:
If you have a network management with up to two HP 9000 systems, you have to define one of them
as license server, and ask for a single node license.
If you have three or more systems, you have to choose three of them and ask for a three server redundant license.
N.B.
The license have to requested for the entire system.
N.B.
The license have to refer to the license server host identifier and NOT to the server
where the application have to be run on.
For each license server you have to retrieve from the system the FlexLM host identifier by entering:
...,sys,root # /opt/poseidon/bin/lmhostid [Enter]
The shown host id have to be provided during the license request, for the three server redundant configuration all three host id have to be provided at once.
Retrieve the license file, and edit it by adding the port number 27000 at the end of each SERVER line.
3.3.4.2 License Setup
Store the license file into the file /opt/poseidon/etc/license.dat of any machine.
Start the license daemon on any machine by entering the command:
...,sys,root # /sbin/init.d/poseidon start [Enter]
3.3.4.3 Check the license server
1AA 00014 0004 (9007) A4 ALICE 04.10
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat a c /opt/poseidon/etc/license.dat[Enter]
ED
01
3AL 88893 BAAA
226
24 / 226

3.3.3.2 Configure as NTP Server

If you do not have any external time source, you can configure your machine as NTP server, login the system as root user and execute scxntp this way:

3.4 Install and Customize Alcatel Software

Finally you are ready o install and customize the Alcatel software on the target system. This activity is performed by the Alcatel Install Wizard just following this short procedure:
N.B.
Before start check if you have the necessary CDROM or an accessible depot with the entire
software.
N.B.
Check it the depot machine or distribution CD are available, and if local system is correctly authorized to access the files (see 5.4.2 and 5.4.3 for more informations).
3.4.1 Install and Customize OSKernel

The first software you have to install and customize is OSKernel.
N.B.
Do not execute this procedure via GoGlobalUX!

Login the system as root user.
Change directory: ...,sys,root # cd /alcatel/Install_Wizard [Enter]
Install and customize OSKernel by entering:
From CDROM:
Instert the SWPOS_KERNELV7.1 CDROM in the driver.
...,sys,root # ./Install.sh OSKERNEL cdrom [Enter]
Remove CD from the drive.
From depot:
...,sys,root # ./Install.sh OSKERNEL[Enter]
Provide the host name or IP Address of the depot system:

NOTE:
Provide DEPOT hostname or address ?
Provide the directory where the depot is located on depot system:

NOTE:
Provide DEPOT PATHNAME [/alcatel/DEPOT] ?
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
Do not interrupt the procedure!
Once installation phase will be completed, the procedure will request a confirm for the execution of
the customization tool, confirm the operation.
When the procedure will be terminated, verify that no error are shown (warnings can be ignored).
Check also /alcatel/Install_Wizard/log/Install_OSKERNEL_*.log trace file.
ED
01
3AL 88893 BAAA
226
25 / 226
Version
NMS/NMC Name
Description
1353NM
7.0
Network Element Manager
1354BMATM
7.0
Broadband ATM
1354BMETH
7.0
Broadband Ethernett
1354RM
7.1
Regional Manager
1354SY
7.1
Synchronization System
1355VPN
4.0
Virtual Private Network
1359HA_OSRES
7.1
High Availability O.S. Resilience
1359HA_OSCLS
7.1
High Availability O.S. Cluster
1359IOO
5.0
Generic O.S. O.S. Interface
1359ISN
4.0
ISN Open Interface
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
The NMS and NMC installation and customization have to be executed with graphical interface.
Change directory: ...,sys,root # cd /alcatel/Install_Wizard [Enter]
Install and customize OSKernel by entering:
From CDROM:
...,sys,root # ./Install.sh <NMS/NMC Name> cdrom [Enter]
Provide the CD on demand.
From depot:
...,sys,root # ./Install.sh <NMS/NMC Name> [Enter]
Provide the host name or IP Address of the depot system:

NOTE:
Provide the directory where the depot is located on depot system:

NOTE:
N.B.
Do not interrupt the procedure!
1353NM Only: The 1353NM installation will require you to confirm the installation of the 1353SH 5
and 6 interface feature (see paragraph 7.2 at page 97 fop more information):
NOTE: Do you want to execute 1353NM Install package to manage NR5/6
1353SH? [y|n|q]
Once installation phase will be completed, the procedure will request a confirm for the execution of
the customization tool, confirm the operation.
The Custom interface will show you the System Instances List window, you have to select
Choose_one button and set it to NewInstance, then Apple & exit in the Actions menu.
The custom Parameters Definition window will be shown on the screen, it allows you to set the relevant NMS/NMC variables.
Set the value, then Apple & exit in the Actions menu to start the execution.
ED
01
3AL 88893 BAAA
226
26 / 226

3.4.2 Install and Customize NMS and NMC

The product installation and customization process has been unified in NR7, with some little differences
mentioned when needed. For more detailed information refer to paragraphs: 7.2 at page 97 and 7.3 at
page 112.
Hereafter the product list manageable this way:

1353NM Only: An additional window will be shown to select an Element Manager subset (see 7.2.8
a page 104 for more information).
When the procedure will be terminated, verify that no error are shown (warnings can be ignored).
Check also /alcatel/Install_Wizard/log/Install_<NMS/NMC Name>_*.log trace file.
3.4.2.1 Customize Multiple NMS/NMC Instance

The installation procedure is combined with the first instance customization of just installed software, this
usually covers the installation process. Some NMS/NMC foresees to have more than one instance, in this
case you have to execute again the Customization process for each of them without the first one.
Start customize process entering the command:

...,sys,root # /alcatel/Kernel/script/Custom [Enter]
Then at the System Instances List window, you have to select Choose_one button and set it to
NewInstance, then Apple & exit in the Actions menu.
The custom Parameters Definition window will be shown on the screen, set the relevant for the next
instance of NMS/NMC.
Apple & exit in the Actions menu to start the execution.

Repeat these steps for each instance.
3.4.3 Proceed in the Process
1AA 00014 0004 (9007) A4 ALICE 04.10
Now you have to proceed with the specific NMS/NMC configuration, refer to the NMS/NMC specific administration guide.
When the configuration of the current system will be performed, you can proceed with the installation, customization and configuration of the next machine.
When all TMN systems will be installed, customized, configured, and connected via TCP/IP, you can proceed with the integration.
ED
01
3AL 88893 BAAA
226
27 / 226
When all TNM machines have been configured in standalone, you have to run on each one of them the
final integration script.
...,sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl [Enter]
For each system that have to be integrated the following question can be issued:
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 configured, 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
01
3AL 88893 BAAA
226
28 / 226

3.5 Final Integration

4 OPERATING SYSTEM INSTALLATION

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

The activity deletes the entire contents of the hard disk involved.
4.1 Preparatory activities

Before proceeding in the HPUX 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
Operating System Configuration data

4.1.1 Check HP9000t Hardware Configuration
This paragraph shows the HP hardware where the OSConf has been validated. The correct behavior of
the procedure on different hardware is not guarantee.
Table 3. List of supported hardware components:
Optional Cards
HP9000 Model
B5509BA
A4974A
C6362A
100BaseT PCI LAN Adapter

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

PCI Single Ended SCSI
Stand alone DDS2 4GB native DAT driver
Server R380 R390
A5220A
A4107A
J3516A
A3312AZ
HP 9000 DVD ROM Device

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

FWD SCSI2 Controller
HSC FF 100BaseX Dual Port LAN Adptr
HA Factory Racked Storage Enclosure
HPPB FWD SCSI2 host adapter
Server L1000 L2000
1AA 00014 0004 (9007) A4 ALICE 04.10
Workstation B2000
A5557A
A5230A
C6364A
C5708A
DVD ROM Device for LClass systems

PCI 100BaseT LAN Adapter
SMART Desktop SE DDS3 DAT module
DDS 3 Data Cartridge, 24GB/125m
Server RP2430
A5230A
C4314A
C6364A
PCI 100BaseT LAN Adapter

SMART Desktop DVDROM module
ED
01
3AL 88893 BAAA
226
29 / 226
Optional Cards
A5838A
A5272AZ
C4318SZ
Opt. 108
C6365A
A4800A
C6379A
A6795A
A6250AZ
A7295AZ
PCI 2 Port 100BaseT 2 Port Ultra2 SCSI

SureStore E Disk System SC10
SMART Family Full Height Enclosure
DVDROM Drive Factory Racked
SMART SE DDS3 DAT Drive, field racked
PCI FWD SCSI2 card for HP 9000 Server
SMART Field Integrated DLT 8000 module
PCI 2GB FIber Channel Adapter
Disk System 2405 Factory Rack
VA 7110 Dual Cntl,512MB Cache Fact Inst
Server RP5430
A5557A
A5230A
C6364A
A5557A
C5687B
A6795A
A6250AZ
A7295AZ
DVD ROM Device for HP Svr rp54X0 systems

PCI 10/100BaseT LAN Adptr for rp24X0
DVD ROM Device for HP Svr rp54X0 systems
HP SureStore DAT40e 40GB Ext UNIX comp
Server RP7400
A5838A
A5272AZ
A6795A
A6250AZ
C7508AZ
C7499A
A7295AZ

SureStore E Disk Sys SC10 Factory Rack
HP SureStore Tape Array 5300 (factory)
HP SureStore DVDROM Array Module
Server RP7410
A5838A
A5272AZ
A6795A
A6250AZ
C7498A
C7456A
C7499A
A7295AZ

SureStore E Disk Sys SC10 Factory Rack
HP DAT 24m Array Module
HP DLT 80m Array Module
HP SureStore DVDROM Array Module
Server RP3410
C5687C
A9919A
HP DAT 40 External Tape Drive

HP server DVDROM drive, Slimline
Server RP3440
C5687C
A9919A
HP DAT 40 External Tape Drive

HP server DVDROM drive, Slimline
Server RP4440
1AA 00014 0004 (9007) A4 ALICE 04.10
Server N4000
A7163A
A6795A
A6250AZ
A5230A
DVD drive (read only) for 4U chassis

PCI 10/100BaseT LAN Adptr
The HPt 9000 server cable connections are shown in APPENDIX H at page 215.
ED
01
3AL 88893 BAAA
226
30 / 226

HP9000 Model

4.1.2 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 different 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 command 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]
1AA 00014 0004 (9007) A4 ALICE 04.10
The command will also reset the VA, if also with the format the status do not change to Ready, call the
hardware support.
ED
01
3AL 88893 BAAA
226
31 / 226
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.1)
Domain name:_____________________
Search Domain Name(s)
DNS Server Address:_____._____._____.______
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 Customer TCP/IP addressing plan. Be careful with IP Address and Hostname, because it can be some times
impossible to change them later.
Timezone is usually the time zone where the system is located and the definition is simplified by the menu
that shows you the possible areas. Do not define the local time with GMT0 time zone, except if the
system is really located in Greenwich time zone area.
For Core Memory Size it is intended the amount of RAM equipped on the system, it is automatically detected by the procedure and shown as default choice, you have just to confirm if the shown value is correct.
1AA 00014 0004 (9007) A4 ALICE 04.10
Mirror Disk/UXt and The CommandView SDMt 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 HPt.
Source Device means the CDROM device will be used to retrieve the software. It is automatically detected by the procedure.
ED
01
3AL 88893 BAAA
226
32 / 226

4.1.3 Operating System Configuration Data

The last information requested is related to the disks. The System Boot disk is the hard disk on which HP
UXt will be installed on, the required space is 8 Gbyte(1), and the minimum disk size allowed is 4 Gbyte.
If the Mirror Disk/UXt as been requested, the procedure will issue also the request for the alternate boot
disk.
(*) with 512 Mbyte of core memory.
The following list summarizes the actions performed during the operating system installation:
1)
2)
3)
4)
5)
6)
7)
8)
Boot from CDROM bootable disk.

HPUXt 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 UXt Software installation option
Command View Software installation option
System Boot disk selection.
Alternate Boot disk selection (2)

The Boot disk(s) will be initialized.
All the file systems and swap areas will be created
The Operating System will be installed on the selected boot disk.
The optional software will be automatically installed, if any.
The Mirror Disk/UXt will be configured, if selected.
The GoGlobalUXt and OSConf software will be installed.
(1) HPUXt 11i required at least eight Gbyte with a machine with up to one Gbyte of RAM, the operating
system can be stored in two four Gbyte disks.
1AA 00014 0004 (9007) A4 ALICE 04.10
(2)The Alternate Boot disk is asked only when the Mirror/Disk UXt has been selected.
ED
01
3AL 88893 BAAA
226
33 / 226
The HPUX operating system is the first software installed on a new system, this task is performed by
using the OSConf bootable CD.
4.2.1 Installing HPUX 11i from Bootable Medium
This chapter describes how to manage with the bootable media interface with the different configurations
that it allows.
4.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 CDROM 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
P0
P1
P2
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Device Path
Device Type
SESCSI.2.0
FWSCSI.6.0
FWSCSI.5.0
TOSHIBA CDROM
SEAGATE ST34572WS
SEAGATE ST32171W
For HP9000 B2000 workstation the CD it is usually on IDE.
01
3AL 88893 BAAA
226
34 / 226

4.2 Installing HPUX 11i

This is an example for server:
Path Number
P0
P1
P2
N.B.
Device Path
Device Path(mnem)
10/0.6
10/12/5.3
10/12/6.0
SESCSI.2.0
FWSCSI.6.0
FWSCSI.5.0
Device Type
Random access media
Random access media
Lan Module
The CDROM 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
P0
P1
P2
P3
P4
N.B.
Device Path(dec)
Device Type
8/4.9
8/4.8
8/16/5.6
8/16/5.2
8/16/6.0
Random access
Random access
Random access
Random access
Lan Module
media
media
media
media
In this case, the CDROM is connected to SCSI Single Ended Target 2 (8/16/5.2).
Insert the bootable CDROM identified by UX32 or UX64 depending by your machine type (32bit for:
C100,C110, B180L and B132Lplus workstations or 64bit for all the other machine models) into the CD
ROM driver.
When the LED of the CDROM 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
OSCONF Technology
__________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
__________________________________________________________________________
ED
01
3AL 88893 BAAA
226
35 / 226
The first question issued is related to the keyboard selection, this is relevant only for hpt 9000 workstations, if you are installing a hpt 9000 server via console, the procedure will skip it and you have to go to
paragraph 4.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)
3)
5)
7)
9)
11)
13)
15)
17)
19)
21)
23)
25)
27)
USB_PS2_DIN_Belgian
USB_PS2_DIN_Danish
USB_PS2_DIN_Euro_Spanish
USB_PS2_DIN_French
USB_PS2_DIN_German
USB_PS2_DIN_Italian
USB_PS2_DIN_JIS_109
USB_PS2_DIN_Norwegian
USB_PS2_DIN_S_Chinese
USB_PS2_DIN_Swedish_Euro
USB_PS2_DIN_Swiss_German2
USB_PS2_DIN_T_Chinese
USB_PS2_DIN_UK_English_Euro
USB_PS2_DIN_US_English_Euro
2)
4)
6)
8)
10)
12)
14)
16)
18)
20)
22)
24)
26)
USB_PS2_DIN_Belgian_Euro
USB_PS2_DIN_Danish_Euro
USB_PS2_DIN_Euro_Spanish_Euro
USB_PS2_DIN_French_Euro
USB_PS2_DIN_German_Euro
USB_PS2_DIN_Italian_Euro
USB_PS2_DIN_Korean
USB_PS2_DIN_Norwegian_Euro
USB_PS2_DIN_Swedish
USB_PS2_DIN_Swiss_French2_Euro
USB_PS2_DIN_Swiss_German2_Euro
USB_PS2_DIN_UK_English
USB_PS2_DIN_US_English
Enter the number of the language you want: <language_number> [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
You have selected the keyboard language PS2_DIN_xxxxx

Please confirm your choice by pressing RETURN or enter a new number :
[Enter]
ED
01
3AL 88893 BAAA
226
36 / 226

4.2.1.2 Keyboard selection

4.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 machine will be operative.
In the following an example shows how to set the Middle European Time Daylight Saving Time (MET
DST), if you are not in the middle European area you have to choose your timezone:
At the first question you have to enter the number of the seven areas of the world:
__________________________________________________________________________
__________________________________________________________________________
The following procedure enables you to set the time zone.
Select your location from the following list:
1) North America or Hawaii
2) Central America
3) South America
4) Europe
5) Africa
6) Asia
7) Australia, New Zealand
___________________________________________________________________________
Enter the number for your location (17) 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 (MET1METDST).
___________________________________________________________________________
Is this correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
It the choice is correct enter y [Enter], to confirm your selection an go on with the next section.
ED
01
3AL 88893 BAAA
226
37 / 226
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
4.2.1.5 at page 39. Otherwise it will ask you to enter the new date and time issuing the following questions:
___________________________________________________________________________
You will be prompted for the date and time.
Please enter numerically values of month, for example January is 1 or 01.
The values in the parentheses give the acceptable range of responses.
__________________________________________________________________________
Please enter the year (19702037) or last two digit, then press [Enter]
Please enter the month (112), then press [Enter]
Please enter the date of the month (131), then press [Enter]
Please enter the hour (using 24 hour time) (023), then press [Enter]
Please enter the minute (059), then press [Enter]
Then the new date and time will be shown for another confirmation:
You have entered: Apr 8 10:30:00 MET1METDST 2003.
This time will be used to reset the system clock.
Is this value correct?
1AA 00014 0004 (9007) A4 ALICE 04.10
If you confirm the procedure will go on, otherwise it will go back asking again for the date and time.
ED
01
3AL 88893 BAAA
226
38 / 226

4.2.1.4 Time Adjusting

4.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 HPUX uname.
The current hostname is unknown. You cannot configure networking
or run HPCDE 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
01
3AL 88893 BAAA
226
39 / 226
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
01
3AL 88893 BAAA
226
40 / 226

4.2.1.6 IP Address Setup

4.2.1.7 SubNetwork Mask and GateWay setup

This section allows to define the subnetwork mask and the gateway, these two information are fundamental to allow your system to access machines place by outside of your LAN. If your system does not need
to communicate with machines outside your LAN you can skip this section by answering n to the next
question. Its also suggested to skip this section if you do not have the subnetwork mask and gateway information or simply your machine is stand alone.
Even in case your machine is stand alone, it is mandatory to connect the primary lan card
to a network hub or switch.
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
This section enables you to specify the subnetwork mask and default
network gateway. This information is necessary if your network has
gateways and you wish to communicate beyond your local subnetwork.
You will need to know the following information:
* Subnetwork mask
* Default gateway IP address
___________________________________________________________________________
Do you wish to specify this information?
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 4.2.1.9 at page 47, 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)
(default)
___________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
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]
ED
01
3AL 88893 BAAA
226
41 / 226
___________________________________________________________________________
Example:
Subnetwork mask:
255.255.255.0
Current Settings:
Subnetwork mask:
255.255.255.0
> 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 confirm it by pressing [Enter], otherwise enter the correct one and [Enter]
___________________________________________________________________________
Example:
Subnetwork mask:
255.255.255.0
Current Settings:
Subnetwork mask:
255.255.255.0
___________________________________________________________________________
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
A ping to the provided gateway is also attempted to verify the correct configuration of both local and gateway IP address, and in the mean time the correct subnet mask. If the ping fails the operator will be required
to confirm his/her data entry
.... Waiting, ping system 192.200.49.1
___________________________________________________________________________
ED
01
3AL 88893 BAAA
226
42 / 226

The procedure will update the window contents (Current Setting) with new value and it will prompt you for
the gateway address:
4.2.1.8 Domain Name System (DNS)

Do not configure DNS, it is not supported by NR7.1.

This section allows to configure the Domain Name System for HPUXt. 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 hpuxt 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
___________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
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 4.2.1.9 at page 47.
ED
01
3AL 88893 BAAA
226
43 / 226
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:
DNS server address:
lab.alcatel.com
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:
Domain name:
DNS server address:
lab.alcatel.com
192.200.49.1
Current Settings:
Domain name:
alcatel.it
> DNS server address:
(not set)
___________________________________________________________________________
Enter the DNS server address, then press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
3AL 88893 BAAA
226
44 / 226

4.2.1.8.1 DNS Server and Domain Name
__________________________________________________________________________


Example:
Domain name:
DNS server address:
lab.alcatel.com
192.200.49.1
Current Settings:
Domain name:
alcatel.it
DNS server address:
192.200.49.244
___________________________________________________________________________
Are the parameters above correct?
If the data entered are correct, reply y[Enter] and proceed, otherwise enter n[Enter] and repeat. Before
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?
1AA 00014 0004 (9007) A4 ALICE 04.10
Double check the DNS server IP address, if it is correct enter y[Enter] to proceed, otherwise enter n[Enter] to go back to the DNS server and Domain Name data entry.
ED
01
3AL 88893 BAAA
226
45 / 226
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 Server), you have to enter n[Enter] and skip to the next paragraph.
Entering y[Enter] the installation procedure will issue 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.fr [Enter]
Third Domain Name: alcatel.nl [Enter]
Fourth Domain Name:[Enter]
___________________________________________________________________________
Note: DNS has been successfully configured on your system.
___________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
Press [Enter] to continue...
ED
01
3AL 88893 BAAA
226
46 / 226

4.2.1.8.2 Search Domain Name(s)

4.2.1.9 Core Memory and Swap/Dump Sizing

The HPUX swap dimensioning rule foresees to create a swap area large as the double of the core
memory, this rule is also followed by the OSConf 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.
4.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 =
Total CDRoms found =
6
1

Then the procedure will ask you to confirm the source media as the CDROM 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
___________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
Please enter the Device Name of source media [c3t2d0]:
ED
01
3AL 88893 BAAA
226
47 / 226
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
the disks, to prevent system down
the license of use and the double
mirror option.
Have you to install a machine with
to create a copy of the data stored on

time due to disk failure, but requires
of the disk space requested without the
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/UXt 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].
1AA 00014 0004 (9007) A4 ALICE 04.10
Choosing the Disk Mirror/UX installation the procedure automatically configures the mirror feature on any
Volume Group youll create in the system by using the feature of OSConf. To perform this activity the
installation will take 30 minutes more and the machine will be rebooted twice.
ED
01
3AL 88893 BAAA
226
48 / 226

4.2.1.11 Mirror/Disk UX Selection

4.2.1.12 Virtual Array Software Selection

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

___________________________________________________________________________
The Virtual Array Manager Software is requested just in case there is any
HP Storage Work Virtual Array hardware equipped in your system.
There is any HP Storage Work Virtual Array (VA7xxx) in the system
hardware configuration ?
4.2.1.13 Disk Selection
The next phase in the procedure bring you to define the disk configuration. The request issued by this activity depends by the previous answer. That means if you had chosen to have the disk mirror capability the
procedure will ask you disk drive to be able to make a copy of all the data. To obtain the higher availability
level is suggested to choose disk connected to different controllers. For a correct disk management it is
advisable to define the disk usage policy in advance.
4.2.1.13.1 Disk Mirror Configuration Policy
The disk mirror capability is used for two main purposes:
1)
Allow system to survive in case of a single disk failure.
2)
Allow system to survive in case of a single disk controller failure.
It is possible to obtain the better high availability goal only with a correct configuration of the disk resources
available on the system. HPUXt Mirror Disk/UXt allows to reach the first target without specific configuration, but to be able to reach the second one you must have an appropriate system configuration in terms
of hardware and software. The hardware suggested by Alcatel are design to allow mirror configuration that
allow system to survive to disk controller failure, but the software configuration has to be done as shown
in this paragraph to do not loose this capability.
First of all you have to be able to identify the hard disk present present in the configuration, them are usually
identified by their file name. In particular the file name can be very helpful to identify the disk controller
relationship. Any disk in the configuration is identified by the following name: c#t#d#
c[015]
t[015]
d[015]
SCSI of Fiber Channel card instance of disk controller to which the disk is attached to.
SCSI of Fiber channel address of the device on the interface.
Is the device unit number, useful for disk array only, such as VA7110.
1AA 00014 0004 (9007) A4 ALICE 04.10
Using the c# of disk file name is possible to identify the relationship between disks and controllers.
HPUXt allows to connect a single disk to two different controller (DualAccess), in this case the system
command can show two device file for the same disk units, but the installation script manage this configuration by showing just one device with a D on the first column of the related line, hereafter an example of
the selection menu shown by installation scripts:
ED
01
3AL 88893 BAAA
226
49 / 226
Disks Selection
___________________________________________________________________________
Device
MByte
Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8672
0/0/1/1.2.0
_(free)_ ______
________
c2t2d0
8672
0/0/2/0.2.0
_(free)_ ______
________
D c4t8d0
8672
0/4/0/0.8.0
_(free)_ ______
________
D c4t9d0
8672
0/4/0/0.9.0
_(free)_ ______
________
c6t12d0
8672
0/7/0/0.12.0
_(free)_ ______
________
c6t13d0
8672
0/7/0/0.13.0
_(free)_ ______
________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
Now you have to define two disk group (physical volume group) with the following characteristics:
1)
2)
3)
N.B.
The sum of disk space amount of the two group have to be the same.
The DualAccess disks can be assigned to any group.
The non DualAccess disks connected to the same controller MUST belong to the same group.
It is important to follow this rules starting from boot disk definition 4.2.1.13.2 at page 51.
The following picture is a schematic example of disk configuration that can produce the output shown before. This is not a typical system, but provided all the case that can occur in field.
c1t2d0
c2t2d0
c4t8d0
c6t12d0
c4t9d0
c6t13d0
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 3. Example of disk configuration

With this configuration the best one are:
group 1 with c1t2d0, c4t8d0 and c4t9d0, group 2 with c2t2d0, c6t12d0 and c6t13d0.
Because the I/O channel are balanced.
Allowed configuration can be:
group 1 with c4t8d0, c1t2d0, and c2t2d0, group c4t9d0, c6t12d0 and c6t13d0.
Wrong configuration:
Because the two non dualaccess disks have been assigned to the two groups, and the controller
failure gets the system in failure too.
ED
01
3AL 88893 BAAA
226
50 / 226

This section enables you to select the boot disk device.

___________________________________________________________________________

4.2.1.13.2 Main Boot Disk Selection

The first disk you have to select is the main boot disk for the system, the list of the available disk will be
shown in the window in the following format:
This section enables you to select the boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
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.
ED
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 Channel device.
01
3AL 88893 BAAA
226
51 / 226
This question will be issued only if you had selected the mirror disk option; enter the device that will be
used as alternate boot disk. To reach the highest availability level, it is advisable to choose a disk not connected to the same SCSI bus of the Main Boot Disk, this choice allows the system to survive also to a SCSI
bus failure. It is also advisable to choose a disk with the same size.
This section enables you to select the alternate boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
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.
4.2.1.13.4 Multiple Disk Request
1AA 00014 0004 (9007) A4 ALICE 04.10
To install minimum HPUX 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.
ED
01
3AL 88893 BAAA
226
52 / 226

4.2.1.13.3 Alternate Boot Disk Selection
4.2.1.13.5 Disk Selection Confirmation

When all the disk selection will be completed, the program will ask you to confirm your choice.
After this confirm question the contents of the selected disk will be lost.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8672
0/0/1/1.2.0
Pri_Boot _Main_
vg00
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
Dont worry if the machine reboots automatically.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
53 / 226
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 HPUX dumps.
To update the configuration files
To reboot the system to activate the HPUX 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).

Dont worry if the system reboots, it is requested by some software, to be able to configure HPUX kernel
and configure driver.
You have only to replace the first installation CDROM (label UX64_1) with the second one (label UX64_2)
when it will be required with a specific message on the console.
When procedure complete its task the on console youll see the message:
The system is ready.
GenericSysName [HP Release B.11.11] (see /etc/issue)
Console Login:
If you have a HPUX workstation the graphical login screen will be shown instead.
Before proceed with the next step, you have to check the execution log to verify no error has been occurred, you have to login the system a superuser root and check that no error message is shown has
explain, hereafter the messages shown at login time to advice you the installation is still in progress or
when it was failed.
4.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 following message:
********************
WAITING INSTALLATION IS IN PROGRESS *****************
Do not alter environment, check log file in /SCINSTALL/scinstall.log

***************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
Any action on the system or depot may compromise the installation.
ED
01
3AL 88893 BAAA
226
54 / 226

4.2.1.14 Execution Phase
1AA 00014 0004 (9007) A4 ALICE 04.10

4.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
***************************************************************************
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
01
3AL 88893 BAAA
226
55 / 226
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
OSConf 7.0.5 to be able to configure the VA7110 it is mandatory to create an array security account. In fact the ASD is provided with a default user already defined, that allows to perform the first connection 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 configuration 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 1359HAOS Cluster configuration it is recommended 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:
reenter password:
N.B.
Do not leave the password empty, an emply password does not allow the correct login to
CommandView Java interface.
Check the just defined user entering the command: list
h)
1AA 00014 0004 (9007) A4 ALICE 04.10
g)
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:
reenter password:
<secadmin on ipb083>:list
Username Group
Host
root
Administrator ipb083
<secadmin on ipb083>:exit
ED
01
3AL 88893 BAAA
226
56 / 226

4.3 Virtual Array Command Authorization

5 SOFTWARE PACKAGE PREDISPOSE

When the HPUX 11i operating system installation is completed, the system is not yet ready for Alcatel
NMS installation; in fact NMS needs some layer software, that are usually called software platform, to be
able to perform their tasks.
5.1 OSConf Installation

The OSConf packages have to be installed by following this procedure:
a)
Login the just installed system as root user.
b)
Ideintify the CDROM device driver (see Find the CDROM Device File appendix A.1 at page 147).
c)
Insert the CDROM with label SWPOSCONFV7.1.0 Volume 1/4.
d)
Mount the CDROM by entering the command:

...,sys,root # mount r /dev/dsk/<device file> /SD_CDROM [Enter]
e)
Install the OSConf packages by enter the command:

...,sys,root # swinstall s /SD_CDROM OSCONF OSC3PP[Enter]
If the procedure is carried out without error, the system is ready to be predisposed.
5.2 Create Depots

The installation can be executed retrieving the software from a local CD or from a network depot. In case
you choose to install from depot you have to define a system with enough disk space available, where
two depots can be created, one for the third party software, that we will call OS_Conf Depot; where you
can store all the software layer distributed by OS_Conf itself, and one for the Alcatel TNM software, that
we will call Alcatel NMS Depot.
To setup the depot you need 2.3 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.
5.2.1 Create OS_Conf Depot
1AA 00014 0004 (9007) A4 ALICE 04.10
OSConf 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 describes by Appendix D How to create a Network Depot at page 169.
ED
01
3AL 88893 BAAA
226
57 / 226
This paragraph shows how to create the depot for Alcatel software. The depot size depends by the software you have to store on the disk, the Table 12. column Depot Package Size at page 151 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)
b)
c)
d)
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
ED
Insert the CD into the driver.

Mount the CD at /SD_CDROM directory:
...,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM[Enter[
Copy the entire CD contents to /alcatel/DEPOT directory by entering the command:
...,sys,root # cp p /SD_CDROM/* /alcatel/DEPOT [Enter]
Dismount the CD:
...,sys,root # umount /SD_CDROM[Enter]
Remove the CD from the device.
01
3AL 88893 BAAA
226
58 / 226

5.2.1.1 Create Alcatel NMS Depot

5.3 Before Starting

Before starting with the system predispose, 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 functionalities:
a)
Master function
b)
Client function
The Master function provides the set of software programs that allows the machine to perform the network
management, and the Client function to provide the manmachine 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 functionalities at 1354RM level (Navigation).
1353NM Master
1353NM
Client
1353NM
Instan. 2
Client
Instan. 3
1354RM
Master+
Client
Instan.1
1353NM
Master+
Client
Instan.2
OSKernel
OSKernel
1354RM Master with two 1353NM Clients
1353NM Master
1353NM
Master+
Client
Instan.3
OSKernel
Figure 4. 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
01
3AL 88893 BAAA
226
59 / 226
5.3.1 Requested Data
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 OSCluster protection?
Fill in the lists of NMS and NMC in APPENDIX B at page 149 where all the foreseen items are shown.
5.3.2 Requested Hardware
The supporter HP9000t hardware configuration is specified in the paragraph 4.1.1 Check HP9000t
Hardware Configuration at page 29. To completely define the HP9000t server or workstation configuration 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.
5.3.2.1 Requested Network Equipments
The installation of a HPUXt 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.
5.3.2.2 Requested PC
The installation of Alcatel TMN systems can be carried out only with a Graphical User Interface (GUI), because of this to be able to install on a HP9000t Servers you must have a MS Windowst personal computer where you have to install GoGlobalUX software (see the appendix C at page 153 for more information).
5.3.2.3 Required GoGlobal UX License
1AA 00014 0004 (9007) A4 ALICE 04.10
GoGlobal UX needs a permanent or temporary license to be able to run (see paragraph GoGlobal UX
License C.3 at page 157 for more information).
ED
01
3AL 88893 BAAA
226
60 / 226

To be able to complete the installation you have to know in advance the answer to the following questions:

5.3.2.4 Requested Hard Disks

The hard disk requirements within NR7.1 are strictly related to the NMS you are installing, and the size
of the instances of them.
Another specific behavior of OSConf is related to the primary SWAP/DUMP management, in fact the default size of this fundamental system area is defined as the double of the core memory size. Because of
this the minimum disk space requirement for HPUXt 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:
Means the amount of disk space requested by HPUXt operating system, it
can be assumed as up to 6 Gbyte for programs (HPt 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 multiplied per two and the sum of swap size required by each NMS you have to instal
and NMSInstance you have to create, refer to Table 12. (page 151) and
Table 13. (page 151) 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 12. (page 151).
NOTE: OSKernel has to be always installed.
<Data>
1AA 00014 0004 (9007) A4 ALICE 04.10
<Unix>
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 13. (page 151).
For the multiple volume group each NMS instance defines the data size for the
volume group.
<Non protected Data> Means the amount of requested for data storage defined not protected by
1359HA OSCluster. 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 NMSinstance you have to install.
ED
01
3AL 88893 BAAA
226
61 / 226
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.1 with one Master Large instance and 1353NM 7.0 with two Presentation
instances on a HP9000t 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 HPt 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 OSKernel, 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 system volume group, and one 9Gbyte or 18Gbyte or 36 Gbyte for the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
IF YOU CONFIGURE THE MIRROR DISK/UXt FEATURE, YOU MUST PROVIDE THE
DOUBLE OF THE HARD DISK SIZE COMPUTED.
01
3AL 88893 BAAA
226
62 / 226

N.B.
5.4 PreInstallation Actions

Hereafter there are some actions that have to be done before installing.
5.4.1 Host declaration
The network node description have to be filled in manually, for each host you have to communicate to, you
must add a line with the IP Address followed by the host name in the /etc/hosts file (see Node Name Management paragraph 6 at page 83).
5.4.2 Authorize Network Loopback Access for CD installation
Even if the installation is performed locally there are some activities that need the network access to perform their tasks, this is the reason why, to be able to install from CD, it is necessary to add a line in the
/.rhosts file (creating it when it doesnt t exist) with the local host name followed by root keyword.
5.4.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
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
All the host included in .rhosts file have to be defined in /etc/hosts one.
01
3AL 88893 BAAA
226
63 / 226
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.
5.5.1 Install NR7 Installation Procedure and NMS Description from CD
To install the NMS description and NR7 installation procedure from CD you have to insert the SWP
OS_KERNELV7.1 CD in the CD driver and execute the following procedure:
a)
b)
c)
d)
e)
f)

...,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM [Enter]
Install the NMS description by entering the command:
...,sys,root # swinstall s /SD_CDROM/SWPDESCV7112.sdpkg \* [Enter]
Install the Install_Wizard software from CD by entering the command:
...,sys,root # cd /SD_CDROM [Enter]
Set the default directory as /, by entering the command:
...,sys,root # cd / [Enter]
Dismount the CD:
...,sys,root # umount /SD_CDROM [Enter[
5.5.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)
b)
c)
d)
e)

Install the Install_Wizard.sh software from depot machine:
...,sys,root # mkdir /alcatel/DEPOT [Enter]
...,sys,root # cd /alcatel/DEPOT [Enter]
...,sys,root # rcp p <depot IP address>:/alcatel/DEPOT/Install_WizardR7.1.7_it4 . [Enter]
Install the Install_Wizard software entering the command:
Remove the temporary file:
...,sys,root # rm /alcatel/DEPOT/Install_WizardR7.1.7_It4 [Enter]
Install the NMS description by entering the command:
...,sys,root # swinstall s <depot Host>:/alcatel/DEPOT SWPDESC,r=7.1.1.2 [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
If the remote shell (remsh) fails with error: remshd: Login incorrect. check the
depot machine access authorization (see paragraph 5.4.3 at page 63)
01
3AL 88893 BAAA
226
64 / 226

5.5 Install NMS Description and NR7 Installation Procedure

5.6 Predispose for Installation

The OSKernel modular approach allows to predispose the machine after the hpux Operating System
installation, this is performed on demand by a specific script. In this paragraph will be shown: how to predispose the system to be able to run OSKernel, because it has to be always installed. Then it will provided
an example of 1353NM, and a generic example for all the other NMS.
5.6.1 Start the SWP Manager Script
To be able to start the SoftWare Package predispose script you have to login as root user and enter the
command:
...,sys,root # scmanageswp [Enter]
N.B.
VERY IMPORTANT: The whole installation has been described as a single predispose action. This means you have to predispose all the NMS and NMS instances in one shot. This
allows to save time and to do not meet problems in disk space computation. If you have
to interrupt the predisposal in the middle of the selection, exit the procedure choosing
Exit to abort the procedure itself.
The following menu will be shown on the screen:
1
2
3
4
5
6
7
a
e
SWP MAIN MENU
Predispose new SWP

View predisposed SWP
Remove SWP
Create new SWP INSTANCE
View created SWP INSTANCES
Remove SWP INSTANCES
Install 3PP Optional software
Apply
Exit
Insert choice and press [Enter]: 1

Select option 1 in order to predispose for a new SWP installation. First of all you have to predispose for
the OS_Kernel.
5.6.2 Predispose for OSKernel
First of all you have to predispose the system for OSKernel, 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 description installed at paragraph 5.5 at page 64.
1AA 00014 0004 (9007) A4 ALICE 04.10
Predispose new SWP

1 Predispose from CDROM
2 Predispose from Depot
3 Predispose from Descriptors installed on System
q Quit
Insert choice and press [Enter]: 3 [Enter]
ED
01
3AL 88893 BAAA
226
65 / 226
Predispose new SWP

Item SWP Name
SWP Version

1
1353NM
7.0
2
1353SH
7.0
3
1354BMATM
7.0
4
1354BMETH
7.0
5
1354RM
7.1
6
1354SY
7.1
7
1355VPN
4.0
8
1359HA_OSCLS
7.1
9
1359HA_OSRES
7.1
10
OS_KERNEL
7.1
Enter q to Quit, d to Display again or the Item Number: 10 [Enter]
Enter the OS_Kernel 7.1 item (10 in the example) to select it for the predisposition. The procedure will ask
you to confirm the choice.
Selected SWP OS_KERNEL 7.1
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 AlcatelOVDL
Analysing Product Apache20
.
.
.
Analysing Product unzip
Analysing Product xloadimage
TRANSLATOR procedure was successful.
1AA 00014 0004 (9007) A4 ALICE 04.10
The OSKernel is now stored for the predisposal that will be done leaving the script.
ED
01
3AL 88893 BAAA
226
66 / 226

Then the SWP description defined on system will be shown.

5.6.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 Predispose for NMS 5.6.4 at page 73.
1353NM subsystems is organized in two components: the software code and instance. You have to predispose the software code once, but you can create one or more instances. Because of this there are two
different actions, where the second can be iterated more than once.
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.
5.6.3.1 Predispose for 1353NM Software
Proceeding in the script execution, after the OSKernel predisposal the script prompt you again for choosing 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
Item
1
2
3
4
5
6
7
8
9
SWP Name
1353NM
1353SH
1354BMATM
1354BMETH
1354RM
1354SY
1355VPN
1359HA_OSCLS
1359HA_OSRES
SWP Version
7.0
7.0
7.0
7.0
7.1
7.1
4.0
7.1
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:
Selected SWP 1353NM 7.0
After the confirm action the procedure analyzes the description showing all the software layers required:
1AA 00014 0004 (9007) A4 ALICE 04.10

Analysing Product AlcatelOVDL
.
.
.
Analysing Product xloadimage
ED
01
3AL 88893 BAAA
226
67 / 226
Predispose new SWP

Item
1
2
3
4
5
6
7
8
SWP Name
1353SH
1354BMATM
1354BMETH
1354RM
1354SY
1355VPN
1359HA_OSCLS
1359HA_OSRES
SWP Version
7.0
7.0
7.0
7.1
7.1
4.0
7.1
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:
1
2
3
q
Predispose new SWP
Predispose from CDROM

Predispose from Depot
Predispose from Descriptors installed on System
Quit
Insert choice and press [Enter]: q[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter q again to go to the initial menu level.
ED
01
3AL 88893 BAAA
226
68 / 226

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:
5.6.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 OSCluster environment.
3)
Predispose for a 1353NM Client, if you just want to have the 1353NM Presentation function on
any other NMS. In this case you have to create an instance for each 1353NM IM and the
Instance Identification number must be the same of the referred IM.
Here after the sequence of actions you have to perform to carry out the job.
At SWP MAIN MENU prompt you have to enter 4 to get in the Create new SWP INSTANCE:
1
2
4
5
7
a
e
SWP MAIN MENU
Predispose new SWP

View created SWP INSTANCE
Apply
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]
1AA 00014 0004 (9007) A4 ALICE 04.10
The list of the 1353NM possible instances foreseen for the specific machine model is provided.
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 OSCluster
7
1353NM_IM_M_CLSSpare 1353NM Master (IM) Medium System for OSClu...
8
1353NM_IM_L_CLSSpare 1353NM Master (IM) Large System for OSCluster
Enter q to Quit, d to Display again or the Item Number :
ED
01
3AL 88893 BAAA
226
69 / 226
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 OSCluster
1353NM_IM_M_CLSSpare
Middle range configuration for Spare system within 1359HA OSCluster
1353NM_IM_L_CLSSpare
High end configuration for Spare system within 1359HA OSCluster
Table 4. 1353NM Instances

N.B.
The 1353NM_US instance is not defined for 1359HA OSCluster protection
The typical configurations are:
1353NM Information Manager
System is completely devoted to 1353NM function.
1353NM Presentation
System is completely devoted to 1353NM manmachine

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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter the instance item number followed by [Enter] to make your choice.
ED
01
3AL 88893 BAAA
226
70 / 226

Before entering the instance item number for the selection, read carefully the meaningful of each item in
the following table:

For each instance the procedure asks for two information: the instance number identifier and the multiple
volume group.
The instance number identifier have to be assigned following these rules:
The master instance identifier has to be unique in the whole network.

The presentation instance identifier must be equal to the related master.
The spate instance identifier must be equal to the related master.
Insert the Instance Number for 1353NM_IM_Small:
The multiple volume group option is mandatory for the 1359HA OSCluster protected instances. You can
also choose to use the multiple volume group configuration without the 1359HA OSCluster, but you have
to devote specific hard disks for each new instance of data.
Do you like a MultiVolume group configuration ? (y/n)
After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:
Selected INSTANCE:
Dimension
Number
MultiVolume
1353NM_IM_Small
3
NO

Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the required software:
NOTE: the volume group defined in the
SWP/1353NM/7.0/descriptor.cfg will not take
multi_volume_group option is not set.
Volume group vg00 will be used.
Analysing Product DBDMySQL
Analysing Product DBI1.32
Analysing Product MySQL
file /alcatel/Conf/
in account, because

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 hereafter and proceed with the other NMS predisposal if it is the case.
List of available INSTANCE dimension for SWP: 1353NM 7.0
1AA 00014 0004 (9007) A4 ALICE 04.10
Item INSTANCE Dimension

INSTANCE Description

........
ED
01
3AL 88893 BAAA
226
71 / 226

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
Item SWP Name
SWP Version Session

1
1353NM
7.0
YES
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
72 / 226

5.6.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.
5.6.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:
1
2
4
5
7
a
e
SWP MAIN MENU
Predispose new SWP

Apply
Exit

The script proposes the capability to retrieve new SWP description files, enter: 3 [Enter] to skip it.
Predispose new SWP
1 Predispose from CDROM
2 Predispose from Depot
3 Predispose from Descriptors installed on System
q Quit
Then the remaining NMS descriptions will be shown.
Item
1
2
3
4
5
6
7
8
Predispose new SWP

SWP Name
SWP Version

1353SH
7.0
1354BMATM
7.0
1354BMETH
7.0
1354RM
7.1
1354SY
7.1
1355VPN
4.0
1359HA_OSCLS
7.1
1359HA_OSRES
7.1
1AA 00014 0004 (9007) A4 ALICE 04.10

Select a NMS of NR7.1 you want to predispose among: 1353SH 7.0, 1354BMATM 7.0, 1354BMETH 7.0,
1354RM 7.1, 1355VPN 4.0, 1359HA_OSRES 7.1 and 1359HA_OSRES 7.1. Enter the item number
shown in the first column of the menu, then press [Enter] :
N.B.
ED
The item belonging to NR7.1 are shown in bold, do not choose the other ones.
01
3AL 88893 BAAA
226
73 / 226
Then it asks you to confirm your choice, by showing you the selected NMS, enter y [Enter] if it is correct:
Please confirm your selection ? (y/n) y[Enter]

The procedure start the description analysis issuing the following messages:
.
The output depends by the chosen NMS
.
Press [Enter] to proceed, then, exit from the Software predisposal by entering q [Enter] twice to come
back to the SWP MAIN MENU and be able to create the instance:
Predispose new SWP
Item SWP Name
SWP Version

.
.
Choose any other NMS you have to predispose, or enter q [Enter] to complete the NMS software selection. When you enter q [Enter] the procedure will show you the previous menu level.
1
2
3
q
Predispose new SWP
Predispose from CDROM

Predispose from Depot
Predispose from Descriptors installed on System
Quit
Insert choice and press [Enter]: q [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter q [Enter] again to go to the SWP MAIN MENU.
ED
01
3AL 88893 BAAA
226
74 / 226

Selected SWP <NMS name>
5.6.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]:
1
2
4
5
7
a
e
SWP MAIN MENU
Predispose new SWP

Apply
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
Item
1
2
SWP Name
1353NM
<NMS name>
SWP Version
7.0
<NMS version>
Session
YES
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 OSCluster protected instances. You can also
choose to use the multiple volume group configuration without the 1359HA OSCluster, but you have to
devote specific hard disks for each one.
1AA 00014 0004 (9007) A4 ALICE 04.10
Do you like a MultiVolume group configuration ? (y/n)
ED
01
3AL 88893 BAAA
226
75 / 226
Selected INSTANCE:
Dimension
Number
MultiVolume
<NMS Instance Type>

<NMS Instance Identifier>
NO

Confirm or refute the selection. If you confirm the procedure will predispose for the installation of the eventual 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.1
Item
INSTANCE
Dimension
INSTANCE
Description

....
Enter q [Enter] again to go back to SWP MAIN MENU.
Create new INSTANCE
Item
1
2
SWP Name
1353NM
<NMS name>
SWP Version
7.0
<NMS version>
Session
YES
YES
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
76 / 226

After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:

5.6.5 Leave the Script and Execute the predisposal

To speedup the predisposal execution and reduce the disk fragmentation, the predisposal is executed
when leaving the script. To execute the predisposal for all the software you have to exit the SWP MAIN
MENU by entering a[Enter]:
1
2
4
5
7
a
e
SWP MAIN MENU
Predispose new SWP

View create SWP INSTANCES
Apply
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
SWP
INSTANCE
SWP
INSTANCE
SWP Name
SWP Version INSTANCE Number INSTANCE Dimen.. Opt

OS_KERNEL
7.1
1353NM
7.0
1353NM
7.1
2
1353NM_IM_Small
<NMS name> <NMS ver.>
<NMS name> <NMS ver.> 4
<NMS name>_IM_Small
Enter a to Apply, c to Cancel or d to Display again: a [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Then procedure start executing the requested predispositions.
ED
01
3AL 88893 BAAA
226
77 / 226
Before start the procedure will ask you where to find all the software packages, by issuing the following
message:
LAYERED PRODUCTS Repository
1 CDROM
2 DEPOT
Insert choice and press [Enter]:[Enter]
You can choose between CDROM or network depot, here only the network depot choice is shown.
5.6.5.1.1 Software Layer Installation Predisposal from Depot
Here the network depot choice is shown, enter 2[Enter], then the procedure requires you to specify the
depot, enter:
<depot hostname>:/alcatel/SCDEPOT[Enter]
Where you have to replace <depot hostname> with the name of the depot machine (see at paragraph
Create the Depot Machine 5.2 at page 57)
Depot specification for LP
Enter q to Quit or the path of the Depot: 192.202.21.8:/alcatel/SCDEPOT

Checking Depot presence ...
Predisposed installation for product: Perl5005_3
.
.
Predisposed installation for product: MySQL
SOFTWARE predisposition was successful.
Press [Enter] to continueu.
5.6.5.1.2 Software Layer Installation Predisposal from CD
Here the CDROM choice is shown, enter 1Enter], then the procedure requires you to specify the CD driver, enter:
Device selection for LAYERED Products installation
1AA 00014 0004 (9007) A4 ALICE 04.10
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: MySQL
SOFTWARE predisposition was successful.
Press [Enter] to continueu
ED
01
3AL 88893 BAAA
226
78 / 226

5.6.5.1 Software Layer Installation Predisposal
1AA 00014 0004 (9007) A4 ALICE 04.10

5.6.5.2 Kernel Configuration

The next execution phase regards the HPUXt Kernel configuration. The kernel resources have to be
increased to allow the machine to run the application.
This phase does not require any human intervention.
KERNEL configuration activated ...
This operation takes a while, please wait ...
KERNEL configuration was successful.l
ED
01
3AL 88893 BAAA
226
79 / 226
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 requested 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.1
Request free MegaByte(s): 5800
Evaluate size MegaByte(s): 6848
Hardware detection in progress, please wait .......
....
Total disk(s) found = 6
Total CDRoms found = 1
Press [Enter] to continue....
When a new disk is requested, the procedure issues a menu with all the disks present in the configuration,
marking the unused disk with the label (free) in the Usage column.
N.B.
If you are implementing the disk mirroring, to reach the highest availability level, it is advisable
to choose a disk not connected to the same SCSI bus of the Main Boot Disk, this choice allow
the system to survive also to a SCSI bus failure.
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 OSCluster configuration some disk unused by
local system (free) can be used by another one, double check the configuration also of
the other systems!
1AA 00014 0004 (9007) A4 ALICE 04.10
_______________________________________________________________________
Disks Selection
Mount Point need 5632 MBytes on Volume Group: /dev/vg00 (pvg0)
_______________________________________________________________________
Device MByte Hardware Path
Usage
Type
VolGroup
_______________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
Pri_Boot _Main_ vg00
c2t2d0
8680 0/0/2/0.2.0
_(free)_ ______ __________
D c4t8d0
8680 0/4/0/0.8.0
_(free)_ ______ __________
D c4t9d0
8680 0/4/0/0.9.0
_(free)_ ______ __________
c5t12d0
8680 0/7/0/0.12.0
_(free)_ ______ __________
c5t13d0
8680 0/7/0/0.13.0
_(free)_ ______ __________
_______________________________________________________________________
Select Data Area (Main instance) dev name or [q] to quit:
Enter the name of a free disk.
ED
01
3AL 88893 BAAA
226
80 / 226

5.6.5.3 Disk Configuration

_______________________________________________________________________
Disks Selection
_______________________________________________________________________
Usage
Type
VolGroup
_______________________________________________________________________
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)_ ______ __________
c5t12d0
8680 0/7/0/0.12.0
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..
1AA 00014 0004 (9007) A4 ALICE 04.10
It is possible that more then one disk is requested to reach the amount of disk required space. The expected disk amount depends by the number of NMS and NMS instances requested, its size can be computed following the instructions shown in the paragraph Requested Hard DIsks 5.3.2.4 at page 61.
ED
01
3AL 88893 BAAA
226
81 / 226
5.6.5.4 Software Layer Installation
ATTENTION: now to complete the configuration ShutdownReboot will be exe...

***** The System reboots automatically, please wait *****
Reply by pressing [Enter], the machine will be automatically rebooted and software components
installed. If you are installing with CD, the request of the medium will be issued in console issuing a message that reports the CD label.
N.B.
Dont worry if the procedure does not require to insert all CDs, nether if it does not ask
CD in ascending order.
5.6.5.5 End of Software Installation

When the installation will be completed on hpt 9000 server console the following prompt will be shown:
The system is ready
1AA 00014 0004 (9007) A4 ALICE 04.10
GenericSysName [HP Release B.11.11] (see /etc/issue)

Console Login:
Instead on the hpt 9000 workstation the CDE login screen will be shown.
Before proceed to the next activities you have to login hpuxt system check for any error occurred during
the predisposition. Usually a specific message (see paragraph 4.2.1.16) immediately advise you that a
fault is occurred, but it also useful verify the contents of file:
/SCINSTALL/scinstall.log
ED
01
3AL 88893 BAAA
226
82 / 226

The last message issued before starting the software package installation is:

6 OPERATING SYSTEM CONFIGURATION

This chapter shows the minimum operating system and platform configuration required to allow TMN machine interworking.
6.1 Node Name Management

Before proceeding in the installation and customization it is necessary to declare all the IP network nodes
involved. The involved nodes means all the IP are defined in the following table:
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 OSCluster: the virtual IP address of the packages.
Time synchronization Any Time synchronization equipment reachable via IP network.

systems
Table 5. 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 hpux man page hosts for more information).
If the line exists check the data is corresponding with your addressing plan. If it doesnt 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
The /etc/hosts file must be manually updated each time a new machine will be installed.
ED
01
3AL 88893 BAAA
226
83 / 226
WAN
hosta
IP 192.200.49.1
gpsrec1 (GPS time receiver)

IP 192.202.21.51
lp1 (network printer)

192.202.22.6
WAN
hostb
IP 192.202.21.7
hostc
IP 192.202.21.8
hostd
IP 192.202.22.4
hoste
IP 192.202.22.5
Figure 5. Network Example

In this example all the machines work together; you have to define their IP address and official host names
in the /etc/hosts of the five servers.
This is mandatory, because it allows the machines to communicate each other.
Supposing that GPS time synchronization system (gpsrec1) has to be used by the entire network management system, it has also to be defined into the /etc/hosts of all servers.
The network printer (lp1) can be defined only on the server on the same local area network.
hosta
hostb
hostc
hostd
hoste
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
1AA 00014 0004 (9007) A4 ALICE 04.10
192.200.49.1
gpsrec1
To insert
To insert
To insert
To insert
To insert
192.202.22.6
lp1
To insert
To insert
Table 6. IP Network Description example.
ED
01
3AL 88893 BAAA
226
84 / 226

6.1.1 Network configuration example.

This paragraph provides an example of a complex network management system, where there are five
servers working together. These are their roles in the TNM.
hosta
1354RM Client
hostb
1353NM Master
hostc
1354RM Client
hostd
1354RM Master
hoste
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 equipment specified by Table 5. at page
83, in the example:
gpsrec1 Time synchronization system via Global Position System.
lp1
Network line printer.

6.2 Synchronize the Clocks

The clock synchronization is mandatory for system working together with Kerberos authentication tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305 has to be configured by following the instructions shown in this paragraph.
If NTP is not configured you have to check the time difference among all the systems and
guarantee that it doesnt 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 timeserver machines. Each timeserver should be a peer with of the other time
servers.
c ) If possible, do not synchronize multiple timeservers to the same outside source.
d ) If you choose to use an hpt 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 cohosted with 1359HA OSResilience.
hostly, host and hostel preform the presentation function for the resilient servers.
The resilient hosts plus a presentation (host) can be configured to receive the time from the GPS receives,
and swap the time among themselves. All the other servers in the network (hostly and hostel) have to be
configured to receive the time from the host, host e hosted.
GPS
WAN
1AA 00014 0004 (9007) A4 ALICE 04.10
hosta
IP 192.200.49.1
GPS Receiver 1
IP 192.202.21.51
GPS Receiver 2
IP 192.202.22.20
WAN
hostb
IP 192.202.21.7
hostc
IP 192.202.21.8
hostd
IP 192.202.22.4
hoste
IP 192.202.22.5
Figure 6. NTP Configuration Example

To obtain such a configuration the three time servers you have to declare the two GSP Receivers as NTP
servers, moreover they can declare the other ones as peers; the resulting configuration will be:
ED
01
3AL 88893 BAAA
226
85 / 226
hostc
server gpsrec1 prefer
server gpsrec2
peer hosta
peer hostd
hostd
server gpsrec1
peer hosta
peer hostc
The prefer attribute distinguishes as the preferred source, this source it is usually the most reliable and
also the nearest one.
The remaining servers can retrieve the time from the other ones, here after the configuration:
hosta
server hostb prefer
server hostc
server hostd
hoste
server hostb
server hostc
server hostd prefer
To make easier the NTP configuration the scxntp script is provided.
To start scxntp script, login the system as root user and enter: scxntp [Enter]
========================================================================
OSConf 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Insert choice and press [Enter]:

To simplify the explanation, the procedure shows how to configure the server hostb and hosta of
Figure 6. at page 85. Note, the configuration order is relevant for the system behavior, it is better to start
configuring the nodes more close to the Timeservers.
ED
01
3AL 88893 BAAA
226
86 / 226

hosta
server gpsrec2
peer hostc
peer hostd
6.2.1 Configure hostb

This is the procedure using scxntp script to configure the hostb of Figure 6. at page 85.
Login hostb as root user.
b)
Start the scxntp script by entering: scxntp [Enter]
c)
Define the preferred timeserver:

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

Would you like to set 192.202.22.20 as preferred (y/n) ? n
NOTE: Updating /etc/ntp.conf adding server 192.202.22.20 ...
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)
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
Start the NTP Daemon, setup the daemon automatic start at system startup, and synchronize the
hostb clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automat...
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE:
Temporary setup xntpd autostart...
NOTE:
Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset 0.026898 sec
xntpd NOTE:
Reset the setup xntpd autostart...
h)
Leave script by entering e or q.
ED
01
3AL 88893 BAAA
226
87 / 226
6.2.1.1 Configure hosta
Login hosta as root user.
b)
Start the scxntp script by entering: scxntp [Enter]
c)
Define the preferred timeserver:

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
d)
Define the other two timeserver:

NOTE:
Checking the configuration ...
NOTE:
Updating /etc/ntp.conf adding server 192.202.22.20 ...
e)
Check the NTP configuration:

NTP configuration
server 192.202.21.7 version 3 prefer
f)
Start the NTP Daemon, setup the daemon automatic start at system startup, and synchronize the
hosta clock with the preferred server in one shot:
WARNING: The xntpd daemons it is not configure to start automatically
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE:
Temporary setup xntpd autostart...
NOTE:
Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset 0.026898 sec
xntpd NOTE:
Reset the setup xntpd autostart...
g)
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
Leave script by entering e or q.
The script allows to easily manage the NTP configuration, you can add or/and delete servers and/or peers,
show the configuration, stop and start the NTP daemon, or align in one shot your system time to a specific
server.
ED
01
3AL 88893 BAAA
226
88 / 226

This is the procedure using scxntp script to configure the hosta of Figure 6. at page 85.

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.
6.2.2 Initial Clock Alignment

When a machine is installed for the first time, the clock is not synchronized with any reference, the easiest
way to synchronize it with the other is by running scxntp script selecting the option N.9 Align the time
to server.
N.B.
The time alignment is forbidden when NTP daemon is running.
To align the time you have to login the system as root user and start the script scxntp by entering:
...,sys,root# scxntp[Enter]
========================================================================
OSConf xntp Protocol Configuration
========================================================================
1 Add new NTP server
2 Add new NTP peer
3 Remove NTP server
4 Remove NTP peer
5 Configure NTP on local clock
6 Show NTP configuration
7 Show NTP status
8 Start/Stop NTP server
9 Align the time to server
e or q for exit
Insert choice and press [Enter]:
At the prompt enter 9 [Enter]
Enter server hostname or IP address or q for Quit :
The procedure will ask you to enter the IP address or Hostname of the timeserver, enter it and press [Enter]
key. The time will be aligned and shown.
6.3 Warning About ip_pmtu_strategy
1AA 00014 0004 (9007) A4 ALICE 04.10
If you plan to install any 1353NM it is MANDATORY set the ip_pmtu_strategy network tuning parameter
to zero, refer to 1353NM 7.0 Administration Guide [2] for more information.
ED
01
3AL 88893 BAAA
226
89 / 226
6.4 Poseidon License Management Configuration
N.B.
THE AUTHORIZATION LICENSE REQUEST CAN BE EXECUTED ONLY BY AUTHORIZED

ALCATEL PERSONAL.
The package foreseen to manage network floating license, that means you must define one or more system in your network to perform the license server task.
If you have three or more machines, you have to setup a Three Redundant License Servers configuration, in accordance with the following rules:.
The three license server machines should be located physically close to each other (if possible).
Never configure redundant servers with slow communications or dialup links.
The three server have to be reliable.

With threeserver redundancy, only one of the three servers is master, capable of issuing licenses.
Since all clients must contact the master, all clients must have reliable networking to a single node.
if in your network there are less than three nodes, you have to define a the license server, and all the
required licenses have to be loaded on that server.
The license have to be required providing the host identifier of the license server(s). Do not provide the
host identifier of the machine where the application is planned to be run.
6.4.1 Retrieve License Servers Host Identifier
When you have selected the license server machine(s), for each of them you have to retrieve the host
identifier by executing the following commands:
a)
Log in as root on the machine.
b)
Get the hostname of the current machine:

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

..,sys,root # /opt/poseidon/bin/lmhostid
[Enter]
Then fillin this one of these forms:

Table 7. Three Server Redundant License Form
Host Name
Host Identifier
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 8. Single License Form
Host Name
ED
Host Identifier
01
3AL 88893 BAAA
226
90 / 226

Poseidon is the license software manager used to authorize the Alcatel Software execution.
6.4.2 Require the Authorization License

The license can be require via Alcatel Intranet Web, by authorized Alcatel personal only.
6.4.3 Store the Authorization Key in the License File.
When you receive the license authorization key. you have to store it in the following file of any machine
that have to execute Alcatel TNM software:
/opt/poseidon/etc/license.dat
Then start the Poseidon software on it, by entering the command:
...,sys,root # /sbin/init.d/poseidon start[Enter]
Dont worry if no daemon is started on the machines that are license client.
6.4.4 Check the License Status
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat a c /opt/poseidon/etc/license.dat[Enter]
Hereafter an example of the command output. It is divided in four sections: title, server status, vendor daemon status, and feature usage.
The title just shows the version of the license manager.
lmstat Copyright (c) 19892003 by Macrovision Corporation. All rights
reserved.
Flexible License Manager status on Tue 7/20/2004 18:15
The server status shows the license server names, which is the current license server master and
License server status: 27000@hosta,27000@hostc,27000@hostd
License file(s) on hosta: /opt/poseidon/etc/license.dat:
hosta: license server UP (MASTER) v9.2
hostc: license server UP v9.2
hostd: license server UP v9.2
The vendor daemon show the status of the software used to control the license, it must contain alcatel:
Vendor daemon status (on hosta):
alcatel: UP v9.2
Then the feature usage list, with the list of all the authorized feature, and for each one of them the user,
the host and the start date of usage:
Feature usage info:
Users of 1353NM_POINT: (Uncounted, nodelocked)
alcatel hostb /dev/tty (v7.1) (hosta/27000 4406), start Tue 7/20 16:34
Users of 1354BM_POINT: (Uncounted, nodelocked)
1AA 00014 0004 (9007) A4 ALICE 04.10
Users of 1354RM_POINT:
ED
(Uncounted, nodelocked)
01
3AL 88893 BAAA
226
91 / 226
Sometimes in the system live it is necessary to increase the number of license. To add a new license on
a running the license server machine without interrupt the serice, you have to proceed this way:
Do not mix permanent floating authorization key with demo one in the same file!
a)
Retrieve the new license key from Alcatel web, asking for the same host identifier of the first one.
b)
Login a Poseidon license server system.
c)
Save the current license file in a security copy by entering:

...,sys,root # cd /opt/poseidon/etc/ Enter]
...,sys,root # cp p license.dat license.save Enter]
d)
Add the INCREMENT line from the just obtained license file, to the /opt/poseidon/etc/license.dat
file.
The INCREMENT line can be split in two or more ones, because of the length. If the INCREMENT line terminated with back slash ( \ ), that means also the next one have to be considered
as part of INCREMENT.
If you have the three host redundant configuration, copy the license file on other two license servers.
f)
Force the license server daemon to reread the license file by entering:
...,sys,root # /sbin/init.d/poseidon reread [Enter]
g)
1AA 00014 0004 (9007) A4 ALICE 04.10
e)
Check again with lmstat (see paragraph 6.4.4) if the number of point has been increased.
ED
01
3AL 88893 BAAA
226
92 / 226

6.4.5 Add a New License

7 INSTALL AND CUSTOMIZE ALCATEL SOFTWARE

Install and Customize Alcatel Software is the most important installation phase, when the entire Alcatel
Network Management software is copied from the distribution media to the installation target, and then
adapted to the target host by the customization phase.
7.1 Install and Customize OSKernel

The Alcatel OSKernel is the operational platform, so it must be the first software installed.
To install OSKernel Install.sh procedure requires:
The depot machine or distribution CD are available, and the local system is correctly authorized
to access the files (see 5.4.2 and 5.4.3 for more informations).
The installing system must be authorized to retrieve the files from itself or from depot machine.
When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
N.B.
In order to prevent error messages during the OSKERNEL customize it is advisable to

configure the GoGlobalUX license as shown in APPENDIX C.3 at page 157.
GoGlobalUX will be stopped by OSKERNEL configuration script. DO NOT start the
Install.sh with OSKERNEL option from any window open via GoGlobalUX, because all
the GoGlobalUX 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_Wizard [Enter]
For installation from CD:
1)
Insert the SWPOS_KERNELV7.1 CD in the CD driver.
2)

...,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM[Enter]
3)
Start the installation script entering:

...,sys,root# ./Install.sh OSKERNEL cdrom [Enter]
4)
The script issues the following question to require you to confirm the CD driver:
You have to reply with [Enter] to confirm, or enter e different CD device file name.
For installation from Depot Machine:
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
ED

...,sys,root# ./Install.sh OSKERNEL [Enter]
01
3AL 88893 BAAA
226
93 / 226
For both installation method:
..........
........
......
....
..
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
Installing
Wed
Jul
28
OSKERNEL
09:46:27
XX
XX
XX
XX
XX
XX
XXXX
package
METDST
2004
===========================================================================
LOADING: #################################################################.
Then the procedure will ask you the software location by issuing the following to questions:
NOTE:
NOTE:

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, take into account that the installation from CD issues the CD request with a message like this:
PLEASE INSERT CDROM : SWPOS_KERNELV7.1 Vol 1/1
The installation is executed by INSTALLER that shows you the contents of the package :
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE:
Preparing to install ...
NOTE:
Preparing to INSTALLER 7.1.0 ...
***********************************************************************
NOTE:
[ d ${INSTALL_ROOT}/Kernel/data ] && ${INSTALL_ROOT}/Kernel/
script/KernelServices stop
NOTE:
Wed Jul 28 09:34:08 METDST 2004 Executing OSKERNEL pre_install_wa ...
NOTE:
Wed Jul 28 09:34:08 METDST 2004 OSKERNEL pre_install_wa
completed ...
***********************************************************************
NOTE:
${INSTALL_ROOT}/INSTALLER/Install OSKERNEL ${DEPOT_HOST}
file=${DEPOT_PATH}/OSKERNEL_7.1.0.tar.gz interactive=no
ED
01
3AL 88893 BAAA
226
94 / 226

The script start issuing the following mask:

NOTE:
Wed Jul 28 09:46:35 METDST 2004 Executing
OSKERNEL install_cmd ...
Install Tool: INSTALLER 7.0.5

[ Supporting NR7.0 ]
NOTE: NO CONFIGURATION provides by OSKERNEL for the package installation, using the default one .
Image Installation requested for:

Product
OSKERNEL
Format
zip
Host
hosta
File
/SD_CDROM//OSKERNEL_7.1.1.tar.gz
Keep_data
no
Check_sum
NOT APPLICABLE
Interactive
no
PLEASE ENSURE LOCAL OSKERNEL SYSTEM IS NOT RUNNING
.
.
.
The installation start automatically, this step will take up to 15 minutes.

The last question is related to the OSKernel customization; you have to reply also this question with
y[Enter]
Do you want to execute OSKERNEL Custom? [y|n|q] y [Enter]
Then the OSKernel customization will be executed showing the trace on the terminal.
*******************************************************************
NOTE:
${INSTALL_ROOT}/Kernel/script/KernelCustomize
NOTE:
Wed Jul 28 09:53:19 METDST 2004 Executing
custom_cmd ...
.
.
.
NOTE:
Reapplying PLT registrations.
NOTE:
Check GoGlobal 2 configuration ...
OSKERNEL
The procedure will stop after up to 12 minutes, asking you to authorize the GoGlobal UX environment
shutdown. Ask all users logged in with GoGlobal UX to log out the system.
GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no)
1AA 00014 0004 (9007) A4 ALICE 04.10
Reply the question with yes[Enter] to allow GoGlobal UX customization, and then the procedure will
be completed in a couple of minutes issuing:
NOTE:
OSKERNEL installation completed
===================================================================
NOTE:
Session finished on: Wed Jul 28 10:06:00 METDST 2004
ED
01
3AL 88893 BAAA
226
95 / 226
/alcatel/Install_Wizard/log/Install_OSKERNEL_*.log
N.B.
If you doesnt have already configure the GoGlobal License server, it could be displayed
an error message.
Dont care of it, and configure the GoGlobal License Server.

1)
1AA 00014 0004 (9007) A4 ALICE 04.10
2)
ED
Dismount the CD by entering:

...,sys,root# umount /SD_CDROM[Enter]
Remove the CD from the driver.
01
3AL 88893 BAAA
226
96 / 226

The OSKernel installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:

7.2 Install and Customize 1353NM

This chapter explains how to install and customize the 1353NM on the server. This activity is performed
by the Install.sh script 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 NR6 1353SH.
7.2.1 Install 1353NM
To install 1353NM Install.sh procedure requires:
A depot machine or distribution CD have to be available.
The installing system must be authorized to retrieve the files from itself or from the depot machine.
When installing from depot machine: The hostname of the depot machine correctly defined in
the /etc/hosts file.
You have to be able to login the system via GUI, in case of HP server the GoGlobalUX have
to be authorized with the license code (see Appendix C.3 at page 157).
If the mentioned requirement are matched, the installation and customization can be started by:
a)
Login the system via Graphical User Interface CDE as root user.
N.B.
1353NM CUSTOMIZATION WILL FAIL, IF THE INSTALL PROCEDURE IS STARTED

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

1)
insert the SWP1353NM_APPV7.0.12 1/3 CD in the CD driver.
2)

3)

...,sys,root# ./Install.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 CDROM : SWP1353NM_APPV7.0.12 Vol ...
For installation from Depot machine:

...,sys,root# ./Install.sh 1353NM [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
For both installation methods:

N.B.
ED
To allow the recovery of errors it is possible to start install with option confirm, the option
causes the issues of confirm request message before executing each step in the installation
and configuration. Replying no to these questions you can skip the step.
01
3AL 88893 BAAA
226
97 / 226
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.
..........
........
......
....
..
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
Installing 1353NM package

Wed Jul 28 10:53:18 METDST 2004
===========================================================================
Install NR7 tool asks you where to find the depot area for the OSKernel software distribution kits. You
have to reply providing the host name or IP address of the depot machine (see paragraph 5.2.1.1 Create
Alcatel NMS Depot at page 57)
NOTE:
NOTE:

Enter the name of the depot host, and the depot directory when different then /alcatel/DEPOT.
For both installation methods:
N.B.
NOTE:
The report shown in this paragraph is just an example, take into account that the installation from CD issues the CD request with a message like this:
PLEASE INSERT CDROM : SWP1353NM_APPV7.0.12 Vol ...
***********************************************************************
NOTE:
${INSTALL_ROOT}/INSTALLER/Install 1353NM ${DEPOT_HOST}
file=${DEPOT_PATH}/1353NM_7010_CORE_MAR19.tar.gz interactive=no
NOTE:
Wed Jul 28
stall_cmd ...
10:53:26 METDST 2004 Executing
1353NM in-
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
3AL 88893 BAAA
226
98 / 226

N.B.
7.2.2 Installing 1353NM Core Software


Product
Format
Host
File
Keep_data
Check_sum
Interactive
1353NM
zip
hosta
/SD_CDROM//1353NM_CORE_7.0.12.tar.gz
no
NOT APPLICABLE
no
PLEASE ENSURE LOCAL 1353NM SYSTEM IS NOT RUNNING

....
....
....
If you had started Install.sh with confirm option, you have to confirm by entering yes [Enter]
User Id: Alcatel 1353NM Lab
DATE: 2004 June Friday 25 11:59:31 METDST
Product: 1353NM
Products list :
None
Freezing identifier confirmed: date Wed Jul 28
NOTE:
Cleaning temporary areas ...
....
....
....>
10:53:28 METDST 2004..
1AA 00014 0004 (9007) A4 ALICE 04.10
The installation of the first package will take few minutes, the next one will be shown.
ED
01
3AL 88893 BAAA
226
99 / 226
7.2.3 Installing 1353NM EMLIM and OBS Software
Product
Format
Host
File
Keep_data
Check_sum
Interactive



1353NM
zip
hosta
/SD_CDROM//1353NM_IM_7.0.12.tar.gz
no
NOT APPLICABLE
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 Jul 28 10:58:19 METDST 2004.
Product: 1353NM
Products list :>
NOTE:
Cleaning temporary areas
....
....
....>
10:58:19 METDST 2004.
1AA 00014 0004 (9007) A4 ALICE 04.10
The installation of the 1353NM EMLIM package will take about 5 minutes, the next one will be shown.
ED
01
3AL 88893 BAAA
226
100 / 226



Product
Format
Host
File
Keep_data
Check_sum
Interactive
1353NM
zip
hosta
/SD_CDROM//1353NM_OBS_7.0.12.tar.gz
no
NOT APPLICABLE
no

N.B.: IT IS RECOMMENDED TO AVOID THE STOP OF
THE IMAGE INSTALLATION PROCESS. >
Product: 1353NM
Products list :>
NOTE:
Cleaning temporary areas
....
....
....>
11:04:19 METDST 2004.
1AA 00014 0004 (9007) A4 ALICE 04.10
The installation of the 1353NM OBM package will take about 5 minutes, the next one will be shown.
ED
01
3AL 88893 BAAA
226
101 / 226
7.2.4 Installing 1353NM EMLUSM Software

Now install.sh script will install the EMLUSM software.


Product
Format
Host
File
Keep_data
Check_sum
Interactive
1353NM
zip
hosta
/SD_CDROM//1353NM_USM_7.0.12.tar.gz
no
NOT APPLICABLE
no>
User Id: NMLab
DATE: 2004 March Friday 19 18:48:19 MET
Product: 1353NM
Products list :
None>
Freezing identifier confirmed: date Wed Jul 28 11:10:49 METDST 2004.
NOTE:
....
....
.....
1AA 00014 0004 (9007) A4 ALICE 04.10
The installation of the 1353NM EMLUSM package will take about 20 minutes, the next one will be shown.
ED
01
3AL 88893 BAAA
226
102 / 226
7.2.5 Installing 1353NM Patches

The following step can be executed more than once, it depends by the number of patches:


Product
Format
Host
File
Keep_data
Check_sum
Interactive
1353NM
zip
hosta
/SD_CDROM//1353NM_CORE_7.0.12_P1.tar.gz
no
NOT APPLICABLE
no

>
User Id: NMLab
DATE: 2004 March Thursday 25 14:46:47 MET
Product: 1353NM
Products list :
None
Freezing identifier confirmed: date Wed Jul 28 11:30:50 METDST 2004.
NOTE:
....
....
.....
This is the patch list:
1353NM_CORE_7.0.12_P1.tar.gz
1353NM_IM_7.0.12_P1.tar.gz
1353NM_USM_7.0.12_P1.tar.gz
1353NM_CORE_7.0.12_P2_21JUL04.tar.gz
1353NM_IM_7.0.12_P2_21JUL04.tar.gz
1353NM_USM_7.0.12_P2_21JUL04.tar.gz
1AA 00014 0004 (9007) A4 ALICE 04.10
When all the patches will be installed , the software installation of 1353NM will be completed.
ED
01
3AL 88893 BAAA
226
103 / 226
7.2.6 Installing 1353SH BKW NR5/6
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).
If you have any NR5 or NR6 1353SH that have to provide the navigation feature from the installing system,
you have to reply with y [Enter] to this question.
N.B.
This package is significant only if you have predispose a 1354RM item too.
7.2.7 Automatic Post Installation Script Execution

Some post installation activities are automatically executed before starting the 1353NM Custom.
7.2.8 Customize 1353NM
1353NM customization executes the minimum configuration of the software, it is performed in two steps
by Install.sh script: precustom workaround and custom. Both of them are started replying y [Enter]
the following question issued by Install.sh:
Do you want to execute 1353NM Custom ? [y|n] y [Enter]
The procedure starts tracing the custom execution:
======================================================================
NOTE:
Executing 1353NM custom_cmd...
NOTE:
runing </alcatel/Kernel/script/Custom>
NOTE:
Executing 1353NM custom_cmd ...
NOTE:
Basic Kernel Services (Connection Manager, Action Polling) Running. ..........
.
The System, Instances,List window will be shown on the screen after a few seconds, it allows you to select the instance that you want customize:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 7. List of existing instances

Select Choose_one and then NewInstance to define and customize 1353NM7.0. Then select Apple
& exit in the Actions menu.
ED
01
3AL 88893 BAAA
226
104 / 226

When the 1353NM installation is completed, Install will prompt you the following question:

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 8. 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 possible choices, moving the pointer choose one of them and release the mouse button: System_Version, System_Instance_Rule, Master Kernel_Type and Driver_Version.
To customize the 1353NM you have to set the System_Version on 1353NM7.0, then enter the Instance
identification number defined at predisposal time (see Predispose 135NM Instance paragraph 5.6.3.2
at page 69) 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Set the System_Instance_Role 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
/etc/host file.
The Client Instance Identifier must be equal to the related Master!
ED
01
3AL 88893 BAAA
226
105 / 226
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, dont 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 9. 1353NM Customize Trace
1AA 00014 0004 (9007) A4 ALICE 04.10
The 1353NM Custom script will show the Custom Product Selection 1353NM <instance number> window. This window allows to reduce the time spent to perform the custom by specifying a subset of the Network 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.
ED
01
3AL 88893 BAAA
226
106 / 226

The input fields identified by System_Instance_Name allows to define the name of the system within
the TMNOS application.

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 10. 1353NM Custom Product Selection N.1
Figure 11. 1353NM Custom Product Selection N.2

procedure.
ED
01
3AL 88893 BAAA
226
107 / 226
Figure 12. 1353NM Custom Warning

The procedure will complete its task in about 45 minutes on a L1000 server, issuing some foreseen warning messages shown in the Figure 12. 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 G Lan Configuration at
page 213 for more information).
The 1353NM installation and customization is now completed, before continue installation it is advisable
/alcatel/Install_Wizard/log/Install_1353NM_*.log
/alcatel/Kernel/maintenance/trace/Custom.trace
/alcatel/Kernel/maintenance/log/Custom.log
1)
2)

7.2.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.sh allows to
custom the first one, if you have more than one, you have to start the OSKernel Custom procedure for
each one of the instance but the first.
To run OSKernel Custom procedure:
Login the system as root with CDE GUI.
Open a graphical terminal .
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter the command: /alcatel/Kernel/script/Custom[Enter]
A window like Figure 8. will be open, enter next instance identification data as shown in the paragraph
Customize 1353NM 7.2.8 at page 104, and proceed customizing the next 1353NM.
Execute the Custom for all instances.
ED
01
3AL 88893 BAAA
226
108 / 226

Please, ignore the warning messages shown in the following picture.

7.2.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 following question also shown at paragraph 7.2.6Installing 1353SH BKW NR5/6 at page 104:
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 paragraph 5.6.3 page 67. For each the created1353SH 7.0 instance you have to perform the data custom script
as shown in this paragraph:
To run OSKernel Custom procedure:
Login the system as root with CDE GUI.
Open a graphical terminal .
Enter the command: /alcatel/Kernel/script/Custom[Enter]
Figure 13. 1353SHBKW 7.0 Custom System Selection.

Select Choose_one and then NewInstance, then select Apple &exit in the Actions menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
The custom Parameters Definition window will be shown on the screen after a few seconds, it allows you
to set the relevant custom variables:
ED
01
3AL 88893 BAAA
226
109 / 226

Figure 14. 1353SHBKW 7.0 Custom Parameters Setup.

N.B.
To customize the 1353NM you have to set the System_Version on 1353SH7.0, then enter the Instance
identification number defined at predisposal time (see Predispose 135NM Instance paragraph 5.6.3.2
at page 69) in the input area under the label System_Instance_Id.
If the Instance identification number does not correspond to the predisposed 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 Client .
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
3AL 88893 BAAA
226
110 / 226

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 15. 1353SHBKW 7.0 Custom Execution window.

The procedure will complete its task in about 10 minutes on a L1000 server, issuing some foreseen warning messages shown in the Figure 15. Please ignore them.
1AA 00014 0004 (9007) A4 ALICE 04.10
The 1353SH installation and customization is now completed, before continue installation it is advisable
/alcatel/Kernel/maintenance/trace/Custom.trace
/alcatel/Kernel/maintenance/log/Custom.log
ED
01
3AL 88893 BAAA
226
111 / 226
This chapter explains how to install and customize a generic NMS or NMC. This activity is performed by
the Install.sh script in one shot.
In the following table the NMS and NMC foreseen for NR7.1:
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 Manager
1354BMETH
7.0
Broadband Ethernet Manager
1354RM
7.1
Regional Manager
1355VPN
4.0
Virtual Private Network
1359HA_OSRES
7.1
High Availability O.S. Resilience
1359HA_OSCLS
7.1
High Availability O.S. Cluster
1359IOO
5.0
Generic O.S. O.S. Interface
1359ISN
4.0
ISN Open Interface
Table 9. NR7.1 NMS/NMC table
1AA 00014 0004 (9007) A4 ALICE 04.10
(*) The installation of this item has been already shown in an other paragraph.
ED
01
3AL 88893 BAAA
226
112 / 226

7.3 Install and Customize a Generic NMS and NMC

7.3.1 Install NMS or NMC

To install any kind NMS or NMC shown at Table 9. (except 1353NM) with Install.sh procedure requires:
A depot machine or CD distribution set available.
The installing system must be authorized to retrieve the files from itself or from the depot machine.
When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
You have to be able to login the system via GUI, in case of HP server the GoGlobalUX 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.
c)
Entering the following commands at dtterm prompt:


1)
2)
3)
insert the the first CD of NMS Distribution kit in the CD driver.

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

...,sys,root# ./Install.sh <NMS/NMC name> [Enter]
N.B.
To allow the recovery of errors it is possible to start install.sh with option confirm, the
option causes the issues of confirm request message before execute each step in the
installation and configuration. Replying no to these questions you can skip the step.
1AA 00014 0004 (9007) A4 ALICE 04.10
The script start issuing the Alcatel mask, then it will ask you some questions.
ED
01
3AL 88893 BAAA
226
113 / 226
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
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 OSKernel software distribution kits. You
have to reply providing the host name or IP address of the depot machine (see paragraph 5.2.1.1 Create
Alcatel NMS Depot at page 57)
NOTE:
NOTE:
Enter the name of the depot host, and the depot directory when different then /alcatel/DEPOT.
NOTE:
.
The output depends by the chosen NMS or NMC
.
NOTE:
Do you want to execute <NMS/NMC name> Custom? [y|n|q] )
1AA 00014 0004 (9007) A4 ALICE 04.10
If you had started Install.sh with confirm option, you have to confirm by entering y [Enter]
The time spent for installation of package depends by NMS.
ED
01
3AL 88893 BAAA
226
114 / 226

........
......
....
..

7.4 Customize NMS

NMS customization execute the minimum configuration of the software, it is performed in two steps by
Install.sh script: precustom workaround and custom.
NOTE:
NOTE:
...
NOTE:
/alcatel/Kernel/script/Custom
Mon Feb 2 14:44:39 MET 2004 Executing <NMS/NMC name> custom_cmd
/alcatel/Kernel/script/Custom
Figure 16. List of existing instances
1AA 00014 0004 (9007) A4 ALICE 04.10
Select Choose_one and then NewInstance , then select Apple &exit in the Actions menu.
ED
01
3AL 88893 BAAA
226
115 / 226

Then custom Parameters Definition window will be shown on the screen after a few seconds, it allows
you to set the relevant custom variables:
Figure 17. 1354RM Customize Window

N.B.
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 5.6.4.2 at page 75) in the input area under the label System_Instance_Id.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the Instance identification number does not correspond to the predisposed the customization script will create the data in a wrong place, and the /alcatel 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).
ED
01
3AL 88893 BAAA
226
116 / 226

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, dont 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 OSCluster 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 procedure.
Figure 18. 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
to check for any error that may have occured by check the contents of the following file:
1AA 00014 0004 (9007) A4 ALICE 04.10
/alcatel/Install_Wizard/log/Install_<NMS/NMC name>_*.log
ED
01
3AL 88893 BAAA
226
117 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
2)
ED
01
3AL 88893 BAAA
226
118 / 226

8 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 configuration.
VERY IMPORTANT!!
When all the TNM machines have been configured in standalone, you have to run on
each one of them the final integration script!
8.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/UpdateNetworkConnections.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:
NOTE:
NOTE:
NOTE:
NOTE:
NOTE:
...
...
Started in Interactive mode on ALL TMN Systems locally defined

Updating Required Client Instances...
Starting Required InterSystem Integrations...
1353NM_1: No Integratable System defined. Skipping 1353NM_1.
1354RM_3: Detected the following integrated Systems: 1353NM_1
1354RM_3: 1353NM_1 Already integrated. ReApplying 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Warning and error messages will advice you that the remote system is not reachable or not properly configured, 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.
When the procedure will be successfully executed, you will be able to use all the Network Management
System features.
ED
01
3AL 88893 BAAA
226
119 / 226
The Alarm Surveillance federation is an OSKernel 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:
ASUSMFederation.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.
<Sec Instance>
<NMS Instance List>
No special characters are allowed in the AS USM Window title.
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.
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/ASUSMFederation.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
1AA 00014 0004 (9007) A4 ALICE 04.10

name RegionWest sec 1354RM_2 1354RM_2 1353NM_2 1353NM_3
ED
01
3AL 88893 BAAA
226
120 / 226

8.2 Alarm Surveillance Federation

9 UPGRADE FROM PREVIOUS VERSION

This chapter describes how to upgrade a 1353NM 7.0 Master or Presentation system from NT7.0 or NR7.1
1st. to the NR7.1T application level.
This activity have to be carried on carefully, because the system you are working on is operational. Because of this it is suggested to perform a data backup via System Management Feature, and check for
the system full backup is available.
N.B.
The upgrade can require one or more system reboots.
N.B.
The 1353NM 7.0 upgrade with 1359HA protection are not described in this document.
N.B.
The upgrade of 1353NM with multiple volume group configuration are not described in this document.
9.1 Prerequisite
The upgrade procedure is allow only for 1353NM pure systems, installed within NR7.0 or NR7.1 1st. context, moreover the upgrade will require a larger amount of disk space.
Before start you have to check if you system meets the requirement starting conditions and you have all
the matirials that can be required by the upgrade process:
a)
b)
c)
The installed software is a pure 1353NM 7.0 system, installed in NR7.0 or NR7.1 1st. context.
The disk space available is enough to store the upgraded version of software and the extention foreseen for the data.
Yo have all matirials needed to be able to carry out the upgrade.
9.1.1 Material requested by Upgrade

This is the bil of material (BOM) you need to be able to perform the upgrade:
1353NM 7.0.12 foreseen Patch 03, not available on the distribution kit. Please refer to Intranet PSC WEB for patch retrieval and for installation instruction.
3AL 72881 AAAA 02
This have to be the second edition, it

have to report on UX64 volume label
HPUX Dec 2003, and on ADD1 volume
label OSConf 7.0.5 P04
SWPOSCONFV7.1.0
3AL 72881 ABAA 01
hpuxt 11i installation tool. Six CD with

the following labels forms it: UX64_1.
UX64_2, 1/4, 2/4, 3/4 and 4/4.
SWPOS_KERNELV7.1
3AL 88872 ABAA 02
Alcatel OSKernel and installation tools.
SWP1353NM_APPV7.0.12
1AA 00014 0004 (9007) A4 ALICE 04.10
SWPOSCONFV7.0.5
3AL 89055 ABAA 01
Alcatel 1353NM NMS Software.
Table 10. 1353NM 7.0 Upgrade BOM
ED
01
3AL 88893 BAAA
226
121 / 226
To check the current installed software have to be executed on two different levels: predispose and
installed.
To see which is the software platform predisposal, login the system as root, enter the command: scmanageswp, enter 2 to show View predisposed SWP, and 5 to show View created SWP INSTANCE.
The output have to show the 1353NM and OS_Kernel items.
This is an example of the scmanageswp View predisposed SWP output for NR7.0 level:
SWP predisposed on system
SWP Name
1353NM
OS_KERNEL
SWP Version Session

7.0
7.0
Total number of SWP on this system is: 2

[Enter] to continue.
This one is the output example of the scmanageswp View predisposed SWP for NR7.1 1st. level:
SWP predisposed on system
SWP Name
1353NM
OS_KERNEL
SWP Version Session

7.0
7.1
Total number of SWP on this system is: 2

This one is the output example of the scmanageswp View created SWP INSTANCE for both NR7.0 and
NR7.1 1st. level:
INSTANCE created on system
SWP Name
SWP Version INSTANCE Number INSTANCE Dimension
Ses...

1353NM
7.0
7
1353NM_IM_Medium
Total number of INSTANCE on this system is: 1
To see which is the installed software, you have to login the system as 1353NM administration user, start
the TMNOS Tool, select the 1353NM instance, and from OS menu activate the System Information
item. The 1353NM version have to be 7.0.10, with any level of path up to P03.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
Take notes about the 1353NM Instance type and identification numbers, because youll
have to provide them later when customizing the new software!
If these prerequisite are met you can start the upgrade.
ED
01
3AL 88893 BAAA
226
122 / 226

9.1.2 Identify the Current Software Level

9.1.3 Disk requirements

The new software require a larger amount of disk space, because to be able to complete the upgrade you
have to verify the amount of available space on the disks. The following table shows the requirements for
the upgrade related to the starting configuration. The data is provided in megabytes and in the corresponding value of physical extent.
From NR7.0
From NR7.1 1st.
Megabytes
Physical Extent
Megabytes
Physical Extent
1353NM
Master
3360
105
2176
68
1353NM
Presentation
2176 +
(64*<N. Instance>)
68 +
(2*<N. Instance>)
2176+
(64*<N. Instance>)
68 +
(2*<N. Instance>)
Table 11. 1353NM 7.0 Upgrade hard disk space requirements.

The show values have to be multiply by two if the system is configured with Disk Mirror/UXt protection.
9.1.3.1 How Verify the Available Disk Space
The relevant configuration described in this document are two:
1)
System configured without Disk Mirror/UXt protection.
2)
System configured with Disk Mirror/UXt protection.
9.1.3.1.1 Check Available Disk Space without Disk Mirror/UXt protection.

To evaluate the amount of available disk space of system configured without Disk Mirror/UXt protection
you have just to enter the commands:
...,sys,root #
...,sys,root #
...,sys,root #
...,sys,root #
...,sys,root #
. /SCINSTALL/lib/scALLfs.lib [Enter]
PVGFile=/etc/lvmpvg [Enter]
PVGArray= [Enter]
PVGFreeExtent /dev/vg00 0 PE [Enter]
echo $PE [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
The echo command will show you the free physical extent available on the volume group, if it is higher then
the requested one you can proceed in the upgrade, if it is not higher you have to check for one unused
hard disk unit as shown at 9.1.3.1.3.
ED
01
3AL 88893 BAAA
226
123 / 226
For machine configured with Disk Mirror/UXt protection to survive to hard disk failure, the hard disk in
use are organized in two group (Physical Volume Groups), that means you have to verify the disk space
requirements for each of them. To do it you have to perform the actions shown at paragraph 9.1.3.1.1 two
times, the first one as it is, the second time with the following PVGFreeExtent command instead of the
shown one:
...,sys,root # PVGFreeExtent /dev/vg00 1 PE [Enter]
For each group that does not satisfy the requirements you have to check for the availability of an unused
hard disk, as shown a 9.1.3.1.3.
9.1.3.1.3 Check Available Unused Disk Units
To check the unused hard disk on your system a specific command option as been design, you have just
to enter:
...,sys,root # scextendfs i [Enter]
And look in the output for any disk shown with _(free)_ in the Usage column.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
c2t2d0
8680 0/0/2/0.2.0
Alt_Boot _Copy_ vg00
c4t0d0
8680 0/4/0/0.0.0
c4t1d0
8680 0/4/0/0.1.0
_(free)_ ______ __________
c5t8d0
8680 0/4/0/0.8.0
__Data__ _Copy_ vg00
c5t9d0
8680 0/4/0/0.9.0
_(free)_ ______ __________
___________________________________________________________________________
Press [Enter] to continue....
N.B.
For Disk Mirror/UXt protected systems,
If you have the Disk Mirror/UXt protection, the upgrade can require to add two hard disk to the configuration, and also the SCSI disk chain can be relevant. Check in paragraph 4.2.1.13.1 Disk Mirror Configuration Policy at page 49 the rule for the hard disk choice.
9.2 Shutdown Entire System
1AA 00014 0004 (9007) A4 ALICE 04.10
The upgrade requires the system shutdown, it is advisable to ask connected users to close their activity
and log out the system. You have to advise all 1353NM users on both Master and Presentation systems.
When the user ill be logged out, log in the machine as 1353NM administrator and shutdown the 1353NM
entire system.
ED
01
3AL 88893 BAAA
226
124 / 226

9.1.3.1.2 Check Available Disk Space with Disk Mirror/UXt protection.

9.3 Software Platform Upgrade

There are two starting point for upgrade the software platform, the OSConf 7.0.5 P03 defined as NR7.0
platform and OSConf 7.0.5 P04 defined as NR7.1 1st. one. To be able to upgrade the platform to the right
level you have to identify the current one, it can be simply done by login the system as root and look at
the welcome message shown.
The OSConf 7.0.5 has been issued in two edition: the first one on January the 16Th 2004, identified by
the following message:
ALCATEL OSConf Boot 7.0.5 HPUX 64bits (16Jan04)
The second edition was issued for supporting the new HP server equipped with PA8800 processor on April
the 30Th 2004, identified by:
ALCATEL OSConf Boot 7.0.5 HPUX 64bits Dec 2003 (30Apr04)
Another message can be shown to report the update level:
ALCATEL OSConf Upgraded to 7.0.5.P03
ALCATEL OSConf Upgraded to 7.0.5.P04
(15Apr04)
(26May04)
If you have a OSConf 7.0.5 P03 or P04 you can proceed in the upgrade by the related paragraph.
9.3.1 Starting from OSConf 7.0.5 P03
The upgrade of OSConf 7.0.5 P03 platform to P04 foreseen three phases:
1)
Check upgrade prerequisite.
2)
Upgrade the OSConf software
3)
Perform the platform upgrade.
9.3.1.1 Extend /opt if Needed.

This paragraph shows how to upgrade your system to OSConf 7.0.5 P04, this activity require to have
50 Mbyte free available in /opt file system. So enter the following command and check that the value shown
in the avail column is higher than 51200:
...,sys,root # bdf /opt[Enter]
If issued value is lower you have to extend /opt file system by entering:
...,sys,root # scextendfs /opt 50 [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Reboot the system as soon it is possible.
ED
01
3AL 88893 BAAA
226
125 / 226
Now the system is ready to upgrade the software platform to OSConf 7.0.5 P04, do it has shown in the
following paragraph:
1)
Insert the CD SWPOSCONFV7.0.5 Volume ADD1 , and mount it by entering:

2)
Remove OSCONF 7.0.5 P03 by entering:

...,sys,root # swremove OSCONF [Enter]
3)
Install OSCONF 7.0.5 P04 by entering:

...,sys,root # swinstall s /SD_CDROM OSCONF,r=7.0.5.P04 [Enter]
9.3.1.3 Upgrade Platform to OSConf 7.0.5 P04 Level

Keeping the CD mounted perform the software platform to OSConf 7.0.5 P04.
1)
Start the upgrade procedure by entering:

...,sys,root # /SCINSTALL/etc/scupgrade [Enter]
2)
Reply the following question by entering 1[Enter] to choose the CDROM:

_________________________________________________________
OSConf 7.0.5 P04 Upgrade Procedure
1 CDROM
2 DEPOT
The available space on /opt and /var file systems will be shown to allow you to check. Example:
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?
5)
If you have more the 51200 in the column avail related to /opt row, reply y[Enter] to proceed.
Otherwise reply N[Enter] and go to paragraph 9.3.1.1 at page 125 and extend the file system.
6)
The procedure will show the upgrade progress until the end.
7)
ED
The procedure asks you to enter the CD driver file name, usually the proposed default is correct.
Enter q to Quit or the CD device [def=/dev/dsk/c2t2d0]:
4)
1AA 00014 0004 (9007) A4 ALICE 04.10
3)
Dismount the cd by entering the following command and then remove the CD:
...,sys,root # umount /SD_CDROM [Enter]
01
3AL 88893 BAAA
226
126 / 226

9.3.1.2 Upgrade OSConf 7.0.5 P03 software to P04
9.3.2 Starting from OSConf 7.0.5 P04

The upgrade of OSConf 7.0.5 P04 platform to 7.1.0 foreseen two phases:
1)
Upgrade the OSConf software
2)
Perform the platform upgrade.
9.3.2.1 Upgrade OSConf 7.0.5 P04 software to OSConf 7.1.0

To upgrade the software platform from OSConf 7.0.5 P04 to OSConf 7.1.0, you have to proceed this
way:
1)
Insert the CD SWPOSCONFV7.1.0 Volume 1/4 , and mount it by entering:

2)
Remove OSCONF 7.0.5 P04 by entering:

...,sys,root # swremove OSCONF [Enter]
3)
Install OSCONF 7.0.5 P04 by entering:

...,sys,root # swinstall s /SD_CDROM OSCONF OSC3PP [Enter]
9.3.2.2 Upgrade Platform to OSConf 7.1.0 Level

Keeping the CD mounted perform the software platform to OSConf 7.1.0:
1)
If the system has been installed with OSConf 7.0.5 P03, execute the workaround described
in the paragraph 9.8.1
2)
Start the upgrade procedure by entering:

...,sys,root # /SCINSTALL/etc/scupgrade [Enter]
3)
The following menu will be issued to allow you to specify where software packages are located,
you have to reply with 1[Enter] to choose the installation from CDROM:
OSConf 7.1.0 Upgrade Procedure

1 CDROM
2 DEPOT
Insert choice and press [Enter]: 1[Enter]
4)
The procedure asks you to enter the CD driver file name, usually the proposed default is correct.
Enter q to Quit or the CD device [def=/dev/dsk/c2t2d0]:
5)
The procedure will check the amount of free space on the file system, and enlarge them when
needed. If any enlarged file system is in use, the extension can non be complete, a reboot will
be required by issuing the following message:
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
The file system extension can ask for new hard disk, refer to paragraph
4.2.1.13.1 Disk Mirror Configuration Policy at page 49 the rule for the hard
disk choice.
___________________________________________________________________
System need reboot x complete extension of file system current ...
___________________________________________________________________
ED
01
3AL 88893 BAAA
226
127 / 226
If one or more file system will require the system reboot the
ATTENTION
Upgrade OSConf install product(s) and/or Patch(es)
System could automaticaly reboot
All Application must be stopped (example: RM, NM, Resilience ec...)
Do you want continue ?
Stop all the activity, if any, and reply with y[Enter].
The installation will take two hours on a R180 system and can execute two automatic reboots.
9)
ED
After the reboot the file system will be enlarged, and the installation will start.
8)
1AA 00014 0004 (9007) A4 ALICE 04.10
7)
The procedure will be terminated when the machine will issue the login prompt. At that time you
have to logging again as root, and check for any error in /SCINSTALL/scinstall.log.
01
3AL 88893 BAAA
226
128 / 226

6)

9.4 Upgrade from NR7.0

The upgrade from NR7.0 is performed by removing the NR7.0 software and predisposing for the new one.
Here after the procedure.
9.4.1 Shutdown OSKernel Services
The 1353NM system is already stop, you have now to shutdown also the OSKernel services by entering
the following command:
...,sys,root # /alcatel/Kernel/script/KernelServices stop[Enter]
9.4.2 Save OSKernel data
Before to proceed with the NM upgrade, is required to save the OS_Kernel data file by entering the following command:
...,sys,root # cp p /alcatel/7.0/Kernel/data/inittab.base /alcatel [Enter]
9.4.3 Remove NR7.0 NMS
This is the procedure to remove NR7.0 1353NM and OSKernel from the system:
a)
Login as root user, and start the scmanageswp by entering:

...,sys,root # scmanageswp[Enter]
b)
The scmanageswp main menu will be shown, enter 3[Enter] to choose Remove SWP:
SWP MAIN MENU
1 Predispose new SWP

2 View predisposed SWP
3 Remove SWP
4 Create new SWP INSTANCE
5 View created SWP INSTANCE
6 Remove SWP INSTANCE
7 Install 3PP Optional software
a Apply
e Exit
Insert choice and press [Enter]: 3[Enter]
c)
The Remove SWP will show you the list of SWP installed, enter the 1353NM 7.0 item number to
require the SWP removal:
Remove SWP
Item
1
2
SWP Name
1353NM
OS_KERNEL
SWP Version
7.0
7.0

1AA 00014 0004 (9007) A4 ALICE 04.10
d)
scmanageswp will advise you that a NMS instance exists, press enter to continue:
=>>> WARNING:There are Instances defined on system for the selected SWP
Remove is acceptable in case of Network Release migration.
ED
01
3AL 88893 BAAA
226
129 / 226
The procedure will ask you to confirm your 1353NM 7.0 choice, reply by entering y[Enter]:
Selected SWP is candidate to be removed from system:
1353NM 7.0
f)
scmanageswp will prompt you the Remove SWP menu, you have to select the OKKernel SWP
do be removed:
Remove SWP
Item SWP Name
SWP Version

1
OS_KERNEL
7.0
g)
The procedure will ask you to confirm your OSKernel 7.0 choice, reply by entering y[Enter]:
Selected SWP is candidate to be removed from system:
OS_KERNEL 7.0
h)
The procedure will advise you there are no more SWP installed, pre [Enter] to proceed:
Remove planned for SWP: OS_KERNEL 7.0
=>>> WARNING: No more SWP are configured on this system.
i)
Apply the new configuration by entering a[Enter] at SWP main menu:
SWP MAIN MENU
2
3
5
6
a
e

Remove SWP
View created SWP INSTANCE
Remove SWP INSTANCE
Apply
Exit
Insert choice and press [Enter]:a[Enter]

j)
The select for removal items will be shown, if them are the correct ones, you have to enter a[Enter]
again to activate the planned actions:
Items SELECTED for the REMOVAL
Item Type
SWP
SWP
SWP Name
1353NM
OS_KERNEL
SWP Version INSTANCE Number INSTANCE Dime...

7.0
7.0
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter a to Apply, c to Cancel or d to Display again:

k)
ED
The procedure can ask you to confirm the /alcatel/7.0, you have to reply entering y[Enter]:
NOTE:
Mount Point:/alcatel/7.0 is not an empty directory
Do you want kill all processes are using Mount Point:/alcatel/7.00 ?
01
3AL 88893 BAAA
226
130 / 226

e)

l)
If the procedure issues an error message like the following and require the system reboot, you have
to allow the procedure to reboot the system, and execute the command shown at point m ):
umount: cannot unmount /alcatel/7.0 : Device busy
umount: return error 1.
WARNING: ...sys,root # unmount /alcatel/7.0 , return error code: 1
m ) When the machine complete the reboot and prompt you for login, you have to login as root user
and execute the following command:
...,sys,root # /SCINSTALL/SCINSTALL start [Enter]
The command as to finish quickly.
9.4.4 Remove Useless Links to NR7.0 Environment
To complete the NR7.0 environment removal you have to remove also some useless links created by product customize, by executing the following commands:
for f in /alcatel/NMS/*/* /alcatel/NMC/*/* /alcatel/NMA/*/* /alcatel/Kernel ; do
if [ h $f ] ; then
ll $f | grep q /alcatel/7.0
if [ $? eq 0 ] ; then
rm $f
fi
fi
done
9.4.5 Remove any NR7.0 SWPDESC

The NR7.0 NMS description is no more useful, so it is better to remove them by entering:
...,sys,root # swremove SWPDESC
9.4.6 Predispose for NR7.1T
Now you can predispose the system like for a NR7.1T fresh installation, with the exception that you do
not have to ask for the instance predisposal, but keep the existing one. You can follow instruction show
hereafter:
a)
The paragraph 5.5 Install NMS Description and NR7 Installation Procedure at page 64 shows how
to retrieve form CD the new NMS description and the installation procedure.
b)
The paragraph 5.6 Predispose for Installation at page 65 shows how predispose for the software.
In particular
1)
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
5.6.2 at page 65 how to predispose for OSKernel.
3)
c)
5.6.1 at page 65 how to start the software predispose procedure.
5.6.3.1 at page 67 how to predispose for 1353NM software.
Skip the paragraph 5.6.3.2 Predispose for 1353NM Instances.
01
3AL 88893 BAAA
226
131 / 226
9.4.7 Review the Master Instance areas
The structure and the size of 1353NM Master instance has been change between NR7.0 and NR7.1T, in
fact a new file system has been created for the 1353NM Master instances, to store all the log and trace
files.
Because of this you have to execute the following procedure:
As root user you have to set the default directory on
...,sys,root # cd /usr/Systems/1353NM_<Inst.Num.>_7.0.Master[Enter]
b)
Change the name of maintenance directory to saveMNT, by entering:

...,sys,root # mv maintenance saveMNT [Enter]
c)
create a new file system one gigabyte large and mount it as:
/usr/Systems/1353NM_<Instance Number>_7.0.Master
By entering the following command:
...,sys,root # scextendfs /usr/Systems/1353NM_<Inst.Num.>_7.0.Master/maintenance \ [Enter]
1000 [Enter]
NOTE: The procedure can ask for adding new hard disk in the volume group, please refer to paragraph 4.2.1.13.1 Disk Mirror Configuration Policy at page 49 the rule for the hard disk choice.
d)
Move the entire contents of saveMNT to the new maintenance, by entering:

...,sys,root # mv saveMNT/* maintenance/ [Enter]
e)
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
Remove saveMNT directory, by entering:

...,sys,root # rm r saveMNT [Enter]
ED
01
3AL 88893 BAAA
226
132 / 226

Meaningful for 1353NM Master only.

9.5 Upgrade from NR7.1 1st.

The software upgrade foresees to reuse the same disk areas already in use, the only action that have to
be done on the disk structure is related to the extension of the /alcatel/7.1 file system to allow the installation of a larger version.
9.5.1 Poseidon Software installation
Poseidon is the license manager daemon software. It usually installed automatically by predisposing the
system for OSKernel 7.1, but in this specific case it have to be installed manually by executing this procedure:
a)
Logging the system as root.
b)
Insert the CD SWPOSCONFV7.1.0 volume 1/4 in the device.
c)

d)
Install the software by entering:

...,sys,root # swinstall s /SD_CDROM Poseidon [Enter]
e)
Check the report for any error, and them dismount the CD by entering:
...,sys,root # umount /SD_CDROM [Enter]
f)
Remove the CD from device.
9.5.2 Shutdown OSKernel Services

The 1353NM system is already stop, you have now to shutdown also the OSKernel services by entering
the following command:
...,sys,root # /alcatel/Kernel/script/KernelServices stop[Enter]
9.5.3 Remove 1353NM and OSKernel NR7.1 1st. Software
N.B.
BE CAREFUL IN TYPING THE FOLLOWING COMMANDS.
This is the commands to remove the entire 1353NM from the installation three:
...,sys,root # cd
...,sys,root # rm
...,sys,root # rm
...,sys,root # rm
...,sys,root # rm
/alcatel/7.1/NMA[Enter]
Rf ANTPSRV DATAPLUG DIMQ3SIM EML* FT* GENERICHOL OBS*[Enter]
Rf OPETOOLS SECPLUG SHCORE SIMDSG SRVADMIN [Enter]
Rf SWPADMIN TSTMGR[Enter]
f /usr/local/data/Install_Wizard/.register/1353NM.list[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
This is the commands to remove OSKernel from the installation three:

...,sys,root # ls d /alcatel/7.1/NMC/* | \[Enter]
egrep v GENOS|ISN|OSRES|OSCLS | \[Enter]
xargs i rm Rf {}[Enter]
...,sys,root # rm f /usr/Systems/Global_Instance[Enter]
...,sys,root # rm f /usr/local/data/Install_Wizard/.register/OSKERNEL.list[Enter]
ED
01
3AL 88893 BAAA
226
133 / 226
The amount of space defined for OSKernel and 1353NM must be 5800 MB, to guarantee these disk
space in /alcatel/7.1 enter the following commands:
...,sys,root # scextendfa /alcatel/7.1 O 5800 [Enter]
File system extension script will check the available space and will extend the file system when needed.
Sometime it will be not possible to extend the file system without reboot, in this case a message like this
will be issued:
/alcatel/7.1 successfully extended, new size will be available on next
reboot
___________________________________________________________________________
System need reboot x complete extension of file system current in use_
___________________________________________________________________________
In this case you have to reboot the system by entering:
...,sys,root # reboot [Enter]
9.5.5 Upgrade SWPDESC and Installation Scripts
The NR7.1 1st. NMS description is no more useful, so you have to remove them by entering:
...,sys,root # swremove SWPDESC
The install the new NMS description foreseen for NR7.1T paragraph 5.5 Install NMS Description and NR7
Installation Procedure at page 64.
9.6 Install and Customize OSKernel and 1353NM

Now both NR7.0 or NR7.1 1st. software have been removed, and the system is ready for the installation
of NR7.1T OSKernel and 1353NM.
9.6.1
Install and Customize NR7.1T OSKernel
Before to proceed with the installation and customize of the new OSKernel is necessary to restore the
OSKernel data file saved previously (see paragraph 9.4.2 at page 129):
...,sys,root # mkdir /alcatel/7.1/Kernel/data [Enter]
...,sys,root # cp p /alcatel/inittab.base /alcatel/7.1/Kernel/data [Enter]
Then, you can install and customize the OSKernel 7.1.1 and related patches as foreseen by the NR7.1T
normal installation. The installation procedure is shown at: Install and Customize OSKernel paragraph
3.4.1 (Quick) at page 25 or 7.1 at page 93.
1AA 00014 0004 (9007) A4 ALICE 04.10
9.6.2
Install and Customize NR7.1T 1353NM
The you have to install and customize 1354NM 7.0.12 and related patches foreseen by the NR7.1T normal
installation. The installation procedure is shown at: Install and CUstomize NMS and NMC paragraph
3.4.2 at page 3.4.2 or Install and Customize 1353NM paragraph 7.2 at page 97.
ED
01
3AL 88893 BAAA
226
134 / 226

9.5.4 Extend /alcatel/7.1 file system
1AA 00014 0004 (9007) A4 ALICE 04.10

9.6.2.1 Special instructions

The 1353NM instance identifier can not be change during the upgrade, that means you have to provide
the same instance identifier number retrieved by the NR7.0 configuration.
9.7 System configuration and Final Integration

To really complete the upgrade, when all the 1353NM machine have been upgrade, you have to execute
perform the System Configuration of the entire 1353NM (Refer to 1353NM Administration Guide) and
then Final Integration as show at chapter 8 at page 119.
ED
01
3AL 88893 BAAA
226
135 / 226
9.8 Upgrade Troubleshooting
9.8.1 Upgrade from OSConf 7.0.5 P03

A problem has been found upgrading to OSConf 7.1.0 when the machine has been installed with HPUXt Edition September 2002, that is the base of OSConf 7.0.5 P03. The problem occurs upgrading the
HPUXt On Line Diagnostic, this paragraph shows how to prevent it or how to proceed in case of failure.
To prevent the error you have to change the On Line Diagnostic upgrade procedure as shown in the paragraph 9.8.1.1 between OSConf 7.1.0 installation and OSConf 7.1.0 scupgrade start.
If the procedure already get failed, you have to modify it as shown at paragraph 9.8.1.1, and then force
the installation script to retry HPUXt On Line Diagnostic and proceed in the installation by renaming a
specific file and reboot the system as shown here:
...,sys,root # rm /SCINSTALL/execution/01005SC.UpgOnlineDiag.in_progress [Enter]
...,sys,root # cp p /SCINSTALL/upgscripts/01005SC.UpgOnlineDiag \[Enter]
/SCINSTALL/execution/[Enter]
...,sys,root #reboot[Enter]
After the system reboot the installation will restart trying again the HPUXt On Line Diagnostic.
9.8.1.1 Change On Line Diagnostic Upgrade Procedure.
Here the information to fix the error in HPUXt On Line Diagnostic upgrade script.
a)
Login as root.
b)
Save the current version
c)
Change the file /SCINSTALL/upgscripts/01005SC.UpgOnlineDiag by adding a set command at the

line begin this way:
Change line 122 from:

Message NOTE: Remove patch PHSS_28844
To:
set e ; Message NOTE: Remove patch PHSS_28844
3)

Message NOTE: Remove old Product: \$SCI_PRD_NAME $ProductVers\
To:
set e ; Message NOTE: Remove old Product: \$SCI_PRD_NAME $ProductVers\
4)
ED

swlist MCSG_Patches.PHSS_28844 1>/dev/null 2>& 1
To
set +e ; swlist MCSG_Patches.PHSS_28844 1>/dev/null 2>& 1
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
Exit vi saving the made changes.
01
3AL 88893 BAAA
226
136 / 226

This paragraph show how to fix or prevent known problem of the upgrade procedure.

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

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

HPUXt Operating System is the first software installed, it is stored in some dump files automatically
restored by the installation procedure. A fault during the HPUXt installation can not be recovered the
installation have to be started from the beginning.
The HPUXt installation will be completed when the following message will be shown on the console:
******* The HPUX software has been successfully restored *******
But the error recovery will be possible only after the first reboot of the system performed just after the message:
1AA 00014 0004 (9007) A4 ALICE 04.10
***** The System reboots automatically, please wait *****
ED
01
3AL 88893 BAAA
226
137 / 226
10.3 Recoverable Faults

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

(noninteractive) (jobid=tlvhhx0027)
* Session started for user root@tlvhhx.
* Beginning Selection
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.
ERROR:
=======
08/05/03 16:41:44 METDST END swinstall SESSION

(noninteractive) (jobid=tlvhhx0027)
EXIT CODE: 1
SCinstall: Error end SCINSTALL
In this case you have to identify the reason of the fault (example: cdrom switched of, action on the target
depot, etc.), remove it, then recover the fault trying to preform again the failed action following this procedure:
Logging the system as root user.
Change the default directory on /SCINSTALL/execution:

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

...,sys,root # ls *.in_progress [Enter]
...,sys,root # mv <file_name>.in_progress <file_name> [Enter]
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
1AA 00014 0004 (9007) A4 ALICE 04.10
The procedure will try again the installation of the failed package.
ED
01
3AL 88893 BAAA
226
138 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10

10.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 proceed.
When the error has been recovered remove the file /SCINSTALL/scextendfs.error_msg to remove the
message to remove the message at login time.
ED
01
3AL 88893 BAAA
226
139 / 226
scmanageswp script can exit for some reason, the situation in which is possible to operate to exit from
the error are the following:
The procedure exit with error because there is a pending installation process in progress, see
paragraph 10.3.2.1.
The procedure has been abnormally terminated, see paragraph 10.3.2.2.
10.3.2.1 Pending Installation Process

At startup time scmanageswp checks if there is any pending installation process,
=>>> ERROR : SCINSTALL System startup script file detected.
This indicate a pending installation process !!!
=>>> ERROR
: Current program terminated.
Execute the workaround describes on paragraph 10.3.1 at page 138,for recover the mistake.
10.3.2.2 scmanageswp Abnormally Terminated
scmanageswp uses a flag directory to prevent multiple execution from different shells, if you start the
script when another it is already running it will terminate issuing the message:
=>>> ERROR : SCMANAGESWP procedure already running on system.
Multi activation is not allowed !!!
=>>> ERROR
: Current program terminated.
May occurs the flag directory it is not removed, for example when it is executed via telnet and a3 network
failure abnormally terminated the connection, in this case you have to manually unlock the synchronization
mechanism. Before proceed with the unlock you have to check there are no other scmanageswp running
instance by entering the commands:
...,sys,root # export UNIX95=true [Enter]
...,sys,root # ps fC scmanageswp [Enter]
N.B.
Be careful, double check the command before press [Enter], because the ps command parameter can not be checked.
If ps command does not issue any line you can proceed with the manual unlock by entering the command:
...,sys,root # rm r /tmp/.scswpsession [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Then start again scmanageswp.
ED
01
3AL 88893 BAAA
226
140 / 226

10.3.2 Recoverable Faults Managing SWP
10.4 Kerberos Problems

There are two Kerberos known problems with possible troubleshooting.

10.4.1 Kerberos kdcd Process Not Running
It has been experienced the failure of Kerberos kdcd daemon process, the result of this failure is that no
activities can be performed on the system. To check if the kdcd process is running you can enter the command:
...,sys,root # ps edf | grep kdcd[Enter]
The output have to be like:
,sys,root # ps edf
root 573
1
root 916 573
root 9416 9363
|
0
0
0
grep kdcd
12:20:23 ? 0:01 /opt/krb5/sbin/kdcd l /dev/null
12:20:27 ? 0:04 /opt/krb5/sbin/kdcd l /dev/null
16:21:30 pts/ta
0:00 grep kdcd
The first workaround applicable is try to start it again by entering the command:
...,sys,root # /sbin/init.d/krbsrv start [Enter]
If after the manual restart 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.
10.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:
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)
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
Start the kdcd process by entering the command:

ED
01
3AL 88893 BAAA
226
141 / 226
Sometimes a file systems can get full, this situation can occur because different reasons, hereafter some
of them are explain.
10.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]
10.5.2 Device full on /usr and /home

These two file systems can get full because of core file created by program termination, in this case is suggested to remove or copy in a different location the core files.
If the core file removal is not enough to reach an appreciable amount of free space, it is possible to extend
the file system. The file system extension can be executed when there are not allocated physical extent
on the logical volume or there are unused hard disks, and it is possible to perform a reboot of the system.
1AA 00014 0004 (9007) A4 ALICE 04.10
The command vgdisplay vg00 can be used to check how many free Mbyte 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
VG Write Access
VG Status
Max LV
Cur LV
Open LV
Max PV
Cur PV
Act PV
Max PE per PV
VGDA
PE Size (Mbytes)
Total PE
Alloc PE
Free PE
Total PVG
Total Spare PVs
Total Spare PVs in use
ED
/dev/vg00
read/write
available
255
15
15
16
3
3
5372
6
32
813
682
131
1
0
0
01
3AL 88893 BAAA
226
142 / 226

10.5 Device Full

If it is too small, you can check the availability of hard disk by entering the command:
The command output will be like the following:
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
c2t2d0
8680 0/0/2/0.2.0
_(free)_ ______ __________
c4t8d0
8680 0/4/0/0.8.0
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)_ ______ __________
___________________________________________________________________________
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 OSCluster 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
___________________________________________________________________________
1AA 00014 0004 (9007) A4 ALICE 04.10
The message System need reboot x complete extension of file system current in use means that the
extension will not available until system reboot.
ED
01
3AL 88893 BAAA
226
143 / 226
Sometimes the processes specified in /etc/inittab file whit option respawn are not respawned correctly, it this case can be useful perform the following procedure:
a)
b)
c)
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
e)
ED
Login the system as root user,

Replace the keyword respawn with once in the line corresponding to the not started process.
Ask init to reread the configuration file by entering:
...,sys,root # init q [Enter]
Restore back the keyword respawn instead of once just modified.
Ask again init to reread the configuration file by entering:
...,sys,root # init q [Enter]
01
3AL 88893 BAAA
226
144 / 226

10.6 Inittab Process Not restarting

10.7 Installing and Configuring Mirror Disk/UXt

Sometimes the Mirror Disk/UXt is not chosen at HPUX installation time, and someone decide to install
it later, in this case you can apply this procedure.
10.7.1 Mirror Disk/UXt Installation Prerequisite.
The Mirror Disk/UXt requires the appropriate HP license to authorize the its usage, and the system shutdown due to two reboots.
10.7.2 Mirror Disk/UXt Configuration Prerequisite
To be able to properly configure Mirror Disk/UXt you must be sure to have enough hard disk available
to store another copy o the entire file system. The highest level of availability is reached by assigning hard
disks belonging to different SCSI chains. Refer to paragraph 4.2.1.13.1 Disk Mirror Configuration Policy
at page 49.
10.7.3 Mirror Disk/UXt Installation
When you not choose the mirror configuration the Mirror Disk/UXt is not installed, here the procedure
to manually install it:
a)
b)
c)
d)
e)
f)
Login the system as root and ask all the user to log out the system.
Insert the CD with label SWPOSCONFV7.1.0 volume UX64_2 in the device driver end mount it
by entering:
To Install the Mirror DIsk/UXt you have to enter the following command, but be careful because the
machine will be automatically rebooted:
...,sys,root # swinstall s /SD_CDROM/MirrorDisk.sd x autoreboot=true LVM [Enter]
When the system will be ready again, you have to login again as root.
Mount the CD with:
Install the Mirror Disk/UXt patches by entering the command, but be careful because the machine
will be automatically rebooted:
...,sys,root # swinstall s /SD_CDROM/MirrorPatch.sd x autoreboot=true \ [Enter]
x reinstall=true x software=* [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
When the system will prompt you for login check in /var/adm/sw/swagent.log for any error met in the software of patch installation.
ED
01
3AL 88893 BAAA
226
145 / 226
A specific configuration script is provided to aid in the Mirror Disk/UXt configuration, you have to enter
the command:
...,sys,root # scmirrorfs [Enter]
And the procedure will show you the current system disk configuration:
___________________________________________________________________________
Disks Selection
Mirroring need Alternate Boot disk on Volume Group:vg00
___________________________________________________________________________
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
c2t2d0
8680 0/0/2/0.2.0
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:
You have to select the disk for the mirror copy by follow the guide line shown at paragraph 4.2.1.13.1 Disk
Mirror Configuration Policy at page 49. And as soon as the amount of disk space requested will be
reached the procedure will configure the mirror by issuing messages like the following:
NOTE:
Updating of LVM physical volume group information file
NOTE:
Group
Set Logical Vol allocation policy = PVGstrict on Active Volume
NOTE:
Preparation of Mirroring Volume Group: vg00
NOTE:
Mirroring all Logical Volume of Volume Group: vg00
1AA 00014 0004 (9007) A4 ALICE 04.10
=>Thu Jul 29 12:34:33 METDST 2004

....... Mirroring Logical Volume:/dev/vg00/lvol1,
with Allocation policy contiguousy
ED
01
3AL 88893 BAAA
226
146 / 226

10.7.4 Mirror Disk/UXt Configuration

APPENDIX A SYSTEM TIPS

In this appendix some system tips are show.
A.1 Find the CDROM Device File

Some activities require to know with is the CDROM device drive, hereafter the procedure to know it.
First of all you have to login the system as root user, and enter the following ioscan command:
...sys,root# ioscan fnC disk [Enter]
The ioscan command output will be like this one:
,sys,root # ioscan fnkCdisk
Class
I H/W Path
Driver S/W State
H/W Type
Description
======================================================================
disk
0 0/0/1/1.2.0
sdisk CLAIMED
DEVICE
SEAGATE ST39204LC
/dev/dsk/c1t2d0
/dev/rdsk/c1t2d0
disk
1 0/0/2/0.2.0
sdisk CLAIMED
DEVICE
SEAGATE ST39204LC
/dev/dsk/c2t2d0
/dev/rdsk/c2t2d0
disk
2 0/0/2/1.2.0
sdisk CLAIMED
DEVICE
HP
DVDROM 305
/dev/dsk/c3t2d0
/dev/rdsk/c3t2d0
disk
3 0/4/0/0.8.0
sdisk CLAIMED
DEVICE
SEAGATE ST39236LC
/dev/dsk/c4t8d0
/dev/rdsk/c4t8d0
disk
4 0/4/0/0.9.0
sdisk CLAIMED
DEVICE
SEAGATE ST39236LC
/dev/dsk/c4t9d0
/dev/rdsk/c4t9d0
disk
5 0/7/0/0.12.0 sdisk CLAIMED
DEVICE
SEAGATE ST39236LC
/dev/dsk/c5t12d0
/dev/rdsk/c5t12d0
disk
DEVICE
SEAGATE ST39236LC
/dev/dsk/c5t13d0
/dev/rdsk/c5t13d0
disk
DEVICE
SEAGATE ST39173WC
/dev/dsk/c5t14d0
/dev/rdsk/c5t14d0
You have to identify a CDROM or a DVDROM device in the description column. Then you can double
check the device file by entering the diskinfo command with the raw device associate to it.
...,sys,root # diskinfo /dev/rdsk/<device file>
The diskinfo command related to the previous example will be:
,sys,root # diskinfo /dev/rdsk/c3t2d0
SCSI describe of /dev/rdsk/c3t2d0:
vendor: HP
product id: DVDROM 305
type: CDROM
size: 584768 Kbytes
bytes per sector: 2048:
1AA 00014 0004 (9007) A4 ALICE 04.10
The correct device type have to be CDROM.
ED
01
3AL 88893 BAAA
226
147 / 226
To safety stop the system it is suggested to perform the system shutdown. This activity allows to stop the
entire system by executing the shutdown procedure of each software component. The shutdown command is allowed only by root user and foresees many switches, the most used are r and h . The first
one performs the automatic reboot, and the second have to be used when you have to switch off the system power supply, because it halts the system.
A.2.1 System Shutdown with Reboot
The system shutdown command allows to perform the system reboot, by entering:
...,sys,root # shutdown r now [Enter]
A.2.2 System Halt
The system shutdown command allows to perform the system switch off, by entering:
...,sys,root # shutdown h now [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Wait until the RUN lamp is switched off or the system status gets in SHUT on the front display
before switch off the power supply.
01
3AL 88893 BAAA
226
148 / 226

A.2 System Shutdown

APPENDIX B NMS/NMC SPECIFIC DATA

Alcatel Application Software is divided in two classes: Network Management Subsystem (NMS) and Network Management Components (NMC). The former class identifies systems that allow the Element Management (1353) or the Network Management (1354/1355), the latter one identifies optional functionalities
separately sold.
B.1 NMS Class

NMS are the basic items for installation purpose, them have a specific predisposal activity that allow them
the correct behavior, in the following list the NMS that can be predisposed by OSConf for NR7.0:
n OS_KERNEL V7.1
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 OSCluster Protection type: Master ` Client ` Spare system ` ( only for 1359HA OSCluster )
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.1
1354BMATM V7.0
1AA 00014 0004 (9007) A4 ALICE 04.10
1354BMETH V7.0
1355VPN
V4.0
(*) Not useful for Client
ED
01
3AL 88893 BAAA
226
149 / 226
The NMC are software components, usually installed to provide additional feature only on an already
installed NMS (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 predispose
NMC Name
NMS Dependencies.
1359IOO V5.0
1353NM 7.0 and 1354RM
1359ISN V4.0
1354RM
1359HA_OSRES V7.1
1353NM, 1354BM and 1354RM
type:
Master `
2 Client `
4 Client `
8 Client `
1359HA_OSCLS
1353SH V7.0 (1353SHBKW)

1353NM 7.0
type:
Client `
V7.1
1353NM 7.0, 1354BM and 1354RM

type:
Client `
type:
Client `
1AA 00014 0004 (9007) A4 ALICE 04.10

type:
Client `
ED
01
3AL 88893 BAAA
226
150 / 226

B.2 NMC Class

B.3 Disk Requirement Tables

The following table shows the disk space requested for swap, program installation, and depot packages.
The value are specified in M bytes
NMS
Swap Required
Software Size
Depot Package Size
OSKernel
100
2000
420
1353NM(*)
500
4120
1700
1354BMATM
500
1120
100
1354BMETH
500
1120
170
1354RM
500
1120
900
1355VPN
500
500
1359HA OSCLS
200
10
1359HA OSRES
100
1359ISN
N.A.
N.A.
70
1359IOO
N.A.
N.A.
15
Table 12. Disk requirements for NMS Software
NMS
Master Small
Swap
1353NM
Data
Master Medium
Swap
Data
Master Large
Swap
Data
Presentation(*)
Swap
Data
500
3000
1500
5000
2500
9000
250
150
1354BMATM
1500
3000
3500
5000
7500
9000
2000
200
1354BMETH
1500
3000
3500
5000
7500
9000
2000
200
1354RM
1500
3000
3500
5000
7500
9000
2000
400
500
3000
1355VPN
N.A.
N.A.
1359HA OSCLS
N.A.
N.A.
N.A.
1359HA OSRES
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
Table 13. Disk Requirements for NMS Instances.
1AA 00014 0004 (9007) A4 ALICE 04.10
(*) The presentation does not foreseen the 1359HA OSCluster protection.
ED
01
3AL 88893 BAAA
226
151 / 226
B.4 Alcatel CD Codes
CD Label
CD Code
Description
SWPOSCONFV7.1.0
3AL 72881 ABAA 01
hpuxt 11i installation tool.

Six CD with the following labels forms it:
UX64_1. UX64_2, 1/4, 2/4, 3/4 and 4/4.
SWPOS_KERNELV7.1
3AL 88872 ABAA 02
Alcatel OSKernel and installation tools.
SWP1353NM_APPV7.0.12
3AL 89055 ABAA 01
Alcatel 1353NM Element Manager.
SWP1354BM_ATMV7.0
3AG 23910 AAAA 01
Alcatel 1354BM ATM Manager.
SWP1354BM_ETHV7.0
3AG 23910 AAAA 01
Alcatel 1354BM Ethernet Manager.
SWP1354RM_APPV7.1
3AL 61339 ABAA 02
Alcatel 1354RM Regional Manager.
SWP1355VPN_APPV4.0
3AL 72168 AAAA 01
Alcatel 1355VPN Virtual Private Network.
SWP1359HA_OSCLSV7.1
3AL 88115 ABAA 01
Alcatel 1359HA OS Cluster Software.
SWP1359HA_OSRESV7.1
3AL 88118 ABAA 01
Alcatel 1359HA OS Resilience Software.
SWP1359IOO_APPV5.0
3AL 88332 AAAA 02
Alcatel 1359IOO Generic OSOS interface Software.
SWP1359ISN_APPV4.0
3AL 88233 AAAA 01
Alcatel 1359ISN Open Interface Software.
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 14. Alcatel NR7.1T CD codes
ED
01
3AL 88893 BAAA
226
152 / 226

The following table provides the Alcatel CD codes of all media provided with NR7.1.

APPENDIX C GOGLOBALUX INSTALLATION AND CONFIGURATION
C.1 GoGlobalUX Installation on HPUX System

The GoGlobalUX software is already installed on the HPUX system foreseen for Alcatel TMN application.
C.2 GoGlobalUX 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>
<username>
<password>
Continue with:
ftp>
ftp>
ftp>
ftp>
= is the IP address of the Unix machine where GOGlobal is installed;

= is the username of UNIX operator;
= is the password relative to the <username> indicated.
cd /opt/graphon/pc [Enter]
bin [Enter]
get go_setup_2*.exe [Enter]
quit [Enter]
b)
Double click on the executable.
c)
The Install Shield Wizard window will be opened:
Figure 19. GoGlobalUX Logo
1AA 00014 0004 (9007) A4 ALICE 04.10
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 GoGlobalUX/Previous Version C.2.1 at page 156 , otherwise proceed with the next point.
ED
01
3AL 88893 BAAA
226
153 / 226
The next window will be opened showing the welcome message:

d)
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
f)
The Destination Location window will be opened:
Choose your destination location and click on Next to go on. Wait a few seconds the install procedure.
ED
01
3AL 88893 BAAA
226
154 / 226

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:
1AA 00014 0004 (9007) A4 ALICE 04.10
Username
Password
Click on OK. GoGlobalUX will open a connection with the configured machine.
ED
01
3AL 88893 BAAA
226
155 / 226
If installing GoGlobalUX a previous version in installed the application asks you the authorization to remove it by issuing the window:
To upgrade the software press the O.K. button.

Then the script ask you to remove also the GoGlobal user setting, if you want to maintain the connection
descriptions press NO button.
The the previous GoGlobalUX will be removed from the PC.

When the removal will be completed the following window will be shown on the screen.
1AA 00014 0004 (9007) A4 ALICE 04.10
You can now install the new version of the software by stating again the installation application.
ED
01
3AL 88893 BAAA
226
156 / 226

C.2.1 Automatic Removal of GoGlobalUX/Previous Version

C.3 GoGlobalUX license

The GoGlobalUX XEmulator for Microsoftt 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 GoGlobalUX 2.
C.3.1 License servers definition rules

Before to require the GoGlobalUX license(s), you have to decide how many and what will be the license
server machine(s) in your network, in accordance with the following rules:
If you have three or more machines, you have to setup a Three Redundant License Servers configuration, in accordance with the following rules:.
the three license server machines should be located physically close to each other (if possible).
never configure redundant servers with slow communications or dialup links.

With threeserver redundancy,only one of the three servers is master, capable of issuing licenses.
Since all clients must contact the master, all clients must have reliable networking to a single node.
if in your network there are less than three nodes, you have to define a the license server, and all the
required licenses have to be loaded on that server.
On the license server machine(s) will be loaded the license(s) data obtained as showed in the paragraph
C.3.3.
C.3.2 Retrieve License Servers Identity
Meaningful only for the license server machine(s).
When you have selected the license server machine(s), for each of them you have to retrieve the machine
identity by executing the following commands:
a)
Log in as root on the machine.
b)
Get the hostname of the current machine:

..,sys,root # uname
c)
[Enter]
Get the FLEXlm host ID of the current machine:

..,sys,root # /opt/graphon/bin/lmhostid
[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
The obtained data will be used in a successive phase of the license request activity.
ED
01
3AL 88893 BAAA
226
157 / 226
C.3.3 Permanent License Request
After that, you can to require the necessary license(s) to activate GoGlobalUX 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 20. GraphOn License WEB Page
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on GoGlobal Permanent Licenses and the following registration form will appear:
Figure 21. GraphOn License WEB Page Registration
ED
01
3AL 88893 BAAA
226
158 / 226

Meaningful only for the license server machine(s).

Scroll down along the window using the scroll bar and fill the following fields about the required registration
information:
Name
Company
Address & Address2
City
State/Province
Country
Postal Code
Phone
Email Address
(1)
(1)
(1)
(1)
(2)
(1)
(1)
(1)
(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 22. GraphOn License WEB Page Software Agreement
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
ED
01
3AL 88893 BAAA
226
159 / 226

Figure 23. GraphOn License WEB Page License Data Entry

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.
N.B.
Scroll down along the window using the scroll bar and fill the following fields:
Product Code (see the Product Code value on the PURCHASED GraphOn LICENSE FOR ALCATEL USE FOR RESALE document if present)
Host Name (see the paragraph C.3.2)
Host ID (see the paragraph C.3.2)
Now if you have the Three Redundant License Servers configuration you have to set YES in the box
close to the label Are you using redundant servers?, and fill in the three couple of information: Hostname and Hostid with the data of each license server.
1AA 00014 0004 (9007) A4 ALICE 04.10
and click on Get License button to continue.
ED
01
3AL 88893 BAAA
226
160 / 226

Figure 24. GraphOn License WEB Page License Output Example
1AA 00014 0004 (9007) A4 ALICE 04.10
Put the showed data in the license file of the license server machine (see the paragraph C.3.4.1.1) and
click on the Back button to come back to the Product Code window to require (eventually) another license
otherwise, if you are terminated, click on File and Close option to exit from the web browser.
ED
01
3AL 88893 BAAA
226
161 / 226
GraphOn Corp. provides both permanent or demo license, hereafter some information to help you to configure the GoGlobalUXt license files and daemons.
C.3.4.1Permanent License
GoGlobalUXt permanent licenses are provided as network floating point, that meas you have to promote one or three machines a License Server and all the other will be License Client.
To be able to use them you have to perform the following actions:
1)
2)
3)
4)
Store the authorization key in the license file.

Configure the license servers machine(s).
Start the license server daemons.
Configure license client system(s) (if any)
C.3.4.1.1 Store the Authorization Key in the License File.

The first activity is to store the license authorization key previously obtained by GraphOn WEB page (see
C.3.3 at page 158) 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 endofline (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:
1AA 00014 0004 (9007) A4 ALICE 04.10
#
# 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=23jan2002
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
Add TCP port number (27001) at any line beginning with SERVER:
Example from:
SERVER host_c 839dc26
to:
SERVER host_c 839dc26 27001
ED
01
3AL 88893 BAAA
226
162 / 226

C.3.4 GoGlobalUX authorization procedure

C.3.4.1.2 Configure License Server(s)

Now you have to configure License Server machine(s) that need to provide the GoGlobalUX floating license on the network.
C.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, including the license servers hosts themselves.
The easy to proceed is create these files on the license server(s) and them distribute them to the client
when configuring it.
Each time you change the license_server.dat file the changes will be recognize only at next GoGlobalUX statup.
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].
C.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 Server machine(s) you can proceed with the daemon startup.
Because hpuxt startup launch both License and GraphOn Daemons, it is advisable to execute the daemon stop before. The entire procedure will be:
1AA 00014 0004 (9007) A4 ALICE 04.10
...,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 GoGlobalUX 2.0 session from any PC to the
license server machine.
ED
01
3AL 88893 BAAA
226
163 / 226
To be able to access the hpuxt machine via GoGlobalUX you need to get a license, this license will
be granted by the license server(s) via network, that means any hpuxt system (license client) have to
be able to connect the license server(s) via network. Moreover the license server(s) have to be referred
by name.
C.3.4.3.1 Verify License Server Connectivity
Before starting the client machine configuration you have to verify the license server machine(s) connectivity, the easiest way to do it is try a 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 CTRLD
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 6 at page 83 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 System AdMinistration tool (SAM) the system configuration:
..,sys,root # sam
[Enter]
At the end, select on the topdown menu File > Exit.
ED
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 topdown 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.
Doubleclick on Network and Communications then Hosts and Local Hosts File
icons.
1AA 00014 0004 (9007) A4 ALICE 04.10
Then select on the topdown menu File > Exit SAM to finish.
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.
01
3AL 88893 BAAA
226
164 / 226

C.3.4.3Configure License Client System(s)

C.3.4.3.2 Verify License Daemon on Server

When the license server machine(s) are reachable, you can also verify on each one of them if the license
daemons are running on these machine(s). this can be done with the following procedure:
N.B.
This check can be done only if the license server machine(s) are already configured.
..,sys,root # export LM_LICENSE_FILE=27001@<Hostname>
..,sys,root # /opt/graphon/bin/lmstat a [Enter]
[Enter]
If the file license daemons are active, an output like the following will be displayed:
lmstat Copyright (C) 19892002 Globetrotter Software, Inc.
Flexible License Manager status on Fri 12/5/2003 10:07
License server status: 27001@host_c,27001@host_d,27001@host_e
License file(s) on host_c: /opt/graphon/etc/license.dat:
host_c: license server UP (MASTER) v8.2
host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges:
N.B.
(Total of 2 licenses available)
The shown output is related to a three redundant server configuration, if you have a single license server, the data shown with italic font will be not shown.
Otherwise an error message advise you of a problem, check the status of the daemons on the license server them selves.
C.3.4.3.3 Copy the license_server.dat File from a License Server
1AA 00014 0004 (9007) A4 ALICE 04.10
All the configuration precondition are now verified, it is possible to configure the license client machine,
the configuration consists only in creating a copy of the license_server.dat file from a license server machine to this one. Like for servers, when the license_server.dat file is created or modified the daemons
have to be stopped and started to catch the changes.
ED
01
3AL 88893 BAAA
226
165 / 226
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) 19892002 Globetrotter Software, Inc.
Flexible License Manager status on Fri 12/5/2003 10:20
License server status: 27001@host_c,27001@host_d,27001@host_e
License file(s) on host_c: /opt/graphon/etc/license.dat://:
host_c: license server UP (MASTER) v8.2
host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges:
(Total of 5 licenses available)
C.3.4.3.4 ReStart the GraphOn Daemons

Because hpuxt startup 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]
1AA 00014 0004 (9007) A4 ALICE 04.10
Now the system ready, you can open a GoGlobalUX 2.0 session from any PC to the this machine until
at least one license is available on the servers.
ED
01
3AL 88893 BAAA
226
166 / 226

C.3.4.3.3.1 Check the License Server

C.3.5 Add a new license(s)

Sometimes in the system live it is necessary to increase the number of users, that means also the number
of concurrent session have to be increased. To add a new license on a running the license server machine
without close the current open interfaces, you have to proceed this way:
Do not mix permanent floating authorization key with demo one in the same file!
a)
Buy the GraphOn license(s).
b)
Require the authorization key via GraphOn WEB Page providing the same host ID of the already
requested keys (the host id are related to the license servers!). Hereby an example of a new authorization key requested for the license servers already see in the paragraph C.3.4.1.1 at page 162. You
can see the server lines have the same values in the third field that means the same host ID.
#
#
#
the SERVER line, like:
.
.
#
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info=Paolo Rossi\
paolo.rossi@alcatel.it ISSUER=GrapOn \
Corporation ISSUED=08jan2002 NOTICE=Copyright (C) \
19962002 GraphOn Corporation. All Rights Reserved ck=45
c)
You have to copy the INCREMENT line(s) from the just received authorization key a the end of the
/opt/graphon/etc/license.dat file:
N.B.
When a back slash \ is present at the end of line, also the next line have to be included.
..,sys,root # vi /opt/graphon/etc/license.dat
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
ED
[Enter]
Move to last line in file and insert the INCREMENT line(s). For example, if you have the authorization key shown at page 162 active on the system, and receive from GraphOn the one shown
at page 167, the resulting file will be:
#
#
.
.
#
#
#
SERVER host_c 77fd17fe 27001
SERVER host_d 77df65d1 27001
SERVER host_e 7751b870 27001
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
01
3AL 88893 BAAA
226
167 / 226
2)
d)
Save and exit vi file pressing [Esc] and typing :x! and [Enter].
Then ask license daemon to reread 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 GoGlobalUX licenses will be available.
C.3.5.1Demo Licenses
1AA 00014 0004 (9007) A4 ALICE 04.10
GoGlobalUXt 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.
ED
01
3AL 88893 BAAA
226
168 / 226

INCREMENT UX graphon 2.0 permanent 1BB31C150136 \

user_info=Paolo Rossi\
paolo.rossi@alcatel.it ISSUER=GrapOn \
Corporation ISSUED=08jan2002 NOTICE=Copyright (C) \
19962002 GraphOn Corporation. All Rights Reserved ck=45

APPENDIX D HOW TO CREATE A NETWORK DEPOT

After the HPUXt11i 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 OSConf
to create a depot with all the software included in the CDs, 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
OSConf 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:
========================================================================
OSConf 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 CDROM, you can just change the default with another one. The default provided is the CDROM device used to install HPUXt.
* 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 ........
Total CDRoms found =
4
1
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
169 / 226
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c0t5d0
4088 8/12.5.0
c0t6d0
2048 8/12.6.0
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 SWPOSCONFV7.1.0 1/4 into the drive
and press [Enter] when ready
Insert the CD and press return when the CDROM driver led will stop blinking. The procedure will ask you
again for all the disks of the set.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
ED
01
3AL 88893 BAAA
226
170 / 226

Mount Point need 1536MB on /dev/vg00 (PVG0)

___________________________________________________________________________
Disks Selection
Mount Point: /alcatel
___________________________________________________________________________

APPENDIX E PRINTER CONFIGURATION

To configure the printer you have to use hpt 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 characters string assigned to

printer by Customer Network administrator(1).
IP Address
IP Address is the IP network address assigned to

printer by Customer Network 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 beginning of any print job?
LAN Hardware Address
LAN HA is the card hardware address also known

as MAC(2).
Table 15. Printer Configuration Data Requested.

Notes:
ED
It is advisable to declare the printer name as external node with scNMmng.
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
The LAN hardware addres have to be retrieved from the printer itself. Refer to the printer installation 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
01
3AL 88893 BAAA
226
171 / 226
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: (HPUX B.11.11)
I N V E N T
****************************************************************
1) Spooler Administration (superuser only)
2) JetDirect Configuration (superuser 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
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
I N V E N T
****************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
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:

Enter 1[Enter] to add the printer to the local spooler.
ED
01
3AL 88893 BAAA
226
172 / 226

E.1 Configure a Printer Queue within Local Spooler

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 disadvantage 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(0Enable, defaultDisable): [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
nonzero numbers. The values will be used to configure this queue
when 0 is selected.
To abort this configuration operation, press q.
Configurable Parameters:
1)
2)
3)
4)
5)
Current Settings
Lp destination (queue) name:

[<Printername>_1]
Status Log
[(No Log)]
Queue Class
[(Not assigned)]
Default Queue
[NO]
Additional printer configuration...
Figure 25. 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):
1AA 00014 0004 (9007) A4 ALICE 04.10
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 25. ) will be issued again.
ED
01
3AL 88893 BAAA
226
173 / 226

If you want to set the banner page issue, at the next Printer Characteriscs Menu (Figure 25. ) 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:
1)
2)
3)
4)
5)
6)
Current Settings
Model Script:
Default Printing Language
Job Recovery
True EndofJob
Banner Page
PostScript Level
[net_lj4x]
[AUTO]
[ON]
[ON]
[OFF]
[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 25. ) 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING: If there are jobs currently being printed, and the page count is
enabled (i.e. when True EndofJob 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
queued.
OK to continue? (y/n/q, default=y) y [Enter]
ED
01
3AL 88893 BAAA
226
174 / 226

If you are configuring the first printer queue or you want to define this one as the new default queue, enter
4[Enter]

If the spooler is not running the following message will be issued to remind you to startup the spooler
to have the print queue operational (see E.1.1 at page 176).
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
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
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
q [Enter]
****************************************************************
*****]
****
**** ]
****
**** ]]]]] ]]]]] ****
Version E.10.18
**** ]
] ]
] ****
**** ]
] ]]]]] ****
M A I N
M E N U
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
I N V E N T
****************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
3) Diagnostics:
?) Help
q) Quit
Please enter a selection (q quit): q [Enter]
ED
01
3AL 88893 BAAA
226
175 / 226
The hpuxt system spooler is automatically started during at system startup 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
..,sys,root # lpsched[Enter]
ED
01
3AL 88893 BAAA
226
176 / 226

E.1.1 Start the System Spooler

E.2 Configure Printer Booting from Local System

This printer configuration allow to remotely load the printer configuration at printer poweron time. If you
decide to use this method it is advisable to choose two hpuxt system configured to setup 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
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
I N V E N T
****************************************************************

3) Diagnostics:
?) Help
q) Quit
Please enter a selection (q quit):
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter 2[Enter] to select the JetDirect configuration.
ED
01
3AL 88893 BAAA
226
177 / 226
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

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 printers 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]
1AA 00014 0004 (9007) A4 ALICE 04.10
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
nonzero 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
01
3AL 88893 BAAA
226
178 / 226

****************************************************************
*****]
****
**** ]
****
**** ]]]]] ]]]]] ****
Version E.10.18
**** ]
] ]
] ****
**** ]
] ]]]]] ****
JetDirect Configuration Menu
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
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 (superuser only)

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/inetd.sec allows JetDirects 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 configuration menu now.
Do you want to send test file(s) to this printer (y/n, default=n)? y
ED
[Enter]
01
3AL 88893 BAAA
226
179 / 226
1)
2)
3)
4)
text file
(if printer is in PCL or AUTO mode)
PostScript file (if printer is in PS or AUTO mode)
HPGL/2 file
(if it is a HPGL/2 plotter)
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
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
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 (superuser 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Please enter selection: q [Enter]
ED
01
3AL 88893 BAAA
226
180 / 226

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:

****************************************************************
*****]
****
**** ]
****
**** ]]]]] ]]]]] ****
Version E.10.18
**** ]
] ]
] ****
**** ]
] ]]]]] ****
M A I N
M E N U
*****
]
****
******
]
****
User: (root)
OS: (HPUX B.11.11)
I N V E N T
****************************************************************

3) Diagnostics:
?) Help
q) Quit
Please enter a selection (q quit): q [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
..,sys,root #
ED
01
3AL 88893 BAAA
226
181 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
182 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10

APPENDIX F BACKUP AND RESTORE

The OSConf 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 online execution, and are integrated with the other OSConf feature such as disk
mirror management.
ED
01
3AL 88893 BAAA
226
183 / 226
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 corruption that does not allow the HPUX to boot again from disk.
Basically the procedure use three HPUX tools:
1)
2)
3)
fbackup
frecover
Ignite UXt
Backup tool included in the HPUX 11.11 Core

Recover tool included in the HPUX 11.11 Core
Add on HP tool for installation and recovery
The tools reference versions are:

HPUX 11i
11.11
Ignite UXt
B.3.6.82 for HPUX 11.11
This means the scbackup behavior is not guarantee with different version.
F.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 online by Ignite UX with a reduced
HPUXt 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 online or offline depending by the system configuration and status. These are the conditions to be able to perform the online full backup:
1)
2)
3)
If entire file system is mirrored.

If there are no stale phisycal extent.
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
Single Volume Group

Multiple Volume Group
The Single Volume Group configuration has all disks in configuration defined in the same HP Logical Volume Manager (LVM) volume group (VG), where there are also the HPUX 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 Application Backup feature, because often there is application data on different systems that have to be consistent each other.
N.B.
ED
The full backup usage is forbidden with 1359HA OSCluster environment.

01
3AL 88893 BAAA
226
184 / 226

F.1 Full disks backup/restore

F.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 OSCluster 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 OSCluster 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 online copy of any Logical Unit (LUN), this mechanism allow
the online 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 HPUX tools:
1)
2)
3)
4)
fbackup
frecover
Ignite UXt
CommandView SDMt
Backup tool included in the HPUX 11.11 Core

Recover tool included in the HPUX 11.11 Core
Add on HP tool for installation and recovery
Virtual Array Command
The tools reference versions are:

HPUX 11i
Ignite UXt
CommandView SDM
11.11
B.3.6.82 for HPUX 11.11
V1.06.00
This means the scbackup behavior is not guarantee with different version.
F.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)
hpuxt 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 hpuxt 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The manual Single Volume Group Backup usage is forbidden. It must be integrated within 1359HA OSCluster Backup feature.
01
3AL 88893 BAAA
226
185 / 226
F.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 FastWide Differential interface cards.
DLT boot WILL NOT work when attached via singleended SCSI.
DLT boot IS NOT supported for systems that use NIO FastWide Differential SCSI cards (Part number 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 16. Bus types required for DLT to be recognized as a bootable media
BUS
SCSI Interface Card
DLT boot support

?
KClass
HSC
NIO
A2969A FWD
A28655A SE, A28696A FWD
yes
no
see 1 ) and 2 )
HSC
Core
EISA
A4107A FWD
yes
no
no
see 2 )
DClass
TClass
HSC
NIO
A3644A FWD
A28655A SE
no
no
NClass
PCI
FWD
yes
LClass
PCI
FWD
yes
VClass
PCI
A4800A FWD
yes
see 4 )
EClass
NIO
A28655A SE, A28696A FWD
no
see 3 )
GClass
NIO
A28655A SE, A28696A FWD
no
see 3 )
HClass
NIO
A28655A SE, A28696A FWD
no
see 3 )
IClass
NIO
A28655A SE, A28696A FWD
no
see 3 )
CLASS
Notes
Notes:
The HSC and GSC busses are the same busses. These terms are used interchangeably.
3)
NIO and HPPB refer to the same bus.
4)
ED
This class system has two internal bus types, HSC and NIO. DLT is only bootable from the HSC
bus.
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
IPR (Independent Peripheral Release). A firmware upgrade (at least 4.3, product number
B6044AA) is required to enable tape boot for the VClass. The release date for firmware upgrade version 4.3 is September 1998. Contact your HP representative about required firmware
upgrades.
01
3AL 88893 BAAA
226
186 / 226

F.3 Restrictions

F.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.
F.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 backup time, the mirror rebuild is not managed directly by the restore procedure, but it must activated separately.
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 appendix F.5.3 at page 206).
F.3.4 Restriction on Console
The fbackup is executed in single user mode during the HPUX 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.
F.3.5 Required disk space
The Ignite UX tool require at least 32Mbyte free in the file system where /var directory is located.
F.3.6 Compatibility
The scbackupscrestore version 2.0 in not compatible with the previous version of the Alcatel
backuprestore 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.
F.3.7 Restriction on Backup
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
3AL 88893 BAAA
226
187 / 226
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)
2)
3)
Split the mirror disk, creating a offline copy of the entire system.
Perform the backup of the off line copy
Merge back the offline copy in the mirror disk configuration.
Off line:
1)
2)
3)
Prepare HPUX system to execute standard backup at HPUXt Run Level 2.

Perform the backup during the HPUX system reboot.
Reboot the system to restore it in service.
F.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
...,sys,root # scbackup t 0
d)
To increase the timeout to three hours.

To disable the timeout.
The script will ask you to enter the HPUX 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>>:
1AA 00014 0004 (9007) A4 ALICE 04.10
Enter the HPUX 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>).
ED
01
3AL 88893 BAAA
226
188 / 226

F.4 FULL BACKUP

F.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 BE NOT WRITEPROTECT !
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 01Dec2003 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!
F.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]
1AA 00014 0004 (9007) A4 ALICE 04.10
Print the output of these two commands and store it with the IRT, them can be useful in case of disk failure.
ED
01
3AL 88893 BAAA
226
189 / 226
When the IRT creation is completed, the scbackup goes to the next query require entering the HPUX
device file for the fbackup, by issuing the message:
Enter tape device for Fbackup <default=<tape_device>>:
Enter the HPUX 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 online backup.
F.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 prepare 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 shutdown 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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 !!!
*****************************************************************************
ED
01
3AL 88893 BAAA
226
190 / 226

F.4.3 Backup the entire disks contents

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 destroyed.
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
01Dec2003 14:28
Execute Backup
Execute Backup
: Please MOUNT TAPE Volume 1
: Start
Backup ...
: End Successfully
*****************************************************************************
DATA ARE SUCCESSFULLY BACKUPED
*****************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
**************************************************
Remove Tape media and recommended label is:
hosta Fbackup Volume x of n
01Dec2003 14:26 Content: Full backup
**************************************************
ED
01
3AL 88893 BAAA
226
191 / 226
After the full online backup the backup logical volumes will be reduced.

**************************************************
MERGEDELETE process
Start MERGEDELETE process activated on backup Logical Volumes
MERGEDELETE End Successfully
*****************************************************************************
ONLINE BACKUP End Successfully
1AA 00014 0004 (9007) A4 ALICE 04.10
*****************************************************************************
ED
01
3AL 88893 BAAA
226
192 / 226

F.4.3.1.1 Online Full Backup Error Management

If problems occour during execution of sconlinebackup, the disks configuration will be automatically restored. 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 F.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 (BackupRestore 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.
*****************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
If the user decides to proceed, the script will work as previously described in this chapter.
ED
01
3AL 88893 BAAA
226
193 / 226
F.4.3.1.1.1 Full Mirror faults
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 doesnt meet the requirements 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
*****************************************************************************
F.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 procedure will be activated at the system startup in case of failure (sconlinebackup_recover).
F.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
/var/adm/syslog/sconlinebackup_recover.log info about the MERGE_DELETE/RECOVER phase.
1AA 00014 0004 (9007) A4 ALICE 04.10
/var/adm/syslog/fbackup.log
ED
records information related to the SPLIT phase.
keeps the full online FBACKUP information.
01
3AL 88893 BAAA
226
194 / 226

The check on the system full mirror can fails for two main reasons:

F.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 uncorrectable 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
1AA 00014 0004 (9007) A4 ALICE 04.10
*****************************************************************************
ERROR:
during data COPY phase
See ONLINE backup log: /var/adm/syslog/sconlinebackup.log
After correction run again procedure sconlinebackup.
*****************************************************************************
ED
01
3AL 88893 BAAA
226
195 / 226
If the user forget to mount the tape and the mount timeout expires, the process terminates with the message 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
*****************************************************************************
02Dec2003 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.
F.4.3.1.2 MergeDelete problems
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
3AL 88893 BAAA
226
196 / 226

F.4.3.1.1.5 Timeout expiration

F.4.3.2Standard Full backup

Proceding with the standard full backup, in order to guarantee the contents of the files it is required to shutdown of the Alcatel TNM applications and reboot the HPUX 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 shutdownreboot 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 SHUTDOWNREBOOT.
*****************************************************************************
*****************************************************************************
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 specified 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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
Enter time in SECONDS [decimal integer or now] >
N.B.
ED
If you are performing the backup of a 1353SH Master, 1354RM IM, 1354NN IM, or the main CoHosted system, it is advisable to ask also the user logged on the presentation to exit.
01
3AL 88893 BAAA
226
197 / 226
After the specified time the system will be shouted down and rebooted.
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 destroyed.
At the end of the fbackup the system will proceed with the startup as usual, and the result of the activity
will be available in the file /var/adm/syslog/fbackup.log.
1AA 00014 0004 (9007) A4 ALICE 04.10
Moreover a message with the backup result will be shown at any login.
ED
01
3AL 88893 BAAA
226
198 / 226

During the HPUX startup the fbackup will be automatically started.
F.4.3.2.1 Login messages

At the end of full backup, just in case of problems, you will find one of the following messages:
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.
Delete the file /var/adm/syslog/fbackup.msg to remove the login message:
******************
02Dec2003 10:30
THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************
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
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 remove the login message:
******************
THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************
02Dec2003 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
Note: If you remove file: /var/adm/syslog/fbackup.msg cancel this message
ED
01
3AL 88893 BAAA
226
199 / 226
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 recreates the LVM
disk configuration existing at backup time, that means the current contents of the disk will be destroyed. The second phase recovers the contents of the backup file systems.
F.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 HPUXt 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.
F.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
P0
8/4.8
Random access media
P1
8/4.3
Sequential access media
P2
10/12.12
Random access media
f)
Boot from tape by enter the command:

boot p<x>
where: p<x>
g)
is the path number corresponding to tape drive (P1 in the example).
Do not interact with IPL by entering n at query:
1AA 00014 0004 (9007) A4 ALICE 04.10
Interact with IPL (Y, N or C) >
ED
01
3AL 88893 BAAA
226
200 / 226

F.5 FULL RESTORE

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 HPUX in minimum configuration. 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 userinterface must be
used to correct them... Noninteractive 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]
++++
[
[
[
[
[
Reboot
Install HPUX
Run a Recovery Shell
Advanced Options
Read SysAdmin Message
]
[
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 (see
section F.5.1.2 at page 202 for more information).
1AA 00014 0004 (9007) A4 ALICE 04.10
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:
NOTE:
tlinstall is searching filesystem please be patient
In this case you can force it to proceed by typing [ctrl]c
ED
01
3AL 88893 BAAA
226
201 / 226
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 F.5.2 page 203.
F.5.1.2Interactive IRT Restore
1AA 00014 0004 (9007) A4 ALICE 04.10
T.B.D.
ED
01
3AL 88893 BAAA
226
202 / 226

l)
F.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 GoGlobalUX 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 HPUX 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:
hosta Fbackup Volume x of n
01Dec2003 14:26 Full Backup
**************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
Press Enter to continue
ED
01
3AL 88893 BAAA
226
203 / 226
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 F.5.4.1 at page 209 to see the foreseen warning message and the tips for check them.
i)
The script issue the following message to ask you the authorisation to change the HPUX 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.
k)
Dont warry for the messages like the following:

frecover(1075): moved emsagent to emsagent.2510 since it was executing. Remove emsagent.2510 when done.
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):
frecover(5424):
frecover(5433):
frecover(5412):
frecover(5411):
incorrect volume mounted;

expected volume 1, and got 2
Do you wish to continue using this volume?([yY]/[nN]) n
Do you wish to try to salvage this volume?([yY]/[nN]) n
Do you wish to try a different volume? ([yY]/[nN]) y
PLEASE MOUNT next TAPE Volume
1AA 00014 0004 (9007) A4 ALICE 04.10
Mount the correct tape when the previous message appears, and then press ENTER at the
request.
The frecover can take 150% of the backup time.
l)
ED
At the end of the restore, if the system was mirrored at the backup time, the procedure will give you
the message reported at follows.
01
3AL 88893 BAAA
226
204 / 226

g)

**************************************************
Frecover end successfully
Unload Fbackup Tape
*****************************************************************************
NOTE:
The restored data was mirrored at the backup time.
You can use the procedure scmirrorfs to rebuild the mirror:
scmirrorfs [<vgname>]
*****************************************************************************
Press Enter to continue
If you like to rebuild the mirror, you can activate the script scmirrorfs when the backup is ended (refer
to appendix F.5.3 at page 206 for an example).
m ) After you press [Enter] the creation of Physical Volume Group 0 will be activated.
*****************************************************************************
Make PVG0 for volume groups: vg00
*****************************************************************************
=>Wed Feb 11 16:40:10 MET 2004
=>START:
OSConf File(s) System Creation of Physical Volume Group 0
NOTE:
NOTE:
Set Logical Vol allocation policy to PVGstrict x select Volume Group
=>Wed Feb 11 16:40:16 MET 2004

=>END:
OSConf File(s) System Creation of Physical Volume Group 0
n)
When the restore is completed the system must be reboot again to perform the HPUX startup 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.

o)
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
p)
When the system will be ready again you can perform the Alcatel TNM application data restore following the appropriate recovery procedure (if any), and then startup again the application too.
If the backuped machine was configured with mirror configuration you have to proceed with Restore Mirror Condifuration paragraph F.5.3 at page 206.
ED
01
3AL 88893 BAAA
226
205 / 226
The full restore function does not cover mirror disk configuration, it restores the entire file system, including
Disk Mirror/UXt but it does not configure the mirror. The reasons of this choice are two:
1)
hp IgniteUXt 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 OSConf provides a specific script scmirrorfs to setup the mirror
configuration again.
To be able to setup 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 recognize 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.
..,sys,root
scmirrorfs vg00
[Enter]
=>Tue Dec
2 16:29:05 MET 2003
=>START:
OSConf File(s) System Mirroring
Hardware detection in progress, please wait ........
Total CDRoms
found =

_______________________________________________________________________________
Disks Selection
1AA 00014 0004 (9007) A4 ALICE 04.10
Mirroring need Alternate Boot disk on Volume Group:vg00

_______________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
_______________________________________________________________________________
ED
01
3AL 88893 BAAA
226
206 / 226

F.5.3 Restore MIrror Configuration
8680 0/0/1/1.2.0
Pri_Boot _Main_
vg00
c2t2d0
8680 0/0/2/0.2.0
_(free)_ ______
_____________
c4t8d0
c1t2d0
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
_______________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
_______________________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
Pri_Boot _Main_
c2t2d0
8680 0/0/2/0.2.0
_(free)_ ______
vg00
_____________
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:
NOTE:
Set Logical Vol allocation policy to PVGstrict 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
1AA 00014 0004 (9007) A4 ALICE 04.10
.......
2 16:33:13 MET 2003

=>Tue Dec
.......
ED
2 16:33:37 MET 2003
Mirroring Logical Volume:/dev/vg00/lvol4
01
3AL 88893 BAAA
226
207 / 226
=>Tue Dec
=>Tue Dec
.......
2 16:38:09 MET 2003
=>Tue Dec
.......
2 16:36:19 MET 2003
=>Tue Dec
.......
2 16:36:01 MET 2003
=>Tue Dec
.......
2 16:33:44 MET 2003
2 16:38:53 MET 2003
=>Tue Dec
2 16:39:19 MET 2003
.......
NOTE:
Check /etc/lvmrc .....
=>Tue Dec
NOTE:
2 16:42:30 MET 2003
Set Alternate Boot Hardware Path to disk:c4t8d0
=>Tue Dec
2 16:42:30 MET 2003
=>END:
1AA 00014 0004 (9007) A4 ALICE 04.10

.......
OSConf File(s) System Mirroring
ED
01
3AL 88893 BAAA
226
208 / 226

F.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 systems have been mixed.
b)
The IRT and Fbackup tape have been produced at different time and with different system configuration. 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 process.
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:
F.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
*****************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
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 hpuxt from IRT. Otherwise it is better
to not go on.
ED
01
3AL 88893 BAAA
226
209 / 226
F.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 OSCluster system.
F.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.
F.5.4.4Logical Volume Configuration Mismatch
*****************************************************************************
ERROR:
Logical volume /dev/vg00/lvol11

present on tape but not defined on system
*****************************************************************************

*****************************************************************************
ERROR:

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:

references different mount point.
Tape mount point > /user
System mount point > /home
*****************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
3AL 88893 BAAA
226
210 / 226

*****************************************************************************
F.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.
F.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
*****************************************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10
Extend the file system using the command: scextendfs <File System> <Free Mega Bytes>
ED
01
3AL 88893 BAAA
226
211 / 226
F.5.4.7How to proceed
*****************************************************************************
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) ? :
1AA 00014 0004 (9007) A4 ALICE 04.10
If the warning messages have been analyzed and the warning condition are not present, enter y[Enter]
to proceed.
ED
01
3AL 88893 BAAA
226
212 / 226

Each time a waring message is issued the following messages are shown:

APPENDIX G 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 26. System Administrator Management Window (1)

b)
Select Networking and Communications.
Figure 27. System Administrator Management Window (2)
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
Select Network Interface Cards.
Figure 28. Networking and Communications Window
ED
01
3AL 88893 BAAA
226
213 / 226
Select the line of Lan to be configure then select Action menu and click on Configure.
Figure 29. Configure LAN Card Window

e)
For each lan to be configure, insert the internet address and click on Add Host Name Aliases...:
Figure 30. Add Host Name Aliases Window

f)
Insert the aliases name and click on Add, thne, click twice on the [OK] button.
Figure 31. Networking and Communications Window
1AA 00014 0004 (9007) A4 ALICE 04.10
g)
ED
Select Action menu and click on Exit twice.
01
3AL 88893 BAAA
226
214 / 226

d)

APPENDIX H HPT 9000 SERVER CABLE CONNECTION

This appendix shows the suggested connections for the SCSI and Fibre Channel cable for the HP servers
foreseen, an example picture is provided for each server model.
H.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
FWSCSI 1
CPU
: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS0
1
Bus B
2
Bus A
2
Bus B
2
Bus A
2
1AA 00014 0004 (9007) A4 ALICE 04.10
HAS1
Figure 32. Rear view of server with two disk cabinets
ED
01
3AL 88893 BAAA
226
215 / 226
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 2
: FWSCSI connector
HAS
1
Bus B
2
Bus A
2
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 33. Rear view of server with one disk cabinet
ED
01
3AL 88893 BAAA
226
216 / 226

b)
c)
The last configuration is just an example of K Class server cluster, with three nodes.

: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 1
FWSCSI 1
FWSCSI 1
FWSCSI 2
FWSCSI 2
FWSCSI 2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 34. Example of K server cluster
ED
01
3AL 88893 BAAA
226
217 / 226
H.2 HP 9000 R Class
N.B.
For the server R the recommended configuration of the HSC and Lan boards is indicated in
Figure 35. :
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
TURBO 3
: FWSCSI connector
HSC
HAS
1
Bus B
2
1
Bus A
2
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 35. Rear view of server R with one disk cabinet
ED
01
3AL 88893 BAAA
226
218 / 226

This paragraph shows the suggested SCSI connections for the R Class servers.

H.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
(c2t0d0)
/0/0/2/0.2.0
(c2t2d0)
DVD
/0/0/1/0.0.0
(c1t0d0)
/0/0/1/0.2.0
(c1t2d0)
Main disks
Figure 36. 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 37. 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.
Install the additional PCI cards starting from the top of PCI Slots.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
01
3AL 88893 BAAA
226
219 / 226
The A Class and RP2430 are the HP9000 server entry levels, them are not provided with external disks
and can equip up to two hard disk units. These hard disks are located in the server front, behind a little
door located on the left side.
Each disk is connected to a different SCSI bus, that guarantee the high availability.
Disks Location
Figure 38. Front view of A Class and RP2430 Servers (without cover panel)
H.5 HP9000 RP3410 and RP3440

RP3410 and RP3440 are the HP9000 system based on PA8800 processors, them requires the 64TH610C
bootable edition to be installed. The difference between the two system is related to the number of CPUs,
RP3410 is foreseen with just one, instead RP3440 with two.
Two system looks is the same from outside, the most relevant characteristic is the disk bay, it foreseen
up to three hard disk slots, but just two SCSI busses. Because of this the machine are provided with two
hard disks, that have to be placed in the slots: HDD 1 and HDD 3.
HDD 1
HDD 2
HDD 3
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 39. RP3410 and RP3440 Server Front
ED
01
3AL 88893 BAAA
226
220 / 226

H.4 HP9000 A Class and RP2430

H.6 HP9000 RP4440

RP4440 are the high end computer equipped with PA8800 processor and require the SWP64THP610C
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 following figures is shown how to connect them each other.
DS2405 Disk System Front view
1
10
11 12 13 14 15
Figure 40. RP4440 Front View

DS2405 Disk System Rear view
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 41. RP4440 Rear View
ED
01
3AL 88893 BAAA
226
221 / 226
The HP disk technology innovation trend brought us to introduce new disk storage in the highend class
server, the supported server/disk storage configuration are:
Server Model
Disk Storage
N4000
SC10
RP7400
SC10, DS2405
H.7.1 HP9000 N Class and RP7400 with SC10

This paragraph provides the instructions for the configuration of the HP HP9000 N Class and RP7400 server configured with the SC10 external disk cabinet. This disk cabinet needs to be configured to 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
: VHDCI SCSI terminator
: VHDCI SCSI connector
NOTE: Dip switchorientation is reverted

on the bottom controller
I
I I
I
O
: HD SCSI terminator
5 4 3 2 1
O
: HD SCSI cable 68pin

A
SC10
A
DAT
PCI Slots
6
12
11 The two internal
5
10 disks are place
4
in this location
9
3
8
2
1
7
DVD
PCI Slots
Figure 42. Rear view of N/RP74xx Server with SC10
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
The position of the components in the rack is not predictable, so the N4000 server can be placed
on top of SC10.
N.B.
It is advisable to install the PCI cards balancing them in the right and left slots, starting from the
bottom.
ED
01
3AL 88893 BAAA
226
222 / 226

H.7 HP9000 N Class and RP7400

H.7.2 HP9000 RP7400 with DS2405

This paragraph provides the instructions for the configuration of the HP HP9000 RP7400 server configured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in
dualaccess 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
DVD
DAT
PCI Slots
6
12
11 The two internal 5
10 disks are place 4
in this location
9
3
8
2
1
7
PCI Slots
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 43. RP7400 Server with DS2405
ED
01
3AL 88893 BAAA
226
223 / 226
This paragraph provides the instructions for the configuration of the HP HP9000 RP7410 server configured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in
Fiber Channel Connector
: VHDCI SCSI cable
DAT
DVD
1 2
3 4
5 6 7 8 1 2
3 4
5 6 7 8
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 44. Rear view of RP7410 Server with DS2405
ED
01
3AL 88893 BAAA
226
224 / 226

H.7.3 HP9000 RP7410 with DS2405
This paragraph provides the instructions for the configuration of the HP HP9000 RP7410 server configured 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
Fiber Channel Connecto
: VHDCI SCSI cable
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8

H.7.4 HP9000 RP7410 Cluster with VA7110
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
FC Switch
FC Switch
1AA 00014 0004 (9007) A4 ALICE 04.10
Virtual Array VA7110

Rear view
Figure 45. Rear view of RP7410 Server with DS2405
ED
01
3AL 88893 BAAA
226
225 / 226
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
3AL 88893 BAAA
226
226 / 226

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
1350 Management Suite
1350 Rel.7.1
NR7.1 INSTALLATION GUIDE
COD.MANUALE HDBK P/N:
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 228+4=232

DIMENSIONE BINDER SORGENTE (du ks): 81.788 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
(facciate)
No pages
numerate
numbered
da from
a to
1/226
226/226
TARGHETTE - LABELS
frontespizio
front
manuale
manual
226
INSERIRE LE 5 BUSTE TRASPARENTI

INSERT FIVE TRANSPARENT PLASTIC ENVELOPES
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
228
TOTALE FOGLI A4 TOTAL A4 SHEETS:
114
1AA 00014 0004 (9007) A4 ALICE 04.10
WARNING FOR A-UNITS OTHER THAN A-ITALY
ED
Labels are done according to A-Italy binder format.

Source files: ALICE 6.10 ARCHIVED BY GAPI 4.1
01
RELEASED
3AL 88893 BAAA TQZZA
4
1/ 4
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

Site
FCG
Originators
M.Occhietti
1350 NR7.1
NR 7.1
INSTALLATION GUIDE
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
OND
NM
1350
1350 REL.7.1 INSTALLATION GUIDE
Internal :
External
Approvals
Name
App.
B.Bosisio
F.Casasole
Name
App.
INFORMAZIONI EDITORIALI
ORIGINALE SU FILE: ALICE 6.10
sistemazione figlist
3AL 88893 BAAA

Ed.01
1350 Rel.7.1
NR7.1
1AA 00014 0004 (9007) A4 ALICE 04.10
Network Release
INSTALLATION GUIDE
ED
01
RELEASED
4
2/ 4

1350 Rel.7.1
Network Release
NR7.1
INSTALLATION GUIDE
VOL.1/1

1350 Rel.7.1
Network Release
NR7.1
INSTALLATION GUIDE
VOL.1/1
1350 Rel.7.1
Network Release
NR7.1
INSTALLATION GUIDE
VOL.1/1
1350 Management Suite 1350 Rel.7.1

Network Release
NR7.1
INSTALLATION GUIDE
VOL.1/1

1350 Rel.7.1
Network Release
NR7.1
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
INSTALLATION GUIDE
VOL.1/1
RELEASED
4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
01
RELEASED
4/ 4

1350 Installation Guide

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1350 Installation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Installation Guide

3AL 88893 BAAA Ed.01

3AL 88893 BAAA Ed.01

All rights reserved. Passing on and copying of this

1350 NR7.1 INSTALLATION GUIDE

1AA 00014 0004 (9007) A4 ALICE 04.10

5 SOFTWARE PACKAGE PREDISPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 OPERATING SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 INSTALL AND CUSTOMIZE ALCATEL SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

4 OPERATING SYSTEM INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

3.3.3 Configure NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

7.2.3 Installing 1353NM EMLIM and OBS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 UPGRADE FROM PREVIOUS VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

APPENDIX C GOGLOBALUX INSTALLATION AND CONFIGURATION . . . . . . . . . . . . . . . . . . . .

APPENDIX D HOW TO CREATE A NETWORK DEPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX E PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX F BACKUP AND RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

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

1AA 00014 0004 (9007) A4 ALICE 04.10

10.4.2 Kerberos kdcd High CPU Consuming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

F.4.1 Start the scbackup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX G LAN CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX H HPT 9000 SERVER CABLE CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Table 4. 1353NM Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

3AL 88893 BAAA

All rights reserved. Passing on and copying of this

All rights reserved. Passing on and copying of this

1.2 Handbook applicability

3AL 88852 AAAA

3AL 88851 ABAA

1AA 00014 0004 (9007) A4 ALICE 04.10

NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

1.3.1 Handbooks related to the specific software application

ANV Part No.

3AL 88893 BAAA

ANV Part No.

1.3.2 NR 7.1 Related Handbooks

3AL 89061 BAAA

3AL 61345 BAAA

1.4 Registered Trademarks

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

HP is a registered trademark of HewlettPackard Corporation.

HP9000/700 and HPUX are trademarks of HewlettPackard Corporation.

HP OpenView and HP OpenView Window are trademarks of HewlettPackard.

1AA 00014 0004 (9007) A4 ALICE 04.10

ORACLE is a registered trademark of Oracle Corporation.

All rights reserved. Passing on and copying of this

1.3 Product-release handbooks

All rights reserved. Passing on and copying of this