U2000 Maintenance PDF

Chapter 1 System Knowledge ........................................................................
1-1
1.1 Requirements on Maintenance Personnel ............................................. 1-1
1.2 Databases .............................................................................................. 1-1
1.3 Related Users ......................................................................................... 1-2
1.3.1 Operating System Users ................................................................ 1-2
1.3.2 Database User ............................................................................... 1-3
1.4 Processes ............................................................................................... 1-4
1.4.1 System Supporting Processes ....................................................... 1-4
1.4.2 Service Supporting Processes ....................................................... 1-6
1.4.3 Sybase Processes ......................................................................... 1-9
1.5 Directory Structure ................................................................................. 1-10
1.6 Environment Variables ........................................................................... 1-11
1.6.1 Environment Variables of M2000 System ...................................... 1-11
1.6.2 Environment Variables of Sybase System ..................................... 1-13
1.7 Log Files ................................................................................................. 1-14
1.7.1 Log of Master Program .................................................................. 1-14
1.7.2 Log of Database System ................................................................ 1-15
1.7.3 Installation Log of M2000 System .................................................. 1-15
1.8 Scripts .................................................................................................... 1-15
1.8.1 Auto Startup Scripts of M2000 ....................................................... 1-15
1.8.2 Related Scripts of AdapterMonitor ................................................. 1-18
Chapter 2 M2000 Routine Maintenance ......................................................... 2-1
2.1 About This Chapter ................................................................................ 2-1
2.2 Overview of Routine Maintenance ......................................................... 2-1
2.3 Routine Maintenance Items .................................................................... 2-1
2.3.1 Daily Maintenance ......................................................................... 2-1
2.3.2 Weekly Maintenance ...................................................................... 2-4
2.3.3 Monthly Maintenance ..................................................................... 2-6
2.4 Routine Maintenance for Hot Backup Systems ...................................... 2-6
2.4.1 Checking Operating System .......................................................... 2-6
2.4.2 Checking Disk Management Software ........................................... 2-7
2.4.3 Checking HA Status ....................................................................... 2-7
2.4.4 Checking Host Hardware ............................................................... 2-8
Chapter 3 Handling M2000 Alarms ................................................................. 3-1
3.1 High CPU Occupation Rate .................................................................... 3-1
3.1.1 Details of Alarm.............................................................................. 3-1
3.1.2 Reference Information ................................................................... 3-1
3.1.3 Troubleshooting ............................................................................. 3-1
3.2 Insufficient Device Space for Alarm Database ....................................... 3-3
3.2.1 Details of Alarm.............................................................................. 3-3
3.3 Incorrect Alarm Explanation or Mapping File ......................................... 3-5
3.4 Insufficient Device Space for Performance Database ............................ 3-5
3.4.1 Details of Alarm.............................................................................. 3-6
3.5 Connection Interrupted Between BAM and Host.................................... 3-7
3.5.1 Details of Alarm.............................................................................. 3-7
3.6 Connection Interrupted Between BAM and Adapter .............................. 3-7
3.6.1 Details of Alarm.............................................................................. 3-7
3.7 FTP Connection Interrupted ................................................................... 3-8
3.7.1 Details of Alarm.............................................................................. 3-8
3.8 Performance Measurement Item Threshold Exceeded .......................... 3-9
3.9 Illegal Login ............................................................................................ 3-9
3.9.1 Details of Alarm.............................................................................. 3-9
Chapter 4 Handling Common Failures .......................................................... 4-1
4.1 List of Common Failures ........................................................................ 4-1
4.2 Procedure of Handling Common Failures .............................................. 4-2
4.2.1 Incorrect User Name and Password .............................................. 4-2
4.2.2 Unable to Delete "M2000 Server" Objects ..................................... 4-2
4.2.3 Red Cross on NE Icon ................................................................... 4-3
4.2.4 Failed to Set Up Connection between M2000 Client and Server... 4-4
4.2.5 Unable to Bring up the NE Service Console Menu with a
Right-click ............................................................................................... 4-6
4.2.6 IP Address Setting ......................................................................... 4-6
4.2.7 Failed to Refresh Configuration Data............................................. 4-7
4.2.8 Failed to Set Up Connection between M2000 Client and Alarm
Server ..................................................................................................... 4-8
4.2.9 Failed to Report Alarm Data .......................................................... 4-12
4.2.10 Low Query Execution Speed ....................................................... 4-12
4.2.11 Message of "Printing. Cannot be closed.".................................... 4-13
4.2.12 Failed to Register Performance Task .......................................... 4-13
4.2.13 Failed to Report Results of Performance Tasks .......................... 4-14
4.2.14 Solution to Log Space Full ........................................................... 4-18
4.2.15 Solution to Locked Database ....................................................... 4-18
4.2.16 Sybase System Installation Aborted ............................................ 4-19
4.2.17 Failed to Display Process Status ................................................. 4-19
4.2.18 Failed to Log in to Sybase System .............................................. 4-19
4.2.19 Failed to Start Sybase Automatically ........................................... 4-20
4.2.20 Failed to Building Database ......................................................... 4-20
4.2.21 Failed to Install M2000 Application Software ............................... 4-20
4.2.22 Failed to Copy File ....................................................................... 4-21
Chapter 5 Process Operations ....................................................................... 5-1
5.1 Service Processes .................................................................................. 5-1
5.1.1 Starting All Service Processes ....................................................... 5-1
5.1.2 Stopping All Service Processes ..................................................... 5-1
5.1.3 Starting Single Service Process ..................................................... 5-1
5.1.4 Stopping Single Service Process ................................................... 5-1
5.2 Sybase Processes .................................................................................. 5-2
5.2.1 Starting Sybase Processes ............................................................ 5-2
5.2.2 Stopping Sybase Processes .......................................................... 5-2
Chapter 6 Hardware Maintenance .................................................................. 6-1
6.1 Shutting Down Sun Server ..................................................................... 6-1
6.1.1 Shutting Down SunFire 4800 ......................................................... 6-1
6.1.2 Shutting Down Sun V880/Netra 20 ................................................ 6-2
6.2 Powering On Sun Server........................................................................ 6-3
6.2.1 Powering On SunFire 4800............................................................ 6-3
6.2.2 Powering On Sun V880/Netra 20................................................... 6-5
6.3 Powering On or Off T3 Disk Array .......................................................... 6-5
6.3.1 Powering On T3 Disk Array ........................................................... 6-5
6.3.2 Powering Off T3 Disk Array ........................................................... 6-5
6.4 Monitoring T3 Disk Array ........................................................................ 6-6
6.4.1 Using pSOSystem Commands to Monitor T3 Disk Array .............. 6-6
6.4.2 Using Manager GUI to Monitor T3 Disk Array ............................... 6-9
Appendix A Handling Common Network Faults ........................................... A-1
A.1 Common Network Faults ....................................................................... A-1
A.1.1 Failure of WS to Connect with M2000 Server ............................... A-1
A.1.2 Failure of WS in Far-end NMC to Connect with M2000 Server ..... A-2
A.1.3 Failure to Log in to M2000 Server ................................................. A-3
A.1.4 Failure of BAM to Connect with WS .............................................. A-4
A.2 Common Faults in the Debugging of Routers ........................................ A-5
A.2.1 Introduction to Router .................................................................... A-5
A.2.2 Faults of Physical Layer ................................................................ A-6
A.2.3 Faults of Link Layer ....................................................................... A-8
A.2.4 Faults of Network Layer ................................................................. A-11
A.2.5 Faults of Ethernet .......................................................................... A-12
Appendix B Common Operations of UNIX System ...................................... B-1
B.1 Solaris Operating System ...................................................................... B-1
B.1.1 Overview ........................................................................................ B-1
B.1.2 Features of UNIX ........................................................................... B-1
B.1.3 Terms Related to UNIX ................................................................. B-3
B.2 System Structure of UNIX ...................................................................... B-3
B.2.1 System Composition of UNIX ........................................................ B-3
B.2.2 File System of UNIX ...................................................................... B-5
B.2.3 Directory Structure of UNIX ........................................................... B-5
B.2.4 UNIX System Files ........................................................................ B-6
B.2.5 Program of UNIX ........................................................................... B-6
B.3 Solaris System Common Operations ..................................................... B-6
B.3.1 The Browse and Control of Directory ............................................ B-6
B.3.2 File Maintenance Command .......................................................... B-10
B.3.3 Text File Content-Displaying Commands ...................................... B-16
B.4 UNIX User Management Commands .................................................... B-20
B.4.1 Add User -- useradd ...................................................................... B-21
B.4.2 Delete User -- userdel ................................................................... B-21
B.4.3 Modify User Login Information -- usermod .................................... B-22
B.4.4 Modify User Password -- passwd .................................................. B-22
B.4.5 Add User Group -- groupadd ......................................................... B-23
B.4.6 Delete User Group -- groupdel ...................................................... B-23
B.4.7 Modify User Group Information -- groupmod ................................. B-23
B.5 Utility Commands and Programs ........................................................... B-23
B.5.1 Search File -- find .......................................................................... B-24
B.5.2 Search Special Character String -- grep ........................................ B-26
B.5.3 Utility Programs for File Backup and Restoration -- tar ................. B-26
B.5.4 Compress and Decompress Files -- compress & uncompress,
pack & unpack ........................................................................................ B-28
B.5.5 Send File Package to the System -- pkgadd ................................. B-29
B.5.6 Remove Package from the System -- pkgrm................................. B-29
B.5.7 Calculator -- bc .............................................................................. B-30
B.5.8 Basic Features of vi Editor ............................................................. B-30
B.6 System Resource Commands ............................................................... B-32
B.6.1 Obtaining Help Information about Commands -- man ................... B-32
B.6.2 Report Free Disk Space -- df ......................................................... B-33
B.6.3 Report the Disk Space Occupied by Each File System -- du ........ B-33
B.6.4 Display the Status of the Active Process -- ps ............................... B-34
B.6.5 Terminate a Process -- kill ............................................................. B-35
B.6.6 List the Information about the Current Login Users -- who ............ B-36
B.6.7 Report the Command Location -- whereis ..................................... B-37
B.6.8 Display the Path of a Specific Command -- which ......................... B-38
B.6.9 Display or Set the Host Name -- hostname ................................... B-38
B.6.10 Display the Information of the Operating System -- uname......... B-39
B.6.11 View the Host IP Address -- ifconfig ............................................ B-39
B.6.12 Recording Screen I/O Activities -- script ...................................... B-40
B.6.13 Display Current Date and Time -- date ........................................ B-41
B.7 Network Communication Commands .................................................... B-42
B.7.1 TCP/IP Protocol ............................................................................. B-42
B.7.2 Network Communication Commands ............................................ B-42
Appendix C Common Operations of Sybase System .................................. C-1
C.1 Sybase Database Concepts .................................................................. C-1
C.1.1 Database Equipment ..................................................................... C-1
C.1.2 System Database .......................................................................... C-2
C.1.3 Database Objects .......................................................................... C-3
C.1.4 SQL Server User and Their Rights................................................ C-4
C.2 Common Operation of Sybase Database System ................................. C-8
C.2.1 isql ................................................................................................. C-8
C.2.2 bcp ................................................................................................. C-10
C.2.3 Showserver ................................................................................... C-11
C.2.4 Startserver ..................................................................................... C-12
C.2.5 Shutdown ...................................................................................... C-12
C.3 T-SQL .................................................................................................... C-13
C.3.1 Data Definition Language (DDL) ................................................... C-13
C.3.2 Data Manipulation Language (DML) ............................................. C-14
C.3.3 Data Control Language (DCL) ....................................................... C-15
C.4 Sybase Database Backup and Restoration ........................................... C-19
C.4.1 System Software Failure Restoration ............................................ C-19
C.4.2 Backup Database and its Transaction Log.................................... C-19
C.4.3 Database Restoration .................................................................... C-20
C.4.4 How to Monitor Transaction Log Space ........................................ C-22
Appendix D Maintenance of UNIX Operating System .................................. D-1
Appendix E File Description of M2000 System ............................................. E-1

E.1 Directory structure .................................................................................. E-1
E.2 File Description ...................................................................................... E-2
E.2.1 ${HOME}/bin .................................................................................. E-2
E.2.2 ${HOME}/data ............................................................................... E-4
E.2.3 ${HOME}/lib ................................................................................... E-6
E.2.4 ${HOME}/etc .................................................................................. E-6
E.2.5 ${HOME}/backup ........................................................................... E-6
E.2.6 ${HOME}/log .................................................................................. E-6
E.2.7 ${HOME}/script/common ............................................................... E-6
E.2.8 ${HOME}/script/commonsvr .......................................................... E-9
E.2.9 ${HOME}/script/timersvr ................................................................ E-9
E.2.10 ${HOME}/script/alarmsvr ............................................................. E-10
E.2.11 ${HOME}/script/configsvr ............................................................ E-12
E.2.12 ${HOME}/script/pmsvr ................................................................. E-13
HUAWEI
iManager M2000
Maintenance Manual
V100R005
iManager M2000
Maintenance Manual
Manual Version T2-030373-20040928-C-1.52
Product Version V100R005
BOM 31033173
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 M2000 V100R005.
Related Manuals
The related manuals are listed in the following table.
Manual Content
It introduces the system structure, software functions, hardware
iManager M2000 Technical
functions and networking applications of the iManager M2000
Manual
Integrated Network Management System.
iManager M2000 Operation It is used for assisting the users in GUIs of iManager M2000
Manual Integrated Network Management System.
It provides information for the system installation, including the
iManager M2000 Installation
installation of the hardware, server software and client software,
Manual
and network applications.
It introduces M2000 system knowledge, routine maintenance
items, internal alarms, common faults and troubleshooting in the
iManager M2000 Maintenance
iManager M2000, as well as the solutions of common network
Manual
faults, the commands of Solaris operating system and Sybase
database, and the file system of M2000 server.
It provides an overall introduction to the iManager M2000
iManager M2000 Intelligent Intelligent Report System, including the system architecture, client
Report System User Manual operation, template customization, software installation,
maintenance and examples.
Organization
The manual consists of six chapters and five appendices.
z Chapter 1 System Knowledge introduces the following aspects: requirements

on maintenance personnel, databases, related users, processes, directory
structure, environment variables, log files and scripts to help user to maintain
iManager M2000 Mobile Network Management System.
z Chapter 2 M2000 Routine Maintenance provides daily, weekly, and monthly

maintenance items.
z Chapter 3 Handling M2000 Alarms introduces in detail how to handle internal
alarms on M2000 system.
z Chapter 4 Handling Common Failures introduces the analysis and locating of

common failures during M2000 running and installation.
z Chapter 5 Process Operations introduces the stop and restart operations of

M2000 service processes and Sybase processes.
z Chapter 6 Hardware Maintenance introduces how to shut down and power on

Sun servers and T3 disk array.
z Appendix A Handling Common Network Faults introduces the common

network faults analysis and fault location methods.
z Appendix B Common Operations of UNIX System lists the common

operations of UNIX system.
z Appendix C Common Operations of Sybase System lists the common

operations of Sybase database system.
z Appendix D Maintenance of UNIX Operating System lists the files under its
each directory of M2000 server.
z Appendix E File Description of M2000 System lists the files under its each
directory of M2000 server.
Intended Audience
The manual is intended for the following readers:

z Installation engineers and technicians
z Operation and maintenance personnel
Conventions
The 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
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.
Alternative items are grouped in braces and separated by vertical bars.
{ x | y | ... }
One is selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ]
by vertical bars. One or none is selected.
Alternative items are grouped in braces and separated by vertical bars. A
{ x | y | ... } *
minimum of one or a maximum of all can be selected.
Optional alternative items are grouped in square brackets and separated
[ x | y | ... ] *
by vertical bars. Many or none can be selected.
III. GUI conventions
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
Press the key with the key name inside angle brackets. For example,
<Key>
<Enter>, <Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
<Key1+Key2>
keys should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should
<Key1, Key2>
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, Warning, Danger: Means reader be extremely careful during the

operation.
Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Maintenance Manual
iManager M2000 Table of Contents
Table of Contents
Chapter 1 System Knowledge...................................................................................................... 1-1

1.1 Requirements on Maintenance Personnel ........................................................................ 1-1
1.2 Databases.......................................................................................................................... 1-1
1.3 Related Users .................................................................................................................... 1-2
1.3.1 Operating System Users ......................................................................................... 1-2
1.3.2 Database User ........................................................................................................ 1-3
1.4 Processes .......................................................................................................................... 1-4
1.4.1 System Supporting Processes ................................................................................ 1-4
1.4.2 Service Supporting Processes ................................................................................ 1-6
1.4.3 Sybase Processes .................................................................................................. 1-9
1.5 Directory Structure ........................................................................................................... 1-10
1.6 Environment Variables..................................................................................................... 1-11
1.6.1 Environment Variables of M2000 System............................................................. 1-11
1.6.2 Environment Variables of Sybase System............................................................ 1-13
1.7 Log Files .......................................................................................................................... 1-14
1.7.1 Log of Master Program ......................................................................................... 1-14
1.7.2 Log of Database System....................................................................................... 1-15
1.7.3 Installation Log of M2000 System ......................................................................... 1-15
1.8 Scripts .............................................................................................................................. 1-15
1.8.1 Auto Startup Scripts of M2000 .............................................................................. 1-15
1.8.2 Related Scripts of AdapterMonitor ........................................................................ 1-18
Chapter 2 M2000 Routine Maintenance....................................................................................... 2-1

2.1 About This Chapter ............................................................................................................ 2-1
2.2 Overview of Routine Maintenance..................................................................................... 2-1
2.3 Routine Maintenance Items ............................................................................................... 2-1
2.3.1 Daily Maintenance................................................................................................... 2-1
2.3.2 Weekly Maintenance............................................................................................... 2-4
2.3.3 Monthly Maintenance .............................................................................................. 2-6
2.4 Routine Maintenance for Hot Backup Systems ................................................................. 2-6
2.4.1 Checking Operating System ................................................................................... 2-6
2.4.2 Checking Disk Management Software.................................................................... 2-7
2.4.3 Checking HA Status ................................................................................................ 2-7
2.4.4 Checking Host Hardware ........................................................................................ 2-8
Chapter 3 Handling M2000 Alarms .............................................................................................. 3-1

3.1 High CPU Occupation Rate ............................................................................................... 3-1
3.1.1 Details of Alarm ....................................................................................................... 3-1
3.1.2 Reference Information............................................................................................. 3-1
i
Maintenance Manual
3.1.3 Troubleshooting....................................................................................................... 3-1

3.2 Insufficient Device Space for Alarm Database .................................................................. 3-3
3.2.1 Details of Alarm ....................................................................................................... 3-3
3.3 Incorrect Alarm Explanation or Mapping File..................................................................... 3-5
3.4 Insufficient Device Space for Performance Database ....................................................... 3-5
3.4.1 Details of Alarm ....................................................................................................... 3-6
3.5 Connection Interrupted Between BAM and Host............................................................... 3-7
3.5.1 Details of Alarm ....................................................................................................... 3-7
3.6 Connection Interrupted Between BAM and Adapter.......................................................... 3-7
3.6.1 Details of Alarm ....................................................................................................... 3-7
3.7 FTP Connection Interrupted .............................................................................................. 3-8
3.7.1 Details of Alarm ....................................................................................................... 3-8
3.8 Performance Measurement Item Threshold Exceeded ..................................................... 3-9
3.9 Illegal Login........................................................................................................................ 3-9
3.9.1 Details of Alarm ....................................................................................................... 3-9
3.9.2 Reference Information........................................................................................... 3-10
3.9.3 Troubleshooting..................................................................................................... 3-10
Chapter 4 Handling Common Failures ........................................................................................ 4-1

4.1 List of Common Failures.................................................................................................... 4-1
4.2 Procedure of Handling Common Failures ......................................................................... 4-2
4.2.1 Incorrect User Name and Password ....................................................................... 4-2
4.2.2 Unable to Delete “M2000 Server” Objects .............................................................. 4-2
4.2.3 Red Cross on NE Icon ............................................................................................ 4-3
4.2.4 Failed to Set Up Connection between M2000 Client and Server ........................... 4-4
4.2.5 Unable to Bring up the NE Service Console Menu with a Right-click..................... 4-6
4.2.6 IP Address Setting .................................................................................................. 4-6
4.2.7 Failed to Refresh Configuration Data...................................................................... 4-7
4.2.8 Failed to Set Up Connection between M2000 Client and Alarm Server ................. 4-8
ii
Maintenance Manual
4.2.9 Failed to Report Alarm Data.................................................................................. 4-12

4.2.10 Low Query Execution Speed............................................................................... 4-12
4.2.11 Message of "Printing. Cannot be closed."........................................................... 4-13
4.2.12 Failed to Register Performance Task ................................................................. 4-13
4.2.13 Failed to Report Results of Performance Tasks ................................................. 4-14
4.2.14 Solution to Log Space Full .................................................................................. 4-18
4.2.15 Solution to Locked Database .............................................................................. 4-18
4.2.16 Sybase System Installation Aborted ................................................................... 4-19
4.2.17 Failed to Display Process Status ........................................................................ 4-19
4.2.18 Failed to Log in to Sybase System ..................................................................... 4-19
4.2.19 Failed to Start Sybase Automatically .................................................................. 4-20
4.2.20 Failed to Building Database ................................................................................ 4-20
4.2.21 Failed to Install M2000 Application Software ...................................................... 4-20
4.2.22 Failed to Copy File .............................................................................................. 4-21
Chapter 5 Process Operations..................................................................................................... 5-1

5.1 Service Processes ............................................................................................................. 5-1
5.1.1 Starting All Service Processes ................................................................................ 5-1
5.1.2 Stopping All Service Processes .............................................................................. 5-1
5.1.3 Starting Single Service Process.............................................................................. 5-1
5.1.4 Stopping Single Service Process ............................................................................ 5-1
5.2 Sybase Processes ............................................................................................................. 5-2
5.2.1 Starting Sybase Processes ..................................................................................... 5-2
5.2.2 Stopping Sybase Processes ................................................................................... 5-2
Chapter 6 Hardware Maintenance................................................................................................ 6-1

6.1 Shutting Down Sun Server ................................................................................................ 6-1
6.1.1 Shutting Down SunFire 4800 .................................................................................. 6-1
6.1.2 Shutting Down Sun V880/Netra 20 ......................................................................... 6-2
6.2 Powering On Sun Server ................................................................................................... 6-3
6.2.1 Powering On SunFire 4800..................................................................................... 6-3
6.2.2 Powering On Sun V880/Netra 20............................................................................ 6-5
6.3 Powering On or Off T3 Disk Array ..................................................................................... 6-5
6.3.1 Powering On T3 Disk Array..................................................................................... 6-5
6.3.2 Powering Off T3 Disk Array..................................................................................... 6-5
6.4 Monitoring T3 Disk Array ................................................................................................... 6-6
6.4.1 Using pSOSystem Commands to Monitor T3 Disk Array ....................................... 6-6
6.4.2 Using Manager GUI to Monitor T3 Disk Array ........................................................ 6-9
Appendix A Handling Common Network Faults ........................................................................A-1

A.1 Common Network Faults...................................................................................................A-1
A.1.1 Failure of WS to Connect with M2000 Server ........................................................A-1
A.1.2 Failure of WS in Far-end NMC to Connect with M2000 Server..............................A-2
A.1.3 Failure to Log in to M2000 Server ..........................................................................A-3
iii
Maintenance Manual
A.1.4 Failure of BAM to Connect with WS .......................................................................A-4

A.2 Common Faults in the Debugging of Routers ...................................................................A-5
A.2.1 Introduction to Router .............................................................................................A-5
A.2.2 Faults of Physical Layer..........................................................................................A-6
A.2.3 Faults of Link Layer ................................................................................................A-8
A.2.4 Faults of Network Layer........................................................................................A-11
A.2.5 Faults of Ethernet .................................................................................................A-12
Appendix B Common Operations of UNIX System....................................................................B-1

B.1 Solaris Operating System..................................................................................................B-1
B.1.1 Overview .................................................................................................................B-1
B.1.2 Features of UNIX ....................................................................................................B-1
B.1.3 Terms Related to UNIX...........................................................................................B-3
B.2 System Structure of UNIX .................................................................................................B-3
B.2.1 System Composition of UNIX .................................................................................B-3
B.2.2 File System of UNIX ...............................................................................................B-5
B.2.3 Directory Structure of UNIX ....................................................................................B-5
B.2.4 UNIX System Files..................................................................................................B-6
B.2.5 Program of UNIX ....................................................................................................B-6
B.3 Solaris System Common Operations ................................................................................B-6
B.3.1 The Browse and Control of Directory .....................................................................B-6
B.3.2 File Maintenance Command.................................................................................B-10
B.3.3 Text File Content-Displaying Commands .............................................................B-16
B.4 UNIX User Management Commands..............................................................................B-20
B.4.1 Add User -- useradd .............................................................................................B-21
B.4.2 Delete User -- userdel...........................................................................................B-21
B.4.3 Modify User Login Information -- usermod ...........................................................B-22
B.4.4 Modify User Password -- passwd .........................................................................B-23
B.4.5 Add User Group -- groupadd ................................................................................B-23
B.4.6 Delete User Group -- groupdel .............................................................................B-23
B.4.7 Modify User Group Information -- groupmod........................................................B-23
B.5 Utility Commands and Programs.....................................................................................B-24
B.5.1 Search File -- find .................................................................................................B-24
B.5.2 Search Special Character String -- grep...............................................................B-26
B.5.3 Utility Programs for File Backup and Restoration -- tar ........................................B-26
B.5.4 Compress and Decompress Files -- compress & uncompress, pack & unpack ..B-28
B.5.5 Send File Package to the System -- pkgadd ........................................................B-29
B.5.6 Remove Package from the System -- pkgrm........................................................B-29
B.5.7 Calculator -- bc......................................................................................................B-30
B.5.8 Basic Features of vi Editor....................................................................................B-30
B.6 System Resource Commands.........................................................................................B-32
B.6.1 Obtaining Help Information about Commands -- man ..........................................B-32
B.6.2 Report Free Disk Space -- df ................................................................................B-33
iv
Maintenance Manual
B.6.3 Report the Disk Space Occupied by Each File System -- du ...............................B-33
B.6.4 Display the Status of the Active Process -- ps......................................................B-34
B.6.5 Terminate a Process -- kill ....................................................................................B-35
B.6.6 List the Information about the Current Login Users -- who...................................B-36
B.6.7 Report the Command Location -- whereis............................................................B-37
B.6.8 Display the Path of a Specific Command -- which................................................B-38
B.6.9 Display or Set the Host Name -- hostname ..........................................................B-38
B.6.10 Display the Information of the Operating System -- uname ...............................B-39
B.6.11 View the Host IP Address -- ifconfig ...................................................................B-39
B.6.12 Recording Screen I/O Activities -- script.............................................................B-40
B.6.13 Display Current Date and Time -- date...............................................................B-41
B.7 Network Communication Commands..............................................................................B-42
B.7.1 TCP/IP Protocol ....................................................................................................B-42
B.7.2 Network Communication Commands ...................................................................B-42
Appendix C Common Operations of Sybase System................................................................C-1

C.1 Sybase Database Concepts..............................................................................................C-1
C.1.1 Database Equipment ..............................................................................................C-1
C.1.2 System Database ...................................................................................................C-2
C.1.3 Database Objects ...................................................................................................C-3
C.1.4 SQL Server User and Their Rights.........................................................................C-4
C.2 Common Operation of Sybase Database System ............................................................C-8
C.2.1 isql ..........................................................................................................................C-8
C.2.2 bcp ........................................................................................................................C-10
C.2.3 Showserver...........................................................................................................C-11
C.2.4 Startserver ............................................................................................................C-12
C.2.5 Shutdown..............................................................................................................C-12
C.3 T-SQL..............................................................................................................................C-13
C.3.1 Data Definition Language (DDL) ..........................................................................C-13
C.3.2 Data Manipulation Language (DML) ....................................................................C-14
C.3.3 Data Control Language (DCL)..............................................................................C-15
C.4 Sybase Database Backup and Restoration ....................................................................C-19
C.4.1 System Software Failure Restoration ...................................................................C-19
C.4.2 Backup Database and its Transaction Log...........................................................C-20
C.4.3 Database Restoration...........................................................................................C-20
C.4.4 How to Monitor Transaction Log Space ...............................................................C-22
Appendix D Maintenance of UNIX Operating System................................................................D-1
Appendix E File Description of M2000 System ..........................................................................E-1

E.1 Directory structure .............................................................................................................E-1
E.2 File Description..................................................................................................................E-2
E.2.1 ${HOME}/bin ...........................................................................................................E-2
E.2.2 ${HOME}/data.........................................................................................................E-4
v
Maintenance Manual
E.2.3 ${HOME}/lib ............................................................................................................E-6

E.2.4 ${HOME}/etc ...........................................................................................................E-6
E.2.5 ${HOME}/backup ....................................................................................................E-6
E.2.6 ${HOME}/log ...........................................................................................................E-6
E.2.7 ${HOME}/script/common ........................................................................................E-6
E.2.8 ${HOME}/script/commonsvr ...................................................................................E-9
E.2.9 ${HOME}/script/timersvr .........................................................................................E-9
E.2.10 ${HOME}/script/alarmsvr ....................................................................................E-10
E.2.11 ${HOME}/script/configsvr....................................................................................E-12
E.2.12 ${HOME}/script/pmsvr ........................................................................................E-13
vi
Maintenance Manual
iManager M2000 Chapter 1 System Knowledge
Chapter 1 System Knowledge
To maintain iManager M2000 Mobile Network Management System (M2000 for short),
you need to know the following aspects:
z Requirements on maintenance personnel
z Databases
z Related users
z Processes
z Directory structure
z Environment variables
z Log files
z Scripts
1.1 Requirements on Maintenance Personnel

M2000 system maintenance personnel must be familiar with the following items:
z Operating systems Solaris and Windows
z Database Sybase
z Knowledge of computer networks such as Ethernet, TCP/IP, and Client/Server
z M2000 system and its functions
Refer to iManager M2000 System Description and “Chapter 1 System
Knowledge” in this manual.
z Installation of M2000 Server and Client application software
Refer to iManager M2000 Installation Manual.
z Routine operation on M2000
Refer to iManager M2000 Online Help.
z Routine maintenance, alarm handling and troubleshooting on M2000
Refer to this manual.
1.2 Databases
M2000 contains six databases built based on the Sybase database. They are cfgdb,
alarmdb, pmdb, comdb, timerdb and logdb.
The spaces of these databases are set during the installation of the M2000 server.
z The database cfgdb stores configuration data of the M2000 system.
z The database alarmdb stores alarm data of NEs and the M2000 system.
z The database pmdb stores the performance statistic data of NEs.
z The database comdb stores security data and topology data of the M2000 system.
1-1
Maintenance Manual
z The database timerdb stores timing task data of the M2000 service servers.
z The database logdb stores the log data of the M2000 system.
1.3 Related Users

At present, users involved in the M2000 system include:
z Operating system users
z Database users
Users with different roles are defined for the M2000 server. The following details the
role of each user.
1.3.1 Operating System Users
I. root
The “root” is the super user of UNIX system. The UNIX system must have a root user
having the highest authority for system management. You must be cautious when
operating the system as “root” to avoid accidental damage to system files, which may
paralyze the system. In routine operation, avoid operating as “root” unless necessary
and keep the password confidential.
The factory setting of the password is “root”. You can modify the password as needed.
II. m2000
The “m2000” is the main user of M2000. The default home directory is
/export/home/m2000, under which all M2000 system files are stored. The “m2000”
must be present. The user information of "m2000" cannot be deleted or modified,
otherwise the system may go wrong.
You can query the home directory of “m2000” using the following command:
$ ls -ld /export/home/m2000
drwxr-xr-x 17 m2000 staff 1536 Aug 11 08:34 /export/home/m2000
The owner of home directory must be m2000, otherwise the system does not operate
normally.
III. m2000ftp
The “m2000ftp” is reserved for third-party access. Its default password is "CfgPwdAc".
There is no content under this directory by default. The default home directory is
/export/home/m2000ftp.
IV. freshver
The "freshver" is the user that manages the client update packet. Its default password
is “freshver”. Changing this password is not recommended unless necessary. The
default home directory is /export/home/freshver.
1-2
Maintenance Manual
V. inrpt
The “inrpt” is the user of intelligent report system. It exists only after the intelligent report
system is installed. The default password is “inrpt”. The default home directory is
/export/home/inrpt.
VI. adaptermonitor
You can log in as “adaptermonitor” to monitor all adapter processes. No default

password is available. You can set the password as needed. The default home
directory is /export/home/adaptermonitor.
VII. adapter
The “adapter” is the owner of adapter processes of multi-version adapters. No default

password is available. You can set the password as needed. The default home
directory is /export/home/adapter, under which you can find different adapter
sub-directories.
The names of adapter users vary with the type of NE. The user name depends on the
actual situation, for example: bssadapter. The password is set during installation.
Corresponding user names are used for the maintenance of adapters of different NEs,
but root is not recommended.
You can query all the adapter user names installed in the system by executing the
following command as the super-user:
#cat /etc/passwd|cut -d: -f1|grep -v ^adapter|grep adapter
Note:
All users of the M2000 system belong to the staff group, and ksh is used under the shell environment.
1.3.2 Database User
I. sybase
The “sybase” is the installation user of Sybase database and must be present. Its
default home directory is /export/home/sybase.
To configure or modify Sybase system parameters, you must log in to the system as
“sybase” or “root”. Maintaining the Sybase system also requires you to log in as
“sybase”. The default password for this user is “sybase”. You modify the password as
needed. The “sybase” user information cannot be deleted or modified, otherwise the
system may go wrong.
1-3
Maintenance Manual
You can query the attributes of the sybase home directory as “m2000” using the
following command:
$ ls -ld /export/home/sybase
drwxr-xr-x 29 sybase staff 3072 Aug 11 08:33 /export/home/Sybase
The owner of the directory must be sybase, otherwise the system does not operate
normally.
II. sa
The “sa” is the administrator of Sybase database. The default password is “server1234”.
Changing this password is not recommended.
The login and access to Sybase database must be strictly controlled. You can log in to
the Sybase database using the following command:
$ isql -Usa -Pserver1234
1>
III. m2000
The user m2000 in the database system is the common user who can log in to Sybase
system. This type of user can perform interactive operation and maintenance for the
M2000 system service database. The password is encrypted. Avoid modifying
attributes of the M2000 service database during operation.
Note:
The “m2000” here is the internal user of the database system. It is totally different in role and function from
the “m2000” user of UNIX system described above.
1.4 Processes
The M2000 server processes can be divided into system supporting processes and
service supporting processes by nature. System supporting processes provide
lower-layer support for other processes and do not involve in service processing.
Service processes complete service functions.
Besides, processes of Sybase database will be introduced in the chapter.
1.4.1 System Supporting Processes
System supporting processes include the switch process, watchd process, timesvrd
process, and timersvrd process.
1-4
Maintenance Manual
I. switch
The switch process is responsible for:

z Frame transmission of service massages among the whole system. The switch
process is the foundation of information exchange and the foundation of the
M2000 operation. If the switch process is faulty, the whole M2000 system breaks
down.
z DeskNo distribution for all M2000 service processes to enable process
identification and information exchange.
The switch process is a daemon process, which contains a monitor process and a
service sub-process. The monitor process monitors the service sub-process and can
restart the service sub-process when the service sub-process stops responding or exits.
When querying the status of the switch process as user m2000, you can see the
following information (two processes):
$ ps -ef|grep switch|grep -v grep
m2000 371 369 0 Aug 11 ? 0:54 /export/home/m2000/bin/switch
m2000 369 1 0 Aug 11 ? 0:00 /export/home/m2000/bin/switch
It shows that the process 369 is the parent process of 371 and also the monitor process
of process 371.
Note:
The switch process does not involve database operations.
II. timesvrd
The timesvrd process is a timer process used by the switch process. It is also a
daemon process. When querying the status of the timesevrd process as user m2000,
you can see the following information (two processes):
$ ps -ef|grep timesvrd|grep -v grep
m2000 362 1 0 Aug 11 ? 0:00 /export/home/m2000/bin/timesvrd
m2000 384 362 0 Aug 11 ? 0:33 /export/home/m2000/bin/timesvrd
It shows that the process 362 is the parent process of 384 and also the monitor process
of process 384.
Note:
The timesvrd process does not involve database operations.
1-5
Maintenance Manual
III. watchd
The watchd monitors the hardware and software resources of M2000 server, such as
database size, CPU and memory utilization, and configuration status of the system
database.The watchd process periodically collects the above information and reports it
to client so that users can know the basic server configuration without logging in to the
UNIX workstation.
When querying the status of the watchd process as user m2000, you can see the
$ ps -ef|grep watchd|grep -v grep
m2000 510 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/watchd
m2000 511 510 0 Aug 11 ? 0:01 /export/home/m2000/bin/watchd
It shows that the watchd is not a daemon process. Its operational status is monitored by
the monsvrd process, which monitors operational status of all service processes and
starts the service processes that are not running. The process 510 is the parent
process of 511 and monitors the operational status of 511.
IV. timersvrd
Unlike the timesvrd described above, the timersvrd provides timing services for service
servers. The service servers register timing tasks in the timersvrd, and the timersvrd
notifies in fixed time the service servers to process the tasks. When querying the status
of the timersvrd process as user m2000, you can see the following information (two
processes):
$ ps -ef|grep timersvrd|grep -v grep
m2000 494 1 0 Aug 11 ? 0:00 monsvrd
/export/home/m2000/bin/timersvrd
m2000 496 494 0 Aug 11 ? 0:01 /export/home/m2000/bin/timersvrd
It shows that the timersvrd is not a daemon process. Its operational status is monitored
by the monsvrd process of M2000 system.
Note:
The timersvrd involves database operations. Its database is timerdb.
1.4.2 Service Supporting Processes
Service supporting processes include commonsvrd, configsvrd, alarmsvrd, alarmsend,

sasvrd, and pmsvrd processes.
1-6
Maintenance Manual
I. commonsvrd
The commonsvrd is a common service process responsible for M2000 user

management, authority management, and sub-net management. Logging in to the
M2000 system requires the presence of the commonsvrd process.
When querying the commonsvrd process status using the user m2000, you can see the
$ ps -ef|grep commonsvrd|grep -v grep
m2000 403 401 0 Aug 11 ? 0:01 /export/home/m2000/bin/commonsvrd
m2000 401 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/commonsvrd
Note:
The commonsvrd involves database operations. The service data is saved in the database comdb.
II. configsvrd
The configsvrd process is the service configuration process responsible for collection
of configuration data and processing of services. It is the sole interface through which
M2000 servers can obtain the configuration data. The configsvrd receives, analyzes,
processes, and stores the collected configuration data of various network elements.
When querying the status of the configsvrd process as user m2000, you can see the
$ ps -ef|grep configsvrd|grep -v grep
m2000 418 417 0 Aug 11 ? 0:11 /export/home/m2000/bin/configsvrd
m2000 417 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/configsvrd
It shows that the configsvrd is not a daemon process. Its operational status is monitored
by the monsvrd process of the M2000 system.
Note:
The configsvrd involves database operations. The service data is saved in the database cfgdb.
III. alarmsvrd
The alarmsvrd is the service alarm process responsible for alarm data collection and
alarm service processing. The M2000 system uses the alarmsvrd as the main platform
for fault monitoring. The alarmsvrd collects, receives, analyzes, processes, stores, and
1-7
Maintenance Manual
reports the real-time alarm information of various network elements. The alarmsvrd
accesses the database alarmdb.
When querying the status of the alarmsvrd process status as user M2000, you can see
the following information (two processes):
$ ps -ef|grep alarmsvrd|grep -v grep
m2000 440 438 0 Aug 11 ? 5:50 /export/home/m2000/bin/alarmsvrd
m2000 438 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/alarmsvrd
IV. alarmsend
The alarmsend is an alarm forwarding interface server responsible for reporting the
received alarm information in the fixed ASCII code format .The alarmsend is open to
third-party developers for re-development of alarm information. The alarmsend is a
daemon process.
When querying the alarmsvrd process status using the user m2000, you can see the
$ ps -ef|grep alarmsend|grep -v grep
m2000 446 1 0 Aug 11 ? 0:00 /export/home/m2000/bin/alarmsend
m2000 447 446 0 Aug 11 ? 0:00 /export/home/m2000/bin/alarmsend
If there is only a parent process, for example process 446, the third-party report
function is disabled and the sub-process is not started.
V. smsvrd
The smsvrd is an alarm SM forwarding server responsible for forwarding the received
alarm information by short message (SM) or Email. When querying the alarmsvrd
process status using the user m2000 after the hardware and software parameters for
alarm information conversion are configured, you can see the following information
(two processes):
$ ps -ef|grep smsvrd|grep -v grep
m2000 462 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/smsvrd
m2000 463 462 0 Aug 11 ? 0:11 /export/home/m2000/bin/smsvrd
If the hardware and software parameters used for converting the alarm information into
SMs are not configured, the alarm-to-SM conversion function is disabled. In such case,
when querying the smsvrd process status as user m2000, you can see only one
process:
$ ps -ef|grep smsvrd|grep -v grep
m2000 462 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/smsvrd
1-8
Maintenance Manual
Note:
The smsvrd process does not involve database operations.
VI. pmsvrd
The pmsvrd is the performance service process responsible for traffic and performance
data collection and service processing. It is the main platform of traffic and performance
monitor. The pmsvrd collects, receives, analyzes, processes, stores, and reports the
traffic information of various network elements.
When querying the pmsvrd process status using the user M2000, you can see the
$ ps -ef|grep pmsvrd|grep -v grep
m2000 478 1 0 Aug 11 ? 0:00 monsvrd /export/home/m2000/bin/pmsvrd
m2000 479 478 0 Aug 11 ? 0:03 /export/home/m2000/bin/pmsvrd
Note:
The pmsvrd involves database operations. The service data is saved in the database pmdb.
1.4.3 Sybase Processes
There are two Sybase processes. When querying the Sybase database process status
using the user M2000 , you can see the following information:
$ ps -ef|grep sybase|grep /export/home/|grep -v grep
sybase 277 275 0 Aug 11 ? 0:01 /export/home/sybase/bin/backupserver
-Ssybserver_back -e/export/home/sybase/ins
sybase 278 273 0 Aug 11 ? 19:55 /export/home/sybase/bin/dataserver
-ssybserver -d/dev/rdsk/c0t0d0s3 -e/export/h
The dataserver is responsible for data processing of Sybase data, including reading
data from and writing data to the database periodically.
The backupserver process backups and restores data.
The above two processes must function properly to ensure the normal operation of the
M2000 system.
1-9
Maintenance Manual
1.5 Directory Structure

You must install the M2000 program under the default home directory
/export/home/m2000. Table 1-1 describes the specific directory structure and files.
Table 1-1 Directory structure of M2000 system
Authority
Path and file name User/group Description
description
The root directory of M2000
${HOME}=/export/home/m2000 m2000/staff drwxr-xr-x
system.
The directory under which

${HOME}/bin m2000/staff drwxr-xr-x executable files and common
tools of program are stored.
The directory under which data
${HOME/data m2000/staff drwxr-xr-x files and configuration files that
change regularly are stored.
database files required for
${HOME}/lib m2000/staff drwxr-xr-x system running are stored. You
are prohibited from modifying
files in this directory.
configuration files of M2000
system are stored. The
${HOME}/etc m2000/staff drwxr-xr-x
contents of files under this
directory are generally
invariable.
The directory under which log
files of system running are
${HOME}/log m2000/staff drwxr-xr-x stored. Each service process
has its own log file named in the
format of *.log.
The system script directory
including scripts for establishing
${HOME}/script m2000/staff drwxr-xr-x
service database tables and
importing service data.
scripts for establishing common
${HOME}/script/common m2000/staff drwxr-xr-x
service database tables are
stored.
scripts for establishing
${HOME}/script/configsvr m2000/staff drwxr-xr-x
configuration server database
tables are stored.

scripts for establishing
${HOME}/script/pmsvr m2000/staff drwxr-xr-x
performance server database
tables are stored.
1-10
Maintenance Manual
Authority
description
scripts for establishing timer
${HOME}/script/timersvr m2000/staff drwxr-xr-x
server database tables are
stored.
scripts for establishing common
${HOME}/script/commonsvr m2000/staff drwxr-xr-x
stored.
scripts for establishing alarm
${HOME}/script/alarmsvr m2000/staff drwxr-xr-x
stored.
The directory under which all
${HOME}/backup sybase/dba drwxr-xr-x data backed up regularly is
stored.
The buffer directory of the alarm
report interface used for the
${HOME}/send m2000/staff drwxrwxrwx
interface of the third-party
network management system.
1.6 Environment Variables

This section introduces variables of the M2000 system.
1.6.1 Environment Variables of M2000 System
The shell environment for the user m2000 is ksh. Execute the command env as m2000
to get the current settings of environment variables:
_=/usr/bin/env
MANPATH=/usr/man:/usr/openwin/share/man
LANG=C
_INIT_UTS_RELEASE=5.8
HZ=100
_INIT_UTS_MACHINE=sun4u
SWITCHCONPATH=/var/tmp/s.switchcon
OMCSWITCHIP=10.129.27.145
PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/bin:/usr/openwin/bin:/usr/ccs/b
in:/opt/SUNWconn/bin:/bin:/export/home/sybase/bin:/export/home/m2000/b
in:.
_INIT_UTS_VERSION=Generic_108528-13
OMCSWITCHPORT=6688
_INIT_RUN_NPREV=0
1-11
Maintenance Manual
_INIT_NET_STRATEGY=none
LOGNAME=m2000
_INIT_UTS_NODENAME=b2k
_INIT_UTS_ISA=sparc
MAIL=/var/mail/m2000
_INIT_PREV_LEVEL=S
SYBASE=/export/home/sybase
DSQUERY=sybserver
SHELL=/bin/ksh
M2000_BACKUP_PATH=/export/home/m2000/backup
HOME=/export/home/m2000
_INIT_UTS_SYSNAME=SunOS
LD_LIBRARY_PATH=/lib:/usr/lib:/usr/ucblib:/usr/dt/lib:/export/home/syb
ase/lib:/export/home/m2000/lib
TERM=vt100
PWD=/export/home/m2000
SMAXSENDQUEUE=500
TZ=GMT-8
_INIT_RUN_LEVEL=3
_INIT_UTS_PLATFORM=SUNW,Sun-Blade-2000
The interpretation for several major environment variables is as follows. These

environment variables can be modified under the .profile environment of the user
m2000. Execute .profile directly under the root directory of the user m2000 if you want
the modification to be effective immediately.
z LANG=C
It indicates that the current language environment is C, that is, the standard
English environment. If the system permits, yon can change the English
environment into the Chinese one by running export LANG=zh. In this way, some
interactive messages of the system are in Chinese. The English environment is
recommended.
z OMCSWITCHIP=
It indicates the IP address of the M2000 server. Ensure that the IP address of
M2000 server is correct. Execute the command ifconfig –a to query and verify the
IP address of the workstation. Do not modify this environment variable. Otherwise,
it may cause system faults.
PATH=
/usr/bin:/usr/ucb:/etc:/usr/sbin:/bin:/usr/openwin/bin:/usr/ccs/bin:/opt/SUNWconn/
bin:/bin:/export/home/sybase/bin:/export/home/m2000/bin:.
It indicates the search path of the system. Make sure that the path
/export/home/sybase/bin:/export/home/m2000/bin is included. Otherwise, you
1-12
Maintenance Manual
cannot execute some system commands. This environment variable is

automatically modified by the system during installation. You cannot modify it.
z OMCSWITCHPORT=6688
It indicates the monitor port of the M2000 server. This environment variable is set
during installation. It is not allowed to modify it manually. Otherwise, the system
cannot run or provide network services.
z SYBASE=/export/home/sybase
It indicates the setting for environment variable of home directory of Sybase used
for calling some services and tools of Sybase. It is set during installation. It is not
allowed to modify this variable. Otherwise the system may not be able to use the
database, thus affecting the running of the system.
z DSQUERY=sybserver
It indicates the setting for query of server. The Sybase server of the M2000 system
is uniformly called sybserver. The setting cannot be modified. Otherwise, the
system may fail to implement operations of database.
z LD_LIBRARY_PATH=/lib:/usr/lib:/usr/ucblib:/usr/dt/lib:/export/home/sybase/lib:/e
xport/home/m2000/lib
It indicates the search path of the library. It is set by the system during installation.
Manual modification may affect system running.
z TZ=GMT-8
It indicates the time zone setting. Make sure that the setting of time zone is
consistent with that of the local area. Otherwise, the time of the whole system may
be affected. Set the time zone in the correct principle and method. For details, see
the installation part.
1.6.2 Environment Variables of Sybase System
The shell environment for the user sybase is also ksh. Execute the command env as
sybase to obtain the current settings of environment variables:
_=/usr/bin/env
LANG=C
HZ=100
PATH=/usr/bin:/usr/ucb:/etc:/export/home/sybase/bin:/export/home/sybas
e/install:.
LOGNAME=sybase
SYBASE=/export/home/sybase
DSQUERY=sybserver
DISPLAY=m2000svr:0.0
SHELL=/bin/ksh
HOME=/export/home/sybase
1-13
Maintenance Manual
DSLISTEN=sybserver
TERM=vt100
PWD=/export/home/sybase
TZ=GMT-8
The interpretation for several major environment variables is as follows. These

environment variables can be modified under the .profile environment of sybase user.
Execute .profile directly under the root directory of the user m2000 if you want the
modification to be effective immediately.
z LANG=C
z PATH=/usr/bin:/usr/ucb:/etc:/export/home/sybase/bin:/export/home/sybase/install
z DSQUERY=sybserver
z DSLISTEN=sybserver
z DISPLAY=m200svr:0.0
It is used to start the installer of graphical interface during sybase installation. That
is, xwindow service can be started in the machine “m2000svr”.
z TZ=GMT-8
The first four variables and the last one are the same as those of the M2000 system.
1.7 Log Files

This section introduces log files of the M2000 system.
1.7.1 Log of Master Program
The M2000 system adopts service modules to record logs and save them in the file
${HOME}/log of the user m2000. The major log files are as follows:
z Logalarmsvrd.383: Running log of the alarm server.
The number denotes the work process number of the alarm server.
z alarmsvrd.log: The log recorded by the system for the alarm server.
z pmsvrd.log: Log of the performance server.
z switch.log: Log of the switch.
z timersvrd.log: Log of the timer server.
z alarmsend.log: Log of the alarm network management interface.
z commonsvrd.log: Log of the common server.
z install.log: System installation log.
It records status information during system installation.
z switchroute: Routing table information of the system.
z configsvrd.log: Log of the configuration server.
z monsvrd.log: Log of system monitoring process.
z *.bakn: The backup files of the above log files.
1-14
Maintenance Manual
The “n” stands for number, for example, 1, 2, and 3. The size of log files of the
system is fixed. If the size exceeds the fixed value, the log files are updated and
saved with the same names as those of the original log files. In this way, the
overlarge file can be avoided and the readability of logs is improved.
1.7.2 Log of Database System
The M2000 system uses sybse as its database. The log recorded by sybase is
sybserver.log saved in the file ${HOME}/install of the user sybse where the running
status of the database system is recorded.
1.7.3 Installation Log of M2000 System
The installation log install.log of the M2000 system is saved in log directory under the
home directory of m2000. It records all the screen output from creating the database to
the end of installation during M2000 installation. To check whether M2000 is
successfully installed, view this log file.
1.8 Scripts
This section describes the scripts of the M2000 system.
1.8.1 Auto Startup Scripts of M2000
Their storage position is under the directory /etc/rc2.d.
I. S97sybsvr
z Function
This script is used to start the sybase database automatically during system restart
to ensure that the sybase database is started before the startup of the M2000
system. This script may also be used to stop or start the Sybase system service
manually.
z Parameters
{ start | stop }
z Introduction to the procedure
start: Run RUN_sybserver and RUN_sybserver_back to start the data server and
backup server of Sybase.
stop: Terminate processes of the data server and backup server so that the
Sybase process and Sybase service are stopped.
z When to be called
The system uses the start process automatically during system restart to start the
Sybase server. If you need to start and stop the Sybase server manually, run this
1-15
Maintenance Manual
script manually as root. For example, to start Sybase service, run #

/etc/rc2.d/S97sybsvr start. To stop Sybase service, run # /etc/rc2.d/S97sybsvr
stop.
z Relation with other scripts
None.
z Precautions
Avoid manual modification when running this script as root. In addition, avoid
terminating the running of the Sybase system. Otherwise, the running of system
may be affected.
II. S98m2000svr
z Function
This script is used to start the M2000 system automatically during system restart.
This script may also be used to stop or start the running of M2000 system
manually.
z Parameters
{ start | stop }
start: Start processes of switch, timesvrd, commonsvrd, configsvrd, alarmsvrd,
alarmsend, pmsvrd, and timersvrd as super-user.
stop: Terminate processes of switch, timesvrd, commonsvrd, configsvrd,
alarmsvrd, alarmsend, pmsvrd, and timersvrd as the super-user.
z When to be called
The system uses the start process automatically during system restart to start the
M2000 system. If you need to start or stop the server of the M2000 system
manually, run this script manually as root. For example, to start Sybase service,
run /etc/rc2.d/ S98m2000svr start. To stop Sybase service, run /etc/rc2.d/
S98m2000svr stop.
Ensure that the Sybase system is normally started before starting the M2000
system.
z Precautions
Run this script as root. Avoid modifying this script manually and terminating the
running of M2000 system. Otherwise, the normal processing of network
management service may be affected. In addition, ensure that M2000 system is
stopped before restarting it. Otherwise, repeated start may result in unpredictable
errors.
1-16
Maintenance Manual
III. S96ntpsvr
z Function
This script is used to start clock synchronization server automatically during
system restart and provide stable clock sources. With this script, the clock
synchronization server may also be stopped or restarted manually.
z Parameters
{ start | stop }
start: Run the /usr/local/bin/ntpd process to start clock synchronization server.
stop: Terminate the /usr/local/bin/ntpd process to stop the running of clock
synchronization server.
z When to be called
The system uses the start process automatically during system restart to start
clock synchronization server. If you need to start or stop clock synchronization
server manually, run this script manually as root. For example, to start Sybase
service, run /etc/rc2.d/ S96ntpsvr start. To stop Sybase service, run /etc/rc2.d/
S96ntpsvr stop.
None.
z Precautions
Avoid modifying this script manually and stopping the running of clock synchronization
server freely. Otherwise, the clock accuracy of whole mobile network system may be
affected, leading to the time error of network bills.
IV. S98m2000svrinrpt
z Function
This script is used to start and terminate the report server process.
z Parameters
{ start | stop }
Start: Start the report server process.
Stop: Terminate the report server process.
z When to be called
The system uses the start process automatically during system restart. If you need
to start or terminate the report server process manually, run the script as root. For
example, to start the report server process, run /etc/rc2.d/S98m2000svrinrpt
1-17
Maintenance Manual
start. To terminate the report server process, run /etc/rc2.d/S98m2000svrinrpt

stop.
Ensure that the Sybase system is normally started before starting the report
server.
z Precaution
Run the script as root.
1.8.2 Related Scripts of AdapterMonitor
I. adaptermonitor
z Function
This script is the link of the scripts S98adaptermonitor and K44adaptermonitor.
z Parameters
{ start | stop }
Start the monsvrd process as root.
The monsvrd process starts the adaptermonitor process and monitors it.
z When to be called
It is directly invoked by users.
z Storage position
Under the directory /etc/init.d.
This script is linked to scripts S98adaptermonitor and K44daptermonitor.
z Precaution
None.
II. S98adaptermonitor
z Function
This script is used to start adaptermonitor automatically during system start.
z Parameters
{ start | stop }
Start monsvrd process as root.
The monsvrd process starts the adaptermonitor process and monitors it.
z When to be called
1-18
Maintenance Manual
This script is used when the OS starts or directly used by users on other
occasions.
z Storage position
Under the directory /etc/rc2.d.
It is the symbolic link of the script /etc/init.d/adaptermonitor.
z Precaution
None.
III. K44adaptermonitor
z Function
This script is used to stop adaptermonitor in case of system start.
z Parameters
{ start | stop }
Send the stop signal to processes monsvrd and adaptermonitor.
z When to be called
It is called when the OS starts.
z Storage position
Under the directory /etc/rc1.d.
It is the symbolic link of the script /etc/init.d/adaptermonitor.
z Precaution
None.
1-19
Maintenance Manual
iManager M2000 Chapter 2 M2000 Routine Maintenance
Chapter 2 M2000 Routine Maintenance
2.1 About This Chapter

Routine maintenance aims to detect problems on time to prevent deterioration of
problems.
This chapter provides a list of routine maintenance items. Maintenance engineers can
check the operation of equipment based on this list. If any exception is found, record
the problem and handle the problem according to alarm processing procedures or the
common troubleshooting procedures.
If the operation instruction in the following lists is not detailed enough, you can refer to
the description in iManager M2000 Operation Manual.
Note:
Engineers conducting the M2000 routine maintenance must get familiar with the UNIX system and Huawei
M2000 system.
2.2 Overview of Routine Maintenance

This chapter provides routine maintenance items and operation instructions of the
M2000 system. You can add or delete the routines maintenance items as needed.
During the routine maintenance, you can
z Log in to the M2000 client as admin to observe the operational status of the
system.
z Log in to the M2000 server as m2000 for routine maintenance operations.
z Log in to the M2000 server to execute the system commands.
2.3 Routine Maintenance Items

This section provides daily, weekly, and monthly maintenance items.
2.3.1 Daily Maintenance
Table 2-1 lists the daily maintenance items of the M2000 system.
2-1
Maintenance Manual
Table 2-1 Daily maintenance checklist
SN. Item Operation instruction Remark

Checking operational status of the client
Topology Management
The status bar of the client indicates that
Check the the communication between the client and
Log in to the M2000 all the servers is normal.
T1 operational status
client as admin.
of the client All NE icons on the topology are normal
and without any cross.
Display the O&M
Select the desired NE,
interface of the The precondition is that the client PC is
T2 right-click the mouse,
network element installed with the LMT program of this NE.
and then select LMT.
(NE).
Configuration Management
View the
configuration
Start the centralized
information of
configuration
equipment in the
management system,
whole network
C1 and expand nodes of
through the
the configuration tree on
centralized
the left to view the
configuration
configuration data.
management
system.
Select the NE icon on
Synchronize the
the configuration tree,
C2 configuration data
right click the mouse,
manually.
and select [Refresh NE].
Fault Management
Check whether the
alarm information
Check the
generated by the host The NE BAM alarms can be reported
F1 real-time alarm
can be viewed on the accurately and promptly.
information.
centralized fault
management system.
Check whether alarm
information can be
Query and browse
queried and browsed
alarms at the fault
F2 according to preset
management
conditions at the
system.
centralized fault
management system.
Performance Management
2-2
Maintenance Manual

Check whether there is
suspended task in the
Check the task
P1 task list at the
statuses.
centralized performance
management system.
All the task results can be reported
normally.
If error messages are returned, handle the
problem as below:
1. If the returned message is “This task
Check the Query the task result does not exist”, re-register the task.
reporting of and see whether the 2. If the returned message is “The object
P2
performance result can be queried does not exist” or “The object does not
tasks. correctly. respond”, it indicates that the operation
results in the change of object and you
need to re-register the task, or delete the
original object and then add a new one.
3. If the returned task status is
“suspended”, activate this task.
Activate, suspend, or
Check the
delete a performance
performance task
P3 task and check whether
management
the operation is
function.
successful.
User operation log management

Select the menu
View the system [View/System Log] on
U1
log. the M2000 remote
workstation (RWS).
Checking the operational status of server
Check the "capacity” column in the output
result.
Normally, at least 20% of the harddisk
Check the
space should be available.
S1 harddisk space of df -k
the server. If the capacity of a file system approaches
80%, you need to remove the useless files
on this system or add harddisk to this
system.
2-3
Maintenance Manual

The server time must be consistent with the
local standard time.
Execute the command date to output the
current time. If the result is inconsistent with
date the local standard time, correct the server
Check the time of time.
S2 mmddHHMM[[cc]yy][.
the M2000 server.
SS] For example, to change the time to
14:53:43 on Friday March 28, 2003,
execute the following command:
#date 0328145303.43
Fri Mar 28 14:53:43 GMT 2003
# vmstat 5 5
procs memory page disk faults
cpu
r b w swap free re mf pi po fr de sr s0 s6 -- --
in sy cs us sy id
0 0 0 1054080 35400 4 16 3 15 12 0 0 15 0 0
Check the CUP 0 398 23171 464 13 7 81
S3 usage of the vmstat 5 5
server. 0 0 0 1022608 18336 2 1 1 28 27 0 0 13 0 0
0 384 28526 560 16 7 76
0 0 0 1022608 18248 1 0 0 14 9 0 0 18 0 0
0 415 30853 565 16 9 76
The CPU idle ratio cannot be lower than
40%. The id value (idle ratio) under the
CPU item cannot be too low.
2.3.2 Weekly Maintenance
Table 2-2 lists the weekly maintenance items of the M2000 system.
Table 2-2 Weekly maintenance checklist

Execute the following
command as m2000:
Check the $isql -Usa The database runs normally. No database is off
1 database -Pserver1234 line. There are at least six databases, including
status. cfgdb, pmdb, alarmdb, comdb, timerdb, and logdb.
1> sp_helpdb
2> go
2-4
Maintenance Manual

Check the 1>sp_helpdb alarmdb
2 space of
alarmdb. 2> go
Check the 1>sp_helpdb cfgdb

3 space of
cfgdb. 2> go
Check the 1>sp_helpdb comdb The available space of each database must be 200
4 space of
2> go MB at least.
comdb.
Check the 1>sp_helpdb pmdb
5 space of
pmdb. 2> go
Check the 1>sp_helpdb timerdb

6 space of
timerdb. 2> go
The following lists the auto backup policies of the

M2000 system:
Incremental backup of logs of five databases at
22:00 every day. The databases include comdb,
timerdb, logdb, cfgdb, and pmdb.
Full backup of all the data and logs of six
Check whether the suffix databases (including comdb, timerdb, logdb, cfgdb,
of each backup file pmdb, and alarmdb) at 00:00 every Sunday.
Check under the directory Deletion of all the backup files of the previous week
backup files /export/home/m2000/ba under the directory /export/home/m2000/backup2
7
of each kcup2 contains the date and moving the log files of the current week from
database. which indicates the day the directory /export/home/m2000/backup to
before the file backup /export/home/m2000/backup2 at 23:57 every
day. Saturday.
Backup of the data and logs to the tape machine (if
installed) at 10:00 every Monday. You can replace
the tape after 10:00 every Monday to obtain the
backup data of the last week.
The system carries out these backup operations
automatically.
Log in as m2000 and go
Remove to the log directory to
delete all the files with It is recommended you delete the outdated log files
8 outdated
the suffix “bak”: periodically.
files.
rm *.bak
Check the The execution result shows that the status is OK.
9 tape mt status
machine. This item is optional.
2-5
Maintenance Manual
2.3.3 Monthly Maintenance
Table 2-3 lists the monthly maintenance items of the M2000 system. The major task is
to check the physical equipment of the system.
Table 2-3 Monthly maintenance checklist
SN Item Operation instruction Remark

In normal case, all the power indicators are on.
For example, the following power indicators
(green) are on:
Check the z Sun Netra20 active and standby power
Observe whether the
system supply indicators (DC-A and DC-B)
1 indicator on each power
power
supply module is on. z POWER indicator
indicators.
z SYSTEM indicator
z DISK0-Active
z DISK1-Active
No maintenance indicator or yellow indicator
should be on or flashing. For the Netra20, the
Observe all the indicators POWER and SYSTEM indicators on the front
Check panel should be ON (green).
on the front and rear
2 system
panels of the host and disk If an error occurs, the ALARM1, ALARM2, and
indicators.
array. FAULT indicators are on (yellow).
If the disk array is configured, the RUN
indicator should be ON.
LAN Switch: The power indicator is on. The
Check all the external
indicator of the network port connected with
indicators.
Check the the network cable is flashing.
3 hardware of Confirm that hardware
If the terminal HUB is configured, the POWER,
the system. connections are correct
UNIT, and NET indicators are on, ACTIVE
and the operation is
indicator flashes slowly, and the rest indicators
normal.
are off.
2.4 Routine Maintenance for Hot Backup Systems

If the M2000 system is a hot-backup one (with two nodes), the routine maintenance is
as follows.
2.4.1 Checking Operating System
Table 2-4 provides the routine maintenance items for the operating system of the
M2000 hot backup system.
2-6
Maintenance Manual
Table 2-4 Operating system checklist
Item Operation instruction Standard Remark

System files does not exceeds
Hard disk size Execute df –k
80% of the total disk size.
No alarm of warning, error, fail,
Check /var/adm/message* and
System log or panic is generated, and no
/var/log/syslog*
process restarts.
Execute date and compare the
System time system time with the current
standard time.
Insert the test tape, log in as The execution result shows that
Tape machine. Optional
root, and execute mt status. the status is OK.
2.4.2 Checking Disk Management Software
Table 2-5 provides the routine maintenance items for the disk management software.
Table 2-5 Disk management software checklist

Statuses of all disks in use are
Status of all disks in Vxvm Execute vxdisk list
"online"
Logical volume status of Execute vxprint -th -g The pl and v of all volumes are
built-in disks in Vxvm rootdg “ACTIVE”, "ENABLED" and "RW"
Execute vxdg list, and
Logical volume status of The pl and v of all volumes are
then execute vxprint
stand-alone disks in Vxvm “ACTIVE”, "ENABLED" and "RW"
–th one by one
2.4.3 Checking HA Status
Table 2-6 provides the routine maintenance items for the HA status.
Table 2-6 HA status checklist

Statuses of all dataservices are
Dataservices status #scstat -g "on". Statuses of all resource
groups and resources are "online".
Status = OK and fo_Time =
NEVER for adapters of public
Status of network network
#pnmstat -L
adapters in cluster
Interconnect is not down for
adapters of private network.
2-7
Maintenance Manual

All nodes are in the cluster.
All private networks are "path
Cluster 3.0 #scstat online".
All resource groups and resources
are "online":
2.4.4 Checking Host Hardware
Table 2-7 provides the routine maintenance items for the host hardware.
Table 2-7 Host hardware checklist

Statuses of the CPU fans, power
/usr/platform/sun4u/sbin/ supply, and CPU temperature are
Whole system
prtdiag –v normal. No hardware failure is found
in the system.
Power supply of lominfo fan;lominfo psu Power supplies of all fans are
Optional
Netra fans lominfo events … normal.
2-8
Maintenance Manual
iManager M2000 Chapter 3 Handling M2000 Alarms
Chapter 3 Handling M2000 Alarms
This chapter describes how to deal with the following alarms within the M2000 server:
z High CPU Occupation Rate
z Insufficient Device Space for Alarm Database
z Incorrect Alarm Explanation or Mapping File
z Insufficient Device Space for Performance Database
z Connection Interrupted Between BAM and Host
z Connection Interrupted Between BAM and Adapter
z FTP Connection
z Performance Measurement Item Threshold Exceeded
z Illegal Login
3.1 High CPU Occupation Rate

This section describes how to handle the alarm of high CPU occupation rate.
3.1.1 Details of Alarm
The alarm indicates that the M2000 server is busy dispatching processes or switching
exchange areas.
The CPU occupation rate ranges from 1% to 99%. The recommended rate is between
70% and 95%, and the default rate is 80%. When the CPU occupation rate exceeds the
set threshold, the system reports “CPU Occupation Rate Too Large”.
3.1.2 Reference Information
The reference information related to the alarm is as follows:
Alarm level Alarm type Event type Alarm No. Alarm parameter
Critical Fault alarm Internal alarm 2141 idle, user, kernel
3.1.3 Troubleshooting
I. Alarm Cause
The possible causes of the alarm are:

z The threshold of the CPU occupation rate is set low.
z The processes are called frequently.
z There are frequent disk operations.
3-1
Maintenance Manual
z The memory size is small or the memory distribution is improper.

The direct causes may be:
z The NEs report a large number of alarms.
z Configuration data of a large number of NEs are refreshed simultaneously.
z The number of registered performance task is large, and the registry cycle is short.
II. Solution
The solutions to the alarm are:

z If the high occupation rate lasts for a short time, no operation is needed.
z Modify the alarm threshold of CPU occupation rate to a higher rate at the client.
z Contact Huawei technical support engineers if the alarm lasts for a long time.
z Check the memory occupation of the M2000 processes to find which process
occupies the CPU for a long time.
Use the following command to check the CPU occupation:
$prstat
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
27178 adapter 17M 13M sleep 58 0 0:00.00 0.1% adapterd/12
274 sybase 258M 63M sleep 59 0 0:48.36 0.1% dataserver/2
8899 m2000 27M 11M sleep 58 0 0:00.00 0.1% alarmsvrd/6
27187 sybase 1528K 1264K cpu0 58 0 0:00.00 0.0% prstat/1
8922 m2000 1040K 744K sleep 48 0 0:00.09 0.0% monsvrd/1
8882 m2000 5816K 4808K sleep 58 0 0:00.08 0.0% configsvrd/1
8836 m2000 2336K 1616K sleep 58 0 0:00.17 0.0% switch/1
8842 m2000 1776K 928K sleep 58 0 0:00.11 0.0% timesvrd/1
150 root 2424K 1640K sleep 58 0 0:00.00 0.0% inetd/1
156 root 1880K 1200K sleep 10 0 0:00.00 0.0% lockd/1
246 root 3040K 1672K sleep 50 0 0:00.00 0.0% htt_server/5
174 root 3360K 1776K sleep 58 0 0:00.00 0.0% syslogd/10
158 daemon 2496K 1648K sleep 20 0 0:00.00 0.0% statd/4
200 root 3064K 976K sleep 51 0 0:00.00 0.0% lpsched/1
120 root 2432K 1552K sleep 58 0 0:00.00 0.0% rpcbind/1
Use the following command to check the memory dispatch:

$ vmstat 1 5
procs memory page disk faults cpu
r b w swap free re mf pi po fr de sr s0 s6 in sy cs us sy id
0 0 0 137128 10808 1 0 1 20 14 0 0 3 0 0 0 158 3299 105 1 3 96
0 0 0 550416 4112 7 1 0 96 80 0 0 10 0 0 0 208 13322 217 5 12 83
0 0 0 550416 4112 4 0 0 40 40 0 0 5 0 0 0 173 10252 175 0 12 88
0 0 0 550416 4112 0 0 0 8 8 0 0 1 0 0 0 146 416 96 1 0 99
0 0 0 550416 4112 0 0 0 0 0 0 0 0 0 0 0 138 574 101 0 0 100
3-2
Maintenance Manual
us id sy
Percentage of time occupied by Percentage of time occupied by system
Percentage of idle time
user processes processes
3.2 Insufficient Device Space for Alarm Database

If the remaining data device space and log device space are less than the thresholds,
the system gives alarms:
z Alarm Database: data device space insufficient.
z Alarm Database: log device space insufficient.
The space can be set from 50 MB to 9999 MB. The recommended space is between
100 MB and 500 MB, and the default space is 200 MB.
The alarm indicates that the free space of the alarm database exceeds the threshold.
z If the data device space of the alarm database is insufficient, alarm data may be
lost.
z If the log device space of the alarm database is insufficient, alarm data may be
unavailable.
Number of parameters: 2
Critical Fault alarm Internal alarm 2143/2144 Data equipment space alarm, total
space(M) = 200, Free(M) = 199
I. Alarm Cause
The possible causes are:

z The remaining space of the database is lower than the threshold.
z The log device space is lower than the threshold.
II. Alarm Location
To locate the alarm, check whether:

z The alarm threshold is improper.
3-3
Maintenance Manual
z There are a large number of alarms.

z The log device space of the alarm database is small.
III. Solution
The solutions to the alarm are:

1) Set proper alarm threshold at the client.
Select the menu [Function/Alarm Server Setting/Alarm Threshold Setting] at the alarm
console. In the “Alarm Threshold Setting” window to set alarm threshold.
2) Delete history alarms manually.
Before deletion, be sure all history alarms can be deleted, because they cannot be
restored once deleted.
Execute the script /export/home/m2000/script/alarmsvr/delete_history.sh as root user
to delete the alarms by alarm level, alarm type, and alarm time. Recover this alarm after
the fault is cleared.
3) Delete alarm log manually.
Execute the script /export/home/m2000/script/alarmsvr/dump_alarmdb.sh. Recover
this alarm after the fault is cleared.
4) Add database space.
z Check the database space.
Use the following command to check the database attribute in the Sybase system:
$ isql -Uusername -Ppasswd
1>sp_helpdb databasename
2>go
For example, to check the database space of alarmdb, execute the following
command:
1>sp_helpdb alarmdb
2>go
z Add the database space.

If the database space is less than 30 MB, use the following command to add the
database space in the Sybase system:
$ isql - Uusername -Ppasswd
1>sp_helpdevice
2>go
1>alter database databasename on devicename=size /*Its unit is M bytes*/
2>go
3-4
Maintenance Manual
For example:
1>alter database alarmdb on data_dev=100
2>go
z Backup history data to other device, and then delete the unnecessary data.
$ isql -Uusername -Ppasswd
1>dump database databasename to filename
2>go
1>truncate table tablename
2>go
For example:
1>dump database alarmdb to "/export/home/sybase/alarmdb.dat1012"
2>go
1>truncate table history
2>go
3.3 Incorrect Alarm Explanation or Mapping File

This section describes the incorrect alarm explanation or mapping file.
Alarm level Alarm type Event type Alarm No.

Critical Event alarm Internal alarm 2501
I. Alarm Cause
The alarm cause is that the configuration file of the adapter is incorrect.
II. Solution
Check whether the files under the directory etc of the adapter exist.
3.4 Insufficient Device Space for Performance Database

If the remaining data device space or log device space of the performance database is
less than the thresholds, the system alarms:
z Performance Database: data device space insufficient
3-5
Maintenance Manual
z Performance Database: log device space insufficient
The alarm indicates that the space of the alarm database exceeds the threshold.
If the remaining data device space of the performance database is insufficient, the
performance statistic results may be lost and the performance server may be
suspended.
If the log device space of the performance database is insufficient, performance service
may be unavailable.
Number of parameters: 2
Critical Fault alarm Internal alarm 2704/2705 Data equipment space alarm, total
space(M) = 200, Free(M) = 199
I. Alarm Cause
The remaining data device space of the performance database is less than 200 MB.
II. Alarm Location
To locate the alarm, check whether:

z The alarm threshold is improper.
z There are a large number of statistic results in the database.
z The log device space of the performance database is small.
III. Solutions
Perform the following operations to clear the alarm:

1) Delete manually the log that is no longer needed. Please refer to “4.2.14 Solution
to Log Space Full”.
2) Add data device space to the performance database. Please refer to “3.2.3 III. 4)
Add database space.”.
3) Manually recover this alarm after the fault is cleared.
3-6
Maintenance Manual
3.5 Connection Interrupted Between BAM and Host

This section describes the alarm of connection interruption between the BAM and the
host.
When the connection between BAM and host is interrupted. “BAM and Host
disconnect” is reported.

Critical Fault alarm Internal alarm 2505
I. Alarm Cause
The alarm cause is that the connection between the BAM and the host is disconnected.
II. Solution
Check whether the connection between the BAM and the host is normal.
3.6 Connection Interrupted Between BAM and Adapter

This section describes the alarm of interruption between the BAM and the adapter.
When the communication between the adapter and the BAM/GPRS is disconnected.
“BAM and Adapter disconnect” is reported.

3-7
Maintenance Manual
To handle this alarm, do as follows:

z Check whether the connection between the adapter and the BAM/host (GPRS) is
normal.
z Check whether the user name and password of the adapter are correct for the
BAM. There is "User login success" in the log of the adapter.
z Select the NE icon in the RWS, and press <Ctrl+Shift+Alt+F11> to modify the user
name and password for the BAM. For security consideration, the user name and
password in the displayed window are blank, no matter whether the user name
and password are set or not.
Caution:
When you modify the binary BAM user name and password at the LocalWS, all inputs are converted to
upper case. Therefore, you must input the upper case user name and password to log in to the BAM from
the RWS.
3.7 FTP Connection Interrupted

This section describes the alarm of FTP connection interruption.
When logging in to the cBSC/RAC BAM by FTP fails, “FTP logging incorrect” is
reported.
The reference information of versions later than B03D502 is as follows:

The reference information of versions earlier than B03D502 is as follows:

3-8
Maintenance Manual
Perform the following operations to clear the alarm:

z Check whether the connection between the cBSC/RAC and the M2000 is normal.
z Check whether the FTP user name and password are correct by logging to BAM in
FTP mode. The default user name and password are “ftp” and “ftp1234”
respectively.
z Confirm whether FTP service is started at the BAM.
3.8 Performance Measurement Item Threshold Exceeded

This section describes the alarms of performance measurement item threshold
exceeded.

Customized Event alarm Internal alarm 65538
I. Alarm Cause
The alarm cause is that the performance indexes exceed the defined alarm threshold.
II. Solution
Check and trace network operations according to the specific indexes that exceed the
threshold.
3.9 Illegal Login

This section describes the alarm of illegal login.
The alarm is reported when:

z Logging in at illegal time.
z Logging in at illegal location.
z Wrong user name and password are entered for three times.
3-9
Maintenance Manual
The reference information related to the alarm is as follow:
Two alarm parameters: illegal user
name and illegal IP
The alarm information may be:

z Locked user (%s) attempts to log in from (%s)!
z User (%s) attempts to log in from (%s) at illegal time!
z User (%s) attempts to log in from illegal location (%s)!
z Password of user (%s) is incorrect! User to be locked…, ip (%s)
I. Alarm Cause
The possible causes for the alarm are:

z The locked user attempts to log in.
z The user attempts to log in at illegal time.
z The user attempts to log in at illegal location.
z The user enters the incorrect password.
II. Solution
Check whether there is illegal intrusion according to the alarm information, or contact
the system administrator.
3-10
Maintenance Manual
iManager M2000 Chapter 4 Handling Common Failures
Chapter 4 Handling Common Failures
The chapter introduces how to analyze and locate common failures of the M2000
system during M2000 running and installation. The common failure are grouped into
the following categories:
z Common failures in the common platform
z Common failures in the configuration management
z Common failures in the fault management
z Common failures in the performance management
z Common installation and maintenance failures
4.1 List of Common Failures

Common failures are listed in Table 4-1. Regarding the detailed analysis and locating
procedures, please see related sections.
Table 4-1 Items of common failure
Service Module Item

Incorrect User Name and Password
Unable to Delete “M2000 Server” Objects
Red Cross on NE Icon
Common platform Failed to Set Up Connection between M2000 Client and Server
Unable to Bring up the NE Service Console Menu with a
Right-click
IP Address Setting
Configuration Management Failed to Refresh Configuration Data

Failed to Set Up Connection between M2000 Client and Alarm
Server
Fault Management Failed to Report Alarm Data
Low Query Execution Speed
Message of "Printing. Cannot be closed."
Failed to Register Performance Task
Failed to Report Results of Performance Tasks
Performance Management
Solution to Log Space Full
Solution to Locked Database
4-1
Maintenance Manual
Service Module Item
Sybase System Installation Aborted

Failed to Display Process Status
Failed to Log in to Sybase System
Installation and Maintenance Failed to Start Sybase Automatically
Failed to Building Database
Failed to Install M2000 Application Software
Failed to Copy File
4.2 Procedure of Handling Common Failures

The following describes how to handle the common failures.
Note:
The remote workstation described in this chapter is the remote client of the iManager M2000. To start the
RWS, you may click Windows menu [Start/Program/iManager M2000/Integrated Network Management
System], or run the remotews.exe file under the "bin" directory in the M2000 installation path.
4.2.1 Incorrect User Name and Password
I. Description
System prompts incorrect user name or password when user tries to log on.
II. Analysis
In the M2000 system, user name and password are case sensitive.
III. Solution
Input the user name and password again, be sure to use correct case.
4.2.2 Unable to Delete “M2000 Server” Objects
I. Description
User is unable to delete an “M2000 Server” object in the integrated network

management system.
4-2
Maintenance Manual
II. Analysis
When M2000 installation is finished, by default there will be an OMC object named
“M2000 Server”, which represents M2000 itself. However in the M2000 system, only
one “M2000 Server” object is allowed, as a result, the integrated network management
system only provides user with the authority to modify other than delete this “M2000
Server” object or add a new one.
4.2.3 Red Cross on NE Icon
I. Description
The red cross on the NE icon indicates that the connection between the Client and the
BAM of the NE is broken. The possible reasons are:
z The adapter runs abnormally.
z The communication between the server and the BAM is abnormal.
z The adapter cannot log in to the BAM successfully.
II. Solution
To handle the problem, proceed as follows:

1) Check whether the Adapter runs normally:
z Press <F6> on the RWS to display the [Running Status Monitoring] window.
z In the top-right sub-window, check whether the NE’s BAM IP is consistent with that
in the routing information of its corresponding Adapter.
z Check whether the type description is “Adapter”.
YÖ 2)
NÖ Check the running status of the Adapter process at the server. Check that the
Adapter is configured correctly and then restart the related Adapter process. Proceed
as follows:
z Check the running status of the Adapter process at the server.
For example, if the adapter is connected to the BAM (IP: 10.105.33.238), there
should be the process of "…/adapterd 10.105.33.238" when executing ps-ef|grep
adapterd.
z Check the adapter.cfg at the server.
Execute more etc/adapter.cfg.
The following information is displayed (example):
#private
[howmany]
AdapterNumbers = 1
[adapter]
SwitchIP = 10.11.43.57
4-3
Maintenance Manual
SwitchPort = 6688
BamIP = 10.105.33.238
BamPort = 6000
FmPort = 6001
UserName = OMC
Password =
NodeTypeName = cmsc61
2) Check whether the communication between the server which Adapter is running
on and the BAM of the NE is normal.
YÖ 3)
NÖ Configure the network correctly to ensure the normal communication between
Adapter and the BAM.
3) Check whether the user name and the password for Adapter to log in to the BAM
are correct. (The Adapter log contains “User Login success”)
YÖ 4)
NÖ Select the NE icon on the RWS and press <Ctrl+Shift+Alt+F11> to modify the user
name and the password to log in to the BAM.
Note:
z For safety reasons, user name and password are not displayed in the popup window no matter
whether they have been set or not.
z When the user name (log in to the binary BAM) and its password are modified through LocalWS, the
LocalWS will convert them to upper case form. Therefore, while entering the user name and password
on the M2000 RWS by selecting the NE icon and then pressing <Ctrl+Shift+Alt+F11>, make sure that
user name and related password are in upper case.
4) Check whether there is red cross on the NE.

YÖ Contact Huawei technical support engineers.
NÖ 5)
5) End.
4.2.4 Failed to Set Up Connection between M2000 Client and Server
I. Description
The M2000 client fails to connect to the server. The RWS client displays “connection
failure with all servers”. But, the processes of the servers still exist.
4-4
Maintenance Manual
II. Solution

1) Log in to the M2000 server and check whether processes of the servers exist,
using the following command.
$ps –ef|grep m2000
m2000 353 1 0 18:11:44 ? 0:00 /export/home/m2000/bin/switch
m2000 376 375 0 18:11:45 ? 0:00 /export/home/m2000/bin/commonsvrd
m2000 369 342 0 18:11:45 ? 0:00 /export/home/m2000/bin/timesvrd
m2000 398 397 0 18:11:48 ? 0:00 /export/home/m2000/bin/configsvrd
m2000 422 421 0 18:11:50 ? 0:05 /export/home/m2000/bin/alarmsvrd
m2000 435 1 0 18:11:53 ? 0:00 /export/home/m2000/bin/alarmsend
m2000 436 435 0 18:11:53 ? 0:00 /export/home/m2000/bin/alarmsend
m2000 478 476 0 18:11:56 ? 0:00 /export/home/m2000/bin/pmsvrd
m2000 342 1 0 18:11:42 ? 0:00 /export/home/m2000/bin/timesvrd
m2000 501 499 0 18:11:59 ? 0:00 /export/home/m2000/bin/timersvrd
YÖ 3)
NÖ 2).
2) Check whether the process of the Sybase is normal.

The commands are:
#ps -ef | egrep "dataserver|backupserver" | egrep -v "sh|grep"|wc –l
If the output value is 2, it means that the process is normal. Otherwise, reboot the
process of the Sybase server manually.
#/etc/rc2.d/S97sybsvr stop
#/etc/rc2.d/S97sybsvr start
Then reboot the process of the M2000 server.
#/etc/rc2.d/S98m2000svr stop
#/etc/rc2.d/S98m2000svr start
After three to five minutes, check whether the processes of the M2000 server are
normal according to step 1.
If the problem still exists, check the log files under /export/home/m2000/log to see
whether there is any error information. If there are, correct the errors according to the
detailed certain information.
Check whether the problem is solved.
YÖ End.
NÖ Contact Huawei technical support engineers.
4-5
Maintenance Manual
3) Press <F6> on the RWS of the M2000 to see the routing information on the right
corner. Check whether processes of the servers exist (as shown in the figure
below).
YÖ Contact Huawei technical support engineers.

NÖ 4).
4) Log in to the M2000 server as the root user, and reboot the process of the M2000
server.
After three to five minutes, check whether the problem is solved.
YÖ End. Upgrade the M2000 common version to the B03D501 or later versions.
4.2.5 Unable to Bring up the NE Service Console Menu with a Right-click
I. Description
The user can not bring up the NE service console menu with a right click.
II. Solution
1) The user does not have authority to operate the object.

2) The NE service console application is not correctly installed.
3) The current object does not carry correct version information.
4.2.6 IP Address Setting
I. Description
How to set IP address in a newly added or modified object.
4-6
Maintenance Manual
II. Solution
1) Adapter IP
The Adapter’s IP for the current object. If the status of an object is "Communication
interrupted", check if the Adapter IP of the current object is correct.
2) NE IP
If the current object has NE service, input the BAM IP address in the NE IP. If there is a
problem starting NE service, please make sure the BAM IP has been correctly input.
3) BAU Server IP
If IE connection fails to establish when user clicks the billing service menu option of the
MSC object, please make sure the information here is correct.
4) HLR Server IP
When the HLR user data management service program is installed in a maintenance
terminal, the integrated network management system will display the installed IP
information in the drop-down list in HLR server’s IP property settings. User may make
the selection in the list according to his own needs. The integrated network
management system will then decide whether to display the HLR User Data
Management menu according to the user’s choice.
Therefore, when the HLR User Data Management menu is not displayed correctly,
please check the settings here.
4.2.7 Failed to Refresh Configuration Data
I. Analysis

z The BAM user has no authority to query the configuration database.
z The workstation of the adapter is not authorized to query the configuration
database.
z The refreshing operation is not performed.
II. Solution

1) Check whether the NE status and the connection between the clients and the
server are normal.
2) Check whether the NE version and the adapter version are consistent.
3) Check whether the user and workstation are authorized to query the configuration
database.
The workstation must be authorized to system administrator.
4) Manually refresh the NE at the centralized configuration client and observe the
information at the status bar to locate the failure.
4-7
Maintenance Manual
4.2.8 Failed to Set Up Connection between M2000 Client and Alarm Server
I. Description
The M2000 client fails to connect to the alarm server. It is displayed on the RWS that
the connection to the alarm server is interrupted or abnormal.
II. Analysis
When the client fails to connect the alarm server, check whether the alarm server
process is normal and whether the number of alarm records exceeds the limit in the
alarm database.
Note:
When the number of history alarms exceeds the preset value, the M2000 alarm server deletes redundant
history alarms. That is, the M2000 alarm server deletes at most 5000 alarms per type per level once every
half an hour.
When the system generates large amount of alarms owing to upgrade or other reasons, the alarms
reported in half an hour may be more than alarms the system deletes automatically. If this situation lasts,
the history alarms will be over redundant, thus affecting the normal operation of the alarm server process.
III. Solution

1) Verify whether the version of the M2000 common service is B03D501 or earlier.
YÖ 2)
2) Check whether history alarms are over redundant in the M2000 alarm database.
Proceed as follows:
Log in to the M2000 server as m2000.
Execute the following commands to query the history alarm table.
1> use alarmdb
2> go
1> select count(*) from m2000.history /*Check the number of history alarms*/
2> go
-----------
4-8
Maintenance Manual
512345
(1 row affected)
If the number of records is over 500,000, it is recommended to clear all the history
alarms.
If the number of records is small, directly go to step 5.
Confirm whether all the history alarms can be deleted because the deletion is
irretrievable.
Confirm whether to delete all the history alarms.
YÖ 3)
NÖ 4)
3) Clear all the records of history alarms in the M2000 alarm database.
Proceed as follows:
Log in to the M2000 server.
Stop the M2000 server process.
$su
Execute the following commands to clear the history alarm table.
#su – m2000
$isql -Usa -Pserver1234
1> use alarmdb
2> go
1> truncate table m2000.history
2> go
1>exit
Restart the M2000 server process.
$su
Check whether the problem is solved five minutes later.
YÖ End.
NÖ 5)
4) If the deleting of all the history alarms is not permitted, you can delete the history
alarms generated before a specific time, which needs a longer time. To delete
4-9
Maintenance Manual
history alarms generated before a specific time, please execute the following
commands:
Log in to the M2000 server.
Stop the M2000 server process.
$su
Execute the following command to delete history alarms generated before a specific
time.
#su – m2000
1> use alarmdb
2> go
1> set rowcount 5000
2> go
/*Execute the following commands repeatedly until the system does not display “(5000
rows affected)”. */
1> delete from m2000.history where occurtime<"20040301 00:00:00"

2> go
/*The above commands mean all the history alarms generated before 00:00:00 on
March 1, 2004 will be deleted. You may change the time as needed. */
Restart the M2000 server process.
$su
YÖ End.
NÖ 5)
5) Check whether event alarms are over redundant in the M2000 alarm database.
Proceed as follows:
Execute the following commands to query the event alarm table.
1> use alarmdb
2> go
4-10
Maintenance Manual
1> select count(*) from m2000.event /*Check the number of event alarms*/
2> go
512345
(1 row affected)
If the number of records is more than 500,000, it is recommended to clear all the event
alarms.
If the number is small, directly go to step 8.
Confirm whether all the event alarms can be deleted before deleting them. (This
operation is irretrievable. )
YÖ 6)
NÖ 7)
6) Clear all the event alarms in the M2000 alarm database.

Change the table name m2000.history to m2000.event and proceed as the step 3
describes.
YÖ End.
NÖ 8)
7) If the deleting of all the event alarms is not permitted, you can delete the event
alarms generated before a specific time. However, it will take comparatively longer
time.
Change the table name m2000.history to m2000.event and proceed as the step 4
describes.
8) Proceed with the following operations

Execute the following commands to query the number of alarm records.
1> use alarmdb
2> go
1> select count(*) from m2000.history /*Check the number of history alarms*/
2> go
1> select count(*) from m2000.fault /*Check the number of fault alarms*/
2> go
4-11
Maintenance Manual
1>select count(*) from m2000.event /*Check the number of event alarms*/

2>go
1>exit
Contact Huawei technical support engineers and feed back the returned result of the
above commands and the log files under the directory /export/home/m2000/log.
4.2.9 Failed to Report Alarm Data
I. Analysis

z The server does not report alarms.
z The alarm server is abnormal.
z The database is abnormal.
II. Solution
To handle this problem, check whether:

z The NE version is consistent with the adapter version.
z There is certain alarm on LMT of host.
z Alarms are shielded.
z Alarms are repeated alarms.
z Alarms are newly added.
z The server works normally if all NEs cannot report alarms.
z The NE adapter works normally if all alarms of a certain NE cannot be reported.
4.2.10 Low Query Execution Speed
I. Description
While querying or browsing command is being executed, the system is in engaged for a
fairly long time. If user switches to other programs and then switches back, the alarm
console seems not responding at all.
II. Analysis
1) There are too many records in the database, and it will take long time for the query
to complete.
2) Or if the network transmission speed is slow at the moment, the query will also
take a long time to finish. In such cases, the program may still be running and will
start responding in a while.
III. Solution
Check if the network connection is Ok.
4-12
Maintenance Manual
4.2.11 Message of "Printing. Cannot be closed."
I. Description
When user tries to shut down the centralized fault management system, a message
pops up saying "Printing. Cannot be closed." or "Alarm system is real-printing, please
finish real-printing before close the real-time browse form." -- the system will not shut
down.
II. Analysis
Probably the program is printing query or browsing alarm records, or the real-time
printing switch is on -- in such cases, the program can not be shut down.
III. Solution
If deciding to exit the alarm console, switch the real-time printing off or wait until current
query or browsing printing process completes.
4.2.12 Failed to Register Performance Task
I. Analysis

z The task object does not exist.
z The number of the registered objects exceeds the processing capability of the
host.
z The number of the registered tasks exceeds the limit of the host.
II. Solution

1) Check whether the NE status and the connection between the clients and the
server are normal.
2) Check whether the NE version and the adapter version are consistent.
3) Check whether the configuration data is refreshed.
You can add scheduled refreshing task at the centralized configuration console to
ensure timely refreshing.
4) Check whether the number of objects exceeds the processing capability of the
host. For example, the GMSC can process only seven objects once.
5) Check whether all cds files under “bin/PM_NWS_SysTable” of M2000 clients are
deleted after upgrading and restarting the M2000 server. Deleting the files can
ensure the clients to obtain the latest performance data from the server.
6) Check whether tasks can be successfully registered at NE LMT.
4-13
Maintenance Manual
4.2.13 Failed to Report Results of Performance Tasks
I. Analysis

z The version is mismatched.
z There is no traffic data reported from the BAM.
z The M2000 server is not assigned the relevant authority.
z The performance server works abnormally.
z The database is abnormal.
II. Solution

1) Check whether the software version matches.
2) Check whether no task result of this NE is reported, or all task results stop being
reported at a certain moment.
YÖ 3)
NÖ 10)
3) Check whether the server where the Adapter is running on is assigned with
relevant authority on the BAM. Execute the commands LST WS and LST OP on
the BAM. The authority information is obtained.
YÖ 5)
NÖ 4)
4) Assign the server with relevant authority on the BAM and reconnect the Adapter
and the BAM by performing the following operations:
Add the administrator authority to the IP address of the server where the Adapter
resides on the BAM through the MML command:
ADD WS:WS="m2000svr", IP="xxx.xxx.xxx.xxx".
(xxx.xxx.xxx.xxx indicates the IP address of the server where the Adapter is running on)
SET WSCG: WS="m2000server", CG=G_SYS-1.
Restart the corresponding adapter on the M2000 server
On completion of the above operations, observe for 2-3 hours to see whether the
performance task result is reported.
YÖ End
NÖ 5)
5) Check whether the NE type is cBSC.
4-14
Maintenance Manual
YÖ 6)
NÖ 7)
6) Check whether the 6002 port is connected well on the cBSC BAM by executing the
command netstat -n. It is possible that the maintenance port 6000 between the
cBSS BAM and Adapter is connected well, while the port 6002 is disconnected.
Because of disconnection, no traffic data and the real-time alarm are reported
through the 6001 port.
To recover the connection of the port 6002, you need to restart the Adapter. Perform the
operation below on the M2000 server where the Adapter is located:
$ps -ef|grep cbssadapter
adapter 21718 2237 0 14:39:49 ? 0:01
/export/home/adapter/cbssadapter/V100R005B03D101/bin/adapterd 10.129.200.108
$kill 21718
After the above operation, check on the cBSS BAM whether the Adapter is connected
to the BAM through port 6002. Observe for 2-3 hours to see whether the performance
task result has been reported.
YÖ End
NÖ 10)
7) Check whether the NE type is MSC61.

YÖ 8)
NÖ 10)
8) On the BAM, query whether the authority group (G_2) for traffic measurement has
been added to “PRE QRST” by using the command LST CCG: CG=G_2.
YÖ 10)
NÖ 9)
9) Log on to the MSC61 BAM as the super user and then execute the command:
ADD CCG: CG=G_2, CN="PRE QRST";. If the operation succeeds, observe for
2-3 hours to see whether the performance task result is reported.
YÖ End
NÖ 10)
10) Query whether the running status of the task is activated on the performance
Client. If other statuses or failure causes are returned, handle it as below:
z “No Task”: Re-register the task.
4-15
Maintenance Manual
z “No Objects” or “Objects Have No Response”: It indicates that the objects have
changed due to the configuration. It is necessary to re-register the task or delete
the original objects through [Modify Objects] and then add new objects.
z If the returned task status is “Suspended”, then activate the task.
On completion of the above operation, observe for 2-3 hours to see whether the
performance task result has been reported.
YÖ End.
NÖ 11)
11) Check on the BAM whether the relevant task result has been reported normally.
YÖ 12)
NÖ Try to find out the reason or contact technical support department of Huawei.
12) Check the running status of the performance server (pmsvrd) by using the
command “ps”:
$ps -ef|grep pmsvrd
m2000 26847 1 0 Sep 11 ? 0:00 monsvrd /export/home/m2000/bin/pmsvrd
If the start time of pmsvrd process is far from that of the monsvrd process, and the start
time of pmsvrd is quite close to the current time of the server, it indicates that pmsvrd
may be restarted frequently.
Check whether the process of the performance server is normal.
YÖ 14)
NÖ 13)
13) For M2000 versions earlier than M2000 (COMMON) V100R005B03D501, if the
bootscript ($/etc/rc2.d/S98m2000svr start) is executed repeatedly, the M2000
server may be restarted frequently. This problem can be solved through the
following steps:
$/etc/rc2.d/S98m2000svr stop
$/etc/rc2.d/S98m2000svr start
YÖ End
NÖ 14)
14) Check whether the performance database is normal.
4-16
Maintenance Manual
Log on to the M2000 server as the m2000 user and then perform the following
operations to check the database.
$su - m2000
1>sp_who
2>go
fid spid status loginame origname hostname blk dbname cmd
0 16 sleeping sa sa yshai 0 pmdb LOG SUSPEND
If "pmdb LOG SUSPEND” is returned, it indicates no space is available for the log.
Continue the following operation and refer to “4.2.14 Solution to Log Space Full”.
1>sp_helpdb pmdb
2>go
name db_size owner dbid created status
pmdb 4096.0 MB sa 10 Aug 25, 2003 ddl in tran, allow nulls by default
(1 row affected)
device_fragments size usage free kbytes

data_dev 2048.0 MB data only 2093056
log_dev 2048.0 MB log only 123392
device segment
data_dev default
data_dev system
log_dev logsegment
(return status = 0)
On completion of the above operation, if there is little space available for log in the
PMDB (less than 200M), it can be confirmed that the log space is full. Refer to “4.2.14
Solution to Log Space Full”. If there is little space available for data in the PMDB (less
than 200), it can be confirmed that the PMDB is full. Then delete some data. If no
problem is found in the above operation, continue the following operation:
1>sp_lock
2>go
The class column will display the cursor name for locks associated with a cursor for the current
user and the cursor id for other users.
fid spid locktype table_id page row dbname class context

0 15 Sh_page 1260531524 8462 0 pmdb Non Cursor Lock
0 16 Ex_table 1292531638 0 0 pmdb Non Cursor Lock
Fam dur
(2 rows affected)
(return status = 0)
4-17
Maintenance Manual
After the above operation, if the page or the table is locked in the PMDB, refer to “4.2.15
Solution to Locked Database” described below.
YÖ End.
NÖ Contact technical support engineers of Huawei.
4.2.14 Solution to Log Space Full
Clear the log in the database through the following command:

1>dump transaction pmdb with no_log
2>go
4.2.15 Solution to Locked Database
There are two solutions:

z If the lock is caused by the insufficient log space, refer to “4.2.14 Solution to Log
Space Full” described in the above.
z If the lock is caused by the access conflict between NWS, SVR or the timing
clearance program, handle it as below:
1) Disable the conflict process through the command KILL.
1>kill 15 /*15 is the process ID (SPID), refer to the above example*/
2>go
1>kill 16 /*16 is the process ID (SPID), refer to the above example*/
2>go
2) Restart the performance server.
$su - m2000
$cd bin
$ps -ef|grep pmsvrd
m2000 10200 1 0 11:56:35 ? 0:00 monsvrd /export/home/m2000/bin/pmsvrd
$kill -9 10201 10200

$monsvrd /export/home/m2000/bin/pmsvrd
4-18
Maintenance Manual
4.2.16 Sybase System Installation Aborted
I. Description
The installation is aborted when configuring the Sybase using command "srvbuild".
II. Analysis
1) The user did not log on as a root user;

2) The IP address in file "/etc/hosts" does not match that of the current host.
III. Solution
1) Log on as a root user;

# su - root
# xhost +hostname
# su - sybase
$ cd /export/home/sybase/bin
$ srvbuild
2) Modify the host IP address in file "/etc/hosts" as that of the current host.
4.2.17 Failed to Display Process Status
I. Description
The process status is not displayed when the command "ps – ef" is executed.
II. Analysis
When installing sybase with raw device mode, the user uninstalled the "/proc" by
mistake.
III. Solution
Use the command "mount" to load the "/proc".

$mount /proc
4.2.18 Failed to Log in to Sybase System
I. Description
Fails to enter Sybase environment using the command "isql -Usa", or fails to start
Sybase process.
II. Analysis
DSQUERY variants have not been set in environment variant settings.
4-19
Maintenance Manual
III. Solution
1) Edit file ".profile" and add in "DSQUERY=sybserver". There is no space before or

after the equal mark.
2) Start Sybase process.
Please refer to “5.2.1 Starting Sybase Processes”.
4.2.19 Failed to Start Sybase Automatically
I. Description
When the system starts, the Sybase database does not start automatically.
II. Analysis
The auto-start file "/etc/rc2.d/S97sybsvr" has not been created.
III. Solution
1) Log on as a root user and create auto-start file "/etc/rc2.d/S97sybsvr":

su - sybase -c "/install/startserver \
-f /install/RUN_sybserver \
-f /install/RUN_sybserver_back"
sleep 15
2) Modify auto-start file properties:
chmod 700 /etc/rc2.d/S97sybsvr
4.2.20 Failed to Building Database
I. Description
The database installation fails.
II. Analysis
The device name created during the Sybase database installation process does not
match that in the installation script.
III. Solution
1) Delete the error device by executing the command sp_dropdevice.

2) Create equipment name as: "data_dev" and "log_dev".
4.2.21 Failed to Install M2000 Application Software
I. Description
The installation is aborted when executing the command "pkgadd".
4-20
Maintenance Manual
II. Analysis
The user did not install software as a root user or had not deleted the M2000 software
installed previously.
III. Solution
Switch to root user or uninstall the M2000 software package.

To uninstall M2000 application software, proceed as follows:
1) Uninstall M2000 server software.
#pkgrm HWM2000
During uninstalling, answer all questions with “yes”.
2) Delete the directory.
#rm -r HWM2000
4.2.22 Failed to Copy File
I. Description
The installation process halts while copying files, a dialogue box of file copy error pops
up. If user presses OK, the installtion process will terminate.
II. Analysis
The files being copied are trying to overwrite the files being used by the system or the
dynamic link library loaded by the system -- this will lead to file copy failure.
III. Solution
1) Close all the other programs currently running, run the setup program again and
see if the error sustains.
YÖ 2)
NÖ 3)
2) Reboot the computer (so as not to load the dynamic link library), and run the setup
program again and see if the error sustains.
YÖ Contact the technical support personnel for help.
NÖ 3)
3) End
4-21
Maintenance Manual
iManager M2000 Chapter 5 Process Operations
Chapter 5 Process Operations
All the processes described in “1.4 Processes” start upon startup of the M2000 server.
In special cases, you can stop or restart a process using the commands provided by the
operating system.
5.1 Service Processes

Service process operation involves how to start and stop the overall service processes
or a single process.
5.1.1 Starting All Service Processes
You can log in as root and start M2000 server processes using the following command:
Or:
#/etc/rc2.d/S98m2000svr restart
5.1.2 Stopping All Service Processes
You can log in as root and stop M2000 server processes using the following command:
5.1.3 Starting Single Service Process
For a daemon process such as switch, you can log in as m2000 and start it using the
following command:
$/export/home/m2000/bin/switch
For a process that needs to be monitored by monsvrd, you can start it using the
following command:
$cd; cd bin; monsvrd /export/home/m2000/bin/timersvrd
5.1.4 Stopping Single Service Process
You can log in as m2000 and stop a process using the command kill directly. But as an
exception, to stop the timervrd,
1) Query its process number using the command:
$ ps -ef|grep timersvrd|grep -v grep
m2000 494 1 0 Aug 11 ? 0:00 monsvrd
/export/home/m2000/bin/timersvrd
5-1
Maintenance Manual
m2000 496 494 0 Aug 11 ? 0:01 /export/home/m2000/bin/timersvrd

2) Execute the following command to stop processes 496 and 494:
$kill -9 496 494
Note:
To prevent process disorder, avoid starting or stopping a single process. Instead, always start or stop the
all the M2000 server processes following methods described in 5.1.1 and 5.1.2 .
5.2 Sybase Processes

The Sybase process operation involves how to start and stop Sybase processes.
5.2.1 Starting Sybase Processes
You can log in as root and start the Sybase process using the command:
#/etc/rc2.d/S97sybsvr start
Or:
#/etc/rc2.d/S97sybsvr restart
Alternatively, you can log in as sybase and execute the flowing command:
$ cd;cd install; ./startserver -f RUN_sybserver -f RUN_sybserver_back
5.2.2 Stopping Sybase Processes
You can log in as m2000 or sybase and stop the Sybase process using the following
command:
1> shutdown SYB_BACKUP
2> go
Backup Server: 3.48.1.1: The Backup Server will go down immediately.
Terminating sessions.
1> shutdown
2> go
Server SHUTDOWN by request.
The SQL Server is terminating this process.
CT-LIBRARY error:
ct_results(): network packet layer: internal net library error:
Net-Library operation terminated due to disconnect
5-2
Maintenance Manual
CT-LIBRARY error:
ct_cancel(): network packet layer: internal net library error:
Net-Library operation terminated due to disconnect
It is not recommended you stop the Sybase processes using one of the following
commands:
z #/etc/rc2.d/S97sybsvr stop
z kill
5-3
Maintenance Manual
iManager M2000 Chapter 6 Hardware Maintenance
Chapter 6 Hardware Maintenance
This chapter describes the maintenance tasks that the System Administrator performs.
6.1 Shutting Down Sun Server

Following are instructions to shut down the whole system in various hardware
environments, including power-off of all power supplies and boards.
6.1.1 Shutting Down SunFire 4800
To shut down the SunFire 4800, do as follows:

1) Log in to the server as root.
2) Shut down the server using the following command:
# scshutdown -i0 -g0 –y /*For one-node system, execute shutdown -i0 -g0 –y */
The two SunFire 4800 servers are in the OK status.
3) Log in to the administration workstation as root.
4) Telnet to the system controller board of the Sun Fire server using the following
command:
# telnet sc_alias
The following is displayed:
Escape character is '^]'.
System Controller '<schostname>':
Type 0 for Platform Shell.
Type 1 for domain A console.
Type 2 for domain B console.
Type 3 for domain C console.
Type 4 for domain D console
5) Enter 1 to select domain A for platform by doing the following:
{2} ok
6) Press <Ctrl + ]> to go back to the platform shell by doing the following:
telnet>
View the prompt using the following command:

send break
6-1
Maintenance Manual
Domain Shell for Domain A - <ISNM_server_hostname>

<schostname>:A>
System Administration Guide for CNM 1.1, PNM 3.0 and RNM 1.2
7) Disconnect the connection using the following command:
disc
Connection closed.
<schostname>:SC>
8) Query the current statuses of the “virtual” key switches using the following
command:
showkeyswitch
Domain A main switch is: on
Domain B main switch is: off
Domain C main switch is: off
Domain D main switch is: off
9) Turn off the main switch for domain A using the following command:
setkeyswitch -d a off
10) Power off all components using the following command:
poweroff all
At this point, the system is powered off; only the system controller board and media tray
are running.
11) Turn off the physical power supply key switches located on the back of the
machine to power off the controller itself.
12) Power off the T3 disk array.
To continue the shutdown procedure, see “6.3 Powering On or Off T3 ”.
6.1.2 Shutting Down Sun V880/Netra 20
To shut down other Sun Servers, do as follows:

1) Log in to the server as root.
2) Shut down the server using the following command:
# shutdown -i0 -g0 -y
{0} ok
3) For the V880 server, press and hold the button on the front panel of the server for
approximately five seconds.
For other servers, turn off the physical power supply key switches on the back of the
machines. Power off the T3 disk array.
6-2
Maintenance Manual
To continue the shutdown procedure, see “6.3 Powering On or Off T3 ”.
6.2 Powering On Sun Server

Following are instructions to power on the whole system in various hardware
environments.
6.2.1 Powering On SunFire 4800
To power on the SunFire 4800, do as follows:

1) Make sure that all disk arrays are powered on.
For more information, see “6.3 Powering On or Off T3 ”.
2) Make sure that the D240 is powered on.
3) Power on the server.
The LED on the controller board is on.
4) Log in to the administrator workstation as root.
5) Telnet to the System Controller board of the SunFire 4800 using the following
command:
# telnet sc_alias
Escape character is ‘^]’.
System Controller ‘<schostname>’:
Type 0 for Platform Shell.
Type 1 for domain A console.
Type 2 for domain B console.
Type 3 for domain C console.
Type 4 for domain D console
Enter 0 to select the Platform Shell.
6) Power on all the modules using the following command:
poweron all
7) Switch to domain A using the following command:
console –d a
Connected to Domain A
Domain Shell for Domain A
<schostname>:A>
8) Set the key switch to "on" using the following command:
setkeyswitch on
This step takes several minutes.
6-3
Maintenance Manual

Powering boards on ...
Testing CPU Boards ...
………
Sun Fire x800
{0} ok
9) Boot the server using the following command:
boot
………
Trapdistributor starting...
The system is ready.
<hostname> console login:
10) Press <Ctrl + ]> to exit the login prompt.
telnet>
11) Send break using the following command:
send brk
<schostname>:A>
You are now in the shell of Domain A.

12) Go back to the System Controller shell using the following command:
disc
At this point, press <Enter> twice.
connection closed
<schostname>:SC>
You are now in the System Controller shell.

13) Exit (return) to the original session using the following command:
disc
Connection closed by foreign host.
Note:
For dual-node system, perform step 3 to 13 for the secondary server.
6-4
Maintenance Manual
6.2.2 Powering On Sun V880/Netra 20
To power on Sun V880/Netra 20, do as follows:

1) Make sure that all disk arrays are powered on.
For more information, see “6.3 Powering On or Off T3 ”.
2) For Sun V880, press the button on the front panel of the server.
For Sun Netra 20, turn on the physical power supply switches on the lower back of the
machine.
The system reboots itself automatically. The following is displayed:
{0} ok
3) Boot the system using the following command:
boot
6.3 Powering On or Off T3 Disk Array

The following describes how to power on or off T3 disk array.
6.3.1 Powering On T3 Disk Array
Always power on the disk array before booting the host server.
To power on the disk array, press the power button on each unit.
LEDs of all units turn green.
6.3.2 Powering Off T3 Disk Array
You need to power off the disk array only when:

z You re-configure the hardware.
z You change the location of the system.
z You replace the parts.
z An emergency such as a threat of flooding occurs.
Caution
This following procedure will power off the disk array and other arrays connected to it.
To power off the T3 disk array, proceed as follows:

1) Make sure the related disk arrays are shut down. Alternatively, you can un-mount
the volumes on the data host before powering off the array.
6-5
Maintenance Manual
2) Ensure that there are no I/O operations on the data path between the host and the
array.
3) Log in to the administration workstation as root.
4) Proceed as follows for each array:
Telnet to the array as user root:
# telnet T3_array_alias
5) Shut down the array:
:/:<1> shutdown
Shutdown the system, are you sure? [N]:
6) Enter “y”.
7) Press the power button once on each power and cooling unit to turn the switch off.
6.4 Monitoring T3 Disk Array

You can monitor the T3 disk array in the following two ways:
z Using pSOSystem commands
z Using the Component Manager GUI
6.4.1 Using pSOSystem Commands to Monitor T3 Disk Array
To monitor the T3 disk array, do as follows:

1) Telnet to the disk array you want to maintain using the following command:
# telnet T3_name
Example: # telnet t3e1
2) Log on as root using the following command:
root
Password:
3) Provide the password of “T3 name”:
<T3_name_root_passwd>
4) Check the information as needed:
z To list the FRU information, use the following command:
:/:<1>fru list
The following is displayed (specific output may differ):
ID TYPE VENDOR MODEL REVISION SERIAL
------ ----------------- ----------- -----------
u1ctr controller card SLR-MI 375-0084-02- 0210 029554
6-6
Maintenance Manual
u2ctr controller card SLR-MI 375-0084-02- 0210 029134

u1d1 disk drive SEAGATE ST336704FSUN A726 3CD1J91N
u1d2 disk drive SEAGATE ST336704FSUN A726 3CD1JBMV
…..
Check the status of the fru:
z To check the status of the FRU, use the following command:
:/:<2>fru stat
CTLR STATUS STATE ROLE PARTNER TEMP
------ ------- ---------- ---------- ------------- -------
u1ctr ready enabled master u2ctr 29.5
u2ctr ready enabled alt master u1ctr 30.5
DISK STATUS STATE ROLE PORT1 PORT2 TEMP VOLUME

------ -------- ---------- --------- --------- ------- ---------
u1d1 ready enabled data disk ready ready 30 v0
u1d2 ready enabled data disk ready ready 26 v0
LOOP STATUS STATE MODE CABLE1 CABLE2 TEMP

------ ----------- ---------- --------- ----------- ------------
u2l1 ready enabled master installed - 23.5
….
POWER STATUS STATE SOURCE OUTPUT BATTERY TEMP FAN1 FAN2
------ ------- --------- ------ ------ ------- -------- ---------
u1pcu1 ready enabled line normal fault normal normal normal
z To list the volumes, use the following command:
:/:<4>vol list
volume capacity raid data standby
v0 269.782 GB 5 u1d1-9 none
z To check the status of the volumes, use the following command:
:/:<3>vol stat
v0 u1d1 u1d2
mounted 0 0
v1 u2d1 u2d2
mounted 0 0
z To display the mode of the volumes, use the following command:
:/:<13>vol mode
6-7
Maintenance Manual
volume mounted cache mirror

v0 yes writebehind on
v1 yes writebehind on
z To list the system information, use the following command:
:/:<21>sys list
blocksize : 64k
cache : auto
mirror : auto
mp_support : rw
rd_ahead : on
recon_rate : med
sys memsize : 128 MBytes
cache memsize : 1024 Mbytes
z To display the system status, use the following command:
:/:<22>sys stat
Unit State Role Partner
----- ------ ------ -------
1 ONLINE Master 2
2 ONLINE AlterM 1
z To display the general information about the array, use the following command:
:/:<23>set
bootmode auto
bootdelay 3
sn 029554
ip 192.168.8.5
netmask 255.255.255.0
gateway 0.0.0.0
tftphost 0.0.0.0
hostname t3-1
z To display the ports on the system, use the following command:
:/:<27>port list
port targetid addr_type status host wwn
u1p1 1 hard online sun 50020f2300002ccf
6-8
Maintenance Manual
6.4.2 Using Manager GUI to Monitor T3 Disk Array
For information on how to use the graphical user interface (GUI), see Component
Manager documentation provided by Sun Microsystems, Inc.
6-9
Maintenance Manual
iManager M2000 Appendix A Handling Common Network Faults
Appendix A Handling Common Network Faults
This appendix introduces network faults analysis and fault location methods.
Faults discussed in this appendix are classified into:

z Network faults, including faults detected in the M2000 Server, back administration
module (BAM), and work station (WS).
z Debugging faults of routers, including faults detected in the physical layer, link
layer, network layer, and Ethernet.
A.1 Common Network Faults
This section describes the common network faults.
A.1.1 Failure of WS to Connect with M2000 Server
I. Fault Description
The WS fails to connect with the M2000 Server, and M2000 Server cannot be pinged
on the WS.
II. Fault Analysis
To locate the faults, check the M2000 Server, the terminal, and network cables.
z Checking the M2000 Server
To check the M2000 Server,
--Log in as root and execute the command "ifconfig -a" to check the setting of the
IP address.
--Execute the command "ping 129.9.10.10" (suppose 129.9.10.10 is the IP

address of the Server).
If the server can be pinged, it indicates the network adapter and the IP address of
the M2000 are set correctly. Otherwise, check and reset the IP address of the
M2000 Server.
z Checking the terminal
To check the terminal,
--Select [Start/Run].
A-1
Maintenance Manual
--Execute the command ping 129.9.200.51 (suppose 129.9.200.51 is the IP

address of the terminal).
If the terminal can be pinged, it indicates the network adapter and the IP address
of the terminal are set correctly. Otherwise, check the relevant settings of the
network adapter and the IP address.
z Checking whether the LAN Switch between the terminal and the M2000 Server
works normally.
Perform the following,
--Check indicators to see whether the connection among other workstations

through the LAN Switch is normal.
--Replace the network cable between the workstation and the M2000 Server to
remove the fault caused by the network cable.
A.1.2 Failure of WS in Far-end NMC to Connect with M2000 Server
The WS of the far-end network management center (NMC) fails to connect with the
M2000 Server. The Ethernet 0 interface of the M2000 LAN router can be pinged at the
far end, but the IP address of the M2000 server cannot be pinged.
II. Fault Analysis
The E0 interface of the M2000 LAN router can be pinged at the far end, which indicates
that the far-end network and the near-end router are operating normally. The IP
address of the M2000 Server cannot be pinged, which indicates that the gateway at the
M2000 Server is not properly set. Add the gateway at the M2000 Server.
Suppose the IP address of the E0 interface of the router is 129.9.10.11, and perform the
following:
1) Execute the following commands as root on the M2000 Server:
# route add default
# route add 129.9.0.0 129.9.10.11

2) Add the above commands to the file /etc/rc2.d/S97sybsvr when the connection is
normal.
A-2
Maintenance Manual
Note:
The purpose of adding the above commands is to add the gateway to the file /etc/rc2.d/S97sybsvr so that
the gateway can be set automatically when the server restarts. Otherwise, you need to enter the above
commands manually.
A.1.3 Failure to Log in to M2000 Server
The following command is executed on the WS of the far-end NMC.
$isql –Usa –Pserver1234 -Ssybwf
Note:
z U: Username. A user can specify a registration name.
z P: Password. A user can specify the current password for the SQL Server.
z S: Server. The name of the SQL Server connected to the WS is specified by a user.
It is failed to log in to the M2000 Server. The system prompts that the connection to the
Client database fails. If the Sybase database is shut down and restarted, the
connection is normal.
II. Fault Analysis
To locate the fault, proceed as follows:

1) Ping the IP address of the M2000 Server at the far end.
If the server can be pinged, it shows that the connection between the far end and
the M2000 Server is normal.
2) Run $isql -Usa -Pserver1234 on the M2000 Server.
If the connection can be established normally, it shows that the Sybase database
runs normally.
3) Shut down the Sybase database and restart it.
The Sybase Client at the far end is connected with the M2000 Server database
through a virtual IP address. The self-start file is stored in the file
/etc/rc2.d/S99dtlogin when the virtual IP address is set. When the server is started,
the system invokes the file /etc.rc2.S97sybsvr to start the Sybase, and then the file
A-3
Maintenance Manual
/etc/rc2.d/S99dtlogin to set the virtual IP address. Consequently, the system

cannot identify the Client IP address used when the Sybase is started.
III. Troubleshooting
Set the relevant virtual IP in the file /etc/rc2.d/S99dtlogin before starting the Sybase.
For instance, the file S97sybsvr can be set as follows (the first three lines are the
settings of relevant virtual IP):
ifconfig hme0:1 inet 134.38.19.77 netmask 255.255.255.0 up
route add default 129.9.200.31
route add 134.32.0.0 134.38.19.65
su - sybase -c "/install/startserver \
-f /install/RUN_sybserver \
-f /install/RUN_sybserver_back"
sleep 20
A.1.4 Failure of BAM to Connect with WS
The WS fails to connect with the BAM. It fails to ping the IP address of BAM on the WS.
II. Fault Analysis
Generally, you must check the network adapter setting, network cable, and LAN
Switch.
1) Check the relevant settings of the network adapter and the IP address.
Click [Start/RUN] on the BAM to execute the command "ping 129.9.200.7"
(suppose 129.9.200.7 is the IP address of the BAM).
If the IP address can be pinged, it shows the settings of the BAM network adapter
and the IP address are correct.
2) Check whether the LAN Switch that connects to the BAM is working normally.
Check indicators to see whether the connection among other workstations through
the LAN Switch is normal. Replace the network cable between the BAM and the
LAN Switch to remove the fault caused by network cable.
3) Check relevant settings of the network adapter.
A-4
Maintenance Manual
a) Check whether the network adapter is normal in [Control

Panel/System/Network Adapter].
b) Select the network adapter attributes to check whether the network adapter
resources conflict with each other and whether the interruption of network
adapters conflicts with I/O address.
If there is a conflict, use the driver disk of the network adapter to run the installation
program of the network adapter for diagnosis and modification.
For instance, for the 3COM network adapter,
a) Run 3c90xcfg.exe on the installation disk in the DOS mode and enter the VIEW
menu to check the original settings.
b) Select the INSTALL menu to change the relevant settings or check the network
adapter.
c) Save the changes and exit
d) Make the relevant settings in [Control Panel/Network] of Windows and install

the relevant TCP/IP.
A.2 Common Faults in the Debugging of Routers
This section describes faults during debugging of routers.
A.2.1 Introduction to Router
A router is a piece of special computer equipment used for network interconnection. It

operates on the third layer (network layer) of the open system interconnect (OSI)
reference model. It is responsible for finding the correct path for the received messages
and forwarding them.
A router must have the following features:

z Having two or more interfaces to connect with different networks.
z Being able to implement the protocols, at least, from the network layer, to the data
link layer, and then to the network layer, to locate faults step by step.
z Supporting at least two sub-network protocols for interconnection of different
sub-networks.
z Having the functions of storage, forwarding, and routing to realize rate matching
and routing.
z Having a group of route protocols, including intra-domain and inter-domain routing
protocols.
A-5
Maintenance Manual
A.2.2 Faults of Physical Layer
The following faults occur at the physical layer:

z The state of the physical port is always DOWN.
Execute the command display port to confirm it.
z The state of the physical port is UP. A large amount of packets are lost when the
peer port is pinged.
Execute the command display port to confirm it.
II. Fault Analysis
When a port is DOWN, there may be two kinds of states:

z The port is shutdown.
The system prompts that port (such as serial number) is administratively down,
and line protocol is down.
z The port is not activated or the state of the physical layer is not changed to up.
The system prompts that port (such as serial number) is down, and line protocol is
down.
Loss of packets is caused by the fault of line clocks. This fault generally occurs on
the private line of a WAN port.
Table A-1 lists causes and troubleshooting procedures of faults.
Table A-1 Cause and troubleshooting procedure
Cause Troubleshooting
For the first case, you can active the port by executing the command undo
shutdown.
Port is shut down. For the second case, check whether the states of the DTR, DSR, RTS, CTS,
and DCD signals at the lower layer are all up by executing the command
display port. If not, it indicates that the physical link between the DTE and DCE
is faulty. Check the connection of cables.
Packet loss is Invert the transmit-clock on the port connected by the private line at both ends
serious. by executing the command invert transmit-clock.
A-6
Maintenance Manual
Note:
Meanings of the above five signals are as follows:
z DTR: Signal of data terminal equipment (DTE) is ready (input signal).
z DSR: Signal of data connection equipment (DCE) is ready (output signal).
z RTS: Request transmission signal (input signal).
z CTS: Clear transmission signal (output signal).
z DCD: Data carrier detection signal (output signal).
By default, the Quidway router detects the above five signals. When the asynchronous port transmits data,
the router automatically detects the CTS signal. If there is a CTS signal, the data is transmitted normally. If
there is no CTS signal, the data transmission is stopped. You can deactivate this function by setting the
relevant parameters of the serial port executing the following command:
[Quidway-Serial0]#flowcontrol normal
If the flow control mode of the asynchronous serial port is set to normal, the router does not detect the CTS
signal and the data is transmitted directly at the port. In this case, if transmission error occurs, the system
automatically transmits the data again.
DTR, DSR, and DCD signals have the level detection function of the serial port, that is, the system detects
whether the serial port is connected to external cables and detects the DCD signal. The system considers
that the serial port is in UP status only when this signal is valid. Otherwise, it is in DOWN status. You can
deactivate this function by executing the following command:
[Quidway-Serial0]#undo detect dsr-dtr
Caution:
z For the WAN port, the router is equipped with a variety of interface cables such as V.24 and V.35, and
the DTE and DCE. Check whether the WAN port of the router works in the synchronous or
asynchronous mode. If it is in asynchronous mode, check the setting of the baud rate. If it is in
synchronous DCE mode, the clock is generated by the router. Then check the clock rate and the clock
mode.
z For the Ethernet port, check whether the connection of the Ethernet is proper. If the HUB or the LAN
Switch is used to connect the Ethernet, check whether the Ethernet ports of the tester and the router
displayed by the indicators on the HUB or the LAN Switch are normal. Two operational modes
including full-duplex and half-duplex are defined in 10Base-T Standard. When a shared HUB is used,
the operational mode must be in the half-duplex mode. When a switched Switch is used, the operation
can be in the full-duplex mode if the full-duplex mode is set on the switch.
z The DTE and DCE mentioned here differ from those of the physical interface. The DTE here refers to
user equipment such as router, and the DCE refers to equipment such as switch. Routers can also be
used as DCE.
A-7
Maintenance Manual
IV. Solution to Common Problems
Table A-2 lists solutions to some common problems.
Table A-2 Solutions to common problems
Description Analysis Solution

This may be because the clock of lines is
non-synchronous, thus causing routers on
both ends of a line not to transmit and receive Invert the transmit-clock
After two 2501 are
signals synchronously. After the on the serial ports
connected, a large amount
transmit-clock is inverted on the interface, the connected to the private
of packets are lost when
clock becomes normal. line at both ends by
the two opposite ends ping
executing the command
each other. If the fault still exists after the inversion, and Invert transmit-clock.
the configuration is correct, you need to check
connection of cables.
When checking the status
of serial ports of a router,
you find the physical port is
DOWN and statuses of the Both DTR and RTS signals are sent from DTE (data terminal). It may be
following signals are as the poor connection of DTE equipment that causes this problem. Check
follows: whether the DTE equipment is correctly connected and whether cables
and lines are faulty.
DCD=UP DTR=DOWN
DSR=UP RTS=DOWN
CTS=UP
The DB9 (25) connector of the cable on the configuration port is DCE
Distinguish the cable on
connector, and that of the cable on the standby port is DTE connector.
the configuration port from
During the configuration of the router, the router is regarded as DCE, and
the cable on the standby
it is regarded as DTE when connected to the MODEM through the AUX
port of the Quidway router.
port.
A.2.3 Faults of Link Layer
The following faults occur at the link layer:

z The physical port is UP and the protocol is DOWN.
z The physical port is UP and the protocol is UP, but the opposite port cannot be
pinged.
z The physical port is UP and the protocol is UP, but many packets are lost when the
data traffic is large. The problem usually occurs at the Ethernet interface.
Execute the command display port to confirm the faults.
A-8
Maintenance Manual
II. Fault Analysis
The possible causes are as follows:

z The port is active, but the link negotiation fails.
The system prompts that the port (such as serial number) is up, but line protocol is
down.
z The address mapping of the link layer or the operational mode is incorrect.
z The format of frames at the link layer is incorrect.
III. Fault Location Procedure
To locate the fault, check whether

z The protocol is correct (such as PPP, X.25, and FR).
z The operational mode is correct (DCE and DTE).
z The frame format of the link layer is correct (X.25, FR, and Ethernet).
z The address mapping of the link layer is correct (when X.25 and FR protocols are
encapsulated).
z The IP address is correct (X.25 and FR).
Note:
z PPP is a widely used WAN protocol. It supports synchronous/asynchronous transmission media
simultaneously and also supports the dialing mode. During daily life and work, the network connection
modes such as dial-up access and DDN uses encapsulated PPP protocol.
z X.25 protocol is the interface protocol between the DTE and DCE. It describes how to establish virtual
circuits, transmit packets, set up links, transmit data, and disconnect links and virtual circuits between
DTE and DCE. In the meantime, it performs error control, flow control, and condition measurement
and provides users with some optional service functions and configuration functions.
z The frame relay (FR) is a simple and effective packet switching protocol.
IV. Troubleshooting
After fault location, you need to solve the problem according to different link protocols.
If the PPP protocol is used, proceed as follows:

1) Check the setting of the link layer protocol.
The routers on both sides of the WAN can communicate with each other only when
they are set with the same protocol.
2) Turn on PPP debug switch.
A-9
Maintenance Manual
When the PPP protocol is adopted and Password Authentication Protocol (PAP) or
Challenge Handshake Authentication Protocol (CHAP) is adopted for password
authentication, you need to confirm whether the passwords on both sides are
correctly set. If they are incorrect, turn on the PPP debug switch.
#debug ppp packet
#mon
After the Link Control Protocol (LCP) negotiation succeeds and the LCP enters the
UP state, PAP or CHAP negotiation is performed. Then the LCP enters the DOWN
state. After debugging, the state of the LCP is changed to the UP state.
V. Solution to Common Problems
Table A-3 lists solutions to some common problems.
Table A-3 Solutions to some common problems

The default protocol of CISCO router is
Change the encapsulated
high-speed digital link channel (HDLC),
The PPP protocol of protocol of the CISCO router to
while the default protocol of Huawei
Huawei Quidway 2501 PPP (recommended solution) or
router is PPP. When executing the
router and that of change the encapsulated
command display int sN (N is serial
CISCO router cannot protocol at the Quidway side to
port number which can be 0 or 1) on
be interconnected with HDLC using the command
2501, you find the state of the serial port
each other. link-protocol ppp or link-protocol
is UP and that of the link protocol is
hdlc.
DOWN.
The two sides
connected
encapsulate the X.25
(or the LAPB directly),
but the protocol is in This is because both sides are encapsulated in the same operational mode
Off state all the time. (DTE or DCE). Change the operational mode at one end.
Turn on the debug
switch DEBUGGING
X.25 PACKET frame, it
cycles continuously.
The X.25 can set up
This is because the incorrect setting of flow control parameters. If it is the
virtual circuits, but
direct back to back connection, check the local transmit window, receive
frequent reset or
window, and the flow control parameters that are interconnected to the
clearance occurs
common packet network and must be consulted with the network
during data
management department.
transmission.
During the
In X.25 address mapping, an IP address
configuration of X.25 Execute the command undo x25
can only correspond to an X.121
address mapping, the map ip to delete the previous
address. When an IP address is
system prompts that address mapping. Re-configure
configured with two different X.121
address mapping is the address mapping.
addresses, conflict occurs.
repeated.
A-10
Maintenance Manual

The PPP protocol belongs to the ISO
protocol on the second layer. Thus you
must locate the fault from the first layer.
The two routers are Execute the command display int sn (n
interconnected is the serial port used) to check whether
the bottom layer signals of DTR, DSR, Observe the debugging
through DDN, and
RTS, CTS, and DCD are all in the UP information with the
encapsulated with
state. BEBUGGING PPP PACKET
PPP protocol at both
switch and find out that both of
ends. Execute the
If they are not, it shows that the physical the routers are in REQUEST
command display to
line between DTE and DCE is not states during the router LCP
check the state of the
connected properly. negotiation at both sides. This
port. The physical
shows that a fault may occur in
layer and the protocol When the system prompts that the serial the intermediate link. In this case,
layer are all in the UP port is in the UP state and there is no check the state of the
state, but after the frame error, it shows the physical layer intermediate transmission cable.
configuration the peer is normal. In this case, use the
end cannot be pinged. command display int sn to check if
LCP and IPCP are in the OPEN state. If
yes, it shows the PPP verification
succeeds.
A.2.4 Faults of Network Layer
Router is network interconnection equipment. Therefore, you must understand the

networking requirements and division of sub-networks when configuring IP address for
the interfaces.
The Ethernet interface IP address of the router must be in the same network segment
of the LAN connected with the Ethernet interface.
Solve problems according to different route protocols. The static route protocol is often
used.
Check whether the corresponding static route is configured correctly with the command
display ip route static.
Check whether the static route is effective with the command display ip route.
Note:
Static route is the only path to the target network configured manually by the system administrator. It
cannot dynamically reflect the change of the network. When the network structure is changed, the system
administrator must modify the configuration. Proper use of static routes can improve the network
performance and save bandwidth for important applications.
You can obtain the routing information for guiding IP forwarding through this path.
A-11
Maintenance Manual
A.2.5 Faults of Ethernet
The following Ethernet faults may occur:

z Check the interface by executing the command display interface. The Ethernet
interface is always in DOWN state
z Check the interface using the command display interface. The Ethernet interface
is in UP state, but the IP address of the host at opposite end cannot be pinged
through.
II. Fault Analysis
The possible causes include:

z The IP address of the Ethernet interface is not configured.
z The IP address or Ethernet protocol configuration is incorrect.
To locate and clear the fault, proceed as follows:

1) View the port information. Check whether the IP address is configured when the
system prompts that the port is in DOWN state.
2) Check whether the IP addresses of the computer and that of the Ethernet interface
of the router are in the same sub-network when the host on the Ethernet cannot be
pinged through.
Their IP addresses must be the same, and only the IP address of the host is
different. If they are not in the same sub-network, IP addresses must be allocated
again. If they are in the same network segment, you must check whether the
protocols match.
Note:
At present, Ethernet (IP network) can adopt two types of protocols: Ethernet-II or Ethernet-SNAP. These
two types of protocols have different encapsulation formats and the maximum transmission unit (MTU).
The maximum transmission unit of former type is 1500 bytes and the later is 1492 bytes.
Routers of Quidway series can receive data of the two formats simultaneously, but the data format
transferred can be selected from any type of the Ethernet-SNAP. You must verify whether the data
transmission format of the router is the same as that of other computers in the Ethernet.
Configuration in the Ethernet interface is as follows:
A-12
Maintenance Manual
send-frame-type Ethernet-II
Or
send-frame-type Ethernet-SNAP
IV. Solutions to Common Problems
Problem: When a dial-up user of Quidway2509 dials up the router from the
asynchronous interface, the asynchronous interface of the Quidway2509 and Ethernet
interface at the terminal can be pinged, but the server in the Ethernet connected with
2509 cannot be pinged.
Analysis: The server in the Ethernet is not configured with the gateway. When
messages are forwarded from the router to the server, the server judges according to
the message that the source address is not the local network address. The reply
message must be sent to the gateway according to the protocol specifications.
However, the server cannot respond to it because the gateway address is not
configured. Therefore, the timeout error occurs on the remote terminal because it
cannot receive messages. After the gateway is added, the server can transfer the reply
message successfully and it can be pinged.
Solution: In the network configuration of the server, direct the gateway in TCP/IP
attributes of the network adapter to the Ethernet interface of the Quideay2509.
A-13
Maintenance Manual
iManager M2000 Appendix B Common Operations of UNIX System
Appendix B Common Operations of UNIX System
The appendix introduces features, terms and structure of the UNIX system and its
commands.
B.1 Solaris Operating System

B.1.1 Overview
Developed by Sun Microsystems Inc., the Solaris operating system is a UNIX

derivative supported by enormous hardware. It bears most of the common features of
the UNIX system.
UNIX is a time-sharing, multi-user and multi-tasking operating system with network
communication function and high transplantability. Since it was launched in 1969, UNIX
has been the most popular and influential operating system all over the world, widely
used in microcomputer, minicomputer, workstation, mainframe computer and
supercomputer. Thanks to the employment of UNIX, great achievements have been
made in fields such as scientific calculation, engineering, network communication and
scientific research & education, etc.
B.1.2 Features of UNIX
The most significant features of UNIX are:
I. Multi-tasking
UNIX is a Multi-tasking operating system which can cope with several tasks
simultaneously, unlike MS DOS, a single-task operating system which is unable to
handle more than one task at the same time. The multi-tasking feature of UNIX in early
stage was realized by the time-sharing mechanism, while the UNIX nowadays has
been enhanced with the real-time multi-tasking capability in addition to the time-sharing
mechanism, which is mainly used in time-critical occasions such as real-time control
and data collection, etc.
II. Multi-user
As a multi-user operating system, UNIX can have two or more concurrent users. In a
Unix system, each user can run his own program as well as a public program, just like
doing that with a personal equipment; while MS DOS, as a single-user operating
system, can only be used by one user at a time.
B-1
Maintenance Manual
III. Concurrent processing capability
UNIX supports a multi-processor system, allowing parallel running of multiple

processors.
IV. Pipe
In a UNIX system, the output of one program can serve as the input of the next program.
Those programs connected in this way looks just like a pipe. By this way, some very
complicated tasks can be completed via the execution of a combination of various
simple tasks, therefore the operability is greatly improved.
V. Powerful Shell
The UNIX program that interprets user commands is called Shell. UNIX provides three
types of Shell. Each shell itself is an interpretive high-level language, by which the user
can create countless commands via programming.
VI. System Protection Mechanism
Featuring powerful system protection mechanism, UNIX can effectively prevent illegal
access into the system and its data.
VII. High Stability
Among all the operating systems currently in use, UNIX is the most stable. Featuring
outstanding failure-handling capability, UNIX can ensure the long-time stable operation
of the system.
VIII. Graphic User Interface
Command line is the main feature of the traditional UNIX user interface, which greatly
limited its popularity among non-computer professionals since it is rather difficult to
remember those commands. This is what Unix has been mostly critisized for.
Nowadays Common Desktop Enviornment (CDE) has been introduced in most of the
UNIX systems, with which the operability of the system has been greatly enhanced.
IX. Strong Networking Support
UNIX offers powerful networking function, the TCP/IP protocol is the default network
protocol in UNIX. It is right owing to the perfect combination of UNIX and TCP/IP that
UNIX, TCP/IP and Internet have been so popularized. So far, UNIX has been the first
choice for all types of servers in Internet.
X. Good Transplantability
UNIX is easy to be transplanted since most of its source codes were written in C
programing language. Moreover, the loose control of the UNIX Association over the
source codes in early stage also boosts the development and popularization of UNIX.
B-2
Maintenance Manual
B.1.3 Terms Related to UNIX
I. User
UNIX is a multi-user operating system that can have two or more concurrent users.
Each user has his own user name, login password and relevant operation authority.
Before using UNIX, the user must log in, i.e. input user name and password. The
system prompt for ordinary users is "$".
II. Group
Several users can constitute a user group, in which the information can be shared.
III. Root user
UNIX super user, having privileges over other users. The system prompt for root user is
"#".
IV. Process
"Process" refers to a program currently running. UNIX can handle multiple processes at
the same time. Each process has a unique ID, which is called process ID (PID).
V. Foreground process
It is a process in which the user interacts directly with the machine. The foreground
process accepts keyboard input and display the result on the monitor screen. By
default, the UNIX program activated by the user is running in the Foreground.
VI. Background Process
It is a process in which the machine does not interact with the user. Generally, the user
is not aware of the running of the background process. Many of the UNIX system
processes are performed in the background.
VII. Device
Also called device file, it stands for a certain piece of hardware, such as a disk, a
diskette or a serial port. In UNIX, the access operation of the hardware is completed via
device file. The device files are saved in directory "/dev", For example, "/dev/hd0" refers
to the first floppy disk drive.
B.2 System Structure of UNIX

B.2.1 System Composition of UNIX
UNIX is a layered operating system, composed of Kernel, Shell and Application

Program. The architecture of UNIX system is shown in Figure B-1.
B-3
Maintenance Manual
Application Program
Shell
Kern sh
Hardware
csh
Kernel
ksh
Shell
Application Program
Figure B-1 UNIX architecture
I. Hardware
The hardware that supports UNIX. It is the physical foundation of the whole operating
system.
II. Kernel
As the core of the whole operating system, the Kernel controls the running of UNIX
equipment and the computer resources, protects the user programs from being
affected by the complicated hardware events. With the Kernel, the user program and
system ourter-layer program will only in charge of the interactive operation with the
Kernel, instead of taking care of the detailed information of the hardware.
III. Shell
As a special program in UNIX, Shell is the interface between the Kernel and the user. It
is also an interpretive high-level language, serving as the command interpreter. A Shell
is made up of some simple programs, running on top of the core program and dealing
with all user inputs. Shells commonly in use nowadays are divided into three types:
Bourne Shell, Korn Shell and C-Shell. Please refer to Table B-1 for details.
Table B-1 Introduction to UNIX Shells
Type Feature Abbr. Command Prompt

The oldest and the most popular type that
Bourne Shell offered by all UNIX systems. It is the basis of B Shell sh $
the three Shell programs.
It is an expansion of B Shell and compatible
Korn Shell K Shell ksh $
with B Shell.
B-4
Maintenance Manual
Type Feature Abbr. Command Prompt

It is the most powerful one in the three Shell
programs, which is closer to C programing
C Shell language. However, the commands are C Shell csh %
difficult to remember. Therefore, it is more
popular in colleges and universities.
Normally, Bourne Shell is the default shell of the system. To switch to another shell,
simply input corresponding Shell command on command prompt. For example, to
change from current Shell to K Shell, input the command "ksh".
IV. Application program
The programs in the outermost layer are the application programs developed by the
user according to their actual needs. UNIX offers a great deal of tools and applications,
such as vi editor, file searching and backup program, etc.
B.2.2 File System of UNIX
UNIX saves and handles files within its file system. Each system can set up and hold a
large number of file systems. Generally speaking, a file system is similar to a drive in
DOS. For example: a typical UNIX system may contain a root file system (/), a user file
system (/user) and a master file system (/home). Those file systems can be saved in
one or several hard disks. The file system can also be created in diskette and tape.
UNIX treats the external devices (such as printer, diskette, etc) and directory as files.
The UNIX file system developes on a tree structure. On top of the structure, it is the root
of the tree – called the root directory, always indicated by "/". Tracking down from the
root directory (/), we will find the subdirectories or lower level directories and files, until
we reach the leaves of the tree -- the files in various subdirectories.
B.2.3 Directory Structure of UNIX
In UNIX file system, all files and file directories are contained in their parent directories.
The parenet directory of the root directory is itself. In fact, a directory is just a list of
information about all the related files and subdirectories.
Some files and directories will be generated for the user when the system installation is
finished. The structures of the file directories are shown below:
z profile User environment parameter definition files.
z bin Directory of executable files.
z etc Directory of configuration files, which stay unchanged during system
operation and don’t need to be restored after system upgrade.
z data Directory of data files, which will change during system operation and
shall be restored after system upgrade.
z log Directory of log files.
B-5
Maintenance Manual
z script Directory of database installation script files.
B.2.4 UNIX System Files
The information of a UNIX file includes the owner of the file, the authority he has for the
file, the date it is created, modified and last accessed, etc. Please refer to the following
for details:
z Mode The protection mode and type of the file.
z Link count The number of links.
z User ID The ID of the user owning the files.
z Group ID The ID of the group to which the file owner belongs.
z Size The size of the file (in byte).
z Access time The time when the file was last accessed.
z File name The name of the file.
The above information will be displayed when the command "ls" (list files) is executed.
In a UNIX system, there is no special requirements on the file structure. The file can be
ASCII file, binary file, or the combination of the two, and exist in the form of text file,
script file or complied object code of a program.
B.2.5 Program of UNIX
Program, or command, can be used by the user to perform interactive operation with
the Kernel, so as to customize certain working environment and accomplish specific
functions. In a UNIX system, the prgram can be an executable shell file, such as a shell
script file, an internal shell command and a source code or complied object code file,
etc.
Shell is a command line interpreter, with which the user interacts with the Kernel and
complies ASCII script file to be executed in shell.
The system programs (system commands) are ususally binary and complied from the
source code in C programing language. They are normally saved in the directories of
"/bin", "/usr/bin", "/usr/local/bin and /usr/ucb", etc. (varying with different UNIX systems),
providing typical UNIX functions, such as sh, csh, date, who and more, etc.
B.3 Solaris System Common Operations

B.3.1 The Browse and Control of Directory
The file system of UNIX is like a tree spreading from the root to the leaves. The root
directory is indicated by "/", and the system and users directories are organized under
the root directory. When logging in, the user normally enters his Home directory directly.
The user can create subdirectories under his Home directory. Table B-2 shows the
directory browse and control commands commonly in use:
B-6
Maintenance Manual
Table B-2 Commands for directory browse and control
Command/Syntax Function
pwd Display current working directory
cd [Directory] Switch directory
mkdir Directory Create a directory
rmdir Directory Delete a directory
ls [Option] [Directory or File] List directory content or file information
I. Display current working directory -- pwd
[Description]
The command "pwd" is used to locate the current direcory at any time.
[Command format]
pwd
[Example]
Display current working directory:
$pwd
/export/home/sybase
Caution:
Unlike DOS, UNIX does not always display the directory name, therefore it is necessary to execute the
command "pwd" from time to time to display the current working directory.
II. Switch directory -- cd
[Description]
The command cd is used to switch to another directory from the current directory. It can
handle both absolute path and relative path.
[Command format]
cd [Directory]
[Example]
Return to Home directory:
$ cd
Enter system root directory:
B-7
Maintenance Manual
$ cd /
Go up one directory:
$ cd ..
Go up two directories:
$ cd /
Enter directory /export/home/sybase by absolute path:

$ cd /export/home/sybase
Note:
After a user logs into the system and switches to other working directory, how can he return to the Home
directory promptly?
The command "cd" without any parameter, as shown in below, can server the purpose.
$ cd
III. Create a directory -- mkdir
[Description]
The command "mkdir" is used to create a subdirectory. When determining the path of
the newly created directory, both absolute path and relative path can be used.
[Command format]
mkdir directory
[Example]
Create a subdirectory "data" in direcory "/home1/omc":
$ mkdir/home1/omc/data
If the current directory is "/home1/omc", the above command can be simplified as :

$ mkdir data
IV. Delete directory
[Description]
When the command "rmdir" is used to delete a directory, the directory shall be empty.
Otherwise, the files in that directory shall be deleted first. What’s more, to delete the
current working directory, the user must first "jump" up to the upper level directory.
[Command format]
rmdir directory
[Example]
B-8
Maintenance Manual
Delete the subdirectory "data" in directory "/home1/omc":

$ rmdir/home1/omc/data
If the current directory is "/home1/omc", the above command can be simplified as:
$ rmdir data
V. List directory content -- ls
[Description]
The command "ls" is used to list the files and subdirectories in the selected direcory.
Executing the command "ls" without any parameter will list the content of current
directory. Executing the command with parameters will list information about the size,
type, authority of the file and the date when it was created and modified.
[Command format]
ls [Option] [Directoy or File]
[Description of options]
There are many options for the command "ls" and combination of options can be used
-- but remember to put a prefix "-" before the options. Here are some common options:
-a List all the files, including the hidden files (files starting with a dot, such as
".login").
-F Specify the type of the file by suffix signs. The meanig of the suffixes are:
/ directory file
= pipe file
@ sign-linking file
* executable file
-l List the detailed information about a file, including the file type, authority, number
of links, owner, file group, file size, filename and the date of last modifications, etc. If
the file is a sign-linking file, there will be a sign "->" at the end of the filename, pointing
to the linked file.
[Example]
Display the long-form content of the files in the current directory:
$ ls -l |more
total 11094632
drwxr-xr-x 2 sybase staff 1024 Sep 5 2001 bin
-rw-r--r-- 1 sybase staff 2048000000 Mar 6 09:50 data_dev.dat
drwxr-xr-x 2 sybase staff 512 Sep 5 2001 devlib
--More—
B-9
Maintenance Manual
Note:
z When the command "ls –l" is executed, the files displayed may take up several screens. Two ways are
available to display the files one screen at a time:
z ls -la | more
z ls -la>ccc Save the result to file "ccc", then execute the command "$ more ccc", the result will be
displayed one screen at a time.
z When the command "ls -l" is executed, seven columns of information will be displayed.
z There are 10 characters in the 1st column:
z The first character indicates the file type (e.g. "-" stands for a common file and "d" for directory, etc).
z The following nine characters are three triplets indicating the access authority of the file owner. The
first triplet pertains to the owner, the middle triplet pertains to members of the user group and the
rightmost pertains to everyone else in the system ("r", "w" and "x" indicate that the user has the
authority to read, write and execute the file, while "-" indicates that the user has no related authority for
it).
z The 2nd column indicates the number of hard links of the file.
z The 3rd and the 4th column display such information as the owner of the file, and the user group to
which the file belongs.
z The 5th column shows the size of the file in byte.
z The 6th column shows the time and date when the file is last modified.
z The 7th column shows the filename.
B.3.2 File Maintenance Command
The commands shown in Table B-3 can be used to create, copy, delete or modify a file.,
etc.
Table B-3 File maintenance commands
Command/Usage Function
cp [Option] file1 file2 Copy a file
mv file1 file2 Move or rename a file
rm [Option] file Delete a file
chmod [Option] file Modify the authority of a file
chown [Option] owner file Modify the owner of a file
chgrp [Option] group file Modify the group of a file
I. Copy a file -- cp
[Description]
B-10
Maintenance Manual
The command "cp" is used to copy the content of a file into another file.
[Command format]
cp [option] file1 file2
-r Recursively copying a directory (the directory copied includes the directory
and any files and subdirectories it contains, as well as files in those
subdirectories).
[Parameter description]
File1: Source file
File2: Object file
[Example]
Copy the file "old_filename" in current directory to a new file named "new_filename".
$ cp old_filename new_filename
II. Move file or rename file -- mv
[Description]
The command "mv" is used to move or rename a file. The difference between them is
that when the source file and the object file are in the same directory, this command is
used to rename the file; when the source file and the object file are not in the same
directory, it is used to move the file.
[Command format]
mv file1 file2
File1 Source file
File2 Object file
[Example]
Modify the name of the file "old_filename" in the current directory to be "new_filename"
$ mv old_filename new_filename
Move the file "old_filename" in the root directory to directory "/home1/omc":

$ mv /old_filename /home1/omc
B-11
Maintenance Manual
Caution:
The difference between the command "mv" and the command "cp" is:
After command mv is executed, there is still only one file--the object file. In the case of "cp", a new copy of
the file was created, so after the command is executed, there are two files—the source file and a new copy
of the file.
III. Delete a file -- rm
[Description]
The command "rm" is used to delete a specific file.
[Command format]
rm [Option] file
-i Interactive operation (wait for confirmation before the command is
executed).
-r Recursively deleting a directory (the directory deleted includes the directory
and any files and subdirectories it contains, as well as files in those subdirectories).
File Specifying the file to be deleted
[Example]
Delete the file "old_filename" in the current directory:
$ rm –i old_filename
rm: remove old_filename (yes/no)? Y
Caution:
z In UNIX, once a file is deleted, it cannot be restored. Therefore, it is strongly suggested to use option
"-i" to avoid misdeletion.
z Two ways are available for deleting directory: execute the command "rmdir" or execute the command
"rm –r". The difference between the two is:
rmdir can only delete empty directories.
rm -r can delete any directory.
B-12
Maintenance Manual
IV. Modify the protection mode of the file -- chmod
[Description]
The command "chmod" is used to modify the protection mode of a directory, i.e. the
authority of the user to the directory.
[Command format]
chmod [Option] file
This command can be used in two ways depending on the different expressions of the
option.
a) Sign mode
b) Digit mode
In the sign mode, the command format is "chmod [object]operational character
[authority] file"
In the digit mode, the command format is: "chmod lmn file"
a) Sign mode
Object: can be one of the following options
u user (owner of the file)
g group members
o other users in the system
a all the users
Operational character: can be one of the following options.
+ Add authority
- Cancel authority
= Set authority
b) Digit mode
The option "lmn" has three numbers, representing the authority of the file owner,
authority of the group members and ahtority of other users in the system. The value of
each number is the sum of the numbers indicating "r" (to read), "w" (to write), "x" (to
execute) and "-" (no authrotiy), among which:
r = 4, w = 2, x = 1, - = 0
Example:
-rwxr-xr-- 1 rms sbsrms 46098432 May 12 16:02 sdh*
The authority of file "sdh" is expressed by "rwxr-xr--", which is composed of three
triplets; the first pertains to the owner of the file, the middle triplet pertains to the
members of the user’s group, and the rightmost pertains to the other users in the
system. Then the value indicating the authority is 754 (7=4+2+1, 5=4+0+1, 4=4+0+0).
B-13
Maintenance Manual
File The name of the file in which the authority is to be modified
[Example]
a) Sign mode
Set the authority of file1 as below: set the file1 to be readable, writable and executable
to its owner; set it to be readable and executable to other users in the group; set it to be
readable and executable to other users in the system. Here are the commands:
$ chmod u=rwx,go=rx file1
Set the authority of file2 to be readable and writable to all the users: Here are the
commands:
$ chmod a=rw file2
b) Digit mode
Set the authority of file1 as below: set the file1 to be readable, wirtable and executable
to the owner; set it to be readable and executable to other users in the group; set it to be
readable and executable to other users in the system. Here are the commands:
$ chmod 755 file1
Set the authority of file2 to be readable and writable to all the users. Here are the
commands:
$ chmod 666 file2
Note:
z In the sign mode, to set the authority of the group members and that of the other users in the system,
the directory in which the file is saved shall be set as executable to those users. The simplest way is to
execute the following commands on the directory where the authority is to be modified:
$ chmod u=rw,+x . or $ chmod u=rwx,go=x .
The symbol "." here stands for the current directory.
z In the digit mode, "r=4, w=2, x=1, -=0" are based on binary system. To the three digits representing the
authority to read, write and execute in the same group, assign it a value of "1" when there is relevant
authority corresponding to that digit, and assign it "0" when there is not relevant authority. Take the file
"sdh" above as an example, the authority "rwxr-xr--" will be "111101100" when represented by binary
value, in which each triplet represents the authority of the three types of users respectively. The
weighted sum of the binary values in each triplet are the decimal value "7", "5" and "4".
V. Modify the owner of the file -- chown
[Description]
B-14
Maintenance Manual
The command "chown" is used to modify the owner of a file. However, to most of the
UNIX systems, this command can only be used by super users, i.e. the ordinary user
cannot modify the ownership of his files.
[Command format ]
chown [Option] owner file
-f Execute the command forcibly, and do not report any error.
-R Recursive directory
Owner The new owner after modification.
File The file whose owner is to be modified.
[Example]
Modify the owner of the "file" to be "new_owner":
# chown new_owner file
Change the owner of all the files in directory "/export/home/sybase" and its
subdirectories to "M2000":
# chown –R M2000 /export/home/sybase
VI. Modify the user group of the file -- chgrp
[Description]
The command "chgrp" is used to move all his files from the user group to which he
belongs, to another user group. Obviously, the user shall belong to at least two user
groups at the same time.
[Commond format]
chgrp [Option] group file
-f Execute the command forcibly, and do not report any error.
-R Recursive directory
Group The new user group after the modification.
File The file of which the user group is to be modified.
[Example]
Modify the user group of "file" to be "new_ group":
$ chgrp new_group file
B-15
Maintenance Manual
Caution:
z The new user group to which a file is moved to shall have already been created. The command
"groups" can be used to list the groups to which the user belongs. Please refer to "Section 1.2 UNIX
User Management Commands" for details about how to create a user group.
z After the owner or group of a directory is changed, the directory will not belong to that user or user
group any more. However, the attributes of the subdirectories and files in that directory remain
unchanged.
z The command "chown" can be used to modify the owner and the user group of a file at the same time:
# chown omc:staff file1
This command above is used to modify the owner of the file1 to be "omc" and the group to be "staff".
B.3.3 Text File Content-Displaying Commands
The following are the system commands used to display and browse the content of text
files, as shown in Table B-4.
Table B-4 Display and browse commands for text files
echo character string [option] Send character string to the screen
cat [option] file Display the content of the file
more [option] file Display a file, one screen at a time.
head [value] file Display the beginning of the file
tail [value] file Display the end of the file
clear Clear screen
I. Send character string to screen -- echo
II. [Description]
The command "echo" is used to send character string to the standard output device
(generally the monitor screen).
[Command format]
echo character string [option]
\c Do not output RETURN
\0n "n" is a 8-digit ASCII character code
B-16
Maintenance Manual
\t Output TAB
\n Output RETURN
\v Output vertical TAB
[Example]
$ echo $HOME
/export/home/sybase
The "/export/home/sybase" displayed on the screen is the meaning of character string

"$HOME".
To avoid outputting RETURN, the following command can be used:
$ echo Hello Class "\c"
Hello Class $
Or:
$ echo "Hello Class \c"
Hello Class $
Note:
The options of \c, \0n, \t, \n and \v generally appear in the character string enclosed in quotation marks.
The quotation marks can be used to quote either an option alone, or multiple options.
III. Display the content of file -- cat
[Description]
The command "cat" is used to display the content of text file.
[Command format]
cat [option] file
-n Number each line of the text when displaying.
-v Display nonprinting characters (except "TAB" and "RETURN").
[Example]
Display the content of "M2000_Table.txt":
$ cat M2000_Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
tbl128Addr m2000
user table
B-17
Maintenance Manual
tblSvrIP m2000
user table
Note:
The command "cat" can display several files at one time, like this:
$ cat file1 file2 file3
IV. Display a file, one screen at a time -- more
[Description]
The command "more" is used to display a file, one screen at a time. It can also be used
to browse the previous pages and search text strings.
[Command format]
more [option] file
-c Clear the screen before the content is output.
-w Do not quit at the end of the input, wait for prompt.
-lines The number of lines displayed on each screen.
+/mode Search by the given mode.
[Example]
Display the content of "M2000_Table.txt", one screen at a time:
$ more M2000_table.txt
Name Owner
Object_type
------------------------------ ------------------------------
tbl128Addr m2000
user table
tblAucFunction m2000
user table
--More--(15%)
B-18
Maintenance Manual
Note:
z To display a file one screen at a time, the following keys can be used to execute relevant operation:
Space key Display the next screenful.
Return key Display next line.
q Quit.
h Display help information.
b Go back to the previous screenful.
/word Search the character string "word" backward.
z Due to the concatenated execution of multiple commands of UNIX, |more can be added to the end of
other commands to display relevant result by several screens. For example, with the command "$ ls -la
|more", the result of "ls –la" can be displayed by several screens.
Display the beginning and the end of a text file -- head & tail
head
[Description]
The command "head" is used to display the first few lines of a text file. By default, 10
lines will be displayed.
[Command format]
head [value] file
Value The number of lines to be displayed.
[Example]
Display the first three lines of M2000_Table.txt:
$ head -3 M2000_Table.txt
Name Owner
Object_type
------------------------------ ------------------------------
tail
[Description]
The command "tail" is used to display the last few lines of a text. By default, 10 lines will
be displayed.
[Command format]
tail [value] file
Digit The number of lines to be displayed.
[Example]
B-19
Maintenance Manual
Display the last three lines of M2000_Table.txt:

$ tail -3 M2000_Table.txt
user table
tblVlrFunction m2000
user table
Note:
A special function of the command tail is to view the latest change of the log file promptly, since all the
latest changes of the log file are added to the end of it. The command format is:
$ tail -f commdrv.log
The option "-f " refers to the function of monitoring the file.
V. Clear the screen -- clear
[Description]
The command "clear" is used to clear the content of the screen.
[Command format]
clear
[Example]
Clear the screen:
$ clear
B.4 UNIX User Management Commands

Table B-5 shows the user management commands commonly in use. Please note that
only the root user and authorized user can add, modify or delete user and user group.
Table B-5 UNIX user management commands
useradd [option] user name Add a user
userdel user name Delete a user
usermod [option] user name Modify the user login information
passwd user name Modify user password
groupadd user group name Add a user group
groupdel user group name Delete a user group
groupmod [option]user group name Modify user group information
B-20
Maintenance Manual
B.4.1 Add User -- useradd
[Description]
The command "useradd" is used to add a user.
[Command format]
useradd [option] user name
-c comment Comment
-d directory The home directory
-m Create a home directory automatically if it does not exist.
-g group User group
-s shell The shell that the user uses.
User name The name of the user to be added.
[Example]
Create a user named "omc1" with home directory of /home1/omc (create automatically)
and comment of "Test User". The user will belong to user group "staff" and B shell be
adopted.
#useradd -c "Test User" –d /home1/omc –m -g staff -s/usr/bin/sh omc1
Caution:
After a user is added, the password for him shall be set. Please refer to "Section 1.4.4 Modify User
Password -- passwd" for details. After the password is set, the user can log in as a new user.
B.4.2 Delete User -- userdel
[Description]
The command userdel is used to delete a user. In some UNIX systems, it is not
allowed to delete a user completely. The command userdel can be used to revoke the
rights granted to the user.
[Command format]
userdel user name
B-21
Maintenance Manual
Caution:
The command userdel cannot be used when the user has logged in, otherwise, the following error
message will be displayed:
UX: userdel: ERROR: omc1 is in use. Cannot remove it.
B.4.3 Modify User Login Information -- usermod
[Description]
The command usermod is used to modify the user login information.
[Command format]
usermod [option] user name
-c comment The comment after modification
-d directory The home directory after modification
-g group The user group after modification
-m Create a home directiory automatically if it does not exist.
-l new_logname The user name after modification
-s shell The shell that the user uses.
user name The name of the user whose login informaiton is to be modified.
[Example]
Modify the login information of "omc1" as below: Modify the user name to be "test", user
group to be "new_group", home directory to be "/home1" and comment to be "Tester".
# usermod -c "Tester" -d /home1 -g new_group -l test omc1
Caution:
The command "usermod" cannot be used when the user has logged in, otherwise, the following error
information will be displayed:
UX: usermod: ERROR: omc1 is in use. Cannot change it.
B.4.4 Modify User Password -- passwd
[Description]
B-22
Maintenance Manual
Command passwd is used to set the password for newly added users or modify user
password.
[Command format]
passwd user name
B.4.5 Add User Group -- groupadd
[Description]
The command groupadd is used to add user group to UNIX system.
[Command format]
groupadd user group name
B.4.6 Delete User Group -- groupdel
[Description]
The command groupdel is used to delete user group.
[Command format]
groupdel user group name
B.4.7 Modify User Group Information -- groupmod
[Description]
The command groupmod is used to modify the user group information.
[Command format]
groupmod [option] user group name
-n name The name of the user group after modification.
User group name The name of the user group to be modified.
[Example]
Modify the name of the user group "staff1" to be "staff2":
# groupmod -n staff2 staff1
B.5 Utility Commands and Programs

Table B-6 shows the utility commands offered by UNIX.
B-23
Maintenance Manual
Table B-6 Utility commands and programs
find directory condition Search file.
grep character string file Search special character string.
tar [function optios[modify option]] [file] Utility program for file backup and restoration.
compress/uncompress file
Compress/decompress file.
pack/unpack file
pkgadd [option] file package name Send file package to system.
pkgrm [option] file package name Remove file package from system
bc Calculator
B.5.1 Search File -- find
[Description]
The command find is used to search the file in specific directory and its subdirectories
that meets preset conditions. With this command, the file can be found even if the
correct path of it is forgotten.
[Command format]
find directory condition
Directory The directory where the file search starts. Multiple directory names can
be input with space between them.
Condition File search conditions, including the file name, the owner, the time of
the last modification, etc.
Table B-7Shows the description of the conditions.
Table B-7 Description of conditions
Conditions Description
The name of the file or directory to be searched. Wildcard can be used, e.g.
-name name
-name ‘*.c.’
-print Print the path that meets the conditions.
-size Search the file occupying n blocks.
Search the file according to the type of the file. The file type x includes:
-type x d --- directory f --- file b --- block
c ---character p --- pipe
-user user Search all the files of "user". The "user" can be user name or UID.
B-24
Maintenance Manual
Conditions Description
Search all the files of user group "group". The "group" can be user group
-group group
name or GID.
-links n Search all the files whose number of links is n.
-atim n Search the files accessed n days ago.
-mtime n Search the files modified n days ago.
Take the file found as the object to be executed by the command. Put the
-exec command {}\;
parameter to be used in the exection of the command in {}.
Table B-8 shows the logical operators of conditions.
Table B-8 The logical operators of conditions
Logical
Meaning Example Description
operators
! non ! All the files with extended name other than ".c".
All the files more than 10 blocks or with number of
-o or -size +10 -o -links 3
links more than 3.
All the files more than 10 blocks and with number
and -size +10 -links 3
of links more than 3.
In the above table, "+10" stands for more than 10 (blocks) and "-10" for less than 10
(blocks).
[Example]
Search files with filename starting with "c" in directory "/tmp", and print the paths:
$ find /tmp -name "c*" -print
/tmp/ctisql_0WBJgt
/tmp/ctisql_M6Bhn_
Search files named "test" in current directory, and print the paths:
$ find . -name test -print
./HWReport/reloc/resin1.2.0/conf/test
B-25
Maintenance Manual
Note:
z It may take several minutes to finish searching the files meeting the conditions with command find.
Therefore, it is suggested to execute this command in the background, i.e. the user may output the
result to a file, so that he can view the result later. The user can end the command line with a "&",
informing the system to execute the command in background. For example:
$ find / -name "abc*" -print > abc.file &
After the task is completed, the following command can be used to view the result of the search.
$ cat abc.file
z Different users may have different rights for the same file, therefore ordinary users may only find part
of the files in the system. To list all the files that meet the criteria, the following operations are
suggested: 1) to operate as a super user; 2) to search from the root directory.
B.5.2 Search Special Character String -- grep
[Description]
The command grep is used to search special character string in a text, and print all the
lines containing that character string.
[Command format]
grep character string file
Character string The character string to be searched.
File The file to be searched in.
[Example]
Search the character string "operation" in "ifconfig.txt":
$ grep operation ifconfig.txt
Caution:
In the above example, the text string "The following options are supported" contains spaces, remember to
enclose it with quotation marks in the command line.
B.5.3 Utility Programs for File Backup and Restoration -- tar
[Description]
B-26
Maintenance Manual
The command tar is used to combine several files into one archive and save it to tape
or disk. When one of the files is wanted, it can be obtained from the archive.
[Command format]
tar [Function options[modification options]] [file]
1) Function options to set the actions of the command tar (such as read,
write, etc)
r Add the specified file to archive.
X Read the file in the archive. If the file name is a directory, its subdirectories
will be read.
c Create a archive.
g Create the file from the beginning of the archive, instead of place it after the
last file.
2) Modification options to modify the actions of the command tar.
v Activate display mode. The name of all the files processed will be displayed.
(used often)
w Activate confirmation mode. User’S confirmation is required before each file
is processed,.
f Indicate that the archive is a file. If this parameter is skipped, the preset tape
and disk will be used as the objects. (used often)
file The file to be backed up or restored.
[Example]
1) Execute the command tar to back up files.
Back up all the files and subdirectories in directory "data" in the current directory to
default device, and display the file information during the backup.
$ tar cv data
In current directory, back up all the files and subdirectories in directory "data" to a
file "databak.tar", and display the file information during the backup.
$ tar cvf databak.tar data
2) Execute the command "tar" to restore files
Restore the files in the default device in step 1) to the hard disk, and display the file
information during the restoration.
$ tar xv
Restore the "databak.tar" backed up in step 1) to the current directory "/data", and
display the file information during the restoration.
B-27
Maintenance Manual
$ tar xvf databak.tar
Caution:
z There is no "-" sign before the function and modification parameters of the command tar.
z The command tar can be used to pack several files into a package, shown as below:
z $ tar cvf filebak.tar file1 file2 file3
z The above command is used to pack the file1, file2 and file3 into a package named "filebak.tar".
z Please note that the names of the diskette and tape devices used in file backup and restoration with
the command tar may vary with different UNIX systems. Check carefully before use.
B.5.4 Compress and Decompress Files -- compress & uncompress, pack &
unpack
1) Command compress/uncompress
[Description]
The command compress is used to compress the file to reduce the memory
space. The name of the compressed file ends with ".Z". The command for file
decompressing is uncompress.
[Command format]
compress file
uncompress compressed file ended with ".Z".
2) Command pack/unpack
[Description]
The command pack can also be used to compress file. The name of the
compressed file ends with ".z". The space achieved after compression depends on
the file type. The related command for extracting the file is unpack.
[Command format]
pack file
unpack compressed file ended with ".z".
B-28
Maintenance Manual
Caution:
z The command pack cannot be used to compress the file, which is too small in size. To compress such
kind of files, use the option -f (forced compression), shown as below:
$ pack -f filename
z The difference between the command tar and the file-compressing commands:
The command tar is used to pack or combine files, like putting a large number of small articles into a
container and labeling it in order to preserve or transport. However, the total weight of the items does not
change. The command "tar" packs many directories or files into a package. Use The command compress
or pack to compress the combined files "*.tar" if necessary.
B.5.5 Send File Package to the System -- pkgadd
[Description]
The command pkgadd is used to send the file package to the system to run it.
[Command format]
pkgadd [option] file package name
-d device Install or copy package from the device. The device can be an absolute path,
the identifier of a tape and a diskette (e.g. "/var/tmp" or "/floppy/floppy_name"), or
device name, such as "/floppy/floppy0".
[Example]
#pkgadd -d. HWM2000
"." indicates the current directory.
B.5.6 Remove Package from the System -- pkgrm
[Description]
The command pkgrm is used to remove the package from the system.
[Command format]
pkgrm [option] file package name
[Example]
# pkgrm HWM2000
B-29
Maintenance Manual
Note:
The command pkgadd and pkgrm are frequently used during the installation and upgrade of iManager
M2000. In the upgrading of M2000 system, HWM2000 shall be unloaded first (pkgrm HWM2000) after the
process stops. After the upgrading files are unloaded, they shall be packed and sent to the system
(pkgadd -d. HWM2000).
B.5.7 Calculator -- bc
[Description]
The command "bc" can be used to perform simple calculation.
[Command format]
bc
[Example]
$ bc
4*5
20
Note:
To get the result, input the command bc, press RETURN;
Input the formula 4*5, and then press RETURN; the result will be displayed. Press <Ctrl+D> to quit bc
program.
B.5.8 Basic Features of vi Editor
As a text editing tool, vi editor is used to creat and modify text files.
There are two working modes for vi editor:
z Text input mode to input the text
z Command mode to input control command
To enter vi editor, type the following command:
vi file name
B-30
Maintenance Manual
To enter text input mode:
a Insert text immediately after the cursor (append)

A Insert text at the end of the line where the cursor is.
i Insert text immediately before the cursor (insert)
I Insert text before the first nonblank character in the line where the cursor is.
o Start a new line below the current one and insert text. (open)
O Start a new line above the current one and insert text.
To move the cursor in command mode:
h Move the cursor one character left.

j Move the cursor one character down.
k Move the cursor one character up.
l Move the cursor one character right.
Line No. G Move the cursor to certain line (e.g. 1G meams to move the cursor to the first line.)
G Move the cursor to the end of the text.
To quit the text insert mode:
<ESC> Press ESC key to quit text insert mode and enter command mode.
To delete characters in command mode:
x Delete the current character.

dd Delete entire line.
To quit vi editor:
The commands used to quit from vi shall be executed in command mode. Therefore,
press <ESC> before executing the following commands, no matter what the current
mode is.
:wq Save the file and quit.

:q Quit without saving the file.
:q! Quit and discard all the changes.
:w Save the file but do not quit.
B-31
Maintenance Manual
B.6 System Resource Commands

Table B-9 shows the system resource report and management commands offered by
UNIX.
Table B-9 System resource report and management commands
man [option]command Obtain help information about specific commands.
df [option] [file system] Report the free disk space.
du [option] [directory or file] Report disk space occupied by each file system.
ps [option] Display the status of an active process.
kill [option] [process No.] Terminate a process.
who [option] List the information of the users currently logged in .
whereis [option] command Report the location of the command.
which command Display the path of a specific command.
hostname [host name] Display or set the host name.
uname [option] Display the information about the operating system.
ifconfig [option] View the IP address of the host.
script [option] [file] Record screen I/O activity.
date [option] [+format] Display current date and time.
B.6.1 Obtaining Help Information about Commands -- man
[Description]
The command man is used to view the online help documents of a specific command.
[Command format]
man [option] command
command the command of which the help information is to be viewed.
Note:
Not all of the parameters of the command "man" are names of commands. For example, the command
"man ascii" will display all the ASCII characters and their expressions. The command "man shell_built-ins"
will display the built-in command list and the shell used.
B-32
Maintenance Manual
B.6.2 Report Free Disk Space -- df
[Description]
The command df is used to report free space of the disk. The system administrator
shall execute this command frequently to check the occupancy of the disk space, so as
to prevent disk failure caused by data overflow.
[Command format]
df [option] [file system]
-l The local file system
-k Report the disk space in Kbyte
[Example]
Check free disk space:
df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 2053605 997684 994313 51% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/dsk/c0t1d0s7 35009161 2562019 32097051 8% /export/home
swap 3431792 6664 3425128 1% /tmp
Note:
z What displayed in the above example are the file system name, the size (unit: Kbyte), used space,
free space, the capacity ratio of the filled file system and the capacity percentage of filling file system
and its mounting point. When user executes the command df without any parameters, the free disk
space in each mounted device will be reported.
z When the free disk space reduces to the bottom line, the system administrator shall take prompt
measures to find out the trouble-making file system. The command du introduced below can be used
to list the disk occupancy of each file system.
B.6.3 Report the Disk Space Occupied by Each File System -- du
[Description]
The command du is used to display the disk space occupied by specific directory or file.
[Command format]
du [option] [directory or file]
B-33
Maintenance Manual
-a Display the disk space occupied by each file.

-s Display the total disk space used.
-k Report the result in Kbyte.
[Example]
Display the disk space occupied by the files in directory "/export/home/sybase".
$du –k/export/home/Sybase |more
Display the disk space occupied by all the file systems in the current directory, and send
the results to the command "sort" for sorting.
$ du -s * |sort -rn |more
425108 bin
174968 devlib
41094 lib
18588 pad
—More--
List the first three of the file systems displayed above according to the size of the file:
$ du -s * |sort -rn |head -10
425108 bin
174968 devlib
41094 lib
B.6.4 Display the Status of the Active Process -- ps
[Description]
The command ps is used to report the status of the processes running in the system
currently.
[Command format]
ps [option]
-e Display the status of all the processes running in the system.
-l Display in long-form list.
-u user Display the process status of a specific user.
-f Display all the status information of the processes currently running.
[Example]
Display the status information of all the running processes controlled by the user login
device (terminal).
$ ps
PID TTY TIME CMD
13726 pts/5 0:00 ksh
B-34
Maintenance Manual
Display the complete information of the user’s active processes:

$ ps -f
UID PID PPID C STIME TTY TIME CMD
sybase 13726 13724 0 08:44:35 pts/5 0:00 –ksh
View M2000 process

ps -ef | grep m2000
m2000 18355 18354 0 10:00:46 ? 0:00/export/home/02000/bin/timersvrd
m2000 18354 1 0 10:00:46 ? 0:00 monsvrd /export/home/m2000/bin/timersvrd
m2000 18318 1 0 10:00:42 ? 0:00 monsvrd /export/home/m2000/bin/commonsvrd
m2000 18320 18318 0 10:00:42 ? 0:00/export/home/m2000/bin/commonsvrd
Note:
z Executing the command "ps" without any parameters will display the information about all the running
processes controlled by the user login device (terminal).
z More information can be displayed by specifying parameter "–f", including the user name (UID), the
process ID (PID), Parent process ID (PPID), a technical number indicating the running time of the
process (C), process start time (STIME), the name of the terminal activating the process (TTY), and
the process name (CMD), etc. If "?" is displayed in TTY, it indicates that process has nothing to do with
terminal.
z To display all the processes related to certain characters, e.g. the process related to M2000 in the
above example, the command grep can be used together with this command.
B.6.5 Terminate a Process -- kill
[Description]
The command kill is used to send termination signal to one or more processes, i.e. to
terminate one or several processes.
[Command format]
kill [option] [process No.]
-l List the name of all the signals
-s signal Send a signal named "signal" to process.
Process No. The ID of the process to be terminated, or process ID.
[Example]
List all the signal names:
B-35
Maintenance Manual
$ kill -l
EXIT HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM USR1
USR2 CLD PWR WINCH URG POLL STOP TSTP CONT TTIN TTOU VTALRM PROF XCPU XFSZ
WAITING LWP FREEZE THAW CANCEL LOST RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMAX-3
RTMAX-2 RTMAX-1 RTMAX
Terminate the process with PID of 256:

$ kill –s KILL 256
Caution:
z The signals above can be expressed by code. For example:

-1 hang up (HUP); -2 interrupt (INT); -3 quit (QUIT); -9 terminate (KILL);
-15 Software interrupt (TERM)
The signal KILL can be replaced with "-9". This signal is the most frequently used one in the command kill,
therefore, it is of the highest priority. The default signal is 15 when no option is specified for the command
kill. Therefore, the following command can be used to terminate the above "Process with PID 256":
kill -9 256
z The command ps can be used to check the execution of the command kill by listing the PIDs of the
terminated processes.
z Using the command "kill" to terminate processes implies great danger of system data loss. DO NOT
use this command to terminate the system processes unless out of absolute necessity (for example:
the process has been deadlocked.)
B.6.6 List the Information about the Current Login Users -- who
[Description]
The command who is used to display all the login information about the users in the
current system.
[Command format]
who [option]
-b Display the date and time when the system last booted.
-m Display the relevant information of the user issuing the command (same as
the command who when executing with parameter am i)
am i Display the information about the user who logs in to the device sending out
commands.
B-36
Maintenance Manual
[Example]
Display the login information about all the users in the current system:
$ who
root pts/3 Feb 4 10:08 (10.129.16.60)
sybase pts/5 Feb 4 08:45 (10.129.28.44)
Display the information of the user who logs in to the device where the command is
sent out:
$ who am i
sybase pts/5 Feb 4 08:45 (10.129.28.44)
or:
$ who -m
sybase pts/5 Feb 4 08:45 (10.129.28.44)
B.6.7 Report the Command Location -- whereis
[Description]
The command "whereis" is used to report the location of the command’s source file,
the binary file and the help manual.
[Command format]
whereis [option] command
-b Report the location of the binary file only.
-m Report the location of the help manual only.
-s Report the location of the source file only.
command The command of which the location is to be reported.
[Example]
Report the exact locations of the files of different versions for the command "ls":
$ whereis ls
ls: /usr/bin/ls /usr/ucb/ls /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
Report the exact location of the binary file for the command "ls":
$ whereis -b ls
ls: /usr/bin/ls /usr/ucb/ls
Report the exact location of the help manual for the command ls:
$ whereis -m ls
ls: /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
B-37
Maintenance Manual
B.6.8 Display the Path of a Specific Command -- which
[Description]
The command which is used to display the location where the specific command is
executed. The result may be an absolute path or alias of the command found in user
environment variant PATH.
[Command format]
which command
[Example]
Display the position where the commands pwd, who and which are executed:
$ which pwd who which
/usr/bin/pwd
/usr/bin/who
/usr/bin/which
Note:
If the command to be located does not exist in the file, the following error messages will be displayed when
the command which is executed:
$ which qqqq
no qqqq in /usr/bin /usr/ucb /etc /export/home/sybase/bin /export/home/sybase/install .
B.6.9 Display or Set the Host Name -- hostname
[Description]
The command hostname is used to display or set the host name.
[Command format]
hostname [host name]
[Example]
Display the host name of the machine:
$ hostname
Note:
If the command hostname is executed without parameter, the host name of the equipment will be
displayed. If with parameters, the host name is to be set. However, only the super user can execute this
operation.
B-38
Maintenance Manual
B.6.10 Display the Information of the Operating System -- uname
[Description]
The command uname is used to display the operating system information. If this
command is executed without parameters, only the name of the operating system will
be displayed. If with parameters, more details of the system will be displayed.
[Command format]
uname [option]
-a Display all the information.
-i Display hardware information.
-m Display the name of the equipment hardware (It is suggested that option
"-p" shall be used instead of this one).
-n Display the network name of the equipment
-p Display the ISA of the host or the type of the processor.
-r Display the serial number of the operating system of the host.
-s Display the name of the operating system of the host (it is the default
option).
-v Display the version of the operating system of the host.
-S system_name Set the host name of the machine
[Example]
Display the the name, the version and serial No. of the operating system of the host:
$ uname-svr
B.6.11 View the Host IP Address -- ifconfig
[Description]
The command ifconfig is used to view the IP address of the host.
[Command format]
ifconfig [option]
-a Display all the address information.
[Example]
Display all the IP address information of the host:
$ ifconfig –a
B-39
Maintenance Manual
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232inet 127.0.0.1 netmask

ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu 1500 inet
129.9.169.143 netmask ffff0000 broadcast 129.9.255.255
hme0:1:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet
129.6.253.136 netmask ffff0000 broadcast 129.6.255.255
Note:
In the above example, the IP address of the host displayed is 129.9.169.143, and the logical IP address is
129.6.253.136. In a UNIX system, a network adapter can bind several logical IP addresses, by which the
communication between different network sections can be realized.
B.6.12 Recording Screen I/O Activities -- script
[Description]
The command script is used to record all the screen input and output in a script file,
from the time it is executed till the command exit is input. This command is very helpful
in programming and debugging.
[Command format]
script [option] [file]
-a Append the screen I/O content to a file (if this parameter is not set, the
screen I/O will overwrite the content of the file).
file The file used to save the screen I/O content (if no file name is specified,
the screen I/O content will be saved in the file "typescript".)
[Example]
Save the screen I/O content in the default destination file "typescript":
$ script
Script started, file is typescript
$ ps
PID TTY TIME CMD
775 pts/8 0:00 ksh
$ pwd
/export/home/sybase
$ exit
Script done, file is typescript
B-40
Maintenance Manual
Display the content of file "typescript":

$ cat typescript
Script started on Mon Feb 04 19:11:49 2002
………Omit the display content
$ exit
script done on Mon Feb 04 19:12:24 2002
Caution:
When the command exit is used to terminate the recording of the I/O of screen, please note that the script
file shall be closed. Otherwise, the script file will build up and hinder the normal operation of the system.
B.6.13 Display Current Date and Time -- date
[Description]
The command date is used to display current system date and time. Super users can
also use the command to set the system date and time.
[Command format]
date [option][+format]
-u to use Greenwich mean time.
+format to specify the command output format
Table shows the output format.
Table B-10 Output format description
Format Description
%h The abbreviation of the month, from Jan to Dec.
%j The day in a year, from 001 to 366.
%n Go to next line
%t tab
%y The last two digits of the year, from 00 to 99.
%D Output format of the date: month/date/year.
%H Hour, from 00 to 23.
%M Minute, from 00 to 59.
%S Second, from 00 to 59.
B-41
Maintenance Manual
Format Description
%T Output format of time: hour:minute:second.
[Example]
Display the current data and time of the system:
$ date
Mon Feb 4 20:26:16 GMT 2002
Display the current system date and time in Greenwich Mean Time:
$ date -u
Mon Feb 4 12:27:26 GMT 2002
B.7 Network Communication Commands

B.7.1 TCP/IP Protocol
The reason why UNIX is so widely used nowadays is its powerful networking function.
TCP/IP protocol is the default network protocol for UNIX. By now, UNIX has been the
first choice for all kinds of servers on the Internet.
The TCP/IP protocol is composed of a series of protocols, which are called the TCP/IP
protocol family. TCP/IP is the basic protocol of this family. The protocols commonly
used include:
z TCP/IP -- Transmission Control Protocol/Internet Protocol, is the basic protocol of
the protocol family.
z UDP -- User Datagram Protocol, provides the connectionless transport layer
protocol. However, the reliability of the transmission cannot be ensured.
z Telnet, a user layer protocol, offers standards for remote login.
z FTP -- File Transfer Protocol, is also a user layer protocol, offering standards for
file copying between different systems.
B.7.2 Network Communication Commands
Table shows the commands commonly used in network communicaiton.
Table B-11 Network communication commands
ping IP address Test the physical connection of the network.
telnet IP address | domain Log in to a remote computer via network.
ftp IP address | domain Transfer files via network.
finger [user name][ @ host domain name | IP View the user information using UNIX system
address] on the network.
B-42
Maintenance Manual
netstat [option] Display network status.
route [option] Modify and maintain routing table
I. Test the physical connection of the network -- ping
[Description]
When the communicaiton between the user computer and the hosts in the network is
interrupted, the command ping can be used to check the physical connection of the
network.
[Command format]
ping IP address
IP address the IP address of the hosts to which the user computer is connected.
[Example]
$ ping 129.9.0.1
129.9.0.1 is alive
ICMP (Internet Control Message Protocol) is used in command ping to check the
network connection. It sends an ICMP echo request message to a specific host, and
requests an ICMP echo response message. If the response message is not received
within a specified time, a message "Host unreachable" will be displayed on the screen.
The "Host unreachable" error may be caused by the following factors: the specified
host is invalid; the physical connection of the network is not secure; or the two
communicating parties do not support the same communicaiton protocol. To determine
the causes, the user can execute the command ping to connect with other hosts in the
same network section. If ping successfully, it indicates that the connection of both the
network and the host itself are correct. In such case, the physical connection and
operating status of the other party shall be checked. Otherwise check whether the
physical network connection of the user’s computer itself is secure or whether the
TCP/IP protocol is set correctly (for Windows’95 users).
II. Log into a Remote Computer via Network -- telnet
[Description]
Telnet is the software used to log into the remote UNIX hosts via network. Telnet
regards the local computer as a simulated terminal of the remote UNIX host, and
enables the user to log into the remote server from the local computer. After the user
successfully logs into the remote UNIX host via telnet, he will become a remote
simulated terminal user and can use his computer as if it were a real UNIX terminal. In
such case, the resource and rights the user can access and the overall operating mode
B-43
Maintenance Manual
will completely depend on the remote host settings and the access rights his login
account has.
[Command format]
telnet IP address / domain
IP address The IP address of the remote UNIX host
Domain The domain name of the remote UNIX host
[Example]
Execute telnet in the local computer and log into a remote WS named Sun. Suppose
the IP address of Sun is 129.9.169.143.
Click the [start] menu of the user computer and select [run], a dialog box will pop up.
Input "telnet 129.9.169.143" and click [ok], a Telnet window will pop up to prompt to
input UNIX user name and password, as shown below:
Sun OS 5.6
log sybase
Password: Password not echo
Last login: Wed Mar 6 10:52:34 from 129.9.28.44
Sun Microsystems Inc. SunOS 5.6 Generic August 1997
You have new mail.
$
The following steps will be the same as those on a terminal window of the Sun WS.
Caution:
Before starting telnet, make sure the TCP/IP protocol between the local computer and the remote UNIX
host is linked correctly.
III. Transfer files via network -- ftp
[Description]
Similar to telnet, which is used to log into a remote UNIX host and share its resource,
ftp is mainly used to transfer files between the local computer and the remote host.
With ftp, one or more files in the remote UNIX system can be copied to the local
computer, and vice versa.
[Command format]
ftp IP address / domain
B-44
Maintenance Manual
IP address The IP address of the remote UNIX host.
Domain name The domain name of the remote UNIX host.
[Example]
Execute ftp in local computer. Suppose the IP address of the remote UNIX host is
129.9.169.143:
Click the [start] menu in the user’s computer, and select [run], a dialog box will appear.
Input "ftp 129.9.169.143", and click <ok>, a ftp window will appear waiting for input of
UNIX user name and password, as shown below:
Connected to 129.9.169.143.
220 m2000-01 FTP server (Sunos 5.6) ready.
User (129.9.169.143: (none) : ) sybase
331 Password required for Sybase.
Password:
230 User Sybase logged in.
ftp>
Input the ftp command after the prompt "ftp>". Table shows the ftp commands
commonly used.
Table B-12 Common ftp Commands
ftp command Description

! Command Execute local command and return to ftp immediately.
? | help [command] Command help.
ascii Transfer files in ASCII format (default).
binary Transfer files in binary format.
cd [directory] Modify remote directory.
close Shut down remote connection.
Display remote directory. r-directory: remote directory.
dir [r-directory] [l-file] l-file: local file.
If there is a local file, write the result to the locla file.
get file1 [file2] Copy the remote file 1 to the local file 2.
lcd [directory] Modify the local directory.
ls [r-directory] [l-file] Same as dir, but with different display format.
mget several files Copy several remote files to local computer.
mput several files Copy several local files to remote computer.
open IPaddress | domain name Re-establish new connection.
put file1 [file2] Copy the local file 1 to remote file 2.
B-45
Maintenance Manual
ftp command Description

pwd List the directories of the current remote host.
Quit | bye Exit ftp
status Display the current ftp status
Copy all the files in "C:\mydoc" of the local computer to "/usr/local/tmp" of the remote
host:
ftp> binary
ftp> lcd c:\mydoc
ftp> cd /usr/local/tmp
ftp> mput *.*
Copy file ".login" in directory "/usr/home/rms" of the remote host to directory

"C:\temp\from" of the local computer:
ftp> ascii
ftp> lcd c:\temp\from
ftp> cd /user/home/rms
ftp> get .login
Copy all the files in "/usr/home/rms" of the remote computer to "C:\temp\from" of the
local computer in binary format:
ftp> binary
ftp> lcd c:\temp\from
ftp> cd /user/home/rms
ftp> mget *
exit ftp:
ftp> quit
B-46
Maintenance Manual
Caution:
Telnet/ftp is the application layer protocol of the TCP/IP protocol family, which works in the client/server
mode. The telnet/ftp program running in the local machine is actually the telnet/ftp client program. It
connects to the server program in the remote host via TCP/IP protocol and works in cooperation with it.
Any system that has the telnet/ftp server-side software installed can serve as a remote host as mentioned
above. The default network protocol of UNIX is TCP/IP, but it also supports telnet/ftp. As a UNIX host has
both the telnet/ftp server-side software and client-side software installed, it can serve either as a
telnet/ftp client or a telnet/ftp server.
IV. Viewing information about online users -- finger
[Description]
The command "finger" is used to view information about the online UNIX system users.
[Command format]
finger [user name][@host domain|IP address]
user name User that has currently logged onto the local system.
host domain UNIX host domain
IP address IP address of the UNIX host
[Example]
Table shows a few examples of finger commands.
Examples of finger commands
Examples Description
$ finger View information about all local users.
$ finger root View information about root user.
$ finger @omcsyb2 View information about all users in host "omcsyb2".
View information about all users in host
$ finger @omcsyb2.huawei.com.cn
"omcsyb2.huawei.com.cn".
$ finger abc@omcsyb2 View information about user "abc" in host "omcsyb2".
$ finger abc@129.6.114.202 View information about user "abc" in host "129.6.114.202".
V. Display network status -- netstat
[Description]
B-47
Maintenance Manual
The command "netstat" is used to display current network status. It is a powerful

command though a little complex in format. Here we’ll just introduce some common
applications of it.
[Command format]
netstat [options]
1) View all sockets and routing tables (netstat [-anv])
-a Display all socket information
-n Display information in number, or in logical name if this parameter is not
specified.
-v Display information about sockets and routing tables of the additional
information.
2) View IP address of the network adapter (netstat [-i][-I interface][interval])
-i Display information about the network interface
-I interface Specify an interface, for exmaple: hme0:1
interval Time intervals
3) View routing table status (netstat -r [-anv])
-r Display information about the routing table
-anv Same as 1)
4) View broadcast information (netstat -M[-ns])
-M Display broadcast routing tables
-s Summarize status of each protocol
5) View DHCP status (netstat -D[-I interface])
-D DHCP information
[Example]
Execute the command "netstat –rn" to view information about the routing table
root@ts-007 # netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface
10.105.28.0 10.105.28.202 U 4 2 hme0
10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 896 lo0
B-48
Maintenance Manual
Caution:
A router can have five different Flags: U, G, H, D and M.

U means the routing is currently available.
G means the routing goes through a gateway (router). If this flag is not set, it indicates the destination is
connected directly. Flag G is of great importance, as it distinguishes direct and indirect routing (Flag G
need not be set for direct routing). The difference is: the packet sent to the direct routing carries both
the destination IP address and the link-layer address. However, in the packet which is sent to an indirect
routing, the IP address points to the destination while the link layer address points to the gateway. (i.e. the
next router)
H indicates the routing leads to a host, i.e. the destination address is a complete host address. If this flag is
not set, it indicates the routing leads to a network, and the destination address is a network address: either
a network number or network. However, flag H indicates that the destination address is a complete host
address. If this flag is not set, that indicates the destination address is a network address (the part in the
address for the host is 0). When searching routing table for an IP address, the host address must match
exactly the destination address, while the network address has only to match the network number and
subnetwork number of the destination address.
D means the routing is created by the redirected packet.
M means the routing is modified by the redirected packet.
Reference count (Refcnt) column shows the number of active processes currently using the routing.
Connection-oriented protocol such as TCP requires fixed routing when establishing connection. If the host
establishes a Telnet connection between svr4 and slip, the reference count will be 1. When another Telnet
connection is established, the reference count will add up to 2, and go on like this.
Next column ("use") shows the number of packets sent via this routing. If we are the only user of this
routing, after we execute the command "ping" and send 5 packets, the number displayed in this column will
be 5. The last column ("interface") shows the name of the local interface.
The second row of the output is a loop-back interface, with its name always being lo0. Flag G is not set
here because the routing is not a gateway. Flag H indicates that the destination address (127.0.0.1) is a
host address other than a network address. As flag G is not set, the routing here is a direct routing and the
gateway column shows the out-going IP address.
Default routing: Each host has one or more default routings. That means if the particular routing is not
found in the table, the packet will be sent to the router. That also means current host can access other
systems via Sun router (and its "slip" link) on the internet with this routing table setting. Establishing
default routing is a very helpful function. The flag UG indicates it is a gateway, which is what we expect.
VI. Modify and Maintain Routing Table -- route
[Description]
The routing table relays IP address between different network sections, the relay
station is the gateway. The command "route" is used to modify and maintain the routing
table.
B-49
Maintenance Manual
[Command format]
route [-fnvq] command [ [modifiers] args]
route [-fnvq] add | change | delete |get [host | net] destination [gateway [args] ]
route [-n] monitor
route [-n] flush
-f Refresh routing tables for all gateways.
-n Display information in characters instead of symbols.
-v Display additional information
-q Suspend all outputs
-command It includes the following commands: "add/chang/flush" (clearing gateways
in the routing table) and "/get/monitor"
-description Destination network section. (10.0.0.0 stands for section10, and
10.11.0.0 stands for section 10.11)
-gateway Gateway IP address
net Network section IP address, for example: 10.11.12.0 stands for
section 10.11.12.
Host Host IP
[Example]
Obtaining routing information about network section 10.
root@ts-007 # route -n get 10.0.0.0
route to: 10.0.0.0
description: 10.0.0.0
mask: 255.0.0.0
gateway: 10.105.31.254
interface: hme0
flags: <UP, GATEWAY, DONE, STATIC>
recvpipe sendpipe ssthresh rtt, msec rttvar hopcount mtu expire
0 0 0 0 0 0 1500 0
Clear gateways in the routing table:

root@ts-007 # route -n flush
10 10.105.31.254 done
Routing Table:
------------------- -------------- ----- ----- ------ ---------
10.105.28.0 10.105.28.202 U 4 6 hme0
224.0.0.0 10.105.28.202 U 4 0 hme0
B-50
Maintenance Manual
127.0.0.1 127.0.0.1 UH 0 1500 lo0

root@ts-007 # telnet 10.129.3.4
Trying 10.129.3.4...
telnet: Unable to connect to remote host: Network is unreachable
Note: when the gateways in the routing table are cleared, network sections beyond
10.105.28.202/34 can no longer be accessed.
Add a routing (important):
root@ts-007 # route add 129.9.0.0 10.105.28.202
add net 129.9.0.0: gateway 10.105.28.202 //Message returned when
adding routing is successful.
Routing Table:
-------------------- ------------- ----- ----- ------ ---------
10.105.28.0 10.105.28.202 U 4 2 hme0
129.9.0.0 10.105.28.202 UG 0 0 //Newly-added routing
10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 313 lo0
Modifying routing table (important):

root@ts-007 # route change 129.9.0.0 1.2.3.4
change net 129.9.0.0: gateway 1.2.3.4
Routing Table:
-------------------- -------------------- ----- ----- -------
10.105.28.0 10.105.28.202 U 4 2 hme0
129.9.0.0 1.2.3.4 UG 0 0 //The gateway has
been modified.
10.0.0.0 10.105.31.254 UG 0 0
224.0.0.0 10.105.28.202 U 4 0 hme0
127.0.0.1 127.0.0.1 UH 0 445 lo0
B-51
Maintenance Manual
iManager M2000 Appendix C Common Operations of Sybase System
Appendix C Common Operations of Sybase

System
The appendix introduces the concepts and operations of Sybase system.
C.1 Sybase Database Concepts

Sybase SQL Server is a multi-database system, consisting of system database and
user database, both of which are built on the database devices.
C.1.1 Database Equipment
Sybase databases are built on database devices, which are created during SQL Server
installation or initiated with device initiation commands. They can be physical disks,
disk partitions or operating system files.
For user databases, new database devices can be initiated with command "disk init",
which maps physical devices or operating system files as Sybase logical database
devices. The initiated Sybase logical database devices can be used to store data and
transaction logs and specified as the default database device. If the user does not
specify a database device while building a database, the database will be built on the
default device.
The following is the format of command "disk init":
disk init name=database device name
physname=physical device name
vdevno=virtual device number
size=number
Here, name indicates the database device name, which will be used in command
"create database" and "alter database".
physname indicates the original disk partition or operating system filename.
vdevno is the ID number of database device, which should be unique in SQL Server.
size refers to a block of 2 Kbytes. For a newly-built database, the smallest size is that of
the model database, which is 1024 blocks of 2 Kbytes (2M).
Example:
1) Add a new database device with 600M space:
1> disk init name="data_dev1",physname="dev/rdsk/c0t0d0s6"
2> vdevno=2,size=300000 /* 600*1024/2 =307200(2K)*/
3> go
C-1
Maintenance Manual
2) Add a new database log device with 300M space:

1> disk init name="log_dev1",physname="dev/rdsk/c0t0d0s7"
2> vdevno=3,size=150000 /* 300*1024/2 =153600(2k)*/
3> go
C.1.2 System Database
The following databases are automatically built during Sybase database installation:
z Master database (master)
z Model database (model)
z System process database (sybsystemprocs)
z Temporary database (tempdb)
The system database is a tool that Sybase uses for system management and
maintenance. It is maintained by Sybase itself, users other than the system
administrator should not modify such databases.
I. Master database
Master database stores all the system tables and stored procedures which record
information about SQL Server, so as to implement an overall control of all the
operations of user database and SQL Server. It mainly serves as a data dictionary of
Sybase system.
Master database mainly records the following information:
z Login account (SQL Server user name).
z Information about each database in SQL Server.
z The storage space occupied by each database.
z Information about the disks and (magnetic) tapes installed in the system.
z On-going processes.
z Revisable environmental variants.
z Information about the active locks.
z Information about character set and language.
II. Model database
Model database provides a user database prototype. While building the database, SQL
Server copies the model database to the new database, and then expand it according
to user's actual needs. Modifing the model database will affect the new database, as a
result, most users are not authorized to modify or even access the model database,
since all its contents have been copied to the new database.
III. "sybsystemprocs" database
All Sybase stored procedures are stored in the "sybsystemprocs" database. When user
runs a stored procedure (starting with "sp_"), SQL Server will first search the specified
stored procedures in current database. If no result is returned, it will continue searching
C-2
Maintenance Manual
the system database, and finally the master database -- if still no result is found there.
IV. "tempdb" database
"tempdb" database provides a storage area for temparory tables and work. It is a
shared workspace for all SQL Server databases. As all the data stored here are
temporary, they will be lost when the user exits the database or when there is a system
failure.
C.1.3 Database Objects
I. Tables
In a relation database, table is the most important object -- it is the "relation" in the
therory of relation database. All the data are stored in tables, other objects just serve to
help user better manage those data.
Tables are all 2-D tables, in which a column is called a "field", and a row is called a
"record", or a datum.
The table includes system table and user table. The name of a system table starts with
"sys" and stores information about the SOL Server. In a master database, most of the
tables are system tables, which are built together with the master database.
Furthermore, each user database comes with a subset of system tables, i.e. system
tables exist both in master database and user database.
For example:
System tables that can only be found in master database are: sysconfigures,
sysdatabases, sysdevices, syslogins, etc.
System tables that exist both in master database and user database are: sysalternates,
syscolumns, sysindexs, syslogs, sysobjects, sysusers, etc.
II. Stored procedures
Stored procedure is the SQL sub-sample procedure written in T-SQL language and
stored in SQL Server at user's service. Different from common SQL statements and
batch processing statements, the stored procedure is a set of compiled SQL
statements and flow control statements. When running a stored procedure for the first
time, the query processor of SQL Server will analyse it and generate an ultimate
scheme of execution.
There are two types of stored procedures: those automatically created during SQL
Server installation (system procedures) and those created by the user.
System procedure is used for system management and provides user with a way of
database management. The name of a system procedure starts with "sp_" and it is
stored in master database and under the control of system administrator. There are
also many other system procedures which can be run in all databases.
C-3
Maintenance Manual
Table C-1 shows some common system procedures:
Table C-1 Common system procedures of Sybase database
System Procedure Description

sp_addgroup create a user group in current database.
sp_addlogin Create a SQL Server user.
sp_adduser Add a new user in current database.
sp_changegroup Change database user group
sp_configure Configure system parameters
sp_dboption Query or change database system settings
sp_dropdevice Detele a device
sp_dropgroup Detele a group
sp_droplogin Detele an account
Query database objects and all database information, i.e. to list table
sp_help
information
sp_helpdb Query database information
sp_helpdevice Query device information
sp_helpgroup Query user group information
sp_helpindex Query information on a specified table
sp_helpuser Query User information
sp_lock Query current lock application information
sp_monitor Query SQL Server statistic information
sp_password Change login account and password
Query number of rows, columns and pages of a table as well as how
sp_spaceused
much space it takes up.
sp_syntax Query command syntax.
sp_who Query information about current user and procedure
C.1.4 SQL Server User and Their Rights
Sybase database users are divided into 2 groups: SQL Server user and database user.
When SQL Server installation completes, system will create an SQL Server user --
system administrator, with null password. System administrator has overall control of
the whole system, other SQL Server users are to be created by him.
A database user has to be an SQL Server user. Only when an SQL Server user creats a
database or is added as a certain database user, can he have access to that database.
C-4
Maintenance Manual
The database users can be divided into 3 groups:

z System administrator, who has overall control of the whole system.
z Database owner (DBO), who has full access to and manages the databases he
creates.
z Common user, who has only limited access to certain databases.
Database users can be divided into groups. A database will be assigned a "public" user
group once it is created.
I. Create SQL Server user name (or login account).
[Description]
To log on to SQL Server, the user must have an SQL Server user name (login account)
in the server. The login account is created by system administrator with command
"sp_addlogin".
[Command format]
sp_addlogin login name, password [, database name][, language][, full name]
login name SQL Server user name (login account)
password Required, and must be at least 6 characters long.
database name Optional parameter, which specifies the database automatically
assigned for use when user logs on to the system. (If it is not speicified, master
database will be used as default. To specify this parameter, the user must be registered
as the default database user, otherwise he will not be able to use the database after
logging in.)
[Example]
Set up an SQL Server user account, the user name is "Hello", password: "password" (at
least 6 characters long), and the full name is "Hello Server":
1> sp_addlogin Hello,password,null,null,"Hello Server"
2> go
Password correctly set.
Account unlocked
New login created.
(return status = 0)
The following command is used to view the information about the new user "Hello".
1> select * from syslogins
2> go
II. Create a database user name
[Brief introduction]
C-5
Maintenance Manual
Likewise, to access the SQL Server database, the user must have an user name
registered in the database, which must not be the same as the login name. Different
user names can be assigned for different database. A number of users can share one
SQL Server login account, and a number of SQL Server login accounts may have the
same database user name.
[Command format]
sp_adduser user name [, alias[, user group name]]
user name: the login name when user logs on to the SQL Server.
Alias: the user name in the database. If it is not specified, the SQL Server login name
will be used in stead.
User group name: the group to which the user belongs. If the group name is not
specified, the user will be automatically added to the "public" user group; if it is specified,
the user will be added in both the specific user group and the "public" user group.
[Example]
Adding SQL Server user "Hello" as user of database "aaa", his alias being "Helloaaa",
belonging to user group "china".
Process:
1) Open database "aaa";
1> use aaa
2> go
2) Query user group information, check if user group "china" exist -- suppose it does
not exist.
1> sp_helpgroup
2> go
Group_name Group_id
------------------------------ --------
public 0
(1 row affected)
(return status = 0)
3) Query user information in the system table "sysusers", check if the database user
"Helloaaa" exists -- suppose it does not exist.
1> select * from sysusers
2> go
4) Add user group "china"
1> sp_addgroup china
2> go
New group added.
(return status = 0)
C-6
Maintenance Manual
5) Add user "Hello" as the user of database "aaa" and his alias is "Helloaaa",
belonging to user group "china".
1> sp_adduser Hello,Helloaaa,china
2> go
New user added.
(return status = 0)
View information about the database user.
1> sp_helpuser
2> go
Users_name ID_in_db Group_name Login_name
----------------- -------- ----------------- -----------------
Helloaaa 3 china Hello
dbo 1 public sa
(return status = 0)
Note:
To delete the above newly-added database user (with alias "Helloaaa" belonging to user group "china")
and the SQL Server user (with login account "Hello"), follow the steps below:
Open database;
1> use aaa
2> go
2. Delete database user with alias "Helloaaa";
1> sp_dropuser Helloaaa
2> go
User has been dropped from current database.
[return status=0
View database user information;
1> sp_helpuser
2> go
Users_name ID_in_db Group_name Login_name
----------------- -------- ----------------- -----------------
dbo 1 public sa
[Startup]
Delete user group "china";
1> sp_dropgroup china
2> go
Group has been dropped.
(return status = 0)
5. Query user group information;
sp_helpgroup
2> go
C-7
Maintenance Manual
Group_name Group_id
------------------------------ --------
public 0
(1 row affected)
(return status = 0)
Open master database;
1> use master
2> go
7. Delete login account "Hello";
1> sp_droplogin Hello
2> go
Account locked.
Login dropped.
(return status = 0)
8. Check the user registration information from “syslogins” and we can see that the login name "Hello" has
been deleted.
1> select * from syslogins
2> go
C.2 Common Operation of Sybase Database System

Sybase Database system provides the following commands for user to access,
manage and maintain SQL Server:
z isql The standard Sybase interface, also used a lot in batch processing
commands.
z bcp For data import and export between SQL Server tables and system
files.
z showserver: Used to check if SQL Server is running, (if not, use command
"startserver" to start it; command "shutdown" can be used to shut the SQL
server down if it is running).
z startserver Start SQL Server
z shutdown Shut down SQL Server
C.2.1 isql
isql is a frontground tool of Sybase system, and also the most fundamental utility based
on characters used for accessing SQL Server. It establishes connection to the server
and send T-SQL commands to it. All SQL query language and system stored
procedures are executed in isql, and the results will be displayed on the screen.
C-8
Maintenance Manual
I. Start up isql
[Description]
isql can be started in Unix system command mode.
[Command format]
isql [Options]
[Option description]
-U username One of login accounts allowing user to access SQL Server.
-P password The password allowing user to access the current SQL Server.
-S Server The name of specified SQL Server which is allowed to link with user.
-i inputfile Specify the input file name.
-o outputfile Specify the output file name.
-w column_width Set up screen volumn width for output.
[Example]
Start isql as user "sa" and the password for current SQL Server access is "1234":
$ isql -U sa -P 1234
or:
$ isql -U sa
Password: (password does not display)
Note:
z In the above example, the user name and password behind –U and –P can use some other characters
than spaces. For example:
isql -Usa -Pserver1234
z If starting normally, isql will display a command prompt "1> " like an operating system. Here "1" is the
command line number -- when multiple lines of commands are typed in, prompt "2> ", "3> " etc. will
appear to indicate the number of command lines until they are submitted to the Sybase system for
execution. End a command with "go" when typing is finished, the Sybase system will begin executing
and display the result, or output the result to a specific file. If there is a mistake in the command line,
use command "reset" to clear the query buffer and return to prompt "1> ".
z If isql starts properly, the Sybase Server should also have started successfully. Of course, the reasons
why isql does not start up properly are complex: it could be either the Sybase Server is not running, or
the user has typed in incorrect login name or password.
II. Exit isql
[Description]
C-9
Maintenance Manual
To quit isql, type "quit" or "exit" on isql command prompt.

[Command format]
quit (or exit)
[Example]
Quit isql enviornment:
1> quit
$
or:
1> exit
$
C.2.2 bcp
[Description]
Batch copying command "bcp" is used to copy database tables to the operating system
files or vise versa. This is a quick and convenient way of data transfer between
database tables and operating system files.
[Command format]
bcp [[database.]owner.] database tables {copy to in|out} data files [optional]
-f formatfile It means the user has saved a format file (extension: ".fmt") when
processing the same table last time which includes the full path.
-U username Allow user to specify a registration name when linking to the server (the
default value is the user name identified by the user environment.)
-P password Allow user to set the current SQL Server password. (If it is not specified
here, the system will prompt the user to input a password when logging on.)
-S Server Allow user to specify the SQL Server name he is trying to link. (If the
server name is not specified, the $DSQUERY value will be used; if $DSQUERY value is
not available, "Sybase" will be used.)
-c File types (for example: c-char, t-text, i-int etc.)
Database: The database in which the table is.
Owner: The owner of the data table to be copied.
Database table: Data table to be copied.
Copying direction in/out: Copying direction ("in" means from system files to data tables; "out"
means from data tables to system files).
C-10
Maintenance Manual
Data files: Source data files or target data files (depending on the copying direction),
including the full path and file description.
[Example]
Backup table "history" in database "warn" as "history.dat" (file type: char):
$ bcp warn.. history out history.dat -U sa -P 1234 -c
Starting copy...
Caution:
If the copying direction of the above command is changed from "out" to "in", it will restore the data table.
C.2.3 Showserver
[Description]
Command "showserver" can be used to show the SQL Server currently running, but
remember the user here must be a Sybase user.
[Command format]
showserver
[Example]
Show SQL Server currently running in this machine:
$ showserver
UID PID PPID C STIME TTY TIME CMD
sybase 204 203 1 Feb 19 944: 19 /home1/sybase/bin/dataserver -ssybserver
-d/dev/rdsk/c0t0d0s4 -e/home1/sybase/i
sybase 208 206 0 Feb 19 0: 00 /home1/sybase/bin/backupserver
-Ssybserver_back -e/home1/sybase/install/sybserv
The above information indicates that the active/standy server have both started.
Caution:
If command "showserver" is executed while SQL Server is running, system will print all the above
information; otherwise, only the title will be printed.
C-11
Maintenance Manual
C.2.4 Startserver
[Description]
Command "startserver" is used to start SQL Server.
[Command format]
startserver [Options]
-f run_serverfile Specifying a run-server file. (This file is referenced each time SQL
Server restarts. Its name in the machine is "RUN_sybserver" or
"RUN_sybserver_back".)
-m Starting SQL Server in the single-user mode, which is used to restore master
database.
C.2.5 Shutdown
[Description]
The system administrator can use command "shutdown" to shut down SQL Server or
Backup Server. This command is used in the "isql" enviornment.
[Command format]
1) Shut down SQL Server
shutdown [Options]
2) Shut down Backup Server
shutdown Backup Server [Options]
with {wait|nowait} Controlling whether the system shuts down immediately or not
(Parameter "with nowait" will skip the checkpoint operation and shut down the
system straight away, as a result it will take much more time and efforts for the
system auto-restoration to complete when it reboots next time. Parameter "with
wait" does the opposite.)
Backup Server Name of Backup Server
C-12
Maintenance Manual
Note:
z Always shut down the backup server prior to the active server.
z If no server name is specified after "shutdown" in the command line, the SQL Server currently running
will be shut down. On "shutdown", SQL Server will do the following:
Prohibit all user login, except the system administrator
Perform “checkpoint” operation: saving all the modified pages from memory to disk.
Wait until all SQL Server statements or procedures finish.
Shutting down SQL Server in this way will minimize the auto-recovery workload when SQL Server reboots.
z By default, Backup Server will shut down with parameter "with wait", so that the system will finish all
the on-going data transfer and loading before terminating the Backup Server procedure. On receipt of
the "shutdown" command, Backup Server will stop processing any new data transfer or loading
session.
C.3 T-SQL
T-SQL (Tansact-SQL) is a kind of enhanced SQL (Structured Query Language), which
is compliant with IBM's SQL and most of other SQLs. It has been expanded on the SQL
basis. Lots of new functions have been included while users' dependency on the
programming lauguage has been minimized.
Standard SQL was originally considered as a query and execution language other than
a programming language. As an expanded SQL, T-SQL has included new features
such as program flow control structure, local variants while allowing DBA to create
stored procedure and trigger, etc.
Standard SQL consists of Data Definition Language (DDL), Data Manipulation
Language (DML) and Data Control Language (DCL). In this section, we'll mainly
discuss DDL and DML.
C.3.1 Data Definition Language (DDL)
Data Definition Language is mainly used to create, modify and delete database objects.
I. Creating objects -- create
Here we'll only discuss creation of tables and indexes.

1) Creating tables
create table table_name(column_1 datatype,…,column_n datatype)
For example: to create a table named "teachers", which includes three fields:
teacher_name (char type, 18 characters long), phone (char type, 12 characters
long) and salary (float type).
C-13
Maintenance Manual
1> create table teachers (teacher_name CHAR(18),phone CHAR(12), salary

FLOAT)
2> go
2) Creating indexes
create index index_name on table_name(column_1,…,column_n)
For example: to create an index file "names" on filed "teacher_name" in table
"teachers".
1> create index names on teachers (teacher_name)
2> go
II. Deleting objects -- drop
Here we'll only explain the deletion of tables and indexes.

1) Deleting tables
drop table table_name
For example: to delete the above new table "teachers":
1> drop table teachers
2> go
2) Deleting indexes
drop index table_name.index_name
For example: to delete the above new index file "names":
1> drop index teachers.names
2> go
III. Clearing tables -- truncate
Command "truncate" will only empty the table while keep its structure.Be careful to tell
it apart from command "drop".
truncate table table_name
C.3.2 Data Manipulation Language (DML)
Data Manipulation Language performs operations such as query, insertion,

modification and deletion of data. Details about each of them are given below.
I. Data query -- select
Command "select" can be used to query table records. It is run in isql environment.
For example: to query records in tabel "history" of database "warn":
1> use warn
2> go
1> select * from history
2> go
C-14
Maintenance Manual
II. Data addition -- insert
Command "insert" can be used to add new data (records) to the existing table. It is also
run in isql environment.
For example: to add a new record in table "teachers":
1> insert into teachers(teacher_name,phone,salary) values
('wangjie','3340546',3000)
2> go
III. Data update -- update
Command "update" is used to update records in the existing table. It is also run in isql
environment.
For example: to update zhanglin's telephone number to 3356789 in table "teachers":
1> update teachers set phone='3356789' where teacher_name='zhanglin'
2> go
IV. Data deletion -- delete
Command "delete" is used to delete specific table records. This command is also run in
isql environment.
For example: to delete records of wangjie in table "teachers":
1> delete teachers where teacher_name='wangjie'
2> go
Caution:
The "where" conditional clause plays an important role in the above commands. For example: to query
names of schoolgirls below 20 in age in table "students", the following commands are suggested:
1> select name from students where age<20 AND sex=F
2> go
C.3.3 Data Control Language (DCL)
Data Control Language is mainly used to monitor, manage and control user access to
the database as well as to grant and revoke user rights in database system. In the
database system, user rights that may be granted and revoked include:
1) System administrator
System adminstrator can grant other users the right to "create database" and
make them the Database Owner (DBO).
C-15
Maintenance Manual
2) User Database Owner

The rights that a Database Owner can grant other users to manipulate his own
database are shown in Table C-2.
Table C-2 The rights that a Database Owner can grant other users:
Rights to grant Description

create table creating a table
create default creating a default gateway
create rule creating rules
create procedure creating stored procedures
create view creating views
dump databse dumping database
dump transaction dumping transaction logs
3) Database object owner

The rights that a Database object owner can grant other users are shown in Table
C-3.
Table C-3 The rights a Database objects owner can grant other users:
Rights to grant Description

select Querying records
insert Adding records
update Updating records
delete Deleting records
I. Grant
There are two types of user right granting: one is to grant user rights to operate the
database objects, which include "select", "insert", "update", "delete", "execute" and
"reference"; the other is to grant user rights to use commands such as: "create
database", "create procedure", "create rule", "create view", "dump database"
and "dump transactiom", etc.They will be described seperately in the following
sections.
z The following is the command format of granting user right for database objects
operation:
grant {all | permission_list}
on {table_name [(column_list)]|
C-16
Maintenance Manual
Host Name
stored_procedure_list}
to {pubic | name_list}
[with grant option]
In the above commands, parameter "all" means to grant all the rights to a specific
user or user group; parameter "permission_list" can be a combination of any or all the
permitted operations of the database objects (seperated by a comma).
The "on" clause is used to specify database objects to be operated, which can be
either a chart, a view or a stored procedure.The user rights granted to opearte
different database objects are shown in Table C-4.
Table C-4 The user rights granted to opearte different database objects
Database system Operation rights that may be granted

table select, update, insert, delete, reference
view select, update, insert, delete
column select, update
stored procedure execute
When parameter "public" is specified in the "to" clause, relevant rights will be
granted to all the users in group "public"; while parameter "name_list" can specify
either a user name or a user group name.
Parameter "with grant option" allows the authorized user to grant his rights to
other users.
z The following is the format of granting user rights for using specific commands:
grant {all | command_list}
to {public | name_list}
In the above commands, parameter "command_list" can be a combination of any or
all the operations permitted by the database owner (seperated by a comma).
z create database
z create procedure
z create rule
z create view
z dump database
z dump transactiom
C-17
Maintenance Manual
Caution:
Since only the system administrator can grant the right of running command "create database" to
other users, only he can specify parameter "all".
For example: to grant user "bob" and "john" the right to access the tabel
"teachers":
1> grant select on teachers to bob, john
2> go
Right revoking
Right revoking is a counterpart to right granting, which can also be divided into
revoking right of database object operation and revoking right of using commands:
z The following is the command format of revoking user rights for database object
operation:
revoke [ grant option for ]
{all | permission_list}
on {table_name [(column_list)]|
view_name [(column_list)]|
stored_procedure_list}
from {pubic | name_list}
[cascade]
In the above commands, parameter "grant option for" is used to revoke the
rights that an authorized user may grant to other users, if such rights have been
granted, select parameter "cascade" to revoke all such rights granted once and for
all.
z The following is the command format of revokign user rights for using specific
commands:
revoke {all | command_list}
from {public | name_list}
For example: to revoke all the rights to operate data table "teachers" which are
granted to the "public" user group:
1> revoke all
2> on teachers
3> from public
4 > go
C-18
Maintenance Manual
C.4 Sybase Database Backup and Restoration

Sybase database provides two types of database restoration functions: one is system
automatic restoration and the other is manual restoration.
z System automatic restoration is a protective measure in case of system failure, the
system automatic restoration runs each time SQL Server reboots. System
automatic restoration ensures that all the data are saved to the database devices
before system failure, and those unfinished tasks will be deleted.
z The manual restoration is accomplished through loading database from other
places with command "dump" and "load". In Sybase database, backup is usually
called "dump", and restore called "load" – by the names of these two commands.
Caution:
While carrying out database backup and restoration, the backup server must be running.
C.4.1 System Software Failure Restoration
System automatic restoration is a kind of protective measure accomplished by

rebooting SQL Server in case of a system software failure.
The system will first try to restore the master database, then the model database, then
the temporary database and finally the user database. The restoration mechnism will
check the transaction logs in each database. If the transaction log has included the data
newer than those in the database, the restoration mechnism will use those data and
perform a roll-forward restoration, those unfinished transaction records will be deleted.
Note:
What is a transaction log
Every single change to the database is recorded in a system table, which is called a "transaction log". The
transaction log records actions such as: update, insert and delete. All changes are logged before
physical changes are made. The transaction log ensures the data can be restored to the status before
system failure occurs.
C.4.2 Backup Database and its Transaction Log
Data backup is the most simple way of restoring important data lost as a result of
database or table corruption, device failure or user mistakes. To keep the data as new
C-19
Maintenance Manual
and updated as possible, data backup actions should be conducted as often as

possible.
Data backup should be conducted when the system is relatively not so busy, this will
ensure the integrity and accuracy of the data.
The following is the command format for data backup:
dump database database_name to filename | device
For example: to backup database "aaa" straight to system file "aaabak":
1> dump database aaa to aaabak
2> go
The following is the command format for transaction log backup (incremental backup):
dump transaction database_name to filename | device [with truncate_only | with
no_log | with no_truncate]
Parameter "with truncate_only" and "with no_log" have the same function – deleting
transaction logs; parameter "with no_truncate" will keep and backup the whole
transaction log (i.e. all that happened since last "dump transaction").
For example: to backup the transaction log of database "aaa" to system file "aaalog":
1> dump transaction aaa to aaalog with no_truncate
2> go
Caution:
z It is pointless to backup transaction logs before backing up database. Generally, it is not necessary to
backup database so often as transaction log, for it takes less space and time to backup transaction log
than to backup database.
z Transaction log restoration should only be done after the backup of database is completed. When the
database is restored, user can start to restore one or more transaction logs. The transaction logs
should be restored in correct order in which they are dumped. SQL Server will check the time stamp of
each restored database and each transaction log for correct order.
C.4.3 Database Restoration
To restore the destroyed database, follow the steps below:

1) Use command "dump transaction" with parameter "no_truncate" to dump the
user database transaction log.
2) Use command "drop database" to delete the detroyed database.
C-20
Maintenance Manual
3) Build a new database with the same structure as that of the destroyed database.
(as for OMC Server database, OMC Server comes with a database rebuilding
program, use it to rebuild the database instead of using command "build".)
4) Use "load database" to reload the database.
5) Use "load transaction" to reload the transaction log.
The following is the command format to reload the database:
load database database_name from file_name | device
The following is the command format to reload the transaction log:
load transaction database_name from file_name | device
For example: to restore database "aaa" with the database files and transaction log
files:
Follow the steps below:
6) Restore database:
1> load database aaa from aaabak
2> go
7) Run command "online" to set the database in the normal working status after it is
restored:
1> online database aaa
2> go
8) Restore transaction log:
1> load transaction aaa from aaalog
2> go
9) Delete transaction log:
1> dump transaction aaa with truncate_only
2> go
Caution:
z If command "dump transaction with no_truncate" is used alone too often, the transaction log will build
up as it is kept. To fix this, run "dump transaction with truncate_only" to delete the transaction log
every time you run command "dump database" and "dump transaction with no_truncate".
z Command "load" will not work if the database is currently being used by other users.
z It will take more time to restore a database than to backup it.
C-21
Maintenance Manual
C.4.4 How to Monitor Transaction Log Space
I. Use system stored procedure "sp_helpdb"
For example: to monitor the transaction log space of database "warn":

1> sp_helpdb warn
2> go
II. Use system stored procedure "sp_spaceused"
The command format:

sp_spaceused tablename
For example: to query how much space table "history" takes up in database "warn":
1> use warn
2> go
1> sp_spaceused history
2> go
III. Use command "dbcc"
Refer to the following command format:

dbcc checktable (tablename)
For example: to query information about table "history":
1> dbcc checktable(history)
2> go
Checking history
The total number of data pages in this table is 4707.
Table has 35437 data rows.
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.
C-22
Maintenance Manual
iManager M2000 Appendix D Maintenance of UNIX Operating System
Appendix D Maintenance of UNIX Operating

System
In this appendix, we are going to focus on the routine maintenance and failure
processing procedure of UNIX operating system.
I. What to Do if the Password of the Sun Server is Lost
What to do if the root password of the Sun Server is lost?

Start the workstation with a Solaris startup disk and then mount the hard disk. Modify
file "shadow" in directory "etc" and delete the password field in the "root" item, this will
set the password to null. Reboot the computer and log in with null password as root
user, and then reset the root password. Follow the process below:
1) Insert the Solaris startup disk in the CD-ROM;
2) Type <STOP+A>
3) On prompt "OK", type "boot cdrom –s" /*This will boot the computer from
CD-ROM*/
4) Type "cd /tmp/root"
5) Type "mkdir /tmp/root/xxx"
6) Type "mount /dev/dsk/c0t0d0s0 /tmp/root/xxx" /*where c0t0d0s0 is the root disk*/
7) Execute "csh"
8) Type "setenv TERM vt220"
9) Type "cp /tmp/root/xxx/etc/shadow /tmp/root/xxx/shadow/shadow.bak"
10) Type "vi /tmp/root/xxx/shadow", and delete the password field in the "root" entry.
11) Reboot and login as root user, reset the password.
II. How to Set the Shared Memory
Add "set shmsys:shminfo_shmmax=XXX" in the last line of the file "system" under the
directory of “/etc/”.
Here XXX stands for the size of the shared memory. (Unit: byte, the size of shared
memory should be all or half of the size of total memory. For example: if the total
memory is 512M, the shared memory setting shall be 512*1024*1000=524288000
bytes.)
III. Why can’t Log in to the Sun Solaris System
Why can’t log in to the Sun Solaris system as root user in the remote X-win pro mode?
When user logs on as root user to the terminal, script "/etc/default/login" runs
automatically. This will prevent logging on as root user to the terminal. To correct it, find
the following line in the script and change it as remark:
D-1
Maintenance Manual
#CONSOLE=/dev/console
IV. Unable to Log in to the System While Using FTP
Unable to Log in to the System as root user while using FTP:

Check "/etc/ftpusers", if "root" is found there, remark or delete it
V. How to Check Whether the Network Configuration is Successful
How to check whether the network configuration is successful in Solaris:

Check it with command "ifconfig -a":
If the binding of network adaptor with IP is successful – the IP address is assigned a
valid value other than 0.0.0.0, the network adaptor is generally configured correctly, go
on and check if the network media (cables, RJ45 connector, etc.) is in good condition.
VI. Why can’t Add Logical Addresses
In Solaris 8, why can’t add logical addresses with command "ifconfig hme0:1
xxx.xxx.xxx.xxx up"?
Solaris 8 has made a few changes to the command "ifconfig". Be sure to execute the
following line before executing "ifconfig":
ifconfig hme0:1 plumb
VII. How to Bind Two IP Addresses
How to bind two IP addresses in one network adaptor automatically on system startup?
Create a new file "/etc/hostname.hme0:1", add the second IP address in it, or write a
startup file and put it in directory "/etc/rc2.d/S99setip", add the second IP address in it
and save it as an executable.
VIII. How to Configure Network Installation
Network installation was not included during the system installation, and now it needs
to be completed, but there is only lo0, no hme0:
1) Touch an empty file "hostname.hme0" in directory "/etc";
2) Reboot with command "reboot –r";
3) In directory "/etc", modify file "hosts".
IX. How to View System Software Information in Solaris
You can execute the command "/usr/bin/pkginfo", or the command "/usr/bin/prodreg". A

graphic interface will display the registered products in a tree chart.
X. How to Get the Current Operational Statistics
How to get the current operational statistics, such as CPU usage, IO volume and free
hard disk space, etc.?
D-2
Maintenance Manual
There are many such commands, for example: "vmstat" and "sar"; "iostat", "df", "du"
are used to check the hard disk status.
XI. How to Change the Shell of “root” User
Execute command "chmod 666 /etc/passwd" (be sure to assign the right for disk writing
to ordinary users. )
Execute command "vi /etc/passwd"
root:x:0:1:Super-User:/:/sbin/sh
the last field is the shell of root user, make sure the program is there before making
changes to it.
XII. How About the Replacement of the Patch
If a patch with ID: 105181-15 is needed, can ID: 105181-19 can be used as a
substitute?
Yes, the last two digits stand for the version number of the same patch.
XIII. Why There is Often a Prompt Saying "Pty is not available"
Change the maximum users number: In directory "/etc/system", set it with parameter
"maxusers", the biggest is 2048. If no setting is found here, the default user number will
be the same as the system memorey (calculated by M, and the maximum is 1024).
XIV. What Command can be Used to Obtain the Patch List
In a Sun workstation, what command can be used to obtain the patch list?
Command "patchadd –p"
XV. What Commands are Used to Check the Status of the Workstation
In a Sun workstation, what commands are used to check the status of disk, tape
recorder, network adapter and swap area?
z Tape recorder: mt -f /dev/rmt/n status
z Disk: fsck
z Network adapter: ndd -get /dev/hme link_status
z Swap area swap -s
XVI. How to Set Dynamic IP
To set dynamic IP, proceed as follows:

1) Edit file "/etc/hosts", delete the existing fixed IP:
2) Edit or create a file "/etc/dhcp.Interface" (for example: dhcp.hme0) and empty it. If
the file does not exist, create it.
3) Locate file "/etc/defaultrouter", also delete it.
4) After computer rebooting, IP address and gateway will be automatically assigned.
D-3
Maintenance Manual
XVII. How to Set Auto-run Scripts
In directory "/etc/rcX.d", create a new file "SxxName", change it into an executable.

In the name "SxxName", Sxx is the startup script which needs to be executed when
entering this running level, while Kxx is the script which needs to be executed when
switching running level and exiting current running level. The xx is the startup sequency
number, the smaller it is, the higher priority it has to run. For example: S10 runs prior to
S50, and K20 runs prior to K30.
XVIII. How to Check a Patch
#showrev -p
Check if the operating system has got relevant patches.
XIX. How to Check Whether the System has Power Management
Use command "vi" to check file "/etc/power.conf", see if there is a string "noshutdown"
in there.
XX. Is it Possible to Launch a Remote Telnet Login as “root” User
Use command "vi" to check file "/etc/default/login", see if there is an # before "console".
User can login remotely if “#“does not exist.
CONSOLE=/dev/console
D-4
Maintenance Manual
iManager M2000 Appendix E File Description of M2000 System
Appendix E File Description of M2000 System
The appendix describes the files of M2000 system according to its directory structure.
E.1 Directory structure

Table E-1 describes the specific directory structure and files.
Table E-1 Directory structure and file description of M2000 system
Authority
description
The root directory of M2000
${HOME}=/export/home/m2000 m2000/staff drwxr-xr-x
system.

${HOME}/bin m2000/staff drwxr-xr-x executable files and common tools
of program are stored.
The directory under which data files
${HOME/data m2000/staff drwxr-xr-x and configuration files that change
regularly are stored.
database files required for system
${HOME}/lib m2000/staff drwxr-xr-x running are stored. You are
prohibited from modifying files in
this directory.
configuration files of M2000 system
${HOME}/etc m2000/staff drwxr-xr-x are stored. The contents of files
under this directory are generally
invariable.
The directory under which log files
of system running are stored. Each
${HOME}/log m2000/staff drwxr-xr-x
service process has its own log file
named in the format of *.log.
The system script directory
including scripts for establishing
${HOME}/script m2000/staff drwxr-xr-x
service database tables and
importing service data.
The directory under which scripts

${HOME}/script/common m2000/staff drwxr-xr-x for establishing common service
database tables are stored.
${HOME}/script/configsvr m2000/staff drwxr-xr-x for establishing configuration
server database tables are stored.
E-1
Maintenance Manual
Authority
description
${HOME}/script/pmsvr m2000/staff drwxr-xr-x for establishing performance server
${HOME}/script/timersvr m2000/staff drwxr-xr-x for establishing timer server
${HOME}/script/commonsvr m2000/staff drwxr-xr-x for establishing common server

${HOME}/script/alarmsvr m2000/staff drwxr-xr-x for establishing alarm server
The directory under which all data
${HOME}/backup sybase/dba drwxr-xr-x
backed up regularly are stored.
The buffer directory of the alarm
report interface used for the
${HOME}/send m2000/staff drwxrwxrwx
interface of the third-party network
management system.
E.2 File Description

The following describes the files and scripts under each directory in detail.
E.2.1 ${HOME}/bin
The files under this directory include:

z monsvrd: Executable file of monitor process server
z alarmsvrd: Executable file of alarm server
z alarmsend: Executable file of alarm report server
z configsvr: Executable file of configuration server
z commonsvrd: Executable file of common server
z pmsvrd: Executable file of performance server
z switch: Executable file of software bus module
z timesvrd: Executable file of timer
z timersvrd: Executable file of timer server
The running of all above executable files forms the service process environment of
the M2000 system.
There are some tools for each service under this directory except the above files:
z Crypt
z cleartable
E-2
Maintenance Manual
Used to clear the history data of the pmdb database (performance database)
regularly by the crontab (system scheduled task) of the performance server. It
must be invoked under the instruction of R&D.
z initmaxobjid
Used to create network element (NE) ID upon the initial installation of the
configuration server. It is invoked by the installation script. You are prohibited from
using it separately.
z pm_table
Used by the performance server to invoke the sql script to perform operations on
the pmdb or batch copy (BCP) table data to the pmdb as the user m2000. The sql
script is invoked in the format of pm_table *.sql, and table data is batch copied in
the format of pm_table *.txt. It must be used under the instruction of R&D.
z Sqlgen
Used to create the database table upon the installation of configuration server. It is
invoked by installation script. You are prohibited from using it separately.
z addlogin
Used to create login sybase of the user m2000. It can be created automatically
during installation or created manually after installation.
z bcpout
z combcp
Used to import the static authority script into the common server. It must be used
under the instruction of R&D.
z execsql
Used to execute the sql script as the user m2000. The parameter is the name of
the sql script. It can be used separately.
z inputpasswd
Used by the alarm server to upgrade the alarm database. This command gives
operation prompt if no parameter is used.
z pminfoupdate
Used to update “data/pmmarker.dat” upon the upgrade of the performance server.
It can be used directly without parameters. You must use it in compliance with the
operation guide during upgrade. Generally You are prohibited from using this tool
separately.
z build
Used to encapsulate the database table by the configuration server as the user
m2000. It is used for table establishment or data import/export. You are prohibited
from using this tool separately.
z initconninfo
E-3
Maintenance Manual
Used to view the initialization connection information of the common server and
update the $HOME/data/connectinfo.dat. It is not allowed to execute it without
special requirement.
z switchcon
Used to view current network flow. It can be used directly without parameters.
z viewconninfo
Used by the common server to check information of history routing tables. It is
used directly without parameters.
z version
Used to obtain the complete information of the current version.
E.2.2 ${HOME}/data
Note:
All the files and scripts under the directory are not allowed to modify manually.
The files under this directory include:

z alarmexception.ini
This file, in the binary format, is used to record the information of exceptional exit
of the alarm server.
z alarmomccsn.dat
This file, in the binary format, is used to record serial numbers of current internal
alarms.
z alarmnetcsn.dat
This file, in the binary format, is used to record serial numbers of current network
alarms.
z alarmsave.ini
This editable text file is used to record conditions for saving current history alarms.
z alarmrelative.ini
This editable text file is used to record conditions related to current alarms.
z send.ini
This text file is used to record conditions for alarm report at the third-party interface.
The conditions for controlling alarm report are modified manually. The contents of
the file are as follows:
[alarmsend]
E-4
Maintenance Manual
support=1 //The control function is active. 1: alarm is reported; 0:

alarm is not reported.
savedays=2 //Days of alarm buffer.
listenport=5200 //Port No. for system monitoring. It can be changed to
other idle ports.
It is not allowed to modify this file without special requirements.

z alarmshield.ini
This file is used to save conditions for alarm prompts, that is, to record alarm
filtering conditions for sending indicator information to the client. This file only
exists after the conditions are set. It is not generated during initial installation.
z alarmconfirm.ini
This file is used to save conditions for automatic alarm acknowledgement, that is,
to record the alarms that currently can be acknowledged automatically. This file
only exists after the conditions are set. It is not generated during initial installation.
z netalarmshield.ini
This file is used to save conditions for alarm shielding in the whole network. It only
exists after the conditions are set. This file is not generated during initial
installation.
z connectinfo.dat
This file is used to save the information of history routing tables. When allocating
object IDs, the switch queries whether the client has registered in the history
routing tables. If yes, it allocates the original object ID to the client. Otherwise, it
allocates a new object ID.
z dbinfo.dat
This file is used to save the information of the current database.
z maxobjid.dat
The file is used to save the current maximum ObjectID. It must be reserved during
upgrade.
z pmalarmbuff.dat
It is the buffer queue file of performance alarm, which is used to save performance
alarms to be sent. This file is in the binary format.
z pmmarker.dat
It is the marker file of performance index list, which is used to save the incremental
marks for the update of the performance index list.
z pminside.dat
It is the internal performance parameter file, which is currently used to save
incremental numbers of performance tasks.
E-5
Maintenance Manual
E.2.3 ${HOME}/lib
All files under this directory are running files of the M2000 system. They cannot and
need not be modified manually.
E.2.4 ${HOME}/etc
The files under this directory are configuration parameter files of the M2000 system.
You can modify it only under the instruction of R&D because the modification has
impact on the running of the system.
Table E-2 lists files under the directory ${HOME}/etc.
Table E-2 Files under the directory ${HOME}/etc
SN File name Type Contents Remark

Error bits and explanation information
1 language.txt Text file
in English
Error bits and explanation information

2 language_cn.txt Text file
in Chinese No modification is
Error bits and explanation information allowed.
3 language_en.txt Text file
in English
Parameter setting of the configuration

4 pmconfig Text file
server
E.2.5 ${HOME}/backup
It is the database backup directory used for the recovery of exceptions. The system
adopts automatic backup mechanism without manual intervention.
E.2.6 ${HOME}/log
It stores the log files that records running information of each service process. This
directory must be packaged and sent back to R&D for further analysis if the system
runs abnormally. Manual intervention is not required.
E.2.7 ${HOME}/script/common
It is the directory under which scripts for creating and deleting database are stored. The
names and usage of several scripts are as follows:
z clear.sh
This script is used to delete the service database of the M2000 system as well as
all users of the M2000 system in sybase database. It is then used to add users to
the sybase database and modify some configuration parameters of sybase
E-6
Maintenance Manual
database. This script is automatically invoked by the installation script. It is not

allowed to use this script in other cases. You can invoke this script to delete the
M2000 system database using the command clear.sh server1234.
z dropdb.sql
This script is used to delete the service database of the M2000 system instead of
modifying user information and configuration parameters of the sybase database.
This differs from the previous script. You can invoke this script using the following
command:
isql –Usa –Pserver1234 < dropdb.sql
You must take the result into full consideration before executing this command.
z init.sql
This script is used to delete m2000 users from the sybase database and re-set
some options of the sybase database. This script can only be executed
successfully after the service database of M2000 system is deleted completely.
The installation script invokes this script during installation. It is not allowed to use
this script in other cases.
z crtalarmdb.sql
This script is used to delete and re-create the script of the alarm database and set
options for the alarm database. To delete the current alarm database and create a
new one, invoke this script by running isql –Usa –Pserver1234<crtalarmdb.sql.
Confirmation is necessary before you invoke this script to prevent the loss of all
alarm data.
z crtcfgdb.sql
This script is used to delete and re-create the script of the configuration database
and set options for this database. When you need to delete the current
configuration database and create a new one, you can invoke this script by
running isql –Usa –Pserver1234<crtcfgdb.sql.
configuration data.
z crtcomdb.sql
This script is used to delete and re-create the script of the command database and
set options for this database. When you need to delete the current alarm database
and establish a new one, you can invoke this script by running isql –Usa
–Pserver1234<crtcomdb.sql.
common data.
z crtpmdb.sql
E-7
Maintenance Manual
This script is used to re-create the script of the performance database and set
options for this database. When you need to re-create the performance database,
you can invoke this script by running isql –Usa –Pserver1234<crtpmdb.sql.
Make sure that the performance database is deleted when invoking this script.
z crttimerdb.sql
This script is used to delete and re-create the timer database and set options for
this database. When you need to delete the current timer database and create a
new one, you can invoke this script by running isql –Usa
–Pserver1234<crttimerdb.sql.
data of timer server.
z crtlogdb.sql
This script is used to delete and re-create the log database and set options for this
database. When you need to delete the current log database and create a new
one, you can invoke this script by running isql –Usa –Pserver1234<crtlogdb.sql.
data of log server.
z createlogtbl.sql
This script is used to delete tables and storage procedures in logdb and re-create
new ones. You can invoke this script by running execsql createlogtbl.sql.
Confirmation is required before you invoke this script to prevent the loss of all log
data.
z init.sh
This script is used to encapsulate the script createlogtbl.sql. Its function is the
same as that of the above script. You can invoke it by running init.sh server1234.
z checkdbsize.sh
This script is used to check the size of database before the service database is
created during system installation. It is automatically invoked by the installation
script.
z AlterDB.sql
This script is used to extend the space of service databases such as pmdb,
alarmdb, cfgdb, and logdb. The space of above databases can be extended to 200
MB, and that of logdb to 300 MB respectively. You can modify this script manually
to change the sizes of different databases. Then you can invoke this script by
executing the command isql –U sa –Pserver1234 < AlterDB.sql. Ensure that in
early stage the current database equipment and log equipment have enough
space for database extension.
z cront.*.sh
E-8
Maintenance Manual
The “*” denotes the wildcard. This is a scheduled task script of the M2000 system
that is processed during system installation. The operating system can invoke this
script to execute tasks regularly.
z restore.sh and restore.sql
These two scripts are used together to restore the service database of the M2000
system, that is, to export the database and restore it to the system. The
precondition is that the service database of M2000 system and other application
data are backed up under the directory of ${M2000_HOME}/backup according to
requirements and the file m2000.tar is generated. You can invoke the script
restore.sh directly as a super-user.
If you want to reload the database when the database is unloaded under the
directory ${M2000_HOME}/backup by the name of *.dat (* denotes the database
name, for example, alarmdb.dat), you can execute the command isql –Usa
–Pserver1234 < restore.sql. You must perform this operation according to the
Operation Guide under the instruction of development personnel.
E.2.8 ${HOME}/script/commonsvr
The following describes files under this directory.

z tblStaticRight.txt
This file contains the table of static rights in comdb (common database). It is
imported to the tblStaticRight of comdb and invoked automatically by the
installation script during system installation. It is not allowed to modify this file.
Otherwise, the authority of system running is affected.
z createproc.sql
This script is used to create the script of storage procedure in comdb, that is, to
delete the original storage procedure and re-create it.
Generally, it is invoked by other scripts. You can use the script execsql
createproc.sql to delete the original stored procedure and re-create it in comdb.
z createtbl.sql
This script is used to delete the original table in comdb and re-create it by
executing the script: execsql createtbl.sql. It is generally invoked by other scripts.
z init.sh
This script is used to encapsulate the script createtbl.sql and import the contents of
tblStaticRight.txt to tblStaticRight by executing init.sh server1234.
E.2.9 ${HOME}/script/timersvr

z createproc.sql
E-9
Maintenance Manual
This script is used to create the script of storage procedure in timerdb (timer
database), that is, to delete the original stored procedure and re-create it.
Generally, it is invoked by other scripts. The following script can be used to delete
the original stored procedure and re-create it in timerdb: execsql createproc.sql.
z createtbl.sql
This script is used to delete the original table in timerdb and re-create it by
executing the script: execsql createtbl.sql. It is generally invoked by other
scripts.
z init.sh
This script is used to encapsulate scripts createproc.sql and createtbl.sql by
executing init.sh server1234. This operation clears all data in the timer server.
E.2.10 ${HOME}/script/alarmsvr
Alarm scripts are encapsulated with the tool inputpasswd. They can be invoked directly
through inputpasswd, thus simplifying the processing by users. The inputpasswd can
be executed without parameters as the user m2000. The following is the prompt
information after this operation:
$ inputpasswd
valid param:
createalarmdbtbl.sql : recreate all tables and import inner alarm
updatealarmdbtbl.sql : recreate and update all tables
renewexp.sql : update all nodetypes' alarmexp file information
updateomc.sql : update the inner alarmattr file information
updatemsc33.sql : only update msc33's alarmexp information
updatebsc32.sql : only update bsc32's alarmexp information
updatehlr36.sql : only update hlr36's alarmexp information
updatechlr36.sql : only update chlr36's alarmexp information
updatecmsc61.sql : only update cmsc61's alarmexp information
updatepcu33.sql : only update pcu33's alarmexp information
updatesgsn80.sql : only update sgsn80's alarmexp information
updateggsn35.sql : only update ggsn35's alarmexp information
updatewll.sql : only update wll's alarmexp information
updatepdsn.sql : only update pdsn's alarmexp information
updatecg.sql : only update cg's alarmexp information
updateimsc.sql : only update imsc's alarmexp information
updatecbsc.sql : only update cbsc's alarmexp information
The scripts of alarm server are all text files as follows. It is not allowed to modify them
manually.
z alarmattr.bcp
It is the file of alarm mapping of all NEs invoked automatically by the system.
E-10
Maintenance Manual
z omcalarm.csv
It is the file for explanation of internal alarms. Internal alarms denote the alarms of
M2000 system instead of NEs. The system invokes this file automatically.
z alarmattr-*.bcp
The “*” stands for NE type, for example, BSC. This is the file of alarm mapping of
the NE. It is automatically invoked by the system script.
z alarmexp-*.csv
The “*” stands for NE type, for example, BSC. This is the file for alarm explanation
of the NE. It is automatically invoked by the system script.
z createalarmdbtbl.sql
This script is used to delete the table and storage procedure of the alarmdb (alarm
database) and re-create them. You must execute this script as the user m2000 of
sybase database. Running execsql createalarmdbtbl.sql can delete the table in
alarmdb of M2000 and re-create a blank table.
Generally this script is used, together with the tool inputpasswd, to re-create alarm
data table and import the contents of file for internal alarm explanation, for
example, inputpasswd createalarmdbtbl.sql. Ensure that alarm data is
processed properly before running this script. Otherwise, all the alarm data will be
lost.
z updatealarmdbtbl.sql
The function of this script is the same as that of createalarmdbtbl.sql. Generally it
is used, together with the tool inputpasswd, to re-create the alarm data table and
import the contents of files for alarm explanation of all NEs and alarm mapping file,
for example, inputpasswd updatealarmdbtbl.sql. Ensure that alarm data is
processed properly before running this script. Otherwise all the alarm data will be
lost.
z renewexp.sql
This script is used to delete the contents of the alarm mapping table alarmattr and
alarm detailed explanation table alarmexp. Generally it is used together with
inputpasswd to update the contents in alarmattr and alarmexp by executing
inputpasswd renewexp.sql.
Ensure that the file to be updated is the current explanation file. Otherwise, the
mismatch of version may result in incorrect handling for alarms of certain NE. You
must perform the operation under the instruction of R&D or the Operation Guide.
z update*.sql
The “*” stands for NE type, for example, MSC and BSC. These scripts are used to
update the alarm mapping file and alarm explanation file of the corresponding NE
by running inputpasswd update*.sql. For example, to update the alarm
E-11
Maintenance Manual
explanation file of BSC, execute inputpasswd updatebsc.sql. The precautions

are the same as those of renewexp.sql.
E.2.11 ${HOME}/script/configsvr
Note:
All the scripts under the directory are executed automatically by the system during installation and not
allowed to invoke manually.

z CrtCfgSysTbl.sql
This script is used to delete the original configuration system table of configuration
database and re-create it. It is invoked by the tool build, for example, build
CrtCfgSysTbl.sql. The data of configuration system table is lost after the script is
executed automatically by the system during installation.
z CrtTopoSysTbl.sql
This script is used to delete and re-create the topology table of the system. It is
invoked by the tool build, for example, build CrtCfgSysTbl.sql. The topology data
of configuration system will be lost after the script is automatically invoked by the
system during installation.
z CrtCfgObjTbl.sql
This script is used to delete and re-create the object table of the configuration
system. It is invoked by the tool build, for example, build CrtCfgObjTbl.sql. All
the current NE information is lost after the execution.
z CrtCfgHisTbl.sql
This script is used to delete and re-create the history object table of the
configuration system and save the configuration information of NE. It is invoked by
the tool build, for example, build CrtCfgHisTbl.sql. All the NE information saved
by the user in the server is lost after this script is executed.
z CrtTopoObjTbl.sql
This script is used to delete the topology object table of configuration system. It is
invoked by the tool build, for example, build CrtTopoObjTbl.sql. All the current
topology data is lost after this script is executed.
z CrtCfgProc.sql
This script is used to delete and re-create the storage procedure of configuration
modules. It is invoked by the tool build, for example, build CrtCfgProc.sql.
z CrtHisCfgProc.sql
E-12
Maintenance Manual
This script is used to delete and re-create the history storage procedure of
configuration modules. It is invoked by the tool build, for example, build
CrtCfgProc.sql.
z insert.sql
This script is used to insert some initial parameters of the configuration system. It
is invoked by the tool build, for example, build insert.sql.
z tbl*.txt
The “*” stands for table name. These text files are used to import the data table of
the configuration system.
z init.sh
This script is used to initialize all the table data of configuration and topology and
integrate functions of all the above scripts. It can also be used to initialize the
configuration and topology data to construct a new configuration and topology
environment by running init.sh server1234. Ensure that all data are properly
backed up and saved before running the script. Otherwise, all the data of
configuration and topology will be lost.
The scripts of the configuration system are all text files, which are run by the installation
script. It is not allowed to modify them manually.
E.2.12 ${HOME}/script/pmsvr
Note:
All the files and scripts under the directory are executed automatically by the system during installation and
not allowed to invoke manually.

z crtsystables.sql
This script is used to establish the data table of the performance server. You can
invoke this script by running pm_table crtsystables.sql. Ensure that all data of
the performance server are properly backed up and saved before running the
script. Otherwise, the data may be lost, thus affecting the running of the
performance system.
z crttsktbl.sql
This script is used to establish the performance task table. You can invoke it by
running pm_table crttsktbl.sql. Ensure that all data of the performance server is
properly backed up and saved before running the script. Otherwise, the data may
be lost, thus affecting the running of the performance system.
z dropsystables.sql
E-13
Maintenance Manual
This script is used to delete the data table of the performance database. Its
function is just opposite to that of crtsystables.sql. You can invoke it by running
pm_table dropsystables.sql.
z drop_tsktbl.sql
This script is used to delete the performance task table. You can invoke it by
running pm_table drop_tsktbl.sql. Ensure that all data of performance are
properly backed up and saved before executing the script. Otherwise, the data
may be lost, thus affecting the running of the performance system.
z *.txt
The “*” denotes the table name of the performance database. These text files are
imported to the table of the corresponding performance database. You can invoke
them by running pm_table *.txt.
E-14

U2000 Maintenance PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

U2000 Maintenance PDF

Uploaded by

Copyright:

Available Formats

Chapter 1 System Knowledge ........................................................................

Appendix E File Description of M2000 System ............................................. E-1

Manual Version T2-030373-20040928-C-1.52

Product Version V100R005

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

This manual applies to iManager M2000 V100R005.

The related manuals are listed in the following table.

The manual consists of six chapters and five appendices.

z Chapter 1 System Knowledge introduces the following aspects: requirements

z Chapter 2 M2000 Routine Maintenance provides daily, weekly, and monthly

z Chapter 4 Handling Common Failures introduces the analysis and locating of

z Chapter 5 Process Operations introduces the stop and restart operations of

z Chapter 6 Hardware Maintenance introduces how to shut down and power on

z Appendix A Handling Common Network Faults introduces the common

z Appendix B Common Operations of UNIX System lists the common

z Appendix C Common Operations of Sybase System lists the common

The manual is intended for the following readers:

The manual uses the following conventions:

III. GUI conventions

IV. Keyboard operation

Caution, Warning, Danger: Means reader be extremely careful during the

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Chapter 1 System Knowledge...................................................................................................... 1-1

Chapter 2 M2000 Routine Maintenance....................................................................................... 2-1

Chapter 3 Handling M2000 Alarms .............................................................................................. 3-1

3.1.3 Troubleshooting....................................................................................................... 3-1

Chapter 4 Handling Common Failures ........................................................................................ 4-1

4.2.9 Failed to Report Alarm Data.................................................................................. 4-12

Chapter 5 Process Operations..................................................................................................... 5-1

Chapter 6 Hardware Maintenance................................................................................................ 6-1

Appendix A Handling Common Network Faults ........................................................................A-1

A.1.4 Failure of BAM to Connect with WS .......................................................................A-4

Appendix B Common Operations of UNIX System....................................................................B-1

Appendix C Common Operations of Sybase System................................................................C-1

Appendix D Maintenance of UNIX Operating System................................................................D-1

Appendix E File Description of M2000 System ..........................................................................E-1

E.2.3 ${HOME}/lib ............................................................................................................E-6

Chapter 1 System Knowledge

1.1 Requirements on Maintenance Personnel

1.3 Related Users

1.3.1 Operating System Users

You can log in as “adaptermonitor” to monitor all adapter processes. No default

The “adapter” is the owner of adapter processes of multi-version adapters. No default

1.3.2 Database User

1.4.1 System Supporting Processes

The switch process is responsible for:

1.4.2 Service Supporting Processes

Service supporting processes include commonsvrd, configsvrd, alarmsvrd, alarmsend,

The commonsvrd is a common service process responsible for M2000 user

1.4.3 Sybase Processes

1.5 Directory Structure

Table 1-1 Directory structure of M2000 system

The directory under which

The directory under which

1.6 Environment Variables

1.6.1 Environment Variables of M2000 System

The interpretation for several major environment variables is as follows. These