A1353-RA Network Administration Handbook ed22.pdf

Alcatel BSS

A1353-RA Network

Administration Handbook

OMC Document

Procedural Handbook

Release B9

3BK 20903 AAAA PCZZA Ed.22

Status RELEASED

Short title A1353-RA Network Administration Handbook

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 / 238 3BK 20903 AAAA PCZZA Ed.22

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.1.1 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.1.2 Using the OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.2 Maintaining the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.2.1 Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.2.2 System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.2.3 Preventive Maintenance Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.2.4 HSI Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2 Backup and Restore of OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.1.1 Types of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1.2 Type and Rotation of Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.1.3 Backup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.2 Perform a Full or Incremental Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.2.1 Perform a Full Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.2.2 Schedule a Full Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.2.3 Perform an Incremental Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.2.4 Schedule an Incremental Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.2.5 Verify the Amount of Data Stored on Tape after an OMC Backup . . . . . . . . . . . . 352.2.6 Perform a Backup with a Centralized Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.3 Perform a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.3.2 Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.3.3 Perform a Restore with a Centralized Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2.4 Prepare SUN StorEdge 3510FC Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3 Access Rights Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.2 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.1 Default Password Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.2.2 Create New Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.2.3 Modify a Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.2.4 Delete Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.2.5 List Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.2.6 Display Global Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.3 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.3.1 Add Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.3.2 Reset User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.3.3 Delete Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.3.4 List Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.3.5 Display Current Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.3.6 Display Login Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.3.7 Display Last Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.3.8 Change Own Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.3.9 Assign Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.3.10 Remove Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.3.11 Unlock axadmin Account - Wrong Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.4 OMC-R Application Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.4.1 BSSUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.4.2 MFSUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.3 RNUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653.4.4 OAM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3BK 20903 AAAA PCZZA Ed.22 3 / 238

Contents

3.4.5 AS CurrentUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.4.6 AS HistoricalUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.4.7 IMT Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.4.8 SEC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.4.9 Other Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3.5 OMC-R FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.1 SYSTEM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.2 DOC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.3 OWN_MRT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.4 DSMUSM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.5 OSM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.6 TELECOM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.7 OAM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.5.8 ASCURUSM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.5.9 PERF_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.5.10 ASHISUSM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5.11 OSM_USER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5.12 SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5.13 ASHISUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.5.14 RNUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.5.15 BSSUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.16 MFSUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.17 TRACE_VIEWER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.18 OAM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.19 RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.20 MFSUSM_RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.21 BSSUSM_RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.22 CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.23 ASHISUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.24 RNUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.5.25 BSSUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.5.26 MFSUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.5.27 ASCURUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.5.28 ASCURUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.5.29 ASCURUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.5.30 HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.5.31 RNUSM_HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.5.32 BSSUSM_HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.33 SOFTWARE_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.34 BSSUSM_SOFTWARE_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.35 MFS_BACKUP_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.36 PRC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.37 RNUSM_PRC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.38 PRC_RESTRICTED_ACCESS_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.39 RNUSM_PRC_RESTRICTED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.40 MLU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.5.41 RNUSM_MLU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.5.42 ACCESS_TO_UNIX_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.5.43 XTERM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.5.44 PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.5.45 PERF_VIEWER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.5.46 RNUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.5.47 MFSUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.5.48 BSSUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.5.49 RESTRICTED_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.5.50 BSSUSM_RESTRICTED_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . 913.5.51 COMMAND_MODE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4 / 238 3BK 20903 AAAA PCZZA Ed.22

Contents

3.5.52 COMMAND_MODE_FAD_A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.5.53 INHIBIT_OAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.5.54 INHIBIT_FAD_CONTROL FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.5.55 RNUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.56 UFM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.57 RNO_TB_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.58 OAM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.5.59 ASHISUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.5.60 MFSUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.61 BSSUSM_RI_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.62 BSSUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.63 ASCURUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.5.64 MULTI_OMC3_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.5.65 UFM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.5.66 NPA_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.5.67 DCN_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.5.68 AS_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.5.69 PROCESS_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.5.70 USER_AND_PLATFORM_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . 1023.5.71 READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.5.72 RNUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.5.73 BSSUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.5.74 MFSUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.5.75 REMOTE_INVENTORY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.5.76 ENSUSM_RI_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.5.77 FULL_MRT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.5.78 Global_Log_Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.5.79 MFSSNMP_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.5.80 OAM_MRTG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.5.81 MFSUSM_NAVIGATE_MRTG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.5.82 IMT_CONF_GPU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.5.83 IMT_CONF_MFS_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.5.84 IMT_ADMIN_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.5.85 IMT_PLATFORM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.5.86 IMT_GPU_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.5.87 IMT_MFS_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.5.88 IMT_MFS_ADMIN_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.5.89 IMT_CONF_READ_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.5.90 IMT_READ_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.5.91 IMT_MFS_PLATFORM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.5.92 ACO_MNG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.5.93 ACO_NTC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

3.6 Operator Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.6.1 Operators window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.6.2 Edit window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

3.7 Terminal Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103.7.1 Create Terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103.7.2 Profiles window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

3.8 Operator Profile Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113.8.1 Display All Available Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.8.2 Create Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.8.3 Delete Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.8.4 Display Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.8.5 Modify an Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143.8.6 Assign Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153.8.7 Unassign Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

3.9 Terminal Profile Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

3BK 20903 AAAA PCZZA Ed.22 5 / 238

Contents

3.9.1 Display All Available Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163.9.2 Create Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163.9.3 Delete Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173.9.4 Display Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173.9.5 Modify a Terminal Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173.9.6 Attach/Detach Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

3.10 OAD Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193.10.1 Create OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193.10.2 Delete OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203.10.3 Display OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203.10.4 Modify Access Rights to OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

3.11 FAD Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.11.1 Create FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.11.2 Delete FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.11.3 Display FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213.11.4 Modify FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

3.12 Restore Default FADs and Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223.13 FTP Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233.14 Change FTP User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253.15 Non-OMC-R Users Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253.16 Activate MPM on OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

4 Day-To-Day Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

4.1 Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.1.1 Display Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.1.2 From the Hardware Inventory Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.1.3 From the Workstation Management Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

4.2 Software Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.2.1 Display Software Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.2.2 Display Third Party Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.2.3 Display Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.2.4 Display Changed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.2.5 Display Binary Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

4.3 Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.3.1 Capture Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.3.2 Display Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.3.3 Capture Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.3.4 Display Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.3.5 Lock/Unlock Failure Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.3.6 Delete Failure Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.3.7 Archive Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.3.8 Display Archived Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.3.9 Delete Archived Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4.4 Monitor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.4.1 Disk Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.4.2 Internet Protocol Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

4.5 Start the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.6 Start OMC-R Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

4.6.1 From a UNIX Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.6.2 From OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

4.7 Stop OMC-R Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.7.1 Whole OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.7.2 Shutdown USMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

4.8 Stop the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.9 Start Application Process from DSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.10 Stop Application Process from DSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.11 Process and Platform Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.12 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

6 / 238 3BK 20903 AAAA PCZZA Ed.22

Contents

4.12.1 Add Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.12.2 Remove Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434.12.3 Add X Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444.12.4 Remove X Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.12.5 Add Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.12.6 Remove Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.12.7 Define Station Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.12.8 Define User Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.12.9 Documentation Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494.12.10 LDAP Hosts Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

4.13 Configuration Parameter Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.14 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514.15 Clean Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1524.16 Broadcast Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544.17 Set Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544.18 Run Multiple OMC-Rs from One HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

4.18.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.18.2 Set UNIX Parameters on One OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.18.3 Connection Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564.18.4 Creating a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

4.19 Logs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584.19.1 View Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584.19.2 Logs Merge on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

4.20 Change NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.20.1 Find NMC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.20.2 Stop q3im Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.20.3 Undeclare Current NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624.20.4 Declare New NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

4.21 List NMC and OMC Network Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634.22 Alarm Sublist and Filter Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

4.22.1 Alarm Sublists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.22.2 Alarm Sublist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654.22.3 Pre-Defined Aging Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.22.4 Change Default Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694.22.5 Retrieve Original Default Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694.22.6 Change Default for Existing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.22.7 Retrieve Original Default for Existing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.22.8 Add Alarm Sublist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

4.23 Navigate in a New Mozilla Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714.24 Secure External Workstation and User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

4.24.1 Add Secure External Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.24.2 Secure External Workstation Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.24.3 Delete Secure External Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

4.25 A1353-RA MRTG View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.25.1 SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.25.2 Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.25.3 MRTG Index Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764.25.4 Detailed Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

4.26 Increase the Trace Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834.27 Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844.28 Security Impact on the A1353-RA Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

4.28.1 AUTOMOUNT Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854.28.2 BOOTPARAMD Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

4.29 Network Information Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864.30 DLS Periodic Check Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874.31 SE3510 Disk Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874.32 Activate Multiple LAN Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

3BK 20903 AAAA PCZZA Ed.22 7 / 238

Contents

4.33 Send Mail Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904.34 Inter OMC-R Adjacency Consistency Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914.35 Configure the VNC Server for RAMSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

5 Modify IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.1 Impact and Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

5.1.1 Impact on Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.1.2 Duration of IP Address Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

5.2 Modify the IP Address for the Entire Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.2.1 Global Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.2.2 Modify the IP Address of the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.2.3 Modify the IP Address of an X Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.2.4 Modify the IP Address of the Master and Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 1985.2.5 Modify the IP Address of the BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035.2.6 Modify the IP Address of the MFS Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045.2.7 Modify the IP Address of the Cisco Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075.2.8 Modify the IP Address of the NPA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075.2.9 Modify the IP Address of the NPA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

5.3 Modify the IP Address for One Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095.3.1 Modify the IP Address of an X Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095.3.2 Modify the IP Address of the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105.3.3 Modify the IP Address of a Network Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105.3.4 Modify the IP Address of the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115.3.5 Modify the IP Address of the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145.3.6 Modify the IP Address of the BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2155.3.7 Modify the IP Address of the MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165.3.8 Modify the IP Address of the Cisco Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165.3.9 Modify the IP Address of the NPA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175.3.10 Modify the IP Address of the NPA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

6 Administrative Tasks for MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196.1 Configure Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2206.2 Display Visu-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216.3 Manage ASCII (OBSYNT) Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216.4 Daily OBSYNT Files Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216.5 Start/Stop MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

6.5.1 Starting MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236.5.2 Stopping MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

7 Backup/Restore MFS Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2267.2 Backup MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

7.2.1 Who Can Perform a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.2.2 O&M and Telecom Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.2.3 Size of Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.2.4 Duration of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

7.3 Backup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.3.1 Backup to Local Disk on MFS Control Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277.3.2 Upload to OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

7.4 Restore MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297.4.1 Who Can Perform a Restore of the Configuration Files . . . . . . . . . . . . . . . . . . . . 2297.4.2 O&M Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297.4.3 Telecom Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297.4.4 Duration of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

7.5 Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307.5.1 Download from OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307.5.2 Restore MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

8 Upgrade Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

8 / 238 3BK 20903 AAAA PCZZA Ed.22

Contents

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2348.2 Upgrade of Customer Documentation CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

8.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2348.2.2 Different Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

8.3 Launch Documentation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2368.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

8.4.1 No Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2368.4.2 Correcting Monitor Color Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

3BK 20903 AAAA PCZZA Ed.22 9 / 238

Figures

FiguresFigure 1: Installation, Backup and Restore Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 2: Type and Rotation of Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 3: Backup of Modified Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 4: Application Manager Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Figure 5: Example Create Action Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Figure 6: A1353-RA MRTG Main View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Figure 7: A1353-RA MRTG MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Figure 8: Detailed Statistics MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Figure 9: Detailed Statistics A9130 BSC Evolution View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

10 / 238 3BK 20903 AAAA PCZZA Ed.22

Tables

TablesTable 1: Preventive Maintenance Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 2: Types of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 3: Password Composition Rules Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 4: FTP server directory organization for omc3ftp , rno , pmuser and laser . . . . . . . . . . . . . . . . . . . . 124

Table 5: FTP server directory organization for metrica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Table 6: Default account settings for non-OMC-R users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Table 7: Password policy for non-OMC-R users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Table 8: DSMUSM Features Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

3BK 20903 AAAA PCZZA Ed.22 11 / 238

Tables

12 / 238 3BK 20903 AAAA PCZZA Ed.22

Preface

Preface

Purpose The Administration Guide describes how to perform day-to-day administrationof the A1353-RA including:

Backup/restore

Access rights

Miscellaneous administration tasks

MPM administration.

What’s New In Edition 22The section Modify the IP Address of the MFS Stations (Section 5.2.6) hasbeen restructured due to system evolution.

Improvements were made in section DLS Periodic Check Tool (Section 4.30)due to system evolution.

In Edition 21The following sections were modified due to system evolution:

Perform a Backup with a Centralized Solution (Section 2.2.6)

Perform a Restore (Section 2.3).

In Edition 20Creation of the Daily OBSYNT Files Availability (Section 6.4) for the OBSYNTgeneration description.

In Edition 19Section Configure the VNC Server for RAMSES (Section 4.35) was created todescribe the configuration of VNC server for RAMSES.

Section SNMP Collector (Section 4.25.1) was added due to system evolution.

3BK 20903 AAAA PCZZA Ed.22 13 / 238

Preface

In Edition 18Creation of the section Inter OMC-R Adjacency Consistency Feature (Section4.34).

Improvements were made to section Activate Multiple LAN Feature (Section4.32)due to system evolution.

Update the Perform a Backup with a Centralized Solution (Section 2.2.6) andPerform a Restore with a Centralized Solution (Section 2.3.3) sections.

In Edition 17Modification done in Perform a Backup with a Centralized Solution (Section2.2.6) and Perform a Restore with a Centralized Solution (Section 2.3.3).Description of centralized backup/restore solution.

In Edition 16Modification done in Activate Multiple LAN Feature (Section 4.32) for betterunderstanding.

Creation of Activate Multiple LAN Feature (Section 4.32).

In Edition 15Modification done in Perform a Full Backup from OSM (Section 2.2.1). Thebackup complete can finish with warnings.

In Edition 14Creation of the Send Mail Activation (Section 4.33) section.

Section Update Master IP Address in the BSC Evolution (Section 5.2.4.1) hasbeen updated due to system evolution.

Improve of Perform Restore (Section 2.3.2.1) section.

Scenario update in A9135 MFS (Section 5.2.6.2).

Section SE3510 Disk Replacement (Section 4.31) has been added dueto system evolution.

Modification done in A9135 MFS (Section 5.2.6.2), Update Master/Agent IPAddress in the MFS (Section 5.2.4.2) and Main Page (Section 4.25.2) bymodifying the MFS IP address change procedure.

In Edition 13Modification done in Network Information Summary (Section 4.29) section toverify the presence of MFS Evolution RI files.

Modification done in Perform Restore (Section 2.3.2.1) section to verify thelogical drive status for SE 3510.

In Edition 12Creation of section HSI Replacement (Section 1.2.4).

Modification done in A9130 MFS Evolution (Section 5.2.6.3) and Modify the IPAddress of the MFS (Section 5.3.7) for the double switchover of the stations.

Modification done in Modify the IP Address of the BSC Evolution (Section 5.2.5),Update Master IP Address in the BSC Evolution (Section 5.2.4.1) and Modifythe IP Address of the BSC Evolution (Section 5.3.6) by explain better the tasks.

14 / 238 3BK 20903 AAAA PCZZA Ed.22

Preface

A new section was added, Activate MPM on OMC-R (Section 3.16) .

Modification done in Perform a Full Backup from OSM (Section 2.2.1) , bycorrecting the path for backup log.

Modification done in Default Password Rules (Section 3.2.1) and Reset UserPasswords (Section 3.3.2) for Password policy section.

Modification done in Modify the IP Address of the Master and Agent (Section

5.2.4) , Modify the IP Address of the HMI (Section 5.2.2) , Modify the IPAddress of the NPA Server (Section 5.2.8) , Modify the IP Address of

the Master (Section 5.3.4) , Modify the IP Address of the Agent (Section5.3.5) , Modify the IP Address of the HMI (Section 5.3.2.2) , Modify the IP

Address of the NPA Server (Section 5.3.9) section by adding informationregarding the netmask and defaultrouter.

Modification done in Modify the IP Address of the Master and Agent

(Section 5.2.4) and Modify the IP Address of the Master (Section 5.3.4)for formattedHtml file update, NSAP configuration and SEC online help

regarding the change of ip address of the Master.

Adding in Backup/Restore section Introduction (Section 2.1) the LEGATOdocument .

Modification done in Manage ASCII (OBSYNT) Output (Section 6.3) section

by adding the MFS directory.

A new section was added, Activate MPM on OMC-R (Section 3.16) .

Modification done in Perform Restore (Section 2.3.2.1) section to verify thelogical drive status for SE 3510.

Modification done in Prepare SUN StorEdge 3510FC Array (Section 2.4)section. Detailing the procedure.

In Edition 11Network info summary easily available at OMC-R. New section introducedNetwork Information Summary (Section 4.29) .

Add the Introduction (Section 2.1) .

Introduction of the Create Terminal window (Section 3.7.1) .

Arrange in right order the subsections from Modify the IP Address of the MFSStations (Section 5.2.6) .

The documentation upgrade from old without Verity to new with Verity can bedone without to save the license before. Improvement done in Upgrade ofCustomer Documentation CD-ROM (Section 8.2) .

The IDs of sections Create FAD (Section 3.11.1) and Modify FAD (Section3.11.4) are modified to correspond to the OMCGseccf package of theSEC-Help.

The password length was increased. Modification done in Default PasswordRules (Section 3.2.1) .

After an MFS IP address modification, a system backup must be performed.Modification done in A9130 MFS Evolution (Section 5.2.6.3) .

3BK 20903 AAAA PCZZA Ed.22 15 / 238

Preface

In Edition 10The section "Verify the amount of data stored on tape after an OMC backup"was removed from the document.

Restriction 3BKA20FBR159175 removed from Perform a Restore (Section 2.3)

To reduce the restore time, wait only for the root and usr mirrorsresynchronization. Updates in step (8) and step (12) in (in section 2.3.2.1)

Update Display Changed Files (Section 4.2.4) .

In Edition 09Documentation installation script improvements. Verity search engine isoptional. Updates in Upgrade Documentation (Section 8) .

Editorial improvements of Display Software Applications (Section 4.2.1) andDisplay Third Party Information (Section 4.2.2) sections.

New section about the amount of data on a tape, section 2.2.5 Verify theamount of data stored on tape after an OMC backup:

It is strongly recommended to preserve existing Alcatel FADs. Updates inCreate FAD (Section 3.11.1) step (3) and Modify FAD (Section 3.11.4) .

Update MRTG Index Page (Section 4.25.3) .The following new sections are added:

Operator Management (Section 3.6)

Terminal Management (Section 3.7) .

In Edition 08For SUN StorEdge 3510FC Array preparing phase, only the serial connectionmust be used. Updates in Prepare SUN StorEdge 3510FC Array (Section 2.4)

MX-MFS introduction. Impacts in A9135 MFS (Section 5.2.6.2) , A9130 MFSEvolution (Section 5.2.6.3) , Update Master/Agent IP Address in the MFS(Section 5.2.4.2) , Modify MFS IP Address in OMC-R (Section 5.2.6.3) andStart MFS Supervision (Section 5.2.6.4)A9130 BSC Evolution was added in MRTG. The following sections wereupdated

A1353-RA MRTG View (Section 4.25)

MFS MRTG Index Page (Section 4.25.3.1)

A9130 BSC Evolution MRTG Index Page (Section 4.25.3.2)

Detailed Statistics (Section 4.25.4)The following new sections are added:

Operator Management (Section 3.6)

Terminal Management (Section 3.7) .

16 / 238 3BK 20903 AAAA PCZZA Ed.22

Preface

In Edition 07MF-improved_restore_OMC.sh.V490 andMF-improved_restore_OMC.sh.E4500 are now integrated in scriptMF-improved_restore_OMC.sh , so they were removed from (in section2.3.2.1) .

AUTOMOUNT and BOOTPARAMD services impact on remote A1353-RAinstallation is described in Security Impact on the A1353-RA RemoteInstallation (Section 4.28)

Only one LUN on all channels must be used. Updates in Prepare SUNStorEdge 3510FC Array (Section 2.4) , step (5)

Update Restore MFS Data (Section 7.5.2) with a re-synchronisation of the MFS.

In Edition 06Synchronization check introduced in step (12) in (in section 2.3.2.1) .

Array to host connection mode must be set on "Loop only". Updates in PrepareSUN StorEdge 3510FC Array (Section 2.4) paragraph.Sun Fire V490 station introduction:

A new section was added: Prepare SUN StorEdge 3510FC Array (Section2.4)

(in section 2.3.2.1) was updated.

Modification of the "Evolium" word in GSM documentation.

In Edition 05Names of the traces are changed in Increase the Trace Level (Section 4.26)

In Edition 04(in section 2.3.2.1) was improved by:

copying MF-improved_restore_OMC.sh.V490 script for the restore

operation

copying extra files in case of StorEdge Array 3510 attached to the machine.

In Edition 03Restriction introduction in Perform a Restore (Section 2.3)xhost + command is modified for security reasons, in:

Run Multiple OMC-Rs from One HMI (Section 4.18)

Connection Procedure (Section 4.18.3)

Creating a Shortcut (Section 4.18.4) .

3BK 20903 AAAA PCZZA Ed.22 17 / 238

Preface

In Edition 02Command that verifies the state of the tapes is inserted in Perform a Full orIncremental Backup (Section 2.2)Security improvement:

rlogin command must be replaced with the ssh command. Updates in

Remove X Stations (Section 4.12.4)

New section for non-OMC users (Non-OMC-R Users Customization(Section 3.15) )

Updates regarding the unlock of users account (Reset User Passwords(Section 3.3.2) )

Cosmetic updates in FTP Users (Section 3.13) .

LDAP server is case insensitive. Updates in Add Users (Section 3.3.1) .

In the Add Workstations (Section 4.12.1) section, add a note regarding acheck of /etc/hosts .

Recommendation regarding Operator Profile added in Operator ProfileManagement (Section 3.8) .

metrica FTP user introduction in FTP Users (Section 3.13)

When setting the color depth, the resolution is given: Correcting Monitor ColorProblems (Section 8.4.2) .

Update Modify the IP Address of the Master and Agent (Section 5.2.4) .

Introduction of new OMC-R Application Functions (Section 3.4) and OMC-RFADs (Section 3.5) and Terminal Profile Management (Section 3.9) .

Remove Basic and QOS Alerters from Administrative Tasks for MPM (Section6) .

It is possible to Restore Default FADs and Profiles (Section 3.12) .

Update paragraph Upgrade Documentation (Section 8) .

New paragraph: Hardware Inventory (Section 4.27) .

In troduction of SEC7 and FAD editor in Access Rights Management (Section3) .

Introduction of LDAP in Modify IP Addresses (Section 5) .

In Edition 01Creation of the document from B8 release.Creation of:

Main Page (Section 4.25.2)

MRTG Index Page (Section 4.25.3)

Detailed Statistics (Section 4.25.4)

A1353-RA MRTG View (Section 4.25) .

Improvement of Backup and Restore of OMC-R (Section 2) to use a set oftapes for full backup/restore.

Update with the right path for OSM improved restore script in Perform aRestore (Section 2.3) .

Audience The handbook is intended for Network administrators.

18 / 238 3BK 20903 AAAA PCZZA Ed.22

Preface

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

Alcatel operations and maintenance concepts

Telecommunications engineering

UNIX concepts.

3BK 20903 AAAA PCZZA Ed.22 19 / 238

Preface

20 / 238 3BK 20903 AAAA PCZZA Ed.22

1 Introduction

1 Introduction

Read this section before you start the procedures.

3BK 20903 AAAA PCZZA Ed.22 21 / 238

1 Introduction

1.1 Before You Start

1.1.1 Access Rights

You must have the administrator profile named axadmin_special_profileassigned to you for access to the OMC-R.

1.1.2 Using the OSM

On the OSM, a number of options are available.

These are represented by a click button and the option name.

If the click button is orange and its associated feature name is underlined

you can click on either the button or the name. If you click on the button, youare offered more choices than if you click on the name (for example, you are

asked to decide which workstation you want information for).

If the button is gray, the name is underlined and you must click on the

name to proceed.

If the name is not underlined, the button is orange and you must clickon the button to proceed.

You can click on [ Back ] , [ Forward ] or [ Exit ] at the top of each screen.

Click on [ Back ] to go to whichever screen you were looking at last.

Click on [ Forward ] after you have used the [Back] button. It takes you to

where you started from, moving forward a screen at a time.

Click on [ Exit ] to close the OSM.

Note: For a distributed A1353-RA system (that is, where more than one workstationcan be used as the main workstation), any change to the system made by anAdministrator applies to all stations.

1.2 Maintaining the SystemRoutine maintenance helps prevent or reduce the number of system failures.

During normal operation sufficient resources are available to the OMC-R,particularly those of:

Disk space

System resources.

1.2.1 Disk Space

Although sufficient resources are available when the application is initiallystarted, normal operation of the OMC-R gradually uses up the available diskspace. It is therefore necessary to perform some system maintenance regularlyto preserve sufficient disk space for correct operation (see Table 1 ).

22 / 238 3BK 20903 AAAA PCZZA Ed.22

1 Introduction

1.2.2 System Resources

Each action requested by an operator results in the dynamic creation of a UNIXprocess. The process is automatically killed when the action ends. However, ifthe action cannot be executed or ends abnormally, the processes are not killed.In this case the system resources used by those processes are not release.

The decrease in available resources reduces the processing capacity of theOMC-R. This can cause other problems which in crease the number ofunrealized processes, and so on.

System can hang, crash or be slow to respond. If system resources are notreleased or a process continues to grow, then eventually all system resourcesare used up. Perform the preventive maintenance tasks listed in Table 1 atthe appropriate time.

1.2.3 Preventive Maintenance Task Schedule

The following table lists the preventive maintenance tasks and the scheduledtime periods.

How Often Routine Task Where If there is a problem

Weekly Shutdown USM sectionof Stop OMC-RApplication (Section4.7)

In UNIX, Master

If OSM, any machine

-

Every three months Stop the System (Section4.8) and then Start theSystem (Section 4.5)

In UNIX, Master

If OSM, any machine

-

After installation,upgrade, massivenetwork change, or whenIncremental Backup uptakes just as long as aFull Backup

Full Backup, see Performa Full or IncrementalBackup (Section 2.2)

If UNIX, Master

If OSM, any machine

System will attemptto resynch disks andreturn to stable state.Analyze log file andsolve problem.

Depends on systemactivity. Daily if lots ofnetwork change. Weeklyor monthly if little or nonetwork change.

Incremental Backup,see Perform a Full orIncremental Backup(Section 2.2)

If UNIX, on Master

If OSM, any machine

Analyze log file and solveproblem.

In case of system fault Failure Management,see Failure Management(Section 4.3)

OSM Warning! These files cantake up to 500 Mbytes ofdisk space.

Daily Monitor the System DiskUsage, see MonitorSystem (Section 4.4)

OSM -

3BK 20903 AAAA PCZZA Ed.22 23 / 238

1 Introduction

How Often Routine Task Where If there is a problem

Daily Process and PlatformMonitoring, see Processand Platform Monitoring(Section 4.11)

OSM -

After installation andwhen change scheduling

Scheduling, seeScheduling (Section4.14)

OSM Check crontab.

Daily (automatic usingcrontab) and manual iffile system is full or filesare no longer needed.

Automatic or manualClean-up of files, seeClean Up (Section 4.15)

OSM Check crontab to see ifscheduled.

Before performingbackup or systemshutdown

Broadcast Messages,see BroadcastMessages (Section4.16)

OSM Check who is logged onand try to contact them(e.g. by phone, e-mail,etc.).

In case of problem. View User Logs, seeView Logs (Section4.19.1)

OSM -

After every Software orHardware modification

Backup MFS, seeBackup MFS Data(Section 7.2)

OMC-R using remoteTerminal

Check IP connection andthat MFS is running.

When power on ofmachines and startingOMC-R application fromUNIX.

Start the System,see Start the System(Section 4.5)

Master Host, all othermachines.

-

When starting orre-starting OMC-Rapplication using DSM

Start OMC-RApplication, see StartOMC-R Application(Section 4.6)

DSM -

When only stopping theOMC-R application orUSMs

Stop OMC-R Application,see Stop OMC-RApplication (Section4.7)

OSM -

When stopping OMC-Rapplication and power offof machines

Stop the System, seeStop the System (Section4.8)

OSM and each machine -

Table 1: Preventive Maintenance Task Schedule

1.2.4 HSI Replacement

1. In case of HSI network board failure, if the old board is X1155A AND there isnot a similar one available, the new generic board X1355A must be used.

24 / 238 3BK 20903 AAAA PCZZA Ed.22

1 Introduction

2. In this case call Alcatel support, because the new drivers are installedusing the “A1353-RA Software Replacement with Hardware Change,Same Number of Agents” procedure.

3BK 20903 AAAA PCZZA Ed.22 25 / 238

1 Introduction

26 / 238 3BK 20903 AAAA PCZZA Ed.22

2 Backup and Restore of OMC-R


This section describes how to perform full and incremental backups, as wellas a system restore.

3BK 20903 AAAA PCZZA Ed.22 27 / 238


2.1 IntroductionRegular backups ensure that data loss is minimized in the case of hardware orsoftware failure such as a disk crash. Backing up allows a restore of the OMC-R.

When an OMC-R is installed, a timestamp is made. Full backups back up allthe files more recent than this timestamp. Incremental Backups back up all thefiles more recent than the full backup, see the following figure.

CD 1

CD 2 T1 /etc/TIMESTAMP_INSTALL

CD 3

OptionalSoftware

CD DOC

Full T2 Relevant files younger than T1Backup

Incremental T3 Relevant files younger than T2Backup 1.1

Incremental T4 Relevant files younger than T2Backup 1.2

System Restore

Full T6 All restored files get the actual date/time.Restore 1.0 This allows Backup 2.0 to know to back them up.

Incremental T7 All restored files get the actual date/timeRestore 1.2 This allows Backup 2.0 to know to back them up.

Full T8 Relevant files younger than T5 are backed upBackup 2.0

Incremental T9 Relevant files younger than T8 are backed upBackup 2.1

System Installation

Time

Time

System Failure,go to System Restore

Figure 1: Installation, Backup and Restore Process

The Backup/Restore procedure can also be performed by LEGATO software,refer to document LEGATO User Guide .

28 / 238 3BK 20903 AAAA PCZZA Ed.22


2.1.1 Types of Backup

The following table describes the types of backups and the frequency in whichthey must be performed.

Type Description Recommended Frequency

Full Backup Saves all files. After installation, upgrade, massivenetwork change, or when Incrementalbackup takes just as long as a Fullbackup.

Incremental Backup Saves files that have been modified sincethe last full backup.

Depends on system activity. Dailyif there are many network changes.Weekly or monthly if little or nonetwork change.

Table 2: Types of Backup

2.1.1.1 In Case of FailureIf the backup fails to complete, the script returns the disks and system to aconsistent state. Check for error messages. Solve the problem and retrythe backup.

2.1.1.2 What is Backed Up/Restored ?Only the Master and Agent hosts are backed up and restored.

2.1.1.3 OSMBackups are performed in OSM. Scheduled full/incremental backups are addedto the crontab of axadmin from OSM.

3BK 20903 AAAA PCZZA Ed.22 29 / 238


2.1.2 Type and Rotation of Tapes

Each backup, full or incremental, uses one tape. Use 160 meter extra-longtapes. Never put more than one backup on a tape. As an absolute minimum,two sets of tapes are recommended in case of trouble with one of the sets. Forsecurity reasons, three sets of tapes would increase security significantly.

For example, having two sets of tapes allows rotation of tapes (see thefollowing figure). The tapes for Full Backup 1 can be reused for Full Backup3. Tapes used for Incremental Backup 1.1 can be reused for IncrementalBackup 1.3 and so on.

1234561234561234561212

1212

123456123456123456123456

123456123456123456

123456123456123456123456

123456123456123456

123456123456123456123456

123456123456123456

123456123456123456123456

123456123456123456

123456123456123456123456

123456123456123456

123456123456123456123456

Set 1 Set 2 Set 3

Full Backup 1 Full Backup 2 Full Backup 3

IncrementalBackup 1.1












.

.

.

.

.

.

.

.

.

Figure 2: Type and Rotation of Tapes

30 / 238 3BK 20903 AAAA PCZZA Ed.22


2.1.3 Backup Process

In the following figure, Full Backup 1.0 saves the files. Incremental Backup 1.1saves the files modified since Full Backup 1.0. Incremental Backup 1.2 and 1.3also save all the files since Full Backup 1.0. Full Backup 2.0 saves all the files.

TIMESTAMP_INSTALL

Full Backup 1.0

Incremental Backup 1.1



Full Backup 2.0

Bac

ks u

p fil

es w

ithtim

esta

mps

you

nger

than

Figure 3: Backup of Modified Files

2.1.3.1 Full BackupRegardless of hardware, the Full Backup process works in the same way.

The backup script performs the following:

1. The MPM application is stopped and the Database access is suspended, inorder to keep all the OMC-R data consistent. UNIX continues to operate.

2. Mirrored disks are detached. For Veritas Filesystems, a "snapshot" istaken of the file systems.

3. The database is released and MPM is restarted. The OMC-R is operational.

4. The OMC-R restarts. In a mirrored disk system, the OMC-R only runs on onedisk set during the backup time, while the other detached set is backed up.

5. The OMC-R data is loaded onto tape.

6. The mirror disks are re-attached and the disks that were used for the backupare updated with the changes that occurred on the active disk during thebackup. The snapshots are destroyed.

7. The backup completes.

2.1.3.2 Incremental BackupAn incremental backup procedure is similar to a full backup.

3BK 20903 AAAA PCZZA Ed.22 31 / 238


2.2 Perform a Full or Incremental BackupBefore you backup, you must have:

Administrator access to the A1353-RA

Access to the tape drive(s) of Master and Agent

An unused tape for every server that requires backup (see Type andRotation of Tapes (Section 2.1.2) ).

Note: It is necessary to have a tape for each machine in an Xlarge configurationwhere there is a Master-Agent relationship.

The following prerequisites apply:

Before you backup, verify that the tapes on which the backup is performed,function correctly:

mt -f <device> sta

where <device> is the tape device on which the backup was made (by default/dev/rmt/0cn ).

To check the state of the metadevices, from a console type the command:metastat

Wait for the end of the verification of each disk before continuing. Replaceany disks whose state is not Okay .

32 / 238 3BK 20903 AAAA PCZZA Ed.22


2.2.1 Perform a Full Backup from OSM

Note: There is an outage of 2 minutes during the backup.

When inserting a tape, be sure that it is positioned at the beginning (it isrewinded).

If the data of the Master can not be stored on one tape, a set of tapes must beused. When the tape is full, a window will ask for the next tape.

Procedure To perform a full backup from OSM:

1. Log in as an administrator.

2. Put a new tape(s) into the tape drive(s) of the Master and each Agent(in case of Xlarge configuration).

3. From the OSM Administration Facilities Main Menu, select Administration-> Backup/Restore -> Backup now .

4. Enter the device path in the Device field or keep the default device path(/dev/rmt/0cn ) that is proposed. In case of XLarge configuration the samedevice path is used on all the machines (Master and each Agent).

5. Click on [ Apply ] to start the backup.

If the tape is full (on Master), a pop-up window is displayed with themessage: The tape is full. Please insert next tape and just

after press OK button.

Remove the tape from the drive. Insert a new tape and click on [ OK ]button from the pop-up window.

6. The system carries out the backup steps and sends an e-mail to the userwho started the backup when the backup is complete.

If the sent message contains the text:Backup completed

the backup is complete. If the message contains the text:Backup completed: warning

the backup is finished with warnings. Check the resulting UNIX logs in:/alcatel/var/maintenance/log/

to diagnose the problem. As well as being stored on the system, this log isalso saved on the tape.

If the message contains the text:Failure

The backup failed. Check the resulting UNIX logs in/alcatel/var/maintenance/log/

to diagnose the problem. As well as being stored on the system, this log isalso saved on the tape.

7. After the backup is complete, store the tape in a safe place so it is availablefor the restore in case of a system crash.

3BK 20903 AAAA PCZZA Ed.22 33 / 238


2.2.2 Schedule a Full Backup from OSM

Note: There is an outage of 2 minutes during the backup.

If the data of the Master can not be stored on one tape, a set of tapes must beused. When the tape is full, a window will ask for the next tape.

Procedure To schedule a full backup:



3. From the OSM Administration Facilities Main Menu, select Administration-> Backup/Restore -> Schedule Backup .


5. Enter the time the backup is to be performed in the Hour field.

6. Enter the day the backup is to be performed in the Day field.

7. Enter the month the backup is to be performed in the Month field.

The system carries out the backup at the defined time and sends an e-mailto the user who started the backup when the backup is complete.

8. Click on [ OK ] to accept the scheduling.

9. The backup will start at the given time.

If the tape is full, a pop-up window is displayed with the message: The

tape is full. Please insert next tape and just after press

OK button.

Remove the tape from the drive. Insert a new tape and click on [ OK ]button from the pop-up window.

10. Store the tape in a safe place so it is available for the restore in case of asystem crash.

2.2.3 Perform an Incremental Backup from OSM

Procedure To perform an incremental backup from OSM:



3. From the OSM Administration Facilities Main Menu, select Administration-> Backup/Restore -> Incremental Backup now .


5. Click on [ Apply ] .

The system carries out the backup steps.


34 / 238 3BK 20903 AAAA PCZZA Ed.22


2.2.4 Schedule an Incremental Backup from OSM

Procedure To schedule an incremental backup from OSM:


2. Put a new tape(s) into the tape drive(s).

3. From the OSM Administration Facilities Main Menu, select Administration-> Backup/Restore -> Schedule Incremental Backup .


5. Enter the time the backup is to be performed in the Hour field.

6. Enter the date the backup is to be performed in the Day field.

7. Enter the month the backup is to be performed in the Month field.

8. Click on [ OK ] to accept the scheduling.

The system carries out the backup steps at the defined time and sends ane-mail to the user who started the backup when the backup is complete.


2.2.5 Verify the Amount of Data Stored on Tape after an OMC Backup

The amount of data stored on a tape after an OMC backup can be verifiedfrom Master .

From OSM Administration Facilities:


2. Insert the tape (if not already inserted) in the tape drive of the Master .

3. Select Administration -> Backup/Restore -> Get Tape Usage

4. In the ’Device’ field, the path to the default tape drive is typed. If the tapedrive is different from the default one, type the path to that device.

5. Press the [ Get usage ] button.

6. When the green Finish notification appears, the ’Blocks’ and ’Size’ textfields represents the final values.

3BK 20903 AAAA PCZZA Ed.22 35 / 238


2.2.6 Perform a Backup with a Centralized Solution

Today the only centralized backup solution described in detail is LEGATO. Butthe customers can use any centralized solution. The condition is that somemandatory actions must be performed before and after the backup itself.

In case of backup, the scripts:

are triggered by the Centralized Backup application

prepare the backup data in a predefined directory on the OMC-R disk.

The Centralized Backup application is responsible:

at backup time: for transferring the backup package from OMC-R predefineddirectory to external disks or to external tape devices.

at restore time: for transferring the backup package from the backup location

(external disks or tapes) into the predefined directory on the OMC-R disk.To execute a centralized backup/restore apply Perform a Backup with aCentralized Solution (Section 2.2.6) respectively Perform a Restore with aCentralized Solution (Section 2.3.3) .

As root user perform the tasks described below.

1. Display all the save sets (partitions) for each OMC-R and note them down:cd /usr/bin./take_save_sets_legato.sh

2. Exclude some directories during the backup procedure. A restore of thesedirectories, explicitly defined as excluded, can cause a system crash./tmp/backup/var/run

3. Run the save_pre_legato.sh script for each OMC-R, which performs thefollowing:

runs system checks

creates a consistent backup image by flushing application data(ObjectStore database)

hangs ObjectStore

stops MPM and the Network Time Protocol daemon (xntpd )

makes the snapshots of the system available in the separate partitions.

/usr/bin/save_pre_legato.sh

4. The image of the partitions needed for backup are saved in the files withextension .backfile located in /backup/backdir directory.

5. Configure the backup solution with the partitions noted down in step 1. Payattention not to backup the directories excluded at step 2. The backup filesstored on OMC-R must be saved on external devices (disks, tape) becausethe save_post_legato.sh script delete the backup files.

6. Re-establish the initial configuration by re-synchronizing the snapshot withthe current system data:

/usr/bin/save_post_legato.sh

36 / 238 3BK 20903 AAAA PCZZA Ed.22


2.3 Perform a RestoreImportant Before you perform a restore, take note of the following:

B9 CD1 and CD3 must be available

Restores are always done off-line

Resynchronization of the system can be necessary to ensuresynchronization between the time of the last backup and the time of the

system failure.This is not part of the restore procedure.

2.3.1 Prerequisites

Before you restore, you must be in Multi User Mode . You must also have:

B9 A1353-RA CD1 and CD3 corresponding with the installed software

version.

For B9 MR4 OMC-R use the B9 MR4 CD1 even if the machine was migratedfrom MR1.

The most recent full backup tape and the most recent correspondingincremental backup tapes.

You must restore the full backup tape(s) first and then the most recentincremental backup tape(s). Otherwise, if you install in the reverse order,nothing prevents the full backup information from overwriting the incrementalbackup, and you have an inconsistent file system.

System Administrator (root) access rights to the A1353-RA

Administrator access rights to the A1353-RA

Note: In the case of an XLarge Configuration, it is necessary to perform the restoreprocedure on each individual machine (Master and Agent) to be restored.

When inserting a tape, be sure that it is positioned at the beginning (it isrewinded).

If the full backup was performed using a set of tapes (on the same machine),start with the first tape.

3BK 20903 AAAA PCZZA Ed.22 37 / 238


2.3.2 Restore Procedure

2.3.2.1 Perform RestoreTo perform a restore:

1. In case of SF V490 with 3510FC Array, perform first Prepare SUN StorEdge3510FC Array (Section 2.4) .

2. Install B9 CD1. Contact Alcatel personnel to do this.

3. After B9 CD1 installation, the following menu is displayed:

1) Insert CD2 and continue with installation

2) Exit to shell in order to get/install the licenses

3) Resume system initialisation

Type [ 3 ] .

4. Wait until the system comes up and log in as root user.

5. If a StorEdge Array 3510 is attached to the machine, perform the followingsteps:

Insert CD1, if not already inserted, and type:cd /cdrom/cdrom0/s0/.install_configcp -pr S77_3510.cd2.* /etc/rc2.d/chmod 0755 /etc/rc2.d/S77_3510.cd2.*

To save time, perform step (7) now.

Check if the RAID initialization is done as root :# scclisccli> sh ld

Verify if the Status is Good and only after that reboot the machine:init 6

Wait until the system comes up and log in as root user.

6. For E4500 systems only , you must reboot the station, if it is notautomatically done:

init 6

Log in as root user.

7. Insert B9 CD3 and copy the restore scripts:cd /var/tmpcp /cdrom/cdrom0/OMC3/OMCGbckup*.gz .cp /cdrom/cdrom0/INDSplmod_*.gz .gzip -cd INDSplmod_*.gz | cpio -icdumDpkgadd -d .

Install the package INDSplmod_<version> .gzip -cd OMCGbckup*.gz | cpio -icdumDpkgadd -d .

Install the package OMCGbckup_<version> .

38 / 238 3BK 20903 AAAA PCZZA Ed.22


8. Search the corresponding device for the root and usr partition:df /usr / | awk ’{print $1 " " $2}’/usr (/dev/md/dsk/ di/ (/dev/md/dsk/ dk

where di is the /usr corresponding device and dk is the root (/ )corresponding device.

Check the usr and root mirrors status:# metastat di dk | grep -i sync

Wait for the end of the root and usr mirrors resynchronization beforecontinuing. In case of disks failure, replace any disks whose state is not ok.

9. To start the restore, load the first tape of the full backup and enter thefollowing command:

/alcatel/omc3/backup/script/MF-improved_restore_OMC.pl-dev= <device>

Where <device> is the tape device on which the backup was made (bydefault /dev/rmt/0cn ).

10. If a set of tapes was used for the backup (on Master), all the tapes mustbe restored.

When the restore of a tape is finished, a pop-up window is displayed:

THIS TAPE IS RESTORED! Please INSERT next tape. Push OK

button! Perform the following:

Push the eject (unload) button of the tape drive (only if the tape isn’t

ejected) and replace the tape.

In the terminal window where the restore script was started press

[ ENTER ] .

In the pop-up window push the [ OK ] button.

11. The system will reboot when the restore is finished. After the restore isfinished on master and the reboot is done, perform also a reboot on eachagent. After this step the fullrestore is finished.

Incremental Restore 12. Search the corresponding device for the root and usr partition:df /usr / | awk ’{print $1 " " $2}’/usr (/dev/md/dsk/ di/ (/dev/md/dsk/ dk

where di is the /usr corresponding device and dk is the root (/ )corresponding device.

Check the usr and root mirrors status:# metastat di dk | grep -i sync

Wait for the end of the root and usr mirrors resynchronization beforecontinuing.

13. Load the tape of the last incremental backup. If you do not have anincremental backup, go to Step (16) .

14. Enter the following command as root to restore the incremental backup:

/alcatel/omc3/backup/script/MF-improved_restore_OMC.sh-dev= <device>

Where <device> is the tape device on which the backup was made (bydefault /dev/rmt/0cn ).

3BK 20903 AAAA PCZZA Ed.22 39 / 238


15. The system will reboot when the restore is finished.

The system is fully restored.

16. From a console, log in as root user.

17. Reboot each HMI, after all backup data is restored:init 6

2.3.2.2 Restart the OMC-RWhen the restore is finished (Master and each Agent in case of Xlarge),restart the OMC-R:

1. Log in as axadmin on the Master Host.

2. Start the OMC-R process by entering the following command from aTerminal window:

sudo /alcatel/omc3/osm/script/MF-start

If the system does not start, contact Alcatel support.

3. Once the system is restarted, resynchronize all workstations. From theA1353-RA Icon Box, select OSM Administration Facilities Main Menu-> Configuration -> Workstation Management -> ResynchronizeWorkstation .

This displays a dialog box.

4. Select all the displayed check boxes and click on [ Apply ] .

This resynchronizes all workstations.

5. Perform the task Discover BSS on each BSC (using BSSUSM).

6. From the RNUSM, check adjacency inconsistencies:

General -> Query Ajacencies InconsistenciesIf the check result is not OK, contact Alcatel support.

2.3.3 Perform a Restore with a Centralized Solution

As root user perform the tasks described below.

1. Type the following command:# init 0

On your screen an ok prompt appears.

2. Perform this step only on E4500 machine.ok> setenv diag-switch? falseok> setenv boot-device diskbrd:bok> reset-all

Wait until the system restarts and press Stop + A simultaneously to getthe ok prompt.

3. In case of SF V490 with 3510FC Array, perform Prepare SUN StorEdge3510FC Array (Section 2.4).

4. Insert the Solaris 10 CD1 CD-ROM in the drive and type the followingcommand:

ok> boot cdrom - install

If the installation from internal CD-ROM drive is not possible (ex. Fatal SCSIerror at script address 8 - Illegal instruction), refer to “B9 A1353-RA PlatformCommissioning - 3BK174224011RJZZA” document, section “Appendix A:CD1 Installation from Network”.

Wait for the OpenWin graphical interface.

40 / 238 3BK 20903 AAAA PCZZA Ed.22


5. Type the following information:

Enter a name for this workstation: type the hostname of the

machine.

Enter an IP address for <hostname>:

Enter the netmask for <hostname>:

Enter default router IP address [just Enter for none]:

6. The System Identification window is displayed, to continue press [ F2 ] .Select your location, date and time:

Continents and Oceans

Countries and Regions

Date and Time

7. The following message appears:Enter WS type (GSM-AGENT GSM-HMI GSM-MASTER GSM-NPA):

Choose the machine type to be installed:

GSM-MASTER for Master Host installation

GSM-AGENT for Agent Host installation

8. Press [ Enter ] to confirm.

9. A summary of the selections is displayed. Type Y to confirm.

After the installation the system reboots automatically.This task takes about:

45 minutes on Sun Fire V880

60 minutes on E4500.

10. If the SOLARIS 10 CD1 was installed from network, skip the next step.

11. The configuration scripts are started automatically.When the system configuration is finished, the following menu is displayed:

1) Insert CD2 and continue with installation

2) Exit to shell in order to get/install the licenses

3) Resume system initialization

Type [ 3 ] and press [ Enter ] .

12. In case of SunFire V490 machine , launch the following commands:cd /cdrom/cdrom0/s0/.install_configcp -pr S77_3510.cd2* /etc/rc2.dinit 6

13. Install on OMC-R the client application of the Centralized Solution.

14. Install the restore scripts from B9 CD3 as root user:cd /cdrom/cdrom0/OMC3cp OMCGbckup* /var/tmpcd /var/tmpgzip -cd OMCGbckup* | cpio -iducd OMCGbckup/reloc/omc3/backup/script

3BK 20903 AAAA PCZZA Ed.22 41 / 238


cp post_restore* pre_restore*/alcatel/omc3/backup/scriptcd /alcatel/omc3/backup/scriptchmod 755 post_restore* pre_restore*

15. Run the following script:./pre_restore_Legato.sh

16. The operator has to use the centralized solution for restoring the information.This centralized solution handles the extraction of useful information from thepreviously obtained back-up. The same centralized solution tool is in chargewith copying the content of partition images into /backup/tmp_mnt_G2and /backup/tmp_mnt_G21 and the distribution of the backed-up filesto their original location.

17. Re-attach the mirrored disks:cd /alcatel/omc3/backup/script./post_restore_Legato.sh

The Master is automatically rebooted.

During the reboot, if there are problems with OSI , type the followingcommand:

# ls -l /devices/pseudo/clone@0:oopiRun mknod command for each nod number previously found:

# mknod oopi0 c <nod0number> 0# mknod oopi1 c <nod1number> 1

18. After the Master finishes booting (the login window appears), in re-configuremode reboot the Agents and then HMIs.

19. Login on the Master as axadmin user.

20. After the Agents finish booting, click on the A1353-RA iconbox on theMaster only to open the OMC-R application.

21. If the following message appears “Warning: Iconbox already running

on this display ” , remove the session files (displayed on the Terminal)from the /alcatel/var/share/nterm directory. The files are hidden andtheir name start with ”.omc3”. In order to see the hidden files too, runthe command “ls -al ”.

22. Start the OMC-R processes:$ sudo /alcatel/omc3/osm/script/MF-start

Check that the sec server is started:$ ps -ef | grep Dsecserver | grep -v grep

23. Follow the steps to open [ DSM ]:$ cd /alcatel/omc3/dsm/script/$ ./run_dsmusm

24. In the [ DSM ] main window, check the color of the processes. The processescan have one of the following colors:

green color if all is OK

yellow color when the process is charging.Wait for the green color of the process.

red color if problems occur.

42 / 238 3BK 20903 AAAA PCZZA Ed.22


If some OMC-R processes stay in red color call Alcatel supportlevel 2. Do not continue before solving these problems.

Note: In Follow-up window, if one or more BSS have problems, start a new discoveraction on it.

3BK 20903 AAAA PCZZA Ed.22 43 / 238


2.4 Prepare SUN StorEdge 3510FC ArrayIn case of using SF V490 with Sun StorEdge 3510FC Array, before startingCD1 installation the following preparation is needed.

A serial connection to the 3510FC Array must be used . For this you need aserial cable and a machine with a serial port. The machine can be a PC withWindows or a station with Solaris.

1. Connect the serial port COM1 of the first controller to the serial port ofyour station.

Set up the serial connection to the Sun StorEdge 3510FC Array:

from Solaris :# tip -38400 /dev/term/aconnected

Press [ Control ] + [ L ] simultaneously. Press [ ESC ] for all the receivednotification messages.From the terminal connection menu select: Terminal (VT100) Mode .

from Windows :

Create a new HyperTerminal connection with the following parameters:

Use: COM1

Bits per second: 38400

Data bits: 8

Parity: none

Stop bits: 1

Flow control: Hardware

2. From the < Main Menu > follow the menus: Configuration parameters ->Host-side Parameters -> Fiber Connection Option and select Loop only .

The following message appears: Set Fiber Channel connection

option?

Select NO

The following message appears: Change made to these settings

will NOT take effect until the controller is RESET. Prior

to resetting the controller, operation may not proceed

normally. Do you want to reset the controller now?

Select NO.

3. From the < Main Menu > follow the menus: Configuration parameters-> Host-side Parameters -> Peripheral Device Type Parameters ->Peripheral Device Type and select Enclosure Services Device

(Type=0xd)

The following message appears: Set peripheral device type?

Select default value (No)

4. From the < Main Menu > select view and edit Host luns .

A list with the host channels is displayed (host channel example: CHL 0ID 40 Primary Controller).

5. For each host channel perform the following actions.

To select a host channel, press [ Enter ] on it (do not select "Edit Host-ID").

44 / 238 3BK 20903 AAAA PCZZA Ed.22


If a selection box is displayed, there is no logical drive mapped on thischannel. Press [ ESC ] to go back to the host channels list.

If a list with mapped LUNs is displayed, there are logical drives mapped onthis channel.

Make sure that there is only one host channel and this host channelhas only one LUN mapped on it.

All LUNs except this one LUN must be deleted. To delete a LUN, press[ Enter ] on it and select [ Yes ] from the confirmation box. Press [ ESC ] togo back to the host channels list.

3BK 20903 AAAA PCZZA Ed.22 45 / 238


6. When the LUN deleting is finished, press [ ESC ] to go back to the < MainMenu > .

Select system Functions , after select Reset controller and confirmwith [ Yes ] .

Wait for the terminal connection menu.

Close the terminal.

46 / 238 3BK 20903 AAAA PCZZA Ed.22

3 Access Rights Management


Access rights management covers:

Password Policy

User Management

OAD Management.

Operator/Terminal Profile Management

FAD Management

FTP Users

3BK 20903 AAAA PCZZA Ed.22 47 / 238


3.1 IntroductionThe access rights management service is provided to allow the managementof UNIX users. It provides graphical interfaces which encapsulate the basicUNIX commands relative to user management. New users can be added, userprofiles can be modified and users can be deleted. All users are added tothe OMC-R group.

User accounts should only be modified from OSM. Otherwise, if you change itfrom UNIX you create an inconsistency between OSM and UNIX.

It is possible to associate an object/group of objects to a FAD/ApplicationFunction(s) inside a profile. For examples a user may have administration rightson some objects and supervision rights only, on other objects.

3.2 Password PolicyThe Password Policy is a set of rules used for checking the users passwords.

3.2.1 Default Password Rules

The administrator has to reset the user password when the user passwordis locked.

If a user password expires, the message is "login incorrect" (in CDE). The

same message is displayed in the CDE window, regardless of whether theentered password is incorrect, or the password for that user is expired.

The administrator can have a global view of the user passwords - locked

or unlocked, by using the /alcatel/omc3/bin/unlockaccount script(used as root user).

3.2.1.1 CompositionPassword composition rules are customizable. The following table showsthe default password composition:

Parameter Default Value Description

MIN_LENGTH (*) 6 Minimum password length

MAX_LENGTH 16 Maximum password length

NB_LETTERS 1 Minimum number of letters in user password

NB_NUMBERS 1 Minimum number of digits in user password

NB_CAPITALS 1 Minimum number of uppercase characters in userpassword

NB_SPECIAL_CHARS 1 Minimum number of special characters (see below) inuser password

MAX_DAYS (*) 90 Number of days before password expires

WARNING_DAYS (*) 8 Number of days warning before password expires

48 / 238 3BK 20903 AAAA PCZZA Ed.22


(*) : used from LDAP password policy

Table 3: Password Composition Rules Description

The default special character list is:

$[]{}()*+?^&=-‘!@%_~,:;’.<>|\/"

3BK 20903 AAAA PCZZA Ed.22 49 / 238


3.2.1.2 System Password RejectionThe main reasons the system rejects a password are:

New password is same as one of the previous five passwords

New password contains four or more letters that are similar to the old

password

Password is made of identical, ascending or descending characters

Password does not contain a minimum of one special sign and one number

Three erroneous attempts to log on have been made

Password has expired. See 90 Day Validity below.

3.2.1.3 90 Day ValidityA password is only valid for 90 days. For the eight days before the expiration,the system reminds you to change your password.

50 / 238 3BK 20903 AAAA PCZZA Ed.22


3.2.2 Create New Password Policy

To create a new password policy:

1. From [ OSM ] follow the menupath: Administration -> Password PolicyManagement -> Add Password Policy

2. Fill in the fields:

’Policy Name’

’Description’ (this field is optional)

’Check Syntax’ (on/off)Indicates whether the password syntax will be checked before thepassword is saved. The password syntax checking mechanism checksthat the password meets the password minimum length requirement andthat the string does not contain any "trivial" words (such as the user’sname any attribute value stored in the user’s directory entry).

’Password minimum length’

’Password Change’ (on/off)If on is selected, the user can change own password

’Allow password changes in’ give the number of days

’Passwords in History’ number of last passwords to keep in history

’Password Expire’ (on/off)

’Password expire after’ the give the number of days

’Send warning’ give the number of daysBefore the password expires, a warning message is send to the user.

’Expire regardless of warning’ (on/off)

on : the password will expire on the original date even if the user didnot receive the warning

off : the expiration can be extended to allow a full warning periodafter the warning is sent

’Account may be lockout’ (on/off)If on is selected, the account will be locked after a given number offailures.

’Lock account after’ give number of login failures

’Reset failure count after’ give number of minutes

’Password Unlock’ (on/off)

on : after the lockout duration, the account is unlocked automatically

off : the account can be unlocked by the administrator, resetting

the password

’Lockout duration’ give the number of minutes to lock the account

3. Click on [ Add ] and after on [ Confirm ] button.

3BK 20903 AAAA PCZZA Ed.22 51 / 238


3.2.3 Modify a Password Policy

To modify a password policy:

1. From [ OSM ] follow the menupath: Administration -> Password PolicyManagement -> Edit Password Policy

2. Select the password policy to be modified from the displayed list. Clickon [ Edit ] button.

3. Update the fields:

’Check Syntax’ (on/off)Indicates whether the password syntax will be checked before thepassword is saved. The password syntax checking mechanism checksthat the password meets the password minimum length requirement andthat the string does not contain any "trivial" words (such as the user’sname any attribute value stored in the user’s directory entry).

’Password minimum length’

’Password Change’ (on/off)If on is selected, the user can change own password

’Allow password changes in’ give the number of days

’Passwords in History’ number of last passwords to keep in history

’Password Expire’ (on/off)

’Password expire after’ the give the number of days

’Send warning’ give the number of daysBefore the password expires, a warning message is send to the user.

’Expire regardless of warning’ (on/off)

on : the password will expire on the original date even if the user didnot receive the warning

off : the expiration can be extended to allow a full warning periodafter the warning is sent

’Account may be lockout’ (on/off)If on is selected, the account will be locked after a given numberof login failures.

’Lock account after’ give number of login failures

’Reset failure count after’ give number of minutes

’Password Unlock’ (on/off)

on : after the lockout duration, the account is unlocked automatically

off : the account can be unlocked by the administrator, resetting

the password

’Lockout duration’ give the number of minutes to lock the account

4. Click on [ Confirm ] button.

52 / 238 3BK 20903 AAAA PCZZA Ed.22


3.2.4 Delete Password Policy

To delete a password policy:

1. From [ OSM ] follow the menupath: Administration -> Password PolicyManagement -> Delete Password Policy

2. Select the password policy to be deleted, from the displayed list. Click on[ Delete ] and after on [ Confirm ] button.

3.2.5 List Password Policy

To display a password policy:

1. From [ OSM ] follow the menupath: Administration -> Password PolicyManagement -> List Password Policy

2. Select the password policy from the displayed list. Click on [ Details ] button.

3.2.6 Display Global Password Policy

This is the default password policy assigned to an user.

From [ OSM ] follow the menupath: Administration -> Password PolicyManagement -> Display Global Password Policy

3BK 20903 AAAA PCZZA Ed.22 53 / 238


3.3 User ManagementUser management includes the following tasks:

Add Users (Section 3.3.1)

Reset User Passwords (Section 3.3.2)

Delete Users (Section 3.3.3)

List Users (Section 3.3.4)

Display Current Users (Section 3.3.5)

Display Login Failures (Section 3.3.6)

Display Last Logins (Section 3.3.7)

Change Own Password (Section 3.3.8)

Unlock axadmin Account - Wrong Password (Section 3.3.11) .

3.3.1 Add Users

There are two ways to add a user. You can add a new user then assign him/hera profile immediately, or you can create a series of users and then assign alltheir profiles afterwards. The results are the same.

Note: The password minimum length must be equal to the MIN_LENGTH parameterdefault value and its maximum length must be equal to the MAX_LENGTHparameter default value (letters, numbers, and special characters included).See Table 3 . Other Password Rules do not apply when adding new users.

The user name is case insensitive and cannot contain the - special character.Replace it with the _ special character.

54 / 238 3BK 20903 AAAA PCZZA Ed.22


Procedure To add new users:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> Add User .Enter the following information:

’Login name’

’UID’ (user identification field is optional)

’Comment’ (optional)

’Passwd’ enter a password for the new user

’Confirm passwd’ enter again the password

2. Click on [ Add ] . The screen displays the new user’s details and asks you to[ Confirm ] or [ Cancel ] the addition.

3. If you are sure the details are correct, click on [ Confirm ] . If you aresuccessful, the following messages appear:

Successful creation of the user: ’username’

If you do not enter the same password in both fields, the system displays thefollowing message:

The two passwords don’t match

If you do not want to add the new user, click on [ Cancel ] to return to theAdd User screen.

4. By default, the new user does not yet have an Operator Profile. One must beassigned (refer to Assign Operator Profiles (Section 3.8.6) ).

3BK 20903 AAAA PCZZA Ed.22 55 / 238


3.3.2 Reset User Passwords

The Reset User Password function allows the administrator to change a user’spassword. For example, this may be necessary if a user cannot remembertheir password, if an existing username is allocated to a different person, orthe user (except axadmin) has locked his account.

If the axadmin user has locked his account refer to Unlock axadmin Account -Wrong Password (Section 3.3.11) .

When the user password has expired, the administrator has to reset the userpassword.

Note: The password must be a minimum of one and a maximum of eight characters inlength (letters, numbers, and special characters included). Other PasswordRules do not apply when re-setting user passwords.

Procedure To reset a user’s password:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> Reset User Password .

2. Click on [ Login name ] to view a list of users.

3. Click on the appropriate user.

4. Enter the new password in the ’New password’ field.

5. Enter the new password in the ’Confirm new password’ field.

6. Click on [ Change password ] . The following messages appear if thereset is successful:

Successful change of password for ’username’

If you do not enter the same password in both fields, the system displays thefollowing message:


7. The [ Sync/Restart http server ] function is automatically performed and thenew passwords now take effect.

56 / 238 3BK 20903 AAAA PCZZA Ed.22


3.3.3 Delete Users

Never delete the following users:

axadmin

metrica.A connected user can not be deleted.

Procedure To delete an existing user:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> Delete User .

A list of all users is shown with a checkbox against each user. The listincludes the user’s Login name, Group and Comment information, theirlocation and information on whether they are connected or not.

2. Click on the checkbox next to the details of the user you want to delete.

3. The screen displays the selected user’s details and asks you to [ Confirm ]or [ Cancel ] the deletion.

4. If you are sure the details are correct, click on [ Confirm ] . If the deletionis successful, the following message appears:

Delete Sec operator ’username’. Successful deletionof user ’username’

If you have selected a user who is currently connected, you receive thefollowing error message:

[Login name] is undeletable.

If the details are not correct and you do not want to remove the selecteduser(s), click on [ Cancel ] to return to the Delete User screen.

5. The deleted user automatically disappears from the SEC Operators list. Goto the SECUSM : Browser window and ensure that the deleted user’s nameno longer appears on the Operators list (refer to List Users (Section 3.3.4) ).If the name is still shown in the list, repeat steps 1 to 4 of this procedure.

3.3.4 List Users

To view a list of all users:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> List Of Users .

This displays a list of all users, and includes the Login name, Groupand Comment information for each user. It also displays the amount ofmegabytes used by the user, whether they are currently connected or not,where they are and when they last connected to the system.

2. A list of all users can also be viewed from the SECUSM : Browser window.Open the SECUSM: Browser window and select Operator to look at theoperators list.

Note: If a user is logged in at more than one station, his name appears more thanonce on the list.

3BK 20903 AAAA PCZZA Ed.22 57 / 238


3.3.5 Display Current Users

To view a list of users currently logged in to the system:

From the OSM Administration Facilities Main Menu, select Administration ->User Management -> Current Users .

This displays a list of users who are currently logged in to the system. Itincludes the Login name of each user, the date they logged in and their location.

Note: If a user is logged in at more than one station, his name appears more thanonce on the list.

3.3.6 Display Login Failures

This feature is used to improve the security of the system. For example, it canbe used to see if someone has attempted to gain unauthorized access to thesystem or if they have tried to access your login. A user only appears on the listafter three successive login attempts have failed. All three failed login attemptsare listed. The user is locked out after three attempts.

To view a list of users who have failed to login successfully:

From the OSM Administration Facilities Main Menu, select Administration ->User Management -> Login Failures .

This displays a list of users who have failed to login to the system. The tableshows the Host name, the Login name of each user, and the date they failed tologin on.

3.3.7 Display Last Logins

To view a list of last logins:

From the OSM Administration Facilities Main Menu, select Administration ->User Management -> Last Logins .

This displays a list of users who are currently or who have recently loggedon to the system. It includes the Login name of each user, the date theylogged in, and their location. If also includes the time they logged in and off,or if they are still logged in.

58 / 238 3BK 20903 AAAA PCZZA Ed.22


3.3.8 Change Own Password

Only use OSM to change your UNIX password. Otherwise, if you change itfrom UNIX you create a inconsistency between OSM and UNIX.The user can change the own password only if the assigned password policyhas the Password Change set to on . For more details refer to PasswordPolicy (Section 3.2) .

Procedure To change your own UNIX password:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> Change Own Password .

2. Check that the Login name is correct.

Note: For security reasons, you are strongly advised not to use an obvious passwordwhich might be easily guessed by another person. Obvious passwords mightinclude your family name or your first name.

3. Enter the old password in ’Old password’ field.

4. Enter the new password in the ’New password’ field.

5. Enter the new password in the ’Confirm new password’ field.

6. Click on [ Change password ] . A message appears which tells you whetherthe change was successful or not. If you do not enter the same password inboth fields, the system displays the following message:


3.3.9 Assign Password Policy

By default each created user has assigned the "Global password policy".

To assign password policy to an user:

1. From [ OSM ] follow the menupath: Administration -> User Management-> Assign Password Policy

2. Select the user(s).

3. Select another password policy from the New Password Policy list.

4. Click on [ Assign ]

5. Click on [ Confirm ] button.

This will change the password policy for the selected user(s).

3.3.10 Remove Password Policy

To remove a defined password policy from an user:

1. From [ OSM ] follow the menupath: Administration -> User Management-> Unassign Password Policy

2. Select the user(s).

3. Click on [ Remove ]

4. Click on [ Confirm ] button

This will assign the "Global password policy" for the selected user(s).

3BK 20903 AAAA PCZZA Ed.22 59 / 238


3.3.11 Unlock axadmin Account - Wrong Password

The axadmin account is locked by typing a wrong password 3 (default value)times in a row.

To unlock axadmin account perform as root the following:

1. Open a Terminal display from the CDE desktop option.

2. At the UNIX prompt, enter:/alcatel/omc3/bin/unlockaccount -l axadmin

60 / 238 3BK 20903 AAAA PCZZA Ed.22


3.4 OMC-R Application FunctionsThe OMC Applications functions are grouped on the applications they areserving. Apart from Applications Functions to be assigned, there are alsoobject access to be allowed.

3.4.1 BSSUSM Functions

BSSUSM.Inhibit_OAD_control inhibits OAD controlAll objects available can be reached (but only in the frame of BSSUSMapplication)

BSSUSM.Navigate_to_RNL allows navigation to RNUSM (Navigate to

Browser option) from a cellThis is possible from Functional Navigator tree if there are cells definedon sectors

BSSUSM.Manage_performance access to Performance menu allowedBoth PMC and ODMC can be managed.

BSSUSM.Navigate_to_MFS allows navigation to MFSUSM only if BSS

is associated with a MFSAter view, only from Ater mux connections which are linked to MFS.

BSSUSM.Navigate_to_performance allows navigation to NPA Counters

(Show Counters option) from a board (Equipment Navigator tree), and froma function, from RSL, OML and N7 popup menu (Functional Navigator tree)

BSSUSM.Manage_indicator allows navigation to NPA Indicators (Show

Indicators option) from a board (Equipment Navigator tree), and from afunction, from RSL, OML and N7 popup menu (Functional Navigator tree)

BSSUSM.Navigate_to_alarm navigation to alarm is allowedBut for completing the task, an operator’s profile should include at leastAsCurrentUsm.startable function. Also access to targeted object should beallowed. Otherwise an empty list will be shown, with no alarm inside!

BSSUSM.Manage_trace trace menu enabled

BSSUSM.Configure_PMC allows to check the PMC actually running on BSS.

BSSUSM.Configure_ODMC allows to create new ODMC

BSSUSM.Start allows to start BSSUSM application

BSSUSM.Manage_alerter allows to manage alerters (view and configure)

BSSUSM.Supervise_function

BTS popup menu

display BSC Related Equipment

display BTS Related equipment from RSL

OML and N7 popup menu

display Related Board from function popup and ACH Synthesis optionfrom ACH popup menu

3BK 20903 AAAA PCZZA Ed.22 61 / 238


BSSUSM.Supervise_action allows other functions to work:

Discover BSS: Discover_BSS function also need it for this

Hardware Audit on BSS, BTS: Hardware_Audit function need it

State Audit on BSS: Alarm_state_audit function need

all board action: Lock, Unlock, Reset, Restart, Test, Verify, Shutdown

Reset, Restart BSS/BTS

Lock, Unlock BTS

Lock, Unlock, Shutdown on RSL and N7

RSL Remapping on TSU/BSC: Map_RSL function need

Create Abis, Paste Abis, Modify Abis Chain/Ring, Delete Abis

Chain/Ring, Defragment Abis Chain/Ring, Display TS Allocation, Modify

BTS HW Capabilities, Modify BTS Characteristics, Delete BTS, Cut BTS,Copy BTS, Create BTS, Detach Secondary Abis, Fill Up Primary Abis,

Go To Other Abis: Configure_hw_ext_red need it for all his operationto be allowed

Upload Transmission Configuration

Allow/Inhibit Alarm Reporting on Tp Up, Allow/Inhibit alarm Reportingon Tp Down from a A Tp

Lock, Unlock, Shutdown, Allow/Inhibit Alarm reporting on BSC side and

Allow/Inhibit Alarm Reporting on TC side on a Ater TP

Lock all Ater TPs, Unlock all Ater TPs, Shutdown all Ater TPs,

Inhibit/Allow Alarm Reporting an All A TPs on a AterMux Connection TP

BSSUSM.Supervise_hardware enables Report option on BSS, report fromBSC and BTS (pop-up window in Equipment Navigator tree)

BSSUSM.Navigate_to_RI navigation to RI allowed

BSSUSM.Manage_software access to Software Management menu andfile Export allowed

BSSUSM.Discover_BSS allows discover BSS feature, BSC Trace Audit

and Display Differential Report only if Supervise_action is included in theuser’s profile

BSSUSM.Alarm_state_audit Alarm state audit allowed only if

Supervise_action is included in the user’s profile

BSSUSM.Open_close_A_channel_loop enables Open Loop and Close

Loop buttons from Achannel Panel

BSSUSM.Manage_USDallows access to USD menu only if Supervise_actionis included in the user’s profile

BSSUSM.Manage_BSC_file access to BSS File Management allowed

BSSUSM.Hardware_audit hardware audit allowed only if Supervise_action

is included in the user’s profile

BSSUSM.Map_RSLRSL Remapping allowed only if Supervise_action is

included in the user’s profile

62 / 238 3BK 20903 AAAA PCZZA Ed.22


BSSUSM.Configure_BSS_parameters allows access to BSS parametersmenu and access to Ater Parameters value

BSSUSM.Configure_transmission not used

BSSUSM.Configure_BTS_file access to transmission configuration filesmanagement menu allowed

BSSUSM.Configure_hw_ext_red allows to add chain/ring or BTSs only if

Supervise_action is included in the user’s profile

BSSUSM.Inhibit_FAD_control inhibits FAD control. All functions available

in this application can be used.

BSSUSM.newly not used

BSSUSM.WildCardSECFunction all functions and objects availableAll functions, all objects are reachable in the limit of MFSUSM application.This function added in the profile, allows complete access inside MFSUSMapplication.

3.4.2 MFSUSM Functions

MFSUSM.Configure_alarm_reporting alarm reporting function can be

allowed or inhibited.

MFSUSM.Configure_link_connection link connections

can be re-configured. This is possible only ifMFSUSM.Display_link_connection_configuration also

belongs to the operator’s profile.

MFSUSM.Check_gb check gb function is allowed

MFSUSM.Align_global align global function is allowed

MFSUSM.Navigate_to_BSS allows navigation to BSSUSM if operator’s

profile includes BSSUSM.start functionAccess to targeted object should be allowed, at least in the frame ofBSSUSM application.

MFSUSM.Navigate_to_RNL not used

MFSUSM.Navigate_to_performance allows to directly check thecounters/indicators values (for Gb interfaces only) available through PM

Browser.This service is accessible only if MFSUSM.Display_gb_configuration isdefined in the user’s profile.

MFSUSM.Navigate_to_alarm allows navigation facilities to alarm ifoperator’s profile includes AsCurrentUsm_Start function.Also access to targeted object should be allowed. Otherwise an empty listwill be shown, with no alarm inside!

MFSUSM.Start allows to start MFSUSM application

MFSUSM.Display_gb_configuration display gb configuration allowed.No modification on gb configuration possible.

MFSUSM.Check_GPU_BSS_allocation Check GPU BSS allocation

3BK 20903 AAAA PCZZA Ed.22 63 / 238


MFSUSM.Check_links check links function allowed

MFSUSM.Display_atermux_configuration display atermux configuration

function allowed

MFSUSM.Check_global check global function allowed

MFSUSM.Check_atermux allows access to checks GPRS Configuration

MFSUSM.Display_link_connection_configuration link connections

can be viewedNo modification function permitted.

MFSUSM.Supervise_gb enables Lock/Unlock NSVC links from GB

Configuration windowThe MFSUSM.Display_gb_configuration function must be in the user’sprofile. Otherwise access to menu is impossible.

MFSUSM.Lock_unlock_GSL lock/unlock GSL function allowed.This menu isactive only on TP supporting GSL.

MFSUSM.Inhibit_OAD_control inhibits OAD control. All objects available

can be reached (but only in the frame of MFSUSM application)

MFSUSM.Configure_radio rershuffle option from Configure menu, TPpopup menu and from GPU popup

MFSUSM.Align_ater allows access to menu Align -> GPRS Configuration ->align all TP/selected TP

MFSUSM.Configure_gb modification of gb configuration allowedFor having access to gb interface, MFSUSM.Display_gb_configurationfunction must be included in operator’s profile as well.

MFSUSM.Align_links align links function allowed

MFSUSM.Configure_ater allows to modify GPRS configuration (OK button

becomes active)

MFSUSM.NavigateToMrtg allows to navigate to MRTG

MFSUSM.Inhibit_FAD_control inhibits FAD controlAll functions available in this application can be used.

MFSUSM.Navigate_to_equipment not used

MFSUSM.Navigate_to_IMT allows to navigate to IMT, in the context of B8

release onlyNo relevance in the context of B9 release. So, even if this function is attachedto a user’s profile, he will have no supplementary rights due to this action.

MFSUSM.Navigate_to_IMT_GPU allows to navigate to IMT with limited rights

MFSUSM.Navigate_to_IMT_MFS allows to navigate to IMT with full accessrights

MFSUSM.WildCardSECFunction all functions and objects availableAll functions, all objects are reachable in the limit of MFSUSM application.This function added in the profile, allows complete access inside MFSUSMapplication.

64 / 238 3BK 20903 AAAA PCZZA Ed.22


3.4.3 RNUSM Functions

RNUSM.Inhibit_OAD_control inhibits OAD control. All objects available

can be reached (in the frame of RNUSM application).

RNUSM.Navigate_to_alarm allows navigation facilities to alarmAlso access to targeted object should be allowed. Otherwise an empty listwill be shown, with no alarm inside!

RNUSM.Force_configuration allows to call force configuration on BSCor cells.

RNUSM.Navigate_to_equipment enables Show equipment function ifoperator’s profile includes BSSUSM.start /MFSUSM.start functionAlso access to targeted object should be allowed, at least in the frame ofBSSUSM/MFSUSM application.

RNUSM.Export export/import functions allowed

RNUSM.Bar_object bar/debar function allowed

RNUSM.Activate_SMSCB activate/deactivate_SMSCB function allowed

RNUSM.Navigate_to_IMT_GPU allows to navigate to IMT, limited actionspermitted

RNUSM.Navigate_to_IMT_MFS allows to navigate to IMT, full range of

actions permitted

RNUSM.Lock_object lock/unlock action allowed

RNUSM.prc_restricted_access access to restricted PRC allowed

RNUSM.Activate_MLU the following actions are enabled:

from SC MLU menu:Download, Preload, Abort, Activate MFSs, Accept, Reject, Close MLUSession for MFSs and Close whole MLU session

from PRC MLU menuCheck All, Check Parameters, Check With Hardware, Check TelecomImpact and Apply MLU Session

RNUSM.Activate_PRC activate PRC action allowed and "Activate" option

from Cell Popup menu with the options: "With forcing cell administrativestate" and "Without forcing cell administrative state".

RNUSM.Modify_object if included in user’s profile, cells and BSS

parameters may be modifiedOtherwise these parameters can be shown only.

RNUSM.Manage_PRCallows to manage a PRC: create, open, close and delete

RNUSM.NodeId_export allows to export Node IdentifiersTo be usable, the user’s profile must include RNUSM.Export function.

RNUSM.NodeId_import allows to import Node IdentifiersTo be usable, the user’s profile must include RNUSM.Export function.

3BK 20903 AAAA PCZZA Ed.22 65 / 238


RNUSM.Navigate_to_performance

allows to check directly the counters/indicators values available throughPM Browser:

Show Counters and Indicators from BSC and Cell popup menu

Show Counters Type 110 on Cell popup menu

RNUSM.Start allows to start RNUSM application

RNUSM.Geographical_localization not used

RNUSM.Commercial_usage allows operator to act upon Commercial usage:

start/stop

RNUSM.Inhibit_FAD_control inhibits FAD control, all functions available in

this application can be used

RNUSM.Configure_MFS

allows access to several GPRS functions:

lock/unlock GPRS

download to MFS

select Cells from NSEI

show LCS NSEI

show GPRS NSEI

resynchronize GPRS

resynchronize MFS

reinitialize GPRS

RNUSM.Logical_audit logical audit function allowed

RNUSM.WildCardSECFunction All functions, all objects are reachable in

the limit of RNUSM application. This function added in the profile, allowscomplete access inside RNUSM application.

3.4.4 OAM Functions

OAM.Inhibit_OAD_control inhibits OAD control, all available objects canbe reached (in the frame of OAM application)

OAM.NavigateToMrtg allows navigation to MRTG window (if collector

enabled)

OAM.ConfigureMrtg allows to enable/disable collector

OAM.Navigate_to_equipment navigation to equipment (MFS/BSS) allowed.

But, access to impacted object should be allowed.

OAM.Declare_BSS BSS declaration allowed

OAM.Start allows the operator to start OAM ApplicationOnly functionalities linked with graphical interface are available. Anynavigation capabilities are forbidden.

OAM.Shutdown_access_point not used

66 / 238 3BK 20903 AAAA PCZZA Ed.22


OAM.Lock_unlock_access_point not used

OAM.Modify_peer_entities allows peer-entities modificationProvides possibility to modify X.25 parameters both on OMC and BSC side.

OAM.Synchronise_date_time allows date/time synchronization fromFunction Menu

OAM.Start_MFS_Supervision Start/Stop MFS_Supervision

OAM.Start_BSS_Supervision not used

OAM.Inhibit_FAD_control inhibits FAD control, all available functionscan be used

OAM.Modify_BSS_MFS allows to modify BSS/MFS characteristics

OAM.Switch_OMC allows to switch OMC (Primary/Secondary) from Functionmenu

OAM.Declare_MFS allows to declare MFS

OAM.Remove_BSS_MFSallows to remove BSS/MFS

OAM.Navigate_to_IMT_MFS allows to navigate to IMT with full access rights

OAM.WildCardSECFunction All functions, all objects are reachable in thelimit of OAM application. This function added in the profile, allows complete

access inside OAM application.

3BK 20903 AAAA PCZZA Ed.22 67 / 238


3.4.5 AS CurrentUSM Functions

AsCurrentUsm.ModifyFilters allows the operator to update or remove

filters, aging, triggers and sorts (the buttons save/remove are activatedonly if this right is given)

AsCurrentUsm.AcknowledgeAlarm allows the operator to perform alarm

acknowledgements

AsCurrentUsm.InhibitFadControl allows the operator to run a SEC-safe

instance of AS current USM without performing any FAD access controlThis function ensures access to any function. No object access included.

AsCurrentUsm.InhibitSecurity allows the operator to run a SEC-safe

instance of AS current USM without performing any access controlThe instance of the USM runs for this operator as if it were not configuredwith SEC.

AsCurrentUsm.NavigateToPnm not used

AsCurrentUsm.SetAlarmUserNote allows the operator to modify alarmassociated user note

AsCurrentUsm.NavigateToHistoricalUsm allows the operator to

run the AS historical USM directly from the AS current USM (onlytogether with and with AsCurrentUsm.HistoricalUsmStartable and

AsHistoricalUsm.HistoricalUsmStartable )

AsCurrentUsm.ReserveAlarm allows the operator to (un)reserve an alarmselection

AsCurrentUsm.AssignAlarmToUser allows the operator to assign to achosen user an alarm selection

AsCurrentUsm.SetCurimAdministration allows the operator to set the

C.A.L. associated parameters (size, overflows, auto-operation filters, etc...)known at the AS current IM level and is also used to control accessibility

to Trigger and Aging submenus

AsCurrentUsm.ClearAlarmManually allows the operator to manuallyclear an alarm selection

AsCurrentUsm.NavigateToExternal allows the operator to send a selected

alarm to an external application and then, to run this external application

AsCurrentUsm.MakeSynchronization allows the operator to resynchronize

the AS current IM with all its Agents

AsCurrentUsm.Start allows the operator to see the AS Current Alarmbox in Icon BoxThis does not allows starting the application. For this,AsCurrentUsm.CurrentUsmStartable is required.

AsCurrentUsm.ExportAlarmInformation allows the operator to export

alarm selection to an ASCII file or a printer

68 / 238 3BK 20903 AAAA PCZZA Ed.22


AsCurrentUsm.ArchiveAlarmManually allows the operator to archive analarm selection on purposeThe selected alarms will not be accessible though the AS current USM anymore, but will be visible through the historical USM.

AsCurrentUsm.GetMoreAlarmInformation allows the operator to request

more information on alarm selection

AsCurrentUsm.CurrentUsmStartable allows the operator to run the

Current USMThis function only permits the application to run. Any user who need to runthis application, must include this function in the profile.

AsCurrentUsm.RestrictedUnreserveAlarm prevent the operator to

unreserve alarms not belonging to him

AsCurrentUsm.RequestTroubleTicketCreation allows the operator to

request from ARS, on alarm selection, the creation of trouble tickets

AsCurrentUsm.HistoricalUsmStartable this function allows to callAsHistoricalUsm (only together with AsCurrentUsm.NavigateToHistorical

and with AsHistoricalUsm.HistoricalUsmStartable )

AsCurrentUsm.InhibitOadControl allows the operator to run a SEC-safeinstance of AS current USM without performing any OAD access control (in

the frame of AsCurrentUsm application)

AsCurrentUsm.WildCardSECFunction all functions, all objects arereachable in the limit of AsCurrentUsm applicationThis function added in the profile, allows complete access insideAsCurrentUsm application.

3.4.6 AS HistoricalUSM Functions

AsHistoricalUsm.InhibitOadControl allows the operator to run a

SEC-safe instance of AS historical USM without performing any OADaccess control

AsHistoricalUsm.BrowsePublicArchive allows the operator to retrievealarms from the public archive

AsHistoricalUsm.NavigateToCurrentUsm allows the operator to run the

AS current USM directly from the AS historical USM

AsHistoricalUsm.NavigateToExternal allows the operator to send aselected alarm to an external application and then, to run this external

application

AsHistoricalUsm.HistoricalUsmStartable allows the operator to run

the Historical USM

AsHistoricalUsm.Start the user can see the [ AS: Histo Alarms ] iconin the iconbox

AsHistoricalUsm.CurrentUsmStartable not used

3BK 20903 AAAA PCZZA Ed.22 69 / 238


AsHistoricalUsm.GetMoreAlarmInformation allows the operator torequest more information on alarm selection

AsHistoricalUsm.ExportAlarmInformation allows the operator to exportalarm selection to an ASCII file or a printer

AsHistoricalUsm.ModifyFilters allows the operator to update or remove

filters, agings, triggers and sorts (the buttons save/remove are activatedonly if this right is given)

AsHistoricalUsm.NavigateToElm not used

AsHistoricalUsm.BrowseHistoricalAlarmLog not used

AsHistoricalUsm.InhibitFadControl allows the operator to run aSEC-safe instance of AS historical USM without performing any FAD

access control

AsHistoricalUsm.InhibitSecurity allows the operator to run a SEC-safeinstance of AS historical USM without performing any access controlThe instance of the USM runs for this operator as if it were not configuredwith SEC.

AsHistoricalUsm.WildCardSECFunction all functions, all objects are

reachable in the limit of AsHistoricaUsm applicationThis function added in the profile, allows complete access insideAsHistoricaUsm application.

3.4.7 IMT Functions

There are 2 groups of IMT functions:

IMT_GPU are related with Navigation_to_IMT for GPU managementNavigation to IMT for GPU management provides access to a limited set offunctionalities. Up to 8 instances for this navigation are available.

IMT_MFS are related with Navigation_to_IMT for MFS managementNavigation to IMT for MFS management provides access to a complete setof functions. Only one instance is available in this case.

IMT_GPU functions:

IMT_GPU.MFS_read MFS related parameters visible from IMT_GPU can beread

IMT_GPU.GPU_write some GPU related parameters visible from IMT_GPU

can be modified

IMT_GPU.Start IMT_GPU application can be started

IMT_GPU.WildCardSECFunction all Functions in this applications are

available

70 / 238 3BK 20903 AAAA PCZZA Ed.22


IMT_MFS functions:

IMT_MFS.MFS_read MFS related parameters visible from IMT_GPU can be

read

IMT_MFS.GPU_write some GPU related parameters visible from IMT_MFScan be modified

IMT_MFS.MFS_write some MFS related parameters visible from IMT_MFS

can be modified

IMT_MFS.MFS_admin administration related parameters are available

IMT_MFS.MFS_platform MFS_Platform related parameters are available

IMT_MFS.Start IMT_MFS application can be started

IMT_MFS.WildCardSECFunction all Functions in this applications areavailable

3.4.8 SEC Functions

These functions are dedicated to security only. They are not of specific interestfor NE managing. By using them a control over the OMCR users is performed.All SEC related functions are gathered in one FAD: CustomSecUsmFADOMC3.

Axadmin user only can see/manage these functions. Even mighty users (userwho can take benefits of the new FAD editor feature) are not even able tosee/manage the content of any FAD/Profile which include these functions.

There is a rule to be respected in managing these functions: FAD/profile shouldinclude exclusively SEC functions.

3.4.9 Other Functions

DSMUSM functions:

DSMUSM.Start allows operator to access DSMUSM

DSMUSM.WildCardSECFunction no extra feature added face to previousfunction

ENSUSM functions:

ENSUSM.Start allows operator to access ENSUSM

ENSUSM.WildCardSECFunction no extra feature added face to previousfunction

FULL_MRT functions:

FULL_MRT.Start allows operator to access FULL_MRT

FULL_MRT.WildCardSECFunction no extra feature added face to previous

function

3BK 20903 AAAA PCZZA Ed.22 71 / 238


OWN_MRT functions:

OWN_MRT.Start allows operator to access OWN_MRT

OWN_MRT.WildCardSECFunction no extra feature added face to previous

function

OSM functions:

OSM.Start allows operator to access OSM

OSM.WildCardSECFunction no extra feature added face to previous function

OSM User functions:

OSM_USER.Start allows operator to access User Facilities

OSM_USER.WildCardSECFunction no extra feature added face to previous

function

Performance Administration functions:

PERF_ADMINISTRATION.Start allows operator to accessPERF_ADMINISTRATION

PERF_ADMINISTRATION.WildCardSECFunction no extra feature addedface to previous function

Performance Viewer functions:

PERF_VIEWER.Start allows operator to access PERF_VIEWER

PERF_VIEWER.WildCardSECFunction no extra feature added face to

previous function

RNO functions:

RNO_TB.Start allows operator to access RNO Tunning Browser

RNO_TB.WildCardSECFunction no extra feature added face to previous

function

Trace functions:

TRACE_VIEWER.Start allows operator to access [ Trace Viewer ] fromthe iconbox

TRACE_VIEWER.WildCardSECFunction no extra feature added face to

previous function

UFM functions:

UFM.Start allows operator to access UFM

UFM.WildCardSECFunction no extra feature added face to previous function

XTERM functions:

XTERM.Start allows operator to access XTERM

XTERM.WildCardSECFunction no extra feature added face to previous

function

72 / 238 3BK 20903 AAAA PCZZA Ed.22


COMMAND MODE functions:

COMMAND_MODE.Startallows operator to access the Command Mode

COMMAND_MODE.WildCardSECFunction extra feature added face to previous

function

MRTGMFS functions:

MRTGMFS.Start allows operator to access MRTGMFS

MRTGMFS.WildCardSECFunction no extra feature added face to previous

function

MFS_BACKUP functions:

MFS_BACKUP.Start allows operator to access MFS Backup

MFS_BACKUP.WildCardSECFunction no extra feature added face toprevious function

DOC Start functions:

DOC.Start allows operator to access the Documentation from the iconbox

DOC.WildCardSECFunction no extra feature added face to previous function

ACO MNG functions:

ACO_MNG.Start allows operator to access Aco Management

ACO_MNG.WildCardSECFunction no extra feature added face to previousfunction

ACO NTC functions (not used):

ACO_NTC.Start

ACO_NTC.WildCardSECFunction

3BK 20903 AAAA PCZZA Ed.22 73 / 238


3.5 OMC-R FADsA set of FADs is predefined and provided by Alcatel.

3.5.1 SYSTEM_ADMINISTRATION_FAD

Included FADs:

OWN_MRT_FAD

DOC_FAD

DSMUSM_FAD

OSM_FAD .

3.5.2 DOC_FAD

No FAD included.

Included Function: DOC.Start

3.5.3 OWN_MRT_FAD

No FAD included.

Included Function: OWN_MRT.Start

3.5.4 DSMUSM_FAD

No FAD included.

Included Function: DSMUSM.Start

3.5.5 OSM_FAD

No FAD included.

Included Function: OSM.Start

3.5.6 TELECOM_ADMINISTRATION_FAD

The administration functions are concerning all the BSCs.

Included FADs:

OWN_MRT_FAD

DOC_FAD

OAM_ADMINISTRATION_FAD

ASCURUSM_ADMINISTRATION_FAD

PERF_ADMINISTRATION_FAD

ASHISUSM_ADMINISTRATION_FAD

OSM_USER_FAD

No functions included.

74 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.7 OAM_ADMINISTRATION_FAD

No FAD included.

Included Functions:

OAM.Navigate_to_equipment

OAM.Declare_BSS

OAM.Start

OAM.Shutdown_access_point

OAM.Modify_BSS_MFS

OAM.Synchronise_date_time

OAM.Switch_OMC

OAM.Start_MFS_Supervision

OAM.Declare_MFS

OAM.Remove_BSS_MFS

OAM.Lock_unlock_access_point

OAM.Modify_peer_entities

3.5.8 ASCURUSM_ADMINISTRATION_FAD

No FAD included.

Included Functions:

AsCurrentUsm.NavigateToHistoricalUsm

AsCurrentUsm.CurrentUsmStartable

AsCurrentUsm.SetCurimAdministration

AsCurrentUsm.NavigateToExternal

AsCurrentUsm.MakeSynchronization

AsCurrentUsm.HistoricalUsmStartable

AsCurrentUsm.Start

3.5.9 PERF_ADMINISTRATION_FAD

No FAD included.

Included Function: PERF_ADMINISTRATION.Start

3BK 20903 AAAA PCZZA Ed.22 75 / 238


3.5.10 ASHISUSM_ADMINISTRATION_FAD

No FAD included.

Included Functions:

AsHistoricalUsm.BrowsePublicArchive

AsHistoricalUsm.NavigateToCurrentUsm

AsHistoricalUsm.CurrentUsmStartable

AsHistoricalUsm.NavigateToExternal

AsHistoricalUsm.HistoricalUsmStartable

AsHistoricalUsm.Start

3.5.11 OSM_USER_FAD

No FAD included.

Included function: OSM_USER.Start

3.5.12 SUPERVISION_FAD

Included FADs:

OWN_MRT_FAD

OAM_SUPERVISION_FAD

DOC_FAD

BSSUSM_SUPERVISION_FAD

ASHISUSM_SUPERVISION_FAD

RNUSM_SUPERVISION_FAD

ASCURUSM_SUPERVISION_FAD

TRACE_VIEWER_FAD

MFSUSM_SUPERVISION_FAD

OSM_USER_FAD

No Function inluded.

76 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.13 ASHISUSM_SUPERVISION_FAD

No FAD included.

Included Functions:


AsHistoricalUsm.GetMoreAlarmInformation




AsHistoricalUsm.ModifyFilters



AsHistoricalUsm.ExportAlarmInformation

3.5.14 RNUSM_SUPERVISION_FAD

No FAD included.

Included Functions:

RNUSM.Navigate_to_alarm

RNUSM.Navigate_to_equipment

RNUSM.Export

RNUSM.Lock_object

RNUSM.Logical_audit

RNUSM.NodeId_export

RNUSM.NodeId_import

RNUSM.Start

3BK 20903 AAAA PCZZA Ed.22 77 / 238


3.5.15 BSSUSM_SUPERVISION_FAD

No FAD included.

Included Functions:

BSSUSM.Discover_BSS

BSSUSM.Navigate_to_RNL

BSSUSM.Navigate_to_MFS

BSSUSM.Supervise_action

BSSUSM.Alarm_state_audit

BSSUSM.Open_close_A_channel_loop


BSSUSM.Navigate_to_alarm

BSSUSM.Manage_USD

BSSUSM.Start

BSSUSM.Supervise_hardware

3.5.16 MFSUSM_SUPERVISION_FAD

No FAD included.

Included Functions:

MFSUSM.Configure_alarm_reporting

MFSUSM.Check_gb

MFSUSM.Navigate_to_IMT

MFSUSM.Supervise_gb

MFSUSM.Navigate_to_BSS

MFSUSM.Check_atermux

MFSUSM.Display_link_connection_configuration

MFSUSM.Display_gb_configuration

MFSUSM.Check_GPU_BSS_allocation

MFSUSM.Navigate_to_alarm

MFSUSM.Check_links

MFSUSM.Start

MFSUSM.Lock_unlock_GSL

MFSUSM.Display_atermux_configuration

MFSUSM.Check_global

78 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.17 TRACE_VIEWER_FAD

No FAD included.

Included Function: TRACE_VIEWER.Start

3.5.18 OAM_SUPERVISION_FAD

No FAD included.

Included Functions:


OAM.Start

3.5.19 RESTRICTED_SUPERVISION_FAD

Included FADs:

OWN_MRT_FAD

OAM_SUPERVISION_FAD

DOC_FAD



MFSUSM_RESTRICTED_SUPERVISION_FAD

BSSUSM_RESTRICTED_SUPERVISION_FAD

TRACE_VIEWER_FAD

OSM_USER_FAD


No Function included.

3BK 20903 AAAA PCZZA Ed.22 79 / 238


3.5.20 MFSUSM_RESTRICTED_SUPERVISION_FAD

No FAD included.

Included Functions:


MFSUSM.Check_gb

MFSUSM.Supervise_gb







MFSUSM.Check_links

MFSUSM.Start



MFSUSM.Check_global

3.5.21 BSSUSM_RESTRICTED_SUPERVISION_FAD

No FAD included.

Included Functions:






BSSUSM.Start


80 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.22 CONFIGURATION_FAD

Included FADs:

OWN_MRT_FAD

ASHISUSM_CONFIGURATION_FAD

RNUSM_CONFIGURATION_FAD

MFSUSM_CONFIGURATION_FAD

OAM_SUPERVISION_FAD

DOC_FAD

BSSUSM_CONFIGURATION_FAD

ASCURUSM_CONFIGURATION_FAD

OSM_USER_FAD


3.5.23 ASHISUSM_CONFIGURATION_FAD

No FAD included.

Included Functions:









3BK 20903 AAAA PCZZA Ed.22 81 / 238


3.5.24 RNUSM_CONFIGURATION_FAD

No FAD included.

Included Functions:


RNUSM.Force_configuration


RNUSM.Export

RNUSM.Bar_object

RNUSM.Activate_SMSCB

RNUSM.Modify_object

RNUSM.Logical_audit

RNUSM.Configure_MFS

RNUSM.NodeId_export

RNUSM.NodeId_import

RNUSM.Start

3.5.25 BSSUSM_CONFIGURATION_FAD

No FAD included.

Included Functions:


BSSUSM.Manage_BSC_file

BSSUSM.Hardware_audit



BSSUSM.Map_RSL



BSSUSM.Configure_BSS_parameters

BSSUSM.Discover_BSS

BSSUSM.Configure_transmission



BSSUSM.Start

82 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.26 MFSUSM_CONFIGURATION_FAD

No FAD included.

Included Functions:


MFSUSM.Configure_link_connection

MFSUSM.Check_gb

MFSUSM.Align_global


MFSUSM.Supervise_gb


MFSUSM.Configure_radio


MFSUSM.Align_ater





MFSUSM.Configure_gb

MFSUSM.Check_links

MFSUSM.Start



MFSUSM.Align_links

MFSUSM.Check_global

MFSUSM.Configure_ater

3BK 20903 AAAA PCZZA Ed.22 83 / 238


3.5.27 ASCURUSM_CONFIGURATION_FAD

No FAD included.

Included Functions:

AsCurrentUsm.ExportAlarmInformation

AsCurrentUsm.GetMoreAlarmInformation





AsCurrentUsm.Start

3.5.28 ASCURUSM_READ_ONLY_FAD

No FAD included.

Included Functions:







AsCurrentUsm.Start

84 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.29 ASCURUSM_SUPERVISION_FAD

No FAD included.

Included Functions:

AsCurrentUsm.ModifyFilters

AsCurrentUsm.AcknowledgeAlarm

AsCurrentUsm.SetAlarmUserNote


AsCurrentUsm.ReserveAlarm

AsCurrentUsm.ClearAlarmManually


AsCurrentUsm.Start


AsCurrentUsm.ArchiveAlarmManually




AsCurrentUsm.RestrictedUnreserveAlarm

3.5.30 HW_EXT_RED_FAD

This FAD must be used in addition with another FAD like Supervision orConfiguration in order to be operational. The Hardware Extension / ReductionFAD mainly enables to achieve Hardware Extension Reduction operations,via BSSUSM.

Included FSDs:

RNUSM_HW_EXT_RED_FAD

BSSUSM_HW_EXT_RED_FAD


3.5.31 RNUSM_HW_EXT_RED_FAD

No FAD included.

Included Functions:

RNUSM.Geographical_localization

RNUSM.Commercial_usage

3BK 20903 AAAA PCZZA Ed.22 85 / 238


3.5.32 BSSUSM_HW_EXT_RED_FAD

No FAD included.

Included Functions:



BSSUSM.Map_RSL

BSSUSM.Configure_BTS_file

BSSUSM.Configure_hw_ext_red

BSSUSM.Start

3.5.33 SOFTWARE_MANAGEMENT_FAD

The software management FAD mainly enables to achieve backup/restore ofDLS and software migration/replacement.

Include FADs:

SOFTWARE_MANAGEMENT_FAD

OWN_MRT_FAD

OAM_SUPERVISION_FAD

DOC_FAD

MFS_BACKUP_FAD

OSM_USER_FAD


3.5.34 BSSUSM_SOFTWARE_MANAGEMENT_FAD

No FAD included.

Included Functions:

BSSUSM Supervise_action

BSSUSM Manage_software

BSSUSM Start

3.5.35 MFS_BACKUP_FAD

No FAD included.

Included Function: MFS_BACKUP.Start

86 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.36 PRC_FAD

The PRC FAD enables to achieve off-line radio configuration via RNUSM (itenables create/modify a PRC, activate the PRC if the user has the accessrights on all the objects which compose the PRC).

Included FADs:

RNUSM_PRC_FAD

OWN_MRT_FAD

DOC_FAD

OSM_USER_FAD


3.5.37 RNUSM_PRC_FAD

No FAD included.

Included Functions:

RNUSM.Activate_PRC


RNUSM.Manage_PRC

RNUSM.NodeId_export

RNUSM.NodeId_import

RNUSM.Start

3.5.38 PRC_RESTRICTED_ACCESS_FAD

The PRC FAD enables to achieve off-line radio configuration via RNUSM (itenables create/modify a PRC, activate the PRC including the restricted ones, ifthe user has the access rights on all the objects which compose the PRC).

Included FADs:

RNUSM_PRC_FAD

OWN_MRT_FAD

DOC_FAD

OSM_USER_FAD

RNUSM_PRC_RESTRICTED_FAD


3.5.39 RNUSM_PRC_RESTRICTED_FAD

No FAD included.

Included Function: RNUSM.prc_restricted_access

3BK 20903 AAAA PCZZA Ed.22 87 / 238


3.5.40 MLU_FAD

This FAD must be used in addition with PRC_FAD . It enables the activatePRC with the MLU mode.

Included FAD: RNUSM_MLU_FAD


3.5.41 RNUSM_MLU_FAD

No FAD included.

Included Functions:

RNUSM.Activate_MLU

RNUSM.NodeId_export

RNUSM.NodeId_import

3.5.42 ACCESS_TO_UNIX_FAD

This FAD offers an Unix terminal in the desktop customisation.

Included FADs:

OWN_MRT_FAD

DOC_FAD

XTERM_FAD

OSM_USER_FAD


3.5.43 XTERM_FAD

No FAD included.

Included Function: XTERM.Start

88 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.44 PERFORMANCE_FAD

Included FADs:

OWN_MRT_FAD

PERF_VIEWER_FAD

OAM_SUPERVISION_FAD

DOC_FAD

MFSUSM_PERFORMANCE_FAD


RNUSM_PERFORMANCE_FAD


BSSUSM_PERFORMANCE_FAD

OSM_USER_FAD


3.5.45 PERF_VIEWER_FAD

No FAD included.

Included Function: PERF_VIEWER.Start

3.5.46 RNUSM_PERFORMANCE_FAD

No FAD included.

Included Functions:




RNUSM.Start

3.5.47 MFSUSM_PERFORMANCE_FAD

No FAD included.

Included Functions:

MFSUSM.Navigate_to_performance


MFSUSM.Start


3BK 20903 AAAA PCZZA Ed.22 89 / 238


3.5.48 BSSUSM_PERFORMANCE_FAD

No FAD included.

Included Functions:





BSSUSM.Manage_USD

BSSUSM.Configure_PMC

BSSUSM.Configure_ODMC

BSSUSM.Manage_performance

BSSUSM.Navigate_to_performance

BSSUSM.Manage_indicator


BSSUSM.Manage_trace

BSSUSM.Manage_alerter

BSSUSM.Start

3.5.49 RESTRICTED_PERFORMANCE_FAD

This FAD is a subset of the PERFORMANCE_FAD . The FAD mainly enablesto achieve performance and trace.

Included FADs:

OWN_MRT_FAD

PERF_VIEWER_FAD

OAM_SUPERVISION_FAD

DOC_FAD

MFSUSM_PERFORMANCE_FAD


RNUSM_PERFORMANCE_FAD


BSSUSM_RESTRICTED_PERFORMANCE_FAD

OSM_USER_FAD


90 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.50 BSSUSM_RESTRICTED_PERFORMANCE_FAD

No FAD included.

Included Funtions:

BSSUSM Navigate_to_RNL

BSSUSM Configure_ODMC

BSSUSM Manage_performance

BSSUSM Navigate_to_MFS

BSSUSM Supervise_action

BSSUSM Navigate_to_performance

BSSUSM Manage_indicator

BSSUSM Navigate_to_alarm

BSSUSM Manage_trace

BSSUSM Configure_PMC

BSSUSM Start

BSSUSM Manage_alerter

3.5.51 COMMAND_MODE_FAD

This FAD allows the operator to use the command mode.

Included FADs:

COMMAND_MODE_FAD_A

OWN_MRT_FAD

DOC_FAD

OSM_USER_FAD


3.5.52 COMMAND_MODE_FAD_A

No FAD included.

Included Function: COMMAND_MODE.Start

3BK 20903 AAAA PCZZA Ed.22 91 / 238


3.5.53 INHIBIT_OAD_CONTROL_FAD

This allows the operator to run an application without performing any OADaccess control. This concerns the applications achieving control on objects.

No FAD included.

Included Functions:

BSSUSM.Inhibit_OAD_control

MFSUSM.Inhibit_OAD_control

OAM.Inhibit_OAD_control

RNUSM.Inhibit_OAD_control

AsCurrentUsm.InhibitOadControl

AsHistoricalUsm.InhibitOadControl

3.5.54 INHIBIT_FAD_CONTROL FAD

This FAD allows the operator to run an application without performing anyFAD access control.

Included FADs:

RNUSM_INHIBIT_FAD_CONTROL_FAD

UFM_FAD

FULL_MRT_FAD

MFSUSM_INHIBIT_FAD_CONTROL_FAD

PERF_VIEWER_FAD

DOC_FAD

BSSUSM_RI_FAD

RNO_TB_FAD

ENSUSM_RI_FAD


OAM_INHIBIT_FAD_CONTROL_FAD

ASHISUSM_INHIBIT_FAD_CONTROL_FAD

MFS_BACKUP_FAD

OSM_USER_FAD

COMMAND_MODE_FAD_A

BSSUSM_INHIBIT_FAD_CONTROL_FAD

OWN_MRT_FAD

DSMUSM_FAD

OSM_FAD

TRACE_VIEWER_FAD

92 / 238 3BK 20903 AAAA PCZZA Ed.22


ACO_MNG_FAD

XTERM_FAD

ASCURUSM_INHIBIT_FAD_CONTROL_FAD .

Included Functions:

IMT_GPUMFS_read

IMT_GPU.GPU_write

IMT_MFS.MFS_read

IMT_MFS.GPU_write

IMT_MFS.MFS_write

IMT_MFS.MFS_admin

IMT_MFS.MFS_platform

MRTGMFS.Start

3BK 20903 AAAA PCZZA Ed.22 93 / 238


3.5.55 RNUSM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

RNUSM.Inhibit_FAD_control

RNUSM.Start

RNUSM.Commercial_usage

RNUSM.Geographical_localization

RNUSM.NodeId_export

RNUSM.NodeId_import

RNUSM.Bar_object




RNUSM.Configure_MFS

RNUSM.Logical_audit

RNUSM.Force_configuration

RNUSM.Activate_SMSCB

RNUSM.Navigate_to_IMT_GPU

RNUSM.Navigate_to_IMT_MFS

RNUSM.Lock_object

RNUSM.prc_restricted_access

RNUSM.Activate_MLU

RNUSM.Activate_PRC

RNUSM.Modify_object

RNUSM.Export

RNUSM.Manage_PRC

3.5.56 UFM_FAD

No FAD included.

Included Function: UFM.Start

3.5.57 RNO_TB_FAD

No FAD included.

Included Function: RNO_TB.Start

94 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.58 OAM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

OAM.Inhibit_FAD_control

OAM.Start

OAM.Shutdown_access_point

OAM.Lock_unlock_access_point

OAM.Modify_peer_entities

OAM.Synchronise_date_time

OAM.Start_MFS_Supervision

OAM.Start_BSS_Supervision

OAM.Switch_OMC

OAM.NavigateToMrtg

OAM.ConfigureMrtg

OAM.Modify_BSS_MFS

OAM.Navigate_to_IMT_MFS

OAM.Remove_BSS_MFS

OAM.Declare_MFS

OAM.Declare_BSS


3BK 20903 AAAA PCZZA Ed.22 95 / 238


3.5.59 ASHISUSM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

AsHistoricalUsm.NavigateToElm






AsHistoricalUsm.ModifyFilters




AsHistoricalUsm.BrowseHistoricalAlarmLog

AsHistoricalUsm.InhibitFadControl

AsHistoricalUsm.InhibitSecurity

96 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.60 MFSUSM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

MFSUSM.Start

MFSUSM.Inhibit_FAD_control

MFSUSM.Supervise_gb

MFSUSM.Configure_radio

MFSUSM.Configure_gb

MFSUSM.Configure_ater

MFSUSM.Configure_link_connection


MFSUSM.Check_gb


MFSUSM.Check_links

MFSUSM.Check_global

MFSUSM.Align_ater

MFSUSM.NavigateToMrtg

MFSUSM.Align_links

MFSUSM.Align_global






MFSUSM.Navigate_to_equipment

MFSUSM.Navigate_to_performance



MFSUSM.Navigate_to_IMT_GPU

MFSUSM.Navigate_to_IMT_MFS


MFSUSM.Navigate_to_RNL

3BK 20903 AAAA PCZZA Ed.22 97 / 238


3.5.61 BSSUSM_RI_FAD

No FAD included.

Included Functions:

BSSUSM.Navigate_to_RI

BSSUSM.Start

98 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.62 BSSUSM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

BSSUSM.Inhibit_FAD_control

BSSUSM.Start


BSSUSM.Open_close_A_channel_loop

BSSUSM.Map_RSL

BSSUSM.Manage_trace

BSSUSM.Manage_USD

BSSUSM.Manage_indicator

BSSUSM.Manage_alerter

BSSUSM.Manage_performance

BSSUSM.Configure_ODMC

BSSUSM.Configure_PMC


BSSUSM.Hardware_audit

BSSUSM.Discover_BSS




BSSUSM.Manage_software

BSSUSM.Configure_BSS_parameters

BSSUSM.Configure_hw_ext_red

BSSUSM.Configure_transmission

BSSUSM.Configure_BTS_file

BSSUSM.Navigate_to_RI

BSSUSM.newly

BSSUSM.Navigate_to_performance




3BK 20903 AAAA PCZZA Ed.22 99 / 238


3.5.63 ASCURUSM_INHIBIT_FAD_CONTROL_FAD

No FAD included.

Included Functions:

AsCurrentUsm.ModifyFilters

AsCurrentUsm.AcknowledgeAlarm

AsCurrentUsm.InhibitFadControl

AsCurrentUsm.InhibitSecurity

AsCurrentUsm.NavigateToPnm

AsCurrentUsm.SetAlarmUserNote


AsCurrentUsm.ReserveAlarm

AsCurrentUsm.AssignAlarmToUser

AsCurrentUsm.SetCurimAdministration

AsCurrentUsm.ClearAlarmManually


AsCurrentUsm.MakeSynchronization

AsCurrentUsm.Start


AsCurrentUsm.ArchiveAlarmManually



AsCurrentUsm.RestrictedUnreserveAlarm

AsCurrentUsm.RequestTroubleTicketCreation


100 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.64 MULTI_OMC3_FAD

This FAD allows the operator to run application involving more than one OMC3.

Included FADs:

OWN_MRT_FAD

DOC_FAD

ACO_MNG_FAD

OSM_USER_FAD

Included Functions:

AsHistoricalUsm.InhibitOadControl

AsCurrentUsm.InhibitOadControl

3.5.65 UFM_ADMINISTRATION_FAD

This FAD is dedicated to the UFM application. The UFM functions havean impact on all the BSC. An operator having a profile that contains theUFM_ADMINISTRATION_FAD is allowed to do some change (like PMCmanagement) on the entire network. It is recommended to use this FAD in aprofile allowing modifications on entire network.

Included FADs:

UFM_FAD

OWN_MRT_FAD

DOC_FAD

OSM_USER_FAD


3.5.66 NPA_ADMINISTRATION_FAD

Included FADs:

OWN_MRT_FAD

DOC_FAD


OSM_USER_FAD


3BK 20903 AAAA PCZZA Ed.22 101 / 238


3.5.67 DCN_ADMINISTRATION_FAD

Included FADs:

OWN_MRT_FAD

DOC_FAD

OAM_ADMINISTRATION_FAD

OSM_USER_FAD


3.5.68 AS_ADMINISTRATION_FAD

Included FADs:

OWN_MRT_FAD

DOC_FAD

ASCURUSM_ADMINISTRATION_FAD


OSM_USER_FAD


3.5.69 PROCESS_MANAGEMENT_FAD

This FAD is a subset of the SYSTEM_ADMINISTRATION_FAD .

Included FADs:

OWN_MRT_FAD

DOC_FAD

DSMUSM_FAD

OSM_USER_FAD


3.5.70 USER_AND_PLATFORM_MANAGEMENT_FAD

This FAD is a subset of the SYSTEM_ADMINISTRATION_FAD .

Included FADs:

OWN_MRT_FAD

DOC_FAD

OSM_FAD


102 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.71 READ_ONLY_FAD

This FAD allows the operator only to read the configuration. No modificationis allowed

Included FADs:

OWN_MRT_FAD

OAM_SUPERVISION_FAD

DOC_FAD


ASCURUSM_READ_ONLY_FAD

RNUSM_READ_ONLY_FAD

MFSUSM_READ_ONLY_FAD

TRACE_VIEWER_FAD

BSSUSM_READ_ONLY_FAD

OSM_USER_FAD


3.5.72 RNUSM_READ_ONLY_FAD

No FAD included.

Included Functions:



RNUSM.Export

RNUSM.NodeId_export

RNUSM.Start

3.5.73 BSSUSM_READ_ONLY_FAD

No FAD included.

Included Functions:





BSSUSM.Start


3BK 20903 AAAA PCZZA Ed.22 103 / 238


3.5.74 MFSUSM_READ_ONLY_FAD

No FAD included.

Included Functions:




MFSUSM.Check_links

MFSUSM.Check_gb

MFSUSM.Start



MFSUSM.Check_global



3.5.75 REMOTE_INVENTORY_FAD

Included FADs:

OWN_MRT_FAD

DOC_FAD

BSSUSM_RI_FAD

ENSUSM_RI_FAD

OSM_USER_FAD


3.5.76 ENSUSM_RI_FAD

No FAD included.

Included function: ENSUSM.Start

3.5.77 FULL_MRT_FAD

Included FADs:

DOC_FAD

Global_Log_Viewer


104 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.78 Global_Log_Viewer

No FAD included.

Included function: FULL_MRT.Start

3.5.79 MFSSNMP_SUPERVISION_FAD

Included FADs:

OWN_MRT_FAD

OAM_SUPERVISION_FAD

DOC_FAD

BSSUSM_SUPERVISION_FAD

MFSUSM_NAVIGATE_MRTG_FAD

OAM_MRTG_FAD




TRACE_VIEWER_FAD

MFSUSM_SUPERVISION_FAD

OSM_USER_FAD

Included function: MRTGMFS.Start

3.5.80 OAM_MRTG_FAD

No FAD included.

Included Functions:

OAM.NavigateToMrtg

OAM.ConfigureMrtg

3.5.81 MFSUSM_NAVIGATE_MRTG_FAD

No FAD included.

Included Function: MFSUSM.NavigateToMrtg

3.5.82 IMT_CONF_GPU_FAD

Included FAD: IMT_GPU_CONF_FAD

Included Functions:



3BK 20903 AAAA PCZZA Ed.22 105 / 238


3.5.83 IMT_CONF_MFS_FAD

Included FAD: IMT_MFS_CONF_FAD

Included Functions:




3.5.84 IMT_ADMIN_FAD

Included FAD: IMT_MFS_ADMIN_FAD

Included Functions:




3.5.85 IMT_PLATFORM_FAD

Included FAD: IMT_MFS_PLATFORM_FAD

Included Functions:




3.5.86 IMT_GPU_CONF_FAD

No FAD included.

Included Functions:

IMT_GPU.MFS_read

IMT_GPU.GPU_write

3.5.87 IMT_MFS_CONF_FAD

No FAD included.

Included Functions:

IMT_MFS.MFS_read

IMT_MFS.GPU_write

IMT_MFS.MFS_write

106 / 238 3BK 20903 AAAA PCZZA Ed.22


3.5.88 IMT_MFS_ADMIN_FAD

No FAD included.

Included Functions:

IMT_MFS.MFS_read

IMT_MFS.GPU_write

IMT_MFS.MFS_write

IMT_MFS.MFS_admin

3.5.89 IMT_CONF_READ_FAD

Included FAD: IMT_READ_CONF_FAD

Included Functions:






3.5.90 IMT_READ_CONF_FAD

No FAD included.

Included Functions:

IMT_GPU.MFS_read

IMT_MFS.MFS_read

3.5.91 IMT_MFS_PLATFORM_FAD

No FAD included.

Included Functions:

IMT_MFS.MFS_read

IMT_MFS.GPU_write

IMT_MFS.MFS_write

IMT_MFS.MFS_admin

IMT_MFS.MFS_platform

3.5.92 ACO_MNG_FAD

No FAD included.

Included Function: ACO_MNG.Start

3BK 20903 AAAA PCZZA Ed.22 107 / 238


3.5.93 ACO_NTC_FAD

No FAD included.

Included Function: ACO_NTC.Start

108 / 238 3BK 20903 AAAA PCZZA Ed.22


3.6 Operator ManagementThe operator management GUI is displayed when the Operator management isselected from the tool bar or from the menu.

The Main Display area contains the following windows:

Operators

Edit.

3.6.1 Operators window

This panel contains the list of all operators. An icon is displayed in front of eachoperator, indicating their state of account: locked or unlocked.

Three buttons are available:

Lock : allows administrator to lock the account of the selected user

Unlock : allows administrator to unlock the account of the selected user

Help : shows the help on the current window.

To add a new entry in the ’assigned profiles’ table, select an entry from the’profiles’ table and click on the upper arrow. Once the assignment is performed,double click on the ’Role’ row and select the appropriate values.


Apply : saves all modification performed in the panel

Reset : discards user modifications. It reverts all fields to the initial value


3.6.2 Edit window

The Edit panel allows the administrator to define which profile should beassigned to the operator, and to specify roles.

This panel is composed of:

- a table on the left - contains all profiles defined in the sec database

- a table on the right - contains only assigned profiles.

3BK 20903 AAAA PCZZA Ed.22 109 / 238


3.7 Terminal ManagementThe Terminal Management GUI is displayed when the Terminal management isselected from the tool bar or from the tool menu. The tree area contains the listof terminals and the attached profile.

Two main windows are available:

Create Terminal

Profiles.

3.7.1 Create Terminal window

There is only one attribute in terminal creation, which is the hostname.

The provided actions are handled via the following buttons:

Apply : grayed by default, enabled when the field "new terminal " is edited.

If pressed, the new terminal is added to terminals list

Reset : grayed by default and enabled when any changes are made onterminal name, it allows the discard of user modifications

Set as default : allows the user to set the selected terminal as "Default

terminal", its name is displayed in the "Default Terminal" field


3.7.2 Profiles window

This panel allows the attachment/detachment of terminal profiles to/from theselected terminal. It contains a list box displaying all available terminal profiles.The user can select one terminal profile and assign it to the terminal.


Attach : allows to attach a terminal profile to a terminal, it is accessible

only when a terminal profile is selected from the list, and if it isn’t yetattached to the terminal

Detach : allows to detach an already attached terminal profile, it isaccessible only when a terminal profile is selected from the list and is

already attached to the terminal selected in the tree in the left side of

the terminal window

Reset : discards user modifications. It reverts all fields to the empty value.

110 / 238 3BK 20903 AAAA PCZZA Ed.22


3.8 Operator Profile ManagementOperator Profile Management is available via the SECUSM : Browser windowfrom the A1353-RA Icon Box. To access it, click on the [ Access RightsDefinition(SEC) ] icon. It is used to manage the creation, deletion andadministration of Operator Profiles.

Note: In the context of this section, Operator has the same meaning as User. Thus,an Operator Profile could also be described as a User Profile.

Recommendations

Operator Profile Management is only available to Administrators with anOperator Profile containing the SYSTEM_ADMINISTRATION_FAD. This FADshould only be assigned to specific users, and you should be very carefulwho else is given access to this FAD.

INHIBIT_FAD_CONTROL_FAD and INHIBIT_OAD_CONTROL_FAD allowaccess to everything. They should also be used with caution.

Note that all these profiles are cumulative. A user can have more than oneprofile and will then have all the access rights associated with each of theprofiles. This can lead to redundant rights, or to one profile completelyover-riding another.

Operator Profile name and operator name must be different. If the OperatorProfile name and the operator name are the same, at logon the user will not beable to access the OADs and FADs that were assigned to him.

It is possible to associate an object/group of objects to a FAD/ApplicationFunction inside a profile. For example a user may have administration rights onsome objects and supervision rights only, on other objects.

If a BSC is added to an Operator Profile, the MFS where the BSC is associated,must also be added to the Operator Profile. If the MFS is removed from theOperator Profile, also the corresponding BSCs must be removed from theOperator Profile. The BSCs will not be seen in the RNUSM even if the MFS isadded back in the Operator Profile. A BSC will be seen in the RNUSM onlyafter it is removed from the Operator Profile and then added back.

Do not delete or change the following profiles:

axadmin_special_profile

sec_profile

Profile_customFAD

For further information, refer to the following tasks:

Display All Available Operator Profiles (Section 3.8.1)

Create Operator Profiles (Section 3.8.2)

Delete Operator Profiles (Section 3.8.3)

Display Operator Profiles (Section 3.8.4)

Modify an Operator Profiles (Section 3.8.5)

Assign Operator Profiles (Section 3.8.6)

Unassign Operator Profiles (Section 3.8.7) .

3BK 20903 AAAA PCZZA Ed.22 111 / 238


3.8.1 Display All Available Operator Profiles

To view a list of all the available Operator Profiles, from the SECUSM:Tools ->Show -> Operator Profiles .

3.8.2 Create Operator Profiles

To create a new Operator Profile:

1. From the SECUSM select:Tools -> Show -> Operator Profiles .

2. In the left window click on Operator_Profile .

3. Use the right window to create the operator profile.

4. Complete the field ’Friendly Name’ with the profile name.

5. Click on the Select Target tab if it is not active.The Excluded Targetslist contains the available:

Objects

Functions

OADs

Operator Profiles

FADs

The checkboxes below this list can be used to display or hide elementsof this list.

The Included Targets list contains the selected elements for this profile.

Use the and buttons to move the selected elementsbetween the 2 lists.

6. To create associations, click on Create Association tab.

Select one FAD or Function from the left list, select one Object orFAD from the list in the middle (do not select WildCardSECObject orSecWildCardSECObject). Click on [ Apply ] button to make the association.To remove an association, select it from the right list and click on [ Remove ]button.

7. To create the profile click on [ Apply ] button.

The created profile is displayed in the operator profile list, in the left window.

112 / 238 3BK 20903 AAAA PCZZA Ed.22


3.8.3 Delete Operator Profiles

It is possible to delete Operator Profiles from the SECUSM : Browser window.

Make sure you do not delete an Operator Profile that is assigned to a user.When deleting an Operator Profile that is assigned to a user, you also unassignthe Operator Profile for the user.If you delete an existing profile that is used by a user that is currently logged on,the changes do not take effect until that user closes all his current sessionsand reopens a new session.

Procedure To delete an existing Operator Profile:

1. From the SECUSM select: Tools -> Show -> Operator Profiles .

2. In the left window click on operator profile to be deleted.

3. From the menu select: Edit -> Remove from database . In the removalconfirmation window click on [ OK ] .

3.8.4 Display Operator Profiles

To view an existing Operator Profile:

1. From the SECUSM select: Tools -> Show -> Operator Profiles .

2. In the left window double click on the profile to be displayed.

3BK 20903 AAAA PCZZA Ed.22 113 / 238


3.8.5 Modify an Operator Profiles

If you modify an existing profile that is used by a user that is currently loggedon, the changes do not take effect until that user closes all his current sessionsand reopens a new session.

Procedure To add access rights to an existing Operator Profile:

1. From the SECUSM select:Tools -> Show -> Operator Profiles .

2. In the left window click on the profile to be modified.

3. Use the right window to modify the operator profile.

4. Click on the Select Target tab if it is not active.The Excluded Targetslist contains the excluded:

Objects

Functions

OADs

Operator Profiles

FADs


The Included Targets list contains the selected elements for the profile. Use

the and buttons to move the selected elements betweenthe 2 lists.

5. To create associations, click on Create Association tab.

Select one FAD or Function from the left list, select one Object orFAD from the list in the middle (do not select WildCardSECObject orSecWildCardSECObject). Click on [ Apply ] button to make the association.To remove an association, select it from the right list and click on [ Remove ]button.

6. To save the modified profile click on [ Apply ] button.

114 / 238 3BK 20903 AAAA PCZZA Ed.22


3.8.6 Assign Operator Profiles

New users must be assigned an Operator Profile before they are able to usethe system. In addition, it is sometimes necessary to change the profile of auser. Both tasks are carried out in the same way.

If you assign an Operator Profile to a user that is currently logged on, thechanges do not take effect until that user closes all his current sessions andreopens a new session.Operator Profile name and operator name must be different. If the OperatorProfile name and the operator name are the same, at logon the user will not beable to access the OADs and FADs that were assigned to him.

Procedure To assign a profile to a new or existing user:

1. After you add a user (refer to Add Users (Section 3.3.1) ), you must assignan Operator Profile to them before they can function. If the new user’s namedoes not appear under the heading Operators, return to Add Users (Section3.3.1) and make sure that you have created the user successfully.

Note: Alcatel provides default profiles (refer to Display All Available Operator Profiles(Section 3.8.1) ). If no other profiles have been created, refer to CreateOperator Profiles (Section 3.8.2) .

2. From the SECUSM select:Tools -> Show -> Operators .

In the left window click on the user to be modified

3. Use the right window to assign operator profiles. The left list contains allthe available user profiles. The right list contains the profiles assigned tothe user.

4. To assign a profile to the user select it in the left list and click on [ >> ] button.

5. To save click on [ Apply ] button.

The message: Operator <user name> was modified.

3.8.7 Unassign Operator Profiles

If you unassign an Operator Profile for a user that is currently logged on,the changes do not take effect until that user closes all his current sessionsand reopens a new session.

To unassign an Operator profile:

1. From the SECUSM select:Tools -> Show -> Operators .

In the left window click on the user to be modified

2. Use the right window to unassign operator profiles. The left list contains allthe available user profiles. The right list contains the profiles assigned tothe user.

3. Select the profile to be unassigned from the right list and click on [ << ] button.

4. To save, click on [ Apply ] button.

The message: Operator <user name> was modified is displayed.

3BK 20903 AAAA PCZZA Ed.22 115 / 238


3.9 Terminal Profile ManagementA terminal is the Master Host or any connected HMI. All users sessionsmanaged by that Master Host or HMI are subject to the same terminal Profile.

This profile type has the same capabilities as the Operator Profile, it issubjected by the same rules. Consequently, we can attach one/severalTerminal Profiles to a terminal.

A terminal does not grant any access rights. The terminal profile is here to limitthe access rights of the operators issuing SEC access control demands fromthis terminal (a logical AND is done between the SEC functions of the operatorprofile and the SEC functions of the Terminal Profile).

3.9.1 Display All Available Terminal Profiles

To view a list of all the available Terminal Profiles, from the SECUSM:Tools ->Show -> Terminal Profiles .

There should always be at least two profiles in this list.

The default terminal profiles provided by Alcatel are listed below:

<omcr_hostname>_terminal_profile

sec_terminal_profile

All other profiles must be defined.

3.9.2 Create Terminal Profiles

To create a new Terminal Profile:

1. From the SECUSM select:Tools -> Show -> Terminal Profiles .

2. In the left window click on Terminal_Profile .

3. Use the right window to create the terminal profile.

4. Complete the field ’Friendly Name’ with the profile name.The ExcludedFADs/Functions list contains the available:

Functions

FADs


The Included FADs/Functions list contains the selected elements for this

profile. Use the and buttons to move the selected elementsbetween the 2 lists.

5. To create the profile click on [ Apply ] button.

The created profile is displayed in the operator profile list, in the left window.

116 / 238 3BK 20903 AAAA PCZZA Ed.22


3.9.3 Delete Terminal Profiles

It is possible to delete Terminal Profiles from the SECUSM : Browser window.

Make sure you do not delete a Terminal Profile that is assigned to a terminal.When deleting a Terminal Profile that is assigned to a terminal, you alsounassign the Profile from the terminal.

Procedure To delete an existing Terminal Profile:


2. In the left window click on terminal profile to be deleted.


3.9.4 Display Terminal Profiles

To view an existing Terminal Profiles:


2. In the left window click on the profile to be displayed.

3.9.5 Modify a Terminal Profile

The modifications are taking into account after the next login from the terminal.

Procedure To modify the access rights of an existing Terminal Profile:


2. In the left window click on the profile to be modified.

3. Use the right window to modify the operator profile.The ExcludedFADs/Functions list contains the available:

Functions

FADs



profile. Use the and buttons to move the selected elementsbetween the 2 lists.

4. To save the modified profile click on [ Apply ] button.

3BK 20903 AAAA PCZZA Ed.22 117 / 238


3.9.6 Attach/Detach Terminal Profiles

Procedure To attach or detach a Terminal Profile:

1. From the SECUSM select:Tools -> Show -> Terminals .

In the left window click on the terminal to be modified

2. In the right window click on the Terminal Profile .

3. To assign the selected profile to the selected terminal click on [ Attach ]button.

4. To detach the selected profile from the selected terminal click on [ Detach ]button.

118 / 238 3BK 20903 AAAA PCZZA Ed.22


3.10 OAD ManagementAn OAD is a set of Network Elements. No default OADs are supplied and sothey must be defined by the users. OADs are used to specify which NEsspecific Operator Profiles are allowed to access.

Modification of OADs is dynamic. If a new object is added to an OAD, everyonewith access to that OAD will have instant access to the new object.

OAD management includes the following tasks:

Create OADs (Section 3.10.1)

Delete OADs (Section 3.10.2)

Display OADs (Section 3.10.3)

Modify Access Rights to OADs (Section 3.10.4)

3.10.1 Create OADs

To create an OAD:

1. From the SECUSM select:Tools -> Show -> OADs .

In the left window click on OAD .

2. Use the right window to create OADs.

3. Complete the field ’Friendly Name’ with the OAD name.

4. The Excluded Objects/OADs list contains the available Objects and OADswhich can be used to create the new OAD.

The checkboxes below this list can be used to display or hide elementsof the list.

The Included Objects/OADs list contains the selected elements for this

OAD. Use the and buttons to move the selected elementsbetween the 2 lists.

5. To create the OAD click on [ Apply ] button.

The created OAD is displayed in the OAD list, in the left window.

3BK 20903 AAAA PCZZA Ed.22 119 / 238


3.10.2 Delete OADs

If you delete an OAD, it will affect all connected users with this OAD in theiroperator profile, except if they have the INHIBIT_OAD_CONTROL_FADin their profile.

To delete an OAD:


2. In the left window click on OAD to be deleted.


3.10.3 Display OADs

To display an OAD:


2. In the left window double click on the OAD to be displayed.

3.10.4 Modify Access Rights to OADs

If you add/remove access rights to an OAD, it will affect all connectedusers with this OAD in their operator profile, except if they have theINHIBIT_OAD_CONTROL_FAD in their profile.

To modify the access rights to an OAD:


In the left window click on the OAD to be modified.

2. Use the right window to modify the OAD.

3. The Excluded Objects/OADs list contains the available Objects and OADswhich can be added to the OAD.


The Included Objects/OADs list contains the selected elements for this

OAD. Use the and buttons to move the selected elementsbetween the 2 lists.

4. To save the OAD click on [ Apply ] button.

The message: OAD <oad name> was modified , is displayed.

120 / 238 3BK 20903 AAAA PCZZA Ed.22


3.11 FAD Management

The FADs provided by Alcatel can be modified. It is strongly recommendedthough to preserve existing Alcatel FADs and to create new FADs. Modifyingexisting Alcatel FADs can lead to dangerous behavior. Alcatel defined FADscan be used to build new FADs.This feature can be used by axadmin or any user including the profileProfile_customFAD .

3.11.1 Create FAD

The new FAD is build using already existing FADs and Functions.

1. From the SECUSM select:Tools -> Show -> functions/FADs .

In the left window click on the FAD.

2. Use the right window to create FADs.

3. Complete the field ’Friendly Name’ with the FAD name.

The FAD name can be composed from alphanumeric characters, "-" and"_" from the special characters.

All the other special characters are not allowed:#$[]{}()*+?^&=-‘!@%_~,:;’.<>|\/"

4. Select the ’Application’ from the list (optional).

5. The Excluded FADs/Functions list contains the available Functions andFADs which can be added to the FAD.



FAD. Use the and buttons to move the selected elementsbetween the 2 lists.

6. To save the FAD click on [ Apply ] button.

The message: FAD <fad name> was created , is displayed.

3.11.2 Delete FAD

To delete an OAD:


2. In the left window click on FAD to be deleted.


3.11.3 Display FAD


2. In the left window double click on the FAD.

3BK 20903 AAAA PCZZA Ed.22 121 / 238


3.11.4 Modify FAD

It is strongly recommended to preserve existing Alcatel FADs and to create newFADs. Modifying existing Alcatel FADs can lead to dangerous behavior.It is recommended to modify only the client customized FADs.


In the left window click on the FAD to be modified.

2. Use the right window to modify the FAD.

3. Select the ’Application’ from the list (optional).

4. The Excluded FADs/Functions list contains the available Functions andFADs which can be added to the FAD.



FAD. Use the and buttons to move the selected elementsbetween the 2 lists.

5. To save the FAD click on [ Apply ] button.

The message: FAD <fad name> was modified , is displayed.

Many functions need the same windows. Removing some functions from apredefined Alcatel FAD doesn’t mean that the windows provided by thesefunctions won’t be accessible, if these windows are needed by anotherfunctions still included in the FAD.It is strongly recommended to preserve existing Alcatel FADs and to createnew FADs for the customers needs.

3.12 Restore Default FADs and ProfilesIf the FADs (and Profiles) delivered by Alcatel have been modified, it ispossible to restore them.

Close all SECUSM windows and perform as axadmin :/alcatel/omc3/sec/script/restore_sec.pl

The FADs and Profiles defined by the operator are not modified.

122 / 238 3BK 20903 AAAA PCZZA Ed.22


3.13 FTP Users

External applications can not launch commands on the B9 OMC-R remotely(telnet, rcp, rsh).

1. The following ftp users are defined:

omc3ftp

rno

laser

pmuser

metrica.

2. The user rights are limited to ftp operations. The default password of eachuser is installed during OMC-R installation and is the same like the user (i.e.user: omc3ftp , password: omc3ftp ).

3. The omc3ftp , rno , pmuser and laser users are logged in their defaultroot directory of the ftp server (/alcatel/var/share/AFTR ). The usercan not go upper than this.

4. The organization of the ftp server directory, for omc3ftp , rno , pmuserand laser users, is the following. The access rights mentioned are relatedto the ftp server configuration and does not concern the Unix accessrights. The MISC directory can be used for various remote file transfersin ftp configuration.

Directory Sub-directory Access Rights

ACIE_B1export R for omc3ftp and rno

ACIE_NLexport_Dir1 R for omc3ftp and rno

ACIE_NLexport_Dir2 R for omc3ftp and rno

ACIE_NLexport_Dir... R for omc3ftp and rno

ACIE_NLimport_Dir1 R/W for omc3ftp and rno

ACIE_NLimport_Dir2 R/W for omc3ftp and rno

ACIE

ACIE_NLimport_Dir... R/W for omc3ftp and rno

AGUE R for omc3ftp

ANIE_export R for omc3ftpANIE

ANIE_import R/W for omc3ftp

ARIE R for omc3ftp

HALD R for omc3ftp

SCD R for omc3ftp

3BK 20903 AAAA PCZZA Ed.22 123 / 238


Directory Sub-directory Access Rights

SOCAD R for omc3ftp

ACME R for omc3ftp, pmuser and laser

BSC R for omc3ftp and pmuser

MFS R for omc3ftp and pmuser

APME

OBSYNT R for omc3ftp and pmuser

RNO R/W for rno

LASER R/W for laser

NPA R for pmuser

MISC R/W for omc3ftp

Table 4: FTP server directory organization for omc3ftp , rno , pmuser and laser

5. The metrica user is logged in his default root directory of the ftp server(/alcatel/npa/var/ ). The user can not go upper than this.

6. The organization of the ftp server directory, for metrica user is the following.The access rights mentioned are related to the ftp server configuration anddoes not concern the Unix access rights.

Directory Access Rights

/ R for metrica

/spool R for metrica

/spool/bss R for metrica

/spool/bss/laser R/W for metrica

Table 5: FTP server directory organization for metrica

124 / 238 3BK 20903 AAAA PCZZA Ed.22


3.14 Change FTP User PasswordTo modify the password of an ftp user:

1. From OSM Administration Facilities menu select: Administration -> UserManagement -> Change ProFtp password .

2. Select the user in the from the Login name list.

Give the new password and confirm the new password, click on [ ChangePassword ] and [ Confirm ] button.

3.15 Non-OMC-R Users CustomizationFor the UNIX users created without the tools provided by OSM (non-OMC-Rusers), a set of parameters must be set in /etc/default/login and/etc/default/passwd files.

The following table shows the settings that must be set in /etc/default/login

:

Parameter Description

ULIMIT Sets the file size limit for the login. Units are diskblocks

TIMEOUT Sets the number of seconds to wait beforeabandoning a login session

RETRIES Sets the number of retries for logging in

Table 6: Default account settings for non-OMC-R users

The following table shows the settings that must be set in /etc/default/passwd

:

Parameter Description

MAXWEEKS Maximum time period that password is valid.

MINWEEKS Minimum time period before the password can bechanged

PASSLENGTH Minimum length of password, in characters

WARNWEEKS Time period until warning of date of password’sensuing expiration

Table 7: Password policy for non-OMC-R users

3BK 20903 AAAA PCZZA Ed.22 125 / 238


3.16 Activate MPM on OMC-RAs root , perform the following actions:

1. Remove the MPM package:# pkgrm OMCGmpm

Answer with y to the following questions:Do you want to remove this package? [y,n,?,q]Do you want to continue with the removal of thispackage [y,n,?,q]

The following message appears at the end of ’OMCGmpm’ removal:Removal of <OMCGmpm> was successful.

2. Remove the following directories:# rm -rf /db# rm -rf /spool# rm -rf /metrica# rm -rf /alcatel/npr# rm -rf /alcatel/var/home/metrica

3. Copy the MPM licence in /install/data directory.

4. Insert CD3 into the CD-ROM drive and perform the following operations:# cd /cdrom/cdrom0/OMC3# cp OMCGmpm_* /var/tmp/# cd /var/tmp# gzip -cd OMCGmpm_* | cpio -icdumD# pkgadd -d .

The list of available packages is displayed, followed by the messageSelect package(s) you wish to process (or ’all’ toprocess all packages). (default: all) [?,??,q]

Type the number corresponding to the ’OMCGmpm’ package (usually [ 1 ] ).Do you want to install these as setuid/setgid files[y,n,?,q]

Type y .Do you want to continue with the installation of<OMCGmpm> [y,n,?]

Type y .

The following message appears at the end of the instalation:Installation of <OMCGmpm> was successful.

126 / 238 3BK 20903 AAAA PCZZA Ed.22

4 Day-To-Day Administration Tasks


This section tells you how to perform day-to-day administration tasks such ashardware and software inventory, displaying Patch identities, checksums andbinary signatures. Fault management is also discussed.

3BK 20903 AAAA PCZZA Ed.22 127 / 238


4.1 Hardware InventoryThe inventory features allow you to:

See what is on the OMC-R system

Check the content of the system

List all the workstations and printers installed and managed by the OMC-R

Quickly access the release version of Software and Hardware for fault

diagnosis.

Inventory information related to each workstation can be presented on the OSMfrom the Hardware Inventory option or the Device Management option.

4.1.1 Display Workstations

The OMC-R Workstations inventory displays a list of all workstations installedand managed by the OMC-R. The Workstation Management option alsodisplays a list of all the workstations.

4.1.2 From the Hardware Inventory Option

1. From the OSM Administration Facilities Main Menu, select HardwareInventory .

2. Click on [ Workstations ] .

A list of workstations is displayed on the left-hand side of the screen. Formore details about a specific workstation, click on its icon.

3. For each selected workstation, a list of workstation attributes appears.

4.1.3 From the Workstation Management Option

From the OSM Administration Facilities Main Menu, select Configuration ->Workstation Management -> Workstation Inventory .

This displays a list of workstations, including the hostname, IP address andtype of workstation.

128 / 238 3BK 20903 AAAA PCZZA Ed.22


4.2 Software InventorySoftware inventory provides traceability of all software components:

OMC-R products and their associated sub-products

Third-party products, release numbers and sub-products

Patch identification from revision number and description

Executable and tag identification from binary signatures.

Software inventory displays:

Checksum and binary signatures

Unauthorized updates

If an update is needed

Which versions are being run

(Using checksums) whether any files have changed since the last upgrade.

Software Inventory also does an integrity check, and when there is a newinstallation the binary signature and the checksum become the new officialversions.

4.2.1 Display Software Applications

To view software applications, which include OMC-R products, their releasenumbers and filesets:

1. From the OSM Administration Facilities Main Menu, select:

Software Inventory .

2. From the Software Inventory menu, click on the [ Applications ] button toselect the workstation you want to view software for.

A list of workstations appears on the left-hand side of the screen.

Alternatively, from the Software Inventory menu, click on the name[ Applications ] to view software for all workstations.

3. If you clicked on the [ Applications ] button, click on the workstation you wantto view the software for.

For the (selected) workstations, a table is displayed on the right-hand side ofthe screen. It contains a list of products, including information about thesoftware version that is loaded on the workstation, as well as a descriptionof the product. Each product has a checkbox next to it.

4. To view the fileset information for a product, click on the checkbox next tothat product, then click on [ Filesets ] .

This displays a table containing details of the filesets associated withthe products you selected.

5. To view more detailed fileset information, click on [ More Details ] .

This displays a table that includes details of the version, architecture,machine type, operating system release and version, packaging dateand size of the product.

3BK 20903 AAAA PCZZA Ed.22 129 / 238


4.2.2 Display Third Party Information

Third-party information can be used to identify third-party products, releasenumbers and filesets.

Procedure To view third-party information:

1. From the OSM Administration Facilities Main Menu, select SoftwareInventory .

2. From the Software Inventory menu, click on the [ Third Parties ] button toselect the workstation you want to view third party software for.


Alternatively, from the Software Inventory menu, click on the name [ ThirdParties ] to view third-party software for all workstations.

3. If you clicked on the [ Third Parties ] button, click on the workstation you wantto view the third-party software for.

For the (selected) workstations, a table is displayed on the right-hand sideof the screen. This table contains a list of products, including informationabout the software version that is loaded on the workstation, as well as adescription of the product. Each product has a checkbox next to it.

4. To view the fileset information for a product, click on the checkbox next tothat product, then click on [ Filesets ] .

This displays a table containing details of the filesets associated withthe products you selected.

5. To view more detailed fileset information, click on [ More Details ] .

This displays a table that includes details of the version, architecture,machine type, operating system release and version, packaging dateand size of the product.

4.2.3 Display Patches

Patch information is used to identify patches from their number, last installationdate and description.

Procedure To view patch information:

1. From the OSM Administration Facilities Main Menu, select SoftwareInventory -> Patches .

A list of workstations opens on the left-hand side of the screen.

2. Click on the workstation you want to view the patches for.

A table opens on the right-hand side of the screen. This table contains alist of patches, along with a description of each patch and a record of thelast time it was installed.

130 / 238 3BK 20903 AAAA PCZZA Ed.22


4.2.4 Display Changed Files

Changed files information is used to display the added, modified, and deletedfiles with their their name, rights, and last modified date since the last softwareupgrade.

Procedure To view changed files information:

1. From the OSM Administration Facilities Main Menu, select SoftwareInventory -> Changed Files .

2. From the pop-up menu on the left frame, select the workstation whosechanged files information you want to view.

3. From the Files Type list, select the appropriate type of files:

Bin Files

Scripts

Configuration Files

Data Files.

4. Click on [ Reset ] to initialize the database. This can take several minutesdepending on the size of the database.

5. Click on [ View last changed files ] to display the added, modified, and deletedfiles since the last software upgrade, for the previously selected file types.

4.2.5 Display Binary Signatures

The OMC-R components provide an additional identification mechanism basedon the internal signatures of binaries that are set at compilation time. Binarysignature information is used to identify executables and their associated tags.

Procedure To view binary signatures:

1. From the OSM Administration Facilities Main Menu, select SoftwareInventory -> Binaries Signatures .

2. From the Software Inventory menu, click on the [ Binary Signatures ] buttonto select the workstation whose binary signature you want to view.


Alternatively, from the Software Inventory menu, click on the name [ BinarySignatures ] to view the binary signatures for all workstations.

3. If you clicked on the [ Binary Signatures ] button, click on the workstation youwant to view the binary signature for.

For the (selected) workstations, a table opens on the right-hand side of thescreen. It contains the binary signature(s).

3BK 20903 AAAA PCZZA Ed.22 131 / 238


4.3 Failure Management

Perform a capture and archive of failure data when a failure occurs so Alcatelsupport personnel can analyze the trace files. Alcatel will advise you on how tosend the archived file (which can be up to 200 Mbytes).

Failure data is used to keep track of the system state when a failure occurs.Failure management allows information about these problems to be gatheredtogether for analysis by Alcatel support personnel. When a failure occurs, usethe failure management function to take a snapshot of the system at thatmoment (of the trace files) while the system continues to run.

As a result, there are three stages to OMC-R failure management:

Capture

Display

Archive.

4.3.1 Capture Failure Data

The first requirement is to capture the data when the failure occurs. Do thismanually from the OSM when there is a failure. Because failure data files arenormally large, the system is unable to retain many of them. Therefore, apredefined number of files can be kept. The default number of failure data filesis three per Master workstation and three per HMI. Once this limit is reached, ifa new failure is logged, the oldest failure is deleted unless the file is locked.

4.3.2 Display Failure Data

The display option shows both the automatic failure captures and any that havebeen done manually. Failure data is recorded and stored for each station,not for the whole system. The display feature allows you to see all the dataon all the stations.

Failures are captured on various stations and then sent to the Master stationwhen they are archived. The archive option allows failure data to be stored in acentral location so that it can be recorded and used for analysis.

132 / 238 3BK 20903 AAAA PCZZA Ed.22


4.3.3 Capture Failure Data

Captured failure data provides information that is used to keep track of thesystem state when a failure occurs. It is used both to diagnose the origin of thefailure and to attempt to fix it. This task must be performed by the operatorafter a system malfunction.

Note: Whenever a new failure is captured, the oldest unlocked failure capture isdeleted. Locked failures are never replaced. If all previous failure capturesare locked, the new failure capture is not saved.

Procedure To capture failure data:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> New Failure .

A list of workstations opens on the left-hand side of the screen.

2. Select the workstation(s) that failure data is to be captured for. Do this byclicking on the checkboxes next to the appropriate workstation(s).

3. In the ’Label’ field, if you wish to, you can specify the name of the newcapture file.

4. If the captured file is to be locked, click on the checkbox next to the Lock icon.If the file is locked, it cannot be deleted by later files with the same name.

5. Click on [ Capture ] . The following message appears:Collecting data: please wait

Once the capture is complete, the captured files are displayed on theworkstation where the failure data has been captured. The list containsthe Date, Hostname, Submitter and Lock for each file. If several capturesare performed for several workstations at the same time, all captured filesrelated to these workstations are displayed.

6. To view more information about a captured file, click on the date information.

7. To return to the list of captured files, click on the [ Back ] button.

4.3.4 Display Failure Data

This task displays capture files from previous failures. Failure data providesinformation that is used to keep track of the system state when a failure occurs.

Procedure To view failure data:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> List Failures .

This displays a list of all captured files giving the Date, Hostname, Submitterand Lock details for each file. By default, a maximum of three captured filesper machine is displayed.

2. To view more information about any of the captured files, click on thedate information.


3BK 20903 AAAA PCZZA Ed.22 133 / 238


4.3.5 Lock/Unlock Failure Data Files

A locked failure capture cannot be deleted; it must first be unlocked.

Procedure To lock or unlock a failure data file:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> Lock/Unlock Failures .

This displays a list of all failure data files, and includes the Date, Hostname,Submitter and Lock details for each file. There is a checkbox next to each file.

2. Select the file that is to be locked or unlocked and click on the checkbox.This updates the list of failure data files so that an icon appears ordisappears in/from the Lock column next to each file.

3. To view more information about the file, click on the date information.

4. To return to the list of failure data files, click on the [ Back ] button.

4.3.6 Delete Failure Data Files

You can delete old failure data to free disk space for new failure capturesand archives or other applications.

Note: If a file is locked it cannot be removed. It must be unlocked first (seeLock/Unlock Failure Data Files (Section 4.3.5) ). If you try to remove a lockedfile, the following message appears:

workstation ’name’: couldn’t remove filename

Procedure To remove failure data:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> Remove Failures .

This displays a list of all unarchived captured files with a checkbox next toeach file. The list shows the Date, Hostname, Submitter and Lock detailsfor each file.

2. Select the files to be removed. To do this, click on the checkbox of eachfile that is to be removed.

3. Click on [ Remove ] . A list opens showing what has been removed andwhat is left, and the following message appears:

workstation: filename removed

134 / 238 3BK 20903 AAAA PCZZA Ed.22


4.3.7 Archive Failure Data

Captured failure data is centralized and the files are archived from the Masterterminal.

Procedure To archive failure data files:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> Archive Failures .

The Failures Management window opens. The display includes a list of allunarchived captured files with a checkbox next to each file. The list showsthe Date, Hostname, Submitter and Lock details for each file.

2. Select the file(s) that are to be archived. Do this by clicking on thecheckboxes next to the appropriate files. This automatically moves the filesto the archive and displays a list of all the archived files.

3. To view more information about the captured file, click on the dateinformation.


4.3.8 Display Archived Failure Data

To view archived failure data files:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> List Archives .

This displays a list of all archived files. The list shows the Date, Hostname,and Submitter for each file.

2. To view more information about a file, click on the date information.

3. To return to the list, click on the [ Back ] button.

4.3.9 Delete Archived Failure Data

This task deletes selected archived failures to free disk space for new failurecaptures, archives or other applications.

Procedure To remove archived failure data:

1. From the OSM Administration Facilities Main Menu, select Administration-> Failure Management -> Remove Archives .

This lists the archives giving the date they were archived, the hostnameand the username of the person who archived the file. There is a checkboxnext to each file.

2. Select the archived files to be removed. To do this, click on the checkboxof each file that is to be removed.

3. Click on [ Remove ] . A list shows what has been removed and what is left.

3BK 20903 AAAA PCZZA Ed.22 135 / 238


4.4 Monitor SystemYou must monitor the Disk Usage and the IP protocol of the OMC-R system.

4.4.1 Disk Usage

You must monitor the OMC-R system to ensure that system files do not becometoo large and that data size limits are not exceeded.

Note: This is not the main monitoring function for the system. This relates to theMozilla window only. You can see some information relating to disk usage butnothing more.

4.4.1.1 What is MonitoredSystem monitoring is used to view the:

Workstation partitions

Size of each partition

Percentage of used disk space

Available disk space.

4.4.1.2 ProcedureTo perform system monitoring:

From the OSM Administration Facilities Main Menu, select Administration ->System Monitoring -> Disk Usage .

The system displays disk usage information for the host machine to which youare currently logged on, including which partition is being used, the size ofthe partition (in megabytes), the percentage of space used and the amountof available space (in megabytes).

136 / 238 3BK 20903 AAAA PCZZA Ed.22


4.4.2 Internet Protocol Monitoring

BSC - IP connections are regularly monitored by the system. The connectionstatus is polled every 5 minutes.

4.4.2.1 Notification of IP Connection FailureIn case of IP connection failure, a pop-up window appears on all workstationsthat are logged onto the system. It reads :

Warning: The workstation "X" is unreachable. Reason: No answer from "X".

An e-mail is also sent to axadmin with the same warning.

4.4.2.2 Resynchronization of SystemWhen the connection is recovered you must resynchronize the system. To doso, you must have system administrator rights (axadmin).

1. From the OSM Administration Facilities main menu, select Configuration ->Workstation Management -> Resynchronize Workstation .

2. Select the required station.

3. Click on [ Apply ] , and then on [ Confirm ] .

4. If the IP connection failure occured on an HMI, complete the SectionShutdown USMs in the task Stop OMC-R Application (Section 4.7) .

5. From the A1353 - RA Icon Box, click on the DSM icon.

DSM opens.

6. Select File-> Load Config.The Open window opens.

7. Select dsm.cfg from the list, and click on [ Apply ] .

The DSMUSM window opens.

8. Expand the OMC tree.

In case of IP connection failureon...

Select...

the Master omc3

an Agent the required Agent

9. Right click and select Stop from the pop-up menu.

When the process has completed, the station name appears in blue.

10. Right click on the station name and select Start from the pop-up menu.

When the process has completed, the station name appears in green.

Note: There is a short outage during the stop/start process.

3BK 20903 AAAA PCZZA Ed.22 137 / 238


4.5 Start the SystemTo start the machines in a distributed system:

1. Switch on the Master host

2. After the Master host has booted, switch on all other machines

3. Log in as axadmin on the Master host

4. At the UNIX command prompt, entersudo /alcatel/omc3/osm/script/MF-start

4.6 Start OMC-R ApplicationThere are two methods for starting the OMC-R:

From an UNIX Terminal

From OSM.

4.6.1 From a UNIX Terminal

To start the OMC-R application from a UNIX Terminal:

1. Log on to the Master host.

2. At the UNIX command prompt, entersudo /alcatel/omc3/osm/script/MF-start

The OMC-R starts all the application processes.

4.6.2 From OSM

To start the OMC-R application from OSM:

1. From the OSM Administration Facilities Main Menu, select Administration-> Start OMC3 .

The Start OMC3 window opens.

2. Click [ Apply ] to start the OMC-R.

138 / 238 3BK 20903 AAAA PCZZA Ed.22


4.7 Stop OMC-R Application

The Shut Down option does not give you a chance to change your mind aboutthe request. Use this option with care.

There are two levels possible for shutdown:

Whole OMC-R

Selected USMs.

4.7.1 Whole OMC-R

To stop the OMC-R from the OSM:

1. From the OSM Administration Facilities Main Menu, select Administration-> Global Shutdown .

2. Click on [ Apply ] . The processes shut down immediately and the followingmessage appears.

Done

3. To cancel the shut down of the selected processes, click on [ Cancel ]instead of [ Apply ] .

4.7.2 Shutdown USMs

You shut down the user views on the HMI server for two reasons:

As part of the Preventive Maintenance Task Schedule (recommendedweekly)

In case of an HMI IP link cut.

Important

In the case of an HMI IP link cut, ensure the HMI IP link has been re-establishedbefore you shutdown the USMs.

To shutdown the USMs:

1. From the OSM Administration Facilities Main Menu, select Administration-> Usm Shutdown .

This displays a list of the processes that are running and includes the PIDand user information for each process. Each process has a checkboxnext to it.

2. Each process is already selected when the list appears. Therefore, you mustdeselect the processes that are not to be shut down.

3. If the correct processes are selected, click on [ Apply ] . The processes shutdown immediately and the following message appears.

Done

4. To cancel the shut down of the selected processes, click on [ Cancel ]instead of [ Apply ] .

3BK 20903 AAAA PCZZA Ed.22 139 / 238


4.8 Stop the System

Shut down the Master host last.

To shut down and power off the machines in a distributed system:

1. From OSM, use the procedure Stop OMC-R Application (Section 4.7)using the option Global Shutdown .

2. Log on as root and perform an init 0 on the following servers:

Workstation

HMI

Agent.

3. Log on to the Master host as root and perform an init 0 .

4. Power off all machines.

4.9 Start Application Process from DSMTo start a process that appears in DSM :

1. In the OMC-R iconbox, click on [ DSM ] .

The System Management window appears.

2. Find the process in the tree. You might have to expand the tree.

3. With the pointer over the process name in the tree, click with the right mousebutton and select Start from the pop-up menu.

The process changes color to green. When it is green, it is started.

4.10 Stop Application Process from DSMTo stop a process that appears in DSM :

1. In the OMC-R iconbox, click on [ DSM ] .

The System Management window appears.

2. Find the process in the tree. You might have to expand the tree.

3. With the pointer over the process, click with the right mouse button andselect Stop from the pop-up menu.

The process changes to blue. When it is blue, it is stopped.

140 / 238 3BK 20903 AAAA PCZZA Ed.22


4.11 Process and Platform MonitoringThe following table lists the DSMUSM features of the OMC-R.

Menu Path Description

File->Load Config Updates the displayed information when the file dsm.cfg is chosen.(This is only available for a DSMUSM that is launched from the Masterworkstation.

File->Exit Quits the application.

Navigation->Hosts Displays the host of the OMC-R including associated information (hostname, operating system, status, and CPU load).

Double click on the arrow in the line where a name of a host isdisplayed to view a new window.

General: Displays the periodicity of the CPU, file system, processmonitoring, and general information (operating system, status, andCPU load).

File System: Gives information about the host’s disk occupancy of themonitored partitions. Each line represents a monitored partition anddisplays the partition load. The color corresponds to the state. Thecolor becomes red if the load is too high.

Navigation->Applications Displays the hierarchy of the applications of the OMC-R. Click on anyitem to view more information (e.g. host name, uid, parent, etc.).Actions can be launched by clicking with the right mouse button toview a pop-up menu.

Navigation->Process Displays processes and information relative to processes (e.g. hostname, uid, pid, etc.).

Use the Process View 0 to Process View 3 to display processesusing different filter and sort criteria.

Navigation->Dsm Displays user-defined commands.

Click on [ Execute ] to execute the selected command.

Actions->to launch actions fora selected process

The following actions can be selected:

Start: Starts a process or group of processes.

Stop: Stops a process or group of processes.

Process: Displays process information.

Inspect: Inspects a process.

Defense Selects a Manual Mode or an Automatic Mode.

Automatic mode automatically relaunches a crashed processaccording to the number of lives and the recovery period.

Table 8: DSMUSM Features Description

3BK 20903 AAAA PCZZA Ed.22 141 / 238


4.12 Device ManagementDevice management is used once the installation phase is over and it allowsyou to modify the hardware configuration of the OMC-R without stoppingthe system. To do this, the upgrades are done online. It further allows youto reconfigure existing or new devices as well as to view the devices that arealready configured. Workstations and Printers can be added to or removedfrom the OMC-R. In addition, a default printer can be defined or print jobs canbe deleted. These functions are performed online from the Master workstation.

For new devices, you must provide the IP address of the new device and,if necessary, the route to reach it.

There are two ways of displaying devices, the procedures to view workstationsand printers are described in Section Hardware Inventory (Section 4.1) .

4.12.1 Add Workstations

From the Master workstation, you can add a local or remote workstation to anexisting OMC-R site. The management function does not cover the installationphase of the workstation to be added, only the (re)configuration phase ofthe new and existing workstations.

Note: Make sure that the workstation to be added is not included in the /etc/hosts

file of the Master.

Procedure To add a local or remote workstation to the system:

1. From the OSM Administration Facilities Main Menu, select Configuration-> Workstation Management -> Add Workstation .Enter the followinginformation:

IP address

Select the Type

Agent if the workstation to be added is an Agent Host

HMI if the workstation to be added is an HMI

2. Make sure the workstation details are correct then click on [ Add ] .

3. Click on [ Confirm ] to add the workstation. The following message appears:Success: ’workstation name’ added

Click on [ Cancel ] to return to the previous screen and reselect theworkstation details.

4. To make sure that the workstations have been added, check the workstationinventory (refer to Hardware Inventory (Section 4.1) ).

142 / 238 3BK 20903 AAAA PCZZA Ed.22


4.12.2 Remove Workstations

From the Master workstation, you can delete local or remote workstations.

Procedure To delete a workstation from the system:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Workstation Management -> Delete Workstation .

This displays a list of available workstations, and includes the hostnameand the IP address of the workstation. Each workstation has a checkboxnext to it.

2. Use the checkboxes to select the workstations to be removed.

3. Click on [ Delete ] to remove the specified workstations. This displays a listof the workstations to be removed.

Note: Because you cannot remove the Master workstation, the list of stations doesnot include the Master workstation.

4. Click on [ Confirm ] to delete the workstations. The following messageappears:

Success: ’workstation name’ has been removed

Click on [ Cancel ] to return to the previous screen and reselect theworkstation details.

5. To make sure that the workstations have been removed, check theworkstation inventory (refer to Hardware Inventory (Section 4.1) ).

3BK 20903 AAAA PCZZA Ed.22 143 / 238


4.12.3 Add X Stations

You can add an X Station (Unix or windows operating system) to an existingOMC-R site. The management function does not cover the installation phase ofthe X Station to be added, only the configuration phase of new and existing XStations. The X Station must be installed on the system before it can be added.After it has been added, it must be rebooted before the addition can take effect.

The Unix X Stations can not be declared with the OSM application . Themachine must be installed in Solaris 10 operating system with SUN cd’s andconnected to OMC-R as described hereafter.

The Unix X Stations must be installed/configured with the latest availablehardware/software patches before using it.

4.12.3.1 UNIX X StationsTo add an X Station to the system:

1. As root user, on the Master (or HMI), where the X Station must be connectedperform the following.

Add the following line to the /etc/hosts file:

<X Station IP adddress> <X Station hostname>

Restart the nscd (naming service caching daemon):# svcadm disable -t svc:/system/name-service-cache# svcadm enable svc:/system/name-service-cache

2. Log in as root user on X Station machine.

3. Check if the following path exist: /etc/dt/config .

4. If not, create the subdirectory structure:# cd /etc# mkdir -p dt/config

5. Copy the following file:# cp /usr/dt/config/Xservers /etc/dt/config/Xservers

6. Edit the /etc/dt/config/Xservers file and comment the last line. As aconsequence the file has all lines commented.

7. To set the color depth to 24, refer to: Correcting Monitor Color Problems(Section 8.4.2) .

8. Edit the /etc/inittab file and add the following line:xt:3:respawn:/usr/openwin/bin/Xsun -query <IP address>-nobanner -ac

where <IP address> is the ip address of the Master host (or HMI) where theX Station will be declared .

9. Reboot the machine:# init 6

144 / 238 3BK 20903 AAAA PCZZA Ed.22


4.12.3.2 Windows X Stations

In order to have the Citrix clients operating in full screen mode and/or with awider range of colors (16 bpp or 24 bpp) the last version of ICA Client must beinstalled. The last version of Citrix ICA Client can be downloaded free at URL:http://www.citrix.com/download/ica_clients.asp

The following example describes the installation and configuration of Citrix ICAClient on Windows NT 4.0 and Windows 2000.

Install ICA Windows

Client

To install an ICA Windows Client:

1. Insert the ICA Clients CD-ROM in CD-ROM unit of PC machine.

2. Log in as Administrator user on PC machine.

3. Type the following command:

D:\ICAINST\en\ICA32\disk1\setup.exe

where ’D:\’ is the CD-ROM drive.

4. The Welcome window is displayed.

Click on [ Next ] button.

5. The Citrix License Agreement window is displayed.

Click on [ Yes ] button.

6. The Choose Destination Location window is displayed.


7. The ICA Client Name window is displayed.

In ’ClientName’ field enter the hostname of computer

Click on [ Next ] button

8. The Information window is displayed.

Click on [ OK ] button.

9. Restart the computer.

3BK 20903 AAAA PCZZA Ed.22 145 / 238


Configure/Start ICA

Windows Client

To configure/start ICA Windows Client:

1. Log in as Administrator user on PC.

2. To start the Windows client, select the following menu path:

Start -> Programs -> Citrix ICA Client -> Citrix Program Neighborhood

3. Double click on Add ICA Connection icon.

4. In Add New ICA Connection window click on [ Next ] button:

Enter a description name for the new ICA connection (e.g. OMC-R

host name)

Select TCP/IP for the network protocol

Select the Citrix ’Server’ bullet

From the pop up menu select the select the name of the server

Click on [ Next ] button

5. Click on [ Next ] button.

6. Enter the user name and password for the new connection (if you left blankthis fields, you will be prompted for this information when you open anew connection).


7. Unselect the ’Use Default’ field for ’Window Colors’ and select 256 colors.

Unselect the ’Use Default’ field for ’Window Size’ and select the right sizefor your computer.


8. Click on [ Next ] button.

9. Click on [ Finish ] button.

4.12.4 Remove X Stations

Procedure To delete an X Station from the system:

1. Log in as root user on Master host machine.

2. Open a remote session on the X Station that you want to delete:# ssh <X Station IP address> -l root

where <X Station IP address> is the IP address of the X Station.

Enter the password for root user.

3. Edit the /etc/inittab file and remove the following line:xt:3:respawn:/usr/openwin/bin/Xsun -query <IP address>-nobanner -ac

where <IP address> is the ip address of the Master host (or HMI) wherethe X Station is declared .

4. Reboot the X Station:# init 6

146 / 238 3BK 20903 AAAA PCZZA Ed.22


4.12.5 Add Printers

From the Master workstation, you can add a printer to an existing OMC-R site.The management function does not cover the installation phase of the printer tobe added, only the (re)configuration phase of the new and existing printers.

Procedure To add a printer to the system:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Printer Management -> Add Printer .

2. From the Add Printer menu, specify the name of the printer in the ’Name’field.

3. Specify the IP address of the new printer in the ’IP Address’ field.

4. Click on [ Server ] to view a list of available servers. Select the appropriateserver for the new printer.

5. Make sure the printer details are correct then click on [ Add ] .

6. Click on [ Confirm ] to add the printer. The following message appears:Success: ’printer name’ added

Click on [ Cancel ] to return to the previous screen and reset the printerdetails.

4.12.6 Remove Printers

From the Master workstation, you can delete printers.

Procedure To delete a printer from the system:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Printer Management -> Delete Printer .

This displays a list of available printers, and includes the hostname and theIP address. Each printer has a checkbox next to it.

2. Use the checkboxes to select the printers to be removed.

3. Click on [ Delete ] to remove the specified printers. This displays a list ofthe printers to be removed.

4. Click on [ Confirm ] to delete the printers. The following message appears:Success: ’printer name’ has been removed

Click on [ Cancel ] to return to the previous screen and reset the printerdetails.

3BK 20903 AAAA PCZZA Ed.22 147 / 238


4.12.7 Define Station Default Printer

To define a station default printer:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Printer Management -> Change Station Default Printer .

This displays details of the hostname and ID of the current default printer.

2. Click on the [ Printer ] box to see the list of available printers.

3. Select the default printer and click on [ Apply ] to set the default. Thisdisplays the details of the selected printer.

4. Click on [ Confirm ] to set the selected printer as the default printer. Thefollowing message appears:

Success: printer is now workstation default printer

Click on [ Cancel ] to reselect the default printer.

4.12.8 Define User Default Printer

The newly defined default printer takes effect after the next login.

Procedure To define a user default printer:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Printer Management -> Change User Default Printer .

This displays the current default printer of the user.

2. Click on the [ Printer ] box to see the list of available printers.

3. Select the default printer and click on [ Apply ] to set the default. Thisdisplays the old default printer and the new default printer.

4. Click on [ Confirm ] to set the selected printer as the default printer. Thefollowing message appears:

Success: printer is now user default printer

Click on [ Cancel ] to reselect the default printer.

148 / 238 3BK 20903 AAAA PCZZA Ed.22


4.12.9 Documentation Server Management

4.12.9.1 Declare/ModifyTo declare a remote Documentation Server:

1. From OSM: select Configuration -> Documentation Server Management-> Declare/Modify Documentation Server .

2. Enter the IP address of the documentation server in the ’IP address’ field.

3. Enter the hostname of the documentation server in the ’Hostname’ field.

4. Click on [ Declare ] and [ Confirm ] button.

4.12.9.2 Server AddressTo display the Documentation Server:

1. From OSM: select Configuration -> Documentation Server Management-> Documentation Server Address .

2. The IP address and hostname of the documentation server is displayed.

If no remote documentation server is used the own IP address andhostname is displayed.

4.12.9.3 Undeclare/ResetTo undeclare the remote Documentation Server:

1. From OSM: select Configuration -> Documentation Server Management-> Undeclare/Reset Documentation Server .

2. Select the checkbox and click on [ Reset ] button. Click on [ Confirm ] button.

3. After this action the OMC-R the remote documentation is no more available.

4.12.10 LDAP Hosts Cleanup

This function has been added to delete an entry from the LDAP database. Forexample, when you delete an external Workstation from OSM, it is not removedfrom the LDAP database. So the workstation can not be declared again. Tosolve the problem:

1. From the OSM Administration Facilities Main Menu, select Configuration ->UNIX Network Management -> LDAP hosts cleanup .

2. A list with all the hosts from the LDAP map is displayed. Entries for existingOMC Master/Agent/HMI/Printer are not associated with a checkbox. Allother entries are listed with a checkbox associated.

Select the checkbox of the host(s) to be deleted.

3. Click on [ Delete ] and [ Confirm ] button.

3BK 20903 AAAA PCZZA Ed.22 149 / 238


4.13 Configuration Parameter InventoryThe configuration parameter Inventory option allows the user to look at thecurrent values of the parameters on the system. The Dictionary option displaysdefault values, shows whether or not values can be edited, and providesexplanations of the parameters. This relates only to the application parameters,and not to UNIX or third-party parameters.

The Parameter Inventory displays a list of specified parameters with theircurrent values.

Procedure To view the Parameter Inventory:

1. From the OSM Administration Facilities Main Menu, select Configuration-> Configuration Parameters .

2. From the Configuration Parameters menu, click on the [ ParametersInventory ] button to be able to search for specific parameters.

3. Alternatively, click on the name [ Parameters Inventory ] to view a listof all parameters.

4. To select specific parameters, after you click on the [ Parameters Inventory ]button, fill in the ’Name Matching Pattern and/or Value Matching Pattern’fields.

5. Use the Display Version check box to view the versions of the parameters.

6. Click on [ Search ] to view the parameters specified in the previous step ifyou did not click on the name [ Parameters Inventory ] in step 2.

150 / 238 3BK 20903 AAAA PCZZA Ed.22


4.14 SchedulingFour different tasks can be performed on a scheduled basis. They are:

Cleanup

BSSIM Export

RNIM Export.

ACME

Procedure To schedule one of the above tasks:

1. From the OSM Administration Facilities Main Menu, select Administration-> Scheduling Management -> Scheduling (crontab) .

2. In the left hand box, select the task to schedule from the pop-up menu.

3. Click on [ Go ] .

The task to schedule appears on the right hand side of the screen.

4. Fill in the ’Parameters’ field.The used parameters ca be:

-s <days> to cleanup older files than the given number of days

-t <task> represents the task(s) which will be performed

5. Specify the time of the process in the ’Hour’ field.

6. Select the day(s) when the process is performed in the ’Day’ field.

7. Select the month(s) when the process is performed in the ’Month’ field.


You receive a confirmation listing the task, parameters, time, day, andmonth. Verify that these are correct.

9. Click on [ Confirm ] .

The following message appears:Success: the task has been correctly scheduled

Click on [ Cancel ] to return to the previous screen.

3BK 20903 AAAA PCZZA Ed.22 151 / 238


4.15 Clean UpThere are two types of clean up. Some files are cleaned up automaticallyand some are not. The automatic clean up is configured at installation timeand is not affected by this procedure.

Clean up deletes unused files to save space on disks. It is activated on demandand must be carried out regularly to prevent the system becoming too full.

The clean up procedure only applies to files that can be safely deleted. It allowsyou to select and filter the files to be deleted.

You can clean up the following files:

File type Description

Log Files Logs of all the user commands

Trace Files Trace files of OMC-R applications

PM BSC Files Performance Measurement files

Historical Alarms Archived alarms

Installation Logs Logs generated during OMC-R installation

Import Files Files located in the OMC-R import directory

Export Files Files located in the OMC-R export directory

PMOBS Files Radio Performance Measurement files for the Trace Viewer

PM MFS Files Files containing counters transmitted by the MFS

BSSIM Files BSSIM audit differential reports and BSSIM software reports

IMSI Files Radio Performance Measurement files for the Trace Viewer

ACME Files BSS configuration files

There are three filtering options, of which you can select any combination:

Workstation

Files type

Older than a given number of days.

By default, all files are selected and must be deselected if they are not to beremoved.

152 / 238 3BK 20903 AAAA PCZZA Ed.22


Procedure To perform the clean up:

1. From the OSM Administration Facilities main Menu, select Administration-> Cleanup .

2. Select the workstation to be cleaned up.

3. Click on [ Files Type ] , and select the files to be cleaned up.

4. Specify the age of the files to be cleaned up. In the ’Older than Day(s)’field enter the appropriate number.

Note: PM BSC and PM MFS files, OBS and IMSI files are automatically cleared fromthe system after 4 days. Historical alarms and BSSIM files (audit differentialreports and BSSIM software reports) are automatically cleared after 30 days.They are cleared off overnight.

5. Click on [ Search ] . This displays a list of files that meet the specifications,and includes the file size, and the date when the file was last modified.Each file has a checkbox next to it. By default, all files that are found areselected, so be careful. If no files meet the specifications, the followingmessage appears:

No files found

6. From the list, check the boxes to select the files to be cleaned up.

7. Click on [ Apply ] to remove the selected files. This displays the followingmessage, along with a list of the selected files:

About to clean up the following files:

8. Click on [ Confirm ] to remove the selected files. Click on [ Cancel ] to returnto the previous screen and reselect the files that are to be cleaned up. Thisdisplays a list that shows any files that remain from the search result. If nofiles are selected, the following message appears:

No files found.

3BK 20903 AAAA PCZZA Ed.22 153 / 238


4.16 Broadcast MessagesThe administrator can send a message to all active users. The message opensin a graphical window which pops up on the users’ desktops.

On the OSM, a list of all users currently logged on is provided, with a text fieldwhere the administrator types the message to be sent. The administrator canalso provide a URL instead of the message. In this case, a new HTML browserwindow pops up on the users’ desktops and the corresponding URL is loaded.The users can save or print the received message.

Procedure To broadcast a message to all active users on the system:

1. From the OSM Administration Facilities Main Menu, select Administration-> User Management -> Broadcast Message To Active Users .

This displays a list of all active users including their Login name, theirWorkstation and their location. There is a checkbox against each user.

2. In the field at the top of the screen, type the text of the broadcast message.

3. Deselect any user(s) who should not receive the message.

4. Click on [ Broadcast Message ] to send the message to the selected users.

4.17 Set Date and TimeTo set the date and time:

1. From the OSM Administration Facilities Main Menu, select Administration-> Set Date & Time .

This displays a list of workstations and the current date (in the formatyyyy/mm/dd where yyyy is the year, mm is the month and dd is the date)and time (in the format hh : mm where hh is the hour and mm the minutes)as set for each workstation. There is a checkbox next to each workstation.

2. Select the workstations that are to have a new time and date set. To do this,click on the checkboxes next to the workstation(s).

3. In the ’Year / Month / Day’ field, enter the new date.

4. In the ’Hour : Min’ field, enter the new time.

5. Click on [ Apply ] . The following message appears:Success: the date and time has been set toyyyy/mm/dd hh:mm

Note: If you set the date and time to an earlier date and time the change does nottake place immediately. Instead, the internal clock slows down until the correcttime is reached. For example, a change of one hour to the time and date cantake up to four hours to complete.

If you set the date and time to a later date and time the change takes placeimmediately.

154 / 238 3BK 20903 AAAA PCZZA Ed.22


4.18 Run Multiple OMC-Rs from One HMIThis function allows one or several OMC-Rs to be accessed from one HMI. Theresponse time from the remote OMC-Rs is much quicker than using the sshUNIX command because a Differential X Protocol Compressor is used. Thecompressor takes the messages from the OMC-R and compresses them beforethey are sent over the communication link and uncompresses them at the otherend. The compressor also differentiates redundant and similar information, onlysending the difference over the communication link.

4.18.1 Prerequisites

The following prerequisites apply:

The HMI must be already declared on one OMC-R

The HMI can be connected to another OMC-R as an existing user (same

name) on both machines.

The user used to connect to the OMC-R, is declared in the OMC-Rapplication (not only Unix user).

4.18.2 Set UNIX Parameters on One OMC-R

Procedure To set the UNIX parameters on one OMC-R (repeat this procedure for eachOMC-R):

1. Verify the HMI can connect to the OMC-R (e.g. use ping).

2. At the HMI, as root edit the /etc/hosts file.

3. Add the IP address and OMC-R name to /etc/hosts , for example:172.25.129.12 omcr2

4. Declare the user from the HMI (used to connect to the OMC-R) as externaluser on the OMC-R, refer to Add Secure External Workstation (Section4.24.1) .

5. As root on the OMC-R, at a command prompt, change user access rightson file /tmp/.X11-unix :

chmod 777 /tmp/.X11-unix

This must be done the first time you are setting up the parameters or whenyou reboot the OMC-R.

6. To keep the access rights to .X11 - unix when the OMC-R is rebooted:

Create file /etc/rc3.d/S80chmod

Add the following lines:

sleep 10

/usr/bin/chmod 777 /tmp/.X11-unix

Save file S80chmod and close.

At a command prompt enter:chmod a+x /etc/rc3.d/S80chmod

3BK 20903 AAAA PCZZA Ed.22 155 / 238


4.18.3 Connection Procedure

To connect to one OMC-R (repeat this procedure each time you want to connectto an OMC-R. To create a shortcut, see Creating a Shortcut, found below):

1. Log in on the HMI as the user with access to the OMC-R.

2. From a command line on the HMI, enter:xhost <omcr>

where <omcr> is the OMC-R name already declared in the /etc/hosts

in the step (3) from the Procedure paragraph.

3. Enter:/alcatel/omc3/iconbox/script/run_remote_iconbox<omcr>

Replace <omcr> with the name of the OMC-R you want to connect to.

The iconbox of the OMC-R opens.

4. From the remote icon box, you can access all the functions of the OMC-Ravailable to axadmin user.

5. As the xhost command is an insecure method and it should be used withcare, after the job is done, the name of the OMC-R must be removed fromthe list allowed to connect to the X server:

xhost - <omcr>

4.18.4 Creating a Shortcut

To avoid having to type in the UNIX command each time, you can create anicon shortcut in the UNIX CDE environment. However, after launching theshortcut for the first time, the name of the OMCR remains in the list allowed toconnect to the X server. This is an insecure method and it should be usedwith care. After running the application, the OMC-R name from the list shouldbe removed, following the step (5) from the Connection Procedure (Section4.18.3) paragraph.

Note: This procedure assumes you are using the CDE environment provided onHPUX. If you are using a different environment, read the documentationprovided with that environment.

1. On the front panel of the HMI, click on [ Application Manager ] .

Figure 4: Application Manager Icon

The Application Manager directory opens.

2. Click on [ Desktop_Apps ] .

156 / 238 3BK 20903 AAAA PCZZA Ed.22


3. Click on [ Create Action ] .

The Create Action window opens.

Figure 5: Example Create Action Window

4. Enter the name of the icon in the ’Action Name’ field.

5. Enter the following in the ’Command’ field:/bin/csh -c "xhost <omcr> ;/alcatel/omc3/iconbox/script/run_remote_iconbox<omcr> "

Replace <omcr> with the name of the OMC-R you want to connect to.

6. To change the icon graphic to hexagons:

Click on [ Find Set ]

Double-click on /etc/dt/appconfig/icons/C

Select an icon

Click on OK.

7. Enter help text in the ’Help Text’ field.

8. Change Window type to: Terminal (Auto Close)

3BK 20903 AAAA PCZZA Ed.22 157 / 238


9. Select File -> Save .

The action is saved in your home directory.

10. In your home directory, double-click on the action icon you created andverify it works.

11. For easy access, drag and drop the action icon into any directory or into anymenu in the front panel.

4.19 Logs ManagementThe Logs Management module allows you to view actions performed by users.Logs Management includes the following tasks:

View Logs (Section 4.19.1)

Logs Merge on Demand (Section 4.19.2) .

4.19.1 View Logs

Logs are recorded for actions performed by users. One log is created for eachsubsystem, for example one log for RNUSM and one log for DCN. Logs areuseful to monitor user actions and to pin-point when problems occur.

Three methods exist for viewing user logs. You can use the Log Viewer(Full)logs viewer, the Log Viewer(Own) logs viewer (to view more restrictive log files),or use a text editor to view the UNIX log files.

4.19.1.1 Log Viewer(Full) Logs ViewerTo view logged actions for a period of up to eight days:

1. From the A1353 -RA Icon Box, click on the [ Log Viewer(Full) ] icon.

The Full MRT window opens.

2. Select Log Viewer(Full) Message Retrieval Tool Main Menu ->LogsViewer .

3. From the Process drop-down menu, select the name of the component onwhich you want to generate a log report.

You can only select one component.

4. Enter a Login name to generate a report on a particular user.

By default, all users are included.

5. Enter the workstation name of the Master or the HMI.

6. Enter the date and time from which to generate a log report, and the dateand time up to which the log report is generated.

The date is formatted as year/month/day/time. For example, 2000/10/0300:00:00.

By default, a report is generated dating from midnight seven days previously,and the last date of log merge on demand is displayed. This default value isalso a maximum value: a report cannot be generated dating from more thanmidnight seven days previoulsy.

7. In the Text Search box, enter a keyword to generate a log report of certainactions.

For example, the word Audit will generate a log report of all audits conductedon the subsystem.

158 / 238 3BK 20903 AAAA PCZZA Ed.22


8. Check the Show Data Block box to view detailed recorded logs of hardwarechanges, or SC changes in RNUSM in ASN.1 format.

9. Click on [ Apply ] to validate the selected log report parameters.

The log report opens.

4.19.1.2 Log Viewer(Own) Logs ViewerTo view more restrictive logged actions for a period of up to eight days (the nameof the machine to which you are currently logged on is automatically entered):

1. From the A1353 -RA Icon Box, click on the [ Log Viewer(Own) ] icon

The Restrict MRT window opens.

2. Select Log Viewer(Own) Message Retrieval Tool Main Menu ->LogsViewer .

3. From the Process drop-down menu, select the name of the component onwhich you want to generate a log report.

You can only select one component.

4. Enter the workstation name of the Master or the HMI.

5. Enter the date and time from which to generate a log report, and the dateand time up to which the log report is generated.

The date is formatted as year/month/day/time. For example, 2003/10/0300:00:00.

By default, a report is generated dating from midnight seven days previously,and the last date of log merge on demand is displayed.

By default, a report is generated dating from midnight seven days previously,and the last date of log merge on demand is displayed. This default value isalso a maximum value: a report cannot be generated dating from morethan seven days previoulsy.

6. In the Text Search box, enter a keyword to generate a log report of certainactions.

For example, the word Audit will generate a log report of all audits conductedon the subsystem.

7. Check the Show Data Block box to view detailed recorded logs of hardwarechanges, or SC changes in RNUSM in ASN.1 format.

8. Click on [ Apply ] to validate the log report parameters selected.

The log report opens.

4.19.1.3 View UNIX Log FilesLogs are located in the following directory:

/alcatel/var/maintenance/log

Any text editor can be used to view the logs, for example vi or dtpad.

3BK 20903 AAAA PCZZA Ed.22 159 / 238


4.19.2 Logs Merge on Demand

4.19.2.1 Log Viewer(Full) Logs Merge on DemandTo extract and merge daily logged actions stored in the log files:

1. From the A1353 -RA Icon Box, click on the [ Log Viewer(Full) ] icon.

The Full MRT window opens.

2. Select Log Viewer(Full) Message Retrieval Tool Main Menu ->LogsMerge on demand .


A message appears displaying the success or failure of the logs mergegeneration.

4.19.2.2 Log Viewer(Own) Logs Merge on DemandTo extract and merge daily logged actions stored in the log files:

1. From the A1353 -RA Icon Box, click on the [ Log Viewer(Own) ] icon.

The Restrict MRT window opens.

2. Select Log Viewer(Own) Message Retrieval Tool Main Menu ->LogsMerge on demand .


A message appears displaying the success or failure of the logs mergegeneration.

160 / 238 3BK 20903 AAAA PCZZA Ed.22


4.20 Change NMCTo change the NMC or change the NMC IP address that is declared at theOMC-R, you must:

Find AETITLE, Pres, Ses, IP of NMC

Undeclare the current NMC

Declare the new NMC (or new NMC IP address)

Restart q3im application.

Note: This procedure makes use of the DSM application to stop and restartapplication processes such as the OMC-R. For information on the use of DSM,refer to A1353-RA Getting Started, System Management window.

4.20.1 Find NMC Parameters

Procedure 1. Open a UNIX terminal on the OMC-R and log on as root .# cd /alcatel/omc3/q3im/script# ./displayNmc.pl

All the declared NMCs are displayed.

2. Note the parameter values specific to your NMC because you must usethem when you undeclare the NMC.

4.20.2 Stop q3im Applications

To stop the q3im applications, use the procedure Stop Application Processfrom DSM (Section 4.10) .

3BK 20903 AAAA PCZZA Ed.22 161 / 238


4.20.3 Undeclare Current NMC

Note: To perform these operations you must be logged in at UNIX level as a root user.

Note: To use the script undeclareNmc.pl, you must have noted down the:

AETITLE (e.g., 1.2.3.4.4.0)

PSEL (e.g., 0601)

SSEL (e.g., 0x0504)

TSEL, if it appears in the example, is left blank

NSAP is the IP Address (e.g. 139.246.135.33).

The example values above are used in the example below.

Procedure To run script undeclareNmc.pl:

1. Open a UNIX terminal on the OMC-R and log on as root.

2. Change to the following directory:/alcatel/omc3/q3im/script

3. Run the script using the following syntax:./undeclareNmc.pl -form2 AETITLE -rfc1006PSEL,SSEL,TSEL,IPADDRESS

where the parameters in italics are replaced by real values, for example:./undeclareNmc.pl -form2 1.2.3.4.4.0 -rfc10060601,0x0504,,139.246.135.33

The NMC is now undeclared.

162 / 238 3BK 20903 AAAA PCZZA Ed.22


4.20.4 Declare New NMC

Note: An NMC is declared only once, at OMC installation.

4.20.4.1 PrerequisitesTo declare the new NMC or change the IP address of the existing NMC, youmust first obtain the following information from the NMC personnel:

Value of the AETITLE of the NMC parameter (e.g., 1.2.3.4.4.0)

Value of the PSEL parameter (e.g., 0701)

Value of the SSEL parameter (e.g., 0x0503)

Value of TSEL (in the example it is left blank)

Value of the IP address of the NMC (e.g., 139.246.135.66).

The example values above are used in the example below.

4.20.4.2 ProcedureTo declare the NMC:


2. Change to the following directory:/alcatel/omc3/q3im/script

3. Run the script using the following syntax:./declareNmc.pl -form2 AETITLE -rfc1006PSEL,SSEL,TSEL,IPADDRESS

where the parameters in italics are replaced by real values, for example:./declareNmc.pl -form2 1.2.3.4.4.0 -rfc10060701,0x0503,,139.246.135.66Are you sure to declare this NMC(y/n)?

Answer with [ y ] .Do you want to start Q3IM now (y/n)?

Answer with [ y ] .

The NMC is now declared.

4.21 List NMC and OMC Network IdThis task displays a list of NMCs, ALMAVISION NMCs and OMC network Ids.

From the OSM Administration Facilities Main Menu, select NMC Management-> List NMC & OMC Network Id .

This displays a list and a table of NMC parameters. The list shows the OMCNode Identifier, the NMC AETitle and the ALMAVISION NMC for each NMC.The table shows the NMC Form type and Connection Type, and the PSAPS,SSAPS, TSAPS and NSAPS for the NMC.

3BK 20903 AAAA PCZZA Ed.22 163 / 238


4.22 Alarm Sublist and Filter Management

4.22.1 Alarm Sublists

Alarm sublists gather sets of alarms that are graphically displayed in ASUSM.Using filters, you define which alarm is put in a sublist. There are two sublistsavailable: the original default sublist delivered with ASUSM (Old), and a newsublist (New).

You can also define your own alarm sublist. However, alarm sublists can not bemerged. You must choose one of the three according to your network needs:

Old sublist

New sublist

Self-defined sublist.

The Old sublists, delivered as the default with ASUSM, are:

Cells

BTSs

BSCs

Transmission

EXTERNALs

MAIN ALARM LIST

DEFAULT ALARM LIST

INDETERMINATE.

Note: The AS:Histo Alarms Old sublists do not contain the INDETERMINATE sublist.

164 / 238 3BK 20903 AAAA PCZZA Ed.22


The New sublists are:

Default_220V_BTS

Default_220V_BSC

MAIN ALARM LIST

DEFAULT ALARM SUBLIST

EXTERNALs

Equipment_BSS

Transmission_BSS

Configuration_BSS

External_BSS

QoS_BSS

Equipment_MFS

Transmission_MFS

Configuration_MFS

External_MFS

NACK_CLR

ACK_NCLR

INDETERMINATE.

Note: The AS:Histo Alarms New sublists do not contain the NACK_CLR andACK_NCLR sublists.

4.22.2 Alarm Sublist Filters

You use filters to define which alarm is put into an alarm sublist. As with alarmsublists, there are two filter lists available: the original default filters deliveredwith ASUSM (Old), and a set of new filters (New). You can also define yourown filters.

Unlike alarm sublists, filters can be merged. You can add the New filters to thedefault filters, as well as creating your own filters.

3BK 20903 AAAA PCZZA Ed.22 165 / 238


For the AS:Current Alarms, the Old filters, delivered as the default withASUSM, are:

IndefExceptQOS

acknowledged

cleared

errors

indeterminate

matchAll

matchNone

not Acknowledged

not Cleared

not Reserved

reserved.

For the AS:Histo Alarms, the Old filters, delivered as the default with ASUSM,are:

Bsc

Cell

Default

ackAndCleared

autoPurged

errors

external

imRemoved

invalidated

manuallyPurged

matchAll

matchNone

overflowed

synchronized

transmition.

166 / 238 3BK 20903 AAAA PCZZA Ed.22


For the AS:Current Alarms, the New filters are:

Equip_BSS

IndefExceptQOS

ack_nclr

acknowledged

cleared

config_BSS

config_MFS

default_220_bsc

default_220_bts

equip_MFS

errors

external_BSS

external_MFS

indeterminate

matchAll

matchNone

nack_clear

notAcknowledged

notCleared

notReserved

qos_BSS

reserved

trans_BSS

trans_MFS.

3BK 20903 AAAA PCZZA Ed.22 167 / 238


For the AS:Histo Alarms, the New filters are:

Equip_BSS

External

IndefExceptQOS

acknowledged

cleared

config_BSS

config_MFS

default_220_bsc

default_220_bts

equip_MFS

errors

external_BSS

external_MFS

indeterminate

matchAll

matchNone

notAcknowledged

notCleared

notReserved

qos_BSS

reserved

trans_BSS

trans_MFS.

4.22.3 Pre-Defined Aging Schemes

In the AS:Current Alarms, some actions are performed periodically if theseverity of an alarm is indeterminate:

Every 10 minutes, all alarms present in the Current Alarm List since 5minutes are automatically acknowledged

Daily, all alarms acknowledged since 10 minutes are automatically purged.

168 / 238 3BK 20903 AAAA PCZZA Ed.22


4.22.4 Change Default Alarm Sublist

From the Master workstation, you can change the default alarm sublist,delivered with ASUSM, to the New alarm sublist. When you create a new user,the New sublist is the default. To change the default of existing users, completethe task Change Default for Existing Users (Section 4.22.6) .

Changing the default to New also adds the New filters.

To perform these actions you must be logged in at the UNIX level as root user.

Procedure To change the default sublist to the New sublist and add the New filters:


2. Change to the following directory:/alcatel/omc3/as/tools/script

3. Run the script using the following text:changeDefault NEW

4. Quit ASUSM and restart.

The new alarm sublist and filters are now the default for all new users youdeclare.

4.22.5 Retrieve Original Default Alarm Sublist

To retrieve the original default alarm sublist:



3. Run the script using the following text:changeDefault OLD


The original default alarm sublist and filters are now the default for all newusers you declare.

3BK 20903 AAAA PCZZA Ed.22 169 / 238


4.22.6 Change Default for Existing Users

4.22.6.1 Individual UsersTo change the default alarm sublist to the New alarm sublist and add the Newfilters for an individual existing user:



3. Run the script using the following text:InstallDefault -user -<userName>


The default alarm sublist and filters for userName are changed.

4.22.6.2 All UsersTo change the default alarm sublist to the New alarm sublist and add the Newfilters for all existing users:



3. Run the script using the following text:InstallDefault -all


The default alarm sublist and filters for all users are changed.

4.22.7 Retrieve Original Default for Existing Users

The original default alarm sublist and filters for userName are retrieved.

The original default alarm sublist and filters for all users are retrieved.

4.22.7.1 Individual UsersTo retrieve the original default alarm sublist for an individual existing user:



3. Run the script using the following text:InstallDefault -user -<userName> -recover


4.22.7.2 All UsersTo retrieve the original default alarm sublist for all existing users:



3. Run the script using the following text:InstallDefault -all -recover


170 / 238 3BK 20903 AAAA PCZZA Ed.22


4.22.8 Add Alarm Sublist Filters

From the Master workstation, you can add the New alarm sublist filters to yourASUSM configuration, without changing the original default alarm sublist. Whenyou create a new sublist, more defined filters are available.

To perform these actions, you must be logged in at the UNIX level as root user.

4.22.8.1 Individual UsersTo add the New alarm sublist filters for an existing individual user:



3. Run the script using the following text:addDefaultFilter -user <userName>


The New alarm sublist filters, with the original default alarm sublist, areavailable to userName.

The New alarm sublist filters, with the original default alarm sublist, areavailable to all users.

4.22.8.2 All UsersTo add the New alarm sublist filters for all existing users:



3. Run the script using the following text:addDefaultFilter -all


4.23 Navigate in a New Mozilla Window1. The present Mozilla window is overwritten, when a navigation to Mozilla

is performed from an USM application (ex. open a report from an USMapplication).

2. To have a window for each Mozilla application, started from the iconboxor by navigation from an USM application, install as root the followingpackage from CD3 :

# /usr/sbin/pkgadd -d /cdrom/cdrom0/OMC3 OMCGmbwin

This will copy the multiBrowserWindow file in/alcatel/var/share/netconf .

3. To restore the initial behavior (overwritten Mozilla window), remove thepackage:

# /usr/sbin/pkgrm OMCGmbwin

This will delete the multiBrowserWindow file from/alcatel/var/share/netconf .

3BK 20903 AAAA PCZZA Ed.22 171 / 238


4.24 Secure External Workstation and UserThe external workstation is a Sun (Solaris) machine.

The remote access to the Master is performed with ssh , no .rhosts filemust be modified.

To be able to perform ssh, the following software is installed on the externalworkstation:

HTTP browser

SSH/SSL environment set (openssh and openssl packages).

4.24.1 Add Secure External Workstation

1. Log in as external user on the external workstation.cd ~/.sshssh-keygen -t rsa -b 768 -N ""

The ~/.ssh/id_rsa.pub file was generated.

2. As root user update /etc/hosts file (if not already done), add the following line:

<Master IP address> <Master hostname>

3. Start HTTP browser (Mozilla) on the external workstation.

Connect to the OSM interface on the Master where the login will beperformed. In the Location field type: http://<Master hostname>/osm/admin.

Connect to OSM as axadmin user, default password omc3 .

4. From OSM Administration facilities follow the menu path: Configuration-> Secure External Workstation Management -> Add Secure ExternalWorkstation .

5. Update the following fields:

Login name : user name, as which the external user can connect

to the Master

External user : name of the user from the external workstation

External WS IP : IP address of the external workstation

External WS name : hostname of the external workstation

Upload key file : click on [ Browse ] button and select the previousgenerated ~/.ssh/id_rsa.pub file. Click on [ OK ] button.

Click on [ Add external user ] and [ Confirm ] button.

4.24.2 Secure External Workstation Inventory

To display the secure external workstations and users, from OSM AdministrationFacilities Main Menu, select Configuration -> Secure External WorkStationManagement -> Secure External WorkStation Inventory .

172 / 238 3BK 20903 AAAA PCZZA Ed.22


4.24.3 Delete Secure External Workstation

To delete a secure external workstation and user:

1. From the OSM Administration Facilities Main Menu, select Configuration ->Secure External WorkStation Management -> Delete Secure ExternalWorkstation .

2. Select the checkbox of the secure external workstation/user to be deleted.

3. Click on [ Delete ] and [ Confirm ] button.

3BK 20903 AAAA PCZZA Ed.22 173 / 238


4.25 A1353-RA MRTG View

4.25.1 SNMP Collector

The current resource usage of the boards of the MFS (both A9135 and A9130MFS Evolution) and of the A9130 BSC Evolution can be reported using thestandard SNMP protocol.

To collect and display the data, the SNMP Manager needs a configurationfile which describes the location of the agent, the identification of objectsto be queried, the formatting instructions, etc. The SNMP Manager mustuse a ‘SNMP password’ also known as ’Community String’ to access to theSNMP agent on Network Element. This Community String is unique for allthe SNMP agents running on the equipment and can be updated during thelifetime of the BSC/MFS.

To enable or disable the collector for MRTG use the procedure described inBSS Configuration Handbook, section Enable/Disable Collector .

The Community String defined at OMC side must be the same as the one

defined at BSC or MFS side during installation. To update the CommunityStrings at OMC side, perform the tasks described in BSS Configuration

Handbook, section Enable/Disable Collector .

4.25.2 Main Page

MRTG (Multi Router Traffic Grapher) is a tool to monitor the MFS and A9130BSC Evolution resources in real-time.

Figure 6: A1353-RA MRTG Main View

174 / 238 3BK 20903 AAAA PCZZA Ed.22


From the A1353RA MRTG main window, select the appropriate equipment onwhich you want to visualize the traffic load.

Depending on your previous choice, a new window is opened displaying a list ofeither the declared MFS(s), or the declared A9130 BSC Evolution. The listcontains only the MFS(s) or the A9130 BSC(s) Evolution with the ’Enablecollection’ function selected, and the value for ’Community string’ set to OMC

The ’Community string’ value can be changed on both OMC-R and MFS side.

Figure 7: A1353-RA MRTG MFS View

Selecting an MFS or an A9130 BSC Evolution, the "MRTG Index Page"is opened.

3BK 20903 AAAA PCZZA Ed.22 175 / 238


4.25.3 MRTG Index Page

4.25.3.1 MFS MRTG Index PageThe following graphs are displayed in the MFS MRTG Index Page:

Memory & SWAP Usage and Allocation Failure

The memory and swap information is reported by the following counters (allvalues for sizes and usage are reported in kB):

Total RAM

Total virtual memory RAM and SWAP

Total SWAP

Virtual memory usage

SWAP usage

Virtual memory allocation failure

SWAP allocation failure.

The total values are static and are displayed on the top of the report. Theyare collected only at the configuration of the file creation.The virtual and swap memory is displayed as percentage in one graph.The allocation failure values for virtual and swap memory are displayedon the same graph.

176 / 238 3BK 20903 AAAA PCZZA Ed.22


OMC-MFS, MFS LSN1 and MFS LSN2 traffic and errorsThe MFS active control station monitors three network cards: one for O&Mlink with OMC-R, and two for internal communication.There are two types of measurements for network activity which aremonitored for each card: bytes sent or received on an interface, and theerrors for the sent or received packets.For each card, there are two graphs, one for traffic and the other one forerrors, each of it contains two lines, for incoming and outgoing traffic.

CPU usage:

idle CPU time - time that the system spent in the idle task

nice CPU time - time that the system spent in user mode with low priority

system CPU time - time that the system spent in system mode

user CPU time - time that the system spent in user mode.

The average CPU load is reported every 5 minutes.

3BK 20903 AAAA PCZZA Ed.22 177 / 238


Disk Usage for different partitionsThe disk usage monitoring is done through computed counters for thepercentage of the disk usage.

The values from the MFS are updated every 5 minutes.

The scale interval for daily graphs is two hours. The current moment isdisplayed on the left, and the past measurements are displayed on the rightof the graphic.

178 / 238 3BK 20903 AAAA PCZZA Ed.22


4.25.3.2 A9130 BSC Evolution MRTG Index Page

3BK 20903 AAAA PCZZA Ed.22 179 / 238


The following graphs are displayed in the A9130 BSC Evolution MRTG IndexPage:

CPU Load:

idle CPU time - time that the system spent in the idle task

nice CPU time - time that the system spent in user mode with low priority

system CPU time - time that the system spent in system mode

user CPU time - time that the system spent in user mode.

The average CPU Load is reported every 5 minutes.

Memory Usage: indicates the amount of memory that is used. It is

expressed in number of 1024 bytes.

Swap Usage: indicates the amount of swap memory that is used. It isexpressed in number of 1024 bytes.

Network traffic:

Ethernet 0 Traffic: indicates the total number of bytes received and

sent on the Ethernet 0 interface

Ethernet 0 Traffic Errors: indicates the number of packets that contained

errors received on the Ethernet 0 interface, or the number of packets thatcould not be sent on the Ethernet 0 interface because of errors

Ethernet 1 Traffic: indicates the total number of bytes received and

sent on the Ethernet 1 interface

Ethernet 1 Traffic Errors: indicates the number of packets that contained

errors received on the Ethernet 1 interface, or the number of packets thatcould not be sent on the Ethernet 1 interface because of errors.

Disk Usage, for the following three partitions:

/ partition, with counters reported on 25.2.3.1.x.1

/common partition, with counters reported on 25.2.3.1.x.5

/alternate partition, with counters reported on 25.2.3.1.x.6 when it is

mounted, otherwise the counters are not available.

The Disk Usage report is expressed in number of 4096 bytes. It contains astatic part which is built at configuration phase, regarding the volumename and its size in MB.Note that the / and /alternate partitions are exchanged during a MajorSW replacement.

Failed allocation requests for the / , /common , and /alternate partitions,indicating the number of allocation requests that have failed for the

corresponding partition.

180 / 238 3BK 20903 AAAA PCZZA Ed.22


4.25.4 Detailed Statistics

The daily, weekly, monthly, and yearly graphs are displayed after clicking on thewanted graph from the MRTG Index Page.

Green : OMC-MFS Traffic

Gray : Peak OMC-MFS Traffic

Figure 8: Detailed Statistics MFS View

3BK 20903 AAAA PCZZA Ed.22 181 / 238


Green : OMC-MFS Traffic

Gray : Peak OMC-MFS Traffic

Figure 9: Detailed Statistics A9130 BSC Evolution View

182 / 238 3BK 20903 AAAA PCZZA Ed.22


4.26 Increase the Trace LevelApply this paragraph to increase the trace level, for a limited time period.

1. To increase the trace level, start as root the following script:# cd /alcatel/omc3/osm/script/# ./TraceDebug.pl -c start -s <trace type> -h<workstation>

<trace type> can be:

mfs for mfsim and mfsusm traces

rn for rnim, rnusm and rncmd traces

bss for bssim, bssusm, bsscmd and bsscomm traces

all for all types of traces

<workstation> is the hostname of the machine (Master, HMI or Agent)where the traces are taken.

The script will display a list with all the modified trace configuration files.

2. To restore the normal trace level, perform the following as root :# cd /alcatel/omc3/osm/script/# ./TraceDebug.pl -c stop -s <trace type> -h<workstation>

If traces have been taken, a tar.gz file is created in the/alcatel/var/share/AFTR/MISC directory.

The filename has the formatOSM_TRACE_DEBUG_<workstation>.<number>.tar.gz

The original trace configuration files are restored.

3BK 20903 AAAA PCZZA Ed.22 183 / 238


4.27 Hardware InventoryThis action can be performed on Master, Agent or HMI.

To display the hardware inventory perform as root :# /usr/local/bin/hw_inquire.sh | tee <log_file>

The output will be written to <log_file> .

The following is displayed by the script:

system diagnostic information

amount of disk space occupied by the file systems

swap space information

disk devices and disk arrays (if they exists)

tape devices

FC-AL devices (on Sun Fire systems)

list of SCSI devices

network interfaces

network routing configuration

oflcf.in file

If this script is started on the Master, the inventory for all connected HMIs andAgents (in case of XLarge) is also displayed.

4.28 Security Impact on the A1353-RA Remote InstallationIf the installation of an A1353-RA cannot be started from the internal CD-ROMdrive, a remote installation can be performed.

In this case, a remote machine with a working CD-ROM drive can be used.Also, two services must be enabled on the remote machine: AUTOMOUNTand BOOTPARAMD .

But, for security reasons, these services can be stopped.

If these services are stopped on the remote machine, the A1353-RA installationcannot be done from this remote machine.

The following sections describe the checking, enabling and disabling procedurefor these services.

184 / 238 3BK 20903 AAAA PCZZA Ed.22


4.28.1 AUTOMOUNT Service

AUTOMOUNT service must be enabled if the remote installation of anA1353-RA is performed from this machine.

4.28.1.1 Check the Service StatusTo check if the AUTOMOUNT service is enabled, enter the following command:

svcs | grep autofs

If the command has no output, the service is stopped.

If the command result is:online <time> svc:/system/filesystem/autofs:default

where <time> is the date or time when the service was started, the service isenabled.

4.28.1.2 Service DisableLogin as root user.

If the AUTOMOUNT service is enabled, enter the following command todisable the service:

# svcadm disable svc:/system/filesystem/autofs

Check that the service is stopped.

4.28.1.3 Service EnableLogin as root user.

If the AUTOMOUNT service is disabled, enter the following command toenable the service:

# svcadm enable svc:/system/filesystem/autofs

Check that the service is started.

3BK 20903 AAAA PCZZA Ed.22 185 / 238


4.28.2 BOOTPARAMD Service

BOOTPARAMD service must be enabled if the remote installation of anA1353-RA is performed from this machine.

4.28.2.1 Check the Service StatusTo check if the BOOTPARAMD service is enabled, enter the following command:

svcs | grep bootparams

If the command has no output, the service is stopped.

If the command result is:online <time> svc:/network/rpc/bootparams:default

where <time> is the date or time when the service was started, the service isenabled.

4.28.2.2 Service DisableLogin as root user.

If the BOOTPARAMD service is enabled, enter the following command todisable the service:

# svcadm disable svc:/network/rpc/bootparams

Check that the service is stopped.

4.28.2.3 Service EnableLogin as root user.

If the BOOTPARAMD service is disabled, enter the following command toenable the service:

# svcadm enable svc:/network/rpc/bootparams

Check that the service is started.

4.29 Network Information SummaryA script is available at the OMC-R that provides a set of network information.

The script is used in automatic and manual mode.

Automatic In the automatic mode, the script is scheduled in crontab by axadmin everyfirst day of the month (01:00AM).

The network_info_A1353RA_<hostid>.zip output file is saved in/alcatel/var/share/netconf/ directory.

Manual In the manual mode, perform the following steps:

1. Perform File Management for BTS RI files (BTS RI clean-up).

2. Open a terminal window.

3. Log in as axadmin user.

4. Launch the script:cd /alcatel/omc3/osm/script/./network_info.pl -demand

5. The network_info_A1353RA_<hostid>.zip output file is saved in/alcatel/var/share/netconf/ directory.

186 / 238 3BK 20903 AAAA PCZZA Ed.22


The needed information is retrieved from ACIE export directory, RI files,oflcf.in file, A1353RA signature file and directly from the operating system.In case of automatic usage, the information contained in the output file canbe false in case of Evolium BTSs and MFS Evolution. To have accurateinformation, all BTS and MFS Evolution RI files should be available and theBTS/MFS Evolution File Management performed.The Evolium BTSs which do not belong to one category defined in the outputfile (i.e. BTS-A9100_G3-Medi-Indoor) will be categorized as unknown.

4.30 DLS Periodic Check ToolDLS Periodic Check is a tool that periodically checks the DLS inconsistency forthe BSCs attached to the OMC-R. It will only check the B9 BSCs.

The script, named launch_dpck , is located in /alcatel/omc3/osm/script/ .It is scheduled in axadmin’s crontab every night.

By default the crontab line is commented. To activate the feature, the commentcharacter must be removed from the crontab file.

The tool produces unitary check reports in/alcatel/var/share/DPCK/report/ named<BSS_Name>_<Date><Time>.log.old where <Bss_Name> is the friendlyname of the BSC used at OMC-R

The tool also generates a synthetic report in /alcatel/var/maintenace/log .The report is named DPCK_<Date>.old.log .

Unitary reports as well as synthetic reports are automatically archivedin/alcatel/var/maintenace/hist .

The tool can be used, for example, to check the DLS inconsistencies, beforeperforming a BSS Software Replacement or a MLU.

4.31 SE3510 Disk Replacement

Failed Disk Check 1. Open sccli tool:sccli

2. Check logical drive status like in the followin example:show logical-drive

LD LD-ID Size Assigned Type Disks Spare Failed Status--------------------------------------------------------------------ld0 7A5D6893 136.23GB Primary RAID5 3 0 0 GoodWrite-Policy Default StripeSize 32KBld1 6E7757C1 136.23GB Primary RAID5 3 0 0 DegradedWrite-Policy Default StripeSize 32KB

Write down the logical drive index (’LD’) of the logical drive status Degraded

(i.e. ’Id1’).

3BK 20903 AAAA PCZZA Ed.22 187 / 238


Identify the Failed Disk 1. From sccli prompt launch:show disk

A table like the one in the following example is displayed:Ch Id Size Speed LD Status IDs Rev--------------------------------------------------------------------...2 4 N/A N/A ld1 BAD FUJITSU MAP3735F SUN72G 1501

Identify the disk with one of the following status values: BAD, ABSENTorMISSING. Write down the disk’s channel (’Ch’) and ’Id’

2. For the failed disk set LED on in order to be physically identified:set led disk <Ch>.<Id> on

The LED of the failed disk is now amber.

Physical Disk

Replacement

Both steps must be done according to SUN’s procedures.

1. Remove the failed disk drive.

2. Install the new disk drive.

Wait 1 min. for the disk to be initialized.

Rebuild the Affected

Logical Drive

1. Check logical presence of replaced disk. From sccli prompt launch:show disk

Check for the disk with the channel and Id previously noted that the ’Status’is USEDlike in the following example:Ch Id Size Speed LD Status IDs Rev--------------------------------------------------------------------...2 4 68.37GB 200MB NONE USED FUJITSU MAP3735F SUN72G1501S/N 000448Q0H44UWWNN 500000E010C0DE90

2. Start rebuilding for the affected logical driverebuild <LD>

where ’LD’ is the logical drive index.

188 / 238 3BK 20903 AAAA PCZZA Ed.22


Logical Drive Check 1. View logical drive rebuilding progressshow logical-drive rebuild

2. View all logical driveshow logical-drive

Check that the ’Status’ for all drives is Good like in the following example.LD LD-ID Size Assigned Type Disks Spare Failed Status--------------------------------------------------------------------ld0 7A5D6893 136.23GB Primary RAID5 3 0 0 GoodWrite-Policy Default StripeSize 32KBld1 6E7757C1 136.23GB Primary RAID5 2 0 1 GoodWrite-Policy Default StripeSize 32KB

3. For replaced disk set LED offset led disk <Ch>.<Id> off

The LED of the replaced disk should be green.

4.32 Activate Multiple LAN FeatureThe multiple LAN feature is used to split the network traffic in two:

OMC network traffic (between Master/Agent/HMI/workstation).This can be configured either by adding a new Ethernet board, or a usingmultiple IP addresses on the same port (if the HW allows it).Each Master/Agent/HMI will have two different IP addresses and twodifferent hostnames (<hostname> and <hostname>_ne ).

Network elements related traffic (between OMC Master / Agent / HMI andA9135 MFS / A9130 MFS Evolution / BSC Evolution).

NMC is classified as OMC traffic.

After activating the multiple LAN feature, the connections between the OMC-Rand network elements are lost.A change of the OMC-R IP address must be performed on each networkelement.

Perform the following actions as root :

1. On the OMC-R Master, stop the OMC-R proceses:# /alcatel/omc3/osm/script/MF-shutdown

2. Perform the following actions on the Master and all its attached Agents andHMIs, if needed, add a new network board, then power on the machines:

Stop the A1353-RA application:# /alcatel/omc3/osm/script/MF-shutdown

Power off on machine:# init 5

Add the new Ethernet board

Power on the machine

Perform a STOP+A and reboot the machine:boot -r

3BK 20903 AAAA PCZZA Ed.22 189 / 238


3. Perform the following actions on the Master and all its attached Agentsand HMIs:

Configure the new board:# /install/script/multiple_lan_setup.pl

Choose the network interface to be configured

Type the appropriate information for the required IP address, netmask,

and default router.

When the question Commit changes? ([y]es/[r]e-enter

data/[a]bort): appears , type :

[ y ] to commit changes

[ r ] to re-enter data for the chosen interface

[ a ] to leave the chosen interaface unchanged.

Type [ q ] to quite the multiple LAN configuration menu.

4. On the OMC-R Master, start the OMC-R processes:# /alcatel/omc3/osm/script/MF-start

5. Start DCN application and check that the connections between the OMC-Rand network elements are done through the new network board. The IPaddress corresponding to the new ethernet board can be seen in DCNwindow, HOST tab.

6. Change the OMC-R IP address defined in each attached A9135 MFS /A9130 MFS Evolution / BSC Evolution.Refer to section Modify the IP Address of the BSC Evolution (Section5.3.6) to modify the OMC-R ip address in BSC Evolution and to the A9130MFS Evolution Maintenance Handbook document, section Configure IPAddresses and Enable/Disable RIP V2, to modify the OMC-R ip addressin MFS Evolution.

4.33 Send Mail Activation1. Configure the sendmail service to send emails outside the OMCR domain.

2. As root user check the /etc/hosts file on the Master:127.0.0.1 localhost<ip address> <hostname> <hostname>.evolium.com ma1353raloghost

where <ip address> is the ip address of the Master and <hostname> is thehostname of the Master.

3. Add in the hosts file of the Master the target machines:1.1.1.1 santal santal.tm.alcatel.ro2.2.2.2 snooker snooker.evolium.com

where snooker is the machine from the same network and santal fromother LAN and domain.

4. Modify the /etc/mail/sendmail.cf on OMC-R:

From:# "Smart" relay host (may be null)DSmailhost$?m.$m$.

190 / 238 3BK 20903 AAAA PCZZA Ed.22


To:# "Smart" relay host (may be null)#DSmailhost$?m.$m$.

From:# my official domain nameDj.evolium.com

To:# my official domain name#Dj.evolium.com

5. Restart the mail server:# /usr/sbin/svcadm disable sendmail# /usr/sbin/svcadm enable sendmail

4.34 Inter OMC-R Adjacency Consistency Feature1. One Master OMC-R can supervise another or several Master OMC-Rs. A list

of supervised Master OMC-Rs must be declared at the supervisor Masterside. A script named updateGsmOMCList provides the list of supervisedOMC-Rs. The resulted list is named GSM_OMC_list and it is locatedin/alcatel/var/share/netconf . The script can add, remove or replace thedata related to a supervised OMC-R from GSM_OMC_list file.

2. Run the following script as axadmin user to declare the supervised OMC-R:cd /alcatel/omc3/script./updateGsmOMCList

Enter the host name and the IP address of the supervised OMC-R. Click on[ Add ] then on [ Ok ] to declare the OMC-R in the list.

3. Declare the supervisor OMC-R as external workstation on each supervisedOMC-R. Use ’axadmin’ account for the supervisor side and ’axexternal’ forthe supervised side. This action must be performed from the OSM, throughthe "Secure External Workstation Management" facility.

4. In case of concentration, if the supervised Master becomes an Agent, theGSM_OMC_list must be updated by removing the supervised Master. If thesupervisor Master becomes an Agent, the list must be updated by declaringanother Master OMC-R as supervisor. If the Master changes his own IPaddress the list must be also updated.

5. The Adjacency Consistency Feature is running periodically on OMC-R. Theon-demand usage is also available.

In case on-demand consistency feature is needed, use the following scripts,that are located in /alcatel/omc3/ei/script directory:

run the exportFriendCellsData script on each supervised OMC-R.

run the processFriendCellsData script on the supervisor OMC-R, with

/alcatel/var/share/netconf/GSM_OMC_list as ’OMC-Rs list’ argument.Optionally, the argument –withAutoactivation may be provided.

if –withAutoactivation has NOT been provided, run the

updateExternalFriendCells script on all involved OMC-Rs, bothsupervisor and supervised.

3BK 20903 AAAA PCZZA Ed.22 191 / 238


4.35 Configure the VNC Server for RAMSESTo configure the vncserver perform the following:

1. Check the environment variables needed when using the VNC. The variableLD_LIBRARY_PATH must contain at least /usr/lib and /usr/local/lib in thisorder.

Run the following commands to check the value of the variable:echo $LD_LIBRARY_PATH

If the path does not contain /usr/lib and /usr/local/lib run thefollowing command to set the variable accordingly:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/usr/local/lib

2. Check if the environment variables USER exists and define it if needed:

Run the following commands to check the existence of the variable:echo $USER

If the variable does not exist, run the following command to define itaccordingly:

USER=‘whoami‘ ; export USER

3. Check the rights of the .X11-unix directory:ls -l /tm/.X11-unix

If the directory doesn’t have 777 rights, set them:chmod 777 /tmp/X11-unix

4. Use your current username (the one obtained using the command whoami )to run the vncserver script:

The first time the script is ran you are asked to type a password:Password: <password>

Confirm the password by typing it one more time:Verify: <password>Would you like to enter a view-only password (y/n)?nNew ’X’ desktop is <hostname>:<x>

Note : <x> is the number associated to the current display. It’s valuemust be between 1 and 5, depending on the port used by RAMSES toallow connection.

Creating default startup script /<USER>/.vnc/xstartupStarting applications specified in/<USER>/.vnc/xstartupLog file is /<USER>/.vnc/<hostname>:<x>.log

From now on you can connect from a client by indicating the desktop.

Beware that RAMSES allows connections using ports from 5900 to 5904. Ifthe port number overcomes 5904, a message appears. You cannot starta new VNC session unless you stop an existing one. To stop a sessionrunning on a certain display, launch:

vncserver -kill :<DISPLAY_number>

5. If a reset of password is needed, run the following command:vncpasswdUsing password file /<USER>/.vnc/passwd

Type the new password:Password: <password>

Confirm the password by typing it one more time:Verify: <password>

192 / 238 3BK 20903 AAAA PCZZA Ed.22


Would you like to enter a view-only password (y/n)?n

3BK 20903 AAAA PCZZA Ed.22 193 / 238


194 / 238 3BK 20903 AAAA PCZZA Ed.22

5 Modify IP Addresses


This section contains the procedures for modifying the IP address of thefollowing:

The entire network

One machine

You can modify the IP addresses of the following machines:

Master

Agent

HMI

X Station

NPA connected to the A1353-RA network

Cisco Router

MFS

Network Printer.

3BK 20903 AAAA PCZZA Ed.22 195 / 238


5.1 Impact and Duration

5.1.1 Impact on Service

The following table shows the loss of supervision in the network when theIP addresses are changed.

Procedure Loss of Supervision

Modify the IP Address of the entire network 15 minutes

Modify the IP Address of the Master 15 minutes

Modify the IP Address of the Agent 10 minutes

Modify the IP Address of the HMI None

Modify the IP Address of X Station None

Modify the IP Address of the NPA None

5.1.2 Duration of IP Address Modification

The following table shows the amount of time needed to modify the IP addressof each machine.

Procedure Total Time

Modify the IP Address for the entire Network 3 hours

Modify the IP Address of One Machine 10 minutes

196 / 238 3BK 20903 AAAA PCZZA Ed.22


5.2 Modify the IP Address for the Entire Network

5.2.1 Global Procedure

When you modify the IP address for the whole network, you must perform thefollowing tasks in the order shown:

1. Remove X Stations (Section 4.12.4)

2. Remove Printers (Section 4.12.6)

3. To remove the HMIs from the network: Remove Workstations (Section4.12.2)

4. Modify the IP Address of the HMI (Section 5.2.2)

5. Modify the IP Address of an X Station (Section 5.2.3)

6. Modify the IP Address of the Master and Agent (Section 5.2.4)

7. Add Workstations (Section 4.12.1)

8. Add X Stations (Section 4.12.3)

9. Add Printers (Section 4.12.5)

10. Modify the IP Address of the BSC Evolution (Section 5.2.5) .

11. Modify the IP Address of the MFS Stations (Section 5.2.6) .

12. Modify the IP Address of the Cisco Router (Section 5.2.7)

13. Modify the IP Address of the NPA Server (Section 5.2.8)

14. Modify the IP Address of the NPA Client (Section 5.2.9) .

5.2.2 Modify the IP Address of the HMI

To modify the IP Address of the HMI:

1. Log in as user root on the HMI.

2. Edit the /etc/hosts file.

Modify the IP address of the HMI and save the file.

3. Modify also the ip address of the nemask and defaultrouter of the network, ifis the case, in /etc/defaultrouter and /etc/netmasks files.

4. Reboot the HMI:init 6

5.2.3 Modify the IP Address of an X Station

To modify the IP Address of the X Station:

1. Log in as user root on the X Station.


Modify the IP address of the X Station and save the file.

3. Reboot the X Station:init 6

3BK 20903 AAAA PCZZA Ed.22 197 / 238


5.2.4 Modify the IP Address of the Master and Agent

In case if the OMC-R adjacency consistency feature is activated thesupervized Master ip address must be updated in GSM_OMC_list by using theupdateGsmOMCList script located in /alcatel/omc3/script.

To modify the IP Address of the Master:

1. Stop the A1353-RA application:# /alcatel/omc3/osm/script/MF-shutdown

2. Stop LDAP clients on Master, Agents:# svcadm disable -t svc:/network/ldap/client

3. Log in as root user on each Agent host (only for XLarge configuration).

Edit the /etc/hosts file.

Modify the IP address of the Agent and the Master and save the file.

4. Update the Master IP address in RDN.# ldapmodrdn -D "cn=Directory Manager" -w <password>

By default <password> is nssecret.Type [ Enter ] after each line.

cn=<hostname> +iphostnumber=<old ipaddress>,ou=hosts,dc=evolium,dc=com

cn=<hostname>+iphostnumber=<new ip address>

Press 2 times [ Enter ] .Where:

<hostname> is the hostname of the Master

<old ip address> is the old IP address of the Master

<new ip address> is the new IP address of the Master.

5. Modify the IP address of the Master in LDAP.# ldapmodify -D "cn=Directory Manager" -w <password>


dn: cn=<hostname> +iphostnumber=<new ip

address>,ou=hosts,dc=evolium,dc=com

changetype: modify

replace: iphostnumber

iphostnumber: <new ip address>

Press 2 times [ Enter ] .# ldapmodify -D "cn=Directory Manager" -w <password>


dn: cn=default,ou=profile,dc=evolium,dc=com

changetype: modify

replace: defaultserverlist

198 / 238 3BK 20903 AAAA PCZZA Ed.22


defaultserverlist: <new ip address>

Press 2 times [ Enter ] .

3BK 20903 AAAA PCZZA Ed.22 199 / 238


6. Modify the IP address of the Master in formattedHtml file:# cd /alcatel/omc3/as/tools/script# vi formattedHtml

Modify the Master IP address in the ’http://<Master ip address>’ field.

7. Modify the IP address of the Master in the SEC online help file:# cd /alcatel/omc3/sec/data/acgui# vi help.properties

Modify in all fields the new IP address of the Master.


Modify the IP address of the Master and all the machines that need to bechanged (NPA, RNO, BSC Evolution, MFS, Printer, Cisco Router).

9. On Master and each Agent Host, edit the file /var/ldap/ldap_client_file .Update the IP address of the Master Host in this file.

10. To update the Agent IP addresses in LDAP perform the following as root(on Master):

# ldapmodify -D "cn=Directory Manager" -w <password>

dn: cn=<Agent> +ipHostNumber=<ipaddress>,ou=Hosts,dc=evolium,dc=com

changetype: modify

replace: ipHostNumber

ipHostNumber: <new ip address>

Where:

<Agent> is the hostname of the Agent

<ip address> is the old IP address of the Master


When finished the update, press 2 times [ Enter ] .

Perform this step for each Agent Host connected to the Master.

11. Modify the following OSM file:vi /alcatel/omc3/osm/conf/wsList.cfg

Modify the IP address for all machines in the file.

12. Update the following files with the new IP address of the Master.

/alcatel/omc3/ens/im/conf/param.cfg

/alcatel/omc3/ens/usm/conf/param.cfg

/alcatel/omc3/ens/usm/script/run_ensusm

/alcatel/omc3/helpd/conf/param.cfg

13. If the customer documentation is installed on the Master host, edit the/alcatel/var/share/doc/doc.url file.

Replace in this file the old IP address with the new IP address.

If the OMC-R is declared as documentation server on other machines, login on these machines and update the /alcatel/var/share/doc/doc.url file,with the new IP address.

200 / 238 3BK 20903 AAAA PCZZA Ed.22



15. Reboot the Master and each Agent host:# init 6

Wait until the machines are up.

16. Log in as user axadmin on the Master host.# sudo /alcatel/omc3/osm/script/MF-start

All processes must be green in [ DSM ] , denoting correct operation of theapplications.

17. The NSAP of the OMC-R used for the OMC-R-NMC Q3 interface must alsobe changed. Launch the following command to generate the new NSAP:

# /alcatel/omc3/q3im/script/configure_omc_for_q3.pl

18. Perform the following commands as root user:# cd /alcatel/omc3/q3im/script# ./configure_omc_for_q3.pl <NetworkId>

where <NetworkId> is the identifier of the OMC-R.

5.2.4.1 Update Master IP Address in the BSC EvolutionThe IP address of the Master must be updated in each connected BSCEvolution.

1. Launch the Windows A9130 BSC Terminal application from the desktop.

2. Type the current IP address of the A9130 BSC Evolution, click on [ OK ] .

3. Check at the bottom status bar, for the User Mode status to be Master .

4. If User Mode: slave then:

Follow the menu path: Utilities -> Switch User Mode .

In the pop up window, click on [ Yes ] .

5. Follow the menu path:

Commands -> BSS Operations -> Display BSC Peer Entities

6. In the next window, perform the following actions:

Select Object Class as BSC

Select Unit Type as BSC

Inside Unit Number, put 1

7. In Declare BSC Peer Entities window:

Select ’Address 2’ tab.

Add the ’Preferred OMC IP address’ value with the one from MasterIP Address.

Modify the ’NTP Server IP address’ value with the one from MasterIP Address.

Click on [ OK ] .

8. Close the Windows A9130 BSC Terminal application.

3BK 20903 AAAA PCZZA Ed.22 201 / 238


5.2.4.2 Update Master/Agent IP Address in the MFSThe IP address of the Master (or Agent) must be updated in each connectedMFS.

1. Log in as root user on the MFS (rlogin from the OMC on the active station)and perform the following:

Delete the line containing the old Master/Agent from /etc/hosts file.

Run the commands:<STATION_A># /usr/mfs/bin/mfs_addomcSNMP manager address:<IP address>Comunity name for SNMP:<hostname><STATION_A># /usr/mfs/bin/mfs_ntpIP address of the NTP server:<IP address>NTP server hostname:<hostname>

Where:<IP address> and <hostname> are thenew IP address andhostname of the Master/Agent.

2. From the active station perform a rlogin on the passive station and:

Delete the line containing the Master/Agent from /etc/hosts file.

Run the commands:<STATION_A># /usr/mfs/bin/mfs_addomcSNMP manager address:<IP address>Comunity name for SNMP:<hostname><STATION_A># /usr/mfs/bin/mfs_ntpIP address of the NTP server:<IP address>NTP server hostname:<hostname>

Where:<IP address> and <hostname> are the hostname and thenew IP address of the Master/Agent.

3. These changes are taken into account only after a switch over of bothstations. To perform it refer to Evolium A9135 MFS IMT User Guide for anA9135 MFS, or refer to A9130 MFS Evolution IMT User Guide for anA9130 MFS.

The switch over can be done after the reboot of the OMC.

202 / 238 3BK 20903 AAAA PCZZA Ed.22


5.2.5 Modify the IP Address of the BSC Evolution

On BSC Evolution 1. Launch the Windows A9130 BSC Terminal application from the desktop.











Inside Unit Number, type 1

Select [ Get and Modify ]

Click on [ OK ] .

7. In Modify BSC Peer Entities window:


Modify the ’BSC IP Subnet’ value.

Click on [ OK ] .

The OCPR process on active OMCPs board will be restarted automatically.


On OMC-R 1. Log in on OMC-R Master host as axadmin .

2. Open the DCN from the A1353-RA iconbox.

3. Select the BSS tab.

4. Select the right A9130 BSC Evolution.

5. Right click on it and select [ Modify ] .

6. In DCN: Modify a BSS window:

Modify the IP address of A9130 BSC Evolution.

Click on [ OK ] .

7. Close the DCN.

3BK 20903 AAAA PCZZA Ed.22 203 / 238


5.2.6 Modify the IP Address of the MFS Stations

5.2.6.1 Stop MFS SupervisionStop MFS supervision by the OMC-R:

1. In the DCN: Management main window, click on the MFS tab.

The DCN MFS view opens.

2. Select the required MFS.

3. Select Function -> Stop MFS Supervision .

The MFS contains 2 stations: Station_A and Station_B.

First update is to change the MFS IP address on the active and standbyMFS stations.

Second update is to change the MFS IP address also in the OMC-R.

In case of A9135 MFS, refer to A9135 MFS (Section 5.2.6.2) .

In case of A9130 MFS, refer to the A9130 MFS Evolution MaintenanceHandbook document, section Configure IP Addresses and Enable/DisableRIP V2.

5.2.6.2 A9135 MFS1. Open an rlogin session. Log in as user root on MFS Station_A (defined as

stand-by station).

2. Open an rlogin session. Log in as user root on MFS Station_B (definedas active station).

3. Stop nectar on both control stations, beginning with stand-by 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.

4. Modify IP Addresses of both control stations, starting with the stand-bystation, using IOLAN connection. To modify the IP Address of Station A :

Open an rlogin session. Log in as user root on MFS Station_B.

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 ’^]’

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

If is necessary enter user name root and appropriatepassword.Wait for the prompt >>>

Enter the following command:# /usr/mfs/bin/mfs_inet -duplex -hostname STATION_A

Press [ Enter ] when a value does not need to be modified.

Modify the following IP addresses:

204 / 238 3BK 20903 AAAA PCZZA Ed.22


Station_A

Netmask

Station_mfs

Gateway.

Note: When you change the IP Address of the MFS, the connection with the OMC-Ris lost.

Close the connection through IOLAN, closing or killing the terminalwindow.

5. To modify the IP Address of the MFS Station_B :

Open an rlogin session. Log in as user root on MFS Station_A.

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 ’^]’

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

If is necessary enter user name root and appropriatepassword.Wait for the prompt >>>

Enter the following command:# /usr/mfs/bin/mfs_inet -duplex -hostname STATION_B

Press [ Enter ] when a value does not need to be modified.

Modify the following IP addresses:

Station_B

Netmask

Station_mfs

Gateway.

Note: When you change the IP Address of the MFS, the connection with the OMC-Ris lost.

Close the connection through IOLAN, closing or killing the terminalwindow.

6. Reconfigure the DecNet OSI:<STATION_A> # /usr/mfs/bin/mfs_decnetosi

Note: Only in case of Duplex<STATION_B> # /usr/mfs/bin/mfs_decnetosi

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

8. Restart STATION B in site mode:<STATION_B># usr/mfs/bin/mfs_start_nectar -site

3BK 20903 AAAA PCZZA Ed.22 205 / 238


Confirm the reboot and wait until the reboot is finished, when directconnection (telnet) is possible again.

5.2.6.3 Modify MFS IP Address in OMC-R1. Refer to the document "BSS Configuration Handbook", section Modify

MFS IP Address .

2. If the MFS IP address was modified, update the /etc/hosts file on Master (orAgent) with the new MFS IP address.

5.2.6.4 Start MFS Supervision1. In the [ DCN ] window click on the MFS tab.

2. Select the required MFS.

3. Select Function -> Start MFS Supervision .

206 / 238 3BK 20903 AAAA PCZZA Ed.22


5.2.7 Modify the IP Address of the Cisco Router

To modify the IP Address of the Cisco Router:

1. Use a hyperterminal program (e.g. the HyperTerminal program included withWindows NT) to connect your Console/Computer to the console port of theCisco Router.Use the following data transmission parameters:

9600 baud

8 data bits

No parity generated or checked

2 stop bits.

2. From the Hyperterminal Program, enter the following command:enable

3. Enter the enable password.

4. Enter the following commands:conf tinterface e0ip address <IP address> | <netmask>endwrite memoryexit

Where <IP address> is the new IP address, and <netmask> is the newnetmask of the Cisco Router.

5.2.8 Modify the IP Address of the NPA Server

This procedure describes how to modify the IP address of the NPA server.

1. Log in as user root on the NPA server.

2. Enter the command:vi /etc/hosts

3. In the displayed file hosts , modify the IP address of the Master host, theNPA server, and if required, the NPA client.

4. Save changes and close the file hosts .


6. Reboot the NPA server:init 6

5.2.9 Modify the IP Address of the NPA Client

This procedure describes how to modify the IP address of the NPA client.

1. Log in as user root on the NPA client.


3. In the displayed file hosts , modify the IP address of the NPA server andthe NPA client.


3BK 20903 AAAA PCZZA Ed.22 207 / 238


5. Reboot the NPA client:init 6

208 / 238 3BK 20903 AAAA PCZZA Ed.22


5.3 Modify the IP Address for One MachineYou can modify individually the IP address of the following machines:

Modify the IP Address of an X Station (Section 5.3.1)

Modify the IP Address of the HMI (Section 5.3.2)

Modify the IP Address of a Network Printer (Section 5.3.3)

Modify the IP Address of the Master (Section 5.3.4)

Modify the IP Address of the Agent (Section 5.3.5)

Modify the IP Address of the BSC Evolution (Section 5.3.6)

Create Terminal window (Section 3.7.1)

Modify the IP Address of the MFS (Section 5.3.7)

Modify the IP Address of the Cisco Router (Section 5.3.8)

Modify the IP Address of the NPA Server (Section 5.3.9)

Modify the IP Address of the NPA Client (Section 5.3.10) .

5.3.1 Modify the IP Address of an X Station

This procedure describes how to modify the IP address of an X Station.

Before modify the IP address of an X Station, be sure that you are logged onthe X Station and not on the Master Host.

To modify the IP address of the X Station, modify the /etc/hosts file of X Stationand run the ifconfig command.

Update the /etc/hosts file of the Master (or HMI) where the X Station isconnected.

Restart the nscd (naming service caching daemon):# svcadm disable -t svc:/system/name-service-cache# svcadm enable svc:/system/name-service-cache

3BK 20903 AAAA PCZZA Ed.22 209 / 238


5.3.2 Modify the IP Address of the HMI

This procedure describes how to modify the IP address of the HMI.

5.3.2.1 Remove HMI from NetworkYou must remove the HMI from the network before you modify its IP Address.

Remove first the Printers declared on the HMI, refer to task Remove Printers(Section 4.12.6) .

To remove the HMI from the network, refer to the task Remove Workstations(Section 4.12.2) .

5.3.2.2 Modify the IP Address of the HMITo modify the IP Address of the HMI:

1. Log in as root on the HMI.


Modify the IP address of the HMI and save the file.

3. Log in as root on the X Stations connected to the HMI.

Edit the /etc/inittab file. Update the IP address of the HMI.


5. Reboot the HMI and connected X Stations:init 6

5.3.2.3 Add the HMI to the NetworkTo add the HMI to the network, refer to the task Add Workstations (Section4.12.1) .

Redeclare the printers, previous deleted: Add Printers (Section 4.12.5) .

5.3.3 Modify the IP Address of a Network Printer

You must remove a Network Printer before you can modify its IP Address.

To remove a Network Printer, refer to the task Remove Printers (Section4.12.6) .

Modify IP Address 1. Log in as user axadmin on the Master.

2. From the A1353-RA Icon Box, click on [ Admin Facilities (OSM) ] .

3. Enter your username and password in the Password dialog box.

4. From the OSM Administration Facilities Main Menu, select Configuration ->Printer Management -> Add Printer .

The Add Printer window opens.

5. Modify the network printer IP Address in the ’IP address’ field.

6. Click on [ Add ] and [ Confirm ] to validate your selection.

7. To add the printer to the network, complete the task Add Printers (Section4.12.5) .

210 / 238 3BK 20903 AAAA PCZZA Ed.22


5.3.4 Modify the IP Address of the Master

In case if the OMC-R adjacency consistency feature is activated thesupervized Master ip address must be updated in GSM_OMC_list by using theupdateGsmOMCList script located in /alcatel/omc3/script.

This procedure describes how to modify the IP address of the Master:

1. Stop the A1353-RA application:# /alcatel/omc3/osm/script/MF-shutdown

2. Stop LDAP clients on Master, Agents and HMIs:# svcadm disable -t svc:/network/ldap/client

3. Update the Master IP address in RDN.# ldapmodrdn -D "cn=Directory Manager" -w <password>


cn=<hostname> +iphostnumber=<old ip

address>,ou=hosts,dc=evolium,dc=com

cn=<hostname>+iphostnumber=<new ip address>

Press 2 times [ Enter ] .Where:

<hostname> is the hostname of the Master

<old ip address> is the old IP address of the Master


4. Modify the IP address of the Master in LDAP.# ldapmodify -D "cn=Directory Manager" -w <password>


dn: cn=<hostname> +iphostnumber=<new ipaddress>,ou=hosts,dc=evolium,dc=com

changetype: modify

replace: iphostnumber

iphostnumber: <new ip address>



dn: cn=default,ou=profile,dc=evolium,dc=com

changetype: modify

replace: defaultserverlist

defaultserverlist: <new ip address>

5. Modify the IP address of the Master in formattedHtml file:# cd /alcatel/omc3/as/tools/script

3BK 20903 AAAA PCZZA Ed.22 211 / 238


# vi formattedHtml

Modify the Master ip address in ’http://<Master ip address>’ field.

6. Modify the IP address of the Master in the SEC online help file:# cd alcatel/omc3/sec/data/acgui# vi help.properties

Modify in all fields the new ip address of the Master.

7. Edit the /etc/hosts file on Master, Agents and HMIs.

Modify the IP address of the Master.

8. On the Master, Agents and HMIs edit as root the /var/ldap/ldap_client_file .Modify the IP address of the Master in this file.

212 / 238 3BK 20903 AAAA PCZZA Ed.22


9. Modify the following OSM file:vi /alcatel/omc3/osm/conf/wsList.cfg

Save the file and exit the vi editor.

10. If the customer documentation is installed on the Master host, edit the/alcatel/var/share/doc/doc.url file.

Replace in this file the old IP address with the new IP address.

If the OMC-R is declared as documentation server on other machines, log inon these machines and update the /alcatel/var/share/doc/doc.url file,with the new IP address.

11. Update the following files with the new IP address of the Master .

/alcatel/omc3/ens/im/conf/param.cfg

/alcatel/omc3/ens/usm/conf/param.cfg

/alcatel/omc3/ens/usm/script/run_ensusm

/alcatel/omc3/helpd/conf/param.cfg

12. Log in as root on the X Stations connected to the Master.

Edit the /etc/inittab file. Update the IP address of the Master.

Reboot the X Station:

13. Modify also the IP address of the nemask and defaultrouter of the network, ifis the case, in /etc/defaultrouter and /etc/netmasks files.

14. Perform a reboot on the Master, Agents, HMIs and X Stations connectedto the Master.

# init 6

Wait until the system comes up.

15. Log in as axadmin and start the the OMC:sudo /alcatel/omc3/osm/script/MF-start

16. Perform the following commands as root user:# cd /alcatel/omc3/q3im/script# ./configure_omc_for_q3.pl <NetworkId>

where <NetworkId> is the identifier of the OMC-R.

You must now modify the IP address for the Master host on other machines:

5.3.4.1 Modify the IP Address of the Master on the MFSTo update the Master IP address in the MFS refer to: Update Master/Agent IPAddress in the MFS (Section 5.2.4.2) .

5.3.4.2 Modify the IP Address of the Master on the NPA Server1. Log in as user root on the NPA server.

2. Open the file hosts , enter the command:vi /etc/hosts

3. Modify the IP address of the Master host in the displayed file hosts .


3BK 20903 AAAA PCZZA Ed.22 213 / 238


5.3.5 Modify the IP Address of the Agent

This procedure describes how to modify the IP address of the Agent machine.

1. On the Master host stop A1353-RA application:# /alcatel/omc3/osm/script/MF-shutdown

2. On the Agent Host stop LDAP client.# svcadm disable -t svc:/network/ldap/client

3. To update the Agent IP addresses in LDAP perform the following as root(on Master):


dn: cn=<Agent> +ipHostNumber=<ip

address>,ou=Hosts,dc=evolium,dc=com

changetype: modify

replace: ipHostNumber

ipHostNumber: <new ip address>

Where:

<Agent> is the hostname of the Agent

<ip address> is the old IP address of the Master


When finished the update, press 2 times [ Enter ] .

4. Modify the following file:vi /alcatel/omc3/osm/conf/wsList.cfg

Modify the IP address of the Agent in the file.



6. Reboot the Agent host:# init 6

Wait until the Agent comes up.

7. Start as axadmin the A1353-RA application:sudo /alcatel/omc3/osm/script/MF-start

Modify the IP Address of

the Agent on the MFS

To update the Agent IP address in the MFS refer to: Update Master/Agent IPAddress in the MFS (Section 5.2.4.2) .

214 / 238 3BK 20903 AAAA PCZZA Ed.22


5.3.6 Modify the IP Address of the BSC Evolution

On BSC Evolution 1. Launch the Windows A9130 BSC Terminal application from the desktop.











Inside Unit Number, put 1

Select [ Get and Modify ]

Click on [ OK ] .

7. In Modify BSC Peer Entities window:


Modify the ’BSC IP Subnet’ value.

Click on [ OK ] .

The OCPR process on active OMCPs board will be restarted automatically.


On OMC-R 1. Log in on OMC-R as axadmin .

2. Open the DCN from the A1353-RA iconbox.

3. Select the BSS tab.

4. Select the right A9130 BSC Evolution.

5. Right click on it and select [ Modify ] .

6. In DCN: Modify a BSS window:

Modify the IP address of A9130 BSC Evolution.

Click on [ OK ] .

7. Close the DCN.

3BK 20903 AAAA PCZZA Ed.22 215 / 238


5.3.7 Modify the IP Address of the MFS

For A9135 MFS IP address modification, perform the followings:

A9135 MFS (Section 5.2.6.2)

Start MFS Supervision (Section 5.2.6.4)

For A9130 MFS Evolution IP address modification, perform the followings:

Configure IP Addresses and Enable/Disable RIP V2 as described in theA9130 MFS Evolution Maintenance Handbook document

Modify MFS IP Address in OMC-R (Section 5.2.6.3)

Start MFS Supervision (Section 5.2.6.4)

5.3.8 Modify the IP Address of the Cisco Router

To modify the IP Address of the Cisco Router:

1. Use a hyperterminal program (e.g. the HyperTerminal program included withWindows NT) to connect your Console/Computer to the console port of theCisco Router.Use the following data transmission parameters:

9600 baud

8 data bits

No parity generated or checked

2 stop bits.

2. From the Hyperterminal Program, enter the following command:enable

3. Enter the enable password.

4. Enter the following commands:conf tinterface e0ip address <IP address> | <netmask>endwrite memoryexit

Where <IP address> is the new IP address, and <netmask> is the newnetmask of the Cisco Router.

5. Log in as user root on the A1353-RA machine where the Cisco Router isdeclared.


7. In the displayed file hosts , modify the IP address of the Cisco Router.


216 / 238 3BK 20903 AAAA PCZZA Ed.22


5.3.9 Modify the IP Address of the NPA Server

This procedure describes how to modify the IP address of the NPA server.

To modify the IP address of the NPA server:

1. Log in as user root on the NPA server.


3. In the displayed hosts file, modify the IP address of the NPA server.

4. Save changes and close the hosts file.


6. Reboot the NPA server:init 6

7. Log in as user root on the NPA client.


9. In the displayed file hosts , modify the IP address of the NPA server.


11. Log in as user root on the A1353-RA machine where the NPA server isdeclared.


13. In the displayed file hosts , modify the IP address of the NPA server.


5.3.10 Modify the IP Address of the NPA Client

This procedure describes how to modify the IP address of the NPA Client.

1. Log in as user root on the NPA Client.


3. In the displayed file: hosts , modify the IP address of the NPA Client.

4. Save changes and close the file: hosts .

5. Reboot the NPA Client:init 6

6. Log in as user root on the NPA Server.


8. In the displayed file: hosts , modify the IP address of the NPA Client.

9. Save changes and close the file: hosts .

3BK 20903 AAAA PCZZA Ed.22 217 / 238


218 / 238 3BK 20903 AAAA PCZZA Ed.22

6 Administrative Tasks for MPM


This section contains procedures which describe administrative tasks. Thetopics include:

Configure a printer

Display Visu-log

Manage ASCII output

Start/stop MPM.

3BK 20903 AAAA PCZZA Ed.22 219 / 238


6.1 Configure PrinterOnly one network printer is activated by default.

Procedure 1. To add a printer refer to Add Printers (Section 4.12.5) . Refer to Define UserDefault Printer (Section 4.12.8) to set the default printer for the metrica user.

2. Test the printer connection. As a metrica user, enter:lp -d <printer_name> /etc/hosts

If the test is successful, go to Step 3 . If the test is unsuccessful, go back toStep 1 .

3. Create a new file for the printer by copying the NPR default file. As ametrica user, enter:

cd $NPR_DIR/etc/hardcopycp NPR_DEFAULT NPR_DEFAULT1

4. Modify the following NPR default parameters using any text editor. Theprinter name lpalp1 is used as an example in the following steps.

Parameters Settings

plainprint <printer_name>

psprint lp -d <printer_name>

psplot lp -d <printer_name>

5. Create a link. As a metrica user, enter:cd $NPR_DIR/tqlclients/etc/hardcopyln -s $NPR_DIR/etc/hardcopy/NPR_DEFAULT1 NPR_DEFAULT1

6. Create a new file for the printer by copying the lpl file. As a metrica user,enter:

cd $NPA_DIR/bincp lpl lpl1

7. Modify the following lpl1 file using any text editor. Enter:$NPA_DIR/bin/postpoint -pl -l50 -m0.7 $1 | lp -d<printer_name>

To add another printer to the network, repeat Steps 1 to 7 .

220 / 238 3BK 20903 AAAA PCZZA Ed.22


6.2 Display Visu-logThis task displays statistics of parsing and loading PM files for GSM and GPRS.

Procedure To display Visu-log:

1. In the MPM administration menu, select Administration -> Start MPMAdministration... .

The A1353-RA Administration menu appears.

2. In the A1353-RA Administration menu, select PM Load Report -> PMLoad Report... .

The PM Load Report window appears.

3. In the PM Load Report window, select:

Reports -> Statistics...or

Reports -> Covered Time (%)... .

6.3 Manage ASCII (OBSYNT) OutputThe administrator can enable or disable the OBSYNT - like output type. Asnew results arrive (each accumulation period), the ASCII output managercreates the ASCII files type OBSYNT for each raw type present (excluding rawtype 31, which is dedicated to RMS).

The ASCII output manager receives the BSS PM counters files from the parser,and the MFS PM counters files from the transfer script. OBSYNT ASCII files(for GSM/GPRS PM files) are produced in the following directories:

/alcatel/var/share/AFTR/APME/OBSYNT/[BSC_NAME] , for GSM PM

counters

/alcatel/var/share/AFTR/APME/OBSYNT/[MFS_NAME] , for GPRS PM

counters.

Procedure To enable/disable ASCII output:

1. In the MPM administration menu, select Administration -> Start MPMAdministration... .

The NPA Administration browser appears.

2. In the Administration browser, select

Options -> ASCII output -> Enable ASCII output...to enable ASCII output

or

Options -> ASCII output -> Disable ASCII output...to disable ASCII output.

6.4 Daily OBSYNT Files Availability1. A new script named ’createZipFiles.pl’ is available to create the OBSYNT

files for BSC and MFS.

2. The script is used in automatic mode and it is ran every night at 3:20 asscheduled in crontab by axadmin:

The crontab file contains the following line:

3BK 20903 AAAA PCZZA Ed.22 221 / 238


20 3 * * * /alcatel/omc3/osm/script/createZipFiles.pl

3. The script produces:

one zip file containing all full BSSconf files per day (previous day)

Input directory: /alcatel/var/share/AFTR/ACME

Output directory: /alcatel/var/share/AFTR/ACME/ZIP

Naming rule: BSSConf.<OMC-R Name>.<date>.zip, where date hasthe ’yyyymmdd’ format

one zip file per NE (BSC, MFS) containing all OBSYNT files per day

(previous day)

Input directory:

/alcatel/var/share/AFTR/APME/OBSYNT/<NE_Name>/<date>,where NE_Name is the BSS/MFS name and date is the previous

day in ’yyyymmdd’ format

Output directory: /alcatel/var/share/AFTR/APME/OBSYNTZIP

Naming rule: OBSYNT.<OMC-R Name>.<NE_Name>.<date>.zip

where NE_Name is the BSS/MFS name and date is the previous dayin ’yyyymmdd’ format

4. The MF-cleanup script used in OMC-R to clean up files is updated in orderto handle the new zip files. Every night at 3:25, the script deletes all thezip files older than 7 days.

222 / 238 3BK 20903 AAAA PCZZA Ed.22


6.5 Start/Stop MPMThe metrica user starts or stops MPM at the UNIX level.

6.5.1 Starting MPM

To start MPM:

Enter the command:mpmstart

6.5.2 Stopping MPM

To stop MPM:

Enter the command:mpmstop

3BK 20903 AAAA PCZZA Ed.22 223 / 238


224 / 238 3BK 20903 AAAA PCZZA Ed.22

7 Backup/Restore MFS Configuration Data


This section describes the backup and restore procedures for MFSConfiguration data. It does not cover the backup and restore of UNIX orNECTAR. For this, please contact Alcatel Support.

Perform a backup before and after each Software change. Backup files areonly compatible with the specific software release in which they were created.For example, a backup generated under Software Release X will not workunder Software Release Y.

3BK 20903 AAAA PCZZA Ed.22 225 / 238


7.1 IntroductionThese procedures describe how to back up and restore the configuration dataof an MFS. Backup files are stored on the shared disks of the MFS. These filescan also be uploaded to the OMC-R for storage.

Process The major steps for a backup and restore consist of the following:

1. Configuration data are compressed and stored on the local disks. Up to fivebackups can be stored on the shared disks. These files can also be copiedto a zip disk or uploaded to the OMC-R via a script launched from theOMC-R. The MFS operator must delete old backup files to make room fornew files. The OMC-R operator must manage the disk space on the OMC-R.

2. Configuration files are put on the MFS. There are three ways to do this:

From the MFS shared disk. If there was no damage to the disks or

files, these files can be used. This is the quickest method because nodownloading from the OMC-R is necessary (a gain of 80 minutes). No

on-site intervention is necessary for this step of the restore as the

OMC-R can remotely access the MFS via the IMT view. The localIMT can also be used.

From the zip disk. Either the zip disk was created previously fromthe backup files, or the files are copied from the OMC-R to the disk

and the disk transported to the MFS site. The local IMT has to be

used in this case.

From the OMC-R. The OMC-R downloads the configuration files and

data (an average of 80 minutes for a 20 Mbyte zipped file).

3. The operator performs the configuration restore procedure which: stopsNECTAR, replaces the existing configuration files with the backup filesand then restarts NECTAR.

4. The OMC-R reconnects to the MFS and the OMC-R operator checks andaligns the restored configuration with the OMC-R configuration.

226 / 238 3BK 20903 AAAA PCZZA Ed.22


7.2 Backup MFS DataA backup is a non-critical operation that must be performed on a regular basis;daily, weekly or monthly depending on the frequency of network modifications.Backup of configuration files and data allow the recovery of this informationin case the MFS configuration must be restored (for example, if both shareddisks crash).

Perform a backup before and after each software change. Backup files areonly compatible with the specific software release in which they were created.Backup files are tagged with the date of their creation. This date must be laterthan the last software change date.

7.2.1 Who Can Perform a Backup

A backup can be performed by the IMT view operator (locally or from theOMC-R).

7.2.2 O&M and Telecom Impact

None.

7.2.3 Size of Backup Files

A maximum of 20 Mbytes. Even with a small configuration the size is near 20Mbytes, due to the dimensioning of the database.

7.2.4 Duration of Operation

The backup to a local disk takes an average of two minutes. The upload of thebackup to the OMC-R takes 80 minutes with a 64 kbit/s connection.

7.3 Backup Procedure

7.3.1 Backup to Local Disk on MFS Control Station

To back up MFS data:

1. From the IMT (either locally or from the OMC-R) GPRS Terminal window,select Backup/Restore -> Backup .

The Backup dialog box opens.

2. Enter the backup file name.

3. Click on [ OK ] .

When the backup is complete, the Backup Done window opens, showing thebackup file name, together the date and hour of the backup. The identity ofthe MFS is included at the start of all backup file names.

3BK 20903 AAAA PCZZA Ed.22 227 / 238


7.3.2 Upload to OMC-R

Note: A file of 20 Mbytes can take up to 80 minutes to load from the MFS to theOMC-R.

To perform an upload of the backup data to the OMC-R from the OMC-R:

1. From the OMC-R Icon box, click on [ MFS Backup ] .

The MFS Backup Manager window opens.

2. At the prompt type:1 [ enter ]

to select an MFS.

3. If this is the first time using the backup facility, type:1 [ enter ]

To select a new MFS, go to Step 4 .

Otherwise, select the MFS from the list by entering the numbercorresponding to the MFS. Go to Step 5

4. Enter the IP address or name of the new MFS and press [ enter ] .

5. After completing steps 3 and (if needed) 4 , the OMC-R checks the networkconnection to the MFS. If it is OK, press [ enter ] and go to Step 6 . Ifit is not OK, check that:

You correctly entered the IP address or name of the MFS

Your network connection is alive (for example, to do this, use the UNIXcommand ping).

6. From the main menu, type:2 [ enter ]

to select the upload option.

The Upload menu opens.

7. Type:1 [ enter ]

to select the Open file for upload .

A list of backup files is displayed.

8. Type the appropriate number of the backup file to upload and press [ enter ] .

9. To upload the file to the OMC-R, type:y [ enter ]

Press [ enter ] to continue.

228 / 238 3BK 20903 AAAA PCZZA Ed.22


7.4 Restore MFS DataA restore is a critical operation with loss of O&M supervision, GPRS and GSMtraffic that is routed through the MFS. A restore is necessary, for example, whenboth control stations have crashed.

Note: The procedure that follows only details the restore of the MFS data andconfiguration files.

Prerequisites UNIX and Nectar and all the necessary software have to be operational andactive before restoring the MFS data and configuration files. Contact Alcatelsupport if this is necessary.

7.4.1 Who Can Perform a Restore of the Configuration Files

A restore can be performed by an IMT user. If the data needs to be downloadedfrom the OMC-R, coordination is needed between the MFS and OMC-R sites.

7.4.2 O&M Impact

Complete. There is no O&M supervision possible during the operation.Supervision is only restored upon successful completion of the restoreprocedure.

7.4.3 Telecom Impact

This depends on the nature of the outage. The times that follow give the outagegenerated when resetting the GPU.

GPRS traffic: Less than one minute

GSM traffic: Less than one second.

7.4.4 Duration of Operation

Restore configuration files and data: 2 minutes if done locally. 80 minutes todownload files from OMC-R.

Alignment/Check from OMC-R: 10 minutes.

3BK 20903 AAAA PCZZA Ed.22 229 / 238


7.5 Restore ProcedureIf the backup files are corrupt on the MFS, download the backup file from theOMC-R or from a zip disk. If the backup files are good on the MFS, skip thedownload from OMC-R/Zip disk and go directly to Restore MFS Data.

Make sure the backup file you use corresponds to the software release that isinstalled on the MFS. Backup files are tagged with the date of their creation.This date must be later than the last SW change date. If it is not, your restoreattempt will fail.

7.5.1 Download from OMC-R

To download the 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.

230 / 238 3BK 20903 AAAA PCZZA Ed.22


7.5.2 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-synchronise the MFS:

From the RNUSM window, select the appropriate MFS, right click andselect Re-Synchronize .

3BK 20903 AAAA PCZZA Ed.22 231 / 238


232 / 238 3BK 20903 AAAA PCZZA Ed.22

8 Upgrade Documentation


This section explains how to update the OMC-R user documentation.

3BK 20903 AAAA PCZZA Ed.22 233 / 238


8.1 IntroductionCustomer Documentation can be installed in two modes:

Installing Flat file documentation, when no Verity is installed

Installing Full documentation, when also a license is needed and theVerity is installed

The upgrade of the Customer Documentation is also done depending on theprevious type of the installation (with or without Verity).

In both cases the upgrade procedure removes the old documentation andinstalls the new one.

If the Verity is previously installed, the upgrade procedure performs also adocumentation re-indexing.

8.2 Upgrade of Customer Documentation CD-ROM

8.2.1 Prerequisites

The new Customer Documentation CD-ROM only needs to be installed onthe documentation server.

root access is needed to install the new Customer Documentation CD-ROM.

Note: For all Hardware configurations, the Customer Documentation CD-ROM can beinstalled with or without Verity Server.

If Verity search engine has not been previously installed but you want to add itnow, a remove/install procedure must be performed.

8.2.2 Different Cases

Two cases are defined:

Case 1 - Upgrade in the same configuration (with/without Verity):

old documentation without Verity to new documentation without Verity

old documentation with Verity to new documentation with Verity

Case 2 - Upgrade with new Verity installation:old documentation without Verity to new documentation with Verity.

234 / 238 3BK 20903 AAAA PCZZA Ed.22


8.2.2.1 Case 1To install a new documentation version from Customer DocumentationCD-ROM, using the same configuration (with/without Verity):

1. Open a terminal window on the A1353-RA host.

2. Log in as root user.

3. Insert the Customer Documentation CD-ROM with the version you wantto install.

4. Enter the following commands to launch the install script:cd /cdrom/cdrom0./install_omc_doc

5. When asked to upgrade documentation:Current Documentation release is : INSPAWxxx(B9)New Documentation release is : INSPAWyyy(B9)Do you want to upgrade the documentation (y|n|q) ? :

type [ y ] then press [ Enter ] .

Wait until the documentation is installed.

8.2.2.2 Case 2To upgrade the old documentation without Verity to the new documentationwith Verity:

1. Open a terminal window on the A1353-RA host.

2. Log in as root user.

3. Insert the Customer Documentation CD-ROM with the version you wantto install.

4. Remove the old documentation installed without Verity:cd /cdrom/cdrom0./remove_omc_doc

5. When asked to remove documentation:Current Documentation release is : INSPAWxxx(B9)Do you want to remove the documentation (y|n|q) ? :

type [ y ] , then press [ Enter ] .

Wait until the documentation is removed.

6. Add the K2 license in the /install/data directory.

7. Enter the following commands to launch the installation script:cd /cdrom/cdrom0./install_omc_doc

8. When asked to install documentation:Documentation release is : INSPAWxxx(B9)-> Installation of Verity K2 is optional.In addition to the Documentation,-> do you want to install the Verity K2 (y|n|q) ? :

Type [ y ] then press [ Enter ] .

Wait until the documentation is installed.

3BK 20903 AAAA PCZZA Ed.22 235 / 238


8.3 Launch Documentation ToolProcedure

To launch the documentation tool, click on [ Doc ] from the A1353-RA iconbox.

The documentation home page is displayed in a Mozilla Firefox window.

8.4 TroubleshootingUse the following to help solve launch problems and monitor color problems.

8.4.1 No Error Message

If process does not launch and no error message is displayed, check to makesure the variable DISPLAY is set correctly:

1. At the command prompt, enterecho $DISPLAY

The following must be displayed:<IP address> :0.0

2. Compare this with the name of the IP address of the machine you areworking on. If they are not the same, at the command prompt, enter:

export DISPLAY= <IP address> :0.0

where <IP address> is the IP address of your machine.

3. To start the documentation launch tool, at a command prompt, enter thefollowing:

mozilla http:// <omc> :8080/doc &

Where <omc> is the hostname or IP address of the OMC-R (documentationserver).

236 / 238 3BK 20903 AAAA PCZZA Ed.22


8.4.2 Correcting Monitor Color Problems

Note: The following procedure works only Ultra 5 workstations and later models. Theresults you get depend on the monitor you are using and your workstation’sgraphics card and the card’s memory.

If you have problems with the colors displayed on your monitor, a possiblesolution is to switch your workstation graphics mode to a color depth deeperthan 8 bits (such as 16 bits, 24 bits, or 32 bits, depending on the video memoryof your workstation).

1. Execute the Solaris command# m64config -prconf

The following is displayed:

Card possible resolutions

Monitor possible resolutions

Possible depths

Current resolution setting

Current depth

2. If the current depth is not 24 , set it:# m64config -res <resolution> -depth 24

Where <resolution> (e.g. 1024x768x85) must be supported by the cardand monitor.

If the following error message is displayed, run again the previous commandwith a lower resolution.

m64config: Not enough memory for resolution<resolution> at depth 24

Note: You must restart the X11 server to activate the changes. If you use the CDEdtlogin window, logging out and then logging in again activates the changes.

3BK 20903 AAAA PCZZA Ed.22 237 / 238


BLANK PAGE BREAK

238 / 238 3BK 20903 AAAA PCZZA Ed.22

A1353-RA Network Administration Handbook ed22.pdf

Documents

Transcript of A1353-RA Network Administration Handbook ed22.pdf