+ All Categories
Home > Documents > A1353-RA Network Administration Handbook ed13.pdf

A1353-RA Network Administration Handbook ed13.pdf

Date post: 14-Nov-2015
Category:
Upload: vu-anh-tuan
View: 230 times
Download: 3 times
Share this document with a friend
Popular Tags:
224
DATE: 20040930 AUTHOR(S): Company: CIT/MND Name: A. FLUCSA Other: APPROVAL AUTHORITY(S): Company: CIT/MND Name: A. FLORUNCUT Other: OPERATOR(S): Company: Name: CUSTOMER COMMENTS: INTERNAL COMMENTS: Proposal 05 3BKA80FBR150442 The SNMP collector must be enabled to see the MFS in MRTGMFS. New sections added: Main Page (Section 4.25.1) , MRTG Index Page (Section 4.25.2) and Detailed Statistics (Section 4.25.3) . Proposal 04 3BKA80FBR155339 Update generic customer documentation installation 3BKA32FBR150805 Not possible to log from an User Terminal to the Master. Proposal 03 3BKA32FBR152883 Update B9 A1353-RA Network Administration Handbook in case the OMC G2 backup/restore is done on a set of tapes. Proposal 02 3BKA55CBR139123 - Supervision of CPU, memory and disks of MFS from OMC-R Proposal 01 Creation from B8 document. 3BKA32CBR145210 - Change the path for the OSM backup/restore scripts.
Transcript
  • DATE: 20040930AUTHOR(S):

    Company: CIT/MNDName: A. FLUCSAOther:

    APPROVAL AUTHORITY(S):Company: CIT/MNDName: A. FLORUNCUTOther:

    OPERATOR(S):Company:Name:

    CUSTOMER COMMENTS:

    INTERNAL COMMENTS:Proposal 053BKA80FBR150442

    The SNMP collector must be enabled to see the MFS in MRTGMFS.New sections added: Main Page (Section 4.25.1) , MRTG Index Page (Section 4.25.2) and DetailedStatistics (Section 4.25.3) .

    Proposal 043BKA80FBR155339

    Update generic customer documentation installation3BKA32FBR150805

    Not possible to log from an User Terminal to the Master.Proposal 033BKA32FBR152883

    Update B9 A1353-RA Network Administration Handbook in case the OMC G2 backup/restoreis done on a set of tapes.

    Proposal 023BKA55CBR139123 - Supervision of CPU, memory and disks of MFS fromOMC-R

    Proposal 01Creation from B8 document.

    3BKA32CBR145210 - Change the path for the OSM backup/restore scripts.

  • Alcatel BSS

    A1353-RA Network

    Administration Handbook

    OMC Document

    Procedural Handbook

    Release B9

    3BK 20903 AAAA PCZZA Ed.13

  • 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/Evolium.

    BLANK PAGE BREAK

    2 / 222 3BK 20903 AAAA PCZZA Ed.13

  • Contents

    ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    1.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.1.1 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.1.2 Using the OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    1.2 Maintaining the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.1 Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.2 System Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.2.3 Preventive Maintenance Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.2.4 HSI Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    2 Backup and Restore of OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    2.1.1 Types of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.1.2 Type and Rotation of Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.1.3 Backup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    2.2 Perform a Full or Incremental Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2.1 Perform a Full Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2.2 Schedule a Full Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.2.3 Perform an Incremental Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.2.4 Schedule an Incremental Backup from OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.2.5 Verify the Amount of Data Stored on Tape after an OMC Backup . . . . . . . . . . . . 31

    2.3 Perform a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.3.2 Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

    2.4 Prepare SUN StorEdge 3510FC Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Access Rights Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

    3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.2 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

    3.2.1 Default Password Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.2.2 Create New Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.2.3 Modify a Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.2.4 Delete Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.2.5 List Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.2.6 Display Global Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    3.3 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3.1 Add Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3.2 Reset User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.3.3 Delete Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.3.4 List Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.3.5 Display Current Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.3.6 Display Login Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.3.7 Display Last Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.3.8 Change Own Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.3.9 Assign Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.3.10 Remove Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.3.11 Unlock axadmin Account - Wrong Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

    3.4 OMC-R Application Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.4.1 BSSUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.4.2 MFSUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.4.3 RNUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.4.4 OAM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.4.5 AS CurrentUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.4.6 AS HistoricalUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    3BK 20903 AAAA PCZZA Ed.13 3 / 222

  • Contents

    3.4.7 IMT Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.4.8 SEC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.9 Other Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    3.5 OMC-R FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.1 SYSTEM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.2 DOC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.3 OWN_MRT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.4 DSMUSM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.5 OSM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.6 TELECOM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.7 OAM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.5.8 ASCURUSM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.5.9 PERF_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.5.10 ASHISUSM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.5.11 OSM_USER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.5.12 SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.5.13 ASHISUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.5.14 RNUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.5.15 BSSUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.5.16 MFSUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.5.17 TRACE_VIEWER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.5.18 OAM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.5.19 RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.5.20 MFSUSM_RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.5.21 BSSUSM_RESTRICTED_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.5.22 CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.5.23 ASHISUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.5.24 RNUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.25 BSSUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.5.26 MFSUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.5.27 ASCURUSM_CONFIGURATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5.28 ASCURUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5.29 ASCURUSM_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.5.30 HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.5.31 RNUSM_HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.5.32 BSSUSM_HW_EXT_RED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.33 SOFTWARE_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.34 BSSUSM_SOFTWARE_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.35 MFS_BACKUP_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.5.36 PRC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.37 RNUSM_PRC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.38 PRC_RESTRICTED_ACCESS_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.39 RNUSM_PRC_RESTRICTED_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.5.40 MLU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.41 RNUSM_MLU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.42 ACCESS_TO_UNIX_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.43 XTERM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.5.44 PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.45 PERF_VIEWER_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.46 RNUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.47 MFSUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.5.48 BSSUSM_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.5.49 RESTRICTED_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.5.50 BSSUSM_RESTRICTED_PERFORMANCE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . 833.5.51 COMMAND_MODE_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.5.52 COMMAND_MODE_FAD_A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.5.53 INHIBIT_OAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

    4 / 222 3BK 20903 AAAA PCZZA Ed.13

  • Contents

    3.5.54 INHIBIT_FAD_CONTROL FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.5.55 RNUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.56 UFM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.57 RNO_TB_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.58 OAM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.59 ASHISUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.5.60 MFSUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.5.61 BSSUSM_RI_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.5.62 BSSUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.5.63 ASCURUSM_INHIBIT_FAD_CONTROL_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.5.64 MULTI_OMC3_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.5.65 UFM_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.5.66 NPA_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.5.67 DCN_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.68 AS_ADMINISTRATION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.69 PROCESS_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.70 USER_AND_PLATFORM_MANAGEMENT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . 943.5.71 READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.5.72 RNUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.5.73 BSSUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.5.74 MFSUSM_READ_ONLY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.5.75 REMOTE_INVENTORY_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.5.76 ENSUSM_RI_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.5.77 FULL_MRT_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.5.78 Global_Log_Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.79 MFSSNMP_SUPERVISION_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.80 OAM_MRTG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.81 MFSUSM_NAVIGATE_MRTG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.82 IMT_CONF_GPU_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.5.83 IMT_CONF_MFS_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.84 IMT_ADMIN_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.85 IMT_PLATFORM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.86 IMT_GPU_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.87 IMT_MFS_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.5.88 IMT_MFS_ADMIN_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.89 IMT_CONF_READ_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.90 IMT_READ_CONF_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.91 IMT_MFS_PLATFORM_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.92 ACO_MNG_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.5.93 ACO_NTC_FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

    3.6 Operator Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.6.1 Operators window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.6.2 Edit window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

    3.7 Terminal Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.7.1 Create Terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.7.2 Profiles window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

    3.8 Operator Profile Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.8.1 Display All Available Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.8.2 Create Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.8.3 Delete Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.8.4 Display Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053.8.5 Modify an Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.8.6 Assign Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.8.7 Unassign Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

    3.9 Terminal Profile Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.9.1 Display All Available Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.9.2 Create Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

    3BK 20903 AAAA PCZZA Ed.13 5 / 222

  • Contents

    3.9.3 Delete Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.9.4 Display Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.9.5 Modify a Terminal Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093.9.6 Attach/Detach Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

    3.10 OAD Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113.10.1 Create OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113.10.2 Delete OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.10.3 Display OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123.10.4 Modify Access Rights to OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

    3.11 FAD Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.11.1 Create FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.11.2 Delete FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.11.3 Display FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.11.4 Modify FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

    3.12 Restore Default FADs and Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143.13 FTP Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153.14 Change FTP User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173.15 Non-OMC-R Users Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173.16 Activate MPM on OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

    4 Day-To-Day Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.1 Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

    4.1.1 Display Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.1.2 From the Hardware Inventory Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.1.3 From the Workstation Management Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

    4.2 Software Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.2.1 Display Software Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.2.2 Display Third Party Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.2.3 Display Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.2.4 Display Changed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.2.5 Display Binary Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

    4.3 Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.1 Capture Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.2 Display Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.3.3 Capture Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.3.4 Display Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.3.5 Lock/Unlock Failure Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.3.6 Delete Failure Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.3.7 Archive Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.3.8 Display Archived Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.3.9 Delete Archived Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

    4.4 Monitor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.4.1 Disk Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.4.2 Internet Protocol Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

    4.5 Start the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.6 Start OMC-R Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

    4.6.1 From a UNIX Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.6.2 From OSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

    4.7 Stop OMC-R Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.7.1 Whole OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.7.2 Shutdown USMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

    4.8 Stop the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.9 Start Application Process from DSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.10 Stop Application Process from DSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.11 Process and Platform Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.12 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

    4.12.1 Add Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.12.2 Remove Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

    6 / 222 3BK 20903 AAAA PCZZA Ed.13

  • Contents

    4.12.3 Add X Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.12.4 Remove X Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.12.5 Add Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.12.6 Remove Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.12.7 Define Station Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.12.8 Define User Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.12.9 Documentation Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.12.10 LDAP Hosts Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

    4.13 Configuration Parameter Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.14 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434.15 Clean Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444.16 Broadcast Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.17 Set Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.18 Run Multiple OMC-Rs from One HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

    4.18.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.18.2 Set UNIX Parameters on One OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.18.3 Connection Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.18.4 Creating a Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

    4.19 Logs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.19.1 View Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.19.2 Logs Merge on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

    4.20 Change NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534.20.1 Find NMC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534.20.2 Stop q3im Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534.20.3 Undeclare Current NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544.20.4 Declare New NMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

    4.21 List NMC and OMC Network Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.22 Alarm Sublist and Filter Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

    4.22.1 Alarm Sublists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564.22.2 Alarm Sublist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574.22.3 Pre-Defined Aging Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604.22.4 Change Default Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.22.5 Retrieve Original Default Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.22.6 Change Default for Existing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624.22.7 Retrieve Original Default for Existing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624.22.8 Add Alarm Sublist Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

    4.23 Navigate in a New Mozilla Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634.24 Secure External Workstation and User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

    4.24.1 Add Secure External Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.24.2 Secure External Workstation Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.24.3 Delete Secure External Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

    4.25 A1353-RA MRTG View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664.25.1 Main Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664.25.2 MRTG Index Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.25.3 Detailed Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

    4.26 Increase the Trace Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754.27 Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764.28 Security Impact on the A1353-RA Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

    4.28.1 AUTOMOUNT Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774.28.2 BOOTPARAMD Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

    4.29 Network Information Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785 Modify IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

    5.1 Impact and Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825.1.1 Impact on Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825.1.2 Duration of IP Address Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

    5.2 Modify the IP Address for the Entire Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835.2.1 Global Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

    3BK 20903 AAAA PCZZA Ed.13 7 / 222

  • Contents

    5.2.2 Modify the IP Address of the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835.2.3 Modify the IP Address of an X Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835.2.4 Modify the IP Address of the Master and Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 1845.2.5 Modify the IP Address of the BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895.2.6 Modify the IP Address of the MFS Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905.2.7 Modify the IP Address of the Cisco Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.2.8 Modify the IP Address of the NPA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.2.9 Modify the IP Address of the NPA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

    5.3 Modify the IP Address for One Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.3.1 Modify the IP Address of an X Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.3.2 Modify the IP Address of the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.3.3 Modify the IP Address of a Network Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.3.4 Modify the IP Address of the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.3.5 Modify the IP Address of the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.3.6 Modify the IP Address of the BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015.3.7 Modify the IP Address of the MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025.3.8 Modify the IP Address of the Cisco Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025.3.9 Modify the IP Address of the NPA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035.3.10 Modify the IP Address of the NPA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

    6 Administrative Tasks for MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2056.1 Configure Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2066.2 Display Visu-log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2076.3 Manage ASCII (OBSYNT) Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2076.4 Start/Stop MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

    6.4.1 Starting MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086.4.2 Stopping MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

    7 Backup/Restore MFS Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2097.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107.2 Backup MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

    7.2.1 Who Can Perform a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.2.2 O&M and Telecom Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.2.3 Size of Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.2.4 Duration of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

    7.3 Backup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.3.1 Backup to Local Disk on MFS Control Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.3.2 Upload to OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

    7.4 Restore MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137.4.1 Who Can Perform a Restore of the Configuration Files . . . . . . . . . . . . . . . . . . . . 2137.4.2 O&M Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137.4.3 Telecom Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137.4.4 Duration of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

    7.5 Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2147.5.1 Download from OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2147.5.2 Restore MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

    8 Upgrade Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188.2 Upgrade of Customer Documentation CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

    8.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188.2.2 Different Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

    8.3 Launch Documentation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2208.4 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

    8.4.1 No Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2208.4.2 Correcting Monitor Color Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

    8 / 222 3BK 20903 AAAA PCZZA Ed.13

  • Figures

    FiguresFigure 1: Installation, Backup and Restore Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 2: Type and Rotation of Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 3: Backup of Modified Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 4: Application Manager Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Figure 5: Example Create Action Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Figure 6: A1353-RA MRTG Main View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Figure 7: A1353-RA MRTG MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Figure 8: Detailed Statistics MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Figure 9: Detailed Statistics A9130 BSC Evolution View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

    3BK 20903 AAAA PCZZA Ed.13 9 / 222

  • Tables

    TablesTable 1: Preventive Maintenance Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 2: Types of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 3: Password Composition Rules Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Table 4: FTP server directory organization for omc3ftp , rno , pmuser and laser . . . . . . . . . . . . . . . . . . . . 116Table 5: FTP server directory organization for metrica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Table 6: Default account settings for non-OMC-R users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Table 7: Password policy for non-OMC-R users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Table 8: DSMUSM Features Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

    10 / 222 3BK 20903 AAAA PCZZA Ed.13

  • Preface

    PrefacePurpose The Administration Guide describes how to perform day-to-day administration

    of the A1353-RA including:

    Backup/restore

    Access rights

    Miscellaneous administration tasks

    MPM administration.

    Whats New 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.2) 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.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 (Section5.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 ofthe Master (Section 5.3.4) , Modify the IP Address of the Agent (Section

    3BK 20903 AAAA PCZZA Ed.13 11 / 222

  • Preface

    5.3.5) , Modify the IP Address of the HMI (Section 5.3.2.2) , Modify the IPAddress 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 helpregarding 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) sectionby 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 chapter 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 subchapters 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.2) .

    12 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 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 chapter 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.2) .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.1) , A9130 MFSEvolution (Section 5.2.6.2) , 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.2.1)A9130 BSC Evolution MRTG Index Page (Section 4.25.2.2)Detailed Statistics (Section 4.25.3)

    The following new sections are added:

    Operator Management (Section 3.6)Terminal Management (Section 3.7) .

    3BK 20903 AAAA PCZZA Ed.13 13 / 222

  • 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 restoreoperation

    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) .

    14 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 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 inRemove 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.1)MRTG Index Page (Section 4.25.2)Detailed Statistics (Section 4.25.3)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.

    3BK 20903 AAAA PCZZA Ed.13 15 / 222

  • Preface

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

    Alcatel operations and maintenance concepts

    Telecommunications engineering

    UNIX concepts.

    16 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 1 Introduction

    1 Introduction

    Read this section before you start the procedures.

    3BK 20903 AAAA PCZZA Ed.13 17 / 222

  • 1 Introduction

    1.1 Before You Start

    1.1.1 Access RightsYou must have the administrator profile named axadmin_special_profileassigned to you for access to the OMC-R.

    1.1.2 Using the OSMOn 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 underlinedyou 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 areasked to decide which workstation you want information for).If the button is gray, the name is underlined and you must click on thename 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 towhere 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 SpaceAlthough 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 ).

    18 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 1 Introduction

    1.2.2 System ResourcesEach 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 ScheduleThe 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, MasterIf OSM, any machine

    -

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

    In UNIX, MasterIf 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, MasterIf 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 MasterIf 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.13 19 / 222

  • 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 Replacement1. In case of HSI network board failure, if the old board is X1155A AND there is

    not a similar one available, the new generic board X1355A must be used.

    20 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 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.13 21 / 222

  • 1 Introduction

    22 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    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.13 23 / 222

  • 2 Backup and Restore of OMC-R

    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 .

    24 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    2.1.1 Types of BackupThe 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.13 25 / 222

  • 2 Backup and Restore of OMC-R

    2.1.2 Type and Rotation of TapesEach 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.

    123456

    123456

    123456

    12

    12

    12

    12

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    123456

    Set 1 Set 2 Set 3

    Full Backup 1 Full Backup 2 Full Backup 3

    IncrementalBackup 1.1

    IncrementalBackup 1.2

    IncrementalBackup 1.3

    IncrementalBackup 1.4

    IncrementalBackup 2.1

    IncrementalBackup 2.2

    IncrementalBackup 2.3

    IncrementalBackup 2.4

    IncrementalBackup 3.1

    IncrementalBackup 3.2

    IncrementalBackup 3.3

    IncrementalBackup 3.4

    .

    .

    .

    .

    .

    .

    .

    .

    .

    Figure 2: Type and Rotation of Tapes

    26 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    2.1.3 Backup ProcessIn 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

    Incremental Backup 1.2

    Incremental Backup 1.3

    Full Backup 2.0

    Back

    s up

    file

    s wi

    thtim

    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, in

    order to keep all the OMC-R data consistent. UNIX continues to operate.2. Mirrored disks are detached. For Veritas Filesystems, a "snapshot" is

    taken 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 one

    disk 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 backup

    are 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.13 27 / 222

  • 2 Backup and Restore of OMC-R

    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 AgentAn 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 sta

    where 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 .

    28 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    2.2.1 Perform a Full Backup from OSMNote: 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 justafter 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 completedthe backup is complete. If the message contains the text:

    Backup completed: warningthe backup is incomplete. 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:

    FailureThe 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.13 29 / 222

  • 2 Backup and Restore of OMC-R

    2.2.2 Schedule a Full Backup from OSMNote: 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: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 -> Schedule Backup .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. 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: Thetape is full. Please insert next tape and just after pressOK 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 OSMProcedure To perform an incremental 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 -> Incremental 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 ] .The system carries out the backup steps.

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

    30 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    2.2.4 Schedule an Incremental Backup from OSMProcedure To schedule an incremental backup from OSM:

    1. Log in as an administrator.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 .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. 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.

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

    2.2.5 Verify the Amount of Data Stored on Tape after an OMC BackupThe amount of data stored on a tape after an OMC backup can be verifiedfrom Master .From OSM Administration Facilities:1. Log in as an administrator.2. Insert the tape (if not already inserted) in the tape drive of the Master .3. Select Administration -> Backup/Restore -> Get Tape Usage4. In the Device field, the path to the default tape drive is typed. If the tape

    drive 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 text

    fields represents the final values.

    3BK 20903 AAAA PCZZA Ed.13 31 / 222

  • 2 Backup and Restore of OMC-R

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

    B9 CD1 and CD3 must be availableRestores 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 thesystem failure.This is not part of the restore procedure.

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

    B9 A1353-RA CD1 and CD3 corresponding with the installed softwareversion.

    The restore script: MF-improved_restore.sh (contained on CD3)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 - RAAdministrator 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.

    32 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    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 StorEdge

    3510FC 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 following

    steps:

    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 not

    automatically done:init 6

    Log in as root user.7. Insert B9 CD3 and copy the restore scripts:

    cd /var/tmpcp /cdrom/cdrom0/MF-improved_restore_OMC.sh .cp /cdrom/cdrom0/MF-improved_restore_OMC.pl .cp /cdrom/cdrom0/x_message_restore .cp /cdrom/cdrom0/INDSplmod_*.gz .gzip -cd INDSplmod_*.gz | cpio -icdumDpkgadd -d .

    Install the package INDSplmod_ .

    3BK 20903 AAAA PCZZA Ed.13 33 / 222

  • 2 Backup and Restore of OMC-R

    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 syncWait 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:

    /var/tmp/MF-improved_restore_OMC.pl -dev:-skipcheck

    Where 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 and push ENTERin the restore window. Just after push OK button. Performthe following:

    Push the eject (unload) button of the tape drive and replace the tape.Insert the next tape, open a new terminal and type:

    mt -f staCheck that the tape was loaded.

    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.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 syncWait 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:

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

    34 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    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. Delete the UNIX lock files in the following directory:

    cd /alcatel/var/share/ntermrm .omc3_session_[hostname]*

    18. 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 a

    Terminal 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 the

    A1353-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.

    3BK 20903 AAAA PCZZA Ed.13 35 / 222

  • 2 Backup and Restore of OMC-R

    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 of

    your 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: COM1Bits per second: 38400Data bits: 8Parity: noneStop bits: 1Flow control: Hardware -----> Press Ctrl + L to refresh window

    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 connectionoption?Select NO

    The following message appears: Change made to these settingswill NOT take effect until the controller is RESET. Priorto resetting the controller, operation may not proceednormally. 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").

    36 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 2 Backup and Restore of OMC-R

    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.13 37 / 222

  • 2 Backup and Restore of OMC-R

    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.

    38 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 3 Access Rights Management

    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.13 39 / 222

  • 3 Access Rights Management

    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). Thesame 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 - lockedor 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 lengthMAX_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 expiresWARNING_DAYS (*) 8 Number of days warning before password expires

    40 / 222 3BK 20903 AAAA PCZZA Ed.13

  • 3 Access Rights Management

    (*) : used from LDAP password policyTable 3: Password Composition Rules Description

    The default special character list is:$[]{}()*+?^&=-!@%_~,:;.|\/"

    3BK 20903 AAAA PCZZA Ed.13 41 / 222


Recommended