00366168-M2000 Administrator Guide (S10) (V200R006 - 05)

M2000 V200R006
Administrator Guide (S10)
Issue Date Part Number
05 2008-05-20 00366168
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
M2000 Administrator Guide (S10)
Contents
Contents
About This Document.....................................................................................................................1 1 Powering On/Off the M2000 ...................................................................................................1-1
1.1 Powering On/Off the M2000 (Netra240)........................................................................................................1-2 1.1.1 Powering On the M2000 (Netra240)......................................................................................................1-2 1.1.2 Powering Off the M2000 (Netra 240)....................................................................................................1-3 1.2 Powering On/Off the M2000 (V890)..............................................................................................................1-3 1.2.1 Powering On the M2000 (V890)............................................................................................................1-3 1.2.2 Powering Off the M2000 (V890)...........................................................................................................1-5 1.3 Powering On/Off the M2000 (E4900)............................................................................................................1-6 1.3.1 Powering On the M2000 (E4900)..........................................................................................................1-7 1.3.2 Powering Off the M2000 (E4900).........................................................................................................1-9
2 Setting the M2000 Time............................................................................................................2-1

2.1 Time Synchronization Solution for Huawei Mobile Network........................................................................2-2 2.1.1 Purpose of Time Synchronization..........................................................................................................2-2 2.1.2 Overview of Time Synchronization.......................................................................................................2-2 2.1.3 Introduction to the NTP/SNTP...............................................................................................................2-3 2.1.4 Time Synchronization Modes of Huawei Mobile Network...................................................................2-6 2.2 Setting Time Information for the M2000 Server..........................................................................................2-12 2.2.1 Modifying the Date and Time on the M2000 Server...........................................................................2-12 2.2.2 Modifying the Time Zone on the M2000 Server.................................................................................2-14 2.2.3 Setting the NTP Service for the M2000 Server....................................................................................2-17 2.2.4 Stopping the NTP Service on the M2000 Server.................................................................................2-18 2.2.5 Setting the DST for the M2000 ...........................................................................................................2-18 2.3 Setting the NTP Service for the M2000 Server.............................................................................................2-19 2.3.1 Time Synchronization Solution for Huawei Mobile Network.............................................................2-19 2.3.2 Checking the Time Settings on the M2000 Server .............................................................................2-20 2.3.3 Setting the M2000 Administration Console as the Secondary NTP Server.........................................2-20 2.3.4 Starting the NTP Service on the M2000 Administration Console.......................................................2-21 2.3.5 Checking the Running Status of the NTP Service on the M2000 Administration Console.................2-22 2.3.6 Setting the M2000 Server as the NTP Client.......................................................................................2-23 2.3.7 Starting the NTP Service on the M2000 Server...................................................................................2-24 2.3.8 Checking the Running Status of the NTP Service on the M2000 Server............................................2-24 Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd i
Contents
2.4 Setting the DST for the M2000 ....................................................................................................................2-25 2.4.1 Introduction to the DST........................................................................................................................2-26 2.4.2 Viewing the DST Rules of a Time Zone .............................................................................................2-26 2.4.3 Modifying the Time Zone on the M2000 Server.................................................................................2-28 2.5 Setting the Time Information on the M2000 Client......................................................................................2-31 2.5.1 Modifying the Date, Time, and Time Zone on the M2000 Client.......................................................2-31 2.5.2 Setting the NTP Service on the M2000 Client.....................................................................................2-32
3 Setting the Host Name and IP Address for the M2000 Server.......................................... 3-1
3.1 Modifying the Host Name of the M2000 Server.............................................................................................3-2 3.2 Modifying the IP Address of the M2000 Server.............................................................................................3-4 3.2.1 Setting a Default Route on the M2000 Server.......................................................................................3-4 3.2.2 Adding or Deleting Routes on the M2000 Server..................................................................................3-5 3.2.3 Modifying the IP Address of the M2000 Server....................................................................................3-6 3.3 Modifying the IP Address of the SC on the M2000 Server..........................................................................3-10 3.3.1 Modifying the IP Address of the SC on the Netra 240 Server.............................................................3-10 3.3.2 Changing the IP Address of the RSC on the V890 Server...................................................................3-11 3.3.3 Modifying the IP Address of the SC on the E4900 Server..................................................................3-12 3.4 Modifying the IP Address of the Disk Array................................................................................................3-14 3.4.1 Modifying the IP Address of the 3320 Disk Array..............................................................................3-14 3.4.2 Modifying the IP Address of the 6140 Disk Array..............................................................................3-15
4 Managing the M2000 Clients...................................................................................................4-1

4.1 Managing Files and Disks on M2000 Clients.................................................................................................4-2 4.1.1 Introduction to the M2000 Client File System.......................................................................................4-2 4.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................4-4 4.2 Setting the Maximum Number of Sessions.....................................................................................................4-4 4.3 Monitoring the Login Status of Clients...........................................................................................................4-5 4.4 Setting the Number of Clients Accessible on a PC.........................................................................................4-6 4.5 Setting the Time Information on the M2000 Client........................................................................................4-7 4.5.1 Modifying the Date, Time, and Time Zone on the M2000 Client.........................................................4-7 4.5.2 Setting the NTP Service on the M2000 Client.......................................................................................4-7
5 Managing the M2000 Users......................................................................................................5-1

5.1 Types of M2000 Users....................................................................................................................................5-3 5.1.1 Introduction to Solaris Users..................................................................................................................5-3 5.1.2 Introduction to Sybase Users..................................................................................................................5-5 5.1.3 NE User..................................................................................................................................................5-5 5.1.4 Principles of NM User Authorization....................................................................................................5-6 5.1.5 Principles of NE User Authorization.....................................................................................................5-7 5.2 Managing Solaris Users..................................................................................................................................5-8 5.2.1 Introduction to Solaris Users..................................................................................................................5-8 5.2.2 Changing the Password of User root....................................................................................................5-10 5.2.3 Changing the Password of User dbuser................................................................................................5-10 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
Contents
5.2.4 Changing the Password of User omcuser.............................................................................................5-11 5.2.5 Changing the Password of the ftpuser User.........................................................................................5-11 5.2.6 Creating a Solaris User.........................................................................................................................5-13 5.2.7 Deleting a Solaris User.........................................................................................................................5-14 5.3 Managing Sybase Users................................................................................................................................5-14 5.3.1 Introduction to Sybase Users................................................................................................................5-14 5.3.2 Changing the Password of User sa.......................................................................................................5-15 5.4 Creating OM Users........................................................................................................................................5-16 5.4.1 Process for Creating OM Users............................................................................................................5-17 5.4.2 Creating an OM User Group................................................................................................................5-19 5.4.3 Set the Managed Domain for an OM User Group...............................................................................5-19 5.4.4 Assigning Operation Rights to an OM User Group.............................................................................5-20 5.4.5 Assigning Rights of New NEs to an OM User Group.........................................................................5-20 5.4.6 Granting MML Authority to an OM User Group................................................................................5-21 5.4.7 Creating an OM User Account.............................................................................................................5-22 5.4.8 Synchronize OM user data...................................................................................................................5-22 5.4.9 Adding an OM User to a User Group..................................................................................................5-23 5.4.10 Assigning Operation Rights to an OM User......................................................................................5-23 5.4.11 Setting the Managed Domain for an OM User..................................................................................5-24 5.4.12 Setting the User ACL.........................................................................................................................5-25 5.4.13 Grant MML authority to an OM user.................................................................................................5-25 5.5 Modifying an OM User.................................................................................................................................5-26 5.5.1 Viewing the Details of an OM User.....................................................................................................5-27 5.5.2 Modifying the Authority to an OM User.............................................................................................5-27 5.5.3 Modifying the Authority to an OM User.............................................................................................5-31 5.5.4 Modifying the Information of an OM User..........................................................................................5-34 5.5.5 Modifying the Password of an OM User ............................................................................................5-35 5.6 Deleting an OM User Group.........................................................................................................................5-35 5.7 Deleting an OM User....................................................................................................................................5-36 5.8 Querying Authorization.................................................................................................................................5-36 5.9 Comparing the OM User Rights....................................................................................................................5-37 5.10 Managing NE Users....................................................................................................................................5-37 5.10.1 Creating an NE User..........................................................................................................................5-38 5.10.2 Deleting an NE User..........................................................................................................................5-38 5.10.3 Changing the Password of an NE User..............................................................................................5-39 5.10.4 Associating OM User with NE User..................................................................................................5-40 5.10.5 Disassociating OM User with NE User..............................................................................................5-41 5.11 Monitoring OM Users.................................................................................................................................5-41 5.11.1 User Operation Logs..........................................................................................................................5-42 5.11.2 User Sessions......................................................................................................................................5-42 5.11.3 Viewing Operation of OM Users on the M2000................................................................................5-42 5.11.4 Viewing Operation of NE Users........................................................................................................5-43 Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd iii
Contents
M2000 Administrator Guide (S10) 5.11.5 Setting the Status of Special NE User................................................................................................5-44 5.11.6 Forcing an OM User to Exit from the M2000....................................................................................5-44 5.11.7 Forcing an NE User to Exit from the LMT........................................................................................5-45 5.11.8 Unlocking an OM User......................................................................................................................5-45 5.11.9 Setting OM User Auto-Locking.........................................................................................................5-45
6 Monitoring the M2000...............................................................................................................6-1

6.1 Monitoring the M2000 on the M2000 Client..................................................................................................6-2 6.1.1 Introduction to the M2000 System Monitor Browser............................................................................6-2 6.1.2 Introduction to the M2000 System Log................................................................................................. 6-3 6.1.3 Viewing the CPU and Memory Usages of the M2000 Server...............................................................6-4 6.1.4 Viewing the Disk Usage of the M2000 Server on the M2000 Client....................................................6-5 6.1.5 Viewing the Database Usage of the M2000 Server on the M2000 Client.............................................6-5 6.1.6 Viewing M2000 Services.......................................................................................................................6-6 6.1.7 Viewing the States of M2000 Processes................................................................................................6-6 6.1.8 Setting Alarm Thresholds for the M2000.............................................................................................. 6-7 6.1.9 Viewing M2000 Logs.............................................................................................................................6-8 6.2 Monitoring the M2000 on the M2000 Server................................................................................................. 6-9 6.2.1 Viewing Solaris Logs...........................................................................................................................6-10 6.2.2 Periodically Monitoring the CPU, Memory, and Disk.........................................................................6-10 6.2.3 Viewing the Database Usage of the M2000 Server Using Sybase Commands...................................6-12 6.2.4 Viewing the Disk Usage of the M2000 Server Using Solaris Commands...........................................6-13 6.3 Monitoring the Login Status of Clients.........................................................................................................6-13
7 Managing M2000 Processes and Services..............................................................................7-1

7.1 Introduction to M2000 Processes and Services...............................................................................................7-2 7.1.1 lic_agent Process....................................................................................................................................7-4 7.1.2 em_agent Process...................................................................................................................................7-4 7.1.3 monitor_agent Process........................................................................................................................... 7-5 7.1.4 partition_agent Process.......................................................................................................................... 7-5 7.1.5 omcne_agent Process............................................................................................................................. 7-5 7.1.6 sm_agent Process................................................................................................................................... 7-5 7.1.7 med_agent Process.................................................................................................................................7-5 7.1.8 ifms_agent Process.................................................................................................................................7-6 7.1.9 manager_agent Process..........................................................................................................................7-6 7.1.10 pm_agent Process.................................................................................................................................7-6 7.1.11 cmserver_agent Process....................................................................................................................... 7-6 7.1.12 swm_agent Process.............................................................................................................................. 7-7 7.1.13 fmnotify_agent Process........................................................................................................................7-7 7.1.14 proxy_agent Process.............................................................................................................................7-7 7.1.15 notify_agent Process............................................................................................................................ 7-7 7.1.16 pmexp_agent Process...........................................................................................................................7-7 7.1.17 irp_agent Process..................................................................................................................................7-8 7.1.18 pmmon_agent Process..........................................................................................................................7-9 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
Contents
7.1.19 tm_agent Process..................................................................................................................................7-9 7.1.20 snmp_agent Process.............................................................................................................................7-9 7.1.21 nimserver_agent Process......................................................................................................................7-9 7.1.22 neuser_agent Process..........................................................................................................................7-10 7.1.23 log_agent Process...............................................................................................................................7-10 7.1.24 itmserver_agent Process.....................................................................................................................7-10 7.1.25 fmexport_agent Process.....................................................................................................................7-10 7.1.26 devdoc_agent Process........................................................................................................................7-11 7.1.27 cmdc_agent Process...........................................................................................................................7-11 7.1.28 chr_agent Process...............................................................................................................................7-11 7.1.29 3rdTool_agent Process.......................................................................................................................7-11 7.1.30 am_agent Process...............................................................................................................................7-11 7.1.31 threshold_agent Process.....................................................................................................................7-12 7.1.32 objgrp_agent Process..........................................................................................................................7-12 7.1.33 nms_mml_agent Process....................................................................................................................7-12 7.1.34 scriptserver_agent Process.................................................................................................................7-12 7.1.35 mmlproxyserver_agent Process..........................................................................................................7-12 7.1.36 maintain_agent Process......................................................................................................................7-13 7.1.37 nhcserver_agent Process....................................................................................................................7-13 7.1.38 porttrunk_agent Process.....................................................................................................................7-13 7.1.39 NodeBCommission_agent Process....................................................................................................7-13 7.1.40 udpdispatch_agent Process.................................................................................................................7-14 7.1.41 nelicense_agent Process.....................................................................................................................7-14 7.1.42 nicserver_agent Process.....................................................................................................................7-14 7.1.43 pmmedexp_agent Process..................................................................................................................7-14 7.1.44 cpm_agent Process.............................................................................................................................7-14 7.1.45 ce_agent Process................................................................................................................................7-15 7.1.46 imapds_agent Process........................................................................................................................7-15 7.1.47 prssum_agent Process........................................................................................................................7-15 7.1.48 prsreport_agent Process......................................................................................................................7-15 7.2 Managing M2000 Processes..........................................................................................................................7-16 7.2.1 Viewing the Number of M2000 Processes...........................................................................................7-16 7.2.2 Viewing the States of M2000 Processes..............................................................................................7-16 7.3 Managing M2000 Services............................................................................................................................7-17 7.3.1 Viewing M2000 Services.....................................................................................................................7-17 7.3.2 Viewing the States of M2000 Services................................................................................................7-18 7.3.3 Starting M2000 Services......................................................................................................................7-20 7.3.4 Stopping M2000 Services....................................................................................................................7-21
8 Managing the M2000 Databases..............................................................................................8-1

8.1 Introduction to M2000 Databases...................................................................................................................8-2 8.1.1 omcdb Database.....................................................................................................................................8-3 8.1.2 omclogdb Database................................................................................................................................8-3 Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd v
Contents
M2000 Administrator Guide (S10) 8.1.3 omcsmdb Database.................................................................................................................................8-4 8.1.4 omctmdb Database.................................................................................................................................8-5 8.1.5 fmdb Database........................................................................................................................................8-5 8.1.6 pmdb Database.......................................................................................................................................8-6 8.1.7 swmdb Database.....................................................................................................................................8-8 8.1.8 pmcomdb Database................................................................................................................................8-8 8.1.9 sumdb Database......................................................................................................................................8-9 8.1.10 itfndb Database...................................................................................................................................8-11
8.2 Viewing the States of M2000 Databases ......................................................................................................8-12 8.2.1 Viewing the Database Usage of the M2000 Server on the M2000 Client...........................................8-12 8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands...................................8-13 8.3 Clearing M2000 Databases...........................................................................................................................8-14 8.4 Backing Up M2000 Databases......................................................................................................................8-16
9 Managing the M2000 Files and Disks ...................................................................................9-1

9.1 Managing Files and Disks on M2000 Clients.................................................................................................9-2 9.1.1 Introduction to the M2000 Client File System.......................................................................................9-2 9.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................9-3 9.2 Managing Files and Disks on the M2000 Server............................................................................................9-4 9.2.1 Introduction to the M2000 Server File System......................................................................................9-5 9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000 Client....................................................9-8 9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands.............................................9-9 9.2.4 Clearing the Disk Space of the M2000 Server.......................................................................................9-9
10 Backing Up and Restoring the M2000................................................................................10-1

10.1 M2000 Backup and Restore Solutions........................................................................................................10-2 10.1.1 Backup of M2000 Dynamic Data.......................................................................................................10-2 10.1.2 Backup of M2000 Static Data............................................................................................................10-3 10.1.3 Backup of M2000 System Data.........................................................................................................10-4 10.1.4 Policies of M2000 Data Backup.........................................................................................................10-5 10.1.5 Scenarios of M2000 Data Restoration...............................................................................................10-6 10.2 Backing Up and Restoring M2000 Dynamic Data......................................................................................10-7 10.2.1 Backup of M2000 Dynamic Data.......................................................................................................10-7 10.2.2 Setting the Storage Device of Backup Data.......................................................................................10-9 10.2.3 Setting the Wait Time for Replacing a Tape....................................................................................10-11 10.2.4 Backing Up M2000 Dynamic Data Periodically..............................................................................10-12 10.2.5 Backing Up M2000 Dynamic Data Manually..................................................................................10-15 10.2.6 Restoring M2000 Dynamic Data......................................................................................................10-17 10.3 Backing Up and Restoring M2000 Static Data.........................................................................................10-19 10.3.1 Backup of M2000 Static Data..........................................................................................................10-19 10.3.2 Backing Up M2000 Static Data.......................................................................................................10-20 10.3.3 Restoring M2000 Static Data...........................................................................................................10-22 10.4 Backing Up and Restoring M2000 System Data......................................................................................10-28 10.4.1 Backup of M2000 System Data.......................................................................................................10-28 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
Contents
10.4.2 Backing Up M2000 System Data.....................................................................................................10-29 10.4.3 Restoring M2000 System Data........................................................................................................10-32
11 M2000 Routine Maintenance...............................................................................................11-1

11.1 M2000 Routine Maintenance Items............................................................................................................11-4 11.2 Checking the Configuration of Alarm Timing............................................................................................11-6 11.3 Checking the Configuration of Automatic Log Dump................................................................................11-7 11.4 Checking the Synchronization Time of NE Log.........................................................................................11-8 11.5 Checking the Configuration of the File Server ..........................................................................................11-9 11.6 Checking the Configuration of System Backup..........................................................................................11-9 11.7 Checking the Configuration of System Monitoring..................................................................................11-10 11.8 Checking the Synchronization Time of NE Configuration.......................................................................11-11 11.9 Checking the Performance Measurement State.........................................................................................11-11 11.10 Checking the Missing Performance Result.............................................................................................11-12 11.11 Checking the Alarm Reception...............................................................................................................11-12 11.12 Checking the NMS Connection...............................................................................................................11-13 11.13 Checking the Functionality of Alarm Box..............................................................................................11-13 11.14 Checking the Threshold of Network Management Capability................................................................11-14 11.15 Checking OMC Alarms...........................................................................................................................11-14 11.16 Checking Connections Between the M2000 and NEs............................................................................11-18 11.17 Checking the Status of the M2000 Routes..............................................................................................11-18 11.18 Checking M2000 Logs............................................................................................................................11-19 11.19 Checking the Error Log of the Solaris....................................................................................................11-19 11.20 Checking the Disk Usage of the M2000 Server......................................................................................11-20 11.21 Checking the States of M2000 Databases...............................................................................................11-21 11.22 Checking the Number of M2000 Processes............................................................................................11-21 11.23 Checking the States of M2000 Services..................................................................................................11-22 11.24 Checking the Core Files on the Server....................................................................................................11-22 11.25 Backing Up the M2000 ..........................................................................................................................11-23 11.26 Checking the Time of the M2000 Server................................................................................................11-26 11.27 Checking the States of M2000 Disks......................................................................................................11-26 11.28 Checking the Power Supply of the M2000 Server..................................................................................11-27 11.29 Checking the Hardware of the M2000 Server.........................................................................................11-28 11.30 Checking the Peripherals of the M2000 Server......................................................................................11-29 11.31 Checking the SMC Collection Results....................................................................................................11-29
12 M2000 Emergency Maintenance..........................................................................................12-1

12.1 Guide to Emergency Maintenance of the M2000 Server............................................................................12-2 12.2 Guide to Emergency Maintenance of the M2000 Client.............................................................................12-2 12.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure...................................12-2 12.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss of System Files.......................................12-3 12.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You to Run fsck Manually........................................................................................................................................................12-4 12.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System..............12-4 Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd vii
Contents
M2000 Administrator Guide (S10) 12.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact........................12-5
13 Troubleshooting the M2000.................................................................................................13-1

13.1 Procedure for Troubleshooting the M2000 ................................................................................................13-2 13.2 Collecting M2000 Site and Software Information......................................................................................13-3 13.2.1 Collecting the M2000 Site Information.............................................................................................13-3 13.2.2 Collecting the Time of M2000 Fault Occurrence..............................................................................13-4 13.2.3 Collecting the IP Address of the M2000 Server................................................................................13-4 13.2.4 Collecting the Solaris Version............................................................................................................13-4 13.2.5 Collecting the Sybase Version...........................................................................................................13-5 13.2.6 Collecting the M2000 Version...........................................................................................................13-5 13.3 Collecting Fault Data Using the M2000 Log Information Collector..........................................................13-6
14 M2000 Command Reference................................................................................................14-1

14.1 M2000 Commands......................................................................................................................................14-2 14.1.1 svc_profile.sh Script...........................................................................................................................14-2 14.1.2 start_svc Command............................................................................................................................14-3 14.1.3 stop_svc Command............................................................................................................................14-4 14.1.4 kill_svc Command..............................................................................................................................14-4 14.1.5 svc_adm -cmd status Command.........................................................................................................14-5 14.1.6 svc_ps Command...............................................................................................................................14-5 14.1.7 svc_adm -cmd reload Command........................................................................................................14-5 14.1.8 svc_stacks Command.........................................................................................................................14-6 14.1.9 svc_adm -cmd status -sysagent all Command....................................................................................14-6 14.2 UNIX Commands........................................................................................................................................14-7 14.2.1 Commands for Operating UNIX Folders...........................................................................................14-7 14.2.2 Commands for Operating UNIX Files.............................................................................................14-11 14.2.3 Commands for Viewing UNIX Text Files.......................................................................................14-25 14.2.4 Commands for Managing UNIX Users............................................................................................14-32 14.2.5 Commands for Managing UNIX System Resources........................................................................14-36 14.2.6 Commands for Network Communication on the UNIX System......................................................14-53
15 FAQ About the M2000...........................................................................................................15-1

15.1 FAQ About the Solaris................................................................................................................................15-2 15.1.1 How to Log In as the root User Through Telnet................................................................................15-2 15.1.2 How to Log In as the root User Through FTP...................................................................................15-3 15.1.3 How to Check the Status of the Tape Drive.......................................................................................15-3 15.1.4 How to Select the Tape Drive............................................................................................................15-4 15.1.5 What Do the files in the etc/rc2.d Folder of Solaris Mean.................................................................15-5 15.1.6 How to View the Hardware Settings of the M2000 Server................................................................15-6 15.1.7 How to Solve Auto Solaris Shutdown When Connection Between the Server and the TC Is Broken .......................................................................................................................................................................15-7 15.1.8 How to Check the Device Status of the M2000 Server......................................................................15-7 15.1.9 Why Cannot Enter the Domain Console of Sun Fire E4900............................................................15-10 15.1.10 How to Change the Port Number of the FTP Server?....................................................................15-11 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
Contents
15.1.11 How to Query a Time Zone Name.................................................................................................15-12 15.2 FAQ About the Sybase..............................................................................................................................15-14 15.2.1 How to Know Whether the Sybase Is Started..................................................................................15-14 15.2.2 How to Start the Sybase...................................................................................................................15-15 15.2.3 How to Stop the Sybase...................................................................................................................15-15 15.2.4 How to View the Name of the Sybase Server..................................................................................15-16 15.2.5 How to Handle Database Alarms.....................................................................................................15-16 15.2.6 How to View Database Deadlock Information................................................................................15-17 15.2.7 Why the Sybase Is Not Started After the M2000 Is Restarted.........................................................15-18 15.2.8 Why the Sybase Is Not Started After Run svc_profile.sh................................................................15-19 15.2.9 How to Solve Sybase Backup Abort................................................................................................15-20 15.2.10 How to Handle the Problem That the Mouse Pointer Changes into an Hourglass upon History Alarm Query...........................................................................................................................................................15-20 15.3 FAQ About the TCP/IP Network..............................................................................................................15-22 15.3.1 Why the Network Port Is Abnormal................................................................................................15-22 15.3.2 How to Connect the Client to the Server with More than One IP Address......................................15-22 15.4 FAQ About the M2000 Server Software...................................................................................................15-23 15.4.1 Why M2000 Services Restart Abnormally......................................................................................15-24 15.4.2 Why M2000 Services Stop Abnormally..........................................................................................15-24 15.4.3 Why M2000 Services Fail to Start or Stop......................................................................................15-25 15.4.4 Why M2000 Dynamic Data Backup Fails.......................................................................................15-25 15.4.5 How to Back Up and Restore the M2000 Mediation Software........................................................15-27 15.4.6 How to Back Up the M2000 Configuration Files............................................................................15-30 15.4.7 How to Restore the M2000 Configuration Files..............................................................................15-31
Index.................................................................................................................................................i-1
Issue 05 (2008-05-20)
ix
Figures
Figures
Figure 1-1 Netra240 server...................................................................................................................................1-2 Figure 1-2 6140 disk array................................................................................................................................... 1-4 Figure 1-3 V890 server.........................................................................................................................................1-5 Figure 1-4 6140 disk array................................................................................................................................... 1-6 Figure 1-5 6140 disk array................................................................................................................................... 1-7 Figure 1-6 E4900 server.......................................................................................................................................1-8 Figure 1-7 6140 disk array.................................................................................................................................1-10 Figure 2-1 NTP rationale......................................................................................................................................2-4 Figure 2-2 NTP layered architecture....................................................................................................................2-5 Figure 2-3 Schematic diagram of time synchronization for device A..................................................................2-7 Figure 2-4 Directly connecting device A and the NTP server............................................................................. 2-9 Figure 2-5 Networking of device A and the intermediate-layer NTP server.....................................................2-10 Figure 2-6 Directly connecting device A to the highest layer NTP server........................................................2-11 Figure 6-1 System monitor configurations...........................................................................................................6-8 Figure 8-1 Periodic backup................................................................................................................................8-17 Figure 8-2 Periodic backup................................................................................................................................8-18 Figure 10-1 Periodic backup............................................................................................................................10-13 Figure 10-2 Periodic backup............................................................................................................................10-14 Figure 10-3 Manual backup.............................................................................................................................10-16 Figure 11-1 Periodic backup............................................................................................................................11-24 Figure 11-2 Periodic backup............................................................................................................................11-25 Figure 13-1 M2000 Log Information Collector dialog box...............................................................................13-7
Issue 05 (2008-05-20)
xi
Tables
Tables
Table 2-1 File timezone_svc_ex.xml.................................................................................................................2-15 Table 2-2 File timezone_svc_ex.xml.................................................................................................................2-29 Table 3-1 Adding or deleting a route....................................................................................................................3-6 Table 3-2 Parameters for the standby controller.................................................................................................3-12 Table 3-3 Parameters for the standby controller.................................................................................................3-13 Table 4-1 Parameter description...........................................................................................................................4-2 Table 4-2 Folders related to the M2000 client software.......................................................................................4-3 Table 5-1 Solaris user accounts............................................................................................................................5-4 Table 5-2 Privileges of M2000 users....................................................................................................................5-6 Table 5-3 Solaris user accounts............................................................................................................................5-9 Table 5-4 Simple process for creating OM users...............................................................................................5-17 Table 5-5 Complete Process for Creating OM Users.........................................................................................5-18 Table 6-1 Description of the system logs.............................................................................................................6-3 Table 6-2 Recommended alarm thresholds..........................................................................................................6-8 Table 8-1 Names and functions of tables in the omcdb database.........................................................................8-3 Table 8-2 Names and functions of the tables in the omclogdb database..............................................................8-3 Table 8-3 Tables of the omcsmdb database and the corresponding functions.....................................................8-4 Table 8-4 Names and functions of the tables in the omctmdb database...............................................................8-5 Table 8-5 Tables of the fmdb database and the corresponding functions............................................................8-6 Table 8-6 Counter tables in the pmdb database and the corresponding functions...............................................8-7 Table 8-7 Template tables in the pmdb database and the corresponding functions.............................................8-7 Table 8-8 Function subset tables and period tables in the pmdb database and the corresponding functions ...............................................................................................................................................................................8-7 Table 8-9 Tables of the swmdb database and the corresponding functions.........................................................8-8 Table 8-10 Counter information tables in the pmcomdb database and the corresponding functions...................8-8 Table 8-11 Template information tables in the pmcomdb database and the corresponding functions................8-9 Table 8-12 Summary data tables in the sumdb database and their functions.....................................................8-10 Table 8-13 History information tables in the sumdb database and the corresponding functions.......................8-10 Table 8-14 Configuration information tables in the sumdb database and the corresponding functions............8-11 Table 8-15 Tables of the itfndb database and the corresponding functions.......................................................8-11 Table 9-1 Parameter description...........................................................................................................................9-2 Table 9-2 Folders related to the M2000 client software.......................................................................................9-2 Table 9-3 Directories related to the M2000 server software................................................................................9-5 Table 9-4 Planning for Server Disk Partitioning (Netra 240)..............................................................................9-7 Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xiii
Tables
M2000 Administrator Guide (S10) Table 9-5 Planning for Disk Partitioning on the Server(V890)............................................................................9-7 Table 9-6 Planning for Server Disk Partitioning (E4900)....................................................................................9-8 Table 10-1 Introduction to dynamic data backup...............................................................................................10-2 Table 10-2 Introduction to the static data backup.............................................................................................. 10-4 Table 10-3 Introduction to system data backup..................................................................................................10-4 Table 10-4 Typical scenarios for M2000 data backup....................................................................................... 10-5 Table 10-5 Data restore solutions for typical scenarios......................................................................................10-7 Table 10-6 Introduction to dynamic data backup...............................................................................................10-8 Table 10-7 Values for the backupMedia parameter.........................................................................................10-10 Table 10-8 Introduction to the static data backup............................................................................................10-20 Table 10-9 Introduction to system data backup................................................................................................10-28 Table 10-10 Encapsulating the local disks of a server.....................................................................................10-36 Table 10-11 Mirroring the disks of the M2000 server.....................................................................................10-37 Table 11-1 Maintenance item list.......................................................................................................................11-4 Table 11-2 Recommended alarm thresholds....................................................................................................11-10 Table 11-3 Fault alarms requiring for immediate handling..............................................................................11-14 Table 11-4 Fault alarms requiring for handling within half an hour................................................................11-15 Table 11-5 Fault alarms requiring for handling within a day...........................................................................11-15 Table 11-6 Fault alarms requiring for attention during network expansion.....................................................11-16 Table 11-7 Fault alarms on malicious actions..................................................................................................11-16 Table 11-8 Event alarms requiring immediate handling..................................................................................11-16 Table 11-9 Event alarms requiring for handling within a day..........................................................................11-17 Table 11-10 Event alarms requiring your attention during network expansion...............................................11-17 Table 14-1 Option description of the ls command...........................................................................................14-10 Table 14-2 Common options in symbol mode of the chmod command .........................................................14-14 Table 14-3 Conditions for file search...............................................................................................................14-18 Table 14-4 Logical operators of conditions......................................................................................................14-18 Table 14-5 Option description for the tar command.......................................................................................14-20 Table 14-6 Descriptions of gtar command options..........................................................................................14-21 Table 14-7 Option description of the echo command......................................................................................14-26 Table 14-8 Option description of the more command......................................................................................14-28 Table 14-9 Operations in the text input mode..................................................................................................14-31 Table 14-10 Operations related to moving the cursor in the text input mode..................................................14-31 Table 14-11 Operation for exiting the text input mode and switching to the command mode........................14-31 Table 14-12 Operations related to deleting characters in the command mode.................................................14-32 Table 14-13 Commands for exiting the vi editor.............................................................................................14-32 Table 14-14 Option description of the useradd command...............................................................................14-33 Table 14-15 Option description of the usermod command..............................................................................14-34 Table 14-16 Description of the uname options................................................................................................14-46 Table 14-17 Format of the command output....................................................................................................14-49 Table 14-18 Common ftp commands...............................................................................................................14-56 Table 14-19 Examples of the finger command................................................................................................14-58
xiv
Issue 05 (2008-05-20)
Tables
Table 14-20 Description of routing flags.........................................................................................................14-59 Table 14-21 Description of the route commands.............................................................................................14-60 Table 15-1 Tape drive status..............................................................................................................................15-4 Table 15-2 Checking the server configuration...................................................................................................15-6 Table 15-3 Commands for checking the device status.......................................................................................15-7 Table 15-4 Example of the matching table between countries and time zone names......................................15-13
Issue 05 (2008-05-20)
xv
About This Document
About This Document
Purpose
This document provides the system administration tasks, the related concepts, the detailed operation procedures of the system administration tasks, the routine maintenance, and the troubleshooting and emergency maintenance. The document is used in the following situations:
l l l
The operating system is Solaris 10. The database device is a bare device. The database is Sybase15.
Related Versions
The following table lists the product versions related to this document. Product Name M2000 Version V200R006
Intended Audience
The intended audiences of this document are network administrators.
Update History 05 (2008-05-20)

Formal release for the fifth time. Compared with the V200R006 04 (2008-03-03), this version incorporates the following new contents:
l l l l
7.1.45 ce_agent Process. 7.1.46 imapds_agent Process. 7.1.47 prssum_agent Process. 7.1.48 prsreport_agent Process.
Compared with the V200R006 04 (2008-03-03), this version has the following modifications:
Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1
About This Document

l l
The sac_agent process is renamed as lic_agent. The step descriptions are optimized in 3.1 Modifying the Host Name of the M2000 Server.
Compared with the V200R006 04 (2008-03-03), this version deletes the following contents:
l l l l
sumdata_agent process sumreport_agent process 3gpp_agent process mml_agent process
04 (2008-03-03)
Formal release for the third time. Compared with the V200R006 03 (2008-01-08), this document has no contents that are deleted, the new contents are as follows:
l l
7.1.40 udpdispatch_agent Process. 10.2.3 Setting the Wait Time for Replacing a Tape.
Compared with the V200R006 03 (2008-01-08), the modifications are as follows: Involved Scope 6.1.1 Introduction to the M2000 System Monitor Browser 3.2.3 Modifying the IP Address of the M2000 Server Description Some figure descriptions are modified. Some figure descriptions are modified.
03 (2008-01-08)
Formal release for the third time. Compared with the V200R006 02 (2007-10-31), this document has no contents that are deleted, the new contents are as follows:
l l l
15.1.4 How to Select the Tape Drive. 2.3.4 Starting the NTP Service on the M2000 Administration Console. 2.3.5 Checking the Running Status of the NTP Service on the M2000 Administration Console.
Compared with the V200R006 02 (2007-10-31), the modifications are as follows: Involved Scope 10.2.2 Setting the Storage Device of Backup Data Description Some figure descriptions are modified.
Issue 05 (2008-05-20)
About This Document
02 (2007-10-31)
Formal release for the second time. Compared with the V200R006 01 (2007-10-17), this document has no contents that are added or deleted. The modifications are as follows: Involved Scope 3.4.1 Modifying the IP Address of the 3320 Disk Array 3.4.2 Modifying the IP Address of the 6140 Disk Array Description Some figure descriptions are modified. Some figure descriptions are modified.
01 (2007-10-17)
This is the initial field trial release.
Organization
1 Powering On/Off the M2000 This describes how to power on or power off the M2000 when Netra 240, V890, or E4900 serves as the M2000 server. 2 Setting the M2000 Time This describes how to set the M2000 time. To enable the M2000 time to meet the time requirements, you must synchronize the time of the M2000 with the time of the other Huawei devices in the Huawei mobile network. 3 Setting the Host Name and IP Address for the M2000 Server This describes how to set the host name and the IP address of the M2000 server, according to field requirements. 4 Managing the M2000 Clients This describes how to manage the M2000 clients. The graphic user interface (GUI) on the M2000 client supports the O&M for the NEs and enables you to monitor the M2000. You must manage the M2000 clients to ensure their normal operation. 5 Managing the M2000 Users This chapter describes the four types of users involved in the operation of the M2000 system: Solaris user, Sybase user, network management user, and NE user. In addition, it describes the management and monitoring operations related to the types of users and M2000 user groups. 6 Monitoring the M2000 This describes how to monitor the usage of the CPU, memory, disk, and database on the M2000 server, the running conditions of M2000 services. You can also monitor the operations of NM users and NE users, and the login status on the client. 7 Managing M2000 Processes and Services
Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3
About This Document
This describes how to manage the M2000 processes and services. 8 Managing the M2000 Databases This chapter describes how to manage the M2000 databases. 9 Managing the M2000 Files and Disks This chapter describes how to manage the file systems and disks on the M2000 server and client. 10 Backing Up and Restoring the M2000 This describes how to back up and restore M2000 data. 11 M2000 Routine Maintenance This chapter describes the maintenance items and the procedures required to conduct the M2000 routine maintenance. These items are, however, only for reference. In real application, specify the maintenance items as required. 12 M2000 Emergency Maintenance This chapter describes the emergency maintenance in the case of a critical fault in the M2000 server or client. This chapter covers the server emergency maintenance, client emergency maintenance, and emergency maintenance for the server power-off. 13 Troubleshooting the M2000 This chapter describes the procedures for troubleshooting the M2000. 14 M2000 Command Reference This describes the functions and usage of M2000 commands. 15 FAQ About the M2000 This chapter describes FAQs and solutions related to the M2000.
Conventions
1. Symbol Conventions The following symbols may be found in this document. They are defined as follows Symbol Description Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results.
Issue 05 (2008-05-20)
DANGER
WARNING
CAUTION
4
About This Document
Symbol
TIP
Description Indicates a tip that may help you solve a problem or save your time. Provides additional information to emphasize or supplement important points of the main text.
NOTE
2. General Conventions Convention Times New Roman Boldface Italic Courier New 3. Command Conventions Convention Boldface Italic [] {x | y | ...} [ x | y | ... ] { x | y | ... } * [ x | y | ... ] * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars.One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars.One or none is selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of one or a maximum of all can be selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of zero or a maximum of all can be selected. Description Normal paragraphs are in Times New Roman. Names of files,directories,folders,and users are in boldface. For example,log in as user root . Book titles are in italics. Terminal display is in Courier New.
4. GUI Conventions Convention Boldface > Description Buttons,menus,parameters,tabs,window,and dialog titles are in boldface. For example,click OK. Multi-level menus are in boldface and separated by the ">" signs. For example,choose File > Create > Folder .
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 5
Issue 05 (2008-05-20)
About This Document
5. Keyboard Operation Convention Key Key1+Key2 Key1,Key2 Description Press the key.For example,press Enter and press Tab. Press the keys concurrently.For example,pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn.For example,pressing Alt,A means the two keys should be pressed in turn.
6. Mouse Operation Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 05 (2008-05-20)
1 Powering On/Off the M2000
1
About This Chapter
Powering On/Off the M2000
This describes how to power on or power off the M2000 when Netra 240, V890, or E4900 serves as the M2000 server. 1.1 Powering On/Off the M2000 (Netra240) This describes how to power on or power off the M2000 when the Netra 240 minicomputer serves as the M2000 server. 1.2 Powering On/Off the M2000 (V890) This describes the procedures for powering on and powering off the M2000 when the V890 minicomputer serves as the M2000 server. 1.3 Powering On/Off the M2000 (E4900) This describes how to power on or power off the M2000 when the E4900 minicomputer serves as the M2000 server.
Issue 05 (2008-05-20)
1-1
1.1 Powering On/Off the M2000 (Netra240)

This describes how to power on or power off the M2000 when the Netra 240 minicomputer serves as the M2000 server. 1.1.1 Powering On the M2000 (Netra240) This describes how to power on the M2000 when the Netra240 minicomputer serves as the M2000 server. 1.1.2 Powering Off the M2000 (Netra 240) This describes how to power off the M2000 when the Netra 240 minicomputer serves as the M2000 server.
1.1.1 Powering On the M2000 (Netra240)

This describes how to power on the M2000 when the Netra240 minicomputer serves as the M2000 server.
Procedure
Step 1 Prepare to power on the M2000. 1. Ensure that the power switches of all devices are set to OFF. If any switch is set to ON, set it to OFF.
NOTE
The devices to be checked include the M2000 server, KVM, networking devices, and cabinet. Perform proper operations to power off the M2000. For details, see 1.1.2 Powering Off the M2000 (Netra 240).
2.
Set the power switch of the cabinet to ON.
Step 2 Power on the Netra240 server. 1. Turn the rotary switch beside the power supply to the normal position (I), as shown in Figure 1-1. Figure 1-1 Netra240 server
2.
Press the On/Standby button of the power switch to start the Netra240 server.
l
If the Solaris operating system is not installed, the system is switched to the ok state after the Netra240 server is powered on. If the Solaris operating system, Sybase, and M2000 server applications are successfully installed, the system automatically starts them. If the system is switched to the ok state,
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
1-2
enter boot to start the operating system. Then the system automatically starts the Sybase and the M2000 applications. 3. Turn the rotary switch to the locked position.
----End
1.1.2 Powering Off the M2000 (Netra 240)

This describes how to power off the M2000 when the Netra 240 minicomputer serves as the M2000 server.
Procedure
Step 1 If the M2000 is running, stop it. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Step 2 If Sybase is running, stop it. For details on how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. Step 3 Switch to user root and power off the Netra 240 server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 Step 4 Set the power switches of the cabinet and the devices in the cabinet to OFF, as required. ----End
1.2 Powering On/Off the M2000 (V890)

This describes the procedures for powering on and powering off the M2000 when the V890 minicomputer serves as the M2000 server. 1.2.1 Powering On the M2000 (V890) This describes how to power on the M2000 when the V890 minicomputer serves as the M2000 server. 1.2.2 Powering Off the M2000 (V890) This describes how to power off the M2000 when the V890 minicomputer serves as the M2000 server.
1.2.1 Powering On the M2000 (V890)

This describes how to power on the M2000 when the V890 minicomputer serves as the M2000 server.
Procedure
Step 1 Prepare to power on the M2000 . 1. Ensure that the power switch of each device in the cabinet are in the OFF state. If any power switch is ON, set it to OFF.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-3
Issue 05 (2008-05-20)

NOTE
The devices to be checked include the M2000 server, disk array, networking devices, and cabinet. Perform proper operations to power off the M2000. For details, see 1.2.2 Powering Off the M2000 (V890).
2.
Step 2 Power on the 6140 disk array. Set the two power switches on the rear of the 6140 disk array to ON. The disk array is shown in Figure 1-2. Figure 1-2 6140 disk array
Step 3 Power on the V890 server. 1. Turn the rotary switch beside the power supply to the normal position (I), as shown in Figure 1-3.
1-4
Issue 05 (2008-05-20)
Figure 1-3 V890 server
1 4
Power switch Normal position
2 5
Rotary switch Lock position
3 6
Forced turn-off Diagnosis position
2.
Press down the power switch to start the V890 server.

l
If the Solaris operating system is not installed, the system is switched to the ok state after the V890 server is powered on. If the Solaris operating system, Sybase, and M2000 server applications are successfully installed, the system automatically starts them. If the system is switched to the ok state, enter boot to start the operating system. Then the system automatically starts the Sybase and the M2000 applications.
3.
Turn the rotary switch to the locked position.
----End
1.2.2 Powering Off the M2000 (V890)

This describes how to power off the M2000 when the V890 minicomputer serves as the M2000 server.
Procedure
Step 1 If the M2000 is running, stop it. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Step 2 If the Sybase is running, stop it. For details on how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. Step 3 Switch to user root and power off the V890 server. # sync; sync; sync; sync; sync; sync
Issue 05 (2008-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-5
# /usr/sbin/shutdown -y -g0 -i5 Step 4 Power off the 6140 disk array. 1. Check whether the I/O activities of the server and the disk array are stopped. Check the LED indicators of the 6140 disk array, as shown in Figure 1-4. Figure 1-4 6140 disk array
NOTE
a. Wait for two minutes. Check whether the LEDs of the cache on the rear of the controller go out. If all the LEDs go out, you can infer that all the data is written into the disk and that the cache does not hold data. b. Ensure that all the LEDs of all the disk drives at the front of controller stop blinking.
2.
Set the two power switches at the rear of the controller to OFF.
Step 5 If required, set the power switches of the cabinet and the devices in the cabinet to OFF. ----End
1.3 Powering On/Off the M2000 (E4900)

This describes how to power on or power off the M2000 when the E4900 minicomputer serves as the M2000 server. 1.3.1 Powering On the M2000 (E4900) This describes how to power on the M2000 when the E4900 minicomputer serves as the M2000 server. 1.3.2 Powering Off the M2000 (E4900)
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)
This describes how to power on the M2000 when the E4900 minicomputer serves as the M2000 server.
1.3.1 Powering On the M2000 (E4900)

Procedure
Step 1 Make the following preparations for powering on the M2000: 1. Ensure that the power switch of each device in the cabinet are in the OFF state. If any power switch is ON, set it to OFF.
NOTE
The devices to be checked include the M2000 server, disk array, Netra 24 administration console, KVM, networking devices, and cabinet. Perform proper operations to power off the M2000. For details, see 1.3.2 Powering Off the M2000 (E4900).
2.
Step 2 Power on the console. On the console, set the power switches of the Netra 240 minicomputer, the display, and all the network equipment to ON. Then, these devices start automatically. Step 3 Power on the 6140 disk array. Set the two power switches on the rear of the 6140 disk array to ON. The disk array is shown in Figure 1-5. Figure 1-5 6140 disk array
Step 4 Power on the E4900 server. 1. Set the power switches of the E4900 server to ON. The E4900 server has three power switches in total, as shown in Figure 1-6. Only two SCs are powered on. The indicators of three power boards are blue.
Issue 05 (2008-05-20)
1-7
Figure 1-6 E4900 server
NOTE
The SC of the E4900 server serves as the console.
2.
Run the telnet command to log in to the SC. Select 0 to open the Platform Shell interface. Run the command setfailover on to enable the failover function. telnet Logical IP address of the SC of the E4900 server
NOTE
If the SC of the E4900 is not configured yet, refer to Configuring SC1 and Configuring SC0 for details on configuration.
3. 4.
To power on all boards, run the poweron all command. All the boards are powered on when all domains are closed. On the Platform Shell interface, run the console -d a command to switch to domain A, and then run the setkeyswitch on command to start domain A. This process lasts for about 20 minutes.
1-8

l
If the enter to domain A fails because the system is busy, troubleshoot the fault by referring to 15.1.9 Why Cannot Enter the Domain Console of Sun Fire E4900. If the Solaris operating system is not installed, the system is switched to the ok state after the E4900 server is powered on. If the Solaris operating system, Sybase, and M2000 server applications are installed successfully, the system automatically starts these operations. If the system is switched to the ok state, enter boot to start the operating system. The system automatically starts the Sybase and the M2000 applications.
----End
1.3.2 Powering Off the M2000 (E4900)

Procedure
Step 1 Stop the M2000 if it is running. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Step 2 Stop the Sybase if it is running. For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. Step 3 Power off the E4900 server. 1. Log in to the E4900 server as user root, and then run the following commands to power off the system: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 2. Run the telnet command to log in to the SC. Select 0 to open the Platform Shell interface. telnet Logical IP address of the SC of the E4900 server
NOTE
l l
If the IP address of the SC is not assigned, use the HyperTerminal to log in from the serial port of the SC. Use the Huawei 04042025 serial port cable to connect the SC and the PC. One end of the Huawei 04042025 serial port cable uses the DB-25 interface, which is inserted into the serial port of the SC. The other end uses the DB-9 interface, which is inserted into one COM port of the PC. The port properties of the HyperTerminal must be restored to the default values. This means that you must set the baud rate to 9600, data digit to 8, parity check to none, stop bit to 1, and data stream control to none.
3.
Run the showkeyswitch command to check which domains are in the ON state. osssvr-sc0:SC> showkeyswitch
Domain Domain Domain Domain A B C D keyswitch keyswitch keyswitch keyswitch is: is: is: is: on off off off
4.
Run the setkeyswitch -d a off command to close domain A. osssvr-sc0:SC> setkeyswitch -d a off
Issue 05 (2008-05-20)
1-9

Powering boards off ...
5.
Run the poweroff all command to power off all the systems. Except the two SCs, all boards including three power boards are powered off. osssvr-sc0:SC> poweroff all
/N0/SB4: is already off /N0/IB6: is already off /N0/IB8: is already off RP0: is already off RP2: is already off PS0: powered off PS1: powered off PS2: powered off osssvr-sc0:SC>
Step 4 Shut down the 6140 disk array. 1. Check whether the I/O activities of the server and the disk array are stopped. Check the LED indicators of the 6140 disk array, as shown in Figure 1-7. Figure 1-7 6140 disk array
NOTE
a. Wait for two minutes. Check whether the LEDs of the cache on the rear of the controller go out. If all the LEDs go out, you can infer that all the data is written into the disk and that the cache does not hold data. b. Ensure that all the LEDs of all the disk drives at the front of controller stop blinking.
2. 1. 2.
1-10
Set the two power switches at the rear of the controller to OFF. Log in to the Netra 240 console as user root. Run the following commands to power off the Netra 240 console:
Step 5 Power off the Netra 240 console.
# sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 Step 6 Shut down the power supplies of all the equipment, such as servers and disk arrays. Shut down the power supply of the cabinet if required. ----End
Issue 05 (2008-05-20)
1-11
2 Setting the M2000 Time
2
About This Chapter
Setting the M2000 Time
This describes how to set the M2000 time. To enable the M2000 time to meet the time requirements, you must synchronize the time of the M2000 with the time of the other Huawei devices in the Huawei mobile network. 2.1 Time Synchronization Solution for Huawei Mobile Network This describes the time synchronization solution of Huawei. By using the time synchronization solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei mobile network equipment. 2.2 Setting Time Information for the M2000 Server The server time is associated with NE data collection, timing task handling, and database information dump. You must ensure that the server time is correct before configuring the NTP service for the server. Therefore, a correct server time is vital to the normal operation of the system. 2.3 Setting the NTP Service for the M2000 Server This describes how to configure the M2000 server as the NTP client. 2.4 Setting the DST for the M2000 To enable the M2000 to support daylight saving time (DST), you must set the time zone of the M2000 server. 2.5 Setting the Time Information on the M2000 Client This describes how to set the time information on the M2000 client.
Issue 05 (2008-05-20)
2-1
2.1 Time Synchronization Solution for Huawei Mobile Network

This describes the time synchronization solution of Huawei. By using the time synchronization solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei mobile network equipment. 2.1.1 Purpose of Time Synchronization The time synchronization function enables you to synchronize the M2000 with other NEs in a mobile network. 2.1.2 Overview of Time Synchronization This defines time synchronization and describes the elements of time synchronization scheme and the impact on system performance and other O&M features. 2.1.3 Introduction to the NTP/SNTP This introduces the rationale of time synchronization and the layered architecture of the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP). 2.1.4 Time Synchronization Modes of Huawei Mobile Network This describes the modes of time synchronization and how to deploy the time synchronization network for the M2000 and NE devices in Huawei mobile network.
2.1.1 Purpose of Time Synchronization

The time synchronization function enables you to synchronize the M2000 with other NEs in a mobile network. The networking mode of a mobile network is complex if the mobile network has multiple NEs. To perform uniform operation and maintenance for NEs in a mobile network, you must synchronize the time of NEs. This ensures that the M2000 correctly manages the alarms and performance data reported by NEs. Inaccurate time may lead to the following scenarios:
l
If the alarm time is inaccurate, the sequence of raised alarms, the interval between alarm raising and alarm reporting, and the associations between alarms may be misjudged. When the M2000 collects the statistics of performance data, the statistics are incorrect owing to inaccurate time.
Therefore, the time synchronization function enables the system to automatically adjust the O&M time of NEs.
2.1.2 Overview of Time Synchronization

This defines time synchronization and describes the elements of time synchronization scheme and the impact on system performance and other O&M features.
Definition of Time Synchronization

Time synchronization refers to the synchronization of the absolute time. The start time of a signal should be consistent with the universal coordinated time (UTC). Time synchronization aims to adjust the time of the devices according to the received time.
Elements of Time Synchronization Scheme

At least two elements are involved in the time synchronization scheme, that is, the method of time synchronization and the choice of time reference.
l
In the architecture of current time synchronization networking, the common method is to realize time synchronization according to the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP). Time reference sources aim to provide the standard reference time for the time synchronization network. This ensures the accuracy of the time reference in the entire network. A common time reference source is the GPS satellite.
Impact on System Performance

If time synchronization is implemented in client/server mode described in the NTP protocol, the message frame between the NTP client and the NTP server is 128 bytes. Therefore, time synchronization does not affect the performance of network transmission. If many NTP clients request to connect to the NTP server at the same time, these connections consume more resources of the NTP server, such as the CPU and the memory of the NTP server. In this case, time synchronization may affect the server performance. Therefore, if you use the NTP protocol to construct a time synchronization network, the number of NTP nodes under a NTP server should not exceed 300. If the number exceeds 300, the performance of the NTP server may be affected. The interval for the time synchronization request of a NTP client should be 30 minutes or longer. In addition, you need reduce the probability of concurrent requests.
Impact on O&M
The time synchronization feature is vital for the O&M of the mobile network. It has the following impact on the other features:
l
Ensure the accuracy and consistency of the time on the network manager (NM) and NEs in the mobile network. Time synchronization plays a key role at fault reporting, information accuracy, and fault correlation analysis in fault management. If the NE time is inaccurate or the NE time is inconsistent with the NM time, a mistake may be made during the fault identification and handling. Have a significant impact on the accuracy of log recording, querying, displaying, auditing, and analyzing. If the NE time is inaccurate or inconsistent with the NM time, the fault identification and handling may be affected. Have a significant impact on recording, collecting, and analyzing performance data in performance management. If the time is inaccurate or the time of NEs in the entire network is not the same, the time of NE performance data records and the dot time may be inaccurate and thus may result in invalid performance data. Have a significant impact on the services such as call tracing and problem locating. If the time is inaccurate or the time of NEs in the entire network is not the same, the call tracing service may fail.
2.1.3 Introduction to the NTP/SNTP

This introduces the rationale of time synchronization and the layered architecture of the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP).
Rationale of NTP Time Synchronization

NTP is used to synchronize the time between the distributed time server and the client. It defines the structure, algorithm, entity, and protocols in the process of time synchronization. Based on the IP and UDP stack protocol in the TCP/IP protocols, NTP can also be used by other protocol groups. Theoretically, the error is less than one nanosecond. Figure 2-1 shows the rationale of NTP time synchronization. Figure 2-1 NTP rationale
Device A and device B communicate through the network. Both devices have their own system time. To implement the automatic synchronization of system clocks, ensure that:
l
Before you synchronize the system time of device A and device B, the time on device A is set to 10:00:00 and the time on device B is set to 11:00:00. Device B is configured as the NTP server. That is, you need synchronize the time on device A with that on device B. The unidirectional transmission of data package between device A and device B takes one second.
To synchronize the time between device A and device B, ensure that the following information is available:
l l
Offset, which is the time difference between device A and device B Delay, which is the loss during the time synchronization between device A and device B
If the previous information is available, device A can easily calculate the time to be adjusted to synchronize with device B. The NTP protocol stipulates the method for calculating the values of the offset and delay between device A and device B. The time synchronization process is as follows: 1. 2. Device A sends an NTP message to device B. The message records the stamp of the leaving time from device A, which is 10:00:00am (T1). When the NTP message reaches device B, device B adds its own time stamp, which is 11:00:01am (T2).
2-4
3. 4.
When the NTP message leaves device B, device B adds its own time stamp again, which is 11:00:02am (T3). When device A receives the response message, it adds a new time stamp, which is 10:00:03am (T4).
After that, device A can calculate the two parameters using the following method:
l l
Delay of a NTP message delivering circle: delay = (T4 - T1) - (T3 - T2). Offset between device A and device B: offset = [(T2 - T1) + (T3 - T4)]/2.
Then, device A can set the time according to this previous information so that device A is synchronized with device B.
Rationale of NTP Layered Architecture

From the origin and purpose of the time synchronization mechanism, you can infer that fewer clock sources enables more uniform time. If a network has a large scale and is very complex, it is time-consuming to connect each device to the same time server if the time of each device needs to be synchronized. In such a case, the layered architecture is applied to the NTP model. Theoretically, the time synchronization network can be classified into 16 levels from 0 to 15, or more than 16 levels on the basis of accuracy and importance. In practice, the number of levels does not exceed six. The device at level 0 is located at the special position of the subnetwork. It provides the reference clock for time synchronization. On the top of the subnet, the device at level 0 uses UTC time codes broadcast by the global positioning system (GPS). The devices in the subnet can play multiple roles. For example, a device on the second layer may be a client to the first layer and a server for the third layer. Figure 2-2 NTP layered architecture
As shown in Figure 2-2, the following servers are configured in the NTP layered architecture:
l
Top level NTP server: level 0 NTP server, which provides the synchronization service for lower level servers (Stratum-1). Medium level NTP server: level 1 and level 2 servers, which acquires time from the upper level server and provides the time for the lower level servers. NTP client: acquires time from upper level NTP server but does not provide time service.
Issue 05 (2008-05-20)
A host can acquire time from multiple NTP servers. An NTP server can also provide time for multiple hosts. Hosts on the same level can exchange time. The NTP protocol supports a maximum of 15 clients.
NOTE
Port 123 is used by NTP during communication through the User Datagram Protocol (UDP). Ensure that all the IP links between the nodes are functional.
Comparison of SNTP and NTP

SNTP is a simplified policy for the NTP server and the NTP client. The difference between SNTP and NTP is that SNTP has disadvantage over the following aspects:
l l l
Handling errors Filtering of multiple servers Choosing among multiple clock sources, that is, acquiring the most accurate clock resource after using an algorithm to analyze multiple connected NTP servers.
2.1.4 Time Synchronization Modes of Huawei Mobile Network

This describes the modes of time synchronization and how to deploy the time synchronization network for the M2000 and NE devices in Huawei mobile network.
Time Synchronization Modes of the M2000

The time synchronization of a mobile network is implemented through the NTP/SNTP protocols. The M2000 server uses the Solaris 8 or the Solaris 10 and supports the NTP features based on NTPV3 protocol versions. By setting the parameters in the file /etc/inet/ntp.conf on the Solaris operating system, you can set the M2000 server as an NTP client in the mobile network. After you specify the IP address of the NTP server for the login of the M2000 server, the M2000 server can obtain the time synchronization information from the specified NTP server. In addition, you can configure the M2000 administration console as an intermediate time server. The M2000 client runs on the Windows 2000 Professional or Windows XP operating system. You need to configure an operating system to support the SNTP client and specify the IP address of the NTP server. Then, the M2000 client can obtain the time synchronization information from the specified NTP server.
Time Synchronization Modes of NEs

l
For an NE with the BAM, the NE time synchronization follows the master/slave networking mode. That is, the host time synchronizes with the BAM and the BAM synchronizes with the NTP server. For an NE without the BAM, the OM board needs to support the NTP protocol. Therefore, the NE can synchronize with the NTP server.
This part takes device A as an example.

l
Rationale of time synchronization for device A
2-6
Issue 05 (2008-05-20)
Figure 2-3 Schematic diagram of time synchronization for device A
The active BAM of device A serves as the NTP client to synchronize the time on each NE node and each module of device A, as shown in Figure 2-3. After the active BAM of device A obtains the reference time from the specified NTP server, the BAM delivers the time to each module of device A and all device B to realize time synchronization.
l
The BAM of device A synchronizes time with the upper-layer NTP server. Device A has two BAM servers, that is, the active and standby BAM servers. In the BAM program of device A, an NTP client process automatically starts after the BAM program and always runs on the active BAM server. By running MML commands, you can specify the upper-layer NTP server as the active BAM server of device A. Then, the NTP client process running on the active BAM automatically obtains the time synchronization information from the specified NTP server. A maximum of 16 NTP server addresses can be specified for the active BAM. The active BAM of device A can perform the synchronization from the preferred time source. If an NTP time source does not work properly, the active BAM can use a new NTP time source to ensure the continuity of the NTP service. When the BAM of device A experiences active and standby switching, the NTP client process is automatically switched to the new active BAM to ensure the continuity of the NTP service.
Time synchronization for each internal module of device A In addition to running the NTP client to synchronize with the external time sources, the active BAM of device A has an SNTP server module for time synchronization between the internal modules. For device A, each internal module has an independent process serving as the SNTP client. The active BAM of device A serves as the SNTP server of all the modules.
Issue 05 (2008-05-20)
2-7
By running the MML commands, you can configure the SNTP server attributes for the active BAM of device A.
l
Time synchronization for the standby BAM of device A If the active and standby BAMs are operational, only the active BAM has the SNTP server, and the SNTP client on the standby BAM is used only to periodically synchronize the time with the active BAM. That is, when the active and standby BAMs are operational, the time of the active BAM is regarded as the reference time. During the time synchronization of the active and standby BAMs, the SNTP client of the standby BAM requests for time synchronization, the SNTP server of the active BAM returns a response message. Then, the standby BAM adjusts the time of the applications and the system based on the response message. The time synchronization of the active and standby BAMs is performed every five minutes. Manual setting of the period is not required because the active and standby BAMs work as a single entity to provide services.
Time synchronization between device B and the BAM of device A The SNTP server of the active BAM provides both the time synchronization service and the time comparison service for the host. The SNTP server of the active BAM periodically broadcasts time synchronization messages to device B and receives the requests for time synchronization from device B. Device B runs an SNTP process and sends requests for time synchronization to the active BAM of device A.
Network of NTP Time Synchronization

The NTP time synchronization network determines the reference time for the network and uses the reference time to specify how device nodes communicate with each other. This part takes device A for example to describe how to choose the reference time for the NTP time synchronization network.
l
Using the NTP server specified by the carrier If the established time synchronization network provides the NTP server that can act as the reference time source, prefer to use the existing NTP server as the time reference source of the RAN network. In this case, the M2000 and the BAM server of device A need to directly communicate with the specified NTP server to obtain standard time signals, as shown in Figure 2-4.
2-8
Issue 05 (2008-05-20)
Figure 2-4 Directly connecting device A and the NTP server
The M2000 server and all the devices must directly communicate with the specified time synchronization server. The NTP server that can serve as the reference time may be deployed in other subnets. Therefore, the communication between the M2000 and device A may involve the policy of traversing the firewall. In such a case, you need to modify the configuration of the firewall.
l
Deploying the intermediate-layer NTP server According to the principle of layered NTP, when constructing an RAN network, you can deploy a dedicated intermediate-layer NTP server in the RAN-OM network to serve as the time reference for the internal RAN devices. The intermediate-layer NTP server obtains the reference time from the upper-layer server, synchronizes its own time, and serves as the NTP server of the RAN network. In such a case, the intermediate-layer NTP server can receive the request on time synchronization from the internal NE devices in the RAN, such as device A and the M2000, and provides standard time, as shown in Figure 2-5.
Issue 05 (2008-05-20)
2-9
Figure 2-5 Networking of device A and the intermediate-layer NTP server
Deploying the intermediate-layer NTP server can effectively simplify the structure of the time synchronization network. It can also prevent too many NEs from directly connecting the highest layer NTP server, thus reducing the risks to the highest layer NTP server. In addition, if a firewall exists between the highest layer NTP server and the RAN network, you need not configure the firewall. You can use the dedicated BITS SYNCLOCK V5 as the NTP intermediate-layer server of device A network. Complying with the NTP V3 protocols, this device can provide two channels of NTP service units and lock multiple upper-layer NTP servers to realize NTP priority. The NTP client provides two channels of NTP service output that are mutually backed up.
2-10
Issue 05 (2008-05-20)

NOTE
The M2000 server uses the Solaris operating system where you can configure the M2000 server as the intermediate-layer NTP server. With regard to that the time synchronization server for the RAN network plays a special role and requires the independent and stable operating environment, Huawei recommends that the M2000 server should not act as the intermediate-layer NTP server for the RAN network. For an HA system or a system using the V890 or E4900 server, the Netra 240 server is integrated as an administration console by default. In this case, the Netra 240 acts as the intermediate-layer NTP server for the RAN network.
Obtaining reference time from the GPS If the upper-layer time synchronization server that can provide the reference time is not available, you should deploy the highest layer NTP server, that is, the NTP server providing the reference time in the RAN-OM network to ensure time synchronization. The highest layer NTP server obtains the reference time from the GPS or other satellite systems and synchronizes time on all the RAN NEs and the M2000. Figure 2-6 shows the networking of device A and the highest layer NTP server. Figure 2-6 Directly connecting device A to the highest layer NTP server
You can use the dedicated BITS SYNCLOCK V5 as the highest layer NTP server of device A. Complying with the NTP V3 protocol, this device can provide two channels of the
satellite access system and two channels of NTP service units. It also provides two channels of NTP service output that are mutually backed up.
NOTE
To improve the reliability of the NTP service, ensure that the following methods are applicable:
l
Choose two or more NTP servers that serve as the upper-layer NTP server to provide time reference. When deploying the upper-layer NTP server for NEs and the M2000, ensure that more than two channels of the NTP service are available. If the stratum 1 NTP server is deployed, it obtains reference time directly from the GPS satellite. In such a case, the stratum 1 NTP server should provide two channels of satellite interfaces.
2.2 Setting Time Information for the M2000 Server

The server time is associated with NE data collection, timing task handling, and database information dump. You must ensure that the server time is correct before configuring the NTP service for the server. Therefore, a correct server time is vital to the normal operation of the system. 2.2.1 Modifying the Date and Time on the M2000 Server The server time is associated with NE data collection, timing task handling, and database information dump. Therefore, you must set the server time correctly. 2.2.2 Modifying the Time Zone on the M2000 Server The correct time zone of the M2000 server is essential to the local time display, the NTP service, and DST. This describes how to modify the time zone of the M2000 server. 2.2.3 Setting the NTP Service for the M2000 Server This describes how to configure the M2000 server as the NTP client. 2.2.4 Stopping the NTP Service on the M2000 Server This describes how to stop the NTP service on the M2000 server. 2.2.5 Setting the DST for the M2000 To enable the M2000 to support daylight saving time (DST), you must set the time zone of the M2000 server.
2.2.1 Modifying the Date and Time on the M2000 Server

The server time is associated with NE data collection, timing task handling, and database information dump. Therefore, you must set the server time correctly.
Prerequisite
You have logged in to the server as user root.
Context
If the M2000 server acts as the NTP server of network equipment, the network equipment time is updated when you modify the M2000 server time.
2-12
Issue 05 (2008-05-20)
CAUTION
l
Modifying the server time results in the change of time at the Solaris bottom layer, thus resetting or invalidating all timers that depend on the operating system. To avoid the function failures resulting from invalid timers, stop the M2000 and the Sybase first. During this process, the performance data and alarm data of managed NEs are not processed in real time. After the Sybase and M2000 services are restarted, the M2000 collects the performance data and alarm data through automatic synchronization and then processes the data. Therefore, the data is not lost. You must first modify the time zone if the time and the time zone must be modified.
Procedure
Step 1 Check system date and time. # date If system date and time are incorrect, perform the following steps: Step 2 Stop the M2000. To know how to stop the M2000, refer to7.3.4 Stopping M2000 Services. Step 3 Stop the Sybase. To know how to stop the Sybase, refer to15.2.3 How to Stop the Sybase. Step 4 Set the system date and time. # date mmddHHMMYYYY.SS
NOTE
l l l l l l
mm indicates a month. dd indicates a day. HH indicates an hour. MM indicates a minute. YYYY indicates a year. SS indicates a second.
For example, to set system date and time to 2005-11-17 16:30:43, run the following command: # date 111716302005.43 Mon Nov 17 16:30:43 CST 2005
NOTE
If GMT time is used, run the command date -u mmddHHMMYYYY.SS to change time.
Step 5 Start the Sybase. For details on how to start the Sybase, refer to15.2.2 How to Start the Sybase. Step 6 Start the M2000. For details on how to start the M2000, refer to7.3.3 Starting M2000 Services. ----End
2.2.2 Modifying the Time Zone on the M2000 Server

The correct time zone of the M2000 server is essential to the local time display, the NTP service, and DST. This describes how to modify the time zone of the M2000 server.
Prerequisite
Context
l
Modifying the time zone on the server results in the change of time at the Solaris bottom layer, thus resetting or invalidating all timers that depend on the operating system. To avoid the function failures resulting from invalid timers, stop the M2000 and the Sybase first. During the period when you change the server time zone, the performance data and alarm data of the managed NEs cannot be handled in time. After the Sybase and the M2000 are running again, the M2000 enables the automatic synchronization function to collect and handle the missing performance data and alarm data. If you need to modify both the time zone and the time, modify the time zone first. Greenwich MeanTime (GMT) is taken as a reference. The time zone that is to the east of GMT is represented by GMT+N. That is, the local time is N hours ahead of GMT. The time zone that is to the west of GMT is represented by GMT-N. That is, the local time is N hours behind GMT. For example, GMT+08:00 indicates that the local time is eight hours ahead of GMT. GMT-08:00 indicates that the local time is eight hours behind GMT. When you, however, modify the time zone configuration file of the Solaris, that is, /etc/ TIMEZONE, GMT+N refers to the time zone that is N hours behind GMT and GMT-N refers to the time zone that is N hours ahead of GMT. The GMT format does not support the DST. Only the time zone name format supports the DST.
l l
Procedure
Step 1 Stop the M2000 if it is running. For details, refer to 7.3.4 Stopping M2000 Services. Step 2 Stop the Sybase if it is running. For details, see 15.2.3 How to Stop the Sybase. Step 3 Change the value of TZ in the /etc/TIMEZONE file to the local time zone. # vi /etc/TIMEZONE For example, set TZ to EET.
NOTE
l l
Find the value of TZ in /usr/share/lib/zoneinfo/src. Ensure that the time binary zone file of the TZ exists in the /usr/share/lib/zoneinfo directory. The GMT format does not support DST. Only the time zone name format supports DST. If DST is not used, change the value of TZ to the current GMT time zone. GMT+N indicates that the local time is N hours behind GMT. GMT-N indicates that the local time is N hours ahead of GMT. Before the modification, ensure that the binary timezone file corresponding to the GMT time zone is located in the /usr/share/lib/zoneinfo directory. Otherwise, the modification fails. The /etc/TIMEZONE file is read-only. Save the file forcibly after the modification.
2-14
Issue 05 (2008-05-20)
Step 4 If the M2000 software is installed, change the time zone configuration file. The time zone configuration file is /M2000 server installation path/etc/conf/ timezone_svc_ex.xml. The default installation path of the M2000 server software is /opt/ OMC.
l l
If the M2000 server software is not installed, you need not modify the file. If the M2000 server software is installed and DST is not used, change the value of TZ to the local GMT time zone. GMT+N indicates the time zone that is N hours ahead of GMT. GMTN indicates the time zone that is N hours behind GMT. The value of DSTOffset should be set to +0:00. If the M2000 server software is installed and DST is used, change the time zone information in the file by referring to Table 2-1.
Table 2-1 File timezone_svc_ex.xml Field Name TZ Value Description

l
Example <param name="TZ">GMT +08:00</param> No space should be added to GMT +08:00. The character should be in English. Type + or - clearly.
Indicates the GMT time zone that corresponds to the current time zone. GMT+N indicates that the local time is N hours ahead of GMT. GMT-N indicates that the local time is N hours behind GMT. For example, GMT+08:00 indicates that the local time is eight hours ahead of GMT. GMT-08:00 indicates that the local time is eight hours behind GMT. Offset the DST. DSTOffset can be set to a positive or negative value. + indicates that the DST should be adjusted ahead of the local standard time. - indicates that the DST should be adjusted behind the local standard time. If the DST is not implemented, set DSTOffset to +0:00.
DSTOffset
l l
<param name="DSTOffset"> +1:00</param> No space should be added to +1:00. The character should be in English. Type + or - clearly.
StartType
The time type when the DST starts. It can be WEEK or DATE. The time type when the DST ends. It can be WEEK or DATE.
<param name="StartType">WEEK</ param> <param name="EndType">WEEK</ param>
EndType
Issue 05 (2008-05-20)
2-15
Field Name StartWeek
Value Description If the start type is WEEK, the date when the DST starts is based on WEEK. Stipulate the day and the week after or before the date that you set as the benchmark. The first number represents a month. The second number represents a date (The number 0 stands for the last day of each month). The third number represents the week sequence number. Positive means that the current date is later than the benchmark. Negative means that the current date is earlier than the current date. The last number represents a day of each week. If the third number is negative, the second number must be 0. That is, if the DST start date or end date is earlier than the reference date, you must specify the last day of the month as the start point.
Example <param name="StartWeek">4/1/1/7</ param> Indicates the first Sunday of April. <param name="StartWeek">4/10/1/7</ param> Indicates the first Sunday from April, 10. That is, the first Sunday in the middle ten days of a month. <param name="StartWeek">4/0/-1/7</ param> Indicates the last Sunday of April.
EndWeek
If the end type is WEEK, the DST end date adheres to WEEK. The rule of EndWeek is the same as that of StartWeek.
<param name="EndWeek">9/1/1/7</ param>
StartDate
If the start type is DATE, the DST start data adheres to DATE. Regulate the date.
<param name="StartDate">4/1</ param> Indicates April 1. <param name="EndDate">9/1</ param>
EndDate
If the end type is DATE, the DST end date adheres to DATE. The rule of EndDate is the same as that of StartDate.
StartTime
Start time of DST in HH:MM:SS format. Use the local standard time for StartTime.
<param name="StartTime">02:00:00 AM</param> Indicates that DST starts from 02:00:00, which is a local standard time. This means that time changes from 01:59:59 (local standard time) to 03:00:00, which is a DST time.
2-16
Issue 05 (2008-05-20)
Field Name EndTime
Value Description End time of DST in HH:MM:SS format. Use the local standard time for EndTime.
Example <param name="EndTime">02:00:00 AM</param> Indicates that DST ends at 02:00:00, which is a local standard time. This means that time changes from 02:59:59 (DST time) to 02:00:00, which is a local standard time.
Step 5 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 The Sybase and M2000 services automatically restart after the Solaris restarts. ----End
2.2.3 Setting the NTP Service for the M2000 Server

This describes how to configure the M2000 server as the NTP client. 2.1 Time Synchronization Solution for Huawei Mobile Network This describes the time synchronization solution of Huawei. By using the time synchronization solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei mobile network equipment. 2.3.2 Checking the Time Settings on the M2000 Server Before configuring the NTP service, ensure that the time zone, date, and time are correctly set on the M2000 server. 2.3.3 Setting the M2000 Administration Console as the Secondary NTP Server This describes how to set the M2000 administration console as the secondary NTP server. The secondary NTP server synchronizes time with the upper-level server and provides a standard time source for a lower-level server.In the single-server system, the administration console is configured only for the E4900 server. 2.3.4 Starting the NTP Service on the M2000 Administration Console This describes how to start the NTP service on the M2000 administration console to synchronize the system. 2.3.5 Checking the Running Status of the NTP Service on the M2000 Administration Console This describes how to check the operational status of the NTP service. 2.3.6 Setting the M2000 Server as the NTP Client This describes how to configure the NTP service to set the M2000 server as the NTP client, which is synchronized with the upper level server. 2.3.7 Starting the NTP Service on the M2000 Server This describes how to start the NTP service on the M2000 server to synchronize the system. 2.3.8 Checking the Running Status of the NTP Service on the M2000 Server
This describes how to check the operational status of the NTP service.
2.2.4 Stopping the NTP Service on the M2000 Server

This describes how to stop the NTP service on the M2000 server.
Prerequisite
You have logged in to the M2000 server as user root.
Procedure
Step 1 Check the operational status of the NTP. # svcs svc:/network/ntp:default
STATE online STIME FMRI 16:41:28 svc:/network/ntp:default
If STATE is online, infer that the NTP is running. Step 2 If the NTP service is started, stop it. # svcadm disable svc:/network/ntp:default
NOTE
This command is an once-time command. This means that the NTP service is not enabled each time the system is restarted.
Step 3 Check whether the NTP service is stopped. # svcs svc:/network/ntp:default If STATE is disabled, infer that the NTP service is stopped.
NOTE
Stopping the NTP service consumes some time.
----End
2.2.5 Setting the DST for the M2000

To enable the M2000 to support daylight saving time (DST), you must set the time zone of the M2000 server. 2.4.1 Introduction to the DST This describes the daylight saving time (DST) and the DST impact on the M2000 system. 2.4.2 Viewing the DST Rules of a Time Zone This describes how to view the DST rules of a time zone. As the local government may adjust the DST rules owing to various reasons, you must query the DST rules of the corresponding time zone based on the time zone code before setting DST. This ensures that the DST rules defined by the time zone code are consistent with the actual DST rules. 2.2.2 Modifying the Time Zone on the M2000 Server The correct time zone of the M2000 server is essential to the local time display, the NTP service, and DST. This describes how to modify the time zone of the M2000 server.
2.3 Setting the NTP Service for the M2000 Server

This describes how to configure the M2000 server as the NTP client. 2.3.1 Time Synchronization Solution for Huawei Mobile Network This describes the time synchronization solution of Huawei. By using the time synchronization solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei mobile network equipment. 2.3.2 Checking the Time Settings on the M2000 Server Before configuring the NTP service, ensure that the time zone, date, and time are correctly set on the M2000 server. 2.3.3 Setting the M2000 Administration Console as the Secondary NTP Server This describes how to set the M2000 administration console as the secondary NTP server. The secondary NTP server synchronizes time with the upper-level server and provides a standard time source for a lower-level server.In the single-server system, the administration console is configured only for the E4900 server. 2.3.4 Starting the NTP Service on the M2000 Administration Console This describes how to start the NTP service on the M2000 administration console to synchronize the system. 2.3.5 Checking the Running Status of the NTP Service on the M2000 Administration Console This describes how to check the operational status of the NTP service. 2.3.6 Setting the M2000 Server as the NTP Client This describes how to configure the NTP service to set the M2000 server as the NTP client, which is synchronized with the upper level server. 2.3.7 Starting the NTP Service on the M2000 Server This describes how to start the NTP service on the M2000 server to synchronize the system. 2.3.8 Checking the Running Status of the NTP Service on the M2000 Server This describes how to check the operational status of the NTP service.
2.3.1 Time Synchronization Solution for Huawei Mobile Network

This describes the time synchronization solution of Huawei. By using the time synchronization solution for the Huawei mobile network, you can synchronize the M2000 with other Huawei mobile network equipment. 2.1.1 Purpose of Time Synchronization The time synchronization function enables you to synchronize the M2000 with other NEs in a mobile network. 2.1.2 Overview of Time Synchronization This defines time synchronization and describes the elements of time synchronization scheme and the impact on system performance and other O&M features. 2.1.3 Introduction to the NTP/SNTP This introduces the rationale of time synchronization and the layered architecture of the Network Time Protocol (NTP) and the Simple Network Time Protocol (SNTP). 2.1.4 Time Synchronization Modes of Huawei Mobile Network
This describes the modes of time synchronization and how to deploy the time synchronization network for the M2000 and NE devices in Huawei mobile network.
2.3.2 Checking the Time Settings on the M2000 Server

Before configuring the NTP service, ensure that the time zone, date, and time are correctly set on the M2000 server.
Procedure
Step 1 Check the time zone on the server. # echo $TZ If the time zone is incorrect, change the time zone by referring to 2.2.2 Modifying the Time Zone on the M2000 Server. Step 2 Check the date and time on the server. # date If the date is incorrect or the time of the server is incorrect with a deviation of more than two minutes, change the date and time by referring to 2.2.1 Modifying the Date and Time on the M2000 Server. ----End
2.3.3 Setting the M2000 Administration Console as the Secondary NTP Server
This describes how to set the M2000 administration console as the secondary NTP server. The secondary NTP server synchronizes time with the upper-level server and provides a standard time source for a lower-level server.In the single-server system, the administration console is configured only for the E4900 server.
Prerequisite
l l l
The top layer NTP server has been configured in the mobile network. The time zone, date, and time of the administration console are set correctly. You have logged in to the administration console as user root.
Context
Normally, the M2000 server is set as the NTP client. If no other server is available to be set as the secondary time server, use the administration console Netra 240 of the M2000 system as the secondary NTP server.
Procedure
Step 1 Open the file ntp.conf. # cp /etc/inet/ntp.server /etc/inet/ntp.conf # TERM=vt100; export TERM
# vi /etc/inet/ntp.conf Step 2 In front of server 127.127.XType.0, add server IP address of the upper-level NTP server prefer.
NOTE
If multiple upper-level NTP servers exist, write multiple lines. Ensure that each line maps to an NTP server. For example:
server server IP address of the upper-level NTP server IP address of the upper-level NTP server prefer
Step 3 Change XType in server 127.127.XType.0 and fudge 127.127.Xtype.0 stratum 0 to 1. The value 1 indicates that the local host serves as the standard time source. Step 4 In fudge 127.127.1.0 stratum 0, delete stratum 0. Step 5 In front of broadcast 224.0.1.1 ttl 4, add # to comment this line out and to prohibit the broadcasting mode. Step 6 Save the file ntp.conf and quit vi. ----End
Example
To synchronize time with the server whose IP address are 10.161.94.212 and 10.161.94.214, you must replace the following contents in the file ntp.conf:
server 127.127.XType.0 fudge 127.127.XType.0 stratum 0 broadcast 224.0.1.1 ttl 4
with:
server 10.161.94.212 server 10.161.94.214 server 127.127.1.0 fudge 127.127.1.0 #broadcast 224.0.1.1 ttl 4 prefer prefer
2.3.4 Starting the NTP Service on the M2000 Administration Console

This describes how to start the NTP service on the M2000 administration console to synchronize the system.
Prerequisite
l l
The time zone, date, and time of the administration console are correctly set. You have logged in to the administration console as user root.
Procedure
Step 1 Check whether any NTP service is running. # svcs svc:/network/ntp:default Check the command result.

l
If STATE is disabled, you can infer that the NTP service is not started. Proceed with Step 2. If STATE is online, you can infer that the NTP service is started. Skip Step 2. If STATE is maintenance, do as follows: 1. 2. If STATE is still maintenance, run the following command to stop the NTP service: # svcadm disable svc:/network/ntp:default Start the NTP service. After the NTP service is started, skip Step 2. # svcadm enable svc:/network/ntp:default
l l
Step 2 Start the NTP service. # svcadm enable svc:/network/ntp:default

NOTE
This command has the once-for-all effect. The NTP service is started each time the system restarts.
----End
2.3.5 Checking the Running Status of the NTP Service on the M2000 Administration Console
Context
After the NTP server and the NTP client are started, the system requires five minutes for the system test. Wait for five minutes, and then run the commands ntpq -p and ntptrace to view the status of the NTP service. During the system test, if you run the ntpq -p command, the displayed address of the remote clock source does not contain *. If you run the ntptrace command during the system test, the system displays Timeout or Not Synchronized.
Procedure
Step 1 View the information about the time source. # ntpq -p In the result of the command ntpq -p, the remote field shows the address and status of the reference clock source. Step 2 Check the information about the clock synchronization path. # ntptrace The ntptrace command traces the NTP synchronization path from the host to the top NTP server. For more information, run the command ntptrace -v. ----End
Example
The administration console serves as the medium-level NTP server
root@osssvr # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *10.161.94.212 .LCL. 1 u 165 512 377 0.406 61.294 0.111 +LOCAL(0) LOCAL(0) 3 1 29 64 377 0.000 0.000 0.000 root@osssvr # root@osssvr # ntptrace localhost: stratum 2, offset 0.000039, synch distance 0.07640 10.161.94.212: stratum 1, offset 0.060665, synch distance 0.01015, refid 'LCL' root@osssvr #
In the result of the command ntpq -p, *10.161.94.212 indicates that the IP address of the NTP server that the host is synchronized with is 10.161.94.212. The value 1 in the column st indicates that the host is located at stratum 1. The symbol * indicates that the NTP is running properly. The result of the command ntptrace shows that the host is located at stratum 2, that the IP address of the upper-level server is 10.161.94.212, and that the upper-level server is at stratum 1.
2.3.6 Setting the M2000 Server as the NTP Client

This describes how to configure the NTP service to set the M2000 server as the NTP client, which is synchronized with the upper level server.
Prerequisite
l l
The time zone, date, and time of the server are correctly set. You have logged in to the server as user root.
Procedure
Step 1 Open the /etc/inet/ntp.conf file. # cp /etc/inet/ntp.client /etc/inet/ntp.conf # TERM=vt100; export TERM # vi /etc/inet/ntp.conf Step 2 Add server IP address of the upper level NTP server at the end of the file to specify the IP addresses of the upper-layer NTP servers. Each line maps to an NTP server. Step 3 Add # to the front of multicastclient 224.0.1.1 to comment the line out.
NOTE
Either the multicast client or the upper-layer NTP server takes effect.
Step 4 Save the ntp.conf file and then quit vi. ----End
Example
If the server with the IP address of 10.161.94.214 is the upper-layer NTP server of the M2000 server, replace the following contents of the ntp.conf file:
multicastclient 224.0.1.1
with:
server 10.161.94.214 #multicastclient 224.0.1.1
Issue 05 (2008-05-20)
2-23
2.3.7 Starting the NTP Service on the M2000 Server

This describes how to start the NTP service on the M2000 server to synchronize the system.
Prerequisite
l l
The time zone, date, and time of the server are correctly set. You have logged in to the server as user root.
Procedure
Step 1 Check whether any NTP service is running. # svcs svc:/network/ntp:default Check the command result.
l
If STATE is disabled, you can infer that the NTP service is not started. Proceed with Step 2. If STATE is online, you can infer that the NTP service is started. Skip Step 2. If STATE is maintenance, do as follows: 1. 2. If STATE is still maintenance, run the following command to stop the NTP service: # svcadm disable svc:/network/ntp:default Start the NTP service. After the NTP service is started, skip Step 2. # svcadm enable svc:/network/ntp:default
l l
Step 2 Start the NTP service. # svcadm enable svc:/network/ntp:default

NOTE
This command has the once-for-all effect. The NTP service is started each time the system restarts.
----End
Postrequisite
If the administration console is configured as the medium-level NTP server, you must start the NTP service on the administration console at the same time.
2.3.8 Checking the Running Status of the NTP Service on the M2000 Server
Context
After the NTP server and the NTP client are started, the system requires five minutes for the system test. Wait for five minutes, and then run the commands ntpq -p and ntptrace to view the status of the NTP service.
During the system test, if you run the ntpq -p command, the displayed address of the remote clock source does not contain *. If you run the ntptrace command during the system test, the system displays Timeout or Not Synchronized.
Procedure
Step 1 View the information about the time source. # ntpq -p In the result of the command ntpq -p, the remote field shows the address and status of the reference clock source. Step 2 Check the information about the clock synchronization path. # ntptrace The ntptrace command traces the NTP synchronization path from the host to the top NTP server. For more information, run the command ntptrace -v. ----End
Example
The M2000 server serves as the NTP client.
root@osssvr # ntpq -p remote refid st t when poll reach delay offset disp ============================================================================== *10.161.94.214 10.161.94.214 2 u 58 64 377 0.37 0.217 0.05 root@osssvr # root@osssvr # ntptrace localhost: stratum 3, offset 0.000035, synch distance 0.08855 10.161.94.214: stratum 2, offset 0.000224, synch distance 0.07860 10.161.94.212: stratum 1, offset 0.060569, synch distance 0.01036, refid 'LCL' root@osssvr #
In the result of the command ntpq -p, *10.161.94.214 indicates that the IP address of the NTP server that the host is synchronized with is 10.161.94.214. The value 2 in the column st indicates that the host is located at level 2. The symbol * indicates that the NTP is running properly. The result of the command ntptrace indicates that the host is located at level 3, that the IP address of the stratum-2 server is 10.161.94.214, and that the IP address of the stratum-1 server is 10.161.94.212.
2.4 Setting the DST for the M2000

To enable the M2000 to support daylight saving time (DST), you must set the time zone of the M2000 server. 2.4.1 Introduction to the DST This describes the daylight saving time (DST) and the DST impact on the M2000 system. 2.4.2 Viewing the DST Rules of a Time Zone This describes how to view the DST rules of a time zone. As the local government may adjust the DST rules owing to various reasons, you must query the DST rules of the corresponding
time zone based on the time zone code before setting DST. This ensures that the DST rules defined by the time zone code are consistent with the actual DST rules. 2.4.3 Modifying the Time Zone on the M2000 Server The correct time zone of the M2000 server is essential to the local time display, the NTP service, and DST. This describes how to modify the time zone of the M2000 server.
2.4.1 Introduction to the DST

This describes the daylight saving time (DST) and the DST impact on the M2000 system.
Introduction
The DST is one hour earlier than the standard time. For example, during the DST, 10:00 am in US east standard time is 11:00 am in US east DST.
Impact on the M2000 System

l
When the DST starts, generally one hour is automatically added to the local time of the operating system. This change does not affect the system clock of the M2000. The M2000 log management and trace management uses the local time. Therefore, one-hour records are missing in trace files. When the DST ends, generally one hour is automatically reduced from the local time of the operating system. This change does not affect the system clock. Thus, time storage and exchange are not affected. This change, however, affects the time display. During the operation of the M2000, some modules in the M2000 generate some files whose names are identified by time stamps. When the DST ends, files that are generated later overwrite the earlier ones.
NOTE
l l
The local time is the time displayed on the computer. It varies according to the time zone. The system clock indicates the GMT. The NTP synchronization uses the GMT, thus not affecting the local time. The DST does not affect the NTP service.
2.4.2 Viewing the DST Rules of a Time Zone

This describes how to view the DST rules of a time zone. As the local government may adjust the DST rules owing to various reasons, you must query the DST rules of the corresponding time zone based on the time zone code before setting DST. This ensures that the DST rules defined by the time zone code are consistent with the actual DST rules.
Prerequisite
Context
On the Solaris operating system, two formats are available for the time zone: GMT and time zone code. The GMT format stipulates only time offset rather than the DST rules. The time zone code format stipulates the time offset and the DST rules, depending on time zones. The GMT format can be used by the countries and districts that do not use DST. The time zone code format must be used by the countries and districts that use DST. Otherwise, the operating system does not support the automatic time system change.
After the DST rules of a time zone are changed, Sun may release a patch for the time zone code. You need to install the patch to obtain the latest time zone code and DST rules.
Procedure
Step 1 Query the local time zone name. For details on how to query time zone names, refer to 15.1.11 How to Query a Time Zone Name. Step 2 Run the following command to view the rules: # zdump -v time zone code | grep the specified year The format of the displayed information is as follows:
Time zone name l l UTC time = local time isdst=0/1
The UTC time refers to GMT. If the last two letters in the local time are ST, you can infer that the local time is the standard time. If the last two letters in the local time are DT, you can infer that the local time is DST. isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DST period. If DST is not used, only a line of information is displayed. If DST is used, at least four lines of information is displayed for describing the DST rules.
NOTE
l l
If you do not add | grep the specified year to the previous command, the system displays all time zone rules of the time zone. The DST rules stipulate the day, week, and month when the DST starts and ends in each year. This means that the week when DST is enabled is fixed and that the date when DST is enabled is flexible. For example, DST in the time zone US/Alaska starts from the second Sunday of March and ends in the first Sunday of November in each year. Use the zdump command to query the DST rules in the three successive years, that is, the last year, this year, and the next year. Based on the command result, you can infer the universal rules of DST jump.
----End
Example
l
To query the DST rules used by PRC in 2007, run the following command: # zdump -v PRC|grep 2007
PRC Mon Sep 17 06:03:55 2007 UTC = Mon Sep 17 14:03:55 2007 CST isdst=0
As only one line of information is displayed after you run the zdump command, you can infer that DST is not used in PRC and that the local time is GMT+8.
l
To query the DST rules used by US/Alaska in 2007, run the following command: # zdump -v US/Alaska|grep 2007
US/Alaska isdst=1 US/Alaska isdst=0 US/Alaska isdst=1 US/Alaska isdst=1 Mon Sep 17 06:09:56 2007 UTC = Sun Sep 16 22:09:56 2007 AKDT Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT
Issue 05 (2008-05-20)
2-27

US/Alaska isdst=0 Sun Nov 4 10:00:00 2007 UTC = Sun Nov

4 01:00:00 2007 AKST
Based on the fact that the first line of the command result contains isdst=1, you can infer that DST is used in US/Alaska. DST is being used. The local time, that is, the DST time, is Sep 16 22:09:56 2007. The UTC time is Sep 17 06:09:56 2007. Based on the information in the second line and the third line, you can infer that DST starts after Mar 11 02:00:00 2007 is changed to Mar 11 03:00:00 2007. Based on the information in the fourth line and the fifth line, you can infer that DST ends after Nov 4 02:00:00 2007 is changed to Nov 4 01:00:00.
2.4.3 Modifying the Time Zone on the M2000 Server

The correct time zone of the M2000 server is essential to the local time display, the NTP service, and DST. This describes how to modify the time zone of the M2000 server.
Prerequisite
Context
l
Modifying the time zone on the server results in the change of time at the Solaris bottom layer, thus resetting or invalidating all timers that depend on the operating system. To avoid the function failures resulting from invalid timers, stop the M2000 and the Sybase first. During the period when you change the server time zone, the performance data and alarm data of the managed NEs cannot be handled in time. After the Sybase and the M2000 are running again, the M2000 enables the automatic synchronization function to collect and handle the missing performance data and alarm data. If you need to modify both the time zone and the time, modify the time zone first. Greenwich MeanTime (GMT) is taken as a reference. The time zone that is to the east of GMT is represented by GMT+N. That is, the local time is N hours ahead of GMT. The time zone that is to the west of GMT is represented by GMT-N. That is, the local time is N hours behind GMT. For example, GMT+08:00 indicates that the local time is eight hours ahead of GMT. GMT-08:00 indicates that the local time is eight hours behind GMT. When you, however, modify the time zone configuration file of the Solaris, that is, /etc/ TIMEZONE, GMT+N refers to the time zone that is N hours behind GMT and GMT-N refers to the time zone that is N hours ahead of GMT. The GMT format does not support the DST. Only the time zone name format supports the DST.
l l
Procedure
Step 1 Stop the M2000 if it is running. For details, refer to 7.3.4 Stopping M2000 Services. Step 2 Stop the Sybase if it is running. For details, see 15.2.3 How to Stop the Sybase. Step 3 Change the value of TZ in the /etc/TIMEZONE file to the local time zone. # vi /etc/TIMEZONE
For example, set TZ to EET.

NOTE
l l
Find the value of TZ in /usr/share/lib/zoneinfo/src. Ensure that the time binary zone file of the TZ exists in the /usr/share/lib/zoneinfo directory. The GMT format does not support DST. Only the time zone name format supports DST. If DST is not used, change the value of TZ to the current GMT time zone. GMT+N indicates that the local time is N hours behind GMT. GMT-N indicates that the local time is N hours ahead of GMT. Before the modification, ensure that the binary timezone file corresponding to the GMT time zone is located in the /usr/share/lib/zoneinfo directory. Otherwise, the modification fails. The /etc/TIMEZONE file is read-only. Save the file forcibly after the modification.
Step 4 If the M2000 software is installed, change the time zone configuration file. The time zone configuration file is /M2000 server installation path/etc/conf/ timezone_svc_ex.xml. The default installation path of the M2000 server software is /opt/ OMC.
l l
If the M2000 server software is not installed, you need not modify the file. If the M2000 server software is installed and DST is not used, change the value of TZ to the local GMT time zone. GMT+N indicates the time zone that is N hours ahead of GMT. GMTN indicates the time zone that is N hours behind GMT. The value of DSTOffset should be set to +0:00. If the M2000 server software is installed and DST is used, change the time zone information in the file by referring to Table 2-2.
Table 2-2 File timezone_svc_ex.xml Field Name TZ Value Description

l
Example <param name="TZ">GMT +08:00</param> No space should be added to GMT +08:00. The character should be in English. Type + or - clearly.
Indicates the GMT time zone that corresponds to the current time zone. GMT+N indicates that the local time is N hours ahead of GMT. GMT-N indicates that the local time is N hours behind GMT. For example, GMT+08:00 indicates that the local time is eight hours ahead of GMT. GMT-08:00 indicates that the local time is eight hours behind GMT. Offset the DST. DSTOffset can be set to a positive or negative value. + indicates that the DST should be adjusted ahead of the local standard time. - indicates that the DST should be adjusted behind the local standard time. If the DST is not implemented, set DSTOffset to +0:00.
DSTOffset
l l
<param name="DSTOffset"> +1:00</param> No space should be added to +1:00. The character should be in English. Type + or - clearly.
Issue 05 (2008-05-20)
2-29
Field Name StartType
Value Description The time type when the DST starts. It can be WEEK or DATE. The time type when the DST ends. It can be WEEK or DATE. If the start type is WEEK, the date when the DST starts is based on WEEK. Stipulate the day and the week after or before the date that you set as the benchmark. The first number represents a month. The second number represents a date (The number 0 stands for the last day of each month). The third number represents the week sequence number. Positive means that the current date is later than the benchmark. Negative means that the current date is earlier than the current date. The last number represents a day of each week. If the third number is negative, the second number must be 0. That is, if the DST start date or end date is earlier than the reference date, you must specify the last day of the month as the start point.
Example <param name="StartType">WEEK</ param> <param name="EndType">WEEK</ param> <param name="StartWeek">4/1/1/7</ param> Indicates the first Sunday of April. <param name="StartWeek">4/10/1/7</ param> Indicates the first Sunday from April, 10. That is, the first Sunday in the middle ten days of a month. <param name="StartWeek">4/0/-1/7</ param> Indicates the last Sunday of April.
EndType
StartWeek
EndWeek
If the end type is WEEK, the DST end date adheres to WEEK. The rule of EndWeek is the same as that of StartWeek.
<param name="EndWeek">9/1/1/7</ param>
StartDate
If the start type is DATE, the DST start data adheres to DATE. Regulate the date.
<param name="StartDate">4/1</ param> Indicates April 1. <param name="EndDate">9/1</ param>
EndDate
If the end type is DATE, the DST end date adheres to DATE. The rule of EndDate is the same as that of StartDate.
2-30
Issue 05 (2008-05-20)
Field Name StartTime
Value Description Start time of DST in HH:MM:SS format. Use the local standard time for StartTime.
Example <param name="StartTime">02:00:00 AM</param> Indicates that DST starts from 02:00:00, which is a local standard time. This means that time changes from 01:59:59 (local standard time) to 03:00:00, which is a DST time.
EndTime
End time of DST in HH:MM:SS format. Use the local standard time for EndTime.
<param name="EndTime">02:00:00 AM</param> Indicates that DST ends at 02:00:00, which is a local standard time. This means that time changes from 02:59:59 (DST time) to 02:00:00, which is a local standard time.
Step 5 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 The Sybase and M2000 services automatically restart after the Solaris restarts. ----End
2.5 Setting the Time Information on the M2000 Client

This describes how to set the time information on the M2000 client. 2.5.1 Modifying the Date, Time, and Time Zone on the M2000 Client This describes how to change the date, time, and time zone of the Windows operating system. The M2000 client is a PC that operates under the Windows operating system. 2.5.2 Setting the NTP Service on the M2000 Client This describes how to set the M2000 client as the NTP client. This task enables you to synchronize the client with the NTP server through the NTP service of the Windows operating system.
2.5.1 Modifying the Date, Time, and Time Zone on the M2000 Client
This describes how to change the date, time, and time zone of the Windows operating system. The M2000 client is a PC that operates under the Windows operating system.
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Choose Start > Settings > Control Panel. The Control Panel window is displayed. This takes a PC with Windows 2000 Professional as an example. Step 2 Double-click Date and Time. Step 3 In the Date and Time window, select the items that you want to change. Items to Be Changed Operation Hour Minute Second Time Zone Double-click Hour, and then click the arrow to change the value. Double-click Minute, and then click the arrow to change the value. Double-click Second, and then click the arrow to change the value. Click the Time Zone tab. On the Time Zone tab page, choose the local time zone from the drop-down list.
Step 4 Click OK. ----End
2.5.2 Setting the NTP Service on the M2000 Client

This describes how to set the M2000 client as the NTP client. This task enables you to synchronize the client with the NTP server through the NTP service of the Windows operating system.
Prerequisite
l
You have logged in to the Windows operating system. The Windows operating system is running properly. The M2000 client and the M2000 server communicate normally. The clock source of the server is operational.
l l
Context
When the M2000 client is configured as the NTP client, synchronize the time of the M2000 client with the time of the M2000 server. The configuration procedure is applicable to the Windows 2000 Professional or Windows XP Professional operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client. In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to
0, which is the default value. If the parameter LocalNTP does not exist, you can infer that the value can be ignored and the registry need not be modified. Step 2 Specify the NTP clock source. Choose Start > Run. Type cmd and press Enter. In the displayed window, run the following command: c:\>net time /setsntp:M2000 IP Address of NTP Server
NOTE
1. The result of the net time command is saved in the Windows registry. This setting of the net time takes effect after Windows restarts. 2. To clear the specification, run the net time /setsntp command.
Step 3 Check the NTP server specified by the PC. c:\>net time /querysntp
NOTE
l l
If the host name and IP address of the PC are specified as the host name and IP address of the NTP server by /setsntp, the NTP server time is the local time of the PC. If the NTP server changes the upper-level time server through the /setsntp option, restart the Windows Time service. To restart the Windows Time service, choose Start > Run. In the displayed Run dialog box, enter services.msc to open the Services window, and then press Enter. Identify the Windows Time service and restart the service. If the NTP client changes the time server through the /setsntp option, restart the Windows Time service.
Step 4 Check the operational status of the Simple Network Time Protocol (SNTP), using the w32tm command of the Windows. c:\>w32tm The system displays the host name of the connected NTP server, deviation of the local time from that on the NTP server, and time cycle of NTP server roll.
NOTE
After running the w32tm command, wait until the command result is displayed.
----End
Issue 05 (2008-05-20)
2-33
3 Setting the Host Name and IP Address for the M2000 Server
Setting the Host Name and IP Address for the M2000 Server
About This Chapter

This describes how to set the host name and the IP address of the M2000 server, according to field requirements. 3.1 Modifying the Host Name of the M2000 Server This describes how to modify the host name of the M2000 server. During the modification of the host name, the M2000 cannot handle the performance data and alarm data of the managed NEs. After the modification, the M2000 implements automatic synchronization to collect and handle the missing performance data and alarm data. 3.2 Modifying the IP Address of the M2000 Server This describes how to modify the IP address of the M2000 server in common mode and maintenance dual-plane mode. In common mode, the maintenance dual-plan is not configured. 3.3 Modifying the IP Address of the SC on the M2000 Server This describes how to modify the IP address of the SC on the M2000 server. The SC can be the SC on the Netra 240 server, RSC on the V890 server, or SC on the E4900 server. In special situations, you can log in to the M2000 server through the IP address of the SC to operate and maintain the server. 3.4 Modifying the IP Address of the Disk Array This describes how to modify the IP address of the disk array. By modifying the IP address of the disk array, you can maintain the disk array easily.
Issue 05 (2008-05-20)
3-1
3.1 Modifying the Host Name of the M2000 Server

This describes how to modify the host name of the M2000 server. During the modification of the host name, the M2000 cannot handle the performance data and alarm data of the managed NEs. After the modification, the M2000 implements automatic synchronization to collect and handle the missing performance data and alarm data.
Prerequisite
You have logged in to server as user root.
Procedure
Step 1 Check the host name of the server. # hostname If the host name is incorrect, proceed with the next step. Step 2 Back up the M2000 configuration files. For details, see 15.4.6 How to Back Up the M2000 Configuration Files. Step 3 If the system is running the M2000 service, stop the M2000 service first. For details on how to stop the M2000, see 7.3.4 Stopping M2000 Services. Step 4 Edit the /etc/hosts file to change the existing host name to a new one. # vi /etc/hosts Step 5 Edit the /etc/nodename file to change the existing host name to a new one. # vi /etc/nodename Step 6 Check whether the maintenance dual plane is configured. Then, determine whether to modify the corresponding file. Whether the Maintenance Dual Plane Is Step Configured Yes Edit the files /etc/hostname.ce0 and /etc/ hostname.ce2 to change the existing host names to new ones. # vi /etc/hostname.ce0 # vi /etc/hostname.ce2 No You need to modify only the /etc/ hostname.ce0 file. # vi /etc/hostname.ce0
3-2
Issue 05 (2008-05-20)

NOTE
l l l
If the /etc/hostname.ce0 and /etc/hostname.ce2 files record IP addresses, you need not modify the two files. In the files /etc/hostname.ce0 and /etc/hostname.ce2, no space is allowed at the beginning of each line. The types of NICs configured on the M2000 servers are various. If an M2000 server does not have the /etc/hostname.ce* file, modify the /etc/hostname.bge* file and change the existing host names.
Step 7 Edit /etc/inet/ipnodes to change the previous host name to the new host name. # vi /etc/inet/ipnodes Step 8 Rename the host name directory in the /var/crash directory, and then change the previous host name directory to the new host name directory. # cd /var/crash # mv old host name new host name Whether the M2000 Server Software Is Installed Yes No Then ... Proceed with Step 10. Proceed with Step 11.
Step 9 Run the following command to view the /opt/sybase/interfaces file. # vi /opt/sybase/interfaces
l
If the file records the information on host names, replace the existing host name with a new host name. Then, press Esc and run the :wq command to save the modification and exit. If the file does not record host names, do not modify the file. Press Esc and run the :q command to exit.
Step 10 To modify the M2000 configuration files, run the following command: 1. Run the script to modify the M2000 configuration files. # . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/config # ./modify.sh When the main menu is displayed, choose 1--Single system > 2--Hostname for omc. 2. 3. As prompted by the system, enter the old host name and the new host name. When the following message is displayed, enter y to start modifying the M2000 configuration files. Enter n to exit.
Are you sure to continue? [y/n]
4.
Issue 05 (2008-05-20)
When the main menu is displayed again, enter q to exit.

If the modification fails, restore the M2000 configuration file first. Then, repeat the steps mentioned previously. For details, see 15.4.7 How to Restore the M2000 Configuration Files. Step 11 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 If the M2000 software is installed, the Sybase and M2000 services restart automatically after the Solaris restarts. ----End
3.2 Modifying the IP Address of the M2000 Server

This describes how to modify the IP address of the M2000 server in common mode and maintenance dual-plane mode. In common mode, the maintenance dual-plan is not configured.
Context
If you set the function of dumping the alarms on the disk array to M2000 server logs, you must modify the IP address of the M2000 server in the array configuration file. 3.2.1 Setting a Default Route on the M2000 Server This describes how to set a default route on the M2000 server from the current network to the target network so that the M2000 server can gain access to the target network through the route. 3.2.2 Adding or Deleting Routes on the M2000 Server This describes how to add or delete routes from the current network to several target networks. 3.2.3 Modifying the IP Address of the M2000 Server This describes how to modify the IP address of the M2000 server. After you change the IP address of the M2000 server, the performance data and alarm data of the managed NEs are not processed. After the modification of the IP address, the M2000 recollects the performance data and alarm data through auto synchronization and then processes the data.
3.2.1 Setting a Default Route on the M2000 Server

This describes how to set a default route on the M2000 server from the current network to the target network so that the M2000 server can gain access to the target network through the route.
Prerequisite
Procedure
Step 1 Open the file /etc/defaultrouter. # vi /etc/defaultrouter Step 2 Enter the default IP address of the router. For example, enter the IP address of 10.161.44.1.

NOTE
l l
The entered IP address independently occupies a line in the file. If an IP address already exists in the file, replace the IP address with a new IP address.
Step 3 Save the file and exit the vi editor. Step 4 Check whether the M2000 is started by referring to 7.3.2 Viewing the States of M2000 Services. Step 5 Stop the M2000 if it is running. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Step 6 Check whether the Sybase is started by referring to 15.2.1 How to Know Whether the Sybase Is Started. Step 7 Stop the Sybase if it is running. For details on how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. Step 8 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 ----End
3.2.2 Adding or Deleting Routes on the M2000 Server

This describes how to add or delete routes from the current network to several target networks.
Prerequisite
Context
CAUTION
Run the following command to add a route. After you restart the server, the route automatically takes effect. # route add Destination address/mask gateway For example: # route add 129.8.0.0/24 10.12.8.1
Procedure
To add, delete, or automatically add the M2000 server route, run the commands listed in Table 3-1.
Table 3-1 Adding or deleting a route Operation s Adding a route Command # route add Destination address/mask gateway
l
Example # route add 129.8.0.0/24 10.12.8.1
Destination address: a network address or a PC address Mask: The number of digit 1 in the subnet mask is binary. For example, 24 means 255.255.255.0. # route delete 129.8.0.0/24 10.12.8.1 route add 129.9.0.1/24 10.12.8.1 route add 129.8.0.0/16 10.12.8.1
Deleting a route Viewing a route Adding a route automatical ly on system restart
# route delete Destination address/ mask gateway # netstat -rv Create the /etc/rc2.d/S97route file. # vi /etc/rc2.d/S97route Write one or more route add Destination address/mask gateway commands into the file.
----End
3.2.3 Modifying the IP Address of the M2000 Server

This describes how to modify the IP address of the M2000 server. After you change the IP address of the M2000 server, the performance data and alarm data of the managed NEs are not processed. After the modification of the IP address, the M2000 recollects the performance data and alarm data through auto synchronization and then processes the data.
Prerequisite
Context
If the IP address of the M2000 server is recorded in the NE database, you need to ask the NE maintenance personnel to modify the related plan. Changing the IP address of the M2000 server results in failure to connect to the M2000 server. After changing the IP address of the M2000 server, you must update the IP address of the M2000 server in the NE database.
Procedure
Step 1 Check the IP address of the server. # ifconfig -a
If the IP address is incorrect, proceed with the next step. Step 2 Check whether the new IP address is already used by other server. This part takes the change of the IP address from 192.168.8.11 to 10.10.10.10 for example. # ping 10.10.10.10
l
If you successfully ping the IP address, you can infer that the IP address is already used. In such a case, you need to use another IP address. If the IP address cannot be pinged, you can infer that the IP address is idle. You can use the IP address.
Step 3 Back up the M2000 configuration files. For details, see 15.4.6 How to Back Up the M2000 Configuration Files. Step 4 If the system is running the M2000 service, stop the M2000 service first. For details on how to stop the M2000, see 7.3.4 Stopping M2000 Services. Step 5 Switch to user dbuser. # su - dbuser Step 6 Stop the Sybase. For details about how to stop the Sybase, see 15.2.3 How to Stop the Sybase. Step 7 Log out as user dbuser and switch to user root. -bash-3.00$ exit Step 8 Edit the /etc/hosts file to modify or add the IP addresses of M2000 server, such as the original physical IP addresses of two network ports and the logical IP address. If there are any changes to the IP address of the IPMP, modify the IP address in the /etc/inet/ipnodes file. # vi /etc/hosts Step 9 Edit the /etc/inet/ipnodes file to modify or add the IP addresses of M2000 server, such as the original physical IP addresses of two network ports and the logical IP address. If there are any changes to the IP address of the IPMP, modify the IP address in the /etc/inet/ipnodes file. # vi /etc/inet/ipnodes Step 10 Change the extended network number and the mask in the /etc/netmasks file. # vi /etc/netmasks
NOTE
You can obtain an extended network number after performing the logic AND operation between an IP address and its mask. For example, if an IP address is 12.34.56.78 and its mask is 255.255.255.0, you can infer that the corresponding extended network number is 12.34.56.0. You must use the Tab key to isolate an extended network number from its mask.
Step 11 Change the default route in the /etc/defaultrouter file. # vi /etc/defaultrouter Edit /etc/defaultrouter to change the default route. If the file does not exist in /etc, create the file and add the IP address, such as "10.10.10.1", to represent the route.
Step 12 Check whether the maintenance dual plane is configured. Then, determine whether to modify the corresponding file. Whether the Maintenance Dual Plane Is Step Configured Yes Edit /etc/hostname.ce0 and /etc/ hostname.ce2 to change the IP address. # vi /etc/hostname.ce0 # vi /etc/hostname.ce2 No You need to modify only the /etc/ hostname.ce0 file. # vi /etc/hostname.ce0
NOTE
l l l
If the /etc/hostname.ce0 and /etc/hostname.ce2 files record host names, you need not modify the two files. In the files /etc/hostname.ce0 and /etc/hostname.ce2, no space is allowed at the beginning of each line of content. The types of Ethernet adapters for the servers are different. If the server does not contain the /etc/ hostname.ce* file, modify the /etc/hostname.bge* file to change the existing IP address to a new IP address. Ensure that the default router in the /etc/defaultrouter file is valid, that is, the address of the router is accessible for servers.
Step 13 Run the following command to view the /opt/sybase/interfaces file. # vi /opt/sybase/interfaces
l
If the file records IP information, replace the existing IP address with a new IP address. Then, press Esc and run the :wq command to save the modification and exit. If the file does not record IP information, do not modify the file. Press Esc and run the :q command to exit. Query the name of the network adapter attached to the original IP address and determine the name of the network adapter attached to the new IP address. # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.8.11 netmask ffffff00 broadcast 192.168.8.255 ce0:1: flags=9040843@UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2 inet 192.168.8.21 netmask ffffff00 broadcast 192.168.8.255 ce0:2: flags=1040843@UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 2 inet 192.168.8.31 netmask ffffff00 broadcast 192.168.8.255 ether 0:3:ba:a7:bd:37
Step 14 Make the new IP address take effect. 1.
3-8
Issue 05 (2008-05-20)

l
As indicated in the command result, the name of the network adapter attached to the original IP address is ce0:2. The rule for naming the network adapter attached to the new IP address is ce0:X, where X is a number that has not been used. You can set X to a value that is equal to the existing maximum value plus one. In this example, the maximum value of the original network adapter name is 2. Thus, X can be set to 3. That is, ce0:3 is used as the name of the network adapter attached to the new IP address.
NOTE
If the name of the network adapter attached to the original IP address is ce0, you can set the name of the network adapter attached to the new IP address to ce0:1.
2.
Make the new IP address take effect. For example, the name of the network adapter attached to the new IP address is ce0:3, the new IP address is 10.10.10.10, and the subnet mask is 255.255.255.0. # ifconfig ce0:3 plumb # ifconfig ce0:3 inet 10.10.10.10 netmask 255.255.255.0 up
NOTE
Run the ifconfig -a command again to check whether the new IP address is attached to the specified network adapter.
Whether the M2000 Server Software Is Installed Yes No
Then ... Proceed with Step 15. Proceed with Step 17.
Step 15 Check whether the Sybase service is running. If the Sybase service is not running, start the Sybase service. For details about how to start the Sybase service, see 15.2.1 How to Know Whether the Sybase Is Started and 15.2.2 How to Start the Sybase. Step 16 Modify the M2000 configuration files. 1. Run a script to modify the M2000 configuration file. # . /opt/OMC/svc_profile.sh # . /opt/sybase/SYBASE.sh # cd /opt/OMC/tools/config # ./modify.sh When the main menu is displayed, choose 1--Single system > 1--IP for omc. 2. 3. As prompted by the system, enter the host name, the Sybase database server name, the old IP address, the new IP address. When the following message is displayed, enter y to modify the M2000 configuration file. Enter n to exit.
4.
Issue 05 (2008-05-20)
When the main menu is displayed again, enter q to exit.

If the modification fails, restore the M2000 configuration file first. Then, repeat the steps mentioned previously. For details, see 15.4.7 How to Restore the M2000 Configuration Files. Step 17 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 If the M2000 software is installed, the Sybase and M2000 services restart automatically after the Solaris restarts. ----End
3.3 Modifying the IP Address of the SC on the M2000 Server

This describes how to modify the IP address of the SC on the M2000 server. The SC can be the SC on the Netra 240 server, RSC on the V890 server, or SC on the E4900 server. In special situations, you can log in to the M2000 server through the IP address of the SC to operate and maintain the server. 3.3.1 Modifying the IP Address of the SC on the Netra 240 Server This describes how to modify the IP address of the SC on the Netra 240 server to comply with the specification. 3.3.2 Changing the IP Address of the RSC on the V890 Server This describes how to change the IP address of the RSC on the V890 server. 3.3.3 Modifying the IP Address of the SC on the E4900 Server This describes how to modify the IP address of the SC on the E4900 server so that the new IP address complies with the specification. The IP address of the SC on the E4900 server can be the IP address of the standby SC1 or the IP address of the active SC0.
3.3.1 Modifying the IP Address of the SC on the Netra 240 Server

This describes how to modify the IP address of the SC on the Netra 240 server to comply with the specification.
Prerequisite
l l l
The PC terminal and the interface of the SC on the server communicate normally. The password for user admin of the SC is available. The new IP address of the SC is planned.
Procedure
Step 1 Run the following command on the PC terminal to establish the connection between the PC and the SC: telnet original IP address of SC
3-10
Issue 05 (2008-05-20)

NOTE
If the PC and SC cannot be connected by running the telnet command, connect them through a serial port cable. For details, refer to Configuring the SC for the Netra 240 Server in the M2000 Software Installation Guide (Netra 240,S10).
Step 2 Log in to the SC as user admin. Step 3 Set the new IP address and the subnet mask for the SC on the server. sc> setsc netsc_ipaddr new IP address of SC sc> setsc netsc_ipnetmask subnet mask of SC sc> setsc netsc_ipgateway gateway address of the SC Step 4 To restart the SC on the server, run the following command: sc> resetsc ----End
3.3.2 Changing the IP Address of the RSC on the V890 Server

This describes how to change the IP address of the RSC on the V890 server.
Prerequisite
l l l
The network communication between the PC terminal and the RSC server is normal. You have obtained the password of the RSC user admin. A new IP address of the SC is planned.
Procedure
Step 1 Run the following command on the PC terminal to establish the connection between the PC and the RSC: telnet original IP address of RSC Step 2 Log in to the RSC and run the following commands to change the IP address of RSC: rsc> set ip_mode config rsc> set ip_addr X.X.X.X rsc> set ip_netmask X.X.X.X rsc> set ip_gateway X.X.X.X
NOTE
l l l
In ip_addr X.X.X.X, X.X.X.X indicates a new IP address planned for the RSC. In ip_netmask X.X.X.X, X.X.X.X indicates a new subnet mask planned for the RSC. In ip_gateway X.X.X.X, X.X.X.X indicates a new gateway planned for the RSC.
Step 3 Restart the RSC for the modification to take effect. rsc> resetrsc When the system prompts the following message, type y for confirmation.
Are you sure you want to reboot RSC (Yes/No)?
----End
3.3.3 Modifying the IP Address of the SC on the E4900 Server

This describes how to modify the IP address of the SC on the E4900 server so that the new IP address complies with the specification. The IP address of the SC on the E4900 server can be the IP address of the standby SC1 or the IP address of the active SC0.
Prerequisite
l
The PC terminal communicates normally with the ports of the standby SC1 and the active SC0. The two new IP addresses of the SC are planned.
Procedure
Step 1 Change the IP address of the standby SC1. 1. Run the following command on the PC terminal to establish the connection between the PC and the SC1: telnet original IP address of SC1
NOTE
If the PC and SC1 cannot be connected by the telnet command, connect them through a serial port cable. For details, refer to Configuring SC1 in the M2000 Software Installation Guide (E4900 +6140,S10).
2. 3.
Log in to the SC as user admin. Set the parameters for the standby controller. :sc> setupplatform
NOTE
When using the command setupplatform to change the IP address of SC1, you also need to enter parameters such as the host name of SC1. If you need to modify only the IP address of the SC1, retain the original settings of other parameters.
4.
Change the IP address of SC1 according to Table 3-2. When the system displays any parameter that is not listed in Table 3-2, press Enter to continue. Table 3-2 Parameters for the standby controller Parameter
Use DHCP or static network settings? [DHCP]:
Value static Retain the host name of SC1 Enter the new IP address of SC1 Enter the actual subnet mask, if required
Issue 05 (2008-05-20)
Hostname IP Address Netmask
3-12
Parameter Gateway Enable SC Failover? [no]:
Value Enter the IP address of the actual gateway, if required yes
5.
Restart the backup SC1. :sc> reboot When the system prompts the following message, enter y, and then press Enter.
Are you sure you want to reboot the system controller now? [no]
NOTE
l l
When the system prompts other messages, retain the default settings and press Enter. Restarting SC1 takes some time. You need to wait for a while.
When the system displays osssvr-1-sc1:sc>, you can infer that the controller is restarted. The osssvr-1-sc1 is the host name of SC1. Step 2 Change the IP address of the active SC0. 1. Run the following commands on the PC terminal to establish the connection between the PC and the SC0. telnet original IP address of SC0
NOTE
If the PC and SC0 cannot be connected by the telnet command, connect them through a serial port cable. For details, refer to Configuring SC0the M2000 Software Installation Guide (E4900 +6140,S10).
2.
Configure the parameters for the active controller. :SC> setupplatform

NOTE
When using the setupplatform command to change the IP address of SC0, you also need to enter parameters such as the host name of SC0. If you need to modify only the IP address of the SC0, retain the original settings of other parameters.
3.
Change the IP address of SC0 according to Table 3-3. When the system prompts any parameter that is not listed in Table 3-3, press Enter to continue. Table 3-3 Parameters for the standby controller Parameter
Use DHCP or static network settings? [DHCP]:
Value static Retain the host name of SC0 Enter the new IP address of SC0
3-13
Hostname IP Address
Issue 05 (2008-05-20)
Parameter Netmask Gateway Enable SC Failover? [no]:

Connection type (ssh, telnet, none) [telnet]: Logical Hostname or IP Address [ ]:
Value Enter the actual subnet mask, if required Enter the IP address of the actual gateway, if required yes telnet Retain the logical host name of the SC
4.
Restart the backup SC0. :SC> reboot When the system prompts the following message, enter y, and then press Enter.
Are you sure you want to reboot the system controller now? [no]
NOTE
l l
When the system prompts other messages, keep the default settings and press Enter. Restarting SC1 takes some time. You need to wait for a while.
When the system displays osssvr-1-sc0:SC>, you can infer that the controller is restarted. The name osssvr-1-sc0 is the host name of SC0. ----End
3.4 Modifying the IP Address of the Disk Array

This describes how to modify the IP address of the disk array. By modifying the IP address of the disk array, you can maintain the disk array easily. 3.4.1 Modifying the IP Address of the 3320 Disk Array This describes how to modify the IP address of the 3320 disk array. To perform this task, you need to log in to the 3320 disk array through PC or administration console. 3.4.2 Modifying the IP Address of the 6140 Disk Array This describes how to modify the IP address of the 6140 disk array. To modify the IP address of the 6140 disk array, the server must be installed with the 6140 management host software. Before delivery, the 6140 management host software is usually installed on the administration console. If the system does not configure the administration console, the 6140 management host software is installed on the M2000 server. When modifying the IP address of the 6140 disk array, you need to log in to the management host software as user root. To modify the IP address on the administration console and the server, the methods of logging in to the management host software are different.
3.4.1 Modifying the IP Address of the 3320 Disk Array

This describes how to modify the IP address of the 3320 disk array. To perform this task, you need to log in to the 3320 disk array through PC or administration console.
Prerequisite
l l
The SUNWsscs software has been installed on the server. All the IO operations related to the disk array have been stopped.
Context
CAUTION
l
If the system is operating the Sybase, stop it before modifying the IP address of the disk array. For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. If the system is operating the M2000, stop the M2000 service before modifying the IP address of the disk array. For details, refer to 7.3.4 Stopping M2000 Services.
Procedure
Step 1 To modify the IP address of the 3320 disk array, run the following command: # sccli sccli > configure network-interface lan0 ip-address IP address netmask Subnet mask gateway Gateway address Take the setting of the IP address for the 3320 disk array to 192.168.8.39 as an example. Supposing the subnet mask is 255.255.255.0 while the gateway address is 192.168.8.1, run the following command: sccli > configure network-interface lan0 ip-address 192.168.8.39 netmask 255.255.255.0 gateway 192.168.8.1 Then, the following message is displayed:
sccli changes will not take effect until controller is reset
Step 2 To restart the controller, run the following command: sccli > reset controller Step 3 When the system displays the following prompt, enter y.
Are you sure?
----End
3.4.2 Modifying the IP Address of the 6140 Disk Array

This describes how to modify the IP address of the 6140 disk array. To modify the IP address of the 6140 disk array, the server must be installed with the 6140 management host software. Before delivery, the 6140 management host software is usually installed on the administration console. If the system does not configure the administration console, the 6140 management host software is installed on the M2000 server. When modifying the IP address of the 6140 disk array, you need to log in to the management host software as user root. To modify the IP address on
the administration console and the server, the methods of logging in to the management host software are different.
Prerequisite
All the I/O operations related to the disk array have been stopped.
Context
CAUTION
l
If the system is operating the Sybase, stop it before modifying the IP address of the disk array. For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. If the system is operating the M2000, stop the M2000 service before modifying the IP address of the disk array. For details, refer to 7.3.4 Stopping M2000 Services.
NOTE
Enter the name of the 6140 disk array and IP address that is involved in the following command Refer to Host Name and IP Address for the E4900 ServerRefer to Host Name and IP Address for the V890 Server.
Procedure
Step 1 Modify the IP address of the 6140 disk array through the administration console or the server. If... You modify the IP address through the server, You modify the IP address through the administration console, Then... Perform Step 2 and Step 3. Perform Step 4 and Step 5.
If you modify the IP address of the 6140 disk array through the server, ensure that the network connection between the server and the 6140 disk array is normal and that you have obtained the IP address of the server. If you modify the IP address of the 6140 disk array through the administration console, you need to first log in to the administration console through the PC, and then log in to the management host software. Therefore, you need to ensure that the communication between the PC and the administration console and between the administration console and the 6140 disk array is normal and that you have obtained the IP address of the SC on the administration console and the password of user admin. Log in to the server as user root. telnet IP address of the M2000 server Enter the user name and password of user root to log in to the server.
Step 2 Log in to the management host software on the server. 1.
3-16
Issue 05 (2008-05-20)
2.
Check whether the server can communicate with controller A of the 6140 disk array. If the server requires to communicate with the 6140 disk array, you need to ensure that the IP address of the network port is on the same network segment as the IP address of controller A on the disk array. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.128.101 If the system output contains 192.168.128.101 is alive after you run the above command, you can infer that the IP address of the server is on the same network segment as the IP address of controller A. Proceed with Step 2.6. Otherwise, you need to perform Step 2.3 through Step 2.5 to set the temporary subnet to ensure that the two IP addresses are on the same network segment.
3.
Determine the name of the network port used to set the temporary subnet. When setting the temporary subnet, choose ce0 as the communication network port. Run the following command to check the name of the network port corresponding to the last IP address bound to this network port. # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index inet 192.168.8.11 netmask ffffff00 broadcast 192.168.8.255 ether 0:3:ba:bb:bc:ad ce1: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index inet 0.0.0.0 netmask 0 ether 0:3:ba:bb:bc:ae ce2: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index inet 0.0.0.0 netmask ffffff00 broadcast 0.0.0.0 ether 0:3:ba:bb:bc:af ce3: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index inet 0.0.0.0 netmask 0 ether 0:3:ba:bb:bc:b0 8232 2 3 4 5
When the network port binds two or more IP addresses, the name of the network port is displayed as ce0:X after you run the preceding commands. Where X is a number starting from 1. When setting the temporary subnet, you cannot use the displayed name of the network port. The above system output indicates that ce0 has configured an IP address. When setting the temporary subnet, you can select ce0:1 as the name of the network port. 4. When setting the temporary subnet, ensure that the IP address of the server is on the same network segment as the IP address of controller A.
CAUTION
The IP address of the server must be on the same network segment as the IP address of controller A. Otherwise, the server cannot have access to the disk array. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ifconfig ce0:1 plumb
# ifconfig ce0:1 192.168.128.100 up 5. Check the setting of the temporary subnet. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.128.101 If the system output contains 192.168.128.101 is alive, you can infer that the setting is correct. Otherwise, perform Step 2.4 to set the temporary subnet again. 6. Run the following command on the server to log in to the management host software as user root. # /opt/SUNWsesscs/cli/bin/sscs login -h host name of the server -u root When the system displays Type your password:, enter the password of user root. Step 3 Perform the following steps on the server to modify the IP address of the 6140 disk array. 1. Run the following command to check whether the 6140 disk array is registered. # /opt/SUNWsesscs/cli/bin/sscs list storage-system
Array: array.no.name
In the system output, array.no.name is the default name of the registered 6140 disk array. If the system returns the similar message, you can infer that the 6140 disk is registered. Otherwise, the 6140 disk array is not registered. 2. If the 6140 disk array is not registered, run the following command to register the disk array to the management host software through controller A. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # /opt/SUNWsesscs/cli/bin/sscs add -i 192.168.128.101 registeredarray 3. Modify the IP address of controller A on the 6140 disk array. In this part, the operation on the 6140 disk array whose disk array name is ST6140-1 is taken as an example. Replace the parameters in the commands with the actual parameters when modifying the IP addresses of other 6140 disk arrays. # /opt/SUNWsesscs/cli/bin/sscs modify -a Name of the 6140 disk array (ST6140-1) -g IP address of the gateway -i IP address of controller A on the 6140 disk array -m subnet mask controller A 4. Set the temporary subnet again to make the IP address of the server be on the same network segment as the IP address of controller A.
CAUTION
The IP address of the server must be on the same network segment as the modified IP address of controller A. Otherwise, the server cannot have access to the disk array.
3-18
Issue 05 (2008-05-20)
In the following commands, the modified IP address 10.70.12.12 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ifconfig ce0:1 plumb # ifconfig ce0:1 10.70.12.100 up 5. Check the setting of the temporary subnet. In the following commands, the modified IP address 10.70.12.12 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 10.70.12.12 If the system output contains 10.70.12.12 is alive, you can infer that the setting is correct. Otherwise, perform Step 3.4 to set the temporary subnet again. 6. Log in to the management host software as user root. # /opt/SUNWsesscs/cli/bin/sscs login -h host name of the server -u root When the system displays Type your password:, enter the password of user root. 7. Register the disk array to the management host software through controller A. # /opt/SUNWsesscs/cli/bin/sscs add -i 10.70.12.12 registeredarray
NOTE
In the following commands, 10.70.12.12 is the IP address of controller A. This address must be the same as that set in Step 3.3.
8.
Modify the IP address of controller B. In this part, the operation on the 6140 disk array whose disk array name is ST6140-1 is taken as an example. Replace the parameters in the commands with the actual parameters when modifying the IP addresses of other 6140 disk arrays. # /opt/SUNWsesscs/cli/bin/sscs modify -a Name of the 6140 disk array (ST6140-1) -g IP address of the gateway -i IP address of controller B on the 6140 disk array -m subnet mask controller B
Step 4 Log in to the management host software on the administration console. 1. 2. Log in to the administration console through the PC. For details, refer to Logging In to the Netra 240 Server Through the SC. Check whether the administration console can communicate with controller A of the 6140 disk array. If the administration console requires to communicate with the 6140 disk array, you need to ensure that the IP address of the network port is on the same network segment as the IP address of controller A on the disk array. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.128.101 If the system output contains 192.168.128.101 is alive after you run the above command, you can infer that the IP address of the administration console is on the same network segment as the IP address of controller A. Proceed with Step 4.6. Otherwise, you
need to perform Step 4.3 through Step 4.5 to set the temporary subnet to ensure that the two IP addresses are on the same network segment. 3. Determine the name of the network port used to set the temporary subnet. When setting the temporary subnet, choose bge0 as the communication network port. Run the following command to check the name of the network port corresponding to the last IP address bound to this network port. # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 bge0: flags=1000843<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.8.236 netmask ffffff00 broadcast 192.168.8.255 ether 0:3:ba:bb:bc:ad bge1: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 0.0.0.0 netmask 0 ether 0:3:ba:bb:bc:ae bge2: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 inet 0.0.0.0 netmask ffffff00 broadcast 0.0.0.0 ether 0:3:ba:bb:bc:af bge3: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index 5 inet 0.0.0.0 netmask 0 ether 0:3:ba:bb:bc:b0
When the network port binds two or more IP addresses, the name of the network port is displayed as bge0:X after you run the preceding commands. Where X is a number starting from 1. When setting the temporary subnet, you cannot use the displayed name of the network port. The above system output indicates that bge0 has configured an IP address. When setting the temporary subnet, you can select bge0:1 as the name of the network port. 4. When setting the temporary subnet, ensure that the IP address of the administration console is on the same network segment as the IP address of controller A.
CAUTION
The IP address of the administration console must be on the same network segment as the IP address of controller A. Otherwise, the administration console cannot have access to the disk array. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ifconfig bge0:1 plumb # ifconfig bge0:1 192.168.128.100 up 5. Check the setting of the temporary subnet. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.128.101 If the system output contains 192.168.128.101 is alive, you can infer that the setting is correct. Otherwise, perform Step 4.3 and Step 4.4 to set the temporary subnet again.
6.
Run the following command on the administration console to log in to the management host software as user root. # /opt/SUNWsesscs/cli/bin/sscs login -h Host name of the administration console -u root When the system displays Type your password:, enter the password of user root.
Step 5 Perform the following steps on the administration console to modify the IP address of the 6140 disk array. 1. Run the following command to check whether the 6140 disk array is registered. # /opt/SUNWsesscs/cli/bin/sscs list storage-system
Array: array.no.name
In the system output, array.no.name is the default name of the registered 6140 disk array. If the system returns the similar message, you can infer that the 6140 disk is registered. Otherwise, the 6140 disk array is not registered. 2. If the 6140 disk array is not registered, run the following command to register the disk array to the management host software through controller A. In the following commands, the default IP address 192.168.128.101 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # /opt/SUNWsesscs/cli/bin/sscs add -i 192.168.128.101 registeredarray 3. Modify the IP address of controller A on the 6140 disk array. In this part, the operation on the 6140 disk array whose disk array name is ST6140-1 is taken as an example. Replace the parameters in the commands with the actual parameters when modifying the IP addresses of other 6140 disk arrays. # /opt/SUNWsesscs/cli/bin/sscs modify -a Name of the 6140 disk array (ST6140-1) -g IP address of the gateway -i IP address of controller A on the 6140 disk array -m subnet mask controller A 4. Set the temporary subnet again to make the IP address of the administration console be on the same network segment as the IP address of controller A.
CAUTION
The IP address of the administration console must be on the same network segment as the modified IP address of controller A. Otherwise, the administration console cannot have access to the disk array. In the following commands, the modified IP address 10.70.12.12 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ifconfig bge0:1 plumb # ifconfig bge0:1 10.70.12.100 up 5.
Issue 05 (2008-05-20)
Check the setting of the temporary subnet.

In the following commands, the modified IP address 10.70.12.12 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 10.70.12.12 If the system output contains 10.70.12.12 is alive, you can infer that the setting is correct. Otherwise, perform Step 5.4 to set the temporary subnet again. 6. Log in to the management host software as user root. # /opt/SUNWsesscs/cli/bin/sscs login -h Host name of the administration console -u root When the system displays Type your password:, enter the password of user root. 7. Register the disk array to the management host software through controller A. # /opt/SUNWsesscs/cli/bin/sscs add -i 10.70.12.12 registeredarray
NOTE
In the preceding commands, 10.70.12.12 is the IP address of controller A. This address must be the same as that set in Step 5.3.
8.
Modify the IP address of controller B. In this part, the operation on the 6140 disk array whose disk array name is ST6140-1 is taken as an example. Replace the parameters in the commands with the actual parameters when modifying the IP addresses of other 6140 disk arrays. # /opt/SUNWsesscs/cli/bin/sscs modify -a Name of the 6140 disk array (ST6140-1) -g IP address of the gateway -i IP address of controller B on the 6140 disk array -m subnet mask controller B
----End
3-22
Issue 05 (2008-05-20)
4 Managing the M2000 Clients
4
About This Chapter
Context
l
Managing the M2000 Clients
This describes how to manage the M2000 clients. The graphic user interface (GUI) on the M2000 client supports the O&M for the NEs and enables you to monitor the M2000. You must manage the M2000 clients to ensure their normal operation.
The requirements of the M2000 client for operation rights are as follows: The users who have the rights to install, upgrade, and uninstall the M2000 client must belong to the user group Administrators. The users who are responsible for the routine maintenance of the M2000 client must belong to the user group Users and have the read and write rights of the M2000 client installation directory.
4.1 Managing Files and Disks on M2000 Clients This describes how to manage the file systems and disks on the M2000 clients. 4.2 Setting the Maximum Number of Sessions This describes how to set the maximum number of sessions for the M2000 server. The number of sessions is in positive correlation with the consumed system resources. 4.3 Monitoring the Login Status of Clients This describes how to monitor the login states of the clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the maximum number set for MaxSession, you must force a user out to establish a new connection. 4.4 Setting the Number of Clients Accessible on a PC This describes how to edit the communicate.xml file on the M2000 client for setting the number of clients (excluding the LMTs that access NEs through the M2000 proxy) that can be started on a PC. 4.5 Setting the Time Information on the M2000 Client This describes how to set the time information on the M2000 client.
Issue 05 (2008-05-20)
4-1
4.1 Managing Files and Disks on M2000 Clients

This describes how to manage the file systems and disks on the M2000 clients. 4.1.1 Introduction to the M2000 Client File System This introduces the M2000 client file system. 4.1.2 Clearing the Disk Space of an M2000 Client This describes how to clear the disk space of an M2000 client. Before performing this operation, ensure that the files to be deleted are not required for future operations. Deleting a useful file by mistake may lead to a system operation error.
4.1.1 Introduction to the M2000 Client File System

This introduces the M2000 client file system. The client software runs on the Windows operating system and is based on the JAVA virtual machine. The installation package of the M2000 client software includes the JAVA virtual machine supported by Windows. The required free disk space on the M2000 client is as follows:
l
Without the integration of the LMT: F = I + T + (S x N) With the integration of the LMT: F = I + T + (S x N) + (L x N)
Table 4-1 describes the parameters specified in the equations. Table 4-1 Parameter description Parameter F I T Description Free disk space (MB) Initial version size (about 300 MB) Temporary space for storing the patches required for the upgrade (smaller than 20 MB) Size of NE adaptation file (3 MB to 10 MB) Number of NE versions (based on requirements) Size of integrated LMT file (20 MB to 50 MB)
S N L
Table 4-2 lists the folders related to the M2000 client software.
4-2
Issue 05 (2008-05-20)
Table 4-2 Folders related to the M2000 client software Folder M2000 client installation path Description Refers to the M2000 client installation path. The default path is C: \iManagerM2000Client. Refers to the directory for saving client programs. Refers to the directory for saving the executable files. Refers to the directory for saving the NE configuration files. Refers to the directory for saving the information that is used for locating problems.
NOTE This directory appears only after you run the M2000 diagnostic tool.
M2000 client installation path\client M2000 client installation path\client\bin M2000 client installation path\client\Data M2000 client installation path\client \diagnosis
M2000 client installation path\client\dtd M2000 client installation path\client\help M2000 client installation path\client \IDAPI32 M2000 client installation path\client\jre M2000 client installation path\client\lib M2000 client installation path\client \localWS M2000 client installation path\client\style M2000 client installation path\client \Templates M2000 client installation path\client\tmp M2000 client installation path\client \tracefile M2000 client installation path\uninstall M2000 client installation path\client \update
Refers to the directory for saving the Dtd files. Refers to the directory for saving the online help files. Refers to the directory for saving the localWS dynamic link libraries. Refers to the Java operating environment. Refers to the directory for saving the library files. Refers to the directory for saving LocalShell that is used to start the 2G LMT. Refers to the directory for saving the configuration files of client. Refers to the directory for saving the mapping between administrative regions and their IDs. Refers to the directory for saving temporary files during the upgrade. Refers to the directory for saving the trace files. Refers to the directory for saving the uninstaller. Refers to the directory for saving the upgrade files.
Issue 05 (2008-05-20)
4-3
4.1.2 Clearing the Disk Space of an M2000 Client

This describes how to clear the disk space of an M2000 client. Before performing this operation, ensure that the files to be deleted are not required for future operations. Deleting a useful file by mistake may lead to a system operation error.
Context
CAUTION
You can delete the files when the client is running. Do not delete the files generated on that day. During the routine O&M, back up and clear the following files:
l l
Trace logs Temporary files after the running of the M2000 log collector
Procedure
l Delete the trace logs. Delete the history trace logs saved in the directory M2000 client installation path\client \tracefile. It is recommended that you preserve the trace logs generated in the latest two weeks. l Delete the temporary files generated after the running of the M2000 log collector. Delete the temporary files that are generated after the running of the M2000 log collector and are saved in the directory M2000 client installation path\client\diagnosis. ----End
4.2 Setting the Maximum Number of Sessions

This describes how to set the maximum number of sessions for the M2000 server. The number of sessions is in positive correlation with the consumed system resources.
Prerequisite
l l
You are authorized to perform security settings. The M2000 server is started and you have logged in to the M2000 client.
Context
Multiple M2000 clients or NMSs may connect to the same M2000 server at the same time and establish sessions with the server. If the sessions are excessive, the performance of the M2000 server may be affected. The M2000 provides the function of setting the maximum number of sessions for clients in an effort to manage the number of accessed sessions. The following programs can establish sessions with the M2000 server:
l
M2000 clients
4-4

l
LMT and NE enhanced maintenance function components that get access to NodeBs through the agent service function of the M2000 CME that gets access to NEs through the agent service function of the M2000 NMS Others, such as the script tool using the 3rdTools function
l l l
The number of required sessions equals to the sum of the previous sessions. In addition, the sessions getting access to the M2000 server are restricted by the maximum number of sessions that is set in the license file. If G is equal to the maximum number of sessions set on a client, L is equal to the maximum number of sessions set in the License file.
l
If G is greater than or equal to L, you can infer that the number of accessible clients is determined by L. If G is smaller than L, you can infer that the number of accessible clients is determined by G.
Procedure
Step 1 Choose Security > Security Policy to view the Security Settings window. Step 2 In the displayed Security Settings dialog box, choose System Policy and set the maximum number of sessions in the Maximum Sessions field. Step 3 Click Apply. ----End
4.3 Monitoring the Login Status of Clients

This describes how to monitor the login states of the clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the maximum number set for MaxSession, you must force a user out to establish a new connection.
Prerequisite
Before monitoring the login status of clients, ensure that you are authorized to monitor the users.
Procedure
Step 1 Start the M2000 client and log in to the M2000. Step 2 Choose Security > User Monitor. The User Monitor dialog box is displayed. Step 3 Click the User Session Monitor tab to monitor all the terminals connected to the M2000 system. Pay close attention to the information about the IP addresses of monitored users and login time. Step 4 Click Refresh to refresh the session list. Step 5 This step is optional. If you need to force a user to exit, select the user, and then click Force User to Exit.

NOTE
The user of the selected client is forced out. The users of the other clients do not exit.
----End
4.4 Setting the Number of Clients Accessible on a PC

This describes how to edit the communicate.xml file on the M2000 client for setting the number of clients (excluding the LMTs that access NEs through the M2000 proxy) that can be started on a PC.
Prerequisite
l l
You have logged in to the PC as a user in the user group Users. The M2000 client is operational.
Context
Ideally, a maximum of 31 clients can be connected to a PC. The number of clients connected to a PC depends on the configuration of the PC and that of the server connected to the PC. The value of corba_portpool sets the port range that the client attempts to occupy. The minimum port number is separated from the maximum number by "-". The client tests the port from the minimum number to the maximum number. If all the ports are occupied, the system gives an Error message. You can set the maximum number of clients started on a PC by modifying the parameter value.
Procedure
Step 1 Open the communicate.xml file in the M2000 client installation path\client\style\defaultstyle \conf\communicate directory. Step 2 Find the attributes of the monitored ports, and then change the range of the monitored ports as required.
<PARAS>  <PARA name="corba_timeout" value="600"/>  <PARA name="heartbeat_interval" value="20"/>  <PARA name="heartbeat_timeout" value="2"/>  <PARA name="reconnect_interval" value="5"/> <PARA name="BiDirection" value="false"/>  <PARA name="corba_portpool" value="30500-30530"/>
4-6
Issue 05 (2008-05-20)

NOTE
l l
Ensure that the ports of this range on the firewall are enabled when you modify the port range. The ports may be used by other applications. Run the netstat -an command to check the occupation of the ports.
----End
4.5 Setting the Time Information on the M2000 Client

This describes how to set the time information on the M2000 client.
4.5.1 Modifying the Date, Time, and Time Zone on the M2000 Client
This describes how to change the date, time, and time zone of the Windows operating system. The M2000 client is a PC that operates under the Windows operating system.
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Choose Start > Settings > Control Panel. The Control Panel window is displayed. This takes a PC with Windows 2000 Professional as an example. Step 2 Double-click Date and Time. Step 3 In the Date and Time window, select the items that you want to change. Items to Be Changed Operation Hour Minute Second Time Zone Double-click Hour, and then click the arrow to change the value. Double-click Minute, and then click the arrow to change the value. Double-click Second, and then click the arrow to change the value. Click the Time Zone tab. On the Time Zone tab page, choose the local time zone from the drop-down list.
4.5.2 Setting the NTP Service on the M2000 Client

This describes how to set the M2000 client as the NTP client. This task enables you to synchronize the client with the NTP server through the NTP service of the Windows operating system.
Prerequisite
l
You have logged in to the Windows operating system. The Windows operating system is running properly. The M2000 client and the M2000 server communicate normally. The clock source of the server is operational.
l l
Context
When the M2000 client is configured as the NTP client, synchronize the time of the M2000 client with the time of the M2000 server. The configuration procedure is applicable to the Windows 2000 Professional or Windows XP Professional operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client. In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to 0, which is the default value. If the parameter LocalNTP does not exist, you can infer that the value can be ignored and the registry need not be modified. Step 2 Specify the NTP clock source. Choose Start > Run. Type cmd and press Enter. In the displayed window, run the following command: c:\>net time /setsntp:M2000 IP Address of NTP Server
NOTE
1. The result of the net time command is saved in the Windows registry. This setting of the net time takes effect after Windows restarts. 2. To clear the specification, run the net time /setsntp command.
Step 3 Check the NTP server specified by the PC. c:\>net time /querysntp
NOTE
l l
If the host name and IP address of the PC are specified as the host name and IP address of the NTP server by /setsntp, the NTP server time is the local time of the PC. If the NTP server changes the upper-level time server through the /setsntp option, restart the Windows Time service. To restart the Windows Time service, choose Start > Run. In the displayed Run dialog box, enter services.msc to open the Services window, and then press Enter. Identify the Windows Time service and restart the service. If the NTP client changes the time server through the /setsntp option, restart the Windows Time service.
Step 4 Check the operational status of the Simple Network Time Protocol (SNTP), using the w32tm command of the Windows. c:\>w32tm
The system displays the host name of the connected NTP server, deviation of the local time from that on the NTP server, and time cycle of NTP server roll.
NOTE
After running the w32tm command, wait until the command result is displayed.
----End
Issue 05 (2008-05-20)
4-9
5 Managing the M2000 Users
5
About This Chapter
Managing the M2000 Users
This chapter describes the four types of users involved in the operation of the M2000 system: Solaris user, Sybase user, network management user, and NE user. In addition, it describes the management and monitoring operations related to the types of users and M2000 user groups. 5.1 Types of M2000 Users This describes the four types of users involved in the operation of the M2000 system: Solaris user, Sybase user, network manager user, and NE user. In addition, it describes the mapping between the network manager user and NE user and the principle for assigning their rights. 5.2 Managing Solaris Users This describes how to manage the Solaris users. The four types of Solaris users involved in running the M2000 server are: root, dbuser, omcuser, and ftpuser. In addition, it describes how to create a user, remove a user, and modify a password. 5.3 Managing Sybase Users This describes how to manage the Sybase user that is required for the operation of the M2000. This also describes how to change the password of the Sybase user. 5.4 Creating OM Users OM users operate and maintain the entire network or specified NEs through the M2000. You can manage OM users by creating OM user groups, assigning the authority to OM user groups, and creating OM user accounts. 5.5 Modifying an OM User This describes how to modify an existing OM user. For an existing OM user, you can modify the user's authority, basic information, and password. 5.6 Deleting an OM User Group This describes how to delete an OM user group. You can delete an unwanted OM user group based on the requirements to save the system resource. The deletion of an OM user group indicates that only the authority of the OM user for the associated command groups is deleted. After the deletion, the OM user still exists without belonging to any user group. 5.7 Deleting an OM User This describes how to delete an OM user. Based on the requirements, you can delete an unneeded OM user to save the system resource. If an OM user already has the binding relationship with
an NE, the user bound to the NE is also deleted when you delete an OM user. In this way, the information on the OM user is removed from the M2000. 5.8 Querying Authorization You can query the authorization of the NEs and the M2000 rights in the M2000. 5.9 Comparing the OM User Rights You can compare the rights of two users in the M2000. 5.10 Managing NE Users This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. 5.11 Monitoring OM Users This describes how to monitor an OM user. The M2000 offers the user-monitoring function to monitor users' login and operations. This prevents illegal users from attacking the system.
5-2
Issue 05 (2008-05-20)
5.1 Types of M2000 Users

This describes the four types of users involved in the operation of the M2000 system: Solaris user, Sybase user, network manager user, and NE user. In addition, it describes the mapping between the network manager user and NE user and the principle for assigning their rights. 5.1.1 Introduction to Solaris Users This introduces the Solaris users involved in the operation of the M2000 server. 5.1.2 Introduction to Sybase Users This introduces the Sybase user accounts used by the M2000 and the mapping authorities. 5.1.3 NE User This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. The NE user can also troubleshoot NEs at the near end of NEs. 5.1.4 Principles of NM User Authorization This describes various privileges of the M2000 NM users and the principles for user authorization. The M2000 assigns privileges to user groups. The privileges assigned to a group are passed on to individual users based on the binding between the user group and the users in the user group. The privileges can also be assigned to users directly. 5.1.5 Principles of NE User Authorization This describes the principles of NE user authorization. The M2000 supports the authorization of operation privileges provided to NE user accounts.
5.1.1 Introduction to Solaris Users

This introduces the Solaris users involved in the operation of the M2000 server. To access the M2000 server, you must have a user account of a Solaris operating system. In addition to the default account of the Solaris operating system, that is, user root, you must have the three manually created user accounts: dbuser, omcuser, and ftpuser. You must also have one manually created user group: omcsysm. If the report system is installed, the report system automatically creates user account inrpt and user group inrpt. Table 5-1 describes the Solaris user accounts.
Issue 05 (2008-05-20)
5-3
Table 5-1 Solaris user accounts Account Name root Usage Authority Group Shell Resolution Program /sbin/sh Director y /
User root is the default user account of the system. User root is authorized to control all resources, create other user accounts, assign authorities to other users, and perform all system operations. User dbuser is the administrator of the database software. User dbuser is responsible for the O&M of the database software. Before installing the Sybase, you must manually create user dbuser.
User root owns the highest authority of the system. User root is authorized to install and uninstall M2000 server applications and to start and stop M2000 services.
Other, bin, sys, adm, uucp, mail, tty, lp, nuucp, daemon, and user.root
dbuser
User dbuser is authorized to perform all operations on the database. For example, user dbuser is authorized to use isql to interact with the database.
Staff
/bin/bash
/opt/ sybase
omcuser
User omcuser is the operator of the M2000. User omcuser is responsible for the O&M of the M2000 system, such as system status inquiry, system backup, and system restoration. Before installing the M2000 applications, you must create user omcuser.
User omcuser is authorized to access the database and perform the O&M operations. User omcuser is not allowed to install or uninstall M2000 server applications and to start or stop M2000 services.
Staff (primary group), sys, root, and omcsys m (seconda ry group)
/bin/bash
/export/ home/ omc
5-4
Issue 05 (2008-05-20)
Account Name ftpuser
Usage
Authority
Group
Shell Resolution Program /bin/bash
Director y /export/ home/ sysm
User ftpuser is used by the M2000 applications to perform software management and file transmission. Before installing the M2000 applications, you must create user ftpuser.
User ftpuser is authorized to perform software management and file transmissions for NEs.
omcsys m
inrpt
User inrpt is used by the M2000 report software to manage the report system.
User inrpt is authorized to manage the report system.
inrpt
/usr/bin/csh
/opt/inrpt
5.1.2 Introduction to Sybase Users

This introduces the Sybase user accounts used by the M2000 and the mapping authorities. To operate the database on the M2000 server, you must use a Sybase user account. Only Sybase users can operate the Sybase database. After the Sybase is installed, the default user account of the Sybase is sa, which has the highest authority. In the M2000 system, sa is the only database user. The default password of user sa is emsems.
5.1.3 NE User
This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users. The NE user can also troubleshoot NEs at the near end of NEs.
Type of NE Users
NE users consist of local NE users and non-local NE users.
l
The account, password, and authority of a local NE user are managed by NEs. The creation and modification of a local NE user are performed through the LMT. NEs provide several default local users. The account, password, and authority of a non-local NE user are managed by the M2000. The creation and modification of a non-local NE user are performed through the M2000.
Issue 05 (2008-05-20)
5-5
User Management of Category A NEs

Category A NEs support local and non-local NE users. If an OM user is granted with the MML authority of category A NEs, the OM user becomes a non-local user of the NEs. The M2000 manages non-local users, which integrates the OM user account and NE user account. Thus, non-local NE users have higher priority than local NE users. You can set whether to enable NE local user to log in to and manage NEs on the M2000.
User Management of Category B/C NEs

Category B/C NEs support only local NE users. To perform centralized management to category B/C NEs, you can create an NE User account in the M2000 NE User window. The user names and passwords of the accounts are the same with those of local NE users. Then you can associate the accounts to corresponding OM users.
NOTE
The user information are independent from each other. The system cannot synchronize the information about the two accounts. You need to manually synchronize the information about the NE user on the M2000 and the local user in the NEs.
5.1.4 Principles of NM User Authorization

This describes various privileges of the M2000 NM users and the principles for user authorization. The M2000 assigns privileges to user groups. The privileges assigned to a group are passed on to individual users based on the binding between the user group and the users in the user group. The privileges can also be assigned to users directly. A user group is a group of users who share the same privileges. The M2000 has three default user groups: Administrators, Operators, and Guests. Table 5-2 describes the M2000 user privileges. Table 5-2 Privileges of M2000 users Privileges Operation period Description Period during which M2000 users can log in to and operate the M2000 or NEs. If the current time is not within the period, M2000 users cannot log in. Validity of a user account Check the validity of a user account. Generally, the status of a user account is valid. If the status of a user account is invalid, the user cannot log in to or operate the M2000. Related Operations Setting the operation period when creating a user account Changing the operation period by modifying the attributes of a user account If a user account is locked for a period greater than the time set by the system, the system automatically unlocks the user account. The system also allows you to manually unlock a user account.
5-6
Issue 05 (2008-05-20)
Privileges Locking status
Description If the number of login failures of a user account during the specified period reaches the preset value, the system locks the user account. The user, whose account is invalid, cannot log in to or operate the M2000.
Related Operations Modifying user validity by modifying the attributes of a user account
Binding IP address
The M2000 does not restrict the IP address of the client using which users log in. After a M2000 user is bound to an IP address, the IP address of the client using which the user logs in must exist in the list of bound IP addresses.
Setting the list of bound IP addresses when creating a user account Changing the list of bound IP addresses by modifying the attributes of a user account
M2000 operation rights
A user has the authority to perform relevant operations on the M2000. After the privileges of users are bound, private privileges for operating the M2000 can be allocated to users directly. The public privileges for operating the M2000 can be allocated first to user groups and then to users based on the binding relations between the user groups and the users. Private privileges refer to the privileges enjoyed by private users. Public privileges are the privileges enjoyed by all the users in a user group. With regard to convenience and efficiency, the recommended privileges are public privileges.
Private privileges indicate that the privileges for operating the M2000 are allocated to users after their privileges are bound. Public privileges indicate that the privileges for operating the M2000 can be allocated first to user groups and then to users based on the binding relations between user groups and users.
5.1.5 Principles of NE User Authorization

This describes the principles of NE user authorization. The M2000 supports the authorization of operation privileges provided to NE user accounts. Each type of NEs provide certain default MML command group. In addition, you can customize new command groups. The principles of NE user authorization are as follows:
l
Prefer to use the default command groups provided by NEs. If you have to customize command groups, customize them as few as possible.
Issue 05 (2008-05-20)

l
Use the principles of NE user authorization for assigning the privileges that are commonly used by NE users and certain NE types. For the privileges that are applicable for certain NEs and cannot be assigned by using the principles of NE user authorization, you must assign them by directly setting users and the command groups of these NEs.
NOTE
l l
Superuser admin can run NE MML commands on the M2000 even without authorization. For details on the authority to manage an NE, refer to the M2000 Online Help.
5.2 Managing Solaris Users

This describes how to manage the Solaris users. The four types of Solaris users involved in running the M2000 server are: root, dbuser, omcuser, and ftpuser. In addition, it describes how to create a user, remove a user, and modify a password. 5.2.1 Introduction to Solaris Users This introduces the Solaris users involved in the operation of the M2000 server. 5.2.2 Changing the Password of User root This describes how to change the password of user root. 5.2.3 Changing the Password of User dbuser This describes how to change the password of user dbuser when you log in to the system as user root. 5.2.4 Changing the Password of User omcuser This describes how to change the password of user omcuser when you log in to the system as user root. 5.2.5 Changing the Password of the ftpuser User This describes how to change the password of ftpuser when you log in to the system as user root. 5.2.6 Creating a Solaris User This describes how to create a Solaris user. The Solaris user can operate and maintain the Solaris system. 5.2.7 Deleting a Solaris User This describes how to delete a Solaris user. You can manually delete the Solaris user that is not required.
5.2.1 Introduction to Solaris Users

This introduces the Solaris users involved in the operation of the M2000 server. To access the M2000 server, you must have a user account of a Solaris operating system. In addition to the default account of the Solaris operating system, that is, user root, you must have the three manually created user accounts: dbuser, omcuser, and ftpuser. You must also have one manually created user group: omcsysm. If the report system is installed, the report system automatically creates user account inrpt and user group inrpt. Table 5-3 describes the Solaris user accounts.
Table 5-3 Solaris user accounts Account Name root Usage Authority Group Shell Resolution Program /sbin/sh Director y /
User root is the default user account of the system. User root is authorized to control all resources, create other user accounts, assign authorities to other users, and perform all system operations. User dbuser is the administrator of the database software. User dbuser is responsible for the O&M of the database software. Before installing the Sybase, you must manually create user dbuser.
User root owns the highest authority of the system. User root is authorized to install and uninstall M2000 server applications and to start and stop M2000 services.
Other, bin, sys, adm, uucp, mail, tty, lp, nuucp, daemon, and user.root
dbuser
User dbuser is authorized to perform all operations on the database. For example, user dbuser is authorized to use isql to interact with the database.
Staff
/bin/bash
/opt/ sybase
omcuser
User omcuser is the operator of the M2000. User omcuser is responsible for the O&M of the M2000 system, such as system status inquiry, system backup, and system restoration. Before installing the M2000 applications, you must create user omcuser.
User omcuser is authorized to access the database and perform the O&M operations. User omcuser is not allowed to install or uninstall M2000 server applications and to start or stop M2000 services.
Staff (primary group), sys, root, and omcsys m (seconda ry group)
/bin/bash
/export/ home/ omc
Issue 05 (2008-05-20)
5-9
Account Name ftpuser
Usage
Authority
Group
Shell Resolution Program /bin/bash
Director y /export/ home/ sysm
User ftpuser is used by the M2000 applications to perform software management and file transmission. Before installing the M2000 applications, you must create user ftpuser.
User ftpuser is authorized to perform software management and file transmissions for NEs.
omcsys m
inrpt
User inrpt is used by the M2000 report software to manage the report system.
User inrpt is authorized to manage the report system.
inrpt
/usr/bin/csh
/opt/inrpt
5.2.2 Changing the Password of User root

This describes how to change the password of user root.
Prerequisite
l l
The old password of user root is available. The new password of user root is available.
Procedure
Step 1 Log in as user root, and then enter the old password of user root. Step 2 Change the password. # passwd root New password:new password Re-enter new password:new password
passwd: password successfully changed for root
----End
5.2.3 Changing the Password of User dbuser

This describes how to change the password of user dbuser when you log in to the system as user root.
Prerequisite
l l
The new password for dbuser is available. You have logged in to the UNIX as user root.
Procedure
Run the following command to change the password: # passwd dbuser New password:new password Re-enter new password:new password
passwd: password successfully changed for dbuser
----End
5.2.4 Changing the Password of User omcuser

This describes how to change the password of user omcuser when you log in to the system as user root.
Prerequisite
l l
The new password for omcuser is available. You have logged in to the UNIX as user root.
Procedure
Run the following command to change the password: # passwd omcuser New password:new password Re-enter new password:new password
passwd: password successfully changed for omcuser
----End
5.2.5 Changing the Password of the ftpuser User

This describes how to change the password of ftpuser when you log in to the system as user root.
Prerequisite
l l
The new password of user ftpuser is available. You have logged in to server as user root.
Issue 05 (2008-05-20)
5-11
Context
CAUTION
The password of user ftpuser cannot exceed 16 characters.
Procedure
Step 1 Back up the M2000 configuration files. For details, see 15.4.6 How to Back Up the M2000 Configuration Files. Step 2 If the system is running the M2000 service, stop the M2000 service first. For details on how to stop the M2000, see 7.3.4 Stopping M2000 Services. Step 3 Check whether the Sybase service is running. If the Sybase service is not running, start the Sybase service. For details, see 15.2.1 How to Know Whether the Sybase Is Started and 15.2.2 How to Start the Sybase. Step 4 To modify the password of user ftpuser, run the following command: # passwd ftpuser New password:new password Re-enter new password:new password
passwd: password successfully changed for ftpuser
Step 5 Modify the M2000 configuration files. 1. Run the script to modify the M2000 configuration file. # . /opt/OMC/svc_profile.sh # . /opt/sybase/SYBASE.sh # cd /opt/OMC/tools/config # ./modify.sh When the main menu is displayed, choose 1--Single system > 5--Password of ftpuser for omc. 2. 3. At the following prompt, enter the new password of user ftpuser:
Please input password of ftpuser:
When the following message is displayed, enter y to modify the M2000 configuration file. Enter n to exit.
If the modification fails, restore the M2000 configuration file first. Then, repeat the steps mentioned previously. For details, see 15.4.7 How to Restore the M2000 Configuration Files.
Step 6 Start the M2000 service. For details, see 7.3.3 Starting M2000 Services. ----End
5.2.6 Creating a Solaris User

This describes how to create a Solaris user. The Solaris user can operate and maintain the Solaris system.
Prerequisite
Keep the user account and password ready for the new user.
Context
Before the installation of the Sybase and the M2000 server software, create three Solaris user accounts: dbuser, omcuser, and ftpuser. For details, see the software installation manual related to each server type. You can also create other user accounts if required. After a user account is created, the details about this user account are saved in system files of the Solaris.
Procedure
Step 1 Log in to the server as user root. Step 2 Run the following command to create a new user account: # useradd Option new user account For instance, create a user account named omc1. User omc1 belongs to the staff group. The main directory /home1 is automatically created. The template files ensure a unified operating environment for all the users. The template files are located in the /etc/skel directory with user ID 123. This user account is in Bourne shell. # useradd -d /home1 -g staff -m -k /etc/skel -u 123 -s /bin/bash omc1
NOTE
l l l
-d dir: indicates the main directory. -m: indicates that if the main directory does not exist, the system creates this directory automatically. -k /etc/skel: indicates that a template file in a specified directory is copied to the main directory. Common template files include .profile and .cshrc. Template files enable each user to operate in the same environment. If you plan to run the useradd command to copy a template file to the main directory, you must check whether the main directory exists. If the main directory does not exist, run the useradd -m command to create one. If the main directory exists, the user group to which the created user belongs must have the read, write, and execute rights over the main directory. -g group: indicates the user group to which the user belongs. -s shell: indicates the shell that is used. -u uid: indicates the user ID. A user account has a unique ID.
l l l
For details of the useradd command, refer to 14.2.4.1 useradd Command.
Step 3 Run the following command to set the password for the new user: # passwd omc1
New password:new password Re-enter new password:new password

passwd: password successfully changed for omc1
----End
5.2.7 Deleting a Solaris User

This describes how to delete a Solaris user. You can manually delete the Solaris user that is not required.
Prerequisite
The account of the user to be deleted is available.
Procedure
Step 1 Log in to the M2000 server as user root. Step 2 Run the following command to delete a user account and the main directory of the account: # userdel -r user account Do not run the userdel command to delete a user when you are still logging in to the system. If you run the command, the system displays the following message:
UX: userdel: ERROR: root is in use. Cannot remove it.
For details of the userdel command, refer to 14.2.4.2 userdel Command.
CAUTION
Do not delete the users required for the OM of the M2000, such as ftpuser, dbuser, and omcuser. ----End
5.3 Managing Sybase Users

This describes how to manage the Sybase user that is required for the operation of the M2000. This also describes how to change the password of the Sybase user. 5.3.1 Introduction to Sybase Users This introduces the Sybase user accounts used by the M2000 and the mapping authorities. 5.3.2 Changing the Password of User sa This describes how to change the password of user sa.
5.3.1 Introduction to Sybase Users

This introduces the Sybase user accounts used by the M2000 and the mapping authorities. To operate the database on the M2000 server, you must use a Sybase user account.
Only Sybase users can operate the Sybase database. After the Sybase is installed, the default user account of the Sybase is sa, which has the highest authority. In the M2000 system, sa is the only database user. The default password of user sa is emsems.
5.3.2 Changing the Password of User sa

This describes how to change the password of user sa.
Prerequisite
Procedure
Step 1 Back up the M2000 configuration files. For details, see 15.4.6 How to Back Up the M2000 Configuration Files. Step 2 If the system is running the M2000 service, stop the M2000 service first. For details on how to stop the M2000, see 7.3.4 Stopping M2000 Services. Step 3 Check whether the Sybase service is running. If the Sybase service is not running, start the Sybase service. For details, see 15.2.1 How to Know Whether the Sybase Is Started and 15.2.2 How to Start the Sybase. Step 4 Change the password of Sybase user sa. # . /opt/sybase/SYBASE.sh # isql -Sdatabase server name -Usa -Pold password of user sa 1>sp_password old password of user sa,new password of user sa 2> go 1>exit
NOTE
After the Sybase server is started, run the following command to view the name of the database server: -bash-3.00$ ps -ef | grep "dataserver -s" | grep -v grep In the command result, the value after the -s parameter is the name of the database server. As shown in the following command result, the name of the database server in this example is SYB:
dbuser 15745 15744 3 11:00:39 ? 2:19 /opt/sybase/ASE-15_0 /bin/dataserver -sSYB -d/data/master.dat -e/opt/sybase/ASE-
Step 5 Modify the M2000 configuration files. 1. Run the script to modify the M2000 configuration file. # . /opt/OMC/svc_profile.sh # . /opt/sybase/SYBASE.sh # cd /opt/OMC/tools/config # ./modify.sh
When the main menu is displayed, choose 1--Single system > 4--Password of sa in sybase for omc. 2. 3. As prompted, enter the name of the Sybase database server and the new password of user sa. When the following message is displayed, enter y to modify the M2000 configuration file. Enter n to exit.
If the modification fails, restore the M2000 configuration file first. Then, repeat the steps mentioned previously. For details, see 15.4.7 How to Restore the M2000 Configuration Files. Step 6 Modify the /etc/init.d/OMC_sybase.dat file. # cd /etc/init.d # TERM=vt100; export TERM # vi OMC_sybase.dat In the OMC_sybase.dat file, search for PASSWORD. Its parameter value is the old password. Set the new password as the value of PASSWORD. Run the wq! command to forcibly exit. Step 7 Modify the authority of the OMC_sybase.dat file. # chmod 500 OMC_sybase.dat Step 8 Start the M2000 service. For details, see 7.3.3 Starting M2000 Services. ----End
5.4 Creating OM Users

OM users operate and maintain the entire network or specified NEs through the M2000. You can manage OM users by creating OM user groups, assigning the authority to OM user groups, and creating OM user accounts. 5.4.1 Process for Creating OM Users This describes the process for creating OM users. The complete process for creating an OM user consists of the following tasks: creating an OM user group, setting the managed domain for an OM user group, setting operation rights for an OM user group, creating an OM user account, setting the managed domain for an OM user account. In actual operations however, you may need to perform only some of the tasks. 5.4.2 Creating an OM User Group By creating an OM user group, you can manage the OM user accounts in groups and grant related rights to the members of the group. 5.4.3 Set the Managed Domain for an OM User Group You can set the managed domain for an OM user group to assign managed objects to the OM user group. 5.4.4 Assigning Operation Rights to an OM User Group This section describes how to assign operation rights to an OM user group. 5.4.5 Assigning Rights of New NEs to an OM User Group
You can allocate new device rights to an OM user group by NE type. When an NE is added, the user group has all the rights of the NE type to the NE. 5.4.6 Granting MML Authority to an OM User Group This describes how to assign the MML authority to an OM user group. This enables users in the same user group have the same MML authority. 5.4.7 Creating an OM User Account You can create the OM user accounts in the M2000 so that multiple OM users can operate and manage the M2000. 5.4.8 Synchronize OM user data This describes how to synchronize the OM user data. The synchronization of OM user data synchronizes the data on the M2000 with that of the associated NE. If the M2000 is disconnected from the NE, the data cannot be synchronized with that of the NE when you set the NE authority on the M2000. When the M2000 is reconnected to the NE, synchronize the data on the M2000 with that of the NE. 5.4.9 Adding an OM User to a User Group You can add the OM users to user groups. These users can be managed in a centralized manner and you can assign rights to the users in this way. 5.4.10 Assigning Operation Rights to an OM User This section describes how to assign operation rights to an OM user. 5.4.11 Setting the Managed Domain for an OM User You can set the managed domain for an OM user to allocate the managed objects to the user. 5.4.12 Setting the User ACL You can set the ACL to allow the users to log in to the M2000 through the clients of only the specific IP addresses or network segment. 5.4.13 Grant MML authority to an OM user This describes how to grant the MML authority to a specified OM user. The user can run all the commands in the command group to NEs. After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs.
5.4.1 Process for Creating OM Users

This describes the process for creating OM users. The complete process for creating an OM user consists of the following tasks: creating an OM user group, setting the managed domain for an OM user group, setting operation rights for an OM user group, creating an OM user account, setting the managed domain for an OM user account. In actual operations however, you may need to perform only some of the tasks. Table 5-4 shows a simple process for creating OM users. Table 5-4 Simple process for creating OM users Process 1 Then... Creating an OM User Account Description Create an OM user account so that users can use the account to log in to the M2000 client.
Issue 05 (2008-05-20)
5-17
Process 2
Then... Adding an OM User to a User Group
Description After a user is added to a user group, a user inherits the rights of the user group.
A complete process for creating OM users is displayed, as shown in Table 5-5. Table 5-5 Complete Process for Creating OM Users Process 1 2 Operation Create an OM user group Set the managed domain for an OM user group Description Grouping can reduce the complexity of user management. By setting the managed domain for a user group, you can set the objects that can be managed by a user group. By authorizing the user groups, you distribute the user groups with the corresponding rights. Distribute the rights for the new equipment to the user group to benefit the users by managing the new equipment. Before you operate the M2000, you should obtain the user account first. Synchronize the data of the M2000 with that of the NEs. Add a user to this user group. Then, the user automatically owns the rights of the user group. By setting the managed domain for the OM user, set the managed objects for the user. By authorizing the user, you assign the user with the corresponding rights. To ensure the security of the M2000, you can set the condition that the user can log in to the client only through a specific IP address.
Assign operation rights to an OM user group Assigning rights of new NEs to an OM user group
Create an OM user account
6 7
Synchronize OM user data Add an OM user to a user group
Set the managed domain for an OM user Assign operation rights to an OM user Set the user ACL
10
5-18
Issue 05 (2008-05-20)
Process 11
Operation Grant MML authority to an OM user
Description Assign OM users with the MML commands of the NEs. After the OM users have related operation rights, they can run the MML commands on the NEs.
5.4.2 Creating an OM User Group

By creating an OM user group, you can manage the OM user accounts in groups and grant related rights to the members of the group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, rightclick the User Group node and choose New User Group. Step 3 In the Add User Group dialog box, on the Detail tab, set Name and Description.You can also click Add to select the user you want to add to the user group, and then click Copy Rights From User Group to copy operation rights from other user groups. Step 4 Optional: If you want to set the managed domain for the user group, in the New User Group dialog box, click the Domain tab. Set the objects that are managed by the user group. Step 5 Optional: If you want to set operation rights for the user group, in the New User Group dialog box, click the Operation Rights tab. Set operation rights for the user group. Step 6 Optional: If you want to set new NE rights for the user group, in the New User Group dialog box, click the New Device Rights tab. Set new NE rights for the user group. Step 7 Click OK. ----End
5.4.3 Set the Managed Domain for an OM User Group

You can set the managed domain for an OM user group to assign managed objects to the OM user group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node, Select the user group you want to set. Step 3 In the pane on the right, click the Domain tab. Step 4 On the Domain tab, click Add.
Step 5 In the navigation tree of the Add Domain dialog box, select the managed objects for the user group, and then click OK. ----End
5.4.4 Assigning Operation Rights to an OM User Group

This section describes how to assign operation rights to an OM user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators group has all the operation rights. You cannot change the rights of this group. You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node, Select the user group you want to set. Step 3 From the pane on the right, click the Operation Rights tab. Step 4 On the Operation Rights tab, click Add. Step 5 In the Add Operation Rights dialog box, select the device type and corresponding rights. Click OK.
NOTE
If the type of the selected operation right is Network Device, you can do as follows:
l l l
You need to add the device to the managed domain of the user group before you set the operation rights to the device. Select the device in the left navigation tree, and select the operation rights to the device in the list on the right to add the operation rights. In the left navigation tree, right-click an NE or an object of an unknown type and choose Copy Rights. Then in the right navigation tree, right-click another NE or another object of an unknown type and choose Paste Rights to paste the rights of an NE or an object of an unknown type to another NE or another object of an unknown type. In the left navigation tree, right-click an NE and choose Copy Rights to. In the Copy Rights to Devices of the Same Type dialog box, select the device where you want to paste the rights, and then click OK. The rights of an NE are copied to other NEs of the same type.
----End
5.4.5 Assigning Rights of New NEs to an OM User Group

You can allocate new device rights to an OM user group by NE type. When an NE is added, the user group has all the rights of the NE type to the NE.
Context
The Administrators user group has all the rights. You cannot change rights of this group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node, Select the user group you want to set. Step 3 In the pane on the right, click the New Device Rights tab. Step 4 On the New Device Rights tab, click Add. Step 5 In the Add New Device Rights dialog box, select relevant rights, and then click OK. ----End
5.4.6 Granting MML Authority to an OM User Group

This describes how to assign the MML authority to an OM user group. This enables users in the same user group have the same MML authority.
Prerequisite
l l l l
You are authorized with the relevant privileges. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some MML commands of the specific NE types to an OM user or group. If the authority rule is successfully created, the OM user or OM user group automatically have the authority to the MML commands of all new NEs of this NE type.
NOTE
When you assign MML command authority to OM user groups, the M2000 does not display the defined rules of NE type authority. The MML command authority of a user group is the union of the NE MML command authority and NE type authority rule. After you assign NE MML command authority to an OM user group and then issue NE type authority rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority of the user group is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to Setting Authority Rules for NE Types and Issuing Authority Rules for NE Types.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group in the User Group node from the navigation tree. Click the Binded NE tab in the right pane. Step 3 Click Bind NE. Step 4 In the Bind NE dialog box, choose a user group, an NE type, and a command group. Click OK or Apply to assign the MML authority to an OM user group.

l l
Click OK to save the settings and close the dialog box. Click Apply to save the setting, but the dialog box is not closed. You can continue to assign the MML authority to other user groups.
----End
5.4.7 Creating an OM User Account

You can create the OM user accounts in the M2000 so that multiple OM users can operate and manage the M2000.
Context
l l
When the default account policy is used, the user name must contain from 6 to 32 characters. You can modify the minimum length of the user name by setting the account policy.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, right-click the User node and choose New User. Step 3 In the New User dialog box, on the Detail tab, set Name, Description, and Password. Step 4 Optional: If you want to add the user to a user group, in the New User dialog box, click the User Groups tab. Select the user group to which you want to add the user. Step 5 Optional: If you want to set the managed domain for the user, in the New User dialog box, click the Domain tab. Set the objects that are managed by the user. Step 6 Optional: If you want to set operation rights for the user, in the New User dialog box, click the Operation Rights tab. Set operation rights for the user. Step 7 Optional: If you want to set the ACL for the user, in the New User dialog box, click the Access Control List tab. Set the ACL for the user. Step 8 Click OK. ----End
5.4.8 Synchronize OM user data

This describes how to synchronize the OM user data. The synchronization of OM user data synchronizes the data on the M2000 with that of the associated NE. If the M2000 is disconnected from the NE, the data cannot be synchronized with that of the NE when you set the NE authority on the M2000. When the M2000 is reconnected to the NE, synchronize the data on the M2000 with that of the NE.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select a user under the User node on the navigation tree. Right-click the node and select Synchronize User Data, or click Synchronize User Data in the NE tab.

NOTE
If the selected user does not have the NEs to which they are bound, the NEs cannot be synchronized.
Step 3 Select the NEs to be synchronized in the Synchronize User Data dialog box. Click Start to synchronize the OM user data with that of the NEs. The Synchronize User Data dialog box displays the progress of synchronizing OM user data to the NEs. Step 4 Click Close. The Synchronize User Data dialog box is closed. ----End
5.4.9 Adding an OM User to a User Group

You can add the OM users to user groups. These users can be managed in a centralized manner and you can assign rights to the users in this way.
Context
You cannot add the Administrator user to a user group.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the User Groups tab. Step 4 On the User Groups tab, click Add. Step 5 In the Add User Group dialog box, select the user group to which you want to add the user. Click OK. ----End
5.4.10 Assigning Operation Rights to an OM User

This section describes how to assign operation rights to an OM user.
Context
l l
You cannot set the operation rights of the admin user. When you set the operation rights for a user, the M2000 does not display the rights of the user group to which the user belongs. The final rights of the user are the combination of rights assigned to the user and the user group to which the user belongs.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set.
Step 3 From the pane on the right, click the Operation Rights tab. Step 4 On the Operation Rights tab, click Add. Step 5 In the Add Operation Rights dialog box, select the type of operation rights and the corresponding rights. Click OK.
NOTE
If the selected type of operation rights is Network Device, then

l l l
You need to add the device to the managed domain of the user group before you set the operation rights to the device. Select the device in the left navigation tree, and select the operation rights to the device in the list on the right to add the operation rights. In the left navigation tree, right-click an NE or an object of an unknown type and choose Copy Rights. Then in the right navigation tree, right-click another NE or another object of an unknown type and choose Paste Rights to paste the rights of an NE or an object of an unknown type to another NE or another object of an unknown type. In the left navigation tree, right-click an NE and choose Copy Rights to. In the Copy Rights to Devices of the Same Type dialog box, select the device where you want to paste the rights, and then click OK. The rights of an NE are copied to other NEs of the same type.
Step 6 Optional: Select Show access from user group. The operation rights of the user group are displayed in gray in the operation rights list. ----End
5.4.11 Setting the Managed Domain for an OM User

You can set the managed domain for an OM user to allocate the managed objects to the user.
Context
l l
You cannot set the managed domain for the admin user. When you set the management domain for a user, the M2000 does not display the management domain of the user group to which the user belongs. The final management domain of the user is the union of the assigned management domain and the management domain of the user group to which the user belongs.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Domain tab. Step 4 On the Domain tab, click Add. Step 5 In the navigation tree of the Add Domain dialog box, select the managed objects, and then click OK. ----End
5.4.12 Setting the User ACL

You can set the ACL to allow the users to log in to the M2000 through the clients of only the specific IP addresses or network segment.
Context
l l
To set the user ACL, you must have the User Management right. The system ACL allows all the OM users to log in to the M2000 through the clients of only the specific IP addresses or network segment. The user ACL is a subset of the system ACL. The user ACL is effective for only the current user.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Access Control List tab. Step 4 On the Access Control List tab, do as follows: l l Select Use the system Access Control List. Select Use the current user Access Control List. Then select the IP addresses or network segment through which the users can log in to the server.
Step 5 Click Apply. ----End
5.4.13 Grant MML authority to an OM user

This describes how to grant the MML authority to a specified OM user. The user can run all the commands in the command group to NEs. After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs.
Prerequisite
l l
You have logged in to the M2000 client. Relevant NEs are properly connected to the M2000.
Context
To reduce work effort, you can set the rule for NE type authority to grant the authority of some MML commands of the specific NE types to an OM user or group. If the authority rule is successfully created, the OM user or OM user group automatically have the authority to the MML commands of all new NEs of this NE type.
Issue 05 (2008-05-20)
5-25

NOTE
When you assign MML command authority to OM users, the M2000 does not display the defined rules of NE type authority. The MML command authority of a user is the union of the NE MML command authority and NE type authority rule. After you assign NE MML command authority to an OM user group and then issue NE type authority rule to this NE, the NE MML command authority is invalid. In this case, the MML command authority of the user is the NE type authority rule.
For details about how to set and issue NE type authority rules, refer to Setting Authority Rules for NE Types and Issuing Authority Rules for NE Types.
Procedure
l Start the setting from the Security Management window. 1. 2. 3. 4. l 1. 2. Choose Security > Security Management . The Security Management window is displayed. Choose a user in the User node from the navigation tree. Right-click the user and choose Bind NE. You can also click Bind NE on the NE tab page in the right pane. In the displayed Bind NE dialog box, choose the command group to be assigned and NEs. Click OK to assign the MML authority to an OM user. Choose Security > NE User Management. The NE User Management window is displayed. Open the Bind Command Group window. You can choose either of the following two methods:
Start the setting from the NE User Management window.
Select a specific NE node from the navigation tree. Right-click the node and choose Bind Command Group. You can also click Bind Command Group on the NE tab page in the right pane. Select an NE user node from the navigation tree. Right-click the node and choose Bind Command Group. You can also click Bind Command Group on the Command Group tab page in the right pane.
3. 4. ----End
In the displayed Bind Command Group dialog box, choose the command group to be assigned and OM user. Click OK to assign the MML authority to an OM user.
Postrequisite
After the OM user obtains the MML authority, the user becomes a nonlocal user of the NEs. You can choose Security > NE User Management and choose the NE user that maps to the OM user from the navigation tree. Click the Command Group tab to view the information about the assigned MML commands.
5.5 Modifying an OM User

This describes how to modify an existing OM user. For an existing OM user, you can modify the user's authority, basic information, and password.
5-26
Issue 05 (2008-05-20)
5.5.1 Viewing the Details of an OM User This describes how to view the information about an OM user. In this way, you can familiarize yourself with the following items: the fundamental information about an OM user, the user group to which the OM user belongs, management domain, operation rights, access control list, MML command authorization of the managed NEs, and the authorization rule. 5.5.2 Modifying the Authority to an OM User This describes the public authority to an OM user. That is, the authority to the user group. Through the M2000 client, you can modify the management domain of the OM user group, operation authority, authority to new devices, and MML authority. The modification to the public authority to the OM user is applicable to all the OM users in the user group. 5.5.3 Modifying the Authority to an OM User This describes how to modify the private authority to an OM user. Through the M2000 client, you can modify the user group to which the OM user belongs, operation authority, access control list, and MML authority. The modification to the authority to the OM user is applicable only to the OM user. 5.5.4 Modifying the Information of an OM User This section describes how to change the information on the OM user description, user validity, and login period. 5.5.5 Modifying the Password of an OM User This section describes how to modify the password of an OM user.
5.5.1 Viewing the Details of an OM User

This describes how to view the information about an OM user. In this way, you can familiarize yourself with the following items: the fundamental information about an OM user, the user group to which the OM user belongs, management domain, operation rights, access control list, MML command authorization of the managed NEs, and the authorization rule.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select an OM user node under the User node on the navigation tree. Check the information about the OM user in each tab of the right window.
l
The Detail tab: displays the fundamental information about the OM user, such as user name, login time, and time for modifying the password. The User Groups tab: displays the user group to which the OM user belongs. The Domain tab: displays the managed objects of the OM user. The Operation Rights tab: displays the operation rights of the OM user. The Access Control List tab: displays the IP addresses on the client from which the OM user can log in to the M2000. The Bind NE tab: displays the MML command authorization that the OM user owns. The Rules tab: displays the authorization rule of the NE type set by the OM user.
l l l l
l l
----End
5.5.2 Modifying the Authority to an OM User

This describes the public authority to an OM user. That is, the authority to the user group. Through the M2000 client, you can modify the management domain of the OM user group,
operation authority, authority to new devices, and MML authority. The modification to the public authority to the OM user is applicable to all the OM users in the user group. 5.5.2.1 Modifying the Management Domain of an OM User Group This describes how to assign and delete management objects by modifying management domain. 5.5.2.2 Modifying the Operation Rights of an OM User Group This describes how to distribute or delete the operation rights of an OM user group by adjusting the operation rights of the OM group. 5.5.2.3 Modifying the Authority to the New Devices in an OM User Group This describes the authority to new devices. The authority is granted according to the type of NE devices. After the authority is granted, the system automatically grants the authority to users if new devices of the defined types are added. 5.5.2.4 Modifying the MML Authority to An OM User Group This describes the MML authority to the users in the same user group. By modifying the MML authority to an OM user group, you can modify the MML authority to the users in the same user group.
Modifying the Management Domain of an OM User Group

This describes how to assign and delete management objects by modifying management domain.
Prerequisite
l l
You have logged in to the M2000 client. You have the management authorization of the user group.
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators have all the authorities. You are not allowed to modify the management domain of this user. You can modify the management domain of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group whose management domain is to be modified under the User Group node from the navigation tree. Click Domain in the right pane. The objects managed by a user group are listed as a navigation tree on the Domain tab page. Step 3 Modify the management domain of an OM user. Modify the management domain of an OM user Add a management object Then...
1. Click Add or right-click and choose Add. 2. In the displayed Add Domain dialog box, choose a management object to be added. 3. Click OK.
5-28
Issue 05 (2008-05-20)
Modify the management domain of an OM user Delete a management object
Then...
1. In the navigation tree on the Domain tab page, choose the management object to be deleted. 2. Click Delete or right-click and choose Delete. 3. In the displayed Confirm dialog box, click Yes.
----End
Modifying the Operation Rights of an OM User Group

This describes how to distribute or delete the operation rights of an OM user group by adjusting the operation rights of the OM group.
Prerequisite
l l
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. Administrators have all the rights. You cannot modify the operation rights of this user group. You can, however, modify the operation rights of Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Select the user group for the adjustment under the User Group in the navigation tree. Click Operation Rights at the right window. In the Operation Rights tab, the operation rights owned by the user group are listed in table. Step 3 Adjust the operation rights of the OM user group. Adjust the operation rights of the OM Procedure user group. Add the operation rights. 1. Click Add or right-click and choose Add. 2. In the displayed Add Operation Rights window, select the type of the operation rights and the corresponding rights. 3. Click OK.
Issue 05 (2008-05-20)
5-29
Adjust the operation rights of the OM Procedure user group. Delete the operation rights. 1. In the list of the operation rights, select the unnecessary operation rights. Then, click Delete, or right-click the list and select Delete. 2. Click Yes in the displayed Confirm dialog box. ----End
Modifying the Authority to the New Devices in an OM User Group

This describes the authority to new devices. The authority is granted according to the type of NE devices. After the authority is granted, the system automatically grants the authority to users if new devices of the defined types are added.
Prerequisite
l l
Context
The M2000 provides three default user groups: Guests, Operators, and Administrators. The Administrators group has all the operation rights. You cannot change the rights of this group. You can change the rights of the Guests and Operators.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user group to whom the authority to new devices is to be modified under the User Group node from the navigation tree. Click New Device Rights in the right pane. The authority to new devices in the user group is displayed in table format on the New Device Rights tab page. Step 3 Modify the authority to new devices in the user group Modify the authority to new devices in Procedure the user group Add authority to new devices 1. Click Add or right-click and choose Add. 2. In the displayed Add New Device Rights dialog box, choose the authority to be added. 3. Click OK.
5-30
Issue 05 (2008-05-20)
Modify the authority to new devices in Procedure the user group Delete authority to new devices 1. Choose the authority to be deleted from the New Device Rights list. 2. Click Delete or right-click and choose Delete. 3. In the displayed Confirm dialog box, click Yes. ----End
Modifying the MML Authority to An OM User Group

This describes the MML authority to the users in the same user group. By modifying the MML authority to an OM user group, you can modify the MML authority to the users in the same user group.
Prerequisite
l l l l
You have the management authorization of the user group. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user group to whom the MML authority is to be modified from the User Group node in the navigation tree, right-click the user group and choose Bind NE from the shortcut menu. You can also click Bind NE on the Bind NE tab page. Step 3 In the displayed Bind NE dialog box, choose the NE type and command group. Step 4 Click OK or Apply. ----End
5.5.3 Modifying the Authority to an OM User

This describes how to modify the private authority to an OM user. Through the M2000 client, you can modify the user group to which the OM user belongs, operation authority, access control list, and MML authority. The modification to the authority to the OM user is applicable only to the OM user. 5.5.3.1 Adjust the user group to which the OM user belongs. This describes how adjust the user group on which an OM user belongs to. In this way, the OM user has the authority to the user groups to which the OM user belongs. 5.5.3.2 Modifying the Operation Rights of an OM User
This describes how to modify the operation rights of an OM user. You can assign or delete relevant authority to an OM user. 5.5.3.3 Modifying the OM Access Control List You can modify the OM access control list to modify the IP addresses of the clients through which the users can log in to the M2000 server. 5.5.3.4 Modifying the MML Authority to an OM User This describes the MML authority to an OM user. That is, the MML commands that the OM user runs on NEs. By modifying the MML authority to an OM user, you can modify the MML authority to the NEs of the user.
Adjust the user group to which the OM user belongs.

This describes how adjust the user group on which an OM user belongs to. In this way, the OM user has the authority to the user groups to which the OM user belongs.
Prerequisite
l l
You have logged in to the M2000 client. You have the authority to manager users.
Context
User admin has all the authority. You are not allowed to change the authority of this user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose a specific user in the User node from the navigation tree. Click the User Groups tab in the right pane. Step 3 Adjust the user group to which the OM user belongs according to actual requirements. Adjust the user group to which the OM user belongs. Procedure
Delete the OM user from a user group. 1. Choose a user group that needs not be bound to the OM user from the list, and click Delete. Alternatively, right-click it and choose Delete on the shortcut menu. 2. In the displayed Confirm dialog box, click Yes. Add the OM user to a user group. 1. Click Add or right-click and choose Add. 2. Choose a user group in the displayed Add User Group dialog box. 3. Click OK. ----End
Modifying the Operation Rights of an OM User

This describes how to modify the operation rights of an OM user. You can assign or delete relevant authority to an OM user.
Prerequisite
l l
You have logged in to the M2000 client. You have the authority to manager users.
Context
User admin have all the authority. You are not allowed to change the operation authority of this user.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user under the User node from the navigation tree. Click the Operation Rights tab in the right pane.
l
The operation rights that an OM user directly obtains is listed on the Operation Rights tab page in table format. Select Show access from user group. The operation rights of the user group are displayed in the operation rights list.
Step 3 Adjust the operation rights of an OM user Adjust the operation rights of an OM Procedure user Add the operation rights. 1. Click Add or right-click and choose Add. 2. In the displayed Add Operation Rights window, select the type of the operation rights and the corresponding rights. 3. Click OK. Delete the operation rights. 1. In the list of the operation rights, select the unnecessary operation rights. Then, click Delete, or right-click the list and select Delete. 2. Click Yes in the displayed Confirm dialog box. ----End
Modifying the OM Access Control List

You can modify the OM access control list to modify the IP addresses of the clients through which the users can log in to the M2000 server.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user you want to set. Step 3 In the pane on the right, click the Access Control List tab. Step 4 On the Access Control List tab, do as follows: l l Select Use the system Access Control List. Select Use the current user Access Control List. Then select the IP addresses or network segment through which the users can log in to the server.
Step 5 Click Apply. ----End
Modifying the MML Authority to an OM User

This describes the MML authority to an OM user. That is, the MML commands that the OM user runs on NEs. By modifying the MML authority to an OM user, you can modify the MML authority to the NEs of the user.
Prerequisite
l l l l
You have the authority to manager users. NEs communicate normally with the M2000. NEs support binding. You are familiar with the policy of authority assignment of the M2000.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Choose the specific user to whom the MML authority is to be modified from the User node in the navigation tree, right-click the user and choose Bind NE from the shortcut menu. You can also click Bind NE on the Bind NE tab page. Step 3 In the displayed Bind NE dialog box, choose the NE type and command group. Step 4 Click OK to modify the command group of the OM user. Select the OM user node from the navigation tree, and then right-click the node and choose Refresh NE & Access from the shortcut menu. You can view the modified MML authority on the Bind NE tab page. ----End
5.5.4 Modifying the Information of an OM User

This section describes how to change the information on the OM user description, user validity, and login period.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Select the user whose information you want to modify. Click the Detail tab from the pane on the right. Step 3 On the Detail tab, modify the parameters in Description, Enable/Disable user account, and Valid time. Step 4 Click Apply. ----End
5.5.5 Modifying the Password of an OM User

This section describes how to modify the password of an OM user.
Context
l
The minimum length of the user password can be set in the password policy. By default, the length of the common user's password is 7. The value ranges from 7 to 16. The length of the admin's password ranges from 8 to 16. The user admin can reset the password of any user. The users in the Administrators group can reset the passwords of the users that are in other groups. If the users that are not in the Administrators group have the Reset Password right, they can reset the passwords of the users that are not in the Administrators group. If the users that are not in the Administrators group do not have the Reset Password right, they can reset only their own passwords.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Right-click the user whose password you want to change, and then choose Reset Password.
NOTE
In the Security Management window, you can choose Security > Change Password to change the password of the current login user.
Step 3 In the Reset Password dialog box, set New Password and Confirm Password. Step 4 Click OK. Step 5 In the Confirm dialog box, click OK. ----End
5.6 Deleting an OM User Group

This describes how to delete an OM user group. You can delete an unwanted OM user group based on the requirements to save the system resource. The deletion of an OM user group indicates that only the authority of the OM user for the associated command groups is deleted. After the deletion, the OM user still exists without belonging to any user group.
Context
NOTE
If an user in the OM user group has logged in to the server, the user group cannot be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Click the User Group node on the navigation tree. Delete a user group using the following two methods:
l l
Right-click a user group under User Group and choose Delete. Choose the user group to be deleted in the right pane, and then click Delete or right-click the user group and choose Delete to delete the user group.
Step 3 In the displayed Confirmation dialog box, click Yes to delete the selected OM user. After the deletion, the users on the M2000 can be regrouped and have new authority. ----End
5.7 Deleting an OM User

This describes how to delete an OM user. Based on the requirements, you can delete an unneeded OM user to save the system resource. If an OM user already has the binding relationship with an NE, the user bound to the NE is also deleted when you delete an OM user. In this way, the information on the OM user is removed from the M2000.
Context
NOTE
The admin users and active users are not allowed to be deleted.
Procedure
Step 1 Choose Security > Security Management . The Security Management window is displayed. Step 2 Remove an OM user You can choose either of the following two methods:
l
Click a specific user under the User node in the navigation tree, right-click the user, and then choose Delete. Choose the User node in the navigation tree. Choose the OM user to be deleted in the right pane and click Delete or right-click the user and choose Delete.
Step 3 In the displayed Confirmation dialog box, click Yes. ----End
5.8 Querying Authorization

You can query the authorization of the NEs and the M2000 rights in the M2000.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management window, click navigation tree. on the top of the Security Management
Step 3 In the Authorization Details dialog box, in the Topology Root navigation tree, select the name of a device . Then select rights from the rights navigation tree. The table on the right of the Authorization Details dialog box displays the users and user groups to which the right is assigned. ----End
5.9 Comparing the OM User Rights

You can compare the rights of two users in the M2000.
Procedure
Step 1 In the Security Management window, click navigation tree. on the top of the Security Management
Step 2 In the Select User for Compare dialog box, select two users. Step 3 Click OK. The comparison result is displayed in the Compare User Rights Result dialog box. ----End
5.10 Managing NE Users

This describes NE users. NE uses can log in to NEs through the LMT and operate and maintain NEs. When NEs are disconnected from M2000 or are not connected to the M2000, you can maintain and operate NEs through NE users.
Context
For difference between users of category A and category B/C NEs, refer to 5.1.3 NE User. 5.10.1 Creating an NE User This describes how to operate and maintain NEs when they are disconnected from the M2000 or M2000. You can create an NE user, and then log in to the LMT as the NE user. In this way, you can operate and maintain NEs. 5.10.2 Deleting an NE User This describes how to delete unwanted NE users. After you delete an NE user, the binding relationship between an OM user and NE is also deleted. 5.10.3 Changing the Password of an NE User This section describes how to change the password of an NE user. 5.10.4 Associating OM User with NE User
This describes how to associate an OM user with an NE user. In this way, the OM user is provided with the authority of the NE user. 5.10.5 Disassociating OM User with NE User This describes how to delete the association between an OM user and a category B/C NE user. In this way, the OM user does not have the authorities of the NE user.
5.10.1 Creating an NE User

This describes how to operate and maintain NEs when they are disconnected from the M2000 or M2000. You can create an NE user, and then log in to the LMT as the NE user. In this way, you can operate and maintain NEs.
Prerequisite
Before you create a user of category B/C NEs, you need to create an NE local user on NE side.
Context
For difference between users of category A and category B/C NEs, refer to 5.1.3 NE User.
Procedure
l Create a user of category A NEs 1. 2. l Create an OM user on the M2000 side. For details, see 5.4.7 Creating an OM User Account. Assign the authority of the MML commands to an OM user For details, see 5.4.13 Grant MML authority to an OM user. Create a user of category B/C NEs 1. 2. Choose Security > NE User Management, the NE User Management window is displayed. Select a specific category B/C NE node from the navigation tree, and then right-click the node and choose New NE User from the shortcut menu. Or you can click New NE User in the right pane. You can also right-click on the right pane and choose New NE User. Set user information in the displayed New NE User dialog box.
NOTE
3.
The information about the new NE user and NE local user is separate from each other. The system cannot synchronize the information about the two user accounts. You need to manually synchronize the information about the NE user on the M2000 and the local user in the NEs.
4. ----End
Click OK.
5.10.2 Deleting an NE User

This describes how to delete unwanted NE users. After you delete an NE user, the binding relationship between an OM user and NE is also deleted.
5-38
Issue 05 (2008-05-20)
Context
NOTE
If you delete a category A NE user, the binding relationship between an OM user and NE is deleted. The OM user exists.
For difference between category A and category B/C NEs, refer to 5.1.3 NE User.
Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is displayed. Step 2 Delete an NE user. Type of NE Users Category A NE user Procedure Mode one: 1. Select the user node to be deleted from the navigation tree, and then right-click the node and choose Delete. 2. In the displayed Confirm dialog box, click Yes. Mode two: 1. Choose Security > Security Management . The Security Management window is displayed. 2. Select the node that maps to the OM user. Right-click the node and choose Bind NE. You can also click Bind NE on the NE tab page in the right pane. 3. To cancel the binding relationship between the user and NE, and the relationship between the user and command group, click OK. User of category B/C NEs Mode one: 1. Choose the user node to be deleted from the navigation tree, right-click and choose Delete NE User. 2. Click Yes in the displayed Confirm dialog box. Mode two: 1. Choose the NE node to which the NE user to be deleted belongs to from the navigation tree. Choose the NE user to be deleted in the right pane. Click Delete NE User or right-click and choose Delete NE User. 2. In the displayed Confirm dialog box, click Yes. ----End
5.10.3 Changing the Password of an NE User

This section describes how to change the password of an NE user.
Issue 05 (2008-05-20)
5-39
Context
For detailed description of category A NE users and category B/C NE users, refer to 5.1.3 NE User. For detailed description of category A/B/C NEs, refer to NE Types.
Procedure
l Change the password of the category A NE user. For a category A NE, the corresponding OM user becomes an NE user after you grant the user the related NE authority. Therefore, you can modify a category NE user by changing the password of the corresponding OM user password. For details, see Modifying the Password of an OM User. l Change the password of the category B/C NE user. 1. 2. Choose Security > NE User Management. In the NE User Management window, in the NE User Management navigation tree, expand the NE type node. Click the NE user whose password you want to change, and then choose Change Password . In the Change Password dialog box, select Effect Range. Enter the value of Old Password. Set New Password and Confirm Password.
NOTE
3.
l l
When Modify the NMS password only is selected for Effect Range, Old Password is input by the system automatically. If you select Modify the NMS password only, it indicates to modify only the password that the NE user uses to log in to the M2000.
4. 5. ----End
Click OK. In the Confirm dialog box, click OK.
5.10.4 Associating OM User with NE User

This describes how to associate an OM user with an NE user. In this way, the OM user is provided with the authority of the NE user.
Context
For differences between users of category A and category B/C NEs, refer to 5.1.3 NE User.
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed. Step 2 Choose the OM user to be associated with the NE user from the navigation tree, right click the user and choose Associate NE User. Or you can click Associate NE User in the right pane. You can also right-click on the right pane and choose Associate NE User. Step 3 Choose the NEs to be associated with the OM user from the navigation tree. Choose the NE user to be associated in the table in the right pane. Click Set Association.
l
All category B/C NEs on the M2000 are displayed in the navigation tree in the dialog box. The selected NE users are displayed in the table in the right pane. For the same NE, one OM user can bind only one NE user.
5-40

l
One OM user can be bound to a maximum of 255 NE users.
5.10.5 Disassociating OM User with NE User

This describes how to delete the association between an OM user and a category B/C NE user. In this way, the OM user does not have the authorities of the NE user.
Prerequisite
The OM user associates with the category B/C NE user.
Context
For difference between users of category A and category B/C NEs, refer to 5.1.3 NE User.
Procedure
Step 1 Choose Security > NE Login Management, the NE Login Management window is displayed. Step 2 Choose the OM user whose association is to be deleted from the navigation tree. Choose one or more associated NE users in the right pane. Step 3 Click Delete Association, or right-click the menu and choose Delete Association . Step 4 In the displayed Confirm dialog box, click Yes. ----End
5.11 Monitoring OM Users

This describes how to monitor an OM user. The M2000 offers the user-monitoring function to monitor users' login and operations. This prevents illegal users from attacking the system. 5.11.1 User Operation Logs User operation logs records the operations of the users. By analyzing user operation logs, you get to know the operations performed by users and easily locate the users. 5.11.2 User Sessions When a user logs in to the M2000 through the M2000 client or through the LMT of an NE, the M2000 or the NE establishes a user session to record the login information. 5.11.3 Viewing Operation of OM Users on the M2000 You can monitor the OM user sessions and operations, to prevent illegal user operations. 5.11.4 Viewing Operation of NE Users This describes how to monitor the sessions and operations of the NE users on the LMT. In this way, you can familiarize yourself with whether the local NE user logs in to the LMT. To prevent dangerous operations and to ensure the system security, you can force the user to exit the LMT. 5.11.5 Setting the Status of Special NE User This describes how to set the status of the special NE user. The status of the non-default NE user includes two types, namely, whether the user can log in to the LMT. By setting the status, the
non-default user's login and operation of the MML commands on the LMT can be controlled. The non-default users are the local NE users except user admin and guest. 5.11.6 Forcing an OM User to Exit from the M2000 You can force an OM user to exit if the user performs dangerous operations or initiates illegal sessions. 5.11.7 Forcing an NE User to Exit from the LMT This describes how to force an NE user to log out the LMT. When an NE user performs dangerous operations and illegal session, you can force the user to exit from the LMT. 5.11.8 Unlocking an OM User If the number of the times that a user enters an incorrect password reaches the number of the preset login attempts, the user is locked. This section describes how to unlock an OM user. 5.11.9 Setting OM User Auto-Locking When an OM user logs in to the M2000 client, the system locks the interface if the number of wrong passwords exceed the maximum attempts, thus protecting the system from authorized operations.
5.11.1 User Operation Logs

User operation logs records the operations of the users. By analyzing user operation logs, you get to know the operations performed by users and easily locate the users. User operation logs falls into two categories: NM user operation logs and NE user operation logs. NM user operation logs records the information on the operations performed on the M2000 by OM users. NE user operation logs records the information on the operations performed by NE users.
5.11.2 User Sessions

When a user logs in to the M2000 through the M2000 client or through the LMT of an NE, the M2000 or the NE establishes a user session to record the login information. A user session records the following information: login time, user group to which the user belongs, the terminal to which the user logs in, and the current status. You get to know what users have logged in to the system by monitoring the user session information. To ensure the security of the system, you can also force some users to exit from the system.
5.11.3 Viewing Operation of OM Users on the M2000

You can monitor the OM user sessions and operations, to prevent illegal user operations.
Context
l l
The session is the connection between the M2000 client and the M2000 server. If a monitored user performs operations, the information in the operation monitoring list is updated in real time. After the M2000 server is restarted or the network is recovered after interruption, you need to click Refresh to refresh the session monitoring list.
5-42
Procedure
Step 1 Choose Security > User Monitor. The Session Monitoring area box in the User Monitoring window displays the session information about users. The information contains the user name, session status, login time, login terminal, and user group to which the user belongs.
NOTE
When the machine of the client uses multiple network cards, the value of Login Terminal can be randomly selected from the IP addresses.
Step 2 Select a user name from the list of session users. The Operation Monitoring area box displays the operations selected by users.
NOTE
The operation monitoring list displays only the operations after the User Monitoring window is activated.
Step 3 Click Filter at the bottom of the operation monitoring list. Step 4 In the Filter dialog box, set Operation and Operation Object, and then click OK. The user operations that match the preset conditions are displayed in the operation monitoring list. ----End
5.11.4 Viewing Operation of NE Users

This describes how to monitor the sessions and operations of the NE users on the LMT. In this way, you can familiarize yourself with whether the local NE user logs in to the LMT. To prevent dangerous operations and to ensure the system security, you can force the user to exit the LMT.
Context
l l
This function supports only A NEs. B/C NEs are not supported. Only the users logging in to the LMTs (the LMT started through the M2000 and the independently started LMT) are monitored. For the virtual NEs, the maintenance and monitoring function is not provided. If a monitored user performs operations, the information in the operation monitoring list is updated in real time. After the M2000 server is restarted or the network is recovered after interruption, you need to click Refresh to refresh the session monitoring list.
Procedure
Step 1 Choose Security > User Monitor. The User Monitor window is displayed. Step 2 Select the Local Maintenance Monitor tab, and then click Subscribe. Step 3 In the displayed Subscribed NE List, select the NEs for the monitoring. Click OK.
NOTE
After you subscribe the NEs, the sessions and operations of the user on the LMT are displayed in the Local Maintenance Monitor tab.
Step 4 Select a session record in the user session list.

The user operation list displays all the operations of the selected user. Step 5 Click Filter to set the filtering conditions. Only the session information that meets the requirements are displayed in the user session list. ----End
5.11.5 Setting the Status of Special NE User

This describes how to set the status of the special NE user. The status of the non-default NE user includes two types, namely, whether the user can log in to the LMT. By setting the status, the non-default user's login and operation of the MML commands on the LMT can be controlled. The non-default users are the local NE users except user admin and guest.
Prerequisite
l l
The user has the relevant operation rights. The M2000 is connected to the LMT normally.
Procedure
Step 1 Click Security > Local Users Setting. The Local Users Setting window is displayed. Step 2 Select an NE type under the NE Type node. All the NEs of this type are displayed at the right window. Step 3 Set the status of the non-default NE user.
l
If you select Managable, it indicates that the NE can be managed. That is, you can create, modify, or delete non-default NE users on the NEs. By default, the system selects Managable. If you select Whether inhibit login, it indicates that the login is inhibited. That is, regardless of login to the LMT directly or through the M2000, other local NE users except the admin and guest cannot log in to the LMT. By default, the system selects Whether inhibit login.
NOTE
You can select multiple NEs in the list. Right-click the list, select an option in the shortcut menu, and then the NEs are processed in batches.
----End
5.11.6 Forcing an OM User to Exit from the M2000

You can force an OM user to exit if the user performs dangerous operations or initiates illegal sessions.
Context
l
The system forces a user to exit only from the specific client in the session monitoring table. If the user has logged in to the M2000 from multiple clients (if possible), you need to repeat the operation to force the user to exit from all the clients. You cannot force your own user account to exit from the M2000.
5-44
Issue 05 (2008-05-20)
Procedure
Step 1 Choose Security > User Monitor. Step 2 From the session monitoring table, select a user name, and then click Force User to Exit. Step 3 In the Confirm dialog box, click Yes. ----End
5.11.7 Forcing an NE User to Exit from the LMT

This describes how to force an NE user to log out the LMT. When an NE user performs dangerous operations and illegal session, you can force the user to exit from the LMT.
Procedure
Step 1 Choose Security > User Monitor, the User Monitor window is displayed. Step 2 Click the Local Maintenance Monitor tab, and then choose the NE user in the NE session list. Step 3 Click Force User to Exit or right-click and choose Force User to Exit from the shortcut menu. Step 4 In the displayed Confirm dialog box, click Yes. ----End
5.11.8 Unlocking an OM User

If the number of the times that a user enters an incorrect password reaches the number of the preset login attempts, the user is locked. This section describes how to unlock an OM user.
Prerequisite
Only the users who have the right to unlock the user can perform this operation.
Context
You can set the maximum login attempts and auto unlock time in the account policy.
Procedure
Step 1 Choose Security > Security Management . Step 2 In the Security Management dialog box, expand the User root node. Right-click the user you want to unlock, and then choose Unlock User. ----End
5.11.9 Setting OM User Auto-Locking

When an OM user logs in to the M2000 client, the system locks the interface if the number of wrong passwords exceed the maximum attempts, thus protecting the system from authorized operations.
Procedure
Step 1 Choose Security > Security Policy. The Security Settings dialog box is displayed. Step 2 Click the Account Policy node in the navigation tree. Then, enter the number of attempts in the Maximum Login Attempts field and the automatic unlocking time in the Automatic Unlock TIme (Minute) field. By default:
l l
the value of Maximum Login Attempts is three. The value of Automatic Unlock TIme (Minute) is 30 minutes.
Step 3 Click Apply. The automatic locking of the OM user is set. ----End
5-46
Issue 05 (2008-05-20)
6 Monitoring the M2000
6
About This Chapter
Monitoring the M2000
This describes how to monitor the usage of the CPU, memory, disk, and database on the M2000 server, the running conditions of M2000 services. You can also monitor the operations of NM users and NE users, and the login status on the client. 6.1 Monitoring the M2000 on the M2000 Client This describes how to monitor the M2000 on the M2000 client. 6.2 Monitoring the M2000 on the M2000 Server This describes how to monitor the M2000 status on the M2000 server. The information monitored on the client covers more aspects than the information monitored on the server. 6.3 Monitoring the Login Status of Clients This describes how to monitor the login states of the clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the maximum number set for MaxSession, you must force a user out to establish a new connection.
Issue 05 (2008-05-20)
6-1
6.1 Monitoring the M2000 on the M2000 Client

This describes how to monitor the M2000 on the M2000 client. 6.1.1 Introduction to the M2000 System Monitor Browser On the M2000 client, you can view the status of the M2000 server using the M2000 system monitor browser. 6.1.2 Introduction to the M2000 System Log The system log records the operational status of the system. It helps you trace and identify problems. In addition, the system log is saved as files or tables. Thus, the M2000 administrator can query the system log with ease. 6.1.3 Viewing the CPU and Memory Usages of the M2000 Server This describes how to monitor the CPU usage, memory capacity, and free memory. When the CPU and memory of the server work improperly, you must log in to the server and rectify the existing fault. 6.1.4 Viewing the Disk Usage of the M2000 Server on the M2000 Client This describes how to view the disk usage of the M2000 server through the system monitor browser on the M2000 client. 6.1.5 Viewing the Database Usage of the M2000 Server on the M2000 Client This describes how to view the attributes of the database of the M2000 client, such as database name, server name, Solaris, database status, and free space of the database. 6.1.6 Viewing M2000 Services This describes how to view the M2000 services on the M2000 client. If the M2000 system services work improperly, you must log in to the system and rectify the existing fault. 6.1.7 Viewing the States of M2000 Processes This describes how to view the states of M2000 processes on the M2000 client. If the M2000 system processes work improperly, you must log in to the system and rectify the existing fault. 6.1.8 Setting Alarm Thresholds for the M2000 On the M2000 client, you can set the alarm threshold to monitor the server status. The monitoring of system status focuses on the system performance, disks, databases, and services. 6.1.9 Viewing M2000 Logs This describes how to view M2000 logs. Viewing M2000 logs occupies a few system resources and does not affect the system operation.
6.1.1 Introduction to the M2000 System Monitor Browser

On the M2000 client, you can view the status of the M2000 server using the M2000 system monitor browser. Choose Monitor > System Monitor > Monitor Browser to view the M2000 system monitor browser. The query items for the M2000 system monitor browser are as follows:
l
Performance Monitor the Solaris status, OS, memory capacity, CPU usage, and memory usage.
6-2
Issue 05 (2008-05-20)

l
Hard disk Monitor the status of the disks in the system, such as total capacity, used capacity, free capacity, and occupancy rate.
Database Monitor the status of the databases, such as database capacity, occupancy rate, and log capacity.
Service Monitor the service status, automatic restart times, and service start time. Process Monitor the number of used handles, CPU usage, memory usage, database connections, and threads.
NE Monitor alarm status and NE connections. For details, refer to the M2000 Operator Guide.
6.1.2 Introduction to the M2000 System Log

The system log records the operational status of the system. It helps you trace and identify problems. In addition, the system log is saved as files or tables. Thus, the M2000 administrator can query the system log with ease.
Save Path
System logs are saved in the following path on the M2000 server:
l
/export/home/omc/var/fileint/syslogs The save path of the system logs that are periodically exported is as follows: /export/home/omc/var/ThresholdExport/Log If the log data in the database exceeds a preset threshold, the system exports the log data to a specific path.
Contents
Table 6-1 describes the contents of the system logs. Table 6-1 Description of the system logs Contents Severity Meaning System logs can be categorized into the following three levels in descending order:
l l l
Error Warning Information
Issue 05 (2008-05-20)
6-3
Contents Source
Meaning Sources, such as FaultService, ServiceAdmin, and MediationService, are identified by the logos of the subsystems in the M2000 system. Provides the information on system operation, such as the information about service startup. Identifies the time when a system log is recorded. The date format is "Week/Month/ Day/Time/Timezone/Year", for example, Thu May 4 11:28:47 CST 2006.
Basic information
Time
6.1.3 Viewing the CPU and Memory Usages of the M2000 Server
This describes how to monitor the CPU usage, memory capacity, and free memory. When the CPU and memory of the server work improperly, you must log in to the server and rectify the existing fault.
Prerequisite
l l
You have logged in to the M2000 system. You are authorized to perform relevant operations.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Performance Monitor tab. The performance of the M2000 server is displayed. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV

NOTE
If the performance monitoring threshold is set for an item, the green icon of the item in the corresponding column turns to red when the value of the item exceeds the threshold.
----End
6-4
Issue 05 (2008-05-20)
6.1.4 Viewing the Disk Usage of the M2000 Server on the M2000 Client
This describes how to view the disk usage of the M2000 server through the system monitor browser on the M2000 client.
Prerequisite
l l
You have logged in to the M2000 system. You are authorized with the relevant operation privileges.
Context
This task uses very few system resources and does not affect the system operation.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Hard Disk Monitor tab. The disk usage of the M2000 server is displayed. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
6.1.5 Viewing the Database Usage of the M2000 Server on the M2000 Client
This describes how to view the attributes of the database of the M2000 client, such as database name, server name, Solaris, database status, and free space of the database.
Prerequisite
l l
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Database Monitor tab.
The database of the M2000 server is displayed. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
6.1.6 Viewing M2000 Services

This describes how to view the M2000 services on the M2000 client. If the M2000 system services work improperly, you must log in to the system and rectify the existing fault.
Prerequisite
l l
Context
This task consumes a few system resources and does not affect system performance.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Service Monitor tab to monitor the processes running on the M2000 server. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
6.1.7 Viewing the States of M2000 Processes

This describes how to view the states of M2000 processes on the M2000 client. If the M2000 system processes work improperly, you must log in to the system and rectify the existing fault.
Prerequisite
l l
6-6
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Process Monitor tab to monitor the processes running on the M2000 server. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following default formats:
l l l l
TXT HTML XML CSV
----End
6.1.8 Setting Alarm Thresholds for the M2000

On the M2000 client, you can set the alarm threshold to monitor the server status. The monitoring of system status focuses on the system performance, disks, databases, and services.
Prerequisite
l l
Context
The M2000 sets the threshold for certain items for system monitoring. When the value of an item exceeds the threshold, the relevant record in the System Monitor Browser window turns red and the M2000 generates the corresponding threshold alarm.
Procedure
Step 1 Choose Monitor > System Monitor > Settings . The System Monitor Settings window is displayed, as show in Figure 6-1.
Issue 05 (2008-05-20)
6-7
Figure 6-1 System monitor configurations
Step 2 Choose a property and set the value. Table 6-2 lists the recommended alarm thresholds for some monitored items. Table 6-2 Recommended alarm thresholds Item Performance monitoring Hard disk monitoring Database monitoring CPU usage ratio (%) Memory usage ratio (%) Hard disk usage ratio (%) Database usage ratio (%) Recommended Value 90 90 90 90
6.1.9 Viewing M2000 Logs

This describes how to view M2000 logs. Viewing M2000 logs occupies a few system resources and does not affect the system operation.
6-8
Issue 05 (2008-05-20)
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform relevant operations.
Procedure
Step 1 Choose System > Log Management > Query System Logs. The Filter Condition window is displayed. Step 2 Set filtering conditions for querying system logs in the Filter Condition window, and click OK. The Query System Log window is displayed. Step 3 Double-click a record and view the details of the record. In the displayed results, the Log Detailed window displays the details about a successful or failed operation. Step 4 Click Save As to save the System Log Records Table to a file. You can save the file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
6.2 Monitoring the M2000 on the M2000 Server

This describes how to monitor the M2000 status on the M2000 server. The information monitored on the client covers more aspects than the information monitored on the server. 6.2.1 Viewing Solaris Logs This describes how to view the Solaris logs. Viewing the Solaris error logs occupies few system resources and does not affect system operation. 6.2.2 Periodically Monitoring the CPU, Memory, and Disk The M2000 periodically exports the report of system performance, such as CPU usage, memory usage, and disk usage. Based on the report, you can analyze the load and performance of the hardware system. 6.2.3 Viewing the Database Usage of the M2000 Server Using Sybase Commands This describes how to view the database status of the M2000 server by using Sybase commands. This operation requires very few system resources and does not affect system operation. 6.2.4 Viewing the Disk Usage of the M2000 Server Using Solaris Commands This describes how to use Solaris commands for viewing the disk usage of the M2000 server. This task uses very few system resources and does not affect the system operation.
Issue 05 (2008-05-20)
6-9
6.2.1 Viewing Solaris Logs

This describes how to view the Solaris logs. Viewing the Solaris error logs occupies few system resources and does not affect system operation.
Prerequisite
Before checking error logs of the Solaris, ensure that you have logged in to the M2000 server as user omcuser.
Context
l
The /var/adm/messages file and the /var/log/syslog file record events in the following format:
Date and time of an event + server name + event description
Generally, the messages such as err or failed are not displayed. If such messages are displayed, contact your Huawei local office for technical support.
Procedure
Step 1 Open the /var/adm/messages file. -bash-3.00$ cd /var/adm -bash-3.00$ more messages Step 2 Check the file for error information. Step 3 Open the /var/log/syslog file. -bash-3.00$ cd /var/log -bash-3.00$ more syslog Step 4 Check the file for error information. ----End
6.2.2 Periodically Monitoring the CPU, Memory, and Disk

The M2000 periodically exports the report of system performance, such as CPU usage, memory usage, and disk usage. Based on the report, you can analyze the load and performance of the hardware system.
Prerequisite
Context
The 3-second period is used for sampling the CPU and the memory and the 1-minute period is used for monitoring disks. The difference between the monitoring of the clients and the monitoring of the server is that the monitoring on the client can export the usage of the CPU, memory, and disks only at certain time. The monitoring on the server, however, can export the periodically sampled usage of the CPU, memory, and disks.

l l
The performance report file records performance reports in the following format:
hostname hostname Total Size(KB) time CPU Occupancy(%) MEM Occupancy(%)
The disk usage report file records disk usage reports in the following format:
time Partition Name Used Size(KB) Avail Size(KB) used rate(%)
Procedure
Step 1 Switch to the default installation path of the M2000 server software. The default installation path of the M2000 server software is /opt/OMC. # cd /opt/OMC Step 2 Run the environment variant commands. # . ./svc_profile.sh Step 3 Enable the function of exporting reports. # svc_monitor -cmd start -type system or disk
l l
If you type system in the command, the system exports the performance report. If you type disk in the command, the system exports the report about disk usage.
The performance report is saved as a .txt file in M2000 server installation path/var/monitor/ sysinfo. The default file name is sysinfo-YYYYMMDDhhmmss. The disk usage report is saved as a .txt file in M2000 server installation path/var/monitor/diskinfo. The default file name is diskinfo-YYYYMMDDhhmmss. Step 4 Disable the function of exporting the report. # svc_monitor -cmd stop -type system or disk If you run the command successfully, the system displays set successfully. Otherwise, the system displays set failed.
NOTE
If you do not stop the system from exporting reports, the system continues to add monitoring records to the existing report file.
Step 5 View the exported reports.

l
View the performance report. # cd M2000 server installation path/var/monitor/sysinfo # more Performance Report File Check the report about disk usage. # cd M2000 server installation path/var/monitor/diskinfo # more Disk Usage Report File
----End
Issue 05 (2008-05-20)
6-11
6.2.3 Viewing the Database Usage of the M2000 Server Using Sybase Commands
This describes how to view the database status of the M2000 server by using Sybase commands. This operation requires very few system resources and does not affect system operation.
Prerequisite
l l
You have logged in to the M2000 server as user dbuser. The Sybase service is running.
Context
In addition to the method described in 6.1.5 Viewing the Database Usage of the M2000 Server on the M2000 Client, you can use the Sybase commands to view the disk usage of the M2000 server.
Procedure
Step 1 Check all the databases of the M2000 server. -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpdb 2> go
NOTE
Step 2 View the database usage and the event log space usage. 1> sp_helpdb M2000 database name 2> go To view the usage of the pmdb database, run the following command: 1> sp_helpdb pmdb 2> go
name db_size status owner dbid created
------------ ------------- ------ ------ ----------------------------------------------------------------------------------------------------------------------------------------pmdb 13000.0 MB sa 9 Mar 13, 2007 select into/bulkcopy/pllsort, trunc log on chkpt (1 row affected)
6-12
Issue 05 (2008-05-20)
device_fragments size usage created free kbytes ------------------------------ ------------- ------------------------------------------- ---------------data001_dev 10000.0 MB data only Mar 13 2007 6:37PM 10193312 log001_dev 3000.0 MB log only Mar 13 2007 6:37PM not applicable -------------------------------------------------------------------------------log only free kbytes = 3059992 (return status = 0)
As shown in the previous command result, the occupied space of the pmdb database is 13,000 MB, where 10,000 MB is used for storing performance data and 3,000 MB is used for storing the performance log data. Run the following command to exit: 1>exit For more information about the M2000 database, see 8.1 Introduction to M2000 Databases. ----End
6.2.4 Viewing the Disk Usage of the M2000 Server Using Solaris Commands
This describes how to use Solaris commands for viewing the disk usage of the M2000 server. This task uses very few system resources and does not affect the system operation.
Prerequisite
You have logged in to the server as user omcuser.
Procedure
Step 1 Run the following command: -bash-3.00$ df -k Step 2 View the disk usage. Normally, the disk usage is smaller than 90%, which means the value of capacity is smaller than 90% in the output. ----End
6.3 Monitoring the Login Status of Clients

This describes how to monitor the login states of the clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the maximum number set for MaxSession, you must force a user out to establish a new connection.
Prerequisite
Before monitoring the login status of clients, ensure that you are authorized to monitor the users.
Procedure
Step 1 Start the M2000 client and log in to the M2000. Step 2 Choose Security > User Monitor. The User Monitor dialog box is displayed. Step 3 Click the User Session Monitor tab to monitor all the terminals connected to the M2000 system. Pay close attention to the information about the IP addresses of monitored users and login time. Step 4 Click Refresh to refresh the session list. Step 5 This step is optional. If you need to force a user to exit, select the user, and then click Force User to Exit.
NOTE
The user of the selected client is forced out. The users of the other clients do not exit.
----End
6-14
Issue 05 (2008-05-20)
7 Managing M2000 Processes and Services
Managing M2000 Processes and Services
About This Chapter

This describes how to manage the M2000 processes and services. 7.1 Introduction to M2000 Processes and Services When the M2000 is running, the M2000 server automatically starts the processes related to the M2000 system. Each process provides different services and functions. 7.2 Managing M2000 Processes This describes how to query the running processes in the M2000 system and the operational status of the processes. 7.3 Managing M2000 Services This describes how to view, start, and stop M2000 system services.
Issue 05 (2008-05-20)
7-1
7.1 Introduction to M2000 Processes and Services

When the M2000 is running, the M2000 server automatically starts the processes related to the M2000 system. Each process provides different services and functions. 7.1.1 lic_agent Process This describes the services and functions provided by the process lic_agent. 7.1.2 em_agent Process This describes the services and functions provided by the em_agent process. 7.1.3 monitor_agent Process This describes the services and functions provided by the monitor_agent process. 7.1.4 partition_agent Process This describes the services and functions provided by the partition_agent process. 7.1.5 omcne_agent Process This describes the services and functions provided by the omcne agent process. 7.1.6 sm_agent Process This describes the services and functions provided by the process sm_agent. 7.1.7 med_agent Process This describes the services and functions provided by the med_agent process. 7.1.8 ifms_agent Process This describes the services and functions provided by the ifms_agent process. 7.1.9 manager_agent Process This describes the services and functions provided by the manager_agent process. 7.1.10 pm_agent Process This describes the services and functions provided by the process pm_agent. 7.1.11 cmserver_agent Process This describes the services and functions provided by the process cmserver_agent. 7.1.12 swm_agent Process This describes the services and functions provided by the swm_agent process. 7.1.13 fmnotify_agent Process This describes the services and functions provided by the fmnotify_agent process. 7.1.14 proxy_agent Process This describes the services and functions provided by the proxy_agent process. 7.1.15 notify_agent Process This describes the services and functions provided by the process notify_agent. 7.1.16 pmexp_agent Process This describes the services and functions provided by the process pmexp_agent. 7.1.17 irp_agent Process This describes the functions provided by the irp_agent process. 7.1.18 pmmon_agent Process This describes the services and functions provided by the process pmmon_agent.
7.1.19 tm_agent Process This describes the TopoService service, which is provided by the tm_agent process, and the dependent services. 7.1.20 snmp_agent Process This describes the SnmpAgent service and the dependent services. The SnmpAgent service is provided by the snmp_agent process. 7.1.21 nimserver_agent Process This describes the NIMServer service and the dependent service. NIMServer is provided by the nimserver_agent process. 7.1.22 neuser_agent Process This describes the NeUserService service. NeUserService is provided by the neuser_agent process. 7.1.23 log_agent Process This describes the LogService service and dependent services. LogService is provided by the log_agent process. 7.1.24 itmserver_agent Process This describes the ITMServer service and the dependent services. 7.1.25 fmexport_agent Process This describes the FaultExportService service and dependent services. 7.1.26 devdoc_agent Process This describes the DevDocService service provided by the devdoc_agent process. 7.1.27 cmdc_agent Process This describes the CmDcService service and dependent services. CmDcService is provided by the cmdc_agent process. 7.1.28 chr_agent Process This describes the CHRService service and the dependent service. CHRService is provided by the chr_agent process. 7.1.29 3rdTool_agent Process This describes the 3rdToolService service and dependent services. 7.1.30 am_agent Process This topic describes the function of the AMServer service, which is provided by the am_agent process. 7.1.31 threshold_agent Process This topic describes the function of the ThresholdService service provided by the threshold_agent process and the service that the threshold_agent process depends on. 7.1.32 objgrp_agent Process This topic describes the function of the ObjGrpService service provided by the objgrp_agent process and the service that the objgrp_agent process depends on. 7.1.33 nms_mml_agent Process This describes the services and functions provided by the process nms_mml_agent. 7.1.34 scriptserver_agent Process This describes the services and functions provided by the process scriptserver_agent. 7.1.35 mmlproxyserver_agent Process
This describes the function of the MMLProxyServer service, which is provided by the mmlproxyserver_agent process. 7.1.36 maintain_agent Process This topic describes the function of the MaintenanceService service, which is provided by the maintain_agent process. 7.1.40 udpdispatch_agent Process This describes the services and functions provided by the udpdispatch_agent process. 7.1.41 nelicense_agent Process This describes the services and functions provided by the nelicense_agent process. 7.1.42 nicserver_agent Process This describes the services and functions provided by the nicserver_agent process. 7.1.43 pmmedexp_agent Process This describes the services and functions provided by the pmmedexp_agent process. 7.1.44 cpm_agent Process This describes the services and functions provided by the cpm_agent process. 7.1.45 ce_agent Process This describes the services and functions provided by the ce_agent process. 7.1.46 imapds_agent Process This describes the services and functions provided by the imapds_agent process. 7.1.47 prssum_agent Process This describes the services and functions provided by the prssum_agent process. 7.1.48 prsreport_agent Process This describes the services and functions provided by the prsreport_agent process.
7.1.1 lic_agent Process

This describes the services and functions provided by the process lic_agent.
LicenseService
LicenseService provides a service interface to validate the license of the current version. Ensure that this service works properly during the M2000 operation. Dependent service: none
7.1.2 em_agent Process

This describes the services and functions provided by the em_agent process. The em_agent process provides the EventService service. EventService provides a mechanism to transmit messages between the M2000 services, and between the M2000 client and server. The EventService service also broadcasts and filters messages. Ensure that this service works properly during the M2000 operation. Dependent services: none.
7.1.3 monitor_agent Process

This describes the services and functions provided by the monitor_agent process. The monitor_agent process provides the MonitorService service. MonitorService monitors the status of system operation, such as CPU usage, memory usage, free disk space, and database operation. Ensure that this service works properly during the M2000 operation. Dependent services: EventService
7.1.4 partition_agent Process

This describes the services and functions provided by the partition_agent process. The partition_agent process provides the PartitionService service. The PartitionService service divides managed objects into various partitions. Each partition is managed by its own process. In the presence of a large quantity of objects, the partitions are managed by various processes on different servers to balance the load. Ensure that this service works properly during the M2000 operation. Dependent services: none.
7.1.5 omcne_agent Process

This describes the services and functions provided by the omcne agent process. The omcne_agent process provides the OMCNEService service. OMCNEService reports and stores the OMC alarms. Ensure that this service works properly during the M2000 operation. Dependent services: none
7.1.6 sm_agent Process

This describes the services and functions provided by the process sm_agent. The sm_agent process provides the SecurityService service. SecurityService controls the access of all sensitive resources in the M2000. Only authorized users can gain access to sensitive resources. Ensure that this service works properly during the M2000 operation. Dependent services: LogService and LicenseService
7.1.7 med_agent Process

This describes the services and functions provided by the med_agent process. The med_agent process provides the MediationService service. During the M2000 operation, the system dynamically generates new processes and services according to NE types and NE quantity. Processes are named med_agent1, med_agent2, and
med_agent3. Services are named MediationService1, MediationService2, and MediationService3. A maximum of 15 med_agents can coexist in the system. These processes share the same function with med_agent. MediationService creates, deletes, and obtains NE engines that map NEs of various types to network devices of the M2000 system, and manages interceptors of the relevant events. The NEs communicate with the M2000 system by using the corresponding NE engines through various network management protocols. Ensure that this service works properly during the M2000 operation. Dependent service: EventService and PartitionService
7.1.8 ifms_agent Process

This describes the services and functions provided by the ifms_agent process. The ifms_agent process provides the FaultService service. FaultService collects the alarm data from NEs and saves the alarm data. In this way, you can query and analyze the data in subsequent operations. You can disable this service when fault management is not required. Dependent services: MediationService, SecurityService, and TopoService
7.1.9 manager_agent Process

This describes the services and functions provided by the manager_agent process. The manager_agent process provides the SystemService service. SystemService enables you to query the M2000 version information such as the version of the operating system, software version of the client, software version of the server, client software version matching the server software, and client upgrade information. Ensure that this service works properly during the M2000 operation. Dependent service: none
7.1.10 pm_agent Process

This describes the services and functions provided by the process pm_agent. The pm_agent process provides the PMService service. PMService monitors performance management on all NEs. The performance management is independent of NEs or objects. Stop PMService if the performance management function is not required. Dependent service: CMServer
7.1.11 cmserver_agent Process

This describes the services and functions provided by the process cmserver_agent. The cmserver_agent process provides the CMserver service. CMserver monitors configuration management on all NEs. Configuration management is independent of NEs or managed objects.
Ensure that this service works properly during the M2000 operation. Dependent service: TopoService
7.1.12 swm_agent Process

This describes the services and functions provided by the swm_agent process. The swm_agent process provides the SWMService service. SWMService manages the version, configuration data, and other files of some NEs. It provides the functions of upload, download, activation, and version fallback. Ensure that this service works properly during the M2000 operation. Dependent service: CMServer
7.1.13 fmnotify_agent Process

This describes the services and functions provided by the fmnotify_agent process. The fmnotify_agent process provides the FMNotify service. FMNotify forwards the alarm data from FaultManager to the network management system (NMS). Disable FMNotify when the real-time alarm forwarding function is not required. Dependent services: LicenseService and FaultService
7.1.14 proxy_agent Process

This describes the services and functions provided by the proxy_agent process. The proxy_agent process provides the Proxyserver service. Proxyserver enables the M2000 client to connect to NEs through the proxy server and to run applications of the NEs on the LMT . Stop Proxyserver when the proxy function is not required. Dependent service: CMServer
7.1.15 notify_agent Process

This describes the services and functions provided by the process notify_agent. The notify_agent process provides the RemoteNotifyService service. RemoteNotifyService implements the remote alarm notification function. Stop RemoteNotifyService when the remote alarm is not required. Dependent service: FaultService
7.1.16 pmexp_agent Process

This describes the services and functions provided by the process pmexp_agent. The pmexp_agent process provides the PMExport service.
PMExport exports performance data of a measurement unit from the database. PMExport is independent of NEs or managed objects. Stop PMExport when the function of exporting performance results is not required. Dependent service: LicenseService
7.1.17 irp_agent Process

This describes the functions provided by the irp_agent process.
EPIRP
The EPIRP is subject to the entry point object. The entry point object is the first object that the NMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent provides a reference of an entry point object to the Manager, and the Manager obtains the reference of this entry point object in some way, for example, from the stored file. If the interface for northbound network management is not required, disable the EPIRP. Basic IRP: None.
NotificationIRP
NotificationIRP is used for subscribing to notifications and encapsulating notification subscription. If the function of subscription through the interface of northbound network management is not required, disable the NotificationIRP. Basic IRP: EPIRP.
CSIRP
CSIRP provides an interface for link monitoring. The link monitoring enables you to supervise the status of links between the Manager and the Agent. In this way, the potential exceptions can be detected at the first time. If the function of monitoring through the interface of northbound network management is not required, disable the CSIRP. Basic IRP: EPIRP, and NotificationIRP.
KernelCMIRP
KernelCMIRP provides an interface for public configuration management. The public configuration management uses KernelCMIRP to carry out some common tasks during the configuration, such as sending configuration objects, or adding, removing and modifying notifications. If the function of public configuration management through the interface of northbound network management is not required, disable the kernelCMIRP. Basic IRP: EPIRP, and NotificationIRP.
BasicCMIRP
BasicCMIRP controls the configuration management. BasicCMIRP is used for querying, modifying, adding, or removing network resource objects. If the function of configuration
management through the interface of northband network management is not enabled, disable the BasicCMIRP. Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.
AlarmIRP
AlarmIRP is used for managing fault data. If the function of fault data management through the interface of northbound network management is not required, disable the AlarmIRP. Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.
7.1.18 pmmon_agent Process

This describes the services and functions provided by the process pmmon_agent. The pmmon_agent process provides the PMMonService service. PMMonService monitors key NE counters and displays the value about these counters in figures and tables. Dependent service: PMService
7.1.19 tm_agent Process

This describes the TopoService service, which is provided by the tm_agent process, and the dependent services. The tm_agent process provides the TopoService service. The TopoService service maintains the relations between objects in subnets. That is, the TopoService service models topology elements and maintain the relations between elements. The TopoService service also enables you to create and delete subnets, nodes, and links. The TopoService service must be functional during M2000 operation. Dependent services: LogService, EventService, ScheduleService, and SecurityService
7.1.20 snmp_agent Process

This describes the SnmpAgent service and the dependent services. The SnmpAgent service is provided by the snmp_agent process. The snmp_agent process provides the SnmpAgent service, that is, the northbound interface service complying with the SNMP protocol. The SnmpAgent service enables the upper-level NMS to obtain the information on the M2000 such as alarm and performance data, through the SNMP protocol. Dependent service: FaultService
7.1.21 nimserver_agent Process

This describes the NIMServer service and the dependent service. NIMServer is provided by the nimserver_agent process. The nimserver_agent process provides the NIMServer service.
The NIMServer service only enables you to centralize the real-time monitoring of alarms, performance, and configuration status of some WRAN configuration objects. It also only provides the functions to some WRAN configuration objectssuch as alarm statistics, query of basic configuration information, query of configuration link constitution and basic configuration information, and query of adjacent cells and channel assignment. Dependent service: FaultService
7.1.22 neuser_agent Process

This describes the NeUserService service. NeUserService is provided by the neuser_agent process. The neuser_agent process provides the NeUserService service. The NeUserService service enables you to manage NE users. When the M2000 and NEs are connected properly, you can manage NE users through the M2000. For example, you can authenticate the login of NE users, deliver command rights and command group rights, and customize command groups. Dependent services: none
7.1.23 log_agent Process

This describes the LogService service and dependent services. LogService is provided by the log_agent process. The log_agent process provides the LogService service. The LogService service enables other services to save the system-related operation information to files. It also enables the client to query log records of the operating system and to set and query the parameters for dumping system logs. Dependent services: none
7.1.24 itmserver_agent Process

This describes the ITMServer service and the dependent services. The itmserver_agent process provides the ITMServer service. The ITMServer service provides the function of timing task management, which in turn centralizes the management and allocation of multiple M2000 timing tasks. The types of the tasks that have to be performed on time are categorized into export, database capacity management, synchronization, and backup. By using the ITMServer service, you can create, modify, delete, allocate, suspend, recover, copy, and perform a task. Dependent services: ScheduleService and LicenseService
7.1.25 fmexport_agent Process

This describes the FaultExportService service and dependent services. The fmexport_agent process provides the FaultExportService service. The FaultExportService service enables you to export alarms from the database. Dependent service: none
7.1.26 devdoc_agent Process

This describes the DevDocService service provided by the devdoc_agent process. The devdoc_agent process provides the DevDocService service. The DevDocService service enables you to manage device files. Dependent service: SWMService
7.1.27 cmdc_agent Process

This describes the CmDcService service and dependent services. CmDcService is provided by the cmdc_agent process. The cmdc_agent process provides the CmDcService service. The CmDcService service provides the functions such as data access interface, synchronization management, and session management. Dependent service: none
7.1.28 chr_agent Process

This describes the CHRService service and the dependent service. CHRService is provided by the chr_agent process. The chr_agent process provides the CHRService service. The CHRService service enables you to filter and upload CHR files for NEs. Dependent service: CMServer
7.1.29 3rdTool_agent Process

This describes the 3rdToolService service and dependent services. The 3rdTool_agent process provides the 3rdToolService service. The 3rdToolService service provides an interface for the third-party tools to access the data center. Dependent services: none
7.1.30 am_agent Process

This topic describes the function of the AMServer service, which is provided by the am_agent process. The am_agent process provides the AMServer service. The AMServer service provides the function of system partition management. During the M2000 operation, ensure that the am_agent process is operational. Dependent service: none
7.1.31 threshold_agent Process

This topic describes the function of the ThresholdService service provided by the threshold_agent process and the service that the threshold_agent process depends on. The threshold_agent process provides the ThresholdService service. The ThresholdService service provides the threshold management function. For example, this service allows you to add, generate, and change a threshold. In addition, this service can generate threshold alarms. During the M2000 operation, ensure that the threshold_agent process is operational. Dependent service: PMService
7.1.32 objgrp_agent Process

This topic describes the function of the ObjGrpService service provided by the objgrp_agent process and the service that the objgrp_agent process depends on. The objgrp_agent process provides the ObjGrpService service. The ObjGrpService service provides the function of object group management. During the M2000 operation, ensure that the am_agent process is operational. Dependent service: CMServer
7.1.33 nms_mml_agent Process

This describes the services and functions provided by the process nms_mml_agent. The nms_mml_agent process provides the NMSMMLServer service. That is, the NMS issues MML commands through the northbound MML transmission interface to managed NEs. If the northbound MML transmission interface is used when the M2000 is running, ensure that the NMSMMLServer is running correctly. When the northbound MML transmission interface is not used, the NMSMMLServer is not disruptive to other services. Dependent services: NeUserService
7.1.34 scriptserver_agent Process

This describes the services and functions provided by the process scriptserver_agent. The scriptserver_agent process provides the ScriptService service. ScriptService provide script timing and NEs access from script. Ensure that this service works properly during the M2000 operation. Dependent services: none
7.1.35 mmlproxyserver_agent Process

This describes the function of the MMLProxyServer service, which is provided by the mmlproxyserver_agent process. The mmlproxyserver_agent process provides the MMLProxyServer service.
The MMLProxyServer service provides channels for issuing MML commands and helps the M2000 receive the supplementary messages reported actively by NEs. You can stop the MMLProxyServer service when you do not need the integrated script tool iSStar to issue MML commands or to receive messages reported by NEs. Dependent service: MediationService
7.1.36 maintain_agent Process

This topic describes the function of the MaintenanceService service, which is provided by the maintain_agent process. The maintain_agent process provides the MaintenanceService service. The MaintenanceService service enables the periodic backup of the important system configuration files, database data, and real-time data of MOs. During the M2000 operation, ensure that the maintain_agent process is operational. Dependent service: none
7.1.37 nhcserver_agent Process

This describes the services and functions provided by the nhcserver_agent process. The nhcserver_agent process provides the NHCServer service. The NHCServer service checks the status, performance, and alarms of NE devices. It also checks the status of the M2000. If you plan to perform a heath check, you must ensure this service is running properly. Dependent service: none
7.1.38 porttrunk_agent Process

This describes the services and functions provided by the porttrunk_agent process. The porttrunk_agent process provides the PortTrunkingService service. By using the PortTrunkingService service, the M2000 server can communicate with the M2000 client through a specified port. You need not configure multiple ports on the firewall for communication. Dependent service: none
7.1.39 NodeBCommission_agent Process

This describes the services and functions provided by the NodeBCommission_agent process. The NodeBCommission_agent process provides the remote commissioning service for NodeBs. By using the NodeBCommission_agent service, you can enable the M2000 to automatically and remotely commission the NodeB upgrade. During the M2000 operation, ensure that the maintain_agent process is operational. Dependent services: cmdc_agent, cmserver_agent, nhc_agent, and swm_agent
7.1.40 udpdispatch_agent Process

This describes the services and functions provided by the udpdispatch_agent process. The udpdispatch_agent process provides the UdpDispatchService service. The UdpDispatchService service controls the forwarding of the Snmp Trap messages that are reported by NEs monitored by the M2000. The UdpDispatchService service forwards the Snmp Trap messages that are reported to port 162 by each NE to the Mediation service of each NE. When the M2000 is running, ensure that the udpdispatch_agent process works properly. Dependent services: EventService and PartitionService
7.1.41 nelicense_agent Process

This describes the services and functions provided by the nelicense_agent process. The nelicense_agent process provides the NeLicenseService service. The NeLicenseService service manages NodeB licenses and implements the sharing of a license between the NEs of the same type. Dependent service: CMService
7.1.42 nicserver_agent Process

This describes the services and functions provided by the nicserver_agent process. The nicserver_agent process provides the NICService service. The NICService service provides the NE information collection function for the NodeB and RNC in UMTS6.1. Specifically, the NICService services provides the functions of collecting the NodeB key statistical information, collecting the environment information about NodeB mirrors, uploading NodeB logs, and collecting RNC information. Dependent service: CMService
7.1.43 pmmedexp_agent Process

This describes the services and functions provided by the pmmedexp_agent process. The pmmedexp_agent process provides the PMMedExport service. The PMMedExport service obtains the resolved NE data directly from the Mediation rather than the database. It exports the performance result files by NE. Dependent services: LicenseService, CMServer, and SecurityService
7.1.44 cpm_agent Process

This describes the services and functions provided by the cpm_agent process. The cpm_agent process provides the CpmAgent service, that is, the pool configuration management service. The Pool configuration management service provides users with the following functions:
l
Creating a pool
7-14

l l l l l l l
Checking pool alarms Measuring the performance of a pool Monitoring the load of a pool in real time Displaying the pool topology Setting pool parameters Checking the NE data in a pool Checking the MSC Server or MSCe of a specific user
Dependent service: AMServer
7.1.45 ce_agent Process

This describes the services and functions provided by the ce_agent process. The ce_agent process provides the ConfigExport service. The ConfigExport service provides a transparent channel which enables the northbound NMS to directly obtain configuration data and set NE configurations from the GBSS. If this function is required, you must ensure that the service runs normally. Dependent service: EventService
7.1.46 imapds_agent Process

This describes the services and functions provided by the imapds_agent process. The imapds_agent process provides the DesktopService service. The DesktopService service enables the system to create, stop, and restart the task of collecting RNC and NodeB information, and collect and download log files. During the M2000 operation, ensure that the imapds_agent process is operational. Dependent service: NICServer
7.1.47 prssum_agent Process

This describes the services and functions provided by the prssum_agent process. The prssum_agent process provides the PRSSumService service. The PRSSumService service provides the function of summarizing the data of the PRS module. It is responsible for retrieving data in a specified order and scheduling the data. If you need to run the PRS module, the PRSSumService service cannot be stopped. Dependent services: CMServer and AMServer
7.1.48 prsreport_agent Process

This describes the services and functions provided by the prsreport_agent process. The prsreport_agent process provides the PRSReportService service. The PRSReportService service provides the function of querying the reports of the PRS module.
If you need to run the PRS module, the PRSReportService service cannot be stopped. Dependent service: none
7.2 Managing M2000 Processes

This describes how to query the running processes in the M2000 system and the operational status of the processes. 7.2.1 Viewing the Number of M2000 Processes This describes how to view the number of running M2000 processes. This task consumes a few system resources and does not affect system performance. 7.2.2 Viewing the States of M2000 Processes This describes how to view the states of M2000 processes on the M2000 client. If the M2000 system processes work improperly, you must log in to the system and rectify the existing fault.
7.2.1 Viewing the Number of M2000 Processes

This describes how to view the number of running M2000 processes. This task consumes a few system resources and does not affect system performance.
Prerequisite
l l
You have logged in to the M2000 server as user omcuser. You are authorized with relevant operation privileges.
Procedure
Step 1 Switch to /opt/OMC, which is the default installation directory of the M2000 server software. -bash-3.00$ cd /opt/OMC Step 2 Run the environment variable script. -bash-3.00$ . ./svc_profile.sh Step 3 View the number of M2000 processes in the system. -bash-3.00$ svc_ps|wc -l 40 The displayed number 40 is the number of processes.
NOTE
The M2000 system activates processes dynamically during operation. Accordingly, the number of processes changes dynamically.
----End
7.2.2 Viewing the States of M2000 Processes

This describes how to view the states of M2000 processes on the M2000 client. If the M2000 system processes work improperly, you must log in to the system and rectify the existing fault.
Prerequisite
l l
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Process Monitor tab to monitor the processes running on the M2000 server. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following default formats:
l l l l
TXT HTML XML CSV
----End
7.3 Managing M2000 Services

This describes how to view, start, and stop M2000 system services. 7.3.1 Viewing M2000 Services This describes how to view the M2000 services on the M2000 client. If the M2000 system services work improperly, you must log in to the system and rectify the existing fault. 7.3.2 Viewing the States of M2000 Services This describes how to view the states of M2000 services on the M2000 server. This operation consumes a few system resources and does not affect system performance. 7.3.3 Starting M2000 Services After you run the command start_svc, all M2000 services are started. If an M2000 service is already started, the system does not handle the service. Actually, the system starts only the inactive services. 7.3.4 Stopping M2000 Services After the M2000 services are stopped, the performance data and alarm data of the managed NEs cannot be processed. After the services are resumed, the M2000 updates the data with the NEs and processes the data.
7.3.1 Viewing M2000 Services

This describes how to view the M2000 services on the M2000 client. If the M2000 system services work improperly, you must log in to the system and rectify the existing fault.
Prerequisite
l l
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Service Monitor tab to monitor the processes running on the M2000 server. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
7.3.2 Viewing the States of M2000 Services

This describes how to view the states of M2000 services on the M2000 server. This operation consumes a few system resources and does not affect system performance.
Prerequisite
You have logged in to the M2000 server as user omcuser.
Procedure
Step 1 Change to the installation directory of the M2000. -bash-3.00$ cd /opt/OMC. By default, the installation directory is /opt/OMC. Step 2 Run the following commands to view the state of the M2000 services: -bash-3.00$ . ./svc_profile.sh -bash-3.00$ svc_adm -cmd status
Host: DEFAULTSYSAGENT Service Agent: 3gpp_agent [1 service(s)] pid: 24278 3GPPAgent [running ] Service Agent: 3rdTool_agent [1 service(s)] pid: 24284 3rdToolService [running ] Service Agent: am_agent [1 service(s)] pid: 24280 AMServer [running ]
7-18
Issue 05 (2008-05-20)
Service Agent: chr_agent [1 service(s)] pid: 24286 CHRService [running Service Agent: cmdc_agent [1 service(s)] pid: 3113 CmDcService [running
] ]
Service Agent: cmserver_agent [1 service(s)] pid: 24282 CMServer [running ] Service Agent: devdoc_agent [1 service(s)] pid: 24290 DevDocService [running ] Service Agent: em_agent [1 service(s)] pid: 24292 EventService [running ]
Service Agent: fmexport_agent [1 service(s)] pid: 24296 FaultExportService [running ] Service Agent: fmnotify_agent [1 service(s)] pid: 24294 FMNotify [running ] Service Agent: ifms_agent [1 service(s)] pid: 24304 FaultService [running ] Service Agent: irp_agent [1 service(s)] pid: 24307 IRPService [running ]
Service Agent: itmserver_agent [1 service(s)] pid: 24309 ITMServer [running ] Service Agent: log_agent [1 service(s)] pid: 24329 LogService [running ]
Service Agent: maintain_agent [1 service(s)] pid: 24355 MaintenanceService [running ] Service Agent: manager_agent [1 service(s)] pid: 24556 SystemService [running ] Service Agent: mml_agent [1 service(s)] pid: 24339 MMLAgent [running ]
Service Agent: mmlproxyserver_agent [1 service(s)] pid: 1334 MMLProxyServer [running ] Service Agent: monitor_agent [1 service(s)] pid: 24367 MonitorService [running ] Service Agent: neuser_agent [1 service(s)] pid: 24400 NeUserService [running ] Service Agent: nimserver_agent [1 service(s)] pid: 3485 NIMServer [running ] Service Agent: nms_mml_agent [1 service(s)] pid: 24392 NMSMMLServer [running ] Service Agent: notify_agent [1 service(s)] pid: 25379 RemoteNotifyService [running ] Service Agent: objgrp_agent [1 service(s)] pid: 24407 ObjGrpService [running ] Service Agent: omcne_agent [1 service(s)] pid: 24403 OMCNEService [running ] Service Agent: partition_agent [1 service(s)] pid: 24444 PartitionService [running ]
Issue 05 (2008-05-20)
7-19
Service Agent: pm_agent [1 service(s)] pid: 24432 PMService [running
Service Agent: pmexp_agent [1 service(s)] pid: 24424 PMExport [running ] Service Agent: pmmon_agent [1 service(s)] pid: 24427 PMMonService [running ] Service Agent: proxy_agent [1 service(s)] pid: 24447 ProxyServer [running ] Service Agent: sac_agent [1 service(s)] pid: 24314 LicenseService [running ]
Service Agent: scriptserver_agent [1 service(s)] pid: 24468 ScriptServer [running ] Service Agent: sm_agent [1 service(s)] pid: 24491 SecurityService [running ]
Service Agent: snmp_agent [1 service(s)] pid: 24513 SnmpAgent [running ] Service Agent: sumdata_agent [1 service(s)] pid: 6456 SumDataService [running ] Service Agent: sumreport_agent [1 service(s)] pid: 24544 SumReportService [running ] Service Agent: swm_agent [1 service(s)] pid: 24450 SWMService [running ]
Service Agent: threshold_agent [1 service(s)] pid: 24571 ThresholdService [running ] Service Agent: tm_agent [1 service(s)] pid: 24627 TopoService [running ]
[All Services: 39 ] [Running: 39 ] [No License: 0 ] [Not Running: 0 ]

NOTE
The M2000 system generates processes and services dynamically during operation. Accordingly, the number of processes and services changes dynamically.
----End
7.3.3 Starting M2000 Services

After you run the command start_svc, all M2000 services are started. If an M2000 service is already started, the system does not handle the service. Actually, the system starts only the inactive services.
Prerequisite
Procedure
Step 1 Switch to /opt/OMC, which is the default installation path of the M2000 server software. # cd M2000
Step 2 Run the following commands: # . ./svc_profile.sh # start_svc

NOTE
Before starting the M2000 server, ensure that the Sybase is started. For information about starting the Sybase, refer to 15.2.2 How to Start the Sybase.
----End
7.3.4 Stopping M2000 Services

After the M2000 services are stopped, the performance data and alarm data of the managed NEs cannot be processed. After the services are resumed, the M2000 updates the data with the NEs and processes the data.
Prerequisite
Procedure
Step 1 Change to the installation directory of the M2000 server. The default installation path of the M2000 server software is /opt/OMC. # cd /opt/OMC Step 2 Run the following command to stop the M2000 services: # . ./svc_profile.sh # stop_svc Step 3 Run the following command to check whether there is any output. If no output is displayed, you can infer that the M2000 services are stopped. # svc_ps Step 4 If some M2000 services are still running, run the following command to forcibly stop them: # kill_svc Step 5 Run the following command to stop the M2000 daemon: # stop_daem Step 6 Run the following command to check whether there is any output. If no output is displayed, you can infer that the M2000 daemon is stopped. # daem_ps Step 7 If the M2000 daemon is still running, run the following command to forcibly stop it: # kill_daem
Step 8 Run the ps -ef |grep 9999 |grep -v grep command and check whether any output is displayed. If some output is displayed, run the stop_tao_services command to stop the TAP process. ----End
7-22
Issue 05 (2008-05-20)
8 Managing the M2000 Databases
Managing the M2000 Databases
About This Chapter

This chapter describes how to manage the M2000 databases. 8.1 Introduction to M2000 Databases Based on the Sybase, the M2000 creates the following databases: omcdb, omclogdb, omcsmdb, omctmdb, fmdb, pmdb, swmdb, pmcomdb, sumdb, itfndb. The capacities of the databases are specified during the installation of the M2000 server application. No manual settings are required. Operate databases using Sybase commands. 8.2 Viewing the States of M2000 Databases This describes how to view the states of M2000 databases. You can run Sybase commands on the server to view the states of M2000 databases. Alternatively, you can view the database states using the system monitor browser. 8.3 Clearing M2000 Databases This describes how to dump the data in the M2000 databases. The data includes the performance data, NE operation logs, NE security logs, alarm data, operation logs, system logs, and security logs. You can configure an integrated task for dumping the data in the M2000 databases. 8.4 Backing Up M2000 Databases This describes how to back up the M2000 databases. The M2000 databases are categorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb and sumdb.
Issue 05 (2008-05-20)
8-1
8.1 Introduction to M2000 Databases

Based on the Sybase, the M2000 creates the following databases: omcdb, omclogdb, omcsmdb, omctmdb, fmdb, pmdb, swmdb, pmcomdb, sumdb, itfndb. The capacities of the databases are specified during the installation of the M2000 server application. No manual settings are required. Operate databases using Sybase commands. The function of each M2000 database is as follows:
l l l l l l l
omcdb: stores the M2000 configuration data and relevant internal data. omclogdb: stores the log management data. omcsmdb: stores the security management data. omctmdb: stores the topology management data. fmdb: stores the alarm data of NEs and the M2000. pmdb: stores the performance measurement data of NEs. swmdb: stores the NE version configuration data and the file information on software management and module management. pmcomdb: stores the performance measurement data of NEs. sumdb: stores the summarization data of NEs. itfndb: This database is created during the installation of northbound components and is used for storing northbound configuration data and the data of performance tasks and performance thresholds.
l l l
8.1.1 omcdb Database This describes the database omcdb. 8.1.2 omclogdb Database This describes the omclogdb database, which stores the M2000 log management data. 8.1.3 omcsmdb Database This describes the omcsmdb database, which stores the security management data. 8.1.4 omctmdb Database This describes the omctmdb database, which stores the topology management data. 8.1.5 fmdb Database This describes the fmdb database, which stores the alarm data of the M2000 and the managed NEs. 8.1.6 pmdb Database This describes the pmdb database, which stores the NE performance measurement data. 8.1.7 swmdb Database This describes the swmdb database, which stores the file information about the software management module and the configuration data of NE versions. 8.1.8 pmcomdb Database The pmcomdb database is used for storing the static performance measurement data of NEs. 8.1.9 sumdb Database The sumdb database stores the summarized performance data of NEs for performance reports to use.
8.1.10 itfndb Database This describes the itfndb database, which stores the northbound configuration data, performance tasks, and performance threshold data.
8.1.1 omcdb Database

This describes the database omcdb. The omcdb database stores the M2000 configuration data, security data, and internal data. The omcdb database requires a disk space of more than 1,000 MB. Table 8-1 lists the names and functions of tables in the omcdb database. Table 8-1 Names and functions of tables in the omcdb database Table Name Tables with moi_ as the prefix Tables with mos_ver_ as the prefix Tables with nbmmlNe_ as the prefix Tables with ne_ as the prefix Tables with omc_ as the prefix Tables with rel_ as the prefix tbl_AllNeInfo Other tables Function Records the information about MO examples. Records the information about versions. Records the information about the format of messages transferred between the M2000 and the NEs. Records the information about NE models. Records the data about network management. Records the associations between MOs. Records the network management data that are created for compatibility with previous versions. Records other configuration data of the M2000.
8.1.2 omclogdb Database

This describes the omclogdb database, which stores the M2000 log management data. The omclogdb database requires more than 500 MB disk space. Table 8-2 lists the names and functions of the tables in the omclogdb database. Table 8-2 Names and functions of the tables in the omclogdb database Table Name tbl_Audit tbl_SysLog
Issue 05 (2008-05-20)
Function Records the logs of user operations. Records the logs of system operations.
Table Name tbl_SysLogResultDef tbl_SysLogStaticInfo Other tables
Function Records the result information about system logs. Records the static information about system logs. Records the information about other logs.
8.1.3 omcsmdb Database

This describes the omcsmdb database, which stores the security management data. Table 8-3 lists the names and functions of the tables in the omcsmdb database. Table 8-3 Tables of the omcsmdb database and the corresponding functions Table Name tbl_AccessTable tbl_AccessViewNodeRelTable tbl_AccessViewNodeTable tbl_IDTable tbl_SMAccessPolicyItem tbl_SMGroup tbl_SMGroupUserMap tbl_SMLoginRec tbl_SMNEUser tbl_SMPrivateGroupUserMap tbl_SMSecurityPolicy tbl_SMTerm tbl_SMUser tbl_SMUserHistoryRec tbl_SMUserNEUserMap tbl_SMUserTerminalMap Function Records the binding relations between user groups and privileges. Records the relations between the privilege display nodes. Records the privilege display nodes. Records the reclaimed IDs. Records the privilege statistics for binding user groups. Records the basic information about user groups. Records the binding relations between user groups and users. Stores the history records on user login. Records the basic information about NE users. Records the binding relations between private groups and users. Records the security policy. Records the basic information about terminals. Records the basic information about users. Records history user passwords. Records the binding relations between users and NE users. Records the binding relations between users and terminals.
Issue 05 (2008-05-20)
8-4
Table Name tbl_SecurityObjectTable tbl_SessionIDTable tbl_StaticTypeRelationTable tbl_StaticTypeTable tbl_StaticTypeViewTable
Function Records security objects. Records session IDs. Records the relations between privileges. Records the static security information about object types, privileges, and operations. Records the static security information.
8.1.4 omctmdb Database

This describes the omctmdb database, which stores the topology management data. The omctmdb database requires a disk space of more than 550 MB. Table 8-4 lists the names and functions of the tables in the omctmdb database. Table 8-4 Names and functions of the tables in the omctmdb database Table Name MOTSConfig MOTSDomain MOTSLink MOTSNode MOTSSubnet MOTSSubtree MOTSVSubnet MOTSView MOTSViewObj TSTempLoc TSTempPos Function Records the topology configuration values, including the initial value and the maximum value assigned by ObjID. Records the information on topology domains. Records the information on topology links. Records the information on topology NEs. Records the information on topology subnets. Records the information on the topology tree. Records the information on topology logical subnets. Records the information on topology views. Records the information on topology view objects. Records the temporary table that stores the longitude and latitude coordinates of the e-map. Records the temporary table that stores the x-axis and y-axis coordinates of common physical topology.
8.1.5 fmdb Database

This describes the fmdb database, which stores the alarm data of the M2000 and the managed NEs.
The fmdb database stores the NE data and the M2000 alarm data. A disk space of more than 3,700 MB is required for the storage. Table 8-5 lists the name and function of each table in the fmdb database. Table 8-5 Tables of the fmdb database and the corresponding functions Table Name tbl_cur_alm tbl_event tbl_his_alm tbl_mask_alm Other tables Function Records current alarms. Records event alarms. Records history alarms. Records shielded alarms. Records the internal processing data of alarms.
8.1.6 pmdb Database

This describes the pmdb database, which stores the NE performance measurement data. The pmdb database stores the NE performance measurement data. A disk space of more than 13,000 MB is required for the storage. If the pmdb database is fully occupied, the M2000 raises an alarm. After the storage period of the performance measurement data expires, the most recent data overwrites the earlier data on a daily basis. If the data is saved for less than 30 days old but the pmdb database is fully occupied, you must change the number of days till when the data can be stored. Otherwise, the pmdb database is suspended and it cannot process any performance data from the NEs. Change the number of saving days when the remaining space of the pmdb database is insufficient. To calculate the number of days till when the data can be stored, perform the following steps: 1. 2. 3. Observe the usage of the pmdb database when the M2000 runs for half a month. Calculate the space of the pmdb database used a day. Calculate the number of days that the pmdb database lasts.
The pmdb database consists of the following types of tables:

l l l
Counter tables Template tables Function subset tables and period tables
Counter Tables
Compared with the data in other types of tables, the data in these tables is stable. Table 8-6 lists the name and function of each table.
Table 8-6 Counter tables in the pmdb database and the corresponding functions Table Name systbl_NeType systbl_FunctionSet systbl_FunctionSubSet systbl_Counters systbl_Counter_Unit Function Records all possible NE types in M2000. Records the function sets of all NEs. Records the measurement units of all function sets. Records all measurement counters. Records the units of all counters.
Template Tables
Template tables contain several tables that record measurement information. Table 8-7 lists the name and function of each table. Table 8-7 Template tables in the pmdb database and the corresponding functions Table Name tbl_ObjectInstance tbl_MeasurementPeriod tbl_MeasurementCounter tbl_RTMeasurementCounter Function Records measurement objects. Records measurement periods. Records measurement counters. Records real-time measurement counters.
Function Subset Tables and Period Tables

The measurement results are saved according to function subset and period. Table 8-8 lists the name and function of each table. Table 8-8 Function subset tables and period tables in the pmdb database and the corresponding functions Table Name tbl_Result_XXX_Y Function Records periodic results. In the table name, XXX is the ID of the function subset and Y is the period index between 0 and 4. Records the lost result information. If the system does not receive any result from an NE within a set interval, a new entry is added to this table. tbl_MeasurementSuspendInfo Records suspended tasks.
tbl_LostResultInfo
Issue 05 (2008-05-20)
8-7
8.1.7 swmdb Database

This describes the swmdb database, which stores the file information about the software management module and the configuration data of NE versions. The swmdb database stores the files managed by the software management module and the NE version configuration data. A disk of more than 3,000 MB is required for storage. Table 8-9 lists the name and function of each table. Table 8-9 Tables of the swmdb database and the corresponding functions Table Name tbl_FTPFileSet tbl_VersionRelation tbl_NELogTable Function Records the files managed by the software management module. Records the information about version relations. Records the NE operation logs.
8.1.8 pmcomdb Database

The pmcomdb database is used for storing the static performance measurement data of NEs. The space of the pmcomdb database must be greater than 400 MB. In the SLS system, the pmcomdb database is deployed on the master node. If the remaining space of the pmcomdb database is insufficient, the system generates an alarm. The pmcomdb database consists of the following types of tables:
l l
Counter information table Template information table
Counter Information Table

The counter information tables comprise several tables and store relatively fixed information. Table 8-10 lists the function and name of each table. Table 8-10 Counter information tables in the pmcomdb database and the corresponding functions Table Name systbl_NeType systbl_FunctionSet systbl_FunctionSubSet Function Record the types of NEs that the M2000 can manage. Record all the function sets of NEs. Record the measurement units of all the function sets.
Issue 05 (2008-05-20)
8-8
Table Name systbl_Counters systbl_Counter_Unit
Function Record the measurement counters of all the measurement units. Record the unit of each counter.
Template Information Table

Template information tables comprise several tables, which record measurement information. Table 8-11 lists the name and function of each table. Table 8-11 Template information tables in the pmcomdb database and the corresponding functions Table Name tbl_ObjectInstance tbl_MeasurementPeriod tbl_MeasurementCounter tbl_MeasurementSuspendInfo Function Record the information on measurement objects. Record the information on measurement periods. Record the information on measurement counters. Record the information on suspended tasks.
8.1.9 sumdb Database

The sumdb database stores the summarized performance data of NEs for performance reports to use. The size of the sumdb database is equal to one thirds the size of the pmdb database, that is, more than 4,500 MB. In the SLS system, the sumdb database is deployed on the master node. The sumdb database consists of the following types of tables:
l l l
Summary data tables History information tables Configuration information tables
Summary Data Tables

Summary data tables store the data collected from the performance result tables in the pmdb database. For details on the name and function of each table among the summary data tables, refer to Table 8-12. fssName indicates the name of a function subset. ObjLevel indicates an object dimension. fssName and ObjLevel can be configured in the configuration file. For example, you can
configure fssName and ObjLevel in the /opt/OMC/etc/pm/sumdata/MSCServer/ Perform.xml file for the NE MSCServer. Table 8-12 Summary data tables in the sumdb database and their functions Table Name f_fssName_Raw Function Indicate original result serial tables, which retrieves data on the basis of performance result tables. Indicate hour serial tables, which retrieves data on the basis of original results. Indicate the day serial tables, which retrieves data on the basis of the hour serial tables. Indicate the week serial tables, which retrieves data on the basis of the day serial tables. Indicate the month serial tables, which retrieves data on the basis of the week serial tables. Indicate the busy-hour serial tables, which stores busy-hour time points and summarizes busy hours on the basis of the hour serial tables.
f_fssName_ObjLevel_H f_fssName_ObjLevel_D
f_fssName_ObjLevel_W
f_fssName_ObjLevel_M
f_ObjLevel_DH
History Information Tables

History information tables comprise several tables, which separately record the summarized history information. Table 8-13 lists the name and function of each table. Table 8-13 History information tables in the sumdb database and the corresponding functions Table Name tbl_RawHistoryInfo Function Refers to the original result history information table, which records the summarized history information of original results. Refers to the summary history information table, which records the history information summarized on the basis of time and objects.
tbl_SumHistoryInfo
8-10
Issue 05 (2008-05-20)
Table Name tbl_BusyHistoryInfo
Function Refers to the busy-hour history information table, which records the history information summarized during busy hours.
Configuration Information Tables

The configuration information tables record the object information retrieved from the configuration database. Table 8-14 describes the name and function of each table in the configuration information tables. ObjLevel indicates the object dimension, which can be configured in the configuration file. Table 8-14 Configuration information tables in the sumdb database and the corresponding functions Table Name d_ObjLevel (such as d_Switch) Function Refers to the configuration information table and stores the object information whose object dimension is at the ObjLevel level, for example, switch.
8.1.10 itfndb Database

This describes the itfndb database, which stores the northbound configuration data, performance tasks, and performance threshold data. The itfndb database is optional. It requires a disk space of at least 200 MB. Table 8-15 lists the name and function of each table. Table 8-15 Tables of the itfndb database and the corresponding functions Table Name tbl_JGeneralInfo tbl_JMoInstance tbl_JStatusRecord tbl_JMeasurementCategory tbl_JSchedule tbl_RegM2KObject tbl_MGeneralInfo tbl_MMoInstance
Issue 05 (2008-05-20)
Function Records the general information about tasks. Records the instances of tasks. Records the Status of tasks. Records the measurement categories of tasks. Records the task scheduling. Records the registered M2000 objects. Records the general information about thresholds. Records the instances of thresholds.
8-11
Table Name tbl_MMeasurementCategory tbl_MThresholdPackElemen tbl_MAlarmRecord tbl_MStatusRecord Other tables
Function Records the measurement categories of thresholds. Records the details of thresholds. Records the alarm records of thresholds. Records the status of thresholds. Records the information about northbound implementation.
8.2 Viewing the States of M2000 Databases

This describes how to view the states of M2000 databases. You can run Sybase commands on the server to view the states of M2000 databases. Alternatively, you can view the database states using the system monitor browser. 8.2.1 Viewing the Database Usage of the M2000 Server on the M2000 Client This describes how to view the attributes of the database of the M2000 client, such as database name, server name, Solaris, database status, and free space of the database. 8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands This describes how to view the database status of the M2000 server by using Sybase commands. This operation requires very few system resources and does not affect system operation.
8.2.1 Viewing the Database Usage of the M2000 Server on the M2000 Client
This describes how to view the attributes of the database of the M2000 client, such as database name, server name, Solaris, database status, and free space of the database.
Prerequisite
l l
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Database Monitor tab. The database of the M2000 server is displayed. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:

l l l l
TXT HTML XML CSV
----End
8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands
This describes how to view the database status of the M2000 server by using Sybase commands. This operation requires very few system resources and does not affect system operation.
Prerequisite
l l
You have logged in to the M2000 server as user dbuser. The Sybase service is running.
Context
In addition to the method described in 8.2.1 Viewing the Database Usage of the M2000 Server on the M2000 Client, you can use the Sybase commands to view the disk usage of the M2000 server.
Procedure
Step 1 Check all the databases of the M2000 server. -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpdb 2> go
NOTE
Step 2 View the database usage and the event log space usage. 1> sp_helpdb M2000 database name 2> go To view the usage of the pmdb database, run the following command: 1> sp_helpdb pmdb 2> go
name db_size status owner dbid created
Issue 05 (2008-05-20)
8-13
------------ ------------- ------ ------ ----------------------------------------------------------------------------------------------------------------------------------------pmdb 13000.0 MB sa 9 Mar 13, 2007 select into/bulkcopy/pllsort, trunc log on chkpt (1 row affected) device_fragments size usage created free kbytes ------------------------------ ------------- ------------------------------------------- ---------------data001_dev 10000.0 MB data only Mar 13 2007 6:37PM 10193312 log001_dev 3000.0 MB log only Mar 13 2007 6:37PM not applicable -------------------------------------------------------------------------------log only free kbytes = 3059992 (return status = 0)
As shown in the previous command result, the occupied space of the pmdb database is 13,000 MB, where 10,000 MB is used for storing performance data and 3,000 MB is used for storing the performance log data. Run the following command to exit: 1>exit For more information about the M2000 database, see 8.1 Introduction to M2000 Databases. ----End
8.3 Clearing M2000 Databases

This describes how to dump the data in the M2000 databases. The data includes the performance data, NE operation logs, NE security logs, alarm data, operation logs, system logs, and security logs. You can configure an integrated task for dumping the data in the M2000 databases.
Prerequisite
l l
You have logged in to the M2000. You are authorized to clear the M2000 databases.
Context
After the data is dumped, the following data is saved in the default directory of the M2000 server and removed from the databases:
l l l l
The performance data in the pmdb database The NE operation logs and the NE security logs in the swmdb database The alarm data in the fmdb database The operation logs, system logs, and security logs in the omclogdb database
8-14
Procedure
Step 1 Dump the performance data in the pmdb database. 1. 2. 3. 4. 1. 2. 3. 4. 1. 2. 3. 4. 1. 2. 3. 4. 1. 2. 3. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select Performance Data under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select NE Operation Log under the node Database Capacity Management from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select NE Security Log under the node Database Capacity Management from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select Alarm Data under the node Database Capacity Management from the navigation tree Task Type. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select Operation Log under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute.
Step 2 Dump the NE operation logs in the swmdb database.
Step 3 Dump the NE security logs in the swmdb database.
Step 4 Dump the alarm data in the fmdb database.
Step 5 Dump the operation logs in the omclogdb database.
Issue 05 (2008-05-20)
4. 1. 2. 3. 4. 1. 2. 3. 4.
In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select System Log under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK. On the GUI of the M2000 client, choose Maintenance > Task Management. The Task Management window is displayed. In the left part of the Integrated Task Management window, select Security Log under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the Integrated Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK.
Step 6 Dump the system logs in the omclogdb database.
Step 7 Dump the security logs in the omclogdb database.
----End
8.4 Backing Up M2000 Databases

This describes how to back up the M2000 databases. The M2000 databases are categorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb and sumdb.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to back up the M2000 system.
Procedure
Step 1 On the main window, choose Maintenance > Task Management. The Centralized Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup in the navigation tree and double-click the node. The Attribute dialog box of server periodic backup is displayed, as shown in Figure 8-1.
8-16
Issue 05 (2008-05-20)
Figure 8-1 Periodic backup
Step 3 Click Common Parameters, and set Task Name and Start Time. Step 4 Click Extended Parameters, and set Server Full Backup Date, as shown in Figure 8-2.
Issue 05 (2008-05-20)
8-17
Step 5 Click OK. The system performs periodic backup automatically. Step 6 If data is backed up on a tape and the tape is fully written during the backup, perform Step 7 through Step 8 to replace the tape with a new tape. Step 7 The system automatically ejects the fully written tape and waits you to replace the tape. As shown in Figure 10-3, the Information field in the Backup Management dialog box displays the following message: The current tape is fully written. Please replace it with another tape as soon as possible. Step 8 Insert a new tape into the tape drive. The Information field in the Backup Management dialog box displays the following message: The tape has been placed in the tape drive. Please resume the backup operation. After you insert a new tape, the system continues to back up the M2000 dynamic data.
8-18
Issue 05 (2008-05-20)

NOTE
If you do not replace the fully written tape within the wait time preset in the configuration file, the Information field in the Backup Management dialog box displays the following message: Tape replacement times out. The data backup fails. In such a case, you need to insert a tape into the tape drive and performs a new full backup.
If the newly inserted tape is fully written again, you need to insert another tape for backup. In this way, change tapes until all the data is backed up.
----End
Issue 05 (2008-05-20)
8-19
9 Managing the M2000 Files and Disks
Managing the M2000 Files and Disks
About This Chapter

This chapter describes how to manage the file systems and disks on the M2000 server and client. 9.1 Managing Files and Disks on M2000 Clients This describes how to manage the file systems and disks on the M2000 clients. 9.2 Managing Files and Disks on the M2000 Server This describes how to manage the file systems and disks on the M2000 server.
Issue 05 (2008-05-20)
9-1
9.1 Managing Files and Disks on M2000 Clients

This describes how to manage the file systems and disks on the M2000 clients.
9.1.1 Introduction to the M2000 Client File System

This introduces the M2000 client file system. The client software runs on the Windows operating system and is based on the JAVA virtual machine. The installation package of the M2000 client software includes the JAVA virtual machine supported by Windows. The required free disk space on the M2000 client is as follows:
l
Without the integration of the LMT: F = I + T + (S x N) With the integration of the LMT: F = I + T + (S x N) + (L x N)
Table 9-1 describes the parameters specified in the equations. Table 9-1 Parameter description Parameter F I T Description Free disk space (MB) Initial version size (about 300 MB) Temporary space for storing the patches required for the upgrade (smaller than 20 MB) Size of NE adaptation file (3 MB to 10 MB) Number of NE versions (based on requirements) Size of integrated LMT file (20 MB to 50 MB)
S N L
Table 9-2 lists the folders related to the M2000 client software. Table 9-2 Folders related to the M2000 client software Folder M2000 client installation path Description Refers to the M2000 client installation path. The default path is C: \iManagerM2000Client.
Issue 05 (2008-05-20)
9-2
Folder M2000 client installation path\client M2000 client installation path\client\bin M2000 client installation path\client\Data M2000 client installation path\client \diagnosis
Description Refers to the directory for saving client programs. Refers to the directory for saving the executable files. Refers to the directory for saving the NE configuration files. Refers to the directory for saving the information that is used for locating problems.
NOTE This directory appears only after you run the M2000 diagnostic tool.
M2000 client installation path\client\dtd M2000 client installation path\client\help M2000 client installation path\client \IDAPI32 M2000 client installation path\client\jre M2000 client installation path\client\lib M2000 client installation path\client \localWS M2000 client installation path\client\style M2000 client installation path\client \Templates M2000 client installation path\client\tmp M2000 client installation path\client \tracefile M2000 client installation path\uninstall M2000 client installation path\client \update
Refers to the directory for saving the Dtd files. Refers to the directory for saving the online help files. Refers to the directory for saving the localWS dynamic link libraries. Refers to the Java operating environment. Refers to the directory for saving the library files. Refers to the directory for saving LocalShell that is used to start the 2G LMT. Refers to the directory for saving the configuration files of client. Refers to the directory for saving the mapping between administrative regions and their IDs. Refers to the directory for saving temporary files during the upgrade. Refers to the directory for saving the trace files. Refers to the directory for saving the uninstaller. Refers to the directory for saving the upgrade files.
9.1.2 Clearing the Disk Space of an M2000 Client

This describes how to clear the disk space of an M2000 client. Before performing this operation, ensure that the files to be deleted are not required for future operations. Deleting a useful file by mistake may lead to a system operation error.
Context
CAUTION
You can delete the files when the client is running. Do not delete the files generated on that day. During the routine O&M, back up and clear the following files:
l l
Trace logs Temporary files after the running of the M2000 log collector
Procedure
l Delete the trace logs. Delete the history trace logs saved in the directory M2000 client installation path\client \tracefile. It is recommended that you preserve the trace logs generated in the latest two weeks. l Delete the temporary files generated after the running of the M2000 log collector. Delete the temporary files that are generated after the running of the M2000 log collector and are saved in the directory M2000 client installation path\client\diagnosis. ----End
9.2 Managing Files and Disks on the M2000 Server

This describes how to manage the file systems and disks on the M2000 server. 9.2.1 Introduction to the M2000 Server File System This introduces the structure of the M2000 server files and the planning of disk partition for various server types. The server communicates with the NEs, stores the O&M data of the NEs, and provides an interface for the NMS. 9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000 Client This describes how to view the disk usage of the M2000 server through the system monitor browser on the M2000 client. 9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands This describes how to use Solaris commands for viewing the disk usage of the M2000 server. This task uses very few system resources and does not affect the system operation. 9.2.4 Clearing the Disk Space of the M2000 Server This describes how to clear the disk space of the M2000 server. Before clearing disk space, ensure that the files to be deleted are useless. Deleting a useful file by mistake may lead to a system failure.
9-4
Issue 05 (2008-05-20)
9.2.1 Introduction to the M2000 Server File System

This introduces the structure of the M2000 server files and the planning of disk partition for various server types. The server communicates with the NEs, stores the O&M data of the NEs, and provides an interface for the NMS. The M2000 server runs on the Solaris platform. The M2000 system operation requires the following software:
l l l
Sybase CORBA supporting software FTP supporting software
The installation package of the M2000 server software includes the software providing the File Transfer Protocol (FTP) and Common Object Request Broker Architecture (CORBA) functions. Table 9-3 lists the folders related to the M2000 server software. Table 9-3 Directories related to the M2000 server software Directory M2000 server installation directory Description M2000 server installation directory is the installation directory of the M2000 server software. By default, the installation directory is / opt/OMC. Refers to directory where executable files are located. Refers to the directory where the system configuration files and structured query language (SQL) scripts are located. Refers to the directory where library files are located. Refers to the directory where the system administration commands are located. Refers to the directory where template files are located. Refers to the directory where third-party software is located. Refers to the directory where the M2000 service management graphical tool is located. Refers to the directory where the log files, the performance files, and the files recording exported alarms are located. Refers to directory where the M2000 operation data is located.
9-5
M2000 server installation directory/ bin M2000 server installation directory/etc
M2000 server installation directory/lib M2000 server installation directory/ lbin M2000 server installation directory/ model M2000 server installation directory/ 3rdTools M2000 server installation directory/ tools/startsvcgui M2000 server installation directory/ var /export/home/omc/var
Issue 05 (2008-05-20)
Directory /export/home/omc/var/syslog /export/home/backup /export/home/sysm/ftproot/pm
Description Refers to the directory where system logs are located. Refers to the directory where backup files are located. Refers to the directory where the traffic measurement data of each NE, which is reported as files, is located. Refers to the directory where the northbound CORBA interface performance files are located. Refers to the directory where the configuration data files that are periodically exported are located. Refers to the directory where the exported performance result files are located. Refers to the directory where the NE version package is located. Refers to the directory where the NE data backup is located.
NOTE
l The NE fdn is a code representing an NE sample in
/opt/OMC/var/itf_n/FileTransferIRP/ PM /export/home/omc/var/fileint/cm /export/home/omc/var/fileint/pm /export/home/sysm/ftproot/NE name/ Software /export/home/sysm/ftproot/NE name/ Data/NE fdn
the program.
l The data generated for manual backup is located in
the BAKDATA****** directory. The data generated for automatic backup is located in the AUTOBAKDATA****** directory.
/export/home/omc/var/logs /opt/sybase/ASE-15_0/install /var/adm /export/home/backup/omc /export/home/omc/var/etc/conf/ license
Refers to the directory where M2000 log files are located. Refers to the directory where Sybase log files are located. Refers to the directory where Solaris log files are located. Refers to the directory where the backup files of dynamic data are located. Refers to the directory where the license file of the M2000 is located.
Sun Netra 240 Disk Partition

A standard disk in the Netra 240 system should be configured with two 146 GB hard disks and partitioned based on Table 9-4.
9-6
Issue 05 (2008-05-20)
Table 9-4 Planning for Server Disk Partitioning (Netra 240) Hard Disk No. 1 Partiti on No. 0 1 2 3 4 5 6 7 Partition Name / swap overlap /data /log /export/home /globaldevices 39000 14000 50000 1024 200 Size (MB) 25000 8192 Description Root partition Data exchange partition Disk mapping. Keep the default size. Application database partition Application database partition M2000 operation data partition Reserved Used for disk mirroring A partition name is not required.
Used as the mirroring disk for the first hard disk
Sun Fire V890 Disk Partition and Disk Array Partition

A standard disk in the V890 system should be configured with six 146 GB hard disks and one 6140 disk array. The 6140 disk array consists of sixteen 146 GB hard disks. Table 9-5 lists the partitioning of local disks. Two disks on the 6140 disk array act as hotspare, while the other fourteen disks act as RAID5. Table 9-5 Planning for Disk Partitioning on the Server(V890) Hard Disk No. Partitio n No. 0 1 2 1 3 4 5 6
Issue 05 (2008-05-20)
Partition Name / swap overlap
Size (MB) 110000 20000
Description Root partition Data exchange partition Disk mapping. Keep the default size.
/globaldevices
1024
Reserved
9-7
Hard Disk No.
Partitio n No. 7
Partition Name
Size (MB) 200
Description Used for disk mirroring,a partition name.is not required.
Sun Fire E4900 Disk Partition and Disk Array Partition

A standard disk in the E4900 system should be configured with two 146 GB hard disks and one 6140 disk array. The 6140 disk array consists of sixteen 146 GB hard disks. Table 9-6 lists the partitioning of local disks. Two disks on the 6140 disk arrays act as hotspare disks, while others act as RAID5. Table 9-6 Planning for Server Disk Partitioning (E4900) Hard Disk No. 1 Partiti on No. 0 1 2 Partition Name Size (MB) Description
/ swap overlap
50000 16384
Root partition Exchange partition Hard disk mapping. Maintain the default size.
3 4 5 6 7 /globaldevices 1024 200 Reserved Used for disk mirroring,a partition name.is not required.
9.2.2 Viewing the Disk Usage of the M2000 Server on the M2000 Client
This describes how to view the disk usage of the M2000 server through the system monitor browser on the M2000 client.
Prerequisite
l l
You have logged in to the M2000 system. You are authorized with the relevant operation privileges.
Context
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . Step 2 Click the Hard Disk Monitor tab. The disk usage of the M2000 server is displayed. Step 3 This step is optional. Click Save As to save the monitoring data. You can save the monitoring data to a file in either of the following four default formats:
l l l l
TXT HTML XML CSV
----End
9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands
This describes how to use Solaris commands for viewing the disk usage of the M2000 server. This task uses very few system resources and does not affect the system operation.
Prerequisite
Procedure
Step 1 Run the following command: -bash-3.00$ df -k Step 2 View the disk usage. Normally, the disk usage is smaller than 90%, which means the value of capacity is smaller than 90% in the output. ----End
9.2.4 Clearing the Disk Space of the M2000 Server

This describes how to clear the disk space of the M2000 server. Before clearing disk space, ensure that the files to be deleted are useless. Deleting a useful file by mistake may lead to a system failure.
Context
During the routine O&M, back up and clear the following files:
l l l l l
Files storing information about NEs and the M2000 server Software upgrade package and decompressed files Trace logs Backup files Temporary files created during the system operation
CAUTION
You can delete files when the server is running. Before deleting files, run the command ls -l to check the files generated on that day. Do not delete the files generated on the very day.
Procedure
l Export the files that save the information of NEs and the M2000 server. Back up the files on a tape. The files are divided into the following types:
NOTE
The directory for saving alarm dump files can be configured on the client. The following default directories are provided:
Files generated during alarm auto-dump Event alarm dump files are stored in the /export/home/omc/var/fm/dump/event/ directory. Fault alarm dump files are stored in the /export/home/omc/var/fm/dump/history/ directory.
User log files User log dump files are stored in the /opt/OMC/var/userlogs directory. System generated core files Core files refer to the files in the /export/home/omc/var/logs/ directory. Trace history files Trace history files are stored in the /export/home/omc/var/logs/tracebak/ directory.
Delete the software update package and the decompressed files. After the upgrade, delete the original upgrade package and the decompressed files. The upgrade package and decompressed files are stored in the folder named after the upgrade patch in the path /export/home.
9-10
Issue 05 (2008-05-20)
CAUTION
Generally, the decompressed upgrade files are saved in the /export/home directory. The folder name of the upgrade files is created according to the upgrade patch name. The actual saving path may be different. For example, the saving folder may be in the /export/home/ bak directory. l Delete trace Logs. Modify the value of tracebackupnum in the tracemonitor_svc_ex.xml file to reduce the number of trace backup files. Edit the tracemonitor_svc_ex.xml file in the /opt/OMC/etc/conf/ directory to set the trace log monitor period, size limit, and number of backup files. /opt/OMC is the default installation path of the M2000 server software. The contents of the tracemonitor_svc_ex.xml file are as follows:
<param name="checktracetime">60</param> <param name="tracesize">50</param> <param name="tracebackupnum">1000</param>
Where, checktracetime sets the control period of trace files. The system checks trace files every 60 seconds. If the size of trace files is larger than the value of tracesize, the system regards that the file space is used up, and thus backing up the file. tracesize sets the threshold for the trace file size to 50 MB. tracebackupnum sets the number of trace backups in the /opt/OMC/var/logs/tracebak directory. If the number of trace files in the tracebak folder exceeds the threshold, the system deletes the oldest trace files. l Clear the backup files.

After the upgrade, delete the backup files for the upgrade or copy them to tapes. Back up all the files in the /export/home/backup/omc directory to tapes.
Delete the files that are no longer in use. Before clearing disk space, ensure that the files to be deleted are no longer required. Deleting a useful file by mistake may lead to a system failure. 1. 2. 3. Choose Start > Program > iManager M2000 Client > M2000 Log Information Collector . In the displayed M2000 Log Information Collector dialog box, select Core files in server. Click Collect. Save the collected core files to the path c:\Program Files\client\diagnosis\collected files. c:\Program Files is the default installation path of the M2000 client software.
Issue 05 (2008-05-20)
9-11
CAUTION
l
The M2000 log information collector collects the stack information from the core files. In addition to the stack information, the core files also include other information. Therefore, before deleting the core files, confirm the deletion with Huawei engineers. Because the size of the core files is large, you must compress the core files before sending them.
4. l
After sending all the core files and the stack files to Huawei for confirmation, delete the core files and stack files that are no longer required.
Clear the remaining data after the deletion of NEs. After the deletion of an NE, the NE-related performance file and the configuration result file remain on the server. If you do not clear these files in time, they still occupy much disk space. The following two methods are used to clear the remaining data after the deletion of NEs:

When you delete an NE, clear the configuration and performance files related to an NE. Clear the disk regularly to delete the configuration and performance files related to an NE.
Clear up the remaining data after the deletion of an NE. 1. 2. Log in to the M2000 server as user dbuser. Change to the Sybase installation directory. By default, the installation directory is /opt/sybase. -bash-3.00$ cd /opt/sybase 3. Run the environment variable. -bash-3.00$ . .profile 4. Access the Sybase database, run the following command, and then find out the NErelated FDN from the data list: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> use omcdb 2> go 1> select fdn,neName from tbl_AllNeInfo where neName='Name of NE' 2> go
9-12
Issue 05 (2008-05-20)

NOTE
Assuming that the FDN of an NE named testne is found out, run the following command: 1> select fdn,neName from tbl_AllNeInfo where neName='testne' 2> go
fdn neName
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.3221229568.3221233664.3221282832 testne
(1 row affected)
The displayed information shows that the FDN of the NE is 0.1.5. 5. Switch to log in as user omcuser. 1> exit -bash-3.00$ su - omcuser Password: Password of omcuser 6. 7. Change to the directories /export/home/sysm/ftproot/Cm/ and /export/home/sysm/ ftproot/pm/ to delete the folder where the FDN of the deleted NE is located. Switch to log in as user root. -bash-3.00$ su - root Password: Password of root 8. Change to the /opt/OMC/var/med directory to delete the folder where the FDN of the deleted NE is located.
Clear up disks regularly.

1. 2.
Log in to the M2000 server as user dbuser. Change to the Sybase installation directory. By default, the installation directory is /opt/sybase. -bash-3.00$ cd /opt/sybase
3.
Run the environment variable. -bash-3.00$ . .profile
4.
Access the Sybase database and run the following commands: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> use omcdb 2> go 1> select fdn,neName from tbl_AllNeInfo 2> go
NOTE
dbuser 15745 15744 3 11:00:39 ? 2:19 /opt/sybase/ASE-15_0 /bin/dataserver -sSYB -d/data/master.dat -e/opt/sybase/ASEfdn neName
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.3221229568.3221233664.3221282825 MSC_jjh .3221229568.3221233664.3221282826 RNC_lnt .3221229568.3221233664.3221282824 gt_SGSN
9-14
Issue 05 (2008-05-20)

.3221229568.3221233664.3221282832 testne .3221229568.3221233664.3221282851 MSC_ZHU .3221229568.3221233664.3221282852 MSC_BAK .3221229568.3221233664.3221282830 msc_lq .3221229568.3221233664.3221282819 test_MSCServer
(8 rows affected)
5.
Switch to log in as user omcuser. 1> exit -bash-3.00$ su - omcuser Password: Password of omcuser
6. 7.
Change to the directories /export/home/sysm/ftproot/Cm/ and /export/home/sysm/ ftproot/pm/ to delete the folders of associated FDNs that are not listed in the database. Switch to log in as user root. -bash-3.00$ su - root Password: Password of root
8. ----End
Change to the /opt/OMC/var/med directory to delete the folders of associated FDNs that are not listed in the database.
Issue 05 (2008-05-20)
9-15
10 Backing Up and Restoring the M2000
10
Backing Up and Restoring the M2000
About This Chapter

This describes how to back up and restore M2000 data. 10.1 M2000 Backup and Restore Solutions This describes the backup and restore solutions of the M2000. Depending on the data to be backed up, three data backup solutions are provided for the M2000. 10.2 Backing Up and Restoring M2000 Dynamic Data This describes how to back up and restore M2000 dynamic data. 10.3 Backing Up and Restoring M2000 Static Data This describes how to back up and restore the M2000 static data. 10.4 Backing Up and Restoring M2000 System Data This describes how to back up and restore the M2000 system data.
Issue 05 (2008-05-20)
10-1
10.1 M2000 Backup and Restore Solutions

This describes the backup and restore solutions of the M2000. Depending on the data to be backed up, three data backup solutions are provided for the M2000. Dynamic data backup: backs up the dynamic service data of the M2000 system. Static data backup: backs up the M2000 server application software, database application software, database device files, and M2000 configuration files on the hard disks of the M2000 server. System data backup: backs up the system data of the M2000 server, such as operating system data, database application data, M2000 server application data. 10.1.1 Backup of M2000 Dynamic Data This describes the backup of the M2000 dynamic data. 10.1.2 Backup of M2000 Static Data The describes the backup contents, backup modes, and storage media of the M2000 static data. 10.1.3 Backup of M2000 System Data This describes the backup of the M2000 system data. The M2000 system data backup refers to the backup of the operating system of the M2000 server. 10.1.4 Policies of M2000 Data Backup Based on the backup scenarios, rules for naming backup files, and rules for naming backup tapes, this describes how to back up the M2000 system. 10.1.5 Scenarios of M2000 Data Restoration You can select different data restore solutions according to the scenarios.
10.1.1 Backup of M2000 Dynamic Data

This describes the backup of the M2000 dynamic data. Dynamic data backup refers to the backup of the M2000 dynamic service data. It is used to restore the history data when the M2000 is running properly. For details about the backup contents, backup modes, and storage media of the dynamic data backup, see Table 10-1. Table 10-1 Introduction to dynamic data backup Item Backup Contents Contents
l
Database data: omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, pmcomdb, sumdb, omcsmdb, and omctmdb. M2000 system files: files under the /export/home/omc/var, /export/ home/sysm/devdoc, and /export/home/sysm/ftproot directories.
l The configuration files related to the static data are stored in the /export/home/
NOTE omc/var directory. Thus, do not delete the directory.

l If the PRS is not configured on the M2000 system, the sumdb database does not
exist.
l When backing up the M2000 system files, the system does not back up the log
files and Trace files in the previous directories.
10-2
Issue 05 (2008-05-20)
Item Backup modes
Contents Periodic backup After the periodic backup is activated, perform the periodic backup once every day. Perform the full backup on the specified day of each week. On the other six days, automatically perform incremental backup at the same time. After a new round of periodic backup is performed, all the backup files of the previous round are deleted automatically.
NOTE Backing up dynamic data consumes system resources. Thus, the time set for backup should be at night when the system traffic is light.
Manual backup
Full backup: backs up all the dynamic data. When a new full backup is performed, all the backup files in the backup directory are deleted automatically. Perform full backup according to your requirements. Incremental backup: backs up the dynamic data that has changed since the last full backup. The incremental backup is saved in another file, without overwriting the file of full backup. Perform incremental backup according to your requirements.
Storage device
l l l l
Tape Hard disk Tape and hard disk Storage device of the NetBackup server
The directory of backup files
/export/home/backup/omc
After the backup is performed, the backup contents are automatically packaged as a backup file. For details about how to name a backup file, see Rules for Naming Backup Files of Dynamic Data.
NOTE
When the M2000 system performs the dynamic data backup, do not perform operations such as modifying the configuration database.
10.1.2 Backup of M2000 Static Data

The describes the backup contents, backup modes, and storage media of the M2000 static data. To back up the M2000 static data, you need to back up the data in the /opt/OMC and /opt/ sybase directories and the data in the /export/home partition on the M2000 server. The backup of the M2000 static data is used to restore the static data of the original database or the M2000 application.
For details about the backup contents, backup modes, and storage media of the static data backup, see Table 10-2. Table 10-2 Introduction to the static data backup Item Backup Contents Contents
l l l l
M2000 server application software Database application software Database device files M2000 configuration files /opt/sybase directory /opt/OMC directory /export/home directory
Partition of backup data
l l l
Backup modes
One-time backup In general, the previous data need not be backed up again after the initial backup. You must back up the data again after upgrading the database program, expanding the database, or upgrading the M2000 application software. Tape Generally, a 36/72 GB tape is required for the backup. You can select a tape type according to the actual partition size.
NOTE A tape with 36/72 GB capacity means that it can store 36 GB data basically while up to 72 GB data when compressed.
Storage device Number of the tapes required for backup
10.1.3 Backup of M2000 System Data

This describes the backup of the M2000 system data. The M2000 system data backup refers to the backup of the operating system of the M2000 server. The M2000 system data backup refers to the backup of the operating system of the M2000 server. For details about the backup contents, backup modes, and storage media of the system data backup, see Table 10-3. Table 10-3 Introduction to system data backup Item Backup Contents Partition of backup data Contents Data of the operating system / partition
10-4
Issue 05 (2008-05-20)
Backup modes
One-time backup If the operating system is not upgraded or the M2000 is upgraded across R versions, another backup is not required after you perform the initial backup of the data. If you plan to upgrade the operating system (for example, installing the patches of the operating system) or install the M2000 across R versions, you need to back up the operating system again. Tape In general, a 36/72 GB tape is required.
NOTE
l Run the df -h / command to view the size of the / partition. l A tape with 36/72 GB capacity means that it can store 36
Storage device The number of tapes required for backup
GB data basically while up to 72 GB data when compressed.
10.1.4 Policies of M2000 Data Backup

Based on the backup scenarios, rules for naming backup files, and rules for naming backup tapes, this describes how to back up the M2000 system.
Typical Scenarios for M2000 Data Backup

Table 10-4 describes the typical scenarios for M2000 data backup. Table 10-4 Typical scenarios for M2000 data backup No. 1 Scenario Description The M2000 system is installed for the first time. Data
l
Backup of dynamic data (manually back up dynamic data to tapes) Back up of static data Backup of the operating system data Backup of dynamic data (manually back up dynamic data to tapes) Back up of static data
l l
The M2000 program is upgraded, or the database is upgraded or expanded. For example, a patch of the operating system is installed. After the M2000 programs are upgraded on the basis of the R version.
Backup of the operating system data
Routine backups
Dynamic data backup (periodic backup)
Issue 05 (2008-05-20)
10-5

NOTE
Structure of the M2000 issue number: product name + VxxxRxxxCxxBxxy[SPxx]. Vxxx (version) refers to a certain product or products of a certain series. A product is classified into multiple V versions. Each V version has a general development plan. According to the plan, multiple R (release) versions are developed. Rxxx (Release) version refers to the version of product features. Multiple features consist a specific series of products. A series of products may have their own feature versions. You can use special letters or numbers to represent the feature versions. Cxx refers to the customer-delivered feature subset version under the R version. Bxxy (Build) refers to the Build version during the development. SPxx (Service Pack) refers to the version of patch. After the M2000 is upgraded on the basis of the R version, for example, the M2000 is upgraded from V200R003 to V200R006, the operating system files may change significantly. Therefore, you must back up the operating system data after the upgrade.
Rules for Naming Backup Files of Dynamic Data

When backing up the static data, name the backup files in the following format: /export/home/ backup/omc/*-YYYYMMDDhhmmss.tar, where, * indicates all for full backup or inc for incremental backup. For example:
l
The file name all-20040601042002.tar refers to a full backup file generated on 2004-06-01 04:20:02. The file name inc-20040602042001.tar refers to an incremental backup file generated on 2004-06-02 04:20:01.
NOTE
l l
The latest backup information is recorded in the /export/home/backup/omc/backup.log file. During the backup process, the inc-YYYYMMDDhhmmss or all-YYYYMMDDhhmmss folder is generated in the /export/home/backup/omc path for storing backup files. When the backup is complete, the folder is packed as the inc-YYYYMMDDhhmmss.tar file, and the incYYYYMMDDhhmmss or all-YYYYMMDDhhmmss folder is automatically deleted.
Rules for Naming the Tapes That Store the Backup Data
The rule for naming a backup tape is as follows: *backup tape (backup date). The character * stands for the following data:
l l l
Dynamic data Static data Data of the operating system
For example, if a tape is labeled "static data backup tape (2007-11-28)", you can infer that the static data backup is performed on November 28, 2007.
10.1.5 Scenarios of M2000 Data Restoration

You can select different data restore solutions according to the scenarios. Table 10-5 describes the data restore solutions for typical scenarios.
10-6
Issue 05 (2008-05-20)
Table 10-5 Data restore solutions for typical scenarios No. 1 Scenario Description The M2000 system runs normally. It needs to roll back to the historical operational status such as the operational status of the last week. The database device or the configuration files of the M2000 are damaged. The operating system of the M2000 server, however, is still running properly. A serious fault occurs on the M2000 server. The operating system of the M2000 server cannot be started. Data Restore Solution Restore dynamic data.
Restore static data. You must also perform the procedure for restoring dynamic data.
Restore the operating system. You need to restore the static data and the dynamic data.
10.2 Backing Up and Restoring M2000 Dynamic Data

This describes how to back up and restore M2000 dynamic data. 10.2.1 Backup of M2000 Dynamic Data This describes the backup of the M2000 dynamic data. 10.2.2 Setting the Storage Device of Backup Data This describes how to set the storage device of backup data. 10.2.3 Setting the Wait Time for Replacing a Tape You can store the dynamic data on multiple tapes. If the current tape is fully written, the system automatically ejects the tape and waits you to replace it. By modifying the configuration file, you can set the wait time. 10.2.4 Backing Up M2000 Dynamic Data Periodically This describes how to periodically back up the M2000 dynamic data. 10.2.5 Backing Up M2000 Dynamic Data Manually This describes how to manually back up the M2000 dynamic data. 10.2.6 Restoring M2000 Dynamic Data This describes how to restore M2000 dynamic data. restoring
10.2.1 Backup of M2000 Dynamic Data

This describes the backup of the M2000 dynamic data.
Issue 05 (2008-05-20)
10-7
Dynamic data backup refers to the backup of the M2000 dynamic service data. It is used to restore the history data when the M2000 is running properly. For details about the backup contents, backup modes, and storage media of the dynamic data backup, see Table 10-6. Table 10-6 Introduction to dynamic data backup Item Backup Contents Contents
l
Database data: omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, pmcomdb, sumdb, omcsmdb, and omctmdb. M2000 system files: files under the /export/home/omc/var, /export/ home/sysm/devdoc, and /export/home/sysm/ftproot directories.
l The configuration files related to the static data are stored in the /export/home/
NOTE omc/var directory. Thus, do not delete the directory.

l If the PRS is not configured on the M2000 system, the sumdb database does not
exist.
l When backing up the M2000 system files, the system does not back up the log
files and Trace files in the previous directories.
Backup modes
Periodic backup
After the periodic backup is activated, perform the periodic backup once every day. Perform the full backup on the specified day of each week. On the other six days, automatically perform incremental backup at the same time. After a new round of periodic backup is performed, all the backup files of the previous round are deleted automatically.
NOTE Backing up dynamic data consumes system resources. Thus, the time set for backup should be at night when the system traffic is light.
Manual backup
Full backup: backs up all the dynamic data. When a new full backup is performed, all the backup files in the backup directory are deleted automatically. Perform full backup according to your requirements. Incremental backup: backs up the dynamic data that has changed since the last full backup. The incremental backup is saved in another file, without overwriting the file of full backup. Perform incremental backup according to your requirements.
Storage device
l l l l
Tape Hard disk Tape and hard disk Storage device of the NetBackup server
The directory of backup files
/export/home/backup/omc
10-8
Issue 05 (2008-05-20)
After the backup is performed, the backup contents are automatically packaged as a backup file. For details about how to name a backup file, see Rules for Naming Backup Files of Dynamic Data.
NOTE
When the M2000 system performs the dynamic data backup, do not perform operations such as modifying the configuration database.
10.2.2 Setting the Storage Device of Backup Data

This describes how to set the storage device of backup data.
Prerequisite
Log in to server as user root.
Context
The backup files for the dynamic data backup are stored on hard disks. To store the backup files on a tape, you need to modify the relevant settings in the maintainsvc.xml file. You can configure the storage device of backup data when the M2000 is running.
CAUTION
l l
Do not modify the storage device file when the backup is in process. When you perform a full backup, the backup overwrites the backup files that already exist on the disk. After you change the current storage device, for example, from a disk to a tape, you must perform a full backup again. Otherwise, dynamic data may fails to be restored owing to the loss of certain backup data. If you set the backupMedia parameter to tape or all, replace the tape after the backup is complete. Do not replace the storage device during the backup process. For data security, back up the dynamic data to a tape. When restoring the static data and the system, use the dynamic data backup files stored on the tape to restore the latest service data.
l l l
Procedure
Step 1 Ensure that the M2000 daemon process is started. Run the following command to check whether the M2000 daemon process is started. # . /opt/OMC/svc_profile.sh # daem_ps
Result of the daem_ps Command Then... The command result is displayed. The M2000 daemon process is started. Perform Step 2. The M2000 daemon process is not started. Run the following command to start it. # start_daem Step 2 Navigate to the /export/home/omc/var/etc/conf directory, and then run the vi command to view the maintainsvc.xml file. # cd /export/home/omc/var/etc/conf # vi maintainsvc.xml Step 3 Locate the line <param name="backupMedia">, and then change the disk for both the full and incremental backups to the actual storage device.
<module name="all"> <param name="backupMedia">disk</param>
No command result is displayed.
and
<module name="inc"> <param name="backupMedia">disk</param>
Table 10-7 lists the values for the backupMedia parameter. Table 10-7 Values for the backupMedia parameter Storage Device Hard disks Tapes Hard disks and tapes Storage device of the NetBackup server Value disk tape all veritas
NOTE
If backupMedia is set to veritas, the system automatically packs the backup data and moves the backup data to the storage media of the NetBackup server. As a result, the M2000 server does not keep any backup data. he storage device of the NetBackup server is determined by the Veritas backup and restore solution. It can be a tape drive, tape library, or disk.
Step 4 To back up dynamic data on a tape, specify the path of the tape drive. To back up the dynamic data on the disk, go to Step 5. Find the following lines:

<path name="backuppath"> <param name="tapePath">/dev/rmt/0</param> </path>
Replace /dev/rmt/0 with the path of the tape drive in the system.
NOTE
If multiple tape drives are installed on the server, select a tape drive by referring to 15.1.4 How to Select the Tape Drive.
Step 5 Save the file and quit. Step 6 Run the following command to load the configuration files of all the processes again. # svc_adm -cmd reload ----End
10.2.3 Setting the Wait Time for Replacing a Tape

You can store the dynamic data on multiple tapes. If the current tape is fully written, the system automatically ejects the tape and waits you to replace it. By modifying the configuration file, you can set the wait time.
Prerequisite
Log in to server as user root.
Context
If multiple tapes are required for data backup, you can modify the relevant contents in the maintainsvc.xml file to set the wait time for replacing a tape. You can configure the storage device of backup data when the M2000 is running.
CAUTION
Do not set the wait time for replacing a tape when the backup is in progress.
Procedure
Step 1 Ensure that the M2000 daemon process is started. Run the following command to check whether the M2000 daemon process is started. # . /opt/OMC/svc_profile.sh # daem_ps Result of the daem_ps Command Then... The command result is displayed. The M2000 daemon process is started. Perform Step 2.
Issue 05 (2008-05-20)
10-11
Result of the daem_ps Command Then... No command result is displayed. The M2000 daemon process is not started. Run the following command to start it. # start_daem Step 2 Navigate to the /export/home/omc/var/etc/conf directory, and then run the vi command to view the maintainsvc.xml file. # cd /export/home/omc/var/etc/conf # vi maintainsvc.xml Step 3 Locate the line <change_tape_time name="change_tape_time"> and set the wait time for replacing a tape.
<change_tape_time name="change_tape_time"> <param name="interval">120</param> </change_tape_time>
The value of the interval parameter indicates the wait time, which is represented in minutes. The default wait time is 120 minutes. Step 4 Save the file and quit. Step 5 Run the following command to load the configuration files of all the processes again. # svc_adm -cmd reload ----End
10.2.4 Backing Up M2000 Dynamic Data Periodically

This describes how to periodically back up the M2000 dynamic data.
Prerequisite
l l l l
You have logged in to the M2000 client. You have the relevant operation privileges. The tape drive is connected properly. It holds a tape if you plan to back up data on the tape. A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Generally, M2000 dynamic data is backed up periodically. The periodic backup of the dynamic data is performed in full backup mode. Dynamic data backup has no restriction on backup time. The backup can be performed during the system operation.
Procedure
Step 1 On the main window, choose Maintenance > Task Management.
The Centralized Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup in the navigation tree and double-click the node. The Attribute dialog box of server periodic backup is displayed, as shown in Figure 10-1. Figure 10-1 Periodic backup
Issue 05 (2008-05-20)
10-13
10-14
Issue 05 (2008-05-20)

NOTE
----End
10.2.5 Backing Up M2000 Dynamic Data Manually

This describes how to manually back up the M2000 dynamic data.
Prerequisite
l l l l
You have logged in to the M2000 client. You have the relevant operation privileges. The tape drive is connected properly. It holds a tape if you plan to back up data on the tape. A hard disk has sufficient free space if you plan to back up data on the hard disk.
Context
Manual backup is required in special or emergency situations, such as the loss of backup tapes or the failure of the M2000 system. Manual backup can be full backup or incremental backup. Dynamic data backup has no restriction on backup time. The backup can be performed during the system operation.
Procedure
Step 1 On the main window, choose Maintenance > Backup Management. The Backup Management dialog box is displayed.
Issue 05 (2008-05-20)
10-15
Figure 10-3 Manual backup
Step 2 On the Server Backup List tab page, as shown in Figure 10-3, click Full Backup to perform full backup. Click Incremental Backup to perform incremental backup.
NOTE
Full backup must be performed before incremental backup. Incremental backup must be performed based on full backup.
Step 3 If data is backed up on a tape and the tape is fully written during the backup, perform Step 4 through Step 5 to replace the tape with a new tape. Step 4 The system automatically ejects the fully written tape and waits you to replace the tape. As shown in Figure 10-3, the Information field in the Backup Management dialog box displays the following message: The current tape is fully written. Please replace it with another tape as soon as possible. Step 5 Insert a new tape into the tape drive. The Information field in the Backup Management dialog box displays the following message: The tape has been placed in the tape drive. Please resume the backup operation. After you insert a new tape, the system continues to back up the M2000 dynamic data.
NOTE
If you do not replace the fully written tape within the wait time preset in the configuration file, the Information field in the Backup Management dialog box displays the following message: Tape replacement times out. The data backup fails. In such a case, you need to insert a tape into the tape drive and performs a new full backup. If the newly inserted tape is fully written again, you need to insert another tape for backup. In this way, change tapes until all the data is backed up.
----End
10.2.6 Restoring M2000 Dynamic Data

This describes how to restore M2000 dynamic data. restoring
Prerequisite
l l l l
You have logged in to server as user root. You have obtained the backup files for restoring the M2000 dynamic data. The backup log file backup.log is stored on a tape or a disk. The M2000 is operational.
Context
Based on the latest full backup files and incremental backup files of the M2000, you can restore the M2000 system. After you restore the M2000 system, all the contents in the backup file package are restored. If some data, such as the NE performance data or alarm data, is not packed in the backup file package, the M2000 starts the automatic synchronization function to obtain and handle the data. During the restoration of the dynamic data, the M2000 services are stopped and thus the NE performance or alarm data cannot be handled.
Procedure
Step 1 If the M2000 service is running, stop it first. The default M2000 installation directory is /opt/ OMC. # cd /opt/OMC # . ./svc_profile.sh # stop_svc Step 2 Ensure that the M2000 daemon process is started. Run the following command to check whether the M2000 daemon process is started. # . /opt/OMC/svc_profile.sh # daem_ps Result of the daem_ps Command Then... The command result is displayed. The M2000 daemon process is started. Perform Step 2. The M2000 daemon process is not started. Run the following command to start it. # start_daem Step 3 Skip this step and go to Step 5 if the backup files are stored on a hard disk. Copy the backup files to a hard disk if the backup files are stored on a tape.
No command result is displayed.
Insert the first tape that stores the dynamic data and run the following command: # gtar xvPfM /dev/rmt/0
CAUTION
l
If more than one tape drive is available on the server, enter the name of the tape drive that is used for backing up the dynamic data. The decompressed file must be stored in the same path as the compressed one. It is not related to the path where you perform the decompression operation.
Step 4 If all the data is stored on the first tape, perform Step 5 after the previous command is run. Otherwise, decompress the data on the tape to a hard disk. 1. Press the button on the tape drive to eject the tape when the following information is displayed. For details, refer to the delivery-attached manual of the tape drive. Prepare volume #2 for '/dev/rmt/0' and hit return:
NOTE
You can also eject the tape by opening a new remote login window and then running the following command: # mt -f /dev/rmt/0 offline
2.
After replacing the first tape with the second tape, press Enter to decompress data on the second tape to a hard disk. Press Ctrl+C to exit if the following message is displayed: gtar: 'export/home/backup/omc/all-20080130180622.tar' is not continued on this volume Then, run the following command to decompress data again: # gtar xvPfM /dev/rmt/0
If you need to restore data from the third tape, the system prompts you to insert the third tape. Insert other tapes in this way as the system prompts you. Prepare volume #3 for '/dev/rmt/0' and hit return: After all the data on tapes are decompressed to a hard disk, perform Step 5. Step 5 Switch to user dbuser and restart the Sybase. Then, switch to user root. # su - dbuser For details about how to the Sybase, see 15.2.3 How to Stop the Sybase. To start the Sybase, refer to 15.2.2 How to Start the Sybase. -bash-3.00$ exit Step 6 Restore the dynamic data. # svc_backuprestore -cmd restore -s MaintenanceService The following message is displayed:
****************************************************** * Restore is a dangerous operation ! * * If you have to do it, please stop system first ! * ****************************************************** Continue ?[n/y]
Enter y and start the restoration. After the restoration is complete, the system displays the message restore successfully! Step 7 Restart the M2000 services. # start_svc Step 8 Ensure that all the M2000 services are started. # svc_adm -cmd status Check the value after Not Running : in the last line. If the value is 0, you can infer that all the M2000 services are started. In this case, the data restoration is complete. ----End
10.3 Backing Up and Restoring M2000 Static Data

This describes how to back up and restore the M2000 static data. 10.3.1 Backup of M2000 Static Data The describes the backup contents, backup modes, and storage media of the M2000 static data. 10.3.2 Backing Up M2000 Static Data This describes how to back up the M2000 static data. After backing up the M2000 dynamic data, you need to back up the M2000 static data so that the M2000 can be recovered in case the M2000 or the Sybase is damaged. Backing up the static data decreases the performance of the M2000. 10.3.3 Restoring M2000 Static Data This describes how to restore the M2000 static data.
10.3.1 Backup of M2000 Static Data

The describes the backup contents, backup modes, and storage media of the M2000 static data. To back up the M2000 static data, you need to back up the data in the /opt/OMC and /opt/ sybase directories and the data in the /export/home partition on the M2000 server. The backup of the M2000 static data is used to restore the static data of the original database or the M2000 application. For details about the backup contents, backup modes, and storage media of the static data backup, see Table 10-8.
Issue 05 (2008-05-20)
10-19
Table 10-8 Introduction to the static data backup Item Backup Contents Contents
l l l l
M2000 server application software Database application software Database device files M2000 configuration files /opt/sybase directory /opt/OMC directory /export/home directory
Partition of backup data
l l l
Backup modes
One-time backup In general, the previous data need not be backed up again after the initial backup. You must back up the data again after upgrading the database program, expanding the database, or upgrading the M2000 application software. Tape Generally, a 36/72 GB tape is required for the backup. You can select a tape type according to the actual partition size.
NOTE A tape with 36/72 GB capacity means that it can store 36 GB data basically while up to 72 GB data when compressed.
Storage device Number of the tapes required for backup
10.3.2 Backing Up M2000 Static Data

This describes how to back up the M2000 static data. After backing up the M2000 dynamic data, you need to back up the M2000 static data so that the M2000 can be recovered in case the M2000 or the Sybase is damaged. Backing up the static data decreases the performance of the M2000.
Prerequisite
l l l
The solution is applicable to all the M2000 systems that are installed with Solaris 10. Keep the required tapes for system data backup ready. The magnetic head of the tape drive is clean. If the tape drive is externally connected, ensure that the connection between the tape drive and the M2000 server is proper. You have logged in to the server as user root. You have decompressed the PlatformTools installation package to the /opt directory on the M2000 server. For details on how to obtain the PlatformTools, refer to Obtaining the M2000 Software Package.
l l
Context
The static data backup is used for recovering the M2000 system in case the system incurs a severe damage, for example, the damage to the M2000 or Sybase application software, the physical damage to databases, or the disk failure of database bare devices.
You can back up the M2000 static data when the M2000 is running. The data backup, however, decreases the performance of the M2000. It is recommended that you perform the backup when the M2000 is stopped or the traffic is light. This part takes the backup of the static data on the stopped M2000 for example.
Procedure
Step 1 Back up the dynamic data. For details, refer to 10.2.5 Backing Up M2000 Dynamic Data Manually. Step 2 If the M2000 services and the Sybase are running, stop the M2000 services and the Sybase. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. # su - dbuser For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. -bash-3.00$ exit Step 3 Insert a tape into the tape drive, and then run the following command to rewind the tape: # mt -f /dev/rmt/0 rewind Store the backup files in two tapes if one tape cannot hold the backup files. Step 4 Delete extra files if the backup is not performed immediately after the initial installation of the M2000. Skip this step and go to Step 5 if the backup is performed immediately after the initial installation of the M2000.
NOTE
If these files are still required, move these files to another folder. Move them back when the backup is complete.
l
To delete the alarm dump files, run the following commands: # cd /export/home/omc/var/fm/dump # rm -R /export/home/omc/var/fm/dump/event/* # rm -R /export/home/omc/var/fm/dump/history/*
To delete the core files, run the following commands: # cd /export/home/omc/var/logs # rm core*
To delete the history trace files, run the following commands: # cd /export/home/omc/var/logs/tracebak # rm iMAP*
Step 5 Back up the M2000 application. # cd /opt # ufsdump 0ucf /dev/rmt/0n OMC Step 6 Back up the Sybase application. # ufsdump 0ucf /dev/rmt/0n sybase
Step 7 Back up the M2000 configuration files and the device files of the Sybase. # cd / # ufsdump 0ucf /dev/rmt/0n /export/home
NOTE
The device files of the Sybase are master.dat, sysprocs.dat, and tmp_dev. The three files are stored in the path /export/home/sybdev.
Step 8 Check whether the static backup data on the tape is valid. If the static backup data is backed up on multiple tapes, check the tapes one by one. 1. Rewind the tape. # mt rewind 2. The contents of the first record on the tape are displayed. # ufsrestore tf /dev/rmt/0n 3. The contents of the second record on the tape are displayed. # ufsrestore tf /dev/rmt/0n If the previous two records do not contain error information such as Media read error: I/O error, you can infer that the data backup is valid. Step 9 Remove the tape from the tape drive. Step 10 Start the M2000 services and the Sybase. For details about how to start the Sybase, refer to 15.2.2 How to Start the Sybase. For details about how to start the M2000, refer to 7.3.3 Starting M2000 Services. ----End
10.3.3 Restoring M2000 Static Data

This describes how to restore the M2000 static data.
Prerequisite
l l
Log in to server as user root. The remaining M2000 applications and database files (such as the files in /opt/OMC and /export/home) have been deleted from the system. The tape storing the backup static data has been inserted into the tape drive. The communication between the PC and the M2000 server is normal. You have decompressed the PlatformTools installation package to the /opt directory on the M2000 server. For details on how to obtain the PlatformTools, refer to Obtaining the M2000 Software Package.
l l l
Context
If the M2000 applications are lost or the disk storing the database raw device breaks down owing to severe system damage, you must perform the following steps to restore the static data.
Procedure
Step 1 If the M2000 services and the Sybase server are running, stop the M2000 services and the Sybase. For details on how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. # su - dbuser For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. -bash-3.00$ exit Step 2 Check whether the raw volume or the disk raw partition used by the data device functions well.
NOTE
Before you rebuild the subscriber database, ensure that the raw volume or disk raw partition used by the data device functions well.
l l
In the case of Netra 240 single-server system, the raw volume used by the data device is created after you use the PlatformTools to encapsulate and mirror the operating system. For other cases, you need to use the PlatformTools to separately create volumes.
If the M2000 server uses Netra 240 and root disks are encapsulated with Solaris Volume Manager, perform the following steps: # metastat metastatIn the command result, check whether each Mirror contains two Submirror and whether the value of each State is Okay. If the M2000 server uses the V890 server or the E4900 server and root disks are encapsulated with the Veritas Volume Manager, perform the following steps: 1. Check whether the raw volume or the disk raw partition used by the data device is available and functions well. # vxprint If the omcdb_data_lv001 and omcdb_log_lv003 are displayed, you can infer that the raw volume exists. Each volume (v) in the system output contains the values of STATE and KSTATE. If the value of STATE is ACTIVE and the value of KSTATE is ENABLED, you can infer that the raw volume or the disk raw partition used by the data device functions well. 2. Check whether the exporthome volume on the disk array is attached to the /export/home path. # df -k
Filesystem /dev/md/dsk/d100 /devices ctfs proc mnttab swap objfs swap swap swap swap /dev/md/dsk/d115 kbytes used avail capacity 17146994 10792168 6183357 64% 0 0 0 0% 0 0 0 0% 0 0 0 0% 0 0 0 0% 5210736 1240 5209496 1% 0 0 0 0% 5209808 312 5209496 1% 5209528 32 5209496 1% 5209496 0 5209496 0% 5209496 0 5209496 0% 1020815 458280 501287 48% Mounted on / /devices /system/contract /proc /etc/mnttab /etc/svc/volatile /system/object /tmp /var/run /dev/vx/dmp /dev/vx/rdmp /globaldevices
Issue 05 (2008-05-20)
10-23

/dev/vx/dsk/ossdg/exporthome 18578778 9987956 8405035
55%
/export/home
In the previous system output, you must ensure that a disk device is mounted on the /export/ home directory. In this example, the disk device is /dev/vx/dsk/ossdg/ exporthome. In this example, ossdg is the name of a disk group. You can run the vxdisk list command to view the actual name of the disk group. Step 3 Insert a tape into the tape drive. Step 4 Check whether the static backup data on the tape is valid. If the static backup data is backed up on multiple tapes, check the tapes one by one. 1. Rewind the tape. # mt rewind 2. The contents of the first record on the tape are displayed. # ufsrestore tf /dev/rmt/0n 3. The contents of the second record on the tape are displayed. # ufsrestore tf /dev/rmt/0n If the previous two records do not contain error information such as Media read error: I/O error, you can infer that the data backup is valid. Step 5 Rewind the tape. If the static backup data is stored on multiple tapes, insert the first tape on which the static backup data is stored, and then rewind the tape. # mt -f /dev/rmt/0 rewind Step 6 Restore the M2000 application. # cd / # rm -R /opt/OMC # ufsrestore rf /dev/rmt/0n When the system displays the following prompt, ignore it.
./lost+found: (inode 3) not found on volume ./.dt: (inode 228133) not found on volume ./export: (inode 5) not found on volume ./globaldevices: (inode 7) not found on volume ./.dtprofile: (inode 2446) not found on volume ./var: (inode 10) not found on volume ./usr: (inode 32) not found on volume ./bin: (inode 1427) not found on volume ./dev: (inode 1480) not found on volume ./etc: (inode 1481) not found on volume ./lib: (inode 1586) not found on volume ./mnt: (inode 1594) not found on volume Warning: ./opt: File exists ./opt/SUNWits: (inode 37499) not found on volume ./opt/SUNWmlib: (inode 137424) not found on volume ./opt/SUNWrtvc: (inode 164893) not found on volume ./opt/sun: (inode 221695) not found on volume ./opt/CTEact: (inode 221705) not found on volume ./opt/SUNWexplo: (inode 221764) not found on volume ./opt/SUNWsneep: (inode 221704) not found on volume ./opt/initvol1.2.tar: (inode 2441) not found on volume
10-24
Issue 05 (2008-05-20)

./opt/sybase: (inode 233071) not found on volume ...
Step 7 Restore the Sybase application. # rm -R /opt/sybase # ufsrestore rf /dev/rmt/0n Step 8 Restore the M2000 configuration files, the Sybase application, and the device files of the Sybase.
NOTE
Before restoring the M2000 configuration file, delete the files that are not required in the /export/home directory to increase the hard disk space.
# cd /export/home # ufsrestore rf /dev/rmt/0n # rm restoresymtable Step 9 Start the Sybase as user dbuser.
CAUTION
l
You must start the Sybase as user dbuser. In this case, the owner of a created database device is user dbuser, and you can start the Sybase as user dbuser in the future. During the startup of the Sybase, if the system displays the message indicating that the device associated with the subscriber database cannot be found, you can ignore the message.
For details about how to start the Sybase, refer to 15.2.2 How to Start the Sybase. Step 10 Check the status of the database. -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpdb 2> go
NOTE
If all the user databases exist and the status of each database is not offline or not recovered, you need not establish the database again. That is, you need not perform Step 11 through Step 14. You can perform Step 15 directly to restore the dynamic data. Switch back to log in as user root. 1> exit
-bash-3.00$ exit Step 11 Run the PlatformTools to rebuild an application database. 1. To configure the rights of the PlatformTools directory, run the following command: # chmod -R 777 /opt/PlatformTools 2. Start the PlatformTools. # cd /opt/PlatformTools # ./setup
NOTE
After you start the PlatformTools, you can enter R on the system interface to return to the upperlevel menu or enter Q to quit the tool.
3.
When the system displays the following prompt, enter 2:

============================================================= Please choose the operation type 1--Installation 2--Maintenance Q--Exit ============================================================= Please make a choice :
4.
When the system displays the following prompt, enter 3 to choose OMC database manipulations:
============================================================= 1--Backup OS 2--Restore OS 3--OMC database manipulations R--Return Q--Exit ============================================================= Please make a choice:
5.
When the system displays the following prompt, enter 1 to choose Rebuild OMC database:
============================================================= 1--Rebuild OMC database 2--Remove OMC database R--Return Q--Exit ============================================================= Please make a choice:
6.
When the system displays the following prompt, enter y to start rebuilding the subscriber database:
============================================================= NOTE: If you only want to remove user databases, don't choose this operation. Before you continue, you must have sybase system databases restored. Stop all M2000 services, and make sure sybase dataserver is online. Do you want to continue? [y/n]
7.
When the system displays the following prompt, enter the name of the database server.
10-26
Issue 05 (2008-05-20)

NOTE
dbuser 15745 15744 3 11:00:39 ? 2:19 /opt/sybase/ASE-15_0 /bin/dataserver -sSYB -d/data/master.dat -e/opt/sybase/ASEPlease input Database server:
8.
When the system displays the following prompt, enter the name of the database administrator. The default name is sa.
Please input Database user name:
9.
When the system displays the following prompt, enter the password of the database administrator. The default password of the database administrator is emsems.
Please input Database password:
If the system does not display any error message and the system output contains the message Rebuilding user databases finished, you can infer that the restoration is successful. 10. When the system displays the following prompt, enter Q to quit the Platformtools.
Please restart Sybase ASE to continue ... ============================================================= 1--Rebuild OMC database 2--Remove OMC database R--Return Q--Exit ============================================================= Please make a choice:
Step 12 Check the status of the database. # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpdb 2> go
NOTE
If all the user database exists and the value of the status is not offline or not recovered in each database, you can infer that the application database is successfully established and you can proceed with the following steps. If the application database is not established, check whether the interface on which the script is running can be correctly displayed. If the interface on which the script is running does not function well, contact your Huawei Technologies Co., Ltd. local office for technical support. Switch back to log in as user root.
1> exit -bash-3.00$ exit Step 13 Stop the Sybase. # su - dbuser For details about how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. Step 14 Start the Sybase. For details about how to start the Sybase, refer to 15.2.2 How to Start the Sybase. -bash-3.00$ exit Check whether the Sybase is started by referring to 15.2.1 How to Know Whether the Sybase Is Started. Step 15 Restore the dynamic data. For details about how to restore the dynamic data, refer to 10.2.6 Restoring M2000 Dynamic Data. ----End
10.4 Backing Up and Restoring M2000 System Data

This describes how to back up and restore the M2000 system data. 10.4.1 Backup of M2000 System Data This describes the backup of the M2000 system data. The M2000 system data backup refers to the backup of the operating system of the M2000 server. 10.4.2 Backing Up M2000 System Data This describes how to back up the M2000 system data in ufsdump mode. 10.4.3 Restoring M2000 System Data This describes how to restore the M2000 system data in ufsrestore mode.
10.4.1 Backup of M2000 System Data

This describes the backup of the M2000 system data. The M2000 system data backup refers to the backup of the operating system of the M2000 server. The M2000 system data backup refers to the backup of the operating system of the M2000 server. For details about the backup contents, backup modes, and storage media of the system data backup, see Table 10-9. Table 10-9 Introduction to system data backup Item Backup Contents Partition of backup data
10-28
Contents Data of the operating system / partition

Issue 05 (2008-05-20)
Backup modes
One-time backup If the operating system is not upgraded or the M2000 is upgraded across R versions, another backup is not required after you perform the initial backup of the data. If you plan to upgrade the operating system (for example, installing the patches of the operating system) or install the M2000 across R versions, you need to back up the operating system again. Tape In general, a 36/72 GB tape is required.
NOTE
l Run the df -h / command to view the size of the / partition. l A tape with 36/72 GB capacity means that it can store 36
Storage device The number of tapes required for backup
GB data basically while up to 72 GB data when compressed.
10.4.2 Backing Up M2000 System Data

This describes how to back up the M2000 system data in ufsdump mode.
Prerequisite
The ufsdump solution is used to back up and restore the data on the local system disk rather than the data on disk arrays. The ufsdump solution used for the system backup has the following requirements:
l l l
The solution is applicable to all the M2000 systems that are installed with Solaris 10. Keep the required tapes ready for system data backup. The magnetic head of the tape drive is clean. If the tape drive is externally connected, ensure that the connection between the tape drive and the M2000 server is proper. You must ensure that other users do not log in to the system. You can run the who command. If only one command result is displayed, you can infer that other users do not log in. If multiple command results are displayed, you can infer that other users have logged in. You must ask them to log out. The communication between the PC and the M2000 server is normal. You have decompressed the PlatformTools installation package to the /opt directory on the M2000 server. For details on how to obtain the PlatformTools, refer to Obtaining the M2000 Software Package.
l l
Procedure
Step 1 Back up the static data. For details, refer to 10.3.2 Backing Up M2000 Static Data. Step 2 If the M2000 services and the Sybase server are running, stop the M2000 services and the Sybase. For details on how to stop the M2000, see 7.3.4 Stopping M2000 Services. # su - dbuser For details about how to the Sybase, see 15.2.3 How to Stop the Sybase.
-bash-3.00$ exit Step 3 Check the server before backup. 1. View the IP address of the server. To view the physical and logical IP addresses of the server, run the following command: # ifconfig -a Ensure that the current local IP addresses are set in consistency with the previous planning. 2. Check the system hardware. a. b. Check the LED indicators of all the system hardware parts to ensure that no LED indicator is flashing for alarms. Ensure that both the local disk and the disk array are included. Run the following command to check the screen output of the information about the local disk and the disk array: # format c. Ensure that no hardware is damaged. # prtdiag -v prtdiag -vIn the command result, check that the screen output does not include the information about hardware damage, such as error or failed: 3. Check whether the root disks are properly encapsulated and mirrored. # metastat metastatIn the command result, check whether each Mirror contains two Submirror and whether the value of each State is Okay. 4. Check the log of the operating system. Check the log file /var/adm/messages of the operating system. Ensure that the system does not report any error log recently. 5. Run the explorer program. The program explorer collects all hardware information about the existing system and then saves the collected information to a package. To save the system information before the operating system is backed up, you need to run the program explorer to generate the information about the system state. Run the following commands: # /opt/SUNWexplo/bin/explorer The results generated after running the explorer program are saved in the /opt/SUNWexplo/ output directory. When you run the backup script later, the previous result file is backed up to a tape. The following file is an example of the result file generated after running explorer: explorer.83af631b.Athene-2006.01.21.10.01.tar.gz
NOTE
The rule for naming result files is as follows: explorer.host id.host name.date time.tar.gz You can obtain "host id" by running the hostid command on the M2000 server.
10-30
Issue 05 (2008-05-20)
Step 4 Check the status of the tape drive. If multiple tape drives are installed on the server, select a tape drive by referring to 15.1.4 How to Select the Tape Drive. If you select /dev/rmt/0, run the following command for confirmation: # mt -f /dev/rmt/0 status If the command results are similar to the following information, you can infer that the inserted tape is functioning well:
HP DAT-72 tape drive: sense key(0x6)= Unit Attention file no= 0 block no= 0 residual= 0 retries= 0
If a tape is not mounted or identified correctly, the following information is displayed:

/dev/rmt/0n: no tape loaded or drive offline
Before continuing the operation, you must enable the tape drive to identify a tape. Step 5 Use the PlatformTools to back up the system data. 1. To configure the rights of the PlatformTools directory, run the following commands: # chmod -R 777 /opt/PlatformTools 2. Start the PlatformTools. # cd /opt/PlatformTools # ./setup
NOTE
After you start the PlatformTools, you can enter R on the system interface to return to the upperlevel menu, or enter Q to exit the tool.
3.
At the following prompt, enter 2.

============================================================= Please choose the operation type 1--Installation 2--Maintenance Q--Exit ============================================================= Please make a choice:
4.

============================================================= 1--Backup OS 2--Restore OS 3--OMC database manipulations R--Return Q--Exit ============================================================= Please make a choice:
5.
At the following prompt, enter y.

============================================================= NOTE: For Solaris 10 system only. Boot disk should be encapsulted and mirrored by VxVM or SVM. Do you want to continue? [y/n]
Issue 05 (2008-05-20)
10-31
After you enter y, the script completes the system backup automatically, collect statistics on the total time taken for the system backup, and displays the time. The system backup takes about two hour. The contents to be backed up on the tape are as follows:
l l l l
PlatformTools Data of root disks Restore script Result of executing the explorer program
If the system displays no error message and the system output contains the message Successfully completed operating system backup!, you can infer that the backup of the operating system is successful. Step 6 Check whether the system backup data on the tape is valid. 1. Rewind the tape. # mt rewind 2. The contents of the first record on the tape are displayed. # tar tf /dev/rmt/0n 3. The contents of the second record on the tape are displayed. # ufsrestore tf /dev/rmt/0n If the previous two records do not contain error information such as Media read error: I/O error, you can infer that the data backup is valid. Step 7 Start the M2000 services and the Sybase. For details about how to start the Sybase, refer to 15.2.2 How to Start the Sybase. For details about how to start the M2000, refer to 7.3.3 Starting M2000 Services. ----End
Result
After the steps mentioned earlier are performed, the system backup is complete. Remove the tape, and then attach a label to the tape. The label contains the backup contents and the date.
10.4.3 Restoring M2000 System Data

This describes how to restore the M2000 system data in ufsrestore mode.
Prerequisite
l
Before restoring the operating system, you must ensure that all the hardware faults of the M2000 server are handled. Insert the tape that stores the operating system backup into the tape drive of the M2000 server to be restored.
10-32
Procedure
Step 1 Log in to the system controller (SC) or remote system controller (RSC) of the server. For details about how to log in to the SC or the RSC, refer to the related M2000 software installation guide. Step 2 After logging in to the SC/RSC of the server, run the following commands to shut down the operating system if the operating system is still running: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i0 Step 3 Power off the disk array. If the server has disk arrays, such as 6140, power off the disk arrays. If the server is not equipped with a disk array, go to the next step.
CAUTION
l l
If you boot the system from the CD-ROM, power off the disk arrays first. Ensure that the logical serial numbers of the local disks that are booted from the CD-ROM are identical to those in the existing system.
Step 4 Start the operating system by using a CD-ROM. Insert the Solaris installation disk into the CD-ROM drive of the server to be restored, and follow the guides displayed by the CD-ROM to start the operating system for the restoration of the system data. If the operating system is started, enter /usr/sbin/shutdown -g0 -y -i0 to switch to the state of the ok prompt. If the operating system is switched to the ok prompt, run the following command: ok boot cdrom -s Step 5 Check the state of the tape drive. After the system starts, insert a tape into the tape drive of the node that requires the backup operation. If the system backup data is stored on multiple tapes, insert the first tape on which the system backup data is stored. If multiple tape drives are installed on the server, select a tape drive by referring to 15.1.4 How to Select the Tape Drive. If you select /dev/rmt/0, run the following command for confirmation: # mt -f /dev/rmt/0 status If the command result is similar to the following information, you can infer that the inserted tape is functioning well:


Handle the problem before you perform the backup operation. Step 6 Restore the PlatformTools from the tape drive to the /tmp directory. # tar xf /dev/rmt/0n Step 7 Start the PlatformTools to automatically restore the system. 1. To configure the rights of the PlatformTools directory, run the following commands: # chmod -R 777 /tmp/PlatformTools 2. Start the PlatformTools. # cd /tmp/PlatformTools # ./setup
NOTE
After you start the PlatformTools, you can enter R on the system interface to return to the upperlevel menu, or enter Q to exit the tool.
3.

============================================================= Please choose the operation type 1--Installation 2--Maintenance Q--Exit ============================================================= Please make a choice:
4.

============================================================= 1--Backup OS 2--Restore OS 3--OMC database manipulations R--Return Q--Exit =============================================================
5.
At the following prompt, enter y.

============================================================= NOTE: For Solaris 10 system only. The server must be booted into single user mode from cdrom to do restoring. Do you want to continue? [y/n] y
The tool determines the original encapsulation type of the system disk and automatically searches for the original disk that is installed with the operating system to restore the system data. At the prompt Is application data on disk array(y/n)?,
l
If the server type is Netra 240, enter n. The Netra 240 server has no disk arrays and its application data is stored on the disk where the operating system is installed. If the server type is V890 or E4900, enter y. The V890 or E4900 server has disk arrays and its application data is stored on the disk arrays.
After you press Enter, the script automatically partitions root disks, creates a file system, restores the partition data of the root disks, rebuilds a device tree, creates a guide block,
and modifies the system and vfstab files to unpack the encapsulation of Volume Manager. The system restore takes about two hours. Please wait with patience. If the system displays no error message and the system output contains the message Successfully completed operating system restore!, you can infer that the restoration of the operating system is successful. 6. After the system data is successfully restored, run the following command to restart the operating system: # sync; sync; sync; sync; sync; sync; reboot -- -r
NOTE
l l l
You must use the command sync; sync; sync; sync; sync; sync; reboot -- -r. Two consecutive symbols "-" exist between reboot and -r. If the operating system cannot be started, switch back to the ok state, and then run the command boot -ar to restart the operating system again. At the system prompts, press Enter repeatedly until the operating system is successfully started.
Step 8 If a server has disk arrays, import a disk group after local disks are encapsulated. If the server does not have disk arrays, go to the next step. 1. 2. Turn on the power of the disk array. Wait for about five minutes. Search for the hardware.
NOTE
If fiber disk arrays such as 6140 and 6130 are used, skip this operation and directly perform Step 8.3.
# devfsadm 3. Check whether the system output contains the information on both local disks and disk arrays. # format
NOTE
If you confirm that the system output is correct, press Ctrl+D to return to the state of the command line.
4. 5.
Refresh the disk information that is stored in the Veritas volume management software. # vxdctl enable Check whether the disk array is imported. # vxdisk list In the command result, if a disk array is displayed under the DEVICE column but the ossdg disk group, which was named m2000dg, is not displayed under the GROUP column, run the following command to import the disk group: # vxdg -fC import ossdg
6.
Check whether the Volume Manager is functional. # vxprint If the KSTATE column is displayed as ENABLED and the STATE column is displayed as ACTIVE in the command result, you can infer that the Volume Manager is functional. Otherwise, run the following command to enable the Volume Manager:
Issue 05 (2008-05-20)
10-35
# vxvol -g ossdg startall Step 9 After the operating system is restored, use the PlatformTools tool to encapsulate the system disk again. Based on your server type, select the corresponding procedure. For details, refer to Table 10-10. Table 10-10 Encapsulating the local disks of a server Server Type Netra 240 V890 E4900 Reference Manual M2000 Software Installation Manual (Netra 240) M2000 Software Installation Manual (V890) M2000 Software Installation Manual (E4900) Reference Chapter Refer to Encapsulating the Local Disk of the Server. Refer to Encapsulating the Local Disk of the Server. Refer to Encapsulating the Local Disk of the Server.
Step 10 If a server has disk arrays, run the following command to edit the file system sheet. If the server does not have disk arrays, go to Step 12. # TERM=vt100; export TERM # vi /etc/vfstab Append the following line to the file:
/dev/vx/dsk/ossdg/exporthome /dev/vx/rdsk/ossdg/exporthome /home ufs 2 yes logging
NOTE
/export
l l
When editing the /etc/vfstab file, do not edit this file on the Windows or then transfer the file to the Solaris server. When adding the previous line, do not press Enter to change to the next line. In addition, you must press Tab to keep the space between fields. If you press Enter to change to the next line, or press another key except Tab to keep the space between fields, errors may occur.
Step 11 If a server has disk arrays, mount the file system of the disk array. If the server does not have disk arrays, go to the next step. # mount /export/home
l
If the file system fails to be mounted, check whether the file system sheet is edited correctly and whether the file system of the disk array works properly. If the file system is damaged, you need to create the file system of the disk array again. For details on how to create a file system, refer to the software installation manual of the corresponding server type. If the file system is successfully mounted, run the mount /export/ home command to mount the file system of the disk array again.
Step 12 Restart the operating system. # sync; sync; sync; sync; sync; sync; reboot -- -r

NOTE
l l
You must run the sync; sync; sync; sync; sync; sync; reboot -- -r command. Two consecutive symbols "-" exist between reboot and -r.
Step 13 Mirror the root disk.

NOTE
l l
After the operating system is restored, the mirror settings of the previous local disks become invalid and you must mirror the local disks again. The mirrors of the disk arrays are still valid.
Based on your server type, select the corresponding procedure. For details, refer to Table 10-11. Table 10-11 Mirroring the disks of the M2000 server Server Type Netra 240 V890 E4900 Reference Manual M2000 Software Installation Manual (Netra 240) M2000 Software Installation Manual (V890) M2000 Software Installation Manual (E4900) Reference Chapter Refer to Mirroring the Local Disk of the Server. Refer to Mirroring the Local Disk of the Server. Refer to Mirroring the Local Disk of the Server.
Step 14 Restore the M2000 static data. For details about how to restore the M2000 static data, refer to 10.3.3 Restoring M2000 Static Data. ----End
Issue 05 (2008-05-20)
10-37
11 M2000 Routine Maintenance
11
About This Chapter
M2000 Routine Maintenance
This chapter describes the maintenance items and the procedures required to conduct the M2000 routine maintenance. These items are, however, only for reference. In real application, specify the maintenance items as required. 11.1 M2000 Routine Maintenance Items This describes the recommended maintenance items of the M2000 system. 11.2 Checking the Configuration of Alarm Timing This describes how to check whether the policy on automatic dumping alarm data from the alarm database is reasonable. 11.3 Checking the Configuration of Automatic Log Dump This describes how to check whether the system of automatic dumping alarm data from the alarm database is satisfactory. 11.4 Checking the Synchronization Time of NE Log This describes how to check whether the configuration of synchronization time of the NE log is correct. The purpose is to avoid the server overload owing to the conflict of time when you perform tasks on the server. 11.5 Checking the Configuration of the File Server This describes how to check whether the configuration of the file server is appropriate. 11.6 Checking the Configuration of System Backup This describes how to check whether the periodic backup of the M2000 server and NEs are started and whether the start time is correct. The purpose is to avoid the server overload owing to the conflict of time when you perform tasks on the server. This also describes how to check whether backup files are generated in the disk. 11.7 Checking the Configuration of System Monitoring This describes how to check the configuration of system monitoring. 11.8 Checking the Synchronization Time of NE Configuration This describes how to check whether the time for synchronizing NE configuration data is appropriate. The purpose is to avoid the server overload. The server overload may occur when the synchronization together with other tasks on the server is performed at the same time.
11.9 Checking the Performance Measurement State This describes how to check the performance measurement state. You can ensure that all the measurement counters and measurement objects are in Measuring state. 11.10 Checking the Missing Performance Result To ensure that no result is lost, you must check that the missing performance result exists. 11.11 Checking the Alarm Reception Check the alarm reception and ensure that the M2000 can receive alarms from NEs in real time. 11.12 Checking the NMS Connection This describes how to check the NMS connection and to ensure that the NMS connection is normal. 11.13 Checking the Functionality of Alarm Box Check the function of generating visual and audible alarms for the alarm box and ensure that the alarm box can indicate the alarms on the M2000 in real time. 11.14 Checking the Threshold of Network Management Capability This describes how to check whether the M2000 management capability exceeds the threshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceed the capability limit. 11.15 Checking OMC Alarms This describes how to check the alarms that the M2000 system generates. 11.16 Checking Connections Between the M2000 and NEs This describes how to check the connections between the M2000 and NEs. 11.17 Checking the Status of the M2000 Routes This describes how to check the configuration of the M2000 routes. 11.18 Checking M2000 Logs M2000 user logs record the details about user operations, such as user name, start time, end time, and log type. The M2000 system administrators and operators can query user logs. 11.19 Checking the Error Log of the Solaris This describes how to check the error logs of the Solaris operating system. 11.20 Checking the Disk Usage of the M2000 Server This describes how to check the disk usage and clean up the expired log files, temporary files, and other files that are no longer in use. This operation requires very few system resources and does not affect the system operation. 11.21 Checking the States of M2000 Databases This describes how to check the states of the M2000 database services, database states, and database usage. This operation requires only a few system resources and does not affect the system operation. 11.22 Checking the Number of M2000 Processes This describes how to check the total number of M2000 processes. This operation requires very few system resources and does not affect system operation. 11.23 Checking the States of M2000 Services This describes how to check the states of M2000 services. This operation requires very few system resources and does not affect system operation. 11.24 Checking the Core Files on the Server
11-2
Issue 05 (2008-05-20)
This describes how to check the /export/home/omc/var/logs directory and to ensure that core files do not exist. 11.25 Backing Up the M2000 This describes how to back up the M2000 . The M2000 backup refers to the backup of M2000 databases and system files. The M2000 databases consists of omcdb, omclogdb, omcsmdb, omctmdb, fmdb, pmdb, swmdb, pmcomdb, sumdb, itfndb. The M2000 system files refer to those files in the directories /export/home/omc/var and /export/home/sysm. 11.26 Checking the Time of the M2000 Server This describes how to check the time of the M2000 server. 11.27 Checking the States of M2000 Disks This describes how to check all the disks in the Vxvm, the logical volumes of the local disk in the Vxvm, and the logical volumes of the disk array in the Vxvm. 11.28 Checking the Power Supply of the M2000 Server This describes how to check the power supply of the M2000 server. 11.29 Checking the Hardware of the M2000 Server This describes how to check the M2000 server hardware. 11.30 Checking the Peripherals of the M2000 Server This describes how to check the peripherals of the M2000 server, such as the CD-ROM drive and the tape drive. 11.31 Checking the SMC Collection Results This describes how to check the SMC collection results and to ensure that the M2000 server environment is normal.
Issue 05 (2008-05-20)
11-3
11.1 M2000 Routine Maintenance Items

This describes the recommended maintenance items of the M2000 system. Table 11-1 lists the recommended maintenance items of the M2000 system. You can add or delete maintenance items according to your requirements. Table 11-1 Maintenance item list No. 1 Item Check the performance measurement status. Check the loss of performance results. Check the status of alarm reception. Check the connection status of the NMS. Check the status of the alarm box. Check OMC alarms. Check the connections between the M2000 and NEs. Check M2000 logs. Check Solaris error logs. Check the CPU usage. Frequenc y Daily Expected Result All measurement counters and measurement objects are being measured. Performance results are not lost. The alarms reported by NEs are received in real time. The NMS can collect the alarms and performance data reported by the M2000 . The alarm box can emit M2000 alarms. The OMC alarms are not generated. The connections with NEs are functioning well. The M2000 is operational. No error log is generated. In the duration when no scheduled tasks exist and when no performance data is dumped, the CPU usage ratio is smaller than 50%. The usage of all partitions is less than 80%. The databases are functional. Their usage ratio is smaller than 80%. When the M2000 is running, run a command to view processes. The M2000 server displays all the processes. Processes not displayed are not running.
2 3 4 5 6 7
Daily Daily Daily Daily Daily Daily
8 9 10
Daily Daily Daily
11 12 13
Check the usage ratio of disk space. Check the database status. Check the total number of processes and the service status.
Daily Daily Daily
11-4
Issue 05 (2008-05-20)
No. 14 15
Item Check the status of M2000 services. Check the core file of the M2000 server. Check the hardware of the M2000 server. Check the results collected by the SMC. Check the configuration of alarm timing tasks. Check the configuration of automatic log dump. Check the configuration of NE log synchronization time. Check the configuration of the file server. Check the configuration of the system backup. Check the configuration of system monitoring. Check the setting of NE configuration synchronization time. Check the status of M2000 routes. Check whether the management capability of the M2000 exceeds the limit.
Frequenc y Daily Daily
Expected Result All services are running well. No "not running" is displayed. Under the directory /export/home/omc/var/ logs, there are no files whose names start with "core". The hardware of the M2000 server is intact. The operating environment of the M2000 server is running properly. The time of alarm timing tasks is set correctly. This prevents the time conflict with background tasks. The conflict may result in the CPU overload. The time of automatic log dump is set properly. This prevents the time conflict with background tasks. The conflict may result in the CPU overload. The time of NE log synchronization is set correctly. This prevents the time conflict with background tasks. The conflict may result in the CPU overload. The file server is configured correctly.
16 17 18
Daily Daily Weekly
19
Weekly
20
Weekly
21
Weekly
22
Weekly
The time for automatically and periodically backing up the M2000 server and NEs is set correctly. The backup files are generated in disks. The thresholds of system monitoring is set correctly. The time of NE configuration synchronization is set correctly. The corresponding boot files exist in the directory /etc/rc2.d. The number of equivalent NEs managed by the M2000 does not exceed the management capability of the M2000 system.
23
Weekly
24
Weekly
25 26
Weekly Weekly
Issue 05 (2008-05-20)
11-5
No. 27
Item Back up the M2000 system Check the time of the M2000 server. Check the states of the local disks on the server and the states of the disks in the disk array. Check the power supply of the M2000 server. Check the external devices of the M2000 server. For the NEs in the GSM and CDMA networks, check the validity period of the M2000 users who logs in to an NE and performs the maintenance on the BAM of the NE. Ensure that the M2000 users are authorized to maintain the BAM of the NE.
Frequenc y Weekly
Expected Result Back up the M2000 database and system files. View the backup files on disks and tapes. The time of the M2000 server is set correctly. The state of all disks available is online. The KSTATE column of pl, sd, and v is ENABLED. The STATE column is ACTIVE. The usage of all partitions is less than 80%. The power supply is functional.
28 29
Weekly Weekly
30
Monthly
31
Monthly
To check the CD-ROM drive and the tape drive, refer to the Solaris Administrator Guide. The M2000 users who logs in to an NE can directly maintain the BAM and are authorized to maintain the BAM of the NE. Ensure that the M2000 can handle the configuration data and performance data of NEs.
32
Monthly
For details about the operation and maintenance of NEs, refer to the M2000 Online Help.
11.2 Checking the Configuration of Alarm Timing

This describes how to check whether the policy on automatic dumping alarm data from the alarm database is reasonable.
Prerequisite
l l
You have logged in to the M2000. You are authorized to check the configuration of M2000 integrated task management.
11-6
Issue 05 (2008-05-20)
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select the Alarm Data node. You can also double-click the Alarm Data node to open the Attributes window. Step 3 Select the task in the right pane and click Property. Step 4 In the Attributes window, check the configuration of automatic alarm data dumping. Step 5 Ensure that the configuration of automatic alarm data dumping is proper. ----End
11.3 Checking the Configuration of Automatic Log Dump

This describes how to check whether the system of automatic dumping alarm data from the alarm database is satisfactory.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to check the configuration of M2000 integrated task management.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Check the configuration of automatic log dump of NE operation logs. 1. 2. 3. 4. 1. 2. 3. 4. 1. 2.
Issue 05 (2008-05-20)
Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select NE Operation Log. Choose the task in the right pane. Click Attribute. Check the configuration of auto operation log dump in the Attribute window. Ensure that the configuration is reasonable. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select NE Security Log. Choose the task in the right pane. Click Attribute. Check the configuration of auto security log dump in the Attribute window. Ensure that the configuration is reasonable. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select Operation Log. Choose the task in the right pane. Click Attribute.
Step 3 Check the configuration of automatic log dump of NE security logs.
Step 4 Check the configuration of automatic log dump of operation logs.
3. 4. 1. 2. 3. 4. 1. 2. 3. 4.
Check the configuration of auto alarm data dump in the Attribute window. Ensure that the configuration is reasonable. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select System Log. Choose the task in the right pane. Click Attribute. Check the configuration of auto system log dump in the Attribute window. Ensure that the configuration is reasonable. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select Security Log. Choose the task in the right pane. Click Attribute. Check the configuration of auto security log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 5 Check the configuration of automatic log dump of system logs.
Step 6 Check the configuration of automatic log dump of security logs.
----End
11.4 Checking the Synchronization Time of NE Log

This describes how to check whether the configuration of synchronization time of the NE log is correct. The purpose is to avoid the server overload owing to the conflict of time when you perform tasks on the server.
Prerequisite
l l
You have logged in to the M2000. You are authorized to check the configuration of the M2000 integrated task management.
Context
You need to run the operation only if the NE supporting this function exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select NE Log Synchronization. Step 3 Select the task in the right pane. Click Attribute. Step 4 View the configuration of synchronization time of NE log in the Attribute dialog box. Step 5 Ensure that the configuration is correct. You are advised to synchronize NE logs when the traffic is not heavy. Generally, this operation is performed at night when no other tasks are performed. ----End
11.5 Checking the Configuration of the File Server

This describes how to check whether the configuration of the file server is appropriate.
Prerequisite
l l
You have logged in to the M2000. You are authorized to check the configuration of the M2000 file server.
Procedure
Step 1 Choose Software > File Server Setting. The File Server Setting window is displayed. Step 2 Select the NE type in theROOT navigation tree in the left pane. Step 3 Check the name and IP address of the file server in the right pane. Step 4 Ensure that the configuration of the file server is appropriate. ----End
11.6 Checking the Configuration of System Backup

This describes how to check whether the periodic backup of the M2000 server and NEs are started and whether the start time is correct. The purpose is to avoid the server overload owing to the conflict of time when you perform tasks on the server. This also describes how to check whether backup files are generated in the disk.
Prerequisite
l l
You have logged in to the M2000. You are authorized to check the configuration of the M2000 integration task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Check whether the periodic backup of the M2000 server is started and whether the start time is correct. 1. 2. 3. 4. Under the Backup node in the Task Type navigation tree in the left pane, select the Server Backup node. View Last Run Time and State in the right pane. Ensure that the task is running in the execution time. Select the task in the right pane. Click Attribute. View the configuration of periodic backup time for the M2000 server in the Attribute dialog box.
Issue 05 (2008-05-20)
5. 1. 2. 3. 4.
Ensure that the configuration is correct. Under the Backup node in the Task Type navigation tree in the left pane, select the NE Backup node. View Last Run Time and State in the right pane. Ensure that the task is running in the execution time. Select the task in the right pane. Click Attribute. View the configuration of periodic backup time for NEs in the Attribute dialog box. Ensure that the configuration is correct.
Step 3 Check whether the periodic backup of the NE is started and whether the start time is appropriate.
Step 4 Log in to the M2000 server as user omcuser. Check whether backup files exist in the backup directory of both the M2000 server and NEs. You can specify the backup directory for the M2000 server and NEs based on the attribute information. ----End
11.7 Checking the Configuration of System Monitoring

This describes how to check the configuration of system monitoring.
Context
The recommended thresholds of the CPU usage ratio, memory usage ratio, and database usage ratio are 80%.
Procedure
Step 1 Choose Monitor > System Monitor > Settings . The System Monitor Configurations dialog box is displayed. Step 2 Click the Performance Monitor tab. Check whether the thresholds of CPU usage ratio and memory usage ratio are appropriate. Step 3 Click the Hard Disk Monitor tab. Check whether the threshold of disk usage ratio is appropriate. Step 4 Click the Database Monitor tab. Check whether the threshold of database usage ratio is appropriate. ----End
Example
Table 11-2 lists the recommended alarm thresholds for the monitored items. Table 11-2 Recommended alarm thresholds Item Performance monitoring
11-10
Recommended Value CPU used rate (%) 90
Issue 05 (2008-05-20)
Item Memory used rate (%) Hard disk monitoring Database monitoring Hard disk used rate (%) Database used rate (%)
Recommended Value 90 90 90
11.8 Checking the Synchronization Time of NE Configuration

This describes how to check whether the time for synchronizing NE configuration data is appropriate. The purpose is to avoid the server overload. The server overload may occur when the synchronization together with other tasks on the server is performed at the same time.
Prerequisite
l l
You have logged in to the M2000. You are authorized to check the configuration of the M2000 integrated task management.
Context
You need to run the operation only if the NE supporting this function exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select the NE Configuration Data Synchronization node. Step 3 Select the task in the right pane. Click Attribute. Step 4 View the setting of the time for synchronizing NE configuration data in the Attribute dialog box. Step 5 Ensure that the configuration is correct. ----End
11.9 Checking the Performance Measurement State

This describes how to check the performance measurement state. You can ensure that all the measurement counters and measurement objects are in Measuring state.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to perform performance management.
Issue 05 (2008-05-20)
Procedure
Step 1 Choose Performance > Measure Management > measurement Status . The Measure Management window is displayed. Step 2 Ensure that all the measurement counters and measurement objects are in Measuring state. ----End
11.10 Checking the Missing Performance Result

To ensure that no result is lost, you must check that the missing performance result exists.
Prerequisite
l l
You have logged in to the M2000. You are authorized to perform performance management.
Procedure
Step 1 Choose Performance > Measure Management > measurement Status . The Measure Management window is displayed. Step 2 Select an NE from the navigation tree in the left pane. Step 3 Select the Measurement Unit under the Measurement Function Set. Step 4 Click LostResult to view the Query Missing Result dialog box. Step 5 Set the time range and query the lost performance result. If there are missing measurement results in the time range, the information is displayed in the Lost Result Message dialog box. ----End
Postrequisite
If missing measurement results exist, synchronize the results. 1. 2. Click Synchronize to view the Please select time segment dialog box. Set the time range for synchronizing measurement results. Click OK.
After the synchronizing command is delivered to the NE, the NE takes some time to report the performance measurement results. After the data is reported, you can query the missing measurement results from the performance measurement results.
11.11 Checking the Alarm Reception

Check the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to perform fault management.
Procedure
Step 1 Choose Monitor > Current Fault Alarms. The Current Fault Alarm Browse 1 window is displayed. Step 2 Set filter condition, then click Filter. Step 3 Ensure that the M2000 can receive the alarms reported by NEs in real time. ----End
11.12 Checking the NMS Connection

This describes how to check the NMS connection and to ensure that the NMS connection is normal.
Procedure
Ensure that the NMS can collect the alarms and performance data reported from the M2000 . ----End
11.13 Checking the Functionality of Alarm Box

Check the function of generating visual and audible alarms for the alarm box and ensure that the alarm box can indicate the alarms on the M2000 in real time.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to perform fault management.
Procedure
Step 1 Choose Monitor > Alarm Box Manager. The Alarm Box Settings window is displayed. Step 2 View the settings. Ensure that alarms generated from the NEs, which satisfy the conditions, can be indicated on the alarm box in real time. ----End
Issue 05 (2008-05-20)
11-13
11.14 Checking the Threshold of Network Management Capability

This describes how to check whether the M2000 management capability exceeds the threshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceed the capability limit.
Procedure
Check whether the M2000 management capability exceeds the threshold. Ensure that the number of equivalent NEs managed by the M2000 is not beyond the capacity. For details on how to calculate equivalent NEs and for the description of the M2000 management capability, refer to the M2000 Product Description. ----End
11.15 Checking OMC Alarms

This describes how to check the alarms that the M2000 system generates.
Prerequisite
l l
You have logged in to the M2000. You are authorized to query alarms.
Procedure
Step 1 Check whether the OMC icon in the topology map indicates alarms. No alarm is generated if the system is operational. Step 2 Right-click the OMC icon and choose Query Alarm > Current Fault Alarm . The Current Fault Alarm Query dialog box is displayed.
l
If the alarms listed in Table 11-3 are generated, you need to consult the local office to clear them immediately. Table 11-3 Fault alarms requiring for immediate handling Alarm Name Array Reconstruction Error Array Reconstruction Disk Usage Is Too High Fan Failure In The Disk Cabinet Hard Disk Failure Alarm ID 204 210 37 208 205
Issue 05 (2008-05-20)
11-14
Alarm Name Hard Disk Synchronization Error Host Fan Is Abnormal Host Power Cable Failure Host Power Failure Host Temperature Is Abnormal Power Failure In The Disk Cabinet Reconstruct The Virtual Disk The temperature Of the Disk Cabinet Is Abnormal OMC Service Is Terminated Abnormally
Alarm ID 206 220 218 217 219 209 212 207 4
If the alarms listed in Table 11-4 are generated for half an hour and are still not been cleared, you need to consult the local office to clear them as soon as possible. Table 11-4 Fault alarms requiring for handling within half an hour Alarm Name OMC Service Is Terminated Abnormally Alarm ID 4
If the alarms listed in Table 11-5 are generated, you need to clear them when you arrive at the office next morning. Table 11-5 Fault alarms requiring for handling within a day Alarm Name Pmdb Not Enough Ran License Expired Ran License Invalid Ran License On Trial Version Load Failed Operation Log Overflow Export Failure Operation Log Periodic Export Failure Operation Log Recording Failure Security Log Over Displace Alarm Security Log Period Displace Alarm System Log Oveflow Export Failure Alarm ID 405 505 501 506 303 7 8 6 232 233 230
11-15
Issue 05 (2008-05-20)
Alarm Name System Log Periodic Export Failure System Log Recording Failure
Alarm ID 231 5
If the alarms listed in Table 11-6 are generated during network expansion, you can export them every day and then check the Location Information column in the exported file. If there are the alarms about important NEs, you must clear the alarms. Table 11-6 Fault alarms requiring for attention during network expansion Alarm Name Connection Broken Alarm ID 301
If the alarms listed in Table 11-7 are generated many times, you need to find out the user who logs in to the M2000 with an incorrect password and to prevent hostile actions. Table 11-7 Fault alarms on malicious actions Alarm Name Reach MaxLogin Attempts Alarm Alarm ID 11
Step 3 Right-click the OMC icon and choose Query Alarm > Event Alarm. The Event Alarm Query dialog box is displayed.
l
If the alarms listed in Table 11-8 are generated, you need to consult the local office to clear them immediately. Table 11-8 Event alarms requiring immediate handling Alarm Name A Disk on the Array Is Faulty Array Disk Is Offline CPU Failure Disk Array Failure Disk Cabinet Failure Disk Local State Is Changed Disk Physical State Is Changed Failure To the Devices in the Disk Array Cabinet Fan Failure Alarm ID 108 213 112 105 214 216 215 107 102
11-16
Alarm Name Hard Disk Failure Memory Failure Power Failure Power or Fan Failure To the Disk Array Cabinet The Battery for the Array Controller Is Faulty The Cache for the Array Controller Is Faulty The CPU Temperature Is Abnormal The Logical Drive Is Offline
Alarm ID 104 110 101 106 201 202 103 203
If the alarms listed in Table 11-9 are generated, you need to clear them when you arrive at the office next morning. Table 11-9 Event alarms requiring for handling within a day Alarm Name OMCDataBackup SMC Alarm Alarm ID 512 1099
If the alarms listed in Table 11-10 are generated during network expansion, you can export them every day and check the Location Information column in the exported file. If there are the alarms about important NEs, you must clear the alarms. Table 11-10 Event alarms requiring your attention during network expansion Alarm Name Pm Result Lost Alarm ID 407
----End
Postrequisite
To handle alarms, perform the following steps: 1. 2. 3. Double-click an alarm record. The Alarm Details dialog box is displayed. Click More information. The M2000 Online Help is displayed. Handle and acknowledge alarms that have not been cleared. Analyze and acknowledge the cleared alarms. The cleared alarms are not displayed. The cleared but unacknowledged alarms are displayed in a different color.
4.
Click the Knowledge Database and Explanation Database tab. Enter the description, causes, and handling suggestion in the Knowledge pane. The knowledge input is saved in the alarm knowledge base. Repeat 1 to 4 for each alarm. Query and handle the current fault alarms, event alarms, history fault alarms, and shielded alarms.
5.
6.
Ensure that the M2000 is operational. Alarms do not occur if the M2000 is operational.
11.16 Checking Connections Between the M2000 and NEs

This describes how to check the connections between the M2000 and NEs.
Prerequisite
Before checking connections between the M2000 and NEs, ensure that:
l l
You have logged in to the M2000 . You are authorized to query the status of NE connections.
NOTE
The connection status of virtual NEs and the OMC (M2000 ) is NA (not applicable).
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . The System Monitor Browser dialog box is displayed. Step 2 Click the NE Monitor tab. You can check the connection status of NEs. There are three connection status: Connected, Break, and NA. Step 3 Handle exceptions. The Break status is caused by the network. Check the network status. The NA status is caused by an unmatched NE version. Check the NE version and then install the adaptation layer. For details, refer to the M2000 Commissioning Guide. Step 4 Check whether the NEs are connected correctly. The status of all NEs is Connected. ----End
11.17 Checking the Status of the M2000 Routes

This describes how to check the configuration of the M2000 routes.
Prerequisite
You have logged in the M2000 server as user root.
Procedure
Check the configuration of the current route. # netstat -r ----End
11.18 Checking M2000 Logs

M2000 user logs record the details about user operations, such as user name, start time, end time, and log type. The M2000 system administrators and operators can query user logs.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to check M2000 logs.
Procedure
Step 1 Choose System > Log Management > Query Operation Logs . The Log Management window is displayed. Step 2 Choose User Log under the Log Query node from the Log Management navigation tree on the left of the Log Management n window. Step 3 Set query conditions in the Filter Condition window and click OK. User logs can be queried based on users, operations, terminals, time ranges, results, or objects. The queried results are displayed. Step 4 Handle abnormal operations. Handle the abnormal or unfriendly operations. For example, if a user fails to log in to the client for several times, perform the validity check for the user. Step 5 Confirm that no error information exists in M2000 logs. The system works properly. No abnormal or unfriendly operations are performed. ----End
11.19 Checking the Error Log of the Solaris

This describes how to check the error logs of the Solaris operating system.
Prerequisite
You have logged in to the M2000 as user omcuser.
Procedure
Step 1 Open the /var/adm/messages file to check the file for errors. Generally, the file does not contain error or failure records are not included in the file. Step 2 Open the /var/log/syslog file and check the file for errors. Generally, the file does not contain error records. Step 3 Handle the error information. If the files contain any error information, handle it by referring to the Solaris Administrator Guide. Step 4 Check whether the Solaris logs are normal. Generally, the Solaris logs do not contain error or failure records. ----End
11.20 Checking the Disk Usage of the M2000 Server

This describes how to check the disk usage and clean up the expired log files, temporary files, and other files that are no longer in use. This operation requires very few system resources and does not affect the system operation.
Prerequisite
l l
You have logged in to the M2000 system. You have the relevant operation privileges.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . The System Monitor Browser window is displayed. Step 2 Click the Hard Disk Monitor tab. The disk usage of the M2000 server is displayed.
l l
The disk usage is smaller than 90%. View the partition with the largest remaining space. The remaining space must be sufficient to back up the M2000.
Step 3 Handle exceptional situations. Clear the disk space if the disk space is insufficient. For details, refer to 4.1.2 Clearing the Disk Space of an M2000 Client and 9.2.4 Clearing the Disk Space of the M2000 Server. Step 4 Check whether the disk usage of the M2000 server is within the normal range. ----End
11-20
Issue 05 (2008-05-20)
11.21 Checking the States of M2000 Databases

This describes how to check the states of the M2000 database services, database states, and database usage. This operation requires only a few system resources and does not affect the system operation.
Prerequisite
l l
You have logged in to the M2000 client. You have the relevant operation privileges.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . The System Monitor Browser window is displayed. Step 2 Click the Database Monitor tab. The information about the database of the M2000 server is displayed. Step 3 Handle exceptional situations. If the database usage is greater than 90%, clear some data space by dumping alarm data and user logs. The clearing operation does not affect the system operation. For details on how to clear a database, refer to 8.3 Clearing M2000 Databases. Step 4 Ensure that the database works properly. The database usage is smaller than 90%. ----End
11.22 Checking the Number of M2000 Processes

This describes how to check the total number of M2000 processes. This operation requires very few system resources and does not affect system operation.
Prerequisite
l l
You have logged in to the M2000 as user omcuser. Switch to the default installation path of the M2000, which is /opt/OMC.
Procedure
Step 1 Run the svc_profile.sh script. -bash-3.00$ . ./svc_profile.sh Step 2 Check the number of the running processes. -bash-3.00$ svc_ps|wc -l The number of the running processes is displayed, such as 37.
For details about how to check all the M2000 processes, refer to 14.1.5 svc_adm -cmd status Command. Step 3 Run the command ps -ef |grep "<defunct>" | grep -v grep to check whether the frozen defunct process exists. If no message is displayed, you can infer that a frozen defunct progress does not exist. ----End
11.23 Checking the States of M2000 Services

This describes how to check the states of M2000 services. This operation requires very few system resources and does not affect system operation.
Prerequisite
l l
You have logged in to the M2000 client. You have the relevant operation privileges.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser . The Monitor Browser window is displayed. Step 2 Click the Service Monitor or Monitor Browser tab to monitor the processes running on the M2000 server. Step 3 Handle exceptional situations. In case a process is running improperly or a process is terminated exceptionally, log in to the M2000 server as user root. Run the command kill -9 pid to forcibly kill the process, where pid indicates the process No.. The start_svc command is used to start all the M2000 services. If some sessions are not started, run the command start_svc again. Step 4 Check whether the M2000 works properly. The Status of all M2000 services is Running. ----End
11.24 Checking the Core Files on the Server

This describes how to check the /export/home/omc/var/logs directory and to ensure that core files do not exist.
Prerequisite
Procedure
Step 1 Go to the /export/home/omc/var/logs directory. -bash-3.00$ cd /export/home/omc/var/logs
Step 2 Check the /export/home/omc/var/logs directory and ensure that core files do not exist. Delete the core files generated one week earlier. Contact Huawei local office to deal with the core files generated within the week. ----End
11.25 Backing Up the M2000

This describes how to back up the M2000 . The M2000 backup refers to the backup of M2000 databases and system files. The M2000 databases consists of omcdb, omclogdb, omcsmdb, omctmdb, fmdb, pmdb, swmdb, pmcomdb, sumdb, itfndb. The M2000 system files refer to those files in the directories /export/home/omc/var and /export/home/sysm.
Prerequisite
l l
You have logged in to the M2000 . You are authorized to back up the M2000 system.
Procedure
Step 1 On the main window, choose Maintenance > Task Management. The Centralized Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup in the navigation tree and double-click the node. The Attribute dialog box of server periodic backup is displayed, as shown in Figure 11-1.
Issue 05 (2008-05-20)
11-23
11-24
Issue 05 (2008-05-20)
Issue 05 (2008-05-20)
11-25

NOTE
----End
11.26 Checking the Time of the M2000 Server

This describes how to check the time of the M2000 server.
Prerequisite
You have logged in to the M2000 as user omcuser.
Procedure
Step 1 Check the time of the M2000 server. -bash-3.00$ date The server time is displayed, for example:
Tue Mar 29 00:35:24 MEST 2005
Step 2 If the M2000 server is configured with the NTP service, run the command ps -ef | grep ntp | grep -v grep to check whether the NTP service is started. Ensure that the NTP service is started and check the service status according to 2.3.8 Checking the Running Status of the NTP Service on the M2000 Server. Step 3 Handle exceptional situations.
l
Change the server time if it is incorrectly set or it is not synchronized with the external clock source through NTP. For details on how to handle the problem, refer to 2.2 Setting Time Information for the M2000 Server. If the M2000 is configured with the NTP service and the NTP service is not running properly, handle the problem according to 2.2.3 Setting the NTP Service for the M2000 Server.
Step 4 Check whether the M2000 works properly. Ensure that the server time is correct. ----End
11.27 Checking the States of M2000 Disks

This describes how to check all the disks in the Vxvm, the logical volumes of the local disk in the Vxvm, and the logical volumes of the disk array in the Vxvm.
Prerequisite
You have logged in to the M2000 as user root.
Context
The following operation applies only for the M2000 server configured with disk array.
Procedure
Step 1 Check all the disks in the Vxvm. # vxdisk -g name of the disk array list Assume that the name of the disk array is ossdg. Run the following command: # vxdisk -g ossdg list The following information is an example of the command result:
DEVICE c4t2d1s2 TYPE auto:cdsdisk DISK ossdisk-1 GROUP ossdg STATUS online
Generally, all the values in the STATUS column in the command result are online. Step 2 Check the logical volumes of the disk array in the Vxvm: # vxprint -g ossdg
NOTE
In the command result, all the values of pl, sd, and v in the KSTATE column are ENABLED and all the values of pl and v in the STATE column are ACTIVE.
Step 3 Ensure that the M2000 disks are functioning properly. # df -k Ensure that the usage ratio of each partition is smaller than 90%. If the usage ratio of a partition is greater than 90%, you must clean the disk immediately. For details on how to clean a disk, refer to 9.2.4 Clearing the Disk Space of the M2000 Server. ----End
11.28 Checking the Power Supply of the M2000 Server

This describes how to check the power supply of the M2000 server.
Prerequisite
The M2000 server is switched on.
Procedure
Step 1 Check power supply indicators. All power indicators are green. All fault indicators are dim. Step 2 Check the power supply indicators of the disk array and the storage device. Green indicators are on or blinking. Step 3 Check the latest power supply fault records in system logs of the Solaris.
The system logs do not contain any fault related records.

NOTE
The methods for checking the power supply fault records are as follows:
l l
For the matching work station 4900 or similar models, if the log is redirected to Netra 240, open the message file defined in /etc/syslog.conf and view the content. Connect to the platform, and then run the showlogs command to view the logs of the recent days.
Step 4 Check the external power supply. The external power supply is functional. Step 5 Handle exceptional situations. The Solaris system log records the faults of the power supply housed in the Sun cabinet. For the external power supply, that is, the power supply outside the Sun cabinet, check the power supply and circuits according to the Sun Netra 240 Installation and User Guide, Sun Fire V890 Server Owner's Guide, and Sun Fire 6800/4810/4800/3800 Installation Guide. If the fault is complex, contact the engineers at Sun Microsystems. Step 6 Ensure that the power of the M2000 works normally. All power indicators must be green and all fault indicators must be dim. ----End
11.29 Checking the Hardware of the M2000 Server

This describes how to check the M2000 server hardware.
Prerequisite
The cables are connected correctly. The M2000 server is switched on.
Procedure
Step 1 Check the server model. The server can be the Sun Netra 240, Sun Fire V890, or Sun Fire E4900 server. Step 2 Check the server hardware based on the server model according to the Netra 240 Server Installation Guide, Sun Fire V890 Server Owner's Guide, or Sun Fire E6900_E4900 Systems Service Manual. The server works properly. The indicators are displayed properly. Step 3 If a disk array is used, check the disk array model. Then, check the hardware according to the manual mapping to the model of disk array. Step 4 Handle exceptional situations. If the hardware incurs a fault, locate the fault by referring to related manuals of the disk array and the Netra 240 Server Installation Guide, Sun Fire V890 Server Service Manual, or Sun Fire E6900_E4900 Systems Service Manual. For a fault difficult to locate, contact the engineers at Sun Microsystems.
Step 5 Ensure that the hardware of the M2000 server and disk array is functional. ----End
11.30 Checking the Peripherals of the M2000 Server

This describes how to check the peripherals of the M2000 server, such as the CD-ROM drive and the tape drive.
Prerequisite
The M2000 system is switched on.
Procedure
Step 1 Check the CD-ROM drive. The CD-ROM drive works properly. Step 2 Check the tape drive. The tape drive works properly. Step 3 If the server uses the StorEdge D240, check whether the StorEdge D240 is functional.
l
The green light of the power indicator on the right of the front panel is on, and the indicator of system faults is off. In the middle of the front panel, there is one hard disk indicator available in both upper line and lower line. The green light of the hard disk indicators are on or blinking. For the two power modules in the rear panel, the green indicator of DC power output is on, the fault indicator is off, the blue service indicator is on, and the green indicator of AC power input is on.
Step 4 Handle exceptional situations. For details on how to handle the faults of the CD-ROM drive and the tape drive, refer to the Solaris Administrator Guide. Step 5 Check whether the peripherals of the server works normally. For details on how to handle the faults of the CD-ROM and the tape drive, refer to the Solaris Administrator Guide. ----End
11.31 Checking the SMC Collection Results

This describes how to check the SMC collection results and to ensure that the M2000 server environment is normal.
Prerequisite
l l
The SMC server software runs properly. The SMC client software runs properly.
Issue 05 (2008-05-20)

l
You have the password of user root to log in to the M2000 server.
Procedure
Step 1 On the SMC client, log in to the server as user root. Step 2 Enter Sun Management Center and check the SMC collection results. For detailed operation procedures, refer the related SMC manuals. ----End
11-30
Issue 05 (2008-05-20)
12 M2000 Emergency Maintenance
12
M2000 Emergency Maintenance
About This Chapter

This chapter describes the emergency maintenance in the case of a critical fault in the M2000 server or client. This chapter covers the server emergency maintenance, client emergency maintenance, and emergency maintenance for the server power-off. 12.1 Guide to Emergency Maintenance of the M2000 Server This describes the guide to emergency maintenance of the M2000 server. 12.2 Guide to Emergency Maintenance of the M2000 Client This section provides guidance for emergency maintenance of the M2000 client. 12.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure This describes the guide to emergency maintenance of the M2000 server in the case of power failure. The abnormal power-off of the M2000 server forces the Solaris and the M2000 application to exit, thereby causing severe faults in the Solaris. In the case of abnormal poweroff, you need to reset the M2000 server and take measures to restore the system based on the symptoms.
Issue 05 (2008-05-20)
12-1
12.1 Guide to Emergency Maintenance of the M2000 Server

This describes the guide to emergency maintenance of the M2000 server. The emergency maintenance of the M2000 server is based on the backup mode. If the server breaks down or a fault occurs in the server, restore the server in the following ways:
l
Through tapes Back up the Solaris to tapes through ufsdump, and then restore the Solaris from the tapes. Through the backup server Restore the Solaris from the backup server if a full system backup is created through the Veritas software.
By reinstalling the Solaris If the system is not backed up, all the user data will be lost if the system crashes owing to a fatal error.
12.2 Guide to Emergency Maintenance of the M2000 Client

This section provides guidance for emergency maintenance of the M2000 client. If the M2000 client breaks down or a fault occurs in the client, you can restore the client in the following ways:
l l
Reinstall the operating system on the M2000 client. Reinstall the M2000 system. For details, refer to the software installation manual related to each server type.
12.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure
This describes the guide to emergency maintenance of the M2000 server in the case of power failure. The abnormal power-off of the M2000 server forces the Solaris and the M2000 application to exit, thereby causing severe faults in the Solaris. In the case of abnormal poweroff, you need to reset the M2000 server and take measures to restore the system based on the symptoms. 12.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss of System Files This describes how to handle the failure to start the Solaris operating system owing to the loss of system files. 12.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You to Run fsck Manually This describes how to manually run the fsck command in maintenance mode. 12.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System This describes how to handle the loss of database device files after the file system is restored. 12.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact This describes how to handle the failure to restore the database though the file system is intact.
12.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss of System Files
This describes how to handle the failure to start the Solaris operating system owing to the loss of system files.
Symptom
The server cannot be started. The system displays the message Cannot open `/etc/ path_to_inst` . After resetting the server, you are not allowed to log in to the server through the telnet or to ping the server. Use the serial port or the SC port to view the following information:
Cannot open `/etc/path_to_inst` Program terminated
The system stops functioning and is switched to the ok status.
Fault Handling
Unexpected power-off of the server damages the Solaris operating system. As a result, the system file path_to_inst is lost. The Solaris operating system, therefore, fails to start. 1. 2. Press Stop+a or Ctrl+Break to exit the startup and switch to the ok status. Only the keyboard delivered with the server has the stop key. Insert the boot disk of the Solaris operating system, that is, the first of the two installation disks, into the CD-ROM. Run the following command in the ok status: ok boot cdrom -s 3. Run the following commands to search for the name of the basic device corresponding to the system root folder: # cd /dev/dsk # ls 4. Mount this basic device to the /mnt mount point. Assume that the name of the basic device corresponding to the root folder is c0t0d0s0. Run the mount /dev/dsk/c0t0d0s0 /mnt command to switch to /mnt to restore the Solaris operating system.
CAUTION
If the /etc/path_to_inst file is lost, restore it using the path_to_inst-INSTALL template stored in the /etc folder. Run the following commands: # cd /mnt/etc # cp path_to_inst-INSTALL path_to_inst 5. Run the following commands to reset the Solaris operating system: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6
After the system starts, run the fsck -y command to restore the system file. Start the Sybase and M2000 application manually.
12.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You to Run fsck Manually
This describes how to manually run the fsck command in maintenance mode.
Symptom
The server cannot be started and can be switched only to the maintenance mode. The system displays the message Run fsck manually (fsck -F ufs /dev/rdsk/ c*t*d*s*). After resetting the server, you are not allowed to log in to the server through the telnet. Use a serial port or the SC port to view the following information:
WARNING - Unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c*t*d*s*). Exit the shell when done to continue the boot process. Type control-d to proceed with normal startup, (or give root password for system maintenance):
NOTE
The warning shows Unable to repair the / filesystem, where filesystem may refer to other partitions.
Fault Handling
The exceptional server power-off damages the Solaris. You must restore the Solaris manually. 1. 2. 3. Log in to the server as user root. Modify the file system. # fsck -y Check the restored information. Ensure that the file systems of all partitions are correct, that the file system of the damaged partition is restored, and that the database device files are complete. After the file system is restored, switch to the /export/home/sybdev folder and check whether the database device files are complete. The database device files are as follows:
master.dat sysproce.dat tmp_dev.dat
4.
5.
Ensure that the SYB.krg file is deleted. When the server powers off abnormally, the Sybase also exits abnormally and the /opt/sybase/SYB.krg file is not deleted. The file disables the startup of the Sybase. Therefore, delete the file if it still exists after you reset the Solaris. If any database device files are lost, refer to 12.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System.
12.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System
This describes how to handle the loss of database device files after the file system is restored.
12-4
Issue 05 (2008-05-20)
Symptom
After the server is reset and the file system is restored, some database device files in /export/ home/sybdev are lost. If the device file related to the system database, such as master.dat or sysprocs.dat, is lost, the database fails to start. If the device file related to certain application database is lost, the corresponding application database and the services related to this database fail to start.
Fault Handling
The abnormal power-off leads to the loss of the database device file dependent on the file system. 1. Delete the following three files, and then reinstall the Sybase database:
l l l
/opt/sybase/interfaces /export/home/sybdev/master.dat /export/home/sybdev/sysprocs.dat
2.
When installing the database, select reinstall to re-establish the application databases of M2000. For details on the installation of the Sybase and M2000, see the software installation manual related to each server type. Perform the full backup and the incremental backup to restore the data in the database and the M2000 configuration files. For details, refer to 10 Backing Up and Restoring the M2000.
3.
12.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact
This describes how to handle the failure to restore the database though the file system is intact.
Symptom
The M2000 fails to start even after the server and the database are started. The system prompts an exception in the database. When you check the application database, you find that it is in the offline status. The database log file /opt/sybase/ASE-15_0/install/SYB.log records the following error information:
00:00000:00001:2005/07/24 18:56:29.08 server Error: 926, Severity: 14, State: 1 00:00000:00001:2005/07/24 18:56:29.08 server Database 'swmdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the SQL Server errorlog for information as to the cause.
Fault Handling
The database is processing transactions when the server is switched off abnormally. The abnormal exit leads to an exception in the database. To handle the fault, perform the following steps: 1. Log in to the M2000 installation directory as user root and run the environment variable script. The default M2000 installation directory is /opt/OMC. # cd M2000 installation path
# . ./svc_profile.sh 2. Switch to user dbuser and log in to the database as user sa. Then, run the following commands: # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_configure "allow updates", 1 2> go 1> update master..sysdatabases set status =-32768 2> Where name="database_name" 3> go 1> shutdown SYB_BACKUP 2> go 1> shutdown 2> go Switch back to user root. 1>exit -bash-3.00$ exit
CAUTION
The parameter database_name indicates the name of the faulty database. 3. Log in as user root and check whether all the values in /opt/sybase/SYB.cfg are the default values. If all the values are the default values, restore the database using the history files. Run the following commands: # cd /opt/sybase # cp SYB.026 SYB.cfg # chown dbuser:staff SYB.cfg 4. Switch to user dbuser to start the database. Exit the database as user dbuser, and then switch back to user root to run the environment variable. # su - dbuser -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ./startserver -f ./RUN_SYB
NOTE
About 30s is required for starting the database service. Wait until the database service is started.
Press Enter. After the prompt -bash-3.00$ is displayed, run the following command: -bash-3.00$ nohup ./startserver -f ./RUN_SYB_back > /dev/null -bash-3.00$ exit # cd M2000 installation path # . ./svc_profile.sh
CAUTION
/opt/OMC is the default installation path of the M2000 server software. Replace the M2000 installation directory with the actual installation directory. 5. Switch to user dbuser and log in as user sa. Then, run the following commands: # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> update master..sysdatabases set status =0 2> Where name="database_name" 3> go 1>exit 6. Run the following commands to reset the database: -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ./startserver -f ./RUN_SYB
NOTE
Press Enter. After the prompt -bash-3.00$ is displayed, run the following command: -bash-3.00$ nohup ./startserver -f ./RUN_SYB_back > /dev/null
Issue 05 (2008-05-20)
12-7
13 Troubleshooting the M2000
13
About This Chapter
Troubleshooting the M2000
This chapter describes the procedures for troubleshooting the M2000. 13.1 Procedure for Troubleshooting the M2000 This describes the procedure for troubleshooting the M2000. The procedure usually consists of three phases: collecting data, locating faults, and handling faults. 13.2 Collecting M2000 Site and Software Information This describes how to collect the M2000 site and software information. 13.3 Collecting Fault Data Using the M2000 Log Information Collector This describes how to collect fault data by using the M2000 log information collector.
Issue 05 (2008-05-20)
13-1
13.1 Procedure for Troubleshooting the M2000

This describes the procedure for troubleshooting the M2000. The procedure usually consists of three phases: collecting data, locating faults, and handling faults.
Collecting Data
When a fault occurs, collect the following data:
l l l l l l l l l
Time when the fault has occurred Place where the fault has occurred Measures taken and the results Version information IP addresses Alarm information Logs Internal fault locating information Database deadlock information
NOTE
l l l
Logs are categorized into user logs, system logs, and trace files. Collect the internal fault location information through the M2000 log collector. For details on using the tool, refer to 13.3 Collecting Fault Data Using the M2000 Log Information Collector. For details on viewing database deadlock information, refer to 15.2.6 How to View Database Deadlock Information.
Locating Faults
This describes the procedure for locating faults. The collection and analysis of faults help you know the causes of the faults. The M2000 system faults are categorized into hardware faults and software faults.
l
Hardware faults Hardware faults are the faults that occur in the M2000 server, client, or other network devices. The appearance of the hardware and indicators indicate the hardware faults clearly.
Software faults Software faults are the faults that occur in the M2000 software, Solaris, and Sybase.
Handling Faults
This describes how to handle faults based on different fault causes:
l
Hardware faults Refer to the manuals delivered with the associated hardware. Software faults For details on alarms, refer to the Help of the M2000 Mobile Element Management System.
13-2
Issue 05 (2008-05-20)
For details on faults of software installation, refer to the associated server type in the software installation manual related to each server type. For details on the client faults, refer to the M2000 Online Help. For details on the server faults, refer to the 15.4 FAQ About the M2000 Server Software.
l
Faults of the Solaris operating system Refer to the Solaris System Administrator Guide. Sybase faults Refer to the Sybase System Administrator Guide. Uncleared faults For the uncleared faults, collect all the information related to the faults by referring to Collecting Data and contact your Huawei local office for technical support.
13.2 Collecting M2000 Site and Software Information

This describes how to collect the M2000 site and software information. 13.2.1 Collecting the M2000 Site Information This describes how to collect the M2000 site information. 13.2.2 Collecting the Time of M2000 Fault Occurrence This describes how to find out the time when M2000 faults occur. 13.2.3 Collecting the IP Address of the M2000 Server This describes how to obtain the IP address of the M2000 server. 13.2.4 Collecting the Solaris Version This describes how to obtain the version information about the Solaris. 13.2.5 Collecting the Sybase Version This describes how to collect the Sybase version. 13.2.6 Collecting the M2000 Version This describes how to obtain the version information about the M2000.
13.2.1 Collecting the M2000 Site Information

This describes how to collect the M2000 site information.
Procedure
Collect the M2000 site information. Collect the following site information:
l l l l l
Site name Customer contact details Hardware model Date and time when a fault occurs Fault description
----End
13.2.2 Collecting the Time of M2000 Fault Occurrence

This describes how to find out the time when M2000 faults occur.
Procedure
Run the date command to check the time. ----End
Example
# date Thu Jul 28 09:56:39 EDT 2005
13.2.3 Collecting the IP Address of the M2000 Server

This describes how to obtain the IP address of the M2000 server.
Procedure
Run the ifconfig -a command to obtain the IP address, subnet mask, and MAC address of the M2000 server. ----End
Example
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.161.94.254 netmask ffffff00 broadcast 10.161.94.255 ether 0:3:ba:12:bb:93
13.2.4 Collecting the Solaris Version

This describes how to obtain the version information about the Solaris.
Procedure
Run the uname -aX command to find out the version information about the Solaris operating system. ----End
Example
# uname -aX
SunOS BackupServer 5.10 Generic_118833-36 sun4u sparc SUNW,Netra-240System = SunO S Node = BackupServer Release = 5.10 KernelID = Generic_118833-36
13-4
Issue 05 (2008-05-20)

Machine = sun4u BusType = <unknown> Serial = <unknown> Users = <unknown> OEM# = 0 Origin# = 1 NumCPU = 2
13.2.5 Collecting the Sybase Version

This describes how to collect the Sybase version.
Procedure
Run the following commands: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1>select @@version 2>go
NOTE
----End
Example
-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1>select @@version 2>go
Adaptive Server Enterprise/15.0.2/EBF 15062 ESD#1 N-OFF/P/Sun_svr4/OS 5.8/ ase1502/2493/64-bit/FBO/Thu Sep 20 16:52:15 2007
1> exit
13.2.6 Collecting the M2000 Version

This describes how to obtain the version information about the M2000.
Procedure
Run the displayVersion command to obtain the version information about the M2000. ----End
Example
Change to /opt/OMC, which is the default installation path of the M2000 server software. Run the following commands: # cd /opt/OMC # . ./svc_profile.sh # displayVersion
------------------------OMC Version-------------------------Product Name: iManagerM2000 Version: iManagerM2000V200R006CHSC01B017 Release Date: 08/17/07 -----------------Installed Mediation Version----------------<MGW> Match Version : iManagerM2000_UMG_MATCH_CHS_V200R006C01B001 NE Version is : UMG8900V200R007C01B024/G9MSC90 UMG8900V200R007C01B024 <MSCServer> Match Version : iManagerM2000_MSOFTX3000_MATCH_CHS_V200R006C01B001 NE Version is : MSC9880 MSOFTX3000V100R006C02B016/G9MSC90 MSOFTX3000V100R006C02B 016 <NodeB3812E> Match Version : iManagerM2000_NodeB3812E_MATCH_CHS_V200R002C03B052 NE Version is : BTS3812E-BTS3812AV100R006C01B061 <RAC> Match Version : iManagerM2000_RAC_MATCH_CHS_V200R006C01B103 NE Version is : RAC6610V200R005C02B012 <RNC> Match Version : iManagerM2000_RNC_MATCH_CHS_V200R002C03B009 NE Version is : BSC6800V100R006C01B061
13.3 Collecting Fault Data Using the M2000 Log Information Collector
This describes how to collect fault data by using the M2000 log information collector.
Context
l
The start_collector process and the start_collector_agent process provide the service of the log collector. The service of the log collector is started upon the startup of the operating system. You can manually stop or start the service after the service is started. To start the service, run the /opt/OMC/bin/start_collector command and the /opt/OMC/ bin/start_collector_agent command. To stop the service, run the /opt/OMC/bin/stop_collector command and the /opt/OMC/ bin/stop_collector_agent command.
13-6
Issue 05 (2008-05-20)
Procedure
Step 1 On the client, choose Start > Program > iManager M2000 Client > M2000 Log Information Collector . The M2000 Log Information Collector dialog box is displayed, as shown in Figure 13-1. Figure 13-1 M2000 Log Information Collector dialog box
NOTE
The shortcut menu M2000 Log Information Collector can be displayed when you choose Start > Program if you configure the shortcut menu during the installation of client. The default setting is iManager M2000 Client.
Step 2 In the Server Information area, enter the following information:

l l
Server Address: IP address of the server. Port: FTP server port number. The default port number is 10119. If you change this number, you must also change the server settings. To change the server settings, log in to the server as user root. Run the stop_collector -port old port number command to shut down the original port. Then, run the start_collector -port new port number command. FTP User Name: ftpuser. Password: password of the Solaris user, such as ftpuser.
l l
Step 3 In Items Selection, select time and the information to be collected.


NOTE
l l
Run the M2000 log information collector to collect fault information. Ensure that both the start_collector process and the start_collector_agent process are running on the server. To check whether the log information collector is running, you can run the ps -ef | grep start_collector | grep -v grep command. Check whether the start_collector process and the start_collector_agent process are running on the corresponding nodes. If the processes are not started, run the /opt/OMC/bin/start_collector command to start the start_collector process and run the /opt/ OMC/bin/start_collector_agent command to start the start_collector_agent process.
Step 4 In the Directory area, select the save directory of the collected log information. Step 5 Click Collect to start the collection. ----End
Result
By default, the collected information is saved as a package in the path M2000 client installation directory\client\diagnosis. If an error is displayed during the decompression of the package, you need to decompress the package to a path with fewer sub-layers.
13-8
Issue 05 (2008-05-20)
14 M2000 Command Reference
14
About This Chapter
M2000 Command Reference
This describes the functions and usage of M2000 commands. 14.1 M2000 Commands This describes the functions of common commands related to the M2000 service, along with application examples. The path M2000 Server Installation Path/bin stores all the commands used for the M2000 system maintenance. Before running commands, ensure that the Sybase works properly and that you already run the M2000 environment setting script svc_profile.sh. 14.2 UNIX Commands This describes the utility commands provided by the UNIX system, including the commands for operating directories, the commands for operating folders, the commands for viewing files, the commands for managing UNIX users, the commands for managing the system resource, and the commands for network communication.
Issue 05 (2008-05-20)
14-1
14.1 M2000 Commands

This describes the functions of common commands related to the M2000 service, along with application examples. The path M2000 Server Installation Path/bin stores all the commands used for the M2000 system maintenance. Before running commands, ensure that the Sybase works properly and that you already run the M2000 environment setting script svc_profile.sh. 14.1.1 svc_profile.sh Script This describes the function, path, and method of running the svc_profile.sh script. Before you run the commands on the M2000, you must run svc_profile.sh to set the operating environment. 14.1.2 start_svc Command This describes the function of the start_svc command and the users authorized to run this command. This also gives examples for the application of this command. 14.1.3 stop_svc Command This describes the function of the stop_svc command and the users authorized to run this command. This also gives examples for the application of this command. 14.1.4 kill_svc Command This describes the function of the kill_svc command and the users authorized to run this command. This also gives examples for the application of this command. Use the kill_svc command only in the case of a deadlock and an abnormal process. 14.1.5 svc_adm -cmd status Command This describes the function of the svc_adm -cmd status command and the users authorized to run this command. It also provides an example to explain the application. 14.1.6 svc_ps Command This describes the function of the svc_ps command and the users authorized to run this command. This also gives examples for the application of this command. 14.1.7 svc_adm -cmd reload Command This describes the function and user identity of the svc_adm -cmd reload command. The command is used to update the M2000 configuration information. This also gives an example to explain the application of the command. 14.1.8 svc_stacks Command This describes the function of the svc_stacks command and the users authorized to run this command. It also provides an example to explain the application of this command. 14.1.9 svc_adm -cmd status -sysagent all Command This describes the function of the svc_adm -cmd status -sysagent all command and the users authorized to run this command. Examples are employed to explain the application.
14.1.1 svc_profile.sh Script

This describes the function, path, and method of running the svc_profile.sh script. Before you run the commands on the M2000, you must run svc_profile.sh to set the operating environment.
Function
Before you run the commands on the M2000, run svc_profile.sh. This script sets the user operating environment such as the searching path and the dynamic searching path.
Path
The script is saved in the M2000 Server Installation Directory.
Operating Method
There are two ways to run the script: manually and automatically.
l
Run the script manually
Take the M2000 default directory /opt/OMC as an example. To manually run the script, run the following command: -bash-3.00$ . /opt/OMC/svc_profile.sh
NOTE
The symbol . exists before the command, and a space exists between the mark . and the mark /.
l
Run the script automatically
After the system is installed correctly, the script is added to the .profile file of user omcuser and user root. If you log in to the system as user omcuser or user root, the system automatically runs the script.
14.1.2 start_svc Command

This describes the function of the start_svc command and the users authorized to run this command. This also gives examples for the application of this command.
Function
The start_svc command starts all M2000 services. After the system starts, this command attempts to start each service again and displays a message to indicate that the service is started.
NOTE
If the installed match version is of V200R005 or of earlier, run the start_svc command. The following message is displayed.
iManagerM2000_SGSN_MATCH_ENG_V200R005C01B002 has not been executed commands{DcNeIns and DcInit}, please run them if necessary!
Ensure that the M2000 system services are stopped. Initiate the mediation layer. # cd /opt/OMC/med/RNCNE/iManagerM2000_RNC_MATCH_ENG_V200R002C02B004 # DcNeIns -i . # DcInit Run the command start_svc to start the M2000 system service.
Permitted Users
User root is authorized to run the start_svc command.
Example
# start_svc
==================== Starting Services ... TAO Naming Service is running
Issue 05 (2008-05-20)
14-3

TAO Notification Service is running Monitor_Service already running. imapsysd already running. LogServer [starting... ] svc_adm:info:service with this name is already running ... ============================ Finished Starting Services.
14.1.3 stop_svc Command

This describes the function of the stop_svc command and the users authorized to run this command. This also gives examples for the application of this command.
Function
The stop_svc command stops all M2000 services. If the system is not started, this command attempts to stop each service and then displays error messages.
Permitted Users
User root is authorized to run the stop_svc command.
Example
# stop_svc
============= Stopping System ... SystemMonitor [stopped ] EventManager [stopped ] LogServer [stopped ] ... ==================== Finished Stopping System.
14.1.4 kill_svc Command

This describes the function of the kill_svc command and the users authorized to run this command. This also gives examples for the application of this command. Use the kill_svc command only in the case of a deadlock and an abnormal process.
Function
The kill_svc command stops services and processes of the M2000 system through the process killing mechanism supported by the primary layer operating system. Running this command may lead to service data loss or abnormal services. Therefore, use this command only when all other measures to restore the services of the system fail. Generally, the stop_svc command is used to stop the M2000 services. Therefore, run kill_svc only in the case of a deadlock and an abnormal process.
Permitted Users
User root is authorized to run the kill_svc command.
Example
# kill_svc
14.1.5 svc_adm -cmd status Command

This describes the function of the svc_adm -cmd status command and the users authorized to run this command. It also provides an example to explain the application.
Function
The svc_adm -cmd status command is used to check the operational status of all the M2000 services.
Permitted Users
Users root and omcuser are authorized to run the svc_adm -cmd status command.
Example
-bash-3.00$ svc_adm -cmd status The status of the M2000 services is Running, No License, or Not Running.
14.1.6 svc_ps Command

This describes the function of the svc_ps command and the users authorized to run this command. This also gives examples for the application of this command.
Function
The svc_ps command is used to check the operational status of the M2000 service processes.
Permitted Users
Users root, omcuser, and dbuser are authorized to run the svc_ps command.
Example
-bash-3.00$ svc_ps The command result shows all the M2000 processes that are running.
14.1.7 svc_adm -cmd reload Command

This describes the function and user identity of the svc_adm -cmd reload command. The command is used to update the M2000 configuration information. This also gives an example to explain the application of the command.
Function
This command loads the configuration file to the configuration module to update the configuration in real time. This means that the M2000 services are not stopped when the system updates the configuration information.
Permitted Users
Users root and omcuser are authorized to run the svc_adm -cmd reload command.
Example
-bash-3.00$ svc_adm -cmd reload After you run the command, the data in the configuration module is the same as the data in the configuration files.
14.1.8 svc_stacks Command

This describes the function of the svc_stacks command and the users authorized to run this command. It also provides an example to explain the application of this command.
Function
The svc_stacks command collects the stack information on the M2000 service processes for locating and debugging system faults.
Permitted Users
User root is authorized to run this command.
Example
# svc_stacks The queried stack information is stored in the file /M2000 server installation path/var/logs/ imap_stacks.YY_MM_DD__HH_NN_SS.trace. The default installation path of the M2000 server software is /opt/OMC. The result file is identified on the basis of the query time. In the file name, YY stands for year, MM for month, DD for day, HH for hour, NN for minute, and SS for second.
14.1.9 svc_adm -cmd status -sysagent all Command

This describes the function of the svc_adm -cmd status -sysagent all command and the users authorized to run this command. Examples are employed to explain the application.
Command Function
You can use this command to view the current status of the M2000 service on each node of the system.
Authorized Users
Users root and omcuser are authorized to run the svc_adm -cmd status -sysagent all command.
Application Example
Log in to any node of the SLS system and run the following command: -bash-3.00$ svc_adm -cmd status -sysagent all In the command result, you can view the running status of the M2000 service on each node of the system. The running status can be Running, No License, or Not Running.
14.2 UNIX Commands

This describes the utility commands provided by the UNIX system, including the commands for operating directories, the commands for operating folders, the commands for viewing files, the commands for managing UNIX users, the commands for managing the system resource, and the commands for network communication. 14.2.1 Commands for Operating UNIX Folders This describes the commands for operating UNIX folders. This also gives function descriptions and examples. 14.2.2 Commands for Operating UNIX Files This describes the usage of the operation commands commonly used for files in the UNIX operating system, including function description and application examples. 14.2.3 Commands for Viewing UNIX Text Files This describes the commands used for viewing UNIX text files, their functions, along with examples. 14.2.4 Commands for Managing UNIX Users This describes the user management commands that are frequently used in the UNIX system. This also describes the functions of these commands and gives some examples. Only user root and the authorized users can add, modify, or delete users and user groups. 14.2.5 Commands for Managing UNIX System Resources This describes the commands for managing UNIX system resources. This also describes the functions of these commands and gives some examples. 14.2.6 Commands for Network Communication on the UNIX System This describes the commands for network communication on the UNIX system. This also describes the functions of these commands and gives some examples.
14.2.1 Commands for Operating UNIX Folders

This describes the commands for operating UNIX folders. This also gives function descriptions and examples. 14.2.1.1 pwd Command This describes the function and example of the pwd command. The pwd command is used to view the current working folder. 14.2.1.2 cd Command This describes the function and example of the cd command. 14.2.1.3 mkdir Command This describes the function and example of the mkdir command. 14.2.1.4 rmdir Command This describes the function and example of the rmdir command. 14.2.1.5 ls Command This describes the function, format, option, parameter, and example of the ls command.
Issue 05 (2008-05-20)
14-7
pwd Command
This describes the function and example of the pwd command. The pwd command is used to view the current working folder.
Function
View the current working folder.
Example
# pwd
/export/home/sybase
NOTE
Unlike DOS, the UNIX system does not always display the folder name. You must run the pwd command periodically to view the current working folder.
cd Command
This describes the function and example of the cd command.
Function
The cd command is used to switch the current folder to another folder. This command applies to both absolute and relative paths.
Example
l
To switch to the home folder, run the following command:
# cd
l
To switch to the system root directory, run the following command:
# cd /
l
To switch back one folder, run the following command:
# cd ..
l
To switch back two folders, run the following command:
# cd ../..
l
To switch to the /export/home/sybase folder by the absolute path, run the following command:
# cd /export/home/sybase
NOTE
If you run the cd command that is not followed by any parameter, the system is switched back to the home folder.
mkdir Command
This describes the function and example of the mkdir command.
Function
The mkdir command is used to create a folder. When the path to the created folder is determined, absolute and relative paths can be used.
Example
To create a subfolder data in /home1/omc, run the following command: # mkdir /home1/omc/data If the current folder is /home1/omc, run the following command: # mkdir data
rmdir Command
This describes the function and example of the rmdir command.
Function
The rmdir command is used to delete an empty folder.
CAUTION
l
If the folder to be deleted is not empty, you must delete the files in the folder before running the rmdir command. To delete the current folder, you must switch to the upper-level folder.
Example
To delete the data subfolder in the /home1/omc folder, run the following command: # rmdir /home1/omc/data If the current folder is /home1/omc, run the following command: # rmdir data
ls Command
This describes the function, format, option, parameter, and example of the ls command.
Function
The ls command is used to list the files and subfolders in a folder. Run the ls command without any parameter to list the content of the current folder. Run the ls command with parameters to list the information about the size, type, and privileges of the file, and the date when the file was created and modified.
Command Format
ls Option Directory or File
Option Description
Several individual options and a combination of options can be used for the ls command. Place the prefix - before the options. Table 14-1 lists some common options. Table 14-1 Option description of the ls command Option -a -F Description Lists all files including the hidden files, that is, the files starting with a dot ., for example, the .login file. Specifies the type of a file by suffix signs. The meaning of the suffixes are as follows:
l l l l
/: for folder files =: for pipe files @: for sign-linking files *: for executable files
-l
Lists the detailed information about a file, such as the file type, privileges, number of links, owner, file group, file size, file name, and the date of the last modification.
If the file is a sign-linking file, then the -> sign is added at the end of the file name for pointing to the linked file.
Example
To view the long-form content of the files in the current folder, run the following command: # ls -l |more
total 11094632 drwxr-xr-x 2 drwxr-xr-x 14 drwxr-xr-x 3 drwxr-xr-x 2 -rw-r--r-1 drwxr-xr-x 2 drwxr-xr-x 7 drwxr-xr-x 2 drwxr-xr-x 2 drwxr-xr-x 7 drwxr-xr-x 3 -rw-r--r-1 -rw-r--r-1 drwxr-xr-x 2 drwxr-xr-x 2 drwxr-xr-x 6 -rw-r--r-1 -rw-r--r-1 sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase sybase staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff 1024 Sep 5 2001 bin 512 Sep 5 2001 charsets 512 Sep 5 2001 collate 512 Sep 5 2001 config 2048000000 Mar 6 09:50 data_dev.dat 512 Sep 5 2001 devlib 512 Sep 5 2001 diag 512 Sep 5 2001 hs_data 512 Sep 5 2001 include 512 Sep 5 2001 init 512 Sep 5 2001 install 268 Sep 5 2001 interf.old 402 Oct 29 15:25 interfaces 1024 Sep 5 2001 lib 512 Sep 5 2001 license 512 Sep 5 2001 locales 2048000000 Mar 6 10:51 log_dev.dat 2048000000 Mar 6 10:36 log_dev1.dat
14-10
Issue 05 (2008-05-20)

drwxr-xr-x -rw-r--r-drwxr-xr-x --More-5 sybase 1 sybase 8 sybase staff staff staff

512 Sep 5 2001 pad 5242880 Feb 19 10:10 phase2.dat 512 Sep 5 2001 sample
After you run the ls -l command, the result may be displayed in several screens. To view the file contents, one screen at a time, run one of the following commands:
l l
# ls -la | more $ ls -la>ccc Save the command output to the ccc file, and then run the following command to view the output on screen at a time: # more ccc
After you run the ls -l command, seven columns of information are displayed, which are described as follows:
l
The first column consists of 10 characters. The first character indicates the file type. For example, the character - refers to a common file and the character d refers to a folder. The following nine characters are three triplets indicating the access privileges of the file owner. The first triplet pertains to the owner, the middle triplet pertains to members of the user group, and the right-most one pertains to other users in the system. For example, the characters r, w, and x indicate that the user has the privileges to read, write, and execute a file, whereas the character - indicates that the user does not have any relevant privileges for the file. The second column indicates the number of links of the file. The third and fourth columns display information such as the owner of the file, and the user group to which the file belongs. The fifth column shows the size of the file in bytes. The sixth column shows the time and date when the file is last modified. The seventh column shows the file name.
l l
l l l
14.2.2 Commands for Operating UNIX Files

This describes the usage of the operation commands commonly used for files in the UNIX operating system, including function description and application examples. 14.2.2.1 cp Command This describes the function, format, option, and parameter of the cp command. It also provides an example of the cp command. 14.2.2.2 mv Command This describes the function, format, and example of the mv command. 14.2.2.3 rm Command This describes the function, format, option, and example of the rm command. 14.2.2.4 chmod Command This describes the function, format, option, and example of the chmod command. 14.2.2.5 chown Command This describes the function, format, option, parameter, and example of the chown command. 14.2.2.6 chgrp Command This describes the function, format, option, parameter, and example of chgrp command.
14.2.2.7 find Command This describes the function, format, parameter, and example of the find command. 14.2.2.8 tar Command This describes the function, format, option, and example of the tar command. 14.2.2.9 gtar Command This describes the function, format, parameter options, and instance of the gtar command. 14.2.2.10 compress Command This describes the function, format, and example of the compress command. 14.2.2.11 uncompress Command This describes the function, format, and example of uncompress command. 14.2.2.12 pack Command This describes the function, format, and example of the pack command. The pack command is used to compress files and save memory space. 14.2.2.13 unpack Command This describes the function, format, and example of the unpack command. 14.2.2.14 pkgadd Command This describes the function, format, option, and example of the pkgadd command. 14.2.2.15 pkgrm Command This describes the function, format, and example of the pkgrm command.
cp Command
This describes the function, format, option, and parameter of the cp command. It also provides an example of the cp command.
Function
The cp command is used to copy the contents of a file to another file.
Command Format
cp option source file object file
Option Description
The option -r indicates recursively copying a folder. That is, when copying a folder, copy the files and subfolders included in the folder, and files and subfolders in the subfolders until the last level of the folder.
Example
To copy the old_filename file in the current folder to the file new_filename, run the following command: # cp old_filename new_filename
mv Command
This describes the function, format, and example of the mv command.
Function
The mv command is used to move and rename a file.
CAUTION
l l
After you run the mv command, only the target file instead of the source file exists. After you run the cp command, the source file still exists and the target file is generated.
Command Format
mv source file object file
Example
To move the old_filename file in the root directory to the /home1/omc folder, and rename the source file to new_filename, run the following command: # mv old_filename /home1/omc/new_filename
rm Command
This describes the function, format, option, and example of the rm command.
Function
The rm command is used to delete a file.
CAUTION
l
In the UNIX system, a file, once deleted, cannot be restored. Therefore, use the -i option to avoid the deletion of a file by mistake. To delete a folder, run either of the following commands: rmdir or rm -r. The difference between the two commands is: rmdir deletes only empty folders but rm -r deletes any folder.
Command Format
rm Option file
Option Description
l l
-i: refers to interactive operations. Your confirmation is required before a command is run. -r: recursively deletes a folder. That is, when deleting a folder, delete the files and subfolders included in the folder, and files and subfolders in the subfolders until the root folder.
Issue 05 (2008-05-20)
Example
To delete the old_filename file in the current folder, run the following command: # rm -i old_filename
chmod Command
This describes the function, format, option, and example of the chmod command.
Function
The chmod command is used to change the access rights of a directory or a file.
Format
chmod option directory or file Based on different notation methods of the option in the command, two modes are available:
l
Symbol mode chmod objectoperatorrights file Digit mode chmod lmn file
Option Description
l
Symbol mode Table 14-2 lists common options in symbol mode of the chmod command. Table 14-2 Common options in symbol mode of the chmod command Option Object Option Detail u g o Description Owner of a file Users sharing the same group with the file owner Other users except the file owner and the users sharing the same group with the file owner All users Add a right Cancel a right Set a right
a Operator + = Digit mode The option lmn represents the following digits:
l: the rights of the owner

14-14

m: the rights of the users sharing the same group with the owner n: the rights of other users in the system
The value of each digit is equal to the sum of the values of r (read right), w (write right), x (execute right), or - (no right) in each group. In each group, r = 4, w = 2, x = 1, and - = 0. In the following example -rwxr-xr-- 1 rms sbsrms 46098432 May 12 16:02 sdh*, the access rights of the file sdh is represented by the symbols rwxrxr--. The nine symbols are divided into three groups, with three symbols as a group. The three groups represent the rights of the file owner, the rights of the users sharing the same group with the file owner, and the rights of other users in the system. The three groups can be represented in digits 754, which is calculated according to the formulas: 7 = 4 + 2 + 1, 5 = 4 + 0 + 1, and 4 = 4 + 0 + 0.
Parameter Description
File: indicates the name of the file whose rights are changed.
Example
l
Symbol mode Authorize the file1 owner with the read, write, and execute rights. Authorize the users sharing the same group with the file owner with the read and execute rights. Authorize other users with the read and execute rights. Run the following command: # chmod u=rwx,go=rx file1 To authorize all the users with the read and write rights, run the following command: # chmod a=rw file2
Digit mode Authorize the file1 owner with the read, write, and execute rights. Authorize the users sharing the same group with the file owner with the read and execute rights. Authorize other users with the read and execute rights. Run the following command: # chmod 755 file1 To authorize all the users with the read and write rights, run the following command: # chmod 666 file2
NOTE
To configure the rights of a file for users in a group and other users in the system in symbol mode, you must authorize these users with the execute right of the directory where a file exists. Run the following command for the directory that requires you to set rights: # chmod u=rw,+x . You can also run the following command: # chmodu=rwx,go=x . In this command, the symbol "." indicates the current directory.
In digit mode, r = 4, w = 2, x = 1, and - = 0. These mappings are set according to the binary mode. For the three symbols in a group, which represent the read right, the write right, and the execute right, assign the binary value 1 if a symbol has the corresponding right and assign the binary value 0 if a symbol does not have the corresponding rights. Take the previous file sdh as an example. The file rights are represented by the symbols rwxr-xr--. After converting the symbols into a binary value, you can obtain "111101100". The binary value is divided into three 3-digit groups, with each group representing a file right. After converting the binary value of each group into a decimal value, you can obtain three values: 7, 5, and 4.
Issue 05 (2008-05-20)
14-15
chown Command
This describes the function, format, option, parameter, and example of the chown command.
Function
The chown command is used to modify the owner of a file. In most UNIX systems, this command can be run only by the super user.
Command Format
chown Option owner file
Option Description
l l
-f: runs the command forcibly without displaying errors -R: recursive folder
l l
Owner: the modified owner File: the file of the owner to be modified
Example
l
Assume that there is a user new_owner and a file in the system. Run the following command to change the owner of the file to new_owner: # chown new_owner file Assume that there is a user M2000 in the system. Change the owner of all files in the / export/home/sybase folder and the subfolders to M2000: # chown CR M2000 /export/home/sybase
chgrp Command
This describes the function, format, option, parameter, and example of chgrp command.
Function
The chgrp command is used to move all files from the user group to which you belong, to another user group. That is, you belong to at least two user groups at the same time.
Command Format
chgrp Option group file
Option Description
l l
-f: runs the command forcibly without displaying errors -R: recursive folder
14-16
l l
Group: the modified user group File: the file the user group of which is to be modified
Example
To change the user group file to new_group, run the following command: # chgrp new_group file
CAUTION
The new user group to which a file is moved should be created. Run the groups command to list the groups to which you belong. For details on how to create a user group, see 14.2.4 Commands for Managing UNIX Users. After the owner or group of a folder is changed, the folder does not belong to that user or user group any more. The attributes of the subfolders and files in the folder, however, are retained. Run the chown command to modify the owner and the user group of a file at the same time: # chown omc:staff file1 For example, run the command to modify the owner of file1 to omc and the group to staff.
find Command
This describes the function, format, parameter, and example of the find command.
Function
The find command is used to search for a file that meets the preset conditions in the specified folders and subfolders. By using this command, you can find the file even if you forget the correct path of the file.
Command Format
find folder condition
l
Folder: indicates the folder to be searched. You can enter multiple folder names. Separate the folder names by using spaces. Condition: indicates the conditions for file search, such as the file name, owner, and time of the last modification.
Table 14-3 describes the conditions for file search.
Issue 05 (2008-05-20)
14-17
Table 14-3 Conditions for file search Condition -name name -print -size n -type x Description The name of the file or folder to be searched. Wildcards, such as -name '*.c', can be used. Prints the path that meets the conditions. Searches for the files that use n blocks. Searches for files by file type. The file type x includes:
l l l l l
d: directory f: file b: block c: character p: pipe
-user user -group group -links n -atime n -mtime n -exec command {}\;
Searches all files of user. The value of user can be a user name or UID. Searches all files of the user group. The value of group can be a user group name or GID. Searches all files with the number of links as n. Searches the files accessed before n days. Searches the files modified before n days. Uses the found file as the object of the command to be run. Put the parameters to be used in the command execution between { and }.
Table 14-4 describes the logical operators of conditions. Table 14-4 Logical operators of conditions Logical Operator ! -o Mean ing non or and Example ! -name "*.c" -size +10 -o -links 3 -size +10 -links 3 Description All the files except those with the extension name as .c All the files with more than 10 blocks or with 3 links All the files with more than 10 blocks and with 3 links
In the preceding table, +10 stands for more than 10 blocks and -10 for fewer than 10 blocks.
Example
To search for files in the /tmp folder with the file name starting with c, and then print the paths, run the following command: # find /tmp -name "c*" -print
/tmp/ctisql_0WBJgt /tmp/ctisql_0dznJ_ /tmp/ctisql_0CpW34 /tmp/ctisql_0FO4vs
To search the file test in the current folder and then print the paths, run the following command: # find . -name test -print
./Report/reloc/resin1.2.0/conf/test ./Report/reloc/resin1.2.0/doc/examples/login/WEB-INF/classes/test ./Report/reloc/resin1.2.0/doc/examples/tags/WEB-INF/classes/test
NOTE
The search may take several minutes. To save time, you can run this command in the background. That is, the output for the command is exported to a file for later query. End the command line with & so that the system runs the command in the background. For example, # find / -name "abc*" -print > abc.file & After the search is complete, run the following command to view the result of the search: # cat abc.file Different users may have different privileges for the same file. Therefore, ordinary users may find only some files of the system. To list all the files that meet the set conditions, log in as a super user and search from the root directory.
tar Command
This describes the function, format, option, and example of the tar command.
Function
The tar command is used to combine several files into one archive and save it to a tape or disk. When one of the files is required, obtain the file directly from an archive.
Command Format
tar function options modification options file
Option Description
l l
function options: sets the actions, such as read and write, of the tar command modification options: modifies the actions of the tar command
Table 14-5 describes the options of the tar command.
Issue 05 (2008-05-20)
14-19
Table 14-5 Option description for the tar command Option Function options Specified Option r x Description Adds the specified file to an archive. Reads a file in an archive. If the file name is a folder, this option reads the subfolders included in the folder. This option is often used. Creates an archive. This option is often used. Creates a file at the beginning of an archive rather than add the file in the last file. Activates the display mode. The names of all the processed files are displayed. This option is often used. Activates the confirmation mode. Your confirmation is required before each file is processed. Indicates that an archive is a file. If this parameter is skipped, the preset tape or disk is used as the object. This option is often used.
c g Modification options v
Example
l
Run the tar command to back up files. To back up all the files and subfolders in the /export/home/sybdev folder in the current folder to the default device and view the file information during the backup, run the following command: # tar cv /export/home/sybdev In current folder, back up all the files and subfolders in the /export/home/sybdev folder to the databak.tar file, and to view the file information during the backup, run the following command: # tar cvf databak.tar /export/home/sybdev
Use tar to restore files. To restore the files in the default device to a hard disk, and to view the file information during the restoration, run the following command: # tar xv In current folder, restore the databak.tar file to the /export/home/sybdev folder, and to view the file information during the restoration, run the following command: # tar xvf databak.tar
14-20
Issue 05 (2008-05-20)
CAUTION
l l
Do not enter "-" on the left of the function and modification options in the tar command. Run the following tar command to pack several files into a package: # tar cvf filebak.tar file1 file2 file3 Run the previous command to pack file1, file2, and file3 into a package named filebak.tar. The names of the disk and tape devices used in file backup and restoration in the tar command may vary according to the UNIX system. Check carefully before running the command.
gtar Command
This describes the function, format, parameter options, and instance of the gtar command.
Function
The gtar command can merge multiple files into an archive and store it in tapes or disks. You can obtain the required files from an archive, if required.
Format
gtar function options modification options file to be backed up or restored
Option Description
l l
Function option: sets the actions of the gtar command, such as read or write. Modification option: modifies the actions of the gtar command.
Table 14-6 lists some options. Table 14-6 Descriptions of gtar command options Option Function option Example r x c g Modification option v w Description Adds the specified file to end of an archive. Reads a file in the archive. If the name is a directory, its sub directories are also read. This option is common. Creates a new archive. This option is common. Creates a file from the beginning of the archive instead of the end of the last file. Starts the display mode. The gtar command can display all names of the processed file. This option is common. Activates the confirm mode. The gtar command requests you to confirm before processing each file.
14-21
Issue 05 (2008-05-20)
Option
Example f
Description Indicates that the archive is a file. Omission of this option indicates that the object is the preset disk or tape. This option is common.
Instance
l
Run the gtar command to back up files. In the current directory, back up all the files and folders in /export/home/sybdev to the default device. During the backup, the file information is displayed. # gtar cv /export/home/sybdev In the current directory, back up all the files and folders in /export/home/sybdev and save them as databak.tar. During the backup, the file information is displayed. # gtar cvf databak.tar /export/home/sybdev
Run the gtar command to restore files. Restore the files of default devices in the backup files to a hard disk. During the restoration, the file information is displayed. # gtar xv In the current directory, decompress the backup file databak.tar to /export/home/ sybdev. During the restoration, the file information is displayed. # gtar xvf databak.tar
CAUTION
l l
There is no - symbol before the function option and modification option of gtar. The gtar command can pack multiple files. The command is as follows: # gtar cvf filebak.tar file1 file2 file3 This command packs the three files, that is, file1, file2, and file3, into the file named filebak.tar. Under different UNIX systems, when using gtar to back up or restore files, note that names of the floppy disk and tape are different. Ensure that you use the right names.
compress Command
This describes the function, format, and example of the compress command.
Function
The compress command is used to compress files and save the memory space. The name of the compressed files ends with .Z. The command for decompressing such files is uncompress.
Command Format
compress file
Example
To compress a file, run the following command: # compress file
CAUTION
The difference between the tar command and the file compressing commands is as follows: The tar command packs or combines files and packs many folders or files into a package. To compress the combined files *.tar, use the compress or pack command.
uncompress Command
This describes the function, format, and example of uncompress command.
Function
The uncompress command is used to decompress the compressed files. The command for compressing files is compress.
Command Format
uncompress compressed file ending with ".Z"
Example
To decompress the file.Z file, run the following command: # uncompress file.Z
pack Command
This describes the function, format, and example of the pack command. The pack command is used to compress files and save memory space.
Function
Run the pack command to compress files. The name of the compressed files ends with .Z. The space achieved through compression depends on file types. To extract files, use the unpack command.
Command Format
pack file
Example
To pack a file, run the following command: # pack file
CAUTION
l
Do not run the pack command to compress files of small sizes. To compress such files, use the pack command with the option -f for forced compression. # pack -f filename The difference between the tar command and the file compression commands is as follows: The tar command packs or combines files and packs many folders or files into a package. To compress the combined files *.tar, use the compress or pack command.
unpack Command
This describes the function, format, and example of the unpack command.
Function
The unpack command is used to extract the packed files. To pack files, use the pack command.
Command Format
unpack compressed file ending with ".Z"
Example
To extract the file.Z file, run the following command: # unpack file.Z
pkgadd Command
This describes the function, format, option, and example of the pkgadd command.
Function
The pkgadd command is used to send a file package to the system for execution. To remove a package from the system, run the pkgrm command.
Command Format
pkgadd option file package name
Option Description
-d device: to install or copy a package from the device. The device can be an absolute path, the identifier of a tape, or a disk such as /var/tmp or /floppy/floppy_name, or a device name such as /floppy/floppy0.
Example
To send a file package in the current folder to the file1 file, run the following command: # pkgadd -d . file1
The dot in the command indicates that the folder is the current folder.
pkgrm Command
This describes the function, format, and example of the pkgrm command.
Function
The pkgrm command is used to remove a package from the system. To pack and send a package to the system, use the pkgadd command.
Command Format
pkgrm option file package name
Example
To remove the file1 file, run the following command: # pkgrm file1
14.2.3 Commands for Viewing UNIX Text Files

This describes the commands used for viewing UNIX text files, their functions, along with examples. 14.2.3.1 echo Command This describes the function, format, option, and example of the echo command. 14.2.3.2 cat Command This describes the function, format, option, and example of the cat command. 14.2.3.3 more Command This describes the function, format, option, and example of the more command. The more command is used to view a file one screen at a time. 14.2.3.4 head Command This describes the function, format, and example of the head command. 14.2.3.5 tail Command This describes the function, format, and example of the tail command. 14.2.3.6 clear Command This describes the function and example of the clear command. 14.2.3.7 grep Command This describes the function, format, and example of the grep command. 14.2.3.8 vi Command This describes the function and format of the vi command. The vi command can be used to create and modify text files.
echo Command
This describes the function, format, option, and example of the echo command.
Function
The echo command is used to send a character string to a standard output device such as the monitor screen.
Command Format
echo character string option
Option Description
Table 14-7 lists five options that are frequently used. Table 14-7 Option description of the echo command Option \c \0n \t \n \v Description The RETURN character is not displayed. n is an 8-digit ASCII character code. The TAB character is displayed. The RETURN character is displayed. The vertical TAB character is displayed.
Example
# echo $HOME /export/home/sybase /export/home/sybase displayed on the screen is the meaning of the character string "$HOME". To prevent the system from displaying RETURN, run the following command: # echo $HOME "\c" /export/home/sybase Or: # echo "$HOME \c" /export/home/sybase
NOTE
The options \c, \0n, \t, \n, and \v are displayed in the character string enclosed in quotation marks. The quotation marks can quote either one option or multiple options.
cat Command
This describes the function, format, option, and example of the cat command.
Function
The cat command is used to view the contents of a text file.
Command Format
cat option file
Option Description
l l
-n: number of each line of the displayed text -v: to view nonprinting characters rather than TAB and RETURN
Example
To view the contents of the cat_Table.txt file, run the following command: # cat cat_Table.txt
Name Object_type --------------------------------------------------tbl128Addr user table tbl128IP user table tbl128Name user table tblAdapterIP user table tblAdjCell user table ... ...
NOTE
Owner -----------------------------cat cat cat cat cat ...
To view several files at the same time, run the following command: # cat file1 file2 file3
more Command
This describes the function, format, option, and example of the more command. The more command is used to view a file one screen at a time.
Function
View a file one screen at a time. You can also use this command to browse the previous screens and to search for character strings.
Command Format
more option file
Option Description
Remember to insert the prefix - before the options when multiple options and combination of options are used. Table 14-8 lists four options that are frequently used.
Table 14-8 Option description of the more command Option -c -w -lines +/mode Description Clears the screen before the content is displayed. Indicates that the system does not exit at the end of the input but waits for the prompt. Displays the number of lines on each screen. Searches files in a preset mode.
Example
To view the contents of the cat_Table.txt file on screen at a time, run the following command: # more cat_Table.txt
NOTE
To view a file on screen at a time, press the following keys to perform relevant operations: Space key: to view the next screen Return key: to view the next line q: to exit h: to view the online help b: to switch back to the previous screen /word: to search the character string "word" backward Due to the consecutive execution of multiple UNIX commands, |more can be added at the end of other commands to view the relevant results on several screens.
head Command
This describes the function, format, and example of the head command.
Function
The head command is used to view the first few lines of a text file. By default, the first 10 lines are displayed.
Command Format
head value file
Example
To view the first three lines of the M2000 _Table.txt file, run the following command: # head -3 M2000 _Table.txt
Name Owner Object_type ------------------------------ ------------------------------
tail Command
This describes the function, format, and example of the tail command.
Function
The tail command is used to view the last few lines of a text. By default, the last 10 lines are displayed.
Command Format
tail value file
Example
To view the last ten lines of the cat_Table.txt file, run the following command: # tail cat_Table.txt
NOTE
A special function of the tail command is to view the latest changes of a log file, because all the latest changes are added at the end of the log file. The command format is as follows: # tail -f commdrv.log The option -f refers to the function of monitoring a file.
clear Command
This describes the function and example of the clear command.
Function
The clear command is used to clear the contents on the screen.
Example
To clear the screen, run the following command: # clear
grep Command
This describes the function, format, and example of the grep command.
Function
The grep command is used to search for a character string in a text file and to print all the lines that contain the character string.
Command Format
grep character string file
Example
To search the character string operation in the ifconfig.txt file, run the following command: # grep operation ifconfig.txt
used to control operation of dhcpagent(1M), the DHCP client operation, be used to modify the address or characteristics dhcpagent wakes up to conduct another DHCP operation on the given, and the operation is one that requested operation will continue.
To search the character string "The following options are supported" in the ifconfig.txt file, run the following the command: # grep "The following options are supported" ifconfig.txt
The following options are supported:
NOTE
The character string "The following options are supported" includes spaces. Remember to enclose the character string within quotation marks in the command line.
vi Command
This describes the function and format of the vi command. The vi command can be used to create and modify text files.
Function
As a powerful text editing tool, the vi editor is used to create and modify text files. The vi editor works in two modes:

l l
Text input mode: to enter the text Command mode: to enter the control command
Format
l
To start the vi editor, enter the following command: vi file name Table 14-9 lists the operations in the text input mode. Table 14-9 Operations in the text input mode Command a A i I o O Function Insert text immediately after the cursor (append). Insert text at the end of the line where the cursor is. Insert text immediately before the cursor (insert). Insert text before the first nonblank character in the line where the cursor is. Insert a new line below the current one and insert text (open). Insert a new line above the current one and insert text.
Table 14-10 lists the operations related to moving the cursor in the text input mode. Table 14-10 Operations related to moving the cursor in the text input mode Command h j k l Line No. G G Function Move the cursor one character left. Move the cursor one character down. Move the cursor one character up. Move the cursor one character right. Move the cursor to a specified line. For example, 1G means that the cursor is moved to the first line. Move the cursor to the end of the text.
Table 14-11 lists the operation for exiting the text input mode and switching to the command mode. Table 14-11 Operation for exiting the text input mode and switching to the command mode Command ESC Function Exit the text input mode and switches to the command mode.
Issue 05 (2008-05-20)
14-31

l
Table 14-12 lists the operations related to deleting characters in the command mode. Table 14-12 Operations related to deleting characters in the command mode Command x dd Function Delete a character. Delete a line.
Exit the vi editor. All the commands that exit vi editor must be run in the command mode. Therefore press ESC before running the commands. Table 14-13 describes the commands for exiting the vi editor. Table 14-13 Commands for exiting the vi editor Command :wq :q :q! :w Function Save a file and exit the vi editor. Exit from the vi editor without saving the file. Exit from the vi editor and discard all the changes. Save a file other than exit the vi editor.
14.2.4 Commands for Managing UNIX Users

This describes the user management commands that are frequently used in the UNIX system. This also describes the functions of these commands and gives some examples. Only user root and the authorized users can add, modify, or delete users and user groups. 14.2.4.1 useradd Command This describes the command function, command format, command option, and example of the useradd command. 14.2.4.2 userdel Command This describes the function, format, and example of the userdel command. 14.2.4.3 usermod Command This describes the function, format, parameter, and example of the usermod command. 14.2.4.4 passwd Command This describes the function, format, and example of the passwd command. 14.2.4.5 groupadd Command This describes the function, format, and example of the groupadd command. 14.2.4.6 groupdel Command This describes the function, format, and example of the groupdel command. 14.2.4.7 groupmod Command This describes the function, format, parameter, and example of the groupmod command.
useradd Command
This describes the command function, command format, command option, and example of the useradd command.
Function
The useradd command is performed to add a user in the UNIX system.
Command Format
useradd option new user name
Option Description
You can combine options of the useradd command. Add the prefix - before these options. Table 14-14 lists the common options. Table 14-14 Option description of the useradd command Option -c comment -d directory -m -g group -s shell Remark Indicate the comment. Indicate the home folder. Indicate the automatic creation of a home folder if the home folder does not exist. Indicate the user group that the user belongs to. Indicate the shell that the user uses.
Example
Create a user named omc1 in the UNIX system. The user omc1 belongs to the staff user group and the home folder is /home1/omc that is created automatically. In addition, the comment is Test User and B shell is applied. To create a user named omc1 in the UNIX system, run the following commands: # useradd -c "Test User" -d /home1/omc -m -g staff -s /usr/bin/sh omc1
CAUTION
After a user is added, set the password for the added user. For details of setting the password, refer to 14.2.4.4 passwd Command. After the password is set, the user can log in as a new user.
userdel Command
This describes the function, format, and example of the userdel command.
Function
The userdel command is used to delete a user. Some UNIX systems do not allow deleting users completely. Run the userdel command to revoke the privileges granted to the user.
Command Format
userdel user name
Example
Assume that there is user omc1 in the system. To delete user omc1, run the following command: # userdel omc1
CAUTION
When a user has logged in, do not run the userdel command to delete the user. If you run the userdel command, the following error message is displayed: UX: userdel: ERROR: omc1 is in use. Cannot remove it.
usermod Command
This describes the function, format, parameter, and example of the usermod command.
Function
The usermod command is used to modify the user login information.
Command Format
usermod option user name
Option Description
The combined option of the usermod command can be used. Add the prefix - before the options. Table 14-15 lists the common options. Table 14-15 Option description of the usermod command Option -c comment -d directory -m -g group
14-34
Description Modified comment Modified home folder Create a home folder automatically if the home folder does not exist Modified user group
Option -s shell -l new_logname
Description Used shell Modified user name
Example
To modify the login information about omc1, you need modify the user name to test, user group to new_group, home folder to /home1, and comment to Tester. Run the following command: # usermod -c "Test User" -d /home1 -g new_group -l test omc1
CAUTION
Do not run the usermod command to modify a user when the user has logged in. If you use the usermod command, the following error message is displayed: UX: usermod: ERROR: omc1 is in use. Cannot change it.
passwd Command
This describes the function, format, and example of the passwd command.
Function
The passwd command is used to set a password for an added user or to change the user password.
Command Format
passwd user name
Example
Assume that the user omc1 is added. To set the password of omc1, run the following command: # passwd omc1
New Password: Re-enter new Password: passwd: password successfully changed for omc1
NOTE
The input password is not displayed.
groupadd Command
This describes the function, format, and example of the groupadd command.
Function
The groupadd command is used to add a user group in the UNIX system.
Command Format
groupadd user group name
Example
To add the user group staff1 in the UNIX system, run the following command: # groupadd staff1
groupdel Command
This describes the function, format, and example of the groupdel command.
Function
The groupdel command is used to delete a user group in the UNIX system.
Command Format
groupdel user group name
Example
To delete the user group staff1, run the following command: # groupdel staff1
groupmod Command
This describes the function, format, parameter, and example of the groupmod command.
Function
The groupmod command is used to modify the information about a user group.
Command Format
groupmod user group name
-n name: the name of the modified user group
Example
To modify the name of the user group staff1 to staff2, run the following command: # groupmod -n staff2 staff1
14.2.5 Commands for Managing UNIX System Resources

This describes the commands for managing UNIX system resources. This also describes the functions of these commands and gives some examples.
14.2.5.1 man Command This describes the function, format, and example of the man command. 14.2.5.2 df Command This describes the function, format, option, and example of the df command. 14.2.5.3 du Command This describes the function, format, option, and example of the du command. 14.2.5.4 ps Command This describes the function, format, option, and example of the ps command. 14.2.5.5 kill Command This describes the function, format, option, and example of the kill command. 14.2.5.6 who Command This describes the functions, command format, option description, parameter description, and example of the who command. 14.2.5.7 whereis Command This describes the function, format, option, parameter, and example of the whereis command. The whereis command is used to view the location of a source file, binary file, and online help of a command. 14.2.5.8 which Command This describes the function, format, and example of which command. 14.2.5.9 hostname Command This describes the function, format, and example of the hostname command. 14.2.5.10 uname Command This describes the function, format, parameter options, and application examples of the uname command. 14.2.5.11 ifconfig Command This describes the function, format, option, and example of the ifconfig command. 14.2.5.12 script Command This describes the function, format, parameter options, and application examples of the script command. You use this command to record all the screen input and output in a script file. You must start recording the screen input and output after running the script command and end recording them after running the exit command. 14.2.5.13 date Command This describes the function, format, parameter options, and application examples of the data command. The data command is used to view the current date and time of the system. 14.2.5.14 bc Command This describes the function and example of the bc command. 14.2.5.15 prtconf Command This describes the function, format, parameter options, and instances of the prtconf command. 14.2.5.16 prstat Command This describes how to use the CPU to check the function and user identity of the prstat command. It also provides an example to explain the application.
Issue 05 (2008-05-20)
14-37
man Command
This describes the function, format, and example of the man command.
Function
The man command is used to view the online help about a command.
Command Format
man option command
Example
To view the online help about the pwd command, run the following command: # man pwd
Reformatting page. User Commands NAME pwd - return working directory name SYNOPSIS /usr/bin/pwd DESCRIPTION pwd writes an absolute path name directory to standard output. of the Korn current shell, working ksh(1), Wait... done pwd(1)
Both the Bourne shell, sh(1), and the also have a built-in pwd command.
ENVIRONMENT See environ(5) for descriptions of the following environment variables that affect the execution of pwd: LC_MESSAGES and NLSPATH. EXIT STATUS --More--(30%)
NOTE
Not all parameters in the man command are command names. For example, the man ascii command displays all the ASCII characters and their expressions. The man shell_builtins command displays the built-in command list and the shell using the commands.
df Command
This describes the function, format, option, and example of the df command.
Function
The df command is used to view the free disk space. The system administrator runs this command frequently to check the usage of the disk space to avoid disk failure due to data overflow.
Command Format
df option file system
Option Description
l l
-l : the local file system -k: to view the free disk space (unit: KB)
Example
To check the free disk space, run the following command: # df -k
Filesystem /dev/dsk/c0t0d0s0 /proc fd /dev/dsk/c0t1d0s7 swap kbytes used avail capacity 2053605 997684 994313 51% 0 0 0 0% 0 0 0 0% 35009161 2562019 32097051 8% 3431792 6664 3425128 1% Mounted on / /proc /dev/fd /export/home /tmp
The command result contains the following information:

l l l l l
File system name File size (unit: KB) Used space Free space Capacity percentage of the filled file system and the mounting point
When you run the df command without any parameters, the free disk space in each mounted device is displayed. When the free disk space is reduced to the bottom line, the system administrator must take immediate measures to locate the faulty file system.
du Command
This describes the function, format, option, and example of the du command.
Function
The du command is used to view the disk space used by a specific folder or file.
Command Format
du option folder or file
Option Description
l l l
-a : to view the disk space used by each file -s: to view the used total disk space -k: to view the result (unit: KB)
Example
l
To view the disk space used by the files in the /export/home/sybase folder, run the following command:
Issue 05 (2008-05-20)
# du -k /export/home/sybase |more
212554 /export/home/sybase/bin 7 /export/home/sybase/charsets/ascii_8 76 /export/home/sybase/charsets/cp437 124 /export/home/sybase/charsets/cp850 214 /export/home/sybase/charsets/deckanji 237 /export/home/sybase/charsets/eucgb 235 /export/home/sybase/charsets/eucjis 142 /export/home/sybase/charsets/iso_1 13 /export/home/sybase/charsets/mac 78 /export/home/sybase/charsets/roman8 221 /export/home/sybase/charsets/sjis 1119 /export/home/sybase/charsets/unicode 1383 /export/home/sybase/charsets/utf8 3850 /export/home/sybase/charsets 76 /export/home/sybase/collate/unicode 77 /export/home/sybase/collate 97 /export/home/sybase/config 87484 /export/home/sybase/devlib 1921 /export/home/sybase/diag/bin 3 /export/home/sybase/diag/custom 37 /export/home/sybase/diag/formdefs 225 /export/home/sybase/diag/locales/us_english --More l
To view the disk space used by all file systems in the current folder and send the results to the sort command for sorting, run the following command: # du -s * |sort -rn |more
425108 bin 174968 devlib 41094 lib 18588 pad 9406 locales 7700 charsets 6810 scripts 5552 install 4636 diag 4404 upgrade 1220 sample 834 symlib 718 include 194 sybhelp 194 config 154 collate 76 init 50 license 14 xappdefaults 12 sybserver.cfg 12 sybserver.bak 12 sybserver.083 --More
To list the first three file systems according to the file size, run the following command: # du -s * |sort -rn |head -10
425108 174968 41094 18588 9406 7700 6810 5552 4636 4404 bin devlib lib pad locales charsets scripts install diag upgrade
14-40
Issue 05 (2008-05-20)
ps Command
This describes the function, format, option, and example of the ps command.
Function
The ps command is used to view the status of the processes currently running in the system..
Command Format
ps option
Option Description
l l l l
-e : to view the status of all the processes that are running in the system -l: to view the running processes in a long-form list -u user: to view the process status of a specific user -f : to view all the status information about the processes that are running in the system
Example
l
To view the status of all the running processes controlled by the login device (the terminal), run the following command: # ps
PID TTY 13726 pts/5 TIME CMD 0:00 ksh
To view the complete information about the active processes, run the following command: # ps -f
UID PID PPID sybase 13726 13724 C STIME TTY 0 08:44:35 pts/5 TIME CMD 0:00 -ksh
To view the M2000 processes, run the following command: # ps -ef | grep imap
root 22344 1 0 17:49:43 ? 0:03 imapsvcd -name devdoc_agent sysagent DEFAULTSYSAGENT -port 31105 -agentid 0 root 22374 1 0 17:49:48 ? 0:02 imapsvcd -name am_agent sysa gent DEFAULTSYSAGENT -port 31131 -agentid 0 root 22346 1 0 17:49:43 ? 0:01 imapsvcd -name em_agent sysa gent DEFAULTSYSAGENT -port 31002 -agentid 0 root 22342 1 0 17:49:43 ? 0:11 imapsvcd -name cmdc_agent sy sagent DEFAULTSYSAGENT -port 31103 -agentid 0 root 22355 1 0 17:49:45 ? 0:11 imapsvcd -name ifms_agent sy sagent DEFAULTSYSAGENT -port 31011 -agentid 119 root 22338 1 0 17:49:42 ? 0:02 imapsvcd -name 3gpp_agent sy ......
Issue 05 (2008-05-20)
14-41

NOTE
l l
After you run the ps command without any parameters, the screen displays information about all running processes that are controlled by the login device (terminal). After you specify the -f parameter, more information is displayed. The information includes the user name (UID), process ID (PID), parent process ID (PPID), technical number that indicates the running time of the process (C), process start time (STIME), name of the terminal that activates the process (TTY), and the process name (CMD). If TTY displays ?, infer that this process is not associated with the terminal. To view all the processes related to specific characters, for example, the process related to the M2000, run the grep command with the ps command.
kill Command
This describes the function, format, option, and example of the kill command.
Function
The kill command is used to terminate a process.
Command Format
kill option process No.
Option Description
l l
-l : lists the names of all the signals -s signal: sends a signal named signal to the processes
Process No.: the ID of the process to be terminated, that is, the process ID
Example
l
To list all the signal names, run the following command: # kill -l
EXIT HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM USR1 USR2 CLD PWR WINCH URG POLL STOP TSTP CONT TTIN TTOU VTALRM PROF XCPU XFSZ WAITING LWP FREEZE THAW CANCEL LOST RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX
To terminate the process with PID as 256, run the following command: # kill -s KILL 256
14-42
Issue 05 (2008-05-20)

NOTE
The previous signal names can be expressed by code. For example, -1 for HUP, -2 for INT, -3 for QUIT, -9 for KILL, -15 for TERM. The signal KILL can be replaced with -9. This signal is the most frequently used one in the kill command, and thus it has the highest priority. The default signal 15 is used when no option is specified for the kill command. Run the following command to terminate the process with the PID as 256: # kill -9 256 Run the ps command to check the execution of the kill command by listing the PIDs of the terminated processes. The kill command may lead to a data loss. Run this command with care.
l l
who Command
This describes the functions, command format, option description, parameter description, and example of the who command.
Function
The who command reports the login information about all the users in the current system.
Command Format
who Option
Option Description
l l
-b : display the system date and time of the last startup -m: display the related information about the users who run the command (the same as the command who with two parameters am i
am i: display the login information about the users who run the command
Example
l
Display the login information about all the users in the current system: # who
root sybase root pts/3 pts/5 pts/6 Feb Feb Feb 4 10:08 4 08:45 4 11:25 (10.129.16.60) (10.129.28.44) (10.129.16.60)
Display the login information about the users who run the command: # who am i
sybase pts/5 Feb 4 08:45 (10.129.28.44)
or: # who -m
sybase pts/5 Feb 4 08:45 (10.129.28.44)
Issue 05 (2008-05-20)
14-43
whereis Command
This describes the function, format, option, parameter, and example of the whereis command. The whereis command is used to view the location of a source file, binary file, and online help of a command.
Function
The whereis command is used to view the location of a source file, binary file, and online help of a command.
Command Format
whereis option command
Option Description
l l l
-b : to view the location of the binary file -m: to view the location of the help manual -s: to view the location of the source file
command: the command for which the location is to be displayed
Example
l
To view the exact location of files of various versions for the ls command, run the following command: # whereis ls
ls: /usr/bin/ls /usr/ucb/ls /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
To view the exact location of the binary file for the ls command, run the following command: # whereis -b ls
ls: /usr/bin/ls /usr/ucb/ls
To view the exact location of the help manual for the ls command, run the following command: # whereis -m ls
ls: /usr/man/man1/ls.1 /usr/man/man1b/ls.1b
which Command
This describes the function, format, and example of which command.
Function
The which command is used to view the location where a command is run. The result may be an absolute path or alias of the command found in the user environment variant PATH.
Command Format
which command
Example
To view the position where the commands pwd, who, and which are run, run the following command: # which pwd who which
/usr/bin/pwd /usr/bin/who /usr/bin/which
NOTE
If the command to be located does not exist in the file, the following error messages are displayed after you run the which command: # which qqqq
no qqqq in /usr/bin /usr/ucb /etc /export/home/sybase/bin /export/home/sybase/ install.
hostname Command
This describes the function, format, and example of the hostname command.
Function
The hostname command is used to view or set the host name.
Command Format
hostname host name
Example
To view the host name, run the following command: # hostname
NOTE
If you run the hostname command without parameters, the host name of the equipment is displayed. If you run the hostname command with parameters, the host name is set. Only the super user can run the hostname command.
uname Command
This describes the function, format, parameter options, and application examples of the uname command.
Function
The uname command is used to view the information about the operating system. If you run this command without parameters, only the name of the operating system is displayed. If you run this command with parameters, more details about the operating system are displayed.
Format
uname option
Option Description
The options of the uname command can be combined. Add the prefix - before the options. Table 14-16 lists some frequently used options. Table 14-16 Description of the uname options Option -a -i -m Description Views all the information. Views hardware information. Views the name of the equipment hardware. It is recommended that -p be used instead of -m. Views the name of the network equipment. Views the ISA of the host or the type of the processor. Views the serial number of the operating system of the host. Views the name of the operating system of the host (it is the default option). Views the version of the operating system of the host. Sets the host name of the machine.
-n -p -r -s -v -S system_name
Example
To view the name, version, and serial number of the operating system on the host, run the following command: # uname -svr
ifconfig Command
This describes the function, format, option, and example of the ifconfig command.
Function
The ifconfig command is used to view the IP address of the host.
Command Format
ifconfig option
Option Description
-a: to view all the address information
Example
To view the IP address of the host, run the following command: # ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu 1500 inet 129.9.169.143 netmask ffff0000 broadcast 129.9.255.255 hme0:1:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 129.6.253.136 netmask ffff0000 broadcast 129.6.255.255
NOTE
In the previous output, the IP address of the displayed host is 129.9.169.143, and the logical IP address is 129.6.253.136. In the UNIX system, a network adapter can bind several logical IP addresses, which realizes communications between different network segments.
script Command
This describes the function, format, parameter options, and application examples of the script command. You use this command to record all the screen input and output in a script file. You must start recording the screen input and output after running the script command and end recording them after running the exit command.
CAUTION
Close the script file before running the exit command to terminate the recording of the screen I/O. If you do not close the script file, the script file builds up and hinders the normal operation of the system.
Function
Record in a script file all the screen input and output that occur from the time when the script command is run to the time when the exit command is entered. The script command is helpful for programming and debugging.
Format
script option file
Option Description
-a: appends the screen I/O content to a file. If you do not set this parameter, the screen I/O overwrites the content of the file.
file: the file used to save the screen I/O content. If you do not specify the file name, the screen I/O content is saved to the typescript file.
Example
To save the screen I/O content in the default destination file typescript, run the following commands: # script
Script started, file is typescript
# ps
PID TTY 775 pts/8 TIME CMD 0:00 ksh
# pwd
/export/home/sybase
# date
Mon Feb 4 19:12:14 GMT 2002
# exit
Script done, file is typescript
To view the content of the typescript file, run the following command: # cat typescript
Script started on Mon Feb 04 19:11:49 2002 $ ps PID TTY TIME CMD 775 pts/8 0:00 ksh $ pwd /export/home/sybase $ date Mon Feb 4 19:12:14 GMT 2002 $ exit script done on Mon Feb 04 19:12:24 2002
date Command
This describes the function, format, parameter options, and application examples of the data command. The data command is used to view the current date and time of the system.
Function
The data command is used to view the current date and time of the system. The super user can run the date command to set the system date and time.
Format
date option +format
Option Description
l l
-a: to use the Greenwich mean time. +format: to specify the command output format.
Table 14-17 describes the format of the command output.

Table 14-17 Format of the command output Format %h %j %n %t %y %D %H %M %S %T Description Abbreviation of the month: from January to December A day in a year: from 001 to 366 Switch to next line The tab key The last two digits of the year: from 00 to 99 Output format of the date: month/date/year Hour: from 00 to 23 Minute: from 00 to 59 Second: from 00 to 59 Output format of time: hour:minute:second
Example
l
To view the current date and time of the system, run the following command: date
Mon Feb 4 20:26:16 GMT 2002
To view the current system date and time in the Greenwich Mean Time, run the following command: date -u
Mon Feb 4 12:27:26 GMT 2002
To view the current date of the system in the format of month/day/year, run the following command: date +%D
02/04/02
bc Command
This describes the function and example of the bc command.
Function
The bc command is used to perform a simple calculation.
Example
To multiply 4 by 5, run the following command: # bc 4*5

20
NOTE
To get the result, run the bc command, and then press Enter. Type the formula 4*5, and then press Enter. The result is displayed on the screen. Press Ctrl+D to exit from the bc program.
prtconf Command
This describes the function, format, parameter options, and instances of the prtconf command.
Function
The prtconf command is used to check the system configuration information.
Format
prtconf option device path
Instance
l
Check all the configuration information about the system. # prtconf

System Configuration: Sun Microsystems Memory size: 4096 Megabytes System Peripherals (Software Nodes): sun4u
SUNW,Netra-240 scsi_vhci, instance #0 packages (driver not attached) SUNW,builtin-drivers (driver not attached) deblocker (driver not attached) disk-label (driver not attached) terminal-emulator (driver not attached) dropins (driver not attached) kbd-translator (driver not attached) obp-tftp (driver not attached) SUNW,i2c-ram-device (driver not attached) SUNW,fru-device (driver not attached) SUNW,asr (driver not attached) ufs-file-system (driver not attached) chosen (driver not attached) openprom (driver not attached) client-services (driver not attached) options, instance #0 aliases (driver not attached) memory (driver not attached) virtual-memory (driver not attached) SUNW,UltraSPARC-IIIi, instance #0 (driver not attached) memory-controller, instance #0 SUNW,UltraSPARC-IIIi, instance #1 (driver not attached) memory-controller, instance #1 pci, instance #0 network, instance #0 network, instance #1 pci, instance #1 isa, instance #0 flashprom (driver not attached) rtc (driver not attached) i2c, instance #0 i2c-bridge (driver not attached) i2c-bridge (driver not attached) motherboard-fru-prom, instance #0 (driver n chassis-fru-prom, instance #1 (driver not a
14-50
Issue 05 (2008-05-20)

alarm-fru-prom, instance #2 (driver not att power-supply-fru-prom, instance #3 (driver power-supply-fru-prom, instance #4 (driver dimm-spd, instance #5 (driver not attached) dimm-spd, instance #6 (driver not attached) dimm-spd, instance #7 (driver not attached) dimm-spd, instance #8 (driver not attached) rscrtc (driver not attached) nvram, instance #9 (driver not attached) idprom (driver not attached) gpio, instance #0 (driver not attached) gpio, instance #1 (driver not attached) gpio, instance #2 (driver not attached) gpio, instance #3 (driver not attached) gpio, instance #4 (driver not attached) gpio, instance #5 (driver not attached) power, instance #0 serial, instance #0 serial, instance #1 (driver not attached) rmc-comm, instance #0 pmu, instance #0 i2c, instance #0 gpio, instance #0 usb, instance #0 ide, instance #0 disk (driver not attached) cdrom (driver not attached) sd, instance #3 pci, instance #2 scsi, instance #0 disk (driver not attached) tape (driver not attached) sd, instance #0 sd, instance #1 (driver not attached) sd, instance #2 (driver not attached) sd, instance #4 (driver not attached) sd, instance #5 (driver not attached) sd, instance #6 (driver not attached) sd, instance #7 (driver not attached) sd, instance #8 (driver not attached) sd, instance #9 (driver not attached) sd, instance #10 (driver not attached) sd, instance #11 (driver not attached) sd, instance #12 (driver not attached) sd, instance #13 (driver not attached) sd, instance #14 (driver not attached) sd, instance #15 (driver not attached) st, instance #1 (driver not attached) st, instance #2 (driver not attached) st, instance #3 (driver not attached) st, instance #4 (driver not attached) st, instance #5 (driver not attached) st, instance #6 (driver not attached) ses, instance #1 (driver not attached) ses, instance #2 (driver not attached) ses, instance #3 (driver not attached) ses, instance #4 (driver not attached) ses, instance #5 (driver not attached) ses, instance #6 (driver not attached) ses, instance #7 (driver not attached) ses, instance #8 (driver not attached) ses, instance #9 (driver not attached) ses, instance #10 (driver not attached) ses, instance #11 (driver not attached) ses, instance #12 (driver not attached) ses, instance #13 (driver not attached) ses, instance #14 (driver not attached) ses, instance #15 (driver not attached) scsi, instance #1
Issue 05 (2008-05-20)
14-51

disk (driver not attached) tape (driver not attached) sd, instance #16 (driver not attached) sd, instance #17 (driver not attached) sd, instance #18 (driver not attached) sd, instance #19 (driver not attached) sd, instance #20 (driver not attached) sd, instance #21 (driver not attached) sd, instance #22 (driver not attached) sd, instance #23 (driver not attached) sd, instance #24 (driver not attached) sd, instance #25 (driver not attached) sd, instance #26 (driver not attached) sd, instance #27 (driver not attached) sd, instance #28 (driver not attached) sd, instance #29 (driver not attached) sd, instance #30 (driver not attached) st, instance #8 (driver not attached) st, instance #9 (driver not attached) st, instance #10 (driver not attached) st, instance #11 (driver not attached) st, instance #12 (driver not attached) st, instance #13 (driver not attached) ses, instance #16 (driver not attached) ses, instance #17 (driver not attached) ses, instance #18 (driver not attached) ses, instance #19 (driver not attached) ses, instance #20 (driver not attached) ses, instance #21 (driver not attached) ses, instance #22 (driver not attached) ses, instance #23 (driver not attached) ses, instance #24 (driver not attached) ses, instance #25 (driver not attached) ses, instance #26 (driver not attached) ses, instance #27 (driver not attached) ses, instance #28 (driver not attached) ses, instance #29 (driver not attached) ses, instance #30 (driver not attached) ses, instance #31 (driver not attached) pci, instance #3 network, instance #2 network, instance #3 iscsi, instance #0 pseudo, instance #0
prstat Command
This describes how to use the CPU to check the function and user identity of the prstat command. It also provides an example to explain the application.
Function
The CPU usage may be high when a large number of NE alarms are reported in a short period. This command is used to find out the cause of these alarms.
Permitted Users
Users root, omcuser, and dbuser are authorized to run the prstat command.
Example
-bash-3.00$ prstat The command result contains the CPU usage of each process.
14.2.6 Commands for Network Communication on the UNIX System

This describes the commands for network communication on the UNIX system. This also describes the functions of these commands and gives some examples. 14.2.6.1 ping Command This describes the function, format, parameter options, and application examples of the ping command. 14.2.6.2 telnet Command This describes the functions, format, parameters, and example of the telnet command. The telnet command is used to log in to remote UNIX hosts through network connection. 14.2.6.3 ftp Command This describes the function, format, parameter options, and application example of the ftp command. 14.2.6.4 finger Command This describes the function, format, parameters, and example of the finger command. 14.2.6.5 netstat Command This describes the function, format, options, and example of the netstat command. 14.2.6.6 route Command This describes the function, format, parameter options, and application example of the route command.
ping Command
This describes the function, format, parameter options, and application examples of the ping command.
Function
The ping command is used to check the physical connection of the network when the communication between a user computer and the hosts in the network is interrupted.
Format
ping IP address of a host
Example
Check the physical connection between the current host and the host whose IP address is 129.9.0.1. # ping 129.9.0.1
129.9.0.1 is alive
The Internet Control Message Protocol (ICMP) is used through the ping command to check the network connection. An ICMP echo request message is sent to a specific host to request an ICMP echo response message. If the response message is not received within a specified time, the Host unreachable message is displayed on the screen.
The Host unreachable message is displayed in the following cases:

l l l
The specified host is invalid. The physical connection of the network is not secure. The two communicating hosts do not support the same communication protocol.
To analyze the causes, run the ping command to connect to other hosts in the same network segment. If the ping command is successful, you can infer that the connection is functional. In this case, check the physical connection and the operational status of the specified host. If the ping command fails, check whether the physical network connection of the current host is secure or whether the TCP/IP protocol is set correctly only for Windows 95 users.
telnet Command
This describes the functions, format, parameters, and example of the telnet command. The telnet command is used to log in to remote UNIX hosts through network connection.
NOTE
Before running the telnet command, ensure that a local computer is connected to the remote UNIX host according to the TCP/IP protocol.
Function
Telnet is the software used to log in to remote UNIX hosts through network connection. Telnet takes the local computer as a simulated terminal of the remote UNIX host and enables you to log in to the remote server from the local computer. After you log in to the remote UNIX host successfully through telnet, you become a remote simulated terminal user and you can use the local computer as a real UNIX terminal. In this case, the resources and functions available and the operating mode depend on the settings of the remote host and the access privileges of the login account.
Command Format
telnet IP address or domain name
l l
IP address: the IP address of a remote UNIX host Domain: the domain name of a remote UNIX host
Example
Run the telnet command on a local computer and log in to a remote Sun workstation. Assume that the IP address of the Sun workstation is 129.9.169.143. On the local computer, choose Start > Run . Enter telnet 129.9.169.143 and click OK. The Telnet dialog box appears and prompts you to enter the UNIX user name and password.
SunOS 5.8
login: sybase Password:sybase password

Last login: Wed Mar 6 10:52:34 from 129.9.28.44 Sun Microsystems Inc. SunOS 5.6 Generic August 1997 You have new mail. $
NOTE
Enter the password on the right of Password:. The entered password is not displayed.
The previous steps are the same as those when you operate on the Sun workstation.
ftp Command
This describes the function, format, parameter options, and application example of the ftp command.
Function
The ftp command is used to transfer files between the local computer and the remote host. You can transfer one or multiple files at a time between the remote UNIX system and the local computer.
Format
ftp IP address or domain
l l
IP address: the IP address of the remote UNIX host Domain name: the domain name of the remote UNIX host
Example
Run the ftp command on the local computer. Assume that the IP address of the remote UNIX host is 129.9.169.143. Choose Start > Run on the local computer. In the displayed dialog box, enter ftp 129.9.169.143 and click OK. When the ftp window is displayed, enter the UNIX user name and password.
Connected to 129.9.169.143. 220 osssvr-01 FTP server (Sunos 5.6) ready.
User (129.9.169.143: (none) : ) sybase

331 Password required for sybase.
Password:password of sybase
230 User sybase logged in. ftp>
NOTE
Enter the password after Password: . The password is not displayed.
Enter the ftp command behind the prompt ftp>. Table 14-18 describes the ftp commands that are commonly used.
Issue 05 (2008-05-20)
14-55
Table 14-18 Common ftp commands ftp Command !command ?|help command ascii binary cd folder close dir r-folder l-file Description Use a local command and return to ftp immediately. View the command help. Transfer files in ASCII format (default). Transfer files in binary format. Modify the remote folder. Break the remote connection. View the remote folder. r-folder refers to the remote folder. l-file refers to the local file. If there is a local file, save the result to the local file. Copy the remote file1 to the local file2. Modify the local folder. Same as dir, but the display format is different. Copy several remote files to the local computer. Reestablish a connection. Copy the remote file1 to the local file2. List the folders of the current remote host. Exit from the ftp. View the current ftp status.
get file1 file2 cd folder ls r-folder l-file mget several files open IP address or domain put file1 file2 pwd quit|bye status
Copy all the files in the path C:\mydoc on the local computer to the /usr/local/tmp folder on the remote host. ftp> binary ftp> lcd c:\mydoc ftp> cd /usr/local/tmp ftp> mput *.*
Copy the .login file in the /usr/home/rms folder on the remote host to the path C: \mydoc folder on the local computer. ftp> ascii ftp> lcd c:\temp\from ftp> cd /usr/home/rms
14-56
Issue 05 (2008-05-20)
ftp> get .login

l
Copy all files in the /usr/home/rms folder on the remote computer to the path C:\temp \from on the local computer in binary format. ftp> binary ftp> lcd c:\temp\from ftp> cd /usr/home/rms ftp> mget * To exit ftp. ftp> quit
CAUTION
The Telnet and FTP protocols belong to the TCP/IP family. They are the protocols at the application layer. They work in client/server mode. The telnet/ftp program running on the local computer is a telnet/ftp client program. The telnet/ftp program connects to the server program in the remote host through the TCP/IP protocol. Any system installed with the telnet/ftp serverside software can serve as a remote host. In addition to the default network protocol TCP/IP, the UNIX system supports the Telnet/FTP protocols. Because a UNIX host is installed with both the telnet/ftp server software and the client software, the UNIX host can serve as either a telnet/ ftp server or a telnet/ftp client.
finger Command
This describes the function, format, parameters, and example of the finger command.
Function
The finger command is used to view the information about online users of the UNIX system.
Command Format
finger user name@host domain|IP address
l l l
user nam: the user that has currently logged in to the local system. host domain: the UNIX host domain. IP address: the IP address of the UNIX host.
Example
Table 14-19 lists some common examples of the finger command.
Issue 05 (2008-05-20)
14-57
Table 14-19 Examples of the finger command Example # finger # finger root # finger @omcsyb2 # finger @omcsyb2.Huawei.com.cn # finger abc@omcsyb2 # finger abc@129.6.114.202 Description View the information about all local users. View the information about user root. View the information about all users in the host omcsyb2. View the information about all users in the host omcsyb2.Huawei.com.cn. View the information about user abc in the host omcsyb2. View the information about user abc in the host 129.6.114.202.
netstat Command
This describes the function, format, options, and example of the netstat command.
Function
The netstat command is used to display the current network status. The netstat command is powerful but complex in format. This describes common applications of the netstat command.
Command Format
netstat options
Option Description
l
For viewing all the sockets and routing tables (netstat -anv)

-a: views all socket information. -n: views the information by number. If you do not specify this parameter, the information is displayed by logical name. -v: views the information about sockets and routing tables of the additional information.
For viewing the IP address of the network adapter (netstat -i -I interface interval interval)

-i: views the information about the network interface. -I interface: specifies an interface, for example, hme0:1 interval: indicates a time interval. -r: views the information about the routing table. -anv: refers to For viewing all the sockets and routing tables.
For viewing the routing table status (netstat -r -anv)

For viewing the broadcast information (netstat -M -ns)

14-58

l
-M: views broadcast routing tables. -s: summarizes the status of each protocol.
For viewing the DHCP status (netstat -D -I interface) -D: views the DHCP information.
Example
Use the command netstat -rn to view the information about the routing tables: root@ts-007 # netstat -rn
Routing Table: Destination 10.105.28.0 10.0.0.0 224.0.0.0 127.0.0.1 Gateway 10.105.28.202 10.105.31.254 10.105.28.202 127.0.0.1 Flags U UG U UH Ref 4 0 4 0 0 0 896 hme0 lo0 Use 2 Interface hme0
A router can be in any of the following five different flags: U, G, H, D, and M, as described in Table 14-20. Table 14-20 Description of routing flags Flag U G Description U indicates that a route is currently available. G indicates that a route is destined for a gateway such as a router. If this flag is not set, you can infer that the destination is connected directly. Flag G distinguishes between direct and indirect routes. Flag G is unnecessary for direct routes. The difference is that the packet sent through a direct route carries both the destination IP address and the link-layer address. In the packet sent through an indirect route, however, the IP address points to the destination and the link layer address points to the gateway (for example, the next router). H H indicates a route destined for a host. That is, the destination address is a complete host address. If this flag is not set, you can infer that the route leads to a network and that the destination address is a network address: either a network number or a network. The part in the address for the host is 0. When you search the routing table for an IP address, the host address must exactly match the destination address. The network address, however, is required to match only the network number and subnet number of the destination address. D M D indicates that a route is created by a redirected packet. M indicates that a route is modified by a redirected packet.
The Ref (Reference count) column lists the number of routing progresses. The protocol for connection, such as TCP, requires a fixed route when a connection is established. If the telnet connection is established between the host svr4 and the host slip, the Ref is 1. If another telnet connection is established, its value is changed to 2. The next column (Use) displays the number of packets sent through a specified route. After you run the ping command as the unique user of this route, the program sends five groups and the
number of packets is displayed as 5. The last column (Interface) indicates the name of the local interface. The second row of the output is a loop-back interface. The interface name is permanent set to lo0. Flag G is not set because the route is not destined for a gateway. Flag H indicates that the destination address, 127.0.0.1, is a host address and not a network address. Because flag G is not set, the route here is a direct route and the gateway column shows the outgoing IP address. Each host has one or multiple default routes. That is, if a particular route is not found in the table, the packet is sent to the router. In addition, the current host can access other systems through the Sun router (and the slip link) on the internet, based on the settings of the routing table. The flag UG refers to the gateway.
route Command
This describes the function, format, parameter options, and application example of the route command.
Function
The routing table relays IP address between network segments. The route command is used to modify and maintain the routing table.
Format
route -fnvq command modifiers args route -fnvq add | change | delete | get host/net destination gateway args route -n monitor route -n flush
NOTE
The meaning of "|" is the same as that of the word "or".
Options of the route command can be combined. Table 14-21 lists some common options. Table 14-21 Description of the route commands Option -f -n -v -q -commond Description Refresh routing tables for all gateways. View the information in characters instead of symbols. View the additional information. Suspend all outputs. Have the command add/chang/flush (clear the gateways in the routing table)/get/monitor.
14-60
Option -destination
Description Indicate the destination network segment. For example, 10.0.0.0 stands for section 10, and 10.11.0.0 stands for section 10.11. Indicate the IP address of the gateway. Indicate the network segment. For example, 10.11.12.0 stands for section 10.11.12. Indicate the IP address of the host.
-gateway net host
Example
l
Obtain the routing information about network segment 10. root@ts-007 # route -n get 10.0.0.0
route to: 10.0.0.0 destination: 10.0.0.0 mask: 255.0.0.0 gateway: 10.105.31.254 interface: hme0 flags: <UP,GATEWAY,DONE,STATIC> recvpipe sendpipe ssthresh rtt,msec 0 0 0 0
rttvar 0
hopcount 0
mtu expire 1500
Clear the gateways in the routing table. root@ts-007 # route -n flush

10 10.105.31.254 done
root@ts-007 # netstat -rn

Routing Table: Destination -------------------10.105.28.0 224.0.0.0 127.0.0.1 Gateway Flags Ref Use Interface -------------------- ----- ----- ------ --------10.105.28.202 U 4 6 hme0 10.105.28.202 U 4 0 hme0 127.0.0.1 UH 0 1500 lo0
root@ts-007 # telnet 10.129.3.4

Trying 10.129.3.4... telnet: Unable to connect to remote host: Network is unreachable
After the gateways in the routing table are cleared, the network segments beyond 10.105.28.202/34 are no longer accessible.
l
Add a routing record. root@ts-007 # route add 129.9.0.0 10.105.28.202

add net 129.9.0.0: gateway 10.105.28.202

Routing Table: Destination -------------------10.105.28.0 129.9.0.0 10.0.0.0 224.0.0.0 127.0.0.1 Gateway Flags Ref Use Interface -------------------- ----- ----- ------ --------10.105.28.202 U 4 2 hme0 10.105.28.202 UG 0 0 10.105.31.254 UG 0 0 10.105.28.202 U 4 0 hme0 127.0.0.1 UH 0 313 lo0
Issue 05 (2008-05-20)
14-61

NOTE
129.9.0.0 10.105.28.202 UG 0 0 is the newly-added routing record.

l
Modify the routing table. root@ts-007 # route change 129.9.0.0 1.2.3.4

change net 129.9.0.0: gateway 1.2.3.4

Routing Table: Destination -------------------10.105.28.0 129.9.0.0 10.0.0.0 224.0.0.0 127.0.0.1
NOTE
Gateway Flags Ref Use Interface -------------------- ----- ----- ------ --------10.105.28.202 U 4 2 hme0 1.2.3.4 UG 0 0 10.105.31.254 UG 0 0 10.105.28.202 U 4 0 hme0 127.0.0.1 UH 0 445 lo0
129.9.0.0 1.2.3.4 UG 0 0 is the routing record of the modified gateway.
14-62
Issue 05 (2008-05-20)
15 FAQ About the M2000
15
About This Chapter
FAQ About the M2000
This chapter describes FAQs and solutions related to the M2000. 15.1 FAQ About the Solaris This describes some FAQs and solutions related to the Solaris. 15.2 FAQ About the Sybase This describes the FAQs and solutions related to the Sybase. 15.3 FAQ About the TCP/IP Network This describes some FAQs and solutions related to the TCP/IP network. 15.4 FAQ About the M2000 Server Software This describes some FAQs and solutions related to the M2000 server software.
Issue 05 (2008-05-20)
15-1
15.1 FAQ About the Solaris

This describes some FAQs and solutions related to the Solaris. 15.1.1 How to Log In as the root User Through Telnet This describes how to log in as user root through the telnet. 15.1.2 How to Log In as the root User Through FTP This describes how to log in as user root through the FTP. 15.1.3 How to Check the Status of the Tape Drive This describes how to check the status of the tape drive. 15.1.4 How to Select the Tape Drive The types of servers that are not equipped with an internal tape drive, such as Netra 240, are equipped with an external tape drive. By default, the external tape drive of these server types is /dev/rmt/0. The types of servers without an external tape drive, such as V890 and E4900, are equipped with an internal tape drive, By default, the internal tape drive of these server types is also /dev/rmt/0. If the servers with an internal tape drive, such as V890 and E4900, are equipped with an external tape drive, which tape drive should the backup data be save on? 15.1.5 What Do the files in the etc/rc2.d Folder of Solaris Mean This describes the definition of the files in the /etc/rc2.d folder of the Solaris. 15.1.6 How to View the Hardware Settings of the M2000 Server This describes how to view the hardware settings of the M2000 server. 15.1.7 How to Solve Auto Solaris Shutdown When Connection Between the Server and the TC Is Broken This describes how to avoid automatic Solaris shutdown when the connection between the server and the TC is broken. 15.1.8 How to Check the Device Status of the M2000 Server This describes the common commands used to check the device status of the M2000 server. 15.1.9 Why Cannot Enter the Domain Console of Sun Fire E4900 This describes the solutions to the failure to enter the domain console of the Sun Fire E4900. 15.1.10 How to Change the Port Number of the FTP Server? By default, the port number of the FTP server is 21. You need to change the port number of the FTP server according to the actual requirement. 15.1.11 How to Query a Time Zone Name This describes how to query a time zone name. Before querying the DST rules of a time zone, you must know the name of the time zone. Based on the time zone name, you can query the corresponding DST rules.
15.1.1 How to Log In as the root User Through Telnet

This describes how to log in as user root through the telnet.
Question
Why can I not log in as user root through the telnet?
Answer
For security, the default setting during the installation of the operating system is that you can log in only as user root on the console. Thus, you are not allowed to log in as user root through the telnet. To log in as user root through the telnet, perform the following steps: 1. 2. 3. 4. Log in as user root on the console. Open /etc/default/login. # vi /etc/default/login Find CONSOLE=/dev/console. Comment this line off by adding # at the beginning of the line. Save, and then exit the file.
15.1.2 How to Log In as the root User Through FTP

This describes how to log in as user root through the FTP.
Question
Why can I not log in as user root through the FTP?
Answer
For security, the default setting during the installation of the operating system is that the FTP service is not available for root. To log in as user root through the FTP, perform the following steps: 1. 2. 3. 4. Log in as user root. Open /etc/ftpd/ftpusers. # vi /etc/ftpd/ftpusers Find root. Comment this line off by adding # at the beginning of the line. Save, and then exit the file.
15.1.3 How to Check the Status of the Tape Drive

This describes how to check the status of the tape drive.
Question
How do I check the server tape drive status?
Answer
If a built-in tape drive is installed, the server identifies the tape drive upon startup. For an external tape drive, you must install it. To install an external Sun tape drive, such as Ultra 60, perform the following steps: 1. 2. 3.
Issue 05 (2008-05-20)
Power off the server and all the peripherals. Set the ID switch on the tape drive to 4 or 5. If you use SCSI interface, connect the SCSI cable to the IN port on the tape drive.
4. 5. 6.
Switch on the server and all the peripherals and start the system. Log in as user root. Run the following command to check the status of the tape drive: # mt -f /dev/rmt/0n status The commands mentioned earlier can be briefly written as mt status. Table 15-1 lists the output. Table 15-1 Tape drive status No. 1 Output HP DDS-3 4MM DAT tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 2 3 4 No such device or address /dev/rmt/0n: no tape loaded or drive offline /dev/rmt/0n: No such file or directory Tape Drive Status The tape drive works normally. A tape is loaded and rewound.
The tape drive is not connected to the workstation properly. The current tape or tape drive is offline. The tape drive is not configured.
7.
Configure the tape drive. # drvconfig # tapes
8.
Load a tape and then check the status of the tape drive. # mt status
15.1.4 How to Select the Tape Drive

The types of servers that are not equipped with an internal tape drive, such as Netra 240, are equipped with an external tape drive. By default, the external tape drive of these server types is /dev/rmt/0. The types of servers without an external tape drive, such as V890 and E4900, are equipped with an internal tape drive, By default, the internal tape drive of these server types is also /dev/rmt/0. If the servers with an internal tape drive, such as V890 and E4900, are equipped with an external tape drive, which tape drive should the backup data be save on?
Question
If the system has multiple tape drives, which tape drive should be used for storing the backup data?
Answer
1. Check for the number of tape drives in the system. # ls /dev/rmt

0 0b l 0bn 0c 0cb 0cbn 0cn 0h 0hb 0hbn 0hn 0l 0lb 0lbn 0ln 0m 0mb 0mbn

0mn 0n 0u 0ub 0ubn 0un
If the command result shows only the logical device files that are preceded by 0, you can infer that only one tape drive is connected. If the command result also shows the logical device files that are preceded by 1, you can infer that two tape drives are connected.
2.
Identify the type of a tape drive. Based on the number of tape drives obtain from 1, determine the type of each tape drive. # mt -f Name of the logical device config Determine the type of the first tape drive. # mt -f /dev/rmt/0 config
"HP C7438A", "HP DAT-72", "CFGHPDAT72"; CFGHPDAT72 = 2,0x34,0,0x18659,4,0x47,0x47,0x47,0x47,3,120,420,3600,36000,3600, 3600,17400;
As indicated by the command result, the type of the first tape drive is HP DAT-72G. This type of tape drive supports the 36 or 72 GB tape. This tape drive matches the logical device / dev/rmt/0. Determine the type of the second tape drive. # mt -f /dev/rmt/1 config
"CERTANCEULTRIUM 3", "Certance Ultrium 3", "CFGCERTANCEULTRIUM3"; CFGCERTANCEULTRIUM3 = 2,0x3B,0,0x18619,4,0x40,0x42,0x44,0x44,3,120,3600,2100, 3600,2100,2100,10800;
As indicated by the command result, the type of the second tape drive is Certance Ultrium 3. This type of tape drive supports the 400 or 800 GB tape. This tape drive matches the logical device /dev/rmt/1. 3. Check the status of the tape drive. Insert a tape into the tape drive and check whether the tape drive is operational. This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example. # mt -f /dev/rmt/0 status If the command results are similar to the following information, you can infer that the tape drive is functioning well:

15.1.5 What Do the files in the etc/rc2.d Folder of Solaris Mean

This describes the definition of the files in the /etc/rc2.d folder of the Solaris.
Question
What do the files in the /etc/rc2.d folder of the Solaris mean?
Answer
There are two types of files in /etc/rc2.d: files starting with S and files starting with K.

l
When the Solaris starts, the Solaris runs the files starting with S in the folder /etc/rc2.d in alphabetical order. When the Solaris stops, the Solaris runs the files starting with K in the folder /etc/rc2.d in alphabetical order. S98sybase: for starting the Sybase S98TAO: for starting the TAO service S99IMAP: for starting the M2000 service program S99Collector: for starting the M2000 Diagnosis
NOTE
The M2000 server installer creates three start files in the folder /etc/rc2.d/:
l l l l
l l
In the /etc directory, the rc0.d, rc1.d, rc2.d, rc3.d, and rcS.d map to phase 0, phase 1, phase 2, phase 3, and single user phase in the start process respectively. The Solaris completes different tasks in different phases. For example, the Solaris checks the memory in phase 0, checks the hardware in phase 1, and runs the user-defined auto-run scripts in phase 2.
15.1.6 How to View the Hardware Settings of the M2000 Server

This describes how to view the hardware settings of the M2000 server.
Question
How to check the Sun server hardware configuration and memory size?
Answer
To view settings about the server hardware, perform the following steps on the server: 1. 2. Log in as user root. Check different items by running the commands listed in Table 15-2.
Table 15-2 Checking the server configuration No. 1 2 3 4 Command # uname -aX # prtconf|grep Memory # psrinfo -v # prtdiag Output Server model and number of CPUs Memory size CPU status Check the status of the hardware.
15-6
Issue 05 (2008-05-20)
15.1.7 How to Solve Auto Solaris Shutdown When Connection Between the Server and the TC Is Broken
This describes how to avoid automatic Solaris shutdown when the connection between the server and the TC is broken.
Question
When the serial port cable connecting the LOM serial port, SC serial port, or RSC serial port of the M2000 server and the TC (or terminal) is disconnected, the operating system is shut down automatically. How to solve this problem?
Answer
According to the default settings of the Solaris, the system is shut down if the connection between the server and the TC (or terminal) is broken. To solve the problem, perform the following steps: 1. 2. 3. 4. 5. 6. Reconnect the cable between the server and the TC (or terminal). Log in to the server as user root on the TC (or terminal). Open /etc/default/kbd. Remove the character # from the line KEYBOARD_ABORT=alternate. Save the file and exit. Restart the system. # /usr/sbin/shutdown -i6 -g0 -y After you remove the serial port cable that connects the M2000 server and the TC (or terminal), the Solaris is still operational.
15.1.8 How to Check the Device Status of the M2000 Server

This describes the common commands used to check the device status of the M2000 server.
Question
Which commands are often used to check the device status?
Answer
Table 15-3 lists the commands often used for checking the device status. Table 15-3 Commands for checking the device status N Item o . 1 Hard ware Confi Description Command Check the disk status. Hardware configuration
# iostat -E
Issue 05 (2008-05-20)
15-7
N Item o . gurati on
Description Command Check the CPU status. Check the device tree. Check the power supply.
Hardware configuration
# psrinfo -v # prtconf -D # /usr/platform/sun4u/sbin/prtdiag -v # ifconfig -a # kstat ce0 | grep ifspeed The network port name varies according to the configuration. # netstat -r # snoop -d ce0 The network port name varies according to the configuration.
Netw ork conn ectio n and confi gurati on
Check network configuration. Check network port speed. Check route information. Locate faults and check network port messages. Locate faults and export network port messages.
# /opt/SUNWexplo/bin/explorer The results, such as /opt/SUNWexplo/output For example:

explorer.83bbbcad.osssvr-2005.08.15.02.05 explorer.83bbbcad.osssvr-2005.08.15.02.05.tar.gz
Check MAC settings for the IPMP technology. 3 File syste m and disk partit ionin g Check the file system. Check disk partitioning.
# eeprom # eeprom local-mac-address?=true
# more /etc/vfstab # df -k Specify disk (enter its number): format 0 format> format p partition> format p
Check system error logs.
# vi /var/adm/messages /#err (This command is used to search the information that contains "# err".)
15-8
Issue 05 (2008-05-20)
N Item o .
Description Command Check system error log settings. Redirect logs from T3/SC/ Domain to Blade 150. Check for the Solaris version and patch. Check all Solaris patches.
Add the contents below to /etc/syslog.conf on the Blade 150:

local7.notice local0.notice local1.notice /var/adm/messages.t3 /var/adm/messages.SC /var/adm/messages.DomainA
Check messages in /var/adm.
# uname -a
# showrev -p # vxdg list This command is not applicable for the Netra 20 or Netra 240. # vxdisk list All hard disks are online. This command is not applicable for the Netra 20 or Netra 240.
Volu me and mirro r
Check volume information. Check volume information.
Check volume information.
# vxprint -th -g rootdg The KSTATE column of pl, sd, and v is displayed ENABLED, and the STATE column is displayed ACTIVE. This command is not applicable for the Netra 20 or Netra 240. # cd /etc/vx/bin # vxslicer -p
Back up the license of Volume Manager. Check the mirror status. 5 Tape drive Check the tape drive status. Rewind the tape. Forward one step. Forward two steps. Backward two steps.
# metastat This command is applicable only for the Netra 20. # mt stat # mt rewind # mt fsf # mt fsf 2 # mt bsf 2
Issue 05 (2008-05-20)
15-9
N Item o .
Description Command Check the tape content. Copy files to the tape. Restore files from the tape to the disk. Check the Solaris system backup. Back up the Solaris to the tape.
# gtar tfM /dev/rmt/0 # tar cvf /dev/rmt/0nfile name # gtar xvPfM /dev/rmt/0
# ufsrestore -t /dev/rmt/0n
# ufsdump 0ucf /dev/rmt/0n backup folder For example: # ufsdump 0ucf /dev/rmt/0n backuprestore # ufsdump 0ucf /dev/rmt/0n /dev/vx/rdsk/rootvol
Restore operating system from tape. Configure the tape drive. 6 CD drive r Flopp y disk Configure the CD-ROM. Configure the floppy disk.
# ufsdump rvf /dev/rmt/0n
# drvconfig # tapes # mount -F hsfs -o ro /dev/rdsk/c0t6d0s0 /cdrom
# volcheck # mount -F pcfs /dev/diskette/floppy
15.1.9 Why Cannot Enter the Domain Console of Sun Fire E4900
This describes the solutions to the failure to enter the domain console of the Sun Fire E4900.
Question
When you attempt to enter the domain console, the system displays the message that the system is busy.
Answer
The domain console allows for only one connection. If a user is already connected to the domain console, the system displays the message that the system is busy. To enter the domain console, perform the following steps:
1. 2. 3. 4.
Enter the platform shell. Run the connections command to view the connection results. Run the disconnect id command to disconnect the console. Enter the console.
Example
osssvr-1-sc0:SC> connections
ID --1 8 11 Hostname ----------------------------Localhost Localhost 10.0.119.150 Idle Time --------00:01 00:01 Connected On -------------Aug 26 17:13 Aug 30 13:51 Aug 30 15:10 Connected To -------------Platform Domain A Platform
osssvr-1-sc0:SC> disconnect 8 osssvr-1-sc0:SC> connections

ID --1 11 Hostname ----------------------------Localhost 10.0.119.150 Idle Time --------00:01 Connected On -------------Aug 26 17:13 Aug 30 15:10 Connected To -------------Platform Platform
osssvr-1-sc0:SC>
15.1.10 How to Change the Port Number of the FTP Server?

By default, the port number of the FTP server is 21. You need to change the port number of the FTP server according to the actual requirement.
Question
How to Change the Port Number of the FTP Server?
Answer
This part takes the change of the port number from 21 to 1234 as an example. To change the port number of the FTP server, perform the following steps: 1. 2. 3. Log in to the server as user root. Run the following command to modify the /etc/services file: # vi /etc/services Identify the following line, change 21 to 1234, and then run the wq! command to save and exit the vi editor:
ftp 21/tcp
4.
Run the following command to make the modification to take effect. # svcadm disable /omc/ftp:default # svcadm enable /omc/ftp:default
Issue 05 (2008-05-20)
15-11
15.1.11 How to Query a Time Zone Name

This describes how to query a time zone name. Before querying the DST rules of a time zone, you must know the name of the time zone. Based on the time zone name, you can query the corresponding DST rules.
Question
How to query the name of a time zone?
Answer
To query the name of a time zone, perform the following steps: 1. 2. Log in to the Solaris server as user root. Obtain the information on the country code of the time zone. # more /usr/share/lib/zoneinfo/tab/country.tab A part of the content to be obtained from the file is as follows:
... BR CL CN ... Brazil Chile China
Based on the previous information, you can confirm that the country codes of Brazil, Chile, and China are BR, CL, and CN respectively. 3. Based on country codes, obtain the information on time zone names. # more /usr/share/lib/zoneinfo/tab/zone_sun.tab
l
The format of the zone_sun.tab file is country code + longitude and latitude + time zone name + comments. The north latitude and the east longitude are considered to be positive. The south latitude and the west longitude are considered to be negative.
A part of the content to be obtained from the file is as follows:

... #country#code coordinates TZ comments BR -0351-03225 America/Noronha Brazil/DeNoronha Atlantic islands BR -0127-04829 America/Belem Amapa, E Para BR -0343-03830 America/Fortaleza NE Brazil (MA, PI, CE, RN, PB) BR -0803-03454 America/Recife Pernambuco BR -0712-04812 America/Araguaina Tocantins BR -0940-03543 America/Maceio Alagoas, Sergipe BR -1259-03831 America/Bahia Bahia BR -2332-04637 America/Sao_Paulo Brazil/East S & SE Brazil (GO, DF, MG, ES, RJ, SP, PR, SC, RS) BR -2027-05437 America/Campo_Grande Mato Grosso do Sul BR -1535-05605 America/Cuiaba Mato Grosso BR -0846-06354 America/Porto_Velho W Para, Rondonia BR +0249-06040 America/Boa_Vista Roraima BR -0308-06001 America/Manaus Brazil/West E Amazonas BR -0640-06952 America/Eirunepe W Amazonas BR -0958-06748 America/Rio_Branco Brazil/Acre Acre CL -3327-07040 America/Santiago Chile/Continental most locations CL -2709-10926 Pacific/Easter Chile/EasterIsland Easter Island & Sala y Gomez CN +3114+12128 Asia/Shanghai PRC ...
The time zone names of Brazil, Chile, and China are listed in Table 15-4.
Table 15-4 Example of the matching table between countries and time zone names Coun try Time Zone Name America/ Noronha America/Belem America/ Fortaleza America/Recife America/ Araguaina America/Maceio America/Bahia America/ Sao_Paulo America/ Campo_Grande America/Cuiaba America/ Porto_Velho America/ Boa_Vista America/Manaus America/ Eirunepe America/ Rio_Branco America/ Santiago Pacific/Easter China PRC Brazil/ DeNoronha Brazil/East Brazil/West Brazil/Acre Chile/ Continental Chile/ EasterIsland Remarks Atlantic islands Amapa, E Para NE Brazil (MA, PI, CE, RN, PB) Pernambuco Tocantins Alagoas, Sergipe Bahia S & SE Brazil (GO, DF, MG, ES, RJ, SP, PR, SC, RS) Mato Grosso do Sul Mato Grosso W Para, Rondonia Roraima E Amazonas W Amazonas Acre
Brazil
Most locations Easter Island & Sala y Gomez -
Chile
NOTE
The time zone names of Europe are special. All the European countries are geographically located in the east Europe, middle Europe, and west Europe. The corresponding time zone names of the east Europe, middle Europe, and west Europe are EET, MET, and WET respectively.
Issue 05 (2008-05-20)
15-13
15.2 FAQ About the Sybase

This describes the FAQs and solutions related to the Sybase. 15.2.1 How to Know Whether the Sybase Is Started This describes how to determine whether the Sybase is started. 15.2.2 How to Start the Sybase This describes how to start the Sybase service. 15.2.3 How to Stop the Sybase This describes how to stop the Sybase. 15.2.4 How to View the Name of the Sybase Server This describes how to view the name of the Sybase server when the Sybase database is running. 15.2.5 How to Handle Database Alarms This describes why database alarms are generated and how to handle these database alarms. 15.2.6 How to View Database Deadlock Information This describes how to check the deadlock information about the Sybase database. 15.2.7 Why the Sybase Is Not Started After the M2000 Is Restarted This describes why the Sybase is not started after the M2000 is restarted. 15.2.8 Why the Sybase Is Not Started After Run svc_profile.sh This describes why the Sybase is not started after the execution of the script svc_profile.sh. 15.2.9 How to Solve Sybase Backup Abort This describes how to solve the Sybase backup abort. 15.2.10 How to Handle the Problem That the Mouse Pointer Changes into an Hourglass upon History Alarm Query This describes how to handle the problem that the mouse pointer changes into an hourglass upon history alarm query.
15.2.1 How to Know Whether the Sybase Is Started

This describes how to determine whether the Sybase is started.
Question
How to check the startup status of the Sybase?
Answer
To know whether the Sybase is started, perform the following steps: 1. 2. Log in to the server as user dbuser. Run the following commands: -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ./showserver
UID dbuser PID 341 PPID 339 C 0 STIME TTY Oct 21 ? TIME CMD 0:01 /opt/sybase/ASE-15_0/bin/
15-14
Issue 05 (2008-05-20)
backupserver -SSYB_back -e/opt/sybase/ASE-15_0/install root 3104 3103 1 Oct 25 ? 312:20 /opt/sybase/ASE-15_0/bin/ dataserver -sSYB -d/export/home/sybdev/master_dev.dat -e/opt/sybase/
If the output includes dataserver and backupserver, you can infer that the data service process and the backup service process of the database are already started.
15.2.2 How to Start the Sybase

This describes how to start the Sybase service.
Question
How to start the Sybase service?
Answer
To start the Sybase, perform the following steps: 1. 2. 3. Log in to the Solaris as user dbuser. Check whether the Sybase is started by referring to 15.2.1 How to Know Whether the Sybase Is Started. Run the following command: -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ./startserver -f ./RUN_SYB
NOTE
-bash-3.00$ nohup ./startserver -f ./RUN_SYB_back >/dev/null In the previous command, SYB is the name of the database server. In actual situations, replace this name with the real name.
15.2.3 How to Stop the Sybase

This describes how to stop the Sybase.
Question
How to stop Sybase service?
Answer
To stop the Sybase, perform the following steps: 1. 2. Log in to the Solaris as user dbuser. Run the following commands: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> shutdown SYB_BACKUP 2> go 1> shutdown
2> go
NOTE
Run the ps -ef | grep sybase | grep -v grep command to check whether the Sybase stops. If no output exists, you can infer that the Sybase is already stopped. If the output still exists, run the kill -9 PID of Sybase command to force the Sybase to stop. After the M2000 server is installed, the Sybase starts automatically upon the startup of the Solaris.
15.2.4 How to View the Name of the Sybase Server

This describes how to view the name of the Sybase server when the Sybase database is running. 1. 2. Log in to the server as user dbuser. Run the following command to view the name of the Sybase server: -bash-3.00$ ps -ef | grep "dataserver -s" | grep -v grep In the command result, the value after the -s parameter is the name of the database server. As shown in the following command result, the name of the database server in this example is SYB:
15.2.5 How to Handle Database Alarms

This describes why database alarms are generated and how to handle these database alarms.
Problem Description
Alarms are generated in the M2000 database, such as the fmdb database and the pmdb database.
Cause Analysis and Solution

The alarms generated in the M2000 database are caused by lack of database space and low alarm threshold.
l
Alarms are generated in the fmdb alarm database. Cause analysis The alarm dump mechanism is not configured correctly, which leads to a scenario in which the alarm data is not dumped immediately. Alarms are generated due to lack of alarm database space. Solution Check and modify the settings for alarm data dump on the M2000 client. For details about how to check and modify the settings for alarm data dump, refer to 8.3 Clearing M2000 Databases.
Alarms are generated in the pmdb alarm database. Cause analysis The pmdb alarm database does not delete the outdated performance data in time, which leads to a scenario in which the outdated performance data is not dumped. Alarms are generated due to lack of alarm database space. Solution
15-16
Issue 05 (2008-05-20)

Modify the configuration file on the M2000 server and restart performance services. Decrease the number of measured objects and measured counters by operating on the M2000 client. Check and modify the settings for performance data dump. For details on how to check and modify the settings for performance data dump, refer to 8.3 Clearing M2000 Databases.
Alarms are generated in the omcdb database, swmdb database, and other databases. Cause analysis

The alarm threshold is configured extremely low. The number of managed NEs exceeds the management capacity of the M2000. The data in the database is not dumped in time. Alarms are generated due to lack of database space. Modify the alarm threshold on the M2000 client. Decrease the number of the NEs under the management of the M2000. Check and modify the settings for data dump on the M2000 client. For details about how to check and modify the settings for data dump, refer to 8.3 Clearing M2000 Databases.
Solution

15.2.6 How to View Database Deadlock Information

This describes how to check the deadlock information about the Sybase database.
Question
How to check the deadlock information about the Sybase database when a fault occurs?
Answer
To view the database deadlock information, perform the following steps: 1. 2. Log in to the Solaris as user dbuser. Run the following commands: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_lock 2> go
NOTE
dbuser 15745 15744 3 11:00:39 ? 2:19 /opt/sybase/ASE-15_0 /bin/dataserver -sSYB -d/data/master.dat -e/opt/sybase/ASEThe class column will display the cursor name for locks associated with a cursor for the current user and the cursor id for other users. fid spid loid locktype table_id page
Issue 05 (2008-05-20)
15-17
row dbname class context ------ ------ ----------- ---------------------------- ----------- ---------------- --------------- --------------------------------------------------------0 10 20 Sh_intent 464004684 0 0 master Non Cursor Lock (1 row affected) (return status = 0)
NOTE
In the command result, Non Cursor Lock shows no dead lock is available. The database name is master,spid=10,table_id=464004684. To check further information, run the following commands:
1> dbcc traceon(3604) 2> go

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.
NOTE
The command output displays the traced information on the monitor.
1> use master 2> go 1> select object_name(464004684) 2> go

-----------------------------spt_values (1 row affected)
1> dbcc sqltext(10) 2> go

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.
NOTE
The commands check the messages of spid=10,table_id=464004684 of the master database.
15.2.7 Why the Sybase Is Not Started After the M2000 Is Restarted
This describes why the Sybase is not started after the M2000 is restarted.
Question
Why does the Sybase not start after the M2000 server restarts? Open the Sybase system log SYB.log. Find the following contents:
kernel Configuration Error: Configuration file, '/opt/sybase/SYB.cfg', does not exist. kernel Warning: A configuration file was not specified and the default file '/opt/sybase/SYB.cfg' does not exist. SQL Server creates the default file with the default configuration.
15-18
Issue 05 (2008-05-20)
kernel Configuration file '/opt/sybase/SYB.cfg' has been written and the previous version has been renamed to '/opt/sybase/SYB.076'
Causes
The file SYB.cfg records the settings of the Sybase. If the system cannot find SYB.cfg, it creates new SYB.cfg for storing the default settings of the Sybase. The major cause is that the default values in SYB.cfg are not consistent with those required by the M2000 system. The file SYB.cfg is generated once the Sybase is installed, and this file cannot be deleted. The Sybase cannot find the file because the Sybase is not authorized to read this file. The M2000 server, after being installed, restarts the Sybase through dbuser on boot. The user account dbuser, however, is not authorized to read SYB.cfg.
SYB.cfg Ownership
After the Sybase is installed, the owner of SYB.cfg is the user who has installed the Sybase, that is, dbuser in the M2000 system. If user root starts the Sybase and changes Sybase settings through isql, root becomes the owner of SYB.cfg. Thus, dbuser cannot read SYB.cfg. If dbuser starts the Sybase, dbuser remains as the owner of SYB.cfg even after root changes the Sybase settings through isql.
Solution
When the Sybase creates SYB.cfg, the Sybase renames the existing SYB.cfg as SYB.*. Find the actual file name in SYB.log, for example, SYB.076. The solution is to rename SYB.076 as SYB.cfg and reset the ownership of this file. To handle the faults, perform the following steps: 1. Log in to the server as user root. # cd /opt/sybase # cp SYB.076 SYB.cfg # chown -R dbuser:staff /opt/sybase # su - dbuser 2. Start the Sybase. For details, see 15.2.2 How to Start the Sybase. To avoid this problem, start the Sybase as user dbuser.
15.2.8 Why the Sybase Is Not Started After Run svc_profile.sh

This describes why the Sybase is not started after the execution of the script svc_profile.sh.
Description
After you run the script svc_profile.sh in M2000 Installation Directory, the Sybase service is not started. The M2000 server default installation path is /opt/OMC.
Analysis
The M2000 needs to support multiple Sybase versions. Therefore, you need to set the value of $SYBASE in svc_profile.sh to the related folder of the M2000, such as M2000 server installation path/3rdTools/sybase. The M2000 server default installation path is /opt/OMC. You, however, must set the value of $SYBASE to the Sybase installation folder to start the Sybase service. The two settings conflict. In this case, if you set the value of $SYBASE in svc_profile.sh to the related folder of the M2000, the Sybase service fails to start.
Solution
Before you start the Sybase service, run SYBASE.sh in Sybase installation path. The Sybase default installation path is /opt/sybase/.
15.2.9 How to Solve Sybase Backup Abort

This describes how to solve the Sybase backup abort.
Question
Why does the Sybase backup database stop abnormally?
Answer
Run the nohup command before you start the Sybase. 1. 2. Log in to the Solaris as user dbuser. Run the following command: -bash-3.00$ cd /opt/sybase/ASE-15_0/install/ -bash-3.00$ nohup ./startserver -f ./RUN_SYB_back >/dev/null In the previous command, SYB is the name of the database server. In actual situations, replace this name with the real name.
NOTE
15.2.10 How to Handle the Problem That the Mouse Pointer Changes into an Hourglass upon History Alarm Query
This describes how to handle the problem that the mouse pointer changes into an hourglass upon history alarm query.
15-20
Issue 05 (2008-05-20)
Question
After you view the query results of history alarms by using the up and down arrows or scroll bar, the cursor indicates every 125 records that the system is busy. Each busy interval lasts about 10 seconds.
Answer
The Sybase database returns the results slowly. The statistics cannot be updated automatically. This causes the Sybase to return the results slowly. You need to update the statistics manually. 1. Obtain the configuration information of the current database in M2000 server installtion path/etc/conf/ifmssvc.xml. Find the following configuration items:
<databaseparam name="databaseparam"> <dbtag name="ifms_common"> <param name="dbservername">SYB</param> <param name="dbusername">sa</param> <param name="dbuserpasswd" type="encrypt">f4310554853445</param> <param name="dbname">fmdb</param> <param name="dblib">libctl63-md.so</param> <param name="dbType">SYBASE</param> <param name="dbMonitor">enable</param> </dbtag>
NOTE
l l l l
<param name="dbservername">SYB1</param>: Sybase database server name. <param name="dbusername">sa</param>: Sybase user name. <param name="dbuserpasswd" type="encrypt">f4310554853445</ param>: Encypted Sybase user password. <param name="dbname">fmdb</param>: Alarm database name.
2.
Access the Sybase database. -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa
NOTE
3.
Run the following commands after you access the database: 1> use fmdb 2> go 1> update statistics tbl_his_alm 2> go
NOTE
l l
fmdb is the alarm database name. obtain the name from ifmssvc.xml. tbl_his_alm is the history database table name.
Issue 05 (2008-05-20)
15-21
15.3 FAQ About the TCP/IP Network

This describes some FAQs and solutions related to the TCP/IP network. 15.3.1 Why the Network Port Is Abnormal This describes how to handle the problem of the abnormal network port. 15.3.2 How to Connect the Client to the Server with More than One IP Address This describes how to set up the connection between the client and the server using multiple IP addresses.
15.3.1 Why the Network Port Is Abnormal

This describes how to handle the problem of the abnormal network port.
Question
During the login from the Sun Netra 240 console through telnet, why does the Sun Fire E4900 server respond slowly?
Answer
The cause is that the two ports have the same MAC address. To solve the problem, perform the following steps: 1. Check the network connection. # ifconfig -a Check the MAC addresses of the two ports. 2. Check the value of local-mac-address?. If the value is false, change the value to true. # eeprom # eeprom "local-mac-address?"=true 3. Restart the Solaris.
15.3.2 How to Connect the Client to the Server with More than One IP Address
This describes how to set up the connection between the client and the server using multiple IP addresses.
Question
Why cannot the client set up a connection with the server?
Answer
If the server has multiple IP addresses, specify one for M2000 services. Otherwise, the client cannot set up a connection with the server.
Stop M2000 services and the Sybase before you change the IP address of the M2000 server. No performance data or alarm data is processed during the process where you change the server IP address. After the services are resumed, the M2000 updates the data with the NEs and processes the data. To specify an IP address for M2000 services, perform the following steps: 1. 2. 3. Log in to server as user root. If the M2000 services server is running, stop the M2000 services. To know how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Switch to dbuser and run the following commands to stop the Sybase. # su - dbuser To know how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. 4. 5. Switch back to user root. # su - root Edit /etc/hosts. The host name corresponds to one IP address for connecting clients and NEs. For example, the server is configured with two IP addresses: 10.161.70.200 and 10.121.5.208. The later one is used for connecting clients. In M2000 server installation path/etc/conf/tao.cfg, the host name is aries. Open /etc/hosts, and then add # on the left of 10.161.70.200 to comment off this line.
# # Internet host table # 127.0.0.1 localhost #10.161.70.200 aries loghost 10.121.5.208 aries loghost
6.
Restart the Solaris. # sync; sync; sync; sync; sync; sync; # /usr/sbin/shutdown -g0 -y -i6 If the M2000 software is installed, the Sybase and the M2000 services restart automatically after the Solaris restarts.
15.4 FAQ About the M2000 Server Software

This describes some FAQs and solutions related to the M2000 server software. 15.4.1 Why M2000 Services Restart Abnormally This describes how to handle the problem of the abnormal restart of the M2000 services. 15.4.2 Why M2000 Services Stop Abnormally This describes how to handle the problem of abnormal stop of the M2000 services. 15.4.3 Why M2000 Services Fail to Start or Stop This describes how to handle the failure to start or stop the M2000 services. 15.4.4 Why M2000 Dynamic Data Backup Fails This describes how to handle the failure to back up the dynamic M2000 data. 15.4.5 How to Back Up and Restore the M2000 Mediation Software This describes how to back up and restore the M2000 mediation software.
15.4.6 How to Back Up the M2000 Configuration Files Before modifying the M2000 configuration files, you need to back up them. This enables you to restore the M2000 configuration files in the event of an operation failure. 15.4.7 How to Restore the M2000 Configuration Files If the M2000 configuration files are backed up before you modify them, you can restore the M2000 configuration files in the event of an operation failure.
15.4.1 Why M2000 Services Restart Abnormally

This describes how to handle the problem of the abnormal restart of the M2000 services.
Question
Why do M2000 services restart abnormally?
Answer
The possible causes are as follows:
l l
The Sybase is faulty. The M2000 system is faulty.
To solve the problem, perform the following steps: 1. 2. 3. Log in to the server as user root. If the M2000 services server is running, stop the M2000 services. To know how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Switch to dbuser and run the following commands to stop the Sybase. # su - dbuser To know how to stop the Sybase, refer to 15.2.3 How to Stop the Sybase. 4. Set the Sybase parameters. Set the Sybase database parameter total memory and modify the RUN_SYB file. For details, refer to software installation manual related to each server type. 5. Start the Sybase. To know how to start the Sybase, refer to 15.2.3 How to Stop the Sybase. # su - root 6. Change to the default installation path of the M2000, that is, /opt/OMC and start the M2000 services. To know how to start the M2000 services, refer to 7.3.3 Starting M2000 Services. 7. Check system logs. Check the system files in the /export/home/omc/var/syslog directory to find out the reason why the service is abnormal.
15.4.2 Why M2000 Services Stop Abnormally

This describes how to handle the problem of abnormal stop of the M2000 services.
Question
Run the following command: # svc_adm -cmd status When the value of not running in the command result is greater than 0, the service is stopped abnormally. How to solve this problem?
Answer
The possible causes are as follows:
l l
An error occurs during program running The startup is stopped manually.
To solve this problem, perform the following steps: 1. 2. Log in to the server as user root. Switch to the installation path of the M2000 . The default installation path of the M2000 is /opt/OMC. # cd M2000 installation path 3. Start M2000 services. # . ./svc_profile.sh # start_svc Do not stop the startup process manually. 4. If the problem persists, contact your Huawei local office for technical support.
15.4.3 Why M2000 Services Fail to Start or Stop

This describes how to handle the failure to start or stop the M2000 services.
Question
Why can the following commands not be successfully run?
l l l
start_svc stop_svc kill_svc
Answer
If the output is command not found, the possible cause is that you do not run the environment script before running these commands. To solve the problem, perform the following steps: 1. 2. Log in to the server as user root. Run the environment script. For details, refer to 14.1.1 svc_profile.sh Script.
15.4.4 Why M2000 Dynamic Data Backup Fails

This describes how to handle the failure to back up the dynamic M2000 data.
Question
During system backup, the progress bar stops at 30%. Why does the system backup fail?
Causes
l l
The character set settings for the server and the client are not consistent. The Sybase backupserver process is executed during system backup. It generates several sub-processes during the backup. If the backupserver process is stopped abnormally, the sub-processes keep running. Thus, the system backup fails.
Solution for Cause 1

The solution for cause 1 is to unify the character settings of the server and client. Perform the following steps: 1. Check character set of the server. # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpsort 2> go
NOTE
dbuser 15745 15744 3 11:00:39 ? 2:19 /opt/sybase/ASE-15_0 /bin/dataserver -sSYB -d/data/master.dat -e/opt/sybase/ASECollation Name Collation ID ------------------------------ -----------Loadable Sort Table Name -----------------------------Sort Order Description -----------------------------------------------------------------Character Set = 171, cp936 CP936 (Simplified Chinese). Class 2 Character Set Sort Order = 50, bin_cp936 Binary sort order for simplified Chinese using cp936. (return status = 0)
2.
Check the current language environment. -bash-3.00$ echo $LANG C
3.
Set the client character set according to the language environment and server character set. -bash-3.00$ cd /opt/sybase/locales -bash-3.00$ vi locales.dat Find the following content. Ensure that the character set settings in bold below are the same as the settings on the server.
15-26
Issue 05 (2008-05-20)

[sun_svr4] ; from Solaris International Developer's Guide ; ISBN 0-13-031063-8 ; refer to "man setlocale()" locale = C, us_english, cp936 locale = fr, french, iso_1
-bash-3.00$ exit
Solution for Cause 2

The solution for cause 2 is to stop the sub-processes. Perform the following steps: 1. 2. Log in to the server as user root. Run the following command for process query. # ps -ef | grep svc_backuprestore
root 3486 1318 0 08:42:17 root 3270 18934 0 08:41:19 svc_backuprestore -cmd backup -m root 3271 3270 4 08:41:19 -cmd backup -m all pts/8 0:00 grep svc_backuprestore ? 0:00 sh -c /opt/OMC/bin/ all 2> /dev/null ? 0:08 /opt/OMC/bin/svc_backuprestore
3.
Delete manually other processes except grep svc_backuprestore. In this example, delete the processes titled 3270 and 3271. # kill -93270 3271 Run the following command for process query. # ps -ef | grep syb | grep -v dataserver | grep -v grep
dbuser 380 1 0 08:53:29 ? 0:02 /opt/sybase/ASE-15_0/bin/ backupserver -SSYB_back -e/opt/sybase/ASE-15_0/install dbuser 6217 380 0 08:52:34 ? 0:00 /opt/sybase/ASE-15_0/bin/ sybmultbuf 19 11 14 /opt/sybase/ASE-15_0/install/SYB_b dbuser 6218 6217 0 08:52:34 ? 0:00 /opt/sybase/ASE-15_0/bin/ sybmultbuf 19 11 14 /opt/sybase/ASE-15_0/install/SYB_b
4.
5.
Delete manually the other processes in the database except backupserver. In this example, delete the processes titled 6217 and 6218. # kill -96217 6218
15.4.5 How to Back Up and Restore the M2000 Mediation Software

This describes how to back up and restore the M2000 mediation software.
Question
How to guarantee that the mediation software falls back to the old version in case of a failure to install a new version?
Answer
The M2000 server installation is categorized into public-layer installation and mediation installation. Back up the mediation version so it can be restored in case of a new version installation failure. Take the RNC as an example. To back up the mediation of the RNC, perform the following steps:
1. 2.
Create a backup folder. # mkdir -p /export/home/RNCNE_bak/C02B002 If the default installation path of the M2000 server software is /opt/OMC, back up the existing mediation version. # cp -Rf /opt/OMC/med/RNCNE/ iManagerM2000_RNC_MATCH_CHS_V200R002C02B002 /export/home/ RNCNE_bak/C02B002/.
3. 4.
If the M2000 services server is running, stop the M2000 services. To know how to stop the M2000, refer to 7.3.4 Stopping M2000 Services. Stop the TAO service. Run the command ps -ef | grep 9999|grep -v grep and check the output. If there is output, stop the TAO process using stop_tao_services.
5. 6.
Stop the fault locating tool. # /opt/OMC/bin/stop_collector Back up the nine databases: omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, pmcomdb, sumdb, and omctmdb. Ensure that the backup database service is started. Otherwise, log in as user dbuser and start the backup database service. # su - dbuser -bash-3.00$ cd /opt/sybase/ASE-15_0/install/ -bash-3.00$ nohup ./startserver -f ./RUN_SYB_back > /dev/null In the previous commands, SYB is the name of the database server. In actual situations, replace this name with the real name of the database server. Log out as user dbuser. Log in again as user root and create the backup directory. -bash-3.00$ exit # mkdir -p /export/home/RNCNE_bak/C02B002/dbbackup # chown -Rf a+rw /export/home/RNCNE_bak/C02B002/dbbackup # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> dump database omcdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ omcdb.dat" 2> go 1> dump database fmdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ fmdb.dat" 2>go 1> dump database pmdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ pmdb.dat" 2> go 1> dump database swmdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ swmdb.dat" 2> go 1> dump database itfndb to "/export/home/RNCNE_bak/C02B002/dbbackup/ itfndb.dat"
15-28
Issue 05 (2008-05-20)
2> go 1> dump database omclogdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ omclogdb.dat" 2> go 1> dump database omcsmdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ omcsmdb.dat" 2> go 1> dump database pmcomdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ pmcomdb.dat" 2> go 1> dump database sumdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ sumdb.dat" 2> go 1> dump database omctmdb to "/export/home/RNCNE_bak/C02B002/dbbackup/ omctmdb.dat" 2> go 1> exit -bash-3.00$ exit Take the RNC for example. If the default installation path of the M2000 server software is /opt/ OMC, perform the following steps to back up the mediation: 1. Set the operating environment for the M2000 system. # cd /opt/OMC # . ./svc_profile.sh 2. Uninstall the new version. # cd /opt/OMC/med/RNCNE/ iManagerM2000_RNC_MATCH_CHS_V200R002C02B002 # ./uninstall.sh The output is as follows:
the Uninstall NE Type is : RNCNE the Uninstall NE Version is : BSC6800V100R005C01B020 Environment variable M2K_ROOT is : /opt/OMC
Are you sure to continue? [y/n] y Press any key except y to exit. Press y to start uninstalling the new version. 3. Restore the mediation version. # cp -Rf/export/home/RNCNE_bak/C02B002/ iManagerM2000_RNC_MATCH_CHS_V200R002C02B002 /opt/OMC/med/RNCNE/. 4. Restore the databases omcdb, swmdb, fmdb, pmdb, itfndb, omclogdb, omcsmdb, and omctmdb through the Sybase data restoration function and enable the databases online. # su - dbuser -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> load database omcdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ omcdb.dat"
2> go 1> load database fmdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ fmdb.dat" 2> go 1> load database pmdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ pmdb.dat" 2> go 1> load database swmdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ swmdb.dat" 2> go 1> load database itfndb from "/export/home/RNCNE_bak/C02B002/dbbackup/ itfndb.dat" 2> go 1> load database omclogdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ omclogdb.dat" 2> go 1> load database omcsmdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ omcsmdb.dat" 2> go 1> load database omctmdb from "/export/home/RNCNE_bak/C02B002/dbbackup/ omctmdb.dat" 2> go 1> exit -bash-3.00$ exit 5. 6. Run the /opt/OMC/bin/start_svc script to start all services. Run the /opt/OMC/bin/start_collector script to start the fault location tool.
15.4.6 How to Back Up the M2000 Configuration Files

Before modifying the M2000 configuration files, you need to back up them. This enables you to restore the M2000 configuration files in the event of an operation failure.
Background Introduction
Before backing up the M2000 configuration files, you must ensure that the M2000 service is running normally. To check whether the M2000 service is running normally, see 7.3.2 Viewing the States of M2000 Services.
NOTE
This section describes how to back up only the M2000 configuration files rather than the configuration files of the operating system and other software.
Operation Procedure
1. 2.
15-30
Log in to the server as user root. Create or clear a backup directory.

# mkdir /export/bak If the backup directory already exists, create another backup directory or run the following command to clear the backup directory:
CAUTION
Perform the clear operation with caution. Before clearing the backup directory, ensure that the files in the directory are not required. If the files are required, you must back up them first. # rm -r /export/bak/* 3. 4. If the system is running the M2000 service, stop the M2000 service first. For details, see 7.3.4 Stopping M2000 Services. Check whether the Sybase service is running. If the Sybase service is not running, start the Sybase service. For details about how to start the Sybase service, see 15.2.1 How to Know Whether the Sybase Is Started and 15.2.2 How to Start the Sybase. Back up the M2000 configuration files. (1) Run the backup script. # cd /opt/OMC/tools/config # ./backupformodify.sh (2) When the main menu is displayed, choose 1--Single system. (3) As prompted by the system, enter the backup directory, the instance name of the database, the name of user sa, and the password of user sa. (4) When the following message is displayed, enter y to start backing up the M2000 configuration files. Enter n to exit.
5.
(5) After the backup is complete, enter q to exit.
15.4.7 How to Restore the M2000 Configuration Files

If the M2000 configuration files are backed up before you modify them, you can restore the M2000 configuration files in the event of an operation failure.
Background Introduction
Before restoring the M2000 configuration files, you must ensure that the Sybase service is running normally. To check whether the Sybase service is running normally, see 15.2.1 How to Know Whether the Sybase Is Started.
NOTE
This section describes how to restore only the M2000 configuration files rather than the configuration files of the operating system and other software.
Operation Procedure
1.
Issue 05 (2008-05-20)

2. 3.
If the system is running the M2000 service, stop the M2000 service first. For details, see 7.3.4 Stopping M2000 Services. Check whether the Sybase service is running. If the Sybase service is not running, start the Sybase service. For details about how to start the Sybase service, see 15.2.1 How to Know Whether the Sybase Is Started and 15.2.2 How to Start the Sybase. Restore the M2000 configuration files. (1) Run a script to restore the M2000 configuration files. # cd /opt/OMC/tools/config # ./restoreformodify.sh (2) When the main menu is displayed, choose 1--Single system. (3) As prompted by the system, enter the restoration directory, the instance name of the database, the name of user sa, and the password of user sa. (4) When the following message is displayed, enter y to start restoring the M2000 configuration files. Enter n to exit.
4.
(5) After the restoration is complete, enter q to exit.
15-32
Issue 05 (2008-05-20)
Index
Index
Symbols/Numerics
3320 disk array modifying IP address, 3-15 6140 disk array configuring IP address, 3-16 notify_agent, 7-7 omcne_agent, 7-5 partition_agent, 7-5 pm_agent, 7-6 pmexp_agent, 7-7 pmmedexp_agent, 7-14 pmmon_agent, 7-9 porttrunk_agent, 7-13 proxy_agent, 7-7 prsreport_agent, 7-15 prssum_agent, 7-15 scriptserver_agent, 7-12 sm_agent, 7-5 snmp_agent, 7-9 swm_agen, 7-7 tm_agent, 7-9
A
ACL modifying, 5-33 user, 5-25 adding route, 3-5 adding user, 14-33 adding user group, 14-35 adding user to user group, 5-23 agent 3rdTool_agent, 7-11 ce_agent, 7-15 chr_agent, 7-11 cmdc_agent, 7-11 cmserver_agent, 7-6 cpm_agent, 7-14 devdoc_agent, 7-11 em_agent, 7-4 fmexport_agent, 7-10 fmnotify_agent, 7-7 ifms_agent, 7-6 imapds_agent, 7-15 irp_agent, 7-8 itmserver_agent, 7-10 lic_agent, 7-4 log_agent, 7-10 maintain_agent, 7-13 manager_agent, 7-6 med_agent, 7-5 monitor_agent, 7-5 nelicense_agent, 7-14 neuser_agent, 7-10 nhcserver_agent, 7-13 nicserver_agent, 7-14 nimserver_agent, 7-9 nms_mml_agent, 7-12 NodeBCommission_agent, 7-13
B
backing up dynamic data, 10-12, 10-15 M2000 database, 8-16 static data, 10-20 system data, 10-29 backup policy, 10-5 static data, 10-3, 10-19 system data, 10-4, 10-28 bc, 14-49
C
calculation command, 14-49 cat, 14-26 cd, 14-8 change password, 14-35 changing IP address V890 SC, 3-11 changing password dbuser, 5-10 omcuser, 5-11 root, 5-10 sa, 5-15 checking
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd i-1
Issue 05 (2008-05-20)
Index
NTP status, 2-22, 2-24 time settings, 2-20 chmod, 14-14 chown, 14-16 clear, 14-29 clearing screen, 14-29 server database, 8-14 client clearing disk space, 4-4, 9-4 file system, 4-2, 9-2 modifying date, 2-31, 4-7 modifying time, 2-31, 4-7 modifying time zone, 2-31, 4-7 setting NTP, 2-32, 4-8 client management monitoring login state, 4-5, 6-13 setting accessible client, 4-6 client managerment setting max session, 4-4 collecting client fault data, 13-6 collecting server fault data fault occurrence time, 13-4 IP address, 13-4 server version, 13-5 site information, 13-3 Solaris version, 13-4 Sybase version, 13-5 command bc, 14-49 cat, 14-26 cd, 14-8 chmod, 14-14 chown, 14-16 clear, 14-29 compress, 14-22 cp, 14-12 date, 14-48 df, 14-38 du, 14-39 echo, 14-25 environment settings, 14-2 find, 14-17 finger, 14-57 ftp, 14-55 grep, 14-30 groupadd, 14-35 groupdel, 14-36 groupmod, 14-36 gtar, 14-21 head, 14-28 hostname, 14-45 ifconfig, 14-46 kill, 14-42 kill_svc, 14-4 ls, 14-9 man, 14-38 mkdir, 14-9
i-2
more, 14-27 mv, 14-13 netstat, 14-58 pack, 14-23 passwd, 14-35 ping, 14-53 pkgadd, 14-24 pkgrm, 14-25 prstat, 14-52 prtconf, 14-50 ps, 14-41 pwd, 14-8 rm, 14-13 rmdir, 14-9 route, 14-60 script, 14-47 start_svc, 14-3 stop_svc, 14-4 svc_adm -cmd reload, 14-5 svc_adm -cmd status, 14-5 svc_adm -cmd status -sysagent all, 14-6 svc_ps, 14-5 svc_stacks, 14-6 tail, 14-29 tar, 14-19 telnet, 14-54 uname, 14-45 uncompress, 14-23 unpack, 14-24 useradd, 14-33 userdel, 14-34 usermod, 14-34 vi, 14-30 whereis, 14-44 which, 14-44 who, 14-43 compare rights, 5-37 compress, 14-22 compressing file, 14-22, 14-23 configuring IP address 6140 disk array, 3-16 conneting administration console, 3-16 copying file, 14-12 cp, 14-12 CPU usage of server monitoring, 6-10 viewing, 6-4 creating folder, 14-9 solaris user, 5-13 user account, 5-22 user group, 5-19
D
database checking status, 11-21
Index
fmdb, 8-6 itfndb, 8-11 omcdb, 8-3 omclogdb, 8-3 omcsmdb, 8-4 omctmdb, 8-5 pmcomd, 8-8 pmdb, 8-6 sumdb, 8-9 swmdb, 8-8 viewing, 6-5, 8-12 database FAQ check database deadlock information, 15-17 know Sybase status, 15-14 mouse pointer changes into hourglass, 15-20 stop Sybase, 15-15 Sybase not start after run svc_profile.sh, 15-19 after server restarted, 15-18 date, 14-48 decompressing file, 14-23 default route setting, 3-4 Deleting OM user group, 5-36 deleting folder, 14-9 route, 3-5 solaris user, 5-14 user, 14-34 user group, 14-36 deleting a file, 14-13 df, 14-38 disk clear client space, 4-4, 9-4 clear server space, 9-9 viewing, 6-5, 6-13, 9-8, 9-9 disk array checking status, 11-26 disk usage check, 11-20 displaying current network status, 14-58 DST, 2-26 viewing rule, 2-26 du, 14-39 dynamic data backing up, 10-12, 10-15 restoring, 10-17
failure in starting operating system, 12-3 server, 12-2 system going into maintenance mode, 12-4
F
file system client, 4-2, 9-2 server, 9-5 find, 14-17 finger, 14-57 Force, exit, 5-44 ftp, 14-55
G
granting rights over new NEs to an OM user group, 5-20 grep, 14-30 groupadd, 14-35 groupdel, 14-36 groupmod, 14-36
H
hard disk checking status, 11-26 hardware check, 11-28 head, 14-28 help information, 14-38 hostname, 14-45
I
ifconfig, 14-46 IP address viewing, 14-46
K
kill, 14-42 kill_svc, 14-4
L
listing current login user information, 14-43 listing folder content, 14-9 log checking server log, 11-19 checking Solaris error log, 11-19 introducing system log, 6-3 viewing server log, 6-8 viewing solaris log, 6-10 log information collector collecting fault data, 13-6 login remote computer, 14-54 ls, 14-9
E
E4900 modifying SC IP address, 3-12 powering off, 1-9 powering on, 1-7 echo, 14-25 emergency maintenance client, 12-2 database device file lost, 12-4
Issue 05 (2008-05-20)
i-3
Index
M
M2000 database back up, 8-16 maintaining routing table, 14-60 maintenance backing up server system, 11-23 checking agent status number, 11-21 alarm box functionality, 11-13 alarm reception, 11-12 alarm timing configuration, 11-6 automatic log dump configuration, 11-7 connection status with NE, 11-18 core file, 11-22 database status, 11-21 disk usage, 11-20 file server configuration, 11-9 missing performance result, 11-12 NE log synchronization time, 11-8 NE synchronization time configuration, 11-11 network management capability threshold, 11-14 NMS connection, 11-13 omc alarm information, 11-14 performance measurement state, 11-11 route status, 11-18 server hardware, 11-28 server log, 11-19 server peripherals, 11-29 server power supply, 11-27 server status, 11-22 server status number, 11-21 server time, 11-26 SMC collection result, 11-29 Solaris error log, 11-19 system backup configuration, 11-9 system monitoring configuration, 11-10 checking disk array status, 11-26 checking local disk status, 11-26 items list, 11-4 maintenance items list, 11-4 man, 14-38 memory monitoring, 6-10, 6-10 memory usage of server viewing, 6-4 mkdir, 14-9 Modify information of an OM user, 5-34 password of an NE user, 5-39 modifying 3320 disk array IP address, 3-15 client date, 2-31, 4-7 time, 2-31, 4-7 time zone, 2-31, 4-7
i-4
date and time, 2-12 protection mode of file, 14-14 routing table, 14-60 time zone, 2-14, 2-28 user group information, 14-36 user login information, 14-34 modifying date on server, 2-12 modifying IP address E4900 SC, 3-12 Netra240 SC, 3-10 modifying protection mode of file, 14-16 modifying time on server, 2-12 Monitor OM user operations, 5-42 monitoring CPU usage of server, 6-10 disk usage of server, 6-10 memory usage of server, 6-10 more, 14-27 moving file, 14-13 mv, 14-13
N
NE user authorization principle, 5-7 Netra 240 modifying SC IP address, 3-10 Netra240 powering off, 1-3 powering on, 1-2 netstat, 14-58 network FAQ client has many IP addresses, 15-22 network port abnormal, 15-22 NM user authorization principle, 5-6 NTP checking status, 2-22, 2-24 set on client, 2-32, 4-8 setting NTP service, 2-20, 2-23 starting service, 2-21, 2-24 stopping service, 2-18
O
OM user modifying password, 5-35 OM user group deleting, 5-36 omc alarm information check, 11-14 operating system FAQ /etc/rc2.d, 15-5 auto shutdown, 15-7 check device status, 15-7 check tape device status, 15-3
Issue 05 (2008-05-20)
Index
enter E4900 domin console, 15-10 login through FTP, 15-3 login through telnet, 15-2 view hardware settings, 15-6 Operation Managed Domain, 5-19 managed domain, 5-24 private rights to an OM user, 5-23 rights to an OM user group, 5-20
S
script, 14-47 searching character string, 14-30 searching file, 14-17 sending character string to screen, 14-25 server clearing disk space, 9-9 file system, 9-5 modifying date, 2-12 modifying time, 2-12 server database clear, 8-14 server software FAQ backup adaptation, 15-27 dynamic data backup fail, 15-26 restore adaptation layer, 15-27 service restart abnormally, 15-24 service stop abnormally, 15-24 starting service fail, 15-25 stopping service fail, 15-25 server status browsing server log, 6-8 checking, 11-22 checking Solaris error log, 11-19 introducing monitor browse, 6-2 introducing system log, 6-3 set alarm threshold, 6-7 viewing CPU usage, 6-4 viewing database, 6-5, 8-12 viewing disk, 6-5, 6-13, 9-8, 9-9 viewing memory usage, 6-4 viewing process, 6-6, 7-16 viewing process number, 7-16 viewing service, 6-6, 7-17 service start, 7-20 viewing, 6-6, 7-17 viewing state, 7-18 setting accessible client, 4-6 max session for client, 4-4 NTP service, 2-20, 2-23 solaris user, 5-3, 5-8 solaris user, 5-3, 5-8 changing password dbuser, 5-10 omcuser, 5-11 root, 5-10 create, 5-13 delete, 5-14 start_svc, 14-3 starting NTP service, 2-21, 2-24 service, 7-20 static data backing up, 10-20
i-5
P
pack, 14-23 passwd, 14-35 peripherals check, 11-29 ping, 14-53 pkgadd, 14-24 pkgrm, 14-25 power supply check, 11-27 powering off E4900, 1-9 Netra240, 1-3 V890, 1-5 powering on E4900, 1-7 Netra240, 1-2 V890, 1-3 principle authorization for NE user, 5-7 authorization for NM user, 5-6 process viewing, 6-6, 7-16 viewing number, 7-16 prstat, 14-52 ps, 14-41 pwd, 14-8
Q
querying authorization, 5-37
R
recording screen I/O activity, 14-47 renaming file, 14-13 restoratin scenarios, 10-2, 10-6, 10-7 restoring dynamic data, 10-17 static data, 10-22 system data, 10-32 rm, 14-13 rmdir, 14-9 route adding, 3-5 deleting, 3-5 setting, 3-4
Issue 05 (2008-05-20)
Index
restoring, 10-22 stop_svc, 14-4 stopping NTP service, 2-18 svc_adm -cmd reload, 14-5 svc_adm -cmd status, 14-5 svc_adm -cmd status -sysagent all, 14-6 svc_profile.sh script, 14-2 svc_ps, 14-5 svc_stacks, 14-6 switching among folder, 14-8 sybase user, 5-5, 5-14 sybase user, 5-5, 5-14 changing password sa, 5-15 synchronization scheme mode, 2-6 purpose, 2-2 synchronize client and server time, 2-32, 4-8 system data backing up, 10-29 restoring, 10-32 system monitor browser, 6-2
server log, 6-8 service state, 7-18 solaris log, 6-10 viewing active process status, 14-41 viewing begging, 14-28 viewing command location, 14-44 viewing content of file, 14-26 viewing current working folder, 14-8 viewing date and time, 14-48 viewing disk space each file used, 14-39 viewing end, 14-29 viewing file on one screen, 14-27 viewing free disk space, 14-38 viewing host IP address, 14-46 viewing of setting hostname, 14-45 viewing online user information, 14-57 viewing operating system information, 14-45 viewing specific command path, 14-44
W
whereis, 14-44 which, 14-44 who, 14-43
T
tail, 14-29 tar, 14-19 telnet, 14-54 terminating process, 14-42 testing physical network connection, 14-53 time synchronization, 2-2 transferring file through network connection, 14-55 troubleshooting procedure, 13-2
U
uname, 14-45 uncompress, 14-23 unlocking user, 5-45 unpack, 14-24 useradd, 14-33 userdel, 14-34 usermod, 14-34
V
V890 changing SC IP address, 3-11 powering off, 1-5 powering on, 1-3 vi, 14-30 vi editor, 14-30 viewing CPU usage of server, 6-4 memory usage of server, 6-4
i-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 05 (2008-05-20)

00366168-M2000 Administrator Guide (S10) (V200R006 - 05)

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

00366168-M2000 Administrator Guide (S10) (V200R006 - 05)

Transféré par

Droits d'auteur :

Formats disponibles

M2000 V200R006

Administrator Guide (S10)

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

2 Setting the M2000 Time............................................................................................................2-1

M2000 Administrator Guide (S10)

4 Managing the M2000 Clients...................................................................................................4-1

5 Managing the M2000 Users......................................................................................................5-1

M2000 Administrator Guide (S10)

6 Monitoring the M2000...............................................................................................................6-1

7 Managing M2000 Processes and Services..............................................................................7-1

M2000 Administrator Guide (S10)

8 Managing the M2000 Databases..............................................................................................8-1

9 Managing the M2000 Files and Disks ...................................................................................9-1

10 Backing Up and Restoring the M2000................................................................................10-1

M2000 Administrator Guide (S10)

11 M2000 Routine Maintenance...............................................................................................11-1

12 M2000 Emergency Maintenance..........................................................................................12-1

13 Troubleshooting the M2000.................................................................................................13-1

14 M2000 Command Reference................................................................................................14-1

15 FAQ About the M2000...........................................................................................................15-1

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

About This Document

About This Document

Update History 05 (2008-05-20)

About This Document

M2000 Administrator Guide (S10)

sumdata_agent process sumreport_agent process 3gpp_agent process mml_agent process

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

About This Document

About This Document

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

About This Document

About This Document

M2000 Administrator Guide (S10)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

M2000 Administrator Guide (S10)

1 Powering On/Off the M2000

Powering On/Off the M2000

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1 Powering On/Off the M2000

M2000 Administrator Guide (S10)

1.1 Powering On/Off the M2000 (Netra240)

1.1.1 Powering On the M2000 (Netra240)

Set the power switch of the cabinet to ON.

M2000 Administrator Guide (S10)

1 Powering On/Off the M2000