Evolium A9135 MFS Maintenance Handbook

Alcatel BSS

Evolium A9135 MFS Maintenance

Handbook

MFS Document

Procedural Handbook

Release B9

3BK 20935 AAAA PCZZA Ed.20

Status RELEASED

Short title MFS Maint Hdbk

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.

BLANK PAGE BREAK

2 / 176 3BK 20935 AAAA PCZZA Ed.20

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Safety Rules and Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 Front View of the MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2 MFS Interconnexions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3 Safety Rules for Equipment Under Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.3.1 Conductive Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.2 Mobile Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.3 Uncommon Replacements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4 Electrostatic Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.1 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.2 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.3 Transportation and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.4.4 Components and PBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Maintain the BSXTU1 Telecommunications Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.1.1 Impact on System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.2 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.3 The BSXTU1 Telecommunications Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.2 Fan Tray (BDAFU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.1 Remove BDAFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2.2 Insert New BDAFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.3 Front RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3.1 BE35B2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.2 JBETI or JBGPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4 Rear RITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.4.1 BA35B2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.4.2 BATTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.4.3 JAETI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.4.4 JAE1 or JAE1C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.4.5 BAREDC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3 Maintain the JSHUB Hub/Switch Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.1.1 Impact on System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.1.2 The JSHUB Hub/Switch Subrack* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2 JAHPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.2.1 Remove JAHPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.2.2 Insert New JAHPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.3 Super Stack II Hub 500 (HUB500)* / Super Stack Baseline 10/100 Switch (SWITCH) . . . . 323.3.1 Remove HUB500** or SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.2 Case: Insert New HUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.3 Case: Insert New SWITCH*** . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.4 IOLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.1 Remove IOLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.2 Insert New IOLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4 Maintain the AS800 Server Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.1.1 Impact on System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.1.2 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.1.3 The AS800 Server Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.2 Beep Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.3 System Backup for MFS AS800 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3BK 20935 AAAA PCZZA Ed.20 3 / 176

Contents

4.3.2 Back Up the Active Local Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.4 Restore the Standby Station of an MFS AS800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.5 Replace CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.5.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.5.2 Isolate a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.5.3 Replace CPU-Box Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.5.4 Install and Configure New CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.5.5 New Station Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.6 Replace PCI Board Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.6.1 Slide Out CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.6.2 Replace PCIBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.6.3 Insert CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.7 Replace 300W Converter (CNVR3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.7.1 Slide Out CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.7.2 Replace CNVR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.7.3 Slide in CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.8 Replace CD-ROM Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.8.1 Remove CD-ROM Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.8.2 Insert New CD-ROM Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.9 Replace a Shared Disk (9GBD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.9.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.9.2 Remove Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.9.3 Insert New Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.9.4 Recover the New Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.10 Replace a Local Hard Disk (9GBD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.10.1 Pre-load Backup Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.10.2 Replace Local Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.11 Replace 90W Converter (CNVR9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.11.1 Remove CNVR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.11.2 Insert New CNVR9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.12 Replace Main Fan Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.12.1 Remove MFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.12.2 Insert New MFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5 Maintain the DS10 Server Subrack (both DS10/RC23 and DS10/RC40) . . . . . . . . . . . . . . . . . . . . . . . 615.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.1.1 Impact on System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.2 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.3 Isolate a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.2 Replace SCSI Bus (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2.2 SCSI Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.2.3 Determine the Faulty SCSI Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.3 System Backup for MFS DS10 RC23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.3.2 Back up the Active Local Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.4 Restore the Standby Station of an MFS DS10 RC23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.5 System Backup for MFS DS10 RC40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.5.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.5.2 Back up the Active Local Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.6 Restore the Standby Station of an MFS DS10 RC40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.7 Replace DS10 Server (both DS10/RC23 and DS10/RC40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.7.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.7.2 Isolate a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.7.3 Replace Station Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.7.4 Install and Configure New Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.7.5 Start Up New Station* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

5.8 Replace StorageWorks Shelf (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4 / 176 3BK 20935 AAAA PCZZA Ed.20

Contents

5.9 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.9.1 Remove the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.9.2 Insert New Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.10 Replace a Shared Disk (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.10.1 Possible Other Failure Origins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.10.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.10.3 Remove Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865.10.4 Insert the New Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.11 Replace 180W Power Supply (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.12 LED Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

5.12.1 Remove 180W Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.12.2 Insert New 180W Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

5.13 Replace DAT Drive PVDAT01 (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.13.1 Remove PVDAT01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.13.2 Insert New PVDAT01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

5.14 Replace Blower (*) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.14.1 Remove Blower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.14.2 Insert New Blower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6 MFS Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6.1 Telecommunications Subrack Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.2 Station, Hub/Switch and IOLAN Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.3 External Cabling to AGPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7 Software Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

7.1 Initial Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107.1.2 Note the Synchronization Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.1.3 Backup NORIMFS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.1.4 UNIX, Nectar and MFS Software Installation for MFS with AS800 or DS10

RC23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.1.5 Automatic Software Installation (UNIX, NECTAR and MFS Software) for DS10

RC40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.1.6 Configure the MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.1.7 Download and Launch BUL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.1.8 Restart MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447.1.9 Restore the NORIMFS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457.1.10 Re-synchronize BSCs with MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

7.2 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497.2.1 Possible Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497.2.2 Configure IOLAN Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1497.2.3 Configure IMT on Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517.2.4 Configure IMT on Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

7.3 Change Configuration on Running MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557.3.1 Customize Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557.3.2 Configure IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1557.3.3 Configure Both Station on Running MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

7.4 NECTAR Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607.4.1 Locking Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607.4.2 Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

7.5 Miscellaneous tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627.5.1 Download New Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627.5.2 How to be connected on MFS control stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647.5.3 Install UNIX Patch using IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677.5.4 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677.5.5 SRM Hardware Settings for DS10 Local Disks (RC40) . . . . . . . . . . . . . . . . . . . . 1697.5.6 Rebuild Shared Disk Configuration - Install LSM (for RC23) . . . . . . . . . . . . . . . 1707.5.7 Rebuild Shared Disk Configuration - Install LSM (for RC40) . . . . . . . . . . . . . . . 174

3BK 20935 AAAA PCZZA Ed.20 5 / 176

Figures

FiguresFigure 1: Front View of a Typical MFS Equipped with the AS800 Server Subrack . . . . . . . . . . . . . . . . . . . . . . 14

Figure 2: Front View of a Typical MFS Equipped with the DS10 Server Subrack . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 3: MFS Interconnexions (with LCS Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 4: The BSXTU1 Telecommunications Subrack, Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 5: Front Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 6: Retaining Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 7: JAETI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 8: Front of the JSHUB Hub Subrack when Installed with an AS800 Server Subrack . . . . . . . . . . . . . 30

Figure 9: Front of the JSHUB Hub/Switch Subrack when Installed with a DS10 Server Subrack . . . . . . . . . 30

Figure 10: AS800: Super Stack II Hub 500s and IOLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 11: DS10: Super Stack II Hubs 500 / Super Stack Baseline 10/100 Switches . . . . . . . . . . . . . . . . . . . 33

Figure 12: IOLAN below AS800 Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 13: IOLAN below DS10 station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 14: The AS800 Server Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 15: Front Panel for AS800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 16: AS800 CPU-Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 17: PCI Board Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 18: 300W Converter (CNVR3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Figure 19: CD-ROM Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 20: Shared Hard Disc Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 21: Local Hard Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 22: 90W Converter (CNVR9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Figure 23: Main Fan Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Figure 24: SCSI Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 25: SCSI 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 26: SCSI 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 27: SCSI Connectors on DS10 CPU Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 28: SCSI Bus 1 Connectors on StorageWorks Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 29: SCSI Bus 2 Connectors on StorageWorks Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 30: DS10 Server Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 31: DS10 CPU Front View (both DS10/RC23 and DS10/RC40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 32: DS10 CPU Rear View (both DS10/RC23 and DS10/RC40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 33: DS10, Rear View, Cables Partly Disconnected (both DS10/RC23 and DS10/RC40) . . . . . . . . . . 76

Figure 34: DS10, Physical Replacement both DS10/RC23 and DS10/RC40). . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 35: The BA356 StorageWork Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 36: Pressing Bezel Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Figure 37: 180W Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 38: Blowers at Rear of SupplyWork Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Figure 39: MFS AS800 Rack Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6 / 176 3BK 20935 AAAA PCZZA Ed.20

Figures

Figure 40: MFS DS10 Rack Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Figure 41: Front View of BSXTU Telecomunications Subracks (same for AS 800 and DS 10) . . . . . . . . . . . 94

Figure 42: Back View of BSXTU Telecomunications Subracks (same for AS 800 and DS 10) . . . . . . . . . . . 94

Figure 43: JAETI Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Figure 44: DS10 Rear Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 45: SCSI Adaptor Cable and Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 46: HUB/SWITCH, Front Connectors (ALETHC cable allowed only for SWITCH) . . . . . . . . . . . . . . . 104

Figure 47: Hub, Rear Connectors (not possible if SWITCH are used) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Figure 48: IOLAN Rear Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Figure 49: Run Ethernet cables through Cable Gland . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Figure 50: Running the two Ethernet cables at lateral side of rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Figure 51: Configuration Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Figure 52: MFS networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Figure 53: On an AS800 machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Figure 54: On DS10 machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

3BK 20935 AAAA PCZZA Ed.20 7 / 176

Tables

TablesTable 1: CPU Diagnosis by Beep-Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 2: Shared Disk Diagnosis by LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table 3: Cable List of Rear RIT BA35B2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Table 4: Cable&Strap List of Rear RIT JAETI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Table 5: Cable List of Rear RIT BATTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Table 6: Cable List of RIT JAHPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Table 7: Cable List of Station, Hub/Switch and IOLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Table 8: Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Table 9: Required Operating System and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Table 10: Hardware Settings for SRM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Table 11: Required Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Table 12: Installation CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table 13: Required Operating System and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Table 14: BUL-Files Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Table 15: BUL-Files Loading I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Table 16: BUL-Files Loading II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Table 17: Hardware Settings for SRM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

8 / 176 3BK 20935 AAAA PCZZA Ed.20

Preface

Preface

Purpose This Maintenance Handbook describes how to replace units and cables in thesubracks and how to install, configure and change MFS software.

There are three types of maintenance related to the MFS:

Maintenance in case of hardware failure

Preventive maintenance for MFS RITs which are considered sensitive.

This includes checking the RITs and replacing them after pre-definedperiods of operation

Software maintenance.

What’s New In Edition 20Improvements were made in following sections due to system behavior:

Update Firmware (Section 7.1.4.3)

Automatic Installation (Section 7.1.5.7)

Update made in MFS Interconnexions (Section 1.2) due to system evolution.

In Edition 19Overall document quality was improved following an editorial review.

Section Replace DS10 Server (both DS10/RC23 and DS10/RC40) (Section5.7) — Prerequisites has been updated due to system evolution.

In Edition 18The following sections were modified due to system behaviour:

Prerequisites (Section 7.1.4.5)

Configure Network (Section 7.1.4.6)

In Edition 17Improvements were made in following sections due to system evolution :

Prerequisites (Section 7.1.4.1)

3BK 20935 AAAA PCZZA Ed.20 9 / 176

Preface

Checks and Updates (Section 7.1.4.2)

Configure Network (Section 7.1.4.6)

Install Licenses on Both Stations (AS800 only) (Section 7.1.4.7)

In Edition 16Section Prerequisites (Section 7.5.7.1)has been changed due to systembehavior.

In Edition 15Overall document quality was improved following an editorial review

In Edition 14Editorial update in section Configure the MFS (Section 7.3.3.3).

In the section Prerequisites (Section 7.5.7.1) the path were install_rc40_lsmscript can be find had been updated.

Improvements were made in section Replace DS10 Server (both DS10/RC23and DS10/RC40) (Section 5.7) and System Backup for MFS DS10 RC40(Section 5.5) following several system evolution changes.

Improvements were made in section Download and Launch BUL Files (Section7.1.7) due to system behaviour.

In Edition 13Document improvement following system evolution changes in sections Restorethe Standby Station of an MFS AS800 (Section 4.4), Restore the StandbyStation of an MFS DS10 RC23 (Section 5.4) and Restore the Standby Stationof an MFS DS10 RC40 (Section 5.6)

Document improvement following several changes in section Restore theStandby Station of an MFS DS10 RC40 (Section 5.6).Document improvement following system evolution changes in sections:

System Backup for MFS AS800 System (Section 4.3)

Restore the Standby Station of an MFS AS800 (Section 4.4)

System Backup for MFS DS10 RC23 (Section 5.3)

Restore the Standby Station of an MFS DS10 RC23 (Section 5.4)


Restore the Standby Station of an MFS DS10 RC40 (Section 5.6)Modifications were made in the following sections



Update for AuditMFS script in Restart MFS (Section 7.1.8)

Update for BUL file application in Download and Launch BUL Files (Section7.1.7).

In Edition 12

10 / 176 3BK 20935 AAAA PCZZA Ed.20

Preface

The section Initial Software Installation (Section 7.1) has been updated dueto system evolution.

Removal of Speclist in Checks and Updates (Section 7.1.4.2)

The following section has been updated Configure Network (Section 7.1.4.6)

In Edition 11Update for Expect program removal in Preparation for Nectar AutomaticInstallation (Section 7.1.5.5), confirmation messages in Installing UNIX OS andMFS (in section 7.1.5.7) and processes listing in Restart MFS (Section 7.1.8)

In Edition 10Restriction removal from section Restart MFS (Section 7.1.8).

Update for installation script in Automatic Software Installation (UNIX, NECTARand MFS Software) for DS10 RC40 (Section 7.1.5)

Introduction of a new section Rebuild Shared Disk Configuration - Install LSM(for RC40) (Section 7.5.7).

In Edition 09The name of the file that stores the OMC-R address has been updated insection Store Information (AS800 only) (in section 7.1.4.2).

In Edition 08Restriction introduction in Restart MFS (Section 7.1.8)

In Edition 07Restriction removal from Copy from FTP Server (Section 7.5.1.4)

In Edition 06Restriction introduction in Copy from FTP Server (Section 7.5.1.4)

In Edition 05Editorial update in System Backup for MFS DS10 RC40 (Section 5.5), RestartMFS (Section 7.1.8), Download and Launch BUL Files (Section 7.1.7) andAutomatic Installation (Section 7.1.5.7).

In Edition 04Update for NTP server script change in Configure the MFS (Section 7.1.6)

Update due to usage of ’mfs_inet’ script for configuration of STATION_Binstead of ’netsetup’ in UNIX, Nectar and MFS Software Installation for MFSwith AS800 or DS10 RC23 (Section 7.1.4)

In Edition 03Usage of ’mfs_addomc’ script for configuration of SNMP server in Configurethe MFS (Section 7.1.6)

New script is used to copy xml files under expect directory for RC40 inPreparation for Nectar Automatic Installation (Section 7.1.5.5). XML directoryupdated in Automatic Installation (Section 7.1.5.7)

3BK 20935 AAAA PCZZA Ed.20 11 / 176

Preface

New script used to to clear previous installation data from the local PC wasintroduced in Automatic Installation (Section 7.1.5.7)

Update for firmware performed in Automatic Software Installation (UNIX,NECTAR and MFS Software) for DS10 RC40 (Section 7.1.5), Replace DS10Server (both DS10/RC23 and DS10/RC40) (Section 5.7) and System Backupfor MFS DS10 RC40 (Section 5.5) .

Restriction on LCS introduced in MFS Interconnexions (Section 1.2).

In Edition 02Update with:

Control station DS10 RC40 in Automatic Software Installation (UNIX,

NECTAR and MFS Software) for DS10 RC40 (Section 7.1.5)

Rebuild Shared Disk Configuration - Install LSM (for RC23) (Section 7.5.6)

Improve the Automatic installation of MFS with DS10 RC40 with modification

of Windows XP firewall in Automatic Installation (Section 7.1.5.7)

Improve the section Initial Software Installation (Section 7.1)by adding twonew steps:Backup NORIMFS file (Section 7.1.3) andRestore the NORIMFS

File (Section 7.1.9)

Editorial improvement for:Replace DS10 Server (both DS10/RC23 andDS10/RC40) (Section 5.7), Restart MFS (Section 7.1.8)

In Edition 01Update in Restart MFS (Section 7.1.8), due to :

“Security improvements for IP Network Elements (MFS)”

“Supervision of CPU, memory and disks of MFS from OMC-R”Other improvements due to system evolution in the following sections:

Install MFS Software (Section 7.1.4.10)

Configure the MFS (Section 7.1.6)

Download and Launch BUL Files (Section 7.1.7).

Audience This Maintenance Handbook is intended for:

Maintenance engineers

System support engineers

Network technicians

Network operators.

Assumed Knowledge You must have a basic understanding of the following:

Alcatel operations and maintenance concepts for the MFS

MFS hardware configurations

Telecommunications engineering

Anti-static procedures

Windows and UNIX environment

12 / 176 3BK 20935 AAAA PCZZA Ed.20

1 Safety Rules and Precautions


This section contains the following information:

Front view of the MFS

Safety rules for equipment under power

Electrostatic precautions.

3BK 20935 AAAA PCZZA Ed.20 13 / 176


1.1 Front View of the MFS

Fan Trays BDAFU3

BE

35B

2

BE

35B

2

BE

35B

2

BE

35B

2

BE

35B

2 B

E35

B2

JBE

TI

JBE

TI

Em

pty

Em

pty

Em

pty

Em

pty

Em

pty

Em

pty

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

DC Connection − Circuit Breakers

Em

pty

TRU (Top Rack Unit)

TelecommunicationsBSXTU1 Subrack

AS800 ServerSubrack

Hub Subrack

BE

35B

2

BE

35B

2

Fan Trays PCIBF

Optional Telecommunications BSXTU1 Subrack

AS800 CPUB

AS800 CPUB

Local Disk9GBD

SharedDisk9GBD

LocalDisk9GBD

Empty

Empty Empty

EmptyCDROM CDROM

PowerUnit90PS

PowerUnit90PS

Empty

Optional HUB500

Optional HUB500

HUB500

HUB500

IOLAN

SharedDisk9GBD

Figure 1: Front View of a Typical MFS Equipped with the AS800 Server Subrack

Fan Trays PCIBF

Fan Trays BDAFU3

BE

35B

2

BE

35B

2

BE

35B

2

BE

35B

2

BE

35B

2

BE

35B

2

JBE

TI

JBE

TI

Em

pty

Em

pty

Em

pty

Em

pty

Em

pty

Em

pty

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

JBG

PU

2

Optional Telecommunications BSXTU1 Subrack

DC Connection − Circuit Breakers TRU (Top Rack Unit)

Telecom.BSXTU1 Subrack

Hub/Switch Subrack

Empty

BA356 Storage Workshelf


DS10

DS10

IOLAN

Opt

iona

l HU

B50

0 /

SW

ITC

H

Opt

iona

l HU

B50

0 /

SW

ITC

H

HU

B50

0 / S

WIT

CH

HU

B50

0 /

SW

ITC

H

DS10 Server Subrack

Figure 2: Front View of a Typical MFS Equipped with the DS10 Server Subrack

14 / 176 3BK 20935 AAAA PCZZA Ed.20


1.2 MFS Interconnexions

BTS

BTS BSC MSC

GMLC

HLR

SGSN

CBC

SMLC

MFS

Router A−GPSServer

MS

Lg

LgLh

LSN1 LSN2

LbInterface Gs

Interface

A Interface

Gb Interface

LCS Client

SAGI

Figure 3: MFS Interconnexions (with LCS Services)

1.3 Safety Rules for Equipment Under Power

Injury from EquipmentPossible death or serious physical harm to personnel and damage to equipmentmay result from mishandling.While performing any maintenance tasks or procedures, you must follow anylocal safety requirements, and those mentioned in this section.

For maintenance purposes, field operators may have to work on equipmentunder power (-48 VDC or -60 VDC). This means that it is possible to touchsome parts under power that are only protected by heavy fuses. Maintenanceactivities must be carried out carefully to avoid short circuits and to preventserious personal injury.

1.3.1 Conductive Objects

Remove all conductive objects from hands and arms such as rings,bracelets, metallic wrist watches or similar. Use appropriate insulated toolsfor maintenance activities.

1.3.2 Mobile Telephone

Do not use a mobile telephone when the MFS doors are open. It can interferewith the operation of the MFS.

3BK 20935 AAAA PCZZA Ed.20 15 / 176


1.3.3 Uncommon Replacements

Uncommon on-site replacements, for example, the BSXTU1Telecommunications Subrack Back panel BSXTU, the Top Rack Unit or theentire AS800 Server Subrack, must be requested specially.

Alcatel will perform a case-by-case study and, if necessary, prepare a specialreplacement procedure. Any such procedure is handled solely by Alcatel.

1.4 Electrostatic PrecautionsThe following electrostatic precautions must be observed:

1.4.1 Environment

Ensure that work benches, tools, and floor mats have a conducting surfaceconnected to ground. Before handling static-sensitive components and

assemblies, ground yourself to the conducting surface using an anti-staticwrist strap

When handling static-sensitive components and assemblies, do not wear

or use clothes made of wool, nylon or any other synthetic material. Suchfabrics are major sources of static build-up

When handling static-sensitive components and assemblies, do not usegloves and finger covers, unless they are made of cotton.

1.4.2 Tools

You need the following tools to perform the procedures described in thishandbook:

An anti-static wrist strap

A serviceable replacement unit

A Torx size 30 screwdriver

A 4 mm Flathead screwdriver

A size 1 Philips crosshead screwdriver.

Ensure that all the tools which come into contact with static-sensitivecomponents are at the same voltage level as the conducting work surfaces

and floor mats.These tools include soldering irons, oscilloscopes, power supplies, andmetal parts of tools and fixtures that are used to hold, assemble or test PBAs

Do not use rough cleaners or erasers to clean the gold-plated contacts

on PBAs

Do not mark a PBA with a lead pencil or any other writing instrument

Do not use synthetic brushes to clean equipment, and do not use dry

cleaning methods.

16 / 176 3BK 20935 AAAA PCZZA Ed.20


1.4.3 Transportation and Storage

Pack all containers used to transport and store static-sensitive components,

and use aluminum container tubes if possible. If not, insert the componentterminations into electrically conductive foam

Before shipping a PBA, wrap it in a conducting synthetic bag or in aluminum

foil. Also pack the PBA in a polyethylene transport box

Before shipping a PBA which has metal oxide semiconductor components,

ensure that an appropriate warning symbol is displayed on the package

Store spare PBAs in their appropriate polyethylene boxes. Keep the boxesclosed except when access to their contents is required

Do not store PBAs in an area where the air is polluted with smoke, dust,

dangerous gases or other airborne particles that may cause damage

Do not stack PBAs side-by-side or on top of each other with the board

surfaces or components in contact with one another

Before cleaning a PBA, remove or disconnect the damage protection, suchas protective foam, to allow the PBA to be cleaned thoroughly. Replace the

damage protection upon completion of the task.

1.4.4 Components and PBAs

Components and PBAs not in protective containers, must only be handledby trained personnel in static-controlled work areas

Before removing a PBA from an equipment rack, discharge any static bytouching the metal frame of the rack with your hand

Always handle a PBA by the edges

Do not handle or carry a PBA by any of the mounted components

Do not handle a PBA by the gold-plated contact terminals and do not applydirect pressure to the components.

Do not touch PBA connection pins or conductor paths

Do not touch PBAs with wet hands

Place PBAs that have been removed during maintenance with the solderedside downwards on a conductive surface.

Do not scratch or rub the soldered side of a PBA with a sharp or rough object

Do not repair PBAs in the switch room

Do not handle components and assemblies by their leads

Do not use excessive force when inserting connection boards.

3BK 20935 AAAA PCZZA Ed.20 17 / 176


18 / 176 3BK 20935 AAAA PCZZA Ed.20

2 Maintain the BSXTU1 Telecommunications Subrack


This section covers replacement of the following BSXTU1 TelecommunicationsSubrack RITs:

Fan Unit (BDAFU)

Front RITs:

BE35B2

JBETI

JBGPU.

Rear RITs:

BA35B2

BATTU

JAETI

JAE1

JAE1C

BAREDC2.

3BK 20935 AAAA PCZZA Ed.20 19 / 176


2.1 Before You StartRead this section before you start the procedures in this section.

2.1.1 Impact on System

As long as only one unit is removed and replaced at any one time, there is noimpact on the system. This is because redundancy is built into the componentsof the BSXTU1 Telecommunications Subrack.

In a standard configuration, the lower BSXTU1 Telecommunications Subrack isempty. In a pre-equipped configuration, the second subrack contains a full setof units. The procedures described here apply to both subracks.

2.1.2 Preventive Maintenance

Only replace RITs on the BSXTU1 Telecommunications Subrack, if the MFSIMT displays alarm signals for them.

2.1.3 The BSXTU1 Telecommunications Subrack

JBETI

Empty

Empty

Empty

Empty

Empty

JBGP

U2JB

GPU2

JBGP

U2JB

GPU2

JBGP

U2JB

GPU2

JBGP

U2JB

GPU2

JBGP

U2JB

GPU2

JBGP

U2JB

GPU2

Fan Trays PCIBF

Empty

BE35B2

BE35B2

BE35B2

JBETI

BE35B2

BE35B2

BE35B2

Figure 4: The BSXTU1 Telecommunications Subrack, Front View

20 / 176 3BK 20935 AAAA PCZZA Ed.20


2.2 Fan Tray (BDAFU)An alarm is sent to the OMC-R if a BDAFU fails. Although the traffic is notinterrupted, you must replace the BDAFU as soon as possible, to prevent thesystem from overheating.

Note: If the system overheats:

Telecommunication functions are affected

There is a station switchover

The converter switches the power supply off, if it detects a temperatureabove 70xC.

Figure 5: Front Fan Unit

3BK 20935 AAAA PCZZA Ed.20 21 / 176


2.2.1 Remove BDAFU

To remove BDAFU:

1. Open the front doors of the MFS, and connect the anti-static wrist strap.

2. Press the Normal/Maintenance switch down, to set the BDAFU toMaintenance mode. The LED changes to green.

3. Turn the two locking screws a quarter turn to the left, to unlock the BDAFU.

4. Pull the BDAFU out.

2.2.2 Insert New BDAFU

To insert a new BDAFU:

1. Check that the new BDAFU is set to Maintenance mode(Normal/Maintenance switch down).

2. Slide the new BDAFU in place. The LED changes to green.

3. Turn the two locking screws a quarter turn to the right, to secure the BDAFU.

4. Press the Normal/Maintenance switch up, to set the BDAFU to Normalrunning mode. The LED switches off.

5. Disconnect the anti-static wrist strap, and close the front doors of the MFS.

22 / 176 3BK 20935 AAAA PCZZA Ed.20


2.3 Front RITsThis section covers the replacement of the following BSXTUTelecommunications Subrack Front RITs:

BE35B2

JBETI

JBGPU.

Note: Two retaining clips secure the Front RITs in place. The bottom clip is markedwith a red triangle.

Figure 6: Retaining Clips

3BK 20935 AAAA PCZZA Ed.20 23 / 176


2.3.1 BE35B2

2.3.1.1 Remove BE35B2To remove BE35B2:

1. Open the front and rear doors of the MFS, and connect the anti-staticwrist strap.

2. Set the BE35B2 On/Off switch to Off (0).

The green LED switches off.

3. At the rear of the subrack, disconnect the - 48V power supply cable from thecorresponding BA35B2.

4. At the front of the subrack, unlock the two retaining clips and pull theBE35B2 out.

2.3.1.2 Insert New BE35B2To insert a new BE35B2:

1. Slide the new BE35B2 in place and secure with the two retaining clips.

2. At the rear of the subrack, reconnect the - 48V power supply cable to thecorresponding BA35B2.

3. At the front of the subrack, set the BE35B2 On/Off switch to On (I).

The LED changes to green.

4. Disconnect the anti-static wrist strap, and close the front and rear doors ofthe MFS.

2.3.2 JBETI or JBGPU

Note: Protected firmware is installed in the ROM of the JBETI and the JBGPU. If theRIT has to be replaced because of faulty firmware, it should be sent back to theAlcatel Repair Center for correction.

When insert/remove JBGPU wait at least 30 seconds before anotherinsert/remove operation.

2.3.2.1 Remove JBETI or JBGPUTo remove JBETI or JBGPU:

1. Open the front doors of the MFS, and connect the anti-static wrist strap

2. For JBGPU removal, verify that JBETI are in stable state. Check that the ledis green for active JBETI, and is green blinking for standby one

3. Unlock the two retaining clips and pull the JBETI or JBGPU out.

2.3.2.2 Insert New JBETI or JBGPUTo insert a new JBETI or JBGPU:

1. Slide the new JBETI or JBGPU in place and secure with the two retainingclips


24 / 176 3BK 20935 AAAA PCZZA Ed.20


2.4 Rear RITsThis section covers the replacement of the following BSXTU1Telecommunications Subrack Rear RITs:

BA35B2

BATTU

JAETI

JAE1

JAE1C

BAREDC2.

A large number of cables run at the rear of the MFS. While working on a RIT,ensure you do not accidentally disconnect cables from other RITs.

Note: Two retaining clips secure the Rear RITs in place. The bottom clip is markedwith a red triangle (see Figure 6).

2.4.1 BA35B2

2.4.1.1 Remove BA35B2To remove BA35B2:


2. At the front of the subrack, change the corresponding BE35B2 On/Off switchto Off (0). The green LED switches off.

3. At the rear of the subrack, disconnect the - 48V power supply cable fromthe BA35B2.

4. Unlock the two retaining clips and pull the BA35B2 out.

2.4.1.2 Insert New BA35B2To insert a new BA35B2:

1. Slide the new BA35B2 in place and secure with the two retaining clips.

2. Connect the -48V power supply cable to the new BA35B2.

3. At the front of the subrack, change the corresponding BE35B2 On/Off switchto On (I). The LED changes to green.


3BK 20935 AAAA PCZZA Ed.20 25 / 176


2.4.2 BATTU

2.4.2.1 Remove BATTUTo remove BATTU:

1. Open the rear doors of the MFS, and connect the anti-static wrist strap.

2. Disconnect the 16 Ethernet cables from the BATTU (slot TU 00 to TU 15).These cables are normally fastened together to keep them in the correctorder, but ensure that they are labeled.

3. Unlock the two retaining clips and pull the BATTU out.

2.4.2.2 Insert New BATTUTo insert a new BATTU:

1. Slide the new BATTU in place and secure with the two retaining clips.

2. Reconnect the Ethernet cables to the BATTU.

3. Disconnect the anti-static wrist strap, and close the rear doors of the MFS.

2.4.3 JAETI

Figure 7: JAETI

26 / 176 3BK 20935 AAAA PCZZA Ed.20


2.4.3.1 Remove JAETITo remove JAETI:


2. Disconnect one or more of the following cables from the JAETI, dependingon the configuration:

ALEXT (two cables)

DRYLOOPS

ADR.OUT

ADR.IN

ADR.1

ADR.2

ADR.3

ETH (gray sleeve)

TRU (green sleeve).

Before disconnecting a cable, ensure that it is properly labeled. This willsave you time, when you later reconnect it.

3. Unlock the two retaining clips and pull the JAETI out.

2.4.3.2 Insert New JAETITo insert a new JAETI:

1. Slide the new JAETI in place and secure with the two retaining clips.

2. Reconnect all the cables

3. Disconnect the anti-static wrist strap, and close the rear doors of the MFS

2.4.4 JAE1 or JAE1C

2.4.4.1 Remove JAE1 or JAE1CTo remove JAE1 or JAE1C:

1. Open the rear doors of the MFS, and connect the anti-static wrist strap

2. Disconnect one of the following cable sets, depending on the configuration:

120 ohm (two cables) for the JAE1

75 ohm (four cables) for the JAE1C.


3. Unlock the two retaining clips and pull the JAE1 or JAE1C out.

2.4.4.2 Insert New JAE1 or JAE1CTo insert a new JAE1 or JAE1C:

1. Slide the new JAE1 or JAE1C in place and secure with the two retaining clips.

2. Reconnect the cables.


3BK 20935 AAAA PCZZA Ed.20 27 / 176


2.4.5 BAREDC2

2.4.5.1 Remove BAREDC2To remove BAREDC2:


2. Unlock the two retaining clips and pull the BAREDC2 out.

2.4.5.2 Insert New BAREDC2To insert a new BAREDC2:

1. Slide the new BAREDC2 in place and secure with the two retaining clips.


28 / 176 3BK 20935 AAAA PCZZA Ed.20

3 Maintain the JSHUB Hub/Switch Subrack


This section covers replacement of the following JSHUB Hub/Switch SubrackRITs:

JAHPS

Terminal Server

Super Stack II Hub 500 (HUB500xx)

Super Stack Baseline 10/100 Switch (SWITCH)

IOLAN.

3BK 20935 AAAA PCZZA Ed.20 29 / 176


3.1 Before You StartRead this section before starting the procedures in this section.


As long as only one Hub/Switch, BE35B2 or JAHPS is removed and replacedat any one time, there is no impact on the system. This is because the RITswork in hot-standby mode. If a RIT fails, the standby RIT takes over the tasks ofthe faulty one. Similarly, the Hub/Switch work in a load-sharing configuration. Ifa Hub/Switch fails, all the traffic is routed through the other one.

In case of failure, a replacement must be organized as soon as possible toprevent traffic interruption.

3.1.2 The JSHUB Hub/Switch Subrack*

*The SWITCH is not allowed in the MFS with AS800.

Empty

Empt

yBE

35B2

BE35

B2

Optional HUB500Optional HUB500

HUB500HUB500IOLAN

Figure 8: Front of the JSHUB Hub Subrack when Installed with an AS800Server Subrack

Empty



DS10

DS10

IOLAN

Opti

onal

HUB

500

Opti

onal

HUB

500

HUB500

HUB500

Figure 9: Front of the JSHUB Hub/Switch Subrack when Installed with aDS10 Server Subrack

30 / 176 3BK 20935 AAAA PCZZA Ed.20


3.2 JAHPSJAHPSs are located at the rear of the Hub Subrack (see Figure 8).

Two retaining clips secure each JAHPS in place. The bottom clip is markedwith a red triangle (see Figure 6).

3.2.1 Remove JAHPS

To remove JAHPS:


2. At the front of the subrack, change the corresponding BE35B2 On/Offswitch to Off. The LED switches off.

3. At the rear of the subrack, possible cables to disconnect from the JAHPS:

- 48V power supply

Hub power supply

IOLAN power supply (switch the IOLAN off before disconnecting thecable).

4. Unlock the two retaining clips and pull the JAHPS out.

3.2.2 Insert New JAHPS

To insert a new JAHPS:

1. Slide the new JAHPS in, and secure with the two retaining clips.

2. Connect the power supply cables and, if necessary, switch the IOLANback on again.

3. At the front of the subrack, change the corresponding BE35B2 On/Offswitch to On. The LED switches on.


3BK 20935 AAAA PCZZA Ed.20 31 / 176


3.3 Super Stack II Hub 500 (HUB500)* / Super Stack Baseline10/100 Switch (SWITCH)

* The Super Stack II Hub 500 (HUB500) is now obsolete and is replaced withSuper Stack Baseline 10/100 Switch (SWITCH) .The SWITCH can be installed only in MFSs with DS10 (NOT in MFSswith AS800 server) !In case of a HUB500 failure, you must change both Hubs on the subrackwith Switches.

The two Hubs for MFS with AS800 are located at the center of the Hub Subrack.

The two Hubs/Switches for MFS with DS10 are located in the margin of theHub/Switch DS10 Subrack.

Their position vary depending on the Server Configuration (see figures 8and 9)

Figure 10: AS800: Super Stack II Hub 500s and IOLAN

32 / 176 3BK 20935 AAAA PCZZA Ed.20


Figure 11: DS10: Super Stack II Hubs 500 / Super Stack Baseline 10/100Switches

3BK 20935 AAAA PCZZA Ed.20 33 / 176


3.3.1 Remove HUB500** or SWITCH

Note: ** Due to the Super Stack II Hub 500 (HUB500) obsolescence you mustreplace two Hubs with two Super Stack Baseline 10/100 Switch (SWITCH) ,for the same subrack.

To remove HUB500** or SWITCH:


2. At the rear of the subrack, disconnect the Hub/Switch power cable.

3. At the front of the subrack, disconnect all the cables attached to theHub/Switch.


4. Unscrew the four screws that secure the Hub/Switch to the subrack, andpull it out.

3.3.2 Case: Insert New HUB

To insert a new HUB:

1. Slide the new HUB in, and secure with the four screws.

2. If both subracks are equipped, connect first (second) inter Hub cable CAHUBbetween Hub1 (2) and Hub3 (4) rear connectors.

3. Connect all the cables at the front of the HUB.


3.3.3 Case: Insert New SWITCH***

Note: *** NOT APPLICABLE FOR MFS WITH AS800. Due to the Super Stack II Hub500 (HUB500) obsolescence you must replace not only one, but the two Hubsfor that subrack with two Super Stack Baseline 10/100 Switch (SWITCH) .

To insert a new SWITCH

1. Slide the new Switch in, and secure with the four screws.

2. If both subracks are equipped, connect first (second) inter Switch cableALETHC between Switch 1 (2) Ethernet port 24 and Switch 3 (4) Ethernetport 24.

This will reduce number of Ethernet ports at 23 for both.

3. Connect all the cables at the front of the Switch.


34 / 176 3BK 20935 AAAA PCZZA Ed.20


3.4 IOLAN

Figure 12: IOLAN below AS800 Hubs

Figure 13: IOLAN below DS10 station

Note: The IOLAN is only used for the AS800 or DS10 Server Subrack configuration ormaintenance.

If the IOLAN fails, there is no impact on the telecom functions and thereplacement can be carried out without any impact on traffic.

3.4.1 Remove IOLAN

To remove IOLAN:


2. Switch the IOLAN off.

3. Mark (if necessary) all cables and note their position for reconnection.

4. Disconnect all the cables from the IOLAN, starting with the power cable.

5. Unscrew the four screws that secure the IOLAN to the subrack, and pull it out.

3BK 20935 AAAA PCZZA Ed.20 35 / 176


3.4.2 Insert New IOLAN

To insert a new IOLAN:

1. Slide the new IOLAN in, and secure with the four screws.

2. Reconnect all the cables to the new IOLAN as noted, ending with thepower cable.

3. Switch the new IOLAN on.

4. Configure the IOLAN parameter setup, use the procedures described inConfigure IOLAN Terminal Server (Section 7.2.2).


36 / 176 3BK 20935 AAAA PCZZA Ed.20

4 Maintain the AS800 Server Subrack


This section covers replacement of the following AS800 Server Subrack RITs:

CPU-Box

PCI Board Fan

300W CPU-Box Converter

CD-ROM Drive

Shared Hard Disk (9GBD)

Local Hard Disk (9GBD)

Disk Converter (90PS)

Man Fan Tray.

3BK 20935 AAAA PCZZA Ed.20 37 / 176




As long as only one unit is removed and replaced at any one time, there is noimpact on the system. This is because redundancy is built into the componentsof the AS800 Server Subrack.


Preventive Maintenance of the AS800 Server Subrack means that RITs arereplaced under the following conditions:

At scheduled intervals regardless of whether the RIT is faulty or not

After a regular RIT check in IMT, if the RIT fails the test

Creation of a pre-loaded backup local hard disk for a AS800 station A andstation B each, in case of

Initial installation of a site

Software version change or modification of data/code on the local disk

After the replacement of a failed AS800 local disk.

4.1.3 The AS800 Server Subrack

AS800CPUB

LocalDisk

9GBDEmpty CD−ROM

AS800CPUB

LocalDisk

9GBDCD−ROM Empty

SharedDisk

9GBDEmpty Empty

PowerUnit

90PS

SharedDisk

9GBD

PowerUnit

90PS

Subrack A Subrack B

Figure 14: The AS800 Server Subrack

38 / 176 3BK 20935 AAAA PCZZA Ed.20


4.2 Beep AlarmsWhen you power the CPU-Box on, you must hear the 1-3 beep code alarm. Itmeans that the CPU is functioning properly.

Any another type of beep alarm indicates a possible problem.

Beep Code Problem Corrective Action

1-1-2 ROM data path error detected while loadingAlphaBIOS/SRM console code.

Replace the CPU-Box.

1-1-4 The SROM code is unable to load theconsole code: Flash ROM header area orchecksum error detected.


1-2-1 TOY NVRAM failure. Replace the CPU-Box.

1-2-4 Backup cache error. Replace the CPU-Box.

1-3-3 No usable memory detected. Make sure that the memory RITs areproperly in place, and power the CPU-Boxup again. If the system still fails, Replacethe CPU-Box.

3-3-1 Generic system failure. Possible problemsources include the TOY NVRAM chip, orthe PCI-to-EISA bridge chipset.


3-3-3 Failure of the native SCSI controller on thesystem board.


Table 1: CPU Diagnosis by Beep-Codes

3BK 20935 AAAA PCZZA Ed.20 39 / 176


4.3 System Backup for MFS AS800 SystemThis procedure consists of a complete software backup (UNIX + NECTAR +MFS) from the local disk of the active station.

This procedure can be performed in two situations:

When a restore procedure is needed on the standby station

When a preventive backup is needed. In that case a new hard disk mustbe used.

4.3.1 Prerequisites

The firmware level is at least 5.5. To verify firmware, see Checks andUpdates (Section 7.1.4.2)

The active station must have been installed properly with the official Alcatel

methods (installation or software change)

Network configuration information for external interface tu0 ( IP address,Gateway, hostname) of the station that must be restored.

4.3.2 Back Up the Active Local Disk

With the IMT Main Window, identify the active station

Log in as root on the active station:telnet 1.1.1.x

x is 1 if active station is STATION_Ax is 2 if active station is STATION_B

Only one serial connection through IOLAN is possible with an AS800 station.

In case a restore procedure is needed on the standby station:

From the active station, log in as root on the standby station using

the IOLAN:telnet 1.1.1.20 port_standby

port_standby is 10002 for STATION_A and 10003 forSTATION_B

Press the [ halt ] (middle) button of the AS800 standby station.

40 / 176 3BK 20935 AAAA PCZZA Ed.20


Legend: 1 Power ON/OFF button 2 Halt button 3 Reset button 4 Power OK LED (green) 5 Halt LED (amber)

45

13

2

Figure 15: Front Panel for AS800

Unplug the standby station’s local hard disk and insert it near thehard disk of the active station, see Replace a Local Hard Disk (9GBD)

(Section 4.10)

In case a preventive backup is needed, insert a new hard disk near the harddisk of the active station. The backup will be performed on this new disk.

Log in as root on the active station

Launch the backup procedure:cd /usr/mfs/binchmod +x mfs_as800_backup./mfs_as800_backup

Note : The backup takes about 25 minutes.The following message is displayed: Backup on going please wait.

Wait until following message appears: Backup completed.

Unplug the hard disk previously copied. In case a restore procedure is

needed, insert it in the hard drive of the standby station (SCSI hot plug).

3BK 20935 AAAA PCZZA Ed.20 41 / 176


4.4 Restore the Standby Station of an MFS AS800This procedure consists of restoring the local disk of the standby stationtaking the system backup as a basis.

Note: Before you start the procedure, make sure to have the required networkconfiguration information for external interface tu0 (IP address, gateway,hostname) of the station that must be restored.

To restore the standby station, perform the following:

Press the [ halt ] (middle) button of the station to be restored

When the station is halted (see previous section), boot in single user mode:>>> b -flags S

Mount the local file systems:bcheckrc

Start the restore:cd /usr/mfs/binchmod +x mfs_as800_restore_fromactive./mfs_as800_restore_fromactive

Answer the questions regarding the network configuration (local name, IP

address, hostname) and follow instructions on the screen.Wait until the following message appears: Restore completed

If the standby station does not reboot automatically, then reboot the

station manually:reboot

Wait until the standby station reboots. The reboot is finished when telnetis possible again on the station.

Exit the IOLAN and close the terminal window

Select ’Nectar View’ in the IMT: View->Nectar View

The station to be restored should be "failed". Select it and choose

’clear_alarm’ action in the pop-up window

Note: After clear_alarm is selected, a station reboot takes place. Wait until thereboot is finished.

If the ’clear_alarm’ item is not visible, then reboot the standby stationmanually:

/usr/mfs/bin/mfs_start_nectar -siteConfirm the reboot and wait until the reboot is finished. The reboot isfinished when telnet is possible again on the station.

42 / 176 3BK 20935 AAAA PCZZA Ed.20


4.5 Replace CPU-Box

Figure 16: AS800 CPU-Box

4.5.1 Prerequisites

Ensure that the available exchange unit is of the same type, with the same

software and firmware

You will need a flat blade screwdriver for the operation

You must have the CD-ROMs of

The operating system

The firmware

The MFS application.

You must have the written licenses for the new station

You need access to the station via IMT or via VT-Console.

3BK 20935 AAAA PCZZA Ed.20 43 / 176


4.5.2 Isolate a Station

1. Check on the active station which UNIX version is used:sizer -v

The UNIX version will be displayed.

2. Check on the active station which firmware version is used:consvar -d |grep Firmware

The firmware version will be displayed.

3. Check on the active station which MFS software version is used:/usr/mfs/bin/mfs_version

The MFS software version will be displayed for GPU and OAM.

4. Check if the versions of:

UNIX

Firmware

MFS software.

match the versions of the available CD-ROMs.

If a version does not match, contact your Alcatel System Support.

If the station to be replaced is no longer in service (e.g. a CPU crash occurred),the system will also have the status ’halt’.

4.5.2.1 Check Station ModeTo check the station mode:

1. Check the active and standby station, if the station to be replaced is still inservice.

2. Log in at IMT and enter:BUI -> Reception ViewBUI -> Request

In the "Request Window", enter:get sta[*](*)

and click on [ Send ].

3. Note the currently active and standby station displayed.

4. Make sure that the station to be replaced is in standby mode. If it is not,switch the station over to standby with the IMT command:tools -> switchover

(This will take several minutes.).

5. Check again that the station to be replaced is in standby mode.

4.5.2.2 Reboot the StationTo reboot the station:

1. To stop the processes running on the standby station, enter:/usr/mfs/bin/mfs_stop_nectar

2. Confirm the reboot request. The reboot is finished when telnet is possibleagain on the station. After the reboot, UNIX is restarted.

3. To stop the system, log in as administrator and enter:halt

A ’>>>’ shows that the system is stopped.

44 / 176 3BK 20935 AAAA PCZZA Ed.20


4.5.3 Replace CPU-Box Hardware

Equipment must be powered off.Before removing and replacing a CPU-Box, ensure that the CPU-Box beingremoved is properly powered off.

4.5.3.1 Remove the CPU-BoxTo remove the CPU-Box:


2. Switch the TRU power supply off by push in the small red button of theappropriate circuit breaker:

A3 for the left-hand side box

B3 for the right-hand side box.

3. Unscrew the four captive screws of the CPU-Box front cover and remove it.

4. Unscrew the six retaining screws that secure the CPU-Box to the subrackand slide the CPU-Box out (a rail stopper on the right hand side of theCPU-Box will prevent it from falling down).

5. On the rear of the subrack, disconnect the -48 to -60 VDC input cable to thepower connector (A1 or B1) for the CPU-Box that is being removed.

6. Remove the 300 W Converter (CNVR) from the CPU-Box that is beingremoved. See Replace 300W Converter (CNVR3) (Section 4.7).

7. Disconnect all the cables connected to the top of the CPU.

8. Remove the two nuts that secure the middle cable clamp to the top of theCPU-Box and lift the clamp off of the two studs. Leave the cable clampsecured to the cable bundle.

9. Remove the two screws that secure the rear cable clamp/guard to the top ofthe CPU-Box. Leave the cable clamp/guard secured to the cable bundle.

10. Push in on the slide releases and pull the CPU-Box out of the Subrackchassis

The CPU-Box weighs 13.6 kg . Carefully remove the station from its location.Use the handle on the front of the CPU-Box to lift and carry the CPU-Box.

3BK 20935 AAAA PCZZA Ed.20 45 / 176


4.5.3.2 Insert New CPU-BoxTo insert New CPU-Box:

1. Position the new CPU-Box in place. Ensure correct locking of the slidereleases.

2. Reconnect all the cables connected to the top of the CPU.

3. Replace the two screws to secure the rear cable clamp/guard to the top ofthe CPU-Box.

4. Replace the two nuts to secure the middle cable clamp to the top of theCPU-Box

5. Carefully slide the CPU-Box in the subrack

Do not use force. If you encounter resistance when sliding the CPU-Box in thesubrack, it means cables are catching on something.Slide the CPU-Box out, position the cables carefully and try again.

6. Secure with the six retaining screws.

7. Place the CPU-Box front cover on, and secure with the four captive screws.

8. Switch the TRU power supply on, by pushing the large green button of theappropriate circuit breaker:



9. Power the CPU-Box on, using the CPU-Box’s recessed Control Panel.

Be careful to press the buttons in the following order:

Right-hand side button (On/Off) - the LED switches on

Middle button [ Halt ] - the LED switches off.

The CPU-Box emits a 1-3 beep code alarm. If you hear another sequenceof beeps, see Beep Alarms (Section 4.2).

46 / 176 3BK 20935 AAAA PCZZA Ed.20


4.5.4 Install and Configure New CPU-Box

To install and configure a new CPU-Box:

1. Press the [ halt ] button on the replaced station.

2. Disconnect the anti-static wrist strap, and close the doors of the MFS.

3. Check the current version of the replaced station, using the CPU consoleconnected to COM1, and enter:>>> sh version

4. If the firmware on the replaced station is not the expected one, update thefirmware using the procedure described in Checks and Updates (Section7.1.4.2).

5. Check the SCSI port settings:

Display the current SCSI ID settings by entering:sh |grep hostThere will be three responses, as there are three SCSI bus on eachstation.

The pka0_host_id should be 7 for both station

The pkb0_host_id and the pkc0_host_id for STATION_A has to be 5,

and for STATION_B has to be 6

If the SCSI ID does not match, change the ID by entering:set <parameter_name> <value>(e.g. pkb0_host_id 5).

6. Check all AS800 SRM variables, see Checks and Updates (Section 7.1.4.2).

7. Start the operating system of the new station:>>>initialize

8. Use System Backup for MFS AS800 System (Section 4.3) to restore UNIX,Nectar and MFS on new station.

4.5.5 New Station Start Up

1. To start the MFS application, enter:/usr/MFS/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished, when telnet ispossible again on the station.

2. Check, after a few minutes, if the replaced station is in standby mode.

3. If this is not successful, contact your Alcatel System Support.

3BK 20935 AAAA PCZZA Ed.20 47 / 176


4.6 Replace PCI Board FanThe PCI Board Fan is located in the CPU-Box, on the right-hand side of theCPU.

Figure 17: PCI Board Fan

4.6.1 Slide Out CPU-Box

To slide out CPU-Box:

1. Lock the AS800 Server Subrack


3. Shut the CPU-Box down, using the CPU-Box’s recessed Control Panel


Middle button [ halt ] - the LED switches on

Right-hand side button [ On/Off ] - the LED switches off.

4. Switch the TRU power supply off by pushing in the small red button of theappropriate circuit breaker:




6. Unscrew the six retaining screws that secure the CPU-Box to the subrackand slide the CPU-Box out (a rail stopper on the right-hand side of theCPU-Box will prevent it from falling down).

48 / 176 3BK 20935 AAAA PCZZA Ed.20


4.6.2 Replace PCIBF

To replace PCIBF:

1. Unscrew the four crosshead screws that secure the PCIB and pull it out.

2. Disconnect the PCIBF power wires from the extension cable.

3. Connect the new PCIBF power wires to the extension cable.

4. Position the new PCIB in place, and secure with the four crosshead screws.

4.6.3 Insert CPU-Box

To insert CPU-Box:

1. Carefully slide the CPU-Box in the subrack.




4. Switch the TRU power supply on, pushing the large green button of theappropriate circuit breaker:



5. Power the CPU-Box on, using the CPU-Box’s recessed Control Panel.


Right-hand side button [ On/Off ] - the LED switches on

Middle button [ Halt ] - the LED switches off.



7. Unlock the AS800 Server Subrack.

3BK 20935 AAAA PCZZA Ed.20 49 / 176


4.7 Replace 300W Converter (CNVR3)The 300W Converter for CPU power supply is located on the top of theCPU-Box.

Figure 18: 300W Converter (CNVR3)

Before removing and replacing a CNVR3, ensure that the installed CPU-Boxis properly powered off and that the -48 to -60 VDC input cable to the powerconnector (A1 or B1) for the CNVR3 being replaced has been disconnected.

4.7.1 Slide Out CPU-Box

To slide out CPU-Box:


2. Lock the AS800 Server Subrack.

3. Shut the CPU-Box down, using the CPU-Box’s recessed Control Panel.


Middle button [ halt ] - the LED switches on

Right-hand side button [ On/Off ] - the LED switches off.

4. Switch the TRU the power supply off, pushing in the small red button of theappropriate circuit breaker:



5. On the rear of the subrack, disconnect the -48 to -60 VDC input cable tothe power connector (A1 or B1) for the CPU-Box which CNVR3 is beingremoved.

50 / 176 3BK 20935 AAAA PCZZA Ed.20



7. Unscrew the six retaining screws that secure the CPU-Box to the subrackand slide the CPU-Box out (a rail stopper on the right hand side of theCPU-Box will prevent it from falling down).

4.7.2 Replace CNVR3

To replace CNVR3:

1. Disconnect the power supply connector on the right side of the CNVR3.

2. Unscrew the eight crosshead screws that secure the CNVR3 to the CPU-Box.

3. Grasp the handles on the left and right side of the CNVR3 and lift it upand out of the CPU-Box.

4. Position the new CNVR3 in place, and secure with the eight crossheadscrews.

5. Connect the power supply cable.

4.7.3 Slide in CPU-Box

To sSlide in CPU-Box:

1. Carefully slide the CPU-Box in the subrack.




4. Switch the TRU power supply on, pushing the large [ green button ] of theappropriate circuit breaker:



5. Power the CPU-Box on, using the CPU-Box’s recessed Control Panel. Becareful to press the buttons in the following order:

Right-hand side button [ On/Off ] - the LED switches on

Middle button [ halt ] - the LED switches off.


6. Unlock the AS800 Server Subrack.


3BK 20935 AAAA PCZZA Ed.20 51 / 176


4.8 Replace CD-ROM DriveThe CD-ROM Drive is located in the optional device slot of the AS800 ServerSubrack.

CDROM−Drives

Figure 19: CD-ROM Drive

4.8.1 Remove CD-ROM Drive

To remove CD-ROM Drive:


2. If there is a CD in the CD-ROM Drive, try to remove it.

3. Unscrew the four captive screws that secure the Local/Shared Disk boxfront cover, and remove it.

4. Pull out the CD-ROM Drive.

4.8.2 Insert New CD-ROM Drive

To insert a new CD-ROM Drive:

1. Slide the new CD-ROM Drive in, and secure with the two crosshead screws.

2. Place the Local/Shared Disk box front cover back on, and secure withthe four captive screws.


52 / 176 3BK 20935 AAAA PCZZA Ed.20


4.9 Replace a Shared Disk (9GBD)The Shared Hard Disks are located in the SDBOX.

Shared Disks

Figure 20: Shared Hard Disc Drives

4.9.1 Prerequisites

1. Identify the shared disk to be replaced physically by obtaining the nameof the device, use the command:

voldisk list

Example:

DEVICE TYPE DISK GROUP STATUS

rz0h simple rz0h rootdg online

rz17 sliced ____ ______ online

rz9 sliced diskA nsedg online

___ ______ diskB nsedg

rz17 is failed

2. Identify the shared disk to be replaced functionally by obtaining thefunctional names in the related alarm or by IMT (In the IMT window:View-> Nectar View -> aspA/aspB ).

Example for AS800:

rz17corresponds to rack1_sb3_aspA_dudisk1A obiect name in the alarm

rz9corresponds to rack1_sb3_aspB_dudisk1B obiect name in the alarm

In the example given, is an alarm relative to the object namerack1_sb3_aspA_dudisk1A , then conclude where is located the faileddisk. In our example the failed rz17 is located on Station A side

The name of the disk given by the voldisk list command does notcorrespond to the functional name.

3BK 20935 AAAA PCZZA Ed.20 53 / 176


3. Examine the StorageWorks Shelf to identify and verify the name of the disk.

4. Ensure that the available exchange disk is of the same type.

4.9.2 Remove Shared Disk

RTo remove Shared Disk:


2. Unscrew the four captive screws that secure the SDBOX front cover, andremove it.

3. Unscrew the two retaining screws that secure the Shared Hard Disc to thesubrack, and pull it out.

4.9.3 Insert New Shared Disk

To insert a new Shared Disk:

1. Slide in the new Shared Hard Disk in place and secure with the tworetaining screws.

2. Place the SDBOX front cover back on, and secure with the four captivescrews.


4.9.4 Recover the New Shared Disk

To rRecover the new Shared Disk:

1. In the IMT window:

View -> Nectar View

2. In the Nectar View window, select the failed object (name is given in thealarm with message I/O device error ) and right on it:

-> Disk_recover

3. Check at OMCR that:

The new disk is operational

The alarm has disappeared.

4. If this is not successful, contact your Alcatel system support.

54 / 176 3BK 20935 AAAA PCZZA Ed.20


4.10 Replace a Local Hard Disk (9GBD)The Local Hard Disks are located in the SDBOX.

Local Hard Disks

Figure 21: Local Hard Disk Drives

3BK 20935 AAAA PCZZA Ed.20 55 / 176


4.10.1 Pre-load Backup Disk

A backup of both local hard disks must be done before a disk failure andreplacement. This backup disk should be done twice for an AS800 subrackfor the local disks of station A and station B. The pre-loaded disks have to belabeled according to their content (i.e. local disk A or B).

Creating a pre-loaded backup of the local hard disks must be done in case of:

First installation of a site

Software version change or modification of data/code on the local disk

After the replacement of a failed AS800 local disk (for rebuilding a new

pre-loaded disk to be available for a future failure).

Use the "Copy Data" procedure to create a pre-loaded disk.

Copy Data 1. Log in as root on the console.

2. Go into single mode:init s


4. Insert the new Local Hard Disk into a free slot on the local bus.

5. Create the device:cd/dev./MAKEDEV rz1

6. Erase the label of the new disk:disklabel -z rz1

7. Copy old disk data to new disk:dd bs=512000 if=/dev/rrz0c of=/dev/rrz1c

8. Halt the station:halt

9. Remove the now pre-loaded disk.

10. Label the pre-loaded disk with its contents (Station A or Station B).

56 / 176 3BK 20935 AAAA PCZZA Ed.20


4.10.2 Replace Local Hard Disk

4.10.2.1 Remove Local Hard DiskTo remove local Hard Disk:



3. Unscrew the two retaining screws that secure the Local Hard Disk to thesubrack.

4. Pull the old local disk to be replaced out.

4.10.2.2 Insert New Local Hard DiskTo insert new local Hard Disk:

1. Slide in the new preloaded Local Hard Disk in place where the removed diskwas and secure it with the two retaining screws.


3. (Optional) Proceed with software installation if required.

4. (Optional) Create a new pre-loaded local hard disk for future use.

5. Disconnect the anti-static wrist strap, and close the doors of the MFS

3BK 20935 AAAA PCZZA Ed.20 57 / 176


4.11 Replace 90W Converter (CNVR9)The 90W Converter for the SDBOX power supply is located on the right side ofeach subrack

CNVR9

Figure 22: 90W Converter (CNVR9)

4.11.1 Remove CNVR9

To remove CNVR9:



3. Unscrew the two retaining screws that secure the CNVR9 to the subrack,and pull it out.

4.11.2 Insert New CNVR9

To insert New CNVR9:

1. Slide in the new CNVR9 in place and secure with the two retaining screws.



58 / 176 3BK 20935 AAAA PCZZA Ed.20


4.12 Replace Main Fan TrayThe Main Fan Trays are located under the SDBOX (Local or Shared Disk Box).

You have five minutes to complete the operation before the systemoverheats . You can complete this procedure without powering the CPU-Box off.

Figure 23: Main Fan Trays

Note: If the system overheats:

Telecommunication functions are affected

There is a station switchover

The converter switches the power supply off, if it detects a temperatureabove 70 xC.

4.12.1 Remove MFT

To remove MFT:


2. Unscrew the four captive screws and remove the SDBOX front cover.

3. Unscrew the two crosshead screws that secure the MFT, and pull out.

4.12.2 Insert New MFT

To insert a new MFT:

1. Slide in the new MFT and secure it with the two crosshead screws.

2. Put the SDBOX front cover back on, and secure it with the four captivescrews.


3BK 20935 AAAA PCZZA Ed.20 59 / 176


60 / 176 3BK 20935 AAAA PCZZA Ed.20

5 Maintain the DS10 Server Subrack (both DS10/RC23 and DS10/RC40)

5 Maintain the DS10 Server Subrack (both DS10/RC23and DS10/RC40)

This section covers replacement of the following DS10 Server Subrack RITs:

SCSI bus

CPU-Box

Shared disk (9GBD)(*)

180W Power Supply(*)

DAT Drives (PVDAT01)(*)

Blower.

The items marked (*) are present only for DS10/RC23 , not for DS10/RC40.

3BK 20935 AAAA PCZZA Ed.20 61 / 176



There are two types of MFS equipped with DS10:

A9135 MFS with DS10/RC23 (one disk DS10 stations or network mirroring

disks stations)

A9135 MFS with DS10/RC40 (two disks DS10 stations or local disksstations)


As long as only one unit is removed and replaced at any one time, there is noimpact on the system. This is because redundancy is built into the componentsof the DS10 Server Subrack. If a server fails, the other server takes over thefunction and there is no telecom traffic interruption.


Preventive Maintenance of the DS10 Server Subrack means that RITs arereplaced under the following conditions:

At scheduled intervals regardless of whether the RIT is faulty or not

After a regular RIT check, if the RIT fails the test

After a self test of the DS10 NECTAR Platform, if a RIT fails the test.

62 / 176 3BK 20935 AAAA PCZZA Ed.20



This section describes a UNIX procedure to isolate a pilot station for repairor test procedures.

5.1.3.1 Prerequisites

A station or PC equipped for UNIX procedures linked to the platform

Open sessions (UNIX window) to both pilot stations active and standby.

5.1.3.2 Change the Platform to Simplex ModeTo change the platform to Simplex Mode:

1. Log in to the active station with the UNIX command:rlogin <station_name>

2. (Optional) If there are faults on the SCSI bus or shared disks, you can isolatethe shared disk connected to the faulty SCSI bus with the UNIX command:

voldg -g<group_name> -k rmdisk<LSMdisk_name>

3. Log in to the standby station with the UNIX command:rlogin <station_name>

4. Open the BUI on the active station with the UNIX command:cd /usr/nectar/bin/UP_BUI -h <station_name> -lm

5. Lock the station that you want to shut down via the hardware managementBUI command:action du [station_letter] (lock());

6. The hardware management command automatically invokes the necessaryUNIX commands to shut down the station.

7. Use the BUI commands or the NMC2 interface to verify in the hardwaremanagement list that the station has changed state to:MANLO(locked, disabled, ok)

8. Stop the power to the machine with the [ Power ] button on the front ofthe machine.

3BK 20935 AAAA PCZZA Ed.20 63 / 176


5.2 Replace SCSI Bus (*)(*) External SCSI Bus is present only for MFS with DS10/RC23.

Note: This section is not applicable for MFS with DS10/RC40.

The alarm generated for a SCSI malfunction defines which SCSI bus is in fault(SCSI1 or SCSI2).

5.2.1 Prerequisites

You must identify the active and standby station

Verify the name and note the positions of:

The faulty SCSI bus

The shared disk connected to the faulty SCSI bus.

Ensure that the available exchange parts are of the same type

You will need a flat blade screwdriver for the operation and a SCSI

terminator for the SCSI bus.

5.2.2 SCSI Components

The SCSI bus is composed of several different replaceable componentswhich include:

The cables to the StorageWorks shelf

The tri-link connector to the StorageWorks shelf

The bus connections in the StorageWorks shelf

The SCSI cards in each station.

Tri−link

Tri−link

PCI slot 3SCSI bus 2

SCSIterminator


SCSIterminator



SCSIterminator

SCSIterminator

StorageWorkson SCSI bus 2

StorageWorkson SCSI bus 1

StationA

StationB

Figure 24: SCSI Components

64 / 176 3BK 20935 AAAA PCZZA Ed.20


SCSI cableSCSI Y cable

PCISCSI

: Protocol Control Information: Small Computer Systems Interface

PCI slot N° 2SCSI bus 1

SCSIterminator

StationA

StationB


SCSIterminator

Tri−link

Figure 25: SCSI 1

SCSI cableSCSI Y cable

PCISCSI

: Protocol Control Information: Small Computer Systems Interface


SCSIterminator

StationA

StationB


SCSIterminator

Tri−link

Figure 26: SCSI 2

Station A or B (rear view)

Ethernet 1

Ethernet 2

SCSI Bus 1

SCSI Bus 2

1

2

3

4

Power 1

2

Figure 27: SCSI Connectors on DS10 CPU Rear View

3BK 20935 AAAA PCZZA Ed.20 65 / 176


StorageWorks on SCSI Bus 1

(Front View)

Streamer Disk Personnalitymodule

Tri−link

SCSI bus 1 to station B

SCSI bus 1 to station A

Figure 28: SCSI Bus 1 Connectors on StorageWorks Shelf

StorageWorks on SCSI Bus 2

(Front View)

Disk Personnalitymodule

Tri−link

SCSI bus 2 to station B

SCSI bus 2 to station A

Figure 29: SCSI Bus 2 Connectors on StorageWorks Shelf

66 / 176 3BK 20935 AAAA PCZZA Ed.20


5.2.3 Determine the Faulty SCSI Component


2. Replace, cable by cable, all the SCSI cables including the tri-link, andtest the platform.

3. Replace the StorageWorks Shelf and test the platform.

4. Replace the redundant station and test the platform.

5. If the SCSI bus test gives a negative working state, return to next item instep 2. If the SCSI bus test works correctly the faulty component wasfound and the fault is solved.

6. If the SCSI problem cannot be solved, contact your Alcatel System Support.


3BK 20935 AAAA PCZZA Ed.20 67 / 176


5.3 System Backup for MFS DS10 RC23This procedure consists of a backup of the Unix, NECTAR and MFS softwareon DAT tape from the local disk of the active station.

5.3.1 Prerequisites

Verify that the firmware version is at least 6.1:# /sbin/consvar -d|grep Firmware

Firmware Rev: 6.1

Verify that the UNIX version and UNIX patch version is at least UNIX4.0F BL21. In the IMT select Software -> Unix patch management ->Display patch version

The active station must have been installed properly with the official Alcatelmethods (installation or software change)

A Compaq cartridge 12/24 GB density

5.3.2 Back up the Active Local Disk

To backup the Active Local Disk:

1. In the IMT Main Window, identify the active station.

2. Insert the tape in the DAT drive located in the StorageWorks shelf.

3. Log in as root on the active station.

4. Type the UNIX backup command:/usr/mfs/bin/mfs_ds10_backup

5. Wait until the message Back-up completed appears on the screen.

68 / 176 3BK 20935 AAAA PCZZA Ed.20


5.4 Restore the Standby Station of an MFS DS10 RC23This procedure consists of restoring the local disk of the standby stationusing the system backup.

There are two cases when it is necessary to perform the system restore:

The Unix file system is corrupted and needs to be repaired

A hardware problem occured and the replacement of DS10 is mandatory.

Prerequisites


Network configuration information for external interface (tu0) (IP address,

gateway and external hostname) of the station that must be restored

To restore the Standby Station:

1. Lock the station to be restored. In Nectar View:

If the tree is not expanded yet, click successively on the expand button ofrack1, srSTA1, srSTA2

Select the station to be restored

Open the contextual menu using right-click and select Lock .Wait for the little red lock to be displayed.

2. Log in as root on the active station:telnet 1.1.1.x


Only one serial connection through IOLAN is possible with a DS10 station.

3. From the active station, log in as root user on the standby station usingthe IOLAN:

telnet 1.1.1.20 port_standbyport_standby is 10002 for STATION_A and 10003 forSTATION_B

Enter in RMC mode and halt out the station:(Press Escape key twice, then type RMC)

>>>[ escape ][ escape ]RMCRMC>halt in [ Enter ]Returning to COM port

Press [ Enter ] in order to get back the SRM prompt >>>.>>>[ escape ][ escape ]RMCRMC>halt out [ Enter ]Returning to COM port

Press [ Enter ] in order to get back the SRM prompt >>>.

4. If the tape with the restore is not in DAT drive, insert the tape in DAT drive

5. Boot form DAT:>>>boot -flags "nc" MKA100

6. Select the boot device

In the SYSTEM TAPE TABLE section, when following message appear:

3BK 20935 AAAA PCZZA Ed.20 69 / 176


Enter your choice:

Enter1

7. Answer with Yes to all the questions asked.

When the script asks questions regarding the network configuration enter IPaddress and external name of the station.

Wait untill the station will be automatically reboot.

8. Boot from local disk:>>>boot dqa0

Wait until the station reboots. The reboot is finished when telnet is possibleagain on the station.

9. Exit the telnet session and close the window for which the telnet was done

10. In the IMT, select View->Nectar View :

If the station to be restored is ’failed’ select it and choose the ’clear_alarm’action in the pop-up window

Note: If the station reboots after clear_alarm is selected, wait until the rebootis finished.

11. Unlock the restored station. In the "Nectar View":


Select the station

Open the contextual menu using right-click and select UnlockWait until the standby station is restarted.

Wait until the "Nectar View" displays:

Availability state: OK

Operational state: Enable.

12. Eject the tape

Press Eject on MFS DAT drive.

5.5 System Backup for MFS DS10 RC40This procedure consists of a backup of the Unix, NECTAR and MFS softwareon DAT tape from the local disk of the active station.

5.5.1 Prerequisites

Verify the firmware version:# /sbin/consvar -d|grep Firmware

Firmware Rev: 6.5.15

Note: The check is OK if the firmware version is in accordance with Table 13(at least6.5). In the SRM firmware revision only the first two digits are relevant.

Verify that the UNIX version and UNIX patch version on active station isat least UNIX 5.1A BL24From IMT Software -> Unix patch management –> Display patchversions

70 / 176 3BK 20935 AAAA PCZZA Ed.20


The active station must have been installed properly with the official Alcatelmethods (installation or software change)


5.5.2 Back up the Active Local Disk

To back up the Active Local Disk:

1. In the IMT Main Window, identify the active station.

2. Insert the tape in the DAT drive located in the active station

3. Log in as root on the active station

4. Type the UNIX backup command:/usr/mfs/bin/mfs_rc40_backup

5. Wait until the backup is complete

6. Press Eject on the DAT drive and remove the tape from the active station.

5.6 Restore the Standby Station of an MFS DS10 RC40This procedure consists of restoring the local disk of the standby stationusing the system backup.

There are two cases when it is necessary to perform the system restore:

The Unix file system is corrupted and needs to be repaired

A hardware problem occured and the replacement of DS10 is mandatory.

Prerequisites

A Compaq cartridge 12/24 GB density (DDS3)

Network configuration information for external interface (ee0) (IP address,

gateway and external hostname) of the station that must be restored

To restore the Standby Station:

1. Insert the tape in the DAT drive located in the station to be restored

2. Lock the station to be restored. In Nectar View:

If the tree is not expanded yet, click successively on the expand button of

rack1, srSTA1, srSTA2

Select the station to be restored


3. Log in as root on the active station:telnet 1.1.1.x


Only one serial connection through IOLAN is possible with a DS10 station.

4. From the active station, log in on the standby station using the IOLAN:

3BK 20935 AAAA PCZZA Ed.20 71 / 176


telnet 1.1.1.20 port_standbyport_standby is 10002 for STATION_A and 10003 forSTATION_B

If the prompt >>> does not appear press [ Enter ].

Enter in RMC mode and halt out the station:(Press Escape key twice, then type RMC)

>>>[ escape ][ escape ]RMCRMC>halt out [ Enter ]Returning to COM port

Press Enter in order to get back the SRM prompt >>>.

Note : The DAT device can have a different name. To check the DATdevice name use:

>>>show dev

An example of the DAT device name is MKA500.

5. Boot from DAT:>>>boot -flag "nc" <DAT_device_name>

6. When the following question appears, type the correct answer:Which station does need to be restored (A or B)?

Type <A> if STATION_A is restoredType <B> if STATION_B is restored

7. When the script asks questions regarding the network configuration enter IPaddress and the external name of the station.

Wait until the station automatically reboots.

8. Boot from local disk:boot dqa0

Confirm the station IP and name.

Then a warning message and question are displayed:WARNING: you have to choose now the type of restoreyou want if master (m), mib data will be restored ifslave (s), mib data will not be restored

…What type of restore do you want? (m=master/s=slave)

You MUST ENTER “s” choice. The “m” choice is NOT SUPPORTED andWOULD ERASE ALL YOUR DATA

s

9. Exit the telnet session and close the window for which the telnet was done.

10. In the IMT, select View->Nectar View :

If the station to be restored is ’failed’ select it and choose the ’clear_alarm’action in the pop-up window

Note: If the station reboots after clear_alarm is selected, wait until the rebootis finished.

11. Unlock the restored station. In the "Nectar View":

If the tree is not expanded yet, click successively on the expand button of

rack1, srSTA1, srSTA2

Select the station

72 / 176 3BK 20935 AAAA PCZZA Ed.20



12. Check the availability and operational states, in IMT select View->NectarView :


Operational state: Enabled.

13. Eject the tape from the standby station

Press Eject on MFS DAT drive.

3BK 20935 AAAA PCZZA Ed.20 73 / 176


5.7 Replace DS10 Server (both DS10/RC23 and DS10/RC40)This section describes how to replace a failed server or a central unit.

Empty



DS10

DS10

IOLAN

Opti

onal

HUB

500

Opti

onal

HUB

500

HUB500

HUB500

Figure 30: DS10 Server Subrack

Figure 31: DS10 CPU Front View (both DS10/RC23 and DS10/RC40)

Station A or B (rear view)

Ethernet 1

Ethernet 2

SCSI Bus 1

SCSI Bus 2

1

2

3

4

Power 1

2

Figure 32: DS10 CPU Rear View (both DS10/RC23 and DS10/RC40)

74 / 176 3BK 20935 AAAA PCZZA Ed.20


5.7.1 Prerequisites

Ensure that the available exchange unit is of the same type

It is mandatory that the two stations have the same type of Ethernet board (ee0or tu0). Do not continue until the prerequisite is fulfilled.

You will need a flat blade screwdriver for the operation

You must have the CD-ROMs of the firmware (for RC40, ask for Alcatel

support).


5.7.2.1 Check Station ModeTo check Station Mode:

1. Check the active and standby station, if the station to be replaced is still inservice.

2. Log in at IMT:BUI -> Reception ViewBUI -> Request

3. In the Request Window, enter:get sta[*](*)

and click on [ Send ].

Note : which station is currently the active and standby station.

4. Make sure that the station to be replaced is in standby mode. If not, switchthe station over with the IMT command:tools -> switchover

(This will take several minutes).

5. Recheck that the station to be replaced is in standby mode.

5.7.2.2 Reboot the StationTo reboot the station:

1. Stop the processes running on the standby station:/usr/mfs/bin/mfs_stop_nectar

2. Confirm the reboot request. The reboot is finished when telnet is possibleagain on the station. After the reboot, UNIX is restarted.

3. From the active station, log in as root on the standby station using the IOLAN:telnet 1.1.1.20 port_standby


4. To stop the system, log in as root and enter:halt

If the prompt >>> appears, the system is stopped.

When the station to be replaced is no longer in service (e.g. a CPU crashoccurred), the system will have the status ’halt’.

3BK 20935 AAAA PCZZA Ed.20 75 / 176


5.7.3 Replace Station Hardware

5.7.3.1 Remove the StationTo remove the station:


2. Check which station has to be physically replaced.

Station A is the upper one; Station B is the lower one.

3. Power down the affected station by pressing the power button of the station.

4. Loosen the plug mounting of the power plug on the rear side of the device.

5. Disconnect the power plug.

6. Label and note the position of the cables to save time when reconnectingafterwards.

7. Disconnect all the cables from the back of the station.

Do not disconnect the SCSI bus terminator from the Storage Box!Disconnect the SCSI cable from the SCSI card on the rear side of the station!

Figure 33: DS10, Rear View, Cables Partly Disconnected (both DS10/RC23and DS10/RC40)

8. Unscrew the retaining screws from the front of the rack.

76 / 176 3BK 20935 AAAA PCZZA Ed.20


9. Carefully remove the station from the rack.

Figure 34: DS10, Physical Replacement both DS10/RC23 and DS10/RC40).

5.7.3.2 Insert New StationTo insert a new Station:

1. Place the new station the right way up on a table with the front facingtowards you.

2. Carefully lift the station shelf into place.

3. Fix the unit in place with the retaining screws on the front of the rack.

4. Reconnect the power cable, then all other cables except the SCSI cables.

Do not connect the SCSI bus cables to the station now.

5. Switch on the power.

3BK 20935 AAAA PCZZA Ed.20 77 / 176


5.7.4 Install and Configure New Station

5.7.4.1 Check the Firmware Version on the Old Running StationTo check the Firmware version on the old running station:

1. Log in on the old station

2. Check the firmware:consvar -d |grep Firmware

The firmware version will be displayed.

5.7.4.2 Check Firmware Version on the New StationTo check firmware version on the new station:

1. Press the [ Power ]button.

2. Press the [ halt ] button on the replaced station

3. Check the current version of the replaced station, using the CPU consoleconnected to COM1(see Indirect Connection with Control Stations, throughIOLAN (Section 7.5.2.3)) , by entering:>>> sh version

4. If the firmware and hardware settings on the replaced station are not theexpected ones, update the firmware and the hardware settings, using theprocedure described in Checks and Updates (Section 7.1.4.2) for DS10RC23 or Checks and Updates (Section 7.1.5.6) for DS10 RC40.

5.7.4.3 Check the SCSI Port SettingsCheck the SCSI Port Settings:

1. Display the current SCSI ID settings:>>> sh |grep host

The SCSI ID for both stations must be 7.

2. If the SCSI ID does not match, change the ID by entering:set <parameter_name> <value>(e.g. pka0_host_id 7)

3. Reconnect the SCSI cables to the SCSI card of the replaced station.

The following sections should be performed only if a DS10/RC40 station isreplaced. Otherwise perform only Restore Unix, Nectar/Tomas and MFS on theNew Station (Section 5.7.4.4) and Start Up New Station* (Section 5.7.5).

Save the omcxchg

directory contents

1. Login as root user on MFS active station

In the console window enter the following command:telnet 1.1.1.x

x is 1 for active station STATION_Ax is 2 for active station STATION_B

Enter the user name and the password

2. Create an archive of the omcxchg directory to copy all its contentscd /omcxchgcd ..tar cvf omcxchg.tar omcxchgchmod 755 omcxchg.tar

78 / 176 3BK 20935 AAAA PCZZA Ed.20


3. Transfer via ftp the omcxchg archive from the active MFS station to PC. Fromthe PC perform the following steps:Connect as omcxchg user (password Omcxchg) to activestation via ftp:

ftp 1.1.1.xx is 1 for the active station STATION_Ax is 2 for the active station STATION_B

4. Copy the omcxchg archive to the PC:cd /omcxchgcd ..promptbinget omcxchg.tarby

Save the BACKUP

directory contents


In the console window enter the following command:telnet 1.1.1.x


Enter the user name and password

2. Create an archive of the BACKUP directory to copy all its contentscd /BACKUPcd ..tar cvf BACKUP.tar omcxchgchmod 755 BACKUP.tar

3. Transfer via ftp the BACKUP archive from the active MFS station to PC.From the PC perform the following steps:Connect as omcxchg user (password Omcxchg) to activestation via ftp:

ftp 1.1.1.xx is 1 for the active station STATION_Ax is 2 for the active station STATION_B

4. Copy the BACKUP archive to the PC:cd /BACKUPcd ..promptbinget BACKUP.tarby

Check Data Backup file On the active station, check in usr/backup_mib if the desired backup file torestore is present. If not, make a backup of MFS as follows:

1. From the GPRS Terminal window, follow the menu path:Backup/Restore->Data Backup/Restore->Backup

2. The Backup dialog box opens

3. Enter the backup file name

4. Click on [OK].

3BK 20935 AAAA PCZZA Ed.20 79 / 176


When the backup is complete, the Backup Done window opens. It showsthe backup file name, together with the date and hour of the backup. Theidentity of the MFS is included at the start of all backup file names.

Note: If the backup file has been previously copied on a safe place, different than/usr/backup_mib, copy the file in the /usr/backup_mib directory. Remove orsave all backup files more recent than the chosen one (remove for instancethe string “backup” from their name). The required backup file name mustinclude the string “backup”.

5.7.4.4 Restore Unix, Nectar/Tomas and MFS on the New StationTo restore Unix, Nectar/Tomas and MFS on the new station:

1. Depending on the station type ( DS10 RC23 or DS10 RC40 ), verify allprerequisites from System Backup for MFS DS10 RC23 (Section 5.3) orSystem Backup for MFS DS10 RC40 (Section 5.5)

2. Use System Backup for MFS DS10 RC23 (Section 5.3) or System Backup forMFS DS10 RC40 (Section 5.5) to restore Nectar and MFS on new station.

The following steps are to be performed only in case of a DS10/RC40 stationreplacement procedure:

3. Press Eject on MFS DAT drive in order to eject the tape from the standbystation.

Stop Nectar on both

stations:

4. Stop Nectar on both stations, beginning with the standby station:/usr/mfs/bin/mfs_stop_nectarTo stop nectar, the station should be restarted. Doyou want to reboot (y/n)?y

Wait until the stations become available.

Launch install_rc40_lsm 1. Close the existing connections. In a new console window enter the followingcommand:

telnet <external IP address of the active controlstation>

2. Enter the user name and the password:login:<enter your user name>password:<enter your password>

After this step you are connected on the console of theactive control station.

3. From the current control station connect on the other control station:telnet 1.1.1.20 port_standby


Trying 1.1.1.20...Connected to 1.1.1.20Escape caracter is ’^]’

At this step press [ ENTER ] in order to see the prompt[ ENTER ]

If necessary enter the user name and password to accessthe station.

4. Perform the same steps for the active station. In a new console windowenter the following command:

80 / 176 3BK 20935 AAAA PCZZA Ed.20


telnet <external IP address of the standby controlstation>

5. Enter the user name and the password:login:<enter your user name>password:<enter your password>

After this step you are connected on the console of thestandby control station.

6. From the current control station connect on the other control station:telnet 1.1.1.20 port_standby


Trying 1.1.1.20...Connected to 1.1.1.20Escape caracter is ’^]’


If necessary enter the user name and password to accessthe station.

7. Launch install_rc40_lsm on the active station. Confirm the messages thatappear while the script is running and then wait for the action to finish.

/usr/mfs/bin/install_rc40_lsm

Note: When a message notifies the operator that the shared files are OK, the operatorcan continue with the next steps.

8. Connect as root to the active station and perform the following:/usr/nectar/bin/nfm_stop/usr/nectar/bin/nfm_start/usr/nectar/bin/nfm_removedisk /dev/rdisk/dsk1g/usr/nectar/bin/nfm_stop/usr/mfs/bin/mfs_stop_nectar

Note: The standby station reboots. Wait for the station to be available again.

9. Connect as root to the standby station and perform the following:dd if=/dev/zero of=/dev/disk/dsk1g bs=1k count=500mv /usr/nectar/var/data/fma.mkfs.backup/usr/nectar/var/data/fma.mkfschmod 755 /usr/nectar/var/data/fma.mkfs/usr/nectar/bin/nfm_startp/usr/nectar/bin/nfm_stop

10. Reboot the standby station manually.reboot

Wait for the station to be available again.

11. Start Nectar on the active station:# /usr/mfs/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished.

12. Start Nectar on the standby station:# /usr/mfs/bin/mfs_start_nectar -site


13. As soon as the stations are operational, connect to IMT:

Select View->Nectar View to check that the availability and operationalstates are:

3BK 20935 AAAA PCZZA Ed.20 81 / 176



Operational state: Enabled

Restore the omcxchg

directory contents

1. Connect as omxchg user (password Omcxchg) via ftp from the PC to MFS:ftp 1.1.1.x


put omcxchgby

2. Login as root user on MFS active station:In the console window enter the following command:

telnet 1.1.1.xx is 1 for active station STATION_Ax is 2 for active station STATION_BEnter the user name and password.

3. Extract the omcxchg archive:tar xvf omcxchg.tar

Restore the BACKUP

directory contents

1. Connect as omxchg user (password Omcxchg) via ftp from the PC to MFS:ftp 1.1.1.x


put BACKUPby

2. Login as root user on MFS active station:In the console window enter the following command:

telnet 1.1.1.xx is 1 for active station STATION_Ax is 2 for active station STATION_BEnter the user name and password.

3. Extract the BACKUP archive:tar xvf BACKUP.tar

5.7.5 Start Up New Station*

Note: (*) This section is to be performed only for MFS DS10/RC23 station.

1. If not already done, start the MFS application:/usr/MFS/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished, when telnet ispossible again on the station.

2. Check, after a few minutes, that the replaced station is in the standby mode.

3. If this is not successful, contact your Alcatel System Support.

82 / 176 3BK 20935 AAAA PCZZA Ed.20


5.8 Replace StorageWorks Shelf (*)

Note: (*) StorageWorks is present only for MFS with DS10/RC23. This section is notapplicable for MFS with DS10/RC40.

This section describes how to replace a unit containing the shared disk/powersupply/fans due to SCSI bus malfunction or faulty ventilation, for a MFS withDS10 RC23.

Power supplies Bus address switch

9GBDPVDAT01

Figure 35: The BA356 StorageWork Shelf

5.9 Prerequisites

You must identify the holder which is not operational

Ensure that the available replacement is of the same type

You will need a flat blade screwdriver for the operation.

5.9.1 Remove the Shelf

To remove the shelf:


2. Switch off the power supply units.

When removing the cables to the holder, pay strict attention to thepositioning of each cable.

3. Disconnect the power cable from the 180W Power Supply.

4. Unscrew and remove the SCSI cables.

5. Remove the power supply cables.

6. Unscrew the retaining clips for the holder using the screwdriver.

7. Remove the holder containing the disk(s) and power supply units.

3BK 20935 AAAA PCZZA Ed.20 83 / 176


5.9.2 Insert New Shelf

To insert a new shelf:

1. Position the replacement holder and fix in place using the retaining clips.

2. Use the handles to unclip and extract the power unit(s) and hard disk(s)and replace them in the corresponding positions in the new holder. Thepositioning is important as the bus positions are recognized addresses inthe NECTAR configuration.

3. Replace the SCSI connectors in the same relative positions.

4. Replace the power cables and switch on the power supply units.

5. Restart the station and run the hardware test.

6. Unlock the station to recreate a duplex platform and synchronize the disks.

7. Check via NECTAR that:

The platform is operational



9. If the replacement is not successful, contact your Alcatel System Support.

5.10 Replace a Shared Disk (*)

Note: (*) StorageWorks is present only for MFS with DS10/RC23. This section is notapplicable for MFS with DS10/RC40.

This section describes the replacement of a faulty shared disk for an MFSwith DS10 RC23.

Figure 36: Pressing Bezel Tabs

84 / 176 3BK 20935 AAAA PCZZA Ed.20


5.10.1 Possible Other Failure Origins

1. The origin for the disk failure alarm could be due to the disk or the powersupplies; check the power supplies and replace them if necessary, seesection Replace 180W Power Supply (*) (Section 5.11).

2. The reason for disk failure could be due to overheating because of fanfailure. Verify that the fans are in working order, see section ReplaceBlower (*) (Section 5.14).

Upper LED Lower LED Diagnosis

On ON The shared disk is not responding to control signals

On Flashing One of the following conditions exists:

The disk is active and spinning down due to a fault.

The controller has issued the locate command (NOT a fault condition.

Off Flashing One of the following conditions exists:

Due to a fault condition, the controller is spinning down the disk.

The controller ha issued the locate command (NOT a fault condition).

Off On The disk is inactive and spun down.

Table 2: Shared Disk Diagnosis by LEDs

5.10.2 Prerequisites

1. Identify the shared disk to be replaced physically by obtaining the nameof the device, use the command:

voldisk list

Example:

DEVICE TYPE DISK GROUP STATUS

rz0h simple rz0h rootdg online

rz24 sliced ____ ______ online

rz16 sliced diskA nsedg online

___ ______ diskB nsedg

rz24 is failed

2. Identify the shared disk to be replaced functionally by obtaining the functionalnames in the related alarm or by IMT (In the IMT window:View -> NectarView -> srSTA1/srSTA2 ).

Example for DS10:

rz24corresponds to rack1_srSTA1_A obiect name in the alarm

rz16corresponds to rack1_srSTA1_B obiect name in the alarm

In the example given, is an alarm relative to the object namerack1_srSTA1_A , then conclude where is located the failed disk. In ourexample the failed rz24 is located on Station A side

3BK 20935 AAAA PCZZA Ed.20 85 / 176


The name of the disk given by the voldisk list command does notcorrespond to the functional name.

3. Examine the StorageWorks Shelf to identify and verify the name of the disk.

4. Ensure that the available exchange disk is of the same type. You will need aflat blade screwdriver for the operation.

5.10.3 Remove Shared Disk

To remove the Shared Disk:


2. Use the handles to unclip.

3. Extract the disk.

5.10.4 Insert the New Shared Disk

To insert the new Shared Disk:

1. Insert the replacement disk, until it clips into position.

2. In the IMT window:

View -> Nectar View

3. In the Nectar View window, select the failed object (name is given in thealarm with message I/O device error ) and right on it:

-> Disk_recover

4. Check at OMCR that:

The new disk is operational


5. If this is not successful, contact your Alcatel system support.

86 / 176 3BK 20935 AAAA PCZZA Ed.20


5.11 Replace 180W Power Supply (*)

Note: (*) 180W Power Supply is present only for MFS with DS10/RC23. This sectionis not applicable for MFS with DS10/RC40.

This section describes how to replace a faulty 180 watt power supply for theshared disks holder.

Both 180W power supplies are located on the left-hand side, when facing theStorageWork shelf.

You must identify the power supply to be replaced functionally and physically

You must only work on one 180W Power Supply at a time, while leaving theother active.

Figure 37: 180W Power Supply

3BK 20935 AAAA PCZZA Ed.20 87 / 176


5.12 LED DisplayThe power supply in the StorageWorks shelf is equipped with two LEDs:

The upper LEDs (SHELF_OK, farthest from the power cable) indicate the

fan working status

The lower LEDs (POWER_OK, nearest to the power cable) indicate the

power supply working status. A green LED indicates normal working status.

When a power supply develops a fault, the SHELF_OK LEDs are both off,and the POWER_OK LED of the faulty power supply is off. Ensure that thereplacement power supply is of the same type.

5.12.1 Remove 180W Power Supply

To remove 180W Power Supply:

1. Open the front doors of the MFS, and connect the anti-static wrist strap

2. Disconnect the power cable from the 180W Power Supply.

3. Press the bezel tabs together to release the 180W Power Supply and pullout, using both hands (see Figure 36).

5.12.2 Insert New 180W Power Supply

To insert a new 180W Power Supply:

1. Push the new 180W Power Supply in, until the bezel tags engagethemselves in the shelf.

2. Connect the power cable to the new 180W Power Supply.


4. If the replacement is not successful, contact your Alcatel System Support.

88 / 176 3BK 20935 AAAA PCZZA Ed.20


5.13 Replace DAT Drive PVDAT01 (*)

Note: (*) DAT Drive is present only for MFS with DS10/RC23. This is not applicablefor MFS with DS10/RC40.

This section describes how to replace a DAT Drive for a MFS with DS10 RC23.

Do not try to remove the DAT Drive for MFS with DS10/RC40, in this casethe whole station must be replaced.

5.13.1 Remove PVDAT01

To remove PVDAT01:


2. Press the bezel tabs together to release the PVDAT01 and pull out, usingboth hands (see Figure 36).

5.13.2 Insert New PVDAT01

To insert a new PVDAT01:

1. Push the new PVDAT01 in, until the bezel tags engage themselves inthe shelf.


3BK 20935 AAAA PCZZA Ed.20 89 / 176


5.14 Replace Blower (*)

Note: (*) The Blower is present only for MFS with DS10/RC23. This is not applicablefor MFS with DS10/RC40.

There are two Blowers at the rear of each StorageWork shelf. If one Blowerfails, the second Blower switches to high speed and the upper 180W PowerSupply LED is off.

Connector

Screw

Blower

Exhaust

Mounting tab

Blower

Exhaust

Screw

Figure 38: Blowers at Rear of SupplyWork Shelf

5.14.1 Remove Blower

To rRemove Blower:


2. Unscrew the safety screws that secure the Blower to the subrack.

3. Press upper and lower mounting tabs together, and pull Blower out.

5.14.2 Insert New Blower

To insert a nNew Blower:

1. Push the new Blower in, until both mounting tags lock in place in the shelf.

2. Secure with the safety screws.


90 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

6 MFS Cables

This section lists all cables used in the MFS. It includes cable lists andconnector position schematics for:

Telecommunications Subrack

Control Station Server.

3BK 20935 AAAA PCZZA Ed.20 91 / 176

6 MFS Cables

Figure 39: MFS AS800 Rack Levels

92 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

BSXTU

BSSKI2

BSXTU

04

2124

39

58

62

67

7376

STORAGE WORK(only for DS10/RC23)

DS10

DS10

IOLAN

HUB500 / SWITCH

HUB500 / SWITCH

HUB500 / SWITCH

HUB500 / SWITCH

STORAGE WORK(only for DS10/RC23)

68 7072 74

Figure 40: MFS DS10 Rack Levels

3BK 20935 AAAA PCZZA Ed.20 93 / 176

6 MFS Cables

BE35

B2BE

35B2

BE35

B2

BE35

B2BE

35B2

BE35

B2

JBET

I

JBET

I

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

BE35

B2BE

35B2

BE35

B2

BE35

B2BE

35B2

BE35

B2

JBET

I

JBET

I

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

Top rack unit (TRU)

Fan unit

Fan unit

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

002 009 016 023 029 035 041 047 053 059 065 071 077 083 089 095 101 107 113 119 125 131 137 143 150 157

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

BDTRU2subrack

BSXTUsubrack

BSXTUsubrack(optional)

GPU

GPU

GPU

GPU

GPU

GPU

GPU

GPU

Figure 41: Front View of BSXTU Telecomunications Subracks (same forAS 800 and DS 10)

BA35

B2BA

35B2

BA35

B2

BA35

B2

JAET

I

JAET

I

Fan unit

Fan unit

0020090160230290350410470530590650710770830890951011071131191251311371431501571234567891011121314151617181920212223242526

BSXTUsubrack

BSXTUsubrack(optional)

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

BA35

B2BA

35B2

BATTU

0020090160230290350410470530590650710770830890951011071131191251311371431501571234567891011121314151617181920212223242526

JAE1

JAE1

JAE1

JAE1

BAREDC2

JAE1

BA35

B2BA

35B2

BA35

B2

BA35

B2

JAET

I

JAET

I

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

BA35

B2BA

35B2

BATTU

JAE1

JAE1

JAE1

JAE1

BAREDC2

JAE1

BATTU

BATTU

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

JAE1

Figure 42: Back View of BSXTU Telecomunications Subracks (same for AS800 and DS 10)

94 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

6.1 Telecommunications Subrack Cables

There are some cables with theirs ends marked with labels accordingly tothe place where this end should be placed. Consequently, pay attention tothis labels when connect the cables.

For example, for cables interconnecting 2 different subracks, each end (mayhave) a label on which is written:

subrack’s corresponding intervention level or/and

board’s slot number or/and or/and

board’s connector related information

CableMnemo

ItemReference

Level ofIntervention

Slot(Start/Finishedif relevant)

Comment

BE35B 3AA 21 002 There is one connector and 6black wires connected inside.

BE35B BW00613AA 21 009 There is one connector and 6black wires connected inside.









3BK 20935 AAAA PCZZA Ed.20 95 / 176

6 MFS Cables

CableMnemo

ItemReference

Level ofIntervention


Comment



Table 3: Cable List of Rear RIT BA35B2

JAETIADR IN ADR2 ADR OUT ALEXT

DAYLOOPSADR3ADR1

RS TRU

ETH

SYN

ALEXT

Figure 43: JAETI Connectors

Cables/StrapsMnemo

ItemReference

Link Level ofIntervention


Slot Memo onBoard/Hub/Switch

JLHALA 3BK08688CL From 21 137 ALEXT

To 76 150 ALA

To 76 143 ALA

BLAAA 3AF02912AW From 21 137 ALEXT

To 21 023 ALEXT

JLADR1(strap)

3BK 08594 ABAA N.A. 21 023 ADR.IN (Telecomsubrack 1)

* BLAAA 3AF02912AN From 21 023 ADR.1(Telecomsubrack 1)

To 39 023 ADR.IN (Telecomsubrack 2)

JLADR1(strap)

3BK 08594 ABAA N.A. 21 137 ADR.IN (Telecomsubrack 1)

* BLAAA 3AF02912AN From 21 137 ADR.1(Telecomsubrack 1)

To 39 137 ADR.IN (Telecomsubrack2)

JLERH 3BK08448CA From 21 023 ETH

96 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

Cables/StrapsMnemo

ItemReference




To 72 09

JLERH 3BK08448CA From 21 137 ETH

To 74 09

JLERH 3BK08442CN From 39 023 ETH

To 68 09

JLERH 3BK08442CN From 39 137 ETH

To 70 09

BLTLM 3BK08442CN 21 023 TRU

BLTLM 3BK08442CN 21 137 TRU

* : Only if Second Telecom Subrack is plugged in MFS. If not, the corresponding end remains unused.

Table 4: Cable&Strap List of Rear RIT JAETI

3BK 20935 AAAA PCZZA Ed.20 97 / 176

6 MFS Cables

CableMnemo

ItemReference

Link LevelofIntervention



JLERH 3BK08442CN From (Back View) 21 029 00

To (Front View) 72 HUB/ SWITCH 01




























98 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

CableMnemo

ItemReference







JLERH 3BK08442DA From (Back View) 21 131 00


























3BK 20935 AAAA PCZZA Ed.20 99 / 176

6 MFS Cables

CableMnemo

ItemReference










JLERH 3BK08442CA From (Back View) 39 29 00























100 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

CableMnemo

ItemReference

































3BK 20935 AAAA PCZZA Ed.20 101 / 176

6 MFS Cables

CableMnemo

ItemReference
















Table 5: Cable List of Rear RIT BATTU

CableMnemo

ItemReference



JLHPS3 3BK08687AN From 76 134

- - To 70 -

JLHPS3 3BK08687AN From 76 150

- - To 68 -

Table 6: Cable List of RIT JAHPS

102 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

6.2 Station, Hub/Switch and IOLAN Cables

SCSI

1

2

3

4

COM1

COM2

TWO

USBParallel Port

ETH A ETH B

EnetA EnetB

SCSI

Figure 44: DS10 Rear Connectors

PVCORD17Position Label

C1

C2 C3

Marking LabelC1C2C3

PVTERM 03

Figure 45: SCSI Adaptor Cable and Termination

3BK 20935 AAAA PCZZA Ed.20 103 / 176

6 MFS Cables

Detail

H1 (HUB/SWITCH)

H2 (HUB/SWITCH )

H3 (HUB/SWITCH)

H4 (HUB/SWITCH)

ALETHC cables each connected to port 24

Figure 46: HUB/SWITCH, Front Connectors (ALETHC cable allowed onlyfor SWITCH)

H1

H2

H3

H4

CAHUB

RPS

Figure 47: Hub, Rear Connectors (not possible if SWITCH are used)

104 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

Serial Ports10BASE−TConnector

1 2 3 4 5 6 7 8 10B

JLPS

Figure 48: IOLAN Rear Connectors

CableMnemo

ItemReference


Slot(Start /Finished ifrelevant)


PVUSM088 1AF01980AAAA 58 StorageWorks

PVDAT01 1AF01985AAAA 58 DAT

PVDD42 1AF01978AAAA 58 Disk

PVADA21 1AF01981AAAA 58 Hub/Switch

PVCORD16 1AF01977AAAA From 58 CV1 ST.W/IDCEM

To 49 A1


To 51 B1

PVCORD18 1AF01982BAAA From 58 PM1 ST.W/PVCORD17

To 67 C2


To 73 C2

PVUSM088 1AF01980AAAA 62 StorageWorks

PVDD42 1AF01978AAAA 62 Disk

PVADA21 1AF01981AAAA 62 Hub/Switch


To 49 A2


To 51 B2


To 67 C2

3BK 20935 AAAA PCZZA Ed.20 105 / 176

6 MFS Cables

CableMnemo

ItemReference





To 73 C2

PVSERV63 1AF01984CAAA 67 DS10

PVCORD16 1AF01977AAAA From 67 DS10/IDCEM

To 49 A3

JLRJDB 3BK08614BT 67 C01 DS10

PVCORD17 1AF01983BAAA 67 3 DS10


PVTERM03 1AF01987BAAA 67 3/C3 PLA


PVSERV63 1AF01984CAAA 73 DS10

PVCORD16 1AF01977AAAA From 73 DS10/IDCEM

To 51 B3

JLRJDB 3BK08614BT From 73 C01 DS10

To 76 3





JS19P 3BK25439AA 76

TSERV 1AF01511BCAA 76 IOLAN

CAHUB 1AF01516AAAA From 76 H1 Hub

To 76 H3

CAHUB 1AF01516AAAA From 74 Hub

To 70

CAHUB 1AF01516AAAA From 77 Hub

To 68

HUB500/SWITCH

1AF01508ABAA From 76 H1 Hub/ Switch +ALIM 220V

To 49 A4

106 / 176 3BK 20935 AAAA PCZZA Ed.20

6 MFS Cables

CableMnemo

ItemReference




CAHUB 1AF01516AAAA From 76 H2 Hub

To 76 H4

HUB500/SWITCH


To 51 B4

HUB500/SWITCH


To 49 A5

HUB500/SWITCH


To 51 B5

IDIO48 3BW11354AA From 76 IOLAN

To 04 B4/40

ALETHD 3BW01804CL From 67 ETH A DS10

To 76 H3/21

ALETHD 3BW01804CL From 67 ETH B DS10

To 76 H4/21

ALETHD 3BW01804CL From 73 ETH A DS10

To 76 H3/22

ALETHD 3BW01804CL From 73 ETH B DS10

To 76 H4/22

ALETHD 3BW01804CL From 76 H3 Hub/Switch

To 76 10B

ALETHC 3BW01805AL From 76 H1/24 Switch

To 76 H3/24

ALETHC 3BW01805AL From 76 H2/24 Switch

To 76 H4/24

BLTLM 3AF02986BT From 04 028/X2

To 21 137/TRU

3BK 20935 AAAA PCZZA Ed.20 107 / 176

6 MFS Cables

CableMnemo

ItemReference




BLTLM 3AF02986BT From 04 105/X2

To 21 023/TRU

Table 7: Cable List of Station, Hub/Switch and IOLAN

6.3 External Cabling to AGPS Server1. Connect the Ethernet cables into external router.

2. Run the Ethernet cables (ALETHD) inside the rack, through a free cell ofcable gland (or in CG1 if bottom entry of cables, see Figure 49).

Figure 49: Run Ethernet cables through Cable Gland

3. Bring the both Ethernet cables with the connector at the front side of therack (at the HUBs subrack level).

See Figure 50.

HUBHUB

IOLAN

IOLAN

AS 800 DS 10

HUB

HUB

Figure 50: Running the two Ethernet cables at lateral side of rack

4. Ensure that the end of the cable has 50 cm free for allowing connection tothe HUBs and attach the cables to the rack (don’t connect the cables).

5. Label the cables with supplied labels.

6. Connect the two Ethernet cables into the hubs, one cable per hub.

Connect the cables into free position in the HUBs connection area.

108 / 176 3BK 20935 AAAA PCZZA Ed.20

7 Software Procedures


This section describes how to install and configure the MFS.

The section is divided into:

Initial Software Installation

Initial Configuration

Change Configuration of a Running MFS

NECTAR procedures

Miscellaneous tasks.

3BK 20935 AAAA PCZZA Ed.20 109 / 176


7.1 Initial Software InstallationThis section describes how to install firmware, Unix, Nectar and MFS Softwareon both stations.

There are three type of MFSs, depending on control station type:

AS 800, the middleware software is Tomas RC23

DS10 with network mirroring disks, the middleware software is Tomas RC23This kind of MFS has storage works, placed on top of DS10 stations

DS10 with local disks, the middleware is Tomas RC40This kind of MFS has no storage works, there is a free space betweenDS10 stations and telecom subracks.

Depending on the equipment, you have to follow the next steps:

Backup NORIMFS file , perform section 7.1.3 for all types of MFSs.

UNIX, Nectar and MFS Software Installation for MFS with AS800 or DS10

RC23 , in this case perform section 7.1.4

Automatic Software Installation (UNIX, NECTAR and MFS Software) for

DS10 RC40 , in this case perform section 7.1.5

After installing UNIX, NECTAR and MFS Software, perform Configure the MFS(Section 7.1.6) and Download and Launch BUL Files (Section 7.1.7) , RestartMFS (Section 7.1.8)., then Restore the NORIMFS File (Section 7.1.9)

If running BSCs have been attached to the MFS and a correct backup of thedatabase is kept, perform also Re-synchronize BSCs with MFS (Section 7.1.10)

At the end of section 7.1 the MFS installation is finished.

If you have running BSSs on the MFS, there is GPRS traffic outage and CStraffic reduction starting with Restart MFS (Section 7.1.8).

7.1.1 Prerequisites

Before starting the MFS installation the following information are necessary:

IP addresses, netmasks and hostnames of both stations

Alias IP address of the MFS equipment

IP address of the default gateway

IP address and hostname of the NTP Server

MFS id and MFS name

If BSCs have been attached to the MFS, the last correct backup of the MFS

data must be available at OMC-R site.

110 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.2 Note the Synchronization Parameters

This sections describes how to note the synchronization parameters:synchronization mode, master GPU if it is the case, synchronizing PCM-TTP(s).The information is needed when re-synchronizing the BSCs with the MFS. Tonote the synchronization parameters of the MFS station:

1. From the GPRS Terminal window, follow the menu path:

Tools -> Synchronize

The default mode of the MFS Station is displayed. Record thesynchronization mode.

2. To note the synchronizing master GPU, from the GPRS Terminal windowfollow the menu path:

View -> Site ViewA dialog box displays the site in a tree form.

3. Right-click on a subrack object to display a pop-up menu.

4. Click on Synchro Master Def. in the pop-up menu.

5. Note the number of Master GPU and the slot number of each of the MasterGPU from the dialog box.

6. To note the synchronization mode of a PCM-TTP board, from the GPRSTerminal window, follow the menu path:

View -> Site View

The site view opens.

7. Note the PCM-TTP that display a clock icon.

3BK 20935 AAAA PCZZA Ed.20 111 / 176


7.1.3 Backup NORIMFS file

Note Task Description Site To do Outage

- Save the file NORIMFS.TXT on the LMT PC MFS 10 min. None.

To save the file NORIMFS.TXT on the LMT PC, follow the next steps:


In Windows 2000 or Windows XP, click on Start->Run

In the Run Window enter the following command:telnet 1.1.1.x


Enter the user name and the password

2. Copy NORIMFS.TXT from /omcxchg/ri in /usr/users/platformcp /omcxchg/ri/NORIMFS.TXT/usr/users/platform/NORIMFS.TXTchmod 777 /usr/users/platform/NORIMFS.TXT

3. Transfer via ftp the NORIMFS.TXT file from the active MFS station to PC.From the PC perform the following steps:

connect to active station via ftp:ftp 1.1.1.x


Type the login user name with the corresponding password

copy the NORIMFS file to PC:ftp>cd /usr/users/platformftp> get NORIMFS.TXTftp>by

7.1.4 UNIX, Nectar and MFS Software Installation for MFS with AS800or DS10 RC23

This section describes for MFS with AS800 or DS10 RC23 how to

1. Check and update the firmware and SRM hardware settings

2. Install Unix

3. Install the software on both stations.

Each step must be done in the order given.

112 / 176 3BK 20935 AAAA PCZZA Ed.20



The following CD-ROMs are necessary:

Platform AS800 reference DS10 RC23 reference

Firmware Bootable CD DIGITAL Alpha Systems FirmwareUpdate V5.5 CD ROM

DIGITAL Alpha Systems FirmwareUpdate V6.1 CD ROM

UNIX Bootable CD MFS_fast_boot_CD_AS800_B9 MFS_fast_boot_CD_DS10_B9

MFS Software MFS CD-ROM

CD-ROM with Customer BUL files

Table 8: Installation CD-ROMs

The Digital UNIX operating system and the different firmware must beinstalled on both stations

Station AS800 DS10 RC23

DUNIX OS Version DUNIX 4.0F DUNIX 4.0F

SRM Firmware Revision V5.5 V6.1

RMC Firmware Revision V1.0 V1.0 V1.1, V1.2

SRM variable rmc_halt value No variable disable enable

Table 9: Required Operating System and Firmware

7.1.4.2 Checks and UpdatesStop NECTAR on Both Stations

To open a conection with control stations see section Direct Connection with

Control Stations, using MFS Internal Network (Section 7.5.2.1).

If the MFS is running, stop NECTAR on both station:# /usr/mfs/bin/mfs_stop_nectar

Type [ y ] at the question: Do you want to reboot(y/N)?

The reboot is finished, when telnet is possible again on the station.

Check Firmware 1. Check the SRM firmware version.

Enter the following commands on both stations:# /sbin/consvar -d|grep Firmware

Check for AS800:Firmware Rev: 5.5

Check for DS10Firmware Rev: 6.1

Note: In the SRM firmware revision only first two digits are relevant.

2. Only for DS10 RC23: Check the RMC firmware version.

3BK 20935 AAAA PCZZA Ed.20 113 / 176


Log in as root on STATION_A. From STATION_A log in on the STATION_Busing the IOLAN:

telnet 1.1.1.20 10003Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’


If is necessary log in as root on station_B# [ ESC ] [ ESC ] RMCRMC> status

The value shown on the terminal is the RMC firmwarerevision for STATION_B, check the RMC firmware revisionin Table 9.

RMC> quit

Close this terminal

Perform the same operation to see the RMC firmware revision forSTATION_A.

Log in as root on STATION_B. From STATION_B log in on the STATION_Ausing the IOLAN:

telnet 1.1.1.20 10002Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’


If is necessary log in as root on STATION_A# [ ESC ] [ ESC ] RMCRMC> status


RMC> quit

Close this terminal

3. Only for AS800: Licenses are required for DECnet OSI and Digital UNIXsoftware. Some of them have to be registered on both stations:

OSF-BASE

OSF-SVR

OSF-USR

ADVFS-UTILITIES

LSM-OA

DECNET-OSI-EXT.

114 / 176 3BK 20935 AAAA PCZZA Ed.20


Store Information

(AS800 only)

When reinstalling from scratch, a configured MFS stores the licences, backup,mfsid, mfs_inet information. Perform the following ations on one section:

1. Verify if get_licenses script is stored in /var/tmp/delivery:ls /var/tmp/delivery|grep licenses

If the script is not in this directory perform the following procedure in order tocopy this file from MFS SW CD-ROM:

Insert the MFS CD-ROM, in the control station CD-ROM drive

Mount MFS SW CD-ROM and copy the script on control station# mount -r -t cdfs -o rrip /dev/rz4c /mnt# cp /mnt/INSTALL* /var/tmp/delivery# cd /var/tmp/delivery# tar xvf ./INSTALL-XXX.tar (XXX is the versionnumber)

Unmount and remove the MFS SW CD-ROM# umount /mnt

2. Execute this script to save the licences:#/var/tmp/delivery/get_licenses

A tar file is created (AS800_licences.tar ).

3. Get this file (AS800_licences.tar ) via ftp from the PC, and store this fileon PC (it will be needed for the re-installation)

4. Get the backup files which should be in /var/nse/arch (ftp).

5. Get the necessary mfs_id information (write it down: it will be needed forthe re-installation):

# /usr/mfs/bin/mfs_mfsid -p

6. Get the necessary mfs_inet information (write it down: it will be needed forthe re-installation):

# mfs_inet -duplex

Press [ Enter ] several times.

Perform this task on the other station too.

7. Get the network information for the OMC-R. Find this information in the file/etc/snmpd.conf

# cat /etc/snmpd.conf | grep OMC

Find the IP address of the OMC-R in the displayed line.

8. Get the network information for the NTP server. Find this information atthe end of the file /etc/ntp.conf

# cat /etc/ntp.conf

3BK 20935 AAAA PCZZA Ed.20 115 / 176


7.1.4.3 Update FirmwareUpdate the firmware if it is not the right version.

Use the MFS Firmware bootable CD-ROM for your platform. Refer to theTable8 in the Prerequisite section.

Before upgrading the firmware on a control station, the control station mustbe fully physically isolated.

1. Open the IMT. Log in as root user

Enter the ’root’ user name and corresponding password.

Following message automatically displayed on screen: Unauthorized

access to this machine is strictly forbidden and may be

liable to legal proceedings

Click on OK button!

2. Open Nectar View, in the IMT select Views -> Nectar View.

Click successively on the expand button of rack1, srSTA1, srSTA2

Select the standby station

Open the contextual menu using right-click and select Maintenance .The standby station will be restarted.

3. In Nectar View.




4. Log in on active station as root.telnet 1.1.1.x


116 / 176 3BK 20935 AAAA PCZZA Ed.20


5. From the active station, log in on the standby station using IOLAN:telnet 1.1.1.20 port_standby

Note: port_standby is 10002 for STATION_A and 10003for STATION_B

Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’


If is necessary enter user name root and appropriatepassword.Wait for the prompt >>>

Enter in RMC mode and halt out the station:(Press Escape key twice, then type rmc)

>>>[ escape ][ escape ]rmcRMC>halt out [ Enter ]Returning to COM port

Press Enter in order to get back the SRM prompt >>>.

6. Insert the Digital Alpha Systems Firmware Update CD-ROM in the standbystation.

7. Power down the standby station.

8. Remove the Ethernet cables from the standby station.

Note: Check that all Ethernet cables are labeled. This will save you timewhen you reconnect them.

9. In case of DS10 MFS, remove the SCSI cables from the standby station.

Note: Check that all SCSI cables are labeled. This will save you timewhen you reconnect them.

10. Power up the standby station.

Wait for the prompt >>>.

Note: When Unix starts, push the Halt button on the front of the DS10station to get the prompt >>>.

11. DS10 only: Set the environment variable and set the rmc_halt variable.

Read the rmc_halt value>>>show rmc_halt

For RMC FW Revision 1.0>>>set rmc_halt disable

For RMC FW Revision 1.1>>>set rmc_halt enable

12. Boot from the CD-ROM.

For AS800 use:>>> boot dka400

For DS10 RC23 use:>>> boot dqb0

13. Hit [ Enter ] several time to load the latest update.

3BK 20935 AAAA PCZZA Ed.20 117 / 176


14. Update the firmware:UPD> update

Confirm update on :

For AS800:ARCsrm

For DS10 RC23:ntsrm[Y/(N)] y

UPD> exit

15. When update is completed, remove the CD-ROM.

16. Power down the standby station.

17. Reconnect the SCSI cables to the standby station.

18. Reconnect the Ethernet cables to the standby station.

19. Power up the standby station.

20. When the station is powered on, disconnect the system console and closethe Terminal Windows.

21. In the "Nectar View".




Wait until the "Nectar View" displays:


Operational state: Enable.

22. Perform a control station switchover, from IMT select Tools > Switchover.Wait until the switchover is finished, and the IMT connection is recovered.

23. Repeat the same procedure for the other station, (which is now thestandby station).

SRM Hardware Settings 1. Check the mandatory SRM hardware settings with this list:

In SRM mode (with the prompt >>>) type the following command:>>>show

Item AS800 DS10 RC23 withRMC V1.0

DS10 RC23 withRMC V1.1, V1.2

console serial serial serial

auto_action restart restart restart

bootdef_dev dka0.0.0.5.0 dqa0 dqa0

boot_osflags A A A

118 / 176 3BK 20935 AAAA PCZZA Ed.20




boot_reset ON ON ON

bus_probe_algorithm NEW - -

ewa0_protocols BOOTP BOOTP BOOTP

ewb0_protocols BOOTP BOOTP BOOTP

ewc0_protocols BOOTP BOOTP BOOTP

ewd0_protocols BOOTP BOOTP BOOTP

ewe0_protocols - BOOTP BOOTP

ewf0_protocols - BOOTP BOOTP

ewa0_mode twisted pair * fast * fast *

ewb0_mode fast * fast * fast *

ewc0_mode fast* twisted pair * twisted pair *

ewd0_mode fast * fast * fast *

ewe0_mode - fast * fast *

ewf0_mode - fast * fast *

pka0_host_id 7 5 on A system, 6 on Bsystem

5 on A system, 6 on Bsystem

pkb0_host_id 5 on A system, 6 onB system



pkc0_host_id 5 on A system, 6 onB system

- -

pka0_soft_term ON (DIFF) - -

pkc0_soft_term - - -

full_powerup_diags OFF OFF OFF

kbd_hardware_type PCXAL PCXAL PCXAL

language 36 36 36

license MU - -

pkb0_fast 1 - -

pkc0_fast 1 - -

os_type UNIX UNIX UNIX

3BK 20935 AAAA PCZZA Ed.20 119 / 176




pci_party ON ON ON

rmc_halt - disabled enabled

scsi_poll ON ON ON

scsi_reset - ON ON

tt_allow_login 1 1 1

com1_baud - 9600 9600

com1_flow - SOFTWARE SOFTWARE

com1_mode - SNOOP SNOOP

com1_modem - OFF OFF

com2_baud - 9600 9600

Table 10: Hardware Settings for SRM Configuration

* these variables are to set up the values depending on the application needs

ewx0_mode=’fast’ for 100BaseT hub or switch.

ewx0_mode=’twisted-pair for 10BaseT hub or switch.

2. Reconnect the Ethernet network cable.

7.1.4.4 Install UNIXThis section describes how to install UNIX on your platform from the MFSbootable CD-ROM if the current UNIX version is not the correct one.

Use the MFS Bootable CD-ROM for your platform. Refer to Table 8.

If the MFS is running, stop NECTAR on both stations:# /usr/mfs/bin/mfs_stop_nectar



120 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.4.5 PrerequisitesIf the UNIX installation procedure is performed on AS800 control station besure that the procedure Store Information (AS800 only) (in section 7.1.4.2)is perform first.

Start UNIX Installation On both stations and in any order :

1. Log in on one station (not on the station where UNIX will be installed) asroot with appropriate password.

telnet 1.1.1.xx is 1 for STATION_Ax is 2 for STATION_B

2. Connect to the second station using the IOLAN (This is the station onwhich the UNIX will be installed) :

telnet 1.1.1.20 port_standbyNote: port_standby is 10002 for STATION_A and 10003for STATION_B



If is necessary enter user name root with appropriatepassword.Wait for the prompt >>>

3. Stop the station, if it is not already stopped:

if the prompt is not >>>:# sync# sync# halt

wait the prompt >>>

4. Insert the UNIX bootable CD-ROM in the disk drive on the station to beinstalled

5. Boot the CD-ROM:

For AS800:>>> boot dka400

For DS10:>>> boot dqb0

Wait until the station is automatically restarted and the login name is asked:Login:<enter root user name>Password:<From this step on, the root password will be Alcatelor Digital>

Be aware that the UNIX bootable CD is generic. After installation bothstations are configured with the same data, both servers looking asSTATION_A.Only after executing mfs_inet , reconfiguration of the second station toSTATION_B will be complete.You can discriminate the stations only according to their position in thesubrack and IOLAN connections, use only IOLAN connections until network isconfigured (after mfs_inet ).

3BK 20935 AAAA PCZZA Ed.20 121 / 176


6. Edit the file /etc/securettys . Insert at the end a new line containing ptys ,by giving the following command:echo ptys >> /etc/securettys

7. Edit the file: /etc/ftpusers

Delete the line containing the string ’root’. (It is commonly the first line inthe file).

8. Perform the same tasks on the other station

7.1.4.6 Configure Network

In the following procedures:

LEFT station stands for the left station in an AS800 and the top station

in an DS10 MFS

RIGHT station stands for the right station in an AS800 and the bottomstation in a DS10 MFS.

DS10 only : if the new Ethernet card (ee0) is used, ignore all the errors alarmsconcerning tu0.

122 / 176 3BK 20935 AAAA PCZZA Ed.20


1. On the right station enter the following command using the connectiontrough IOLAN:

<RIGHT># mfs_inet -duplex -hostname STATION_B

Note: The following messages are as example, but they can differ depending on theconfiguration.

== System configuration ==Hostname changed from "right" to "STATION_B"."STATION_A root" added to /.rhosts."STATION_B root" added to /.rhostsSTATION_A added to /etc/hosts.STATION_B added to /etc/hosts.== tu0 interface configuration ==Enter the alias name for tu0 : <External name ofSTATION_B>

(The Hostname should not be STATION_A, STATION_B, or ALIAS IP.)Enter <External name of STATION_B> IP address: <IPaddress of STATION_B>Enter "netmask" IP address: <Netmask of STATION_B>Alias hostname for active station is fixed to"station_mfs" or "STATION_MFS"

(The Alias IP should not be STATION_A, STATION_B, or an internalNetwork IP address.)Enter "station_mfs" IP address: <Alias IP of MFS>"station_mfs" is already defined in /etc/hosts withanother IP address: 1.2.3.5 station_mfs STATION_MFSDo you want to remove it [y]?

[ Enter ]Route to the default gatewayEnter the gateway IP address: <IP address of the defaultgateway>Configuring tu0 interface.== tu1 and tu2 interfaces configuration ==Configuring tu1 interfaceConfiguring tu2 interface.== tu3 interface configuration ==Checking only: OK

At the end of this task all the network services are automatically restarted.

Reboot the right station.#reboot

During the reboot, proceed for the left station (next step) with:mfs_inet

When the right station is available see section Direct Connection withControl Stations, using MFS Internal Network (Section 7.5.2.1)

3BK 20935 AAAA PCZZA Ed.20 123 / 176


2. On the left station enter the following command using the connectiontrough IOLAN:

<LEFT> # mfs_inet -duplex -hostname STATION_A

Note: The following messages are as example, but they can differ depending on theconfiguration.

== System configuration ==Hostname changed from "left" to "STATION_A""STATION_A root" added to /.rhosts."STATION_B root" added to /.rhosts.STATION_A added to /etc/hostsSTATION_B added to /etc/hosts.== tu0 interface configuration ==Enter the alias name for tu0 : <External name ofSTATION_A>

(The Hostname must not be STATION_A, STATION_B, or ALIAS IP.)Enter <External name of STATION_A> IP address: <IPaddress of <STATION_A>Enter "netmask" IP address: <Netmask of STATION_A>Alias hostname for active station is fixed to"station_mfs" or "STATION_MFS"Enter "station_mfs" IP address : <Alias IP of MFS>

(The Alias IP should not be STATION_A, STATION_B, or an internalNetwork IP address.)"station_mfs" is already defined in /etc/hosts withanother IP address: 1.2.3.5 station_mfs STATION_MFSDo you want to remove it [y]?

[ Enter ]Route to the default gateway:Enter the gateway IP address: <IP address of the defaultgateway>Configuring tu0 interface== tu1 and tu2 interfaces configuration ==Configuring tu1 interface.Configuring tu2 interface.== tu3 interface configuration ==Checking only: OK


3. Reboot STATION_A# reboot


4. Reboot STATION_B# reboot


When the left station is available see section Direct Connection with ControlStations, using MFS Internal Network (Section 7.5.2.1)

7.1.4.7 Install Licenses on Both Stations (AS800 only)The licenses are specific to each AS800 station and are generic for DS10.

Install Licences (only for

AS800)

1. Get the AS800_licences.tar file from the PC and put it in the /var/tmp

directory

2. install the licences:# tar xvf AS800_licences.tar# cd AS800_licences

124 / 176 3BK 20935 AAAA PCZZA Ed.20


# ./install

Check Licences (only for

AS800)

On both stations and in any order :

1. Check the registered software licenses:# /usr/sbin/lmf list

The following six licenses are required:

Product Status Users

OSF-BASE active unlimited

OSF-SVR active unlimited

OSF-USR active unlimited

ADVFS-UTILITIES active unlimited

LSM-OA active unlimited

DECNET-OSI-EXT active unlimited

Table 11: Required Licences

The installation scripts check if all needed licenses are installed.

3BK 20935 AAAA PCZZA Ed.20 125 / 176


2. If one or more of them are missing use the lmfsetup command to registerit/them:

# /usr/sbin/lmfsetupRegister PAK (type q or quit to exit) [template]<Return>Issuer : <Specific to the software>Authorization Number : <Specific to the software>Product Name : <Specific to the software>Producer : <Specific to the software>Number of units : <Specific to the software>Version : <Specific to the software>Product Release Date : <Specific to the software>Key Termination Date : <Specific to the software>Availability Table Code : <Specific to the software>Activity Table Code : <Specific to the software>Key Options : <Specific to the software>Product Token : <Specific to the software>Hardware-Id : <Specific to the software>Checksum : <Specific to the software>PAK registered for template successfullyRegister PAK (type q or quit to exit) [template] qYou have registered at least one new PAK. Until itis loaded by use of the lmf reset, lmf load for eachnewly registered PAK, or rebooting your system,software dependent on them will be treated as if theregistrations had not been performed.Would you like a lmf reset to be performed at thistime? [Yes] <Return>

3. Perform the same tasks for the other station.

Note: <Specific to the software> is the information given in the license note.

7.1.4.8 Install NECTARNECTAR can be installed only in Duplex mode.

Duplex mode means installation on both stations; data backed up on shareddisks; defense of stations, software replacement.

Start NECTAR

Installation


1. Insert the CD-ROM MFS Software.

2. Create the delivery directory# mkdir /var/tmp/delivery

3. Put the software package in the /var/tmp/delivery directory

See Download Possibilities (Section 7.5.1.1).


Extract Installation

Script Package


1. Check the version:cd /var/tmp/deliveryls | grep INSTALL

The version of the INSTALL-XXX.tar is displayed.

2. Extract the installation script package on each station:tar xvf ./INSTALL-XXX.tar (XXX is the version nr.)

126 / 176 3BK 20935 AAAA PCZZA Ed.20



This tar file includes the following installation scripts:

install_3rd_party

install_mfs

uninstall_mfs

indus_libscp

mfs_inet

mfs_start_nectar

mfs_stop_nectar.

get_licenses

install_lsm

mfs_platform_name

3BK 20935 AAAA PCZZA Ed.20 127 / 176


7.1.4.9 Install Third-Party SoftwareThe third-party software is DECNet OSI, Digital UNIX Patches, NECTARNGP231, NECTAR Hot codes, Apache Web Server, additional DUNIX V40Fpackages.

Now, the left station is named STATION_A and the right station is namedSTATION_B.

Install 1. Enter the following command:<STATION_A> #cd /var/tmp/delivery<STATION_A> # ./install_3rd_party -duplex -master-reinstall

Depending on the state of the station, the script can ask questions and/orreboot the station.

2. If the partition of the Shared Disk is wrong, it should be recreated:A new FM configuration will be done. All existing dataon the shared Disk will be destroyed. Do you want tocontinue (y/N)? y

Note: Sometimes, after the FM configuration , the install script stops with thefollowing error:

Figure 51: Configuration Error

In this case, reboot the station and relaunch the installation:<STATION_A> # reboot

The reboot is finished, when telnet is possible again on the station.Reconnect with telnet and launch:

<STATION_A> # cd /var/tmp/delivery<STATION_A> # ./install_3rd_party -duplex -master

Do not launch any command on STATION_B during this step.

3. After the installation has been completed on STATION_A, (no errormessage), on STATION_B, enter the following command:

<STATION_B> #cd /var/tmp/delivery<STATION_B> # ./install_3rd_party -duplex -slave

Wait until this task is finished.

4. Reboot both control stations.

On station A:<STATION_A> # reboot

On station B:<STATION_B> # reboot

Wait until both stations reboot, when direct connection (telnet) is possibleagain on each station.

128 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.4.10 Install MFS SoftwareThe MFS software consists of OAM and GPU components.

1. On STATION_A, enter the following command:<STATION_A> #cd /var/tmp/delivery<STATION_A> #./install_mfs MFS -master

Answer Yes to the question:Do you want to install OAM-MFSB9.xx-xx andGPU-MFSB9.xx-xx(Y/n)? < Y>

Do not launch any command on STATION_B during this step.

2. After the installation has been completed on STATION_A, (no errormessages), on STATION_B, enter the following command:

<STATION_B> #cd /var/tmp/delivery<STATION_B> #./install_mfs MFS -slave

Answer Yes to the question:Do you want to install OAM-MFSB9.xx-xx andGPU-MFSB9.xx-xx(Y/n)? < Y>

The following error may occur: "ERROR: Can’t mount file systems of

shared disks (ret=1 FMHOST=STATION_A) ".Only in this case , perform the following steps:

Enter the following command to force the un-installation of the MFS software

already installed:<STATION_B>#./uninstall_mfs MFS -noSWR

When the process above is terminated, reboot both control stations.

Wait until the reboot is finished, when direct connection (telnet) is possible

again on the station. If both stations have finished the UNIX restart, enterthe following command which will be successfully executed:

<STATION_B>#./install_mfs MFS -slaveAnswer Yes to the question:Do you want to install OAM-MFSB9.xx-xx andGPU-MFSB9.xx-xx(Y/n)? < Y>

3. Check that the installation of the new OAM and GPU software is correct:<STATION_A> # /usr/mfs/bin/mfs_version<STATION_B> # /usr/mfs/bin/mfs_version

MFS version: <MFS Version> :<OAM Version> <GPUVersion>

Some GPU and/or OAM subsets of the following release(s) are installed:<GPU Version><OAM Version>

3BK 20935 AAAA PCZZA Ed.20 129 / 176


7.1.5 Automatic Software Installation (UNIX, NECTAR and MFS Software)for DS10 RC40

This section describes the following steps:

1. Installation of TCL/ Expect and installation scripts, see Preparation forNectar Automatic Installation (Section 7.1.5.5).

2. Check and update the firmware and SRM hardware settings, see Checksand Updates (Section 7.1.5.6).

3. Automatic installation of Unix OS, Tomas and the MFS software on bothstations, see Automatic Installation (Section 7.1.5.7).


The following CD-ROMs are necessary:

Platform DS10 RC40 reference

UNIX Bootable 2 CDs* DSBCD-DUNIX5.1A-01

MFS Software 2 MFS CD-ROMs* (Nectar RC40)

Table 12: Installation CD-ROMs

* 2 pairs of identical CDs are used, to install the software in parallel onboth stations.

Digital UNIX operating system and different firmware versions are supposed

to be installed on both stations.

Station DS10 RC40

DUNIX OS Version DUNIX 5.1A

SRM Firmware Revision

(Any version from this list is accepted)

6.5

6.6

6.7

6.8

RMC Firmware Revision V1.2

SRM variable rmc_halt value enable

Table 13: Required Operating System and Firmware

This installation is performed only from local PC (LMT), configured with the IPaddress as described in Configure IMT on Windows XP (Section 7.2.3) or inConfigure IMT on Windows 2000 (Section 7.2.4).

130 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.5.2 Required InformationThe following IP addresses and names are necessary to install the MFS

External IP address and name for STATION_A

External IP address and name for STATION_B

Station_mfs IP address (floating IP address)

Gateway

Netmask

OMC hostname and IP address

Ntp server hostname and IP address (only if is different from OMC).

7.1.5.3 Disable the Firewall


If the PC is with Windows XP, disable the firewall MFS 5 min None.

During MFS automatic installation with Expect the Windows XP firewallmust be disabled.If the firewall was enable when you start the operation, be careful to set thefirewall back to enable at the end of the operation.You must be logged on PC as an administrator or a member of theAdministrators group in order to modify the firewall status.

7.1.5.4 Windows XP FirewallThe following procedure must be performed only if the PC used for localterminal, is running Windows XP as operating system.

1. Open Windows Network Connections

Click Start, point to Settings, click Control Panel, and then double-clickNetwork Connections.

2. Select the LAN connection and then in left frame under Network Tasks, clickChange settings of this connection.

The Local Area Connection Properties window is opened.

3. Check the firewall status, depending on the Windows XP service pack:

SP1: Click on the Advanced tab, and see the status of the check box.

SP2: Click on the Advanced tab, click on Settings, in Windows Firewallwindow click on Advanced tab and see the check box corresponding

to your LAN

3BK 20935 AAAA PCZZA Ed.20 131 / 176


4. If the firewall is enable in order to disable the firewall depending of theWindows XP service pack, you have to:

SP1: clear the Protect my computer and network by limiting orpreventing access to this computer from the Internet box

SP2: clear the Local Area Connection box from Network Connection

Settings an click OK

Click on OK in Local Area Connection Properties window.

5. Close the Network Connections window.

7.1.5.5 Preparation for Nectar Automatic Installation

TCL / Expect Installation 1. From Control Panel-> Add/Remove Programs , check that the programExpect5.21 exists

If present, remove Expect5.21 program from the PC.

2. Check on the PC system disk for the presence of the folder C:/Expect.Delete this folder if it is present.

3. Insert delivery support (CD-ROM MFS) containing the Expect environmentand the scripts in the PC

4. From the CD-ROM MFS, in the subdirectory Install/ , select and launchthe setup file:

expect_5_21r1b1_setup.exe

5. Select on the windows as they are appearing:

Welcome!

Choose [ Next ]

More information

Choose [ Next ]

6. Type in the field for Select application folder

C:/Expect

Choose [ Next ]

Program icon folder

Choose [ Next ]

Ready

Choose [ Next ]

Setup was successful

Choose [ Close ], then close the ’Expect-5.21’ window

132 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.5.6 Checks and Updates

Check Firmware on Both

Stations

1. Log in on each station:telnet 1.1.1.x

x is 1 or 2 if active station is STATION_A or STATION_B

2. Stop Nectar on both stations, starting with the standby station:# /usr/mfs/bin/mfs_stop_nectar


Wait until the stations become available, when direct connection (telnet) ispossible again, then log in.

3. Check the SRM firmware version to know the RMC firmware revision, enterthe following commands on both stations:

# /sbin/consvar -dFirmware Rev: 6.5.15

Note: The check is OK if the firmware version is conform with Table13. In the SRMfirmware revision only the first two digits are relevant.

4. Check the RMC firmware version.

Note: Use the Expect telnet to open the connections for checking RMC, notthe MS-DOS command shell. In Windows select [ Start -> Programs->Expect-5.21–>telnet ]

Log in as root on STATION_A. From STATION_A log in on the STATION_Busing the IOLAN:

open 1.1.1.20 10003Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’


If is necessary enter user name and password.# [ ESC ] [ ESC ] RMCRMC> status


RMC> quit

Close this terminal

Perform the same operation to see the RMC firmware revision forSTATION_A.

Log in as root on STATION_B. From STATION_B log in on the STATION_Ausing the IOLAN:

open 1.1.1.20 10002Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’


If is necessary enter user name and password.# [ ESC ] [ ESC ] RMCRMC> status


RMC> quit

3BK 20935 AAAA PCZZA Ed.20 133 / 176


Close this terminal.

In case you need to update the firmware, request for Alcatel support. You needa MFS bootable CD-ROM.

Update Firmware 1. If MFS is already running, verify that firmware update is performed onstandby station

2. Stop Nectar on standby station# /usr/mfs/bin/mfs_stop_nectar

Confirm the reboot and wait until the reboot is finished, when directconnection (telnet) is possible again on the station.

3. Insert the Firmware Update CD-ROM provided by Alcatel.

4. Stop the station:# sync# sync# halt

5. Log in on active stationtelnet 1.1.1.x


6. From the active station log in as root user in the standby station usingthe IOLAN :

telnet 1.1.1.20 port_standbyNote: port_standby is 10002 for STATION_A and 10003for STATION_Bwait the prompt >>>

7. Boot the CD-ROM>>> boot dqb0

8. Hit <Enter> several time until to load the latest update.

9. Update the firmware.UPD> update

Confirm update on :ntSRM[Y/(N)] y

UPD> exit

10. When the update is completed, remove the CD.

11. Close the terminal and close the window

12. Wait until the standby station reboots, when direct connection (telnet) ispossible again, then connect on the standby station and start Nectar:

# /usr/mfs/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished, when directconnection (telnet) is possible again.

Perform a control station switchover and then upgrade the firmware on theother station.

134 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.5.7 Automatic Installation

Stop NECTAR on Both

Stations

1. Open a connection with control stations see section Direct Connection withControl Stations, using MFS Internal Network (Section 7.5.2.1)

2. If the MFS is running, stop NECTAR on both station:# /usr/mfs/bin/mfs_stop_nectar



Installing UNIX OS

and MFS

1. From the CD-ROM MFS, in the subdirectory Install , select and launch theWinzip auto-extract file :

Install_RC40B_xxx.exe

2. In the window ’WinZip - self extractor’ choose [ Unzip ], then [ OK ] and[ Close ]

3. Insert the UNIX CD-ROM disks in both MFS stations.

4. From the MFS CD-ROM (on the local PC terminal), select and launchthe script:

install.bat

The following message appears:To start press y and return, to quit press any othercharacter(s) and return.

Type y, than press [ Enter ].

The installation takes about 4h 25min and is finished when the followingmessage is displayed:-I- (12-20-05 16:13): Execution completed instart<inall/STATION_B>: Doneend of inall A+BEND OF INSTALLATION OF MFS OKPress any key to continue...

Note: If a window (’cmd.exe - No Disk’) appears at the end of the installation process,ignore it (press [ Cancel ]).

At this state, the Unix OS, the Tomas and MFS software are installedon both workstations. The MFS configuration is completed, theTomas and MFS processes are started in configuration mode onthe STATION_A.

5. Remove the two UNIX CD-ROMs from control stations and the MFSCD-ROM from the local PC terminal..

6. Open telnet sessions on control stations using MFS local network.

7. The MFS is started with default values (IP addresses, MFS ID, ...). Tochange these values, first stop Nectar and MFS processes on STATION_Awith command:

<STATION_A> #/usr/mfs/bin/mfs_stop_nectar

Confirm the reboot request.

Wait until the reboot is finished and UNIX is restarted.

Connect again with the terminal on STATION_A.

3BK 20935 AAAA PCZZA Ed.20 135 / 176


8. On the Control Station B (IP address 1.1.1.2), enter the following command:<Station_B> #/usr/mfs/bin/mfs_inet -duplex -hostnameSTATION_B

== System configuration ==Hostname: "STATION_B"."STATION_A root" added to /.rhosts."STATION_B root" added to /.rhosts/etc/hosts up to date== tu1 and tu2 interface configuration ==ee0:flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>inet 1.2.3.4 netmask ffffff00 broadcast 1.2.3.255 ipmtu1500==ee0 interface configuration==Enter the alias name for ee0 [laniob] : <External nameof STATION_B>

(The Hostname should not be STATION_A, STATION_B, or ALIAS IP.)Enter ’laniob’ IP address [1.2.3.4]: <IP address ofSTATION_B>

(Configure the IP Address with an IP address different of the internalNetwork (1.1.1.x or 2.2.2.x) for example 1.2.3.4.)Enter ’netmask’ IP address [255.255.255.0]: <Netmaskof STATION_B>hostname for active station fixed to "station_mfs" or"STATION_MFS"Enter "station_mfs" IP address[1.2.3.6]: <Alias IPof MFS>

(The Alias IP must not be STATION_A, STATION_B, nor an internal NetworkIP address; for example 1.2.3.8)’station_mfs’ is already defined in /etc/hosts withanother IP address: 1.2.3.6 station_mfs STATION_MFSDo you want to remove it [y] ? YRoute to the default gatewayEnter the gateway IP address [1.2.3.252]: <IP addressof the default gateway>Configuring ee0 interface.shutdown ee0 interfaceTo take into account network modifications, networkservices should be restartedAll connections (rlogin, telnet...) using networkinterfaces may be closedDo you want to restart the network services [y]? Y

The folowing IP addresses must be the same on both stations:

Station_mfs

Gateway

Netmask.

136 / 176 3BK 20935 AAAA PCZZA Ed.20


9. On the Control Station A(IP address 1.1.1.1), enter the following command:<Station_A>#/usr/mfs/bin/mfs_inet -duplex -hostnameSTATION_A

== System configuration ==Hostname: "STATION_A"."STATION_A root" added to /.rhosts."STATION_B root" added to /.rhosts/etc/hosts up to date== tu1 and tu2 interface configuration ==ee0:flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>inet 1.2.3.5 netmask ffffff00 broadcast 1.2.3.255 ipmtu1500==ee0 interface configuration==Enter the alias name for ee0 [lanioa] : <External nameof STATION_A>

(The Hostname should not be STATION_A, STATION_B, or ALIAS IP.)Enter ’lanioa’ IP address [1.2.3.5]: <IP address ofSTATION_A>

(Configure the IP Address with an IP address different of the internalNetwork (1.1.1.x or 2.2.2.x) for example 1.2.3.4.)Enter ’netmask’ IP address [255.255.255.0]: <Netmaskof STATION_A>hostname for active station fixed to "station_mfs" or"STATION_MFS"Enter "station_mfs" IP address[1.2.3.6]: <Alias IPof MFS>

(The Alias IP must not be STATION_A, STATION_B, nor an internal NetworkIP address; for example 1.2.3.8)wait...pinging’station_mfs’ is already defined in /etc/hosts withanother IP address: 1.2.3.6 station_mfs STATION_MFSDo you want to remove it [y] ? YRoute to the default gatewayEnter the gateway IP address [1.2.3.252]: <IP addressof the default gateway>Configuring ee0 interface.shutdown ee0 interfaceTo take into account network modifications, networkservices should be restartedAll connections (rlogin, telnet...) using networkinterfaces may be closedDo you want to restart the network services [y]? Y

3BK 20935 AAAA PCZZA Ed.20 137 / 176


7.1.6 Configure the MFS

7.1.6.1 Customize Time ZoneTime zone information is stored in files in the /etc/zoneinfo directory. The/etc/zoneinfo/localtime file is linked to a file in the /etc/zoneinfo

directory and specifies the local time zone. These files are linked duringsystem installation, but, as super user, you can change your local time zoneby relinking the /etc/zoneinfo/localtime file.

To customize the time zone of the MFS, run the following command. Otherwise,go directly to the next task.

For example, the following commands change:

The local time zone to Canada’s Atlantic time zone:<STATION_A> # ln -sf /etc/zoneinfo/Canada/Atlantic/etc/zoneinfo/localtime<STATION_B> # ln -sf /etc/zoneinfo/Canada/Atlantic/etc/zoneinfo/localtime

The local time zone for France:<STATION_A> # ln -sf /etc/zoneinfo/MET/etc/zoneinfo/localtime<STATION_B> # ln -sf /etc/zoneinfo/MET/etc/zoneinfo/localtime

7.1.6.2 Configure MFS Identifier and NameThe MFS Id is an integer between 500 to 999 and must be identical on bothstations. Each identifier must be unique for a given MFS within a customernetwork.

To configure the MFS Identifier and MFS Name, run the following command.Otherwise, go to the next section.

<STATION_A> # /usr/mfs/bin/mfs_mfsid<STATION_B> # /usr/mfs/bin/mfs_mfsid

Enter the MFS Ident (Manager Element Id) [<old mfs_id>]? <your MFS ID>

(The MFS Ident and MFS Name must be the same on both stations.)Enter the MFS Name (32 maximum characters) [<oldmfs_name>] ? <your MFS Name>/usr/mfs/etc/GPMGP has been modified/usr/nectar/var/data/nServerFile has been modified/usr/nectar/var/data/param.cfg has been modified.

Configure SNMP Server 1. To configure SNMP Server:<STATION_A># /usr/mfs/bin/mfs_addomc<STATION_B># /usr/mfs/bin/mfs_addomc (In Duplex only)

SNMP manager address as received by the MFS:<SNMP_address>

<SNMP_address> is the OMC-R IP address, or the one after translation ifthere is a NAT router.Community name for SNMP requests: <Community_string>

Note: The default Community_string (also called SNMP password) for B9 MFS SNMPagent is “OMC”, but this can be changed by the operator.

... 172.25.129.29 & OMC updated in /etc/snmpd.conf

Some more messages are appearing, as processes are starting.

138 / 176 3BK 20935 AAAA PCZZA Ed.20


Configure NTP Server 2. Configure the NTP Server:<STATION_A> # /usr/mfs/bin/mfs_ntp<STATION_B> # /usr/mfs/bin/mfs_ntp (In Duplex only)

The NTP server is usually on the OMC-R. Its hostname should be definedin the /etc/hosts .IP address of the NTP server [<Old IP of the NTPServer>] : <IP address of the NTP Server>Testing... <IP Address of the NTP Server>

Some more messages appear after a while, then the prompt.

Now, the software is installed on STATION_A and STATION_B in duplexconfiguration.

7.1.7 Download and Launch BUL Files


The IMT PC is installed

The IMT PC is connected to internal network: LSN1 Hub/Switch

The MFS software is installed

The nectar must be stopped on the stand-by station.

7.1.7.2 Start MFS in conf modeTo start the MFS in configuration mode, type:

<STATION_A> #cd /usr/mfs/bin<STATION_A> # ./mfs_start_nectar -conf

Confirm the reboot.

Wait until station will reboot and do not launch any command on STATION_Bduring this step.The reboot is finished when direct connection (telnet) is possible again.

7.1.7.3 Download BUL Files with the Web BrowserThe BUL files are installed on each station during the installation step. For usewith the IMT GUI Applet, these files must also be downloaded on the IMT PC.

1. Log in as ’lmt1 NT’ user (lmt1 is an example of user name) on the IMT PC.

2. Create a new directory, bul_<MFS version>, in the lmt1 home directoryC:\Winnt\Profiles\lmt1. (This is an example directory).

3. Start the web browser and connect to the following URL address:http://1.1.1.1/bul (station A).

3BK 20935 AAAA PCZZA Ed.20 139 / 176


4. Download the following BUL files to the bul_<MFS version> directory:

You have two choices:

Download the concatenated BUL files (column 3 from Table 14 ): thisprocedure is recommended and described in this document in theLoad BUL Files to the MFS (Section 7.1.7.4)01_mfs.bul contains the BUL files prefixed from 10 to 50.02_mfsconfig.bul contains the BUL files prefixed from 60 to 90.

Download the unit BUL files (columns 1 and 2) see Table 14. Thismethod is not recommended and must be used only in faulty cases.

Unit bul files AS800 Unit bul files DS10 Concatenated bul files AS800/DS10

10_gp.bul 10_gp.bul 01_mfs.bul

20_mfsfap.bul 20_mfsfap.bul 02_mfsconfig.bul

30_ref_alarm.bul 30_ref_alarm.bul -

40_gem.bul 40_gem.bul -

41_gam.bul 41_gam.bul -

42_gom.bul 42_gom.bul -

43_gpm.bul 43_gpm.bul -

44_q3agent.bul 44_q3agent.bul -

46_craft.bul 46_craft.bul -

50_start_scim.bul 50_start_scim.bul -

60_cnfalarm.bul 60_cnfalarm_DS10.bul -

70_cs_port.bul 70_cs_port.bul -

80_subrack_profile.bul 80_subrack_profile.bul -

81_site_objects.bul 81_site_objects.bul -

90_ghm_objects.bul 90_ghm_objects_ds10.bul -

95_first_version.bul 95_first_version.bul -

Table 14: BUL-Files Download

5. Download dataPatch.bul file to the bul_<MFS version> directory

Unit bul files do not have numbers in the files names for DS10 RC40 controlstations.

140 / 176 3BK 20935 AAAA PCZZA Ed.20


7.1.7.4 Load BUL Files to the MFSTo load BUL files to the MFS:

1. On the IMT PC, log in as’ lmt1 NT’ user.

2. Start the web browser and connect to the following URL address:http://1.1.1.1

The IMT GUI applet is loaded on the browser and following messageappears:.

Following message automatically displayed on screen: Unauthorized

access to this machine is strictly forbidden and may be

liable to legal proceedings

Click on [ OK ] button

3. Login as ’platform’ user

4. Select the menu path: BUI –> ReceptionView .

5. Select the menu path BUI –> Request.

6. In the "Request" Window, click on [ File ], select the files listed belowone-by-one and click on [ Send ].

Unit bul files AS800 Unit bul files DS10 Concatenated bul filesAS800/DS10

10_gp.bul 10_gp.bul 01_mfs.bul

20_mfsfap.bul 20_mfsfap.bul -

30_ref_alarm.bul 30_ref_alarm.bul -

40_gem.bul 40_gem.bul -

41_gam.bul 41_gam.bul -

42_gom.bul 42_gom.bul -

43_gpm.bul 43_gpm.bul -

44_q3agent.bul 44_q3agent.bul -

46_craft.bul 46_craft.bul -

50_start_scim.bul 50_start_scim.bul -

Table 15: BUL-Files Loading I

7. Wait until the SCIMs Ready message appears in the "Request Window",before continuing the configuration!

3BK 20935 AAAA PCZZA Ed.20 141 / 176


8. Start the files shown in the following table.

Unit bul files AS800 Unit bul files DS10 Concatenated bul filesAS800/DS10

60_cnfalarm.bul 60_cnfalarm_DS10.bul 02_mfsconfig.bul

70_cs_port.bul 70_cs_port.bul -

80_subrack_profile.bul 80_subrack_profile.bul -

81_site_objects.bul 81_site_objects.bul -

90_ghm_objects.bul 90_ghm_objects_ds10.bul -

95_first_version.bul 95_first_version.bul -

Table 16: BUL-Files Loading II

Wait until file 02_mfsconfig.bul is loaded.

Check in the reception view that all the sessions are closed.

9. In the "Request" Window, click on [ File ], select dataPatch.bul and click on[ Send ]

10. Download the Customer BUL file from CD-ROM .

Insert the CD-ROM, with the customer BUL file, in the PC.

From IMT window, select the BUI -> Request menu to see the bul file

execution result

In the Request window, click on the button [ File ]. BUL File Chooserwindow is opened.

From the CD-ROM, select Customer bul file (e.g. BULxWxxx.bul).

Click on [ OK ]

In the Request window, click on the button [ Send ].

Click on [ Switch View ] to see the result. The Reception View appears in

the IMT Request Window.

Open with a text editor the Customer BUL file.

For each SET command not included between /* and */ delimiters perform

the following checks in the Reception View of IMT Request Window:

check if the SET command exists and identify the value it assigned to

the parameter in the corresponding /* NEWVALUE */ line.

compare the assigned value with the parameter’s value to beassigned from customer BUL file (the one not included between /*

and */ delimiters).

142 / 176 3BK 20935 AAAA PCZZA Ed.20


If not all parameters/alarm values from Customer BUL file were set to theNEWVALUE in Reception View of IMT Request Window, that means theCustomer BUL file is not correct.

Close the text editor with the Customer BUL file.

Close "Request" and "Receive" Windows

11. Close IMT.

3BK 20935 AAAA PCZZA Ed.20 143 / 176


7.1.8 Restart MFS

During MFS restart on both station the connection through IOLAN must not beused, close these connections before performing this procedure.Use usual telnet or rlogin sessions instead of connection trough IOLAN.

If you have running BSSs on the MFS, there is GPRS traffic outage and CStraffic reduction starting with this section.

1. Restart MFS STATION_A:<STATION_A> # /usr/mfs/bin/mfs_start_nectar -site

Confirm the reboot.

Wait five minutes and reconnect on STATION_A.

2. Restart MFS STATION_B:<STATION_B> # /usr/mfs/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished, when directconnection (telnet) is possible again

3. Check that the MFS starts correctly, when both stations have restarted,check that all the MFS UNIX processes are launched:

<STATION_A> # ps -edf | grep /[u]sr/mfs/bin<STATION_B> # ps -edf | grep /[u]sr/mfs/bin

root 765 1 0.0 09:57:43 ?? 0:00.06/usr/mfs/bin/DUMP_SRVroot 1196 1 0.0 09:57:57 ?? 0:05.94 sh/usr/mfs/bin/start_http startroot 1255 1 0.0 09:57:59 ?? 0:00.03/usr/mfs/bin/TRACE_SERVERroot 1444 1125 0.0 09:58:10 ?? 0:00.12/usr/mfs/bin/GAM 6299root 1465 1125 0.0 09:58:17 ?? 0:13.60/usr/mfs/bin/GEM 6297root 1466 1125 0.0 09:58:17 ?? 0:00.08/usr/mfs/bin/SCA 6296root 1478 1125 87.3 09:58:22 ?? 1:12.43/usr/mfs/bin/GOM 6295root 1479 1125 0.0 09:58:22 ?? 0:00.17/usr/mfs/bin/GPM 6294root 1480 1125 0.0 09:58:23 ?? 0:00.17/usr/mfs/bin/GLM 6293root 1481 1125 0.0 09:58:25 ?? 0:00.03/usr/mfs/bin/CRAFT_SUP 6291root 1483 1125 0.1 09:58:25 ?? 0:07.73/usr/mfs/bin/mfsQ3Agt 6290 -compkg SOCKETroot 21514 1 0.0 10:20:38 ?? 0:00.31/usr/mfs/bin/PatchSrvroot 4647 1 0.0 10:20:38 ?? 0:00.02/usr/mfs/bin/BckpRstr

Note 1 : The "BckpRstr" and"PatchSrv" processes runs only on the activecontrol station.

4. Display the Craft_SRV process by typing:# ps -edf | grep CRAFT_SRV

144 / 176 3BK 20935 AAAA PCZZA Ed.20


root 4614 1481 0.0 10:20:37 ?? 0:00.05 (CRAFT_SRV)(Only on the Active station)

When the GOM is started, the Q3AGENT (mfsQ3Agt) and CRAFT_SRVstart about ten minutes later. When the CRAFT_SRV UNIX process starts,the IMT connection is possible.

5. Start IMT by connecting it with the internal IP 1.1.1.1

The IMT GUI Applet is loaded on the browser and the following messageappears:

Unauthorized access to this machine is strictly forbidden and

may be liable to legal proceedings

Click on OK button!

6. Log in as platform user

7. Check that Enhanced security feature is installed on both servers.

From IMT select Software -> Unix patch management -> Display patchversion and check that "SEC" word is present in the Unix patch version.

Now the installation of the MFS equipment is complete!


- Launch script AuditMfs and check the results. MFS 5 min. None.

1. On the active station:cd /usr/mfs/binls | grep Audit

The script for audit is displayed.

2. Launch the respective script:./AuditMFS.pl*

The result is displayed on the screen, and saved in the files AuditMFS.log

and AuditMFS.trace in the folder usr/mfs/log .

7.1.9 Restore the NORIMFS File


- Restore the NORIMFS file from PC LMT to MFS. MFS 10 min. None

Follow the next steps:

1. Conect via ftp from the PC to MFSftp 1.1.1.x


ftp>put NORIMFS.TXTftp>by

2. Login as platform user on MFS active station

In Windows 2000 or Windows XP, click on Start->Run

In the Run Window enter the following command:telnet 1.1.1.x

3BK 20935 AAAA PCZZA Ed.20 145 / 176



Enter the user name and the passwordcp /usr/users/platform/NORIMFS.TXT /omcxchg/ri

7.1.10 Re-synchronize BSCs with MFS

7.1.10.1 Set Synchronization ModeSet the same values as before the MFS software installation for thesynchronization mode, master GPU (if it is the case), synchronizingPCM-TTP(s).

The definition of synchronization parameters involves:

Setting the synchronization mode

Defining master GPUThe user can define one or two synchronizing master GPU on each MFSsubrack if the MFS station is in centralized clock synchronization mode.

Setting the synchronizing PCM-TTP(s) for the autonomous and centralizedclocking modeThe operator must define at least one synchronizing PCM-TTP, but it isadvisable to define two synchronizing PCM-TTPs for redundancy.In case of centralized clock synchronization mode only the master GPUallows this modification.

The first two tasks involve the reset of each GPU board (GPRS reset only)to take into account the new mode.

Set synchronization

mode

To set the synchronization mode of the MFS station:

1. From the GPRS Terminal window, follow the menu path:

Tools -> SynchronizeThe default mode of the MFS Station is displayed.

2. From the drop down list, select the new mode.

3. Click on [ OK ].

Define Master GPU 1. To define a synchronizing master GPU, from the GPRS Terminal windowfollow the menu path:

View -> Site View

A dialog box displays the site in a tree form.

2. Right-click on a subrack object to display a pop-up menu.

3. Click on Synchro Master Def. in the pop-up menu.

4. Define the number of Master GPU and the slot number of each of theMaster GPU in the dialog box.

5. Click on [ OK ] to complete Master GPU Definition.

A dialog box opens.

6. Click on [ OK ] to validate the Master GPU Definition.

146 / 176 3BK 20935 AAAA PCZZA Ed.20


Synchronize PCM-TTP 1. To redefine the synchronization mode of a PCM-TTP board, from the GPRSTerminal window, follow the menu path:

View -> Site View

The site view opens.

Alternatively, users can follow the menu path:

View -> Physical View

The physical view opens.

2. Right-click on a PCM-TTP board to display a pop-up context menu.

3. Click on Set Attributes in the pop-up context menu.

4. Select ’Yes’ from the drop down list in the ’Synchronizing’ field.

5. Click on [ Set ].

7.1.10.2 Restore Database

Download from OMC-R To download the last correct backup data from the OMC-R:

1. From the iconbox, click on [ MFS Backup ].

The MFS Backup Manager window opens.

2. At the prompt type:1 [ enter ]

to select an MFS.

3. Type the number of the MFS and press [ enter ].

4. Type:3 [ enter ]

to select the Download option.

The download menu opens.

5. Type:1 [ enter ]

to select the Open file for download option.

A list of backup files stored on the OMC-R opens.

6. Type the appropriate number of the backup file to download to the MFSand press [ enter ].

7. Type:y [ enter ]

to download the file to the MFS.

Press [ enter ] to continue.

Restore MFS Data To restore MFS data from a backup:

1. From the IMT (either locally or from the OMC-R) GPRS Terminal window,select Backup/Restore -> Restore .

The Restore window opens.

2. Select the file name of the backup you require.

3. Click on [ OK ].

The restore process stops NECTAR on both the active and standbymachines, replaces the existing files with the backup files, restarts NECTAR,and then restarts the IMT in site mode. The MFS data is restored.

4. After the restore was finished, re-synchronize the MFS:

3BK 20935 AAAA PCZZA Ed.20 147 / 176


From the RNUSM window, select the appropriate MFS, right click andselect Re-Synchronize .

7.1.10.3 Test Call and GPRS Services

CS and GPRS Calls Display USD Detailed DTC Information to check in the DTC report if CS andGPRS calls are made on each link and print the report. To open the DTCReport window and display detailed DTC information:

1. Open the RNUSM window of the OMC-R.

2. Right- click on the BSC in the ’Tree Browser Menu’ and select Showequipment

3. In the BSSUSM: Main View window, select USD -> USD A Interface .

The USD A Interface window opens.

4. Select the required DTCs from the DTC Information panel, and clickon [ DTC Report ].

5. To close the window, click on [ Close ].

Several packets must be transferred. Resource allocation is not performed atmobile connection but at data transfer.

If the internal processing of the BSC is overloaded, the values of the DTCare set to 0!

148 / 176 3BK 20935 AAAA PCZZA Ed.20


7.2 Initial Configuration

7.2.1 Possible Configurations

This section describes the different possible configurations of the MFS or IMTin the case of new software installation.

It is possible to:

Configure IOLAN Terminal Server

Configure the IMT on Windows XP

Configure the IMT on Windows 2000.

7.2.2 Configure IOLAN Terminal Server

7.2.2.1 PrerequisitesThe given data sites are:

Numbering of ports used via TELNET: 10002 and 10003 by default

The IP address of the IOLAN corresponding to LSN 1: 1.1.1.20 in MFS

network configurations.

The installation assumes that the IOLAN is in a standard constructorconfiguration.

Connect the IOLAN 1. Connect the IOLAN to the mains circuit (220V AC or 48V DC according tothe type of power supply).

2. Check that the light on the POWER switch is permanently on.

3. Connect the IOLAN via port Number 1 to a VT100 type console (or a PC orworkstation capable of emulating a VT100 console).

For the initial installation, the port is configured by the constructor at the timeof programming to provide complementary information. This configuration is:9600 Baud, 8 data bits, & stop bit, No Parity.

4. When the prompt local> appears, enter:set term vt100 <ENTER>

5. In the menu, select ’Admin mode’. The administration Menu display.

6. Select ’password’ and type the default password IOLAN. The Administrationmenu reappears with fields.

3BK 20935 AAAA PCZZA Ed.20 149 / 176


7.2.2.2 Configure Ports 2 and 3In a duplex NECTAR configuration, only ports 2 and 3 are used. It is advisableto leave port 1 in VT100 mode in order to facilitate further interventionson the IOLAN.

1. In the Administration menu, select ’line’.

2. Select the sub-menu ’access’ and position lines 2 and 3 at.

Access = remote

Password = disable

Mode= telnet.

There is nothing to change in the sub-menus Flow ctrl, Hardware andOptions.

3. Select the sub-menu ’Network’ to position the numbers Local port of ports 2and 3 at 10002 and 10003 respectively, which are the values by defaultof the constructor.

4. Select the sub-menu ’Terminal’ to set the value of ’Terminal’ to VT100.

Configure Ethernet Link 1. In the administration menu select ’server’.

2. Set following parameters:

IP address = 1.1.1.20

Mask (255.255.255.0)

Ethernet Interface = TWISTED_PAIR.

3. Save each modification.

The IOLAN is now configured and must be restarted.

Restart IOLAN 1. In the Administration menu, select ’reboot’.

2. Press [ ENTER ].

3. Press the spacebar, which resets the hardware.

The IOLAN is now ready to be used on the Internet network.

150 / 176 3BK 20935 AAAA PCZZA Ed.20


7.2.3 Configure IMT on Windows XP

The IMT GUI Applet must be run under either Windows XP or Windows 2000.

For Windows XP, this section describes how to:

Create a local user account (optional)

Configure the network board


The maximum possible number of IMT instances (PC and/or OMC-R IMTwindow) used with a MFS is two

The IMT is connected to the MFS internal network. Note that it can be alsoconnected to the external network

While configuring the IMT, access from the OMC-R to the MFS involved

must be blocked

The web browser (according to the Evolium A9135 MFS IMT User Guide).

7.2.3.2 Create User AccountThis procedure describes how to create the local user lmt1 . lmt1 is an exampleand is used afterwards in the document.

On the IMT:

1. Connect as the local Administrator on the LMT PC

2. Right click on Start , select Properties , select Start Menu and chooseClassic Start Menu and click Apply and click on OK

3. Select the following menu path:

Start –> Settings –> Control Panel –> Users Accounts.

The "Users Accounts Window" is displayed.

4. Select the Advanced tab and click on [ Advanced ] in ’Advanced UserManagement’ frame

The "Local Users and Groups Window" is displayed.

5. Right-click on ’Users mode’ in the tree and select ’New User’.

A box is displayed.

6. Enter the lmt1 login in the ’Username’ field.

7. Enter the name of the user, Craft’s User 1, in the ’Full Name’ field.

8. Enter ’User MFS IMT’ in the ’Descriptor ’field.

9. Enter the password in the ’Confirm Password’ field.

10. Unselect ’User must exchange password at next logon’ and click on [ Create ].

11. Close the window.

3BK 20935 AAAA PCZZA Ed.20 151 / 176


Modify Properties 1. Right-click on the new ’lmt1’ item and select ’Properties’

The lmt1 "Properties Window" is displayed.

2. Select the ’Member Of ’tab and click on [ Add ].

The "Select Group Window" is displayed.

3. Click on ’Advanced’ and the in the Select Group window click on ’Find Now’

4. Select either the ’Power Users’ or ’Administrator’ group and click on [ OK ].

5. Click on [ OK ] twice, close ’Local Users and Groups’ and quit the "UsersAccounts Window".

If Windows XP is installed on disk C, the home directory is created underC:\Documents and Settings\lmt1 after the first connection.

7.2.3.3 Configure Network BoardThis procedure describes how to configure the network board of the IMT onthe internal network. The IMT’s internal IP address must be chosen between1.1.1.180 and 1.1.1.189. The IMT’s IP address can be external too. But thenetwork board can only be configured with the internal or external IP addressat a time

On the IMT:

1. Connect as local Administrator.


Start -> Setting -> Network ConnectionsThe "Network Connections" Window is displayed.

3. Select ’Local Area Connection’.

The "Local Area Connection" Window is displayed.

4. Right-click on [ Properties ] and select ’Internet Protocol (TCP/IP)’ in the list.

5. Click on [ Properties ].

The "Properties" Window is displayed.

6. Select ’Use the following IP address’ frame.

7. Enter the IMT’s IP address in the ’IP address’ field.

8. Enter 255.255.255.0 in the ’Subnetmask’field.

9. Click on [ OK ] twice.

10. Reboot the IMT to take into account the new IP address.

7.2.3.4 Install and Configure IMTTo run the IMT software, the two following files must be installed on the IMT:

Java Plug-in

Applet Security file.

To download these files, the MFS must be started.

To install and configure IMT, see Install IMT Environement

152 / 176 3BK 20935 AAAA PCZZA Ed.20


7.2.4 Configure IMT on Windows 2000

The IMT GUI Applet must be run under either Windows XP or Windows 2000.

For Windows 2000, this section describes how to:

Create a local user account (optional)

Configure the network board


The maximum possible number of IMT instances (PC and/or OMC-R IMTwindow) used with a MFS is two

The IMT is connected to the MFS internal network. Note that it can be alsoconnected to the external network

While configuring the IMT, access from the OMC-R to the MFS involved

must be blocked

The web browser (according to the Evolium A9135 MFS IMT User Guide).

7.2.4.2 Create User AccountThis procedure describes how to create the local user lmt1 . lmt1 is an exampleand is used afterwards in the document.

On the IMT:

1. Connect as the local Administrator on the LMT PC


Start –> Settings –> Control Panel –> Users and Passwords.The "Users and Passwords Window" is displayed.

3. Select the Advanced tab and click on [ Advanced ] in ’Advanced UserManagement’ frame

The "Local Users and Groups Window" is displayed.

4. Right-click on ’Users’ in the tree and select ’New User’.

A box is displayed.

5. Enter the lmt1 login in the ’User name’ field.

6. Enter the name of the user, Craft’s User 1, in the ’Full Name’ field.

7. Enter ’User MFS IMT’ in the ’Descriptor ’field.

8. Enter the password in the ’Confirm Password’ field.

9. Unselect ’User must exchange password at next logon’ and click on[ Create ].

10. Close the window.

3BK 20935 AAAA PCZZA Ed.20 153 / 176


Modify Properties 1. Right-click on the new ’lmt1’ item and select ’Properties’ on the button[ Group ]

The lmt1 "Properties Window" is displayed.

2. Select the ’Member Of ’tab and click on [ Add ].

The "Select Group Window" is displayed.

3. Select either the ’Power Users’ or ’Administrator’ group and click on [ Add ].

4. Click on [ OK ] twice, close ’Local Users and Groups’ and quit the "Usersand Passwords Window".

If Windows 2000 is installed on disk C, the home directory is created underC:\Documents and Settings\lmt1 after the first connection.

7.2.4.3 Configure Network BoardThis procedure describes how to configure the network board of the IMT onthe internal network. The IMT’s internal IP address must be chosen between1.1.1.180 and 1.1.1.189. The IMT’s IP address can be external too. But thenetwork board can only be configured with the internal or external IP addressat a time

On the IMT:

1. Connect as local Administrator.


Start -> Setting -> Network and Dial-up ConnectionsThe "Network and Dial-up Connections" Window is displayed.

3. Select ’Local Area Connection’.

The "Local Area Connection" Window is displayed.

4. Right-click on [ Properties ] and select ’Internet Protocol (TCP/IP)’ in the list.

5. Click on [ Properties ].

The "Properties" Window is displayed.

6. Select ’Use the following IP address’ frame.

7. Enter the IMT’s IP address in the ’IP address’ field.

8. Enter 255.255.255.0 in the ’Subnetmask’field.

9. Click on [ OK ] twice.

10. Reboot the IMT to take into account the new IP address.

7.2.4.4 Install and Configure IMTTo run the IMT software, the two following files must be installed on the IMT:

Java Plug-in

Applet Security file.

To download these files, the MFS must be started.

To install and configure IMT, see Install IMT Environement

154 / 176 3BK 20935 AAAA PCZZA Ed.20


7.3 Change Configuration on Running MFSThis section summarizes the different possible configurations of the MFS orIMT in case they were not done during the MFS installation or in case someconfigurations changed.

This section is divided in three parts:

Customize the time zone, see Configure the MFS (Section 7.1.6)

Configure the IMT, see Configure IMT (Section 7.3.2)

Configure both station, see Configure Both Station on Running MFS

(Section 7.3.3)

Configure a station’s external IP addresses, external hostname, alias IPaddress, and default gateway of MFS equipment

Configure the NTP server

Configure the MFS identifier.

7.3.1 Customize Time Zone

To customize the time zone of the MFS, refer to Configure the MFS (Section7.1.6).

7.3.2 Configure IMT

The IMT GUI Applet must run under Windows XP or Windows 2000.

To configure the IMT on Windows XP, refer to Configure IMT on WindowsXP (Section 7.2.3).

To configure the IMT on Windows 2000, refer to Configure IMT on Windows2000 (Section 7.2.4).

3BK 20935 AAAA PCZZA Ed.20 155 / 176


7.3.3 Configure Both Station on Running MFS


Log in as Admin

If the stations are connected to a external network, the following parametersare necessary:

IP addresses and netmasks of one or both stations

Alias IP of the MFS equipment

IP address of the default gateway

IP address and hostname of the NTP Server.

All software is now installed on the stations, and the IMT as well as the

Terminal Server are configured

The MFS is running.

7.3.3.2 Stop the MFS1. To check which station is "ACTIVE", log in as lmt1 user on the IMT PC.

2. Start the web browser and connect to the following URL address:http://1.1.1.1

Following message automatically displayed on screen:Unauthorized

access to this machine is strictly forbidden and may be liable

to legal proceedings

Click on [ OK ] button.

3. The IMT GUI applet is loaded on the browser and asks for a login.

4. Log in as admin user, entering the admin user name and password.

5. Select the menu path: BUI –> ReceptionView.

6. Select the menu path: BUI –> Request .

7. In the "Request" Window, enter the command get sta[*](*) ; and click on[ Send ].

8. In the ’Reception View’, look at the attribute ’system_state’ for STATION_Aand STATION_B.

9. If the MFS software is running, stop the standby station before the Activeone as follows:

<STANDBY_STATION># /usr/mfs/bin/mfs_stop_nectar

Confirm the reboot and wait until the reboot is finished, when directconnection (telnet) is possible again

The station is stopped.

10. Then, stop the Active station:<ACTIVE_STATION># /usr/mfs/bin/mfs_stop_nectar


The MFS software is stopped.

156 / 176 3BK 20935 AAAA PCZZA Ed.20


7.3.3.3 Configure the MFSTo configure or change the External IP or/and Alias IP addresses and/or thedefault gateway IP address of the MFS, run the following commands.

Otherwise, go to the next procedure.

Note: Start with the stand-by station, use the connection through IOLAN.

Station_A is defined as the stand-by station, Station_B is defined as theactive station.

Station_A: 1. Open an rlogin session. Log in as user root on MFS Station_B.

2. Log in on the Station_A using IOLAN:telnet 1.1.1.20 10002Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’



3. Enter the following command:# /usr/mfs/bin/mfs_inet -duplex -hostname STATION_A

Note: The ALIAS IP address is the IP address used to communicate with the MFSplatform whether the station is active or stand by. The ALIAS IP must beidentical on both stations.

== System configuration ==Hostname: "STATION_A"/.rhosts up to date/etc/hosts up to date.== tu0 interface configuration ==Enter the alias name for tu0 [<old name>]: <Externalname of STATION_A>

(The Hostname should not be STATION_A, STATION_B, or ALIAS IP. Press[ ENTER ] if you do not want to change.)Enter IP address for tu0 [<old IP address]: <IPaddress of STATION_A>

(Configure the IP Address with an IP address different from that of theinternal Network (1.1.1.x or 2.2.2.x). Press [ ENTER ] if you do not want tochange.)Enter netmask [<old netmask>]: <Netmask of STATION_A>Simplex installation: No external alias IP definedfor MFS.

OrAlias hostname for active station is fixed to"station_mfs" or "STATION_MFS"Enter the IP address of "station_mfs"[<old alias ip ofMFS>: <Alias IP of MFS>

(The Alias IP should not be STATION_A, STATION_B, or an internal NetworkIP address. Press [ ENTER ] if you do not want to change).Route to the default gateway:Enter the gateway IP address: <IP address of thedefault gateway>Configuring tu0 interface.== tu1 and tu2 interfaces configuration ==

3BK 20935 AAAA PCZZA Ed.20 157 / 176


tu1 interface already configured.tu2 interface already configured.== tu3 interface configuration ==Checking only: OK


4. Close the connection through IOLAN, closing or killing the terminal window.

Station_B 1. Open an rlogin session. Log in as user root on MFS Station_A.

2. Log in on the Station_B using IOLAN:telnet 1.1.1.20 10003Trying 1.1.1.20...Connected to 1.1.1.20.Escape character is ’^]’



3. Enter the following command:# /usr/mfs/bin/mfs_inet -duplex -hostname STATION_B

Note: The ALIAS IP address is the IP address used to communicate with the MFSplatform whether the station is active or stand by. The ALIAS IP must beidentical on both stations.

== System configuration ==Hostname: "STATION_B"/.rhosts up to date/etc/hosts up to date.== tu0 interface configuration ==Enter the alias name for tu0 [<old name>]: <Externalname of STATION_B>

(The Hostname should not be STATION_A, STATION_B, or ALIAS IP. Press[ ENTER ] if you do not want to change.)Enter IP address for tu0 [<old IP address]: <IPaddress of STATION_B>

(Configure the IP Address with an IP address different from that of theinternal Network (1.1.1.x or 2.2.2.x). Press [ ENTER ] if you do not want tochange.)Enter netmask [<old netmask>]: <Netmask of STATION_B>Simplex installation: No external alias IP definedfor MFS.

OrAlias hostname for active station is fixed to"station_mfs" or "STATION_MFS"Enter the IP address of "station_mfs"[<old alias ip ofMFS>: <Alias IP of MFS>

(The Alias IP should not be STATION_A, STATION_B, or an internal NetworkIP address. Press [ ENTER ] if you do not want to change).Route to the default gateway:Enter the gateway IP address: <IP address of thedefault gateway>Configuring tu0 interface.== tu1 and tu2 interfaces configuration ==tu1 interface already configured.tu2 interface already configured.

158 / 176 3BK 20935 AAAA PCZZA Ed.20


== tu3 interface configuration ==Checking only: OK


4. Close the connection through IOLAN, closing or killing the terminal window.

Reconfigure the DECNet

OSI

1. Enter the following command on the Station_A:<STATION_A> # /usr/mfs/bin/mfs_decnetosi

2. Only in case of DUPLEX, enter the same command on the Station_B:<STATION_B> # /usr/mfs/bin/mfs_decnetosi

3BK 20935 AAAA PCZZA Ed.20 159 / 176


7.3.3.4 Configure MFS Identifier, MFS Name and NTP ServerTo configure the MFS Identifier, the MFS Name, the SNMP and the NTPServer, refer toConfigure the MFS (Section 7.1.6). Otherwise, finish theconfiguration by restarting the MFS.

7.3.3.5 Restart MFSTo restart the MFS, refer to Restart MFS (Section 7.1.8) .

7.4 NECTAR ProceduresThis section describes IMT procedures linked to RIT replacement.

7.4.1 Locking Procedure

It is strongly recommended that you follow these procedures. They aredesigned to set the subrack to:

Locking mode before removing a RIT (which requires a locking action

before replacement)

Running mode after inserting a new RIT (which was locked beforereplacement).

Before setting a subrack in Maintenance mode, you must first ensure that thissubrack is in standby mode.If it is not, use the MFS IMT Switchover function to relay operations fromthis subrack to the mirror subrack.

7.4.1.1 LockTo lock:

1. In the "IMT Window", follow the menu path:

View -> Nectar View .

2. In the "Nectar View Window", right-click on the subrack:

Context menu -> Lock .

3. In the "Confirmation Window", click on [ OK ]

The locking action is successful if the result displayed is:ACTION_RSP du A(lock ())

for the left-hand side / upper station.ACTION_RSP du B (lock ())

for the right-hand side / lower station.

160 / 176 3BK 20935 AAAA PCZZA Ed.20


7.4.1.2 UnlockTo unlock:

1. In the" Nectar View Window", right-click on the subrack:

Context menu -> Unlock

2. In the "Confirmation Window", click on [ OK ]

The unlocking action is successful if the result displayed is:ACTION_RSP du A(unlock ())

for the left-hand side / upper station.ACTION_RSP du B(unlock ())

for the right-hand side / lower station.

7.4.2 Test Procedure

Follow this procedure to test a specific subrack for RIT failures, before replacinga RIT.

Before testing a subrack, you must ensure that this subrack is in standby mode.If it is not, use the MFS IMT Switchover function to relay operations fromthis subrack to the mirror subrack.

1. Lock the subrack, see Locking Procedure (Section 7.4.1).

2. Test the subrack with a right-click on the same subrack:Context menu -> Test.The results of the test appear in the "Reception View Window".

3. Unlock the subrack, see Locking Procedure (Section 7.4.1).

3BK 20935 AAAA PCZZA Ed.20 161 / 176


7.5 Miscellaneous tasks

7.5.1 Download New Package

7.5.1.1 Download PossibilitiesPrerequisites

All the software for manual installation is delivered either from the MFS

CD-ROM or from an FTP server

When using FTP, the External IP address must be already configured.

7.5.1.2 Copy All Packages to the StationsIn this document, the directory /var/tmp/delivery is chosen as the temporarydirectory in which to install the set of packages. (To be created if it doesnot exist.)

Choose one of the following methods, according to your delivery method:CD-ROM or FTP.

7.5.1.3 Copy from CD-ROMOn both stations and in any order:

1. Log in as root

2. Insert the MFS CD-ROM.

3. Mount MFS CD-ROM.# mount -r -t cdfs -o rrip /dev/rz4c /mnt (on AS800Station)# mount -r -t cdfs -o rrip /dev/rz8c /mnt (on DS10Station

(It uses the Rock Ridge Interchange Protocol (RRIP) extensions to ISO9660 (if present on the file system) to provide mixed-case file names, devicespecial files, and other attributes for files on the file system. If there are noRRIP extensions on the file system, the file system will be mounted andthe option will be ignored).

4. Copy all files into the /var/tmp/delivery directory:# cp /mnt/* /var/tmp/delivery

5. To remove the CD, umount the mount point# cd /# umount /mnt

6. Remove the CD from CD-ROM drive.

162 / 176 3BK 20935 AAAA PCZZA Ed.20


7.5.1.4 Copy from FTP ServerIf the MFS CD-ROM is not available, use the ftp command if the delivery isavailable on a external server.

The External IP address (tu0) must be configured!Delete the line "root" in /etc/ftpusers file if it exists.

On both stations and in any order:

1. Log in as root.

2. Connect to the FTP server and download all files:# cd /var/tmp/delivery# ftp < IP address of the FTP server>

3. When ftp is connected, answer the prompt and enter the ftp subcommandsto get the files.

4. Connect to <the IP address of the FTP server> :220 [.........]Name : <your login name>331 [.........]Password: <your password name>230 [.........]ftp> bin200 Type set to Iftp> promptInteractive mode offftp> cd <path where the packages are present>250 CWD command successfulftp> mget *200 PORT command successful150 Opening BINARY mode data connection for [.........][.........]226 Transfer completeftp> bye221

Now the package is installed on both stations.

3BK 20935 AAAA PCZZA Ed.20 163 / 176


7.5.2 How to be connected on MFS control stations

During this section it is described different ways to be connected on the MFScontrol stations in order to:

check the status of control stations

install the firmware, operating system or MFS software

configure the MFS

There are several ways to be connected to the MFS control stations:

direct, using internal MFS networks

direct, using external MFS networks

indirect, through IOLAN

In the following figure there is a exhaustive representation of the internaland external MFS networks:

tu 0 1 2

COM 1

STATION_A

tu 0 1 2

COM 1

STATION_B

HU

B/S

WIT

CH

1

HU

B/S

WIT

CH

2

COM COM IOLAN

External Network

IMT PC

1.1.1.180

IMT PC

Ext. Net. IP

OMC

Ext. Net. IP

10002 100031.1.1.20

Figure 52: MFS networks

On STATION_A the default values of the IP addresses are:

tu0: depending on the external network configuration

tu1: 1.1.1.1

tu2: 2.2.2.1

164 / 176 3BK 20935 AAAA PCZZA Ed.20


On STATION_A the default values of the IP addresses are:

tu0: depending on the on the external network configuration

tu1: 1.1.1.2

tu2: 2.2.2.2

If you are connected on one control station, it is possible to see the networkaddresses using the following command:

ifconfig -a

7.5.2.1 Direct Connection with Control Stations, using MFS Internal NetworkPrerequisites

The IMT PC must be configured with an internal IP address, see ConfigureIMT on Windows XP (Section 7.2.3) or Configure IMT on Windows 2000

(Section 7.2.4)

The Ethernet cable between the IMT PC and the HUB/SWITCH 1 must beconnected, see Figure 52

Procedure 1. In Windows 2000 or Windows XP, click on Start->Run

2. In the Run Window enter the following command:telnet 1.1.1.x

x is 1 for STATION_Ax is 2 for STATION_B

3. Enter the user name and the passwordlogin:<enter your user name>Password<enter your password>

After this step you are connected on the console of the control station.

7.5.2.2 Direct Connection with Control Stations, using MFS External NetworkPrerequisites

The IMT PC must be configured with an IP address compatible with MFS

external network, see Figure 52

The IMT PC is integrated in the network

The MFS must be configured

Procedure 1. In Windows 2000 or Windows XP, click on Start->Run

2. In the Run Window enter the following command:telnet <external IP address of the control station>

3BK 20935 AAAA PCZZA Ed.20 165 / 176


It is possible to open a connection with the MFS control station using the aliasIP address, which always points to the active control station. This alias IPaddress it is configured during Configure Network (Section 7.1.4.6).

3. Enter the user name and the passwordlogin:<enter your user name>Password<enter your password>

After this step you are connected on the console of the control station.

7.5.2.3 Indirect Connection with Control Stations, through IOLANPrerequisites

The connection with one control stations is already made, see Direct

Connection with Control Stations, using MFS Internal Network (Section7.5.2.1) or Direct Connection with Control Stations, using MFS External

Network (Section 7.5.2.2)

The IOLAN is already configured, see Configure IOLAN Terminal Server(Section 7.2.2)

Because access on the control station through IOLAN is on the serial link, itis possible only one connection in the same time.

Procedure 1. From curent control stations connect on the other control station usingIOLAN:

telnet 1.1.1.20 port_standbyport_standby is 10002 for STATION_Aport_standby is 10003 for STATION_B



If necessary enter the user name and the password inorder to access the station

Close the connection through IOLAN, when the station is rebooted andthe Nectar is started.

2. After all the operation on the control station are finished, close theconnection through IOLAN, closing or killing the terminal window.

166 / 176 3BK 20935 AAAA PCZZA Ed.20


7.5.3 Install UNIX Patch using IMT

A UNIX patch installation can be performed from an LMT or from the OMC-R.

7.5.4 Prerequisites

Before starting the patch installation, the following prerequisites must befulfilled or verified:

If the installation is performed from a PC, verify that the IMT is correctly

configured. See Configure IMT on Windows XP (Section 7.2.3) or ConfigureIMT on Windows 2000 (Section 7.2.4)

Both stations have been properly installed using the official Alcatel methods

(installation or software change) and the MFS is running

The CD-ROM with MFS software is available

The PC used for this operation must be configured with IP address

compatibile with the MFS external network

7.5.4.1 Verify Patch VersionVerify the patch version and verify if the same patch version is installed onboth stations:

1. Open IMT using floating address, for more information about MFS networkconnections see How to be connected on MFS control stations (Section7.5.2)

2. In the IMT select Software->Unix patch management->Display patchversions.

3. Wait until Unix patch versions window opens. If the Unix patch version isconsistent on both stations and with the desired version, skip the patchinstallation procedure.

7.5.4.2 Copy Files to the OMC-RCopy the files from the MFS software CD-ROM on to the LMT or on theOMC-R. This action is performed automatically by running a script present onthe MFS software CD-ROM. If the installation is performed from an OMC-R oron a OMC-R workstation:

1. Insert CD-ROM with MFS software in OMC-R CD-ROM drive.

2. Launch the installation script.cd /cdrom/cdrom0./cp_patchn.sh

Where n is a number

3. Wait until files will be copied in (user home) /alcatel/tmp_patch_mfsdirectory (e.g. for axadmin user, the files will be copied in/alcatel/var/home/axadmin/alcatel/tmp_patch_mfs).

4. Remove CD-ROM from OMC-R.eject cdrom

3BK 20935 AAAA PCZZA Ed.20 167 / 176


7.5.4.3 Copy Files to LMT PCIf the installation is performed from an LMT PC, this PC must be connectedto the MFS external network. The following steps are necessary for thepreparation:

1. Insert CD-ROM with MFS software in PC CD-ROM drive.

2. In Windows, go to Start->Run and insert the following command.<CD-Rom drive>:\cp_patchn.bat

Where n is a number

Click on [ Ok ].

3. Wait until files are copied in C:\Alcatel\tmp_patch_mfs directory.

4. Remove CD-ROM from PC.

If patch installation failed during the process, the installation process must beperformed again from the beginning.No menu option is available during UNIX patch installation and it is not possibleto launch another UNIX patch installation from another IMT.

7.5.4.4 Install PatchTo install patch:

1. In the IMT, select the menu path:Software->Unix patchmanagement->Install unix patch.

2. Click on [ Yes ] in the" Unix Patch Installation Confirmation Window"

Do not close the IMT terminal as long as the process is on going !It is forbidden to re-use the IMT browser window, intentionally, for anyaction during UNIX patch installation, otherwise the installation of UNIXpatches fails.

The installation consists of 8 steps performed automatically:

Step 1: Transfer filesIf the installation is performed from the OMC-R, the lead time for thistask depends on the MFS-OMC connection. During this task the patchfiles are copied on both MFS control stations

Step 2: Stop NECTAR on standby station

Step 3: Install patch on standby station

Step 4: Start NECTAR on standby station

Step 5: Switch over the stationsNote: The active station becomes standby and the standby becomesactive.

Step 6: Stop NECTAR on standby station

Step 7: Install patch on standby station

Step 8: Start NECTAR on standby station.

3. When "Unix patch installation finished" is displayed, click on [ OK ]

168 / 176 3BK 20935 AAAA PCZZA Ed.20


4. Verify that the patch was correctly installed. In the IMT,select:Software->Unix patch management->Display patch versions.

5. Wait for the message that confirms that UNIX patches on both stationsare consistent.

Click on [ OK ]

6. Close the IMT session

7.5.5 SRM Hardware Settings for DS10 Local Disks (RC40)

1. To check the SRM station the control station must be in SRM mode

Note: This mode is accesible only using Indirect Connection with ControlStations, through IOLAN (Section 7.5.2.3)

2. Check the mandatory SRM hardware settings with the list:

To check this table the station must be in SRM mode (you have to beconnected through IOLAN), then type the command:>>>show

Item DS10/RC40 with RMC V1.2

console serial

auto_action RESTART

bootdef_dev dqa0.0.0.13.0

boot_osflags A

boot_reset ON

ewa0_protocols BOOTP

ewb0_protocols BOOTP

ewa0_mode fast*

ewb0_mode fast*

pka0_host_id 7

full_powerup_diags OFF

kbd_hardware_type PCXAL

language 36

license MU

os_type UNIX

pci_party ON

rmc_halt ENABLED

scsi_poll ON

3BK 20935 AAAA PCZZA Ed.20 169 / 176


Item DS10/RC40 with RMC V1.2

scsi_reset ON

tt_allow_login 1

com1_baud 9600

com1_flow SOFTWARE

com1_mode SNOOP

com1_modem OFF

com2_baud 9600

Table 17: Hardware Settings for SRM Configuration

* these variables are to set up to the values depending on the applicationneeds

ewx0_mode=’fast’ for 100BaseT hub or switch.

ewx0_mode=’twisted-pair for 10BaseT hub or switch.

3. To change one parameter use the following command>>>set <parameter> <new value>

7.5.6 Rebuild Shared Disk Configuration - Install LSM (for RC23)

The purpose of this section is to re-create the shared disk configuration.

This section is applicable only for RC23 platforms: DS10 with external shareddisk and AS800.

7.5.6.1 Prerequisites1. Check if a valid backup is saved in usr/backup_mib on STATION A or in a

safe place on OMC-R ( /alcatel/var/share/MFSbackup ) .

2. Check if is a shared disk re-syncronization in progress :

type the following command on active station:# ps - ef | grep fsgen

if a process fsgen is displayed, wait and perform the operation few

minutes later (this operation can take as long as 30 minutes).

if no synchronisation process is in progress (there is no answer,except

the grep) go to the next check.

170 / 176 3BK 20935 AAAA PCZZA Ed.20


3. Check the LSM configuration using the following command on the activecontrol station:

# /usr/sbin/volprint - Agts

It returns the following answers ( the length of diskA and diskB may bedifferent than below , but identical on both logical disks) :

Figure 53: On an AS800 machine

3BK 20935 AAAA PCZZA Ed.20 171 / 176


Figure 54: On DS10 machines

172 / 176 3BK 20935 AAAA PCZZA Ed.20


This procedure involves the restart of both control stations under UNIX, theuse of a valid backup of the mibs, so it must be used in case of emergencyonly. It is performed by a tool script called install_lsm which is available in apackage named INSTALL_xxx.tar (xxx stands for the current version) onthe delivery CDROM.

7.5.6.2 Procedure1. Insert MFS CDROM in Station A.

2. Mount the CDROM on Station A:

On AS800:# mount -r -t cdfs -o rrip /dev/rz4c /mnt

On DS10:# mount -r -t cdfs -o rrip /dev/rz8c /mnt

3. The script rebuilds the shared disks content from the most recent backupfile. The script must be downloaded on the control station “A”.

Copy the INSTALL package from /mnt to a temporary directory and extractthe procedure:

# cp /mnt/INSTALL_xxx.tar /tmp# cd /tmp; tar xvf INSTALL_xxx.tar install_lsm

4. Stop nectar on both control stations, beginning with standby station :# /usr/mfs/bin/mfs_stop_nectar

Confirm the reboot.

Wait until both stations have fully rebooted under UNIX, when directconnection (telnet) is possible again.

5. Log in as root on STATION_A. Check in /usr/backup_mib if the desiredbackup file to restore is present. If backup has been copied previously ona safe place different than above (OMC…) , copy the file in the directory/usr/backup_mib . Remove or save all backup files more recent than thechosen one (remove for instance the string “ backup “ in their name). Thebackup file name to exploit must include the string “backup”.

6. Launch install_lsm script :# /tmp/install_lsm

Wait for the end of the process.

7. Restart STATION A :#usr/mfs/bin/mfs_start_nectar -site


8. Restart STATION B :#usr/mfs/bin/mfs_start_nectar -site


9. Eject CDROM.

3BK 20935 AAAA PCZZA Ed.20 173 / 176


7.5.7 Rebuild Shared Disk Configuration - Install LSM (for RC40)

The purpose of this section is to re-create the shared disk configuration in caseof MIB corruption and when the Restore data from IMT can not be performed.

This section is applicable only for DS10 RC40 platforms.

7.5.7.1 Prerequisites1. Check if a valid backup is saved in /usr/backup_mib on STATION A or in a

safe place on OMC-R ( /alcatel/var/share/MFSbackup ) .

2. Verify that on STATION_A in /usr/backup_mib there is only one file (thechosen backup) with the string " backup " in their name

This procedure involves the restart of both control stations underUNIX, the use of a valid backup of the mibs, so it must be usedin case of emergency only. It is performed by a tool script calledinstall_rc40_lsm which is available on the delivery CDROM in the path/OAM-MFSB9–RC40–xx.tar.gz/OAM-MFSB9.RC40–xx//OAMMFSB9RC40PREINSTALLxx.gz/OAMMFSB9RC40PREINSTALLxx//usr/opt/OAMMFSB9RC40xx/mfs/bin (xx stands for the current packageversion) .

1. Insert MFS CDROM in Station A.

2. Mount the CDROM on Station A:# mount -r -t cdfs -o rrip /dev/rz8c /mnt

3. The script rebuilds the shared disks content from the most recent backupfile. The script must be downloaded on the control station “A”.

Copy the OAM-MFSB9-RC40-xx.tar.gz package from /mnt to a temporarydirectory and unpack it:

# cp /mnt/OAM-MFSB9-RC40-xx.tar.gz /var/tmp# cd /var/tmp# gunzip OAM-MFSB9-RC40-xx.tar.gz# tar xvf OAM-MFSB9-RC40-xx.tar

4. In the directory OAM-MFSB9.RC40–xx, rename theOAMMFSB9RC40PREINSTALLxx file, then unpack it:

# cd OAM-MFSB9.RC40-xx# mv OAMMFSB9RC40PREINSTALLxxOAMMFSB9RC40PREINSTALLxx.gz# gunzip OAMMFSB9RC40PREINSTALLxx.gz

5. Run the following command to extract the procedure:# tar xvf OAMMFSB9RC40PREINSTALLxx

The script is available in the path ./usr/opt/OAMMFSB9RC40xx/mfs/bin.

174 / 176 3BK 20935 AAAA PCZZA Ed.20


7.5.7.2 Procedure1. Save the remote inventory file, see Backup NORIMFS file (Section 7.1.3)

If the procedure is performed from OMC-R, save the remote inventoryfile on OMC-R.

2. Stop nectar on both control stations, beginning with standby station:# /usr/mfs/bin/mfs_stop_nectar

Confirm the reboot.

Wait until both stations have fully rebooted under UNIX, when directconnection (telnet) is possible again.

3. Log in as root on STATION_A.

Check into the folder /usr/backup_mib if the desired backup file to restoreis present.

If backup has been copied previously on a safe place different than above(OMC...) , copy the file in the directory /usr/backup_mib .

4. Launch install_rc40_lsm script on STATION_A and wait until theaction is finished:

# /usr/mfs/bin/install_rc40_lsm

5. Restart STATION A in site mode:<STATION_A># usr/mfs/bin/mfs_start_nectar -site

Confirm the reboot and wait until the reboot is finished when directconnection (telnet) is possible again.

6. Restart STATION B in site mode:<STATION_B># usr/mfs/bin/mfs_start_nectar -site


7. Restore the remote inventory file:

If the procedure is performed from PC , see Restore the NORIMFS File(Section 7.1.9)

If the procedure is performed from OMC-R, copy the remote inventoryfile in /omcxchg/ri on STATION A.

3BK 20935 AAAA PCZZA Ed.20 175 / 176


BLANK PAGE BREAK

176 / 176 3BK 20935 AAAA PCZZA Ed.20

Evolium A9135 MFS Maintenance Handbook

Documents

Transcript of Evolium A9135 MFS Maintenance Handbook