N2000 Troubleshooting Manual

Chapter 1 Routine Maintenance .....................................................................
1-1
1.1 Maintenance Categories ........................................................................

1.2 Maintenance Suggestions ......................................................................
1.3 Routine Maintenance Items ....................................................................
1.3.1 Viewing Server Performance .........................................................
1.3.2 Checking Connectivity of NMS Server, NMS Client, and
Managed Devices ...................................................................................
1.3.3 Viewing Topology and Alarm Information ......................................
1.3.4 Backing Up NMS Database ...........................................................
1.3.5 Backing Up Device Configuration ..................................................
1.3.6 Viewing Operation Log ...................................................................
1.3.7 Managing User Authority ...............................................................
1.3.8 Viewing Used NMS Database Space ............................................
1.3.9 Viewing Used Hard Disk Space of NMS Server ............................
1.3.10 Checking Hardware, Power Supply, and Equipment Room
Environment of NMS Workstation ...........................................................
1.3.11 Installing Windows Patches and Killing Viruses in Time ..............
1.4 Maintenance Reports .............................................................................
1.4.1 Duty Report ....................................................................................
1.4.2 Weekly Maintenance Report ..........................................................
1.5 Starting and Shutting Down an NMS Workstation ..................................
1-1
1-1
1-2
1-3
1-10
1-12
1-13
1-14
1-15
1-16
1-17
1-22
1-23
1-24
1-25
1-25
1-26
1-27
Chapter 2 Troubleshooting .............................................................................
2-1
2.1 Basic Concepts ......................................................................................

2.1.1 Alarm Definition and Category .......................................................
2.1.2 Terms .............................................................................................
2.2 General Troubleshooting Procedure ......................................................
2.2.1 Collecting Information ....................................................................
2.2.2 Judging the Fault ...........................................................................
2.2.3 Locating the Fault ..........................................................................
2.2.4 Eliminating the Fault ......................................................................
2.3 General Fault Locating Methods ............................................................
2.3.1 Analyzing Raw Information ............................................................
2.3.2 Analyzing Alarm Information ..........................................................
2.3.3 Analyzing Indicator Status .............................................................
2.3.4 Tracing Connection and Signaling .................................................
2.3.5 Test and Loopback ........................................................................
2.3.6 Comparison and Replacement ......................................................
2.3.7 Switchover and Reset ....................................................................
2.3.8 Using Instruments and Meters .......................................................
2.3.9 Performance Measurement ...........................................................
2-1
2-1
2-2
2-3
2-4
2-4
2-4
2-4
2-5
2-5
2-5
2-5
2-6
2-6
2-6
2-6
2-7
2-7
2.4 Troubleshooting Cases ..........................................................................

2.4.1 The SQL Server Fails to Start After the Password of
"administrator" Is Changed. ....................................................................
2.4.2 The Adaptive Server Cannot be Created During Installation of
Sybase. ...................................................................................................
2.4.3 The NMS Cannot Be Installed After the SQL Server Is
Reinstalled. .............................................................................................
2.4.4 The NMS Client and SysMonitor Cannot Be Used Due to
Unsuccessful Start of the NMS Daemon. ...............................................
2.4.5 The Security Daemon Fails to Start After the License Is
Updated. .................................................................................................
2.4.6 The Fault Daemon Fails to Start. ...................................................
2.4.7 The iManager N2000 UMS Fails to Add an AMG Due to
Incorrect "snmp port" ..............................................................................
2.4.8 The iManager N2000 UMS Cannot Receive Alarms from a
TMG Due to an Incorrect Alarm Language. ............................................
2.4.9 The iManager N2000 UMS Fails in Circuit Test and Loop Line
Test Because No Test Group Is Created on the AMG............................
2.4.10 The Line Test Fails Because an Incorrect NMS IP Address Is
Set on the MD5500. ................................................................................
2-7
2-7
2-8
2-8
2-9
2-10
2-11
2-11
2-12
2-12
2-13
Chapter 3 Maintenance Tools .........................................................................
3-1
3.1 Database Password Tool .......................................................................

3.1.1 Changing Password of "N2000user" in Windows ..........................
3.1.2 Changing Password of "N2000user" in Solaris ..............................
3.2 Database Backup Tool ...........................................................................
3.2.1 Preparations ...................................................................................
3.2.2 Backing Up a Database .................................................................
3.2.3 Recovering a Database .................................................................
3-1
3-1
3-1
3-2
3-3
3-10
3-11
Chapter 4 Remote Maintenance .....................................................................
4-1
4.1 Remote Maintenance Channel ...............................................................

4.2 Hardware Requirement and Connection ................................................
4.3 Software Configuration ...........................................................................
4.3.1 PC/Windows 2000 Serving as a Dial-up Server ............................
4.3.2 PC/Windows 2000 Serving as a PSTN Client ................................
4.3.3 SUN Workstation Serving as a PSTN Dial-up Server ....................
4.4 Remote Maintenance Solutions .............................................................
4.5 Troubleshooting ......................................................................................
4-1
4-1
4-2
4-2
4-6
4-9
4-15
4-16
Chapter 5 FAQ ..................................................................................................
5-1
5.1 Operating System ...................................................................................

5.1.1 How to Start Sun Workstation from CD-ROM (Sun/Solaris)? ........
5.1.2 How to Set IP Address of Sun Workstation (Sun/Solaris)?............
5-1
5-1
5-1
5.1.3 How to Change Host Name of Sun Workstation (Sun/Solaris)? ....

5.1.4 How to Configure Maximum Terminals for Sun Workstation
(Sun/Solaris)? .........................................................................................
5.1.5 How to Extract a File with a ".tar.gz" Extension? ...........................
5.1.6 How to View the Version and Release Date of Solaris? ................
5.1.7 How to Switch from a Common User to a Superuser? ..................
5.1.8 How to Add or Delete a Static Route? ...........................................
5.1.9 How to Add or Delete a Default Route? .........................................
5.1.10 Sun Workstation Aborts (Sun/Solaris) .........................................
5.1.11 File Size Changed When FTP Is Used to Send Files ..................
5.1.12 Execution Authority of Files Is Lost When FTP Is Used to
Send Files ...............................................................................................
5.2 Database ................................................................................................
5.2.1 How to Change the Password of "sa" (Sun/Solaris/Sybase)? .......
5.2.2 How to Set a Password for "sa" Windows/SQL Server 2000)? .....
5.2.3 How to Quit Sybase 12.0 and Log in as "root"?? ..........................
5.2.4 How to Check the NMS Database in Case of Power Failure? .......
5.2.5 Unable to Start Sybase (Sun/Solaris/Sybase) ...............................
5.2.6 How to View Sybase Information? .................................................
5.2.7 How to View the Data Table? ........................................................
5.2.8 How to Check Database Error Using the DBCC Tool? ..................
5.3 NMS .......................................................................................................
5.3.1 A Device Can Be Pinged but the NMS Prompts That the
Communication of the Device Is Interrupted. ..........................................
5.3.2 No Traffic Measurement Data Is Received After the Task
Created on the BAM Is Synchronized to the NMS. .................................
5.3.3 No Data Is Measured During Measurement of Global Traffic. .......
5.3.4 Unable to Reinstall the NMS ..........................................................
5.3.5 How to Prohibit the iManager N2000 from Running When Your
Computer Starts? ....................................................................................
5.3.6 How to Set CPU and Memory Alarm Thresholds for the
iManager N2000 Workstation? ...............................................................
5.3.7 IP Address of the NMS Server Is Changed. ..................................
5.3.8 Basic Algorithms for Traffic Measurement .....................................
5-1
5-9
5-9
5-10
Appendix A SNMP ...........................................................................................
A-1
A.1 Introduction ............................................................................................

A.2 Architecture ............................................................................................
A.3 Principles of SNMP ................................................................................
A.4 Security Systems ...................................................................................
A.4.1 Security System in SNMPV1 .........................................................
A.4.2 Comparison of Security Systems in SNMP V1, V2, and V3 ..........
A-1
A-1
A-2
A-3
A-3
A-4
5-1
5-2
5-2
5-2
5-2
5-3
5-3
5-3
5-3
5-4
5-4
5-4
5-4
5-5
5-6
5-7
5-7
5-7
5-8
5-8
5-8
5-8
5-8
5-9
Appendix B Solaris ..........................................................................................
B-1
B.1 Introduction ............................................................................................

B.1.1 Basic Concepts..............................................................................
B.1.2 Architecture ...................................................................................
B.1.3 User Authority ................................................................................
B.1.4 File System ....................................................................................
B.2 Login and Logout Commands ................................................................
B.3 User Management Commands ..............................................................
B.4 File Operation Commands .....................................................................
B.5 Process Control Commands ..................................................................
B.6 Network Communication Commands ....................................................
B.7 vi ............................................................................................................
B.7.1 Starting/Exiting vi ...........................................................................
B.7.2 vi Commands.................................................................................
B.7.3 vi Application Examples .................................................................
B.8 find .........................................................................................................
B.9 grep ........................................................................................................
B.10 cmp ......................................................................................................
B.11 UNIX Utilities ........................................................................................
B.11.1 tar ................................................................................................
B.11.2 compress and uncompress .........................................................
B.11.3 pkzip and pkunzip ........................................................................
B.11.4 gzip and zip and ..........................................................................
B-1
B-1
B-2
B-3
B-4
B-7
B-8
B-10
B-15
B-16
B-18
B-18
B-18
B-20
B-20
B-22
B-22
B-23
B-23
B-24
B-24
B-25
Appendix C Sybase .........................................................................................
C-1
C.1 Introduction ............................................................................................

C.1.1 System Databases ........................................................................
C.1.2 Sybase Objects .............................................................................
C.2 Sybase Operations ................................................................................
C.2.1 Starting Sybase .............................................................................
C.2.2 Shutting Down Sybase ..................................................................
C.2.3 Recovering a System Software Fault ............................................
C.2.4 Recovering a Medium Fault ..........................................................
C.2.5 Backing Up a Database and Transaction Logs .............................
C.2.6 Recovering a User Database ........................................................
C.3 Sybase Utilities ......................................................................................
C.3.1 isql .................................................................................................
C.3.2 showserver ....................................................................................
C.3.3 startserver .....................................................................................
C-1
C-1
C-2
C-3
C-3
C-4
C-4
C-5
C-5
C-6
C-7
C-7
C-9
C-9
Appendix D SQL Server ..................................................................................
D-1
D.1 Introduction ............................................................................................

D.2 Backing Up and Recovering a Database ...............................................
D.2.1 Creating a Backup Device .............................................................
D.2.2 Backing Up a Database .................................................................
D.2.3 Creating a Backup Wizard .............................................................
D.2.4 Recovering a Database .................................................................
D.2.5 Backing Up and Recovering a System Database .........................
D-1
D-2
D-3
D-3
D-4
D-5
D-6
Appendix E Terms and Acronyms .................................................................
E-1
E.1 Terms .....................................................................................................

E.2 Acronyms ...............................................................................................
E-1
E-2
HUAWEI
HUAWEI iManager N2000 Fixed Network Integrated
Management System
Troubleshooting Manual
V200
HUAWEI iManager N2000 Fixed Network Integrated Management

System
Manual Version
T2-100333-20040830-C-2.00
Product Version
V200
BOM
31033533
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2004 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual

Release Notes
This manual applies to iManager N2000 Fixed Network Integrated Management
System V200 (hereinafter referred to as iManager N2000).
Related Manuals
The related manuals are listed in the following table.
Manual
Content
HUAWEI iManager N2000 Fixed

Network Integrated Management
System Installation Manual
It introduces the installation procedures of the iManager

N2000, including operating system, database, NMS
software and client.

System User Manual
It introduces the basic operations of iManager N2000,

including system description, topology management, fault
management, performance management, security
management, database backup, and system monitor. It also
introduces the security strategy, daily maintenance and
remote maintenance of the iManager N2000.

System Troubleshooting Manual
It offers suggestions on the routine maintenance of the

iManager N2000. It also introduces the troubleshooting and
remote maintenance of the iManager N2000. It also
introduces how to use the maintenance tools and presents
answers to the FAQ about the maintenance of the iManager
N2000. Besides, it briefs SNMP, Solaris, Sybase, and SQL
Server.
Organization
This manual offers suggestions on the routine maintenance of the iManager N2000. It
also introduces the troubleshooting and remote maintenance of the iManager N2000.
Besides, it explains how to use the maintenance tools.
There are six chapters in this manual.
Chapter 1 Routine Maintenance focuses on the routine maintenance items of the
iManager N2000. It also provides detailed operation guidance and troubleshooting
suggestions.
Chapter 2 Troubleshooting introduces alarm definition and categories. It presents

general procedure and methods for troubleshooting. It also provides some typical
troubleshooting cases for reference.
Chapter 3 Maintenance Tools introduces how to use the database password tool and
the database backup tool.
Chapter 4 Remote Maintenance introduces the remote maintenance means and
methods of the iManager N2000.
Chapter 5 FAQ presents answers to the frequently asked questions about the
maintenance of the iManager N2000.
Chapter 6 Appendix NMS Basics briefs SNMP, Solaris, Sybase, and SQL Server.
Intended Audience
The manual is intended for the following readers:
z
Network design & management personnel
Network maintenance personnel
Engineer for the iManager N2000 NMS
Conventions
This manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface
Headings are in Boldface.
Courier New
Terminal Display is in Courier New.
II. Command conventions

Convention
Description
Boldface
The keywords of a command line are in Boldface.
italic
Command arguments are in italic.
[]
Items (keywords or arguments) in square brackets [ ] are optional.
Convention
Description
{ x | y | ... }
Alternative items are grouped in braces and separated by vertical bars.

One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets and separated

by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by vertical bars. A

minimum of one or a maximum of all can be selected.
[ x | y | ... ] *
Optional alternative items are grouped in square brackets and separated

by vertical bars. Many or none can be selected.
III. GUI conventions

Convention
Description
<>
Button names are inside angle brackets. For example, click the <OK>
button.
[]
Window names, menu items, data table and field names are inside square
brackets. For example, pop up the [New User] window.
Multi-level menus are separated by forward slashes. For example,

[File/Create/Folder].
IV. Keyboard operation

Format
Description
<Key>
Press the key with the key name inside angle brackets. For example,
<Enter>, <Tab>, <Backspace>, or <A>.
<Key1+Key2>
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
keys should be pressed concurrently.
<Key1, Key2>
Press the keys in turn. For example, <Alt, A> means the two keys should
be pressed in turn.
V. Mouse operation
Action
Description
Click
Press the left button or right button quickly (left button by default).
Double Click
Press the left button twice continuously and quickly.
Drag
Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.
HUAWEI iManager N2000 Fixed Network Integrated Management System
Table of Contents
Table of Contents
Chapter 1 Routine Maintenance................................................................................................... 1-1
1.1 Maintenance Categories.................................................................................................... 1-1
1.2 Maintenance Suggestions ................................................................................................. 1-1
1.3 Routine Maintenance Items ............................................................................................... 1-2
1.3.1 Viewing Server Performance .................................................................................. 1-3
1.3.2 Checking Connectivity of NMS Server, NMS Client, and Managed Devices ....... 1-10
1.3.3 Viewing Topology and Alarm Information ............................................................. 1-12
1.3.4 Backing Up NMS Database .................................................................................. 1-13
1.3.5 Backing Up Device Configuration ......................................................................... 1-14
1.3.6 Viewing Operation Log.......................................................................................... 1-15
1.3.7 Managing User Authority....................................................................................... 1-16
1.3.8 Viewing Used NMS Database Space ................................................................... 1-17
1.3.9 Viewing Used Hard Disk Space of NMS Server ................................................... 1-22
1.3.10 Checking Hardware, Power Supply, and Equipment Room Environment of NMS
Workstation .................................................................................................................... 1-23
1.3.11 Installing Windows Patches and Killing Viruses in Time..................................... 1-24
1.4 Maintenance Reports....................................................................................................... 1-25
1.4.1 Duty Report ........................................................................................................... 1-25
1.4.2 Weekly Maintenance Report ................................................................................. 1-26
1.5 Starting and Shutting Down an NMS Workstation........................................................... 1-27
Chapter 2 Troubleshooting .......................................................................................................... 2-1
2.1 Basic Concepts .................................................................................................................. 2-1
2.1.1 Alarm Definition and Category ................................................................................ 2-1
2.1.2 Terms ...................................................................................................................... 2-2
2.2 General Troubleshooting Procedure.................................................................................. 2-3
2.2.1 Collecting Information ............................................................................................. 2-4
2.2.2 Judging the Fault..................................................................................................... 2-4
2.2.3 Locating the Fault.................................................................................................... 2-4
2.2.4 Eliminating the Fault................................................................................................ 2-4
2.3 General Fault Locating Methods........................................................................................ 2-5
2.3.1 Analyzing Raw Information ..................................................................................... 2-5
2.3.2 Analyzing Alarm Information ................................................................................... 2-5
2.3.3 Analyzing Indicator Status....................................................................................... 2-5
2.3.4 Tracing Connection and Signaling .......................................................................... 2-6
2.3.5 Test and Loopback.................................................................................................. 2-6
2.3.6 Comparison and Replacement................................................................................ 2-6
2.3.7 Switchover and Reset ............................................................................................. 2-6
Table of Contents
2.3.8 Using Instruments and Meters ................................................................................ 2-7

2.3.9 Performance Measurement..................................................................................... 2-7
2.4 Troubleshooting Cases...................................................................................................... 2-7
2.4.1 The SQL Server Fails to Start After the Password of administrator Is Changed. 2-7
2.4.2 The Adaptive Server Cannot be Created During Installation of Sybase................. 2-8
2.4.3 The NMS Cannot Be Installed After the SQL Server Is Reinstalled. ...................... 2-8
2.4.4 The NMS Client and SysMonitor Cannot Be Used Due to Unsuccessful Start of the
NMS Daemon................................................................................................................... 2-9
2.4.5 The Security Daemon Fails to Start After the License Is Updated. ...................... 2-10
2.4.6 The Fault Daemon Fails to Start. .......................................................................... 2-11
2.4.7 The iManager N2000 UMS Fails to Add an AMG Due to Incorrect snmp port... 2-11
2.4.8 The iManager N2000 UMS Cannot Receive Alarms from a TMG Due to an Incorrect
Alarm Language. ............................................................................................................ 2-12
2.4.9 The iManager N2000 UMS Fails in Circuit Test and Loop Line Test Because No Test
Group Is Created on the AMG. ...................................................................................... 2-12
2.4.10 The Line Test Fails Because an Incorrect NMS IP Address Is Set on the MD5500.2-13
Chapter 3 Maintenance Tools ...................................................................................................... 3-1
3.1 Database Password Tool................................................................................................... 3-1
3.1.1 Changing Password of N2000user in Windows ................................................... 3-1
3.1.2 Changing Password of N2000user in Solaris ....................................................... 3-1
3.2 Database Backup Tool ...................................................................................................... 3-2
3.2.1 Preparations ............................................................................................................ 3-3
3.2.2 Backing Up a Database ........................................................................................ 3-10
3.2.3 Recovering a Database......................................................................................... 3-11
Chapter 4 Remote Maintenance................................................................................................... 4-1
4.1 Remote Maintenance Channel .......................................................................................... 4-1
4.2 Hardware Requirement and Connection ........................................................................... 4-1
4.3 Software Configuration ...................................................................................................... 4-2
4.3.1 PC/Windows 2000 Serving as a Dial-up Server ..................................................... 4-2
4.3.2 PC/Windows 2000 Serving as a PSTN Client......................................................... 4-6
4.3.3 SUN Workstation Serving as a PSTN Dial-up Server............................................. 4-9
4.4 Remote Maintenance Solutions....................................................................................... 4-15
4.5 Troubleshooting ............................................................................................................... 4-16
Chapter 5 FAQ ............................................................................................................................... 5-1
5.1 Operating System .............................................................................................................. 5-1
5.1.1 How to Start Sun Workstation from CD-ROM (Sun/Solaris)?................................. 5-1
5.1.2 How to Set IP Address of Sun Workstation (Sun/Solaris)? .................................... 5-1
5.1.3 How to Change Host Name of Sun Workstation (Sun/Solaris)?............................. 5-1
5.1.4 How to Configure Maximum Terminals for Sun Workstation (Sun/Solaris)? .......... 5-1
5.1.5 How to Extract a File with a .tar.gz Extension? .................................................... 5-2
5.1.6 How to View the Version and Release Date of Solaris?......................................... 5-2
ii
Table of Contents
5.1.7 How to Switch from a Common User to a Superuser? ........................................... 5-2

5.1.8 How to Add or Delete a Static Route? .................................................................... 5-2
5.1.9 How to Add or Delete a Default Route?.................................................................. 5-3
5.1.10 Sun Workstation Aborts (Sun/Solaris) .................................................................. 5-3
5.1.11 File Size Changed When FTP Is Used to Send Files ........................................... 5-3
5.1.12 Execution Authority of Files Is Lost When FTP Is Used to Send Files ................. 5-3
5.2 Database............................................................................................................................ 5-4
5.2.1 How to Change the Password of "sa" (Sun/Solaris/Sybase)? ................................ 5-4
5.2.2 How to Set a Password for sa(Windows/SQL Server 2000)? .............................. 5-4
5.2.3 How to Quit Sybase 12.0 and Log in as root? ...................................................... 5-4
5.2.4 How to Check the NMS Database in Case of Power Failure?................................ 5-5
5.2.5 Unable to Start Sybase (Sun/Solaris/Sybase) ........................................................ 5-6
5.2.6 How to View Sybase Information? .......................................................................... 5-7
5.2.7 How to View the Data Table?.................................................................................. 5-7
5.2.8 How to Check Database Error Using the DBCC Tool?........................................... 5-7
5.3 NMS ................................................................................................................................... 5-8
5.3.1 A Device Can Be Pinged but the NMS Prompts That the Communication of the
Device Is Interrupted. ....................................................................................................... 5-8
5.3.2 No Traffic Measurement Data Is Received After the Task Created on the BAM Is
Synchronized to the NMS. ............................................................................................... 5-8
5.3.3 No Data Is Measured During Measurement of Global Traffic................................. 5-8
5.3.4 Unable to Reinstall the NMS ................................................................................... 5-8
5.3.5 How to Prohibit the iManager N2000 from Running When Your Computer Starts?5-9
5.3.6 How to Set CPU and Memory Alarm Thresholds for the iManager N2000 Workstation?
.......................................................................................................................................... 5-9
5.3.7 IP Address of the NMS Server Is Changed. ........................................................... 5-9
5.3.8 Basic Algorithms for Traffic Measurement ............................................................ 5-10
Appendix A SNMP .........................................................................................................................A-1
A.1 Introduction........................................................................................................................A-1
A.2 Architecture .......................................................................................................................A-1
A.3 Principles of SNMP ...........................................................................................................A-2
A.4 Security Systems...............................................................................................................A-3
A.4.1 Security System in SNMPV1 ..................................................................................A-3
A.4.2 Comparison of Security Systems in SNMP V1, V2, and V3...................................A-4
Appendix B Solaris........................................................................................................................B-1
B.1 Introduction........................................................................................................................B-1
B.1.1 Basic Concepts .......................................................................................................B-1
B.1.2 Architecture.............................................................................................................B-2
B.1.3 User Authority .........................................................................................................B-3
B.1.4 File System .............................................................................................................B-4
B.2 Login and Logout Commands ...........................................................................................B-7
B.3 User Management Commands .........................................................................................B-8
iii
Table of Contents
B.4 File Operation Commands ..............................................................................................B-10

B.5 Process Control Commands ...........................................................................................B-15
B.6 Network Communication Commands..............................................................................B-16
B.7 vi ......................................................................................................................................B-18
B.7.1 Starting/Exiting vi ..................................................................................................B-18
B.7.2 vi Commands ........................................................................................................B-18
B.7.3 vi Application Examples........................................................................................B-20
B.8 find...................................................................................................................................B-20
B.9 grep .................................................................................................................................B-22
B.10 cmp................................................................................................................................B-22
B.11 UNIX Utilities .................................................................................................................B-23
B.11.1 tar........................................................................................................................B-23
B.11.2 compress and uncompress.................................................................................B-24
B.11.3 pkzip and pkunzip ...............................................................................................B-24
B.11.4 gzip and zip and..................................................................................................B-25
Appendix C Sybase .......................................................................................................................C-1
C.1 Introduction........................................................................................................................C-1
C.1.1 System Databases .................................................................................................C-1
C.1.2 Sybase Objects.......................................................................................................C-2
C.2 Sybase Operations............................................................................................................C-3
C.2.1 Starting Sybase ......................................................................................................C-3
C.2.2 Shutting Down Sybase ...........................................................................................C-4
C.2.3 Recovering a System Software Fault .....................................................................C-4
C.2.4 Recovering a Medium Fault....................................................................................C-5
C.2.5 Backing Up a Database and Transaction Logs ......................................................C-5
C.2.6 Recovering a User Database .................................................................................C-6
C.3 Sybase Utilities..................................................................................................................C-7
C.3.1 isql ..........................................................................................................................C-7
C.3.2 showserver .............................................................................................................C-9
C.3.3 startserver...............................................................................................................C-9
Appendix D SQL Server ................................................................................................................D-1
D.1 Introduction........................................................................................................................D-1
D.2 Backing Up and Recovering a Database ..........................................................................D-2
D.2.1 Creating a Backup Device ......................................................................................D-3
D.2.2 Backing Up a Database..........................................................................................D-3
D.2.3 Creating a Backup Wizard......................................................................................D-4
D.2.4 Recovering a Database ..........................................................................................D-5
D.2.5 Backing Up and Recovering a System Database ..................................................D-6
Appendix E Terms and Acronyms...............................................................................................E-1
E.1 Terms ................................................................................................................................E-1
E.2 Acronyms...........................................................................................................................E-2
iv
Chapter 1 Routine Maintenance

This chapter focuses on the routine maintenance items of the iManager N2000 Fixed
Network Integrated Management System (the iManager N2000 for short). It also
provides detailed operation guidance and troubleshooting suggestions.
1.1 Maintenance Categories

Based on the maintenance purpose, device maintenance falls in routine maintenance
and troubleshooting.
I. Routine maintenance
Routine maintenance means that preventive maintenance operations are regularly
performed on normal devices to detect and eliminate their defaults or hidden troubles. It
aims to ensure the long-term secure, stable, and reliable running of the devices.
Based on the maintenance period, routine maintenance falls in daily maintenance and
regular maintenance.
z
Daily maintenance
Daily maintenance means that maintenance operations are performed every day, such
as viewing alarm information and viewing server performance.
Daily maintenance aims to detect device alarms or faults and take proper measures to
reduce the fault rate of the devices. With daily maintenance, you can keep track of the
running status and trend of the devices or network to enhance your efficiency in
handling emergencies.
z
Regular maintenance
Regular maintenance means that maintenance operations are performed periodically,

such as backing up NMS database and managing user authority.
With regular maintenance, you can detect device faults such as malfunction and
degraded performance so as to take proper measures in time.
II. Troubleshooting
Troubleshooting means that remedial maintenance operations are performed on a
faulty system or devices. It aims to locate and eliminate faults quickly.
1.2 Maintenance Suggestions

To ensure normal and reliable running of the iManager N2000, you need to pay
attention to the following suggestions and requirements.
1-1
A UPS needs to be configured for the NMS workstation to prevent hardware
damage, system corruption, and data loss due to power failure.

A label saying "Do not power off the NMS workstation! Follow this way to shut
down ..." needs to be pasted on the NMS workstation and the power connector.
If you do not have a UPS for the NMS workstation, after being notified that the
power supply will be cut, you must shut down the NMS and NMS workstation
correctly before the power cut.
Always follow these steps to shut down the NMS workstation: shut down
NMS->shut down NMS database->run init5 (for Solaris). Never shut down the
NMS workstation by running halt (for Solaris) or switching off the power supply;
otherwise the system may be corrupted.
After the NMS starts, three application systems usually need to be started:
SysMonitor, NMS client, and real-time alarm browser to monitor the system status.
z
The equipment room must be dust-proof and moisture-proof.
Do not play games on or install unnecessary software on the workstation.
Check the daily maintenance items every day, and take down the results. Paste
the telephone number and fax number of Huawei Customer Service Center in the
equipment room and be familiar with them.
Handle any fault immediately after it is detected. For the problems you cannot
solve, you may contact the Huawei Customer Service Center according to the
warranty of the equipment.
The passwords for logging into the NMS workstation must be provided in different
levels. Management-level passwords shall only be issued to authorized persons.
1.3 Routine Maintenance Items
Caution:
To ensure normal and stable running of the iManager N2000, we recommend that you perform routine
maintenance in strict accordance with Table 11.
Table 11 Routine maintenance items and period for the iManager N2000
No.
Maintenance item
Period
Viewing server performance
Daily
Checking connectivity of NMS server, NMS client, and devices
Daily
Viewing topology/alarm information
Daily
Backing up NMS database
Weekly
1-2
No.
Maintenance item
Period
Backing up device configuration
Weekly
Viewing operation log
Weekly
Managing user authority
Monthly
Viewing used NMS database space
Monthly
Viewing used NMS server hard disk space
Monthly
10
Checing hardware, power supply, and equipment room environment

of NMS worksation
Monthly
11
Immediately Installing Windows patches and killing viruses
1.3.1 Viewing Server Performance

I. Purpose
To view the CPU occupancy and memory occupancy of the NMS server so as to keep
track of the current running status of the NMS server.
II. Reference
The CPU occupancy of the server must be lower than 80%.
III. Operation guidance

1)
Start the SysMonitor, and then click the System Resource tab, as shown in
Figure 1-1.
The resource information of the system is displayed, including server name, CPU
occupancy, physical memory, used memory, and available memory.
1-3
Figure 1-1 System resource information

2)
If the CPU occupancy is higher than 80%, take measures accordingly.
3)
At the SysMonitor, click the Process tab, as shown in Figure 1-2.
This tab displays the processes running in the NMS, their CPU occupancy, and their
memory occupancy.
Figure 1-2 Processes

4)
Stop the unnecessary NMS processes by referring to Table 12: Set the start
mode to manual start, and then stop the process.
5)
Reduce the operations performed on the NMS server.
1-4
Note:
To improve the performance of the NMS server, we recommend that you stop the unnecessary NMS
processes even when the NMS is normal.
6)
At the NMS client, select [System/Security Manager].
7)
In the security management window that appears, right click Users under
Security Object, and then select [Login User Information] to view information
about the login users.
8)
Observe the CPU occupancy and memory occupancy of the NMS server for a
while. If the CPU occupancy is higher than 80% for a long time, restart the NMS
server.
9)
Continue observing the CPU occupancy and memory occupancy of the NMS
server. If the CPU occupancy is still higher than 80% for a long time, contact
Huawei Customer Service Center.
Note:
If the NMS server does not meet the performance requirement after the network to be managed is
expanded, the configuration of the NMS server must be updated, or the NMS server must be replaced with
a new one; otherwise the stable running of the NMS will be affected.
Table 12 iManager N2000 processes

Process
Function
Description
iMAP
EmfTopoDm
Topology management. It manages the

topologies of network devices by space,
logic, or network.
It must be started.
EmfSecuDm
Security management. It manages users and

user authority.
It must be started.
EmfFaultDm
Fault management. It receives, queries, and

acknowledges the alarms from devices,
NMS, and NMS server, as well as analyzes
the correlation of the alarms.
It must be started.
EmfPerfDm
Real-time performance management. It

monitors the performance indices of the
narrowband devices in real time.
Optional. It can be stopped if

the real-time performance
management function is not
needed.
EmfResourceDm
Resource management. It manages

resources such as devices, frames, boards,
ports, and some services.
It must be started.
1-5
Process
Function
Description
Scheduled
Policy management. It manages the

automatic tasks and event-triggering tasks in
the system.

no
timed
task
or
event-triggering
task
is
registered.
ProjDocd
Engineering document management. It

obtains all information about the devices
managed by the NMS and generates
engineering documents. It also manages
common devices.

no engineering document
needs to be generated.
EmfExamDm
Test command management. It controls the

dynamic debugging level of the processes
through the emfexam interface and obtains
the running information of the processes.

no dynamic debugging is
needed.
EmfProxyServer
Device access agent. The proxy used for

accessing devices through TCP protocols
such as Telnet and FTP.
It must be started.
EmfGnlDevDm
It provides simple management functions for

the devices of unknown type.
It must be started.
SNMPAgent
Northbound interface (SNMP). It implements

the agent function of SNMP. It is the
interface provided by the lower NMS to the
upper NMS or transfers alarms to the third
partys NMS.

neither upper NMS is available
nor any alarm needs to be
transferred.
CORBAAgent
Northbound
interface
(COBRA).
It
implements the agent function of CORBA. It
provides an interface for other NMSs to get
topology information, alarm information, and
so on.

no other NMS needs to
interconnect with the system
through CORBA.
EmfDBBackup
Database backup management. It provides

simple backup of NMS database and
supports automatic and manual backup
modes.

no backup task needs to be
done
automatically
or
manually.
iManager N2000 UMS

Ums112TestDm
Subscriber line test process
It can be stopped if the

subscriber line test is not
needed.
UmsAmg5000Dm
AMG5000V1 management process
It can be stopped if no AMGV1

device needs to be managed.
UmsIadmsDm
IADMS process
It can be stopped if no IAD

needs to be managed.
UmsIgwbDm
iGWB management process
It can be stopped if non iGWB

UmsMRSDm
MRS management process
It can be stopped if non MRS

1-6
Process
Function
Description
It can be stopped if no service
or resource needs to be
operated.
Note: After this process is
stopped, the resource client
and service client will prompt
that the communication with
the daemon fails when loading
data.
UmsServDm
It configures services and resources.
UmsSgDm
SG7000 management process
It can be stopped if no SG7000

UmsSoftXV3Dm
SoftX3000V3 management process
It can be stopped if non

SoftX3000V3 needs to be
managed.
UmsSyncDm
NE synchronization process. It monitors the

operations performed on devices (except
those performed through the NMS) and
keeps the NMS data consistent with the
device data.
It must be started.
UmsTmg8010Dm
TMG8010 management process
It can be stopped if no
TMG8010 needs to be
managed.
UmsUMG8900Dm
UMG8900 management process
UMG8900 needs to be
managed.
UmsXmlDM
IADMS/TFTP/DHCP device management

process
It can be stopped if non

IADMS/TFTP/DHCP device
UmsXmlAgent
IADMS northbound
interface
It can be stopped if non IAD

needs to be managed and the
IADMS does not need to
interact with the upper NMS.
UmsNISmDm
Northbound interface module (service)

process
It can be stopped if this

northbound interface is not
needed.
UmsNI112Dm
Northbound interface module (subscriber

line test) process

needed.
IPMSDm
Performance measurement process
It can be stopped if
performance measurement is
not needed.
DC process

no data needs to be backed up
automatically or manually or no
program needs to be loaded
manually.
DCServer
1-7
interface
module
Process
Function
Description
iManager N2000 BMS

ADSLiDm
ADSL northbound interface

needed.
CFMSiDm
CFMS service provisioning interface

needed.
CLTSiDm
CLTS test interface

needed.
StdCltsiDm
StdClts test interface

needed.
TestDm
Line test process
It can be stopped if the line test

function is not needed.
DSLMgrDM
DSL Manager process
It can be stopped if no service

needs to be operated.
EnpowerDm
Environment monitoring process

environment
monitoring
Esrv5r3
ESRV5R3 management process
ESRV5R3 needs to be
managed.
HonetDm
Honet management process
It can be stopped if no HONET

NE needs to be managed.
ISN8850V5R2Dm
ISN8850V5R2 management process
ISN8850V5R2 needs to be
managed.
Ma5100V1Dm
MA5100V1 management process
MA5100V1 needs to be
managed.
Ma5100V2R1Dm
MA5100V2R1 management process
MA5100V2R1 needs to be
managed.
Ma5105Dm
MA5105 management process
It can be stopped if no MA5105

Ma5200V1R6Dm
managed.
Ma5200V1R7Dm
managed.
1-8
Process
Function
Description
Ma5200V1R9Dm
managed.
Ma5300Dm
MA5300 management process
It can be stopped if no MA5300

Md5500V1Dm
MD5500V1 management process
MD5500V needs to be
managed.
Radium8750Dm
Radium8750 management process
Radium8750 needs to be
managed.
Ua5000Dm
UA5000 management process
It can be stopped if no UA5000

IPMSDm
Performance measurement process.

performance
measurement
DC process

no data needs to be backed up
automatically or manually or no
program needs to be loaded
manually.
DCServer
iManager N2100
SwitchDm
Switch management. It adds or deletes

devices together with the topology daemon
and the resource daemon. It also
synchronizes device data as well as
manages and measures the switch
resources.
It must be started.
HonetDm
HV20 NE management. It provides topology

management for HV20 devices and calls
service clients for them.
It must be started.
IPMSDm
Performance measurement process. It

manages the traffic measurement tasks for
the BAM of the switch. It also provides
functions such as querying measured traffic
data, managing data integrity, managing
threshold alarms, traffic measurement
(including time distribution measurement,
time distribution comparative measurement,
and global traffic measurement).
It must be started.
EnpowerDm
Environment monitoring process. It monitors

the environment parameters and power
supply of the devices.
It must be started.
1-9
Process
Function
Description
N2100MCsvr
Upper NMS. It manages topology and

alarms in a centralized manner. It provides a
hierarchical network management solution
together with iManager N2000.
It must be started.
Java
Report management.

the report function is not
needed.
1.3.2 Checking Connectivity of NMS Server, NMS Client, and Managed

Devices
I. Purpose
z
To ensure the network connectivity between NMS workstation and the managed
NEs.
To ensure the network connectivity between NMS clients.
To ensure the network connectivity between lower NMS and upper NMS.
II. Reference
If a device node or board is not gray, it indicates that its communication is normal. If the
system prompts that the refreshing of device nodes or a device panel succeeds, it also
indicates that the communication of the device nodes is normal.

1)
For managed NEs
At the NMS client, select [Edit/Refresh Status] to view the colors of the device
nodes.
Table 13 shows the meaning of the device icon colors.

Table 13 Meaning of device icon colors
Legend
1-10
Color
Polling status
Green
Normal
Gray
Offline
Cyan
Slight fault
Yellow
Minor fault
Orange
Major fault
Red
Critical fault
Note:
SNMP devices have only three statuses: normal (green), offline (gray), and fault (red).
If a device icon shows the offline status, it may be caused by disconnection from
the network. In this case, select the icon, and then select [Edit/Device Access
Protocol]. In the dialog box as shown in Figure 1-3, click <Test> to check whether
the device connects well with the network. Then handle the problem accordingly.
Figure 1-3 Device access protocol parameters

z
If a device icon shows the fault status, select the icon, right click, and then select
[Browse Alarm] to view the alarm information. Then handle the problem
accordingly.
2)
For route switching device, clients, and upper or lower NMS device related to the
NMS workstation
Start a terminal under Solaris, ping other devices to check the connectivity. The
following takes ping 10.71.47.43 as an example.
# ping 10.71.47.43
10.71.47.43 is alive
If the above information is displayed, it means that the device connects well with the
network.
z
Open the DOS window from the Windows, ping other devices to check the
connectivity. The following takes ping 10.71.47.43 as an example.
C:\>ping 10.71.47.43
Pinging 10.71.47.43 with 32 bytes of data:
1-11
Reply from 10.71.47.43: bytes=32 time<10ms TTL=128

Ping statistics for 10.71.47.43:

Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum =
0ms, Average =
0ms
If the above information is displayed, it means that the device connects well with the
network.
1.3.3 Viewing Topology and Alarm Information

I. Purpose
To keep track of device alarm status and perform maintenance operations for the
device and system based on the alarm status in order to prevent faults from occurring.
II. Reference
Based on severity, device alarms fall in four levels: critical, major, minor, and warning.
For the meaning of alarm icons of the four levels, see Table 14, Table 15, and Table
16.
Table 14 Icons of unrecovered alarms and their meaning
Legend
Color
Alarm level
Cyan
Warning
Yellow
Minor
Orange
Major
Red
Critical
Table 15 Icons of unacknowledged alarms and their meaning

Legend
1-12
Color
Alarm level
Cyan
Warning
Yellow
Minor
Orange
Major
Red
Critical
Table 16 Icons on the alarm panel and their meaning

Legend
Color
Alarm level
Cyan
Warning
Yellow
Minor
Orange
Major
Red
Critical

The device status and alarms need to be monitored in real time. To facilitate monitoring
of current alarm information, the topological view displays the device alarm status as
shown in Table 14 and Table 15, and the alarm panel thumbnail at the NMS client
displays the reported alarms as shown in Table 16.
z
If an alarm indicator on the alarm panel thumbnail flashes, it indicates that an

alarm of the corresponding level is reported. In this case, double click the
thumbnail to display the alarm panel, and then double click the corresponding
alarm indicator to view all the current data of the alarms of the level.
If a device alarm status icon is displayed in the topological view, it indicates that
the device has reported an alarm. In this case, select the icon, right click, and then
select [Browse Alarm] to view the alarm information of the device.
After querying the current alarm, focus on the critical and major alarms. Locate the fault
based on the alarm details and the possible fault cause given by the system, and then
handle the problem accordingly.
1.3.4 Backing Up NMS Database

I. Purpose
To weekly back up the configuration data stored in the NMS database and view the
automatic backup status of the automatic backup tool in order to minimize data loss and
recover the NMS quickly in case of faults.
II. Reference
The NMS database needs to be automatically or manually backed up to the specified
directory or medium. By default, the NMS database is backed up to the backup
directory under the installation directory of the iManager N2000.

At the SysMonitor, click the Database tab to view the current usage and last backup
time of the NMS database, as shown in Figure 1-4.
1-13
If the automatic backup function is enabled, view the database backup files in the
specified directory or medium to check whether the automatic backup is normal. If
necessary, back up the database manually and keep the latest backup files, so as to
minimize data loss and recover the NMS quickly in case of faults.
During daily maintenance, two backup modes are available: manual backup and
automatic backup. The automatic backup is preferred over manual backup to ease
daily maintenance.
z
Follow this procedure to configure the automatic backup:
1)
Double click
2)
to start the database backup tool.
Select [System/Add Database Server] to configure the database server, and then
log in.
3)
Select [Configuration/Database Set] to configure the database set.
4)
Select [Configuration/Auto Backup Policy] to configure the automatic backup

policy.
5)
Select [Configuration/Backup Device] to configure the backup device.
6)
Select [Operation/Auto Backup Task] to create the automatic backup task.
Follow this procedure to back up the NMS database manually:
1)
Start the database backup tool, and then log in to the server node to be backed up.
2)
Select [Operation/Manual Backup].
3)
In the Select database set to backup area, select the database set to be backed
up, and then click <Next>.
4)
In the Selection backup device, select the target device, and then click <Finish>.
5)
Wait until the backup is completed.
It is recommended that the automatic backup be done between 00:00 and 06:00 so that
the normal maintenance operations will not be affected. The manual backup is
recommended to be done when the load of the NMS server is not heavy.
Note:
For details on the automatic backup and manual backup, see 3.2 Database Backup Tool".
1.3.5 Backing Up Device Configuration

I. Purpose
To weekly back up the configuration data of NEs and view the automatic backup status
of the Data Center (DC) in order to minimize data loss and recover devices in case of
faults.
1-14
II. Reference
The configuration data of NEs should be automatically or manually backed up to the
specified directory of the TFTP/FTP server. The default directory is ./TFTP/backup.

During daily maintenance, two backup modes are available: manual backup and
automatic backup. The automatic backup is preferred over manual backup to ease
daily maintenance.
If the automatic backup function is enabled, view the configuration data backup files in
the specified directory of the TFTP/FTP server to check whether the automatic backup
is normal. If necessary, back up the NE configuration data manually and keep the latest
backup files, so as to minimize data loss and recover devices in case of faults.
z
Follow this procedure to configure the automatic backup:
1)
Configure TFTP/FTP service.
2)
Double click
3)
Select [Options/Config System Information] to specify the backup directory.
4)
Select [Options/Config Default Save Policy] to configure the default backup policy.
5)
Select a device type node, right click, and then select [Configure Backup Policy] to
to start the DC, and then log in.
modify the backup policy.

6)
Select a device type node, right click, and then select [Run Backup Policy] to run
Follow this procedure to back up the NE configuration data manually:
1)
In the device navigation tree, select a device, right click, and then select [Backup].
2)
In the Backup dialog box that appears, click <Start>.
3)
After the configuration data of all the selected devices are backed up, click
the backup policy.
<Close> to end the backup operation, or click <Restart> to back up the NE data
again.
Note:
For details on the automatic backup and manual backup, see HUAWEI iManager N2000 Fixed Network
Integrated Management System Data Center User Manual.
1.3.6 Viewing Operation Log

I. Purpose
To check whether any illegal operations are performed so as to ensure the normal
running of the NMS and NEs.
1-15
II. Reference
Check whether any malicious or unauthorized operations are performed.

1)
Log in to the NMS as admin.
2)
At the NMS client, select [System/Browse User Log].
3)
In the Log Browse dialog box that appears, view the operation logs of the NMS
users.
1.3.7 Managing User Authority

I. Purpose
To view the users of the NMS and NMS workstation regularly, delete unauthorized
users, and adjust the authority of common users reasonably, so as to ensure the
security of the NMS and NMS workstation. After a device is added, authority must be
allocated to the person who manages the device.
II. Reference
View the users of the NMS and NMS workstation, clear illegal users, and adjust the
authority of common users reasonably.

1)
At the NMS client, select [System/Security Manager], and then do as follows:
Delete illegal users.
Set user ACL.
Allocate operation authority to users.
Allocate management authority to users.
2)
To manage the users of the NMS workstation, at the Solaris maintenance terminal,
switch to a superuser by entering #admintool. In the window that appears, do as
follows:
Delete illegal users.
Add users and user groups.
Add or delete user authority, and change user login password.
3)
In Windows, select [Start/Programs/Administrative Tools/Computer Management].

In the Computer Management dialog box that appears, manage the Windows
users.
1-16
Note:
The user authority must be allocated based on user group and operation set. The users with the same
authority should be added to the same group. The authority must not be allocated based on a single user,
otherwise the performance of the NMS will be affected.
1.3.8 Viewing Used NMS Database Space

I. Purpose
z
To view the automatic dumping status and automatic backup status of the system
and ensure that enough free space is available in the database system for storing
data and logs.
To monitor the usage of the database space and expand the database space (if
necessary), so as to prevent error and data loss due to insufficient space.
II. Reference
The free database space must be determined according to the system requirement. We
recommend that the used database space be less than 80%.

At the SysMonitor, click the Database tab to view the current usage of each database,
as shown in Figure 1-4.
Figure 1-4 Database information

If the used space of a database exceeds 80%, handle the problem accordingly.
1-17
z
For FaultDB, the system supports automatic dumping, manual dumping, and
dumping when the database is full.
1)
At the NMS client, select [Fault/Dump Alarm].
2)
In the "Dump Alarm dialog box as shown in Figure 1-5, set the dumping
conditions, and then click <OK> to manually dump the alarm data and event data.
Figure 1-5 Dumping alarm data

3)
At the NMS client, select [Fault/Fault Setting/Dump&Sync&Ack].
4)
In the Dump&Sync&Ack dialog box that appears, click the Others tab, as
shown in Figure 1-6.
Figure 1-6 Automatic alarm dumping

5)
Set Auto Ack after Alarm Clear, Enable Alarm Auto Dumping, Enable Event
Auto Dumping, Dump Alarms When Overflow, and Dump Events When
Overflow, and then click <OK>.
1-18
Note:
z
We recommend these settings:
The automatic alarm dumping period be 7 days and the alarms to be dumped be those generated 7 days
ago.
The automatic event dumping period be 2 days and the alarms to be dumped are those generated 2 days
ago;
20% of the alarm/event data be dumped when the alarm/event database is full.
These values can be changed based on the network size.
z
Historical alarms can be dumped automatically but current alarms cannot. By default, the automatic
dumping operation is performed at 1:00 A.M.
The current alarm table can store up to 50,000 alarm records. The history alarm table store can store
up to 1,000,000 history alarm records. The event alarm can store up to 100,000 event records.
6)
If the automatic alarm dumping and automatic event dumping functions are
enabled, view alarm dumping files and event dumping files in the directory for
automatic dumping (../serve/dump/ by default) to check whether the dumping
functions are normal.
For LogDB, the system supports automatic dumping, manual dumping, and
dumping when the database is full.
1)
At the NMS client, select [System/Dump Log].
2)
In the Dump Log dialog box as shown in Figure 1-7, set the dumping condition,
and then click <OK> to manually dump the user logs.
Figure 1-7 Dumping user logs

3)
At the NMS client, select [System/System Setting].
4)
In the System Setting dialog box that appears, click the Log Dumping tab, as
1-19
Figure 1-8 Automatic log dumping

5)
Set the desired parameters, and then click <OK>.
Note:
z
We recommend these settings:
Automatic log dumping period be 90 days and the logs to be dumped are those generated 2 days ago.
300,000 log entries be dumped when the log database is full.
These values can be changed based on the network size.
z
6)
The system can store up to 300,000 log entries.
If the automatic alarm dumping and automatic event dumping functions are
enabled, view alarm dumping files and event dumping files in the directory for
automatic dumping (../serve/dump/ by default) to check whether the dumping
functions are normal.
1)
For IPMS and PerfDB, the system supports security term.

At the NMS client, select [Performance&Stat/Performance Data Management] to
back up the performance data.
2)
At the NMS client, select [Performance&Stat/Performance Data Management] to

delete the performance data before the security term.
3)
If necessary, expand the IPMS and PerfDB.
Other databases can be expanded.
1-20
4)
At the SysMonitor, select [System/Stop All Processes] to stop all the NMS
processes to disconnect the database to be expanded from the NMS.
5)
Log in to the NMS database using isql.
root@umstest44 # . /n2kuser/.profile
root@umstest44 # isql -Usa -Psa_password -SN2000DBServer
6)
Create a database device using disk init.
1>
disk
init
name=myextenddevicename,
physname=/opt/sybase/data/myextenddevicefile.dat, vdevno=100, size=51200

2> go
Note:
name=device name
physname=name of physical device
vedev=virtual device number
//Path and name of the file where the device data is saved.
//It must be unique. Run sp_helpdevice to view the used device
numbers.
size=device capacity
7)
//Measured in 2k.
Run alter database to make the database device available.
1> alter database dbname on myextenddevicename=100

2> go
Note:
dbname
//Name of the database to be expanded; for example, IPMS, LogDB, and FaultDB.
myextenddevicename
//Name of the database device.
myextenddevicename=available capacity
//Measured in 1M.
To store log entries in the database device, run these commands:

1> alter database dbname log on myextenddevicename=100
2> go
To store both log entries and data in the database device, run these commands:
1>
alter
database
dbname
myextenddevicename2=50
2> go
1-21
on
myextenddevicename1=100
log
on
Note:
If you want to expand the database to a bare partition, set the name of the physical device to that of the
bare partition when creating the database device.
8)
Run quit or exit to leave the NMS database.
9)
At the SysMonitor, select [System/Start All Processes] to start all the NMS
processes.
Note:
z
The database expansion is applicable to Sybase. The SQL Server supports automatic expansion, so it
is not necessary to expand it manually.
After the database is expanded, the initial configuration cannot be restored. The database space
cannot be expanded without limit. Therefore exercise caution when expanding the data section and
log section.
1.3.9 Viewing Used Hard Disk Space of NMS Server

I. Purpose
To check the usage of the partitions of the disk in the server to prevent the system
performance from being degraded due to insufficient free space. If necessary, clear up
the disk and clear the junk files to ensure sufficient free disk space.
II. Reference
The used space of each partition should be less than 80%.

At the SysMonitor, click the Disk tab to view the current usage of the disk, as shown in
Figure 1-9.
1-22
Figure 1-9 Hard disk information

If the used space of a partition exceeds 80%, clean up the disk and clear the junk files
as follows:
1)
Copy the automatically dumped alarm files from the directory for automatic alarm
dumping to a tape drive or another storage medium, and then clear the alarm files
from the directory for automatic alarm dumping.
2)
Copy the automatically dumped log files from the directory for automatic log
dumping to a tape drive or another storage medium, and then clear the log files
from the directory for automatic log dumping.
3)
Delete the unwanted NMS database backup files.
1.3.10 Checking Hardware, Power Supply, and Equipment Room

Environment of NMS Workstation
I. Purpose
To check the operation status of the NMS workstation, auxiliary equipment, and UPS.
II. Reference
z
The temperature inside the equipment room must be normal (15C30C).
The humidity must be normal (40%65%).
The equipment room must be clean.
The server must be equipped with UPS.
The NMS must be provided with reserved power supply.
The power socket must be connected well.
1-23

1)
Check the temperature, humidity, and cleanness inside the equipment room.
2)
Check the position of the NMS workstation.
3)
Check the keyboard, mouse, display, network adapter, serial port, power cable,
network cable, and CD-ROM of the workstation.
4)
Check whether the NMS server is equipped with UPS and whether the NMS is
provided with reserved power supply.
5)
Check whether the power cables are aged.
6)
Check whether the reserved power supply of the NMS is connected well and
whether any contact point is eroded.
7)
Check whether the power socket is connected well and whether the switch is
normal.
8)
Check whether the voltage and current are displayed normally.
1.3.11 Installing Windows Patches and Killing Viruses in Time

I. Purpose
To prevent the NMS server and computers from being attacked by network viruses.
II. Reference
None.

Microsoft releases Windows patches aperiodically. Install the patches in time
Update your anti-virus software in time, and scan the NMS server, NMS workstation,
and NMS client at regular intervals, to ensure normal running of the NMS.
1-24
1.4 Maintenance Reports

1.4.1 Duty Report
NMS name:
NMS IP address:
Duty time
(Hour)
Date: (Month)
Shifted
from
(Hour)
Maintenance items
Result
Checking server performance
Normal
Abnormal
Checking connectivity of NMS

server, NMS client, and devices
Normal
Abnormal
Viewing
information
Normal
Abnormal
topology/alarm
Normal
Abnormal
Contents
Normal
Abnormal
Tools, instruments, and documents:
Summary:
Duty
contents
Abnormalities and solutions:
Outstanding problems:
Supervisors feedback:
1-25
(Day)
(Year)
Shifted
to
Remark
1.4.2 Weekly Maintenance Report

NMS name:
NMS IP address:
Maintenance period:
From (Month)
(Day)
(Year) to (Month)
(Day)
(Year)
Maintenance items
Backing up
database
NMS
Backing up
configuration
device
Maintenance contents
Viewing operation logs
Abnormalities and solutions:
Remarks:
1-26
Maintenance
person
Maintenance time
1.5 Starting and Shutting Down an NMS Workstation

I. Start an NMS workstation
Follow this procedure to start the NMS workstation:
1)
Start the Solaris.
2)
Run the environment variables.
ksh
. /n2kuser/.profile
3)
Start the Sybase.
cd /opt/sybase/ASE-12_0/install
./startserver -f ./RUN_N2000DBServer
4)
Start the NMS.
cd /opt/n2000/server/bin
sh ./startn2000.sh
II. Shut down an NMS workstation
Caution:
Do not shut down the NMS workstation by using halt (for Solaris) or by cutting the power supply, otherwise
the system may fail to recover.
Follow this procedure to shut down the NMS workstation:

1)
Run the SysMonitor, and then stop all the NMS processes.
2)
Quit the Sybase.
ksh
. /n2kuser/.profile
isql -Usa -Psa_password -SN2000DBServer
1>shutdown
2>go
3)
Quit the Solaris.
#sync
#init 5
1-27
Chapter 2 Troubleshooting
This chapter introduces alarm definition and categories. It presents general procedure
and methods for troubleshooting. It also provides some typical troubleshooting cases
for reference.
2.1 Basic Concepts

2.1.1 Alarm Definition and Category
I. Fault alarm and event alarm
Generally, alarms are divided into fault alarms and event alarms. A fault alarm usually
corresponds to a recovery alarm. An event alarm only indicates the occurrence of an
event.
II. Alarm ID
An alarm ID identifies an alarm uniquely. It consists of four bytes. Each alarm ID
corresponds to one alarm. Alarm IDs are usually allocated according to alarm type and
alarm module type.
III. Alarm level

An alarm level indicates the severity of an alarm. Based on the severity, alarms are
divided into four levels: critical alarm, major alarm, minor alarm, and warning alarm.
z
A critical alarm refers to a global alarm that endangers the normal running of
devices and needs to be handled immediately. For example, power failure and
clock output fault are critical alarms.
A major alarm refers to a board alarm or line alarm occurred within a specified
range. It needs to be handled immediately, otherwise the normal running of the
user services will be affected. For example, fiber cut and physical line fault are
major alarms.
A minor alarm refers to an ordinary fault alarm or event alarm that indicates
whether a board or line is normal. For example, bit error on a physical line is a
minor alarm.
A warning alarm refers to a status change or event in which you might be

interested. It can also be a message prompting that a device recovers. A warning
alarm does not affect the system performance or user services.
IV. Alarm category

Alarms functionally fall into many categories, including:
z
Power supply alarm

2-1
z
Environment alarm
Trunk alarm
Hardware alarm
Software alarm
Running alarm
Communication alarm
QoS alarm
Process alarm
2.1.2 Terms
I. Real-time alarm display
Real-time alarm display means that the newly reported alarms are displayed in real
time. In this way, you can keep track of the operation status of devices.
The real-time alarm browser displays the recently generated alarms matching the filter.
It automatically scrolls up to display the latest alarms.
II. Current alarm

A current alarm refers to an alarm in one of the following statuses:
z
Unrecovered and unacknowledged
Unrecovered and acknowledged
Recovered and unacknowledged.
Current alarms require handling.
III. Historical alarm

An historical alarm refers to a recovered and acknowledged alarm. It does not require
handling.
IV. Real-time event display

Real-time event display means that the newly reported events are displayed in real time.
In this way, you can keep track of the operation status of devices.
The real-time event browser displays the recently generated events matching the filter.
It automatically scrolls up to display the latest events.
V. Alarm acknowledgement
Alarm acknowledgement means confirming an alarm. The alarm acknowledgement
status (acknowledged or unacknowledged) indicates whether an alarm is handled by
the user.
Manual acknowledgment and automatic acknowledgement are supported.
2-2
VI. Alarm state transition

If a device becomes faulty, it reports an alarm to the NMS. The NMS receives the alarm
in real time. Currently, the iManager N2000 can receive alarms and events reported
through MML and SNMP.
z
The alarm newly received by the NMS is in unrecovered and unacknowledged

status.
After the NMS receives the corresponding recovery alarm, the alarm becomes
recovered .
After the fault is eliminated and the alarm is recovered, the alarm needs to be
acknowledged manually or automatically. After that, the alarm becomes
acknowledged.
After the alarm is recovered and acknowledged, it becomes a historical alarm.
Figure 2-1 shows the alarm state transition model.

NE
Reporting alarm
Acknowledgement
Unacknowledged & unrecovered
alarm
Recovery
Acknowledged &
unrecovered alarm
Recovery
Acknowledgement
Unacknowledged &
recovered alarm
Historical alarm
Figure 2-1 Alarm state transition
2.2 General Troubleshooting Procedure
Note:
An alarm usually reflects a fault. When a device is faulty, it sends an alarm to the NMS. The NMS receives
the alarm in real time. Therefore, after you analyze and locate the alarm cause and take corresponding
measures to eliminate the fault, the alarm will recover.
Generally, troubleshooting takes four steps:

1)
Collecting information.
2)
Judging the fault.
3)
Locating the fault.
4)
Eliminating the fault.

2-3
See Figure 2-2.

View alarm info.
Collect fault info.
Restore network status
Analyze alarm/fault info.
Judging fault
Make possible schemes
Locating fault
Carry out a scheme

N
Collecting info.
Eliminating fault
Fault eliminated?
Y
Acknowledge alarm
Figure 2-2 General troubleshooting procedure
2.2.1 Collecting Information

When a fault occurs, you need to collect detailed raw information such as related alarm,
symptom, operation log, and time, so as to locate the fault quickly.
2.2.2 Judging the Fault

After getting the fault information, you need to judge the range and type of the fault.
2.2.3 Locating the Fault

Fault locating is the most important troubleshooting step. You need to compare and
analyze the possible causes and detect the real cause.
2.2.4 Eliminating the Fault

After detecting the fault cause, you need to take proper measures to eliminate the fault
and recover the system. Before eliminating the fault, you need to back up the
necessary data.
If you cannot eliminate the fault and need support from Huawei, we recommend that
you make these preparations:
z
Collecting necessary information about the fault.
Making necessary debugging preparations.
2-4
The engineers from Huawei may guide you through some operations to collect more
information about the fault or to eliminate the fault. Therefore, you need to make
necessary preparations.
2.3 General Fault Locating Methods

2.3.1 Analyzing Raw Information
Raw information includes the fault information reflected by the faults reported by the
user and other offices and the related information obtained by the maintenance
personnel at the early stage of the fault.
Raw information is very important for fault judgment and analysis. It can be used for
judging fault range and type. It also provides reference for locating the problem.
2.3.2 Analyzing Alarm Information

Analyzing alarm information is the major means for analyzing a device fault.
Alarm information refers to the information outputted by the NMS after receiving a
device alarm. It is usually reflected through audio, light, LED or screen.
Alarm information includes detailed description of the fault or abnormality, possible
causes, and recovery suggestions, as well as the hardware, link, and system
configuration of the involved device. Alarm information is the major basis for fault
analysis and locating.
Alarm information analysis is used for locating the fault and detecting the cause. Based
on the complete alarm information outputted by the NMS and device, you can locate
the fault cause directly or with the help of other methods.
2.3.3 Analyzing Indicator Status

Running and status indicators are available on each board of a device. Function or
feature indicators are also available on some boards. These indicators reflect the
operation status of the corresponding boards. Most of them also reflect the operation
status of circuits, links, optical paths, and nodes, active/standby status, and so on. They
provide an important basis for fault analysis and locating.
Indicator status analysis is used for locating a fault or detecting the cause. It provides
reference for further handling of the fault. Because the indicator status analysis does
not provide enough information, it is usually used together with alarm information
analysis.
2-5
2.3.4 Tracing Connection and Signaling

Tracing connection and signaling is very important for analyzing failed call connections
and failed signaling coordination between devices. Based on the traced results, usually
you can detect the cause for device interconnection failure or call connection failure.
2.3.5 Test and Loopback

Test means that software test tool, meters, and instruments are used to measure the
technical parameters related to the possible faulty objects such as subscriber line,
transmission channel, and relay device. Based on the test result, you can judge
whether the tested object is faulty or will become faulty.
Loopback means that self-loop back is performed on a transmission device or channel
through hardware or software. Based on the status of the transmission device or
channel, service, and signaling coordination, you can judge whether the hardware is
normal or whether the software parameters are set correctly. Loopback is usually used
to locate problems related to the transmission part and check whether the relay
parameters are set properly.
2.3.6 Comparison and Replacement

Comparison means that a faulty part is compared with a normal part to detect their
differences, so as to locate the problem. It is used to locate a fault when the fault range
is narrow.
Replacement means that a faulty part such as a board or fiber is replaced with a normal
one to locate the fault. It is used to locate a fault when the fault range is broad.
2.3.7 Switchover and Reset

Switchover means that the services running on the active board or device are switched
to the standby board or device. It aims to check whether the active board or device is
normal and whether the active and standby boards or devices coordinate smoothly.
Reset means that a part of a device or the whole device is manually restarted to check
whether the software is running well or a program is suspended. It is used when a fault
cannot be eliminated using other methods.
Compared with other methods, switchover and reset cannot be used for locating a fault
accurately. Because of the random software running, it is probable that the fault
symptom does not recur after the switchover or reset. This may bring a hidden trouble
to the device. Therefore, they can be used only when other methods are not available.
2-6
2.3.8 Using Instruments and Meters

Instruments and meters are used for fault analysis and locating. They provides visual
data to reflect the nature of a fault, so they are widely used for line analysis, power
supply test, signaling analysis, waveform analysis, bit error detection, and so on.
2.3.9 Performance Measurement

By measuring the device performance data, you can judge the device operation status
and network quality. This helps you diagnose and locate the fault. It also provides
reference for handling device faults or solving network problems.
2.4 Troubleshooting Cases

2.4.1 The SQL Server Fails to Start After the Password of administrator Is
Changed.
I. Symptom
When I log in to Windows 2000 after changing the password of the administrator, I find
that the SQL Server does not start together. I start the SQL Server from the service
manager, the system prompts that the SQL server cannot start due to login failure.
II. Cause analysis

The iManager N2000 server requires the authentication of SQL Server and Windows,
so the password of administrator is saved in the database. After the password of
administrator is changed, the one set in the database remains unchanged. In this
case, the SQL server login will fail due to inconsistent passwords.
III. Solution
Follow this procedure to change the Windows login password of the SQL Server:
1)
Change the password of administrator back to the original one.
2)
Start the SQL Server from the database service manager.
3)
Change the password of administrator from Computer Management.
4)
Start the database enterprise manager.
5)
From the database server list on the left, right click the desired server, and then
select [Properties].
6)
In the SQL Server Properties dialog box that appears, click the Security tab.
7)
In the Startup service account area, select This account, and then change the
password of administrator to the new one, and then click <OK>.
8)
In the dialog box that appears, click <Yes> to restart the database server.
2-7
2.4.2 The Adaptive Server Cannot be Created During Installation of Sybase.

I. Symptom
When I install Sybase 11.9, the system prompts that the creation of adaptive server
fails.
II. Cause analysis

Before installing Sybase, the kernel of the Solaris needs to be changed, and the shared
memory needs to be set; otherwise, this failure occurs.
III. Solution
1)
Set the shared memory: Add this line to the end of the /etc/system file, and the
save the change.
set shmsys: shminfo_shmmax = actual size of the physical memory of the
workstation (M) *1024*1000
2)
Restart the workstation.
3)
Reinstall the Sybase.
2.4.3 The NMS Cannot Be Installed After the SQL Server Is Reinstalled.
I. Symptom
After uninstalling the SQL Server and NMS from the computer, I try to reinstall them to
the original installation directory. During the installation, the SQL Server already runs
and all the parameters are set correctly, but the system prompts that the reinstallation
of the NMS fails.
II. Cause analysis

The SQL server is uninstalled, but the NMS database is not. In this case, the NMS
database will fail to be reinstalled to the original directory because the NMS database
files already exist.
III. Solution
1)
Select [Start/Programs/Microsoft SQL Server/Enterprise Manager].
2)
In the SQL Server Enterprise Manager window that appears, select Databases
under SQL Server Group, as shown in Figure 2-3.
2-8
Figure 2-3 SQL Server Enterprise Manager

3)
Delete all databases except master, model, msdb, pubs, and tempdb.
4)
Install the NMS.
Note:
Before uninstalling the SQL Server, back up the important databases and delete the data files from the
NMS databases. After that, uninstall the SQL Server and then reinstall it.
2.4.4 The NMS Client and SysMonitor Cannot Be Used Due to Unsuccessful
Start of the NMS Daemon.
I. Symptom
After I install the NMS and restart the NMS server, the NMS client cannot be used, and
the system prompts that the communication connection cannot be established. When I
try to use the SysMonitor, the system also prompts that the communication connection
cannot be established.
I check the NMS database and find that it fails to start. I check and set the environment
variables and start the NMS database manually. Then I try to use SysMonitor, but the
system still prompts that the communication connection cannot be established.
2-9
II. Cause analysis

Normally, if the NMS server is restarted after the installation of the NMS, the NMS
database and daemon will start automatically. Here, the NMS database and daemon
fail to start due to improper environment variables and other causes.
The related configuration is modified and the NMS database is started manually.
However, if some NMS processes need to be started through SysMonitor, the MDP and
SysMonitor processes of the NMS must be started first. Because SysMonitor is not
started after the NMS database is started, it cannot be used.
III. Solution
1)
2)
Check whether the Sybase starts.

If the Sybase fails to start, check whether the environment variables of the Sybase
are set correctly.
3)
If the environment variables are incorrect, correct them.
4)
Start the database, and try to use the SysMonitor.
If the system still prompts that the communication connection cannot to be established,
it is possible that the related NMS processes do not start automatically after the NMS
database starts.
5)
Check whether the NMS start script is available under the NMS installation
directory.
6)
If the script is available, switch to the superuser, run the script.
7)
After a while, run the SysMonitor.
8)
Run the NMS client.
2.4.5 The Security Daemon Fails to Start After the License Is Updated.
I. Symptom
The Solaris, Sybase, and NMS server run well, but the security NMS daemon fails to
start after the license is updated.
II. Cause analysis

1)
The license file is not unique or is invalid.
2)
The format of the license file is not the text format of the Solaris.
III. Solution
1)
Check
whether
valid
license
file
is
available
in
the
$N2000ROOT/server/license directory.
2)
If a valid license file is available, transfer it to the NMS server in ASCII format
through FTP, and then update the license file.
3)
Restart the security daemon.
2-10
Note:
The license generator runs under Windows, so the format of the generated license file is different from the
text format of UNIX. After the license file is transferred to the Solaris server in ASCII format (asc mode)
through FTP, its format can be converted automatically.
2.4.6 The Fault Daemon Fails to Start.

I. Symptom
The SysMonitor detects that the fault daemon always fails to start.
II. Cause analysis

To receive traps from devices, the fault daemon needs to monitor port 162 during start.
If the port is used by any other process, the fault daemon fails to start.
III. Solution
1)
Use netstat a to check whether any other process is using the port.
2)
If a process is using the port, stop the process, and then start the fault daemon.
2.4.7 The iManager N2000 UMS Fails to Add an AMG Due to Incorrect snmp
port.
I. Symptom
An AMG5000 cannot be added to the iManager N2000, and the system prompts that
the SNMP device cannot be created due to insufficient authority.
II. Cause analysis

The AMG5000 is not configured with NMS parameters or the configured NMS
parameters are incorrect.
III. Solution
1)
Log in to the AMG5000 through Telnet.
2)
Use show nms to view the configured NMS workstation information.
3)
Check whether the record of the local NMS workstation is available.
4)
If no record of the local NMS workstation is available, use nms add to add it.
5)
If the local NMS workstation is added to the AMG5000, check whether the
community names and IP address set on the AMG500 are consistent with those
set in the NMS.
6)
If they are consistent, check whether the snmp port is set to 0.
2-11
7)
If the snmp port of the AMG5000 is not 0, activate the local NMS workstation
using no nms active, change snmp port to 0 using nms modify, and then
activate the local workstation using nms active.
8)
Add the AMG5000 to the NMS.
2.4.8 The iManager N2000 UMS Cannot Receive Alarms from a TMG Due to
an Incorrect Alarm Language.
I. Symptom
A TMG is already added to the NMS. When I reset the TMG, no alarm information of the
TMG is displayed in the fault browser of the NMS. I use Sniffer to capture packets and
find that some alarm information is reported by the TMG to the iManager N2000 UMS.
II. Cause analysis

1)
Because the TMG is successfully added to the NMS, it indicates that SNMP
parameters such as snmp-server acl, snmp-server community ro, and
snmp-server community rw are set correctly on the TMG.
2)
I use Sniffer to capture packets and detect some alarm information is reported by
the TMG to the iManager N2000 UMS. It indicates "traphost" is set correctly.
3)
I use Sniffer to capture packets and detect various alarm levels. It indicates that
traphost level is set correctly.
4)
I use Sniffer to capture packets and detects that some alarm information appears
in Chinese, indicating that traphost language is set to Chinese. I also detect
some illegal characters, indicating that the alarm language is set improperly.
III. Solution
1)
Set "traphost language to English on the TMG.
2)
Restart the NMS daemon.
3)
Reset the TMG board.
4)
View the fault browser to check whether TMG alarms are generated.
2.4.9 The iManager N2000 UMS Fails in Circuit Test and Loop Line Test
Because No Test Group Is Created on the AMG.
I. Symptom
An AMG is added to the NMS, and operations such as board addition and query can be
performed on the AMG. However, an error message is displayed during the test of the
circuit/loop line of the ASL board.
II. Cause analysis

1)
The TSS board is faulty.
2)
No test group is configured for the AMG.
2-12
III. Solution
1)
Self-test the TSS board through the NMS.
2)
If the self-test succeeds, view the test group configuration of the AMG to check
whether a TSS board is specified for the ASL board.
3)
If no TSS board is specified, specify one for the ASL board.
To create a test group, run the following command:

AMG5000(config)#testgroup
{ set<K>|clear<K> }:set
{ groupno<U><0,9> }:0
{ phy<K> }:phy
{ frameid/slotid<S><3,5> }:0/2
To add a test group to the frame, run the following command:

AMG5000(config)#frame
{ set<K>|delete<K>|add<K> }:set
{ frameid<U><0,9> }:0
{ testgroup<K>|disc<K> }:testgroup
{ groupid<U><0,255> }:0
4)
Test the circuit and loop line of the ASL board through the NMS.
2.4.10 The Line Test Fails Because an Incorrect NMS IP Address Is Set on the
MD5500.
I. Symptom
A UA5000 is attached to the MD5500. The NMS server is connected to an external
network port on the ASX board of the MD5500 to manage the MD5500 and
UA5000.However; the NMS always fail to test the line of the UA5000 due to time-out.
II. Cause analysis

1)
The test group is set improperly on the MD5500.
2)
The TSS board on the UA5000 is faulty.
3)
The NMS server is set incorrectly.
III. Solution
1)
2)
Check whether the MD5500 is configured with a correct test group.

If the test group is configured correctly, test the line of the MD5500 through the
command line.
3)
If the test result is normal, it indicates that the MD5500 is configured correctly and
the TSS board is normal.
4)
Send a line test command from the NMS server, and check whether the network
card sends any traffic.
5)
If the network card sends traffic, it indicates that the command is sent.
2-13
6)
Check whether the TSS board generates sound to indicate the on/off status of the
relay.
7)
If the TSS board generates such sound, it means that the line test is underway,
and that the test command is sent and is executed by the TSS board successfully.
In this case, it is possible that the MD5500 have not reported the test result.
8)
View the data configuration on the NMS server to check whether the NMS IP
address configured for the MD5500 is the IP address of the IPoA gateway.
9)
If the NMS IP address is the IP address of the IPoA gateway, change it to the IP
address of the external network port on the ASX board.
10) Conduct the line test.
Note:
z
The MD5500 sends data, (for example, fault data) to the NMS server through the external network port
on the ASX board.
If the NMS manages the MD5500 through the IPoA gateway, the MD5500 and the panels of the slave
frames can be viewed, and some simple maintenance operations can be performed. But in this case,
the NMS server cannot receive line test data and fault data, which requires the use of an external
network port.
2-14
Chapter 3 Maintenance Tools

This chapter introduces how to use the database password tool and the database
backup tool.
3.1 Database Password Tool

The iManager N2000 provides a password management tool that is based on
command line (DbPwdTool). Using this tool, the administrator can change the
password of the N2000user of the NMS database.
Assuming that the iManager N2000 is installed in $n2000, the password tool is
available in $n2000/server/bin.
3.1.1 Changing Password of N2000user in Windows

1)
In $n2000/server/bin, double click the executable file DbPwdTool.
A command line window appears:

iManager N2000 Database Password Tool
Please input the password of super user "sa" of the database server.
Press ESC then Enter to exit without doing anything:
2)
If the password of sa is not available, press <Enter> directly. If the password is

available, enter it, and then press <Click>. To exit without doing anything, press
<Esc>, and then press <Enter>.
Please input the new password of the iManager N2000 system database user:
3)
Enter the new password of N2000user, and then press <Enter>.
Reinput the new password:
4)
Reenter the new password of N2000user, and then press <Enter>.
Done. Please check the above information. Be sure there is no any error before
restarting your NMS.
3.1.2 Changing Password of N2000user in Solaris

1)
Start the Solaris, and then run the following commands:
# cd /opt/n2000/server/bin
# ksh
# . /n2kuser/.profile
# ./DbPwdTool
iManager N2000 Database Password Tool
Please input the password of super user "sa" of the database server.
3-1
2)
If the password of sa is not available, press <Enter> directly. If the password is

available, enter it, and then press <Click>. To exit without doing anything, press
<Esc>, and then press <Enter>.
Please input the new password of the iManager N2000 system database user:
3)
Enter the new password of N2000user, and then press <Enter>.
Reinput the new password:
4)
Reenter the new password of N2000user, and then press <Enter>.
Done. Please check the above information. Be sure there is no any error before
restarting your NMS
Note:
z
If you change the password of N2000user in the database but does not change the encrypted
password of N2000user stored in the configuration file the same time, the NMS daemon will fail to
start.
Using the database password tool, you can change the password of "N2000user" in both the database
and the configuration file of the NMS daemon at the same time.
3.2 Database Backup Tool

The database backup tool can be used for manual and automatic backup and recovery
of the NMS database. It can also be used for remote maintenance of the NMS
database.
The NMS database needs to be backed up at regular intervals so that it can be
recovered when necessary.
Database backup/recovery usually involves the following steps:
I. Preparations
Configure the NMS database to be backed up or recovered and the related database
set, backup policy, and backup device.
II. Back up a database

Determine the backup method and back up the NMS database.
III. Recover a database

Determine the recovery method and recover the NMS database.
3-2
Caution:
The database backup tool is an independent component. To use this tool, select and install it when you
install the NMS.
3.2.1 Preparations
Before backing up or recovering the NMS database, make the following preparations:
I. Start the database backup tool

Start the database backup tool through the graphical user interface (GUI) or the
command line.
To start the tool through the GUI, do one of the following:
z
In Solaris, right click on the CDE desktop, and then select [iManager N2000/
N2000 Database Backup Tool].
In Windows, select [Start/Programs/iManager N2000/DBBackup Client] or click

the DBBackup Client icon on the desktop.
To start the tool from the command line, do one of the following:
z
Assuming
that
the
iManager
N2000
is
installed
in
$n2000,
run
$n2000\server\bin\EmfDBBackup.exe to start the tool.

z
In Solaris, start the database backup manually. We recommend that you start it
from the background by appending &" to the command. If so, the related output
information is not displayed on the interface.
II. Configure the database server

Before backing up or recovering the NMS database, start the database backup tool,
and then configure the database.
To add an NMS database, do as follows:
1)
Select [System/Add Database Server].
2)
In the Add Database Server area, set the following parameters:
Server Name: Unique ID of the NMS server. It can be up to 30 characters.
IP Address: IP address of the NMS server. It must be in dotted decimal notation.

By default, it is 127.0.0.1.
Description: Information about the NMS server.
3)
Click <Add>.
4)
When a dialog box prompts the success, click <OK>.
The server node appears in the navigation tree on the left, as shown in Figure 3-1.
3-3
Figure 3-1 Database backup tool

To delete the NMS server, do as follows:
1)
In the navigation tree on the left, select the server node to be deleted.
2)
Select [System/Delete Database Server].
3)
When a dialog box prompts the success, click <Yes>.
The selected server node disappears from the navigation tree.
Caution:
z
The server name must be unique.
If the added NMS database server does not exist, you cannot log in from the database backup tool.
III. Log in to the database server

In the User Login window, enter the Access Password to log in to the database
server to be configured.
The Access Password must be identical to the password of the iManager N2000.
3-4
IV. Configure a database set

You can put the NMS databases in different sets to share them among all the backup
and recovery tasks. You can also put one database in multiple database sets.
z
To add a database set, do as follows:
1)
Select [Configuration/Database Set].
2)
Click <Add>.
3)
In the dialog box that appears, set the name of the database set; for example,
DB.
4)
Use
and
to specify the databases to be included in the set, as
Figure 3-2 Configuring a database set

5)
Click <Finish>.
6)
The added database set appears in the All Database Sets area.
z
To delete a database set, do as follows:
1)
In the All Database Sets area, select the database set to be deleted.
2)
Click <Delete>.
A dialog box shows details about the database set, including name of the set and the
included databases.
3)
Click <Finish>.
3-5
The selected database set disappears from the All Database Sets area.
Note:
The name of a database set must be unique. It must not begin with the underscore _.
V. Configure an automatic backup policy

Configure the period and start time for the automatic backup task.
To add an automatic backup policy, do as follows:
1)
Do one of the following to display the configuration window:
Select [Configuration/Auto Backup Policy].
In the navigation tree, select the Auto Backup Policy node under a database.
2)
Click <Add>.
3)
In the Add Time Policy area, as shown in Figure 3-3, set the following
parameters:
Time Policy Name: Name of the automatic backup policy.
Backup Frequency: The options include Daily, Weekly, and Monthly.
If you select Weekly, specify the day of each week for starting the backup task,
ranging from Monday to Sunday. If you select Monthly, specify the day of each month
for starting the backup task, ranging from 1 to 31.
z
Start Time: Time for starting the backup task. The range is 023 hours.
3-6
Figure 3-3 Adding an automatic backup policy

4)
Click <Finish>.
5)
The automatic backup policy appears in the Add Time Policy area.
Caution:
If Day 31 is specified, the backup task shall not start in a month that has only 30 days.
To modify an automatic backup policy, do as follows:

1)
In the Add Time Policy area, select an automatic backup policy, and then click
<Modify>.
2)
In the Modify Time Policy area, set the backup frequency (daily, weekly, or
monthly) and the backup time.
3)
Click <Finish>.
A dialog box prompts the success, and the system updates information about the
automatic backup policy.
To delete an automatic backup policy, do as follows:
1)
In the Add Time Policy area, select an automatic backup policy.
2)
Click <Delete>.
3-7
Details about the automatic backup policy are displayed.

3)
Click <Finish>.
A dialog box prompts the success, and the selected automatic backup policy
disappears from the Add Time Policy area.
Caution:
The name of an automatic backup policy is unique and case sensitive. It must not begin with the
underscore _.
VI. Configure a backup device

Configure the type of the backup device and the backup path.
To configure a backup device, do as follows:
1)
Select [Configuration/Backup Device].
In the navigation tree on the left, select Backup Device node under a database.
2)
To change the backup device, select the desired device type: disk or tape.
3)
Do one of the following:
If you select disk, the system displays these parameters: Backup Device Name,
Backup device type, User Backup to, and Current Backup to. Click <Modify>
to change User Backup to.
If you select tape, the system displays these parameters: Backup Device Name,
Backup device type, and Backup to. Click <Modify> to change Backup to.
4)
After modifying the parameters, click <Modify>.
5)
Information about the backup device appears in the Description area.
Note:
z
In general, User Backup to" and Current Backup to are set to the same directory.
When the directory of User Backup to is not available, the system switches to current directory of
Current Backup to, for example, the backup subdirectory under the installation directory of the
iManager N2000.
If the directory of User Backup to becomes available when the system backs up data to the directory
of Current Backup to, the system switches to the directory of User Backup to.
3-8
If you select a tape for database backup, before backing up the Sybase or SQL Server
database, initialize the tape in this way:
1)
In the Backup Device area, select the tape.
2)
Click <Initialize tape>.
VII. View a log

View the operation records of the database backup tool of an NMS database server.
If multiple database backup tools are used to back up the same NMS database, the
logs obtained by using all the tools are the same.
To view the log, do as follows:
1)
Select [View/Log].
In the navigation tree on the left, select the Log node under an NMS database.
2)
In the View Log area, set these parameters:
Log Type: Type of the records to be displayed. The options include All, Backup,
and Restore.
Time: Period of the records to be displayed. The options include Latest Month,
Latest Three Months, Latest Half Year, and Latest One Year.
3)
Click <Next>.
All the matching logs appear in the Operation Log area, as shown in Figure 3-4.
Figure 3-4 Viewing logs
3-9
VIII. View a database

View basic information about an NMS database, including space, occupied space, and
creation date, and so on.
To view a database, do as follows:
1)
Select [View/Database].
In the navigation tree on the left, select the Database node.
2)
In the All Database area, select the database.
Details about the database appears in the Description area, including database name,
space, occupied space, and creation date
3.2.2 Backing Up a Database

I. Manual backup
Back up a database manually.
To back up a database manually, do as follows:
1)
Select [Operation/Manual Backup].
In the navigation tree on the left, select the Manual Backup node under a
database.
2)
In the Select database set to backup area, select a database set, and then click
<Next>.
3)
In the Selection backup device area, select the target device, and then click
<Finish>.
4)
Wait until the backup is completed.
II. Automatic backup

Configure an automatic backup task.
To add an automatic backup task, do as follows:
1)
Start the database backup tool.
2)
Log in to the desired server.
3)
Select [Operation/Auto Backup Task].
In the navigation tree on the left, select Auto Backup Task under a database.
4)
Click < Add >.
5)
In the Select database set area, select a database set, and then click <Next>.
6)
In the Select time policy area, select a backup policy, and then click <Next>.
7)
In the Selection backup device area, select a device.
8)
Click <Finish>.
9)
When a dialog box prompts the success, click <OK>
3-10
The added backup task appears in the All Time Policies area.
To delete an automatic backup task, do as follows:
1)
Follow Steps 13 for adding an automatic backup task.
2)
In the All Time Policies area, select an automatic backup task.
3)
Click <Delete>.
Details about the automatic backup task are displayed.

4)
Click <Finish>.
5)
The selected task disappears from the All Time Policies area.
Note:
z
You can configure an automatic backup task only after configuring a database set, an automatic
backup policy, and a backup device.
Before backing up a Sybase database, you need to start the backup database
N2000DBServer_back; otherwise, you cannot backup the database using the backup tool.
3.2.3 Recovering a Database

If a database is faulty, you can recover it with a database record to minimize the loss.
To recover a database, do as follows:
1)
Select [Operation/Restore Database].
2)
In the Select backup device area, select a device, and then click <Next>.
3)
In the Select database set to restore area, select a database set, and then click
<Next>.
4)
In the Select one backup area, select the desired backup record.
5)
Click < Finish >.
6)
Wait until the recovery is completed.
After a database is backed up, the system generates a backup folder named after the
backup time in the backup directory. For example, if the backup time is 2004-4-9
12:06:08, the backup folder is named 20040409120608. Therefore, you can locate
the directory of the database to be recovered based on the backup time.
3-11
Caution:
z
The name of a server, database set, and automatic backup policy must not contain any character in
this set: `~!@#$%^&*()\":;?/\\,.|{}[]<> '+=-.
Before recovering a database, make sure that neither NMS user nor other user connects with the
database; otherwise, the recovery fails.
Before recovering a database, stop all the processes through the SysMonitor except the Database
Backup Process.
3-12
Chapter 4 Remote Maintenance

This chapter introduces the remote maintenance means and methods of the iManager
N2000.
4.1 Remote Maintenance Channel

The major NMS server platforms include SUN Solaris and Microsoft Windows 2000.
The dial-up client adopts PC/Windows 98/2000 platform.
The dial-up server adopts PC/Windows 98/2000 or SUN Solaris platform.
You need to determine the dial-up access function of the remote end and the local end.
Currently, the NMS workstation can only serve as the dial-up server; as shown in mode
(1). For Windows platform, the end with the dial-up access function serves as the
dial-up access server, as shown in modes (2) and (3). The client connects with the
dial-up access server.
----------------Remote end--------------------------------Local end------------------------(1) PC/Windows98/2000 ---PSTN---> Workstation dial-up access server ---> Gateway
(2) PC/Windows98/2000 ---PSTN---> PC/Windows98/2000 --->Gateway
(3) PC/Windows98/2000 <--PSTN---- PC/Windows98/2000 ---> Gateway
----------------------------------------------------------------------------------------------------
4.2 Hardware Requirement and Connection

In the above modes, one Robotics Sportster 33.6K, Hayes, or Etek modem is required
at each end.
For the sites equipped with NMS PC or workstation, the modems are usually delivered.
The following introduces how to connect the NMS PC or workstation and the modems.
I. PC/PC workstation
For a PC or PC workstation, connect the serial cable attached to the modem to the
serial port of the PC or PC workstation, connect the phone line to the Line port on the
modem.
II. SUN workstation

Serial port A or B and the serial port of the modem are usually DB25 ports. A "DB
(Male)------DB25 (Male) cable is required to connect the modem to the SUN
workstation, so use the delivered serial cable.
4-1
Note:
Because the serial cable attached to the modem is usually Female--------Male, do not use it to connect
the modem to the SUN workstation.
Figure 4-1 shows the connection. Connect the phone line to the Line port on the
modem.
Ground (GND)
Transmit Data (TD)
Request To Send (RTS)
Clear To Send (CTS)
Date Set Ready (DSR)
Signal Ground (SG)
20
Receive Data (RD)
Data Carrier Detect (DCD)
Data Terminal Ready (DTR)
20
Figure 4-1 Connection between the SUN workstation and modem
4.3 Software Configuration
Note:
Connect the modem and install its driver before you set the network connection parameters.
4.3.1 PC/Windows 2000 Serving as a Dial-up Server

I. Software
The system itself provides this function, so no additional software is needed.
II. Configuration procedure

To configure the Windows 2000 Server dialup server, do as follows:
1)
Select [Start/Settings/Network and Dial-up Connections/Make New Connection].
2)
In the Network Connection Wizard dialog box that appears, click <Next>.
4-2
The Network Connection Type dialog box appears, as shown in Figure 4-2.
Figure 4-2 Network connection type

3)
Click Accept incoming connections, and then click <Next>.
The Devices for Incoming Connections dialog box appears, as shown in Figure 4-3.
Figure 4-3 Dial-up access device

4)
Select Standard Modem, and then click <Next>.
4-3
The Incoming virtual private connection dialog box appears, as shown in Figure 4-4.
Figure 4-4 Incoming virtual private connection

5)
Click Not Allowed Virtual Private Connection, and then click <Next>.
The Allowed Users dialog box appears, as shown in Figure 4-5.
Figure 4-5 Allowed users

6)
Click <Add>.
The New User dialog box appears, as shown in Figure 4-6.

4-4
Figure 4-6 Adding a new user

7)
Click <Next>.
The Networking Components dialog box appears, as shown in Figure 4-7.
Figure 4-7 Network components

8)
Select all the listed network components, and then click <Next>.
The Completing the Network Connection Wizard dialog box appears, as shown in
Figure 4-8.
4-5
Figure 4-8 Finish

9)
Enter a name for the network connection, and then click <Finish>.
4.3.2 PC/Windows 2000 Serving as a PSTN Client

I. Software
The system itself provides the function, so no additional software is needed.

The following example shows how to configure the Windows 2000 PSTN client. For a
Windows 98 PSTN client, the procedure is similar.
1)
Select [Start/Settings/Network and Dial-up Connections/Make New Connection].
2)
In the Network Connection Wizard dialog box that appears, click <Next>.
The Network Connection Type dialog box appears, as shown in Figure 4-9.
4-6
Figure 4-9 Network connection type

3)
Click Dial-up to private network, and then click <Next>.
The Phone Number to Dial dialog box appears, as shown in Figure 4-10.
Figure 4-10 Phone number to dial

Assuming that a toll call is configured here.
4)
Select the Use dialing rules check box.
5)
Enter the desired area code.
4-7
6)
Enter the phone number to dial.
7)
Select the desired country/region code.
8)
Click <Next>.
Note:
If you want to configure a local call, it is not necessary to select Use dialing rules. Only the Phone
number is needed.
The Connection Availability dialog box appears, as shown in Figure 4-11.

9)
Click For all users or Only for myself (recommended), and then click <Next>.
Figure 4-11 Connection availability

10) In the Completing the Network Connection Wizard dialog box that appears, enter
Remote Maintenance Client in the Type the name you want to use for this
connection box.
11) Select Add a shortcut to my desktop, and then click <Finish>.
If you want to establish a dial-up connection, do as follows:
1)
Double click the Remote Maintenance Client icon on the desktop.
2)
In the dialog box as shown in Figure 4-12, enter the user name and password of a
valid user of the dial-up server and the phone number of the dial-up server (NMS
server.
3)
Click <Dial>.
4-8
Figure 4-12 Dial-up access window
4.3.3 SUN Workstation Serving as a PSTN Dial-up Server

I. Configuration requirement
z
When a SUN workstation serves as the PPP server, there are two kinds of virtual
network interfaces: ipdptpn and ipdn (where n indicates the device number. Serial
port A corresponds to 0 and serial port B to 1). For ipdptpn interface, one modem
can only connect to one PPP client. For ipdn interface, one modem can connect to
multiple PPP clients.
Currently, the iManager N2000 supports PPP client that is based on static IP
address. If a PC serves as the PPP client, set "PPP" as the server type when
setting the connection attributes, and select the specified IP address when setting
TCP/IP attributes. Do not change other settings.
The dial-up script must be compiled according to the type of modem. It is hard to
do so when you configure dial-up service on the workstation. Three types of
modems are recommended: Robotics, Hayes, and Etek. The configuration of
Hayes modem is introduced here.
Unix to Unix Copy Protocol (UUCP) software and PPP software need to be
preinstalled on the workstation (they are already installed on the current
workstations). If necessary, use this command to install the PPP software:
# pkginfo | grep ppp

1)
Check the connection of modem.
4-9
Connect the modem to the serial port, and then use this command to check whether the
modem is properly connected (assume that the modem is connected to serial port A):
# tip /dev/cua/a
connected
If connected is displayed, it indicates that the modem is connected to serial port A. In

this case, if the modem can be configured by using AT commands, it indicates that the
modem is connected properly. Otherwise, check whether the serial port cable and the
modem are normal. Type ~ to quit the command tip.
2)
Configure the PPP.
Default settings of configuration script:

z
The IP addresses of the PPP server and PPP client are set to 192.168.55.1 and
192.168.55.2 respectively.
The PPP server adopts ipdptpn network interfaces.
The login user name of the PPP client is ppp_user.
These parameters can be changed if necessary.

Set the server:
z
On the PC, load the file ppp.tar to the directory /usr/local/rms/ as the user root.
Note that this file is transmitted in binary system.
Log in to the workstation as a superuser, and then decompress the file ppp.tar.
# cd /usr/local/rms
# tar xvf ppp.tar
z
Connect the modem to the workstation and phone line, and then power on the
modem. On the workstation, enter the PPP directory, and then configure the PPP
server as below:
# cd PPP
# sh setup_ppp.sh (or use ./setup_ppp.sh).
z
Specify the computer as the remote monitor server (options are client and server.
By default it serves as the client): server
Input the serial port used (a or b. It is a by default): b
Rate of serial communication (19200bps, 9600bps, or 38400bps. It is 19200bps

by default (recommended).
Input the type of the used modem: Hayes, Robotics, or Etek. It is case-sensitive. It
is Hayes by default.
The PPP user is ppp_user by default.
Input the password of "ppp-user":
New password: (input the password of the PPP user.)
Re-enter new password: (Input the password of the PPP user again)
4-10
Caution:
If you have forgotten the password of "ppp_user", log in as a superuser and then change the password
using the command passwd ppp_user.
Input these two commands to control the Hayes modem (we recommend that you copy
and paste them).
AT&FN0Q2X0&C1&D2S0=1&W&y<CR>: Set parameters of modem
~.<CR>: End the session with modem
Caution:
Input the above two commands at the beginning of the line. <CR> stands for Carriage Return.
If a Robotics modem is used, we recommend that the AT command used to

communicate with the modem be changed to:
AT&F1&B1&C1&D2X0S0=1&W
If an Etek modem is used, change the AT commands used to communicate with the
modem to:
ATX0&C1&D2S0=1&W
connected
AT&FN0Q2X0&C1&D2S0=1&W&y
OK
~.
[EOT]
#
Note:
z
Both serial ports a and b are ok. You are recommended to select 19200bps as the serial port baudrate.
The modem type is case sensitive.
You are recommended to input the AT commands for communicating modem with Copy and Paste.
To end the session with the modem, type ~ at the beginning of the line.
3)
Establish and end connections.
Check if the process asppp is started:

4-11
# ps -ef | grep asppp

Start asppp
# /etc/init.d/asppp start
Stop asppp
# /etc/init.d/asppp stop
After "asppp is started on both the server and the client, ping the server to
establish the dial-up connection.

# ping ppp_server [N]
Note:
z
The dial-up may take some time. If you ping the server for the first time, a time-out might occur. "N" is
used to set the time-out period of the command ping.
You can check the connection state by viewing the log files (see "4.5 Troubleshooting" or the LEDs on
the modem.
III. Change default settings

1)
Change the default phone number of the client.
Modify the last row of the file /etc/uucp/Systems:

UNIX Any PPP 19200 0,163 ...
Where 0,163 indicates the phone number of the PPP server. Modify it directly.
2)
Change the IP address.
The server and the client must be synchronized.

z
Modify the IP address of the server.
Log in to the server a superuser, and then edit the file /etc/hosts:
...
192.168.55.1
ppp_server
192.168.55.2
ppp_client
...
Change the corresponding IP addresses of ppp_server and ppp_client.

z
If the client is a workstation, change the IP address in the above way. If the client is
a PC, enter the IP address of the ppp.chient in the file /etc/hosts at the server.
The IP addresses of the PPP server and all PPP clients must be within the same
subnet.
3)
Rename the server and client.
The name is only valid at the local end.

4-12
z
Modify the server:
Step 1: Log in as a superuser, and then modify the file /etc/hosts:

...
192.168.55.1
ppp_server
192.168.55.2
ppp_client
...
Modify ppp_server and ppp_client

Step 2: Change the file /etc/asppp.cf:
...
ifconfig ipdptp0 plumb ppp_server ppp_client up
...
Modify ppp_server and ppp_client
Note:
If the virtual network interface is ipdn, the format of the file asppp.c is different from the one listed above.
Simply modify ppp_server and ppp_client.
Modify the client (workstation):
Step 1: The same as Step 1 in modifying the server.

Step 2: The same as Step 2 in modifying the server. The virtual network interface of the
client can only be ipdptpn. Do not change the format of asppp.cf.
4)
Change the type of the virtual network interface of the server to ipdn
Log in as a superuser, and then modify the file /etc/asppp.cf:

ifconfig ipdptp0 plumb ppp_server ppp_client up
path
...
interface ipdptp0
...
Change the above information to:

ifconfig ipd0 plumb ppp_server up
path
...
interface ipd0
peer_ip_address
ppp_client
...
5)
Connect the server with multiple clients
Change the interface type to ipdn.

4-13
z
Log in as a superuser, and then add the IP addresses of the clients to the file
/etc/hosts.
...
192.168.55.1
ppp_server
192.168.55.2
ppp_client
192.168.55.3
ppp_client2
192.168.55.4
ppp_client3
...
z
Log in as a superuser, and then add the description of the paths to the file
/etc/asppp.cf,
#Connection parameter setting of ppp_client(192.168.55.2)

path
...
peer_ip_address
ppp_client
...
#Connection parameter setting of ppp_client1(192.168.55.3)
path
...
peer_ip_address
ppp_client1
...
For all the paths, the peer_ip_address is different but other parameters are identical.
IV. Configure the PPP server as a router

1)
Add ppp network number.
Log in as a superuser, and then add the ppp network number to the file /etc/networks ,
...
pppnet
2)
192.168.55
ppp
#ppp network
Set subnet mask.
Log in as a superuser, and then modify the file /etc/netmasks.

...
192.168.55.0
3)
255.255.255.0
Add PPP host name.
If the virtual network interface is ipdn, create the file /etc/hostname.ipdn. If it is ipdptpn,
create the file /etc/hostname.ipdptpn .
Enter the PPP host name, and then log in as a superuser.
# vi /etc/hostname.ipdn
ppp_server
Save the file, and then restart the workstation.
4)
Start the routing process.
4-14
Check whether the routing process (in.routed, in.rdisc) of the access server has been
started.
# ps -ef | grep in.routed
# ps -ef | grep in.rdisc
If not, run these commands:
# /usr/sbin/ndd -set /dev/ip ip_forwarding 1
# /usr/sbin/in.routed -s
# /usr/sbin/in.rdisc -r
5)
Set default route at the client.
Set a default route at the PPP client, with the gateway being ppp_server.
# route add default ppp_server
6)
Set default route at the host.
At the LAN host side, set a route to the PPP network, with the gateway being the
Ethernet IP address of the PPP server.
# route add 192.168.55.0 xxx.xxx.xxx.xxx
4.4 Remote Maintenance Solutions

The remote maintenance mode varies with the operating system and remote
maintenance tool. The following details the remote maintenance modes of the
iManager N2000.
I. Sun workstation serving as the dial-up server

This mode is used in situations where the server of the operator is a SUN workstation.
It features high connection rate and high security.
First set up the corresponding dial-up connection, and then follow these steps to
perform the maintenance.
1)
Both parties establish connections in between. The remote maintenance client

needs to get information such as the phone number of the opposite end, dial-up
user name and password. Then dial in the iManager N2000 NMS Workstation of
the operator.
2)
The remote end runs the iManager N2000 Client, inputs 192.168.55.1: 9801 in
the server input box, and then the user name and password provided by the
operator, and clicks <Login>.
4-15
Caution:
z
Both parties establish communication connections in between. The remote maintenance client must
get information such as the phone number of the opposite end, dial-up user name and password. Then
dial in iManager N2000 NMS Workstation of the operator.
For the sake of security, set one TELNET connection for the SUN workstation and disable the FTP
function.
II. PC/Windows2000 serving as the dial-up server

This mode is used in situations where the server of the operator is a PC. It features high
connection rate and high security.
First set up the corresponding dial-up connection (see 4.2 Hardware Requirement
and Connection), and then follow these steps to perform the maintenance.
1)
Both parties establish communication connections in between. The remote

maintenance client must get information such as the phone number of the
opposite end, dial-up user name and password. Then dial in the network
management PC of the operator.
2)
The remote end runs the iManager N2000 Client, inputs 192.168.55.1: 9801 in
the server input box, and then the user name and password provided by the
operator, and clicks <Login>.
Note:
z
If the dial-up connection at the server side is disconnected, restart the SS module of the NMS Server.
For the sake of security, the number of the login users is limited.
4.5 Troubleshooting
I. Failed to connect to SUN workstation
1)
Check whether the connections are correct, especially the connection of the SUN
workstation. Check whether the modem is connected properly. The phone line
must be connected to the jacket marked line.
2)
Make sure that connection of the modem is normal. If a message similar to the
following appears during the setup, it means that the modem is improperly
connected:
tip: /dev/cua/b: No such device or address

all ports busy
4-16
In this case, check the condition of the lines and make sure that the modem is switched
on. Use tip termb (or terma, respectively indicates that the modem is connected to
serial port b or a) or tip -19200 /dev/cua/b (a) to connect the modem.
z
If the message connected appears, it indicates that the modem is connected. In

this case, you can input AT.
If "OK is returned, it indicates that the modem is normal. Input ~ to exit, and then
set setup_ppp.sh again.
If no OK is returned after you input AT, input ATE1Q0.
If still no response is returned, replace the port or re-connect the modem.
For more information about debugging modem, see the document Modem_conf.pl.
You can open this file with an HTML browser.
Caution:
To use terma or termb, the setup_ppp.sh must be set correspondingly. terma or termb is an entry to file
/etc/remote.
3)
Make sure that the password of ppp_user input at the client side is identical to the
one set at the server side. Run vi to view the file /etc/uucp/Systems. The
password of ppp_user is located at the last row (login: ppp_user word:) of the file.
It must be identical to the one set at the server side. To change the password of
ppp_user without setting PPP again, log in as a superuser, and use
/usr/bin/passwd ppp_user to change the password of ppp_user.
4)
The file /var/adm/log/asppp.log (the same as etc/log/asppp.log) records the

operations performed by the PPP user. You can view the dial-up connection
progress in tail -f /var/adm/log/asppp.log.
5)
If no change occurs in tail -f /var/adm/log/asppp.log when the client dials, it

means that the PPP user has not logged in or the login shell is not
/usr/sbin/aspppls. Modify the file /etc/passwd directly, or change the login shell
of the PPP user to /usr/sbin/aspppls in admintool.
6)
If the following message is displayed in /var/adm/log/asppp.log:
10:13:22 get_fifo_msg: can't find path with peer_system_name ppp_user
It means that the PPP user name set at the client side might be inconsistent with the
one set in peer_system_name in /etc/asppp.cf at the server side. If so, make them
consistent.
II. No display in the SUN workstation login window

The cause is possibly related to cables. Check the specifications of the cables and
make sure they are complied.
4-17
III. Frequent problems with the PC workstation serving as the dial-up client
1)
Illegible characters appear in the PC client login window. The likely reason is that
the baudrate of the PC client is not set to 19200.
2)
Make sure that the dial-up server is correctly installed and is bound with TCP/IP.
Problems may occur if multiple dial-up servers are installed.
IV. Verifying installation of PPP software

UUCP software and PPP software must be preinstalled on the workstation (currently,
they are already installed on the workstation). Run this command to check whether the
PPP software has been installed:
# pkginfo | grep ppp
V. No response from the modem

Set the modem to auto answer mode. For Robotics, Hayes and Etek modems, run the
scripts again and select a correct modem type (case-sensitive). For another modem
type, set the corresponding AT commands by referring to the configuration manual.
4-18
Chapter 5 FAQ
Chapter 5 FAQ
This chapter presents answers to the frequently asked questions about the
maintenance of the iManager N2000.
5.1 Operating System

5.1.1 How to Start Sun Workstation from CD-ROM (Sun/Solaris)?
1)
Power on the workstation.
2)
When the startup screen appears, enter <Stop+A>.
The prompt "OK" appears.

3)
Put the Solaris installation CD-ROM into the CD-ROM drive, and then run boot
cdrom.
The workstation then starts from the CD-ROM.
5.1.2 How to Set IP Address of Sun Workstation (Sun/Solaris)?

Two methods are available:
z
Method 1: Enter the IP address of the Sun workstation correctly in the "Configure
Network" option while installing the operating system.
Method 2: Set the IP address by modifying the corresponding file.
1)
Open the "/etc/hosts" file and change the IP address.
2)
Open the "/etc/netmasks" file and change the network mask. If the corresponding
item is unavailable, add "host IP network mask", for example, "10.110.1.1
255.255.0.0".
3)
Restart the workstation.
5.1.3 How to Change Host Name of Sun Workstation (Sun/Solaris)?

To change the host name of the Sun workstation, change the following three files:
z
/etc/hostname.hme0
/etc/hosts
/etc/nodename
1)
Change the host name of the three files to the desired one.
2)
Restart the workstation to validate your change.
5.1.4 How to Configure Maximum Terminals for Sun Workstation

(Sun/Solaris)?
1)
Add the following to the "/etc/system" file:

5-1
Chapter 5 FAQ
set npty=100
set pt_
cnt=100
2)
Restart the NMS workstation to validate your settings.
5.1.5 How to Extract a File with a .tar.gz Extension?

This example shows how to extract the abc.tar.gz file:
#gunzip abc.tar.gz
#tar xvf abc.tar
5.1.6 How to View the Version and Release Date of Solaris?

Use uname a to view the Solaris version.
Use more /etc/release to view the release date of Solaris.
5.1.7 How to Switch from a Common User to a Superuser?

After logging in to Solaris as a common user, you can run su to switch to a superuser.
$su
password: (Enter the password of the superuser)
#
If the # prompt appears, it indicates that the operation succeeds.

To switch back to a common user, run exit.
5.1.8 How to Add or Delete a Static Route?

At the terminal console, use netstat r to view the static route information of the
system.
z
To add a static route, run this command:
route add network address -netmask subnet mask gateway
This example adds a route to the network segment 192.168.0.0, with the gateway IP
address being 10.11.201.254.
#route add 192.168.0.0 -netmask 255.255.255.0 10.11.201.254
After you restart the operating system, the route added in this way does not exist.
Therefore, add the corresponding route configuration command to the start script; for
example, add it to the end of the /etc/rc3 file.
z
To delete a route, run this command:
route delete network address -netmask network mask gateway address
For example:
#route delete 192.168.0.0 -netmask 255.255.255.0 gateway
5-2
Chapter 5 FAQ
5.1.9 How to Add or Delete a Default Route?

At the terminal console, use netstat r to view the static route information of the
system.
z
To add a default route, run this command:
#route add default IP address of next hop
To avoid loss of the route, add the route configuration command to the end of the
/etc/rc3 file. After that, the default route takes effect after you restart the workstation.
z
To delete a default route, run this command:
#route delete default IP address of next hop
5.1.10 Sun Workstation Aborts (Sun/Solaris)

When the UNIX system aborts, the file system might be damaged. If so, when you
restart the workstation, the graphical boot interface will not be displayed.
In this case, run fsck to check the file system, and then restart the workstation.
1)
Enter the password of the superuser, and then run this command:
#fsck -y
The system begins to correct the errors in the file system.

2)
Run reboot to restart the workstation.
Note that fsck can only be used to correct ordinary errors. It cannot recover the errored
start parameters or damaged kernel of the operating system caused by power failure.
5.1.11 File Size Changed When FTP Is Used to Send Files

When FTP is used to send files with binary contents (for example, NMS Setup and
database interface files), the files must be sent in binary format. When you start the
FTP program, the default transmission mode is ASCII. In this case, before sending the
files, use bin to change the transmission mode to binary format.
5.1.12 Execution Authority of Files Is Lost When FTP Is Used to Send Files
If the execution authority of Setup is lost when the Setup is copied to a hard disk
through FTP program, change the authority of the file. Taking the installation script of
the NMS as an example, run this command:
# chmod +x setup.sh
To add the execution authority of all the files in the subdirectory, run this command:
chmod -R +x subdirectory name
5-3
Chapter 5 FAQ
5.2 Database
5.2.1 How to Change the Password of "sa" (Sun/Solaris/Sybase)?
"sa" is the user name of the Sybase system administrator. After the Sybase database is
installed, the password of "sa" is null by default.
The following example shows how to set the password to "abc123".
$ isql -Usa P
1> sp_password null, abc123
2> go
The password is set correctly.
(return status=0)
1> quit
The password of "sa" cannot be changed back to null after setting, so remember the
new password.
5.2.2 How to Set a Password for sa(Windows/SQL Server 2000)?

If you have not set a password for sa during the installation of SQL Server 2000, you
can set it after installation.
z
Method 1:
1)
Select [Start/Programs/Microsoft SQL Server/Enterprise Manager].
The "SQL Server Enterprise Manager" window appears.

2)
Unfold the directory tree on the left and locate the security node.
3)
Click "Login" and double click "sa" on the right.
4)
In the "SQL Server Login Properties" dialog box that appears, set the password.
Method 2:
Modify the password through "isql". It is the same as the operations for Sybase. See
5.2.1 How to Change the Password of "sa" (Sun/Solaris/Sybase)?.
5.2.3 How to Quit Sybase 12.0 and Log in as root?

1)
Log in to the database through isql, run shutdown SYB_BACKUP to shut down
the backup server, and run shutdown to shut down the master server.
2)
Run su to switch to "root", and then run these environment variables:
#cd /opt/sybase
#. ./SYBASE.sh
#cd /opt/sybase/OCS-12_0
#. ./OCS-12_0.sh
#cd /opt/sybase/ASE-12_0
#. ./ASE-12_0.sh
5-4
Chapter 5 FAQ
5.2.4 How to Check the NMS Database in Case of Power Failure?

In case of power failure of the NMS workstation, the NMS database cannot start
normally due to corrupted data when you restart the workstation.
In this case, do as follows:
1)
Check whether the database server has started normally.
When you restart the NMS workstation, the database server usually starts
automatically.
Run this command:
#ps -ef|grep dataserver
If /opt/sybase/bin/dataserver is displayed, it indicates that the database server has

started. If only grep dataserver is displayed, it indicates that the database sever has
not started.
If the database server has started, go to Step 3.
2)
Start the database server manaully.
Run these commands:

#cd $SYBASE/install
#ls
#./startserver -f ./RUN_XXX
(After you run ls, the files in the current
directory are usually displayed. Locate the two files beginning with RUN_,
and enter the one without the suffix back.)
3)
Check whether the database is faulty.
If the database server has started, view the database server name.log file to check
whether the database file is faulty:
#cd $SYBASE/install
#tail -100 database server name.log (This command displays the last 100 start
records. You can change the number of the records to be displayed.)
Check whether the word error and error number are displayed.
For example, if the frequent Error 926 occurs, the following information is displayed:
Error: 926, Severity: 14, State: 1
00:00000:00001:2002/05/31 09:26:26.65 server Database 'FaultDB' cannot be
opened.
It indicates that the FaultDB is faulty.

4)
Check whether the NMS database is normal using isql.
If the above error does not occur, check whether the NMS database is normal:
#cd $SYBASE/bin
#./isql -Usa P(password of sa)
5-5
Chapter 5 FAQ
Usually, the 1> prompt is displayed. If it is not displayed, check whether the database
server has started (see Step 1) and whether the password of sa is correct.
Then run these commands:
1>sp_helpdb
2>go
Check whether the database status is offline.

If no error message is displayed, it indicates that the NMS database is normal, and you
can start the NMS.
5)
Eliminate fault
If an error message is displayed, recover the database according to the error number.
This example shows how to recover the FaultDB in case of Error 926:
Log in as sa using isql:
1>sp_configure "allow updates", 1
2>go
1>update sysdatabases set status =-32768, where name="FaultDB"
2>go
1>shutdown with nowait
2>go
Restart the SQL Server, and then register with it as sa.

1>update sysdatabases set status=0 where name="FaultDB"
2>go
1>sp_configure "allow updates", 0
2>go
1>shutdown with nowait
2>go
Restart the SQL Server, and then register with it again as sa.
5.2.5 Unable to Start Sybase (Sun/Solaris/Sybase)

Check the shared memory in the "/etc/system" file for the following contents (usually at
the end of this file):
set shmsys:shminfo_shmmax = 131072000
Where, "131072000" is calculated with the following formula based on a memory of
128MB.
Y=X*1024*1000 (where X is the physical memory, measured in MB).
If the set shared memory is lower than the value that is calculated, the Sybase will not
start.
In this case, calculate the shared memory on the basis of the physical memory, set it
again, and then restart the operating system.
5-6
Chapter 5 FAQ
5.2.6 How to View Sybase Information?

1)
View information about all the databases:
$cd /opt/sybase/bin
$./isql -Usa -Psa_password
1>sp_helpdb
2>go
Information about all the Sybase databases is displayed, including name, size, owner,
status, and so on.
2)
View details about a database:
1>sp_helpdb dcnmdb
2>go
The basic information and space occupancy of the database are displayed.
5.2.7 How to View the Data Table?

1)
View all the tables in the database:
$cd /opt/sybase/bin
$./isql -Usa -Psa_password
1>use db_name
2>go
1>sp_help
2>go
Information about all the data tables in the db_name database is displayed, including
name, owner, and type.
2)
View details about a data table:
1>sp_help table_name
2>go
The structure information of the data table is displayed.

This operation must be performed on the current database; otherwise the system
prompts that the data table is not found.
5.2.8 How to Check Database Error Using the DBCC Tool?

1)
View the error information of the database:
1>dbcc checkdb(dcnmconsdb)
2>go
All data table information and error information of the database are displayed.
2)
View the error information of a data table:
1>dbcc checktable(tbl_Event)
2>go
5-7
Chapter 5 FAQ
The error information of the data table is displayed.

3)
Reindex the data table:
1>dbcc reindex(tbl_Event)
2>go
The data table is reindexed.
5.3 NMS
5.3.1 A Device Can Be Pinged but the NMS Prompts That the Communication
of the Device Is Interrupted.
The device is configured with no or incorrect NMS parameters.
Configure the device with correct NMS parameters such as IP address of the NMS
server, and then activate them.
5.3.2 No Traffic Measurement Data Is Received After the Task Created on the
BAM Is Synchronized to the NMS.
No output port is specified when the task is created on the BAM.
When you create a task on the BAM using MML command line, an output port is not
mandatory. However, in order for the NMS to receive the traffic measurement packets,
an output port must be specified.
This problem does not occur when a task is created on the NMS, because the NMS port
is selected by default.
5.3.3 No Data Is Measured During Measurement of Global Traffic.

Global traffic measurement requires that traffic is obtained for the eight related
measuring units; otherwise the measurement fails.
The tasks include:
z
Originating traffic measurement
Internal traffic measurement
Originating outgoing traffic measurement
Incoming traffic measurement
Incoming terminating traffic measurement
Transit traffic measurement
Terminating traffic measurement
Outgoing traffic measurement
5.3.4 Unable to Reinstall the NMS

After the SQL Server is uninstalled, it is possible that the NMS database is not deleted
completely. In this case, if you try to install the same NMS database again in the original
5-8
Chapter 5 FAQ
installation directory, the operation will fail because NMS database files to be created
are already there.
Therefore, before uninstalling the SQL Server, back up the important database files,
and then delete all database files.
5.3.5 How to Prohibit the iManager N2000 from Running When Your
Computer Starts?
z
In Unix:
Delete the /etc/init.d/n2000sys file.

z
In Windows, do as follows:
1)
Open the registry.
2)
Locate this subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
3)
Delete N2000SysMonitor.
5.3.6 How to Set CPU and Memory Alarm Thresholds for the iManager N2000
Workstation?
Set the emfmoni.cfg file under the \server\conf" in the installation directory of the
NMS server:
CpuThreshold=80 cpu: It is 80% by default.
DiskThreshold=90: It is 90% by default.
5.3.7 IP Address of the NMS Server Is Changed.

After the IP address of the NMS server is changed, you need to modify the following
settings before the NMS can run:
I. Operating system
z
If only the IP address is changed, open the /etc/hosts file, replace the old IP
address with the new one, and then restart the NMS workstation.
If the network mask is also changed, in addition to the above change, you also
need to change the mask in the etc/netmasks file.
If the gateway is changed, you also need to change the routing information in
the /etc/defaultrouter or /etc/rc3 file.
II. Sybase
If Sybase is installed (assume that the name is SUNR6), you need to change the
interfaces file of the database:
1)
Shut down the database using isql.
2)
Run su to switch to the root user, and then run $SYBASE/bin/dsedit

5-9
3)
Chapter 5 FAQ
In the Select a directory Server dialog box that appears, select Sybase
interfaces file, and then click <OK>.
4)
In the Directory Server Session dialog box that appears, select SUNR6 (the
master database), and then click <Modify Server entry>.
5)
In the Server Entry Editor dialog box, select li tcp :SUNR6 4100 from the
Available network transport list, and then click <Modify Network Transport>.
6)
In the Network Transport Editor dialog box that appears, enter the new IP
address of the workstation in the Host name box, and then click <OK>.
7)
Follow the above steps to change the IP address of SUNR6_BACK (the backup
server).
III. NMS
In the /n2kuser/.profile file, change
QNMSERV = original IP address of the server
To: QNMSERV = new IP address of the server.
5.3.8 Basic Algorithms for Traffic Measurement

According to the measurement formulas of the measuring entity, the traffic
measurement comes in four forms:
z
If the formula aims to get a SUM, for each entity: result = SUM (all the
records)*(end timestart time)/SUM (period of all the records).
If the formula aims to get an AVG, for each entity, result = SUM (each record
value*period of the record) /SUM (period of all the records).
If the formula aims to get a MAX, for each entity: result = MAX (all the records).
If the formula aims to get a MIN, for each entity: result = MIN (all the records).
5-10
Appendix A SNMP
Appendix A SNMP
A.1 Introduction
I. Concept
Simple network management protocol (SNMP) is widely used to ensure transmission of
management information between any two points. It runs over user datagram protocol
(UDP).
II. Features
SNMP includes SNMP V1, V2, and V3. They are based on the UDP/TCP/IP.
The SNMP features the following:
z
It is flexible, scalable, and independent of the managed devices.
It adopts a polling mechanism and provides basic function sets.
It replaces complex command set with GET-SET mode. You can adopt the
standard management information base (MIB) or define your MIB.
III. Model
The SNMP resides at the application layer and runs over the UDP.
Figure A-1 shows the model of the SNMP.
SNMP
UDP
IP
Data link layer
Physical layer
Figure A-1 SNMP model
A.2 Architecture
The SNMP consists of NMS and agent, as shown in Figure A-2.
A-1
Appendix A SNMP
NMS
UDP Port 162
Request
Response
Trap
UDP Port 161
Agent
Figure A-2 Architecture of SNMP

In order for the SNMP to collect and configure device data remotely, three basic
elements must be available:
z
Managed device
A managed device is also known as a network element (NE). The SNMP agent runs on
an NE to collect and store management information. The NE can be a router, a switch,
a Hub, a printer, and so on.
z
Agent
An agent is a software process residing in the managed device. It receives and

processes the request packets from the NMS workstation; gets values of the
management variables and form them in response packets; get the values of
management variables, and forms them into response packets; sends the response
packets to the NMS. The agent also sends traps to the NMS to notify the latter of
emergencies such as change to interface status call success.
z
NMS
The NMS sends query packets to the network devices. It also receives and displays the
responses and traps from the managed devices.
A.3 Principles of SNMP

The SNMP agent receives a packet from the NMS workstation through UDP port 161. It
decodes the packet, authenticates the community names, and analyzes the
management variables to locate the corresponding MIB node. It then gets the values of
the management variables from the related module and forms and codes a response
packet. After that, it sends the response packet to the NMS workstation. Upon receiving
the response packet, the NMS workstation processes it similarly and displays the
result.
After receiving a packet, the SNMP agent follows this procedure:
A-2
1)
Appendix A SNMP
Decodes the packet based on ASN.1 to get an internal packet. If the decoding fails,
it discards the packet.
2)
Extracts the SNMP version from the packet. If it does not support the version, it
discards the packet.
3)
Extracts the community names from the packet. If the community names are not
identical to those set at the device, it discards the packet and generates a trap.
4)
Tries to extract a packet data unit (PDU) from the packet. If the operation fails, it
discards the packet. If the operation succeeds, it processes the PDU, generates a
packet, and sends the packet to the source address of the received packet.
The SNMP processes different PDUs in different ways.
A.4 Security Systems

The SNMP ensures the system security through SNMP V1, V2, and V3.
A.4.1 Security System in SNMPV1

SNMP V1 ensures system security through authentication and access control.
I. SNMP community
An SNMP community contains one SNMP agent and one group of SNMP managers.
The SNMP agent and SNMP managers are provided with authentication and access
control. One SNMP agent can be combined with multiple groups of SNMP managers to
form multiple SNMP communities.
Each SNMP community is identified by an octet, known as community name. The
community name is like a password. If an SNMP manager provides correct community
names, it has the access authority corresponding to the community. The process of
checking community names is known as authentication.
One SNMP agent has two communities: read community and write community . The
NMS identifies an SNMP agent through trap community. When sending a trap to the
NMS, the SNMP agent must provide a correct trap community; otherwise the NMS
rejects the trap.
II. Access control

z
MIB view
MIB view is a subset of all the managed objects in the MIB. An SNMP community has a
MIB view. The SNMP managers within an SNMP community can only access the MIB
objects in the MIB view of the SNMP community. The node in the MIB view must not
belong to a subtree in the MIB tree.
z
Access mode
A-3
Appendix A SNMP
There are two access modes: read-only and read-write. An access mode is available to
each managed object in the MIB view of an SNMP community. In general, the access
mode available to the managed objects in a read community is read-only, and the one
available to the managed objects in a write community is read-write.
A.4.2 Comparison of Security Systems in SNMP V1, V2, and V3

Table A-1 compares the security systems in SNMP V1, V2, and V3.
Table A-1 Comparison of security systems in SNMP V1, V2, and V3
Protocol
version
Function features
SNMP V1
SNMP V1 defines a community. The community represents a group of managed

devices. Each device can have a table of SNMP community names. The NMS
workstation uses this table to control the SNMP-based device access. However, the
SNMP agent does not check whether the sender uses the correct community
names. That is to say, the SNMP agent does not authenticate the SNMP manager.
SNMP V2
SNMP V2 defines "community name.
SNMP V3
In addition to the basic functions of SNMP V1 and V2, SNMP V3 defines the
management functions related to network security and access control.
A-4
Appendix B Solaris
Appendix B Solaris
Note:
z
For details on Solaris, see the related technical materials from SUN Microsystems Computer
Corporation.
The company name, trademarks, and manual names involved in this chapter belong to SUN
Microsystems Computer Corporation.
B.1 Introduction
B.1.1 Basic Concepts
I. Operating system
Independent of applications, the operating system manages resources and
applications.
Figure B-1 shows the position of the operating system.
Application
Operating system
Computer hardware
Figure B-1 Position of the operating system
II. Solaris
As a major branch of UNIX, Solaris usually runs on a SUN workstation or a
minicomputer.
B-1
Appendix B Solaris
III. SUN workstation

z
The models of SUN workstations include SPARC5, Ultra1, Ultra5, and Ultra10.
The hardware interfaces of the SUN workstation include SCSI, Ethernet, Serial
BUS, and MultiMedia.
The system software installed in the SUN workstation includes Solaris 2.X, CDE,
and OSF/Motif.
B.1.2 Architecture
The UNIX operating system consists of three parts: kernel, shell, and application, as
shown in Figure B-2.
Application
Shell
System invoke
Kernel
Hardware
Figure B-2 Architecture of the UNIX
II. Kernel
As the core of the UNIX, the kernel directs and schedules the running of the UNIX. It
also controls the resources of the computer and protects the applications from being
affected by the complex and detailed hardware events.
The core functions of the kernel include:
z
Managing computer memory.
Controlling the access to the computer resources.
Maintaining the consistency of the file system.
Managing interrupts and errors.
Controlling and allocating computer resources.
Maintaining the file system.
B-2
Appendix B Solaris
III. Shell
Shell is a special program of the UNIX. It is the interface between the kernel and user. It
is also the command descriptor of the UNIX. Three kinds of shells are commonly used,
as shown in Table B-1.
Table B-1 Classification of shells
Shell type
Shortened
form
Command
Major features
Bourne Shell
B Shell
sh
It is oldest, most widely used, and provided by

each UNIX operating system.
Korn Shell
K Shell
ksh
It is an extension to and compatible with B Shell
csh
Its format is like language C. It is powerful and

widely used in universities and colleges.
C Shell
By default, the current shell is Bourne Shell. To switch to another shell, enter the
desired shell command at the command prompt. For example, to switch from B Shell to
K Shell, run $ ksh.
IV. Application
The UNIX provides many software tools and applications, such as vi text editor and file
search and backup tools.
B.1.3 User Authority

There are two kinds of UNIX users: common user and superuser.
z
Common user: A common user is set by the account manager. A common user
can only change his login password and the properties and operation authority of
the files created by him. The command prompt for a common user is usually $.
Superuser: "root". The name cannot be changed. A superuser can create and
delete users. A superuser can also change the login passwords, file properties,
and operation authority of all other users. The command prompt for a superuser is
usually "#.
B-3
Appendix B Solaris
Note:
The difference between su and root:
su is used to switch from a common user to a superuser. That is to say, when a common user runs su at
the maintenance terminal, the system displays the password of root. In this way, the common user gets
the authority of root and can perform some operations the superuser is authorized to perform. However,
the environment variables "su" and root are different.
B.1.4 File System

File is a form of organizing and storing information in computer. In UNIX, a file is a
stream of bytes. File types include text file, binary file, device file, and directory.
I. File name
A file name usually consists of directory name and basic name. For example, The file
name /user/fred/report1, consists of directory name /user/fred/ and basic name
report1.
The maximum length of a UNIX file name is 255 bytes, and the file name is case
sensitive.
The UNIX file system also contains some special file names, as shown in Table B-2.
Table B-2 Special file names
File name
Description
Indicates the root directory.
Indicates the current directory.
..
Indicates the parent directory.
. character string
Indicates a hidden file, for example, a .profile file.
The file name supports wildcards.

z
? indicates one character.
For example, abc? represents all the file names that begin with abc and end with
one character.
z
* indicates any characters.
For example, ab*10 represents all the file names that begin with ab and end with
10.
B-4
Appendix B Solaris
II. File access authority

There are three kinds of UNIX file access authority, as shown in Table B-3.
Table B-3 File access authority
Authority
Access authority of a
common file
Read
Reads file name.
Write
Creates and deletes files and change file name.
Execution
Uses the files (for example, "cd command) to search for files.
Access authority of a directory
III. File path

There are two file path formats: absolute path and relative path. An absolute begins
with /, and a relative path begins with the current location.
Figure B-3 shows the absolute path and relative path.
/
Absolute path
bin
lib
usr
dev
etc
Relative path
stu1
program
sybase
data
install
Figure B-3 File path

The following example shows how to get the path/user/sybase/install/n2000.sh based
on the current relative path.
Table B-4 Path operation
Current directory
Run
/user/Sybase/install
cd n2000
/user/Sybase
cd install/n2000
/user
cd Sybase/install/n2000
cd /user/Sybase/install/n2000
B-5
Appendix B Solaris
IV. Directory structure of the file system

The directory of the file system looks like a tree, as shown in Figure B-4.
bin
lib
usr
stu1
program
dev
etc
sybase
install
data
Figure B-4 Directory structure of the file system

The following describes the directories of the file system:
z
/: root directory. It is the basis of the directory structure of the file system. All the
files and commands are logically connected to the root directory, regardless of
their location in the disk.
/bin: It usually saves the commands and programs to be used by the users. In
many operating systems, it is the link symbol of the files in /usr/bin.
/dev: It saves the special device files. In most operating systems, many
subdirectories are available in the /dev for saving different types of special files.
The names of these subdirectories are usually associated with the device name.
For example, "dsk and rdsk are for a disk, and pts and ptc are for a virtual
terminal. In Solaris, the /device directory is newly added. The files in /dev are
linked to /device based on file type so that they are saved in different directories
in /device.
/etc and /sbin: The two directories save usually save important files such as
configuration files, setting tools, and management programs. The /default
subdirectory is usually available in "/etc" for saving default command parameters.
For example, if you enter only one parameter when running su, the system will
get other needed parameters from /etc/default so as to run the command
correctly.
/home: The home directory used to save the user data.
lost+found: It saves the lost files. If a file is lost, it means that the file exists but
cannot be found in any directory. A disk error and abnormal shutdown of a
computer may result in loss of files. In this case, during the system boot-strap, the
B-6
Appendix B Solaris
"fsck" program can detect the lost file and put it in the lost+found directory. Each
disk partition contains one lost+found directory.
z
/mnt: For temporary use during the installation of the file system.
/proc: The files in this directory correspond to the processes in use. The files
execute the invocations involved in the access to the UNIX file system.
/tmp: It stores temporary files, which are cleared when the system starts.
/user: Many subdirectories are available in this directory for saving the
commands to be used by the users, shard libraries, and other programs of the
UNIX.
/var: It saves the data that frequently changes. For example, the /var/spoo
subdirectory saves the subsystem that provides spool service.

user/adm: Administration directory. It saves the account files and login related
files of the UNIX users. In a relatively new system, this directory is linked to
/var/adm.
user/bin: It saves binary command files, shell scripts, and some common
programs.
B.2 Login and Logout Commands

To log in to the operating system, you must have one login username and one login
password.
I. Login
There are two login modes. Normally, the system displays the login interface.
Command
Function
Login
Logs in to the system.
CDE login
Opens the terminal window.
II. Logout
There are three logout modes.
Command
Function
Logout
Logs out of the system.
Exit
Quits a shell.
^C
Interrupts a CDE.
B-7
Appendix B Solaris
III. Running level

At startup, the system logs in to different system running levels based on the
parameters. By default, after the boot-strap succeeds, the system logs in to running
level 3, that is, the multi-user status.
Table B-5 Running levels of the system
Running level
Function
PROM monitoring level
Single-user status: Other users cannot register with some file systems.
Multi-user status: No resource is shared.
Multi-user status: Some resources are shared.
Not used.
Halt and interactive boot (boot -a)
Reenters the default running level 3.
Ss
Single-user status: Other users cannot register with some file systems.
In the single-user status, the virtual console terminal becomes the system console, and
only the superuser can use the system console. To enter the single-user status, you
must know the password of root. In the multi-user status, all the defined terminals and
daemons run.
B.3 User Management Commands

ls -l
Use ls -l to view the query authority.
Example:
-rwxr-xr-x 1 rms sbsrms 12738 May 24 12: 13 disp
Parameter
Description
File type
rwxr-xr-x
File authority of the owner, co-group users, and other users.
Number of the links of the file
rms
Owner of the file
sbsrms
User group of the file
12738
File size, measured in bytes.
B-8
Parameter
Appendix B Solaris
Description
May 24 12: 13
The time at which the file is last changed.
disp
File name
I. useradd
Format
useradd [-u uid] [-g group] [-G group [,group]] [-d dir] [-s shell] [-m] [-e
expire] [-f inactive] username
Parameter
-m: Generates a home directory and copies the boot files to it. The user
information is saved in /etc/passwd.
Function
Adds a user.
Example
To add the user gama, run:

useradd -m -s /usr/bin/sh -g smp -G scp, infomix gama.
II. userdel
Format
userdel -r <username>
Parameter
-r: Deletes the home directory of a user.
Function
Deletes a user.
Example
To delete the user gama, run:

userdel gama.
III. usermod
Format
usermod [-u uid] [-g group] [G group [,group]] [-d dir [-m] ] [-s shell] [-e
expire] [-f inactive] <username>
Parameter
Function
Example
Modifies a user.
To change the shell type of the user gama, run:
/usr/bin/csh: usermod -s /usr/bin/csh gama.
B-9
Appendix B Solaris
B.4 File Operation Commands

I. ls
Format
ls [-l][-t][-a][-s][-d][-r][-i][-ul] [name]
-l: Generates a long list.
-t: Sorts files by change time.
-a: Lists all the files in the command directory, including those
beginning with a period.
Parameter
-S: Displays file size

-d: Displays the name of the specified directory.
-r: Inverts the output order.
-i: Displays of the number of the index nodes of each file.
-ul: Displays the access time of the files.
Function
Displays the contents of a directory or a file.
Example
To display the contents of the subdirectory first in the current

directory, run:
% ls first.
II. cd
Format
cd [dirname]
Parameter
dirame: Directory name
Function
Changes the working directory.

To enter the user directory: $ cd /user
To enter the parent directory: $ cd..
To switch to the home directory: $ cd
Example
To switch to the root directory: $ cd /

To
switch
from
/user/fred/docs/2000sales, run:
/user/fred/docs/97sales
cd ../2000sales or cd /user/fred/docs/2000sales
B-10
to
Appendix B Solaris
III. pwd
Format
pwd
Parameter
None.
Function
Displays the full path name of the current working directory.
Example
To display the path of the current directory:

$ pwd
IV. mkdir
Format
mkdir dirname1 [dirname2]
Parameter
dirname: Directory name
Function
Creates a directory or subdirectory.
Example
To create the n2000 subdirectory in opt, run:

mkdir opt/n2000
V. rmdir
Format
Parameter
rmdir dirname1
dirname1: Directory name
Deletes an empty directory.
Function
To delete a directory with files, run:

rm r.
Example
To delete the empty directory abc, run:

rmdir abc
VI. cp
Format
cp [-i][-p][-r][filenames] target
-i: Prompts whether to overwrite the files with the identical names.
Parameter
-p : Keeps the last change time and authority of the original files for
the new files.
-r: Copies a directory and all its subdirectories.
Function
Copies files.
B-11
Appendix B Solaris
To copy "f1" from /user/fred/reports/acme to /user/fred/reports/98Jan

and names the new file f2, run:
Example
cd /user/fred/reports
cp acme/f1 98Jan/f2
VII. mv
Format
Parameter
Function
mv [-f] [-i] filename1 [filename2] target

-f: Overwrites the files with the same names forcedly.
-i: Prompts whether to overwrite the files with the same names.
Moves and/or renames a file.
To move "f1 to user/fred/reports, run:
Example
mv i f1 user/fred/reports/
To move f1 to user/fred and name it f2run:
mv f1 user/fred/reports/f2
VIII. chmod
Format
chmod [ugoa]{+|-|=}[rwxlsStTugo] filename

chmod nnn filename
nnn: The range is 07. 1 indicates execution; 2 indicates write; 4 indicates
read.
u: Changes the authority of the owner.
g: Changes the authority of the group.
o: Changes the authority of other users.
a: Changes the authority of all the users.
+: Adds one kind of authority.
Parameter
-: Cancels one kind of authority.

=: Sets specified authority and deletes the original authority.
r: Assigns read authority.
w: Assigns write authority.
x: Assigns execution authority.
u: Assigns the authority of the owner.
g: Assigns the authority of the group.
o: Assigns the authority of other users.
B-12
Appendix B Solaris
Function
Changes the access mode of a file.
Example
To assign read, write, and execution authority of myfile, run: chmod

u+rwx myfile
IX. chown
Format
chown [-fhR]owner filenames

-f: Prevents errors from being reported.
Parameter
-h: Changes the owner of the linked files but not that of the original file.
-R: The operation is also performed on the subdirectories.
Function
Example
Changes the owner of a file for which the user has write authority.
To change the owner of file1 to user1, run:
chown user1 file1
X. chgrp
Format
chgrp [-f][-h][-R] owner filenames

-f: Prevents errors from being reported.
Parameter
-h: Changes the linked files.

-R: The operation is also performed on the subdirectories.
Function
Example
Changes the user group of a file.

To change the owner of file1 to group1, run:
chgrp group1 file1
XI. cat
Format
Parameter
cat filename
filename: Name of the file.
Displays the contents of the file.
Function
Outputs multiple files as one file. Note that the name of the output file must
be unique.
Creates a file.
Example
To display the contents of file1.c, run:

cat file1.c
B-13
Appendix B Solaris
XII. more
Format
more [-n][+row number][+/expression][filename]

-n: An integer. It specifies the number of the rows to be displayed. By
default, 22 rows are displayed.
Parameter
+row number: Specifies the first row to be displayed.

+expression: Specifies the first row as the one following the expression.
Function
Example
Displays a file.
To display 10 rows of the file1.c at one time, run:
more 10 file1
XIII. less
Format
more [-n] [+row number] [+/expression] [filename]

-n: An integer. It specifies the number of the rows to be displayed. By
default, 22 rows are displayed.
Parameter
+row : Specifies the first row to be displayed.

+expression: Specifies the first row as the one following the expression.
Displays a file.
Function
Example
With this command, you can press <y> to scroll up to display the next
row. You can also use ? to search for a single word.
To display the contents of file.c, run:
less file1.c
XIV. pg
Format
Parameter
Function
Example
pg [-number] [filename]
number: Specifies the number of rows to be displayed.
filename: Specifies the name of the file to be displayed.
Displays a file.
To display 10 rows of the file1.c at one time, run:
pg 10 file1
B-14
Appendix B Solaris
XV. head
Format
Parameter
Function
Example
head [- number] [filename]

number: Specifies the number of the rows to be displayed.
Displays the first n rows of a file. By default, the first 10 rows are
displayed..
To display the first 10 rows of file1.c, run:
head file1
XVI. tail
Format
Parameter
Function
Example
tail [- number] [filename]

number: Specifies the number of the rows to be displayed.
Displays the last n rows of the file. By default, the last 10 rows are displayed.
To display the last 10 rows of file1.c, run:
tail file1.
B.5 Process Control Commands

A process is a running program or a task being executed.
The UNIX completes multi-tasking through process control and schedule, and storage
management.
The following describes the frequently used process operation commands.
I. ps
Format
ps
Parameter
ps [-acdefjl][-g][-p][-s][-t][-u]
Function
Displays the status of all the current processes.
Example
B-15
Appendix B Solaris
II. kill
Format
kill pid
kill -9 pid (kills a process forcedly)
pid: Specifies the process ID
Parameter
signal: A number indicating a signal. It ranges from 0 to 31. 9 indicates

SIGKILL, which is the signal used to kill the processes that cannot be
terminated.
Function
Sends a signal to kill a specified process.
Example
To kill process 2032:, run:

% kill 2032
B.6 Network Communication Commands

The following describes the frequently used network communication commands.
I. ipconfig
Format
ipconfig
Parameter
None.
Function
Gets the IP address of a computer.
Example
To get the IP address of the local computer, run:

ipconfig
II. telnet
Format
telnet [IP address or domain name]
Parameter
IP address or domain name: The IP address or domain name of the

remote UNIX host.
Function
Logs in to a remote UNIX host from the local computer, and treats the
local computer as an emulation terminal of the remote computer.
Example
To telnet UNIX host 129.6.114.201, run:

telnet 129.6.114.201
B-16
Appendix B Solaris
III. ftp
Format
ftp [IP address or domain name]

?: Gets help on a command.
binary: Transfers files in binary system.
ascii: Transfers files in ASCII format.
cd: Changes the remote directory.
pwd: Displays the current remote directory.
dir: Displays the contents of the remote directory.
lcd: Changes the local directory.
Parameter
put [file1] [file2]: Copies the local file1 to remote file2.

get [file1] [file2]: Copies the remote file1 to remote file2.
mput: Copies multiple local files to the remote host.
mget: Copies multiple remote files to the local host.
status: Displays the current FTP status.
open [IP address or domain name]: Re-creates a new connection.
close: Closes the remote connection
quit or bye: Exits FTP.
Function
Transfers files between the local host and the remote host.
To copy "file1.zip from "C:\TEMP in the local computer to /usr/abc in
the remote host 129.6.114.201, do as follows:
C:
cd \ftp
C:\FTP>ftp 129.6.114.201
Enter user name and password
Example
ftp>binary
ftp>lcd c:\temp
ftp>cd /user/abc
ftp>fupt file1.zip
ftp>close
ftp>quit
C:\FTP>
B-17
Appendix B Solaris
B.7 vi
vi is a text editor. It can be used to insert and delete text and edit commands.
It has two modes:
z
Command mode:: Commands can be executed in this mode.
Insertion mode: Text can be inserted in this mode.
To switch from the insertion mode to the command mode, press <Esc>.
B.7.1 Starting/Exiting vi
z
To start vi, do as follows:
1)
At the shell prompt, enter vi. Before being prompted, do not press <Enter>.
2)
Enter a space and then the name of the file to be edited. If the file name does not
exist, vi will create it. If the file name exists in another directory, enter the path.
3)
Press <Enter> to start vi and displays the contents of the file.
To exit vi, do as follows:
4)
After editing the file, press <Esc>.
5)
Enter :wq to save the file and exit vi or enter :q! to exit vi without saving the file.
B.7.2 vi Commands
I. Text insertion commands
vi
Description
Inserts text before the pointer until <Esc> is pressed.
Inserts text at the beginning of a line until <Esc> is pressed.
Inserts text behind the pointer until <Esc> is pressed.
Inserts text at the end of a line until <Esc> is pressed.
Opens a new line above the current line, and inserts text until <Esc> is
pressed.
Opens a new line below the current line, and inserts text until <Esc> is
created.
II. Pointer move commands

vi
Description
h/j/k/I
Moves left/down/up/right
Moves to the beginning of the current line.
Moves to the beginning of the current line.
B-18
vi
Appendix B Solaris
Description
Moves to the end of the current line.
w,b
Moves to the beginning of the current word or the end/beginning of the

previous/next word.
WB
Moves one break forward/backward.
eE
Moves to the end of the current word/break.
LMH
Moves to the lowest/middle/highest line of the screen.
{}
Moves to the beginning of the previous/next paragraph.
Ctrl+F Ctrl+B
Moves to the previous/next screen.
Ctrl+D Ctrl+U
Moves to the previous/next half screen.
nG
Moves to line n.
1G G
Moves to the first/last line.
III. Text deletion commands

vi
Description
xdd
Deletes character/the entire line.
Deletes to the end of the current line.
dwDW
Deletes to the previous word/break
dbDB
Deletes to the next word/break.
deDE
Deletes to the end of the current word/break.
d0d$
Deletes to the beginning/end of the current line.
dhdl
Deletes the left/right character.
d{d}
Deletes to the beginning of the previous/next paragraph.
Da
Deletes to the beginning of the line containing a.
Da
Deletes to the character containing a.
IV. Text modification commands

vi
Description
cc
Changes the entire line.
Changes to the end of the current line.
cwcW
Changes to the previous word/break.
cbcB
Changes to the next word/break.
B-19
vi
Appendix B Solaris
Description
cecE
Changes to the end of the current word/break.
c0c$
Changes to the beginning/end of the current line.
chcl
Changes the left/right character.
c{c}
Changes to the beginning of the previous/next paragraph.
ca
Changes to the beginning of the line containing a.
ca
Changes to the character containing a.
B.7.3 vi Application Examples

I. Save change & exit vi
To save the changed contents and exit vi, run:
:wq
II. Exit vi witout saving change

To exit vi without saving the changed contents, run:
:q!
III. Undo
To undo insertion, deletion, or change, do as follows:
1)
If illegal characters appear on the screen, press <Ctrl+L> or <Ctrl+R> to refresh

the screen and delete the illegal characters.
2)
Run u to undo the modification.
B.8 find
Use find to search the specified directory and its subdirectories for a file meeting the
set conditions.
I. Format
find directory name conditions
Directory name: The directory to be searched. The directory and its subdirectories will
be searched. Multiple directory names can be specified here, with spaces between
them.
B-20
Appendix B Solaris
Conditions: The conditions for searching for a file, such as file name, owner, and last
change time.
II. Conditions
Condition
Description
-name name
Specifies the file or directory to be searched. A wildcard is supported, for

example, -name '*.c'.
-print
Prints the matching path.
-size n
Searches for the file that occupies n blocks.

Specifies the file type to be searched.
The file type x can be:
d : directory
f: file
-type x
b: block
c: character
p: pipe
-user user
Specifies the user of the file to be searched for. user can be a user
name or a uid.
-group group
Specifies the group to be searched. group" can be a group name or a

gid.
-links n
Searches for all the files with n links.
-atim n
Searches for the files accessed n days ago.
-mtime n
Searches for the files modified n days ago.
-exec command {}\;
Executes command on the file that is searched for. {} specifies the

parameters of command.
III. Logical operators

Logical
operator
Meaning
Example
Description
NOT
!-name "*.c"
All the files without a .c extension.
-o
OR
-size +10 -o -links 3
All the files with more than 10 blocks or more

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

links.
B-21
Appendix B Solaris
IV. Example
Example
Description
find /temp -name "ab*" -print
Searches "/temp for the files beginning with abc.
Find . -name test1 -print
Searches the current directory for test1.
B.9 grep
Use grep to search for the specified character string and print all the lines that contain
the character string.
I. Format
grep character string filename
II. Example
Example
Description
grep abc temp
Searches temp for abc.
grep This is a pentemp
Searches temp for This is a pen.
B.10 cmp
Use cmp to compare two text files or non-text files. The location of the first difference
between the two files is displayed. If the two files are identical, no information is
displayed.
I. Format
cmp [-Is] filename 1 filename 2
II. Parameter
Parameter
Description
-I
Displays the differences between the two files.
-s
Displays the value returned for cmp: 0 or 1. 0 indicates that two files are
identical; 1 indicates that they are different.
B-22
Appendix B Solaris
III. Example
Example
Description
cmp file1 file2
Compares file1 and file2 in the current directory.
B.11 UNIX Utilities

B.11.1 tar
Use tar to combine multiple files into one file library and save it in a tape or disk. If
necessary, the files can be extracted from the file library.
I. Format
$ tar [function -option [modifier]] [files]
tar consists of two parts: function option and modifier. The function option specifies the
actions of tar, such as read and write. The modifier is used to modify the actions of tar.
No - is needed in front of an option of tar.
II. Parameter
Category
function-option
modifier
Parameter
Description
Appends the specified file to the file library.
Accesses the files in the file library. If the file name is a directory,
the subdirectories are also accessed.
Creates a file library.
Creates the file at the beginning of the file library.
Activates the display mode to display the name of the file being
processed.
Activates the confirmation mode. After that, before processing

each file, tar requires you to confirm it.
Indicates that the file library is a file. If this option is omitted, the
file is saved in the preset tape or disk.
III. Example
z
To back up a file, run:
$ tar cv work
B-23
Appendix B Solaris
All files and subdirectories in the work directory in the current directory are backed up
to the default device, and the file information is displayed.
z
To restore a file, run:
$tar xvf /dev/rdsk/c0s0

The original file is restored.
B.11.2 compress and uncompress

Use compress to a file to save storage space. After being compressed, the file takes a
.z extension.
Use uncompress to extract a compressed file.
I. Format
compress
compress filename
uncompress
uncompress compressed-filename
II. Example
Example
Description
compress abc
Compresses the abc file.
uncompress abc.z
Uncompresses the abc.z file.
B.11.3 pkzip and pkunzip

Use pkzip to compress a file. After being compressed, the file takes a .zip extension.
Use pkunzip to extract a file.
I. Format
pkzip
pkzip filename
pkunzip
pkunzip filename
II. Example
Example
pkzip abc
Description
B-24
Example
unpikzip abc.zip
Appendix B Solaris
Description
Uncompresses the abc.zip file.
B.11.4 gzip and zip and

Use gzip to compress a file. After being compressed, the file takes a .gz extension.
Use zip to uncompress a file.
I. Format
gzip
filename
zip
zip -d filename
II. Example
Example
Description
gzip abc
zip abc.gz
Uncompresses the "abc.gz file.
B-25
Appendix C Sybase
Appendix C Sybase
Note:
z
For details on Solaris, see the related technical materials from Sybase Corporation.
The company name, trademarks, and manual names involved in this chapter belong to Sybase
Corporation.
C.1 Introduction
There are three Sybase versions:
z
Sybase running in UNIX
Sybase running in Novell Netware
Sybase running in Windows NT
Currently, Sybase 12.6 is most widely used in UNIX.

The Sybase adopts the client/server architecture. It supports resource sharing and load
balancing. It supports multiple hosts.
C.1.1 System Databases

After Sybase is installed, the following databases are generated:
I. master
The master database contains system tables and processes. It controls the users
operations on the user database and SQL Server. It constitutes the data dictionary of
Sybase.
The master database stores the following information:
z
Login accounts (user name of the SQL Server): syslogins, and sysremolelogins
System processes in execution: sysprocesses
Environment parameters: sysconfigures
Error messages: sysmessages
Information about each database in the SQL Server: sysdatabases
Storage space of each database: sysusages
Information about the installed tape and disk: sysdevices

C-1
z
Appendix C Sybase
Information about action locks: syslocks
II. model
The model database provides a model for new user databases. When you run create
database, the SQL Server generates a copy of the model and expands it as required. If
you modify the model database, all the newly created databases also change
accordingly.
III. sybsystemprocs
The sybsystemprocs database stores the system processes. When you execute a
storage process, which begins with sp_, the SQL Server searches the current
database for the process. If the process is not available in the current database, the
SQL Server searches the sybsystemprocs database. If the process is still not
available, the SQL Server searches the master database.
IV. tempdb
The tempdb database stores the temporary data tables. It is shared by all the
databases in the SQL Server. After you log out of the database or the system fails, all
the temporary data tables disappear.
C.1.2 Sybase Objects

The Sybase objects include tables, views, indexes, storage processes, triggers, default,
and rules.
The following describes the frequently used Sybase objects.
I. Tables
In a relational database, tables are the most important objects. All the data are stored in
tables. A table has two dimensions. A column is a field, and a row is an entry.
A table beginning with sys is a system table. A system table stores information about
the SQL Server. In the master databases, most tables are system tables. These
tables are generated when the "master database is created. Besides, when a user
database is created, a subset of the system tables is generated.
These system tables exist in only the master database:
z
sysconfigures
sysdatabases
sysdevices
syslogins
C-2
Appendix C Sybase
These system tables exist in both a user database and the system database:
z
sysalternates
syscolumns
sysindexs
syslogs
sysobjects,
sysusers.
II. Views
A view is a combination of the data in one or more tables . It looks like a table. However,
it is different from a table. The data you get through the view actually exists in the table
or tables. The database only defines the view.
III. Indexes
An index is based on a field. In Sybase, index is managed by the system. After the
index of a table is created, the system updates and maintains it automatically to keep
consistency with the corresponding table. It is not necessary for you to specify index,
because the system automatically confirms whether index is needed.
The Sybase supports three index types:
z
Combined index
The index is based on several fields.

z
Single index
The index is based on one filed.

z
Clustered index and nonclustered index
Clustered index enables the SQL Server to rearrange the table rows until the physical
order of the rows is identical to their logical order.
Nonclustered index does not require the physical order of the table rows to be identical
to their logical order.
One clustered index and multiple nonclustered indexes can be created.
Compared with nonclustered index, the clustered index enables faster information
retrieval. A clustered index must be created before any nonclustered index is created.
C.2 Sybase Operations

C.2.1 Starting Sybase
1)
Make sure that all the environment variables are set.
C-3
Appendix C Sybase
#SYBASE=/opt/sybase
#export SYBASE
#DSQUERY=sun2 (name of the Sybase server)
#export DSQUERY
2)
Run startserver to start Sybase server or backup server.
#cd $SYBASE/install
#./startserver -f ./RUN_sun2 (starts the master server: sun2)
3)
Run showserver to check whether Sybase server has started.
#cd $SYBASE/install
#./showserver
C.2.2 Shutting Down Sybase

1)
Execute isql under "/opt/sybase/bin.
#/opt/sybase/bin/isql -Usa -P
1>shutdown SYB_BACKUP
2>go (shuts down the backup Sybase server)
1>shutdown
2>go (shuts down the master Sybase server)
2)
Run showserver to check whether the Sybase server is shut down.
#cd $SYBASE/install
#./showserver
C.2.3 Recovering a System Software Fault

Automatic system recovery means that the system automatically starts the Sybase
server to recover system software fault.
The automatic recovery follows this order: master->model->temporary->user database.
In each database, the recovery mechanism observes the transaction log. If transaction
log records newer data than the database saves, the database is recovered forwards. If
the transaction is not completed, it is backed off.
C-4
Appendix C Sybase
Note:
The transaction log is a system table: syslogs. This table records database update requests such as
insertion, modification, and deletion. It does not record query operations.
C.2.4 Recovering a Medium Fault

If a fault occurs to a medium, you can recover the database through only the back up
database and transaction log. Therefore, you need to back up the database and
transaction log frequently.
Use dump to back up a database and transaction log. Use load to recover the
database and transaction log.
In creating a database, a database device is needed. Similarly, in backing up a
database and transaction log, a dump device is needed. The dump device can be a
tape, disk, or a file of the operating system.
To add a dump device, run sp_addumpdevice.
The command format is as follows:
sp_addumpdevice "type",device_name,physicalname
For example: sp_addumpdevice "disk", "db114", "/usr/sybase/zyl114.bak",1.
C.2.5 Backing Up a Database and Transaction Logs

I. Back up a database
Format: dump database database_name to dump_device
Example: dump database dcnmdb to /bak/dcnmdb.dmp
II. Back up transaction logs

Format: dump transaction database_name to dump_device
[with truncate_only | with no_log | with no_truncate]
The first two options delete the submitted transactions from the log, while the last
option does not.
Before the database backup, all the backup transaction logs are meaningless. You are
recommended to back up transaction logs frequently, because backing up transaction
logs takes less time and storage space than backing up the database.
C-5
Appendix C Sybase
C.2.6 Recovering a User Database

z
To recover a corrupted database, do as follows:
1)
Run dump with the option no_truncate to dump the transaction log of the user
database.
2)
Build a new database whose structure is identical to that of the corrupted

database.
3)
Run load to load the database and transaction log.
To load the database, run:
load database database_name

z
from file_name
To load the transaction log, run:
load transaction database_name from file_name

If the master, model, or sybsystemproces database is corrupted, do as follows to
recover it.
I. Recovering master
1)
Copy the system tables: sysdatabases, sysdevices, sysusages, sysloginroles,

and Syslogins.
2)
Dump the user database from the master device.
3)
Shut down the SQL Server.
4)
Run buildmaster to build a new master database or master device.
buildmaster m (rebuilds the master database)

buildmaster (rebuilds the master device)
5)
Start the SQL Server in single-user mode.
startserver -f RUN_server name -m

6)
If the master database is expanded using alter database, rebuild its distribution
sysusages strictly.
7)
If the network name of the backup server is not SYB_BACKUP in the interface file,
change the network name in sysservers:
update
sysservers
set
srvnetname="PRODUCTION_BSRV"
where
srvname="SYB_BACKUP"
8)
Make sure that the backup server is running.
Run showserver to check whether the backup server is running. If necessary, restart
the backup server.
9)
Load database master from master.bak". After the database is loaded, the SQL
Server is automatically shut down.
10) If a database device is added since the master database is last dumped, run
disk reinit to rebuild sysdevices.
C-6
Appendix C Sybase
11) If disk reinit is executed, or if create database or alter database is executed

since the database is last dumped, run disk refit to rebuild sysusages and
sysdatabases.
After the execution is completed, the SQL Server is automatically shut down.
12) Check consistency.
Compare the backup versions and new versions of sysusages and sysdatabases.
Run dbcc checkalloc for each database, and check the important tables in each
database. If any error is detected, run disk reinit and disk refit again.
13) If the master device recovers, recover the model database:
cd $SYBASE /scripts
setenv DSQUERY server name
isql -Usa P password -S server name <installmodel>
14) Load all the affected user databases.
15) Restore the ID of the server user.
16) Restart the SQL Server in multi-user mode..
II. Recovering model

buildmaster -d/device name -x
III. Recovering sybsystemproces

1)
Delete the sybsystemproces database.
If the physical disk is damaged, delete the device, and then run disk init to rebuild the
device.
2)
Rebuild the database.
C.3 Sybase Utilities

C.3.1 isql
isql is the SQL syntax analyzer used for the interaction with the Sybase Server.
I. Format
isql [switches]
II. Commonly used parameters

Parameter
-U username
Description
Allows you to specify a registration name.
C-7
Parameter
Appendix C Sybase
Description
-P password
Allows you to specify a password for the current Sybase server.
-S serve
Allows you to specify the name of the connected Sybase server.
-i
Inputs isql statement to a file.
-o
Outputs isql statement to a file.
III. Commonly used commands

Command
Function
go
Terminates a command.
reset
Clears the query buffer.
quit or exit
Quits isql.
The SQL provides these functions:

z
Data query commands
Creating a database and its objects
Adding, deleting, and modifying data
They are respectively defined as:

z
Data query language
Data definition language
Data query language
Table C-1 shows the commonly used syntax.

Table C-1 Commonly used syntax
Syntax
Description
select
select column_1,,column_n from table_name where conditions
insert
insert into table_name(column_1,,column_n) values(value_1,, value_n)
update
update table_name
conditions
delete
delete from table_name where conditions
truncate
truncate table table_name
drop
drop database database_name
sp_dropdevice
sp_dropdevice device_name
set
C-8
column_1=value_1,column_n=value_n
where
Appendix C Sybase
C.3.2 showserver
Use showserver to view information about the Sybase server running on the local
computer.
#cd /opt/sybase/install
#./showserver
C.3.3 startserver
Use startserver to start the Sybase server.
I. Format
startserver [switches]
II. Commonly used parameters

Parameter
Description
-f runserverfile
Specifies the name of the server running file. This file is taken as a reference
when the Sybase server is restarted.
-m
Starts the Sybase server in single-user mode. This mode is used to recover the
master database.
C-9
Appendix D SQL Server
Note:
z
For details on Microsoft SQL Server 2000, see the related technical materials from Microsoft
Corporation
The company name, trademarks, and manual names involved in this chapter belong to Microsoft
Corporation.
D.1 Introduction
Microsoft SQL Server is a large-capacity database management system (DBMS). It is a
relational database system based on the client/server architecture.
The Microsoft SQL Server features the following:
z
Using SQL to manage the data in the database.
Efficient concurrent control measures.
A secure accounting management system.
Be able to ensure data integrity.
The SQL Server has these objects: table, view, role, index, data type, and default value.
z
Table
The most important object in the database. All the user data is stored in tables. A
database may contain multiple tables for storing different data. A table consists of rows
and columns.
z
View
It is used to display a subset of the data stored in the tables. Two or more tables can be
linked to form a view. A view does not contain data. Only the linked data can be
displayed.
z
Role
A role can be defined and granted authority. Any user of this role has the authority
granted to the role. More than one role can be defined for a database. Each MS Server
has default roles.
z
Data type
D-1
A data type defines or describes the type of the data that can be input in a column, such
as number, character, time, and date. It also describes how the SQL server stores the
data. When a table is created, one data type is specified for a column. The SQL server
provides built-in data types. You can also define data types in the SQL server.
z
Default value
If you do not enter data in a column, the SQL server assigns a default value. For
example, if all the users are in Shanghai, you can set the default location of the users to
Shanghai. After that, this value will be input in each new row. You can input a value to
overwrite the default value.
D.2 Backing Up and Recovering a Database

The SQL server supports four database backup modes:
z
Database backup
Database backup means that all the data and objects in the database are backed up. In
this mode, the transaction logs are usually saved in a disk, the same database and
objects are created based on the transaction, and then the data is copied. This backup
mode costs much time and disk space, so it is usually used at night.
When a database is backed up, all the ongoing transactions will not be backed up. If
this mode is used, all the database modifications made between the backup and the
recovery cannot be recovered.
z
Transaction log backup
Transaction log backup means that all the transactions implemented on the database
are backed up, including those implemented since the last transaction log backup,
differential backup, and database backup.
In the transaction log backup, no data in the database is backed up. But if the database
is faulty, it can be recovered based on the backup transaction logs.
z
Differential backup
Differential backup means that the data changes made since the last database backup
is backed up, so it is incremental backup. The data loss can be minimized through
frequent differential backup.
The database backup, transaction log backup, and differential backup can be used
together to reduce the database backup time and reduce data loss.
The scheme is as follows:
1)
Back up the entire database regularly; for example, at every night.
2)
Make a differential backup at short intervals, for example, every three or four
hours.
D-2
3)
Make a transaction log backup between differential backup; for example, every 20
or 30 minutes.
File or file group backup
File or file group backup means that the database files or database folders are backed
up. The database consists of many files. If it is hard to back up the entire database at
one night, you can back up a portion of it every night.
D.2.1 Creating a Backup Device

Before the backup is made, a backup device must be created. The backup device
stores databases, transactions, or files. It can be a hard disk, tape, or pipe.
The SQL Server supports backing up the database to the local tape drive. When a hard
disk is used, the SQL Server can take the disks in the local and remote hosts as backup
devices. A hard disk stores data as files.
To add a backup device, do as follows:
1)
Start the SQL Server Enterprise Manager, and then log in to the desired server.
2)
Expand the Management folder.
3)
Right click the Backup, and then select [New Backup Device].
4)
In the Backup Device Properties-New Device dialog box that appears, enter the
logical name of the backup device.
5)
Select the type of the backup device.
If you click File Name, it means that a hard disk is used. This option is available when
disk files are created.
If you click Tape drive name, it means that a tape drive is used. This option is available
when a tape drive is connected with the local server.
6)
Click <OK>.
D.2.2 Backing Up a Database

In the SQL Server, the procedures for database backup, transaction log backup,
differential backup, and file or file group backup are the same.
To make a backup, do as follows:
1)
Start the SQL Server Enterprise Manager, and then log in to the desired database
server.
2)
Expand the database folder.
3)
Right click the desired database icon, and then select [All Tasks/Backup
Database].
4)
In the SQL Server Backup dialog box that appears, click the General tab.
5)
Select the desired backup type in the Backup area.
D-3
6)
In the Destination area, click <Add>.
7)
In the Select Backup Destination dialog box that appears, select a backup device,
and then click <OK>.
Now you return to the SQL Server Backup dialog box.

8)
Select the desired overwrite mode.
If you select Append to media, the current contents are appended to the current
backup. If you select Overwrite Existing Media, the existing backup is overwritten.
9)
Select the Schedule check box, and then click <>.
10) In the Edit Schedule dialog box that appears, enter the name of the backup task
in the Name box.
11) To change the default backup time, click Recurring, and then click <Change>. In
the Edit Recurring Job Schedule dialog box that appears, set the backup time,
12) In the SQL Server dialog box, click the Option tab, and then set the additional
options.
If you select Verify backup upon completion, the SQL Server will read all the backup
data, check whether the backup medium is accessible, and ensure the integrity of the
backup medium.
If you select Eject tape after backup, the tape will be ejected when the backup is
completed.
If you select Check media set name and backup set expiration, the SQL Server will
check whether the selected medium and backup device are valid.
If you select Backup set will expire, click On and then select a date.
13) Click <OK>.
D.2.3 Creating a Backup Wizard

A backup wizard provides a shortcut for database backup.
To create a backup wizard, do as follows:
1)
Start the SQL Server Enterprise Manager, and then click the desired.
2)
Select [Tools/Wizards] from the main menu.
3)
In the Select Wizard dialog box that appears, click + beside Management.
4)
From the expanded list, select Backup Wizard, and then click <OK>.
5)
In the welcome window that appears, click <Next>.
6)
In the Select Database to Backup dialog box that appears, select the database to
be backed up, and then click <Next>.
7)
In the Type Name and Description for Backup dialog box that appears, enter the
backup name and description, and then click <Next>.
D-4
8)
In the Select Type of Backup dialog box that appears, select a backup type, and
then click <Next>.
9)
In the Select Backup Destination and Action dialog box that appears, select a
backup device and the desired properties, and then click <Next>.
10) In the Backup Verification and Scheduling dialog box that appears, select
Checking media set name and backup set expiration date, and then click
<Next>.
11) In the Completing the Create Database Backup wizard dialog box that appears,
click <Finish>.
D.2.4 Recovering a Database

To recover a database, do as follows:
1)
Start the SQL Server Enterprise Manager, and then click the database server to
be recovered.
2)
Select [Tools/Restore Database] from the main menu.
3)
In the Restore database dialog box that appears, select the database to be
recovered from the Restore as database drop-down list.
4)
Select the desired recovery type in the Restore area.
5)
In the Parameters area, select the desired database from the Show backups of
database drop-down list.
If the database has been backed up, the backup history is displayed.
6)
From the First backup to restore drop-down list, select the desired backup
record.
By default, the last backup record is used to recover the database.

7)
Click the Option tab, and then set other parameters, as shown in Table D-1.
Table D-1 Other parameters

Option
Description
Eject tapes (if any) after restoring each backup
Ejects the tape from the tape drive after the database
recovery.
Prompt before restoring each backup
Prompts you to confirm each recovery.
Force restore over existing database
Overwrites the existing database files.
Restore database files as
Changes file location during the recovery.
Recovery completion state
Leaves the database after recovery so that the

database can be used immediately.
Leave database operational
Recovers the database and the transaction logs.
8)
Click <OK>.
D-5
D.2.5 Backing Up and Recovering a System Database

The system database stores the important data of the SQL Server. The loss of such
data will cause severe result, so the system database needs to be backed up. In this
way, the system database can be rebuilt if the system or database fails.
Usually, the entire master database needs to be backed up.
The master database can be recovered in two ways:
z
If the master database is damaged but the SQL Server can still start, recover the
database using the current backup.
If the master database is damaged and the SQL server cannot start or the
current backup cannot be used, rebuild the database using Rebuild Master Utility,
and then recover it using the backup.
To rebuild the master database, do as follows:

1)
Shut down the SQL Server.
2)
Run Rebuildem.exe in \Microsoft SQL Server\80\tools\Binn.
3)
In the Rebuild Master dialog box that appears, click <Browse> to view the source
directory containing the data files.
4)
Click <Setting>.
5)
In the Collation Settings dialog box that appears, set the desired parameters,
6)
Click <Rebuild>.
7)
After the master database is rebuilt, load its backup.
8)
If the backup cannot be used, re-create the backup device, and then recover
msdb, model, distribution, and user databases.
D-6
HUAWEI iManager N2000 Fixed Network Integrated Management System Appendix E Terms and Acronyms
Appendix E Terms and Acronyms

E.1 Terms
I. Multi-user
The ability that allows multiple users to use the same computer.
II. Multi-tasking
The ability that allows a user to execute multiple tasks at one time.
III. Terminal
A terminal is the interface unit between the user and the computer. They are two types
of terminals: character terminal and graphic terminal. A terminal usually consists of
monitor, keyboard, and terminal console. Sometimes, a mouse is also included. The
monitor connects with the keyboard through the terminal console. The terminal console
connects with the host of the computer through a common port, for example, a serial
port. The user communicates with the computer through the terminal. One UNIX host
can be connected with multiple terminals.
IV. Emulation terminal

An emulation terminal is a computer that serves as the terminal of another computer
when running a special program.
Currently, an emulation terminal usually connects with the UNIX host through a network
or a serial port.
V. Console
A console is a special terminal. It consists of monitor, keyboard, and mouse. They are
respectively connected to the monitor interface, keyboard interface, and mouse
interface of the host.
Usually, one host can connect with only one console. In addition to the functions of an
ordinary terminal, the console provides special functions. Important information such
as information about severe errors can be displayed only at the console. Some special
tasks such as recovery can be done only at the console.
E-1
VI. User name

UNIX is a multi-user operating system. That is to say, it can be used by multiple users at
the same time. Each user has login username, password, and operation authority.
Before using the UNIX, the user must enter username and password to log in. The
command prompt for a common UNIX user is $.
VII. Workgroup
Multiple users can be grouped to share information.
VIII. Process
A process is a program that is running. The UNIX supports multiple processes. Each
process has a unique process ID.
IX. Foreground process

A foreground process interacts with the user directly. It can receive the information input
by the user from the mouse and display the result on the monitor.
By default, the UNIX program started by the user runs at the foreground.
X. Background process
A background process does not interact with the user directly. Many UNIX processes
run at the background.
XI. Device
Also known as device file. It can be a hard disk, a floppy disk, and a serial port. In the
UNIX, all the hardware access operations are performed through the device files. The
device files are stored in the /dev directory. For example, /dev/hd0 indicates the first
floppy disk drive.
XII. Raw device

A raw device is a device file that is not processed. Its filename begins with an r. For
example, /dev/rhd0 indicates the raw device of the first floppy disk drive.
E.2 Acronyms
I
IP
Internet Protocol
E-2
MIB
Management Information Base
N
NMS
Network Management System
P
PDU
Protocol Data Unit
S
SNMP
Simple Network Management Protocol
T
TCP
Transmission Control Protocol
U
UDP
User Datagram Protocol
E-3

N2000 Troubleshooting Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

N2000 Troubleshooting Manual

Загружено:

Авторское право:

Доступные форматы

Chapter 1 Routine Maintenance .....................................................................

1.1 Maintenance Categories ........................................................................

Chapter 2 Troubleshooting .............................................................................

2.1 Basic Concepts ......................................................................................

2.4 Troubleshooting Cases ..........................................................................

Chapter 3 Maintenance Tools .........................................................................

3.1 Database Password Tool .......................................................................

Chapter 4 Remote Maintenance .....................................................................

4.1 Remote Maintenance Channel ...............................................................

Chapter 5 FAQ ..................................................................................................

5.1 Operating System ...................................................................................

5.1.3 How to Change Host Name of Sun Workstation (Sun/Solaris)? ....

Appendix A SNMP ...........................................................................................

A.1 Introduction ............................................................................................

Appendix B Solaris ..........................................................................................

B.1 Introduction ............................................................................................

Appendix C Sybase .........................................................................................

C.1 Introduction ............................................................................................

Appendix D SQL Server ..................................................................................

D.1 Introduction ............................................................................................

Appendix E Terms and Acronyms .................................................................

E.1 Terms .....................................................................................................

HUAWEI iManager N2000 Fixed Network Integrated

HUAWEI iManager N2000 Fixed Network Integrated Management

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

About This Manual

HUAWEI iManager N2000 Fixed

It introduces the installation procedures of the iManager

HUAWEI iManager N2000 Fixed

It introduces the basic operations of iManager N2000,

HUAWEI iManager N2000 Fixed

It offers suggestions on the routine maintenance of the

Chapter 2 Troubleshooting introduces alarm definition and categories. It presents

Network design & management personnel

Network maintenance personnel

Engineer for the iManager N2000 NMS

Normal paragraphs are in Arial.

Warnings, Cautions, Notes and Tips are in Arial Narrow.

Headings are in Boldface.

Terminal Display is in Courier New.

II. Command conventions

The keywords of a command line are in Boldface.

Command arguments are in italic.

Items (keywords or arguments) in square brackets [ ] are optional.

Alternative items are grouped in braces and separated by vertical bars.

Optional alternative items are grouped in square brackets and separated

Alternative items are grouped in braces and separated by vertical bars. A

Optional alternative items are grouped in square brackets and separated

III. GUI conventions

Multi-level menus are separated by forward slashes. For example,

IV. Keyboard operation

Press the left button twice continuously and quickly.

Caution: Means reader be extremely careful during the operation.

2.3.8 Using Instruments and Meters ................................................................................ 2-7

5.1.7 How to Switch from a Common User to a Superuser? ........................................... 5-2

B.4 File Operation Commands ..............................................................................................B-10

Chapter 1 Routine Maintenance

Chapter 1 Routine Maintenance

1.1 Maintenance Categories