Administration Guide NMC2 R161 Ed03

Nokia
A1300 CMC 10
ADMINISTRATION GUIDE
OPERATOR GUIDE
3BL 24534 AHAA PCAGA Ed.03

Status RELEASED 10/12/2020
Mnemonic NM2ADM
All rights reserved. Passing on and copying of this document, use and
communication of its contents not permitted without written authorization
from Alcatel-Lucent.
2 / 197 3BL 24534 AHAA PCAGA Ed.03

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1 Introduction to technical concepts and principles of the document . . . . . . . . . . . . . . . . . . . . . 15
1.1 Command conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Role of the administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3 Host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 System management processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5 Supported NMC2 hardware configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6 Services in distributed architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6.1 DSS-HMS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7 Server shutdown and restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.1 Shutting down and reboot a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.2 Shutting down complete a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.3 Restarting a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.4 Shutting down or restarting a server gracefully . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.8 Maintenance tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Online user documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1 Installing the ADES documentary collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 Removing the ADES documentary collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3 General NMC2 tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1 Accessing the TMN-OSs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Managing an NMC2 instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.1 Starting permanent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.2 Stopping permanent processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.3 Launching the system configuration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.4 Viewing information about an NMC2 instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.5 Defining the maximum number of operators logged . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Setting a personal printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4 Synchronizing systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5 How to change the system date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4 Managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1 Accessing the operator administration application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Defining your own “User password policy” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.1 Password Aging Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.2 Password Format Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3 Creating a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.4 Password definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.5 Updating a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.6 Deleting a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.7 Changing the password of a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.8 Assigning a new password in case of loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.9 Activating an account with expired password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.9.1 Procedure for PARISC servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.9.2 Procedure for ITANIUM servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5 Managing sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1 Accessing the session management application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2 Customizing the workstations area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3 Broadcasting a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.4 Viewing good logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.5 Viewing bad logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.6 Locking the workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.6.1 Manual lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.6.2 Automatic lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3BL 24534 AHAA PCAGA Ed.03 3 / 197

Contents
5.7 Unlocking a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.8 Forcing the user logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6 ProcessMonitoring Control (PMC) tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1 Functional groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1.1 Dependencies between groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.1.2 Example of dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.2 Functional states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.4 Accessing the PMC tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.5 PMC main window description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.5.1 Menu and toolbar area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.5.2 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.5.3 Selected item information area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.6 PMC command line tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7 Starting an item or a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.8 Stopping an item or a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.9 Controlling the processes of an NMC2 instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.9.1 Starting the process control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.9.2 Stopping the process control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.9.3 Starting the automatic process control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.9.4 Stopping the automatic process control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.10 Executing commands on agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.11 Synchronizing configuration and data file information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.12 Viewing information on agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.12.1 Viewing basic information on an agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.12.2 Viewing trace files of a selected agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.13 Viewing the PMC log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.14 Setting thresholds for CPU charge and disk occupation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7 Administration of redundant Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.1 Startup/shutdown of a redundant Network Management System . . . . . . . . . . . . . . . . . . . . . . . . 77
7.1.1 Starting a whole Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.1.2 Shutting down a whole Network Management System . . . . . . . . . . . . . . . . . . . . . . 78
7.1.3 OS Resilience application start on a single NMS instance . . . . . . . . . . . . . . . . . . . 78
7.1.4 OS Resilience application stop on a single NMS instance . . . . . . . . . . . . . . . . . . . 78
7.1.5 OS Resilience application Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.2 System configuration updating on a resilient NMS instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.3 Switchover activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.4 Backup and restore on a resilient Network Management System . . . . . . . . . . . . . . . . . . . . . . . . 81
7.4.1 Backup procedure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.4.2 Restore procedure management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.5 Replicated data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8 Managing the scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.1 Accessing the scheduler management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.2 Creating a new scheduler plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.3 Editing a scheduler plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.4 Validating a scheduler plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.5 Stopping a scheduler plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.6 Deleting a scheduler plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.7 Using crontab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.8 Using the NECTAR OS calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
9 SMF Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.1 Overview of log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.2 Log Management user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.3 Managing log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.3.1 Viewing log file information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4 / 197 3BL 24534 AHAA PCAGA Ed.03

Contents
9.3.2 Archiving log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

9.3.3 Deleting log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.4 Managing log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.4.1 Filtering log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.4.2 Updating the log records area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9.4.3 Viewing log record information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
9.4.4 Sorting log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
9.4.5 Changing the display mode for all log records . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
10 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
10.1 Trace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
10.1.1 Accessing the trace management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10.1.2 Editing trace levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
10.1.3 Managing trace files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
10.1.4 Viewing a trace file statically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.1.5 Viewing a trace file dynamically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
10.1.6 Clearing contents of a trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
10.2 OS snapshot management/Failure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
10.2.1 Accessing OS snapshot management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
10.2.2 Taking an OS snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
10.2.3 Managing the OS snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
10.2.4 Setting the maximum number of OS snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . 114
10.3 Cleanup management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
10.3.1 Accessing the cleanup management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
10.3.2 Viewing details of files of a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
10.3.3 Cleaning up files from a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
10.4 CORBA script management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
11 Managing printers and X25 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
11.1 Printer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
11.1.1 Declaring a network printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
11.1.2 Declaring a local printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11.1.3 Removing a printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
11.1.4 Setting a printer as default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
11.2 X25 link configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
12 Q3ES administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
12.1 Q3ES subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
12.1.1 Offered/used services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.1.2 External information model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.1.3 Mechanisms to support offered services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.1.4 Q3ES interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.1.5 Multi instances of Q3ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
12.2 Q3ES administration user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
12.2.1 Accessing the Q3ES user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
12.2.2 Q3ES main windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
12.3 OSS management in Q3ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
12.3.1 Declaring an OSS in Q3ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
12.3.2 Modifying an OSS in Q3ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.3.3 Deleting an OSS in Q3ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.4 Log FTAM management (reduced interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.4.1 Creating a log FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
12.4.2 Deleting a log FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
12.4.3 Browsing a log FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
12.4.4 Deleting a log FTAM record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
12.4.5 Sending a log FTAM record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
12.4.6 Viewing Log FTAM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
12.4.7 Changing the transfer type of a log FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
12.5 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3BL 24534 AHAA PCAGA Ed.03 5 / 197

Contents
12.5.1 Accessing the log management user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

12.5.2 Deleting a log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
12.6 Q3ES information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
12.7 EFD management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
12.7.1 Accessing the EFD user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
12.7.2 Deleting an EFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
13 BDH management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
13.1 Introduction to BDH management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
13.2 BDH management user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
13.2.1 Accessing the BDH management user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
13.2.2 BDH Management main windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
13.3 OSS management in BDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
13.3.1 Declaring an OSS in BDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
13.3.2 Modifying an OSS in BDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
13.3.3 Deleting an OSS in BDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
13.4 Bulk data collection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
13.4.1 Creating a bulk data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
13.4.2 Modifying the parameters of a bulk data collection . . . . . . . . . . . . . . . . . . . . . . . 153
13.4.3 Deleting a bulk data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
13.5 BDH file management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
13.5.1 Accessing the BDH file management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
13.5.2 BDH file management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
13.5.3 Deleting a BDH file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
13.5.4 Exporting a BDH file to DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
13.5.5 Importing a BDH file from DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
14 Connecting external applications via CORBA SNM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
14.1 NMC2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
14.2 External OS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
14.3 “X733” vs “X733 extended” alarm format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
14.4 External OS connection problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
15 OS security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
15.1 Activating/deactivating a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
15.2 Using the FTP flow control server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
15.3 Using the Secure Shell services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
15.4 NFS ACTIVATION / DEACTIVATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
15.4.1 NFS ACTIVATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
15.4.2 NFS DEACTIVATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
15.5 Trusted-UNIX configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.5.1 How to Check the Activation of Trusted-UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.5.2 How to Activate Trusted-UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
15.5.3 How to check that Trusted-UNIX is activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
16 NMC2 supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
16.1 Introduction to NMC2 supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
16.2 NMC2 software supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
16.2.1 nmc_SOS monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
16.2.2 Os1300nmc NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
16.2.3 NMC2 internal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
16.2.4 Alarms troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
16.3 NMC2 hardware supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
16.3.1 Introduction to System Management Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . 179
16.3.2 Checking the hardware status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
17 CONFIGURATION OF MOZILLA FOR TELNET (mozex plugin) . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Appendix A: Access to the web console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Appendix B: How to extend partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6 / 197 3BL 24534 AHAA PCAGA Ed.03

Contents
Appendix C: Appendix C: How to access to the MP interface for ITANIUM servers . . . . . . . . . 189
C.1 How to configure ILO 2 TO MP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
C.2 How to access to the MP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
3BL 24534 AHAA PCAGA Ed.03 7 / 197

Figures
Figures
Figure 1: Example of the system response to a command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2: Maintenance directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 3: Device Name of source media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 4: Collection type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 5: TMN-OSs Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 6: System information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 7: Maximum operators management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 8: Set personal printer window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 9: Operators Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 10: Warning of double launch of Operators Admin window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 11: Sistem Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 12: Sistem Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 13: Auditing and Security Attributes Configuration Tool window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 16: Create User dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 17: Update a user dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 18: Delete current user dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 19: Change Your Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 20: EFI main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 21: EFI booting prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 22: Session Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 23: Workstations sub-menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 24: Broadcast Message dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 25: Example of a Broadcast Message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 26: Good Logins dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 27: Lock Screen dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 28: Lock options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 29: Unlock Screen dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 30: Force Logout dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 31: Process Monitoring Control main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 32: Menu and toolbar area of the PMC tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 33: Work area part of the PMC main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 34: Node health status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 35: Managed NMC2 instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 36: Example of a PMC group list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 37: Example of a PMC agent list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 38: Information on a PMC agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 39: Select agent trace file window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8 / 197 3BL 24534 AHAA PCAGA Ed.03

Figures
Figure 40: Trace file window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 41: Trace file too big window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 42: PMC2 log file window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 43: Log file size too big window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 44: Set Threshold window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 45: Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 46: New plan dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 47: Current date dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 48: Edit plan dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 49: Scheduler window showing an active plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 50: Scheduler window showing only deactivated plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 51: Delete plan dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 52: Life Cycle of a Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 53: SMF Log Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 54: SMF Log Management window with log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 55: LOG File Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 56: Move log to save Area dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 57: LOG:LOG Records Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 58: LOG:LOG Record Information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 59: Log Records Area with full details displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 60: Trace File Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 61: Trace: Trace Levels Edition dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 62: Static View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 63: Search_dialog dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 64: Dynamic View dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 65: Trace File Management dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 66: OS Snapshot Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 67: Set Maximum Number of Snapshots on Workstation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 68: Cleanup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 69: Files to be cleaned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 70: SMH console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 71: Sistem Managementwindow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 72: Sistem Management window: Configutre Printers Or Plotters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 73: Add Parallel Printer/Plotter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 74: Q3ES Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Figure 75: Example of a Q3ES Management main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 76: Q3ES: OSS Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 77: Q3ES: OSS Parameters dialog box: General Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 78: Q3ES: OSS Parameters dialog box: OSS Address 1 Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 79: Q3ES: Log FTAM Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3BL 24534 AHAA PCAGA Ed.03 9 / 197

Figures
Figure 80: Q3ES: Log FTAM Parameters dialog box: General Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 81: Q3ES: Log FTAM Parameters dialog box: Parameters Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Figure 82: Q3ES: Log FTAM Browsing window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Figure 83: Q3ES: Log FTAM Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 84: Q3ES: Log Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 85: Q3ES Informations window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 86: Q3ES: EFD Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 87: BDH Administration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 88: Example of a BDH: OSS Management main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 89: BDH: OSS Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 90: BDH: OSS Declaration dialog box (OSS Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 91: BDH: OSS Declaration dialog box (USER Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 92: BDH: Bulk Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 93: BDH: Bulk Declaration dialog box (Bulk Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 94: BDH: Bulk Declaration dialog box (Files Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 95: BDH: File Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 96: BDH: File Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 97: BDH: Bulk Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 98: Open Connection dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 99: Connection Settings dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 100: NE Os1300nmc creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 101: NE Os1300nmc creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 102: SMH Home tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 103: Cooling status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 104: Cooling events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 105: Disks status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 106: Mark telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 107: “mozex preferences” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Figure 108: MP main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 109: MP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 110: Connect to MP interface window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 111: Commands list of the MP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
10 / 197 3BL 24534 AHAA PCAGA Ed.03

Tables
Tables
Table 1: Services in distributed architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 2: Levels of dependencies among groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 3: Functional states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 4: PMC icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 5: PMC command line parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 6: Origin of the available log types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 7: Information traced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 8: Secure Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 9: Alarms troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
3BL 24534 AHAA PCAGA Ed.03 11 / 197

Tables
12 / 197 3BL 24534 AHAA PCAGA Ed.03

Preface
Preface
Purpose This document describes the tasks to be done by the system administrator to man-
age and monitor the Alcatel-Lucent 1300 CMC E10 processes.
This document concerns the Alcatel-Lucent 1300 CMC E10 from rel. 1.3.3
Audience This document is intended for the Alcatel-Lucent 1300 CMC E10 administrator.
It is recommended having some knowledge of UNIX environment.
This document does not replace a training on Alcatel-Lucent 1300 CMC
E10 administration.
Contents This document is organized as follows:

Chapter 1 describes the Alcatel-Lucent 1300 CMC E10 processes and lists as-
sociated management services that are offered to the system ad-
ministrator.
Chapter 2 describes how to install/uninstall the online documentation.
Chapter 3 describes the general tasks accessible from the main A1300 CMC
E10 window
Chapter 4 describes the operations necessary for managing users
Chapter 5 describes the operations necessary for managing sessions
Chapter 6 describes the operations necessary for monitoring processes.
Chapter7 describes the operations necessary for High Availability Adminis-
tration.
Chapter 8 describes the operations necessary for managing periodic actions
with the scheduler management tool.
Chapter 9 describes the operations necessary for managing SMF logs
Chapter 10 describes the maintenance tools to manage traces, OS snapshots
and cleanups.
Chapter 11 describes how to configure printers and manage X25 links.
Chapter 12 describes the Q3ES administration.
Chapter 13 describes the BDH management.
Chapter 14 describes how to connect external applications to A1300 CMC E10.
3BL 24534 AHAA PCAGA Ed.03 13 / 197

Preface
Chapter 15 describes the access to the FTP, telnet and rlogin services.
Chapter 16 describes the supervision of NMC2 system
Chapter 17 describes the CONFIGURATION OF MOZILLA FOR TELNET (mozex
plugin)
Appendix give the procedure to access the web console.
A
AppendixB give the procedure to extend partitions manually.
Appendix C give the procedure to configure and access to the MP interface for
ITANIUM servers.
Abbrevia- gives the meaning of the acronyms and abbreviations used in this
tions document.
Index gives another way to get information from a word or a concept.
Referenced documents The documents referenced in this guide are as follows:

NMC Backup online Administration guide, BOLADMGOP
Alcatel-Lucent 1300 CMC E10 Map Management operator guide, NM2MAP-
GOP
Alcatel-Lucent 1300 CMC E10 Log Management operator guide, NM2LOG-
GOP
Alcatel-Lucent 1300 CMC E10 Security Management operator guide,
NM2SECGOP
Alcatel-Lucent 1300 CMC E10 Alarm Management operator guide,
NM2ALAGOP
NECTAR OS MML User Guide, ALNOSMLGOP
HP Secure Web Console (J3591A)
ALMAP SMF 2.0 User’s Guide Operator Manual, SMF 2.0 UG
Configuration and use of Remote Desktop user guide, REMOTGOP
Typographical conventions The following typing conventions are used in this guide :
text in italics: document titles, window names and field values
text in bold -i tali cs : menu items, buttons and field names
text in bold important information, headings of lists and paragraphs that are
not numbered
Terminological conventions The following terminologic conventions are used in this guide :
NMC2 is often used for shorts instead of Alcatel-Lucent 1300 CMC E10. In
this guide, sometimes NMC2 is used.
<NMS_INSTANCE_DIR> is a term which represents the product root directory
: /usr/Systems/NMC2_1
14 / 197 3BL 24534 AHAA PCAGA Ed.03

1 Introduction to technical concepts and principles of the document
1 Introduction to technical concepts and principles of

the document
This chapter describes the conventions, concepts and principles on which the op-
erator tasks of this document are based. This chapter describes:
command conventions (see section 1.1)
command conventions (see section 1.2)
host name (see section 1.3)
system management processes (see section 1.4)
supported hardware configurations (see section 1.5)
the services available in distributed architectures (see section 1.6)
server shutdown and restart (see section 1.7)
maintenance tools (see section 1.8)
1.1 Command conventions

This manual sometimes indicates the commands that have to be typed out by
the system administrator in a UNIX command shell. To avoid any ambiguity, the
following conventions are used:
The UNIX prompt is chosen as the # sign.
Commands that are typed out by the system administrator will be in the bold
courier font preceded by the UNIX prompt.
Variable names will be in the courier italic font. They will usually represent
server hostnames or process names.
For example, the UNIX command "date" is written # date [CR].

The carriage return sign [CR] indicates that the <Return> or <Enter> key is
pressed on the keyboard.
The system responses in general will be displayed as shown in figure 1.
3BL 24534 AHAA PCAGA Ed.03 15 / 197

Figure 1: Example of the system response to a command
1.2 Role of the administrator

The role of the administrator is to:
manage the system and keep the OS up and running:
process monitoring and configuration
log management
trace management
backup/restore operations
NE maintenance (software download)
reconfigurations (processes)
perform preventive maintenance operations:

backup: to minimize the failure consequences and to be able to start up
the system as quickly as possible in the case of a power supply failure for
example
cleanup: to avoid file system full occurrence or hardware failures
perform corrective maintenance operations in the case of a:

power supply failure
file system full
hardware failures (disk crash, SCSI errors)
software failures (Panic UNIX, application bug)
1.3 Host name

The host name cannot be modified after installation.
There is no way for the administrator to modify the host name, except by doing a
new installation.
16 / 197 3BL 24534 AHAA PCAGA Ed.03

1.4 System management processes

Management services are offered to the system administrator to:
start/stop the NMC2 system
get the process startup results from the servers composing the system
start/stop processes on servers
get process status results for a server or for the NMC2
perform backup/restore operations of data
get troubleshooting information
Each of the processes that constitute the NMC2, treats a particular functionality of
the system. Three types of processes can be identified:
General processes
They correspond to the functional parts of the operation. They control the
data processing and the data persistency. Some of these processes are started
automatically on launching of the system. They run independently of the user
session and are controlled through PMC process management features (Local
Registration File) and by the NMC2 application manager PMC.
PMC manages single processes, groups of processes or subsystems. A group
of processes is a set of dependent processes. If a process of the group is
launched then all the other processes of this group are also launched. If it is
stopped, the group stops. A subsystem is also a group of processes but they
are independent. When one of them crashes, the others are not affected.
Presentation processes
They control the Human Machine Interface (HMI) of an application. The pre-
sentation processes are started at user login, on explicit request by the user or
as a result of navigation between different functions of the system. The pro-
cesses that can be started by a user depend on his/her access rights.
These processes have a lifespan contained in a user session.
The failure of a presentation process is reported to the operators using that par-
ticular presentation process. Generally, the failure of a presentation process
results in the disappearance of the graphical user interface associated to it.
Presentation processes are not supervised by PMC. They cannot be restarted
automatically. In the case of a failure, they have to be restarted manually.
Note: When a presentation process fails it is not always stopped. The user has to check
if it is still running, and eventually ’kill’ it.
Monitoring processes
They are the processes that monitor the general processes composing the
NMC2. They detect the failed processes and report the failure to the NMC2
system administrator via PMC USM.
The allocation of the general processes on the servers is recorded in a PMC con-
figuration file that can be edited. This file contains information on the different
processes. It is not recommended to modify this file.
3BL 24534 AHAA PCAGA Ed.03 17 / 197

1.5 Supported NMC2 hardware configurations

The NMC2 hardware configurations are based on servers without screen that can
run presentation, application or communication processes, and workplaces.
Servers The NMC2 servers are based on HP9000 enterprise servers. There are three types
of NMC2 servers:
Element and Network Management Server (ENMS)
In the NMC2, the role of the ENMS depends on the configuration of the system
presented later on.
Network Management Servers (NMS)
The NMSs run application processes in the case of a distributed configuration
for large networks.
Human Machine Interface Management Servers (HMS)
The HMSs only run application processes (USMs) whose lifespan is contained
in a user session. They are not subject to any system management operations.
HMS can be added to the system dynamically (online).
An HMS can support several operator workplaces (OWP).
Workplaces Workplaces (WP) represent PCs intended for operators (OWP) and administrators
(AWP). A WP can display the graphical views of the USM that is running on the
servers.
An OWP is a PC with a UNIX emulation (Exceed and/or Metaframe and/or
GoGlobal).
An AWP is a PC with a UNIX emulation (Exceed and/or Web Console and/or MP
interface and/or GoGlobal).
Supported Configurations Three configurations may exist :

the Single Server System (SSS)
[ENMS] + [AWP] + [OWP]...[OWP]
This configuration is recommended for small and medium networks with less
than 24 OWPs. It is composed of:
one ENMS hosting the client and server parts of all the NMC2 applications
one AWP connected to the ENMS
OWPs connected to the ENMS
the Distributed Server System (DSS) with HMS

[ENMS] + [AWP] + [HMS1] + [HMS2] + [OWP]...[OWP]
This configuration is recommended when a single server cannot address the
customer configuration. It is composed of:
one ENMS running the server part of all the NMC2 applications
one AWP connected to the ENMS
one or two HMSs running the client part and the USMs
OWPs connected to the HMS(s)
18 / 197 3BL 24534 AHAA PCAGA Ed.03

Connecting the Workplaces An OWP is always installed with the IP address of the HMS on which it depends.
In DSS-HMS configuration, an AWP must be installed with the IP address of the
ENMS.
Specific ENMS Services Some services are available only from the ENMS . They are listed hereafter:
printer configuration (see section 11.1)
X25 configuration (see section 11.2)
Q3ES administration (see chapter 12)
NSAP address configuration (refer to the Alcatel-Lucent 1300 CMC E10 Map
Management operator guide, NM2MAPGOP)
Server Management In order to know the status of the servers, the administrator must declare then
supervise them by means of the map management application, from the AWP.
In the case of a high availability configuration, the servers must be declared with
their real IP address (not the virtual address of the cluster).
The management of the system processes is done by using the Process Monitoring
Control (PMC) application that enables the supervision of each NMC2 server. They
can be used from any WP by the administrator but only if the ENMS is running.
Operators who have access rights to UNIX a normal UNIX command shell (called
command shell in this document), where commands are typed.
All the messages forwarded to the console are saved in log files (e.g. syslog.log).
They can be visualized by the administrator, by using a text editor.
1.6 Services in distributed architectures

There is 1 type of distributed architecture in the A1300 CMC E10 :
DSS-HMS architecture
The SSS architecture is not a distributed architecture but a standalone architecture.
The following table summarizes the available services on each server in different
architectures. The optional applications are Traffic management, Trouble Ticket-
ing and Software management.
Table 1: Services in distributed architectures
Architecture Server type Manages what
SSS ENMS All CMC E10 functions (CMC E10 core and optional ap-
plications)
DSS-HMS ENMS All CMC E10 functions
HMS All CMC E10 functions except SWM. The number of HMS
servers can be 1 or 2.
3BL 24534 AHAA PCAGA Ed.03 19 / 197

1.6.1 DSS-HMS architecture

This architecture is composed of 1 ENMS server and several HMS servers (maxi-
mum 2).
All administration services (BDH administration, Q3ES administration, X25 config-
uration, interferences installation and so on) must be done from the ENMS server.
All exploitation services must be done from the HMS servers except for the Software
management optional application (which is available only from the ENMS).
Profile declaration
In this architecture, a new security profile must be declared from the ENMS via
SEC USM.
User declaration
A new user must be declared from the ENMS via SMF USM (see chapter 4.3).
Note: While declaring users in SMF USM, the administrator must pay attention to which
server the user will be authorized to log in.
Changing password
To change its password in this architecture, the user must change it from the HMS
server via Global Actions menus (see chapter 4.7).
1.7 Server shutdown and restart

The shutdown and restart of a server may be necessary if the attempt to relaunch
some processes fails.
If required to stop the server (Ex: in forecast of a power supply cut-off), apply the
shutdown complete with halt and power off the server
The consequence of a server shutdown is that the administrator will have to restart
the server before any operator can login.
1.7.1 Shutting down and reboot a server

Prerequisites: you must have the password for the user “root”.
To shut down a server
1. Log in as axadmin.
2. Broadcast a warning to all the users to ask them to log out (see section 5.3).
3. Shutdown all the application processes by using the menu path:
OS -> S top S y stem
4. Shut down the server by entering the command lines:
# su - root [CR]
# shutdown -r now [CR]
The -r option will cause the reboot of the station.
1.7.2 Shutting down complete a server

Prerequisites: you must have the password for the user “root”.
Before stopping the server, a recent full back up must be present
20 / 197 3BL 24534 AHAA PCAGA Ed.03

To shut down a server

1. Log in as axadmin.
2. Broadcast a warning to all the users to ask them to log out (see section 5.3).
3. Shutdown all the application processes by using the menu path:
OS -> S top S y stem
4. Log as root
5. In the Unix terminal launch the command: shutdown –h –y
6. Press the button power (Off) in the server
1.7.3 Restarting a server

Server restart is done in two possible cases:
a) Following a complete shutdown by the administrator.
Press the button Power (On) to start the server
Log as axadmin on the server
Start all the processes: OS -> S tart S y stem
b) Following a server crash
A server crash can occur due to:
a power supply failure
a UNIX panic
a disk crash
After a crash, pay attention to the messages indicating a disk corruption. If fsck is
required, that means the integrity of the NMC2 application can not be assumed
any longer. In such a case it is recommended to perform a full system restore.
In all these cases, after a server reboot, the third party software products are
restarted automatically.
The NMC2 processes have to be relaunched manually by using the Process Mon-
itoring function.
All the stages in the relaunching of the server processes are displayed in trace files
that store all the events occurring in the process of the server.
1.7.4 Shutting down or restarting a server gracefully

To shut down gracefully / restart the NMC2
1. Stop the processes via PMC before rebooting
2. Restart the processes manually .
1.8 Maintenance tools

Several tools are provided with the NMC2 to handle common maintenance tasks.
3BL 24534 AHAA PCAGA Ed.03 21 / 197

The maintenance directory can be located under the <NMS_INSTANCE_DIR>

root directory. This directory (<NMS_INSTANCE_DIR>/maintenance) is dedicated
to the collection and the recording of all data concerning the system mainte-
nance. The data is distributed in various sub-directories located under the main
maintenance directory (see figure 2): in this figure $OSCOREDIR=<NMS_IN-
STANCE_DIR>
Figure 2: Maintenance directory
backup on the slave server this directory will be empty. On the

master server, this directory will contain the backup
data which is formatted by the UNIX command ’tar’
and compressed.
maintenance/ the UNIX files are saved in this sub directory.
maintenance/trace current trace and dataflow files.
maintenance/log log files.
maintenance/failure saving (of traces, of ; etc.) when a process fails. The
name of the files (directories) located in this sub-di-
rectory are conform to the format date_time (e.g.
199802101455), for the date and time of the anom-
aly. Two directories are used for the failure saving.
First the saving is performed on each server in the
maintenance/failure/local directory, then the saved
files are transferred to the master server in the main-
tenance/failure/global directory. By this way if the
communication between the master server and an-
other server is down, the administrator can retrieve
the locally saved files in manual mode.
For each rubric, the tools management provided by SMF enable the visualization,
the saving and the deletion of the corresponding files or directories (see chapter
10).
22 / 197 3BL 24534 AHAA PCAGA Ed.03

2 Online user documentation

This chapter explains how to install and remove the ADES documentary collection.
The collection must be installed on each server.
2.1 Installing the ADES documentary collection

To install the ADES documentary collection:
1. Log in as the user root.
2. Mount the ADES reader (for e.g.):
hostname,sys,root # bash
root@hostname$ mountNMC /SCINSTALL/sc-
nfs/isos/new/3BL492172216_R160_FR_ADES_V2.iso y
3. Go to the ADES script directory: cd /opt/ades/script
4. Launch the installation script:
./install_collect
5. Select the Device Name of your source media according to the menu dis-
played, see figure 3).:
Figure 3: Device Name of source media
6. Three collection types are offered : NEDOC, OSDOC or NIL. Choose the
collection type you are going to install.
Figure 4: Collection type
Enter the collection type you are going to install or NIL: OSDOC (for e.g.)
3BL 24534 AHAA PCAGA Ed.03 23 / 197

Copying the collection NMC2 on the disk...
There can be only one collection of type "OSDOC" installed. The collection is
copied from the CD-ROM to the disks.
7. If you choose "NEDOC", a list of NE Types and Releases are displayed. This
list corresponds to the list of NE types and Releases PNM is configured with.
Choose the neType/neRelease associated to the collection you are installing.
2.2 Removing the ADES documentary collection

To remove the ADES documentary collection
1. Log in asrooton the host.
2. Go to the ADES script directory:
cd /opt/ades/script
3. Launch the removing script:
./remove_collect
4. A list of installed collection is displayed. User must choose the reference of
collection to remove.
5. A confirmation of the collection removal is requested, if you confirm, the
collection is removed from the disks.
This procedure also covers the special case when a documentary collection gath-
ers the documentation of several NE types and releases, meaning you have to
launch the remove_collect script only once.
24 / 197 3BL 24534 AHAA PCAGA Ed.03

3 General NMC2 tasks

This chapter describes the general NMC2 tasks: The administrator can manage
all system functions from the TMN Management window.
This chapter describes:
how to access the TMN-OSs window (see section 3.1)
how to manage an NMC2 instance (see section 3.2)
3.1 Accessing the TMN-OSs window

You can access the TMN-OSs window either
from the front panel, click the icon.

from a free area of the workspace, click the mouse right button and select
TMN-OSs item from the menu displayed.
After this, the TMN-OSs window opens (refer to figure 5)
3BL 24534 AHAA PCAGA Ed.03 25 / 197

Figure 5: TMN-OSs Management window
The window is divided horizontally into two areas: the OSs area and the message
area. By default only the OSs area is shown.
OSs area The OSs area shows the NMC2 instances. The instance can have the following
colors:
green: all permanent processes of this instance are running
red: instance is running partially (at least 1 process is down)
blue: instance is stopped (all processes are stopped)
yellow: instance is in an indeterminate state
Message area By default the Message area is not shown. To view the message area, go to menu
Vi ew —> Messag e area —> S how
The message area shows the results of performed actions. The messages is
stamped by the date and time (year/month/day hour:minutes:seconds) (e.g.
launchSMFwithNAV) in a command shell. The scripts are gathered into the
<NMS_INSTANCE_DIR>/script directory.
For more information on the TMN OSs window, refer to the Alcatel-Lucent 1300
CMC E10 Getting Started operator guide, NM2GSGOP.
3.2 Managing an NMC2 instance

You can manage the selected NMC2 instance from the menu OS. You can start
the permanent processes, stop them, configure them and show information about
the SW packages composing the instance.
26 / 197 3BL 24534 AHAA PCAGA Ed.03

3.2.1 Starting permanent processes

To start all permanent processes, go to menu
OS —> S tart sy stem
3.2.2 Stopping permanent processes

To stop all permanent processes, go to menu
OS —> S to p sy stem
3.2.3 Launching the system configuration tool

To launch the system configuration application either
go to menu OS —> S y stemconf i g or
from the TMN OSs Management window, click the icon
This launches the system configuration tool.
3.2.4 Viewing information about an NMC2 instance

To view information about the packages composing the selected NMC2
instance
1. Go to menu
OS —> S y stem i nf or mati o n
2. The following window opens (see figure 6). All components of the selected
NMC2 instance are displayed indicating their name and release number.
Patches are also identified.
3BL 24534 AHAA PCAGA Ed.03 27 / 197

Figure 6: System information window
3.2.5 Defining the maximum number of operators logged

With this function you can set the maximum number of operators who can be
logged in at the same time in the current server.
This modification will be available only for the current server, so it should be done
on all servers (HMS and ENMS Active and Stand BYE).
To define the maximum number of users that can be logged simulta-
neously
1. Go to menu:
Glo bal acti ons —> Max op er ator log g ed Ad mi n
The following window opens (see figure 7):
28 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 7: Maximum operators management window
2. In the New value field, enter the new value for the maximum number of
users that can be logged simultaneously. To enter the default value, you can
also click the default button.
3. Click Apply to validate you selection.
4. Click Close to exit.
3.3 Setting a personal printer

You can set a personal printer among locally configured printers.
To set the personal printer:
1. In the TMN OSs Management window, go to menu Global acti ons —>
S et p ersonal p r i nter
The following window opens (see figure 8):
3BL 24534 AHAA PCAGA Ed.03 29 / 197

Figure 8: Set personal printer window
2. Fill out the Pr i nt command field, and click Ap p l y .

3. A window saying “The new printer will be available in the next session”
appears. To close the Set Personal Printer window, click OK .
3.4 Synchronizing systems

With this function you can synchronize the state of the system shown in the window
with the real state of the system.
To synchronize systems, go to menu:
Gl obal Acti ons —> S y nchr oni z e S y stems
3.5 How to change the system date and time

Log as root then launch this command:
sys,root # date MMDDHHmmAA
where :
MM : month
30 / 197 3BL 24534 AHAA PCAGA Ed.03

DD : day
HH : hour
mm : minutes
AA : year
If you have the following question, type yes :
date: do you really want to run time backwards ? [yes / no]
Example :
…,sys,root # date 0601010008
date : do you really want to run time backwards?[yes/no] yes
Jobs on crontab or scheduler planified to be executed at the hour of change will

not be executed.
3BL 24534 AHAA PCAGA Ed.03 31 / 197

32 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
4 Managing users
how to access the operator management tool (see section 4.1)
how to create a user (see section 4.3)
how to update a user (see section 4.5)
how to delete a user (see section 4.6)
how to change the password of a user (see section 4.7)
These tasks can be accessed only by an administrator (whose operator profile is

admin), except the C hang e Passw ord option which is available for all the
users.
System users are characterized by their login and password. They are known and
managed by the underlaying operating system.
Note: System users must be defined before being used in the Security Management.
User management does not cover the users of Trouble Ticketing, PEX and PC SW.
4.1 Accessing the operator administration application

With the operator administration application the administrator can manage the
operators of the selected NMC2 instance.
In case of distributed configuration, see before paragraph 1.6
To access the operator administration application:

1. From the TMN OSs Management window, go to menu
Acti o ns —> S MF —> Op erato rs Ad mi ni strati on
3BL 24534 AHAA PCAGA Ed.03 33 / 197

4 Managing users
2. The following window opens (see figure 9) opens:
Figure 9: Operators Administration window
The Workstations area shows all the available servers.

The Users Management area shows the OS user tree for the selected server(s). At
least one server must be selected in the Workstations area so that this tree appears.
When clicking on the + sign located on the left of a user icon, the profile of this
user is displayed at the lower hierarchical level. The profiles cannot be selected
since no action is available on them.
User management The menu bar of the User Management window contains two user management-
pull-down menus specific menus:
Work stati on: to select all the servers
User : to manage the users. By using this menu, the administrator can:
create a user
update a user
delete a user
You can also change the appearance of the Workstation area (see section 5.2).
User management icons The meaning of the icons specific to the user management is given, as follows,
(from left to right in the icon bar):
Create User,
Update User,
Delete User,
34 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
In order to ensure the user data consistency; when this application is already
opened and we try to launch it again, the following error message is displayed :
Figure 10: Warning of double launch of Operators Admin window
4.2 Defining your own “User password policy”

Before creating new users, you have to modify some parameters that determine
the password policy on your system.
4.2.1 Password Aging Policy

To define the Password Aging Policy, proceed as follows :
login as root on the system
launch SAM tool, the main window of this tool is then displayed :
3BL 24534 AHAA PCAGA Ed.03 35 / 197

4 Managing users
Figure 11: Sistem Management window
double-click on the “Auditing and Security Attributes Configuration” tab
36 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
Figure 12: Sistem Management window
then double-click on the “System Security Policies”, then the “Auditing and Se-
curity Attributes Configuration Tool” window is displayed:
3BL 24534 AHAA PCAGA Ed.03 37 / 197

4 Managing users
Figure 13: Auditing and Security Attributes Configuration Tool window
where the « PASSWORD_MAXDAYS » , « PASSWORD_MINDAYS » and « PASS-

WORD_WARNDAYS » parameters can be modified.
recommended values are :
1. PASSWORD_MAXDAYS : -1 <default> (password aging is turned off)
PASSWORD_MAXDAYS=N A new password is valid for up to N days, after
which the password must be changed. N can be an integer from -1 to 441.
2. PASSWORD_MAXDAYS : 0 <default>
PASSWORD_MINDAYS=N A new password cannot be changed until at least
N days since it was last changed. N can be an integer from 0 to 441.
3. PASSWORD_MAXDAYS : 0 <default> (no warning)
PASSWORD_WARNDAYS=N Users are warned N days before their pass-
word expires. N can be an integer from 0 to 441.
exit SMH tool by selecting the “File —> Quit” in the SMH main window.
4.2.2 Password Format Policy

To define the Password Format Policy, proceed as follows :
login as root on the system
launch SMH tool, double-click on the “Auditing and Security Configuration”
tab, then the “Auditing and Security Attributes Configuration Tool” window is
displayed:
38 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
then the target parameters are shown in the displayed window:
3BL 24534 AHAA PCAGA Ed.03 39 / 197

4 Managing users
recommended values are :

1. PASSWORD_MIN_DIGIT_CHARS : 0 <default>
PASSWORD_MIN_DIGIT_CHARS=N Specifies that a minimum of N digit
characters are required in a password when changed.
2. PASSWORD_MIN_LOWER_CASE_CHARS : 0 <default>
PASSWORD_MIN_LOWER_CASE_CHARS=N Specifies that a minimum of N
lower-case characters are required in a password when changed.
3. PASSWORD_MIN_SPECIAL_CHARS : 0 <default> (no warning)
PASSWORD_MIN_SPECIAL_CHARS=N Specifies that a minimum of N spe-
cial characters are required in a password when changed.
4. PASSWORD_MIN_UPPER_CASE_CHARS : 0 <default> (no warning)
PASSWORD_MIN_UPPER_CASE_CHARS=N Specifies that a minimum of N
upper-case characters are required in a password when changed.
exit SMH tool by selecting the “File —> Quit” in the SMH main window.
4.3 Creating a user

The only users created by the NMC2 by default are as follows:
user name : axadmin, user profile: administrator
user name : rem2gope, user profile : operator
40 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
Each NMC2 administrator can create other user profiles (see NM2SECGOP) for
more details, and can create other user accounts.
To create a user, proceed as follows:
1. In the User Management window either:
go to menu User -> C r eate or
click the Create User icon
The following dialog box (see figure 16) opens:
Figure 16: Create User dialog box
2. Complete the Login Information area:

In the User Lo g i n field, enter a user login name.
In the Descri p ti on field, enter the profile description.
In the New Passw or d field, enter a password . For the rules to be
fullfiled by passwords, see the chapter 4.4
In the C onf i rm p assw or d field, enter the new password again.
3. Configure the Profiles Management area:

To add a profile, select it in the Unselected Pro f i les list then click
the right arrow-button to move it to the S elected Prof i les list.
To remove a profile, select it in the S el ected Pr of i l es list then click
the left arrow-button to move it to the Unsel ected Pr of i l es list.
To select all the profiles in a list, click the icon-button.
To deselect all the profiles in a list, click the icon-button.
3BL 24534 AHAA PCAGA Ed.03 41 / 197

4 Managing users
In the current release, the click on the Mor e on Pr of i l es... push button has
no action.
4. Configure the Login Localization area:

To enable the new user to log on a server, select the server in the Und e-
f i ned on Ws list then click the right arrow-button to move it to the
Present on Ws list.
To prevent the new user from logging on a server, select it in the Present
on Ws list then click the left arrow-button to move it to the Und ef i ned
on Ws list.
To select all the servers in a list, click the icon-button.
To deselect all the servers in a list, click the icon-button.
Any user must be present at least on the ENMS server. So do not remove the ENMS
server from the Present o n Ws list.
Tick the C onti nue i n the case of p r obl ems button if you
want the creation to continue whatever happens. If the creation of the
user fails on one server, it will be performed on all the others.
5. Click either Ap p l y to create the new user or C lose to close the window
without making any changes.
The user is also created in the SEC database.
4.4 Password definition

The password must be sufficiently complex to prevent it from being guessed by
other users, for security purposes. It must fulfil the following rules :
Trusted-UNIX is not Without any other indication, the rules are those of SMF. They are described in the
configured document SMF20UG ( User Management chapter ). In some cases, the SMF rules
may be bypassed by a specific rules (like for BDH for instance).
To check the installation of this Trusted-UNIX package, please refer to the chapter
16.2.4 .
Trusted-UNIX is configured The following rules below are added to the SMF rules :
The password must have a minimum length of 7 characters with at least 2 al-
phabetic characters, at least 1 numeric character and at least 1 special Char-
acter.
The special characters must be different than blank and #.
Each user is invited to change its password after 90 days.
42 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
Validity of a password is 180 days.

The minimum time between password change is 7 days
The new password must be different from the last 4 precedent passwords
The creation of new users, which passwords are not compliant with the SMF rules,
is rejected immediately.
The creation of new users, which passwords are not compliant with the Trusted-
UNIX rules, is not rejected immediately : During the creation, following messages
appear: "passwd of user not updated to some workstations ..." "default configured
password is invalid. It’s also rejected. Password could be updated by adminis-
trator". Finally, the user is created and appears on the operator list. Its login is
refused with the message "login incorrect. Please, try again". If you are in such sit-
uation, you must delete the user login and create it again with an other password
that respects the Trusted-UNIX rules or perform an update user (as described in
the following chapter).
4.5 Updating a user
Do not update the axadmin user.
To update a user, proceed as follows:

1. In the User Management window, either:
go to menu User -> Up d ate or
click the Update User icon
3BL 24534 AHAA PCAGA Ed.03 43 / 197

4 Managing users
Figure 17: Update a user dialog box
This window is the same as for the Create user window. The contents of all the
areas can be updated (refer to section 4.3), except the User Log i n field. The
only way to update it, is to delete the user account and to create a new one with
a new login name.
Updating a user profile does not modify the ’security profile’ information in the
front panel (refer to the Alcatel-Lucent 1300 CMC E10 Getting Started operator
guide - NM2GSGOP).
4.6 Deleting a user
Before deleting a user, you have to first delete all the resources (alarm aging, etc.)
for this user.
To delete a user, proceed as follows:

1. In the User Management window, select a user in the User Management area
then either:
go to menu User -> Delete or
click the Delete User icon
44 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
Figure 18: Delete current user dialog box
2. Click either Ok to confirm or C ancel to cancel the operation.

When you click Ok , the user account is removed from the selected server(s). If
the user does not exist on another server after this deletion, make sure it has been
removed from the SEC database.
Because the network supervision system needs at least one administrator, it is

impossible to delete the last administrator. In this case an error message will be
generated to indicate this.
4.7 Changing the password of a user

All users can access this function.
To change a user’s password, proceed as follows:
1. In the TMN OSs Management window, go to menu:
Glo bal acti ons —> Op er ator —> C hang e p assw or d
3BL 24534 AHAA PCAGA Ed.03 45 / 197

4 Managing users
Figure 19: Change Your Password dialog box
2. Enter the current password in the Old Passw ord field.

3. Enter the new password in the New Passw or d field.
4. Enter the new password again in the C onf i rm p assw or d field.
For the rules to be fullfiled by passwords, see the chapter 4.4.
4.8 Assigning a new password in case of loss

Case of a user different When a user (who can be either an administrator like axadmin or an operator)
from root lose his password, the only way to restore his password is to give him a new
password. The procedure is as follows :
log off the user from the system
log on the system as root
type the UNIX command p assw d <userl og i n>
enter a new password for <userlogin>
the user is now able to log in the system by using his new password. He can
also change his new password by using the Global Actions —> Operator —>
Change password menu item in the TMN-OS window.
Case of root When the root password is lost, the solution is specific to the operating System.
Please follow the procedure provided by the underlying platform for this situation.
46 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
4.9 Activating an account with expired password

4.9.1 Procedure for PARISC servers
There are two cases to activate an expired password:
If the account is root, the On the Web console press Ctrl + B
procedure to follow is: Press Enter for : Service Processor login
Press Enter for : Service Processor password
Restart the machine by entering the following command: GSP>rs
Answer withY to the confirmation message.
Return to console mode: GSP>co
Follow reboot messages in the console and hit return when it gives you this
message:“To discontinue, press any key within 10 seconds”
You will then get a prompt, issue the "bo" command, when it asks if you want
to interact with IPL enter”Y ”
After getting the prompt, issue the command “hp ux -i s ”; this will boot the
system into single user mode.
Enter the following commands:Y
# fsck -y
# mount -a
Execute the command:/ usr / lbi n/ mo d p rp w -l -k r oot
Execute the command:/ usr/ lbi n/ mod p rp w – v r oot (in order to re-
fresh other passwords).
Execute the command:i ni t 4 in order to start the server in multi-user mode.
If the account is different Login as root on the NMC2

from root, the account has Execute the command:...sy s, roo t # / usr/ l bi n/ mod p rp w -l -k
to be activated with the <account>
following procedure: Execute the command:....sy s, r oot # / usr / lbi n/ mod p rp w –v
<account>
Where<account>is the account that we want to activate

Ex: axadmin
4.9.2 Procedure for ITANIUM servers

There are two cases to activate an expired password:
If the account is root, the Connect to the MP interface via telnet or ssh, refer to the appendix C.2 in order
procedure to follow is: to know how to access to the MP interface.
Switch off the server via the command : pc —off
Switch on the server via the command : pc —on
Launch the console via the command : co
The EFI boot manager will be displayed:
3BL 24534 AHAA PCAGA Ed.03 47 / 197

4 Managing users
Figure 20: EFI main window
In the EFI window select the Primary device as boot device (this is the default
choice).
You will get the EFI auto boot window:
Press any key in order to stop the auto booting
Figure 21: EFI booting prompt
After getting the prompt HPUX>, issue the command “hp ux -i s ”; this will
boot the system into single user mode.
Enter the following commands:Y
48 / 197 3BL 24534 AHAA PCAGA Ed.03

4 Managing users
# fsck -y
# mount -a
Execute the command:/ usr / lbi n/ mo d p rp w -l -k r oot
Execute the command:/ usr/ lbi n/ mod p rp w – v r oot (in order to re-
fresh other passwords).
Execute the command:i ni t 4 in order to start the server in multi-user mode.
If the account is different Login as root on the NMC2

from root, the account has Execute the command:...sy s, roo t # / usr/ l bi n/ mod p rp w -l -k
to be activated with the <account>
following procedure: Execute the command:....sy s, r oot # / usr / lbi n/ mod p rp w –v
<account>
Where<account>is the account that we want to activate

Ex: axadmin
3BL 24534 AHAA PCAGA Ed.03 49 / 197

4 Managing users
50 / 197 3BL 24534 AHAA PCAGA Ed.03

5 Managing sessions
5 Managing sessions
how to access the section management tools (see section 5.1)
how to customize the workstations area (see section 5.2)
how to broadcast a message (see section 5.3)
how to view the good logins (see section 5.4)
how to view the bad logins (see section 5.5)
how to lock the workstation (see section 5.6)
how to unlock the workstation (see section 5.7)
how to force the user logout (see section 5.8)
5.1 Accessing the session management application

This application and its services are available on each server in all distributed ar-
chitectures. When launched on a server, this application manages sessions locally
on the selected servers in the Workstations area in the Session Management win-
dow.
See before paragraph 1.6
This function is allowed to all operators.

To manage sessions:
1. In the TMN OSs Management window, go to menu
Glo bal acti ons —> Op er ator —> S essi on manag ement
2. The following window (see figure 22) opens.
3BL 24534 AHAA PCAGA Ed.03 51 / 197

5 Managing sessions
Figure 22: Session Management window
The Workstations area shows all OS workstations and remote terminals that are
connected. OS servers are labeled with their name (e.g. ornmos56) while remote
terminals are labeled with the OS workstation name, “@” and their network ad-
dress (e.g. ornmos56@139.54.93.253:0).
The Sessions area shows all the sessions on all the servers, with the following
attributes:
Login: user login name
From: OS server name or network address from which the user is logged
Login Date: date and time of the login start
Terminal: terminal type (console for OS server or dtremote for remote termi-
nals)
Session management The menu bar of the Session Management window contains 3 session manage-
pull-down menus ment-specific menus:
Work stati on:
to broadcast a message (see section 5.3)
to view the good logins (see section 5.4)
to view the bad logins (see section 5.5)
to lock the workstation (see section 5.6)
to unlock the workstation (see section 5.7)
User s : to force the logout of users (see section 5.8)
52 / 197 3BL 24534 AHAA PCAGA Ed.03

5 Managing sessions
Operator sessions connected via Metaframe are not displayed.
Session management icons The meaning of the icons specific to the session management is as follows (from
left to right in the icon bar):
Workstation -> Show Good Logins
Workstation -> Show Bad Logins
5.2 Customizing the workstations area

You can change the appearance of the Workstations area by going to the menu
(see figure 23):
Vi ew -> Wor k stati ons
Figure 23: Workstations sub-menu
By using the Wor k stati ons submenu, you can select:

to display (S how radio-button) or not (Hi d e radio-button) the Workstations
area
the way the server symbols are displayed in the Workstations area (Di sp l ay
option):
the alignment, by ticking the Hor i z ontal , Verti cal or S quar e radio-
button
the appearance, by ticking the Bi g Icon, S mall Icon or Tex t radio-
button
5.3 Broadcasting a message

To broadcast a message to all OS workstations, proceed as follows:
1. In the Session Management window, go to menu:
Work stati on -> Broad cast Messag e
The following dialog box opens (see figure 24):
3BL 24534 AHAA PCAGA Ed.03 53 / 197

5 Managing sessions
Figure 24: Broadcast Message dialog box
2. Type the text of the message in the text entry area.

3. select the priority level of the message by ticking the Urgent, Warning or Info
radio button.
4. Click Ok to send the message and close the window.
The broadcast message appears as in the following example (see figure 25):
Figure 25: Example of a Broadcast Message window
The color of the broadcast message is as follow:

red: the message is urgent
orange: it is a warning message
green: the message is for information
5.4 Viewing good logins

To view information on the good logins, proceed as follows:
1. In the Session Management window, select one server then go to menu:
Work stati on -> S how Good Log i ns
54 / 197 3BL 24534 AHAA PCAGA Ed.03

5 Managing sessions
Figure 26: Good Logins dialog box
2. The Logins area shows all successful logins on the selected servers, with the
following attributes:
Workstation: server name
From: station from which the user is logged
Terminal: terminal name
Login Date: date and time of the login start
Logout Date: date and time of the logout
Status: true or false
3. Click C l ose to close the window.
5.5 Viewing bad logins

To view information on the bad logins, proceed as follows:
1. In the Session Management window select one server, then go to menu:
Work stati on -> S how Bad Log i ns
(see figure 26):it’s the same like the “Good Login” figure
2. The Logins area shows all the unsuccessful logins on the selected servers,
with the following attributes:
From: station from which the user is logged
Terminal: terminal name
Date: date and time of the unsuccessful login
3. Click C l ose to close the window.
3BL 24534 AHAA PCAGA Ed.03 55 / 197

5 Managing sessions
5.6 Locking the workstation

5.6.1 Manual lock
An operator cannot lock his/her own workstation. In this case an error message
will be generated.
To lock the workstation:

1. In the Session management window, first select at least one workstation.
2. Go to menu:
Work stati on —> Lock
3. The following confirmation dialog box opens (see figure 27)
Figure 27: Lock Screen dialog box
4. To lock the workstation, click OK . To cancel, click C ancel . The following

dialog box opens (see figure 28)
Figure 28: Lock options dialog box
5. To dismiss the dialog box, click OK . To cancel the operation, click C ancel .
56 / 197 3BL 24534 AHAA PCAGA Ed.03

5 Managing sessions
5.6.2 Automatic lock

After 24 hours of inactivity (per default value), session is automatically locked by
the system.Operator has to give its password to open again the session
5.7 Unlocking a workstation

To unlock the workstations:
1. In the Session management window, first select at least one workstation.
2. Go to menu:
Work stati on —> Unlock
3. The following confirmation dialog box opens (see figure 29)
Figure 29: Unlock Screen dialog box
4. To unlock the workstation, click OK . To cancel, click C ancel .
5.8 Forcing the user logout

An administrator can force the logout of any user from a particular workstation.
In that case, all the sessions of the user are terminated (all the Xsessions or rlogin
processes are killed). If the user has several sessions open on different presenta-
tion servers, only the sessions initiated from the selected presentation server are
closed.
Note: Some privileged users cannot be forced to logout. The list of privileged users (e.g.
axadmin, root) is defined in a configuration file at the integration time.
To force the logout of a user, proceed as follows:
1. In the Session Management window, select a server in the Workstations area.
2. In the Sessions area, select a user login.
3. Go to menu:
User s -> For ce Log o ut
3BL 24534 AHAA PCAGA Ed.03 57 / 197

5 Managing sessions
Figure 30: Force Logout dialog box
This dialog box lists all the processes launched by the selected user and
running on the selected presentation server.
58 / 197 3BL 24534 AHAA PCAGA Ed.03

6 Process Monitoring Control (PMC) tool

With the Process Monitoring Control tool (PMC) the administrator can start and
stop processes dynamically and check the running state of processes that belong
to an NMC2 instance. It is possible to manage several system instances on the
same physical machine. The lrf (Local Register Files) and the ax conf i g file are
updated on each station.
functional groups, see section 6.1
functional states, see section 6.2
security of PMC, see section 6.3
how to access the PMC tool, see section 6.4
the main PMC window, see section 6.5
the PMC command line tool, see section 6.6
how to start an item or a group, see section 6.7
how to stop an item or a group, see section 6.8
how to control the processes of an NMC2 instance, see section 6.9
how to execute commands on agents, see section 6.10
how to synchronize configuration and data files, see section 6.11
how view information on agents, see section 6.12
how to view the PMC log, see section 6.13
how to set thresholds for CPU charge and disk occupation, see section 6.14
6.1 Functional groups

NMC2 product processes, also called as agents, are divided into functional groups
as a single entity. The groups contain, for example, database processes, alarm
processes etc.
3BL 24534 AHAA PCAGA Ed.03 59 / 197

6.1.1 Dependencies between groups

The administrator can start and stop groups one by one. To avoid starting the
groups in a bad order, there is a dependence mechanism between groups. There-
fore all groups have an associated “level” that specifies from which other groups
it depends. Every time when the administrator starts a group, PMC searches for
groups with a lower level and starts them first.
Group dependence information is available in a separate window that the ad-
ministrator can launch.
6.1.2 Example of dependencies

This section shows an example on how the dependencies work for the Group X.
The following table clarifies the dependency levels:
Table 2: Levels of dependencies among groups
Level Group
5 Group Z
4 Group Y
3 Group X
2 System RM
1 Database
Thus, starting the Group X (level 3) requires that the groups System RM (level 2)
and Database (level 1) are running. If they are not running, PMC starts them au-
tomatically. Stopping the Group X requires that the Group Y (level 4) and Group Z
(level 5) must be stopped. If they are running, PMC stops them first automatically.
6.2 Functional states

The managed elements can have the following functional states (see table 3)
Table 3: Functional states
State Color Description
Run Green Element is running correctly.
Stop Blue Element is stopped.
Wrong Red Assigned to an element whose child (or chil-

dren) of an element is stopped it should be
running.
Unknown Yellow Assigned to an element for which no infor-

mation is available from the server.
Status change Clear blue An action for an element is in process.
60 / 197 3BL 24534 AHAA PCAGA Ed.03

6.3 Security
Only the users who have administrator rights can access the PMC tool.
6.4 Accessing the PMC tool

To access the PMC tool:
1. In the TMN OSs Management window, either:
go to menu OS -> Pr ocess Moni tori ng or
click the icon
2. The PMC main window opens (see figure 31).
6.5 PMC main window description

For instructions on how to access the PMC main window, see section 6.4.
The PMC main window (see figure 31) is divided into three main areas:
Menu and toolbar area
Work area
Selected Item info area
3BL 24534 AHAA PCAGA Ed.03 61 / 197

Figure 31: Process Monitoring Control main window
6.5.1 Menu and toolbar area

In the menu and toolbar area the different menus and icons are shown (see figure
32)
Figure 32: Menu and toolbar area of the PMC tool
The following table describes the PMC icons:
Table 4: PMC icons
Icon Description
Closes the PMC application after a confirmation.
Starts the selected item.
62 / 197 3BL 24534 AHAA PCAGA Ed.03

Icon Description
Stops the selected item.
Synchronizes information in the Status Area.
Shows an information window that contains static data about the selected item.
The same information is shown in the Info Area of the PMC window. When no
data is available for an item, the warning “IM not running. No info available for
host [name of the host]”
6.5.2 Work area

The work area shows the state of the NMC2 instance. All items are organized
in hierarchical view, represented by icons with different colors to show the actual
functional state. A "tree" object simplifies navigation through the system. The hi-
erarchical organization is composed of different items, as follow. For an example
of the work area window, refer to figure 33
Figure 33: Work area part of the PMC main window
Node health status The following figure 34 shows the node health status part of the status area.
Figure 34: Node health status
3BL 24534 AHAA PCAGA Ed.03 63 / 197

Machine State . Summarizes the NMC2 instance state. This is useful

when the tree object is collapsed (only node health status is visible). The Ma-
chine State can have the following colors:
Green: the machine is in the Run functional state
Blue: the machine is in the Stop functional state
Red: the machine is in the Wrong functional state
Yellow: the machine is in the Unknown functional state
Clear blue: the machine is in the Working functional state
Node CPU charge . Two thresholds, warning and critical, can be set.
The icon color is either:
green (charge is smaller than warning threshold),
yellow (charge is higher than the warning threshold) or
red (charge is higher than the critical threshold).
For more information on setting the thresholds, see section 6.14.
A yellow triangle replaces the Node CPU icon when no information is available
for the machine.
Node file system allocation (CPU disk occupation) . Two thresholds,

warning and critical, can be set. The icon color is either green (disk usage is
smaller than warning threshold), yellow (disk usage is higher than the warning
threshold), or red (disk usage is higher than the critical threshold).
A yellow triangle replaces the Node file system icon when no information is avail-
able for the machine.
Remote node address . This label shows the monitored ma-

chine IP address, supplied in the PMC configuration. If the local machine has
a configured Domain Name Server (DNS), or entry in the host file, the trans-
lated name may be shown.
Managed NMC2 instance The following figure shows the managed NMC2 instance.
Figure 35: Managed NMC2 instance
64 / 197 3BL 24534 AHAA PCAGA Ed.03

NMC2 instance state . When you select the NMC2 instance state icon,
the information area displays:
the node name
load averages
total number of processes and the number of sleeping/running/zombie
processes
memory occupation: real memory (kbytes), virtual memory (kbytes) and
free memory (kbytes)
File system occupation: the total memory (Mbyte), the available memory
(Mbyte), the usage (%) of each directories.
The color of the NMC2 instance state may be:

green (all groups are running as required by the set run level)
yellow (no data available)
red (one or more groups are in a wrong state)
clear blue (change state in progress)
blue (product stopped)
Control state . When the control is not running the eye has a red cross
on it. When this icon shows a yellow triangle with an exclamation mark inside,
the PMC Server-side is not running. Also machine state icon is affected by this
situation showing a red icon.
Label shows the

name supplied in PMC configuration
Group list The group list consists of one icon and a label for each defined group. The label
shows the name supplied in the PMC server side configuration. See figure 36 for
an example of a group list.
Figure 36: Example of a PMC group list
The group icon can be:

green (all agents are running as required by actually set run level)
3BL 24534 AHAA PCAGA Ed.03 65 / 197

yellow (no data available)

red (one or more agents are in wrong state)
clear blue (change state in progress)
blue (group is stopped
You can select groups one by one by clicking on a group. To select more than one
group, keep the CTRL key pressed and click on the groups you want to select. To
select the groups between the first item and last item selected, keep the SHIFT key
pressed and click on the first group you want to select, then on the last group. All
groups between these ones will be included in the selection.
Agent list The agent list consists of one icon and one label for each defined agent. Label
shows the name supplied in PMC server side configuration. For an example of an
agent list, see figure 37.
Figure 37: Example of a PMC agent list
The icon type and color may be:

green arrow upwards: the agent and its child agents run correctly
blue arrow downwards: the agent is stopped (not defined in current set run
level or stopped by user request)
a red circle with a white X: the agent is in wrong state.
Child list The agents can have subsidiary agents as child objects. The child objects act the
same way as the agents.
6.5.3 Selected item information area

Information on the selected item is available for the “NODE” item and “agent”
item. Selecting a child agent always shows information on its parent. Selecting a
node item shows information on CPU(s) load (like the UNIX command top) and
for file system occupation (like the UNIX command bdf). Note that all information
showed in this area is static. To refresh the information you need to reselect the
item.
Example See figure 38 for an example of a selected agent item. In this example the name of
the selected agent is "TopologyManager-IM" and it is identified by its highlighted
name. The information area shows all information defined in PMC server side
configuration, among others the Process ID (PID) and the memory allocation for
this agent (and to all its possible children).
66 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 38: Information on a PMC agent
6.6 PMC command line tool

You can execute actions for the PMC server by command line. The command to
be used is
pmc2im
with the following parameters that are described in the table.
Table 5: PMC command line parameters
Command Description
startup <agent_name> Starts the named item.
shutdown <agent_name> Stops the named item.
server Starts the PMC server.
startup_sys Starts the entire system, according to group dependencies.
3BL 24534 AHAA PCAGA Ed.03 67 / 197

Command Description
shutdown_sys Shuts the entire system down, according to group dependen-

cies.
startup_group <group_name> Starts the named group and all the groups required by its
dependencies.
shutdown_group <group_name> Stops the named group and all the groups required by its
dependencies.
start_ctrl_server Enables the PMC server to automatically restart a process
stop_ctrl_server Disables the PMC server to automatically restart a process
check Checks for system status. Returns 0 if system is running, 1 if

system is wrong, 2 for system stopped.
6.7 Starting an item or a group

The administrator can start a single selected item or a group of selected items. It
is possible to start:
an NMC2 instance
group(s)
agent(s)
It is not possible to start nodes or child items.

To start an item or group of items:
1. In the work area, select an item or a group of items.
2. To start the item(s), either
go to menu Acti o ns —> S tart —> S elected Item or
click the icon .
3. A confirmation window opens.

a) To start the item, click Y es . When the action is completed successfully,
the color of the selected item becomes green in the work area. To see
updated information on the started item, in the work area click the item
and check that its status has been changed to RUN.
b) To cancel the starting of the item, click No .
When the control state is ON, a warning message “Control is active” will be dis-
played. To start the item, click Y es . To cancel the starting of the item, click No .
68 / 197 3BL 24534 AHAA PCAGA Ed.03

6.8 Stopping an item or a group

The administrator can stop a single selected item or a group of selected items. It
is possible to stop:
an NMC2 instance
group(s)
agent(s)
It is not possible to stop nodes or child items.

To stop an item:
1. In the work area, select an item or items.
2. To stop the item, either
go to menu Acti ons —> S top —> S elected Item or
click the icon .

a) To start the item(s), click Y es . When the action is completed successfully,
the color of the selected item(s) becomes blue in the work area. To see
updated information on the started item(s), in the work area click the item
and check that its status has been changed to STOP.
b) To cancel the stopping of the item(s), click No .
When the control state is ON, a warning message “Control is active” will be dis-
played. To start the item, click Y es . To cancel the starting of the item, click No .
6.9 Controlling the processes of an NMC2 instance

It is possible to control the NMC2 instance. This means that the controlling mech-
anism continuously checks the status of all the processes and starts processes that
stopped unintentionally. If it cannot start a process, it tries two more times. If this
did not help, it does not try to start the process anymore. The administrator can,
however, start the process manually.
Automatic process control The automatic start of the process control is applied when the control function is
active and the PMC server is restarted, for example, after a machine reboot.
If the AutoStart Enable is set, the process control function will be enabled at start
time of the PMC server, for example, after a machine reboot.
If the AutoStart Disable is set, the process control function will be disabled at start
time of the PMC server, for example, after a machine reboot. In this case, the
administrator can start the process control manually.
6.9.1 Starting the process control

To start the process control of an NMC2 instance:
1. Go to menu Acti ons —> C o ntr ol —> Acti vate
3BL 24534 AHAA PCAGA Ed.03 69 / 197


a) To start the control, click Y es . When the action is completed successfully,
the control icon is displayed next to the NMC2 instance icon in

the work area. The information area shows that the state of the control
function is ON.
b) To cancel the starting of the process control, click No .
6.9.2 Stopping the process control

To stop the process control of an NMC2 instance:
1. Go to menu Acti ons —> C ontr ol —> Deacti vate
a) To stop the control, click Y es . When the action is completed successfully,
the control icon is removed from the work area. The information
area shows that the state of the control function is OFF.
b) To cancel the stopping of the process control, click No .
6.9.3 Starting the automatic process control

To start the automatic process control :
1. In the work area, select the NMC2 instance icon and check from the infor-
mation area that the Control state is ON but the AutoStart state is OFF. If the
Control State is OFF, start first the process control function.
2. Go to menu Acti ons —> C ontrol —> AutoS tar t Enabl e
6.9.4 Stopping the automatic process control

To stop the automatic process control:
1. In the work area, select the NMC2 instance icon and check from the infor-
mation area that the Control state and the AutoStart state is ON.
2. Go to menu Acti ons —> C ontrol —> AutoS tart Di sabl e
a) To stop the automatic process control, click Y es . The information area
shows that the state of the AutoStart control is OFF.
b) To cancel the stopping of the automatic process control, click No .
6.10 Executing commands on agents

Feature not available
6.11 Synchronizing configuration and data file information

The purpose of synchronizing all the configuration and data files is to update all
information displayed in the work area.
To synchronize all the configuration and data files:
70 / 197 3BL 24534 AHAA PCAGA Ed.03

1. Go to menu:
Acti o ns —> S y nchr oni z e
2. A confirmation window about the reload of the configuration appears.
a) To execute the command, click Y es .
b) To cancel the execution of the command, click No .
3. If you clicked Y es , the hierarchical views of the NMC2 instance are closed
and the work area only displays the node icons and a yellow NMC2 instance
icon which indicates an unknown functional state and that the PMC IM is not
running. The NMC2 instance will be opened again automatically.
6.12 Viewing information on agents

The administrator can view detailed information on an item.
6.12.1 Viewing basic information on an agent
The basic information on an agent is also available in the information area of the
PMC main window (where it is dynamically updated).
If you want to view basic information on a selected item in a separate window,

proceed as follows.
To view information on a selected item:
1. In the work area, select the item whose information you want to view by
clicking on it.
2. To view information on the selected item either:
go to menu:
Vi ew —> Inf o
click the icon .
3. A window showing information on the selected item appears. To close the

window, click C l ose .
The information in the window is not dynamically updated.
6.12.2 Viewing trace files of a selected agent

The administrator can view trace files of a selected agent. It is also possible to
view the trace file of a child object of an agent.
To view information trace of a selected agent
1. In the work area, select an agent or its child object.
2. Go to menu:
3BL 24534 AHAA PCAGA Ed.03 71 / 197

View —> Selected Agent Trace

3. A window with all possible selectable traces opens (see figure 39). In this
case the Agent “Emlim_OCB_1_3” was selected. Select the trace file that you
want to view and click OK .
Figure 39: Select agent trace file window
If no trace file is available for an agent, an error message “No trace available for
this item” appears.
4. A window containing the selected trace file opens (see figure 40).
Figure 40: Trace file window
72 / 197 3BL 24534 AHAA PCAGA Ed.03

This trace file view is dynamic and when opened, it displays the latest 100
lines. It can display up to 8000 bytes of data. When the file size exceeds the
maximum value, the older bytes are discarded.
5. To view all the lines of the trace file in a static view, click Total .
6. In this example an information message appears saying that only 2 MB of
the size of the file can be shown (see figure 41). To dismiss the window, click
OK .
Figure 41: Trace file too big window
You can now view all the lines by using the scroll bar of the window.
7. To view the dynamic partial view of the maximum number of bytes, click
S tart .
8. To stop the updating of the dynamic partial view, click S top .
9. To close the window, click C lose .
6.13 Viewing the PMC log

To view the PMC log file:
1. Go to menu
Vi ew —> PMC 2 Log
2. A PMC2 window opens (see figure 42).
Figure 42: PMC2 log file window
3BL 24534 AHAA PCAGA Ed.03 73 / 197

The PMC2 log file view is dynamic, and when opened, it displays the latest
100 lines. In dynamic view, it can display up to 8000 bytes of data. When
the file size exceeds the maximum value, the older bytes are discarded.
3. To view all the lines of the log file in a static view, click Total .
4. In this example an information message appears saying that only 2 MB of
the size of the file can be shown (see figure 43). To dismiss the window, click
OK .
Figure 43: Log file size too big window
You can now view all the lines by using the scroll bar of the window.
5. To view the dynamic partial view of the maximum number of bytes, click
S tart .
6. To stop the updating of the dynamic partial view, click S top . You can view
again the log file in a static view.
6.14 Setting thresholds for CPU charge and disk occupation

The administrator can set warning and critical thresholds for CPU and disk occu-
pation. When the thresholds are reached, he/she is warned by the color of the
disk symbol of the PMC tool main window.
When all partitions in the host are less than the first threshold set, the disk symbol
is green. When at least 1 partition exceeds the first threshold, the disk symbol
becomes yellow. When at least 1 partition exceeds the second threshold, the disk
symbol becomes red. For more information, see section 6.5.2.
To set the tresholds
1. Go to menu:
Configuration —> Set Threshold
2. A window containing the CPU and disk thresholds opens (see figure 44)
74 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 44: Set Threshold window
3. To set the threshold for either CPU or Disk, click on the corresponding panel.
4. To set the warning threshold, place the mouse pointer on the warning thresh-
old button and drag it to the desired value.
The warning threshold value must be smaller than the critical threshold value.
5. To set the critical threshold, place the mouse pointer on the critical threshold
button and drag it to the desired value.
6. To confirm the thresholds set, click Ap p l y .
3BL 24534 AHAA PCAGA Ed.03 75 / 197

76 / 197 3BL 24534 AHAA PCAGA Ed.03

7 Administration of redundant Network Management System
7 Administration of redundant Network Management

System
7.1 Startup/shutdown of a redundant Network Manage-

ment System
This chapter details the procedures to be followed to startup/shutdown a redun-
dant NMC2 System
7.1.1 Starting a whole Network Management System

The first machine where we start OS Resilience application willbe the stand bye
machine.
To start a redundant NMC2 System a well-defined chronological order must be
followed:
a) Starting OSRes application on Stand-by machine
start the TMN System (through PMC tool) and verify it goes in RUNNING
status
stop the TMN System (through PMC tool) and verify it goes in STOPPED
status
start the OS Resilience application: refer to 7.1.3
wait until all the IMs are in the Stand-by status
b) Starting OSRes application on Active machine

start the TMN System (through PMC tool) and verify it goes in RUNNING
status
start the OS Resilience application: refer to 7.1.3
wait until all IMs are in the Active status
c) Start on all the Presentations machine OSRes application : refer to 7.1.3
3BL 24534 AHAA PCAGA Ed.03 77 / 197

7.1.2 Shutting down a whole Network Management System

To shut down a whole redundant network management system it’s important to
follow a well-defined chronological order to avoid unwanted switchover or un-
wanted application restarting
More precisely the right order is:
a) For each Presentation NMS instance : stop the OS Resilience application, refer
to 7.1.4
b) For each Master Active NMS instance: stop the OS Resilience application, refer
to 7.1.4
c) For each Master Standby NMS instance: stop the OS Resilience application,
refer to section 7.1.4
d) For each running NMS instance stop it by the proper command
7.1.3 OS Resilience application start on a single NMS instance

This section deals with the start of the OS Resilience application related to a specific
NMS instance
Starting OS Resilience application on a Master NMS instance

a) Login as root and launch the following command:
...sys,root#rm —f /usr/Systems/NMC2_1/SEC/repository/secim-exports/OS-
RES_SecDB
b) Login to the CDE as OS Administrator user
c) Start the TMN-OSs GUI from the user tools subpanel
d) From TheTMN-OSs GUI:
Select the NMS instance icon
Select Actions -> OS Resilience -> Start
Select YES on the confirm message
e) Verify, on the log window, that the procedure terminates correctly
Starting OS Resilience application on a Presentation NMS instance

a) Login to the CDE as OS Administrator user
b) Start the TMN-OSs GUI from the user tools subpanel
c) From TMN-OSs GUI:
Select Actions -> OS Resilience -> Start
d) Verify, on the log window, that the procedure terminates correctly
7.1.4 OS Resilience application stop on a single NMS instance

This section deals with the stop of the OS Resilience application related to a specific
NMS instance.
78 / 197 3BL 24534 AHAA PCAGA Ed.03

Stopping OS Resilience application on a Master NMS instance

c) From TMN-OSs start the OSRES GUI for the NMS instance:
Select Actions -> OS Resilience -> Graphical User Interface
d) From OSRES GUI

Stop the Data Replication
Set the switchover mode in MANUAL
e) From TMN-OSs GUI:

Select Actions -> OS Resilience -> Stop
f) Verify, on the log window, that the procedure terminates correctly
Stopping OS Resilience application on a Presentation NMS instance

Select Actions -> OS Resilience -> Stop
d) Verify, on the log window, that the procedure terminates correctly

e) Press Dismiss button to terminate the site configuration procedure
7.1.5 OS Resilience application Data Replication

Data replication can be activated on Active NMS instance.:
Select Actions -> OS Resilience -> Graphical User Interface. Os
Resilience window opens. Select an icon Replication—off, then:
Select Actions -> Start Data Replicationand wait for the correct pro-
cedure termination
Select Yeson the confirm message
Icon Replication-Off become Start Replication in progressn
Verify, on the log window, that the procedure terminates correctly. Wait the
message Start Data Replication Completed Successfully
Press Dismiss button to terminate the site configuration procedure, Wait,
icon become Replication—on
Nota: if you decide to stop Data Replication, Select Replication on, action
Stop Data Replication
3BL 24534 AHAA PCAGA Ed.03 79 / 197

7.2 System configuration updating on a resilient NMS in-

stance
To update the System Configuration on a resilient Master NMS instance, perform
the following steps:
a) Set, if needed, the switchover mode in Manual
b) Put in Active status the NMS instance you are going to configure
c) Stop, if needed, the Data Replication
d) Perform the System Configuration procedure
e) Only if you have changed the OSRES NMC configuration:
On the local Master instance:
Stop OS Resilience application and then restart it to take in charge the
modifications
On all remote resilient Presentation instances related to the local Master

one:
Stop OS Resilience application
Re-configure the OSRES instance:
# /<NMS_PHYSICAL_INSTANCE_DIR>/OSRES/etc/OSResSys-
temConfig
Start OS Resilience application
f) Start the Data Replication

The new configuration files are replicated on Stand-by NMS instance and the
new System Configuration will be applied on it after the next Switch-Over
g) Perform a manual Switch-Over and wait for the correct procedure termination
h) Verify the new System Configuration has been correctly applied on the new
Active NMS instance
7.3 Switchover activation

Before switch over activation, if downloading software NE session active,
On NMC2 active, Create a temporary log :
Menu SWD -> Archives Management -> Temporary archive creation
Then the log archive will be replicated
Switchover can be activated on Active or Standby NMS instance. Switchover can

be performed as follow:
Select Actions -> OS Resilience -> Graphical User Interface. Os
Resilience window opens. Select an icon, then:
Select Actions -> Switchover and wait for the correct procedure termi-
nation
80 / 197 3BL 24534 AHAA PCAGA Ed.03

7.4 Backup and restore on a resilient Network Manage-

ment System
The Backup and Restore procedures have to be executed only on the
Active NMS instance.
They have not to be run during the Active - Standby transitions.
7.4.1 Backup procedure management

To perform the Backup of a generic kind of data, the following procedure must
be followed:
b) Perform the Backup procedure
c) Resume the switchover mode
The Data Replication replicates the Backup data files on Stand-by host, and it is
possible to restore them after a Switch Over.
There aren’t restrictions about the Data Replication status during a Backup action.
7.4.2 Restore procedure management

There are two possible cases to be managed in the restore action, as detailed in
the following.
a) The backup has been executed on the local host
To perform the Restore of a generic kind of data, the following procedure must
be followed:
1) Set, if needed, the switchover mode in Manual
2) Stop, if needed, the Data Replication
3) Perform the Restore procedure
4) Resume the switchover mode
5) Resume the Data Replication status
b) The backup has been executed on an external host

This case can arise from one of the following actions:
the backup has been executed on the old Active host and it has been repli-
cated on local one by Data Replication tool (the backup files are available
from the standard NMS instance backup area)
the backup has been executed on the old Active host and it has been stored
on a tape storage device (the backup files are available from a tape)
the backup has been executed on an external not resilient host (the backup
files are available from a tape)
To perform the Restore of a generic kind of data, the following procedure must
be followed:
b) Stop, if needed, the Data Replication
c) Perform the Restore procedure, and taking into account the following advises:
3BL 24534 AHAA PCAGA Ed.03 81 / 197

From Restore window click on theChange mapping button: the Sub-

System mapping window opens
From Sub-System mapping window select, as target Sub-System, the
SS<local_hostname> option, where <local_hostname> is the host
name of the local machine
d) Resume the switchover mode

e) Resume the Data Replication status
7.5 Replicated data

The table below shows the data replicated automatically by default.
Data type Data description Data content
Network EML data NE data
TVA database local maps
DNM database distributed maps
Operator SEC database security related data
users user accounts created via

SMF or BDH
Unsol filters $HOME/.filters/
operator’s calendar crontabs
CORBA scripts macros .mjs
Alarm configuration sublists, filters, triggers, ag-

ging
Alarms Current list
Historical list
External OS NMSI configuration Registry Table
External OS param BDH parameters
Q3ES data
SWM persistence data
archives
82 / 197 3BL 24534 AHAA PCAGA Ed.03

8 Managing the scheduler

With the scheduler management tool the Administrator can schedule periodic ac-
tions, for example, backup and cleanup commands on one or several servers.
All the commands to be scheduled are declared into a configuration file with all
their parameters. A command may be a script or an executable binary. A plan is
built from one or several commands. An obvious example of a plan is the backup
the administrator may want to schedule daily, weekly or other.
A scheduled actions is a validated plan. It may be periodic or unique.
You can visualize the list of tasks that can be scheduled. You can schedule a task
and see the scheduled planning for the next week.
There is no priority nor precedence management for the scheduled tasks.
They are launched independently at the hour that you have set.
Note: You may want to schedule your own scripts and/or macro-commands. In that
case, you can use crontab files under UNIX (see section 8.7) or the NECTAR OS
Calendar (see section 8.8).
This section describes:
how to access the scheduler management tool, see section 8.1
how to create a plan, see section 8.2
how to edit a plan, see section 8.3
how to validate a plan , see section 8.4
how to stop a plan, see section 8.5
how to delete a plan, see section 8.6
how to use crontab files, see section 8.7
how to use the NECTAR OS calendar, see section 8.8
8.1 Accessing the scheduler management tool

To manage scheduled actions, in the TMN OSs Management window, go to menu:
Acti ons —> S MF —> S ched uler Manag ement
The following window (see figure 45) opens:
3BL 24534 AHAA PCAGA Ed.03 83 / 197

Figure 45: Scheduler window
The Plan list area displays all the servers. Double-click on a server icon to show
or hide the associated plans.
The Plan details area gives the parameters of the plan that is selected in the Plan
list area.
After logging in, you have full access (modify/delete) to the periodic or punctual
actions you had previously created, but not to other user’s plans.
Scheduler window The menu bar of the Scheduler window contains one Scheduler-specific menu
pull-down menu (Pl an) enabling you to:
create a new a plan
edit a plan
validate a plan
stop a plan
delete a plan
Scheduler management The meaning of the icons specific to the scheduler management is given, as fol-
icons lows, (from left to right in the icon bar):
create new scheduler plan icon , task also available from menu Plan
-> New plan
84 / 197 3BL 24534 AHAA PCAGA Ed.03

edit a scheduler plan icon , task also available from menu Plan ->
Edit plan
validate scheduler plan icon , task also available from menu Plan ->
Valid plan
stop scheduler plan icon , task also available from menu Plan -> Stop
plan
delete a scheduler plan icon , task also available from menu Plan ->
Delete plan
8.2 Creating a new scheduler plan

To create a new scheduler plan:
1. To create a new plan either:
In the Scheduler window, go to menu:
Plan -> New p l an
or click the New Plan icon
3BL 24534 AHAA PCAGA Ed.03 85 / 197

Figure 46: New plan dialog box
2. In the Plan name area, enter a name in the text entry field.
3. In the Plan parameters area:
Use the Ho st name option button to select the server on which the
plan is to be executed.
Note: To plan a backup, you must select the ENMS server.

To get the current date and time on the host server, click Vi ew OS
d ate . The following dialog box (see figure 47) opens:
Figure 47: Current date dialog box
Click OK to close the Current date dialog box.

Use the C ommand option button to select the command to be executed.
Enter the S tart d ate and the S tar t ti me of the script execution.
If the execution is to be done one time only, fill in the S top d ate and
S top ti me fields. Those fields are greyed if the Rep eat d el ay
check box is ticked.
86 / 197 3BL 24534 AHAA PCAGA Ed.03

If the execution is to be periodic, tick the Rep eat d elay check box then
fill in the Day ( s) , Hour(s) , Mi nute(s) and S econd e(s) fields.
To suspend the execution during the weekend, tick the Not on w eek -
end check box.
4. Click either Ap p l y to validate or C lo se to cancel the operation and close

the dialog box.
The state of the new plan is inactive (this is indicated by a blue cross). To activate
the execution of the plan, you must validate it first (see section8.4 )
8.3 Editing a scheduler plan

The purpose of this task is to edit an existing plan to change one or several pa-
rameters.
To edit a scheduler plan:
1. In the Scheduler window, select a plan in the Plan list and then either:
go to menu:
Plan -> Ed i t p lan
or click the Edit Plan icon
3BL 24534 AHAA PCAGA Ed.03 87 / 197

Figure 48: Edit plan dialog box
2. Modify any parameter except the Pl an name and the Host name
which are greyed.
3. Click either Ap p l y to validate or C lo se to cancel the operation and close
the dialog box.
Note: If the plan was active at the time of the modification, it is automatically stopped.
8.4 Validating a scheduler plan

This purpose of this task is to activate the execution of a plan.
When a plan is added in the Plan list of the Scheduler window, it is inactive. To
activate the plan, you have to validate it.
To validate a scheduler plan:
1. In the Scheduler window, select an inactive plan in the Plan list and then
either:
go to menu:
Plan -> Vali d ate p l an
or click the Validate Plan icon
2. In the Plan list, a green arrow appears on the left of the selected plan name,
as shown in figure 49).
88 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 49: Scheduler window showing an active plan
8.5 Stopping a scheduler plan

The purpose of this task is to deactivate the execution of a plan.
To stop a scheduler plan
1. In the Scheduler window, select an active plan in the Plan list and then either:
go to menu:
Plan -> S top p lan
or click the Stop Plan icon
2. In the Plan list, a blue cross appears on the left of the selected plan name,
as shown in figure 50).
3BL 24534 AHAA PCAGA Ed.03 89 / 197

Figure 50: Scheduler window showing only deactivated plans
Note: A command launched by the scheduler can only be stopped by using UNIX com-
mands (kill) from a terminal window.
8.6 Deleting a scheduler plan

To delete a scheduler plan
1. In the Scheduler window, select the plan to be deleted in the Plan list and
then either:
go to menu:
Plan -> Delete p l an
or click the Delete Plan icon
2. The following dialog box (see figure 51) opens:
Figure 51: Delete plan dialog box
Click either Y es to confirm or No to cancel the operation and close the

dialog box.
90 / 197 3BL 24534 AHAA PCAGA Ed.03

8.7 Using crontab files

Crontab files contain commands that are launched by the cron process at times
defined by the user. User must have administrator profile. More ever username
has to be present in the /usr/lib/cron/cron.allow file managed by root
There is one crontab file per user. The crontab files (named <username>) are in
the /var/spool/cron/crontabs directory.
Editing a crontab To edit a crontab file, proceed as follows:
1. Login as <username>
2. Enter: crontab -e
The <username> crontab file opens under the vi editor
3. Edit the crontab file then save it. The crontab file is ready to be managed by
cron.
Syntax The syntax of a command in a crontab file is as follows:

v w x y z path
where:
v is the minute(s) (0 to 59) at which the command is launched
w is the hour(s) (0 to 23) at which the command is launched
x is the day(s) (1 to 31) of the month at which the command is launched
y is the month(s) (1 to 12) at which the command is launched
z is the day(s) (0 for Sunday to 6 for Saturday) of the week at which the com-
mand is launched
path is the full path of the script to be used in the command
Each field of the command is separated by a space. Each field (v, w, x, y, z) may
contain several values separated by commas. * character means: all the values.
Javascript macro-command To directly execute a javascript macro-command file (essai.mjs for instance, lo-
files cated in the /users/name directory), use the following script:
<NMS_INSTANCE_DIR>/switchmml/script/mmlmacroinline -f
/users/name/essai.mjs
After execution, the result of the macro-command is sent by the cron process in
the user’s mailbox.
Examples of commands Here are some examples of commands:

* * * * * <NMS_INSTANCE_DIR>/switchmml/script/mmlmacroinline
-f /users/name/command.mjs: launches the command.mjs macro-com-
mand every minute.
0,5,10,15,20,25,30,35,40,45,50,55 * * * * <NMS_IN-
STANCE_DIR>/switchmml/script/mmlmacroinline -f
/users/name/command.mjs: launches the command.mjs macro-command
every five minutes.
3BL 24534 AHAA PCAGA Ed.03 91 / 197

* 1,2,3 * 5 * <NMS_INSTANCE_DIR>/switchmml/script/mmlmacroin-
line -f /users/name/command.mjs: launches the command.mjs
macro-command every minute from 1:00 to 3:59 every day of May.
* * * * 2 <NMS_INSTANCE_DIR>/switchmml/script/mmlmacroinline
mand every Tuesday.
* * 5 * * <NMS_INSTANCE_DIR>/switchmml/script/mmlmacroinline
th
mand every 5 day of the month.
Note: When you plan to launch commands during the night, do not trigger all of them
at midnight. In that way, you will prevent an overload.
Reading a crontab To list the contents of a crontab, enter:

crontab -l
More information about You can get more information about the crontab commands by entering:
crontab man crontab
8.8 Using the NECTAR OS calendar

The Nectar OS Calendar enables the execution of CORBA script macro-com-
mands (refer to the Nectar OS MML User Guide).
Javascript macro-command To execute a javascript macro-command file (essai.mjs for example), create the
files following CORBA script:
import posix
posix.system("<NMS_INSTANCE_DIR>/switchmml/script/mmlmacroinline
-f essai.mjs")
92 / 197 3BL 24534 AHAA PCAGA Ed.03

9 SMF Log management

This chapter describes how to manage SMF logs. It contains the following sections:
Overview of log management (see section 9.1)
Description of the log management user interface (see section9.2)
Managing log files (see section 9.3)
Managing the log record display (see section 9.4)
9.1 Overview of log management

The log files are written by administration scripts to archive meaningful operations
in the history of the NMC2 server. They must not be confused with the trace files
which are cyclic files written by application programs for debug purposes and
which are detailed in section 10.1.
There are several types of logs, but not all logs are treated by this SMF functionality.
Only logs concerning data associated with operators or system actions (NMC2-
based logs) can be viewed by the SMF log browser.
The two types of NMC2-based logs managed by SMF are:
the System logs that are:
SMF Logs: each SMF component logs its main actions to constitute the
system history. Only actions that affect the system are concerned (e.g. user
creation) These logs can also be sorted by date and filtered. Records have
no headers
the Applicative logs with the:

Command Logs which are generated by operators via PNMUSM and EM-
LUSM. They contain USM commands and reports (for example, PNM USM
generates a pnmusm.log). Their format enables to sort the records by date
(in ascending or descending order). It is also possible to view record head-
ers only. Filters can also be applied to various record fields.
Text Logs: the other logs using general text format. Filtering or sorting is
not possible with SMF tools.
3BL 24534 AHAA PCAGA Ed.03 93 / 197

Table 6: Origin of the available log types
Subsystem Log File Name * Log Type
SMF smf.log System log
PNM pnmusm.log Command log
SEC acdbm.log System log
SEC acsi.log System log
SEC lss.log System log
SEC secusm.log Command log
AS ascurusm.log Command log
PMC pmc2.log System log
EML emlusm.log Command log
MML mmlcorbaserver.log Common log
HP-UX ftp.log ** Common log
BDH bdhusm.log Command log
(*) only the name of the main log file is given, but it is also true for the overflow
logs that have the same name and a ".log.old" extension.
(**) for more information about the ftp.log format, refer to the HP-UX documen-
tation.
All the log files are located on the server where they have been generated.
Life cycle of logs Figure 52 presents the life cycle of a log file.
Figure 52: Life Cycle of a Log File
The IM and USM create current log files. Each log file has a predefined size
When a log file exceeds its predefined size, it is renamed and it becomes an
overflow log file. These files have the same name than the original log and
the extension ”.old” (e.g. lss.log and lss.log.old). Log types for text logs are
”Command Log”, ”System Log” and ”LogEngineTrivial”. The logging continues
with the current log file.
94 / 197 3BL 24534 AHAA PCAGA Ed.03

When the administrator is informed an overflow log file has been created,
he/she has to move this file in an area on the master server: the overflow log
file becomes an archived log file. Archived log files are compressed by using
.gzip
Current log and overflow log files are stored into <NMS_INSTANCE_DIR>/main-
tenance/log
Archived log files are stored on the master server into <NMS_IN-
STANCE_DIR>/maintenance/log
Archived logs An archived log is a log in a compressed format, stored in a specific area on the
backup server. It is possible to archive several logs into the same archive file. Only
logs that are archived may be saved using the SMF backup, or deleted.
Capacity of log browser The capacity of the log browser is limited. In the current release it cannot display
more than one thousand records. If the log is bigger, a warning message indicates
that the display has been truncated.
Distributed architectures This application and its services are available on each server in case of all dis-
tributed architectures. However, the list of the logs and the list of available work-
stations depend on the selected instance.
9.2 Log Management user interface

To manage logs, in the TMN OSs Management window, go to menu:
Acti ons -> S MF -> Log Manag ement
3BL 24534 AHAA PCAGA Ed.03 95 / 197

Figure 53: SMF Log Management window
Log management icons The meaning of the icons specific to log management operations is given, as
follows (from left to right in the icon bar):
View log file information icon , task also available from the menu Log
File -> Info
Archive log file icon , task also available from the menu Log File ->
Archive
Update log file icon , task also available from the menu Log File ->
Update
Window description The Log Files area shows all the existing logs, with the following attributes:
Type: log type (system, command, security or other logs)
Name: user friendly log name, different from the log file path-name
Archived: indicates whether the log is archived (archived) or not (original)
The Log Records (no filter applied) area shows the log records contained in the
log file(s) selected on the left.
When no log file is selected in the Log Files area, the Log Records (no filter applied)
area is empty as in figure 53.
96 / 197 3BL 24534 AHAA PCAGA Ed.03

When at least one log file is selected in the Log Files area, the SMF Log Manage-
ment window may become as in figure 54, as follows.
Figure 54: SMF Log Management window with log records
Note: Each time a change occurs in the file selection, the Log Records area is emptied
to ensure that its contents is coherent with the file selection.
By default the log records are sorted from the most recent one to the oldest one
and only the header of each log record is displayed. The header format depends
on the type of log:
Command Log:
<date><time>:<server name>:<usm><process identifier>:Operator
name= <user login name>:<Command><command status>
SMF Log:
<date><time> <hostname>:NMC2>/<functional domain>:<user login
name> <text>
Other Log:
The header has no specific format, i.e. in general text format (ASCII). It is
possible to edit any text file (ASCII format) with the SMF log browser if the file
is in the logging area. In particular, SMF can be used to edit and delete (after
archiving) copies of ELM logs.
The error level is not written in the log.

The following functional domains are used:
user
log
agent
backup restore
operation
3BL 24534 AHAA PCAGA Ed.03 97 / 197

tmn
configuration
start stop
maintenance
plugin
Log management The menu bar of the Log Management window contains 2 log management-spe-
pull-down menus cific menus:
Log Fi l e : to manage the log files (see section 9.3)
Log Recor d : to manage the log record display (see section 9.4)
Log management icons The meaning of the icons specific to the log management is given, as follows,
(from left to right in the icon bar):
Log File -> Info
Log File -> Archive
Log Record -> From Update
9.3 Managing log files

The log file management enables you to:
view information about a log file (see section 9.3.1)
archive a log file (see section 9.3.2)
delete a log file (see section 9.3.3)
9.3.1 Viewing log file information

To get information about a log file, proceed as follows:
1. In the Log Management window, select a log file in the Log Files area then
go to menu:
Log Fi le -> Inf o
Figure 55: LOG File Information dialog box
98 / 197 3BL 24534 AHAA PCAGA Ed.03

2. Click Ok to close the dialog box.
9.3.2 Archiving log files

You can archive current and overflow logs. This operation can be performed
automatically or manually (see figure 52).
To archive log files, proceed as follows:
1. In the Log Management window, select one or several log files in the Log Files
area then go to menu:
Log Fi le -> Ar chi ve
Figure 56: Move log to save Area dialog box
2. Enter a name in the entry field.

3. Click either Ok to validate the operation, or C ancel to cancel the operation
and close the dialog box.
In the Log Files list the name of the log file has been changed according to
the name that you gave in the step 2. Also the Archived status changes to
“Archived”.
Note: The log file contents is erased when the log is archived.
The Archive is a file containing compressed logs, the save area contains what is
saved or restored when using SMF backup or the log domain.
9.3.3 Deleting log files

In the SMF application, if is possible to delete archived logs only.
To delete archived log files:
1. In the Log Management window, select one or several archived log files in
the Log Files area then go to menu:
Log Fi l e -> Del et e
2. In the question dialog box that opens, click:
either on the Y es push button to confirm the deletion of the first log file
or on the No push button to cancel the deletion of the first log file
or on the All push button to delete all the remaining selected log files in
one time
or on the C ancel push button to cancel the deletion of all the remaining
selected log files
3BL 24534 AHAA PCAGA Ed.03 99 / 197

3. Repeat the same operation for each selected log files, except if you clicked
on the All or C ancel push button the previous time.
9.4 Managing log records

Log records are items inside a log file.The log record management enables you
to:
filter the log records (see section 9.4.1)
update the log record display (see section 9.4.2)
get detailed information about a log record (see section 9.4.3)
change the log record sorting order (see section 9.4.4)
change the display mode (see section 9.4.5)
9.4.1 Filtering log records

To filter the log records displayed in the Lo g Reco rd area
1. In the Log Management window, select a log file whose log records you want
to view.
2. Go to menu:
Log Record -> Fi l ter
Figure 57: LOG:LOG Records Filter dialog box
100 / 197 3BL 24534 AHAA PCAGA Ed.03

3. In the Date Filter area, indicate the period of time where records must be
retrieved.
4. If you want to refine your search, in the Attribute Filter area, define other
filtering criteria to be applied to log records:
Click the Attr i bute option-button to select an attribute among a list.
Click the Op erator option-button to select the kind of comparison
which is going to be performed between the previously selected attribute
and a value.
The Val ue part enables you to select a value among a list (if there is an
option-button) or to enter a value (if there is only an entry field).
The Filter Items subarea displays all the attribute filter criteria just being de-
fined by the user.
To manage those filter items, you can:
click Ad d to add an item just after defining an attribute criterion
click Remove to delete an item from the Filter Items list
click the AND radio-button if all the items of the Filter Items list must be
verified to retrieve a log record
click the OR radio-button if at least one of the items of the Filter Items list
must be verified to retrieve a log record
Note: AND and OR radio-buttons are exclusive.

5. Click either Ap p ly to validate the filter, or C lo se to close the dialog box
without change.
The result is that you can view the filtered log records in the Log Records area
of the Log Management window.
Note: When a filter is applied to log records, the Log Records ( no filter applied ) area
of the SMF Log Management window becomes the Log Records ( filter applied )
area, informing you about what it is precisely displayed in this area.
To disactivate the filter To disactivate the filter, open it and click the Reset button to remove the previous
filtering criteria. Then, click Apply.
9.4.2 Updating the log records area

You must update the log records area:
at the opening of the Log Management window
at each time the selection changes in the Log Files area
at each time the filter on log records is changed
To update the Log Recor d s area of the Log Manag ement window
1. Go to menu:
Log Recor d -> Up d ate
2. The Log Records area will be updated.
3BL 24534 AHAA PCAGA Ed.03 101 / 197

9.4.3 Viewing log record information

To view detailed information about a log record
1. In the Log Records area of the Log Management window, select a log record
then go to menu:
Log Recor d -> Inf o
Figure 58: LOG:LOG Record Information dialog box
2. Click Ok to close the window.
9.4.4 Sorting log records

This option toggles the display order of the log records in the Log Records area of
the Log Management window.
To sort the log records from the most recent one to the oldest one, use the following
menu path:
Lo g Record -> Most Recent Fi rst
To sort the log records from the oldest one to the most recent one (sorting by
default), use the following menu path:
Lo g Reco rd -> Old est Fi r st
9.4.5 Changing the display mode for all log records

This option toggles the display for all the log records in the Log Records area of
theLog Management window.
To display all the details of the log records, go to menu:
Lo g Record -> Full Detai ls
The Log Records area becomes as follows (see figure 59):
102 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 59: Log Records Area with full details displayed
To display only the header of the log records (display by default), go to menu:
Lo g Record -> Head er s Onl y
The Log Records area becomes as in figure 54 again.
Note: It is also possible to expand (or shrink) a log record by clicking on the + (or -)
sign on the left of the header.
3BL 24534 AHAA PCAGA Ed.03 103 / 197

104 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
10 Maintenance
From the OS Management window, you can access maintenance tasks by going
to menu:
Ad mi ni strati on Too l -> Mai ntenance
The Mai ntenance submenu contains the items as follows:
Trace Manag ement : to edit the trace levels, visualize and reset the trace
files (see section 10.1)
OS S nap shot Manag ement/ Fai lure Manag ement : to manage
the OS snapshots (see section 10.2)
C leanup Manag ement : to manage the files to be deleted (see section
10.3),
C orba scri p t manag ement : to access the MML CORBA Script appli-
cations (see section 10.4)
These tools can be accessed only by an administrator (of admin profile).
10.1 Trace management

Trace files are records of the process activity in the NMC2.
The level of these traces define the details which are currently archived. All the
trace files in the NMC2 are cyclic traces, except if it is explicitly mentioned.
The administrator is allowed to modify the level of traces to ease the diagnostic of
problems under special circumstances. On each station, each component has its
own trace configuration file, named trace.cfg, under a specific directory.
The default trace levels are 1, 2 and 5.
The following table gives the information traced according to the trace level spec-
ified:
3BL 24534 AHAA PCAGA Ed.03 105 / 197

10 Maintenance
Table 7: Information traced
Level Information
1 error statuses (raising, ignoring, clearing)
2 process events (init, shutdown, I/O)
3 process I/O dataflow
4 method calls and results
5 platform calls and results (system, TVA, SGBD,...)
6 debugging
7+ specific
When enabled, dataflow tracing (level 3), is issued, along with process events
(level 2) in dedicated trace files with extension .dataflow.
The trace management user interface in detailed in section 10.1.1.
10.1.1 Accessing the trace management tool

To access the trace management tool
1. In the TMN OSs Management window, go to menu:
Acti o ns -> S MF -> Trace Manag ement
2. The following window (see figure 60) opens:
106 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
Figure 60: Trace File Management window
Trace management window The Workstations area shows all the available servers.
description The Trace Files area shows all the existing traces on the selected server (when no
server is selected, this area is empty), with the following attributes:
Name: trace file name
Size (byte): trace file size (in bytes)
Trace management The menu bar of the Trace File Management window contains 2 trace manage-
pull-down menus ment-specific menus:
Processes : to edit the process trace levels (see section 10.1.2)
Trace-Fi l e : to manage the trace files (see section 10.1.3)
10.1.2 Editing trace levels

To consult and/or edit the trace levels of each process of a server:
1. In the Trace File Management window, go to menu:
Pro cesses -> Ed i t Tr ace Levels
3BL 24534 AHAA PCAGA Ed.03 107 / 197

10 Maintenance
Figure 61: Trace: Trace Levels Edition dialog box
In this window, each line shows the trace levels of one process. Each level
can be switched on (tick in the small square) or off (empty square). If a level
is switched on, the traces of this level will be written in the trace file. If a level
is switched off, no trace is written for this level.
2. Edit the trace level configuration:
To switch on (or off) a level, click on the corresponding square to tick (or
untick) it.
To switch on all the levels of a process, click Al l in the corresponding
line.
To switch off all the levels of a process, click C l ear in the corresponding
line.
Increasing the trace level also increases the load of processing of the server. Thus
you can change the trace level only if the operator need it.
3. Click either Ap p ly to validate the possible modifications, or C lose to close

the window without change.
10.1.3 Managing trace files

The trace file management enables you to:
view a trace file statically (see section 10.1.4)
view a trace file dynamically (see section 10.1.5)
108 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
reset the trace files (see section 10.1.6)
10.1.4 Viewing a trace file statically

This option enables you to view the static contents of the selected trace file, that
is, all the events up to the moment when the command was launched.
To view a trace file statically
1. To view the traces statically, select a trace file in the Trace Files area of the
Trace File Management window, then go to menu:
Trace-Fi l e -> S tati c Vi ew
Figure 62: Static View window
Static trace file window From this window, you can:

description search for a text occurrence
close the window
Searching for a text To search for a text occurrence

occurrence 1. In the Static View window, go to menu:
Fi l e -> S earch
3BL 24534 AHAA PCAGA Ed.03 109 / 197

10 Maintenance
Figure 63: Search_dialog dialog box
2. Type the text in the entry field.

3. Set the search parameters:
Tick the C ase sensi t i ve check box so that the research respects the
text case.
Tick the Word search only check box so that the search applies
only to whole words. Otherwise all the text occurrences will be displayed,
even into a word.
4. Click Ok to launch the search. The first occurrence appears in reverse video.
5. Click either Ok again to go to the next occurrence, or C ancel to stop the
search and close the dialog box.
Closing the window To close the Static View window, go to menu:

Fi l e -> C l ose
10.1.5 Viewing a trace file dynamically

This option enables you to view the dynamic contents of the selected trace file,
that is all the events from the moment when the command was launched.
To view the traces dynamically
1. In the Trace File Management window, select a trace file in the Trace Files
area, then go to menu:
Trace-Fi l e -> Dy nami c Vi ew
110 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
Figure 64: Dynamic View dialog box
This dialog box displays online all the traces that are currently executed.
2. Click C ancel to close the dialog box.
10.1.6 Clearing contents of a trace file

To clear trace files:
1. In the Trace File Management window, select at least one trace file in the
Trace Files area, then go to menu:
Trace-Fi l e -> Reset Traces
The following dialog box (see figure 65) appears as soon as the reset action
is finished:
Figure 65: Trace File Management dialog box
2. Click Ok to close the dialog box.
3BL 24534 AHAA PCAGA Ed.03 111 / 197

10 Maintenance
10.2 OS snapshot management/Failure Management

With the OS snapshot management you can capture data representative of the
state of the OS when a failure occurs. Only the snapshot of the whole OS (work-
station) is possible. On user request a list of files (log, trace, , etc.) defined by
configuration is collected for a server or for the whole OS.
The result of such a capture is called OS snapshot and is stored in a failure direc-
tory. Then it can be transferred on a tape connected to the snapshot server.
An OS snapshot may be used to diagnose a failure or to debug the OS.
The following data are associated with an OS snapshot:
date of the data capture
server on which the capture is done
list of the collected files and directories
type of the collection (automatic or manual)
number of OS snapshots on a server
The number of OS snapshots on a server is defined by configuration.

For more information on OS snapshot management, refer to SMF 2.0 User’s
Guide Operator Manual, SMF 2.0 UG.
10.2.1 Accessing OS snapshot management

To access the OS snapshot management (also called Failure management), in the
TMN OSs Management window, go to menu:
Acti ons -> S MF -> Fai lure Manag ement
Figure 66: OS Snapshot Management window
The Workstations area shows all the available servers.

The OS Snapshots area shows all the existing OS snapshots stored on the OS
Snapshot Server, with the following attributes:
Workstation: workstation (server) name
Name: OS snapshot name
112 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
Mode: ’Manual’ means that the OS snapshot has been made on user request.
’Automatic’ means that the failure of a process has triggered the OS snapshot
Failed Process: indicates the failed process (in manual mode, this column is
empty)
Access: ’Locked’ means that the OS snapshot is protected against a possibly
deletion from a user. ’Unlocked’ means that the OS snapshot is not protected
Size (KBs): OS snapshot size (in kilobytes)
OS snapshot management The menu bar of the OS Snapshot Management window contains 3 OS snapshot
pull-down menus management-specific menus:
Work stati on: to perform an OS snapshot (see section 10.2.2)
OS -S nap shot : to manage the OS snapshots (see section 10.2.3)
Op ti ons : to set the maximum number of OS snapshots (see section 10.2.4)
There are also, in the E d i t menu, two specific items:

S el ect Al l : to select all the servers
Unsel ect Al l : to deselect all the servers
OS snapshot management The icons in the toolbar correspond to the OS snapshot menus, as follows, (from
icons left to right in the icon bar):
Workstation -> Do a Snapshot
OS Snapshot -> Save on Tape
OS Snapshot -> Lock
OS Snapshot -> Unlock
OS Snapshot -> Delete
10.2.2 Taking an OS snapshot

To take an OS snapshot, in the OS Snapshot Management window, select a server
in the Workstations area, then go to menu:
Work stati on -> Do a S nap shot
10.2.3 Managing the OS snapshots

By using the OS -S nap shot menu, you can:
S ave an OS snapshot o n Tap e
Lock an OS snapshot
Unl ock an OS snapshot
3BL 24534 AHAA PCAGA Ed.03 113 / 197

10 Maintenance
Del ete an OS snapshot
10.2.4 Setting the maximum number of OS snapshots

To set the maximum number of OS snapshots that can be stored on the OS snap-
shot server, proceed as follows:
1. In the OS Snapshot Management window, go to menu:
Op ti ons -> S et Max i mum
Figure 67: Set Maximum Number of Snapshots on Workstation dialog box
2. In the New Max i mum field, enter the new maximum number of OS
snapshots the OS snapshot server will be able to store.
3. Click either Ok to validate the possible modifications, or C ancel to close
the dialog box without change.
10.3 Cleanup management

For the safety of the NMC2 it is necessary to limit the number and size of the files
created for management purposes. The size of some current operating files is
limited — such as logs and traces — as well as their number, since it is associated
to the number of processes. For some others, the file number and size is not
limited, for example, for the files.
The administrator can also create some files or directories whose size cannot be
controlled easily. The cleanup tool helps the user handle the data overcharge by
looking at these extra files and deleting them from time to time.
Before cleaning the Event Forward Discriminator (EFD) definition files, you must
stop the OS. For more information on EDF, refer to section 12.7.
114 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
10.3.1 Accessing the cleanup management tool

To access the OS cleanup management
1. In the OS Management window, go to menu:
Acti o ns -> S MF -> C leanup Manag ement
Figure 68: Cleanup window
Cleanup management The Domain list area is a table whose each line corresponds to a server. The files
window description to be cleaned are classified in domains:
Back up :
directories created for the backup and restore operations, located on
the master station only, under <NMS_INSTANCE_DIR>/Backu-
pArea, <NMS_INSTANCE_DIR>/maintenance/backup, <NMS_IN-
STANCE_DIR>/maintenance/restore
Log :
files concerning the PM-logfile, the .old log files, and all the .log files under
save, located in <NMS_INSTANCE_DIR>/maintenance/log on a server
Trace :
files concerning all the files .trace, .err and .dataflow in the NMC2 run time
tree of a server
Fai lure :
snapshot files written on failure. Concerns the directories located on
<NMS_INSTANCE_DIR>/maintenance/failure on a server
:
files dumped on process crashes. Concerns all the files on a station: of NMC2
processes within <NMS_INSTANCE_DIR>/maintenance/, and resulting
of panic UNIX error within /var/adm/crash
NE Doc :
NE documentation release
EFD :
3BL 24534 AHAA PCAGA Ed.03 115 / 197

10 Maintenance
concerns all the Event Forwarding Discriminator definition files. After removal,
the administrator has to restart the system. Only available in command line.
Cleanup management The menu bar of the Cleanup window contains one cleanup-specific menu
pull-down menus (C l eanup ) enabling you to:
get details about a domain to be cleaned (see section 10.3.2)
perform the cleanup (see section 10.3.3)
Cleanup management The meaning of the icons specific to the cleanup management is given, as follows,
icons (from left to right in the icon bar):
View details on files of a domain , task also available from the

menuCleanup -> Details
Clean files from a domain , task also available from the menuCleanup
-> Clean
10.3.2 Viewing details of files of a domain

To view details on files who belong to the domains
1. Select the domain whose details you want to view by ticking the box.
2. In the Domain list area of the Cleanup window, go to menu:
C leanup -> Detai ls
3. A Files to be cleaned window opens (see figure 69). It lists information
(name, size, used and available space, and associated directory) about the
files belonging to the domains.
116 / 197 3BL 24534 AHAA PCAGA Ed.03

10 Maintenance
Figure 69: Files to be cleaned
4. Close the dialog box by clicking C lose .
10.3.3 Cleaning up files from a domain

A cleanup is performed globally on all the files of a domain for a server.
To perform a cleanup
1. In the Cleanup window, for each server of the Domain list area, select the
domains to be cleaned:
To select a domain, tick the corresponding check box.
To select all the domains, click Al l .
To deselect all the domains, click C lear .
2. Go to menu:
C leanup -> C l ean
3BL 24534 AHAA PCAGA Ed.03 117 / 197

10 Maintenance
10.4 CORBA script management

The CORBA Script management application enables the user to communicate
directly with the NEs by using MML commands written in CORBA Script.
To access the CORBA Script management application, in the Map Management
(Topology Manager) application, go to menu:
Tool s -> MML
For more information about the CORBA Script management, refer to the NECTAR
OS MML User Guide, ALNOSMLGOP.
118 / 197 3BL 24534 AHAA PCAGA Ed.03

11 Managing printers and X25 links

From the TMN OSs Management window, you can access following functions from
the Actions pull-down:
Pri nters : to configure the printers (see section 11.1)
X 2 5 Li nk s : to configure the X25 links (see section 11.2)
11.1 Printer configuration

There are two types of printer:
A network printer is managed by the master server and can take into account
printing requests from any server of the OS.
A local printer can only manage printing requests from the server to which it
is connected. It can be declared as the default printer for its server.
The printer configuration enables an administrator to:

declare a network printer (see section 11.1.1)
declare a local printer (see section 11.1.2)
remove a printer (see section 11.1.3)
set a printer as default one (see section 11.1.4)
11.1.1 Declaring a network printer

Prerequisites
Login as root .
In /etc/hosts file, add the printer IP address and its name (For example :
155.132.209.221 hppsRS)
To declare a network printer, proceed as follows:

1. First have the following information available:
the printer name
the printer location name
3BL 24534 AHAA PCAGA Ed.03 119 / 197

the network printer IP address

the LAN hardware address
2. Like root on the system:
Figure 70: SMH console
launch SMH tool, the main window of this tool is then displayed, select the
“Configure Printers or Plotters” tab:
Figure 71: Sistem Managementwindow
3. Double-click on the Run button :
120 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 72: Sistem Management window: Configutre Printers Or Plotters
4. In the Printer and Plotters window, select a port then go to menu:

Acti o ns -> Ad d Remote Pri nter/ Pl otter s
11.1.2 Declaring a local printer

To declare a local printer, proceed as follows:
1. Execute steps to of section 11.1.1.
2. In the Printer and Plotters window, select a port then go to menu:
Acti o ns -> Ad d Local Pri nter/ Pl otter s -> Ad d Parall el
Pri nter/ Plotters...
Figure 73: Add Parallel Printer/Plotter dialog box
3. Click OK to confirm.
4. In the dialog box that opens, fill in the Pr i nter Name and Pr i nter
Mod el/ Interf ace fields then click OK .
3BL 24534 AHAA PCAGA Ed.03 121 / 197

5. In the Printer and Plotters window, if the status of the Print Spooler is STOPPED,
start it by using the menu path:
Acti o ns -> S tart P ri nt S p ool er
11.1.3 Removing a printer

The printer has already been installed. It is either a local or a network printer. To
remove it, proceed as follows:
2. In the Printer and Plotters window, select a printer in the list then go to menu:
Acti o ns -> Remove
3. In case the selected printer is the default one, a confirmation dialog box
opens in which you have to click Y es .
After a few seconds, the printer is removed and its corresponding line dis-
appears from the printer list.
11.1.4 Setting a printer as default

The printer has already been installed. It is either a local or a network printer. To
set it as the default printer, proceed as follows:
2. In the Printer and Plotters window, select the printer in the list then go to
menu:
Acti o ns -> S et as S y stem Def aul t Desti nati on
11.2 X25 link configuration

In vNMC2 there is no more X25 Board.
It is strictly forbidden to launch the X25 interface from SMH. If by mistake, the
administrator accesses the X25 Menu from SMH, all the XOT configuration is re-
moved, the server trying to communicate with the NE sites through the hardware
X25 board (which is no longer available vNMC2). The problem can be solved
only with a full restauration of the vNMC2 server.
The X25 board and the XOT front router is replace by the XOT HP software.
The pseudo-interface X25 is automatic configured when the first install of the
VM is performed. It is necessary to specify the equivalent of the front XOT
router in the former software XOT conf file => / etc / x25 / x121_to_ip_map
(pairs X25 @ destination - @IP XOT router knows the next router):
root@nmc2ve01:1/317:/$ cat /etc/x25/x121_to_ip_map
…
9406402 135.243.16.117 #TIM02 1
9406502 135.243.16.117 #TIM02 2
The rest of the routing is provided by the IP layer.
122 / 197 3BL 24534 AHAA PCAGA Ed.03

12 Q3ES administration
the Q3ES subsystem (see section 12.1)
the Q3ES user interface (see section 12.2)
how to declare, modify and delete an OSS (see section 12.3)
how to manage log FTAM (File Transfer Access and Management) functions
(see section 12.4)
how to view logs and delete an EFD (event forwarding discriminator) (see sec-
tion 12.5)
how to access information on Q3ES processed and addresses (see section
12.6)
how to send alarms and observation elements through the EFD user interface
(see section12.7)
12.1 Q3ES subsystem

The Q3ES (Q3ES Subsystem) is in charge of managing all the communications
with external OSS through the Q3ES protocol. It offers an indirect access to the
different NMC2 local MIBs. This protocol is a proprietary interface between the
NMC2 and other applications or OSS which offers an indirect access to the dif-
ferent NMC2 local MIBs. This feature is optional.
The concerned data flows are of several types:
Bulk Data
Unsolicited Messages
Alarms
Network Topology (Configuration Update and State Change)
3BL 24534 AHAA PCAGA Ed.03 123 / 197

Network Route and System Objects characteristics
Note: The Q3ES administration concerns only OCB and Alcatel-Lucent 8300—based
NEs.
Note: The use of Q3ES for the bulk data in files (Q3ES File Transfer Access and Man-
agement (FTAM) is exclusive with the BDH interface described in chapter 13.
Q3ES external interface Q3ES uses both services CMISE and FTAM as described, as follows:
The CMISE services offered by Q3ES are those of a Q3 agent in charge of the
Object Model (MOC). It contains:
the Network Topology (NEs and Routes) managed by the OSS
standardized support object classes, namely EFD (Event Forwarding Dis-
criminator), Log and Log Record. These objects can be managed from the
interface, with restrictions for some event types
The ones are handled by Q3IC and Q3ES partly overlap: Unsolicited and Bulk
Data Messages and Alarms; the others are added: "file available" events and
Network Topology.
The FTAM file transfer can be started:
by a client of Q3ES (i.e. the external OSS is the file transfer initiator) having
created EFDs for ’file available’ events of some expected families of bulk
data (see the basic interface defined later). In that case, Q3ES is ’FTAM
server’.
by Q3ES (i.e. Q3ES is the file transfer initiator) for clients not provided with
CMISE capabilities (see the reduced interface defined later). In that case,
Q3ES is ’FTAM client’.
Q3ES component The Q3ES component has to carry exchanges with external OSSs through two
different types of interfaces, according to the external OSS capabilities:
the Basic interface, through which both entities communicate via CMISE
messages, and via FTAM transfers for file transmission. In that case, the distant
OS is always the initiator of the FTAM session.
the Reduced interface, through which both entities can only transfer files via
FTAM, without any CMISE capabilities. In that case, as Q3ES has no possibility
to warn the distant OS of the file availability, it will decide by its own to establish
an FTAM session to transfer the available file. The decision can be carried out
by two means:
either automatically thanks to a static configuration file
or manually, upon local operator decision through Q3ES USM
The Q3ES functions are:

to communicate and manage subscriptions with external OSS
to handle translations between internal naming and LDN
to query all internal components
to manage transitory buffers
to broadcast incoming messages to all external subscribed OSS
124 / 197 3BL 24534 AHAA PCAGA Ed.03

The Q3ES behaves as a manager towards COLLIM (provides Bulk Data), ASIM
(provides current Alarms), PNMIM (provides EMLIM instances list), EMLIMs in-
stances (provides Network Topology, NE objects and Unsolicited).
The Q3ES component can be composed of several sub-components:
a broadcast handler
a Q3ES agent
a collection manager
an FTAM server and an FTAM client for the file transmission to external OS
12.1.1 Offered/used services

These services concerning the several types of data flow named in section 12.1
are offered to external OSS,
Q3ES can manage a "max number of external OS". The total of Logs, EFD and
FTAM logs must not exceed a "max number of subscriptions". Those numbers
are configuration parameters.
For one NE, one given data flow cannot be sent more than twice toward the
OSS. Q3ES refuses the EFD creation if this limit is exceeded
These services are used from: COLLIM - PNMIM - EMLIM - ASIM
12.1.2 External information model

The information model is accessible from the external OSS, is created for the Q3ES
Communication.
There are several types of objects concerned by this model (Network, System,
NetworkRoutes, Log, Discriminator, EFD, LogRecord, AlarmRecord) called MOC.
These MOCs have each their specific attributes and emit specific notifications
Mapping depend on the same types of objects as previously indicated
Q3ES-USM enables to create, modify and delete external OSS, through di-
alogs between Q3ES-USM and Q3ES, by using files. All those external OSS
characteristics are contained in a unique external OSS declaration file
12.1.3 Mechanisms to support offered services

The general mechanisms are provided to support offered services EFD and LOG.
They are based on standards but are not fully compliant with them, because of
the several added services. Consequently it is not possible to use standard EFDs
and LOGs.
The mechanisms depend on the Q3ES Basic Interface (refer to the previous "Q3ES
component") concerning Alarms, Bulk Data files, Unsolicited and Bulk Data mes-
sage (for EFD), Configuration management, Coll_NE creation/deletion notifica-
tions (for EFD).
12.1.4 Q3ES interfaces

Q3ES needs interfaces to perform its communications between:
Q3ES and COLL IM - PNM IM - EML IM - COMM SERVER - AS IM
Q3ES and Q3ES-USM which is always the initiator of the CMIS exchanges. Due
to COMET constraints, Q3ES-USM cannot communicate with Q3ES agents at
3BL 24534 AHAA PCAGA Ed.03 125 / 197

the same time; the communication with several Q3ES is sequential; to dialog
with one Q3ES, Q3ES-USM waits that the dialog with another is terminated;
before sending a request to Q3ES, Q3ES-USM has to unregistered then register
the agent
12.1.5 Multi instances of Q3ES

NMC2 must support up to 300 NE on a single multi CPU server. It is necessary
to provide load balancing with multiple Q3ES processes. Each Q3ES process is
independent from the other Q3ES processes, each has its own addresses which
are contained in each Q3ES configuration file.
Several instances of Q3ES can run on the same server. Q3ES instance manages a
set of NEs, corresponding to one or several NE group, which group list is contained
in each Q3ES configuration file.
One instance of Q3ES can manage up to 4 NE groups (i.e. up to 32NEs).
Note: The Q3ES processes receive all the alarms; Q3ES sends only the alarms to the
OSS matching the EFD filter.
12.2 Q3ES administration user interface

This section describes how to access the Q3ES administration user interfaces and
what are its main windows.
12.2.1 Accessing the Q3ES user interface

The user interface enables you to define configuration parameters, to export data
streams towards external applications in external systems.
To access the Q3ES administration, In the OS Management window, go to menu:
Acti ons -> Q3esusm
Figure 74: Q3ES Administration window
The seven push buttons in the middle of the window enable you to access the
main Q3ES applications. They are as follows:
OS S Ad mi ni strati on: to manage the OSSs (see section 12.3)
126 / 197 3BL 24534 AHAA PCAGA Ed.03

Log Manag ement : to visualize the configured subscriptions given through

CMISE messages to the log management (see section 12.5)
Log FTAM Manag ement : to define the configuration parameters used
by all the exported data streams (see section 12.4)
EFD Manag ement : to visualize the unsolicited messages (see section 12.7)
Q3ES Inf ormati ons : to get information about the Q3ES processes (see
section 12.6)
The E x i t push button enables you to quit the Q3ES administration user interface.
The Help push button opens the contextual help on line of the window.
12.2.2 Q3ES main windows

When clicking on one of the first five buttons presented in the beginning of section
12.2, a main window as in figure 75, as follows, opens:
Figure 75: Example of a Q3ES Management main window
The Q3ES main windows are composed of five areas, from top to bottom:
the window title
the menu bar
the list area
at the bottom left, the information field
at the bottom right, the number field
Window title The window title indicates the Q3ES application name (OSS Management in the
example above).
Menu bar The menu bar contains four pull-down menus. The pull-down menus introduced,
as follows, are common to all the Q3ES main windows:
Vi ew : contains five items:
OS S Ad mi ni strati on: to open the OSS Management main window
(see section 12.3)
Log FTAM Manag ement : to open the Log FTAM Management main
window (see section 12.4)
3BL 24534 AHAA PCAGA Ed.03 127 / 197

Log Manag ement : to open the Log Management main window (see
section 12.5)
Q3E S Inf or mati o ns : to open the Q3ES Informations main window
(see section 12.6)
E FD Manag ement : to open the EFD Management main window (see
section 12.7)
C lose : to close the current Q3ES main window and go back to the Q3ES
Administration window
E x i t : to quit the Q3ES administration user interface
Acti on : contains two items:

P ri nt : to print the contents of the window
Ref r esh : to update the contents of the window
Note: You can select the sub-menu Ref resh the E nti re Li st to update the
data displayed (number of records...); indeed Q3ES-USM is not automatically re-
freshed.
Help : to open the contextual help on line about the window
The fourth pull-down menu is specific to each Q3ES main window. It is presented
in the corresponding paragraphs hereafter.
List area This area contains the lists of the objects managed in the Q3ES application. The
column headers are presented in the corresponding paragraphs.
Information field This field indicates the last operation performed from the window.
Number field This field indicates the number of items in the list area.
12.3 OSS management in Q3ES

There are two ways of accessing the OSS management:
either from the Q3ES Administration window, by clicking on the OS S Ad -
mi ni str ati on push button
or from another Q3ES main window, by using the menu path:
Vi ew -> OS S Ad mi ni strati on
128 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 76: Q3ES: OSS Management window
The window areas are described in section 12.2.2. Only specific items are pre-
sented here.
List area The list area includes two columns:
OS S Name : OSS user label used by the four other applications
AE Ti tle : application address
OSS management The menu bar of the Q3ES: OSS Management window contains the common
pull-down menu menus mentioned in section 12.2.2 and one specific menu (OS S ) enabling you
to:
declare an OSS (see section 12.3.1)
modify an OSS (see section 12.3.2)
delete an OSS (see section 12.3.3)
12.3.1 Declaring an OSS in Q3ES

OSS is a distant application and must be declared.
To declare an OSS, proceed as follows:
1. In the Q3ES: OSS Management window, go to menu:
OS S -> OS S Decl ar ati on
3BL 24534 AHAA PCAGA Ed.03 129 / 197

Figure 77: Q3ES: OSS Parameters dialog box: General Panel
2. In the OSS area, enter the OSS user label (8 characters or less).
Note: Q3ES can manage a maximum number of external OSSs. A new OSS declara-
tion may be refused by Q3ES-USM if this number is reached. This number is a
configuration parameter.
3. In the Application Entity Title area, enter the external application parameters:
In the Application Title field, enter the application name that can be only
composed of numbers and points. It cannot start nor end with a point,
and two points must be separated by at least one digit: "123.2.4.24" is
a possible value but "12.3." is not, nor than "12..3".
In the Application Entity Qualifier(AEQ), enter a number: "1234" is a
possible value but "X12345" is not.
4. Click on the OSS Address 1 panel to enter the main address of the OSS.
The dialog box becomes as in figure 78.
130 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 78: Q3ES: OSS Parameters dialog box: OSS Address 1 Panel
This panel gives the user address elements for the different used classes:
In the Presentation Address area, fill in:
the Pr esentati on S elector field: 16 characters maximum
the S essi on S elector field: 16 characters maximum
Transp ort S el ector field: 32 characters maximum
Note: Selector can also be filled up in hexadecimal format. Example to introduce 22
hexadecimal value: give 22’h or 22’H in the selector’s field
In the Network Service Access Point area, select the address type by click-
ing:
either on the X 12 1 radio button: in that case, enter a number of 14
digits maximum.
or on the ISO 8348(RFC 1006) radio button: in that case the IP ad-
dress (= RFC 1006) must be preceded with the prefix . For example,
if the IP address is "123.56.2.245", enter the address as follows:
in the first field: 123
in the second field: 56
in the third field: 2
in the fourth field: 245
5. Click on the OSS Address 2 panel to enter the backup destination.
3BL 24534 AHAA PCAGA Ed.03 131 / 197

The panel that appears in exactly the same as the OSS Address 1 panel. It
is use for the external OSS secondary address.
6. Click either Ok to validate or C l ose to cancel the operation and close the
dialog box.
12.3.2 Modifying an OSS in Q3ES

To modify an OSS, proceed as follows:
1. In the Q3ES: OSS Management window, select the OSS to be modified then
go to menu:
OS S -> OS S Mod i f i cati on
The dialog box that opens is like in figure 77.
2. Modify the desired fields.
3. Click either Ok to validate the modifications or C lose to close the dialog
box without change.
Note: The AE Tittle modification is not performed by Q3ES-USM if there are remaining
resources (Log, EFD) associated to this OSS.
12.3.3 Deleting an OSS in Q3ES

To delete an OSS, proceed as follows:
1. In the Q3ES: OSS Management window, select the OSS to be deleted.
2. Then go to menu OS S -> OS S Del eti on
The deletion starts without any confirmation dialog box.
Note: The OSS deletion is not performed by Q3ES-USM if there are remaining resources
(Log, EFD) associated to this OSS. The verification of the deletion availability is
performed by the agent part.
12.4 Log FTAM management (reduced interface)

There are two ways to access the log FTAM management:
either from the Q3ES Administration window, by clicking on the Log FTAM
Manag ement push button
Vi ew -> Log FTAM Manag ement
132 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 79: Q3ES: Log FTAM Management window
Note: If there are problems to communicate with at least one Q3ES process, a message:
"Communication problem" is displayed in the information field.
sented here.
List area The list area includes four columns:
Log Id : log FTAM identifier
Fi lter ty p e : data flow type
NEs Li st : indicates the list of the NEs concerned by the log FTAM
OS S Name : name of the OSS for which the log FTAM is created (declared
on FTAM creation). It can be different from a log to another one.
Number Rec.: number of records
Tr. ty p e : type of transfer
Log FTAM management The menu bar of the Q3ES: Log FTAM Management window contains the com-
pull-down menu mon menus mentioned in section 12.2.2 and one specific menu (Log FTAM)
enabling the user to:
create a log FTAM (see section 12.4.1)
delete a log FTAM (see section 12.4.2)
browse a log FTAM (see section 12.4.3)
get information about a log FTAM (see section 12.4.6)
change the transfer type of a log FTAM (see section 12.4.7)
12.4.1 Creating a log FTAM

To create a log FTAM, proceed as follows:
1. In the Q3ES: Log FTAM Management window, go to menu:
Log FTAM -> Log FTAM creati on
3BL 24534 AHAA PCAGA Ed.03 133 / 197

Figure 80: Q3ES: Log FTAM Parameters dialog box: General Panel
2. In the OSS area, use the Name option button to select an OSS. The AE
Ti tl e field, displaying the corresponding external application name, is read-
only.
3. In the Filter area, use the Fi lter ty p e option button to select the bulk data
flow type
4. In the NEs area, the All NEs value appears by default in the S elected NE s
list (indeed an empty NE list is forbidden).
To add an NE in the list, select it in the Prop o sed NEs list, then click
the right arrow button.
To remove an NE from the list, select it in the S el ected NEs list, then
click the left arrow button.
5. Click on the Parameters panel.

134 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 81: Q3ES: Log FTAM Parameters dialog box: Parameters Panel
This panel gives the transfer management parameters.

6. In the Fi le p urg i ng d elay af ter transf er field, enter a value
between 1 and 65535.
7. In the Number of si mul taneous tr ansf er p er l i nk field, enter
a value between 1 and 10.
8. In the Number of r estart field, enter a value between 0 and 65535.
This number is significant only for FTAM transfer with recovery.
9. In the User i d enti ty field, enter 8 characters maximum.
10. In the User p assw ord field, see the chapter 4.4 for the password defi-
nition rules.
11. Use the Transf er mod e option button to select between with recovery
and without recovery.
12. Use the Transf er ty p e option button to select between automatic and
manual.
13. Click either Ok to validate or C lose to cancel the operation and close the
dialog box.
Once created, an FTAM log is not automatically deleted when the corresponding
NE is deleted. You have to delete such an FTAM log (see section 12.4.2).
3BL 24534 AHAA PCAGA Ed.03 135 / 197

12.4.2 Deleting a log FTAM

To delete a log FTAM, proceed as follows:
1. In the Q3ES: Log FTAM Management window, select the log FTAM to be
deleted then go to menu:
Log FTAM -> Log FTAM d eleti on
12.4.3 Browsing a log FTAM

To browse a log FTAM, proceed as follows:
In the Q3ES: Log FTAM Management window, select a log FTAM then go to
menu:
Lo g FTAM -> Log FTAM brow si ng

Figure 82: Q3ES: Log FTAM Browsing window
sented here.
List Area The list area includes four columns:
Recor d Id : record identifier
Event Ti me :
Fi le Name :
Transf er S tate : indicates whether the record has been transferred or is
to be transferred.
136 / 197 3BL 24534 AHAA PCAGA Ed.03

Log FTAM browsing The menu bar of the Q3ES: Log FTAM Browsing window contains the common
pull-down menu menus mentioned in section 12.2.2 and one specific menu (Reco rd ) enabling
the user to:
delete a record (see section 12.4.4)
send a record (see section 12.4.5)
12.4.4 Deleting a log FTAM record

To delete a log FTAM record, proceed as follows:
1. In the Q3ES: Log FTAM Browsing window, select the record to be deleted then
go to menu:
Recor d -> Record d eleti on
12.4.5 Sending a log FTAM record

To send a log FTAM record to the related external OS, proceed as follows:
1. In the Q3ES: Log FTAM Browsing window, select the record to be deleted then
go to menu:
Recor d -> Record send i ng
Note: If you want to do multiple transfer, you have to select only log FTAM records related
to the same q3esmed process.
12.4.6 Viewing Log FTAM information

To view information about a log FTAM, proceed as follows:
In the Q3ES: Log FTAM Management window, select a log FTAM then go to
menu:
Lo g FTAM -> Lo g FTAM i nf ormati on

Figure 83: Q3ES: Log FTAM Information window
3BL 24534 AHAA PCAGA Ed.03 137 / 197

sented here.
List area The list area includes six columns whose content is detailed in section 12.4.1.
Log FTAM information The menu bar of the Q3ES: Log FTAM Information window contains two of the
pull-down menu common menus mentioned in section 12.2.2.
12.4.7 Changing the transfer type of a log FTAM

To change the transfer type of a log FTAM record, proceed as follows:
1. In the Q3ES: Log FTAM Browsing window, select the record whose the type is
to be changed then go to menu:
Log FTAM -> Log FTAM tr ty p e chang i ng
The transfer type changes from manual to automatic or vice versa.
12.5 Log management

This application is used for the alarms. It enables you to view them from external
OSS created logs.
12.5.1 Accessing the log management user interface

There are two ways of accessing the log management:
either from the Q3ES Administration window, by clicking on the Log Man-
ag ement button
Vi ew -> Log Manag ement
In both cases, the following window (see figure 84) opens:
Figure 84: Q3ES: Log Management window
sented here:
List area The list area includes five columns:
138 / 197 3BL 24534 AHAA PCAGA Ed.03

Log Id : log identifier (it is unique). Since there are several Q3ES instances,
Q3ES-USM displays the Log Ids as follow:
<Q3ESid><.><Log identifier> (Example OS00_1.7).
The log are classified according to the Q3ES instance, first the log in Q3ES
number 1, then the log in Q3ES number 2...
Fi lter ty p e : indicates the type of bulk data involved in the log
NEs Li st : indicates the list of the NEs concerned by the log. The value may
be All NEs.
OS S Name : indicates the originator of the log
Number Rec.: number of non cleared alarms of all the NEs managed by
the Q3ES instance
Log management The menu bar of the Q3ES: Log Management window contains the common
pull-down menu menus mentioned in section 12.2.2 and one specific menu (Log ) enabling you
to delete a log (see section 12.5.2).
12.5.2 Deleting a log
Deleting a log is available only for debug purposes. It must only be used in critical
situations.
To delete a log, proceed as follows:

1. In the Q3ES: Log Management window, select the log to be deleted then go
to menu:
Log -> Log Del eti on
12.6 Q3ES information

This application enables you to access information on Q3ES processes and ad-
dresses, and their NE list.
Q3ES-USM retrieves the Q3ES list with their addresses in its configuration file.
Before displaying the Q3ES information window, Q3ES-USM gets the NE list by
asking all the Q3ES processes.
Note: If there are problems to retrieve the NE list from any Q3ES process, a "communi-
cation problems" message is displayed in the NE list field.
There are two ways of accessing the Q3ES information:
either from the Q3ES Administration window, by clicking on the Q3ES In-
f ormati ons push button
Vi ew -> Q3ES Inf or mati ons
3BL 24534 AHAA PCAGA Ed.03 139 / 197

Figure 85: Q3ES Informations window
The window areas are described in section 12.2.2.
12.7 EFD management

This application is a broadcast of unsolicited MML messages and enables you to
send alarms and observation elements.
12.7.1 Accessing the EFD user interface

There are two ways of accessing the EFD management:
either from the Q3ES Administration window, by clicking on the EFD Man-
ag ement push button
Vi ew -> E FD Manag ement
Figure 86: Q3ES: EFD Management window
Note: If there are problems to communicate with one Q3ES process, a pop-up displays
the following message: "War ni ng : The displayed information may be uncom-
pleted. At least one Q3ES process is unreachable". If all the Q3ES processes are
unreachable, the message is " War ni ng : All the Q3ES processes are unreach-
able".
140 / 197 3BL 24534 AHAA PCAGA Ed.03

sented here.
List area The list area includes eight columns:
EFD Id : EFD identifier (it is unique). Since there are several Q3ES instances,
Q3ES-USM displays the EFD Ids as follow:
<Q3ESid><.><EFD identifier> (example OS00_1.7). The EFDs are classi-
fied according to the Q3ES instance, first the EFD in Q3ES number 1, then the
EFD in Q3ES number 2...
Ad mi n. S tate
Fi lter Ty p e : indicates if the EFD concerns the Bulk Data, the Alarms, the
Unsolicited, the States Changes or the Configuration Updates
NEs Li st : indicates the list of the NEs concerned by the EFD. The value may
be All Nes. in the case of a State change or Configuration Update EFD, this
piece of information has no sense, so nothing is displayed in this column.
Fi lter characteri sti cs : indicates:
the alarm severity for an Alarms EFD
the application list for an Unsolicited EFD
the MOC list for a State Change or Configuration Update EFD
Those values may be All Nes. in the case of Bulk Data EFD, this piece of
information has no sense, so nothing is displayed in this column.
OS S Name : indicates the main destination of the EFD
OS S acti ve name : indicates the active destination of the EFD
OS S Back up name : indicates the backup destination of the EFD
EFD management The menu bar of the Q3ES: EFD Management window contains the common
pull-down menu menus mentioned in section 12.2.2 and one specific menu (E FD ) enabling you
to delete an EFD (see section 12.7.2).
12.7.2 Deleting an EFD
Deleting an EFD is available only for debug purposes. It must be used only in
critical situations.
To delete an EFD, proceed as follows:

1. In the Q3ES: EFD Management window, select the EFD to be deleted.
2. Then go to menu EFD -> EFD Del eti on.
3BL 24534 AHAA PCAGA Ed.03 141 / 197

142 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
13 BDH management
This section describes:
what is BDH management
the BDH user interface
how to declare, modify or delete an OSS in BDH
how to create, modify, delete a Bulk Data Collection
how to manage BDH files
13.1 Introduction to BDH management

The Bulk Data Handling (BDH) interface enables the FTP transfer of bulk data
between the NMC2 and customer (OSS) applications.
Note: The use of this interface is exclusive with the bulk data mode of Q3ES described
in chapter 12.
The bulk data sent by the different NEs in supervised state are stored in a disk
partition called repository. The bulk data repository is the file structure gathering
all the bulk data files. All the bulk data can be put in files.
The repository is organized according to the system type (HLR, OCB, OS, etc.),
the system name and the bulk data type (via the file naming). From the OSS, the
repository is read-only.
It is the responsibility of the OSS to perform the FTP operations to transfer the file
from the repository. There are no mechanisms in the NMC2 to ensure the transfer
integrity. The OSS may retransfer the file if it detects incomplete or corrupted data.
The NMC2 do not guarantee the data in the case of a server switchover, connec-
tion breakdown with the NE or when the NE supervision is stopped.
The list of NEs is not provided by this interface but by the OS-OS topology inter-
face. No indication on the NE releases is provided by the BDH interface.
The BDH management is only available for an administrator.
3BL 24534 AHAA PCAGA Ed.03 143 / 197

13 BDH management
13.2 BDH management user interface

This section describes how to access the BDH management user interface and its
main windows.
13.2.1 Accessing the BDH management user interface

To access the BDH management, in the OS Management window, go to menu:
Acti ons -> Bd hsusm
Figure 87: BDH Administration window
The three buttons in the middle of the window enable you to access the main BDH
management functions. They are as follows:
OS S Manag ement : to manage the OSSs (see section 13.3)
Bulk Manag ement : to manage the bulk data (see section 13.4)
Fi le Manag ement : to manage the BDH files in the repository (see section
13.5)
The E x i t push button enables you to quit the BDH management user interface.
The Help push button opens the contextual help on line of the window.
13.2.2 BDH Management main windows

When clicking on one of the first three push buttons presented in the beginning of
section 13.2, a main window as in figure 88, as follows, opens:
144 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
Figure 88: Example of a BDH: OSS Management main window
The BDH management main windows are composed of five areas, from top to
bottom:
the window title
the menu bar
the list area
at the bottom left, the information field
at the bottom right, the number field
Window title The window title indicates the BDH management domain (OSS Management in
the example above).
Menu bar The menu bar contains four pull-down menus. The pull-down menus introduced,
as follows, are common to all the BDH management main windows:
Vi ew : contains five items:
OS S Manag ement : to open the OSS Management main window (see
section 13.3)
B ul k Manag ement : to open the Bulk Management main window (see
section 13.4)
Fi le Manag ement : to open the File Management main window (see
section 13.5)
C lose : to close the current BDH management main window and go back
to the BDH Administration window
E x i t : to quit the BDH management user interface
Acti on : contains two items:

P ri nt : to print the contents of the window
Ref r esh : to update the contents of the window
Help : to open the contextual help on line about the window
3BL 24534 AHAA PCAGA Ed.03 145 / 197

13 BDH management
The fourth pull-down menu is specific to each BDH management main window.
It is presented in the corresponding paragraphs hereafter.
List area This area contains the lists of the objects managed in the BDH management do-
main. The column headers are presented in the corresponding paragraphs.
Information field This field indicates the last operation performed from the window.
Number field This field indicates the number of items in the list area.
13.3 OSS management in BDH

There are two ways of accessing the OSS management:
either from the BDH Administration window, by clicking on the OS S Man-
or from another BDH management main window, by using the menu path:
Vi ew -> OS S Manag ement
Figure 89: BDH: OSS Management window
sented here.
List area The list area includes three columns:
OS S Name : OSS user label
OS S Ad d r ess : DNS or IP address
User Name : user login
OSS management The menu bar of the BDH: OSS Management window contains the common menus
pull-down menu mentioned in section 13.2.2 and one specific menu (OS S ) enabling you to:
declare an OSS (see section 13.3.1)
146 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
modify an OSS (see section 13.3.2)

delete an OSS (see section 13.3.3)
13.3.1 Declaring an OSS in BDH

To declare an OSS, proceed as follows:
1. In the BDH: OSS Management window, go to menu:
OS S -> C reate
Figure 90: BDH: OSS Declaration dialog box (OSS Panel)
2. In the OSS name area, enter the OSS user label (up to 8 characters).
3. In the OSS addressing area, enter the DNS or IP address (4 fields for integer
values from 0 to 255).
4. Click on the USER panel.
3BL 24534 AHAA PCAGA Ed.03 147 / 197

13 BDH management
Figure 91: BDH: OSS Declaration dialog box (USER Panel)
5. In the User definition area, enter the user’s identification:

In the User i d enti ty field, enter the user login (from 3 to 8 characters).
In the User p assw ord field, enter the user password, see the chapter
4.4 for the password definition rules.
Note: User identity field must not be already used by an other application or External
OS
dialog box.
Declaring an OSS via BDH enables any NMC2 user previously created viaSMF to
connect to the NMC2 from the external OS by using FTP. However only the ’BDH’
user (created during the OSS declaration) home directory is directly in the BDH
repository.
13.3.2 Modifying an OSS in BDH

To modify an OSS, proceed as follows:
1. In the BDH: OSS Management window, select the OSS to be modified then
go to menu:
OS S -> Mod i f y
2. Modify the desired fields.
box without change.
148 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
13.3.3 Deleting an OSS in BDH

To delete an OSS, proceed as follows:
1. In the BDH: OSS Management window, select the OSS to be deleted.
2. Then go to menu:OS S -> Delete .
13.4 Bulk data collection management

This function consists of managing the bulk data collections.
There are two ways of accessing the bulk management:
either from the BDH Administration window, by clicking on the B ul k Man-
Vi ew -> Bul k Manag ement
Figure 92: BDH: Bulk Management window
3BL 24534 AHAA PCAGA Ed.03 149 / 197

13 BDH management
sented here.
List area The list area includes five columns:
Bulk Data Ty p e
S y stem l i st : list of the concerned systems (all by default). For a given bulk
data type, a list of possible systems is provided by means of an option button.
Li f eti me : lifetime (in day) of the bulk data file in the repository
C onsti tuti on mod e : there are four modes defining how a BDH file is
closed and moved to the repository:
per dispatch: only for performance data types of the A8300 NEs
size: when a configurable file size is reached
close timer: at the expiration of a configurable timer
close daily: everyday at a specified time
si z e, close ti mer or close ti me : there are four information types:

inper dispatch constitution mode, nothing is displayed
insize constitution mode, the size (in kbytes) is displayed
inclose timer constitution mode, the max time (in mn) is displayed
inclose daily constitution mode, the hours to close the file (HH:MM:SS) is
displayed
Bulk management The menu bar of the BDH: Bulk Management window contains the common menus
pull-down menu mentioned in section 13.2.2 and one specific menu (B ul k ) enabling you to:
create a new bulk data collection (see section 13.4.1)
modify the parameters of a bulk data collection (see section 13.4.2)
delete a bulk data collection (see section 13.4.3)
13.4.1 Creating a bulk data collection

To create a bulk data collection, proceed as follows:
1. In the BDH: Bulk Management window, go to menu:
Bulk -> C reate
150 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
Figure 93: BDH: Bulk Declaration dialog box (Bulk Panel)
2. In the Bulk type area, select the bulk data type by using the option button.
3. In the NEs area, select the systems:
To add a system, select it in the Prop osed sy stems list then click the
right arrow button.
To remove a system, select it in the S elected sy stems list then click
the left arrow button.
4. Click on the Files panel.

3BL 24534 AHAA PCAGA Ed.03 151 / 197

13 BDH management
Figure 94: BDH: Bulk Declaration dialog box (Files Panel)
5. In the File life time area, enter a number of days (7 days maximum).
6. In the File constitution mode area, click on one radio button to select the
mode, then:
if the Fi l e si z e mode has been chosen, enter the size in the si z e field
(30.72 kbytes maximum).
if the C l ose ti mer mode has been chosen, enter the expiration time
in the d elay field (1440 mn maximum, i.e. 1 day).
if the C lose ti me mode has been chosen, enter the hours in the HH,
MM and S S fields (HH accepted values are from 0 to 23, for MM and
SS accepted values are form 0 to 59).
dialog box.
152 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
Once created, a bulk data collection is not automatically deleted when the cor-
responding NE is deleted. You have to delete such a bulk data collection (see
section 13.4.3).
13.4.2 Modifying the parameters of a bulk data collection

To modify the parameters of a bulk data collection, proceed as follows:
1. In the BDH: Bulk Management window, select the collection to be modified
then go to menu:
Bulk -> Mod i f y
2. Modify the desired parameters (you cannot change the file constitution
mode).
3. It is possible to request an immediate closing of a file by pushing the button
C l ose now
box without changes.
13.4.3 Deleting a bulk data collection

To delete a bulk data collection, proceed as follows:
1. In the BDH: Bulk Management window, select the collection to be deleted.
2. Then go to menu:
Bulk -> Delete
13.5 BDH file management

This function consists of managing the BDH files present in the repository.
After defining a file filter (see section 13.5.1), you can open the BDH: File Man-
agement window (see section 13.5.2).
13.5.1 Accessing the BDH file management

There are two ways of accessing the file management:
either from the BDH Administration window, by clicking on the Fi le Man-
Vi ew -> Fi l e Manag ement
3BL 24534 AHAA PCAGA Ed.03 153 / 197

13 BDH management
In both cases, the following dialog box (see figure 95) opens:
Figure 95: BDH: File Filter dialog box
This dialog box enables you to define a filter to be applied to the BDH files dis-
played in the BDH: File Management window (see figure 96). You can select three
main criteria by means of check buttons and option buttons.
After selecting the filtering criteria, click either Ok to validate them or C lose to
close the dialog box without change.
The BDH: File Management window (see figure 96) opens.
13.5.2 BDH file management window

Figure 96: BDH: File Management window
sented here.
List area The list area includes four columns:
Fi le name : BDH file name
154 / 197 3BL 24534 AHAA PCAGA Ed.03

13 BDH management
S i z e (k by tes) : BDH file size

Date/ ti me : date and time of the BDH file creation
File management The menu bar of the BDH: File Management window contains the common menus
pull-down menu mentioned in section 13.2.2 and one specific menu (Fi le ) enabling you to:
delete a BDH file (see section 13.5.3)
export a BDH file (see section 13.5.4)
import a BDH file (see section 13.5.5)
In the case of an import action a list is built from the DAT content, the window is
similar to the window used to display list of files from the repository but the file
menu is replaced by the simple action "import" which triggers the copy of the file
from the DAT to the repository.
13.5.3 Deleting a BDH file

To delete a BDH file, proceed as follows:
1. In the BDH: File Management window, select the file to be deleted.
2. Then go to menu:
Fi l e -> Delete Fi l e .
13.5.4 Exporting a BDH file to DAT

To export a BDH file towards a DAT, proceed as follows:
1. In the BDH: File Management window, select the file to be exported then go
to menu:
Fi l e -> Ex p ort Fi l e
2. In the question dialog box that opens, click either Y es to confirm or No to
cancel the deletion.
The export starts without any confirmation dialog box.
Note: The exported BDH file is stored on the DAT just after the last record.
3BL 24534 AHAA PCAGA Ed.03 155 / 197

13 BDH management
13.5.5 Importing a BDH file from DAT

To import a BDH file from a DAT, proceed as follows:
1. In the BDH: File Management window, go to menu:
Fi l e -> Imp ort Fi le
Figure 97: BDH: Bulk Management window
2. In this window, use the Imp ort pull-down menu to trigger the copy of the
BDH files from the DAT to the repository.
156 / 197 3BL 24534 AHAA PCAGA Ed.03

14 Connecting external applications via CORBA SNM API
14 Connecting external applications via CORBA SNM

API
The CORBA SNM API optional feature enables an external OS to collect NMC2
alarms and topology and to send Man Machine Commands (MMC).
An external OS will be able to connect to the NMSI interface only if both NMC2
and the external OS has been properly configured.
The NMC2 administrator may need to perform this configuration. This section
describes how to proceed.
Configuration can be done at any time, regardless of the NMSI process which
may be already running. It can be changed as new clients must be connected /
removed.
14.1 NMC2 configuration

In order to connect to NMC2 via the CORBA SNM API interface, an external OS
must be declared in NMC2.
To access to NMC2 CORBA services there should be no firewall between NMC2
and external OS.
This involves two parameters:
the IP address of the external OS
the password (or key) of the external OS / client application (access control
for the connection of the external OS in NMC2)
NMC2 can support several clients (external OSs / application), and therefore this
couple of parameters is required for each externalOS/application.
Note that two client applications located on a same externalOS will have the same
IP address. They need to have different passwords. IP address and password are
declared in the configuration file registryTable.xml.
This file is located in the directory <NMS_INSTANCE_DIR>/NMSI/instance/de-
fault/nmsi/1/conf.
The file registryTable.xml is parsed each time an externalOS connection request
is processed, so it is possible to declare a new client even while the serverOs is
running.
3BL 24534 AHAA PCAGA Ed.03 157 / 197

Here is an example extracted from this file. In this example, 3 clients are declared
with values:
IPaddress1 and password1
The first two clients are hosted by the same external machine with IPaddress1.
They have different passwords.

<client WS="IPaddress1"
KEY="password1"></client>
Note: You have to replace IPaddressn with an IP address (whose format is

xxx.yyy.zzz.aaa).
You do not have to reboot or stop/restart the processes after this registration. The
processes will dynamically use the updated file.
Note: To enable the file transfer between NMC2 and the external applications, see the
chapter 15.1.
14.2 External OS configuration

All clients must get the server IORs. The servers must be started at least once to
have these files not empty.
The IOR is a string representing IP, HostName, Port of the server.
Alarm and topology server The IOR is in the file:
IOR <NMS_INSTANCE_DIR>/NMSI/working/default/1/serveros.ior.
The IOR is a string following the tag “IOR:”.
Example :
IOR:000000000000002849444c3a616c6d61702e616c636174
656c2e636f6d2f4f534f532f5365727665724f533a312e300000
000001000000000000002f000100000000000f3133392e353
42e3130342e3232350000ea6b00000000000f6d6f6e53657276
657572616d6f6900
MML server IOR The IOR is in the file nspd.out:

/alcatel/Kernel/SystemInstances/Global_Instance/mainte-
nance/trace.
The IOR is a string following the tag “NsfrontalIOR:”.
Example :
NspFrontalIOR:000000000000002949444C3A616C6D61702E
616C636174656C2E636F6D2F4E737046726F6E74616C2F4E7
158 / 197 3BL 24534 AHAA PCAGA Ed.03

3703A312E300000000000000001000000000000003000010
000000000076E6D6F73353700000FAA0000000000184465
6661756C744E616D6553657276657250726F63657373
Note: One easy way to retrieve the server IOR is to use FTP to retrieve the files indicated
above. This approach implies to have FTP account in the NMC2 machine.
14.3 “X733” vs “X733 extended” alarm format

Alarms can be forwarded to an upper OS in either “X.733” or “X.733 extended”
format.
Selection of the required value is done according to the parameter
USE_X733_OSOS defined in the file <NMS_INSTANCE_DIR>/AS/data/as-
curim/param.cfg
This parameter can take either True or False value.
NMC2 is delivered with the parameter set to False.
If it is changed, the ascurim process should be stopped and restarted.
14.4 External OS connection problem

In case during the connection of the external OS, a warning message "Not all GC
are available" is displayed, you must :
1. Stop ascurim and pnmim processes using Process Monitoring Window (PMC)
2. Stop nspd process : kill -9 of process nspd_Global_Instance_
3. Start ascurim and pnmim processes using Process Monitoring Window (PMC)
4. Verify nspd_Global_Instance_ ( using ps) is automatically restarted
5. Try to connect the external OS
3BL 24534 AHAA PCAGA Ed.03 159 / 197

160 / 197 3BL 24534 AHAA PCAGA Ed.03

15 OS security
15 OS security
When the OS security package is installed on the NMC2, any FTP, telnet or rlogin
command performed from any UNIX machine to an NMC2 machine fails. The
corresponding messages are as follows:
FTP case:
421 Service not available, remote server has closed connection
telnet case
Trying... telnet: Unable to connect to remote host: Connec-
tion ref
rlogin case (the IP address of the NMC2 machine is for example
abc.def.ghi.jkl):
Wait for login exit: ..
You can activate / deactivate a service (see section 15.1).

For the FTP service, NMC2 provides you with a standard FTP server or a proFTP
server (see section 15.2).
15.1 Activating/deactivating a service

Two files have to be modified, for allowing the service and defining the authorized
users. Proceed as follows:
Login as root user to the NMC2 machine.
Verify that inetd.conf file contains a line for each service to be activated.If no line,
or if the line begins with # , the service is not activated. Remove # or add a such
line if necessary. Example of telnet, rlogin, ftp lines:
telnet stream tcp nowait root /usr/lbin/telnetd telnetd
login stream tcp nowait root /usr/lbin/rlogind rlogind
ftp stream tcp nowait root /usr/lbin/ftpd ftpd
Then reconfigure inetd daemon by following command:

inetd –c
Then define allowed users. Verify that /var/adm/inetd.sec file contains the line
3BL 24534 AHAA PCAGA Ed.03 161 / 197

15 OS security
service allow IPADRESS
If this line is present in the file, add the IP address of the new authorized machines.
Otherwise, add the line with the IP address of the authorized machines. If you want
to forbid all machines, delete the service line. Then save the file
For a given service, only the last line beginning with the service name will
be taken into account. So, if you have to modify a line for a given service, check
that it is the last line of the file beginning with the service name
Example of the line of ftp service allowed for 2 IP address machines

ftp allow 155.132.54.180 155.132.209.25
15.2 Using the FTP flow control server

ProFTP is optional: to be chosen at installation.
ProFTP is a server that performs flow control . The client applications can use it in
order to prevent an overflow on their network.
To use the FTP flow control server, configure FTP , depending of the user context,
for example as follows:
1. In Windows, go to menu:
S tar t -> Pr og rams -> Ex ceed -> Host Access -> FTP
Figure 98: Open Connection dialog box
2. In the S erver Name field, enter the name of the server to which you want
to connect.
3. Fill in the User Name and Passw or d fields.
4. Click S etti ng s . The following dialog box (see figure 99) opens:
162 / 197 3BL 24534 AHAA PCAGA Ed.03

15 OS security
Figure 99: Connection Settings dialog box
5. In the S erver Port field, replace the displayed value (21, that corresponds
to the standard FTP server) with 2001 (for the proFTP server).
6. Click OK .
7. In the Open Connection dialog box, click Op en .
Launching ProFTP by using You can also activate the ProFTP service by launching the script:
a script <NMS_INSTANCE_DIR>/tools/user/script/UpdateOSS.pl <argument>
where <argument> is composed of the following parameters:
old IP address
new IP address
old user
new user
password
a digit (0 to add, 1 to modify, 2 to remove)
15.3 Using the Secure Shell services
This paragraph is available when SSH is installed
The standard services (ftp, telnet and rlogin) are not secured and they must be
forbidden to make efficient the use of the Secure Shell services. To de-activate
them refer to the chapter 15.1.
3BL 24534 AHAA PCAGA Ed.03 163 / 197

15 OS security
As the product provides this secured shell, Nokia is not responsible of problems
that may occur due to the use of the non-secured services.
The Secure Shell package is a set of commands that provide secured remote login,
file transfer, and remote command execution.
It ensures the data integrity and provides secure tunneling features and port for-
warding.
The following table lists the main Secure Shell commands and provides a brief
description of each.
Table 8: Secure Shell Commands
Command Description
ssh client program similar to rlogin, telnet and rsh
sftp secure ftp program
scp secure file copy program similar to rcp
slogin symbolic link to ssh
More information on this package can be found on the HP web site (the name of
the package contains the string : HP-UX S ecur e S hell ).
How to know if the Secure By executing the command sw li st | g r ep “HP-UX S ecure S hel l” as
Shell package is installed root.
15.4 NFS ACTIVATION / DEACTIVATION

15.4.1 NFS ACTIVATION
Log as root in the NMC2 server, and perform the followings commands:
Edit the file / etc/ rc.conf i g .d / nf sconf
Replace:
NFS _C LIENT=0
NFS _S E RVE R=0
By
NFS _C LIENT=1
NFS _S E RVE R=1
Save the file / etc/ r c.conf i g .d / nf sconf

Then, launch the following commands as root:
…, sy s, root # / sbi n/ i ni t.d / nf s.server stop
…, sy s, root # / sbi n/ i ni t.d / nf s.ser ver star t
15.4.2 NFS DEACTIVATION

Log as root in the NMC2 server, and perform the followings commands:
…, sy s, ro ot # / sbi n/ i ni t.d / nf s.server stop
164 / 197 3BL 24534 AHAA PCAGA Ed.03

15 OS security
Edit the file / etc/ rc.conf i g .d / nf sconf

Replace:
NFS _C LIENT=1
NFS _S E RVE R=1
By
NFS _C LIENT=0
NFS _S E RVE R=0
Save the file / etc/ r c.conf i g .d / nf sconf
15.5 Trusted-UNIX configuration

TRUSTED-UNIX is a security layer that strengthen the basic UNIX security rules.
Please refer to HP-UX documentation for more details on this package.
15.5.1 How to Check the Activation of Trusted-UNIX

Check the activation of the trusted-UX in the server:
sys,root # /SCINSTALL/security/bin/scsecurity
Security profile configured: "trusted-base"
If is not the case, the trustedUX (Base or Advanced) activation on server
can be done, only if the parameter “COMPANY_NAME” from /SCIN-
STALL/security/data/custom/security.parms is filled (e.g.: COM-
PANY_NAME="Nokia" )
15.5.2 How to Activate Trusted-UNIX

The Activation of the trusted-UX in the server can be done using
for Trusted Base:
sys,root # /SCINSTALL/security/bin/scsecurity trusted-base
or for Trusted Advanced:
sys,root # /SCINSTALL/security/bin/scsecurity trusted-advanced
Wait the end of the script:
Security Setup ended.
Security configuration ended with Bastille warning. Check the log file:
/SCINSTALL/security/log/scsecurity.log
The special characters, blank and #, are allowed in the password after
trusted-UX activation on server.
3BL 24534 AHAA PCAGA Ed.03 165 / 197

15 OS security
15.5.3 How to check that Trusted-UNIX is activated

To check that the Trusted-UNIX is activated on the host, please launch the following
command as root :
mca9fz98,sys,root # /SCINSTALL/security/bin/scsecurity
If the output is Security profile configured: "base1", then the Trusted-
UNIX is configured on your host.
If the output is There is no security profile configured, then the Trusted-
UNIX is NOT configured on your host.
166 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision
16 NMC2 supervision
16.1 Introduction to NMC2 supervision

The concept of NMC2 supervision provides a separation between the monitoring
of the system’s software and hardware resources:
Monitoring of the system-wide software resources (like process CPU load, con-
nections with connected hosts, health of some core processes, etc.) as well as
the NMC2 instance specific software resources (PMC processes, HA function-
ality, etc.) is performed via NMC2 monitors running in the NMC2 instance.
An alarm agent is installed which handles all local machine specific traps gen-
erated by the NMC2 monitors. This agent keeps its own Active Problem Table
(APT). A specific NE (Os1300nmc) must be declared and supervised in the
Topology Manager. Thus, the corresponding alarms will be visible in Alarm
Surveillance.
Monitoring of hardware resources (Cooling, Memory, Power, etc.) is carried
out by the HP-UX’s System Management Homepage (SMH) tool.
16.2 NMC2 software supervision

16.2.1 nmc_SOS monitors
The NMC2 software supervision is performed via NMC2 monitors (scripts) imple-
mented in the NMA nmc_SOS. This NMA is instantiated in the NMC2 instance.
The NMA nmc_SOS implements the following monitors:
connmoni tor.p l is checking that the connected hosts of this NMC2 server
are reachable. The events produced by this monitor have RRN=74.
cp umoni tor .p l verifies if the processes running on the server are over the
CPU threshold. The events produced by this monitor have RRN=77.
f i l emoni t or.p l checks that the size of certain log files does not exceed the
maximum allowed size. The events produced by this monitor have RRN=5.
f i l esy stem.p l checks that the occupation of the declared filesystems does
not exceed the given threshold. The events produced by this monitor have
RRN=88.
3BL 24534 AHAA PCAGA Ed.03 167 / 197

16 NMC2 supervision
i ni tt ab.p l verifies if the inittab processes are running or spawning too

rapidly. The events produced by this monitor have RRN=3.
max op erator .p l signals if the number of users logged on the host has
reached the maximum number of users allowed on station. The events pro-
duced by this monitor have RRN=79.
nf smoni tor .p l checks for NFS problems. The events produced by this mon-
itor have RRN=72.
osresmo ni tor.p l checks for HA replication, switch over or connectivity
problems. The events produced by this monitor have RRN=75.
p mcmoni tor .p l verifies if the PMC processes are running. The events pro-
duced by this monitor have RRN=30.
p rocessmoni t.p l checks whether some important processes are running(if
enabled). The events produced by this monitor have RRN=30.
smf moni tor .p l verifies if the SMF Scheduler is working properly. The events
produced by this monitor have RRN=76.
tunables.p l verifies if the usage of the HP-UX tunables exceeds the given
threshold. The events produced by this monitor have RRN=89.
An alarm agent is installed which store all local machine specific events (SNMP
traps) generated by the NMC2 monitors. This agent keeps its own Active Problem
Table (APT).
16.2.2 Os1300nmc NE
The Os1300nmc NE is an EMP based network element used for the NMC2 super-
vision. It provides the mapping rules needed by EMP to convert the SNMP traps
generated by the nmc_SOS monitors in Alarm Surveillance specific alarms.
Alarm synchronization for the Os1300nmc NE is performed when aligning-up the
NE, automatically (every 10 minutes) or manually from Alarm Surveillance. This is
realized using SNMP GET operations on the APT of the alarm agent implemented
in NMA nmc_SOS.
When declaring an Os1300nmc NE in Topology Manager, the “Operations Sys-
tem” Family and “1300 NMC2” Type must be used:
168 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision
Figure 100: NE Os1300nmc creation
When setting the NE address and port, port 7161 must be chosen:
Figure 101: NE Os1300nmc creation
For NMC2 software supervision of the own server (self-supervision), the declara-
tion and supervision of the corresponding Os1300nmc NE is the only necessary
step to perform.
The supervision of the own NMC2 server on distant NMC2 server(s) is possible but
require manual configuration in order for the corresponding traps to be forwarded
in real time. A trapsink <IP_address>directive must be added in the local
/ etc/ snmp / snmp d .conf file. The IP address to be used is the IP address
of the NMC2 server where the supervision is performed (NE Os1300nmc with
local IP address created). This mechanism must be applied for supervision of HA
stand-by servers and HMS servers.
3BL 24534 AHAA PCAGA Ed.03 169 / 197

16 NMC2 supervision
16.2.3 NMC2 internal alarms

The Os1300nmc NE maps the traps received from the NMC2 monitors to alarms
in order to be displayed in the Alarm Surveillance. The two-digit report reference
numbers (RRN) of these alarms are specific for each nmc_SOS monitor that can
generate them.
Each RRN can refer to one or more different events from the same family. The
subreason (nmcRRNSubReason attribute) of the alarm is used to discriminate
between alarms with the same RRN.
The following list of alarms is mapped for Os1300nmc NE:
RRN = 03 Supervision of i ni ttab processes
Subreason 03..24: The inittab script <file> of instance <instance_name> has
died.
Subreason 28..74: The inittab script <file> of the Global_Instance has died.
Subreason 78..99: The inittab script <file> of instance <instance_name>
spawns too rapidly.
Subreason 103..149: The inittab script <file> of the Global_Instance spawns too
rapidly.
RRN = 05 File exceeds maximum size

Subreason 01..04: File <logfile> exceeds maxsize <size>.
RRN = 30 PMC or core processes not running

Subreason 01..100: PMC process <name> of group <group> does not run.
Subreason 101..123: Core process <name> not running.
RRN = 72 NFS problem

Subreason 01: The NFS server is down or not reachable. Home directories cannot
be used.
Subreason 02: NFS badcalls statistics problem.
Subreason 03..999: NFS client <id> hangs.
RRN = 74 Kerberos connexion to host <hostname> is broken
RRN = 75 HA problem
Subreason 01: HA file replication problem.
Subreason 02: HA data replication problem.
Subreason 03: HA switchover problem.
Subreason 04: HA connectivity with the stand-by node problem.
RRN = 76 SMF Scheduler error

Subreason 01: The schedulerdb.dat file is corrupted.
170 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision
Subreason 02: SMF scheduler is blocked.

Subreason 03..99: Scheduled task ’<id>’ corrupted definition.
Subreason 03..99: Scheduled task ’<id>’ did not return successfully.
Subreason 03..99: Scheduled task ’<id>’ is expired.
RRN = 77 Process CPU usage over threshold

Subreason 01..32768: Process ’<PID>’ (’<name>’) exceeds CPU usage upper
threshold.
RRN = 79 Too many users are logged into the system and further logins are dis-
abled.
RRN = 88 Filesystem occupation problem

Subreason 01..100: Filesystem <filesystem> occupation is <occupation>%.
RRN = 89 Tunable over the threshold

Subreason 01..100: Tunable <tunable> is over the <treshold> usage threshold.
16.2.4 Alarms troubleshooting

Note: If traces are required for the troubleshooting of a problem, level 5 traces should
be activated. Contact Nokia Support Team if help is needed to activate or interpret
the traces.
Note: The paths containing the <NMS_INSTANCE_DIR> keyword present in this chap-
ter relate to the instance and server from where the alarm originates, not to the
instance and server where the respective Os1300nmc NE is supervised.
3BL 24534 AHAA PCAGA Ed.03 171 / 197

16 NMC2 supervision
Table 9: Alarms troubleshooting
RRN Problem/Error Diagnostic and possible correction

message
3 - Inittab process Check the script or process from /etc/inittab.

<name> of
Solve the problem of the crash, and restart init by calling:
instance <in-
stance_name> is # /sbin/init q
not running.
Contact the Nokia Support Team if the problem persists.
- Inittab process
<name> of the
Global Instance is
not running.
- Inittab process
<name> of
instance <in-
stance_name>
is spawning too
rapidly.
- Inittab process
<name> of the
Global Instance
is spawning too
rapidly.
5 - file /var/adm/ sys- To solve the problem of growing syslog file, restart the syslogd. This is done by
log/syslog.log ex- logging in as root and launching:
ceeds maximum size
# /sbin/init.d/syslogd stop
<maxsize>
# /sbin/init.d/syslogd start
After that the oversized syslog file is moved to OLDsyslog.log and a new sys-
log.log is created. Pay attention, that the old OLDsyslog.log is deleted.
Nevertheless, it should be analysed why the log file grew so large.
5 - file The /var/adm/wtmp file logs all logins, rlogins and telnet sessions.
/var/adm/wtmp
Use the following command to convert the content of the wtmp file in a readable
exceeds maximum
format:
size <maxsize>
# /usr/sbin/acct/fwtmp < /var/adm/wtmp >/tmp/wtmp_out
Open the /tmp/wtmp_out file with a text editor and verify if corrupted entries
(wrong structure of the log) are the cause of the growing log.
Clear the /var/adm/wtmp file using the command:
# cat /dev/null >/var/adm/wtmp
5 - file /var/adm/btmp This file contains the logs of bad login attempts.
exceeds maximum
Run as user root the following command to check the content of the btmp file:
size <maxsize>
# lastb -f /var/adm/btmp
Clear the /var/adm/btmp file using the following command, as user root:
# cat /dev/null >/var/adm/btmp
172 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision

message
5 - file /var/adm/su- This file contains the logs of "su" command attempts.
log exceeds max-
Log as user root and check the content of the /var/adm/sulog file.
imum size <max-
size> Rename the /var/adm/sulog file using the command:
# mv /var/adm/sulog /var/adm/sulog_old
The original file will be recreated by the next attempted "su" command.
30 - PMC process Check the <NMS_INSTANCE_DIR>/maintenance/log/pmc2.log file.

<name> of group
Verify the status history of the crashed process.
<group> does not
run. Try to restart the process using PMC.
Contact the Nokia Support Team if the process does not come up after several
retries.
30 - Core process gold The GoGlobal Login Daemon is not running.

does not run.
Check the GoGlobal-UX license using the command:
# /opt/graphon/etc/check_server
Check if the License Manager Daemon (lmgrd) is running:
# ps -ef | grep lmgrd
The GoGlobal Login Daemon logs errors in the /var/adm/syslog/syslog.log file.
Try to stop and start GoGlobal-UX:
# /sbin/init.d/goglobalux stop
# /sbin/init.d/goglobalux start
30 - Core process lm- Verify if the /opt/graphon/etc/license.dat file exists.

grd does not run.
Try to stop and start GoGlobal-UX:
# /sbin/init.d/goglobalux stop
# /sbin/init.d/goglobalux start
30 - Core process Check if the syntax of the httpd.conf file is correct:

httpd does not run.
# /opt/hpws/apache/bin/httpd -t
Verify the settings of the httpd:
# /opt/hpws/apache/bin/httpd -S
Verify that the ports 80 and 443 are assigned in the /etc/services file to http and
https services respectively.
Check the /opt/hpws22/apache/logs/error_log file for errors.
Stop and start the Apache server using, as user root, the commands:
# <NMS_GLOBAL_INSTANCE_DIR>/APACHE/script/apache_stop.sh
# <NMS_GLOBAL_INSTANCE_DIR>/APACHE/script/apache_start.sh
Check the logs in <NMS_GLOBAL_INSTANCE_DIR>/APACHE/logs, if httpd still
not running.
Contact the Nokia Support Team if the problem persists.
3BL 24534 AHAA PCAGA Ed.03 173 / 197

16 NMC2 supervision

message
30 - Core process nfsd Verify that NFS_CORE is set to "1" in the /etc/rc.config.d/nfsconf file.
does not run.
Check if the <rpcbind> and <nfs4srvkd> processes are running.
Try to stop and start the NFS server.
30 - Core process Verify that NFS_CORE is set to "1" in the /etc/rc.config.d/nfsconf file.
rpc.mountd does
Check if the rpc.mountd has ports assigned (look for mountd service entries),
not run.
using the command:
# rpcinfo -p
Try to stop and start the NFS server.
30 - Core pro- Execute as user root the following:

cesses nfsmapid,
On the NMC2 server:
nfs4clntkd or
nfs4srvkd do not # /sbin/init.d/nfs.client stop
run.
On the host where the NFS server is running, stop the NFS server.
On the NMC2 server:
# /sbin/init.d/nfs.core stop
# /sbin/init.d/nfs.core start
# /sbin/init.d/nfs.client start
On the host where the NFS server is running, start the NFS server.
30 - Core process nfs- Verify if the nfslogkd daemon has logged errors in the /var/adm/syslog/sys-
logkd does not run. log.log file.
Execute as user root the following:
On the NMC2 server:
# /sbin/init.d/nfs.client stop
On the NMC2 server:
174 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision

message
30 - Core process Check if the rpcbind has ports assigned (look for mountd service entries), using
rpcbind does not the command:
run.
# rpcinfo -p
On the NMC2 server:
# /sbin/init.d/nfs.client stop
On the NMC2 server:
30 - Core processes Verify that NFS_CORE is set to "1" in the /etc/rc.config.d/nfsconf file.
rpc.statd or
Check if the rpcbind process is running.
rpc.lockd do not
run. Enter as user root the following commands to kill rpc.statd and rpc.lockd:
# /usr/bin/ps -ef | grep rpc.statd
# kill <PID>
# /usr/bin/ps -ef | grep rpc.lockd
# kill <PID>
Enter the following commands to restart rpc.statd and rpc.lockd:
# /usr/sbin/rpc.statd
# /usr/sbin/rpc.lockd
Enter the following commands to verify that rpc.statd, rpc.lockd and nfsd are all
running and responding to RPC requests:
# /usr/bin/rpcinfo -u <NFS_server_host> status
# /usr/bin/rpcinfo -u <NFS_server_host> nlockmgr
# /usr/bin/rpcinfo -u <NFS_server_host> nfs
# /usr/bin/rpcinfo -u <NFS_client_host> status
# /usr/bin/rpcinfo -u <NFS_client_host> nlockmgr
# /usr/bin/rpcinfo -u <NFS_client_host> nfs
30 - Core process Verify if the rpc.ttdbserver service has logged errors in the /var/adm/syslog/sys-
rpc.ttdbserver log.log file.
does not run.
Enter as user root the following command to restart the rpc.ttdbserver service:
# /usr/sbin/inetd -c
3BL 24534 AHAA PCAGA Ed.03 175 / 197

16 NMC2 supervision

message
30 - Core process sshd Verify if the rpc.ttdbserver service has logged errors in the /var/adm/syslog/sys-
does not run. log.log file.
Enter as user root the following:
# /sbin/init.d/secsh stop
# /sbin/init.d/secsh start
30 - Core process swa- Verify if the swagentd daemon has logged errors in the /var/adm/sw/swa-
gentd does not run. gentd.log
Check for invalid or duplicate entries in the /etc/hosts file.
Verify the content of the /etc/resolv.conf file, if configured.
# /sbin/init.d/swagentd stop
# /sbin/init.d/swagentd start
30 - Core process smh- Log as user root and check the logs from the /var/opt/hpsmh/logs directory.
startd does not run.
# /opt/hpsmh/lbin/hpsmh stop
# /opt/hpsmh/lbin/hpsmh start
30 - Core processes Check the logs from the /etc/opt/resmon/log folder.

emsagent or
Execute as user root the following to restart the snmp daemons and the EMS
hp_unixagt does
agent:
not run.
# /sbin/init.d/emsa stop
# /sbin/init.d/SnmpHpunix stop
# /sbin/init.d/SnmpMib2 stop
# /sbin/init.d/SnmpMaster stop
# /sbin/init.d/SnmpMaster start
# /sbin/init.d/SnmpMib2 start
# /sbin/init.d/SnmpHpunix start
# /sbin/init.d/emsa start
30 - Core process kr- Contact the Nokia Support Team.

pckd does not run.
30 - Core process sys- Check the content of the /var/adm/syslog/syslog.log file.

logd does not run.
Restart the syslogd process by launching as user root the commands:
# /sbin/init.d/syslogd stop
# /sbin/init.d/syslogd start
Note that a new syslog.log file is created. The initial syslog.log file is moved to
OLDsyslog.log. Pay attention, that the old OLDsyslog.log is deleted.
176 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision

message
30 - Core process cron Check the /var/adm/syslog/syslog.log, /etc/rc.log and /var/adm/cron/log files
does not run. for errors.
Display the crontab file by executing as user root the following:
# crontab -l
Try to start the cron process by running as user root the command:
# /sbin/init.d/cron start
72 - The NFS server is Check the connexion with the host where the NFS server is running.
down or not reach-
Check file /var/adm/syslog/syslog.log for errors.
able. Home directo-
ries cannot be used Do as root user on NMC2 Master and Presentation:
- NFS badcalls statis- # /sbin/init.d/nfs.client stop
tics problem.
Connect as root user on the host where the NFS server is running and restart
- NFS client <id> NFS server.
hangs.
Do as root user on NMC2 Master and Presentation:
74 - Kerberos connex- To solve the problem, check the Kerberos connection to the missing host. A possi-
ion to host <host- ble problem might be different local times on the connecting hosts, or temporary
name> is broken. network problems in general.
75 - HA file replication Check the files from the <NMS_INSTANCE_DIR>/HA/log directory.

problem.
Resume HA replication in case of replication failure.
- HA data replication
Contact Nokia Technical Support Team if replication still fails after some retries.
problem.
75 - HA switchover Check the files from the <NMS_INSTANCE_DIR>/HA/log directory.

problem.
Perform SwitchOver again.
Contact Nokia Technical Support Team if SwitchOver still fails after some retries.
In case that an automatic switchover fails and both Master hosts become Standby
Masters, HA must be stopped on both Master hosts.
Use PMC to start the NMC2 instance on the intended Active Master, until all
processes are running.
Afterwards, HA must be restarted on both Master hosts.
75 - Connectivity with Check the connection with the stand-by host.

the stand-by node
A possible problem might be different local times on the HA hosts, or temporary
problem.
network problems in general.
After the connectivity is solved, start the HA and the HA replication. The alarm
will be cleared when the "replication ON" status is achieved.
3BL 24534 AHAA PCAGA Ed.03 177 / 197

16 NMC2 supervision

message
76 - The Check the <NMS_INSTANCE_DIR>/maintenance/log/smf.log and <NMS_IN-

/SMF/tools/sched- STANCE_DIR>/maintenance/trace/smf.trace files for errors.
uler/conf/sched-
Check the <NMS_INSTANCE_DIR>/SMF/tools/scheduler/data/traceDebug.sch
ulerdb.dat file is
log for errors.
corrupted.
Restart the SMF scheduler using the command:
# <NMS_INSTANCE_DIR>/SMF/tools/scheduler/script/restartSched-
Srv.sh
Check if the schedulerdb.dat file contains corrupted scheduled tasks (brackets or
curly brackets not closed, missing parameters or comma’s).
Use the Scheduler Management GUI to edit/recreate the faulty plan (task), if any.
76 - SMF scheduler is Check if the scheduler Server is running:

blocked.
# ps -ef | grep schedServer<NMS_SYSTEM><NMS_IN-
STANCE_NUM><NMS_DIGIT_VERSION>.sh
Check the <NMS_INSTANCE_DIR>/maintenance/log/smf.log and <NMS_IN-
STANCE_DIR>/maintenance/trace/smf.trace files for errors.
Srv.sh
76 - Scheduled task Verify the task’s syntax in the <NMS_INSTANCE_DIR>/SMF/tools/sched-

<id> corrupted def- uler/conf/schedulerdb.dat file (brackets or curly brackets not closed, missing
inition. parameters or comma’s).
Use the Scheduler Management GUI to edit/recreate the faulty plan (task), if any.
Check the <NMS_INSTANCE_DIR>/maintenance/log/smf.log and <NMS_IN-
STANCE_DIR>/maintenance/trace/smf.trace files for errors.
Srv.sh
76 - Scheduled task Check the <NMS_INSTANCE_DIR>/maintenance/log/smf.log and <NMS_IN-

<id> did not return STANCE_DIR>/maintenance/trace/smf.trace files for errors.
successfully.
Check the corresponding error from the <NMS_IN-
STANCE_DIR>/SMF/tools/scheduler/data/traceDebug.sch log.
Verify the task’s syntax in the <NMS_INSTANCE_DIR>/SMF/tools/sched-
uler/conf/schedulerdb.dat file.
Srv.sh
76 - Scheduled task Check the corresponding error from the <NMS_IN-

<id> is expired. STANCE_DIR>/SMF/tools/scheduler/data/traceDebug.sch log.
Open the Scheduler Management GUI, stop and start (Valid Plan) the faulty plan.
Verify if the error is cleared after the next scheduled run of the task.
178 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision

message
77 - Process ’<PID>’ The monitor that supervises the CPU usage of the running processes will periodi-
(’<name>’) exceeds cally check if CPU usage exceeds a threshold for any of the processes. A process
CPU usage upper (e.g. firefox) must be found running over the CPU threshold three times in a row
threshold. to produce this internal event.
Because sometimes high CPU usage can occur even under normal operations,
the operator should assess the situation:
- Check process information with the ’top’ command
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COM-
MAND
2 ? 26036 alvc3776 237 20 2080K 316K run 1:06 90.25 90.09 sh
- To get more details about the process name, use below command
# ps -efax | grep -i <PID>
alvc3776 26036 26029 232 12:23:01 ? 1:11 /bin/sh /opt/firefox/bin/firefox
-CreateProfile firefox _profile_alvc3776_slsm6i
- Monitor the process for some time. If the CPU process is not coming down, kill
the process with the following command:
# kill -9 <PID>
79 - Too many users Logoff stale /unused sessions.

are logged into the
Use Max Session Administration GUI to administer the maximum number of
system and further
user sessions allowed on the host.
logins are disabled.
88 - Filesystem <filesys- Check the directory structure of the filesystem for old logs, archives, oversized
tem> occupation is traces or core files.
<occupation>.
Extend filesystem if needed. Contact Nokia for support.
89 - Tunable <tun- Monitor the system and see if problem persists.

able> is over the
Check if the problem is linked to faulty NMC2 processes on the server.
<threshold>% us-
age threshold. Increase the value that the tunable can get. Contact Nokia for support.
16.3 NMC2 hardware supervision

16.3.1 Introduction to System Management Homepage
The System Management Homepage (SMH) from HP provides a web-based sys-
tem management functionality for monitoring the system’s hardware component
health. SMH provides a common interface for displaying hardware fault and sta-
tus monitoring, performance data, system thresholds and diagnostics.
SMH can be started directly from a browser window, using the URL shown below.
Root credentials are needed to log into the application.
https://<IP Address>:2381
3BL 24534 AHAA PCAGA Ed.03 179 / 197

16 NMC2 supervision
The IP address to use is the address of the HP-UX server that hosts the NMC2
virtual machine. The fully qualified name of that server can also be used.
16.3.2 Checking the hardware status

The SMH interface can display a multitude of informations regarding the hardware
faults, performance, thresholds and diagnostics for the NMC2 system.
For hardware details regarding Cooling, Memory, Power, Processors, Temperature
and Voltage, select the corresponding menu from Home -> System.
Figure 102: SMH Home tab
From the Cooling status window the Events window for the Cooling resources can
be accessed.
180 / 197 3BL 24534 AHAA PCAGA Ed.03

16 NMC2 supervision
Figure 103: Cooling status
Figure 104: Cooling events
For hardware status regarding Disks, select the Disks menu from Home-> Stor-
age.
3BL 24534 AHAA PCAGA Ed.03 181 / 197

16 NMC2 supervision
Figure 105: Disks status
182 / 197 3BL 24534 AHAA PCAGA Ed.03

17 CONFIGURATION OF MOZILLA FOR TELNET (mozex plugin)
17 CONFIGURATION OF MOZILLA FOR TELNET (mozex

plugin)
In case of HC34 NEs, Mozilla has to be configured for each user as described
below :
1. Log as the user
2. Launch Mozilla by entering the command line:
# /opt/mozilla/mozilla&
3. Open Edit menu and select “Preferences”
4. Select mozex in the left columm of the “Preferences” window

5. In the “mozex preferences” window, mark telnet ( see figure 106 )
in the general section, and type /usr/dt/bin/dtterm -e telnet %h %o in
the telnet related line.
3BL 24534 AHAA PCAGA Ed.03 183 / 197

17 CONFIGURATION OF MOZILLA FOR TELNET (mozex plugin)
Figure 106: Mark telnet
Figure 107: “mozex preferences” window
6. Click OK to confirm and close Mozilla

7. Exit
184 / 197 3BL 24534 AHAA PCAGA Ed.03

Appendix A: Access to the web console

Prerequisites The web secure terminal server is considered as installed.
An IP address has been allocated to this terminal server.
The UNIX station or the PC NT which executes the web browser is well installed.
The web browser can be either Netscape from version 4.75 or Microsoft® Ex-
plorer from version 5.5.
The user has got the documents dedicated to the web secure usage.
The user is assumed to have the HP Secure Web Console document.
Launching the web console 1. Launch your web browser.

2. In the URL area, enter the IP address of your terminal server:
For example: http :/ / 19 2 .2 00.2 54 .9 0/
A page is displayed.
3. Enter your login and password.
4. select Access C onsole and Z oom In/ Out
5. Press the <Enter> key to initialize the console.
The web console is ready to be used.
3BL 24534 AHAA PCAGA Ed.03 185 / 197

186 / 197 3BL 24534 AHAA PCAGA Ed.03

Appendix B: How to extend partitions

Log as root and launch :
bdf /usr/Systems/NMC2_1
You will get a return value similar to what follows :
/dev/vg00/lvol13 12943360 1425676 10798194 12% /usr/Sys-
tems/NMC2_1_140.1_Master
Then, launch these commands to extend this partition :
cd /usr/Systems/NMC2_1/script/
./Extention_partition.sh /usr/Systems/NMC2_1_<VERSION>_Master
<NEW-SIZE>
where <NEW-SIZE> is the total size of the partition after the extension in MB.
For example, in the previous case : NEW-SIZE = (12943360 +
2*1024*1024)/1024 = 14688
where <VERSION> is the version of the NMC2.
For example, in the previous case : VERSION = 140.1
After this, stop processes via PMC2 as following:
Log as axadmin in the server then launch the TMNOS system from desktop
Select the NMC2_1, and then launch in the menu bar of TMNOS: OS->Process
Monitoring.
The window of Process Monitoring will appear, and then stop all processes of
the NMC2 instance.
If necessary you should stop automatic control before, by clicking on the menu
Actions->Control->Deactivate
Reboot the system :

as root run this command sys,root # shutdown -ry now
After reboot, start processes via PMC2 as following:
Log as axadmin in the server then launch the TMNOS system from desktop
Select the NMC2_1, and then launch in the menu bar of TMNOS: OS->Process
Monitoring.
The window of Process Monitoring will appear, and then start all processes of
the NMC2 instance.
If necessary you should stop automatic control before, by clicking on the menu
Actions->Control->Activate
3BL 24534 AHAA PCAGA Ed.03 187 / 197

188 / 197 3BL 24534 AHAA PCAGA Ed.03

Appendix C: Appendix C: How to access to the MP interface for ITANIUM servers
Appendix C: Appendix C: How to access to the MP in-

terface for ITANIUM servers
The classic concept of the MP interface disappeared in virtual NMC2 R160. On
the contrary the VSP (host where the virtual machine is created) has the ILO.
The « hpvmconsole » command from the VSP replaces the hardware console ILO.
To acces the console MP console of the VMx (x is the VM index), tape from VSP
server :
# hpvmstatus
# hpvmconsole –px
vMP MAIN MENU
CO: Console
CM: Command Menu
CL: Console Log
SL: Show Event Logs
VM: Virtual Machine Menu
HE: Main Help Menu
X: Exit Connection
[XXXXX] vMP> co
or:
# hpvmstatus
# hpvmconsole –P guestname
vMP MAIN MENU

CO: Console
CM: Command Menu
SL: Show Event Logs
VM: Virtual Machine Menu
HE: Main Help Menu
X: Exit Connection
[XXXXX] vMP> co
3BL 24534 AHAA PCAGA Ed.03 189 / 197

C.1 How to configure ILO 2 TO MP

Access the iLO 2 MP using Use the local RS-232 serial port Remote/modem port. And RS-232 DB-9F to
RS-232 serial port as DB-9F modem eliminator cable.
following : Use the terminal emulation device runs software that interfaces with the server
(As HyperTerminal). The software emulates console output as it would appear
on an ASCII terminal screen and displays it on a console device screen.
To ensure the emulation software is correctly configured, verify the following:
Verify that the communication settings are configured as follows:
8/none (parity)
9600 baud
None (receive)
None (transmit)
Verify that the terminal type is configured appropriately. Supported terminal

types are as follows:
hpterm
vt100
vt100+
vt-utf8
Once the previous steps are done, The iLO 2 MP login prompt appears. Log in
using the default the iLO 2 MP user name and password (Admin/Admin). The MP
Main Menu screen appears :
Figure 108: MP main menu
Enter CM and press Enter. The prompt of command menu will appear. To con-
figure IP address, host name, subnet mask, and gateway address, enter LC.
190 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 109: MP configuration
If the “MAC address” field is empty, Enter - and press Enter.

— Enter the MAC address for MP LAN (See behind the server), and press Enter.
Follow the instructions on the screen to configure also IP address, host name,
subnet mask, and gateway address.
C.2 How to access to the MP

Connect to the Itanium server Management Port (MP) from a telnet or ssh client in
order to perform a manual reboot.
Note: If the MP is not configured, refer to the previous appendix.

Log to the MP the following window will shows up:
Figure 110: Connect to MP interface window
And choose Admin/Admin as “MP login/MP password”.

The following screen will show up :
3BL 24534 AHAA PCAGA Ed.03 191 / 197

Figure 111: Commands list of the MP interface
Type the following commands one at the time :
Y ou need t o p erf or m the f ol low i ng acti o ns qui ck l y i n

or d er to catch the ser ver EFI Boot Manag er, o therw i se
the server w i l l try to boot f rom the Pri mary har d d i sk .
cm (to enter to the command menu)

co (to enter to the console)
pc –off (to perform a hardware shutdown to the server)
pc –on (to turn the server on)
exit (to exit from cm)
192 / 197 3BL 24534 AHAA PCAGA Ed.03

Abbreviations
Abbreviations
A
AWP Administrator WorkPlace
CMC E10 Convergence Management Center for E10

CMISE Common Management Information Service Element
CORBA Common Object Request Broker Architecture
CPU Control Processing Unit
DAT Digital Audio Tape

DNS Domain Name Server
DSS Distributed Server System
EFI Extensible Firmware Interface : boot manager for Integrity servers (During
HP-UX integrity initial boot, EFI boot manager loads \efi\hpux\hpux.efi,
which reads the \efi\hpux\auto file to determine which kernel and mode
to boot. You can interrupt the HP-UX kernel loader when prompted and
Type the HP-UX kernel and mode to boot from.)
ENMS Element and Network Management Server
FTAM File Transfer Access and Management

FTP File Transfer Protocol
HMI Human Machine Interface

HMS Human Machine Interface Management Server
IM Information Manager
IP Internet Protocol
ITANIUM Integrity, ITANIUM, ia64 are the terms for new HP servers
MIB Management Information Base

MMC Man Machine Command
MML Man Machine Language
MOC Managed Object Class
MP Management Port interface for ITANIUM servers : plays the same role
as WEB console for PARISC servers
3BL 24534 AHAA PCAGA Ed.03 193 / 197

Abbreviations
NE Network Element
NMC2 Network Management Center, 2nd generation
NMS Network Management Server
NSAP Network Service Access Point
OWP Operator WorkPlace
PC Personal Computer
PID Process ID
PMC Process Monitoring Control
SCSI Small Computer Serial Interface

SMF System Management Functions
TRUSTED-UNIX Package that strengthen the HP-UX security rules
USM User Service Manager
WP WorkPlace
194 / 197 3BL 24534 AHAA PCAGA Ed.03

Index
Index
A Forcing user logout . . . . . . . . . . . . . . . . . . . . . . . . . 57
FTP flow control server . . . . . . . . . . . . . . . . . . . . . 162
Administrator Functional
role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
workplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Agent list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 G
Application process restart . . . . . . . . . . . . . . . . . . . 21
Applicative logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 General processes . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Group dependencies . . . . . . . . . . . . . . . . . . . . . . . 60
B Group list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 H
Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
OSS backup destination . . . . . . . . . . . . . . . . . . 131 Host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
OSS backup name . . . . . . . . . . . . . . . . . . . . . . 141
BDH file I
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
exporting to DAT . . . . . . . . . . . . . . . . . . . . . . . . 155
importing from DAT . . . . . . . . . . . . . . . . . . . . . 156 IOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
BDH file management . . . . . . . . . . . . . . . . . . . . . 153 Items/groups
BDH management . . . . . . . . . . . . . . . . . . . . . . . . . 143 starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
BDH management user interface . . . . . . . . . . . . 144 stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
BDH repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Broadcasting a message . . . . . . . . . . . . . . . . . . . . 53 L
Bulk data collection . . . . . . . . . . . . . . . . . . . . . . . . 149
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Log files
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
C Log FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Child list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16, 114
Log FTAM record
Command conventions . . . . . . . . . . . . . . . . . . . . . 15
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Command logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Control state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Log management . . . . . . . . . . . . . . . . . . . . . 93, 138
CORBA SNM API . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Log records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Crontab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
changing display mode . . . . . . . . . . . . . . . . . . 102
filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
D sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Domain files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Logins
bad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
E good . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
EFD management . . . . . . . . . . . . . . . . . . . . . . . . . 140 M

ENMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Machine state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
F Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Maintenance tools . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Failure management . . . . . . . . . . . . . . . . . . . . . . . 112 Maximum number of operators . . . . . . . . . . . . . . 28
3BL 24534 AHAA PCAGA Ed.03 195 / 197

Index
N R
Nectar OS calendar . . . . . . . . . . . . . . . . . . . . . . . . 92 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

NMC2 instance . . . . . . . . . . . . . . . . . . . . . . . . 26, 65 Restart mode
Node manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CPU charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 S
Node health status . . . . . . . . . . . . . . . . . . . . . . . . . 63
Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
O Scheduler plan
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Online documentation . . . . . . . . . . . . . . . . . . . . . . 23 deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Operator administration . . . . . . . . . . . . . . . . . . . . 33 editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
OS Snapshot triggering . . . . . . . . . . . . . . . . . . . . 113 validating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
OSS Server
declaring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Server configurations
OSS management . . . . . . . . . . . . . . . . . . . . . . . . . 146 DSS with HMS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
ENMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
P SSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Session
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42, 45 FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Management . . . . . . . . . . . . . . . . . . . . . . . . 51, 53
PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Snapshot management . . . . . . . . . . . . . . . . . . . . 112
command line tool . . . . . . . . . . . . . . . . . . . . . . . 67 Synchronizing configuration and data files . . . . . 70
log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Synchronizing systems . . . . . . . . . . . . . . . . . . . . . . 30
main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 System logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Presentation processes . . . . . . . . . . . . . . . . . . . . . . 17
Printer T
declaring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Text logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
personal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 TMN-OSs Management Window . . . . . . . . . . . . . 25
removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Trace files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Printer configuration . . . . . . . . . . . . . . . . . . . . . . . 119 clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 of agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 viewing dynamically . . . . . . . . . . . . . . . . . . . . . 110
failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 viewing statically . . . . . . . . . . . . . . . . . . . . . . . . 109
number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Trace levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
trace files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 U
Process Monitoring Control tool . . . . . . . . . . . . . . 59
User
Q creating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41, 42
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Q3ES login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41, 44
component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 password . . . . . . . . . . . . . . . . . . . . . . . . . . . 45, 148
external interface . . . . . . . . . . . . . . . . . . . . . . . . 124 profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34, 41
information model . . . . . . . . . . . . . . . . . . . . . . . 125 updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 User access rights . . . . . . . . . . . . . . . . . . . . . . . . . . 17
multi instances . . . . . . . . . . . . . . . . . . . . . . . . . . 126
OSS management . . . . . . . . . . . . . . . . . . . . . . . 128 W
processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Web console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
196 / 197 3BL 24534 AHAA PCAGA Ed.03

Index
Workstation
customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
unlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
X.733 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3BL 24534 AHAA PCAGA Ed.03 197 / 197

Administration Guide NMC2 R161 Ed03

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Administration Guide NMC2 R161 Ed03

Uploaded by

Copyright:

Available Formats

Nokia

3BL 24534 AHAA PCAGA Ed.03

2 / 197 3BL 24534 AHAA PCAGA Ed.03

3BL 24534 AHAA PCAGA Ed.03 3 / 197

5.7 Unlocking a workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 / 197 3BL 24534 AHAA PCAGA Ed.03

9.3.2 Archiving log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3BL 24534 AHAA PCAGA Ed.03 5 / 197

12.5.1 Accessing the log management user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

6 / 197 3BL 24534 AHAA PCAGA Ed.03

3BL 24534 AHAA PCAGA Ed.03 7 / 197

8 / 197 3BL 24534 AHAA PCAGA Ed.03

Figure 40: Trace file window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3BL 24534 AHAA PCAGA Ed.03 9 / 197

10 / 197 3BL 24534 AHAA PCAGA Ed.03

3BL 24534 AHAA PCAGA Ed.03 11 / 197

12 / 197 3BL 24534 AHAA PCAGA Ed.03

Contents This document is organized as follows:

3BL 24534 AHAA PCAGA Ed.03 13 / 197

Referenced documents The documents referenced in this guide are as follows:

14 / 197 3BL 24534 AHAA PCAGA Ed.03

1 Introduction to technical concepts and principles of

1.1 Command conventions

For example, the UNIX command "date" is written # date [CR].

3BL 24534 AHAA PCAGA Ed.03 15 / 197

Figure 1: Example of the system response to a command

1.2 Role of the administrator

perform preventive maintenance operations:

perform corrective maintenance operations in the case of a:

1.3 Host name

16 / 197 3BL 24534 AHAA PCAGA Ed.03

1.4 System management processes

3BL 24534 AHAA PCAGA Ed.03 17 / 197

1.5 Supported NMC2 hardware configurations

Supported Configurations Three configurations may exist :

the Distributed Server System (DSS) with HMS

18 / 197 3BL 24534 AHAA PCAGA Ed.03

1.6 Services in distributed architectures

The SSS architecture is not a distributed architecture but a standalone architecture.

Table 1: Services in distributed architectures

Architecture Server type Manages what

DSS-HMS ENMS All CMC E10 functions

3BL 24534 AHAA PCAGA Ed.03 19 / 197

1.6.1 DSS-HMS architecture

1.7 Server shutdown and restart

1.7.1 Shutting down and reboot a server

1.7.2 Shutting down complete a server

20 / 197 3BL 24534 AHAA PCAGA Ed.03

To shut down a server

1.7.3 Restarting a server

1.7.4 Shutting down or restarting a server gracefully

1.8 Maintenance tools

3BL 24534 AHAA PCAGA Ed.03 21 / 197

The maintenance directory can be located under the <NMS_INSTANCE_DIR>

Figure 2: Maintenance directory

backup on the slave server this directory will be empty. On the

22 / 197 3BL 24534 AHAA PCAGA Ed.03

2 Online user documentation

2.1 Installing the ADES documentary collection

Figure 3: Device Name of source media

Figure 4: Collection type

3BL 24534 AHAA PCAGA Ed.03 23 / 197

Copying the collection NMC2 on the disk...

2.2 Removing the ADES documentary collection