1354rm52b Instalacion

QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
COD.MANUALE HDBK P/N: 957.130.892 W Ed.02 3AL 61261 AAAA Ed.02

1300NM
1354RM Rel.5.2B
Version 5.2.1.5 PL1 INSTALLATION GUIDE
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 324
DIMENSIONE BINDER SORGENTE (du ks): 51.824 kBytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

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

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

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

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

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

Site
VIMERCATE ALCATEL OPTICS GROUP
Originators 1354RM REL.5.2B

M.Mantegazza
N.Saggiomo VERSION 5.2.1.5 PL1
INSTALLATION GUIDE
Domain : TND
Division : NM
Rubric : 1354RM
Type : 1354RM REL.5.2B INSTALLATION GUIDE
Distribution Codes Internal : External :
Approvals
Name B.Bosisio
App.
Name
App.
INFORMAZIONI EDITORIALI
ORIGINALE SU FILE: ALICE 6.10

sistemazione figlist
957.130.892 W
3AL 61261 AAAA
Ed.02
1300NM
1354RM Rel.5.2B
Version 5.2.1.5 PL1
Regional Network Manager for SDH and Optical Networks

INSTALLATION GUIDE
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02 RELEASED
4
1300NM
1354RM Rel.5.2B

Version 5.2.1.5 PL1
INSTALLATION GUIDE
957.130.892 W Ed.02 3AL 61261 AAAA Ed.02
VOL.1/1
1300NM
1354RM Rel.5.2B
Version 5.2.1.5 PL1
INSTALLATION GUIDE
957.130.892 W Ed.02 3AL 61261 AAAA Ed.02
VOL.1/1
1300NM
1354RM Rel.5.2B
Version 5.2.1.5 PL1
957.130.892 W Ed.02 3AL 61261 AAAA Ed.02 INSTALLATION GUIDE VOL.1/1
1300NM 1354RM Rel.5.2B

Version 5.2.1.5 PL1
1300NM
1354RM Rel.5.2B
Version 5.2.1.5 PL1

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02 RELEASED
4
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
RELEASED
957.130.892 TQZZA
4
3AL 61261 AAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
4/ 4
Installation Guide
Alcatel 1300NM
Network Management
1354RM Rel.5.2B
Version 5.2.1.5 PL1
957.130.892 W Ed.02 3AL 61261 AAAA Ed.02

957.130.892 W Ed.02 3AL 61261 AAAA Ed.02
1354RM REL. 5.2B INSTALLATION GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 PRELIMINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.2 NR 5.0B Related Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Registered Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 Purpose of Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.1 Required Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2.3 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.4 SDH Manager Software delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2.5 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 SYSTEM PRESENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2 Operation System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.4 Groups and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 INSTALLATION OF HPUX AND THIRD PARTS SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 Stages of Softwares Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2 Manual Installation of HPUX 10.20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.1 HPUX 10.20 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.2 Add Tape Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2.3 Configure floppy drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.2.4 Retrieve Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
02 010409 SC 01041102 B. Bosisio ITAVE M. Mantegazza ITAVE

N. Saggiomo
01 001207 B. Bosisio ITAVE M. Mantegazza ITAVE
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

1AA 00014 0004 (9007) A4 ALICE 04.10
1354RM REL.5.2B
Version 5.2.1.5 PL1
INSTALLATION GUIDE
ED 02
957.130.892 W 3AL 61261 AA AA 1 / 318
318
4.2.5 Installation for Alcatel ALMAP HP4.2 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.6 Optional Softwares allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.2.7 Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.2.8 Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.2.9 Post installation step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.2.10 Load OTS 9000 drivers into kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3 Installing HPUX 10.20 from Bootable Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3.1 Boot the machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3.2 Keyboard selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.3 Set up the Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.3.4 Application Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.3.5 Disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.3.6 RM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3.7 Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.3.8 Optional Softwares selelection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.3.9 Source media selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.3.10 Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.4 Check the validity of the HPUX 10.20 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.5 Manual Installation of HPUX 11.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.5.1 HPUX 11.00 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.5.2 HPUX 11.00 Manual Installation Post Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.5.3 Retrieve Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.5.4 Installation for Alcatel ALMAP HP4.2 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.5.5 Optional Softwares allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.5.6 Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.5.7 Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.5.8 Post installation step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.6 Installing HPUX 11.00 from Bootable Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.6.1 Boot the machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.6.2 Keyboard selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.6.3 Set up the Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.6.4 Application Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.6.5 Disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.6.6 RM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.6.7 Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.6.8 Optional Softwares selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.6.9 Source media selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.6.10 Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.7 Check the validity of the HPUX 11.00 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.8 Post HPUX Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.8.1 Dismount the CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.8.2 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.8.3 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5 BOOTABLE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

5.1 Bootable Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.1.1 Using Cdrom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.1.2 Using distribution tar file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.1.3 Upgrade on HPUX 10.20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.1.4 Upgrade on HPUX 11.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.1.5 Post Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1AA 00014 0004 (9007) A4 ALICE 04.10
6 SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

6.1 Run the initialization script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ED 02
957.130.892 W 3AL 61261 AA AA 2 / 318
318
6.1.1 On Workstation with graphic interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.1.2 On Workstation without graphic interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.2 Run the kernel configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6.3 Synchronize the time on all the machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.4 OSI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6.4.1 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6.4.2 OTS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
6.4.3 Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
6.5 Run the application OSI stack configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
6.6 Configure HPOV for the HPOV communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
6.7 Run the mailer configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.8 Mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7 X TERMINAL INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

7.1 Add an Xterminal station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.2 Remove an Xterminal station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
8 PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

8.1 Configure Printer Booting from Local System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.2 Configure Local Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.3 Local printer for Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
8.3.1 Configure printer booting from local system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
9 INSTALLATION OF 1354RM R5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.1 1354RM R5.2 Installation from scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9.1.1 1354RM R5.2 preinstallation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9.1.2 Create the 1354RM installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9.2 Installation of the Delivery Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
9.2.1 1354RM installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
9.2.2 Mandatory Patches installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
9.3 1330 AS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
9.3.1 1330 AS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
9.3.2 1330 AS Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9.3.3 Swedish language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
9.4 SMF Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.4.1 Check the crontab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.4.2 Install the SMF package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.4.3 SMF package postinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
9.5 Integration of 1354RM with Navigation Component (NAV) . . . . . . . . . . . . . . . . . . . . . . . . . 185
9.5.1 NAV Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
9.6 SEC Security Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
9.6.1 SEC Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
9.6.2 SEC Workaround . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
9.6.3 SEC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
9.7 1354RM Post installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
9.7.1 Increase the Max Data Segment Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
9.7.2 Increase the shared pool size parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
9.7.3 Database Reset for 1354RM for Patch FIX16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
9.7.4 Performance Monitoring Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
9.7.5 PM Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
9.7.6 Create ORACLE User for Archive purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
1AA 00014 0004 (9007) A4 ALICE 04.10
9.7.7 Prevent Unnecessary Mail Messages to root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

9.7.8 Software Download Workaround . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
9.7.9 MultiIM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
ED 02
957.130.892 W 3AL 61261 AA AA 3 / 318
318
9.7.10 QNN Interface Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
9.7.11 End of Postinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
9.7.12 License Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
9.7.13 How request the HP OpenView license to HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

9.7.14 Insert the HP OpenView license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

10 1354RM UPGRADE TO NR5.0B PATCH LEVEL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
10.1 Bootable Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
10.2 1354RM Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
10.2.1 Backup database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
10.2.2 Install the new patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
10.2.3 Install the new AS package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.2.4 Install the new SMF package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.2.5 Install the NAV package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.2.6 Install the new SEC package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.2.7 Post Upgrade steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11 ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.1 Remote Event Sieve configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.2 Database Schema Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.3 Database extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.4 Oracle processes number extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.5 Object Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
11.6 How to modify a kernel parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
11.7 Root User password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
11.8 Date&Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
11.9 Change IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
11.9.1 Change IP address on the IM machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
11.9.2 Change IP address on the RM USM workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
11.10 Install Optional Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
11.10.1 Run the installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.10.2 Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.10.3 Optional Software Additional Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.10.4 Remove the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.11 Set the Swedish language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
11.11.1 Swedish chars on the keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
11.11.2 Swedish language for AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
11.12 A1330AS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.12.1 1330AS Processes registration and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.12.2 1330AS Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.12.3 Deinstalling 1330 AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.13 NAV Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
11.13.1 Deinstalling NAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
11.14 SEC Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.14.1 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.14.2 Alarm Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
11.14.3 SEC Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
11.15 SMF deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
11.16 How to verify if a software is installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
11.17 Configure the Iview printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
11.18 Configure a printer after the 1354RM customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
1AA 00014 0004 (9007) A4 ALICE 04.10
11.19 RM Zoomin from NN Using RM USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

11.20 Add a Presentation Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
11.20.1 Add the workstation to existing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
ED 02
957.130.892 W 3AL 61261 AA AA 4 / 318
318
11.20.2 Run the kernel configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
11.20.3 Synchronize the time on all the stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
11.20.4 Run the application OSI stack configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
11.20.5 Configure HPOV for the HPOV communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
11.20.6 Run the mailer configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

11.20.7 Align the printer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

11.21 Remove a Presentation Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.21.1 Remove the HP OpenView agent registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.21.2 Remove the workstation from configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.21.3 Configure the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.22 Full backup/restore disk on tape (using IgniteUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
11.22.1 IgniteUX BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
11.22.2 IgniteUX RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
12 DISK MIRRORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

12.1 Disk Mirror Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
12.1.1 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
12.1.2 Verify the Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
12.1.3 Verify the Hardware configuration for server N Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
12.1.4 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
12.1.5 Configure the mirror copy disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
12.1.6 How identify the disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
12.1.7 Mirror Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
12.2 Mirror Configuration Final Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
12.2.1 Verify all Logical Volumes are Mirrored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
12.2.2 Verify the Boot from both Boot Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
13 VERIFY THE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

13.1 Verify the RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
13.1.1 Start the RM from IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
13.1.2 Start the RM from USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
13.1.3 AS initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
13.1.4 Verify the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
13.1.5 Verify the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
13.2 Verify RM IM plus SH IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
14 TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
14.1 Ovlad registration error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
14.2 Ov_log errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
14.3 How to Recover Error Installing Layered Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
14.4 Axprintconf Script Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
14.5 Performance Monitoring Tools Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
14.6 XTerminal Fonts Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
14.7 SEC box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
14.8 SMF installation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
14.9 Recover LAN Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
14.10 Large Database Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
14.11 Install tape for backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
14.12 Process Monitor (mngAgent) does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
APPENDIX A CONFIGURATION SECURE WEB CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

1AA 00014 0004 (9007) A4 ALICE 04.10
A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

A.2 Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
A.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
A.4 Login to Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
ED 02
957.130.892 W 3AL 61261 AA AA 5 / 318
318
A.5 Console Emulation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
A.6 Configuration reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
APPENDIX B SYSTEM SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

APPENDIX C GOGLOBAL INFORMATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
C.1 Introduction to GoGlobal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
C.2 Installation on UNIX machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
C.3 Installation on PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
C.4 GOGlobal Connections creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
C.4.1 Creating a new generic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
C.4.2 Completing the connection with log in phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
C.4.3 Creating a new connection with automatic login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
C.5 GOGlobal connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
C.5.1 Editing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
C.5.2 Check Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
C.5.3 Exiting a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
APPENDIX D HOW DISABLE/ENABLE HP SERVER CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

D.1 Disable a HP Server CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
D.2 Enable a HP Server CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
APPENDIX E SWITCH OFF FAULT LAMP OF N & L CLASS SERVER . . . . . . . . . . . . . . . . . . . . . . 313
APPENDIX F NR5.0B PL1 UPGRADE CHECK LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 6 / 318
318
LIST OF FIGURES AND TABLES
FIGURES
Figure 1. Example of management platform configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 2. HPUX Set Parameters Welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 3. HPUX Set Parameters Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 4. HPUX Set Parameters Hostname Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 5. HPUX Hostname Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 6. HPUX Set Parameters Time Zone First Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 7. Set Unlisted Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 8. Set Data and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 9. Reboot System Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 10. HPUX Set Parameters Root Password Set Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 11. HPUX Set Parameters Root Password 1st window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 12. HPUX Set Parameters Root Password 2nd window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 13. HPUX Set Parameters Root Password Accepted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 14. HPUX Set Parameters TCP/IP Address Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 15. HPUX Set Parameters TCP/IP Address Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 16. HPUX Set Parameters Configure Additional Network Parameters . . . . . . . . . . . . . . . . . 49
Figure 17. SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 18. Sam Areas: Kernel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 19. SAM Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 20. SAM Drivers Add Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 21. SAM Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 22. SAM Driver Create a New Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 23. SAM Confirm - 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 26. Optional 3rd part softwares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 27. HPUX 11.00 Installation Presentation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 28. HPUX 11.00 Installation: User Interface and Media Option Window . . . . . . . . . . . . . . . 79
Figure 29. HPUX 11.00 Installation: Basic Choices Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 30. HPUX 11.00 Installation: Language Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 31. HPUX 11.00 Installation: Keyboard Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 32. HPUX 11.00 Installation: Additional configuration Control window . . . . . . . . . . . . . . . . . 83
Figure 33. HPUX 11.00 Installation: System Choices Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 34. HPUX 11.00 Installation: Time Zone Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 35. HPUX 11.00 Installation: Set Root Password Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 36. HPUX 11.00 Installation: Verify Root Password Window . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 37. HPUX 11 Installation: File System Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 38. HPUX 11 Installation: Add/Remove Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 39. HPUX 11 Installation: Add/Remove Disk for IM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 40. HPUX 11 Installation: Add/Remove disk for US . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 41. HPUX 11 Installation: File System Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 42. HPUX 11 Installation. Confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 43. Optional 3rd part softwares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 44. HPUX Set Parameters Time Zone First Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 45. Set Unlisted Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 46. Set Data and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 47. Reboot System Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 48. SAM Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 49. SAM Areas: Networking and Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Figure 50. Networking and Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 51. Configure LAN Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 52. 1354RM Install Variables Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
ED 02
957.130.892 W 3AL 61261 AA AA 7 / 318
318
Figure 53. Aca: Access Rights Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 54. Aca: Initiator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 55. Aca: Operator Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 56. Initiator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Figure 57. Aca: Operator Group Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Figure 58. Rear view of server with two disk cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 59. Front view of two disk cabinets (HAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Figure 60. Rear view of server with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Figure 61. Rear view of server R with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 62. Front view of one disk cabinet (HAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 63. Front view of L Server (without cover panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 64. Rear view of L Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Figure 65. Rear view of N Server with SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 66. Front view of SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figure 67. Sam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 68. Disk and File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 69. Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 70. RM start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Figure 71. The Start smf window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 72. The Counter Summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 73. The Root window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 74. The browser window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Figure 75. The TMNOSs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Figure 76. SH System Management Feature window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 77. The SH AS window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 78. The SDHNet window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 79. LED status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Figure 80. Welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 81. First administrator account window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Figure 82. Configure IP window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 83. End of initial setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Figure 84. Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 85. Web Console window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Figure 86. Connection Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 87. Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 88. Log in Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 89. Automatic connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 90. List of connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Figure 91. GoGlobal Host Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 92. Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
TABLES
Table 1. Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 2. Runtime keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 3. Installation keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 4. A1354RM Disk Partition for series 700 and series 800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 5. HPUX 11.00 1354RM IM Disk Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 6. HPUX 11.00 1354RM US Disk Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 7. NN users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 8. HP Password Delivery Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Table 9. Volume Group Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Table 10. Logical Volume Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 11. Boot Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Table 12. Disks table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
ED 02
957.130.892 W 3AL 61261 AA AA 8 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
HISTORY
Ed. 01
Ed. 02
Edition
957.130.892 W
Date
April 09 2001
January 02 2001
318
3AL 61261 AA AA
Notes
version 5.2.1.5
Version 5.2.1.5 Patch level 1
9 / 318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
10 / 318
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

1354RM 3AL 61101 AAAA 521.200.800 Y
PRODUCT RELEASE VERSION (N.B.) ANV P/N Factory P/N

1354RM 5.2B 5.2.1.5 3AL 61169 ADAA 521.560.420 A
N.B. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 11 / 318
318
1.3 Product-release handbooks
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.

Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose
product-release-version is stated in para.1.2 on page 11 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application
FACTORY THIS
REF HANDBOOK ANV Part No.
Part No. HANDBOOK
1354RM Rel.5.2B
3AL 61261 AAAA 957.130.892 W
Installation Guide
1354RM Rel.5.2B
[1] 3AL 61259 AAAA 957.130.872 H
Operators Handbook
1354RM Rel.5.2B
[2] 3AL 61260 AAAA 957.130.882 U
Administration Guide
1.3.2 NR 5.0B Related Handbooks
THIS
FACTORY
REF HANDBOOK ANV Part No. HANDBOOK
Part No.
or note
1330AS Rel.5.1
[3] 3AL 71109 AAAA 957.130.722 A
Operators Handbook
Generic OSOS Interface

[4] REL.4.2 3AL 71184 AAAA 957.140.112 H
Installation & User Guide
OS Resilience Rel.5.0.1
[5] 3AL 71199 AAAA 957.140.192 A
Installation Guide
OS Resilience Rel.5.0.1
[6] 3AL 71198 AAAA 957.140.182 G
Operators Handbook
1353SH Rel.5.3
[7] 3AL 71808 AAAA 957.130.942 F
1AA 00014 0004 (9007) A4 ALICE 04.10
Installation Guide
ED 02
957.130.892 W 3AL 61261 AA AA 12 / 318
318
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.
ORACLE is a registered trademark of Oracle Corporation.
1.5 Overview
This document describes how to install and configure the HP 9000 computer systems in order to allow the
correct usage of A1354RM 5.2 application.
1.6 Conventions
The following conventions are used in this manual:
[Enter] A key name is shown between square brackets to indicate that you press a
named key on the keyboard.
courier Courier type is uses to indicate the output produced by the system or data that
you can find.
bold italic Bold italic letters indicate informations that you must enter from the keyboard.
<data> Data shown between angle brackets means that these data depending by the
particular instance of the system. It must be substituted with the correct data.
# Actions must be performed as root.
..,sys,root # Actions must be performed as root.
..,$ Actions must be performed as normal user (not as root).
..,oracle> Actions must be performed as oracle user.
SQL> Actions must be performed in SQL utility.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 13 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
14 / 318
2 INTRODUCTION
2.1 Purpose of Document

The purpose of this document is to describe the Regional Manager installation process with mandatory
configuration parameters, up to the operational state after which the System Administrator takes over and
launches the Regional Manager.
This document is destined to the Regional Manager product installer.
2.2 Requirements
2.2.1 Required Knowledge
It is advisable that the installer knows the basic Unixcommands and the vi editor.
2.2.2 Hardware Requirements
The 1354RM IM requires: two or more hard disks with at least 13 GByte. The raccomanded configurations
are 9+9 GByte or bigger.
The 1354RM US requires: one or more disks with at least 6 Gbyte.
To guarantee performance, we suggest to install on an isolated CLNS/802/3 network, not linked to the
outside world.
In order to prevent problem on the network it is advisable to do use the LANTP connection with HUB.
On some workstations have been observed that it is necessary to reset the LAN board in case of cable
disconnecion using LANAUI (see 14.9).
N.B. The environment is dedicated to the Regional Manager software. Therefore the integrity of the
system can not be guaranteed if other applications than those delivered run on the platform at
the same time.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 15 / 318
318
2.2.3 Software Requirements
The Regional Manager is based on 3rd party products.

The following table give the rights to use and keys required for each of the main basic components of the

A1354RM.

Table 1. Licenses
Product name Category Licences
HPUX Operating System LICENCE : 1 per WS
Oracle7 RDBMS Server Data bases LICENCE : On IM WS only.
Oracle SQL*Net Data bases Access LICENCE : On IM WS only.
Oracle SQL*Plus Data bases Interface LICENCE : 1 per WS
Oracle PL/SQL Procedural Language LICENCE : On IM WS only.
HP OpenView Distributed Processing Services LICENCE : 1 per WS
HP OTS 9000 OSI Transport Services LICENCE : On IM WS only. (A1353WX)
HP 100VGAnyLan 100VGAnyLan Driver LICENCE : 1 for each WS with

(If there is any present) 100VGAnyLan Board
HP 100BaseT 100BaseT Driver LICENCE : 1 for each WS with

(If there is any present) 100BaseT Board
Table 2. Runtime keys
Product name Category Keys
HPOpenView Distributed Processing KEY : 1 per WS, attached to SPU Target ID

Services
ILOG Views Users Interface Services KEY : 1 per WS , already included in the delivered
product
Table 3. Installation keys
Product name Category Keys
HP OTS 9000 OSI Transport Services KEY : 1 per IM WS only.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 16 / 318
318
2.2.4 SDH Manager Software delivery
The software delivery is based on CDROM labelled:

SWPC742C17D_TSD Bootable Medium HPUX 10.20 for H9000/700 workstation

Cod. 3AL 71852 AAAA CS. 01 1/2 and 2/2
SWPC842C17D_TSD Bootable Medium HPUX 10.20 for H9000/800 server

Cod. 3AL 71853 AAAA CS. 01 1/2 and 2/2
SWPC342C20E_TSD Bootable Medium HPUX 11.00 for HP9000 32 Bit

for HP9000 C110/B180/B132
Cod. 3AL 71857 AAAA CS. 01 1/2 and 2/2
SWPC642C20E_TSD Bootable Medium HPUX 11.00 for HP9000 64 Bit

for HP9000 B1000/B2000/R/L/K/N
Cod. 3AL 71858 AAAA CS. 01 1/2 and 2/2
SWPA1354RM _APPV5.2 Regional Manager Application

Cod. 3AL 61257 AAAA CS. 01
SWPNR50B_PL1 Patch Level 1 for NR5.0B PL1

for 1353SH 5.3.0.5, 1254RM 5.2.1.5 & Bootable Media of NR50.B
Cod. 3AL 71801 AAAA CS. 03 1/2 and 2/2
With the following configuration: 1354RM with OSResilience or/and CoHosted with 1353SH
have been observed a crash of the objAlrMng Agent of 1354RM.
To fix this crash a specific patch have been issued (1354RM Fix16 Plus).
If you have such kind of configuration or the objAlrMng crashes please contact the Product Sup-
port Center.
2.2.5 Documentation
See the REFERENCE DOCUMENTS section.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 17 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
18 / 318
3 SYSTEM PRESENTATION
3.1 System Overview

From a functional point of view, 1354RM Application Subsystems consist of components which are one
or more User Services Managers (USMs) and the Information Manager (IM). This decomposition
reflects the separation between the USM, the part of the subsystem that controls the HumanMachine
Interface (HMI), and the IM, the functional part of subsystems (application core).
The following lists the major characteristics of IM and USM components:
Information Manager (IM)

IMs are distributed over the agent machines of the system according to a predefined site
configuration that should optimize performance. There is only one instance of each IM running in the
system.
User Service Manager (USM)

The USMs of an IM may run on any workstation of the system, preferably on presentation
workstations to guarantee performance. There may be multiple instances of the same USM running
in parallel, one for each user of the application.
3.2 Operation System Architecture
The hardware/software configuration will be a scalable function according to the required number of
operator positions and to the required network configurations. It depends on the customer requirements
and needs.
The following figure gives an example of management platform configuration with three machines.
3 Operators
Printer
console console console

Telecommunication
Network
Master EML EML

WS WS WS
OPERATION
SYSTEM
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. Example of management platform configuration.
ED 02
957.130.892 W 3AL 61261 AA AA 19 / 318
318
3.3 Machines
The 1354RM machines are classified in the following way:

Agent Machines

These are machines on which information managers run (IMs). They are subject to all management
operations. They may run USMs as well but this affects performance of the machine.
Presentation Workstations
These workstations only run application processes (USMs) whose lifespan is contained in a user
session. They are not subject to any system management operations.
Presentation workstations can be added to the system dynamically (online).
Terminal X
The X Terminal offers an X11 graphic display to an user. It is logically linked to a presentation
workstation.
3.4 Groups and Users
Group Description
dba RM & Oracle administration
User Group Home Directory Password Profile Description
root sys / install10 Installation only
oracle dba /users/oracle 1353sh Oracle administrator
snml snml, dba /home/snml system1 osadmin System administrator

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 20 / 318
318
4 INSTALLATION OF HPUX AND THIRD PARTS SOFTWARE
This chapter shows how to install the HPUX 10.20 or 11.00 and all the third party software on a HP 9000
system. This approach foresees to destroy the whole contents of the system hard disk, that means it is
applicable on system where there is no 1354RM application installed yet.

There are two ways to install the machine: the first is manual installation HPUX with the HP CDROM, the
second is through the bootable medium.
If you have to install the disk mirroring on a server series 800, please refer to Chapter 12 at page
249, before starting the installation.
For HP server are now provided the Secure Web Console instead of the terminal, please refer to
Configure Secure Web Console in APPENDIX A.
During the installation, the LAN0 must be always connected to a hub or through a transceiver
with a Te and a load to each end.
To be able to install you need to have the following information:
a) The size of the CoreMemory (RAM) of your machine

b) The hostname of your machine
c) The IP address of your machine
d) The IP address of the gateway (Optional)
e) The subnet mask (Optional)
f) The Time Zone
g) If are present some more additional lan cards
h) If are present some XTerminals with:
IP address
hostname
i ) If are present some 1353WXs with:
IP address
hostname
j ) If Disk Mirror configuration is planned
k ) Keyboard type
l ) Which kind of application you have to install (RM IM, RM USM and so on)
m ) IP address, Mac address, name for printer
n ) KEY for HPOpen View basic software for each station, one license per station.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 21 / 318
318
4.1 Stages of Softwares Installation and configuration
The installation will be performed according to the following chronology:

SystemSoftware installation

loading : on each machine independently
configuration : global, launched from the Master

IP addresses and hostnames
OTS
HPOV
TimeZone, Date & Time
Master
RM Application software installation
or or or
configuration: global
Retix stacks configuration
Processes configuration
Master
Terminal X installation
Printer installation
Post installation
Startup
Backup: on each machine

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 22 / 318
318
4.2 Manual Installation of HPUX 10.20
This section describes how to install and customize the HPUX 10.20 on the HP 9000 system, in order
to allow the correct execution of the Alcatel Network Management application within NR5 environment.
4.2.1 HPUX 10.20 installation and configuration
The HPUX installation have to be performed using the following HPUX 10.20 CDROM distribution
medium:
For the 700 series machine the CDROM is labeled: HPUX Additional Core Enhancements
Release 10.20 Part. N B378210456, December 1999
The case of the CDROM is labeled: HPUX Additional Core Enhancements Release 10.20 Part.
N B378268149, December 1999
For the 800 series server HPUX Install and Core OS Release 10.20 Part. N B392013640, July
1996
N.B. The reference to the device (path, size, model) are provided as examples, they can change
depending by the hardware configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 23 / 318
318
4.2.1.1 Step 1
Insert the medium in the CDROM driver and 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 ,and press [Enter]
This is an example for the 700 series workstation:
Path Number Device Path Device Type
P0 SESCSI.2.0 TOSHIBA CDROM

P1 FWSCI.6.0 SEAGATE ST34572WS
P2 FWSCI.5.0 SEAGATE ST32171W
This is an example for the 800 series server:
N.B. The CDROM is usually connected to SCSI Single Ended Target 2 (SESCSI.2.0).
Path Number Device Path Device Path(mnem) Device Type
P0 10/0.6 SESCSI.2.0 Random access media

P1 10/12/5.3 FWSCI.6.0 Random access media
P2 10/12/6.0 FWSCI.5.0 Lan Module
This is an example of another modality to display the devices for the 800 series server:
N.B. In this case, the CDROM is connected to SCSI Single Ended Target 2 (8/16/5.2).
Path Number Device Path(dec) Device Type
P0 8/4.9 Random access media

P2 8/16/5.6 Random access media
P4 8/16/6.0 Lan Module
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 24 / 318
318
4.2.1.2 Step 2
When the LED of the CDROM device stops blinking, boot by entering the boot command:
Main Menu: Enter command or menu > boot P<n> , and press [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 before:
Interact with IPL (Y or N?) > n , and press [Enter]
The machine boots from the CDROM device, issuing some messages like:
HARD Booted
ISL Revision A.00.38 OCT 26, 1994
ISL booting hpux (;0): INSTALL
Boot
: disk (.....
N.B. Please ignore the following warning message:
WARNING: No dump device configured. Dump is disabled

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 25 / 318
318
4.2.1.3 Step 3
Again only for the 700 series workstation, the script explains how to declare the type of keyboard. It asks
you for the keyboard language:

DIN 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) PS2_DIN_Arabic 2) PS2_DIN_Belgian
3) PS2_DIN_Bulgarian 4) PS2_DIN_Canada_TBITS3
5) PS2_DIN_Canadian_French 6) PS2_DIN_Czech
7) PS2_DIN_Danish 8) PS2_DIN_Euro_Spanish
9) PS2_DIN_French 10) PS2_DIN_German
11) PS2_DIN_Greek 12) PS2_DIN_Hebrew
13) PS2_DIN_Hungarian 14) PS2_DIN_ITF_Danish
15) PS2_DIN_ITF_Euro_Spanish 16) PS2_DIN_ITF_Finnish
17) PS2_DIN_ITF_French 18) PS2_DIN_ITF_German
19) PS2_DIN_ITF_Italian 20) PS2_DIN_ITF_Japanese
21) PS2_DIN_ITF_Korean 22) PS2_DIN_ITF_Norwegian
23) PS2_DIN_ITF_Swedish 24) PS2_DIN_ITF_Swiss_French2
25) PS2_DIN_ITF_Swiss_German 26) PS2_DIN_ITF_T_Chinese
27) PS2_DIN_ITF_UK_English 28) PS2_DIN_ITF_US_English
29) PS2_DIN_Italian 30) PS2_DIN_JIS
31) PS2_DIN_Korean 32) PS2_DIN_Norwegian
33) PS2_DIN_Polish 34) PS2_DIN_Romanian
35) PS2_DIN_Russian 36) PS2_DIN_S_Chinese
37) PS2_DIN_SerboCroatian 38) PS2_DIN_Slovak
39) PS2_DIN_Swedish 40) PS2_DIN_Swiss_French2
41) PS2_DIN_Swiss_German2 42) PS2_DIN_T_Chinese
43) PS2_DIN_Turkish 44) PS2_DIN_UK_English
45) PS2_DIN_US_English
Enter the number of the language you want: <language_number> ,and press [Enter]
You have selected the keyboard language PS2_DIN_xxxxx

Please confirm your choice by pressing RETURN or enter a new number : [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 26 / 318
318
After this selection, still only for the 700 series workstation, the script prompts you this message:
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

If you choose to interact with SDUX during the installation, in

order to choose individual software products, do not select

either of the following bundles (xx varies with the ACE release):
B6193xx Workstation ACE

B6378xx Networking ACE
Selecting ether of these bundles will cause software load

errors. These bundles will appear in the software selection
screen, but do not select them. The B6193xx bundle will be
loaded automatically after the Core OS is installed. B7368xx
can be loaded by selecting Load 10.20 Networking ACE [ TRUE ]
in a following configuration screen.
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
Press any key to continue. > ,press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 27 / 318
318
4.2.1.4 Step 4
For the 700 series workstation:

Welcome to the HPUX installation process!
Use the <tab> and/or arrow keys to navigate through the following menus
and use the <return> key to select an item. If the menu items are not
clear, select the Help item for more information.
[ Install HPUX ]
[ Run a Recovery Shell ]
[ Cancel and Reboot ]
[ Advanced Options ]
[ Read SysAdmin Message ]
[ Help ]
Using [Tab] key or arrow keys select [Install HPUX] and press [Enter].
For the 800 series server:
Welcome to the HPUX installation process!
Use the <tab> and/or arrow keys to navigate through the following menus
and use the <return> key to select an item. If the menu items are not
clear, select the Help item for more information.
[ Install HPUX ]
[ Cancel and Reboot ]
[ Help ]
Using [Tab] key or arrow keys select [Install HPUX] and press [Enter].
4.2.1.5 Step 5
Now the HPUX install asks to enable the network with:
If you plan to use a network software depot to load the operating

system, you will need to enable networking at this time.
Would you like to enable networking now? [y]
Press: n , to proceed with the HP_UX Install Utility.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 28 / 318
318
4.2.1.6 Step 6
The HP_UX Install Utility prompt you with this screen:


HPUX Install Utility Select System Root Disk

This install utility has discovered the following disks attached to your
system. You must select one disk to be your system root disk. When
configured, this disk will contain (at least) the boot area, a root file
system and primary swap space.
Hardware Product Size

Path ID (Mega byte [Mb])
/\
| 8/0/19/0.5.0 ST32171W 2048 |
| 8/0/19/0.6.0 SR34572WS 4095 |
| |
| |
| |
| |
| |
\/
[OK] [Cancel] [Help]

Using the arrow keys select the disk that you want to use as root disk, then using [Tab] move the cursor
on [OK] and press [Enter] to confirm.
For A1354RM IM it is mandatory to choose the root disk in agreement with the A1354RM
Disk Partition shown in Table 4. Because the minimum size of the root disk is 4 Gbyte, if you
do not have a 4 Gbyte disk in your configuration, you MUST add one or more disk unit in the Root
Volume Group (vg00) when you will perform the Step 10 of this procedure (see Para. 4.2.1.10 ).
In the following table you will find the partitions requested for the RM application configuration.
N.B. The disk size shown in the table define the minimum requirements, if you have larger disks, you
can increase the size of the partitions, in agreement with the following rules.
N.B. The total amount of swap on Root Volume Group (vg00) have to be larger than the size of the
CoreMemory, because it can be also used as dump.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 29 / 318
318
Table 4. A1354RM Disk Partition for series 700 and series 800
A1354RM IM and Spare 9 + 4 Gb 9 + 9 Gb

Disk Partition
root disk data disk root disk data disk
9 Gb 4 Gb 9 Gb 9 Gb
(vg00) (vg01) (vg00) (vg01)
/stand 50 (lvol1) 100(lvol1)
Primary Swap 1110 (lvol2) 1600 (lvol2)
/ 2500 (lvol3) 3000 (lvol3)
/mirror 1500 (lvol1) 1900 (lvol4)
/backup 2500 (lvol2) 2000 (lvol5)
/alcatel 5000 (lvol4) 7600 (lvol1)
Secondary Swap 1000 (lvol2)
A1354RM IM and Spare 9 + 4 + 9 Gb

Disk Partition
root disk 9 Gb data disk 4 Gb data disk 9 Gb
(vg00) (vg01) (vg02)
/stand 100 (lvol1)
Primary Swap 1000 (lvol2)
/ 2600 (lvol4)
/mirror 2700 (lvol5)
/backup 4000 (lvol1)
/alcatel 8600 (lvol1)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 30 / 318
318
A1354RM IM and Spare 9 + 9 + 9 Gb
Disk Partition
root disk 9 Gb data disk 9 Gb data disk 9 Gb
(vg00) (vg01) (vg02)
/stand 100 (lvol1)
Secondary Swap I 1600 (lvol3)
/ 2800 (lvol4)
/tmp 500 (lvol5)
/var 600 (lvol6)
Secondary Swap II 1400 (lvol7)
A1354RM IM and Spare 9 + 4 + 9 + 9 Gb

Disk Partition
root disk 9 Gb data disk 4 Gb data disk 9 Gb data disk 9 Gb
(vg00) (vg01) (vg02) (vg03)
/stand 100 (lvol1)
Primary Swap/Dump 1600 (lvol2)
/ 2800 (lvol4)
Swap III 2500 (lvol5)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 31 / 318
318
Disk Partition
(vg00) (vg02) (vg03) (vg04)

/stand 100 (lvol1)
/ 2800 (lvol4)
/tmp 500 (lvol1)
/var 600 (lvol2)
A1354RM USM 6Gb 8 Gb 13 Gb 22 Gb 31 Gb

Disk Partition (vg00) (vg00) (vg00) (vg00) (vg00)
/stand 100 (lvol1) 100 (lvol1) 200 (lvol1) 200 (lvol1) 200 (lvol1)
Primary Swap 704 (lvol2) 704 (lvol2) 1408 (lvol2) 1408 (lvol2) 1408 (lvol2)
Secondary Swap 1000 (lvol3) 2200 (lvol3) 3200 (lvol3)
/ 100 (lvol3) 100 (lvol3) 200 (lvol4) 200 (lvol4) 200 (lvol4)
/opt 1200 (lvol4) 1200 (lvol4) 2000 (lvol5) 2000 (lvol5) 2000 (lvol5)
/tmp 100 (lvol5) 100 (lvol5) 500 (lvol6) 500 (lvol6) 500 (lvol6)
/users 52 (lvol6) 52 (lvol6) 200 (lvol7) 200 (lvol7) 200 (lvol7)
/home 600 (lvol7) 1200 (lvol7) 2400 (lvol8) 4800 (lvol8) 9600 (lvol8)
/usr 600 (lvol8) 600 (lvol8) 1200 (lvol9) 1200 (lvol9) 1200 (lvol9)
/var 300 (lvol9) 300 (lvol9) 600 (lvol10) 600 (lvol10) 600 (lvol10)
/alcatel 2044 3044 3000 8000 10000

(lvol10) (lvol10) (lvol11) (lvol11) (lvol11)
N.B. The vgx and lvolx are the notations relating to Volume Group and Logical Volume where the
partitions are mapped on the corresponding disk.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. Only in the USM configuration, if you have more than one disk, add the free disk space to the
/alcatel partition.
ED 02
957.130.892 W 3AL 61261 AA AA 32 / 318
318
4.2.1.7 Step 7
For both series (700 and 800) the HPUX Install Utility shows you the next screen:

HPUX Install Utility Select WholeSystem Configuration

Choose one item upon which to base your system configuration. You will
have a chance to modify that configuration.
Available WholeSystem Configurations: (Scroll to see entire list)

/\
| Standard LVM configuration |
| LVM Configuration with VxFS (Journaled File System) |
\/
WholeSystem Configuration Description:
/\
| |
| <Description of current selected configuration> |
| |
\/

Using the arrow keys select [Standard LVM configuration], then using [Tab] move the cursor on
[OK] and press [Enter] to confirm.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 33 / 318
318
4.2.1.8 Step 8
Modify only the values described follow:

For the A1354RM IM:

Software Selection: CDE Runtime Environment
How many disks in root group: One
/home Configuration None
For the A1354RM US:
Software Selection: CDE Runtime Environment

How many disks in root group: All
/home Configuration None
For 700 series workstation:

HPUX Install Utility View/Modify Basic Configuration

You may modify the following basic configuration parameters. Press OK to
save your changes.
Primary swap size [512 >]

Secondary swap size [None >]
Software Selection [CDE Runtime Environment >]
Load 10.20 Networking ACE [Falsee >]
Software Language [English >]
Locale Setting [default (C) >]
File system file name length [Long >]
/home Configuration [Minimal>]
How many disks in root group [One >]
Make volatile dirs separate [True >]
Create /export volume [False >]


Using the arrow keys select the parameter and press [Enter] to open the menu, with the arrow keys choose
the value, then press [Enter] to confirm.
Using [Tab] move the cursor on [OK] and press [Enter] to get to the next step.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 34 / 318
318
For 800 series server:

HPUX Install Utility View/Modify Basic Configuration

You may modify the following basic configuration parameters. Press OK to

save your changes.
Primary swap size [512 >]

Secondary swap size [None >]
Software Selection [VUE Runtime Environment >]
Software Language [English >]
Locale Setting [default (C) >]
File system file name length [Long >]
/home Configuration [Minimal>]
How many disks in root group [One >]
Make volatile dirs separate [True >]
Create /export volume [False >]


Using the arrow keys select the parameter and press [Enter] to open the menu, with the arrow keys choose
the value, then press [Enter] to confirm.
Using [Tab] move the cursor on [OK] and press [Enter] to get to the next step.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 35 / 318
318
4.2.1.9 Step 9

HPUX Install Utility System Configuration


Any data on the following disks will be destroyed ... :
Hardware Path Product ID Size (Mb) Disk Use Volume group

/\
| 8/0/19/0.6.0 ST34572WS 4095 LVM vg00 |
| |
\/
Uncofigured space from those disks: 1220 Mb
... and the following file systems and swap space will be created:
Mount directory Size (Mb) Usage Disk group
/\
| / 84 HFS vg00 |
| /stand 48 HFS vg00 |
| (swap) 512 swap vg00 |
| /opt 252 HFS vg00 |
| /tmp 32 HFS vg00 |
\/
For more advanced configuration options...[Modify Disk Parameters ...]
[Modify FS Parameters ... ]


If you are installing an A1354RM Presentation, skip to the paragraph 4.2.1.12. Instead, using [Tab] select
[Modify Disk Parameters ...] and press [Enter], to modify the disk partitioning.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 36 / 318
318
4.2.1.10 Step 10

HPUX Install Utility Specify Disk Usage

Select a disk from the list, specify the disk usage scheme and (if
applicable) the volume group, then select Modify to apply the changes.
/\
| Hardware Product Size Disk Volume |
| Path ID (Mb) Usage Group |
| /\ |
| | 8/0/19/0.6.0 ST34572WS 4095 LVM vg00 | |
| | 8/0/19/0.5.0 ST32171W 2048 unused | |
| | | |
| | | |
| \/ |
| Disk Usage: [ LVM >] |
| Volume Group: vg00____ |
| |
| [Modify] |
\/
[Modify Disk Parameters...] [Modify Volume Group Parameters...]


Now you have to define the usage of the hard disks in agreement with the A1354RM Disk Partition shown
in Table 4.
Using arrow keys select the unused disk, then press [Tab] to get the Disk Usage menu (that in the
mean time will be change in used), press [Enter] to open the menu. Using arrow keys move the cursor
on [ LVM >], and press [Enter] again, assign this disk to the Volume Group vg01, move with [Tab]
on [Modify] and press [Enter] to modify the configuration.
If you have a data disk bigger the 4 GByte, execute the following step: when the disk in configuration will
have vg01 in column Volume Group, select [Modify Volume Group Parameters...] and
press [Enter]. The system shows you the next windows:
If you do not have configured the Root Volume Group (vg00) with 4 Gbyte disk you have to
choose one or more disks in your configuration, and add them to the Root Volume Group (vg00)
just follow the instructions above entering vg00 instead of vg01.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 37 / 318
318
4.2.1.11 Step 11

HPUX Install Utility Modify Volume Group Parameters


Select the volume group for which to modify parameters, set the desired
parameters, then select Apply to apply the change. A default keyword
signifies that the default values as specified by the vgcreate(1m) com-
mand will be used. Otherwise the specified value will be used.
Use care when making changes, the default values should be sufficient.
Volume Group Total Size (Mb)

/\
| vg00 4052 |
| vg01 8680 |
\/
Maximum Physical Extents: default

Maximum Logical Volumes: default
Maximum Physical Volumes: default
Physical Extents Size (Mb): [4 >]

[OK] [Apply] [Cancel] [Help]

Using the arrow keys select the Volume Group vg00, then using [Tab] move the cursor on Maximum
Physical Extents: default and substitute default with 4000. Select [Apply] and then [OK]
to leave the window. Repeat this step for the Volume Group vg01.
You came back at the previous window, press [Tab] until the cursor will get [OK] and press [Enter] to
confirm the modification on Disk Usage.
Press still [Tab] until the cursor will get [OK] and press [Enter] to return at the System Configuration
window.
N.B. The total amount of available disk space to have compliant with the disk requirements shown
in Table 4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 38 / 318
318
4.2.1.12 Step 12
This is the screen that the system shows you:




/\
| 8/0/19/0.6.0 ST34572WS 4095 LVM vg00 |
| 8/0/19/0.5.0 ST32171W 2048 LVM vg00 |
\/
File systems and swap space will be created:
/\
| / 84 HFS vg00 |
| /stand 48 HFS vg00 |
| /opt 252 HFS vg00 |
| /tmp 32 HFS vg00 |
\/


Using the arrow keys select [Modify FS Parameters ...] and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 39 / 318
318
4.2.1.13 Step 13

HPUX Install Utility Configure File System


To add, enter data and select Add. To modify/Remove, place cursor on
list item. To modify, enter data and select Modify. To remove, select
Remove.
/\
| Mount Size Volume Disk |
| Directory (Mb) Usage Group |
| /\ |
| | / 84 HFS vg00 | |
| | /stand 48 HFS vg00 | |
| | (swap) 512 swap vg00 | |
| | /opt 252 HFS vg00 | |
| \/ |
| Disk Group [vg00 >] Information for vg00 |
| Volume usage [HFS >] Space available: 1220 Mb |
| Mount Directory / LVM Physical extent size 4Mb |
| Size (Mb) 60 |
| [Add] [Modify] [Remove] |
\/
[Modify Logical Volume Parameters...][Modify File system Parameters...]


Look at your configuration table and configure the system as explained below.
N.B. For the A1354RM disk partition, please refer to the Table 4.
If there are some partitions that are not requested for the application configuration, select them using arrow
keys, then press [Tab] to get out of the scroll area, select [Remove] and press [Enter] to remove them.
If there are some partitions that are requested and not included in the list, with [Tab] get out of the scroll
area on Mount Directory, digit the new partition, then move on Size (Mb) always with [Tab] and
modify the size of the partition. Then using [Tab] again, select [Add] and press [Enter].
Then select one of the lines in the scroll area of the window, then press [Tab] to get out of the scroll area
on Size (Mb), modify the size of the partition, then using [Tab] select [Modify] and press [Enter].
Now you have to configure the data disk under the Volume Group vg01: select Disk Group and then
vg01. Add the partitions requested.
When all the partitions are as requested, with [Tab] select [OK] and press [Enter] to align the default disk
configuration to the requested one.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 40 / 318
318
4.2.1.14 Step 14
Now you return at the window HPUX Install Utility System Configuration:



/\
| 8/0/19/0.6.0 ST34572WS 4095 LVM vg00 |
| 8/0/19/0.5.0 ST32171W 2048 LVM vg00 |
\/
File systems and swap space to be created:
/\
| / 1240 HFS vg00 |
| /alcatel 2200 HFS vg00 |
| /tmp 100 HFS vg00 |
| /var 248 HFS vg00 |
\/


Using [Tab] move the cursor on [OK] and press [Enter] to confirm.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 41 / 318
318
4.2.1.15 Step 15
If the disk that you choose to be the HPUX root disk, has been already used in the past as file system,
the following message appears on the screen:


| HPUX Install Utility Message Dialog |
/\
| Before continuing, you must address any error listed below. |
| You may choose to continue in the presence of warning or notes. |
| (You may have to scroll to see the entire list.) |
| |
| WARNING: Using a combined root (/) and boot volume (stand) |
| is no longer a recommended configuration. The preferred system |
| layout for 10.20 and future LVM system is to use separate root |
| (/) and boot (stand) volumes. |
| |
| WARNING: The disk at: 8/0/19/0.6.0 (C3325W) appears to contain |
| a file system and boot area. Continuing the installation |
| will destroy any existing data on this disk. |
| |V|
| [Continue...] [Modify Configuration...] |
\/
You have to move the cursor on [Continue...] and press [Enter] to proceed with the installation of
HPUX.
4.2.1.16 Step 16
The HPUX Install Utility issues the following screen to asks you if you want to interact with Software
Distributor tool:

HPUX Install Utility Enter SDUX swinstall information

The SD_UX software distribution utility, swinstall, will actually load
the HPUX software on your system. (This will take place after the disk
and file system are configured.)
The software selections you have already specified should be sufficient,

but you might want to interact with SDUX swinstall to view or modify
the software selection.
Do you want to interact with SD_UX swinstall ? [ No > ]


1AA 00014 0004 (9007) A4 ALICE 04.10
Using [Tab] move the cursor on [OK] then press [Enter]. Wait for the download.
ED 02
957.130.892 W 3AL 61261 AA AA 42 / 318
318
4.2.1.17 Step 17
N.B. The graphical window reported below are related to the installation steps on the Series 700
workstation, on the Series 800 server youll have to answer (in the same way) to the same
questions but the interface will be in character mode.

After that the SD swinstall utility start the software installation issuing many messages to log the process,
at the end of this phase, you have to set the machine parameters answer the following windows:
Figure 2. HPUX Set Parameters Welcome window
At this window click on Yes to proceed in the parameter setting.
4.2.1.18 Step 18
Figure 3. HPUX Set Parameters Confirmation
At this window click on Yes, Continue to proceed in the parameter setting.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 43 / 318
318
4.2.1.19 Step 19
Now the HPUX Set Parameters Utility issues the following window asking you for the name of the
machine (hostname).

Type the hostname on your choice, then click on OK.

In the hostname is not allowed to use the special characters (i. e. and _ ). Only alphabetic
and numeric (but not as first) characters are allowed.
Figure 4. HPUX Set Parameters Hostname Definition
HPUX Set Parameters Utility asks you to confirm the hostname with:
Figure 5. HPUX Hostname Confirmation
Check the name of the host, it is the right one, click on Yes.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 44 / 318
318
4.2.1.20 Step 20
The next step is the time zone selection. The next windows show you the first level of time zone selection:
click on the button next to your location and then click on OK.
In the following example show how to select the time zone for GMT0. On the first level Europe is selected,
in the second one you have to choose your Time Zone and follow the instructions given by the system.
This is an example of GMT0 time zone:
Select a location Select a Time
Figure 6. HPUX Set Parameters Time Zone First Selection
First select Europe then click on OK button, then Unlisted Time Zone and click on OK button.
Confirm
Example of unlisted time zone
Figure 7. Set Unlisted Time Zone
Insert the GMT0 time zone and click on OK button, then confirm at the Confirm Time Zone window.
1AA 00014 0004 (9007) A4 ALICE 04.10
Now, the utility issue the next window to allow you to set the right system time. Usually the time displayed
is wrong, and you have to click on No to get the window that allows you to change the date/time.
ED 02
957.130.892 W 3AL 61261 AA AA 45 / 318
318
Figure 8. Set Data and Time
The window contains the current values of system date/time. To change them, click on the input fields that
you want to modify, delete its contents, and type the right one.
When you have changed all the information that you need, click on OK to activate your modifications.
If the system shows you the following window:
Figure 9. Reboot System Question
Click on No, do not reboot button.
REMEMBER: DO NOT ANWER YES AT THE REBOOT QUESTION !

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 46 / 318
318
4.2.1.21 Step 21
As last action HPUX Set Parameters Utility requires if you want to set the root password:
Figure 10. HPUX Set Parameters Root Password Set Request
If you choose to set the root password, clicking on Yes the next window will be open on the screen. You
have to type the password at prompt.
N.B. For security reason the password is not echoed.
N.B. The root installation password for the factory is install10.
Figure 11. HPUX Set Parameters Root Password 1st window
In order to prevent any error, HPUX Set Parameters asks you to retype the password.
Figure 12. HPUX Set Parameters Root Password 2nd window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 47 / 318
318
If you have typed two times the same password, HPUX Set Parameters completes its task accepting your
root password with:

Figure 13. HPUX Set Parameters Root Password Accepted.
4.2.1.22 Step 22
The next step executed in the HPUX Set Parameters Utility is to set the TCP/IP address defined for this
machine: click on Internet Address box and type the TCP/IP address, then click on the OK button.
Figure 14. HPUX Set Parameters TCP/IP Address Definition
HPUX Set Parameters Utility asks you to confirm your choice with:
Figure 15. HPUX Set Parameters TCP/IP Address Confirmation

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 48 / 318
318
4.2.1.23 Step 23
Now the utility asks you to configure some additional network parameters, that are not requested in this
moment. Click on No to skip this phase.
Figure 16. HPUX Set Parameters Configure Additional Network Parameters
4.2.1.24 Step 24
HPUX Set Parameters Utility asks you to choose among the configuration of the machine as font client,
font server or neither. Click on No button to skip the font client/server configuration.
4.2.1.25 Step 25
The system shows you the last window System Parameters. Click on Close .
After this question the machine reboot and after few minutes, prompt you for login.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 49 / 318
318
4.2.2 Add Tape Driver
Meaningful only for series 700

If your system has a tape driver connected, or you foreseen to use a tape driver in the future, you have

to configure the stape driver in the HPUX kernel as shown in this section.
4.2.2.1 Add Tape Driver with graphic interface
First of all you have to verify if the tape driver is known to the system. Login as root and start the SAM
tool with the command:
# sam ,and press [Enter]
With double click of the mouse select and open the Kernel Configuration icon:
Figure 17. SAM
With double click of the mouse select and open the Drivers icon.
Figure 18. Sam Areas: Kernel Configuration

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 50 / 318
318
Search for the name stape and verify in the Pending State column if the tape driver status is In.
Figure 19. SAM Drivers
If its in, select the menu File, Exit twice to exit SAM.
Instead, choose with the arrow keys the driver Tape, select it with the space bar, with the mouse select
the menu Actions, Add driver to Kernel as shown Figure 20.
Figure 20. SAM Drivers Add Driver

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 51 / 318
318
Verify that the tape driver in the Pending State is in (Figure 21. ), then select the menu Actions and
Create a new kernel (Figure 22. ).

Figure 21. SAM Driver
Figure 22. SAM Driver Create a New Kernel
Now the system asks the permission to reboot the workstation. Confirm the reboot with Yes.
Figure 23. SAM Confirm - 1

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 52 / 318
318
The sam tool issues a new message asking if you want to move the kernel and reboot the system.
Confirm the action with OK.
Confirm again at the message with OK , then the workstation reboots.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 53 / 318
318
4.2.2.2 Configure Tape Driver without graphic interface
If you dont have the graphic interface, perform these steps to configure the tape subsystems in the HPUX
kernel, to check if that driver is already configured in the kernel and, if not, add it:

Login as root and start the SAM tool with the command:
# sam ,and press [Enter]
Starting the terminal version of sam...
To move around in sam:
use the Tab key to move between screen elements

use the arrow keys to move within screen elements
use CtrlF for contextsensitive help anywhere in sam
On screens with a menubar at the top like this:
||
|File View Options Actions Help|
||
use Tab to move from the list to the menubar

use the arrow keys to move around
use Return to pull down a menu or select a menu item
use Tab to move from the menubar to the list without selecting a
menu item
use the spacebar to select an item in the list
On any screen, press CTRLK for more information on how to use the
Keyboard.
Press [Enter].
Using the arrow keys, select the Kernel Configuration > SAM area and press [Enter].
Using the arrow keys again, select Drivers and press [Enter].
With the arrow keys, move the cursor on the stape and verify in the Current State column if the tape
driver status is In.
If the driver status is In , you can leave this section of procedure in this way:
Press [Tab] and [f] to open the File menu.

Using the arrow keys select the Exit choice, and press [Enter].
Press [Tab] and [f] to open the File menu another time.
Using the arrow keys select the Exit SAM choice, and press [Enter].
Otherwise, if the status is Out, the tape is not configured. In this case you have to proceed with the
following actions.
Press [Tab] and [a] to open the Action menu.
Using the arrow keys, select the Add Driver to Kernel and press [Enter]: the value in the
1AA 00014 0004 (9007) A4 ALICE 04.10
Pending state column will change from Out to In.
ED 02
957.130.892 W 3AL 61261 AA AA 54 / 318
318
When you have completed the checks and the modifications, press [Tab] and [a] to open the Action
menu and select Create a New Kernel.
The system asks if you are sure to create a new kernel: moving on the menu with [Tab], select [OK] and
press [Enter].
The SAM tool issues a new message asking if you want to move the kernel and reboot the system: moving
on the menu with [Tab], select [OK] and press [Enter].
The SAM tool replace the current HPUX with the new one and reboots the system.
4.2.3 Configure floppy drive
If you have a floppy drive, you have to give the necessary rights to the floppy special device file:
# cd /dev/floppy ,and press [Enter]

# chmod o+wr c0t1d0 ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 55 / 318
318
4.2.4 Retrieve Installation Procedure
To reduce the risk of error installation of the ALMAP HP4.2 software a script is provided to automatically
perform these activities.

This section shows how to retrieve this script from the bootable medium.
4.2.4.1 Find the CDRom
Login as root.
Use the ioscan command to find the cdrom device file:
# ioscan fn C disk ,and press [Enter]
Example of ioscan command output:
Class I H/W Path Driver S/W State H/W Type Description

=======================================================================
disk 0 8/0/19/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST34572WS
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/0/19/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST32171W
disk 3 8/16/5.1.0 sdisk CLAIMED DEVICE IBM DORS32160
disk 2 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CDROM ...
4.2.4.2 For the 700 Series
To perform the download of the block one, insert the bootable C742C17D_TSD CDROM 1/2 in the driver
and execute the following commands:
# mount r /dev/dsk/<cdrom device file> /SD_CDROM ,and press [Enter]

# cd /tmp ,and press [Enter]
# cpio id < /SD_CDROM/C742C17d_TSDBLOCK01 ,and press [Enter]
4.2.4.3 For the 800 Series
To perform the download of the block one, insert the bootable C842C17D_TSD CDROM 1/2 in the driver
and executing the command described below.

# cpio id < /SD_CDROM/C842C17d_TSDBLOCK01 ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 56 / 318
318
4.2.4.4 Create the PATCH_NOSAVE file
Before start the installation, in order to prevent the unuseful saving of files replaced by the HP patches,
you have to create the empty file PATCH_NOSAVE with:
# cd /var/adm/sw/patch ,and press [Enter]

# mkdir patch ,and press [Enter]
# cd patch ,and press [Enter]
# touch PATCH_NOSAVE ,and press [Enter]
The existence of this file disable the automatic save of the patches that will be install.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 57 / 318
318
4.2.5 Installation for Alcatel ALMAP HP4.2 Platform
N.B. Due the number of reboot that the installation procedure requires it can take 2 hours or more
(depending on the hardware).

To start the installation execute the following commands:

# etc/install10 required ,and press [Enter]
The system gives you the following choice:
For the series 700:
Workstation Type:
CST = Construction Workstation

NMCE = A1354IF 1.0 Slave Workstation
NMCM = A1354IF 1.0 Master Workstation
NMCP = A1354IF 1.0 Presentation Workstation
NNM = A1354NN 2.2/5.0 Information Manager (Master)
NNP = A1354NN 2.2/5.0 User Services (Presentation)
NNS = A1354NN 2.2/5.0 Information Manager (Spare)
QAM = A1354QA 2.x Information Manager (Master)
R2GM = 1300NMC2 1.0 Master Workstation
R2GP = 1300NMC2 1.0 Presentation Workstation
RMM = A1354RM 5.2 Information Manager (Master)
RMP = A1354RM 5.2 User Sevice Manager (Presentation)
RMS = A1354RM 5.2 Information Manager (Slave)
RMSH3M = A1354RM 5.2 + A1353SH 5.3 Master Workstation
RMSH3P = A1354RM 5.2 + A1353SH 5.3 User Sevice Manager (Presentation)
RMSH3S = A1354RM 5.2 + A1353SH 5.3 Spare Workstation
SH3E = A1353SH 5.3 Element Manager Workstation
SH3M = A1353SH 5.3 Master Workstation
SH3P = A1353SH 5.3 Presentation Workstation
SH3S = A1353SH 5.3 Spare Workstation
VPNM = A1355VPN 2.1 Master Workstation
VPNS = A1355VPN 2.1 Spare Workstation
Enter WS type (CST NMCE NMCM NMCP NNM NNP NNS QAM R2GM R2GP RMM RMP RMS
RMSH3M RMSH3P RMSH3S SH3E SH3M SH3P SH3S VPNM VPNS) : <WS_type> ,and press
[Enter]
You have to respect the choice made during the disk partition allocation, because each one may
have different requirements in term of disk and RAM capacity, or configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 58 / 318
318
For the series 800:
INSTALLATION FOR ALCATEL HP2 PLATFORM

Workstation Type :

RMSH3P = A1354RM 5.2 + A1353SH 5.3 User Service Workstation
(Presentation)
Enter WS type (NMCE NMCM NMCP NNM NNP NNS QAM R2GM R2GP RMM RMP RMS
RMSH3M RMSH3P RMSH3S SH3E SH3M SH3P SH3S VPNM VPNS): <WS_type> ,and press
[Enter]
According to the type of station some optional softwares are proposed to be loaded or not. For more
explanations please refer to the next paragraph 4.2.6 Optional software allocations.
The follow is an example of RMM installation:
Optimal Software Selection
Would you like to install :
100BT 100BT/9000 Software (y|n|q) ? :

100VG 100VGAnyLAN/9000 EISA (y|n|q) ? :
Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0 (y|n|q) ? :
ENWARE7 for ENTRIA/ ENVIZEX XTerminals (y|n|q) ? :
ENWARE8 for ENTRIA II/ ENVIZEX II XTerminals (y|n|q) ?
HPUXMIRROR MirrorDisk/UX (y|n|q) ? :
OTS9000FULL HP OSI Transport and Services Full for HP 9000 (y|n|q) ? :
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 59 / 318
318
4.2.6 Optional Softwares allocation
Some softwares, corresponding to certain functionalities, are optional according to the type of machines.
The following table gives the permitted configurations:

Functionality Software RMM/RMS RMP
100VGAnyLan Lan Driver (1 ) opt no
100BaseT Lan Driver opt (2 ) no
Apache and Tomcat Web Servers opt (3 ) no
XTerminal ENWARE 7 opt (4 ) opt (4 )
XTerminal ENWARE 8/9 opt (4 ) opt (4 )
Disk Mirror HPUXMIRROR opt (5 ) opt (5 )
High Availability MC/Service Guard no (6 ) no
OTS9000 Full OSI Stack opt (7 ) no
Figure 26. Optional 3rd part softwares
1) The 100VgAnyLan software has to be installed only when a 100VGAnyLan card is present
in the system configuration.
2) The 100BaseT software has to be installed only when a 100BaseT card is present in the system
configuration. It is usefull on all the systems with more then one LAN cards except HP9000
C100/C110 workstations.
3) The Apache and Tomcat Web Server software has to be installed only if you have to install also
the 1355VPN.
4) ENWARE 7 is for Xterminal ENTRIA and ENVIZEX, ENWARE 8 is for ENTRIA 2 and ENVIZEX
2. If ENTRIA or ENVIZEX plus ENTRIA 2 or ENVIZEX 2 must be connected, both versions of
ENWARE must be installed.
5) The MIRROR software has to be installed only if the mirror disk configuration is planned on your
system. Remember that the disk mirror configuration is supported only on the HP Server 800
series (see Chapter 12 at page 249).
6) The High Availability MC/Service Guard software have to be installalled only with OSCluster
configuration.
7) The OTS 9000 full stack is requested when there are any A1353WX system in the SDH
configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 60 / 318
318
4.2.7 Confirm
The system asks you the confirm of the software packages selected.
Example of RMM installation:

This is the list of software packages:
(R) PERLTK Perl/Tk release 5.003 (22Jul97)

(R) TCLTK Tcl/Tk release 8.2.1
(R) FBBOOTAPE Utility to create bootable tape for Full BackuP/Restore
(R) TOOLS Utilities (a2ps, super, unzip, xloadimage)
(R) DIAGTOOLS HPUX 10.0 Support Tools Bundle
(R) OTS9000 HP OSI Transport and Services Lite for HP 9000
(R) HPOV HP OpenView DM Platform B.05.03
(R) ILOGVIEWS Ilog Views 2.41
(R) XSW700GR1020 B.10.20.48 General Release 700QPK1020 Ws Quality Pack
(R) ALMAPHP4.2PATCHES ALMAP HP4.2 Platform Patches
(R) HPPATCHES Others Patches
(R) ttsession Aug 99 PHSS_19482
(R) ALCATELSYSCONF Alcatel System Configuration Scripts TSD Edition
(R) JAVA development Kit and SWING for s700 10.20 (21Oct98)
(R) 100VG 100VGAnyLAN/9000 EISA
(O) Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0
(O) 100VG 100VGAnyLAN/9000 EISA
(O) 100VGPATCHES 100VGAnyLAN/9000 EISA Patches
(O) 100BT 100BT/9000 Software
(O) 100BTPATCHES 100BT/9000 Patches
(R) Netscape COMMUNICATOR 4.08
(R) Netscape FASTTRACK Server 03.01.05
(R) JETADMIN HewlettPackard JetAdmin for Unix Utility
(R) ORACLE Oracle 7.2.3
NOTE:ORACLE only
(R) ORACLE Patch BUG338507

(R) ORACLEDEV2000 Oracle Develop 2000
NOTE:ORACLE_DEV2000 only
(R) ORACLESRODDBO Oracle SRO DDBO 7.2.3

NOTE:ORACLESRODDBO only
(R) WORLDVIEW Interleaf World View 2.2.1

NOTE:WorldView only
(R) GO GLOBAL V1.6.5.1 Host kit software

(R) Expect 5.31
(R) Ignite UX 10.20 V2.4.307
^
|
+( Requested / Optional)
Please confirm to start the installation (y|n|q) ? y ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
After the confirm, the system start the installation of the selected softwares. This operation take some
minutes.
ED 02
957.130.892 W 3AL 61261 AA AA 61 / 318
318
4.2.8 Loading
Loading of disks is automatically launched.

=>date and time

=>Creating physical volume on ...
....
...
Physical volume has been successfully created.
Start : date and time

End : date and time
Ignore Warning Messages if there is
..................................................
After loading the system software the station reboots automatically.

Wait the HP CDE login screen. Log as user root with password install10.
4.2.9 Post installation step
Now you have to copy the bootape_version and HPUX Kernel description (*.system) file in the
/usr/local/data directory and to create the wstype file:
..,sys,root # cd /usr/local/data ,and press [Enter]

..,sys,root # cp /tmp/bootape_version . ,and press [Enter]
The next operations depend of the machine type:
a) only for IM machine:
..,sys,root # echo RMM > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMM.system . ,and press [Enter]
b) only for USM workstation:
..,sys,root # echo RMP > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMP.system . ,and press [Enter]
c) only for Spare workstation:
..,sys,root # echo RMS > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMS.system . ,and press [Enter]
The validity of the installation must be now verified; go on with chapter 4.4 Check the validity of the
Installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 62 / 318
318
4.2.10 Load OTS 9000 drivers into kernel

To be able to start OTS properly, it is necessary to load the OTS drivers into the kernel. To perform this
step execute the following commands:
..,sys,root # cd /stand ,and press [Enter]
Edit the system file:
..,sys,root # vi system ,and press [Enter]
Type /Drivers and press [Enter]
Then using the arrow keys move the cursor under the title and press [o] (lowercase) to create a new line.
Insert here the first string: strlan and press [Enter], then insert the second string: rfc1006.
To save and escape from the file press [Esc] and type :x! and press [Enter].
Now is necessary to rebuild and load the kernel:
..,sys,root # mk_kernel ,and press [Enter]
Compiling /stand/build/conf.c...
Loading the kernel...
/usr/ccs/bin/ld: (Warning) Linker features were used that may not be
supported in future releases. The +vallcompwarnings option can be used
to display more details, and the ld(1) man page contains additional
information. This warningscan be supposed with the +vnocompatwarnings
option.
Copy the vmunix file:
..,sys,roo # cp vmunix vmunix.old ,and press [Enter]
Rename the vmunix_test file just compiled by the mk_kernel command:
..,sys,root # mv build/vmunix_test vmunix ,and press [Enter]
To activate the new HPUX image you have to perform a system reboot:
..,sys,root # reboot ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 63 / 318
318
4.3 Installing HPUX 10.20 from Bootable Medium
This chapter describes how to manage with the bootable media interface with the different configurations
that it allows.

After the boot to launched from the CDROM device, the process will have completely installed on the hard

disk the system part of the software.
4.3.1 Boot the machine
Power on the HP 9000 system. If your system is active, simply power off and power on it again.
on the screen:

You have to identify the medium driver that you want to use in the provided device list.
This is an example for the series 700:

P1 FWSCSI.6.0 SEAGATE ST34572WS
P2 FWSCSI.5.0 SEAGATE ST32171W
This is an example for the series 800:

P1 10/12/5.3 FWSCSI.6.0 Random access media
P2 10/12/6.0 FWSCSI.5.0 Lan Module
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 64 / 318
318
This is an example of another modality to display the devices for the 800 series server:

Insert the bootable CDROM 1/2 for your machine type (series 700 or series 800) into the CDROM driver.
Interact with IPL (Y or N) > n ,and press [Enter]
Booting...
ISL Revision A.00.29 July 17, 1993
...
The script of installation allows to :
Keyboard selection
Date&Time
Application selection (the workstation type)
Disk configuration (system partitions)
Network informations (hostname , IP address)
Optional Softwares selection
Source Media selection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 65 / 318
318
4.3.2 Keyboard selection
The script explains how to declare the type of keyboard. It asks you if the keyboard that it has set is right:

This is the ALCATEL BOOTMEDIUM C742C17d (26Sep00)

The keyboardmap has been set to PS2_DIN_US_English (QWERTY)
Enter y if you agree, or n to select another one (y|n|q):
Enter y if the keyboard is right, otherwise enter n and the system prompts you:


Please confirm your choice by pressing RETURN or enter a new number :
[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 66 / 318
318
4.3.3 Set up the Date
The current timestamp is shown to allow to check it and set up if needed the right date and time:
The current date is date and time

Please confirm (y|n|q) ? :
If the timestamp is wrong, enter: n, then press [Enter]. The procedure issues the following message
requesting the new date and time:
Enter the new date (mmddhhmm[yy]) :
where: mm means month between 1 and 12

dd means day between 1 and 31
hh means hour between 0 and 23
mm means minute between 0 and 59
yy means year between: [70 and 99] or [00 and 69] (Optional)
where: [70 and 99] means the years between 1970 and 1999
[00 and 69] means the years between 2000 and 2069
The new date MUST be provided adding or subtracting at the local current time the number of
hours your time is offset from Greenwich Mean Time (GMT) at zero degrees longitude.
The system asks again:

Press y to confirm and proceed or n to change again the date.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 67 / 318
318
4.3.4 Application Selection
Now the procedure shows you the list of the supported application platforms that it is able to prepare. You
have to choose which application and which configuration of it you want to install, typing the associate

name at the procedure request:

For the series 700:
Workstation Type :

RMP RMS RMSH3M RMSH3P RMSH3S SH3E SH3M SH3P SH3S VPNM VPNS) : <WS_type>
,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 68 / 318
318
For the series 800:

Workstation Type :

Enter WS type (NMCE NMCM NMCP NNM NNS R2GM RMM RMS RMSH3M RMSH3S SH3M
SH3S VPNM VPNS): <WS_type> ,and press [Enter]
Depending by the application and configuration the disk management can be different.
4.3.5 Disk configuration
The disk configuration depends by the application requirements. The disk configuration can be done using
a single volume group to include all disks or a different volume group for each physical volume, because
of these capabilities here you can find an example for each set of request issued by the installation
procedure.
N.B. In any case you must satisfy the disk requirements show in Table 4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 69 / 318
318
4.3.6 RM Installation
The system retrieves the list of the hard disks in configuration, checks if the required amount of disk space
is available, and configure the disk as well for the selected application.

The following example contains disk size and disk path for the RMM installation:
Hardware detection in progress, please wait ...
The install script detects the disks configuration of the machine. Example :
Hard disk : c0t5d0 detected 8886 MB


Total: 13080 MB
Boot disk : c0t6d0 selected 4194 MB
The procedure shows you the hard disk found in the system configuration, with the related size. Then asks
you to select the disk configuration. Example:
Select the disk configuration for RMM installation

Root disk Application disks
1 4096000 (c0t6d0) 2048000 (c0t5d0)
2 4096000 (c0t6d0) 4096000 (c0t5d0)
3 8192000 (c0t5d0) (same as root disk)
4 8880000 (c0t5d0) 4096000 (c0t6d0)
Enter the disk configuration number, ? to look of other configuration

or press return to abort: <Number_configuration> ,and press [Enter]
Now the system asks you the confirm. Example:
The selected configuration for RMM is

8880000 (c0t5d0) 4096000 (c0t6d0)
Do you confirm the disk configuration? (y|n|q) ? y ,and press [Enter]
At this step if your choice is wrong and you type n, the system gives you the # prompt, then type
etc/autoexec to restart the configuration script .
All the disk assigned to the application will be format again. The contents of those disks
will be lost!.
N.B. The install script allows to do particular configurations for specific needs, that requires flexible
installation procedure. For an installation on customer site perform a standard
installation, that means answer yes to the default proposals to have an optimized usage
of the machine in term of security and performance. Only this option is described here.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 70 / 318
318
4.3.7 Network Information
The next install step allows you to define the Network Information.
the hostname is free, it can be dictated by the customer, but must have not more than 8 characters,
the lower case is raccomanded, and the first one must be an alphabetic character.
The suggested names are :
axrmm for the IM RM WS

axrmp# for the US RM WS number #
In the hostname is not allowed to use the special characters as ,for example, (minus) or _
(underscore). Only alphabetic and numeric (but not as first) characters are allowed.
The IP address is a free different address dictated by the customer and assigned to each machine.
Must have the xxx.xxx.xxx.xxx format and must be unique in the network.
Network information:
Enter the Hostname : <WS_hostname> ,and press [Enter]
Enter the IP addr. : <IP_address> ,and press [Enter]
Now the system asks if you want to set a default gateway:
Would you like to set a default gateway (y/n/q)? [y] : ,and press [Enter]
If you want to set it, press y and remember that the default gateway must be your default router:
Enter Router IP address [151.98.8.254] : <Router_IP_Address> ,and press [Enter]
Enter the Netmask[] : <Netmask> ,and press [Enter]

or press <RETURN> to use default netmask : <Default_netmask> ,and press [Enter]
4.3.8 Optional Softwares selelection
The system asks you which software you want to install. Example of RMM installation:
N.B. According to the type of machine some optional softwares are proposed to be loaded or not.
For more explanations please refer to the paragraph 4.2.6 Optional software
allocations.
Optional Software Selection:
Would you like to install:

Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0 (y|n|q) ? :
ENWARE7 for ENTRIA/ ENVIZEX Xterminals (y|n|q) ? :
ENWARE8 for ENTRIA II/ENVIZEX II Xterminals (y|n|q) ? :
OTS9000FULL HP OSI Transport and Services Full for HP 9000 (y|n|q) ?
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 71 / 318
318
4.3.9 Source media selection
Now the system asks you the media that you want to use:

For the series 700:

Source Media Selection:
Please enter the device file of source media [/dev/dsk/clt2d0]: press [Enter]
For the series 800:
Please enter the device file of source media [cxtxdx]: ,and press [Enter]
You have taked note of the sescsi value before. The boot path SESCSI.2.0 or 8/16/5.2 corresponding
to the c1t2d0.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 72 / 318
318
4.3.10 Confirm
The system asks you the confirm of the software packages selected. Example of RMM installation:
This is the list of software packages :


(R) FBBOOTAPE Utility to create bootable tape for Full BackuP/Restore
(R) XSW700GR1020 B.10.20.48 General Release 700QPK1020 Ws Quality Pack
(R) HPPATCHES Others Patches
(R) ttsession Aug 99 PHSS_19482
(R) ALCATELSYSCONF Alcatel System Configuration Scripts TSD Edition
(R) JAVA development Kit and SWING for s700 10.20 (21Oct98)
(R) 100VG 100VGAnyLAN/9000 EISA
(O) Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0
(O) 100VG 100VGAnyLAN/9000 EISA
(O) 100VGPATCHES 100VGAnyLAN/9000 EISA Patches
(R) ORACLE Oracle 7.2.3
NOTE:ORACLE only
(R) ORACLE Patch BUG338507

(R) ORACLEDEV2000 Oracle Develop 2000
NOTE:ORACLE_DEV2000 only
(R) ORACLESRODDBO Oracle SRO DDBO 7.2.3

NOTE:ORACLESRODDBO only

NOTE:WorldView only

(R) Expect 5.31
(R) Ignite UX 10.20 V2.4.307
^
|
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 73 / 318
318
This is the list of parameters:
HPUX disk : disk

APPLI disk : disk

Hostname : WS_hostname

Ip address : IP_address
Gateway : Gateway
Netmask : Netmask
Type of Ws : WS_type
Keyboard : keyboard
Please confirm to start the installation (y|n|q) ? : y ,and press [Enter]
After you answer the procedure checks the effective disk size, formatting all the assigned disks.
=>Date and Time

=>The selected disk are going to be initialized, please wait ...
=>Date and Time

=>Creating /dev/vg00 volume group on c0t5d0 c0t6d0 ...
Increased the number of physical extents per physical volume to 1023.
Volume group /dev/vg00 has been successfully created.
Volume Group configuration for /dev/vg00 has been saved in

/etc/lvmconf/vg00.conf
...
After loading the system software the machine reboots automatically.
If the system fails the reboot, please verify the boot path and retry.
N.B. Dont care if, during the installation, the system shows you messages like these:
/usr/lib/dld.sl: text file busyump
/sbin/rc[38]: 15241 Abort (CoreDump)
unable to add all swap for device file: /dev/vg00/lov9

increase the tunable parameter maxswapchunks by 850 and
reconfigure system.rt syncer daemon
or:
run cmd: process [85] killing by signal 9.
error: could not execute net_cfg_prep
or:
An error occoured: for more information see the rc.log file.
If the message in rc.log file, is the follow error related to the ovtrapd process:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 74 / 318
318
Starting OpenView
Output from /sbin/rc3.d/S940ov500 start:

Network management daemons started: object manager name: ovtrapd
state: FAILED
PID: 19031
last message: ovtrapd: Cannot open SNMP Trap port, UDP 162.
The port is already in use by another application. Look in
inetd.conf to determine if another process is automatically binding
to this UDP port. Also determine if an application that binds
directly to the SNMP trap port is already installed and running on
the system.
exit status:
If you have requested the software contained in the second CDROM, the installation script will ask you
to insert the second CD (C742C17D_TSD 2/2 for presentation and C842C17D_TSD 2/2 for server) to
finish the installation.
The validity of the installation must be now verified; go on with paragraph 4.4 Check the validity of the
Installation.
4.4 Check the validity of the HPUX 10.20 installation
Wait the HP CDE login screen, then login the system as user root with password install10.
If at the login the system shows you the following message:
ALCATEL BOOTMEDIUM C742C17d_TSD (<date and time>)
station type : RMM

********** THIS WORKSTATION IS NOT CORRECTLY INSTALLED ****************
To fix the problem, check the log file in /AXINSTALL/axinstall.log
***********************************************************************
Value of TERM has been set to vt200.
WARNING: YOU ARE SUPERUSER !!
It means that the machine is not correctly installed.
Look at the file /AXINSTALL/axinstall.log that contains the log of the installation. Try to identify the cause
of the failure reading the log file and, if is possible, remove the problem. Start again the installation looking
in the /AXINSTALL/axinstall.in_progress file, that contains the identity of the failed package as comment
in the first line of the file.
Refer to the paragraph 14.3 to restart properly the installation.
Before starting the system configuration stage, it is mandatory to load the system and
applicative software on all the WS (chapter 4.2 or 4.3).
1AA 00014 0004 (9007) A4 ALICE 04.10
If you need, for any reason, to power off the machine, please refer to APPENDIX B before proceed.
ED 02
957.130.892 W 3AL 61261 AA AA 75 / 318
318
4.5 Manual Installation of HPUX 11.00
This section describes how to install and customize the HPUX 11.00 on the HP 9000 system, in order
to allow the correct execution of the Alcatel Network Management application within NR5 environment.

4.5.1 HPUX 11.00 installation and configuration
The HPUX installation have to be performed using the following HPUX 11.00 CDROM distribution
medium:
HPUX 11.00 Core OS Install/Update/Recovery Part No. B378210475
N.B. The references to the device (path, size, model) are provided as examples, they can change
depending by the hardware configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 76 / 318
318
4.5.1.1 Step 1
Insert the medium in the CDROM driver and power on the HP 9000.
If your system is active, reboot the system.

The system automatically starts up, issuing some messages. Wait until the following message appears
on the screen:

This is an example for the 32bit series workstation:

This is an example for the 64bit series server:

This is an example of another modality to display the devices for the 64bit series server:

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. Usually youll find the CD hardware path written close to the CD or DVD driver, or on the internal
side of the front door of the K server.
ED 02
957.130.892 W 3AL 61261 AA AA 77 / 318
318
4.5.1.2 Step 2
When the LED of CDROM device stops blinking, boot by entering:


where n is the value corresponding the CDROM.
Interact with IPL (Y or N?) > n , and press [Enter]
The workstation boots from the CDROM device, issuing some messages like:
HARD Booted
ISL Revision A.00.38 OCT 26, 1994
ISL booting hpux (;0): INSTALL
Boot
: disk (.....
N.B. Please ignore the following warning message:

WARNING: No dump device configured. Dump is disabled
4.5.1.3 Step 3
The first window shown is the presentation:
Welcome to the HPUX installation/recovery process!

Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return> or <spacebar> to popup a choices list. If the
menus are not clear, select the Help item for more information.
Hardware Summary: System Model: 9000/800/L1000|6

++++[Scan Again ]
| Disks: 6 ( 50.9GB) | Floppies: 0 | LAN cards: 1 |
| CD/DVDs: 1 | Tapes: 0 | Memory: 512Mb |
| Graphics Ports: 0 | IO Buses: 6 | CPUs: 2 |[H/W Details]
++++
[ Install HPUX ]
[ Reboot ] [ Help ]
Figure 27. HPUX 11.00 Installation Presentation Window
Using [Tab] key or arrow keys select [ Install HPUX ] and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 78 / 318
318
4.5.1.4 Step 4
The next window shown the installation modalities:

User Interface and Media Option

This screen lets you pick from options that will determine if an
IgniteUX server is used, and your user interface preference.
Source Location Options:

[ * ] Media only installation
[ ] Media with Network enabled (allows use of SD depots)
[ ] IgniteUX server based installation
User Interface Options:

[ * ] Guided Installation (racommended for basic installs)
[ ] Advanced Installation (racommended for disk and filesystem mng.)
[ ] No user interface use all the defaults an go
Hint: If you need to make LVM size changes, or want to set the
final networking parameters during the install, you will
need to use the Advanced mode (or remote graphical interface).
[ OK ] [ Cancel ] [ Help ]
Figure 28. HPUX 11.00 Installation: User Interface and Media Option Window
Using [Tab] key or arrow keys select Advanced Installaation ... and press [Enter] to mark this
option, then using [Tab] key select [ OK ] to proceed with the installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 79 / 318
318
4.5.1.5 Step 5
The displayed window shown some folders, with Basic Choices one selected.

+ /opt/ignite/bin/itool () +

| |
| ++++++++++ |
| | Basic || Software || System || File System || Advanced | |
| | \+|
| | ||
| | Configurations:[ HPUX B.11.00 Default >] [ Description... ] ||
| | ||
| | Environments:[ 64Bit CDE HPUX Environme >] (HPUX B.11.00) ||
| | ||
| | [ Root Disk...] SEAGATE_ST|9204LC, 0/0/1/1.2.0, 868| MB ||
| | ||
| | File System: [ Logical Volume Manager (LVM) with VxFS >] ||
| | ||
| | [ Root Swap (MB)... ] 1024 Physical Memory (RAM) = 512 MB ||
| | ||
| | [ Languages... ] English [ Keyboards... ] [ Additional... ]||
| | ||
| ++|
| [ Show Summary... ] [ Reset Configuration ] |
||
| [ Go! ] [ Cancel ] [ Help ] |
+
Figure 29. HPUX 11.00 Installation: Basic Choices Window
If you are installing a B1000, B2000,R3xxx or K3xxx, you have to select, using [Tab] key or arrow keys,
on the menu Environments, the choice [ 64Bit CDE HPUX Environme >].
Using [Tab] key or arrow keys select [ Languages... ] and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 80 / 318
318
4.5.1.6 Step 6
This window allow to choose the languages that have to be installed. You have to choose the default
language, and mark the languages you want to install. The installation done with bootable medium
includes all the European languages and defines English as default.

| |
| ++++++++++ |
| | Basic + Languages + |
| | | |+|
| | | Marked ? Language | ||
| | Config| ++ | ] ||
| | | | No Chinese_Simplified ^ | ||
| | Enviro| | No Chinese_Traditional | ||
| | | | Yes English | ||
| | [ Root| | No European v | ||
| | | ++ | ||
| | File S| | ||
| | | [ Default Language:... ] English (optional)| ||
| | [ Root| | ||
| | | Code Set: SET_NULL_LOCALE | ||
| | [ Lan| |nal... ]||
| | || ||
| +| [ OK ] [ Cancel ] [ Help ] |+|
| [ S++ation ] |
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 30. HPUX 11.00 Installation: Language Selection Window
Get on the language list by pressing [Tab]. Move in with arrow keys, and select the languages by pressing
[Space Bar].
To select the default language: get on [ Default Language:... ] press [Enter] move on the list with
arrow keys and select by pressing [Enter].
When the selection have been completed, get on to [ OK ] and press [Enter] to go back on the Basic
Choices Window (shown at page 80).
If you are installing a HP 9000 workstation (B/C Class systems) you have to select [Keyboards... ]
and press [Enter] to get to 4.5.1.7 and define the keyboard, otherwise if you are installing a HP 9000 Server
(R/L/K/N Class systems) you have to skip the 4.5.1.7 and select [ Additional... ] and press [Enter]
to get to 4.5.1.8.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 81 / 318
318
4.5.1.7 Step 7
N.B. This step is useful only on HP 9000 Workstation

This window allows to select the keyboard. You have to set it in agreement with the keyboard equipped

on the workstation.
| |
| ++++++++++ |
| | \+|
| | ||
| | Configuratio+ Language Specific Keyboards +on... ] ||
| | | | ||
| | Environments| Keyboards: |11.00) ||
| | | ++| ||
| | [ Root Disk.| | Not_Applicable ^| ||
| | | | PS2_DIN_Arabic | ||
| | File System:| | PS2_DIN_Belgian v|>] ||
| | | ++| ||
| | [ Root Swap ||B ||
| | | [ OK ] [ Cancel ] [ Help ] | ||
| | [ Languages++dditional... ]||
| | ||
|+|
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 31. HPUX 11.00 Installation: Keyboard Selection Window
Choose the keyboard moving on the list with arrow keys, when the right keyboard will be selected press
[Tab] to select [ OK ] and press [Enter].
The Basic Choices Window will be shown again. You have to select [ Additional... ] to proceed
with 4.5.1.8.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 82 / 318
318
4.5.1.8 Step 8
Additional configuration Control window allow to disable the DHCP daemon, that is not useful.
+ + Additional Configuration Controls + +

| |++| |
| +|| ^| |
| | Ba|| /\ | |
| | || |The miscellaneous controls listed are for two purposes:| |+|
| | || | setting config file variables, and | | ||
| | Co|| | shortcutting complex tasks | | ||
| | || \/ ||
| | En|| Create /export volume [ No >]| ||
| | || | ||
| | [ || Create separate volumes (/usr, /var, ...[ Yes >]| ||
| | || | ||
| | Fi|| [Secondary Swap space (KB).. ] 0 | ||
| | || | ||
| | [ || [ # of disks in root VG... ] 1 | ||
| | || | ||
| | [ || [Force IgniteUX autoboot?.. ] YES |.. ]||
| | || | ||
| +|| [ Disable DHCP?... ] NO |+|
| || v|n ] |
||++||
| [ G||lp ] |
+| [ OK ] [ Cancel ] [ Help ] |+
++
Figure 32. HPUX 11.00 Installation: Additional configuration Control window
Using [Tab] select [ Disable DHCP?... ], press [Enter] , move to YES and press [Enter] to choose.
Then select [ OK ] and press [Enter] to go back to Basic Choices Window (shown at page 80).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 83 / 318
318
4.5.1.9 Strep 9
Change form Basic Choices Window (shown at page 80) currently shown, on to System Choices Window
by moving the cursor with on System and press [Enter]. The following window will be displayed on the

screen.

| |
| ++++++++++ |
| +/ \+|
| | ||
| | Final System Parameters: [ Set parameters now >] ||
| | ||
| | ++ ||
| | | Hostname: | ||
| | | | ||
| | |IP Address: Subnet Mask: | ||
| | | | ||
| | | Time: 06:16 Day: 7 Month: [ November >] Year: 2000 | ||
| | ++ ||
| | [ Set Time Zone ( None )... ] [ Network Services... ] ||
| | [ Set Root Password... ] [ Additional Interface(s)...] ||
| | ||
| ++|
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 33. HPUX 11.00 Installation: System Choices Window
Now you have to fill in the fields Hostname, the IP Address and optionally Subnet Mask. Then
change if necessary the time and date.
The next step allow to set the time zone: select [ Set Time Zone ( None )... ] and press [Enter]
to get to 4.5.1.10.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 84 / 318
318
4.5.1.10 Step 10
This window allows to select the appropriate time zone.

| |
| ++++++++++ |
| ++ Set Time Zone ++|
| | | | ||
| | F| | ||
| | | General Locations [ North America or Hawa >] | ||
| | +| | ||
| | || Timezone Definition | ||
| | || ++| ||
| | || | Newfoundland Standard/Daylight NST|:|0NDT ^| ||
| | || | Atlantic Standard/Daylight AST4ADT | ||
| | || | Eastern Standard/Daylight EST5EDT | ||
| | +| | Eastern Standard Only (US: Most of Indiana) EST5 | ||
| | | | Central Standard/Daylight CST6CDT v| ||
| | | ++| ||
| | || ||
| +| [ OK ] [ Cancel ] [ Help ] |+|
| ++n ] |
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 34. HPUX 11.00 Installation: Time Zone Selection Window
With [Tab] select [ North America or Hawa >] and press [Enter]: the list of General
Location will be shown, move the cursor on the right one with the arrows and press [Enter] to confirm
it.
The list of the Timezone will be updated as well. Now move the cursor into the time zone list and choose
the right one with arrow keys. Then press [Tab] to select [ OK ] and press [Enter] to fix your choice.
The HPUX installation will go back to the System Choices Window (shown at page 84).
To get to 4.5.1.11 on the System Choices Window you have to select [ Set Root Password... ]
and press [Enter] .
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 85 / 318
318
4.5.1.11 Step 11
Now set the root password by enter it at password prompt and press [Enter].

..

| ++++++++++ |
| +/ \+|
| | ||
| | Final + Set Root Password + ||
| | | | ||
| | +| |+ ||
| | | Hos| The root account is used for system | | ||
| | | | administration tasks. To insure the | | ||
| | |IP Ad| security of the system, the root account | | ||
| | | | should have a password. | | ||
| | | | |00 | ||
| | +| Password: |+ ||
| | [ Se||] ||
| | [ | [[ OK ]] [ Cancel ] [ Help ] | ||
| | ++ ||
..
..
Figure 35. HPUX 11.00 Installation: Set Root Password Window
The procedure prompt you immediately for verification. Reenter the root password and press [Enter].
..
| ++++++++++ |
| +/ \+|
| | ||
| | Final + Set Root Password + ||
| | + Verify Root Password + ||
| | +| |+ ||
| | | Hos| | | ||
| | | | Reenter the root password for verification | | ||
| | |IP Ad| | | ||
| | | | Password: | | ||
| | | ||00 | ||
| | +| [[ OK ]] [ Cancel ] [ Help ] |+ ||
| | [ Se++] ||
| | [ | [[ OK ]] [ Cancel ] [ Help ] | ||
| | ++ ||
..
Figure 36. HPUX 11.00 Installation: Verify Root Password Window

1AA 00014 0004 (9007) A4 ALICE 04.10
Select [ OK ] to confirm and go back to the System Choices Window (shown at page 84).
ED 02
957.130.892 W 3AL 61261 AA AA 86 / 318
318
4.5.1.12 Step 12
Change now from System Choices Window (shown at page 84) to File System Window:
| |
| ++++++++++ |
| +/ \+|
| | Mount Dir Usage Size(MB) % Used VG Name ||
| | ++ ||
| | | /stand HFS 84 24 vg00 ^ [ Add ] ||
| | | primary SWAP+D 1024 0 vg00 [ Modify ] ||
| | | / VxFS 140 11 vg00 v [ Remove ] ||
| | +< >+ ||
| | ||
| | Usage: [ HFS >] VG Name: [ vg >] Mount Dir: /stand ||
| | ||
| | Size: [ Fixed MB >] 84 Avail: 6004 MB ||
| | ||
| | [ Add/Remove Disks... ] [ Additional Tasks >] ||
| | ||
| ++|
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 37. HPUX 11 Installation: File System Window
With [Tab] select [ Add/Remove Disks... ] and press [Enter]: the list of disks will be shown, move
the cursor on the right one with the arrows.
Now always with the [Tab] select Usage and press [Enter] to open the menu, move the cursor on LVM
using the arrows and press [Enter] to select it.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 87 / 318
318
++ Add/Remove Disks ++
|| ||
|| ++ ||
|| | Addr Usage Vol Grp Disk Size(MB) Descri | ||

|| | ++ [ Modify ]| ||

|| | | 0/0/1/1.2.0 LVM vg00 8680 MB SEAGAT ^ | ||
|| | | 0/0/2/0.2.0 None 8680 MB SEAGAT | ||
|| | | 0/7/0/0.++ 8680 MB SEAGAT | ||
|| | | 0/7/0/0.| LVM | 8680 MB SEAGAT | ||
|| | | 0/4/0/0.| Whole Disk/HFS | 8680 MB SEAGAT v | ||
|| | +< | Whole Disk/VxFS | >+ | ||
|| | | Whole Disk/All Swap | | ||
|| | Usage: [| None |>] | ||
|| | ++ | ||
|| | | ||
|| ++ ||
|| ||
||||
|| [ OK ] [ Cancel ] [ Help ] ||
+++|
Figure 38. HPUX 11 Installation: Add/Remove Disks
With [Tab] select [ Modify ] and press [Enter] to confirm the choice.
N.B. The [ Vol Grp:... ] choice will be shown no the window.
It is now necessary to distinguish between 1354RM IM and 1354RM US:
The 1354RM IM is using the each disk as volume group;

The 1354RM US uses all the disks in the same volume group.
Because of this difference you have to proceed in different manner.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 88 / 318
318
4.5.1.12.1 Configure VG for 1354RM IM
The configuration of volume group for 1354RM depends by the number and by the size of present disks.
You must take into the account also the mirror disk configuration, If it is foreseen you have to reserve 50%
of drive to be able to configure the mirror as well.

The 1354RM IM foreseen the Multiple Volume Group configuration, that means the all the disk you
are adding to the configuration have to be define as a new volume group.
Now you have to define a different volume group for each disk (example: vg01, vg02 and vg03), change
the value shown close to [ Vol Grp:... ] .
|| ||
|| ++ ||
|| | ++ [ Modify ]| ||
|| | | 0/0/1/1.2.0 LVM vg00 8680 MB SEAGAT ^ | ||
|| | | 0/0/2/0.2.0 None 8680 MB SEAGAT | ||
|| | | 0/7/0/0.10.0 None 8680 MB SEAGAT | ||
|| | | 0/7/0/0.12.0 None 8680 MB SEAGAT | ||
|| | | 0/4/0/0.9.0 None 8680 MB SEAGAT v | ||
|| | +< >+ | ||
|| | | ||
|| | Usage: [ LVM >] | ||
|| | | ||
|| | [ Vol Grp:... ] vg01 | ||
|| ++ ||
|| ||
|| ||
||||
|| [ OK ] [ Cancel ] [ Help ] ||
++++
Figure 39. HPUX 11 Installation: Add/Remove Disk for IM
When all the disk foreseen have been assigned to a volume group, mode the cursor on to [ OK ] and
press [Enter] to go back to File System Window to proceed with disk partitioning.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 89 / 318
318
4.5.1.12.2 Configure VG for 1354RM US
The 1354RM US disk configuration foreseen the Single Volume Group configuration. This means
all the disk have to be configured in the volume group vg00.

|| ||
||++ ||
|| | ++ [ Modify ]| ||
|| | | 0/0/1/1.2.0 LVM vg00 8680 MB SEAGAT ^ | ||
|| | | 0/0/2/0.2.0 None 8680 MB SEAGAT | ||
|| | | 0/7/0/0.1|.0 None 8680 MB SEAGAT | ||
|| | | 0/7/0/0.12.0 None 8680 MB SEAGAT | ||
|| | | 0/4/0/0.9.0 None 8680 MB SEAGAT v | ||
|| | +< >+ | ||
|| | | ||
|| | Usage: [ LVM >] | ||
|| | | ||
|| | [ Vol Grp:... ] vg00 | ||
|| ++ ||
|| ||
|| ||
|| ||
|| ||
||||
|| [ OK ] [ Cancel ] [ Help ] ||
++++
Figure 40. HPUX 11 Installation: Add/Remove disk for US
When all the disk foreseen have been assigned to volume group vg00, mode the cursor on to [ OK ] and
press [Enter] to go back to File System Window to proceed with disk partitioning.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 90 / 318
318
4.5.1.13 Step 13
Now you have to change the predefined disk partitions according with the disk partition tables defined
later for both 1354RM IM and US.
The possible actions are modify an existing partition or define a new one.
To modify:
Select the partition on the list by moving the cursor on it and pressing [Space Bar]. Then change the
values show in the items Usage, VG Name and Size. Then move the cursor on [ Modify ]
and press [Enter].
To create a new one:

Select the partition mounted on / and press [Space Bar], then change the same items of modify,
adding Mount directory. When all the items have been changed, move the cursor on [ Add
] and press [Enter].
N.B. Before change Size select Fixed MB.
N.B. All the file system in HPUX 11 are defined as VxFS except /stand (/stand MUST be HFS)
| |
| ++++++++++ |
| +/ \+|
| | Mount Dir Usage Size(MB) % Used VG Name ||
| | ++ ||
| | | /stand HFS 84 24 vg00 ^ [ Add ] ||
| | | primary SWAP+D 1024 0 vg00 [ Modify ] ||
| | | / VxFS 140 11 vg00 v [ Remove ] ||
| | +< >+ ||
| | ||
| | Usage: [ HFS >] VG Name: [ vg >] Mount Dir: /stand ||
| | ||
| | Size: [ Fixed MB >] 84 Avail: 6004 MB ||
| | ||
| | [ Add/Remove Disks... ] [ Additional Tasks >] ||
| | ||
| ++|
||
| [ Go! ] [ Cancel ] [ Help ] |
++
Figure 41. HPUX 11 Installation: File System Window
The file system have to be define according with the following tables: Table 5. for 1354RM IM and
Table 6. for 1354RM US.
When all the file system will be defined select [ Go! ] and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 91 / 318
318
Table 5. HPUX 11.00 1354RM IM Disk Partitioning
A1354RM IM and Spare 9 + 4 Gb 9 + 9 Gb

Disk Partition
root disk data disk root disk data disk
9 Gb (vg00) 4 Gb (vg01) 9 Gb (vg00) 9 Gb (vg01)
/stand 100 (lvol1) 100 (lvol1)
Primary Swap 1600 (lvol2) 1600 (lvol2)
/ 100 (lvol3) 100 (lvol3)
/opt 1200 (lvol4) 1200 (lvol4)
/tmp 100 (lvol5) 100 (lvol5)
/users 52 (lvol6) 52 (lvol6)
/home 600 (lvol7) 600 (lvol7)
/usr 800 (lvol8) 800 (lvol8)
/var 300 (lvol9) 300 (lvol9)
/mirror 1000(lvol10) 1000(lvol10)
/backup 2000(lvol11) 2000(lvol11)
/alcatel 4000 (lvol1) 8000 (lvol1)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 92 / 318
318
A1354RM IM and Spare 9 + 4 +9Gb
Disk Partition
root disk data disk data disk
9 Gb (vg00) 4 Gb (vg01) 9 Gb (vg01)
/stand 100 (lvol1)
/ 100 (lvol3)
/opt 1200 (lvol4)
/tmp 100 (lvol5)
/users 52 (lvol6)
/home 600 (lvol7)
/var 800 (lvol8)
/var 300 (lvol9)
/mirror 3000(lvol10)
A1354RM IM and Spare 9 + 9 +9Gb

Disk Partition
root disk data disk data disk
9 Gb (vg00) 9 Gb (vg01) 9 Gb (vg01)
/stand 100 (lvol1)
/ 100 (lvol3)
/opt 1200 (lvol4)
/tmp 200 (lvol5)
/users 52 (lvol6)
/home 700 (lvol7)
/usr 800 (lvol8)
/var 700 (lvol9)
secondary swap 1000 (lvol1)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 93 / 318
318
Disk Partition
(vg00) (vg02) (vg03) (vg04)

/stand 100 (lvol1)
/ 2800 (lvol4)
/tmp 500 (lvol1)
/var 600 (lvol2)
Table 6. HPUX 11.00 1354RM US Disk Partitioning
A1354RM USM 6Gb 8 Gb 13 Gb 22 Gb 31 Gb

Disk Partition (vg00) (vg00) (vg00) (vg00) (vg00)
/stand 100 (lvol1) 100 (lvol1) 200 (lvol1) 200 (lvol1) 200 (lvol1)
Primary Swap 704 (lvol2) 704 (lvol2) 1408 (lvol2) 1408 (lvol2) 1408 (lvol2)
Secondary Swap 1000 (lvol3) 2200 (lvol3) 3200 (lvol3)
/ 100 (lvol3) 100 (lvol3) 200 (lvol4) 200 (lvol4) 200 (lvol4)
/opt 1200 (lvol4) 1200 (lvol4) 2000 (lvol5) 2000 (lvol5) 2000 (lvol5)
/tmp 100 (lvol5) 100 (lvol5) 500 (lvol6) 500 (lvol6) 500 (lvol6)
/users 52 (lvol6) 52 (lvol6) 200 (lvol7) 200 (lvol7) 200 (lvol7)
/home 600 (lvol7) 1200 (lvol7) 2400 (lvol8) 4800 (lvol8) 9600 (lvol8)
/usr 600 (lvol8) 600 (lvol8) 1200 (lvol9) 1200 (lvol9) 1200 (lvol9)
/var 300 (lvol9) 300 (lvol9) 600 (lvol10) 600 (lvol10) 600 (lvol10)
/alcatel 2044 3044 3000 8000 10000

(lvol10) (lvol10) (lvol11) (lvol11) (lvol11)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 94 / 318
318
4.5.1.14 Step 14
If the HPUX installation tool does not identify errors, a window like the following will be shown.
If a warning message like the shown one will be issued by the installation tool, the means is you are using
a disk already used for other purpose before, and the contents of if will be lost.
If no other error are shown goto [ Go! ] and press [Enter], otherwise review you data entry by choosing
[ Cancel ] and pressing [Enter].
++ itool Confirmation ++
|| ||
|| All data will be destroyed on the following disks: ||
|| ||
|| Addr Disk Size(MB) Description ||
|| ++ ||
|| | 0/0/1/1.2.0 868| MB SEAGATE_ST|9204LC ^ ||
|| | ||
|| | v ||
|| +< >+ ||
|| ||
|| The results of the preinstall analysis are: ||
|| ||
|| ++ ||
|| | WARNING: The disk at: 0/0/1/1.2.0 (SEAGATE_ST|9204LC) ^ ||
|| | appears to contain a file system and boot area. Continuing ||
|| | the installation will destroy any existing data on this ||
|| | disk. ||
|| | ||
|| | v ||
|| ++ ||
||||
+| [ Go! ] [ Cancel ] [ Help ] |+
++
Figure 42. HPUX 11 Installation. Confirmation window
Then the HPUX 11.00 Installation tool will install all the components selected and configure the disks as
well.
At the end it will reboot the system.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 95 / 318
318
4.5.2 HPUX 11.00 Manual Installation Post Reboot
4.5.2.1 HPUX 11 on server R class

Installing HPUX 11.00 on Server R3xx with additional LAN cards a wrong behavior have been observed.

During the first reboot the system is not able to configure the LAN cards as well.
There is the following workaround to fix this mulfuncion:
a) Login as root.
b) Remove the following files: /etc/ioconfig and /stand/ioconfig by entering:
# rm /etc/ioconfig ,and press [Enter]

# rm /stand/ioconfig ,and press [Enter]
c) Reboot the system.
# reboot ,and press [Enter]
d) When the system will be rebooted, it will stop because of the file removed. You have to create the
files again by entering:
# /sbin/ioinit c ,and press [Enter]

# /sbin/ioinit i ,and press [Enter]
# /sbin/insf e ,and press [Enter]
The proceed by enter [Ctrl] and [d].
4.5.2.2 HPUX 11 Patch PHSS_20140
In order to allow the foreseen behavior of the HP tool talk, the HP Patch PHSS_20140, automatically
installed by HPUX 11.00 have to be removed, by enter the command:
# swremove PHSS_20140 ,and press [Enter]
4.5.2.3 HPUX 11 Patch Saved File Removal
In order to allow the PHSS_20140 removal all the files saved by the patch installation have been kept on
to the system. It is now possible to remove them by enter the following commands:
# cd /var/adm/sw/save ,and press [Enter]

# ls ,and press [Enter]
Just to check the default directory contains only PHx_<num> directories. Then remove all of them by enter:
# rm Rf * ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 96 / 318
318
4.5.3 Retrieve Installation Procedure
To reduce the risk of error installation of the ALMAP HP4.2 software a script is provided to automatically
perform these activities.
This section shows how to retrieve this script from the bootable medium.
4.5.3.1 Find the CDRom
Login as root.
Use the ioscan command to find the cdrom device file:
# ioscan fn C disk ,and press [Enter]
Example of ioscan command output:

=======================================================================
disk 0 8/0/19/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST34572WS
disk 1 8/0/19/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST32171W
disk 2 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CDROM ...
4.5.3.2 For the 32bit systems
To perform the download of the block one, insert the bootable C342C20E_TSD CDROM 1/2 in the driver

# cpio id < /SD_CDROM/C342C20e_TSDBLOCK01 ,and press [Enter]
4.5.3.3 For the 64bit systems
To perform the download of the block one, insert the bootable C642C20E_TSD CDROM 1/2 in the driver
and executing the command described below.

# cpio id < /SD_CDROM/C642C20e_TSDBLOCK01 ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 97 / 318
318
4.5.4 Installation for Alcatel ALMAP HP4.2 Platform
N.B. Due the number of reboot that the installation procedure requires it can take 2 hours or more
(depending on the hardware).

To start the installation execute the following commands:

# etc/install10 required ,and press [Enter]
For the series 32bit:
Workstation Type:

NNM = A1354NN 5.0 Information Manager (Master)
NNP = A1354NN 5.0 User Services (Presentation)
NNS = A1354NN 5.0 Information Manager (Spare)
RMM = A1354RM 5.x Information Manager (Master)
RMP = A1354RM 5.x User Sevice Manager (Presentation)
RMS = A1354RM 5.x Information Manager (Slave)
RMSH3M = A1354RM 5.x / A1353SH 5.3 Master Workstation
RMSH3P = A1354RM 5.x / A1353SH 5.3 User Sevice Manager (Presentation)
RMSH3S = A1354RM 5.x / A1353SH 5.3 Spare Workstation
Enter WS type (CST NNM NNP NNS QAM RMM RMP RMS RMSH3M RMSH3P RMSH3S
SH3E SH3M SH3P SH3S VPNM VPNS) : <WS_type> ,and press [Enter]
You have to respect the choice made during the disk partition allocation, because each one may
have different requirements in term of disk and RAM capacity, or configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 98 / 318
318

Workstation Type :

According to the type of station some optional softwares are proposed to be loaded or not. For more
explanations please refer to the next paragraph 4.5.5 Optional software allocations.

MC/Service Guard 11.09 (y|n|q) ? :
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 99 / 318
318
4.5.5 Optional Softwares allocation
Some softwares, corresponding to certain functionalities, are optional according to the type of machines.
The following table gives the permitted configurations:

Functionality Software RMM/RMS RMP
100BaseT Lan Driver (1 ) opt no
100VGAny Lan Lan Driver (2 ) opt no
XTerminal ENWARE 7 (3 ) opt opt
XTerminal ENWARE 8/9 (3 ) opt opt
Disk Mirror HPUXMIRROR (4 ) opt opt
High Availability MC/Service Guard (5 ) no no
OTS9000 Full OSI Stack (6 ) opt no
Figure 43. Optional 3rd part softwares
1) The 100BaseT software has to be installed only when a 100BaseT card is present in the system
configuration. It is useful on all the systems with more then one LAN cards except HP9000
C100/C110 workstations.
2) The 100VgAnyLan software has to be installed only when a 100VGAnyLan card is present
in the system configuration.
3) ENWARE 7 is for Xterminal ENTRIA and ENVIZEX, ENWARE 8 is for ENTRIA 2 and ENVIZEX
2. If ENTRIA or ENVIZEX plus ENTRIA 2 or ENVIZEX 2 must be connected, both versions of
ENWARE must be installed.
4) The MIRROR software has to be installed only if the mirror disk configuration is planned on your
system. Remember that the disk mirror configuration is supported only on the HP Server 800
series (see Chapter 12 at page 249).
5) The High Availability MC/Service Guard software have to be installed only with OSCluster
configuration.
6) The OTS 9000 full stack is requested when there are any A1353WX system in the SDH
configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 100 / 318
318
4.5.6 Confirm
Example of RMM installation:

This is the list of software packages:

(O) HPUXMIRROR MirrorDisk/UX
(R) XSW700GR1020 B.10.20. XR41 Extension Software Patch Bundle
(R) HPPATCHES Extension Software Patch Bundle + Others Patches
(R) ALCATELSYSCONF Alcatel System Configuration Scripts
(R) JAVA development Kit and SWING for s700 11.00
(R) Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0
(R) ORACLE RDBMS 7.2.3 and Developer 2000 (IM)
NOTE:ORACLE_RDBMS only
(O) ENWARE7 for ENTRIA/ ENVIZEX Xterminals

(O) ENWARE9 for ENTRIA II/ENVIZEX II Xterminals
NOTE:WorldView only
(O) OTS9000FULL HP OSI Transport and Services Full for HP 9000

(O) OTS9000FULLPATCHES HP OSI Full Patches
(R) Expect 5.31
(R) Ignite UX 10.20 V1.59
(O) MC/Service Guard 11.09
(O) DM5.03 SG Support patch
^
|
After the confirm, the system start the installation of the selected softwares. This operation take some
minutes.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 101 / 318
318
4.5.7 Loading
Loading of disks is automatically launched.

=>date and time

=>Creating physical volume on ...
....
...
Physical volume has been successfully created.

End : date and time
Ignore Warning Messages if there is
..................................................
After loading the system software the station reboots automatically.

Wait the HP CDE login screen. Log as user root with password install10.
4.5.8 Post installation step
Now you have to copy the bootape_version and HPUX Kernel description (*.system) file in the
/usr/local/data directory and to create the wstype file:

..,sys,root # cp /tmp/bootape_version . ,and press [Enter]
The next operations depend of the machine type:
a) only for IM machine:
..,sys,root # echo RMM > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMM.system . ,and press [Enter]
b) only for USM workstation:
..,sys,root # echo RMP > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMP.system . ,and press [Enter]
c) only for Spare workstation:
..,sys,root # echo RMS > wstype ,and press [Enter]

..,sys,root # cp /tmp/etc/RMS.system . ,and press [Enter]
The validity of the installation must be now verified; go on with chapter 4.4 Check the validity of the
Installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 102 / 318
318
4.6 Installing HPUX 11.00 from Bootable Medium
This chapter describes how to manage with the bootable media interface with the different configurations
that it allows.
After the boot to launched from the CDROM device, the process will have completely installed on the hard
disk the system part of the software.
4.6.1 Boot the machine
Power on the HP 9000 system. If your system is active, simply power off and power on it again.
on the screen:

You have to identify the medium driver that you want to use in the provided device list.
This is an example for the series 32bit:

This is an example for the series 64bit:

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 103 / 318
318
This is an example of another modality to display the devices for the 64bit series server:


Insert the bootable CDROM 1/2 for your machine type (series 32bit or series 64bit) into the CDROM
driver.
Main Menu: Enter command or menu > boot P<n> ,and press [Enter]
Interact with IPL (Y or N) > n ,and press [Enter]
Booting...
ISL Revision A.00.29 July 17, 1993
...
The script of installation allows to :
Keyboard selection (only for Workstation)

Date&Time
Application selection (the workstation type)
Disk configuration (system partitions)
Network informations (hostname , IP address)
Optional Softwares selection
Source Media selection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 104 / 318
318
4.6.2 Keyboard selection
Meaningful for Servers only.

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

Enter y if you agree, or n to select another one (y|n|q):
Enter y if the keyboard is right, otherwise enter n and the system prompts you:


Please confirm your choice by pressing RETURN or enter a new number :
[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 105 / 318
318
4.6.3 Set up the Date
The current timestamp is shown to allow to check it and set up if needed the right date and time:


If the timestamp is wrong, enter: n, then press [Enter]. The procedure issues the following message
requesting the new date and time:
Enter the new date (mmddhhmm[yy]) :
where: mm means month between 1 and 12

The new date MUST be provided adding or subtracting at the local current time the number of
hours your time is offset from Greenwich Mean Time (GMT) at zero degrees longitude.
The system asks again:

Press y to confirm and proceed or n to change again the date.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 106 / 318
318
4.6.4 Application Selection
Now the procedure shows you the list of the supported application platforms that it is able to prepare. You
have to choose which application and which configuration of it you want to install, typing the associate
name at the procedure request:

Workstation Type :

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 107 / 318
318

Workstation Type :

Depending by the application and configuration the disk management can be different.
4.6.5 Disk configuration
The disk configuration depends by the application requirements. The disk configuration can be done using
a single volume group to include all disks or a different volume group for each physical volume, because
of these capabilities here you can find an example for each set of request issued by the installation
procedure.
N.B. In any case you must satisfy the disk requirements show in Table 4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 108 / 318
318
4.6.6 RM Installation
The system retrieves the list of the hard disks in configuration, checks if the required amount of disk space
is available, and configure the disk as well for the selected application.
The following example contains disk size and disk path for the RMM installation:
Hardware detection in progress, please wait ...
The install script detects the disks configuration of the machine. Example :


Total: 13080 MB
Boot disk : c0t6d0 selected 4194 MB
The procedure shows you the hard disk found in the system configuration, with the related size. Then asks
you to select the disk configuration. Example:
Select the disk configuration for RMM installation

1 4096000 (c0t6d0) 2048000 (c0t5d0)
2 4096000 (c0t6d0) 4096000 (c0t5d0)
3 8192000 (c0t5d0) (same as root disk)
4 8880000 (c0t5d0) 4096000 (c0t6d0)
Enter the disk configuration number, ? to look of other configuration

or press return to abort: <Number_configuration> ,and press [Enter]
Now the system asks you the confirm. Example:
The selected configuration for RMM is

8880000 (c0t5d0) 4096000 (c0t6d0)
Do you confirm the disk configuration? (y|n|q) ? y ,and press [Enter]
At this step if your choice is wrong and you type n, the system gives you the # prompt, then type
etc/autoexec to restart the configuration script .
All the disk assigned to the application will be format again. The contents of those disks
will be lost!.
N.B. The install script allows to do particular configurations for specific needs, that requires flexible
installation procedure. For an installation on customer site perform a standard
installation, that means answer yes to the default proposals to have an optimized usage
of the machine in term of security and performance. Only this option is described here.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 109 / 318
318
4.6.7 Network Information
The next install step allows you to define the Network Information.

The hostname is free, it can be dictated by the customer, but must have not more than 8 characters, the

lower case is raccomanded, and the first one must be an alphabetic character, is not allowed to use the
special characters (i. e. and _ ).
The suggested names are :
axrmm for the IM RM WS

axrmp# for the US RM WS number #
The IP_Address is free, it can be dictated by the customer, but must have the xxx.xxx.xxx.xxx format.
N.B. A different address is assigned for each WS and must be unique in the network.
Network information:
Enter the Hostname : <WS_hostname> ,and press [Enter]
Enter the IP addr. : <IP_address> ,and press [Enter]
Now the system asks if you want to set a default gateway:
Would you like to set a default gateway (y/n/q)? [y] : ,and press [Enter]
If you want to set it, press y and remember that the default gateway must be your default router:
Enter Router IP address [151.98.8.254] : <Router_IP_Address> ,and press [Enter]
Enter the Netmask[] : <Netmask> ,and press [Enter]

or press <RETURN> to use default netmask : <Default_netmask> ,and press [Enter]
4.6.8 Optional Softwares selection
The system asks you which software you want to install. Example of RMM installation:
N.B. According to the type of machine some optional softwares are proposed to be loaded or not.
For more explanations please refer to the paragraph 4.2.6 Optional software
allocations.
Optional Software Selection:
Would you like to install:

ENWARE7 for ENTRIA/ ENVIZEX Xterminals (y|n|q) ? :
ENWARE9 for ENTRIA II/ENVIZEX II Xterminals (y|n|q) ? :
MC/Service Guard 11.09 (y|n|q) ? :
OTS9000FULL HP OSI Transport and Services Full for HP 9000 (y|n|q) ?
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 110 / 318
318
4.6.9 Source media selection
Now the system asks you the media that you want to use:
For the 32bit systems:

Please enter the device file of source media [/dev/dsk/clt2d0]: press [Enter]
For the 64bit systems:
Please enter the device file of source media [cxtxdx]: ,and press [Enter]
You have taked note of the sescsi value before. The boot path SESCSI.2.0 or 8/16/5.2 corresponding
to the c1t2d0.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 111 / 318
318
4.6.10 Confirm
The system asks you the confirm of the software packages selected. Example of RMM installation:


(O) HPUXMIRROR MirrorDisk/UX
(R) XSW700GR1020 B.10.20. XR41 Extension Software Patch Bundle
(R) HPPATCHES Extension Software Patch Bundle + Others Patches
(R) ALCATELSYSCONF Alcatel System Configuration Scripts
(R) JAVA development Kit and SWING for s700 11.00
(R) Apache 1.3.11 HTTPD and TOMCAT Plugin 3.0
(R) ORACLE RDBMS 7.2.3 and Developer 2000 (IM)
NOTE:ORACLE_RDBMS only
(O) ENWARE7 for ENTRIA/ ENVIZEX Xterminals

(O) ENWARE9 for ENTRIA II/ENVIZEX II Xterminals
NOTE:WorldView only

(O) OTS9000FULLPATCHES HP OSI Full Patches
(R) Expect 5.31
(R) Ignite UX 11.00 V2.2.160
(O) MC/Service Guard 11.09
(O) DM5.03 SG Support patch
^
|
This is the list of parameters:
HPUX disk : disk

APPLI disk : disk
Hostname : WS_hostname
Ip address : IP_address
Gateway : Gateway
Netmask : Netmask
1AA 00014 0004 (9007) A4 ALICE 04.10
Type of Ws : WS_type
Keyboard : keyboard
Please confirm to start the installation (y|n|q) ? : y ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 112 / 318
318
After you answer the procedure checks the effective disk size, formatting all the assigned disks.
=>Date and Time

=>The selected disk are going to be initialized, please wait ...
=>Date and Time

=>Creating /dev/vg00 volume group on c0t5d0 c0t6d0 ...
Increased the number of physical extents per physical volume to 1023.
Volume group /dev/vg00 has been successfully created.
Volume Group configuration for /dev/vg00 has been saved in

/etc/lvmconf/vg00.conf
...
After loading the system software the machine reboots automatically.
If the system fails the reboot, please verify the boot path and retry.
N.B. Dont care if, during the installation, the system shows you messages like these:
/usr/lib/dld.sl: text file busyump
/sbin/rc[38]: 15241 Abort (CoreDump)
unable to add all swap for device file: /dev/vg00/lov9

increase the tunable parameter maxswapchunks by 850 and
reconfigure system.rt syncer daemon
run cmd: process [85] killing by signal 9.

error: could not execute net_cfg_prep
(during the HPOV product installation):

WARNING: <nodename>:/: 3 products are not compatible for this
systems
architecture or operating system.
ERROR: <nodename>:/: 7 filesets have a version with a higher
revision
number already installed.
WARNING: <nodename>:/: The software dependencies for 13
products or
filesets cannot be resolved.
* The analysis phase failed for <nodename>:/.
* Analysis had errors.
An error occoured: for more information see the rc.log file.

If the message in rc.log file, is the follow error related to the ovtrapd process:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 113 / 318
318
Starting OpenView
Output from /sbin/rc3.d/S940ov500 start:

Network management daemons started: object manager name: ovtrapd

state: FAILED

PID: 19031
last message: ovtrapd: Cannot open SNMP Trap port, UDP 162.
The port is already in use by another application. Look in
inetd.conf to determine if another process is automatically binding
to this UDP port. Also determine if an application that binds
directly to the SNMP trap port is already installed and running on
the system.
exit status:
If you have requested the software contained in the second CDROM, the installation script will ask you
to insert the second CD (C342C20D_TSD 2/2 for 32bit machines and C642C20E_TSD 2/2 for 64bit
machines) to finish the installation.
The validity of the installation must be now verified; go on with paragraph 4.7 Check the validity of the
Installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 114 / 318
318
4.7 Check the validity of the HPUX 11.00 installation
Wait the HP CDE login screen, then login the system as user root with password install10.
If at the login the system shows you the following message:

ALCATEL BOOTMEDIUM C642C20E_TSD (<date and time>)
station type : RMM

********** THIS WORKSTATION IS NOT CORRECTLY INSTALLED ****************
To fix the problem, check the log file in /AXINSTALL/axinstall.log
***********************************************************************
Value of TERM has been set to vt200.
WARNING: YOU ARE SUPERUSER !!
It means that the machine is not correctly installed.
Look at the file /AXINSTALL/axinstall.log that contains the log of the installation. Try to identify the cause
of the failure reading the log file and, if is possible, remove the problem. Start again the installation looking
in the /AXINSTALL/axinstall.in_progress file, that contains the identity of the failed package as comment
in the first line of the file.
Refer to the paragraph 14.3 to restart properly the installation.
Before starting the system configuration stage, it is mandatory to load the system and applicative
software on all the WS (chapter 4.2 or 4.6).
If you need, for any reason, to power off the machine, please refer to APPENDIX B before proceed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 115 / 318
318
4.8 Post HPUX Steps
4.8.1 Dismount the CDROM

At the end of the installation dismount the CDROM (if mounted):
..,sys,root # umount /SD_CDROM ,and press [Enter]
4.8.2 Keyboard
Meaningful only if you have installed from bootable medium.
The installation assumes the keyboard is QWERTY. If not, the file /etc/kbdlang must be edited after the
initial login, as root user.
By default, the file /etc/kbdlang contains the following line :
PS2_DIN_US_English
Modify this file on the machine according to the type of the keyboard:
PS2_DIN_Arabic PS2_DIN_Belgian
PS2_DIN_Bulgarian PS2_DIN_Canada_TBITS3
PS2_DIN_Canadian_French PS2_DIN_Czech
PS2_DIN_Danish PS2_DIN_Euro_Spanish
PS2_DIN_French PS2_DIN_German
PS2_DIN_Greek PS2_DIN_Hebrew
PS2_DIN_Hungarian PS2_DIN_ITF_Danish
PS2_DIN_ITF_Euro_Spanish PS2_DIN_ITF_Finnish
PS2_DIN_ITF_French PS2_DIN_ITF_German
PS2_DIN_ITF_Italian PS2_DIN_ITF_Japanese
PS2_DIN_ITF_Korean PS2_DIN_ITF_Norwegian
PS2_DIN_ITF_Swedish PS2_DIN_ITF_Swiss_French2
PS2_DIN_ITF_Swiss_German PS2_DIN_ITF_T_Chinese
PS2_DIN_ITF_UK_English PS2_DIN_ITF_US_English
PS2_DIN_Italian PS2_DIN_JIS
PS2_DIN_Korean PS2_DIN_Norwegian
PS2_DIN_Polish PS2_DIN_Romanian
PS2_DIN_Russian PS2_DIN_S_Chinese
PS2_DIN_SerboCroatian PS2_DIN_Slovak
PS2_DIN_Swedish PS2_DIN_Swiss_French2
PS2_DIN_Swiss_German2 PS2_DIN_T_Chinese
PS2_DIN_Turkish PS2_DIN_UK_English
PS2_DIN_US_English
The change will be taken into account after a reboot.
4.8.3 Links
Meaningful only if you have installed with bootable medium C842C17D_TSD.

1AA 00014 0004 (9007) A4 ALICE 04.10
After the installation is necessary to create a link executing as root user with the following command:
..,sys,root # ln s /opt/expect/bin/expect /usr/local/bin/expect ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 116 / 318
318
5 BOOTABLE UPGRADE
5.1 Bootable Upgrade

5.1.1 Using Cdrom
The installation procedure is located on the Update CD, to launch it you have simply to mount the SWP
NR50B_PL1 1/2 cdrom and start the procedure by enter the following commands:
..,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM ,and press [Enter]
Where <cdrom device file> is the cdrom device file found in the paragraph 4.2.4.
..,sys,root # cd /SD_CDROM ,and press [Enter]
..,sys,root # ./UpdateNR50BPL1 ,and press [Enter]
The procedure recognizes the operating system and the bootable medium used to install it, starting from
this information proposes the possible updates.
5.1.2 Using distribution tar file
To be able to install the upgrade kit from the distribution gziptar you have to store the file on the system
(the suggested directory in /alcatel) and decompress by enter:
..,sys,root # cd /alcatel ,and press [Enter]
..,sys,root # gzip d UpdBootableNR50BPL1.tar.gz ,and press [Enter]
Then extract the contents of the tar by entering:
..,sys,root # tar xvf UpdBootableNR50BPL1.tar ,and press [Enter]
Now it is possible to run the installation procedure with:
..,sys,root # ./UpdateNR50BPL1 ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 117 / 318
318
5.1.3 Upgrade on HPUX 10.20
This section describes the upgrade on a HPUX 10.20 system. If you are upgrading a HPUX 11.00 sy-
stem skip to paragraph 5.1.4.

On HPUX 10.20 the possible updates are related to ALCATELSYCNFTSD and GoGlobal, so when the
procedure will be started it will issues the following messages:
# =========================================================================
# Procedure to update the Bootable Medium NR5.0B to NR5.0B Patch level 1
#
# The script allow to update the following depots on HPUX 11.00:
# (Bootable C642C20E_TSD and C342C20E_TSD)
# 1. ALCATELSYCNFTSD from V1.7 to V1.8
# 2. Java Run Time form C.01.18.01 to 1.2.2.06.00
# 3. Tomcat from V3.0 to V3.1 (jakarta)
# 4. Apache from V1.3.11 to V1.3.12
# 5. GoGlobal from V1.6.5.x to V1.6.5.3
# The item 1 will be updated by enter yes at question:
# Update ALCATELSYCNFTSD (y|n|q) ? :
# The items 2.,3. and 4. by enter yes at questuion:
# Update JAVA, APACHE and TOMCAT (y|n|q) ? :
# The item 5. by enter yes al question:
# Update GoGlobal (y|n|q) ? :
#
# and on HPUX 10.20:
# (Bootable C842C17D_TSD and C742C17D_TSD)
# =========================================================================
Update ALCATELSYCNFTSD (y|n|q) ? :
Update GoGlobal (y|n|q) ? :
Entering y or yes at the two prompts the procedure will update both components.
The installation will be trace on the console and into the file /AXINSTALL/UpdateNR0BPL1.log, and at the
end the following messages will be shown at login time on any terminal window.
Updated GoGlobalHost for NR5.0B PL1

Updated ALCATELSYCNFTSD for NR5.0B PL1
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 118 / 318
318
5.1.4 Upgrade on HPUX 11.00
On HPUX 11.00 the possible updates are related to ALCATELSYCNFTSD, GoGlobal, Java, Apache
and Tomcat, so when the procedure will be started it will issues the following messages:
# =========================================================================
# Procedure to update the Bootable Medium NR5.0B to NR5.0B Patch level 1
#
# The script allow to update the following depots on HPUX 11.00:
# (Bootable C642C20E_TSD and C342C20E_TSD)
# 2. Java Run Time form C.01.18.01 to 1.2.2.06.00
# 3. Tomcat from V3.0 to V3.1 (jakarta)
# 4. Apache from V1.3.11 to V1.3.12
# The items 2.,3. and 4. by enter yes at questuion:
# Update JAVA, APACHE and TOMCAT (y|n|q) ? :
#
# and on HPUX 10.20:
# (Bootable C842C17D_TSD and C742C17D_TSD)
# =========================================================================
Update ALCATELSYCNFTSD (y|n|q) ? :
Update JAVA, APACHE and TOMCAT (y|n|q) ? :
Update GoGlobal (y|n|q) ? :
Entering y or yes at the prompts the procedure will update related components.
The ALCATELSYCNFTSD and GoGlobal are recommended for all the platforms.
The Java, Apache and Tomcat for the platform where is foreseen 1354RM IM.
The installation will be trace on the console and into the file /AXINSTALL/UpdateNR0BPL1.log, and at the
end the following messages will be shown at login time on any terminal window.

Updated ALCATELSYCNFTSD for NR5.0B PL1
Updated Java, Apache & Tomcat for NR5.0B PL1
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 119 / 318
318
At the new login the system will show you the following message (example):
######################################################################

This is HPUX release B.11.00 for ALMAP HP4.2 TSD Customization
######################################################################
You have mail
ALCATEL BOOTMEDIUM C642C20e_TSD (20Oct00)
Updated ALCATEL_SYSNFTD for NR5.0B PL1
Update Java, Apache & Tomcat for NR5.0B PL1
station type : RMM
5.1.5 Post Installation
5.1.5.1 Umount the CDROM
At the end of the installation dismount the CDROM:
..,sys,root # cd / ,and press [Enter]
5.1.5.2 Configure again Mail
After the installation of the upgrade kit on a not master system (RMP) you have to check the file /etc/fstab.
If it contains a line beginning with:
mailhost:/usr/mail
you have to remove it from the file.
Then you have to dismount the file system /usr/mail if mounted, by entering:
..,sys,root # umount /usr/mail ,and press [Enter]
Then run the command axmailconf v from the master in order to configure again the mail, but using the
directory /var/mail.
..,sys,root # axmailconf v ,and press [Enter]
5.1.5.3 Remove the file
If you have executed the upgrade using gziptar distribution, it is suggested to clean up the temporary files:
..,sys,root # rm UpdBootableNR50PL1.tar ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
..,sys,root # rm UpdateNR50BPL1 UpdateCx42Cxxx_TSD.sd ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 120 / 318
318
6 SYSTEM CONFIGURATION
After loading on every machine, the system needs to be configured. This is done by mean of tool scripts
launched on the Master machine.
The configuration of all the system is done from the Master, so all the systems must be connected and
reachable from the Master before starting. No manual operation is necessary on the remote machine.
N.B. If you have to add or remove a workstation, please refer to the Chapter 11.20.
The following operations must be performed :
Check that all the machines are running.

Log in as root on the master machine (password install10).
WARNING : the inactivity time out temporization is activated. If it happens the screen becomes
locked, you only have to type the password for root (install10) to unlock it.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 121 / 318
318
6.1 Run the initialization script
This script enables to declare all the system as components of a same installation for the TCP/IP
communication (file /etc/hosts within each machine). It is essential that all the machines are connected

on lan0 and HPUX running on them.

In this phase you have only to declare the RM Master, RM spare (if present) and all their Presentations.
6.1.1 On Workstation with graphic interface
For the Workstation with graphic intefrace you have to login as root and enter the following command:
..,sys,root # axinitwsGui ,and press [Enter]
For each station that belong at your network enter the Name, IP address and select the Type, then click
on the Add button.
N.B. Adding the Master will cause a warning , dont take care of it.
Click on Exit button when all the stations have been declared.
If you are using an XTerminal as graphical interface and the system gives you the following error:
Unknown option class font dt interface usermediumrnormalm*********
doesnt exist at /usr/local/lib/perl5/site_perl/Tk/Widget.pm line 180
Please refer to the 14.6 paragraph.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 122 / 318
318
6.1.2 On Workstation without graphic interface
For the Workstation with graphic intefrace you have to login as root and enter a command with the
following syntax for each system that you want to configure:
..,sys,root # axinitws.pl add <hostname> type <system type> ip <ip address> ,and press
[Enter]
Where:
<hostname> means the name of the system
<system type> means the role of the system among: RMM (1354RM Master), RMS (1354RM
Slave), RMP (1354RM Presentation).
<ip address> means the system tcp/ip address in xxx.xxx.xxx.xxx format.
Example:
..,sys,root # axinitws.pl add axrmm type RMM ip 130.1.1.1
..,sys,root # axinitws.pl add axrmp type RMP ip 130.1.1.2
..,sys,root # axinitws.pl add axrms type RMS ip 130.1.1.3
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 123 / 318
318
6.2 Run the kernel configuration script
The first configuration script is the axhpuxconf, it configure the HPUX kernel, allow to define the time
zone and configure the NFS server.

N.B. For HP servers installed with bootable C842C17D_TSD it is necessary to change the
value realted to ncallout from 4100 to 8200 in the file that correspond to your
workstation type:
RMM.system
RMS.system
RMSH3M.system
RMSH3S.system
using the following commands (example for RMM.system):
..,sys,root # cp p RMM.system RMM.system.save ,and press [Enter]
..,sys,root # vi RMM.system ,and press [Enter]
Modify the indicated parameter then save and exit from the file pressing [Esc] and typing
:x! and press [Enter].
The script can be launched only from the 1354RM IM (Master) by the root user entering the following
command:
..,sys,root # axhpuxconf ,and press [Enter]
This script initializes the time zone on the Master machine and configures it as a NFS server.
A serial of menus allows to set Time Zone and date.
On the first level Europe is selected, in the second one you have choose your Time Zone.
*********************************************************
* *
* AXHPUXCONF SCRIPT *
* *
*********************************************************
...
*********************** CAUTION ***********************
Now, the procedure will ask you to enter some parameters.
NEVER ANSWER YES AT THE REBOOT QUESTION.
Press the <Enter> key to continue ,and press [Enter]
Now, the procedure asks you to enter some parameters.
This is an example of GMT0 time zone:
N.B. On the Servers the manmachine interface is not graphical, but the informations that you have
to provide are the same.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 124 / 318
318
Select a location Select a Time
Figure 44. HPUX Set Parameters Time Zone First Selection
First select Europe then click on OK button, then Unlisted Time Zone and click on OK button.
Confirm
Example of unlisted time zone
Figure 45. Set Unlisted Time Zone
Insert the GMT0 time zone and click on OK button, then confirm at the Confirm Time Zone window.
Now, the utility issue the next window to allow you to set the right system time. Usually the time displayed
is wrong, and you have to click on No to get the window that allows you to change the date/time.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 125 / 318
318
Figure 46. Set Data and Time
Where: mm means month between 1 and 12

The window contains the current values of system date/time. To change them, click on the input fields that
you want to modify, delete its contents and type the right one.
When you have changed all the informations that you need, click on OK to activate your modifications.
When you have modify the date, the system asks once again the confirm.
N.B. If the system shows you the following window:
Figure 47. Reboot System Question
Click on No, do not reboot button.
REMEMBER: DO NOT ANWER YES AT THE REBOOT QUESTION !

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 126 / 318
318
Spawning /etc/set_parms timezone...
Spawning /etc/set_parms date_time ...
Starting configuration of nfs...
nfs config complete.
...
kernelconf > Building the new kernel ...

Building a new kernel based on template file /stand/RMM.system
Compiling conf.c...
supported in future releases. The +vallcompatwarnings option can be used to
display more details, and the ld(1) man page contains additional
information. This warning can be suppressed with the +vnocompatwarnings
option.
* The current kernel at /stand/vmunix has been moved
to /stand/vmunix.prev.
* The newly built kernel has been moved to /stand/vmunix.
kernelconf > Moving /stand/system to /stand/system.prev ...
kernelconf > The kernel has been successfully build!.
Terminated
At this time the http daemon server is configured on the Master machine.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 127 / 318
318
6.3 Synchronize the time on all the machines
The axxntpconf configures the xntp protocol to synchronize the time of all the machines defined in the
configuration of 1354RM. The 1354RM IM will provide the time reference for all the 1354RM US.

..,sys,root # xntpd ,and press [Enter]
..,sys,root # axxntpconf ,and press [Enter]
*********************************************************
*
* AXXNTPCONF SCRIPT *
*
*********************************************************
Starting configuration of xntp, please wait ......
xntpd stopped
xntpd
xntp configured with success
If the procedure emit the following message:
ERROR: Unable to stop xnmtp (cannot find PID)

Waiting for xntpd to be up (5 minutes max)
Please wait the end without interrupt it.
It is possible to synchronize the 1354RM IM to an external time source entering the following command
instead of the previous one:
..,sys,root # xntpd ,and press [Enter]

...,sys,root # axxntpconf remote <ip address or hostname> ,and press [Enter]
If there is any 1354NN, it is advisable to set the 1354NN IM as time source for the 1354RM.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 128 / 318
318
6.4 OSI configuration
If there is any NR3.x A1353WX Systems and related 1641SX cross connect in your network, you must
install the HP OSI Transport Services 9000 (OTS) on the A1354RM Master machine, otherwise you have
to skip this step.

In order to allow the correct communication between the A1354RM Master and the A1353WX you MUST
configure the OTS 9000 Full Stack on A1354RM Master.
N.B. It is NOT necessary to install and configure the OTS 9000 Full Stack on A1354RM Presentation.
If you are working on HPUX 10.20, before configure OTS 9000 you MUST set the LAN Card that you
devote to be used for OSI communications as IEEE802.3/Ethernet.
If you are working on HPUX 11.00 skip next parafraph and get to the paragraph 6.4.2 at page 132.
If there is any A1353WX and related 1641SX cross connect in your network, you must install the HP OSI
Transport Services 9000 (OTS) on the A1354RM Master machine, otherwise you have to skip this step.
In order to allow the correct communication between the A1354RM Master and the A1353WX you MUST
configure the OTS on A1354RM Master.
N.B. It is NOT necessary to install and configure the OTS 9000 on A1354RM Presentation.
Before configure OTS 9000 you MUST set the LAN Card that you devote to be used for OSI
communications as IEEE802.3/Ethernet. To do this follow these steps:
6.4.1 LAN Configuration
Meaningful during an HPUX 10.20 environment installation only.
The new kernel just created at axhpuxconf step can prevent to access the LAN description.
To be able to proceed it is necessary to fix the current kernel parameters executing a reboot of the system:
When the system will be available again login as root and start SAM:
..,sys,root # sam ,and press [Enter]
Select and open Networking and Communications with a double click of the mouse:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 129 / 318
318
Figure 48. SAM Areas
Select and open Network Interface Cards with a double click of the mouse:
Figure 49. SAM Areas: Networking and Communication
With the mouse select the LAN interface that you plant to use for OSI communications, then select
Actions and Configure:
N.B. If more lan cards are installed, will be displaied in sequence and for the configuration of them
is necessary to repeat the actions previously indicated.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 130 / 318
318
Figure 50. Networking and Communications
N.B. The example show how to configure the LAN card known as lan0 only.
Figure 51. Configure LAN Card
With the mouse select CARD TYPE and choose IEEE802.3/Ethernet. Then click on OK.
At the next window click on OK: SAM close the Configure LAN Card window.
Select File and then Exit on the Networking and Communication window to leave this section.
Select File, then Exit SAM on SAM Areas: Networking and Communication window to exit SAM and
continue the installation procedure.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 131 / 318
318
6.4.2 OTS Configuration
Start the Osiadmin with the following command:

For 700 Series Workstation or 32bit systems:

..,sys,root # hpterm e /opt/ots/bin/osiadmin ,and press [Enter]
For 800 Series Server or 64bit systems:

..,sys,root # /opt/ots/bin/osiadmin ,and press [Enter]
STEP1: The system shows you the Osiadmin Main Menu :
===========================================================================
C.06.00 Osiadmin Main Menu
To configure, start, verify or stop a layer; tab to the layer and then
press Return or Select Item.
X.25 >
LAN >
OTS >
FTAM >
X.400 >
===========================================================================
With the arrow keys select OTS > and press [Enter].
STEP2: The system shows you the OTS Menu:
===========================================================================
C.06.00 OTS Menu
Highlight an item and then press Return or Select Item.
Configure OTS >
Configure OSI over TCP (RFC1006) >
Start OTS
View Configuration >
Test Connectivity >
Update OTS
===========================================================================
With the arrow keys select Configure OTS > and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 132 / 318
318
STEP3: Now the system shows you the OTS Configuration:
===========================================================================
OTS Configuration
Set Configuration Mode
Before configuring OTS or FTAM you must define the configuration

mode and file set for OSICONF. Press Done to select the default
parameters, otherwise, modify the desired fields and then press Done.
For more information on each choice, highlight the field and press Help.
Update Mode (R=restart/D=dynamic) R
Configuration File Set Path . . /etc/opt/ots/conf
===========================================================================
Now press [F4] (Perform task).
If the system shows you a warning box, press [Space Bar] to continue.
STEP4: Now the system shows you another OTS Configuration window:
===========================================================================
C.06.00 OTS Configuration
Subnetworks:
Configure >
Destination Systems:
Add ...
View/Modify ...
Delete ...
Routes:
Add ...
View/Modify ...
Delete ...
Layers:
Session Parameters ...
Transport Parameters over CLNS ...
Transport Parameters over CONS ...
========================================================================
Select with the arrow keys Subnetworks: and Configure >, then press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 133 / 318
318
STEP5: Now the system shows you another Subnetwork Configuration window:
==========================================================================
C.06.00 Subnetwork Configuration

CLNS over 802.3: Add ...

View/Modify ...
Delete ...
CLNS over FDDI: Add ...

View/Modify ...
Delete ...
CLNS over X.25: Add ... (not installed)

View/Modify ... (not installed)
Delete ... (not installed)
CONS over X.25: Add ... (not installed)

View/Modify ... (not installed)
Delete ... (not installed)
========================================================================
Select with the arrow keys CLNS over 802.3: and Add ... and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 134 / 318
318
STEP6: Now you have to fill the following form:
===========================================================================
C.06.00 Add CLNS over 802.3
Modify the desired fields and then press Perform Task.
Subnetwork name . . . . . . ________________
Network ID . . . . . . . . . ________________________________ (optional)
Local network address (NSAP) ________________________________________
Device interface name . . . ________________________________________
CLNP subset . . . . . . . . 3 0 = Null

1 = NonSegmenting
2 = Full Accept Null
3 = Full Discard Null (NIST compliant)
========================================================================
Fill in the following lines:
Subnetwork name: This value is on your choice.

(suggested value: osi followed by the LAN name)
Network ID: AFI : 2 digit see the note #1
IDI : 4 digit see the note #1
VER : 80
AUTH : 6 digit see the note #2
Reserved : 0000
DOMAIN : 4 digit see the note #2
AREA : 4 digit see the note #2
Local network address (NSAP): AFI : 2 digit see the note #1
IDI : 4 digit see the note #1
VER : 80
AUTH : 6 digit see the note #2
Reserved : 0000
DOMAIN : 4 digit see the note #2
AREA : 4 digit see the note #2
SYSTEM : 12 digit see the note #3
NSEL: 00
example:
AFI IDI VER AUTH Reserved DOMAIN AREA SYSTEM NSEL
39 250F 80 012345 0000 0001 0001 0060B007916C 00
Device interface name: lan0 or lan1 depending to the LAN that you want to use.
NOTE #1 The IDI value depends by the AFI one.

The AFI recommended values are 39 and 47.
If you choose 39 the IDI is a country depending parameter fixed by the ISO DCC 3166.
Examples : France 250F Italy 380F Ireland 372F
1AA 00014 0004 (9007) A4 ALICE 04.10
RSA 710F UK 826F Argentina 032F
If you choose 47 the suggested IDI value is 0005.
ED 02
957.130.892 W 3AL 61261 AA AA 135 / 318
318
NOTE #2 These values have to be define in agreement with the OSI addressing plant.
NOTE #3 The SYSTEM is usually set with the MAC address of the lan card.

N.B. The NSAP address has to be defined in agreement with the OSI addressing plan of customer.

At the end, press [F4], at the message Task completed press the [Space bar].
STEP7: Then press [F8] until the system prompts you the OTS Menu window (if the system prompts you
some other message press the [Space bar]) :
===========================================================================
C.06.00 OTS Menu
Configure OTS >
Start OTS
Test Connectivity >
Update OTS
===========================================================================
Select Start OTS with the arrow keys and then press [Enter]. If the OTS is still running, the system
prompts you a message. Ignore it.
If you dont have a router, press twice [F8] to finish the OTS Configuration. Instead, if you have it follow
the paragraph 6.4.3.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 136 / 318
318
6.4.3 Router Configuration
If you have a router, you need to configure it as follow:

a) Pressing [F8] came back to the menu OTS Configuration (as STEP4) and choose Routes then
Add.
===========================================================================
C.07.00 Add a Route
Fill in or modify the desired fields and then press Perform Task.
Network ID or network address (NSAP) _____________________________________
Subnetwork Name . . . . . . . . . . ________________
Primary route (NSAP) . . . . . . . . _____________________________________
Note: To configure the DEFAULT route, use 0 (a single zero) as the Network
ID.
===========================================================================
Fill in the following lines:
Network ID or network address (NSAP): 0 that identify the default router
Subnetwork name: This is the value that you have given to the Subnetwork name of RM
(suggested value: osi followed by the LAN name)
Primary route (NSAP): is the NSAP of the router .
When you have filled all the lines, press [F4] to perform the task. At the message Task completed
press the [Space Bar].
b) Then press [F8] until the system prompts you the OTS Menu window (if the system prompts you
some other messages press the [Space Bar]):
===========================================================================
C.06.00 OTS Menu
Configure OTS >
Start OTS
Test Connectivity >

1AA 00014 0004 (9007) A4 ALICE 04.10
Update OTS
===========================================================================
ED 02
957.130.892 W 3AL 61261 AA AA 137 / 318
318
Select Start OTS with the arrow keys and then press [Enter]. If the OTS is still running, the system
prompts you a message. Ignore it.
Press twice [F8] to finish the OTS Configuration.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 138 / 318
318
6.5 Run the application OSI stack configuration script
WARNING! This configuration step MUST be performed always, also if there is no OTS 9000 full
stack installed.
Log in again as root on the Master machine (password install10) and execute the command:
..,sys,root # axotsconf v ,and press [Enter]
*******************************************
* AXOTSCONF SCRIPT *
* *
*******************************************
otsconf > updating configuration on tlvhhf
otsconf > Checking if file netconf exists on tlvhhf
otsconf > Loading /etc/rc.config.d/netconf
...
otsconf > Checking if file ots exists on tlvhhf
otsconf > Updating /etc/rc.config.d/ots
otsconf > Cleaning ifor conf
The machines reboot automatically at the end of the script.
About to reboot workstation(s) ... , continue [y|n] ? y ,and press [Enter]
Successively all the machines reboot. After the reboot you have to continue the configuration on the
Master machine.
WARNING: before proceed check all the machines are running again before to continue.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 139 / 318
318
6.6 Configure HPOV for the HPOV communications
Log in again as root on the Master machine (password install10).

a) If OTS 9000 Full Stack is installed on your system, you have to execute the following command:

..,sys,root # $OV_BIN/create_paddr ,and press [Enter]
Check the contents of the $OV_CONF/local_p_addr file:
..,sys,root # more $OV_CONF/local_p_addr ,and press [Enter]
it MUST be in the following form:
ORS_CMIP
OVDM,ses0,tp0,0x540072872203<IP_Address>:1006
OVDM,ses0,tp0,<nsap_address>:CLNS
The first line shows the CI (Communication Infrastructure) Protocol that has to be ORS_CMIP, the
second MUST be the description for RFC 1006 protocol with a line that has at the end the notation:
1006. The third line describes the OSI protocol with a line that has at the end the notation: CLNS.
If the second and the third line are in the opposite order it is MANDATORY to swap them.
b) IN ANY CASE to configure the HP OpenView as requested by the Alcatel Application you have now
to launch the axhpovconf script:
..,sys,root # axhpovconf v ,and press [Enter]
This script clears the old HPOV objects, initializes the new one using the OSI configuration,
configures the machines as Master or Slave and declares the slaves as trusted hosts.
WARNING : reconfiguring the stations using RFC1006

*********************************************************
*
* AXHPOVCONF SCRIPT *
*
*********************************************************
Starting configuration of HP openview, please wait ......
...
ovaddobj Static Registration Utility
hpovconf > updating configuration on tlvhhf
hpovconf > Check if OTS correctly configured on tlvhhf found
...
Successful Completion
...
HPOV configured with success
N.B. If you are installing a HPUX 11.00 environment, please ignore the warning messages
displayed during the axhpovconf script.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 140 / 318
318
6.7 Run the mailer configuration script
If you are installing a HPUX 11.00 environment, it is necessary to modify the

/usr/local/lib/perl5/1353sh/axmailconf.pm changing the line 42:
..,sys,root # vi /usr/local/lib/perl5/1353sh/axmailconf.pm ,and press [Enter]
Type /MAILDIR and modify the following line:
from:
my $MAILDIR = /usr/mail
to:
my $MAILDIR = /var/mail
Save and exit from the file pressing [Esc] and typing :x! and press [Enter].
In any case you have to execute the following commands:
..,sys,root # touch /etc/exports ,and press [Enter]
..,sys,root # axmailconf ,and press [Enter]
*********************************************************
* *
* AXMAILCONF SCRIPT *
* *
*********************************************************
mail configured with success

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 141 / 318
318
6.8 Mail Configuration
To make work correctly the mail, you need to perform the following steps:

a) Save the files:

..,sys,root # cp /etc/mail/sendmail.cf /etc/mail/sendmail.cf.save ,and press [Enter]
..,sys,root # cp /etc/mail/service.switch /etc/mail/service.switch.save ,and press [Enter]
b) Modify the contents of the /etc/mail/service.switch file:
..,sys,root # vi /etc/mail/service.switch ,and press [Enter]
Type [G] and modify the following line:
from:
hosts dns files
to:
hosts files
c) Modify the /etc/mail/sendmail.cf file:
..,sys,root # vi /etc/mail/sendmail.cf ,and press [Enter]
Type /ServiceSwitchFile and delete the comment # from the line below:
from:
#O ServiceSwitchFile=/etc/mail/service.switch
to:
O ServiceSwitchFile=/etc/mail/service.switch
Type /pass to name server and, on the line below, insert the comment #:
from:
#pass to name server to make hostname canonical
R$* < @ $* $~P > $* $: $1 < @ $[ $2 $3 $] > $4
to:
#pass to name server to make hostname canonical
#R$* < @ $* $~P > $* $: $1 < @ $[ $2 $3 $] > $4
d) To make the modifications active, stop and restart the sendmail process with the following command:
..,sys,root # /sbin/rc1.d/K460sendmail stop ,and press [Enter]

..,sys,root # /sbin/rc1.d/K460sendmail start ,and press [Enter]
The system configuration is done.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 142 / 318
318
7 X TERMINAL INSTALLATION
In order to be able to use the xterminals foreseen in the configuration, specially for the 1354RM installed
on HP 9000/800, it is advisable to configure them before proceed with the installation of the application.
7.1 Add an Xterminal station
The Xterminal configuration script must be run on the Master machine, logged as root.
To be able to configure the Xterminal is necessary first to declare the Xterminal via axinitwsGui.
If you dont have already done this step, please refer to the paragraph 6.1 for both machine
series (Servers and Workstations) giving the following informations:
IP address: <IP address of the Xterminal>

Name: <name of the Xterminal>
Type: choose RM Xterminal
N.B. For more information on the syntax of Name and IP address see the paragraph 4.3.7.
N.B. If in your network are present SH IM or/and RM IM, remember to configure the
Xterminal on all the SH IM and RM IM via axinitwsGui, giving the same informations.
Click on Add button to add the Xterminal and then clik on Exit button to quit the axinitwsGui
procedure.
Now you have to execute the axxterminalconf procedure to ask you IP address, hostname, IP
address of gateway (which are data depending of your configuration) and the Mac address
(which depends of your XTerminal
..,sys,root # axxterminalconf ,and press [Enter]
Searching for existing XTerminal and WS supporting ENWARE

software...
hostname Xterminal found on hostname station.
...
ENWARE found on host(s) : hostname1 hostname2 ...
Enter hostname from list above or type . to quit [] :<hostname>
press [Enter]
Executing /usr/bin/X11/700X/xtadm on hostname

Initializing ...
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 143 / 318
318
_________________________________________________
HP NETSTATION ADMINISTRATIVE TASKS
MAIN MENU

1) Add an Netstation

2) Remove an Netstation
3) Printers, plotters
4) Installation testing
5) XDM Administration
6) Manage Software versions
?) Help x) exit
Please enter selection (default=1): 1 ,and press [Enter]
_________________________________________________
ADD AN NETSTATION
To add an Netstation to this computer you will need to obtain the

following information from your local network administrator:
* The name you want to call the Netstation (network hostname).
* The internet protocol (IP) address of the Netstation.
* The LAN hardware (link level) address of the Netstation.

(From the boot screen or shipping carton of the Netstation)
If the network you are adding the Netstation to is connected to other

networks you will also need to know:
* The subnet mask of the Netstation.
* The internet protocol (IP) address of the default gateway.
Continue adding an Netstation [y|n] (y): y ,and press [Enter]
_________________________________________________
ADD AN NETSTATION
Enter name of Netstation to add [q|?] : <XTerminal_hostaname> ,and press [Enter]
Enter the IP address of the Netstation in dot notation, [q|?] : <IP Address>
,and press [Enter]
The following line was added to /etc/hosts:

192.200.250.6 axtx1 # Netstation [no SMTP]
1AA 00014 0004 (9007) A4 ALICE 04.10
The LAN hardware address of an HP NetStation is shown on

its boot screen and its shipping carton label.
Enter LAN hardware address of Netstation [q|?] : <Mac Address> ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 144 / 318
318
Enter subnet mask in dot notation [q|?] (none): [Enter]
Enter gateway IP address in dot notation [q|?] (none): [Enter]

You have entered the following network parameters for this Netstation:
Name: axtx1
IP address: 192.200.250.6
LAN hardware address: 080009c81430
Subnet mask: none
Default gateway IP address: none
Are these correct? [y|n|?] (y): y ,and press [Enter]
axtx1 added to /etc/bootptab.
For any SLAVE station the script responds :

nfsd is not running or there are no local file systems... NFS cannot be
used.
For the MASTER station the script responds :
nNFS is running on this computer.

Use master hostname as NFS server for this Netstation? [y|n|?] (y) : n
,and press [Enter]
Configuration file /usr/tftpdir/usr/lib/X11/700X/config/axtx1.cfg created.
Vuelogin is already running

This Netstation will start using Vuelogin after powerup if factory defaults
in the Startup config screen have not been changed.
See the System Administrators Guide for HP NetStations for
information on configuring Vuelogin.
Copy .xsession script to a user home directory? [y|n|?] (def=y): [Enter]
Please enter user login name or q to quit and continue: q ,and press [Enter]
Add another Netstation? [y|n] (y): n ,and press [Enter]
N.B. On this stage answering y would allow to declare an other xterminal.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 145 / 318
318
_________________________________________________
MAIN MENU


?) Help x) exit
Please enter selection (default=1): x ,and press [Enter]

=>Copying axpres:/etc/hosts to /etc/hosts
=>Copying /etc/hosts to hostname1:/etc/hosts ...
=>Copying /etc/hosts to hostname1:/etc/hosts ...
=> . . .
To verify, list all the XTerminals created relaunching the command :
and quit.
Start the Xterminal and wait for the HP CDE screen.

The Xterminal station now is ready and can be connected to the server station.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 146 / 318
318
7.2 Remove an Xterminal station
The Xterminal configuration script must be run on the Master machine, logged as root.

Searching a workstation which has ENWARE software installed ...

ENWARE found on host(s) : hostname1 hostname2 ...
Enter hostname from list above or type . to quit [] :<hostname> ,and press
[Enter]
Executing /usr/bin/X11/700X/xtadm on hostname
Initializing ...
_________________________________________________
MAIN MENU
?) Help x) exit
Please enter selection (default=1): 2 ,and press [Enter]
_________________________________________________
REMOVE AN NETSTATION
Enter name of Netstation to remove [q|?] : <XTerminal_hostaname> ,and press [Enter]
Remove Netstation axtx1? [y|n|?] (y): [Enter]
axtx1 removed from /etc/bootptab.
Configuration file /usr/tftpdir/usr/lib/X11/700X/config/axtx1.cfg removed.
axtx1 removed from /etc/hosts.
***************************************************************************
* If you are running Network Information Services (Yellow Pages) or BIND, *
* please ask your site network administrator to remove the IP address *
* of this Netstation from the NIS or BIND database. *
***************************************************************************
Please press <Enter> to continue: [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 147 / 318
318
_________________________________________________
MAIN MENU


?) Help x) exit
Please enter selection (default=1): x ,and press [Enter]
ENWARE found on host(s): hostname1 hostname2 ...

Enter hostname from list above or type . to quit [] : .
The Xterminal station still remains connected to the server station up to the next power
off.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 148 / 318
318
8 PRINTER CONFIGURATION
To configure the printer you have to use axprintconf script. The axprintconf script configures the printer
on the master 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.
In this chapter two types of printer are considered. The first one, is a printer that needs to boot from the
RM, the second one is a printer that has already booted from another machine, so is necessary only to
configure the local spooler.
N.B. If there is no printer in your configuration the Performance Monitoring tool will fail.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 149 / 318
318
8.1 Configure Printer Booting from Local System
To be able to configure the printer to boot from the current system, the operator must know:

Printer name: a character strings up to 8 characters.

Location name: the site where the printer is installed.
IP address: with the same network field as for the stations
LAN hardware address: see #1
NOTE #1 The operator must get the information from the printer itself looking for the LAN address:
put the printer off line, press the Menu key several times to get TEST MENU, then press the Rubric key
several times to get PCL Configuration Page; print with the Selection key.
The only printer configuration to check locally is to declare the usage of network with TCP/IP address and
BOOTP.
The printer configuration script must be run on the Master machine, logged as root:
..,sys,root # axprintconf ,and press [Enter]
In the following example is described the complete sequence to declare, configure and test a printer:
Configuration:
Create printer
LAN address
printer name
IP address
Location
Test PostScript file
Add printer to local spooler

Lp destination name
Job Monitor
Default Queue
Banner Page
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 150 / 318
318
Configuring printer on axmaster ...
************************************************
* MAIN MENU *
* HP JetAdmin Utility for UNIX (Rev. D.00.37) *

************************************************
1) Configuration (superuser only): configure printer, add printer

to spooler
2) Diagnostics: diagnose printing problems
3) Administration (superuser only): manage HP printer, JetDirect
4) Administration (superuser only): manage JetAdmin
5) Printer Status: show printer status, location, and contact
?) Help q) Quit
Please enter a selection (q quit): 1 ,and press [Enter]
***************************************
* CONFIGURATION *
* HP JetAdmin Utility for Unix *
***************************************
Printer Network Interface:

1) Create printer configuration in BOOTP/TFTP database
2) Remove printer configuration from BOOTP/TFTP
Spooler:
3) Add printer to local spooler
4) Delete printer from local spooler
5) Modify existing spooler queue(s)
?) Help q) Quit
Please enter selection: 1 ,and press [Enter]
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> ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
A LAN address different from is suspected not to be an HP LAN address. Confirm

the validity of the LAN address.
NOTE: <Mac Address> is not an official address for HP JetDirect!
ED 02
957.130.892 W 3AL 61261 AA AA 151 / 318
318
Continue (y/n/q, default=n) [Enter]
Enter the network printer name/IP name (q quit): <Printer Name> ,and
press [Enter]

Enter IP address: <IP Address> ,and press [Enter]
Add axprinter and 192.200.250.8 to /etc/hosts? (y/n/q, default=y): y

,and press [Enter]
Printer name and IP address have been added to /etc/hosts. If your

/etc/hosts file is updated automatically from a master source, add the
name and IP address to your master source after the configuration is
complete.
Is this a (1) ethernet or (2) tokenring connection? (1/2/q,

default=1): [Enter]
Following are other settable parameters. You may set any items by
selecting the corresponding numbers. The values are used only when 0
is selected. To abort the operation, press q and no bootptab will be
created.
Other optional parameters:

1) Set location
2) Set contact
3) Set subnetmask
4) Set gateway
5) Set syslog
6) Change idle timeout
7) Create access list (up to 10 names). (Default: all allowed).
8) Other SNMP parameters:
(GET/SET community name, trap and community name, authentication
trap)
9) Set HP JetDirect lpd banner page
Select an item for change, or 0 to configure (q quit): 1 ,and press

[Enter]
Enter the printer location (q quit): <Location name> ,and press [Enter]
...

[Enter]
(configuring) ...
Completed creating BOOTP/TFTP configuration database for axprinter.
Note: Tftp service is also used for JetDirect bootup.

Make sure /var/adm/inetd.sec allows JetDirect to access tftp service on
1AA 00014 0004 (9007) A4 ALICE 04.10
this node.
ED 02
957.130.892 W 3AL 61261 AA AA 152 / 318
318
(testing, please wait) ...
......
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. [Enter]
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. [Enter]
Do you want to send test file(s) to this printer (y/n, default=n)? y

,and press [Enter]
This test is using test files to demonstrate that data bytes can be
transmitted across the HP JetDirect interface setup. As long as a few
characters print out, the test is successful.
The printer must be ready, i.e. online and not printing anything.
The following types of test files can be sent to the printer:
1) text file (if printer is in PCL or AUTO mode)

2) PostScript file (if printer is in PS or AUTO mode)
3) HPGL/2 file (if it is a HPGL/2 plotter)
4) User supplied file
Which one should be transmitted? (1/2/3/q, default=1) 2 ,and press [Enter]
===============================================================
Sending a test file to axprinter ...
Result: The file has been successfully sent to axprinter. Check output!
===============================================================
Press the return key to continue ... [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 153 / 318
318
*************************************
* CONFIGURATION *
*************************************


Spooler:
?) Help q) Quit
Enter the network printer name/IP name

(default=Printer Name, q quit): <Printer Name> ,and press [Enter]
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: Current Settings

1) Lp destination (queue) name: [Printer Name_1]
2) Status Log [(No Log)]
3) Queue Class [(Not assigned)]
4) Job Monitor [ON]
5) Default Queue [NO]
6) Additional printer configuration...
Choose successively 1 , 4 , 5 , 6 , q , 0 to set the corresponding parameters .

[Enter]
Currently used names:

(no queues are configured)
Enter the lp destination name (default=Printer Name_1,qquit): <Printer Name>

,and press [Enter]
. . .

[Enter]
. . .

[Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
. . .
ED 02
957.130.892 W 3AL 61261 AA AA 154 / 318
318
[Enter]
Following is a list of suggested parameter values for this printer.

To abort this operation, press q.


1) Model Script: [net_lj4x]

2) Default Printing Language [AUTO]
3) Job Recovery [ON]
4) True EndofJob [OFF]
5) Banner Page [OFF]
6) PostScript Level [Level 1]
Select an item for change, or q when done: 5 , and press [Enter]
The values are now:

5) Banner Page [ON]
Select an item for change, or q when done: q ,and press

[Enter]
The values are now :
1) Lp destination (queue) name: [Printer Name]

4) JobMonitor [OFF]
5) Default Queue [YES]
Ready to shut down the spooler and configure the new print queue.
The spooler will be running again after the configuration is done.
WARNING: If there are jobs currently being printed, and the page count
is enabled (i.e. when True EndofJob is turned on), this shutdown and
rerun of the spooler may result in incorrect page count.
OK to continue? (y/n/q, default=y) y ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
......
ED 02
957.130.892 W 3AL 61261 AA AA 155 / 318
318
Finished adding axprinter to the spooler.
Press the return key to continue ...
***************************************

* CONFIGURATION *

***************************************

Spooler:
?) Help q) Quit
Please enter selection: q ,and press [Enter]
************************************************
* MAIN MENU *
************************************************

to spooler
?) Help q) Quit
Please enter a selection (q quit): q ,and press [Enter]
scheduler stopped
printer axprinter now disabled
printer axprinter now enabled
destination axprinter now accepting requests
scheduler is running
...
..,sys,root #
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 156 / 318
318
8.2 Configure Local Spooler
This section shows how to configure a HP printer already active in your network.

IP address: with the same subnetwork of the HP 9000 system.
The printer configuration script must be run on the Master machine , logged as root:
..,sys,root # axprintconf ,and press [Enter]
Configuration

Lp destination name
Job Monitor
Default Queue
Banner Page
************************************************
* MAIN MENU *
************************************************

to spooler
?) Help q) Quit

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 157 / 318
318
*************************************
* CONFIGURATION *
*************************************


Spooler:
?) Help q) Quit

(default=axprinter, q quit): <IP Address> ,and press [Enter]

selected.

1) Lp destination (queue) name: [151_1]
4) Job Monitor [ON]
Choose successively 1 , 4 , 5 , 6 , 5 , q , 0 to set the corresponding parameters .

[Enter]

lp
Enter the lp destination name (default=axprinter_1, q quit): axprinter

,and press [Enter]
. . .

[Enter]
. . .

[Enter]
. . .
1AA 00014 0004 (9007) A4 ALICE 04.10

[Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 158 / 318
318



6) PostScript Level [N/A]
The values are now :
1) Lp destination (queue) name: [axprinter]

4) JobMonitor [OFF]
5) Default Queue [YES]

[Enter]
If the spooler is already running on the current system, the procedure displays the following message:
Otherwise, if the spooler is NOT already running on the current system:
axprinter.
The spooler is already not running in the system!
It will not be switched on after the configuration
In both cases you have to continue with the following sequence of answers:

......

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 159 / 318
318
***************************************
* CONFIGURATION *
***************************************

Spooler:
?) Help q) Quit
************************************************
* MAIN MENU *
************************************************

to spooler
?) Help q) Quit
scheduler stopped
...
..,sys,root #
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 160 / 318
318
8.3 Local printer for Presentation
A local printer can be declared as default printer for one presentation station.
However the script of configuration is always started from the master station as root. Of course the
presentation station must be reachable.
8.3.1 Configure printer booting from local system

Location name: the site where the printer is installed.
IP address: with the same network field as for the stations
LAN hardware address: see #1
NOTE #1 The operator must get the information from the printer itself looking for the LAN address:
put the printer off line, press the Menu key several times to get TEST MENU, then press the Rubric key
several times to get PCL Configuration Page; print with the Selection key.
The only printer configuration to check locally is to declare the usage of network with TCP/IP address and
BOOTP.
Configuration:
Create printer
LAN address
printer name
IP address
Location
Test PostScript file

Lp destination name
Job Monitor
Default Queue
Page Banner
..,sys,root # axprintconf server <station_hostname> ,and press [Enter]
where <station_hostname> is the name of the USM station.
************************************************
* MAIN MENU *
************************************************

1AA 00014 0004 (9007) A4 ALICE 04.10
to spooler
ED 02
957.130.892 W 3AL 61261 AA AA 161 / 318
318


?) Help q) Quit
***************************************
* CONFIGURATION *
***************************************

Spooler:
?) Help q) Quit
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> ,and press [Enter]
A LAN address different from is suspected not to be an HP LAN address. Confirm

the validity of the LAN address.
NOTE: <Mac Address> is not an official address for HP JetDirect!
Continue (y/n/q, default=n) [Enter]
Enter the network printer name/IP name (q quit): <Printer Name> ,and
press [Enter]
Enter IP address: <IP Address> ,and press [Enter]
Add axprinter and 192.200.250.8 to /etc/hosts? (y/n/q, default=y): y

,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 162 / 318
318
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.
Is this a (1) ethernet or (2) tokenring connection? (1/2/q,

default=1): [Enter]
Following are other settable parameters. You may set any items by
selecting the corresponding numbers. The values are used only when 0
is selected. To abort the operation, press q and no bootptab will be
created.
Other optional parameters:

1) Set location
2) Set contact
3) Set subnetmask
4) Set gateway
5) Set syslog
6) Change idle timeout
7) Create access list (up to 10 names). (Default: all allowed).
8) Other SNMP parameters:
(GET/SET community name, trap and community name, authentication
trap)
9) Set HP JetDirect lpd banner page

[Enter]
Enter the printer location (q quit): <Location name> ,and press [Enter]
...

[Enter]
(configuring) ...
Completed creating BOOTP/TFTP configuration database for axprinter.
Note: Tftp service is also used for JetDirect bootup.

Make sure /var/adm/inetd.sec allows JetDirect to access tftp service on
this node.
(testing, please wait) ...

......
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 163 / 318
318
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.)

[Enter]

Press the return key to continue the test.

If you are not ready for the next test (for example, the IP name has
not taken affect in your DNS server), press q to return to the
configuration menu now. [Enter]
Do you want to send test file(s) to this printer (y/n, default=n)? y

,and press [Enter]
This test is using test files to demonstrate that data bytes can be
transmitted across the HP JetDirect interface setup. As long as a few
characters print out, the test is successful.
The printer must be ready, i.e. online and not printing anything.
The following types of test files can be sent to the printer:
1) text file (if printer is in PCL or AUTO mode)

2) PostScript file (if printer is in PS or AUTO mode)
3) HPGL/2 file (if it is a HPGL/2 plotter)
4) User supplied file
Which one should be transmitted? (1/2/3/q, default=1) 2 ,and press [Enter]
===============================================================
Sending a test file to axprinter ...
Result: The file has been successfully sent to axprinter. Check output!
===============================================================
Press the return key to continue ... [Enter]
*************************************
* CONFIGURATION *
*************************************
Spooler:
?) Help q) Quit

(default=Printer Name, q quit): <Printer Name> ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 164 / 318
318
selected.


1) Lp destination (queue) name: [Printer Name_1]
4) Job Monitor [ON]
Choose successively 1 , 4 , 5 , 6 , 5, q , 0 to set the corresponding parameters .

[Enter]

(no queues are configured)
Enter the lp destination name (default=Printer Name_1,qquit): <Printer Name>

,and press [Enter]
. . .

[Enter]
. . .

[Enter]
. . .

[Enter]



1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 165 / 318
318
The values are now:


5) Banner Page [ON]

[Enter]
N.B. If the script fails because of the scheduler see section 14.4.

......

***************************************
* CONFIGURATION *
***************************************

Spooler:
?) Help q) Quit
************************************************
* MAIN MENU *
************************************************
1AA 00014 0004 (9007) A4 ALICE 04.10

to spooler
ED 02
957.130.892 W 3AL 61261 AA AA 166 / 318
318


?) Help q) Quit
scheduler stopped
...
..,sys,root #
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 167 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
168 / 318
9 INSTALLATION OF 1354RM R5.2
9.1 1354RM R5.2 Installation from scratch

This section explains how to install the 1354RM R5.2 on the workstation 700 series or on the server 800
series for the first time.
Either Korn Shell or Bourne Shell are supposed to be used by the operator.
The shell commands needed to be executed as user root (password install10) are prompted with
..,sys,root # , the command that have to be execute by snml (password system1) will be prompted with
..,$ .
9.1.1 1354RM R5.2 preinstallation steps
It is possible to install 1354RM software in two different ways:
as Information Manager (IM) or Master host:

this mean that a complete 1354RM installation will be made.
as User Service (US) or Presentation host:

this mean that only an User Interface Application installation will be made.
9.1.2 Create the 1354RM installation directory
Login as root.
Create the 1354RM R5.2 installation directory:
..,sys,root # mkdir /alcatel/1354RM52 ,and press [Enter]

..,sys,root # chmod g+w /alcatel/1354RM52 ,and press [Enter]
N.B. The RM user administrator snml will be automatically created by the customize procedure with
the home directory /home/snml.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 169 / 318
318
9.2 Installation of the Delivery Package
In the following chapter you can find the procedure to install a complete 1354RM delivery.

9.2.1 1354RM installation steps
Login as root.
Change current directory to the 1354RM R5.2 installation:
..,sys,root # cd /alcatel/1354RM52 ,and press [Enter]
Be sure that the current default directory is the right one:
..,sys,root # pwd ,and press [Enter]
N.B. If the output of pwd command is not /alcatel/1354RM52 execute the previous cd command
before proceed.
Insert the 1354RM R5.2 distribution medium labeled SWP1354RM_APPV5.2 into the CD driver.
Mount the CDROM with the following commands:
Where <cdrom device file> is the cdrom device file found in the paragraph 4.2.4.
Extract the restore file from 1354RM distribution kit:
..,sys,root # gunzip cd /SD_CDROM/1354RM.R5.2.1.5.tar.gz | tar xvf ./etc/restore

,and press [Enter]
9.2.1.1 Check the DISPLAY shell variable
Check the current value of the DISPLAY shell variable typing:
..,sys,root > echo $DISPLAY ,and press [Enter]
The command shows in the next line the current value of the variable. If the next line is a blank one, the
display is not set and the operator has to choose, if set it as well or get to the 9.2.1.3 to proceed with the
not graphical approach.
If the DISPLAY shell variable has been set with a valid X window display when the restore script is
started, a graphical window appears on the display showing all the environment variables that A1354RM
provides to allow to adapt it to the specific field requirements.
To know the meaningful of all the parameters, please refer to 9.2.1.4 of this document.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 170 / 318
318
9.2.1.2 Execute the Restore/Customize using Graphical Interface
N.B. If you are installing an RM IM machine, before launching the restore command, you have to
configure the printer. Please refer to the Chapter 8.
If the DISPLAY shell variable is set, execute the restore script file by running the following command:
..,sys,root # etc/restore /SD_CDROM/1354RM.R5.2.1.5.tar.gz ,and press [Enter]
N.B. Ignore the messages displayed from the procedure.
After few minutes requested to uncompress and restore the files in their right places, the following window
will appear on the display:
Figure 52. 1354RM Install Variables Definition
Set environment variables according to your configuration (please refer to the paragraph 9.2.1.4 of this
manual for variables description).
To change the values in the inputtext fields, you have to click on the inputtext field close to the variable
name and edit it as well.
To change the values of the menus, you have to select them by clicking on with the MB1 button of the
mouse (if you are righthanded the right button, if you are lefthanded the opposite one) the menu that
you have to modify and then select what you need. For example, select the menu IM of the variables
HOST_TYPE , and choose between IM, US.
1AA 00014 0004 (9007) A4 ALICE 04.10
When all the values have been set according with the requirements, click on Apply to store them into the
A1354RM environment description file.
ED 02
957.130.892 W 3AL 61261 AA AA 171 / 318
318
WARNING !! Before starting the Customize, in order to prevent the failure on the web
customization, modify the contents of the /alcatel/1354RM52/web/conf/magnus.conf:
..,sys,root # vi /alcatel/1354RM52/web/conf/magnus.conf ,and press [Enter]

Type /ServerName and modify the following line:
from:
ServerName tlvhbq.vim.tlt.alcatel.it (or similar host name)
to:
ServerName THIS_HOST
Type /User snml and modify the following line:
from:
User snmlr52 (or similar user name)
to:
User snml
Execute customize script pressing the Customize button, a window will be opened containing the traces
of the Customize execution. If some errors occur during customize execution, it signals to the operator
the log file where he can find informations on the occurred error. The customize procedure will produce
a trace file called etc/customize.trc containing all the messages printed out by this script.
At the end of the procedure click the Close button to continue the installation.
If the customize procedure stops with an error as the following:
ERROR: ovedelobj /usr/snml/lrf/old/tlvhhw/consChkAge.lrf failed, see

/usr/snml/trace/smf_trc/install/7513/objmng.trc for reason.
ERROR: unable to deregister old agents
Please refer to the paragraph 14.1 Ovlad registration error.
if the customize procedure fail with the following error:
NOTE: Registrating fields in OVw database ...

ERROR: reset OVw database terminated with failure
You have to exit from the windows of the customize procedure, then launch manually the
following command:
..,sys,root # /usr/snml/etc/reset_ovwdb ,and press [Enter]
NOTE: stopping OV platform

NOTE: resetting OVwDb
NOTE: restarting OVw processes
NOTE: loading 1354RM OVw fields
NOTE: loading embedded OVw fields
NOTE: starting OV platform
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: reset OVw db completed
to complete the customize procedure.

The command may fail, in this case repeat the command until it will be executed successfully.
ED 02
957.130.892 W 3AL 61261 AA AA 172 / 318
318
9.2.1.3 Execute the Restore/Customize without Graphical Interface
N.B. Before launching the restore command, you have to configure the printer. Please refer to the
Chapter 8.
If the DISPLAY shell variable is not set or it is set on a not valid X window display, when you execute the
restore file script by running the following command:
..,sys,root # etc/restore /SD_CDROM/1354RM.R5.2.1.5.tar.gz ,and press [Enter]
The system gives you back a message:
WARNING: cannot supported graphic interface, use editor for modify

env_snml_make file.
Edit etc/env_snml_make template file (generated by the restore procedure):
..,sys,root # vi etc/env_snml_make ,and press [Enter]
and set environment variables according to your configuration (please refer to sections 9.2.1.4, 9.2.1.5,
9.2.1.6, 9.2.1.7 of this manual for variables description).
Save and exit from the file pressing [Esc] and typing :x! and press [Enter] then copy on a new file
etc/env_snml typing:
..,sys,root # cp etc/env_snml_make etc/env_snml ,and press [Enter]
The etc/env_snml_make file contains all the needed environment variables that, if possible, are initialized
with the values assigned to them by the operator in previous release.
Variables contained in env_snml file are used in order to customize some configuration files in
properly way. This customization is done by means of substitution of symbols with the related
values. This substitution can be performed only on original files extracted from the installation kit
by means of the restore script.
For this reason it is forbidden to modify the env_snml file if you are not installing from
the beginning (executing a restore procedure) a complete installation kit.
Execute customize script running the following command:
..,sys,root # etc/trace etc/customize ,and press [Enter]
You will find a trace of the customize procedure execution in etc/customize.trc.
If the customize procedure stops with an error as the following:
ERROR: ovedelobj /usr/snml/lrf/old/tlvhhw/consChkAge.lrf failed, see

/usr/snml/trace/smf_trc/install/7513/objmng.trc for reason.
ERROR: unable to deregister old agents
Please refer to the paragraph 14.1 Ovlad registration error.
If the customize procedure fail with the following error:
NOTE: Registrating fields in OVw database ...

1AA 00014 0004 (9007) A4 ALICE 04.10
ERROR: reset OVw database terminated with failure
You have to exit from the customize procedure, then launch manually the following command:
ED 02
957.130.892 W 3AL 61261 AA AA 173 / 318
318
..,sys,root # /usr/snml/etc/reset_ovwdb ,and press [Enter]
NOTE: stopping OV platform

NOTE: resetting OVwDb

NOTE: restarting OVw processes

NOTE: loading 1354RM OVw fields
NOTE: loading embedded OVw fields
NOTE: starting OV platform
NOTE: reset OVw db completed
to complete the customize procedure.
The command may fail, in this case repeat the command until it will be executed successfully.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 174 / 318
318
9.2.1.4 Application Variables
SNML_HOME Set it to: /alcatel/1354RM52

Root directory of 1354RM product installation tree. The directory must exist
before installation.
HOST_TYPE It specifies if the host is an Information Manager (IM), with a complete 1354RM
installation, or an User Service (US), where the User Interface Application only
is installed. In the former installation type the database is created and agents
can be started, in the second type can be started User Interface Application
only, that are connected with a remote database.
N.B. In a multimachine installation only one can be defined as

Information Manager. In the following chapters this machine will be
referred as the IM host.
MIB Meaningful for IM configuration only.

This variable specifies if the old 1354RM database must be saved or not. Its
values can be NEW (create new DB), OLD (save the current DB or recover
it from an old installation directory) or REC (recover DB from backup).
NEW : This value have to be used during the first
installation of 1354RM. Using this value the
customize procedure will create a new empty DB.
OLD : This value have to be used during the 1354RM
upgrade. Using this value the customize will keep
the old DB (if the installation is performed on the old
installation tree) or will copy the old DB in the new
directory (if the new installation is performed on a
new installation tree).
REC : This value should be used after a disk failure that
causes the reinstallation of 1354RM
application. The customize procedure will not
create a new DB in order to save the mirrored DB
information to permit the recover of DB from an
incremental backup.
SNML_MIRROR Meaningful for IM configuration only.

Set it to: /mirror/snml
This variable specifies the directory that contains the database mirrored data
and Oracle Archive Log data.
N.B. It is mandatory that $SNML_MIRROR and /backup/snml

directories are completely disjointed. It is important that the
mirror directory is placed in an independent tree regards the
/backup/snml directory, otherwise some operations will fail (e.g.
during restore the redolog file will be overwritten).
N.B. In order to support properly 1354RM backup and restore features,

this mirror directory and the /backup/snml directory must be created
on a different physical disk than the one where 1354RM product
has to be installed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 175 / 318
318
NTWDOMAIN This variable specifies the identifier of the network domain handled by the
1354RM (by default the variable value is 1).
For the US node the value of this variable must be equal to the same variable
on the related IM_SERVER node.

N.B. Remember that this value must be different for each RM present in
the network.
IM_SERVER Meaningful for US configuration only.

This variable specifies the hostname of the IM machine.
REMOTE_SERVER Meaningful for IM configuration only.

This variable has to be set to allow the SMF transfer of all 1354RM backup to
a remote server. This server must be a 1354RMIM machine. These two
1354RM system MUST to have identical value of the variables that specifies the
Oracle root directory (ORACLE_HOME) and the RMDB Mirror directory
(SNML_MIRROR). Moreover the directory /tmp must to have enough space to
take up the gzipped backup transfer.
AC_INFO_FLAG Meaningful for IM configuration only.

This variable specifies if the old AC_INFO directory must be saved or not. Its
value can be YES (recover the old directory) or NO (create new directory).
It indicates if the data operators of the previous release have to be saved or not.
CNM_FLAG Meaningful for IM configuration only.

This variable specifies if you want to define the two new CNM (Customer
Network Management) operator profiles. Its value can be YES (define the new
profiles) or NO (not define the profiles).
9.2.1.5 Oracle DB Variables
In the following the environment variables that have to be defined to allows the installation procedure to
configure in the proper way the Oracle database are listed.
ORACLE_HOME Meaningful for IM configuration only.

Set it to: /opt/oracle7.2.
This variable specifies the Oracle root directory.
DB_SIZE Meaningful for IM configuration only.

It indicates the 1354RM Oracle database size. Possible values are:
small database dimension = 1 Gb.
medium database dimension = 1.5 Gb (default).
large database dimension = 1.9 Gb.
If the RM help is installed the previous Disk size shall be increased of 200 Mb.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 176 / 318
318
9.2.1.6 HPOV Variables
The following environment variables are used to configure properly HPOV during the 1354RM installation
procedure.
AGENT_REGISTRATION Meaningful for IM configuration only.

It specifies if the agent LRF file static registration must be performed
during the 1354RM installation phase. Its values can be YES (perform
the static registration default) or NO (do not perform the static
registration).
9.2.1.7 Operating System Variables
PRINTER This variable specifies the default system printer.

To enable the printer functionality in the RM help the Iview*printerConfig
resource must be defined in $XAPPLRESDIR/$LANG/Iview file. This
resources is a semicolon separated list of comma separated tuples giving
printer network names. If you need to configure this functionality, refer to
paragraph 11.17.
TAPE_SERVER Meaningful for IM configuration only.

<host name> which the tape is connected to.
This variable specifies the name of the host which the tape is connected to. If
it is set to none that means the no tape driver is available. The backup will be
executed leaving the file on hard disk.
N.B. If the tape server host is not the IM itself, on that host the snml user
must be defined and in its home directory you have to create the file
.rhosts with line in it composed as the following:
<1354RM IM host name> snml
X_CONSOLE Meaningful for IM configuration only.

This variable specifies the nodename of the console to display system
messages. It is already set to <host name>, where <hostname> is the name
of your host.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 177 / 318
318
9.2.2 Mandatory Patches installation
Meaningful for both IM and USM

In the following you can find the procedure to install the 1354RM patch provided with the 1354RM R5.2.

This patch have to be installed only if the related delivery has been already installed.
Close all application windows, shutdown the 1354RM using the application menu and stop all user service
manager instances (ovw, browser, mngAgent).
Shutdown the 1354RM by login as snml:
..,$ mngAgent shutdown control ,and press [Enter]

..,$ mngAgent shutdown system ,and press [Enter]
..,$ mngAgent shutdown database ,and press [Enter]
The rest of the procedure must be performed by root user.
If you have an open session with HP CDE presentation open, exit end login again as root.
Insert the 1354RM R5.2 distribution medium labeled SWP1354RM_APPV5.2 into the CD driver. If you
dont have already mounted the CDROM, mount it with the following command:
where <cdrom device file> is the cdrom device file found in the paragraph 4.2.4.
Change current directory to the snml installation root and extract patched file from 1354RM patch package:

If the output of pwd command is not /alcatel/1354RM52 execute the previous cd command before
proceed.
N.B. If the customize_patch procedure emits a chmod cant change ... message, please ignore it.
N.B. If the customize_patch procedure emits strange characters (i.e. 2;3;4;5;6;7;8;9c; ...) after the
end, please press [Enter] twice and ignore it.
9.2.2.1 1354RM R5.2 Fix 1 Installation
Extract the files from the patch delivery package:
..,sys,root # gunzip cd /SD_CDROM/1354RM.R5.2.1.5F1.tar.gz | tar xvf ,and press [Enter]
Execute customize patch script running the following command:
..,sys,root # etc/trace ./etc/customize_patch ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 178 / 318
318


Umount the cdrom SWP1354RM_APPV5.2, and remove it.

Insert the SWPNR50B_PL1 1/2 cdrom, if its not already present, and mount it if it not mounted:
After this patch installation will be not possible to login as snml or other RM user until the
upgrade of SMF has been done.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 179 / 318
318


N.B. After the patch installation it is necessary to verify the contents of the
/usr/snml/conf/im_host_conf file, since it is generated by the customize_patch procedure
(please refers to the paragraph 11.1).
Became snml user. Clean the resources area:
..,sys,root # su snml ,and press [Enter]

..,$ cd /usr/snml/etc ,and press [Enter]
..,$ ./RMremUnusedBitmaps.com ,and press [Enter]
..,$ exit ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 180 / 318
318
9.3 1330 AS Installation
The 1330AS (Alarm Sourveillance) is an Alcatel Generic Component that provides the alarm management
for all the Alcatel Applications.
The following chapter describes how to install and integrate the A1330AS 5.1 software in the 1354RM 5.2
environment, with both their possible configurations IM or USM.
N.B. To know how to deinstall the A1330AS, that can be helpful for the system management see
section Deinstalling A1330AS 11.12.3. Also, to know how to register and deregister the HP
OpenView agents of 1330AS see section: 1330AS Process Registrationand Removal
11.12.1.
9.3.1 1330 AS Installation
This procedure must be executed each time a new delivery of A1330AS and 1354RM has to be installed.
After the execution of the following procedure the A1330 IM processes will be integrated in the 1354RM
Process Monitor Control PMC and the A1330 tables space is created inside the 1354RM database.
In order to integrate the 1330AS with the 1354RM you have to execute the script file present in the directory
/usr/snml/etc with the name install_A1330.
N.B. The IM AS installation means the complete installation of IM/USM AS processes, therefore it
must be made on the 1354RM IM host.
N.B. This document does not show how to install A1330AS without the 1354RM platform.
If you dont have already mounted the CDROM, insert the 1354RM R5.2 distribution medium labeled
SWPNR50B_PL1 1/2 into the driver and download the kit with the following commands:
Execute the following commands :
..,sys,root # export ALARM_DIR=/alcatel/ALARM5.1 ,and press [Enter]
N.B. If you are installing on USM configuration, substitute IM with US in the following command:
..,sys,root # /usr/snml/etc/trace /usr/snml/etc/install_A1330

/SD_CDROM/1330AS511.1.P02.P03.HP4.2.tar IM ,and press [Enter]
acting A1330 depots ...

NOTE: Creating new /alcatel/ALARM5.1 directory
NOTE: Extracting A1330 depots ...
NOTE: Reading product configuration file
NOTE: Installing AS 5.1.1 product ...
NOTE: Installing ASTOOLS 5.1.1 product ...
NOTE: Adding link to /alcatel/ALARM5.1 area ...
NOTE: Updating A1330 files ...
NOTE: Add product specific probable causes
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: Updating IM parameter files for AS 5.1.1

NOTE: Configuring AS Current IM for 1354RM 1 ...
NOTE: Configuring AS Historical IM for 1354RM 1 ...
NOTE: Configuring AS Historical IM Rec for 1354RM 1 ...
ED 02
957.130.892 W 3AL 61261 AA AA 181 / 318
318
NOTE: Configuring AS 5.1.1 USMs for network domain 1 ...
NOTE: Managing startup procedures ...
NOTE: Creating default startup procedures ...
NOTE: Install navigation patterns on snml user

NOTE: Registrating A1330 agents on HPOV CI ...

NOTE: Adding link to /usr/A1330/data/ascurim_tlvhln1 area...
NOTE: Updating nml sieve file ...
NOTE: Updating network configuration files
NOTE: procedure terminated with success
Trace file in </usr/snml/etc/install_A1330.trc>
Press Enter to continue [Enter]
The /usr/snmletc/trace script will produce a trace file of the procedure install_A1330 execution called
/usr/snml/etc/install_A1330.trc.
9.3.2 1330 AS Customization
1330AS is provided with a default US customization in order to see only alarms relevant in 1354RM
environment and to distinguish them by their typology. All the AS1330 users have the possibility to change
the default customizations (HMI Layout, Counter Customizations, Colors, etc.) and so to work in an own
customized AS environment. These customizations are not saved at the end of the work session in order
to not propagate them to all the AS users, even if at USM exit AS requests for customizations saving.
The only user that can make persistent changes to 1330AS customizations is snml and these changes
are effective for all the users.
When a new configuration is made effective by running us_config_A1330 all the changes made by snml
are lost and is restored the initial default customizations.
9.3.3 Swedish language
In order to let ASUSM Components manage alarms containings swedish chars in the right way, execute
the following commands as snml user:
..,$ cp /usr/snml/conf/AS_graphicResources /usr/snml/conf/AS_graphicResources_english

,and press [Enter]
..,$ cp /usr/snml/conf/AS_graphicResources_sv_SE /usr/snml/conf/AS_graphicResources

,and press [Enter]
Now all the following start of ASUSM Components will be able to manage swedish chars using roman8
fonts.
In order to roolback the configuration to the default one (ASUSM displaying alarms in English) perform
the following command as snml user:
..,$ cp /usr/snml/conf/AS_graphicResources_english /usr/snml/conf/AS_graphicResources

,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 182 / 318
318
9.4 SMF Installation
The following are the steps to perform the first installation of the SMF package. In this case is assumed
that no previous SMF installation has been done.
9.4.1 Check the crontab environment
Meaningful for IM installation.
Before to install the package, is necessary to check the crontab environment for the snml username:
Login as snml (password system1) and check if you can read the associated crontab file:
..,$ crontab l ,and press [Enter]
If the crontab command displays some errors, you have to continue with the following actions (as root):
if the /var/adm/cron/cron.allow file is present you have to add the snml username to it:
..,sys,root # vi /var/adm/cron/cron.allow ,and press [Enter]
Type :G and add at the end of the file the snml username then save the file pressing [Esc] and typing
:x! and press [Enter].
otherwise, if the previous file is not present, you have to modify the /etc/cron/cron.deny file removing
the snml username from it:
..,sys,root # vi /var/adm/cron/cron.deny ,and press [Enter]
Type /snml and remove the current line then save the file pressing [Esc] and typing :x! and press
[Enter].
9.4.2 Install the SMF package
Login as root user.
SWPNR50B_PL1 1/2 into the driver and mount it with the following commands:
and install the kit:
..,sys,root # swinstall s /SD_CDROM/SMF_R5.1.7.9.sdpkg SMF ,and press [Enter]
N.B. Ignore the messages displayed from the procedure.
N.B. If the SMF installation in a RMP machine configured in HPUX 11.00 doesnt work well, refer
to paragraph 14.8.
N.B. If you need to remove the SMF package refer to paragraph 11.15, if you have a problem during
the installation refer to paragraph 14.8.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 183 / 318
318
If the 1354RM is installed again the SMF icon disappair from the vertical palette of the desktop, to insert
it again it is necessary execute the command:
..,sys,root # swconfig x reconfigure=true SMF ,and press [Enter]

9.4.3 SMF package postinstallation
After the installation of SMF kit, it is necessary execute some actions (as root):
a) a new smf_conf file is available so it is necessary execute the command:
..,sys,root # /usr/snml/etc/update_network ,and press [Enter]
to generate a new system management features configuration according to the smf_conf file.
N.B. This procedure must be executed both from IM and US hosts in the given order.
N.B. Ignore the warning messages displayed from the procedure.
b) Change current directory to the snml installation root and execute customize_patch script running
the following commands:

N.B. If the procedure emits a chmod cant change ... message, please ignore it.
N.B. If the procedure emit strange characters (i.e. 2;3;4;5;6;7;8;9c; ...) after the end, please
press [Enter] twice and ignore it.
c) Change the ownership of /tmp/smf_tmp/1354RM/* directory trees as follow:
..,sys,root # chown R root:dba /tmp/smf_tmp/1354RM ,and press [Enter]

..,sys,root # chmod 777 /tmp/smf_tmp/1354RM ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 184 / 318
318
9.5 Integration of 1354RM with Navigation Component (NAV)
Navigation Subsystem (in the following NAV) is a subsystem that allows the Navigation Communication
between different precesses.
The Navigation and Communication services are made available by the navserver process. Each user
logged in on the 1354RM system will have its own navserver instance serving him.
It must be installed only on 1354RM (both IM, US and SPARE).
9.5.1 NAV Installation
Login as root user.
If 1354RM users are logged before NAV installation, they will not be served by navserver up to the next
login.
N.B. Due to 1353SH installation procedure limitation, if the 1353SH and 1354RM has to be co-
Hosted, install first 1353SH.
Insert the SWPNR50B_PL1 1/2 cdrom. Mount it with the command:

Execute the following command to launch the installation script:
..,sys,root # /usr/snml/etc/install_NAV /SD_CDROM/NAV502.3.sdpkg <target directory>[Enter]
where <target directory> is installation directory for the kit. The suggested is /alcatel/NAV50.
NOTE: Creating a new /alcatel/NAV50 directory

NOTE: Reading NAV (FWK RunTime) product version informations...
NOTE: Determined NAV (FWK RunTime) version: 5.0.2
NOTE: Loading NAV 5.0.2 dependent parameters...
NOTE: Installing FWK RunTime 5.0.2 product...
NOTE: Addinng link to /alcatel/NAV50 area...
NOTE: Extracting files for NAV integration on 1354RM system
NOTE: Configuring NAV installation for default instance...
NOTE: Loading Version dependent parameters...
NOTE: Configuring NAV 5.0.2 with default instance (0)
NOTE: Configuring NAV 5.0.2 navserver_0 process
NOTE: Managing navserver_0 trace setting under /usr/snml/trace/
NAV.trcDir
NOTE:Managing navserver_0 starting script
After the procedure execution, NAV process will be run automatically at each user login. Each user has
its own NAV instance serving its application.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 185 / 318
318
9.6 SEC Security Subsystem
If you have to install the RMPlugin of SH in the current RM environment after the end of this
installation procedure, you can to avoid the RM SEC software installation at this time, and skip to

the paragraph 9.7 directly. IN THIS CASE, YOU WILL HAVE TO INSTALL THE RM SEC

SOFTWARE AFTER THE END OF THE RMPLUGIN INSTALLATION.
The SEC Subsystem is composed of two permanent processes:
secim process which is the agent of the Security Subsystem and keep all the informations related
to the users and the system;
secim process have to be running only on 1354RMIM.
lss process which is a kind of gate for applications who are interested on user Security profile. There
is one lss process for each workstation/server belonging to the 1354RM system (1 for each
presentation and each IM).
These permanent processes are configured to automatically run everytime just after the installation.
The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage as in RM Browser
In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator mgt. Moreover the
integration of SEC in SMF is also related to the Operator Backup. Each time a new Operator backup is
performed also SEC database is backuped.
If on top of 1354RM is installed also 1353SH software for cohosted or presentation installations you have
to install SEC for SH using the axinstallGui.ptk procedure and SEC for RM as described below.
Keep into account that the SEC installations for RM and SH are different, the integration schemas and the
configuration steps are different.
The following chapter describes how to install and integrate the SEC 5.0 software in the 1354RM 5.2
environment, with both their possible configurations IM or USM.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 186 / 318
318
9.6.1 SEC Warning
This procedure must be executed each time a new delivery of SEC and 1354RM has to be installed.
After the execution of the following procedure the SEC processes will be integrated in the 1354RM System.
In order to integrate the SEC with the 1354RM you have to execute the script file present in the directory
/usr/snml/etc with the name install_SEC.
Due to 1353SH installation procedure limitation, if on top of 1354RM you have to install
also 1353SH software, you MUST to install first SEC for 1353SH.
N.B. This procedure works only if no old SEC installations for RM are present (e.g. /usr/sec link is
present).
N.B. If a different SEC instance is already installed (after cohosted or 1353SH presentation
installation) on the target 1354RM host STOP all the running SEC processes with the script
/usr/1353sh/install/script/stop_security.sh.
N.B. This document does not show how to install SEC without the 1354RM platform.
N.B. The procedure, in order to grant a proper installation, check that the chosen target installation
directory is empty, otherwise it returns an error.
9.6.2 SEC Workaround
In order to avoid problem during the 1354RM SEC installation on both 1354RM IM and USM the
install_SEC script must be modified this way:
Login as root:
Save the script file in a backup copy:

..,sys,root # cd /alcatel/1354RM52/etc/ ,and press [Enter]
..,sys,root # cp p install_SEC install_SEC.save ,and press [Enter]
Modify the script with vi:

..,sys,root # vi install_SEC ,and press [Enter]
Locate the line:

ilog_home=swlist l file ILOGVIEWS* | grep ilog.*views.* | (read a ; echo \$a)
and comment it by inserting a # as first character of the line
Exit vi saving the modification by pressing [Esc] and enter: :x! and [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 187 / 318
318
9.6.3 SEC Installation
SWPNR50B_PL1 1/2 into the driver and download the kit with the following commands:

Execute the following commands (as root):

..,sys,root # /usr/snml/etc/trace /usr/snml/etc/install_SEC
/SD_CDROM/SEC_500.1.P01.HP4.2.sdpkg <target directory> ,and press [Enter]
where <target directory> is installation directory for the kit. The suggested is /alcatel/SEC50.
The /usr/snml/etc/trace script will produce a trace file of the procedure install_SEC execution called
/usr/snml/etc/install_SEC.trc.
After the SEC installation on top of RM restart the SEC processes installed on top of SH with the script
/usr/1353sh/install/script/start_security.sh.
After the installation the link /usr/sec is created in order to point to the target installation directory chosen.
N.B. In the case in which SEC is already installed on RM please do a Backup of Operator datatype,
deinstall old SEC, install the new version of SEC and perform a Restore of the Operator
datatypes. If you want to install a new version of SEC it is possible that the DB have to be
migrated.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 188 / 318
318
9.7 1354RM Post installation steps
In order to allow the correct behavior of the application, it is necessary to do some actions by hand, these
actions are the minimum configuration required by application.
9.7.1 Increase the Max Data Segment Size
Meaningful for IM configuration only.
After the package installation you have to increase the maxdsiz kernel parameter as following:
database SMALL > maxdsiz = the default value

database MEDIUM > maxdsiz = (128*1024*1024)
database LARGE > maxdsiz = (256*1024*1024)
If on machine installed with bootable medium C842C17D_TSD SAM issue an error

message related to ncallout, you have to change also it to 8200.
To modify the indicated parameter see 11.6 paragraph.
9.7.2 Increase the shared pool size parameter
N.B. If on the current machine you have to install also the OSResilience, is profitable to modify now
the kernel parameters required by it (see [5] on page 12).
You have to execute the following post installation steps:
a) Shutdown the database and RM system.
Login as snml and shutdown the database and the system :

and login again as root user.
b) Force the ORACLE modify the interested kernel parameters:
1) Edit the /usr/snml/databases/dbsnml/admin/pfile/init1.ora file:
..,sys,root # vi /usr/snml/databases/dbsnml/admin/pfile/init1.ora ,and press [Enter]
Type /shared and change the value of the line not commented of shared_pool_size parameter
to 64000000 (64Mb).
ONLY if you have to selected a small Oracle database size (see DB_SIZE variable value in
the paragraph 9.2.1.5) you have to type /processes and change the value of the line not
commented of processes parameter to 200.
1AA 00014 0004 (9007) A4 ALICE 04.10
Then save the file pressing [Esc] and typing :x! and press [Enter].
ED 02
957.130.892 W 3AL 61261 AA AA 189 / 318
318
2) Edit the /usr/snml/databases/dbsnml/admin/pfile/init1_make.ora file:
..,sys,root # vi /usr/snml/databases/dbsnml/admin/pfile/init1_make.ora ,and press

[Enter]

Type /shared and modify the line with the line defining shared_pool_size parameter from:
shared_pool_size = $shared_pool_size
to
shared_pool_size = 64000000
Example:
...
# shared_pool_size = 3500000 # SMALL
# shared_pool_size = 6000000 # MEDIUM
# shared_pool_size = 18000000 # LARGE
shared_pool_size = 64000000
...
The installation guide Ed.01 contain wrong instruction, it ask to add a new line
shared_pool_size = 64000000 just before shared_pool_size = $shared_pool_size. If you
find both line leave the line with shared_pool_size = 64000000.
ONLY if you have to selected a small Oracle database size (see DB_SIZE variable value in
the paragraph 9.2.1.5) you have to type /processes and change the line not commented of
processes parameter to value 200.
...
# processes = 20 # SMALL
# processes = 50 # MEDIUM
# processes = 200 # LARGE
processes = 200
...
9.7.3 Database Reset for 1354RM for Patch FIX16
The FIX16 patch installation foreseen to recreate the database by login as snml and executing the
following command:
be sure that the database is not mounted:

..,$ /usr/snml/databases/dbsnml/etc/create_db ,and press [Enter]

..,$ /usr/snml/databases/dbsnml/etc/stop_db ,and press [Enter]
Restart the database and RM system.

..,$ mngAgent startup database ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 190 / 318
318
9.7.4 Performance Monitoring Customization
Meaningful for IM configuration only where the Plugin will be installed.

The file /usr/snml/conf/eml_PM_nodes have to be updated each time a new 1353SH or

1353WX Element Manager is added to the 1354RM.
It is on User responsibility to specify in the configuration file eml_PM_nodes the host machines where the
EMLIM applications communicating to RM the PM Data are. To do this follow these steps:
..,sys,root # cd /usr/snml/conf ,and press [Enter]
Edit the file eml_PM_nodes adding a line for each managed EML.
..,sys,root # vi eml_PM_nodes ,and press [Enter]
a) If you dont have already installed the plugin, first of all delete all the rows already present as default,
then add the needed rows with the following syntax:
<EML_ID> <host1> <host2> <remote_user> <home_dir_remote_user> <dir_15M> <dir_24M>
where:
<EML_ID> is the EML identifier. To know which is the range used refer to the manual
1353SH Installation Guide [7], chapter SH Configuration, paragraph
Instatiate Network Elements.
<host1> is the hostname where EMLIM application is located.
<host2> for 1353WX implemented on a 1641SX with two AU, it is the hostname
of the redundant AU.
It must be set none for 1353SH or 1353WX implemented on 1641SX with
a single UA.
<remote_user> is the user used by RM during the remote connection to get files, it as
to be always set to rmpm.
<home_dir_remote_user> is the home directory of the remote user, that has to be:
/usr/1353sh/rmplug/data/pm (link to /usr/rmpm) for 1353SH
or /usr/rmpm for 1353WX.
<dir_15M> is the name of the subdirectory where EML provides files for 15 minutes
granularity, it has to be set to pm15Dir
<dir_24M> is the name of the subdirectory where EML provides files for 24 minutes
granularity, it has to be set to pm24Dir
Example for SH:

200 axsh3m none rmpm /users/rmpm pm15Dir pm24Dir
Example for WX installed only on one AU:

13 AUxb none rmpm /users/rmpm pm15Dir pm24Dir
Example for WX installed on two different AU (redundant):

1AA 00014 0004 (9007) A4 ALICE 04.10
14 AUxa AUxb rmpm /users/rmpm pm15Dir pm24Dir
ED 02
957.130.892 W 3AL 61261 AA AA 191 / 318
318
b) If you have the plugin installed, you will find already configured some rows regarding emlims. Verify
which emlims are configured and modify the file as you need, adding the rows regarding the emlims
that you need and removing the one not necessary. Use always the syntax explained in point a ).

9.7.5 PM Backup/Restore
In order to allow the correct behavior of Performance Monitoring Backup/Restore the right on the file
/usr/snml/bin/managerFK have to be changed with the following command:
..,sys,root # chmod ax /usr/snml/bin/manageFK ,and press [Enter]
9.7.6 Create ORACLE User for Archive purpose
Meaningful for IM configuration.
To allow the PM data archive function, a new ORACLE user environment is required. The following
procedure has to be executed after the RM installation:
a) Login as snml and startup the database:
b) Create the ORACLE user (rmpmarch/rmpmarch) and relevant tablespace:
..,$ export DB_ADMIN=/usr/snml/databases/dbsnml/admin ,and press [Enter]

..,$ /usr/snml/bin/pmInitRMPArchive.com ,and press [Enter]
c) Create required tables and views (dropping the old ones if any):
..,$ /usr/snml/bin/pmCreateRMPArchive.com ,and press [Enter]
The command will show some errors like the following:
ERROR: table or view does not exist
d) Initialize the PM Book Period table in RM User DB (snml/system1) in order to customize the
starting & ending time of Archive activity that will be taken into account by the next user archive
request:
..,$ chmod u+x /usr/snml/RMP/Admin/InitRMP ,and press [Enter]

..,$ /usr/snml/bin/pmInitRMP.com ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 192 / 318
318
9.7.7 Prevent Unnecessary Mail Messages to root
In order to prevent the unnecessary mail messages to root user like the following:
A message has appeared in the diagnostic message buffer (dmesg).

Following the body of this message :

(Note : all the messages are logged into /var/adm/messages)
Nov 2 18:00
Cant open /var/adm/msgbuf
enter the following command:
..,sys,root # chown root /sbin/dmesg ,and press [Enter]
9.7.8 Software Download Workaround
In order to avoid problems related to run the Software Donwload as plugin is necessary to execute the
following actions:
Meaningful for RM IM and USM
..,sys,root # vi /usr/1353sh/swdl/swdlman/script/run_swdlman ,and press [Enter]
a) At the beginning of the file, after the line #!/bin/ksh, add the following line:
. ~/.profile
b) Now change all the $1 to $* digiting the command: :%s/\$1/\$*/ ,press [Enter] then [Esc], type :x!
to save and quit the file.
Verify the modifications have been made.
c) Change the rights of the following file:
..,sys,root # chmod 777 /alcatel/1353sh/swdl/swdlman/script/run_swdlman ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 193 / 318
318
9.7.9 MultiIM Configuration
At the end of 1354RM installation in the file /usr/snml/conf/<hostname>/ntwDomains is described the

default Network Domain (with the Identifier specified in env_snml file) that will be used by RM user

interface. The informations will have the following format:

loc <n> on RMIM machine
far <n> <hostname> on RMUS workstation
where <n> is the Network Domain Identifier and <hostname> is the name of the host where the
relevant RMIM is running.
N.B. In a ntwDomains file a loc row can exist only.
In order to enable the RM User Interface to connect to different Network Domain the user shall, insert
manually in the ntwDomains file a line with the far format, and execute the following commands:
..,sys,root # /usr/snml/etc/customize_patch ,and press [Enter]
and if AS is installed:
..,sys,root # /usr/snml/etc/us_config_A1330 ,and press [Enter]
The /etc/hosts file must contain the new added RMIM machine address and the
AGENT_REGISTRATION environment variable, in /usr/snml/etc/env_snml file, must be set to yes.
When the MultiIM configuration is enabled, opening an empty map in NetView will present a dialog box
to the user in order to associate a Network Domain to the map (info taken into account when normal
operation are executed), on the other side opening the Browser application a MultiRM icon is presented
as root object and, with the Main related item operation, the user can view all the defined Network
Domains.
N.B. Is necessary to declare the unknown IM on each /etc/hosts files of each USM of your network.
To have got access to the whole network domain, in a multimaster network configuration (i.e. 3 IM WSs
and 1 USM WS), it is necessary to do the following steps:
1) Add user1 on USM and IM_1 (assuming you are working on USM ws);
2) Add the USM ws console on all IM WSs by Add console function (working on each IM);
3) Add the user1 on IM_2 and IM_3 by Add Operator function (working on each IM).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 194 / 318
318
9.7.10 QNN Interface Management
If in your network is present a 1354NN, you have to define the RM user profiles to allow the Qnn ZoomIn
function.
If there is no 1354NN you can skip this section.

9.7.10.1 Enable/Disable QNN Agent Management
Login as root to execute the following steps:
Modify the /.rhosts file to allow the comunication between the machines:
..,sys,root # vi /.rhosts ,and press [Enter]
and insert at the end of the file the following line:

+ root
Save and quit the file pressing [Esc], typing :x! [Enter].
Before to proceed, you MUST modify this file on both machines (NN and RM).
Declare the A1354NN IM and USM via axinitwsGui tool with the command:
Enter the TCP/IP address and the hostname of the A1354NN IM machine and click on Add button.
Then click on Exit to dismiss the tool.
If you have any NNX XTerminals, you have to add them manually in the /etc/hosts file:
..,sys,root # vi /etc/hosts , and press [Enter]
and insert a line with the following format for each of them:
<A1354NN_IP_Address> <A1354NN_XTerm_hostname> #NNX
Save and quit the file pressing [Esc], typing :x! [Enter].
Configure the xntp network service with:

..,sys,root # axxntpconf remote <hostname_A1354NN_IM> , and press [Enter]
Register the aetitle HP OpenView agent of A1354NN on A1354RM system:

..,sys,root # $OV_BIN/ovaddobj r t <hostname_A1354NN_IM> \ ,and press [Enter]
$OV_LRF/aetitle.lrf <hostname_A1354NN_IM> ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 195 / 318
318
Enable the Qnn Agent Manager:
Logout as root and login as snml.

During the current phase the database agent MUST BE UP, the system and the control agents

MUST BE DOWN. If are not already thus, you have execute the commands:

Proceed with the commands:
..,$ su root ,and press [Enter]

..,sys,root # /usr/snml/etc/QnnAgentMng add ,and press [Enter]
..,sys,root # exit ,and press [Enter]
..,$ mngAgent startup system ,and press [Enter]
..,$ mngAgent startup control ,and press [Enter]
N.B. This sequence of commands will change the configuration file of the Process Monitor Con-
trol (PMC) application.
If the PMC window is already open, close and open it again. So, you have to control the status of the
agents. Open the icon Administration, in the window System Management Features select System
Start/Stop, then Process Monitor Control. The Database box must be green. Also the System and
the Control boxes must be green.
After a RM patch installation the operator should perform the enabling of the QnnAgent Mana-
gement using the previous sequence of commands.
9.7.10.2 QNN Privilege Rule Setup
In this release it is necessary to verify the /usr/snml/ac_info/initiators.ac.<n> (where <n> is the network
domain of the current RM), defining for the initiator 301 1354NN the rule AC_R_NN:
..,sys,root # vi /usr/snml/ac_info/initiators.ac.<n> ,and press [Enter]
Type /301 and [Enter]:
Modify from:
50 : Path Administrator Operator : AC_R_PADMIN
301 : 1354NN : AC_R_VPN
400 : Enhanced Virtual Private Operator : AC_R_EVPN
401 : EVPN Operator 1 : AC_R_EVPN
to:
50 : Path Administrator Operator : AC_R_PADMIN
301 : 1354NN : AC_R_NN
400 : Enhanced Virtual Private Operator : AC_R_EVPN
1AA 00014 0004 (9007) A4 ALICE 04.10
save and quit with pressing [Esc] and typing :x! and [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 196 / 318
318
9.7.10.3 RM user definition for Qnn ZoomIn
The zoomin operation from 1354NN on RM can be performed with three different profiles according to
the definitions given in the Qnn interface. The defined profiles are:
a) NN administrator
b) NN user
c) NN viewer
The first profile must be mapped on the RM user qnnmng, the second one must be mapped on the RM
user qnnagent, and the latter one with the RM user qnnview. These three users must be manually de-
fined on RMIM, the definition on RMUSM is not required.
All the users use NAD already defined in RM, the qnnagent uses a dedicated NAD that is described in
the NAD description list with the 1354NN NAD identifier.
If the following users are not defined, the zoomin from NN cannot work and it is not displayed any addition-
al message.
9.7.10.3.1 The users
To configure the needed users, execute the following steps:
Login as root.
a) Check the current value of the DISPLAY shell variable typing:
..,sys,root # echo $DISPLAY ,and press [Enter]
The command shows in the next line the current value of the variable. If the next line is a blank one, the
display is not set and the operator has set it as well.
b) Proceed with the following commands:

..,sys,root # vi etc/AddQnnUser ,and press [Enter]
Type the following command: :%s/LOC_HOST:0.0/DISPLAY/ and press [Enter].

Type :x! to save and quit the file.
c) Configuration of the users:
This scripts is launched from the RM IM machine always as root user.
Login as root.
Enable the access to the screen from everyone with:
..,sys,root # xhost + ,and press [Enter]
Became snml with the following commands:
..,sys,root # su snml ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. Remember to set the display:
..,$ export DISPLAY=<$DISPLAY> ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 197 / 318
318
where <$DISPLAY>: is the output of the command echo $DISPLAY previously executed
in point a ).
Execute the following steps:

..,$ . ./.dtprofile ,and press [Enter]
Retrieve the $NTWDOMAIN variable value:
..,$ echo $NTWDOMAIN ,and press [Enter]
The result must be used in the next command (for example 1). Launch the aca tool:
..,$ /usr/sec/1354RM_<$NTWDOMAIN>/script/aca ,and press [Enter]
N.B. <NTWDOMAIN> is the value of the variable inserted during the customization procedure
(see paragraph 9.2.1.4).
Figure 53. Aca: Access Rights Definitions
Select the menu Configuration, then Initiator.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 198 / 318
318
Figure 54. Aca: Initiator Configuration
Click on the ADD button. A new window will opened:
Figure 55. Aca: Operator Creation
Type qnnmng and then click on the APPLY button. To close the window click on CLOSE.
Now you have to declare the group that qnnmng will belong. Select the Operator Group card on Initia-
tor Configuration window (see Figure 54. ), then select the group OSadministrator (see Figure 56. )
with the mouse, then click on MODIFY.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 199 / 318
318
Figure 56. Initiator Configuration
The Operator Group Definition window will be open on the screen.
Figure 57. Aca: Operator Group Definition
Select qnnmng in the Excluded Operator box. Click on the upper arrow (right arrow) to add the
qnnmng user to Osiadministrator group.
Click on APPLY button and then close the window clicking on the CLOSE button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Repeat these configuration steps for all the users included in Table 7. In this table are shown all the
users and their groups (Profile).
Close the Initiator Configuration window.
ED 02
957.130.892 W 3AL 61261 AA AA 200 / 318
318
Verify in the Access Rights Definitions window that the user qnnmng (and all the other configured)
is included on the Initiator list, then close the window. At the next message confirm with YES.

d) and proceed:

..,sys,root # ./.snmlrc ,and press [Enter]
..,sys,root # /usr/bin/X11/xhost +hostname ,and press [Enter]
..,sys,root # etc/AddQnnUser ,and press [Enter]
Where <hostname> is the name of the 1354NN.
N.B. Please ignore the messages displayed during the execution of the procedure.
The command will define the users with the following characteristics:
RM user Profile NAD
qnnmng OSadmin 1
qnnagent PathBuilder 301
qnnviewer LookOnly 40
qnnpmop PathBuilder 301
Table 7. NN users
9.7.11 End of Postinstallation
Now the postinstallation of 1354RM application is completed, but if you have any SH in your network, the
1354RM installation must be integrated with the 1353SH Plugin as shown in RM Integration chapter of
1353SH Installation Guide, [7] on page 12.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 201 / 318
318
9.7.12 License Configuration
To be able to use the HP OpenView software you have to ask for a nodelock license, to do it you have to
get the SPU target id of your host using the following command:

Get the SPU target ID:
For HPUX 10.20:

..,sys,root # i4target v ,and press [Enter]
For HPUX 11.00:

..,sys,root # /opt/ifor/ls/bin/i4target v ,and press [Enter]
Permanent Target ID: fff95812
SPU Target ID: 2196895
The Permanent Target ID is derived from a permanent hardware source

on the system from which the i4target program is executed.
This target ID may be used for all license types.
The SPU ID is derived from a hardware identification number on the

SPU. It is used as the Permanent Target ID when no higherpriority
sources for Permanent Target ID (i.e., LAN cards) are present.Current
Then you have to require to the HP License Center by follow the steps described in chapter 9.7.13 of this
document.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 202 / 318
318
9.7.13 How request the HP OpenView license to HP
The HP OpenView licence have to be requested for each system, because we user the nodelock license
type so all the node must hate their own license.
To obtain the license password for HP OpenView DM, you must fill in a form and sent it to one of the HP
Password Delivery Centers listed in Table 8.
The form is stored in the file $OV_CONF/OVLicense/forms/dm/product, you have to edit it with vi
inserting your data, the licensing data and the product license data:
To be able to fill in the licensing data you have to collect some informations:
HP Order No. shown on the Entitlement Certificate of HP OpenView.

License SPU Server Target ID provided by command i4target executed by root
user at line SPU Target ID:.
License Server Hostname provided by command hostname.
License Server Operating System HPUX followed by the output of command uname r.
Fill in the product license data line J1055DA HP OpenView Telecom DM TMN Manager Platform 5.x
License with: 1
N.B. Add the following line just after the License Server Operating System line:
License Type: Nodelock
When the form will be filled in send it by fax or EMail to the appropriate HP Password Delivery Center.
Table 8. HP Password Delivery Centers
Geographic Email Address Fax Number Phone Number Hours of

Location Operation
(local time)
America americas_password@ U.S.A. Est U.S.A. Est U.S.A. Est

cnd.hp.com +1 801 431 3654 +1 801 431 1597 8 a.m.8p.m.
Asia asia_password@ Japan Japan Japan

cnd.hp.com +81 3 3227 5238 +81 3 3227 5264 9 a.m. 5 p.m.
Europe & europe_password@ Netherlands Netherlands Netherlands

Africa cnd.hp.com +31 55 543 4645 +31 55 543 4642 8 a.m.5 p.m.
N.B. The information shown in Table 8. could be subject to change without notice.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 203 / 318
318
9.7.14 Insert the HP OpenView license
a) When the HP License Center gives you back the license you have to insert the password line in the
file /var/opt/ifor/nodelock.

..,sys,root # vi $OV_NODELOCK/nodelock ,and press [Enter]

670985ac8b34.02.0f.02.71.2b.00.00.00 kathvjxr2vhz2f8tah7bybn6
DM DEMO 31 DEC 20
05 * M * N 5.XDEMO
670985ac8b34.02.0f.02.71.2b.00.00.00 qdxy97y69qg3yf8tah7cicda
DM_PLATFORM DEMO
31 DEC 2005 * M * N 5.XDEMO
670985ac8b34.02.0f.02.71.2b.00.00.00 shjvw5rjyuyp6f8tah7t2brv
OPI DEMO 31 DEC 2
005 * M * N 4.2DEMO
670985ac8b34.02.0f.02.71.2b.00.00.00 ugvcq4ee428baf8tah7b4bt6
WINC DEMO 31 DEC
2005 * M * N 5.XDEMO
670985ac8b34.02.0f.02.71.2b.00.00.00 e26xzn9cwjfinf9fah7b6bwe
ASSOC DEMO 31 DEC
2005 * M * N 5.XDEMO
670985ac8b34.02.0f.02.71.2b.00.00.00 jtjtevuy9mitignxah7cgb9i
NNM_NNM250 DEMO 3
1 DEC 1999 * M * N 5.XDEMO
Press [G] to go to the end of the file, press [o] and insert the password.
Press [Esc] and type :x! and [Enter] to save and quit the file.
N.B. $OV_NODELOCK should be set to /var/opt/ifor.
b) Set the entry file /etc/opt/OV/share/conf/nnmlicense to DM 250.
Modify the file from:
# Valid types and numbers of licenses to request are:

#
# Type Number
#
# Full 1
# NNM250 250 or more
# Developer 1 or more
# ITO 1
# ITA 1
# DM 250 or more
#
###########################################################
#
NNM250 250
to:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 204 / 318
318
# Valid types and numbers of licenses to request are:
#
# Type Number
#
# Full 1
# NNM250 250 or more

# Developer 1 or more
# ITO 1
# ITA 1
# DM 250 or more
#
###########################################################
#
DM 250
Save and quit the file pressing [Esc] and typing :x! and press [Enter].
c) Stop all the Alcatel application which are running.
d) Stop HPOV:
..,sys,root # $OV_BIN/ovstop ,and press [Enter]
e) Start HPOV:
..,sys,root # $OV_BIN/ovstart ,and press [Enter]
On the console will appear a message as the following:

HP OpenView DM: license type is DEMONSTRATION.
This license expires on <date>
HP OpenView DM: license type is PERMAMENT

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 205 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
206 / 318
10 1354RM UPGRADE TO NR5.0B PATCH LEVEL 1
This chapter shown how to proceed in the 1354RM 5.2B upgrade to Patch Level 1.
The procedure require to shutdown the application to be able to change the software, becuse of this all
the activities on the systems have to be stoped and all the user have to logout.
10.1 Bootable Upgrade
Refer to chapter 5 Bootable Upgrade at page 117.
10.2 1354RM Upgrade Procedure
10.2.1 Backup database
Meaningful for IM
Execute the backup of the database (Network and PM). Refer to the RM Operator Handbook [1].
10.2.2 Install the new patches
a) To install the new patches:
Meaningful for both IM and USM
In the following you can find the procedure to install the 1354RM patch provided with the 1354RM
R5.2. This patch have to be installed only if the related delivery has been already installed.
The following procedure must be performed by root user.
Close all application windows, shutdown the 1354RM (only on IM):

If you have an open session with HP CDE presentation open, exit end login again as root.
If you dont have already mounted the CDROM, mount it with the following command:

Change current directory to the snml installation root and extract patched file from 1354RM patch
package:

If the output of pwd command is not /alcatel/1354RM52 execute the previous cd command before
proceed.
N.B. After the patch installation it is necessary to verify the contents of the /usr/snml/conf/
1AA 00014 0004 (9007) A4 ALICE 04.10
im_host_conf file, (please refers to the paragraph 11.1).
b) To install the Fix14 refer to paragraph 9.2.2.6 at page 179.

c) To install the Fix16 refer to paragraph 9.2.2.7 at page 180.
ED 02
957.130.892 W 3AL 61261 AA AA 207 / 318
318
10.2.3 Install the new AS package
a) First of all remove the old installation. Refer to paragraph 11.12.3 at page 224.

b) Install the new package. Refer to paragraph 9.3 at page 181.

10.2.4 Install the new SMF package
a) First of all remove the old installation. Refer to paragraph 11.15 at page 228.
b) Install the new package. Refer to paragraph 9.4 at page 183.
10.2.5 Install the NAV package
Refer to paragraph 9.5 at page 185.
10.2.6 Install the new SEC package
N.B. If you are upgrading a RM with the SH plugin or in cohosted configuration, stop the SH securi-
ty as explained in the note of the paragraph 11.14.3 and restart it only after the installation of
the new RM security package as explained in paragraph 9.6.
a) First of all remove the old installation. Refer to paragraph 11.14.3 at page 227.
b) Upgrade 1353SH and 1353SH_RMplug software (Refer to 1353SH Installation Guide [7] chapter
SH Software Upgrade and RM integration)
c) Install the new package. Refer to paragraph 9.6 at page 186.
N.B. Remember to install the new SEC package in an empty directory, because the procedure
checks that the chosen target directory is empty, otherwise it returns an error.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 208 / 318
318
10.2.7 Post Upgrade steps
10.2.7.1 Upgrase 1354RM Database

Execute the actions shown in the following paragraph:

Increase the shared pool size parameter 9.7.2 page 189.

Database Reset for 1354RM for Patch FIX16 9.7.3 page 190.
Create ORACLE User for Archive purpose 9.7.6 page 192.
Then execute the following actions:
Login as root user:

10.2.7.2 Increase the Allowed EML ID Value
The 1353SH/1354RM integration procedure provided with NR5.0B and PL1 allow to integrate 1353SH
Element Managers with EML ID in the range 0 to 999, to override this limit you have to change with vi
the line 61 of the following files: /usr/snml/bin/AddEML and /usr/snml/bin/RemEML.
From:
[ $eml_id lt 0 o $eml_id gt 999 ] && errorexit eml_id must be into [0999] range
to:
[ $eml_id lt 0 o $eml_id gt 9999 ] && errorexit eml_id must be into [09999] range
10.2.7.3 Restore database
Execute the restore of the database (Network and PM). Refer to the RM Operator Handbook [1].
Login as snml on 1354RM IM:
First of all verify that the system is down and the database is up. Then execute the following commands:
..,$ cd /alcatel/1354RM52/databases/dbsnml/admin.conv ,and press [Enter]

..,$ sqlplus $NXNL_DATABASE @set_all_sequences_to_max.sql.wrapper ,and press [Enter]
Logout snml user and login as root user:
..,sys,root # /usr/snml/etc/update_SH_domain ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 209 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
210 / 318
11 ADMINISTRATION
In this chapter you will find some useful procedure for the system administration.
11.1 Remote Event Sieve configuration
Login as snml.
This configuration is based on a configuration file (/usr/snml/conf/im_host_conf), where host names of

machine are described giving also their product supported (EML, AS or RM). This file is automatically used
by applications to create Remote Event Sieve in order to enable sending events only on machines really
involved in the event handling.
The file is update in automatic way by the RM and AS installation procedures. When a new EMLs
workstation is installed the following procedure has to be executed to update the configuration file:
..,$ /usr/snml/etc/update_nml_sieve ,and press [Enter]
N.B. WX host name must be removed manually from im_host_conf file, since no Event Forwarding
Discriminator shall be created on WX.
11.2 Database Schema Creation
Meaningful for IM configuration only
In order to create a new database the following procedure shall be executed:
Login as snml.
Shutdown the RM application. Then execute the following command:
..,$ $DB_ROOT/etc/create_db ,and press [Enter]
After the database recreation you can perform a restore of network configuration, alarms and PM data
from a backup (if any).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 211 / 318
318
11.3 Database extension
Oracle uses preallocated and not extendible tablespaces, so it could happen that some RM functions
fails and in trace files could be found messages as the following:

Message: ORA01653: unable to extend table SNML. <TP> by 512 in tablespace DATA
N.B. <TP> is the name of the table where the error arises, messages with different table name can
be found.
It is strongly recommended to execute a backup and then a restore on the RM database.
To solve this problem, the tablespace must be extended using the following procedure (as snml):
..,$ export ORACLE_SID=dbsnml ,and press [Enter]
..,$ $ORACLE_HOME/bin/sqlplus system/manager ,and press [Enter]
SQL> select * from dba_data_files; ,and press [Enter]

FILE_NAME

FILE_ID TABLESPACE_NAME BYTES BLOCKS STATUS

/usr/snml/databases/dbsnml/data/system01.dbf
1 SYSTEM 15728640 7680 AVAILABLE
/usr/snml/databases/dbsnml/data/rbs01.dbf
2 RBS 15728640 7680 AVAILABLE
/usr/snml/databases/dbsnml/data/temp01.dbf
3 TEMP 10485760 5120 AVAILABLE
FILE_NAME

FILE_ID TABLESPACE_NAME BYTES BLOCKS STATUS

/usr/snml/databases/dbsnml/data/data01.dbf
4 DATA 31457280 15360 AVAILABLE
/usr/snml/databases/dbsnml/data/index01.dbf
5 INDEX_T 10485760 5120 AVAILABLE
SQL> alter tablespace data add datafile /usr/snml/database/dbsnml/data/data02.dbf size

30M; ,and press [Enter]
SQL> quit; ,and press [Enter]
..,sys,root # chmod g+w /usr/snml/database/dbsnml/data/data02.dbf ,and press [Enter]
N.B. In the previous sqlplus session, a new datafiles for the tablespace data was created
(/usr/snml/databases/dbsnml/data/data02.dbf). It is recommended to create a new datafile with
the same size of the previous case.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 212 / 318
318
11.4 Oracle processes number extension
If you have to increase the size of the max number of oracle processes you must to execute the following
procedure:
a) Be sure that the RM system and the database are off;
b) Force the ORACLE modify processes parameter:
1) Login as snml and shutdown the database and the system (if running):

2) Login again as root and edit the /usr/snml/databases/dbsnml/admin/pfile/init1.ora file:
Type /processes and change the value of the line not commented of processes parameter.
3) Repeat point 2 ) for the file /usr/snml/databases/dbsnml/admin/pfile/init1_make.ora.
c) Restart the database and RM system.
Login as snml and startup the database:
If it starts with no problems youre ok. You can restart also the system:

Otherwise, this means that the oracle processes need more resources by the UNIX kernel that are
not available. In this case you have to increase the kernel resources for oracle processes:
1) Login as root and activate the sam utility:
2) Increase the semmnu and semmns parameters by the same number (see 11.6).
N.B. The value has to be enlarged at least by the number of tfeps processes you have
configured on RM.
3) Whel the reboot is finished, restat the database and the system

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 213 / 318
318
11.5 Object Registration

In the directory $NXNL_PRD/lrf are present the local registration files, used by the installation procedure

to register the objects managed by agent process. A lrf file exists for each agent and has the same agent
name with the .lrf tag.
In directory /usr/snml/etc are present two procedures: addobj and delobj. These procedures have to be
executed with root user privileges and register and deregister all the 1354RM local registration files.
11.6 How to modify a kernel parameter
If you have to modify the value of a kernel parameter you must to execute the following procedure:
a) Login as root and activate the sam utility:
b) Select Kernel Configuration.
c) Select Configurable Parameters, select the parameter, then select the menu Actions then Modify
Configurable Parameter and modify the parameter (one or more) with the needed value.
d) Select Action menu, click on Create a New Kernel (Process New Kernel on hpux 11.00) and
confirm the action clicking on Yes button in the displayed window.
e) At the next window, Reboot the system click on the [OK] button.
f) At the next window, Note click on the [OK] button.
g) Now the system will reboot the machine automatically.
11.7 Root User password
To guarantee the OS integrity it is important to forbid not agreed expert people the access as superuser
so it recommended to change the password for root to keep the confidentiality of access right.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 214 / 318
318
11.8 Date&Time
If date or time must be changed on a multi stations OS, it is recommended to use the script axhpuxconf
already launched during installation. The script initializes and distributes on all the stations time zone, date
and time.
On the Master station, logged in as root :
..,sys,root # axhpuxconf ,and press [Enter]

Follow the script (for more details refer to Chapter 6 SYSTEM CONFIGURATION)
...
To synchronize on all the stations
Changing the time could be also assumed using only the unix command date on the master station, and
after a short delay a few minutes the xntp daemon synchronizes the other stations.
..,sys,root # date <mmddhhmm> ,and press [Enter]
..,sys,root # exit ,and press [Enter]
The desktop will be updated after logout (Exit) then login again as root.
Note that the correspondence with the Universal Time is given with the command date :
..,sys,root # date ,and press [Enter] > Local time
..,sys,root # date u ,and press [Enter] > UTC time
N.B. You can give these commands also as any other user.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 215 / 318
318
11.9 Change IP addresses
The IP address have been declared while installing the bootable CDROM (Network Information).
Nevertheless it is possible to change it by modifying the suitable files and doing some configurations.

This procedure is applicable if the current TCP/IP address and the new one are in the
same TCP/IP subnetwork, or there is a router that allows the communication between the
current and the new subnetwork.
11.9.1 Change IP address on the IM machine
a) Login as administrator (snml) on the RM IM and stop the RM application.
b) Login as root on the RM IM and remove the RM agent registration:
Remove the RM agent :

..,sys,root # /usr/snml/etc/delobj ,and press [Enter]
Remove the AS agent :

..,sys,root # /usr/snml/etc/delobj_A1330 ,and press [Enter]
c) If you have any SH IM in your network:
Login on each of them as administrator (axadmin) and stop them using the Process Monitoring
tool.
On the SH IM remove the RM via axinitwsGui.
d) On the RM IM station log on as root.
Modify the IP address in the files /etc/hosts and /etc/rc.config.d/netconf:

..,sys,root # vi /etc/hosts ,and press [Enter]
Modify the information
Save and quit with :x! and press [Enter]
..,sys,root # vi /etc/rc.config.d/netconf ,and press [Enter]

Modify the field IP_ADDRESS[0]=nnn.eee.ttt.xxx
Modify the field SUBNET_MASK[0] with a compliant value (ONLY IF NECESSARY)
Modify the field ROUTE_GATEWAY[0]=nnn.eee.ttt.yyy with the new network
address nnn.eee.ttt (ONLY IF NECESSARY)
Save and quit with :x! and press [Enter]
Reboot the machine:

e) If you have any RM USM in your network:
Modify manually (as root) the IP address of the Master in the /etc/hosts file of every USM
machines:
save and quit with :x! and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
Reregister the HPOV agent :

..,sys,root # /usr/snml/etc/addobj ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 216 / 318
318
Reregister the AS agent :
..,sys,root # /usr/snml/etc/addobj_A1330 ,and press [Enter]
Reboot the workstation:


f) After the reboot, login the RM IM station as root:
Check the accessibility from the master towards each station using the ping command:
..,sys,root # ping <hostname_station> ,and press [Enter]
Reconfigure OTS Lite:

..,sys,root # axotsconf ,and press [Enter]
N.B. After the axotsconf, all the stations will be rebooted !
Reconfigure HPOV:
..,sys,root # $OV_BIN/create_paddr ,and press [Enter]
Check the contents of the $OV_CONF/local_p_addr file, it MUST be in the following form:
ORS_CMIP
The first line shows the CI (Communication Infrastructure) Protocol that has to be
ORS_CMIP, the second MUST be the description for RFC 1006 protocol with a line that
has at the end the notation: 1006. The third line describes the OSI protocol with a line that
has at the end the notation: CLNS. If the second and the third line are in the opposite order
it is MANDATORY to swap them.
Execute the axhpovconf command:

..,sys,root # axhpovconf ,and press [Enter]
g) If in your network you have any SH:
Login as root on the SH Master and register the RM with the new address via axinitwsGui.
Shutdown the SH application and HP OpenView.
On each SH Master and EML remove all the HP OpenView EFD files present:
..,sys,root # cd $OV_STACKS/EFD.per ,and press [Enter]
Check the default directory is set to /etc/opt/OV/stacks/EFD.per:
Remove the files:
..,sys,root # rm * ,and press [Enter]
h) On the RM IM reregister the agents:


1AA 00014 0004 (9007) A4 ALICE 04.10
Reboot the machine:

ED 02
957.130.892 W 3AL 61261 AA AA 217 / 318
318
i) On the master station logged on as OS administrator:
Start the network:

Open the TMN OSs menu

Select Global Actions and then Network Start.
Confirm the action at the next window with Yes.
11.9.2 Change IP address on the RM USM workstation
a) Remove any SH Clusters from the RM IM as explained in 1353SH Installation Guide [7] on page 12,
Chapter RM Integration Configuration in order to reconfigure the network.
b) Remove the RMUSM with old ip address from any SH Clusters executing axinitwsGui on each SH
Master.
c) On the RM USM remove the HP OpenView agent registrations:
Remove the AS agent :

Remove the HPOV agent :

d) On the RM USM station log in as root user.
Modify the IP address in the files:

..,sys,root # vi /etc/rc.config.d/netconf ,and press [Enter]

Modify the information in field IP_ADDRESS[0]=nnn.eee.ttt.xxx
If necessary modify the information in field SUBNET_MASK[0] with a compliant value
In field ROUTE_GATEWAY[0]=nnn.eee.ttt.yyy update with the new network address
nnn.eee.ttt
Reboot the workstation:

e) On the RM IM station log in as root user.
Register the USM with the new address via axinitwsGui as shown in Add the workstation to
existing configuration section 11.20.1.
Reconfigure the USM:

..,sys,root # axotsconf v w <USM_node_name> ,and press [Enter]
The station reboots.

1AA 00014 0004 (9007) A4 ALICE 04.10
..,sys,root # axhpovconf v w <USM_node_name> ,and press [Enter]

..,sys,root # axmailconf ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 218 / 318
318
f) On the RM USM reregister the agents:


g) Add the RMUSM with new ip address from any SH Clusters executing axinitwsGui on each SH
Master.
h) Add again the SH Clusters previously removed from the RM IM as explained in 1353SH Installation
Guide [7] on page 12, Chapter RM Integration Configuration in order to reconfigure the
network.
Now the workstation is ready to work.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 219 / 318
318
11.10 Install Optional Software
If you need to install a new package at the end of the installation, you can perform this procedure:

Some packages can require the reboot of the system, it is advisable to shutdown the application

and database before proceed.
Login as root.
If you dont have already mounted the CDROM, insert the bootable distribution medium into the driver and
download the kit with the following commands:
For 700 serie or 32bit systems:

# cpio id < /SD_CDROM/<bootable_name>BLOCK01 ,and press [Enter]
For 800 serie or 64bit systems:

# cpio id < /SD_CDROM/<bootable_name>BLOCK01 ,and press [Enter]
Where <cdrom device file> is the cdrom device file found in the paragraph 4.2.4.1.
Where <bootable_name> is:

C742C17d_TSD for the 700 series with HPUX 10.20
C842C17d_TSD for the 800 series with HPUX 10.20
C342C20e_TSD for the 32bit machines with HPUX 11.00
C642C20e_TSD for the 64bit machines with HPUX 11.00
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 220 / 318
318
11.10.1 Run the installation script
To start the installation execute the following command:

..,sys,root # etc/install10 ,and press [Enter]

Workstation Type:

RMSH3M RMSH3P RMSH3S SH3E SH3M SH3P SH3S VPNM VPNS) : <WS_type> ,and press
[Enter]
You have to respect the choice made during the installation.
According to the type of station some optional softwares are proposed. Choose the software that you need.
For more explanations please refer to the paragraph 4.2.6 Optional software allocations.

The procedure will install only the software that you have chosen.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. The following software perform the automatic system reboot: 100B, 100VG and
OTS9000. The system can execute up to two reboots for each software.
ED 02
957.130.892 W 3AL 61261 AA AA 221 / 318
318
11.10.2 Confirm



^
|
Before to start the installation, the system asks you the confirm of your choice:
If the package required a system reboot, the procedure will do it automatically.
11.10.3 Optional Software Additional Actions
The following software require additional actions after the installation:
Mirror Disk/UX software installation requires the reinstallation of the HP patches: PHCO_14378,
PHCO_14598 and PHCO_17389.
These patches are available on the bootable medium C842C17D_TSD as block 20

(C842C17D_TSDBLOCK20).
To reinstall then you have to shutdown the application, and then enter the following commands:

..,sys,root # gunzip c /SD_CROM/C842C17d_TSDBLOCK20 > hppatch.sd ,and press [Enter]
..,sys,root# swinstall x reinstall=true s hppatch.sd PHCO_14378 PHCO_14598 PHCO_17389
,and press [Enter]
..,sys,root # rm hppatch.sd ,and press [Enter]
11.10.4 Remove the Installation Procedure
When the software installation has been completed, it is possible to remove the installation procedure login
the system as root user and entering the commands:
..,sys,root # cd /tmp/etc ,and press [Enter]

..,sys,root # rm * ,and press [Enter]
..,sys,root # cd /tmp ,and press [Enter]
..,sys,root # rmdir etc ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 222 / 318
318
11.11 Set the Swedish language
11.11.1 Swedish chars on the keyboard

In order to enable the swedish chars on the keyboard you have to execute the following operations:
a) Login as root and modify, using a vi command, the file /etc/kbdlang according to the type of the
swedish keyboard:
from:
PS2_DIN_US_English
to:
PS2_DIN_Swedish
b) Login as snml and execute the following commands:
..,$ cd $XAPPLRESDIR/C/include ,and press [Enter]

..,$ cp NLguiCommon NLguiCommon_english ,and press [Enter]
..,$ cp NLguiCommon_latin1 NLguiCommon ,and press [Enter]
..,$ cp NLfont NLfont_english ,and press [Enter]
..,$ cp NLfont_latin1 NLfont ,and press [Enter]
..,$ cp NLmatrix NLmatrix_english ,and press [Enter]
..,$ cp NLmatrix_latin1 NLmatrix ,and press [Enter]
The change will be taken into account after a reboot.
11.11.2 Swedish language for AS
In order to let ASUSM Components manage alarms containing swedish chars in the right way login as
snml and execute the following commands:
..,$ cd /usr/snml/conf ,and press [Enter]

..,$ cp AS_graphicResources AS_graphicResources_english ,and press [Enter]
..,$ cp AS_graphicResources_sv_SE AS_graphicResources ,and press [Enter]
Now all the following start of ASUSM Components will be able to manage swedish chars using roman8
fonts.
In order to roll back the configuration to default one (ASUSM displaying alarms in english) login as snml
..,$ cd /usr/snml/conf ,and press [Enter]

..,$ cp AS_graphicResources_english AS_graphicResources ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 223 / 318
318
11.12 A1330AS Management
11.12.1 1330AS Processes registration and removal

If you need to register or deregister all the 1330AS process, the following commands should be executed:
11.12.2 1330AS Maintenance
1330AS subsystem is provided with a maintenance tool, just only on the IM installation, that scratches the
database of the historical alarms.
This tool is activated from root executing the following command:
..,sys,root # /usr/snml/etc/reset_ovlog_A1330 ,and press [Enter]
This procedure is useful if the historical alarms database is very old and full of not interesting alarms; the
database scratch can be useful to widely reduce the time spent in the alarms retrieval from it.
11.12.3 Deinstalling 1330 AS
In order to remove an AS installation the following procedure is available:
..,sys,root # /usr/snml/etc/deinstall_A1330 IM ,and press [Enter]
NOTE: stopping A1330 IM processes ...

NOTE: Deregistrating A1330 agents on HPOV CI ...
NOTE: Removing old installation ...
NOTE: Reading version configuration file
NOTE: Deinstalling AS 5.1.1 product ...
NOTE: Deinstalling AS_TOOLS 5.1.1 product ...
NOTE: Removing link /usr/A1330 to /alcatel/ALARM3.1 area ...
NOTE: Updating snml sieve file ...
NOTE: Updating network configuration files
NOTE: procedure terminated with success
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 224 / 318
318
11.13 NAV Management
11.13.1 Deinstalling NAV

In order to remove an NAV installation the following procedure is available:
Login as root user.
..,sys,root> /usr/snml/etc/deinstall_NAV ,and press [Enter]
NOTE: Unconfiguring NAV default instance (0)

NOTE: Removing old installation ...
NOTE: Deinstalling FWKRunTime 5.0.2 product ...
NOTE: Removing link /usr/nav to /alcatel/NAV50 area ...
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 225 / 318
318
11.14 SEC Management
11.14.1 SEC Administration

SEC Subsystem is provided with a default customization for which on a RM is automatically configured
to run secim process if RMIM and lss process for each kind of RM (IM/US).
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>, where

<NTWDOMAIN> is the value assigned to the NTWDOMAIN configuration variable (see 9.2.1.4).
In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.
The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is inserted
1 line for each permanent SEC process. This line invokes the script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on runlevel
4 that is the 1354RM runlevel default. No checks are performed on the 1354RM effective runlevel (it
is supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator
Informations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.
If some problems occurs during SMF>Operator Administration and SEC DB is not updated on changes
executed on RM, it is possible to launch the script as snml user through the SMF:
...$ /usr/sec/integration/script/alignsecdb ,and press [Enter]
This procedure starts from the last well finished SEC commands and alignes the SEC DB to the actual
RM Security definitions.
If at login time the user receives a Message Box saying:
Security for 1354RM_<NTWDOMAIN> is not activated. Please contact your System Administrator
the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been stopped
(Restore proc.) or internal error.
N.B. If the Message does not include the string 1354RM, this means that it belongs to the SEC
installed for SH.
SEC 5.0 doesnt manage the scheduling time. This means that if an user has a scheduled rule
this rule is applied everytime. This limitation is not due to the integration level but to the fact that
SEC 5.0 doesnt support it.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 226 / 318
318
11.14.2 Alarm Access Configuration
Even if SEC has to be not installed on top of 1354RM, in order to be able to use AS is necessary to change
the following files:
/usr/A1330/data/ascurusm_<hostname><NTWDOMAIN>/param.cfg
/usr/A1330/data/ashistusm_<hostname><NTWDOMAIN>/param.cfg
/usr/A1330/data/ashistusm_<hostname>_rec<NTWDOMAIN>/param.cfg
where <hostname> is the name of the current machine and <NTWDOMAIN> is the value assigned
to the NTWDOMAIN configuration variable (see 9.2.1.4).
Everyone of the indicated files have to be modified as follow (as snml):
..,$ vi <filename> ,and press [Enter]
and change the following line from:
SEC_ENABLED True
to:
SEC_ENABLED False
11.14.3 SEC Deinstallation
N.B. Due to SEC installation limitation during this procedure all the installed SEC subsystems have
to be stopped. If SEC on top of 1353SH installation is installed run the script
/usr/1353sh/install/script/stop_security.sh.
In order to remove SEC installation the following procedure is available (as root):
..,sys,root # /usr/snml/etc/deinstall_SEC ,and press [Enter]
The procedure executes the following steps:
a) it stops all the SEC processes running on the host (only related to RM installation);
b) it removes the system configurations related to SEC;
c) it removes the /usr/sec link;
d) it removes all the files related to the SEC installation.
N.B. After the deinstallation all the other SEC subsystems installed have to be restarted at hand
executing the script /usr/1353sh/install/script/start_security.sh.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 227 / 318
318
11.15 SMF deinstallation
N.B. It is strongly recommended to avoid the manual removal of the SMF installation subtree. If such
a kind of operation has been done, refer to the paragraph 14.8 to recover the environment

integrity.

The following are the steps to perform the SMF installation removal.
Log in as root user.
Launch the swremove procedure:
..,sys,root # swremove SMF ,and press [Enter]
11.16 How to verify if a software is installed
If you need to verify if a software is installed or not on your system, follow these steps:
Login on your machine as root an execute the command:
..,sys,root # swlist l fileset <fileset_name> ,and press [Enter]
If the software is installed, the system will show you an output like in the following example:
tlvhhv,sys,root > swlist l fileset PHSS_15795

# Initializing...
# Contacting target tlvhhv...
#
# Target: tlvhhv:/
#
#PHSS_15795 B.10.00.00.AA CDE Runtime SEP 98 Cumulative Patch

PHSS_15795.CDEDTTERM B.10.00.00.AA CDE dtterm SEP 98 Patch
PHSS_15795.CDEENGAMAN B.10.00.00.AA CDE Man Page SEP 98 Patch
PHSS_15795.CDEENGAMSG B.10.00.00.AA CDE Msg C locale SEP 98 Patch
PHSS_15795.CDEHELPRUN B.10.00.00.AA CDE Runtime Help SEP 98 Patch
PHSS_15795.CDEMIN B.10.00.00.AA CDE Minimul Runtime SEP 98 Patch
PHSS_15795.CDEPAM B.10.00.00.AA CDE Pam SEP 98 Patch
PHSS_15795.CDERUN B.10.00.00.AA CDE Runtime SEP 98 Patch
PHSS_15795.CDESHLIBS B.10.00.00.AA CDE Shared Library SEP 98 Patch
PHSS_15795.CDETT B.10.00.00.AA CDE ToolTalk SEP 98 Patch
If the software is not installed, the system will show you an output like in the following example:
tlvhhv,sys,root > swlist l fileset PHSS_15660

# Initializing...
# Contacting target tlvhhv...
WARNING: Software PHSS_15660 was not found on host tlvhhv:/
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 228 / 318
318
11.17 Configure the Iview printer
To enable the printer functionality in the RM help the Iview*printerConfig resource must be defined in
$XAPPLRESDIR/$LANG/Iview file. This resources is a semicolon separated list of comma separated
tuples giving printer network names.

Login as snml.
..,$ vi $XAPPLRESDIR/$LANG/Iview ,and press [Enter]
Type /printerConfig: and [Enter]:
! The Iview*postscriptDirectory must be enabled and specify the

directory
! containing PostScript print filtering support files so WorldView can
! produce PostScript output. The Iview*printerConfig resource is a
! semicolon separated list of comma separated tuples giving printer
network
! names (with optional descriptive text), their types, optional
spooling
! override string (of the form lp d%s %s) and extra Pl2PostScript
arguments.
Iview*postscriptDirectory: ps
!Iview*europeanPaper: False
!Iview*outlineFontType: 1
!Iview*printerConfig: <name>[ comment], <type>[, <spool string>
[, <extra Pl2PostScript args>]];
! for example,
!Iview*printerConfig: alw+, LaserWriter+; \
! alwj, Pl2PostScript, , R; \
! hplj75, LaserJet75; \
! hplj300, LaserJet300;
!
Iview*printerConfig: <printer_name>, <printer_model>;
Where:
<printer_name>: is the name of your printer
<printer_model>: you have to insert the model LaserJet300.
Insert a line (not commented) as the one in bold related to your printer.
To configure more then one printer, divided the description lines with \ (as in the example).
Save and quit the file pressing [Esc] and typing :x! and [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 229 / 318
318
11.18 Configure a printer after the 1354RM customization
If you want to add a printer after the 1354RM installation and configuration operations, you have to modify
the printer definition line in the file /alcatel/1354RM52/etc/env_snml_make using the following commands

(as root):

..,sys,root # vi /alcatel/1354RM52/etc/env_snml_make ,and press [Enter]
Type /PRINTER= and [Enter]. Modify the line as follow:
from:
PRINTER=
to:
PRINTER=<printer_name>
where <printer_name> is the new configured printer.
After this modification is necessary to update the 1354RM environment:
..,sys,root # /alcatel/1354RM52/etc/customize_patch ,and press [Enter]
11.19 RM Zoomin from NN Using RM USM
The 1354RM zoomin execute from 1354NN is usually performed running the required application on
1354RM Master system. If there are many 1354NN operators, this activity can overload the 1354RM
Master system.
In order to reduce the amount of activities on 1354RM Master it is possible to specify which 1354RM USM
of the same 1354RM cluster have to execute the zoomin application instead of the 1354RM Master.
The /usr/snml/conf/qnnDispMapping file contains the relationship between the 1354NN X Display require
the zoomin and the 1354RM USM that have to execute the application. To request this feature add one
line for each display that have to be served by 1354RM USM in the qnnDispMapping with the following
syntax:
<nn display> <1354RM USM hostname>
where:
nn display is the1354NN display identifier, using the X11 standard notation:
<hostname>:<display number>.<screen number>
1354RM USM hostname is the hostname of the 1354RM USM of the SAME 1354RM cluster
of the 1354RM Master.
Example of /usr/snml/conf/qnnDispMapping:
nnmst1:0.0 rmusm1
nnxt01:0.0 rmusm2
nnmst1:1.0 rmusm2
N.B. In case of 1354RM USM failure, the 1354RM zoomin will fail also.
N.B. If the 1354RM USM is removed from the configuration also the related line(s) have to be
removed from /usr/snml/conf/qnnDispMapping.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 230 / 318
318
11.20 Add a Presentation Workstation
The 1354RM Application allows to add a new 1354RM presentation to an existing 1354RM IM. The steps
to execute are the following:
Install the HPUX and the Third Party Software, see Chapter 3.
Add the workstation to existing configuration, see section 11.20.1 of this manual.
Run the kernel configuration script, see section 11.20.2 of this manual.
Synchronize the time on all the stations, see section 11.20.3 of this manual.
Run the application OSI stack configuration script, see section 11.20.4 of this manual.
Configure HPOV for the HPOV communications, see section 11.20.5 of this manual.
Run the mailer configuration script, see section 11.20.6 of this manual.
Run the printer configuration script, see section 11.20.7 of this manual.
Install the 1354RM as shown in Chapter 9 of this manual (included AS, SMF, SEC and the
postinstallation actions).
N.B. If you have to install the 1353SH Plugin on the new 1354RM presentation, after the last action
indicated in the previous list (installation of the 1354RM) you have to refer the Chapter RM
Integration in 1353SH Installation Guide [7].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 231 / 318
318
11.20.1 Add the workstation to existing configuration
This script enables to declare all the WS as components of a same installation for the TCP/IP
communication (file /etc/hosts within each station). It is essential that all the stations are connected on

lan0.

Log in as root on the master machine (password install10)
For each station enter the Name, IP address and Type, then click on the Add button.
N.B. Remember to add the machine also on all the SHs IM present in your network.
When you have finished click on Exit button to quit the window.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 232 / 318
318
11.20.2 Run the kernel configuration script
Log in again as root on the Master machine (password install10)

..,sys,root # axhpuxconf v w <workstation name> ,and press [Enter]

Where <workstation name> is the machine USM that you are installing.
This script initializes the time zone on the station.
Start : date and time...
*********************************************************
* AXHPUXCONF SCRIPT *
*********************************************************
Starting configuration of HPUX, please wait ......
kernelconf > Building the new kernel ...

Building a new kernel based on template file /stand/RMM.system
Compiling conf.c...
supported in future releases. The +vallcompatwarnings option can be used to
display more details, and the ld(1) man page contains additional
information. This warning can be suppressed with the +vnocompatwarnings
option.
* The current kernel at /stand/vmunix has been moved
to /stand/vmunix.prev.
* The newly built kernel has been moved to /stand/vmunix.
kernelconf > Moving /stand/system to /stand/system.prev ...
nfs configured with success!
kernelconf > The kernel has been successfully build !.
hpuxconf > Updating /etc/inittab file on tlvhhv
hpux configured with success
The http daemon server is configured on the master station.
11.20.3 Synchronize the time on all the stations
..,sys,root # axxntpconf v ,and press [Enter]

*********************************************************
*
* AXXNTPCONF SCRIPT *
*
*********************************************************
Starting configuration of xntp, please wait ......
1AA 00014 0004 (9007) A4 ALICE 04.10
xntp configured with success
ED 02
957.130.892 W 3AL 61261 AA AA 233 / 318
318
11.20.4 Run the application OSI stack configuration script

..,sys,root # axotsconf v w <workstation name> ,and press [Enter]

*******************************************
* AXOTSCONF SCRIPT *
* *
*******************************************
otsconf > updating configuration on tlvhhf
...
otsconf > Checking if file ots exists on tlvhhf
otsconf > Updating /etc/rc.config.d/ots
otsconf > Cleaning ifor conf
The stations reboot automatically at the end of the script.

About to reboot workstation(s) ... , continue [y|n] ? y ,and press [Enter]
N.B. Successively only the stations that you have add reboots. After the reboot you have to continue
the configuration on the Master station.
WARNING: before proceed check all the stations are running again before to continue.
11.20.5 Configure HPOV for the HPOV communications
..,sys,root # axhpovconf v w <workstation name> ,and press [Enter]
This script clears the old HPOV objects, initializes the new one using the OSI configuration, configures
the stations as Master or Slave and declares the slaves as trusted hosts.
WARNING : reconfiguring the stations using RFC1006

*********************************************************
*
* AXHPOVCONF SCRIPT *
*
*********************************************************
Starting configuration of HP openview, please wait ......
...
ovaddobj Static Registration Utility
hpovconf > updating configuration on tlvhhf
hpovconf > Check if OTS correctly configured on tlvhhf found
...
Successful Completion
...
HPOV configured and restarted with success
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 234 / 318
318
11.20.6 Run the mailer configuration script

..,sys,root # axmailconf v ,and press [Enter]

*********************************************************
*
* AXMAILCONF SCRIPT *
*
*********************************************************
mail configured with success
11.20.7 Align the printer configuration
In order to align the printer configuration of the new presentation to the master one it is necessary execute
the axprintconf script as shown in the next line:
..,sys,root # axprintconf align <workstation name> ,and press [Enter]
The system configuration is done.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 235 / 318
318
11.21 Remove a Presentation Workstation
The 1354RM Application allows to remove an existing 1354RM presentation from a 1354RM IM, just follow
these procedures:

Remove the HP OpenView agent registration, see section 11.21.1 of this manual.

Remove the workstation from configuration, see section 11.21.2 and 11.21.3 of this manual.
11.21.1 Remove the HP OpenView agent registration
To remove the HP OpenView registrations performed on 1354RM IM from the presentation it is necessary:
a) Log in as root on the 1354RM presentation workstation:
b) Remove static event forwarding discriminators:

Check if the file exists by entering:
...,sys,root # remsh <1354RM IM hostname> ls x $OV_STACKS/EFD.per [Enter]
If exists a file with the name of the 1354RM US sytem, remove it by entering:
..,sys,root # $OV_BIN/ovederegister h <1354RM IM hostname> ,and press [Enter]
c) Remove the RM agent:

11.21.2 Remove the workstation from configuration
This script allows to remove a WS as components of a same installation for the TCP/IP communication.
It is essential that all the stations are connected and running on lan0.
Log in as root on the master machine (password install10)

Select the 1354RM system that you want to remove, then click on the Remove button.
The system will be removed from the configuration of all the other systems.
When you have finished click on Exit button to quit the window.
11.21.3 Configure the network
If in your network is present a SH, is necessary to perform the following steps:

1AA 00014 0004 (9007) A4 ALICE 04.10
a) Remove the workstation also from the SH always via axinitwsGui.
b) Add again the SH to the RM IM as explained in 1353SH Installation Guide [7], Chapter RM
Integration SH/RM Configuration Steps in order to reconfigure the network.
ED 02
957.130.892 W 3AL 61261 AA AA 236 / 318
318
11.22 Full backup/restore disk on tape (using IgniteUX)
11.22.1 IgniteUX BACKUP

The IgniteUX backup is design to allow the stand alone backup of a system, in order to be able to recover
it in case of disk corruption and/or disk failure.
The IgniteUX backup procedure depends by the disk configuration, in fact the Alcatel TMN Application
foreseen two different Volume Group management:
1) Single Volume Group
2) Multiple Volume Group
With Single Volume Group all the physical devices are managed as a unique volume (vg00), in the Multiple
Volume Group the physical disks are assigned to different volume (vg00, vg01, etc.).
IgniteUX provides the feature to produce a recovery tape able to create the disk structure of vg00 and
restore on it a minimum HPUX environment. When the minimum HPUX is installed on the hard disk,
it allows to restore all the file system contents stored in a fbackup tape.
The IgniteUX recovery tape reinitialize all the disks belonging to vg00 but it does not change the con-
tents of the volume group different than vg00. Because of this the Multiple Volume Group Configurations
requires some more activities.
If you have a Multiple Volume Group configuration, such as 1354RM IM, before to start with the backup
operation you have to follow the action described in paragraph Retrieve Volume Group information
11.22.1.1 and Retrieve Logical Volume information 11.22.1.2 in order to save some informations which
will be used during the restore phase.
If you have a Single Volume Group configuration, such as 1354RM US, you can proceed with Mirror Spe-
cific Activities on Backup 11.22.1.3.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 237 / 318
318
11.22.1.1 Retrieve Volume Group information
To be able to perform the restore in case of disk failure you have to retrieve some informations about the
Volume Group defined in your configuration and store them in a form that have to be kept attached to the

backup tapes.

The the most important information have to be retrieve is the relationship among Volume Group and Physi-
cal Volumes, and among Volume Group and Logical Volumes. This data have to be retrieved by entering
the vgdisplay command and written in the Table 9. at page 241.
..,sys,root # vgdisplay v | grep i name ,and press [Enter]
The output will be like:
VG Name /dev/vg00
LV Name /dev/vg00/lvol1
.... Do not take into account vg00
PV Name /dev/dsk/c1t2d0
VG Name /dev/vg01 note 1
LV Name /dev/vg01/lvol1 note 2
PV Name /dev/dsk/c4t8d0 note 3
VG Name /dev/vg02
VG Name /dev/vg03
note 1: write the value in bold into the column Volume Group Name of Table 9. at page 241.
note 2: write the value in bold into the column Logical Volume Name of Table 9. at page 241.
note 3: write the value in bold into the column Physical Volume Name of Table 9. at page 241.
where for each Volume Group Name are shown the Logical Volume (LV Name) and the Physical Volumes
(PV Name). Record for each vg different than vg00 the logical volume and physical volume in the Table 9.
at page 241.
Other useful informations are related to the group file. The group file is a special file defined for each
Volume Group with specific characteristics known as Major and Minor number. The Major number is
always equal to 64, but the minor is always different. To retrieve the Minor number enter:
..,sys,root # ll /dev/vg*/group ,and press [Enter]
the system will gives you back an output like the following, where in bold characters are highlighted the
Minor numbers for each Volume Group:
crwr 1 root sys 64 0x000000 Jan 22 08:56 /dev/vg00/group
Write the Minor number of each volume group into column Minor Number of Table 9. at page 241.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 238 / 318
318
11.22.1.2 Retrieve Logical Volume information
The relevant informations about the Logical Volume are: size, mount point and file system type.
You have to fill in Table 10. at page 241 with size, mount point and file system type of each logical volume
not belonging to vg00.
The following command allow to retrieve the Logical Volume size:
..,sys,root # lvdisplay /dev/<vg name>/<lv name> | grep LV Size ,and press [Enter]
Where:
<vg name> means the volume group name shown in Table 9. at page 241
<lv name> means the logical volume name shown in Table 9. at page 241
Write <vg name> and <lv name> into columns Volume Group Name and Logical Volume Name of
Table 10. at page 241.
The list of the Volume Group and related Logical Volume has been filled in in Table 9. at page 241
The command output will be like:

LV Size (Mbytes) 512
Write the size into the column Size of Table 10. at page 241.
To retrieve the mount point and the file system type for all logical volume enter:
..,sys,root # grep v vg00 /etc/fstab ,and press [Enter]
/dev/vg01/lvol1 ... swap pri=1 0 0

/dev/vg01/lvol2 /mirror vxfs defaults 0 1
/dev/vg02/lvol1 /backup vxfs defaults 0 1
/dev/vg03/lvol1 /alcatel hfs defaults 0 1
note 2
note 1
note 1: write the value in bold into the column Mount Point of Table 10. at page 241.
note 2: mark file system type in bold into the column File System Type of Table 10. at page 241.
The first column shows the logical volume name; the second one the directory used as mount point or ...
for swap or swap/dump logical volume; the third column shows the file system type as hfs, vxfs or swap.
Record file system type for all logical volumes, and mount point for all hfs and vxfs file system types in the
Table 10. at page 241.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 239 / 318
318
11.22.1.3 Mirror Specific Activities on Backup
Ignite does not support mirror configuration, that means it is necessary to perform some additional actions
to be able to recovery a system when the mirror disk is present in the configuration. If you do not have the

mirror disk skip this paragraph.

To be able to create again the right configuration you have to take note on the tape label of the primary
and alternative boot disk. If the mirror have been configured as well as the primary and alternative boot
disks are set on the system boot parameter the boot configuration, that can be retrieved entering com-
mand:
..,sys,root # lvlnboot v ,and press [Enter]
That provides an output like the following:
Boot Definitions for Volume Group /dev/vg00:

Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t8d0 (8/12.8.0) Boot Disk
Boot: lvol1 on: /dev/dsk/c1t8d0
/dev/dsk/c0t12d0
Root: lvol3 on: /dev/dsk/c1t8d0
/dev/dsk/c0t12d0
Swap: lvol2 on: /dev/dsk/c1t8d0
/dev/dsk/c0t12d0
Dump: lvol2 on: /dev/dsk/c1t8d0, 0
Write on the cassette label both the line shown with Boot Disk.
If you have a Multi Volume Group configuration fill in also the Table 11. at page 241.
Doublecheck this information entering the following command to read:
..,sys,root # setboot ,and press [Enter]
The output of setboot command is like:
Primary bootpath : 8/12.8.0

Alternate bootpath : 8/8.12.0
Autoboot is ON (enabled)
Autosearch is ON (enabled)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 240 / 318
318
Table 9. Volume Group Data
Volume Group Name Logical Volume Name Physical Volume Name Minor Number
Table 10. Logical Volume Data
Volume Group Name Logical Volume Name Size Mount Point File System Type
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
-hfs -vxfs -swap
Table 11. Boot Disks
Primary Boot Disk & Path Alternative Boot Disk & Path
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 241 / 318
318
11.22.1.4 Perform the Backup
This paragraph shows how to perform the full backup of your system.

The backup procedure foreseens the system reboot and a downtime depending by the amount

of the data recorded on the disk and the tape driver used.
If you are working on a server, to be able to perform the backup you need to have a console or a
WEB Console and a PC.
a) Login as root.
b) Insert a writable tape into the DAT device.
c) When the LEDs DAT device are lighted permanently, create a bootable tape entering the following
commands:
..,sys,root # cd /opt/ignite/bin ,and press [Enter]

..,sys,root # ./make_recovery C v ,and press [Enter]
The recommended format for the tape label is:
<hostname> Ignite Bootable <date>
Example: admrm1 Ignite Bootable 21Jul1999
N.B. This tape has to be marked as boot tape for the machine used to produce it. It has
to be used only on that machine.
d) Remove the tape from the tape driver and reboot the system:
Before proceed with the shutdown is suggested to ask all the users to logout.
..,sys,root # cd / ,and press [Enter]
The next step MUST BE EXECUTED USING THE CONSOLE or THE WEB CONSOLE. Be
careful, check the availability of these tools before perform the shutdown.
..,sys,root # shutdown r now ,and press [Enter]
e) Wait till the following message will be shown on the console or web console:
Press [Enter] to interrupt the boot by console, and boot manually in single user mode:
Main menu> boot pri ,and press [Enter]
Interactive with IPL (Y,N o C) > y ,and press [Enter]
isl> hpux is ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. Please ignore the error messages referring file not found on /usr file system. These errors
are due to particular boot method, but are not relevant.
ED 02
957.130.892 W 3AL 61261 AA AA 242 / 318
318
f) Activate the Volume Group:
# vgchange a y ,and press [Enter]

g) Mount the file systems ignoring the Network File System unreachable error messages:
# mountall l ,and press [Enter]
h) Perform the backup.

Insert a new tape into the tape driver and execute the following command:
# fbackup 0i / f /dev/rmt/0m ,and press [Enter]
It is possible that fbackup asks to insert another tape issuing the message:
Enter yes when the volume 2 is ready on /dev/rmt/0m,

or no to discontinue:
In any case it is recommended to clear mark on the tape label which is the system name, how many
tapes have been produced and which is the order number.
Is recommended the notation:
<hostname> <order number>/<number of tape> <date>
Example: admrm1 1/3 21Jul1999

admrm1 2/3 21Jul1999
admrm1 3/3 21Jul1999
N.B. If at the end of the backup some error messages regards the .profile file will be
printed in console, please ignore them.
i) Reboot the system:
# reboot s ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 243 / 318
318
11.22.2 IgniteUX RESTORE
This paragraph shows how to recover a system in case of disk crash or file system damage, where the
HP machine is not able to boot in the proper way.

The restore destroy all the data present on the disk.
Before start, verify the tape set. If you do not have all the tape of the backup tape set the restore procedure
will fail.
a) Insert the Ignite Boot Tape previously produced by the machine.
b) When the LED of the tape device stops blinking, reboot the system, or turn off and on again the power
supply.
c) Interrupt the boot by console, and execute the following commands:
1) Find the id of the tape device, entering the search command:
2) Boot the system from tape entering the boot command:
Main Menu: Enter command or menu > boot P<n> ,and press [Enter]
where P<n> is the path number corresponding at the tape device.
3) The system asks you if you want to perform an interactive boot, reply as shown before:
Interactive with IPL (Y,N o C) > n ,and press [Enter]
d) Wait until the Ignite does not complete the HPUX recovery.
e) At the end of the recovery Ignite reboots the system. Wait till the following message will be shown
on the screen:
Press [Enter] to interrupt the boot by console, and boot manually in single user mode:
Main menu> boot pri ,and press [Enter]
Interactive with IPL (Y,N o C) > y ,and press [Enter]
isl> hpux is ,and press [Enter]
N.B. Please ignore the error messages referring file not found on /usr file system. These errors
are due to particular boot method, but are not relevant.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 244 / 318
318
f) Check for the presence of the disks and install the related special files using the command
# ioscan fnCdisk ,and press [Enter]


=================================================================
disk 0 8/12.12.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
disk 1 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVDROM 3
disk 2 8/16/5.5.0 sdisk CLAIMED DEVICE SEAGATE ST39175LW
disk 3 8/16/5.6.0 sdisk CLAIMED DEVICE SEAGATE ST39175LW
disk 4 10/12.8.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
g) Remove Volume Group definition by enter the following command for each different volume group
described in Table 9. at page 241:
# vgexport <vg name> ,and press [Enter]

Where: vg name means the name shown in the column Volume Group Name ( ex: vg01).
h) Create the physical volume by enter the following command for each different physical volumes
described in Table 9. column Physical Volume Name at page 241:
# pvcreate f /dev/rdsk/<pv name> ,and press [Enter]

Where: pv name means the device file name of the Physical Volume.
(ex: if the Physical Volume name is /dev/dsk/c0t4d0 the device file name
is c0t4d0)
i) Create of Volume Group by enter the following set of command for each different volume groups de-
scribed in Table 9. at page 241:
# mkdir /dev/<vg name> ,and press [Enter]

# mknod /dev/<vg name>/group c 64 <minor num.> ,and press [Enter]
# vgcreate f /dev/<vg name> /dev/dsk/<pv name> ,and press [Enter]
Where:
<vg name> means the name shown by column Volume Group Name of Table 9. ( ex: vg01)
<minor num.> means the value shown by column Minor Number of Table 9.
<pv name> means the name shown by column Physical Volume Name of Table 9.
j) Then you have to create the logical volumes belonging to the Volume Group created a point ( i ), by
entering the following commands:Table 10.
# lvcreate n <lv name> L <lv size> <vg name> ,and press [Enter]
where:
<lv name> means the logical volume name shown in Table 10. at page 241.
<lv size> means the size related to logical volume in Table 10.
<vg name> means the volume group related to the logical volume shown in Table 10. with
/dev/ as prefix (ex: /dev/vg01)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 245 / 318
318
k) Create the file system in the logical volumes. For each logical volume shown in Table 10. is also show
the file system type as: hfs, vxfs or swap. Do not take into account the logical volume marked
as swap, and create a file system on the logical volumes hfs or vxfs by entering the one of following
command:

1) For hfs file systems:
# newfs F hfs m 3 /dev/<vg name>/r<lv name> ,and press [Enter]
2) For vxfs file systems:

# newfs F vxfs o largefiles /dev/<vg name>/r<lv name> ,and press [Enter]
where:
<lv name> means the logical volume name shown in Table 10. at page 241.
<vg name> means the volume group related to the logical volume as shown in Table 10.
l) Create the file system mount point shown in Table 10. if they not exist by enter:
# mkdir <mount point> ,and press [Enter]

where:
<mount point> means the directory name shown in the column Mount Point of table Table 10.
N.B. Please ignore the error message mkdir: cannot create /alcatel: File exist
m ) Mount all file system and activate the auxiliary swap if any using the commands:
# swapon a ,and press [Enter]

# mountall l ,and press [Enter]
Do not take into account if mount command can issue message like:
mount: /dev/vg00/lvol1 is already mounted on /stand
n) Check if all the file systems shown in Table 10. are correctly manage by the HPUX by enter:
# bdf ,and press [Enter]

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 102400 35914 62379 37% /
/dev/vg00/lvol1 99669 41371 48331 46% /stand
/dev/vg00/lvol9 716800 181138 502223 27% /var
/dev/vg00/lvol8 819200 536036 265488 67% /usr
/dev/vg00/lvol6 53248 1820 48256 4% /users
/dev/vg00/lvol5 204800 11397 181584 6% /tmp
/dev/vg00/lvol4 1228800 1059304 158918 87% /opt
/dev/vg01/lvol2 5120000 3985 4796333 0% /mirror
/dev/vg00/lvol7 716800 2038 670136 0% /home
/dev/vg02/lvol1 8192000 740865 6985634 10% /backup
/dev/vg03/lvol1 8192000 4880508 3104549 61% /alcatel
The logical volume marked as hfs or vxfs in Table 10. must be present in the first column of the out-
put.
o) The last step of this prerecover procedure consists to check if all the logical volumes used as swap
shown in Table 10. are correctly manage by the HPUX by enter:
# swapinfo ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 246 / 318
318
The output wil be like:
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4198400 35300 4163100 1% 0 1 /dev/vg00/lvol2
dev 3072000 35796 3036204 1% 0 1 /dev/vg01/lvol1

reserve 392348 392348

memory 361492 187564 173928 52%
The swap logical volume show in Table 10. must be present in the last column of the output.
p) Create the graph file for the selective frecover with name /tmp/lvm_graph by enter:
# cat > /tmp/lvm_graph << EOF ,and press [Enter]

i/
e /dev
e /stand
e /etc/fstab
e /etc/lvmtab
e /etc/lvmconf
e /etc/ioconfig
e /usr/lib/uxbootlf
EOF
N.B. Double check the contents of the graph file.
q) Remove the IgniteUX bootable tape with the first tape produced by fbackup.
r) Start the recovery command by enter:
# frecover x o g /tmp/lvm_graph f /dev/rmt/0m ,and press [Enter]

Insert all tapes where the frecover requires them.
s) After the frecover it is necessary to review the special file created by Ignite by entering:
# insf e ,and press [Enter]
t) Change the right on /var/spool/sockets directory:
# chmod 777 /var/spool/sockets ,and press [Enter]
u) Reboot the system:
# reboot s ,and press [Enter]
v) If you have the mirror disk execute the specific actions shown in the paragraph 11.22.2.1.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 247 / 318
318
11.22.2.1 Mirror Specific Activities on Restore
After the restore of the Ignite recovery tape the Volume Group 00 is already created, but there is no alterna-
tive boot disk configured and the logical volume have no mirror copy.

First of all it is necessary to identify the alternative boot disk by entering the command:

..,sys,root # lvlnboot v ,and press [Enter]
That provides an output like the following:

Compare the output of the command with the data shown in Table 11. (at page 241) or on to the cassette
label to identify the missed boot disk (/dev/dsk/c0t12d0 in the example). Then remove the disk from the
volume group entering the command:
..,sys,root # vgreduce /dev/vg00 /dev/dsk/<disk file name> ,and press [Enter]
Where <disk file name> is the file in /dev/dsk or /dev/rdsk used by HPUX to access the specific disk.
For example, using the data shown in the backup section c0t12d0 so the command will be:
..,sys,root # vgreduce /dev/vg00 /dev/dsk/c0t12d0
Then create on it the boot area by entering the command:
..,sys,root # pvcreate Bf /dev/rdsk/<disk file name> ,and press [Enter]
Then add it again to the volume group by entering:
..,sys,root # vgextend /dev/vg00 /dev/dsk/<disk file name> ,and press [Enter]
Create and initiate the boot area by entering:
..,sys,root # mkboot /dev/rdsk/<disk file name> ,and press [Enter]

..,sys,root # mkboot a hpux lq (;0)/stand/vmunix /dev/dsk/<disk file name> ,and press
[Enter]
Then mirror all the logical volumes entering the command indicated in the paragraph 12.1.7.6.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 248 / 318
318
12 DISK MIRRORING
The disk mirror is a technology that allow to increase the availability of the disks, it provides the capability
to have two copies of the data stored on disk devices.
If the application software is already installed on the server, without follow the instruc-
tion shown in this chapter, the disk mirror should be not configurable.
12.1 Disk Mirror Configuration
The disk mirror is ONLY foreseen for installation on HP Server, it requires the double of disks normally
used, this allow to store the mirror copy of all the disk partitions and allow the system survival to a single
disk failure.
12.1.1 Hardware configuration
An important step in the disk mirror configuration is related to the disk rule definition. The disk set have
to be divided in two subsets: the main set and the mirror copy set. It is advisable divide the disks in order
to have the same amount of disk space for each subset.
The HP9000 server foreseen are the following models:

K Class (K370 and K380)
R Class (R380 and R390)
L Class (L1000 and L2000)
N Class (N4000)
In the following the foreseen configuration:
a) The server HP 9000/800 K Class can be provided in two different configurations:
1) with two different disk cabinets (HAS) and one CPU cabinet (see Figure 58. at page 250)
2) with one disk cabinet and one CPU cabinet (see Figure 60. at page 252)
b) The server HP 9000/800 R Class are provided with a disk cabinet (HAS) (see Figure 61. at page
253).
c) The server HP9000/800 L Class are provided without external disks (see Figure 63. page 254 ).
d) The server HP 9000/800 N Class are provided with a disk cabinet (SC10) (see Figure 65. at page
256).
In order to increase the availability is foreseen to connect each disk subset to different SCSI bus controller.
For this reason the CPU are equipped with two or more SCSI buses.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 249 / 318
318
12.1.1.1 HP9000 K Class
To guarantee the higher performance level is suggested to use the FWSCSI buses located on HSC board.

In the 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 both kind of server configurations:
a) In the first kind of server (with two disk cabinets) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS0. The connector 2 of the BusB is connected to the connector 2 of the BusA.
The connector 1 of the BusA is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusB in the HAS1. The connector 2 of the
BusB is connected to the connector 2 of the BusA. The connector 1 of the BusA is closed with a SCSI
terminator.
HSC
CPU FWSCSI 1 : FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS0
1 1
Bus B Bus A
2 2
HAS1
1 1
Bus B Bus A
2 2
Figure 58. Rear view of server with two disk cabinets
In this kind of configuration the mirroring has to be done as in the following: the main disks must be
on the HAS0 starting from the position 8 (using the 4.3Gbyte disk if any), and the copy disks must
1AA 00014 0004 (9007) A4 ALICE 04.10
be on the HAS1 in the same position. The configuration will be:
ED 02
957.130.892 W 3AL 61261 AA AA 250 / 318
318
If a DLT tape driver is present in this configuration, it is suggested to connect it to the HAS0 Bus A
connector 1. NOTE: Before connect the DLT tape to the SCSI bus check the SCSI ID switch placed
on the rear is set to value 3.
Main disks
disk cabinet #1
disk # 12 disk # 8
disk # 13 disk # 9
disk # 14 disk # 10
disk # 15 disk # 11
Copy disks
disk cabinet #2
disk # 12 disk # 8
disk # 13 disk # 9
disk # 14 disk # 10
disk # 15 disk # 11
Figure 59. Front view of two disk cabinets (HAS)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 251 / 318
318
b) In the second kind of server (with one disk cabinet) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS, and the connector 2 of the BusB is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusA and the connector 2 of the BusA is

closed with a SCSI terminator.

HSC
CPU FWSCSI 1
: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS
1 1
Bus B Bus A
2 2
Figure 60. Rear view of server with one disk cabinet
If a DLT tape driver is present in this configuration, it is suggested to connect it to the HAS Bus A
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 252 / 318
318
12.1.1.2 HP 9000 R Class
N.B. For the server R the recommended configuration of the HSC and Lan boards is indicated in
Figure 61. :
The HSC boards should be placed in position 1 and TURBO.

If you have a supplementary Lan board it should be placed in position 3.
CPU
: SCSI cable
FWSCSI 1
: SCSI terminator
FWSCSI 2
: FWSCSI connector
TURBO 3 2 1 0 HSC
HAS
1 1
Bus B Bus A
2 2
Figure 61. Rear view of server R with one disk cabinet
In this kind of configuration the mirroring has to be done as in the following: the main disks must be
on the BusB starting from the position 8 (with the 4.3Gbyte disk if any), and the copy disks must be
on the BusA in the same position, starting from the position 12. The configuration will be:
Copy disks Main disks

Bus A Bus B
disk cabinet #1
disk # 12 disk # 8
disk # 13 disk # 9
disk # 14 disk # 10
disk # 15 disk # 11
Figure 62. Front view of one disk cabinet (HAS)
If a DLT tape driver is present in this configuration, it is suggested to connect it to the HAS Bus A
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 253 / 318
318
12.1.1.3 HP9000 L Class
The HP9000 server L class are provided without any disk cabinet. The L server have all disk 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 rules in the
mirroring configuration and their hardware path (and device file names).
Copy disks
/0/0/2/0.0.0 /0/0/2/0.2.0
(c2t0d0) (c2t2d0)
DVD
/0/0/1/0.0.0 /0/0/1/0.2.0
(c1t0d0) (c1t2d0)
Main disks
Figure 63. Front view of L Server (without cover panel)

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 254 / 318
318
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 64. Rear view of L Server
If a DLT tape driver is present in this configuration, an extra SCSI adapter will be provided (A4800A). It
has be place in one of the slots: from 7 to 12. Then connect the connect the DLT tape driver via FWSCSI
68 pin cable.
N.B. Install the additional PCI cards starting from the top of PCI Slots.
N.B. Before connect the DLT tape to the SCSI bus check the SCSI ID switch placed on the rear is
set to value 3.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 255 / 318
318
12.1.1.4 HP9000 N Class
The HP9000 N Class server are provided 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) con-
nectors
: VHDCI SCSI cable I NOTE: Dip switchorientation is reverted

on the bottom controller
I I I I
: VHDCI SCSI terminator O : HD SCSI terminator
5 4 3 2 1 : HD SCSI cable 68pin
: VHDCI SCSI connector O
SC10
DAT DVD
N4000
12 6
11 The two internal 5
PCI Slots PCI Slots
10 disks are place 4
in this location
9 3
8 2
7 1
Figure 65. Rear view of N Server with SC10
N.B. The position of the components in the rack is not predictable, so the N4000 server can be placed
on top of SC10.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. It is advisable to install the PCI cards balancing them in the right and left slots, starting from the
bottom.
ED 02
957.130.892 W 3AL 61261 AA AA 256 / 318
318
Main disks Copy disks
Slot: 0 1 2 3 4 5 6 7 8 9
SCSI: 8 8 9 9 10 10 11 11 12 12
Figure 66. Front view of SC10
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: 4, 5, 6 , 10, 11 or 12. Then connect the connect the DLT tape driver via
FWSCSI 68 pin cable.
N.B. Before connect the DLT tape to the SCSI bus check the SCSI ID switch placed on the rear is
set to value 3.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 257 / 318
318
12.1.2 Verify the Hardware configuration
N.B. This verification it is not applicable for HP 9000 Server N Class because the external
disks are not recognized in console mode.

To verify the correct hardware configuration:
shut down the host and poweroff the disk cabinet;
remove the main disks from:

K Class with two HASs:
Upper disk cabinet;
K Class with one HAS and R Class:
the bus B on the right side of HAS by pulling out the module lever;
L Class:
Couple of disks in the lower slots;
N Class:
Do not remove any disk. For the N Class this action is not possible.
poweron the disk cabinet and restart the host;
interrupt the boot sequence, and type search at the Main Menu prompt.
You have to identify the disks that you want to use as copy, in the provided list:

P1 10/0.12.0 FWSCI.12.0 Random access media
P2 10/0.13.0 FWSCI.13.0 Random access media
if the disks are correct, shut down the host and poweroff the disk cabinet again;
insert the main disks and remove the copy disks from:
K Class with two HASs:
Lower disk cabinet;
K Class with one HAS and R Class:
the bus A on the left side of HAS by pulling out the module lever;
L Class:
Couple of disks in the upper slots;
N Class:
Do not remove any disk. For the N Class this action is not possible.
You have to identify the disks that you want to use as main, in the provided list:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 258 / 318
318

P1 10/4/4.8.0 FWSCI.8.0 Random access media

P2 10/4/4.9.0 FWSCI.9.0 Random access media
if the disks are correct, you can start the software installation as shown at Chapter ...
When the installation will be successfully completed proceed with
12.1.3 Verify the Hardware configuration for server N Class
To verify the correct hardware configuration of server N Class:
shut down the host and poweroff the disk cabinet;
You have to identify the disks that you want to use as copy, in the provided list:
P0 0/0/1/0.2 media.2 Random access media

P1 0/0/2/0.6 intscsia.6 Random access media
P2 0/0/2/1.6 intscsib.6 Random access media
The internal disks and CD/DVD rom will be shown. In fact the disks placed in the SC10 storage are
not available at the boot time;
Choose the hard disk will be the boot device taking into account that usually the hardware path on
the server N Class are:
0/0/1/0.2.0 DVD ROM (c0t2d0)
0/0/2/0.6.0 9 G byte hard disk (c1t6d0)
0/0/2/1.6.0 9 G byte hard disk (c2t6d0)
Remove the copy disks from the SC10 shown in the Figure 66. at page 257.
Start with the software installation as shown a Chapter ... tacking into account:
The boot disk MUST BE AN INTERNAL DISK.
Do not include both internal disks in the list of disk included in the installation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 259 / 318
318
12.1.4 Software installation
When the rule of all the disk is defined it is possible to proceed with the software installation as shown in
Chapter 3, using only the disks of the main set.

It is important to select the HPUXMirror Software during the optional software installation (see para-
graph 4.2.6 at page 60).
At the end of the installation shut down the server and poweroff the disk cabinet. Insert the copy disks,
previously removed, poweron the disk cabinet and restart the server.
12.1.5 Configure the mirror copy disks
Performing the installation of HPUX with switched off disks, does not allow the operating system to recog-
nize them, that means it did not create the appropriate device files.
To create the device files for the disks just powered on:
Login as root:
Enter the following commands:
..,sys,root # ioscan C disk ,and press [Enter]
..,sys,root # insf C disk ,and press [Enter]

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 260 / 318
318
12.1.6 How identify the disks
It is now necessary to identify which disk is used as boot disk within the main disk set, in order to know
its characteristics and be able to identify the disk in the copy disk set that has to be used as alternative
boot disk.
To scan your system configuration, execute the following command:
Start the sam utility with:
System Administration Manager (cntsvss) (1)
File View Options Actions Help

Press CTRLK for keyboard help.
SAM Areas
Source Area
SAM Accounts for Users and Groups > ^

SAM Auditing and Security >
SAM Backup and Recovery >
SAM Clusters >
SAM Disk and File Systems >
SAM Display >
Other ENWARE XStation Administration
Other HP Netstation Administration
SAM Kernel Configuration >
SAM Networking and Communications >
SAM Performance Monitors >
SAM Peripheral Devices >
SAM Printers and Plotters >
SAM Process Management > v
Figure 67. Sam
Moving on the menu with arrows, select Disk and File Systems and press [Enter].
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 261 / 318
318
System Administration Manager (cntsvss) (1)
File View Options Actions Help


SAM Areas:Disks and File Systems
Source Area
..(go up) ^
SAM Disk Devices
SAM File Systems
SAM Logical Volumes
SAM Swap
SAM Volume Groups
Figure 68. Disk and File Systems
Moving on the menu with arrows, select Disk Devices and press [Enter].
Disks and File Systems (cntsvss) (1)
File List View Options Actions Help

Disk Devices 1 of 5 selected
Hardware Number Volume Total

Path of Paths Use Group Mbytes Description
10/4/4.8.0 1 LVM vg00 4095 SEAGATE ST34572WC

^
10/4/4.9.0 1 LVM vg00 8683 SEAGATE ST19171N
10/12/5.2.0 1 Unused 0 Toshiba CDROM SCSI
10/0.13.0 1 Unused 8683 SEAGATE ST39173WC
10/0.12.0 1 Unused 4095 SEAGATE ST34572WC
v
< >
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 69. Disk Devices
It is necessary to fill in the following table with the data regarding the disk sets.
ED 02
957.130.892 W 3AL 61261 AA AA 262 / 318
318
To identify which disks are used in the main disk set, and be able to identify the disk in the copy disk set,
follow these procedure:
Table 12. Disks table

HW Path Block device file Char. device file Size Vg #

Main Boot
/dev/dsk/ /dev/rdsk/ vg00
disk
Copy Boot
/dev/dsk/ /dev/rdsk/ vg00
disk
Main data
/dev/dsk/ /dev/rdsk/
disk 1
Copy data
disk 1
Main data
disk 2
Copy data
disk 2
Main data
disk 3
Copy data
disk 3
Main Boot Disk:
a) Select the disk shown in the Disk Device list that has the vg00 in the Volume Group column,
by moving the cursor with arrow keys, and pressing [Spacebar].
b) Press [Tab] and [a] to open the Action menu.
c) Select the View more information option using arrow keys and press [Enter]. SAM will show
you the file system present on the disk.
d) If the / (root) partition is present, press [Enter] to activate the Show device files ... option
and identify the Device Files of the Main Boot disk. Use these information to fill in the columns Block
device file and Char. device file of Table 12.
Now press [o] key twice to go back at Disk and file Systems window of SAM, where you can
see the previously selected line and use the string shown in the Hardware Path column to fill in
the HW path column, and the Total Mbytes to fill in the Size one of Main boot disk row in
the Table 12.
When the data of the Main Boot disk are defined, fill in the table with the data of the Main data disks.
e) If there is no / (root) partition, press [o] key to go back to the previous window, deselect the current
disk by pressing [Spacebar]. Select the next disk of the volume group vg00, moving with arrow key
and pressing [Spacebar] key and repeat from the step b ).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 263 / 318
318
Main Data Disk:
The Main data disks are the used disks where there is no the / partition. To know the data of the Main data
disks use the SAM utility as for the Main Boot disk:

a) Select the disk shown in the Disk Device list skipping the Main Boot disk, by moving the cursor
with arrow keys, and pressing [Spacebar].
b) Press [Tab] and [a] to open the Action menu.
c) Select the View more information option using arrow keys and press [Enter]. SAM will show
you the file system present on the disk.
d) Press [Enter] to activate the Show device files ... option and identify the Device Files of the
Main data disk. Use these information to fill in the columns Block device file and Char. device file
of Table 12. of the Main data disk 1 row
Now press [o] key twice to go back at Disk and file Systems window of SAM, where you can
see the previously selected line and use the string shown in the Hardware Path Total
Mbytes and Volume Group columns to complete the Main data disk 1 row in the Table 12.
e) If there are other used disks, deselect the current disk by pressing [Spacebar] and repeat from the
step a ) selecting the next disk (not the Main Boot disk), moving with arrow key and pressing [Space-
bar] key, filling in the next Main data disk row available in Table 12.
When the data of the Main disks set are defined, fill in the table with the data of the Copy disks set.
Copy Disk Set:
a) Choose from theDisk and File System window an Unused disk with the same capacity
(Total Mbytes) of the Main Boot one (see Figure 69. ).
Fill in the Table 12. the HW Path and Total Mbytes columns of the Copy Boot disk row, with the
data of the selected disk.
b) Choose from Figure 69. an Unused disk with the same capacity (Total Mbytes) of the Main data
one. If there are more than one of data disk with the same capacity, select the Copy data disk 1 with
also the same description of the Main data disk 1 (if any).
Fill in the Table 12. the HW Path and Total Mbytes columns of the Copy data disk 1 row, with
the data of the selected disk. The Volume Group must be the same of the Main data disk 1.
c) If there are other unused disks, repeat the step b ) selecting the next disk, moving with arrow key and
pressing [Spacebar] key, filling in the next Copy data disk row available in Table 12.
d) Exit from SAM with [TAB] and [f] and selecting Exit option.
e) To know the Device File of the unused disk it is not possible to use the SAM utility. It is necessary
to use the following command:
..,sys,root # ioscan fn C disk ,and press [Enter]
In the report of this command it is possible to view the Device Files of the Copy disks set. Fill in the
Table 12. the Block device file and Char. device file columns of the Copy disks row selected be-
1AA 00014 0004 (9007) A4 ALICE 04.10
fore.
ED 02
957.130.892 W 3AL 61261 AA AA 264 / 318
318
12.1.7 Mirror Configuration
When the Alcatel Application Software has been installed on the main set, it is possible to proceed with
the Mirror configuration for the mirror copy disk set.
12.1.7.1 Create the Physical Volume
The first action is to create a bootable physical volume on the disk using the pvcreate command.
The physical volume on the Copy Boot disk that will be the mirror copy of the root disk have to be created
with:
..,sys,root # pvcreate Bf <Char. device file> ,and press [Enter]
where:
Char. device file: means the device special file of the disk, placed in the /dev/rdsk directory (see
Table 12. ).
The command will be:

..,sys,root # pvcreate Bf /dev/rdsk/cxtxdx
For the other disks you have to enter the same command without B option:
..,sys,root # pvcreate f <Char. device file> ,and press [Enter]

..,sys,root # pvcreate /dev/rdsk/cxtxdx
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 265 / 318
318
12.1.7.2 Extend the Volume Group
The 1354RM foreseen two different disk management.

For 1354RM IM it is foreseen the Multiple Volume Group disk management, that means when the HPUX

is installed a Volume Group is created for each physical disk.
For 1354RM US it is foreseen the Single Volume Group disk management, that means when the HPUX
is installed all the physical disk are placed in the Volume Group vg00.
12.1.7.2.1 Multiple Volume Group
In the 1354RM IM disk configuration there are at least two different volume groups, for this reason be care-
ful during the Volume Group Extension. Each volume group have to be extended with a disk having the
same size of the disk already present (see Table 12. ).
The command syntax to extend the Volume Group is:
..,sys,root # vgextend <volume group> <Block device file> ,and press [Enter]
Where:
volume group means the Volume Group name (ex: /dev/vg00)
Block device file means the device file of disk that have to be added to VG.
Examples:
..,sys,root # vgextend /dev/vg00 /dev/dsk/c0t12d0
12.1.7.2.2 Single Volume Group
In the 1354RM US disk configuration there is just one volume group, so all the copy disk have to be added
to the Volume Group vg00.
The command syntax to extend the Volume Group is:
..,sys,root # vgextend /dev/vg00 <Block device file> ,and press [Enter]
Where:
Block device file means the device file of disk that have to be added to vg00.
Examples:
..,sys,root # vgextend /dev/vg00 /dev/dsk/c0t12d0
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 266 / 318
318
12.1.7.3 Make the disk bootable
To make the disk bootable you must have previously created a physical volume whit the option B on
the Copy Boot disk.
This command have to be executed for each boot disk:
..,sys,root # mkboot <Char. device file> ,and press [Enter]
Where:
Char. device file: means the special device file of each boot disks (see Table 12. ).
The commands will be:

..,sys,root # mkboot /dev/rdsk/cxtxdx
12.1.7.4 Set the AUTO file
Now you have to modify the Auto file, in order to allow the server to boot also if the quorum is not satisfied.
This mean that, if you have only one disk and his mirror copy, and one of this two disks is unusable, the
server is able to boot with only one disk.
This command have to be executed for each boot disk (see Table 12. ):
..,sys,root # mkboot a hpux lq (;0)/stand/vmunix <Char. device file> ,and press [Enter]

..,sys,root # mkboot a hpux lq (;0)/stand/vmunix /dev/rdsk/cxtxdx
N.B. Take note of the device file that you have decided to use as mirror root disk.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 267 / 318
318
12.1.7.5 Disable Disk Quorum on Application VG
Meaningful for 1354RM IM only

For the machine with Multiple Volume Group configuration, to allow the volume group activation also if a

disk is in failure you have to change the LVM startup file as shown in this paragraph.
As root user you have to make a copy of the file /etc/lvmrc by entering:
...,sys,root # cp p /etc/lvmrc /etc/lvmrc.save [Enter]
Then change the file /etc/lvmrc by changing the line:

AUTO_VG_ACTIVATE=1
to:
AUTO_VG_ACTIVATE=0
and from:
custom_vg_activation()
{
# e.g. /sbin/vgchange a y s
# parallel_vg_sync /dev/vg00 /dev/vg01
# parallel_vg_sync /dev/vg02 /dev/vg03
return 0
}
to:
custom_vg_activation()
{
/sbin/vgchange a y q n
parallel_vg_sync /dev/vg*
return 0
}
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 268 / 318
318
12.1.7.6 Create the Mirror Copy
Also the mirror copy creation procedure depends by the volume group management.
12.1.7.6.1 Create the Mirror Copy with Multiple Volume Group

To create the mirror copy with Multiple Volume Group management ( 1354RM IM ) you have just to require
the mirror copy of each logical volume by enter the command lvexetend including both file system and
swap/dump logical volumes.
For each Logical Volumes defined execute the command:
..,sys,root # lvextend m 1 <logical volume file> ,and press [Enter]
N.B. You have to start with the first Logical Volume of the first Volume Group (i.e. /dev/vg00/lvol1)
and finish with the last Logical Volume of the last Volume Group (i.e. /dev/vg01/lvol2) respecting
the numeric increasing order.
Example:
..,sys,root # lvextend m 1 /dev/vg00/lvol1


12.1.7.6.2 Create the Mirror Copy with Single Volume Group
To create the mirror copy with Single Volume Group management ( 1354RM US ) it necessary to enter
a lvextend command for each logical volume, including both file system and swap/dump logical volumes,
specify the physical volumes, and proceed with a correct extension order.
For each Logical Volumes defined execute the command:
..,sys,root # lvextend m 1 <logical volume file> <disk device [disk device]> ,and press [Enter]
In order to mirror the logical volume on the correct copy disk it is required to perform the logical volume
extension in the correct order.
The order is defined by the following classes:
a) Contiguous logical volume.

b) Logical volume located on one physical volume
c) Logical volume distributed on more physical volumes.
First of all you have to extend the contiguous logical volume, following the order of their name (lvol1, lvol2,
etc.), then extend the logical volume located on a single physical volume and at the end the logical volume
located on more than physical volume.
To identify the logical volume defined on the system you can enter the command:
..,sys,root # vgdisplay v /dev/vg* | grep LV Name ,and press [Enter]
1AA 00014 0004 (9007) A4 ALICE 04.10
The for each one of them enter the command:

..,sys,root # lvdisplay v /dev/<vg name>/<logical volume> | more ,and press [Enter]
ED 02
957.130.892 W 3AL 61261 AA AA 269 / 318
318
The output will be like the following:
Logical volumes

VG Name /dev/vg00

LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 48
Current LE 12
Allocated PE 12
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default
Distribution of logical volume

PV Name LE on PV PE on PV
/dev/dsk/c2t6d0 12 12
Logical extents
LE PV1 PE1 Status 1
00000 /dev/dsk/c2t6d0 00000 current
Where you can identify the contiguous logical volumes in the Allocation attribute, and the Physical volume
in the Distribution of logical volume section.
It is suggested to prepare a list of the logical volume before start the extension of them.
Example:
..,sys,root # lvextend m 1 /dev/vg00/lvol1 /dev/dsk/c4t12d0

..,sys,root # lvextend m 1 /dev/vg00/lvol5 /dev/dsk/c4t12d0 /dev/dsk/c4t13d0
To create the mirror copy of each Logical Volumes, see Table 4. to check the name of the partitions (in-
cluded the swap partitions) associated at each Volume Group.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 270 / 318
318
12.1.7.7 Assign the rules to the Logical Volumes
Assign the boot, root, swap and dump rules to the Logical Volumes to allow the HPUX to identify where
boot, root, swap and dump partitions are located:
..,sys,root # lvlnboot b /dev/vg00/lvol1 ,and press [Enter]
..,sys,root # lvlnboot v /dev/vg00 ,and press [Enter]

/dev/dsk/c1t8d0 (10/4/4.8.0) Boot Disk
/dev/dsk/c1t9d0 (10/4/4.9.0)
..,sys,root # lvlnboot d /dev/vg00/lvol2 ,and press [Enter]
12.1.7.8 Set the mirror boot path
Now you have to define the alternative boot path, that must be the mirror root disk:
..,sys,root # ioscan C disk ,and press [Enter]
H/W Path Class Description

================================================
10/4/4.8.0 disk SEAGATE ST34572WC
10/4/4.9.0 disk SEAGATE ST19171N
10/0.12.0 disk SEAGATE ST34572WC
10/0.13.0 disk SEAGATE ST39173WC
10/12/5.2.0 disk TOSHIBA CDROM XM5701TA
Find the disk hardware path of the mirror root disk (refer to the Table 12. ) and execute the following com-
mand:
..,sys,root # setboot a <HW path> ,and press [Enter]
Where <HW path> is the disk hardware path of the Copy Boot disk.
Example:
..,sys,root # setboot a 10/0.x.0 ,and press [Enter]
12.1.7.9 Verify the current boot path
In order to verify the Primary bootpath and the Alternate bootpath, execute the following command:
..,sys,root # setboot ,and press [Enter]
Primary bootpath : 10/4/4.8.0

Alternate bootpath : 10/0.12.0
1AA 00014 0004 (9007) A4 ALICE 04.10
Autoboot is ON (enabled)
Autosearch is ON (disabled)
ED 02
957.130.892 W 3AL 61261 AA AA 271 / 318
318
12.2 Mirror Configuration Final Test
After the mirror configuration it is advisable to verify the right configuration of the mirror. This test is based
on two actions:

a) Verify that all the logical volumes are mirrored.
b) Verify the system is able to boot from both boot disks.
12.2.1 Verify all Logical Volumes are Mirrored
To verify all logical volume are mirrored entering the command lvdisplay, and verifying the Mirror Copy
have to be set to 1 for all of them.
Enter the command:

..,sys,root # lvdisplay /dev/vg*/lvol* | more ,and press [Enter]
12.2.2 Verify the Boot from both Boot Disks
To verify the machine is able to boot from both bootable disk you have to perform the boot twice, one time
from the alternate boot path and one prom the primary boot path.
To do it you have to ask the operators to interrupt their activities, shutdown the application, then reboot
the system entering the following command by root user:
Interrupt the boot when the following message will appears on the screen:
Then enter the command: boot alt ,and press [Enter]
The system boots from the alternate boot disk. Wait until the system will be ready. If the boot fails you have
to boot from primary (see following) and review the the disk mirror configuration.
Then login as root, do not start the application and shutdown again the system with:
Interrupt the boot when the following message will appears on the screen:
Then enter the command: boot pri ,and press [Enter]
The system boots from the primary boot disk. Wait until the system will be ready.
If both test succeeded the test is completed.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 272 / 318
318
13 VERIFY THE INSTALLATION
13.1 Verify the RM

13.1.1 Start the RM from IM
Meaningful for both IM and USM.
To verify the installation of a RM Master, start the application:
a) Login as snml.
b) Open the Network Management System box.

Click on Administration icon.
The System Management Feature window will be opened.
Click on System start/stop menu.
Click on Process Monitoring Control menu.
The 1354RM process control window will be opened.
Stop the control, the system and the database:
Select Actions, then Startup, then Database menus.
Wait until the database is started, the icon must change from blue to green.
Select Actions, then Startup , then System menus.
Wait until the system is started, the icon must change from blue to green.
Select Actions, then Control then Start Process menus.
Wait until the control is started, the icon must change from blue to green.
Figure 70. RM start
With the following configuration: 1354RM with OSResilience or/and CoHosted with 1353SH
have been observed a crash of the objAlrMng Agent of 1354RM.
To fix this crash a specific patch have been issued (1354RM Fix16 Plus).
1AA 00014 0004 (9007) A4 ALICE 04.10
If you have such kind of configuration or the objAlrMng crashes please contact the Product Sup-
port Center.
ED 02
957.130.892 W 3AL 61261 AA AA 273 / 318
318
13.1.2 Start the RM from USM
You can open the Monitor also from the RM USM.

Login as administrator (snml)on the RM IM.

Open the 1354RM Network Management System box.
Click on Administration icon.
The system asks you where you want to start the SMF. Under the Start smf window click on on the
master button.
Figure 71. The Start smf window
Start the system as in point b ).
13.1.3 AS initialization
Verify if the installation of the AS following these steps:
On the RM login as snml.

Open the Network Management System box.
Open the Alarms box.
A window will be opened. Wait for the initialization.
If the installation is successfully completed, the Counter Summary window will be opened.
Click on Exit then Exit again menu to quit the window. Confirm with No at the Question window.
Figure 72. The Counter Summary window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 274 / 318
318
13.1.4 Verify the network

Verify if the window of the network running:


Open the Network View box.
A window will be opened. Wait for the initialization.
If the installation is successfully completed, the Root window will be opened.
Click on Map then Exit again menu to quit the window. Confirm with OK at the Warning window.
Figure 73. The Root window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 275 / 318
318
13.1.5 Verify the browser

Verify if the window of the browser running:

Open the Browser box.
If the installation is successfully completed, the Browser window will be opened.
Click on File then Exit menu to quit the window. Confirm with YES at the Confirm window.
Figure 74. The browser window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 276 / 318
318
13.2 Verify RM IM plus SH IM
Meaningful only for IM and USM.

If your network has a RM IM plus a SH IM, verify the plugin installation as follow:
a) Login in the RM IM as snml.
b) Open the Network Management System box.

Open the TMN OSs box.
The TMN OSs window will be opened.
Open the Global Action menu then Network Start.
Confirm with Yes at the next window.
The Network Start/Stop window will be opened. You have to wait 30 seconds (the system will
shows you three windows telling you how many seconds to the start, they will close automatical-
ly at the network start) then the installation starts.
At the network start the SDH Network window will be opened. This window shows you the ac-
tions performed from the system.
Wait until on the SDH Network window the following message appear: ws initialization complete
and the RM and SH icons became green.
At the end close the Network Start/Stop window clicking on Close button.
Figure 75. The TMNOSs window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 277 / 318
318
c) In the Network Start/Stop window, select the SH.
Select Action, then SMF.
The System Management Feature window of the SH will be opened:

Figure 76. SH System Management Feature window
Exit from the window clicking on Exit button.
d) In the Network Start/Stop window, select the SH.

Select Action, then AS.
The AS window of the SH will be opened:
Figure 77. The SH AS window

1AA 00014 0004 (9007) A4 ALICE 04.10
Exit from the window selecting on Exit then Exit menu.
ED 02
957.130.892 W 3AL 61261 AA AA 278 / 318
318
e) In the Network Start/Stop window, select the SH.
Select Action, then PNM.
The SDHNet window of the SH will be opened:
Figure 78. The SDHNet window
Exit from the window selecting on Map then Exit menu.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 279 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
280 / 318
14 TROUBLESHOOTING
The intention of this section is to give a solution to the most frequent problems that occurs during the
A1354RM R5.2 installation.
14.1 Ovlad registration error
If during the registration of the ovlad agent, during the A1354RM R5.2 installation, the system gives you
back this error message:
ERROR: Cant contact DM Communications Infrastructure (is it

running?) (OVs 116)
You have to check the contents of the $OV_CONF/local_p_addr file, it must be in the following form:
ORS_CMIP
N.B. The IP address must be formatted as in the example below:

For the address 151.98.9.4 the format is 151098009004
If the three lines are not in this order modify the file and rerun the axhpovconf.
14.2 Ov_log errors
If the Event log of RM gives you some problems, you have to do these checks:
a) Verify that in the $OV_LOG/ovelog/#0 there is this error:
Unknown file $OV_LOG/ovlog/#0
if this error is present, you have to perform these steps:

..,sys,root # rm r $OV_LOG/ovedb/*.dbs ,and press [Enter]
..,sys,root # rm $OV_LOG/ovedb/*.log ,and press [Enter]
..,sys,root # rm $OV_STACKS/Log.per/* ,and press [Enter]
..,sys,root # swconfig x reconfigure=true DMAgent.Runtime.OVEMSLOG ,and press
[Enter]
..,sys,root # cd /etc/opt/OV/stacks/ems.mibs ,and press [Enter]
..,sys,root # ovstopms.per ems.per ,and press [Enter]
..,sys,root # ovstart ,and press [Enter]
b) If this error is not present, check in the $OV_STACKS/Log.per/0 file if the hostname of the machine
is wrong. In this case the file gives you this error:
CMIS ERROR 1 (wrong hostname)
Modify the name of the machine.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 281 / 318
318
14.3 How to Recover Error Installing Layered Product
If an error occurs during the installation of the layered product the procedure automatically stops and at
the login the following message will be issued:

*************** THIS WORKSTATION IS NOT CORRECTLY INSTALLED **************
To fix the problem, check the log file in AXINSTALL/axinstall.log
***************************************************************************
You have to read the /AXINSTALL/axinistall.log to identify which is the reason of the failure.
If the reason of failure is one of the following, you can retry the installation without starting from the begin:
a) Error reading the medium, because of device power off.

b) Error installing HP Diagnostic Tools, because of wrong primary boot path.
In these cases you can retry the failed installation changing the name of file
/AXINSTALL/axinstall.in_progress in /AXINSTALL/axi.<n>, where <n> is the number of the file written
at the top of the /AXINSTALL/axinstall.in_progress file itself, and rebooting the system.
14.4 Axprintconf Script Failure
The axprintconf can fail because it is not able to shutdown the line printer scheduler, to fix this problem
you have to kill the lpshed process entering the following commands:
..,sys,root # ps edf | grep lpsched ,and press [Enter]
the command issue a line like this:

lp 2670 1 0 Sep 25 ? 0:00 lpsched v
the value show in the second column is the process id (underlined in the example), enter the next
command replacing <process id> with the value of the second column:
..,sys,root # kill 9 <process id> ,and press [Enter]
Then start again the axprintconf.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 282 / 318
318
14.5 Performance Monitoring Tools Failure
The Oracle Developer 2000 printer configuration has usually done by axprintconf, but if you met
problems using Performance Monitoring Tools can be useful to check the Oracle Developer 2000
configuration.
The Oracle Developer 2000 does not allow to format the output if no printer is define in the system and
in its configuration files.
N.B. The printer have to be always configured, also when no printer is present.
To configure the printer you have to: login as root user, modify the file
/opt/oracle7.2/guicommon2/tk23/admin/uiprint.txt adding a new line at the end, with the following format:
for a Postscript printer you have to put a line as in the following:
<printer_name>:Postscript:2:<printer identifier>:dclps171.ppd:
where:
<printer_name> is the name of printer

Postscript indicates a Postscript printer
2 is the numeric identifier for a Postscript printer
Is also allowed the numeric identifier 1.
<printer identifier> is a free string for identify the printer
dclps171.ppd is the Postscript Printer Definition (PPD) file for the printer.
For more information see the contents of the file uiprint.txt itself.
Example:
axprinter:Postsctipt:2:Network Management Printer:dclps171.ppd:
For an ASCII printer you have to put the following line e.g.:
<printer_name>:ASCII:1:<printer identifier>:none:
where:
<printer_name> is the name of printer

ASCII indicates a ASCII printer
1 is the numeric identifier for a ASCII printer
<printer identifier> is a free string for identify the printer
none No Postscript Printer Definition (PPD) file is foreseen for ASCII printer.
Example:
axprinter:ASCII:1:Network Management Printer:none:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 283 / 318
318
14.6 XTerminal Fonts Error
If the system gives you the following error:

Unknown option class font dt interface usermediumrnormalm*********

doesnt exist at /usr/local/lib/perl5/site_perl/Tk/Widget.pm line 180
You have to modify the following file:
For Entria 2 or Envizex 2 Xterminal

..,sys,root # vi /opt/hpxt/enware2/xthome/config/<hostname>.cfg ,and press [Enter]
For Entria or Envizex Xterminal

..,sys,root # vi /opt/hpxt/enware/xthome/config/<hostname>.cfg ,and press [Enter]
Near the line 756, you have the following:
you have to search (with / ) the word Font Path (for Entria or Envizex Xterminal) or the word FontPath (for
Entria 2 or Envizex 2 Xterminal). Remove the comment (#) to this line and add at the end of the line the
following sequence: ,./dt/usr/config/xfonts/C
Save and quit the file pressing [Esc], typing :x! and press [Enter].
Then turn off and turn on again the XTerminal.
14.7 SEC box
If login on the RM as snml user a box blue with the following message appear:
Security not activated
it means that you dont have performed the step explained in the paragraph Integrate SH machine on
1354RM contained in the 1353SH Installation Guide [7]. Close the box and perform this step.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 284 / 318
318
14.8 SMF installation failure
a) If it is not possible to install the SMF package because the Software Distributer detects the same
version already present, and it is not possible to remove it using the swremove, execute the following
command:
..,sys,root # swinstall s /SD_CDROM/SMF_R5.1.7.9.sdpkg x reinstall_files=true SMF

,and press [Enter]
This problem occurs when the SMF installation subtree has been accidentally removed by command line
(rm r).
b) If the SMF installation in a RMP machine configured in HPUX 11.00 doesnt work well, you have
to control if the /usr/local/lib/perl5/1353sh/axmailconf.pm file contains the following lines:
..,sys,root # vi /usr/local/lib/perl5/1353sh/axmailconf.pm ,and press [Enter]
Type /MAILDIR:
my $MAILDIR = /usr/mail
my $MAILDIR = /var/mail
If both are present, you need to remove the first one (the one in bold).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 285 / 318
318
14.9 Recover LAN Failure
On some system, especially using LANAUI connections, a temporary network disconnection can put the
interface DOWN, also when the network is reconnected. In this case can be useful to reset the interface

using landiag tool. This paragraph shows how to reset a lan interface.

N.B. Be careful. Do not reset an active lan interface.
Login the system as root, then enter the command:

..,sys,root # lanscan ,and press [Enter]
To identify the Network Management ID of the LAN Interface (nmid).

..,sys,root # landiag ,and press [Enter]
LOCAL AREA NETWORK ONLINE ADMINISTRATION, Version 1.0
Wed, Dec 1,1999 13:02:08
Copyright 1994 Hewlett Packard Company.

All rights are reserved.
Test Selection mode.
lan = LAN Interface Administration

menu = Display this menu
quit = Terminate the Administration
terse = Do not display command menu
verbose = Display command menu
Enter command: lan ,and press [Enter]
LAN Interface test mode. LAN Interface Net Mgmt ID = 4
clear = Clear statistics registers

display = Display LAN Interface status and statistics register
end = End LAN Interface Administration, return to Test ...
menu = Display this menu
nmid = Network Management ID of the LAN Interface
quit = Terminate the Administration, return to shell
reset = Reset LAN Interface to execute its selftest
Enter command:
The NMID 4 is usually set as default, if the NMID of the LAN have to be recovered is different enter nmid
and [Enter], the system asks for the new NMID issuing the following question:
Enter Network Management ID. Currently 4: <new NMID> and press [Enter]
Enter the right NMID and proceed entering :

Enter command: reset , and press [Enter]
If the system issues just the following message follow by the menu the interface have been reset without
any error.
Resetting LAN Interface to run selftest.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the message is followed by error messages the interface is fault or still not connected.
In any case is advisable to verify the interface status with lanscan.
ED 02
957.130.892 W 3AL 61261 AA AA 286 / 318
318
14.10 Large Database Startup Failure
If you have some problems to startup a large database with the command:

you have increase the current value of the kernel parameter db_block_buffers of 30% and rebuild the
kernel using the sam utility.
a) Force the ORACLE modify db_block_buffers:
1) Login as snml and shutdown the database and the system (if running):

and login again as root user.
2) Edit the /usr/snml/databases/dbsnml/admin/pfile/init1.ora file:
Type /db_block_buffers and change properly the value of the line not commented of
parameter db_block_buffers.
3) Repeat point 1 ) for the file /usr/snml/databases/dbsnml/admin/pfile/init1_make.ora.
b) Restart the database.
c) Restart the RM system.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 287 / 318
318
14.11 Install tape for backup/restore
If you need to execute a backup (or restore) of your machine but the tape was not present when the
machine was installed, you can get in trouble because there are no speciale files in HPUX to acess the

tape.

In this case you have to create the tape special files.
First of all check the connection or connect the tape driver to the system, power on it.
Verify if the system recognizes the tape. Login as root user:
..,sys,root # ioscan fnC tape ,and press [Enter]
a) If the result is like:

======================================================================
tape 0 10/1/4/0.3.0 stape CLAIMED DEVICE QUANTUM DLT8000
execute the following command:
..,sys,root # insf C tape ,and press [Enter]
The system will answer you (for example):
insf: Installing special files for stape instance 0 address

10/1/4/0.3.0
b) otherwise control the tape connections, then execute the insf command as explained in point a ).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 288 / 318
318
14.12 Process Monitor (mngAgent) does not start
If the SMF Process Monitor does not start or at the manual execution of the mngAgent command the
system stops and gives you back the following error:
/usr/snml/bin/mngAgentSU[101]:/usr/snml/bin/mng_agent_HPUX_11_S800.exe:
Executable file incompatible with hardware.
a) You must execute the following command as root user:
..,sys,root # mv /usr/snml/bin/mng_agent_HPUX_11_S800.exe
/usr/snml/bin/mng_agent_HPUX_11_S800.exe.removed ,and press [Enter]
..,sys,root # ln s /usr/snml/bin/mng_agent_HPUX_10.20_S700.exe
/usr/snml/bin/mng_agent_HPUX_11_S800.exe ,and press [Enter]
b) If cliking on the Administration icon you are not able to start the Monitor (System Start/Stop menu),
open a display on your machine as snml user, set the DISPLAY variable and launch the following
command:
..,$ mngAgent ,and press [Enter]
If the system gives you back the same error:
/usr/snml/bin/mngAgentSU[101]:/usr/snml/bin/mng_agent_HPUX_11_S800.exe:
Executable file incompatible with hardware.
execute the command shown on point a ).

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 289 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
290 / 318
APPENDIX A CONFIGURATION SECURE WEB CONSOLE
A.1 Introduction
The HP Secure Web Console comes with a preconfigured IP address 192.0.0.192. An Initial Configuration
step is required to assign the final IP address to the Secure Web Console. This step requires you to run
a web browser (Internet Explorer or Netscape Communicator) from a PC or a Workstation (called
client_host), using the http://192.0.0.192 URL to reach the Secure Web Console over a LAN connection.
N.B. You should have obtained an IP address and a subnet mask for the Secure Web Console and
know the name of the system to be administered.
If you are installing and configuring more than one HP Secure Web Console, you must install and configure
each Secure Web Console individually.
N.B. The Secure Web Console support the latest web browser versions:
Netscape Communicator 4.0 or higher

Internet Explorer 4.0 or higher
On your web browser enable Java and disable Proxies.
A.2 Initial configuration
a) The IP address, 192.0.0.192, is the preconfigured IP address of the Secure Web Console. Power
off any other devices having the same IP address.
b) Connect the LAN cable.
c) Connect the power adapter to the Web Console.
d) Connect the external power adapter to a wall socket. The Web Console performs an hardware and
firmware selftests, then starts the software boot sequence (see Figure 79. ).
e) Ensure the client_host where the web browser is running, is on the same IP subnet as the Secure
Web Console, and add it to the gateway list, entering the following commands. These commands
can be used in either DOS or UNIX (PC or Workstation where your browser is running), as
administrator (root) user:
1) > route add 192.0.0.192 <client_host IP address> ,and press [Enter]
Example: route add 192.0.0.192 130.13.54.23
2) > ping 192.0.0.192 ,and press [Enter]
If ping is successful, follow the instructions in section A.3, else proceed with the next step.
3) > arp s 192.0.0.192 <Web Console MAC_address> ,and press [Enter]
N.B. The MAC address must be entered in the appropriate format, as shown below:
PCs: 0060b0223eae
1AA 00014 0004 (9007) A4 ALICE 04.10
UNIX workstation: 00:60:b0:22:3e:ae
ED 02
957.130.892 W 3AL 61261 AA AA 291 / 318
318
The MAC address of the Secure Web Console is marked on the top of the device and also on
the box of the device.

WEB SECURE CONSOLE
reset button
Solid amber = test in progress

Amber off = selftest passed amber green
Amber stays on = selftest failed
Flashing green = network activity
Figure 79. LED status

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 292 / 318
318
A.3 Configuration
To configure the IP address and the users on the Web Console, access to the device through your web
browser on the same subnet, by typing the following URL: http://192.0.0.192
The following window will appear:
N.B. In every window it is possible to access to an help online clicking on the HELP button.
Figure 80. Welcome window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 293 / 318
318
Click on the OK button. The following window will appear:

Figure 81. First administrator account window
You have to fill the fields in the window to create the first administrator account.
Complete the fields with the following informations:
Name: is the operator name. Set it to: Administrator
Function: it is the user level. It can be Administrator or Operator.

Administrators manage user accounts and are responsible for administration, net-
work configuration and software upgrades.
Operators manage the connected system and perform system administrator tasks.
They can change their own passwords but cannot change user account information
for other users.
The first user account that is created on a Secure Web Console is an administra-
tors account.
Information: This optional field enables you to enter information about the account. For example:
First Administrator account
Login: Enter the name that you will use to access your user account on the Secure Web
Console. Set it to: administrator
Password: Enter a password of at least six alphanumerical characters. Set it to: administrator
Reenter password: Enter administrator again.

1AA 00014 0004 (9007) A4 ALICE 04.10
At the end click on the OK button.
ED 02
957.130.892 W 3AL 61261 AA AA 294 / 318
318
Figure 82. Configure IP window
You have to fill the fields in the window to set the network information for the Secure Web Console.
Complete the fields with the following informations:
Secure Console Name: Is the host name of the Web Console. This name must be unique in your
network.
IP address: Is the IP address of the Secure Web Console.
IP subnet mask: Is the subnet mask of the network where the Secure Web Console will be
installed.
IP gateway: This is an optional field. Is the IP address of the gateway of your network.
System name: Is the host name of the system to which the Secure Web Console is
connected. This name will be displayed on each browser window when
you are logged on the Secure Web Console.
At the end click on the OK button.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 295 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
Click on the OK button.
957.130.892 W
Figure 83. End of initial setup window
318
3AL 61261 AA AA
296 / 318
A.4 Login to Web Console
Now you have to connect the serial cable from the system to the Secure Web Console and restart the web
browser on your PC or Workstation, using the IP address of the Secure Web Console.
If the installation and configuration are correct the following window will appear:
Figure 84. Login window

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 297 / 318
318
Insert the login name and password defined for the first administrator account, and click on LOGIN button.

Figure 85. Web Console window
The main options in this window are:
Users: Is the list of the users currently connected to the Secure Web Console.
Up to 4 users can be simultaneously connected. Only the user whose name is
underlined has write access to the console.
If you click on the user name you obtain more informations about it.
Guided tour: Is an help online for the Secure Web Console.
Access console: Click on this option to access to the system connected to the Web Console.
Configuration: Using these options you can change the configuration parameters.
Support: Using these options you can change same device parameters.
Exit: Use this option to exit from Secure Web Console.
To access to the system connected to the Secure Web Console you have to:
a) click on the Access Console option;
b) the terminal window of the system connected to Web Console will appear. Press [Enter] to have the
prompt of the controlled system;
1AA 00014 0004 (9007) A4 ALICE 04.10
c) at this point you can use the Web Console as a terminal;
N.B. If you want to extract the terminal window from the browser window click on the In/Out option.
ED 02
957.130.892 W 3AL 61261 AA AA 298 / 318
318
d) to close the terminal click on Close console option;
e) to exit from the Web Console click on the Exit option.

A.5 Console Emulation setup
Some time the WEB console is issued by HP with terminal emulation set to VT100, this setup can pro-
duce mulfuction executing the application installation. In order to prevent such kind of problem it is advis-
able to check the terminal emulation set on the console.
To access the terminal emulation setup you have to click on Access Console In/Out button, this open
a new window with a bigger terminal and some menus. Click on Setting menu and then on Emulation
to open the Emulation Setting window and check that the Alpha Emulation box contains the value:
HP70092. If not change it as well and press OK to store the change.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 299 / 318
318
A.6 Configuration reset
If it is necessary to reset the Secure Web Console to the factory settings, you have to use the following
procedure:

Using the following procedure all configuration data will be lost!
a) Power off the console by unplugging the power cable.
b) Press the button on the top of the console (see Figure 79. ) and keep it pressed.
c) Power on the box by replugging the power cable.
d) Release the button after a couple of seconds.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 300 / 318
318
APPENDIX B SYSTEM SHUTDOWN
In order to prevent problem when a system have to be powered off, it is advisable to follow this procedure.
Login as root user, and enter the following command:
..,sys,root # shutdown h now ,and press [Enter]
When the shutdown procedure will be finished, the system will issue a message that authorize the power
off.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 301 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
318
3AL 61261 AA AA
302 / 318
APPENDIX C GOGLOBAL INFORMATIONS
C.1 Introduction to GoGlobal

GOGlobal Version is a PC X server application package that provides access to X applications running
on UNIX host computers from PC display devices.
GOGlobal is comprised of two pieces of software: GlobalPC residing on the desktop device and Global-
Host on the UNIX host machine:
N.B. This chapter is applicable to the GOGlobal PC X server Versions 1.5, 1.62 and 1.63: they are
functionally equivalent and the installation procedure is the same.
C.2 Installation on UNIX machine
If the installation of HPUX is executed using the 17D bootable support, this package is installed automati-
cally during the installation of the Operating System. If the bootable medium is the 15a, 15b, 15c or 15d
the bootable procedure during the Optional Software Selection, asks to the user if he wants to install the
GOGlobal host kit Software.
If you have executed a manual installation of HPUX and you want to install GOGlobal after this phase,
you have execute this steps:
a) Login as root.
b) Copy in your machine at location /alcatel/DEPOT the file GoGlobalHostV<package_version> (i.e.

GoGlobalHostV163.sdpkg) from the location where this file is stored.
c) Check if there is a old version of GOGlobal already installed on your computer using the command:
$ swlist | grep GoGlobalHost ,and press [Enter]
If it is present you have to remove it with the command:
$ swremove GoGlobalHost ,and press [Enter]
d) Launch from current directory (/alcatel/DEPOT) the following command:
$ swinstall s $PWD/GoGlobalHostV<package_version>.sdpkg * ,and press [Enter]
When this command will be finished, the package will be installed on the current machine.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 303 / 318
318
C.3 Installation on PC
In both cases (HPUX installed with bootable or manually) you have to install GOGlobal on the Personal
Computer which will be used as Xterminal.

N.B. Before this step, be sure that the installation on Unix machine was done.
a) Open a DOS window on PC and type the following commands:
c:\> mkdir gotmp ,and press [Enter]

c:\> cd gotmp ,and press [Enter]
c:\gotmp> ftp <host_IP> ,and press [Enter]
user : root ,and press [Enter]
password : <root_password> ,and press [Enter]
where <host_IP> is the IP address of the Unix machine where GOGlobal is installed and <root_pas-
sword> is the password of the user root of that machine (install10 if was not modified).
Continue with:
ftp> cd /usr/G11R6.1/pc ,and press [Enter]

ftp> bin ,and press [Enter]
ftp> get gpc<package_version>.exe ,(i.e. gpc163.exe) and press [Enter]
ftp> quit ,and press [Enter]
b) Now, always fron the c:\gotmp PC directory, you have execute the following command:
c:\gotmp> gpc<package_version>.exe ,(i.e. gpc163.exe) and press [Enter]
The self extractor program ask you to confirm the directory where to install the files extracted (use
the default: c:\GoGlobal) then select Unzip and proceed.
When the procedure is finished, you have to select OK and Close.
c) Now, you have open Explorer tool and in the directory GoGlobal you have execute the file:
Setup.exe
If this is an update from a previeus version of GOGlobal, you have confirm all clicking on Next >
button until Finish.
Otherwise, if this is the first installation of this tool, the procedure ask you to load the licenses data,
and then to proceed until Finish.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 304 / 318
318
C.4 GOGlobal Connections creation
C.4.1 Creating a new generic connection

Start GOGlobal. In order to create a connection you have to choose the icon New from the Connection
Manager or the menu Connection/New.
First, assign a name to your connection. You may find it useful to provide a descriptive name for the con-
nection (connection names may contain spaces).
Figure 86. Connection Name
The name is used in the Connection Manager to identify it from the other connections, and does not deter-
mine the type of connection or its attributes. When youre defining a new connection you can decide to
create it completely new or copying settings from a previously defined connection.
N.B. The figures in this chapter are related to GOGlobal version 1.5 but the new versions are func-
tionally equivalent (dont take into account the version number).
The Connection Manager contains a list of all the connections currently in GOGlobal. For this example,
type tlvhac_login in the Connection name field. Click Next > to continue.
In the next dialog, there are two connection types to choose.
Choose Network connection and check that radio buttons below are not selected. In order to complete
a network connection, the following information is needed:
The UNIX host name you are connecting to; this has to be inserted in one of the following forms:
an individual host name;
an IP address in numeric form.
The connection port type to be chosen in the port field after clicking on Details button: be sure that
the one selected is telnet. Then click OK.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 305 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
Click Next > to continue.
Figure 87. Host Name
318
3AL 61261 AA AA
306 / 318
C.4.2 Completing the connection with log in phase
Click Script Editor to configure your log in.

Now you have to insert the correct commands in order to perform a correct log in. Respect the example
and fill the two commands:
1st. command:
Type in the Wait for: field >
Type in the Transmit: field cd /usr/G11R6.1/bin
with the Enter radio button selected then click Insert.
2nd. command:
Type in the Transmit: field ./goglobal
With the Enter radio button selected then click Insert.
Click OK.
Figure 88. Log in Connections
Click Finish to complete your first connection.
It is possible introduce only a command. In the example:

Type in the Transmit: field /usr/G11R6.1/bin/goglobal
With the Enter radio button selected then click Insert.
Click Finish to complete the connection.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 307 / 318
318
C.4.3 Creating a new connection with automatic login
The user has to execute the following steps:

Create a new connection.

Insert the related name.

Click Next to continue.
When you are in the Connection type window, choose Network connection, insert the host name in the
Host field and check the follow radio button: Connect directly to the X server, bypassing login shell. In
the same window click Details button and select gologin port in the Port field.
Click OK and Next > to continue.
When you are in the AutoLogin window, insert your login ID and password.
Figure 89. Automatic connection
Click Finish to complete your connection.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 308 / 318
318
C.5 GOGlobal connection management
To open a connection, it must first be selected by clicking on the name in the Connection Manager as
shown in the figure:
Figure 90. List of connections
N.B. The figures in this chapter are related to GOGlobal version 1.5 but the new versions are func-
tionally equivalent (dont take into account the version number).
After selecting the connection, open it in one of the following ways:
Click on the Toolbar (Connect icon).

Select Connect! in the Connection menu.
Right click on the connection and select Connect!
Press the [Enter] key.
Double click on the connection.
If a generic connection is chosen, a telnet window will appear where you have to insert login ID and pas-
sword; no actions have to be performed if an automatic log in connection is opened.
GOGlobal can be connected to one host or multiple hosts. Managing these connections is done through
the Connection Manager which maintains a connection list showing one name per connection. Each con-
nection maintains its own attributes, such as text window size and text color. Though unique attributes are
maintained for each connection, you can apply any attribute changes or updates to all the connections
(such as font size) with one operation.
Connections can be created, edited, or deleted, as well as moved up and down in the connection list. As
with other functions in GOGlobal, these operations can be initiated in several ways:
Click Toolbar buttons.

Select from menus.
Right click on the desired connection and make selections.
Use hot keys shown on the right side of menus.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 309 / 318
318
C.5.1 Editing a connection
Any connection parameters may be changed. If the connection is open when you change the parameters,
the new setting will not take effect until the connection is reopened. As with creating a connection, there

are several ways a connection can be edited. First, you select the connection to be edited by clicking on

it. Editing a connection is initiated in one of the following ways:
Click on the Toolbar.
Select QuickEdit... in the Connection menu.
Right click on the desired connection and select QuickEdit....
Simultaneously press the Alt and Q keys.
N.B. The editing process is identical to creating a new connection when using the Connection Wiz-
ard.
N.B. It is not possible convert a login connection to an autologin connection.
C.5.2 Check Connection Configuration
The GoGlobal client can create bottleneck on the PC with particular configurations. In order to avoid this,
make sure that in the Quick Edit > Display Settings of the GoGlobal connection the boxes AutoCopy
from Host Selection to Clipboard and AutoCopy from Clipboard to Host Selection are unselected, like
as shown in the following figure:
Figure 91. GoGlobal Host Display Settings
C.5.3 Exiting a connection

1AA 00014 0004 (9007) A4 ALICE 04.10
When you are connected with GOlogin port (automatic log in connection) its enough to exit the applica-
tion (1353SH or 1354RM) and all windows related with the current connection will be closed. If your con-
nection is telnet type you have to exit the application and close the telnet window.
ED 02
957.130.892 W 3AL 61261 AA AA 310 / 318
318
APPENDIX D HOW DISABLE/ENABLE HP SERVER CPU
To be able to perform the installation of the HPUX as shown in this document on HP Server R390
equipped with two CPUs, it is necessary to disable one of them before installing the HPUX. In the follow-
ing paragraph youll find the procedure to disable and enable the CPUs.
To disable or enable a CPU it is necessary to access the Boot Console Interface. The Boot Console Inter-
face is the feature of the HP system that allow to set up the system to boot and provides some configuration
and display command before booting HPUX, to access you have two different ways:
1 When the system of powered off, you have just to power on it.
2 When the system is running HPUX, login as root and enter the command:
shutdown r now ,and press [Enter]
In both cases you have to wait until the following message will appear on the console (or Secure Web Con-
sole):
Then press any key to interrupt the auto boot procedure and access the Boot Console Interface.
D.1 Disable a HP Server CPU
The Boot Console Interface prompt you with:

Main Menu: Enter command or menu >
You have to enter: co and press [Enter] key to access the configuration menu.
Configuration Menu
Command Description

AUto [BOot|SEArch] [ON|OFF] Display or set specified auto flag
BootID [<proc>] [<boot ID>] Display or modify processor boot ID
BootINfo Display bootrelated information
BootTimer [0200] Display or set boot delay time
CPUconfig [<proc>] [ON|OFF] Config/deconfig processor
DEfault Set the system to predefined values
FastBoot [ON|OFF] Display or set boot tests execution
LanConfig [ENABLE|DISABLE] Enable or Disable the builtin LAN
PAth [PRI|ALT] [<path>] Display or modify a path
SEArch [DIspaly|IPL] [<path>] Search for boot devices
TIME [c:y:m:d:h:m:[s]] Read or set the real time clock in GMT
BOot [PRI|ALT|<path>] Boot from specified path
DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
MAin Return to Main menu

Configuration Menu: Enter command >
Figure 92. Configuration Menu

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 311 / 318
318
At configuration menu prompt you have to enter: CPU and press [Enter] key to see how many CPUs are
present in the server configuration.
Then you have to enter for each of them except the CPU 0, the command: CPU <cpu number> OFF and

press [Enter]. The CPU will flagged to be disable.

When all but one CPUs will be flagged to be disable, reset the system entering the command: RESET
and press [Enter].
N.B. Do not forget to enable again the CPUs at the end of installation!
The system restarts with just one CPU.
D.2 Enable a HP Server CPU
To enable the CPUs you have to access the Boot Console Interface, and at the Main menu prompt:
Main Menu: Enter command or menu >
You have to enter: co and press [Enter] key to access the configuration menu (see Figure 92. ).
Then enter the command: CPU and [Enter], to identify all the disabled CPUs.
For each of them enter the command: CPU <cpu number> ON and [Enter]. The CPU will be flagged to
be enable.
When all but one CPUs will be flagged to be enable, reset the system entering the command: RESET and
press [Enter].
The system restarts with all the CPUs operational.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 312 / 318
318
APPENDIX E SWITCH OFF FAULT LAMP OF N & L CLASS SERVER
The HP server N and L Class are provided with an additional processor, the Guardian Service Processor
(GSP). This processor has many functions including the management of the front panel lamps.
About the full description of the GSP functionalities refer to HP documentation provided by as help online
by GSP itself.
About the front panel lamps, this appendix just explains how to reset the fault and the alert lamp in case
of boot failure.
In fact the GSP manages the boot failure as a Alert Level 15:
Fatal hardware or configuration problem prevents operation
When the problem is solved, you can reset the alert and the fault lamps by performing the following proce-
dure:
Get the access to the console, directly connecting a console terminal or through a Web Console.
Press [Ctrl] [b] to access the GSP
GSP issues the the message:
Leaving Console Mode you may lose write access

When Console Mode returns, type ^Ecf to get the write access.
Service Processor login:
Enter [Enter] to proceed.
Service Processor password:
Enter [Enter] to proceed.
Then you get the GSP prompt: GSP>
At GSP prompt enter: sl [Enter] to read the logs stored in the GSP.
The sl command issues the following message:
SL
Select Chassis Code Buffer to be displayed:

Incoming, Activities, Error, Current boot or Last boot? (I/A/E/C/L)
Enter: E [Enter] to select the Errors
GSP issues the message Set up filter options on this buffer? (Y/[N])
Enter: N [Enter]
GSP issues a message like:
Log Entry # 0
1AA 00014 0004 (9007) A4 ALICE 04.10
SYSTEM NAME: uninitialized

DATE: 01/12/2000 TIME: 08:36:02
ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents oper...
SOURCE: 8 = I/O
ED 02
957.130.892 W 3AL 61261 AA AA 313 / 318
318
SOUCE DETAIL: 6 = disk SOURCE ID 0
PROBLEM DETAIL: 3 = Functional failure
CALLER ACTIVITY: 1 = test STATUS:0
CALLER SUBACTIVITY: 48 = implementation dependent

REPORTING ENTITY TYPE:0 = system firmware REPORTING ENTITY ID: 00

0x000000F386001480 00000000 00000000 type 0 = Data Field Unused
0x580008F386001480 00006501 05082602 type 11 = Timestamp01/12/2000 08:36:02
Type CR for next entry, q CR to quit.
Press [Enter] until the GSP issues as last line of the message:
This is the last log entry corresponding to your choice
Press [q] [Enter] to exit the sl command.
Now check the status of the front panel lamps by enter: vfp [Enter]
The command issues an output like:
VFP
This command activates the immediate display of the Virtual Front Panel.
LEDs: RUN ATTENTION FAULT REMOTE POWER

ON OFF OFF OFF ON
processor display_activity() update 1f00
Proceed with Live Mode of VFP? (y/[n])
Enter: N [Enter] to get back to GSP prompt.
Both Attention and fault have to be off, that means also the front panel lamps are also switched off. If the
fault lamp is still on means the failure is not recovered.
To return to console mode enter: co [Enter] at GSP prompt.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 314 / 318
318
APPENDIX F NR5.0B PL1 UPGRADE CHECK LIST
There are some dependencies within the 1353SH and 1354RM application, that require a specific se-
quence in the upgrade activities. The following Check List drives you to NR5.0B PL1 Upgrade.
Before start with the upgrade is it suggested to perform the full system backup.
Upgrade sequence:
- As 1354RM user (snml) acknowledge all alarms.
- Backup with SMF the 1354RM database including:

1354RM Network, 1354RM PM, 1354RM Alarm and 1354RM Operators
- Shutdown 1354RM system
Update 1354RM IM
- Install Bootable Medium Addendum
- Install Patch F14
N.B. After this patch installation will be not possible to login as snml or other
RM user until the upgrade of SMF has been done.
- Install Patch F16
- Remove A1330AS 5.1.1
- Install A1330AS 5.1.1 + P002 + P003
- Remove SMF 5.1.7.6
- Install SMF 5.1.7.9
- Install NAV 5.0.2
- Remove SEC 5.0.0
- Create Oracle Users for PM
- Restore the 1354RM database
- Install PMV
- Update the 1353SH software on 1354RM
- Update the 1353SH/1354RM Plugin
- Install SEC 5.0.0 + P001
Update 1354RM USM (Perform this step for each presentation)

1AA 00014 0004 (9007) A4 ALICE 04.10
- Install Patch F14
- Install Patch F16
ED 02
957.130.892 W 3AL 61261 AA AA 315 / 318
318
- Remove A1330AS 5.1.1
- Install A1330AS 5.1.1 + P002 + P003

- Remove SMF 5.1.7.6

- Install SMF 5.1.7.9
- Install NAV 5.0.2
- Remove SEC 5.0.0
- Install PMV
- Update the 1353SH software on 1354RM
- Update the 1353SH/1354RM Plugin
- Install SEC 5.0.0 + P001
- Startup the 1354RM
For each 1353SH set of Master (SHCluster)
- Shutdown the the SHCluster
Update 1353SH Master and Element Managers
- Remove the SHINSTALL 5.3.0.8
- Install the SHINSTALL 5.3.1.0
- Install the axinstallSH 2.0.3
- Create the /AXINSTALL/axinstallSH.lis
- Save PNM Configuration
- Update the 1353SH software to PL1
- Stop HP OpenView
- Start HP OpenView
Update 1353SH Presentations
- Install the A1330AS USM
- Remove the SHINSTALL 5.3.0.8
-
1AA 00014 0004 (9007) A4 ALICE 04.10
Install the SHINSTALL 5.3.1.0
- Install the axinstallSH 2.0.3
ED 02
957.130.892 W 3AL 61261 AA AA 316 / 318
318
- Create the /AXINSTALL/axinstallSH.lis
- Save PNM Configuration

- Update the 1353SH software to PL1

Reconfigure the SHCluster
- Configure again the processes performing a Force HPOV Registration
- Integrate again the SHCluster with 1354RM
- Startup the SHCluster

1AA 00014 0004 (9007) A4 ALICE 04.10
ED 02
957.130.892 W 3AL 61261 AA AA 317 / 318
318
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
957.130.892 W
END OF DOCUMENT
318
3AL 61261 AA AA
318 / 318

1354rm52b Instalacion

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

1354rm52b Instalacion

Caricato da

Copyright:

Formati disponibili

QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 957.130.892 W Ed.02 3AL 61261 AAAA Ed.02

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

SERVONO 5 BUSTE TRASPARENTI (Es.Cod.854.010.051 H)

INSERIRE LE 5 BUSTE TRASPARENTI

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 320

TOTALE FOGLI A4 TOTAL A4 SHEETS: 160

WARNING FOR A-UNITS OTHER THAN A-ITALY

Labels are done according to A-Italy binder format.

957.130.892 TQZZA 3AL 61261 AAAA TQZZA Y 1/ 4

not permitted without written authorization from Alcatel.

Originators 1354RM REL.5.2B

ORIGINALE SU FILE: ALICE 6.10

Regional Network Manager for SDH and Optical Networks

957.130.892 TQZZA 3AL 61261 AAAA TQZZA Y 2/ 4

Regional Network Manager for SDH and Optical Networks

Version 5.2.1.5 PL1

957.130.892 W Ed.02 3AL 61261 AAAA Ed.02

Version 5.2.1.5 PL1

1300NM 1354RM Rel.5.2B

957.130.892 W Ed.02 3AL 61261 AAAA Ed.02 INSTALLATION GUIDE VOL.1/1

957.130.892 TQZZA 3AL 61261 AAAA TQZZA Y 3/ 4

Version 5.2.1.5 PL1

957.130.892 W Ed.02 3AL 61261 AAAA Ed.02

LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 INSTALLATION OF HPUX AND THIRD PARTS SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

02 010409 SC 01041102 B. Bosisio ITAVE M. Mantegazza ITAVE

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

957.130.892 W 3AL 61261 AA AA 1 / 318

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

5 BOOTABLE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

6 SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

957.130.892 W 3AL 61261 AA AA 2 / 318

6.4 OSI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6.4.1 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

7 X TERMINAL INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

8 PRINTER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

9 INSTALLATION OF 1354RM R5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.7.7 Prevent Unnecessary Mail Messages to root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

957.130.892 W 3AL 61261 AA AA 3 / 318

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

11.19 RM Zoomin from NN Using RM USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

957.130.892 W 3AL 61261 AA AA 4 / 318

11.20.6 Run the mailer configuration script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

11.20.7 Align the printer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

12 DISK MIRRORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

13 VERIFY THE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

APPENDIX A CONFIGURATION SECURE WEB CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

957.130.892 W 3AL 61261 AA AA 5 / 318

APPENDIX B SYSTEM SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

not permitted without written authorization from Alcatel.

APPENDIX D HOW DISABLE/ENABLE HP SERVER CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

APPENDIX E SWITCH OFF FAULT LAMP OF N & L CLASS SERVER . . . . . . . . . . . . . . . . . . . . . . 313

APPENDIX F NR5.0B PL1 UPGRADE CHECK LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

957.130.892 W 3AL 61261 AA AA 6 / 318

Figure 1. Example of management platform configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 2. HPUX Set Parameters Welcome window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 49. SAM Areas: Networking and Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130