Académique Documents
Professionnel Documents
Culture Documents
1-1
1-1
1-1
1-2
1-2
1-3
1-4
1-4
1-6
1-9
1-10
1-11
1-11
1-13
1-14
1-14
1-15
1-15
1-15
1-15
1-18
2-1
2-1
2-1
2-1
2-1
2-4
2-6
2-6
2-6
2-7
2-7
2-8
3-1
3-1
3-1
3-1
3-1
3-3
3-3
3-3
3-3
3-5
3-5
3-5
3-5
3-6
3-6
3-6
3-7
3-7
3-7
3-7
3-7
3-7
3-7
3-8
3-8
3-8
3-8
3-9
3-9
3-9
3-9
3-9
3-9
3-10
3-10
4-1
4-1
4-2
4-2
4-2
4-3
4-4
4-6
4-6
4-7
4-8
4-12
4-12
4-13
4-13
4-14
4-18
4-18
4-19
4-19
4-19
4-20
4-20
4-20
4-21
5-1
5-1
5-1
5-1
5-1
5-1
5-2
5-2
5-2
6-1
6-1
6-1
6-2
6-3
6-3
6-5
6-5
6-5
6-5
6-6
6-6
6-9
A-1
A-1
A-1
A-2
A-3
A-4
A-5
A-5
A-6
A-8
A-11
A-12
B-1
B-1
B-1
B-1
B-3
B-3
B-3
B-5
B-5
B-6
B-6
B-6
B-6
B-10
B-16
B-20
B-21
B-21
B-22
B-22
B-23
B-23
B-23
B-23
B-24
B-26
B-26
B-28
B-29
B-29
B-30
B-30
B-32
B-32
B-33
B-33
B-34
B-35
B-36
B-37
B-38
B-38
B-39
B-39
B-40
B-41
B-42
B-42
B-42
C-1
C-1
C-1
C-2
C-3
C-4
C-8
C-8
C-10
C-11
C-12
C-12
C-13
C-13
C-14
C-15
C-19
C-19
C-19
C-20
C-22
D-1
E-1
E-1
E-2
E-2
E-4
E-6
E-6
E-6
E-6
E-6
E-9
E-9
E-10
E-12
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.
Trademarks
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.
Related Manuals
The related manuals are listed in the following table.
Manual
Content
Organization
The manual consists of six chapters and five appendices.
z
Intended Audience
The manual is intended for the following readers:
z
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Arial Narrow
Boldface
Courier New
Description
Boldface
italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... } *
[ x | y | ... ] *
Description
<>
Button names are inside angle brackets. For example, click the <OK>
button.
[]
Window names, menu items, data table and field names are inside square
brackets. For example, pop up the [New User] window.
Description
<Key>
Press the key with the key name inside angle brackets. For example,
<Enter>, <Tab>, <Backspace>, or <A>.
<Key1+Key2>
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three
keys should be pressed concurrently.
<Key1, Key2>
Press the keys in turn. For example, <Alt, A> means the two keys should
be pressed in turn.
V. Mouse operation
Action
Description
Click
Press the left button or right button quickly (left button by default).
Double Click
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:
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
iManager M2000
Table of Contents
ii
Maintenance Manual
iManager M2000
Table of Contents
iii
Maintenance Manual
iManager M2000
Table of Contents
iv
Maintenance Manual
iManager M2000
Table of Contents
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
Maintenance Manual
iManager M2000
Table of Contents
vi
Maintenance Manual
iManager M2000
Databases
Related users
Processes
Directory structure
Environment variables
Log files
Scripts
Database Sybase
System
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 alarmdb stores alarm data of NEs and the M2000 system.
The database comdb stores security data and topology data of the M2000 system.
1-1
Maintenance Manual
iManager M2000
The database timerdb stores timing task data of the M2000 service servers.
The database logdb stores the log data of the M2000 system.
Database users
Users with different roles are defined for the M2000 server. The following details the
role of each user.
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
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
iManager M2000
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
Maintenance Manual
iManager M2000
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
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
Maintenance Manual
iManager M2000
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.
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
m2000
369
Aug 11 ?
Aug 11 ?
0:54 /export/home/m2000/bin/switch
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
m2000
384
362
Aug 11 ?
0
Aug 11 ?
0:00 /export/home/m2000/bin/timesvrd
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
iManager M2000
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
following information (two processes):
$ ps -ef|grep watchd|grep -v grep
m2000
510
m2000
1 0
511
Aug 11 ?
510
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
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-6
Maintenance Manual
iManager M2000
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
following information (two processes):
$ ps -ef|grep commonsvrd|grep -v grep
m2000 403 401
m2000 401 1 0
Aug 11 ?
Aug 11 ?
0:01 /export/home/m2000/bin/commonsvrd
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
following information (two processes):
$ ps -ef|grep configsvrd|grep -v grep
m2000 418
417
m2000 417 1 0
Aug 11 ?
Aug 11 ?
0:11 /export/home/m2000/bin/configsvrd
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
iManager M2000
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
m2000 438
1 0
Aug 11 ?
Aug 11 ?
5:50 /export/home/m2000/bin/alarmsvrd
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
following information (two processes):
$ ps -ef|grep alarmsend|grep -v grep
m2000
446
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
m2000
463
1 0
462
Aug 11 ?
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 ?
1-8
Maintenance Manual
iManager M2000
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
following information (two processes):
$ ps -ef|grep pmsvrd|grep -v grep
m2000
478
m2000
479
1 0
478
Aug 11 ?
0
Aug 11 ?
Note:
The pmsvrd involves database operations. The service data is saved in the database pmdb.
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
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
iManager M2000
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
description
Description
User/group
${HOME}=/export/home/m2000
m2000/staff
drwxr-xr-x
${HOME}/bin
m2000/staff
drwxr-xr-x
${HOME/data
m2000/staff
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
${HOME}/lib
${HOME}/etc
${HOME}/log
${HOME}/script
${HOME}/script/common
${HOME}/script/configsvr
${HOME}/script/pmsvr
m2000/staff
m2000/staff
m2000/staff
m2000/staff
m2000/staff
m2000/staff
m2000/staff
1-10
Maintenance Manual
iManager M2000
${HOME}/script/timersvr
${HOME}/script/commonsvr
Authority
description
User/group
m2000/staff
m2000/staff
Description
drwxr-xr-x
drwxr-xr-x
${HOME}/script/alarmsvr
m2000/staff
drwxr-xr-x
${HOME}/backup
sybase/dba
drwxr-xr-x
drwxrwxrwx
${HOME}/send
m2000/staff
1-11
Maintenance Manual
iManager M2000
_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
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.
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
iManager M2000
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.
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.
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.
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.
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-13
Maintenance Manual
iManager M2000
DSLISTEN=sybserver
TERM=vt100
PWD=/export/home/sybase
TZ=GMT-8
LANG=C
PATH=/usr/bin:/usr/ucb:/etc:/export/home/sybase/bin:/export/home/sybase/install
DSQUERY=sybserver
DSLISTEN=sybserver
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.
TZ=GMT-8
The first four variables and the last one are the same as those of the M2000 system.
alarmsvrd.log: The log recorded by the system for the alarm server.
1-14
Maintenance Manual
iManager M2000
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.8 Scripts
This section describes the scripts of the M2000 system.
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.
Parameters
{ start | stop }
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
iManager M2000
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.
Parameters
{ start | stop }
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.
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
iManager M2000
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.
Parameters
{ start | stop }
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.
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.
Parameters
{ start | stop }
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
iManager M2000
Precaution
Run the script as root.
Function
This script is the link of the scripts S98adaptermonitor and K44adaptermonitor.
Parameters
{ start | stop }
When to be called
It is directly invoked by users.
Storage position
Under the directory /etc/init.d.
Precaution
None.
II. S98adaptermonitor
z
Function
This script is used to start adaptermonitor automatically during system start.
Parameters
{ start | stop }
When to be called
1-18
Maintenance Manual
iManager M2000
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.
Precaution
None.
III. K44adaptermonitor
z
Function
This script is used to stop adaptermonitor in case of system start.
Parameters
{ start | stop }
When to be called
It is called when the OS starts.
Storage position
Under the directory /etc/rc1.d.
Precaution
None.
1-19
Maintenance Manual
iManager M2000
Note:
Engineers conducting the M2000 routine maintenance must get familiar with the UNIX system and Huawei
M2000 system.
Log in to the M2000 client as admin to observe the operational status of the
system.
2-1
Maintenance Manual
iManager M2000
Item
Operation instruction
Remark
T1
T2
Check
the
operational status
of the client
Configuration Management
C1
View
the
configuration
information
of
equipment in the
whole
network
through
the
centralized
configuration
management
system.
C2
Synchronize the
configuration data
manually.
Fault Management
F1
F2
Check
the
real-time
alarm
information.
Performance Management
2-2
Maintenance Manual
iManager M2000
SN.
P1
Item
Operation instruction
Remark
P2
Check
reporting
performance
tasks.
the
of
P3
Check
the
performance task
management
function.
Activate, suspend, or
delete a performance
task and check whether
the
operation
is
successful.
U1
Select
the
menu
[View/System Log] on
the M2000 remote
workstation (RWS).
Check
the
harddisk space of
the server.
df -k
2-3
Maintenance Manual
iManager M2000
SN.
Item
Operation instruction
Remark
The server time must be consistent with the
local standard time.
S2
date
mmddHHMM[[cc]yy][.
SS]
page
disk
faults
S3
vmstat 5 5
0 0 0 1054080 35400 4 16 3 15 12 0 0 15 0 0
0 398 23171 464 13 7 81
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
Item
Operation instruction
Remark
Check the
database
status.
$isql -Usa
-Pserver1234
1> sp_helpdb
2> go
2-4
Maintenance Manual
iManager M2000
SN.
Item
Operation instruction
Check the
space
of
alarmdb.
1>sp_helpdb alarmdb
Check
space
cfgdb.
1>sp_helpdb cfgdb
Check the
space
of
comdb.
1>sp_helpdb comdb
Check
space
pmdb.
1>sp_helpdb pmdb
Check the
space
of
timerdb.
the
of
the
of
Remark
2> go
2> go
2> go
2> go
1>sp_helpdb 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.
Check
backup files
of
each
database.
Remove
outdated
files.
rm *.bak
9
Check the
tape
machine.
mt status
2-5
Maintenance Manual
iManager M2000
Item
Operation instruction
Remark
In normal case, all the power indicators are on.
For example, the following power indicators
(green) are on:
Check the
system
power
indicators.
Check
system
indicators.
POWER indicator
SYSTEM indicator
DISK0-Active
DISK1-Active
Check the
hardware of
the system.
2-6
Maintenance Manual
iManager M2000
Operation instruction
Standard
Execute df k
System log
System time
Tape machine.
Remark
Optional
Operation instruction
Standard
Remark
Status of network
adapters in cluster
Operation instruction
Standard
Statuses of all dataservices are
"on". Statuses of all resource
groups and resources are "online".
#scstat -g
#pnmstat -L
2-7
Remark
Maintenance Manual
iManager M2000
Item
Operation instruction
Standard
Remark
#scstat
Whole system
Power supply
Netra fans
of
Operation instruction
Standard
/usr/platform/sun4u/sbin/
prtdiag v
2-8
Remark
Optional
Maintenance Manual
iManager M2000
FTP Connection
Illegal Login
Alarm type
Fault alarm
Event type
Internal alarm
Alarm No.
2141
3.1.3 Troubleshooting
I. Alarm Cause
The possible causes of the alarm are:
z
3-1
Alarm parameter
idle, user, kernel
Maintenance Manual
iManager M2000
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.
Modify the alarm threshold of CPU occupation rate to a higher rate at the client.
Contact Huawei technical support engineers if the alarm lasts for a long time.
Check the memory occupation of the M2000 processes to find which process
occupies the CPU for a long time.
SIZE
RSS STATE
PRI NICE
TIME
CPU PROCESS/NLWP
13M sleep
58
274
sybase
258M
63M sleep
59
8899
m2000
27M
11M sleep
58
27187 sybase
58
8922
m2000
48
8882
m2000
8836
m2000
8842
m2000
58
58
150
root
58
156
root
10
246
root
174
root
58
158
daemon
20
200
root
51
120 root
50
58
memory
swap
free
page
faults
cpu
re mf pi po fr de sr s0 s6 in sy cs us sy id
0 0 0 137128 10808 1
0 0 0 550416 4112
disk
0 1 20 14
7 1
0 96 80
0 0 0 550416
4112 4 0
0 40 40
0 5
0 0 0 550416
4112 0 0
0 8 8
146
416
96
0 0 0 550416
4112 0
0 0 0 0
138
574
101
3-2
5 12 83
0 12 88
1
0 99
0 0 100
Maintenance Manual
iManager M2000
us
id
sy
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.
If the data device space of the alarm database is insufficient, alarm data may be
lost.
If the log device space of the alarm database is insufficient, alarm data may be
unavailable.
Alarm type
Critical
Fault alarm
Event type
Alarm No.
Alarm parameter
Number of parameters: 2
Internal alarm
2143/2144
3.2.3 Troubleshooting
I. Alarm Cause
The possible causes are:
z
3-3
Maintenance Manual
iManager M2000
III. Solution
The solutions to the alarm are:
1)
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)
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)
3-4
Maintenance Manual
iManager M2000
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
Alarm type
Event type
Event alarm
Internal alarm
Alarm No.
2501
3.3.2 Troubleshooting
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.
Maintenance Manual
iManager M2000
Alarm type
Event type
Alarm No.
Alarm parameter
Number of parameters: 2
Critical
Fault alarm
Internal alarm
2704/2705
3.4.3 Troubleshooting
I. Alarm Cause
The remaining data device space of the performance database is less than 200 MB.
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)
3-6
Maintenance Manual
iManager M2000
Alarm type
Fault alarm
Event type
Internal alarm
Alarm No.
2505
3.5.3 Troubleshooting
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.
Alarm type
Fault alarm
Event type
Internal alarm
3-7
Alarm No.
2504
Maintenance Manual
iManager M2000
3.6.3 Troubleshooting
To handle this alarm, do as follows:
z
Check whether the connection between the adapter and the BAM/host (GPRS) is
normal.
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.
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.
Alarm type
Fault alarm
Event type
Internal alarm
Alarm No.
2706
Alarm type
Event alarm
Event type
Internal alarm
3-8
Alarm No.
2703
Maintenance Manual
iManager M2000
3.7.3 Troubleshooting
Perform the following operations to clear the alarm:
z
Check whether the connection between the cBSC/RAC and the M2000 is normal.
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.
Alarm type
Event alarm
Event type
Internal alarm
Alarm No.
65538
3.8.2 Troubleshooting
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.
Wrong user name and password are entered for three times.
3-9
Maintenance Manual
iManager M2000
Alarm type
Event type
Critical
Event alarm
Internal alarm
Alarm No.
2800
Alarm parameter
Two alarm parameters: illegal user
name and illegal IP
3.9.3 Troubleshooting
I. Alarm Cause
The possible causes for the alarm are:
z
II. Solution
Check whether there is illegal intrusion according to the alarm information, or contact
the system administrator.
3-10
Maintenance Manual
iManager M2000
Item
Incorrect User Name and Password
Unable to Delete M2000 Server Objects
Red Cross on NE Icon
Common platform
Configuration Management
Fault Management
Performance Management
4-1
Maintenance Manual
iManager M2000
Service Module
Item
Sybase System Installation Aborted
Failed to Display Process Status
Failed to Log in to Sybase System
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.
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
Maintenance Manual
iManager M2000
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.
II. Solution
To handle the problem, proceed as follows:
1)
Press <F6> on the RWS to display the [Running Status Monitoring] window.
In the top-right sub-window, check whether the NEs BAM IP is consistent with that
in the routing information of its corresponding 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
4-3
Maintenance Manual
iManager M2000
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.
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)
End.
Maintenance Manual
iManager M2000
II. Solution
To handle the problem, proceed as follows:
1)
Log in to the M2000 server and check whether processes of the servers exist,
using the following command.
353
m2000
376
m2000
369
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
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 ?
m2000
342
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
375
342
0:00 /export/home/m2000/bin/commonsvrd
0 18:11:45 ?
0:00 /export/home/m2000/bin/timesvrd
0:00 /export/home/m2000/bin/pmsvrd
Y 3)
N 2).
2)
4-5
Maintenance Manual
iManager M2000
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).
4)
Log in to the M2000 server as the root user, and 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 problem is solved.
Y End. Upgrade the M2000 common version to the B03D501 or later versions.
N Contact Huawei technical support engineers.
II. Solution
1)
2)
3)
4-6
Maintenance Manual
iManager M2000
II. Solution
1)
Adapter IP
The Adapters 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 servers 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 users choice.
Therefore, when the HLR User Data Management menu is not displayed correctly,
please check the settings here.
II. Solution
To handle the problem, proceed as follows:
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
iManager M2000
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
To handle the problem, proceed as follows:
1)
Verify whether the version of the M2000 common service is B03D501 or earlier.
Y 2)
N Contact Huawei technical support engineers.
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.
$ isql -Usa -Pserver1234
1> use alarmdb
2> go
1> select count(*) from m2000.history
2> go
-----------
4-8
Maintenance Manual
iManager M2000
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
#/etc/rc2.d/S98m2000svr stop
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
#/etc/rc2.d/S98m2000svr start
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
iManager M2000
history alarms generated before a specific time, please execute the following
commands:
Log in to the M2000 server.
Stop the M2000 server process.
$su
#/etc/rc2.d/S98m2000svr stop
Execute the following command to delete history alarms generated before a specific
time.
#su m2000
$isql -Usa -Pserver1234
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). */
5)
Check whether event 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 event alarm table.
$ isql -Usa -Pserver1234
1> use alarmdb
2> go
4-10
Maintenance Manual
iManager M2000
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)
Change the table name m2000.history to m2000.event and proceed as the step 3
describes.
Check whether the problem is solved five minutes later.
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)
2> go
1> select count(*) from m2000.fault
2> go
4-11
Maintenance Manual
iManager M2000
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.
II. Solution
To handle this problem, check whether:
z
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
iManager M2000
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.
The number of the registered objects exceeds the processing capability of the
host.
The number of the registered tasks exceeds the limit of the host.
II. Solution
To handle the problem, proceed as follows:
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)
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)
4-13
Maintenance Manual
iManager M2000
II. Solution
To handle the problem, proceed as follows:
1)
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)
4-14
Maintenance Manual
iManager M2000
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
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)
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
Maintenance Manual
iManager M2000
z
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 10102 26847 1 11:46:32 ? 0:02 /export/home/m2000/bin/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
On completion of the above operation, observe for 2-3 hours to see whether the
performance task result is reported.
Y End
N 14)
14) Check whether the performance database is normal.
4-16
Maintenance Manual
iManager M2000
Log on to the M2000 server as the m2000 user and then perform the following
operations to check the database.
$su - m2000
$isql -Usa -Pserver1234
1>sp_who
2>go
fid spid status loginame origname hostname blk dbname cmd
0 16 sleeping sa
sa
yshai
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
pmdb 4096.0 MB sa
(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
iManager M2000
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.
On completion of the above operation, observe for 2-3 hours to see whether the
performance task result is reported.
Y End.
N Contact technical support engineers of Huawei.
If the lock is caused by the insufficient log space, refer to 4.2.14 Solution to Log
Space Full described in the above.
If the lock is caused by the access conflict between NWS, SVR or the timing
clearance program, handle it as below:
1)
2>go
2)
10200
11:56:35
0:00
monsvrd
/export/home/m2000/bin/pmsvrd
4-18
Maintenance Manual
iManager M2000
II. Analysis
1)
2)
The IP address in file "/etc/hosts" does not match that of the current host.
III. Solution
1)
# 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.
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
II. Analysis
DSQUERY variants have not been set in environment variant settings.
4-19
Maintenance Manual
iManager M2000
III. Solution
1)
2)
II. Analysis
The auto-start file "/etc/rc2.d/S97sybsvr" has not been created.
III. Solution
1)
su - sybase -c "/install/startserver \
-f /install/RUN_sybserver \
-f /install/RUN_sybserver_back"
sleep 15
2)
II. Analysis
The device name created during the Sybase database installation process does not
match that in the installation script.
III. Solution
1)
2)
Maintenance Manual
iManager M2000
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)
#pkgrm HWM2000
During uninstalling, answer all questions with yes.
2)
#rm -r HWM2000
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.
End
4-21
Maintenance Manual
iManager M2000
494
/export/home/m2000/bin/timersvrd
5-1
Aug
11
0:00
monsvrd
Maintenance Manual
iManager M2000
m2000
2)
496
494 0
Aug 11 ?
0:01 /export/home/m2000/bin/timersvrd
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 .
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
iManager M2000
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
kill
5-3
Maintenance Manual
iManager M2000
2)
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)
6)
Press <Ctrl + ]> to go back to the platform shell by doing the following:
6-1
Maintenance Manual
iManager M2000
7)
disc
The following is displayed:
Connection closed.
<schostname>:SC>
8)
Query the current statuses of the virtual key switches using the following
command:
showkeyswitch
The following is displayed:
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 .
2)
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
iManager M2000
3)
5)
Telnet to the System Controller board of the SunFire 4800 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
Enter 0 to select the Platform Shell.
6)
poweron all
7)
console d a
The following is displayed:
Connected to Domain A
Domain Shell for Domain A
<schostname>:A>
8)
setkeyswitch on
This step takes several minutes.
6-3
Maintenance Manual
iManager M2000
9)
boot
The following is displayed:
Trapdistributor starting...
The system is ready.
<hostname> console login:
Note:
For dual-node system, perform step 3 to 13 for the secondary server.
6-4
Maintenance Manual
iManager M2000
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
Caution
This following procedure will power off the disk array and other arrays connected to it.
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
iManager M2000
2)
Ensure that there are no I/O operations on the data path between the host and the
array.
3)
4)
:/:<1> shutdown
The following is displayed:
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.
Telnet to the disk array you want to maintain using the following command:
# telnet T3_name
Example: # telnet t3e1
2)
root
The following is displayed:
Password:
3)
<T3_name_root_passwd>
4)
6-6
Maintenance Manual
iManager M2000
volume
capacity
raid
data
standby
v0
269.782 GB
u1d1-9
none
Maintenance Manual
iManager M2000
To display the general information about the array, use the following command:
:/:<23>set
The following is displayed (specific output may differ):
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
6-8
Maintenance Manual
iManager M2000
6-9
Maintenance Manual
iManager M2000
Network faults, including faults detected in the M2000 Server, back administration
module (BAM), and work station (WS).
Debugging faults of routers, including faults detected in the physical layer, link
layer, network layer, and Ethernet.
A-1
Maintenance Manual
iManager M2000
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.
2)
Add the above commands to the file /etc/rc2.d/S97sybsvr when the connection is
normal.
A-2
Maintenance Manual
iManager M2000
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.
Note:
z
P: Password. A user can specify the current password for the SQL Server.
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.
2)
3)
A-3
Maintenance Manual
iManager M2000
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
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)
A-4
Maintenance Manual
iManager M2000
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.
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.
Having the functions of storage, forwarding, and routing to realize rate matching
and routing.
A-5
Maintenance Manual
iManager M2000
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.
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.
III. Troubleshooting
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.
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
serious.
loss
is
Invert the transmit-clock on the port connected by the private line at both ends
by executing the command invert transmit-clock.
A-6
Maintenance Manual
iManager M2000
Note:
Meanings of the above five signals are as follows:
z
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.
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.
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
iManager M2000
DTR=DOWN
RTS=DOWN
Analysis
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
signals
synchronously.
After
the
transmit-clock is inverted on the interface, the
clock becomes normal.
If the fault still exists after the inversion, and
the configuration is correct, you need to check
connection of cables.
Solution
Both DTR and RTS signals are sent from DTE (data terminal). It may be
the poor connection of DTE equipment that causes this problem. Check
whether the DTE equipment is correctly connected and whether cables
and lines are faulty.
The DB9 (25) connector of the cable on the configuration port is DCE
connector, and that of the cable on the standby port is DTE connector.
During the configuration of the router, the router is regarded as DCE, and
it is regarded as DTE when connected to the MODEM through the AUX
port.
The physical port is UP and the protocol is UP, but the opposite port cannot be
pinged.
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.
A-8
Maintenance Manual
iManager M2000
The address mapping of the link layer or the operational mode is incorrect.
The frame format of the link layer is correct (X.25, FR, and Ethernet).
The address mapping of the link layer is correct (when X.25 and FR protocols are
encapsulated).
Note:
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.
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)
2)
A-9
Maintenance Manual
iManager M2000
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.
Analysis
Solution
Change
the
encapsulated
protocol of the CISCO router to
PPP (recommended solution) or
change
the
encapsulated
protocol at the Quidway side to
HDLC using the command
link-protocol ppp or link-protocol
hdlc.
The
two
sides
connected
encapsulate the X.25
(or the LAPB directly),
but the protocol is in
Off state all the time.
Turn on the debug
switch DEBUGGING
X.25 PACKET frame, it
cycles continuously.
This is because both sides are encapsulated in the same operational mode
(DTE or DCE). Change the operational mode at one end.
During
the
configuration of X.25
address mapping, the
system prompts that
address mapping is
repeated.
A-10
Maintenance Manual
iManager M2000
Description
Analysis
The PPP protocol belongs to the ISO
protocol on the second layer. Thus you
must locate the fault from the first layer.
Execute the command display int sn (n
is the serial port used) to check whether
the bottom layer signals of DTR, DSR,
RTS, CTS, and DCD are all in the UP
state.
If they are not, it shows that the physical
line between DTE and DCE is not
connected properly.
When the system prompts that the serial
port is in the UP state and there is no
frame error, it shows the physical layer
is normal. In this case, use the
command display int sn to check if
LCP and IPCP are in the OPEN state. If
yes, it shows the PPP verification
succeeds.
Solution
Observe
the
debugging
information
with
the
BEBUGGING PPP PACKET
switch and find out that both of
the routers are in REQUEST
states during the router LCP
negotiation at both sides. This
shows that a fault may occur in
the intermediate link. In this case,
check the state of the
intermediate transmission cable.
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
iManager M2000
Check the interface by executing the command display interface. The Ethernet
interface is always in DOWN state
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.
III. Troubleshooting
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.
A-12
Maintenance Manual
iManager M2000
send-frame-type Ethernet-II
Or
send-frame-type Ethernet-SNAP
A-13
Maintenance Manual
iManager M2000
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
iManager M2000
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.
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
iManager M2000
II. Group
Several users can constitute a user group, in which the information can be shared.
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.
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-3
Maintenance Manual
iManager M2000
Application Program
Shell
Kern
sh
Hardware
Kernel
csh
ksh
Shell
Application Program
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.
Bourne Shell
B Shell
sh
Korn Shell
K Shell
ksh
B-4
Command
Prompt
Maintenance Manual
iManager M2000
Type
C Shell
Feature
Abbr.
C Shell
Command
csh
Prompt
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".
profile
bin
etc
data
Directory of data files, which will change during system operation and
log
Maintenance Manual
iManager M2000
z
script
Mode
Link count
User ID
Group ID
Size
Access time
File name
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-6
Maintenance Manual
iManager M2000
Function
pwd
cd [Directory]
Switch directory
mkdir Directory
Create a directory
rmdir Directory
Delete a directory
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.
Maintenance Manual
iManager M2000
$ cd /
Go up one directory:
$ cd ..
Go up two directories:
$ cd /
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
B-8
Maintenance Manual
iManager M2000
If the current directory is "/home1/omc", the above command can be simplified as:
$ rmdir data
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
-rw-r--r--
1 sybase
staff
drwxr-xr-x
2 sybase
staff
512 Sep 5
--More
B-9
2001 bin
2001 devlib
Maintenance Manual
iManager M2000
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:
ls -la | more
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.
When the command "ls -l" is executed, seven columns of information will be displayed.
The first character indicates the file type (e.g. "-" stands for a common file and "d" for directory, etc).
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).
The 2nd column indicates the number of hard links of the file.
The 3rd and the 4th column display such information as the owner of the file, and the user group to
which the file belongs.
The 6th column shows the time and date when the file is last modified.
Function
Copy a file
mv file1 file2
rm [Option] file
Delete a file
I. Copy a file -- cp
[Description]
B-10
Maintenance Manual
iManager M2000
The command "cp" is used to copy the content of a file into another file.
[Command format]
cp [option] file1 file2
[Description of options]
-r
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
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
B-11
Maintenance Manual
iManager M2000
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 filesthe source file and a new copy
of the file.
executed).
-r
and any files and subdirectories it contains, as well as files in those subdirectories).
[Parameter description]
File
[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.
Two ways are available for deleting directory: execute the command "rmdir" or execute the command
"rm r". The difference between the two is:
B-12
Maintenance Manual
iManager M2000
group members
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 users 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
iManager M2000
[Parameter description]
File
[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.
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:
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".
B-14
Maintenance Manual
iManager M2000
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
[Description of options]
-f
-R
Recursive directory
[Parameter description]
Owner
File
[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
-R
Recursive directory
[Parameter description]
Group
File
[Example]
Modify the user group of "file" to be "new_ group":
$ chgrp new_group file
B-15
Maintenance Manual
iManager M2000
Caution:
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.
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.
The command "chown" can be used to modify the owner and the user group of a file at the same time:
Function
clear
Clear screen
B-16
Maintenance Manual
iManager M2000
\t
Output TAB
\n
Output RETURN
\v
[Example]
$ echo $HOME
/export/home/sybase
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.
-v
[Example]
Display the content of "M2000_Table.txt":
$ cat M2000_Table.txt
Name
Owner
Object_type
------------------------------ -----------------------------tbl128Addr
m2000
user table
B-17
Maintenance Manual
iManager M2000
tblSvrIP
m2000
user table
Note:
The command "cat" can display several files at one time, like this:
$ cat file1 file2 file3
-w
-lines
+/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
iManager M2000
Note:
To display a file one screen at a time, the following keys can be used to execute relevant operation:
Space key
Quit.
/word
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
[Description of options]
Value
[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
[Description of options]
Digit
[Example]
B-19
Maintenance Manual
iManager M2000
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.
Function
Add a user
Delete a user
B-20
Maintenance Manual
iManager M2000
Comment
-d directory
-m
-g group
User group
-s shell
[Parameter description]
User name
[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-21
Maintenance Manual
iManager M2000
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.
-d directory
-g group
-m
-l
-s shell
[Parameter description]
user name
[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-22
Maintenance Manual
iManager M2000
Command passwd is used to set the password for newly added users or modify user
password.
[Command format]
passwd user name
[Parameter description]
User group name
[Example]
Modify the name of the user group "staff1" to be "staff2":
# groupmod -n staff2 staff1
B-23
Maintenance Manual
iManager M2000
Function
Search file.
compress/uncompress file
Compress/decompress file.
pack/unpack file
pkgadd [option] file package name
bc
Calculator
The directory where the file search starts. Multiple directory names can
File search conditions, including the file name, the owner, the time of
Description
-name name
The name of the file or directory to be searched. Wildcard can be used, e.g.
-name *.c.
-size
-type x
-user user
d --- directory
c ---character
p --- pipe
Search all the files of "user". The "user" can be user name or UID.
B-24
Maintenance Manual
iManager M2000
Conditions
Description
-group group
Search all the files of user group "group". The "group" can be user group
name or GID.
-links n
-atim n
-mtime n
Take the file found as the object to be executed by the command. Put the
parameter to be used in the exection of the command in {}.
Meaning
non
-o
or
and
Example
Description
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
iManager M2000
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:
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.
File
[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-26
Maintenance Manual
iManager M2000
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]
[Description of options]
1)
Function options
write, etc)
r
Read the file in the archive. If the file name is a directory, its subdirectories
will be read.
c
Create a archive.
Create the file from the beginning of the archive, instead of place it after the
last file.
2)
Modification options
v Activate display mode. The name of all the files processed will be displayed.
(used often)
w
is processed,.
f
Indicate that the archive is a file. If this parameter is skipped, the preset tape
[Example]
1)
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)
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
iManager M2000
Caution:
z
There is no "-" sign before the function and modification parameters of the command tar.
The command tar can be used to pack several files into a package, shown as below:
The above command is used to pack the file1, file2 and file3 into a package named "filebak.tar".
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
iManager M2000
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-29
Maintenance Manual
iManager M2000
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.
Command mode
B-30
Maintenance Manual
iManager M2000
Insert text at the end of the line where the cursor is.
Insert text before the first nonblank character in the line where the cursor is.
Start a new line below the current one and insert text. (open)
Start a new line above the current one and insert text.
Line No. G
Move the cursor to certain line (e.g. 1G meams to move the cursor to the first line.)
Press ESC key to quit text insert mode and enter command mode.
dd
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
:q
:q!
:w
B-31
Maintenance Manual
iManager M2000
Function
man [option]command
ps [option]
Terminate a process.
who [option]
which command
uname [option]
ifconfig [option]
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
iManager M2000
-k
[Example]
Check free disk space:
df -k
Filesystem
kbytes
used
/dev/dsk/c0t0d0s0
2053605
997684
/proc
fd
avail capacity
994313
51%
0%
/proc
0%
/dev/dsk/c0t1d0s7
35009161 2562019
32097051 8%
swap
3431792
3425128
6664
Mounted on
1%
/dev/fd
/export/home
/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.
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.
Maintenance Manual
iManager M2000
-a
-s
-k
[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
-l
-u user
-f
[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
iManager M2000
PID
PPID
STIME TTY
TIME CMD
0 08:44:35 pts/5
0:00 ksh
0 10:00:46 ?
0:00/export/home/02000/bin/timersvrd
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).
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.
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.
-s signal
[Parameter description]
Process No.
[Example]
List all the signal names:
B-35
Maintenance Manual
iManager M2000
$ 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
Caution:
z
The command ps can be used to check the execution of the command kill by listing the PIDs of the
terminated processes.
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]
[Description of options]
-b
Display the date and time when the system last booted.
-m
Display the relevant information of the user issuing the command (same as
Display the information about the user who logs in to the device sending out
commands.
B-36
Maintenance Manual
iManager M2000
[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)
pts/5
Feb
4 08:45
(10.129.28.44)
or:
$ who -m
sybase
-m
-s
[Parameter description]
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
iManager M2000
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 .
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
iManager M2000
-i
-m
Display the name of the equipment hardware (It is suggested that option
-p
-r
-s
Display the name of the operating system of the host (it is the default
option).
-v
-S
system_name
[Example]
Display the the name, the version and serial No. of the operating system of the host:
$ uname-svr
[Example]
Display all the IP address information of the host:
$ ifconfig a
B-39
Maintenance Manual
iManager M2000
flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu
1500
inet
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.
Append the screen I/O content to a file (if this parameter is not set, the
The file used to save the screen I/O content (if no file name is specified,
TIME CMD
0:00 ksh
$ pwd
/export/home/sybase
$ exit
Script done, file is typescript
B-40
Maintenance Manual
iManager M2000
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.
+format
Description
%h
%j
%n
Go to next line
%t
tab
%y
%D
%H
%M
%S
B-41
Maintenance Manual
iManager M2000
Format
Description
%T
[Example]
Display the current data and time of the system:
$ date
Mon Feb
Display the current system date and time in Greenwich Mean Time:
$ date -u
Mon Feb
FTP -- File Transfer Protocol, is also a user layer protocol, offering standards for
file copying between different systems.
Function
ping IP address
B-42
Maintenance Manual
iManager M2000
Command/Usage
Function
netstat [option]
route [option]
[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 users computer itself is secure or whether the
TCP/IP protocol is set correctly (for Windows95 users).
Maintenance Manual
iManager M2000
will completely depend on the remote host settings and the access rights his login
account has.
[Command format]
telnet IP address / domain
[Parameter description]
IP address
Domain
[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
SunOS 5.6
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.
B-44
Maintenance Manual
iManager M2000
[Parameter description]
IP address
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
? | help [command]
Command help.
ascii
binary
cd [directory]
close
lcd [directory]
ls [r-directory] [l-file]
B-45
Maintenance Manual
iManager M2000
ftp command
Description
pwd
Quit | bye
Exit 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 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
iManager M2000
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.
host domain
IP address
[Example]
Table shows a few examples of finger commands.
Examples of finger commands
Examples
Description
$ finger
$ finger root
$ finger @omcsyb2
$ finger @omcsyb2.huawei.com.cn
View
information
about
"omcsyb2.huawei.com.cn".
$ finger abc@omcsyb2
$ finger abc@129.6.114.202
B-47
all
users
in
host
Maintenance Manual
iManager M2000
-n
specified.
-v
information.
2)
4)
5)
Time intervals
-anv
Same as 1)
-s
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
hme0
10.0.0.0
10.105.31.254
UG
224.0.0.0
10.105.28.202
hme0
127.0.0.1
127.0.0.1
UH
896
lo0
B-48
Maintenance Manual
iManager M2000
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.
Maintenance Manual
iManager M2000
[Command format]
route [-fnvq] command [ [modifiers] args]
route [-fnvq] add | change | delete |get [host | net] destination [gateway [args] ]
route [-n] monitor
route [-n] flush
[Description of options]
-f
-n
-v
-q
Gateway IP address
net
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:
mask:
10.0.0.0
255.0.0.0
gateway: 10.105.31.254
interface: hme0
flags: <UP, GATEWAY, DONE, STATIC>
recvpipe
sendpipe
ssthresh
rtt, msec
0
rttvar
hopcount
1500
mtu
0
10.105.31.254
done
Gateway
Flags
Ref
Use
Interface
10.105.28.202
10.105.28.202
B-50
4
U
6
4
hme0
0
hme0
expire
Maintenance Manual
iManager M2000
127.0.0.1
UH
1500
lo0
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
Gateway
Flags
Ref Use
Interface
10.105.28.202
hme0
129.9.0.0
10.105.28.202
UG
//Newly-added routing
10.0.0.0
10.105.31.254
UG
224.0.0.0
10.105.28.202
127.0.0.1
127.0.0.1
UH
313
hme0
lo0
Gateway
Flags
Ref
Use
Interface
10.105.28.202
hme0
129.9.0.0
1.2.3.4
UG
been modified.
10.0.0.0
10.105.31.254
UG
224.0.0.0
10.105.28.202
hme0
127.0.0.1
127.0.0.1
UH
445
lo0
B-51
Maintenance Manual
iManager M2000
/* 600*1024/2 =307200(2K)*/
3> go
C-1
Maintenance Manual
iManager M2000
2)
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
Information about the disks and (magnetic) tapes installed in the system.
On-going processes.
Maintenance Manual
iManager M2000
the system database, and finally the master database -- if still no result is found there.
C-3
Maintenance Manual
iManager M2000
Description
sp_addgroup
sp_addlogin
sp_adduser
sp_changegroup
sp_configure
sp_dboption
sp_dropdevice
Detele a device
sp_dropgroup
Detele a group
sp_droplogin
Detele an account
sp_help
Query database objects and all database information, i.e. to list table
information
sp_helpdb
sp_helpdevice
sp_helpgroup
sp_helpindex
sp_helpuser
sp_lock
sp_monitor
sp_password
sp_spaceused
sp_syntax
sp_who
C-4
Maintenance Manual
iManager M2000
Database owner (DBO), who has full access to and manages the databases he
creates.
Database users can be divided into groups. A database will be assigned a "public" user
group once it is created.
password
The following command is used to view the information about the new user "Hello".
1> select * from syslogins
2> go
C-5
Maintenance Manual
iManager M2000
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]]
[Parameter description]
user name:
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)
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
(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)
C-6
Maintenance Manual
iManager M2000
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
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
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
iManager M2000
Group_name
Group_id
------------------------------ -------public
(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
isql
commands.
z
bcp
For data import and export between SQL Server tables and system
files.
z
showserver:
"startserver" to start it; command "shutdown" can be used to shut the SQL
server down if it is running).
z
startserver
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
iManager M2000
I. Start up isql
[Description]
isql can be started in Unix system command mode.
[Command format]
isql [Options]
[Option description]
-U username
-P password
-S Server
The name of specified SQL Server which is allowed to link with user.
-i inputfile
-o outputfile
-w column_width
[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:
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> ".
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.
C-9
Maintenance Manual
iManager M2000
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]
[Parameter description]
-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
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
[Parameter description]
Database:
Owner:
Database table:
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
iManager M2000
Data files:
Source data files or target data files (depending on the copying direction),
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
-d/dev/rdsk/c0t0d0s4 -e/home1/sybase/i
sybase
208
206
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
iManager M2000
C.2.4 Startserver
[Description]
Command "startserver" is used to start SQL Server.
[Command format]
startserver [Options]
[Option description]
-f run_serverfile
Server
Its
restarts.
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)
2)
C-12
Maintenance Manual
iManager M2000
Note:
z
Always shut down the backup server prior to the active server.
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:
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.
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
iManager M2000
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
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
C-14
Maintenance Manual
iManager M2000
insert
into
teachers(teacher_name,phone,salary)
values
('wangjie','3340546',3000)
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
System administrator
System adminstrator can grant other users the right to "create database" and
make them the Database Owner (DBO).
C-15
Maintenance Manual
iManager M2000
2)
3)
Description
create table
creating a table
create default
create rule
creating rules
create procedure
create view
creating views
dump databse
dumping database
dump transaction
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
iManager M2000
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
table
view
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).
create database
create procedure
create rule
create view
dump database
dump transactiom
C-17
Maintenance Manual
iManager M2000
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.
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
iManager M2000
Caution:
While carrying out database backup and restoration, the backup server must be running.
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.
Maintenance Manual
iManager M2000
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"
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.
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.
2)
C-20
Maintenance Manual
iManager M2000
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)
5)
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)
9)
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".
Command "load" will not work if the database is currently being used by other users.
C-21
Maintenance Manual
iManager M2000
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
2)
Type <STOP+A>
3)
On prompt "OK", type "boot cdrom s" /*This will boot the computer from
CD-ROM*/
4)
5)
6)
7)
Execute "csh"
8)
9)
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.
Maintenance Manual
iManager M2000
#CONSOLE=/dev/console
2)
3)
D-2
Maintenance Manual
iManager M2000
There are many such commands, for example: "vmstat" and "sar"; "iostat", "df", "du"
are used to check the hard disk status.
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
Disk: fsck
Network adapter:
Swap area
swap -s
3)
4)
D-3
Maintenance Manual
iManager M2000
D-4
Maintenance Manual
iManager M2000
User/group
Authority
description
${HOME}=/export/home/m2000
m2000/staff
drwxr-xr-x
${HOME}/bin
m2000/staff
drwxr-xr-x
${HOME/data
m2000/staff
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
drwxr-xr-x
${HOME}/lib
${HOME}/etc
${HOME}/log
m2000/staff
m2000/staff
m2000/staff
Description
${HOME}/script
m2000/staff
drwxr-xr-x
${HOME}/script/common
m2000/staff
drwxr-xr-x
${HOME}/script/configsvr
m2000/staff
drwxr-xr-x
E-1
Maintenance Manual
iManager M2000
User/group
Authority
description
${HOME}/script/pmsvr
m2000/staff
drwxr-xr-x
${HOME}/script/timersvr
m2000/staff
drwxr-xr-x
${HOME}/script/commonsvr
m2000/staff
drwxr-xr-x
${HOME}/script/alarmsvr
m2000/staff
drwxr-xr-x
${HOME}/backup
sybase/dba
drwxr-xr-x
drwxrwxrwx
${HOME}/send
m2000/staff
Description
E.2.1 ${HOME}/bin
The files under this directory include:
z
There are some tools for each service under this directory except the above files:
z
Crypt
cleartable
E-2
Maintenance Manual
iManager M2000
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.
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.
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.
addlogin
Used to create login sybase of the user m2000. It can be created automatically
during installation or created manually after installation.
bcpout
combcp
Used to import the static authority script into the common server. It must be used
under the instruction of R&D.
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.
inputpasswd
Used by the alarm server to upgrade the alarm database. This command gives
operation prompt if no parameter is used.
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.
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.
initconninfo
E-3
Maintenance Manual
iManager M2000
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.
viewconninfo
Used by the common server to check information of history routing tables. It is
used directly without parameters.
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.
alarmexception.ini
This file, in the binary format, is used to record the information of exceptional exit
of the alarm server.
alarmomccsn.dat
This file, in the binary format, is used to record serial numbers of current internal
alarms.
alarmnetcsn.dat
This file, in the binary format, is used to record serial numbers of current network
alarms.
alarmsave.ini
This editable text file is used to record conditions for saving current history alarms.
alarmrelative.ini
This editable text file is used to record conditions related to current alarms.
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
iManager M2000
support=1
listenport=5200
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.
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.
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.
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.
dbinfo.dat
This file is used to save the information of the current database.
maxobjid.dat
The file is used to save the current maximum ObjectID. It must be reserved during
upgrade.
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.
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.
pminside.dat
It is the internal performance parameter file, which is currently used to save
incremental numbers of performance tasks.
E-5
Maintenance Manual
iManager M2000
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
language.txt
Text file
language_cn.txt
Text file
language_en.txt
Text file
pmconfig
Text file
Remark
No modification is
allowed.
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
iManager M2000
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.
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.
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.
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.
Confirmation is necessary before you invoke this script to prevent the loss of all
configuration data.
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.
Confirmation is necessary before you invoke this script to prevent the loss of all
common data.
crtpmdb.sql
E-7
Maintenance Manual
iManager M2000
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.
Confirmation is necessary before you invoke this script to prevent the loss of all
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.
Confirmation is necessary before you invoke this script to prevent the loss of all
data of log server.
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.
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.
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.
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.
cront.*.sh
E-8
Maintenance Manual
iManager M2000
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
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.
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.
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.
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
The following describes files under this directory.
z
createproc.sql
E-9
Maintenance Manual
iManager M2000
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.
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
updatealarmdbtbl.sql
renewexp.sql
updateomc.sql
updatemsc33.sql
updatebsc32.sql
updatehlr36.sql
updatechlr36.sql
updatecmsc61.sql
updatepcu33.sql
updatesgsn80.sql
updateggsn35.sql
updatewll.sql
updatepdsn.sql
updatecg.sql
updateimsc.sql
updatecbsc.sql
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
iManager M2000
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.
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.
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.
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.
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.
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.
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
iManager M2000
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.
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.
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.
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.
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.
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.
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.
CrtHisCfgProc.sql
E-12
Maintenance Manual
iManager M2000
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.
tbl*.txt
The * stands for table name. These text files are used to import the data table of
the configuration system.
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.
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.
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.
dropsystables.sql
E-13
Maintenance Manual
iManager M2000
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.
*.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