You are on page 1of 132

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.3.1 Operation Effect .............................................................................
2.3.2 Operation Procedure ......................................................................
2.4 Modifying Server IP Address ..................................................................
2.4.1 Operation Effect .............................................................................
2.4.2 Operation Procedure ......................................................................
2.5 Setting Parameters of Server with Multiple IPs ......................................
2.5.1 Operation Effect .............................................................................
2.5.2 Operation Procedure ......................................................................

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.3.1 Operation Effect .............................................................................
3.3.2 Operation Procedure ......................................................................
3.4 Modifying Password of Operating System User .....................................
3.4.1 Operation Effect .............................................................................
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.5.1 Operation Effect .............................................................................
3.5.2 Operation Procedure ......................................................................
3.6 Creating M2000 User Group ..................................................................
3.6.1 Operation Effect .............................................................................
3.6.2 Operation Procedure ......................................................................
3.7 Creating M2000 User Account ...............................................................
3.7.1 Operation Effect .............................................................................
3.7.2 Operation Procedure ......................................................................
3.8 Monitoring M2000 Users ........................................................................
3.8.1 Operation Effect .............................................................................
3.8.2 Operation Procedure ......................................................................

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.3.1 Operation Effect .............................................................................
4.3.2 Operation Procedure ......................................................................
4.4 Browsing System Log .............................................................................
4.4.1 Operation Effect .............................................................................
4.4.2 Operation Procedure ......................................................................
4.5 Checking Solaris Error Log ....................................................................
4.5.1 Operation Effect .............................................................................
4.5.2 Operation Procedure ......................................................................

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.2.2 Operation Procedure ......................................................................
5.3 Setting the Threshold of Server Status Alarm ........................................
5.3.1 Function .........................................................................................
5.3.2 Operation Procedure ......................................................................
5.4 Querying System Performance ..............................................................
5.4.1 Operation Effect .............................................................................
5.4.2 Operation Procedure ......................................................................

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.5.1 Operation Effect .............................................................................
5.5.2 Operation Procedure ......................................................................

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.3.1 Operation Effect .............................................................................
6.3.2 Operation Procedure ......................................................................
6.4 Querying Service Status .........................................................................
6.4.1 Operation Effect .............................................................................
6.4.2 Operation Procedure ......................................................................
6.5 Starting M2000 Services ........................................................................
6.5.1 Operation Effect .............................................................................
6.5.2 Operation Procedure ......................................................................
6.6 Stopping M2000 Services ......................................................................
6.6.1 Operation Effect .............................................................................
6.6.2 Operation Procedure ......................................................................

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....7........................................... 8.....3.................................................2............. 8....................... 8-1 8.............................. 7.3......................................... 7..................................................5...................1 Operation Effect ....................................4 pmdb ........ 7.............2 Operation Procedure ......................................2 Operation Procedure ........8 Deleting Performance Task .......4..................... 7.................................. 7.............4 Clearing Disk Space ..........2 Operation Procedure ............2....... 8......................................7 Setting Auto Displacing for User Log ........................7......8........ 7............................................................................................. 7........................ 7..............2.........................2 Server File System .............................................................................................4 Manually Displacing Alarm Data ......... 8...........................2 Operation Procedure ........ 8.................................2............................................................................................................... 8-1 8-1 8-1 8-1 8-2 8-2 8-2 8-3 8-3 8-3 8-3 ............................................................................................................................................................................ 8....................................................................9.1 Overview of System Structure ................................................ 7.......................................... 7......................5 sysmdb .......2.................................... 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 ..............................1 Overview of Disk Space Management ....................................................................... 7................................................................ 8................................... 7..........................1 Overview of Database .......................2 Introduction to Database ...................................................................................................3 Query Disk Space .2 Operation Procedure .........................................3 Querying Database Status .. 7......... 7.............4............... 7....5...................3............6 Setting Auto Displacing for Alarm Data .................... 8.................................................................1 Operation Effect ........................... 7...... 8...............................1 Operation Effect ......1 Operation Effect ............ 7.............3 fmdb ......................................... 7......2 Operation Procedure .....................2 Operation Procedure .... 8........................................... 7.......................3 Client File System .................................................................3.......................2 Operation Procedure .................2...... 7...................................1 Operation Effect ......................................... 7.......... 7...................1 Operation Effect .............7........8..........................1 Operation Effect ......................9 Clearing Database .......2..............1 Operation Effect ......................................................5 Manually Displacing User Log ..............................................6.................................4..... 7.....................2..................9............................2 Introduction to File System ......6................................................................4........... 7...2 Operation Procedure .....2 omcdb ........... 7...............................................1 Operation Effect ........................................................

...5........... 10.............2 M2000 System Backup and NE Data Backup ..........2 Introduction to Backup and Restoration ...................................2 Operation Procedure ........ 9..........................................5 Setting M2000 as NTP Client ....................2 Operation Procedure ..................................................................................................................... 11..........................................................................4 Planning IP Data ......6 Starting NTP Service ............................................................................... 10...3.8 Stopping NTP Service .........................................................................................6..7. 11..........1 Operation Effect ............................................4 Automatically Backing Up M2000 System . 9-1 9...3 Configuration Procedure of Dual-Plane ...............1 Overview of Dual-Plane Configuration ................................... 11............................... 11............1 Introduction to Auto Backup ........... 9........ 9......1 Overview of Backup and Restoration .2......................................2 Setting Tape Drive Path ....................1 Operation Effect .................4............................................................... 11-1 11..... 11.....6.........................................................................................2..................... 10..........3 Setting Backup Media .................................................2...............................3 Setting M2000 as Top NTP Server ............................................1 Introduction to Configuration File ...................3 Abnormal Handling ..............................Chapter 9 Dual-Plane Configuration .......... 10............. 11... 9..........3............7............................................. 11.............3.......... 9..............7 Verifying Dual-Plane Settings ......................................................................................................1 Operation Effect .................. 11........... 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 ......................6 Automatically Setting Dual-Plane ................................................ 10-1 10............. 9... 9................. 9.................1 M2000 System Backup Contents .........................................................7 Checking Running Status of NTP Service ......................... 11..........................5...................................................................7.........................................3 The Mode of M2000 System Backup and Restore ................................................... 11............4 Setting M2000 as Middle NTP Server .........5 Manually Setting Dual-Plane ............................... 9..............2................................. 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.. 10............4...... 11.....................2 Setting Auto Backup Time ...................... 9........................................4 Name of Backup Files ......................................................................................1 Overview of NTP Service Configuration .. 9............................................. 10...3 Function Setting ..2...........5 Storage Media of Backup File ..............2 Introduction to Dual-Plane ... 11. 9....................................................2 Operation Procedure ......................................................... 9.... 11.................................2 Introduction to NTP Service .............................................. 10-1 10-1 10-2 10-2 10-2 10-2 10-3 10-3 Chapter 11 Backup and Restoration ..................

..... 11........................7 Checking CPU Utilization ..........3....2.......................1 Overview of Routine Maintenance ....6............................. 11........1 Daily Maintenance Item List ...............2................................................................ 12. 12.......... 11............ 12...................2 Operation Procedure ...................................3.........5 Clearing Useless Files ................ 11.................... 11.....5 Manually Backing Up M2000 System........... 11....1 Monthly Maintenance Item List .........................1 Introduction to Manual Backup ......................... 11......................................1 Function Introduction ..............3.....3 Checking M2000 Server Time ........... 12...7.............8....................... 12-1 12...................... 11............ 12..............4....... 12........ 12.......................................................3 Checking Log Information .......... 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 ...........8............................2.............................................4 Monthly Maintenance .... 12......................................... 12......... 12....................4 Checking Solaris Error Log .................11..............2 Operation Procedure ....................5...........................................3 Weekly Maintenance .......................................2...... 11. 11.............. 12.....................................................7 Backing Up Operating System .........................8..........................................3 Carrying Out Manual Backup on Server .................. 12.............. 12........ 12.................................................................................................................... 12....9 Checking Service Status .....6 Restarting System.............2.......................................................................................................................... 12...2 Backing Up M2000 System ............ 12.........2.................................3.....................................................2 Operation Procedure ........................................8 Checking Number of Processes ....................................................6 Restoring M2000 System ....................1 Function Introduction ...8 Restoring Operating System .....................................................................................................2. 11.......2...............................................................7...5..........3................5 Checking Database Status .............. 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 ...........8.................8..................................8.........2 Daily Maintenance ........................................................................2 Carrying Out Manual Backup on Client ............2..3 Checking Server Hardware ..................5 Modifying System File and File System Information .......4 Finding core Files ...................1 Function Introduction .................. 11..............3 Restoring Tape Information ...........6........................................ 11.......................................... 11............................8........................................... 11.....4 Setting Up Equipment Tree and Boot Block .......... 12............................................4...........2 Checking Power Supply ......... 11......................................5...... 12.... 12.........1 Weekly Maintenance Item List .....4..........6 Checking Hard Disk Space ...................... 11.......................2 Checking Alarm Information.........7 Encapsulating Disk Using Volume Manager ..........................

..3 Fault Clearance ..........................6.....1 Overview of Troubleshooting Procedure ..........3...........6 M2000 Services Starting or Stopping Failure ..2 Operation Procedure ........ 14-1 14-1 14-1 14-1 14-1 14-1 14-2 Chapter 15 Command Guide ...................2...............3 Fault Clearance ..........................................................................................2........1 Symptom .................................................................................... 13.......2 Emergency Maintenance for M2000 Server ...................................................2 Fault Analysis .......................................................................................... 13.... 13.........................................2 Prerequisites of Using Commands ...............................................................4 Fault Clearance ......................................2 Operation Procedure .......... 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 ......1 Function Introduction .............2........2 Fault Analysis ............. 13......... 13................2...1 Symptom ............3........................3 Fault Clearance ................... 14.............................. 13....sh ...........5....2.........................................3...............................................3 Fault Location ................ 13................4.............................................................................................................................................3...........................2 Information Collection ................. 15.............1 Overview of Troubleshooting . 13........................ 13.... 12-4 Chapter 13 Troubleshooting ........................... 15... 14......1 Overview of Emergency Maintenance ........ 13.....................................................................................3 svc_profile.........................4....... 15...........4.... 13.6.3......................1 Symptom ................2 Troubleshooting Procedure ................................................................................................................... 13.........1 Symptom ................................... 13.......................................... 13.................................... 13. 13................5.1 Overview of Command Guide ............. 15......................................................... 13.............................................................................................................................................2........................5...................6......................................... 13-1 13...................... 14............................... 15........... 15-1 15.................................... 14-1 14....................... 13.............2 Fault Analysis .........4.................... 14..............................2 Introduction to Commands ..... 13........1 Function of svc_profile...................1 Path of Commands ...........2...............................1 Function Introduction ............................................................................................................ 15-1 15-1 15-1 15-1 15-1 15-1 ........................sh ...12....................................... 14......2 Fault Analysis .........5 Abnormal Service Termination ..... 13........................................................................................3 Auto Shutdown of Operating System ........3 Fault Clearance .....................3 Emergency Maintenance for M2000 Client .......................4 Checking Auxiliary Devices of Server ............................................................................... 14.....2.................4 Abnormal Service Restart .............................................3. 13..............................................................

. 15...................................... 16.... 15..9..............................................................................................3 Operation Guide....3 Running svc_profile.................11............................................................................... 15...................................... 15.. 16... 15......5 stop_svc ..........................2............................................. 15............................4. 16-1 16........................2.....1 Command Function ........... 16..........11.....4 Forbidding Using Diagnostic Tool ..... 15................................................................................................... 15.........10............................................................................2 Example ......... 16.......... 15......12......................9...12 svc_lockdump ............... 15............................................ 15..................................................................................................1 Command Function ................................2 Example .....................1 Command Function .........7.................................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 ............................... 15..................................................................................................................................................... 15.... 15................................................................... 16..............................3............................8......... 16...................1 Overview of Tool Guide .............................2 Example ........3........................................2 Example ..........................................3.................... 15...................................................................................................................... 16..........4 start_svc .......... 16.............................................1 Function ....................................................................................................................................................................................................3.................. 15..........12.........................................1 Function ........5................ 15.............................1 Command Function ............. 15... 15...................................................... 15.................................. 16-1 16-1 16-1 16-1 16-2 16-2 16-2 16-3 16-5 16-5 ......1 Command Function ............................................................................................................................... 15..................................................................10........... 15............................2 Example .................. 15.15................8..............................3 Abnormal Handling .................................................1 Command Function ...4.................................2 Starting method ...6 kill_svc ...10 svc_adm-cmd reload .........................................................................................2 Example .............7...2 Running Diagnostic Tool .1 Command Function .............................1 Command Function .6........................ 15..........8 svc_ps .....................................2 Tape Drive Management Tool .............................3 M2000 Diagnostic Tooling ....................1 Command Function ....................................................................2.................................3.. 15................... 15......sh ...............................................................................................6.....9 top ..........................2 Example ...........................................3........................ 15..............2 Path of svc_profile............. 15.....sh ...................................................11 svc_stacks ..7 svc_adm-cmd status ............ 16.2 Example ..................................................5.......

.............. 17............................8..................................... 17......... 17-1 17.................................................................................................. 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 ....1 Question.............4.............................5..........2 Answer . 17...............................2................................... 17......... 17.....2 Answer .......................................... 16-10 16........7.......................6 Adding and Deleting Routes ........................................4 Performance Job Result Auto Export Tool ........................................................................4..........4 Modifying Solaris IP Address...................................................................1 Overview of FAQ ..........8.................................................1 Question.4... 17...............4 Stopping Auto Export Tool ........7 "/etc/rc2..............................2 Logging in as root though Telnet ................5........................................3................... 17.... 16-6 16......................1 Question...2 Answer ............... 16-10 Chapter 17 FAQ.. 17...... 16-8 16............. 17............................................................................................4...............................................................................................1 Question............................4.........5.4 Installing Tape Drive ..1 Function ........3 Logging in as root though FTP .............. 17.........................................................6..........5........5 IP Modification Tool ........8 Querying Hardware Configuration of Server ....... 17....................... 16-7 16...................................5.........................5 Modifying Sybase IP ... 16-8 16....... 17................................ 17................2 Answer .....................................................7 Modifying Host Name ..................................................6 Modifying Sybase Service IP and Port Number ...........................................5.............................. 17........................5...............4...........................5.............................. 16-8 16.................... Default Gateway and Subnet Mask .... 17............5 Setting Default Route ........................ 17..................5................... 16-5 16.....................3 Querying IP Settings ....d" in Solaris ........... 16-9 16. 16-5 16...........................2................. 16-7 16........................................4......................16................................................................................................................................................................................... 17.............................. 17. 16-8 16....................................2 Prerequisites .................................................... 16-9 16....5.............3 Running Auto Export Tool ...........8 Modifying Gateway ... Host name.......................2 Answer .......................................2 Answer ............... 16-10 16...............................9 Confirming Startup of Sybase ............................................. 17............................1 Function .............................................1 Question........................................................... 17..............................................................................6.......................................... 17..................................................................................................1 Question................................................................................................ 17....................5 Abnormal Handling .......................1 Question......................................7.............................................................. 16-5 16.............3............................2 Function Settings ................................................2 Answer .....................

......................... ....2 Answer ............... 1 Index ................................................................11 Stopping Sybase ............................1 Question...............11........................................... 17............................ 17.......1 Question ...................... 17-5 17-5 17-5 17-5 17-5 17-6 17-6 17-6 Appendix Acronyms and Abbreviations .... 17.....2 Answer ......... 17...........................10.1 Question ...........................11...... 17...............................................................................................................9........................................................17....10................................................................................ 17..................................2 Answer ......................................................................................................................................................................10 Starting Sybase ..................................................9.. 17................................

HUAWEI iManager M2000 Mobile Element Management System Administrator Guide V200R002 .

. Shenzhen.20 Product Version V200R002 BOM 31014659 Huawei Technologies Co.com . Longgang District. Bantian. Huawei Technologies Co. P.huawei.. Ltd. provides customers with comprehensive technical support and service. R.iManager M2000 Mobile Element Management System Administrator Guide Manual Version T2-030159-20041010-C-2.. Huawei Technologies Co. Please feel free to contact our local office or company headquarters.com Email: support@huawei. Ltd. China Postal Code: 518129 Website: http://www. Address: Administration Building.. Ltd.

C&C08 iNET. iMUSE. U-SYS. NETENGINE. infoX. Airbridge. DOPRA. C&C08.Copyright © 2004 Huawei Technologies Co. Inmedia. Ltd. iTELLIN. M900/M1800. Quidview. . InfoLink. All other trademarks mentioned in this manual are the property of their respective holders. SYNLOCK. HUAWEI OptiX. TopEng are trademarks of Huawei Technologies Co. HUAWEI. and recommendations in this manual do not constitute the warranty of any kind. HONET. information. Tellwin. SmartAX. ViewPoint. Musa. OptiX. but all statements. Notice The information in this manual is subject to change without notice. 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. iSite. ETS. Ltd. Radium. EAST8000.. Quidway. OpenEye. Lansway. DMC.. . TELESIGHT. VRP. INtess. Ltd. TELLIN.. Trademarks . Netkey. express or implied. Every effort has been made in the preparation of this manual to ensure accuracy of the contents.

Summary of Updates This section provides the update history of this manual and introduces the contents of subsequent updates. Notes Initial field trial release . 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.20 Updates of Contents None. Manual Version T2-030159-20041010-C-2.

the related concepts and detailed operation procedures of the system administration 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 5 Server Performance Monitor introduces the concepts related to server performance monitor and provides the details of the major server performance monitor tasks. troubleshooting and emergency maintenance. as well as the routine maintenance.About This Manual Release Notes This manual applies to iManager M2000 Mobile Element Management System V200R002. Chapter 4 Log Management introduces the concepts related to log management and provides the details of the major log management tasks. contents and the requirement of an administrator. . Chapter 7 Database Management introduces the concepts related to database management and provides the details of the major database management tasks. Chapter 3 User Management introduces the concepts related to user management and provides the details of the major user management 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 2 Server Parameter Settings introduces the setting and modification of server parameters. Organization This manual provides the system administration tasks. This manual consists of 17 chapters and one appendix: Chapter 1 Overview of Administrator Guide introduces the objective. 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 17 FAQ introduces the frequently asked question and the solutions concerning operating system and database. General conventions Convention Description Arial Normal paragraphs are in Arial. Chapter 15 Command Guide introduces functions and usage of the important commands. Chapter 12 Routine Maintenance provides the maintenance items for M2000 and the operation guide. Notes and Tips are in Arial Narrow. Chapter 16 Tool Guide introduces the functions and usage of the M2000 tools. Arial Narrow Warnings. 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 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. Courier New Terminal Display is in Courier New.Chapter 10 NTP Service Configuration introduces the concepts related to NTP service configuration and provides the details of the major NTP service configuration tasks. 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 z M2000 administrator z Network administrator Conventions The manual uses the following conventions: I. Boldface Headings are in Boldface. Cautions.

. } Alternative items are grouped in braces and separated by vertical bars. ] Optional alternative items are grouped in square brackets and separated by vertical bars.. <Ctrl+Alt+A> means the three keys should be pressed concurrently. Mouse operation Action Click Description Press the left button or right button quickly (left button by default).. One or none is selected. A minimum of one or a maximum of all can be selected. For example. [File/Create/Folder]. GUI conventions Convention Description <> Button names are inside angle brackets. Key2> Press the keys in turn. / Multi-level menus are separated by forward slashes. <Enter>.II. Many or none can be selected. italic Command arguments are in italic. A> means the two keys should be pressed in turn. V. data table and field names are inside square brackets. menu items.. <Key1+Key2> Press the keys concurrently. . III.. <Tab>. ] * Optional alternative items are grouped in square brackets and separated by vertical bars.. For example. <Key1. One is selected. For example. For example. or <A>. [] Window names. IV. <Alt.. [ x | y | . } * Alternative items are grouped in braces and separated by vertical bars. For example. { x | y | . [ x | y | . <Backspace>. Keyboard operation Format Description <Key> Press the key with the key name inside angle brackets. [] Items (keywords or arguments) in square brackets [ ] are optional. Command conventions Convention Description Boldface The keywords of a command line are in Boldface. pop up the [New User] window. For example. click the <OK> button.. { x | y | .

Tip. Symbols Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. Note.Double Click Press the left button twice continuously and quickly. They are defined as follows: Caution. . Knowhow. Thought: Means a complementary description. Danger: Means reader be extremely careful during the operation. Comment. VI. Drag Press and hold the left button and drag it to a certain position. Warning.

.3..........................................3..............................................................................................4..........2 Maintenance Items............................................. 1-3 Chapter 2 Server Parameter Settings.................................2 Operation Procedure..............3..........3 Commands and Tools ...................3............................................................................................................. 3-3 3.................................................2................ 2-5 Chapter 3 User Management................................... 3-4 i ... 2-2 2................................................................................4........ 3-3 3.... 3-4 3.............................1 Administrative Tasks ............................................4 Modifying Password of Operating System User .............. 3-4 3.......................................1 Operation Effect ..................... 1-2 1........ 1-1 1.........1 Operation Effect .........................................................................3.................................... 1-1 1...................................................4 FAQ ......................................................................................................................................... 3-3 3.........................................................................3...................................... 2-4 2............................................................................5.................2 Operation Procedure........................................................2 Modifying Server Time........................ 3-1 3.......................................4 Modifying Server IP Address ................................................................3.........................2 Operation Procedure.........................2...........................2.........2.................2 Operation Procedure................... 2-3 2............. 1-2 1..................................3 Organization of This Guide .....2 Modifying Password of root.......... 3-1 3...................Administrator Guide iManager M2000 Mobile Element Management System Table of Contents Table of Contents Table of Contents ......2 Operating System User Accounts and the Authority................................................................... 2-1 2....................... i Chapter 1 Overview of Administrator Guide ........................................................... 2-2 2........................................................................................... 3-1 3......................................................................................................... 2-1 2............................................... 3-1 3...............................1 Objective .....................................................3 Modifying Host name of Server ...............................5 Setting Parameters of Server with Multiple IPs ............ 2-1 2............................................................1 Overview of Server Parameter Settings ............ 2-1 2..........2................2 Introduction to User Account .. 3-3 3.... 3-1 3.................. 2-4 2.........................................................2 Requirements for Administrator ............................................................... 1-2 1........................................................................................................................................................................4...............................................5....1 Operation Effect ..................... 3-3 3....................................3.........1 Operation Effect ...........................................................................1 Operation Effect .......1 Operation Effect ......................................... 2-3 2.......................................................... 2-1 2.4...... 1-2 1.................................................................................... 2-3 2..................................................1 Overview of User Management ................................................................................................................1 Types of User Account...............................3 Creating Operating System User...............................................3 Database User Account and the Authority...................... 2-2 2..................2.2 Operation Procedure........................ 1-1 1..............................................................................................................4 M2000 User Accounts and the Authority .

............. 4-3 4............................................. 5-2 5.............5 Modifying Password of ftpuser .. 4-3 4.......................................................................................................2...................................................................1 Operation Effect ...5 Trace log ....4 Browsing System Log ...................................2 Introduction to Log .2 Operation Procedure................................4.......................... 3-6 3...................... 3-6 3...........................5.. 5-1 5......................................................................... 3-4 3.4........................................................................... 3-7 Chapter 4 Log Management .............. 3-6 3.......................2 Operation Procedure........ 4-1 4.......................................2 Operation Procedure................................................................................................................ 5-1 5.................. 4-1 4...............................3 NE Log ....................... 4-3 4.....................5 Checking Solaris Error Log.......................1 Operation Effect .............................................. 5-1 5......................................................................................................2............................................................................................................2 Operation Procedure................................................................................................................4.........2 Operation Procedure............. 3-6 3..3................................ 5-1 5....... 5-1 5...........4.................................................................Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 3.........................................................1 Operation Effect ...........................................1 Overview of Log Management.. 4-1 4........................................................................................ 5-2 ii .............. 4-3 Chapter 5 Server Performance Monitor ...... 4-2 4...................................................................................................................................................................................... 3-5 3.......................................................... 3-6 3.................................................3 Modifying Password of dbuser .............5...........................................6.................................................................................... 4-1 4.............................1 Operation Effect .......................................................................1 Operation Effect ................ 4-1 4......2............................................ 3-4 3......................................................3 Setting the Threshold of Server Status Alarm ............................................................................2.........1 Function.........2 Operation Procedure.2 Operation Procedure........... 3-6 3..............6...................................................................................4 Querying System Performance................................................................................................ 4-3 4...............................................................................................8 Monitoring M2000 Users......................8......................... 3-5 3..........................................4 Modifying Password of omcuser ................................... 3-4 3....................2 Operation Procedure...................................................................................................................1 Operation Effect ..............................................................2 Operation Procedure..3....2 Querying Server Status through Client...............................................3................ 3-6 3...............................................................................................................................7 Creating M2000 User Account.........8.....2...............5......................................................................... 4-3 4........1 Operation Effect ........ 4-1 4.......................................... 4-3 4...................................................... 3-5 3.............2..................................................7.................................... 5-2 5...........................................4................................3 Browsing User Log ...........1 Overview of Server Performance Monitor .....................................................5 Modifying Password of Database User ...............................................5..............3....2................................................... 5-2 5....................................................... 4-3 4......6 Creating M2000 User Group.............................................1 Function.......2 User Log.... 4-3 4.................................................................... 3-6 3.....7...............1 Operation Effect .....................................................................................................1 Types of Logs.................... 5-2 5................ 4-2 4..............4.................4 System Log ...........................................................

.................................................................. 6-1 6................................ 5-3 5.....................................1 Overview of Database Management ....... 6-4 6.....................................................................6 partition_agent.........................................................................................2..................7 audit_agent...............2.............................................................................2..........................................2 Operation Procedure......... 6-5 6.... 6-2 6..... 6-3 6..........................2 SystemConfigurator ........... 6-1 6.................................................................................. 6-9 Chapter 7 Database Management............2..............................................................................................................................................................................5...................................................... 6-3 6.............. 6-4 6........................................................................................................................................2 Operation Procedure..........................1 Operation Effect .18 proxy_agent........................................................................................................................................................................ 6-6 6............4 Querying Service Status ..2...........2.......................................................................................................................................................4......5 Starting M2000 Services......10 med_agent ..............................1 Overview of M2000 Process and Service Management........2 Operation Procedure....................................................................................................................................1 Operation Effect .......................................................... 6-1 6............................... 5-3 5...................................................... 7-1 7.......................... 7-1 7..............................4................5......................... 6-1 6.................2.................. 6-8 6.........................2 Introduction to M2000 Processes and Services .......................2..................9 sm_agent....................4......2.........................................2.................................................................................................................2..... 7-1 7.........................................................................................................................................2...........................................4 em_agent ................................................................................................ 5-3 5...... 6-8 6.....................................1 Overview of Database................................ 6-6 6....................15 cmserver_agent....... 6-6 6.................... 6-9 6............................... 6-6 6. 6-5 6.....................................................................................................13 manager_agent .... 6-4 6.............. 6-6 6....... 6-6 6.............................. 6-5 6..........19 notify_agent..........................6................................................................................. 5-4 Chapter 6 M2000 Process and Service Management ...........5 monitor_agent ...................................................1 Operation Effect ......2.3.......14 pm_agent ........................................................................................2 Operation Procedure................................................................................1 Operation Effect ...................................................................16 swm_agent ................................................Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 5..........3 Querying Number of M2000 Processes .................................1 Overview to Processes and Services .........................................2...... 6-1 6...............................................5..........2..............5.........2.......2 Operation Procedure.......................................... 7-1 iii ................................................ 6-6 6..........2.....................................................2.........12 ifms_agent........................................................................11 ts_agent...........2 Operation Procedure..2 Introduction to Database.. 6-6 6......................................................2.......1 Operation Effect ..............2..................................6..........................3........5 Adjusting System Performance .....................17 fmnotify_agent........ 6-2 6....... 6-3 6....................................................6 Stopping M2000 Services.. 6-1 6......................... 6-4 6...................................................... 6-8 6............... 6-5 6..8 mo_agent ........................................................................................................ 6-4 6.......................................................................................................................................................3 sac_agent......... 6-9 6...........................

..............................4.........................................3............Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 7............................................1 Overview of Disk Space Management .............................................................................................. 9-1 9............. 7-6 7.............3 Client File System ................................... 7-5 7..........3............................. 7-6 7.........................1 Operation Effect ............... 8-3 Chapter 9 Dual-Plane Configuration......................................................... 8-2 8..............................................5 sysmdb ................. 7-8 Chapter 8 Disk Space Management............................................................................................................ 7-5 7..................... 8-3 8................................................................ 8-3 8......................6.......... 7-8 7.......... 9-2 9....9........... 8-1 8.................................................................................9 Clearing Database .............6 Setting Auto Displacing for Alarm Data .......................... 8-1 8..5..................2 Introduction to Dual-Plane ......................... 7-6 7.........................................................................................................................................................................................................................................................................................................................................................2 Server File System ...................................................... 8-1 8.......1 Operation Effect ....1 Overview of System Structure.....................1 Operation Effect ....2 omcdb....................................................................8......................... 8-2 8...... 7-4 7...........................................1 Operation Effect ......................................5 Manually Displacing User Log ................2......................................................................8..................2 Operation Procedure..................................................................................................................................4 pmdb ...........4 Manually Displacing Alarm Data................................................................................1 Operation Effect ............................ 7-4 7...................................................................... 9-1 9...... 9-2 iv .................................................................................7....................................3 Query Disk Space ............................7.1 Overview of Dual-Plane Configuration ...................1 Operation Effect .................................................................................................................3 Querying Database Status.......2 Operation Procedure....................................................................................... 9-1 9.......................................... 7-2 7...................................... 7-7 7............................4 Planning IP Data ......................... 7-7 7...........4.........................................................................2 Operation Procedure............... 7-5 7... 8-2 8........... 7-3 7.2.. 7-5 7............................................................................... 7-7 7........................................................................... 7-5 7................................................................................. 8-1 8...................4...... 7-2 7.2..9....................1 Operation Effect ...................................................................................................3 fmdb ...................................................................................2 Introduction to File System .............................................................2......4........... 7-7 7......................2 Operation Procedure.................................1 Operation Effect ......2..........................1 Operation Effect ...... 7-1 7..................................................................... 7-6 7..........................................3.......2 Operation Procedure.............................................................................................................. 7-7 7.......................8 Deleting Performance Task ..................................2 Operation Procedure....................................... 8-3 8.....3 Configuration Procedure of Dual-Plane ..................... 7-4 7...................................................................................................2...................................................................................2 Operation Procedure.......................................................................2 Operation Procedure......4 Clearing Disk Space ..............2 Operation Procedure................7 Setting Auto Displacing for User Log..........................................................3..... 7-7 7............................................................................6..............5......................2............... 7-8 7................................................................................................... 8-1 8..........................................

..............6 Starting NTP Service ...........................................................................................7 Checking Running Status of NTP Service................................... 11-3 11... 11-3 11......2 Setting Tape Drive Path .........................5 Manually Backing Up M2000 System .................................................... 10-2 10....... 10-2 10......7.............. 11-6 11................................................................2 Operation Procedure..8 Stopping NTP Service ........Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 9.................................................................................................................................... 11-6 11.............................................................................................................................................................................................. 11-3 11.... 11-2 11....................................................4 Automatically Backing Up M2000 System.................3 The Mode of M2000 System Backup and Restore ........................................1 Overview of Backup and Restoration ...... 9-4 9..................2........................................2 Operation Procedure................... 9-3 9........................................................... 11-4 11....... 11-1 11................................................................5.........................................6.............................................................................................................................................................................5.....................2 Introduction to NTP Service..................4 Setting M2000 as Middle NTP Server ...........7.1 Introduction to Manual Backup.4 Name of Backup Files ....................................................5............2 Introduction to Backup and Restoration ......................................................................................................................................................................................................................... 10-3 10...............................................2 Operation Procedure........................................................................................................7 Backing Up Operating System.....................5..............................................................5 Storage Media of Backup File ........................... 11-2 11............................................. 9-4 9...........................6 Restoring M2000 System ................5 Setting M2000 as NTP Client ..........................6..................................................1 Operation Effect ................2 M2000 System Backup and NE Data Backup ................................................. 11-5 11.................................................................................................. 9-2 9.................1 Introduction to Configuration File ..................................................3 Setting M2000 as Top NTP Server............................... 9-2 9........................................................... 11-5 11................1 M2000 System Backup Contents........................................................................................................ 11-5 11............ 11-1 11.....2 Setting Auto Backup Time.........2 Operation Procedure.......................................... 9-3 9................1 Function Introduction................ 10-2 10.......6 Automatically Setting Dual-Plane ................................. 11-4 11.2.............2 Carrying Out Manual Backup on Client...............6.....4........1 Introduction to Auto Backup ......................................... 10-1 10.................. 11-2 11............................................1 Operation Effect ........3 Abnormal Handling......... 11-1 11..................................................3......................................................... 11-6 11........... 11-6 11.........5 Manually Setting Dual-Plane ................................................................. 11-3 11....... 11-1 11........................................................................... 11-1 11. 10-1 10...................................5......................................................................................... 9-4 Chapter 10 NTP Service Configuration ........2..... 9-3 9.................................... 10-2 10...............2............................. 9-4 9.......7 Verifying Dual-Plane Settings ...1 Operation Effect ...........................6..............3 Carrying Out Manual Backup on Server .................... 11-7 v ............................................................... 11-5 11....................................................................1 Overview of NTP Service Configuration ....................3................. 9-2 9..2..................... 10-1 10................3 Setting Backup Media ...........7............................... 10-3 Chapter 11 Backup and Restoration ................................3 Function Setting ..........................3..........4.............

............2.........................................2.......................1 Weekly Maintenance Item List ...............................3 Weekly Maintenance .............2 Daily Maintenance ............ 12-2 12.. 13-1 13........................................................................1 Overview of Troubleshooting Procedure.8......................................2 Operation Procedure...... 12-4 12...4.............. 12-4 12...........3 Auto Shutdown of Operating System .......................7....3..........................8.............................................................................................................................................. 13-2 13..........................................................................................................................................8 Checking Number of Processes....................................3................. 11-9 11......................................... 12-1 12............................... 13-2 13....................... 13-1 13...........................2 Operation Procedure...................4 Checking Auxiliary Devices of Server ..................................................... 11-7 11......................................................................................... 11-12 Chapter 12 Routine Maintenance..............................................2.....8...............2.. 13-1 13.............................5 Checking Database Status....... 13-1 13........................... 13-1 13...............................4.............2................................................................. 12-4 12...................................................................................................................................... 12-3 12.............................................1 Monthly Maintenance Item List ..................................................2 Checking Alarm Information...... 11-10 11...................3.................................4 Fault Clearance ...2....3 Checking Server Hardware ........................................................................................................................................................2..............................3......... 12-2 12.....8 Restoring Operating System................4......................................4 Checking Solaris Error Log .........................................................................4.........2 Backing Up M2000 System...3 Checking Log Information ...............2 Troubleshooting Procedure ..5 Modifying System File and File System Information ............................. 12-1 12.............................................. 12-4 12...........................................7 Encapsulating Disk Using Volume Manager.....1 Function Introduction.Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 11...................................................4 Finding core Files .... 12-1 12................................................... 13-2 vi .......................................2 Checking Power Supply .......................................................................1 Symptom .........6 Restarting System ..................1 Daily Maintenance Item List ....6 Checking Hard Disk Space . 11-9 11.. 13-1 13......................................................................... 12-1 12.....8...................... 11-9 11....................................................1 Overview of Troubleshooting ........................................9 Checking Service Status ....................2.................................................... 12-3 12.........................................4 Monthly Maintenance...2 Information Collection .......................................... 11-7 11.............................2.3 Checking M2000 Server Time..3 Fault Location................................ 12-2 12...................... 11-11 11...........3........... 11-9 11..................................................................................2..... 12-2 12......7..4 Setting Up Equipment Tree and Boot Block ....................................................................... 12-4 Chapter 13 Troubleshooting ............................................................ 12-1 12......2......... 12-4 12..................3 Restoring Tape Information...................................................................5 Clearing Useless Files .................................................. 11-12 11............................................................................8...................................8............3.........8........................................................7 Checking CPU Utilization ................ 12-3 12........................................................ 12-3 12.. 12-3 12..................................................................................................................................2.............. 12-2 12.........................................2................................... 12-4 12...................... 12-2 12.................1 Function Introduction......................1 Overview of Routine Maintenance...................

.......... 14-2 Chapter 15 Command Guide ..6......2........4..5..........................................................................2..................2 Operation Procedure... 15-1 15.........................................3............................................... 14-1 14....1 Overview of Command Guide........................................................... 14-1 14..............................2 Example ................ 15-3 15..............................2 Fault Analysis ................................................ 15-1 15.......2 Example ..........3..................1 Symptom ......2.........3 Fault Clearance ............Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 13........ 13-3 13...3............................................................ 13-2 13........................6................................................ 15-1 15...........................................................................3 Emergency Maintenance for M2000 Client .................................................................................................... 14-1 14..................3 svc_profile.......5.......... 15-1 15............. 15-3 15................................................................................................... 13-5 13.... 14-1 14................5........ 13-3 13.................................................... 14-1 14.................4 Abnormal Service Restart...........................................................5................................ 15-3 vii .............................................................1 Function of svc_profile.......................1 Symptom .....................4 start_svc............................ 13-4 13........................................................................4..................... 13-3 13.............................................. 13-4 13...3..............................................................................................................2 Introduction to Commands................................................1 Path of Commands ..................... 15-3 15.................................................................... 15-3 15..................... 15-1 15.........sh .. 15-2 15.........................5 Abnormal Service Termination ............. 13-4 13......................6.................. 13-3 13.......................................................................................3.............................2 Fault Analysis .................................................. 15-1 15............................................................................................................ 15-3 15............................................................... 13-5 Chapter 14 Emergency Maintenance.............................................. 14-1 14................................................................................................................................................................................................3.................................................................................................................... 15-3 15.............................................................sh........2 Example .......sh.............................................. 15-1 15.......1 Command Function.........................................................................................................................................................................6 kill_svc .................1 Function Introduction...............................................2 Emergency Maintenance for M2000 Server ....................................... 15-3 15........................sh ...................... 13-3 13..............................................2 Prerequisites of Using Commands........2 Operation Procedure............................. 14-1 14..........................................5 stop_svc............................................................3 Fault Clearance .................................................................................................1 Command Function.............................................................2 Path of svc_profile......................... 15-1 15.............1 Command Function....................2 Fault Analysis ................................................... 15-1 15................................. 15-2 15...4.. 13-5 13...........7 svc_adm –cmd status ...........................................................2........................................4...........................3 Running svc_profile........................................6.............................................................6................................. 13-5 13.............................................................1 Function Introduction.........1 Command Function.......................3............4.......7.............5.........................................3 Fault Clearance ......................................................................................................... 13-4 13.............................3 Fault Clearance ......1 Overview of Emergency Maintenance.6 M2000 Services Starting or Stopping Failure ..................................................1 Symptom .................................2 Fault Analysis ...... 15-2 15.......................................................

...........................................................................2 Function Settings ................................... 16-8 16...........................................2 Example ............. 15-4 15............................. 16-1 16......8 svc_ps............................................................................................. 16-8 16.2......................... 15-3 15.........1 Function..........................10.......................... 16-7 16...........................................................4 Stopping Auto Export Tool ..............9....................................12.............................................5..................................................................1 Overview of Tool Guide ..........................................................3............................................................................................................................................ 16-10 viii ...... 16-9 16............. 16-8 16..........................10............................................................9 top ...................4 Forbidding Using Diagnostic Tool ......................... 15-5 15.................................4.......... 16-2 16................11.........................11 svc_stacks ..........5 IP Modification Tool ........................................1 Command Function...1 Function........................2 Example ......5.......... 15-6 15..............................4........................................................................................................8.................................................................................................................................................................................................... 16-10 16.......................... 16-9 16....... 15-6 15. Default Gateway and Subnet Mask..................................................7................4.3 Querying IP Settings .................................. 16-5 16..5............................................................................... 16-6 16........1 Command Function................................... 15-4 15.......................................................................................................................................................................................... 15-4 15............................ 15-4 15.......................2 Starting method ....................................................5 Abnormal Handling...............4....................................................................................2 Example .Administrator Guide iManager M2000 Mobile Element Management System Table of Contents 15.........................................................................................5 Modifying Sybase IP ..............................7 Modifying Host Name.....11.........................2..................................3......................................................................................................... 16-7 16. 16-1 16..................................................4........................................10 svc_adm –cmd reload.....9........4 Performance Job Result Auto Export Tool ...3 Running Auto Export Tool ............... 15-4 15........................ 15-6 Chapter 16 Tool Guide ............................................ 16-10 16.....5....................8 Modifying Gateway.....3 M2000 Diagnostic Tooling .........2 Running Diagnostic Tool ..................8.................................3....3...............................................................2 Example ....................................... 16-1 16........................................1 Command Function..............6 Modifying Sybase Service IP and Port Number................................................................................................................................................................... 16-1 16...........................5........................... 16-5 16.......2 Tape Drive Management Tool ..................................2 Example .............................................................................................. 16-8 16.......................................5....................................3 Abnormal Handling........12 svc_lockdump .... 15-5 15................................................................ 15-5 15........................................ 15-5 15........................................ 15-4 15... 16-5 16...............12......... 15-5 15........................ 16-3 16.........1 Command Function........................................................1 Command Function........................................................................................................3 Operation Guide ................................................ 16-5 16....... 15-5 15.................4 Modifying Solaris IP Address..2 Prerequisites ...2................................. 16-1 16... 16-5 16....................... 16-2 16.........................................2 Example ........................................................................................1 Function........................ 16-2 16....5......................................1 Function..................................................................5.................................................... Host name..

...............................................9.................................................................... 17-4 17....................1 Question ..11... 17-4 17...........d" in Solaris.............................................................................................1 Question .......................11..................................... 17-5 17................................... 17-1 17. 17-6 17.................1 Question ....................................................................9 Confirming Startup of Sybase..................10 Starting Sybase ...........5......5 Setting Default Route......2 Answer ............2 Answer .................................................6............................ 17-2 17................................................... 17-3 17..................8...............1 Question . 17-2 17......3..2 Answer ......... 17-5 17......................................................1 Question ....................................................9.....5........................2 Answer .........................................................................................................................................................................................................2 Answer ...............................3...................................................................................................................................................................................................................................... 17-3 17...4 Installing Tape Drive ...................................2 Answer ....................................................... 17-1 17................... 17-1 17...........................................7.......................................................................................................................... 17-3 17........... 17-4 17..................................2.... 17-3 17........................................6 Adding and Deleting Routes ...........................................................................................10.............................. 17-1 17........11 Stopping Sybase................................... 17-6 Appendix Acronyms and Abbreviations ...................1 Question ..................................6......................................................2 Answer .....................................................8.............................................................................. 17-6 17.................................1 Question ...................................8 Querying Hardware Configuration of Server ... 17-3 17...........................1 Question ............................................................................................................................................................................. 17-4 17......................7.................................. 17-5 17..............................................................................................................................7 "/etc/rc2.2 Logging in as root though Telnet .................. i-1 ix .............................................................................................................. 17-3 17....Administrator Guide iManager M2000 Mobile Element Management System Table of Contents Chapter 17 FAQ ..............................3 Logging in as root though FTP ....10...................................................................................... 17-5 17............................ 17-1 17..........................2 Answer .................. 17-1 17.....2 Answer .................................................................. 17-5 17...................................................................................................................................1 Question ......................................................................................................................................................... 17-4 17............... 17-1 17.............................................................................................................................2 Answer ............. 17-5 17............................................................................... 17-2 17...............4............................................................. 17-4 17.............................................4..........................................1 Overview of FAQ ..........2.. 17-1 17.......... 1 Index ....................................................................1 Question .................

database management. NE software upgrade and entire network data backup and restoring. including network performance monitoring. 1. This manual provides the related concepts and detailed operation procedures of the operation tasks. and Client/Server z M2000 system and its functions Refer to iManager M2000 Mobile Element Management System Description and this guide. TCP/IP. NE configuration. This guide focuses on M2000 single-server system administration. system backup and restoration. 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.2 Requirements for Administrator The system administrator of M2000 must be familiar with the following items: z Solaris and Windows operating systems z Sybase database z Knowledge of computer networks such as Ethernet. user management.Administrator Guide iManager M2000 Mobile Element Management System Chapter 1 Overview of Administrator Guide Chapter 1 Overview of Administrator Guide 1. z iManager M2000 Mobile Element Management System Administrator Guide The intended reader of this guide is system administrator. alarm query. This manual focuses on operations and maintenance of the mobile networks through M2000. z iManager M2000 Mobile Element Management System Operation Manual The intended reader of this manual is M2000 operator.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. and general fault handling. including Server status monitoring. disk space management. z Routine maintenance and troubleshooting on M2000 1-1 . This guide provides the related concepts and detailed operation procedures of the system administration tasks.

refer to iManager M2000 Mobile Element Management System Operation Manual.2 Maintenance Items This guide also introduces the following maintenance items based on administration tasks: z Routine maintenance z Troubleshooting z Emergency maintenance This part is concerning on M2000. The first section of each chapter describes the structure of the chapter. For operation and maintenance of NE. and NE’s corresponding manual. 1. 1.3 Commands and Tools This guide also introduces M2000 commands and tools in system administration: z Command guide z Tool guide 1-2 .3. 1. may not be present. refer to Solaris system administrator manual or Sybase system administrator manual.3.Administrator Guide iManager M2000 Mobile Element Management System Refer to "Chapter 12 Chapter 1 Overview of Administrator Guide Routine Maintenance".3 Organization of This Guide 1.1 Administrative Tasks This guide introduces the following administrative tasks and the related concepts: z Server parameter setting z User management z Log management z Server performance monitor z M2000 process and service management z Database management z Disk space management z Dual-plane configuration z NTP service configuration z Backup and restoration Each of the above tasks is explained in an individual chapter. "Chapter 13 Troubleshooting" and "Chapter 14 Emergency Maintenance" in this guide.3. and so. the second section introduces the task concepts and the third section explains the task details. For the maintenance and fault handling of Solaris operating system or Sybase database. The second section may not be applicable for a few chapters.

1-3 .4 FAQ This guide also introduces the frequently asked question and the solutions concerning Solaris operating system and Sybase database.Administrator Guide iManager M2000 Mobile Element Management System Chapter 1 Overview of Administrator Guide 1.3.

It is necessary to stop M2000 services if you want to modify system time.2 Operation Procedure To modify the Server time. and thus M2000 can not process the performance data and alarm data of the managed NEs when M2000 services are not running. 2) Execute the following commands to stop M2000 services.2.1 Operation Effect System time modification during M2000 running will affect the system timer. When tempdb is full.2. # echo $TZ 2-1 . # 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. M2000 will get the data from NEs by using auto synchronization function and then process the data. 2. After M2000 services have been restarted.2 Modifying Server Time 2. Sybase cannot work and M2000 cannot run.1 Overview of Server Parameter Settings This chapter introduces the modifications and settings of the Server parameters. # stop_svc 3) Execute the following command to stop Sybase.Administrator Guide iManager M2000 Mobile Element Management System Chapter 2 Server Parameter Settings Chapter 2 Server Parameter Settings 2. thus disabling the timed cleaning of the database tempdb. including: z Modifying Server time z Modifying host name of Server z Modifying IP address of Server z Setting multiple IPs for Server 2. perform the following operations on the Server: 1) Log in as root.

Sybase services and M2000 services will start automatically if M2000 Server software application has been installed. After M2000 services have been restarted. 2. the M2000 services will stop abnormally. perform the following operations on the Server: 1) Log in as root. modify the file "/etc/TIMEZONE" to change the value of "TZ" to the local time zone. For example.3. "TZ=PRC".Administrator Guide iManager M2000 Mobile Element Management System Chapter 2 Server Parameter Settings If the current time zone is incorrect. to set the system date and time to 2003-11-17 16:30:43. 5) Use the command "date" to set system date and time. execute the command: # date 111716302003. It is necessary to stop M2000 services if you want to modify the host name. For example. and thus M2000 can not process the performance data and alarm data of the managed NEs when M2000 services are not running. Otherwise. # init 6 When the operating system starts up.3 Modifying Host name of Server 2. # stop_svc 3) Execute the following command to stop sybase. # isql –SSYB –Usa –P<user sa password> 1> shutdown SYB_BACKUP 2> go 2-2 . 2) Execute the following commands to stop M2000 services.3.1 Operation Effect Do not modify the host name of the Server during M2000 running. M2000 will get the data from NEs by using auto synchronization function and then process the data.2 Operation Procedure To change the host name of the Server. Note: You can query the time zone information through "/usr/share/lib/zoneinfo". 2.43 Mon Nov 17 17:53:29 CST 2003 6) Execute the following command to restart the Server.

refer to "16. # init 6 When the operating system starts up. M2000 will get the data from NEs by using auto synchronization function and then process the data. 5) Edit the file "<M2000 installation directory>/etc/conf/tao.cfg". 2. Change the original host name to the new host name.4. to set the host name to "omc": # iptools -H omc Note: For the functions and usage of IP modification tool “iptools”. # stop_svc 3) Execute the following command to stop sybase. perform the following operations on the Server: 1) Log in as root. After M2000 services have been restarted. 2. the M2000 services will stop abnormally. Otherwise.4. # isql –SSYB –Usa –P<user sa password> 1> shutdown SYB_BACKUP 2-3 .Administrator Guide iManager M2000 Mobile Element Management System Chapter 2 Server Parameter Settings 1> shutdown SYB 2> go 4) Use the IP modification tool to modify the host name.4 Modifying Server IP Address 2. It is necessary to stop M2000 services if you want to modify the Server IP address. and M2000 can not process the performance data and alarm data of the managed NEs when M2000 services are not running.1 Operation Effect Do not modify the IP address of the Server during M2000 running. 6) Execute the following command to restart the Server. # iptools -H host-name For example. 2) Execute the following commands to stop M2000 services.5 IP Modification Tool". Sybase services and M2000 services will start automatically if M2000 Server software application has been installed.2 Operation Procedure To modify the IP address of the Server.

default gateway as 10.RUNNING. 2.161.255.IPv4> mtu 1500 index 2 inet 10.141.1. and all Server IPs of Sybase databases as 10.70.141. refer to "16.70.1 netmask ff000000 eri0: flags=1000843<UP.241 netmask fffffe00 broadcast 10.0 –G 10.141.161. # init 6 When the operating system starts up.70.54.70.45.1 –H host –d 6) Execute the following command to restart the Server. Otherwise.LOOPBACK.0.5 IP Modification Tool".IPv4> mtu 8232 index 1 inet 127. Note: For the functions and usage of IP modification tool.BROADCAST.70. # iptools –n eri0 –i 10. host name as host. it is necessary to specify one of them for M2000 services.RUNNING. # iptools {-n interface-name -i ip-address -m subnet-mask -G default -gateway -H host-name -d } For example.255 ether 0:3:ba:12:f9:12 5) Use the IP modification tool to modify the IP settings in Solaris and Sybase. # ifconfig –a lo0: flags=1000849<UP. 2-4 .141. M2000 will get the data from NEs by using auto synchronization function and then process the data.45.54. modify the IP of Solaris system as 10.141.5 Setting Parameters of Server with Multiple IPs 2. Sybase services and M2000 services will start automatically if M2000 Server software application has been installed.MULTICAST. It is necessary to stop M2000 services if you want to set multiple IPs.5.0. and thus M2000 can not process the performance data and alarm data of the managed NEs when M2000 services are not running. the Client cannot set up connection with the Server.Administrator Guide iManager M2000 Mobile Element Management System Chapter 2 Server Parameter Settings 2> go 1> shutdown SYB 2> go 4) Execute the following command to query the current IP settings. After M2000 services have been restarted.255.54 –m 255.1 Operation Effect When a Server has multiple IPs.MULTICAST.

add a note "#" before "10. # stop_svc 3) Execute the following command to stop sybase.121. "<M2000 installation directory>/etc/conf/tao.208 5) aries loghost Execute the following command to restart the Server. which is used to connect the Client and managed NEs.70.1 localhost #10.70. For example.200" and "10.200".161.5. perform the following operations on the Server: 1) Log in as root.0. among the two IP of the Server "10. Sybase services and M2000 services will start automatically if M2000 Server software application has been installed. "10. # isql –SSYB –Usa –P<user sa password> 1> shutdown SYB_BACKUP 2> go 1> shutdown SYB 2> go 4) Edit the file "/etc/hosts". then in the file "/etc/hosts". 2-5 .0.161.cfg" shows that the host name is "aries".208".Administrator Guide iManager M2000 Mobile Element Management System Chapter 2 Server Parameter Settings 2.121.5.5. # # Internet host table # 127. # init 6 When the operating system starts up.121.161.2 Operation Procedure To specify an IP for M2000 services. to make the host name correspond to an IP.208" is used to connect the Client.5.200 aries loghost 10. 2) Execute the following commands to stop M2000 services.70.

create other users. root The user root is with the highest authority to the system. and provides the details of the major user management tasks. omcuser. 3-1 . z User account of M2000: For M2000 Client operations. and ftpuser.2 Introduction to User Account 3. dbuser.Administrator Guide iManager M2000 Mobile Element Management System Chapter 3 User Management Chapter 3 User Management 3. the installer will create the user account inrpt and the user group inrpt automatically. Only the user root can install and uninstall the M2000 Server application software. you should have a user account of the operating system. You should also create a user group omcsysm. If you install Report System. and perform all the operation functions provided by the operating system.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. you should create three user accounts. z User account of database: For M2000 Server database operations. including type and authority of user account. and start and stop M2000 services.2. Apart from the default user accounts of the operating system Solaris.1 Overview of User Management This chapter introduces the concepts related to user management.2. I.2 Operating System User Accounts and the Authority To carry out operations on M2000 Server. including: z Creating operating system user account z Modifying operating system user account z Modifying database user password of database z Creating M2000 user group z Creating M2000 user account z Monitoring M2000 user 3. This user can control all resources. grant authorities to other users. 3.

You do not need to create inrpt manually. ftpuser The user ftpuser manages software of NEs and transfers software information to NEs. including querying system status. inrpt The user inrpt manages the Intelligent Report System. The attributes of the user are as follows: z Home directory: /export/home/sysm z The group that it belongs to: omcsysm z Login shell: /bin/bash V. the user inrpt will be created automatically. z Login shell: /bin/bash IV. The attributes of the user are as follows: z Home directory: /export/home/omc z The primary group that it belongs to: staff. The user omcuser also has the authority to access databases. The related attributes are as follows: z Home directory: /opt/sybase z The group that it belongs to: staff z Login shell: /bin/bash III. When the Intelligent Report System is installed. You should create omcuser before installing the M2000 Server application software. dbuser The user dbuser handles routine operation and maintenance of Sybase database. omcsysm. z The secondary group that it belongs to: sys. root. omcuser The user omcuser has the authority to perform routine operation and maintenance on the M2000 system. You should create ftpuser before installing M2000 Server application software. The user can neither install/uninstall M2000 Server application software. The attributes of the user are as follows: z Home directory: /opt/inrpt z The group that it belongs to: inrpt z Login shell: /usr/bin/csh 3-2 . The user can perform any operation such as interaction with the database through isql on the database. nor start/stop M2000 services.Administrator Guide iManager M2000 Mobile Element Management System Chapter 3 User Management II. You should create dbuser before installing Sybase. backing up and restoring system data.

For detailed description of M2000 user account and authority.2 Operation Procedure To create a Solaris operating system user account. It is necessary to set password for each user and the password update period. 3. For details on user creation. refer to iManager M2000 Mobile Element Management System Operation Manual. For creating method. and then click <OK> to close the dialog box. 2) Execute the following command to run the system administration tool: # admintool 3) In the dialog box [Admintool: Users]. For M2000 system. 4) In the dialog box [Admintool: Add User]. it is necessary to create three users manually: dbuser.3.3. set the new user properties. refer to "3. select the menu [Edit/Add].4 M2000 User Accounts and the Authority After the installation of M2000 Server and Client.3. It has the highest administration authorities of the database. 3-3 . you need a user account of Sybase. 3. refer to iManager M2000 Mobile Element Management System Installation Manual. perform the following operations on the Server: 1) Log in as root.2. the user information will be recorded in Solaris system file. omcuser and ftpuser.Administrator Guide iManager M2000 Mobile Element Management System Chapter 3 User Management 3. 3.3 Creating Operating System User 3. "admin" and "administrator" have all operation authorities to all NEs.1 Operation Effect After an operating system Solaris user account is created.2 Operation Procedure".3 Database User Account and the Authority To use M2000 Server database Sybase. Before the installation of Sybase and M2000 Server software.2. the user "admin" and the user group "administrator" will be created. The user sa is the default user account of Sybase. only the user sa is necessary.

2) Execute the following command to modify the password of "omcuser" # passwd omcuser New password: Re-enter new password: passwd (SYSTEM): passwd successfully changed for omcuser 3. 2) Execute the following command to modify the password of "dbuser": # passwd dbuser New password: Re-enter new password: passwd (SYSTEM): passwd successfully changed for dbuser 3.4.4.4 Modifying Password of omcuser 1) Log in as root.3 Modifying Password of dbuser 1) Log in as root.4 Modifying Password of Operating System User 3.Administrator Guide iManager M2000 Mobile Element Management System Chapter 3 User Management 3.1 Operation Effect It is necessary to stop the M2000 services to modify user password of "ftpuser".4. 3. "omcuser" and other users will not affect the running of M2000. The modification of passwords of "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.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: Re-enter new password: passwd (SYSTEM): passwd successfully changed for ftpuser 3-4 .2 Modifying Password of root 1) Log in as root. "dbuser".4.4.

select "Remote control parameters" to modify the password of ftpuser. # start_svc 3.2 Operation Procedure 1) Log in as root. # stop_svc 4) Run the M2000 parameter modification tool: # /opt/OMC/imap_setup. Figure 3-1 M2000 parameter setting 6) Execute the following command to start M2000 services.5.1 Operation Effect It is necessary to stop M2000 services to modify the password of the user sa.5.5 Modifying Password of Database User 3. 3.sh 5) In the dialog box shown in Figure 3-1. 3-5 .Administrator Guide iManager M2000 Mobile Element Management System 3) Chapter 3 User Management Execute the following command to stop the M2000 services.

6. For details. refer to iManager M2000 Mobile Element Management System Operation Manual. <new password> 2>go 4) Run the M2000 parameter modification tool: # /opt/OMC/imap_setup. 6) Execute the following command to start M2000 services.2 Operation Procedure Carry out the operations on M2000 Client. 3.7.1 Operation Effect After the creation of M2000 user group. # start_svc 3.1 Operation Effect The operation of M2000 user monitoring uses few system resources and has no effect on the system.8 Monitoring M2000 Users 3.8. the M2000 system will record all information of this user.7. For details.6 Creating M2000 User Group 3. 3.sh 5) In the dialog box shown in Figure 3-1. # 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 >. 3. 3.1 Operation Effect After the creation of M2000 user account.7 Creating M2000 User Account 3. select "Database parameters" to modify the password of "sa". 3-6 . refer to iManager M2000 Mobile Element Management System Operation Manual.Administrator Guide iManager M2000 Mobile Element Management System 2) Chapter 3 User Management Execute the following command to stop M2000 services.2 Operation Procedure Carry out the operations on M2000 Client. the M2000 system will record all information of this user group.6.

8. For details. 3-7 .2 Operation Procedure Carry out the operations on M2000 Client.Administrator Guide iManager M2000 Mobile Element Management System Chapter 3 User Management 3. refer to iManager M2000 Mobile Element Management System Operation Manual.

including: z Browsing user log z Browsing system log z Checking Solaris error log 4. including log types and their corresponding contents. 4-1 . user name. Path The user log is stored in the database in M2000 Server. Contents The information in user log includes operation contents. terminal. Its information can be queried and dumped through Client. III. Function The user log records the operations of M2000 users. operation start/end time. Function The NE log records the operations on managed NEs.2. and provides the details of log management tasks. M2000 system administrator and operators can query the user log. operation objective and result.2 User Log I.3 NE Log I.1 Overview of Log Management This chapter introduces the concepts related to log management. user type. 4. II.1 Types of Logs M2000 system provides four types of logs: z User log z NE log z System log z trace log 4.2.Administrator Guide iManager M2000 Mobile Element Management System Chapter 4 Log Management Chapter 4 Log Management 4.2 Introduction to Log 4. M2000 system administrator and operators can query the NE log.2.

iMAP.root. 4.trace.log.tar.tar.Administrator Guide iManager M2000 Mobile Element Management System Chapter 4 Log Management II. Path The trace log is stored in "/export/home/omc/var/logs" in M2000 Server.4 System Log I.gz.root. module identification and record time.trace. The file names are iMAP. NE type and name.root. iMAP. II.gz.1 and iMAP.root. III. The information is then written into the previous file.2.1 and iMAP. When one trace file is full. Path The NE log is generated on NEs. The information header includes level.xxx.root.log. II.log.root. In this way.5 Trace log I.root.trace.gz.2. iMAP.root. Function The system log records the operation of the system. M2000 system administrator can query system log.trace and iMAP.root. Contents The information in NE log includes user name. the trace information is updated into these two files alternatively. Function The trace log is used to locate the system internal problems.trace. 4-2 .1 are used to save the current trace information.root. When the other file is full.root. The information will then be written in the other trace file. Contents The contents of the system log include information header and information.1 and iMAP. 4. operation start/end time. III.2 in cycle and normally not into iMAP.trace. The file names are iMAP. terminal.root.log. The system log information can be queried through Client. Path The system log is stored in "/export/home/omc/var/logs" in M2000 Server. it will be converted to /export/home/omc/var/logs/traceback/iMAP. operation contents and operation result. and then sent to M2000 Server and stored in the database in M2000 Server.root. The system log information is written into iMAP. again it is converted to iMAP. Its information can be queried through Client.log.2.tar.xxx.trace.xxx.log.

2) In the main window. 4. service proxy identification (process name).3. 2) Open the file "/var/adm/messages". 4-3 . 4.5. refer to iManager M2000 Mobile Element Management System Operation Manual.1 Operation Effect The operation of browsing Solaris error log uses few system resources and will not affect the system. 4.2 Operation Procedure Carry out the operations on M2000 Client.3.3 Browsing User Log 4.5 Checking Solaris Error Log 4. select the menu [System/Log/Log Manager]. module identification.2 Operation Procedure To check the Solaris error log.Administrator Guide iManager M2000 Mobile Element Management System Chapter 4 Log Management III. select "System Log" in the navigation tree. For details. record time and process thread ID.2 Operation Procedure To browse system log.4. and the click <Query> in the right window.1 Operation Effect The operation of browsing user log uses few system resources and will not affect the system.5. 4. Contents The contents of trace log consist of information header and information. perform the following operations on the Server: 1) Log in as omcuser. 4. 4. 4) Check whether any error information exists.4. The information header includes level. 3) In the dialog box [Log Manager].1 Operation Effect The operation of browsing system log uses few system resources and will not affect the system.4 Browsing System Log 4. perform the following operations: 1) Log in to the Client.

Normally. 4) Open the file "/var/log/syslog". there is no error information.Administrator Guide iManager M2000 Mobile Element Management System 3) Chapter 4 Log Management Check whether this file contains any error information. there is no error information. 5) Check whether this file contains any error information. Normally. 4-4 .

Administrator Guide iManager M2000 Mobile Element Management System Chapter 5 Server Performance Monitor Chapter 5 Server Performance Monitor 5.2 Operation Procedure To query Server status.2 Querying Server Status through Client 5. 3) In the dialog box [System Monitor Browser]. as shown in Figure 5-1.2.2. including: z System performance z Hard Disk z Database z Service 5. select the item to be queried. Figure 5-1 System monitor Browser 5-1 . select the menu [Tools/System Monitor/Monitor Browser]. perform the following operations: 1) Log in to the Client.1 Function It is possible to query M2000 Server status through M2000 Client. including: z Querying Server status through Client z Setting Server status alarm threshold z Querying system performance z Adjusting system performance 5.1 Overview of Server Performance Monitor This chapter provides the details of Server performance monitor tasks. 2) In the main window.

Administrator Guide iManager M2000 Mobile Element Management System Chapter 5 Server Performance Monitor 5. 5. 5-2 .4. Figure 5-2 System monitor configurations 5.3.1 Function It is possible to set the threshold of M2000 Server status alarm through M2000 Client. including: z CPU occupancy z Memory occupancy z Hard Disk space occupancy z Database space occupancy When an item reaches its threshold. perform the following operations: 1) Log in to the Client. select the item to be set. 2) In the main window. 3) In the dialog box [System Monitor Configurations]. the system will generate the corresponding alarm.3 Setting the Threshold of Server Status Alarm 5.3. select the menu [Tools/System Monitor/Configurations].1 Operation Effect The operation of querying system performance uses few system resources and will not affect the system.2 Operation Procedure To set Server status alarm threshold. as shown in Figure 5-2.4 Querying System Performance 5.

That is.4. “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. 5-3 . Normally the CPU occupancy must be lower than 80%.Administrator Guide iManager M2000 Mobile Element Management System Chapter 5 Server Performance Monitor 5.2 Querying Server Status through Client. 2) Execute the following command: bash-2.2 Operation Procedure Besides querying through Client in the way introduced in 5.03$ vmstat 1 10 procs r b w memory swap free page re disk faults mf pi po fr de sr s0 s6 -. 5. 3) Check the system performance.5. you can also perform the following operations on M2000 Server: 1) Log in as omcuser. the system operation may become abnormal.1 Operation Effect If the adjustment is improper.-- in sy 543 87 cpu cs us sy id 0 0 0 5114824 1032584 24 95 8 1 1 0 0 0 0 0 0 0 0 9 0 0 0 692 17 6 76 0 0 0 4884768 891800 43 264 0 0 0 0 0 536 30913 1046 50 19 31 0 0 0 4885104 892136 0 1 0 0 0 0 0 0 0 546 30019 910 53 16 0 0 0 0 0 0 0 0 0 0 609 30131 1119 54 14 0 0 0 4883552 890936 98 747 168 8 8 0 0 25 0 0 0 739 33041 1263 54 20 31 0 0 0 4885104 892136 0 32 26 0 0 0 4883888 891272 0 1 0 0 0 0 0 0 0 0 0 532 31216 892 50 17 0 0 0 0 0 0 0 0 0 0 506 30112 963 52 15 0 0 0 4883552 890936 43 258 0 0 0 0 0 0 0 0 0 890 31651 1787 57 13 0 0 0 0 0 0 0 0 541 30023 1063 53 16 0 0 0 4883760 890640 289 1651 192 0 0 0 0 26 0 0 0 869 32775 1106 56 22 33 0 0 0 4883888 891272 0 33 29 0 0 0 4883888 891272 0 1 0 31 22 In the output. the value of “id” must be higher than 20.5 Adjusting System Performance 5.

07% imapsvcd 13540 root 11 58 0 99M 66M sleep 6:34 0. 1.01% Naming_Service Check whether the value of database memory parameter is too small. 1 on cpu CPU states: 97.49% dataserver 13524 root 27 48 0 60M 32M sleep 112:23 0.02% Monitor_Service 0:00 0:29 0.5% user. For example.5. 0. 1.1% kernel.09.4% idle. 2) Execute the following command to check the CPU occupancy of each process.16% imapsvcd 13871 root 14 58 0 285M 188M sleep 10:10 0.12% top 13527 root 14 58 0 96M 66M sleep 5:24 0. 0. 2821M swap free PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 13529 root 60 58 0 75M 56M sleep 160:11 0. 2743M swap in use.14% imapsvcd 45 root 1 58 0 2072K 1360K cpu/1 0:00 0. 211M free. 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.0% swap Memory: 2048M real.2 Operation Procedure If the CPU occupancy is too high (higher than 80%). bash-2.24% imapsvcd 13531 root 25 58 0 96M 69M sleep 69:42 0.07.03$ top load averages: 95 processes: 0.72% dataserver 345 root 72 58 0 73M 65M sleep 639:50 0. 0.05% imapsvcd 13520 root 27 6 root 1 13511 root 56 3) 58 0 58 0 58M 0 0 27M sleep 352K 248K sleep 25M 22M sleep 8:22 0. then: set shmsys:shminfo_shmmax=2.147.16% imapsvcd 10904 root 128 58 0 321M 223M sleep 9:19 0.483.10 11:30:4 94 sleeping. if the memory of the Server is 4096MB. perform the following operations: 1) Check whether the high CPU occupancy is caused by number of reported alarms exceeding the threshold.02% sh 0.42% imapsysd 13761 root 37 58 0 155M 115M sleep 60:03 0.0% iowait. 0.91% imapsvcd 357 root 180 58 0 75M 66M sleep 916:19 0.Administrator Guide iManager M2000 Mobile Element Management System Chapter 5 Server Performance Monitor 5.648 5-4 .05% imapsvcd 13591 root 30 58 0 322M 236M sleep 32:56 0.

When M2000 services are running. including types and functions of the processes and services.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management Chapter 6 M2000 Process and Service Management 6.2 SystemConfigurator SystemConfigurator manages all other local processes. including: z Querying number of M2000 processes z Querying service status z Starting M2000 services z Stopping M2000 services 6. Dependent service: None. z BackupService 6-1 . 6. and provides the details of the major process and service management tasks. this service cannot be stopped.1 Overview of M2000 Process and Service Management This chapter introduces the concepts related to M2000 services and processes. Each process includes different services and provides different functions.2.2. 6. The following section introduces the function of each processes and services. When M2000 services are running.2 Introduction to M2000 Processes and Services 6. it communicates and interacts with imapsysd processe on other machines. which enables the scheduling and control of user tasks. In a distributed environment.3 sac_agent The process sac_agent provides the following services: z ScheduleService ScheduleService provides a frame construction. Dependent service: None.2.1 Overview to Processes and Services When M2000 is running normally. this process cannot be stopped. the Server starts 18 processes. so as to avoid the impact on application processes caused by the distributed system.

5 monitor_agent The process monitor _agent provides the following services: z MonitorService MonitorService monitors the system running status. Dependent service: None. z LogService LogService records system log. 6. this service can be stopped. When M2000 services are running.2. Dependent service: None. free disk space and database system running status. It decides whether to block a request according to the current CPU and memory utilization. z LicenseService LicenseService provides a service interface for checking the validity of license file of the current version. These requests are mainly those requiring large amount of resources. EventService provides a message transmission mechanism between imap services and between imap and iview. When M2000 services are running.2. this service cannot be stopped. this service cannot be stopped. this service cannot be stopped. 6. When M2000 services are running. and then manages and stores the system logs. 6-2 . Dependent service: None. databases and managed object (MO) instance data of the system periodically. including CPU and memory occupancy. this service cannot be stopped. It also provides the function of message broadcast and filter. When there is no backup task. Dependent service: None.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management BackupService backs up important configuration files. It receives the system logs from other processes through a socket. When M2000 services are running. When M2000 services are running. Dependent service: EventService.4 em_agent The process em_agent provides the service EventService. z FlowController FlowController accepts the operation requests from other modules. this service cannot be stopped. Dependent service: EventService and MonitorService.

2. z RelationService RelationService creates. 6.7 audit_agent The process audit-agent provides the service AuditService. Dependent service: ScheduleService. creates managed object cases and solidifies the managed object. 6. When M2000 services are running. deleting. These processes can be deployed in different servers. loads managed object dynamic base. Dependent service: None. queries and deletes the relations between management objects and saves these relations into database. When M2000 services are running. querying and modifying management objects to ensure the consistency and completeness of the operations from multiple services to the same management objects.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management 6. AuditService records the operation information in database.6 partition_agent The process partition_agent provides the service PartitionService. and provides periodic or manual displacing. this service cannot be stopped. the load can be balanced. this service cannot be stopped. z MOService MOService loads and verifies the types of all managed objects in M2000 system. When M2000 services are running.2. When M2000 services are running. this service cannot be stopped. this service cannot be stopped. this service cannot be stopped. supports operation information query and log statistics information query on the Client. PartitionService divides the management objects into partitions.2. In this way. even when the number of management objects is large. When M2000 services are running. 6-3 . Different partitions are managed by different processes.8 mo_agent The process mo_agent provides the following services: z LockService LockService provides lock management when other services are creating. Dependent service: None. Dependent service: None.

6. Dependent service: MOService. this service cannot be stopped. When M2000 services are running. 6. creates and deletes the subnet. 6.2. Dependent service: EventService. Dependent service: EventService.2. SecurityService and TopoService.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management Dependent service: LockService.2. The NE engines realize the communication between M2000 system and various network equipments. It realizes the access control by restricting the users' authority to use various interfaces. 6-4 .12 ifms_agent The process ifms_agent provides the service FaultService.11 ts_agent The process ts_agent provides the service TopoService.10 med_agent The process med_agent provides the service MediationService. When M2000 services are running. EventService and PartitionService. AuditService and MOService. sub-node and link. so that only those authorized users can access to these resources. SecurityService controls the access to the sensitive resources in the Element Management System (EMS). 6. this service cannot be stopped. handles.2. stores and displays the faults reported by equipment.13 manager_agent The process manager_agent provides the service SystemService. analyzes. node.2. 6. RelationService. FaultService collects.9 sm_agent The process sm_agent provides the service SecurityService. this service cannot be stopped. MOService. MediationService creates. Dependent service: SecurityService. deletes and retrieves various NE engines mapped to network equipment in M2000 system and manages the relevant event intercepter. This service can be stopped when the fault management function is not in use. TopoService maintains the relations between the objects in the subnet. MonitorService. When M2000 services are running.

MO and the interaction with Hosts.2. 6. Dependent service: EventService. activation and rollback functions. FMNotify forwards the fault information from FaultManager to Network Management System (NMS). Dependent service: EventService.2. CMServer realizes the configuration service of all NEs. this service cannot be stopped. When M2000 services are running. It provides download. SecurityService. SecurityService and AuditService. TopoService and AuditService. When M2000 services are running. this service cannot be stopped. and is entirely independent of individual NE. this service cannot be stopped. MOService. configuration data and other files of all NEs. SecurityService and AuditService. SecurityService and AuditService. Server software version query and the corresponding Client software version. 6-5 . When M2000 services are running. This service can be stopped when the software management function is not needed. and Client upgrade information.15 cmserver_agent The process cmserver_agent provides the service CMServer.17 fmnotify_agent The process fmnotify_agent provides the service FMNotify. Dependent service: ventService.14 pm_agent The process pm_agent provides the service PMService.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management SystemService provides the function of querying M2000 version information. PMService realizes the performance services of all NEs. MOService.2. Client software version. It is entirely independent of individual NE. 6. Dependent service: None. MOService. MO and the interaction with Hosts. including operating system version.2. MOService. When M2000 services are running. 6.16 swm_agent The process swm_agent provides the service SWMService. SWMService manages the versions. this service cannot be stopped. Dependent service: EventService. 6. upload. This service can be stopped when realtime alarm forwarding is not needed. Dependent service: EventService and FaultService.

6. MOService. Dependent service: EventService. 6. This service can be stopped when remote alarm notification is not needed.2 Operation Procedure You can query on Client according to 5. or query on M2000 Server by performing the following operations: 6-6 . 6.2. 6.3. TopoService and FaultService.03$ svc_ps | wc –l 18 6.19 notify_agent The process notify_agent provides the service RemoteNotifyService. SecurityService. This service can be stopped when proxy of BTS maintenance is not needed.18 proxy_agent The process proxy_agent provides the service ProxyServer.2 Operation Procedure To query the number of M2000 processes.2.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management 6.4.2 Querying Server Status through Client. RemoteNotifyService realizes the remote notification of alarms.1 Operation Effect The operation of querying service status uses few system resources and will not affect the system. perform the following operations on the Server: 1) Log in as omcuser.3. ProxyServer enables M2000 Client to access NEs through a proxy server to run the LMT programs of these NEs.3 Querying Number of M2000 Processes 6.4.1 Operation Effect The operation of querying number of M2000 processes uses few system resources and will not affect the system. 2) Execute the following command: bash-2. Dependent service: EventService.4 Querying Service Status 6.

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 iManager M2000 Mobile Element Management System 1) Log in as omcuser. 2) Execute the following command: Chapter 6 M2000 Process and Service Management bash-2.

5.1 Operation Effect The execution of this command starts all M2000 services. refer to "17. For information about starting Sybase service.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management 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.10 Starting Sybase". Those already started will not be affected. make sure that Sybase service has been started normally.5.5 Starting M2000 Services 6. perform the following operations on the Server: 1) Log in as root. 6.2 Operation Procedure To start M2000 services. 6-8 . 2) Execute the following command: # start_svc Note: Before starting M2000 Server.

all M2000 services will be stopped. 6. 2) Execute the following command: # stop_svc If there is any service still running.6.6. execute the following command to stop it: # kill_svc 6-9 . perform the following operations on the Server: 1) Log in as root.1 Operation Effect After executing the command. the performance data and alarm data of the NEs may be lost.2 Operation Procedure To stop M2000 services.Administrator Guide iManager M2000 Mobile Element Management System Chapter 6 M2000 Process and Service Management 6. When the M2000 services are stopped.6 Stopping M2000 Services 6.

including types and contents of the databases. M2000 has four databases: z omcdb z fmdb z pmdb z sysmdb After the installation of M2000 Server applications. SMNEUser NE user information. and do not need manual modification.1 Overview of Database Management This chapter introduces the concepts related to M2000 database. 7-1 .2 Introduction to Database 7. SMSecurityPolic Security strategy. the sizes of the databases are decided.1 Overview of Database On the basis of Sybase database. including: z Querying database status z Manually displacing alarm data z Manually displacing user log z Setting auto displacing for alarm data z Setting auto displacing for user log z Deleting performance task z Clearing database 7.2 omcdb The database omcdb is used to store the M2000 configuration data. Table 7-1 Database table name and contents of omcdb Name Content SMLoginRec User login information. 7.2. It needs at least 1000MB of free space. The tables in omcdb and their contents are shown in Table 7-1.Administrator Guide iManager M2000 Mobile Element Management System Chapter 7 Database Management Chapter 7 Database Management 7. security data and the data related to internal realization. and provides the details of major database management tasks. You can use Sybase commands to manage the databases.2.

Administrator Guide iManager M2000 Mobile Element Management System Name Chapter 7 Database Management Content SMTerminal Terminal information.4 pmdb I.3 fmdb The database fmdb is used to store the alarm data of the NEs and M2000. tbl_AccessTable Save and read authority. 7-2 . The tables and their contents are shown in Table 7-3. Overview of pmdb The database pmdb is used to store the performance measurement data of NEs. The tables in fmdb and their contents are as are shown in Table 7-2. SMUserGroup User group information.2. It needs at least 3700MB of free space. It needs at least 13000MB of free space. Table 7-2 Database table name and contents of fmdb Name Content tbl_cur_alm Current alarms. 7.2. tbl_AuditTable Operation log information. Other tables Information about internal realization of alarm handling. tbl_mask_alm Screened alarms. 7. Counter information tables The counter information tables store a group of relatively fixed information. SMUser User information. Other tables Information of configuration. tbl_event Event alarms. The table types in pmdb are as follows: z Counter information tables z Task information tables z Task result tables II. security and other internal realization. tbl_his_alm History alarms.

Administrator Guide
iManager M2000 Mobile Element Management System

Chapter 7 Database Management

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
iManager M2000 Mobile Element Management System

Chapter 7 Database Management

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
7.3.1 Operation Effect
The operation of querying database status uses few system resources and will not
affect the system.

7.3.2 Operation Procedure
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
iManager M2000 Mobile Element Management System

Chapter 7 Database Management

7.4 Manually Displacing Alarm Data
7.4.1 Operation Effect
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.

7.4.2 Operation Procedure
To manually dump the alarm data, perform the following operations:
1)

Log in to the Client.

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
7.5.1 Operation Effect
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

Figure 7-2 Log displace 3) Select the tab "Manual Displace". 4) Specify whether to dump by time or by quantity of log information.2 Operation Procedure To manually dump the logs. perform the following operations: 1) Log in to the Client. 2) In the main interface of M2000 Client.Administrator Guide iManager M2000 Mobile Element Management System Chapter 7 Database Management 7. and then click <Displace>. 7.1 Operation Effect After auto displacing.5. as shown in Figure 7-1. 7.6 Setting Auto Displacing for Alarm Data 7. select the menu [System/Log/User Log Settings] to open the window [User Log Set]. 7-6 . 2) In the main interface of M2000 Client. and the dumped data will be deleted from the database. perform the following operations: 1) Log in to the Client.2 Operation Procedure To set auto displacing for alarm data. as shown in Figure 7-2.6. select the menu [Fault/Alarm Displace] to open the window [Alarm Displace]. 3) Select the tab "Auto Displace".6. the alarm data in fmdb will be saved as files to the default path in the Server.

4) Confirm the deletion. 7.1 Operation Effect After auto displacing. Specify the displacing condition. 3) Right-click the task to be deleted.Administrator Guide iManager M2000 Mobile Element Management System 4) Chapter 7 Database Management Specify the parameters such as the type of alarm to be dumped. Specify the displacing condition.2 Operation Procedure To delete a performance task. 7-7 .1 Operation Effect The performance task data cannot be dumped directly. and then select the menu [Job/Delete] in the shortcut menu. 2) In the main interface of M2000 Client. select the menu [Performance/Show Job List] to open the window [Performance Job List]. and then click <Set> to realize periodic auto displacing.8 Deleting Performance Task 7.8. but the performance task results can be saved as files and then the tasks can be deleted to clear pmdb. 7.7 Setting Auto Displacing for User Log 7. 7. 3) Select the tab "Overflow Displace". select the menu [System/Log/Settings] to open the window [Log Setting].8.7. 2) In the main interface of M2000 Client. and then click <Set>. perform the following operations: 1) Log in to the Client. perform the following operations: 1) Log in to the Client. as shown in Figure 7-2. 7. After deleting a performance task. 4) Select the tab "Periodic Displace". and then click <Set> to realize auto displacing on overflow.2 Operation Procedure To set auto displacing for user log data.7. and the dumped data will be deleted from the database. the user log data in omcdb will be saved as files to the default path in the Server. all information related to this task will be deleted from the database.

3 Querying Database Status"): 1) Dump the alarm data. 2) Dump the user log data.9.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 .9 Clearing Database 7.5 Manually Displacing User Log" and "7. 7.6 Setting Auto Displacing for Alarm Data". bash-2.9. Clearing the transaction log space of database will affect the system backup function. 4) Execute the following commands to clear the transaction data log space: Caution: Clearing transaction log will affect the backup function of the system.1 Operation Effect Clearing the data space of database has no effect on the running of the system. Refer to "7. It causes incomplete backup.4 Manually Displacing Alarm Data" and "7. and clear data space in fmdb.8 Deleting Performance".7 Setting Auto Displacing for User Log" 3) Delete the performance task to clear data space in pmdb. Refer to "7.Administrator Guide iManager M2000 Mobile Element Management System Chapter 7 Database Management 7. Refer to "7.2 Operation Procedure 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. and clear data space in omcdb.

z The Client provides graphic user interface to realize the operation and maintenance to NEs and the status monitor to M2000. Table 8-1 Directory structure of M2000 Server software Directory Description $M2K_ROOT Installation directory of M2000. It is constructed on the basis of the following software: z Sybase database z CORBA functional software z 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.2 Introduction to File System 8. 8. and provides the details of disk space management tasks. $M2K_ROOT/lib Directory storing library files. including: z Querying disk space z Clearing disk space 8.1 Overview of System Structure The system structure of M2000 is server/client mode.Administrator Guide iManager M2000 Mobile Element Management System Chapter 8 Disk Space Management Chapter 8 Disk Space Management 8.1 Overview of Disk Space Management This chapter introduces the concepts related to M2000 file system. stores the operation and maintenance data of NEs and provides NMS-oriented interface. $M2K_ROOT/idl_northbound Directory storing northbound IDL interface files.2. Default: /opt/OMC $M2K_ROOT/bin Directory storing executable files. 8-1 . $M2K_ROOT/etc Directory storing system configuration files and SQL scripts.2 Server File System The M2000 Server software runs on Solaris. z The Server realizes the communication with the NEs.2.

/export/home/omc/var/logs Directory storing system logs. 8-2 . 8. and will not affect the system. The installation package of M2000 Client software includes JAVA virtual machine for Windows. 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. It is constructed on the basis of JAVA virtual machine. Table 8-2 Directory structure of M2000 Client software Directory Description <M2000 install directory> Installation directory of M2000.3 Query Disk Space 8. /export/home/backup Directory storing backup files.2.Administrator Guide iManager M2000 Mobile Element Management System Chapter 8 Disk Space Management 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.1 Operation Effect Querying disk space uses few system resources.3. /export/home/omc/var Directory storing M2000 running data. Table 8-2 lists the directory structure of M2000 Client software.3 Client File System The Client software runs on Windows.

4) Delete all files in "/var/tmp" under that directory.4 Clearing Disk Space 8.2 Operation Procedure To clear the disk space. the output value of “capacity” must be lower than 80. 8.03$ df –k 3) Check the usage of disk space. 2) Execute the following command to search for the core files: bash-2.2 Querying Server Status through Client.3.1 Operation Effect Do not delete any file of the operating system.03$ find / -name “core*” –ls 3) Delete the useless core files. or query on M2000 Server by performing the following operations: 1) Log in as omcuser.4. That is. 8.2 Operation Procedure You can query on M2000 Client according to 5. the system cannot operate. 2) Execute the following command: bash-2. perform the following operations on the Server: 1) Log in as root. 5) Delete other useless files.4. Normally the usage of disk space must be lower than 80%. 8-3 . If any file of the operating system is deleted.Administrator Guide iManager M2000 Mobile Element Management System Chapter 8 Disk Space Management 8.

Administrator Guide iManager M2000 Mobile Element Management System Chapter 9 Dual-Plane Configuration Chapter 9 Dual-Plane Configuration 9. and automatically switch the IP address of the faulty network adapter to the normal one. Solaris OS goes on monitoring the faulty network card.1 Overview of Dual-Plane Configuration This chapter introduces the concepts related to dual-plane. 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. and restores the original IP address and mask if it becomes valid again. In this way. the Server has two Ethernet adapters: hme0 and hme1. continuous communications are insured. including: z Planning IP data z Manually setting dual-plane z Automatically setting dual-plane z Verifying dual-plane settings 9. Each adapter has an IP. and provides the details of dual-plane configuration tasks. They belong to the same IP group.These two adapters are connected with the management network. As shown in Figure 9-1. In addition.2 Introduction to Dual-Plane Dual-plane means that Solaris OS dynamically monitors dual network adapters of a single computer. 9-1 .

subnet mask: 255.68.255.255. for Figure 9-1 the planning information is: z hme0: IP: 10. all setting information will be lost.255.2 Operation Procedure To manually set the two adapters. If the Server is restarted.1 Operation Effect Manual setting is carried out through commands.0. Therefore. In practice.66.22.0 z hme1: IP: 10.23. The test IP of this adapter: 10.0.0 z IP group name: imap 9. subnet mask: 255.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.255. The test IP of this adapter: 10. The results are stored in the memory.5.105. 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 .255.10. manual setting is normally used to test the correctness of dual-plane configuration.Administrator Guide iManager M2000 Mobile Element Management System Chapter 9 Dual-Plane Configuration 9. You can select either one for the application.255.105.10. 9.10.105. subnet mask: 255.4 Planning IP Data The following information needs to be planned: z IPs and subnet masks of the two Ethernet adapters z Two test IPs and their subnet masks z IP group name For example.105. automatic setting is recommended. subnet mask: 255. the Server provides two external IPs.5.5 Manually Setting Dual-Plane 9.255.255. In this mode.10.

105.66 netmask 255.10.22 netmask 255.23 netmask 255.Administrator Guide iManager M2000 Mobile Element Management System Chapter 9 Dual-Plane Configuration # ifocnfig hme1 group imap 3) Execute the following commands to set the IP of the adapters. disable their failover and add deprecated flag.255.10. # ifconfig hme0 10. which is different from the manual mode.105.hme1". there must be no space before each line.hme0" and "/etc/hostname.255.68 netmask 255.10.105. 9.hme0".1 Operation Effect Automatic setting is realized by writing the commands into the operating system files. When the operating system is started.255.hme1".6.0 -failover deprecated up Caution: In the files "/etc/hostname. and add the following contents: 9-3 .255.6. the external IP is 10.255.66 netmask 255. 2) Open the configuration file of the first Ethernet adapter "/etc/hostname.0 up # ifconfig hme0 addif 10. and add the following contents: 10.0 -failover deprecated up Dual-plane is complete.0 up # ifconfig hme1 10. This mode provides an external IP only.105.105.10.255.22.255.255.10.10.255.2 Operation Procedure To carry out the automatic settings of the two Ethernet adapters. perform the following operations: 1) Open the file "/etc/hosts".105.255.22 imap-e4500 Note: imap-e4500 is the host name.10.105.6 Automatically Setting Dual-Plane 9. 9. In the following example.0 -failover deprecated up # ifconfig hme1 addif 10. the settings of dual-plane will take effect automatically. 3) Open the configuration file of the second Ethernet adapter "/etc/hostname. and add the following contents: imap-e4500 group imap up addif 10.

10.LOOPBACK.10.0.66 netmask ffffff00 broadcast 10.7.IPv4> mtu 1500 index 4 inet 10.IPv4> mtu 8232 index 1 inet 127.RUNNING.MULTICAST.0.105.255 groupname imap ether 8:0:20:8b:0:8d hme1:1:flags=9040843<UP.RUNNING. 9.1 Operation Effect The verification of dual-plane settings uses little system resource and will not affect the system.68 netmask ffffff00 broadcast 10.MULTICAST.10.BROADCAST.255.255 groupname imap ether 8:0:20:8b:0:8d hme0:1:flags=9040843<UP.NOFAIL OVER> mtu 1500 index 4 inet 10.105.3 Abnormal Handling If the settings is not successful. and their test IPs are also correct.MULTICAST.DEPRECATED.255 ether 8:0:20:8b:0:8d The above information shows that the IPs of the two adapters are set as 10. the dual-plane settings take effect.1 netmask ff000000 hme0:flags=1000843<UP.255.BROADCAST.255.MULTICAST.NOFAIL OVER> mtu 1500 index 5 inet 10.Administrator Guide iManager M2000 Mobile Element Management System Chapter 9 Dual-Plane Configuration 10.BROADCAST.255.68 netmask 255. and have been added to the group imap.105.7.10. perform the following operations: 9-4 .BROADCAST.105.255.7 Verifying Dual-Plane Settings 9.105.7.10.MULTICAST.255.IPv4> mtu 1500 index 4 inet 10.IPv4.255.2 Operation Procedure Execute the following commands to verify the dual-plane settings: # ifconfig -a lo0: flags=1000849<UP.105. 9.RUNNING.DEPRECATED.255.RUNNING.0 group imap -failover deprecated up 4) Execute the following command to restart the system: # init 6 After restarting the system.255 ether 8:0:20:8b:0:8d hme1:flags=1000843<UP.255.23 respectively.255.23 netmask ffffff00 broadcast 10. 9.105.10.10.22 netmask ffffff00 broadcast 10.IPv4.RUNNING.22 and 10.

3) Set the dual-plane again. check the parameter "local-mac-address" in Server openboot ROM.Administrator Guide iManager M2000 Mobile Element Management System 1) Chapter 9 Dual-Plane Configuration Check the file "/etc/hostname. There must be no space before the script in this file.hme*". Its value must be true. 9-5 . 2) In the system startup information.

The M2000 Server uses Solaris system to support NTP.Administrator Guide iManager M2000 Mobile Element Management System Chapter 10 NTP Service Configuration 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. 10-1 . It synchronized the time between distributed time Server and Client. You can set M2000 as the NTP Server or Client by setting the Solaris parameters.2 Introduction to NTP Service NTP defines time synchronization mechanism. there are three types of computers: z Top NTP Server: Refer to level 0 NTP Server. 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. The theoretical precision reaches nanoseconds. It provides time synchronization service for next level. including: z Setting M2000 as top NTP Server z Setting M2000 as middle NTP Server z Setting M2000 as NTP Client z Starting NTP service z Checking NTP service running status z Stopping NTP 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) Execute the following command: # cp /etc/inet/ntp.0 stratum 0".XXX. 2) Execute the following command: # cp /etc/inet/ntp.1.client /etc/inet/ntp.conf" and quit vi.conf # vi /etc/inet/ntp.conf 3) Add a line "server XXX.Xtype. It retrieves time from higher level and provides time service for lower level. 2) Execute the following command: # cp /etc/inet/ntp. 5) Set the values of all "XType"s in the file to "1".conf # vi /etc/inet/ntp.conf" and quit vi.4 Setting M2000 as Middle NTP Server Perform the following operations to set M2000 as the middle NTP Server: 1) Log in to M2000 Server as root.XXX.XXX.127.Administrator Guide iManager M2000 Mobile Element Management System z Chapter 10 NTP Service Configuration Middle NTP Server: Refer to level 1 Server and Level 2 Server.server /etc/inet/ntp.conf" and quit vi.127.XXX" to the file to specify the IP of the higher level NTP Server. 4) Delete "stratum 0" from " fudge 127.6 Starting NTP Service Perform the following operations to start NTP service: 10-2 . 10.XXX. 10. and does not provide time service.conf 3) Add a line "server XXX. 10.5 Setting M2000 as NTP Client Perform the following operations to set M2000 as the NTP Client: 1) Log in to M2000 Server as root.XXX" before " server 127.server /etc/inet/ntp.conf # vi /etc/inet/ntp. 4) Save the file "/etc/inet/ntp. 10. 4) Save the file "/etc/inet/ntp. z NTP Client: It only retrieves time.0 prefer" to specify the IP of the higher level NTP Server.conf 3) Set the values of all "XType"s in the file to "1". 6) Save the file "/etc/inet/ntp.

00 In the returned information.000 0.d/xntpd stop Note: The startup script of NTP is in "/etc/rc2. if there is as "*" before "LOCAL(0)". If M2000 is set as top or middle NTP Server. If they are incorrect.1.0.d/xntpd stop 10-3 .0. it is necessary to modify them manually. execute the following command: # /etc/init.1 . The NTP service will be automatically started after Solaris is started. there is no need to add the auto startup script manually. 4) Start NTP service in the NTP Server.8 Stopping NTP Service Perform the following operations to stop the NTP service: 1) Log in to M2000 Server as root. it is necessary to stop it first: # /etc/init.000 16 - - 64 0 0.0. data and time of the Server are correct. 2) Execute the following command: # /etc/init.d/xntpd start 5) Start NTP service in the NTP Client. "LOCAL(0)" means that the local clock is used as the reference clock source. 3) If the NTP service is already running. execute the following command: # ntpdate <NTP Server IP> # /etc/init.000 0.Administrator Guide iManager M2000 Mobile Element Management System Chapter 10 NTP Service Configuration 1) Log in to M2000 Server as root.d/xntpd start 10. 0.0 0 l 10 64 377 0. it means that the status of this clock reference source is normal.LCL.2 Modifying Server Time". Refer to "2.000 4000.d/". 10. 2) Check whether the time zone.000 0. Therefore.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. If M2000 is set as NTP Client.

sysmdb z The system file of M2000: the files in "/export/home/omc/var" and "/export/home/sysm" After the execution of backup. As for the data that hasn’t been packed in the file package because of being processed after backup is executed. After the execution of restoration. 11.1 M2000 System Backup Contents M2000 system backup means to back up the following contents: z The four databases of M2000: omcdb. z NE data backup: With NE data backup function.2. can be backed up to M2000 Server hard disks.1 Overview of Backup and Restoration This chapter introduces the concepts related to backup and restoration. fmdb.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration Chapter 11 Backup and Restoration 11. pmdb. and process it over again. z M2000 System Backup: With M2000 system backup function. all the content in the file package will be restored. and provides the details of backup and restoration tasks. 11-1 . including: z Modifying configuration file z Automatically backing up M2000 system z Manually backing up M2000 system z Restoring M2000 system z Backing up operating system z Restoring operating system 11.2. the above files are packed into a file package. M2000 can get it from NE by using auto synchronization function.2 Introduction to Backup and Restoration 11. refer to iManager M2000 Mobile Element Management System Operation Manual. the information on M2000 Server hard disks can be backed up to types.2 M2000 System Backup and NE Data Backup M2000 provides system backup and NE data backup function. including NE configuration data and LICENSE. For detailed information of NE data backup. the data on NEs.

II. The Mode of M2000 System Backup z M2000 system backup mode can be classified as auto backup and manual backup. 11. The second line means that the incremental backup file was generated on 2004-6-2 04:20:02. 11. It is recommended to use a tape for each day. 11-2 . system will save the backup files to "/export/home/backup/omc".4 Name of Backup Files After the execution of backup.tar.tar.gz 0 20040602042001 /export/home/backup/omc/inc-20040602042001.2.gz 1 20040603042002 /export/home/backup/omc/inc-20040603042002. and user can not set them manually. path and name of the backup files. the first line indicates that the full backup file was generated on 2004-6-1 04:20:02.3 The Mode of M2000 System Backup and Restore I. Prepare a tape before backup. the latest backup information will be recorded in "/export/home/backup/omc/backup.tar.log". system will wind the tape to the beginning. The third line indicates that the incremental backup file was generated on 2004-6-3 04:20:02. The Mode of M2000 System Restore All the content of incremental backup and full backup can be restored manually. During the backup of the second week. The information includes the generation date. the backup of the first week will be deleted automatically.gz 1 In the above information. and never replace the tape when the backup is underway. z When the storage media is magnetic tape. z M2000 system backup mode can also be classified as incremental backup and full backup. The system sets the path and name of backup files automatically.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. For example: 20040601042002 /export/home/backup/omc/all-20040601042002.2. and then back up the files together with the path to the magnetic tape. Auto backup is also referred as periodic backup. z When the storage media is disk.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration 11.2.

11.xml" meets the requirement.3. check whether the configuration related to backup or restoration in the configuration file "omcsvc. Default: all (backup to both disk and tape).xml".xml" is in "/<M2000 installation directory>/opt/OMC/etc/conf/".3.03$ su –root 7) Execute the following command to restart M2000 services: # stop_svc # start_svc 11.3.xml". 6) Switch to root bash-2.2 Setting Tape Drive Path" and "11. 2) Open the file "omcsvc. 2) Open the file "omcsvc.xml". refer to "11.2 6)Switch to root bash-2. 3) Find the following contents: 11-3 .3 Function Setting 11. Default: /dev/rmt/0 z Storage media.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration 11.3 Setting Backup Media Perform the following operations to modify the path of tape drive: 1) Log in as omcuser. It includes: z Tape drive path.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. 5) Save the file and quit. "omcsvc. 1) If the above settings do not meet the requirement.3.3.1 Introduction to Configuration File Before backup or restoration.2 Setting Tape Drive Path Perform the following operations to modify the path of tape drive: 1) Log in as omcuser. 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.

If the "all" in "<param name="backupMedia">all</param>" is "tape" or "disk". the system carries out full backup on one day. </module> …. 6) Switch to root bash-2.. "<param name="backupMedia">all</param>" means that the backup is stored in both disk and magnetic tape. then it means that the backup will be saved in disk or tape only. means that the system carries out backup at a fixed moment every day..4. <param name="backupMedia">all</param> …..4 Automatically Backing Up M2000 System 11. and carries out incremental backup on other six days.03$ su –root 7) Execute the following command to restart M2000 services: # stop_svc # start_svc 11.... In a week.1 Introduction to Auto Backup Auto backup. also called periodic backup. 5) Save the file and quit the edit status. The execution time and the full backup day can be set on M2000 Client. <module name="inc"> …… <param name="backupMedia">all</param> …… </module> Note: "<module name="all">" and "<module name="inc">" respectively stands full backup and incremental backup. 11-4 .Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration <module name="all"> …. 4) Change the "all" in "<param name="backupMedia">all</param>" to "tape" or "disk" according to the requirement.

select the tab "Server".Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration 11. The backup type can be full backup or incremental backup.4. 11.5. as shown in Figure 11-2.2 Carrying Out Manual Backup on Client Perform the following operations on M2000 Client: 1) Log in to the Client.1 Introduction to Manual Backup Manual backup is carried in special or emergent circumstances. 2) In the main window. and then select "Enable Server Periodic Backup" and set the execution time and full backup day.2 Setting Auto Backup Time Perform the following operations on M2000 Client: 1) Log in to the Client. and then select the backup type. 2) In the main window. 11-5 . such as backup tape lost and system failure. select the menu [Tools/System Backup/Periodic Backup]. From then on. 3) In the dialog box [Periodic Backup]. the system will carry out auto backup.5. select the menu [Tools/System Backup/Manual Backup]. 4) Click <OK> to save the settings. 3) In the dialog box [Manual Backup]. select the tab "Server". as shown in Figure 11-1.5 Manually Backing Up M2000 System 11. Figure 11-1 Periodic backup 11.

6.6.Administrator Guide iManager M2000 Mobile Element Management System 4) Chapter 11 Backup and Restoration Click <Start> to start backing up M2000 system. 11. Figure 11-2 Manual backup 11. execute the following command to stop the M2000 services: # stop_svc 11-6 .3 Carrying Out Manual Backup on Server Perform the following operations on the M2000 Server: 1) Log in as root.6 Restoring M2000 System 11.2 Operation Procedure Perform the following operations on M2000 Server: 1) Log in as root.1 Function Introduction Restore the M2000 system from the latest M2000 full backup and incremental backup file. 2) If the M2000 services are running. 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.5.

Administrator Guide
iManager M2000 Mobile Element Management System

3)

Chapter 11 Backup and Restoration

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
20040602042001 /export/home/backup/omc/inc-20040602042001.tar.gz 1
20040603042002 /export/home/backup/omc/inc-20040603042002.tar.gz 1

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
11.7.1 Function Introduction
Use the Solaris commands to back up the disk information (including Solaris, Sybase
and M2000 software and parameters) to the tape.

11.7.2 Operation Procedure
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
iManager M2000 Mobile Element Management System

Chapter 11 Backup and Restoration

# 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

0

0

0%

/proc

fd

0

0

0

0%

/dev/fd

mnttab

0

0

0

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
iManager M2000 Mobile Element Management System

Chapter 11 Backup and Restoration

11.8 Restoring Operating System
11.8.1 Function Introduction
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.

11.8.2 Operation Procedure
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

find .8. rm -r * 2) Import the current equipment information: # cd /devices. –print | cpio -pduVm /tmp/root2/devices # cd / 11-10 . # rm restoresymtable # cd / # umount /tmp/root3 # fsck /dev/dsk/c0t0d0s5 11. rm tmp/root2/dev/rmt/* # cd /tmp/root2/devices . it is restored first.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration # ufsrestore rf /dev/rmt/0n Note: Because the root partition is backed up first.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: # mount /dev/dsk/c0t0d0s0 /tmp/root2 # 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 restoresymtable # cd / # umount /tmp/root2 # fsck /dev/dsk/c0t0d0s0 7) Restore the partition "/opt": # mkdir /tmp/root3 # ufsrestore rf /dev/rmt/0n Note: The restored one is the "/opt" backed up after the root partition.

8.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.d/state.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration # 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. # 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/dsk/m2000dg/data /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 . installboot ./bootblk /dev/rdsk/c0t0d0s0 # mount /dev/dsk/c0t0d0s0 /tmp/root2 # touch /tmp/root2/etc/vx/reconfig.d/install-db 11.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 . 5) Open the file "vfstab".

Do you wish to review them [y.8. 11.?] (default: n) n 4) Volume Manager Installation Options Menu: VolumeManager/Install 1 Quick Installation 2 Custom Installation 11-12 .n.?] (default: y) y 3) Do you want to use enclosure based names for all disks ? [y.8.q.6 Restarting System Execute the following command to restart the system: # reboot 11. The restored hard disk has no "volum manager".q.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.Administrator Guide iManager M2000 Mobile Element Management System /dev/vx/dsk/m2000dg/data Chapter 11 Backup and Restoration /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". 2) Some licenses are already installed. so the partitions managed by "volume manager" needs to be renamed using the standard partition name.n.

. ? Display help about menu ?? Display help about the menuing system q Exit from menus Select an operation to perform: 4 7) Is this correct [y. (encapsulate) 2 Install all disks as new disks. (discards data on disks!) 3 Install one disk at a time.n.n.q.q. 6) Installation options for controller OTHER_DISKS Menu: VolumeManager/Install/Custom/OTHER_DISKS 1 Install all disks as pre-existing disks.n.?] (default: n) n 9) Restart the system: # reboot .?] (default: n) y Enter disk name for [<name>.?] (default: y) y 8) Shutdown and reboot now [y.Administrator Guide iManager M2000 Mobile Element Management System Chapter 11 Backup and Restoration 3 Prevent multipathing/Suppress devices from VxVM's view ? Display help about menu ?? Display help about the menuing system q Exit from menus Select an operation to perform: 2 5) Encapsulate Boot Disk [y.q.-x 11-13 .?] (default: rootdisk) rootdisk_1 Hit RETURN to continue.q. 4 Leave these disks alone.

Administrator Guide iManager M2000 Mobile Element Management System Chapter 12 Routine Maintenance Chapter 12 Routine Maintenance 12. 2 Check log information There is no abnormal and malicious operations implemented. refer to iManager M2000 Mobile Element Management System Operation Manual. 5 Check hard disk space The used space of each partition is lower than 80% 6 Check CPU utilization CPU utilization is lower than 80%. You can customize them according to actual needs.2. 12-1 . 7 Check the number of processes The number of running processes is 18. 4 Check database status Database system operates normally. 3 Check Solaris error log There is no err message. 12. including: z Daily maintenance z Weekly maintenance z Monthly maintenance These items are recommendation. Refer to 12.2 Checking Alarm Information Perform the following operations on M2000 Client: 1) Log in to the Client. 2) In the main window. 8 Check service status All the services are running normally. and the used space is lower than 80%. For operation and maintenance of NE. 12.2 “Checking Alarm Information” and the later section for operation guide of each maintenance item.2. select the menu [Tools/System Monitor/Monitor Browser].2.2 Daily Maintenance 12.1 Daily Maintenance Item List Table 12-1 lists the daily maintenance items. Table 12-1 Daily maintenance checklist SN Item Reference 1 Check alarm information There is no alarm information.1 Overview of Routine Maintenance This chapter provides the maintenance items and operation guide for M2000.

If any error information is found. If the free hard disk space is insufficient.3 Querying Database Status" to check the database status and used space.3 Browsing User Log" to check user operation log. implement the corresponding handling.2. For example. 12. If the CPU ululation is too high. refer to "5. refer to 7.8 Checking Number of Processes Refer to "6.3 Querying Number of M2000 Processes" to check the number of processes. if a user failed to log in to the Client for multiple times. 5) If any alarm exists.2. check the validity of this user. Refer to "4.4 Querying System Performance" to check the CPU utilization of the Server. 12.4 Querying Service Status" to check the processes which need to be started.4 Checking Solaris Error Log Refer to "4.4 Browsing System Log" to check whether there is any system operation error.7 Checking CPU Utilization Refer to "5.4 Clearing Disk Space" to handle it. 12. If the number is not enough. 12. refer to "8.9 Clearing Database" to handle it. refer to "6.5 Adjusting System Performance" to handle it. and then refer to "6. If any abnormal or malicious operation is found.Administrator Guide iManager M2000 Mobile Element Management System Chapter 12 Routine Maintenance 3) Select the tab "NE Monitor". 12.5 Services" to start them.3 Query Disk Space" to check the space of the disk.2. 12. handle it according to Solaris system administrator manual. 4) Check whether any alarm exists.2.5 Checking Solaris Error Log" to check whether the log contain any error information.2.2. If the free space of the database is insufficient.5 Checking Database Status Refer to "7.3 Checking Log Information Refer to "4. 12-2 Starting M2000 .6 Checking Hard Disk Space Refer to "8. select the menu [Fault/Query/Current Alarm] to view its detailed information.

2 Backing Up M2000 System 1) Refer to "11.3. If any one of them is abnormal.Administrator Guide iManager M2000 Mobile Element Management System Chapter 12 Routine Maintenance 12.3. 2) Execute the following command to view the current Server time: bash-2. 3 Find core files There are no core files on the Server.1 Weekly Maintenance Item List Table 12-2 lists the weekly maintenance item of M2000 system. 12.3. 12.3 6)Switch to root bash-2.2.3 Checking M2000 Server Time Perform the following operations on M2000 Server: 1) Log in as omcuser.3 Weekly Maintenance 12. temporarily files and other useless files. refer to "2.9 Checking Service Status Refer to "6.5 Manually Backing Up M2000 System" to back up M2000 system. refer to "6.3. Table 12-2 Weekly maintenance checklist SN Item Reference 1 Backup M2000 system Open the [Periodic Backup] dialog box on M2000 Client.5 Starting M2000 Services" start the process or service to be started. 2 Check the M2000 Server time The time is right.3.4 Querying Service Status" to check the status of the services. 4 Clear useless files Clear overdue log files. and select all the data to be backed up.2 Modifying Server Time".2 “Backing Up M2000 System” and the later section for operation guide of each maintenance item. 12.03$ su –root 2) Execute the following command to restart M2000 services: # stop_svc # start_svc Automatically Backing Up M2000" or "11. 12-3 .03$ date 3) To adjust time. Refer to 12.

3. Refer to 12.Administrator Guide iManager M2000 Mobile Element Management System Chapter 12 Routine Maintenance 12. 12.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.4 Clearing Disk Space" to clear the useless files in the hard disk. Table 12-3 Monthly maintenance checklist SN Item Reference 1 Check power supply The power supply of the Server is normal. 12.4. Check whether the power supply of the Server is normal. 2 Check Server hardware The Server is not damaged physically. 12-4 .4.4. 3 Check the auxiliary devices of the Server The devices such as the magnetic tape drive and CD-ROM drive are working normally.5 Clearing Useless Files Refer to "8.3.4 Monthly Maintenance 12.3 Checking Server Hardware Check whether the hardware of the Server is damaged. 2) Execute the following command to file the core files: bash-2.4 Finding core Files Perform the following operations on M2000 Server: 1) Log in as omcuser.2 “Checking Power Supply” and the later section for operation guide of each maintenance item. 12.03$ find / -name “core*” –ls 3) Read core files and delete the useless core files. z Check whether the tape drive can run normally. 12.4.2 Checking Power Supply Check whether the power indicator of the Server indicates normal.4. 12.1 Monthly Maintenance Item List Table 12-3 lists the monthly maintenance items of M2000 system.

Administrator Guide iManager M2000 Mobile Element Management System Chapter 12 Routine Maintenance For details of check CD-ROM and tape drive. refer to Solaris system administrator manual. 12-5 .

For the maintenance and fault handling of Solaris. Collection and analysis of fault information help locate the fault cause. For details of the M2000 diagnostic tool. z Troubleshooting cases. 13. fault location and fault removal. system log and trace log. For the maintenance and fault handling of Sybase database. refer to "16.3 Fault Location Fault location refers to the processes of looking for the actual fault cause from many possible causes.2 Information Collection In case of a system fault. fault location. including collection of fault information.3 M2000 Diagnostic Tool". 13.1 Overview of Troubleshooting Procedure Generally.2. it is necessary to collect the following information: z Time and place of the fault occurrence z Symptom z Implemented measures and results after fault occurrence z Version information z IP information z Alarm information z Log information The logs include user log. 13-1 . refer to Sybase system administrator manual. refer to Solaris system administrator manual.1 Overview of Troubleshooting This chapter introduces the following contents: z General troubleshooting procedure.2. range division and fault clearance.2 Troubleshooting Procedure 13. detailing the analysis and handling of faults. Each section describes a fault.2. z Internal problem location Information Use the M2000 diagnostic tool to collect the internal problem location information. a troubleshooting procedure covers information collection. 13.Administrator Guide iManager M2000 Mobile Element Management System Chapter 13 Troubleshooting Chapter 13 Troubleshooting 13.

2.2. the operating system shuts down automatically. 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. 13.3.1 Symptom When the serial port cable connecting the M2000 Server and terminal is removed. when the Server is disconnected from the terminal. refer to this chapter.2 Fault Analysis Under the default settings of Solaris. For the clearance of faults related to the Server. For the clearance of faults related to the Client.3. refer to iManager M2000 Mobile Element Management System Operation Manual. 13-2 .4 Fault Clearance Clear the faults according to their causes: z Hardware faults Refer to the manual delivered with device.Administrator Guide iManager M2000 Mobile Element Management System Chapter 13 Troubleshooting M2000 system faults include hardware faults and software faults. z M2000 software faults Refer to M2000 Client alarm online help to clear the faults. z Solaris faults Refer to Solaris system administrator manual. z Hardware faults The hardware faults include the ones occurring to M2000 Server. 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. The appearance and status indicators of hardware help locate hardware faults easily. For the clearance of faults related to software installation. the system will be shut down automatically.2 Information Collection")and contact Huawei for handling immediately. 13. Client and networking equipment.3 Auto Shutdown of Operating System 13. refer to iManager M2000 Mobile Element Management System Installation Manual.

6) Restart the system.4.1 Symptom Some services automatically restart abnormally. execute the following command to stop the service: # kill_svc 3) Execute the following command to stop Sybase: # isql –SSYB –Usa –P<user sa password> 1> shutdown SYB_BACKUP 2> go 1> shutdown 2> go 4) Set Sybase operation parameter: 13-3 . 4) Delete the "#" before "KEYBOARD_ABORT=alternate" in this file. 2) Execute the following command to stop M2000 services: # stop_svc This command fails. 13. 13. 13.4 Abnormal Service Restart 13. 3) Open the file "/etc/default/kbd".3 Fault Clearance Perform the following operations to clear the faults: 1) Reconnect the serial port cable between M2000 Server and the terminal.4. 5) Save the change and quit.3 Fault Clearance Perform the following operations to clear the fault: 1) Log in to the Server with the ID of "root". # /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.4. 2) Log in to the Server as root on the terminal. z The M2000 system is abnormal.3.Administrator Guide iManager M2000 Mobile Element Management System Chapter 13 Troubleshooting 13.2 Fault Analysis The possible causes are: z Sybase is abnormal.

5) Execute the following command to restart Sybase: # cd /opt/sybase/ASE-12_0/install # . 3) If there is any service not started yet./startserver –f .5.5./RUN_SYB # .5 Abnormal Service Termination 13. 13-4 .Administrator Guide iManager M2000 Mobile Element Management System Chapter 13 Troubleshooting Refer to iManager M2000 Mobile Element Management System Installation Manual to set Sybase operation parameters. contact Huawei for solution. meaning that this service is terminated abnormally. 13.5.1 Symptom Execute the following command: # svc_adm -cmd status The output message contains "not running"./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.2 Fault Analysis The possible causes are: z Error occurs to program operation causing the abnormal termination of the service. 2) Execute the following command to start service: # start_svc Do not manually terminate the startup procedure. z The startup procedure is manually terminated./startserver –f . 13.3 Fault Clearance Perform the following operations to clear the fault: 1) Log in to the Server as root.

Administrator Guide
iManager M2000 Mobile Element Management System

Chapter 13 Troubleshooting

13.6 M2000 Services Starting or Stopping Failure
13.6.1 Symptom
Executing one of the following commands fails:
z

start_svc

z

stop_svc

z

kill_svc

13.6.2 Fault Analysis
The possible causes are:
z

No execution runtime script is available before executing these commands.

z

More that one user is executing the above commands at the same time.

13.6.3 Fault Clearance
Perform the following operations to clear the faults:
1)

Log in to the Server as root.

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
iManager M2000 Mobile Element Management System

Chapter 14 Emergency Maintenance

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

z

Emergency maintenance for M2000 Client

14.2 Emergency Maintenance for M2000 Server
14.2.1 Function Introduction
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.

14.2.2 Operation Procedure
Perform the following operations to recover the M2000 Server:
1)

Recover the operating system

z

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.

z

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
14.3.1 Function Introduction
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
iManager M2000 Mobile Element Management System

Chapter 14 Emergency Maintenance

14.3.2 Operation Procedure
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

03$ .2.3. can be manual running and auto running.sh The script.2 Introduction to Commands 15. z svc_profile. 15.1 Function of svc_profile.2.3 svc_profile. such as command search path and dynamic library search path. 15.3. 15. svc_profile.sh. /<M2000 installation directory>/svc_profile.3 Running svc_profile. z The M2000 environment setting script svc_profile. 15.sh The script.sh.1 Path of Commands The M2000 system maintenance commands are stored in "/<M2000 installation directory>/bin".sh It is necessary to execute the script.2 Path of svc_profile.2 Prerequisites of Using Commands The prerequisites of using M2000 commands are: z Sybase is running normally.3. 15. is in "/<M2000 installation directory>". svc_profile.sh 15-1 . svc_profile. before using the M2000 commands. z Functions of some important commands and the corresponding examples.Administrator Guide iManager M2000 Mobile Element Management System Chapter 15 Command Guide Chapter 15 Command Guide 15. z Manual running The method of manually running this script is: bash-2.sh: introduces the functions and running of the environment script.sh has been executed.sh.sh 15. This script is used to set the user’s working environment.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.

Administrator Guide iManager M2000 Mobile Element Management System Chapter 15 Command Guide Caution: There must be a “..2 Example # start_svc ============================ Starting Services . and a space between “. and prompts that each service is already running. this command will try to start each service.4 start_svc 15. ============================ Finished Starting Services. the script is added to the file ".” and “/”.1 Command Function This command is used to start all the M2000 services. z Auto running After the installation of the system according to iManager M2000 Mobile Element Management System Installation Manual.. Note: iManager M2000 Mobile Element Management System Installation manual introduces the settings of the file ".. If the services have been already started.. 15.4. imapsysd already running.. 15-2 . TAO Naming Service is running TAO Notification Service is running Monitor_Service already running. 15.. LogServer [starting.profile" of "omcuser" and "root". ] svc_adm:info:service with this name is already running ….4. If you log in as omcuser or root. the system will automatically run this script.profile" of "omcuser" and "root".” at the beginning of a command.

7.. 15.Administrator Guide iManager M2000 Mobile Element Management System Chapter 15 Command Guide 15. this command will try to stop each service and prompts error.5. 15.03$ svc_adm –cmd status The current status ("running" or "not running") of all services will be displayed. SystemMonitor [stopped ] EventManager [stopped ] LogServer [stopped ] …. It is an extreme measure to use this command.1 Command Function This command is used to view the current running status of all M2000 services...7 svc_adm –cmd status 15.1 Command Function This command stops all the M2000 processes and services using the kill process mechanism of the operating system. use stop_svc to stop all the M2000 services. 15-3 . 15.5 stop_svc 15.7.2 Example bash-2. 15.1 Command Function This command is used to stop all the M2000 services If the services are not started yet.6. Do not use kill_svc to kill the processes unless in special cases such as when the process is abnormal. It may cause data loss and service abnormal.. ============================ Finished Stopping System. In normal cases.2 Example # stop_svc ============================ Stopping System .6.5.6 kill_svc 15.2 Example # kill_svc 15.

9.4% idle.03. 2655M free. 0.9 top 15.03$ top load averages: 0.9.8.. 0. 15.07% imapsysd 6726 root 1 58 0 2160K 1664K cpu0 0:00 0.1 Command Function This command is used to query the running status of all M2000 processes.. 15.2 Example bash-2. Table 15-1 lists the meanings of the columns in the returned message of the command "top".8 svc_ps 15.11. 8099M swap free PID USERNAME THR PRI NICE SIZE RES STATE TIME 346 root 52 59 0 109M 5378 root 22 58 0 95M 67M sleep 0:08 0.0% swap Memory: 4096M real. 15.07% top 101M sleep 632:43 CPU COMMAND 0. 0. 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 .6% kernel.32% dataserver …. 0.30 10:37:25 107 processes: 106 sleeping.2 Example bash-2.09% imapsvcd 5371 root 21 58 0 61M 30M sleep 0:07 0.8.0% iowait.Administrator Guide iManager M2000 Mobile Element Management System Chapter 15 Command Guide 15. 1 on cpu CPU states: 99.1 Command Function This command is used to display the total CPU and memory utilization in the system and the CPU and memory utilization of each process.03$ svc_ps This command returns the running M2000 processes in the system.0% user. 0. 0.

11.1 Command Function This command is used to load the configuration data from the configuration file imap. If the process is running.10. This command realizes the real time update of configuration information during M2000 service running. It is used in internal problem location and commissioning.10. "MM" is the month. the configuration data in the configuration module is the same as the data in the file imap.YY_MM_DD__HH:MM:SS".Administrator Guide iManager M2000 Mobile Element Management System Column Chapter 15 Command Guide 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.xml to the system configuration module.10 svc_adm –cmd reload 15.2 Example bash-2. TIME The time this process has been running by far CPU CPU utilization of this process COMMAND Command that starts this process 15. In the above description.03$ svc_adm –cmd reload After executing this command.03$ svc_stacks After executing this command. then the CPU it uses is displayed.11 svc_stacks 15. the query results will be saved in "/<M2000 installation directory>/var/logs/imap_stacks. 15. "MM" is the minute and "SS" is the second. 15-5 . "HH" is the hour. 15. 15. "YY" is the last two digits of the year.1 Command Function This command is used to collect the stack information of the M2000 services. "DD" is the date.11.2 Example bash-2.xml.

dump". After executing this command. It is used in internal problem location and commissioning.2 Example bash-2.lock.Administrator Guide iManager M2000 Mobile Element Management System Chapter 15 Command Guide 15.12 svc_lockdump 15. the query results will be saved in "/<M2000 installation directory>/var/logs/iMAP.12.12. 15-6 .03$ svc_lockdump Dump MO Locks information successfully.1 Command Function This command is used to collect the lock status of the current management objects. 15.

2. 16.2.1 Function The tape drive management tool provides GUI for the user to manage various types of type drive.03$ . HP and Sun. /<M2000 installation directory>/tapemanager/tapemanager.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide Chapter 16 Tool Guide 16.1 Overview of Tool Guide This chapter introduces the functions and usages of M2000 tools.2 Tape Drive Management Tool 16.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. 3) Execute the following command to start the tape management tool: bash-2. 16-1 . 2) Execute the following command to check whether the status of the tape drive is normal: bash-2. including the produces of Sony.sh Figure 16-1 illustrates the main interface of the tape drive management tool.2 Starting method Perform the following operations on M2000 Server: 1) Log in as omcuser. 16. it means that the tape drive is running normally.

no tape in the tape drive and tape drive busy. eject the tape from the tape drive z Format tape: Format the tape to the specified format z Backup and restoration files: back up the files in the disk to the tape drive.3 Operation Guide The tape drive management tool provides the following operations: Caution: It is necessary to load the tape before any operation.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool 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. tape damaged.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.3.2.3 M2000 Diagnostic Tooling 16. The possible causes of tape loading failure are tape drive not connected correctly. z Load and eject: Load the tape into the tape drive. The information includes: 16-2 . restore the files in the disk z Search files: search for a file in the tape drive or disk z Query tape drive status z Refresh z Delete 16.

16. Figure 16-2 M2000 diagnostic tool 3) In the window [M2000 Diagnostic Tool]. 2) Select the menu [Start/iManager M2000 Client/M2000 Diagnosis] to run the diagnostic tool. as shown in Figure 16-2. 16-3 .2 Running Diagnostic Tool Perform the following operations to run the diagnostic tool: 1) Log in to the Client.3. The window [M2000 Diagnostic Tool] is displayed. the result of pstack z Lock status of MO z Alarm synchronization numbers of the NEs z Alarm diagnostic data. as shown in Figure 16-3.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide z Client trace log z Client JAVA virtual machine thread stacks and lock status z Server trace log z Server core files z Queue synchronization pointer of software management z Number and status of background threads. that is. click <Setting> to open the window [FTP Server Setting].

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

cfg".3 Abnormal Handling If you fail to run the diagnostic tool. perform the following operations on the Server to stop diagnostic service: 1) Log in to the Server as root.2 Function Settings You can configure the export function by modifying the configuration file "/<M2000 installation directory>/bin/PMExporst. the service is not running.4. 2) Check whether the diagnostic service is running: # ps -ef | grep start_collector | grep -v grep If there is any message returned.4. 16. it means that the service is running.2 “Running Diagnostic Tool”. Refer to 16. the diagnostic service start to run automatically after M2000 Server application software is installed successfully. 16. 16-5 . Note: Normally.3. the system periodically exports the specified job results to a file.1 Function The performance job result auto export tool is used to automatically export the performance job results.3. # start_collector 4) Restart diagnostic tool on the Client. 2) Stop diagnostic service: # stop_collector 16. They will be deleted after they have been stored for a period of time (defined when the task is created). perform the following operations: 1) Log in to the Server as root.4 Performance Job Result Auto Export Tool 16.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide 16.4 Forbidding Using Diagnostic Tool To forbid using diagnostic tool. Otherwise. The exported job results will not be deleted from the performance database. 3) Start the diagnostic service if it is not running yet. After running this tool.3.

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

. The related information can be viewed in the log file 16-7 . 2) Run the auto export tool PMExporst.log". 1:00-2:00. 1:30-2:00. The possible cause is that wrong parameter was entered when starting the tool. the result of 0:00–1:00 will be exported at 1:30.5 Abnormal Handling If the result files cannot be generated as expected.. 0:30-1:00. to export the results with the export period of 60 minutes and the delay of 30 minutes. 4) If the service is running.... For example..03$ ps -ef | grep PMExporst | grep -v grep 2) If the service is not running.. 0:00-0:30. and stop this process: bash-2. the possible cause is that the task does not exist or it has not report result yet. see Table 16-1.out". bash-2. 3:00-4:00..4 Stopping Auto Export Tool Perform the following operations on the Server to stop the service: 1) Log in as omcuser. 0:00-1:00.. 1440 Every day.03$ ps -ef | grep PMExporst | grep -v grep 3) Query the process ID (pid) of PMExporst. 2) Stop the auto export tool: bash-2.03$ nohup PMExporst SYB sa <sa user password> & After that. perform the following operations: 1) Execute the following command to check whether the service is running: bash-2. 16. Table 16-1 Export period and time segment Export period ( minute) Time segment 30 Every 30 minutes starting from 0:00. For example. and the result of 1:00–2:00 will be exported at 2:30. 3) Check whether any error information exists in the log file " /opt/OMC/bin/PMExporest. 2:00-3:00. For example.. 0:00-24:00 For example. 1:00-1:30.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide 1) Log in as omcuser.4.03$ kill -9 <pid> 16. The time segment is divided according to export period. job results of each time segment is exported to files after a delay automatically. 60 Every hour starting from 0:00.4. check whether any error prompt exists in the file "/opt/OMC/bin/nohup.

Command format # iptools –l II.sh"). The path of the IP modification tool is "/<M2000 installation directory>/bin". 16. If a task does not exist. z Mac address: 00:03:ba:12:f9:12 z Sybase listen address: 10. z Log in as root. Example # iptools –l InterfaceName IPAddress MACAddress -----------------------------------------------------------eri0 Titan 00:03:ba:12:f9:12 -----------------------------------------------Sybase Listener IP Address Port -----------------------------------------------10.5.241 z Port number: 4100 16-8 .161. "Titan" is the host name.3 Querying IP Settings I. 16.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide "/opt/OMC//var/logs/PMExporest.3 svc_profile.45.5. 16.45.5.241 4100 The output message displays the current system IP settings: z Interface name: eri0 z IP address: Titan. Its corresponding IP address can be queried in the file "\etc\hosts".2 Prerequisites The prerequisites of running the IP modification tool are as follows: z The M2000 system has been installed successfully.161.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.5 IP Modification Tool 16.log". z The environment setting script is running (refer to "15. it will not affect the export of other task results.

255. host name is "host".141. Host name.1 –H host –d change net default: gateway 10. default gateway is 10.54. # iptools –D 10. the IP is 10.255. 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 z -i: IP of the Ethernet adapter (decimal IP address) z -G: Default gateway of Solaris z -H: Host name of Solaris z -d: Switch.54 –m 255.255.5.141.4 Modifying Solaris IP Address. # iptools –n hme0 –i 10.54 succeed ! 16.141. Command format # iptools -D ip-address II.54 succeed ! set all services of sybase ip 10. and the subnet mask is 255. Default Gateway and Subnet Mask I.70.54 set all services of sybase ip 10.1 set new ip : 10.141.70.5 Modifying Sybase IP I.70. The Solaris IP is 10.70.255.70.54.70.70. # iptools –n hme0 –i 10.1. which means that the IPs of all database services of Sybase are set as the new IPs II.70.141. The interface name is "hme0".54 succeed ! 16-9 .255.54 –m 255.141.141.0 set new ip : 10.141.141.141.0 –G 10.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide 16.70. Example Set IP interface descriptions of all Sybase database services.54.5.141.255.70. and the IPs of all servers of Sybase are 10.70.141.70.70.141.0. Example z Set all interfaces.54 succeed ! set old hostname : UFO ---> new hostname : host succeed ! z Set the Ethernet adapter interface.

70.141.5.5. Example Set the IP of the SYB service of Sybase database as 10. # iptools –S SYB –D 10.141.141. the system will prompt: omc is same with the current host name ! 16.54 –P 4000 set service SYB with ip 10.5.1 change net default: gateway 10.8 Modifying Gateway I.6 Modifying Sybase Service IP and Port Number I. Command format # iptools {-S service-name -D ip-address -P port } II.141.141.70. # iptools –H omc set old hostname : host ---> new hostname : omc succeed ! If the new name is the same as the original name.70.54 succeed ! 16.Administrator Guide iManager M2000 Mobile Element Management System Chapter 16 Tool Guide 16.54 and the port number as 4000. Example Set the Solaris gateway as 10.7 Modifying Host Name I.70. Command format # iptools -G gateway II.141.1. Command format # iptools -H host-name II.1 If the modification of gateway fails. the system prompts: change default gate failed!! 16-10 . Example Modify the Solaris host name as "omc". # iptools –G 10.70.70.

1) Log in as root. 17.3. 2) Open the file "/etc/default/login". If it is necessary to log in to the system as root through ftp. the user root can log in to the system only through the console after Solaris8 is installed. 2) Open the file “/etc/ftpusers” 3) Find the line of root user.2 Logging in as root though Telnet 17. 17-1 .3. 1) Log in as root. 3) Find the line of CONSOLE=/dev/console.2.2. the user root does not have the authority to use FTP by default. Add "#" in the front of the line to turn it to a comment line.2 Answer For the sake of security.2 Answer For the sake of security.3 Logging in as root though FTP 17. follow the procedure below. If it is necessary to log in to the system through telnet as root. and delete the line.1 Question Why can't I log in as root through FTP? 17. 17.1 Overview of FAQ This chapter introduces the frequently asked questions and the solutions concerning Solaris operating system and Sybase database. 4) Save the settings and exit.1 Question Why can't I log in as root through Telnet? 17. It is recommended restoring the original setting after that. It is recommended restoring the original setting after that. 4) Save the settings and exit. follow the procedure below.Administrator Guide iManager M2000 Mobile Element Management System Chapter 17 FAQ Chapter 17 FAQ 17.

the installation is as follows: 1) Power off all peripherals. There is a tape in the tape drive.Administrator Guide iManager M2000 Mobile Element Management System Chapter 17 FAQ 17. 5) Log in as root. it will be identified automatically. /dev/rmt/0n: No such file or directory This means that the tape drive is not attached. and then execute the following command to view the tape drive status: 17-2 . 3) To use the SCSI interface. /dev/rmt/0n: no tape loaded or drive offline This means that the tape or tape drive is in offline state. When the Server is started up.1 Question How to install tape drive for the Server? 17. execute the following command to attach the tape drive: # drvconfig # tapes 8) When the tape drive is attached. connect the SCSI cable to the IN interface of the tape drive. and the tape has been rewound to the beginning. 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. 7) If the tape drive is not attached. No such device or address This means that the tape drive is not connected with the work station or the connection is incorrect.2 Answer The built-in tape drive does not require the installation of driver.4 Installing Tape Drive 17.4. 2) Set the ID switch of the tape drive to 4 or 5. and boot the system. In the case of Sun Ultra 60. 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 external tape drive requires the installation of driver.4. 4) Power on all peripherals and the host. insert a tape.

0".Administrator Guide iManager M2000 Mobile Element Management System Chapter 17 FAQ # mt status 17.0.2 Answer Perform the following operations on the Server: 1) Log in as root. 2) Perform the following operations according to the actual needs: z Too add a route.1 4) Save the change and quit vi.12. How to set the RNC IP as the default route IP.8.2 Answer Perform the following operations on the Server: 1) Log in as root.255. that is.5.6.255.0/32 10.1 17-3 . For example.6 Adding and Deleting Routes 17.44. route add 129. Subnet mask: Must be a number.1 Question How to add and delete routes in Solaris system? For example. for example: 10.1 Question How to set the default route in Solaris system? For example. execute the following command: # route add <destination address>/<subnet mask> <gateway> Destination address: can be either a network address or a host address. how to establish the maintenance channels to NodeBs controlled by multiple RNCs? 17. the total number of "1" in the binary subnet mask.6.161. "32" means "255.5. 2) Execute the following command: # vi /etc/defaultrouter 3) Enter the default route IP in the file. For example.8. 5) Execute the following command to restart the Server: # init 6 17. there multiple NodeBs are controlled by one RNC. so as to establish a maintenance channel from M2000 to NodeBs? 17.5 Setting Default Route 17.

7.0. 17. S98TAO (for starting TAO service) and S99IMAP (for starting M2000 services).8.9.12.0/32 10.2 Answer Perform the following configurations on the Server: 17-4 . The installation software of M2000 Server will generate three startup files in "/etc/rc2.12. For example: route add 129. the system executes all script files with the initial letter of "K" in "/etc/rc2.1 Question How to query the hardware configuration of the Sun server? How to check the size of memory? 17. z During the startup of Solaris.8 Querying Hardware Configuration of Server 17.0/16 10.8.1/32 10.d/": S98sybase (for starting Sybase).8.d" in Solaris 17. z During the shutdown of Solaris. route delete 129.2 Answer There are two types of files in "/etc/rc2.d/S97route": # vi /etc/rc2.7.0.7 "/etc/rc2. execute the following command: # netstat –rv z To enable the system to automatically execute the route adding command on system startup.8.1 Question What are the meanings of the files in the directory "/etc/rc2.d/S97route Write one or more entries of router add <destination address>/<subnet mask> <gateway> commands in this file.8. create the file "/etc/rc2.d": those with the initial letter of capitalized "S" and those with the initial letter of capitalized "K".0. execute the following command: # route delete <destination address>/<subnet mask> <gateway> For example.8.Administrator Guide iManager M2000 Mobile Element Management System z Chapter 17 FAQ To delete a route.12.d" in alphabetical order.d" in alphabetical order. the system executes all script files with the initial letter of "S" in "/etc/rc2.d" in Solaris? 17.1 17.8.1 z To view the route information.1 route add 129.

Ultra-60" is the type of the Server.2 Answer Perform the following operations on the Server to check the status of Sybase: 1) Log in as dbuser. 17. it means that the active and standby databases are both started.1 Question How to check the startup status of Sybase? 17.10.9. "Memory size: 512 Megabytes" indicates the size of memory. 2) Execute the following command: bash-2.2 Answer Perform the following operations on the Server to start Sybase service: 17-5 .9 Confirming Startup of Sybase 17. 17.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.9.10 Starting Sybase 17.1 Question How to start Sybase service? 17.dat -e/opt/sybase/ If the returned message contains "dataserver" and "backupserver". 2) Execute the following command: 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. and "SUNW.Administrator Guide iManager M2000 Mobile Element Management System 1) Log in as root.10.03$ cd /opt/sybase/ASE-12_0/install bash-2.

03$ .2 Answer Perform the following operations on the Server to stop Sybase service: 1) Log in as dbuser. 17-6 . 2) Execute the following command: Chapter 17 FAQ bash-2.11.Administrator Guide iManager M2000 Mobile Element Management System 1) Log in as dbuser./RUN_SYB bash-2.03$ cd /opt/sybase/ASE-12_0/install/ bash-2./startserver -f . Sybase will be started automatically after the startup of the operating system.1 Question How to stop Sybase service? 17.03$ .11.11 Stopping Sybase 17. 2) Execute the following command: bash-2./RUN_SYB_back 17.03$ isql -SSYB -Usa -P<password of user sa> 1> shutdown SYB_BACKUP 2> go 1> shutdown 2> go Note: If the M2000 Server software has been installed./startserver -f .

Administrator Guide iManager M2000 Mobile Element Management System Appendix Acronyms and Abbreviations 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 T 1 .

Administrator Guide iManager M2000 Mobile Element Management System TCP Transfer Control Protocol 2 Appendix Acronyms and Abbreviations .

3-6 backing up operating system user. 7-8 user log. 15-3 M2000 user. 7-2 introduction. 17-5 sysmdb. 7-3 user account.sh. 4-3 fmdb. 15-5 route. 12-1 setting. 11-3 operation guide. 15-6 system performance. 7-7 modifying password. 7-2 solaris error log. 7-4 Sybase. 15-3 adjusting svc_lockdump. 15-2 M2000 user group. 12-1 browsing database system log. 11-4. 11-1 item list. 11-5 operating system. 4-3 clearing. 3-2 pmdb. 4-3 querying. 8-3 introduction. 7-1 checking NTP service. 10-3 pmdb. 8-2 route. 11-1 daily maintenance introduction. 15-1 alarm data svc_ps. 3-3 M2000 system. 3-6 M2000 user group. 3-4 default route client setting. 15-4 displacing automatically. 15-5 displacing manually. 7-1 C modifying user password. 7-6 svc_stacks. 11-7 D backup and restoration database. 3-3 clearing dbuser database. 17-3 emergency maintenance. 3-6 start_svc. 3-5 omcdb. 7-8 disk space. 3-3 svc_adm –cmd reload.Administrator Guide iManager M2000 Mobile Element Management System Index Index fault information. 15-3 operating system user. 3-6 stop_svc. 15-4 creating B M2000 user. 17-3 collecting i-1 . 16-2 A command adding kill_svc. 5-3 svc_profile. 7-5 top. 17-3 svc_adm –cmd status. 14-1 deleting file system.

8-2 modifying. 6-1 file system client. 15-1 dumping. 9-1 E file system. 10-1 performance result. 4-2 trace log. 3-2 automatically setting. 8-1 system log. 4-1 server. 16-8 displacing I alarm data. 16-8 introduction. 3-1 fmdb user log. 7-1 pmdb. 11-1 verifying. 4-1 backup and restoration. 6-1 service. 17-2 introduction. 11-1 IP displacing automatically. 4-1 modifying password. 8-2 sysmdb. 7-5 modifying. 14-1 NE log. 7-2 F process. 4-2 server. 4-1 exporting NTP. 7-6 user log. 16-8 diagnosis tool. 2-2. 9-3 installing configuration procedure. 7-2 querying. 7-3 introduction. 3-4 system log. 9-2 tape drive. 14-1 log. 16-5 omcdb. see displacing database. 2-3. 7-1 dual-plane. 4-2 G type. 7-5.Administrator Guide iManager M2000 Mobile Element Management System Index modifying. 9-4 command. 17-1 ftpuser log introduction. 4-1 ftpusr NE log. 7-5. 9-2 backup and restoration. 8-1 trace log. 8-1 emergency maintenance fmdb. 4-1 gateway i-2 . 7-2 client. 16-2 H disk space clearing. 4-2 user account. 3-2 introduction. 8-3 host name querying. 9-1 introduction manually setting. 4-1 user log. 7-6 displacing manually. 16-8 FTP L logging. 7-7 inrpt dual-plane introduction.

13-1 operation guide. 7-2 M2000 user. 10-2 system performance. 6-6 starting. 11-6 modifying user password. 4-1 database. 11-1 M displacing automatically. 8-2 checking. 10-3 hardware configuration. 3-6 procedure server status. 3-4 user account. 7-7 M2000 introduction. 9-2 monthly maintenance emergency maintenance. 3-4 exporting job result. 2-3. 3-3 restoring. 3-6 backing up. 3-5 clearing. 3-6 operating system creating user group. 6-6 setting NTP client. 3-1 gateway. 3-2 backing up manually. 16-8 pmdb time. 11-5 modifying password. 6-6 N Q NE log querying introduction. 2-4 querying number.Administrator Guide iManager M2000 Mobile Element Management System Index O logging through FTP. 16-8 setting middle NTP server. 11-4 introduction. 10-3 i-3 . 3-4 creating user. 17-4 omcuser backing up automatically. 17-1 backup and restoration. 7-1 displacing manually. 16-8 IP. 10-2 service status. 14-1 item list. 10-2 process number. 10-2 server status. 2-1 backup and restoration. 6-1 setting. 11-7 monitoring user. 16-8 P host name. 3-6 creating user. 11-1 user password of database. 17-1 omcdb through Telnet. 7-4 NTP disk space. 16-5 monitoring introduction. 5-2 stopping. 5-1 configuring dual-plane. 7-5 auto startup. 12-4 troubleshooting. 2-2. 12-4 process multiple IPs introduction. 10-1 IP. 11-9 modifying user account. 7-7 user password of operating system. 3-3 restoring. 17-4 introduction. 5-1 setting top NTP server.

17-3 M2000 service. 5-1 introduction. 6-9 tape drive setting installing. 6-8 T stopping. 3-5 stopping. 17-4 deleting.Administrator Guide iManager M2000 Mobile Element Management System Index R threshold server status alarm. see deleting solaris error log restoring checking. 5-2 system performance service adjusting. 4-3 M2000 system. 17-3 stopping setting. 10-2 i-4 . 6-8 root NTP service. 10-2 removing. 17-5 introduction. 17-3 Telnet gateway. 2-1 middle NTP server. 17-4 backup and restoration. 14-1 introduction. 11-9 M2000 service. 16-8 logging. 17-1 host name. 17-5 modifying password. 6-6 starting. 5-2 top NTP server. 17-6 server sysmdb auto startup. 17-3 for Sybase. 16-8 modifying. 11-1 emergency maintenance. 10-2 trace log multiple IPs. 4-2 setting status alarm threshold. 3-4 startup file route for M2000. 12-1 Sybase. 10-3 daily maintenance. 11-3 management. 17-5 modifying password. 6-9 routine maintenance NTP service. 17-4 adding. 10-2 introduction. 6-1 querying. 17-4 browsing. 5-2 querying status. 16-8 time IP. 17-4 sa checking. 5-3 introduction. 2-2. 2-3. 3-3 starting. 2-4 introduction. 3-1 Sybase. 4-3 querying status. 4-2 NTP client. 8-1 system log querying hardware configuration. 17-2 backup and restoration. 16-1 default route. 2-1 Sybase S auto startup. 12-3 time. 11-6 starting operating system. 12-4 stting weekly maintenance. 17-6 monthly maintenance. 7-3 file system.

13-2 type. 13-1 M2000. 3-2 introduction. 13-2 root. i-5 . 3-1 user log U browsing. 3-2 operation guide. 3-3 item list. 3-1 weekly maintenance M2000. 7-5 dbuser. 3-2 inrpt.Administrator Guide iManager M2000 Mobile Element Management System Index operating system. 3-1 troubleshooting case. 13-1 information collection. 4-1 ftpuser. 3-3 displacing manually. 16-2 operating system. 7-7 user account database. 12-3 omcuser. 4-3 displacing automatically. 3-3 tool. 12-3 i. 3-2 W introduction. 3-3 procedure. 3-1 fault clearance. 3-1 user authority fault location. 13-1 database.