N2000 System User Manual

iManager N2000 DMS Datacomm Network Management
System
V500R003C01
Administrator Guide - Solaris
Issue 06
Date 2010-06-21
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 06 (2010-06-21) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
System
Administrator Guide - Solaris About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager N2000 DMS V500R003C01

Datacomm Network
Management System
Intended Audience
This guide provides management guides to the following aspects: secure startup and shutdown
of the N2000 DMS, system settings, security management, users, logs, processes and services,
databases, and files and disks. It also provides operation guides to routine maintenance,
emergency maintenance, and troubleshooting.
This document is intended for:
l Installation and commissioning engineer

l N2000 DMS administrator
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
Issue 06 (2010-06-21) Huawei Proprietary and Confidential iii

System
About This Document Administrator Guide - Solaris
Symbol Description
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
iv Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
Administrator Guide - Solaris About This Document
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 06 (2010-06-21)

Sixth commercial release.

Fifth commercial release.

Fourth commercial release.

Third commercial release.

Second commercial release.

Initial field trial release.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential v

System
Administrator Guide - Solaris Contents
Contents
About This Document...................................................................................................................iii

1 Starting and Shutting Down the N2000 DMS Server.........................................................1-1
1.1 Starting the N2000 DMS.................................................................................................................................1-2
1.1.1 Starting the N2000 DMS Server............................................................................................................1-2
1.1.2 Logging In to the N2000 DMS Client....................................................................................................1-3
1.2 Shutting Down the N2000 DMS.....................................................................................................................1-5
1.2.1 Quitting the N2000 DMS Client............................................................................................................1-5
1.2.2 Shutting Down the N2000 DMS Server.................................................................................................1-6
2 Setting the N2000 DMS Time..................................................................................................2-1

2.1 N2000 DMS Time Synchronization Solutions................................................................................................2-2
2.1.1 Purpose of Time Synchronization..........................................................................................................2-2
2.1.2 Time Synchronization Principle.............................................................................................................2-2
2.1.3 Time Synchronization Plans...................................................................................................................2-5
2.2 Setting the N2000 DMS Server Time.............................................................................................................2-5
2.2.1 Modifying the N2000 DMS Server Time Zone.....................................................................................2-5
2.2.2 Modifying the Time and Date of the N2000 DMS Server.....................................................................2-6
2.3 Setting the NTP Service for the N2000 DMS Server......................................................................................2-7
2.3.1 NTP Service Overview...........................................................................................................................2-8
2.3.2 Checking the N2000 DMS Server Time Configuration.........................................................................2-9
2.3.3 Setting the N2000 DMS Server to the Secondary Time Server.............................................................2-9
2.3.4 Setting the N2000 DMS Server to the NTP Client..............................................................................2-10
2.3.5 Starting the NTP Service on the N2000 DMS Server..........................................................................2-11
2.3.6 Stopping the NTP Service on the N2000 DMS Server........................................................................2-11
2.3.7 Querying the Status of the NTP Service..............................................................................................2-12
2.4 Setting the Daylight Saving Time for the N2000 DMS Server.....................................................................2-13
2.4.1 Daylight Saving Time Overview..........................................................................................................2-14
2.4.2 Viewing the Daylight Saving Time Rule of a Time Zone...................................................................2-14
2.4.3 Changing the Time Zone of the N2000 DMS Server...........................................................................2-15
2.5 Modifying the Date, Time, and Time Zone of the N2000 DMS Client........................................................2-16
2.6 Setting the N2000 DMS Client to the NTP Client........................................................................................2-17
3 Setting N2000 DMS Server Parameters..................................................................................3-1

3.1 Setting N2000 DMS Environment Variables..................................................................................................3-2
Issue 06 (2010-06-21) Huawei Proprietary and Confidential vii

System
Contents Administrator Guide - Solaris
3.2 Changing the Host Name of the N2000 DMS Server.....................................................................................3-2

3.3 Changing the IP Address of the N2000 DMS Server......................................................................................3-3
3.4 Setting Routes on the N2000 DMS Server......................................................................................................3-5
3.5 Setting the Login Mode of the N2000 DMS...................................................................................................3-6
4 Managing the N2000 DMS Client...........................................................................................4-1

4.1 Changing to Another N2000 DMS Server......................................................................................................4-2
4.2 Setting the Login Mode on the N2000 DMS Client........................................................................................4-2
4.3 Setting Maximum Online Users on the N2000 DMS Client...........................................................................4-3
4.4 Monitoring Login Statuses of N2000 DMS Users..........................................................................................4-3
5 N2000 DMS Security Management.........................................................................................5-1

5.1 Policies of the N2000 DMS Security Management........................................................................................5-2
5.1.1 Policies of Security Protocols................................................................................................................5-3
5.1.2 OS Security Policies...............................................................................................................................5-3
5.1.3 User Security Policies............................................................................................................................5-4
5.1.4 Policies of the N2000 DMS Log Management......................................................................................5-5
5.1.5 Database Security...................................................................................................................................5-5
5.2 Setting Communication Security Between the Server and the Client.............................................................5-6
6 Managing the N2000 DMS Users............................................................................................6-1

6.1 Users and Rights..............................................................................................................................................6-2
6.1.1 Concepts Related to the N2000 DMS Users..........................................................................................6-2
6.1.2 N2000 DMS User Rights Assignment Policies......................................................................................6-4
6.1.3 OS User..................................................................................................................................................6-5
6.1.4 Database User.........................................................................................................................................6-5
6.1.5 NMS Users and Rights...........................................................................................................................6-6
6.2 Managing Users in OS....................................................................................................................................6-6
6.2.1 Creating an OS User...............................................................................................................................6-7
6.2.2 Changing the Password of root..............................................................................................................6-7
6.2.3 Changing the Password of n2kuser........................................................................................................6-8
6.2.4 Changing the Password of OS User sybase...........................................................................................6-8
6.3 Managing Database Users...............................................................................................................................6-9
6.3.1 Changing the Password of sa.................................................................................................................6-9
6.3.2 Changing the Password of N2000 DMS User......................................................................................6-10
6.4 Setting the N2000 DMS User Security.........................................................................................................6-12
6.4.1 Setting the Login Mode of the N2000 DMS........................................................................................6-12
6.4.2 Setting the Password Policy.................................................................................................................6-13
6.4.3 Setting the User Account Policy..........................................................................................................6-14
6.4.4 Setting the ACL....................................................................................................................................6-15
6.4.5 Modifying the Validity Period of an N2000 DMS User Account........................................................6-16
6.4.6 Modifying the Validity Period of an N2000 DMS User Password......................................................6-16
6.4.7 Setting the Period for Disabling an N2000 DMS User Account..........................................................6-16
6.4.8 Initializing an N2000 DMS User Password.........................................................................................6-17
viii Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
6.5 Creating N2000 DMS Users.........................................................................................................................6-17

6.5.1 Process of Creating an N2000 DMS User............................................................................................6-18
6.5.2 Creating Device Set..............................................................................................................................6-20
6.5.3 Creating an N2000 DMS Operation Set...............................................................................................6-21
6.5.4 Creating a User Group..........................................................................................................................6-22
6.5.5 Assigning a Managed Domain to a User Group..................................................................................6-23
6.5.6 Assigning Operation Rights to a User Group.......................................................................................6-24
6.5.7 Assigning Device Management Rights to a User Group.....................................................................6-26
6.5.8 Creating an N2000 DMS User.............................................................................................................6-27
6.5.9 Adding an N2000 DMS User to a User Group....................................................................................6-28
6.5.10 Assigning a Managed Domain to an N2000 DMS User....................................................................6-29
6.5.11 Assigning Operation Rights to an N2000 DMS User........................................................................6-30
6.5.12 Setting the ACL for N2000 DMS Users............................................................................................6-31
6.6 Example of Creating an N2000 DMS User...................................................................................................6-32
6.7 Modifying N2000 DMS Users......................................................................................................................6-33
6.7.1 Modifying the Member of an N2000 DMS Operation Set...................................................................6-34
6.7.2 Modifying the Properties of an N2000 DMS User..............................................................................6-34
6.7.3 Changing the User Group That an N2000 DMS User Belongs To......................................................6-35
6.7.4 Modifying the ACL for N2000 DMS Users.........................................................................................6-36
6.7.5 Modifying the Management Domain of an N2000 DMS User............................................................6-37
6.7.6 Modifying the Operation Rights of an N2000 DMS User...................................................................6-38
6.7.7 Modifying the General Attributes of a User Group.............................................................................6-39
6.7.8 Modifying the Managed Domain of a User Group..............................................................................6-39
6.7.9 Modifying the Operation Rights of a User Group................................................................................6-40
6.7.10 Changing an N2000 DMS User Password.........................................................................................6-41
6.8 Monitoring N2000 DMS Users.....................................................................................................................6-41
6.8.1 Querying Login User Information........................................................................................................6-41
6.8.2 Monitoring User Operations in Real Time...........................................................................................6-42
6.8.3 Forcing a Login User to Exit................................................................................................................6-43
6.8.4 Unlocking a User Account...................................................................................................................6-44
6.8.5 Sending Messages to Online Users......................................................................................................6-44
7 Managing N2000 DMS Logs....................................................................................................7-1

7.1 Log Types........................................................................................................................................................7-2
7.1.1 N2000 DMS Security Logs....................................................................................................................7-2
7.1.2 N2000 DMS Operation Logs................................................................................................................. 7-2
7.1.3 System Logs...........................................................................................................................................7-2
7.1.4 Debugging Logs.....................................................................................................................................7-3
7.2 Managing NMS Security Logs........................................................................................................................7-4
7.2.1 Browsing Security Logs.........................................................................................................................7-4
7.2.2 Dumping Security Logs Manually.........................................................................................................7-5
7.2.3 Setting Auto Dump of Security Logs.....................................................................................................7-6
7.3 Managing NMS Operation Logs.....................................................................................................................7-7
Issue 06 (2010-06-21) Huawei Proprietary and Confidential ix

System
7.3.1 Browsing Operation Logs......................................................................................................................7-8

7.3.2 Dumping Operation Logs Manually......................................................................................................7-9
7.3.3 Setting Auto Dump of Operation Logs................................................................................................7-10
7.4 Managing Remote Notification Logs............................................................................................................7-11
7.4.1 Browsing Remote Notification Logs....................................................................................................7-11
7.4.2 Resending Remote Notification Messages...........................................................................................7-11
7.4.3 Forwarding Remote Notification Messages.........................................................................................7-12
7.5 Setting a Log Forwarding Server..................................................................................................................7-12
8 Managing N2000 DMS Processes and Services....................................................................8-1

8.1 Processes and Services....................................................................................................................................8-3
8.1.1 Start Modes of Processes........................................................................................................................8-3
8.1.2 List of N2000 DMS Processes...............................................................................................................8-3
8.2 Setting Server Thresholds.............................................................................................................................8-16
8.2.1 Relations Between Thresholds and Alarms.........................................................................................8-16
8.2.2 Setting the Performance Threshold......................................................................................................8-16
8.3 Monitoring Process Status.............................................................................................................................8-17
8.4 Monitoring Database Status..........................................................................................................................8-18
8.5 Monitoring the Status of the N2000 DMS Server Performance...................................................................8-18
8.6 Monitoring Hard Disk Status........................................................................................................................8-19
8.7 Managing N2000 DMS Processes.................................................................................................................8-19
8.8 Starting the N2000 DMS Service..................................................................................................................8-20
8.9 Setting Sampling...........................................................................................................................................8-20
8.9.1 Manual Sampling.................................................................................................................................8-20
8.9.2 Automatic Sampling.............................................................................................................................8-21
8.10 Stopping the N2000 DMS Service..............................................................................................................8-22
9 Managing N2000 DMS Databases..........................................................................................9-1

9.1 Basic Concepts About Databases....................................................................................................................9-3
9.1.1 N2000 DMS Database Overview...........................................................................................................9-3
9.1.2 Introduction to Database Backup Tool...................................................................................................9-5
9.1.3 Differences Between Dump and Backup...............................................................................................9-5
9.2 Starting the Database Backup Tool.................................................................................................................9-6
9.3 Setting the Database Server.............................................................................................................................9-7
9.4 Viewing the Database......................................................................................................................................9-7
9.5 Setting the Backup Device..............................................................................................................................9-8
9.6 Setting the Database Set................................................................................................................................9-10
9.7 Configuring the Timing Backup Policy........................................................................................................9-12
9.8 Backing Up the N2000 DMS Database Manually........................................................................................9-14
9.9 Configuring a Timing Backup Task..............................................................................................................9-16
9.10 Querying Backup and Restoration Logs.....................................................................................................9-17
9.11 Expanding an N2000 DMS Database..........................................................................................................9-17
9.11.1 Through the GUI................................................................................................................................9-17
9.11.2 Through the Command Line..............................................................................................................9-18
x Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
9.12 Clearing an N2000 DMS Database.............................................................................................................9-19

9.12.1 Setting Auto Dump of Alarms...........................................................................................................9-19
9.12.2 Setting Auto Dump of Events............................................................................................................9-20
9.12.3 Setting Auto Dump of Security Logs.................................................................................................9-21
9.12.4 Setting Auto Dump of Operation Logs..............................................................................................9-22
9.12.5 Dumping Alarms Manually................................................................................................................9-23
9.12.6 Dumping Events Manually.................................................................................................................9-24
9.12.7 Dumping Security Logs Manually.....................................................................................................9-26
9.12.8 Dumping Operation Logs Manually..................................................................................................9-26
9.12.9 Clearing the Transaction Log Space..................................................................................................9-27
10 Managing N2000 DMS Files and Disks.............................................................................10-1

10.1 N2000 DMS File Systems...........................................................................................................................10-2
10.1.1 N2000 DMS Server File System........................................................................................................10-2
10.1.2 N2000 DMS Client File System.........................................................................................................10-3
10.2 Viewing Disk Usage of the N2000 DMS Server........................................................................................10-4
10.3 Clearing Disk Space....................................................................................................................................10-5
10.3.1 Cleaning Up the N2000 DMS Server Disk Space..............................................................................10-5
10.3.2 Cleaning Up the N2000 DMS Client Disk Space..............................................................................10-6
11 N2000 DMS Routine Maintenance.....................................................................................11-1

11.1 Suggestions on Secure Running..................................................................................................................11-2
11.2 Routine Maintenance List...........................................................................................................................11-2
11.3 Daily Maintenance......................................................................................................................................11-3
11.3.1 Monitoring Process Status..................................................................................................................11-4
11.3.2 Monitoring Database Status...............................................................................................................11-4
11.3.3 Monitoring the Status of the N2000 DMS Server Performance........................................................11-5
11.3.4 Monitoring Hard Disk Status.............................................................................................................11-5
11.3.5 Monitoring User Operations in Real Time.........................................................................................11-5
11.3.6 Viewing N2000 DMS Alarms............................................................................................................11-6
11.3.7 Checking Exception Logs of the OS..................................................................................................11-9
11.3.8 Checking Database Logs....................................................................................................................11-9
11.4 Weekly Maintenance.................................................................................................................................11-10
11.4.1 Monitoring Hard Disk Status...........................................................................................................11-11
11.4.2 Checking the Disk Status of the N2000 DMS Server......................................................................11-11
11.4.3 Checking the N2000 DMS Server Time..........................................................................................11-12
11.4.4 Manually Backing Up an N2000 DMS Database............................................................................11-12
11.4.5 Backing Up Databases Periodically.................................................................................................11-13
11.5 Monthly Maintenance...............................................................................................................................11-14
11.5.1 Checking Hardware Devices of the N2000 DMS............................................................................11-14
11.5.2 Backing Up the N2000 DMS Files..................................................................................................11-15
11.5.3 Deleting N2000 DMS User Rights...................................................................................................11-15
11.5.4 Changing an N2000 DMS User Password.......................................................................................11-16
11.5.5 Collecting Monthly Alarm Statistics................................................................................................11-16
Issue 06 (2010-06-21) Huawei Proprietary and Confidential xi

System
11.5.6 Checking System Logs.....................................................................................................................11-17

11.5.7 Checking the Ambient Temperature and Fan Status........................................................................11-18
11.5.8 Cleaning Up the Disk Space of the N2000 DMS Server.................................................................11-18
11.5.9 Checking the Equipment Room Environment.................................................................................11-19
12 N2000 DMS Emergency Maintenance................................................................................12-1

12.1 Emergency Maintenance Overview............................................................................................................12-2
12.2 Emergency Maintenance Flow....................................................................................................................12-2
12.3 Emergency Maintenance Preparations........................................................................................................12-4
12.3.1 Backing Up the System Files.............................................................................................................12-4
12.3.2 Backing Up the N2000 DMS Data.....................................................................................................12-4
12.3.3 Checking Necessary Items.................................................................................................................12-4
12.4 Guide to Emergency Maintenance of the N2000 DMS Server...................................................................12-5
12.4.1 Reinstalling OS..................................................................................................................................12-5
12.4.2 Reinstalling Database.........................................................................................................................12-6
12.4.3 Reinstalling the N2000 DMS Software..............................................................................................12-6
12.4.4 Restoring the Solaris System Files.....................................................................................................12-6
12.4.5 Restoring the Sybase Files.................................................................................................................12-6
12.4.6 Restoring the N2000 DMS Files........................................................................................................12-6
12.4.7 Restoring the N2000 DMS Data........................................................................................................12-7
12.5 Checking the System Recovery Results......................................................................................................12-7
12.5.1 Checking the N2000 DMS Service Status.........................................................................................12-7
12.5.2 Checking the Sybase Service Status...................................................................................................12-8
12.5.3 Checking Data Synchronization.........................................................................................................12-8
12.6 Seeking for Technical Support from Huawei..............................................................................................12-9
13 N2000 DMS Fault Handling.................................................................................................13-1

13.1 Procedure for Handling a Fault...................................................................................................................13-3
13.2 Troubleshooting Precautions.......................................................................................................................13-4
13.3 Discovering a Fault.....................................................................................................................................13-5
13.4 Handling the N2000 DMS Alarm...............................................................................................................13-5
13.4.1 Port Connection Interrupted Between NMS and Command Line Device.........................................13-6
13.4.2 CPU Alarm of the NMS Server..........................................................................................................13-6
13.4.3 Hard Disk Alarm of the NMS Server.................................................................................................13-7
13.4.4 NMS Server Physical Memory Alarm...............................................................................................13-8
13.4.5 NMS Server Virtual Memory Alarm.................................................................................................13-9
13.4.6 NMS Server Database Data Space Alarm........................................................................................13-10
13.4.7 NMS Server Database Transaction Log Space Alarm.....................................................................13-10
13.4.8 Availability of the NMS Server Service Alarm...............................................................................13-11
13.4.9 Illegal Login Alarm..........................................................................................................................13-12
13.4.10 Trap Receiver Disconnection.........................................................................................................13-12
13.4.11 NMS NE License Alarm................................................................................................................13-13
13.4.12 Avalanche Alarm............................................................................................................................13-14
13.4.13 The Number of Records in the Database Table Reaches the Threshold........................................13-14
xii Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
13.4.14 Switch to the Slave Syslog Server..................................................................................................13-15

13.4.15 Failed to Connect the Syslog Server..............................................................................................13-16
13.4.16 NMS Client Exits Abnormally.......................................................................................................13-17
13.4.17 Sending the Remote Notification SMS Gateway Message Fails...................................................13-18
13.5 Collecting Fault Information.....................................................................................................................13-18
13.5.1 Collecting the Alarm Information....................................................................................................13-19
13.5.2 Collecting the Log Information........................................................................................................13-19
13.5.3 Collecting the Version Information..................................................................................................13-20
13.5.4 Collecting the Core File...................................................................................................................13-21
13.5.5 Collecting the Process Running Information...................................................................................13-22
13.6 Determining Fault Causes.........................................................................................................................13-22
13.7 Eliminating a Fault....................................................................................................................................13-22
13.8 Checking Whether the Fault Is Cleared....................................................................................................13-23
13.8.1 Checking Whether the Alarm Is Cleared.........................................................................................13-23
13.8.2 Clearing Alarms Manually...............................................................................................................13-24
13.8.3 Checking Whether Performance Specifications of the N2000 DMS Server Are Normal...............13-25
13.9 Recording Alarm Maintenance Experiences.............................................................................................13-25
14 N2000 DMS FAQs..................................................................................................................14-1

14.1 Solaris OS....................................................................................................................................................14-2
14.1.1 How to View the Concrete Version and Date of the Solaris OS........................................................14-2
14.1.2 How to Start the Workstation from the CD-ROM.............................................................................14-2
14.1.3 How to Rectify the Fault That the CD-ROM Cannot Be Ejected......................................................14-3
14.1.4 How to Transfer Binary Files Through FTP......................................................................................14-3
14.1.5 How to Rectify the Fault That the Executable Right of an Executable File Is Lost..........................14-3
14.1.6 How to Decompress the *.tar.gz File.................................................................................................14-4
14.1.7 How to Log in as the root User When Using the Telnet...................................................................14-4
14.1.8 How to Log in as the root User When Using FTP.............................................................................14-4
14.1.9 How to View the Hardware Configuration of the Server...................................................................14-5
14.1.10 Starting the N2000 DMS as the root User Failed............................................................................14-8
14.1.11 Why Does the N2000 DMS Server Process Exit When I Press Ctrl+C..........................................14-9
14.1.12 How to Set the ACL for a Server with Multiple Network Adapters................................................14-9
14.2 Sybase Database........................................................................................................................................14-10
14.2.1 How to Check Whether the Sybase Database Is Started..................................................................14-10
14.2.2 How to Manually Start the Sybase Database...................................................................................14-10
14.2.3 How to Manually Stop the Sybase Database...................................................................................14-11
14.2.4 How to View the Bit Number of the Sybase Database....................................................................14-11
14.2.5 How to Change the License of the Sybase Database.......................................................................14-12
14.2.6 How to Process the Abnormal Stop of the Backup Sybase Database..............................................14-12
14.2.7 How to View the Deadlock Information in the Database................................................................14-13
14.3 N2000 DMS Software...............................................................................................................................14-14
14.3.1 How to Obtain Version Information................................................................................................14-14
14.3.2 Invalid User Name or Password Is Prompted When the Client Automatically Upgrades...............14-14
Issue 06 (2010-06-21) Huawei Proprietary and Confidential xiii

System
14.3.3 Client Does Not Respond For a Long Time.....................................................................................14-15

14.4 Security Management................................................................................................................................14-15
14.4.1 A User Cannot Log In After the Client Exits Abnormally..............................................................14-16
14.4.2 Cannot Find the Operation Objects When Assigning Operation Rights..........................................14-16
14.4.3 Server Cannot Start After the License Is Updated...........................................................................14-16
A N2000 DMS Command Reference........................................................................................A-1

A.1 N2000 DMS Command Reference................................................................................................................A-2
A.2 Solaris Common Reference...........................................................................................................................A-2
A.2.1 Commands for Operating Solaris Directories......................................................................................A-2
A.2.2 Commands for Operating Solaris Files................................................................................................A-6
A.2.3 Commands for Viewing Solaris Files.................................................................................................A-20
A.2.4 Commands for Solaris User Management..........................................................................................A-27
A.2.5 Commands for Managing Solaris System Resources.........................................................................A-31
A.2.6 Commands for Solaris Network Communication..............................................................................A-47
B N2000 DMS Services and Processes......................................................................................B-1

B.1 N2000 DMS (iMAP) Processes.....................................................................................................................B-2
B.1.1 Message Distribution Process: mdp......................................................................................................B-2
B.1.2 System Monitoring Process: EmfSysMoniDm.....................................................................................B-3
B.1.3 Scheduled Task Process: EmfSchdSvr.................................................................................................B-4
B.1.4 Security Management Process: EmfSecuDm.......................................................................................B-5
B.1.5 Topology Process: EmfTopoDm..........................................................................................................B-6
B.1.6 Fault Process: EmfFaultDm..................................................................................................................B-7
B.1.7 Alarm Synchronization Process: EmfFaultSynDm..............................................................................B-8
B.1.8 Alarm Agent Process: EmfAlarmAgent...............................................................................................B-9
B.1.9 Trap Report and Explanation Process: EmfTrapReceiver..................................................................B-10
B.1.10 Real-Time Performance Process: EmfPerfDm.................................................................................B-11
B.1.11 Third-Party Device Configuration Management Process: EmfGnlDevDm.....................................B-12
B.1.12 Device Access Proxy Process: EmfProxyServer..............................................................................B-13
B.1.13 SNMP Forwarding Process: ForwardAgent.....................................................................................B-14
B.1.14 Database Backup Process: EmfDBBackup.......................................................................................B-15
B.1.15 Test Process: EmfExamDm..............................................................................................................B-16
B.1.16 Project Document Process: EmfProjDocDm....................................................................................B-17
B.1.17 Northbound Interface Module (SNMP) Process: SNMPAgent........................................................B-18
B.1.18 Northbound Interface Module (CORBA) Process: iAF_Agent........................................................B-19
B.1.19 Northbound Interface Module (XML) Process: iAF_XMLAgent....................................................B-20
B.1.20 CORBA Notification Service Process: iagent_nt.............................................................................B-22
B.1.21 CORBA Naming Service Process: Naming_Service........................................................................B-22
B.1.22 Log Forwarding Process: EmfSyslogAgent......................................................................................B-23
B.2 N2000 DMS Processes................................................................................................................................B-24
B.2.1 Layer 2 View Management Process: DmsL2VDm............................................................................B-25
B.2.2 N2000 DMS SysLog Collector Process: DmsSyslogCollector..........................................................B-26
B.2.3 Resource Management Process: DmfResDm.....................................................................................B-27
xiv Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
B.2.4 Command Line Interface Drive Process: DmfClidrvDm...................................................................B-28

B.2.5 Data Center Management Process: DmsDcDm..................................................................................B-29
B.2.6 IP View Management Process: Dmsipdm..........................................................................................B-30
B.2.7 Cluster Management Process: UcmDm..............................................................................................B-31
B.2.8 ME60 and MA5200 Series Device Management Process: DmsMseDm............................................B-32
B.2.9 Quidway Device Management Process: DmsQvxDm........................................................................B-33
B.2.10 N2000 DMS RPR View Management Process: DmsrprDm............................................................B-35
B.2.11 N2000 DMS Syslog Management Process: DmsSyslogDm............................................................B-36
B.2.12 N2000 DMS NeMpls Management Process: NeMplsDm................................................................B-37
B.2.13 Collector Module Process: ColAgentDm.........................................................................................B-37
B.2.14 Collector Process: CollectorDm.......................................................................................................B-39
B.2.15 Collector Manager Process: CollectorMgrDm.................................................................................B-40
B.2.16 General Configuration Template Process: GctlDm..........................................................................B-41
B.2.17 Link Management Process: DmsLinkMgrDm..................................................................................B-42
B.2.18 Performance Configuration Process: DmsPerfConfDm...................................................................B-42
B.2.19 Performance Probe Process: DmsPerfProbeDm...............................................................................B-43
B.2.20 Performance Poll Process: DmsPerfPollDm.....................................................................................B-44
B.2.21 T&D Management Process: VasDiagDm.........................................................................................B-45
B.2.22 Service Management Process: DmsScDm........................................................................................B-46
B.2.23 SecPolicyMgrDm..............................................................................................................................B-47
B.3 N2000 DMS Services and Ports..................................................................................................................B-48
B.3.1 Common Services and the Related Port Lists.....................................................................................B-49
B.3.2 List of Ports for System Services........................................................................................................B-53
B.3.3 List of Ports for Two-Node Cluster Services......................................................................................B-54
C IP Address Migration..............................................................................................................C-1
C.1 IP Address Migration Scenarios....................................................................................................................C-2
C.2 Migrating the IP Address of the Server.........................................................................................................C-2
C.3 Migrating the IP Address of the NMS...........................................................................................................C-3
C.4 Migrating the IP Address Related to NE Software Management..................................................................C-4
C.5 Migrating the IP Addresses Related to the Report Server.............................................................................C-5
C.6 Migrating the IP Address of a Managed Device............................................................................................C-6
D Changing a Password by Using the IP Tool.......................................................................D-1

E Glossary.......................................................................................................................................E-1
F Acronyms and Abbreviations..................................................................................................F-1
Issue 06 (2010-06-21) Huawei Proprietary and Confidential xv

System
Administrator Guide - Solaris Figures
Figures
Figure 1-1 Rotary switch......................................................................................................................................1-2

Figure 2-1 NTP synchronization principle...........................................................................................................2-3
Figure 2-2 NTP hierarchical networking..............................................................................................................2-4
Figure 2-3 NTP synchronization network............................................................................................................2-8
Figure 6-1 Adding rights to manage devices......................................................................................................6-26
Figure 12-1 Emergency maintenance flowchart.................................................................................................12-3
Figure 13-1 Flow for handling a fault................................................................................................................13-3
Issue 06 (2010-06-21) Huawei Proprietary and Confidential xvii

System
Administrator Guide - Solaris Tables
Tables
Table 6-1 Simple process of creating an N2000 DMS user...............................................................................6-19

Table 6-2 Complete process of creating an N2000 DMS user...........................................................................6-19
Table 7-1 Parameters of system running logs......................................................................................................7-3
Table 7-2 Debugging logs....................................................................................................................................7-4
Table 8-1 List of N2000 DMS processes and services.........................................................................................8-3
Table 10-1 Directory structure of the N2000 DMS server ................................................................................10-2
Table 10-2 Directory structure of the N2000 DMS client .................................................................................10-4
Table 11-1 Routine maintenance list..................................................................................................................11-2
Table 11-2 Checking the ambient temperature of the equipment room and the fan status..............................11-18
Table 13-1 Fault handling procedure..................................................................................................................13-4
Table A-1 Common programs in the Solaris OS.................................................................................................A-2
Table A-2 Commands for browsing and controlling the directory......................................................................A-3
Table A-3 Option description of the ls command...............................................................................................A-5
Table A-4 Commands for operating a file...........................................................................................................A-7
Table A-5 Common options in symbol mode of the chmod command .............................................................A-9
Table A-6 Conditions for file search.................................................................................................................A-12
Table A-7 Logical operators of conditions........................................................................................................A-13
Table A-8 Option description for the tar command..........................................................................................A-14
Table A-9 Descriptions of gtar command options.............................................................................................A-16
Table A-10 Commands for displaying and browsing the contents of a text file...............................................A-20
Table A-11 Option description of the echo command.......................................................................................A-21
Table A-12 Option description of the more command......................................................................................A-23
Table A-13 Operations in the text input mode..................................................................................................A-26
Table A-14 Operations related to moving the cursor in the text input mode....................................................A-26
Table A-15 Operation for exiting the text input mode and switching to the command mode..........................A-26
Table A-16 Operations related to deleting characters in the command mode...................................................A-27
Table A-17 Commands for exiting the vi editor................................................................................................A-27
Table A-18 Commands for user management...................................................................................................A-27
Table A-19 Option description of the useradd command..................................................................................A-28
Table A-20 Option description of the usermod command................................................................................A-29
Table A-21 Commands for reporting and managing system resources.............................................................A-32
Table A-22 Description of the uname options...................................................................................................A-40
Table A-23 Format of the command output......................................................................................................A-43
Issue 06 (2010-06-21) Huawei Proprietary and Confidential xix

System
Tables Administrator Guide - Solaris
Table A-24 Common network communication commands...............................................................................A-48

Table A-25 Common ftp commands.................................................................................................................A-50
Table A-26 Examples of the finger command...................................................................................................A-52
Table A-27 Description of routing flags............................................................................................................A-54
Table A-28 Description of the route commands................................................................................................A-55
xx Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
Administrator Guide - Solaris 1 Starting and Shutting Down the N2000 DMS Server
1 Starting and Shutting Down the N2000

DMS Server
About This Chapter
This describes how to securely start and shut down the N2000 DMS server.
1.1 Starting the N2000 DMS

This describes how to start the N2000 DMS server and log in to the N2000 DMS client.
1.2 Shutting Down the N2000 DMS
This describes how to quit the N2000 DMS client and shut down the N2000 DMS server.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential 1-1

System
1 Starting and Shutting Down the N2000 DMS Server Administrator Guide - Solaris
1.1 Starting the N2000 DMS

This describes how to start the N2000 DMS server and log in to the N2000 DMS client.
1.1.1 Starting the N2000 DMS Server

This describes how to start the N2000 DMS server in the Solaris OS.
1.1.2 Logging In to the N2000 DMS Client
After you log in to the N2000 DMS server using a client, you can manage the network on the
N2000 DMS client.
1.1.1 Starting the N2000 DMS Server

This describes how to start the N2000 DMS server in the Solaris OS.
Context
Normally, the Sybase and N2000 DMS services start at the boot of the Solaris OS.
Procedure
Step 1 Use the key delivered with the device to turn the rotary switch (next to the power switch) to
, as shown in Figure 1-1.
Figure 1-1 Rotary switch
NOTE
Here, the Sun Fire V890 is taken as an example. Whether the device has a rotary switch depends on the
actual situation.
Step 2 Power on the workstation and start the Solaris OS.
Step 3 After the system starts, turn the rotary switch to . In this case, the workstation will not be
forcibly powered off when you touch the power switch by accident.
NOTE
After the Solaris OS starts, the Sybase database and N2000 DMS services automatically start.
Step 4 Log in to the Solaris OS as the root user.

Step 5 Run the following commands to check whether the Sybase service is running:
# cd /opt/sybase/ASE-12_5/install
1-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
# ./showserver
The following information is displayed.

UID PID PPID C STIME TTY TIME CMD
root 2266 2264 1 7 10 ? 252:54 /opt/sybase/ASE-12_5/bin/
dataserver -d/opt/sybase/data/master.dat -e/opt/sybase
root 1058 1057 0 7 10 ? 0:00 /opt/sybase/ASE-12_5/bin/
backupserver -e/opt/sybase/ASE-12_5/install/N2000DBServer
If you find the dataserver and backupserver processes, it indicates that the Sybase service is
started. If not, run the following commands to start the Sybase service manually:
# ./startserver -f ./RUN_N2000DBServer
# ./startserver -f ./RUN_N2000DBServer_back
NOTE
N2000DBServer and N2000DBServer_back are names of the database server and database backup server.
They must be the same as the actual databases.
Step 6 Run the following commands to check whether the N2000 DMS service is running:
# ps -ef|grep mdp

root 3763 3761 0 7 11 ? 5:03 /opt/n2000/server/bin/mdp root 2068
642 0 16:34:13 pts/8 0:00 grep mdp
# ps -ef|grep EmfSysMoniDm

root 3761 1 0 7 11 ? 68:39 ./EmfSysMoniDm sybase 2098 642 0
16:35:26 pts/8 0:00 grep EmfSysMoniDm
If you find the EmfSysMoniDm and mdp processes, it indicates that the N2000 DMS service
is started. If not, run the following commands:
1. # cd /opt/n2000/server/bin
2. # sh startn2000.sh
Step 7 Right-click on the Solaris OS interface, and choose iManager N2000 > N2000 System
Monitor to log in to the N2000 System Monitor client as the admin user. The user name is
admin and the default password is admin.
NOTE
If you log in for the first time, the N2000 DMS prompts you to change the password of the admin user.
Step 8 Check the running statuses of the N2000 DMS service processes.
----End
1.1.2 Logging In to the N2000 DMS Client

After you log in to the N2000 DMS server using a client, you can manage the network on the
N2000 DMS client.

System
Prerequisite
To log in to the N2000 DMS client, note that:
l The N2000 DMS server must be in the normal state.
l The N2000 DMS client must communicate well with the N2000 DMS server.
l The IP address of the client must be in the access control list (ACL) set on the server.
l The valid user name and password of the N2000 DMS must be assigned.
Context
l You can log in to the NMS server through the client on the server host or the clients running
in the Windows OS on other computers.
l The default administrator in the N2000 DMS is admin and the default password is
admin. The system forces you to change the password at the first login. To ensure the
security of the N2000 DMS, you need to change the password in time and keep it in mind.
l If you input wrong login password for three times, your account is locked by the N2000
DMS. The admin user can unlock a common user. The N2000 DMS automatically unlocks
the locked user after 30 minutes.
Procedure
Step 1 Start the login interface of the N2000 DMS.
l On Windows, choose Start > Programes > iManager N2000 > N2000 Client, or double-
click the shortcut icon on the desktop.

l In the Solaris OS, right-click on the CDE desktop and choose iManager N2000 > N2000
Client on the shortcut menu, or double-click the shortcut icon on the desktop.
Step 2 In the Server Name drop-down list box, select the desired server.
1. You can also add a server in this way: Click ... next to Server Name. In the Server
Setting dialog box, click Add.
2. In the Add Server dialog box, set the IP address, secondary server IP address, port number,
data transmission mode, and name of the N2000 DMS server, and click OK.

System
CAUTION
l By default, the N2000 DMS adopts the data transmission mode of Security(SSL).
l The data transmission mode can be set to Common or Security(SSL). The port number
is 9800 in Common mode, while the port number is 9803 in Security(SSL) mode.
l When the client and the server are on the same host, the client can log in to the server
in Common or Security(SSL) mode if the server adopts the Security(SSL) mode; while
the client can log in to the server only in Common mode if the server adopts the
Common mode.
l When the client and the server are on different hosts, the data transmission mode of the
client must be consistent with that of the server.
l If the client is connected to a single server, you need to enter the IP address of the N2000
DMS server in the IP Address text box. You do not need to enter any information in
the Secondary Server IP Address text box.
l If the client is connected to the VCS HA system, you need to enter the system IP address
of the primary server in the IP Address text box and the system IP address of the
secondary server in the Secondary Server IP Address text box.
3. In the Server Setting dialog box, select a record, and click OK.
Step 3 Enter a valid user name and password. Click Login.
After you log in to the N2000 DMS server, the N2000 DMS client obtains the related data from
the N2000 DMS server. After the data loading, the main topological view of the N2000 DMS
client is displayed.
----End
1.2 Shutting Down the N2000 DMS

This describes how to quit the N2000 DMS client and shut down the N2000 DMS server.
1.2.1 Quitting the N2000 DMS Client

You need to quit the N2000 DMS client before shutting down the N2000 DMS server.
1.2.2 Shutting Down the N2000 DMS Server
This describes how to shut down the N2000 DMS server in the Solaris OS.
1.2.1 Quitting the N2000 DMS Client

You need to quit the N2000 DMS client before shutting down the N2000 DMS server.
Procedure
Step 1 Choose File > Exit on the menu bar.
Step 2 In the Confirm dialog box, click OK.
If certain operations on the system topology are performed but not saved, the system prompts
you to save the changes.
----End

System
1.2.2 Shutting Down the N2000 DMS Server

This describes how to shut down the N2000 DMS server in the Solaris OS.
Context
CAUTION
Do not stop the workstation with the halt command or directly unplug the power supply of the
hardware. Otherwise, the system may fail to recover.
Follow the correct procedure to shut down the N2000 DMS server safely.
Procedure
Step 1 Log in to the Solaris OS as the n2kuser user.
Step 2 Right-click on the Solaris OS interface, and choose iManager N2000 > N2000 System
Monitor to log in to the N2000 System Monitor client as the admin user.
Step 3 Choose System > Stop All NMS Service on the menu bar. In the dialog box, click OK.
Step 4 Run the following command to check whether the N2000 DMS service is stopped:
$ps -ef|grep EmfSysMoniDm

n2kuser 12366 12350 0 12:02:04 pts/14 0:00 grep EmfSysMoniDm
$ps -ef|grep mdp

n2kuser 12364 12350 0 12:01:53 pts/14 0:00 grep mdp
If you cannot find the EmfSysMoniDm or mdp process, it indicates that the N2000 DMS service
is stopped. Otherwise, run the kill -9 PID command to shut down the relevant processes.
Step 5 Run the following command to validate environment variables:
$. /n2kuser/.profile
Step 6 To shut down the Sybase service with the isql tool, run the following commands:
$ cd /opt/sybase/OCS-12_5/bin
$ ./isql -SN2000DBServer -Usa -P <sa password>
1> shutdown SYB_BACKUP
2> go
1> shutdown
2> go

System
Step 7 Run the following command to check whether the Sybase service is stopped:
$ps -ef|grep syb
sybase 1043 1024 0 04:06:02 pts/5 0:00 grep syb
If you cannot find the dataserver and backupserver process, it indicates that the N2000
DMS service is stopped. Otherwise, run the kill -9 PID command to shut down the relevant
processes.
Step 8 Run the following commands to shut down workstation:
$sync;sync;sync;sync;sync;sync
$shutdown -y -g0 -i5
Step 9 After the workstation is shut down, turn the rotary switch to .
----End

System
Administrator Guide - Solaris 2 Setting the N2000 DMS Time
2 Setting the N2000 DMS Time
About This Chapter
This describes how to set the time, Network Time Protocol (NTP) service, and daylight saving
time for the N2000 DMS server, and how to set the time and NTP service for the N2000 DMS
client.
2.1 N2000 DMS Time Synchronization Solutions

This describes the purposes, principles, and methods of N2000 DMS time synchronization
solutions.
2.2 Setting the N2000 DMS Server Time
This describes how to change the time zone, date, and time of the N2000 DMS server.
2.3 Setting the NTP Service for the N2000 DMS Server
This describes the NTP service mechanism, and the methods of setting, starting, and stopping
the NTP service on the N2000 DMS server.
2.4 Setting the Daylight Saving Time for the N2000 DMS Server
This describes the daylight saving time, rules for viewing the daylight saving time, and the
method of changing the server time zone.
2.5 Modifying the Date, Time, and Time Zone of the N2000 DMS Client
This section describes how to modify the date, time, and time zone of the N2000 DMS client.
2.6 Setting the N2000 DMS Client to the NTP Client
This section describes how to use the NTP service provided by Windows to set the N2000
DMS client to the NTP client so that the client can synchronize the time with that of the NTP
server.

System
2 Setting the N2000 DMS Time Administrator Guide - Solaris
2.1 N2000 DMS Time Synchronization Solutions

This describes the purposes, principles, and methods of N2000 DMS time synchronization
solutions.
2.1.1 Purpose of Time Synchronization
Time synchronization is to ensure the time consistency of the N2000 DMS and NEs.
2.1.2 Time Synchronization Principle
This section describes the time synchronization principle and hierarchical networking principle
of the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP).
2.1.3 Time Synchronization Plans
This section describes the plans of the N2000 DMS time synchronization.
2.1.1 Purpose of Time Synchronization

Time synchronization is to ensure the time consistency of the N2000 DMS and NEs.
The networking is complex and many NEs are located on the network. The NEs work in unified
operation and maintenance mode; therefore, the time of the NEs must be the same to ensure that
the N2000 DMS can correctly manage the alarms and performance data reported by the NEs
and avoid disorder.
Inaccurate time has the following disadvantages:
l If alarm time is inaccurate, you may misjudge the sequence of raised alarms, the interval
between alarm raising and alarm reporting, and the associations between alarms.
l When the N2000 DMS collects the statistics of performance data, inaccurate time decreases
the precision of statistics.
Therefore, a non-manual-intervened method is required for precisely adjusting the time of the
N2000 DMS and NEs at any time to keep the time consistency.
2.1.2 Time Synchronization Principle

This section describes the time synchronization principle and hierarchical networking principle
of the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP).
NTP Synchronization Principle

NTP is used for time synchronization between the distributed time server and client. NTP defines
the structure, algorithm, entity, and protocol that are used in the time synchronization. NTP is
based on the IP and UDP protocol of TCP/IP, and it can also be used by other protocol suites.
Theoretically, the accuracy of NTP can reach one nanosecond.
Figure 2-1 shows the basic principle of the NTP time synchronization.

System
Figure 2-1 NTP synchronization principle
Device A and Device B are connected through the network. Each of them has independent system
time. Now the system time of the two devices needs to be synchronized automatically. Suppose
the following conditions are met:
l The clock of Device A is set to 10:00:00 and that of Device B is set to 11:00:00 before the
system time of Device A and that of Device B are synchronized.
l Device B serves as the NTP time server, that is, Device A synchronizes its time with that
of Device B.
l A data packet takes one second for unidirectional transfer between Device A and Device
B.
If Device A needs to synchronize its time with that of Device B, the following information is
required:
l Offset: time deviation between Device A and Device B.
l Delay: time loss during the time synchronization between Device A and Device B.
When Offset and Delay are known, Device A can calculate the amount of time that needs to be
modified if Device A synchronizes its time with that of Device B. NTP specifies how to calculate
the values of Offset and Delay.
The process of time synchronization is as follows:

1. Device A sends an NTP message packet to Device B. The message packet contains the time
stamp when it is sent from Device A. The time stamp is 10:00:00am(T1).
2. When the NTP message packet reaches Device B, Device B adds its own time stamp
11:00:01am(T2) to the packet.
3. When the NTP message packet leaves Device B, Device B adds its own time stamp
4. When Device A receives the response message packet, it adds a new time stamp

System
Now Device A has enough information to calculate the two important parameters Offset and
Delay.
l Delay of the period that Device A sends the NTP message and receives the response
message: Delay = (T4-T1) - (T3-T2).
l Time offset between Device A and Device B: Offset = ((T2 - T1) + (T3 - T4))/2.
Based on this information, Device A can set its own clock to synchronize with that of Device
B.
NTP Hierarchical Networking Principle

According to the principle and purpose of the time synchronization mechanism, time consistency
is better when the clock sources are fewer. Due to the huge and complex network, however, it
is not practical to connect all the devices that need to be synchronized to the same time server.
Therefore, the hierarchical structure is used in the NTP model.
Theoretically, the time synchronization network is divided into 16 (from 0 to 15) or more levels
according to accuracy and importance. In practice, the levels are less than six.
The devices of the 0 level are in special position. They are the reference time sources of the
synchronization network. They are located on the top of the network and use the Global
Positioning System (GPS), that is, the UTC time codes broadcast by the GPS.
The devices in a subnetwork plays multiple roles. For example, a device of the second level
serves as the client for the devices of the first level and server for the devices of the third level.
Figure 2-2 NTP hierarchical networking
As shown in Figure 2-2, the servers in the NTP hierarchical networking can be configured as
follows:
l NTP servers of the top level: NTP servers of the 0 level that provide time synchronization
service for the next level.
l NTP servers of the medium level: NTP servers of the levels such as the first and second
levels that obtain time from the NTP servers of the upper level and provide the time
synchronization service for the servers of the lower level.
l NTP clients: Obtain time from the NTP servers of the upper level but do not provide the
time synchronization service.
A host can obtain time information from multiple NTP servers and an NTP server can provide
time information for multiple hosts. The hosts of the same level can provide time information
for each other. NTP can provide up to 15 levels of clients.

System
NOTE
NTP uses the port number 123 and uses UDP for communication. Therefore, ensure that the IP links are
normal between nodes.
Comparison Between SNTP and NTP

SNTP is a simplified policy of the NTP server and client. SNTP is the same as NTP in terms of
time synchronization process, but the following control functions of SNTP are not as powerful
as those of NTP.
l Error processing function of time synchronization
l Multi-server filtering function
l Selection of multiple time sources (obtaining the most accurate time source among the
connected NTP servers by algorithm-based comparison and analysis)
2.1.3 Time Synchronization Plans

This section describes the plans of the N2000 DMS time synchronization.
You can configure the OS to synchronize the N2000 DMS server time, N2000 DMS client time,
and NE time. The following are the two time synchronization plans:
l Time synchronization on the intermediate level NTP server
The N2000 DMS server is set to the intermediate level NTP server. The N2000 DMS client
and all NEs are set to NTP or SNTP clients. The N2000 DMS server obtains the time
synchronization information from the external NTP time server. The N2000 DMS client
and all NEs obtain the time synchronization information from the N2000 DMS server.
l Time synchronization on the NTP client
The N2000 DMS server, N2000 DMS client, and all NEs are set to NTP clients to receive
the time synchronization information from the external NTP time server.
2.2 Setting the N2000 DMS Server Time

This describes how to change the time zone, date, and time of the N2000 DMS server.
2.2.1 Modifying the N2000 DMS Server Time Zone
This section describes how to modify the time zone of the N2000 DMS server.
2.2.2 Modifying the Time and Date of the N2000 DMS Server
This section describes how to modify the time and date of the N2000 DMS server.
2.2.1 Modifying the N2000 DMS Server Time Zone

This section describes how to modify the time zone of the N2000 DMS server.
Prerequisite
The N2000 DMS and database services must be stoped before you modify the server time zone.
Context
The NE performance data and alarm data cannot be retrieved when the N2000 DMS service is
stopped.

System
Procedure
Step 1 Run the N2000 DMS environment variables:
# cd $N2000ROOT
# . ./svc_profile.sh
Step 2 Run the Sybase database environment variables:

# Sybase_path
# . ./SYBASE.sh
The variable Sybase_path indicates the installation path of the Sybase database.
Step 3 Log in to the System Monitor Client as admin.
Step 4 Choose System > Stop All NMS Services. In the displayed Confirm dialog box, click OK.
The In Process... dialog box is displayed. Click OK in the Information dialog box, the System
Monitor Client exits.
Step 5 Run the following command to stop the Sybase database:
# isql -SN2000DBServer -Usa -P<sa password>
2> go
1> shutdown
2> go
Step 6 Run the following command to check the OS time zone:
# echo $TZ
Step 7 If the current time zone is incorrect, change the value of TZ in /etc/TIMEZONE to your local
time zone.
For example, set the value of TZ to PRC.
NOTE
In /usr/share/lib/zoneinfo/src directory, you can find all original data on different time zones.
Step 8 Run the following command to restart the server:

# sync;sync;sync;sync;sync;sync;
# shutdown -i6 -g0 -y
The Sybase database and the N2000 DMS service start automatically after the OS is restarted.
----End
2.2.2 Modifying the Time and Date of the N2000 DMS Server
This section describes how to modify the time and date of the N2000 DMS server.
Prerequisite
Before modifying the server time and data, the N2000 DMS service and database service must
be stopped.

System
Context
l The server time cannot be modified when the N2000 DMS service is running. Otherwise,
the system timer is affected. Then the tempdb in Sybase cannot be cleared. When the
tempdb is full, the Sybase database cannot work and the N2000 DMS service cannot run.
l The NE performance data and alarm data cannot be retrieved when the N2000 DMS service
is stopped.
l The system date must be a value between 1971 to 2037. Otherwise, exceptions occur in the
N2000 DMS.
l In the case that the N2000 DMS has been running for some time and some performance
data is generated, after the system time is modified, the performance data displayed in the
performance graph becomes uncontinuous.
Procedure
Step 2 Choose System > Stop All NMS Services. In the displayed Confirm dialog box, click OK.
Monitor Client exits.
Step 3 Run the following command to stop the Sybase database:
2> go
1> shutdown
2> go
Step 4 Run the date command to set the system date and time.
For example, to set the system date and time to 2005-11-17 16:30:43, run the following
command:
# date 111716302005.43
Mon Nov 17 16:30:43 CST 2005
Step 5 Run the following commands to restart the server:

The Sybase database and the N2000 DMS service start automatically after the system is restarted.
----End
2.3 Setting the NTP Service for the N2000 DMS Server
This describes the NTP service mechanism, and the methods of setting, starting, and stopping
the NTP service on the N2000 DMS server.
2.3.1 NTP Service Overview
This describes the NTP service mechanism.

System
2.3.2 Checking the N2000 DMS Server Time Configuration

Before configuring the NTP service, ensure that the time zone, date, and time of the NTP server
are correct.
2.3.3 Setting the N2000 DMS Server to the Secondary Time Server
This task is performed to set the N2000 DMS server to the secondary NTP server. The secondary
NTP server synchronizes the time with that of the upper-level server and provides a standard
time source for a lower-level server.
2.3.4 Setting the N2000 DMS Server to the NTP Client
This section describes how to set the N2000 DMS server to the NTP client.
2.3.5 Starting the NTP Service on the N2000 DMS Server
This task is performed to start the NTP service on the N2000 DMS server to synchronize the
time.
2.3.6 Stopping the NTP Service on the N2000 DMS Server
This section describes how to stop the NTP service on the N2000 DMS server.
2.3.7 Querying the Status of the NTP Service
Solaris allows you to run the ntpq -p and ntptrace commands to check whether the NTP
synchronization status is normal.
2.3.1 NTP Service Overview

This describes the NTP service mechanism.
The Network Time Protocol (NTP) specifies a time synchronization mechanism. It synchronizes
the time between the distributed time server and the client. The theoretical precision reaches
nanoseconds.
Network time is synchronized through NTP or Simple Network Time Protocol (SNTP). NTP
and SNTP are compatible. The difference is that NTP provides encryption for messages for
security purpose. The basic principle for the plan is that the NTP or SNTP server sends the time
information, and the NTP or SNTP client receives the information, and adjusts the local time.
Based on the two protocols, all the nodes (including all NEs and the N2000 DMS) for
synchronization should be set to NTP or SNTP clients. The nodes (such as the N2000 DMS) in
the center of the network serve as NTP or SNTP servers to provide the time source.
Figure 2-3 NTP synchronization network
Level 0
NTP Server
Level 1 Level 1 Level 1

NTP Server NTP Server NTP Server
Level 2 Level 2
NTP Client
NTP Server NTP Server
NTP Client

System
In the network shown in Figure 2-3, there are three kinds of devices:
l NTP server at the highest level: Level 0 NTP server, providing the time synchronization
service to the servers at the next level.
l NTP server at intermediate levels: The NTP servers at level 1 and level 2 obtain the time
from the servers at the higher levels, and provide time service to the servers at the next
levels.
l NTP client: It only obtains the time, and does not provide time service.
2.3.2 Checking the N2000 DMS Server Time Configuration

Before configuring the NTP service, ensure that the time zone, date, and time of the NTP server
are correct.
Procedure
Step 1 Run the following command to check the OS time zone:
# echo $TZ
Step 2 Run the following command to check the OS date and time:
# date
----End
Postrequisite
The following errors may occur on the server:
l The time zone is incorrect.
l The date is incorrect.
l The server time is two minutes earlier or later than the local time.
If any of the preceding errors occur, perform the following steps to avoid system exceptions.
1. Stop all the time-based service (Database service and N2000 DMS service).
2. Correct the time zone, date, and time.
NOTE
You can configure the NTP service only after you complete the preceding steps. All the stopped time-
based applications need to be restarted after the configuration.
2.3.3 Setting the N2000 DMS Server to the Secondary Time Server
This task is performed to set the N2000 DMS server to the secondary NTP server. The secondary
NTP server synchronizes the time with that of the upper-level server and provides a standard
time source for a lower-level server.
Prerequisite
The time zone, date, and time of the N2000 DMS server are set correctly.

System
Procedure
Step 1 Log in to the N2000 DMS server as root.
Step 2 Run the following commands:
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
# vi /etc/inet/ntp.conf
Step 3 Modify all "XType" to "1".
Step 4 Add "server XXX.XXX.XXX.XXX" before "server 127.127.1.0 prefer" to specify the IP address
of the upper-level NTP server. Each line maps to an NTP server.
NOTE
"XXX.XXX.XXX.XXX" represents the IP address of the upper-level NTP server. If there are multiple
upper-level NTP servers, write as many rows as necessary. For example:
server XXX.XXX.XXX.XXX prefer
server XXX.XXX.XXX.XXX prefer
Step 5 Delete "stratum 0" from "fudge 127.127.1.0 stratum 0".
Step 6 Add "#" before "broadcast 224.0.1.1 ttl 4".
Step 7 Save the /etc/inet/ntp.conf file and exit from the vi editor.
----End
2.3.4 Setting the N2000 DMS Server to the NTP Client

This section describes how to set the N2000 DMS server to the NTP client.
Context
The method of setting the N2000 DMS client as the NTP client is similar to that of setting the
N2000 DMS server as the NTP client.
Procedure
Step 1 Log in to the N2000 DMS server as the root.
Step 2 Run the following commands:
# cp /etc/inet/ntp.client /etc/inet/ntp.conf
# vi /etc/inet/ntp.conf
Step 3 Add a line to file: server XXX.XXX.XXX.XXX.

NOTE
XXX.XXX.XXX.XXX represents the IP address of the upper-level NTP server, such as server 10.10.10.100.
Step 4 Disable the multicast client mode. Put a comment (# character without quotes) in front of
multicastclient 224.0.1.1. For example, # multicastclient 224.0.1.1.
Step 5 Save the /etc/inet/ntp.conf file and exit from the vi editor.
----End

System
2.3.5 Starting the NTP Service on the N2000 DMS Server

This task is performed to start the NTP service on the N2000 DMS server to synchronize the
time.
Context
l The NTP boot script is in /etc/rc2.d/. After you start Solaris, the NTP service is started
automatically. Therefore, you need not add the NTP boot script manually.
l Check whether the current time zone, date, and time of the N2000 DMS server are correct
before you start the NTP service. If they are incorrect, correct them.
l After you start the NTP service, the NTP client starts to synchronize the time with that of
the NTP server and slowly adjusts the time deviation. As the adjustment is in the millisecond
level, it does not affect the running of the N2000 DMS server.
Procedure
Step 2 Check if the time zone, date, and time of the server are correct. If not, adjust them manually.
For details, see section 2.2.2 Modifying the Time and Date of the N2000 DMS Server.
Step 3 Run the following command to check whether the NTP service is started:
# ps -ef | grep ntp
The following information is displayed:

root 25972 25945 0 15:45:06 pts/5 0:00 grep ntp
NOTE
If the screen output does not contain /usr/lib/inet/xntpd, it indicates that the NTP service is not
started.
Step 4 If the NTP service process is running, stop it first by running the following command:
l In solaris 10
# svcadm disable svc:/network/ntp:default
l In solaris 8
# /etc/rc2.d/S74xntpd stop
Step 5 Run the following command to start the NTP service:

l In solaris 10
# svcadm enable svc:/network/ntp:default
l In solaris 8
# /etc/rc2.d/S74xntpd start
----End
2.3.6 Stopping the NTP Service on the N2000 DMS Server

This section describes how to stop the NTP service on the N2000 DMS server.

System
Context
After the NTP service is stopped, the N2000 DMS server fails to synchronize the time with that
of the NTP server. This may result in a time deviation.
Procedure
Step 2 Stop the NTP service.

l In Solaris 10, run the following command:
# svcadm disable svc:/network/ntp:default
NOTE
The command can be run only once. This means that the NTP service is not enabled each time the
system is restarted.
l In Solaris 8, run the following command:
# /etc/rc2.d/S74xntpd stop
Step 3 Check whether the NTP service is stopped and run the following command:
# ps -ef | grep ntp
If /usr/lib/inet/xntpd is not displayed, it indicates that the NTP service is stopped.
----End
2.3.7 Querying the Status of the NTP Service

Solaris allows you to run the ntpq -p and ntptrace commands to check whether the NTP
synchronization status is normal.
Context
l The remote field in the return message of the ntpq -p command is the IP address of the
reference time source. It indicates the status of the reference time source.
l The ntptrace command traces the entire NTP synchronization link from the local machine
to the NTP server at the highest level. For details, run the ntptrace -v command.
l When the NTP server and NTP client are started, it takes five minutes for detection. During
the detection, when the ntpq -p command is run, the remote time source is not displayed
with *. When the ntptrace command is run, Timeout or Not Synchronized is
displayed. Wait for five minutes, and then run the ntpq -p command or ntptrace command.
Procedure
Step 1 In the command line interface, run the ntpq -p command to check the NTP clock source.
Step 2 In the command line interface, run the ntptrace command to check the NTP synchronization
link.
----End

System
Result
l If the N2000 DMS is the NTP server at the intermediate level, the return result is as follows:
In the return result obtained after the ntpq -p command is run, *10.161.94.212
indicates that the IP address of the NTP server is 10.161.94.212 at level 1. The asterisk
(*) indicates that the status is normal.
The return result obtained after the ntptrace command is run indicates that the server
is at level 2, and the IP address of the server at the upper level is 10.161.94.212 at level
1.
# ntpq -p remote refid st t when
poll reach delay offset jitter
==============================================================================
== *10.161.94.212 .LCL. 1 u 165 512
377 0.406 61.294 0.111 +local(0) Local(0)
3 1 29 64 377 0.000
0.000 0.000 # # ntptrace localhost:stratum 1, offset 0.060665,
sycn distance 0.01015, refid 'LCL'
l If the N2000 DMS is the NTP client at the intermediate level, the return result is as follows:
# ntpq -p remote refid st t
when poll reach delay offset disp
==============================================================================
= *10.161.94.214 10.161.94.212 2 u 58
64 377 0.37 0.217 0.05 # # ntptrace localhost:stratum
3, offset 0.000035, sycn distance 0.08855 10.161.94.214: stratum
2, offset 0.000224, synch distance 0.07860 10.161.94.212: stratum
1, offset 0.060569, synch distance 0.01036, refid 'LCL'
In the return result obtained after the ntpq -p command is run, *10.161.94.214
indicates that the IP address of the NTP server is 10.161.94.214 at level 2. The asterisk
(*) indicates that the status is normal.
The return result obtained after the ntptrace command is run indicates that the server
is at level 3, and the IP address of the server at the upper level is 10.161.94.212 at level
1.
2.4 Setting the Daylight Saving Time for the N2000 DMS
Server
This describes the daylight saving time, rules for viewing the daylight saving time, and the
method of changing the server time zone.
2.4.1 Daylight Saving Time Overview

This describes the concept of daylight saving time and influences on the N2000 DMS.
2.4.2 Viewing the Daylight Saving Time Rule of a Time Zone
This describes how to view the daylight saving time rule of a time zone. Before setting the
daylight saving time, you need to query the daylight saving time rule for the specified time zone
through the time zone code. Thus, the daylight saving time rule of the time zone is the same as
the actual rule.
2.4.3 Changing the Time Zone of the N2000 DMS Server
This describes how to change the time zone of the N2000 DMS server. To make sure that the
time zone configuration, NTP service, and daylight saving time are correct, you need to change
the time zone of the N2000 DMS server.

System
2.4.1 Daylight Saving Time Overview

This describes the concept of daylight saving time and influences on the N2000 DMS.
Concept of Daylight Saving Time

Daylight saving time is one hour earlier than the standard time. For example, in the daylight
saving time period, the 10 a.m. in American eastern standard time is 11 a.m. in American eastern
daylight saving time.
Influences on the N2000 DMS

l When the daylight saving time starts, the local time of the OS automatically adds one hour.
This does not affect the system clock or the N2000 DMS timer. The N2000 DMS log uses
the local time. Thus, the log of the added one hour is missed.
l When the daylight saving time ends, the local time of the OS automatically subtracts one
hour. This does not affect the system clock and the time storage and exchange, but affects
the display of time. Certain N2000 DMS modules may produce files, and those files are
identified as time stamp. When daylight saving time ends, the latest files may overwrite
the earlier files.
NOTE
l The local time is the displayed time on the computer. The local time changes according to different
time zones.
l The system clock specifies the Greenwich Mean Time (GMT). The NTP synchronization uses the GMT
and does not affect the local time. Thus, the daylight saving time does not affect the NTP service.
2.4.2 Viewing the Daylight Saving Time Rule of a Time Zone

This describes how to view the daylight saving time rule of a time zone. Before setting the
daylight saving time, you need to query the daylight saving time rule for the specified time zone
through the time zone code. Thus, the daylight saving time rule of the time zone is the same as
the actual rule.
Context
In the Solaris OS, two types of time zone formats exist: the GMT and time zone code. The GMT
format contains only the time difference rather than the daylight saving time rule. The time zone
code format contains both the time difference and daylight saving time rule (depending on the
specific time zone).
For countries or regions that do not use the daylight saving time, the GMT format is
recommended. For countries or regions use the daylight saving time, the time zone code must
be adopted. Otherwise, the automatic change of the daylight saving time is not supported by the
OS.
When the daylight saving time rule of a certain time zone changes, Sun Microsystems Inc may
release a patch for the time zone code. You can install the patch to obtain the latest time zone
code and daylight saving time rule.
Procedure

System
Step 2 Check the name of the local time zone.
Step 3 Run the following command to view the daylight saving time rule of the time zone in the specified
year:
# zdump -vtime zone name | grepspecified year
The format of the returned information is as follows.
Time zone name UTC time = local time isdst=0/1
The meanings of the returned information are as follows:

l Universal Time Coordinated (UTC) is the GMT.
l In the local time, ST stands for the standard time, DT stands for the daylight saving time.
l isdst=0 indicates that it is not the daylight saving time; isdst=1 indicates that it is the daylight
saving time.
l If it is not the daylight saving time, a line of information is displayed. If it is the daylight
saving time, at least four lines of information are displayed to describe the daylight saving
time rule.
NOTE
l If the command does not contain | grepspecific year, the daylight saving rules for all years are displayed.
l The daylight saving time in a time zone may start and end on the fixed dates, or starts from a day in a
certain week of a certain month and ends on a day in a certain week of a certain month. That is, the
week is fixed but the date is not. For example, in the Alaska state of the USA, the daylight saving time
starts on the second Sunday in March, and ends on the first Monday in November.
l Run zdump consecutively to view the daylight saving time of the last year, this year, and next year.
Then, you can know the universal change rule of the daylight saving time.
----End
Example
View the time zone rule of Alaska, USA.
# zdump -v US/Alaska | grep 2007

US/Alaska Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST isdst=0
US/Alaska Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT isdst=1
US/Alaska Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT isdst=1
US/Alaska Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 AKST isdst=0
From the display information, you can know that Alaska has daylight saving time. Currently, it
is not in the daylight saving time because isdst=0.
From the first and second lines, you can know that the time changes from Mar 11 02:00:00
2007 to Mar 11 03:00:00 2007, and the daylight saving time starts.
From the third and fourth lines, you can know that the time changes from Nov 4 02:00:00
2007 to Nov 4 01:00:00, and the daylight saving time ends.
2.4.3 Changing the Time Zone of the N2000 DMS Server

This describes how to change the time zone of the N2000 DMS server. To make sure that the
time zone configuration, NTP service, and daylight saving time are correct, you need to change
the time zone of the N2000 DMS server.

System
Context
l The NE performance data and alarm data cannot be retrieved when the N2000 DMS service
is stopped.
l If you need to change the time zone and time at the same time, you must change the time
zone first.
l The GMT format does not support the daylight saving time. The time zone code format
supports the daylight saving time.
Procedure
Step 2 Run the following commands to stop the N2000 DMS service:
# cd /opt/n2000/server/bin
# ./stopn2000.sh
Step 3 Run the following commands to stop the Sybase service:

2> go
1> shutdown
2> go
Step 4 Run the following command to check the time zone of the OS.
# echo $TZ
Step 5 If the current time zone is incorrect, change the value of TZ to the local time zone (DST) in /
etc/TIMEZONE.
For example, set the value of TZ to "PRC".
NOTE
You can find the time zone information in /usr/share/lib/zoneinfo/src. If you cannot find the time zone code
that matches your locality, you can customize a time zone file. For details, see 2.4.2 Viewing the Daylight
Saving Time Rule of a Time Zone.
Step 6 Restart the N2000 DMS server with the following commands:
# sync;sync;sync;sync;sync;sync
# shutdown -y -g0 -i6
After the computer is restarted, the Sybase database and N2000 DMS services automatically
restart.
----End
2.5 Modifying the Date, Time, and Time Zone of the N2000
DMS Client
This section describes how to modify the date, time, and time zone of the N2000 DMS client.

System
Context
l Modifying the time of the client is to modify the time of the PC operating system. This
section takes Windows 2000 Professional as an example.
l The system date must be a value between year 1971 to 2037. Otherwise, exceptions may
occur in the N2000 DMS.
Procedure
Step 1 Open Date/Time in the Control Panel.
Step 2 In the Date&Time window, modify the items.
Item Step
Time zone To modify the time zone, click the Time Zone tab. In the drop-down list box under
the tab, click the drop-down arrow, and then click the time zone to which the PC
operating system belongs.
Hour To modify the hour, double-click the hour, and then increase or decrease the value
in the spin box.
Minute To modify the minute, double-click the minute, and then increase or decrease the
value in the spin box.
Second To modify the second, double-click the second, and then increase or decrease the
value in the spin box.
----End
2.6 Setting the N2000 DMS Client to the NTP Client

This section describes how to use the NTP service provided by Windows to set the N2000
DMS client to the NTP client so that the client can synchronize the time with that of the NTP
server.
Prerequisite
l The Windows operating system works properly.
l The clock source of the NTP server works properly.
Context
The configuration procedure is applicable to the Windows 2000 Professional or Windows XP
Professional operating system.
Procedure
Step 1 To set the N2000 DMS client to the NTP client, do as follows:
Open the registry. Under the key HKEY_LOCAL_MACHINE\SYSTEM

\CurrentControlSet\Services\W32Time\Parameters, modify the value of LocalNTP to 0.

System
NOTE
l The default value of LocalNTP is 0.

l In Windows XP, if the registry does not contain LocalNTP, it indicates that the value of LocalNTP
can be ignored and you need not modify the value.
Step 2 Specify the NTP clock source by running the following command:
c:\> net time /setsntp:<NTP Server IP address>
NOTE
The execution result of net time is saved in Windows registry. Therefore, the parameters configured using
net time still works after you restart Windows.
Step 3 To cancel your settings, run the following command:

c:\> net time /setsntp
Step 4 View the specified NTP server of the current machine by running the following command:
c:\> net time /querysntp
Step 5 Check the status of NTP by running the following command:
c:\> tasklist /svc
Check whether the svchost.exe process contains the W32Time service. If the process contains
the W32Time service, it indicates that the NTP service is running.
NOTE
To start the W32Time service in Windows, run the net start w32time command. To stop the W32Time
service in Windows, run the net stop w32time command.
----End

System
Administrator Guide - Solaris 3 Setting N2000 DMS Server Parameters
3 Setting N2000 DMS Server Parameters
About This Chapter
This describes how to set N2000 DMS server parameters, including environment variables,
server host names, IP addresses, and routes.
3.1 Setting N2000 DMS Environment Variables

The N2000 DMS has some environment variables related to operation. After setting the
environment variables, you only need to enter corresponding commands at the console, and then
the N2000 DMS is started. You can also run some commands of the N2000 DMS at the console.
3.2 Changing the Host Name of the N2000 DMS Server
When the host name of the N2000 DMS server needs to be changed, for example, when the host
name of the N2000 DMS server conflicts with other host names or the host name if illegal, you
need to use IP tools to change the host name.
3.3 Changing the IP Address of the N2000 DMS Server
When the IP address of the N2000 DMS server need be changed due to such causes as network
changes, you can use IP tools to change the IP address.
3.4 Setting Routes on the N2000 DMS Server
This task is performed to add or delete routes from the current network to several destination
networks.
3.5 Setting the Login Mode of the N2000 DMS
When you perform certain maintenance tasks, to avoid the impacts on other users, you can set
the login mode of the N2000 DMS to single-user mode. In this mode, you can maintain the
N2000 DMS exclusively.

System
3 Setting N2000 DMS Server Parameters Administrator Guide - Solaris
3.1 Setting N2000 DMS Environment Variables

The N2000 DMS has some environment variables related to operation. After setting the
environment variables, you only need to enter corresponding commands at the console, and then
the N2000 DMS is started. You can also run some commands of the N2000 DMS at the console.
Context
In Solaris, the N2000 DMS environment variables are recorded in the .profile file of the
n2kuser user.
Therefore, there are two conditions:
l Log in to Solaris as n2kuser.
The N2000 DMS environment variables are set automatically and you do not need to set
them manually.
NOTE
The n2kuser user is created automatically only when the N2000 DMS is installed in Solaris.
l Log in to Solaris as a user other than n2kuser.
You need to run the .profile file (a hidden file) under the n2kuser folder to set environment
variables.
Procedure
Step 1 Go to the n2kuser folder:
# cd /n2kuser
Step 2 Run the .profile file under the n2kuser folder:
# . ./.profile
NOTE
l According to the N2000 DMS maintenance policy in Solaris, you are recommended to log in to
Solaris as n2kuser, and then the N2000 DMS is started automatically. The n2kuser user can also
switch to the root user when necessary.
l Only the root user can start the N2000 DMS service manually.
l After setting environment variables, the root user can run startn2000.sh on the console to start the
N2000 DMS. If the environment variables are not set, run startn2000.sh under $N2000ROOT/server/
bin to start the N2000 DMS.
----End
3.2 Changing the Host Name of the N2000 DMS Server

When the host name of the N2000 DMS server needs to be changed, for example, when the host
name of the N2000 DMS server conflicts with other host names or the host name if illegal, you
need to use IP tools to change the host name.
Prerequisite
Before modifying the host name, stop the N2000 DMS service and the Sybase service.

System
Context
CAUTION
l The host name cannot be modified while the N2000 DMS service is running, otherwise the
N2000 DMS service exit abnormally.
l When the N2000 DMS service is stopped, the performance and alarm data of the NEs may
be lost.
Procedure
Step 2 Choose System > Stop All NMS Service, in the Confirm dialog box, click OK.
The In Process... dialog box is displayed. After the N2000 DMS service is stopped, the
Information dialog box is displayed. Click OK. The System Monitor Client exits.
Step 3 Log in to the N2000 DMS server as root. Run the following commands to stop the Sybase
service.
# . /n2kuser/.profile
2> go
1> shutdown
2> go
Step 4 Run IP tools to modify the host name in Solaris and the Sybase.
# ./iptools -H <host-name>
Step 5 Run the following commands to restart the N2000 DMS server.
After the operating system is restarted, the Sybase and N2000 DMS services are started
automatically.
----End
3.3 Changing the IP Address of the N2000 DMS Server

When the IP address of the N2000 DMS server need be changed due to such causes as network
changes, you can use IP tools to change the IP address.

System
Prerequisite
Before modifying the IP address, stop the N2000 DMS service and the Sybase service.
Context
CAUTION
l The IP address cannot be modified while the N2000 DMS service is running, otherwise the
N2000 DMS service exit abnormally.
l When the N2000 DMS service is stopped, the performance and alarm data of the NEs may
be lost.
Procedure
Step 2 Choose System > Stop All NMS Service, in the Confirm dialog box, click OK.
Monitor Client exit.
Step 3 Log in to the N2000 DMS server as root. Run the following commands to stop the Sybase
service.
1>shutdown SYB_BACKUP
2>go
1>shutdown
2>go
Step 4 Run the following command to view the current IP address settings of the N2000 DMS server.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843 mtu 1500 index 2
inet 10.10.10.8 netmask ffffff00 broadcast 10.161.45.255
ether 0:3:ba:12:f9:12
Step 5 Run IP tools to change the IP address settings in Solaris and Sybase.
iptools {-n interface-name -i ip-address -m subnet-mask -G default -gateway -H host-name
-d }
Step 6 Run the following commands to restart the N2000 DMS server.

System
After the operating system is restarted, the Sybase and N2000 DMS services are restarted
automatically.
----End
Example
For example, if you want to change the IP address of Solaris to 10.10.10.10, the host name to
host, default gateway to 10.10.10.1, and the IP addresses of all the Sybase servers to 10.10.10.10,
run the following commands:
# iptools -n hme0 -i 10.10.10.10 -m 255.255.255.0 -G 10.10.10.1 -H host -d
3.4 Setting Routes on the N2000 DMS Server

This task is performed to add or delete routes from the current network to several destination
networks.
Procedure
Step 1 Log in the N2000 DMS server as root.
Step 2 To add, delete, view, or automatically add the N2000 DMS server route:
Operation Command
Adding a route # route add Destination address Next hop

Subnet mask of the destination network
l Destination address: a network address or a
PC address
l Next hop: forward the IP address of the route.
l Mask: the number of digit 1 in the subnet
mask is binary. For example, 24 means
255.255.255.0.
Deleting a route # route delete Destination address Next hop

Viewing a route # netstat -rv
The operating system automatically adds Create the file /etc/rc2.d/S97route

route records when being restarted.
# vi /etc/rc2.d/S97route
Write one or more route entries to the file:

router add Destination address Next hop
----End

System
3.5 Setting the Login Mode of the N2000 DMS

Prerequisite
You must be the NMS user admin.
Context
l There are two login modes: single-user mode and multi-user mode. In single-user mode,
only the admin user can log in to the N2000 DMS.
l In multiuser mode, the admin user and other users can log in to the N2000 DMS at the
same time. When the mode is changed to single-user mode, other users are forced to log
out of the N2000 DMS, and only the admin user can log in.
Procedure
Step 1 Choose System > NMS Security Settings > Single User Mode.
----End

System
Administrator Guide - Solaris 4 Managing the N2000 DMS Client
4 Managing the N2000 DMS Client
About This Chapter
This describes how to set the login modes, set the maximum number of online users, and monitor
the login statuses of clients.
4.1 Changing to Another N2000 DMS Server

This describes how to quickly log in to another server without quitting the current client. Through
this function, you do not need to enter the user name and password when you log in to the selected
server.
4.2 Setting the Login Mode on the N2000 DMS Client
The login modes of the N2000 DMS include the single-user mode and the multi-user mode. In
single-user mode, the admin user and multiple admin users can log in to the N2000 DMS. In
multi-user mode, the admin user and other users can log in to the N2000 DMS at the same time.
When the multi-user mode is changed to the single-user mode, all users except the admin user
are forced to quit.
4.3 Setting Maximum Online Users on the N2000 DMS Client
This describes how to set the maximum number of online users on the N2000 DMS client.
Through this function, you can monitor and manage online users.
4.4 Monitoring Login Statuses of N2000 DMS Users
This describes how to monitor login statuses and locking statuses of N2000 DMS users.

System
4 Managing the N2000 DMS Client Administrator Guide - Solaris
4.1 Changing to Another N2000 DMS Server

This describes how to quickly log in to another server without quitting the current client. Through
this function, you do not need to enter the user name and password when you log in to the selected
server.
Prerequisite
l The IP address of the local computer is in the ACL of the server to be logged in.
l The server to be switched to is added in Server Setting.
Procedure
Step 1 Log in to the N2000 DMS client.
Step 2 Choose File > Change Login Server on the main menu.
Step 3 In the Change Login Server dialog box, select the server to be logged in, and then click OK.
NOTE
If the previous user name and password are valid for the changed server, you can automatically log in to
the server; otherwise, the system prompts you that the user name and password are invalid and the login
dialog box is displayed.
----End
4.2 Setting the Login Mode on the N2000 DMS Client

The login modes of the N2000 DMS include the single-user mode and the multi-user mode. In
single-user mode, the admin user and multiple admin users can log in to the N2000 DMS. In
multi-user mode, the admin user and other users can log in to the N2000 DMS at the same time.
When the multi-user mode is changed to the single-user mode, all users except the admin user
are forced to quit.
Context
l After the N2000 DMS is installed, the default login mode is the multi-user mode.
l It is dangerous to change the login mode to the single-user mode, because the other users
are forced to log out and only the admin user can log in.
l Only the admin user can change the login mode.
Procedure
Step 1 Log in to the N2000 DMS client as the admin user.
Step 2 Choose System > NMS Security Settings > Single User Mode on the menu bar.
----End

System
Administrator Guide - Solaris 4 Managing the N2000 DMS Client
4.3 Setting Maximum Online Users on the N2000 DMS

Client
This describes how to set the maximum number of online users on the N2000 DMS client.
Through this function, you can monitor and manage online users.
Prerequisite
The login user has the rights of the security operator or higher level rights than the security
operator.
Procedure
Step 2 Choose System > NMS User Management on the main menu.
Step 3 In Security Object, select the user to be set with the maximum number of online users or the
user group to be set with the maximum number of sessions.
Step 4 On the General tab, select Yes for Unrestricted, and then set the value of Maximum number
of online users.
Step 5 Click Apply.
----End
4.4 Monitoring Login Statuses of N2000 DMS Users

This describes how to monitor login statuses and locking statuses of N2000 DMS users.
Prerequisite
The login user has the rights of the security watcher or higher level rights than the security
watcher.
Procedure
Step 3 In the Security Object navigation tree, select Users.
All login users are displayed in the right pane. You can also view whether an account is locked
in Account Lock Status.
Step 4 Optional: If Account Lock Status of a certain user is Locked, do as follows to unlock the user:
1. Select the locked user.
2. Right-click the user and select Unlock.

System
4 Managing the N2000 DMS Client Administrator Guide - Solaris
The Account Lock Status value of the user changes to Unlocked. The user can log in
again.
----End

System
Administrator Guide - Solaris 5 N2000 DMS Security Management
5 N2000 DMS Security Management
About This Chapter
This describes the policies of the N2000 DMS security management and the methods of setting
the N2000 DMS data transmission security.
5.1 Policies of the N2000 DMS Security Management

This describes the N2000 DMS security management. Through the security management, you
can perform authority and domain-based management, and monitor and manage the login N2000
DMS users in real time. Thus, the network and data security can be ensured, and the invalid
logins or wrong operations will not affect the network.
5.2 Setting Communication Security Between the Server and the Client
When you set the communication mode between the server and the client, you can use the
Security Socket Layer (SSL) mode to ensure that the communication is secure.

System
5 N2000 DMS Security Management Administrator Guide - Solaris
5.1 Policies of the N2000 DMS Security Management

This describes the N2000 DMS security management. Through the security management, you
can perform authority and domain-based management, and monitor and manage the login N2000
DMS users in real time. Thus, the network and data security can be ensured, and the invalid
logins or wrong operations will not affect the network.
Policies of N2000 DMS security management include the following aspects:
l User management
The user management includes user policies and password policies, such as the minimum
length of the user name, automatic lock of the user, complexity of the password, and
requirement of changing the password of the first login.
l Login management
The login management includes login modes, system ACLs, and user ACLs.
l Log management
The log management includes operation logs and system running logs, such as, by
monitoring operation logs in real time, the administrator can force the user performing
unauthorized operations to log out.
l Authority management
The authority management includes operation rights and management rights. By assigning
the least operation rights and management rights to users or user groups, you can ensure
that the N2000 DMS runs safely.
NOTE
If you use the RADIUS server to authenticate the NMS users, the security policy of the NMS is different
in the following aspects:
l An NMS user is added on the RADIUS server.
l Operation Rights and Managed Domain of an NMS user are the unions of Operation Rights and
Managed Domain of all user groups that the NMS user belongs to.
5.1.1 Policies of Security Protocols

This describes the security protocols supported by the N2000 DMS, including SNMP, SSH, and
SSL.
5.1.2 OS Security Policies
OS security is the basis for the secure running of the N2000 DMS. You need to maintain the OS
of the N2000 DMS based on the OS security policies.
5.1.3 User Security Policies
All the operations on the N2000 DMS are performed by the N2000 DMS users. Therefore, user
security is very important to N2000 DMS security. You need to manage the N2000 DMS users
based on the user management policies.
5.1.4 Policies of the N2000 DMS Log Management
This describes the policies of the N2000 DMS log management, including querying and dumping
logs.
5.1.5 Database Security
The data related to the N2000 DMS are stored in databases. Therefore, database security is very
important to the running of the N2000 DMS. You need to maintain the databases based on the
database security policies.

System
5.1.1 Policies of Security Protocols

This describes the security protocols supported by the N2000 DMS, including SNMP, SSH, and
SSL.
SNMP
The Simple Network Management Protocol (SNMP) is widely used for network management.
It has been recognized and become an industrial standard. It aims to ensure that management
information can be transmitted between any two nodes. Based on SNMP, network administrators
can search information at any node in the network, locate faults, plan capacities, and generate
reports.
Compared with SNMPv1 and SNMPv2, SNMPv3 is improved in many aspects, including the
security and the access control. SNMPv3 defines the processing model of the third version SNMP
messages (V3MP), the user-based security model (USM), and the view-based access control
model (VACM).
SSH
The secure shell (SSH) permits a user to log in to the remote device in security, execute
commands, and transmit files. It is the key exchange protocol and the authentication protocol of
the remote device and client.
SSL
The secure sockets layer (SSL) is a security protocol, and provides the security for the
communication of networks (such as the Internet). The SSL prevents application programs from
wire tapping and being tampered during communication.
In fact, the SSL consists of two protocols:

l SSL record protocol: It refers to the information segmenting, information compressing,
data authentication, and data encryption provided by the application programs. SSLV3
supports the MD5 used and SHA for the data authentication and R4 and DES used for data
encryption. The key used for the data authentication and encryption can be negotiated
through the SSL handshaking protocol.
l SSL handshaking protocol: It is used for exchanging the version numbers, ciphering
algorithm, authentication, and exchanging keys. SSLV3 provides the key exchange
algorithm for the Deffie-Hellman, the key exchange mechanism based on the RSA, and
another key exchange mechanism based on Fortezza chip.
5.1.2 OS Security Policies

OS security is the basis for the secure running of the N2000 DMS. You need to maintain the OS
of the N2000 DMS based on the OS security policies.
Ensure the OS security in the following ways:

l Virus defense
Install the antivirus software, update the virus database in time, and start the real-time
protection function of the antivirus software.
l Network isolation

System
Install the firewall software, close the ports that are not used, and close the unnecessary
network services.
l OS account security
Change the initial password in time. The password should be complex enough. Change the
password periodically. Delete the unnecessary accounts.
l Application security
Do not install the applications that are not related to the N2000 DMS, such as the game
applications and the personal office applications that are not related to the N2000 DMS.
5.1.3 User Security Policies

All the operations on the N2000 DMS are performed by the N2000 DMS users. Therefore, user
security is very important to N2000 DMS security. You need to manage the N2000 DMS users
based on the user management policies.
Right Security
l N2000 DMS user
An N2000 DMS user can log in to the N2000 DMS through the N2000 DMS client. The
unique name and password of the N2000 DMS user decide the operation and management
rights of the user. When the N2000 DMS user is added to a user group, the N2000 DMS
user inherits all the rights of the user group. The administrator of the N2000 DMS is
admin. The N2000 DMS user admin has all operation rights to the N2000 DMS.
l N2000 DMS user group
A set of the N2000 DMS users with the same operation and management rights. When an
N2000 DMS user is added to a N2000 DMS user group, the N2000 DMS user automatically
has all the rights of the N2000 DMS user group.
l Device set
A set of managed devices. Divide the managed devices into different device sets, and you
can assign device management rights conveniently. If a user or user group is assigned the
operation rights to a device set, the user or user group has the operation rights to all the
devices in the device set. Therefore, you need not assign the user or user group the
management rights to individual devices respectively.
l Operation set
A set of operation rights. You can divide the operation rights into different operation sets
according to the operation level or specific requirements. Assign an operation set to a user
or user group, and you can assign the operation rights to the user or user group. In this way,
you can conveniently manage the operation rights.
l Division of authority and division of domain
The divisions of authority and domain are achieved by dividing operations and devices into
different sets. By division of authority, you can divide operation rights into different
functional domains. by division of domain, you can divide the NEs into network domains.
You can set the managed group for an N2000 DMS user to manage the users based on
domains.
Typically, you can assign the rights to an N2000 DMS user in the following ways:
Add the N2000 DMS user to a user group.

System
Generally, you can add the N2000 DMS user to a user group. Then the N2000 DMS
user automatically inherits all the rights of the user group. In this way, you assign the
rights to the N2000 DMS user.
Adjust the rights.
When the user needs a certain operation right or right on a device, you can assign the
right to the user directly.
Password Security
l Password policy
The password policy defines the requirement on the password complexity. According to
the password policy, all passwords need to meet the requirement on the password
complexity. A reasonable password policy can effectively improve the N2000 DMS
security.
l Weak password dictionary
A weak password dictionary collects the passwords that are easy to crack. When the
password is the same as any of the passwords in the weak password dictionary, the password
is regarded as an invalid one. You need to reset the password. The N2000 DMS weak
password dictionary does not collect the common passwords that are easy to crack. You
can redefine the weak password dictionary according to the actual needs.
5.1.4 Policies of the N2000 DMS Log Management

This describes the policies of the N2000 DMS log management, including querying and dumping
logs.
N2000 DMS logs include N2000 DMS user logs, dynamic debugging information logs, system
running logs, database logs, and device logs.
The policies of log management include querying and dumping logs.
l The N2000 DMS supports the graphical interface for querying log information. The
administrator can know the operations of other users on the N2000 DMS.
l The N2000 DMS supports the functions of manually and automatically dumping logs.
For details of log management, see 7 Managing N2000 DMS Logs.
5.1.5 Database Security

The data related to the N2000 DMS are stored in databases. Therefore, database security is very
important to the running of the N2000 DMS. You need to maintain the databases based on the
database security policies.
Database security involves the following two aspects:

l Database password security
By default, the administrator of the Sybase database is sa. The sa user has the highest
administrative right. Therefore, you need to ensure the password of sa is secure.
You need to immediately change the password of N2000user by using the user
password change tool of the database after the N2000 DMS is installed.
l Data security

System
Back up the database manually: When necessary, you can back up the database
manually. For example, before you perform a dangerous operation, you need to back
up the database in case that damages occur as the result of data loss.
Back up the data regularly: Set the policies on backing up the database regularly; back
up the database regularly so that you can use the backup data to restore the database
when necessary.
Dump the data: You can export data from a database either in manual mode or automatic
mode and then save the data to other locations.
NOTE
The dumped data is deleted from the database.
5.2 Setting Communication Security Between the Server

and the Client
When you set the communication mode between the server and the client, you can use the
Security Socket Layer (SSL) mode to ensure that the communication is secure.
Prerequisite
Context
l If the client and server applications are on the same host and the server uses SSL, then the
client can use Common or SSL mode. If the server uses Common mode, the client can use
Common mode only.
l If the client and server applications are not on the same host, the client can log in to the
server only when it uses the same mode as the server.
Procedure
Step 1 Log in to the System Monitor Client.
Step 2 Choose System > Communication Mode Settings.
Step 3 In the Communication Mode Settings dialog box, select a communication mode.
NOTE
l Common: The server and the client use a common protocol to communicate.
l Security(SSL): The server and the client use SSL to communicate. All messages between them are
encrypted.

System
CAUTION
After you change the communication mode, the System Monitor Client and the N2000 DMS
server exit automatically. You need to manually restart the System Monitor Client and the N2000
DMS server. The new communication mode takes effect after you restart the N2000 DMS.
----End

System
Administrator Guide - Solaris 6 Managing the N2000 DMS Users
6 Managing the N2000 DMS Users
About This Chapter
The N2000 DMS is operated and maintained by users. Therefore, assigning user rights correctly
and reasonably is important to the N2000 DMS security.This describes users and rights,
managing the OS and database users, setting the security of N2000 DMS users, processes and
examples of creating users, and changing and monitoring users.
6.1 Users and Rights

This describes users and rights. Assigning user rights is the prerequisite and base of managing
N2000 DMS users.
6.2 Managing Users in OS
This describes how to create different OS users and change their passwords.
6.3 Managing Database Users
This describes database users related to the N2000 DMS and the methods of changing the
passwords of database users.
6.4 Setting the N2000 DMS User Security
This describes how to set global security policies of N2000 DMS users to manage N2000
DMS users globally.
6.5 Creating N2000 DMS Users
This describes how to create N2000 DMS users. Creating users includes creating operation sets,
creating user groups, creating users, and setting management domains and operation rights for
user groups and users.
6.6 Example of Creating an N2000 DMS User
This section provides an example on how to create an N2000 DMS user. It also describes user
right management.
6.7 Modifying N2000 DMS Users
This describes how to modify and delete relevant attributes of N2000 DMS users.
6.8 Monitoring N2000 DMS Users
This describes how to monitor all login N2000 DMS users. Through this function, you can
monitor their operations and force the user who performs invalid operations to quit the N2000
DMS.

System
6 Managing the N2000 DMS Users Administrator Guide - Solaris
6.1 Users and Rights

This describes users and rights. Assigning user rights is the prerequisite and base of managing
N2000 DMS users.
6.1.1 Concepts Related to the N2000 DMS Users

When you perform user management tasks, you need to know some basic concepts, such as the
user, user group, operation set, ACL, managed domain, and operation right. Knowing these
concepts helps you perform user management, especially when rights management is complex.
6.1.2 N2000 DMS User Rights Assignment Policies
When assigning user rights, you need to know the management policies such as the general
policy, user group management policy, and user management policy. These policies help you
to complete user rights management more quickly and accurately.
6.1.3 OS User
This section describes the OS user types and their rights related to N2000 DMS.
6.1.4 Database User
This section describes the N2000 DMS database users and related rights.
6.1.5 NMS Users and Rights
This section describes the NMS users and related rights. The NMS user account is used to
perform operations on the N2000 DMS client. In the N2000 DMS, the NMS user refers to the
N2000 DMS user.
6.1.1 Concepts Related to the N2000 DMS Users

When you perform user management tasks, you need to know some basic concepts, such as the
user, user group, operation set, ACL, managed domain, and operation right. Knowing these
concepts helps you perform user management, especially when rights management is complex.
l User
In different scenarios, the concept of user has different meanings:
A user who logs in to the N2000 DMS by using a user account and performs operations.
A user account. For example, creating a user refers to creating a user account.
l Normal user
A user who has non-security operation rights.
l Security administrator
A user who has security subtype rights.
According to the managed groups, there are two types of administrators:
Local security administrator
The local security administrator (local administrator for short) can query only the user
groups in the managed groups. The local administrator cannot perform the operations
at the group level.
Global security administrator
The global security administrator (global administrator for short) can query all user
groups and perform the operations at the group level.
l User group

System
A set of user accounts and rights.

You can assign rights to users by creating a user group and then adding the users to the user
group. The users then automatically inherit all the rights of the user group. You can manage
user rights better by grouping the users.
l Security user group
A user group that has the right to perform the security subtype operations or operation sets.
If a user group has the security rights, the group belongs to the security user group.
l Group administrator
The administrator of a user group that can manage the users in the user group.
l Global group administrator
The administrator of a user group that can manage all user groups. The super user admin
is also a global group administrator.
l Operation set
A set of the operations that can be performed in the N2000 DMS.
You can assign an operation set to a user or a user group. This helps you to avoid the trouble
caused by assigning operation rights to users individually and managing users and rights
individually. You can conveniently assign a set of operations to users by creating and
managing an operation set.
l Security operation set
A security operation set is a set of security operations.
l Device set
Device set management enables you to manage the operation rights to the devices in a
device set.
After you plan and create a device set, you can assign the device set to a specified user
group. Then the users in the user group have the operation rights to the devices in the device
set. This helps you to uniformly assign and manage the N2000 DMS user rights.
l ACL
The N2000 DMS supports the function of ACL. The ACL is a secure access control
mechanism. It restricts a user of logging in to the server through only the clients with the
specified IP addresses.
The ACL can effectively control the client IP addresses through which the user can log in
to the N2000 DMS. In this case, even if the user account and the password are obtained by
illegal users, these users cannot log in to the N2000 DMS; thus the N2000 DMS security
is improved. The N2000 DMS provides two ACLs:
System ACL
The ACL of the entire N2000 DMS. All the users can log in to the N2000 DMS only
through specific IP addresses or network segments.
User ACL
The ACL of a user. The current user can log in to the N2000 DMS only through specific
IP addresses or network segments.
NOTE
The IP addresses or the network segments for the user ACL cannot exceed the range of the IP
addresses or the network segments for the system ACL.
l Managed domain
A managed domain refers to the physical resources and logical resources managed by the
user or the specific domains managed by the user group.

System
In the topology view or on the device panel, only the managed objects are displayed. You
can change the managed domain of a user or a user group to change the user rights. The
managed domain is represented as a submap tree (consistent with the physical topology
view).
If the entire submap tree is selected, the parent submap and all the child submaps in the
parent submap can be managed.
If the tree is partially selected, the parent submap can be managed, but some child
submaps under it cannot be managed.
If the tree is not selected, the parent submap cannot be managed, but some child
submaps under it may be manageable.
l Operation rights
Operation rights determine the operations that a user can perform.
l Group-level operations
These are operations performed on user groups. For example, the operations such as setting
the managed domain or operation rights to a user group, creating a user group, or deleting
a user group.
6.1.2 N2000 DMS User Rights Assignment Policies

When assigning user rights, you need to know the management policies such as the general
policy, user group management policy, and user management policy. These policies help you
to complete user rights management more quickly and accurately.
l General policy
Only admin can assign and modify security operation rights, and add a user to a user group
that has security rights. Other operation rights can be assigned by the administrator who
has the assignment right.
l User group management policy
Only admin can create and delete security user groups. As a global administrator, you can
query all user groups, perform the operations at the group level, set the members for normal
user groups, and change the general properties of your own user group. But you cannot
change the operation rights and managed domain of your own user group. As a local
administrator, you can only view the user groups in your managed groups, but you cannot
perform the operations at the group level. If you have no managed group, you cannot view
any user group. You can manage a user group only when it is in your managed user groups.
l User management policy
Only admin can create and delete a security administrator, and manage the validity of a
security administrator. The admin user can change some general properties of admin while
other users cannot change their own general properties. Security administrators can manage
the normal users in the managed user groups of the security administrators. Security
administrators can manage users only when the users are in the managed user groups of
the security administrators.
User management realizes simple division of authority and domain. Division of authority
specifies the operation rights that a user has and division of domain specifies the user groups
that can be managed by a user. You can manage users only when you have security rights
and manageable user groups. If you have manageable user groups and you have the rights
to query the information on a single user and set user operation rights, you can assign all
non-security rights to other users. If you can manage all user groups and you have the rights
to query the information on a single user group and set operation rights of user groups, you

System
can assign all non-security rights to other user groups. In this case, you cannot assign non-
security rights to your own user group.
l Operation set management policy
Operation set management is not restricted by managed user groups. Only admin can
create, delete, and modify security operation sets. Normal operation sets can be managed
by security administrators, and they are not related to the user groups or users that they
belong to. As a security administrator, if you have the right to manage operation sets, you
can add non-security operation sets.
l Login rights management policy
User login rights are related to security properties. You can set security properties to manage
the login period and the IP address range for login.
6.1.3 OS User
This section describes the OS user types and their rights related to N2000 DMS.
root
The root user is the default system administrator of the solaris operating system.
With the highest right of the operating system, the root user controls all resources, creates other
users, assigns rights to other users, and performs all operations of the operating system. The
root user is responsible for installing or uninstalling the application software of the N2000
DMS server.
n2kuser
During the N2000 DMS installation, the N2000 DMS creates a nmsuser user of the operating
system automatically. The n2kuser user is responsible for setting environment variables of the
N2000 DMS server and starting the N2000 DMS client at the server.
The n2kuser user has all the rights of the directory /n2kuser. The file ./profile in this directory
records environment variables for N2000 DMS running.
sybase
The sybase user is responsible for setting Sybase environment variables, installing, maintaining
and managing the Sybase database.
With all the rights of the directory /opt/sybase, the sybase user can manage the Sybase database,
for example, configuring Sybase environment variables and starting/stopping the Sybase service.
6.1.4 Database User

This section describes the N2000 DMS database users and related rights.
sa
The sa user is the default Sybase system administrator.
The sa user has the highest right to the database.

System
N2000user
When you install the N2000 DMS, it creates the database user N2000user automatically. You
use this user to access the Sybase database.
The N2000user user can manage the N2000 DMS database.
The user N2000user manages the N2000 DMS database through the N2000 DMS database
backup tool.
6.1.5 NMS Users and Rights

This section describes the NMS users and related rights. The NMS user account is used to
perform operations on the N2000 DMS client. In the N2000 DMS, the NMS user refers to the
N2000 DMS user.
After you install the N2000 DMS, two default users are created: admin and corba.
NOTE
The corba user is created only after you install the northbound interface component.
The N2000 DMS user accounts and their rights are described as follows:
l admin
The admin user has all the operation rights of NMS operation. You use it to manage the
N2000 DMS. The default password is admin. When you for the first time log in to the
N2000 DMS as admin, the system forces you to change the password. By default, only
one admin user is allowed to log in at the same time.
l corba
The third-party NMS uses the corba user to connect to the N2000 DMS. The default
password is corbaagent. Change the password on your first login.
By default, the corba user has no managed domain or operation right. Typically, the
administrator does not need to change the rights of the corba user. You need to modify the
ACL of the corba user before the third-party NMS uses the corba user to connect to the
N2000 DMS.
l Other N2000 DMS users
Other N2000 DMS users are created by the admin user. These N2000 DMS users are
created base on the requirements of management.
6.2 Managing Users in OS

This describes how to create different OS users and change their passwords.
6.2.1 Creating an OS User

This section takes creating admin as an example and describes how to create an OS user in
Solaris.
6.2.2 Changing the Password of root
This section describes how to change the root user password.
6.2.3 Changing the Password of n2kuser
This section describes how to change the n2kuser user password.
6.2.4 Changing the Password of OS User sybase

System
For the security purpose, you should change the passwords of sybase regularly.
6.2.1 Creating an OS User

This section takes creating admin as an example and describes how to create an OS user in
Solaris.
Procedure
Step 1 Log in as root.
Step 2 On a terminal screen, run the following command:
# useradd -c "admin" -m -d /opt -g n2000group -s /bin/ksh admin

NOTE
l -c: comment
l -m: create a home path in case of no home path
l -d: home path, namely, the N2000 DMS is located
l -g: user group of the admin user
l -s: shell used by the admin user
----End
6.2.2 Changing the Password of root

This section describes how to change the root user password.
Context
l For the security purpose, you should change the passwords of root regularly.
l You need to change the password of use root at least once every six months.
l The password consists of letters and numbers. It must contain at least eight characters.
l If the password is known to an unauthorized person, it is recommended to change it
immediately to ensure the regular management and maintenance of the N2000 DMS.
Procedure
Step 1 Log in the Solaris operating system as the nmsuser.
Step 2 Open a terminal window and switch to the root user. Run the following commands:
$ su
Password:<root password>
Step 3 Run the following command to change the password of the root user:
# passwd root
New Password: <new password>
Re-enter new Password: <new password>

System
passwd: password successfully changed for root
----End
6.2.3 Changing the Password of n2kuser

This section describes how to change the n2kuser user password.
Context
l For the security purpose, you should change the passwords of n2kuser regularly.
l You need to change the n2kuser password at least once every six months.
Procedure
Step 1 Log in to the Solaris operating system as the n2kuser user.
Step 2 Open a terminal window and switch to the root user. Run the following commands:
$ su
Password:<root password>
Step 3 Run the following command to change the password of the n2kuser user:
# passwd nmsuser
passwd: password successfully changed for nmsuser
----End
6.2.4 Changing the Password of OS User sybase

For the security purpose, you should change the passwords of sybase regularly.
Context
l You need to change the password of user sybase at least once every six months. The
password consists of letters and numbers. It must contain at least eight characters. If the
password is known to an unauthorized person, it is recommended to change it immediately
to ensure the regular management and maintenance of the N2000 DMS.
l When the N2000 DMS is deployed in a distributed manner, you are recommended to
maintain the database as the sybase user (not the root user).
Procedure
Step 1 Log in to the OS as root.

System
Step 2 Open a terminal window.

Step 3 Run the following command to change the password of the sybase user:
# passwd sybase
passwd: password successfully changed for sybase
----End
6.3 Managing Database Users

This describes database users related to the N2000 DMS and the methods of changing the
passwords of database users.
6.3.1 Changing the Password of sa

This section describes how to change the sa user password.
6.3.2 Changing the Password of N2000 DMS User
This section describes how to change the password of the N2000 DMS user.
6.3.1 Changing the Password of sa

This section describes how to change the sa user password.
Prerequisite
When you change the password of the database user by using the DbPwdTool, other
configuration files of the N2000 DMS are modified automatically. Therefore, stop the N2000
DMS server program before you changing the password.
Context
l For the security purpose, you should change the sa user password regularly to insure the
security of the sa user password.
l This section describes how to change the password of the sa user of the Sybase database
in Solaris. For the password change the sa user of the SQL Server database in Windows,
you can refer to this section as these two operations are similar.
CAUTION
The operation of changing the sa user password is incorrect, which may cause an N2000 DMS
running exception. Please use the provided password changing tool (DbPwdTool)to change the
password.

System
Procedure
Step 1 Open a terminal window, and run the following commands.
# DbPwdTool
The following information appears.

iManager NMS Database Password Tool
Input '1' to modify sa password.

Input '2' to modify NMS normal user password.
Input 'x' to exit the tool.
Please input your choice:
Step 2 Input 1, and press Enter.

Press ESC then Enter to exit without doing anything:
Please input the old password of the sa in database:
Step 3 Input the old password, and press Enter.

Please input the new password:
<sa new password>
Step 4 Input the new password, and press Enter.
Reinput the new password:
<sa new password>
Step 5 Input the new password again, and press Enter.
You have changed the password.
Please check the above informations. Be sure there is not any error before resta
rting your NMS.
Step 6 Input x and press Enter to exit the DbPwdTool.

Thanks, exit.
Press any key to continue
Step 7 Close the terminal window.
----End
6.3.2 Changing the Password of N2000 DMS User

This section describes how to change the password of the N2000 DMS user.

System
Prerequisite
When you change the password of the database user by using the DbPwdTool, other
configuration files of the N2000 DMS are modified automatically. Therefore, stop the N2000
DMS server program before you changing the password.
Context
l The password consists of letters and numbers. It must contain at least eight characters. If
the password is known to an unauthorized person, change it immediately to ensure regular
management and maintenance of the N2000 DMS.
l To avoid improper operations, you should use the password change tool (DbPwdTool) to
change the password of N2000user. Improper operations can cause the N2000 DMS to fail.
l Use the DbPwdTool to change the password in the configuration files on the database server
and N2000 DMS server.
Procedure
Step 1 Open a terminal window, and run the following commands.
# DbPwdTool

iManager NMS Database Password Tool
Input '1' to modify sa password.

Input '2' to modify NMS normal user password.
Input 'x' to exit the tool.
Step 2 Input 2, and press Enter.

Press ESC then Enter to exit without doing anything:
Please input the old password of the NMS normal user or sa:
<N2000user old password>
Step 3 Input the old password, and press Enter.
The following information appears:
Please input the new password:
<N2000user new password>
Step 4 Input the new password, and press Enter.
Reinput the new password:
<N2000user new password>
Step 5 Input the new password again, and press Enter.
The information similar to the following appears:

System
You have changed the password.

Please check the above informations. Be sure there is not any error before resta
rting your NMS.
Step 6 Input x and press Enter to exit the DbPwdTool.

Thanks, exit.
Press any key to continue
Step 7 Close the terminal window.
----End
6.4 Setting the N2000 DMS User Security

This describes how to set global security policies of N2000 DMS users to manage N2000
DMS users globally.
6.4.1 Setting the Login Mode of the N2000 DMS

6.4.2 Setting the Password Policy
The password policy ensures security for the N2000 DMS. You can set the security policies such
as the password length and the password complexity.
6.4.3 Setting the User Account Policy
To ensure security of the N2000 DMS user account, you need to set the account policy.
6.4.4 Setting the ACL
With this function, you can access the N2000 DMS only through a client whose IP address is
listed in the ACL.
6.4.5 Modifying the Validity Period of an N2000 DMS User Account
You can modify the validity period of an N2000 DMS user account.
6.4.6 Modifying the Validity Period of an N2000 DMS User Password
You can modify the validity period of an N2000 DMS user password.
6.4.7 Setting the Period for Disabling an N2000 DMS User Account
You can set the period for disabling an N2000 DMS user account. When a user account is not
used in the period, the account is disabled.
6.4.8 Initializing an N2000 DMS User Password
When you forget the password, or the password expires, you need to apply for the administrator
so that you can initialize the password.
6.4.1 Setting the Login Mode of the N2000 DMS


System
Prerequisite
Context
l There are two login modes: single-user mode and multi-user mode. In single-user mode,
only the admin user can log in to the N2000 DMS.
l In multiuser mode, the admin user and other users can log in to the N2000 DMS at the
same time. When the mode is changed to single-user mode, other users are forced to log
out of the N2000 DMS, and only the admin user can log in.
Procedure
Step 1 Choose System > NMS Security Settings > Single User Mode.
----End
6.4.2 Setting the Password Policy

The password policy ensures security for the N2000 DMS. You can set the security policies such
as the password length and the password complexity.
Prerequisite
You must be an NMS user with the security operator authority or higher.
Procedure
Step 1 Choose System > NMS Security Settings > Security Policies from the main menu.
Step 2 In the Security Policies dialog box, click the Password Police tab.

System
Step 3 On the Password Policy tab, set the password policy.
Step 4 Click OK.
----End
6.4.3 Setting the User Account Policy

To ensure security of the N2000 DMS user account, you need to set the account policy.
Prerequisite
Procedure
Step 1 Choose System > NMS Security Settings > Security Policies.
Step 2 In the Security Policies dialog box, click the Account Policies tab.

System
Step 3 On the Account Policies tab, set the parameters for the user account policy.
Step 4 Click OK.
----End
6.4.4 Setting the ACL

With this function, you can access the N2000 DMS only through a client whose IP address is
listed in the ACL.
Prerequisite
You must be an NMS user with the security maintainer authority or higher.
Context
l Before setting the ACL, you can log in to the N2000 DMS only as admin.
l When you log in to the N2000 DMS as admin for the first time, you can log in through the
client that is not installed on the same computer as the server. The N2000 DMS adds the
IP address of the client to the ACL automatically.
l The values of the ACL can be IP addresses or network segments. When network segments
are used, the format is A.B.C.D/E. The value E is the mask of the N2000 DMS. For example,
10.10.10.0/24. The value 24 indicates the first 24 bits of the 32-bit binary subnet mask are
1, that is, 255.255.255.0.
Procedure
Step 1 Choose System > NMS Security Settings > ACL.
Step 2 In the ACL dialog box, configure the ACL settings.

l Add an ACL item.
Click Add. In the Add dialog box, select IP Address or Segment and then specify an IP
address or segment. Or select Start IP address to end IP address and then specify the
start IP address and end IP address. Click OK.
l Modify an ACL item.
Select an ACL item and then click Modify. In the Modify dialog box, modify the IP address
or segment, or the start IP address and the end IP address. Click OK.
l Delete an ACL item.

System
Select an ACL item and then click Delete. In the Confirm dialog box, click OK.
----End
6.4.5 Modifying the Validity Period of an N2000 DMS User Account

You can modify the validity period of an N2000 DMS user account.
Prerequisite
Procedure
Step 1 Choose System > NMS User Management.
Step 2 In the Security Object navigation tree, expand the Users node, and then select a user.
Step 3 Click the General tab. In Account validity (days), modify the value of the validity period or
select Always Valid.
Step 4 Click Apply.
----End
6.4.6 Modifying the Validity Period of an N2000 DMS User

Password
You can modify the validity period of an N2000 DMS user password.
Prerequisite
Procedure
Step 3 Click the General tab. In Password Validity (days), modify the value of the validity period or
select Always Valid.
Step 4 Click Apply.
----End
6.4.7 Setting the Period for Disabling an N2000 DMS User Account
You can set the period for disabling an N2000 DMS user account. When a user account is not
used in the period, the account is disabled.
Prerequisite

System
Procedure
Step 3 Click the General tab. In Disable User Account Unused For (days), set the period or select
Unrestricted.
Step 4 Click Apply.
----End
6.4.8 Initializing an N2000 DMS User Password

When you forget the password, or the password expires, you need to apply for the administrator
so that you can initialize the password.
Prerequisite
Context
You do not need to enter the old password when you initialize the password. You only need to
set a new password directly. As an administrator, however, if you want to change your password,
you need to enter the old password. Therefore, administrators cannot initialize their own
passwords.
Procedure
Step 2 In the Security Object navigation tree, expand the Users node. Right-click a user and choose
Set Password.
Step 3 In the Set New Password dialog box, enter the new password twice, and then click OK.
NOTE
If you want to change the current user password, open the Change Password dialog box. In the dialog
box, enter the old password, new password, and confirmation password. Click OK.
----End
6.5 Creating N2000 DMS Users

This describes how to create N2000 DMS users. Creating users includes creating operation sets,
creating user groups, creating users, and setting management domains and operation rights for
user groups and users.
6.5.1 Process of Creating an N2000 DMS User

This section describes the common configuration process of creating users, including a complete
process and a simple process of creating users.
6.5.2 Creating Device Set

System
After the planning and creation of an equipment set, you can assign the set to a specified user
group. In this way, all users in this user group are authorized to perform the operations on the
equipment within the equipment set. This function helps allocate and manage NM user
authorities uniformly.
6.5.3 Creating an N2000 DMS Operation Set
You can create an operation set to assign it to a specific user group or user. The user group or
user then has the right to perform the operations in the set. Therefore, you can manage the N2000
DMS user rights in a unified manner.
6.5.4 Creating a User Group
This section describes how to create N2000 DMS user groups. For the convenience of
management, you can assign rights to the user group where the users are when you assign rights
to the users.
6.5.5 Assigning a Managed Domain to a User Group
You can assign a managed domain to a user group, and then the user group can manage the
specific objects, such as a specific submap or a specific device set. By default, a user in a user
group inherits all the rights of the user group. You can change the managed domain of a user to
adjust the user rights.
6.5.6 Assigning Operation Rights to a User Group
You can assign operation rights to a user group so that the users in the user group can perform
relevant operations.
6.5.7 Assigning Device Management Rights to a User Group
After you assign rights to a user group to manage a new device, all users in this group can manage
the device.
6.5.8 Creating an N2000 DMS User
This topic describes how to create an N2000 DMS user and how to set the properties for the
user.
6.5.9 Adding an N2000 DMS User to a User Group
This section describes how to add a user to a user group so that the user can inherit the rights of
the user group.
6.5.10 Assigning a Managed Domain to an N2000 DMS User
You can assign a managed domain to a user so that the user can have a managed domain besides
the managed domains of the user group. You can perform this operation when you want to assign
a managed domain to a specific user.
6.5.11 Assigning Operation Rights to an N2000 DMS User
You can assign operation rights to a user so that the user can have the rights besides those of the
user group. You can perform this operation when you want to assign operation rights to a specific
user.
6.5.12 Setting the ACL for N2000 DMS Users
You can set the ACL for all the N2000 DMS users so that the users can log in to the N2000
DMS through only specific IP addresses.
6.5.1 Process of Creating an N2000 DMS User

This section describes the common configuration process of creating users, including a complete
process and a simple process of creating users.
The complete process of creating an N2000 DMS user consists of the following steps:

System
l Create a user group.

l Create a user.
l Add the user to the user group.
l Assign management rights.
l Assign operation rights.
In actual situations, because the user group is created and operation sets are configured, the
process of creating a user usually covers one or some of the complete process of creating a user.
Table 6-1 shows a simple process of creating an N2000 DMS user.
Table 6-1 Simple process of creating an N2000 DMS user
Step Operation Description
1 6.5.8 Creating an N2000 DMS Before you operate the N2000 DMS, you
User need to obtain a user account.
2 6.5.9 Adding an N2000 DMS User After a user is added to a user group, the user
to a User Group automatically inherits the rights of the user
group.
Table 6-2 shows the complete process of creating an N2000 DMS user.
Table 6-2 Complete process of creating an N2000 DMS user
1 6.5.2 Creating Device Set Assigning devices in sets to users reduces

the complexity of user management.
2 6.5.3 Creating an N2000 DMS Assigning operations in sets to users

Operation Set reduces the complexity of user
management.
3 6.5.4 Creating a User Group Managing users in groups reduces the

complexity of user management.
4 6.5.5 Assigning a Managed Generally, you are recommended to assign

Domain to a User Group a management domain to the user through
the user group.
5 6.5.6 Assigning Operation Rights Generally, you are recommended to assign

to a User Group operation rights to the user through the user
group.
6 6.5.8 Creating an N2000 DMS Before you operate the N2000 DMS, you
User need to obtain a user account.
7 6.5.9 Adding an N2000 DMS User When a user is added to a user group, the
to a User Group user automatically inherits the rights of the
group.

System
8 6.5.10 Assigning a Managed After a managed domain is assigned to a

Domain to an N2000 DMS User user, the user can manage specific devices.
9 6.5.11 Assigning Operation Rights After operation rights are assigned to a user,
to an N2000 DMS User the user can perform specific operations.
10 6.5.12 Setting the ACL for N2000 For security purposes, you can set the user
DMS Users to log in to the N2000 DMS from only the
specific IP addresses.
6.5.2 Creating Device Set

After the planning and creation of an equipment set, you can assign the set to a specified user
group. In this way, all users in this user group are authorized to perform the operations on the
equipment within the equipment set. This function helps allocate and manage NM user
authorities uniformly.
Prerequisite
Procedure
Step 2 In the Security Object navigation tree, right-click the Device Sets node and choose New Device
Sets.

System
Step 3 In the New Device Sets dialog box, set the information on and members of the new device set.
NOTE
To add a member, click and then click Browse topology by group or Browse topology by NE type.
In the displayed list, choose the topology object to be modified.
Step 4 Click OK.
----End
6.5.3 Creating an N2000 DMS Operation Set

You can create an operation set to assign it to a specific user group or user. The user group or
user then has the right to perform the operations in the set. Therefore, you can manage the N2000
DMS user rights in a unified manner.
Prerequisite

System
Context
Only admin can create a security operation set.
Procedure
Step 2 In the Security Object navigation tree, right-click the Operation Sets node and choose New
Operation Set.
Step 3 In the New Operation Set dialog box, set the information on the new operation set.
Step 4 Click OK.
----End
6.5.4 Creating a User Group

This section describes how to create N2000 DMS user groups. For the convenience of
management, you can assign rights to the user group where the users are when you assign rights
to the users.

System
Prerequisite
Context
l You can create a user group only when you have the right to manage all the user groups.
l If a user can manage all the user groups, this user is not displayed in the group administrator
properties.
l You cannot create a user group twice or create a user group named ALL.
Procedure
Step 2 In the Security Object navigation tree, right-click the User Groups node and choose New User
Group.
Step 3 In the New User Group dialog box, enter the information on the new user group.
Step 4 Click OK.
----End
6.5.5 Assigning a Managed Domain to a User Group

You can assign a managed domain to a user group, and then the user group can manage the
specific objects, such as a specific submap or a specific device set. By default, a user in a user
group inherits all the rights of the user group. You can change the managed domain of a user to
adjust the user rights.
Prerequisite
l You must be an NMS user with the security operator authority or higher.

System
l You can set the managed domain of a user group only when you have the right to manage
all the user groups.
Context
l When the managed domain of a submap is assigned to a user group, the users in the group
can manage all the resources under the submap by default.
l You can manage the resources under a submap only when you have the right to the managed
domain of the submap.
Procedure
Step 2 In the Security Object navigation tree, expand the User Groups node, and then select a user
group.
Step 3 Click the Managed Domain tab to view the managed domain of the user group.
Step 4 Click Modify. In the Modify User Group Managed Domain dialog box, modify the state of
the managed domain in the submap navigation tree.
Step 5 Click OK.
----End
6.5.6 Assigning Operation Rights to a User Group

You can assign operation rights to a user group so that the users in the user group can perform
relevant operations.

System
Prerequisite
l You must be an NMS user with the security operator authority or higher.
l You can set a user group only when you can manage all the user groups.
Context
l Only admin can assign security operation rights.
Procedure
group.
Step 3 Click the Operation Rights tab to view the operation rights of the user group.
Step 4 Click Add. In the dialog box, add the operation rights.
Step 5 Click OK.
----End

System
6.5.7 Assigning Device Management Rights to a User Group

After you assign rights to a user group to manage a new device, all users in this group can manage
the device.
Prerequisite
operator.
Procedure
Step 3 Select the new user group in the Security Object navigation tree.
Step 4 Click the Operation Rights tab.
Step 5 Click Add.
Step 6 In the Add Right dialog box shown in Figure 6-1, select Fixed Network Device
Management for Type and the device to be managed for Subtype. Select operation sets to be
added in the Operation Name list. Click OK.
Figure 6-1 Adding rights to manage devices
Step 7 Click OK.
----End

System
6.5.8 Creating an N2000 DMS User

This topic describes how to create an N2000 DMS user and how to set the properties for the
user.
Prerequisite
Context
l If you have the right to manage all the user groups, you can create a user that does not
belong to any user group.
l If you have the right to manage the specified user groups, you can create a user belong to
only your managed groups and you must add the user to a group.
l NM SYSTEM is a special user of the N2000 DMS. The operations performed by NM
SYSTEM are triggered by the N2000 DMS automatically. If you create the NM
SYSTEM user on the client, the N2000 DMS prompts that a user with the same name
already exists.
l You cannot create a user twice or create a user named ALL.
Procedure
Step 2 In the Security Object navigation tree, right-click the Users node and choose New User.

System
Step 3 In the New User dialog box, enter the information on the new user.
Step 4 Click OK.
----End
6.5.9 Adding an N2000 DMS User to a User Group

This section describes how to add a user to a user group so that the user can inherit the rights of
the user group.
Prerequisite
Context
Only admin can add a user to a security user group.

System
Procedure
Step 3 Click the Groups tab.
Step 4 Click Add. In the Add User Groups dialog box, select the user group to be added.
Step 5 Click OK.
NOTE
When a user belongs to multiple user groups, the rights of the user are a union of rights of multiple user
groups.
----End
6.5.10 Assigning a Managed Domain to an N2000 DMS User

You can assign a managed domain to a user so that the user can have a managed domain besides
the managed domains of the user group. You can perform this operation when you want to assign
a managed domain to a specific user.
Prerequisite
Context
If a user has the right to set the management domain, then the user can assign all management
domains to managed users, including management domains that the user does not belong to.
Procedure
Step 2 In the Security Object navigation tree, expand the Users node. Select a user.
Step 3 Click the Managed Domain tab to view the managed domain of the user.
Step 4 Click Modify. In the Modify User Managed Domain dialog box, click and then click Browse
topology by group or Browse topology by NE type. In the displayed list, choose the topology
object to be modified.

System
Step 5 Click OK.
----End
6.5.11 Assigning Operation Rights to an N2000 DMS User

You can assign operation rights to a user so that the user can have the rights besides those of the
user group. You can perform this operation when you want to assign operation rights to a specific
user.
Prerequisite
Context
l Only admin can assign the security operation rights.
l If a user has the security administrator right, this user can assign all operation rights except
(including the operation rights that this user does not have) for the security right for the
managed users.

System
Procedure
Step 2 In the Security Object navigation tree, expand the Users node. Select a user.
Step 3 Click the Operation Rights tab to view the operation rights of the user.
Step 4 Click Add. In the Add Right dialog box, set the user operation rights.
Step 5 Click OK.
----End
6.5.12 Setting the ACL for N2000 DMS Users

Prerequisite

System
Procedure
Step 3 Click the ACL Settings tab.
l Use the system ACL.

Select Use System ACL.
l Use the user ACL.
Select Use User ACL. In the ACL list box, set the IP address or the network segment that
the user can access.
NOTE
When you set the user ACL, you can select the ACL from only the system ACL. If the ACL to be
set is not in the system ACL, click Set ACL. After adding the system ACL, set the user ACL.
Step 4 Click Apply.
----End
6.6 Example of Creating an N2000 DMS User

This section provides an example on how to create an N2000 DMS user. It also describes user
right management.
Simple Example of Creating a User

To create user A, who is responsible for monitoring network devices, do as follows:
1. Create a user account.
Before you operate the N2000 DMS, you need to obtain a user account.
2. Add the user to a user group.
Add user A to the monitor group. User A then inherits the managed domains and operation
rights of the monitor group.
After the operations are complete, the account can be used by user A.
Complex Example of Creating a User

Create two area (area A and area B) management devices that are monitored, operated, and
maintained by the personnel having different rights.
1. Create user groups.
To help manage the devices, the administrator creates 6 new user groups:
l Maintainer group of region A: is responsible for the device maintenance in region A.

System
l Operator group of region A: is responsible for the device operations in region A.

l Watcher group of region A: is responsible for the device status monitoring in region A.
l Maintainer group of region B: is responsible for the device maintenance in region B.
l Operator group of region B: is responsible for the device operations in region B.
l Watcher group of region B: is responsible for the device status monitoring in region B.
2. Add managed domains to user groups.
The new user groups have no device to manage, and you need to add the manageable devices
to the domains that can be managed by the user groups. Assign the managed domains of
devices in region A to the user groups of region A, and the managed domains of devices
in region B to the user groups in region B.
3. Add operation rights to user groups.
Assign operation rights to the user groups according to the user responsibilities.
4. Create user accounts.
Create user accounts according to the current users. To ensure the security of the N2000
DMS, different login periods are set according to the user shifts, and the login IP addresses
are bound to the users according to the workstations in different regions. For password
security purposes, the password must be changed upon the first login.
5. Add users to user groups.
Add the users to different user groups according to the user responsibilities. The users then
inherit the operation rights to the corresponding devices.
6.7 Modifying N2000 DMS Users

This describes how to modify and delete relevant attributes of N2000 DMS users.
6.7.1 Modifying the Member of an N2000 DMS Operation Set

You can modify the Member of an N2000 DMS operation set.
6.7.2 Modifying the Properties of an N2000 DMS User
You can modify the information on an N2000 DMS user, including the general properties, user
groups, ACL, managed domain, and operation rights.
6.7.3 Changing the User Group That an N2000 DMS User Belongs To
You can modify the user group of an N2000 DMS user so that the user can have the management
rights and operation rights of the user group.
6.7.4 Modifying the ACL for N2000 DMS Users
6.7.5 Modifying the Management Domain of an N2000 DMS User
You can modify the devices that a user can manage so that different N2000 DMS users can
manage specified devices.
6.7.6 Modifying the Operation Rights of an N2000 DMS User
To strictly control user operations on the managed devices, you can assign specific operation
rights to users. By default, a user has all the operation rights of the user group that the user
belongs to. You can adjust the operation rights of a user by modifying the operation rights of
the user or its user group.
6.7.7 Modifying the General Attributes of a User Group

System
This describes how to modify user group attributes. The user group attributes include basic user
group information such as the maximum number of sessions and group manager, and you can
change them as required.
6.7.8 Modifying the Managed Domain of a User Group
When a managed domain is no longer used, delete it to ensure the network security.
6.7.9 Modifying the Operation Rights of a User Group
You can adjust the operation rights of a user group and assign different rights to the user group.
6.7.10 Changing an N2000 DMS User Password
You need to change the N2000 DMS user password periodically to prevent a password theft.
6.7.1 Modifying the Member of an N2000 DMS Operation Set

You can modify the Member of an N2000 DMS operation set.
Prerequisite
Context
Only the admin user can modify members of the operation set that contains operation rights of
the security module.
Procedure
Step 2 In the Security Object navigation tree, expand the Operation Sets node, and then select an
operation set.
Step 3 Click the Members tab. Modify the properties of an N2000 DMS operation set.
l Add an operation
Click Add. In the Add Operations dialog box, set the operation you want to add. Click
OK.
l Delete an operation
Select the operation right you want to delete, and then click Delete. In the Confirm dialog
box, click OK.
----End
6.7.2 Modifying the Properties of an N2000 DMS User

You can modify the information on an N2000 DMS user, including the general properties, user
groups, ACL, managed domain, and operation rights.
Prerequisite

System
Procedure
Step 3 Click the General tab. In the right list, modify the general properties of the user, and then click
Apply.
Step 4 Click the Groups tab. At the bottom of the list box, click Add. In the Add User Group dialog
box, select a user group, and then click OK.
Step 5 Click the ACL Setting tab, choose Use User ACL. Choose the ACL, and then click Apply.
Step 6 Click the Managed Domain tab. Click Modify. In the Modify User Managed Domain dialog
box, modify the managed domain of the user. Click OK.
Step 7 Click the Operation Rights tab, and then modify the operation rights of the user.
l Add an operation right.
At the bottom of the list box, click Add. In the Add Rights dialog box, select a right you
want to add, and click OK.
l Delete an operation right.
In the right list box, select an operation right you want to delete, and then click Delete.
----End
6.7.3 Changing the User Group That an N2000 DMS User Belongs
To
You can modify the user group of an N2000 DMS user so that the user can have the management
rights and operation rights of the user group.

System
Prerequisite
Context
You cannot set the user group that the admin user belongs to.
Procedure
Step 2 In the Security Object navigation tree, expand the User node, and then select a user.
Step 3 Click the Groups tab.
Step 4 Change the user group to which the NMS user belongs.
l Add the user group to which the NMS user belongs.
Click Add. Choose the user group to be added from the list, and then click OK.
l Delete the user group to which the NMS user belongs.
Choose the user group to be deleted, click Delete, and then click OK in the Confirm dialog
box.
----End
6.7.4 Modifying the ACL for N2000 DMS Users

Prerequisite
Procedure
Step 3 Click the ACL Settings tab.
l Use the system ACL.

Select Use System ACL.
l Use the user ACL.
Select Use User ACL. In the ACL list box, set the IP address or the network segment that
the user can access.

System
NOTE
When you set the user ACL, you can select the ACL from only the system ACL. If the ACL to be
set is not in the system ACL, click Set ACL. After adding the system ACL, set the user ACL.
Step 4 Click Apply.
----End
6.7.5 Modifying the Management Domain of an N2000 DMS User

You can modify the devices that a user can manage so that different N2000 DMS users can
manage specified devices.
Prerequisite
Procedure
Step 3 Click the Managed Domain tab. Click Modify. In the Modify User Managed Domain dialog
box, modify the status of the management domain in the submap tree.

System
Step 4 Click OK.
----End
6.7.6 Modifying the Operation Rights of an N2000 DMS User

To strictly control user operations on the managed devices, you can assign specific operation
rights to users. By default, a user has all the operation rights of the user group that the user
belongs to. You can adjust the operation rights of a user by modifying the operation rights of
the user or its user group.
Prerequisite
Context
l Only admin can modify security operation rights.
l Only when you have the right to set the operation rights of users and user groups, you can
assign all the operation rights except the security operation rights to other users, including
the operation rights that you do not have.

System
Procedure
Step 3 Click the Operation Rights tab to view the operation rights of the user.
Step 4 Modify the operation rights of the user:

l Add operation rights.
Click Add. In the Add Right dialog box, set the rights you want to add. Click OK.
l Delete operation rights.
Select the operation rights you want to delete, and then click Delete. In the
Confirmation dialog box, click OK.
----End
6.7.7 Modifying the General Attributes of a User Group

This describes how to modify user group attributes. The user group attributes include basic user
group information such as the maximum number of sessions and group manager, and you can
change them as required.
Prerequisite
operator.
Procedure
Step 3 In the Security Object navigation tree, select User Groups.
Step 4 Click the General tab.
Step 5 Change the user group attributes.
Step 6 Click Apply.
----End
6.7.8 Modifying the Managed Domain of a User Group

When a managed domain is no longer used, delete it to ensure the network security.
Prerequisite
l You must be an NMS user with the security maintainer authority or higher.
l You can set the managed domain of a user group only when you have the right to manage
all the user groups.

System
Procedure
group.
Step 3 Click the Managed Domain tab to view the current managed domain of the user group.
Step 4 Click Modify. In the Modify User Group Managed Domain dialog box, modify the status of
the managed domain in the submap navigation tree, and then click OK.
Step 5 Click OK.
----End
6.7.9 Modifying the Operation Rights of a User Group

You can adjust the operation rights of a user group and assign different rights to the user group.
Prerequisite
Procedure
group.
Step 3 Click the Operation Rights tab.
Step 4 Modify the operation rights of the user group:

l Add operation rights.

System
Click Add. In the Add Right dialog box, set the rights you want to add. Click OK.
l Delete operation rights.
Select the operation rights you want to delete, and then click Delete. In the
Confirmation dialog box, click OK.
----End

Prerequisite
Procedure
Set Password.
NOTE
box, enter the current password and your new password. Click OK.
----End
6.8 Monitoring N2000 DMS Users

This describes how to monitor all login N2000 DMS users. Through this function, you can
monitor their operations and force the user who performs invalid operations to quit the N2000
DMS.
6.8.1 Querying Login User Information

This section describes how to query the information on all the login users in the N2000 DMS.
6.8.2 Monitoring User Operations in Real Time
This section describes how to monitor the operations performed by the login users.
6.8.3 Forcing a Login User to Exit
You can force a user to exit the N2000 DMS if necessary.
6.8.4 Unlocking a User Account
You can unlock a user account.
6.8.5 Sending Messages to Online Users
You can send messages to specified users or all online users. Thus, users in different regions
can communicate with each other in real time on N2000 DMS maintenance experiences.
6.8.1 Querying Login User Information

This section describes how to query the information on all the login users in the N2000 DMS.

System
Prerequisite
l You must be an NMS user with the security watcher authority or higher.
l The group administrator can view the login information of all the users managed in the
group.
l You can query the information on all the users only when you can manage all the user
groups.
Procedure
Step 2 In the Security Object navigation tree, click the User node and choose Login User.
The login users are displayed on the Login User tab.
----End

Prerequisite
You must be an NMS user with the security watcher authority or higher.
Context
l Any users can monitor only their own operation logs.
l The group administrator can monitor operation logs of the users in the managed group.
l The global group administrator can monitor operation logs of all users.
l The user operations can be monitored only when the monitoring window is displayed.
Procedure
Step 1 Choose System > Monitor User Operations.

System
Step 2 In the Monitor User Operations dialog box, click Filter. Set User, Client, Result, and
Operation Level.
Step 3 Click OK.

The operations matching the conditions are displayed in the user operation checklist.
----End
6.8.3 Forcing a Login User to Exit

You can force a user to exit the N2000 DMS if necessary.
Prerequisite
Context
l You cannot force your own user account or admin to exit.
l The user can force only the managed users to exit.
Procedure
Step 2 In the Security Object navigation tree, click the Users node and choose Login User.
The login user information is displayed on the Login User tab.
Step 3 Right-click a user and choose Force to Exit.
Step 4 Click OK.

System
The user is forced to exit.
----End
6.8.4 Unlocking a User Account

You can unlock a user account.
Prerequisite
You must be an NM user with the "Security Operator" or higher priority.
Context
l If you log in to the N2000 DMS and enter incorrect passwords for the specified number of
consecutive times, your user account is locked. You can use the same account to log in to
the N2000 DMS again only when your account is unlocked.
l Only the user with the Security Operator rights or higher rights can unlock the managed
users.
l If a locked user is not unlocked manually, the N2000 DMS will unlock the user account
after a specified period of time (the default value is 30 minutes).
Procedure
Step 2 In the Security Object navigation tree, click the Users node, and then click the All User tab.
The information on all the users is displayed on the All User tab.
Step 3 Right-click a locked user and choose Unlock.

The user is unlocked.
----End
6.8.5 Sending Messages to Online Users

You can send messages to specified users or all online users. Thus, users in different regions
can communicate with each other in real time on N2000 DMS maintenance experiences.
Prerequisite
Procedure
Step 2 In the Security Object navigation tree, click the Users node and choose Login User.

System
Step 3 Send a message to a selected client or all other clients.

l Send a message to a selected client.
1. In the login user list, right-click a user and choose Send Message.
2. In the Send Message dialog box, select Send the message to the selected clients.
Enter the message content, and then click Send.
l Send the message to all clients.
1. In the login user list, right-click a user and choose Send Message.
2. In the Send Message dialog box, select Send the message to the all other clients.
Enter the message content, and then click Send.
----End

System
Administrator Guide - Solaris 7 Managing N2000 DMS Logs
7 Managing N2000 DMS Logs
About This Chapter
This describes log types in the N2000 DMS and the methods of dumping log data and monitoring
operation logs in real time.
7.1 Log Types

The log types of N2000 DMS including security logs, operation logs, and system logs. The
security logs and operation logs can be queried and dumped on the client GUI. The system logs
cannot be operated on the client GUI.
7.2 Managing NMS Security Logs
The N2000 DMS provides the function of managing security logs. This function enables you to
query and dump security logs.
7.3 Managing NMS Operation Logs
The N2000 DMS provides the function of managing operation logs. This function enables you
to query and dump non-security operation logs.
7.4 Managing Remote Notification Logs
The N2000 DMS provides the function of managing remote notification logs. This function
enables you to understand the status of sending remote notifications in real time. According to
the actual condition, you can resend or forward the remote notification message.
7.5 Setting a Log Forwarding Server
You can set a log forwarding server to forward the N2000 DMS logs to a third-party server.

System
7 Managing N2000 DMS Logs Administrator Guide - Solaris
7.1 Log Types

The log types of N2000 DMS including security logs, operation logs, and system logs. The
security logs and operation logs can be queried and dumped on the client GUI. The system logs
cannot be operated on the client GUI.
7.1.1 N2000 DMS Security Logs

You can browse security logs regularly to find vulnerabilities of N2000 DMS. Then you can
take corresponding measures to ensure the security of the N2000 DMS. Security logs record the
security operations performed by the N2000 DMS user, such as login and logout.
7.1.2 N2000 DMS Operation Logs
You can browse operation logs to know an operation performed by an N2000 DMS user at a
specific time. This can help to eliminate the impacts of faulty operations.
7.1.3 System Logs
The system logs record the running status of a program, such as loading data during the startup
of a program.
7.1.4 Debugging Logs
The debugging logs provide a detailed record on how the program functions are invoked. These
logs help the developers to find code problems.
7.1.1 N2000 DMS Security Logs

You can browse security logs regularly to find vulnerabilities of N2000 DMS. Then you can
take corresponding measures to ensure the security of the N2000 DMS. Security logs record the
security operations performed by the N2000 DMS user, such as login and logout.
Security logs record the operations of an N2000 DMS user on the N2000 DMS, such as logout,
login, log dump, device log synchronization, and other operations related to N2000 DMS
security.
7.1.2 N2000 DMS Operation Logs

You can browse operation logs to know an operation performed by an N2000 DMS user at a
specific time. This can help to eliminate the impacts of faulty operations.
Operation logs record the operations of an N2000 DMS user on the N2000 DMS, such as fault
management, performance management, topology management, and resource management.
7.1.3 System Logs

The system logs record the running status of a program, such as loading data during the startup
of a program.
The system logs are detailed as follows:
Path
The system logs are saved in $N2000ROOT/server/log, including the log files that are related
to the platform and those generated by the N2000 DMS service processes.
Logs in $N2000ROOT/server/log

System
l The logs in this path record the message processing and thread status of a process. A log
is generated when the N2000 DMS is started.
l The naming rule for the log file is: Process name_ProcID_YYYYMMDD_HHMMSS.log.
For example, the platform log of the security process is
N2000Secu_p52_20060307_084252.log.
l By default, each process has up to 10 log files, and the maximum size of each log file is 5
MB. When the number of log files exceeds the maximum number, the new log file
overwrites the earliest one automatically.
Format
The format of system logs is as follows:
10:31:22.408000.T950 EmfSysMoni INFO:
CEmfMoniCommonMethod::IsProcActive:
Each system log message consists of the header and the message body.
The header indicates the time, process ID, module name, and log debugging level. The header
and other parts of the message are separated by colons (:). For details, refer to Table 7-1.
Table 7-1 Parameters of system running logs

Parameter Description
Time Time when a debugging record is recorded.
Process ID Unique process identifier.
Module name Module name.
Log debugging level Log debugging level: ERROR, WARN, or INFO.
Message body User-defined debugging items.
7.1.4 Debugging Logs

The debugging logs provide a detailed record on how the program functions are invoked. These
logs help the developers to find code problems.
The debugging logs are detailed as follows:
Path
l The debugging logs are saved in $N2000ROOT/server/debug.
l The name format of the file is: debugged program name + number + .dbg. The "number"
ranges from 1 to 5, that is, each program has up to five debugging files by default. The five
files are used circularly, and the maximum size of each file is 1 MB by default. When the
fifth file reaches the maximum size, it overwrites the first file automatically.
Format
The format of debugging logs is as follows:

System
2006/03/21-20:07:28 TRACE-INFO EmfGnlDev CEmfQvCtrTask : Find

the device which need to ping!
Each dynamic debugging log consists of the header and the message body.
The header consists of four parts: time, debug ID, process ID, and module ID. The header and
other parts of the message are separated by colons (:). For details, refer to Table 7-2.
Table 7-2 Debugging logs
Time To identify the time when a debugging record is recorded. The format
is YYYY/MM/DD-HH:MM:SS.
Alarm level flag Grouped into three categories: TRACE-INFO, TRACE-WARN, and
TRACE-ERR, indicating three levels of debugging information.
Process flag Process names in the N2000 DMS.
Process internal Internal class name of a process, such as CEmfTopoQueryTask and

module flag GLOBAL.
Message body User-defined debugging items.
7.2 Managing NMS Security Logs

The N2000 DMS provides the function of managing security logs. This function enables you to
query and dump security logs.
7.2.1 Browsing Security Logs

You can query security logs to know the information about the security operations of the N2000
DMS.
7.2.2 Dumping Security Logs Manually
You can dump the security logs manually on the N2000 DMS. The dumped logs are saved as
files and deleted from the database.
7.2.3 Setting Auto Dump of Security Logs
Through the auto dump of security logs, you can periodically dump the security logs in the
N2000 DMS database. This can avoid that the logs reach the maximum storage capacity of the
database and that the system performance is degraded.
7.2.1 Browsing Security Logs

You can query security logs to know the information about the security operations of the N2000
DMS.
Prerequisite

System
Context
l Users can query only their own security logs.
l The group administrator can query security logs of the users in the managed group.
l The global group administrator and admin can query security logs of all users.
Procedure
Step 1 Choose System > Browse Log.
Step 2 In the Log Class navigation tree, select Security Logs. In the right pane, double-click a security
log to view its details.
NOTE
If the user has only the right to browse security logs, the Operation Logs node is not displayed.
Step 3 Choose to perform the following operations.

l Click Refresh to refresh the security logs.
l Click Filter. In the Filter dialog box, set the conditions to filter the security logs you
browse.
l Click Print. In the Range dialog box, set the start row and the end row. Then click OK.
l Click Save As. In the Save As dialog box, set the start row, end row, and file name. Then
click OK to save the logs to your local disk.
l Click Dump. In the Confirm dialog box, click OK. The security logs are saved to the
server.
----End


System
Prerequisite
Procedure
Step 1 Choose System > Database > Dump Manually.
Step 2 In the Manual Dump navigation tree, select Security Logs.
Step 3 In the Generation Time of Security Logs group box, set the dump condition.
Step 4 In the Records That Meet The Dump Condition group box, click Query.
Step 5 Click Dump.
Step 6 Click Close.
----End

Prerequisite

System
Procedure
Step 1 Choose System > Database > Dump Settings.
Step 2 In the Dump Settings navigation tree, select Security Logs.
Step 3 In the Overflow Dump group box, set overflow dump.
Step 4 In the Enable Dumping Periodically group box, set period dump.
Step 5 In the Dump Settings group box, set the dump path.
Step 6 Click OK.
----End
7.3 Managing NMS Operation Logs

The N2000 DMS provides the function of managing operation logs. This function enables you
to query and dump non-security operation logs.
7.3.1 Browsing Operation Logs

You can browse the operation logs to know the non-security operations and their results on the
N2000 DMS.
7.3.2 Dumping Operation Logs Manually
You can dump the operation logs manually on the N2000 DMS. The dumped logs are saved as
7.3.3 Setting Auto Dump of Operation Logs

System
Through the auto dump of operation logs, you can periodically dump the operation logs in the
7.3.1 Browsing Operation Logs

You can browse the operation logs to know the non-security operations and their results on the
N2000 DMS.
Prerequisite
Context
l If the user has the right to browse operation logs, the user can browse operation logs of all
users.
l The group administrator can query operation logs of the users in the managed group.
l The global group administrator and admin can query operation logs of all users.
Procedure
Step 1 Choose System > Browse Log.
Step 2 In the Log Class navigation tree, select Operation Logs. In the right pane, double-click a log
to view its details.
NOTE
If the user has only the right to browse operation logs, the Security Logs node is not displayed.
Step 3 Choose to perform the following operations.

l Click Refresh to refresh the operation logs.
l Click Filter. In the Filter dialog box, set the conditions to filter the security logs you
browse.

System
l Click Print. In the Range dialog box, set the start row and the end row. Then click OK.
l Click Save As. In the Save As dialog box, set the start row, end row, and file name. Then
click OK to save the logs to your local disk.
l Click Dump. In the Confirm dialog box, click OK. The operation logs are saved to the
server.
----End

Prerequisite
Procedure
Step 2 In the Manual Dump navigation tree, select Operation Logs.
Step 3 In the Generation Time of Operation Logs group box, set the dump condition.
Step 5 Click Dump.

System
Step 6 Click Close.
----End

Prerequisite
Procedure
Step 2 In the Dump Settings navigation tree, select Operation Logs.
Step 6 Click OK.
----End

System
7.4 Managing Remote Notification Logs

The N2000 DMS provides the function of managing remote notification logs. This function
enables you to understand the status of sending remote notifications in real time. According to
the actual condition, you can resend or forward the remote notification message.
7.4.1 Browsing Remote Notification Logs

The N2000 DMS provides the function of browsing remote notification logs. This function
enables you to check whether alarm remote notifications are sent successfully.
7.4.2 Resending Remote Notification Messages
The function of resending remote notification logs enables you to resend a remote notification
message conveniently after you fail to send it for the first time. Thus, you can remind the relevant
personnel to handle this alarm in time.
7.4.3 Forwarding Remote Notification Messages
The function of remote notification logs enables you to conveniently forward an alarm to the
relevant personnel for handling.
7.4.1 Browsing Remote Notification Logs

The N2000 DMS provides the function of browsing remote notification logs. This function
enables you to check whether alarm remote notifications are sent successfully.
Prerequisite
You must be an NMS user with the fault operator authority or higher.
Procedure
Step 1 Choose Fault > Browse Remote Notification Logs.
Step 2 In the Browse Remote Notification Logs window, click Filter. In the Filter dialog box, set
filter conditions, and then click OK.
NOTE
l The Browse Remote Notification Logs window displays only the required remote notification logs
according to the filter conditions.
l In the Filter dialog box, click Reset. The filter conditions before modification are restored.
Step 3 In the Browse Remote Notification Logs window, select a remote notification log. The
Notification Message and Failure Reason fields at the bottom of the window display the
detailed notification message and cause for failure.
----End
7.4.2 Resending Remote Notification Messages

The function of resending remote notification logs enables you to resend a remote notification
message conveniently after you fail to send it for the first time. Thus, you can remind the relevant
personnel to handle this alarm in time.

System
Prerequisite
Procedure
Step 2 In the Browse Remote Notification Logs window, right-click a remote notification log, and
then choose Resend Message.
NOTE
If the remote notification log is sent successfully, the Resend Message button becomes grey.
Step 3 In the Confirm dialog box, confirm whether you want to resend the remote notification message.
----End
7.4.3 Forwarding Remote Notification Messages

The function of remote notification logs enables you to conveniently forward an alarm to the
relevant personnel for handling.
Prerequisite
Procedure
Step 2 In the Browse Remote Notification Logs window, right-click a remote notification log, and
then choose Forward Message.
Step 3 In the Forward Message dialog box, enter email addresses or mobile phone numbers. Click
OK.
----End
7.5 Setting a Log Forwarding Server

You can set a log forwarding server to forward the N2000 DMS logs to a third-party server.
Prerequisite
Context
The log forwarding server forwards only security logs, operation logs, and device logs.
Procedure
Step 1 Choose System > Log Forwarding Server.

System
Step 2 In the Log Forwarding Server dialog box, click Add.
Step 3 In the Create Log Forwarding Server dialog box, set the server that receives the logs.
NOTE
l The IP address cannot be set to a loopback address.

l String Filter does not support wildcards.
l The switchover between the primary and secondary servers is supported when the value of Protocol is
TCP. When the primary sever fails, the secondary server takes over the service and receives the logs. When
the primary server is recovered, the service is switched back to the primary server.
l You can set a maximum of five servers to receive logs.
Step 4 In the Log Forwarding Server dialog box, choose to perform the following operations:
l Select a record, and then click Modify to modify the server information.
l Select a record, and then click Delete to delete the server information.
l Click Refresh to refresh the server information.
l Click Cancel to exit the Log Forwarding Server dialog box.
----End

System
Administrator Guide - Solaris 8 Managing N2000 DMS Processes and Services
8 Managing N2000 DMS Processes and

Services
About This Chapter
This describes how to manage N2000 DMS processes and services. Through this function, you
can manage processes and services through the graphical user interface (GUI).
8.1 Processes and Services
This describes the processes and services of the N2000 DMS. The processes of the N2000
DMS are started in four modes. When the system runs normally, multiple processes are started
on the server. Each process provides a specific service.
8.2 Setting Server Thresholds
When the alarm thresholds are set for the alarm server and a value exceeds the threshold, an
alarm is sent to the N2000 DMS, and you can obtain the exception information of the N2000
DMS server in time.
8.3 Monitoring Process Status
Monitoring process status enables you to view the process information on the server. You can
start, stop, and set the process start mode.
8.4 Monitoring Database Status
This function enables you to view the database name, server name, and database status and
understand the running status of the N2000 DMS server. This function helps you identify and
solve problems in time and ensures that the system runs effectively.
8.5 Monitoring the Status of the N2000 DMS Server Performance
Monitoring the performance status enables you to view the system resource information of the
N2000 DMS server.
8.6 Monitoring Hard Disk Status
This section describes how to monitor the hard disk status of the currently logged-in N2000
DMS server.
8.7 Managing N2000 DMS Processes
The N2000 DMS provides the System Monitor Client (a GUI tool) to manage the processes.
You can use the tool to view process information, start or stop a process. You can also set the
process start mode. This helps you to handle emergency faults.

System
8 Managing N2000 DMS Processes and Services Administrator Guide - Solaris
8.8 Starting the N2000 DMS Service

You can start all N2000 DMS services on the System Monitor Client at a time by starting the
N2000 DMS service.
8.9 Setting Sampling
The sampling function enables you to save the running status of the N2000 DMS in a file to help
further analysis. Only the process information, database information, and resource information
of the N2000 DMS are sampled.
8.10 Stopping the N2000 DMS Service
You can stop all N2000 DMS services on the System Monitor Client at a time by stopping the
N2000 DMS service.

System
8.1 Processes and Services

This describes the processes and services of the N2000 DMS. The processes of the N2000
DMS are started in four modes. When the system runs normally, multiple processes are started
on the server. Each process provides a specific service.
8.1.1 Start Modes of Processes

This describes the start modes of the N2000 DMS processes.
8.1.2 List of N2000 DMS Processes
This describes the processes and services of the N2000 DMS.
8.1.1 Start Modes of Processes

This describes the start modes of the N2000 DMS processes.
The start modes of the N2000 DMS processes are as follows:
l Automatic
When the system is started, processes are automatically started. In automatic mode, the
system automatically restarts a process if the process is stopped abnormally.
l Manual
When the system is started, processes must be started manually. In manual mode, the system
does not automatically restart a process when the process is stopped abnormally.
l Disabled
When a process is disabled, the system cannot automatically restart the process and you
cannot manually start the process. After you set the process in disabled start mode to the
automatic start mode or the manual start mode, you can restart the process.
l External
It is the fixed start mode of the database server process. This mode cannot be modified.
8.1.2 List of N2000 DMS Processes

This describes the processes and services of the N2000 DMS.
Table 8-1 lists the details of N2000 DMS processes.
Table 8-1 List of N2000 DMS processes and services
Start Dependen
Process Function Description t Process Occupied Port
mdp It indicates the It must be started This In common

message and cannot be process communication mode,
distribution stopped. depends on use the 9800 port. In
process. the Sybase security socket layer
It distributes the process. (SSL) communication
messages of mode, use the 9803
each process. port.

System
Start Dependen
EmfSysMoni It indicates the It must be started mdp None

Dm system monitor and cannot be
process. stopped.
It starts, stops,
or monitors
processes on the
N2000 DMS
server.
It monitors the
running statuses
of the memory,
CPU, and
database.
EmfSecuDm It indicates the It must be started mdp None

security and cannot be
process. stopped.
It manages
users and
authorities.
EmfTopoDm It indicates the It must be started mdp None

topology and cannot be EmfSecuD
management stopped. m
process. If this process is
It provides the stopped, the
topology operation on the
management to client does not
devices respond.
classified on the
basis of space,
logic, or
network.

System
Start Dependen
EmfFaultDm It indicates the It must be started mdp None

fault and cannot be EmfsecuD
management stopped. m
process.
EmfTopoD
It provides m
functions such
as receiving,
querying,
providing the
correlation
analysis of, and
acknowledging
alarms
generated by
devices, the
N2000 DMS
and servers.
EmfPerfDm It indicates the It can be started mdp None

real-time optionally. You
performance can stop this
management process if it is not
process. required.
It monitors the
performance
indicators of
devices in real
time.
EmfGnlDevD It indicates the It can be started mdp None

m configuration optionally. EmfSecuD
management It can be stopped m
process of when the
general devices. EmfTopoD
management of m
It manages the ICMP and
Internet Control SNMP devices is EmfFaultD
Message not required. m
Protocol
(ICMP) devices
and the Simple
Network
Management
Protocol
(SNMP)
devices.

System
Start Dependen
EmfProxySer It indicates the It must be started mdp The default port is

ver device access and cannot be 9811.
proxy process. stopped.
It provides
proxy functions
of accessing
devices through
the TCP
protocols such
as Telnet and
FTP. Thus,
accessing a
device from the
client is
simplified.
ForwardAgen It indicates the It can be stopped mdp 9826

t SNMP when the SNMP
forwarding forwarding is not
process. required.
It forwards an
SNMP request
to the managed
device and
returns the
SNMP response
from the device.
EmfDBBack It indicates the It can be stopped mdp 9809

up database when no
backup process. scheduled
It provides the backup task
simple backup exists or you do
for the NMS not need to
database, and manually back
supports both up the database.
scheduled and
manual backup.

System
Start Dependen
EmfExamDm It indicates the It can be stopped EmfSecuD 9810

test process. when the m
It dynamically dynamic
debugs the debugging is not
EmfTopoDm, required.
EmfGnlDevD
m, and
EmfFaultDm
processes.
Through this
process, you
can query the
running status
of them.
EmfProjDoc It indicates the It can be stopped mdp None

Dm project when the output
document of project
management documents is not
process. required.
It provides the
details of the
managed
devices and
generates
project
documents.
SNMPAgent It indicates the It can be stopped mdp 9812

SNMP process when the alarm EmfFaultD
of the forwarding m
northbound function is not
interface required. EmfsecuD
module. m
It realizes the EmfTopoD

proxy function m
of SNMP, and
provides the
alarm
forwarding
function to the
superior NMS
or third-party
NMS.

System
Start Dependen
EmfSyslogA It indicates the It can be stopped mdp None

gent log forwarding when no other
process. NMS needs to be
It forwards logs connected to the
to the log server N2000 DMS
of the system. through the
Syslog protocol.
iAF_Agent It indicates the It can be stopped mdp 9815

Common when no other iagent_nt
Object Request NMS needs to be
Broker connected to the Naming_Se
Architecture N2000 DMS rvice
(CORBA) through the
process of the CORBA
northbound protocol.
interface
module.
It realizes the
proxy function
of the CORBA
protocol, and
provides the
access of
obtaining the
topology and
alarm
information for
other NMSs.
iagent_nt It indicates the It can be stopped Naming_Se 9817

CORBA when no other r-vice
notification NMS needs to be mdp
service process. connected to the
It provides the N2000 DMS
services of through the
subscribing to, CORBA
filtering, and protocol.
distributing the
CORBA
notification.

System
Start Dependen
Naming_Serv It indicates the It can be stopped mdp 9816

ice CORBA name when no other
service process. NMS needs to be
It provides the connected to the
service of N2000 DMS
querying through the
CORBA CORBA
objects protocol.
according to
name.
EmfTrapRece It indicates the It must be started EmfFaultD The UDP listening

iver process of and cannot be m port number ranges
receiving and stopped. from 162 to 65535 and
translating Trap the default number is
messages. 162.
The service port
number ranges from
11000 to 12000 and
the default number is
11000.
DmsL2VDm It indicates the It must be started EmfFaultD None

Layer 2 view and cannot be m
management stopped. EmfTopoD
process. It m
manages Layer
2 views.
DmsSyslogC It indicates the It must be started None 514

ollector Syslog collector and cannot be
process. It stopped.
collects the
Syslog of
devices.
DmfResDm It indicates the It must be started None None

resource and cannot be
management stopped.
process. It
manages device
resources.
DmfClidrvD It indicates the It must be started None None

m driver process and cannot be
of the command stopped.
line interface.

System
Start Dependen
DmsDcDm It indicates the It must be started EmfSecuD None

data center and cannot be m
management stopped.
process. It
manages the
device
configuration
files and image
programs.
DmsIPDm It indicates the It must be started EmfTopoD None

IP view and cannot be m
management stopped. EmfSecuD
process. It m
manages IP
views.
UcmDm It indicates the It must be started EmfSecuD None

cluster and cannot be m
process. It m
manages
clusters. EmfFaultD
m
DmsMseDm It indicates the It must be started EmfSecuD None

management and cannot be m
process of the stopped. EmfTopoD
ME60 and m
MA5200
devices. It
manages the
data of the
ME60 and
MA5200
devices.
DmsQvxDm It indicates the It must be started EmfSecuD None

NE and cannot be m
process of the m
Quidway
devices. It
manages the
data of the
Quidway
devices

System
Start Dependen
DmsrprDm It indicates the It must be started EmfSecuD None

N2000 DMS and cannot be m
RPR view stopped. EmfFaultD
management m
process. It
manages RPR EmfTopoD
views. m
DmsSyslogD It indicates the It must be started EmfSecuD None

m N2000 DMS and cannot be m
Syslog stopped. EmfFaultD
management m
process.
EmfTopoD
It manages the
m
policies of
receiving the CollectorM
Syslog. grDm
NeMplsDm It indicates the It can be started EmfSecuD None

DMS NeMpls optionally. It can m
process. be stopped when EmfTopoD
It provides NE the function of m
configuration collector
for the LSP management is
service. not used.
Cau It indicates the Optional. mdp 8250

client auto Can be stopped if
upgrade it is not required
service. to back up the
It provides the database
function of periodically or
automatically manually.
upgrading the
client from an
earlier version
to a later
version.
ColAgentDm It indicates the It must be started None 12101

collector and cannot be
module stopped.
process.
It provides the
function of
sending alarms
to the alarm
manager.

System
Start Dependen
CollectorDm It indicates the It must be started ColAgentD None

collector and cannot be m
process. stopped.
It provides the
function of
collecting the
NMS data.
CollectorMgr Indicates the It must be started EmfSecuD None

Dm collector and cannot be m
management stopped. EmfFaultD
process. m
It manages the EmfTopoD
collector. m
GctlDm It indicates the It can be started EmfSecuD None

general optionally. It can m
configuration be stopped when EmfTopoD
template the general m
process. configuration
It provides template
configurations function is not
to templates. used.
sybase It indicates the It must be started None None

database server and cannot be
process. In stopped.
Solaris, it
provides
database
services.
DmslinkMgr It indicates the It must be started EmfSecuD None

Dm link and cannot be m
process. m
It provides the
function of
importing and
creating links.

System
Start Dependen
DmsPerfConf It indicates the It can be started None 8900, 9005, 9443, and
Dm performance optionally. It can 9009
configuration be stopped when
process. the IP network
It manages performance
resources, manager is not
resource running.
groups,
templates,
group
templates,
instances, and
group
instances.
DmsPerfProb It indicates the It can be started None 7321

eDm performance optionally. It can
probe process. be stopped when
It provides the the IP network
function of performance
managing tasks, manager is not
collecting data, running.
and processing
data.
DmsPerfPolD It indicates the It can be started None None

m performance optionally. It can
polling process. be stopped when
It provides the the IP network
function of performance
managing manager is not
resource group running.
tasks, obtaining
probe data,
processing data,
and dumping
history data.

System
Start Dependen
VasDiagDm It indicates the It can be started mdp 162

T&D optionally. It can
management be stopped when
process. the test diagnosis
It provides the is not running.
functions of
creating,
deleting,
modifying, and
querying test
suites, test
cases, and
diagnosis
policies in the
diagnosis
feature. The
process also
support the
functions of
network scan,
and exporting
and dumping
history data.
DmsScDm It indicates the It can be started EmfSecuD 162

service optionally. It can m
It manages is not running.
customers,
composite
services, PW
services,
L3VPN
services, and
VPLS services.
DmsCasDm It indicates the It can be started EmfSecuD None

change auditing optionally. It can m
process of the be stopped when
N2000 DMS. the test diagnosis
It displays the is not running.
changes of
device entities,
software
images, and
configuration
files.

System
Start Dependen
DmsLspDm It indicates the It can be started EmfSecuD None

LSP service optionally. It can m
process of the the test diagnosis
N2000 DMS. is not running.
It manages
static LSP, TE
tunnel, and
MPLS OAM
services. It does
not support
single-point
MPLS
management.
DCServer It indicates the It can be started EmfSecuD None

DC optionally. It can m
It manages is not running.
device
configuration
files and image
programs.
LdapAgent It provides the It can be started EmfSecuD None

LDAP NBI optionally. It can m
service. be stopped when
the test diagnosis
is not running.
SNMPServer It provides It can be started None It uses port 9800 and

background optionally. If the port 9803 of the mdp
support for intended office process. It does not
DMB of H3C does not have the occupy other ports.
devices. devices of H3C,
this process does
not need to be
started.
SecPolicyMg It indicates the It must be started None None

rDm process of and cannot be
centralized stopped.
security policy
configuration.
It manages
policy
configuration
for security
devices.

System
8.2 Setting Server Thresholds

When the alarm thresholds are set for the alarm server and a value exceeds the threshold, an
alarm is sent to the N2000 DMS, and you can obtain the exception information of the N2000
DMS server in time.
8.2.1 Relations Between Thresholds and Alarms

The N2000 DMS enables you to set the alarm thresholds.
8.2.2 Setting the Performance Threshold
You can set the N2000 DMS performance threshold through the System Monitor Client. When
the CPU, memory, hard disk, or database usage of the N2000 DMS exceeds the threshold, the
System Monitor Server sends an alarm to the N2000 DMS.
8.2.1 Relations Between Thresholds and Alarms

The N2000 DMS enables you to set the alarm thresholds.
N2000 DMS supports the alarm threshold setting:
l When the usage of the CPU, memory, disk, or database exceeds the alarm threshold, the
System Monitor Server sends an alarm to the N2000 DMS server. You can see that the
related record turns red on the System Monitor Client.
l After the alarm is sent, if the usage is lower than the alarm threshold, the System Monitor
Server sends a cleared alarm to the N2000 DMS server. The record turns to normal color
on the System Monitor Client.
8.2.2 Setting the Performance Threshold

You can set the N2000 DMS performance threshold through the System Monitor Client. When
the CPU, memory, hard disk, or database usage of the N2000 DMS exceeds the threshold, the
System Monitor Server sends an alarm to the N2000 DMS.
Context
To set N2000 DMS thresholds, you need to have the rights to set the SysMonitor information.
Procedure
Step 2 Choose System > Monitor Settings.
Step 3 Click the Threshold tab to set the thresholds.

System
Step 4 In the Monitor Settings dialog box, click OK.
----End
8.3 Monitoring Process Status

Context
In routine maintenance, you need to view the process information only. Do not perform other
operations because N2000 DMS services may be affected in case of misoperations.
Procedure
Step 2 Click the Process tab. The details of all processes to be monitored are displayed in a table on
the Process tab.
Step 3 From the list, right-click one or more records, and then choose one of the following actions:
l Refresh: To refresh all the information of the selected process.
l Start Process: To start the selected process.
l Stop Process: To stop the selected process.
l Start mode: To change the start mode of the selected process.

System
NOTE
There are three start modes:
l Automatic: The process restarts automatically after it exits exceptionally.
l Manual: The process does not restart automatically after it exits exceptionally. You need to restart it
manually.
l Disabled: The process cannot be started through the System Monitor Client.
l Details: To query the process information.
----End
8.4 Monitoring Database Status

Context
When the database usage exceeds the alarm threshold, the System Monitor sends an alarm to
the N2000 DMS server. Meanwhile, the related record on the System Monitor Client turns red.
Procedure
Step 2 Click the Database tab. The managed databases are listed in detail.
l Refresh: To refresh the information on the selected databases.
l Expand: To expand the data space or log space of selected databases.
----End
8.5 Monitoring the Status of the N2000 DMS Server

Performance
N2000 DMS server.
Procedure
Step 2 Click the System Resource tab.

The system information of the N2000 DMS server is listed in detail.
Step 3 From the list, right-click one or more records and choose Refresh to refresh the system resource
information of the N2000 DMS server.
----End

System
8.6 Monitoring Hard Disk Status

DMS server.
Context
When the hard disk usage exceeds the alarm threshold, the System Monitor sends an alarm to
Procedure
Step 2 Click the Disk tab. The hard disk information is listed in detail.
Step 3 From the list, right-click one or more records and choose Refresh to refresh the hard disk
information.
----End
8.7 Managing N2000 DMS Processes

The N2000 DMS provides the System Monitor Client (a GUI tool) to manage the processes.
You can use the tool to view process information, start or stop a process. You can also set the
process start mode. This helps you to handle emergency faults.
Context
In daily maintenance, you are recommended to view only the process information. Do not
perform other operations. Improper operations might affect the operation of the N2000 DMS.
Procedure
Step 2 Click the Process tab. All monitored processes are listed.
Step 3 From the process list, select one or more processes, and then right-click them to choose:
l Start Process to start the selected processes. If a process is already started, you do not need
to restart it.
l Stop Process to stop the selected processes.
l Start Mode to set the start mode of the selected processes.
NOTE
You can set three modes for a process:

l Automatic: The process restarts automatically after it stops for an exception.
l Manual: The process does not restart automatically after it stops for an exception. You need to
restart it manually.

System
l Refresh to update the process information.

l Details to view the process details.
----End
8.8 Starting the N2000 DMS Service

You can start all N2000 DMS services on the System Monitor Client at a time by starting the
N2000 DMS service.
Context
When you start the N2000 DMS service, you can view the startup status of the services on the
Process tab on the System Monitor Client.
Procedure
Step 2 Choose System > Start All NMS Service.

The N2000 DMS server is started.
----End
8.9 Setting Sampling

The sampling function enables you to save the running status of the N2000 DMS in a file to help
further analysis. Only the process information, database information, and resource information
of the N2000 DMS are sampled.
8.9.1 Manual Sampling

You can manually sample the process information, database information, and resource
information of the N2000 DMS. This helps analyze the running status of the N2000 DMS in
time.
8.9.2 Automatic Sampling
The monitoring system automatically sample the process information, database information, and
resource information of the N2000 DMS according to the specified sampling period.
8.9.1 Manual Sampling

You can manually sample the process information, database information, and resource
information of the N2000 DMS. This helps analyze the running status of the N2000 DMS in
time.
Prerequisite

System
Context
l You can sample only the process information, database information, and resource
information.
l If -- appears in the sample file, it indicates that the field is meaningless in current state.
l In the Solaris OS, the sample file is saved to $N2000ROOT/server/log/report. In the
Windows OS, the sample file is saved to %N2000ROOT%\server\log\report.
l The default format of the name of a sampling file is systemresourceyear/month/date/
hour/minute/second,databaseyear/month/date/hour/minute/second,processyear/
month/date/hour/minute/second, such as systemresource20080221095842. You can
change the name of a sampling file as required.
l Sampling files can be saved only in the .csv format.
Procedure
Step 2 Click the Process, Database or System Resource tab.
Step 3 Choose System > Manual Sampling.
Step 4 In the Process Manual Sampling dialog box, enter a sampling file name.
Step 5 Click OK.
----End
8.9.2 Automatic Sampling

The monitoring system automatically sample the process information, database information, and
resource information of the N2000 DMS according to the specified sampling period.
Prerequisite
Context
l Automatic sampling applies to only the information on processes, databases, and system
resources.
l If -- appears in the sample file, it indicates that the field is meaningless in current state.
l The report file name does not contain the extension.
l If the sample data is less than 1 KB (the minimum requirement), automatic sampling stops.
l When reported files reach the maximum capacity, the old sampling information is cleared
so that the new information is saved.
l In the Solaris OS, the sample file is saved to $N2000ROOT/server/log/report. In the
Windows OS, the sample file is saved to %N2000ROOT%\server\log\report.
Procedure

System
Step 2 Choose System > Automatic Sampling Settings.

Step 3 Click the Process, Database or System Resource tab.
Step 4 In the Automatic Sample Settings dialog box, select Automatic Sampling.
Step 5 In the Automatic Sample Parameters group box, set Sampling Period(s), Report
Filename, and Maximum Report Size.
l Sampling Period(s): indicates the cycle that the System Monitor performs automatic
sampling. The value ranges from 1 to 31536000, in seconds. The default value is 10.
l Report Filename: indicates the name of the sampling report file. The value ranges from 1
to 64, in bytes.
l Maximum Report Size: indicates the maximum space for saving the sampling report file.
The value ranges from 512 to 10240, in KB. The default value is 1024.
Step 6 Click OK.
----End
8.10 Stopping the N2000 DMS Service

You can stop all N2000 DMS services on the System Monitor Client at a time by stopping the
N2000 DMS service.
Context
CAUTION
Stopping the N2000 DMS service causes disconnection from the client. Therefore, the
unreserved data on the client cannot be stored or accessed.
Procedure
Step 2 Choose System > Stop All NMS Service.
Step 3 In the Confirm dialog box, click OK. The N2000 DMS service stops in 30 seconds.
----End

System
Administrator Guide - Solaris 9 Managing N2000 DMS Databases
9 Managing N2000 DMS Databases
About This Chapter
This describes the concepts about databases, the methods of viewing N2000 DMS databases and
their status, and the methods of backing up, restoring, expanding, and clearing N2000 DMS
databases. The N2000 DMS databases store all data about the interaction between the N2000
DMS and devices. Based on the databases, You can process and view relevant data on the N2000
DMS.
9.1 Basic Concepts About Databases
This describes the N2000 DMS basic databases, and the methods of dumping and backing up
the databases.
9.2 Starting the Database Backup Tool
Start the database backup tool and configure the database server before you back up the database.
9.3 Setting the Database Server
Set the database server before you backup or restore the specific N2000 DMS database.
9.4 Viewing the Database
This operation allows you to view basic information of an N2000 DMS database, including
database size, used size, and created time.
9.5 Setting the Backup Device
The settings of backup device are related to the configuration of backup file path, tape drive,
and other important configuration. Therefore, set the backup device correctly before you perform
backup.
9.6 Setting the Database Set
Databases are backed up based on database sets. Therefore, before backing up databases, you
need to set database sets.
9.7 Configuring the Timing Backup Policy
You can configure the timing backup period and the start time when you add, modify, or delete
the timing policy process.
9.8 Backing Up the N2000 DMS Database Manually
The database backup tool provides two manual backup modes: backup and bcpout. After you
set the parameters for manually backing up a database, the N2000 DMS starts the database
backup immediately.

System
9 Managing N2000 DMS Databases Administrator Guide - Solaris
9.9 Configuring a Timing Backup Task

Timing backup indicates that the system backs up data automatically according to the backup
frequency set in the timing backup task.
9.10 Querying Backup and Restoration Logs
This describes how to query backup and restoration logs. The backup and restoration operations
of the N2000 DMS databases are performed through the database backup tool. You can view
the operation records of the backup and restoration in the database backup tool.
9.11 Expanding an N2000 DMS Database
This describes how to expand an N2000 DMS database. Through this function, according to the
scale of the communication networks managed by the N2000 DMS, you can manually expand
the databases that have insufficient spaces for data or logs. You can expand databases through
the GUI or command lines.
9.12 Clearing an N2000 DMS Database
This describes how to clear an N2000 DMS database. When a database has a large amount of
data, you can dump the data in the database to files. The dumped data is removed from the
database. Then, you can clear the N2000 DMS database to ensure the performance and normal
running of the database.

System
9.1 Basic Concepts About Databases

This describes the N2000 DMS basic databases, and the methods of dumping and backing up
the databases.
9.1.1 N2000 DMS Database Overview
This describes the six basic databases of the N2000 DMS.
9.1.2 Introduction to Database Backup Tool
The database backup tool helps you to back up and restore the N2000 DMS database to protect
the data. The database backup tool also supports the centralized remote maintenance of the
N2000 DMS database. Thus, you can perform the backup and dump operations continently and
quickly.
9.1.3 Differences Between Dump and Backup
Dump and backup are two operations on data. Knowing their definitions and differences help
you perform the two operations properly.
9.1.1 N2000 DMS Database Overview

This describes the six basic databases of the N2000 DMS.
The N2000 DMS sets up the following basic databases:
l FaultDB
l LogDB
l PerfDB
l SecurityDB
l TopoDB
l GnldevDB
NOTE
master, model and tempdb are the system databases.
FaultDB
Alarm data is stored in FaultDB. It is recommended that the data space is not less than 750 MB
and the log space is not less than 500 MB.
The names and functions of tables in FaultDB are as follows:
l tbl_AlarmCfg: It records static configuration information about alarms.

l tbl_CurAlm: It records current alarms.
l tbl_Event: It records event information.
l tbl_HisAlm: It records history alarms.
l tbl_AlmShieldCondition: It records the shielding conditions of alarms and events.
l Other tables: They record internal realization information about fault management.

System
LogDB
The NMS user operation logs and related data are stored in LogDB. It is recommended that the
data space is not less than 150 MB and the log space is not less than 75 MB.
The names and functions of tables in LogDB are as follows:
l tbl_Log: It records operation information about NMS users.
l tbl_LogPara: It records personal setting information about NMS user logs.
l tbl_Syslog: It records the Syslog operation information.
l tbl_SyslogServer: It records running information about the Syslog server.
PerfDB
The real-time performance data is stored in PerfDB. It is recommended that the data space is
not less than 40 MB and the log space is not less than 20 MB.
The names and functions of tables in PerfDB are as follows:
l tbl_PerfTmpl: It records performance template information.
l tbl_PerfIndi: It records performance index information.
l tbl_IndiInTmpl: It records information about performance indexes and templates.
l tbl_MibObj: It records information about the Management Information Base (MIB) nodes
that the performance indexes need to access.
l Other tables: They record internal realization information about performance management.
SecurityDB
The security right data is stored in SecurityDB. It is recommended that the data space is not less
than 80 MB and the log space is not less than 80 MB.
The names and functions of tables in SecurityDB are as follows:
l tbl_User: It records user information.
l tbl_Group: It records user group information.
l tbl_CmdSet: It records operation set information.
l tbl_GrantRight: It records information of assigning rights.
l Other tables: They record internal realization information about security management.
TopoDB
The topology data is stored in TopoDB. It is recommended that the data space is not less than
80 MB and the log space is not less than 50 MB.
The names and functions of tables in TopoDB are as follows:
l tbl_Node: It records the data of topology nodes.
l tbl_Submap: It records the data of topology submaps.
l tbl_Link: It records the data of topology connections.
l Other tables: They record internal realization information about topology management.

System
GnldevDB
The data of third-party devices is stored in GnldevDB. It is recommended that the data space is
not less than 80 MB and the log space is not less than 40 MB.
The names and functions of tables in GnldevDB are as follows:
l tbl_DevTypeAndNodeTypeTab: It records information about the relationships between
device types and node types.
l tbl_IPIfTab: It records information about the list of device interfaces.
l Other tables: They record internal realization information about third-party device
management.
9.1.2 Introduction to Database Backup Tool

The database backup tool helps you to back up and restore the N2000 DMS database to protect
the data. The database backup tool also supports the centralized remote maintenance of the
N2000 DMS database. Thus, you can perform the backup and dump operations continently and
quickly.
The basic functions of the database backup tool are as follows:
l Viewing Information
View the general information of the N2000 DMS database and logs of the backup tool
operations.
l Configuring Parameters
Configure the parameters for backup, including the backup device, database set and time
backup policy.
l Performing Tasks
Back up and restore the database, including timing backup, manual backup, and restore
database.
NOTE
The database backup tool is provided as a stand-alone component. This function is supported only when this
component is selected during the installation of the N2000 DMS.
9.1.3 Differences Between Dump and Backup

Dump and backup are two operations on data. Knowing their definitions and differences help
you perform the two operations properly.
Operation Meaning Description
Dump Export data from the l The purpose is to view the data in the
database into a file for future future.
reference. l The source data is deleted.
l The dumped data cannot be recovered
from the file to the database.

System
Operation Meaning Description
Backup Export data from the l The purpose is to recover the data to
database into a file. When the database in case of a fault.
the source data is damaged, l The source data is not deleted.
you can import the backup
data into the database for l The backup data is recovered to the
recovery purpose. database.
9.2 Starting the Database Backup Tool

Start the database backup tool and configure the database server before you back up the database.
Prerequisite
l The network communication between the database backup tool client and the N2000
DMS server is normal.
l The database backup process is normal.
Context
l During the N2000 DMS installation, the N2000 DMS creates a nmsuser user of the
operating system automatically. The nmsuser is responsible for setting environment
variables of the N2000 DMS server and starting the N2000 DMS client at the server. The
nmsuser has all the rights of the directory /nmsuser. The file ./profile in this directory
records environment variables for N2000 DMS running.
l When you install the N2000 DMS, it creates the database user N2000user automatically.
You use this user to access the Sybase database. The N2000user user can manage the
N2000 DMS database. The user N2000user manages the N2000 DMS database through
the N2000 DMS database backup tool.
Procedure
Step 1 Start the database backup tool client as follows:
l Solaris OS: log in to the Solaris operating system as user n2kuser and enter the CDE. Click
on the front panel.

l Windows OS: log in to the Windows OS. Choose Start > All Programs > Network
Management System > N2000 DMS Database Backup Tool. or double-click in

the desktop.
Step 2 Choose System > Add Server. In Adding Server, set the server name and IP address.
Step 3 Click Add to add a database server.
Step 4 In the navigation tree on the left, choose the server to log in to.
The Login group box is displayed.
Step 5 In the Password text box, enter the password of the N2000 DMS database user N2000user.

System
Step 6 Click OK.
----End
9.3 Setting the Database Server

Set the database server before you backup or restore the specific N2000 DMS database.
Context
l The server name should be unique on one client. It contains alphanumeric characters,
underscore (_) and hyphen (-). It should not contain special characters.
l To delete the N2000 DMS database server, you need to log in to the N2000 DMS database
backup tool first.
Procedure
Step 1 Start the database backup tool.
Step 2 Add or delete the database server according to the requirement:

l Add a database server
Choose System > Add Server. In Adding Server, set the parameters. Click Add. In the
Information dialog box, click OK. Then the server node is displayed in the N2000
DMS database server navigation tree.
l Delete a database server
To delete a server, in the N2000 DMS database server navigation tree, select a server node.
Choose System > Delete Server. In the Confirm dialog box, click Yes. The server is then
deleted and the corresponding node is removed from the N2000 DMS database server
navigation tree.
----End
9.4 Viewing the Database

This operation allows you to view basic information of an N2000 DMS database, including
database size, used size, and created time.
Context
When you query the databases, you can view the information on all the databases in All
Databases. When you set a database set, you cannot select the filtered databases such as master
and the databases with their names longer than 32 characters.
Procedure
Step 1 Log in to the database backup tool.
Step 2 Choose View > Database. In the All Databases group box, choose the desired database. In the
Description group box, the details of the database are displayed, including Database Name,
Size, Used Size, and Created Time.

System
----End
9.5 Setting the Backup Device

The settings of backup device are related to the configuration of backup file path, tape drive,
and other important configuration. Therefore, set the backup device correctly before you perform
backup.
Context
l Parameters backup device name and device type are defined by the system automatically.
No modification is allowed.
l If a tape is the backup device and needs to be initialized, in the Backup Devices group box,
select the tape to be initialized. Click Initialize Tape.
l In the Sybase or SQL Server database, only the initialized tape can be used for backup. In
the Sybase or SQL Server database, the data is backed up onto the tape incrementally. For
example, if the capacity of the tape is 20 GB, 100 MB was used for the first backup. Then
the rest space is used for the second backup, with the previous data reserved.
Procedure
Step 2 Choose Configuration > Backup Device to configure the backup device.

System
Step 3 In Backup Devices, select the backup device you want to change. You can select disk or
tape.
l If you select disk, click Modify. The following parameters are displayed.
Back up to Target backup path set by the user. The path must be an
absolute path. The default value is the backup path at the
same level with the installation path of the N2000
DMS.

System
Current backup path Actual backup path. The default value is the backup path
at the same level with the installation path of the N2000
DMS.
Generally, the value of Current backup path is the same
as that of Back up to.
l When an error occurs in the value of Back up to, the
value of Current backup path is automatically
switched to the default backup path the backup path
at the same level with the installation path of the
N2000 DMS.
l If the value of Back up to is restored, the value of
Current backup path is automatically switched to that
of Back up to.
After you modify the parameters, click Modify.

l If you select tape, click Modify. The following parameters are displayed.
Select a tape from Back up to. The default value is tape0.

After you modify the parameters, click Modify.
Step 4 In the prompt, click OK.
----End
Result
The information of the backup device is displayed in Description.
9.6 Setting the Database Set

Databases are backed up based on database sets. Therefore, before backing up databases, you
need to set database sets.

System
Context
l The name of a database can only contain letters, numbers, and underscores. The maximum
length of the name is 32 characters.
l The name of a database set must be unique. It contains only letters, numbers, underscores,
and hyphens, and cannot start with an underscore. The name cannot contain a special
character or start with an underscore. The maximum length of the name is 20 characters.
l When setting a database set, you are not allowed to select the filtered databases such as the
master database and the database with an illegal name.
l The name of a database set is case insensitive.
Procedure
Step 2 Choose Configuration > Database Set.
Step 3 Configure a database set:

l Add a database set.
1. Click Add and set the following parameters:
Database Set Name: Enter the name of the database set to be added.
Database For Selection: Including all the available databases in the server.
Selected Database: Displays all the databases in the database set.

System
2. Click or to select a database and add it to the database set. Click

or to delete the databases contained in the database set. After you
complete the settings, click Finish. In the confirmation dialog box, click OK. The
database set is displayed in the All Database Sets group box.
l Delete a database set.
In ALL Database Sets, choose the database set to be deleted. Click Delete. The details
related to the database set are displayed. Click Delete. In the confirmation dialogue box,
click OK. The database set is removed from the All Database Sets group box.
----End
9.7 Configuring the Timing Backup Policy

You can configure the timing backup period and the start time when you add, modify, or delete
the timing policy process.
Context
l The name of a timing backup policy must be unique. It consists of letters, numbers,
underscores, and hyphens. It cannot contain special characters, begin with an underscore,
or exceed 20 characters.
l If the specific date is last than the 28th of the month and this month does not have the
specific date, the timing backup fails.
Procedure
Step 2 Choose Configuration > Auto Backup Policy.
Step 3 Configure the backup policy.

System
l Add a timing backup policy.

1. Click Add. In the Add Time Backup Policy group box, set the following parameters:
Time Policy Name: The name of the timing policy that need be added.
Backup Frequency: Day, Week or Month. If you choose Week in the check box,
select a specific day from Monday to Sunday in a week; if you choose Month,
select a specific date from 1 to 31 in the Every Month in the drop-down list.
Start Time: The start time for the backup, ranging from 00:00 to 23:00.
2. After setting the parameters, click Finish. A prompt is displayed, indicating that the
timing backup policy is added successfully. Click OK. The timing backup policy is
displayed in the All Timing Backup Policies group box.
l Modify a timing backup policy.
1. In All Timing Policies, choose a timing backup policy that need be modified. Click
Modify. In Modify Time Policy, set the backup frequency and backup start time.
2. Click Finish. A prompt is displayed, indicating that the timing backup policy is
modified successfully. After confirmation, the timing backup policy information is
refreshed.
l Delete a timing backup policy.
1. In All Timing Policies, choose a timing backup policy that need be deleted. Click
Delete.
The details related to the timing backup policy are displayed.
2. Click Delete.
A prompt is displayed, indicating that the timing backup policy is deleted successfully.
After confirmation, the timing backup policy is removed from All Timing Backup
Policies.
----End

System
9.8 Backing Up the N2000 DMS Database Manually

The database backup tool provides two manual backup modes: backup and bcpout. After you
set the parameters for manually backing up a database, the N2000 DMS starts the database
backup immediately.
Prerequisite
l The backup device and database set are configured.
l You have the right to back up the database.
l Only n (by default, n = 4) copies of data are allowed in the same database set. During the
manual backup, if the number of data copies in one database set reaches n, the system
prompts whether to delete the earliest data or not. During the timing backup, the earliest
data is deleted without any prompt. The number n can be configured in the
MaxBackupNumber field of diskbak.cfg which is located in the $N2000ROOT/server/
conf/dbback folder of the Solaris system. After the configuration file is modified, you need
to restart the database backup process so that the modification can take effect.
Context
l backup: To back up the data of the database to a data file.
l bcpout: To back up the data of the database user table to a data file. This method cannot be
used for common database backup.
l Use bcpout method to back up the data of the database set, it cannot contains an empty
users database table.
Procedure
Step 2 Choose Operation > Manual Backup.
Step 3 In Select Database Set to Backup, select the required database set, and then click Next.

System
Step 4 In Select Backup Device, select the destination backup device, and then click Next.
Step 5 In Select Backup Mode, select the backup mode.
Step 6 Click Start. The backup progress is displayed.
Step 7 When the backup succeeds, click OK.
----End

System
9.9 Configuring a Timing Backup Task

Timing backup indicates that the system backs up data automatically according to the backup
frequency set in the timing backup task.
Context
Configure the database set, timing backup policy, and backup device first and then configure
the timing backup task.
Procedure
Step 2 Choose Operation > Auto Backup Task.
Step 3 Configure the timing backup task.

l Add a timing task
1. Click Add. In Select Database Set, select the desired database set. Click Next.
2. In Select Time Backup Policy, select the desired backup policy. Click Next.
3. In the Select Backup Device group box, select the backup device, and then click
Finish. The system prompts that adding a timing task is successful. Click OK.
The backup task is displayed in All Time Backup Tasks.
l Delete a timing task
1. In All Time Backup Tasks, choose the timing backup task to be deleted. Click
Delete.
2. Details on the timing backup task are displayed. Click Delete. A dialog box is
displayed to prompt that the deletion is successful. Click OK.

System
The timing backup task disappears from All Time Backup Tasks.
----End
9.10 Querying Backup and Restoration Logs

This describes how to query backup and restoration logs. The backup and restoration operations
of the N2000 DMS databases are performed through the database backup tool. You can view
the operation records of the backup and restoration in the database backup tool.
Procedure
Step 1 Start the database backup tool and log in to the server to be configured.
Step 2 Choose View > Log on the menu bar, or in the navigation tree, click Log under View.
Step 3 In the Check log dialog box, set the following parameters:
l Log type: Select the type to be viewed from All, Backup, and Restore.
l Time range: Select the time range to be viewed from Recent Day, Recent Week, Recent
Month, Recent Three Months, Recent Six Months,Recent Year, and Recent All.
Step 4 Click Next.
In the Operation Log dialog box, you can view information about the logs as required.
----End
9.11 Expanding an N2000 DMS Database

This describes how to expand an N2000 DMS database. Through this function, according to the
scale of the communication networks managed by the N2000 DMS, you can manually expand
the databases that have insufficient spaces for data or logs. You can expand databases through
the GUI or command lines.
9.11.1 Through the GUI
You can expand the data space and the log space of the N2000 DMS databases through the
System Monitor Client.
9.11.2 Through the Command Line
When you want to expand a database in a drive other than the N2000 DMS database installation
drive, you need to expand the database through the command line.
9.11.1 Through the GUI

You can expand the data space and the log space of the N2000 DMS databases through the
System Monitor Client.
Context
l When the usage reaches 80% of the database space, the database must be expanded. It is
recommended to expand the database to 1.5 times the original space.
l You cannot expand a system database.

System
l The expanded data space or log space cannot exceed 500 MB.
l With the help of the GUI, you can expand the database only in the database installation
drive.
Procedure
Step 1 Log in to the N2000 DMS through the System Monitor Client.
Step 2 Click the Database tab.
The N2000 DMS databases are listed.
Step 3 In the database list, right-click one or more records and choose Expand.
Step 4 In the Database Expansion dialog box, fill in Data Expansion Space(MB) and Log Expansion
Space(MB).
Step 5 Click OK.

The data space and log space are expanded.
----End
9.11.2 Through the Command Line

When you want to expand a database in a drive other than the N2000 DMS database installation
drive, you need to expand the database through the command line.
Context
l The following describes the procedure for expanding databases, taking the FaultDB
expansion for example.
l Suppose you need to expand the FaultDB to a new device with 512 MB, and the path is /
new_data/.
Procedure
Step 1 Run the following commands to initialize the device.
isql>disk init name='new_fault_dev',physname= '/new_data/fault_new_dev.dat',vdevno =

101,size= 256000
isql>disk init name='new_fault_log_dev',physname= '/new_data/

fault_new_log_dev.dat',vdevno = 101,size= 256000
NOTE
l You can customize the file names of the disk and database. The unit of the parameters is 2 KB.
l vdevno is the device number. Each database device has a unique device number. You can run the isql>
sp_helpdevice command to query the used vdevno. device_number in the returned message is the device
number.
Step 2 Run the following commands to expand the database.
isql>alter database FaultDB on new_fault_dev = 512
isql>alter database FaultDB log on new_fault_log_dev = 512

System
NOTE
The unit of the parameters are MB.
----End
9.12 Clearing an N2000 DMS Database

This describes how to clear an N2000 DMS database. When a database has a large amount of
data, you can dump the data in the database to files. The dumped data is removed from the
database. Then, you can clear the N2000 DMS database to ensure the performance and normal
running of the database.
9.12.1 Setting Auto Dump of Alarms

After you set alarm auto dump, the history alarms on the N2000 DMS are saved to a specified
file.
9.12.2 Setting Auto Dump of Events
After you enable auto event dump, the events on the N2000 DMS are automatically saved to a
specified file.
9.12.5 Dumping Alarms Manually
You can dump the history alarms to a specific file manually.
9.12.6 Dumping Events Manually
You can manually dump events to a file.
9.12.9 Clearing the Transaction Log Space
This describes how to clear the log space of a database. Through this function, you can ensure
sufficient database space for the running of the system. Thus, you can avoid the abnormal running
of the database caused by insufficient log space.
9.12.1 Setting Auto Dump of Alarms

After you set alarm auto dump, the history alarms on the N2000 DMS are saved to a specified
file.

System
Prerequisite
Context
l Auto dump applies to only history alarms.
l After dump, the source data is deleted from the database immediately.
l By default, the N2000 DMS can store a maximum of 50,000 current alarms, and 1,000,000
history alarms. You can modify the maximum number of the history alarms to the maximum
of 2,000,000.
l By default, auto periodic dump starts between 1:00 and 2:00 in the morning; auto overflow
dump starts automatically in 10 minutes after the number of alarms reaches the maximum.
Procedure
Step 2 In the Dump Settings dialog box, in the Dump Settings navigation tree, select Alarm Data.
Step 3 Set the parameters for alarm dump.
Step 4 Click OK.
----End
9.12.2 Setting Auto Dump of Events

After you enable auto event dump, the events on the N2000 DMS are automatically saved to a
specified file.

System
Prerequisite
Context
l After dump, the source data is deleted from the database immediately.
l By default, the N2000 DMS can store a maximum of 120,000 event alarms. You can modify
the maximum number of the event alarms to the maximum of 1,000,000.
l By default, auto periodic dump starts between 1:00 and 2:00 in the morning; auto overflow
dump starts automatically in 10 minutes after the number of alarms reaches the maximum.
Procedure
Step 2 In the Dump Settings dialog box, in the Dump Settings navigation tree, select Event Data.
Step 3 Set the parameters for event dump.
Step 4 Click OK.
----End


System
Prerequisite
Procedure
Step 2 In the Dump Settings navigation tree, select Security Logs.
Step 6 Click OK.
----End

Prerequisite

System
Procedure
Step 2 In the Dump Settings navigation tree, select Operation Logs.
Step 6 Click OK.
----End
9.12.5 Dumping Alarms Manually

You can dump the history alarms to a specific file manually.
Prerequisite
Context
After dump, the source data is deleted from the database immediately.
Procedure

System
Step 2 In the Manual Dump dialog box, in the Manual Dump navigation tree, select Alarm Data.
Step 3 Specify the file path and the file format.

NOTE
The file path is similar to the file path for automatically dumping alarm data, if you want to change this
file path, you need to modify the related parameter in System > Database > Dump Settings.
Step 4 Specify the start time and end time of the alarms.
NOTE
If the start time and end time are not specified, all the history alarms in the database are dumped.
Step 5 Click Query to query the alarms that meet the dump conditions.
Step 6 Click Dump. In the Confirm dialog box, click Yes.

NOTE
If you need not dump files, click Delete Dump File. Once the files are deleted, you cannot restore them.
----End
9.12.6 Dumping Events Manually

You can manually dump events to a file.
Prerequisite

System
Context
After dump, the source data is deleted from the database immediately.
Procedure
Step 2 In the Manual Dump dialog box, in the Manual Dump navigation tree, select Event Data.
Step 3 Specify a file path and file format.

NOTE
The dumping path is similar to the file path for automatically dumping event data, if you want to change this
file path, you need to modify the related parameter in System > Database > Dump Settings.
Step 4 Specify the start time and end time of the events.
NOTE
If you do not set the start time and end time, all the events in the database are dumped.
Step 5 Click Query to query the events that meet the dump conditions.
Step 6 Click Dump. In the Confirm dialog box, click Yes.

NOTE
If you do not need a dump file, click Delete Dump File. Once the file is deleted, you cannot restore it.
----End

System

Prerequisite
Procedure
Step 2 In the Manual Dump navigation tree, select Security Logs.
Step 3 In the Generation Time of Security Logs group box, set the dump condition.
Step 5 Click Dump.
Step 6 Click Close.
----End


System
Prerequisite
Procedure
Step 2 In the Manual Dump navigation tree, select Operation Logs.
Step 3 In the Generation Time of Operation Logs group box, set the dump condition.
Step 5 Click Dump.
Step 6 Click Close.
----End
9.12.9 Clearing the Transaction Log Space

This describes how to clear the log space of a database. Through this function, you can ensure
sufficient database space for the running of the system. Thus, you can avoid the abnormal running
of the database caused by insufficient log space.
Context
This operation uses few system resource and does not affect the system.

System
Procedure
Step 2 Open a terminal window to switch to the root user.
Run the following commands:
$su
Password:<root user password>
Step 3 Run the following commands to clear the log space of the database:
# isql -SN2000DBServer -Usa -P<sa user password>
1>dump tran <database name> with no_log
2>go
For example, run the following commands to clear the log space of the master database:
1>dump tran master with no_log
2>go
----End

System
Administrator Guide - Solaris 10 Managing N2000 DMS Files and Disks
10 Managing N2000 DMS Files and Disks
About This Chapter
This describes how to manage file systems and disks of the N2000 DMS server and client.
10.1 N2000 DMS File Systems

This describes the file systems of the N2000 DMS server and client.
10.2 Viewing Disk Usage of the N2000 DMS Server
This section describes how to view the disk usage of the N2000 DMS server on the System
Monitor Client or with the command. By viewing the disk usage, you can know the free space
size of the disk and the proportion between the occupied space size and the free space size.
10.3 Clearing Disk Space
Clearing disk space in time helps the N2000 DMS client and server to run normally.

System
10 Managing N2000 DMS Files and Disks Administrator Guide - Solaris
10.1 N2000 DMS File Systems

This describes the file systems of the N2000 DMS server and client.
10.1.1 N2000 DMS Server File System

After you install the N2000 DMS server, the program files and directories are created in the
installation path. If you know well about these files and folders, you can better manage the file
system of the N2000 DMS server.
10.1.2 N2000 DMS Client File System
After you install the N2000 DMS client, the program files and directories are created in the
system of the N2000 DMS client.
10.1.1 N2000 DMS Server File System

After you install the N2000 DMS server, the program files and directories are created in the
system of the N2000 DMS server.
Table 10-1 shows the installation directory structure after the N2000 DMS server is installed.
Table 10-1 Directory structure of the N2000 DMS server
Path Description
backup folder at the same level with To store the configuration file of the database
$N2000ROOT backup tool.
$N2000ROOT/server To store the files and subdirectories of the N2000

DMS server.
$N2000ROOT/server/action To store the processing file of the N2000 DMS

alarm event.
$N2000ROOT/server/bin To store the executable files of the N2000

DMS server.
$N2000ROOT/server/conf To store the configuration files of the N2000

DMS server.
$N2000ROOT/server/debug To store the dynamic debugging information

files of the N2000 DMS server.
$N2000ROOT/server/lib To store the dynamic link libraries of the N2000

DMS server.
$N2000ROOT/server/dump To store alarm dump files, log dump files, and

device log dump files.
$N2000ROOT/server/installscript To store the database script.
$N2000ROOT/server/license To store product license files of the N2000

DMS.

System
Path Description
$N2000ROOT/server/license_SS_bak To store the backup license file of the N2000

DMS.
$N2000ROOT/server/log To store the logs output by the N2000 DMS

server.
$N2000ROOT/server/log/devlog To store the device logs that are synchronized

from the devices.
$N2000ROOT/server/plugin To store the plug-ins invoked by the N2000

DMS.
Typically, a plug-in is developed by the relative
application product and invoked by the N2000
DMS. For example, the dynamic link library of
the fault module is stored in the trapdll folder
under this path.
$N2000ROOT/server/res To store the resource files for the N2000 DMS

server.
The resource files are sorted by language. The
en_US directory stores the English resource
files, and the zh_CN directory stores the Chinese
resource files.
$N2000ROOT/server/sybase To store the files of the Sybase client.
$N2000ROOT/server/script To store the script programs for system

maintenance like data backup.
$N2000ROOT/server/tools To store the files of the database expansion tool.
$N2000ROOT/client To store the related files of the N2000 DMS

client.
$N2000ROOT/installscript To store the files used to install the N2000

DMS.
$N2000ROOT/jre To store Java Runtime Environment (JRE).
$N2000ROOT/uninstall To store the files used to uninstall the N2000

DMS.
$N2000ROOT/update To store the configuration file of the client

upgrade tool.
$N2000ROOT/upgrade To store the client package files consistent with

the server version for auto upgrade of the client.
10.1.2 N2000 DMS Client File System

After you install the N2000 DMS client, the program files and directories are created in the
system of the N2000 DMS client.

System
Table 10-2 shows the installation directory structure after the N2000 DMS client is installed.
Table 10-2 Directory structure of the N2000 DMS client
Path Description
$N2000ROOT/client To store the files and subdirectories of the N2000

DMS client.
$N2000ROOT/client/dbback To store the library files, the configuration files, and the
help files of the database backup tool.
$N2000ROOT/client/dtd To store the files used to define the format of the XML
configuration file.
$N2000ROOT/client/help To store the N2000 DMS help files.
$N2000ROOT/client/installscript To store the scripts used to complete the installation of

the N2000 DMS.
$N2000ROOT/client/lib To store the library files of the N2000 DMS client.
$N2000ROOT/client/log To store the logs generated by the N2000 DMS client.

The log is named as follows:
module_logYYYY_MM_DD_HH_MM_SS.0.txt
For example,
security_log2006_11_02_10_02_51.0.txt.
When the exported log files of a module reach a specific
number, the client packages these log files in the zip
format.
$N2000ROOT/client/putty Stores files related to the secure shell (SSH) remote

login software.
$N2000ROOT/client/report The report folder is the default folder for you to save a
file as another file.
$N2000ROOT/client/style To store the configuration files of the client, such as the

user configuration file.
$N2000ROOT/client/sysmoni To store the configuration files, log files, and help files
of the System Monitor client.
$N2000ROOT/client/tools To store the tools. At present, it stores a device agent

access tool.
$N2000ROOT/client/tracefile To store the debug information of the client.
10.2 Viewing Disk Usage of the N2000 DMS Server

This section describes how to view the disk usage of the N2000 DMS server on the System
Monitor Client or with the command. By viewing the disk usage, you can know the free space
size of the disk and the proportion between the occupied space size and the free space size.

System
Procedure
l Using the System Monitor Client
1. Log in to the System Monitor Client.
2. Choose the Disk tab.
The disk usage of the server is displayed.
l Using a Command
1. Log in to the Solaris as root.
2. Run the following command to check the disk usage of the active and standby nodes:
# df -k
The information similar to the following is displayed:

Filesystem kbytes used avail capacity
Mounted on
/dev/vx/dsk/bootdg/rootvol
9260525 3990038 5177882 44% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 10831272 8 10831264 1% /var/run
dmpfs 10831264 0 10831264 0% /dev/vx/dmp
dmpfs 10831264 0 10831264 0% /dev/vx/rdmp
swap 10833744 2480 10831264 1% /tmp
/dev/vx/dsk/bootdg/ftp
4133838 9 4092491 1% /ftp
/dev/vx/dsk/bootdg/opt
30983686 661511 30012339 3% /opt
----End
10.3 Clearing Disk Space

Clearing disk space in time helps the N2000 DMS client and server to run normally.
10.3.1 Cleaning Up the N2000 DMS Server Disk Space

To ensure sufficient disk space for the server, you need to delete the outdated and useless backup
files and trash files to clean up the disk space. Otherwise, the insufficiency of disk space may
cause a running error of the N2000 DMS server.
10.3.2 Cleaning Up the N2000 DMS Client Disk Space
To ensure the sufficient disk space for running the client, you need to clean up the disk space
by deleting useless backup files and trash files. Otherwise, the insufficiency of disk space may
cause a running error of the N2000 DMS client.
10.3.1 Cleaning Up the N2000 DMS Server Disk Space

To ensure sufficient disk space for the server, you need to delete the outdated and useless backup
files and trash files to clean up the disk space. Otherwise, the insufficiency of disk space may
cause a running error of the N2000 DMS server.
Context
Do not delete useful files, especially operating system files. Otherwise, the N2000 DMS server
may not run stably.

System
Procedure
Step 1 Log in to Solaris as the root user.
Step 2 Delete the outdated and useless files:
l Delete the outdated and useless alarm dump files. The default path is $N2000ROOT/
server/dump.
l Delete the outdated and useless log dump files. The default path is $N2000ROOT/server/
dump.
l Delete the outdated and useless database backup files. The default folder is backup at the
same level with $N2000ROOT.
l Delete the outdated and useless N2000 DMS running logs. The default path is
$N2000ROOT/server/log.
l Delete other outdated and useless files, such as installation files and patch files of earlier
versions.
----End
10.3.2 Cleaning Up the N2000 DMS Client Disk Space

To ensure the sufficient disk space for running the client, you need to clean up the disk space
by deleting useless backup files and trash files. Otherwise, the insufficiency of disk space may
cause a running error of the N2000 DMS client.
Context
Before you delete a file, ensure that the file is no more needed. Otherwise, the N2000 DMS
client may not run stably.
Procedure
Step 1 Empty the Trash.
Step 2 Delete the files in %N2000ROOT%\client\log.
Step 3 Delete other useless files.
----End

System
Administrator Guide - Solaris 11 N2000 DMS Routine Maintenance
11 N2000 DMS Routine Maintenance
About This Chapter
This describes how to perform routine maintenance. Through routine maintenance, you can
detect and rectify potential faults to ensure the secure, stable, and reliable running of the N2000
DMS.
11.1 Suggestions on Secure Running

To ensure that the N2000 DMS runs properly and stably, maintain the N2000 DMS according
to suggestions on secure running.
11.2 Routine Maintenance List
Routine maintenance can be classified into three types based on the maintenance phases or
intervals, namely, the daily maintenance, weekly maintenance, and monthly maintenance. Refer
to the routine maintenance list when maintaining the N2000 DMS.
11.3 Daily Maintenance
This describes daily maintenance. Through daily maintenance, you can know the running
statuses and trends of the devices and network in real time, and effectively process the accidental
events. Daily maintenance include viewing N2000 DMS alarms, server resource statuses, and
process statuses.
11.4 Weekly Maintenance
This describes weekly maintenance. Through weekly maintenance, you can find the defects such
as invalid functions and low performances, and take proper measures to rectify the defects and
prevent potential accidents. You can also back up the database to protect data. Weekly
maintenance include viewing the hard disk usage of the server, viewing the Solaris error logs,
backing up system files, and backing up databases.
11.5 Monthly Maintenance
This describes how to ensure the normal status of the device, and the secure, stable, and reliable
running of the system. Monthly maintenance include cleaning the user rights, checking logs,
and cleaning the disk space of the N2000 DMS server.

System
11 N2000 DMS Routine Maintenance Administrator Guide - Solaris
11.1 Suggestions on Secure Running

To ensure that the N2000 DMS runs properly and stably, maintain the N2000 DMS according
to suggestions on secure running.
l Configure a Uninterrupted Power Supply (UPS) on the N2000 DMS workstation to protect
the system against hardware corruption, system crash and data loss due to unexpected power
failure.
l Any time you need to power off the N2000 DMS workstation, follow the sequence: exit
the N2000 DMS, exit the database, and shutdown the workstation. Do not directly run
halt (in Solaris) or switch off the power of the hardware, or irretrievable damages might
occur to the N2000 DMS.
l Ensure that the client and the System Monitor is always running after the operating system
is started so that the status of the N2000 DMS can be monitored.
l Maintain a hierarchy of accounts for the N2000 DMS. Each account is available and
accessible to responsible personnel only.
11.2 Routine Maintenance List

Routine maintenance can be classified into three types based on the maintenance phases or
intervals, namely, the daily maintenance, weekly maintenance, and monthly maintenance. Refer
to the routine maintenance list when maintaining the N2000 DMS.
Table 11-1shows the maintenance tasks.
Table 11-1 Routine maintenance list
Maintenance Routine Maintenance Task Maintenance Tool

frequency
Daily Viewing N2000 DMS alarms N2000 DMS client
Collecting statistics on alarms N2000 DMS client
Viewing server resource status N2000 DMS system monitoring

client
Viewing database status N2000 DMS system monitoring

client
Viewing process status N2000 DMS system monitoring

client
Monitoring user operations N2000 DMS client
Weekly Viewing server disk usage N2000 DMS system monitoring

client
Viewing Solaris error log -
Backing up system files Tape management tool

System
Maintenance Routine Maintenance Task Maintenance Tool

frequency
Backing up databases periodically N2000 DMS database backup tool
Backing up databases manually N2000 DMS database backup tool
Viewing server time -
Monthly Deleting user rights N2000 DMS client
Collecting statistics on alarms N2000 DMS client
Viewing logs N2000 DMS client
Cleaning up N2000 DMS server -

disk space
11.3 Daily Maintenance

This describes daily maintenance. Through daily maintenance, you can know the running
statuses and trends of the devices and network in real time, and effectively process the accidental
events. Daily maintenance include viewing N2000 DMS alarms, server resource statuses, and
process statuses.
11.3.1 Monitoring Process Status

11.3.2 Monitoring Database Status
11.3.3 Monitoring the Status of the N2000 DMS Server Performance
N2000 DMS server.
11.3.4 Monitoring Hard Disk Status
DMS server.
11.3.6 Viewing N2000 DMS Alarms
You need to check for the N2000 DMS alarms periodically to ensure that the N2000 DMS works
properly. Handle the alarms that are not handled.
11.3.7 Checking Exception Logs of the OS
This describes how to detect and find abnormal information of the OS by checking exception
logs of the OS. Thus, the OS runs normally.
11.3.8 Checking Database Logs

System
This describes how to check the log information of database.
11.3.1 Monitoring Process Status

Context
In routine maintenance, you need to view the process information only. Do not perform other
operations because N2000 DMS services may be affected in case of misoperations.
Procedure
Step 2 Click the Process tab. The details of all processes to be monitored are displayed in a table on
the Process tab.
l Refresh: To refresh all the information of the selected process.
l Start Process: To start the selected process.
l Stop Process: To stop the selected process.
l Start mode: To change the start mode of the selected process.
NOTE
There are three start modes:
l Automatic: The process restarts automatically after it exits exceptionally.
l Manual: The process does not restart automatically after it exits exceptionally. You need to restart it
manually.
l Details: To query the process information.
----End
11.3.2 Monitoring Database Status

Context
When the database usage exceeds the alarm threshold, the System Monitor sends an alarm to
Procedure
Step 2 Click the Database tab. The managed databases are listed in detail.

System
l Refresh: To refresh the information on the selected databases.
l Expand: To expand the data space or log space of selected databases.
----End
11.3.3 Monitoring the Status of the N2000 DMS Server Performance

N2000 DMS server.
Procedure
Step 2 Click the System Resource tab.

The system information of the N2000 DMS server is listed in detail.
Step 3 From the list, right-click one or more records and choose Refresh to refresh the system resource
information of the N2000 DMS server.
----End

DMS server.
Context
Procedure
information.
----End

Prerequisite

System
Context
l Any users can monitor only their own operation logs.
l The group administrator can monitor operation logs of the users in the managed group.
l The global group administrator can monitor operation logs of all users.
l The user operations can be monitored only when the monitoring window is displayed.
Procedure
Step 1 Choose System > Monitor User Operations.
Step 2 In the Monitor User Operations dialog box, click Filter. Set User, Client, Result, and
Operation Level.
Step 3 Click OK.

The operations matching the conditions are displayed in the user operation checklist.
----End
11.3.6 Viewing N2000 DMS Alarms

You need to check for the N2000 DMS alarms periodically to ensure that the N2000 DMS works
properly. Handle the alarms that are not handled.
Prerequisite
To perform the browse operation, you must be an NMS user with the fault watcher authority or
higher. To perform the acknowledgement or clearance operation, you must be an NMS user with
the fault operator authority or higher.

System
Procedure
Step 1 Choose Fault > Browse Current Alarm.
Step 2 In the Filter[Unnamed] dialog box, set the filter conditions. Click OK.
NOTE
l You can also click import, choose the exist filter template to import the filter condition to the Filter
[Unnamed] dialog box.
l If the startup template for browsing the current alarms is set, the Filter[Unnamed] dialog box is not
displayed. Instead, the alarms that meet the filter conditions set in the startup template are displayed
directly.
Step 3 In the query result table, click a field to sort the results.
NOTE
l If you click Alarm Source or Alarm Source Type, the NEs are grouped by NE ID. If you click a
different field, the alarm records are sorted in alphabetical order.
l If you click of a field, the results are sorted by this field in ascending order. If you click , the results
are sorted in descending order. Switch between and to sort the result in ascending or descending
order.
Step 4 In the query result table, right-click an alarm and do as follows:

l Choose Select All to select all the records in the query result table.
l Choose Root Alarms. In the Root Alarms dialog box, query the root alarms of the selected
alarm.
l Choose Correlative Alarms. In the Correlative Alarms dialog box, query the correlative
alarms of the selected alarm.

System
l Choose Remark to set the remarks of the alarm.

l Choose Maintenance Experience to set the maintenance experience.
l Choose Mask. In the Confirm dialog box, click Yes to mask the selected alarm.
l Choose Acknowledge to acknowledge the alarm.
NOTE
If the alarm is unacknowledged and cleared, it is moved to the history alarm database.
l Choose Clear to clear the alarm.
NOTE
l If the alarm is unacknowledged and uncleared, the alarm status changes to Unack&Cleared after
clearance.
l If the alarm is acknowledged and uncleared, it is moved to the history alarm database.
l Choose Locating to Topo Object to locate the topology object that raises the alarm.
l Choose Save Selected Records to save the selected records to a file.
Step 5 Select Display latest alarms to query new alarms in real time.
NOTE
If you deselect Display latest alarms, pay attention to the following:

l When alarms that meet the filter conditions are generated, the Refresh button turns to red. Click
Refresh to update records.
l You can also click a field in the table to sort and refresh alarm records.
l The status change in alarm acknowledgement and clearance does not cause that the Refresh button
becomes red. This avoids that the Refresh button is in red for a long time.
Step 6 Click the buttons in the lower part of the browse window:
l Click Refresh to synchronize the latest alarms to the NMS interface according to the filter
conditions.
l Click Acknowledge to acknowledge the selected unacknowledged alarms.
l Click Clear to clear the selected uncleared alarms.
l Click Print to print the alarm information.

System
l Click Save As to save the alarm information as a file. You can also specify the rows to be
saved.
----End
11.3.7 Checking Exception Logs of the OS

This describes how to detect and find abnormal information of the OS by checking exception
logs of the OS. Thus, the OS runs normally.
Context
Information about exceptions that affect the OS running does not exist.
Procedure
$ su
Password:<password of the root user>
Step 3 Run the following command to access the directory of the log files:
# cd /var/adm
Step 4 Run the following command to view the OS log files with the file names beginning with
message:
# more messages

Sep 18 09:49:27 nms143 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Sep 18 09:49:27 nms143 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/ devinfo@0
Sep 19 11:21:38 nms143 htt_props[23937]: [ID 684959 user.error] Attempt to run
htt_props independeltly...
Sep 19 11:32:21 nms143 reboot: [ID 662345 auth.crit] rebooted by root
----End
Postrequisite
If the exception log information exists, rectify the fault according to the error information in the
log file. You can also contact Huawei technical personnel.
11.3.8 Checking Database Logs

This describes how to check the log information of database.
Context
Information about errors that affect the database running is not in the log file.

System
Procedure
$ su

Step 3 Run the following command to access the directory of the log files:
Step 4 Run the following commands to view the log files of the primary database and backup database
respectively.
# more N2000DBServer.log
# more N2000DBServer_back.log

00:00000:00000:2005/09/19 12:18:51.79 kernel Use license file /opt/sybase/SYSAM
-1_0/licenses/license.dat.
00:00000:00000:2005/09/19 12:18:51.79 kernel Feature ASE_SERVER is over drafted
273112632 times.
00:00000:00000:2005/09/19 12:18:51.79 kernel Using config area from primary mas ter
device.
----End
Reference Index
Information about errors that affect the database running is not in the log file.
Postrequisite
If the abnormal log information exists, rectify it according to the error information in the log
file. You can also contact Huawei technical personnel.
11.4 Weekly Maintenance

This describes weekly maintenance. Through weekly maintenance, you can find the defects such
as invalid functions and low performances, and take proper measures to rectify the defects and
prevent potential accidents. You can also back up the database to protect data. Weekly
maintenance include viewing the hard disk usage of the server, viewing the Solaris error logs,
backing up system files, and backing up databases.

DMS server.
11.4.2 Checking the Disk Status of the N2000 DMS Server
This describes how to check the disk status of the N2000 DMS server and process the exceptions.
11.4.3 Checking the N2000 DMS Server Time

System
This describes how to view the N2000 DMS server time through the date command to ensure
the consistency of the system time and the actual time.
11.4.4 Manually Backing Up an N2000 DMS Database
This describes how to manually back up data in an N2000 DMS database. You can perform the
manual backup operation when the load of the N2000 DMS server is low.
11.4.5 Backing Up Databases Periodically
When a periodic backup condition is set in advance, the N2000 DMS will automatically back
up the databases at the specified time.

DMS server.
Context
Procedure
information.
----End
11.4.2 Checking the Disk Status of the N2000 DMS Server

This describes how to check the disk status of the N2000 DMS server and process the exceptions.
Procedure
$ su

Step 3 Run the following command to view the physical status of the server disk:
# iostat -E
----End
Reference Index
In the Solaris OS, no hardware errors exist in the information.

System
For example, run the iostat -E command to view hard disk information. Check whether Hard
Errors of sd1 is 0. If Hard Errors is 0, the physical status of the hard disk is normal.
sd1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: SEAGATE Product:
ST373307LSUN72G Revision: 0507 Serial No: 3HZ9JBYN000 07518 Size: 73.40GB
"73400057856 bytes" Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
Exception Handling
If the hard disk fails, refer to the relevant operation guides provided by Sun Microsystems Inc
to replace the disk.
11.4.3 Checking the N2000 DMS Server Time

This describes how to view the N2000 DMS server time through the date command to ensure
the consistency of the system time and the actual time.
Procedure
Step 2 Run the following command to view the server time:
$ date
Fri Nov 19 21:37:01 CST 2007
----End
Postrequisite
If the server time is incorrect, do as follows:
l Change the server time
l Check and change the running status of the NTP service
11.4.4 Manually Backing Up an N2000 DMS Database

This describes how to manually back up data in an N2000 DMS database. You can perform the
manual backup operation when the load of the N2000 DMS server is low.
Prerequisite
l The related backup device and database set are configured.
l The backup device is configured.
l The value n is set through the MaxBackupNumber field in the diskbak.cfg configuration
file. The diskbak.cfg configuration file is in the $N2000Root/server/conf/dbback path.
Procedure
Step 1 Start the database backup tool and log in to the server to be configured.
Step 2 Choose Operation > Manual Backup on the menu bar.

System
Step 3 In the Select Database Set to Backup area, select the database set to be backed up, and then
click Next.
Step 4 Select the backup device, and then click Next.
l If the backup device is disk, click Next to perform Step 5.
l If the backup device is tape, perform Step 6.
Step 5 Select the backup mode:
NOTE
l backup: In this mode, the data is backed up from the database to a specified file.
l bcpout: In this mode, the data in the database user table is backed up to a specified file. You cannot
select this mode for the general database backup.
Step 6 Click Start to back up data to the specified path.

Step 7 After the backup is complete, click OK in the dialog box that is displayed.
----End
11.4.5 Backing Up Databases Periodically

When a periodic backup condition is set in advance, the N2000 DMS will automatically back
up the databases at the specified time.
Context
You have to configure database set, time backup policy and backup device before you can
configure a periodic backup task.
Procedure
Step 2 Choose Operation > Auto Backup Task, and configure the timing backup task by adding or
deleting.
l Add a timing task
1. Click Add, in the Select Database Set, select the desired database set. Click Next.
2. In the Select Time Backup Policy, select the desired backup policy. ClickNext.
3. In the Select Backup Device group box, select the backup device, and then click
Finish.
A dialog box is displayed to prompt that the addition is successful. Click OK. The backup
task is displayed in All Time Backup Tasks.
l Delete a timing task
1. In All Time Backup Tasks, choose the timing backup task to be deleted. Click
Delete.
2. Details on the timing backup task are displayed. Click Delete. A dialog box is
displayed to prompt that the deletion is successful. Click OK.
The timing backup task disappears from All Time Backup Tasks.
----End

System
11.5 Monthly Maintenance

This describes how to ensure the normal status of the device, and the secure, stable, and reliable
running of the system. Monthly maintenance include cleaning the user rights, checking logs,
and cleaning the disk space of the N2000 DMS server.
11.5.1 Checking Hardware Devices of the N2000 DMS

This describes how to check the hardware devices of the N2000 DMS to prevent damages to the
server hardware and peripherals.
11.5.2 Backing Up the N2000 DMS Files
This describes how to periodically back up the N2000 DMS files. The backup files can be used
to restore the system in emergency maintenances.
11.5.3 Deleting N2000 DMS User Rights
You should delete user rights periodically to ensure the security of the N2000 DMS.
11.5.5 Collecting Monthly Alarm Statistics
Take the N2000 DMS as an example. You can collect statistics on monthly alarms, and then
classify these alarms by Severity or Day.
11.5.6 Checking System Logs
This describes how to check N2000 DMS system logs. System logs store the system running
information, such as the data loading information about the start of a system. System logs can
help you to locate faults.
11.5.7 Checking the Ambient Temperature and Fan Status
This describes the ambient temperature and fan status required by the N2000 DMS server.
11.5.8 Cleaning Up the Disk Space of the N2000 DMS Server
This describes how to clean up the disk space of the N2000 DMS server. Deleting outdated
backup files and useless files leaves more free disk space for the N2000 DMS. This can avoid
abnormal running of the N2000 DMS caused by insufficient disk space.
11.5.9 Checking the Equipment Room Environment
This describes the required temperature, humidity, and cleanness in the equipment room.
11.5.1 Checking Hardware Devices of the N2000 DMS

This describes how to check the hardware devices of the N2000 DMS to prevent damages to the
server hardware and peripherals.
Procedure
Step 1 Check whether the server hardware is damaged.
Step 2 Check whether the DVD-ROM runs normally.
Step 3 Check whether the tape drive runs normally.
----End

System
Postrequisite
If the server hardware and peripherals are damaged, contact the manufacturer to repair or replace
the damaged devices.
11.5.2 Backing Up the N2000 DMS Files

This describes how to periodically back up the N2000 DMS files. The backup files can be used
to restore the system in emergency maintenances.
Procedure
Step 2 Run the following command to back up the files of the Solaris OS to a tape:
# ufsdump -0ucf /dev/rmt/0n<files to be backed up>
NOTE
In the command, /dev/rmt/0n refers to the backup tape.
It is recommended to back up at least the following files of the Solaris OS:
l /etc/hosts
l /etc/netmasks
l /etc/nodename
l /etc/hostname.* (The asterisk (*) is the name of the network adapter, such as ce0. You can
view the name through the ifconfig -a command.)
l /etc/net/ticlts/hosts
l /etc/net/ticots/hosts
l /etc/net/ticotsord/hosts
l /etc/profile
l /etc/rc3
l /etc/rc3.d
l /n2kuser
Step 3 Run the following command to back up the files of the Sybase database to a tape:
# ufsdump -0ucf /dev/rmt/0n /opt/sybase
Step 4 Run the following command to back up the N2000 DMS files to a tape:
# ufsdump -0ucf /dev/rmt/0n /opt/n2000
----End
11.5.3 Deleting N2000 DMS User Rights

You should delete user rights periodically to ensure the security of the N2000 DMS.

System
Procedure
Step 1 Log in to the N2000 DMS as admin.
Step 3 In the NMS User Management window, delete the rights of the N2000 DMS users.
Follow the rules below to delete user rights:
l Delete discarded user accounts in time. When a device is added, assign proper rights to the
user of this device.
l Assign user rights by user group and operation set. Add users with the same rights to the
same group. To ensure that the NMS runs properly without performances being affected,
avoid assigning rights to users one by one.
----End

Prerequisite
Procedure
Set Password.
NOTE
box, enter the current password and your new password. Click OK.
----End
11.5.5 Collecting Monthly Alarm Statistics

Take the N2000 DMS as an example. You can collect statistics on monthly alarms, and then
classify these alarms by Severity or Day.
Context
l When you collect alarm statistics, you can set the common statistical conditions provided
by the N2000 DMS as statistical templates. You can also specify a statistical template as
the startup template. But only one statistical template can be specified as the startup
template.
l If you have not specified the startup template, you can choose Fault > Alarm Statistics
on the N2000 DMS client. Then a statistical condition dialog box is displayed.

System
l If you have specified the startup template, the statistical condition dialog box is not
displayed. The N2000 DMS collects alarm statistics according to the statistical conditions
set in the startup template.
Procedure
Step 1 Choose Fault > Alarm Statistics.
Step 2 In the Statistical Condition[Unnamed] dialog box, set the statistical conditions. Because only
the alarm statistics of the current month are collected, you should choose Month from Row
heading and set the generated time in the Generated Time box. You also can set other statistics
conditions as required. Click OK after setting all the conditions. At that time, the statistics results
are displayed in list form.
NOTE
l If there is a desired template for collecting monthly alarms, you can click Import in the Statistical Condition
[Unnamed] dialog box. In the Import dialog box, select the template and click Import. The statistical
conditions in the template are imported to the Statistical Condition[Unnamed] dialog box. Click OK.
l If you have specified a startup template, the Statistical Condition[Unnamed] dialog box is not displayed.
To collect statistics on monthly alarms, you need to click Statistical Condition for collecting statistics on
monthly alarms in the Alarm Statistics.
Step 3 Click Statistics by Template and select Save As. In the Save As dialog box, enter the template
name. Click OK. The statistical conditions set in the previous step are saved as a template.
When you collect the monthly alarm statistics next time, you can use this template by performing
the import operation.
Step 4 Click Statistics by Template and select Open. In the Open dialog box select the template
created in the previous step. Click Set Startup Template. This template is specified as the
startup template.
When you open the Alarm Statistics window again, the statistical results according to the
statistical conditions set in the startup template is displayed.
----End
11.5.6 Checking System Logs

This describes how to check N2000 DMS system logs. System logs store the system running
information, such as the data loading information about the start of a system. System logs can
help you to locate faults.
Context
The system running logs are stored in the following paths:
$N2000ROOT/server/conf/log, $N2000ROOT/server/log, and $N2000ROOT/server/

debug.
Procedure
Step 1 Open log files in the paths that stores the system logs.
Step 2 View the related log files.

System
If exception information exists in a log, locate the faults according to the relevant prompt
information.
----End
11.5.7 Checking the Ambient Temperature and Fan Status

This describes the ambient temperature and fan status required by the N2000 DMS server.
Check the ambient temperature of an equipment room and the fan status according to the
following table.
Table 11-2 Checking the ambient temperature of the equipment room and the fan status
Item Specification
Temperature 15C-35C
Cleanness of the fan frame The fan frame is clean and free of dusts.
Fan running status The fan rotates stably and freely.
11.5.8 Cleaning Up the Disk Space of the N2000 DMS Server

This describes how to clean up the disk space of the N2000 DMS server. Deleting outdated
backup files and useless files leaves more free disk space for the N2000 DMS. This can avoid
abnormal running of the N2000 DMS caused by insufficient disk space.
Context
Do not delete useful files. In particular, do not delete OS files. Deleting system files may result
in system crash. It is recommended not to delete the files generated in recent three days.
Procedure
$ su
Step 3 Delete the alarm files that were automatically dumped and outdated (Default Path:
$N2000ROOT/server/dump).
NOTE
Compare the creation time and the modification time of a file with the current system time. If a file was
created long time ago and has not been used for a long time, the file is outdated.
Step 4 Delete the unnecessary core files and stack files (Default Path: $N2000ROOT/server/conf).
Step 5 Delete the temporary files in the /var/tmp directory.

System
Step 6 Delete the log files that were automatically dumped and outdated (Default Path: $N2000ROOT/
server/dump).
Step 7 Delete the performance data files that were automatically backed up and outdated (Default Path:
$N2000ROOT/server/HisDataBackup).
Step 8 Delete the database files that were automatically backed up and outdated (Default Path:
$N2000ROOT/backup).
Step 9 Delete the DC backup files that are outdated. The default path is the initial FTP server path set
on the N2000 DMS. You can choose System > System Parameters Setting > NMS FTP/TFTP/
SFTP Server Setting on the client to view the initial path.
Step 10 Delete the N2000 DMS running log files that were outdated (The default path is $N2000ROOT/
server/conf/log).
Step 11 Delete other files that were outdated, such as program installation files and patch installation
files of previous versions.
----End
11.5.9 Checking the Equipment Room Environment

This describes the required temperature, humidity, and cleanness in the equipment room.
Check the temperature, humidity, and cleanness of the equipment room according to the
following table.
Item Specification
Temperature 15C-35C
Humidity 30%-60%
Cleanness Clean, no dusts
Regulate the temperature and humidity of the equipment room, improve the tightness of the
doors and windows, and clean the room periodically.

System
Administrator Guide - Solaris 12 N2000 DMS Emergency Maintenance
12 N2000 DMS Emergency Maintenance
About This Chapter
This describes the preparations for emergency maintenance, the operation guide to emergency
maintenance, and the test after maintenance.
12.1 Emergency Maintenance Overview

This describes emergency maintenance. Through emergency maintenance, you can restore the
system to the latest status before the collapse. Then, you can minimize the service outage time
and the loss.
12.2 Emergency Maintenance Flow
This describes the work flow for emergency maintenance when the system collapses.
12.3 Emergency Maintenance Preparations
This describes the preparations for emergency maintenance.
12.4 Guide to Emergency Maintenance of the N2000 DMS Server
This describes how to perform emergency maintenance.
12.5 Checking the System Recovery Results
This describes how to check the system recovery results. After all data is restored, restart the
Solaris OS, and then check the status of the Sybase and N2000 DMS services.
12.6 Seeking for Technical Support from Huawei
This describes how to obtain technical support from Huawei when a fault cannot be rectified.

System
12 N2000 DMS Emergency Maintenance Administrator Guide - Solaris
12.1 Emergency Maintenance Overview

This describes emergency maintenance. Through emergency maintenance, you can restore the
system to the latest status before the collapse. Then, you can minimize the service outage time
and the loss.
Emergency maintenance is not a common maintenance method. When the system collapses, you
need to reinstall the OS and database, and restore the backup files and data such as the Solaris
system file, Sybase file, N2000 DMS file, and N2000 DMS data to the normal status before the
crash.
12.2 Emergency Maintenance Flow

This describes the work flow for emergency maintenance when the system collapses.
Figure 12-1 shows the process for emergency maintenance of a server.

System
Figure 12-1 Emergency maintenance flowchart
Start
Preparations
Reinstall the Solaris OS

and patch
Reinstall the Sybase

database and patch
Reinstall the N2000 DMS
Import the system and

database data
Restore the program and

data file
Check the system

recovery result
System Yes
recovery
No
Contact Huawei technical
support
End

System
CAUTION
Preparations include backing up the Solaris program files, Sybase data files, N2000 DMS
program files, and N2000 DMS data files. You need to routinely back up these files so that you
can restore them when the system collapses. If the files are not backed up before the collapse,
you can only restore the system to the initial condition and the data before the collapse cannot
be restored.
12.3 Emergency Maintenance Preparations

This describes the preparations for emergency maintenance.
12.3.1 Backing Up the System Files

This describes how to back up system files, including the Solaris system files, Sybase files, and
N2000 DMS files.
12.3.2 Backing Up the N2000 DMS Data
This describes how to back up the N2000 DMS data.
12.3.3 Checking Necessary Items
This describes necessary items for emergency maintenance.
12.3.1 Backing Up the System Files

This describes how to back up system files, including the Solaris system files, Sybase files, and
N2000 DMS files.
For details, see 11.5.2 Backing Up the N2000 DMS Files.
12.3.2 Backing Up the N2000 DMS Data

This describes how to back up the N2000 DMS data.
You can periodically back up the system data by configuring the periodic backup policies and
tasks. It is recommended to back up the system data to a tape or the hard disk of another
workstation.
For details, see 9 Managing N2000 DMS Databases.
12.3.3 Checking Necessary Items

This describes necessary items for emergency maintenance.
Backup Tapes
Before performing the maintenance, you need to prepare the following backup tapes:
l The latest backup tape of the N2000 DMS data
l The latest backup tape of the N2000 DMS file
l The latest backup tape of the Sybase file
l The latest backup tape of the Solaris system file

System
NOTE
Generally, all data and files can be backed up to one tape. You can prepare one tape.
Installation Disks
You may reinstall the OS and database when performing the emergency maintenance. Thus, you
need to prepare the following installation disks:
l SUN Solaris 10 (08/07), Multilingual Version, SPARC Platform Edition and Huawei Patch
7.0.3 (DVD)
l Sybase12.5.2 for Solaris(SPARC) installation disk and Sybase Patch EBF13325
l N2000 DMS software (disk)
References
You need to prepare the iManager N2000 DMS Datacomm Network Management System
Installation Guide - Solaris.
12.4 Guide to Emergency Maintenance of the N2000 DMS

Server
This describes how to perform emergency maintenance.
12.4.1 Reinstalling OS
This describes how to rectify a fault by reinstalling the OS.
12.4.2 Reinstalling Database
This describes how to rectify a fault by reinstalling the database.
12.4.3 Reinstalling the N2000 DMS Software
This describes how to rectify a fault by reinstalling the N2000 DMS software.
12.4.4 Restoring the Solaris System Files
This describes how to restore the Solaris system files.
12.4.5 Restoring the Sybase Files
This describes how to restore the Sybase files.
12.4.6 Restoring the N2000 DMS Files
This describes how to restore the backup N2000 DMS files to the restored OS.
12.4.7 Restoring the N2000 DMS Data
This describes how to restore the N2000 DMS data.
12.4.1 Reinstalling OS
This describes how to rectify a fault by reinstalling the OS.
Procedure
Step 1 To reinstall OS, refer to the iManager N2000 DMS Datacomm Network Management System
Installation Guide - Solaris.
----End

System
12.4.2 Reinstalling Database

This describes how to rectify a fault by reinstalling the database.
To reinstall the Sybase database, refer to the iManager N2000 DMS Datacomm Network
Management System Installation Guide - Solaris.
12.4.3 Reinstalling the N2000 DMS Software

This describes how to rectify a fault by reinstalling the N2000 DMS software.
After reinstalling the Solaris OS and Sybase database, you need to reinstall the N2000 DMS
software. For details, refer to the iManager N2000 DMS Datacomm Network Management
System Installation Guide - Solaris.
12.4.4 Restoring the Solaris System Files

This describes how to restore the Solaris system files.
Restore the backup Solaris system files to the relevant directory. For the system files to be
restored, see 12.3.1 Backing Up the System Files.
Use the tape drive to restore the Solaris system files. Run the following command:
# ufsrestore rf /dev/rtm/0n
12.4.5 Restoring the Sybase Files

This describes how to restore the Sybase files.
Restore the backup Sybase files to the relevant directory. For the system files to be restored, see
12.3.1 Backing Up the System Files.
Use the tape drive to restore the Sybase files. Run the following command:
12.4.6 Restoring the N2000 DMS Files

This describes how to restore the backup N2000 DMS files to the restored OS.
Prerequisite
Before restoring the N2000 DMS files, stop all N2000 DMS services.
Procedure
Step 1 Log in to the N2000 System Monitor.
Step 2 Choose System > Stop All NMS Service.
Step 3 In the dialog box, click OK.
All N2000 DMS services are shut down.
Step 4 To use the tape drive to restore the N2000 DMS files, run the following command:

System
Step 5 To shut down the Sybase service with the isql tool, run the following commands:
# cd /opt/sybase/OCS-12_5/bin
# ./isql -SN2000DBServer -Usa -P<sa password>
2> go
1> shutdown
2> go
Step 6 Run the following commands to restart the OS:

# sync;sync;sync;sync;sync;sync
# shutdown -y -g0 -i6
----End
12.4.7 Restoring the N2000 DMS Data

This describes how to restore the N2000 DMS data.
Use the N2000 DMS Database Backup Tool to restore the N2000 DMS data and database data.
For details, see 9 Managing N2000 DMS Databases.
12.5 Checking the System Recovery Results

This describes how to check the system recovery results. After all data is restored, restart the
Solaris OS, and then check the status of the Sybase and N2000 DMS services.
12.5.1 Checking the N2000 DMS Service Status
This describes how to check the N2000 DMS service status after the system recovers.
12.5.2 Checking the Sybase Service Status
This describes how to check the Sybase service status after the system is restored.
12.5.3 Checking Data Synchronization
This describes how to check data synchronization.
12.5.1 Checking the N2000 DMS Service Status

This describes how to check the N2000 DMS service status after the system recovers.
Procedure
Step 1 Run the following commands to check whether the N2000 DMS service is started:
# ps -ef|grep mdp

root 1360 1352 0 17:47:38 ? 0:00 /opt/n2000/server/conf/../bin/mdp
# ps -ef|grep EmfSysMoniDm

System

root 1352 1 0 17:47:31 ? 0:01 ./EmfSysMoniDm
If the information of the EmfSysMoniDm and mdp processes is displayed, the N2000 DMS
service is started.
Step 2 Log in to the N2000 System Monitor to view the statuses of all N2000 DMS processes.
Step 3 Log in to the N2000 DMS client to view the restoration of the N2000 DMS.
----End
12.5.2 Checking the Sybase Service Status

This describes how to check the Sybase service status after the system is restored.
Procedure
Step 1 Run the following commands to check whether the Sybase service is started:
# ./showserver
If the following information is displayed, the server and the backup server of the database are
started normally.
UID PID PPID C STIME TTY TIME CMD root 895 894 0
12:48:41 ? 0:32 /opt/sybase/ASE-12_5/bin/dataserver -d/opt/sybase/data/
master.dat -e/opt/sybase root 901 900 0 12:48:41 ? 0:00 /opt/sybase/
ASE-12_5/bin/backupserver -e/opt/sybase/ASE-12_5/install/N2000DBSer
Step 2 Run the following commands to check whether you can set up the database connection:
# ./isql -SN2000DBServer -Usa -P<sa password>
If the following information is displayed, the database server can be connected and the database
is normal.
1>
You can run the quit command to quit the isql program.
----End
12.5.3 Checking Data Synchronization

This describes how to check data synchronization.
Context
After the N2000 DMS server is started, the data is synchronized between the mirrored disk and
the data disk.
Procedure

System
Step 2 Run the following commands to check whether the disk mirroring is synchronizing data:
# cd /usr/sbin
# metastat -t|grep progress
If the following information is displayed:

Resync in progress: 50 % done
The data is being synchronized and the number indicates the progress of the data synchronization.
If no information is displayed, the data synchronization is complete.
----End
12.6 Seeking for Technical Support from Huawei

This describes how to obtain technical support from Huawei when a fault cannot be rectified.
If you have a technical problem and cannot find a solution to it from this manual, please contact
the Huawei customer service center.
You can contact our technical support personnel through telephone, fax, or email.
l Tel: 0755-28560000 4008302118
l Fax: 0755-28560111
l Email: support@huawei.com
You can also obtain the latest technical documents from http://support.huawei.com.

System
Administrator Guide - Solaris 13 N2000 DMS Fault Handling
13 N2000 DMS Fault Handling
About This Chapter
This chapter describes the procedure for handling a fault, information collecting, fault
identifying, fault handling, and suggestions on N2000 DMS troubleshooting.
13.1 Procedure for Handling a Fault

The procedure for handling a fault consists of three phases: collecting information, identifying
the fault, and rectifying the fault. After receiving an alarm, you need to collect fault information,
analyze the fault cause, identify the fault, and rectify the fault to restore the system.
13.2 Troubleshooting Precautions
Before troubleshooting, you must take the following precautions.
13.3 Discovering a Fault
This section describes the sources of the common faults. To reduce the service loss, you need
to discover and handle the fault in time.
13.4 Handling the N2000 DMS Alarm
If a fault leads to the N2000 DMS alarm, you can handle the fault according to the iMAP alarm
information.
13.5 Collecting Fault Information
A fault occurs on the N2000 DMS with various symptoms. It is difficult to correctly identify a
fault with limited information. Therefore, when a fault occurs, you need to collect the details
about the fault. This section describes how to collect fault information, and this helps you to
identify a fault efficiently.
13.6 Determining Fault Causes
Determining an alarm is the process of detecting the causes of the alarm. You can use certain
methods to analyze and compare the possible causes, and then determine the causes of the alarm.
13.7 Eliminating a Fault
This section describes how to eliminate a fault.
13.8 Checking Whether the Fault Is Cleared
After you clear a fault alarm on the N2000 DMS, you can search for the current alarms to see if
the fault persists. You can also monitor the server performance to check if the server works
properly.

System
13 N2000 DMS Fault Handling Administrator Guide - Solaris
13.9 Recording Alarm Maintenance Experiences

You can record the alarm maintenance experiences. When a similar alarm is raised, you can
refer to the alarm maintenance experiences so that the alarm can be cleared in time.

System
13.1 Procedure for Handling a Fault

The procedure for handling a fault consists of three phases: collecting information, identifying
the fault, and rectifying the fault. After receiving an alarm, you need to collect fault information,
analyze the fault cause, identify the fault, and rectify the fault to restore the system.
Flow Chart
Figure 13-1 shows the flow for handling a fault.
Figure 13-1 Flow for handling a fault

System
Procedure
The fault handling procedure shown in Figure 13-1 is described inTable 13-1.
Table 13-1 Fault handling procedure
1 Find out a fault. You need to find out and handle the fault in time to reduce
loss. For details, see 13.3 Discovering a Fault.
2 Check whether the If the fault leads to an N2000 DMS alarm, perform Step 3.
fault leads to an iMAP
alarm.
3 Handle the iMAP If the fault leads to an N2000 DMS alarm, handle the alarm
alarm according to the according to the operation guide. For details, see 13.4
operation guide. Handling the N2000 DMS Alarm. If the fault is not
rectified after the alarm disappears, perform Step 4.
4 Collect fault Check whether the fault is emergent according to the fault
information. information. See 13.5 Collecting Fault Information.
5 Check whether the If the fault is emergent, perform Step 6. Otherwise, perform
fault is emergent. Step 7.
6 Perform emergency Perform emergency maintenance to reduce loss.

maintenance.
7 Find out the fault Determine the fault cause according to the collected fault
cause. information. See13.6 Determining Fault Causes.
8 Rectify the fault. Rectify the fault by analyzing the fault cause. See13.7
Eliminating a Fault.
9 Check whether the Check whether the fault is rectified completely. See 13.8
fault is rectified. Checking Whether the Fault Is Cleared.
10 Contact the Huawei Contact the Huawei technical support personnel if the fault
technical support persists.
personnel.
11 Record the alarm After the fault is rectified, record the fault handling
maintenance experience in the alarm knowledge base for future
experience. reference. See 13.9 Recording Alarm Maintenance
Experiences.
13.2 Troubleshooting Precautions

Before troubleshooting, you must take the following precautions.
l Record all the information about a fault. Do not delete any data or log.
l Back up the configuration and the data before you make any change.

System
l When you rectify a fault of the N2000 DMS, ensure that this does not affect the running
of the NEs.
13.3 Discovering a Fault

This section describes the sources of the common faults. To reduce the service loss, you need
to discover and handle the fault in time.
The fault can be discovered in the following ways:
l In routine maintenance, monitor the alarms on the N2000 DMS client.
l In routine maintenance, a service exception occurs, but no alarm is generated.
l After receiving a fault reported from the user, check whether there is any alarm on the
N2000 DMS client.
13.4 Handling the N2000 DMS Alarm

If a fault leads to the N2000 DMS alarm, you can handle the fault according to the iMAP alarm
information.
13.4.1 Port Connection Interrupted Between NMS and Command Line Device
13.4.2 CPU Alarm of the NMS Server
13.4.3 Hard Disk Alarm of the NMS Server
13.4.4 NMS Server Physical Memory Alarm
13.4.5 NMS Server Virtual Memory Alarm
13.4.6 NMS Server Database Data Space Alarm
13.4.7 NMS Server Database Transaction Log Space Alarm
13.4.8 Availability of the NMS Server Service Alarm
13.4.9 Illegal Login Alarm
13.4.10 Trap Receiver Disconnection
13.4.11 NMS NE License Alarm
13.4.12 Avalanche Alarm
13.4.13 The Number of Records in the Database Table Reaches the Threshold
13.4.14 Switch to the Slave Syslog Server
13.4.15 Failed to Connect the Syslog Server
13.4.16 NMS Client Exits Abnormally
13.4.17 Sending the Remote Notification SMS Gateway Message Fails

System
13.4.1 Port Connection Interrupted Between NMS and Command

Line Device
Description
When a network fault occurs or the number of connections at the port of the command line device
reaches the maximum, the NMS is disconnected from the command line device. In this case, the
fault module raises a disconnection alarm.
Attribute
Alarm Severity Alarm Type
Major Running
Impact on the System

The disconnection disables the N2000 DMS to monitor the device status. The data generated on
the device, such as alarm data, cannot be passed to the N2000 DMS.
Possible Causes
l The network is faulty.
l The port connections of the command line device reach the maximum number.
Procedure
Step 1 Check whether the connection between the command line device and the N2000 DMS server is
normal.
Step 2 Check whether the connection number of the port of the device is maximum. If yes, release some
connections.
----End
13.4.2 CPU Alarm of the NMS Server

Description
The CPU usage exceeds a threshold (85% by default) for a long time. The system continuously
samples ten CPU usage values. If all values are greater than the threshold, a CPU alarm is
generated. You can set the threshold in System > Monitor setting on the monitor client. In
normal cases, when the NMS is processing a large number of data, the CUP usage may become
high. However, if the CPU usage is more than 85% for a long time (for example, for 20 minutes),
the system is abnormal.
Attribute
Major Running

System

l The high CUP usage causes the slow speed of system running. And the N2000 DMS speed,
interface refresh speed, and the processing function may be reduced.
l Some operations time out due to the delay in acquiring the CPU usage.
Possible Causes
l The N2000 DMS operators are performing query operations which require a large number
of data.
l The N2000 DMS service processes are performing busy tasks on the server.
l The memory shortage leads to frequent system dispatch.
l The specified alarm threshold for the usage of the N2000 DMS CPU is too small.
Procedure
Step 1 Close the processes irrelevant to the N2000 DMS.
Step 2 Close some clients that are not used.
Step 3 Pause all operations on the N2000 DMS. Resume after the alarm is cleared.
Step 4 Adjust the alarm threshold for the usage of the N2000 DMS CPU.
----End
13.4.3 Hard Disk Alarm of the NMS Server

Description
The usage of the disk space exceeds a threshold. When the usage of the disk space exceeds a
specified threshold (90% by default), the system monitor server sends an alarm to the fault server.
You can set the threshold by choosing System > Monitor setting in the system monitor
client window.
Attribute
Major Running

When the disk space in the N2000 DMS partition is full, the N2000 DMS process can not record
running logs any more. If the database locates in the disk, the database operation most probably
fails.
Possible Causes
l There is a large number of data and data records.
l The initial disk partition is small. And the N2000 DMS partition is far from being enough.
l The hard disk space is too small to store a large number of data.

System
l Users save irrelevant files in the N2000 DMS installation directory.

l The specified alarm threshold for the usage of the N2000 DMS disk space is too small.
Procedure
Step 1 Delete redundant files which are irrelevant to the N2000 DMS. In the Solaris system, run the
rm -rf command to delete files and directories. Do not delete the contents in the N2000 DMS
directory or in the database installation directory.
Step 2 Check whether the dump files in $N2000ROOT/server/dump(Solaris) occupy a large space.
If yes, you can either delete the dump files or back them up in another memory device. The
deletion of the dump file does not impact system running.
Step 3 Enlarge the disk space. If the disk space where the N2000 DMS is located in shortage, consider
enlarging the disk space.
Step 4 Adjust the alarm threshold for the usage of the N2000 DMS disk space.
----End
13.4.4 NMS Server Physical Memory Alarm
Description
The memory usage exceeds a threshold. When the usage of the physical memory exceeds a
specified threshold (95% by default), the system monitor server sends alarms to the faulty server.
You can set the threshold in the System > Monitor setting on the system monitor client.
Attribute

Major Running

l High memory usage will make the system running speed and the N2000 DMS responding
speed low.
l In case of system memory shortage, the N2000 DMS processes can not work properly.
Possible Causes
l Physical memory is too small.
l NMS processes occupy large percentage of the system memory.
l The processes irrelevant to the N2000 DMS are started.
l NMS operators are performing the operations which require a large number of data.
l The specified alarm threshold for the usage of the N2000 DMS memory is too small.

System
Procedure
Step 1 Enlarge the physical memory. In case of memory shortage, the physical memory needs to be
enlarged. You are recommended to enlarge the memory to more than 512 MB.
Step 2 Analyze the processes that occupy large memory. If the memory occupied by a process keeps
increasing, the process may be in error.
NOTE
l On the System Monitor Client, click the Process tab. You can view the memory usage by the N2000
DMS process.
l On Windows, you can view the memory usage on the Process tab of Windows Task Manager.
l On Solaris, you can view the memory usage through the process management application.
Step 3 Close the processes irrelevant to the N2000 DMS.
Step 4 Pause all N2000 DMS operations. Resume after the alarm is cleared.
Step 5 Adjust the alarm threshold for the usage of the N2000 DMS memory.
----End
13.4.5 NMS Server Virtual Memory Alarm
Description
When the system monitors that the virtual memory of the operating system is insufficient, it
notifies the alarm module to raise a major alarm.
Attribute
Major Running

The operating system and the NMS run slowly.
Possible Causes
l The number of programs running on the server is large.
l Some programs have been running for a long time and cannot release the occupied virtual
memory space in time.
l The size of the virtual memory set for the operating system is small.
Procedure
Step 1 Check the usage of virtual memory and stop unnecessary processes.
Step 2 Check the usage of virtual memory and restart the processes occupying a large virtual memory
space.

System
Step 3 Increase the size of virtual memory.

NOTE
For details on how to check the usage of virtual memory and how to set the size of virtual memory, refer to
related operating system manuals.
----End
13.4.6 NMS Server Database Data Space Alarm
Description
If the usage of the data space exceeds the threshold (95% by default), the N2000 DMS raises an
alarm. You can set the threshold by choosing System > Monitor Settings in the System Monitor
Client window.
Attribute

Major Running

Database operations fail if the usage of the data space keeps increasing and is close or equal to
100%.
Possible Causes
l Too many alarm data records exist.
l The data space specified when you install the N2000 DMS is too small.
l The specified alarm threshold for the usage of the data space is too small.
Procedure
Step 1 In the System Monitor Client window, on the Database tab, right-click the database that needs
to be expanded to increase the data space. Select Expand from the shortcut menu and enter a
value in MB to specify the expanded space.
Step 2 Adjust the alarm threshold for the usage of the N2000 DMS data space.
----End
13.4.7 NMS Server Database Transaction Log Space Alarm
Description
The usage of the database log space exceeds the threshold. If the usage of the database log space
exceeds the specified threshold (80% by default), the N2000 DMS raises an alarm. You can set
the threshold by choosing System > Monitor Settings on System Monitor Client.

System
Attribute
Major Running

Operations relating to the log database fail when the usage of the log space keeps increasing and
is close or equal to 100%.
Possible Causes
l The log space assigned to the database is too small. You can view the size and use rate of
the log space in the current database through the Database tab in the System Monitor
Client window.
l The specified alarm threshold for the usage of the N2000 DMS database log space is too
small.
Procedure
Step 1 To increase the database log space, you can right-click the database whose log space needs to
be expanded on the Database tab in the System Monitor Client window. Select Expand from
the shortcut menu and enter a value in MB to specify the expanded space.
Step 2 Adjust the alarm threshold for the usage of the N2000 DMS database log space.
----End
13.4.8 Availability of the NMS Server Service Alarm

Description
In the N2000 DMS, if a process exits abnormally, or a process still fails after the times of
automatic restarting reach the maximum, the system monitor server sends an alarm to the faulty
server.
Attribute
Major Running

Process failures prevent the system from providing corresponding service, and the availability
of the N2000 DMS is reduced.
Possible Causes
l A process exits abnormally.
l A process still fails after the times of automatic restarting reach the maximum.

System
Procedure
Step 1 Log in to the system monitor client.
Step 2 Click the Process information tab. Find the abnormal process. Right-click the process to restart
it.
----End
13.4.9 Illegal Login Alarm
Description
If a user tries to log in to the N2000 DMS using an invalid password for three times continuously,
the system security server sends an alarm to the faulty server.
Attribute

Critical Running

There is no impact on system running. To ensure security, the system security server sends an
alarm to the administrator to monitor the user.
Possible Causes
A user tries to log in to the N2000 DMS server using an invalid password for three times
continuously.
Procedure
Step 1 Check whether the user is an illegal user who wants to invade the N2000 DMS.
Step 2 If a legal user forgets the password, ask the user whether to initialize the password.
Step 3 If the user is a legal user, unlock the locked account.
----End
13.4.10 Trap Receiver Disconnection
Description
The alarm module contains two functional sub-modules: Trap receiver and fault process. The
Trap receiver receives SNMP alarms and analyzes them. The fault process handles the alarms
and receives the MML alarms. When an exception occurs in the connection between the Trap
receiver and the fault process, an alarm on Trap receiver disconnection is raised.

System
Attribute
Major Communication

When an alarm on Trap receiver disconnection occurs, it indicates that an exception occurs in
the connection between the Trap receiver and the fault process. The SNMP alarms received by
the Trap receiver cannot be sent to the fault process successfully. This leads to the loss of the
SNMP alarms.
Possible Causes
The Trap receiver process runs abnormally.
Procedure
Step 1 Restart the Trap receiver.
Log in to the N2000 DMS client. Choose Fault > Settings > Trap Receiver. In the Trap
Receiver dialog box, select the Trap receiver and click Restart.
Step 2 Restart the faulty process.
Log in to the System Monitor Client. Click the Process tab. Right-click the faulty process and
select Start Process from the shortcut menu.
----End
13.4.11 NMS NE License Alarm

Description
When the license usage exceeds the specific threshold, an alarm is generated. You can specify
the threshold in System > NE License Alert on the client. Set the threshold in the NE License
Alert dialog box.
Attribute
Major Running

If the number of the managed devices reaches the maximum, no new device can be added to the
N2000 DMS.
Possible Causes
The license usage exceeds the preset threshold.

System
Procedure
Step 1 On the client, choose System > NE License Alert. In the NE License Alert dialog box, check
the threshold of the NE license alarm. Change the threshold to a reasonable value if the original
one is too small.
Step 2 Check the threshold of the NE license alarm. If it is reasonable, choose Help > About on the
client. In the About dialog box, click the Lincense tab to check the usage of the network element
license. Apply for new license authorization based on the usage.
----End
13.4.12 Avalanche Alarm
Description
In the Fault > Settings > Correlation Rule window, click the Alarm/Event Frequecy
Analysis tab. Create a record and set the triggering condition. The NMS alarms that satisfy the
condition are called avalanche alarms.
Attribute

Major Running

This type of alarms aims to remind users to check the device which reaches the threshold.
Possible Causes
The current alarm or event reported to the N2000 DMS exceeds the preset threshold.
Procedure
Step 1 View the alarm information.
Step 2 Handle the fault according to the alarm information.
----End
13.4.13 The Number of Records in the Database Table Reaches the

Threshold
Description
The usage of some tables in the N2000 DMS server database exceeds the threshold.

System
Attribute
Minor Running

New data insertion and update fail when the usage of some tables in the N2000 DMS server
database reaches the threshold.
Possible Causes
l The specified threshold is too small.
l The specified database space is too small.
l The amount of the N2000 DMS data is too large due to long time running of the device.
Procedure
Step 1 Increase the threshold of the used database space.
(1) Log in to the N2000 DMS client.
(2) Choose System > Database > Dump Settings. The Dump Settings dialog box is displayed.
(3) In the Overflow Dump group box, increase Record threshold-crossing value(%).
Step 2 Expand the database space.

(1) Log in to the System Monitor Client.
(2) Click the Database tab.
(3) Right-click the database whose space is insufficient. Select Expand from the shortcut
menu.
(4) In the Database Expansion dialog box, specify the values of Data Expand Space(MB)
and Log Expand Space(MB). Click OK.
(5) In the displayed Confirm dialog box, click Yes. In the Expansion successful prompt, click
OK.
Step 3 Dump alarm or event data.

(2) Choose System > Database > Dump Manually. The Dump Settings dialog box is
displayed.
(3) In the Dump Manually dialog box, set the condition to dump alarm or event dump. See
and N2000 DMS Help for details.
----End
13.4.14 Switch to the Slave Syslog Server
Description
Switch to the slave system log server when connecting the master system log server fails.

System
Attribute
Minor Communication

When you switch from the master system log server to the slave system log server, the N2000
DMS cannot forward the operation log to the master system.
Possible Causes
The master system log server is not started or the network is faulty.
Procedure
Step 1 Check whether the master system log server works normally. For the details on checking whether
the master system log server is started and whether the master system log server works normally,
see the description of the third party system log server.
Step 2 Use the ping command to check whether the network where the master system log server resides
is connected normally. For example, ping the IP address or host name of the PC where the master
system log server resides.
----End
13.4.15 Failed to Connect the Syslog Server
Description
The N2000 DMS forwards the operation logs to the system log server regularly. When an
exception occurs in the connection between the N2000 DMS server and the master or slave
system log server, the N2000 DMS raises the Failed to connect the syslog server alarm.
Attribute
Major Communication

When the N2000 DMS server cannot forward the logs to the system log server, the logs are
stored in the NMS database. When the system log server is successfully connected, the N2000
DMS server continues to forward the accumulated logs to the system log server. If the
accumulated logs occupy too much database space, new logs cannot be written to the database.
Possible Causes
The master and slave system log servers are not started, or the network is faulty.

System
Procedure
Step 1 Check whether the master and slave system log servers work normally. For the details on
checking whether the master and slave system log servers are started and whether the servers
work normally, see the description of the third party system log server.
Step 2 Use the ping command to check whether the network where the master and slave system log
servers reside is normally connected. For example, ping the IP address or host name of the PC
where the system log server resides.
----End
13.4.16 NMS Client Exits Abnormally
Description
The security module forces out the client due to no handshake message being received for a long
time. "NMS client exits abnormally" is an event.
Attribute

Major Running

If you are forced to log out of the client and the number of the users that log in to the N2000
DMS with the same account is smaller than the maximum of online users, you need to wait three
minutes before a successful re-login. You can also directly log in to the N2000 DMS on another
client without waiting. The superuser admin can directly log in to the N2000 DMS on the client
that is installed to the same computer as the N2000 DMS server even if the number of the online
admin users reaches the maximum.
Possible Causes
The security module forces out the client due to no handshake message being received for a long
time.
Procedure
Step 1 Check and remove the causes of the exception:
(1) Check whether the Client well connects with the N2000 DMS Server.
(2) Check if the Client is closed abnormally like abnormal turnoff of the computer.
(3) Check whether the Client is forced to exit.
Step 2 Wait some time for logging in to theN2000 DMS Server again.
----End

System
13.4.17 Sending the Remote Notification SMS Gateway Message

Fails
Description
In SMS gateway mode, if no message can be sent due to a failure (for example, failed to connect
to the SMS gateway) on the NMS, an event is sent to the NMS.
Attribute
Major Running

None
Possible Causes
l The SMS gateway parameter is incorrect.
l Failed to connect to the SMS gateway.
Procedure
Step 1 View the remote notification log and find out the causes.
(2) Choose Fault > Browse Remote Notification Logs.
(3) In the Browse Remote Notification Logs window, search for the remote notification log
for the failure and find out the cause.
Step 2 Reset the SMS gateway parameter according to the remote notification log, and then test whether
the remote alarm notifications are sent successfully.
(2) Choose Fault > Settings > Remote Notification in the main menu.
(3) In the Remote Notification window, click Communication Settings.
(4) On the SMS tab of the Communication Settings dialog box, choose SMS gateway.
(5) Reset the SMS gateway parameter according to the remote notification log, click Test, and
then enter Mobile phone.
NOTE
The format is country code+mobile phone number. For example, if the country code is 86 (China) and the
mobile phone number is 13900001234, you need to enter 8613900001234.
----End
13.5 Collecting Fault Information

A fault occurs on the N2000 DMS with various symptoms. It is difficult to correctly identify a
fault with limited information. Therefore, when a fault occurs, you need to collect the details

System
about the fault. This section describes how to collect fault information, and this helps you to
identify a fault efficiently.
13.5.1 Collecting the Alarm Information
This section describes how to collect the alarm information on the N2000 DMS when a fault
occurs.
13.5.2 Collecting the Log Information
This section describes how to collect the log information when a fault occurs.
13.5.3 Collecting the Version Information
This section describes how to collect the version information when a fault occurs.
13.5.4 Collecting the Core File
This section describes how to collect the core file.
13.5.5 Collecting the Process Running Information
This section describes how to collect the process running information.
13.5.1 Collecting the Alarm Information

This section describes how to collect the alarm information on the N2000 DMS when a fault
occurs.
To collect the alarm information, do as follows:
1. When an alarm is generated on the N2000 DMS client, right-click a device node that
generates the alarm and choose Browse Alarm.
2. In the Current Alarms window, select an alarm.
The details about the alarm are displayed in the lower left part of the alarm list. The
suggestions for handling the alarm are displayed in the lower right part of the alarm list.
NOTE
For details, see the N2000 DMS Operation Guide.
13.5.2 Collecting the Log Information

This section describes how to collect the log information when a fault occurs.
N2000 DMS Log

The logs of the N2000 DMS are divided into client logs and server logs. Client logs collect
information of operations performed on the client. Server logs collect information of processes.
l The client logs are stored in $N2000ROOT/client/log. The log file is named the login time.
l The server logs are stored in $N2000ROOT/server/log, including the log files that are
related to the N2000 DMS and those generated by the N2000 DMS service processes.
You can analyze the server logs and client logs to identify the faulty process. If the faulty process
can be identified, submit the log files related to the faulty process for analysis. In the case of any
uncertainty, back up all the log files for further analysis and identification.
Database Log
The logs of the Sybase database are stored in $SYBASE/ASE-*/install/SYB_server.log and
$SYBASE/ASE-*/install/SYB_server_back.log.

System
NOTE
l The asterisk (*) stands for the Sybase database version.

l SYB_server is the name of the database instance, and SYB_server_back is the name of the backup database
instance.
13.5.3 Collecting the Version Information

This section describes how to collect the version information when a fault occurs.
OS Version
To view the versions of the Solaris OS and its patches, run the following command:
# uname -a
The information like the following is displayed:

l On Solaris 10
SunOS Server 5.10 Generic_118833-23 sun4u sparc
SUNW,Sun-Fire-V440
l On Solaris 8
SunOS Server 5.8 Generic_117350-02 sun4u sparc
SUNW, SUN-Blade-2500
Database Version
To view the versions of the Sybase and its patches, run the following commands:
# cd /opt/sybase/OCS-12_5/bin/
# ./isql -SSYB_server -Usa -Psybase
1> select @@version
2> go
The information like the following is displayed:

Adaptive Server Enterprise/12.5.3/EBF 13055 ESD#5/P/Sun_svr4/OS 5.8/ase1253/193
9/64-bit/FBO/Tue Dec 6 09:13:20 2005
NOTE
SYB_server is the name of the Sybase database instance.

Replace sybase with the password of the database superuser sa. OCS-12_5 varies with the version number.
N2000 DMS Version

If you can start the client of the N2000 DMS or the Sysmonitor, do as follows to view the client
and server versions.
l Client version: On the N2000 DMS client, choose Help > About. In the displayed dialog
box, view the versions on the Component tab.
l Server version: On the Sysmonitor, view the versions on the Component tab.
If you cannot start the client of the N2000 DMS or the Sysmonitor, do as follows to view the
versions in the directory.

System
l Client version: Run the more emf_package.xml command to view the

emf_package.xml file in the $N2000ROOT/client/style/defaultstyle/conf/about
directory.
l Server version: View the configuration files in $N2000ROOT/server/conf/about, such as
emfver.cfg.
You can run the following command in the command line interface to view the versions:
# more emfver.cfg
Device Version
If the N2000 DMS fault is related to a device, obtain the device version with one of the following
two methods:
l On the N2000 DMS client, right-click the device and choose the shortcut menu to view
device details or open the device panel. You can also view the host version and the board
version.
l Log in to the device in Telnet mode and run the related commands to view the host version
and the board version.
13.5.4 Collecting the Core File

This section describes how to collect the core file.
The processes of the N2000 DMS may be corrupted in the case of an exception. The core file
generated during the corruption is important for identifying a fault. You can collect the core file
for further analysis and identification in the case of a core dump.
The methods for obtaining the core file are as follows:
l Check whether the core file is located in the $N2000ROOT/server/conf directory.
If the core dump occurs on the N2000 DMS server, the core file may be generated in the
directory.
l Manually obtain the core file.
When the CPU or memory occupancy of a process is very high before the core dump occurs
in this process, you can manually dump the core file of the process.
Run the prstat command to view the ID (PID) of the process with high CPU occupancy
or high memory occupancy. Then run the gcore PID command to dump the core file of the
process.
The core.PID file is generated in the current operation directory. Save the file for
identifying the fault.
l Automatically obtain the core file.
Run the coreadm -e global -g /home/corefiles/core.%f.%p command to enable the function
of automatically obtaining the core file.

System
NOTE
l In the above command, the core file is saved in the /home/corefiles directory. You can specify
another directory according to the actual condition.
l As the core file is large, the specified directory and the $N2000ROOT cannot be placed on the
same partition. If there are two partitions / and /opt, you need to save the core file to the /opt
partition.
l You can also specify a fixed name for the core file. Thus, the latest core file overwrites the old
one, and the occupied space is not enlarged. This method, however, is not recommended because
the information may be lost when the core dump of several processes occurs.
To specify a fixed name, run the following command: coreadm -e global -g /home/corefiles/
coredump.
If core.* files exist in the directory of the core file, it indicates that the core dump occurs.
Save these files for further analysis.
Run the coreadms -d global -d process command to disable the function of automatically
obtaining the core file.
CAUTION
After collecting the core file, disable the function of automatically obtaining the core file.
Otherwise, the disk occupancy is large.
13.5.5 Collecting the Process Running Information

This section describes how to collect the process running information.
To check the process running status, do as follows:
1. Log in to the system monitoring client. On the Process tab, check whether the processes
in automatic start mode are running and whether they are restarted frequently.
2. Snap the interface of the system monitoring client and save it to the local computer.
13.6 Determining Fault Causes

Determining an alarm is the process of detecting the causes of the alarm. You can use certain
methods to analyze and compare the possible causes, and then determine the causes of the alarm.
The procedure for identifying faults is as follows:
1. Check whether an alarm is generated. If yes, handle it according to Alarm Details and
Handling Suggestion.
2. If no alarm is generated, check whether the fault is common. If so, handle it as a common
fault.
3. Try other methods to identify the fault or contact Huawei for technical support. See 13.5
Collecting Fault Information to collect the required fault information and prepare for
debugging before you contact Huawei.
13.7 Eliminating a Fault

This section describes how to eliminate a fault.

System
To eliminate a fault and restore the system, do as follows.
1. After receiving an alarm, follow the operation guides of the troubleshooting manual to
handle the fault.
2. If there is no alarm, handle the fault based on the maintenance experiences and measures
collected in the troubleshooting cases.
3. If you need assistance from on-site engineers, inform them of the fault and guide them in
handling the fault.
4. Check whether the fault is removed. If not, report it to the senior engineer.
Before contacting Huawei technical support engineers, do as follows to rectify the fault fast and
reduce loss:
l Collect necessary fault information.

l Prepare for the debugging.
Huawei technical support engineers may guide you to operate the device, so as to collect the
fault information and eliminate the fault.
The telephone number of Huawei Customer Care Center is 400-830-2118.
13.8 Checking Whether the Fault Is Cleared

After you clear a fault alarm on the N2000 DMS, you can search for the current alarms to see if
the fault persists. You can also monitor the server performance to check if the server works
properly.
13.8.1 Checking Whether the Alarm Is Cleared

After the N2000 DMS alarm is cleared, you can check whether the alarm caused by the current
fault is cleared by setting the alarm querying conditions.
13.8.2 Clearing Alarms Manually
Alarms may be missed due to some faults. For example, the N2000 DMS fails to communicate
with the device. In this case, if the device does not support alarm check, these alarms cannot be
cleared automatically and you need to clear the alarms manually.
13.8.3 Checking Whether Performance Specifications of the N2000 DMS Server Are Normal
After a fault of the N2000 DMS is rectified, check whether performance specifications of the
server are normal. Ensure that the N2000 DMS runs properly.
13.8.1 Checking Whether the Alarm Is Cleared

After the N2000 DMS alarm is cleared, you can check whether the alarm caused by the current
fault is cleared by setting the alarm querying conditions.
Procedure
Step 3 Set the alarm filtering conditions in the Filter dialog box, and then click OK.

System
The queried result is displayed in the Browse window under the tab. If you can find the current
alarms that match the conditions, it indicates that the fault is not cleared; otherwise, the fault is
cleared.
----End
13.8.2 Clearing Alarms Manually

Alarms may be missed due to some faults. For example, the N2000 DMS fails to communicate
with the device. In this case, if the device does not support alarm check, these alarms cannot be
cleared automatically and you need to clear the alarms manually.
Prerequisite
Context
You cannot roll back the operation of clearing an alarm.
Procedure
Step 2 In the Current Alarms window, right-click an alarm and choose Clear.
Step 3 In the Clear Alarms dialog box, click Yes.
----End
Result
l The N2000 DMS changes the status of an alarm to Cleared. The N2000 DMS records when
the alarm is cleared and who performs this task. It also refreshes the information in all
windows on the client and updates the data of the alarm panel and alarm box.
l If an alarm is acknowledged and cleared, it is dumped to the history database.

System
13.8.3 Checking Whether Performance Specifications of the N2000

DMS Server Are Normal
After a fault of the N2000 DMS is rectified, check whether performance specifications of the
server are normal. Ensure that the N2000 DMS runs properly.
Procedure
Step 1 Log in to the System Monitor.
Step 2 In the System Monitor window, check whether the performance index (such as, server process
or database) is normal.
----End
13.9 Recording Alarm Maintenance Experiences

You can record the alarm maintenance experiences. When a similar alarm is raised, you can
refer to the alarm maintenance experiences so that the alarm can be cleared in time.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > Maintenance Experience.
Step 2 In the Alarm/Event navigation tree, select an alarm, and then click Edit.
Step 3 In the Edit dialog box, enter the experience of handling this alarm.

System
NOTE
The alarm experience cannot exceed 250 characters.
Step 4 Click OK.
----End

System
Administrator Guide - Solaris 14 N2000 DMS FAQs
14 N2000 DMS FAQs
About This Chapter
This describes the common problems and solutions for maintaining the N2000 DMS.
14.1 Solaris OS
This describes common problems in the Solaris OS.
14.2 Sybase Database
This describes common problems of using the Sybase database.
14.3 N2000 DMS Software
This describes common problems of using the N2000 DMS software.
14.4 Security Management
This describes how to process the common problems in user right management and license
management.

System
14 N2000 DMS FAQs Administrator Guide - Solaris
14.1 Solaris OS
This describes common problems in the Solaris OS.
14.1.1 How to View the Concrete Version and Date of the Solaris OS
14.1.2 How to Start the Workstation from the CD-ROM
14.1.3 How to Rectify the Fault That the CD-ROM Cannot Be Ejected
14.1.4 How to Transfer Binary Files Through FTP
14.1.5 How to Rectify the Fault That the Executable Right of an Executable File Is Lost
14.1.6 How to Decompress the *.tar.gz File
14.1.7 How to Log in as the root User When Using the Telnet
14.1.8 How to Log in as the root User When Using FTP
14.1.9 How to View the Hardware Configuration of the Server
14.1.10 Starting the N2000 DMS as the root User Failed
14.1.11 Why Does the N2000 DMS Server Process Exit When I Press Ctrl+C
14.1.12 How to Set the ACL for a Server with Multiple Network Adapters
14.1.1 How to View the Concrete Version and Date of the Solaris
OS
Problem Description
When maintaining the Solaris OS, how to view the version and date of the Solaris OS?
Solution
Run the following command to view the version information of the Solaris OS:
# uname -a
Run the following command to view the release date of the Solaris OS:
# more /etc/release
14.1.2 How to Start the Workstation from the CD-ROM
Problem Description
How to start the Sun workstation through the CD-ROM?
Solution
Perform the following operations on the Sun workstation:

System
1. Power on the Sun workstation.

2. Press Stop+A after the startup interface is displayed. Then, the OK prompt is displayed.
3. Insert the Solaris installation disk, run the boot cdrom command and press Enter. The Sun
workstation starts from the CD-ROM.
14.1.3 How to Rectify the Fault That the CD-ROM Cannot Be

Ejected
Description
A CD-ROM is in the CD-ROM drive. When you use the eject command to open the drive, the
system prompts Device busy and the CD-ROM cannot be ejected.
Solution
1. Run the following command as the root user:
# /etc/init.d/volmgt stop
2. Press the eject button on the drive panel to take out the disk from the CD-ROM.
3. Run the following command to resume the drive:
# /etc/init.d/volmgt start
14.1.4 How to Transfer Binary Files Through FTP

Problem Description
How to transfer files through FTP?
Solution
To transfer binary files, such as the N2000 DMS installation file or the database interfaces file,
use the binary codes. Otherwise, the file size may change.
By default, FTP uses ASCII codes to transfer files. To transmit binary contents, you must run
the bin command to change the transmission mode to the binary codes.
Run the following command:
ftp> bin
14.1.5 How to Rectify the Fault That the Executable Right of an

Executable File Is Lost
Problem Description
When copying the executable file to the hard disk through FTP, you find that the executable
right of the executable file is lost.
Solution
Log in to the Solaris OS as the root user to change the right of the file.

System
The following takes the installation script of the N2000 DMS as an example. To change the right
of the file, run the following command:
# chmod +x setup.sh
To add the executable right to all files in the subdirectory, run chmod -R +x subdirectory
name.
14.1.6 How to Decompress the *.tar.gz File
Problem Description
The *.tar.gz file exists in a certain software installation package, and how to decompress the
file?
Solution
The following takes the abc.tar.gz file as an example. Run the following commands to
decompress the file:
# gunzip abc.tar.gz
# tar xvf abc.tar
14.1.7 How to Log in as the root User When Using the Telnet
Problem Description
By default, the root user cannot use the Telnet service after the Solaris OS is installed. How to
use the Telnet service as the root user?
Solution
Make sure that the Telnet service is started in the Solaris OS before login.
1. Log in to the Solaris OS as the root user, and run the following command to edit the /etc/
default/login file:
# vi /etc/default/login
2. Add the number sign (#) in front of CONSOLE=/dev/console to comment out this line.
#CONSOLE=/dev/console
3. Save it and quit.
It is recommended to undo the comment operation after using the Telnet service.
14.1.8 How to Log in as the root User When Using FTP
Problem Description
The root user cannot log in to the FTP server after the Solaris OS is installed. How to log in to
the FTP server as the root user?

System
Solution
By default, the root user cannot use the FTP service after the Solaris OS is installed. This ensures
the security of the system.
To use FTP as the root user, do as follows:
1. Log in to the OS as the root user, and run the following command to edit the /etc/ftpd/
ftpusers file:
# vi /etc/ftpd/ftpusers
2. Use the number sign (#) to comment out the root line. Save it and quit.
It is recommended to undo the comment operation after using the FTP service.
14.1.9 How to View the Hardware Configuration of the Server

Problem Description
When maintaining the Solaris server, how to view the hardware configuration of the server?
Solution
Run the following command to view the hardware configuration:
# prtdiag -v

System Configuration: Sun Microsystems sun4u Sun Fire V240
System clock frequency: 167 MHZ
Memory size: 4GB
==================================== CPUs ====================================

E$ CPU CPU
CPU Freq Size Implementation Mask Status Location
--- -------- ---------- --------------------- ----- ------ --------
0 1503 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 on-line MB/P0
1 1503 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 on-line MB/P1
================================= IO Devices =================================

Bus Freq Slot + Name +
Type MHz Status Path Model
------ ---- ---------- ---------------------------- --------------------
pci 66 MB pci108e,1648 (network)
okay /pci@1f,700000/network@2

okay /pci@1f,700000/network@2,1
pci 33 MB isa/su (serial)

okay /pci@1e,600000/isa@7/serial@0,3f8
pci 33 MB isa/su (serial)

okay /pci@1e,600000/isa@7/serial
pci 33 MB isa/rmc-comm-rmc_comm (seria+

okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
pci 33 MB pci10b9,5229 (ide)

okay /pci@1e,600000/ide@d
pci 33 PCI2 SUNW,XVR-100 (display) SUNW,375-3290

okay /pci@1e,600000/SUNW,XVR-100

System
pci 66 MB scsi-pci1000,21 (scsi-2)

okay /pci@1c,600000/scsi@2
pci 66 MB scsi-pci1000,21 (scsi-2)

okay /pci@1c,600000/scsi@2,1

okay /pci@1d,700000/network@2

okay /pci@1d,700000/network@2,1
============================ Memory Configuration ============================

Segment Table:
-----------------------------------------------------------------------
Base Address Size Interleave Factor Contains
-----------------------------------------------------------------------
0x0 2GB 4 BankIDs 0,1,2,3
0x1000000000 2GB 4 BankIDs 16,17,18,19
Bank Table:
-----------------------------------------------------------
Physical Location
ID ControllerID GroupID Size Interleave Way
-----------------------------------------------------------
0 0 0 512MB 0,1,2,3
1 0 1 512MB
2 0 1 512MB
3 0 0 512MB
16 1 0 512MB 0,1,2,3
17 1 1 512MB
18 1 1 512MB
19 1 0 512MB
Memory Module Groups:

--------------------------------------------------
ControllerID GroupID Labels Status
--------------------------------------------------
0 0 MB/P0/B0/D0
0 0 MB/P0/B0/D1
0 1 MB/P0/B1/D0
0 1 MB/P0/B1/D1
1 0 MB/P1/B0/D0
1 0 MB/P1/B0/D1
1 1 MB/P1/B1/D0
1 1 MB/P1/B1/D1
============================ Environmental Status ============================

Fan Status:
-------------------------------------------
Location Sensor Status
-------------------------------------------
F0 RS okay
F1 RS okay
F2 RS okay
MB/P0/F0 RS okay
MB/P0/F1 RS okay
MB/P1/F0 RS okay
MB/P1/F1 RS okay
PS0 FF_FAN okay
PS1 FF_FAN okay
Temperature sensors:
-----------------------------------------
-----------------------------------------
MB/P0 T_CORE okay

System
MB/P1 T_CORE okay

MB T_ENC okay
PS0 FF_OT okay
PS1 FF_OT okay
------------------------------------
Current sensors:
----------------------------------------
----------------------------------------
MB FF_SCSI okay
PS0 FF_OC okay
PS1 FF_OC okay
------------------------------------
Voltage sensors:
-----------------------------------
-----------------------------------
MB/P0 V_CORE okay
MB/P1 V_CORE okay
MB V_VTT okay
MB V_GBE_+2V5 okay
MB V_GBE_CORE okay
MB V_VCCTM okay
MB V_+2V5 okay
MB V_+1V5 okay
MB/BAT V_BAT okay
PS0 P_PWR failed
PS0 FF_POK okay
PS0 FF_UV okay
PS0 FF_OV okay
PS1 P_PWR okay
PS1 FF_POK okay
PS1 FF_UV okay
PS1 FF_OV okay
-----------------------------------------
Keyswitch:
-----------------------------------------
Location Keyswitch State
-----------------------------------------
MB SYSCTRL NORMAL
--------------------------------------------------
Led State:
--------------------------------------------------------------
Location Led State Color
--------------------------------------------------------------
MB ACT on green
MB SERVICE on amber
MB LOCATE off white
PS0 ACT off green
PS0 SERVICE off amber
PS0 OK2RM off blue
PS1 ACT on green
PS1 SERVICE off amber
PS1 OK2RM off blue
HDD0 SERVICE off amber
HDD0 OK2RM off blue
HDD1 OK2RM off blue
HDD2 OK2RM off blue
HDD3 OK2RM off blue
=========================== FRU Operational Status ===========================

---------------------------------
Fru Operational Status:
---------------------------------
Location Status
---------------------------------

System
MB/SC okay
PS0 faulty
HDD0 present
HDD1 present
PS1 okay
================================ HW Revisions ================================

ASIC Revisions:
-------------------------------------------------------------------
Path Device Status Revision
-------------------------------------------------------------------
/pci@1f,700000 pci108e,a801 okay 4
/pci@1e,600000 pci108e,a801 okay 4
/pci@1c,600000 pci108e,a801 okay 4
/pci@1d,700000 pci108e,a801 okay 4
System PROM revisions:

----------------------
OBP 4.22.19 2006/09/06 23:44 Sun Fire V210/V240,Netra 210/240
OBDIAG 4.22.19 2006/09/06 23:57
NOTE
Run the man prtdiag command to view the prtdiag usage.
To view information about the CPU, memory, and hard disk, respectively run the following
commands:
l CPU:
# psrinfo -v
l Memory:
# prtconf | grep Memory
l I/O device:
# iostat -E
14.1.10 Starting the N2000 DMS as the root User Failed
Description
The system prompts operation failure when I log in to the Solaris OS as the root user and start
the N2000 DMS.
Analysis
You need to set the environment variables for the N2000 DMS, such as the DLL path and
database variables. Before you start the N2000 DMS, you must run the environment variable
file.
Solution
Execute the following environment variables:
# cd /n2kuser
# . ./.profile
NOTE
Include a dot to the left of profile. The dot (.) is part of the file.

System
14.1.11 Why Does the N2000 DMS Server Process Exit When I Press
Ctrl+C
Description
In Solaris, manually run the startn2000.sh script to start the N2000 DMS. On the console where
the N2000 DMS is started, all server processes exit when I press Ctrl+C.
Analysis
According to the bash in the Solaris OS, when you press Ctrl+C on the N2000 DMS console,
all processes on the console receive the signal. The N2000 DMS responds as Exit to the signal.
In this case, all N2000 DMS service processes exit when you press Ctrl+C.
Solution
To solve this problem, you need to correctly start the N2000 DMS. Do as follows:
1. Open a console. Run the following command to run the environment variable of the
n2kuser user:
#cd /n2kuser
#. ./.profile
2. Run the following command to run the N2000 DMS system script:
#cd $N2000ROOT/server/bin
#. ./startn2000.sh
3. After starting the script, close the current console to avoid operations on this console.
14.1.12 How to Set the ACL for a Server with Multiple Network
Adapters
Description
You have added the IP address of the first network adapter of a client to the ACL. Sometimes
you cannot access the N2000 DMS server.
Analysis
The server controls the access based on IP addresses. If a client has multiple network adapters,
it uses a random IP address of the network adapters to connect to the server.
If the address does not belong to the first network adapter, the system prompts that the address
is not in the ACL.
Solution
If a server has multiple network adapters, all its IP addresses need to be added to the ACL.

System
14.2 Sybase Database

This describes common problems of using the Sybase database.
14.2.1 How to Check Whether the Sybase Database Is Started

14.2.2 How to Manually Start the Sybase Database
14.2.3 How to Manually Stop the Sybase Database
14.2.4 How to View the Bit Number of the Sybase Database
14.2.5 How to Change the License of the Sybase Database
14.2.6 How to Process the Abnormal Stop of the Backup Sybase Database
14.2.7 How to View the Deadlock Information in the Database
14.2.1 How to Check Whether the Sybase Database Is Started

Problem Description
How to check whether the Sybase database is started?
Solution
To check whether the Sybase database is started, do as follows:
1. Log in to the database server as the root user.
2. Run the following commands:
# ./showserver
root 475 473 2 09:51:56 ? 2:57 /opt/sybase/ASE-12_5/bin/
dataserver -sN2000DBServer -d/opt/sybase/data/master.d
root 569 567 0 09:52:56 ? 0:00 /opt/sybase/ASE-12_5/bin/
backupserver -SN2000DBServer_back -e/opt/sybase/ASE-12
If dataserver and backupserver are displayed, the database and backup database
are normally started.
14.2.2 How to Manually Start the Sybase Database

Problem Description
How to manually start the Sybase database?
Solution
To start the Sybase database, do as follows:
# cd /opt/sybase/ASE-12_5/install/

System
# ./startserver -f ./RUN_N2000DBServer
# ./startserver -f ./RUN_N2000DBServer_back
14.2.3 How to Manually Stop the Sybase Database
Problem Description
How to manually stop the Sybase database?
Solution
To stop the Sybase database, do as follows:

1>shutdown SYB_BACKUP
2>go
1>shutdown
2>go
14.2.4 How to View the Bit Number of the Sybase Database
Problem Description
Both the 32-bit and 64-bit Sybase databases can be installed in the Solaris 64-bit OS. After the
Sybase database is installed, the bit numbers of the database patch and database need to be the
same. The inconsistent bit numbers may damage the database. Thus, you need to view the bit
number of the database after installing the Sybase database.
Solution
Run the following commands to view the bit number of the database:
# cd /opt/sybase/OCS-12_5/bin/
# ./isql -SDBServer -Usa -P<sa password>
1>select @@version
2>go
Adaptive Server Enterprise/12.5.3/EBF 13325 ESD#5/P/Sun_svr4/OS 5.8/ase1253/193

9/64-bit/FBO/Tue Dec 6 09:13:20 2005
64-bit is the bit number of the database.

System
14.2.5 How to Change the License of the Sybase Database
Problem Description
When the software or hardware changes, or the license expires, how to change the license of the
Sybase database?
Solution
1. Log in to the Sybase server as the root user and back up the original license. Run the
following commands:
# cd /opt/sybase/SYSAM-1_0/licenses
# cp license.dat license.dat.bak
2. Run the following commands to register with the new license:
# cd /opt/sybase/SYSAM-1_0/bin
# ./lmgr
(1) In the Sybase License Management dialog box, click Yes.

(2) In the License Manager dialog box, type the new license, and then click Finish.
3. Run the following commands to read the new license information:
# ./lmutil lmreread
4. Run the sp_configure options_name value command to activate the relevant component.
For example:
sp_configure "enable ha" 1
sp_configure "enable ha" 1
NOTE
The value is 1 and 0.1 indicates the component is activated, and 0 indicates the component is
deactivated.
5. Restart the Sybase database.
14.2.6 How to Process the Abnormal Stop of the Backup Sybase

Database
Problem Description
How to process the abnormal stop of the backup Sybase database?
Solution
Before starting the Sybase, run the nohup command.
# nohup ./startserver -f ./RUN_SYB_back>/dev/null

System
14.2.7 How to View the Deadlock Information in the Database

Problem Description
How do view the deadlock information in the Sybase database when errors occur?
Solution
To collect the deadlock information of the Sybase database, do as follows:
# isql -SDBServer -Usa -P<sa password>
1>sp_lock
2>go
fid spid loid locktype table_id page row

dbname class context ------ ------ -----------
---------------------------- ----------- ----------- ------ ---------------
------------------------------ ---------------------------- 0 10
20 Sh_intent 464004684 0 0 master Non
Cursor Lock
(1 row affected) (return status = 0)
NOTE
The preceding information (Non Cursor Lock) indicates no deadlock occurs. The database name is
master, the process ID of the locked table is spid=10 , and the locked table ID is
table_id=464004684.
For further information, perform the following operations:
1>dbcc traceon(3604)
2>go
The execution of the dbcc command is complete. If the error information is printed, contact
the system administrator.
1>use master
2>go
1>select object_name(464004684)
2>go
------------------------------ spt_values
(1 row affected)
1>dbcc sqltext(10)
2>go
The execution of the dbcc command is complete. If the error information is displayed,
contact the system administrator.
NOTE
The previous commands are to view the sessions of table_id=464004684 and spid=10.

System
14.3 N2000 DMS Software

This describes common problems of using the N2000 DMS software.
14.3.1 How to Obtain Version Information

14.3.2 Invalid User Name or Password Is Prompted When the Client Automatically Upgrades
14.3.3 Client Does Not Respond For a Long Time
14.3.1 How to Obtain Version Information
Problem Description
How to obtain the version information of the N2000 DMS software?
Analysis
The inconsistent versions of the N2000 DMS client and server may cause problems. You can
view the version numbers to check whether the versions of the client and server are consistent.
Solution
If you can start the client and N2000 System Monitor, view the version information on their
interfaces.
l To view the client version: Choose Help > About, and then click the Component tab.
l To view the server version: Click the Component tab in the N2000 System Monitor.
14.3.2 Invalid User Name or Password Is Prompted When the Client

Automatically Upgrades
Description
When the client automatically upgrades, the error prompt of invalid user name or password is
displayed.
Analysis
The configuration parameters of the client automatic upgrade on the server are incorrect.
Solution
1. In the $N2000ROOT/server/conf path, check whether the upgrade server address and user
name in the autoupgrade.cfg file are the same as the parameters on the actual upgrade
server.
2. Set the correct upgrade parameters through the $N2000ROOT/server/bin/
UpgradeParaTool path.
3. Restart the security service on the server.

System
4. Restart the client and the client automatically upgrades.
14.3.3 Client Does Not Respond For a Long Time
Description
In the Login dialog box, after you enter the user name and password, click Login. The N2000
DMS client does not respond for a long time.
Analysis
The client is connected to the server after you click Login. The connection may be delayed
because of network transmission.
The default login time-out time is 100 seconds. When the delay time exceeds the time-out time,
a network transmission time-out dialog box may be displayed.
Solution
You can configure the login time-out time according to the actual network connection.
Configure the login time-out time in the securityConfig.xml file in the $N2000ROOT/client/
style/defaultstyle/conf/security path. A typical securityConfig.xml file is shown as follows:
Change the values of the parameters (in bold) and restart the client.

<AREADESC areaname="SECURITY_TIME">
<DESC descname="high">
<PARAS>
<PARA name="overtime" value="200000"/>
</PARAS>
</DESC>
<DESC descname="middle">
<PARAS>
<PARA name="overtime" value=/>
</PARAS>
</DESC>
<DESC descname="low">
<PARAS>
<PARA name="overtime" value="100000"/>
</PARAS>
</DESC>
</AREADESC>
14.4 Security Management

This describes how to process the common problems in user right management and license
management.
14.4.1 A User Cannot Log In After the Client Exits Abnormally

14.4.2 Cannot Find the Operation Objects When Assigning Operation Rights
14.4.3 Server Cannot Start After the License Is Updated

System
14.4.1 A User Cannot Log In After the Client Exits Abnormally

Description
The client exits abnormally. When you log in again to the client as the user name, the system
may prompt the user is logged in. The problem persists after you restart the N2000 DMS server.
Analysis
When the user logs in, the process saves the login information in one file to ensure that the
process is connected to the client after the process is restarted.
If many users cannot log in through the user account, when the user quits the system abnormally,
the process cannot clear the login information and the system considers that the account logs in
to the system.
Solution
1. Stop the security process in the N2000 System Monitor.
2. Delete the userlist.sav file in the $N2000ROOT/server/conf path.
3. Start the security process in the N2000 System Monitor.
14.4.2 Cannot Find the Operation Objects When Assigning

Operation Rights
Description
Certain devices are added in the topology view. When a user opens the window for assigning
operation rights, the user cannot find the relevant operation objects.
Analysis
The user does not have management rights to the devices.
Solution
1. In the Security Management window, select the user in Users.
2. On the Managed Domain tab, assign the device management rights to the user.
3. On the Operation Rights tab, assign operation rights to the user.
14.4.3 Server Cannot Start After the License Is Updated

Description
The server cannot start after the license is updated.
Analysis
l The formats of the license file and files in the Solaris OS are different.
l The network adapter does not correctly connected.

System
l More than one license files exist or the license file is invalid.
Solution
l In the Solaris OS, make sure that the license file is transmitted to the server in ASCII codes.
The license generation tool is the Windows version, and the license file format is different
from the file format in the Solaris OS. A file format is automatically converted when the
file is transmitted to the Solaris server in ASCII codes.
l Make sure that physical connection between the client and server is normal, the network
adapter is normal, and the network cable is correctly connected to the network adapter.
l Make sure that only one license file exists in the $N2000ROOT/server/license path, and
the file is formally released and valid.

System
Administrator Guide - Solaris A N2000 DMS Command Reference
A N2000 DMS Command Reference
A.1 N2000 DMS Command Reference

This describes the common N2000 DMS programs. The N2000 DMS provides certain simple
application programs and users can use them conveniently.
A.2 Solaris Common Reference
This describes common commands in the Solaris OS.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential A-1

System
A N2000 DMS Command Reference Administrator Guide - Solaris
A.1 N2000 DMS Command Reference

This describes the common N2000 DMS programs. The N2000 DMS provides certain simple
application programs and users can use them conveniently.
Table A-1 Common programs in the Solaris OS
Program Function Path
n2000.sh Start the N2000 DMS client. $N2000ROOT/client/
sysmonitor.sh Start the N2000 System $N2000ROOT/client/

Monitor.
run_help.sh Start the online Help. $N2000ROOT/client/
bktool.sh Start the database backup $N2000ROOT/client/

tool.
DbPwdTool The password change tool for $N2000ROOT/server/bin/

changing the passwords of
the N2000user and sa users.
A.2 Solaris Common Reference

This describes common commands in the Solaris OS.
A.2.1 Commands for Operating Solaris Directories

This describes the architecture of the Solaris file system and provides some commands for
browsing and controlling the directory.
A.2.2 Commands for Operating Solaris Files
This describes the commands for copying, deleting, and modifying a file.
A.2.3 Commands for Viewing Solaris Files
This describes the commands for displaying and browsing the contents of a text file.
A.2.4 Commands for Solaris User Management
This describes common commands for user management.
A.2.5 Commands for Managing Solaris System Resources
This describes the commands for managing Solaris system resources.
A.2.6 Commands for Solaris Network Communication
This describes common network communication commands.
A.2.1 Commands for Operating Solaris Directories

This describes the architecture of the Solaris file system and provides some commands for
browsing and controlling the directory.
A-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
In the file system of Solaris, the root directory is usually indicated by /. The system directory
and user directory are available in the root directory. After logging in to the Solaris OS, you can
access the home directory. You can create subdirectories in the home directory.
Table A-2 shows the common commands used to browse and control the directory.
Table A-2 Commands for browsing and controlling the directory
Use To
pwd Display the current directory.
cd [directory] Change to another directory.
mkdir [directory] Create a directory.
rmdir [directory] Delete a directory.
ls [option][directory or file] Display the contents of the directory or

information about the file.
pwd Command
This topic describes the pwd command used for viewing the current working folder.
Function
View the current working folder.
Example
# pwd
/export/home
cd Command
This topic describes the cd command used for switching the current folder to another folder.
Function
The cd command is used to switch the current folder to another folder. This command applies
to both absolute and relative paths.
Example
l To switch to the home folder, run the following command:
# cd
l To switch to the system root directory, run the following command:
# cd /

System
l To switch back one folder, run the following command:
# cd ..
l To switch back two folders, run the following command:
# cd ../..
l To switch to the /export/home folder by the absolute path, run the following command:
# cd /export/home
NOTE
If you run the cd command that is not followed by any parameter, the system is switched back to the home
folder.
mkdir Command
This topic describes the mkdir command used for creating a folder.
Function
The mkdir command is used to create a folder. When the path to the created folder is determined,
absolute and relative paths can be used.
Example
To create a subfolder data in /home1/omc, run the following command:
# mkdir /home1/omc/data
If the current folder is /home1/omc, run the following command:

# mkdir data
rmdir Command
This topic describes the rmdir command used for deleting an empty folder that is no longer
useful.
Function
The rmdir command is used to delete an empty folder.
CAUTION
l If the folder to be deleted is not empty, you must delete the files in the folder before running
the rmdir command.
l To delete the current folder, you must switch to the upper-level folder.
Example
To delete the data subfolder in the /home1/omc folder, run the following command:

System
# rmdir /home1/omc/data
If the current folder is /home1/omc, run the following command:

# rmdir data
ls Command
This topic describes the ls command used for listing the files and subfolders in a specific folder.
Function
The ls command is used to list the files and subfolders in a folder. Run the ls command without
any parameter to list the content of the current folder. Run the ls command with parameters to
list the information about the size, type, and privileges of the file, and the date when the file was
created and modified.
Command Format
ls Option Directory or File
Option Description
Several individual options and a combination of options can be used for the ls command. Place
the prefix - before the options. Table A-3 lists some common options.
Table A-3 Option description of the ls command
Option Description
-a Lists all files including the hidden files, that is, the files starting with a
dot ., for example, the .login file.
-F Specifies the type of a file by suffix signs.

The meaning of the suffixes are as follows:
l /: for folder files
l =: for pipe files
l @: for sign-linking files
l *: for executable files
-l Lists the detailed information about a file, such as the file type, privileges,
number of links, owner, file group, file size, file name, and the date of the last
modification.
If the file is a sign-linking file, then the -> sign is added at the end of the file name for pointing
to the linked file.
Example
To view the long-form content of the files in the current folder, run the following command:

System
# ls -l |more
total 11094632
drwxr-xr-x 2 sybase staff 1024 Sep 5 2001 bin
drwxr-xr-x 14 sybase staff 512 Sep 5 2001 charsets
drwxr-xr-x 3 sybase staff 512 Sep 5 2001 collate
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 config
-rw-r--r-- 1 sybase staff 2048000000 Mar 6 09:50 data_dev.dat
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 devlib
drwxr-xr-x 7 sybase staff 512 Sep 5 2001 diag
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 hs_data
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 include
drwxr-xr-x 7 sybase staff 512 Sep 5 2001 init
drwxr-xr-x 3 sybase staff 512 Sep 5 2001 install
-rw-r--r-- 1 sybase staff 268 Sep 5 2001 interf.old
-rw-r--r-- 1 sybase staff 402 Oct 29 15:25 interfaces
drwxr-xr-x 2 sybase staff 1024 Sep 5 2001 lib
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 license
drwxr-xr-x 6 sybase staff 512 Sep 5 2001 locales
-rw-r--r-- 1 sybase staff 2048000000 Mar 6 10:51 log_dev.dat
-rw-r--r-- 1 sybase staff 2048000000 Mar 6 10:36 log_dev1.dat
drwxr-xr-x 5 sybase staff 512 Sep 5 2001 pad
-rw-r--r-- 1 sybase staff 5242880 Feb 19 10:10 phase2.dat
drwxr-xr-x 8 sybase staff 512 Sep 5 2001 sample
--More--
After you run the ls -l command, the result may be displayed in several screens. To view the file
contents, one screen at a time, run one of the following commands:
l # ls -la | more
l $ ls -la>ccc
Save the command output to the ccc file, and then run the following command to view the
output on screen at a time:
# more ccc
After you run the ls -l command, seven columns of information are displayed, which are
described as follows:
l The first column consists of 10 characters. The first character indicates the file type. For
example, the character - refers to a common file and the character d refers to a folder. The
following nine characters are three triplets indicating the access privileges of the file owner.
The first triplet pertains to the owner, the middle triplet pertains to members of the user
group, and the right-most one pertains to other users in the system. For example, the
characters r, w, and x indicate that the user has the privileges to read, write, and execute a
file, whereas the character - indicates that the user does not have any relevant privileges
for the file.
l The second column indicates the number of links of the file.
l The third and fourth columns display information such as the owner of the file, and the user
group to which the file belongs.
l The fifth column shows the size of the file in bytes.
l The sixth column shows the time and date when the file is last modified.
l The seventh column shows the file name.
A.2.2 Commands for Operating Solaris Files

This describes the commands for copying, deleting, and modifying a file.
Table A-4 shows the commands for operating a file.

System
Table A-4 Commands for operating a file
Use To
cp [option]file 1 file 2 Copy a file.
mv file 1 file 2 Move or rename a file.
rm [option] file Delete a file.
chmod [option] file Change the authority of a file.
chown [option] owner file Change the owner of a file.
chgrp [option] group file Change the group of a file.
cp Command
This topic describes the cp command used for copy the contents of a file to another file.
Function
The cp command is used to copy the contents of a file to another file.
Command Format
cp option source file object file
Option Description
The option -r indicates recursively copying a folder. That is, when copying a folder, copy the
files and subfolders included in the folder, and files and subfolders in the subfolders until the
last level of the folder.
Example
To copy the old_filename file in the current folder to the file new_filename, run the following
command:
# cp old_filename new_filename
mv Command
This topic describes the mv command used for moving and renaming a file.
Function
The mv command is used to move and rename a file.

System
CAUTION
l After you run the mv command, only the target file instead of the source file exists.
l After you run the cp command, the source file still exists and the target file is generated.
Command Format
mv source file object file
Example
To move the old_filename file in the root directory to the /home1/omc folder, and rename the
source file to new_filename, run the following command:
# mv old_filename /home1/omc/new_filename
rm Command
This topic describes the rm command used for deleting a specific file.
Function
The rm command is used to delete a file.
CAUTION
l In the UNIX system, a file, once deleted, cannot be restored. Therefore, use the -i option
to avoid the deletion of a file by mistake.
l To delete a folder, run either of the following commands: rmdir or rm -r. The difference
between the two commands is: rmdir deletes only empty folders but rm -r deletes any
folder.
Command Format
rm Option file
Option Description
l -i: refers to interactive operations. Your confirmation is required before a command is run.
l -r: recursively deletes a folder. That is, when deleting a folder, delete the files and subfolders
included in the folder, and files and subfolders in the subfolders until the root folder.
Example
To delete the old_filename file in the current folder, run the following command:
# rm -i old_filename

System
chmod Command
This topic describes the chmod command used for changing the access rights of a directory or
a file.
Function
The chmod command is used to change the access rights of a directory or a file.
Format
chmod option directory or file
Based on different notation methods of the option in the command, two modes are available:
l Symbol mode
chmod objectoperatorrights file
l Digit mode
chmod lmn file
Option Description
l Symbol mode
Table A-5 lists common options in symbol mode of the chmod command.
Table A-5 Common options in symbol mode of the chmod command

Option Option Detail Description
Object u Owner of a file
g Users sharing the same group

with the file owner
o Other users except the file owner

and the users sharing the same
group with the file owner
a All users
Operator + Add a right
- Cancel a right
= Set a right
l Digit mode
The option lmn represents the following digits:
l: the rights of the owner
m: the rights of the users sharing the same group with the owner
n: the rights of other users in the system
The value of each digit is equal to the sum of the values of r (read right), w (write right),
x (execute right), or - (no right) in each group. In each group, r = 4, w = 2, x = 1, and - =

System
0. In the following example -rwxr-xr-- 1 rms sbsrms 46098432 May 12

16:02 sdh*, the access rights of the file sdh is represented by the symbols rwxr-
xr--. The nine symbols are divided into three groups, with three symbols as a group. The
three groups represent the rights of the file owner, the rights of the users sharing the same
group with the file owner, and the rights of other users in the system. The three groups can
be represented in digits 754, which is calculated according to the formulas: 7 = 4 + 2 + 1,
5 = 4 + 0 + 1, and 4 = 4 + 0 + 0.
File: indicates the name of the file whose rights are changed.
Example
l Symbol mode
Authorize the file1 owner with the read, write, and execute rights. Authorize the users
sharing the same group with the file owner with the read and execute rights. Authorize
other users with the read and execute rights. Run the following command:
# chmod u=rwx,go=rx file1
To authorize all the users with the read and write rights, run the following command:
# chmod a=rw file2
l Digit mode
Authorize the file1 owner with the read, write, and execute rights. Authorize the users
sharing the same group with the file owner with the read and execute rights. Authorize
other users with the read and execute rights. Run the following command:
# chmod 755 file1
To authorize all the users with the read and write rights, run the following command:
# chmod 666 file2
NOTE
l To configure the rights of a file for users in a group and other users in the system in symbol mode,
you must authorize these users with the execute right of the directory where a file exists. Run the
following command for the directory that requires you to set rights:
# chmod u=rw,+x .
You can also run the following command:
# chmodu=rwx,go=x .
In this command, the symbol "." indicates the current directory.
l In digit mode, r = 4, w = 2, x = 1, and - = 0. These mappings are set according to the binary mode.
For the three symbols in a group, which represent the read right, the write right, and the execute right,
assign the binary value 1 if a symbol has the corresponding right and assign the binary value 0 if a
symbol does not have the corresponding rights. Take the previous file sdh as an example. The file
rights are represented by the symbols rwxr-xr--. After converting the symbols into a binary value,
you can obtain "111101100". The binary value is divided into three 3-digit groups, with each group
representing a file right. After converting the binary value of each group into a decimal value, you
can obtain three values: 7, 5, and 4.
chown Command
This topic describes the chown command used for changing the owner of a file.

System
Function
The chown command is used to modify the owner of a file. In most UNIX systems, this command
can be run only by the super user.
Command Format
chown Option owner file
Option Description
l -f: runs the command forcibly without displaying errors
l -R: recursive folder
l Owner: the modified owner
l File: the file of the owner to be modified
Example
l Assume that there is a user new_owner and a file in the system. Run the following command
to change the owner of the file to new_owner:
# chown new_owner file
l Assume that there is a user test in the system. Change the owner of all files in the /export/
home folder and and the subfolders to test:
# chown -R test /export/home
chgrp Command
This topic describes the chgrp command used for moveing all files from the user group to which
you belong to another user group.
Function
The chgrp command is used to move all files from the user group to which you belong, to another
user group. That is, you belong to at least two user groups at the same time.
Command Format
chgrp Option group file
Option Description
l -f: runs the command forcibly without displaying errors
l -R: recursive folder
l Group: the modified user group
l File: the file the user group of which is to be modified

System
Example
To change the user group file to new_group, run the following command:
# chgrp new_group file
CAUTION
The new user group to which a file is moved should be created. Run the groups command to
list the groups to which you belong.
After the owner or group of a folder is changed, the folder does not belong to that user or user
group any more. The attributes of the subfolders and files in the folder, however, are retained.
Run the chown command to modify the owner and the user group of a file at the same time:
# chown omc:staff file1
For example, run the command to modify the owner of file1 to omc and the group to staff.
find Command
This topic describes the find command used for searching for a file that meets the preset
conditions in the specified folders and subfolders.
Function
The find command is used to search for a file that meets the preset conditions in the specified
folders and subfolders. By using this command, you can find the file even if you forget the correct
path of the file.
Command Format
find folder condition
l Folder: indicates the folder to be searched. You can enter multiple folder names. Separate
the folder names by using spaces.
l Condition: indicates the conditions for file search, such as the file name, owner, and time
of the last modification.
Table A-6 describes the conditions for file search.
Table A-6 Conditions for file search
Condition Description
-name name The name of the file or folder to be searched.

Wildcards, such as -name '*.c', can be used.
-print Prints the path that meets the conditions.
-size n Searches for the files that use n blocks.

System
Condition Description
-type x Searches for files by file type. The file type x includes:
l d: directory
l f: file
l b: block
l c: character
l p: pipe
-user user Searches all files of user. The value of user can be a
user name or UID.
-group group Searches all files of the user group. The value of group
can be a user group name or GID.
-links n Searches all files with the number of links as n.
-atime n Searches the files accessed before n days.
-mtime n Searches the files modified before n days.
-exec command {}\; Uses the found file as the object of the command to be
run. Put the parameters to be used in the command
execution between { and }.
Table A-7 describes the logical operators of conditions.
Table A-7 Logical operators of conditions
Logical Operator Meaning Example Description
! non ! -name "*.c" All the files except

those with the
extension name as .c
-o or -size +10 -o -links 3 All the files with more

than 10 blocks or with
3 links
and -size +10 -links 3 All the files with more

than 10 blocks and
with 3 links
In the preceding table, +10 stands for more than 10 blocks and -10 for fewer than 10 blocks.
Example
To search for files in the /tmp folder with the file name starting with c, and then print the paths,
run the following command:

System
# find /tmp -name "c*" -print

/tmp/ctisql_0WBJgt
/tmp/ctisql_0dznJ_
/tmp/ctisql_0CpW34
/tmp/ctisql_0FO4vs
To search the file test in the current folder and then print the paths, run the following command:
# find . -name test -print

./Report/reloc/resin1.2.0/conf/test
./Report/reloc/resin1.2.0/doc/examples/login/WEB-INF/classes/test
./Report/reloc/resin1.2.0/doc/examples/tags/WEB-INF/classes/test
NOTE
l The search may take several minutes. To save time, you can run this command in the background.
That is, the output for the command is exported to a file for later query. End the command line with
& so that the system runs the command in the background. For example,
# find / -name "abc*" -print > abc.file &
l After the search is complete, run the following command to view the result of the search:
# cat abc.file
l Different users may have different privileges for the same file. Therefore, ordinary users may find
only some files of the system. To list all the files that meet the set conditions, log in as a super user
and search from the root directory.
tar Command
This topic describes the tar command used for combining several files into one archive and save
it to a tape or disk.
Function
The tar command is used to combine several files into one archive and save it to a tape or disk.
When one of the files is required, obtain the file directly from an archive.
Command Format
tar function options modification options file
Option Description
l function options: sets the actions, such as read and write, of the tar command
l modification options: modifies the actions of the tar command
Table A-8 describes the options of the tar command.
Table A-8 Option description for the tar command
Option Specified Description

Option
Function options r Adds the specified file to an archive.

System
Option Specified Description

Option
x Reads a file in an archive. If the file name is a

folder, this option reads the subfolders included
in the folder. This option is often used.
c Creates an archive. This option is often used.
g Creates a file at the beginning of an archive rather

than add the file in the last file.
Modification v Activates the display mode. The names of all the

options processed files are displayed. This option is often
used.
w Activates the confirmation mode. Your

confirmation is required before each file is
processed.
f Indicates that an archive is a file. If this parameter

is skipped, the preset tape or disk is used as the
object. This option is often used.
Example
l Run the tar command to back up files.
To back up all the files and subfolders in the /export/home folder in the current folder to
the default device and view the file information during the backup, run the following
command:
# tar cv /export/home
In current folder, back up all the files and subfolders in the /export/home folder to the
databak.tar file, and to view the file information during the backup, run the following
command:
# tar cvf databak.tar /export/home
l Use tar to restore files.
To restore the files in the default device to a hard disk, and to view the file information
during the restoration, run the following command:
# tar xv
In current folder, restore the databak.tar file to the /export/home folder, and to view the
file information during the restoration, run the following command:
# tar xvf databak.tar

System
CAUTION
l Do not enter "-" on the left of the function and modification options in the tar command.
l Run the following tar command to pack several files into a package:
# tar cvf filebak.tar file1 file2 file3
l Run the previous command to pack file1, file2, and file3 into a package named
filebak.tar.
l The names of the disk and tape devices used in file backup and restoration in the tar
command may vary according to the UNIX system. Check carefully before running the
command.
gtar Command
This topic describes the gtar command used for combining multiple files into an archive and
storing it in a tape or disk.
Function
The gtar command can merge multiple files into an archive and store it in tapes or disks. You
can obtain the required files from an archive, if required.
Format
gtar function options modification options file to be backed up or restored
Option Description
l Function option: sets the actions of the gtar command, such as read or write.
l Modification option: modifies the actions of the gtar command.
Table A-9 lists some options.
Table A-9 Descriptions of gtar command options
Option Example Description
Function option r Adds the specified file to end of an archive.
x Reads a file in the archive. If the name is a directory, its sub

directories are also read. This option is common.
c Creates a new archive. This option is common.
g Creates a file from the beginning of the archive instead of

the end of the last file.
Modification v Starts the display mode. The gtar command can display all
option names of the processed file. This option is common.
w Activates the confirm mode. The gtar command requests

you to confirm before processing each file.

System
Option Example Description
f Indicates that the archive is a file. Omission of this option

indicates that the object is the preset disk or tape. This option
is common.
Instance
l Run the gtar command to back up files.
In the current directory, back up all the files and folders in /export/home/sybdev to the
default device. During the backup, the file information is displayed.
# gtar cv /export/home/sybdev
In the current directory, back up all the files and folders in /export/home/sybdev and save
them as databak.tar. During the backup, the file information is displayed.
# gtar cvf databak.tar /export/home/sybdev
l Run the gtar command to restore files.
Restore the files of default devices in the backup files to a hard disk. During the restoration,
the file information is displayed.
# gtar xv
In the current directory, decompress the backup file databak.tar to /export/home/
sybdev. During the restoration, the file information is displayed.
# gtar xvf databak.tar
CAUTION
l There is no - symbol before the function option and modification option of gtar.
l The gtar command can pack multiple files. The command is as follows:
# gtar cvf filebak.tar file1 file2 file3
l This command packs the three files, that is, file1, file2, and file3, into the file named
filebak.tar.
l Under different UNIX systems, when using gtar to back up or restore files, note that names
of the floppy disk and tape are different. Ensure that you use the right names.
compress Command
This topic describes the compress command used for compressing files.
Function
The compress command is used to compress files and save the memory space. The name of the
compressed files ends with .Z. The command for decompressing such files is uncompress.
Command Format
compress file

System
Example
To compress a file, run the following command:
# compress file
CAUTION
The difference between the tar command and the file compressing commands is as follows:
The tar command packs or combines files and packs many folders or files into a package. To
compress the combined files *.tar, use the compress or pack command.
uncompress Command
This topic describes the uncompress command used for decompressing files.
Function
The uncompress command is used to decompress the compressed files. The command for
compressing files is compress.
Command Format
uncompress compressed file ending with ".Z"
Example
To decompress the file.Z file, run the following command:
# uncompress file.Z
pack Command
This topic describes the pack command used for compressing files and saving memory space.
Function
Run the pack command to compress files. The name of the compressed files ends with .Z. The
space achieved through compression depends on file types. To extract files, use the unpack
command.
Command Format
pack file
Example
To pack a file, run the following command:
# pack file

System
CAUTION
l Do not run the pack command to compress files of small sizes. To compress such files, use
the pack command with the option -f for forced compression.
# pack -f filename
l The difference between the tar command and the file compression commands is as follows:
The tar command packs or combines files and packs many folders or files into a package.
To compress the combined files *.tar, use the compress or pack command.
unpack Command
This topic describes the unpack command used for extracting files.
Function
The unpack command is used to extract the packed files. To pack files, use the pack command.
Command Format
unpack compressed file ending with ".Z"
Example
To extract the file.Z file, run the following command:
# unpack file.Z
pkgadd Command
This topic describes the pkgadd command used for sending a file package to the system for
execution.
Function
The pkgadd command is used to send a file package to the system for execution. To remove a
package from the system, run the pkgrm command.
Command Format
pkgadd option file package name
Option Description
-d device: to install or copy a package from the device. The device can be an absolute path, the
identifier of a tape, or a disk such as /var/tmp or /floppy/floppy_name, or a device name such
as /floppy/floppy0.
Example
To send a file package in the current folder to the file1 file, run the following command:

System
# pkgadd -d . file1
The dot in the command indicates that the folder is the current folder.
pkgrm Command
This topic describes the pkgrm command used for removing a package from the system.
Function
The pkgrm command is used to remove a package from the system. To pack and send a package
to the system, use the pkgadd command.
Command Format
pkgrm option file package name
Example
To remove the file1 file, run the following command:
# pkgrm file1
A.2.3 Commands for Viewing Solaris Files

This describes the commands for displaying and browsing the contents of a text file.
For details, see Table A-10.
Table A-10 Commands for displaying and browsing the contents of a text file
Use To
echo character string [option] Send a character string to the screen.
cat [option] file Display the contents of a file.
more [option] file Display a file in pages.
head [number] file Display the head of a file.
tail [number] file Display the tail of a file.
clear Clear the information displayed on the screen.
echo Command
This topic describes the echo command used for sending a character string to a standard output
device such as the monitor screen.
Function
The echo command is used to send a character string to a standard output device such as the
monitor screen.

System
Command Format
echo character string option
Option Description
Table A-11 lists five options that are frequently used.
Table A-11 Option description of the echo command
Option Description
\c The RETURN character is not displayed.
\0n n is an 8-digit ASCII character code.
\t The TAB character is displayed.
\n The RETURN character is displayed.
\v The vertical TAB character is displayed.
Example
# echo $HOME
/export/home
/export/home displayed on the screen is the meaning of the character string "$HOME".
To prevent the system from displaying RETURN, run the following command:
# echo $HOME "\c"
/export/home
Or:
# echo "$HOME \c"
/export/home
NOTE
The options \c, \0n, \t, \n, and \v are displayed in the character string enclosed in quotation marks. The
quotation marks can quote either one option or multiple options.
cat Command
This topic describes the cat command used for viewing the contents of a text file.
Function
The cat command is used to view the contents of a text file.

System
Command Format
cat option file
Option Description
l -n: number of each line of the displayed text
l -v: to view nonprinting characters rather than TAB and RETURN
Example
To view the contents of the cat_Table.txt file, run the following command:
# cat cat_Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
----------------------
tbl128Addr cat
user table
tbl128IP cat
user table
tbl128Name cat
user table
tblAdapterIP cat
user table
tblAdjCell cat
user table
... ... ...
NOTE
To view several files at the same time, run the following command:
# cat file1 file2 file3
more Command
This topic describes the more command used for displaying the content of a large file in different
pages.
Function
You can use this command to view a file on screen at a time. You can also use this command to
browse the previous screens and to search for character strings.
Command Format
more option file
Option Description
Remember to insert the prefix - before the options when multiple options and combination of
options are used. Table A-12 lists four options that are frequently used.

System
Table A-12 Option description of the more command
Option Description
-c Clears the screen before the content is displayed.
-w Indicates that the system does not exit at the end of the input but waits for the
prompt.
-lines Displays the number of lines on each screen.
+/mode Searches for files in a preset mode.
Example
To view the contents of the cat_Table.txt file on screen at a time, run the following command:
# more cat_Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
----------------------
tbl128Addr cat
user table
tbl128IP cat
user table
tbl128Name cat
user table
tblAdapterIP cat
user table
tblAdjCell cat
user table
... ... ...
NOTE
l To view a file on screen at a time, press the following keys to perform relevant operations:
Space key: to view the next screen
Return key: to view the next line
q: to exit
h: to view the online help
b: to switch back to the previous screen
/word: to search the character string "word" backward
l UNIX commands can be used in combinations. For example, add |more after other commands to
view relevant results on several screens.
head Command
This topic describes the function, format, and example of the head command.
Function
The head command is used to view the first few lines of a text file. By default, the first 10 lines
are displayed.

System
Command Format
head value file
Example
To view the first three lines of the Table.txt file, run the following command:
# head -3 Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
tail Command
This topic describes the tail command used for viewing the last few lines of a text.
Function
The tail command is used to view the last few lines of a text. By default, the last 10 lines are
displayed.
Command Format
tail value file
Example
To view the last ten lines of the cat_Table.txt file, run the following command:
# tail cat_Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
----------------------
tbl128Addr cat
user table
tbl128IP cat
user table
tbl128Name cat
user table
tblAdapterIP cat
user table
tblAdjCell cat
user table
... ... ...
NOTE
A special function of the tail command is to view the latest changes of a log file, because all the latest
changes are added at the end of the log file. The command format is as follows:
# tail -f commdrv.log
The option -f refers to the function of monitoring a file.
clear Command
This topic describes the clear command used for clearing the contents on the screen.

System
Function
The clear command is used to clear the contents on the screen.
Example
To clear the screen, run the following command:
# clear
grep Command
This topic describes the grep command used for searching for a character string in a text file.
Function
The grep command is used to search for a character string in a text file and to print all the lines
that contain the character string.
Command Format
grep character string file
Example
To search the character string operation in the ifconfig.txt file, run the following command:
# grep operation ifconfig.txt
used to control operation of dhcpagent(1M), the DHCP client
operation, be used to modify the address or characteristics
dhcpagent wakes up to conduct another DHCP operation on the
given, and the operation is one that
requested operation will continue.
To search the character string "The following options are supported" in the ifconfig.txt file, run
the following the command:
# grep "The following options are supported" ifconfig.txt
The following options are supported:
NOTE
The character string "The following options are supported" includes spaces. Remember to enclose the
character string within quotation marks in the command line.
vi Command
This topic describes the vi command used for creating and modifying text files.
Function
As a powerful text editing tool, the vi editor is used to create and modify text files.
The vi editor works in two modes:
l Text input mode: to enter the text

System
l Command mode: to enter the control command
Format
l To start the vi editor, enter the following command:
vi file name
l Table A-13 lists the operations in the text input mode.
Table A-13 Operations in the text input mode

Command Function
a Insert text immediately after the cursor (append).
A Insert text at the end of the line where the cursor is.
i Insert text immediately before the cursor (insert).
I Insert text before the first nonblank character in the line where the
cursor is.
o Insert a new line below the current one and insert text (open).
O Insert a new line above the current one and insert text.
l Table A-14 lists the operations related to moving the cursor in the text input mode.
Table A-14 Operations related to moving the cursor in the text input mode
Command Function
h Move the cursor one character left.
j Move the cursor one character down.
k Move the cursor one character up.
l Move the cursor one character right.
Line No. G Move the cursor to a specified line. For example, 1G means
that the cursor is moved to the first line.
G Move the cursor to the end of the text.
l Table A-15 lists the operation for exiting the text input mode and switching to the command
mode.
Table A-15 Operation for exiting the text input mode and switching to the command mode
Command Function
ESC Exit the text input mode and switches to the command mode.
l Table A-16 lists the operations related to deleting characters in the command mode.

System
Table A-16 Operations related to deleting characters in the command mode
Command Function
x Delete a character.
dd Delete a line.
l Exit the vi editor.

All the commands that exit vi editor must be run in the command mode. Therefore press
ESC before running the commands. Table A-17 describes the commands for exiting the
vi editor.
Table A-17 Commands for exiting the vi editor
Command Function
:wq Save a file and exit the vi editor.
:q Exit from the vi editor without saving the file.
:q! Exit from the vi editor and discard all the changes.
:w Save a file other than exit the vi editor.
A.2.4 Commands for Solaris User Management

This describes common commands for user management.
Only the root user and authorized users can add, modify, or delete users or user groups.
Table A-18 shows the user management commands.
Table A-18 Commands for user management
Use To
useradd [option] user name Add a user.
userdel user name Delete a user.
usermod [option] user name Modify the login information of a user.
passwd user name Change the password of a user.
groupadd group name Add a user group.
groupdel group name Delete a user group.
groupmod [option] group name Modify a user group.
smc Start the system management console in the

GUI.

System
useradd Command
The useradd command is used to add a user in the UNIX system.
Function
The useradd command is performed to add a user in the UNIX system.
Command Format
useradd option new user name
Option Description
You can combine options of the useradd command. Add the prefix - before these options. Table
A-19 lists the common options.
Table A-19 Option description of the useradd command

Option Remark
-c comment Indicate the comment.
-d directory Indicate the home folder.
-m Indicate the automatic creation of a home

folder if the home folder does not exist.
-g group Indicate the user group that the user belongs

to.
-s shell Indicate the shell that the user uses.
Example
Create a user named omc1 in the UNIX system. The user omc1 belongs to the staff user group
and the home folder is /home1/omc that is created automatically. In addition, the comment is
Test User and B shell is applied. To create a user named omc1 in the UNIX system, run the
following commands:
# useradd -c "Test User" -d /home1/omc -m -g staff -s /usr/bin/sh omc1
CAUTION
After a user is added, set the password for the added user. For details of setting the password,
refer to A.2.4.4passwd Command. After the password is set, the user can log in as a new user.
userdel Command
This topic describes the userdel command used for deleting a specific user of the UNIX operating
system.

System
Function
The userdel command is used to delete a user. Some UNIX systems do not allow deleting users
completely. Run the userdel command to revoke the privileges granted to the user.
Command Format
userdel user name
Example
Assume that there is user omc1 in the system. To delete user omc1, run the following command:
# userdel omc1
CAUTION
When a user has logged in, do not run the userdel command to delete the user. If you run the
userdel command, the following error message is displayed:
UX: userdel: ERROR: omc1 is in use. Cannot remove it.
usermod Command
This topic describes the usermod command used for modifying the user login information.
Function
The usermod command is used to modify the user login information.
Command Format
usermod option user name
Option Description
The combined option of the usermod command can be used. Add the prefix - before the options.
Table A-20 lists the common options.
Table A-20 Option description of the usermod command

Option Description
-c comment Modified comment
-d directory Modified home folder
-m Create a home folder automatically if the

home folder does not exist
-g group Modified user group

System
Option Description
-s shell Used shell
-l new_logname Modified user name
Example
To modify the login information about omc1, you need modify the user name to test, user group
to new_group, home folder to /home1, and comment to Tester. Run the following command:
# usermod -c "Test User" -d /home1 -g new_group -l test omc1
CAUTION
With the different operation system, do not run the usermod command to modify a user when
the user has logged in, or you must reboot operation system for some settings when perform the
command.
passwd Command
This topic describes the passwd command used for setting or changing a password for a user.
Function
The passwd command is used to set a password for an added user or to change the user password.
Command Format
passwd user name
Example
Assume that the user omc1 is added. To set the password of omc1, run the following command:
# passwd omc1
New Password:
Re-enter new Password:
passwd: password successfully changed for omc1
NOTE
The input password is not displayed.
groupadd Command
This topic describes the groupadd command used for adding a user group in the UNIX system.
Function
The groupadd command is used to add a user group in the UNIX system.

System
Command Format
groupadd user group name
Example
To add the user group staff1 in the UNIX system, run the following command:
# groupadd staff1
groupdel Command
This topic describes the groupdel command used for deleting a user group in the UNIX system.
Function
The groupdel command is used to delete a user group in the UNIX system.
Command Format
groupdel user group name
Example
To delete the user group staff1, run the following command:
# groupdel staff1
groupmod Command
This topic describes the groupmod command used for modifying the information about a user
group..
Function
The groupmod command is used to modify the information about a user group.
Command Format
groupmod user group name
-n name: the name of the modified user group
Example
To modify the name of the user group staff1 to staff2, run the following command:
# groupmod -n staff2 staff1
A.2.5 Commands for Managing Solaris System Resources

This describes the commands for managing Solaris system resources.

System
Table A-21 shows the system resource commands in Solaris.
Table A-21 Commands for reporting and managing system resources

Use To
man [option] command Get the help to a command.
df [option] [file system] Display the free disk space.
du [option] [directory or file] Display the used disk space of each file
system.
ps [option] Display the status of running processes.
kill [option] [process ID] End a process.
who [option] Display information about current login

users.
whereis [option] command Display the location of a command.
which command Display the path of a command.
hostname [host name] Display or set the host name.
uname [option] Display information about the OS.
ifconfig [option] Configure the parameters of the network

interface.
script [option] [File] Record I/O actions.
date [option] [+ format] Display the current date and time.
prtconf [option] Print system configuration information.
sysdef [option] Output system definitions.
prtdiag [option] Display system diagnosis information.
man Command
This topic describes the man command used for viewing the online help about a command.
Function
The man command is used to view the online help about a command.
Command Format
man option command
Example
To view the online help about the pwd command, run the following command:

System
# man pwd
Reformatting page. Wait... done
User Commands pwd(1)
NAME
pwd - return working directory name
SYNOPSIS
/usr/bin/pwd
DESCRIPTION
pwd writes an absolute path name of the current working
directory to standard output.
Both the Bourne shell, sh(1), and the Korn shell, ksh(1),
also have a built-in pwd command.
ENVIRONMENT
See environ(5) for descriptions of the following environment
variables that affect the execution of pwd: LC_MESSAGES and
NLSPATH.
EXIT STATUS
--More--(30%)
NOTE
Not all parameters in the man command are command names. For example, the man ascii command
displays all the ASCII characters and their expressions. The man shell_builtins command displays the
built-in command list and the shell using the commands.
df Command
This topic describes the df command used for viewing the free disk space.
Function
The df command is used to view the free disk space. The system administrator runs this command
frequently to check the usage of the disk space to avoid disk failure due to data overflow.
Command Format
df option file system
Option Description
l -l : the local file system
l -k: to view the free disk space (unit: KB)
Example
To check the free disk space, run the following command:
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 2053605 997684 994313 51% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/dsk/c0t1d0s7 35009161 2562019 32097051 8% /export/home
swap 3431792 6664 3425128 1% /tmp

System
The command result contains the following information:

l File system name
l File size (unit: KB)
l Used space
l Free space
l Capacity percentage of the filled file system and the mounting point
When you run the df command without any parameters, the free disk space in each mounted
device is displayed.
When the free disk space is reduced to the bottom line, the system administrator must take
immediate measures to locate the faulty file system.
du Command
This topic describes the du command used for viewing the disk space used by a specific folder
or file.
Function
The du command is used to view the disk space used by a specific folder or file.
Command Format
du option folder or file
Option Description
l -a : to view the disk space used by each file
l -s: to view the used total disk space
l -k: to view the result (unit: KB)
Example
l To view the disk space used by the files in the /etc folder, run the following command:
# du -k /etc |more
4 /etc/X11/fs
4 /etc/X11/twm
84 /etc/X11/xdm/pixmaps
157 /etc/X11/xdm
721 /etc/X11/xkb/rules
52 /etc/X11/xkb/types
16 /etc/X11/xkb/semantics
8 /etc/X11/xkb/geometry/ibm_vndr
44 /etc/X11/xkb/geometry/digital_vndr
44 /etc/X11/xkb/geometry/sgi_vndr
285 /etc/X11/xkb/geometry
81 /etc/X11/xkb/compat
28 /etc/X11/xkb/symbols/sun_vndr
16 /etc/X11/xkb/symbols/fujitsu_vndr
84 /etc/X11/xkb/symbols/macintosh_vndr
8 /etc/X11/xkb/symbols/nec_vndr
32 /etc/X11/xkb/symbols/digital_vndr
4 /etc/X11/xkb/symbols/sony_vndr
12 /etc/X11/xkb/symbols/xfree68_vndr

System
4 /etc/X11/xkb/symbols/hp_vndr
4 /etc/X11/xkb/symbols/sgi_vndr
850 /etc/X11/xkb/symbols
40 /etc/X11/xkb/keymap/sun_vndr
8 /etc/X11/xkb/keymap/digital_vndr
93 /etc/X11/xkb/keymap/sgi_vndr
181 /etc/X11/xkb/keymap
16 /etc/X11/xkb/keycodes/digital_vndr
12 /etc/X11/xkb/keycodes/sgi_vndr
108 /etc/X11/xkb/keycodes
2345 /etc/X11/xkb
4 /etc/X11/xsm
4 /etc/X11/lbxproxy
16 /etc/X11/fvwm2
4 /etc/X11/xserver/C/print/ddx-config/raster
4 /etc/X11/xserver/C/print/ddx-config
12 /etc/X11/xserver/C/print/attributes
245 /etc/X11/xserver/C/print/models/PSdefault/fonts
--More--
l To view the disk space used by all file systems in the current folder and send the results to
the sort command for sorting, run the following command:
# du -s * |sort -rn |more
28672 opt
3757 X11
2522 cups
1282 bootsplash
822 xscreensaver
808 sysconfig
661 services
661 init.d
473 postfix
428 apparmor
416 mono
389 joe
193 profile.d
165 ssl
165 apparmor.d
164 ssh
145 pam.d
145 lvm
112 fonts
109 xinetd.d
--More--
l To list the first ten file systems according to the file size, run the following command:
# du -s * |sort -rn |head -10
28672 opt
3757 X11
2522 cups
1282 bootsplash
822 xscreensaver
808 sysconfig
661 services
661 init.d
473 postfix
428 apparmor
ps Command
This topic describes the ps command used for viewing the status of the processes currently
running in the system.
Function
The ps command is used to view the status of the processes currently running in the system..

System
Command Format
ps option
Option Description
l -e : to view the status of all the processes that are running in the system
l -l: to view the running processes in a long-form list
l -u user: to view the process status of a specific user
l -f : to view all the status information about the processes that are running in the system
Example
l To view the status of all the running processes controlled by the login device (the terminal),
run the following command:
# ps
PID TTY TIME CMD
13726 pts/5 0:00 ksh
l To view the complete information about the active processes, run the following command:
# ps -f
UID PID PPID C STIME TTY TIME CMD
sybase 13726 13724 0 08:44:35 pts/5 0:00 -ksh
l To view the N2000 DMS processes, run the following command:

# ps -ef | grep imap
root 22344 1 0 17:49:43 ? 0:03 imapsvcd -name devdoc_agent
-
sysagent DEFAULTSYSAGENT -port 31105 -agentid 0
root 22374 1 0 17:49:48 ? 0:02 imapsvcd -name am_agent -
sysa
gent DEFAULTSYSAGENT -port 31131 -agentid 0
root 22346 1 0 17:49:43 ? 0:01 imapsvcd -name em_agent -
sysa
gent DEFAULTSYSAGENT -port 31002 -agentid 0
root 22342 1 0 17:49:43 ? 0:11 imapsvcd -name cmdc_agent -
sy
sagent DEFAULTSYSAGENT -port 31103 -agentid 0
root 22355 1 0 17:49:45 ? 0:11 imapsvcd -name ifms_agent -
sy
sagent DEFAULTSYSAGENT -port 31011 -agentid 119
root 22338 1 0 17:49:42 ? 0:02 imapsvcd -name 3gpp_agent -
sy
......
NOTE
l After you run the ps command without any parameters, the screen displays information about all
running processes that are controlled by the login device (terminal).
l After you specify the -f parameter, more information is displayed. The information includes the user
name (UID), process ID (PID), parent process ID (PPID), technical number that indicates the
running time of the process (C), process start time (STIME), name of the terminal that activates the
process (TTY), and the process name (CMD). If TTY displays ?, infer that this process is not associated
with the terminal.
l To view all the processes related to specific characters, for example, the process related to the N2000
DMS, run the grep command with the ps command.

System
kill Command
This topic describes the kill command used for terminating one or more processes.
Function
The kill command is used to terminate a process.
Command Format
kill option process No.
Option Description
l -l : lists the names of all the signals
l -s signal: sends a signal named signal to the processes
Process No.: the ID of the process to be terminated, that is, the process ID
Example
l To list all the signal names, run the following command:
# kill -l
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGUSR1
17) SIGUSR2 18) SIGCHLD 19) SIGPWR 20) SIGWINCH
21) SIGURG 22) SIGIO 23) SIGSTOP 24) SIGTSTP
25) SIGCONT 26) SIGTTIN 27) SIGTTOU 28) SIGVTALRM
l To terminate the process with PID as 256, run the following command:
# kill -s KILL 256
NOTE
l The previous signal names can be expressed by code.

For example, -1 for HUP, -2 for INT, -3 for QUIT, -9 for KILL, -15 for TERM. The signal
KILL can be replaced with -9.
This signal is the most frequently used one in the kill command, and thus it has the highest priority.
The default signal 15 is used when no option is specified for the kill command. Run the following
command to terminate the process with the PID as 256:
# kill -9 256
l Run the ps command to check the execution of the kill command by listing the PIDs of the terminated
processes.
l The kill command may lead to a data loss. Run this command with care.
who Command
This topic describes the who command used for reporting the login information about all the
users in the current system.

System
Function
The who command reports the login information about all the users in the current system.
Command Format
who Option
Option Description
l -b : display the system date and time of the last startup
l -m: display the related information about the users who run the command (the same as the
command who with two parameters am i
am i: display the login information about the users who run the command
Example
l Display the login information about all the users in the current system:
# who
root pts/3 Feb 4 10:08 (10.129.16.60)
sybase pts/5 Feb 4 08:45 (10.129.28.44)
root pts/6 Feb 4 11:25 (10.129.16.60)
l Display the login information about the users who run the command:
# who am i
sybase pts/5 Feb 4 08:45 (10.129.28.44)
or:
# who -m
sybase pts/5 Feb 4 08:45 (10.129.28.44)
whereis Command
This topic describes the whereis command used for viewing the location of a source file, binary
file, and online help of a command.
Function
The whereis command is used to view the location of a source file, binary file, and online help
of a command.
Command Format
whereis option command
Option Description
l -b : to view the location of the binary file
l -m: to view the location of the help manual
l -s: to view the location of the source file

System
command: the command for which the location is to be displayed
Example
l To view the exact location of files of various versions for the ls command, run the following
command:
# whereis ls
ls: /usr/bin/ls /usr/ucb/ls /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
l To view the exact location of the binary file for the ls command, run the following
command:
# whereis -b ls
ls: /usr/bin/ls /usr/ucb/ls
l To view the exact location of the help manual for the ls command, run the following
command:
# whereis -m ls
ls: /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
which Command
This topic describes the which command used for viewing the location where a command is run.
Function
The which command is used to view the location where a command is run. The result may be
an absolute path or alias of the command found in the user environment variant PATH.
Command Format
which command
Example
To view the position where the commands pwd, who, and which are run, run the following
command:
# which pwd who which

/usr/bin/pwd
/usr/bin/who
/usr/bin/which
NOTE
If the command to be located does not exist in the file, the following error messages are displayed after
you run the which command:
# which qqqq
no qqqq in /usr/bin /usr/ucb /etc
hostname Command
This topic describes the hostname command used for viewing or setting the host name.

System
Function
The hostname command is used to view or set the host name.
Command Format
hostname host name
Example
To view the host name, run the following command:
# hostname
NOTE
If you run the hostname command without parameters, the host name of the equipment is displayed. If
you run the hostname command with parameters, the host name is set. Only the super user can run the
hostname command.
uname Command
This topic describes the uname command used for viewing the information about the operating
system.
Function
The uname command is used to view the information about the operating system. If you run this
command without parameters, only the name of the operating system is displayed. If you run
this command with parameters, more details about the operating system are displayed.
Format
uname option
Option Description
The options of the uname command can be combined. Add the prefix - before the options. Table
A-22 lists some frequently used options.
Table A-22 Description of the uname options
Option Description
-a Views all the information.
-i Views hardware information.
-m Views the name of the equipment hardware.

It is recommended that -p be used instead of
-m.
-n Views the name of the network equipment.

System
Option Description
-p Views the ISA of the host or the type of the

processor.
-r Views the serial number of the operating

system of the host.
-s Views the name of the operating system of the

host (it is the default option).
-v Views the version of the operating system of

the host.
-S system_name Sets the host name of the machine.

system_name stands for the host name set by
the user.
Example
To view the name, version, and serial number of the operating system on the host, run the
following command:
# uname -svr
ifconfig Command
This topic describes the ifconfig command used for viewing the IP address of the host.
Function
The ifconfig command is used to view the IP address of the host.
Command Format
ifconfig option
Option Description
-a: to view all the address information
Example
To view the IP address of the host, run the following command:
# ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232inet 127.0.0.1 netmask
ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu 1500 inet
129.9.169.143 netmask ffff0000 broadcast 129.9.255.255
hme0:1:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet
129.6.253.136 netmask ffff0000 broadcast 129.6.255.255

System
NOTE
In the previous output, the IP address of the displayed host is 129.9.169.143, and the logical IP address is
129.6.253.136. In the UNIX system, a network adapter can bind several logical IP addresses, which realizes
communications between different network segments.
script Command
This topic describes the script command used for recording in a script file all the screen input
and output that occur from the time when the script command is run to the time when the exit
command is entered.
Function
CAUTION
Close the script file before running the exit command to terminate the recording of the screen
I/O. If you do not close the script file, the script file builds up and hinders the normal operation
of the system.
Record in a script file all the screen input and output that occur from the time when the script
command is run to the time when the exit command is entered. The script command is helpful
for programming and debugging.
Format
script option file
Option Description
-a: appends the screen I/O content to a file. If you do not set this parameter, the screen I/O
overwrites the content of the file.
file: the file used to save the screen I/O content. If you do not specify the file name, the screen
I/O content is saved to the typescript file.
Example
To save the screen I/O content in the default destination file typescript, run the following
commands:
# script
Script started, file is typescript
# ps
PID TTY TIME CMD
775 pts/8 0:00 ksh
# pwd
/export/home

System
# date
Mon Feb 4 19:12:14 GMT 2002
# exit
Script done, file is typescript
To view the content of the typescript file, run the following command:
# cat typescript
Script started on Mon Feb 04 19:11:49 2002
$ ps
PID TTY TIME CMD
775 pts/8 0:00 ksh
$ pwd
/export/home
$ date
Mon Feb 4 19:12:14 GMT 2002
$ exit
exit
script done on Mon Feb 04 19:12:24 2002
date Command
This topic describes the date command used for viewing the current date and time of the system.
Function
The data command is used to view the current date and time of the system. The super user can
run the date command to set the system date and time.
Format
date option +format
Option Description
l -u: to use the Greenwich mean time.
l +format: to specify the command output format.
Table A-23 describes the format of the command output.
Table A-23 Format of the command output
Format Description
%h Abbreviation of the month: from January to December
%j A day in a year: from 001 to 366
%n Switch to next line
%t The tab key
%y The last two digits of the year: from 00 to 99
%D Output format of the date: month/date/year

System
Format Description
%H Hour: from 00 to 23
%M Minute: from 00 to 59
%S Second: from 00 to 59
%T Output format of time: hour:minute:second
Example
l To view the current date and time of the system, run the following command:
date
Mon Feb 4 20:26:16 GMT 2002
l To view the current system date and time in the Greenwich Mean Time, run the following
command:
date -u
Mon Feb 4 12:27:26 GMT 2002
l To view the current date of the system in the format of month/day/year, run the following
command:
date +%D
02/04/02
bc Command
This topic describes the bc command used for simple calculation.
Function
The bc command is used to perform a simple calculation.
Example
To multiply 4 by 5, run the following command:
# bc
4*5
20
NOTE
To get the result, run the bc command, and then press Enter. Type the formula 4*5, and then press
Enter. The result is displayed on the screen. Press Ctrl+D to exit from the bc program.
prtconf Command
This topic describes the prtconf command used for checking the system configuration.

System
Function
The prtconf command is used to check the system configuration.
Format
prtconf option device path
Instance
l Check all the configuration information about the system.
# prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 4096 Megabytes
System Peripherals (Software Nodes):
SUNW,Netra-240
scsi_vhci, instance #0
packages (driver not attached)
SUNW,builtin-drivers (driver not attached)
deblocker (driver not attached)
disk-label (driver not attached)
terminal-emulator (driver not attached)
dropins (driver not attached)
kbd-translator (driver not attached)
obp-tftp (driver not attached)
SUNW,i2c-ram-device (driver not attached)
SUNW,fru-device (driver not attached)
SUNW,asr (driver not attached)
ufs-file-system (driver not attached)
chosen (driver not attached)
openprom (driver not attached)
client-services (driver not attached)
options, instance #0
aliases (driver not attached)
memory (driver not attached)
virtual-memory (driver not attached)
SUNW,UltraSPARC-IIIi, instance #0 (driver not attached)
memory-controller, instance #0
SUNW,UltraSPARC-IIIi, instance #1 (driver not attached)
memory-controller, instance #1
pci, instance #0
network, instance #0
pci, instance #1
isa, instance #0
flashprom (driver not attached)
rtc (driver not attached)
i2c, instance #0
i2c-bridge (driver not attached)
i2c-bridge (driver not attached)
motherboard-fru-prom, instance #0 (driver n
chassis-fru-prom, instance #1 (driver not a
alarm-fru-prom, instance #2 (driver not att
power-supply-fru-prom, instance #3 (driver
power-supply-fru-prom, instance #4 (driver
dimm-spd, instance #5 (driver not attached)
rscrtc (driver not attached)
nvram, instance #9 (driver not attached)
idprom (driver not attached)
gpio, instance #0 (driver not attached)

System

power, instance #0
serial, instance #0
serial, instance #1 (driver not attached)
rmc-comm, instance #0
pmu, instance #0
i2c, instance #0
gpio, instance #0
usb, instance #0
ide, instance #0
disk (driver not attached)
cdrom (driver not attached)
sd, instance #3
pci, instance #2
scsi, instance #0
tape (driver not attached)
sd, instance #0
sd, instance #1 (driver not attached)
st, instance #1 (driver not attached)
ses, instance #1 (driver not attached)
scsi, instance #1
tape (driver not attached)

System

pci, instance #3
iscsi, instance #0
pseudo, instance #0
prstat Command
This topic describes the prstat command used for viewing the CPU usage.
Function
The CPU usage may be high when a large number of NE alarms are reported in a short period
or when the performance data is high. This command is used to find out the cause of these alarms.
Permitted Users
Users root, omcuser, and dbuser are authorized to run the prstat command.
Example
-bash-3.00$ prstat
The command result contains the CPU usage of each process.
A.2.6 Commands for Solaris Network Communication

This describes common network communication commands.
Table A-24 shows the common network communication commands.

System
Table A-24 Common network communication commands

Use To
ping IP address Test the network connectivity.
telnet IP address / domain name Log in to a remote computer through Telnet.
ftp IP address / domain name Transfer a file through FTP.
finger [user name] @domain name/IP View information about the Solaris user.
address
netstat [option] Show the network status.
route [option] Maintain the routing table.
ping Command
This topic describes the ping command used for checking the connection of networks.
Function
The ping command is used to check the physical connection of the network when the
communication between a user computer and the hosts in the network is interrupted.
Format
ping IP address of a host
Example
Check the physical connection between the current host and the host whose IP address is
129.9.0.1.
# ping 129.9.0.1
129.9.0.1 is alive
The Internet Control Message Protocol (ICMP) is used through the ping command to check the
network connection. An ICMP echo request message is sent to a specific host to request an ICMP
echo response message. If the response message is not received within a specified time, the
Host unreachable message is displayed on the screen.
The Host unreachable message is displayed in the following cases:
l The specified host is invalid.

l The network cables are not correctly connected.
l The two communicating hosts do not support the same communication protocol.
To analyze the causes, run the ping command to connect to other hosts in the same network
segment. If the ping command is successful, you can infer that the connection is functional. In
this case, check the physical connection and the operational status of the specified host. If the
ping command fails, check whether the physical network connection of the current host is secure
or whether the TCP/IP protocol is set correctly only for Windows 95 users.

System
telnet Command
This topic describes the telnet command used for logging in to the remote UNIX host from the
local computer.
Function
NOTE
Before running the telnet command, ensure that a local computer is connected to the remote UNIX host
according to the TCP/IP protocol.
Telnet is the software used to log in to remote UNIX hosts through network connection. Telnet
takes the local computer as a simulated terminal of the remote UNIX host and enables you to
log in to the remote server from the local computer. After you log in to the remote UNIX host
successfully through telnet, you become a remote simulated terminal user and you can use the
local computer as a real UNIX terminal. In this case, the resources and functions available and
the operating mode depend on the settings of the remote host and the access privileges of the
login account.
Command Format
telnet IP address or domain name
l IP address: the IP address of a remote UNIX host
l Domain: the domain name of a remote UNIX host
Example
Run the telnet command on a local computer and log in to a remote UNIX host. Assume that
the IP address of the UNIX host is 129.9.169.143.
On the local computer, choose Start > Run. Enter telnet 129.9.169.143 and click OK. The
Telnet dialog box appears and prompts you to enter the UNIX user name and password.
login: root
Password:root password
NOTE
Enter the password on the right of Password. The entered password is not displayed.
The subsequent steps are the same as those when you operate on the UNIX host.
ftp Command
This topic describes the ftp command used for transfering files between the local computer and
the remote host.
Function
The ftp command is used to transfer files between the local computer and the remote host. You
can transfer one or multiple files at a time between the remote UNIX system and the local
computer.

System
Format
ftp IP address or domain
l IP address: the IP address of the remote UNIX host
l Domain name: the domain name of the remote UNIX host
Example
Run the ftp command on the local computer. Assume that the IP address of the remote UNIX
host is 129.9.169.143.
Choose Start > Run on the local computer. In the displayed dialog box, enter ftp
129.9.169.143 and click OK. When the ftp window is displayed, enter the UNIX user name and
password.
User (129.9.169.143: (none) : ) ftpuser
Password:password of ftpuser
230 Login successful.
ftp>
NOTE
Enter the password after Password: . The password is not displayed.
Enter the ftp command behind the prompt ftp>. Table A-25 describes the ftp commands that
are commonly used.
Table A-25 Common ftp commands
ftp Command Description
!command Use a local command and return to ftp

immediately.
?|help command View the command help.
ascii Transfer files in ASCII format (default).
binary Transfer files in binary format.
cd folder Modify the remote folder.
close Break the remote connection.
dir remote-directory local-file View the remote directory. If there is a local

file, save the result to the local file.
get file1 file2 Copy the remote file1 to the local file2.
cd folder Modify the local folder.
ls r-folder l-file Same as dir, but the display format is

different.

System
ftp Command Description
mget several files Copy several remote files to the local

computer.
open IP address or domain Reestablish a connection.
put file1 file2 Copy the remote file1 to the local file2.
pwd List the folders of the current remote host.
quit|bye Exit from the ftp.
status View the current ftp status.
l Copy all the files in the path C:\mydoc on the local computer to the /usr/local/tmp folder
on the remote host.
ftp> binary
ftp> lcd c:\mydoc
ftp> cd /usr/local/tmp
ftp> mput *.*
l Copy the .login file in the /usr/home/rms folder on the remote host to the path C:
\mydoc folder on the local computer.
ftp> ascii
ftp> lcd c:\temp\from
ftp> cd /usr/home/rms
ftp> get .login
l Copy all files in the /usr/home/rms folder on the remote computer to the path C:\temp
\from on the local computer in binary format.
ftp> binary
ftp> lcd c:\temp\from
ftp> cd /usr/home/rms
ftp> mget *
l To exit ftp.
ftp> quit

System
CAUTION
The Telnet and FTP protocols belong to the TCP/IP family. They are the protocols at the
application layer. They work in client/server mode. The telnet/ftp program running on the local
computer is a telnet/ftp client program. The telnet/ftp program connects to the server program
in the remote host through the TCP/IP protocol. Any system installed with the telnet/ftp server-
side software can serve as a remote host. In addition to the default network protocol TCP/IP, the
UNIX system supports the Telnet/FTP protocols. Because a UNIX host is installed with both
the telnet/ftp server software and the client software, the UNIX host can serve as either a telnet/
ftp server or a telnet/ftp client.
finger Command
This topic describes the finger command used for viewing the information about the online users
who are using the UNIX system.
Function
The finger command is used to view the information about online users of the UNIX system.
Command Format
finger user name@host domain|IP address
l user name: the user that has currently logged in to the local system.
l host domain: the UNIX host domain.
l IP address: the IP address of the UNIX host.
Example
Table A-26 lists some common examples of the finger command.
Table A-26 Examples of the finger command
Example Description
# finger View the information about all local users.
# finger root View the information about user root.
# finger @omcsyb2 View the information about all users in the

host omcsyb2.
# finger @omcsyb2.huawei.com.cn View the information about all users in the

host omcsyb2.huawei.com.cn.
# finger abc@omcsyb2 View the information about user abc in the

host omcsyb2.

System
Example Description
# finger abc@10.10.10.1 View the information about user abc in the

host 10.10.10.1.
netstat Command
This topic describes the netstat command used for displaying the current network status.
Function
The netstat command is used to display the current network status. The netstat command is
powerful but complex in format. This describes common applications of the netstat command.
Command Format
netstat options
Option Description
l For viewing all the sockets and routing tables (netstat -anv)
-a: views all socket information.
-n: views the information by number. If you do not specify this parameter, the
information is displayed by logical name.
-v: views the information about sockets and routing tables of the additional information.
l For viewing the IP address of the network adapter (netstat -i -I interface interval
interval)
-i: views the information about the network interface.
-I interface: specifies an interface, for example, hme0:1
interval: indicates a time interval.
l For viewing the routing table status (netstat -r -anv)
-r: views the information about the routing table.
-anv: refers to For viewing all the sockets and routing tables.
l For viewing the broadcast information (netstat -M -ns)
-M: views broadcast routing tables.
-s: summarizes the status of each protocol.
l For viewing the DHCP status (netstat -D -I interface)
-D: views the DHCP information.
Example
Use the command netstat -rn to view the information about the routing tables:
root@ts-007 # netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface

System
10.105.28.0 10.105.28.202 U 4 2 hme0

10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 896 lo0
A router can be in any of the following five different flags: U, G, H, D, and M, as described in
Table A-27.
Table A-27 Description of routing flags
Flag Description
U U indicates that a route is currently available.
G G indicates that a route is destined for a gateway such as a router.

If this flag is not set, you can infer that the destination is connected directly.
Flag G distinguishes between direct and indirect routes. Flag G is unnecessary
for direct routes. The difference is that the packet sent through a direct route
carries both the destination IP address and the link-layer address. In the packet
sent through an indirect route, however, the IP address points to the destination
and the link layer address points to the gateway (for example, the next router).
H H indicates a route destined for a host. That is, the destination address is a
complete host address.
If this flag is not set, you can infer that the route leads to a network and that
the destination address is a network address: either a network number or a
network. The part in the address for the host is 0. When you search the routing
table for an IP address, the host address must exactly match the destination
address. The network address, however, is required to match only the network
number and subnet number of the destination address.
D D indicates that a route is created by a redirected packet.
M M indicates that a route is modified by a redirected packet.
The Ref (Reference count) column lists the number of routing progresses. The protocol for
connection, such as TCP, requires a fixed route when a connection is established. If the telnet
connection is established between the host svr4 and the host slip, the Ref is 1. If another telnet
connection is established, its value is changed to 2.
The next column (Use) displays the number of packets sent through a specified route. After you
run the ping command as the unique user of this route, the program sends five groups and the
number of packets is displayed as 5. The last column (Interface) indicates the name of the
local interface.
The second row of the output is a loop-back interface. The interface name is permanent set to
lo0. Flag G is not set because the route is not destined for a gateway. Flag H indicates that the
destination address, 127.0.0.1, is a host address and not a network address. Because flag G is
not set, the route here is a direct route and the gateway column shows the outgoing IP address.
Each host has one or multiple default routes. That is, if a particular route is not found in the table,
the packet is sent to the router. In addition, the current host can access other systems through
the Sun router (and the slip link) on the internet, based on the settings of the routing table. The
flag UG refers to the gateway.

System
route Command
This topic describes the route command used for changing the maintenance routing table.
Function
The routing table relays IP address between network segments. The route command is used to
modify and maintain the routing table.
Format
route -fnvq command modifiers args
route -fnvq add | change | delete | get host/net destination gateway args
route -n monitor
route -n flush
NOTE
The meaning of "|" is the same as that of the word "or".
Options of the route command can be combined. Table A-28 lists some common options.
Table A-28 Description of the route commands

Option Description
-f Refresh routing tables for all gateways.
-n View the information in characters instead of symbols.
-v View the additional information.
-q Suspend all outputs.
-commond Refer to the add, chang, flush (clear the gateways in the
routing table), get or monitor.
-destination Destination network segment. For example, 10.0.0.0 stands

for section 10, and 10.11.0.0 stands for section 10.11.
-gateway Indicate the IP address of the gateway.
net Indicate the network segment. For example, 10.11.12.0

stands for section 10.11.12.
host Indicate the IP address of the host.
Example
l Obtain the routing information about network segment 10.
root@ts-007 # route -n get 10.0.0.0

System
route to: 10.0.0.0

destination: 10.0.0.0
mask: 255.0.0.0
gateway: 10.105.31.254
interface: hme0
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
0 0 0 0 0 0 1500
0
l Clear the gateways in the routing table.

root@ts-007 # route -n flush
10 10.105.31.254 done

Routing Table:
-------------------- -------------------- ----- ----- ------ ---------
10.105.28.0 10.105.28.202 U 4 6 hme0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 1500 lo0
root@ts-007 # telnet 10.129.3.4

Trying 10.129.3.4...
telnet: Unable to connect to remote host: Network is unreachable
After the gateways in the routing table are cleared, the network segments beyond
10.105.28.202/34 are no longer accessible.
l Add a routing record.
root@ts-007 # route add 129.9.0.0 10.105.28.202
add net 129.9.0.0: gateway 10.105.28.202

Routing Table:
-------------------- -------------------- ----- ----- ------ ---------
10.105.28.0 10.105.28.202 U 4 2 hme0
129.9.0.0 10.105.28.202 UG 0 0
10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 313 lo0
NOTE
129.9.0.0 10.105.28.202 UG 0 0 is the newly-added routing record.

l Modify the routing table.
root@ts-007 # route change 129.9.0.0 1.2.3.4
change net 129.9.0.0: gateway 1.2.3.4

Routing Table:
-------------------- -------------------- ----- ----- ------ ---------
10.105.28.0 10.105.28.202 U 4 2 hme0
129.9.0.0 1.2.3.4 UG 0 0
10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 445 lo0
NOTE
129.9.0.0 1.2.3.4 UG 0 0 is the routing record of the modified gateway.

System
Administrator Guide - Solaris B N2000 DMS Services and Processes
B N2000 DMS Services and Processes
This describes the details of the N2000 DMS services and processes.
B.1 N2000 DMS (iMAP) Processes
This describes the services and processes related to the iMAP platform.
B.2 N2000 DMS Processes
This describes the N2000 DMS services and processes.
B.3 N2000 DMS Services and Ports
This describes the services and ports related to the N2000 DMS.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential B-1

System
B N2000 DMS Services and Processes Administrator Guide - Solaris
B.1 N2000 DMS (iMAP) Processes

This describes the services and processes related to the iMAP platform.
B.1.1 Message Distribution Process: mdp

B.1.2 System Monitoring Process: EmfSysMoniDm
B.1.3 Scheduled Task Process: EmfSchdSvr
B.1.4 Security Management Process: EmfSecuDm
B.1.5 Topology Process: EmfTopoDm
B.1.6 Fault Process: EmfFaultDm
B.1.7 Alarm Synchronization Process: EmfFaultSynDm
B.1.8 Alarm Agent Process: EmfAlarmAgent
B.1.9 Trap Report and Explanation Process: EmfTrapReceiver
B.1.10 Real-Time Performance Process: EmfPerfDm
B.1.11 Third-Party Device Configuration Management Process: EmfGnlDevDm
B.1.12 Device Access Proxy Process: EmfProxyServer
B.1.13 SNMP Forwarding Process: ForwardAgent
B.1.14 Database Backup Process: EmfDBBackup
B.1.15 Test Process: EmfExamDm
B.1.16 Project Document Process: EmfProjDocDm
B.1.17 Northbound Interface Module (SNMP) Process: SNMPAgent
B.1.18 Northbound Interface Module (CORBA) Process: iAF_Agent
B.1.19 Northbound Interface Module (XML) Process: iAF_XMLAgent
B.1.20 CORBA Notification Service Process: iagent_nt
B.1.21 CORBA Naming Service Process: Naming_Service
B.1.22 Log Forwarding Process: EmfSyslogAgent
B.1.1 Message Distribution Process: mdp

Function
This process enables you to distribute messages of each process.
You must start this process and cannot stop it.
Component
Core Platform and core platform patch components
B-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
Database
None
Program File
Path File
$N2000ROOT/server/bin mdp
Configuration File
None
Log File
Path Name Remarks
$N2000ROOT/server/log Naming rule: All logs of application

iMAPMdp_p2_date_time.l processes are stored in this
og path.
Occupied Port
Port 9800 is used in common communication mode, and port 9803 is used in SSL communication
mode.
Dependency Process
None
B.1.2 System Monitoring Process: EmfSysMoniDm
Function
This process enables you to start, stop, and monitor the processes on the N2000 DMS server. In
addition, this process monitors the running status of the memory, CPU, and database.
Component
Database
SecurityDB

System
Program File
Path File
$N2000ROOT/server/bin EmfSysMoniDm
Configuration File
Path File
$N2000ROOT/server/conf/sysmoni It varies according to the monitored

process.
Log File
Path Name Remarks

iMAPSysMoni_p65_date_t processes are stored in this
ime.log path.
Occupied Port
None
Dependency Process
dataserver
B.1.3 Scheduled Task Process: EmfSchdSvr

Function
This function enables you to manage scheduled tasks of the NMS.
Component
Database
LogDB

System
Program File
Path File
$N2000ROOT/server/bin EmfSchdSvr
Configuration File
Path File
$N2000ROOT/server/conf emfschdsrv.cfg
$N2000ROOT/server/conf/sysmoni monisvhdsvr.cfg
Log File
Path Name Remarks
$N2000ROOT/server/log Naming rule: Application message

iMAPSchdSvr_p256_date_ processing logs and thread
time.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
mdp
B.1.4 Security Management Process: EmfSecuDm
Function
This process enables you to perform user management, user group management, authority
management, and log management.
Component
Database
SecurityDB and LogDB

System
Program File
Path File
$N2000ROOT/server/bin EmfSecuDm
Configuration File
Path File
$N2000ROOT/server/conf emfsecu.cfg
$N2000ROOT/server/conf/sysmoni moniemfsecu.cfg
Log File
Path Name Remarks

iMAPSecu_p52_date_time. processing logs and thread
log status logs are stored in this
path.
Occupied Port
None
Dependency Process
None
B.1.5 Topology Process: EmfTopoDm
Function
This process enables you to manage the device topology in the network according to the space,
logics, or network deployment.
Component
Database
TopoDB

System
Program File
Path File
$N2000ROOT/server/bin EmfTopoDm
Configuration File
Path File
$N2000ROOT/server/conf emftopo.cfg
$N2000ROOT/server/conf/sysmoni moniemftopo.cfg
Log File
Path Name Remarks

iMAPTopo_p51_date_time processing logs and thread
.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
EmfSecuDm
B.1.6 Fault Process: EmfFaultDm
Function
This process enables you to receive, query, confirm, save, and dump alarms of the device and
N2000 DMS, and perform correlation analysis.
Component
Database
FaultDB

System
Program File
Path File
$N2000ROOT/server/bin EmfFaultDm
Configuration File
Path File
$N2000ROOT/server/conf emffault.cfg
$N2000ROOT/server/conf emffloatip.cfg
$N2000ROOT/server/conf/sysmoni moniemffault.cfg
Log File
Path Name Remarks

iMAPFault_p56_date_time processing logs and thread
.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
EmfTopoDm
B.1.7 Alarm Synchronization Process: EmfFaultSynDm
Function
This function enables you to synchronize NMS history alarms.
Component
Database
FaultDB

System
Program File
Path File
$N2000ROOT/server/bin EmfFaultSynDm
Configuration File
None
Log File
None
Occupied Port
None
Dependency Process
EmfFaultDm
B.1.8 Alarm Agent Process: EmfAlarmAgent

Function
This function enables you to enable or disable the trap receiver of the NMS.
Component
Database
None
Program File
Path File
$N2000ROOT/server/bin EmfAlarmAgent
Configuration File
Path File
$N2000ROOT/server/conf/sysmoni moniemfalmagent.cfg

System
Log File
Path Name Remarks

iMAPAlarmAgent_p271_d processing logs and thread
ate_time.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
None
B.1.9 Trap Report and Explanation Process: EmfTrapReceiver
Function
After you create a trap receiver and enable it, the NMS creates a EmfTrapReceiver process.
Component
Database
None
Program File
Path File
$N2000ROOT/server/bin EmfTrapReceiver
Configuration File
None
Log File
Path Name Remarks
$N2000ROOT/server/log Naming rule of the start log: All logs of application

iMAPTrapReceiver_p1000 processes are stored in this
0_r4_date_time.log path.

System
Path Name Remarks
$N2000ROOT/server/log Naming rule of the running All logs of application

log: processes are stored in this
iMAPTrapReceiver_p1000 path.
0_r4_Comm_date_time.log
Occupied Port
l UDP monitoring port: 162-65535. The default port is 162.
l Service port: 11000-12000. The default port is 11000.
Dependency Process
l EmfFaultDm
l EmfAlarmAgent
B.1.10 Real-Time Performance Process: EmfPerfDm

Function
This process enables you to collect, query, and measure the performance data of the objects
managed by the N2000 DMS.
This process can be stopped if you do not need to monitor the performance in real time.
Component
Database
PerfDB
Program File
Path File
$N2000ROOT/server/bin EmfPerfDm
Configuration File
Path File
$N2000ROOT/server/conf emfperf.cfg
$N2000ROOT/server/conf/sysmoni moniemfperf.cfg

System
Log File
Path Name Remarks

iMAPPerf_p57_date_time.l processes are stored in this
og path.
Occupied Port
None
Dependency Process
None
B.1.11 Third-Party Device Configuration Management Process:

EmfGnlDevDm
Function
This process enables you to manage third-party devices on the N2000 DMS. For example, add
or delete a third-party device.
Component
Core Platform and core platform patch components.
Database
GnldevDB
Program File
Path File
$N2000ROOT/server/bin EmfGnlDevDm
Configuration File
Path File
$N2000ROOT/server/conf emfgnldev.cfg
$N2000ROOT/server/conf/sysmoni moniemfgnldev.cfg

System
Log File
Path Name Remarks

iMAPGnlDev_p48_date_ti processing logs and thread
me.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfFaultDm
B.1.12 Device Access Proxy Process: EmfProxyServer

Function
The agent function for device access is provided. This function enables you to connect to devices
on the client easily through the Transfer Control Protocol (TCP) such as the Telnet protocol and
File Transfer Protocol (FTP).
Component
Database
None
Program File
Path File
$N2000ROOT/server/bin EmfProxyServer
Configuration File
Path File
$N2000ROOT/server/conf emfproxy.cfg
$N2000ROOT/server/conf moniemfproxy.cfg

System
Log File
Path Name Remarks

iMAPProxy_date_time.log processing logs and thread
status logs are stored in this
path.
Occupied Port
9811
Dependency Process
None
B.1.13 SNMP Forwarding Process: ForwardAgent
Function
This process performs the transit function. It forwards the SNMP request to the SNMP device
managed by the N2000 DMS and return the response from the SNMP device.
You can stop this process if you do not need SNMP request forwarding.
By default, this process is stopped.
Component
Northbound Interface (SNMP) Server component
Database
None
Program File
Path File
$N2000ROOT/server/bin ForwardAgent
Configuration File
Path File
$N2000ROOT/server/conf/sysmoni moniforwadagent.cfg

System
Log File
Path Name Remarks

iMAPForwardAgent_date_ processing logs and thread
path.
Occupied Port
9826
Dependency Process
None
B.1.14 Database Backup Process: EmfDBBackup
Function
This process enables you to back up and recover the N2000 DMS database. The backup is
classified into two types: timing backup and manual backup.
Component
Database Backup Tool component
Database
None
Program File
Path File
$N2000ROOT/server/bin EmfDBBackup
Configuration File
Path File
$N2000ROOT/server/conf dbbaktools.cfg
$N2000ROOT/server/conf/dbback diskbak.cfg
$N2000ROOT/server/conf/sysmoni moniemfdbback.cfg

System
Log File
Path Name Remarks
$N2000ROOT/server/log/ Naming rule: Application message

dbback DBBackupDm_date_time.l processing logs and thread
og status logs are stored in this
path.
Occupied Port
9809
Dependency Process
None
B.1.15 Test Process: EmfExamDm
Function
This process enables you to configure and query the debug parameters of the N2000 DMS in
Telnet mode.
Component
Database
None
Program File
Path File
$N2000ROOT/server/bin EmfExamDm
Configuration File
Path File
$N2000ROOT/server/conf emfexam.cfg
$N2000ROOT/server/conf/sysmoni moniemfexam.cfg

System
Log File
Path Name Remarks

iMAPExam_p53_date_tim processing logs and thread
e.log status logs are stored in this
path.
Occupied Port
9810
Dependency Process
EmfSecuDm
B.1.16 Project Document Process: EmfProjDocDm
Function
This process enables you to obtain the complete information about the devices managed by the
N2000 DMS, and generate a project document.
Component
Database
Topo
Program File
Path File
$N2000ROOT/server/bin EmfProjDocDm
Configuration File
Path File
$N2000ROOT/server/conf/projdoc All the configuration files in the directory.
$N2000ROOT/server/conf/sysmoni monigsprojdoc.cfg

System
Log File
Path Name Remarks

iMAPProjDoc_p106_date_ processing logs and thread
path.
Occupied Port
None
Dependency Process
None
B.1.17 Northbound Interface Module (SNMP) Process:

SNMPAgent
Function
This process provides the SNMP proxy that can forward alarms to the upper level NMS or third-
party NMS.
Component
Northbound Interface (SNMP) Server component
Database
None
Program File
Path File
$N2000ROOT/server/bin SNMPAgent
Configuration File
Path File
$N2000ROOT/server/conf snmpagent.cfg
$N2000ROOT/server/sysmoni monisnmpagent.cfg

System
Log File
Path Name Remarks

iMAPSNMPAgent_p59_da processing logs and thread
te_time.log status logs are stored in this
path.
Occupied Port
9812
Dependency Process
EmfFaultDm
B.1.18 Northbound Interface Module (CORBA) Process: iAF_Agent
Function
This process implements the agent function of CORBA. It provides other NMSs with the
interfaces for obtaining the alarm, resource, and topology information.
Component
Northbound Interface Module (CORBA) component
Database
None
Program File
Path File
$N2000ROOT/server/bin iAF_Agent
Configuration File
Path File
$N2000ROOT/server/conf corbaagent.cfg
$N2000ROOT/server/conf inblicenseinfo.cfg
$N2000ROOT/server/conf/iaf_corbaconf All the configuration files in the directory.

System
Path File
$N2000ROOT/server/conf/sysmoni monicorbaagent.cfg
Log File
Path File Remarks

iMAPCORBAAgent_p70_ processing logs and thread
date_time.log status logs are stored in this
path.
$N2000ROOT/server/conf/ iAGENT.trace The northbound interface

iaf_xmlconf/var/logs module (CORBA) process
path.
$N2000ROOT/server/conf/ Naming rule: The backups of northbound

iaf_corbaconf/var/logs/ iAGENT.trace.date and interface module (CORBA)
tracebak time.tr process status logs are
stored in this path.
Occupied Port
9815
Dependency Process
iagent_nt
B.1.19 Northbound Interface Module (XML) Process:

iAF_XMLAgent
Function
This process implements the agent function of SOAP/XML. It provides other NMSs with the
interfaces for obtaining the alarm and topology information.
You can stop this process when no other NMSs need to interconnect to the N2000 DMS through
the SOAP/XML protocol.
Component
Northbound Interface Module (XML) component

System
Database
None
Program File
Path File
$N2000ROOT/server/bin iAF_XMLAgent
Configuration File
Path File
$N2000ROOT/server/conf/iaf_xmlconf All the configuration files in the directory.
$N2000ROOT/server/conf/sysmoni monixmlagent.cfg
Log File
Path Name Remarks

iMAPXMLAgent_p15_dat processing logs and thread
e_time.log status logs are stored in this
path.
$N2000ROOT/server/conf/ iAGENT.trace The northbound interface

iaf_xmlconf/var/logs module (XML) process
path.
$N2000ROOT/server/conf/ Naming rule: The backups of northbound

iaf_corbaconf/var/logs/ iAGENT.trace.date and interface module (XML)
tracebak time.tr process status logs are
stored in this path.
Occupied Port
10501
Dependency Process
EmfSecuDm

System
B.1.20 CORBA Notification Service Process: iagent_nt

Function
This process enables you to subscribe, filter and distribute CORBA notifications.
Component
Northbound Interface Module (CORBA) component
Database
None
Program File
Path File
$N2000ROOT/server/bin iagent_nt
Configuration File
Path File
$N2000ROOT/server/conf notify.cfg
$N2000ROOT/server/conf/sysmoni monicorbanotifyservice.cfg
Log File
None
Occupied Port
10510
Dependency Process
Naming_Service
B.1.21 CORBA Naming Service Process: Naming_Service

Function
This process enables you to search for a CORBA object by name.

System
Component
Northbound Interface Module(CORBA) component
Database
None
Program File
Path File
$N2000ROOT/server/bin Naming_Service
Configuration File
Path File
$N2000ROOT/server/conf/sysmoni monicorbanamingservice.cfg
Log File
None
Occupied Port
9816
Dependency Process
None
B.1.22 Log Forwarding Process: EmfSyslogAgent
Function
This process enables you to forward logs to the system log server.
Component
Database
None

System
Program File
Path File
$N2000ROOT/server/bin EmfSyslogAgent
Configuration File
Path File
$N2000ROOT/server/conf emfsyslogagent.cfg
$N2000ROOT/server/conf/sysmoni monisyslogagent.cfg
Log File
Path Name Remarks

EmfSyslogAgent_p149_dat processing logs and thread
e_time.log status logs are stored in this
path.
Occupied Port
None
Dependency Process
None
B.2 N2000 DMS Processes

This describes the N2000 DMS services and processes.
B.2.1 Layer 2 View Management Process: DmsL2VDm

B.2.2 N2000 DMS SysLog Collector Process: DmsSyslogCollector
B.2.3 Resource Management Process: DmfResDm
B.2.4 Command Line Interface Drive Process: DmfClidrvDm
B.2.5 Data Center Management Process: DmsDcDm
B.2.6 IP View Management Process: Dmsipdm
B.2.7 Cluster Management Process: UcmDm
B.2.8 ME60 and MA5200 Series Device Management Process: DmsMseDm

System
B.2.9 Quidway Device Management Process: DmsQvxDm

B.2.10 N2000 DMS RPR View Management Process: DmsrprDm
B.2.11 N2000 DMS Syslog Management Process: DmsSyslogDm
B.2.12 N2000 DMS NeMpls Management Process: NeMplsDm
B.2.13 Collector Module Process: ColAgentDm
B.2.14 Collector Process: CollectorDm
B.2.15 Collector Manager Process: CollectorMgrDm
B.2.16 General Configuration Template Process: GctlDm
B.2.17 Link Management Process: DmsLinkMgrDm
B.2.18 Performance Configuration Process: DmsPerfConfDm
B.2.19 Performance Probe Process: DmsPerfProbeDm
B.2.20 Performance Poll Process: DmsPerfPollDm
B.2.21 T&D Management Process: VasDiagDm
B.2.22 Service Management Process: DmsScDm
B.2.23 SecPolicyMgrDm
B.2.1 Layer 2 View Management Process: DmsL2VDm

Function
It indicates the Layer 2 view management process. It is a management background used to
manage the Layer 2 view.
Component
DMS Core Package
Database
DmsL2VDB
Program File
Path File
$N2000ROOT/server/bin DmsL2VDm

System
Configuration File
Path File
$N2000ROOT/server/conf/dms/l2vdm/init nml_l2vdm_init.cfg
Log File
Path: $N2000ROOT/server/log
Naming rule: DmsL2VDmdate_time.log
By default, the maximum number of log files is 10 and the maximum size of each log file is 5
MB. When the number of log files reaches the maximum, the log files are automatically
compressed to a .tar.gz file. If a process is restarted, the log files previously generated are
automatically compressed to a .tar.gz file. The maximum number of compressed files is 10. If
the number of compressed files reaches the maximum, the earliest compressed log file is deleted.
The compressed file containing the log file generated at the last startup of the process, however,
is not deleted.
Occupied Port
None
Dependency Process
l EmfTopoDm
l EmfSecuD
B.2.2 N2000 DMS SysLog Collector Process: DmsSyslogCollector
Function
It indicates the system log collector process. It collects the Syslogs of devices.
Component
Device Syslog Management
Database
DmsSysLogDB
Program File
Path File
$N2000ROOT/server/bin DmsSyslogCollector

System
Configuration File
Path File
$N2000ROOT /server/conf/about dmssyslogcollector.cfg
$N2000ROOT /server/conf/sysmoni monidmssyslogcollector.cfg
$N2000ROOT /server/conf/dms/ eml_syslogcollectordm_init.cfg

syslogcollectordm/init
Log File
Naming rule: DmsSyslogControldate_time.log
is not deleted.
Occupied Port
514
Dependency Process
None
B.2.3 Resource Management Process: DmfResDm

Function
It indicates the resource management process. It manages device resources.
Component
N2000 DMS Core Package
Database
DmfResDB;DmsResDB

System
Program File
Path File
$N2000ROOT/server/bin DmfResDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/resdm/ dmf_res_init_module.xml
init
Log File
Naming rule: DmfRes_PID_date_time.log
is not deleted.
Occupied Port
None
Dependency Process
None
B.2.4 Command Line Interface Drive Process: DmfClidrvDm
Function
It indicates the drive process of the command line interface.
Component
N2000 DMS Basic Package
Database
DmfResDB

System
Program File
Path File
$N2000ROOT/server/bin DmfClidrvDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/clidrvdm/init dmf_clidrv_dm_init.cfg
Log File
Naming rule: DmfCliDrv_PID_date_time.log
is not deleted.
Occupied Port
None
Dependency Process
None
B.2.5 Data Center Management Process: DmsDcDm
Function
It indicates the data center management process. It manages the device configuration files and
image programs.
Component
Database
DmsEmsDB

System
Program File
Path File
$N2000ROOT/server/bin DmsDcDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/dcdm/init eml_casdm_init.cfg
$N2000ROOT/server/conf/dms/dcdm/init eml_dcdm_init.cfg
Log File
Naming rule: DmsDcDmdate_time.log
is not deleted.
Occupied Port
None
Dependency Process
EmfSecuDm
B.2.6 IP View Management Process: Dmsipdm

Function
It indicates the IP view management process. It is a management background used to manage
the IP view.
Component
Database
IPViewDB

System
Program File
Path File
$N2000ROOT/server/bin dmsipdm
Configuration File
Path File
$N2000ROOT/server/conf/dms/ipdm/init nml_ipdm_init.cfg
Log File
The path is $N2000ROOT/server/log.
Logs are named in the format of dmsipdmDate_Time.log.
is not deleted.
Occupied Port
None
Dependency Process
l EmfTopoDm
l EmfSecuDm
B.2.7 Cluster Management Process: UcmDm
Function
It indicates the cluster management process. It is a management background used to manage the
clusters.
Component
HGMP Manager
Database
ClstDB

System
Program File
Path File
$N2000ROOT/server/bin UcmDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/clusterdm/init nml_clusterdm_init.cfg
$N2000ROOT/server/conf/dms/clusterdm/init
Log File
Naming rule: UcmDmdate_time.log
is not deleted.
Occupied Port
None
Dependency Process
l EmfTopoDm
l EmfFaultDm
l EmfSecuDm
B.2.8 ME60 and MA5200 Series Device Management Process:

DmsMseDm
Function
It indicates the management process of the ME60 and MA5200 devices. It manages the data of
the ME60 and MA5200 devices.
Component

System
Database
DmsEmsDB
Program File
Path File
$N2000ROOT/server/bin DmsMseDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/msedm/init dmf_mse_dm_init.cfg
$N2000ROOT/server/conf/dmf/msedm/init dmf_mse_init_groupware.xml
$N2000ROOT/server/conf/dmf/msedm/init dmf_mse_init_module.xml
Log File
Naming rule: DmfMse_PID_date_time.log
is not deleted.
Occupied Port
None
Dependency Process
l EmfTopoDm
l EmfSecuDm
B.2.9 Quidway Device Management Process: DmsQvxDm
Function
It indicates the NE management process of the Quidway devices. It manages the data of the
Quidway devices.

System
Component
Database
DmsEmsDB
Program File
Path File
$N2000ROOT/server/bin DmsQvxDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/qvxdm/init dmf_qvx_dm_init.cfg
$N2000ROOT/server/conf/dmf/qvxdm/init dmf_qvx_init_groupware.xml
$N2000ROOT/server/conf/dmf/qvxdm/init dmf_qvx_init_module.xml
Log File
Naming rule: DmfQvx_PID_date_time.log
is not deleted.
Occupied Port
l EmfTopoDm
l EmfSecuDm
Dependency Process
EmfTopoDm

System
B.2.10 N2000 DMS RPR View Management Process: DmsrprDm

Function
It indicates the N2000 DMS RPR view management process. It is a management background
used to manage the RPR view.
Component
Database
DmsRprDB
Program File
Path File
$N2000ROOT/server/bin DmsrprDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/rprdm/init nml_rprdm_init.cfg
Log File
Naming rule: DmsRPRDmdate_time.log
is not deleted.
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfFaultDm

System
l EmfTopoDm
B.2.11 N2000 DMS Syslog Management Process: DmsSyslogDm

Function
It indicates the N2000 DMS Syslog management process. It manages the receiving policy of
Syslogs.
Component
Device Syslog Management
Database
DmsSysLogDB
Program File
Path File
$N2000ROOT/server/bin DmsSyslogDm
Configuration File
Path File
$N2000ROOT /server/conf/about dmssyslogcontrol.cfg
$N2000ROOT /server/conf/sysmoni monidmssyslogdm.cfg
$N2000ROOT /server/conf/dms/syslogdm/ eml_syslogdm_init.cfg

init
$N2000ROOT /server/conf/dmf/ eml_perf_cmdreg.cfg

collectormgr/cmdreg eml_syslog_cmdreg.cfg
Log File
None
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfTopoDm

System
l EmfFaultDm
l CollectorDm
B.2.12 N2000 DMS NeMpls Management Process: NeMplsDm

Function
It indicates the N2000 DMS NE MPLS management process. It provides NE configuration for
the LSP service.
Component
N2000 DMS Basic Package
Database
None
Program File
Path File
$N2000ROOT/server/bin NeMplsDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/nemplsdm/ nemplsdm.cfg
init
Log File
None
Occupied Port
None
Dependency Process
None
B.2.13 Collector Module Process: ColAgentDm

Function
It indicates the collector module process. It sends alarms to the alarm manager.

System
Component
Database
None
Program File
Path File
$N2000ROOT/server/bin ColAgentDm
$N2000ROOT/server/bin CollectorDm
$N2000ROOT/server/conf/dmf/ dmf_collectormgr_dm_init.cfg
collectormgrdm/init
Configuration File
Path File
$N2000ROOT/server/conf/dmf/collectordm/init dmf_collector_dm_init.cfg
NOTE
This process uses certain fields in the configuration file.
Log File
Path: $N2000ROOT/server/conf/log
Naming rule: CollectorAgentdate_time.log
is not deleted.
Occupied Port
12101
Dependency Process
None

System
B.2.14 Collector Process: CollectorDm
Function
It indicates the collector process. It provides the N2000 DMS data collection function.
Component
Database
CollectorDB
Program File
Path File
Configuration File
Path File
$N2000ROOT/server/conf/dmf/collectordm/init dmf_collector_dm_init.cfg
Log File
Naming rule: DmfCollector_PID_date_time.log
is not deleted.
Occupied Port
None
Dependency Process
ColAgentDm

System
B.2.15 Collector Manager Process: CollectorMgrDm
Function
It indicates the collector manager process. It provides management to the collector.
Component
Database
GdclDB
Program File
Path File
$N2000ROOT/server/bin CollectorMgrDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/collectormgrdm/init dmf_collectormgr_dm_init.cfg
Log File
Naming rule: DmfCollectorMgr_PID_date_time.log
By default, the directory contains a maximum of 10 logs. These logs are used cyclically. The
size of each log is 5 MB.
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfTopoDm
l EmfFaultDm

System
B.2.16 General Configuration Template Process: GctlDm

Function
It indicates the general configuration template process. It provides configurations to templates.
Component
Database
GctlDm
Program File
Path File
$N2000ROOT/server/bin GctlDm
Configuration File
Path File
$N2000ROOT/server/conf/dmf/gctldm/init dmf_gctl_dm_init.cfg
Log File
Naming rule: DmfGctl_PID_date_time.log
By default, the directory contains a maximum of 10 logs. These logs are used cyclically. The
size of each log is 5 MB.
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfTopoDm

System
B.2.17 Link Management Process: DmsLinkMgrDm
Function
It indicates the link management process. It provides the functions of importing and creating
links.
Component
Database
DmsResDB
Program File
Path File
$N2000ROOT/server/bin DmsLinkMgrDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/linkmgr/init nml_linkmgr_init.cfg
Log File
None
Occupied Port
None
Dependency Process
l EmfSecuDm
l EmfTopoDm
B.2.18 Performance Configuration Process: DmsPerfConfDm
Function
It indicates the performance configuration process. It provides the function of managing the
resources, resource groups, templates, group templates, instances, and group instances.

System
Component
N2000 DMS Perf Management
Database
DmsPerfDB
Program File
Path File
$N2000ROOT/server/bin DmsPerfConfDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/perfconfdm/init dms_perfconfdm_init.cfg
Log File
Path:$N2000ROOT/server/log
Naming rule: DmsPerfConf_date_time.log.
By default, the directory contains a maximum of 10 logs. The size of each log is 5 MB. The
exceeded 10 log files are automatically compressed.
Occupied Port
8900, 9005, 9443, 9009
Dependency Process
None
B.2.19 Performance Probe Process: DmsPerfProbeDm
Function
It indicates the performance probe process. It provides the functions of managing tasks,
collecting data, and processing data.
Component

System
Database
DmsPerfProbeDB
Program File
Path File
$N2000ROOT/server/bin DmsPerfProbeDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/perfprobedm/init dms_perfprobedm_init.cfg
Log File
Naming rule: DmsPerfProbe_date_time.log.
Occupied Port
7321
Dependency Process
None
B.2.20 Performance Poll Process: DmsPerfPollDm
Function
It indicates the performance poll process. It provides the functions of managing tasks of resource
groups, obtaining and processing probe data, and dumping history data.
Component
Database
None

System
Program File
Path File
$N2000ROOT/server/bin DmsPerfPollDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/perfpolldm/init dms_perfpolldm_init.cfg
Log File
Naming rule: DmsPerfPoll_date_time.log.
Occupied Port
None
Dependency Process
None
B.2.21 T&D Management Process: VasDiagDm
Function
The process provides the functions of creating, deleting, modifying, and querying test suites,
test cases, and diagnosis policies in the diagnosis feature. The process also support the functions
of network scan, and exporting and dumping history data.
Component
diag
Database
VasDiagDB

System
Program File
Path File
$N2000ROOT/server/bin VasDiagDm.exe
Configuration File
Path File
$N2000ROOT/server/conf/dms/vas/diag/private vas_diag.cfg
Log File
Naming rule: VasDiag_PID_date_time.log
is not deleted.
Occupied Port
162
Dependency Process
mdp
B.2.22 Service Management Process: DmsScDm
Function
The process provides the functions of Customer Management, Composite Service, PW Service,
L3 VPN, and VPLS.
Component
Service Core Package
Database
DmsScDB

System
Program File
Path File
$N2000ROOT/server/bin DmsScDm
Configuration File
Path File
$N2000ROOT/server/conf/dms/sc/common sml_sc_dm_init.cfg
Log File
Naming rule:base_pID_date_time.log
is not deleted.
Occupied Port
162
Dependency Process
EmfSecuDm
B.2.23 SecPolicyMgrDm
Function
It indicates the centralized security policy process of the N2000 DMS. It provides centralized
policy configurations of devices.
Component
SecPolicyMgr
Database
VSMPolicyDB

System
Program File
Path File
$N2000ROOT/server/bin SecPolicyMgrDm
Configuration File
Path File
$N2000ROOT/server/conf smlsecpolicydm.cfg
Log File
Naming rule: SmlSecPolicy_P2074_date_time.log
is not deleted.
Occupied Port
None
Dependency Process
EmfSecuDm
B.3 N2000 DMS Services and Ports

This describes the services and ports related to the N2000 DMS.
B.3.1 Common Services and the Related Port Lists

B.3.2 List of Ports for System Services
B.3.3 List of Ports for Two-Node Cluster Services

System
B.3.1 Common Services and the Related Port Lists

Service Direction (with
Port/ the Server as
Service Protocol the Reference
Name Type Object) Description Remarks
Message 9800 and Server It is used to If routes or firewalls exist

Distributi 9803/ monitor all on the network between
on TCP background the client and server, you
Process processes and the need to check whether
non-SSL packets from the server are
connections with filtered.
the client.
Database 9809/ Server It is used for the If routes or firewalls exist

Backup TCP communication on the network between
Process between the the client and server, you
foreground and need to check whether
background of the packets from the server are
database backup filtered.
tool.
Exam 9810/ Server As a test process, If routes or firewalls exist

Process TCP it is used to on the network between
dynamically the client and server, you
modify the need to check whether
running packets from the server are
environment and filtered.
settings of other
processes.
Device 9811/ Server It serves as a If routes or firewalls exist

Access TCP proxy between the on the network between
Proxy client and host. the client and server, you
Process need to check whether
packets from the server are
filtered.
Northbou 9812/ Server It is used to listen If routers or firewalls exist

nd UDP to the access to the on the network between
Interface OSS/BSSs the N2000 DMS server
Module through the and OSS/BSSs, you need
(SNMP) SNMP NBI. If the to check whether packets
Process SNMP NBI from the N2000 DMS
function is not server ports are filtered.
enabled, this
interface cannot
be used.

System

Port/ the Server as
Northbou 9813/ Server It is used to If routers or firewalls exist

nd UDP receive trap on the network between
Interface packets. the N2000 DMS server
Module and OSS/BSSs, you need
(SYSLO to check whether packets
G) from the N2000 DMS
Process server ports are filtered.
Northbou 514/UDP Server It is used to If routers or firewalls exist

nd receive Syslog on the network between
Interface packets. the N2000 DMS server
Module and OSS/BSSs, you need
(SYSLO to check whether packets
G) from the N2000 DMS
Process server ports are filtered.
Interface 9815 and Server It is used to listen If routers or firewalls exist

Module 9817/ to the access to the on the network between
(CORBA TCP OSS/BSSs the N2000 DMS server
) Process through the and OSS/BSSs, you need
CORBA NBI. If to check whether packets
the CORBA NBI from the N2000 DMS
enabled, this
interface cannot
be used.
Naming 9816/ Server It is used to listen If routers or firewalls exist

Service TCP to the access to the on the network between
Process OSS/BSSs the N2000 DMS server
through the and OSS/BSSs, you need
the naming from the N2000 DMS
service is not server ports are filtered.
enabled, this
interface cannot
be used.
Forward 9826/ Server It is used to listen If routers or firewalls exist

Agent UDP to the access to the on the network between
Process OSS/BSSs the N2000 DMS server
SNMP NBI. If the to check whether packets
Forward NBI from the N2000 DMS
enabled, this
interface cannot
be used.

System

Port/ the Server as
Notificati 10510/ Server It is used to listen If routers or firewalls exist

on TCP to the access to the on the network between
service OSS/BSSs the N2000 DMS server
the notification from the N2000 DMS
service is not server ports are filtered.
enabled, this
interface cannot
be used.
Interface 10501/ Server It is used to listen If routers or firewalls exist

Module HTTP to the HTIPL on the network between
(XML) access of the OSS/ the N2000 DMS server
Process BSSs. If the XML and OSS/BSSs, you need
NBI function is to check whether packets
not enabled, this from the N2000 DMS
interface cannot server ports are filtered.
be used.
Platform COM1 or - It is used to send The N2000 DMS can

alarm COM2 data to the alarm shield the initialization of
box (assigned box through the the alarm box through the
service by the serial port. related configuration file.
user)
SNMP 161/UDP Server - Device It is used to send It is used to capture

get/set Bidirectional packets during the packets during the opening
opening of the of the DMA panel and to
DMA panel. check whether port 161 is
used in packets.
SNMP 162/UDP Server - Device It is used by the It is used to enable the

trap Unidirectional N2000 DMS device to send alarms to
server to receive the N2000 DMS, catch
the alarms sent packets, and check
from devices to whether port 162 is used in
the N2000 DMS. packets.

System

Port/ the Server as
Trap 11000-12 Device - Server It is used to -

receiver 000/UDP configure the port
occupied after
multiple trap
receivers are
configured. (It is
opened when the
N2000 DMS is
integrated with
the BMS. In
normal situations,
it does not need to
be opened.)
Report_S 8080/ Server It is used to If routers or firewalls exist

ystem_in HTTP receive the on the network between
stallation requests to access the N2000 DMS server
date the report server. and OSS/BSSs, you need
to check whether packets
from the N2000 DMS
server ports are filtered.
DMS TCP/ N2000 DMS It is used by the -

Perf 7321 server (Web)- client to open the
Probe Probe server related window.
Process Bidirectional
DMS TCP/ N2000 DMS It is used by the -

Performa 8900 client (Web)- client to open the
nce Web N2000 DMS related window.
Process server (Web)
Bidirectional
DMA 10000-10 Client - Device It is used by the -

004/UDP client to open the
router panel.
DMB 20000-20 Client - Device It is used by the -

004/UDP client to open the
switch panel.

System
B.3.2 List of Ports for System Services

Direction (with
the Server as the
Service Service Port/ Reference
Name Protocol Type Object) Description Remarks
FTP 20/TCP and 21/ Device - Server It is used for the -

TCP Bidirectional FTP service.
Telnet 23/TCP Device - Server It is used for the -

Bidirectional Telnet service.
iMAP 137/TCP, 138/ External server - It is used to set -

usage TCP, 139/TCP, N2000 DMS file sharing. If
(common) and 445/TCP server the file sharing is
Unidirectional not set, the
N2000 DMS
may fail to start.
Sybase 4100/TCP Performance It is the port used -

probe/report server by the Sybase
- N2000 DMS database.
server
Unidirectional
Sybase 4200/TCP Performance It is the port used -

backup probe/report server by the Sybase
- N2000 DMS backup database.
server
Unidirectional
PPTP VPN 1723/TCP Server - Device It can be -

service Bidirectional configured if the
PPTP VPN
service is used.
Otherwise, it
does not need to
be configured.
Terminal 3389/TCP Server - terminal It needs to be -

service device configured if the
Bidirectional terminal service
is used. (It needs
to be opened
when the
terminal service
is required, such
as remotely
accessing the
server from the
Windows 2000
desktop.)

System
B.3.3 List of Ports for Two-Node Cluster Services

Service Port/ Direction (with the
Service Protocol Server as the
Name Type Reference Object) Description Remarks
Veritas 4145/UDP Active server - It is used by the -

VVR standby server Veritas WR to
Bidirectional detect the
heartbeat
between the
active and
standby
servers.
Veritas 4145/TCP Active server - It is used by the -

VVR standby server Veritas WR to
Bidirectional perform TCP
listening.
Veritas 8989/TCP Active server - It is used by the -

vxrsyncd standby server Veritas
Bidirectional VxRSync to
perform
vxrsyncd
communicatio
n between the
active and
standby
servers.
hacl-hb 5300/TCP Active server - HA cluster -

standby server heartbeat.
Bidirectional
hacl-hb 5300/UDP Active server - HA cluster -

standby server heartbeat.
Bidirectional
hacl-gs 5301/TCP Active server - HA cluster -

standby server general
Bidirectional services.
hacl-gs 5301/UDP Active server - HA cluster -

standby server general
Bidirectional services.
hacl-cfg 5302/TCP Active server - HA cluster -

standby server configuration.
Bidirectional

System
Service Port/ Direction (with the

Service Protocol Server as the
Name Type Reference Object) Description Remarks
hacl-cfg 5302/UDP Active server - HA cluster -

standby server configuration.
Bidirectional
hacl- 5303/TCP Active server - HA cluster -

probe standby server probing.
Bidirectional
hacl- 5303/UDP Active server - HA cluster -

probe standby server probing.
Bidirectional
hacl-local 5304/TCP Active server - - -

standby server
Bidirectional
hacl-local 5304/UDP Active server - - -

standby server
Bidirectional
hacl-test 5305/TCP Active server - - -

standby server
Bidirectional
hacl-test 5305/UDP Active server - - -

standby server
Bidirectional

System
Administrator Guide - Solaris C IP Address Migration
C IP Address Migration
This describes how to perform IP address migration.
C.1 IP Address Migration Scenarios

This describes IP address migration scenarios.
C.2 Migrating the IP Address of the Server
This describes how to migrate the IP address of the server.
C.3 Migrating the IP Address of the NMS
This describes how to use the tool to migrate the IP address of the NMS.
C.4 Migrating the IP Address Related to NE Software Management
This describes how to migrate the IP address related to NE software management.
C.5 Migrating the IP Addresses Related to the Report Server
This describes how to migrate the IP addresses related to the report server.
C.6 Migrating the IP Address of a Managed Device
This describes how to migrate the IP address of a managed device.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential C-1

System
C IP Address Migration Administrator Guide - Solaris
C.1 IP Address Migration Scenarios

This describes IP address migration scenarios.
The following describes two scenarios for IP address migration.
l The NMS is installed, but devices are not added. In this scenario, do as follows to perform
IP address migration.
1. C.2 Migrating the IP Address of the Server
2. C.3 Migrating the IP Address of the NMS
3. C.4 Migrating the IP Address Related to NE Software Management
4. C.5 Migrating the IP Addresses Related to the Report Server
l The NMS is installed and devices are added. In this scenario, do as follows to perform IP
address migration.
1. C.2 Migrating the IP Address of the Server
2. C.3 Migrating the IP Address of the NMS
3. C.4 Migrating the IP Address Related to NE Software Management
4. C.5 Migrating the IP Addresses Related to the Report Server
5. C.6 Migrating the IP Address of a Managed Device
C.2 Migrating the IP Address of the Server

This describes how to migrate the IP address of the server.
Prerequisite
The operation personnel can log in to the server as the root user.
Context
Aftr the IP address is changed, you need to restart the system to make the new IP address take
effect.
Procedure
Step 2 Start the system configuration tool.
# cd /export/home/clonetools/SYSCfg
# sh configtool.sh
Information similar to the following is displayed:

Select the single-server or two-server vcs [s,v]:>_
Step 3
C-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
Information similar to the following is displayed:

****************************************************************
1 : Change the IP address
2 : Change the host name
3 : Configure the time zone
4 : Change the date
5 : Update the n2000 license
6 : Change the password of the root user
q : Quit
****************************************************************
Please enter [ 1 2 3 4 5 6 q ]:
Step 4 Modify the first item according to the prompt.

Step 5 After the modification, select q to exit and choose to restart the OS.
----End
C.3 Migrating the IP Address of the NMS

This describes how to use the tool to migrate the IP address of the NMS.
Procedure
Step 2 Run the following commands to start the IP Tool:
# cd /opt/dmstools/IpTool
# sh run_IpTool_sol.sh
Step 3 In the dialog box that is displayed, enter New IP Address, N2000 Installation Path, Database
Server IP Address, Database Port, Database User Name, and Database Password.

System
Step 4 Click Start Execute.

The dialog box indicating successful operation is displayed.
----End
C.4 Migrating the IP Address Related to NE Software

Management
This describes how to migrate the IP address related to NE software management.
Procedure
Step 1 Log in to the NMS as the admin user.
Step 2 Select NE Software Management > Options > FTP Settings from the main menu to open the
FTP Settings dialog.
Step 3 On the System Information tab, set the parameters according to the actual conditions.
l If Single NIC Configuration is selected, set the NMS server IP address.
l If the Multiple NIC Configuration is selected, configure the NMS server IP address for
multiple network interface cards.
1. Enter the NMS server IP address in the Server IP Address field.

System
2. Set the device IP address and the network segment in the NE Network IP/
Segment field to connect the devices in different network.
3. Click Add to add the server IP address to the new network segment.
4. Click Modify to modify the NMS server IP address.
5. Click Delete to delete the existing NMS server IP address.
Step 4 Click OK to configure the system information settings successfully.
----End
C.5 Migrating the IP Addresses Related to the Report Server

This describes how to migrate the IP addresses related to the report server.
Procedure
Step 2 Run the following commands in the report installation directory.
# cd iWebReportServer/bin
# ./ServiceManager.sh
Step 3 In the iWeb Report Server Manager dialog box, click Security.
Step 4 In the Configure Security Settings dialog box that is displayed, select the iMAP(FN) check
box.
Step 5 Set Security Server IP and Security DB IP to the new IP addresses.
Step 6 Click Test. The Test Results dialog box is displayed.
If the system prompts Destination Reachable, click OK.
Step 7 Log in to the report system as the admin user.
Step 8 Select the Project tab.
Step 9 Select one project file. Select the Data Source tab on the right of the project file.
NOTE
The SystemReports project is the built-in project of the report system. You do not need to set the data
source for it.

System
Step 10 Set Database IP to the new IP address.
Step 11 Click Test.

l If the test is successful, the system prompts Test Successful.
l If the test fails, check whether the server is started and the parameters of the data source are
correctly set.
Step 12 After the test is successful, click Apply to complete setting of the project file.
----End
C.6 Migrating the IP Address of a Managed Device

This describes how to migrate the IP address of a managed device.
Context
l When the alarm and log functions of the NMS are required, you need to migrate the IP
addresses related to managed devices.
l The following takes the change of the original IP address 10.10.10.10 to the new IP address
10.20.20.20 as an example.
Procedure
Step 1 In the topology navigation tree or the topology view, select the NE to be operated and right-click
it. Then select NE Management on the shortcut menu.
Step 2 In the service tree, expand NE Channel Management, and then click Syslog Service.

System
Step 3 On the Syslog Service tab page, select the entry of whom Log Host IP Address is
10.10.10.10 and right-click it. Then, select Delete on the shortcut menu.
Step 4 Right-click on the Syslog Service tab and select Add on the shortcut menu.
Step 5 In the dialog box that is displayed, set Log Host IP Address to 10.20.20.20, Channel
Number to 0, Log Facility to local0, and Log Language to English.
NOTE
In the actual operation, set Channel Number, Log Facility, and Log Language as required.
Step 6 Click OK.

Step 7 In the service tree, expand NE Channel Management, and then click Trap Service.
Step 8 On the Trap Service tab page, select the entry of whom Receive Host IP Address is
10.10.10.10 and right-click it. Then, select Delete on the shortcut menu.
Step 9 Right-click on the Trap Service tab and select Add on the shortcut menu.
Step 10 In the dialog box that is displayed, set Receive Host IP Address to 10.20.20.20, Alarm UDP
Port No. to 162, Security String to public, SNMP Version to V2C, and Alarm Mode to
Trap.
NOTE
l In the actual operation, you can set Security String as required.

l Select the actual version for SNMP Version.

System
Step 11 Click OK.
----End

System
Administrator Guide - Solaris D Changing a Password by Using the IP Tool
D Changing a Password by Using the IP Tool
This describes how to change a password by using the IP Tool. For example, after the NMS is
uninstalled due to a certain reason, the same NMS is installed but a different N2000user
password is set. After restoring the NMS database data that is backed up, the N2000user
password is still the original password, rather than the password that is set during re-installation.
Then, you can use the IP Tool to change the N2000user password to the password that is set
during re-installation.
Procedure
Step 1 Run the following commands to start the IP Tool:
# cd /opt/dmstools/IpTool
# sh run_IpTool_sol.sh
Step 2 Click the PWDSync tab and enter the new password of the N2000user user.
Step 3 Click Start Execute.
The dialog box indicating successful operation is displayed.
----End
Issue 06 (2010-06-21) Huawei Proprietary and Confidential D-1

System
Administrator Guide - Solaris E Glossary
E Glossary
A
Alarm Level Alarm level is to identify the severity of an alarm or event. It is divided
up into four levels: critical, major, minor, and warning alarm.
Alarm The correlation analysis is a kind of rule-based complete and effective
Correlation analysis about the alarm reported by the device, which helps reduce the
Analysis network storm and helps the maintenance personnel quickly locate the
problems.
C
Collector An important component of the N2000 DMS that is used to collect
device data. It collects device data through continuous polling and stores
the collected data in the database for collectors. The NMS server reads
required data from the collector database. Different devices are
collected by different collectors.
Current Alarm An alarm that is uncleared and unacknowledged, uncleared but
acknowledged, or cleared but unacknowledged
F
Fault A circumstance in which the system cannot function normally due to
some physical or logical factors.
Flash Alarm The same alarm was sent several times within a short period of time and
is promptly recovered.
H
History Alarm An alarm that is cleared and acknowledged.
I
Intermittent When the interval between the reported clearance time of two alarms is
Alarm shorter than the reporting period, the later alarm is called an intermittent
alarm.
Issue 06 (2010-06-21) Huawei Proprietary and Confidential E-1

System
E Glossary Administrator Guide - Solaris
L
Link Link is one of the topology objects. It displays the relationship between
the node and the submap. It is displayed as one straight line between the
node and the submap on the topological view.
Locked Status A status in which the instanced cannot be operated.
O
Operation Set A collection of operations. Classifying operations into operation sets
helps to manage user operation rights. Operations performed by
different users have different impacts on system security. Operations
with similar impacts are classified into an operation set. Users or user
groups entitled to an operation set can perform all the operations in the
operation set. The NMS provides some default operation sets. If the
default operation sets cannot meet the requirements for right allocation,
users can create operation sets as required.
S
Submap Submap is one of the topology objects, which contains the submap,
nodes and the connection. It is displayed in the topological view with
the submap icon. Submap contains several types, such as the common
submap and the IP submap.
T
Topology Object The basic element of the topology includes the submap, the device and
the connection.
U
User A client user of the NMS. The user name and password uniquely
identifies the operation rights of a user in the NMS.
User Group The user group is group in the device and used to control the access of
the user to the network.
V
View Edits and displays the rule of the topology data or the filter conditions.
It can be tailored according to the requirements.
E-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

System
Administrator Guide - Solaris F Acronyms and Abbreviations
F Acronyms and Abbreviations
A
ACL Access Control List
C
CORBA Common Object Request Broker Architecture
CPU Central Processing Unit
D
DMS Datacom Integrated Network Management System
F
FTP File Transfer Protocol
G
GUI Graphic User Interface
GMT Greenwich Time
H
HTML Hyper Text Markup Language
I
iMAP Integrated Management Applicant Platform
ICMP Internet Control Message Protocol
ID Identity
IP Internet Protocol
Issue 06 (2010-06-21) Huawei Proprietary and Confidential F-1

System
F Acronyms and Abbreviations Administrator Guide - Solaris
L
LDAP Lightweight Directory Access Protocol
LSP Label Switch Path
M
MIB Management Information Base
MPLS MultiProtocol Label Switching
N
NMS Network Management System
NTP Network Time Protocol
P
PID Process Identification
PRC People's Republic of China
S
SNMP Simple Network Management Protocol
SQL Structured Query Language
SSL Security Socket Layer
T
TCP Transport Control Protocol
F-2 Huawei Proprietary and Confidential Issue 06 (2010-06-21)

N2000 System User Manual

Uploaded by

Copyright:

Available Formats

N2000 System User Manual

Uploaded by

Document Information

Original Title

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

N2000 System User Manual

Uploaded by

Copyright:

Available Formats

iManager N2000 DMS Datacomm Network Management

Administrator Guide - Solaris

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2010-06-21) Huawei Proprietary and Confidential i

About This Document

Product Name Version

iManager N2000 DMS V500R003C01

This document is intended for:

l Installation and commissioning engineer

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Issue 06 (2010-06-21) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

iv Huawei Proprietary and Confidential Issue 06 (2010-06-21)

Updates in Issue 06 (2010-06-21)

Updates in Issue 05 (2009-08-31)

Updates in Issue 04 (2009-06-30)

Updates in Issue 03 (2009-03-25)

Updates in Issue 02 (2009-01-20)

Updates in Issue 01 (2008-12-10)

Issue 06 (2010-06-21) Huawei Proprietary and Confidential v

About This Document...................................................................................................................iii

2 Setting the N2000 DMS Time..................................................................................................2-1

3 Setting N2000 DMS Server Parameters..................................................................................3-1

Issue 06 (2010-06-21) Huawei Proprietary and Confidential vii

3.2 Changing the Host Name of the N2000 DMS Server.....................................................................................3-2

4 Managing the N2000 DMS Client...........................................................................................4-1

5 N2000 DMS Security Management.........................................................................................5-1

6 Managing the N2000 DMS Users............................................................................................6-1

viii Huawei Proprietary and Confidential Issue 06 (2010-06-21)

6.5 Creating N2000 DMS Users.........................................................................................................................6-17

7 Managing N2000 DMS Logs....................................................................................................7-1

Issue 06 (2010-06-21) Huawei Proprietary and Confidential ix

7.3.1 Browsing Operation Logs......................................................................................................................7-8

8 Managing N2000 DMS Processes and Services....................................................................8-1

9 Managing N2000 DMS Databases..........................................................................................9-1

x Huawei Proprietary and Confidential Issue 06 (2010-06-21)

9.12 Clearing an N2000 DMS Database.............................................................................................................9-19

10 Managing N2000 DMS Files and Disks.............................................................................10-1

11 N2000 DMS Routine Maintenance.....................................................................................11-1

Issue 06 (2010-06-21) Huawei Proprietary and Confidential xi

11.5.6 Checking System Logs.....................................................................................................................11-17

12 N2000 DMS Emergency Maintenance................................................................................12-1

13 N2000 DMS Fault Handling.................................................................................................13-1

xii Huawei Proprietary and Confidential Issue 06 (2010-06-21)

13.4.14 Switch to the Slave Syslog Server..................................................................................................13-15

14 N2000 DMS FAQs..................................................................................................................14-1