Академический Документы
Профессиональный Документы
Культура Документы
Alcatel 1350
Management Suite
1350 Rel.7.4
Network Release
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 PRELIMINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Referred External Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Related Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Registered Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
8
8
8
9
10
10
10
2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Requested Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 HPUX Operating System Installation & Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Predispose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Instance creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 Software copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5 Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.6 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.7 Network Management SubSystems Fuctional Dependencies . . . . . . . . . . . . . . . . . . . .
2.2.8 Optional Network Management SubSystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
15
16
16
16
16
16
16
18
19
20
3 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Quick Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 HPUX Operating System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 System Predisposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 HPUX Operating System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4 Install and Customize Alcatel Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.5 Final Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
22
22
23
26
28
31
02
061127
01
060724
ED
DATE
ECR38607
F.Casasole
B.Bosisio
M.Occhietti
B.Bosisio
M.Occhietti
F.Casasole
CHANGE NOTE
APPRAISAL AUTHORITY
ORIGINATOR
ED
02
3AL 88924 BAAA
178
1 / 178
32
32
37
57
58
58
59
60
61
62
63
64
86
88
88
90
95
99
99
103
111
123
124
125
ED
135
135
135
136
136
138
140
140
140
141
141
141
143
144
144
144
144
02
3AL 88924 BAAA
178
2 / 178
145
145
146
146
146
147
147
148
149
150
151
151
151
154
155
155
155
156
160
165
167
167
170
171
172
172
173
173
174
175
175
176
177
178
ED
02
3AL 88924 BAAA
178
3 / 178
FIGURES
Figure 1. GPS/MP to Wcable connecion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. F/F adaptor cable to connect PC to HP GSP/MP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Installation Phases on a server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Example of TMN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. NMS functional dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Example of disk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Alcatel NMS Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. 1359HA OSResilience communication example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. NTP Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. NMS Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. NMS Customize trace window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. List of existing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. 1353NM Customize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. 1353NM Customize Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. 1353NM Custom Product Selection N.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. 1353NM Custom Product Selection N.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. 1353NM Custom Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. 1353SHBKW 7.0 Custom System Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. 1353SHBKW 7.0 Custom Parameters Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. 1353SHBKW 7.0 Custom Execution window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Add 1359HA OSResilience Starting configuration Example . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Add 1359HA OSResilience Final configuration Example . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. GoGlobalUX Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. GraphOn License WEB Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. GraphOn License WEB Page Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. GraphOn License WEB Page Software Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. GraphOn License WEB Page License Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. GraphOn License WEB Page License Output Example . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Rear view of server with two disk cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Rear view of server with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Example of K server cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Rear view of server R with one disk cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Front view of L Server (without cover panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Rear view of L Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Front view of A Class and RP2430 Servers (without cover panel) . . . . . . . . . . . . . . . . . .
Figure 38. RP3410 and RP3440 Server Front . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. RP4440 Front View without fromt pannel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. RP4440 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. RP4440 Front View withou fron pannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. RP4440 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Rear view of N/RP74xx Server with SC10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. RP7400 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Rear view of RP7410 Server with DS2405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
15
17
18
51
61
86
89
90
108
108
110
115
115
117
117
118
118
121
121
122
130
131
151
156
156
157
158
159
167
168
169
170
171
171
172
172
173
173
174
174
175
176
177
178
TABLES
Table 1. Optional Network Management Subsystem Applicability Table . . . . . . . . . . . . . . . . . . . . . .
Table 2. NR7.4 NMS/NMC table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
29
ED
02
3AL 88924 BAAA
178
4 / 178
ED
32
73
88
89
95
95
103
149
149
150
02
3AL 88924 BAAA
178
5 / 178
ED
Edition
Date
Notes
Ed. 01
July 2006
NR7.4 Installation Guide
Ed. 02
November 2006
NR7.4 new addendum issue.
1354BM ATM has been included.
178
HISTORY
02
6 / 178
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.
ANV P/N
1350
PRODUCT
RELEASE
VERSION (N.B.)
ANV P/N
1350
7.4
7.4
N.B.
ED
PRODUCT
02
3AL 88924 BAAA
178
7 / 178
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 7 consists of the following handbooks:
REF
[1]
1350 Rel7.4
Installation Guide
[2]
1350 Rel7.4
Administration Guide
THIS
HANDBOOK
[4]
ED
02
3AL 88924 BAAA
178
8 / 178
REF
ED
HANDBOOK
[5]
1353NM 7.3
Administration Guide
[6]
1354RM 7.4
Administration Guide
[7]
1354BM 7.1A
ATM Administration Guide
[8]
1354BM 7.3E
ETH Administration Guide
[9]
1354BM 7.2R
PR Installation Guide
[10]
1355VPN 5.0
Administration Guide
[11]
[12]
[13]
1359IOO 5.2
Administration Guide
[14]
1359ISN 5.0
Administration Guide
[15]
1354SY 7.4
Administration Guide
THIS
HANDBOOK
or note
02
3AL 88924 BAAA
178
9 / 178
UNIX is a registered trademark of UNIX System Laboratories in the U.S.A. and other countries.
1.6 Overview
This document describes how to install and configure the HP 9000 computer systems in order to allow the
correct usage of the Alcatel NMS application Software.
1.7 Conventions
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.
..,sys,root #
..,$
..,oracle>
SQL>
ED
02
3AL 88924 BAAA
178
10 / 178
2 INTRODUCTION
This document describes how to install Alcatel Network Management Subsystem (NMS) on a HP 9000
system devoted to this purpose. The initial installation is foreseen for machine where the operating system
is not installed, it includes HPUX 11i V1 for PARISC and the third party software requested by an
NMS and NMC.
If you have HP 9000 system already installed for NR7.4, you can use this document for installing a new
NMS, new NMC or create new NMS instance (refer to chapter 4 Add New NMS/NMC at page 127).
If the machine has been installed with previous NR7 platform, it is suggested to evaluate the opportunity
to upgrade the current installation to NR7.4 following the 1350 Upgrade guidelines [4].
2)
The installation can not be performed if the LAN card it is not connected to the LAN plug or a
stand alone Ethernet Hub.
ED
02
3AL 88924 BAAA
178
11 / 178
To be able to perform Alcatel TMN systems installation you have to be able to perfomor some actions by
using HP9000 server console and some other have to done via Graphical User Interface (GUI), for these
reasones the personal computer must be equipped with one RS232 and one Local Area Network (LAN)
ports. The RS232 port have to be connected with the HP 9000 server console (see the HP 9000 server
specific documetaion to know how to find it).
Hereafter an example that shows how to connect HP 9000 L1000 server console to a PC. HP 9000 server
class L, A, N and rp are equipped with a specific processor that allows the system remote control. This
procssor name can be Guardian Service Processor (GSP) or Managenet Processor (MP) depending by
model. In both cases it has a RS232 port where a A519163001 cable has to be connected to. The
A519163001 is call W cable, bacuse you have just a 25 pins RS232 connector splitted in three 9 pins
connectors, and one of them is mark with Console:
Lan Connector RS232 Connector
GSP/MP Connector
A519163001
WCable
Console connector.
A F/F Adapter cable have to be used to connect the PC RSR 232 port with the A519163001 Wcable
console. The cable schema is shwon in Figure 2.
3
Tx
Tx
Rx
Rx 2
RTS
RTS 7
CTS
CTS 8
DSR
DSR 6
S.G.
S.G. 5
DCD
DCD 1
DTR
DTR 4
RI
RI
ED
02
3AL 88924 BAAA
178
12 / 178
2.1.1.2 Requested PC
The system can not share the same physical hardware, that means to implement a
multiple volume system you need al least one hard disk drive for each data volume.
Where:
<Unix>
<Software>
Means the amount of requested disk space for storing the software. Its value
can be computed by summing the code size defined by each NMS you have to
install, refer to Table 10. (page 149).
NOTE: OSKernel has to be always installed.
ED
02
3AL 88924 BAAA
178
13 / 178
Means the amount of requested for data storage. If you are computing the value
for a single volume system, you sum the data size defined by each NMS
instance you have to create, refer to Table 11. (page 149).
For the multiple volume group each NMS instance defines the data size for the
volume group.
<Non protected Data> Means the amount of requested for data storage defined not protected by
1359HA OSCluster. For this kind of data there is no difference in management
between single or multiple volume system, you sum the data size defined by
each NMSinstance you have to install.
Independently by the results of the computation the minimum disk requirement are specified
at the beginning of this paragraph.
N.B.
Example: To install a 1354RM 7.1 with one Master Large instance and 1353NM 7.0 with two Presentation
instances on a HP9000 server equipped with 3Gbyte RAM.
Single volume:
The size of primary swap/dump area will be 3*2*1024 Mbyte=6144 Mbyte, the amount of requested
swap will be: (500+7500)+(500+2*250) Mbyte=9000 Mbyte, so 9000 Mbyte is the higher value, and
it will be used. So the total a mount of operating system you have to add: 6114 Mbyte for HP and
3PP software, 9000 Mbyte for swap areas, and 1536 Mbyte for crash area. The result will be: 16650
The you have to add: 1800 Mbyte for OSKernel, 3600 Mbyte for 1353NM , 1000 Mbyte for 1354RM
to compute the disk space amount for Alcatel Software. Total 6400 Mbyte.
The last the value for the data instances: 8000 Mbyte for 1354RM, 2*100 Mbyte for 1353NM. Total
8200 Mbyte.
16650+(6400+8200)115/100=33440
You need 4x9Gbyte or 2x18Gbyte or 1x36Gbyte. Moreover, if you want to use this system as depot
machine, you have also to add other disks.
Multi Volume:
The difference with the previous is only related to the 1354RM data instance, that will be place in a
different volume group. So the system volume group will need:
16650+(6400+200)115/100=24240
Data volume group:
8000*115/100=9200
For the multiple volume group configuration you need 3x9Gbyte or 2x18Gbyte or 1x36Gbyte for system volume group, and one 9Gbyte or 18Gbyte or 36 Gbyte for the data.
N.B.
ED
IF YOU CONFIGURE THE MIRROR DISK/UX FEATURE, YOU MUST PROVIDE THE
DOUBLE OF THE HARD DISK SIZE COMPUTED.
02
3AL 88924 BAAA
178
14 / 178
<Data>
The NR7 initial installation approach allow to distinguish six main activities:
1)
2)
3)
4)
5)
6)
The following picture shows the NR7 installation process on a server, starting from an empty system up
to an operational one. Each step adds a something new in term of areas, software or references.
Predispose
HPUX
Instance
Creation
HPUX 11i
HPUX 11i
HPUX 11i
NMS2_1_Vx_Master
NMS2_1_Vx_Master
SW copy
NMS2_2_Vx_Master
NMS2_2_Vx_Master
NMS1_1_Vx_Master
NMS2_1_Vx_Client
NMS2_2_Vx_Client
NMS1_1_Vx_Master
NMS2_1_Vx_Client
NMS2_2_Vx_Client
Customize
Integration
File system
OSKernel, NMS
OSKernel, NMS
OSKernel, NMS
HPUX 11i
HPUX 11i
HPUX 11i
Integration reference
ED
02
3AL 88924 BAAA
178
15 / 178
The HPUX 11i operating system installation is performed to setup a new system or recicle an old one,
that is not installed with the right operating system version. The previous hard disk contents will be lost.
2.2.2 Predispose
Predispose allows predisposing HPUX for Alcatel software installation and execution, in terms of: kernel
parameter, file system (size, location), and software layer products. These data have to be provided with
a Software Packages Description (SWPDESC). A specific set of program will prerare the system as requested.
N.B.
This activity can require the system reboot and can be combined with predispose.
Compiles parameter files by setting the values relevant for instance configuration.
2.2.6 Integration
Integration phase allows to join together feature of different NMSs when it is foreseen.
ED
02
3AL 88924 BAAA
178
16 / 178
1354RM
Presentation
1354RM_1_Vy_M
HPUX 11i
1353NM_2_Vx_C
OSKernel, 1353NM Vx
1354RM Vy Software
1353NM_1_Vx_C
1354RM_1_Vy_C
1353NM_2_Vx_C
1353NM_1_Vx_C
1354RM
Master
OSKernel, 1353NM Vx
1354RM Vy Software
HPUX 11i
1353NM_1_Vx_M
1353NM_2_Vx_M
OSKernel,
1353NM Vx Software
OSKernel,
1353NM Vx Software
HPUX 11i
1353NM
Master
HPUX 11i
1353NM
Master
ED
02
3AL 88924 BAAA
178
17 / 178
The 1350 Management Suite is a multilayer architecture where NMS (Network Management SubSystems) can require functionalities provided by other NMSs. This implies dependencies in the system isntallation.
The following figure summarizes the dependencies among the NMSs: NMSs shown in the upper level require the installation of NMS located in the lower layers.
N.B.
1354SY
1354BM
ATM
1354BM
ETH
Mediator
1354BM
PR
1355VPN
1354RM
1353NM
OSKERNEL
N.B.
ED
02
3AL 88924 BAAA
178
18 / 178
Applicable NMS
1359ISN
1354RM
1359IOO
1359HA OSResilience
ED
02
3AL 88924 BAAA
178
19 / 178
2.3 Restriction
N.B.
this configuration is allowed only for machine with up to 512 Mbyte of core memory, for
larger amount of memory the minimum disk requirement is higher.
The boot disk size has to be larger than double of the core memory size.
The machine configuration not included in the List of supported hardware Table 3. at page 32 are
not guarantee.
The usage of hard disk larger than 300 GB is not allowed for booting.
The usage of dual access disks with mirror disk option is not allowed for booting.
OSConf use /etc/lvmpvg to correcly manage the Mirror Disk/UX configuration and file system extension. Manual changes of this file are forbibben!
ED
02
3AL 88924 BAAA
178
20 / 178
3 INSTALLATION
This chapter shows how to install Alcatel Network Management Subsystems on a HP9000 system included in the supported hardware configurations defined in paragraph 3.2.1.1 Check HP9000 Hardware Configuration at page 32.
For upgrade or migration refer to 1350 Management Suite Upgrade Guide 7.4 [4]
VERY IMPORTANT!!
Before proceed in the installation, upgrade or migration you have to visit the OND Technical Excellence Center WEB site (http://tec.ond.alcatel.it/), looking for additional installation notes. This notes are available within Network Release section, selecting:
NR7.4 > installation_notes.
The installation done by following the information provided by this chapter causes the complete removal
of hard disks involved.
The chapter contents:
Quick Installation
ED
02
3AL 88924 BAAA
178
21 / 178
a quick installation guide for speed up the installation task. The current edition of the document provides
information useful for installing the Alcatel NMS/NMC HPUX based software.
Before start with installation it is strong recommended to read the software release notes
and check on the related Product Support Center WEB site for any warning and known
problems!
Insert CDROM SWPOSCONF_BOOTV7.1.1 (1/1 in case of DVD, 1/2 in case of CD) in the
driver.
Boot or reboot the system from CD/DVD.
Reply the question issued:
Enter IP address
Enter the default gateway and subnetwork mask when they are present.
NOTE: the procedure check default gateway executing a ping
Enter the memory size to be used for swap area configuration, you can leave the default value.
Enter CDROM device to be used as default source media, you can leave the default value
Choose to install and configure mirrored disks only if there is the related license.
Choose to install and configure Hp Storage Work Virtual Array only when HP VA7110 disk storage is present in the hardware configuration.
When the mirror disk has been selected, also the alternate boot disk will be required.
The system will perform the requested activities in unattended mode. Wait the end of installation, it can
take from 30 up to 90 minutes. When the system will prompt you for logging, log in as root and check
in /SCINSTALL/scinstall.log for any error before proceed.
For more information see at Chapter 3.2 at page 32.
ED
02
3AL 88924 BAAA
178
22 / 178
If you have to install many systems, you have now the opportunity to create a software depot that allow
you to proceed in the installation without swap CD from a machine to the other, refer to paragraph 3.3.3
at page 60 and 1350 Rel7.4 Administration Guide [2].
ED
02
3AL 88924 BAAA
178
23 / 178
Now you have to predispose in one shot the entire system, that means you must know which system configuration you have to create, in term of software and data. Because there are some possible Alcatel NMS/
NMC combinations, it is advisable to identify the software and the data instances you have to predispose
for before stating.
Now you can start the predisposal by running scmanageswp as shown hereafter:
The list of software available for predispose will be shown, select the item you want to predispose for by referring the column identified by <Product> S.
When all of them have been selected, enter q[Enter] until you do not get to the SWP MAIN
MENU.
You have now to create the data instance for the software by choosing the items from the list,
but considering the following rules:
Create the NMS Instances Master and/or Presentation, taking also into account the functional dependencies shown in paragraphs 2.2.7 and 2.2.8 at page 19.
For each instance selected, a set of questions will be issued (for more info refer to paragraph
Predispose for Installing 3.3.7 at page 64):
Choose one of the possible instance foreseen for the software show as a list.
When all the foreseen software data instance have been declared, enter q[Enter] until you do
not get to the SWP MAIN MENU.
The list of the pending action will be shown, if everything is correct enter: a [Enter] to start the
predisposal.
The procedure will compute the system requirements in terms of disk space, and it can ask you
for add unused available disks to the current configuration (see paragraph 3.3.7.6.3 at page 82
for more info).
Then, it will ask you for the third party software, you can choose to retrieve it from depot (if any)
or from CD ( see paragraph 3.3.7.6.1 at page 81 for more information).
ED
02
3AL 88924 BAAA
178
24 / 178
Then the procedure will show you just some trace, asking you sometimes to press enter to continue.
After the following message you have to press [Enter] key to perform the system reboot:
=>>> WARNING: Now SCINSTALL will be invoked to activate the mod...
The installation will run unattended !!!
Press [Enter] to continue.
ED
02
3AL 88924 BAAA
178
25 / 178
Printers
Enter 1 at OSConf xntp Protocol Configuration menu prompt to Add a new NTP server.
Enter the time server host name (if defined in /etc/hosts) or IP address.
Set it as preferred.
If you have more than one time server, execute again a ) and b ), but do not set the second as preferred.
d)
e)
f)
g)
h)
ED
Enter 9 at OSConf xntp Protocol Configuration menu prompt to Align the time to server.
Enter 8 at OSConf xntp Protocol Configuration menu prompt to Start/Stop NTP server.
If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter y to configure NTP daemon to start automatically at system startup.
Start the NTP daemon replaying with y[Enter] to message:
NTP server is stop
Would you like to start it (y/n) ?
Exit by entering e[Enter] at OSConf xntp Protocol Configuration menu prompt.
02
3AL 88924 BAAA
178
26 / 178
f)
Enter 5 at OSConf xntp Protocol Configuration menu prompt to Configure NTP on local clock.
Enter y[Enter] at the question:
Would you like to set Local Clock as preferred source (y/n) ?
Enter 8 at OSConf xntp Protocol Configuration menu prompt to Start/Stop NTP server.
If the message Would you like to start xntpd automatically at reboot (y/n) is
shown, enter y to configure NTP daemon to start automatically at system startup.
Start the NTP daemon replaying with y[Enter] to message:
NTP server is stop
Would you like to start it (y/n) ?
Exit by entering e[Enter] at OSConf xntp Protocol Configuration menu prompt.
If you have a network management with up to two HP 9000 systems, you have to define one of them
as license server, and ask for a single node license.
If you have three or more systems, you have to choose three of them and ask for a three server redundant license.
N.B.
N.B.
The license have to refer to the license server host identifier and NOT to the server
where the application have to be run on.
For each license server you have to retrieve the system host identifier by entering:
For Alcatel license:
...,sys,root # /opt/poseidon/bin/lmhostid [Enter]
For GraphOn license: ...,sys,root # /opt/graphon/bin/lmhostid [Enter]
The shown host id have to be provided during the license request, for the three server redundant configuration all three host id have to be provided at once.
Retrieve the license file, and edit it by adding the port number 27010 at the end of each SERVER line
in the Alcatel license file, instead 27011 in the GraphOn GoGlobalUX one.
3.1.3.3.2 Alcatel License Setup
Store the license file into the file /opt/poseidon/etc/license.dat of any machine.
Verify the license server are correctly declared within /etc/hosts file.
Start the license daemon on any machine by entering the command:
...,sys,root # /sbin/init.d/poseidon stop [Enter]
...,sys,root # /sbin/init.d/poseidon start [Enter]
3.1.3.3.3 Check the license server
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat a c /opt/poseidon/etc/license.dat[Enter]
ED
02
3AL 88924 BAAA
178
27 / 178
Store the license file into the file /opt/graphon/etc/license.dat of license server machines, create
file /opt/graphon/etc/license.dat with a line like the following for each license server:
SERVER <hostname> 27001
Copy this file in the same location of each NMS machine.
Verify the license server are correctly declared within /etc/hosts file.
Start the license daemon on any machine by entering the command, on each machine.
...,sys,root # /sbin/init.d/goglobalux stop [Enter]
...,sys,root # /sbin/init.d/goglobalux start [Enter]
3.1.3.3.5 Check the license server
To check the license server availability and license status enter the command:
...,sys,root # /opt/poseidon/bin/lmstat a c /opt/poseidon/etc/license.dat[Enter]
3.1.4 Install and Customize Alcatel Software
Finally you are ready to install and customize the Alcatel software on the target system. This activity is
performed by the Alcatel Install Wizard just following this short procedure:
N.B.
Before start check if you have the necessary CDROM or an accessible depot with the entire
software.
N.B.
Check if the depot machine or distribution CD are available, and if local system is correctly authorized to access the files (see 3.3.5.2 and 3.3.5.3 for more informations).
From CDROM:
N.B.
Do not interrupt the procedure!
Once installation phase will be completed, the procedure will request a confirm for the execution of
the customization tool, confirm the operation.
When the procedure will be terminated, verify that no error are shown (warnings can be ignored).
ED
02
3AL 88924 BAAA
178
28 / 178
NMS/NMC Name
Description
1353NM
7.3 (7.3.6)
1354BM ETH
1354BM ATM
7.1.4
1354BM PR
7.2 (7.2.4)
1354RM
7.4 (7.4.3.2)
Regional Manager
1354SY
7.4 (7.4.0.2)
Synchronization Manager
1355VPN
5.3 (5.3.0)
1359HA OSReslience
1359IOO
5.2 (5.2.0.5)
1359ISN
5.0 (5.0.0.5)
The NMS and NMC installation and customization have to be executed with graphical interface.
Login the system with graphical interface as root user.
Change directory: ...,sys,root # cd /alcatel/Install_Wizard [Enter]
Install and customize the designed software package (NMS/NMC) by entering:
From CDROM:
N.B.
Do not interrupt the procedure!
1353NM Only: The 1353NM installation will require you to confirm the installation of the 1353SH 5
and 6 interface feature (see paragraph 3.5.3 at page 111 for more information):
NOTE: Do you want to execute 1353NM Install package to manage NR5/6
1353SH? [y|n|q]
ED
02
3AL 88924 BAAA
178
29 / 178
Once installation phase will be completed, the procedure will request a confirm for the execution of
the customization tool, confirm the operation.
The Custom interface will show you the System Instances List window, you have to select
Choose_one button and set it to NewInstance, then Apply & exit in the Actions menu.
The custom Parameters Definition window will be shown on the screen, it allows you to set the relevant NMS/NMC variables.
Set the value, then Apply & exit in the Actions menu to start the execution.
1353NM Only: An additional window will be shown to select an Element Manager subset (see 3.5.3.2
a page 114 for more information).
When the procedure will be terminated, verify that no error are shown (warnings can be ignored).
Check also /alcatel/Install_Wizard/log/Installer_<NMS/NMC Name>_*.log trace file.
Then at the System Instances List window, you have to select Choose_one button and set it to
NewInstance, then Apply & exit in the Actions menu.
The custom Parameters Definition window will be shown on the screen, set the relevant for the next
instance of NMS/NMC.
Now you have to proceed with the specific NMS/NMC configuration, refer to the NMS/NMC specific administration guide.
When the configuration of the current system will be performed, you can proceed with the installation, customization and configuration of the next machine.
When all TMN systems will be installed, customized, configured, and connected via TCP/IP, you can proceed with the integration.
ED
02
3AL 88924 BAAA
178
30 / 178
In case of a 1354BMPR Master that has to be integrated with a 1354RM or 1353NM, do not integrate
PLT and Backup/Restore (SMF) when requested.
Here is an example :
...
NOTE: 1354RM_17.1: MasterMaster Communication Integration (PLT) of 1354BMPR_17.2 can be
performed...
1354RM_17.1: Run the PLT Integration of 1354BMETH_17.3? [y/n] n [Enter]
NOTE: 1354RM_17.1: Backup/Restore Integration (SMF) of 1354BMPR_17.2 can be performed...
1354RM_17.1: Run the Backup/Restore Integration of 1354BMETH_17.3? [y/n] n [Enter]
...
NOTE: 1353NM_17.0: MasterMaster Communication Integration (PLT) of 1354BMPR_17.2 can be
performed...
1353NM_17.0: Run the PLT Integration of 1354BMETH_17.3? [y/n] n [Enter]
NOTE: 1353NM_17.0: Backup/Restore Integration (SMF) of 1354BMPR_17.2 can be performed...
1353NM_17.0: Run the Backup/Restore Integration of 1354BMETH_17.3? [y/n] n [Enter]
ED
02
3AL 88924 BAAA
178
31 / 178
This chapter describes the first part of initial installation, it explains how to perform a HPUX 11i Operating
System installation.
N.B.
Optional Cards
HP9000 Model
Workstation B2000
B5509BA
A4974A
C6362A
Workstation B2600
B5509BA
A4974A
C6362A
A5220A
A4107A
J3516A
A3312AZ
A5220A
A4107A
J3516A
A3312AZ
28696A
A5557A
A5230A
C6364A
C5708A
ED
02
3AL 88924 BAAA
178
32 / 178
HP9000 Model
Optional Cards
Server RP2430
A5230A
C4314A
C6364A
Server N4000
A5838A
A5272AZ
C4318SZ
Opt. 108
C6365A
A4800A
C6379A
A6795A
A6250AZ
A7295AZ
Server RP5430
A5557A
A5230A
C6364A
A5557A
C5687B
A6795A
A6250AZ
A7295AZ
Server RP7400
A5838A
A5272AZ
A6795A
A6250AZ
C7508AZ
C7499A
A7295AZ
Server RP7410
A5838A
A5272AZ
A6795A
A6250AZ
C7498A
C7456A
C7499A
A7295AZ
Server RP3410
C5687C
A9919A
Server RP3440
C5687C
A9919A
Server RP4440
A7163A
A6795A
A6250AZ
A5230A
The HP 9000 server cable connections are shown in APPENDIX D at page 167.
ED
02
3AL 88924 BAAA
178
33 / 178
When a Virtual Array is powered on for the first time it is possible that you have to format disks to be able
to access it.
To proceed with the Virtual Array format you must connect the console terminal to the RS232 port of either
array controller (refer to HP Virtual Array Installation Guide for more information).
As soon as you have connected the console press [Enter] key, and the VA have to reply with the prompt.
The prompt shows the VA status followed by major sign >, you have to check if the status value is ready,
if it is not, wait up to ten minutes,to allow the start up termination. If after ten minutes the status is still different than ready , you have to try the full reset of the VA by entering:
...> vfpmgr r full [Enter]
Do not perform the Virtual Array format on a system already operational, the format command destroys all the data present on the system!
When the reset is completed, check again the VA status, if the status is still Not Ready and especially
if the status is No map you have to format it by entering the command:
No map> vfpfmt [Enter]
The command will also reset the VA, if also with the format the status do not change to Ready, call the
hardware support.
ED
02
3AL 88924 BAAA
178
34 / 178
Hostname:____________________________
TimeZone:_______________________
Gateway Address:_____._____._____._____ Subnet Mask:_____._____._____.______
Core Memory Size:________________
Source Device:/dev/dsk/________________
No
N.B.
IP Address,Gateway Address, Subnetmask and Hostname must be defined in agreement with the Customer TCP/IP addressing plan. Be careful with IP Address and Hostname, because it can be some times
impossible to change them later.
Timezone is usually the time zone where the system is located and the definition is simplified by the menu
that shows you the possible areas. Do not define the local time with GMT0 time zone, except if the
system is really located in Greenwich time zone area.
For Core Memory Size it is intended the amount of RAM equipped on the system, it is automatically detected by the procedure and shown as default choice, you have just to confirm if the shown value is correct.
Mirror Disk/UX and The CommandView SDM are HP software that can be installed on demand. Both
of them are available only for 64bit processor and can be installed only if the Customer had bought the
license. The installation of these software is forbidden on system where there is no evidence of the
related license royalties to HP.
Source Device means the CDROM or DVDROM device will be used to retrieve the software. It is automatically detected by the procedure.
The last information requested is related to the disks. The System Boot disk is the hard disk on which HP
UX will be installed on, the required space is 8 Gbyte(1), and the minimum disk size allowed is 4 Gbyte.
If the Mirror Disk/UX as been requested, the procedure will issue also the request for the alternate boot
disk.
(1) HPUX 11i required at least eight Gbyte with a machine with up to one Gbyte of RAM, the operating
system can be stored in two four Gbyte disks.
ED
02
3AL 88924 BAAA
178
35 / 178
The following list summarizes the actions performed during the operating system installation:
3)
4)
5)
6)
7)
8)
Hostname
IP address
Subnetmask [Optional]
Gateway [Optional]
Source device
1)
2)
(2)The Alternate Boot disk is asked only when the Mirror/Disk UX has been selected.
ED
02
3AL 88924 BAAA
178
36 / 178
N.B.
ED
Device Path
Device Type
SESCSI.2.0
FWSCSI.6.0
FWSCSI.5.0
TOSHIBA CDROM
SEAGATE ST34572WS
SEAGATE ST32171W
02
3AL 88924 BAAA
178
37 / 178
P0
P1
P2
Device Path
Device Path(mnem)
10/0.6
10/12/5.3
10/12/6.0
SESCSI.2.0
FWSCSI.6.0
FWSCSI.5.0
Device Type
Path Number
N.B.
This is an example of another modality to display the devices for the 64bit series server:
Path Number
P0
P1
P2
P3
P4
N.B.
Device Path(dec)
Device Type
8/4.9
8/4.8
8/16/5.6
8/16/5.2
8/16/6.0
Random access
Random access
Random access
Random access
Lan Module
media
media
media
media
In this case, the driver is connected to SCSI Single Ended Target 2 (8/16/5.2).
Insert the bootable CDROM 1/2 or DVD 1/1 into the driver.
When the LED of the CDROM device stops blinking, boot by entering the boot command:
Main Menu: Enter command or menu > boot P<n> [Enter]
where P<n> is the path number corresponding at the driver.
The system asks you if you want to perform an interactive boot, reply as shown below:
Interact with IPL (Y, N, Q) > n [Enter]
Booting...
ISL Revision A.00.43 Apr 12, 2000
ISL booting hpux (;0): INSTALL
Boot
...
The system shows you the start of boot with the following message:
ALCATEL INSTALLATION PROCEDURE
OSCONF Technology
__________________________________________________________________________
__________________________________________________________________________
ED
02
3AL 88924 BAAA
178
38 / 178
1)
3)
5)
7)
9)
11)
13)
15)
17)
19)
21)
23)
25)
27)
USB_PS2_DIN_Belgian
USB_PS2_DIN_Danish
USB_PS2_DIN_Euro_Spanish
USB_PS2_DIN_French
USB_PS2_DIN_German
USB_PS2_DIN_Italian
USB_PS2_DIN_JIS_109
USB_PS2_DIN_Norwegian
USB_PS2_DIN_S_Chinese
USB_PS2_DIN_Swedish_Euro
USB_PS2_DIN_Swiss_German2
USB_PS2_DIN_T_Chinese
USB_PS2_DIN_UK_English_Euro
USB_PS2_DIN_US_English_Euro
2)
4)
6)
8)
10)
12)
14)
16)
18)
20)
22)
24)
26)
USB_PS2_DIN_Belgian_Euro
USB_PS2_DIN_Danish_Euro
USB_PS2_DIN_Euro_Spanish_Euro
USB_PS2_DIN_French_Euro
USB_PS2_DIN_German_Euro
USB_PS2_DIN_Italian_Euro
USB_PS2_DIN_Korean
USB_PS2_DIN_Norwegian_Euro
USB_PS2_DIN_Swedish
USB_PS2_DIN_Swiss_French2_Euro
USB_PS2_DIN_Swiss_German2_Euro
USB_PS2_DIN_UK_English
USB_PS2_DIN_US_English
ED
02
3AL 88924 BAAA
178
39 / 178
To allow the set up of time zone and time of the system related to the geographical location of the machine
the program issues a sequence of menu, choose the time zone appropriate for the country where the machine will be operative.
In the following an example shows how to set the Middle European Time Daylight Saving Time (MET
DST), if you are not in the middle European area you have to choose your timezone:
At the first question you have to enter the number of the seven areas of the world:
__________________________________________________________________________
__________________________________________________________________________
The following procedure enables you to set the time zone.
Select your location from the following list:
1) North America or Hawaii
2) Central America
3) South America
4) Europe
5) Africa
6) Asia
7) Australia, New Zealand
___________________________________________________________________________
Enter the number for your location (17) then press [Enter] 4 [Enter]
The items of the next question depends by the area chosen in the previous one, for Europe these will be
the following:
___________________________________________________________________________
Select your time zone from the following list:
1) Greenwich Mean Time
It the choice is correct enter y [Enter], to confirm your selection an go on with the next section.
ED
02
3AL 88924 BAAA
178
40 / 178
If you confirm the procedure will go on, otherwise it will go back asking again for the date and time.
ED
02
3AL 88924 BAAA
178
41 / 178
This section of the program ask you to enter the mnemonic name of the machine also known as hostname.
Enter the hostname foreseen for machine following the guide line shown in the instruction:
The Hostname must contain only numbers and alphabetic characters in lower case,
starting with an alphabetic character.
Upper case and special characters are FORBIDDEN!
This section enables you to enter Hostname.
___________________________________________________________________________
For the system to operate correctly, you must assign it a unique
system name or hostname. The hostname can be a simple name (example:
widget)
A simple name must:
* Start and end with a letter or number.
* Contain no more than 8 characters.
* Contain only letters, numbers, underscore (_), or dash ().
The underscore (_) is not recommended.
NOTE: The hostname should contain 8 characters or less
for compatibility with HPUX uname.
The current hostname is unknown. You cannot configure networking
or run HPCDE if the hostname is unknown. Please choose another name.
___________________________________________________________________________
Just pressing [Enter] will keep the (not recommended) name unknown
Enter the system name [unknown]: hosta[Enter]
Enter the hostname and press [Enter] key, then procedure will ask you to confirm your choice, if you enter
the right name confirm it by entering y [Enter].
You have chosen hosta as the name for this system.
Is this correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
ED
02
3AL 88924 BAAA
178
42 / 178
134.32.3.10
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
ED
02
3AL 88924 BAAA
178
43 / 178
This section allows to define the subnetwork mask and the gateway, these two information are fundamental to allow your system to access machines place by outside of your LAN. If your system does not need
to communicate with machines outside your LAN you can skip this section by answering n to the next
question. Its also suggested to skip this section if you do not have the subnetwork mask and gateway information or simply your machine is stand alone.
Even in case your machine is stand alone, it is mandatory to connect the primary lan card
to a network hub or switch.
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
This section enables you to specify the subnetwork mask and default
network gateway. This information is necessary if your network has
gateways and you wish to communicate beyond your local subnetwork.
You will need to know the following information:
* Subnetwork mask
* Default gateway IP address
___________________________________________________________________________
Do you wish to specify this information?
Press [y] for yes or [n] for no, then press [Enter]
In case you do not have the subnet mask and default gateway information available skip this section by
entering n [Enter] and go to paragraph Swap/Dump Sizing 3.2.2.1.8 at page 46, otherwise enter y[Enter]
and proceed with the following:
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information.
Example:
Subnetwork mask:
255.255.255.0
Gateway IP address: 192.200.49.1
Current Settings:
> Subnetwork mask:
255.255.255.0
(default)
Gateway IP address: 192.200.49.1
(default)
___________________________________________________________________________
ED
02
3AL 88924 BAAA
178
44 / 178
The procedure will update the window contents (Current Setting) with new value and it will prompt you for
the gateway address:
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information.
Example:
Subnetwork mask:
255.255.255.0
Gateway IP address: 192.200.49.1
Current Settings:
Subnetwork mask:
255.255.255.0
> Gateway IP address: 192.200.49.1
(default)
___________________________________________________________________________
Enter the gateway address [192.200.49.1]:
The procedure shows you a default IP address for the gateway, if it corresponds to the right one, just confirm it by pressing [Enter], otherwise enter the correct one and [Enter]
___________________________________________________________________________
Additional Network Parameters: Subnetwork Mask and Default Gateway
Enter the subnetwork mask and default gateway information.
Example:
Subnetwork mask:
255.255.255.0
Gateway IP address: 192.200.49.1
Current Settings:
Subnetwork mask:
255.255.255.0
Gateway IP address: 192.200.49.1
___________________________________________________________________________
Are the parameters above correct?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
Before proceeding with the next step the program shows the entered data asking to confirm them. If you
do not confirm, the procedure goes back to subnetmask data entry.
A ping to the provided gateway is also attempted to verify the correct configuration of both local and gateway IP address, and in the mean time the correct subnet mask. If the ping fails the operator will be required
to confirm his/her data entry
.... Waiting, ping system 192.200.49.1
___________________________________________________________________________
ED
02
3AL 88924 BAAA
178
45 / 178
The HPUX swap dimensioning rule foresees to create a swap area large as the double of the core
memory, this rule is also followed by the OSConf installation script, but to allow different approaches the
capability to define different size of the core memory is provided.
This step in the procedure shows you the amount of core memory detected and ask you to confirm.
This section enables you to enter size of primary SWAP/DUMP area.
___________________________________________________________________________
___________________________________________________________________________
The primary SWAP/DUMP area is: 2046 Mbyte
Just pressing [Enter] will keep this primary SWAP/DUMP size,
enter new value if you wish to change size.
___________________________________________________________________________
Enter primary SWAP/DUMP size in MByte [2046]:
The shown value is the primary SWAP/DUMP disk area size, it corresponds to the current amount of RAM
Core memory, Press [Enter] to confirm it or enter a different value in order to increase on reduce the disk
space used for primary SWAP/DUMP. The total amount of swap space requested will be adjusted if needed.
N.B.
ED
Do not enter a value less then 50% of RAM size, it can prevent the DUMP creation.
02
3AL 88924 BAAA
178
46 / 178
Now the program is scanning the hardware looking for the present hard disks, it will take a few seconds.
Hardware detection in progress, please wait ...
Total Disk(s)
Total CD/DVD(s)
found =
found =
2
1
ED
02
3AL 88924 BAAA
178
47 / 178
Before proceeding in the hard disk assignment rules it is mandatory to define if there is any high availability
feature or device in the system. First of all, if the disk mirroring has to be implemented by procedure you
have to reply y to the next question:
This section enables you to choose for Mirror Software option.
___________________________________________________________________________
The Mirror/Disk UX software allow
the disks, to prevent system down
the license of use and the double
mirror option.
Have you to install a machine with
Press [y] for yes or [n] for no, then press [Enter]
To implement the disk mirroring you need to have the HP Disk Mirror/UX licence and double of the disk
space requested without the feature, for these reasons the procedure issues the following confirmation
question:
N.B.
The installation of the HP Disk Mirror/UX software without license is not allowed
WARNING
To be able to install and configure mirror software the following
requirements must be matched:
You MUST have evidence of HP Disk Mirror/UX software license
customer ownership
The hardware configuration MUST have a spare hard disk for each
one in use
Are both requirements satisfied ?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
If you have the required items just replay with y[Enter].
Choosing the Disk Mirror/UX installation the procedure automatically configures the mirror feature on any
Volume Group youll create in the system by using the feature of OSConf. To perform this activity the
installation will take 30 minutes more and the machine will be rebooted twice.
ED
02
3AL 88924 BAAA
178
48 / 178
The installation of the virtual array disk storage software is not allowed if the hardware
is not present!
ED
02
3AL 88924 BAAA
178
49 / 178
The next phase in the procedure bring you to define the disk configuration. The request issued by this activity depends by the previous answer. That means if you had chosen to have the disk mirror capability the
procedure will ask you disk drive to be able to make a copy of all the data. To obtain the higher availability
level is suggested to choose disk connected to different controllers. For a correct disk management it is
advisable to define the disk usage policy in advance.
3.2.2.1.12.1 Disk Mirror Configuration Policy
The disk mirror capability is used for two main purposes:
1)
2)
It is possible to obtain the better high availability goal only with a correct configuration of the disk resources
available on the system. HPUX Mirror Disk/UX allows to reach the first target without specific configuration, but to be able to reach the second one you must have an appropriate system configuration in terms
of hardware and software. The hardware suggested by Alcatel are design to allow mirror configuration that
allow system to survive to disk controller failure, but the software configuration has to be done as shown
in this paragraph to do not loose this capability.
First of all you have to be able to identify the hard disk present in the configuration, them are usually identified by their file name. In particular the file name can be very helpful to identify the disk controller relationship. Any disk in the configuration is identified by the following name: c#t#d#
c[015]
t[015]
d[015]
SCSI of Fiber Channel card instance of disk controller to which the disk is attached to.
SCSI of Fiber channel address of the device on the interface.
Is the device unit number, useful for disk array only, such as VA7110.
Using the c# of disk file name is possible to identify the relationship between disks and controllers.
HPUX allows to connect a single disk to two different controller (DualAccess), in this case the system
command can show two device file for the same disk units, but the installation script manage this configuration by showing just one device with a D on the first column of the related line, hereafter an example of
the selection menu shown by installation scripts:
This section enables you to select the boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte
Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8672
0/0/1/1.2.0
_(free)_ ______
________
c2t2d0
8672
0/0/2/0.2.0
_(free)_ ______
________
D c4t8d0
8672
0/4/0/0.8.0
_(free)_ ______
________
D c4t9d0
8672
0/4/0/0.9.0
_(free)_ ______
________
c6t12d0
8672
0/7/0/0.12.0
_(free)_ ______
________
c6t13d0
8672
0/7/0/0.13.0
_(free)_ ______
________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
ED
02
3AL 88924 BAAA
178
50 / 178
Now you have to define two disk group (physical volume group) with the following characteristics:
1)
2)
3)
N.B.
The sum of disk space amount of the two group have to be the same.
The DualAccess disks can be assigned to any group.
The non DualAccess disks connected to the same controller MUST belong to the same group.
It is important to follow this rules starting from boot disk definition 3.2.2.1.12.2 at page
52.
The following picture is a schematic example of disk configuration that can produce the output shown before. This is not a typical system, but provided all the case that can occur in field.
c1t2d0
c2t2d0
c4t8d0
c6t12d0
c4t9d0
c6t13d0
ED
02
3AL 88924 BAAA
178
51 / 178
The first disk you have to select is the main boot disk for the system, the list of the available disk will be
shown in the window in the following format:
This section enables you to select the boot disk device.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8672
0/0/1/1.2.0
_(free)_ ______
________
c2t2d0
8672
0/0/2/0.2.0
_(free)_ ______
________
D c4t8d0
8672
0/4/0/0.8.0
_(free)_ ______
________
D c4t9d0
8672
0/4/0/0.9.0
_(free)_ ______
________
c5t12d0
8672
0/7/0/0.12.0
_(free)_ ______
________
c5t13d0
8672
0/7/0/0.13.0
_(free)_ ______
________
___________________________________________________________________________
Select Primary BOOT Disk device Name :
Enter the disk device that will be used as boot device then press [Enter].
A D character is shown before the device name in the Device column to advice the disk is
accessible via two different disk controllers. This configuration is typically used with Fiber Channel device.
N.B.
ED
02
3AL 88924 BAAA
178
52 / 178
To install minimum HPUX configuration on a machine with 512 Mbyte, 8 Gbyte of hard disk are required.
If you provide 4 Gbyte or smaller hard disks, the procedure will prompt you again until the requested
amount of disk space will be reached.
ED
02
3AL 88924 BAAA
178
53 / 178
After this confirm question the contents of the selected disk will be lost.
___________________________________________________________________________
Disks Selection
___________________________________________________________________________
Device
MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c1t2d0
8672
0/0/1/1.2.0
Pri_Boot _Main_
vg00
c2t2d0
8672
0/0/2/0.2.0
Alt_Boot Mirror
vg00
D c4t8d0
8672
0/4/0/0.8.0
_(free)_ ______
________
D c4t9d0
8672
0/4/0/0.9.0
_(free)_ ______
________
c5t12d0
8672
0/7/0/0.12.0
_(free)_ ______
________
c5t13d0
8672
0/7/0/0.13.0
_(free)_ ______
________
___________________________________________________________________________
These are your Disks Selection x HPUX installation on this system.
ATTENTION: The contents of selected disks will be permanent lost
Do you want CONTINUE?
Press [y] for yes, [n] for no or [q] to quit then press [Enter]
If you are sure of your choice enter y[Enter], then the procedure will start the execution phase.
This is the last question issued by the procedure, after your reply the
procedure will operate unattended.
The procedure executed by a HP9000 L1000 server will take:
45 minutes for operating system
+30 minutes to install and configure mirror
Dont worry if the machine reboots automatically.
ED
02
3AL 88924 BAAA
178
54 / 178
When all the disk selection will be completed, the program will ask you to confirm your choice.
To create the physical volume on the alternate boot disk (only for mirror disk configuration).
To set the alternate boot path (only for mirror disk configuration).
To reboot the system to activate the HPUX installed on the hard disks.
To install the Mirror/Disk UX and related patches (only for mirror disk configuration).
To configure the mirror for all the Logical Volumes (only for mirror disk configuration).
ED
02
3AL 88924 BAAA
178
55 / 178
In case any error is met during the execution phase, the procedure stops and the following message is
issued:
******************* THIS SYSTEM IS NOT CORRECTLY INSTALLED ****************
To fix the problem, check the log file in /SCINSTALL/scinstall.log
***************************************************************************
The procedure it is not able to recover the error by itself, look at the log file to have more information about
the error.
ED
02
3AL 88924 BAAA
178
56 / 178
b)
c)
Secadmin will prompt you asking for username, you have to replay with: Administrator
N.B.
d)
e)
secadmin will prompt you with: <secadmin on <hostname> >: . At this prompt you have to enter
the user definition commad:
<secadmin on ... >: add user <username> group Administrator host <hostname> [Enter]
Where:
<username> means the user you whant to create.
<hostname> is the same hostmane entered staring secadmin.
f)
secadmin will prompt you to enter the password twice without echo of input by issuing the following
two prompts:
password:
reenter password:
N.B.
Do not leave the password empty, an emply password does not allow the correct login to
CommandView Java interface.
g)
h)
Example:
...,sys,root# secadmin host ipb083
username: Administrator
password:
<secadmin on ipb083>:add user root group administrator host ipb083
password:
reenter password:
<secadmin on ipb083>:list
Username Group
Host
root
Administrator ipb083
<secadmin on ipb083>:exit
ED
02
3AL 88924 BAAA
178
57 / 178
When the HPUX 11i operating system installation is completed, the system is not yet ready for Alcatel
NMS installation; in fact NMS needs some layer software, that are usually called software platform, to be
able to perform their tasks.
3.3.1 OSConf Installation
The OSConf packages have to be installed by following this procedure:
a)
b)
Identify the device driver (see Find the CDROM/DVDROM Device File appendix A.1 at page
145).
c)
Insert the medium with label SWPOSCONF_ADDV7.1.1.P04 volume 1/1 in the driver.
d)
e)
If the procedure is carried out without error, the system is ready to be predisposed.
ED
02
3AL 88924 BAAA
178
58 / 178
Keeping the CD mounted perform the software platform upgrade to OSConf 7.1.1 P04.
a)
b)
The procedure will ask you if the software platform upgrade must be perform by CD/DVD or network
depot.
_________________________________________________________
OSC3PP 7.1.1P04 Upgrade Procedure
LAYERED PRODUCTS Repository
1 CDROM/DVD
2 DEPOT
Insert choice and press [Enter]:
[Enter]
2)
The procedure asks you to enter the CD driver file name, usually the proposed default is correct.
Enter q to Quit or the CD device [def=/dev/dsk/c2t2d0]:
c)
The procedure will check the amount of free space on the file system, and enlarge them when needed. If any enlarged file system is in use, the extension can not be complete, a reboot will be required
by issuing the following message:
N.B.
The file system extension can ask for new hard disk, refer to paragraph 3.2.2.1.12.1
Disk Mirror Configuration Policy at page 50 the rule for the hard disk choice.
___________________________________________________________________
System need reboot x complete extension of file system current ...
___________________________________________________________________
d)
If one or more file system will require the system reboot the following message will be displayed:
ATTENTION
Upgrade OSConf install product(s) and/or Patch(es)
System could automaticaly reboot
All Application must be stopped (example: RM, NM, Resilience ec...)
Do you want continue ?
Press [y] for yes or [n] for no, then press [Enter]
Stop all the activity, if any, and reply with y[Enter].
ED
02
3AL 88924 BAAA
178
59 / 178
The installation can be executed retrieving the software from a local CD or from a network depot. In case
you choose to install from depot you have to define a system with enough disk space available, where
two depots can be created, one for the third party software, that we will call OS_Conf Depot; where you
can store all the software layer distributed by OS_Conf itself, and one for the Alcatel TNM software, that
we will call Alcatel NMS Depot.
To setup the depot you need 2.3 Gbyte for OS_Conf Depot, while the size of Alcatel TNM depends by the
different NMS you plan to install.
The following paragraphs provide the instructions to create the depots.
3.3.3.1 Create OS_Conf Depot
OSConf Depot can be useful when you have to install more than one system, because it allows to execute
simultaneously and unattended installations. The detailed procedure to create the OS_Conf Depot (see
1350 Administration Guide [2] How to create a Network Depot).
3.3.3.2 Create Alcatel NMS Depot
This paragraph shows how to create the depot for Alcatel software. The depot size depends by the software you have to store on the disk, the Table 10. column Depot Package Size at page 149 summarizes
the space required in M bytes.
The following actions must be executed on the depot machine; preferably it should be a machine in the
network. It may be the same machine that you are installing, if you have sufficient free disks space.
You have to login to the alcatel depot machine as root user, and execute the following command:
1)
Extend /alcatel to allow the storage of Alcatel software by entering the command:
...,sys,root # scextendfs /alcatel/DEPOT <required disk size> [Enter]
2)
3)
For each distribution CD Rom that contains the software you have to install:
a)
b)
c)
d)
e)
f)
ED
02
3AL 88924 BAAA
178
60 / 178
Master function
b)
Client function
The Master function provides the set of software programs that allows the machine to perform the network
management, and the Client function to provide the manmachine interface. The two functionalities can
be installed on the same system or on a different one. Where system navigation is foreseen, it is mandatory
to install the NMS Client on the system that has to perform the navigation. Just to clarify the concept look
at the following example: considering system with three machines, the first is installed with both 1354RM
Master and 1353NM clients, where two 1353NM instances have been created with the same identifier of
the two 1353NM master located on the other two systems. In this case it is possible to have 1353NM functionalities at 1354RM level (Navigation).
1353NM Master
1353NM
Client
1353NM
Instan. 2
Client
Instan. 3
1354RM
Master+
Client
Instan.1
1353NM
Master+
Client
Instan.2
OSKernel
1354RM Master with two 1353NM Clients
OSKernel
1353NM Master
1353NM
Master+
Client
Instan.3
OSKernel
Moreover some other software can be installed as component, they are qualified as NMC.
ED
02
3AL 88924 BAAA
178
61 / 178
a)
b)
c)
d)
e)
f)
g)
Fill in the lists of NMS and NMC in APPENDIX B at page 147 where all the foreseen items are shown.
3.3.5 PreInstallation Actions
Hereafter there are some actions that have to be done before installing.
3.3.5.1 Host declaration
The network node description have to be filled in manually, for each host you have to communicate to, you
must add a line with the IP Address followed by the host name in the /etc/hosts file (see Node Name Management paragraph 3.4 at page 88).
3.3.5.2 Authorize Network Loopback Access for CD/DVD installation
Even if the installation is performed locally there are some activities that need the network access to perform their tasks, this is the reason why, to be able to install from CD(or DVD), it is necessary to add a line
in the /.rhosts file (creating it when it doesnt t exist) with the local host name followed by root keyword.
3.3.5.3 Authorize the Retrieval from Depot Machine
This paragraph explains how to authorize the file retrieval from the depot machine, if you do not use any
depot machine skip it.
To be able to retrieve the Alcatel software packages from the depot machine, the access to these files have
to be granted to all the root users of all the machines that have to be installed. This can be obtained by
writing in the /.rhosts file the hostname and the keyword root for each machine, and add a line for each
of them in the /etc/hosts file.
Example: you have to install the following three systems: hosta, hostb and hostc (the depot machine itself).
You have to write /.rhosts this way:
hosta root
hostb root
hostc root
All the host included in .rhosts file have to be defined in /etc/hosts one.
N.B.
ED
02
3AL 88924 BAAA
178
62 / 178
To be able to complete the installation you have to know in advance the answer to the following questions:
e)
f)
3.3.6.2 Install NR7 Installation Procedure and NMS Description from Network Depot
To install NR7 installation procedure from network depot you have to execute the following procedure:
a)
b)
c)
d)
e)
N.B.
ED
If the remote shell (remsh) fails with error: remshd: Login incorrect. check the
depot machine access authorization (see paragraph 3.3.5.3 at page 62)
02
3AL 88924 BAAA
178
63 / 178
The OSKernel modular approach allows to predispose the machine after the hpux Operating System
installation, this is performed on demand by a specific script. In this paragraph will be shown: how to predispose the system to be able to run OSKernel, because it has to be always installed. Then it will be provided
an example of 1353NM, and a generic example for all the other NMS.
3.3.7.1 Start the SWP Manager Script
To be able to start the SoftWare Package predispose script you have to login as root user and enter the
command:
...,sys,root # scmanageswp [Enter]
N.B.
VERY IMPORTANT: The whole installation has been described as a single predispose action. This means you have to predispose all the NMS and NMS instances in one shot. This
allows to save time and to do not meet problems in disk space computation. If you have
to interrupt the predisposal in the middle of the selection, exit the procedure choosing
Exit to abort the procedure itself.
ED
02
3AL 88924 BAAA
178
64 / 178
Item
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
SWP Name
1353NM
1353NM
1353SH
1354BMATM
1354BMETH
1354BMETH
1354BMPR
1354BMPR
1354QA
1354RM
1354RM
1354RM
1354RMPhM
1354SN
1354SY
1355VPN
1355VPN
1359HA_OSCLS
SWP Version
7.0
7.3
7.0
7.1
7.1
7.3
7.1
7.2
7.2
7.1
7.3
7.4
1.0
7.1
7.4
4.1
5.0
7.1
ED
02
3AL 88924 BAAA
178
65 / 178
Analysing Product
Analysing Product
...
...
Analysing Product
Analysing Product
TRANSLATOR procedure
Product Name
Product Version
AlcatelOVDL
Apache20
2.1
2.0
unzip
xloadimage
was successful.
5.42.20010612
4.1
INSTANCE Dimension
INSTANCE Description
OSKERNEL
OSKernel Global Instance
Selected INSTANCE:
Dimension
Number
MultiVolume
OSKERNEL
1
NO
ED
02
3AL 88924 BAAA
178
66 / 178
Confirm or refuse the selection. If you confirm the procedure will predispose for the installation of the required software:
TRANSLATOR procedure activated ...
Note: There arent kernel parameters defined.
Note: There arent additional components defined.
TRANSLATOR procedure was successful.
Press [Enter] to continue.
The procedure shows again the list of possible instance for the next choice, enter q [Enter] twice as
shown hereafter and proceed with the NMS predisposal.
ED
02
3AL 88924 BAAA
178
67 / 178
This section describes the 1353NM predisposal, it is provided to better clarify the procedure behavior, but
you have to execute it only if you need the 1353NM functionality, otherwise go to next paragraph Predispose for NMS 3.3.7.5 at page 75.
1353NM subsystems is organized in two components: the software code and instance. You have to predispose the software code once, but you can create one or more instances. Because of this there are two
different actions, where the second can be iterated more than once.
ED
02
3AL 88924 BAAA
178
68 / 178
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
SWP Name
1353NM
1353NM
1353SH
1354BMATM
1354BMETH
1354BMETH
1354BMPR
1354BMPR
1354QA
1354RM
1354RM
1354RM
1354RMPhM
1354SN
1354SY
1355VPN
1355VPN
1359HA_OSCLS
SWP Version
7.0
7.3
7.0
7.1
7.1
7.3
7.1
7.2
7.2
7.1
7.3
7.4
1.0
7.1
7.4
4.1
5.0
7.1
After the confirm action the procedure analyzes the description showing all the software layers required:
ED
02
3AL 88924 BAAA
178
69 / 178
Product Version
AlcatelOVDL
Apache20
2.1
2.0
xemacs
xloadimage
was successful.
21.1.14.20010612
4.1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
SWP Name
1353NM
1353SH
1354BMATM
1354BMETH
1354BMETH
1354BMPR
1354BMPR
1354QA
1354RM
1354RM
1354RM
1354RMPhM
1354SN
1354SY
1354SY
1355VPN
1355VPN
1359HA_OSCLS
SWP Version
7.0
7.0
7.1
7.1
7.3
7.1
7.2
7.2
7.1
7.3
7.4
1.0
7.1
7.0
7.4
4.1
5.0
7.1
Item
19
20
21
22
SWP Name
1359HA_OSRES
OS_KERNEL
OS_KERNEL
OS_KERNEL
SWP Version
7.1
7.0
7.1.2
7.1.3
q [Enter
ED
02
3AL 88924 BAAA
178
70 / 178
Analysing Product
Analysing Product
.
.
.
Analysing Product
Analysing Product
TRANSLATOR procedure
Product Name
ED
02
3AL 88924 BAAA
178
71 / 178
1)
Predispose for a 1353NM Information Manager (IM), if you want to install a 1353NM stand alone
or 1354RM cohosted system.
2)
Predispose for a 1353NM Spare IM, if you are installing the spare system in a 1359HA OSCluster environment.
3)
Predispose for a 1353NM Client, if you just want to have the 1353NM Presentation function on
any other NMS. In this case you have to create an instance for each 1353NM IM and the
Instance Identification number must be the same of the referred IM.
Here after the sequence of actions you have to perform to carry out the job.
At SWP MAIN MENU prompt you have to enter 4 to get in the Create new SWP INSTANCE:
1
2
4
5
7
a
e
1
2
SWP Name
1353NM
OS_KERNEL
SWP Version
7.3
7.1.4
Session
YES
YES
The list of the 1353NM possible instances foreseen for the specific machine model is provided.
List of available INSTANCE dimension for SWP: 1353NM 7.3
Item INSTANCE Dimension INSTANCE Description
1
1353NM_IM_Test
1353NM Master (IM) System Small Configuration
2
1353NM_IM_Small
1353NM Master (IM) System Small Configuration
3
1353NM_IM_Medium
1353NM Master (IM) System Medium Configuration
4
1353NM_IM_Large
1353NM Master (IM) System Large Configuration
5
1353NM_US
1353NM Client (US)
6
1353NM_IM_S_CLSSpare 1353NM Master (IM) Small System for OSCluster
7
1353NM_IM_M_CLSSpare 1353NM Master (IM) Medium System for OSClu...
8
1353NM_IM_L_CLSSpare 1353NM Master (IM) Large System for OSCluster
Enter q to Quit, d to Display again or the Item Number :
ED
02
3AL 88924 BAAA
178
72 / 178
The 1353NM Instance define the behavior of the application, you have three possibilities:
Before entering the instance item number for the selection, read carefully the meaningful of each item in
the following table:
Instance type item
Description
1353NM_IM_Test
1353NM_IM_Small
1353NM_IM_Medium
1353NM_IM_Large
1353NM_US
1353NM_IM_S_CLSSpare
1353NM_IM_M_CLSSpare
1353NM_IM_L_CLSSpare
1353NM Presentation
1353NM/1354RM CoHosted
Enter the instance item number followed by [Enter] to make your choice.
ED
02
3AL 88924 BAAA
178
73 / 178
The multiple volume group option is mandatory for the 1359HA OSCluster protected instances. You can
also choose to use the multiple volume group configuration without the 1359HA OSCluster, but you have
to devote specific hard disks for each new instance of data.
Do you like a MultiVolume group configuration ? (y/n)
After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:
Selected INSTANCE:
Dimension
Number
MultiVolume
1353NM_IM_Small
3
NO
Analysing Product
Analysing Product
Analysing Product
TRANSLATOR procedure
Product Name
Product Version
DBDMySQL
DBI1.32
MySQL
was successful.
2.1026
1.32
3.23
If you have to create more than one instance, enter the item number of the menu that corresponds to the
type you want to create, enter the instance number and multiple volume option. Otherwise enter q [Enter]
to go back to the previous menu level.
ED
02
3AL 88924 BAAA
178
74 / 178
For each instance the procedure asks for two information: the instance number identifier and the multiple
volume group.
The instance number identifier have to be assigned following these rules:
1
2
4
5
7
a
e
ED
02
3AL 88924 BAAA
178
75 / 178
The item belonging to NR7.4 are shown in bold, do not choose the other ones.
To allow the correct behavior of 1359HA_OSRES with cohosted NMS refer to 1359HA
OSResilience Post Predisposal paragraph 3.3.8 at page 86.
If you predispose the system for 1359HA OSResilience you have to remind to predispose a 1359HA OSRES instance for each NMS subjected to protection (see Create
NMS instance paragraph 3.3.7.5.2 at page 78).
Then it asks you to confirm your choice, by showing you the selected NMS, enter y [Enter] if it is correct:
ED
02
3AL 88924 BAAA
178
76 / 178
ED
02
3AL 88924 BAAA
178
77 / 178
N.B.
1
2
4
5
7
a
e
1
2
4
SWP Name
SWP Version
1353NM
7.3
YES
<NMS name>
<NMS version>
OS_KERNEL
7.1.4
YES
Session
YES
ED
02
3AL 88924 BAAA
178
78 / 178
This paragraph shows how to create a NMS instance for the specific data storage.
After the volume group configuration, the procedure summarize the information asking you to confirm your
choice:
Selected INSTANCE:
Dimension
Number
MultiVolume
INSTANCE
Dimension
INSTANCE
Description
....
Enter q to Quit, d to Display again or the Item Number : q [Enter]
Enter q [Enter] again to go back to SWP MAIN MENU.
Create new INSTANCE
Item
1
2
SWP Name
1353NM
<NMS name>
SWP Version
7.3
<NMS version>
Session
YES
YES
ED
02
3AL 88924 BAAA
178
79 / 178
To speedup the predisposal execution and reduce the disk fragmentation, the predisposal is executed
when leaving the script. To execute the predisposal for all the software you have to exit the SWP MAIN
MENU by entering a[Enter]:
1
2
4
5
7
a
e
SWP
INSTANCE
SWP
INSTANCE
OS_KERNEL
7.1.4
OS_KERNEL
7.1.4
1
OSKERNEL
<NMS name> <NMS ver.>
<NMS name> <NMS ver.>
n
<NMS name>_IM_Small
Confirm your choice by entering a[Enter] (as apply) or cancel. Then procedure start executing the requested predispositions.
ED
02
3AL 88924 BAAA
178
80 / 178
ED
02
3AL 88924 BAAA
178
81 / 178
free:
size:
used:
free:
1072 MegaByte(s)
1536 MegaByte(s)
512 MegaByte(s)
960 MegaByte(s)
When such a message occurs during the predispose, replay with R[Enter] to postpone the file system
extension to the next reboot.
ED
02
3AL 88924 BAAA
178
82 / 178
If you are implementing the disk mirroring, to reach the highest availability level, it is advisable
to choose a disk not connected to the same SCSI bus of the Main Boot Disk, this choice allow
the system to survive also to a SCSI bus failure.
N.B.
If you are implementing the disk mirroring, it is advisable to keep the two disk chains balanced.
If them are unbalanced the useful disk space amount is the minimum size of them.
If you are installing a machine in 1359HA OSCluster configuration some disk unused by
local system (free) can be used by another one, double check the configuration also of
the other systems!
_______________________________________________________________________
Disks Selection
Mount Point need 5632 MBytes on Volume Group: /dev/vg00 (pvg0)
_______________________________________________________________________
Device MByte Hardware Path
Usage
Type
VolGroup
_______________________________________________________________________
c1t2d0
8680 0/0/1/1.2.0
Pri_Boot _Main_ vg00
c2t2d0
8680 0/0/2/0.2.0
_(free)_ ______ __________
D c4t8d0
8680 0/4/0/0.8.0
_(free)_ ______ __________
D c4t9d0
8680 0/4/0/0.9.0
_(free)_ ______ __________
c5t12d0
8680 0/7/0/0.12.0
_(free)_ ______ __________
c5t13d0
8680 0/7/0/0.13.0
_(free)_ ______ __________
_______________________________________________________________________
Select Data Area (Main instance) dev name or [q] to quit:
Enter the name of a free disk.
ED
02
3AL 88924 BAAA
178
83 / 178
It is possible that more than one disk is requested to reach the amount of disk required space. The expected disk amount depends by the number of NMS and NMS instances requested, its size can be computed following the instructions shown in the paragraph Requested Hard DIsks 2.1.1.4 at page 13.
ED
02
3AL 88924 BAAA
178
84 / 178
_______________________________________________________________________
Disks Selection
_______________________________________________________________________
The last message issued before starting the software package installation is:
ATTENTION: now to complete the configuration ShutdownReboot will be exe...
Press [Enter] to continue.
***** The System reboots automatically, please wait *****
Reply by pressing [Enter], the machine will be automatically rebooted and software components
installed. If you are installing with CD/DVD, the request of the medium will be issued in console issuing
a message that reports the medium label.
N.B.
Dont worry if the procedure does not require to insert all media, nether if it does not ask
media in ascending order.
ED
02
3AL 88924 BAAA
178
85 / 178
When there are two or more cohosted NMS Master instances and the system has also the 1359HA OS
Resilience failure protection, some additional action are required after the system predisposal and
before customizing the software. In this conditions 1359HA OSResilience maximizes system performance allowing to use both master and spare servers for performing the normal operations, recovering
the faulty application on a single server.
The following figure shows how the 1359HA OSResilience manages these faulty conditions, it is important to note in the example how 1354RM is communicating with 1353NM in the two cases:
When both machine are operational, 1354RM and 1353NM communication occurs via 1353NM Client instance on board of 1354RM machine.
When one of the two systems is out of service, the communication are direct
The software component shown in Figure 8. in gray color are not operational, them can be the standby
instances created by 1359HA OSResilience.
Server hosta
1354RM
Master
Active
Normal system
Operation
1353NM Client
1353NM
Master
StandBy
Server hosta
System failure
example.
1354RM
Master
Active
1353NM Client
1353NM
Master
Active
Server hostb
1354RM
Master
StandBy
1353NM Client
1353NM
Master
Active
Server hostb
FAULT
ED
02
3AL 88924 BAAA
178
86 / 178
N.B.
Now you have to create manually the NMS Client to allow interNMS communication has shown in the
following paragraphs.
3.3.8.1 Manage 1353NM cohosted with any 1354 NMS
N.B.
When a 1353NM is cohosted with any 1354 NMS (1354RM, 1354BM ATM, and 1354BM ETH), you have
to create the NMS client data instance file system manually, by entering the following command:
...,sys, root # scextendfs /usr/Systems/1353NM_<NMS Instance>_7.3_Presentation 250[Enter]
Where;
<NMS Instance> has to be replaced by the NMS Instance identified associated to the 1353NM master.
3.3.8.2 Manage 1354RM cohosted with any 1354BM NMS
N.B.
When a 1354RM is cohosted with 1354BM ATM, and/OR 1354BM ETH, you have to create the NMS client
data instance file system manually, by entering the following command:
...,sys, root # scextendfs /usr/Systems/1354RM_<NMS Instance>_7.4_Presentation 400[Enter]
Where;
<NMS Instance> has to be replaced by the NMS Instance identified associated to the 1354RM master.
ED
02
3AL 88924 BAAA
178
87 / 178
This chapter shows the minimum operating system and platform configuration required to allow TMN machine interworking.
3.4.1 Node Name Management
Before proceeding in the installation and customization it is necessary to declare all the IP network nodes
involved. The involved nodes means all the IP are defined in the following table:
Description
Type
Alcatel TNM system
Any HP 9000 server and/or workstation with Alcatel TNM on board, that have
to communicate with the machine you are installing.
Printers
Any network printer that have to be used by the machine you are installing.
Virtual IP Address
The /etc/hosts file must be manually updated each time a new machine will be installed.
ED
02
3AL 88924 BAAA
178
88 / 178
hosta
1354RM Client
hostb
1353NM Master
hostc
1354RM Client
hostd
1354RM Master
hoste
1353SH Master
There are other network equipments, such as rooters, printers (local and network), personal computer,
and time synchronization equipments. You have to identify the equipment specified by Table 5. at page
88, in the example:
lp1
Network line printer.
WAN
hosta
IP 192.200.49.1
WAN
hostb
IP 192.202.21.7
hostc
IP 192.202.21.8
hostd
IP 192.202.22.4
hoste
IP 192.202.22.5
In this example all the machines work together; you have to define their IP address and official host names
in the /etc/hosts of the five servers.
This is mandatory, because it allows the machines to communicate each other.
Supposing that GPS time synchronization system (gpsrec1) has to be used by the entire network management system, it has also to be defined into the /etc/hosts of all servers.
The network printer (lp1) can be defined only on the server on the same local area network.
hosta
hostb
hostc
hostd
hoste
192.200.49.1
hosta
Present
To insert
To insert
To insert
To insert
192.202.21.7
hostb
To insert
Present
To insert
To insert
To insert
192.202.21.8
hostc
To insert
To insert
Present
To insert
To insert
192.202.22.4
hostd
To insert
To insert
To insert
Present
To insert
192.202.22.5
hoste
To insert
To insert
To insert
To insert
Present
192.202.21.51
gpsrec1
To insert
To insert
To insert
To insert
To insert
192.202.22.6
lp1
To insert
To insert
ED
02
3AL 88924 BAAA
178
89 / 178
The clock synchronization is mandatory for system working together with Kerberos authentication tool, to do it the Network Timing Protocol (NTP) specified by RFC 1305 has to be configured by following the instructions shown in this paragraph.
If NTP is not configured you have to check the time difference among all the systems and
guarantee that it doesnt exceed five minutes.
Before proceeding with the NTP configuration you must have a clear picture of the configuration among
the involved machines, it is advisable to prepare a time distribution plan taking into account the following
rules:
a)
The primary time sources have to be reliable ones, such as a Global Position System (GPS) receiver
time source.
b ) Define two or three timeserver machines. Each timeserver should be a peer with of the other time
servers.
c ) If possible, do not synchronize multiple timeservers to the same outside source.
d ) If you choose to use an hp server as time source, it must be configured to be synchronized with
its internal clock.
For example in a network with two GPS receivers and five nodes, with the following roles:
host and hosted configured with: 1353NM and 1354RM cohosted with 1359HA OSResilience.
hostly, host and hostel preform the presentation function for the resilient servers.
The resilient hosts plus a presentation (host) can be configured to receive the time from the GPS receives,
and swap the time among themselves. All the other servers in the network (hostly and hostel) have to be
configured to receive the time from the host, host e hosted.
GPS
WAN
hosta
IP 192.200.49.1
GPS Receiver 1
IP 192.202.21.51
GPS Receiver 2
IP 192.202.22.20
WAN
hostb
IP 192.202.21.7
hostc
IP 192.202.21.8
hostd
IP 192.202.22.4
hoste
IP 192.202.22.5
ED
02
3AL 88924 BAAA
178
90 / 178
hosta
server gpsrec1 prefer
server gpsrec2
peer hostc
peer hostd
hostc
server gpsrec1 prefer
server gpsrec2
peer hosta
peer hostd
hostd
server gpsrec1
server gpsrec2 prefer
peer hosta
peer hostc
The prefer attribute distinguishes as the preferred source, this source it is usually the most reliable and
also the nearest one.
The remaining servers can retrieve the time from the other ones, here after the configuration:
hosta
server hostb prefer
server hostc
server hostd
hoste
server hostb
server hostc
server hostd prefer
To make easier the NTP configuration the scxntp script is provided.
To start scxntp script, login the system as root user and enter: scxntp [Enter]
========================================================================
OSConf xntp Protocol Configuration
========================================================================
1 Add new NTP server
2 Add new NTP peer
3 Remove NTP server
4 Remove NTP peer
5 Configure NTP on local clock
6 Show NTP configuration
7 Show NTP status
8 Start/Stop NTP server
9 Align the time to server
e or q for exit
ED
02
3AL 88924 BAAA
178
91 / 178
a)
b)
c)
d)
e)
f)
Start the NTP Daemon, setup the daemon automatic start at system startup, and synchronize the
hostb clock with the preferred server in one shot:
Insert choice and press [Enter]: 8
WARNING: The xntpd daemons it is not configure to start automat...
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE:
Temporary setup xntpd autostart...
NOTE:
Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset 0.026898 sec
xntpd NOTE:
Reset the setup xntpd autostart...
Press return to continue ...
g)
This is the procedure using scxntp script to configure the hosta of Figure 10. at page 90.
a)
b)
c)
ED
02
3AL 88924 BAAA
178
92 / 178
This is the procedure using scxntp script to configure the hostb of Figure 10. at page 90.
e)
Start the NTP Daemon, setup the daemon automatic start at system startup, and synchronize the
hosta clock with the preferred server in one shot:
Insert choice and press [Enter]: 8
WARNING: The xntpd daemons it is not configure to start automatically
Would you like to start xntpd automatically at reboot (y/n) ? y
NTP server is stop
Would you like to start it (y/n) ?y
NOTE:
Temporary setup xntpd autostart...
NOTE:
Starting xntpd ...
4 Sep 18:33:01 ntpdate[14482]: step time server 151.98.45.29 offset 0.026898 sec
xntpd NOTE:
Reset the setup xntpd autostart...
Press return to continue ...
f)
The script allows to easily manage the NTP configuration, you can add or/and delete servers and/or peers,
show the configuration, stop and start the NTP daemon, or align in one shot your system time to a specific
server.
Defining a NTP server the management script allows to specify the preferred one, it is not recommended
to define more than one preferred server.
The NTP mechanism takes a long time to synchronize the machine with server. The NTP
daemon has to be stopped and started each time the configuration changes. Usually the
NTP daemon is not running.
3.4.2.2 Initial Clock Alignment
When a machine is installed for the first time, the clock is not synchronized with any reference, the easiest
way to synchronize it with the other is by running scxntp script selecting the option N.9 Align the time
to server.
The time alignment is forbidden when NTP daemon is running.
N.B.
To align the time you have to login the system as root user and start the script scxntp by entering:
...,sys,root# scxntp[Enter]
ED
02
3AL 88924 BAAA
178
93 / 178
========================================================================
OSConf xntp Protocol Configuration
========================================================================
1 Add new NTP server
2 Add new NTP peer
3 Remove NTP server
4 Remove NTP peer
5 Configure NTP on local clock
6 Show NTP configuration
7 Show NTP status
8 Start/Stop NTP server
9 Align the time to server
e or q for exit
Insert choice and press [Enter]:
At the prompt enter 9 [Enter]
Enter server hostname or IP address or q for Quit :
The procedure will ask you to enter the IP address or Hostname of the timeserver, enter it and press [Enter]
key. The time will be aligned and shown.
ED
02
3AL 88924 BAAA
178
94 / 178
Poseidon is the license software manager used to authorize the Alcatel Software execution.
N.B.
If you have three or more machines, you have to setup a Three Redundant License Servers configuration, in accordance with the following rules:.
The three license server machines should be located physically close to each other (if possible).
if in your network there are less than three nodes, you have to define a the license server, and all the
required licenses have to be loaded on that server.
The license have to be required providing the host identifier of the license server(s). Do not provide the
host identifier of the machine where the application is planned to be run.
3.4.3.1 Retrieve License Servers Host Identifier
When you have selected the license server machine(s), for each of them you have to retrieve the host
identifier by executing the following commands:
a)
b)
c)
[Enter]
Host Name
Host Identifier
Host Name
ED
Host Identifier
02
3AL 88924 BAAA
178
95 / 178
ED
02
3AL 88924 BAAA
178
96 / 178
The license can be require via Alcatel Intranet Web, by authorized Alcatel personal only.
Retrieve the new license key from Alcatel web, asking for the same host identifier of the first one.
b)
c)
d)
Add the INCREMENT line from the just obtained license file, to the /opt/poseidon/etc/license.dat
file.
The INCREMENT line can be split in two or more ones, because of the length. If the INCREMENT line terminated with back slash ( \ ), that means also the next one have to be considered
as part of INCREMENT.
e)
If you have the three host redundant configuration, copy the license file on other two license servers.
f)
Force the license server daemon to reread the license file by entering:
...,sys,root # /sbin/init.d/poseidon reread [Enter]
g)
Check again with lmstat (see paragraph 3.4.3.4) if the number of point has been increased.
ED
02
3AL 88924 BAAA
178
97 / 178
Some problem has been experienced configuring the three redundant Poseidon license servers. This
paragraph summarizes these problems and show a possible solution way.
3.4.3.6.1 Redundant Connectivity
The three redundant servers work properly only if each server is able to communicate with the other two.
This is the reason why it is better check the server configuration and connectivity. The easiest way to do
it is try a network ping from each license server to any other one:
..,sys,root # ping <Hostname> [Enter]
where <Hostname> is the name of the remote license server machine(s).
If the server replies the ping request an output like the following will be provided:
,sys,root # ping hostc 64 2
PING hostc: 64 byte packets
64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms
64 bytes from 192.202.21.8: icmp_seq=1. time=0. ms
hostc PING Statistics
2 packets transmitted, 2 packets received, 0% packet loss
roundtrip (ms) min/avg/max = 0/0/0
Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
First of all it is better to verify that the server is running. It the server is running check on the
/etc/hosts file if the IP address defined for the specified server is correct. If also the IP address
is correct, the reason can depend by the Default Gateway, check is adefault gateway si defined
and reachable. If you do not know name and IP address of the network default gateway refer
to the network administrator.
3.4.3.6.2 Two licence servers down
The three redundant license server fails when more than two servers are down or are unreachabe, in order
to reduce the risk of license failure is suggested to peridiacally check the license servers entering:
...,sys,root # /opt/poseidon/bin/lmstat a c /opt/poseidon/etc/license.dat[Enter]
ED
02
3AL 88924 BAAA
178
98 / 178
The depot machine or distribution CD are available, and the local system is correctly authorized to access the files (see 3.3.5.2 and 3.3.5.3 at page 62 for more informations).
The installing system must be authorized to retrieve the files from itself or from depot machine.
When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
N.B.
If the mentioned requirement are matched, the installation and customization can be started by entering:
...,sys,root # cd /alcatel/Install_Wizard [Enter]
For installation from CD:
1)
2)
3)
4)
The script issues the following question to require you to confirm the CD driver:
Please enter the Device Name of source media [c0t0d0]:
You have to reply with [Enter] to confirm, or enter e different CD device file name.
1)
ED
02
3AL 88924 BAAA
178
99 / 178
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
N.B.
NOTE:
Preparing to install ...
NOTE:
Preparing to INSTALLER 7.1.3.1 ...
===========================================================================
Installation OSKERNEL package
===========================================================================
***************************************************************************
NOTE:
${INSTALL_ROOT}/INSTALLER/Install
OSKERNEL
${DEPOT_HOST}
file=${DEPOT
_PATH}/OSKERNEL_7.1.2.tar.gz interactive=no
NOTE:
***************************************************************************
The installation is executed by INSTALLER that shows you the contents of the package :
ED
02
3AL 88924 BAAA
178
100 / 178
NOTE: NO CONFIGURATION provides by OSKERNEL for the package installation, using the default one .
Image Installation requested for:
Product
OSKERNEL
Format
zip
Host
151.98.42.32
File
/SD_CDROM//OSKERNEL_7.1.2.tar.gz
Keep_data
no
Check_sum
NOT APPLICABLE
Interactive
no
PLEASE ENSURE LOCAL OSKERNEL SYSTEM IS NOT RUNNING
.
The installation start automatically, this step will take up to 20 minutes.
The last question is related to the OSKernel customization; you have to reply also this question with
y[Enter]
Do you want to execute OSKERNEL Custom? [y|n|q] y [Enter]
Then the OSKernel customization will be executed showing the trace on the terminal.
*******************************************************************
NOTE:
${INSTALL_ROOT}/Kernel/script/KernelCustomize
NOTE:
...
.
.
.
NOTE:
NOTE:
OSKERNEL custom_cmd
The procedure will stop after up to 12 minutes, asking you to authorize the GoGlobal UX environment
shutdown. Ask all users logged in with GoGlobal UX to log out the system.
GoGlobal 2 server will be stopped. Do you want continue ? (yes/no,
default=no)
Reply the question with yes[Enter] to allow GoGlobal UX customization, and then the procedure will
be completed in a couple of minutes issuing:
NOTE:
OSKERNEL installation completed
===================================================================
NOTE:
Session finished on: Mon Sep 26 14:38:37 METDST 2005
The OSKernel installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_OSKERNEL_*.log
ED
02
3AL 88924 BAAA
178
101 / 178
If you doesnt have already configure the GoGlobal License server, it could be displayed
an error message.
Dont care of it, and configure the GoGlobal License Server.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
N.B.
ED
02
3AL 88924 BAAA
178
102 / 178
N.B.
In the following table the NMS and NMC foreseen for NR7.4:
Name
Version
Description
1353NM(*)
7.3 (7.3.6)
1354BM ETH
7.3.0.5_ P02(RP10.1)
1354BM PR
7.2 (7.2.4)
1354BM ATM
7.1.4 (RP003)
1354RM
7.4 (7.4.3.2)
Regional Manager
1354SY
7.4 (7.4.0.2)
Synchronization Manager
1355VPN
5.0 (5.0.3B)
1359HA OSReslience
1359IOO
5.2 (5.2.0.5)
1359ISN
5.0 (5.0.0.5)
ETHMEDIATOR
1.1.7.4.3
(*) The installation of this item is better detailed in in paragraph 3.5.3 Install and Customize1353NM at
page 111.
ED
02
3AL 88924 BAAA
178
103 / 178
This paragraph shows how to install the Alcatel TNM software optimizing the time need to adapt it to this
specific environment.
To be able to curry out this section the following items are required:
The installing system must be authorized to retrieve the files from itself or from the depot machine.
When depot machine is used: The hostname of the depot machine correctly defined in the /etc/
hosts file.
You have to be able to login the system via GUI, in case of HP server the GoGlobalUX have
to be authorized with the license code.
Then you can proceed with NMS and/or NMC shown at Table 9. as summarized hereafter:
a)
If ETHMEDIATOR installation is requested, perform the action shown at 3.5.2.1.1. at page 104
b)
c)
When ETHMEDIATOR is present, perform the action shown at 3.5.2.1.3 at page 106
d)
e)
f)
Then complete the installation and customization with integrating the systems among themselves.
3.5.2.1.1 ETHMEDIATOR Preinstallation Special Instruction.
Meaningful for ETHMEDIATOR Only.
The 1354BM ETH Mediator has to be installed on 1354RM system Before installing the ETHMEDIATOR
it is necessary to stop any running NMS present on the system and OSKernel services. Shutdown the
NMS via Process Monitoring Control (PMC), and stop the OSKernel services by entering the following
as root user:
...,sys,root # /alcatel/kernel/scrip/KernelServices stop [Enter]
3.5.2.1.2 NMS or NMC Installation Procedure
If the mentioned requirement are matched, the installation and customization can be started by entering:
a)
Login the system via Graphical User interface CDE as root user.
N.B.
b)
c)
ED
02
3AL 88924 BAAA
178
104 / 178
1)
2)
3)
4)
5)
To allow the recovery of errors it is possible to start install.sh with option confirm, the
option causes the issues of confirm request message before execute each step in the
installation and configuration. Replying no to these questions you can skip the step.
The script start issuing the Alcatel mask, then it will ask you some questions.
........
......
....
..
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
NOTE:
Preparing to install ...
.
The output depends by the chosen NMS or NMC
.
.
If you had started Install.sh with confirm option, you have to confirm by entering y [Enter]
The time spent for installation of package depends by NMS.
ED
02
3AL 88924 BAAA
178
105 / 178
The installation script can issues a message asking you for inserting a specific CDROM medium, just
replace CD in the driver with the requested one and the procedure will go on automatically.
Dismount the CD by entering:
...,sys,root# umount /SD_CDROM[Enter]
3.5.2.1.3 ETHMEDIATOR Postinstallation Special Instruction
Meaningful for ETHMEDIATOR Only.
After ETHMEDIATOR installation you can startup again OSKernel services by entering
...,sys,root # /alcatel/kernel/scrip/KernelServices start [Enter]
ED
02
3AL 88924 BAAA
178
106 / 178
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
/alcatel/Kernel/script/Custom
/alcatel/Kernel/script/Custom
The System, Instances,List window will be shown on the screen after a few seconds, it allows you to select the instance that you want customize:
ED
02
3AL 88924 BAAA
178
107 / 178
Select Choose_one and then NewInstance , then select Apply & exit in the Actions menu.
Then custom Parameters Definition window will be shown on the screen after a few seconds, it allows
you to set the relevant custom variables:
ED
02
3AL 88924 BAAA
178
108 / 178
To select the value for the following items you have to move the pointer on the box under the
label, then press the selection button of the mouse, a popup menu will be shown with the possible choices, moving the pointer choose one of them and release the mouse button: System_Version, System_Instance_Rule, Master Kernel_Type and Driver_Version.
N.B.
To customize the 1354RM you have to set the System_Version on new NMS/NMC (including version),
then enter the Instance identification number defined at predisposal time (see Create NMS Instance
paragraph 3.3.7.5.2 at page 78) in the input area under the label System_Instance_Id.
If the Instance identification number does not correspond to the predisposed the customization script will create the data in a wrong place, and the /alcatel file system can get in
overflow.
Set the System_Instance_Rule depending by the rule of the specific instance identification number.
You have to set it to Master when the instance is an Information Manager (IM), Client when the instance
is a User Service (US). MasterClient has to be set only with1359HA OSResilience protection, when
a client file system has been manually created for 1353NM and 1354RM as shown in 1359HA OS_Resilience Post Predisposal 3.3.8 at page 86.
The input fields identified by System_Instance_Name allows to define the name of the system within
the TMNOS application.
For the Client instances it must be the same than the Master one. If you choose a name different
then the default customizing the master instance, dont you forget to enter it again for the client.
When you customize a NMS Client the related Master hostname have to be defined in
/etc/host file.
The Master_HostName is meningeal for Client and MasterClient instances. For the Client it must
be set with the hostname of the corresponding master instance, instead MasterClient is useful only for
1359HA OSResilience, and it must refer the companion hostname (refer 1359HA OSResilience 7.1
Administration Guide [12] for more information about companion concept).
For 1359HA OSCluster you have to specify the Virtual Hostname.
Leave Master_Kernel_Type and Driver_Version at default setting.
Then pulldown the menu Action (in the left upper corner), select Apply & exit to start the custom procedure.
A trace window will be open on the screen showing the customization progress.
ED
02
3AL 88924 BAAA
178
109 / 178
The procedure will complete when the [Dismiss] button will be enabled.
The NMS/NMC installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_<NMS/NMC name>_*.log
ED
02
3AL 88924 BAAA
178
110 / 178
The installing system must be authorized to retrieve the files from itself or from the depot machine.
When installing from depot machine: The hostname of the depot machine correctly defined in
the /etc/hosts file.
You have to be able to login the system via GUI, in case of HP server the GoGlobalUX have
to be authorized with the license code(see 1350 Administration Guide [2] for more information).
If the mentioned requirement are matched, the installation and customization can be started by:
a)
Login the system via Graphical User Interface CDE as root user.
N.B.
b)
c)
5)
ED
02
3AL 88924 BAAA
178
111 / 178
N.B.
d)
To allow the recovery of errors it is possible to start install with option confirm, the
option causes the issues of confirm request message before executing each step in the
installation and configuration. Replying no to these questions you can skip the step.
The script start issuing the Alcatel mask, then it will ask you some questions.
N.B.
The output provided are just an example of the procedure behavior. THE INSTALLATION CAN ISSUE DIFFERENT MESSAGES!
..........
........
......
....
..
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
NOTE:
${INSTALL_ROOT}/INSTALLER/Install 1353NM ${DEPOT_HOST} file=${DEPOT_PATH}/1353NM_736_CORE_20SEP2005.tar.gz interactive=no
ED
02
3AL 88924 BAAA
178
112 / 178
Then the 1353NM distribution files will be insalled issiung a list of information like the following:
Image Installation requested for:
Product
Format
Host
File
Keep_data
Check_sum
Interactive
1353NM
zip
hosta
<file name>
no
NOT APPLICABLE
no
to
execute
1353NM
Install
package
to
manage
NR5/6
1353SH 6.3 specific patch must be installed onto the 1353SH system to allow the integration with the 1354RM (see the 1353SH 5 and 1353SH 6 release notes).
If you have any NR5 or NR6 1353SH that have to provide the navigation feature from the installing system,
you have to reply with y [Enter] to this question.
N.B.
This package is significant only if you have predispose a 1354RM item too.
Some post installation activities are automatically executed before starting the 1353NM Custom.
ED
02
3AL 88924 BAAA
178
113 / 178
1353NM customization adapt software to the specific machine context, it is performed in two steps by
Install.sh script:
Precustom Activities
Custom.
To execute the 1353NM custom enter:
...,sys,root# ./Install.sh custom 1353NM [Enter]
The script start issuing the Alcatel mask, then it will execute the Precustom activities.
..........
........
......
....
..
XX
XX
XXXX
X X
XX XX
XXXXXX
XX
XX
XX
XX
XX
XX
XX
XX
XXXXX
XXXX
XX XX
XX
XX
XX
XX XX
XXXX
XX
XX
XXXX
XXXX
XXXXXX
XXXXXX
XXXXXXXX
XXXXXX
XX
XX
XX
XX
XX
XX
XXXXX
XX
XX
XXXX
XX
XX
XXXXX
XX
XX
XX
XX
XX
XX
XXXX
======================================================================
NOTE:
Executing 1353NM custom_cmd...
NOTE:
runing </alcatel/Kernel/script/Custom>
NOTE:
Executing 1353NM custom_cmd ...
NOTE:
Basic Kernel Services (Connection Manager, Action Polling) Running. ..........
.
The System, Instances,List window will be shown on the screen after a few seconds. It allows you to
select the instance that you want customize:
ED
02
3AL 88924 BAAA
178
114 / 178
if you are performing an installation from scratch: select Choose_one and then NewInstance to
define and customize 1353NM7.0.
if you are performing an upgrade: select Choose_one and then the instance you are upgrading,
identified during the software upgrade procedure.
The custom Parameters Definition window will be shown on the screen after a few seconds, it allows you
to set the relevant custom variables:
ED
02
3AL 88924 BAAA
178
115 / 178
To customize the 1353NM you have to set the System_Version on 1353NM7.0, then enter the Instance
identification number defined at predisposal time (see Predispose 135NM Instance paragraph 3.3.7.4.2
at page 72) in the input area under the label System_Instance_Id.
If the Instance identification number does not correspond to the predisposed one, the
customization script will create the data in a wrong place, and the /usr file system can get
in overflow.
Set the System_Instance_Rule depending by the rule of the specific instance identification number.
You have to set it to Master when the instance is an Information Manager (IM), Client when the instance
is a User Service (US). MasterClient has to be set only with1359HA OSResilience protection, when
a client file system has been manually created for 1353NM as shown in 1359HA OS_Resilience Post Predisposal 3.3.8 at page 86.
When you customize a 1353NM Client the related Master hostname have to be defined in
/etc/host file.
The Client Instance Identifier must be equal to the related Master!
The input fields identified by System_Instance_Name allows to define the name of the system within
the TMNOS application.
N.B.
The Master_HostName is meningeal for Client and MasterClient instances. For the Client it must
be set with the hostname of the corresponding master instance, instead MasterClient is useful only for
1359HA OSResilience, and it must refer the companion hostname (refer 1359HA OSResilience 7.1Administration Guide [12] for more information about companion concept).
For 1359HA OSCluster you have to specify the Virtual Hostname.
The System_Instance_Name and Master_HostName must be different.
Leave Master_Kernel_Type and Driver_Version at default setting.
Then pulldown the menu Action (in the left upper corner), select Apply & exit to start the customizing
procedure.
A trace window will be open on the screen showing the customization progress.
ED
02
3AL 88924 BAAA
178
116 / 178
To select the value for the following items you have to move the pointer on the box under the
label, then press the selection button of the mouse, a popup menu will be shown with the possible choices, moving the pointer choose one of them and release the mouse button: System_Version, System_Instance_Rule, Master Kernel_Type and Driver_Version.
N.B.
ED
02
3AL 88924 BAAA
178
117 / 178
There are also some error messages that can rise that have also to be ignored, hereafter an example of
them:
ED
02
3AL 88924 BAAA
178
118 / 178
NOTE:
Importing EmlUsm.....import definitions ...
Importing from file:/usr/Systems/1353NM_.../SEC/repository/secimim...
ERROR: , line #494: Name Already Used.
ERROR: , line #499: Name Already Used.
ERROR: , line #577: Name Already Used.
ERROR: , line #582: Name Already Used.
ERROR: , line #1069: Name Already Used.
ERROR: , line #1074: Name Already Used.
ERROR: , line #1578: Name Already Used.
ERROR: , line #1583: Name Already Used.
Import problem: Name Already Used.
The procedure will complete its task in about 60 minutes on a RP3410 server.
If your planning foresees more than one 1353NM Retix Stack, it is suggested to configure
now all the lan cards needed with an IP Address (see 1350 Administration Guide [2] for
more information).
The 1353NM installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:
/alcatel/Install_Wizard/log/Installation_1353NM_*.log
/alcatel/Kernel/maintenance/trace/Custom.trace
/alcatel/Kernel/maintenance/log/Custom.log
For installation from CD:
1)
2)
ED
02
3AL 88924 BAAA
178
119 / 178
The 1353NM foresees to have more than one client instance on board of 1354RM, the reason is: the
1354RM must have a 1353NM client for each 1353NM Master it has to supervise. In this case you have
to install the 1353NM software once and customize any predisposed instance. The Install.sh allows to
custom the first one, if you have more than one, you have to start the OSKernel Custom procedure for
each one of the instance but the first.
To run OSKernel Custom procedure:
The System, Instances,List window will be shown on the screen after a few seconds, it allows you to select the instance that you want customize:
ED
02
3AL 88924 BAAA
178
120 / 178
N.B.
To customize the 1353NM you have to set the System_Version on 1353SH7.0, then enter the Instance
identification number defined at predisposal time (see Predispose 135NM Instance paragraph 3.3.7.4.2
at page 72) in the input area under the label System_Instance_Id.
ED
02
3AL 88924 BAAA
178
121 / 178
Set the System_Instance_Rule depending by the rule of the specific instance identification number.
You have to set it to Client .
The input fields identified by System_Instance_Name allows to define the name of the system within
the TMNOS application.
N.B.
Then pulldown the menu Action (in the left upper corner), select Apply & exit to start the customizing
procedure.
A trace window will be open on the screen showing the customization progress.
The 1353SH installation and customization is now completed, before continue installation it is advisable
to check for any error that may have occurred by check the contents of the following file:
/alcatel/Kernel/maintenance/trace/Custom.trace
/alcatel/Kernel/maintenance/log/Custom.log
ED
02
3AL 88924 BAAA
178
122 / 178
If the Instance identification number does not correspond to the predisposed the customization script will create the data in a wrong place, and the /usr file system can get in
overflow.
1359HA OSResilience requires its own system configuration, refer to 1359HA OSResilience 7.1 Administration Guide [12] for more information.
VERY IMPORTANT!!
When all the TNM machines have been configured in standalone, you have to run on
each one of them the final integration script!
ED
02
3AL 88924 BAAA
178
123 / 178
1)
Before start, you must be sure that all systems involved are already installed, customized and
configured by system configuration tool. To easy identify the potential involved system opening
the TMN OS tool available on display front panel of any Alcatel NMS operator session.
2)
3)
Start the global integration script by entering /alcatel/Kernel/script/UpdateNetworkConnections.pl and answer to the questions:
...,sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl [Enter]
The procedure starts tracing the integration execution issuing an output like the following:
NOTE:
NOTE:
NOTE:
NOTE:
NOTE:
NOTE:
...
...
For each system that have to be integrated the following question can be issued:
1354RM_3: Run the Integration of 1353NM_1? [y/n]
If you reply y the system will be integrated, and the procedure will issue also these other questions:
1354RM_3: Run the PLT Integration of 1353NM_1? [y/n]
1354RM_3: Run the Backup/Restore Integration of [y/n]
1354RM_3: Run the Navigation Integration of 1353NM_1? [y/n]
Generally you have to reply y to all of them, with the following excepion, when procedure asks you to
authorize the integration between a 1354RM and 1354BM ETH, where you MUST reply NO to PLT
and Backup/Restore integration, like the following example:
1354RM_3: Run the PLT Integration of 1354BMPR_1? [y/n] n
1354RM_3: Run the Backup/Restore Integration of 1354BMPR_1 [y/n] n
1354RM_3: Run the Navigation Integration of 1354BMPR_1? [y/n] y
Warning and error messages will advice you that the remote system is not reachable or not properly configured, and the machine will be not integrated. If such kind of message are issued, identify the problem, fix
it, and run again the integration script.
Example:
WARNING: 1353RM_3: Connection problems with <hostname>. Skipping Update.
When the procedure will be successfully executed, you will be able to use all the Network Management
System features.
ED
02
3AL 88924 BAAA
178
124 / 178
s <Sec Inst> (optional) This option allows to specify the NMS instance will be referred by ASUSM
for granting network object access permission (SEC). This feature was
mandatory untill NR7.1T, when AS did not support the multiple SEC. With
NR7.1D/7.2 specifying this option you force AS to refer just one SEC, reducing the AS federation access authorization to the operators defined in
the indicated NMS instance.
<NMS Inst List>
Specifies the NMS instance list that will be part of federation. with the
followong syntax:
<NMS_NAME>_<NMS_INSTANCE><NMS_VERSION>
Example:
1354RM_27.1
You can create different AS Federations, by running the command with different ASF names.
The command must be executed by root user, and the file is located in /usr/Systems/Global_Instance/
AS/script/, so to start the command you have to logging the system as root and enter:
...,sys,root # /usr/Systems/Global_Instance/AS/script/ASUSMFederation.pl \[Enter]
name <ASF Name> <NMS Instance List>[Enter]
This is an example of two AS federation performed on a system equipped with: 1354RM Master instance
number 2, three 1353NM Client instance number 1, 2 and 3. The latter will be call RegionEst involving
the 1354RM and 1353NM instance number 1, and the former will be call RegionWest involving the
1354RM and 1353NM instance number 2 and 3.
...,sys,root # /usr/Systems/Global_Instance/AS/script/ASUSMFederation.pl \[Enter]
name RegionEst 1354RM_27.1 1353NM_17.0 [Enter]
ED
02
3AL 88924 BAAA
178
125 / 178
ED
02
178
126 / 178
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4.1 Prerequisites
Before proceed in new software installation can be operate only if the prerequisite shown in this paragraph
are met. The prerequisite evaluation is require to do not compromise an existing system with an incompatible software or simply get in trouble during the installation.
4.1.1 Previous installation status.
The entire installation process is based in two step, predisposal and installation. These two actions must
be execute in the order, when the machine is predisposed for a specific software, this software have to
be installed before proceed with a new predispose action. If this sequence is not respected, the installation
process is not guarantee. That means, before proceed in the predisposal for the new NMS or NMC, you
have to check that there are no predisposed NMS and NMC not yet installed. If any of them is present,
please install them or delete the related Software Package (SWP) predisposal with scmanageswp tool.
4.1.2 Network Release Compatibility
You can install any NMS or NMC of the same Network Release level.
For installation of NMS of different network release refer to the specific release notes.
4.1.3 Disk space requirements
Disk space requirements are specified in paragraph B.3 at page 149.
4.1.4 Reboot Planning
The installation of a new NMS or a new NMS instance creation requires the system reboot, the only exception to this role is 1353NM client, that means before start the system predispose you have to plan a system
reboot.
ED
02
3AL 88924 BAAA
178
127 / 178
This paragraph describes which paragraphs of the previous chapters you have to follow to install a new
NMS on an existing TMN machine.
The 1359HA OSResilience NMC has specific instructions
a)
Predispose the system for both software package and instance for new NMS/NMC using scmanageswp tool has shown in paragraph: Start SWP Management Script 3.3.7.1 at page 64, when
needed Predispose for 1353NM 3.3.7.4 at page 68, and Predispose for other NMS/NMC 3.3.7.5
at page 75.
The system predispose can require the reboot of hpux.
N.B.
b)
Add the NMS/NMC related license in the Poseidon license file of the license server machine.
c)
Force the license server machine to load the new license by entering the following command on one
of them:
...,sys,root # /sbin/init.d/poseidon reread [Enter]
d)
Install the Alcatel software following instruction shown in paragraphs: Install NMS and NMC 3.5.2.1
at page 104.
e)
Execute the custom for each NMS instance and/or for each NMC just installed following paragraph
Customize NMS Instance or NMC 4.2.1 at page 128.
f)
Then proceed in the process configuration as described in the specific administration guide.
g)
Perform the TMN system Final Integration shown in the paragraph 3.6 at page 123.
Within the additional software and instances it is possible to distinguish three different cases:
ED
1)
2)
3)
02
3AL 88924 BAAA
178
128 / 178
Login system as 1354RM administrator and shutdown the application via PMC.
2)
3)
4)
Execute the 1354RM Master customizing following this instruction shown in Customize NMS
paragraph 3.5.2.2 at page 107.
5)
6)
7)
Login system as 1354RM administrator and startup the application via PMC.
2)
3)
Verify that no errors are displayed on standard output (warnings can be ignored).
4)
In case of errors, after upgrade instance completion, you can check the following trace files:
/alcatel/Install_Wizard/log/Installation_ <NMC Name>_#.log
/alcatel/Kernel/maintenance/trace/updateInstance.trace
ED
02
3AL 88924 BAAA
178
129 / 178
The 1359HA OSResilience NMC installation on board of an existing NMS does not involve only the system itself, but it requires to operate on many machine, including the spare system that are specifically requested in addition.
First of all you have to draw a clear picture of starting and final configurations. Just to better understand
the sequence of activity we can considering a common network management configuration shown in
Figure 23.
hosta
1354RM Client
1353NM Client
hostb
1354RM Master
hostc
1353NM Master
1353NM Client
Starting from the network management shown in Figure 23. the suggested 1359HA OSResilience configuration is shown by Figure 24. The picture distinguishes among Network Operation Center, Disaster
Recovery Center, and machine that do not belong to them (presentation machines). The white arrows
shows the clientmaster relationship when the NOC is operational, the striped ones when the DRC takes
the control.
ED
02
3AL 88924 BAAA
178
130 / 178
hosta
hostb
1353NM Client
1359HA OSRes
1354RM Master
hostb1
hostc
1353NM Master
1359HA OSRes
1353NM Client
hostc1
1359HA OSRes
1353NM Master
1354RM Master
1359HA OSRes
1353NM Client
1359HA OSRes
1354RM Client
ED
02
3AL 88924 BAAA
178
131 / 178
This paragraph provides the guidelines for installing 1359HA OSResilience on an existing TMN system
referring the previous example.
a)
b)
Install and customize new DRC machines (hostb1 and hostc1) with the same configuration of
the related companions adding the 1359HA OSResilience function referring the installation
chapter of this document, operating like a new fresh installation.
Login the system as TMN administrator (alcatel user), and shut down the applications.
2)
Predispose the system for 1359HA_OSRES SWP and create a 1359HA OSRES IM instance
for each local NMS IM instance subjected to resilience protection, and 1359HA_OSRES US
instance for each client referring a resilient IM.
3)
Install 1359HA OSResilience following the instruction shown by paragraph Install NMS or
NMC 3.5.2.1 at page 104.
4)
Execute any foreseen precustomization actions for 1359HA OSResilience following the instruction of paragraph Customize NMS or NMC 3.5.2.2 at page 107, with the exception that
you have to reply no[Enter] at the custom execution question:
NOTE:
Do you want to execute <NMS/NMC name> Custom? [y|n|q]
5)
Depending by the NMS/NMC instance type present on the machine, execute the procedure described in one of the following paragraphs:
Customize and Configure 1359HA OSResilience in distributed configuration.
Customize and Configure 1359HA OSResilience in cohosted configuration.
Customize and Configure 1359HA OSResilience in Presentation only configuration.
ED
1)
2)
02
3AL 88924 BAAA
178
132 / 178
A 1353NM Master in installed with one of the following NMS Master: 1354RM, 1354BM ATM or
1354BM ETH
A 1354RM Master in installed with one of the following NMS Master: 1354BM ATM or 1354BM ETH
a)
For each 1354BM Master subjected to resilience protection, execute the procedure described at
paragraph 4.2.3.2 Customize and Configure 1359HA OSResilience in distributed configuration .
b)
For each 1354RM Master subjected to resilience protection, when there is no 1354BM Master cohosted, execute the procedure described at paragraph 4.2.3.2 Customize and Configure 1359HA
OSResilience in distributed configuration .
c)
For each 1354RM Master subjected to resilience protection, when any 1354BM Master is cohosted,
execute the following procedure:
d)
ED
1)
Create an additional 1354RM Client instance file system as shown at paragraph 3.3.8.2 Manage 1354RM cohosted with any 1354BM NMS at page 87.
2)
3)
For each 1353NM Master subjected to resilience protection, when any 1354 Master is cohosted, execute the following procedure:
1)
Create an additional 1353NM Client instance file system as shown at paragraph 3.3.8.1 Manage 1353NM cohosted with any 1354 NMS at page 87.
2)
3)
02
3AL 88924 BAAA
178
133 / 178
For each NMS Client referring a NMS Master subjected to resilience protection:
ED
1)
2)
02
3AL 88924 BAAA
178
134 / 178
This paragraph is applicable to Alcatel TMN system where there is only NMS Client installed.
5 TROUBLESHOOTING
Here after is shown how to solve some trouble can occur during the installation, and how to proceed when
possible.
N.B.
ED
02
3AL 88924 BAAA
178
135 / 178
* Beginning Selection
tlvhhx:/: This target or source is already in use either
within this same session or by another session. A read or
write lock was denied.
* Target connection failed for tlvhhx:/.
ERROR:
More information may be found in the daemon logfile on this
target (default location is tlvhhx:/var/adm/sw/swagentd.log).
* Selection had errors.
ERROR:
=======
EXIT CODE: 1
SCinstall: Error end SCINSTALL
In this case you have to identify the reason of the fault (example: cdrom switched of, action on the target
depot, etc.), remove it, then recover the fault trying to preform again the failed action following this procedure:
The procedure will try again the installation of the failed package.
ED
02
3AL 88924 BAAA
178
136 / 178
When the error has been recovered remove the following files:
ED
02
3AL 88924 BAAA
178
137 / 178
scmanageswp script can exit for some reason, the situation in which is possible to operate to exit from
the error are the following:
The procedure exit with error because there is a pending installation process in progress, see
paragraph 5.3.2.1.
Execute the workaround describes on paragraph 5.3.1 at page 136,for recover the mistake.
5.3.2.2 scmanageswp Abnormally Terminated
scmanageswp uses a flag directory to prevent multiple execution from different shells, if you start the
script when another it is already running it will terminate issuing the message:
=>>> ERROR : SCMANAGESWP procedure already running on system.
Multi activation is not allowed !!!
=>>> ERROR
May occurs the flag directory it is not removed, for example when it is executed via telnet and a3 network
failure abnormally terminated the connection, in this case you have to manually unlock the synchronization
mechanism. Before proceed with the unlock you have to check there are no other scmanageswp running
instance by entering the commands:
...,sys,root # export UNIX95=true [Enter]
...,sys,root # ps fC scmanageswp [Enter]
Be careful, double check the command before press [Enter], because the ps command parameter can not be checked.
N.B.
If ps command does not issue any line you can proceed with the manual unlock by entering the command:
...,sys,root # rm r /tmp/.scswpsession [Enter]
ED
02
3AL 88924 BAAA
178
138 / 178
b)
c)
d)
e)
ED
02
3AL 88924 BAAA
178
139 / 178
|
0
0
0
grep kdcd
12:20:23 ? 0:01 /opt/krb5/sbin/kdcd l /dev/null
12:20:27 ? 0:04 /opt/krb5/sbin/kdcd l /dev/null
16:21:30 pts/ta
0:00 grep kdcd
The first workaround applicable is try to start it again by entering the command:
...,sys,root # /sbin/init.d/krbsrv start [Enter]
If after the manual restart the process is not able to stay running, check the size of the file /opt/krb5/tmp/
pf/kdcd.pid . If it is zero byte length you have to delete it and the file /vat/tmp/rc_krbkdcd one:
...,sys,root # rm /opt/krb5/tmp/pf/kdcd.pid [Enter]
...,sys,root #rm /var/tmp/rc_krbkdcd [Enter]
Then try again to start kdcd.
...,sys,root # /sbin/init.d/krbsrv start [Enter]
5.4.2 Kerberos kdcd High CPU Consuming
Has been observed that some times the kdcd process spends a long time to startup at CPU bound, the
resulting behavior is like the kdcd fail show in the previous paragraph, but the kdcd process is running CPU
bound (with top command it is shown with a CPU percent usage higher than 90%). in this case you have
to check the size of the file /vat/tmp/rc_krbkdcd, if it is larger than 10Mbyte you have to:
a)
b)
c)
d)
ED
02
3AL 88924 BAAA
178
140 / 178
If you remove the patch saved files, no one of these patches could be removed any more.
b)
c)
ED
02
3AL 88924 BAAA
178
141 / 178
Disks Selection
___________________________________________________________________________
Device MByte Hardware Path
Usage
Type
VolGroup
___________________________________________________________________________
c2t0d0 34720 0/1/1/0.0.0
Pri_Boot _Main_ vg00
c2t1d0 34720 0/1/1/0.1.0
_(free)_ ______ __________
___________________________________________________________________________
Press [Enter] to continue...
N.B.
If you have a disk mirror protection, the file system extension can ask for more than one
disk.
Before proceed within a 1359HA OSCluster environment you have to check that the
disks you want to use are not already in use from a different system.
If all precondition are met, you can enlarge the file system by entering the command:
...,sys,root # scextendfs <file system mount point> <desired free space> [Enter]
Analyze Mount Point:/usr
Request free MegaByte(s): 100
Evaluate size MegaByte(s): 1248
Extend Mount Point /usr to 1248 MByte
/usr successfully extended, new size will be available on next reboot
___________________________________________________________________________
System need reboot x complete extension of file system current in use
___________________________________________________________________________
The message System need reboot x complete extension of file system current in use means that the
extension will not available until system reboot.
ED
02
3AL 88924 BAAA
178
142 / 178
___________________________________________________________________________
ED
02
3AL 88924 BAAA
178
143 / 178
Sometimes the Mirror Disk/UX is not chosen at HPUX installation time, and someone decide to install
it later, in this case you can apply this procedure.
5.7.1 Mirror Disk/UX Installation Prerequisite.
The Mirror Disk/UX requires the appropriate HP license to authorize the its usage, and the system shutdown due to two reboots.
5.7.2 Mirror Disk/UX Configuration Prerequisite
To be able to properly configure Mirror Disk/UX you must be sure to have enough hard disk available
to store another copy o the entire file system. The highest level of availability is reached by assigning hard
disks belonging to different SCSI chains. Refer to paragraph 3.2.2.1.12.1 Disk Mirror Configuration
Policy at page 50.
5.7.3 Mirror Disk/UX Installation
When you not choose the mirror configuration the Mirror Disk/UX is not installed, here the procedure
to manually install it:
a)
b)
c)
d)
e)
f)
Login the system as root and ask all the user to log out the system.
Insert the CD with label SWPOSCONFV7.1.0 volume UX64_2 in the device driver end mount it
by entering:
...,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM [Enter]
To Install the Mirror DIsk/UX you have to enter the following command, but be careful because the
machine will be automatically rebooted:
...,sys,root # swinstall s /SD_CDROM/MirrorDisk.sd x autoreboot=true LVM [Enter]
When the system will be ready again, you have to login again as root.
Mount the CD with:
...,sys,root # mount r /dev/dsk/<cdrom device file> /SD_CDROM [Enter]
Install the Mirror Disk/UX patches by entering the command, but be careful because the machine
will be automatically rebooted:
...,sys,root # swinstall s /SD_CDROM/MirrorPatch.sd x autoreboot=true \ [Enter]
x reinstall=true x software=* [Enter]
When the system will prompt you for login check in /var/adm/sw/swagent.log for any error met in the software of patch installation.
ED
02
3AL 88924 BAAA
178
144 / 178
ED
02
3AL 88924 BAAA
178
145 / 178
To safety stop the system it is suggested to perform the system shutdown. This activity allows to stop the
entire system by executing the shutdown procedure of each software component. The shutdown command is allowed only by root user and foresees many switches, the most used are r and h . The first
one performs the automatic reboot, and the second have to be used when you have to switch off the system power supply, because it halts the system.
A.2.1 System Shutdown with Reboot
The system shutdown command allows to perform the system reboot, by entering:
...,sys,root # shutdown r now [Enter]
A.2.2 System Halt
The system shutdown command allows to perform the system switch off, by entering:
...,sys,root # shutdown h now [Enter]
Wait until the RUN lamp is switched off or the system status gets in SHUT on the front display
before switch off the power supply.
N.B.
ED
02
3AL 88924 BAAA
178
146 / 178
This is the base platform for all the Alcatel TNM Applications. No instance is foreseen, but it has to
be always installed.
1353NM V7.3
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
N.B.
You must install 1353NM on 1354 subsystem, and you have to create a 1353NM
instance for each 1353NM system under control of 1354 one.
1354RM V7.4
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
1354BMETH V7.3
Instance Definition: Identifier N ______
1359HA OSCluster Protection
type: Master Client Spare system ( only for 1359HA OSCluster )
Size(*):Small Medium Large
1355VPN
V5.0.3
Instance Definition: Identifier N ______
ED
1354SN V5.0
Instance Definition: Identifier N ______
type: Master Client
Size(*):Small Medium Large
02
3AL 88924 BAAA
178
147 / 178
1354SY V7.4
Instance Definition: Identifier N ______
type: Master Client
Size(*):Small Medium Large
NMS Dependencies.
1359IOO V5.2
1359ISN V5.0
1354RM
1359HA_OSRES V7.1.1
Instance Definition: Identifier N ______
type:
Master
2 Client
4 Client
8 Client
1353NM 7.3
ED
V1.1.7
1354RM
02
3AL 88924 BAAA
178
148 / 178
Swap Required
Software Size
OSKernel
100
2600
1000
1353NM
500
7500
4000
1354BM ETH
500
1120
350
1354BM PR
200
100
35
1354RM
500
1120
600
1355VPN
500
500
10
1359HA OSRES
100
10
1359ISN
N.A.
N.A.
100
1359IOO
N.A.
N.A.
40
NR7.4 ADDENDUM 1
N.A.
N.A.
1100
NMS
Master Small
Swap
OSKernel
Data
Master Medium
Master Large
Presentation(*)
Swap
Data
Swap
Data
Swap
Data
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
200
500
3000
1500
5000
2500
9000
250
250
1354BM ETH
1500
3000
3500
5000
7500
9000
2000
200
1354BM PR
3500
1700
3000
500
1354RM
1500
3000
3500
5000
7500
9000
2000
400
1354SN
1000
1000
1500
2000
2500
5000
300
300
500
3000
1353NM
1355VPN
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
1359HA OSCLS
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
1359HA OSRES
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
N.A.
ED
02
3AL 88924 BAAA
178
149 / 178
CD Label
CD Code
Description
SWPOSCONF_BOOTV7.1.1
DVD
SWPOSCONF_PLTV7.1.1 DVD
SWPOSCONF_BOOTV7.1.1 CD
SWPOSCONF_PLTV7.1.1 CD
SWPOSCONF_ADDV7.1.1_P04
DVD
SWPOSCONF_ADDV7.1.1_P04
CD
SWPOS_KERNELV7.1.2
SWP1353NM_APPV7.3
SWP1354RM_APPV7.4
SWP1354BM_ETHV7.3.0.5_P2
SWP1353BM_PRV7.2
SWP1353BM_ATMV7.1.4
SWP1354SY_APPV7.4
SWP1355VPN_APPV5.0
SWP1359IOO_APPV5.2
SWP1359ISN_APPV5.0
SWP1359HA_OSCLSV7.1
SWP1359HA_OSRESV7.1.1
SWPNR74_ADD01
ED
02
3AL 88924 BAAA
178
150 / 178
The following table provides the Alcatel CD codes of all media provided with NR7.4
cd /opt/graphon/pc [Enter]
bin [Enter]
get go_setup_2*.exe [Enter]
quit [Enter]
b)
c)
The installation application checks if there is a previous version installed. If a previous version is
found remove it by follow the instruction in paragraph Automatic Removal of GoGlobalUX/Previous Version C.2.1 at page 154 , otherwise proceed with the next point.
ED
02
3AL 88924 BAAA
178
151 / 178
d)
f)
Choose your destination location and click on Next to go on. Wait a few seconds the install procedure.
ED
02
3AL 88924 BAAA
178
152 / 178
g)
You have to insert the Server Address of the machine that you want to be connected to.
Click on Connect. The Authentication window will be opened
Username
Password
Click on OK. GoGlobalUX will open a connection with the configured machine.
ED
02
3AL 88924 BAAA
178
153 / 178
If installing GoGlobalUX a previous version in installed the application asks you the authorization to remove it by issuing the window:
You can now install the new version of the software by stating again the installation application.
ED
02
3AL 88924 BAAA
178
154 / 178
If you have three or more machines, you have to setup a Three Redundant License Servers configuration, in accordance with the following rules:.
the three license server machines should be located physically close to each other (if possible).
if in your network there are less than three nodes, you have to define a the license server, and all the
required licenses have to be loaded on that server.
On the license server machine(s) will be loaded the license(s) data obtained as showed in the paragraph
C.3.3.
C.3.2 Retrieve License Servers Identity
Meaningful only for the license server machine(s).
When you have selected the license server machine(s), for each of them you have to retrieve the machine
identity by executing the following commands:
a)
b)
c)
[Enter]
[Enter]
The obtained data will be used in a successive phase of the license request activity.
ED
02
3AL 88924 BAAA
178
155 / 178
After that, you can to require the necessary license(s) to activate GoGlobalUX on your machine(s) visiting
the GraphOn Licensing web site through your web browser, by typing the following URL:
http://www.graphon.com/support/license.shtml
The following window will appear:
Click on GoGlobal Permanent Licenses and the following registration form will appear:
ED
02
3AL 88924 BAAA
178
156 / 178
Scroll down along the window using the scroll bar and fill the following fields about the required registration
information:
Name
Company
Address & Address2
City
State/Province
Country
Postal Code
Phone
Email Address
(1)
(1)
(1)
(1)
(2)
(1)
(1)
(1)
(1)
(1) Introduce the data of the reference person near the customer or the your own ones.
(2) Leave it as Not Specified when the system is located outside of U.S.A..
Fill in the data, then click on Next> button to continue with the next window.
The Software Agreement window will appear:
Scroll down until the bottom of the window using the scroll bar and click on I Accept button to continue.
The License Information window will appear:
ED
02
3AL 88924 BAAA
178
157 / 178
N.B.
Scroll down along the window using the scroll bar and fill the following fields:
Product Code (see the Product Code value on the PURCHASED GraphOn LICENSE FOR ALCATEL USE FOR RESALE document if present)
Host Name (see the paragraph C.3.2)
Host ID (see the paragraph C.3.2)
Now if you have the Three Redundant License Servers configuration you have to set YES in the box
close to the label Are you using redundant servers?, and fill in the three couple of information: Hostname and Hostid with the data of each license server.
ED
02
3AL 88924 BAAA
178
158 / 178
Put the showed data in the license file of the license server machine (see the paragraph C.3.4.1.1) and
click on the Back button to come back to the Product Code window to require (eventually) another license
otherwise, if you are terminated, click on File and Close option to exit from the web browser.
ED
02
3AL 88924 BAAA
178
159 / 178
GraphOn Corp. provides both permanent or demo license, hereafter some information to help you to configure the GoGlobalUX license files and daemons.
C.3.4.1Permanent License
GoGlobalUX permanent licenses are provided as network floating point, that meas you have to promote one or three machines a License Server and all the other will be License Client.
To be able to use them you have to perform the following actions:
1)
2)
3)
4)
Example of /opt/graphon/etc/license.dat file with three servers and two licenses (INCREMENT options)
defined:
# NOTE: You can change the hostname on the SERVER line.
#
You can also add a port number after the hostid on
#
the SERVER line, like:
#
SERVER hostname.domain.com 00HOSTID0 27001
#
which will make the lmgrd managing this file use
#
port 27001.
#
Most other changes will invalidate this file.
#
ISSUED_DATE=23jan2002
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
Add TCP port number (27011) at any line beginning with SERVER:
Example from:
SERVER host_c 839dc26
to:
SERVER host_c 839dc26 27011
Copy this file on each license server when the three redundant configuration is foreseen.
ED
02
3AL 88924 BAAA
178
160 / 178
SERVER
is a keyword
<host>
<port>
is the IP port number stored in the license.dat file as fourth field of the line
starting with SERVER, if that field is blank 27000 have to be used.
[Enter]
Because hpux startup launch both License and GraphOn Daemons, it is advisable to execute the daemon stop before. The entire procedure will be:
...,sys,root # /sbin/init.d/goglobalux stop [Enter]
...,sys,root # /sbin/init.d/goglobalux start [Enter]
When the daemons will be started on the single license server on at least two license server nodes for the
three redundant configuration, you will be able to open a GoGlobalUX 2.0 session from any PC to the
license server machine.
ED
02
3AL 88924 BAAA
178
161 / 178
To be able to access the hpux machine via GoGlobalUX you need to get a license, this license will
be granted by the license server(s) via network, that means any hpux system (license client) have to
be able to connect the license server(s) via network. Moreover the license server(s) have to be referred
by name.
C.3.4.3.1 Verify License Server Connectivity
Before starting the client machine configuration you have to verify the license server machine(s) connectivity, the easiest way to do it is try a ping to any license server host name:
..,sys,root # ping <Hostname> [Enter]
where <Hostname> is the name of the remote license server machine(s).
If the server replies the ping request an output like the following will be provided:
,sys,root # ping hostc 64 2
PING hostc: 64 byte packets
64 bytes from 192.202.21.8: icmp_seq=0. time=0. ms
64 bytes from 192.202.21.8: icmp_seq=1. time=0. ms
hostc PING Statistics
2 packets transmitted, 2 packets received, 0% packet loss
roundtrip (ms) min/avg/max = 0/0/0
Otherwise, there is something wrong. From the error message issued by telnet you can have an idea
of the problem.
First of all it is better to verify that the server is running. It the server is running check on the
/etc/host file if the IP address defined for the specified server is correct. If also the IP address
is correct, the reason can depend by the Default Gateway, check is adefault gateway si defined
and reachable. If you do not know name and IP address of the network default gateway refer
to the network administrator.
ED
02
3AL 88924 BAAA
178
162 / 178
N.B.
[Enter]
If the file license daemons are active, an output like the following will be displayed:
lmstat Copyright (C) 19892002 Globetrotter Software, Inc.
Flexible License Manager status on Fri 12/5/2003 10:07
License server status: 27011@host_c,27011@host_d,27011@host_e
License file(s) on host_c: /opt/graphon/etc/license.dat:
host_c: license server UP (MASTER) v8.2
host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges:
The shown output is related to a three redundant server configuration, if you have a single license server, the data shown with italic font will be not shown.
N.B.
Otherwise an error message advise you of a problem, check the status of the daemons on the license server them selves.
C.3.4.3.3 Copy the license_server.dat File from a License Server
All the configuration precondition are now verified, it is possible to configure the license client machine,
the configuration consists only in creating a copy of the license_server.dat file from a license server machine to this one. Like for servers, when the license_server.dat file is created or modified the daemons
have to be stopped and started to catch the changes.
ED
02
3AL 88924 BAAA
178
163 / 178
In order to check the correct definition of the license server in the license_server.dat file you can execute
the script /opt/graphon/etc/check_server.
..,sys,root # /opt/graphon/etc/check_server
[Enter]
If the configuration is correct the output have to contain one set of line for each server defined, like the
following example:
lmstat Copyright (C) 19892002 Globetrotter Software, Inc.
Flexible License Manager status on Fri 12/5/2003 10:20
License server status: 27011@host_c,27011@host_d,27011@host_e
License file(s) on host_c: /opt/graphon/etc/license.dat://:
host_c: license server UP (MASTER) v8.2
host_d: license server UP v8.2
host_e: license server UP v8.2
Vendor daemon status (on host_c):
graphon: UP v8.2
Feature usage info:
Users of bridges:
Now the system ready, you can open a GoGlobalUX 2.1 session from any PC to the this machine until
at least one license is available on the servers.
ED
02
3AL 88924 BAAA
178
164 / 178
b)
Require the authorization key via GraphOn WEB Page providing the same host ID of the already
requested keys (the host id are related to the license servers!). Hereby an example of a new authorization key requested for the license servers already see in the paragraph C.3.4.1.1 at page 160. You
can see the server lines have the same values in the third field that means the same host ID.
#
# NOTE: You can change the hostname on the SERVER line.
#
You can also add a port number after the hostid on
#
the SERVER line, like:
.
.
#
ISSUED_DATE=23jan2002
#
SERVER host_c 77fd17fe
SERVER host_d 77df65d1
SERVER host_e 7751b870
VENDOR graphon
INCREMENT UX graphon 2.0 permanent 1BB31C150136 \
user_info=Paolo Rossi\
paolo.rossi@alcatel.it ISSUER=GrapOn \
Corporation ISSUED=08jan2002 NOTICE=Copyright (C) \
19962002 GraphOn Corporation. All Rights Reserved ck=45
c)
You have to copy the INCREMENT line(s) from the just received authorization key a the end of the
/opt/graphon/etc/license.dat file:
N.B.
When a back slash \ is present at the end of line, also the next line have to be included.
..,sys,root # vi /opt/graphon/etc/license.dat
1)
ED
[Enter]
Move to last line in file and insert the INCREMENT line(s). For example, if you have the authorization key shown at page 160 active on the system, and receive from GraphOn the one shown
at page 165, the resulting file will be:
#
# NOTE: You can change the hostname on the SERVER line.
#
You can also add a port number after the hostid on
.
.
#
#
ISSUED_DATE=23jan2002
#
SERVER host_c 77fd17fe 27011
SERVER host_d 77df65d1 27011
SERVER host_e 7751b870 27011
VENDOR graphon
INCREMENT UX graphon 2.0 permanent FDE548BE0802 ck=164
02
3AL 88924 BAAA
178
165 / 178
2)
d)
Save and exit vi file pressing [Esc] and typing :x! and [Enter].
[Enter]
After completing these steps, the new GoGlobalUX licenses will be available.
C.3.5.1Demo Licenses
GoGlobalUX demo license can be retrieve from the GraphOn Web server. The demo license are node
locked, and to use them you have just to copy the authorization key into the license.dat file, and delete
license_server.dat if exists.
ED
02
3AL 88924 BAAA
178
166 / 178
In the first kind of server (with two disk enclosures) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS0. The connector 2 of the BusB is connected to the connector 2 of the BusA.
The connector 1 of the BusA is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusB in the HAS1. The connector 2 of the
BusB is connected to the connector 2 of the BusA. The connector 1 of the BusA is closed with a SCSI
terminator.
HSC
FWSCSI 1
CPU
: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 2
HAS0
1
Bus B
2
Bus A
2
Bus B
2
Bus A
2
HAS1
ED
02
3AL 88924 BAAA
178
167 / 178
In the second kind of server (with one disk cabinet) the FWSCSI1 bus is connected to the connector
1 of the BusB in the HAS, and the connector 2 of the BusB is closed with a SCSI terminator.
The FWSCSI2 bus is connected to the connector 1 of the BusA and the connector 2 of the BusA is
closed with a SCSI terminator.
HSC
CPU
FWSCSI 1
: FWSCSI cable
: FWSCSI terminator
FWSCSI 2
: FWSCSI connector
HAS
1
Bus B
2
Bus A
2
ED
02
3AL 88924 BAAA
178
168 / 178
b)
c)
The last configuration is just an example of K Class server cluster, with three nodes.
: FWSCSI cable
: FWSCSI terminator
: FWSCSI connector
FWSCSI 1
FWSCSI 1
FWSCSI 1
FWSCSI 2
FWSCSI 2
FWSCSI 2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
Bus B
2
Bus A
2
ED
02
3AL 88924 BAAA
178
169 / 178
For the server R the recommended configuration of the HSC and Lan boards is indicated in
Figure 34. :
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.
N.B.
CPU
: SCSI cable
FWSCSI 1
: SCSI terminator
FWSCSI 2
TURBO 3
: FWSCSI connector
HSC
HAS
1
Bus B
2
1
Bus A
2
ED
02
3AL 88924 BAAA
178
170 / 178
This paragraph shows the suggested SCSI connections for the R Class servers.
/0/0/2/0.2.0
(c2t2d0)
DVD
/0/0/1/0.0.0
(c1t0d0)
/0/0/1/0.2.0
(c1t2d0)
Main disks
Figure 35. Front view of L Server (without cover panel)
PCI Slots
Lan RJ45
Connector
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.
ED
02
3AL 88924 BAAA
178
171 / 178
The A Class and RP2430 are the HP9000 server entry levels, them are not provided with external disks
and can equip up to two hard disk units. These hard disks are located in the server front, behind a little
door located on the left side.
Each disk is connected to a different SCSI bus, that guarantee the high availability.
Disks Location
Figure 37. Front view of A Class and RP2430 Servers (without cover panel)
ED
02
3AL 88924 BAAA
178
172 / 178
10
11 12 13 14 15
ED
02
3AL 88924 BAAA
178
173 / 178
10 11 12 13 14
ED
02
3AL 88924 BAAA
178
174 / 178
Disk Storage
N4000
SC10
RP7400
SC10, DS2405
I
I I
I
O
: HD SCSI terminator
5 4 3 2 1
O
A
DAT
PCI Slots
6
12
11 The two internal
5
are place
10 disks
in this location4
9
3
8
2
1
7
DVD
PCI Slots
The position of the components in the rack is not predictable, so the N4000 server can be placed
on top of SC10.
N.B.
It is advisable to install the PCI cards balancing them in the right and left slots, starting from the
bottom.
ED
02
3AL 88924 BAAA
178
175 / 178
This paragraph provides the instructions for the configuration of the HP HP9000 RP7400 server configured with the DS2405 external disk cabinet.
To implement the disk mirroring on DS2405 Disk Storage, the cabinet have to be connected in
dualaccess mode, that means the disks can be accessed by two ways, the side effect of this
cable connection is that the hard disks are shown twice.
: VHDCI SCSI cable
: HD SCSI terminator
DVD
DAT
PCI Slots
6
12
11 The two internal 5
are place
10 disks
in this location 4
9
3
8
2
1
7
PCI Slots
ED
02
3AL 88924 BAAA
178
176 / 178
: HD SCSI terminator
DAT
DVD
1 2
3 4
5 6 7 8 1 2
3 4
5 6 7 8
ED
02
3AL 88924 BAAA
178
177 / 178
This paragraph provides the instructions for the configuration of the HP HP9000 RP7410 server configured with the VA7110 external disk cabinet connected via fiber channel swicth.
To implement the disk mirroring on DS2405 Disk Storage, the cabinets have to be connected in
dualaccess mode, that means the disks can be accessed by two ways, the side effect of this
cable connection is that the hard disks are shown twice.
: HD SCSI terminator
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
DAT
DVD
RP7410
1 2 3 4 5 6 7 81 2 3 4 5 6 7 8
FC Switch
FC Switch
END OF DOCUMENT
ED
02
3AL 88924 BAAA
178
178 / 178
numerate
numbered
da from
a to
1/178
178/178
TARGHETTE - LABELS
frontespizio
front
manuale
manual
2
178
180
90
ED
02
RELEASED
3AL 88924 BAAA
4
1/ 4
1350 NR7.4
Originators
B.Bosisio
M.Occhietti
NR 7.4
INSTALLATION GUIDE
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
OND
NM
1350
Internal :
External
Approvals
Name
App.
F.Casasole
Name
App.
INFORMAZIONI EDITORIALI
sistemazione figlist
Network Release
INSTALLATION GUIDE
ED
02
RELEASED
3AL 88924 BAAA
4
2/ 4
1350 Rel.7.4
Network Release
NR7.4
INSTALLATION GUIDE
3AL 88924 BAAA Ed.02
VOL.1/1
VOL.1/1
1350 Management Suite
1350 Rel.7.4
3AL 88924 BAAA Ed.02
Network Release
NR7.4
INSTALLATION GUIDE
VOL.1/1
Network Release
NR7.4
INSTALLATION GUIDE
VOL.1/1
ED
02
INSTALLATION GUIDE
VOL.1/1
RELEASED
3AL 88924 BAAA
4
3/ 4
ED
02
RELEASED
4/ 4
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.