M2000 Administrator Guide PDF

Chapter 1 Overview of Administrator Guide .................................................
1-1
1.1 Objective ................................................................................................

1.2 Requirements for Administrator ..............................................................
1.3 Organization of This Guide.....................................................................
1.3.1 Administrative Tasks ......................................................................
1.3.2 Maintenance Items .........................................................................
1.3.3 Commands and Tools ....................................................................
1.3.4 FAQ................................................................................................
1-1
1-1
1-2
1-2
1-2
1-2
1-3
Chapter 2 Server Parameter Settings ............................................................
2-1
2.1 Overview of Server Parameter Settings .................................................

2.2 Modifying Server Time ...........................................................................
2.2.1 Operation Effect .............................................................................
2.2.2 Operation Procedure ......................................................................
2.3 Modifying Host name of Server ..............................................................
2.4 Modifying Server IP Address ..................................................................
2.5 Setting Parameters of Server with Multiple IPs ......................................
2-1
2-1
2-1
2-1
2-2
2-2
2-2
2-3
2-3
2-3
2-4
2-4
2-5
Chapter 3 User Management ..........................................................................
3-1
3.1 Overview of User Management ..............................................................

3.2 Introduction to User Account ..................................................................
3.2.1 Types of User Account ...................................................................
3.2.2 Operating System User Accounts and the Authority ......................
3.2.3 Database User Account and the Authority .....................................
3.2.4 M2000 User Accounts and the Authority .......................................
3.3 Creating Operating System User ...........................................................
3.4 Modifying Password of Operating System User .....................................
3.4.2 Modifying Password of root............................................................
3.4.3 Modifying Password of dbuser .......................................................
3.4.4 Modifying Password of omcuser ....................................................
3.4.5 Modifying Password of ftpuser .......................................................
3.5 Modifying Password of Database User ..................................................
3-1
3-1
3-1
3-1
3-3
3-3
3-3
3-3
3-3
3-4
3-4
3-4
3-4
3-4
3-4
3-5

3.6 Creating M2000 User Group ..................................................................
3.7 Creating M2000 User Account ...............................................................
3.8 Monitoring M2000 Users ........................................................................
3-5
3-5
3-6
3-6
3-6
3-6
3-6
3-6
3-6
3-6
3-7
Chapter 4 Log Management ............................................................................
4-1
4.1 Overview of Log Management ...............................................................

4.2 Introduction to Log ..................................................................................
4.2.1 Types of Logs ................................................................................
4.2.2 User Log ........................................................................................
4.2.3 NE Log ...........................................................................................
4.2.4 System Log ....................................................................................
4.2.5 Trace log ........................................................................................
4.3 Browsing User Log .................................................................................
4.4 Browsing System Log .............................................................................
4.5 Checking Solaris Error Log ....................................................................
4-1
4-1
4-1
4-1
4-1
4-2
4-2
4-3
4-3
4-3
4-3
4-3
4-3
4-3
4-3
4-3
Chapter 5 Server Performance Monitor .........................................................
5-1
5.1 Overview of Server Performance Monitor ..............................................

5.2 Querying Server Status through Client...................................................
5.2.1 Function .........................................................................................
5.3 Setting the Threshold of Server Status Alarm ........................................
5.3.1 Function .........................................................................................
5.4 Querying System Performance ..............................................................
5-1
5-1
5-1
5-1
5-2
5-2
5-2
5-2
5-2
5-3
5.5 Adjusting System Performance ..............................................................

5-3
5-3
5-4
Chapter 6 M2000 Process and Service Management ...................................
6-1
6.1 Overview of M2000 Process and Service Management ........................

6.2 Introduction to M2000 Processes and Services .....................................
6.2.1 Overview to Processes and Services ............................................
6.2.2 SystemConfigurator .......................................................................
6.2.3 sac_agent ......................................................................................
6.2.4 em_agent .......................................................................................
6.2.5 monitor_agent ................................................................................
6.2.6 partition_agent ...............................................................................
6.2.7 audit_agent ....................................................................................
6.2.8 mo_agent .......................................................................................
6.2.9 sm_agent .......................................................................................
6.2.10 med_agent ...................................................................................
6.2.11 ts_agent .......................................................................................
6.2.12 ifms_agent ...................................................................................
6.2.13 manager_agent ............................................................................
6.2.14 pm_agent .....................................................................................
6.2.15 cmserver_agent ...........................................................................
6.2.16 swm_agent ...................................................................................
6.2.17 fmnotify_agent .............................................................................
6.2.18 proxy_agent .................................................................................
6.2.19 notify_agent .................................................................................
6.3 Querying Number of M2000 Processes .................................................
6.4 Querying Service Status .........................................................................
6.5 Starting M2000 Services ........................................................................
6.6 Stopping M2000 Services ......................................................................
6-1
6-1
6-1
6-1
6-1
6-2
6-2
6-3
6-3
6-3
6-4
6-4
6-4
6-4
6-4
6-5
6-5
6-5
6-5
6-6
6-6
6-6
6-6
6-6
6-6
6-6
6-6
6-8
6-8
6-8
6-9
6-9
6-9
Chapter 7 Database Management ..................................................................
7-1
7.1 Overview of Database Management ......................................................
7-1
7.2 Introduction to Database ........................................................................

7.2.1 Overview of Database ....................................................................
7.2.2 omcdb ............................................................................................
7.2.3 fmdb ...............................................................................................
7.2.4 pmdb ..............................................................................................
7.2.5 sysmdb ...........................................................................................
7.3 Querying Database Status .....................................................................
7.4 Manually Displacing Alarm Data ............................................................
7.5 Manually Displacing User Log ................................................................
7.6 Setting Auto Displacing for Alarm Data ..................................................
7.7 Setting Auto Displacing for User Log .....................................................
7.8 Deleting Performance Task ....................................................................
7.9 Clearing Database ..................................................................................
7-1
7-1
7-1
7-2
7-2
7-3
7-4
7-4
7-4
7-5
7-5
7-5
7-5
7-5
7-6
7-6
7-6
7-6
7-7
7-7
7-7
7-7
7-7
7-7
7-8
7-8
7-8
Chapter 8 Disk Space Management ...............................................................
8-1
8.1 Overview of Disk Space Management ...................................................

8.2 Introduction to File System .....................................................................
8.2.1 Overview of System Structure .......................................................
8.2.2 Server File System .........................................................................
8.2.3 Client File System ..........................................................................
8.3 Query Disk Space ..................................................................................
8.4 Clearing Disk Space ...............................................................................
8-1
8-1
8-1
8-1
8-2
8-2
8-2
8-3
8-3
8-3
8-3
Chapter 9 Dual-Plane Configuration ..............................................................
9-1
9.1 Overview of Dual-Plane Configuration ...................................................

9.2 Introduction to Dual-Plane ......................................................................
9.3 Configuration Procedure of Dual-Plane ..................................................
9.4 Planning IP Data ....................................................................................
9.5 Manually Setting Dual-Plane ..................................................................
9.6 Automatically Setting Dual-Plane ...........................................................
9.7 Verifying Dual-Plane Settings .................................................................
9.7.3 Abnormal Handling ........................................................................
9-1
9-1
9-2
9-2
9-2
9-2
9-2
9-3
9-3
9-3
9-4
9-4
9-4
9-4
Chapter 10 NTP Service Configuration ..........................................................
10-1
10.1 Overview of NTP Service Configuration ...............................................

10.2 Introduction to NTP Service .................................................................
10.3 Setting M2000 as Top NTP Server ......................................................
10.4 Setting M2000 as Middle NTP Server ..................................................
10.5 Setting M2000 as NTP Client ...............................................................
10.6 Starting NTP Service ............................................................................
10.7 Checking Running Status of NTP Service ............................................
10.8 Stopping NTP Service ..........................................................................
10-1
10-1
10-2
10-2
10-2
10-2
10-3
10-3
Chapter 11 Backup and Restoration ..............................................................
11-1
11.1 Overview of Backup and Restoration ...................................................

11.2 Introduction to Backup and Restoration ...............................................
11.2.1 M2000 System Backup Contents .................................................
11.2.2 M2000 System Backup and NE Data Backup .............................
11.2.3 The Mode of M2000 System Backup and Restore ......................
11.2.4 Name of Backup Files ..................................................................
11.2.5 Storage Media of Backup File ......................................................
11.3 Function Setting ...................................................................................
11.3.1 Introduction to Configuration File .................................................
11.3.2 Setting Tape Drive Path ...............................................................
11.3.3 Setting Backup Media ..................................................................
11.4 Automatically Backing Up M2000 System ............................................
11.4.1 Introduction to Auto Backup .........................................................
11.4.2 Setting Auto Backup Time ...........................................................
11-1
11-1
11-1
11-1
11-2
11-2
11-2
11-3
11-3
11-3
11-3
11-4
11-4
11-5
11.5 Manually Backing Up M2000 System...................................................

11.5.1 Introduction to Manual Backup ....................................................
11.5.2 Carrying Out Manual Backup on Client ........................................
11.5.3 Carrying Out Manual Backup on Server ......................................
11.6 Restoring M2000 System .....................................................................
11.6.1 Function Introduction ...................................................................
11.6.2 Operation Procedure ....................................................................
11.7 Backing Up Operating System .............................................................
11.8 Restoring Operating System ................................................................
11.8.3 Restoring Tape Information .........................................................
11.8.4 Setting Up Equipment Tree and Boot Block ................................
11.8.5 Modifying System File and File System Information ....................
11.8.6 Restarting System........................................................................
11.8.7 Encapsulating Disk Using Volume Manager ................................
11-5
11-5
11-5
11-6
11-6
11-6
11-6
11-7
11-7
11-7
11-9
11-9
11-9
11-9
11-10
11-11
11-12
11-12
Chapter 12 Routine Maintenance ...................................................................
12-1
12.1 Overview of Routine Maintenance .......................................................

12.2 Daily Maintenance ................................................................................
12.2.1 Daily Maintenance Item List .........................................................
12.2.2 Checking Alarm Information.........................................................
12.2.3 Checking Log Information ............................................................
12.2.4 Checking Solaris Error Log ..........................................................
12.2.5 Checking Database Status ..........................................................
12.2.6 Checking Hard Disk Space ..........................................................
12.2.7 Checking CPU Utilization .............................................................
12.2.8 Checking Number of Processes ..................................................
12.2.9 Checking Service Status ..............................................................
12.3 Weekly Maintenance ............................................................................
12.3.1 Weekly Maintenance Item List .....................................................
12.3.2 Backing Up M2000 System ..........................................................
12.3.3 Checking M2000 Server Time .....................................................
12.3.4 Finding core Files .........................................................................
12.3.5 Clearing Useless Files .................................................................
12.4 Monthly Maintenance ...........................................................................
12.4.1 Monthly Maintenance Item List ....................................................
12.4.2 Checking Power Supply ...............................................................
12.4.3 Checking Server Hardware ..........................................................
12-1
12-1
12-1
12-1
12-2
12-2
12-2
12-2
12-2
12-2
12-3
12-3
12-3
12-3
12-3
12-4
12-4
12-4
12-4
12-4
12-4
12.4.4 Checking Auxiliary Devices of Server ..........................................
12-4
Chapter 13 Troubleshooting ...........................................................................
13-1
13.1 Overview of Troubleshooting ................................................................

13.2 Troubleshooting Procedure ..................................................................
13.2.1 Overview of Troubleshooting Procedure ......................................
13.2.2 Information Collection ..................................................................
13.2.3 Fault Location ..............................................................................
13.2.4 Fault Clearance ............................................................................
13.3 Auto Shutdown of Operating System ...................................................
13.3.1 Symptom ......................................................................................
13.3.2 Fault Analysis ...............................................................................
13.3.3 Fault Clearance ............................................................................
13.4 Abnormal Service Restart ....................................................................
13.4.1 Symptom ......................................................................................
13.4.2 Fault Analysis ...............................................................................
13.4.3 Fault Clearance ............................................................................
13.5 Abnormal Service Termination .............................................................
13.5.1 Symptom ......................................................................................
13.5.2 Fault Analysis ...............................................................................
13.5.3 Fault Clearance ............................................................................
13.6 M2000 Services Starting or Stopping Failure .......................................
13.6.1 Symptom ......................................................................................
13.6.2 Fault Analysis ...............................................................................
13.6.3 Fault Clearance ............................................................................
13-1
13-1
13-1
13-1
13-1
13-2
13-2
13-2
13-2
13-3
13-3
13-3
13-3
13-3
13-4
13-4
13-4
13-4
13-5
13-5
13-5
13-5
Chapter 14 Emergency Maintenance .............................................................
14-1
14.1 Overview of Emergency Maintenance ..................................................

14.2 Emergency Maintenance for M2000 Server .........................................
14.3 Emergency Maintenance for M2000 Client ..........................................
14-1
14-1
14-1
14-1
14-1
14-1
14-2
Chapter 15 Command Guide ..........................................................................
15-1
15.1 Overview of Command Guide ..............................................................

15.2 Introduction to Commands ...................................................................
15.2.1 Path of Commands ......................................................................
15.2.2 Prerequisites of Using Commands ..............................................
15.3 svc_profile.sh .......................................................................................
15.3.1 Function of svc_profile.sh ............................................................
15-1
15-1
15-1
15-1
15-1
15-1
15.3.2 Path of svc_profile.sh ...................................................................

15.3.3 Running svc_profile.sh .................................................................
15.4 start_svc ...............................................................................................
15.4.1 Command Function ......................................................................
15.4.2 Example .......................................................................................
15.5 stop_svc ...............................................................................................
15.5.2 Example .......................................................................................
15.6 kill_svc ..................................................................................................
15.6.2 Example .......................................................................................
15.7 svc_adm-cmd status ............................................................................
15.7.2 Example .......................................................................................
15.8 svc_ps ..................................................................................................
15.8.2 Example .......................................................................................
15.9 top ........................................................................................................
15.9.2 Example .......................................................................................
15.10 svc_adm-cmd reload ..........................................................................
15.10.1 Command Function ....................................................................
15.10.2 Example .....................................................................................
15.11 svc_stacks ..........................................................................................
15.11.2 Example .....................................................................................
15.12 svc_lockdump .....................................................................................
15.12.2 Example .....................................................................................
15-1
15-1
15-2
15-2
15-2
15-3
15-3
15-3
15-3
15-3
15-3
15-3
15-3
15-3
15-4
15-4
15-4
15-4
15-4
15-4
15-5
15-5
15-5
15-5
15-5
15-5
15-6
15-6
15-6
Chapter 16 Tool Guide ....................................................................................
16-1
16.1 Overview of Tool Guide ........................................................................

16.2 Tape Drive Management Tool ..............................................................
16.2.1 Function .......................................................................................
16.2.2 Starting method ............................................................................
16.2.3 Operation Guide...........................................................................
16.3 M2000 Diagnostic Tooling ....................................................................
16.3.1 Function .......................................................................................
16.3.2 Running Diagnostic Tool ..............................................................
16.3.3 Abnormal Handling ......................................................................
16.3.4 Forbidding Using Diagnostic Tool ................................................
16-1
16-1
16-1
16-1
16-2
16-2
16-2
16-3
16-5
16-5
16.4 Performance Job Result Auto Export Tool ........................................... 16-5

16.4.1 Function ....................................................................................... 16-5
16.4.2 Function Settings ......................................................................... 16-5
16.4.3 Running Auto Export Tool ............................................................ 16-6
16.4.4 Stopping Auto Export Tool ........................................................... 16-7
16.4.5 Abnormal Handling ...................................................................... 16-7
16.5 IP Modification Tool .............................................................................. 16-8
16.5.1 Function ....................................................................................... 16-8
16.5.2 Prerequisites ................................................................................ 16-8
16.5.3 Querying IP Settings .................................................................... 16-8
16.5.4 Modifying Solaris IP Address, Host name, Default Gateway
and Subnet Mask .................................................................................... 16-9
16.5.5 Modifying Sybase IP .................................................................... 16-9
16.5.6 Modifying Sybase Service IP and Port Number ........................... 16-10
16.5.7 Modifying Host Name ................................................................... 16-10
16.5.8 Modifying Gateway ...................................................................... 16-10
Chapter 17 FAQ................................................................................................
17-1
17.1 Overview of FAQ ..................................................................................

17.2 Logging in as root though Telnet ..........................................................
17.2.1 Question.......................................................................................
17.2.2 Answer .........................................................................................
17.3 Logging in as root though FTP .............................................................
17.3.1 Question.......................................................................................
17.3.2 Answer .........................................................................................
17.4 Installing Tape Drive .............................................................................
17.4.1 Question.......................................................................................
17.4.2 Answer .........................................................................................
17.5 Setting Default Route ...........................................................................
17.5.1 Question.......................................................................................
17.5.2 Answer .........................................................................................
17.6 Adding and Deleting Routes .................................................................
17.6.1 Question.......................................................................................
17.6.2 Answer .........................................................................................
17.7 "/etc/rc2.d" in Solaris ............................................................................
17.7.1 Question.......................................................................................
17.7.2 Answer .........................................................................................
17.8 Querying Hardware Configuration of Server ........................................
17.8.1 Question.......................................................................................
17.8.2 Answer .........................................................................................
17.9 Confirming Startup of Sybase ..............................................................
17-1
17-1
17-1
17-1
17-1
17-1
17-1
17-2
17-2
17-2
17-3
17-3
17-3
17-3
17-3
17-3
17-4
17-4
17-4
17-4
17-4
17-4
17-5
17.9.1 Question.......................................................................................
17.9.2 Answer .........................................................................................
17.10 Starting Sybase ..................................................................................
17.10.1 Question .....................................................................................
17.10.2 Answer .......................................................................................
17.11 Stopping Sybase ................................................................................
17.11.1 Question .....................................................................................
17.11.2 Answer .......................................................................................
17-5
17-5
17-5
17-5
17-5
17-6
17-6
17-6
Appendix Acronyms and Abbreviations .......................................................
Index .................................................................................................................
HUAWEI
iManager M2000 Mobile Element Management System

Administrator Guide
V200R002

Administrator Guide
Manual Version
T2-030159-20041010-C-2.20
Product Version
V200R002
BOM
31014659
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

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

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

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Summary of Updates
This section provides the update history of this manual and introduces the contents of
subsequent updates.
Update History
This manual is updated for a major product version to maintain consistency with system
hardware or software versions and to incorporate customer suggestions.
Manual Version
T2-030159-20041010-C-2.20
Updates of Contents
None.
Notes
Initial field trial release
About This Manual

Release Notes
This manual applies to iManager M2000 Mobile Element Management System
V200R002.
Organization
This manual provides the system administration tasks, the related concepts and
detailed operation procedures of the system administration tasks, as well as the routine
maintenance, troubleshooting and emergency maintenance. This manual consists of
17 chapters and one appendix:
Chapter 1 Overview of Administrator Guide introduces the objective, contents and
the requirement of an administrator.
Chapter 2 Server Parameter Settings introduces the setting and modification of
server parameters.
Chapter 3 User Management introduces the concepts related to user management
and provides the details of the major user management tasks.
Chapter 4 Log Management introduces the concepts related to log management and
provides the details of the major log management tasks.
Chapter 5 Server Performance Monitor introduces the concepts related to server
performance monitor and provides the details of the major server performance monitor
tasks.
Chapter 6 M2000 Process and Service Management introduces the concepts
related to M2000 process and service management and provides the details of the
major M2000 process and service management tasks.
Chapter 7 Database Management introduces the concepts related to database
management and provides the details of the major database management tasks.
Chapter 8 Disk Space Management introduces the concepts related to disk space
management and provides the details of the major disk space management tasks.
Chapter 9 Maintenance Dual-Plane Configuration introduces the concepts related
to maintenance dual-plane configuration and provides the details of the major
maintenance dual-plane configuration tasks.
Chapter 10 NTP Service Configuration introduces the concepts related to NTP

service configuration and provides the details of the major NTP service configuration
tasks.
Chapter 11 Backup and Restore introduces the concepts related to backup and
restore and provides the details of the major backup and restore tasks.
Chapter 12 Routine Maintenance provides the maintenance items for M2000 and the
operation guide.
Chapter 13 Troubleshooting introduces command troubleshooting procedure and
some cases of troubleshooting.
Chapter 14 Emergency Maintenance provides the operation guide of emergency
maintenance when serious failure occurs to the M2000 or client.
Chapter 15 Command Guide introduces functions and usage of the important
commands.
Chapter 16 Tool Guide introduces the functions and usage of the M2000 tools.
Chapter 17 FAQ introduces the frequently asked question and the solutions
concerning operating system and database.
Appendix Acronyms and Abbreviations lists the abbreviations and acronyms in this
manual.
Intended Audience
The manual is intended for the following readers:
z
System engineer of mobile network
M2000 administrator
Network administrator
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface
Headings are in Boldface.
Courier New
Terminal Display is in Courier New.
II. Command conventions

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

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

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

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

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

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

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

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

operation.
Note, Comment, Tip, Knowhow, Thought: Means a complementary description.
Administrator Guide
Table of Contents
Table of Contents
Table of Contents .............................................................................................................................. i
Chapter 1 Overview of Administrator Guide .............................................................................. 1-1
1.1 Objective ............................................................................................................................ 1-1
1.2 Requirements for Administrator ......................................................................................... 1-1
1.3 Organization of This Guide ................................................................................................ 1-2
1.3.1 Administrative Tasks ............................................................................................... 1-2
1.3.2 Maintenance Items.................................................................................................. 1-2
1.3.3 Commands and Tools ............................................................................................. 1-2
1.3.4 FAQ ......................................................................................................................... 1-3
Chapter 2 Server Parameter Settings.......................................................................................... 2-1
2.1 Overview of Server Parameter Settings ............................................................................ 2-1
2.2 Modifying Server Time....................................................................................................... 2-1
2.2.1 Operation Effect ...................................................................................................... 2-1
2.2.2 Operation Procedure............................................................................................... 2-1
2.3 Modifying Host name of Server ......................................................................................... 2-2
2.4 Modifying Server IP Address ............................................................................................. 2-3
2.5 Setting Parameters of Server with Multiple IPs ................................................................. 2-4
Chapter 3 User Management........................................................................................................ 3-1
3.1 Overview of User Management ......................................................................................... 3-1
3.2 Introduction to User Account ............................................................................................. 3-1
3.2.1 Types of User Account............................................................................................ 3-1
3.2.2 Operating System User Accounts and the Authority............................................... 3-1
3.2.3 Database User Account and the Authority.............................................................. 3-3
3.2.4 M2000 User Accounts and the Authority ................................................................ 3-3
3.3 Creating Operating System User....................................................................................... 3-3
3.4 Modifying Password of Operating System User ................................................................ 3-4
3.4.2 Modifying Password of root..................................................................................... 3-4
Administrator Guide
Table of Contents
3.4.3 Modifying Password of dbuser ................................................................................ 3-4

3.4.4 Modifying Password of omcuser ............................................................................. 3-4
3.4.5 Modifying Password of ftpuser ................................................................................ 3-4
3.5 Modifying Password of Database User ............................................................................. 3-5
3.6 Creating M2000 User Group.............................................................................................. 3-6
3.7 Creating M2000 User Account........................................................................................... 3-6
3.8 Monitoring M2000 Users.................................................................................................... 3-6
Chapter 4 Log Management ......................................................................................................... 4-1
4.1 Overview of Log Management........................................................................................... 4-1
4.2 Introduction to Log ............................................................................................................. 4-1
4.2.1 Types of Logs.......................................................................................................... 4-1
4.2.2 User Log.................................................................................................................. 4-1
4.2.3 NE Log .................................................................................................................... 4-1
4.2.4 System Log ............................................................................................................. 4-2
4.2.5 Trace log ................................................................................................................. 4-2
4.3 Browsing User Log ............................................................................................................ 4-3
4.4 Browsing System Log ........................................................................................................ 4-3
4.5 Checking Solaris Error Log................................................................................................ 4-3
Chapter 5 Server Performance Monitor ...................................................................................... 5-1
5.1 Overview of Server Performance Monitor ......................................................................... 5-1
5.2 Querying Server Status through Client.............................................................................. 5-1
5.2.1 Function................................................................................................................... 5-1
5.3 Setting the Threshold of Server Status Alarm ................................................................... 5-2
5.3.1 Function................................................................................................................... 5-2
5.4 Querying System Performance.......................................................................................... 5-2
ii
Administrator Guide
Table of Contents

5.5 Adjusting System Performance ......................................................................................... 5-3
Chapter 6 M2000 Process and Service Management ................................................................ 6-1
6.1 Overview of M2000 Process and Service Management.................................................... 6-1
6.2 Introduction to M2000 Processes and Services ................................................................ 6-1
6.2.1 Overview to Processes and Services ..................................................................... 6-1
6.2.2 SystemConfigurator ................................................................................................ 6-1
6.2.3 sac_agent................................................................................................................ 6-1
6.2.4 em_agent ................................................................................................................ 6-2
6.2.5 monitor_agent ......................................................................................................... 6-2
6.2.6 partition_agent......................................................................................................... 6-3
6.2.7 audit_agent.............................................................................................................. 6-3
6.2.8 mo_agent ................................................................................................................ 6-3
6.2.9 sm_agent................................................................................................................. 6-4
6.2.10 med_agent ............................................................................................................ 6-4
6.2.11 ts_agent................................................................................................................. 6-4
6.2.12 ifms_agent............................................................................................................. 6-4
6.2.13 manager_agent ..................................................................................................... 6-4
6.2.14 pm_agent .............................................................................................................. 6-5
6.2.15 cmserver_agent..................................................................................................... 6-5
6.2.16 swm_agent ............................................................................................................ 6-5
6.2.17 fmnotify_agent....................................................................................................... 6-5
6.2.18 proxy_agent........................................................................................................... 6-6
6.2.19 notify_agent........................................................................................................... 6-6
6.3 Querying Number of M2000 Processes ............................................................................ 6-6
6.4 Querying Service Status .................................................................................................... 6-6
6.5 Starting M2000 Services.................................................................................................... 6-8
6.6 Stopping M2000 Services.................................................................................................. 6-9
Chapter 7 Database Management................................................................................................ 7-1
7.1 Overview of Database Management ................................................................................. 7-1
7.2 Introduction to Database.................................................................................................... 7-1
7.2.1 Overview of Database............................................................................................. 7-1
iii
Administrator Guide
Table of Contents
7.2.2 omcdb...................................................................................................................... 7-1

7.2.3 fmdb ........................................................................................................................ 7-2
7.2.4 pmdb ....................................................................................................................... 7-2
7.2.5 sysmdb .................................................................................................................... 7-3
7.3 Querying Database Status................................................................................................. 7-4
7.4 Manually Displacing Alarm Data........................................................................................ 7-5
7.5 Manually Displacing User Log ........................................................................................... 7-5
7.6 Setting Auto Displacing for Alarm Data ............................................................................. 7-6
7.7 Setting Auto Displacing for User Log................................................................................. 7-7
7.8 Deleting Performance Task ............................................................................................... 7-7
7.9 Clearing Database ............................................................................................................. 7-8
Chapter 8 Disk Space Management............................................................................................. 8-1
8.1 Overview of Disk Space Management .............................................................................. 8-1
8.2 Introduction to File System ................................................................................................ 8-1
8.2.1 Overview of System Structure................................................................................. 8-1
8.2.2 Server File System .................................................................................................. 8-1
8.2.3 Client File System ................................................................................................... 8-2
8.3 Query Disk Space .............................................................................................................. 8-2
8.4 Clearing Disk Space .......................................................................................................... 8-3
Chapter 9 Dual-Plane Configuration............................................................................................ 9-1
9.1 Overview of Dual-Plane Configuration .............................................................................. 9-1
9.2 Introduction to Dual-Plane ................................................................................................. 9-1
9.3 Configuration Procedure of Dual-Plane ............................................................................. 9-2
9.4 Planning IP Data ................................................................................................................ 9-2
iv
Administrator Guide
Table of Contents
9.5 Manually Setting Dual-Plane ............................................................................................. 9-2

9.6 Automatically Setting Dual-Plane ...................................................................................... 9-3
9.7 Verifying Dual-Plane Settings ............................................................................................ 9-4
9.7.3 Abnormal Handling.................................................................................................. 9-4
Chapter 10 NTP Service Configuration ..................................................................................... 10-1
10.1 Overview of NTP Service Configuration ........................................................................ 10-1
10.2 Introduction to NTP Service........................................................................................... 10-1
10.3 Setting M2000 as Top NTP Server................................................................................ 10-2
10.4 Setting M2000 as Middle NTP Server ........................................................................... 10-2
10.5 Setting M2000 as NTP Client ........................................................................................ 10-2
10.6 Starting NTP Service ..................................................................................................... 10-2
10.7 Checking Running Status of NTP Service..................................................................... 10-3
10.8 Stopping NTP Service ................................................................................................... 10-3
Chapter 11 Backup and Restoration ......................................................................................... 11-1
11.1 Overview of Backup and Restoration ............................................................................ 11-1
11.2 Introduction to Backup and Restoration ........................................................................ 11-1
11.2.1 M2000 System Backup Contents........................................................................ 11-1
11.2.2 M2000 System Backup and NE Data Backup .................................................... 11-1
11.2.3 The Mode of M2000 System Backup and Restore ............................................. 11-2
11.2.4 Name of Backup Files ......................................................................................... 11-2
11.2.5 Storage Media of Backup File ............................................................................. 11-2
11.3 Function Setting ............................................................................................................. 11-3
11.3.1 Introduction to Configuration File ........................................................................ 11-3
11.3.2 Setting Tape Drive Path ...................................................................................... 11-3
11.3.3 Setting Backup Media ......................................................................................... 11-3
11.4 Automatically Backing Up M2000 System..................................................................... 11-4
11.4.1 Introduction to Auto Backup ................................................................................ 11-4
11.4.2 Setting Auto Backup Time................................................................................... 11-5
11.5 Manually Backing Up M2000 System ............................................................................ 11-5
11.5.1 Introduction to Manual Backup............................................................................ 11-5
11.5.2 Carrying Out Manual Backup on Client............................................................... 11-5
11.5.3 Carrying Out Manual Backup on Server ............................................................. 11-6
11.6 Restoring M2000 System .............................................................................................. 11-6
11.6.1 Function Introduction........................................................................................... 11-6
11.6.2 Operation Procedure........................................................................................... 11-6
11.7 Backing Up Operating System....................................................................................... 11-7
v
Administrator Guide
Table of Contents

11.8 Restoring Operating System.......................................................................................... 11-9
11.8.3 Restoring Tape Information................................................................................. 11-9
11.8.4 Setting Up Equipment Tree and Boot Block ..................................................... 11-10
11.8.5 Modifying System File and File System Information ......................................... 11-11
11.8.6 Restarting System ............................................................................................. 11-12
11.8.7 Encapsulating Disk Using Volume Manager..................................................... 11-12
Chapter 12 Routine Maintenance............................................................................................... 12-1
12.1 Overview of Routine Maintenance................................................................................. 12-1
12.2 Daily Maintenance ......................................................................................................... 12-1
12.2.1 Daily Maintenance Item List ................................................................................ 12-1
12.2.2 Checking Alarm Information................................................................................ 12-1
12.2.3 Checking Log Information ................................................................................... 12-2
12.2.4 Checking Solaris Error Log ................................................................................. 12-2
12.2.5 Checking Database Status.................................................................................. 12-2
12.2.6 Checking Hard Disk Space ................................................................................. 12-2
12.2.7 Checking CPU Utilization .................................................................................... 12-2
12.2.8 Checking Number of Processes.......................................................................... 12-2
12.2.9 Checking Service Status ..................................................................................... 12-3
12.3 Weekly Maintenance ..................................................................................................... 12-3
12.3.1 Weekly Maintenance Item List ............................................................................ 12-3
12.3.2 Backing Up M2000 System................................................................................. 12-3
12.3.3 Checking M2000 Server Time............................................................................. 12-3
12.3.4 Finding core Files ................................................................................................ 12-4
12.3.5 Clearing Useless Files ........................................................................................ 12-4
12.4 Monthly Maintenance..................................................................................................... 12-4
12.4.1 Monthly Maintenance Item List ........................................................................... 12-4
12.4.2 Checking Power Supply ...................................................................................... 12-4
12.4.3 Checking Server Hardware ................................................................................. 12-4
12.4.4 Checking Auxiliary Devices of Server ................................................................. 12-4
Chapter 13 Troubleshooting ...................................................................................................... 13-1
13.1 Overview of Troubleshooting ......................................................................................... 13-1
13.2 Troubleshooting Procedure ........................................................................................... 13-1
13.2.1 Overview of Troubleshooting Procedure............................................................. 13-1
13.2.2 Information Collection ......................................................................................... 13-1
13.2.3 Fault Location...................................................................................................... 13-1
13.2.4 Fault Clearance ................................................................................................... 13-2
13.3 Auto Shutdown of Operating System ............................................................................ 13-2
13.3.1 Symptom ............................................................................................................. 13-2
vi
Administrator Guide
Table of Contents
13.3.2 Fault Analysis ...................................................................................................... 13-2

13.3.3 Fault Clearance ................................................................................................... 13-3
13.4 Abnormal Service Restart.............................................................................................. 13-3
13.4.1 Symptom ............................................................................................................. 13-3
13.4.2 Fault Analysis ...................................................................................................... 13-3
13.4.3 Fault Clearance ................................................................................................... 13-3
13.5 Abnormal Service Termination ...................................................................................... 13-4
13.5.1 Symptom ............................................................................................................. 13-4
13.5.2 Fault Analysis ...................................................................................................... 13-4
13.5.3 Fault Clearance ................................................................................................... 13-4
13.6 M2000 Services Starting or Stopping Failure ................................................................ 13-5
13.6.1 Symptom ............................................................................................................. 13-5
13.6.2 Fault Analysis ...................................................................................................... 13-5
13.6.3 Fault Clearance ................................................................................................... 13-5
Chapter 14 Emergency Maintenance......................................................................................... 14-1
14.1 Overview of Emergency Maintenance........................................................................... 14-1
14.2 Emergency Maintenance for M2000 Server .................................................................. 14-1
14.3 Emergency Maintenance for M2000 Client ................................................................... 14-1
Chapter 15 Command Guide ...................................................................................................... 15-1
15.1 Overview of Command Guide........................................................................................ 15-1
15.2 Introduction to Commands............................................................................................. 15-1
15.2.1 Path of Commands ............................................................................................. 15-1
15.2.2 Prerequisites of Using Commands...................................................................... 15-1
15.3 svc_profile.sh ................................................................................................................. 15-1
15.3.1 Function of svc_profile.sh ................................................................................... 15-1
15.3.2 Path of svc_profile.sh.......................................................................................... 15-1
15.3.3 Running svc_profile.sh........................................................................................ 15-1
15.4 start_svc......................................................................................................................... 15-2
15.4.1 Command Function............................................................................................. 15-2
15.4.2 Example .............................................................................................................. 15-2
15.5 stop_svc......................................................................................................................... 15-3
15.5.2 Example .............................................................................................................. 15-3
15.6 kill_svc ........................................................................................................................... 15-3
15.6.2 Example .............................................................................................................. 15-3
15.7 svc_adm cmd status .................................................................................................... 15-3
vii
Administrator Guide
Table of Contents
15.7.2 Example .............................................................................................................. 15-3

15.8 svc_ps............................................................................................................................ 15-4
15.8.2 Example .............................................................................................................. 15-4
15.9 top .................................................................................................................................. 15-4
15.9.2 Example .............................................................................................................. 15-4
15.10 svc_adm cmd reload.................................................................................................. 15-5
15.10.1 Command Function........................................................................................... 15-5
15.10.2 Example ............................................................................................................ 15-5
15.11 svc_stacks ................................................................................................................... 15-5
15.11.2 Example ............................................................................................................ 15-5
15.12 svc_lockdump .............................................................................................................. 15-6
15.12.2 Example ............................................................................................................ 15-6
Chapter 16 Tool Guide ................................................................................................................ 16-1
16.1 Overview of Tool Guide ................................................................................................. 16-1
16.2 Tape Drive Management Tool ....................................................................................... 16-1
16.2.1 Function............................................................................................................... 16-1
16.2.2 Starting method ................................................................................................... 16-1
16.2.3 Operation Guide .................................................................................................. 16-2
16.3 M2000 Diagnostic Tooling ............................................................................................. 16-2
16.3.1 Function............................................................................................................... 16-2
16.3.2 Running Diagnostic Tool ..................................................................................... 16-3
16.3.3 Abnormal Handling.............................................................................................. 16-5
16.3.4 Forbidding Using Diagnostic Tool ....................................................................... 16-5
16.4 Performance Job Result Auto Export Tool .................................................................... 16-5
16.4.1 Function............................................................................................................... 16-5
16.4.2 Function Settings ................................................................................................ 16-5
16.4.3 Running Auto Export Tool ................................................................................... 16-6
16.4.4 Stopping Auto Export Tool .................................................................................. 16-7
16.4.5 Abnormal Handling.............................................................................................. 16-7
16.5 IP Modification Tool ....................................................................................................... 16-8
16.5.1 Function............................................................................................................... 16-8
16.5.2 Prerequisites ....................................................................................................... 16-8
16.5.3 Querying IP Settings ........................................................................................... 16-8
16.5.4 Modifying Solaris IP Address, Host name, Default Gateway and Subnet Mask. 16-9
16.5.5 Modifying Sybase IP ........................................................................................... 16-9
16.5.6 Modifying Sybase Service IP and Port Number................................................ 16-10
16.5.7 Modifying Host Name........................................................................................ 16-10
16.5.8 Modifying Gateway............................................................................................ 16-10
viii
Administrator Guide
Table of Contents
Chapter 17 FAQ ........................................................................................................................... 17-1

17.1 Overview of FAQ ........................................................................................................... 17-1
17.2 Logging in as root though Telnet ................................................................................... 17-1
17.2.1 Question .............................................................................................................. 17-1
17.2.2 Answer ................................................................................................................ 17-1
17.3 Logging in as root though FTP ...................................................................................... 17-1
17.3.1 Question .............................................................................................................. 17-1
17.3.2 Answer ................................................................................................................ 17-1
17.4 Installing Tape Drive ...................................................................................................... 17-2
17.4.1 Question .............................................................................................................. 17-2
17.4.2 Answer ................................................................................................................ 17-2
17.5 Setting Default Route..................................................................................................... 17-3
17.5.1 Question .............................................................................................................. 17-3
17.5.2 Answer ................................................................................................................ 17-3
17.6 Adding and Deleting Routes .......................................................................................... 17-3
17.6.1 Question .............................................................................................................. 17-3
17.6.2 Answer ................................................................................................................ 17-3
17.7 "/etc/rc2.d" in Solaris...................................................................................................... 17-4
17.7.1 Question .............................................................................................................. 17-4
17.7.2 Answer ................................................................................................................ 17-4
17.8 Querying Hardware Configuration of Server ................................................................. 17-4
17.8.1 Question .............................................................................................................. 17-4
17.8.2 Answer ................................................................................................................ 17-4
17.9 Confirming Startup of Sybase........................................................................................ 17-5
17.9.1 Question .............................................................................................................. 17-5
17.9.2 Answer ................................................................................................................ 17-5
17.10 Starting Sybase ........................................................................................................... 17-5
17.10.1 Question ............................................................................................................ 17-5
17.10.2 Answer .............................................................................................................. 17-5
17.11 Stopping Sybase.......................................................................................................... 17-6
17.11.1 Question ............................................................................................................ 17-6
17.11.2 Answer .............................................................................................................. 17-6
Appendix Acronyms and Abbreviations ........................................................................................ 1
Index ................................................................................................................................................ i-1
ix
Administrator Guide
Chapter 1 Overview of Administrator Guide

1.1 Objective
The documentation package of iManager M2000 Mobile Element Management System
(M2000 for short) contains two task-oriented manuals: iManager M2000 Mobile
Element Management System Administrator Guide and iManager M2000 Mobile
Element Management System Operation Manual.
z
iManager M2000 Mobile Element Management System Administrator Guide
The intended reader of this guide is system administrator. This guide provides the
related concepts and detailed operation procedures of the system administration tasks.
This guide focuses on M2000 single-server system administration, including Server
status monitoring, database management, disk space management, user management,
system backup and restoration, and general fault handling.
z
iManager M2000 Mobile Element Management System Operation Manual
The intended reader of this manual is M2000 operator. This manual provides the
related concepts and detailed operation procedures of the operation tasks. This manual
focuses on operations and maintenance of the mobile networks through M2000,
including network performance monitoring, alarm query, NE configuration, NE software
upgrade and entire network data backup and restoring.
1.2 Requirements for Administrator

The system administrator of M2000 must be familiar with the following items:
z
Solaris and Windows operating systems
Sybase database
Knowledge of computer networks such as Ethernet, TCP/IP, and Client/Server
M2000 system and its functions
Refer to iManager M2000 Mobile Element Management System Description and this
guide.
z
Installation of M2000 Server and Client application software
Refer to iManager M2000 Mobile Element Management System Installation Manual

z
Operation on M2000 Client
Refer to iManager M2000 Mobile Element Management System Online Help and
iManager M2000 Mobile Element Management System operation Manual.
z
Routine maintenance and troubleshooting on M2000
1-1
Administrator Guide
Refer to "Chapter 12
Routine Maintenance", "Chapter 13
Troubleshooting" and
"Chapter 14 Emergency Maintenance" in this guide.
1.3 Organization of This Guide

1.3.1 Administrative Tasks
This guide introduces the following administrative tasks and the related concepts:
z
Server parameter setting
User management
Log management
Server performance monitor
M2000 process and service management
Database management
Disk space management
Dual-plane configuration
NTP service configuration
Backup and restoration
Each of the above tasks is explained in an individual chapter. The first section of each
chapter describes the structure of the chapter, the second section introduces the task
concepts and the third section explains the task details. The second section may not be
applicable for a few chapters, and so, may not be present.
1.3.2 Maintenance Items

This guide also introduces the following maintenance items based on administration
tasks:
z
Routine maintenance
Troubleshooting
Emergency maintenance
This part is concerning on M2000.

For the maintenance and fault handling of Solaris operating system or Sybase
database, refer to Solaris system administrator manual or Sybase system administrator
manual.
For operation and maintenance of NE, refer to iManager M2000 Mobile Element
Management System Operation Manual, and NEs corresponding manual.
1.3.3 Commands and Tools

This guide also introduces M2000 commands and tools in system administration:
z
Command guide
Tool guide
1-2
Administrator Guide
1.3.4 FAQ
This guide also introduces the frequently asked question and the solutions concerning
Solaris operating system and Sybase database.
1-3
Administrator Guide
Chapter 2 Server Parameter Settings

2.1 Overview of Server Parameter Settings
This chapter introduces the modifications and settings of the Server parameters,
including:
z
Modifying Server time
Modifying host name of Server
Modifying IP address of Server
Setting multiple IPs for Server
2.2 Modifying Server Time

2.2.1 Operation Effect
System time modification during M2000 running will affect the system timer, thus
disabling the timed cleaning of the database tempdb. When tempdb is full, Sybase
cannot work and M2000 cannot run.
It is necessary to stop M2000 services if you want to modify system time, and thus
M2000 can not process the performance data and alarm data of the managed NEs
when M2000 services are not running. After M2000 services have been restarted,
M2000 will get the data from NEs by using auto synchronization function and then
process the data.
2.2.2 Operation Procedure

To modify the Server time, perform the following operations on the Server:
1)
Log in as root.
2)
Execute the following commands to stop M2000 services.
# stop_svc
3)
Execute the following command to stop Sybase.
# isql SSYB Usa P<user sa password>

1> shutdown SYB_BACKUP
2> go
1> shutdown SYB
2> go
4)
Execute the following command to check the time zone of the operating system.
# echo $TZ
2-1
Administrator Guide
If the current time zone is incorrect, modify the file "/etc/TIMEZONE" to change the
value of "TZ" to the local time zone. For example, "TZ=PRC".
Note:
You can query the time zone information through "/usr/share/lib/zoneinfo".
5)
Use the command "date" to set system date and time.
For example, to set the system date and time to 2003-11-17 16:30:43, execute the
command:
# date 111716302003.43
Mon Nov 17 17:53:29 CST 2003
6)
Execute the following command to restart the Server.
# init 6
When the operating system starts up, Sybase services and M2000 services will start
automatically if M2000 Server software application has been installed.
2.3 Modifying Host name of Server

Do not modify the host name of the Server during M2000 running. Otherwise, the
M2000 services will stop abnormally.
It is necessary to stop M2000 services if you want to modify the host name, and thus
process the data.

To change the host name of the Server, perform the following operations on the Server:
1)
Log in as root.
2)
# stop_svc
3)
Execute the following command to stop sybase.

2> go
2-2
Administrator Guide
1> shutdown SYB

2> go
4)
Use the IP modification tool to modify the host name.
# iptools -H host-name
For example, to set the host name to "omc":
# iptools -H omc
Note:
For the functions and usage of IP modification tool iptools, refer to "16.5 IP Modification Tool".
5)
Edit the file "<M2000 installation directory>/etc/conf/tao.cfg". Change the original

host name to the new host name.
6)
# init 6
2.4 Modifying Server IP Address

Do not modify the IP address of the Server during M2000 running. Otherwise, the
M2000 services will stop abnormally.
It is necessary to stop M2000 services if you want to modify the Server IP address, and
process the data.

To modify the IP address of the Server, perform the following operations on the Server:
1)
Log in as root.
2)
# stop_svc
3)

2-3
Administrator Guide
2> go
1> shutdown SYB
2> go
4)
Execute the following command to query the current IP settings.
# ifconfig a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.161.45.241 netmask fffffe00 broadcast 10.161.45.255
ether 0:3:ba:12:f9:12
5)
Use the IP modification tool to modify the IP settings in Solaris and Sybase.
Note:
For the functions and usage of IP modification tool, refer to "16.5 IP Modification Tool".
# iptools {-n interface-name -i ip-address -m subnet-mask -G default -gateway -H

host-name -d }
For example, modify the IP of Solaris system as 10.70.141.54, host name as host,
default gateway as 10.70.141.1, and all Server IPs of Sybase databases as
10.70.141.54.
# iptools n eri0 i 10.70.141.54 m 255.255.255.0 G 10.70.141.1 H host d
6)
# init 6
2.5 Setting Parameters of Server with Multiple IPs

When a Server has multiple IPs, it is necessary to specify one of them for M2000
services. Otherwise, the Client cannot set up connection with the Server.
It is necessary to stop M2000 services if you want to set multiple IPs, and thus M2000
can not process the performance data and alarm data of the managed NEs when
M2000 services are not running. After M2000 services have been restarted, M2000 will
get the data from NEs by using auto synchronization function and then process the
data.
2-4
Administrator Guide

To specify an IP for M2000 services, perform the following operations on the Server:
1)
Log in as root.
2)
# stop_svc
3)

2> go
1> shutdown SYB
2> go
4)
Edit the file "/etc/hosts", to make the host name correspond to an IP, which is used
to connect the Client and managed NEs.
For example, among the two IP of the Server "10.161.70.200" and "10.121.5.208",
"10.121.5.208"
is
used
to
connect
the
Client.
"<M2000
installation
directory>/etc/conf/tao.cfg" shows that the host name is "aries", then in the file
"/etc/hosts", add a note "#" before "10.161.70.200".
#
# Internet host table
#
127.0.0.1
localhost
#10.161.70.200 aries loghost

10.121.5.208
5)
aries loghost
# init 6
2-5
Administrator Guide
Chapter 3 User Management

3.1 Overview of User Management
This chapter introduces the concepts related to user management, including type and
authority of user account, and provides the details of the major user management tasks,
including:
z
Creating operating system user account
Modifying operating system user account
Modifying database user password of database
Creating M2000 user group
Creating M2000 user account
Monitoring M2000 user
3.2 Introduction to User Account

3.2.1 Types of User Account
The operation of M2000 system involves three types of user accounts:
z
User account of operating system: For M2000 Server operations.
User account of database: For M2000 Server database operations.
User account of M2000: For M2000 Client operations.
3.2.2 Operating System User Accounts and the Authority

To carry out operations on M2000 Server, you should have a user account of the
operating system.
Apart from the default user accounts of the operating system Solaris, you should create
three user accounts, dbuser, omcuser, and ftpuser. You should also create a user group
omcsysm.
If you install Report System, the installer will create the user account inrpt and the user
group inrpt automatically.
I. root
The user root is with the highest authority to the system. This user can control all
resources, create other users, grant authorities to other users, and perform all the
operation functions provided by the operating system.
Only the user root can install and uninstall the M2000 Server application software, and
start and stop M2000 services.
3-1
Administrator Guide
II. dbuser
The user dbuser handles routine operation and maintenance of Sybase database. The
user can perform any operation such as interaction with the database through isql on
the database.
You should create dbuser before installing Sybase. The related attributes are as
follows:
z
Home directory: /opt/sybase
The group that it belongs to: staff
Login shell: /bin/bash
III. omcuser
The user omcuser has the authority to perform routine operation and maintenance on
the M2000 system, including querying system status, backing up and restoring system
data. The user omcuser also has the authority to access databases. The user can
neither install/uninstall M2000 Server application software, nor start/stop M2000
services.
You should create omcuser before installing the M2000 Server application software.
The attributes of the user are as follows:
z
Home directory: /export/home/omc
The primary group that it belongs to: staff.
The secondary group that it belongs to: sys, root, omcsysm.
IV. ftpuser
The user ftpuser manages software of NEs and transfers software information to NEs.
You should create ftpuser before installing M2000 Server application software. The
attributes of the user are as follows:
z
Home directory: /export/home/sysm
The group that it belongs to: omcsysm
V. inrpt
The user inrpt manages the Intelligent Report System. You do not need to create inrpt
manually. When the Intelligent Report System is installed, the user inrpt will be created
automatically. The attributes of the user are as follows:
z
Home directory: /opt/inrpt
The group that it belongs to: inrpt
Login shell: /usr/bin/csh
3-2
Administrator Guide
3.2.3 Database User Account and the Authority

To use M2000 Server database Sybase, you need a user account of Sybase.
The user sa is the default user account of Sybase. It has the highest administration
authorities of the database.
For M2000 system, only the user sa is necessary.
3.2.4 M2000 User Accounts and the Authority

After the installation of M2000 Server and Client, the user "admin" and the user group
"administrator" will be created. "admin" and "administrator" have all operation
authorities to all NEs.
For detailed description of M2000 user account and authority, refer to iManager M2000
Mobile Element Management System Operation Manual.
3.3 Creating Operating System User

After an operating system Solaris user account is created, the user information will be
recorded in Solaris system file.
Before the installation of Sybase and M2000 Server software, it is necessary to create
three users manually: dbuser, omcuser and ftpuser. For creating method, refer to
iManager M2000 Mobile Element Management System Installation Manual. It is
necessary to set password for each user and the password update period.
For details on user creation, refer to "3.3.2 Operation Procedure".

To create a Solaris operating system user account, perform the following operations on
the Server:
1)
Log in as root.
2)
Execute the following command to run the system administration tool:
# admintool
3)
In the dialog box [Admintool: Users], select the menu [Edit/Add].
4)
In the dialog box [Admintool: Add User], set the new user properties, and then click
<OK> to close the dialog box.
3-3
Administrator Guide
3.4 Modifying Password of Operating System User

It is necessary to stop the M2000 services to modify user password of "ftpuser". The
modification of passwords of "root", "dbuser", "omcuser" and other users will not affect
the running of M2000.
3.4.2 Modifying Password of root

1)
Log in as root.
2)
Execute the following command to modify the password of "root":
# passwd root
New password:
Re-enter new password:
passwd (SYSTEM): passwd successfully changed for root
3.4.3 Modifying Password of dbuser

1)
Log in as root.
2)
Execute the following command to modify the password of "dbuser":
# passwd dbuser
New password:
passwd (SYSTEM): passwd successfully changed for dbuser
3.4.4 Modifying Password of omcuser

1)
Log in as root.
2)
Execute the following command to modify the password of "omcuser"
# passwd omcuser
New password:
passwd (SYSTEM): passwd successfully changed for omcuser
3.4.5 Modifying Password of ftpuser

1)
Log in as root.
2)
Execute the following command to modify the password of "ftpuser":
# passwd ftpuser
New password:
passwd (SYSTEM): passwd successfully changed for ftpuser
3-4
Administrator Guide
3)
Execute the following command to stop the M2000 services.
# stop_svc
4)
Run the M2000 parameter modification tool:
# /opt/OMC/imap_setup.sh
5)
In the dialog box shown in Figure 3-1, select "Remote control parameters" to
modify the password of ftpuser.
Figure 3-1 M2000 parameter setting

6)
Execute the following command to start M2000 services.
# start_svc
3.5 Modifying Password of Database User

It is necessary to stop M2000 services to modify the password of the user sa.

1)
Log in as root.
3-5
Administrator Guide
2)
Execute the following command to stop M2000 services.
# stop_svc
3)
Execute the following command to modify the password of Sybase user "sa":
# isql SSYB -Usa P<old password>

1>sp_password <old password >, <new password>
2>go
4)
Run the M2000 parameter modification tool:
# /opt/OMC/imap_setup.sh
5)
In the dialog box shown in Figure 3-1, select "Database parameters" to modify the
password of "sa".
6)
Execute the following command to start M2000 services.
# start_svc
3.6 Creating M2000 User Group

After the creation of M2000 user group, the M2000 system will record all information of
this user group.

Carry out the operations on M2000 Client. For details, refer to iManager M2000 Mobile
3.7 Creating M2000 User Account

After the creation of M2000 user account, the M2000 system will record all information
of this user.

3.8 Monitoring M2000 Users

The operation of M2000 user monitoring uses few system resources and has no effect
on the system.
3-6
Administrator Guide

3-7
Administrator Guide
Chapter 4 Log Management

4.1 Overview of Log Management
This chapter introduces the concepts related to log management, including log types
and their corresponding contents, and provides the details of log management tasks,
including:
z
Browsing user log
Browsing system log
Checking Solaris error log
4.2 Introduction to Log

4.2.1 Types of Logs
M2000 system provides four types of logs:
z
User log
NE log
System log
trace log
4.2.2 User Log

I. Function
The user log records the operations of M2000 users. M2000 system administrator and
operators can query the user log.
II. Path
The user log is stored in the database in M2000 Server. Its information can be queried
and dumped through Client.
III. Contents
The information in user log includes operation contents, user name, operation start/end
time, user type, terminal, operation objective and result.
4.2.3 NE Log
I. Function
The NE log records the operations on managed NEs. M2000 system administrator and
operators can query the NE log.
4-1
Administrator Guide
II. Path
The NE log is generated on NEs, and then sent to M2000 Server and stored in the
database in M2000 Server. Its information can be queried through Client.
III. Contents
The information in NE log includes user name, terminal, operation start/end time,
operation contents and operation result, NE type and name.
4.2.4 System Log

I. Function
The system log records the operation of the system. M2000 system administrator can
query system log.
II. Path
The system log is stored in "/export/home/omc/var/logs" in M2000 Server. The file
names are iMAP.root.log, iMAP.root.log.1 and iMAP.root.log.2.
The system log information is written into iMAP.root.log.1 and iMAP.root.log.2 in cycle
and normally not into iMAP.root.log.
The system log information can be queried through Client.
III. Contents
The contents of the system log include information header and information. The
information header includes level, module identification and record time.
4.2.5 Trace log

I. Function
The trace log is used to locate the system internal problems.
II. Path
The trace log is stored in "/export/home/omc/var/logs" in M2000 Server. The file names
are iMAP.root.trace, iMAP.root.trace.1 and iMAP.root.trace.xxx.tar.gz.
iMAP.root.trace and iMAP.root.trace.1 are used to save the current trace information.
When
one
trace
file
is
full,
it
will
be
converted
to
/export/home/omc/var/logs/traceback/iMAP.root.trace.xxx.tar.gz. The information will

then be written in the other trace file. When the other file is full, again it is converted to
iMAP.root.trace.xxx.tar.gz. The information is then written into the previous file. In this
way, the trace information is updated into these two files alternatively.
4-2
Administrator Guide
III. Contents
The contents of trace log consist of information header and information. The
information header includes level, module identification, service proxy identification
(process name), record time and process thread ID.
4.3 Browsing User Log

The operation of browsing user log uses few system resources and will not affect the
system.

4.4 Browsing System Log

The operation of browsing system log uses few system resources and will not affect the
system.

To browse system log, perform the following operations:
1)
Log in to the Client.
2)
In the main window, select the menu [System/Log/Log Manager].
3)
In the dialog box [Log Manager], select "System Log" in the navigation tree, and
the click <Query> in the right window.
4)
Check whether any error information exists.
4.5 Checking Solaris Error Log

The operation of browsing Solaris error log uses few system resources and will not
affect the system.

To check the Solaris error log, perform the following operations on the Server:
1)
Log in as omcuser.
2)
Open the file "/var/adm/messages".

4-3
Administrator Guide
3)
Check whether this file contains any error information. Normally, there is no error
information.
4)
Open the file "/var/log/syslog".
5)
Check whether this file contains any error information. Normally, there is no error
information.
4-4
Administrator Guide
Chapter 5 Server Performance Monitor

5.1 Overview of Server Performance Monitor
This chapter provides the details of Server performance monitor tasks, including:
z
Querying Server status through Client
Setting Server status alarm threshold
Querying system performance
Adjusting system performance
5.2 Querying Server Status through Client

5.2.1 Function
It is possible to query M2000 Server status through M2000 Client, including:
z
System performance
Hard Disk
Database
Service

To query Server status, perform the following operations:
1)
2)
In the main window, select the menu [Tools/System Monitor/Monitor Browser].
3)
In the dialog box [System Monitor Browser], select the item to be queried, as
shown in Figure 5-1.
Figure 5-1 System monitor Browser
5-1
Administrator Guide
5.3 Setting the Threshold of Server Status Alarm

5.3.1 Function
It is possible to set the threshold of M2000 Server status alarm through M2000 Client,
including:
z
CPU occupancy
Memory occupancy
Hard Disk space occupancy
Database space occupancy
When an item reaches its threshold, the system will generate the corresponding alarm.

To set Server status alarm threshold, perform the following operations:
1)
2)
In the main window, select the menu [Tools/System Monitor/Configurations].
3)
In the dialog box [System Monitor Configurations], select the item to be set, as
shown in Figure 5-2.
Figure 5-2 System monitor configurations
5.4 Querying System Performance

The operation of querying system performance uses few system resources and will not
affect the system.
5-2
Administrator Guide

Besides querying through Client in the way introduced in 5.2 Querying Server Status
through Client, you can also perform the following operations on M2000 Server:
1)
Log in as omcuser.
2)
Execute the following command:
bash-2.03$ vmstat 1 10
procs
r b w
memory
swap
free
page
re
disk
faults
mf pi po fr de sr s0 s6 -- --
in
sy
543
87
cpu
cs us sy
id
0 0 0 5114824 1032584 24 95 8
692 17
76
0 0 0 4884768 891800 43 264 0
536 30913 1046 50 19
31
0 0 0 4885104 892136 0
546 30019 910 53 16
609 30131 1119 54 14
0 0 0 4883552 890936 98 747 168 8 8
0 25
739 33041 1263 54 20
31
0 0 0 4885104 892136 0
32
26
0 0 0 4883888 891272 0
532 31216 892 50 17
506 30112 963 52 15
0 0 0 4883552 890936 43 258 0
890 31651 1787 57 13
541 30023 1063 53 16
0 0 0 4883760 890640 289 1651 192 0 0 0 0 26
869 32775 1106 56 22
33
0 0 0 4883888 891272 0
33
29
0 0 0 4883888 891272 0
31
22
In the output, us is the percentage usage of CPU time of user process, sy is the
percentage usage of CPU time of system process and id is the percentage idle of
CPU time.
3)
Check the system performance. Normally the CPU occupancy must be lower than
80%. That is, the value of id must be higher than 20.
5.5 Adjusting System Performance

If the adjustment is improper, the system operation may become abnormal.
5-3
Administrator Guide

If the CPU occupancy is too high (higher than 80%), perform the following operations:
1)
Check whether the high CPU occupancy is caused by number of reported alarms
exceeding the threshold.
2)
Execute the following command to check the CPU occupancy of each process.
bash-2.03$ top
load averages:
95 processes:
0.07,
0.09,
0.10
11:30:4
94 sleeping, 1 on cpu
CPU states: 97.4% idle,
1.5% user,
1.1% kernel,
0.0% iowait,
0.0% swap
Memory: 2048M real, 211M free, 2743M swap in use, 2821M swap free
PID USERNAME THR PRI NICE
SIZE
RES STATE
TIME
CPU COMMAND
13529 root
60
58
75M
56M sleep
160:11
0.91% imapsvcd
357 root
180
58
75M
66M sleep
916:19
0.72% dataserver
345 root
72
58
73M
65M sleep
639:50
0.49% dataserver
13524 root
27
48
60M
32M sleep
112:23
0.42% imapsysd
13761 root
37
58
155M
115M sleep
60:03
0.24% imapsvcd
13531 root
25
58
96M
69M sleep
69:42
0.16% imapsvcd
10904 root
128
58
321M
223M sleep
9:19
0.16% imapsvcd
13871 root
14
58
285M
188M sleep
10:10
0.14% imapsvcd
45 root
58
0 2072K 1360K cpu/1
0:00
0.12% top
13527 root
14
58
96M
66M sleep
5:24
0.07% imapsvcd
13540 root
11
58
99M
66M sleep
6:34
0.05% imapsvcd
13591 root
30
58
322M
236M sleep
32:56
0.05% imapsvcd
13520 root
27
6 root
13511 root
56
3)
58
0
58
58M
0
27M sleep
352K
248K sleep
25M
22M sleep
8:22
0.02% Monitor_Service
0:00
0:29
0.02% sh
0.01% Naming_Service
Check whether the value of database memory parameter is too small. It is

recommended that the value of "set shmsys:shminfo_shmmax" in the file
"/etc/system" be the size of the Server memory (unit: MB) 1024 1024 / 2.
For example, if the memory of the Server is 4096MB, then:

set shmsys:shminfo_shmmax=2,147,483,648
5-4
Administrator Guide
Chapter 6
M2000 Process and Service Management
Chapter 6 M2000 Process and Service

Management
6.1 Overview of M2000 Process and Service Management
This chapter introduces the concepts related to M2000 services and processes,
including types and functions of the processes and services, and provides the details of
the major process and service management tasks, including:
z
Querying number of M2000 processes
Querying service status
Starting M2000 services
Stopping M2000 services
6.2 Introduction to M2000 Processes and Services

6.2.1 Overview to Processes and Services
When M2000 is running normally, the Server starts 18 processes. Each process
includes different services and provides different functions. The following section
introduces the function of each processes and services.
6.2.2 SystemConfigurator
SystemConfigurator manages all other local processes. In a distributed environment, it
communicates and interacts with imapsysd processe on other machines, so as to avoid
the impact on application processes caused by the distributed system.
When M2000 services are running, this process cannot be stopped.
Dependent service: None.
6.2.3 sac_agent
The process sac_agent provides the following services:
z
ScheduleService
ScheduleService provides a frame construction, which enables the scheduling and

control of user tasks.
When M2000 services are running, this service cannot be stopped.
z
BackupService
6-1
Administrator Guide
Chapter 6
BackupService backs up important configuration files, databases and managed object

(MO) instance data of the system periodically.
When there is no backup task, this service can be stopped.
z
LicenseService
LicenseService provides a service interface for checking the validity of license file of
the current version.
z
LogService
LogService records system log. It receives the system logs from other processes
through a socket, and then manages and stores the system logs.
6.2.4 em_agent
The process em_agent provides the service EventService.
EventService provides a message transmission mechanism between imap services
and between imap and iview. It also provides the function of message broadcast and
filter.
6.2.5 monitor_agent
The process monitor _agent provides the following services:
z
MonitorService
MonitorService monitors the system running status, including CPU and memory
occupancy, free disk space and database system running status.
Dependent service: EventService.
z
FlowController
FlowController accepts the operation requests from other modules. These requests are
mainly those requiring large amount of resources. It decides whether to block a request
according to the current CPU and memory utilization.
Dependent service: EventService and MonitorService.
6-2
Administrator Guide
Chapter 6
6.2.6 partition_agent
The process partition_agent provides the service PartitionService.
PartitionService divides the management objects into partitions. Different partitions are
managed by different processes. These processes can be deployed in different servers.
In this way, even when the number of management objects is large, the load can be
balanced.
6.2.7 audit_agent
The process audit-agent provides the service AuditService.
AuditService records the operation information in database, supports operation
information query and log statistics information query on the Client, and provides
periodic or manual displacing.
Dependent service: ScheduleService.
6.2.8 mo_agent
The process mo_agent provides the following services:
z
LockService
LockService provides lock management when other services are creating, deleting,
querying and modifying management objects to ensure the consistency and
completeness of the operations from multiple services to the same management
objects.
z
RelationService
RelationService creates, queries and deletes the relations between management

objects and saves these relations into database.
z
MOService
MOService loads and verifies the types of all managed objects in M2000 system, loads
managed object dynamic base, creates managed object cases and solidifies the
managed object.
6-3
Administrator Guide
Chapter 6
Dependent service: LockService, RelationService, EventService and PartitionService.
6.2.9 sm_agent
The process sm_agent provides the service SecurityService.
SecurityService controls the access to the sensitive resources in the Element
Management System (EMS), so that only those authorized users can access to these
resources. It realizes the access control by restricting the users' authority to use various
interfaces.
Dependent service: EventService, MonitorService, AuditService and MOService.
6.2.10 med_agent
The process med_agent provides the service MediationService.
MediationService creates, deletes and retrieves various NE engines mapped to
network equipment in M2000 system and manages the relevant event intercepter. The
NE engines realize the communication between M2000 system and various network
equipments.
Dependent service: MOService.
6.2.11 ts_agent
The process ts_agent provides the service TopoService.
TopoService maintains the relations between the objects in the subnet, creates and
deletes the subnet, node, sub-node and link.
Dependent service: SecurityService.
6.2.12 ifms_agent
The process ifms_agent provides the service FaultService.
FaultService collects, analyzes, handles, stores and displays the faults reported by
equipment.
This service can be stopped when the fault management function is not in use.
Dependent service: EventService, MOService, SecurityService and TopoService.
6.2.13 manager_agent
The process manager_agent provides the service SystemService.
6-4
Administrator Guide
Chapter 6
SystemService provides the function of querying M2000 version information, including

operating system version, Client software version, Server software version query and
the corresponding Client software version, and Client upgrade information.
6.2.14 pm_agent
The process pm_agent provides the service PMService.
PMService realizes the performance services of all NEs. It is entirely independent of
individual NE, MO and the interaction with Hosts.
Dependent service: EventService, MOService, SecurityService and AuditService.
6.2.15 cmserver_agent
The process cmserver_agent provides the service CMServer.
CMServer realizes the configuration service of all NEs, and is entirely independent of
individual NE, MO and the interaction with Hosts.
Dependent service: ventService, MOService, SecurityService, TopoService and
AuditService.
6.2.16 swm_agent
The process swm_agent provides the service SWMService.
SWMService manages the versions, configuration data and other files of all NEs. It
provides download, upload, activation and rollback functions.
When M2000 services are running, this service cannot be stopped. Dependent service:
EventService, MOService, SecurityService and AuditService.
This service can be stopped when the software management function is not needed.
Dependent service: EventService, MOService, SecurityService and AuditService.
6.2.17 fmnotify_agent
The process fmnotify_agent provides the service FMNotify.
FMNotify forwards the fault information from FaultManager to Network Management
System (NMS).
This service can be stopped when realtime alarm forwarding is not needed.
Dependent service: EventService and FaultService.
6-5
Administrator Guide
Chapter 6
6.2.18 proxy_agent
The process proxy_agent provides the service ProxyServer.
ProxyServer enables M2000 Client to access NEs through a proxy server to run the
LMT programs of these NEs.
This service can be stopped when proxy of BTS maintenance is not needed.
Dependent service: EventService.
6.2.19 notify_agent
The process notify_agent provides the service RemoteNotifyService.
RemoteNotifyService realizes the remote notification of alarms.
This service can be stopped when remote alarm notification is not needed.
Dependent service: EventService, MOService, SecurityService, TopoService and
FaultService.
6.3 Querying Number of M2000 Processes

The operation of querying number of M2000 processes uses few system resources and
will not affect the system.

To query the number of M2000 processes, perform the following operations on the
Server:
1)
Log in as omcuser.
2)
bash-2.03$ svc_ps | wc l
18
6.4 Querying Service Status

The operation of querying service status uses few system resources and will not affect
the system.

You can query on Client according to 5.2 Querying Server Status through Client, or
query on M2000 Server by performing the following operations:
6-6
Administrator Guide
1)
Log in as omcuser.
2)
Chapter 6
bash-2.03$ svc_adm cmd status

Number of hosts: 1
Host: DEFAULTSYSAGENT
SystemConfigurator: running
Service Agent: sac_agent [4 service(s)] pid: 427

ScheduleManager
[running
SysBackupMgr
[running
LicenseMgr
[running
LogServer
[running
Service Agent: em_agent [1 service(s)] pid: 429

EventManager
[running
Service Agent: monitor_agent [1 service(s)] pid: 431

SystemMonitor
[running
Service Agent: partition_agent [1 service(s)] pid: 445

PartitionManager
[running
Service Agent: audit_agent [1 service(s)] pid: 451

AuditServer
[running
Service Agent: mo_agent [3 service(s)] pid: 457

LockManager
[running
RelationManager
[running
MOManager
[running
Service Agent: sm_agent [1 service(s)] pid: 595

SecurityController
[running
Service Agent: med_agent [1 service(s)] pid: 623

MediationController
[running
Service Agent: ts_agent [1 service(s)] pid: 613

TSService
[running
Service Agent: ifms_agent [1 service(s)] pid: 904

FaultManager
[running
6-7
Administrator Guide
Chapter 6
Service Agent: manager_agent [1 service(s)] pid: 439

SystemManager
[running
Service Agent: pm_agent [1 service(s)] pid: 990

PMService
[running
Service Agent: cmserver_agent [1 service(s)] pid: 1036

CMServer
[running
Service Agent: swm_agent [1 service(s)] pid: 1106

SWMService
[running
Service Agent: fmnotify_agent [1 service(s)] pid: 1076

FMNotify
[running
Service Agent: proxy_agent [1 service(s)] pid: 1137

ProxyServer
[running
Service Agent: notify_agent [1 service(s)] pid: 934

NotifyManager
[running
6.5 Starting M2000 Services

The execution of this command starts all M2000 services. Those already started will not
be affected.

To start M2000 services, perform the following operations on the Server:
1)
Log in as root.
2)
# start_svc
Note:
Before starting M2000 Server, make sure that Sybase service has been started normally. For information
about starting Sybase service, refer to "17.10 Starting Sybase".
6-8
Administrator Guide
Chapter 6
6.6 Stopping M2000 Services

After executing the command, all M2000 services will be stopped. When the M2000
services are stopped, the performance data and alarm data of the NEs may be lost.

To stop M2000 services, perform the following operations on the Server:
1)
Log in as root.
2)
# stop_svc
If there is any service still running, execute the following command to stop it:
# kill_svc
6-9
Administrator Guide
Chapter 7 Database Management

7.1 Overview of Database Management
This chapter introduces the concepts related to M2000 database, including types and
contents of the databases, and provides the details of major database management
tasks, including:
z
Querying database status
Manually displacing alarm data
Manually displacing user log
Setting auto displacing for alarm data
Setting auto displacing for user log
Deleting performance task
Clearing database
7.2 Introduction to Database

7.2.1 Overview of Database
On the basis of Sybase database, M2000 has four databases:
z
omcdb
fmdb
pmdb
sysmdb
After the installation of M2000 Server applications, the sizes of the databases are
decided, and do not need manual modification.
You can use Sybase commands to manage the databases.
7.2.2 omcdb
The database omcdb is used to store the M2000 configuration data, security data and
the data related to internal realization. It needs at least 1000MB of free space.
The tables in omcdb and their contents are shown in Table 7-1.
Table 7-1 Database table name and contents of omcdb
Name
Content
SMLoginRec
User login information.
SMNEUser
NE user information.
SMSecurityPolic
Security strategy.
7-1
Administrator Guide
Name
Content
SMTerminal
Terminal information.
SMUser
User information.
SMUserGroup
User group information.
tbl_AccessTable
Save and read authority.
tbl_AuditTable
Operation log information.
Other tables
Information of configuration, security and other internal realization.
7.2.3 fmdb
The database fmdb is used to store the alarm data of the NEs and M2000. It needs at
least 3700MB of free space.
The tables in fmdb and their contents are as are shown in Table 7-2.
Table 7-2 Database table name and contents of fmdb
Name
Content
tbl_cur_alm
Current alarms.
tbl_event
Event alarms.
tbl_his_alm
History alarms.
tbl_mask_alm
Screened alarms.
Other tables
Information about internal realization of alarm handling.
7.2.4 pmdb
I. Overview of pmdb
The database pmdb is used to store the performance measurement data of NEs. It
needs at least 13000MB of free space.
The table types in pmdb are as follows:
z
Counter information tables
Task information tables
Task result tables
II. Counter information tables

The counter information tables store a group of relatively fixed information. The tables
and their contents are shown in Table 7-3.
7-2
Administrator Guide
Table 7-3 Database table name and contents of pmdb (counter information tables)
Name
Content
systbl_NeType
All NE types that can be managed by M2000.
systbl_FuncSet
Function sets of all NEs.
systbl_FuncSubSet
Measurement units of all function sets.
systbl_Counters
Measurement items of all measurement units.
systbl_Counter_Unit
Units of various measurement items.
III. Task information tables

The task information tables store the information related to task registration. The tables
and their contents are shown in Table 7-4.
Table 7-4 Database table name and contents of pmdb (task information tables)
Name
Content
tbl_JobGeneralInfo
Basic task information. Each record stands for a task.
tbl_JobObject
Object information corresponding to tasks.
tbl_JobCounter
Measurement item information corresponding to tasks.
IV. Task result tables

The task result tables store the information related to task result. The tables and their
contents are shown in Table 7-5.
Table 7-5 Database table name and contents of pmdb (task result tables)
Name
Content
tbl_jobrst_*
Task result. Each task corresponds to a task result table.
tbl_LostResultInfo
Task loss information. If the task result of a NE cannot be received

within a certain period of time, a record will be added to this table.
tbl_JobSuspendInfo
Information of suspended task.
7.2.5 sysmdb
The database sysmdb is used to store the file information and NE version configuration
data managed by the software management module. It needs at least 3000MB of free
space.
The tables in sysmdb and their contents are shown in Table 7-6.
7-3
Administrator Guide
Table 7-6 Database table name and contents of sysmdb

Name
Content
tbl_FTPFileSet
File information managed by software management module.
tbl_VersionRelation
Information of version file matching.
log
Information of internal realization.
sys_log_del
Auto-clearing conditions of logs.
tbl_UnsendMMLCmd
Commands to be sent to the disconnected NEs once the connection

recovers.
tbl_NELogTable
NE operation logs
7.3 Querying Database Status

The operation of querying database status uses few system resources and will not
affect the system.

You can query on Client according to 5.2 Querying Server Status through Client, or
query on M2000 Server by performing the following operations:
1)
Log in as omcuser.
2)
Execute the following command to view all databases:
bash-2.03$ isql SSYB Usa P <user sa password>

1> sp_helpdb
2> go
3)
Execute the following command to view the data space and transaction log space
in each database:
1> sp_helpdb fmdb

2> go
1> sp_helpdb pmdb
2> go
1> sp_helpdb omcdb
2> go
1> sp_helpdb sysmdb
2> go
1> exit
7-4
Administrator Guide
7.4 Manually Displacing Alarm Data

After displacing, the alarm data in fmdb will be saved as files to the default displacing
path in the Server. User can decide whether to delete the original data from the
database.

To manually dump the alarm data, perform the following operations:
1)
2)
In the main interface M2000 Client, select the menu [Fault/Alarm Displace] to open
the window [Alarm Displace], as shown in Figure 7-1.
Figure 7-1 Alarm displace

3)
Select the tab "Manual Displace".
4)
Specify the parameters such as the alarm types to be dumped, and then click
<Start>.
7.5 Manually Displacing User Log

After displacing operation, the log data in omcdb will be saved as files to the default
displacing path in the Server and the dumped logs will be deleted from the database.
7-5
Administrator Guide

To manually dump the logs, perform the following operations:
1)
2)
In the main interface of M2000 Client, select the menu [System/Log/User Log
Settings] to open the window [User Log Set], as shown in Figure 7-2.
Figure 7-2 Log displace

3)
Select the tab "Manual Displace".
4)
Specify whether to dump by time or by quantity of log information, and then click
<Displace>.
7.6 Setting Auto Displacing for Alarm Data

After auto displacing, the alarm data in fmdb will be saved as files to the default path in
the Server, and the dumped data will be deleted from the database.

To set auto displacing for alarm data, perform the following operations:
1)
2)
In the main interface of M2000 Client, select the menu [Fault/Alarm Displace] to
open the window [Alarm Displace], as shown in Figure 7-1.
3)
Select the tab "Auto Displace".

7-6
Administrator Guide
4)
Specify the parameters such as the type of alarm to be dumped, and then click
<Set>.
7.7 Setting Auto Displacing for User Log

After auto displacing, the user log data in omcdb will be saved as files to the default
path in the Server, and the dumped data will be deleted from the database.

To set auto displacing for user log data, perform the following operations:
1)
2)
In the main interface of M2000 Client, select the menu [System/Log/Settings] to

open the window [Log Setting], as shown in Figure 7-2.
3)
Select the tab "Overflow Displace". Specify the displacing condition, and then click
<Set> to realize auto displacing on overflow.
4)
Select the tab "Periodic Displace". Specify the displacing condition, and then click
<Set> to realize periodic auto displacing.
7.8 Deleting Performance Task

The performance task data cannot be dumped directly, but the performance task results
can be saved as files and then the tasks can be deleted to clear pmdb.
After deleting a performance task, all information related to this task will be deleted from
the database.

To delete a performance task, perform the following operations:
1)
2)
In the main interface of M2000 Client, select the menu [Performance/Show Job
List] to open the window [Performance Job List].
3)
Right-click the task to be deleted, and then select the menu [Job/Delete] in the
shortcut menu.
4)
Confirm the deletion.
7-7
Administrator Guide
7.9 Clearing Database

Clearing the data space of database has no effect on the running of the system.
Clearing the transaction log space of database will affect the system backup function. It
causes incomplete backup.

Perform the following operations to clear the data space and transaction log space in
database according to the query result of database space (refer to "7.3 Querying
Database Status"):
1)
Dump the alarm data, and clear data space in fmdb. Refer to "7.4 Manually
Displacing Alarm Data" and "7.6 Setting Auto Displacing for Alarm Data".
2)
Dump the user log data, and clear data space in omcdb. Refer to "7.5 Manually
Displacing User Log" and "7.7 Setting Auto Displacing for User Log"
3)
Delete the performance task to clear data space in pmdb. Refer to "7.8 Deleting
Performance".
4)
Execute the following commands to clear the transaction data log space:
Caution:
Clearing transaction log will affect the backup function of the system.
bash-2.03$ isql SSYB Usa P<user sa password>

1> dump tran fmdb with no_log
2> go
1> dump tran omcdb with no_log
2> go
1> dump tran pmdb with no_log
2> go
1> dump tran sysmdb with no_log
2> go
1> exit
7-8
Administrator Guide
Chapter 8 Disk Space Management

8.1 Overview of Disk Space Management
This chapter introduces the concepts related to M2000 file system, and provides the
details of disk space management tasks, including:
z
Querying disk space
Clearing disk space
8.2 Introduction to File System

8.2.1 Overview of System Structure
The system structure of M2000 is server/client mode.
z
The Server realizes the communication with the NEs, stores the operation and
maintenance data of NEs and provides NMS-oriented interface.
The Client provides graphic user interface to realize the operation and
maintenance to NEs and the status monitor to M2000.
8.2.2 Server File System

The M2000 Server software runs on Solaris. It is constructed on the basis of the
following software:
z
Sybase database
CORBA functional software
FTP functional software
The installation package of M2000 Server software includes the software provides the
FTP function and CORBA (Common Object Request Broker Architecture) function.
Table 8-1 lists the directory structure of M2000 Server software.
Table 8-1 Directory structure of M2000 Server software
Directory
Description
$M2K_ROOT
Installation directory of M2000. Default: /opt/OMC
$M2K_ROOT/bin
Directory storing executable files.
$M2K_ROOT/etc
Directory storing system configuration files and SQL

scripts.
$M2K_ROOT/idl_northbound
Directory storing northbound IDL interface files.
$M2K_ROOT/lib
Directory storing library files.
8-1
Administrator Guide
Directory
Description
$M2K_ROOT/lbin
Directory storing system management commands.
$M2K_ROOT/model
Directory storing managed object XML model files.
$M2K_ROOT/3rdTools
Directory storing third-party software.
/export/home/omc/var
Directory storing M2000 running data.
/export/home/omc/var/logs
Directory storing system logs.
/export/home/backup
Directory storing backup files.
8.2.3 Client File System

The Client software runs on Windows. It is constructed on the basis of JAVA virtual
machine. The installation package of M2000 Client software includes JAVA virtual
machine for Windows.
Table 8-2 lists the directory structure of M2000 Client software.
Table 8-2 Directory structure of M2000 Client software
Directory
Description
<M2000 install directory>
Installation directory of M2000. Default: C:\

iManagerM2000Client
<M2000 install directory>\bin
Directory storing executable files
<M2000 install directory>\Data
Directory storing NE configuration files
<M2000 install directory>\dtd
Directory storing "dtd" files used to analyze "xml" files
<M2000 install directory>\help
Directory storing online help
<M2000 install directory>\jre
Directory storing java runtime
<M2000 install directory>\lib
Directory storing operation base files
<M2000 install directory>\openorb
Directory storing openorb third-party base
<M2000 install directory>\style
Directory storing configuration files
<M2000 install directory>\tracefile
Directory storing trace files
<M2000 install directory>\UninstallerData
Directory storing uninstall executable files
<M2000 install directory>\update
Directory storing upgrade base files
8.3 Query Disk Space

Querying disk space uses few system resources, and will not affect the system.
8-2
Administrator Guide

You can query on M2000 Client according to 5.2 Querying Server Status through Client,
or query on M2000 Server by performing the following operations:
1)
Log in as omcuser.
2)
bash-2.03$ df k
3)
Check the usage of disk space. Normally the usage of disk space must be lower
than 80%. That is, the output value of capacity must be lower than 80.
8.4 Clearing Disk Space

Do not delete any file of the operating system. If any file of the operating system is
deleted, the system cannot operate.

To clear the disk space, perform the following operations on the Server:
1)
Log in as root.
2)
Execute the following command to search for the core files:
bash-2.03$ find / -name core* ls

3)
Delete the useless core files.
4)
Delete all files in "/var/tmp" under that directory.
5)
Delete other useless files.
8-3
Administrator Guide
Chapter 9 Dual-Plane Configuration

9.1 Overview of Dual-Plane Configuration
This chapter introduces the concepts related to dual-plane, and provides the details of
dual-plane configuration tasks, including:
z
Planning IP data
Manually setting dual-plane
Automatically setting dual-plane
Verifying dual-plane settings
9.2 Introduction to Dual-Plane

Dual-plane means that Solaris OS dynamically monitors dual network adapters of a
single computer, and automatically switch the IP address of the faulty network adapter
to the normal one. In this way, continuous communications are insured. In addition,
Solaris OS goes on monitoring the faulty network card, and restores the original IP
address and mask if it becomes valid again.
As shown in Figure 9-1, the Server has two Ethernet adapters: hme0 and hme1.These
two adapters are connected with the management network. Each adapter has an IP.
They belong to the same IP group.
Server
Client
hme0
hme1
Management
Network
Figure 9-1 Dual-plane networking
Caution
The names of the Ethernet adapters are not necessarily hme0 and hme1.
9-1
Administrator Guide
9.3 Configuration Procedure of Dual-Plane

The configuration procedure of dual-plane is as follows:
1)
Planning IP data
2)
Manually or automatically setting the dual-plane
3)
Verifying the settings of dual-plane
9.4 Planning IP Data

The following information needs to be planned:
z
IPs and subnet masks of the two Ethernet adapters
Two test IPs and their subnet masks
IP group name
For example, for Figure 9-1 the planning information is:

z
hme0: IP: 10.10.105.22, subnet mask: 255.255.255.0. The test IP of this adapter:
10.10.105.66, subnet mask: 255.255.255.0
hme1: IP: 10.10.105.23, subnet mask: 255.255.255.0. The test IP of this adapter:
10.10.105.68, subnet mask: 255.255.255.0
IP group name: imap
9.5 Manually Setting Dual-Plane

Manual setting is carried out through commands. The results are stored in the memory.
If the Server is restarted, all setting information will be lost. Therefore, manual setting is
normally used to test the correctness of dual-plane configuration. In practice, automatic
setting is recommended.
In this mode, the Server provides two external IPs. You can select either one for the
application.

To manually set the two adapters, perform the following operations:
1)
Execute the following commands to set the adapters:
# ifconfig hme0 unplumb

# ifconfig hme1 unplumb
# ifconfig hme0 plumb
# ifconfig hme1 plumb
2)
Execute the following commands to add the adapters to the group:
# ifconfig hme0 group imap

9-2
Administrator Guide
# ifocnfig hme1 group imap

3)
Execute the following commands to set the IP of the adapters, disable their
failover and add deprecated flag.
# ifconfig hme0 10.10.105.22 netmask 255.255.255.0 up

# ifconfig hme1 10.10.105.23 netmask 255.255.255.0 up
# ifconfig hme0 addif 10.10.105.66 netmask 255.255.255.0 -failover deprecated up
# ifconfig hme1 addif 10.10.105.68 netmask 255.255.255.0 -failover deprecated up
Dual-plane is complete.
9.6 Automatically Setting Dual-Plane

Automatic setting is realized by writing the commands into the operating system files.
When the operating system is started, the settings of dual-plane will take effect
automatically.
This mode provides an external IP only, which is different from the manual mode. In the
following example, the external IP is 10.10.105.22.

To carry out the automatic settings of the two Ethernet adapters, perform the following
operations:
1)
Open the file "/etc/hosts", and add the following contents:
10.10.105.22 imap-e4500
Note:
imap-e4500 is the host name.
2)
Open the configuration file of the first Ethernet adapter "/etc/hostname.hme0", and
add the following contents:
imap-e4500 group imap up

addif 10.10.105.66 netmask 255.255.255.0 -failover deprecated up
Caution:
In the files "/etc/hostname.hme0" and "/etc/hostname.hme1", there must be no space before each line.
3)
Open the configuration file of the second Ethernet adapter "/etc/hostname.hme1",

and add the following contents:
9-3
Administrator Guide
10.10.105.68 netmask 255.255.255.0 group imap -failover deprecated up

4)
Execute the following command to restart the system:
# init 6
After restarting the system, the dual-plane settings take effect.
9.7 Verifying Dual-Plane Settings

The verification of dual-plane settings uses little system resource and will not affect the
system.

Execute the following commands to verify the dual-plane settings:
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0:flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 10.10.105.22 netmask ffffff00 broadcast 10.255.255.255
groupname imap
ether 8:0:20:8b:0:8d
hme0:1:flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAIL
OVER> mtu 1500 index 4
ether 8:0:20:8b:0:8d
hme1:flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
groupname imap
ether 8:0:20:8b:0:8d
hme1:1:flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAIL
OVER> mtu 1500 index 5
ether 8:0:20:8b:0:8d
The above information shows that the IPs of the two adapters are set as 10.10.105.22
and 10.10.105.23 respectively, and have been added to the group imap, and their test
IPs are also correct.
9.7.3 Abnormal Handling

If the settings is not successful, perform the following operations:
9-4
Administrator Guide
1)
Check the file "/etc/hostname.hme*". There must be no space before the script in
this file.
2)
In the system startup information, check the parameter "local-mac-address" in

Server openboot ROM. Its value must be true.
3)
Set the dual-plane again.
9-5
Administrator Guide
Chapter 10 NTP Service Configuration

10.1 Overview of NTP Service Configuration
This chapter introduces the concepts related to Network Time Protocol (NTP) service,
and provides the details of NTP service configuration tasks, including:
z
Setting M2000 as top NTP Server
Setting M2000 as middle NTP Server
Setting M2000 as NTP Client
Starting NTP service
Checking NTP service running status
Stopping NTP service
10.2 Introduction to NTP Service

NTP defines time synchronization mechanism. It synchronized the time between
distributed time Server and Client. The theoretical precision reaches nanoseconds.
The M2000 Server uses Solaris system to support NTP. You can set M2000 as the NTP
Server or Client by setting the Solaris parameters.
Level 0
NTP server
Level 1
Level 1
Level 1
NTP server
NTP server
NTP server
Level 2
Level 2
NTP server
NTP server
NTP client
NTP client
Figure 10-1 NTP synchronization networking

As shown in Figure 10-1, there are three types of computers:
z
Top NTP Server: Refer to level 0 NTP Server. It provides time synchronization
service for next level.
10-1
Administrator Guide
z
Middle NTP Server: Refer to level 1 Server and Level 2 Server. It retrieves time
from higher level and provides time service for lower level.
NTP Client: It only retrieves time, and does not provide time service.
10.3 Setting M2000 as Top NTP Server

Perform the following operations to set M2000 as the top NTP Server:
1)
Log in to M2000 Server as root.
2)
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
# vi /etc/inet/ntp.conf
3)
Set the values of all "XType"s in the file to "1".
4)
Save the file "/etc/inet/ntp.conf" and quit vi.
10.4 Setting M2000 as Middle NTP Server

Perform the following operations to set M2000 as the middle NTP Server:
1)
2)
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
3)
Add a line "server XXX.XXX.XXX.XXX" before " server 127.127.1.0 prefer" to

specify the IP of the higher level NTP Server.
4)
Delete "stratum 0" from " fudge 127.127.Xtype.0 stratum 0".
5)
Set the values of all "XType"s in the file to "1".
6)
10.5 Setting M2000 as NTP Client

Perform the following operations to set M2000 as the NTP Client:
1)
2)
# cp /etc/inet/ntp.client /etc/inet/ntp.conf
3)
Add a line "server XXX.XXX.XXX.XXX" to the file to specify the IP of the higher
level NTP Server.
4)
10.6 Starting NTP Service

Perform the following operations to start NTP service:
10-2
Administrator Guide
1)
2)
Check whether the time zone, data and time of the Server are correct. If they are
incorrect, it is necessary to modify them manually. Refer to "2.2 Modifying Server
Time".
3)
If the NTP service is already running, it is necessary to stop it first:
# /etc/init.d/xntpd stop
Note:
The startup script of NTP is in "/etc/rc2.d/". The NTP service will be automatically started after Solaris is
started. Therefore, there is no need to add the auto startup script manually.
4)
Start NTP service in the NTP Server. If M2000 is set as top or middle NTP Server,
execute the following command:
# /etc/init.d/xntpd start
5)
Start NTP service in the NTP Client. If M2000 is set as NTP Client, execute the
following command:
# ntpdate <NTP Server IP>

# /etc/init.d/xntpd start
10.7 Checking Running Status of NTP Service

Execute the following command to check the running status of NTP:
# ntpq p
remote
refid
st t when poll reach
delay
offset
jitter
==========================================================================
====
*LOCAL(0)
224.0.1.1
.LCL.
0.0.0.0
0 l
10
64
377
0.000
0.000
0.000
16 -
64
0.000
0.000 4000.00
In the returned information, if there is as "*" before "LOCAL(0)", it means that the status
of this clock reference source is normal. "LOCAL(0)" means that the local clock is used
as the reference clock source.
10.8 Stopping NTP Service

Perform the following operations to stop the NTP service:
1)
2)
# /etc/init.d/xntpd stop
10-3
Administrator Guide
Chapter 11 Backup and Restoration

11.1 Overview of Backup and Restoration
This chapter introduces the concepts related to backup and restoration, and provides
the details of backup and restoration tasks, including:
z
Modifying configuration file
Automatically backing up M2000 system
Manually backing up M2000 system
Restoring M2000 system
Backing up operating system
Restoring operating system
11.2 Introduction to Backup and Restoration

11.2.1 M2000 System Backup Contents
M2000 system backup means to back up the following contents:
z
The four databases of M2000: omcdb, fmdb, pmdb, sysmdb
The
system
file
of
M2000:
the
files
in
"/export/home/omc/var"
and
"/export/home/sysm"
After the execution of backup, the above files are packed into a file package.
After the execution of restoration, all the content in the file package will be restored. As
for the data that hasnt been packed in the file package because of being processed
after backup is executed, M2000 can get it from NE by using auto synchronization
function, and process it over again.
11.2.2 M2000 System Backup and NE Data Backup

M2000 provides system backup and NE data backup function.
z
NE data backup: With NE data backup function, the data on NEs, including NE
configuration data and LICENSE, can be backed up to M2000 Server hard disks.
For detailed information of NE data backup, refer to iManager M2000 Mobile
M2000 System Backup: With M2000 system backup function, the information on
M2000 Server hard disks can be backed up to types.
11-1
Administrator Guide
11.2.3 The Mode of M2000 System Backup and Restore

I. The Mode of M2000 System Backup
z
M2000 system backup mode can be classified as auto backup and manual backup.
Auto backup is also referred as periodic backup.
M2000 system backup mode can also be classified as incremental backup and full
backup.
II. The Mode of M2000 System Restore

All the content of incremental backup and full backup can be restored manually.
11.2.4 Name of Backup Files

After the execution of backup, the latest backup information will be recorded in
"/export/home/backup/omc/backup.log". The information includes the generation date,
path and name of the backup files. For example:
20040601042002 /export/home/backup/omc/all-20040601042002.tar.gz 0
20040602042001 /export/home/backup/omc/inc-20040602042001.tar.gz 1
In the above information, the first line indicates that the full backup file was generated
on 2004-6-1 04:20:02. The second line means that the incremental backup file was
generated on 2004-6-2 04:20:02. The third line indicates that the incremental backup
file was generated on 2004-6-3 04:20:02.
The system sets the path and name of backup files automatically, and user can not set
them manually.
11.2.5 Storage Media of Backup File

The backup files will be saved to disks or magnetic tapes or both according to the
settings in the configuration file.
z
When the storage media is disk, system will save the backup files to
"/export/home/backup/omc".
During the backup of the second week, the backup of the first week will be deleted
automatically.
z
When the storage media is magnetic tape, system will wind the tape to the
beginning, and then back up the files together with the path to the magnetic tape.
It is recommended to use a tape for each day. Prepare a tape before backup, and never
replace the tape when the backup is underway.
11-2
Administrator Guide
11.3 Function Setting

11.3.1 Introduction to Configuration File
Before backup or restoration, check whether the configuration related to backup or
restoration in the configuration file "omcsvc.xml" meets the requirement. "omcsvc.xml"
is in "/<M2000 installation directory>/opt/OMC/etc/conf/". It includes:
z
Tape drive path. Default: /dev/rmt/0
Storage media. Default: all (backup to both disk and tape).
1)
If the above settings do not meet the requirement, refer to "11.3.2 Setting Tape
Drive Path" and "11.3.2 6)Switch to root
bash-2.03$ su root
2)
Execute the following command to restart M2000 services:
# stop_svc
# start_svc
Setting Backup MediaSetting Backup Media " to modify the file "omcsvc.xml".
11.3.2 Setting Tape Drive Path

Perform the following operations to modify the path of tape drive:
1)
Log in as omcuser.
2)
Open the file "omcsvc.xml".
3)
Find the following contents:
<path name="backuppath">
<param name="tapePath">/dev/rmt/0</param>
</path>
4)
Replace "/dev/rmt/0" with the path of the tape drive.
5)
Save the file and quit.
6)
Switch to root
bash-2.03$ su root
7)
# stop_svc
# start_svc
11.3.3 Setting Backup Media

Perform the following operations to modify the path of tape drive:
1)
Log in as omcuser.
2)
Open the file "omcsvc.xml".
3)
Find the following contents:

11-3
Administrator Guide
<module name="all">
..
<param name="backupMedia">all</param>
....
</module>
...
<module name="inc">
<param name="backupMedia">all</param>
</module>
Note:
"<module name="all">" and "<module name="inc">" respectively stands full backup and incremental
backup.
"<param name="backupMedia">all</param>" means that the backup is stored in both disk and magnetic
tape. If the "all" in "<param name="backupMedia">all</param>" is "tape" or "disk", then it means that the
backup will be saved in disk or tape only.
4)
Change the "all" in "<param name="backupMedia">all</param>" to "tape" or

"disk" according to the requirement.
5)
Save the file and quit the edit status.
6)
Switch to root
bash-2.03$ su root
7)
# stop_svc
# start_svc
11.4 Automatically Backing Up M2000 System

11.4.1 Introduction to Auto Backup
Auto backup, also called periodic backup, means that the system carries out backup at
a fixed moment every day. In a week, the system carries out full backup on one day,
and carries out incremental backup on other six days. The execution time and the full
backup day can be set on M2000 Client.
11-4
Administrator Guide
11.4.2 Setting Auto Backup Time

Perform the following operations on M2000 Client:
1)
2)
In the main window, select the menu [Tools/System Backup/Periodic Backup].
3)
In the dialog box [Periodic Backup], select the tab "Server", and then select
"Enable Server Periodic Backup" and set the execution time and full backup day,
as shown in Figure 11-1.
4)
Click <OK> to save the settings. From then on, the system will carry out auto
backup.
Figure 11-1 Periodic backup
11.5 Manually Backing Up M2000 System

11.5.1 Introduction to Manual Backup
Manual backup is carried in special or emergent circumstances, such as backup tape
lost and system failure. The backup type can be full backup or incremental backup.
11.5.2 Carrying Out Manual Backup on Client

1)
2)
In the main window, select the menu [Tools/System Backup/Manual Backup].
3)
In the dialog box [Manual Backup], select the tab "Server", and then select the
backup type, as shown in Figure 11-2.
11-5
Administrator Guide
4)
Click <Start> to start backing up M2000 system.
Figure 11-2 Manual backup
11.5.3 Carrying Out Manual Backup on Server

Perform the following operations on the M2000 Server:
1)
Log in as root.
2)
Execute the following command to carry out full backup:
# svc_backuprestore -cmd backup -m all -v

3)
Or execute the following command to carry out incremental backup:
# svc_backuprestore -cmd backup -m inc -v
11.6 Restoring M2000 System

11.6.1 Function Introduction
Restore the M2000 system from the latest M2000 full backup and incremental backup
file.

Perform the following operations on M2000 Server:
1)
Log in as root.
2)
If the M2000 services are running, execute the following command to stop the
M2000 services:
# stop_svc
11-6
Administrator Guide
3)
Execute the following command to view the backup log "backup.log":
# cd /export/home/backup/omc
# more backup.log
20040601042002 /export/home/backup/omc/all-20040601042002.tar.gz 0
4)
Make sure that the file recorded in backup.log is saved in the disk. If it is saved in
the tape, it is necessary to copy the file from the tape to the disk in this way: Enter
the root directory, insert the tapes from the first day to the last day one by one, and
execute tar command to copy the file from the tape to the disk.
# cd /
# tar xf /dev/rmt/0
5)
Execute the restoration command:
# svc_backuprestore -cmd restore

******************************************************
*
Restore is a dangerous operation !
If you have to do it, please stop system first !
******************************************************
Continue ?[n/y]
6)
Press <Y> to start restoring M2000 system.
7)
Execute the following command to start the M2000 services:
# start_svc
11.7 Backing Up Operating System

Use the Solaris commands to back up the disk information (including Solaris, Sybase
and M2000 software and parameters) to the tape.

The following description is based on Sun Fire V880. The operations on other server
type are similar to this. The specific commands depend on the server type.
1)
Log in as root.
2)
Create a temporary directory:
# mkdir /data/backuprestore
# cd /data/backuprestore
3)
Back up VTOC:
11-7
Administrator Guide
# prtvtoc /dev/rdsk/c0t0d0s2 > ./c0t0d0.vtoc

# vxdisk list > vxdisk_list.out
# vxdg list
NAME
STATE
ID
rootdg
enabled
1074053501.1025.f4800
m2000dg
enabled
1074054023.1091.f4800
# vxprint -g rootdg -vpshm > rootdg.private

# vxprint -g m2000dg -vpshm > m2000dg.private
4)
Back up vfstab:
# cp /etc/vfstab ./
5)
Rewind the tape:
# mt rewind
6)
Back up the partition information:
# cd /data
# ufsdump 0ucf /dev/rmt/0n backuprestore
7)
Retrieve the partition information:
# df k
Filesystem
/dev/vx/dsk/rootvol
kbytes
used
avail capacity
7059201 3887574 3101035
56%
Mounted on
/
/proc
0%
/proc
fd
0%
/dev/fd
mnttab
0%
/etc/mnttab
swap
7367984
16 7367968
1%
/var/run
swap
7368296
328 7367968
1%
/tmp
/dev/vx/dsk/m2000dg/data
24772232 19746352 4778158
/dev/vx/dsk/opt
5646574 3041380 2548729
81%
55%
/data
/opt
/dev/vx/dsk/m2000dg/exporthome
467699068 20191726 442830352
8)
5%
/export/home
Back up the partition data according to the above partition information

("/dev/vx/dsk/rootvol" and "/dev/vx/dsk/opt"):
# ufsdump 0ucf /dev/rmt/0n /dev/vx/rdsk/rootvol

# ufsdump 0ucf /dev/rmt/0n /dev/vx/rdsk/opt
11-8
Administrator Guide
11.8 Restoring Operating System

Use the Solaris commands to restore the tape information (including Solaris, Sybase
and M2000 software and parameters) to the disk so that the system can operate
normally.

The following description is based on Sun Fire V880. The operations on other server
type are similar to this. The specific commands depend on the server type.
1)
Restore the tape information.
2)
Set up equipment tree and boot block.
3)
Modify the system file and file system information.
4)
Restart the system.
5)
Use Volume Manager to encapsulate the disk.
11.8.3 Restoring Tape Information

Perform the following operations to restore the information in the tape to the disk:
1)
Start up the system using CD-ROM and enter the single user mode:
ok> boot cdrom s

# TERM=vt100; export TERM
2)
Rewind the tape:
# mt rewind
3)
Restore the directory "backuprestore" in the tape to "/tmp/backuporestore".
# cd /tmp
# ufsrestore rf /dev/rmt/0n
4)
Implement hard disk partition according to the hard disk vtoc backed up in the
tape:
# fmthard s /tmp/backuprestore/c0t0d0.vtoc /dev/rdsk/c0t0d0s2

5)
Set up file system:
# newfs /dev/rdsk/c0t0d0s0
# newfs /dev/rdsk/c0t0d0s5
6)
Restore the root partition:
# mkdir /tmp/root2
# mount /dev/dsk/c0t0d0s0 /tmp/root2
# cd /tmp/root2
11-9
Administrator Guide
Note:
Because the root partition is backed up first, it is restored first.
# rm restoresymtable
# cd /
# umount /tmp/root2
# fsck /dev/dsk/c0t0d0s0
7)
Restore the partition "/opt":
# mkdir /tmp/root3
Note:
The restored one is the "/opt" backed up after the root partition.
# rm restoresymtable
# cd /
# umount /tmp/root3
# fsck /dev/dsk/c0t0d0s5
11.8.4 Setting Up Equipment Tree and Boot Block

Perform the following operations to set up equipment tree and boot block:
1)
Delete the original equipment information:

# mv /tmp/root2/etc/path_to_inst /tmp/root2/etc/ORIGINAL_PATH_TO_INST
# rm /tmp/root2/dev/rdsk/c*
# rm /tmp/root2/dev/dsk/c* ; rm tmp/root2/dev/rmt/*
# cd /tmp/root2/devices ; rm -r *
2)
Import the current equipment information:
# cd /devices; find . print | cpio -pduVm /tmp/root2/devices

# cd /
11-10
Administrator Guide
# devfsadm -r /tmp/root2 -p /tmp/root2/etc/path_to_inst

# umount /tmp/root2
3)
Set up the boot block:
# cd /usr/platform/sun4u/lib/fs/ufs; installboot ./bootblk /dev/rdsk/c0t0d0s0

# touch /tmp/root2/etc/vx/reconfig.d/state.d/install-db
11.8.5 Modifying System File and File System Information

Perform the following operations to modify the system file and file system information:
1)
Set display output:
# TERM=vt100 ;export TERM

2)
Open the file "system":
# vi /tmp/root2/etc/system
3)
Disable the two lines in the file (add "#" before each line)
* rootdev:/pseudo/vxio@0:0
* set vxio:vol_rootdev_is_volume=1
4)
Save the file "system" and quit.
5)
Open the file "vfstab".
# vi /tmp/root/etc/vfstab
#device
device
mount
FS
fsck mount
mount
# to mount
to fsck
point
type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr
fd
/proc -
/dev/fd fd
/proc
no
proc -
no
swap -
ufs 1
/dev/vx/dsk/swapvol
/dev/vx/dsk/rootvol
/dev/vx/rdsk/rootvol /
ufs 1
/dev/vx/rdsk/opt /opt ufs 2
yes -
/dev/vx/dsk/opt
swap -
/tmp tmpfs
no
yes -
no
yes -
#NOTE: volume rootvol (/) encapsulated partition c0t0d0s0

#NOTE: volume swapvol (swap) encapsulated partition c0t0d0s1
#NOTE: volume opt (/opt) encapsulated partition c0t0d0s5
/dev/vx/rdsk/m2000dg/data
/data
yes logging
/dev/vx/dsk/m2000dg/exporthome /dev/vx/rdsk/m2000dg/exporthome
/export/home ufs 2
6)
Delete the last two lines of in "vfstab":
11-11
ufs 2
Administrator Guide
/dev/vx/rdsk/m2000dg/data
/data
ufs 2
yes logging
/dev/vx/dsk/m2000dg/exporthome /dev/vx/rdsk/m2000dg/exporthome
/export/home ufs 2
7)
Modify the following three lines in "vfstab":
/dev/vx/dsk/swapvol
/dev/vx/dsk/rootvol
/dev/vx/rdsk/rootvol /
ufs 1
/dev/vx/rdsk/opt /opt ufs 2
yes -
/dev/vx/dsk/opt
swap -
no
no
As:
/dev/dsk/c0t0d0s1 -
swap -
no
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no /dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /opt ufs 2 yes
Note:
The original "vfstab" is managed by "volume manager". The restored hard disk has no "volum manager",
so the partitions managed by "volume manager" needs to be renamed using the standard partition name.
11.8.6 Restarting System

Execute the following command to restart the system:
# reboot
11.8.7 Encapsulating Disk Using Volume Manager

Execute the following commands to encapsulate the disk using Volume Manager:
1)
Run Volume Manager
# vxinstall
According to the system prompts, enter the following information.
2)
Some licenses are already installed. Do you wish to review them
[y,n,q,?] (default: y) y
3)
Do you want to use enclosure based names for all disks ?
[y,n,q,?] (default: n) n
4)
Volume Manager Installation Options
Menu: VolumeManager/Install
Quick Installation
Custom Installation
11-12
Administrator Guide
Prevent multipathing/Suppress devices from VxVM's view
Display help about menu
??
Display help about the menuing system
Exit from menus
Select an operation to perform: 2

5)
Encapsulate Boot Disk [y,n,q,?] (default: n) y
Enter disk name for [<name>,q,?] (default: rootdisk) rootdisk_1

Hit RETURN to continue.
6)
Installation options for controller OTHER_DISKS
Menu: VolumeManager/Install/Custom/OTHER_DISKS
Install all disks as pre-existing disks. (encapsulate)
Install all disks as new disks. (discards data on disks!)
Install one disk at a time.
Leave these disks alone.
Display help about menu
??
Display help about the menuing system
Exit from menus
Select an operation to perform: 4

7)
Is this correct [y,n,q,?] (default: y) y
8)
Shutdown and reboot now [y,n,q,?] (default: n) n
9)
Restart the system:
# reboot - - -x
11-13
Administrator Guide
Chapter 12 Routine Maintenance

12.1 Overview of Routine Maintenance
This chapter provides the maintenance items and operation guide for M2000, including:
z
Daily maintenance
Weekly maintenance
Monthly maintenance
These items are recommendation. You can customize them according to actual needs.
For operation and maintenance of NE, refer to iManager M2000 Mobile Element
Management System Operation Manual.
12.2 Daily Maintenance

12.2.1 Daily Maintenance Item List
Table 12-1 lists the daily maintenance items. Refer to 12.2.2
Checking Alarm
Information and the later section for operation guide of each maintenance item.
Table 12-1 Daily maintenance checklist
SN
Item
Reference
Check alarm information
There is no alarm information.
Check log information
There is no abnormal and malicious operations

implemented.
Check Solaris error log
There is no err message.
Check database status
Database system operates normally, and the used

space is lower than 80%.
Check hard disk space
The used space of each partition is lower than 80%
Check CPU utilization
CPU utilization is lower than 80%.
Check the number of processes
The number of running processes is 18.
Check service status
All the services are running normally.
12.2.2 Checking Alarm Information

1)
2)
In the main window, select the menu [Tools/System Monitor/Monitor Browser].

12-1
Administrator Guide
3)
Select the tab "NE Monitor".
4)
Check whether any alarm exists.
5)
If any alarm exists, select the menu [Fault/Query/Current Alarm] to view its
detailed information.
12.2.3 Checking Log Information

Refer to "4.4 Browsing System Log" to check whether there is any system operation
error.
Refer to "4.3 Browsing User Log" to check user operation log. If any abnormal or
malicious operation is found, implement the corresponding handling. For example, if a
user failed to log in to the Client for multiple times, check the validity of this user.
12.2.4 Checking Solaris Error Log

Refer to "4.5 Checking Solaris Error Log" to check whether the log contain any error
information. If any error information is found, handle it according to Solaris system
administrator manual.
12.2.5 Checking Database Status

Refer to "7.3 Querying Database Status" to check the database status and used space.
If the free space of the database is insufficient, refer to 7.9 Clearing Database" to
handle it.
12.2.6 Checking Hard Disk Space

Refer to "8.3 Query Disk Space" to check the space of the disk. If the free hard disk
space is insufficient, refer to "8.4 Clearing Disk Space" to handle it.
12.2.7 Checking CPU Utilization

Refer to "5.4 Querying System Performance" to check the CPU utilization of the Server.
If the CPU ululation is too high, refer to "5.5 Adjusting System Performance" to handle
it.
12.2.8 Checking Number of Processes

Refer to "6.3
Querying Number of M2000 Processes" to check the number of
processes. If the number is not enough, refer to "6.4 Querying Service Status" to check
the processes which need to be started, and then refer to "6.5
Services" to start them.
12-2
Starting M2000
Administrator Guide
12.2.9 Checking Service Status

Refer to "6.4 Querying Service Status" to check the status of the services. If any one of
them is abnormal, refer to "6.5 Starting M2000 Services" start the process or service to
be started.
12.3 Weekly Maintenance

12.3.1 Weekly Maintenance Item List
Table 12-2 lists the weekly maintenance item of M2000 system. Refer to 12.3.2
Backing Up M2000 System and the later section for operation guide of each
maintenance item.
Table 12-2 Weekly maintenance checklist
SN
Item
Reference
Backup M2000 system
Open the [Periodic Backup] dialog box on M2000 Client,

and select all the data to be backed up.
Check the M2000 Server time
The time is right.
Find core files
There are no core files on the Server.
Clear useless files
Clear overdue log files, temporarily files and other

useless files.
12.3.2 Backing Up M2000 System

1)
Refer to "11.3.3 6)Switch to root
bash-2.03$ su root
2)
# stop_svc
# start_svc
Automatically Backing Up M2000" or "11.5 Manually Backing Up M2000 System" to
back up M2000 system.
12.3.3 Checking M2000 Server Time

1)
Log in as omcuser.
2)
Execute the following command to view the current Server time:
bash-2.03$ date
3)
To adjust time, refer to "2.2 Modifying Server Time".
12-3
Administrator Guide
12.3.4 Finding core Files

1)
Log in as omcuser.
2)
Execute the following command to file the core files:
bash-2.03$ find / -name core* ls

3)
Read core files and delete the useless core files.
12.3.5 Clearing Useless Files

Refer to "8.4 Clearing Disk Space" to clear the useless files in the hard disk.
12.4 Monthly Maintenance

12.4.1 Monthly Maintenance Item List
Table 12-3 lists the monthly maintenance items of M2000 system. Refer to 12.4.2
Checking Power Supply and the later section for operation guide of each
maintenance item.
Table 12-3 Monthly maintenance checklist
SN
Item
Reference
Check power supply
The power supply of the Server is normal.
Check Server hardware
The Server is not damaged physically.
Check the auxiliary devices of

the Server
The devices such as the magnetic tape drive and

CD-ROM drive are working normally.
12.4.2 Checking Power Supply

Check whether the power indicator of the Server indicates normal. Check whether the
power supply of the Server is normal.
12.4.3 Checking Server Hardware

Check whether the hardware of the Server is damaged.
12.4.4 Checking Auxiliary Devices of Server

Check the following items for the auxiliary devices of the M2000 Server:
z
Check whether the CD-ROM can run normally.
Check whether the tape drive can run normally.
12-4
Administrator Guide
For details of check CD-ROM and tape drive, refer to Solaris system administrator
manual.
12-5
Administrator Guide
Chapter 13 Troubleshooting
13.1 Overview of Troubleshooting
This chapter introduces the following contents:
z
General troubleshooting procedure, including collection of fault information, fault

location, range division and fault clearance.
Troubleshooting cases, detailing the analysis and handling of faults. Each section
describes a fault.
For the maintenance and fault handling of Solaris, refer to Solaris system administrator
manual.
For the maintenance and fault handling of Sybase database, refer to Sybase system
administrator manual.
13.2 Troubleshooting Procedure

13.2.1 Overview of Troubleshooting Procedure
Generally, a troubleshooting procedure covers information collection, fault location and
fault removal.
13.2.2 Information Collection

In case of a system fault, it is necessary to collect the following information:
z
Time and place of the fault occurrence
Symptom
Implemented measures and results after fault occurrence
Version information
IP information
Alarm information
Log information
The logs include user log, system log and trace log.
z
Internal problem location Information
Use the M2000 diagnostic tool to collect the internal problem location information. For
details of the M2000 diagnostic tool, refer to "16.3 M2000 Diagnostic Tool".
13.2.3 Fault Location

Fault location refers to the processes of looking for the actual fault cause from many
possible causes. Collection and analysis of fault information help locate the fault cause.
13-1
Administrator Guide
M2000 system faults include hardware faults and software faults.

z
Hardware faults
The hardware faults include the ones occurring to M2000 Server, Client and networking
equipment. The appearance and status indicators of hardware help locate hardware
faults easily.
z
Software faults
The software faults include the ones occurring to M2000 system, the operating system
and the database that M2000 is based on.
13.2.4 Fault Clearance

Clear the faults according to their causes:
z
Hardware faults
Refer to the manual delivered with device.

z
M2000 software faults
Refer to M2000 Client alarm online help to clear the faults.

For the clearance of faults related to software installation, refer to iManager M2000
Mobile Element Management System Installation Manual.
For the clearance of faults related to the Client, refer to iManager M2000 Mobile
For the clearance of faults related to the Server, refer to this chapter.
z
Solaris faults
Refer to Solaris system administrator manual.

z
Sybase database faults
Refer to Sybase system administrator manual.

z
Fault unable to clear
Collect all the information about an irremovable fault (refer to "13.2.2 Information
Collection")and contact Huawei for handling immediately.
13.3 Auto Shutdown of Operating System

13.3.1 Symptom
When the serial port cable connecting the M2000 Server and terminal is removed, the
operating system shuts down automatically.
13.3.2 Fault Analysis

Under the default settings of Solaris, when the Server is disconnected from the terminal,
the system will be shut down automatically.
13-2
Administrator Guide

Perform the following operations to clear the faults:
1)
Reconnect the serial port cable between M2000 Server and the terminal.
2)
Log in to the Server as root on the terminal.
3)
Open the file "/etc/default/kbd".
4)
Delete the "#" before "KEYBOARD_ABORT=alternate" in this file.
5)
Save the change and quit.
6)
Restart the system.
# /usr/sbin/shutdown i6 g0 y
7)
Remove the serial port cable between M2000 Server and the terminal, and the
operating system will not shut down automatically.
13.4 Abnormal Service Restart

13.4.1 Symptom
Some services automatically restart abnormally.

The possible causes are:
z
Sybase is abnormal.
The M2000 system is abnormal.

Perform the following operations to clear the fault:
1)
Log in to the Server with the ID of "root".
2)
Execute the following command to stop M2000 services:
# stop_svc
This command fails, execute the following command to stop the service:
# kill_svc
3)
Execute the following command to stop Sybase:

2> go
1> shutdown
2> go
4)
Set Sybase operation parameter:
13-3
Administrator Guide
Refer to iManager M2000 Mobile Element Management System Installation Manual to

set Sybase operation parameters.
5)
Execute the following command to restart Sybase:
# cd /opt/sybase/ASE-12_0/install
# ./startserver f ./RUN_SYB
# ./startserver f ./RUN_SYB_back
6)
Execute the following command to start M2000 services:
# start_svc
7)
View system log
View the system log file in "/export/home/omc/var/logs" to find the cause of abnormal
service.
13.5 Abnormal Service Termination

13.5.1 Symptom
# svc_adm -cmd status
The output message contains "not running", meaning that this service is terminated
abnormally.

z
Error occurs to program operation causing the abnormal termination of the

service.
The startup procedure is manually terminated.

Perform the following operations to clear the fault:
1)
Log in to the Server as root.
2)
Execute the following command to start service:
# start_svc
Do not manually terminate the startup procedure.
3)
If there is any service not started yet, contact Huawei for solution.
13-4
Administrator Guide
13.6 M2000 Services Starting or Stopping Failure

13.6.1 Symptom
Executing one of the following commands fails:
z
start_svc
stop_svc
kill_svc

z
No execution runtime script is available before executing these commands.
More that one user is executing the above commands at the same time.

Perform the following operations to clear the faults:
1)
Execute the runtime script. For the execution of runtime script, refer to "15.3
svc_profile.sh".
2)
Make sure that only one user executes the above commands at the same time.
13-5
Administrator Guide
Chapter 14 Emergency Maintenance

14.1 Overview of Emergency Maintenance
This chapter provides the operation guide of emergency maintenance in the case of
serious accident on M2000 Server or Client, including:
z
Emergency maintenance for M2000 Server
Emergency maintenance for M2000 Client
14.2 Emergency Maintenance for M2000 Server

If the problems of operating system abnormal, database abnormal or service failure
occur to the Server, and cannot be cleared according to the methods introduced in
"Chapter 13 Troubleshooting", you can recover the Server using the backup of the
operating system and M2000 system.

Perform the following operations to recover the M2000 Server:
1)
Recover the operating system
If the operating system backup is available, refer to "11.8 Restoring Operating

System" to recover the operating system, database, M2000 software and
parameter settings.
If the operating system backup is not available, refer to iManager M2000 Mobile
Element Management System Installation Manual to reinstall the operating
system.
2)
Recover the M2000 system
Refer to "11.6 Restoring M2000" to recover the M2000 database data and M2000
system files.
14.3 Emergency Maintenance for M2000 Client

If the problems of operating system abnormal or service failure occur to the Server, and
cannot be cleared according to the methods introduced in "Chapter 13
Troubleshooting", you need to reinstall the Client.
14-1
Administrator Guide

Perform the following operations to recover the M2000 Client:
1)
Recover the operating system
Reinstall the operating system of the M2000 Client.

2)
Recover the M2000 system
Refer to iManager M2000 Mobile Element Management System Installation Manual to

reinstall the M2000 Client software.
14-2
Administrator Guide
Chapter 15 Command Guide

15.1 Overview of Command Guide
This chapter consists of the following contents:
z
Introduction to commands: introduces the path of the commands and

prerequisites of using them.
svc_profile.sh: introduces the functions and running of the environment script.
Functions of some important commands and the corresponding examples.
15.2 Introduction to Commands

15.2.1 Path of Commands
The M2000 system maintenance commands are stored in "/<M2000 installation
directory>/bin".
15.2.2 Prerequisites of Using Commands

The prerequisites of using M2000 commands are:
z
Sybase is running normally.
The M2000 environment setting script svc_profile.sh has been executed.
15.3 svc_profile.sh
15.3.1 Function of svc_profile.sh
It is necessary to execute the script, svc_profile.sh, before using the M2000 commands.
This script is used to set the users working environment, such as command search
path and dynamic library search path.
15.3.2 Path of svc_profile.sh

The script, svc_profile.sh, is in "/<M2000 installation directory>".
15.3.3 Running svc_profile.sh

The script, svc_profile.sh, can be manual running and auto running.
z
Manual running
The method of manually running this script is:

bash-2.03$ . /<M2000 installation directory>/svc_profile.sh
15-1
Administrator Guide
Caution:
There must be a . at the beginning of a command, and a space between . and /.
Auto running
After the installation of the system according to iManager M2000 Mobile Element
Management System Installation Manual, the script is added to the file ".profile" of
"omcuser" and "root". If you log in as omcuser or root, the system will automatically run
this script.
Note:
iManager M2000 Mobile Element Management System Installation manual introduces the settings of the
file ".profile" of "omcuser" and "root".
15.4 start_svc
15.4.1 Command Function
This command is used to start all the M2000 services. If the services have been already
started, this command will try to start each service, and prompts that each service is
already running.
15.4.2 Example
# start_svc
============================ Starting Services ...
TAO Naming Service is running
TAO Notification Service is running
Monitor_Service already running.
imapsysd already running.
LogServer
[starting... ]
svc_adm:info:service with this name is already running
...
============================ Finished Starting Services.
15-2
Administrator Guide
15.5 stop_svc
This command is used to stop all the M2000 services If the services are not started yet,
this command will try to stop each service and prompts error.
15.5.2 Example
# stop_svc
============================ Stopping System ...
SystemMonitor
[stopped
EventManager
[stopped
LogServer
[stopped
...
============================ Finished Stopping System.
15.6 kill_svc
This command stops all the M2000 processes and services using the kill process
mechanism of the operating system. It is an extreme measure to use this command. It
may cause data loss and service abnormal.
In normal cases, use stop_svc to stop all the M2000 services. Do not use kill_svc to kill
the processes unless in special cases such as when the process is abnormal.
15.6.2 Example
# kill_svc
15.7 svc_adm cmd status

This command is used to view the current running status of all M2000 services.
15.7.2 Example
bash-2.03$ svc_adm cmd status
The current status ("running" or "not running") of all services will be displayed.
15-3
Administrator Guide
15.8 svc_ps
This command is used to query the running status of all M2000 processes.
15.8.2 Example
bash-2.03$ svc_ps
This command returns the running M2000 processes in the system.
15.9 top
This command is used to display the total CPU and memory utilization in the system
and the CPU and memory utilization of each process.
15.9.2 Example
bash-2.03$ top
load averages: 0.03, 0.11, 0.30
10:37:25
107 processes: 106 sleeping, 1 on cpu

CPU states: 99.4% idle,
0.0% user,
0.6% kernel,
0.0% iowait,
0.0% swap
Memory: 4096M real, 2655M free, 8099M swap free
PID USERNAME THR PRI NICE
SIZE
RES STATE
TIME
346 root
52
59
109M
5378 root
22
58
95M
67M sleep
0:08
0.09% imapsvcd
5371 root
21
58
61M
30M sleep
0:07
0.07% imapsysd
6726 root
58
0 2160K 1664K cpu0
0:00
0.07% top
101M sleep 632:43
CPU COMMAND
0.32% dataserver
...
Table 15-1 lists the meanings of the columns in the returned message of the command
"top".
Table 15-1 Meanings of columns in returned message of command "top"
Column
Meaning
PID
Process number
USERNAME
Name of the user running this process
THR
Thread number
PRI
Priority
NICE
Indicates whether this process is normal
15-4
Administrator Guide
Column
Meaning
SIZE
Size of buffer and memory occupied by this process (unit: megabyte)
RES
Size of memory occupied by this process (unit: megabyte)
STATE
Current status of this process. If the process is running, then the CPU it uses is
displayed.
TIME
The time this process has been running by far
CPU
CPU utilization of this process
COMMAND
Command that starts this process
15.10 svc_adm cmd reload

This command is used to load the configuration data from the configuration file
imap.xml to the system configuration module. This command realizes the real time
update of configuration information during M2000 service running.
15.10.2 Example
bash-2.03$ svc_adm cmd reload
After executing this command, the configuration data in the configuration module is the
same as the data in the file imap.xml.
15.11 svc_stacks
This command is used to collect the stack information of the M2000 services. It is used
in internal problem location and commissioning.
15.11.2 Example
bash-2.03$ svc_stacks
After executing this command, the query results will be saved in "/<M2000 installation
directory>/var/logs/imap_stacks.YY_MM_DD__HH:MM:SS".
In the above description, "YY" is the last two digits of the year, "MM" is the month, "DD"
is the date, "HH" is the hour, "MM" is the minute and "SS" is the second.
15-5
Administrator Guide
15.12 svc_lockdump
This command is used to collect the lock status of the current management objects. It is
used in internal problem location and commissioning.
15.12.2 Example
bash-2.03$ svc_lockdump
Dump MO Locks information successfully.
After executing this command, the query results will be saved in "/<M2000 installation
directory>/var/logs/iMAP.lock.dump".
15-6
Administrator Guide
Chapter 16 Tool Guide

16.1 Overview of Tool Guide
This chapter introduces the functions and usages of M2000 tools.
16.2 Tape Drive Management Tool

16.2.1 Function
The tape drive management tool provides GUI for the user to manage various types of
type drive, including the produces of Sony, HP and Sun.
16.2.2 Starting method

1)
Log in as omcuser.
2)
Execute the following command to check whether the status of the tape drive is
normal:
bash-2.03$ mt -f /dev/rmt/0 status

HP DDS3 4mm DAT
tape drive:
sense key(0x6)= Unit Attention

file no= 0
residual= 0
retries= 0
block no= 0
If the status information of the tape drive can be displayed, it means that the tape drive
is running normally.
3)
Execute the following command to start the tape management tool:
bash-2.03$ . /<M2000 installation directory>/tapemanager/tapemanager.sh

Figure 16-1 illustrates the main interface of the tape drive management tool.
16-1
Administrator Guide
Tape drive
directory tree
Local disk
directory tree
Tape drive file

information
output area
Disk file
information
output area
Figure 16-1 Tape drive management tool
16.2.3 Operation Guide

The tape drive management tool provides the following operations:
Caution:
It is necessary to load the tape before any operation. The possible causes of tape loading failure are tape
drive not connected correctly, tape damaged, no tape in the tape drive and tape drive busy.
Load and eject: Load the tape into the tape drive, eject the tape from the tape drive
Format tape: Format the tape to the specified format
Backup and restoration files: back up the files in the disk to the tape drive, restore
the files in the disk
Search files: search for a file in the tape drive or disk
Query tape drive status
Refresh
Delete
16.3 M2000 Diagnostic Tooling

16.3.1 Function
This tool can be used to collect and save the problem locating information of the Server
and Client to the specified directory in the Server or Client. The information includes:
16-2
Administrator Guide
Client trace log
Client JAVA virtual machine thread stacks and lock status
Server trace log
Server core files
Queue synchronization pointer of software management
Number and status of background threads, that is, the result of pstack
Lock status of MO
Alarm synchronization numbers of the NEs
Alarm diagnostic data.
16.3.2 Running Diagnostic Tool

Perform the following operations to run the diagnostic tool:
1)
2)
Select the menu [Start/iManager M2000 Client/M2000 Diagnosis] to run the

diagnostic tool. The window [M2000 Diagnostic Tool] is displayed, as shown in
Figure 16-2.
Figure 16-2 M2000 diagnostic tool

3)
In the window [M2000 Diagnostic Tool], click <Setting> to open the window [FTP
Server Setting], as shown in Figure 16-3.
16-3
Administrator Guide
Note:
If the tool parameters have been set, step 2) and 3) can be skipped.
Figure 16-3 FTP service setting

4)
In the dialog box [FTP Server Setting], enter the parameter information, and then
click <OK>.
IP Address: Server IP
Port: FTP service port number. Normally the default value 10119 is adopted. If it
needs to be modified, then the setting on the Server also needs to be modified. To
modify the service parameter setting, log in to the Server as ftpuser and execute
the command "start_collector port <port number>".
FTP User Name: ftpuser
Password: password of Solaris user "ftpuser"
Delete the collected files in Server after collecting: if select it, the collected
information will be deleted from the Server, and only stored in the Client; if do not
select it, the collected information will be saved to both the Client and
"/export/home/omc/var/DebugInfo" in the Server.
5)
In the window [M2000 Diagnostic Tool], enter the time and file path. If you want to
collect some NEs alarm diagnostic data, select Collect Alarm Diagnostic Data,
and input the NE name. Then click <Collect> to start collecting Diagnostic
information.
16-4
Administrator Guide

If you fail to run the diagnostic tool, perform the following operations:
1)
2)
Check whether the diagnostic service is running:
# ps -ef | grep start_collector | grep -v grep

If there is any message returned, it means that the service is running. Otherwise, the
service is not running.
Note:
Normally, the diagnostic service start to run automatically after M2000 Server application software is
installed successfully.
3)
Start the diagnostic service if it is not running yet.
# start_collector
4)
Restart diagnostic tool on the Client. Refer to 16.3.2 Running Diagnostic Tool.
16.3.4 Forbidding Using Diagnostic Tool

To forbid using diagnostic tool, perform the following operations on the Server to stop
diagnostic service:
1)
2)
Stop diagnostic service:
# stop_collector
16.4 Performance Job Result Auto Export Tool

16.4.1 Function
The performance job result auto export tool is used to automatically export the
performance job results. After running this tool, the system periodically exports the
specified job results to a file.
The exported job results will not be deleted from the performance database. They will
be deleted after they have been stored for a period of time (defined when the task is
created).
16.4.2 Function Settings

You can configure the export function by modifying the configuration file "/<M2000
installation directory>/bin/PMExporst.cfg".
16-5
Administrator Guide
This file consists of the following four parts:

z
PATH=/export/home/omc/var/backup/pm/
The storage directory of the exported file. In this example, the directory is
/export/home/omc/var/backup/pm/. When this tool is running, it creates a sub-directory
under this directory every day. The name of a sub-directory is "PMExporst_<the current
date>". All files generated that day are saved in this sub-directory. The name of an
exported file is "PMResult_<task number>_<start time>_<end time>.csv".
z
SAVEDAYS=3
The storage days of the exported file. In this example, the file will be kept for three days.
After the storage days, it will be deleted from the disk.
z
DELAY=30
Because some NEs may report performance job results with delay, M2000 can export
the results of the previous measurement period only after a delay of several minutes.
The setting here indicates that the delay is set to 30 minutes. The delay ranges from 30
to the integer multiple of 30.
z
101:30
The job number and the jobs export period. The export period (unit: minute) can be set
as 30, 60 or 1440. In this example, 101 is the task number, and the export period is 30
minutes.
To export multiple jobs result, it is necessary to add multiple entries of such information
to the configuration file. For example:
102:60
103:1440
The parameter PATH, SAVEDAYS and DELAY is the same for each task, and only the
export period is different for each task.
Because the processing of performance task results takes some time, the task of a
period is exported 30 minutes later. For example, if the export period is 60 minutes,
then the data within 1:002:00 will be exported at 2:30, and the data within 2:003:00
will be exported at 3:30.
16.4.3 Running Auto Export Tool
Caution:
When this tool is running, you cannot start this tool again.
Perform the following operations on the Server to run the auto export tool:
16-6
Administrator Guide
1)
Log in as omcuser.
2)
Run the auto export tool PMExporst.
bash-2.03$ nohup PMExporst SYB sa <sa user password> &

After that, job results of each time segment is exported to files after a delay
automatically. The time segment is divided according to export period, see Table 16-1.
Table 16-1 Export period and time segment
Export period ( minute)
Time segment
30
Every 30 minutes starting from 0:00. For example, 0:00-0:30,

0:30-1:00, 1:00-1:30, 1:30-2:00......
60
Every hour starting from 0:00. For example, 0:00-1:00, 1:00-2:00,

2:00-3:00, 3:00-4:00......
1440
Every day. For example, 0:00-24:00
For example, to export the results with the export period of 60 minutes and the delay of
30 minutes, the result of 0:001:00 will be exported at 1:30, and the result of 1:002:00
will be exported at 2:30.
16.4.4 Stopping Auto Export Tool

Perform the following operations on the Server to stop the service:
1)
Log in as omcuser.
2)
Stop the auto export tool:
bash-2.03$ ps -ef | grep PMExporst | grep -v grep

3)
Query the process ID (pid) of PMExporst, and stop this process:
bash-2.03$ kill -9 <pid>

If the result files cannot be generated as expected, perform the following operations:
1)
Execute the following command to check whether the service is running:
bash-2.03$ ps -ef | grep PMExporst | grep -v grep

2)
If the service is not running, check whether any error prompt exists in the file
"/opt/OMC/bin/nohup.out". The possible cause is that wrong parameter was
entered when starting the tool.
3)
Check
whether
any
error
information
exists
in
the
log
file
"
/opt/OMC/bin/PMExporest.log".
4)
If the service is running, the possible cause is that the task does not exist or it has
not report result yet. The related information can be viewed in the log file
16-7
Administrator Guide
"/opt/OMC//var/logs/PMExporest.log". If a task does not exist, it will not affect the

export of other task results.
16.5 IP Modification Tool

16.5.1 Function
M2000 provides the IP modification tool based on command line mode for the system
administrator to implement IP setting and query of Solaris and Sybase data base.
The path of the IP modification tool is "/<M2000 installation directory>/bin".
16.5.2 Prerequisites
The prerequisites of running the IP modification tool are as follows:
z
The M2000 system has been installed successfully.
The environment setting script is running (refer to "15.3 svc_profile.sh").
Log in as root.
16.5.3 Querying IP Settings

I. Command format
# iptools l
II. Example
# iptools l
InterfaceName
IPAddress
MACAddress
-----------------------------------------------------------eri0 Titan 00:03:ba:12:f9:12

-----------------------------------------------Sybase Listener IP Address
Port
-----------------------------------------------10.161.45.241
4100
The output message displays the current system IP settings:

z
Interface name: eri0
IP address: Titan. "Titan" is the host name. Its corresponding IP address can be
queried in the file "\etc\hosts".
Mac address: 00:03:ba:12:f9:12
Sybase listen address: 10.161.45.241
Port number: 4100
16-8
Administrator Guide
16.5.4 Modifying Solaris IP Address, Host name, Default Gateway and

Subnet Mask
I. Command format
# iptools {-n interface-name -i ip-address -m subnet-mask -G default -gateway -H
host-name -d }
Parameter description:
z
-n: Ethernet adapter interface name
-i: IP of the Ethernet adapter (decimal IP address)
-G: Default gateway of Solaris
-H: Host name of Solaris
-d: Switch, which means that the IPs of all database services of Sybase are set as
the new IPs
II. Example
z
Set all interfaces. The Solaris IP is 10.70.141.54, host name is "host", default
gateway is 10.70.141.1, and the IPs of all servers of Sybase are 10.70.141.54.
# iptools n hme0 i 10.70.141.54 m 255.255.255.0 G 10.70.141.1 H host d

change net default: gateway 10.70.141.1
set new ip : 10.70.141.54 succeed !
set all services of sybase ip 10.70.141.54 succeed !
set old hostname : UFO ---> new hostname : host succeed !
Set the Ethernet adapter interface. The interface name is "hme0", the IP is
10.70.141.54, and the subnet mask is 255.255.255.0.
# iptools n hme0 i 10.70.141.54 m 255.255.255.0

set new ip : 10.70.141.54 succeed !
16.5.5 Modifying Sybase IP

I. Command format
# iptools -D ip-address
II. Example
Set IP interface descriptions of all Sybase database services.
# iptools D 10.70.141.54
set all services of sybase ip 10.70.141.54 succeed !
16-9
Administrator Guide
16.5.6 Modifying Sybase Service IP and Port Number

I. Command format
# iptools {-S service-name -D ip-address -P port }
II. Example
Set the IP of the SYB service of Sybase database as 10.70.141.54 and the port number
as 4000.
# iptools S SYB D 10.70.141.54 P 4000
set service SYB with ip 10.70.141.54 succeed !
16.5.7 Modifying Host Name

I. Command format
# iptools -H host-name
II. Example
Modify the Solaris host name as "omc".
# iptools H omc
set old hostname : host ---> new hostname : omc succeed !
If the new name is the same as the original name, the system will prompt:
omc is same with the current host name !
16.5.8 Modifying Gateway

I. Command format
# iptools -G gateway
II. Example
Set the Solaris gateway as 10.70.141.1.
# iptools G 10.70.141.1
change net default: gateway 10.70.141.1
If the modification of gateway fails, the system prompts:

change default gate failed!!
16-10
Administrator Guide
Chapter 17 FAQ
Chapter 17 FAQ
17.1 Overview of FAQ
This chapter introduces the frequently asked questions and the solutions concerning
Solaris operating system and Sybase database.
17.2 Logging in as root though Telnet

17.2.1 Question
Why can't I log in as root through Telnet?
17.2.2 Answer
For the sake of security, the user root can log in to the system only through the console
after Solaris8 is installed. If it is necessary to log in to the system through telnet as root,
follow the procedure below. It is recommended restoring the original setting after that.
1)
Log in as root.
2)
Open the file "/etc/default/login".
3)
Find the line of CONSOLE=/dev/console. Add "#" in the front of the line to turn it to
a comment line.
4)
Save the settings and exit.
17.3 Logging in as root though FTP

17.3.1 Question
Why can't I log in as root through FTP?
17.3.2 Answer
For the sake of security, the user root does not have the authority to use FTP by default.
If it is necessary to log in to the system as root through ftp, follow the procedure below.
It is recommended restoring the original setting after that.
1)
Log in as root.
2)
Open the file /etc/ftpusers
3)
Find the line of root user, and delete the line.
4)
Save the settings and exit.
17-1
Administrator Guide
Chapter 17 FAQ
17.4 Installing Tape Drive

17.4.1 Question
How to install tape drive for the Server?
17.4.2 Answer
The built-in tape drive does not require the installation of driver. When the Server is
started up, it will be identified automatically. The external tape drive requires the
installation of driver. In the case of Sun Ultra 60, the installation is as follows:
1)
Power off all peripherals;
2)
Set the ID switch of the tape drive to 4 or 5;
3)
To use the SCSI interface, connect the SCSI cable to the IN interface of the tape
drive.
4)
Power on all peripherals and the host, and boot the system.
5)
Log in as root.
6)
Execute the following command to view the tape drive status:
# mt f /dev/rmt/0mn status
The above command can be abbreviated as mt status.
The following prompts may appear:
HP DDS-3 4MM DAT tape drive:
sense key(0x6)= Unit Attention
file no= 0
residual= 0
retries= 0
block no= 0
This means that the tape drive is normal. There is a tape in the tape drive, and the tape
has been rewound to the beginning.
No such device or address
This means that the tape drive is not connected with the work station or the connection
is incorrect.
/dev/rmt/0n: no tape loaded or drive offline
This means that the tape or tape drive is in offline state.

/dev/rmt/0n: No such file or directory
This means that the tape drive is not attached.

7)
If the tape drive is not attached, execute the following command to attach the tape
drive:
# drvconfig
# tapes
8)
When the tape drive is attached, insert a tape, and then execute the following
command to view the tape drive status:
17-2
Administrator Guide
Chapter 17 FAQ
# mt status
17.5 Setting Default Route

17.5.1 Question
How to set the default route in Solaris system? For example, there multiple NodeBs are
controlled by one RNC. How to set the RNC IP as the default route IP, so as to establish
a maintenance channel from M2000 to NodeBs?
17.5.2 Answer
Perform the following operations on the Server:
1)
Log in as root.
2)
# vi /etc/defaultrouter
3)
Enter the default route IP in the file, for example:
10.161.44.1
4)
Save the change and quit vi.
5)
Execute the following command to restart the Server:
# init 6
17.6 Adding and Deleting Routes

17.6.1 Question
How to add and delete routes in Solaris system? For example, how to establish the
maintenance channels to NodeBs controlled by multiple RNCs?
17.6.2 Answer
Perform the following operations on the Server:
1)
Log in as root.
2)
Perform the following operations according to the actual needs:
Too add a route, execute the following command:
# route add <destination address>/<subnet mask> <gateway>

Destination address: can be either a network address or a host address.
Subnet mask: Must be a number, that is, the total number of "1" in the binary subnet
mask.
For example, "32" means "255.255.255.0".
For example, route add 129.8.0.0/32 10.12.8.1
17-3
Administrator Guide
z
Chapter 17 FAQ
To delete a route, execute the following command:
# route delete <destination address>/<subnet mask> <gateway>

For example, route delete 129.8.0.0/32 10.12.8.1
z
To view the route information, execute the following command:
# netstat rv
z
To enable the system to automatically execute the route adding command on

system startup, create the file "/etc/rc2.d/S97route":
# vi /etc/rc2.d/S97route
Write one or more entries of router add <destination address>/<subnet mask>
<gateway> commands in this file. For example:
route add 129.9.0.1/32 10.12.8.1
route add 129.8.0.0/16 10.12.8.1
17.7 "/etc/rc2.d" in Solaris

17.7.1 Question
What are the meanings of the files in the directory "/etc/rc2.d" in Solaris?
17.7.2 Answer
There are two types of files in "/etc/rc2.d": those with the initial letter of capitalized "S"
and those with the initial letter of capitalized "K".
z
During the startup of Solaris, the system executes all script files with the initial
letter of "S" in "/etc/rc2.d" in alphabetical order.
During the shutdown of Solaris, the system executes all script files with the initial
letter of "K" in "/etc/rc2.d" in alphabetical order.
The installation software of M2000 Server will generate three startup files in
"/etc/rc2.d/": S98sybase (for starting Sybase), S98TAO (for starting TAO service) and
S99IMAP (for starting M2000 services).
17.8 Querying Hardware Configuration of Server

17.8.1 Question
How to query the hardware configuration of the Sun server? How to check the size of
memory?
17.8.2 Answer
Perform the following configurations on the Server:
17-4
Administrator Guide
1)
Log in as root.
2)
Chapter 17 FAQ
# prtconf
System Configuration:
Sun Microsystems
sun4u
Memory size: 512 Megabytes

System Peripherals (Software Nodes):
SUNW,Ultra-60
packages (driver not attached)
terminal-emulator (driver not attached)
In the message above, "Memory size: 512 Megabytes" indicates the size of memory,
and "SUNW, Ultra-60" is the type of the Server.
17.9 Confirming Startup of Sybase

17.9.1 Question
How to check the startup status of Sybase?
17.9.2 Answer
Perform the following operations on the Server to check the status of Sybase:
1)
Log in as dbuser.
2)
bash-2.03$ cd /opt/sybase/ASE-12_0/install
bash-2.03$ ./showserver
root 21684 21683 0 October 29 ?
0:00 /opt/sybase/ASE-12_0/bin/backupserver
-SSYB_back -e/opt/sybase/ASE-12_0/install
root 23718 23716 7 November 01 ?
678:28 /opt/sybase/ASE-12_0/bin/dataserver
-sSYB -d/data/master_dev.dat -e/opt/sybase/
If the returned message contains "dataserver" and "backupserver", it means that the
active and standby databases are both started.
17.10 Starting Sybase

17.10.1 Question
How to start Sybase service?
17.10.2 Answer
Perform the following operations on the Server to start Sybase service:
17-5
Administrator Guide
1)
Log in as dbuser.
2)
Chapter 17 FAQ
bash-2.03$ cd /opt/sybase/ASE-12_0/install/
bash-2.03$ ./startserver -f ./RUN_SYB
bash-2.03$ ./startserver -f ./RUN_SYB_back
17.11 Stopping Sybase

17.11.1 Question
How to stop Sybase service?
17.11.2 Answer
Perform the following operations on the Server to stop Sybase service:
1)
Log in as dbuser.
2)
bash-2.03$ isql -SSYB -Usa -P<password of user sa>

2> go
1> shutdown
2> go
Note:
If the M2000 Server software has been installed, Sybase will be started automatically after the startup of
the operating system.
17-6
Administrator Guide
Appendix Acronyms and Abbreviations

C
CORBA
Common Object Request Broker Architecture
CPU
Central Processing Unit
E
EMS
Element Management System
F
FAQ
Frequent Ask Question
FTP
File Transfer Protocol
I
ID
Identity
IDL
Interface Description Language
IP
Internet Protocol
L
LMT
Local Maintenance Terminal
M
MB
Mega Byte
N
NMS
Network Management System
NTP
Network Time Protocol
O
OMC
Operation & Maintenance Center
P
PID
Process Identification
R
RNC
Radio Network Controller
S
SCSI
Small Computer Systems Interface
SQL
Structured Query Language
Administrator Guide
TCP
Transfer Control Protocol
Administrator Guide
Index
Index
fault information, 16-2
command
adding
kill_svc, 15-3
M2000 user, 3-6
start_svc, 15-2
M2000 user group, 3-6
stop_svc, 15-3
operating system user, 3-3
svc_adm cmd reload, 15-5
route, 17-3
svc_adm cmd status, 15-3
adjusting
svc_lockdump, 15-6
system performance, 5-3
svc_profile.sh, 15-1
alarm data
svc_ps, 15-4
displacing automatically, 7-6
svc_stacks, 15-5
displacing manually, 7-5
top, 15-4
creating
M2000 user, 3-6

M2000 user group, 3-6
backing up
operating system user, 3-3
M2000 system, 11-4, 11-5

operating system, 11-7
backup and restoration

database, 11-1
daily maintenance
introduction, 11-1
item list, 12-1
setting, 11-3
operation guide, 12-1
browsing
database
system log, 4-3
clearing, 7-8
user log, 4-3
fmdb, 7-2
introduction, 7-1
modifying user password, 3-5

omcdb, 7-1
checking
NTP service, 10-3
pmdb, 7-2
solaris error log, 4-3
querying, 7-4
Sybase, 17-5
sysmdb, 7-3
user account, 3-3
clearing
dbuser
database, 7-8
disk space, 8-3
introduction, 3-2
pmdb, 7-7
modifying password, 3-4

default route
client
setting, 17-3
emergency maintenance, 14-1
deleting
file system, 8-2
route, 17-3
collecting
i-1
Administrator Guide
Index
modifying, 16-8
diagnosis
tool, 16-2
disk space
clearing, 8-3
host name
querying, 8-2
modifying, 2-2, 16-8
displacing
alarm data, 7-5, 7-6

user log, 7-5, 7-7
inrpt
dual-plane
introduction, 3-2
automatically setting, 9-3
installing
configuration procedure, 9-2
tape drive, 17-2
introduction, 9-1
introduction
manually setting, 9-2
backup and restoration, 11-1
verifying, 9-4
command, 15-1
dumping. see displacing
database, 7-1
dual-plane, 9-1
file system, 8-1
emergency maintenance
fmdb, 7-2
client, 14-1
log, 4-1
server, 14-1
NE log, 4-1
exporting
NTP, 10-1
performance result, 16-5
omcdb, 7-1
pmdb, 7-2
process, 6-1
service, 6-1
file system
client, 8-2
sysmdb, 7-3
introduction, 8-1
system log, 4-2
server, 8-1
trace log, 4-2

user account, 3-1
fmdb
user log, 4-1

IP

modifying, 2-3, 16-8
introduction, 7-2
querying, 16-8
FTP
logging, 17-1
ftpuser
log
introduction, 3-2
introduction, 4-1
ftpusr
NE log, 4-1
system log, 4-2

trace log, 4-2
type, 4-1
user log, 4-1
gateway
i-2
Administrator Guide
Index
logging
through FTP, 17-1
omcdb
through Telnet, 17-1
M2000
introduction, 7-1
auto startup, 17-4
omcuser
backing up automatically, 11-4
introduction, 3-2
backing up manually, 11-5
creating user, 3-6
operating system
creating user group, 3-6
backing up, 11-7
monitoring user, 3-6
creating user, 3-3
restoring, 11-6
modifying user password, 3-4
user account, 3-3
restoring, 11-9
modifying
user account, 3-1
gateway, 16-8
host name, 2-2, 16-8

IP, 2-3, 16-8
pmdb
time, 2-1
user password of database, 3-5
clearing, 7-7
user password of operating system, 3-4
exporting job result, 16-5
monitoring
introduction, 7-2
M2000 user, 3-6
procedure
server status, 5-1
configuring dual-plane, 9-2
monthly maintenance
item list, 12-4
troubleshooting, 13-1
process
multiple IPs
introduction, 6-1
setting, 2-4
querying number, 6-6
NE log
querying
introduction, 4-1
database, 7-4
NTP
disk space, 8-2
checking, 10-3
hardware configuration, 17-4
introduction, 10-1
IP, 16-8
setting middle NTP server, 10-2
process number, 6-6
setting NTP client, 10-2
server status, 5-1
setting top NTP server, 10-2
service status, 6-6
starting, 10-2
system performance, 5-2
stopping, 10-3
i-3
Administrator Guide
Index
threshold server status alarm, 5-2

top NTP server, 10-2
removing. see deleting
solaris error log
restoring
checking, 4-3
M2000 system, 11-6
starting
M2000 service, 6-8
root
NTP service, 10-2
introduction, 3-1
Sybase, 17-5
startup file
route
for M2000, 17-4
adding, 17-3
for Sybase, 17-4
deleting, 17-3
stopping
setting, 17-3
M2000 service, 6-9
routine maintenance
NTP service, 10-3
daily maintenance, 12-1
Sybase, 17-6
monthly maintenance, 12-4
stting
weekly maintenance, 12-3
time, 2-1
Sybase
auto startup, 17-4
sa
checking, 17-5
introduction, 3-3
starting, 17-5
stopping, 17-6
server
sysmdb
auto startup, 17-4
introduction, 7-3
file system, 8-1
system log
querying hardware configuration, 17-4
browsing, 4-3
querying status, 5-1
introduction, 4-2
setting status alarm threshold, 5-2
system performance
service
adjusting, 5-3
introduction, 6-1
querying, 5-2
querying status, 6-6

starting, 6-8
stopping, 6-9
tape drive
setting
installing, 17-2
management, 16-1
default route, 17-3
Telnet
gateway, 16-8
logging, 17-1
host name, 2-2, 16-8
time
IP, 2-3, 16-8
modifying, 2-1
middle NTP server, 10-2
trace log
multiple IPs, 2-4
introduction, 4-2
NTP client, 10-2
i-4
Administrator Guide
Index
troubleshooting
case, 13-2
root, 3-1
fault clearance, 13-2
type, 3-1
user authority
fault location, 13-1

information collection, 13-1
database, 3-3
procedure, 13-1
M2000, 3-3
tool, 16-2

user log
browsing, 4-3
user account
database, 3-3
dbuser, 3-2
introduction, 4-1
ftpuser, 3-2
inrpt, 3-2
introduction, 3-1
weekly maintenance
M2000, 3-3
item list, 12-3
omcuser, 3-2
i.
i-5

M2000 Administrator Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M2000 Administrator Guide PDF

Uploaded by

Copyright:

Available Formats

Chapter 1 Overview of Administrator Guide .................................................

1.1 Objective ................................................................................................

Chapter 2 Server Parameter Settings ............................................................

2.1 Overview of Server Parameter Settings .................................................

Chapter 3 User Management ..........................................................................

3.1 Overview of User Management ..............................................................

3.5.1 Operation Effect .............................................................................

Chapter 4 Log Management ............................................................................

4.1 Overview of Log Management ...............................................................

Chapter 5 Server Performance Monitor .........................................................

5.1 Overview of Server Performance Monitor ..............................................

5.5 Adjusting System Performance ..............................................................

Chapter 6 M2000 Process and Service Management ...................................

6.1 Overview of M2000 Process and Service Management ........................

Chapter 7 Database Management ..................................................................

7.1 Overview of Database Management ......................................................

7.2 Introduction to Database ........................................................................

Chapter 8 Disk Space Management ...............................................................

8.1 Overview of Disk Space Management ...................................................

Chapter 9 Dual-Plane Configuration ..............................................................

9.1 Overview of Dual-Plane Configuration ...................................................

Chapter 10 NTP Service Configuration ..........................................................

10.1 Overview of NTP Service Configuration ...............................................

Chapter 11 Backup and Restoration ..............................................................

11.1 Overview of Backup and Restoration ...................................................

11.5 Manually Backing Up M2000 System...................................................

Chapter 12 Routine Maintenance ...................................................................

12.1 Overview of Routine Maintenance .......................................................

12.4.4 Checking Auxiliary Devices of Server ..........................................

Chapter 13 Troubleshooting ...........................................................................

13.1 Overview of Troubleshooting ................................................................

Chapter 14 Emergency Maintenance .............................................................

14.1 Overview of Emergency Maintenance ..................................................

Chapter 15 Command Guide ..........................................................................

15.1 Overview of Command Guide ..............................................................

15.3.2 Path of svc_profile.sh ...................................................................

Chapter 16 Tool Guide ....................................................................................

16.1 Overview of Tool Guide ........................................................................

16.4 Performance Job Result Auto Export Tool ........................................... 16-5

17.1 Overview of FAQ ..................................................................................

Appendix Acronyms and Abbreviations .......................................................

iManager M2000 Mobile Element Management System

iManager M2000 Mobile Element Management System

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

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

About This Manual

Chapter 10 NTP Service Configuration introduces the concepts related to NTP

System engineer of mobile network

Normal paragraphs are in Arial.

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

Headings are in Boldface.

Terminal Display is in Courier New.

II. Command conventions

The keywords of a command line are in Boldface.

Command arguments are in italic.

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

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

Optional alternative items are grouped in square brackets and separated

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