1350 rel.7.1 administration guide.pdf

3AL 88893 CAAA Ed.03

Administration Guide

Alcatel 1350Management Suite

1350 Rel.7.1Network Release

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

1

03

/3AL 88893 CAAA

112

112

1350 REL.7.1 ADMINISTRATION GUIDE

TABLE OF CONTENTS

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

HISTORY 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 PRELIMINARY 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General Information 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Handbook applicability 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Product-release handbooks 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 Handbooks related to the specific software application 8. . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Referred External Documents 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.1 NR Related Handbooks 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 Registered Trademarks 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6 Overview 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7 Conventions 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 INTRODUCTION 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 IP ADDRESS AND NODE NAME MANAGEMENT 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Fuctional Restrictions 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Basic Fuctions 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Network Example 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Node Name Management Interface 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.1 1 – INIT 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2 2 – ADD 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.3 3 – REMOVE 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.4 4 – PUT 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.5 5 – LIST 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.6 6 – TOTALIGN & 7 – ACTALIGN 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.7 8 – GRPOPEN, 9 – GRPIMPORT & 10 – GRPMERGE 19. . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.8 11 – CHIPADDR 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.9 12 – CHHOSTNAME 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.10 13– CHNETMASK 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.11 14 – CHGATEWAY 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.12 15 – DNSADD 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.13 16 – DNSCHANGE 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.14 17 – DNSREMOVE 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

01 050428 F.Casasole ITAVE B.Bosisio ITAVE

02 050901 ECR24299 F.Casasole ITAVE B.Bosisio ITAVE

06030303 ECR31574 F.Casasole ITAVE B.Bosisio ITAVE

1350 Management SuiteNR7.1ADMINSTRATION GUIDE

M.Occhietti

S.Franco

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

2

03

/3AL 88893 CAAA

112

112

4 BACKUP AND RESTORE 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Full disks backup/restore 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1 Full Backup Strategy 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Single Volume Group Backup 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 Single Volume Group Backup Strategy 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Restrictions 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 Ignite Recovery tape restrictions 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 1359HA OS Cluster Support 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.3 Mirror Disk configuration rebuild 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.4 Restriction on Console 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.5 Required disk space 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.6 Compatibility 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7 Restriction on Backup 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 FULL BACKUP 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Start the “scbackup” script 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2 Create the IRT 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.3 Backup the entire disks contents 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 FULL RESTORE 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Restore of IRT Tape Set 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Restore from Fbackup Tape Set 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.3 Restore MIrror Configuration 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.4 Restore Warning and/or Error Messages 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 BACKUP AND RESTORE Know problems and workaroundS 59. . . . . . . . . . . . . . . . . . . . . . 4.6.1 Ignite Rcovery Problem 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.2 Recovery Archive Error – Ignite recovery 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.3 Full User Disk Backup problem 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 MIRROR DISK/UX MANAGEMENT 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Configuring Mirror Disk/UX 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1.1 Prerequisite 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.2 Install Mirror Disk/UX 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.3 Configure Mirror Disk/UX with Alcatel Script 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 NETWORK DEPOT MANAGEMENT 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Platform Software Depot 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1 Build Depot know bug and workaround 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.2 Additional Software 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.3 Software Depot Update 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 Application Software Depot 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.1 Authorize Access to Application Depot 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 Disk Requirement Tables 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 SECURITY 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Introduction 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Security Preparation 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.1 Software Requirements 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2 Security User and Groups 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Customize Login and FTP Banners 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Security Profiles 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.5 Access to Secure Host 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.6 Define the System Password Configuration 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 Security Set–Up 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1 Security in High Availability environment Restictions 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2 Security Activation 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

3

03

/3AL 88893 CAAA

112

112

7.3.3 Required Software Installation 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.4 Security set up Execution 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.4 Remove Security 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Change Security Profile 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 PRINTER CONFIGURATION 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Configure a Printer Queue within Local Spooler 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.1 Start the System Spooler 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Configure Printer Booting from Local System 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 GSP & MP PROCESSORS CONFIGURATION 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Configure Guardian Service Processor 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1.1 Access the GSP with Local Terminal or PC. 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 Configure GSP LAN console 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.3 Define the Administrator User 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.4 Enable the Access via LAN 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.5 Check the GSP LAN Console Accessibility 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.6 How to get to the GSP Console 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2 Configure Management Process 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1 Access the MP with Local Terminal or PC. 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.2 Configure Lan Console 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX A FILE EXAMPLES 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1 security.params 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

4

03

/3AL 88893 CAAA

112

112

LIST OF FIGURES AND TABLES

FIGURESFigure 1. Network Example 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Example of disk configuration 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Printer Characteriscs Menu 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TABLESTable 1. Bus types required for DLT to be recognized as a bootable media 32. . . . . . . . . . . . . . . . . . . . Table 2. Disk requirements for NMS Software 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Software requested by 1350 MS Security 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Security User 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Security Groups 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6. Security Feature 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7. Security Password Structure Constants 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8. Security Password Aging Parameters 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 9. Printer Configuration Data Requested. 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

5

03

/3AL 88893 CAAA

112

112

HISTORY

Edition Date Notes

Ed. 01 April 2005 OS–Conf Administration Guide

Ed. 02 September 2005 Included security feature

Ed. 03 March 2006 Added error message description in restore formbackup tape.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

6

03

/3AL 88893 CAAA

112

112

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

7

03

/3AL 88893 CAAA

112

112

1 PRELIMINARY

1.1 General Information

WARNING

ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims theimplied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liablefor errors contained herein or for damages, whether direct, indirect, consequential, incidental, or spe-cial, in connection with the furnishing, performance, or use of this material.

NOTICE

The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on thepart of ALCATEL.

COPYRIGHT NOTIFICATION

The technical information of this manual is the property of ALCATEL and must not be copied, repro-duced or disclosed to a third party without written consent.

1.2 Handbook applicability

This handbook applies to the following product-releases:

PRODUCT ANV P/N

1350 3AL 88852 AAAA

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

1350 7.1 7.1D 3AL 88851 ABAA

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONSHandbooks relevant to software applications (typically the Operator’s Handbooks) are not mod-ified unless the new software ”version” distributed to Customers implies man–machine interfacechanges or in case of slight modifications not affecting the understanding of the explained pro-cedures.Moreover, should the screen prints included in the handbook contain the product-release’s ”ver-sion” marking, they are not replaced in the handbooks related to a subsequent version, if thescreen contents are unchanged.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

8

03

/3AL 88893 CAAA

112

112

1.3 Product-release handbooks

The list of handbooks given here below is valid on the issue date of this Handbook andcan 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 thisHandbook.

The standard Customer Documentation in the English language for the equipment whose product-re-lease-version is stated in para.1.2 on page 7 consists of the following handbooks:

1.3.1 Handbooks related to the specific software application

REF HANDBOOK ANV Part No.THIS

HANDBOOK

[1]1350 Rel7.1Administration Guide

3AL 88893 CAAA

[2]1350 Rel7.1Installation Guide

3AL 88893 BAAA

[3]1350 Rel7.1System Management Operator’s Handbook

3AL 88893 AAAA

1.4 Referred External Documents

For factory internal use only.

[4] HP System Partitions Guide – Revision 3.1� Copyright 2002 Hewlett–Packard Company. All rights reserved.Part Number: B2355–90746

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

9

03

/3AL 88893 CAAA

112

112

1.4.1 NR Related Handbooks

REF HANDBOOK ANV Part No.THIS

HANDBOOKor note

[5]1353NM 7.0Administration Guide

3AL 89061 BAAA

[6]1354RM 7.1Administration Guide

3AL 61345 BAAA

[7]1354BM 7.1AATM Administration Guide

3AG 23946 BAAA

[8]1354BM 7.1EETH Administration Guide

3AG 23946 DAAA

[9]1354BM 7.1RPR Installation Guide

3AG 23946 FAAA

[10]1355VPN 4.0Administration Guide

3AL 72170 CAAA

[11]1359HA OS–Cluster 7.1Administration Guide

3AL 88127 BAAA

[12]1359HA OS–Resilience 7.1Administration Guide

3AL 88129 BAAA

[13]1359IOO 5.1Administration Guide

3AL 88347 AAAA

[14]1359ISN 4.0Administration Guide

3AL88235 AAAA

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

10

03

/3AL 88893 CAAA

112

112

1.5 Registered Trademarks

– UNIX is a registered trademark of UNIX System Laboratories in the U.S.A. and other countries.

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

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

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

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

– ORACLE is a registered trademark of Oracle Corporation.

1.6 Overview

This document describes how to install and configure the HP 9000 computer systems in order to allow thecorrect usage of Network Map Management (NM) application.

1.7 Conventions

The following conventions are used in this manual:

[Enter] A key name is shown between square brackets to indicate that you press anamed key on the keyboard.

courier Courier type is uses to indicate the output produced by the system or data thatyou 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 theparticular instance of the system. It must be substituted with the correct data.

# Actions must be performed as root.

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

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

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

SQL> Actions must be performed in SQL utility.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

11

03

/3AL 88893 CAAA

112

112

2 INTRODUCTION

This document describes how to administering a HP 9000 Server with OS–Conf configuration tools. OS–Conf provides some function to make easier the HP–UX administration in agreement with Alcatel SoftwareManagement. These tools provide aids for software installation and removal, combined with HP–UX oper-ating system configuration and security improvements.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

12

03

/3AL 88893 CAAA

112

112

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

13

03

/3AL 88893 CAAA

112

112

3 IP ADDRESS AND NODE NAME MANAGEMENT

The purpose of the Node Name Management tool is provide a centralized and integrated mechanism toadminister the IP address and host name relationship for the HP servers used inside the Alcatel TMN ap-plication.

Node Name Management allows configuring the TCP/IP address and host name relationship on the entirenodes in the Alcatel Network Management. Its main purpose is allowing the host naming distributed man-agement.

The code design philosophy is based on the working group concept. The group is an entity that includesthe entire node needs to work together. The first node placed in configuration creates the group, and thenthe other will be added.

Each node belongs the group has a copy of entire node name repository, and it is able to add a new nodeto the group, or remove an existing one. Any action can be carried on only if there is the group node mem-ber quorum. We decide to implement this philosophy after the experience on the previous NR where it wasvery difficult to review the configuration when a node was failed or simply unreachable.

The node group members are not the only entities in the repository database, in fact the communicationsare not limited to the node group members, but there are other nodes in the TPC/IP network that can beuseful to know. These nodes can be described in the database as ”External”, that means them can be add-ed and removed such as a ”Member” one, but them can non remove nether add any thing, and them arenot voters to reach the quorum. Another special entity are the ”Cluster” nodes, that are specific designedfor virtual IP Address of MC/Service Guard cluster application packages, the characteristic of this kind ofelement are: them have to be defined in the Kerberos database like ”Members”, but them are not votersfor quorum, nether useful to execute actions.

An important principle regards the security, in fact to prevent back–doors or other strategy to allow the ac-tion of a node to another, to include a new node in the group, it is not enough that a member node addit to the database, but it have to authorize the group access, by performing a add action by itself. Just tobetter explain the behavior with an example:

We have a group with three members: hosta, hostb and hostc, if have to add hostd to the group the firstaction has to be done from one of the three members, it have to add hostd to the database, that meansall the three nodes will know hostd and its IP address, and implicitly accept request from that source. Thenhostd have to accept the group membership by performing an add on itself specifying one of the groupmembers. With this action hostd authorize the other group member to operate on itself.

N.B. This tool does not provide any support for the IP network design, it just allow to reducethe effort in describing an already planned network.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

14

03

/3AL 88893 CAAA

112

112

3.1 Fuctional Restrictions

The Node name Management program bases network communication on OS–Kernel ”Remotizer” library,that means OS–Kernel have to be installed and customized before be able to correctly execute the Nodename Management program.

The Node Name Management can not be started before OS–Kernel installation and cus-tomization.

To allow the correct execution of the program, the involved machines does not havemore five minutes difference in system time. Be careful, the relevant system time doesnot involve the Time Zone, so you have to check the time difference by entering the com-mand: date –u

3.2 Basic Fuctions

This paragraph briefly shows the actions foreseen by OS–Conf Node Name Management:

– Found the group is done by network management first node.

– Add new node allows adding any type of host to the database.

– Remove a node allows removing any type of host to the database.

– List of data provides the contents of database in terms of hostname and its characteristics.

– IP address and hostname changes.

– Single or multiple node alignment.

– Change network gateway and subnet mask.

– Add and remove DNS configuration.

– Group management.

All these functions are available through a menu driven interface, this interface is described hereafter.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

15

03

/3AL 88893 CAAA

112

112

3.3 Network Example

To make easier understand the software behavior an example of network will be provided. Within this net-work management system we have five HP9000 servers, with the following information:

– hosta IP address 192.200.49.1 Role 1354RM Client– hostb IP address 192.202.21.7 Role 1353NM Master– hostc IP address 192.202.21.8 Role 1354RM Client– hostd IP address 192.202.22.4 Role 1354RM Master– hoste IP address 192.200.22.5 Role 1353SH Master

There are other network equipments, such as rooters, printers (local and network), personal computer,and time synchronization equipments:

– router1 IP address 192.200.49.244 Left LAN router – router2 IP address 192.202.21.244 Central LAN router– gpsrec1 IP address 192.202.21.51 Time synchronization via Global Position System.– router3 IP address 192.202.22.244 Right LAN router– lp1 IP address 192.202.22.6 Network line printer.

gpsrec1 (GPS time receiver)

hosta

hostb hostd hoste

hostc

��

lp1 (network printer)

Figure 1. Network Example

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

16

03

/3AL 88893 CAAA

112

112

3.4 Node Name Management Interface

The Node name Management program interface is menu oriented, when you can start this software bylogin as user “root” and entering:

...,sys,root # scNMmng [Enter]

It prompts you the following menu:

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

– Network Management Nodes (V2.3.1) –

Management options:

1 – INIT = network map init. 11 – CHIPADDR = change IP addr.

2 – ADD = add a node 12 – CHNODENAME = change hostname

3 – REMOVE = remove a node 13 – CHNETMASK = change netmask

4 – PUT = put network map 14 – CHGATEWAY = change gateway

5 – LIST = list network map 15 – DNSADD = add to DNS

6 – TOTALIGN = alignment each node 16 – DNSCHANGE = change DNS

7 – ACTALIGN = alignment a single node 17 – DNSREMOVE = remove from DNS

8 – GRPOPEN = open the current group

9 – GRPIMPORT = import a remote group

10 – GRPMERGE = merge two groups [0] – exit

Enter management option [0..17] :

3.4.1 1 – INIT

Establish the Group: you are installing the first NMS system of the entire network. Before perform any activ-ity you have to initialize the Node Management persistent data.

The detailed procedure is:

a ) Login a node as root user (hostb of example in paragraph 3.3 ).

b ) Run the “scNMmng” script (see paragraph 3.4 at page 16) then enter ”1“ and [Enter] to execute theinitialization. This action creates the group.

c ) The execution will be confirmed by the message:** MESSAGE: node ”<hostname>” (<IP_addr>) initialized.

Press [Enter] to continue.

The Node Management Persistent Data has been initialized. Press [Enter] to go back to main menu,then press [Enter] or “0” and [Enter] to exit.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

17

03

/3AL 88893 CAAA

112

112

3.4.2 2 – ADD

The Node Name Management procedure have been design to guarantee the security of the entire system,that meas the access to any system in configuration must be formally granted. As consequence it is notpossible to operate on a remote system without authorize the access to it in advance, that also means itis not possible to add a new node to a group in one shot. We have to authorize the new node to accessthe group, and then the new node authorize all the machines belonging to the group to operate with it. Itis important to preform the to action in this order because the action performed by the adjoining ma-chine have to be able to retrieve from the specified group member the data related to all the system belong-ing to the group.

3.4.2.1 Add a New Group Member

You add a new node member to the group when the adding node is a TMN system, that have to swap dataover the network with the other group members. To add a new member you have to perform the node addi-tion on two machines:

1 ) First of all, you have to add the new system on a machine already belonging to the group. Thisaction stores the new host in the database of all nodes belonging to the group, and authorizenew candidate member to join the group.

2 ) Then, execute again the add action on the machine that have to join the group. This action allowthe new group member to retrieve the node name database from any other group memeber.

N.B. Executing some commands you can see the following message, please ignore it:Redefining sub ConnectionManager::GetConnectionPort at /alcatel/Kernel/lib/lib_perl/Remotizer.pm line 695

3.4.2.1.1 Add the New Menber to the Group

To add a new host to the group as member you have to:– Log in as root a system already group member.– Start “scNMmng”.– Enter 2 (ADD = add a new node).– On “ADD – Management option” window enter “2” to choose “add remote node (member)”.– Enter the “hostname” and “IP Address” of the new host on demand.– Wait the end of program execution.Now the new host is known by all group member systems.

3.4.2.1.2 New Member Joins the Group

To complet the action, you have to execute the add also from the joining host. To do it you have to:– Log in as root the new incoming host.– Start “scNMmng”.– Enter 2 (ADD = add a new node).– On “ADD – Management option” window enter “1” to choose “add current node”.– Enter the “hostname” and “IP Address” of a group member node on demand.– Wait the end of program execution.Now the new node is member of the group.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

18

03

/3AL 88893 CAAA

112

112

3.4.2.2 Add a New External Node

You add a new external node to the group when the adding node is NOT a TMN system, it can be a printeror any other kind of machine not running Alcatel TMN system based on OS–Kernel. This case you havejust to perform the add on any group member node. The information will be automatically distributed tothe entire group.

3.4.2.3 Add a Cluster Node

A specific area has been defined to allow the definition of the Virtual Hostname requested by MC Service-Guard configurations. In fact this requires a special management, the host have to be authorized to swapmessages with the other group members, but is must be not included in the voters for reaching the quorum.

3.4.3 3 – REMOVE

This menu choice allows to remove any node form the database. This command has been designed tobe able to remove the system also if it is not reachable through the network.

3.4.3.1 Remove Entry for the Current Node

There are two way to remove entries related to the current node: one for the primary or physical hostnameand another for the virtual hostname for cluster configurations. Choose the option related to the action youwant to execute from the menu. The entry is removed from all group members databases.

3.4.3.2 Remove Entry for Other Group Member

You can also remove the entry for other group members, for both primary and virtual hostname. Choosethe option related to the action you want to execute from the menu. The entry will be removed from all groupmembers databases.

3.4.3.3 Remove Entry for External Nodes.

A specific remove choice is foreseen also for the external nodes. Choose the option related to the actionyou want to execute from the menu. The entry will be removed from all group members databases.

3.4.4 4 – PUT

A specific menu option is foreseen for update the node name database of a remote group member. Thiscan be useful in case to align a node database.

3.4.5 5 – LIST

List option allow to read the database contents of the current or any other group member node.

3.4.6 6 – TOTALIGN & 7 – ACTALIGN

This two option allows to align all the group member nodes to the specified one or a specific one to anothergroup memeber.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

19

03

/3AL 88893 CAAA

112

112

3.4.7 8 – GRPOPEN, 9 – GRPIMPORT & 10 – GRPMERGE

Functions to enable the comunication and, eventually, the merge between two different hosts groups con-figured on the same network. To perform this, is necessary to execute two different steps in the followingsequence:

1 ) First of all, you have to enable on a host belonging to a hosts group, the remote access froma specific host belonging to other hosts group (GRPOPEN).

2 ) Then, you can choose to include the remote group description on the current group hosts(GRPIMPORT) or merge the current and remote hosts groups (GRPMERGE) obtaining as finalresult a single group containing the description of the hosts of both indicated groups.

3.4.7.1 GRPOPEN

To enable the access on the current host, belong to a network hosts group, from a remote host (and ONLYfrom it) belong to other network hosts group you have to:– Log in as root the group member you want to enable to remote group comunication.– Start “scNMmng”.– Enter 8 (GRPOPEN = open the current group).– Enter the “hostname” and “IP Address” of the remote host you want to link.– Wait the end of program execution.Now the two groups to which belong the current and the remote hosts can comunicate each other.

3.4.7.2 GRPIMPORT

N.B. You can to activate this function ONLY from the remote host indicated during the GRPOPENoperation previously executed.

To configure on the current node (and on each node belonging to the same nodes group) the nodes be-longing to a remote nodes group you have to:– Log in as root the group member you want to configure the hosts of the remote group.– Start “scNMmng”.– Enter 9 (GRPIMPORT = import a remote group).– Enter the “hostname” and “IP Address” of the remote host belonging to the group you want to link.

N.B. Must be the same of the node where you executed the GRPOPEN.– Wait the end of program execution.Now the configuration of each host member of local group include the description of all hosts member ofthe remote group.

3.4.7.3 GRPMERGE

N.B. You can to activate this function ONLY from the remote host indicated during the GRPOPENoperation previously executed.

To merge the hosts members of two different groups in a single group you have to:– Log in as root the host member of the group you want to merge with the remote group.– Start “scNMmng”.– Enter 10 (GRPMERGE = merge two groups).– Enter the “hostname” and “IP Address” of the remote host belonging to the group you want to merge.

N.B. Must be the same of the node where you executed the GRPOPEN.– Wait the end of program execution.Now all the hosts members of the two groups has been merged in a singre group.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

20

03

/3AL 88893 CAAA

112

112

3.4.8 11 – CHIPADDR

This paragraph shows how to change the IP address of a system configured with OS–Conf Node Manage-ment script.

There are two different situations:

1 ) The IP address have to be change is related to a group member, that means you have to changean IP address configuration, and inform all the other network nodes about the change.

2 ) The IP address have to be change is related to an external system, and you have just to informall network nodes about this change.

3.4.8.1 Change Member Node IP Address

To better understand how to proceed it is advisable have clear in mind some concepts of OS–Conf networkmanagement:

– To be able to communicate each other using the hostname alias, two machines have to register thecorrect relationship between hostname and IP address in /etc/hosts file.

– Changing the IP address on a node the communication can be lost.

– The hostname/IP address relationship has to be changed on the entire network.

– The new IP address have to be defined in agreement with IP addressing plan of the local area networkwhere the system have to operate. NO IP ADDRESS DUPLICATION IS ALLOWED.

When changing the IP address also the IP Network or sub–network (RFC 1878) ischanged, you have to change also any related routing information.

Do not run the scNMmng procedure on the machine where the IP address has to bechanged by using remote connection or X Motif interface, because the connection canbe lost and the CDE can gets blocked.

Because of these reasons we decide to split the change IP address in two actions:

1 ) The hostname/IP address relationship change on all network nodes but the one that the IP ad-dress is defined on.

2 ) The IP address change on the node where the IP address is defined on.

The first action have to be performed on any group member node different that ome where the IP addressis defined.The the second one on node where the IP address have to be really changed.

Is important to preform the to action in this order. The communication can not be establish again be-fore both of these steps will be not completed.

Before proceed is better to verify that the communication among the machine with thenew IP address and the remaining group members are established again.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

21

03

/3AL 88893 CAAA

112

112

3.4.8.2 Change External Node IP Address

The external node IP address change does not require any modification on the LAN card configurationof any network node. That means this action can be done in one shot over all the nodes.In any case you have to synchronize yourself with who is in charge to perform the IP address change onthe external system, in order to reduce the down time between that external system and the node belong-ing to the group.

3.4.8.3 Change Node IP address to the Other Members

This activity allows to change the relationship between an IP address on all the group member nodes atonce. The detailed procedure is:

N.B. In the following sequence to form the hypothesis to change from hostb node of example in para-graph. 3.3 , the IP address of hostc node from 192.202.21.8 to 192.202.21.99.

a ) Login a group member node as root user (hostb of example in paragraph. 3.3).

b ) Run the “scNMmng” script (see paragraph 3.4 at page 16) then enter ”11“ [Enter] to change the IPaddress of a node.

c ) On the display will be appear the Change IP Addr. Menu:–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Network Management Nodes (V2.3.1) ––

CHANGE–IP – Management options: 1 – change the IP addr. on current node 2 – change the IP addr. on remote node (member)

[0] – Main menu Enter management option [0..2] :

Enter “2” and [Enter] . The procedure ask you the following questions:Please insert the HOSTNAME for remote host : <hostname> [Enter]Please insert the OLD IP ADDR. for remote host : <cur_IP_addr> [Enter]Please insert the NEW IP ADDR. for remote host : <new_IP_addr> [Enter]Please insert the NETWORK ID for remote host : <lan_ID> [Enter]

Where <hostname>, <cur_IP_addr> (displayed automatically) and <new_IP_addr> are the remotehostname, the current and the new IP address of the node you want to modify (respectively hostc,192.202.21.8 and 192.202.21.99 in the example). <lan_ID> is the LAN identification number (0=lan0,1=lan1, ...).

d ) The procedure ask you to confirm the current execution:Do you confirm the execution [Y/N – def.=Y]? :

Enter “Y” and [Enter] to proceed or “N” and [Enter] to go back to main menu.

e ) If you continue the operation, the procedure will start a update on all the group member nodes. Waitthe end of the activity as requested by:

WAIT THE END OF THE ACTIVITY (DO NOT PRESS ANY KEY !!).

f ) The execution will be confirmed by the message:** MESSAGE: IP ad. of ”<hostname>” (<cur_IP_addr>) changed in <new_IP_addr>.Press [Enter] to continue.

The IP address of indicated node has to be changed. Press [Enter] to go back to main menu, thenpress [Enter] or “0” and [Enter] to exit.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

22

03

/3AL 88893 CAAA

112

112

3.4.8.4 Change Node IP address on Local Member

The IP address change can have influence on the application behavior. In fact any open connection canfault down, because IP address change need to shutdown the LAN services. For the same reason it isforbidden perform such kind of action using network connection (such as telnet connection and Xterminalemulation GoGlobal–UX) involving the LAN interface subject to change. Moreover, if you are changingthe IP address on a hp9000 workstation, you must exit any CDE interface and login in console mode (blackscreen).

Because the tool is not able to identify when started from a network opened shell, no check canbe done to prevent the execution from a wrong source.


N.B. The sequence completes the hostc IP address chence from 192.202.21.8 to 192.202.21.99.

a ) Login changing group member node as root user (hostc of example in paragraph. 3.3).

b ) Run the “scNMmng” script (see paragraph 3.4 at page 16) then enter ”11“ [Enter] to change the IPaddress of a node.

c ) On the display will be appear the Change IP Addr. Menu:–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Network Management Nodes (V2.3.1) ––

CHANGE–IP – Management options:

1 – change the IP addr. on current node 2 – change the IP addr. on remote node (member)

[0] – Main menu Enter management option [0..2] :

Enter “1” and [Enter] . The procedure ask you the following questions:Please insert the OLD IP ADDR. for local host : <cur_IP_addr> [Enter]Please insert the NEW IP ADDR. for local host : <new_IP_addr> [Enter]Please insert the NETWORK ID for local host : <lan_ID> [Enter]

Where <cur_IP_addr> (displayed automatically) and <new_IP_addr> are the current and the newIP address of the node (192.202.21.8 and 192.202.21.99 in the example). <lan_ID> is the LAN identi-fication number (0=lan0, 1=lan1, ...).





N.B. The activity may take a few minutes (a Kernel serivces re–configuration is required). DONOT ABORT THE PROGRAM !!

f ) The execution will be confirmed by the message:** MESSAGE: IP ad. of ”<hostname>” (<cur_IP_addr>) changed in <new_IP_addr>.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

23

03

/3AL 88893 CAAA

112

112


3.4.9 12 – CHHOSTNAME

This paragraph shows how to change the node name of a system configured with OS–Conf Node Manage-ment script.

There are two different situations:

1 ) The node name have to be change is related to a group member, that means you have to changean node name configuration, and inform all the other network nodes about the change.

2 ) The node name have to be change is related to an external system, and you have just to informall network nodes about this change.

3.4.9.1 Change Member Node Name

To better understand how to proceed it is advisable have clear in mind some concepts of OS–Conf networkmanagement:

– To be able to communicate each other using the hostname alias, two machines have to register thecorrect relationship between hostname and IP address in /etc/hosts file.

– Changing the node name on a mode the communication can be lost.

– The hostname/IP address relationship has to be changed on the entire network.

– OS–Conf has to guarantee the execution of the action declared succeeded.

Because of these reasons we decide to split the change node name in two actions:

1 ) The hostname/IP address relationship change on all the other network nodes.

2 ) The node name change on the local node.

The first action have to be performed on any other one it the configuration, the the second one on nodewhere the node name have to be really changed.

Is important to preform the to action in this order. The communication can not be establish again be-fore both of these steps will be not completed.

3.4.9.2 Change External Node Name

The external node node name change does not require any modification on the LAN card configurationof any network node. That means this action can be done in one shot over all the nodes.

In any case you have to synchronize yourself with who is in charge to perform the node name change onthe external system, in order to reduce the down time between that external system and the node belong-ing to the group.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

24

03

/3AL 88893 CAAA

112

112

3.4.9.3 Change Node Name to the Other Members

This activity allows to change the relationship among a node name on all the group member nodes at once.


N.B. In the following sequence to form the hypothesis to change from hostb node of example in para-graph. 3.3, the node name of hostc node from hostc to hostx.

a ) Login a group member node as root user (hostb of example in paragraph. 3.3).

b ) Run the “scNMmng” script (see paragraph 3.4 at page 16) then enter ”12“ [Enter] to change the nameof a node.

c ) On the display will be appear the Change Hostname Menu:

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Network Management Nodes (V2.3.1) ––


1 – change the hostname on current node 2 – change the hostname on remote node (member)

[0] – Main menu


Enter “2” and [Enter] . The procedure ask you the following questions:Please insert the OLD HOSTNAME for remote host : <hostname> [Enter]Please insert the IP ADDR. for remote host : <IP_addr> [Enter]Please insert the NEW HOSTNAME for local host : <new_hostname> [Enter]

Where <hostname>, <IP_addr> (displayed automatically) and <new_hostname> are the currentname, the IP address and the new name of the remote node you want to modify (respectively hostc,192.202.21.8 and hostx in the example).





f ) The execution will be confirmed by the message:** MESSAGE: nodename ”<hostname>” changed in “<new_hostname>”.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

25

03

/3AL 88893 CAAA

112

112

3.4.9.4 Change Node Name on Local Member

After the “Change Nodename” activity execution on other group member nodes, you have to execute thesame action on the node you want to modify.


N.B. The sequence completes the hostc name chence from hostc to hostx.

a ) Login a group member node as root user (hostc of example in paragraph. 3.3).

b ) Run the “scNMmng” script (see paragraph 3.4 at page 16) then enter ”12“ [Enter] to change the nameof a node.

c ) On the display will be appear the Change Hostname Menu:

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Network Management Nodes (V2.3.1) ––


1 – change the hostname on current node 2 – change the hostname on remote node (member)

[0] – Main menu


Enter “1” and [Enter] . The procedure ask you the following questions:Please insert the NEW HOSTNAME for local host : <new_hostname> [Enter]

Where <new_hostname> is new name of the remote node you want to modify (hostx in the example).





N.B. The activity may take a few minutes (a Kernel serivces re–configuration is required). DONOT ABORT THE PROGRAM !!

f ) The execution will be confirmed by the message:** MESSAGE: nodename ”<hostname>” changed in “<new_hostname>”.** WARNING: reboot your system immediately after this operation !!



N.B. After the node name changing, a system reboot is required !!

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

26

03

/3AL 88893 CAAA

112

112

3.4.10 13– CHNETMASK

N.B. This function manage each network interface configured.

To change the subnetwork mask of a group member host you have to:– Log in as root the host member where you want to change the subnetwork mask.– Start “scNMmng”.– Enter 13 (CHNETMASK = change netmask).– Enter the “new subnetwork mask” and “LAN identification number” (0=lan0, 1=lan1, ...).– Wait the end of program execution.At the end of this operation, on current host the new subnetwork mask is actvated on line automatically.

3.4.11 14 – CHGATEWAY

N.B. This function manage each network interface configured.

To change the current gateway IP address and hostname of a group member host you have to:– Log in as root the host member where you want to change the gateway configuration.– Start “scNMmng”.– Enter 14 (CHGATEWAY = change gateway).– Enter the following informations:

• “current gateway IP address” have to be replaced. If you want to modify the default gateway,you have to indicate the key “default”.

• “new gateway hostname” and “new gateway IP address”.– Wait the end of program execution.At the end of this operation, on current host the new the new gateway IP address and hostname are act-vated on line automatically.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

27

03

/3AL 88893 CAAA

112

112

3.4.12 15 – DNSADD

To allow to add a new server to the current Distributor Names Server (DNS) configuration of a group mem-ber host. If the DNS is not already configured, it will be initialized. To perform this you have to:– Log in as root the host member where you want to define or update the DNS configuration.– Start “scNMmng”.– Enter 15 (DNSADD = add the DNS).– Enter the following informations:

• “new DNS server hostname” .• “new DNS server IP address”.• “new DNS local domain name” (required only if the DNS is not yet configured on the current

host).– Wait the end of program execution.Now, on the current member host the DNS configuration is updated.

3.4.13 16 – DNSCHANGE

To allow to modify the current Distributor Names Server (DNS) configuration of a group member host. It’spossible to:

a ) replace a Distributor Names Server (DNS) nameserver currently configured with a new one.b ) replace the current local domain name with a new one.c ) perform an update of the search domain list.

To perform this you have to:– Log in as root the host member where you want to modify the current DNS configuration.– Start “scNMmng”.– Enter 16 (DNSCHANGE = change DNS).– Enter the following informations:

• current DNS nameserver name (optional – required only if you want to replace a DNS names-erver currently configured).

• new DNS nameserver name (optional – required only if you want to replace a DNS nameservercurrently configured).

• new DNS nameserver IP addr (optional – required only if you want to replace a DNS nameservercurrently configured).

• new DNS local domain name (optional – if is not indicated, the current local domain name willbe maintained.

• search list for host–name lookup (optional – if is not indicated, the current search domain listwill be maintained.

– Wait the end of program execution.Now, on the current member host the DNS configuration is modifyed.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

28

03

/3AL 88893 CAAA

112

112

3.4.14 17 – DNSREMOVE

Remove a server from the current Distributor Names Server (DNS) configuration of a group member host.If the DNS Server indicated is the last configured on the local node, the DNS will be unconfigured:– Log in as root the host member where you want to remove the DNS nameserver.– Start “scNMmng”.– Enter 17 (DNSREMOVE = remove from DNS).– Enter the “DNS nameserver name“ and “DNS nameserver IP addr” of the server you want to remove.– Wait the end of program execution.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

29

03

/3AL 88893 CAAA

112

112

4 BACKUP AND RESTORE

The OS–Conf includes a backup/restore function. This function allows to make a security archive tape setof the entire system, or a specified volume group, reducing the down time of the system where it is possible.

The backup function can be executed in two ways:

– Full backup of the entire system.

– Single volume group back.

Both of them allow the on–line execution, and are integrated with the other OS–Conf feature such as diskmirror management.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

30

03

/3AL 88893 CAAA

112

112

4.1 Full disks backup/restore

The target of the procedure is: provide an easy tool to allow the backup and restore of the complete diskscontents (including the disk partitioning), to allow the system recovery in case of disk failure or data corrup-tion that does not allow the HP–UX to boot again from disk.Basically the procedure use three HP–UX tools:

1 ) fbackup – Backup tool included in the HP–UX 11.11 Core2 ) frecover – Recover tool included in the HP–UX 11.11 Core3 ) Ignite UX� – Add on HP tool for installation and recovery

The tools reference versions are:HP–UX 11i 11.11Ignite UX� B.3.6.82 for HP–UX 11.11

This means the scbackup behavior is not guarantee with different version.

4.1.1 Full Backup Strategy

The system backup is always done using two tape cassette sets:

a ) The fist tape set is the Ignite Recovery Tape (IRT). It is created on–line by Ignite UX with a reducedHP–UX� and allows the boot from tape. Usually the IRT is done using just one 4 Gbyte tape.The contents of IRT depends also by the Logical Volume Management (LVM) configuration, it thePhysical Volume Group (PVG) are defined, only the disk beloging to PVG0 will be stored in the IRT,this is done this way because Ignite does not manage mirror disk nor PVG. This approach has beenimplemented to be able to build again the same configuration in the restore.

b ) The second tape set is created by “fbackup” tool with the entire disk contents. This activity can becarried out on–line or off–line depending by the system configuration and status. These are the condi-tions to be able to perform the on–line full backup:

1 ) If entire file system is mirrored.2 ) If there are no stale phisycal extent.3 ) If there is no Virtual Array in configuration.

This tape set can be require more than one tape.

N.B. If you have both DAT and DLT tape device, it is allowed to create the two tape sets using differenttype of tape cassettes, such as DAT tape for IRT and DLT for fbackup.But it is NOT allowed to mix different type tape cassettes in the same tape set.

The procedure manages both volume group configuration provided for Alcatel TNM Applications:

– Single Volume GroupMultiple Volume Group

The Single Volume Group configuration has all disks in configuration defined in the same HP Logical Vol-ume Manager (LVM) volume group (VG), where there are also the HP–UX system partitions.The Multiple Volume Group configuration foreseen a different VG for each disk (vg01, vg02, vg03, etc.)with the exception of the Mirror UX configuration where each VG must contains two disks.Within the Alcatel TNM environment it is RECOMMENDED to use this tool in together with the Alcatel Ap-plication Backup feature, because often there is application data on different systems that have to be con-sistent each other.

N.B. The full backup usage is forbidden with 1359HA OS–Cluster environment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

31

03

/3AL 88893 CAAA

112

112

4.2 Single Volume Group Backup

The single volume group backup has been introduced to allow the backup when there are 1359HA OS–Cluster System configuration.

The 1359HA OS–Cluster specific volume group management does not allow to perform the full backupin the usual way, because them are shared between two systems, and their Logical Volume Manager(LVM) configuration must be managed by 1359HA OS–Cluster scripts.

Single volume group backup feature is also due to the Virtual Array (VA7110) backup method, in fact thereis a specific feature of VA7110 to make an on–line copy of any Logical Unit (LUN), this mechanism allowthe on–line backup of any information stored with the VA7110, but require an extra space on device equalto the amount of space that have to be backup at once.

Basically the procedure uses the following HP–UX tools:

1 ) fbackup – Backup tool included in the HP–UX 11.11 Core2 ) frecover – Recover tool included in the HP–UX 11.11 Core3 ) Ignite UX� – Add on HP tool for installation and recovery4 ) CommandView SDM� – Virtual Array Command

The tools reference versions are:

HP–UX 11i 11.11Ignite UX� B.3.6.82 for HP–UX 11.11CommandView SDM V1.06.00

This means the scbackup behavior is not guarantee with different version.

4.2.1 Single Volume Group Backup Strategy

The behavior of the single volume group backup is more flexible, but more complex than the full backupone. Within the single VG backup it is possible to distinguish two different VG types:

1 ) hp–ux� system volume group (vg00).

2 ) Data volume group (different than vg00)

The backup of the system volume group (vg00) is perform with the full backup approach, it is done withtwo tapes (IRT and fbackup) to be able to rebuitd a minimum hp–ux� system and the data stored inside.Instead the data volume group backup is related only the data.As result of this policy is the single volume group backup require a number of tapes equal to the numberof volume group plus one, and all of them have to be properly labeled to prevent misusage.

N.B. The manual Single Volume Group Backup usage is forbidden. It must be integrated with-in 1359HA OS–Cluster Backup feature.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

32

03

/3AL 88893 CAAA

112

112

4.3 Restrictions

4.3.1 Ignite Recovery tape restrictions

The Ignite Recovery Tape (IRT) has some restrictions with using the DLT tape driver.– DLT MUST BE attached to HP 9000 Enterprise servers via Fast–Wide Differential interface cards.– DLT boot WILL NOT work when attached via single–ended SCSI.– DLT boot IS NOT supported for systems that use NIO Fast–Wide Differential SCSI cards (Part num-

ber 28696A).

The matrix below explains systems (by class) along with the bus types required for DLT to be recognizedas a bootable media device.

Table 1. Bus types required for DLT to be recognized as a bootable media

CLASSBUS SCSI Interface Card DLT boot support

?Notes

K–ClassHSCNIO

A2969A FWDA28655A SE, A28696A FWD

yesno

see 1 ) and 2 )

D–ClassHSCCoreEISA

A4107A FWD yesnono

see 2 )

T–ClassHSCNIO

A3644A FWDA28655A SE

nono

N–Class PCI FWD yes

L–Class PCI FWD yes

V–Class PCI A4800A FWD yes see 4 )

E–Class NIO A28655A SE, A28696A FWD no see 3 )

G–Class NIO A28655A SE, A28696A FWD no see 3 )

H–Class NIO A28655A SE, A28696A FWD no see 3 )

I–Class NIO A28655A SE, A28696A FWD no see 3 )

Notes:

1 ) This class system has two internal bus types, HSC and NIO. DLT is only bootable from the HSCbus.

2 ) The HSC and GSC busses are the same busses. These terms are used interchangeably.

3 ) NIO and HP–PB refer to the same bus.

4 ) IPR (Independent Peripheral Release). A firmware upgrade (at least 4.3, product numberB6044AA) is required to enable tape boot for the V–Class. The release date for firmware up-grade version 4.3 is September 1998. Contact your HP representative about required firmwareupgrades.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

33

03

/3AL 88893 CAAA

112

112

4.3.2 1359HA OS Cluster Support

The OS Cluster environment is supported only with Single Volume Group in conjunction with 1359HA OS–Cluster backup feature.

4.3.3 Mirror Disk configuration rebuild

The restore procedure after restoring the data it will inform the user if the system was mirrored at the back-up time, the mirror rebuild is not managed directly by the restore procedure, but it must activated separate-ly.

For systems protected with Mirror/Disk UX, it is possible to proceed with the full online disk backup by usingthe “scbackup” script, after the disk restore via “screstore” script the “scmirrorfs“ script can be invoked torebuild the mirror configuration, this script will require to specify the mirror disks to be used (refer to appen-dix 4.5.3 at page 52).

4.3.4 Restriction on Console

The fbackup is executed in single user mode during the HP–UX boot phase, but it is VERY IMPORTANTto know that switching off the console terminal or disconnecting the Web console during the fbackupexecution, the fbackup itself will be interrupt, and the backup will be not completed.

4.3.5 Required disk space

The Ignite UX tool require at least 32Mbyte free in the file system where /var directory is located.

4.3.6 Compatibility

The ’scbackup–screstore’ version 2.0 in not compatible with the previous version of the Alcatelbackup–restore software, so the tapes produced with old versions cannot be managed by the new one.

Pay attention to label correctly the new tapes and to keep them separated from the previous.

4.3.7 Restriction on Backup

The system you want to backup may have volume groups not active or logical volumes not mounted; thesewill not be managed by the procedure and you will be informed by warning messages.

Moreover:

– is strictly recommended do NOT perform the backup of file systems mounted using a pathcontaining symbolic link. In fact, the backup of a file system of this type will generate a recoveryarchive error during the restore procedure (see paragraph 4.6.2 at page 61).

– pay particular attention to perform a full user disk backup in a Cluster environment configuredwith a Virtual Array. It could be generate a backup error (see paragraph 4.6.3 at page 63).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

34

03

/3AL 88893 CAAA

112

112

4.4 FULL BACKUP

This chapter shows how to perform the backup of the entire disk structure and contents by using thescbackup procedure.

The script is design to be executed in following the phases showed below:

a ) Create the Ignite recovery tape (IRT).

b ) Perform backup

On line:

1 ) Split the mirror disk, creating a off–line copy of the entire system.2 ) Perform the backup of the off line copy3 ) Merge back the off–line copy in the mirror disk configuration.

Off line:

1 ) Prepare HP–UX system to execute standard backup at HP–UX� Run Level 2.2 ) Perform the backup during the HP–UX system reboot.3 ) Reboot the system to restore it in service.

4.4.1 Start the “scbackup” script

To activate the scbackup script and execute the backup of your environment you have to proceed as follow:

a ) Login as root.

b ) Insert the tape cassette into the tape device.

c ) Start the procedure by entering:

..,sys,root # scbackup [Enter]

The scriot foreseen a timeout on the tape cassete request, the default value is 60 minutes, if you wantto have a different timeout period or inibit any timeout you have to use the “–t“ option.:

....sys,root # scbackup –t 180 To increase the timeout to three hours.

...,sys,root # scbackup –t 0 To disable the timeout.

d ) The script will ask you to enter the HP–UX device file for the IRT to be able to identify the tape driveryou want to use by issuing the request:

Enter tape device for Ignite <default=<tape_device>>:

Enter the HP–UX file associated to the tape device (i.e.: /dev/rmt/0m) you want to use for the IRT tapeset and press [Enter], or just press [Enter] to select the shown file (<tape_device>).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

35

03

/3AL 88893 CAAA

112

112

4.4.2 Create the IRT

Now we get into the IRT creation phase. The script issues the following message to ask you to insert atape cassette into the tape driver.

Please load Tape with label Ignite on device: </dev/rmt/0m>and press Enter when READY

You have now to insert an unprotected tape cassette waiting until the drive light stops blinking.

The tape cassette MUST BE NOT WRITE–PROTECT !

When the device light will be stable on, press [Enter] key to start the activities on the tape.

The IRT creation can take up to 40 minutes. (20 minutes with a HP9000 R380 Server with a DDS2 tapedriver).

The output of the execution will shown on the terminal.

Any error detected will abort the execution.

When the IRT will be completed without errors, the following message will be shown:

************************************************** Remove Tape media and recommended label is: hosta – Ignite Bootable – 01–Dec–2003 14:04

Please label the tape as suggested by the message.

ATTENTION: The root password saved into IRT has to be used at the recovery time. Donot forget it!

4.4.2.1 IRT Integration Data

To have a better view of the backuped system configuration it is required to printout some information andattach them to IRT.

The required information are issued by the following command:• ...,sys,root # vgdisplay –v [Enter]• ...,sys,root # scextendfs –i [Enter]

Print the output of these two commands and store it with the IRT, them can be useful in case of disk failure.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

36

03

/3AL 88893 CAAA

112

112

4.4.3 Backup the entire disks contents

When the IRT creation is completed, the scbackup goes to the next query require entering the HP–UXdevice file for the fbackup, by issuing the message:

Enter tape device for Fbackup <default=<tape_device>>:

Enter the HP–UX file associated to the tape device (i.e.: /dev/rmt/0m) you want to use for backup theentire disk contents and press [Enter], or just press [Enter] to select the shown file (<tape_device>).

After this question it determinate if there are the condition to perform the on–line backup.

4.4.3.1 Online full backup

This procedure checks if the mirror software is installed on the system, in case of positive result it evaluatesif a full mirrored/stable disks configuration is present and activates the split of the logical volumes to pre-pare the data for the online backup from the mirrored disks.

************************************************** Verificaton of FULL MIRROR

Checking correct configuration of Logical Volumes mirror ...

In case of compatible system configuration, It is suggested to stop the Alcatel TNM applications beforeto continue as reported at follows:

During the splitting phase, in order to preserve the data integrity, it is required to shut-down of the Alcatel TNM applications.

MIRROR verificaton End Successfully

***************************************************************************** To preserve data integrity and avoid problems you should: STOP ALL APPLICATIONS before start backup. *****************************************************************************

***************************************************************************** NOTE: If you need to stop anything, do it before answer ’YES’ to the next question. *****************************************************************************

Do you want continue with backup operation (y|n) ? : y

When you answer “y” the logical volumes split will be executed.

If the split succeeds the following message will inform you to reactivate the Alcatel TMN applications andthe full backup will be started.

***************************************************************************** ATTENTION: NOW you can RESTART APPLICATIONS !!! *****************************************************************************

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

37

03

/3AL 88893 CAAA

112

112

It is necessary to attend the fbackup execution, because of it can ask for more tape cassettes, and whenit requires a new cassette you have to remove the current tape and insert a new unprotected one. Thefbackup by default will wait up to 1 hour for the new tape cassette after issuing the message:

Please MOUNT TAPE Volume <x>

where <x> means the tape cassette number.

If the cassette will be not replaced in 1 hour or you insert a wrong tape the fbackup will fail.

N.B. The default timeout can be changed using the –t option on scbackup commad.

N.B. Fbackup DOES NOT CHECK if you are inserting the IRT one, in this case the IRT will be de-stroyed.

If everything goes well you will recevive the following output:

************************************************** SPLIT procedure

Start split operation for Logical Volume /dev/vg00/lvol3

Check FS on splitted Logical Volume

Mount FS on backup directory /sconlinebackup

...

SPLIT End Successfully

***************************************************************************** ATTENTION: NOW you can RESTART APPLICATIONS !!! *****************************************************************************

************************************************** ONLINE BACKUP process

************************************************** Preparation Tape media for BACKUP Fbackup tape devices /SCINSTALL/data/backup/fbackup_tape Backup Tape check : Please MOUNT TAPE Volume 1

01–Dec–2003 14:28 Execute Backup : Start Backup ... Execute Backup : End Successfully

***************************************************************************** DATA ARE SUCCESSFULLY BACKUPED *****************************************************************************

************************************************** Remove Tape media and recommended label is: hosta – Fbackup Volume x of n 01–Dec–2003 14:26 – Content: Full backup

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

38

03

/3AL 88893 CAAA

112

112

After the full online backup the backup logical volumes will be reduced.

************************************************** MERGE–DELETE process

Start MERGE–DELETE process activated on backup Logical VolumesThis operation takes a while, please wait ...

MERGE–DELETE End Successfully

***************************************************************************** ONLINE BACKUP End Successfully *****************************************************************************

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

39

03

/3AL 88893 CAAA

112

112

4.4.3.1.1 Online Full Backup Error Management

If problems occour during execution of sconlinebackup, the disks configuration will be automatically re-stored. In case of errors during the logical volumes split operation, the user can decide to continue withstandard backup or to stop the procedure in order to analyse the problem, make the corrections and runagain the command sconlinebackup (refer to paragraph 4.4.3.1.1.4 for an example).

The sconlinebackup procedure can also run alone just if a new IRT is not required. In this case it will showthe following output:

************************************************** sconlinebackup (Backup–Restore Ver. 2.0)

************************************************** Environment verification

***************************************************************************** ATTENTION: ’sconlinebackup’ procedure can be invoked directly just if your SYSTEM IS NOT CHANGED since the last creation of the IRT (Ignite Recovery Tape). *****************************************************************************

***************************************************************************** If you have doubt or if you need to create a new IRT, answer ’NO’ to the next question and use the ’scbackup’ command instead of ’sconlinebackup’. *****************************************************************************

Do you want continue with backup operation (y|n) ? : y

***************************************************************************** NOTE: You choose to proceed with backup. The last produced IRT MUST BE VALID. *****************************************************************************

If the user decides to proceed, the script will work as previously described in this chapter.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

40

03

/3AL 88893 CAAA

112

112

4.4.3.1.1.1 Full Mirror faults

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

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

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

WARNING: Logical Volume /dev/vg00/lvol13 not mirrored.

ALL Significant Logical Volumes must be mirrored.

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

– logical volumes have the “stale” status, a message like the following will be shown:

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

WARNING: Logical Volume /dev/vg00/lvol13 has status available/stale

This indicates problems in mirroring synchronization.

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

The procedure skips the full online backup when it finds the first logical volume who doesn’t meet the re-quirements and before continue with standard backup it will show the message:

***************************************************************************** WARNING: MIRROR verificaton End with warnings *****************************************************************************

***************************************************************************** NOTE: ONLINE BACKUP NOT SUPPORTED by this system *****************************************************************************

4.4.3.1.1.2 System crash

As you can realize this process is quite critical because in case of crash during the online backup thereis the necessity to recover the original disks’ configuration. For this purpose an automatic recover proce-dure will be activated at the system startup in case of failure (sconlinebackup_recover).

4.4.3.1.1.3 Logs

There are three log files where you can check in case of errors to identify the reason of the fault:

– /var/adm/syslog/sconlinebackup.log records information related to the SPLIT phase.

– /var/adm/syslog/sconlinebackup_recover.log info about the MERGE_DELETE/RECOVER phase.

– /var/adm/syslog/fbackup.log keeps the full online FBACKUP information.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

41

03

/3AL 88893 CAAA

112

112

4.4.3.1.1.4 Split problems

Problems should appear during the splitting operation, if the applications have not stopped, because a filesystem check is activated on the splitted logical volume and it could find inconsistent state and uncorrect-able errors. In this condition the backup procedure ends as reported at follows:

...Start split operation for Logical Volume /dev/vg00/lvol7

Check FS on splitted Logical Volume

***************************************************************************** ERROR: exit status 36 for command ’fsck –F vxfs /dev/vg00/lvol7backup’ *****************************************************************************

***************************************************************************** ATTENTION: Recover process activated due to ERROR. Error during data copy phase see: /var/adm/syslog/sconlinebackup.log *****************************************************************************

************************************************** RECOVER process

RECOVER process activated on backup Logical VolumesThis operation takes a while, please wait ...

RECOVER End Successfully

***************************************************************************** ERROR: during data COPY phase.*****************************************************************************

Do you want continue with standard backup (y|n) ? : n

***************************************************************************** ERROR: during data COPY phase See ONLINE backup log: /var/adm/syslog/sconlinebackup.log After correction run again procedure ’sconlinebackup’.*****************************************************************************

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

42

03

/3AL 88893 CAAA

112

112

4.4.3.1.1.5 Timeout expiration

If the user forget to mount the tape and the mount timeout expires, the process terminates with the mes-sage at follows:

************************************************** ONLINE BACKUP process

************************************************** Preparation Tape media for BACKUP Fbackup tape devices /SCINSTALL/data/backup/fbackup_tape Execute Backup : ERROR: timeout expired for Mount Tape

***************************************************************************** ERROR: DATA ARE NOT CORRECTLY BACKUPED *****************************************************************************02–Dec–2003 09:40 ERROR: timeout expired and Tape media was not mounted

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

************************************************** REDUCE process

Start REDUCE process on backup Logical VolumesThis operation takes a while, please wait ...

REDUCE End Successfully

***************************************************************************** ERROR: Online Backup ends with errors. See FBACKUP log: /var/adm/syslog/fbackup.log After correction run again procedure ’sconlinebackup’.*****************************************************************************

The user shuold mount the tape and run again the sconlinebackup command.

4.4.3.1.2 Merge–Delete problems

Normally the merge of the logical volumes works fine, but if it fails the disks mirroring will be faulty, to solvethis kind of problem you must check the log file for errors and run manually the sconlinebackup_mergecommand.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

43

03

/3AL 88893 CAAA

112

112

4.4.3.2 Standard Full backup

Proceding with the standard full backup, in order to guarantee the contents of the files it is required to shut-down of the Alcatel TNM applications and reboot the HP–UX system. Because of this it is necessary tocarefully schedule this activity.

The time required full backup depends by:

– Amount of the disk space used by files.

– Type of tape device.

– I/0 system.

The scbackup require to perform the shutdown–reboot immediately.

The procedure shows the messages at follows and it asks if the system is ready for the shutdown, if youanswer with “y” the system will reboot, if you answer “n” the backup will be aborted.

***************************************************************************** ATTENTION: you can continue with standard system backup, but this requires the system SHUTDOWN–REBOOT. *****************************************************************************

***************************************************************************** Applications is better already stopped before start shutdown, do it before answer ’YES’ at the next question. *****************************************************************************

***************************************************************************** NOTE: If you answer ’NO’ at the question the backup will be aborted. *****************************************************************************

Is system READY for execute standard backup with SHUTDOWN & REBOOT (y|n) ? :

If you decide to answer “y”, it is better to shutdown the Alcatel Application, also if the procedure will stopthe system with “shutdown –r” command.

If you decide to proceed the procedure asks to insert an unprotected tape cassette in the tape driver speci-fied for the full backup issuing the following message:

************************************************** Preparation Tape media for FBACKUP tool

Please load Tape with label Fbackup on device: </dev/rmt/0m>and press Enter when READY

You have to insert the tape cassette in the requested tape drive and press [Enter] when the drive will beready.

The following message will be issued by scbackup invites you to enter the grace time to allow the userto logout.

Enter time for users to log off, before shutdownEnter time in SECONDS [decimal integer or ”now”] >

N.B. If you are performing the backup of a 1353SH Master, 1354RM IM, 1354NN IM, or the main Co-Hosted system, it is advisable to ask also the user logged on the presentation to exit.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

44

03

/3AL 88893 CAAA

112

112

After the specified time the system will be shouted down and rebooted.

During the HP–UX start–up the fbackup will be automatically started.

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

It is necessary to attend the fbackup execution, because of it can ask for more tape cassettes, and whenit require a new cassette you have to remove the current tape and insert a new unprotected one.The fbackup by default will wait up to 1 hour for the new tape cassette issuing the message:

Please MOUNT TAPE Volume <x>

where <x> means the tape cassette number.

If the cassette will be not replaced in 1 hour or you insert a wrong tape the fbackup will fail.

N.B. The default timeout can be defined using the –t option on scbackup commad.

N.B. Fbackup DOES NOT CHECK if you are inserting the IRT one, in this case the IRT will be de-stroyed.

At the end of the fbackup the system will proceed with the start–up as usual, and the result of the activitywill be available in the file /var/adm/syslog/fbackup.log.

Moreover a message with the backup result will be shown at any login.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

45

03

/3AL 88893 CAAA

112

112

4.4.3.2.1 Login messages

At the end of full backup, just in case of problems, you will find one of the following messages:

– Full backup issues a warning. You have to check in the file /var/adm/syslog/fbackup.log, ignoringwarning messages related to the volume header: “WARNING: unable to read a volume header”.Delete the file /var/adm/syslog/fbackup.msg to remove the login message:

****************** THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************

02–Dec–2003 10:30 – Warning: during Fbackup see /var/adm/syslog/fbackup.log

To fix the problem, check the log file

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

Note: If you remove file: ”/var/adm/syslog/fbackup.msg” cancel this message

– Full backup issues an error. You have to check in the file /var/adm/syslog/fbackup.log to identify thereason of the fault, but the backup it is not useful. Delete the file /var/adm/syslog/fbackup.msg to re-move the login message:

****************** THIS SYSTEM IS NOT CORRECTLY BACKUPED *******************

02–Dec–2003 10:30 ERROR : during Fbackup see /var/adm/syslog/fbackup.log

To fix the problem, check the log file

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

Note: If you remove file: ”/var/adm/syslog/fbackup.msg” cancel this message

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

46

03

/3AL 88893 CAAA

112

112

4.5 FULL RESTORE

The full backup and restore tool is design to restore on the same physical system the complete contenstof the hard disks in use with Logical Volume Manager (LVM), the restore on a different hardware it is notguarantee, also if the Ignite UX tool allows such kind of stuff.

The restore is divided in two phases. The first one is done using the IRT tape set and re–creates the LVMdisk configuration existing at backup time, that means the current contents of the disk will be de-stroyed. The second phase recovers the contents of the backup file systems.

4.5.1 Restore of IRT Tape Set

The first step in the recovery process consists in:

– Reconfiguring all the hard disks in use at backup time exactly as them was.

– Restoring a minimum set of HP–UX� operating system on the hard disks, to be able to operate with“frecover” tool.

These two activities are perform by booting the HP9000 system from IRT.

4.5.1.1 Boot from IRT Tape

To boot the HP9000 system from tape you have to:

a ) Switch off the machine.

b ) Switch on the machine.

c ) Wait the message:

To discontinue, press any key within 10 seconds

Press any key to get the console main menu.

d ) Insert IRT in the tape driver, and wait for ready condition of the tape.

e ) Enter the command: sea to identify the tape device in a list like:

To discontinue search, press any key (temination may not be immediate).Path Number Device Path (dec) Device TypeP0 8/4.8 Random access mediaP1 8/4.3 Sequential access mediaP2 10/12.12 Random access media

f ) Boot from tape by enter the command:

boot p<x>

where: p<x> is the path number corresponding to tape drive (P1 in the example).

g ) Do not interact with IPL by entering “n” at query:

Interact with IPL (Y, N or C) >

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

47

03

/3AL 88893 CAAA

112

112

h ) Now the machine have to boot from tape by issuing messages like:

HARD BootedISL Revision ......ISL Booting hpux (;0) INSTALLBoot...: tape (...

i ) If the boot is correctly started you do not get the ISL prompt after three minutes.

j ) The Ignite will perform the recovery of the LVM disk structure and the HP–UX in minimum configura-tion. You do not need to enter any command, just check for any error message.

N.B. The IRT recovery reboots the system twice.

The recovery of IRT can take up to 90 minutes, it depend by the model of the system.

in case of error the Ignite will give a message like the one at follows:

ERROR: The disk at HW path: 0/0/1/1.2.0 was specified in the configuration

files but does not exist on the system. And since

allow_disk_remap=false, no attempt to find a substitute will be made.

Because of the error(s) above, the user–interface must be

used to correct them... Non–interactive install canceled.

Press Return to continue:

When you press “Enter” the Ignite prompt you a window like:

Hardware Summary: System Model: 9000/800/rp7400+––––––––––––––––––––+–––––––––––––––+––––––––––––––––––+ [Scan Again]| Disks: 10 (113.9GB)| Floppies: 0 | LAN cards: 3 || CD/DVDs: 1 | Tapes: 1 | Memory: 2040Mb|| Graphics Ports: 0 | IO Buses: 8 | CPUs: 4 | [H/W Details]+––––––––––––––––––––+–––––––––––––––+––––––––––––––––––+

[ Install HP–UX ]

[ Run a Recovery Shell ]

[ Advanced Options ]

[ Read Sys–Admin Message ] [ Reboot ] [ Help ]

That means there is some thing different in the system configuration that prevents Ignite to performthe automatic recovery, in this case you hove to drive Ignite manually to bypass the problem.

k ) Wait until the end of second reboot.

Some time the machine does not reboot automatically, it stop for a long time (more then20 minutes) just after issue the message:NOTE: tlinstall is searching filesystem – please be patient In this case you can force it to proceed by typing [ctrl]c

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

48

03

/3AL 88893 CAAA

112

112

l ) When the system will start again from the restored disks, you can see on the console one or moremessages like the following one:

INIT: Command is respawning too rapidly.Will try again in 5 minutes.Check for possible errors.id: .....

Do not worry about them in this phase, in fact they are due to the partial restore of performed by Ignite,and to the temporary inconsistency between the restored files and /etc/inittab contents.The messages have to disappear after the restore of fbackup set shown at paragraph 4.5.2 page 48.

4.5.2 Restore from Fbackup Tape Set

At the end of the recovery of IRT you can proceed with the recovery of the fbackup tape set:

Do not perform the restore by a session open via network, because in case of network discon-nection the restore has no recovery procedure, and have to be started again from the beginning.

Do not try to login with GoGlobal–UX tool it is not yet available.

a ) Login as root.

N.B. You have to enter the same password which was active when the backup was done!

b ) After restoring the Ignite tape the system is not fully restored, this means not all the required files areavailable at this time, it is for this reason that at the login some messages are printed:

Cannot chdir to /var/news

cat: Cannot open /SCINSTALL/data/boot_version*: No such file or

directory

Ignore them, obviously these messages will desappear when the restore will be completed.

c ) This is an optional step. If some preliminary actions are required on the system before to activate therestore, it is possible to create a commands procedure named “screstore_init” in the directory“SCINSTALL/etc” that will be executed before to activate the frecover command.

d ) Start the screstore script by entering:

..,sys,root # screstore [Enter]

e ) screstore asks you to enter the tape device file that have to be used for the restore by issuing thefollowing request message:

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

Selection of Tape device

Enter tape device for Frecover <default=<tape device>

Enter the HP–UX file associated to the tape device (ex: /dev/rmt/0m) you want to use for the fbackuptape set and press [Enter], or just press [Enter] to select the shown file (<tape device>).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

49

03

/3AL 88893 CAAA

112

112

f ) Now the procedure asks you to insert the first tape of fbackup tape set. You have to insert the firstcassette into the shown tape device, wait the tape device is ready, and press [Enter] to start.

Preparation Tape media for RECOVER

Please load Tape with label Fbackup on device: </dev/rmt/0m>

and press Enter when READY

g ) The recovery will start showing you the label that you should have on the Fbackup tape:

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

Execution of RECOVER

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

Mounted Tape media should have this label:

hosta – Fbackup Volume x of n

01–Dec–2003 14:26 – Full Backup

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

Press Enter to continue

h ) After you press [Enter] a check on the tape data is made to verify if it is consistent with the currentsystem configuration. First of all a report is provided regarding the list of saved volume groups:

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

Tape data compared with the system

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

Backup tape contains the volume groups:

vg00

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

i ) Then the some more information are checked, refer to paragraph 4.5.4.1 at page 55 to see the fore-seen warning message and the tips for check them.

j ) The script issue the following message to ask you the authorisation to change the HP–UX run levelto level three:

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

Now all Application must be stopped, system go to run level 3

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

Are you ready, system go to run level 3 (y|n) ? :

Just enter “y” and press [Enter] to proceed.

k ) The recovery will start, but it is necessary to attend the frecover execution, because it can ask formore tape cassettes, and when it require a new cassette you have to remove the current tape andinsert the next one.

Mount the next tape when the request message “Please MOUNT next TAPE Volume” appears,and press “ENTER” after the message:

frecover(5404): Press return when the next volume is ready on /dev/rmt/0m:

N.B. Don’t warry for the messages like the following:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

50

03

/3AL 88893 CAAA

112

112

frecover(1075): moved emsagent to emsagent.2510 since it was executing. Remove em-sagent.2510 when done.

l ) If you insert the wrong tape the frecover will return some messages and questions like the onesreported at follows, you have to answer as indicated in the example.

frecover(5423): incorrect volume mounted;frecover(5424): expected volume 1, and got 2frecover(5433): Do you wish to continue using this volume?([yY]/[nN]) nfrecover(5412): Do you wish to try to salvage this volume?([yY]/[nN]) nfrecover(5411): Do you wish to try a different volume? ([yY]/[nN]) y

PLEASE MOUNT next TAPE Volume

Mount the correct tape when the previous message appears, and then press “ENTER” at therequest.

The frecover can take 150% of the backup time.

m ) At the end of the restore, if the system was mirrored at the backup time, the procedure will give youthe message reported at follows.

************************************************** Frecover end successfullyUnload Fbackup Tape

***************************************************************************** NOTE: The restored data was mirrored at the backup time. You can use the procedure ’scmirrorfs’ to rebuild the mirror: scmirrorfs [<vgname>] *****************************************************************************

Press Enter to continue

If you like to rebuild the mirror, you can activate the script ’scmirrorfs’ when the backup is ended (referto appendix 4.5.3 at page 52 for an example).

n ) After you press [Enter] the creation of Physical Volume Group 0 will be activated.

***************************************************************************** Make PVG0 for volume groups: vg00 *****************************************************************************

=>Wed Feb 11 16:40:10 MET 2004 =>START: OSConf File(s) System Creation of Physical Volume Group 0

NOTE: Updating of LVM physical volume group information file

NOTE: Set Logical Vol allocation policy to ”PVG–strict” x select Volume Group

=>Wed Feb 11 16:40:16 MET 2004 =>END: OSConf File(s) System Creation of Physical Volume Group 0

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

51

03

/3AL 88893 CAAA

112

112

o ) When the restore is completed the system must be reboot again to perform the HP–UX start–up withthe complete environment available on disks.

***************************************************************************** Now you must execute SHUTDOWN and REBOOT for go to Production *****************************************************************************

Is system READY for execute SHUTDOWN & REBOOT (y|n) ? :

Just enter “y” and press [Enter] to proceed.

p ) screstore asks for the time to reboot:

Enter time for users to log off, before shutdownEnter time in SECONDS [decimal integer or ”now”] >

Enter “now” and press [Enter] to proceed.

q ) When the system will be ready again you can perform the Alcatel TNM application data restore follow-ing the appropriate recovery procedure (if any), and then start–up again the application too.

If the backuped machine was configured with mirror configuration you have to proceed with “Restore Mir-ror Condifuration” paragraph 4.5.3 at page 52.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

52

03

/3AL 88893 CAAA

112

112

4.5.3 Restore MIrror Configuration

The full restore function does not cover mirror disk configuration, it restores the entire file system, includingDisk Mirror/UX� but it does not configure the mirror. The reasons of this choice are two:

1 ) hp Ignite–UX� recovery procedure does not support the mirror disk recovery.

2 ) Perform the mirror configuration during the restore phase increases the down time of the TMNApplications.

To make easier the mirror configuration OS–Conf provides a specific script “scmirrorfs” to set–up the mirrorconfiguration again.

To be able to set–up again the mirror configuration, it is advisable that all the disks previously present inthe configuration are available. Really “scmirrorfs” does not completely know the mirror disk configurationpresent during the backup, so you have to assign again the mirror copy disks.

N.B. Assigning the disks is possible to change the previous configuration.

The procedure will show you the current disk usage asking you to enter the device name of the disk thathave to be used to store the mirror copy of the data. It is not mandatory that disks belonging to the mirrorcopy disk set have to be physically identical to the main disk set, but the amount of space have to beenough to store all the logical volume currently defined, and it is advisable that disks belonging to mirrorcopy disk set do not share the same SCSI chain of the main disk ones. When the configuration script recog-nize that the disk you are adding to the mirror copy is connected to a SCSI chain already in use for themain disk set the following warning message is issued:

WARNING: Controller disk already used in “Main path (pvg0)”Do you want to choose another disk ?

If you have to guarantee the machine functionality also in case of failure of the disk controller, you mustto choose another disk belonging to another chain.

This is an example of the input required and the output produced by ’scmirrorfs’ script.

..,sys,root # scmirrorfs vg00 [Enter]

=>Tue Dec 2 16:29:05 MET 2003

=>START: OSConf File(s) System Mirroring

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

Total disk(s) found = 6

Total CDRoms found = 1

Press [Enter] to continue...

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

53

03

/3AL 88893 CAAA

112

112

_______________________________________________________________________________

Disks Selection

Mirroring need Alternate Boot disk on Volume Group:”vg00”

_______________________________________________________________________________

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)_ ______ _____________

c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ _____________

c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ _____________

c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ _____________

c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ _____________

_______________________________________________________________________________

Select Alternate BOOT dev name or [q] to quit: c4t8d0

_______________________________________________________________________________

Disks Selection

_______________________________________________________________________________

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)_ ______ _____________

c4t8d0 8680 0/4/0/0.8.0 Alt_Boot Mirror vg00

c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ _____________

c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ _____________

c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ _____________

_______________________________________________________________________________

Confirm selection of device ”c4t8d0”

Press [y] for yes, [n] for no or [q] to quit, then press [Enter] y


NOTE: Set Logical Vol allocation policy to ”PVG–strict” x select Volume Group

NOTE: Preparation of Mirroring Volume Group: ”vg00”

NOTE: Mirroring all Logical Volume of Volume Group: ”vg00”

=>Tue Dec 2 16:31:27 MET 2003

....... Mirroring Logical Volume:”/dev/vg00/lvol1”,

with Allocation policy ”contiguous”

=>Tue Dec 2 16:31:40 MET 2003

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

54

03

/3AL 88893 CAAA

112

112



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



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

....... Mirroring Logical Volume:”/dev/vg00/lvol4”

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


=>Tue Dec 2 16:36:01 MET 2003


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


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


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


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


NOTE: Check /etc/lvmrc .....

=>Tue Dec 2 16:42:30 MET 2003

NOTE: Set Alternate Boot Hardware Path to disk:”c4t8d0”

=>Tue Dec 2 16:42:30 MET 2003

=>END: OSConf File(s) System Mirroring

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

55

03

/3AL 88893 CAAA

112

112

4.5.4 Restore Warning and/or Error Messages

In order to prevent errors due to tape labeling mistake, or simple tape swap, screstore procedure foreseento perform some checks before start the file system(s) restore. This paragraph summarize the possiblewarning messages and provides information to support who is operating to decide when proceed andwhen stop.

In case of inconsistency between the data present on tape and the system configuration, you will receiveerror or warning message. Normally this should happen for three main reasons:

a ) The IRT and Fbackup tape was not produced on the same system, tapes coming from different sys-tems have been mixed.

b ) The IRT and Fbackup tape have been produced at different time and with different system configura-tion. That means you are trying to restore a Fbackup tape over a system where the disk configurationis so different that the target file system is not available or not enough large to perform the restore.

c ) The tape set is the correct one, but something has been modified during the Ignite recover process(interactive restore installation), or after the successful Ignite recover and before the scretore pro-cess.

For the first two possibilities you should check the tapes validity and the last one obviously should createproblems.

If an inconsistency occurs it is advisable to stop the restore process in order to investigate on the problemand after the correction you can run again the ’screstore’ procedure.

At follows are reported some examples listed in category order, where it is possible a corrective action isdescribed:

4.5.4.1 /alcatel File System Not Empty

Each time the backup involves the system volume group (vg00) the following message is shown:

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

NOTE: If you have activated the ’screstore’ procedure after the system

recover from the Ignite tape, do NOT take into account the

message at follows related to the ’/alcatel’ directory

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

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

WARNING: Mount Point: ”/alcatel”

is not an empty directory

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

The message is shown because the file system mount on to /alcatel directory is not empty, but this casecan occur very often, because every NMS instance can create a directory in /alcatel one. So the best wayto proceed is: ignore this warning message if you have just restore hp–ux� from IRT. Otherwise it is betterto not go on.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

56

03

/3AL 88893 CAAA

112

112

4.5.4.2 Host inconsitency

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

ATTENTION: Current host is different from the one backuped.

Current host –> hosta Backuped host –> hostb

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

N.B. This message can be ignored when you are restoring on a 1359HA OS–Cluster system.

4.5.4.3 Volume Group Configuration Mismatch

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

ERROR: Volume group name ”1353NM_1”

present on tape but not defined on system

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

Verify the IRT and Fbackup tape consistency.

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

ERROR: Volume group name ”1353NM_1”

present on tape but not activated on system

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

Try to activate the volume group you can use the command: vgchange –a y <Volume Group>, and lookat the error messages issued by the activation command, if any.

4.5.4.4 Logical Volume Configuration Mismatch

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

ERROR: Logical volume ”/dev/vg00/lvol11”

present on tape but not defined on system

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


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

ERROR: Logical volume ”/dev/vg00/lvol11”

present on tape but not mounted on system

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

Try to mount the logical volume with the command: mount <Logical Volume Device>If the command succeded just run again “screstore”, otherwise if the error issued looks like:mount: /dev/vg00/lvol11 was either ignored or not found in /etc/fstabverify the IRT and Fbackup tape consistency.

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

WARNING: Logical volume ”/dev/vg00/lvol4”

references different mount point.

Tape mount point –> ”/user”

System mount point –> ”/home”

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


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

57

03

/3AL 88893 CAAA

112

112

4.5.4.5 Mount Point Directory Mismatch

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

ERROR: Mount Point: ”/alcatel/Kernel/SystemInstances/1353NM_1_7.0_Master”

is not a directory

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


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

WARNING: Mount Point: ”/alcatel/Kernel/SystemInstances/1353NM_1_7.0_Master”

is not an empty directory

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

This message can be issued in case of mount point directory nesting, in this case you should have oneor more empty directory, it it is the case you can proceed, otherwise check the contents.

4.5.4.6 File System Configuration Mismatch

The disk size is erroneously shown in Kilo byte instead of Mega bytes.

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

WARNING: There is not enough space available on file system:

”/alcatel”

required space –> 500 Kb free allocated space –> 400 Kb

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

Extend the file system using the command: scextendfs <File System> <Free Mega Bytes>

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

WARNING: The dimension of the file system:

”/alcatel”

is smaller than the required

required space –> 600 Kb total allocated space –> 550 Kb

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

Extend the file system using the command: scextendfs <File System> <Free Mega Bytes>

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

58

03

/3AL 88893 CAAA

112

112

4.5.4.7 How to proceed

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

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

NOTE: Are you sure the CORRECT TAPE HAS BEEN MOUNTED ?

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

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

WARNING: If you proceed you should have data or system problems.

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

Do you want continue the restore (y|n) ? :

If the warning messages have been analyzed and the warning condition are not present, enter “y[Enter]”to proceed.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

59

03

/3AL 88893 CAAA

112

112

4.6 BACKUP AND RESTORE KNOW PROBLEMS AND WORKAROUNDS

4.6.1 Ignite Rcovery Problem

The problem concerns the ignite recovery ERROR from bootable tape.

================================================================================= 10/05/04 05:07:22 EDT HP–UX Installation Initialization. (Tue Oct 05 05:07:22 EDT 2004) @(#) Ignite–UX Revision B.5.1.33 @(#) install/init (opt) $Revision: 10.279 $ * Scanning system for IO devices... * Querying disk device: 0/0/1/1.0.0 ... * Querying disk device: 0/0/1/1.2.0 ... * Querying disk device: 0/0/2/0.0.0 ... * Querying disk device: 0/0/2/0.2.0 ... Recovery tape created from system: bonhomme on Mon Oct 4 11:10:15 2004 WARNING: The configuration information calls for a non–interactive installation. Press <Return/Enter> within 10 seconds to cancel batch–mode installation: * Using client directory: /var/opt/ignite/clients/0x001083FFA90A * Checking configuration for consistency... ERROR: There is not enough disk space to allocate for volume: ”/opt” (short by 16Mb). NOTE: Free space (786432KB) in ”/var/adm/crash” where /var/adm/crash is located is less than system memory (1572864KB). This should be enough space to capture at least a single dump (and likely more than that if the dump is selective and/or compressed) in the event of a system crash. Additional space may be required to uncompress the dump in order to analyze it and to save multiple dumps. You can increase the size of the ”/var/adm/crash” volume on the ”File System” tab when using the advanced user interface. ... ... ...

Because of the error(s) above, the user–interface must be used to correct them... Non–interactive install canceled. Press Return to continue: ==========================================================================

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

60

03

/3AL 88893 CAAA

112

112

4.6.1.1 Workaround

This error is due to an Ignite fault, in some particular conditions the restore of filesystems extended overmultiple disks fail.This should happen on hosts with many small disks.

The problem has been alredy submitted to HP and it has been accepted, so the Ignite software will beupdated, but at the moment we have no idea about the delivery date of the new Ignite release solving theproblem.

In consideration of the long time that should be taken by HP, a by–pass will be implemented in the AlcatelBackup–Restore product.

As workarond you should make an adjustement, activate the recovery from the Ignite tape and when theerror appears go in interactive and perform the following actions:

a ) From the Ignite selection menu click on the [ Install HP–UX ] button, then select the “[ * ] AdvancedInstallation” option ( it is already flagged by default ), continue and select the ”File System” menu(which is showing the error).

b ) Click on the [ Additional Tasks ] button, then go to ”Volume parameters”.

c ) From the list select the volume associated to the mount directory which gives the error and then clickon the [ Disk Mapping ] button.

d ) Change from ”Assigned Disk” to ”Any”.

e ) Apply the modified configuration so that Ignite will create the filesystem on any of the disks that hasenough space.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

61

03

/3AL 88893 CAAA

112

112

4.6.2 Recovery Archive Error – Ignite recovery

The problem concerns the ignite recovery ERROR from bootable tape.

========================================================================== x ./monitor_bpr, 20480 bytes, 40 tape blocks * Download_mini–system: Complete * Loading_software: Begin * Installing boot area on disk. * Enabling swap areas. * Backing up LVM configuration for ”vg00”. * Processing the archive source (Recovery Archive). * Wed Oct 06 05:47:55 EDT 2004: Starting archive load of the source (Recovery Archive). * Positioning the tape (/dev/rmt/0mn). * Archive extraction from tape is beginning. Please wait. pax_iux: alcatel/Kernel : File exists ERROR: Cannot load OS archive (Recovery Archive) The configuration process has incurred an error, would you like to push a shell for debugging purposes? (y/[n]): ==========================================================================

4.6.2.1 Problem solution

If on the system was created by mistake a wrong file system, probably you have NOT respected the backuprestrictions (see paragraph 4.3.7 at page 33). In this case, to correct the problem you have to perform thefollowing actions:

a ) After the error, when the system suggest to push a shell for debugging, answer ”n” so the systemreboot:

==========================================================================

ERROR: Cannot load OS archive (Recovery Archive)

The configuration process has incurred an error, would you like to push a shell for debugging purposes? (y/[n]): n

* Loading_software: Error

======= 10/05/04 05:01:03 EDT Installation complete: Failure

NOTE: Search for the word ”ERROR” in the log file for details:

on a server: /var/opt/ignite/clients/0x00306E086FA0/install.log on a client: /var/opt/ignite/local/install.log

NOTE: Rebooting system.

...

==========================================================================

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

62

03

/3AL 88893 CAAA

112

112

b ) Wait for the message:

Press <Return/Enter> within 10 seconds to cancel batch–mode installation:

c ) Press [Enter] and confirm the start of the user–interface:

========================================================================== ======= 10/05/04 05:07:22 EDT HP–UX Installation Initialization. (Tue Oct 05 05:07:22 EDT 2004) @(#) Ignite–UX Revision B.5.1.33 @(#) install/init (opt) $Revision: 10.279 $ * Scanning system for IO devices... * Querying disk device: 0/0/1/1.0.0 ... * Querying disk device: 0/0/1/1.2.0 ... * Querying disk device: 0/0/2/0.0.0 ... * Querying disk device: 0/0/2/0.2.0 ... Recovery tape created from system: bonhomme on Mon Oct 4 11:10:15 2004 WARNING: The configuration information calls for a non–interactive installation.

Press <Return/Enter> within 10 seconds to cancel batch–mode installation: Really cancel non–interactive install and start the user–interface? ([y]/n): y ==========================================================================

d ) Go in interactive and from the Ignite selection menu click on the [ Install HP–UX ] button, then select the ”[ * ] Advanced Installation” option (flagged by default), continue and select themenu ”File System”.

e ) From the list select the file system associated to the mount directory defined by mistake and thengo on the ”Mount Dir” field.

f ) Change from ”wrong mount” to ”correct mount”, in particular for the TNDvy31274 ddt from:

”/alcatel/Kernel/SystemInstances/1353NM_13_7.0_Presentation”

to:

”/usr/Systems/1353NM_13_7.0_Presentation”

g ) Then click the [ Modify ] button and after apply the modified configuration using the [ Go! ] button,so that Ignite will define the new mount point for the filesystem.

N.B. Consequently to the modification when the screstore procedure will be activated after the recov-er completion the following error will be reported, it can be obviously ignored.

***************************************************************************** ERROR: Logical volume ”/dev/vg00/lvol18” references different mount point: Tape mount point –> ”/alcatel/Kernel/SystemInstances/1353NM_13_7.0_Presentation” System mount point –> ”/usr/Systems/1353NM_13_7.0_Presentation” *****************************************************************************

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

63

03

/3AL 88893 CAAA

112

112

4.6.3 Full User Disk Backup problem

The problem concerns the full user disk backup in a Cluster environment configured with a Virtual Array.

During the backup, there was an ERROR message (see the log below) . The backup was relaunched auto-matically after a recovery process. It seems that the backup eventually ended successfully.

========================================================================== ************************************************** scbackup (Backup–Restore Ver. 2.3)

***************************************************************************** ATTENTION: You select the volume group ’1354RM_3’ this suppose your SYSTEM IS NOT CHANGED since the last creation of the IRT (Ignite Recovery Tape) ***************************************************************************** ************************************************** Selection of Tape device Enter tape device for Fbackup <default=/dev/rmt/0m> ************************************************** Environment verification sh: armdsp: not found. sh: armdsp: not found. ***************************************************************************** To preserve data integrity and avoid problems you should: STOP APPLICATIONS that use the volume group ’1354RM_3’ before start backup. ***************************************************************************** ***************************************************************************** NOTE: If you need to stop anything, do it before answer ’YES’ to the next question. ***************************************************************************** Do you want continue with backup operation (y|n) ? : y ************************************************** Business Copy procedure /SCINSTALL/bin/sconlinebackup[11]: test: Specify a parameter with this command. /SCINSTALL/bin/sconlinebackup[11]: armdsp: not found. ***************************************************************************** ERROR: (Internal Error in AddDiskVG), not found LUN 0 on Virtual Array: ”” ***************************************************************************** ***************************************************************************** ATTENTION: Recover process activated due to ERROR. Error during data copy phase see: /var/adm/syslog/sconlinebackup.log ***************************************************************************** ************************************************** RECOVER process Start RECOVER process on backup Logical Volumes This operation takes a while, please wait ... RECOVER End Successfully ***************************************************************************** ERROR: during data COPY phase. *****************************************************************************

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

64

03

/3AL 88893 CAAA

112

112

Do you want continue with standard backup (y|n) ? : y ************************************************** Preparation Tape media for FBACKUP tool Please load Tape with label Fbackup on device: </dev/rmt/0m> and press Enter when READY Waiting on Rewind tape ***************************************************************************** To preserve data integrity and avoid problems you should: – STOP APPLICATIONS that use the volume group ’1354RM_3’ before start backup; – WAIT the backup completion and than restart applications. ***************************************************************************** ***************************************************************************** NOTE: If you need to stop anything, do it before answer ’YES’ to the next question. ***************************************************************************** Do you want continue with backup operation (y|n) ? : y ************************************************** Preparation Tape media for BACKUP Fbackup tape devices ”/dev/rmt/0m” 21–Oct–2004 15:34 Execute Backup : Start Backup ... Execute Backup : End Successfully ***************************************************************************** DATA ARE SUCCESSFULLY BACKUPED ***************************************************************************** ************************************************** Remove Tape media and recommended label is: bibiche – Fbackup Volume x of n 21–Oct–2004 15:33 – Cluster Single Volume 1354RM_3 ************************************************** ***************************************************************************** ATTENTION: NOW you can RESTART APPLICATIONS !!! ***************************************************************************** ==========================================================================

4.6.3.1 Problem solution

The problem is due to the path not well configured for the VA commands, this is because the logic for thepath setup has been changed starting from backup version 2.3. As conseguence of this problem in notpossible to make the business–copy of the volume group, however this have no impact on the backup butit require a logger downtime of the involved applications because you should not reactivate them until thebackup is ended.

N.B. The backup of the volume group is successful, obviously on condition that the involved applica-tions have been stopped.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

65

03

/3AL 88893 CAAA

112

112

5 Mirror Disk/UX Management

A specific configuration script is provided to aid in the Mirror Disk/UX� configuration, you have to enterthe command:

5.1 Configuring Mirror Disk/UX

This paragraph describe how to configure disk fault protection with Mirror Disk/UX� in the Alcatel TNMenvironment using the script provided for this purpose.

5.1.1 Prerequisite

The mirror configuration require that both hereafter conditions are satisfied:

– The HP Mirror Disk/UX is authorized and installed on the system.

– The amount of available hard disks is enought to create a copy of entire file system.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

66

03

/3AL 88893 CAAA

112

112

5.1.2 Install Mirror Disk/UX

Mirror Disk/UX is usually installed together HP–UX operating system, if you need to install it later followthe hereafter procedure.

N.B. Mirror Disk/UX is a HP Software, check that the customer has the related license of use.

N.B. The Mirror Disk/UX installation forces the system to reboot.

a ) Login the system as user “root’.

b ) Enter the command:...,sys, root # /SCINSTALL/etc/scinstall3PP MIRROR[Enter]

c ) Select the source between CD/DVD or depot:––––––––––––––– LAYERED PRODUCTS Repository ––––––––––––– 1 – DVD/CDRom 2 – DEPOT

q – quit

Insert choice and press [Enter]:

d ) If you choose DVD/CDRom, you have to confirm the source device by replying the following question:––– Device selection for LAYERED Products installation ––––

Enter ’q’ to Quit or the CD device [def=/dev/dsk/c3t2d0]:

e ) If you choose depot, you have to provide the depot absolute path, including the host name when thedepot is not local:

––– Depot selection for LAYERED Products installation ––––

Enter ’q’ to Quit or the Depot absolute path name:

f ) Before start execution and reboot the system, the procedure give you last chance to postpone theactivity by issuing the following message:

***************************************************************** ATTENTION Installation require shutdown and reboot Applications is better already stopped before start installation ****************************************************************

Do you want execute installation NOW?:Press [y] for yes or [n] for no, then press [Enter]

N.B. Replying no to this question you do not cancel the Mirror Disk/UX installation!

Enter “y[Enter]” to reboot and start the installation, or “n[Enter]” to postpone it, in this case you haveto resume the installation, when ready to reboot, by entering:

...,sys,root # /SCINSTALL/SCINSTALL start[Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

67

03

/3AL 88893 CAAA

112

112

5.1.3 Configure Mirror Disk/UX with Alcatel Script

Alcatel TMN system configuration tools allow to easy manage the file system extension, but requires aspecific mirror configuration. The mirror configuration can be execute in three different stages:

1 ) Initial system installation.

2 ) Restore from full disk backup.

3 ) New disk mirror configuration.

The initial system installation automatically execute the entire file system mirroring, the remaining twocases the mirror have to be set up executing the following procedure.

N.B. After the mirror disk set up, any file system belonging to mirrored volume group will be mirrored.

...,sys,root # scmirrorfs [Enter]

And the procedure will show you the current system disk configuration:___________________________________________________________________________

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

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 __Data__ _Main_ vg00 c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ ___________ c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ ___________ c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ ___________ c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ ______________________________________________________________________________________

Select Alternate BOOT dev name or [q] to quit:

You have to select the disk for the mirror copy by follow the guide line shown at paragraph 5.1.3.1 “DiskMirror Configuration Policy” at page 68. And as soon as the amount of disk space requested will bereached the procedure will configure the mirror by issuing messages like the following:


NOTE: Set Logical Vol allocation policy = ”PVG–strict” on Active VolumeGroup

NOTE: Preparation of Mirroring Volume Group: ”vg00”

NOTE: Mirroring all Logical Volume of Volume Group: ”vg00”

=>Thu Jul 29 12:34:33 METDST 2004....... Mirroring Logical Volume:”/dev/vg00/lvol1”, with Allocation policy ”contiguous”y

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

68

03

/3AL 88893 CAAA

112

112

5.1.3.1 Disk Mirror Configuration Policy

The disk mirror capability is used for two main purposes:

1 ) Allow system to survive in case of a single disk failure.

2 ) Allow system to survive in case of a single disk controller failure.

It is possible to obtain the better high availability goal only with a correct configuration of the disk resourcesavailable on the system. HP–UX� Mirror Disk/UX� allows to reach the first target without specific configu-ration, but to be able to reach the second one you must have an appropriate system configuration in termsof hardware and software. The hardware suggested by Alcatel are design to allow mirror configuration thatallow system to survive to disk controller failure, but the software configuration has to be done as shownin 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 identi-fied by their file name. In particular the file name can be very helpful to identify the disk – controller relation-ship. Any disk in the configuration is identified by the following name: c#t#d#

c[0–15] SCSI of Fiber Channel card instance of disk controller to which the disk is attached to.t[0–15] SCSI of Fiber channel address of the device on the interface.d[0–15] 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.

HP–UX� allows to connect a single disk to two different controller (Dual–Access), in this case the systemcommand can show two device file for the same disk units, but the installation script manage this configura-tion by showing just one device with a “D” on the first column of the related line, hereafter an example ofthe 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 :

Now you have to define two disk group (physical volume group) with the following characteristics:

1 ) The sum of disk space amount of the two group have to be the same.2 ) The Dual–Access disks can be assigned to any group.3 ) The non Dual–Access disks connected to the same controller MUST belong to the same group.

N.B. It is important to follow this rules starting from boot disk definition 5.1.3.2 at page 69.

The following picture is a schematic example of disk configuration that can produce the output shown be-fore. This is not a typical system, but provided all the case that can occur in field.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

69

03

/3AL 88893 CAAA

112

112

c1t2d0

c2t2d0

c4t8d0 c4t9d0

c6t12d0 c6t13d0

Figure 2. Example of disk configuration

With this configuration the best one are:group 1 with c1t2d0, c4t8d0 and c4t9d0, group 2 with c2t2d0, c6t12d0 and c6t13d0.group 1 with c2t2d0, c4t8d0 and c4t9d0, group 2 with c1t2d0, c6t12d0 and c6t13d0.Because the I/O channel are balanced.

Allowed configuration can be:group 1 with c4t8d0, c1t2d0, and c2t2d0, group c4t9d0, c6t12d0 and c6t13d0.

Wrong configuration:group 1 with c1t2d0, c4t8d0 and c6t12d0, group 2 with c2t2d0, c4t9d0 and c6t13d0.Because the two non dual–access disks have been assigned to the two groups, and the controllerfailure gets the system in failure too.

5.1.3.2 Main Boot Disk Selection

The first disk you have to select is the main boot disk for the system, the list of the available disk will beshown 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].

N.B. A ”D” character is shown before the device name in the “Device” column to advice the disk isaccessible via two different disk controllers. This configuration is typically used with Fiber Chan-nel device.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

70

03

/3AL 88893 CAAA

112

112

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

71

03

/3AL 88893 CAAA

112

112

6 NETWORK DEPOT MANAGEMENT

Multiple system installation can be improved by using network depot for software warehousing. The Alca-tel TMN installation procedure foresees two type of software depot: platform and application depot.

6.1 Platform Software Depot

After the HP–UX�11i installation it is possible to performed the rest of installation of software layeredproducts in unattended mode. This can be done devoting some Gbyte of a machine installed with OS–Confto create a depot with all the software included in the CD’s, then when the predispose script will ask youfor the source you, have to reply with the following depot address: <depot host>:/alcatel/SCDEPOT. In factOS–Conf includes “scbuilddepot“ script that drives the depot building.

Login the devoted depot system as root user and enter the command:

...,sys,root # scbuilddepot [Enter]

The procedure will ask you to confirm your request by issuing the message:

======================================================================== OS–Conf Depot Builder========================================================================The depot copy requires 2.3 Gbytes extra space on disks* Do you have enough space available [Y/N] :

If you have enough large disks replay with “y” , and the activity will start asking for the source media, theonly media supported is the CD–ROM, you can just change the default with another one. The default pro-vided is the CD–ROM device used to install HP–UX�.

* Enter the CDROM device [ /dev/dsk/c1t2d0 ] :

NOTE: Checking/Extending /alcatel for depot creation

If the current size of the partition mounted at /alcatel is not enough, new disk resources will be requireduntil reach the requested size. Here an example of the extension:

Analyze Mount Point:”/alcatel”Request free MegaByte(s): 1950 Evaluate size MegaByte(s): 4128

Hardware detection in progress, please wait ........ Total disk(s) found = 4 Total CDRoms found = 1 Press [Enter] to continue...

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

72

03

/3AL 88893 CAAA

112

112

Mount Point need 1536MB on /dev/vg00 (PVG0)___________________________________________________________________________ Disks SelectionMount Point: /alcatel___________________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup___________________________________________________________________________ c0t5d0 4088 8/12.5.0 Pri_Boot _Main_ vg00 c0t6d0 2048 8/12.6.0 __Data__ _Main_ vg00 c1t4d0 2048 8/16/5.4.0 _(free)_ ______ __________ c1t5d0 2048 8/16/5.5.0 _(free)_ ______ _____________________________________________________________________________________Select Data Area (Main instance) dev name or [q] to quit: c1t4d0

When finally the file system mounted at /alcatel will be large to contain the depot the procedure will askyou to introduce the first disk of the set:

* Please insert CD SWP–OSCONF–V7.1.0 – 1/4 into the drive and press [Enter] when ready

Insert the CD and press return when the CD–ROM driver led will stop blinking. The procedure will ask youagain for all the disks of the set.The procedure will terminate displaying the following error message:

ERROR: Depot /alcatel/SCDEPOT created with 1 errors

6.1.1 Build Depot know bug and workaround

A software bug has been identified creating a depot with OS–Conf V7.1.0–P05, two software packagesare not automatically copied in the depot. If you are use this version creatre a depot you have to executethe following procedure:

– Mount the SWP–OSCONF–V7.1.0 volume 1/4 CD–ROM currently inserted in the CD driver:...,sys,root # scmountcd /dev/dsk/<device name> /SD_CDROM[Enter]

– Copy two packages in the depotNote: The courier font has been used instead of to better show the second character of workPlRPC is a lower case L, and not an uppercase i....,sys,root # swcopy –x enforce_dependencies=false \.[Enter]–s /SD_CDROM Net–Daemon PlRPC @/alcatel/SCDEPOT[Enter]

– Dismount the CD and remove it from CD or DVD drive:...,sys,root # umount /SD_CDROM [Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

73

03

/3AL 88893 CAAA

112

112

6.1.2 Additional Software

To add the OSCONF Engine and 3PP description and the NMS description to the depot, is necessary toexecute the following commands:

– Mount the SWP–OSCONF–V7.1.0 volume ADD1_P05 CD–ROM currently inserted in the CD driver:...,sys,root # mount –o rr /dev/dsk/<device name> /SD_CDROM[Enter]

– Copy OS–CONF engine and 3PP description:...,sys,root # swcopy –x enforce_dependencies=false \ [Enter]–s /SD_CDROM OS–CONF OSC–3PP @/alcatel/SCDEPOT [Enter]

– Dismount the CD and remove it from CD or DVD drive:...,sys,root # umount /SD_CDROM [Enter]

When the depot construction will be completed, you can predispose any Network Management Systemin your local area network by choosing entering: <depot hostname>:/alcatel/SCDEPOT

6.1.3 Software Depot Update

If a software platform depot already exists, before use it you have to upgrade also the software depot byexecute again the depot building script:

...,sys,root# scbuilddepot [Enter]

6.2 Application Software Depot

This paragraph shows how to create the depot for Alcatel software. The depot size depends by the soft-ware you have to store on the disk, Table 2. summarizes the space required in Mega bytes.

The following actions must be executed on the depot machine; preferably it should be a machine in thenetwork. It may be the same machine that you are installing, if you have sufficient free disks space.You have to login to the alcatel depot machine as “root” user, and execute the following command:

1 ) Extend /alcatel to allow the storage of Alcatel software by entering the command:...,sys,root # scextendfs /alcatel/DEPOT <required disk size> [Enter]

2 ) Change the default directory on the depot one:...,sys,root # cd /alcatel/DEPOT [Enter]

3 ) For each distribution CD Rom that contains the software you have to install:

a ) Insert the CD into the driver.b ) Check the CD–ROM type:

...,sys,root # fstyp /dev/dsk/<cdrom device file> [Enter]c ) Mount the CD at /SD_CDROM directory:

• if the CD–ROM type at point “b )” is “cdfs” use:...,sys,root # mount –o rr /dev/dsk/<cdrom device file> /SD_CDROM[Enter]

• if the CD–ROM type at point “b )” is “hfs” use:...,sys,root # mount –r /dev/dsk/<cdrom device file> /SD_CDROM[Enter]

d ) Copy the entire CD contents to /alcatel/DEPOT directory by entering the command:...,sys,root # cp –p /SD_CDROM/* /alcatel/DEPOT [Enter]

e ) Dismount the CD:...,sys,root # umount /SD_CDROM[Enter]

f ) Remove the CD from the device.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

74

03

/3AL 88893 CAAA

112

112

6.2.1 Authorize Access to Application Depot

To be able to retrieve the Alcatel software packages from the depot machine, the access to these files haveto be granted to all the root users of all the machines that have to be installed. This can be done by tempo-rary adding the hostname followed by keyword “root” for each machine involved in the /.rhosts 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 roothostb roothostc root

N.B. At the end of installationn do not forget to delete the lines added in /.rhost file.

N.B. All the host included in .rhosts file have to be defined in /etc/hosts one.

6.2.2 Disk Requirement TablesThe following table shows the disk space requested for swap, program installation, and depot packages.The value are specified in M bytes

NMS Depot Package Size

OS–Kernel 750

1353NM 2400

1354BM ATM 100

1354BM ETH 350

1354BM PR 35

1354RM 550

1355VPN 10

1359HA OS–RES 5

1359ISN 130

1359IOO 15

Table 2. Disk requirements for NMS Software

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

75

03

/3AL 88893 CAAA

112

112

7 SECURITY

This chapter describes the security feature introduced to prevent unauthorized access to the system.

7.1 Introduction

The 1350 security provided a concrete improvement to standard HP–UX system. It sets up HP TrustedSystem configuration and performs system hardening with HP Bastille. This approach considerably re-duces the risk of attack, also if it can not guarantee 100% the system security.This security approach is based on user authentication, that means each user is identified by the systemwith it user identifier and the access is granted by a password.

7.2 Security Preparation

The security configuration script is provided with 1350 MS starting from Network Release 7.1D, but beforeuse it, some activities as to be executed to allow the correct security set–up.

7.2.1 Software Requirements

The security set–up procedure is base on software shown in the following table:

Product Version Description

B6849AA B.02.01.01 HP–UX Bastille Security Hardening Tool

T1471AA A.03.71.00 HP–UX Secure Shell

KRNG11i B.11.11.07 HP–UX 11i Strong Random Number Generator

ixSUDO A.02.00–1.6.7p5 Super User DO

logrotate 3.7 Logs rotate Tool

Table 3. Software requested by 1350 MS Security

The security set–up procedure will check the software in the target system, and it automatically activatethe software installation procedure when any of them is not found, refer to paragraph 7.3.3 at page 80 forthe specific procedure.

N.B. The software installation can require the system reboot.

N.B. When at least one required software is not present, the procedure does not activate the securityprofile, but just install the software.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

76

03

/3AL 88893 CAAA

112

112

7.2.2 Security User and Groups

The security set–up requires defining the security administrator user and two user groups, the securitygroup for the security administrator and a specific one for ftp guest users (ftpscoss).

The UID and GID of these users and groups is defined in advance, in agreement with the UID and GIDdefinition roles of 1350 MS environment, it is not allowed a different user and group definition then oneshown in the following tables:

Table 4. Security User

User name UID

security 199

Table 5. Security Groups

Group name GID

security 199

ftpscoss 198

The user belonging to ftponly group will be manage as ftp guests.

7.2.3 Customize Login and FTP Banners

1350 MS security set–up the banners pages that will be shown at login time for both shell and ftp access.The two banners are just as example, you have to customize them with your company trade marks, orreplace them with your own one. The banner issued after the login with a shell is stored in /etc/motd file,instead the ftp one into /etc/ftpd/ftp_banner

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

77

03

/3AL 88893 CAAA

112

112

7.2.4 Security Profiles

Before set up security feature you have to choose the security profile. 1350 MS security provides two pro-files base and advanced with two levels each one. Both of them set up HP Trusted System, and removethe useless network services, but the advanced provides the following feature more than base:

Table 6. Security Feature

Feature Base1 Base2 Adv1 Adv2

HP Trusted System set–up � � � �

Shell login banner � � � �

ftp login banner � � � �

Disable un–used network services � � � �

Disable remote command � �

Disable telnet � � � �

Deactivate NFS � � � �

Deactivate NIS � � � �

Disabling sendmail daemon � � � �

Predispose sendmail execution via cron � � � �

Disabling ftp real user access � � � �

Create Audit log file systems � �

Create security user � �

Enable rotation on system log files � �

Configure Audit � �

Disable XDMCP external access � �

7.2.5 Access to Secure Host

When the security is activate on host the telnet command is not more available, ssh (secure shell) mustbe used instead. If a profile of version 2 is configured also the ”r” commands (rlogin, rcp ...) are disabled,so ssh must be used for connection and scp (secure copy) to copy files.Secure Shell software is installed on all secure Alcatel 1350 MS systems, refer to to ssh and scp manpages for more information.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

78

03

/3AL 88893 CAAA

112

112

7.2.6 Define the System Password Configuration

One o the most evident difference in the system behavior when security is active is related to the password,in fact the 1350 MS security forces roles in password structure definition and aging. In the following tablesthe default values for both structure and aging:

Table 7. Security Password Structure Constants

Role Value Parameter

Minimum password length in characters 7 MIN_PASSWORD_LENGTH

Minimum number of numeric characters 1 PASSWORD_MIN_DIGIT_CHARS

Minimum number of special characters 1 PASSWORD_MIN_SPECIAL_CHARS

Number of changes before reuse the samepassword

4 PASSWORD_HISTORY_DEPTH

Table 8. Security Password Aging Parameters

Role Value Parameter

Expiration time (number of days) 180 PASSWORD_MAXDAYS

Minimum time interval between passwordchanges

0 PASSWORD_MINDAYS

Expiration warning time interval 14 PASSWORD_WARNDAYS

Grace period time 21 gptm

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

79

03

/3AL 88893 CAAA

112

112

7.3 Security Set–Up

When the security profile have been properly reviewed, and the banners have been customized, you canproceed in the security set–up.

7.3.1 Security in High Availability environment Restictions

For system where is present 1359HA OS–Cluster or OS–Resilience the 1350 security has to be set upat the same profile level on every system, the different password storage method cause serious problemswhen the security are not aligned.

7.3.2 Security Activation

1350 Security can be activated by entering the command “scsecurity” followed by the requested securityprofiles (see 7.2.4 at page 77 for feature list): base1, base2, advanced1 and advanced2.

7.3.2.1 Audit Filesystem creation

Meaningful for Advanced Profile Only

The security advanced set–up requires the creation of three new file systems:

1 ) /.ARCHIVE Archive file system where a compress copy of the log file are stored.

2 ) /.AUDITING/1 first audit filesystem

3 ) /.AUDITING/2 second audit filesystem

The filesystem creation is shown by following output:

NOTE: Entering Critical Code Execution. Security has disabled keyboard interrupts. Executing ”Archive log files” File System Configuration =>Tue Aug 2 17:11:38 METDST 2005 =>START: OSConf Extend/Create File(s) System ___________________________________________________________________________ Analyze Mount Point:”/.ARCHIVE”Request free MegaByte(s): 481Evaluate size MegaByte(s): 512Create Logical Volume x ”/.ARCHIVE”Extend Mount Point ”/.ARCHIVE” to 512 MByteMaking new file system (vxfs) on Mount Point ”/.ARCHIVE”Mount /dev/vg00/lvol17 on /.ARCHIVEUpdating /etc/fstab x Mount Point ”/.ARCHIVE”___________________________________________________________________________

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

80

03

/3AL 88893 CAAA

112

112

___________________________________________________________________________ Analyze Mount Point:”/.AUDITING/1”Request free MegaByte(s): 29Evaluate size MegaByte(s): 32Create Logical Volume x ”/.AUDITING/1”Making new file system (vxfs) on Mount Point ”/.AUDITING/1”Mount /dev/vg00/lvol18 on /.AUDITING/1Updating /etc/fstab x Mount Point ”/.AUDITING/1”______________________________________________________________________________________________________________________________________________________ Analyze Mount Point:”/.AUDITING/2”Request free MegaByte(s): 29Evaluate size MegaByte(s): 32Create Logical Volume x ”/.AUDITING/2”Making new file system (vxfs) on Mount Point ”/.AUDITING/2”Mount /dev/vg00/lvol19 on /.AUDITING/2Updating /etc/fstab x Mount Point ”/.AUDITING/2”___________________________________________________________________________

7.3.3 Required Software Installation

Meaningful for both Base and Advance Profiles.

Each time the 1350 security script is activated for setting up a profile, it looks at the required software, ifat least a software is missed, the script activates the automatic installation.

N.B. If the software installation requires system reboot, the set up has to be execute again.

First of all, the procedure checks the disk space availability within the interested filesystems. It it is notenough the procedure tries to extend them, rarely the procedure can ask for adding one or more harddisks. If any process prevent the filesystem extension, the procedure will ask you to reboot the system,in this case the software installation will be done automatically during the system reboot, like “scmana-geswp”.

When the procedure completes the installation you have to execute again the security set–up, to reallyset–up the secure environment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

81

03

/3AL 88893 CAAA

112

112

7.3.3.1 Software Installation example

This paragraph provides an example of base1 profile security set–up output.

When the procedure starts, it verifies the amount of filesystem free space:

___________________________________________________________________________Analyze Mount Point:”/opt”Request free MegaByte(s): 23Mount Point ”/opt”do not need extension, Free size available is 233 MByte______________________________________________________________________________________________________________________________________________________Analyze Mount Point:”/usr”Request free MegaByte(s): 1Mount Point ”/usr”do not need extension, Free size available is 69 MByte______________________________________________________________________________________________________________________________________________________Analyze Mount Point:”/var”Request free MegaByte(s): 4Mount Point ”/var”do not need extension, Free size available is 171 MByte

=>Sat Jun 11 16:53:05 METDST 2005 =>END: OSConf Extend/Create File(s) System

The it advice the possibility of reboot due to the software installation:

WARNING: One of the security software selected for the installation, it will require the system REBOOT. NOTE: if you decide to continue the system will automatically reboot and when the system come up you have to run again thisprocedure, otherwise the procedure will be aborted.Do you like to continue ? [yes|no]

N.B. This message is just an advise, the software installation does not always require reboot,but it is better to plan it.

Reply “yes[Enter]” when the reboot is possible.

ATTENTION: You have accepted to REBOOT the system ! Are you sure ?Do you like to continue ? [yes|no]

Another message is issued to be sure of the answer, reply “yes[Enter]” again when the reboot is possible,then press [Enter] to acknowledge the software predisposal activation message:

SOFTWARE predisposition activated ... Now you have to specify where are stored the LAYERED PRODUCTS. Press [Enter] to continue.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

82

03

/3AL 88893 CAAA

112

112

You have to provide the OS–Conf software distribution kit location replying, the same questions issuedby the NMS predisposition procedure:

––––––––––––– LAYERED PRODUCTS Repository ––––––––––– 1 – CDROM 2 – DEPOT Insert choice and press [Enter]:

Depending by you answer, you have to reply with the network depot location or confirm the CD driver, andthen installation will start issuing a report like the following:

Checking Depot presence ... Predisposed installation for product: BastillePredisposed installation for product: SecureShellPredisposed installation for product: KRNG11iPredisposed installation for product: ixSudoPredisposed installation for product: logrotateSOFTWARE predisposition was successful.Started installation of the security software... Alcatel Installation : Processing B6849AA B.02.01.01 Alcatel Installation : Processing T1471AA A.03.71.000 Alcatel Installation : Processing KRNG11i B.11.11.07

If the machine reboots, you have to enter again the scsecurity set–up command.

7.3.3.2 Creation of Security User

Meaningful for Advanced Profile Only

Just for security advanced profile the procedure creates the security user. This user is allow to managewith the HP Trusted System password database, without permissions on root user password.The procedure issues a message like the following for asking to define the security user password:

=>Tue Aug 2 17:12:05 METDST 2005 =>END: OSConf Extend/Create File(s) System Checking Security Software...Software already installed.Executing Security User ConfigurationWARNING: home directory ’/home/security’ already defined. Owner and group for the directory and all files and subdirect... in the file hierarchy below it will be changed.Directory ’/home/security’ old–user=199 old–group=securityExecuting ’security’ user creationDefine password for user ’security’Changing password for securityAt the request of new password you have to enter a password useful for security administrator, the pass-word have to be defined in agreement with the current password definition roles:New password:Re–enter new password:

The password is accepted on when this message is issued: Password successfully changed

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

83

03

/3AL 88893 CAAA

112

112

7.3.4 Security set up Execution

The last activity is the real security set–up. Hereafter an example of the output produced:

NOTE: ”ftp banner file” has been created: /etc/ftpd/ftp_banner Please, review/replace the contents of this file to apply more specifically to your organization.NOTE: Entering Critical Code Execution. Bastille has disabled keyboard interrupts.NOTE: Bastille is scanning the system configuration...Bastille is now locking down your system in accordance with youranswers in the ”config” file. Please be patient as some modulesmay take a number of minutes, depending on the speed of your machine.Executing File Permissions Specific ConfigurationExecuting Account Security Specific ConfigurationExecuting Inetd Specific ConfigurationExecuting Daemon Specific ConfigurationExecuting Sendmail Specific ConfigurationExecuting DNS Specific ConfigurationExecuting Apache Specific ConfigurationExecuting FTP Specific ConfigurationExecuting HP–UX’s Security Patch Check ConfigurationExecuting IPFilter Configuration

Please check/var/opt/sec_mgmt/bastille/TODO.txtfor further instructions on how to secure your system. Executing Login Banners Configuration

NOTE: ”issue login message file” exists: /etc/issue Please, review its contents adding an ”Authorized Use Only” warning message.NOTE: ”message of the day file” has been created: /etc/motd Please, review/replace the contents of this file to apply more specifically to your organization.

warning: commands will be executed using /usr/bin/shwarning: commands will be executed using /usr/bin/shSetting Security DefaultsUpdating Password SettingsExecuting Accounting ConfigurationAccounting started

Executing Auditing Configurationwarning: commands will be executed using /usr/bin/shwarning: commands will be executed using /usr/bin/shwarning: commands will be executed using /usr/bin/sh

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

84

03

/3AL 88893 CAAA

112

112

HP–UX Secure Shell stoppedHP–UX Secure Shell startedwarning: commands will be executed using /usr/bin/shwarning: commands will be executed using /usr/bin/shATTENTION:’scsecurity’ should be rerun whenever new software, OS revisions or patches are installed. It should also be rerun any time customizations are made that might loosen security.NOTE: Running ’scsecurity revert’ will revert the security changes, but it may not revert changes made in the interim (manually or by programs). In case of differences a copy of the modified files will be kept so that you can compare them.Security Setup ended.

When the procedure is completed verify /var/opt/sec_mgmt/bastille/TODO.txt file contents, in the file Bas-tille writes the processes running related to TCP/IP services that has been closed, them will be no morestarted at the next reboot, but if you want to guarantee the higher security level you have to look at thefile contents, and identify these processes. The process names are usually shown between two dash lines,see the following TODO.txt example:

{Thu Aug 11 16:51:59 2005}–––––––––––––––––––––––––––––––––––––––Deactivating Inetd Service: rtools–––––––––––––––––––––––––––––––––––––––The following process(es) are associated with the inetd service ”rtools”.They are most likely associated with a session which was initiated prior torunning Bastille. To disable a process see ”kill(1)” man pages or rebootthe systemActive Processes:################################### rlogind################################### {Thu Aug 11 16:51:59 2005}–––––––––––––––––––––––––––––––––––––––Deactivating Inetd Service: bootps–––––––––––––––––––––––––––––––––––––––The following process(es) are associated with the inetd service ”bootps”.They are most likely associated with a session which was initiated prior torunning Bastille. To disable a process see ”kill(1)” man pages or rebootthe systemActive Processes:################################### bootpd###################################

Then execute the following procedure:

a ) Login the system as root on system console or via Secure Shell, if you are connected in a differentway executing the procedure you can kill your own login session.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

85

03

/3AL 88893 CAAA

112

112

b ) Identify the process identifier by entering:...,sys,root # UNIX95= ps –C <process name>[Enter]

Where <process name> have to be replaced with the process name between dush lines (ex.:bootpd).

c ) Get the process identifiers from the PID column of the prevoius commnad output.

d ) for each PID enter the command:...,sys,root# kill –15 <PID>[Enter]

Where <PID> have to be replaced with the process identifiers issued by the command at point b ).

e ) Repeat the points: b ), c ) and d ) for each process shown in the TODO.txt file.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

86

03

/3AL 88893 CAAA

112

112

7.4 Remove Security

At any time you can remove1350 security set–up entering the command:...,sys,root #scsecurity revert [Enter]

This command restore the system as it was before the security set up.

If any changes to the system were made in the interim (either manually or by other programs), thosechanges should be reviewed again to make sure they still work and have not broken the system or compro-mised its security. In case of changes the involved items will be listed.

7.5 Change Security Profile

To change the security profile you must revert the system to any security profile and set up the new one.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

87

03

/3AL 88893 CAAA

112

112

8 PRINTER CONFIGURATION

To configure the printer you have to use hp� hppi script. This script configures the printer on the systemin order to allow the download of the software through the network, and also configures the spooler andthe printer queues on all the system declared.

This instaction is useful only for HP Printers.

In this chapter two printer configuration aspects are considered. First case how to configure a printer spoolqueue within the local spooler. The second one how to configure a printer to retrieve its configuration fromlocal machine.

To be able to perform the printer configuration you must know some information

Item Data Description Queue Boot

Name Name is the up to 8 charac-ters string assigned toprinter by Customer Net-work administrator(1).

� �

IP Address IP Address is the IP net-work address assigned toprinter by Customer Net-work administrator.

� �

Default Queue � Yes � No Is this the system defaultqueue? (it is suggested toset the first defined queueas default)

�

Banner Page � Yes � No Would you like to issue thebanner page at the begin-ning of any print job?

�

LAN Hardware Address LAN HA is the card hard-ware address also knownas MAC(2).

�

Table 9. Printer Configuration Data Requested.

Notes:

1 ) It is advisable to declare the printer name as external node with scNMmng.

2 ) The LAN hardware addres have to be retrieved from the printer itself. Refer to the printer instal-lation guide and/or operator handbook to know how to get the hardware address. It is usuallyshown as six couple of hexadecimal figures column separted like: 00:30:6E:08:AF:6F

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

88

03

/3AL 88893 CAAA

112

112

8.1 Configure a Printer Queue within Local Spooler

This section shows how to configure a HP printer already active in you network. This is the most usefulhint to configure a network printer. The printer availble today can be configure from the font panel, and youjust need to create a spool queue.

To create the printer spool queue you have to log the system as root user. and enter “hppi” command:

..,sys,root # hppi [Enter] **************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** M A I N M E N U ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T ****************************************************************

1) Spooler Administration (super–user only)

2) JetDirect Configuration (super–user only) – TCP/IP configurable parameters

3) Diagnostics: – diagnose printing problems

?) Help q) Quit Please enter a selection (q – quit):Enter “1[Enter]” to select the “Spooler Administration item”. **************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** Spooler Administration ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T ****************************************************************

Spooler: 1) Add printer to local spooler 2) Delete printer from local spooler 3) Modify existing spooler queue(s) 4) Install New Model Script 5) Remove Model Script ?) Help q) Quit Please enter selection:Enter “1[Enter]” to add the printer to the local spooler.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

89

03

/3AL 88893 CAAA

112

112

If you have already declare the printer name in the /etc/hosts file, directly of via scNMmng you can enterthe printer node name, otherwise you have to enter the IP address. This second choice has the disadvan-tage that you have to review the printer configuration in case of printer IP address changes:

Enter the network printer name or IP address (q – quit): <name>|<IP Ad.>[Enter]

The latest model script can be downloaded from the web before creatingany queue. This can be done by enabling Realtime Model Script Update. TheRealtime Model Script Update can be Enabled/Disabled from the diagnosticsmenu.

Do not enable the Realtime Model Script Update by replying just [Enter] to the next question:

Do you want to Enable Realtime Model Script Update(0–Enable, default–Dis-able): [Enter]

In any case, the procedure continue as follow:

The following is a list of suggested parameter values for thisqueue. You may change any settings by selecting the correspondingnon–zero numbers. The values will be used to configure this queuewhen ’0’ is selected. To abort this configuration operation, press ’q’. Configurable Parameters: Current Settings–––––––––––––––––––––––– ––––––––––––––––

1) Lp destination (queue) name: [<Printername>_1]2) Status Log [(No Log)]3) Queue Class [(Not assigned)]4) Default Queue [NO] 5) Additional printer configuration...

Figure 3. Printer Characteriscs Menu

Select an item for change, or ’0’ to configure (q – quit): 1 [Enter]

Enter “1[Enter]” to change the LP queue name:

Currently used names:––––––––––––––––––––(no queues are configured)

Enter the lp destination name (default=<Printername>_1, q – quit):

Enter the name you want to assing to the queue followed by [Enter], usually is the printer name itsef.

The item shown in the “Current Settings” column will be updated and “Printer Characteriscs Menu”(Figure 3. ) will be issued again.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

90

03

/3AL 88893 CAAA

112

112

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


If you want to set the banner page issue, at the next “Printer Characteriscs Menu” (Figure 3. ) prompt enter“5[Enter]”.


The following submenu will be shown on the dispaly, enter “5[Enter]” again:

The following is a list of suggested parameter values for this printer.

To abort this operation, press ’q’.

Configurable Parameters: Current Settings–––––––––––––––––––––––– ––––––––––––––––

1) Model Script: [net_lj4x]2) Default Printing Language [AUTO]3) Job Recovery [ON]4) True End–of–Job [ON]5) Banner Page [OFF]6) PostScript Level [Level 1]

Select an item for change, or q when done: 5 [Enter]

The “Banner Page” current setting will be change from [OFF] to [ON] and the submenu issued again. Enter“q[Enter]” to leave the submenu.

Select an item for change, or q when done: q [Enter]

The “Printer Characteriscs Menu” (Figure 3. ) will be proposed again, enter “0[Enter]” to finally create theprinter queue.


Depending by the “System Spooler” status one of the one of the following messages will be issued:

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

When the spooler is running: Ready to shut down the spooler and configure the new print queue. The spooler will be running again after the configuration is done. WARNING: If there are jobs currently being printed, and the page count is enabled (i.e. when True End–of–Job is turned on), this shutdown and rerun of the spooler may result in incorrect page count.

If the spooler is running before enter “y[Enter]” check with “lpstat –t” command that there is no print jobqueued.

OK to continue? (y/n/q, default=y) y [Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

91

03

/3AL 88893 CAAA

112

112

If the spooler is not running the following message will be issued to remind you to start–up the spoolerto have the print queue operational (see 8.1.1 at page 92).

WARNING : The spooler is not running!To print, turn on the spooler (lpsched)

hppi returns to the “Spooler Adminstration menu”, enter “q[Enter]” two times to exit the procedure.

Finished adding ”<Printername>” to the spooler.

**************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** Spooler Administration ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T ****************************************************************

Spooler: 1) Add printer to local spooler 2) Delete printer from local spooler 3) Modify existing spooler queue(s) 4) Install New Model Script 5) Remove Model Script ?) Help q) Quit Please enter selection: q [Enter]

**************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** M A I N M E N U ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T ****************************************************************




?) Help q) Quit Please enter a selection (q – quit): q [Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

92

03

/3AL 88893 CAAA

112

112

8.1.1 Start the System Spooler

The hp–ux� system spooler is automatically started during at system start–up time only when there is atlist a print queue defined. When you define the first queue it is usually not running, so to allow the correctprint activities you have to munually start it by entering the follwoing command as “root” user:

..,sys,root # lpsched[Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

93

03

/3AL 88893 CAAA

112

112

8.2 Configure Printer Booting from Local System

This printer configuration allow to remotely load the printer configuration at printer power–on time. If youdecide to use this method it is advisable to choose two hp–ux� system configured to set–up the printers,and keep the two system database alligned.

To perform this job you have to log in the system as root and enter the command:

..,sys,root # hppi [Enter]





?) Help q) Quit

Please enter a selection (q – quit):

Enter “2[Enter]” to select the JetDirect configuration.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

94

03

/3AL 88893 CAAA

112

112

**************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** JetDirect Configuration Menu ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T **************************************************************** Printer Network Interface: 1) Create printer configuration in BOOTP/TFTP database 2) Remove printer configuration from BOOTP/TFTP 3) Check Bootp and TFTP operation (super–user only)

– OR –

Telnet Configure JetDirect: 4) Set IP Address locally (within your local subnet – router) 5) Open Telnet Session to JetDirect Card

?) Help Me Decide q) Quit Please enter selection:

Enter “1[Enter]” to create configure the printer for booting from this node.

You will be asked a series of questions. After all of the questions have been answered, the responses areused to create an /etc/bootptab entry, and an optional configuration file. This configuration file is retrievedby the network printer with TFTP after it receives the BOOTP response.

These responses apply to all questions: ”q” – returns you to the next higher level menu ”?” – prints help text <return> – skips optional parameters or selects the default value

Enter the printer’s LAN hardware address: <Mac Address> [Enter]

Enter the network printer name (q – quit): <Printer Name> [Enter]

Enter IP address: <IP Address> [Enter]

Add <Printer Name> and <IP Address> to /etc/hosts? (y/n/q, default=y): y[Enter]

Printer name and IP address have been added to /etc/hosts. If your /etc/hosts file is updated automatically from a master source, add the name andIP address to your master source after the configuration is complete.

Following are optional parameters you may set for JetDirect. Select anynon–zero numbers to make the changes. The settings are used to create aBOOTP/TFTP database when ’0’ is selected. To abort the operation, press’q’

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

95

03

/3AL 88893 CAAA

112

112

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


Enter the printer location (q – quit): <Location name> [Enter]

...

Select an item for change, or ’0’ to configure (q – quit): 0 [Enter](configuring) ...

Completed creating BOOTP/TFTP configuration database for <Printer Name>.

Tftp service is also used to boot up JetDirect. Make sure /var/adm/in-etd.sec allows JetDirect’s IP to accesstftp service on this node.

Please wait...(testing, please wait) ...Testing BOOTP with 080009000000...: RESULT: Passed BOOTP test 1 with 080009000000....... BOOTP/TFTP has been verified functional.

Configuration data is now in place. The next test is to ping theprinter for the IP name you just assigned it. To continue the test,you MUST do the following so that the printer can configure itselfwith the configuration data:

Power cycle the printer. (operator must do a power cycle : power off – power on)Wait until the printer finishes the self test. (Note: It may take 20 sec to 1 min for a token ring HP JetDirect interface to finish the configuration.)Press the return key to continue the test.

If you are not ready for the next test (for example, the IP name hasnot taken affect in your DNS server), press ’q’ to return to the con-figuration menu now.

Do you want to send test file(s) to this printer (y/n, default=n)? y [Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

96

03

/3AL 88893 CAAA

112

112

This test is using test files to demonstrate that data bytes can betransmitted across the HP JetDirect interface setup. As long as a fewcharacters print out, the test is successful.The printer must be ready, i.e. online and not printing anything.The following types of test files can be sent to the printer: 1) text file (if printer is in PCL or AUTO mode) 2) PostScript file (if printer is in PS or AUTO mode) 3) HP–GL/2 file (if it is a HPGL/2 plotter) 4) User supplied file

Which one should be transmitted? (1/2/3/q, default=1) 2 [Enter]

===============================================================

Sending a test file to <Printer Name> ...

Result: The file has been successfully sent to <Printer Name>. Checkoutput!

===============================================================

Press the return key to continue ... [Enter]

**************************************************************** *****] **** **** ] **** JetDirect Printer Installer for UNIX **** ]]]]] ]]]]] **** Version E.10.18 **** ] ] ] ] **** **** ] ] ]]]]] **** JetDirect Configuration Menu ***** ] **** ****** ] **** User: (root) OS: (HP–UX B.11.11) I N V E N T ****************************************************************

Printer Network Interface: 1) Create printer configuration in BOOTP/TFTP database 2) Remove printer configuration from BOOTP/TFTP 3) Check Bootp and TFTP operation (super–user only)

– OR –

Telnet Configure JetDirect: 4) Set IP Address locally (within your local subnet – router) 5) Open Telnet Session to JetDirect Card

?) Help Me Decide q) Quit Please enter selection: q [Enter]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

97

03

/3AL 88893 CAAA

112

112





?) Help q) Quit Please enter a selection (q – quit): q [Enter]

..,sys,root #

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

98

03

/3AL 88893 CAAA

112

112

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

99

03

/3AL 88893 CAAA

112

112

9 GSP & MP PROCESSORS CONFIGURATION

The HP9000 Server of the following classes are provided with Guardian Service Processor (GSP) or Man-agement Processor (MP), to be able to use the console you must use a local VT100 terminal or a PC witha VT100 terminal emulator.

The GSP can be configured to allow to use the console via LAN, moreover the GSP rev B provides alsothe Web Console function.

N.B. If you use a PC with the VT100 terminal emulator you must have a RS232 9–24 pin male/malecable adapter.

9.1 Configure Guardian Service Processor

9.1.1 Access the GSP with Local Terminal or PC.

To configure the GSP LAN console you must have the following information available:

a ) An IP address for the GSPb ) An hostname for GSPc ) The subnetmaskd ) The IP address of the gateway

Optional data requested:

a ) Username for GSP administratorb ) Password for GSP administrator

Connect a terminal (or PC) to the console serial port and enter the GSP pressing [Ctrl]+b keys.

You’ll see the following message:

Leaving Console Mode–you may lose write access. When Console Mode returns, type ^Ecf to get console write accessPress [Enter]GSP replays with:

[Read only – use ^Ecf for console write access.]

Enter [Ctrl]+E then c f to get to the GSP prompt (some times it does not succeed, please try it again).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

100

03

/3AL 88893 CAAA

112

112

9.1.2 Configure GSP LAN console

The output provided in the following are related to a GSP rev A, that means the output of theGSP rev B can be different.

At GSP prompt (GSP>) enter the command: lc [Enter]This command allows you to modify the LAN configuration.Current configuration:

MAC Address : 0x00306e0860d4IP Address : 127.0.0.1GSP Host Name: uninitializedSubnet Mask : 255.255.255.0Gateway : 127.0.0.1Do you want to modify the LAN configuration? (Y/[N]) y [Enter]

Answer “y” to change the GSP LAN configuration.

GSP will show you the current IP address configured asking you to change: Current IP Address: 127.0.0.1 Do you want to modify it? (Y/[N]) y [Enter]

Answer “y” to change.

Then it will ask you for the GAP IP address: Enter new IP Address: <GAP LAN IP address> [Enter]

Enter the GSP LAN IP address followed by [Enter].

GSP will issues the following message requesting you to confirm you data entry: New IP Address: < GAP LAN IP address> Confirm? (Y/[N]): y [Enter] * IP Address will be updated.

Enter “y [Enter]” if the IP address is correct and go on.

The same method will be used by GSP to modify the hostname, subnetmask and gateway:

Current GSP Host Name: uninitialized Do you want to modify it? (Y/[N]) y [Enter]y Enter new GSP Host Name:<hostname> [Enter]<hostname> New GSP Host Name: <hostname> Confirm? (Y/[N]): y [Enter]y –> GSP Host Name will be updated. Current Subnet Mask: 255.255.255.0 Do you want to modify it? (Y/[N]) y [Enter]y

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

101

03

/3AL 88893 CAAA

112

112

Enter new Subnet Mask: <subnet mask><subnet mask> New Subnet Mask: <subnet mask> Confirm? (Y/[N]): y [Enter]y –> Subnet Mask will be updated. Current Gateway: 127.0.0.1 Do you want to modify it?(Y/[N])(Default will be IP Address) y [Enter]y Enter new Gateway: <gateway IP address> [Enter]<gateway IP address> New Gateway: <gateway IP address> Confirm? (Y/[N]): y [Enter]y –> Gateway will be updated. –> Settings have been updated. GSP>

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

102

03

/3AL 88893 CAAA

112

112

9.1.3 Define the Administrator User

Now you have to define a use profile for the GSP administrator in order to allow the GSP access to autho-rized people only:

The GSP user can manage with “reset” and “power management” command, that means themcan switch off the server from remote site!

At GSP prompt enter the command: so [Enter]GSP> so

SO

This command allow you to modify the security options and access con-trol.

GSP wide parameters are: . Login Timeout: 1 minutes. . Number of Password Faults allowed: 3 . Flow Control Timeout: 5 minutes.

Answer “n” on the GSP wide parameter modification request:Do you want to modify the GSP wide parameters? (Y/[N]) n [Enter]

GSP shows you the first user profile, that usually has all field empty, access level operator and user statedisable. GSP shows the user profile issuing:

User number 1 parameters are: . User’s Name: . User’s Login: . Organization’s Name: . Dial–back configuration: Disabled . Access Level: Operator . Mode: Single . User’s state: Disabled

At the modify request answer with “y”:Do you want to modify the user number 1 parameters? (Y/[N]/Q to quit) y[Enter]

Then you have to enter the name of the user (ex: John Smith) ( if it is not defined we suggest root): Current User’s Name: Enter new User’s Name: root [Enter]root New User’s Name: root Confirm? (Y/[N]): y [Enter]y –> User’s Name will be updated.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

103

03

/3AL 88893 CAAA

112

112

It is not necessary to set the Organization name: Current Organization’s Name: Do you want to modify it? (Y/[N]) n [Enter]rn

Enter the user name for the login (we suggest root): Enter new Login: root [Enter]root Enter new Login for confirmation: rootroot –> Login will be updated.

Now you have to enter the password for the administrator user:

N.B. The password will be not shown! Do you want to modify the current password? (Y/[N]) y [Enter]y Enter new Password: Enter new Password for confirmation: –> Password will be updated.

Do not enable the Dial–back option: Current Dial–back configuration: Disabled Do you want to modify it? (Y/[N]) n [Enter]n

Change the default User Access from operator to administrator: Current Access Level: Operator Do you want to modify it? (Y/[N]) y [Enter]y Enter new Access Level (Operator / Administrator):A [Enter]A New Access Level: Administrator Confirm? (Y/[N]): y [Enter]y –> Access Level will be updated.

Change the current mode of the user from Single to Multiple by: Current Mode: Single Do you want to modify it? (Y/[N]) y [Enter] Enter new Mode (Single / Multiple): M [Enter]m New Mode: Multiple Confirm? (Y/[N]): y [Enter]y –> Mode will be updated.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

104

03

/3AL 88893 CAAA

112

112

Enable the user to complete the user definition: Current User’s state: Disabled

Do you want to modify it? (Y/[N]) y [Enter]y Enter new User’s state (Enabled / Disabled): E [Enter]e New User’s state: Enabled Confirm? (Y/[N]): y [Enter]y –> User’s state will be updated.

Then GSP shows you the second user profile, it is not required to set up also it, so enter “q” to quit:User number 2 parameters are: . User’s Name: . User’s Login: . Organization’s Name: . Dial–back configuration: Disabled . Access Level: Operator . Mode: Single . User’s state: Disabled

Do you want to modify the user number 2 parameters? (Y/[N]/Q to quit) q[Enter]

–> Settings have been updated.User may be disconnected in this process

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

105

03

/3AL 88893 CAAA

112

112

9.1.4 Enable the Access via LAN

Now the access to the console via LAN can be authorize, by entering the command “el” as shown int thefollowing example:

GSP> el [Enter]

Current LAN port access: Disabled

Do you want to modify this configuration? (Y/[N]) y [Enter]

LAN port access options:

On GSP rev A: [A] All access enabled [D] All access disabled

On GSP rev B: [A] All access enabled – both Telnet and Web [D] Disable LAN port – prevent Telnet and Web access [T] Telnet only enabled [W] Web only enabled

In any casePlease indicate the new mode for the LAN port,or <CR> to retain current value. Choose one of (...): A [Enter]

New LAN port access settings will be: Enabled

Confirm? (Y/[N]): y [Enter]

Current LAN port access: Enabled

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

106

03

/3AL 88893 CAAA

112

112

9.1.5 Check the GSP LAN Console Accessibility

It is advisable to check the GSP LAN Console accessibility trying to connect it with a telnet connection froma PC or HP–UX system.

N.B. The behavior of the GSP depend by the last connection, so the example can be different thanwhat you will see.

Example:....,sys,root # telnet <IP address GSP> [Enter] Trying...Connected to .......Escape character is ’^]’.Local flow control off

Service Processor login: rootService Processor password:

Hewlett–Packard Guardian Service Processor

9000/800/L1000–36 System Name:

[Enter] [Read only – use Êcf for console write access.][Ctrl]+E c f[bumped user – ][Ctrl]+BLeaving Console Mode – you may lose write access.When Console Mode returns, type Êcf to get console write access. GSP>

The test is OK just if you are able to login.

To close the connection press [Ctrl]+] (Control key +, and type “close [Enter] ” at “telnet>” prompt.

9.1.6 How to get to the GSP Console

To get in console mode at GSP prompt type: co [Enter]GSP> co [Enter]

Leaving Guardian Service Processor Command Interface and enteringConsole mode. Type Ctrl–B to reactivate the GSP Command Interface.

[Enter] [Read only – use Êcf for console write access.][Ctrl]+E c f[bumped user – ][Enter] GenericSysName [HP Release B.11.00] (see /etc/issue)Console Login:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

107

03

/3AL 88893 CAAA

112

112

9.2 Configure Management Process

This paragraph show only the minimum configuration for the Management Processor (MP) provided withone of the following HP9000 9000 servers: rp7410, rp3410, rp3440 and rp4440.

9.2.1 Access the MP with Local Terminal or PC.

Like to GSP configuration MP must requires the following information available:

a ) An IP address for the MPb ) An hostname for MPc ) The subnetmaskd ) The IP address of the gateway

Connect a terminal (or PC) to the console serial port RS–232 and enter the MP pressing [Enter] key, ithave t reply requesting the Login and password:

MP login: MP password:

Both of them are initialized to “Admin”, entering them the MP shows you some information about the MPitself and the Main menu:

Welcome to the rp7410 Management Processor (c) Copyright 1995–2002 Hewlett–Packard Co., All Rights Reserved. Version 3.05 MP MAIN MENU: CO: Consoles VFP: Virtual Front Panel (partition status) CM: Command Menu CL: Console Logs SL: Show chassis Logs HE: Help X: Exit Connection MP>

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

108

03

/3AL 88893 CAAA

112

112

9.2.2 Configure Lan Console

The minimum configuration consists of the lan parameter set–up, if you want more information about howto use MP the “HE” command can provide a breaf explanation, for specific management realted to thehardware partitioning please refer to “HP System Partitions Guide” [4] at page 8.

Enter the command “CM” to get into the Command Memu:

MP> CM

It replays with “MP: CM >” prompt:

Enter HE to get a list of available commandsMP:CM>

To configure the lan interface you have to enter the command “LC” (Lanc Console).

MP:CM> LC This command modifies the LAN parameters. Current configuration of MP LAN interface MAC address : 00:30:6e:38:b2:d0 IP address : 127.0.0.1 (0xef000001) Hostname : notdefined Subnet mask : 255.0.0.0 (0xff000000) Gateway : 0.0.0.0 (0x00000000) Status : UP and RUNNING AutoNegotiate : Enabled Data Rate : 10 Mb/s Duplex : Half Error Count : 46 Last Error : rx FIFO overflow

The command shows the current lan configuration, then it starts to issue some questions to allow you tochange any one of them.

The first question is related to if you want to modify the Lan Console configuration reply “y” to the question:

Do you want to modify the configuration for the customer LAN?(Y/[N]) y[Enter]

The lan console condifugration asks you to change the IP Address:

Current IP Address is: 127.0.0.1 Do you want to modify it? (Y/[N]) y[Enter] Enter new IP Address : <New IP Address> [Enter] New IP Address will be: .... Please confirm (Y/[N]) y[Enter]

–> IP Address will be updated.

Then it provides you the current hostname assigned to the MP:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

109

03

/3AL 88893 CAAA

112

112

Current MP Network Name is: notdefined Do you want to modify it? (Y/[N]) y[Enter] Enter new MP Network Name : <New MP hostname> New MP Network Name will be: ... Please confirm (Y/[N]) y[Enter]

–> MP Network Name will be updated.

The next step is to change the Subnet mask:

Current Subnet Mask is: 255.0.0.0 Do you want to modify it? (Y/[N]) y[Enter] Enter new Subnet Mask : <New Subnet Mask> New Subnet Mask will be: .... Please confirm (Y/[N]) y[Enter]

–> Subnet Mask will be updated.

The last question ragards the Gateway:

Current Gateway is: 0.0.0.0 Do you want to modify it? (Y/[N]) (Default will be IP address.) y[Enter] Enter new Gateway : < New Gateway IP Address> New Gateway will be: .... Please confirm (Y/[N]) y[Enter]

–> Gateway will be updated.

And the terminates issuing the message, followed by the prompt:

–> Parameters have been updated.MP:CM>

It is advisable to check the connecion via telnet from another system, if it fails check if the Lan ConsoleAccess is enabled with the “EL” commnad.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

110

03

/3AL 88893 CAAA

112

112

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

111

03

/3AL 88893 CAAA

112

112

APPENDIX A FILE EXAMPLES

This appendix provides some configuration file examples.

A.1 security.params

# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––# Copyright (c) 2004 by Alcatel Telecom. All rights reserved.# ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––## YOU CAN MAKE CHANGES UNDER THIS LINE # Users advised against problems#WARN_USERS_LIST=”root” ## List of users separated by blank # Parameters for UN–Trusted Systems (SECURITY)#PASSWORD_MAXDAYS=180 ## Password expiration time interval (days)## ATTENTION: IF THE VALUE OF THE NEXT VARIABLE IS CHANGED YOU SHOULD HAVEPROBLEMS IN# PASSWORD CHANGING. IT IS RECOMMENDED TO KEEP PASSWORD_MIN-DAYS=0PASSWORD_MINDAYS=0 ## Minimum time interval between passwordchanges (days)PASSWORD_WARNDAYS=14 ## Password expiration warning timeinterval (days) PASSWORD_HISTORY_DEPTH=4 ## Password history depthPASSWORD_MIN_DIGIT_CHARS=1 ## Password minimum digit charactersPASSWORD_MIN_SPECIAL_CHARS=1 ## Password minimum special charactersMIN_PASSWORD_LENGTH=7 ## Minimum password length## end of UN–Trusted System parameters # Parameters for Trusted Systems#usrpick=YES ## User picks passwordsyspnpw=NO ## System does not generate pronounceable..rstrpw=YES ## Check password for trivialitynullpw=NO ## Null passwords are not allowedsyschpw=NO ## System does not generate passwords ha...sysltpw=NO ## System does not generate passwords ha...#mintm=PASSWORD_MINDAYS ## ##From SECURITY###exptm=PASSWORD_MAXDAYS ## ##From SECURITY##gptm=21 ## Grace period time (days)llog=0 ## Last login time interval (days)#expwarn=PASSWORD_WARNDAYS ## ##From SECURITY##umaxlntr=–1 ## Maximum number of consecutive unsuces...tmaxlntr=3 ## Maximum unsuccessful login tries allo...dlylntr=2 ## Delay between login trieslntmout=30 ## Login timeout in seconds

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

112

03

/3AL 88893 CAAA

112

112

## End of Trusted System parameters # Auditing# # ATTENTION: # DO NOT CHANGE BELOW THIS LINE AFTER THE FIRST APPLY OF THE SECURITYPRI_SWITCH=24576 ## Switch size of primary audit log file (kbytes)SEC_SWITCH=24576 ## Switch size of secondary audit log file (kbytes)

END OF DOCUMENT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 1

03

RELEASED

/3AL 88893 CAAA

4

4

LABELS AND ASSEMBLY INSTRUCTIONSTARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA

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

COD.MANUALE HDBK P/N: 3AL 88893 CAAA Ed.031350 Management Suite1350 Rel.7.1NR7.1 ADMINISTRATION GUIDE

ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)

– No PAGINE TOTALI PER ARCHIVIAZIONE: 114+4=118– DIMENSIONE BINDER SORGENTE (du –ks): 3.511 Kbytes

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:HANDBOOK COMPOSITION AND ASSEMBLY:

SERVONO 5 BUSTE TRASPARENTI (Es.Cod.854.010.051 H)FIVE TRANSPARENT PLASTIC ENVELOPES ARE NECESSARY

No pagine(facciate)

numeratenumbered(facciate)

No pages da from a to

TARGHETTE - LABELS

frontespiziofront

2

3AL 88893 CAAA Ed.03 manualemanual

112 1/112 112/112

INSERIRE LE 5 BUSTE TRASPARENTIINSERT FIVE TRANSPARENT PLASTIC ENVELOPES

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 114

TOTALE FOGLI A4 TOTAL A4 SHEETS: 57

WARNING FOR A-UNITS OTHER THAN A-ITALY

• Labels are done according to A-Italy binder format.• Source files: ALICE 6.10 ARCHIVED BY GAPI 4.1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 2

03

RELEASED

/3AL 88893 CAAA

4

4

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

Site

Originators

:

Domain

1350 NR7.1

Division

NR 7.1

Rubric

ADMINISTRATION GUIDE

TypeDistribution Codes Internal External

::::

ONDNM1350

:

B.BosisioS.Franco

Approvals

NameApp.

App.Name

F.Casasole

INFORMAZIONI EDITORIALI

– ORIGINALE SU FILE: ALICE 6.10• sistemazione ’figlist’

3AL 88893 CAAAEd.031350 Management Suite1350 Rel.7.1NR7.1

Network ReleaseADMINISTRATION GUIDE

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 3

03

RELEASED

/3AL 88893 CAAA

4

4

1350 Management Suite


NR7.1

ADMINISTRATION GUIDE


VOL.1/1

1350 Management Suite


NR7.1

ADMINISTRATION GUIDE 3AL 88893 CAAA Ed.03

VOL.1/1

1350 Management Suite1350 Rel.7.1Network Release

NR7.1 3AL 88893 CAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1

1350 Management Suite 1350 Rel.7.1Network Release

NR7.1 3AL 88893 CAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1

1350 Management Suite1350 Rel.7.1Network Release

NR7.1

3AL 88893 CAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 4

03

RELEASED

/3AL 88893 CAAA

4

4

FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT