M2000 Administrator Guide (Sun, S10) (V200R009 - 10)

M2000 V200R009
Administrator Guide (Sun, S10)

Issue Date 10 2010-09-06
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. 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 trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. 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 all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
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:
Issue 10 (2010-09-06)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
M2000 Administrator Guide (Sun, S10)
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 V200R009
Intended Audience
The intended audiences of this document are network administrators.
Revision History 10 (2010-09-06)

Formal release for the tenth time. Compared with 09 (2010-07-30), the following content is modified.
Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
Content 14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays 14.1.20 How Should I Uninstall the OceanStor Monitoring Software
Description New added.
New added.
09 (2010-07-30)
Formal release for the ninth time. Compared with 08 (2010-06-15), the following content is modified. Content 7.2.3 Starting the M2000 System Services 7.2.4 Stopping the M2000 Services 8.4 Backing Up M2000 Databases 10.2.4 Periodically Backing Up the M2000 Dynamic Data 10.2.6 Restoring the M2000 Dynamic Data 11.3.10 Backing Up the M2000 Description The content descriptions are changed. The content descriptions are changed. The content descriptions are changed. The content descriptions are changed. The content descriptions are changed. The content descriptions are changed.
08 (2010-06-15)
Formal release for the eighth time. Compared with 07 (2010-03-30), the following content is modified. Content 2.5.8 Setting the NTP Service on the M2000 Client 5.2.5 Changing the Password of User ftpuser 5.3.2 Changing the Password of User sa 7.1.61 son_agent Process 7.1.62 swm_agent Process
iv
Description The content descriptions are changed. The content descriptions are changed. The content descriptions are changed. The content descriptions are changed. The content descriptions are changed.
Issue 10 (2010-09-06)
About This Document
Content 10.2.6 Restoring the M2000 Dynamic Data
Description The content descriptions are changed.
07 (2010-03-30)
Formal release for the seventh time. Compared with 06 (2010-01-20), the following content is modified. Content 3.2.3 Changing the IP Address of Ethernet Port nxge3 on the M2000 Server 14.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)? 14.1.21 How Should I Check the Running Status of the FTP Service on the M2000 Server? 14.1.22 How Should I Start the FTP Service on the M2000 Server? 14.1.23 How Should I Check the Running Status of the SFTP Service on the M2000 Server? 14.1.24 How Should I Start the SFTP Service on the M2000 Server? 14.4.10 How Should I Handle an Incremental Backup Failure? Description The content descriptions are changed. The content descriptions are changed.
New added.
New added. New added.
New added. New added.
06 (2010-01-20)
Sixth commercial release. Compared with V200R009 05 issued on December 10 of 2009, this version has the following modifications: The content descriptions are optimized in 3 Setting the Host Name and IP Address for the M2000 Server.
Issue 10 (2010-09-06)
About This Document
05 (2009-12-10)
Fifth commercial release. Compared with V200R009 04 issued on October 31 of 2009, this version has the following modifications: The content descriptions are optimized in 1 Powering the M2000 On or Off.
04 (2009-10-31)
Fourth commercial release. Compared with V200R009 03 issued on September 20 of 2009, this version has the following modifications: The content descriptions are optimized in 1 Powering the M2000 On or Off.
03 (2009-09-20)
Third commercial release. Compared with V200R009 02 issued on July 25 of 2009, this version has the following modifications: The content descriptions are optimized in 7.1 Introduction to M2000 Processes and Services.
02 (2009-07-25)
Second commercial release. Compared with V200R009 01 issued on June 30 of 2009, this version has the following modifications: The content descriptions are optimized in 7.1 Introduction to M2000 Processes and Services.
01 (2009-06-30)
Initial release. Also, the first formal release.
Organization
1 Powering the M2000 On or Off This chapter describes how to power on and power off the M2000 server.
vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
About This Document
2 Setting the M2000 Time This chapter 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 chapter 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 chapter 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 Managing OSS System The M2000 provides the OSS management function. By using this function, you can viewing NE partitioning, managing the M2000 license, monitoring the M2000 server, integrated task management, check OMC status, collecting NM log files. 7 Managing M2000 Processes and Services This chapter 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 chapter 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. Specific maintenance items are required in real applications. 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 FAQs (Sun)
Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
About This Document
This chapter describes FAQs and solutions related to the M2000.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which 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, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New 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. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic
viii
Description The keywords of a command line are in boldface. Command arguments are in italics.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
About This Document
Convention [] { x | y | ... } [ x | y | ... ] { x | y | ... }*
Description Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. 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.
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 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.
Mouse Operations The mouse operations that may be found in this document are defined as follows.
Issue 10 (2010-09-06)
ix
About This Document
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 10 (2010-09-06)
Contents
Contents
About This Document...................................................................................................................iii 1 Powering the M2000 On or Off...............................................................................................1-1
1.1 Powering the M2000 On or Off (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 the M2000 On or Off (V890)..........................................................................................................1-4 1.2.1 Powering On the M2000 (V890)............................................................................................................1-4 1.2.2 Powering Off the M2000 (V890)...........................................................................................................1-6 1.3 Powering the M2000 On or Off (E4900)........................................................................................................1-8 1.3.1 Powering On the M2000 (E4900)..........................................................................................................1-8 1.3.2 Powering Off the M2000 (E4900).......................................................................................................1-12 1.4 Powering the M2000 On or Off (T5220)......................................................................................................1-14 1.4.1 Powering On the M2000 (T5220)........................................................................................................1-15 1.4.2 Powering Off the M2000 (T5220).......................................................................................................1-16 1.5 Powering the M2000 On or Off (M4000/M5000)........................................................................................1-16 1.5.1 Powering On the M2000 (M4000/M5000)..........................................................................................1-16 1.5.2 Powering Off the M2000 (M4000/M5000)..........................................................................................1-20
2 Setting the M2000 Time............................................................................................................2-1

2.1 Time Management for the Huawei Mobile Network......................................................................................2-2 2.1.1 Introduction to Time Synchronization................................................................................................... 2-2 2.1.2 Introduction to the NTP/SNTP...............................................................................................................2-3 2.1.3 Time Synchronization Modes of Huawei Mobile Network...................................................................2-6 2.1.4 Introduction to the DST........................................................................................................................2-12 2.2 Modifying the Date and Time on the M2000 Server....................................................................................2-12 2.3 Changing the Time Zone of the M2000 Server Without Using DST...........................................................2-14 2.4 Modifying the Date, Time, and Time Zone on the M2000 Client................................................................2-15 2.5 Configuring the NTP Service of the M2000.................................................................................................2-16 2.5.1 Checking the Time Settings of the M2000 Server...............................................................................2-17 2.5.2 Setting the M2000 Administration Console as the Secondary NTP Server.........................................2-17 2.5.3 Starting the NTP Service on the M2000 Administration Console.......................................................2-19 2.5.4 Checking the Running Status of the NTP Service on the M2000 Administration Console.................2-19 2.5.5 Setting the M2000 Server as the NTP Client.......................................................................................2-20 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
M2000 Administrator Guide (Sun, S10) 2.5.6 Starting the NTP Service on the M2000 Server...................................................................................2-21 2.5.7 Checking the Running Status of the NTP Service on the M2000 Server............................................2-22 2.5.8 Setting the NTP Service on the M2000 Client.....................................................................................2-23
2.6 Setting DST for the M2000...........................................................................................................................2-25
3 Setting the Host Name and IP Address for the M2000 Server..........................................3-1
3.1 Changing the Host Name of the M2000 Server..............................................................................................3-2 3.2 Modifying the IP Address of the M2000 Server.............................................................................................3-5 3.2.1 Adding or Deleting Routes on the M2000 Server..................................................................................3-5 3.2.2 Changing the IP Address of the M2000 Server......................................................................................3-6 3.2.3 Changing the IP Address of Ethernet Port nxge3 on the M2000 Server..............................................3-14 3.3 Modifying the IP Address of the SC or RSC or XSCF on the M2000 Server..............................................3-15 3.3.1 Modifying the IP Address of the SC on the Netra 240 Server.............................................................3-16 3.3.2 Changing the IP Address of the RSC on the V890 Server...................................................................3-17 3.3.3 Modifying the IP Address of the SC on the E4900 Server..................................................................3-17 3.3.4 Modifying the IP Address of the SC on the T5220 Server..................................................................3-20 3.3.5 Changing the IP Address of the XSCF on the M4000/M5000 Server.................................................3-20 3.4 Modifying the IP Address of the Disk Array................................................................................................3-23 3.4.1 Modifying the IP Address of the 3320 Disk Array..............................................................................3-23 3.4.2 Changing the IP Address of the S3200 Series Disk Array (Serial Port Mode)....................................3-24 3.4.3 Changing the IP Address of the S2600 Disk Array (Serial Port Mode)..............................................3-27 3.4.4 Changing the IP Address of the 6140 Disk Array (Serial Port Mode).................................................3-31
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 Monitoring the Login Status of the M2000 Clients........................................................................................4-5 4.3 Setting the Number of Clients Accessible on a PC.........................................................................................4-5 4.4 Setting the Time Information on the M2000 Client........................................................................................4-6 4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client.........................................................4-7 4.4.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-2 5.1.1 Introduction to Solaris Users..................................................................................................................5-2 5.1.2 Introduction to Sybase Users..................................................................................................................5-4 5.1.3 NE Users................................................................................................................................................5-4 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-7 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-11 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
Contents
5.2.4 Changing the Password of User omcuser.............................................................................................5-11 5.2.5 Changing the Password of User ftpuser...............................................................................................5-12 5.2.6 Creating a Solaris User.........................................................................................................................5-14 5.2.7 Deleting a Solaris User.........................................................................................................................5-14 5.3 Managing Sybase Users................................................................................................................................5-15 5.3.1 Introduction to Sybase Users................................................................................................................5-15 5.3.2 Changing the Password of User sa.......................................................................................................5-15 5.3.3 Changing the Name of the Database Server.........................................................................................5-17 5.4 Managing OM Users.....................................................................................................................................5-19
6 Managing OSS System..............................................................................................................6-1

6.1 Monitoring the M2000 Server.........................................................................................................................6-3 6.1.1 Refreshing the Monitoring Information.................................................................................................6-4 6.1.2 Checking the CPU and Memory Usage Information About the M2000 Server....................................6-4 6.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client..............6-5 6.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000 Client .........................................................................................................................................................................6-6 6.1.5 Checking the M2000 Services................................................................................................................6-7 6.1.6 Checking the Status of the M2000 Processes.........................................................................................6-8 6.1.7 Viewing the Information about M2000 Server Components.................................................................6-9 6.1.8 Saving the Monitoring Information......................................................................................................6-10 6.1.9 Setting Alarm Thresholds for the M2000............................................................................................6-10 6.2 Querying the System Logs of the M2000.....................................................................................................6-18 6.3 Collecting NM Log Files...............................................................................................................................6-19 6.4 Querying NE Subareas..................................................................................................................................6-21 6.5 Managing the M2000 License.......................................................................................................................6-21 6.5.1 Querying the M2000 License...............................................................................................................6-22 6.5.2 Updating the M2000 License...............................................................................................................6-22 6.6 Check OMC status........................................................................................................................................6-22 6.7 Integrated Task Management........................................................................................................................6-23 6.7.1 Basic Knowledge..................................................................................................................................6-24 6.7.2 Customizing the Interface for Managing Timing Tasks......................................................................6-36 6.7.3 Creating a User Timing Task...............................................................................................................6-37 6.7.4 Modifying a Timing Task....................................................................................................................6-38 6.7.5 Managing Timing Tasks.......................................................................................................................6-39 6.7.6 Browsing the Information of Timing Tasks.........................................................................................6-42 6.7.7 Viewing the Task Execution................................................................................................................6-42 6.7.8 Downloading Result Files....................................................................................................................6-43 6.7.9 Technical Specifications of Centralized Task Management................................................................6-46 6.8 Reference of the OSS Management GUI......................................................................................................6-47 6.8.1 Interface Description: Managing Timing Tasks...................................................................................6-49 6.8.2 Interface Description: M2000 Log Information Collector...................................................................6-51 6.8.3 Parameters for the NE Partitioning Information..................................................................................6-51 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
M2000 Administrator Guide (Sun, S10) 6.8.4 Parameters for Querying the M2000 License ......................................................................................6-52 6.8.5 Parameters for Setting Monitoring Parameters of the M2000 Server..................................................6-53 6.8.6 Parameters for Monitoring the M2000 Server Service Status..............................................................6-59 6.8.7 Parameters for Monitoring the M2000 Server Process Status............................................................. 6-60 6.8.8 Parameters for Monitoring the M2000 Server Hard Disk Status.........................................................6-60 6.8.9 Parameters for Monitoring the M2000 Server Database Status...........................................................6-61 6.8.10 Parameters for Setting Task Filter Conditions...................................................................................6-62 6.8.11 Parameters for Setting the Common Information About Timing Tasks............................................6-64 6.8.12 Parameters for Modifying Database Capacity....................................................................................6-65 6.8.13 Parameters for Modifying File interface Task................................................................................... 6-69 6.8.14 Parameters for Modifying Synchronization task................................................................................6-77 6.8.15 Parameters for Modifying NE Basic Information Export Task......................................................... 6-77 6.8.16 Parameters for Modifying Alarm Timing Acknowledgement...........................................................6-78 6.8.17 Parameters for Modifying Data Backup Task....................................................................................6-78 6.8.18 Parameters for Creating/Modifying/Copying MML Command Script..............................................6-80 6.8.19 Parameters for Creating/Modifying/Copying RAN Report Task...................................................... 6-82 6.8.20 Parameters for Creating, Viewing, or Modifying a Scheduled Report Task..................................... 6-82 6.8.21 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top Power..............6-86 6.8.22 Parameters for Creating/Modifying/Copying an RSSI Test Task......................................................6-87 6.8.23 Parameters for Creating/Modifying/Copying Software Download....................................................6-87 6.8.24 Parameters for Creating/Modifying/Copying Dual-Home Management...........................................6-88 6.8.25 Parameters for Creating/Modifying/Copying iSStar Script...............................................................6-88 6.8.26 Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log..................................6-89 6.8.27 Parameters for Creating/Modifying/Copying a CME Upload Task...................................................6-89 6.8.28 Parameters for Creating/Modifying/Copying Cell Parameters Compare Task..................................6-90 6.8.29 Parameters for Creating/Modifying/Copying Cell Consistency Check Task.................................... 6-91 6.8.30 Parameters for Creating/Modifying/Copying a CME Current Area Export Task..............................6-91 6.8.31 Parameters for Setting Time of Timing Tasks...................................................................................6-92 6.8.32 Parameters for Selecting Objects for Device Check..........................................................................6-93 6.8.33 Parameters for Collecting NM Logs Parameters................................................................................6-93
7 Managing M2000 Processes and Services..............................................................................7-1

7.1 Introduction to M2000 Processes and Services...............................................................................................7-2 7.1.1 3rdTool_agent Process...........................................................................................................................7-5 7.1.2 adn_agent Process..................................................................................................................................7-5 7.1.3 adss_agent Process.................................................................................................................................7-6 7.1.4 antenna_agent Process............................................................................................................................7-6 7.1.5 ce_agent Process....................................................................................................................................7-6 7.1.6 cmdc_agent Process...............................................................................................................................7-6 7.1.7 cmengine_agent Process........................................................................................................................7-6 7.1.8 cmeserver_agent Process........................................................................................................................7-7 7.1.9 cmexp_agent Process.............................................................................................................................7-7 7.1.10 cmserver_agent Process.......................................................................................................................7-7 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
Contents
7.1.11 cnnhc_agent Process............................................................................................................................7-8 7.1.12 corba_agent Process.............................................................................................................................7-8 7.1.13 cpm_agent Process...............................................................................................................................7-8 7.1.14 devdoc_agent Process..........................................................................................................................7-8 7.1.15 dsXXXX agent Process..........................................................................................................................7-8 7.1.16 eam_agent Process...............................................................................................................................7-9 7.1.17 fars_agent Process................................................................................................................................7-9 7.1.18 fmnotify_agent Process........................................................................................................................7-9 7.1.19 FMPreServiceXXXX_agent Process...................................................................................................7-10 7.1.20 fnlicense_agent Process......................................................................................................................7-10 7.1.21 glmssyn_agent Process.......................................................................................................................7-10 7.1.22 ifms_agent Process.............................................................................................................................7-10 7.1.23 ipqdt_agent Process............................................................................................................................7-11 7.1.24 ipm_agent Process..............................................................................................................................7-11 7.1.25 irp_agent Process................................................................................................................................7-11 7.1.26 itm_agent Process...............................................................................................................................7-12 7.1.27 lcsserver_agent Process......................................................................................................................7-12 7.1.28 lic_agent Process................................................................................................................................7-13 7.1.29 log_agent Process...............................................................................................................................7-13 7.1.30 lte_agent Process................................................................................................................................7-13 7.1.31 maintain_agent Process......................................................................................................................7-13 7.1.32 manager_agent Process......................................................................................................................7-13 7.1.33 medXXXX_agent Process...................................................................................................................7-14 7.1.34 nelicense_agent Process.....................................................................................................................7-14 7.1.35 neuser_agent Process..........................................................................................................................7-14 7.1.36 ngnffs_agent Process..........................................................................................................................7-15 7.1.37 ngnnis_agent Process.........................................................................................................................7-15 7.1.38 ngnni112_agent Process.....................................................................................................................7-15 7.1.39 ngntestmanage_agent Process............................................................................................................7-15 7.1.40 nhcservice_agent Process...................................................................................................................7-15 7.1.41 nicservice_agent Process....................................................................................................................7-15 7.1.42 nimserver_agent Process....................................................................................................................7-16 7.1.43 nms_mml_agent Process....................................................................................................................7-16 7.1.44 partition_agent Process......................................................................................................................7-16 7.1.45 pm_agent Process...............................................................................................................................7-16 7.1.46 pmexp_agent Process.........................................................................................................................7-17 7.1.47 pmmon_agent Process........................................................................................................................7-17 7.1.48 pmncdXX01_agent Process................................................................................................................7-17 7.1.49 porttrunk_agent Process.....................................................................................................................7-17 7.1.50 proxy_agent Process...........................................................................................................................7-18 7.1.51 PRSAssistantService_agent Process..................................................................................................7-18 7.1.52 prsdc_agent Process...........................................................................................................................7-18 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
M2000 Administrator Guide (Sun, S10) 7.1.53 prsfs_agent Process............................................................................................................................7-18 7.1.54 prsreport_agent Process......................................................................................................................7-19 7.1.55 prssum_agent Process........................................................................................................................ 7-19 7.1.56 rn_agent Process.................................................................................................................................7-19 7.1.57 ScriptModuleService_agent Process..................................................................................................7-19 7.1.58 scriptserver_agent Process................................................................................................................. 7-19 7.1.59 sm_agent Process............................................................................................................................... 7-20 7.1.60 snmp_agent Process........................................................................................................................... 7-20 7.1.61 son_agent Process.............................................................................................................................. 7-20 7.1.62 swm_agent Process............................................................................................................................ 7-20 7.1.63 threshold_agent Process.....................................................................................................................7-21 7.1.64 uap_agent Process..............................................................................................................................7-21 7.1.65 udpdispatch_agent Process.................................................................................................................7-21 7.1.66 umgupdsvr_agent Process..................................................................................................................7-21 7.1.67 xftpXX01_agent Process.....................................................................................................................7-21 7.1.68 Processes and Services Related to Each Northbound Interface.........................................................7-22 7.1.69 Checking the Status of the M2000 Processes.....................................................................................7-23
7.2 Managing M2000 Services............................................................................................................................7-24 7.2.1 Checking the M2000 Services..............................................................................................................7-24 7.2.2 Viewing the States of M2000 Services................................................................................................7-25 7.2.3 Starting the M2000 System Services................................................................................................... 7-26 7.2.4 Stopping the M2000 Services.............................................................................................................. 7-27
8 Managing the M2000 Databases..............................................................................................8-1

8.1 M2000 Database..............................................................................................................................................8-2 8.1.1 farsdb Database......................................................................................................................................8-3 8.1.2 fmdb Database........................................................................................................................................8-4 8.1.3 itfndb Database.......................................................................................................................................8-4 8.1.4 omcdb Database.....................................................................................................................................8-5 8.1.5 omceamdb Database...............................................................................................................................8-6 8.1.6 omclogdb Database................................................................................................................................8-7 8.1.7 omcsmdb Database.................................................................................................................................8-8 8.1.8 omctempdb Database.............................................................................................................................8-9 8.1.9 omctmdb Database.................................................................................................................................8-9 8.1.10 pmcomdb Database............................................................................................................................8-10 8.1.11 pmdb Database...................................................................................................................................8-12 8.1.12 sumdb Database..................................................................................................................................8-13 8.1.13 swmdb Database.................................................................................................................................8-17 8.2 Viewing the States of M2000 Databases ......................................................................................................8-17 8.2.1 Checking the Database Usage Information About the M2000 Server Through the M2000 Client .......................................................................................................................................................................8-18 8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands................................... 8-19 8.3 Clearing M2000 Databases........................................................................................................................... 8-20 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
Contents
8.4 Backing Up M2000 Databases......................................................................................................................8-22
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-4 9.2 Managing Files and Disks on the M2000 Server............................................................................................9-5 9.2.1 Introduction to the M2000 Server File System......................................................................................9-5 9.2.2 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client............9-13 9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands...........................................9-14 9.2.4 Clearing the Disk Space of the M2000 Server.....................................................................................9-15
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 Policies of M2000 Data Backup.........................................................................................................10-3 10.1.3 Scenarios of M2000 Data Restoration...............................................................................................10-4 10.2 Backing Up and Restoring M2000 Dynamic Data......................................................................................10-4 10.2.1 Setting the Storage Device of Backup Data Using Solaris Commands.............................................10-5 10.2.2 Setting the Storage Device of Backup Data Through the Client........................................................10-7 10.2.3 Setting the Wait Time for Replacing a Tape......................................................................................10-9 10.2.4 Periodically Backing Up the M2000 Dynamic Data........................................................................10-10 10.2.5 Manually Backing Up the M2000 Dynamic Data............................................................................10-14 10.2.6 Restoring the M2000 Dynamic Data................................................................................................10-16
11 M2000 Routine Maintenance...............................................................................................11-1

11.1 M2000 Routine Maintenance Items............................................................................................................11-2 11.2 Daily Maintenance Operations....................................................................................................................11-4 11.2.1 Checking the Status of Performance Measurement...........................................................................11-5 11.2.2 Checking the Missing Performance Result........................................................................................11-6 11.2.3 Checking the Alarm Reception..........................................................................................................11-6 11.2.4 Checking the NMS Connection..........................................................................................................11-7 11.2.5 Checking the Functionality of Alarm Box.........................................................................................11-7 11.2.6 Check OMC Alarms/Events...............................................................................................................11-7 11.2.7 Checking Connections Between the M2000 and NEs.....................................................................11-10 11.2.8 Checking M2000 Logs.....................................................................................................................11-11 11.2.9 Checking the Error Log of the Solaris.............................................................................................11-11 11.2.10 Checking the Disk Usage of the M2000 Server.............................................................................11-12 11.2.11 Checking the States of M2000 Databases......................................................................................11-13 11.2.12 Checking the States of M2000 Services.........................................................................................11-13 11.2.13 Checking the Core Files on the Server...........................................................................................11-14 11.2.14 Checking the Hardware of the M2000 Server................................................................................11-14 11.2.15 Checking the SMC Collection Results...........................................................................................11-15 11.3 Weekly Maintenance Operations..............................................................................................................11-15 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
M2000 Administrator Guide (Sun, S10) 11.3.1 Checking the Configuration of Alarm Timing.................................................................................11-16 11.3.2 Checking the Configuration of Automatic Log Dump.....................................................................11-17 11.3.3 Checking the Synchronization Time of NE Log..............................................................................11-18 11.3.4 Checking the Configuration of the File Server ...............................................................................11-18 11.3.5 Checking the Configuration of System Backup...............................................................................11-19 11.3.6 Checking the Configuration of System Monitoring.........................................................................11-20 11.3.7 Checking the Synchronization Time of NE Configuration..............................................................11-27 11.3.8 Checking the Threshold of Network Management Capability.........................................................11-28 11.3.9 Checking the Status of the M2000 Routes.......................................................................................11-28 11.3.10 Backing Up the M2000 .................................................................................................................11-28 11.3.11 Checking the Time of the M2000 Server.......................................................................................11-31 11.3.12 Checking the States of M2000 Disks.............................................................................................11-31
11.4 Monthly Maintenance Operations.............................................................................................................11-32 11.4.1 Checking the Power Supply of the M2000 Server...........................................................................11-33 11.4.2 Checking the Peripherals of the M2000 Server...............................................................................11-33 11.4.3 Checking the Front Panel of a Disk Array.......................................................................................11-34 11.4.4 Querying the M2000 License...........................................................................................................11-34
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 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 Sybase Version Information.............................................................................................13-5 13.2.6 Collecting the M2000 Version...........................................................................................................13-6 13.3 Collecting Fault Data Using the Log Information Collector.......................................................................13-6
14 FAQs (Sun)..............................................................................................................................14-1
14.1 About Solaris...............................................................................................................................................14-2 14.1.1 How Do I Log In to the M2000 Server as User root Through Telnet?..............................................14-3 14.1.2 How to Log In the M2000 Server as the root User Through FTP.....................................................14-4 14.1.3 How to Check the Status of the Tape Drive.......................................................................................14-4 14.1.4 How Do I Select the Tape Drive?......................................................................................................14-5 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
Contents
14.1.5 What are the files in the etc/rc2.d Folder of Solaris...........................................................................14-6 14.1.6 How to View the Hardware Settings of the M2000 Server................................................................14-7 14.1.7 How to Check the Device Status of the M2000 Server......................................................................14-8 14.1.8 Why Unable to Enter the Domain Console of Fire E4900...............................................................14-11 14.1.9 How to Modify the Port Number of the FTP Server?......................................................................14-12 14.1.10 How to Query the Time Zone Name..............................................................................................14-12 14.1.11 How Do I Stop the NTP Service on the M2000 Server.................................................................14-14 14.1.12 How Do I Change the IP Address of the S3200 Disk Array (Command Mode)...........................14-15 14.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)?.........................14-17 14.1.14 How Do I Change the IP Address of the 6140 Disk Array (Command Mode).............................14-19 14.1.15 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROM?.................................14-24 14.1.16 How to Handle the corrupt label - wrong magic number Message?..........................................14-25 14.1.17 What Should I Do When the Server Disk Space Is Insufficient?...................................................14-25 14.1.18 How to Configuring the Monitoring Function of the S2600 Disk Array.......................................14-27 14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays..................14-29 14.1.20 How Should I Uninstall the OceanStor Monitoring Software.......................................................14-32 14.1.21 How Should I Check the Running Status of the FTP Service on the M2000 Server?...................14-33 14.1.22 How Should I Start the FTP Service on the M2000 Server?.........................................................14-34 14.1.23 How Should I Check the Running Status of the SFTP Service on the M2000 Server?.................14-34 14.1.24 How Should I Start the SFTP Service on the M2000 Server?.......................................................14-35 14.2 About Sybase.............................................................................................................................................14-35 14.2.1 How Do I Check Whether the Sybase Is Started?............................................................................14-36 14.2.2 How to Start the Sybase...................................................................................................................14-37 14.2.3 How Do I Stop the Sybase?..............................................................................................................14-38 14.2.4 How to View the Name of the Sybase Server..................................................................................14-38 14.2.5 How to Handle Database Alarms.....................................................................................................14-39 14.2.6 How to View Database Deadlock Information................................................................................14-40 14.2.7 Why the Sybase Is Not Started After the Server Restarted..............................................................14-41 14.2.8 Why the Sybase Is Not Started After Run svc_profile.sh................................................................14-42 14.2.9 Why the Sybase Backup Database Abort.........................................................................................14-43 14.2.10 Why the Mouse Pointer Changes into an Hourglass upon History Alarm Query..........................14-43 14.2.11 What Should I Do When the Database Cannot Be Started Properly?............................................14-44 14.2.12 What Should I Do When the Client Is Disconnected Due to Damaged System Tables in the Database? .....................................................................................................................................................................14-45 14.2.13 What Should I Do When the Number of Database Connections Is Insufficient?..........................14-47 14.2.14 How to Handle the '/export/home/sybdev/master.dat' already in use Message?......................14-49 14.2.15 What Should I Do to Handle Database Startup Failure Due to Incorrect User Type?...................14-49 14.3 About TCP/IP Network.............................................................................................................................14-50 14.3.1 Why the Network Port Is Abnormal................................................................................................14-50 14.3.2 How to Connect the Client to the Server with More than One IP Address......................................14-51 14.4 About Server Software..............................................................................................................................14-52 14.4.1 Why M2000 Services Restart Abnormally......................................................................................14-53 14.4.2 Why M2000 Services Stop Abnormally..........................................................................................14-54 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
M2000 Administrator Guide (Sun, S10) 14.4.3 What Should I Do When I Fail to Start the M2000 Services?.........................................................14-54 14.4.4 What Should I Do When I Fail to Stop the M2000 Services?.........................................................14-55 14.4.5 Why M2000 Dynamic Data Backup Fails.......................................................................................14-56 14.4.6 How to Set the M2000 Administration Console as the Intermediary-Layer NTP Server (In Encryption Mode)..........................................................................................................................................................14-58 14.4.7 How Do I Check the Running Status of the NTP Services on the Administration Console (In Encryption Mode)?........................................................................................................................................................14-60 14.4.8 How to Set the M2000 Server as the NTP Client (In Encryption Mode)........................................14-61 14.4.9 How Should I Check the Running Status of the NTP Services on the M2000 Server (In Encryption Mode)?........................................................................................................................................................14-64 14.4.10 How Should I Handle an Incremental Backup Failure?.................................................................14-65 14.4.11 How Should I Periodically Monitoring the CPU, Memory, and Disk...........................................14-66 14.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SC.............................14-67
xx
Issue 10 (2010-09-06)
Figures
Figures
Figure 1-1 Netra 240 server..................................................................................................................................1-3 Figure 1-2 6140 disk array...................................................................................................................................1-5 Figure 1-3 V890 server.........................................................................................................................................1-5 Figure 1-4 6140 disk array (I)..............................................................................................................................1-7 Figure 1-5 6140 disk array (II).............................................................................................................................1-7 Figure 1-6 Netra 240 server..................................................................................................................................1-9 Figure 1-7 6140 disk array................................................................................................................................. 1-10 Figure 1-8 E4900 server.....................................................................................................................................1-11 Figure 1-9 6140 disk array (I)............................................................................................................................ 1-13 Figure 1-10 6140 disk array (II).........................................................................................................................1-14 Figure 1-11 T5220 server...................................................................................................................................1-15 Figure 1-12 S2600 disk array.............................................................................................................................1-17 Figure 1-13 S3200 disk array.............................................................................................................................1-18 Figure 1-14 The front operation panel of SPARC Enterprise M4000/M5000...................................................1-19 Figure 1-15 Disk array (I).................................................................................................................................. 1-21 Figure 1-16 Disk array (II).................................................................................................................................1-21 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 3-1 Serial ports of the S3X00..................................................................................................................3-25 Figure 3-2 Serial ports provided by the S2600 disk array..................................................................................3-28 Figure 3-3 Successful connection interface........................................................................................................3-29 Figure 3-4 Successful login dialog box..............................................................................................................3-29 Figure 3-5 Serial ports of the 6140 disk array....................................................................................................3-31 Figure 6-1 Server Monitor tab page.....................................................................................................................6-5 Figure 6-2 Hard Disk Monitor tab page...............................................................................................................6-6 Figure 6-3 Database Monitor tab page.................................................................................................................6-7 Figure 6-4 Service Monitor tab page....................................................................................................................6-8 Figure 6-5 Process Monitor tab page...................................................................................................................6-9 Figure 6-6 System Monitor Settings dialog box................................................................................................ 6-11 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Figures
M2000 Administrator Guide (Sun, S10) Figure 6-7 State transition of a scheduled task...................................................................................................6-35 Figure 6-8 Timing Task Management interface.................................................................................................6-50
Figure 6-9 M2000 Log Information Collector interface....................................................................................6-51 Figure 7-1 Process Monitor tab page.................................................................................................................7-24 Figure 7-2 Service Monitor tab page..................................................................................................................7-25 Figure 8-1 Database Monitor tab page...............................................................................................................8-18 Figure 8-2 Periodic backup................................................................................................................................8-23 Figure 8-3 Periodic backup................................................................................................................................8-24 Figure 9-1 Hard Disk Monitor tab page.............................................................................................................9-14 Figure 10-1 Setting the storage device (I)..........................................................................................................10-8 Figure 10-2 Setting the storage device (II).........................................................................................................10-9 Figure 10-3 Periodic backup............................................................................................................................10-12 Figure 10-4 Periodic backup............................................................................................................................10-13 Figure 10-5 Manual backup.............................................................................................................................10-15 Figure 11-1 Periodic backup............................................................................................................................11-29 Figure 11-2 Periodic backup............................................................................................................................11-30 Figure 13-1 Log Information Collector dialog box............................................................................................13-7 Figure 14-1 SNMP tab page............................................................................................................................14-31
xxii
Issue 10 (2010-09-06)
Tables
Tables
Table 3-1 Adding or deleting a route....................................................................................................................3-6 Table 3-2 Parameters for the standby controller.................................................................................................3-18 Table 3-3 Parameters for the standby controller.................................................................................................3-19 Table 3-4 Setting properties of the serial port....................................................................................................3-26 Table 3-5 Setting the properties of a serial port.................................................................................................3-28 Table 3-6 Setting properties of the serial port....................................................................................................3-32 Table 4-1 M2000 client software directory..........................................................................................................4-2 Table 5-1 Solaris user accounts............................................................................................................................5-3 Table 5-2 Privileges of M2000 users....................................................................................................................5-6 Table 5-3 Solaris user accounts............................................................................................................................5-9 Table 6-1 Server Monitor...................................................................................................................................6-12 Table 6-2 Hard Disk Monitor.............................................................................................................................6-13 Table 6-3 Database Monitor...............................................................................................................................6-16 Table 6-4 Service Monitor..................................................................................................................................6-17 Table 6-5 Tasks grouped according to execution periods..................................................................................6-25 Table 6-6 Tasks grouped according to functions................................................................................................6-25 Table 6-7 Tasks grouped according to task features..........................................................................................6-29 Table 6-8 Description of system timing tasks....................................................................................................6-29 Table 6-9 Description of user timing tasks.........................................................................................................6-32 Table 6-10 Description of the task description parameters................................................................................6-34 Table 6-11 Allowable operations for different task types..................................................................................6-43 Table 6-12 Description of the Timing Task Management interface...................................................................6-50 Table 6-13 Server Monitor.................................................................................................................................6-53 Table 6-14 Hard Disk Monitor...........................................................................................................................6-54 Table 6-15 Database Monitor.............................................................................................................................6-57 Table 6-16 Service Monitor................................................................................................................................6-58 Table 6-17 Common Parameters........................................................................................................................6-64 Table 6-18 Parameters of alarm database capacity management tasks..............................................................6-65 Table 6-19 Parameters of performance database capacity management tasks...................................................6-66 Table 6-20 Parameters of NE log database capacity management tasks............................................................6-68 Table 6-21 Parameters of M2000 log database capacity management tasks......................................................6-68 Table 6-22 Parameters for Modifying an Alarm Data Export Task...................................................................6-70 Table 6-23 Parameters for Modifying the Export of Performance Data............................................................6-72 Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Tables
M2000 Administrator Guide (Sun, S10) Table 6-24 Parameters for Modifying the Export of Inventory Data.................................................................6-74 Table 6-25 Parameters for Modifying the Export of NE Logs...........................................................................6-74 Table 6-26 Parameters for Modifying the Export of M2000 Logs.....................................................................6-75 Table 6-27 Extension parameters of Configuration Data Export tasks..........................................................6-76 Table 6-28 Parameters for Modifying the Synchronization of NE Configuration Data.....................................6-77 Table 6-29 Parameters for Modifying the Synchronization of Inventory Data..................................................6-77 Table 6-30 Parameters for Modifying Data Backup in the M2000....................................................................6-79 Table 6-31 Parameters for Creating/Modifying/Copying NE Backup...............................................................6-79 Table 6-32 Predefined Macros...........................................................................................................................6-84 Table 6-33 Description of extended parameters.................................................................................................6-89 Table 6-34 Descriptions of parameters for setting timing task time..................................................................6-92 Table 7-1 Relations between northbound interfaces and their corresponding processes and services..............7-22 Table 8-1 Tables of the farsdb database and the corresponding functions...........................................................8-3 Table 8-2 Tables of the fmdb database and the corresponding functions............................................................8-4 Table 8-3 Tables of the itfndb database and the corresponding functions...........................................................8-4 Table 8-4 Names and functions of tables in the omcdb database.........................................................................8-5 Table 8-5 Name and function of each table in the omceamdb database..............................................................8-7 Table 8-6 Names and functions of the tables in the omclogdb database..............................................................8-8 Table 8-7 Tables of the omcsmdb database and the corresponding functions.....................................................8-8 Table 8-8 Name and function of each table in the omctempdb database.............................................................8-9 Table 8-9 Names and functions of the tables in the omctmdb database...............................................................8-9 Table 8-10 Counter information tables in the pmcomdb database and the corresponding functions.................8-10 Table 8-11 Template information tables in the pmcomdb database and the corresponding functions..............8-11 Table 8-12 Function subsets and period tables in the pmcomdb database and their functions..........................8-12 Table 8-13 Template tables in the pmdb database and their functions...............................................................8-13 Table 8-14 Function subset tables and period tables in the pmdb database and the corresponding functions .............................................................................................................................................................................8-13 Table 8-15 Name and function of each object type information table in the sumdb database...........................8-13 Table 8-16 Name and function of each system setting information table in the sumdb database......................8-14 Table 8-17 Name and function of each report information table in the sumdb database...................................8-15 Table 8-18 Name and function of each performance result table in the sumdb database..................................8-16 Table 8-19 Tables of the swmdb database and the corresponding functions.....................................................8-17 Table 9-1 M2000 client software directory..........................................................................................................9-2 Table 9-2 Directories related to the M2000 server software................................................................................9-6 Table 9-3 Planning of the server disk partitions (Netra 240)...............................................................................9-8 Table 9-4 Planning for disk partitioning on the server (V890)............................................................................9-9 Table 9-5 Planning for the 6140 disk array........................................................................................................9-10 Table 9-6 Planning for disk partitioning on the server (E4900).........................................................................9-10 Table 9-7 Planning for the 6140 disk array........................................................................................................9-11 Table 9-8 Planning of the Sun T5220 server disk partitions..............................................................................9-11 Table 9-9 Partitioning of the local server disks (M4000/M5000)......................................................................9-12 Table 9-10 Disk partitions of the S3200 disk array............................................................................................9-13 Table 9-11 Disk partitions of the S2600 disk array............................................................................................9-13
xxiv
Issue 10 (2010-09-06)
Tables
Table 10-1 Introduction to dynamic data backup...............................................................................................10-2 Table 10-2 Values of backup media...................................................................................................................10-6 Table 11-1 List of maintenance items................................................................................................................11-2 Table 11-2 Alarms that need to be handled immediately...................................................................................11-8 Table 11-3 Alarms that need to be handled within one day...............................................................................11-8 Table 11-4 Alarms to be focused on during network expansion........................................................................11-9 Table 11-5 Alarms about malicious operations..................................................................................................11-9 Table 11-6 Events that need to be handled within one day................................................................................11-9 Table 11-7 Events that need to be focused on during network expansion.........................................................11-9 Table 11-8 Server Monitor...............................................................................................................................11-21 Table 11-9 Hard Disk Monitor.........................................................................................................................11-22 Table 11-10 Database Monitor.........................................................................................................................11-25 Table 11-11 Service Monitor............................................................................................................................11-26 Table 14-1 Tape drive status..............................................................................................................................14-5 Table 14-2 Checking the server configuration...................................................................................................14-7 Table 14-3 Commands for checking the device status.......................................................................................14-8 Table 14-4 Example of the matching table between countries and time zone names......................................14-13 Table 14-5 Setting the properties of the serial port..........................................................................................14-21
Issue 10 (2010-09-06)
xxv
1 Powering the M2000 On or Off
1
About This Chapter
Powering the M2000 On or Off
This chapter describes how to power on and power off the M2000 server. 1.1 Powering the M2000 On or Off (Netra240) This section describes how to power on and power off the M2000 when the Netra 240 minicomputer serves as the M2000 server. 1.2 Powering the M2000 On or Off (V890) This section describes how to power on and power off the M2000 when the V890 minicomputer serves as the M2000 server. 1.3 Powering the M2000 On or Off (E4900) This section describes how to power on and power off the M2000 when the E4900 minicomputer serves as the M2000 server. 1.4 Powering the M2000 On or Off (T5220) This section describes how to power on and power off the M2000 system by following a specific operation sequence to guarantee the system security. 1.5 Powering the M2000 On or Off (M4000/M5000) This section describes how to power on and power off the M2000 system by following a specific operation sequence to guarantee the system security.
Issue 10 (2010-09-06)
1-1
1.1 Powering the M2000 On or Off (Netra240)

This section describes how to power on and power off the M2000 when the Netra 240 minicomputer serves as the M2000 server. 1.1.1 Powering On the M2000 (Netra240) This section 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 section 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 section describes how to power on the M2000 when the Netra240 minicomputer serves as the M2000 server.
Prerequisite
The M2000 system is already shut down. For details, see1.1.2 Powering Off the M2000 (Netra 240).
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.
2. 1.
Set the power switch of the cabinet to ON. Turn the rotary switch beside the power supply to the normal position (I), as shown in Figure 1-1.
Step 2 Power on the Netra240 server.
1-2
Issue 10 (2010-09-06)
Figure 1-1 Netra 240 server
1 4
Power switch Normal position
2 5
Rotary switch Lock position
3 6
Forced turn-off Diagnosis position
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, 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 section 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 about how to stop the M2000, refer to 7.2.4 Stopping the M2000 Services. Step 2 If Sybase is running, stop it. # su - dbuser For details about how to stop the Sybase, refer to 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit 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
Issue 10 (2010-09-06) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
Step 4 If required, set the power switches of the cabinet and the other devices in the cabinet to OFF. ----End
1.2 Powering the M2000 On or Off (V890)

This section describes how to power on and power off the M2000 when the V890 minicomputer serves as the M2000 server. 1.2.1 Powering On the M2000 (V890) This section 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 section 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 section describes how to power on the M2000 when the V890 minicomputer serves as the M2000 server.
Prerequisite
The M2000 system is already shut down. For details, see1.2.2 Powering Off the M2000 (V890).
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.
NOTE
The devices to be checked include the M2000 server, disk array, networking devices, and cabinet.
2.
Set the power switch of the cabinet to ON.
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.
CAUTION
Each disk array has two power switches and their directions are opposite.
1-4
Issue 10 (2010-09-06)
Figure 1-2 6140 disk array
Off
On
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.
Figure 1-3 V890 server
1 4
2 5
3 6
2.
Issue 10 (2010-09-06)
Press down the power switch to start the V890 server.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-5

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 section 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 about how to stop the M2000, refer to 7.2.4 Stopping the M2000 Services. Step 2 If the Sybase is running, stop it. # su - dbuser For details about how to stop the Sybase, refer to 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 3 Switch to user root and power off the V890 server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 Step 4 Power off the 6140 disk array. 1. 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, it indicates that all the data is written into the disk and that the cache does not hold data. Figure 1-4 shows the 6140 disk array.
1-6
Issue 10 (2010-09-06)
Figure 1-4 6140 disk array (I)
Off
On
2.
Ensure that all the LEDs of all the disk drives at the front of controller stop blinking, as shown in Figure 1-5.
Figure 1-5 6140 disk array (II)
3.
Set the two power switches at the rear of the controller to OFF.
Issue 10 (2010-09-06)
1-7

NOTE
Step 5 If required, set the power switches of the cabinet and the other devices in the cabinet to OFF. ----End
1.3 Powering the M2000 On or Off (E4900)

This section describes how to power on and power off the M2000 when the E4900 minicomputer serves as the M2000 server. 1.3.1 Powering On the M2000 (E4900) This section describes how to power on the M2000 when the E4900 minicomputer serves as the M2000 server. 1.3.2 Powering Off the M2000 (E4900) This section describes how to power off the M2000 when the E4900 minicomputer serves as the M2000 server.
1.3.1 Powering On the M2000 (E4900)

This section describes how to power on the M2000 when the E4900 minicomputer serves as the M2000 server.
Prerequisite
The M2000 system is already shut down. For details, see1.3.2 Powering Off the M2000 (E4900).
Procedure
Step 1 Make the following preparations to power on the M2000: 1. Ensure that the power switch of each device in the cabinet is in the OFF state.
NOTE
The devices to be checked include the M2000 server, disk array, Netra 240 administration console, KVM, networking devices, and cabinet.
2. 1.
Set the power switch of the cabinet to ON. Turn the rotary switch beside the power supply to the normal position (I), as shown in Figure 1-6.
Step 2 Start the administration console Netra 240.
1-8
Issue 10 (2010-09-06)
Figure 1-6 Netra 240 server
1 4
2 5
3 6
2.
Press down the On/Standby button on the power switch of the Netra 240 server to start the M2000 system.
l
If the Solaris operating system is not installed on the M2000 server, the M2000 system is switched to the ok state. If the Solaris operating system is installed on the M2000 server, the M2000 system automatically starts the Solaris operating system. If the M2000 system is switched to the ok state, enter boot to start the Solaris operating system.
3. 4.
Turn the rotary switch to the locked position. Turn on the power of KVM and that of all the network equipment. All the equipment starts automatically after the power is turned on.
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-7.
CAUTION
Issue 10 (2010-09-06)
1-9
Figure 1-7 6140 disk array
Off
On
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-8. Currently, only two SCs are powered on. The front indicators of the three power boards remain at steady blue.
1-10
Issue 10 (2010-09-06)
Figure 1-8 E4900 server
Off
On
NOTE
The SC of the E4900 server serves as the console.
2.
Run the telnet logical IP address of the SC of the E4900 server command to log in to the SC. Select 0 to open the Platform Shell interface. Run the following command to enable the failover function of the SC: sc> setfailover on
NOTE
If the SC of the E4900 server is not configured yet, configure the SC by seeing M2000 Software Initialization Installation Guide (Sun,S10).
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.
Issue 10 (2010-09-06)

l
If the enter to domain A fails because the system is busy, troubleshoot the fault by referring to 14.1.8 Why Unable to Enter the Domain Console of 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)

This section describes how to power off the M2000 when the E4900 minicomputer serves as the M2000 server.
Procedure
Step 1 Stop the M2000 if it is running. For details about how to stop the M2000, refer to 7.2.4 Stopping the M2000 Services. Step 2 Stop the Sybase if it is running. # su - dbuser For details about how to stop the Sybase, refer to 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit 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
1-12
Issue 10 (2010-09-06)
4.
Run the setkeyswitch -d a off command to close domain A. osssvr-sc0:SC> setkeyswitch -d a off
Powering boards off ...
NOTE
If some domain is on, run the corresponding command to close the domain.
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. 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, it indicates that all the data is written into the disk and that the cache does not hold data. Figure 1-9 shows the 6140 disk array. Figure 1-9 6140 disk array (I)
Off
On
2.
Ensure that all the LEDs of all the disk drives at the front of controller stop blinking, as shown in Figure 1-10.
Issue 10 (2010-09-06)
1-13
Figure 1-10 6140 disk array (II)
3.
NOTE
Step 5 Power off the Netra 240 console. 1. 2. Log in to the Netra 240 console as user root. Run the following commands to power off the Netra 240 console: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 Step 6 Set the power switch of the E4900 server to OFF. Set the power switches of the cabinet and other devices in the cabinet to OFF if required. ----End
1.4 Powering the M2000 On or Off (T5220)

This section describes how to power on and power off the M2000 system by following a specific operation sequence to guarantee the system security. 1.4.1 Powering On the M2000 (T5220) This section describes how to power on the M2000 system before starting the T5220 server when the M2000 is installed on the T5220 server. 1.4.2 Powering Off the M2000 (T5220)
1-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 10 (2010-09-06)
This section describes how to power off the M2000 by following a specific operation sequence when the M2000 system is installed on the T5220 server.
1.4.1 Powering On the M2000 (T5220)

This section describes how to power on the M2000 system before starting the T5220 server when the M2000 is installed on the T5220 server.
Prerequisite
l
The M2000 system is powered off. For details, see 1.4.2 Powering Off the M2000 (T5220). The PC terminal communicates with the server well.
Procedure
Step 1 Prepare for powering on the M2000. 1. Before powering on the M2000, shut down the power supply of all the devices.
NOTE
The devices to be checked are the M2000 server, all the network devices, and cabinet.
2.
Power on the cabinet.
Step 2 Start the T5220 server. Waiting for 3 minutes, press the power switch to power on the T5220 server when the LED indicator is lighted, as shown in Figure 1-11.
NOTE
You can also power on the T5220 server through the serial port of the SC. For details, see 14.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SC.
Figure 1-11 T5220 server
If the Solaris operating system is not installed, the system is switched to the ok state after the T5220 is started. If the Solaris, Sybase, and M2000 server software are correctly installed, the system automatically starts the Solaris, Sybase, and M2000 services after the T5220 is started. If the system is switched to the ok state, type boot to start the operating system. The system automatically starts the Sybase and the M2000.
----End
1.4.2 Powering Off the M2000 (T5220)

This section describes how to power off the M2000 by following a specific operation sequence when the M2000 system is installed on the T5220 server.
Prerequisite
You have logged in to the server as user root.
Procedure
Step 1 If the system is running the M2000 services, stop the services. For details, see 7.2.4 Stopping the M2000 Services. Step 2 If the system is running the Sybase service, stop the service. # su - dbuser Stop the Sybase service, see 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 3 Switch to user root and power off the T5220 server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5
NOTE
Shutting down the server takes a long time. Wait for 30 minutes before performing the subsequent operations.
Step 4 If required, shut down the power supply of the cabinet and the devices in the cabinet. ----End
1.5 Powering the M2000 On or Off (M4000/M5000)

This section describes how to power on and power off the M2000 system by following a specific operation sequence to guarantee the system security. 1.5.1 Powering On the M2000 (M4000/M5000) This section describes how to power on the M2000 system before starting the M4000/M5000 server when the M2000 is installed on the M4000/M5000 server. 1.5.2 Powering Off the M2000 (M4000/M5000) This section describes how to power off the M4000/M5000 server according to a specific operation sequence when the M2000 system is installed on the M4000/M5000 server.
1.5.1 Powering On the M2000 (M4000/M5000)

This section describes how to power on the M2000 system before starting the M4000/M5000 server when the M2000 is installed on the M4000/M5000 server.
Prerequisite
l l
The M2000 is stopped. For details, see 1.5.2 Powering Off the M2000 (M4000/M5000). The communication between the PC and the port 0 on the XSCF of the server is normal.
Context
l
For the M2000 single-server system using the M4000/M5000 server, configure the S3200 disk array, the 6140 disk array or the S2600 disk array for the system. The methods for starting the S3200 disk array or the 6140 disk array are the same. The S3200 disk array is taken as an example in the description of powering on the M2000 system.
Procedure
Step 1 Prepare for powering on the server. 1. Ensure that each device in the cabinet is switched off.
NOTE
The devices to be checked include the M2000 server, disk array, all the network devices, and cabinet.
2.
Power on the cabinet.
Step 2 Power on the disk array. Option S2600 disk array S3200 disk array or 6140 disk array Description Perform Step 2.1. Perform Step 2.2.
1.
Insert the two plugs at the rear of the disk array into the socket, as shown in Figure 1-12. When the hard disk LEDs of all the disk arrays stop blinking, the disk array are started successfully.
CAUTION
l l
Each disk array has two plugs. Ensure that both plugs are inserted into the socket. The S2600 disk array does not have a power switch. After you insert the plug into the socket, the S2600 disk array is automatically powered on.
Figure 1-12 S2600 disk array
Issue 10 (2010-09-06)
1-17
(Disk array with a controller)
(Hard disk frame of the disk array)
2.
Set the two power switches at the rear of the S3200 disk array to ON, as shown in Figure 1-13.
CAUTION
Figure 1-13 S3200 disk array
OFF
ON
Step 3 Power on the M2000 server. 1. Start the PuTTY on the PC and log in to the XSCF of the server through the telnet.
1-18
Issue 10 (2010-09-06)

NOTE
l l l l l
The XSCF of the M4000/M5000 server functions as the system console. Log in to the XSCF of the M4000/M5000 server through the IP address of port 0 on the XSCF. Log in to the http://support.huawei.com to download the PuTTY to the PC. For details about how to log in to the XSCF through the PuTTY, see M2000 Software Initialization Installation Guide (T5220&M4000&M5000, S10) If the XSCF of the M4000/M5000 server is not configured yet, configure the XSCF by referring to M2000 Software Initialization Installation Guide (T5220&M4000&M5000, S10).
2.
Log in to the XSCF as user adminuser. The recommended password of user adminuser is adminuser.
3.
On the front panel of the M2000 server, switch the key to the position for Maintenance, as shown in Figure 1-14. Figure 1-14 The front operation panel of SPARC Enterprise M4000/M5000
1 Power indicator 4 Power button 7 Mode switch
2 LED of available XSCF 5 Locked - -
3 LED of check status 6 Maintenance - -
4.
Run the following command to power on domain 0. XSCF> poweron -d 0

DomainIDs to power on: 00 Continue? [y|n] :y
The server automatically starts and performs self-check. This process lasts about 20 minutes. 5. Run the following command to switch to area 0: XSCF> console -d 0
When the system displays the following information, enter y to confirm the information.
Connect to DomainID 0? [y|n] :y l
If the Solaris operating system is not installed on the server, the server switches to the ok state.
6. 7.
If the Solaris, Sybase, and M2000 server software are correctly installed, the system automatically starts the Solaris, Sybase, and M2000 services. If the system switches to the ok state, type boot to start the operating system. Then, the system automatically starts the Sybase and the M2000. Ensure that the LED of available XSCF on the operation panel is in green. On the front panel of the M2000 server, switch the key to the position for Locked.
l
----End
1.5.2 Powering Off the M2000 (M4000/M5000)

This section describes how to power off the M4000/M5000 server according to a specific operation sequence when the M2000 system is installed on the M4000/M5000 server.
Prerequisite
l l
You have logged in to the M2000 server as user root. The communication between the PC and the server is normal.
Context
l l
For the M2000 single-server system using the M4000/M5000 server, configure the S3200 disk array, the 6140 disk array or the S2600 disk array for the system. The methods of starting the S3200 disk array or the 6140 disk array are the same, the S3200 disk array is taken as an example in the description of powering off the M2000 system.
Procedure
Step 1 If the M2000 services are running, stop them. For details about how to stop M2000 services, see 7.2.4 Stopping the M2000 Services. Step 2 If the Sybase service is running, stop it. # su - dbuser For details about how to stop the Sybase service, see 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 3 Power off the M2000 server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i5 Step 4 Power off the disk array. Option S2600 disk array S3200 disk array or 6140 disk array Description Perform Step 4.1 and Step 4.2. Perform Step 4.3 and Step 4.4.
1-20
Issue 10 (2010-09-06)
1.
Check whether the I/O activities of the disk arrays are stopped.
NOTE
a. Wait for two minutes. If the LED indicators of all the drives and caches stop blinking, it indicates that the read and write operations of the disk array are stopped. b. Check the cache LED on the controller and determine whether any data on the cache needs to be written to the disk. c. Ensure that the LEDs of all the drive and caches stop blinking.
2. 3.
Remove the two plugs at the rear of the disk array from the socket. Check whether the I/O activities of the disk arrays are stopped. a. Wait for two minutes. If all the LEDs stop blinking, it indicates that all the data is written into the disk and that the cache does not hold data. See Figure 1-15 .
Figure 1-15 Disk array (I)
1 b.
OFF
ON
Ensure that all the LEDs of all the disk drives at the front of the controller stop blinking. See Figure 1-16. Figure 1-16 Disk array (II)
Issue 10 (2010-09-06)
1-21
4.
NOTE
Step 5 If required, shut down the cabinet and other devices. ----End
1-22
Issue 10 (2010-09-06)
2 Setting the M2000 Time
2
About This Chapter
Setting the M2000 Time
This chapter 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 Management for the Huawei Mobile Network This section describes the time synchronization solution of the Huawei mobile network. By using the time synchronization solution, you can synchronize time between the M2000 and other Huawei mobile network devices. In addition, the M2000 supports the setting of DST and the automatic change according to the preset DST rules. 2.2 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.3 Changing the Time Zone of the M2000 Server Without Using DST This section describes how to change the time zone of the M2000 server without using DST. The correct setting of the time zone on the M2000 server is essential to the local time display and NTP service. You need to change the time zone of the M2000 server to ensure that the time zone meets the requirement. 2.4 Modifying the Date, Time, and Time Zone on the M2000 Client This section describes how to modify the date, time, and time zone on the M2000 client that is based on the Windows operating system. Modifying the date, time, and time zone on the M2000 client means modifying the date, time, and time zone of Windows. 2.5 Configuring the NTP Service of the M2000 This section describes how to set the M2000 server as the NTP client and synchronize time with the upper-layer server and how to set the M2000 client as the NTP client and synchronize time with the M2000 server. 2.6 Setting DST for the M2000 This section describes how to set the time zone of the M2000 server to enable the M2000 support DST. If DST change occurs on an NE, ensure that the M2000 can handle the data reported by the NE and that no reported data is missing.
Issue 10 (2010-09-06)
2-1
2.1 Time Management for the Huawei Mobile Network

This section describes the time synchronization solution of the Huawei mobile network. By using the time synchronization solution, you can synchronize time between the M2000 and other Huawei mobile network devices. In addition, the M2000 supports the setting of DST and the automatic change according to the preset DST rules. 2.1.1 Introduction to Time Synchronization This section describes the purpose and definition of time synchronization, the elements of the time synchronization solution, and the impact on system performance and other OM features after the time synchronization solution is implemented. 2.1.2 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.3 Time Synchronization Modes of Huawei Mobile Network This section 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.4 Introduction to the DST This section describes the daylight saving time (DST) and the DST impact on the M2000 system.
2.1.1 Introduction to Time Synchronization

This section describes the purpose and definition of time synchronization, the elements of the time synchronization solution, and the impact on system performance and other OM features after the time synchronization solution is implemented.
Purpose of Time Synchronization

Time synchronization enables you to synchronize time between the M2000 and other NEs. The networking mode of a mobile network is complex if the mobile network has multiple NEs. The uniform OM mode of NEs in a mobile network requires the time synchronization between NEs. This ensures that the M2000 correctly manages the alarms and performance data reported by the NEs. Inaccurate time may lead to the following scenarios:
l
If the alarm time is inaccurate, the sequence of generated alarms, the interval between alarm generation 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, time synchronization enables the system to automatically adjust the OM time of NEs.
Definition of Time Synchronization

Time synchronization is the synchronization of 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 devices according to the received time.
Elements of the Time Synchronization Solution

At least two elements are involved in the time synchronization solution, namely, the method of time synchronization and the choice of time reference sources.
l
In the architecture of the current time synchronization networking, the common method is to implement 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 a great number of NTP clients request to connect to the NTP server at the same time, these connections consume mass resources, such as the CPU and the memory of the NTP server. As a result, the performance of the NTP server is affected. Therefore, if you use the NTP protocol to construct a time synchronization network, the number of NTP nodes under an 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 an NTP client should be 30 minutes or longer. In addition, you need to reduce the probability of concurrent requests.
Impact on OM
The time synchronization feature is vital for the OM of the mobile network. It has the following impacts on the other features:
l
Ensures the accuracy and consistency of the time on the M2000 and NEs in a mobile network. Time synchronization plays a key role in timely fault reporting, information accuracy, and fault correlation analysis in fault management. If the NE time is inaccurate or inconsistent with the M2000 time, a mistake may be made during the fault identification and handling. Has a significant impact on the accuracy of log record, query, display, audit, and analysis. If the time is inaccurate or the time of NEs in the entire network is not the same, the log record is incorrect and the log audit is also affected. Has 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. Has a significant impact on 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.2 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).
Issue 10 (2010-09-06)

l
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.
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 disadvantages in 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.3 Time Synchronization Modes of Huawei Mobile Network

This section 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 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. Specify an IP address for the NTP server that the M2000 server gains access to, 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.
NOTE
The upper-level time servers of the M2000 server and the administration console require to use the NTP protocol. The server running the Windows operating system uses the SNTP protocol, and thus it cannot function as the upper-level time server of the M2000 server and the administration console.
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.
2-6

l
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
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.
Issue 10 (2010-09-06)
2-7
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.
l
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. By running the MML commands, you can configure the SNTP server attributes for the active BAM of device A.
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 10 (2010-09-06)
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 10 (2010-09-06)
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, the workload on configuring the firewall is reduced. 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 intermediate-layer NTP server provides two channels of NTP service output that are mutually backed up.
2-10
Issue 10 (2010-09-06)

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. When 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
Issue 10 (2010-09-06)
2-11
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.1.4 Introduction to the DST

This section 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, which does not affect the local time. The DST does not affect the NTP service.
2.2 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
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.
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 to 7.2.4 Stopping the M2000 Services. Step 3 Stop the Sybase. # su - dbuser To know how to stop the Sybase, refer to 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit 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. # su - dbuser

For details on how to start the Sybase, refer to 14.2.2 How to Start the Sybase. -bash-3.00$ exit Step 6 Start the M2000. For details on how to start the M2000, refer to 7.2.3 Starting the M2000 System Services. ----End
2.3 Changing the Time Zone of the M2000 Server Without Using DST
This section describes how to change the time zone of the M2000 server without using DST. The correct setting of the time zone on the M2000 server is essential to the local time display and NTP service. You need to change the time zone of the M2000 server to ensure that the time zone meets the requirement.
Prerequisite
Context
l
On the Solaris operating system, two time 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 regions that do not use DST. The time zone code format must be used by the countries and regions that use DST. Otherwise, the operating system does not support the automatic DST change. The change of the server time zone results in the change of time at the Solaris bottom layer. In this case, all the timers depending on the operating system are reset or become invalid. To avoid the function failure caused by invalid timers, you need to stop the M2000 and Sybase services before you change the server time zone. During this period, the performance data and alarm data of the managed NEs cannot be handled in time. After the M2000 and Sybase services are restored, the M2000 starts the automatic synchronization function, and collects and handles the missing performance data and alarm data from the managed NEs. If you need to change both the time and the time zone, change the time zone first. If the M2000 does not use DST, you need to change the time zone of the server by performing the following operations. Otherwise, you need to change the time zone of the server by referring to 2.6 Setting DST for the M2000. Coordinated Universal Time, which is referred to as Greenwich Mean Time (GMT), is taken as a reference. The time zone of the region to the east of the GMT region is represented by GMT+N. That is, the time of the region is N hours earlier than the GMT. The time zone of the region to the west of the GMT region is represented by GMT-N. That is, the time of the region is N hours later than the GMT. For example, GMT+08:00 is eight hours earlier than the GMT and GMT-08:00 is eight hours later than the GMT. When you modify the time zone configuration file /etc/TIMEZONE of the Solaris, GMT+N refers to the time zone that is N hours later than the GMT and GMT-N refers to the time zone that is N hours earlier than the GMT.
l l
2-14
Procedure
Step 1 If any M2000 service is running, stop it. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. Step 2 If any Sybase service is running, stop it. # su - dbuser For details about how to stop the Sybase services, see 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 3 Run the following command to change the value of TZ in the /etc/TIMEZONE file to the name of the required local time zone: # TERM=vt100; export TERM # vi /etc/TIMEZONE For example, set TZ to GMT+8.
NOTE
In this case, GMT+N indicates that the local time is N hours later than the GMT. GMT-N indicates that the local time is N hours earlier than the GMT. Before the change, ensure that the binary time zone file corresponding to the GMT time zone exists in the /usr/share/lib/zoneinfo directory. Otherwise, the change fails. The /etc/TIMEZONE file is read-only. Save the file after modification.
Step 4 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 The Sybase and M2000 services automatically start after the operating system is restarted. ----End
2.4 Modifying the Date, Time, and Time Zone on the M2000 Client
This section describes how to modify the date, time, and time zone on the M2000 client that is based on the Windows operating system. Modifying the date, time, and time zone on the M2000 client means modifying the date, time, and time zone of Windows.
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Open the Control Panel. This takes the Windows XP operating system as an example. Step 2 Double-click Date and Time.
Step 3 In the Date and Time Properties dialog box, select the items to be modified. Item Hour Minute Second Operation Set the required hour on the Time tab page. Set the required minute on the Time tab page. Set the required second on the Time tab page.
Time Zone Click the Time Zone tab. On the Time Zone tab page, choose the local time zone from the drop-down list. Step 4 Click Apply. ----End
2.5 Configuring the NTP Service of the M2000

This section describes how to set the M2000 server as the NTP client and synchronize time with the upper-layer server and how to set the M2000 client as the NTP client and synchronize time with the M2000 server. 2.5.1 Checking the Time Settings of the M2000 Server This section describes how to check the time settings of the M2000 server. Before configuring the NTP service, you need to ensure that the time zone, date, and time are set correctly on the M2000 server. 2.5.2 Setting the M2000 Administration Console as the Secondary NTP Server This section 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.5.3 Starting the NTP Service on the M2000 Administration Console This section describes how to start the NTP service on the M2000 administration console to synchronize the system. 2.5.4 Checking the Running Status of the NTP Service on the M2000 Administration Console This section describes how to check the operational status of the NTP service. 2.5.5 Setting the M2000 Server as the NTP Client This section 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.5.6 Starting the NTP Service on the M2000 Server This section describes how to start the NTP service on the M2000 server to synchronize the system. 2.5.7 Checking the Running Status of the NTP Service on the M2000 Server This section describes how to check the operational status of the NTP service. 2.5.8 Setting the NTP Service on the M2000 Client
This section 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 Checking the Time Settings of the M2000 Server

This section describes how to check the time settings of the M2000 server. Before configuring the NTP service, you need to ensure that the time zone, date, and time are set correctly on the M2000 server.
Procedure
Step 1 Run the following command to check the time zone of the server: # echo $TZ If the time zone is set incorrectly on the system that does not use DST, change the time zone by referring to 2.3 Changing the Time Zone of the M2000 Server Without Using DST. Otherwise, change the time zone by referring to 2.6 Setting DST for the M2000. Step 2 Run the following command to check the date and time of the server: # date If the date is incorrect or the time difference of the server time and the clock source exceeds two minutes, change the date and time by referring to 2.2 Modifying the Date and Time on the M2000 Server. ----End
2.5.2 Setting the M2000 Administration Console as the Secondary NTP Server
This section 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. The upper-level time server of the M2000 administration console requires to use the NTP protocol. The server running the Windows operating system uses the SNTP protocol, and thus it cannot function as the the upper-level time server of the M2000 administration console.
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
prefer indicates that the IP address of the NTP server is synchronized preferentially. If multiple upper-level NTP servers exist, write multiple lines. Ensure that each line maps to an NTP server. For example:
server IP address of the upper-level NTP server prefer server IP address of the upper-level NTP server
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 is 10.161.94.212, 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 prefer server 127.127.1.0 fudge 127.127.1.0 #broadcast 224.0.1.1 ttl 4
Postrequisite
After setting the M2000 administration console as the secondary NTP server, you need to start the NTP service on the administration console. For details, see 2.5.3 Starting the NTP Service on the M2000 Administration Console.
2-18
Issue 10 (2010-09-06)
2.5.3 Starting the NTP Service on the M2000 Administration Console

This section 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 According to the system output, you can check whether the NTP service is started.
l
In the system output, if STATE is disabled, it indicates that the NTP service is not started. Then, perform Step 2 to start the NTP service. In the system output, if STATE is online or maintenance, run the following command to stop the NTP service. Then, perform Step 2 to restart the NTP service. # svcadm disable svc:/network/ntp:default
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.5.4 Checking the Running Status of the NTP Service on the M2000 Administration Console
This section describes how to check the operational status of the NTP service.
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.5.5 Setting the M2000 Server as the NTP Client

This section 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.
Context
The upper-level time server of the M2000 server requires to use the NTP protocol. The server running the Windows operating system uses the SNTP protocol, and thus it cannot function as the upper-level time server of the M2000 server.
Procedure
Step 1 Stop the M2000. To know how to stop the M2000, refer to 7.2.4 Stopping the M2000 Services.
Step 2 Stop the Sybase. # su - dbuser To know how to stop the Sybase, refer to 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 3 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 4 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 5 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 6 Save the ntp.conf file and then quit vi. Step 7 Start the Sybase. # su - dbuser For details on how to start the Sybase, refer to 14.2.2 How to Start the Sybase. -bash-3.00$ exit Step 8 Start the M2000. For details on how to start the M2000, refer to 7.2.3 Starting the M2000 System Services. ----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
Postrequisite
After setting the M2000 server as the Network Time Protocol (NTP) client, you need to start the NTP service on the server. For details, see 2.5.6 Starting the NTP Service on the M2000 Server.
2.5.6 Starting the NTP Service on the M2000 Server

This section 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 According to the system output, you can check whether the NTP service is started.
l
In the system output, if STATE is disabled, it indicates that the NTP service is not started. Then, perform Step 2 to start the NTP service. In the system output, if STATE is online or maintenance, run the following command to stop the NTP service. Then, perform Step 2 to restart the NTP service. # svcadm disable svc:/network/ntp:default
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.5.7 Checking the Running Status of the NTP Service on the M2000 Server
This section describes how to check the operational status of the NTP service.
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.5.8 Setting the NTP Service on the M2000 Client

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, Windows 2003, Windows 2008, Windows XP Professional or Windows Vista Business operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client. Choose Start > Run. In the displayed Run dialog box, enter regedit to open the Registry Editor window. 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, it indicates that the value can be ignored and the registry need not be modified.
NOTE
For the operating systems of Windows 2003 or Windows 2008, In the registry, change the value of Enable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpServer to 0.
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 Restart the Windows Time service. Choose Start > Run. In the displayed Run dialog box, enter services.msc to open the Services window. Identify the Windows Time service and restart the service. Step 4 Check the NTP server specified by the PC. c:\>net time /querysntp
NOTE
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.
Step 5 Perform operations based on operating systems.

l l
If the M2000 client runs on Windows 2000 operating system, perform Step 6. If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vista operating system, perform Step 7 through Step 8.
Step 6 Run the following command to check the running status of the SNTP: c:\>w32tm -once -v -test The system displays the host name of the connected NTP server, deviation between the local time and the NTP server time, and time cycle of NTP server roll. Step 7 Run the following command to manually synchronize the time: c:\>w32tm /resync
Step 8 Run the following command to check the running status of the SNTP: c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly The system displays the following information, including the local time of the client and deviation of the local time from that on the NTP server.
Tracking 10.71.15.98 [10.71.15.98]. The current time is 2009-6-22 10:05:09 (local time). 10:05:09, +04.9881239s 10:05:11, +04.9814570s 10:05:13, +04.9740897s 10:05:15, +04.9589559s 10:05:17, +04.9449507s ...
In the system output, the first column displays the local time of the client, and the second column displays the deviation between the local time and the server time. + indicates that the client time is earlier than the server time. - indicates that the client time is later than the server time. You can press Ctrl+C to exit the browse window. ----End
2.6 Setting DST for the M2000

This section describes how to set the time zone of the M2000 server to enable the M2000 support DST. If DST change occurs on an NE, ensure that the M2000 can handle the data reported by the NE and that no reported data is missing.
Prerequisite
Context
l
On the Solaris operating system, two time 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 regions that do not use DST. The time zone code format must be used by the countries and regions that use DST. Otherwise, the operating system does not support the automatic DST change. The government may adjust the DST rule of a time zone owing to various reasons. Therefore, you need to query the DST rule of the corresponding time zone based on the time zone code before setting DST. This ensures that the DST rule defined by the time zone code is consistent with the actual DST rule. When the DST rule of a time zone are adjusted, the Sun may release the code patch of this time zone. You can install the code patch to obtain the latest time zone code and DST rule. The setting of the M2000 DST leads to the change of the time at the Solaris bottom layer. In this case, all the timers depending on the operating system are reset or invalidated. To avoid the function failure caused by invalid timers, you need to stop the M2000 and Sybase services before you set the M2000 DST. During this period, the performance data and alarm data of the managed NEs cannot be handled in time. After the M2000 and Sybase services are restored, the M2000 starts the automatic synchronization function, and collects and handles the missing performance data and alarm data from the managed NEs.
Issue 10 (2010-09-06)

l
If you need to set DST and change time, set DST first.
Procedure
Step 1 Query the local time zone name. For details about how to query the name of a time zone name, see 14.1.10 How to Query the Time Zone Name. Step 2 Run the following command to view the DST rule of the time zone in a specified year: # zdump -v time zone name | grep specified year
l
If specified year refers to the current year:
If DST is not used, only one row of information is displayed. If DST is used, five rows of information is displayed for describing the DST rule. The format of the displayed information is as follows:
Time zone name UTC time = local time isdst=0/1
The UTC time is the GMT. isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DST period. If DST is used, four rows of information is displayed for describing the DST rule. If the displayed information does not have four rows, you can infer that DST is not used. The format of the displayed information is as follows:
Time zone name UTC time = local time isdst=0/1
If specified year does not refer to the current year:
The UTC time is the GMT. isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DST period.
If you do not add | grep specified year to the previous command, the system displays the DST rules of the time zone in all years. The DST rule of a time zone stipulates the day, week, and month when DST starts and ends in each year. This means that the week when DST starts is fixed and that the date when DST starts is flexible. For example, DST in the time zone US/Alaska starts from the second Sunday of March and ends on the first Sunday of November in each year. You can run 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 system output, you can infer the universal change rules of DST.
NOTE
l l
Step 3 Select different operations based on the DST rule.

l
If the DST rule defined by the time zone code is consistent with the actual DST rule, proceed with Step 4 through Step 7 to set DST. If the DST rule defined by the time zone code is inconsistent with the actual DST rule, obtain and install the latest code patch of the time zone before setting DST.
Step 4 If any M2000 service is running, stop it. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. Step 5 If any Sybase service is running, stop it. # su - dbuser
For details about how to stop the Sybase services, see 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit Step 6 Run the following command to change the value of TZ in the /etc/TIMEZONE file to the name of the required local time zone: # TERM=vt100; export TERM # vi /etc/TIMEZONE For example, set TZ to PRC.
NOTE
Query the required time zone in the /usr/share/lib/zoneinfo/src directory. Ensure that the relevant binary time zone file exists in the /usr/share/lib/zoneinfo directory. For example, if you find the local time zone name PRC in the asia file in the /usr/share/lib/zoneinfo/src directory, you need to check whether the binary time zone file /usr/share/lib/zoneinfo/PRC exists. The /etc/TIMEZONE file is read-only. Save the file after modification.
Step 7 Restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6 The Sybase and M2000 services automatically start after the operating system is restarted. ----End
Example
The query of the DST rules of PRC and US/Alaska in 2007 is taken as an example.
l
Run the following command to view the DST rule of the RPC time zone in 2007: # zdump -v PRC|grep 2007
If the current year is 2007, the system displays only one row of the following information:
PRC Mon Sep 17 06:03:55 2007 UTC = Mon Sep 17 14:03:55 2007 CST isdst=0
If the current year is not 2007, the system does not display any information.
Therefore, you can infer that the PRC time zone does not have DST in 2007.
l
Run the following command to view the rule of the US/Alaska time zone in 2007: # zdump -v US/Alaska|grep 2007
If the current year is 2007, The system displays the following information:
US/Alaska isdst=1 US/Alaska isdst=0 US/Alaska isdst=1 US/Alaska isdst=1 US/Alaska isdst=0 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 Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT 4 01:00:00 2007 AKST
Issue 10 (2010-09-06)
2-27
Based on isdst=1 contained in the information in the first row, you can infer that DST is used in US/Alaska. 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 row and the third row, you can infer that DST starts after Mar 11 02:00:00 2007 changes to Mar 11 03:00:00 2007. Based on the information in the fourth row and the fifth row, you can infer that DST ends after Nov 4 02:00:00 2007 changes to Nov 4 01:00:00.
If the current year is not 2007, The system displays the following information:
US/Alaska isdst=0 US/Alaska isdst=1 US/Alaska isdst=1 US/Alaska isdst=0 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 Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT 4 01:00:00 2007 AKST
Based on the information in the first row and the second row, you can infer that DST starts after Mar 11 02:00:00 2007 changes to Mar 11 03:00:00 2007. Based on the information in the third row and the fourth row, you can infer that DST ends after Nov 4 02:00:00 2007 changes to Nov 4 01:00:00.
2-28
Issue 10 (2010-09-06)
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 chapter describes how to set the host name and the IP address of the M2000 server, according to field requirements. 3.1 Changing the Host Name of the M2000 Server This section describes how to change the host name of the M2000. 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 section 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 or RSC or XSCF on the M2000 Server This section describes how to modify the IP address of the SC/RSC/XSCF on the M2000 server. In special situations, you can log in to the M2000 server through the IP address of the SC/RSC/ XSCF to operate and maintain the server. 3.4 Modifying the IP Address of the Disk Array This section 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 10 (2010-09-06)
3-1
3.1 Changing the Host Name of the M2000 Server

This section describes how to change the host name of the M2000. 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.
Context
CAUTION
l
Please note if there are any alarms which alarm object is old hostname, please manully clear those alarms after the hostname changed to the new one. Because those alarms object (hostname) was changed, they can not be automatically cleared. The network adapter type varies with the model of the server. The network adapter of the Netra 240 is bge, the network adapter of the V890 or E4900 is ce, the type of the network adapters used by the T5220 servers is e1000g. When the M4000/M5000 server is used, run the following command: # ifconfig -a | grep e1000g If there is any system output, it indicates that the M4000/M5000 server uses the nxge0 and e1000g0 Ethernet ports. The function of port nxge0 is similar to that of port bge0 of the Netra 240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of port e1000g0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, and port e1000g2 of the T5220. If there is no system output, it indicates that the M4000/M5000 server uses the bge0 and nxge0 Ethernet ports. The function of port bge0 is similar to that of port bge0 of the Netra 240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of port nxge0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, and port e1000g2 of the T5220.
If the file to be modified is read-only, run the wq! command to save the file forcibly after the modification. The following procedure takes the ce as an example. Change the network adapter type according to actual situations.
Procedure
Step 1 Log in to the system controller (SC), remote system controller (RSC) or eXtended System Controller facility (XSCF) of the server. For details, see the M2000 Software Initialization Installation Guide (Sun, S10). Step 2 Check the host name of the server. # hostname
l l
If the host name is incorrect, proceed with the next step. If the host name is correct, do not proceed with the next step.
3-2
Step 3 If the M2000 is running, stop it. For details about how to view the M2000 service, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000, refer to 7.2.4 Stopping the M2000 Services. Step 4 Check whether the Sybase service is running. If the Sybase service is running, stop it. # su - dbuser For details about how to view and stop the Sybase service, see 14.2.1 How Do I Check Whether the Sybase Is Started? and 14.2.3 How Do I Stop the Sybase? respectively. -bash-3.00$ exit Step 5 Edit the /etc/hosts file to change the existing host name to a new one. # TERM=vt100; export TERM # vi /etc/hosts Step 6 Edit the /etc/nodename file to change the existing host name to a new one. # vi /etc/nodename Step 7 Check whether the maintenance dual plane is configured. Then, determine whether to modify the corresponding file. Maintenance dual plane is configured? Step 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 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 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 of content. For the /etc/hostname.ce0 and /etc/hostname.ce2 files, ce in the file names refers to the network adapter type. Thus, the names of the two files vary with the network adapter type. For example, when the network adapter type is bge, the corresponding files are /etc/hostname.bge0 and /etc/ hostname.bge2. The network adapter type varies with the model of the server. For their relation, see the background information.
Step 8 Check the correlation between the /etc/inet/ipnodes and /etc/hosts files. 1. Run the following command to check the correlation between the /etc/inet/ipnodes and / etc/inet/hosts files.
Issue 10 (2010-09-06)
# ls -al /etc/inet/ipnodes
l
If the command result contains /etc/inet/ipnodes -> ./hosts, it indicates that the two files are correlated. Then, go to Step 8.2. If the command result does not contain /etc/inet/ipnodes -> ./hosts, it indicates that the two files are not correlated. Then, go to Step 9.
2.
Run the following command to check the correlation between the /etc/hosts and /etc/inet/ hosts files. # ls -al /etc/hosts
l
If the command result contains /etc/hosts -> ./inet/hosts, it indicates that the /etc/hosts and /etc/inet/hosts files are correlated, and thus the /etc/hosts and /etc/ inet/ipnodes files are also correlated Then, go to Step 10. If the command result does not contain /etc/hosts -> ./inet/hosts, it indicates that the /etc/hosts and /etc/inet/hosts files are not correlated, and thus the / etc/hosts and /etc/inet/ipnodes files are not correlated. Then, go to Step 9.
Step 9 Edit /etc/inet/ipnodes to change the previous host name to the new host name. # vi /etc/inet/ipnodes Step 10 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 Step 11 Switch to user dbuser. Open the /opt/sybase/interfaces file. # su - dbuser -bash-3.00$ 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.
After the modification, switch to user root. -bash-3.00$ exit Step 12 Restart the server and view the status of the Sybase and M2000 services.
CAUTION
If the Sybase and M2000 services are exceptional after the server is restarted, contact Huawei technical support engineers for assistance. 1. Run the following command to restart the server. # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -g0 -y -i6
After the server is restarted, both of the Sybase and M2000 services are automatically restarted. 2. 3. Log in to the server as user root. View the status of the Sybase and M2000 services. # su - dbuser For details about how to view the status of the Sybase service, see 14.2.1 How Do I Check Whether the Sybase Is Started?. -bash-3.00$ exit # . /opt/OMC/svc_profile.sh # svc_adm -cmd status ----End
3.2 Modifying the IP Address of the M2000 Server

This section 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 Adding or Deleting Routes on the M2000 Server This section describes how to add or delete routes from the current network to several destination networks. 3.2.2 Changing the IP Address of the M2000 Server This section describes how to change the IP address of the M2000 server based on the actual requirements.
3.2.1 Adding or Deleting Routes on the M2000 Server

This section describes how to add or delete routes from the current network to several destination networks.
Prerequisite
Issue 10 (2010-09-06)
3-5
Context
CAUTION
Run the following command to add a route. After you restart the server, the added route is automatically disabled. # route add Destination address/mask gateway For example: # route add 129.8.0.0/24 10.12.8.1
Procedure
Step 1 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.2 Changing the IP Address of the M2000 Server

This section describes how to change the IP address of the M2000 server based on the actual requirements.
Context
l
Maintenance dual plane: After the two network ports are set, the Solaris operating system dynamically monitors the validity of each network port. When the active network port is out of service, the system switches the IP address from the previous active port to the current active port. This ensures continuity in the communication between the server and the external network. The system continues the monitoring on the port that is currently invalid. Once the invalid port becomes active, the system switches the IP address and subnet mask to the IP address and subnet mask of the restored port. The M2000 client, NEs, and network management system (NMS) set up communication with the M2000 server through the IP address of the server. Thus, functions such as data transfer, operation, and maintenance are implemented. Allocate physical IP addresses to the Ethernet ports of the server and configure the maintenance dual plane to implement the redundancy backup of Ethernet ports. In this case, the communication between the server and external devices is secure and reliable. When the OM network requires reparenting, adjustment or reallocation of IP addresses, you need to change the IP address of the server. You can change the IP address of the server to meet the requirements for network reparenting and adjustment. In this case, the OM network is easily managed and maintained and is more open and flexible. In addition, the scalability and evolution of the network are improved. During the change of the server IP address, the performance data and alarm data of the managed NEs cannot be processed. If the IP address of the M2000 server are recorded in the NE database, changing the IP address of the M2000 server leads to the disconnection between the M2000 server and NEs. When changing the IP address of the M2000 server, you need to notify the NE maintenance engineers and ask them to modify the relevant plans and update the IP address of the M2000 server recorded in the NE database. After you change the IP address of the server, the M2000 collects performance data and alarm data again through automatic synchronization and then processes the data. The IP addresses are stored in the relevant configuration files of the operating system, the database, and the M2000. You can run the modify.sh script to modify the IP address information in these configuration files and change the IP address of the server. The M2000 supports both LAN and WAN networking modes. For details, see the M2000 Commissioning Guide (Sun, S10).
Issue 10 (2010-09-06)
3-7
CAUTION
l
The network adapter type varies with the model of the server. The network adapter of the Netra 240 is bge, the network adapter of the V890 or E4900 is ce, the type of the network adapters used by the T5220 servers is e1000g. When the M4000/M5000 server is used, run the following command: # ifconfig -a | grep e1000g If there is any system output, you can infer that the M4000/M5000 server uses the nxge0 and e1000g0 Ethernet ports. The function of port nxge0 is similar to that of port bge0 of the Netra 240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of port e1000g0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, and port e1000g2 of the T5220. If there is no system output, you can infer that the M4000/M5000 server uses the bge0 and nxge0 Ethernet ports. The function of port bge0 is similar to that of port bge0 of the Netra 240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of port nxge0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, and port e1000g2 of the T5220.
For example, the model of the server is V890. If the maintenance dual plane is configured on the system, the ce0 and ce2 network ports on the server are used to configure the maintenance dual plane. The maintenance dual plane implement backup of network ports. Thus, the communication between the server and external devices can be secure and reliable. When other servers are adapted, the maintenance dual plane is similar with that of the V890 except the network adapter type. The network adapter type varies with the model of the server. For their relation, see the previous information. If the maintenance dual plane is configured on the system, the server IP address and the physical IP addresses of network ports must be set in the same network segment. If you change the IP addresses on different network segments, you need to plan and change the M2000 server IP address, and the physical IP addresses of network ports at the same time. In this case, run the modify.sh script to change the IP address of the M2000 server, modify the IP address information in routing devices, and then restart the M2000 server. This assumes that the system is configured with the maintenance dual plane and describes how to change the IP address of the server and the physical IP addresses of two Ethernet ports. If you need to change only some IP addresses of the system, perform operations to change only these IP addresses in the relevant steps. If the system is not configured with the maintenance dual plane, perform operations to change only the IP address of the server in the relevant steps. The following procedure takes the ce as an example. Change the network adapter type according to actual situations.
Procedure
Step 1 Log in to the server as user root. Step 2 Run the following command to view the host name of the server: # hostname The system displays the host name of the server. This takes host name osssvr-1 as an example.
Step 3 View the /etc/hosts file to obtain the host name of the server and the IP addresses corresponding to the host names of the two Ethernet ports. # more /etc/hosts The system displays the following information:
# # Internet host table # 127.0.0.1 localhost 192.168.8.11 192.168.8.18 192.168.8.19 #6140 192.168.8.39 192.168.8.40 osssvr-1 osssvr-1-ce0 osssvr-1-ce2 ST6140-1 ST6140-1 loghost omc.com
According to the system output, the IP address corresponding to osssvr-1 is 192.168.8.11, that of osssvr-1-ce0 is 192.168.8.18, and that of osssvr-1-ce2 is 192.168.8.19.
NOTE
In the system output, ce in osssvr-1-ce0 and osssvr-1-ce2 refers to the Ethernet adapter type and varies with the Ethernet adapter type. When the Ethernet adapter type is bge, the corresponding parameter is osssvr-1-bge0 and osssvr-1-bge2. The Ethernet adapter type varies with the server type. For their correspondence, see the background information.
Step 4 Run the following command to check the IP addresses: # ifconfig -a The system displays the IP addresses obtained in Step 3. Check whether the IP addresses meet the site requirements.
l l
If the IP addresses do not meet the requirements, perform the following steps to change them. If the IP addresses meet the requirements, you need not perform the following steps.
Step 5 Check whether the new IP address is already used. This section describes how to change the IP address of the server from 192.168.8.11 to 10.10.10.10, the physical IP addresses of the two Ethernet ports from 192.168.8.18 and 192.168.8.19 to 10.10.10.18 and 10.10.10.19. On the client PC whose IP address is on the same network segment as the new IP address, open the DOS command window and then run the ping 10.10.10.10, ping 10.10.10.18, ping 10.10.10.19 commands.
l
If the IP address can be successfully pinged, you can infer that this new IP address is already used and you need to use another one. If the IP address cannot be pinged, you can infer that this new IP address is idle and can be used.
Step 6 If the M2000 is running, stop the M2000 services. Check the operation status of the M2000 services. For details, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services.
Step 7 Check whether the Sybase services are running. If not, run the following command to start the Sybase services: # su - dbuser For details about how to check and start the Sybase services, see 14.2.1 How Do I Check Whether the Sybase Is Started? and 14.2.2 How to Start the Sybase. -bash-3.00$ exit Step 8 Run the modify script to change the IP address of the server.
CAUTION
After being used to change the IP address of the server, the modify script can not be used immediately to modify parameters. You can use the modify script only when the IP address takes effect after the restart of the server. 1. Run the modify script. The default installation directory of the M2000 server software is /opt/OMC. # . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/config # ./modify.sh 2. 3. Choose 1--Single system > 1--IP. Based on the system prompts, enter the previous and new IP addresses. This section describes how to change the IP addresses 192.168.8.11 to 10.10.10.10, 192.168.8.18 to 10.10.10.18, and 192.168.8.19 to 10.10.10.19. a. When the system output is similar to the following information, press Enter. The default values in the system output are used.
-----------------------------------------------------------------Note: -- Enter key f/F to finish ip input old-new ip pairs -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the old ip[default 192.168.8.11]:
b.
When the system output is similar to the following information, enter the new IP address corresponding to the previous IP address in 8.3.a.
Please input the new ip[default 192.168.8.11]: 10.10.10.10
c.
When the system output is similar to the following information, enter the old IP address corresponding to osssvr-1-ce0.
Please input the old ip: 192.168.8.18
d.
When the system output is similar to the following information, enter the new IP address corresponding to the previous IP address in 8.3.c.
e.
When the system output is similar to the following information, enter the old IP address corresponding to osssvr-1-ce2.
3-10
Please input the old ip: 192.168.8.19
f.
When the system output is similar to the following information, enter the new IP address corresponding to the previous IP address in 8.3.e.
g.
When the system output is similar to the following information, enter f or F. Then, go to the next step.
Please input the old ip: f
NOTE
l l l l l l
When running the modify script to change the IP address of the server, if you need to change multiple IP addresses, enter all previous addresses to be changed and their new IP addresses here. If the maintenance dual-plane is not configured, enter f or F when Please input the old ip: is displayed in 8.3.c. Then, go to the next step. If you need not change a certain IP address, press Enter when you are prompted for a new IP address. Then, the default value is used. Enter p or P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. Enter q or Q to exit the modify script. When the system prompts you to enter the previous IP address, enter f or Fto finish entering IP address and proceed with the next step.
4.
Based on the system prompt, enter the password of user sa and change the subnet mask, and default route. a. When the system displays the following information, enter the password of user sa. This takes emsems as the password of user sa.
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the database superuser's password: emsems
b.
When the system output is similar to the following information, press Enter. The default value in the system output is used as the previous subnet mask.
Please input the old mask number[default 255.255.255.0]:
c.
When the system output is similar to the following information, enter the new subnet mask. If the subnet mask is not changed, press Enter.
Please input the new mask number[default 255.255.255.0]:
d.
When the system output is similar to the following information, press Enter. The default value in the system output is used as the previous default route.
Please input the old router ip address[default 192.168.8.1]:
e.
When the system output is similar to the following information, enter the new default route.
Please input the new router ip address[default 192.168.8.1]: 10.10.10.1
NOTE
l l l
Enter p or P to return to the previous step. Then, you can perform this step again to change the settings of the relevant parameters. Enter q or Q to exit the modify script. Press Enter. The default values in the system output are used.
5.
The system displays all the parameters that you set. After confirmation, enter Y to apply the changes.
Issue 10 (2010-09-06)
Are you sure to continue? Y--Yes. Q--Quit. R--Re-input P--Return pre-step Please make a choice[Y/Q/R/P]: Y
NOTE
l l l l
Enter Q to exit the script without performing any operations. Enter R to return to Step 8.3. You can reconfigure the relevant parameters. Enter P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. You need to wait for about three minutes if you run the modify script to change the IP address of the server.
6.
When the change is successful, the system displays the following information and exits the modify script.
-----------------------------------------------------------------Operator complete!
If the system output contains failed, you can infer that the change fails.Contact Huawei technical support engineers for assistance. Step 9 Based on the application scenario, perform the relevant operations. Whether to Change the Server IP Address on Different Network Segments No Yes Procedure
Perform Step 10. Perform Step 11 through Step 14.
Step 10 After restarting the server, check the status of the Sybase and M2000 services.
CAUTION
If the login fails or the Sybase and M2000 services are exceptional after the server is restarted, contact Huawei technical support engineers for assistance. 1. Run the following commands to restart the M2000 server: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i6 2. 3. Restart the server, and then log in to the server as user root through the new IP addresses. Run the following command to check the status of the Sybase and M2000 services: # su - dbuser For details about how to view the status of the Sybase services, see 14.2.1 How Do I Check Whether the Sybase Is Started?. -bash-3.00$ exit
# . /opt/OMC/svc_profile.sh # svc_adm -cmd status Step 11 Modify the gateway address information about the original network segment configured on the route switching device. Step 12 Log in to the server through the system controller (SC), remote system controller (RSC), or extended system controller facility (XSCF). For details, see the M2000 Software Initial Installation Guide (SUN, S10). Step 13 Run the following commands to restart the M2000 server: # sync; sync; sync; sync; sync; sync # /usr/sbin/shutdown -y -g0 -i6 Step 14 Use the new IP addresses to log in to the server as user root and check the status of the Sybase and M2000 services.
CAUTION
If the login fails or the Sybase and M2000 services are exceptional after the server is restarted, contact Huawei technical support engineers for assistance. # su - dbuser For details about how to check the status of the Sybase services, see 14.2.1 How Do I Check Whether the Sybase Is Started?. -bash-3.00$ exit # . /opt/OMC/svc_profile.sh # svc_adm -cmd status ----End
Postrequisite
l
(Optional) If the S2600 disk array is configured and the IP address of the server is configured as the Trap IP address of the S2600 disk array, you need to reconfigure the monitoring function of the S2600 disk array after changing the IP address of the server. For details, see 14.1.18 How to Configuring the Monitoring Function of the S2600 Disk Array. (Optional) If the S3000 series disk array is configured, you need to reconfigure the monitoring function of the disk array after changing the IP address of the server. For details, see 14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays.
Issue 10 (2010-09-06)
3-13
3.2.3 Changing the IP Address of Ethernet Port nxge3 on the M2000 Server
This section describes how to change the IP address of Ethernet port nxge3 on the M2000 server to meet the site requirement.
Prerequisite
Log in to the server as user root.
Context
CAUTION
l
If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a disk array. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must be on the same network segment. If you have changed the IP address of Ethernet port nxge3 on a different segment, you need to change the IP address of the corresponding disk array to ensure that both changed IP addresses are on the same network segment. Changing the IP address of Ethernet port nxge3 does not affect the database services and the M2000 services.
Procedure
Step 1 Run the following command to check the IP address: # ifconfig -a The system displays the IP address of Ethernet port nxge3 on the server. Check whether the IP address meets the site requirements.
l
If the IP address does not meet the requirements, you need to perform the following steps to change it. If the IP address meets the requirements, you need not perform the following steps.
Step 2 Check whether the new IP address is used. This takes changing the IP address of Ethernet port nxge3 from 192.168.8.241 to 10.10.10.241 as an example. On the client PC whose IP address is on the same network segment as the new IP address, open the DOS command window, and then run the ping 10.10.10.241 command.
l
If the IP address can be successfully pinged, it indicates that this new IP address is already used. In this case, use another IP address. If the IP address cannot be pinged, it indicates that this IP address is idle and can be used.
Step 3 Perform the following steps on the server to change the existing IP address of Ethernet port nxge3 to a new IP address.
1.
Modify the /etc/hosts file to change the existing IP address of Ethernet port nxge3 to a new IP address. # TERM=vt100; export=TERM # vi /etc/hosts
2.
Run the following command to check the link between the /etc/inet/ipnodes file and the / etc/inet/hosts file: # ls -al /etc/inet/ipnodes
l
If /etc/inet/ipnodes -> ./hosts is contained in the system output, it indicates that the two files are linked. Then, proceed with Step 3.3. If /etc/inet/ipnodes -> ./hosts is not contained in the system output, it indicates that the files are not linked. Then, perform Step 3.4.
3.
Run the following command to check the link between the /etc/hosts file and the /etc/inet/ hosts file: # ls -al /etc/hosts
l
If /etc/hosts -> ./inet/hosts is contained in the system output, it indicates that the two files are linked, that is, the /etc/hosts file and the /etc/inet/ipnodes file are linked. Then, perform Step 4. If /etc/hosts -> ./inet/hosts is not contained in the system output, it indicates that the two files are not linked, that is, the /etc/hosts file and the /etc/inet/ ipnodes file are not linked. Then, perform Step 3.4.
4.
Modify the /etc/inet/ipnodes file to change the existing IP address of Ethernet port nxge3 to a new IP address. # vi /etc/inet/ipnodes
Step 4 Modify the /etc/hostname.nxge3 file to change the existing IP address of Ethernet port nxge3 to a new IP address. # vi /etc/hostname.nxge3
NOTE
l l
If this file records the information about host names, do not modify this file. In the /etc/hostname.nxge3 file, no space is allowed at the beginning of each line of content.
Step 5 Run the following command for the new IP address of Ethernet port nxge3 to take effect: # ifconfig nxge3 10.10.10.241 netmask 255.255.255.0 up ----End
3.3 Modifying the IP Address of the SC or RSC or XSCF on the M2000 Server
This section describes how to modify the IP address of the SC/RSC/XSCF on the M2000 server. In special situations, you can log in to the M2000 server through the IP address of the SC/RSC/ XSCF to operate and maintain the server.
Issue 10 (2010-09-06)
3-15
3.3.1 Modifying the IP Address of the SC on the Netra 240 Server This section 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 section 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 section 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.4 Modifying the IP Address of the SC on the T5220 Server This section describes how to change the IP address of the SC on the T5220 server to ensure that the IP address meet the requirement. 3.3.5 Changing the IP Address of the XSCF on the M4000/M5000 Server This section describes how to change the IP address of the XSCF on the M4000/M5000 server to meet the actual requirements.
3.3.1 Modifying the IP Address of the SC on the Netra 240 Server

This section 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
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 M2000 Software Initialization Installation Guide (Sun,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 section 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 section 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.
Issue 10 (2010-09-06)
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 M2000 Software Initialization Installation Guide (M4000/M5000, 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 Enter the IP address of the actual gateway, if required yes
Hostname IP Address Netmask Gateway Enable SC Failover? [no]:
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.
3-18
Issue 10 (2010-09-06)
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 M2000 Software Initialization Installation Guide (M4000/M5000, 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 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
Hostname IP Address Netmask Gateway Enable SC Failover? [no]:

Connection type (ssh, telnet, none) [telnet]: Logical Hostname or IP Address [ ]:
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]
Issue 10 (2010-09-06)
3-19
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.3.4 Modifying the IP Address of the SC on the T5220 Server

This section describes how to change the IP address of the SC on the T5220 server to ensure that the IP address meet the requirement.
Prerequisite
l l l
The PC terminal and the network port of the SC on the server communicate well. The password for user admin of the SC is available. The new IP address of the SC is planned.
Procedure
Step 1 Start the PuTTY on the PC terminal and set up the connection between the PC and the SC based on the SSH protocol. In the window of the PuTTY Configuration, select SSH, enter IP address of the SC in Host Name (or IP Address), and click Open to log in to the SC.
NOTE
l l
Log in to the http://support.huawei.com to download the PuTTY to the PC. If the PC and SC cannot be connected through the PuTTY, connect them by using a serial port cable. For details, refer to the corresponding Software Initialization Installation Guide.
Step 2 Enter the user name admin and the password to log in to the SC. The sc> prompt is displayed. 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 the SC sc> setsc netsc_ipnetmask subnet mask of the SC sc> setsc netsc_ipgateway IP address of the SC gateway Step 4 Run the following command to change the IP address and subnet mask of the SC: sc> setsc netsc_commit true ----End
3.3.5 Changing the IP Address of the XSCF on the M4000/M5000 Server

This section describes how to change the IP address of the XSCF on the M4000/M5000 server to meet the actual requirements.
Prerequisite
l l l
The communication between the PC and port 0 on the XSCF is normal. The password of user adminuser is available. A new IP address of the XSCF is planned.
Context
l l
Port 0 and port 1 on the XSCF are independent of each other. When the M4000/M5000 server is used as the M2000 server, port 0 on the XSCF is used for networking. Thus, you need to use the IP address of port 0 to log in to the XSCF.
Procedure
Step 1 Start the PuTTY on the PC and log in to the XSCF of the server through the telnet.
NOTE
l l l l
To log in to the XSCF of the M4000/M5000 server, use the IP address of port 0 on the XSCF. Log in to the http://support.huawei.com to download the PuTTY to the PC. For details about how to log in to the XSCF through the PuTTY, see M2000 Software Initialization Installation Guide (T5220&M4000&M5000, S10) If the PC and XSCF cannot be connected by running the telnet command, connect them through a serial port cable. For details, see M2000 Software Initialization Installation Guide (T5220&M4000&M5000, S10).
Step 2 Log in to the XSCF as user adminuser. Step 3 Run the following command to change the IP address of the XSCF. XSCF> setupplatform Step 4 When the system displays Do you want to set up an account? [y|n]:, type n, and then press Enter. Step 5 When the system displays Do you want to set up networking? [y|n]:, type y, and then press Enter. Step 6 When the system displays Do you want to set up the XSCF network interfaces? [y|n]:, type y, and then press Enter. Step 7 Set the IP address, subnet mask, and gateway IP address of xscf#0-lan#0. 1. 2. When the system displays Do you want to configure xscf#0-lan#0? [y| n]:, type y. When the system displays the following prompt, enter the IP address, subnet mask, and gateway IP address of port 0 on the XSCF according to the planning:
xscf#0-lan#0 ip address? []: xscf#0-lan#0 netmask? [255.255.255.0]: xscf#0-lan#0 default gateway? []:
3.
Check the entered information.

xscf#0-lan#0 ip address: X.X.X.X xscf#0-lan#0 netmask: X.X.X.X xscf#0-lan#0 default gateway: X.X.X.X Are these settings correct? [y|n]: y
Issue 10 (2010-09-06)
3-21
NOTE
l l l
In xscf#0-lan#0 ip address: X.X.X.X, X.X.X.X indicates a new IP address planned for port 0 on the XSCF. In xscf#0-lan#0 netmask: X.X.X.X, X.X.X.X indicates a new subnet mask planned for port 0 on the XSCF. In xscf#0-lan#0 default gateway: X.X.X.X, X.X.X.X indicates a new gateway IP address planned for port 0 on the XSCF.
Step 8 When the system displays Do you want to configure xscf#0-lan#1? [y| n]: , type n. Step 9 When the system displays Do you want to configure lan#0? [y|n]:, type n. Thus, you need not configure the take over function for network adapter 0. Step 10 When the system displays Do you want to configure lan#1? [y|n]:, type n. Thus, you need not configure the take over function for network adapter 1. Step 11 When the system displays Do you want to set up the DSCP network? [y| n]:, type n. Thus, you need not configure the DSCP protocol. Step 12 When the system displays Do you want to set up the domain name service? [y|n]:, type n. Step 13 When the system displays Do you want to set up the network time protocol? [y|n]:, type n. Thus, you need not configure the NTP service. Step 14 When the system displays Do you want to set up ssh? [y|n]:, type n. Thus, you need not configure the SSH protocol. Step 15 When the system displays Do you want to set up https? [y|n]:, type n. Then, the https will not be enabled. Step 16 When the system displays Do you want to configure email reports? [y| n]:, type n. Then, the email function will not be enabled. Step 17 When the system displays Do you want to apply the network changes? [y| n]:, type y. Step 18 Check the network configuration information about the XSCF.
The following network settings will be applied: xscf#0 hostname :osssvr-1-xscf0 DNS domain name : interface status IP address netmask route interface status IP address netmask route Continue? [y|n] :y :xscf#0-lan#0 :up :X.X.X.X :X.X.X.X :-n 0.0.0.0 -m 0.0.0.0 -g X.X.X.X :xscf#0-lan#1 :up :192.168.9.141 :255.255.255.0 :-n 0.0.0.0 -m 0.0.0.0 -g 192.168.9.254
Step 19 When the system displays Do you want to reboot the XSCF now? [y|n]:, type y. Then, the XSCF automatically restarts. ----End
3.4 Modifying the IP Address of the Disk Array

This section 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. Normally, you need not change the IP address of the disk array because the disk array is connected to the server directly through optical fibers. In addition, change of IP addresses does not affect data read and write operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation. 3.4.2 Changing the IP Address of the S3200 Series Disk Array (Serial Port Mode) This section describes how to change the IP address of the S3200 series disk array. Normally, you need not change the IP address of the disk array because the disk array is connected to the server directly through optical fibers. In addition, change of IP addresses does not affect data read and write operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation. 3.4.3 Changing the IP Address of the S2600 Disk Array (Serial Port Mode) This section describes how to change the IP address of an S2600 disk array in serial port mode. The disk array is connected to the server directly through optical fibers. Therefore, changing the IP address of the disk array does not affect data read operations on the disk array. It is strongly recommended that you retain the default IP address of the disk array. If you need to change the IP address of the disk array, change it according to the actual situation. You need to configure each S2600 disk array. 3.4.4 Changing the IP Address of the 6140 Disk Array (Serial Port Mode) This section describes how to change the IP address of the 6140 disk array. Normally, you need not change the IP address of the disk array because the disk array is connected to the server directly through optical fibers. In addition, change of IP addresses does not affect data read operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation.
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. Normally, you need not change the IP address of the disk array because the disk array is connected to the server directly through optical fibers. In addition, change of IP addresses does not affect data read and write operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation.
Prerequisite
l l
The SUNWsscs software has been installed on the server. All the IO operations related to the disk array have been stopped.
Issue 10 (2010-09-06)
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?
Step 4 (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file.
NOTE
To change the disk array IP address recorded in the /etc/hosts file and the /etc/inet/ipnodes file, you need not stop the M2000 services and the database services. After the modification, you need not restart the server either.
1. 2.
Log in to server as user root. Perform the following operations on the server to modify the /etc/hosts file and to replace the existing IP address of the disk array with a new one. # vi /etc/hosts After the modification, press Esc and then run the :wq! command to save the modification and exit.
3.
Perform the following operations on the server to modify the /etc/inet/ipnodes file. # vi /etc/inet/ipnodes
l
If the file records the existing IP address of the disk array, replace the existing IP address with the new one. After the modification, press Esc and then run the :wq command to save the modification and exit. If the file records the new IP address of the disk array, you need not perform any modification. Press Esc and then run the :q command to exit.
----End
3.4.2 Changing the IP Address of the S3200 Series Disk Array (Serial Port Mode)
This section describes how to change the IP address of the S3200 series disk array. Normally, you need not change the IP address of the disk array because the disk array is connected to the
server directly through optical fibers. In addition, change of IP addresses does not affect data read and write operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation.
Context
The S3200 disk array has two controllers. Each controller has two Ethernet ports. When changing the IP address of a controller, only Ethernet port 1 needs to be modified. Ethernet port 2 is reserved for maintenance. If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a disk array. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must be on the same network segment. If you have changed the IP address of the disk array on a different segment, you need to change the IP address of the corresponding Ethernet port nxge3 to ensure that both changed IP addresses are on the same network segment.
Procedure
Step 1 Use the serial port cable to connect the serial port of the controller of the disk array and that of the PC. Figure 3-1 shows the disk array. Figure 3-1 Serial ports of the S3X00
NOTE
You must use the serial port cable that is delivered with the disk array instead of the serial port cable of other devices. The serial port cable delivered with the disk array is special for the storage device. If you do not use this serial port, the communication may fail. A DB-9 connector at one end of the serial port cable is connected to the serial port on the PC. A 6-thread round connector at the other end is connected to the port of the disk array controller. You configure the controller that is connected to the serial port (Controller A is on the left while controller B is on the right.)
Step 2 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal. Step 3 In the Connection Description dialog box, enter a name for the new connection. Step 4 Select the PC serial port that is connected to the SC, such as COM1. Step 5 Set the properties of the serial port. For details about how to set the properties of a serial port, see Table 3-4. Then, click OK.
Table 3-4 Setting properties of the serial port Property Bits per second Data bits Parity Stop bits Data stream control Value 9600/38400 8 Null 1 Null
Step 6 Press Ctrl+Break to activate Shell of the serial port. Step 7 If the following information is displayed in the HyperTerminal window, enter Esc within five seconds. The Shell Login interface is displayed.
Press within 5 seconds: <S>for Service Interface , <BREAK>for band rate
Step 8 If the following information is displayed, enter the login password infiniti and press Enter to log in to the disk array and to configure Shell.
Enter password to access shell:
Step 9 Run the following command to check the information about the configuration network port of the controller where the user logs in. -> netCfgShow Step 10 Run the netCfgSet command to set the IP address of the network port. Enter 192.168.8.39 after IP Address if0. To change the subnet mask, enter 192.168.8.39 after Subnet Mask if0.
NOTE
Only port if0 needs to be configured. The settings of port if1 remain unchanged.
Step 11 Press Enter. The following information is displayed after the successful modification.
Network Configuration successfully written to NVSRAM.
Step 12 Use the serial port cable to connect the serial port of controller B and that of the PC to change the IP address of the configuration network port of the other controller in the same way. Step 13 (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file.
NOTE
1. 2.
3.
3-26
Perform the following operations on the server to modify the /etc/inet/ipnodes file.
# vi /etc/inet/ipnodes
l
----End
Postrequisite
(Optional) After changing the IP address of the S3200 disk array, you need to reconfigure the monitoring function of the disk array. For details, see 14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays in the corresponding Administrator Guide. You need to reconfigure the two series disk arrays.
3.4.3 Changing the IP Address of the S2600 Disk Array (Serial Port Mode)
This section describes how to change the IP address of an S2600 disk array in serial port mode. The disk array is connected to the server directly through optical fibers. Therefore, changing the IP address of the disk array does not affect data read operations on the disk array. It is strongly recommended that you retain the default IP address of the disk array. If you need to change the IP address of the disk array, change it according to the actual situation. You need to configure each S2600 disk array.
Context
l
Each S2600 disk array has an active controller and a standby controller. Each controller has a CLI serial port. You can change the IP address in serial port mode or command mode. The serial port mode is preferred because it features high success rate in changing IP addresses. In the case of remote operations, use the command mode. For details, see 14.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)?. Before changing the IP address, you must familiarize yourself with the default IP address planning at delivery. Then, determine whether to re-set the IP address according to the actual situation. The IP address mentioned here is only an example. Replace it with the actual IP address. If you change the IP addresses of disk arrays on different network segments, change the IP address of the maintenance Ethernet port on the corresponding server to ensure that two changed IP addresses are on the same network segment.
l l
Procedure
Step 1 Use the serial port cable to connect any serial port on the controller of the disk array and that of the PC. Figure 3-2 shows the disk array.
Issue 10 (2010-09-06)
3-27
Figure 3-2 Serial ports provided by the S2600 disk array
NOTE
l l
You need to use the serial port cable that is delivered with the disk array. Otherwise, the disk array may fail to be connected. When using the serial port cable to connect a control to the maintenance terminal, you must use the serial port cable to connect the maintenance terminal first. When disconnecting the control from the maintenance terminal, you must remove the serial port cable from the control first. After using the serial port cable to connect a controller to the maintenance terminal, do not enable the control and the maintenance terminal at the same time. After using the DB9-RJ45 serial port cable to connect a controller and the maintenance terminal, you need to use the HyperTerminal or any other program provided by the Windows operating system to log in to the CLI serial port.
l l
Step 2 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on the PC. Step 3 In the Connection Description dialog box, type the name of a new connection. Step 4 Specify a serial port of the PC terminal to connect the PC terminal to the disk array, for example, COM1. Step 5 Set the properties of the serial port by referring to Table 3-5, and then click OK. Table 3-5 Setting the properties of a serial port Property Bits per second Data bits Parity check Stop bits Flow control Property Value 115200 8 None 1 None
Step 6 Press Enter. If the connection is successful, a dialog box is displayed, as shown in Figure 3-3.
Figure 3-3 Successful connection interface
Step 7 In the successful connection interface, type the user name and password. Then the successful login success dialog box is displayed, as shown in Figure 3-4.
CAUTION
The initial name and password of the administrator is admin and 123456, respectively. To ensure the system security, you need to change the password after the initial login.
Figure 3-4 Successful login dialog box
Issue 10 (2010-09-06)
3-29
Step 8 Run the following command to set the IP address of the Ethernet port managed by controller A: OceanStor:admin> chgctrlip -c a -a new IP address of controller A -s subnet mask -g gateway For example, to change the IP address of the Ethernet port that is managed by controller A to 10.71.15.20, run the following command: OceanStor:admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0 -g 10.71.15.1 When the system displays the following prompt, type y:
OceanStor: admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0 This operation will change your controller's IP configuration. if you want to ch ange the IP of the controller you logged in, you will log out after you set the new IP. However, if you change the IP of the peer controller, you needn't log out. Do you want to continue? y or n: y
Step 9 Run the following command to check whether the IP address is correct: OceanStor:admin> showctrlip -c a
Controller IP Address A 10.71.15.20 00:18:82:e2:00:fb Subnet Mask 255.255.255.0 Gateway 10.71.15.1 MAC Address
Step 10 Run the following command to set the IP address of the Ethernet port managed by controller B: OceanStor:admin> chgctrlip -c b -a new IP address of controller A -s subnet mask -g gateway For example, to change the IP address of the Ethernet port that is managed by controller B to 10.71.15.21, run the following command: OceanStor:admin> chgctrlip -c b -a 10.71.15.21 -s 255.255.255.0 -g 10.71.15.1 When the system displays the following prompt, type y:
This operation will change your controller's IP configuration. if you want to ch ange the IP of the controller you logged in, you will log out after you set the new IP. However, if you change the IP of the peer controller, you needn't log out. Do you want to continue? y or n: y
Step 11 Run the following command to check whether the IP address is correct: OceanStor:admin> showctrlip -c b
IP Address B 10.71.15.21 00:18:82:e2:01:57 Controller Subnet Mask 255.255.255.0 Gateway 10.71.15.1 MAC Address
----End
Postrequisite
During commissioning, you need to configure the monitoring function of the S2600 disk array after you install and configure the M2000 client application. For details, see section "Configuring the Monitoring Function of the S2600 Disk Array". During maintenance, if the monitoring function of the S2600 disk array is configured, you need to reconfigure this function after changing the IP address of the server. For details, see section "How to Configuring the Monitoring Function of the S2600 Disk Array" in the corresponding administrator manual.
3.4.4 Changing the IP Address of the 6140 Disk Array (Serial Port Mode)
This section describes how to change the IP address of the 6140 disk array. Normally, you need not change the IP address of the disk array because the disk array is connected to the server directly through optical fibers. In addition, change of IP addresses does not affect data read operations on the disk array. Generally, use the factory default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation.
Context
The 6140 disk array has two controllers. Each controller has two Ethernet ports. When changing the IP address of a controller, only Ethernet port 1 needs to be modified. Ethernet port 2 is reserved for maintenance. If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a disk array. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must be on the same network segment. If you have changed the IP address of the disk array on a different segment, you need to change the IP address of the corresponding Ethernet port nxge3 to ensure that both changed IP addresses are on the same network segment.
Procedure
Step 1 Connect the 6-pin mini DIN connector of the basic cable to the serial port connector of controller A. Figure 3-5 shows the disk array. Figure 3-5 Serial ports of the 6140 disk array
NOTE
Two serial port cables are attached to the pallet of each controller.
l l
One end is the 6-pin mini DIN connector, and the other end is the basic cable of the standard 9-pin serial port connector. Extended cables of the standard 9-pin serial port connector are attached to both ends.
Step 2 Connect the 9-pin serial extended cable from the 9-pin connector of the basic cable to the serial port connector of the PC.
Step 3 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on the PC. Step 4 In the Connection Description dialog box, enter a name for the new connection. Step 5 Choose the PC serial port that connects to the connector, for example, COM1. Step 6 Set the properties of the serial portaccording to Table 3-6. Then, click OK. Table 3-6 Setting properties of the serial port Property Bits per second Data bits Parity Stop bits Data stream control Value 38400 8 Null 1 Null
After the connection is complete, a physical connection between the PC and the 6140 disk array is set up. Step 7 Press Ctrl+Break. The serial port responses with a request so that the baud rate can be synchronized with that on the PC.
Set baud rate: press <space> within 5 seconds
NOTE
The serial ports on the disk array request that Break be accepted. Set the corresponding escape sequence for the terminal configuration, and then send the essential Break to the controller of the disk array. For instance, press Ctrl and Break at the same time to generate the Break character on certain terminals.
Step 8 Press the spacebar within five seconds. The serial port The serial port check the baud rate set up for the connection.
Baud rate set to 38400
Step 9 Press Ctrl+Break. The serial port responds with the following information:
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
Step 10 Press S. The system prompts you to enter the password.
CAUTION
S must be in upper case.
Enter Password to access Service Interface (60 sec timeout): - >
Step 11 Enter the password kra16wen, and then press Enter. Step 12 If the following information is displayed, type 2.
Service Interface Main Menu ============================== 1) Display IP Configuration 2) Change IP Configuration 3) Reset Storage Array (SYMbol) Password Q) Quit Menu Enter Selection:
Step 13 If the following information is displayed, type 1.

Select Ethernet Port ============================== 1) Ethernet Port: 0 2) Ethernet Port: 1 Q) Quit Enter Selection: 1
Step 14 If the following information is displayed, type n. The DHCP function is not used to configure the dynamic IP address for the port.
Configure using DHCP ? (Y/N): n
Step 15 If the following information is displayed, enter the IP address of controller A and its subnet mask.
NOTE
The subnet mask is optional.

Press '.' to clear the field; Press '-' to return to the previous field; Press <ENTER> and then ^D to quit (Keep Changes) Current Configuration New Configuration IP Address if1 : 192.168.128.101 IP-address Subnet Mask if1 : 255.255.255.0 <ENTER>
After the configuration, the system displays the information about the specified IP address. Step 16 If the following information is displayed, type 1.
Step 17 If the following information is displayed, type 1.

The IP address of the selected Ethernet port is displayed. Check whether the modified IP address is correct again. If the modified IP address is incorrect, perform operations Step 12 through Step 17 to configure the IP address of the controller again. Step 18 If the following information is displayed, enter Q to exit.
Issue 10 (2010-09-06)
3-33
Step 19 Perform Step 1 through Step 18 again to change the IP address of control B in the same way. Step 20 (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file.
NOTE
1. 2.
3.
Perform the following operations on the server to modify the /etc/inet/ipnodes file. # vi /etc/inet/ipnodes
l
----End
3-34
Issue 10 (2010-09-06)
4 Managing the M2000 Clients
4
About This Chapter
Context
l
Managing the M2000 Clients
This chapter 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 are authorized to install, upgrade, and uninstall the M2000 client are Windows users. They 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 section describes how to manage the file systems and disks on the M2000 clients. 4.2 Monitoring the Login Status of the M2000 Clients This section describes how to monitor the login status of the M2000 clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the preset maximum number of M2000 threads, you must force a user out to establish a new connection. 4.3 Setting the Number of Clients Accessible on a PC This section describes how to edit the configuration file on the M2000 client for setting the number of clients of the same version (excluding the LMTs that gain access to NEs through the M2000 proxy) that can be started on a PC. 4.4 Setting the Time Information on the M2000 Client This section describes how to set the time information on the M2000 client.
Issue 10 (2010-09-06)
4-1
4.1 Managing Files and Disks on M2000 Clients

This section 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 section 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. Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size of the initial version, that is, about 300 MB; T refers to the temporary space for saving patches, which is less than 20 MB; S refers to the size of mediation files, which ranges from 3 MB to 10 MB; N refers to the number of NE versions, which depends on the actual situation. Table 4-1 describes the parameters specified in the equations. Table 4-1 M2000 client software directory Directory client installation path 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 M2000 client installation path. The default path is C:\iManagerM2000Client. Refers to the directory for saving client programs. Refers to directory where executable files are located. 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 diagnosis tool.
M2000 client installation path\client \ext_runcfg M2000 client installation path\client\dtd
Refers to the directory where the files related to integrated components are located. Refers to the directory for saving the Dtd files.
4-2
Issue 10 (2010-09-06)
Directory M2000 client installation path\client\help M2000 client installation path\client \IDAPI32 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\client \update M2000 client installation path\client\cbb M2000 client installation path\client \configuration M2000 client installation path\client \features M2000 client installation path\client \plugins M2000 client installation path\uninstall M2000 client installation path\script M2000 client installation path\client\bin \run
Description Refers to the directory for saving the online help files. Refers to the directory for saving the localWS dynamic link libraries. 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 upgrade files. Stores the CBB files of the M2000 client. Stores the configuration files of the M2000 client. Stores the feature configuration files of the subsystems of the M2000 client. Stores the configuration files of the subsystems of the M2000 client as plug-ins. Refers to the directory for saving the uninstaller. Refers to the root directory of the iSStar script. Refers to the directory in which the files for configuring the startup parameters of the client and components are located.
Issue 10 (2010-09-06)
4-3
Directory M2000 client installation path\cau
Description Refers to the installation directory of the cau (Client Auto Upgrade) client software and the directory in which the version, document abstract, and group information about the M2000 client are located.
NOTE
l The cau(Client Auto Upgrade) client software
provides an upgrade detection mechanism that is based on the document abstract. It also compares the document abstract of the server with that of the client. If the document abstracts are not consistent, you need to upgrade the client.
l Based on the group information, the server groups
and packs all the client documents deployed on the server for the client to download, install, and upgrade. Based on the group information, the client also groups and packs all client files. Thus, when these files are being downloaded, they can be compared with those files grouped and packed by the server.
M2000 client installation path\jre M2000 client installation path\lib
Stores the Java virtual machine of the M2000. Stores the library files of M2000 client, remote notification client, script framework tool client and datamanager client.
4.1.2 Clearing the Disk Space of an M2000 Client

This section 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
4-4
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 Monitoring the Login Status of the M2000 Clients

This section describes how to monitor the login status of the M2000 clients (including the LMTs which access NEs through the M2000 proxy). When the number of login clients exceeds the preset maximum number of M2000 threads, you must force a user out to establish a new connection.
Prerequisite
Before monitoring the M2000 clients, ensure that you are authorized to monitor the users.
Procedure
Step 1 Start the M2000 client and log in to the M2000 server. Step 2 Choose Security > Monitor User Sessions. The Monitor User Sessions dialog box is displayed. Step 3 Click the Monitor User Sessions tab to monitor all the terminals connected to the M2000 system. Pay special attention to information such as login IP address and login time. Step 4 Click Refresh to refresh the session list. This step is optional. Step 5 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. The current user cannot force itself to exit.
----End
4.3 Setting the Number of Clients Accessible on a PC

This section describes how to edit the configuration file on the M2000 client for setting the number of clients of the same version (excluding the LMTs that gain access to 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 running properly.
Issue 10 (2010-09-06)
Context
Ideally, a maximum of 31 M2000 clients of the same version can be started on a PC. The number of clients of the same version connected to a PC depends on the configuration of the PC and that of the server connected to the PC. In the M2000 client installation directory\client\plugins\com.omc.cm\style\productstyle \com.swimap.corba\conf\communicate.xml file, the value of corba_portpool indicates 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 displays an Error message. You can set the maximum number of clients of the same version started on a PC by modifying the value of corba_portpool.
Procedure
Step 1 Open the communicate.xml file in the M2000 client installation path\client\plugins \com.omc.cm\style\productstyle\com.swimap.corba\conf directory. Step 2 Find the corba_portpool field, and then change the range of the ports as required.
<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE COMMINIDATA SYSTEM "commini.dtd"> <COMMINIDATA> <AREADESC areaname="communicate"> <DESC descname="communicate"> <PARAS> <PARA name="operation" value="modify"></PARA> <PARA name="corba_portpool" value="30500-30699"/> </PARAS> </DESC> </AREADESC> </COMMINIDATA>
NOTE
l l l
The ports after modification cannot exceed the range from 30500 to 30699. Ensure that the ports in the modified range on the firewall are enabled when you modify the port range. The ports may be used by other applications. Perform the following substeps to check the occupation of the ports. 1. Choose Start > Run. The Run dialog box is displayed. 2. Type cmd. Then, click OK. 3. In the displayed window, run the netstat -an command to check the occupation of the ports.
----End
4.4 Setting the Time Information on the M2000 Client

This section describes how to set the time information on the M2000 client. 4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client This section describes how to modify the date, time, and time zone on the M2000 client that is based on the Windows operating system. Modifying the date, time, and time zone on the M2000 client means modifying the date, time, and time zone of Windows. 4.4.2 Setting the NTP Service on the M2000 Client
4.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client
This section describes how to modify the date, time, and time zone on the M2000 client that is based on the Windows operating system. Modifying the date, time, and time zone on the M2000 client means modifying the date, time, and time zone of Windows.
Prerequisite
The Windows operating system is operational.
Procedure
Step 1 Open the Control Panel. This takes the Windows XP operating system as an example. Step 2 Double-click Date and Time. Step 3 In the Date and Time Properties dialog box, select the items to be modified. Item Hour Minute Second Operation Set the required hour on the Time tab page. Set the required minute on the Time tab page. Set the required second on the Time tab page.
Time Zone Click the Time Zone tab. On the Time Zone tab page, choose the local time zone from the drop-down list. Step 4 Click Apply. ----End
4.4.2 Setting the NTP Service on the M2000 Client

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
Issue 10 (2010-09-06)
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, Windows 2003, Windows 2008, Windows XP Professional or Windows Vista Business operating system.
Procedure
Step 1 Configure the M2000 client as the NTP client. Choose Start > Run. In the displayed Run dialog box, enter regedit to open the Registry Editor window. 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, it indicates that the value can be ignored and the registry need not be modified.
NOTE
For the operating systems of Windows 2003 or Windows 2008, In the registry, change the value of Enable under HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpServer to 0.
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 Restart the Windows Time service. Choose Start > Run. In the displayed Run dialog box, enter services.msc to open the Services window. Identify the Windows Time service and restart the service. Step 4 Check the NTP server specified by the PC. c:\>net time /querysntp
NOTE
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.
Step 5 Perform operations based on operating systems.

l l
If the M2000 client runs on Windows 2000 operating system, perform Step 6. If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vista operating system, perform Step 7 through Step 8.
Step 6 Run the following command to check the running status of the SNTP:
c:\>w32tm -once -v -test The system displays the host name of the connected NTP server, deviation between the local time and the NTP server time, and time cycle of NTP server roll. Step 7 Run the following command to manually synchronize the time: c:\>w32tm /resync Step 8 Run the following command to check the running status of the SNTP: c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly The system displays the following information, including the local time of the client and deviation of the local time from that on the NTP server.
Tracking 10.71.15.98 [10.71.15.98]. The current time is 2009-6-22 10:05:09 (local time). 10:05:09, +04.9881239s 10:05:11, +04.9814570s 10:05:13, +04.9740897s 10:05:15, +04.9589559s 10:05:17, +04.9449507s ...
In the system output, the first column displays the local time of the client, and the second column displays the deviation between the local time and the server time. + indicates that the client time is earlier than the server time. - indicates that the client time is later than the server time. You can press Ctrl+C to exit the browse window. ----End
Issue 10 (2010-09-06)
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 section 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 section 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 chapter describes how to manage the Sybase user that is required for the operation of the M2000. This chapter also describes how to change the password of the Sybase user. 5.4 Managing OM Users OM users operate and maintain the entire network or specified NEs through the M2000. The M2000 provides the user management function. By using this function, you can manage user information and user rights. You can also monitor user sessions and operations. This helps to prevent unauthorized operations and ensure system security.
Issue 10 (2010-09-06)
5-1
5.1 Types of M2000 Users

This section 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 Users NE users refer to the users accounts that can log in to and operate and maintain NEs through the LMT or WEB LCT. To use the LMT or WEB LCT to operate and maintain NEs (for example, in the case that NEs are not connected to or are disconnected from the M2000, you need to operate and maintain NEs as NE users. NE users can also perform operations such as troubleshooting at the near ends of NEs. 5.1.4 Principles of NM User Authorization This section 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 section 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. Table 5-1 describes the Solaris user accounts.
5-2
Issue 10 (2010-09-06)
Table 5-1 Solaris user accounts Account Name Usage Authority Group Shell Resoluti on Program Directory
root
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/bash 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 and omcsys m
/bin/bash
/opt/sybase
Issue 10 (2010-09-06)
5-3
Account Name
Usage
Authority
Group
Shell Resoluti on Program /bin/bash
Directory
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)
/export/home/ omc
ftpuser
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
/bin/bash
/export/home/ sysm
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 Users
NE users refer to the users accounts that can log in to and operate and maintain NEs through the LMT or WEB LCT. To use the LMT or WEB LCT to operate and maintain NEs (for example, in the case that NEs are not connected to or are disconnected from the M2000, you need to
operate and maintain NEs as NE users. NE users can also perform operations such as troubleshooting at the near ends of NEs.
Types of NE Users
NE users consist of local NE users and non-local NE users.
l
Local NE users refer to the users whose account, password, and authority are managed by NEs. The creation and modification of a local NE user are performed on the LMT. NEs provide several default local users.
CAUTION
NodeBs have only default local users because they do not have the BAM and cannot create any local user.
l
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 on the M2000.
Management of Mode 1 NE Users

Mode 1 NEs of centralized user management support local and non-local NE users. If an OM user is granted with the MML authority of a mode 1 NE, the OM user becomes a non-local user of this NE. You can log in to the M2000 as a non-local NE user to operate and maintain the mode 1 NEs. For details about mode 1 NEs, see NEs Corresponding to Different Centralized User Management Modes. The M2000 manages non-local users, which consist of OM user accounts and NE user accounts. Thus, non-local NE users have higher priority than local NE users. You can set whether to enable NE local users to log in to and manage NEs on the M2000.
Management of Mode 2 NE Users

Mode 2 NEs of centralized user management support only local NE users. For the list of mode 2 NEs, see NE Types. To perform centralized management on mode 2 NEs, you can create an NE User account for each local NE user (with the same user name and password) in the NE User Management window on the M2000 and correlate the accounts to the corresponding OM users. You can log in to the M2000 as a non-local OM user that is correlated to a local NE user to operate and maintain the mode 2 NEs.
NOTE
The information about the user account on the M2000 and that on the NE is independent from each other, and thus they cannot be automatically synchronized. You need to manually synchronize the information about the NE user on the M2000 according to the information about the local NE user.
Management of Optical Transmission NE Users

Optical transmission NEs support only local NE users. For details about optical transmission NEs, see NE Types. In the NE User Management window on M2000, you can create NE users for the optical transmission NEs. In the Main Topology window on the M2000, you can use a created or default
NE user as a parameter for creating an optical transmission NE and then log in to the NE to operate and maintain it.
5.1.4 Principles of NM User Authorization

This section 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 four default user groups: Administrators, Operators, Guests and SMManagers. 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. 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. 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 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. Modifying user validity by modifying the attributes of a user account
Locking status
5-6
Issue 10 (2010-09-06)
Privileges M2000 operation rights
Description 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.
Related Operations 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 section 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
It is recommended to use the default command groups provided by NEs. If you have to customize command groups, customize as few as possible. 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 section 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.
Issue 10 (2010-09-06)
5-7
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 section describes how to change the password of user root. 5.2.3 Changing the Password of User dbuser This section 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 section 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 User ftpuser This section describes how to change the password of user ftpuser when you log in to the system as user root. 5.2.6 Creating a Solaris User This section 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 section 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. Table 5-3 describes the Solaris user accounts.
5-8
Issue 10 (2010-09-06)
Table 5-3 Solaris user accounts Account Name Usage Authority Group Shell Resoluti on Program Directory
root
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/bash 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 and omcsys m
/bin/bash
/opt/sybase
Issue 10 (2010-09-06)
5-9
Account Name
Usage
Authority
Group
Shell Resoluti on Program /bin/bash
Directory
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)
/export/home/ omc
ftpuser
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
/bin/bash
/export/home/ sysm
5.2.2 Changing the Password of User root

This section 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 section 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 M2000 server as user root.
Procedure
Step 1 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 section 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 M2000 server as user root.
Context
NOTE
The provided password must meet the policy of minimum complexity. That is, the password comprises of at least 6 letters or digits, among which one digit or special character is included.
Procedure
Step 1 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 User ftpuser

This section describes how to change the password of user 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 the system as root.
Context
CAUTION
The special characters '"$ cannot be contained in the password of user ftpuser. To improve the password security, you are advised to use the following policies to set the password:
l l l l l l
The password length ranges from 8 to 30 characters. At least one uppercase is contained in the password. At least one lowercase is contained in the password. At least one digit is contained in the password. At least one special character is contained in the password. No user name is contained in the password.
Procedure
Step 1 If the M2000 services are running, stop them. Check the operation status of the M2000 services. For details, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. Step 2 Check whether the Sybase services are started. For details, see 14.2.1 How Do I Check Whether the Sybase Is Started?. If the Sybase services are not started, start them first. For details, see 14.2.2 How to Start the Sybase. If the Sybase services are started, perform Step 3. Step 3 Run the modify script to change the password of user ftpuser. 1. Run the modify script. The default installation directory of the M2000 server software is /opt/OMC.
# . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/config # ./modify.sh 2. 3. Choose 1--Single system > 4--Password of ftpuser. Based on the system prompt, enter the new password of user ftpuser twice.
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the new ftpuser password: Please Re-enter the password:
NOTE
l l
Enter p or P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. Enter q or Q to exit the modify script.
4.
When the system displays the following information, enter Y to apply the change.
NOTE
l l l l
Enter Q to exit the script without performing any operations. Enter R to return to Step 3.3. You can reconfigure the relevant parameters. Enter P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. You need to wait for about one minute if you run the modify script to change the password of user ftpuser.
5.
When the system displays the following information, it indicates that the change is successful.
If the system output contains failed, it indicates that the change fails. Contact Huawei technical support engineers for assistance. 6. When the system displays the function menu, enter q to exit.
Step 4 Check whether the Sybase services are started. For details, see 14.2.1 How Do I Check Whether the Sybase Is Started?. If the Sybase services are not started, start them first. For details, see 14.2.2 How to Start the Sybase. If the Sybase services are started, perform Step 5. Step 5 Start the M2000 services. For details, see 7.2.3 Starting the M2000 System Services. ----End
5.2.6 Creating a Solaris User

This section 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
For details of the useradd command, refer to M2000 Command Reference.
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 section 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 For details of the userdel command, refer to M2000 Command Reference.
NOTE
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 chapter describes how to manage the Sybase user that is required for the operation of the M2000. This chapter 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 section describes how to change the password of user sa. 5.3.3 Changing the Name of the Database Server This section describes how to change the name of the database server based on the actual requirements.
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 section describes how to change the password of user sa.
Prerequisite
You have logged in to the system as user root.
Issue 10 (2010-09-06)
5-15
Context
CAUTION
To improve the password security, you are advised to use the following policies to set the password:
l l
The valid password ranges from 8 to 30 characters. The special characters '"$ cannot be contained in the password. Instead, the password can contain only 0 to 9, a to z, A to Z, and special characters ~!@#%^&*()_-+=|\/<>,.;: []{}.
Procedure
Step 1 If the M2000 services are running, stop them. Check the operation status of the M2000 services. For details, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. Step 2 Check whether the Sybase services are started. For details, see 14.2.1 How Do I Check Whether the Sybase Is Started?. If the Sybase services are not started, start them first. For details, see 14.2.2 How to Start the Sybase. If the Sybase services are started, perform Step 3. Step 3 Run the modify script to change the password of user sa. 1. Run the modify script. The default installation directory of the M2000 server software is /opt/OMC. # . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/config # ./modify.sh 2. 3. Choose 1--Single system > 3--Database password. Based on the system prompt, enter the previous and new passwords of user sa.
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the old database superuser's password: Please input the new database superuser's password: Please Re-enter the password:
5-16
Issue 10 (2010-09-06)

NOTE
l l l l
Enter p or P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. Enter q or Q to exit the modify script. Press Enter. The default values in the system output are used. You need to enter the new password of user sa twice.
4.
When the system displays the following information, enter y to apply the change.
NOTE
l l l l
Enter Q to exit the script without performing any operations. Enter R to return to Step 3.3. You can reconfigure the relevant parameters. Enter P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. You need to wait for about 12 minutes if you run the modify script to change the password of user sa.
5.
If the system output contains failed, it indicates that the change fails. Contact Huawei technical support engineers for assistance. 6. When the function menu is displayed again, enter q to exit. Step 4 Start the M2000 services. For details, see 7.2.3 Starting the M2000 System Services. ----End
5.3.3 Changing the Name of the Database Server

This section describes how to change the name of the database server based on the actual requirements.
Prerequisite
Context
l
The name of the database server is stored in the system configuration files and the M2000 configuration files. By modifying the relevant configuration files, you can change the name of the database server. When the data is transferred between two M2000 servers, the database server names of the two servers must be consistent. You can change the database server name of one of the servers for implementing the data transfer.
Issue 10 (2010-09-06)

l l
This takes the change of the database server name from SYB to SYB1 as an example. The format of the database server name is SYB or SYBX where X is a numeral. For example, SYB, SYB2, and SYB3 are names of database servers.
Procedure
Step 1 If the M2000 services are running, stop them. Check the operation status of the M2000 services. For details, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. Step 2 Check whether the Sybase services are started. For details, see 14.2.1 How Do I Check Whether the Sybase Is Started?. If the Sybase services are not started, start them first. For details, see 14.2.2 How to Start the Sybase. If the Sybase services are started, perform Step 3. Step 3 Run the modify script to change the name of the database server. 1. Run the modify script. The default installation directory of the M2000 server software is /opt/OMC. # . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/config # ./modify.sh 2. 3. Choose 1--Single system > 2--Database password. Based on the system prompts, enter the previous and new name of the database server and the password of user sa.
-----------------------------------------------------------------Note: -- Enter key p/P to return pre-step -- Enter key q/Q to exit this tools -----------------------------------------------------------------Please input the old database server name[default SYB]: Please input the new database server name[default SYB]: Please input the database superuser's password:
NOTE
l l l
Enter p or P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. Enter q or Qto exit the modify script. Press Enter. The default values in the system output are used.
4.
When the system displays the following information, enter Y to apply the change.
5-18
Issue 10 (2010-09-06)

NOTE
l l l l
Enter Q to exit the script without performing any operations. Enter R to return to Step 3.3. You can reconfigure the relevant parameters. Enter P. The system displays the function menu of the modify script, prompting you to perform operations such as changing the IP address or user password. You need to wait for about 15 minutes if you run the modify script to change the IP address of the server.
5.
If the system output contains failed, it indicates that the change fails. Contact Huawei technical support engineers for assistance. 6. When the system displays the function menu again, enter q to exit. Step 4 Start the M2000 services. For details, see 7.2.3 Starting the M2000 System Services. ----End
5.4 Managing OM Users

OM users operate and maintain the entire network or specified NEs through the M2000. The M2000 provides the user management function. By using this function, you can manage user information and user rights. You can also monitor user sessions and operations. This helps to prevent unauthorized operations and ensure system security. Managing OM users, see M2000 User Management User Guide.
Issue 10 (2010-09-06)
5-19
6 Managing OSS System
6
About This Chapter
Managing OSS System
The M2000 provides the OSS management function. By using this function, you can viewing NE partitioning, managing the M2000 license, monitoring the M2000 server, integrated task management, check OMC status, collecting NM log files. 6.1 Monitoring the M2000 Server You can monitor the status (including the status of the service, process, hard disk and database) and the component information of the M2000 server as well as logs of the operations performed on the system monitor client. 6.2 Querying the System Logs of the M2000 This section introduces the M2000 system log. System logs record the operation of the M2000 system. System logs also record the files and data tables of various types of information, which can be queried by the M2000 administrator. 6.3 Collecting NM Log Files When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic information from the M2000 Server and Client through the FTP protocol. When the M2000 client or server cannot run properly, you can collect all the operational information from the M2000 client or server to locate faults. 6.4 Querying NE Subareas This section describes how to query NE subareas. An NE subarea refers to the M2000 server that manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed by different servers (subareas). On the M2000 client, you can query different NE subareas. 6.5 Managing the M2000 License M2000 licenses can restrict the number of manageable devices, and the availability duration of the M2000. You need to manage the licenses periodically. 6.6 Check OMC status OMC check is used to check the status of the M2000. This check also exports check reports in .html format. The device check enables you to find the hidden problems of devices. Thus, severe accidents are avoided and proper operation of current devices is ensured. 6.7 Integrated Task Management The M2000 provides the function of integrated management of scheduled tasks. Thus, you can browse information such as the task status and the progress. You can also create, modify, and
delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and save task result files to the client. 6.8 Reference of the OSS Management GUI This part describes the OSS management interfaces and related information such as the parameters used in the OSS management. This helps you understand the functions of OSS management easily.
6-2
Issue 10 (2010-09-06)
6.1 Monitoring the M2000 Server

You can monitor the status (including the status of the service, process, hard disk and database) and the component information of the M2000 server as well as logs of the operations performed on the system monitor client. Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. The system monitor browser consists of the following items:
l
Service Monitor: Monitors information about services, such as status and start time. Process Monitor: Monitors information about processes, such as number of used handles, CPU usage, memory usage, number of database connections, and number of threads.
Hard Disk Monitor: Monitors information about the disks in the system, such as total capacity, used space, free space, usage, and status.
Database Monitor: Monitors information about the databases in the system, such as status, space, usage, and log space.
Server Monitor: Monitors information about the services, such as status, operating system, memory capacity, CPU usage, and memory usage.
Component Information: Provides information about server components, such as name, version, and description.
6.1.1 Refreshing the Monitoring Information To know the latest running status of the M2000 server, you need to refresh the monitoring information. 6.1.2 Checking the CPU and Memory Usage Information About the M2000 Server This section describes how to check the CPU usage, memory capacity, and free memory space. When the CPU and memory status of the server is abnormal, you need to locate faults and log in to the server to rectify the faults in time. 6.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client This section describes how to check the disk usage information about the M2000 server through the system monitor browser of the M2000 client. 6.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000 Client This section describes how to check the database status through the M2000 client to know the usage of the databases. 6.1.5 Checking the M2000 Services This section describes how to check the M2000 services. When the M2000 services are not running normally, you need to locate faults and log in to the server to rectify the faults in time. 6.1.6 Checking the Status of the M2000 Processes
This section describes how to check the status of the M2000 processes. When the M2000 processes are not running normally, you need to locate faults and log in to the server to rectify the faults in time. 6.1.7 Viewing the Information about M2000 Server Components This function enables you to view the information of the components installed on the M2000 server that you log in to. 6.1.8 Saving the Monitoring Information For the convenience of future analysis of the information that is monitored at certain time, you can save the required monitoring information to the server. 6.1.9 Setting Alarm Thresholds for the M2000 This section describes how to set the alarm thresholds for the M2000. On the M2000 client, you can set the alarm thresholds to monitor the server status. The monitoring of system status consists of server monitoring, disk monitoring, databases monitoring, and service monitoring. if the value of a parameter exceeds the threshold, the system generates the corresponding alarm.
6.1.1 Refreshing the Monitoring Information

To know the latest running status of the M2000 server, you need to refresh the monitoring information.
Context
l
When you refresh the current tab page, only the information on this tab page is refreshed. The information on other tab pages is not refreshed. When you switch tab pages, the information on these tab pages are refreshed immediately. Therefore, when you switch tab pages, the information is refreshed at the same time.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab of the monitoring information to be refreshed. Step 3 click Refresh. ----End
6.1.2 Checking the CPU and Memory Usage Information About the M2000 Server
This section describes how to check the CPU usage, memory capacity, and free memory space. When the CPU and memory status of the server is abnormal, you need to locate faults and log in to the server to rectify the faults in time.
Prerequisite
l l
You have logged in to the M2000 client. You have the relevant operation rights.
6-4
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Server Monitor tab to check the performance of the M2000 server. See Figure 6-1. Figure 6-1 Server Monitor tab page
NOTE
In the CPU Usage (%) column and the Memory Usage (%) column, the green icon indicates that the CPU usage or memory usage of the corresponding server is normal; the red icon indicates that the CPU usage or memory usage of the corresponding server is abnormal. In the case that you have set the performance monitoring threshold for an item, the icon corresponding to the item changes from green to red when the value of the item reaches the threshold.
Step 3 (Optional) Click Save AS to save the monitoring data as a file. You can save the monitoring data in one of the following formats: .txt, .html, .xml, and .csv. ----End
6.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client
This section describes how to check the disk usage information about the M2000 server through the system monitor browser of the M2000 client.
Prerequisite
l l
Issue 10 (2010-09-06)
Context
Checking the disk usage information about the M2000 server requires only a few system resources and does not affect system operation.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Hard Disk Monitor tab to check disk usage information about the M2000 server. See Figure 6-2. Figure 6-2 Hard Disk Monitor tab page
NOTE
In the Status column, the green icon indicates that the usage of the corresponding disk is normal; the red icon indicates that the usage of the corresponding disk is abnormal. If the usage of a disk exceeds the preset threshold, the icon in this column changes from green to red.
6.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000 Client
This section describes how to check the database status through the M2000 client to know the usage of the databases.
6-6
Issue 10 (2010-09-06)
Prerequisite
l l
Context
This operation requires only a few system resources and does not affect system operation.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Database Monitor tab to check the database status of the M2000 server. See Figure 6-3. Figure 6-3 Database Monitor tab page
NOTE
In the Status column, the green icon indicates that the usage of the corresponding database is normal; the red icon indicates that the usage of the corresponding database is abnormal. If the usage of a database exceeds the preset threshold, the icon in this column changes from green to red.
6.1.5 Checking the M2000 Services

This section describes how to check the M2000 services. When the M2000 services are not running normally, you need to locate faults and log in to the server to rectify the faults in time.
Prerequisite
l l
Context
Checking the M2000 services on the M2000 client requires only a few system resources and does not affect system performance.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Service Monitor tab to check the M2000 services. See Figure 6-4. Figure 6-4 Service Monitor tab page
NOTE
In the Status column, the green icon indicates that the corresponding process is normal; the red icon indicates the corresponding process is abnormal.
6.1.6 Checking the Status of the M2000 Processes

This section describes how to check the status of the M2000 processes. When the M2000 processes are not running normally, you need to locate faults and log in to the server to rectify the faults in time.
Prerequisite
l l
Context
Checking the states of the M2000 processes on the M2000 client requires only a few system resources and does not affect system performance.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on the M2000 server. See Figure 6-5. Figure 6-5 Process Monitor tab page
6.1.7 Viewing the Information about M2000 Server Components

This function enables you to view the information of the components installed on the M2000 server that you log in to.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser from the main menu.
Step 2 In the System Monitor Browser window, click the Component Information tab. Step 3 View the information of all the installed components in Component Information tab. ----End
6.1.8 Saving the Monitoring Information

For the convenience of future analysis of the information that is monitored at certain time, you can save the required monitoring information to the server.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab of the monitoring information, and then click Save As.
NOTE
l l
The monitoring information can be saved in the format of TXT, HTML, CSV, or XML. The default format is XML.
Step 3 In the Save dialog box, select a storage path, enter the file name, and click Save. ----End
6.1.9 Setting Alarm Thresholds for the M2000

This section describes how to set the alarm thresholds for the M2000. On the M2000 client, you can set the alarm thresholds to monitor the server status. The monitoring of system status consists of server monitoring, disk monitoring, databases monitoring, and service monitoring. if the value of a parameter exceeds the threshold, the system generates the corresponding alarm.
Prerequisite
l l
Context
On the M2000, you can set the thresholds of certain parameters for the purpose of system monitoring. When the value of a parameter exceeds the threshold, the relevant record in the System Monitor Browser window is displayed in red. In addition, the corresponding alarm is generated.
Procedure
Step 1 In the main window, choose Monitor > System Monitor > Configurations. The System Monitor Settings dialog box is displayed, as show in Figure 6-6.
6-10
Issue 10 (2010-09-06)
Figure 6-6 System Monitor Settings dialog box
Step 2 Select a monitoring item to set the thresholds. For details about the parameters for monitoring the server, see Table 6-1.
Issue 10 (2010-09-06)
6-11
Table 6-1 Server Monitor Name Server Monitor Parameter Settings CPU sustained overload times (times) Description Description:
l
Settings Value: Value range: 10-400 Default value: 40
If the CPU usage is larger than Threshold for Alarm Generation of CPU used rate for consecutive x times, the M2000 generates a high CPU usage alarm. If the CPU usage is smaller than Threshold for Alarm Clearance of CPU used rate for consecutive x times, the M2000 generates an alarm, prompting that the high CPU usage alarm is cleared.
Server status refresh interval (seconds)
Description: Refresh interval for server monitoring, that is, the CPU usage is sampled every x seconds. Description: Used to set Threshold for Alarm Generation, Threshold for Alarm Clearance for the CPU usage alarm and whether to enable the bubble.
Value: Value range: 2-60. Default value: 15.
Server Monitor Threshold Settings
CPU used rate (%)
Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50.
6-12
Issue 10 (2010-09-06)
Name Memory used rate (%)
Description Used to set Threshold for Alarm Generation and Threshold for Alarm Clearance for the memory usage alarm.
l
Settings Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50.
If the memory usage is larger than Threshold for Alarm Generation of Memory used rate, the M2000 generates a high memory usage alarm. If the memory usage is smaller than Threshold for Alarm Clearance of Memory used rate, the M2000 generates an alarm, prompting that the high memory usage alarm is cleared. When the function of bubble information is enabled, if the server is faulty, the system displays a bubble information.
Table 6-2 describes the parameters for monitoring the disks of the server. Table 6-2 Hard Disk Monitor Name Disk Monitor Parameter Settings Hard disk status refresh interval (seconds) Description Description: Refresh interval for hard disk monitoring. Settings Value: Value range: 60-3600 Default value: 60
Issue 10 (2010-09-06)
6-13
Name Disk Monitor Threshold Settings Default value setting (%)
Description Description: All default thresholds of hard disk usage on the M2000 server.
l
Settings Value: Value range: 1-99 Default value:

l l l l
Warning: 60 Minor: 70 Major: 80 Critical: 90
When the hard disk usage is larger than Threshold for Alarm Generation of an alarm severity level, the M2000 generates a high hard disk usage alarm of this severity level. When the hard disk usage is smaller than Threshold for Alarm Clearance of an alarm severity level, the M2000 clears the high hard disk usage alarm of this severity level. When the function of bubble information is enabled, if the hard disk is faulty, the system displays a bubble information.
6-14
Issue 10 (2010-09-06)
Name Advanced Setting (%)
Description Description: Thresholds of all the hard disk usage on the M2000 server.
l
Settings Value: Value range: 1-99
l If you select
NOTE Default Value, the M2000 uses the threshold specified in Default Value Setting.
l If you select
Customize Value, the M2000 uses customized thresholds of alarms.
Issue 10 (2010-09-06)
6-15
Table 6-3 describes the parameters for monitoring the database of the server. Table 6-3 Database Monitor Name Database Monitor Parameter Settings Database status refresh interval (seconds) Description Description: Interval of database refreshing. Settings Value: Value range: 300-3600 Default value: 300 Database Monitor Threshold Settings Default Value Setting (%) Description: All default thresholds of database usage on the M2000 server.
l
Value: Value range: 1-100 Default value:

l l l l
When the database usage is larger than Threshold of an alarm severity level, the M2000 generates a high database usage alarm of this severity level. When the database usage is smaller than Threshold of an alarm severity level, the M2000 clears the high database usage alarm of this severity level.
6-16
Issue 10 (2010-09-06)
Description Description: Thresholds for the database usage alarms of different severities. You need to set these thresholds separately for each database on the M2000 server.
l
Settings Setting method: Set the following parameters for each database:
l
Default Value: use default thresholds for the database usage alarms of different severities. Customize Value: customize thresholds for the database usage alarms of different severities. Value range: 1-100 Default value:

Disabled Monitoring: Disable the database monitoring.
Table 6-4 describes the parameters for monitoring the server services. Table 6-4 Service Monitor Name Services Monitor Parameter Settings Service status refresh interval (seconds) Description Description: Interval of service refreshing. Settings Value: Value range: 60-3600 Default value: 60
Issue 10 (2010-09-06)
6-17
Name Service Monitor Screen Tip Settings Default Group
Description Description: Set whether to display the service status at the lower right corner of the M2000 system monitor client by or .
l If all the monitored
Settings Setting method: Select a service from the Service Name drop-down list. Select enable or disable in the corresponding Show Screen Tips dropdown list.
NOTE services are running, displayed. is
l if a monitored
service is stopped, is displayed.

l You can double-
click or to access the Service Monitor tab.
Step 3 Click OK. ----End
6.2 Querying the System Logs of the M2000

This section introduces the M2000 system log. System logs record the operation of the M2000 system. System logs also record the files and data tables of various types of information, which can be queried by the M2000 administrator.
Prerequisite
l l
Context
l
Querying the system logs requires only a few system resources and does not affect the system operation. System logs are saved in the following path on the M2000 server:
/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
6-18
If the log data in the database exceeds a preset threshold, the system exports the log data to a specific path.
l
The contents of the system logs:
Level: Risk, Minor, Info. System logs can be categorized into three levels in descending order. Source: Sources, such as FaultService, ServiceAdmin, and MediationService, are identified by the logos of the subsystems in the M2000 system. Time: 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: Provides the basic information on system operation, such as the information about service startup. Details: Provides the details on system operation.
Procedure
Step 1 Choose System > Log Management > Query System Logs. The Filter dialog box is displayed. Step 2 Set the filtering conditions in the Filter dialog box, and then click OK. The Query System Logs window is displayed. Step 3 Double-click a record to view the detailed information. In the displayed Log Details dialog box, the system displays details about a successful operation or a failed operation. Step 4 Right-click a record and save the specified system logs as a file. You can save the system logs in one of the following formats: .txt, .html, .xls, .csv, and .pdf. ----End
6.3 Collecting NM Log Files

When the M2000 system fails, you can run the diagnostic tool to collect all the related diagnostic information from the M2000 Server and Client through the FTP protocol. When the M2000 client or server cannot run properly, you can collect all the operational information from the M2000 client or server to locate faults.
Context
By using this information, you can locate faults. The collected information includes:
l l
Trace files on the client, for example, Client_DebugTrace. Java virtual machine thread stack and lock state in client, for example, Client_ThreadStackDump.txt Trace files on the server, for example, iMAP.root.trace (to store the current trace files) and imap_stacks.20070206.170237.trace (to store the historical trace files collected before the NM log files) Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack File of alarm NE synchronization number, for example, FMSyncNo The pstack file, for example, imap_stacks.20070207.155817.trace.
l l l
Issue 10 (2010-09-06)

l
Information about the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, and SYBLog.20070206.171040.zip.
By default, the collected files are saved in M2000 client\client\diagnosis\collected files. You can change the save path.
l
The information collection progress is displayed in the Collection Details area of the Log Information Collector window. The M2000 diagnostic tool automatically collects diagnostic information from the client and then from the server.
Procedure
Step 1 Choose Programs > iManager M2000 Client > M2000 Log Information Collector. The Log Information Collector window is displayed. Step 2 In the Port Select window, select the M2000 client from which you need to collect information, and then click OK. If you have opened multiple M2000 clients concurrently, all the open clients are displayed in a list in the Port Select window. By performing this step, you can specify the client from which the diagnostic information is collected.
TIP
By comparing whether the process IDs in the PID column of the list with the progress ID of the target client, you can determine the client from which you will collect the diagnostic information. 1. Choose Start > Run. The Run dialog box is displayed. 2. Type taskmgr, and then click OK. The Windows Task Manager dialog box is displayed. 3. Click the Processes tab. 4. Choose View > Select Columns. The Select Columns dialog box is displayed. 5. Select the PID (Process Identifiers) check box, and then click OK. 6. Click the Applications tab. 7. Right-click the M2000 client to be viewed, and then choose Go To Process from the shortcut menu. 8. In the Port Select window, select the column where the value of PID is the same as the value displayed in the PID column.
Step 3 Configure the FTP server. 1. 2. 3. Enter the IP address of the M2000 server. Enter the port number. Enter the FTP user name and password for logging in to the target server.
Step 4 Select the information to be collected. For details, see Parameters for Collecting NM Logs Parameters.
l
To collect the trace files on the client, trace files on the server, core files on the server, or trace files on the LMT, you need to set Start Time and End Time to collect the information within the specified time range. To collect alarm localization information, you need to enter the name of the NE whose alarm localization information needs to be collected in NE Name.
Step 5 Set the folder for saving the diagnostic information. The collected files are saved under M2000 Client Installation Directory\client\diagnosis \collected files. You can modify the directory for saving collected files.
Step 6 Click Collect to collect the diagnostic information.

l
If you click Stop when collecting the diagnostic information from a client, do not stop the progress of collecting information from the client. If you click Stop when collecting the diagnostic information from the M2000 server, the diagnostic information about the server cannot be obtained. To view the collected diagnostic information, you can click Browse to navigate the directory of the collected files.
----End
6.4 Querying NE Subareas

This section describes how to query NE subareas. An NE subarea refers to the M2000 server that manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed by different servers (subareas). On the M2000 client, you can query different NE subareas.
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Configuration > Query NE SubArea to open the Query NE Subarea window. Step 2 Select a query condition, and then click Query. You can query NE subareas based on NE subareas or NE names.
l
Querying NE subareas based on NE subareas: In the Query Result dialog box, the NE distributions and NE information such as NE types, NE names, and NE versions on the selected NE subarea are displayed. In the Statistic dialog box, the subarea information such as host names, IP addresses, and database instance names are displayed. Querying NE subareas based on NE names: In the Query Result dialog box, the NE distributions and NE information such as NE types, NE names, and NE versions on the selected NE subarea are displayed. In the Statistic dialog box, the subarea information such as host names, IP addresses, and database instance names are displayed.
NOTE
You can click Save to save the query results as a file.
For the detailed parameter description, see 6.8.3 Parameters for the NE Partitioning Information. ----End
6.5 Managing the M2000 License

M2000 licenses can restrict the number of manageable devices, and the availability duration of the M2000. You need to manage the licenses periodically. 6.5.1 Querying the M2000 License This topic describes how to query the license file on the M2000 server through the M2000 client. 6.5.2 Updating the M2000 License
This section describes how to replace the M2000 license file on the M2000 server through the client.
6.5.1 Querying the M2000 License

This topic describes how to query the license file on the M2000 server through the M2000 client.
Procedure
Step 1 Choose Help > License Information from the main menu. Step 2 In the License Information dialog box, query the license information about resources and functions on the Resource control item and Function control item tabs. ----End
6.5.2 Updating the M2000 License

This section describes how to replace the M2000 license file on the M2000 server through the client.
Prerequisite
When updating a license, delete the license files that are not in use from the server directories license and licensebak, and then update the license.
Context
l l l
The type of the license applied for must be consistent with the version type. Before the licenses expire, the M2000 displays a warning periodically. The valid time for the license that is uniformly used in M2000 contains two fields: Expiry (Days) and End Time. If both the fields exist, the value of Expiry(Days) is valid.
Procedure
Step 1 Choose Help > License Information from the main menu. Step 2 In the License Information dialog box, click Update License. Step 3 In the Open dialog box, select the new license file, and then click Open. Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click OK. ----End
6.6 Check OMC status

OMC check is used to check the status of the M2000. This check also exports check reports in .html format. The device check enables you to find the hidden problems of devices. Thus, severe accidents are avoided and proper operation of current devices is ensured.
Prerequisite
l l
You have logged in to the M2000 successfully. You are authorized to perform associated operations.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Click New or double-click OMC Check node. Step 3 In the displayed New Task dialog box, set the basic information of the task. 1. 2. In the Task Name field, enter the name of the task. From the Run Type drop-down list, select Once or Period.
Step 4 Click Next. Step 5 Then, set the start time of the task. To set the start time of the task, perform the following operations:
l l l
In the Start Time field, enter the start time. Click Click
NOTE
or
to adjust the time.
. In the displayed Date/Time Selection dialog box, set the start time.
The Start Time must be later than the current system time.
Step 6 Perform different operations based on task types. Task Type Steps
One-time task Perform Step 7. Periodic task In Period and Run Times fields, enter the associated information. Then, perform Step 7.
Step 7 Click Next. Then, set the information about device check. Step 8 Click Finish. The progress bar displays the progress of file upload. After the upload is complete, the new device check task is displayed on the task list. ----End
6.7 Integrated Task Management

The M2000 provides the function of integrated management of scheduled tasks. Thus, you can browse information such as the task status and the progress. You can also create, modify, and delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, and save task result files to the client. 6.7.1 Basic Knowledge
The integrated task management integrates the concepts such as types of integrated tasks, task scheduling parameters, states of timing tasks. The knowledge of integrated task management helps you perform the operations related to the integrated task management. 6.7.2 Customizing the Interface for Managing Timing Tasks This describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks meeting the condition in the task list. 6.7.3 Creating a User Timing Task This section describes how to create a user timing task. Parameter setting varies according to different tasks. 6.7.4 Modifying a Timing Task This section describes how to modify the attributes of a user timing task or a system timing task. 6.7.5 Managing Timing Tasks User timing tasks refer to those timing tasks managed by the user. The user can delete, suspend, resume, cancel, terminate, and roll back user timing tasks. 6.7.6 Browsing the Information of Timing Tasks In the M2000, you can browse information about timing tasks such as the task name, user name, process, and execution result according to your own permissions. 6.7.7 Viewing the Task Execution You can view the last execution results of a timing task. 6.7.8 Downloading Result Files This describes how to download the results of timing tasks. You can save the results of timing tasks on the server to the local client in .txt format. 6.7.9 Technical Specifications of Centralized Task Management The technical specifications of centralized task management refer to the limitations on the centralized task management.
6.7.1 Basic Knowledge

The integrated task management integrates the concepts such as types of integrated tasks, task scheduling parameters, states of timing tasks. The knowledge of integrated task management helps you perform the operations related to the integrated task management.
Types of Integrated Tasks

The M2000 divides timing tasks into different types according to execution periods, functions, and task features.
Tasks Grouped According to Execution Periods

According to the execution periods of tasks, the M2000 divides the managed timing tasks into two types, that is, one-time tasks and periodic tasks. Table 6-5 provides the meaning of each task type.
6-24
Issue 10 (2010-09-06)
Table 6-5 Tasks grouped according to execution periods Types of Integrated Tasks Once Period Description Refers to a task that is performed only once at a specific time. Refers to a task that is performed periodically since a specific time.
Tasks Grouped According to Functions

According to the functions of tasks, the M2000 divides the managed timing tasks into nine types, that is, database capacity management tasks, file interface tasks, NE Information Collector (NIC) tasks, synchronization tasks, backup tasks, report tasks, CME tasks, network health check tasks, and other tasks. Table 6-6 provides the meaning of each task type.
NOTE
l l
Only BSC6000, BSC6900GSM, BSC6900UMTS, BSC6900GU, RNCs and NodeBs support CME tasks. CME tasks are available only after you install the CME software that maps with the NE version. Network health check tasks are available only after you purchase and install the relevant components.
Table 6-6 Tasks grouped according to functions Types of Integrated Tasks Database capacity management Description The system periodically deletes the data that reaches the specified Save Days from the database. Through database capacity management tasks, the database capability is maintained in a proper range to avoid database faults caused by large amount of data. By default, Save Days is set to the maximum value, that is, 90. The custom value cannot exceed 90. The databases that can be managed consists of the operation log database, system log database, security log management database, NE operation log database, NE security log database, alarm database, and performance database. File interface Various types of data can be periodically exported to a specified directory on the server. Through this function, you can save the data outside the system. The exported data is still saved in the database. The exported data consists of performance data, configuration data, NE license allocation information, NE operation logs, NE security logs, NE inventory data, alarm data, network management operation logs, network management system logs, and network management security logs.
Issue 10 (2010-09-06)
6-25
Types of Integrated Tasks NIC
Description NIC tasks provide NE data to the Nastar for performance analysis, configuration data query and check, uplink interference analysis, and neighboring cell analysis.
l
2G/3G neighboring cells optimization: collecting information about neighboring GSM cells for analyzing the relation between neighboring 3G cells. CHR data collection: provides CHR data to the Nastar for abnormal calls analysis. GSM MR data collection: provides MR data to the performance analysis tool for network optimization analysis. NIC configuration export: provides NE configuration data to the Nastar for NE configuration data query and check. RTWP data collection: provides NodeB interference data to the Nastar. Deamon collection: provides the Nastar with various types of data, such as the interference data, co-channel neighboring cell optimization data, complaint handling data of CDMA networks and the co-channel neighboring cell optimization data and coverage analysis data of UMTS networks. NE basic information export: provides NE basic information to the Nastar. Uplink frequency scanning: provides uplink frequency data to the Nastar for uplink interference analysis. Neighboring cell optimization: Provides neighboring cell optimization data to the Nastar for neighboring cell analysis.
6-26
Issue 10 (2010-09-06)
Types of Integrated Tasks Others
Description The other tasks consist of MML script tasks, PRS timing tasks, dual-home management tasks, alarm timing acknowledgement tasks, NE license sharing management tasks, NE software timing download tasks, and HSL script tasks .
l
MML script: After an MML script is configured, the M2000 can issue the commands contained in the script in batches. You need not manually issue the commands one by one. PRS timing task: You can set PRS timing tasks for the performance tables that you require on the M2000. The performance data is collected periodically to generate performance tables. Dual-home management: The system checks the data of dual-home NE pairs periodically or on schedule so that you can check whether the data is consistent. Thus, you can ensure that an softswitch can take over some or all data on the other softswitch after dual-home switchover. PM object synchronization: Maintains the data consistency between the PM objects on the M2000 and the actual NE objects by synchronizing NE objects regularly. Alarm timing acknowledgement: Helps you minimize operations by periodically acknowledging the faults or event alarms that meet the user-defined conditions. NE software timing download: enables you to specify an interval or the time to download NE mediation software from the M2000 server to a specified NE. In this case, NE version files can be delivered to the NE on time. HSL script: By running the preset HSL scripts, you can perform operations such as modifying NE parameters and obtaining alarm data. NE upgrade log export: Exports NE upgrade logs to the specified directory on the server periodically or on schedule. Upgrade Checking: After an NE is upgraded, you can use this function to verify whether the NE is successfully upgraded by collecting some KPIs.
Synchronization
Certain data may be missing due to reasons such as communication interruption. The synchronization function enables the M2000 to obtain the latest data from NEs. Through the synchronization function, the NE configuration data, NE logs, NE inventory data, and alarm timing data can be synchronized.
Issue 10 (2010-09-06)
6-27
Types of Integrated Tasks Backup
Description The M2000 allows you to save the server data and NE data as backup files to a specified directory on the server. The saved system data and NE data can be used to restore the system and NEs in case of missing data or abnormality of the system and NEs. Backup tasks consist of NE timing backups and server timing backups. The data that can be backed up on the M2000 consists of configuration data and log data. The system files and operating system cannot be backed up.
Report
The file export function enables you to periodically export various types of data as files to a specified directory of the server. By using this function, you can save the data outside the system. The exported data is still saved in the database. The reports that can be exported are RAN reports.
CME
CME tasks are divided into the following types:

l
CME Upload: After you select configuration data of NEs, this task enables you to specify an interval or the time to upload the data to the CME server. In this case, the CME can obtain the latest data of the NEs and configure the data. Cell Parameters Compare: compares the parameters in the Current area with the default parameters in the CME configuration template and then exports the results to the specified path. Cell Consistency Check: checks that the data in the Current area complies with the selected check rules. Currently, both unidirectional neighboring cell check rules and cell consistency check rules are provided. Current Area Export: exports the data in the Current area for Northbound to facilitate you manage the Current area.
Network health check
The network health check task checks the status of NE devices and the M2000, the performance of NE devices, and the alarm information. The health check report is generated in .html format. Through the network health check, you can detect the hidden problems of devices in time. Thus, severe accidents are avoided and proper operation of current devices is ensured. For details, see the Help related to network health check.
6-28
Issue 10 (2010-09-06)
Tasks Grouped According to Task Features

According to different task features, the M2000 divides the managed tasks into two types, that is, system timing tasks and user timing tasks. Table 6-7 provides the meaning of each task type. Table 6-7 Tasks grouped according to task features Types of Integrated Tasks System timing tasks Description System timing tasks are the tasks required for the normal operation of the M2000 system. They consist of database capacity management tasks, NIC tasks, synchronization tasks, file interface tasks, alarm timing acknowledgement tasks, and backup tasks (excluding NE backup tasks). For details, see System Timing Tasks. User timing tasks are the user-defined tasks created to meet the requirements of network maintenance. User timing tasks consist of MML script tasks, PRS timing tasks, uplink frequency scanning tasks, dual-home management tasks, NE software timing download tasks, NE timing backup tasks, configuration report export tasks, HSL script tasks, NE upgrade log export tasks, neighboring cell optimization tasks, CME tasks, and network health check tasks. For details, see User Timing Tasks.
User timing task
System Timing Tasks

A system timing task is created during the installation or upgrade of the M2000 system. The Creator of a system timing task is omc. System timing tasks consist of database capacity management tasks, some NIC tasks, synchronization tasks, file interface tasks, alarm timing acknowledgement tasks, and backup tasks (excluding NE backup tasks). The M2000 uses
NOTE
to identify system timing tasks.
l l l
Only users in the administrator group can manage and view system timing tasks. System timing tasks cannot be copied. Only some parameters of system timing tasks can be modified. These parameters, however, cannot be deleted. System timing tasks consist of multiple types of tasks. Database capacity management tasks cannot be suspended or canceled while synchronization tasks and backup tasks can be suspended or canceled. You can also set the time to suspend or cancel synchronization tasks or backup tasks.
For details about system timing tasks, see Table 6-8. Table 6-8 Description of system timing tasks Task Type Database capacity management Task Name Performance data NE operation logs Remarks For details, see 6.8.12 Parameters for Modifying Database Capacity.
Issue 10 (2010-09-06)
6-29
Task Type
Task Name NE security logs Alarm data NM Operation Log Dump NM System Log Dump NM Security Log Dump
Remarks
File interface
Performance data export Configuration data export NodeB License Data Export NE operation log export NE system log export NE security log export NE inventory data export Alarm data export NM Operation Log Export NM System Log Export NM Security Log Export
For details, see 6.8.13 Parameters for Modifying File interface Task and 6.8.11 Parameters for Setting the Common Information About Timing Tasks.
NIC
CHR data collection EAM export
For details, see Modifying a CHR Data Collection Task. For details, see 6.8.15 Parameters for Modifying NE Basic Information Export Task. For details, see Parameters for Modifying the Export of NIC CMExport Data. For details, see 6.8.16 Parameters for Modifying Alarm Timing Acknowledgement.
NIC configuration export Others Alarm timing acknowledgement
6-30
Issue 10 (2010-09-06)
Task Type
Task Name Performance object synchronization
Remarks For details, see 6.8.11 Parameters for Setting the Common Information About Timing Tasks. For details, see 6.8.14 Parameters for Modifying Synchronization task and 6.8.11 Parameters for Setting the Common Information About Timing Tasks.
Synchronization
NE configuration data synchronization NE log synchronization NE inventory data synchronization Alarm timing synchronization NE upgrade log synchronization Maintance Mode synchronization
Backup
Server timing backup
For details, see 6.8.17 Parameters for Modifying Data Backup Task.
User Timing Tasks

A user timing task is the custom task created to meet the requirements of network maintenance. User timing tasks consist of MML script tasks, PRS timing tasks, uplink frequency scanning tasks, dual-home management tasks, NE software timing download tasks, NE timing backup tasks, configuration report export tasks, iSStar script tasks, neighboring cell optimization tasks, CME tasks, and network health check tasks.
l l
You can create, modify, delete, copy, suspend, or restore user timing tasks. The M2000 uses to identify user timing tasks.
For details about user timing tasks, see Table 6-9.

NOTE
l l
Only BSC6000, BSC6900GSM, BSC6900UMTS, BSC6900GU, RNCs and NodeBs support CME tasks. CME tasks are available only after you install the CME software that maps with the NE version. Network health check tasks are available only after you purchase and install the relevant components.
Issue 10 (2010-09-06)
6-31
Table 6-9 Description of user timing tasks Task Type Backup Task Name NE timing backup Description To store NE data, you can regularly save NE data as backup files to a specified directory on the server. Thus, data loss can be avoided. After any error occurs on NEs, you can restore the data of NEs. You can back up all NEs on the entire network, the NEs of a certain type, or only some NEs. You can set the RAN report export task on the M2000 to export the RAN report of a specified NE to a specified directory on the server. Provides uplink frequency data to the Nastar for uplink interference analysis. Provides neighboring cell optimization data to the Nastar for neighboring cell analysis. You can run an MML script based on the interval or based on the time to issue commands in the script in batches. Thus, you need not manually issue the commands one by one. You can set PRS timing tasks for the performance tables that you require on the M2000. The performance data is collected periodically to generate performance tables. After you set a specified interval or a time to download NE mediation software from the M2000 server to specified NEs, NE versions can be delivered to NEs in time. Remarks For details, see 6.8.17 Parameters for Modifying Data Backup Task.
Report
RAN report export
For details, see 6.8.19 Parameters for Creating/ Modifying/Copying RAN Report Task. For details, see Parameters for Creating a Task of Collecting the Uplink ARFCN Data. For details, see Creating a Data Collection Task for Neighbor Cell Optimization. For details, see 6.8.18 Parameters for Creating/ Modifying/Copying MML Command Script.
NIC
Uplink frequency scanning task Neighboring cell optimization
Others
MML script
PRS timing task
For details, see 6.8.20 Parameters for Creating, Viewing, or Modifying a Scheduled Report Task.
NE software timing download
For details, see 6.8.23 Parameters for Creating/ Modifying/Copying Software Download.
6-32
Issue 10 (2010-09-06)
Task Type
Task Name Dual-home management task
Description The system checks the data of dual home pair NE periodically or on schedule so that you can determine whether the data is consistent. Thus, you can ensure that an softswitch can take over some or all data on the other softswitch. By running the preset HSL scripts, you can perform operations such as modifying NE parameters and obtaining alarm data. After an NE is upgraded, you can use this function to verify whether the NE is successfully upgraded by collecting some KPIs. Exports NE upgrade logs to the specified directory of the server periodically or on schedule.
Remarks For details, see 6.8.24 Parameters for Creating/ Modifying/Copying Dual-Home Management.
iSStar script task
For details, see 6.8.25 Parameters for Creating/ Modifying/Copying iSStar Script. For details, see Parameters for Creating an NE Upgrade Verification Task. For details, see 6.8.26 Parameters for Creating/ Modifying/Copying the Export of NE Upgrade Log. For details, see 6.8.27 Parameters for Creating/ Modifying/Copying a CME Upload Task.
Upgrade Checking
File interface
NE upgrade log export
CME
CME Upload
After you set a specified interval or a time to upload the selected NE configuration data to the CME server side, the CME can obtain the latest NE data for data configuration. Only RNCs and NodeBs support CME upload tasks. Compares the parameters in the Current area with the default parameters in the CME configuration template and then exports the results to the specified path. Checks that the data in the Current area complies with the selected check rules. Currently, both unidirectional neighboring cell check rules and cell consistency check rules are provided.
Cell Parameters Compare
For details, see 6.8.28 Parameters for Creating/ Modifying/Copying Cell Parameters Compare Task. For details, see 6.8.29 Parameters for Creating/ Modifying/Copying Cell Consistency Check Task.
Cell Consistency Check
Issue 10 (2010-09-06)
6-33
Task Type
Task Name Current Area Export
Description Exports the data in the Current area for Northbound to help you manage the Current area.
Remarks For details, see 6.8.30 Parameters for Creating/ Modifying/Copying a CME Current Area Export Task. For details, see the Help related to network health check.
Network health check
The network health check enables you to check the NE device, check alarms, check performance, and compare result files. The network health check enables you to find the hidden problems of devices. Thus, severe accidents are avoided and proper operation of current devices is ensured. For details, see the Help related to network health check.
Task Scheduling Parameters

The task scheduling parameters are the parameters related to the task execution type, task start time, task execution period, and execution times. Table 6-10 describes the task scheduling parameters. Table 6-10 Description of the task description parameters Parameter Task Type Description According to different task execution periods, the M2000 divides the execution types of the managed timing tasks into two types: periodic execution and one-time execution. The execution type of the system timing tasks is periodic execution. The execution type of user timing tasks can be periodic execution or one-time execution. Indicates start time of periodic tasks and one-time tasks set during task creation, including date and time. The start time of tasks should be later than the current server time.
l
Start Time
Period
Interval between periodic tasks. It has two enlistments: unit and duration. The task execution period can be represented by month, week, day, hour, and minute. Second is not supported. The period interval range is as follows: 1 to 12 for month, 1 to 52 for week, 1 to 366 for day, 1 to 366x24 for hour and 1 to 366x24x60 for minute.
6-34
Issue 10 (2010-09-06)
Parameter Run Times
Description Indicates execution times of a periodic task. The execution times range from 0 to 65535. The value 0 indicates no limit.
NOTE
Assume that the scheduling parameters of the entire network NE backup task are:
l l l l
Execution type = Periodicity Start time = 2006-10-21 09:07:28 Execution period = 1 day Period execution times = 0
The preceding information indicates that the system executes the entire network NE backup task at 09:07:28 every day from 09:07:28 on Oct. 21, 2006.
States of a Timing Task

A timing task has four states: idle, running, suspend, archived and finished. The states of a scheduled task change with different operations. For details, see Figure 6-7. Figure 6-7 State transition of a scheduled task
Start Creating a timing task Idle
Suspend a timing task
Restore a timing task
Scheduling
Cancel Finish Yes
Running
Deleting a timing task
Suspend
Terminate a CME task
Terminate a CME task
Another Scheduling? Scheduling No
D tim ele in ting g ta sk
ete Del task E M aC
Archived
Ter a C minate ME task

Finished
Deleting a timing task End
State transition of a scheduled task is as follows:

l
A scheduled task is in the idle state after it is initially created.

Issue 10 (2010-09-06)

l l l l l
An idle task is changed to the running state after being scheduled. An idle task is changed to the suspended state after being suspended. A running task is changed to the idle state after being cancelled. A suspended task is changed to the idle state after being resumed. If a task need not be scheduled after being performed, it is in the finished state. If it needs to be scheduled again, it returns to the idle state.
If a CME task is in the finished state and you terminate the task, the CME task is in the archiving state. When a timing task is in the idle, suspended, or finished state and a CME task is in the archiving state, you can delete the timing task.
6.7.2 Customizing the Interface for Managing Timing Tasks

This describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks meeting the condition in the task list.
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window perform different operations according to different customized requirement. Customized Requirement Operation
Customize the navigation tree 1. Right-click in the navigation tree and choose Filter Type from the shortcut menu. The Filter Type dialog box is displayed. 2. Select the timing task type to be displayed. By default, all the timing task types that the current user is authorized to browse are displayed. Customize the task list 1. Right-click the task list and select Filter Task. The Task Filter Setting dialog box is displayed. 2. Set the User Name, Category, Task State, and Last Run Result as the filtering conditions. For detailed parameter description, refer to 6.8.10 Parameters for Setting Task Filter Conditions. Step 3 Click OK. ----End
6.7.3 Creating a User Timing Task

This section describes how to create a user timing task. Parameter setting varies according to different tasks.
Prerequisite
You have logged in to the M2000 client successfully.
Context
l
To quickly create a task, you can copy a multi-instance user timing task of user and then modify its parameters. The instance quantity of the timing tasks of a specific type is restricted. If the instance quantity of the existing timing tasks of a type reaches the maximum, you cannot create or copy a timing task of this type.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, create a user timing task. You can create a user timing task by using one of the following methods:
l l
In general, click New. To quickly create a task of the specified type, double-click a user timing task in the Task Type navigation tree. To quickly create a multi-instance user timing task whose parameter settings are similar to those of the specified task, select the specified multi-instance user timing task, and then click Copy.
NOTE
l l
If the Copy button is gray, it indicates that the user timing task does not support multiple instances or the number of instances reaches the maximum. When you create a task, the task types for which the number of user timing task instances reaches the maximum are not displayed in the Task Type navigation tree.
Step 3 In the New Task or Copy Task dialog box, set the parameters of the created user timing task. Option Parameter Description Setting
Issue 10 (2010-09-06)
6-37
Option Common Parameters
Description 1. Set Task Name, Task Type, and Run Type. Do as follows:
l l
Task Name: Enter the task name in Task Name. Task Type: Select the type of the task to be created in the Task Type navigation tree. Run Type: Select Once or Period in the Run Type area.
NOTE The value of Run Type for part of tasks is fixed to Once or Period because of their task types.
2. Click Next. 3. Set Start Time and Period Setting. Do as follows:

l l
Start Time: In the Time Setting area, set Start Time. Period Setting: In the Period Setting area, set Period and Run Times.
l For a one-time task, you can select Run at Once. After the task is created, it runs
NOTE at once.
l For a periodic task, you need to set the parameters in the Period Setting area.
Extended Parameters Step 4 Click Finish.
Set extended parameters according to the task requirements.
The created user timing task is displayed in the task list. ----End
6.7.4 Modifying a Timing Task

This section describes how to modify the attributes of a user timing task or a system timing task.
Prerequisite
You have logged in to the M2000 client successfully.
Context
Timing tasks are classified into System Timing Tasks and User Timing Tasks.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, modify the attributes of a timing task. You can modify a timing task by using one of the following methods:
NOTE
Parameter modification varies according to the task type.
6-38
Issue 10 (2010-09-06)

l
Select a task from the task list, and then click Attribute. In the Attribute dialog box, modify common and extended parameters. Double-click a task in the task list. In the displayed Attribute dialog box, modify common and extended parameters.
Step 3 Click Finish. ----End
6.7.5 Managing Timing Tasks

User timing tasks refer to those timing tasks managed by the user. The user can delete, suspend, resume, cancel, terminate, and roll back user timing tasks.
Suspending Timing Tasks

To delay the time for scheduling a task, you can suspend an idle timing task. After a task is suspended, it is changed to the suspended state.
Prerequisite
l l
You have logged in to the M2000 client. At least one idle timing task exists.
Context
The M2000 can execute the tasks that are not suspended only through scheduling.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Suspend one or more idle tasks with one of the following methods:
l
Manual suspending Select one or more tasks in the task list. Right-click the task and select Suspend. In the Confirm dialog box, click Yes.
Automatic suspending Select a task in the task list. Right-click the task and select Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and then specify the time. Click OK.
----End
Resuming Timing Tasks

You can resume a suspended task. After that, the task becomes idle and is ready to be dispatched by the system.
Prerequisite
l l
You have logged in to the M2000 client. At least one suspended scheduled task exists.
Context
Only idle tasks can wait to be used.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Resume the suspended task with one of the following methods:
l
Manual resuming Select one or more tasks in the task list in the right pane. Right-click the task and select Resume. In the Confirm dialog box, click Yes.
Automatic resuming Select a task in the task list in the right pane. Right-click the task and select Timely Suspend/ Resume. In the Timely Suspend/Resume dialog box, select Resume Time and then specify the time. Click OK.
----End
Setting Time of Timing Tasks

You can set an automatic suspend time or an automatic restore time for a scheduled task. In this situation, the M2000 automatically suspends the task or restores the task.
Prerequisite
l l
You have logged in to the M2000 client. At least one suspended or idle timing task exists.
Context
l
The system suspends an idle task and delay the time for using this task. If the timing task is not in the Idle state at the specified time, it fails to be suspended. In the specified time, the system resume a suspended task and then the task is in the idle status and wait to be dispatched. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You are not allowed to set auto-suspend or resume a Running timing task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to suspend. Step 3 From the task list in the right part of the window, select a timing task to be suspended.
Step 4 Right-click the task and choose Timing Suspend/Resume. Step 5 In the displayed Timing Suspend/Resume dialog box, select Suspend Time or Resume Time as required. Step 6 Set the suspend time or resume time. For details of setting an automatic suspend time or an automatic restore time, refer to 6.8.31 Parameters for Setting Time of Timing Tasks. ----End
Cancelling Timing Tasks

You can cancel a running task. The task status is changed to idle after being cancelled.
Prerequisite
l l
You have logged in to the M2000 client. At least one Running timing task exists.
Context
A user in the common user group can cancel only the tasks created by himself. A admin can cancel the timing tasks created by all users.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Select one or more running tasks in the task list in the right pane. Right-click the task and select Cancel. Step 4 In the Confirm dialog box, click Yes. Then the status of the task is changed from running to idle. ----End
Deleting Timing Tasks

You can delete the tasks created by yourself according to the actual requirements to save system resources.
Prerequisite
l l
You have logged in to the M2000 client. At least one timing task exists.
Context
l
Users can delete only the tasks created by themselves. The admin can delete the tasks created by all users. System tasks cannot be deleted.
Issue 10 (2010-09-06)

l l
Running tasks cannot be deleted. You can delete only an Archived CME download task.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Select one or more scheduled tasks in the task list in the right pane. Step 4 Click Delete. Step 5 In the Confirm dialog box, click Yes. Then the task is deleted from the task list. ----End
6.7.6 Browsing the Information of Timing Tasks

In the M2000, you can browse information about timing tasks such as the task name, user name, process, and execution result according to your own permissions.
Prerequisite
l l
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree.
NOTE
l l
The task list area on the right displays the information about the tasks that can be viewed by the current user. If you want to view the common parameters and extended parameters of each task, go to Step 3
Step 3 Double click a task, or select a task and click Attribute. The Attribute dialog box is displayed. In the Common Parameter tab and Extended Parameter tab, you can view the task details.
NOTE
l l
If State of a task is Finished, you can view the task information only. If State of a task is Idle, Suspend, or Running, you can modify the task details in the Attribute dialog box.
----End
6.7.7 Viewing the Task Execution

You can view the last execution results of a timing task.
Prerequisite
l l
Context
l
During the creation of CME tasks, sub-tasks are created, which are executed in different phases. You can browse the execution progress of subtasks of CME tasks.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree.
l
View the execution conditions in the Prev Execution Result column in the task list in the right pane. You can check the result details in the Result Info area.
----End
6.7.8 Downloading Result Files

This describes how to download the results of timing tasks. You can save the results of timing tasks on the server to the local client in .txt format.
Prerequisite
l l
You have logged in to the M2000 client. The timing task that is used for downloading the result files exists and it is run for at least once.
Context
The allowable operations vary depending on the task type, as shown in Table 6-11. Table 6-11 Allowable operations for different task types Task Type CME and iSStar Script Executor task Allowable Operation The task result are saved on the server in logs. The Result Info area displays only the information about the last task execution. The result logs are not displayed. You can download all the result files to the local client. Result files of multiple tasks can be downloaded concurrently. MML Script task Network Health Check task
Issue 10 (2010-09-06)
You can download the latest result file to the local client. Result files of multiple tasks can be downloaded concurrently. You can download the result file of the selected task. Result files of multiple tasks can be downloaded concurrently.
6-43
Task Type Dual Home Management task Timing task, NE Software Download task, and NE Backup task
Allowable Operation You can view the latest consistency check result on line. If a task is performed at least once, you can save the messages in the Result Info area to a local path.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the type of the task that is used to download the result files. Select the specific tasks in the right pane. Step 3 Perform the following operations according to the task type. Task Type CME or iSStar Script Executor task Procedure To download the result logs of a download task, perform the following steps: 1. Select the task whose result logs you plan to download. 2. Click Save Log. In the displayed Please select a directory dialog box, set the save path 3. Click OK.
NOTE The system generates a folder for the log file generated each time and saves the folder to the specified path. The result log file is named in the format YYYY-MMDD_HH-MM-SS, for example, 2008-04-18_10-27-53.
6-44
Issue 10 (2010-09-06)
Task Type MML Script task
Procedure To download the result files of a single task, do as follows: 1. Select the MML script task whose result files you plan to download. 2. Right-click a task and choose Save MML Result on the shortcut menu. Alternatively, you can right-click the Result Info field and choose Save AS on the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save. To download the result files of multiple tasks, do as follows: 1. Press Ctrl or Shift to select multiple MML script tasks in the task list. 2. Right-click the tasks and choose Save MML Result on the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save. Save the execution results of multiple MML script tasks to the same file.
Network Health Check task
1. Select the task whose result files you plan to download. 2. Right-click a task and choose NHC Report on the shortcut menu. 3. In the displayed NHC Report dialog box, select the check report based on Report Nameand then click Save.
NOTE You can click Open to view the contents of the check report and decide whether the report needs to be downloaded.
4. Set the save path in the displayed Please select a directory dialog box. 5. Click OK. Dual Home Management task Right-click a task and choose Checked Result from the shortcut menu.
NOTE If data inconsistency exists, you need to generate a script to adjust the data difference and synchronize the data.
Issue 10 (2010-09-06)
6-45
Task Type Timing task, NE Software Download task, and NE Backup task
Procedure To download the result information about a download task, perform the following steps: 1. Select a task whose result information needs to be downloaded. 2. Right-click in the Result Info area can choose Save As from the shortcut menu. 3. Set the save path in the displayed Save dialog box, and then click Save.
----End
6.7.9 Technical Specifications of Centralized Task Management

The technical specifications of centralized task management refer to the limitations on the centralized task management. Function Centralized task interface Specification Maximum size of the execution results of MML tasks can be displayed on the M2000 client (MBytes). Maximum size of script files uploaded for MML tasks (MBytes). User task Maximum number of scheduled NE backup tasks Maximum number of tasks configured with MML scripts (including the dualhome consistency check task) Maximum number of scheduled software download tasks Maximum number of iSStar script tasks Maximum number of CME upload tasks
6-46
Value 2
50
50
50
500 50
Issue 10 (2010-09-06)
Function
Specification Maximum number of CME download tasks Maximum number of dual-home management tasks Maximum number of TMO configuration import tasks
Value 50 50
100
6.8 Reference of the OSS Management GUI

This part describes the OSS management interfaces and related information such as the parameters used in the OSS management. This helps you understand the functions of OSS management easily. 6.8.1 Interface Description: Managing Timing Tasks This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. 6.8.2 Interface Description: M2000 Log Information Collector When the log information collector on the M2000 client or server is faulty, you can collect all related log files through FTP from the M2000 client or server to locate faults. 6.8.3 Parameters for the NE Partitioning Information This topic describes the related parameters in the Query NE Subarea dialog box. You can refer to the these parameters when you check the NE partitioning information. 6.8.4 Parameters for Querying the M2000 License This section describes the parameters in the License Information dialog box. You can refer to these parameters when you view M2000 licenses information. 6.8.5 Parameters for Setting Monitoring Parameters of the M2000 Server This section describes the parameters of system monitor settings. You can use these parameters when you set the server thresholds. 6.8.6 Parameters for Monitoring the M2000 Server Service Status This section describes the parameters of the query result displayed in the Service Monitor tab. You can use these parameters when you monitor the M2000 server service status 6.8.7 Parameters for Monitoring the M2000 Server Process Status This section describes the parameters of the query result displayed in the Process Monitor tab. You can use these parameters when you monitor the M2000 server process status. 6.8.8 Parameters for Monitoring the M2000 Server Hard Disk Status This section describes the parameters of the query result displayed in the Hard Disk Monitor tab. You can use these parameters when you monitor the M2000 server hard disk status. 6.8.9 Parameters for Monitoring the M2000 Server Database Status This section describes the parameters of the query result displayed in the Database Monitor tab. You can use these parameters when you monitor the M2000 server database status.
6.8.10 Parameters for Setting Task Filter Conditions This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section. 6.8.11 Parameters for Setting the Common Information About Timing Tasks This topic describes the common parameters of all timing tasks except CEM download tasks. When you create or copy a user timing task or when you modify a user or system timing task, you can refer to this topic. 6.8.12 Parameters for Modifying Database Capacity This section describes the parameters of database capacity management tasks. When modifying database management tasks, you can set the parameters by referring to the information described in this section. 6.8.13 Parameters for Modifying File interface Task This section describes the parameters of file interface tasks. When modifying file interface tasks, you can set the parameters by referring to the information described in this section. 6.8.14 Parameters for Modifying Synchronization task This section describes the parameters of Synchronization task. When modifying Synchronization task, you can set the parameters by referring to the information described in this section. 6.8.15 Parameters for Modifying NE Basic Information Export Task This section describes the parameters involved in the NE basic information export task. When modifying an NE basic information export task, you can refer to this part and perform relevant operations. 6.8.16 Parameters for Modifying Alarm Timing Acknowledgement This part describes the parameters in the alarm acknowledgement. When modifying alarm acknowledgement, you can set the parameters in the alarm acknowledgement by referring to the information described in this section. 6.8.17 Parameters for Modifying Data Backup Task This section describes the parameters of data backup tasks. When modifying data backup tasks, you can set the parameters by referring to the information described in this section. 6.8.18 Parameters for Creating/Modifying/Copying MML Command Script This section describes the parameters of MML command script tasks. When creating or modifying MML command script tasks, you can refer to this part. 6.8.19 Parameters for Creating/Modifying/Copying RAN Report Task This describes the parameters involved in the RAN report task. When creating, modifying, or copying a RAN report task, you can refer to this part and perform relevant operations. 6.8.20 Parameters for Creating, Viewing, or Modifying a Scheduled Report Task This section describes the parameters for setting a scheduled report task. You can refer to this part when you create, query, or modify a scheduled task. 6.8.21 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top Power This section describes the parameters of a task for testing BTS cabinet-top power. You can refer to this section when creating or modifying such a task. 6.8.22 Parameters for Creating/Modifying/Copying an RSSI Test Task This section describes the parameters of an RSSI test task. You can refer to this section when creating or modifying an RSSI test task. 6.8.23 Parameters for Creating/Modifying/Copying Software Download
6-48
Issue 10 (2010-09-06)
This section describes the parameters in the software download task. When creating or modifying software download task, you can set the parameters for software download task by referring the information described in this section. 6.8.24 Parameters for Creating/Modifying/Copying Dual-Home Management This describes the parameters used in dual-homing management. You can refer to these parameters when creating, modifying, or copying dual-home management. 6.8.25 Parameters for Creating/Modifying/Copying iSStar Script This section describes the parameters in the iSStar script task. When creating or modifying iSStar scripts, you can set the parameters in the iSStar tasks by referring to the information described in this section. 6.8.26 Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log This describes the parameters for exporting NE logs and can be taken as reference during the parameter modification. 6.8.27 Parameters for Creating/Modifying/Copying a CME Upload Task This describes the parameters of a CME upload task. When creating or modifying a CME upload task, you can refer to the parameter description and perform relevant operations. 6.8.28 Parameters for Creating/Modifying/Copying Cell Parameters Compare Task This describes the parameters involved in the CME cell algorithm comparison task. When creating or modifying a CME cell algorithm comparison task, you can refer to this part and perform relevant operations. 6.8.29 Parameters for Creating/Modifying/Copying Cell Consistency Check Task This describes the parameters involved in the CME cell consistency check task. When creating or modifying a CME cell consistency check task, you can refer to this part and perform relevant operations. 6.8.30 Parameters for Creating/Modifying/Copying a CME Current Area Export Task This describes the parameters of CME Current Area Export tasks. When creating or modifying a CME Current Area Export task, you can refer to the information described in this part. 6.8.31 Parameters for Setting Time of Timing Tasks This section describes the parameters of time for automatic suspending and automatic resuming timing tasks 6.8.32 Parameters for Selecting Objects for Device Check This part describes the extended parameters for selecting objects for device check. You can refer to this part when creating device check tasks. 6.8.33 Parameters for Collecting NM Logs Parameters This describes the parameters of the M2000 log information collecting tool dialog box. When collecting NMS log files, refer to the information described here for parameter setting.
6.8.1 Interface Description: Managing Timing Tasks

This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. After you log in to the server, the Timing Task Management interface is displayed, as shown in Figure 6-8. Table 6-12 describes each element displayed in Figure 6-8.
Issue 10 (2010-09-06)
6-49
Figure 6-8 Timing Task Management interface
Table 6-12 Description of the Timing Task Management interface No. (1) (2) Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out central task management are available on the button panel. You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors are used to indicate different states of tasks: Gray: complete; Orange: suspended; Blue: active; White: idle. The selected color of the task is darker than the previous color of the task.
(3)
Button panel
(4)
Task list
6-50
Issue 10 (2010-09-06)
6.8.2 Interface Description: M2000 Log Information Collector

When the log information collector on the M2000 client or server is faulty, you can collect all related log files through FTP from the M2000 client or server to locate faults. The Log Information Collector interface contains four parts:
l
Server Information: In this area, you can set Server Address, Port, FTP User Name, and Password. Items Selection: In this area, you can select the required information. To collect the client trace files, server trace files, or server core files, you must set Start Time and End Time of a specific time segment. To collect the alarm location information, enter an NE name in NE Name. Directory: This area shows the path for saving the diagnosis information. You can change the path. Collected Information Details: In this area, you can view the information collection process and progress.
Figure 6-9 shows the interface. Figure 6-9 M2000 Log Information Collector interface
6.8.3 Parameters for the NE Partitioning Information

This topic describes the related parameters in the Query NE Subarea dialog box. You can refer to the these parameters when you check the NE partitioning information.
Issue 10 (2010-09-06)
6-51
Parameter Description
Parameter Query Condition NE Subarea Description Host Name of the NE Partitioning When you query the specific partitioning information, you can select names of all partitions or the name of a specific partition from the dropdown list. indicates the NE Name. indicates the serial number of the NE. indicates the NE Name. indicates the version of the NE. indicates the number of the NEs that belong to the NE Partitioning. indicates the partitioning information about the NE, including the IP address and the instance name of the database.
NE Name Query Result No. NE Name NE Version Number of NEs Statistic
6.8.4 Parameters for Querying the M2000 License

This section describes the parameters in the License Information dialog box. You can refer to these parameters when you view M2000 licenses information.
Parameters for Resource Control Item Tab

Parameter License name Description Description: Names of authorization items. License capacity Description: Capacity defined in the license. License consumption Description: Capacity of the licenses consumed. License expiration time Description: Expiry time of each authorization item. Detailed Information Description: View details of authorization items. Server ID Description: Local server ID and authorization server ID displayed after you click Server ID
Parameter Update License
Description Description: Click the button to update license.
Parameters for Function Control Item Parameters Tab

Parameter License name Description Description: Names of authorization items. License capacity Description: Number of the license of the devices authorized to be managed.
6.8.5 Parameters for Setting Monitoring Parameters of the M2000 Server

This section describes the parameters of system monitor settings. You can use these parameters when you set the server thresholds.
Parameters
l
Issue 10 (2010-09-06)
6-53
Name Server status refresh interval (seconds)
Description Description: Refresh interval for server monitoring, that is, the CPU usage is sampled every x seconds. Description: Used to set Threshold for Alarm Generation, Threshold for Alarm Clearance for the CPU usage alarm and whether to enable the bubble. Used to set Threshold for Alarm Generation and Threshold for Alarm Clearance for the memory usage alarm.
l
Settings Value: Value range: 2-60. Default value: 15.
CPU used rate (%)
Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50. Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50.
Memory used rate (%)
Table 6-14 Hard Disk Monitor Name Disk Monitor Parameter Settings Hard disk status refresh interval (seconds) Description Description: Refresh interval for hard disk monitoring. Settings Value: Value range: 60-3600 Default value: 60
6-54
Issue 10 (2010-09-06)
l

l l l l
Issue 10 (2010-09-06)
6-55
l
l If you select
l If you select
6-56
Issue 10 (2010-09-06)
Table 6-15 Database Monitor Name Database Monitor Parameter Settings Database status refresh interval (seconds) Description Description: Interval of database refreshing. Settings Value: Value range: 300-3600 Default value: 300 Database Monitor Threshold Settings Default Value Setting (%) Description: All default thresholds of database usage on the M2000 server.
l

l l l l
Issue 10 (2010-09-06)
6-57
l
l

Table 6-16 Service Monitor Name Services Monitor Parameter Settings Service status refresh interval (seconds) Description Description: Interval of service refreshing. Settings Value: Value range: 60-3600 Default value: 60
6-58
Issue 10 (2010-09-06)
l if a monitored

l You can double-
6.8.6 Parameters for Monitoring the M2000 Server Service Status

This section describes the parameters of the query result displayed in the Service Monitor tab. You can use these parameters when you monitor the M2000 server service status
Parameters
Name Service Name Description Description: Name of a service. Process Name Description: Name of a process. Description Description: Description of functions and interfaces provided by a service. Status Description: Status of a service.
Issue 10 (2010-09-06)
6-59
Name Startup Mode
Description Description: Service start mode, including Automatic, Manual, and Disable. The Disable mode is available only for stopped services.
Start Time
Description: Time that the service is started.
Server Name
Description: Name of the server.
6.8.7 Parameters for Monitoring the M2000 Server Process Status

This section describes the parameters of the query result displayed in the Process Monitor tab. You can use these parameters when you monitor the M2000 server process status.
Parameters
Name Process Name Description Description: Name of a process. Process ID Description: ID of a process. Handle Number Description: Number of handles used by a process. CPU Usage(%) Description: CPU usage of a process. Memory Usage(MB) Description: Sum of the virtual and physical memory usage of a process. DB Connection Number Description: Number of database connections used by a process. Thread Number Description: Number of threads generated by a process.
6.8.8 Parameters for Monitoring the M2000 Server Hard Disk Status
This section describes the parameters of the query result displayed in the Hard Disk Monitor tab. You can use these parameters when you monitor the M2000 server hard disk status.
Parameters
Name File System Description Description: Hard disk partitions and their paths. Total Size(MB) Description: Total space of a specific partition, equals to the sum of Used Size and Free Size. Used Size(MB) Description: Used space of a specific partition. Free Size(MB) Description: Available space of a specific partition. Usage(%) Description: Current usage of a specific partition. Status Description: Current status of a specific partition, including normal and abnormal. If the usage is more than or equal to the maximum, the system displays Abnormal.
6.8.9 Parameters for Monitoring the M2000 Server Database Status

This section describes the parameters of the query result displayed in the Database Monitor tab. You can use these parameters when you monitor the M2000 server database status.
Parameters
Name Database Name Description Description: Name of the database on the M2000 server. Total Data Space (MB) Description: Total data space. Free Data Space (MB) Description: Remaining data space.
Issue 10 (2010-09-06)
6-61
Name Data Space Usage (%)
Description Description: Usage rate of the used data space and total data space.
NOTE The Oracle database occupies the table space in a greedy manner. The high-water mark determines the used and unused blocks in a segment. The high-water mark increases after data is added, but does not decrease after data is deleted. The M2000 calculates the Oracle data usage by monitoring the high-water mark. Therefore, the Oracle data usage monitored by the M2000 does not decrease after data deletion.
Total Log Space (MB)
Description: It refers to the space allocated to each database log of the M2000.
Free Log Space (MB)
Description: It refers to the unused disk space allocated to database logs.
Log Space Usage (%)
Description: It is calculated by the following formula: Log Used Rate = (Total Log Space - Free Log Space)/Total Log Space x 100%.
Status
Description: Database status, including normal and abnormal. If the database usage is more than or equal to the threshold, the system displays Abnormal.
6.8.10 Parameters for Setting Task Filter Conditions

This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section.
Parameters
Parameter User Name Current User Description Description: Indicates the user that operates the client. Other Users Description: Indicates other users except the current user. Catego ry User Task Description: Indicates the task created by users.
6-62
Issue 10 (2010-09-06)
Parameter System Task
Description Description: Indicates the task created by OMC during the system installation or upgrade.
State
Idle
Description: Indicates that the task waits for being performed by the system.
Running
Description: Indicates that the task is being performed by the system.
Suspend
Description: The task is not ready to be scheduled.
Finished
Description: Indicates that the task is completed by the system.
Archived
Description: The archived state is supported only by the CME download task. After the CME download task is stopped, the task is archived. Only when the task is in the archived state, the task can be deleted.
Last Run Result
Success
Description: Indicates that the task is successfully carried out.
Processing
Description: Indicates that the task is being processed by the system.
Partly Success Failed
Description: Indicates that the task is partly successfully carried out. Description: Indicates that the task fails to carry out.
Miss Run Time
Description: Indicates that the task misses the previous performed time. If the server is not running properly or the task is suspended before the execution, the task may miss the previous execution. Description: Indicates that the previous execution result in the server is lost due to improper service or sudden power cut. Thus, after recovery, the previous execution result cannot be determined.
Unknown
Issue 10 (2010-09-06)
6-63
6.8.11 Parameters for Setting the Common Information About Timing Tasks
This topic describes the common parameters of all timing tasks except CEM download tasks. When you create or copy a user timing task or when you modify a user or system timing task, you can refer to this topic.
Parameters
Table 6-17 Common Parameters Parameter Task Name Description Description: Refers to the name of a timing task. Settings Value:
l l l
A maximum of 60 characters Unique and not null Case sensitive
Run Type
Description:
l
Value:
l l
Once: If you select this option, the system runs the created task once at the defined time point. Period: If you select this option, the system runs the created task periodically.
Once Period
Start time
Description: This parameter sets the time for starting a task.
Value: The start time should be later than the time displayed on the server.
NOTE For a one-time timing task, if you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete.
Task Type
Description: Refers to the type of a timing task.
6-64
Issue 10 (2010-09-06)
Parameter Period
Description Description: Interval between periodic tasks. It has two enlistments: unit and duration.
Settings Value:
l
The period can be represented in either of the following units: minutes, hours, days, weeks, months. The period, however, cannot be represented in seconds. The value range for period should be as follows: Minute (1 - 366 x 24 x 60), Hour (1 - 366 x 24), Day (1 - 366), Week (1 52), Month (1 - 12).
Run Times
Description: This parameter indicates the times that a periodic task is executed.
Value: 0 - 65535
NOTE
l 0 indicates that the number of times
for executing periodic tasks is not restricted.

l This parameter is displayed in the
Attribute dialog box only after you set it when creating and copying a periodic task.
6.8.12 Parameters for Modifying Database Capacity

This section describes the parameters of database capacity management tasks. When modifying database management tasks, you can set the parameters by referring to the information described in this section.
l l l l
Parameters of Alarm Database Capacity Management Tasks Parameters of Performance Database Capacity Management Tasks Parameters of NE Log Database Capacity Management Tasks Parameters of M2000 Log Database Capacity Management Tasks
Table 6-18 Parameters of alarm database capacity management tasks Parameter Compress File After Export Value Range Selected from the drop-down list Description When the data in the database expires, the system can choose whether to compress files after the export. You can select either Yes or No in this field. Yes is selected by default.
Issue 10 (2010-09-06)
6-65
Parameter File Format
Value Range Selected from the drop-down list
Description Refers to the format of the file that saves the exported data. Alarm database capacity management tasks support .txt, .csv, .html, and .xml files. Refers to the path for saving exported data. The save path is specified by the server and cannot be modified. Alarm database capacity management tasks: /export/home/omc/var/ ThresholdExport/FM. Refers to the storage duration of data in the database. The default storage duration is 90 days. Refers to the upper threshold of the file dump space. When you export files, the earliest dumped files are replaced if the total size of the files in the specified path exceeds the preset upper threshold.
NOTE When setting the upper threshold of dump space, you need to task the space of the partition to which the save path of files belongs into consideration. The set upper threshold cannot exceed the size of the partition.
Save File Path
None.
Hold Days in the Database File Size
Unit: day Value range: 1-90 Unit: MB Default value: 1,024 Value range: 200-2048
File Hold Days
Unit: day Default value: 15 Value range: 3-30
Refers to the storage duration of dumped files. The system automatically deletes the files whose storage duration exceeds the preset days. Refers to the upper threshold of the files in the file dump space. When you export files, the earliest dumped files are replaced if the total number of the files in the specified path exceeds the preset upper threshold.
File Sum
Number of files Default value: 1,000 Value range: 200-2000
Table 6-19 Parameters of performance database capacity management tasks Parameter Export Data Value Range Selected from the drop-down list Description If you select No, the system automatically deletes the expired performance data, and the parameters related to file export become invalid. If you select Yes, the system exports the expired performance data according to the preset file export parameters.
6-66
Issue 10 (2010-09-06)
Parameter Compress File After Export
Value Range Selected from the drop-down list
Description When the data in the database expires, the system can choose whether to compress files after the export. You can select either Yes or No in this field. Yes is selected by default. Refers to the format of the file that saves the exported data. Performance database capacity management tasks support .csv files. Refers to the path for saving exported data. The save path is specified by the server and cannot be modified. Performance database capacity management tasks: /export/home/omc/var/ ThresholdExport/PM. Refers to the storage duration of data in the database. The default storage duration is 30 days. Refers to the upper threshold of the file dump space. When you export files, the earliest dumped files are replaced if the total size of the files in the specified path exceeds the preset upper threshold.
File Format
Selected from the drop-down list None.
Save File Path
File Hold Days
l
File Sum
Hold Days Setting
Select Common Mode or Configuration Mode.
Common Mode: You need to manually enter a value in Hold Days in the Database. The value range is 1-90. The default value is 30. Configuration Mode: You need to specify Configuration File. The system uses the storage duration specified in the configuration file.
Issue 10 (2010-09-06)
6-67
Table 6-20 Parameters of NE log database capacity management tasks Parameter Compress File After Export Value Range Selected from the drop-down list Description When the data in the database expires, the system can choose whether to compress files after the export. You can select either Yes or No in this field. Yes is selected by default. Refers to the format of the file that saves the exported data. NE log database capacity tasks support .txt and .csv files. Refers to the path for saving exported data. The save path is specified by the server and cannot be modified. NE log database capacity management tasks: /export/home/omc/var/ ThresholdExport/NeLog. Refers to the storage duration of data in the database. The default storage duration is 30 days. Refers to the upper threshold of the file dump space. When you export files, the earliest dumped files are replaced if the total size of the files in the specified path exceeds the preset upper threshold.
File Format
Selected from the drop-down list None.
Save File Path
File Hold Days
File Sum
Table 6-21 Parameters of M2000 log database capacity management tasks Parameter Compress File After Export Value Range Selected from the drop-down list Description When the data in the database expires, the system can choose whether to compress files after the export. You can select either Yes or No in this field. Yes is selected by default.
Issue 10 (2010-09-06)
6-68
Parameter File Format
Value Range Selected from the drop-down list None.
Description Refers to the format of the file that saves the exported data. M2000 log database capacity management tasks support .xml and .csv files. Refers to the path for saving exported data. The save path is specified by the server and cannot be modified. The M2000 log database capacity management tasks: /export/home/omc/var/ ThresholdExport/Log. Refers to the storage duration of data in the database. The default storage duration is 30 days. Refers to the storage duration of dumped files. The system automatically deletes the files whose storage duration exceeds the preset days. Refers to the upper threshold of the files in the file dump space. When you export files, the earliest dumped files are replaced if the total number of the files in the specified path exceeds the preset upper threshold. Refers to the upper threshold of the file dump space. When you export files, the earliest dumped files are replaced if the total size of the files in the specified path exceeds the preset upper threshold.
Save File Path
Hold Days in the Database File Hold Days
Unit: day Value range: 1-180 Unit: day Default value: 15 Value range: 3-180
File Sum
File Size
Unit: MB Default value: 1,024 Value range: 200-4096
6.8.13 Parameters for Modifying File interface Task

This section describes the parameters of file interface tasks. When modifying file interface tasks, you can set the parameters by referring to the information described in this section.
l l l l l
Parameters for Modifying an Alarm Data Export Task Parameters for Modifying the Export of Performance Data Parameters for Modifying the Export of Inventory Data Parameters for Modifying the Export of NE Logs Parameters for Modifying the Export of M2000 Logs
Issue 10 (2010-09-06)

l
Parameters for Modifying the Export of Configuration Data
Table 6-22 Parameters for Modifying an Alarm Data Export Task Parameter File type Description Description: The format of the exported files. Value Range Value: You can select the following file types:
l l l l
CSV XML TXT HTML
Compression format
Description:
l
Value: You can select one of the following items.

l l l
If you select zip or gzip, it indicates that the .csv, .xml, .txt or .html files are decompressed and then exported. If you select Not compress, it indicates that the .csv, .xml file, .txt or .html is exported.
Not compress zip gzip
Export To
Description: The save path of exported alarm data.
Value: The default value is used and cannot be changed. The default path is /export/home/omc/var/ fileint/fm/.
File prefix
Description: Prefix of export file names. Export files are named in the export path in the format of prefix-export timedata type. For example, assume that the prefix is abc. The generated file names are abc-20090928104022 -alarm-log-auto-1.zip and abc-20090928104022 -event-log-auto-1.zip.
Value: The value contains 0-30 characters.
6-70
Issue 10 (2010-09-06)
Parameter Export Mode of Alarm Logs
Description Description:
l
Value Range Value: -
Export all unacknowledged and uncleared alarms indicates that all unacknowledged and uncleared alarms are exported based on the export conditions. Export incremental alarms indicates that only the alarms that are generated from the time of last export to now are exported based on the same export conditions. If the current export conditions are different from the previous export conditions, all alarms that meet the current conditions are exported.
Alarm Severity, Category, and Type
Description: Select the severity, category, and type of the alarm to be exported.
Value: You can select the following values:

l
Alarm severities: critical, major, minor, and warning. Alarm categories: current alarm, event alarm, history alarm, and shielded alarm. Alarm types: Power system, Environment system, Signaling system, Trunk system, Hardware system, Software system, Running system, Communication system, QoS, Processing error, Internal, Integrity violation, Operational violation, Physical violation, Security service or mechanism violation, Time domain violation.
Alarm Name
Description: List the alarms that can be exported currently.
Value: Select Alarm Name tab, and then click to select the alarm name.
Issue 10 (2010-09-06)
6-71
Table 6-23 Parameters for Modifying the Export of Performance Data Parameter File Format Value Range You can choose:
l l l
Description Performance measurement results are exported as a .csv or .xml file.
CSV. XML. TXT.
Hold Days
Enter as required. The default value is 90.
The data of a task is deleted from the server after the storage duration expires. By default, the exported data is saved in the /export/home/omc/ var/fileint/pm/ path. The default value cannot be changed. You can set the measurement period for an export task by clicking different measurement period tabs. This parameter is used to set the execution period of an export task. The available values of this parameter depend on the selected NE type.
NOTE The export period and measurement period of performance data must be consistent.
File Path
Default value. No change. The default path is /export/ home/omc/var/fileint/pm/.
Period
You can click different measurement period tabs.
Export Period
Options in the drop-down list.
Delay Time
The value must be multiples of 5 minutes. Value range: 5 to 1440. The unit is minute.
The parameter specifies the delay time for running a task. The value must be an integral multiple of 5 minutes and should not be null.
6-72
Issue 10 (2010-09-06)
Parameter Function Subsets
Value Range You can select function subsets from the navigation tree.
Description You can control the function subset navigation tree in the left pane by selecting Show Been Set Measuring Function Subsets and Show All Function Subsets. In the navigation tree in the left pane, you can select the function subset whose performance measurement results are to be exported and then click or to add the function subset to the area on the right so that the performance measurement results of the selected function subset can be periodically exported according to the task settings.
Template
You can select templates from the navigation tree.
After a result query template is selected, query results are periodically exported according to the settings of the template.
CAUTION
l If the result query templates
having the same name exist on one measurement period tab page, and if the performance measurement results are to be exported by template name according to the setting in the configuration file of the tool for exporting performance measurement results collected by the M2000, the result files that are exported on the basis of the templates sharing the same name will replace each other when you select a template sharing the same name with other templates. To avoid file replacement, you need to change the names of the result query templates or modify the setting in the configuration file so that performance measurement results are exported by template ID.
l If the result query templates
having the same template ID exist on one measurement period tab page, only one displayed.
Issue 10 (2010-09-06)
6-73
Parameter Filter Search
Value Range None
Description The system searches for results by the name of a function subset. The searching condition is case insensitive. In addition, the fuzzy search is supported, whereas the wildcard search is not supported.
Table 6-24 Parameters for Modifying the Export of Inventory Data Parameter File Format File Path Description Exports the operation logs to a .txt file, csv file or .txt file. Indicates the path to save the exported inventory data. Default value: /export/home/omc/var/fileint/cm/ InvtTimerExport. All NE Please Select NE If you select this option, the system exports the inventory data of all NEs on the network. This option is selected by default. Indicates all the NEs in the entire network. Multiple NEs are supported. You can select the specific NEs in Please Select NE only after you deselect All NE.
Table 6-25 Parameters for Modifying the Export of NE Logs Parameter File Format File Path Value Range You can select .txt or .csv. Default value: No change. The default path is: /export/ home/omc/var/fileint/nelogs/. File Size Unit: MB Default value: 1024 Refers to the threshold of the space for dumping log files. During the export of log files, if the size of the files existing in the specified path exceeds the preset threshold, the earliest files are replaced.
NOTE When setting the threshold of dump space, the size of the partition that the path for saving log files belongs to must be taken into account. The threshold cannot exceed the size of the partition.
Description Exports the operation logs to a .txt file or .csv file. Saves NE logs.
6-74
Issue 10 (2010-09-06)
Parameter File Hold Days
Value Range Unit: day Default value: 15
Description Refers to the number of the days within which the dump files can be saved. After these days, the files are automatically deleted. Refers to the maximum number of files in the dump space. During the export of log files, if the number of the files existing in the specified path exceeds the preset threshold, the earliest files are replaced.
File Sum
Number of files Default value: 1000
Table 6-26 Parameters for Modifying the Export of M2000 Logs Parameter Compress Exported File Value Range
l l
Description
l
Yes. No.
If you select Yes, the .csv files or .xml files are compressed to a packet and exported. If you select No, the .csv files or .xml files are directly exported.
Exported File Format Save File Path
You can select .csv or .xml. Default value. No change. The default path is:/export/ home/omc/var/fileint/ ***logs/, where *** stands for the log type.
Exports operation logs to a .csv file or .xml file. Saves the exported logs.
File Size
Unit: MB Default value: 1024
Refers to the threshold of the space for dumping log files. During the export of log files, if the size of the files existing in the specified path exceeds the preset threshold, the earliest files are replaced.
NOTE When setting the threshold of dump space, the size of the partition that the path for saving log files belongs to must be taken into account. The threshold cannot exceeds the size of the partition.
Issue 10 (2010-09-06)
6-75
Parameter File Hold Days
Value Range Unit: day Default value: 15
Description Refers to the number of the days within which the dump files can be saved. After these days, the files are automatically deleted. Refers to the maximum number of files in the dump space. During the export of log files, if the number of the files existing in the specified path exceeds the preset threshold, the earliest files are replaced.
File Sum
Number of files Default value: 1000
Table 6-27 Extension parameters of Configuration Data Export tasks Parameter File Format Value Range Two formats are available, that is, .xml and .csv. You can select from the dropdown list. Default value. No change. The default path is: /export/home/ omc/var/fileint/ cm/autoExport. Please Select NE You can select the required NEs in Physical Topology Tree. If All NE Configuration Data is selected, the Physical Topology Tree becomes unavailable. Then the M2000 exports the configuration data of all NEs.
l l l
Description Refers to the format in which the exported data files are saved.
File Path
Refers to the path to save the exported configuration data.
Click Click
to expand all the sub nodes. to collapse all the sub nodes.
refers to cascading select. That is, by selecting a parent node, all the subnodes under it are selected.
6-76
Issue 10 (2010-09-06)
6.8.14 Parameters for Modifying Synchronization task

This section describes the parameters of Synchronization task. When modifying Synchronization task, you can set the parameters by referring to the information described in this section.
Parameter description
l l
Parameters for Modifying the Synchronization of NE Configuration Data Parameters for Modifying the Synchronization of Inventory Data
Table 6-28 Parameters for Modifying the Synchronization of NE Configuration Data Parameter All NE Configuration Data Please Select NE Description If All NE Configuration Data is selected, the system synchronizes the configuration data of all existing NEs in the network. Select existing NEs in the entire network. Multiple NEs are supported.
Table 6-29 Parameters for Modifying the Synchronization of Inventory Data Parameter All NE Please Select NE Description If you select this option, the system synchronizes the inventory data of all NEs on the network. Indicates all the NEs in the entire network. Multiple NEs are supported. You can select the specific NEs in Please Select NE only after you clear All NE.
6.8.15 Parameters for Modifying NE Basic Information Export Task

This section describes the parameters involved in the NE basic information export task. When modifying an NE basic information export task, you can refer to this part and perform relevant operations.
The M2000 provides the function of exporting NE basic information. Thus, it can provide data to the Nastar for performance analysis. You can modify the common parameters and extended parameters of the task according to the actual requirement. Parameter Exported File Description Export the file containing NE basic information to the /export/home/omc/var/fileint/network/ EAMInfo.xml path on the M2000 server.
Issue 10 (2010-09-06)
Parameter Export All NE
Description The NE navigation tree is unavailable. You need not specify the NEs to be exported. The M2000 exports the information about all NEs. After you select a certain NE type from the NE navigation tree, the M2000 exports the information about all NEs of this type. After you select some NEs from the NE navigation tree, the M2000 exports the information about all selected NEs.
Export By NE Type
Export By NE
6.8.16 Parameters for Modifying Alarm Timing Acknowledgement

This part describes the parameters in the alarm acknowledgement. When modifying alarm acknowledgement, you can set the parameters in the alarm acknowledgement by referring to the information described in this section.
Parameter Alarm Level Value Range
l l l l
Description Indicates the level of alarms. Multiple choices are supported.
Critical Major Minor Warning Unacknowledge and unclear Fault Unacknowledge and clear Fault
Alarm State
Indicates the alarm states. Multiple choices are supported.
6.8.17 Parameters for Modifying Data Backup Task

This section describes the parameters of data backup tasks. When modifying data backup tasks, you can set the parameters by referring to the information described in this section.
l l
parameters for Modifying Data Backup in the M2000 Parameters for Creating/Modifying/Copying NE Backup
6-78
Issue 10 (2010-09-06)
Table 6-30 Parameters for Modifying Data Backup in the M2000 Parameter Server Full Backup Day File Path Value Range Form Monday to Sunday Description The full backup is executed each week. If you set to Monday, the full backup is performed each Monday. The path to save the backup M2000 system data.
Default value. No change. The default path is: /export/ home/backup/omc.
Table 6-31 Parameters for Creating/Modifying/Copying NE Backup Parameter File Path Backup All NE By NE Type Description Refers to the path to save NE data backup files. It is specified by the system. If you select this parameter, the system backs up the data of all NEs available in the current network. By default, the system backs up the data of all NEs in the entire network. If this option is selected, you should specify the NE type in the NE Type navigation tree. 1. Select By NE Type. 2. Click proceeded by By NE Type. The By NE Type dialog box is displayed. 3. In the navigation tree in the left pane, select one or multiple NE types. 4. Click side.
NOTE
l Click
to add the selected NE types to the valid domain at the right
to delete the selected NE types from the valid domain at the right
side.
l Click
and
to collapse and expand nodes in the navigation tree. to filter nodes in the
l Enter filtering conditions in Name, and then click
navigation tree.
5. Click Apply.
Issue 10 (2010-09-06)
6-79
Parameter By NE
Description If this option is selected, you should specify the NE in the NE navigation tree. 1. Select By NE. 2. Click proceeded by By NE. The By NE dialog box is displayed. 3. In the navigation tree in the left pane, select one or multiple NEs. 4. Click
NOTE
l Click l Click
to add the selected NEs to the valid domain at the right side.
to delete the selected NEs from the valid domain at the right side. and to collapse and expand nodes in the navigation tree. to filter nodes in the
l Enter filtering conditions in Name, and then click
navigation tree.
5. Click Apply.
6.8.18 Parameters for Creating/Modifying/Copying MML Command Script

This section describes the parameters of MML command script tasks. When creating or modifying MML command script tasks, you can refer to this part.
Parameter Script file Value Range The script file is in .txt format. The maximum size is 1 MB. Description The MML script file is a text file that records MML commands for one NE or multiple NEs of the same type. You can enter the path of an MML script file in the text box, or click . In the displayed Open dialog box, select the MML script file.
6-80
Issue 10 (2010-09-06)
Parameter Select NE
Value Range None.
Description After you select this option, you can change the NE of a script command by selecting the NE in the NE tree instead of modifying the script file. After the NE is selected, the original NE information in the script file is invalid, and all the commands are issued to the newly selected NE. The NE tree displays all the NEs in a physical topology tree. The function buttons for selecting NEs are described as follows:
l l l
: You can click this button to expand the NE tree. : You can click this button to collapse the NE tree. : You can click this button to use the Single Select mode. That is, if you select a node, the subnodes are not selected. You can click this button to switch to the Recursive Select mode. : to use the Recursive Select mode. That is, if you select a node, the subnodes are also selected. You can click this button to switch to the Single Select mode.
NOTE When creating MML script tasks, you must select Select NE to choose NE objects if certain command lines in the script file does not contain object information.
Execution Mode
Parallel or Serial.
Two modes for issuing MML commands are available:

l
Parallel: indicates that the MML commands are issued to the NE concurrently. Serial: indicates that the MML commands are issued to the NE in sequence.
Error-Execute Mode
Ignore or Stop.
Refers to the mode of handling the errors that occur when you run the MML commands in the MML script file.
l
Ignore: ignores the MML commands where errors occur and continues running other MML commands. Stop: stops running other MML commands.
Execution Result
None.
If the type of a created task is Once, you can select Save As and specify the path for adding the execution result of the task to a certain redirection file. If the specified redirection file does not exist, you can create the file. If the specified redirection file exists, the new information written into the file does not overwrite the original information. If you have set task result redirection, the path specified in Save As cannot be changed after a task is created.
Issue 10 (2010-09-06)
6-81
6.8.19 Parameters for Creating/Modifying/Copying RAN Report Task

This describes the parameters involved in the RAN report task. When creating, modifying, or copying a RAN report task, you can refer to this part and perform relevant operations.
You can set the RAN report export task on the M2000 to export the RAN report of a specified NE to a specified directory on the server. You can set a report task to export the MBTS, WCDMA, CDMA, or GSM reports. Parameter File Path Ne Type Description Refers to the default path for saving the file. The path cannot be changed. You can select MBTS, WCDMA, CDMA,or GSM. After you select the NE type, you also need to select the NEs whose reports are to be exported from the NE navigation tree. You can select Selected to specify Report Type.
Selected Report Type
6.8.20 Parameters for Creating, Viewing, or Modifying a Scheduled Report Task

This section describes the parameters for setting a scheduled report task. You can refer to this part when you create, query, or modify a scheduled task.
Common Parameters
Parameter Basic Informatio n Task Name Description Indicates the name of a scheduled report task. The value range is as follows:
l l
A maximum of 64 characters The following characters except ' are allowed: English characters, numbers, and other special characters. Unique and not null
Start Time
Indicates the time when a task starts to be executed. You can click and set the related parameters in the displayed Date/Time Selection dialog box. The start time must be later than the current time of the server.
6-82
Issue 10 (2010-09-06)
Parameter Execution Type
Description Indicates the execution type of a scheduled report task. The value range is as follows:
l
Periodic: indicates that the system performs a created task periodically. Once: indicates that the system performs a created task once at a specific time. If you select this option, the parameters in Execution Period become unavailable.
Execution Period
Indicates the interval between periodic tasks. Setting this parameter involves setting the unit and duration. The unit can be hour, day, week, or month.
Execution Times
Indicates the execution time of a periodic task. The value range is as follows:
l
Unlimited: indicates that the system runs this task unlimited times. Limited: indicates that the system runs this task N times. N represents a specific number.
Extended Parameters
Parameter Extended Parameter Report Name Save Path Description Indicates the name of a scheduled report task. Indicates the path for saving the generated reports. For example, /report/$ReportOwner$/$TaskName$$Date $. For the description of each field in the path, see Table 6-32. File Name Indicates the name of a generated report. For example, $reportname$-$date$. For the description of each field in the file name, see Table 6-32. File Format Indicates the format of the file where a report is saved. The value range is as follows:
l l l
Excel HTML CSV
Issue 10 (2010-09-06)
6-83
Parameter Compress
Description Indicates whether to compress the report files that are generated periodically. The value range is as follows:
l l
Selected Not selected
The system selects Compress by default. In this case, files are compressed in .zip format. Maximum File Number Indicates that the report files of a scheduled task that are generated in the latest N times are saved. N represents a specific number. The value range is as follows:
l
Unlimited: indicates that the system saves all the report files of the task. Limited: indicates that the system saves the report files of the latest generated tasks.
Table 6-32 lists the predefined macros that the save path and file name support. Table 6-32 Predefined Macros Predefined Macro $ReportOwner$ $TaskType$ Meaning Indicates the creator of a report. Indicates the type of a periodic task. The values are once, hour, daily, weekly, and monthly. $Time$ $DateTime$ $Format$ $TaskOwner$ $ReportName$ $TaskName$ $Date$ $Index$ Indicates the generation time of a periodic report. Indicates the generation date and time of a periodic report. Indicates the format of a periodic report. Indicates the creator of a scheduled report task. Indicates the name of a report. Indicates the name of a scheduled task. Indicates the generation date. Indicates the times of performing a scheduled task.
6-84
Issue 10 (2010-09-06)
Predefined Macro $yy$
Meaning Indicates a year. It supports simple expressions. For example, $yy-1$ indicates the year before the current year; $yy+1$ indicates the year after the current year.
$mm$
Indicates a month. It supports simple expressions. For example, $mm-1$ indicates the month before the current month; $mm+1$ indicates the month after the current month.
$dd$
Indicates a day. It supports simple expressions. For example, $dd-1$ indicates the day before the current day; $dd+1$ indicates the day after the current day.
$hh$
Indicates an hour. It supports simple expressions. For example, $hh-1$ indicates the hour before the current hour; $dd+1$ indicates the hour after the current hour.
$Moh$
Indicates a minute. It can be represented in a simple format. For example, $Moh-1$ indicates the minute before the current minute; $Moh+1$ indicates the minute after the current minute.
NOTE
The naming convention for scheduled task files is as follows:

l l
The name of the performance report file in Excel format is specified by File Name. The name of the performance report file in HTML or CSV format is specified as File Name +Subreport Name. For example, in task_120080523151900report_1, task_120080523151900 is the user-defined report name, and report_1 is the subreport name.
Issue 10 (2010-09-06)
6-85
Distribution Parameters
Parameter Email Distributio n To Description Indicates the recipient of emails. Use semicolons to separate recipient names. Click Email Boxes. The Select the distributing email box dialog box is displayed. Select one or multiple mailboxes, and then click OK.
TIP You can also right-click any row and choose Select All or Clear All from the shortcut menu.
The system can send scheduled report files to a maximum of 64 mailboxes simultaneously. Email Subject Indicates the subject of an email. If you have set To, you need to set the subject. Email Contents FTP Distributio n FTP Server Indicates the contents of an email. Indicates the IP address of the FTP server. Click FTP Server. The Select the distributing FTP server dialog box is displayed. Select one or multiple servers, and then click OK.
TIP You can also right-click any row and choose Select All or Clear All from the shortcut menu.
The system can send scheduled report files to a maximum of eight FTP servers simultaneously.
NOTE
The system adopts a redistribution mechanism. That is, in the case of an email or FTP distribution failure, the system redistributes the email or the FTP service three times immediately. In addition, you can manually perform a scheduled report task to generate a report file at a specific time and distribute the report file to an email or FTP server.
6.8.21 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top Power
This section describes the parameters of a task for testing BTS cabinet-top power. You can refer to this section when creating or modifying such a task.
Parameter Execution Duration Value Range 3-120 minutes Description Maximum execution duration of a task
6-86
Issue 10 (2010-09-06)
Parameter NE
Value Range None
Description Existing NE that supports cabinet-top power test.
6.8.22 Parameters for Creating/Modifying/Copying an RSSI Test Task

This section describes the parameters of an RSSI test task. You can refer to this section when creating or modifying an RSSI test task.
Parameter Execution Duration NE Frequency Value Range 3-120 minutes None 0-2047 The default value is null, which indicates that all frequencies are tested. Description Maximum execution duration of a task Existing NE that supports RSSI test. Frequency to be tested in an RSSI task.
6.8.23 Parameters for Creating/Modifying/Copying Software Download

This section describes the parameters in the software download task. When creating or modifying software download task, you can set the parameters for software download task by referring the information described in this section.
Parameter NE Type Edition List Value Range Select the value from the drop-down list. None. Description Indicates all of the NE types available in the current network. Indicates the editions of all NEs that can be downloaded from the server. These NEs are of the same type. Multiple choices are not allowed. Indicates all of the NEs of an NE type available in the current network. Multiple choices are supported.
NE List
None.
Issue 10 (2010-09-06)
6-87
6.8.24 Parameters for Creating/Modifying/Copying Dual-Home Management

This describes the parameters used in dual-homing management. You can refer to these parameters when creating, modifying, or copying dual-home management.
Parameter Dual Homing Pairs Description Indicates the dual-homing pairs. For detailed information about dual homing, refer to LN Domain Management. Indicates the data resource type of the dual homing pairs to be checked. Data resource types vary depending on the version of dual-homing pair NE. Setting Select from the drop-down list.
Resource Type
Select the item in the Resource Type navigation tree. Enter the data resource type or key word in the Search box. Then the related resource types are listed under the Search box. You can doubleclick resource type to be checked.
Search
Use to search for the type of the data resource to be checked. The search conditions support case insensitive fuzzy search. Wildcard search is not supported.
Enter the data resource type of key word in the Search box.
6.8.25 Parameters for Creating/Modifying/Copying iSStar Script

This section describes the parameters in the iSStar script task. When creating or modifying iSStar scripts, you can set the parameters in the iSStar tasks by referring to the information described in this section.
Parameter Main File Value Range The main file is in .hsl format. The main file has a maximum size of 1 MB. Description The main file is the entry file for the execution of script files.
6-88
Issue 10 (2010-09-06)
Parameter Assistant File
Value Range The assistant file has a maximum size of 1 MB. None.
Description When the script files are being executed, the main file selects from assistant files if the main file need to invoke other script files. You need to select NEs when script files contain operations on several NEs. Multiple choices are supported.
NE Selection
6.8.26 Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log

This describes the parameters for exporting NE logs and can be taken as reference during the parameter modification. Table 6-33 lists the extended parameters. Table 6-33 Description of extended parameters Parameter NE Start Time Value Range None. The start time must meet the requirement of time format. Description Refers to all the NEs on the entire network. All NE upgrade logs within the time range specified by the start time and end time are to be queried. All NE upgrade logs within the time range specified by the start time and end time are to be queried. Operation logs are exported to .xml files. Refers to the path for saving NE logs.
End Time
The end time must meet the requirement of time format.
File Format File Path
The default file format must be retained. The default file path must be retained. The default path is /export/ home/omc/var/field/ UpgradeHistory/.
6.8.27 Parameters for Creating/Modifying/Copying a CME Upload Task

This describes the parameters of a CME upload task. When creating or modifying a CME upload task, you can refer to the parameter description and perform relevant operations.
Parameter All NE All NodeBs Under RNC Description After you select this option, the system uploads the configuration data of all the existing RNCs and NodeBs on the network. After you select this option, the system uploads the configuration data of all the NodeBs under the selected RNCs.
6.8.28 Parameters for Creating/Modifying/Copying Cell Parameters Compare Task

This describes the parameters involved in the CME cell algorithm comparison task. When creating or modifying a CME cell algorithm comparison task, you can refer to this part and perform relevant operations. A CME cell algorithm comparison task can be performed to compare the parameters in the Current area with the default parameters in the CME configuration template and then export the comparison results to the specified path. Parameter Cell Input Mode Select the NE of a Cell Description After you select this mode, you can specify the NEs of a cell whose parameters are to be compared. After you select this mode, you can import the list of cells whose parameters are to be compared. Select the name of the controller managing the cell. The M2000 automatically compares the parameters of all the cells managed by the selected controller. Select the template to be compared. The M2000 automatically compares the cell parameters with the default configuration parameters of the selected template. For example, you can select Default 2G Cell Template.
Import Cell
Select the NE of a Cell and the Template
NE
Template
6-90
Issue 10 (2010-09-06)
6.8.29 Parameters for Creating/Modifying/Copying Cell Consistency Check Task

This describes the parameters involved in the CME cell consistency check task. When creating or modifying a CME cell consistency check task, you can refer to this part and perform relevant operations.
A cell consistency check task can be performed to check that the data in the Current area complies with the selected check rules. Parameter NE Description Select the name of the controller managing the cell. The M2000 automatically compares the parameters of all the cells managed by the selected controller. Select check rules.
Rule
6.8.30 Parameters for Creating/Modifying/Copying a CME Current Area Export Task

This describes the parameters of CME Current Area Export tasks. When creating or modifying a CME Current Area Export task, you can refer to the information described in this part.
To manage the current data area, you can perform a CME data export task to export the data from the current data area for Northbound. Parameter Select Export Type Description Select the data to be exported and its file format. The parameter values are as follows:
l
XML format:

radio parameter transmission parameter radio and transmission parameter radio parameter transmission parameter radio and transmission paramete
CSV format:

Issue 10 (2010-09-06)
6-91
Parameter Select NE
Description Select one or multiple controllers of the cell to which the data to be exported belongs. If you select All NEs, the data in the current data areas under all the controllers is to be exported.
6.8.31 Parameters for Setting Time of Timing Tasks

This section describes the parameters of time for automatic suspending and automatic resuming timing tasks Table 6-34 lists the parameters of auto-suspend time and auto-resume time for timing tasks. Table 6-34 Descriptions of parameters for setting timing task time Parameter Suspend Time Description The system suspends an idle task and delay the time for using this task. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You can set the value manually. Alternatively, you can click
l l l l l l
and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS. YYYY stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
Resume Time
In the specified time, the system resume a suspended task and then the task is in the idle state and wait to be dispatched. If the timing task is not in the Idle state at the specified time, it fails to be suspended. You can set the value manually. Alternatively, you can click
l l l l l l
and select the time from the time select panel.
The time format is DD/MM/YYYY HH:MM:SS. YYYY stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
6-92
Issue 10 (2010-09-06)
6.8.32 Parameters for Selecting Objects for Device Check

This part describes the extended parameters for selecting objects for device check. You can refer to this part when creating device check tasks.
Parameter Device Check NE Device Check Item Description Displays the type of the NE that supports device check, such as RNC, NodeB, eNodeB, BSC6000, and OMC. Displays the specific NE. Grouped by topology or type. Displays the device check items supported by NEs.
CAUTION
l Check items vary according to NE versions. For detailed meaning
of each check item, refer to NE Reference Information.

l For the BSC6000, the device check enables you to perform update
check to ensure that the check items related to device update are normal.
6.8.33 Parameters for Collecting NM Logs Parameters

This describes the parameters of the M2000 log information collecting tool dialog box. When collecting NMS log files, refer to the information described here for parameter setting.
Parameter Server informatio n Server address Description Complies with the principles of IP address rules. Cannot be null. Port Number Indicates the port of the server. Value range: 1-65,536 The default value is 10119. Cannot be null. FTP User name Indicates a valid name that the user already registered to the M2000. Cannot be null. password Indicates the password that is used to log in to the target server. Cannot be null. Items selection Trace files in Local Host Trace files in server
Issue 10 (2010-09-06)
Collects the trace files from the M2000 client. Collects the trace files from the M2000 server.
6-93
Parameter Core files in server LMT trace files in server Start Time End Time Alarm diagnostic data NE Name Save Positions Save Positions
Description Collects the core files from the server. Collects the trace files from the local maintenance terminal (LMT). Indicates the start time for collecting trace files and core files. Indicates the end time for collecting trace files and core files. Collects the alarm synchronization signals of NEs. Collects the NEs involved in alarm diagnostic data. Indicates the directory for the collected diagnostic data.
6-94
Issue 10 (2010-09-06)
7 Managing M2000 Processes and Services
Managing M2000 Processes and Services
About This Chapter

This chapter 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 Services This section describes how to view, start, and stop M2000 system services.
Issue 10 (2010-09-06)
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 3rdTool_agent Process This section describes the 3rdToolService service and dependent services. 7.1.2 adn_agent Process This section describes the services and functions provided by the adn_agent process. 7.1.3 adss_agent Process This section describes the services and functions provided by the adss_agent process. 7.1.4 antenna_agent Process This section describes the services and functions provided by the antenna_agent process. 7.1.5 ce_agent Process This section describes the services and functions provided by the ce_agent process. 7.1.6 cmdc_agent Process This section describes the CmDcService service and dependent services. CmDcService is provided by the cmdc_agent process. 7.1.7 cmengine_agent Process This section describes the services and functions provided by the cmengine_agent process. 7.1.8 cmeserver_agent Process This section describes the services and functions provided by the cmeserver_agent process. 7.1.9 cmexp_agent Process This section describes the service and functions provided by the cmexp_agent process. 7.1.10 cmserver_agent Process This section describes the services and functions provided by the process cmserver_agent. 7.1.11 cnnhc_agent Process This section describes the services and functions provided by the cnnhc_agent process. 7.1.12 corba_agent Process This section describes the services and functions provided by the corba_agent process. 7.1.13 cpm_agent Process This section describes the services and functions provided by the cpm_agent process. 7.1.14 devdoc_agent Process This section describes the DevDocService service provided by the devdoc_agent process. 7.1.15 dsXXXX agent Process This section describes the services and functions provided by the dsXXXX_agent process. 7.1.16 eam_agent Process This section describes the services and functions provided by the eam_agent process. 7.1.17 fars_agent Process This section describes the service and function provided by the fars_agent process. 7.1.18 fmnotify_agent Process
This section describes the services and functions provided by the fmnotify_agent process. 7.1.19 FMPreServiceXXXX_agent Process This section describes the services and functions provided by the FMPreServiceXXXX_agent process. 7.1.20 fnlicense_agent Process This section describes the services and functions provided by the fnlicense_agent process. 7.1.21 glmssyn_agent Process This section describes the services and functions provided by the glmssyn_agent process. 7.1.22 ifms_agent Process This section describes the service and functions provided by the ifms_agent process. 7.1.23 ipqdt_agent Process This section describes the services and functions provided by the ipqdt_agent process. 7.1.24 ipm_agent Process This section describes the services and functions provided by the ipm_agent process. 7.1.25 irp_agent Process This section describes the functions provided by the irp_agent process. 7.1.26 itm_agent Process This section describes the ItmService service and the dependent services by the itm_agent process. 7.1.27 lcsserver_agent Process This section describes the services and functions provided by the lcsserver_agent process. 7.1.28 lic_agent Process This chapter describes the services and functions provided by the process lic_agent. 7.1.29 log_agent Process This section describes the LogService service and dependent services. LogService is provided by the log_agent process. 7.1.30 lte_agent Process This section describes the services and functions provided by the lte_agent process. 7.1.31 maintain_agent Process This topic describes the function of the MaintenanceService service, which is provided by the maintain_agent process. 7.1.32 manager_agent Process This section describes the services and functions provided by the manager_agent process. 7.1.33 medXXXX_agent Process This section describes the services and functions provided by the medXXXX_agent process. 7.1.34 nelicense_agent Process This section describes the services and functions provided by the nelicense_agent process. 7.1.35 neuser_agent Process This section describes the NeUserService service. NeUserService is provided by the neuser_agent process. 7.1.36 ngnffs_agent Process This section describes the NGNFullFillService service and dependent services.
7.1.37 ngnnis_agent Process This section describes the NGNNIService service and dependent services. 7.1.38 ngnni112_agent Process This section describes the services and functions provided by the ngnni112_agent process. 7.1.39 ngntestmanage_agent Process This section describes the services and functions provided by the ngntestmanage_agent process. 7.1.40 nhcservice_agent Process This section describes the services and functions provided by the nhcservice_agent process. 7.1.41 nicservice_agent Process This section describes the services and functions provided by the nicservice_agent process. 7.1.42 nimserver_agent Process This section describes the NIMServer service and the dependent service. NIMServer is provided by the nimserver_agent process. 7.1.43 nms_mml_agent Process This section describes the services and functions provided by the process nms_mml_agent. 7.1.44 partition_agent Process This section describes the services and functions provided by the partition_agent process. 7.1.45 pm_agent Process This section describes the services and functions provided by the process pm_agent. 7.1.46 pmexp_agent Process This section describes the services and functions provided by the process pmexp_agent. 7.1.47 pmmon_agent Process This section describes the services and functions provided by the process pmmon_agent. 7.1.48 pmncdXX01_agent Process This section describes the services and functions provided by the pmncdXX01_agent process. 7.1.49 porttrunk_agent Process This section describes the services and functions provided by the porttrunk_agent process. 7.1.50 proxy_agent Process This section describes the services and functions provided by the proxy_agent process. 7.1.51 PRSAssistantService_agent Process This section describes the services and functions provided by the PRSAssistantService_agent process. 7.1.52 prsdc_agent Process This section describes the services and functions provided by the prsdc_agent process. 7.1.53 prsfs_agent Process This section describes the services and functions provided by the prsfs_agent process. 7.1.54 prsreport_agent Process This section describes the services and functions provided by the prsreport_agent process. 7.1.55 prssum_agent Process This section describes the services and functions provided by the prssum_agent process. 7.1.56 rn_agent Process This section describes the services and functions provided by the rn_agent process.
7.1.57 ScriptModuleService_agent Process This section describes the services and functions provided by the ScriptModuleService_agent process. 7.1.58 scriptserver_agent Process This section describes the services and functions provided by the process scriptserver_agent. 7.1.59 sm_agent Process This section describes the services and functions provided by the process sm_agent. 7.1.60 snmp_agent Process This section describes the SnmpAgent service and the dependent services. The SnmpAgent service is provided by the snmp_agent process. 7.1.61 son_agent Process This section describes the services and functions provided by the son_agent process. 7.1.62 swm_agent Process This section describes the services and functions provided by the swm_agent process. 7.1.63 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.64 uap_agent Process This section describes the services and functions provided by the uap_agent process. 7.1.65 udpdispatch_agent Process This section describes the services and functions provided by the udpdispatch_agent process. 7.1.66 umgupdsvr_agent Process This section describes the services and functions provided by the umgupdsvr_agent process. 7.1.67 xftpXX01_agent Process This section describes the services and functions provided by the xftpXX01_agent process. 7.1.68 Processes and Services Related to Each Northbound Interface This section describes the processes and services related to each northbound interface. 7.1.69 Checking the Status of the M2000 Processes This section describes how to check the status of the M2000 processes. When the M2000 processes are not running normally, you need to locate faults and log in to the server to rectify the faults in time.
7.1.1 3rdTool_agent Process

This section 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. Required services: none
7.1.2 adn_agent Process

This section describes the services and functions provided by the adn_agent process. The adn_agent process provides the ADNService service.
The ADNService service supports the NodeB plug-and-play function. It provides various functions for newly constructed NodeBs, such as remote automatic activation and automatic fault detection. This helps engineers quickly deploy NodeBs. You can disable the service when it is not required. Required services: FaultService and PMService.
7.1.3 adss_agent Process

This section describes the services and functions provided by the adss_agent process. The adss_agent process provides the AdvancedSwitchService service. The AdvancedSwitchService service authenticates the MOI resources to enhance the security of the operations on the NEs, and deepen the security level hiberarchy. During the operation of the M2000, ensure that this service is running properly. Required services: CMServer, CmDcService, and MediationServiceXXXX.
7.1.4 antenna_agent Process

This section describes the services and functions provided by the antenna_agent process. The antenna_agent process provides the AntennaTune service. The AntennaTune service provides the functions of managing NodeB antennas and locating the faults related to GBSS antennas. Required service: EAMService.
7.1.5 ce_agent Process

This section 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. Required services: none.
7.1.6 cmdc_agent Process

This section 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. Required services: TopoAdapterService.
7.1.7 cmengine_agent Process

This section describes the services and functions provided by the cmengine_agent process.
The cmserver_agent process provides the CMEngine service. CMEngine manages the configuration of the network manager. Configuration management is independent of NEs or managed objects. When the M2000 is running, ensure that this service functions properly. Required services: TopoService.
7.1.8 cmeserver_agent Process

This section describes the services and functions provided by the cmeserver_agent process. The cmeserver_agent process provides the CmeServer service. The cmeserver_agent service provides the function of quickly configuring NEs. You can disable the service when it is not required. Required service: none.
7.1.9 cmexp_agent Process

This section describes the service and functions provided by the cmexp_agent process. The cmexp_agent process provides the CMExport service. The CMExport service provides the functions of exporting configuration files and exporting the configuration database. Through the CMExport service, you can set the NE whose configuration data is to be exported, set the save path and file format of the exported data, and export the NE configuration data by using the Management Information Tree (MIT). To enable the functions of exporting configuration files and exporting the northbound database, you need to ensure that this service is running normally. Dependent service: LicenseService.
7.1.10 cmserver_agent Process

This section describes the services and functions provided by the process cmserver_agent. The cmserver_agent process provides the CMServer service. CMserver configures the managed objects of the network manager. Configuration management is independent of NEs or managed objects. The CMServer provides channels for issuing MML commands and helps to receive the supplementary messages reported automatically by NEs. The CMServer provides the function of managing object groups and enables the M2000 to automatically and remotely commission the NodeB upgrade. When the M2000 is running, ensure that this service functions properly. Required services: TopoService.
7.1.11 cnnhc_agent Process

This section describes the services and functions provided by the cnnhc_agent process. The cnnhc_agent process provides the CNNHCService service. CNNHCService provides the functions of information collection and health check. Required service: none.
7.1.12 corba_agent Process

This section describes the services and functions provided by the corba_agent process. The corba_agent process provides the CorbaService service. The CorbaService provides the NBI on which the TMF 814 CORBA protocol runs. Required services: LicenseService, LogService, SecurityService.
7.1.13 cpm_agent Process

This section describes the services and functions provided by the cpm_agent process. The cpm_agent process provides the CPMService service, that is, the pool configuration management service. The Pool configuration management service provides users with the following functions:
l l l l l l l l
Creating a pool 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
Required services: none
7.1.14 devdoc_agent Process

This section 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. Required services: none
7.1.15 dsXXXX agent Process

This section describes the services and functions provided by the dsXXXX_agent process. The dsXXXX_agent process provides the DesktopServiceXXXX service.
Some typical process names are ds0101_agent and ds0102_agent. The corresponding service names are DesktopService0101 and DesktopService0102. dsXXXX_agent is a multi-instance process and XXXX refers to the process number. The DesktopServiceXXXX service presents and operates data on several types of clients such as the Java GUI client and the Web client. You can log in to the client only when the DesktopServiceXXXX service is running properly. During the operation of the M2000, ensure that this service is running properly. Required service: LicenseService.
7.1.16 eam_agent Process

This section describes the services and functions provided by the eam_agent process. The eam_agent process provides the EAMService, TopoAdapterService, and TopoService services. The EAMService service provides the function of NE access management and maintains a globally complete NE list. The EAMService service does not depend on any other services. The TopoAdapterService service provides the mediation for earlier versions so that the users who use the earlier versions can use the topology function. The TopoAdapterService service depends on the EAMService, TopoService, LogService, SecurityService, and LicenseService services. The TopoService service can maintain the relation between the devices in the subnet, create and delete subnets, nodes, and topology node, and move nodes among subnets. The TopoService service depends on the EAMService services.
7.1.17 fars_agent Process

This section describes the service and function provided by the fars_agent process. The fars_agent process provides the FarsService. The FarsService provides the function of tracing data collection, data analysis, and data collection management. To enable the tracing function, you need to ensure that the FarsService is running normally during the operation of the M2000. Dependent service: MediationServiceXXXX, and XXXX refers to the instance number.
7.1.18 fmnotify_agent Process

This section 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) by Alarm Streaming Interface. Disable FMNotify when the real-time alarm forwarding function is not required. Required service: LicenseService
7.1.19 FMPreServiceXXXX_agent Process

This section describes the services and functions provided by the FMPreServiceXXXX_agent process. The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service. The FMPreServiceXXXX_agent process is a multi-instance process. XXXX refers to the process number. The FMPreServiceXXXX service provides the function of prehandling faults. In an SLS system, you can deploy the FMPreServiceXXXX_agent process on the master node and several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent processes on one node. For example, you can deploy the FMPreService0101_agent, FMPreService0102_agent, and FMPreService0103_agent processes on the master node for providing the FMPreService0101, FMPreService0102, and FMPreService0103 services separately. You can also deploy the FMPreService0201_agent, FMPreService0202_agent, and FMPreService0203_agent processes on a slave node for providing the FMPreService0201, FMPreService0202, and FMPreService0203 services separately. Required service: FaultService.
7.1.20 fnlicense_agent Process

This section describes the services and functions provided by the fnlicense_agent process. The fnlicense_agent process provides the FNLicenseService service. The FNLicenseService provides the fix network management function of managing the license authorization information about EMS. The number of purchased licenses determines the number of available resources and whether the user can use a specific functional component. Required services: LicenseService.
7.1.21 glmssyn_agent Process

This section describes the services and functions provided by the glmssyn_agent process. The glmssyn_agent process provides the GLMSSynService service. The GLMSSynService periodically obtains the information about QChat cluster communication changes from the Group and List Management Server (GLMS) and then applies the information to CBSCs. You can stop this process if the QChat cluster communication is not required. Required services: CMServer
7.1.22 ifms_agent Process

This section describes the service and functions provided by the ifms_agent process. The ifms_agent process provides the FaultService. The FaultService collects alarm data from NEs and saves the data, thus providing the functions of querying, dumping, and analyzing the fault data. You can disable the service when fault management is not required.
Required service: none.
7.1.23 ipqdt_agent Process

This section describes the services and functions provided by the ipqdt_agent process. The ipqdt_agent process provides the IPQosDailingTest service. IPQosDailingTest tests the IP bearer network to obtain the QoS of the network so as to build a high performance network. The process can be stopped if the QoS dialing test on the IP network is not required. Required services: CMServer and CmDcService
7.1.24 ipm_agent Process

This section describes the services and functions provided by the ipm_agent process. The ipm_agent process provides the IPMService service. The IPMService service enables you to manage an IP network. To use the IP network management function, ensure that the IPMService service is running correctly during the operation of the M2000. Required services: none.
7.1.25 irp_agent Process

This section 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.
Required Services
The required service is the LicenseService.
7.1.26 itm_agent Process

This section describes the ItmService service and the dependent services by the itm_agent process. The itm_agent process provides the ItmService service. The ItmService service provides the function of integrated task management. Required services: LicenseService
7.1.27 lcsserver_agent Process

This section describes the services and functions provided by the lcsserver_agent process. The lcsserver_agent process provides the LCSServer service. LCSServer provides the function of handling the configuration of LTEs. Through LCSServer, users can edit, maintain, verify, import, and export LTE configuration data. This process can be stopped if the LTE configuration function is not required.
7.1.28 lic_agent Process

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

This section 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. Required services: none.
7.1.30 lte_agent Process

This section describes the services and functions provided by the lte_agent process. The lte_agent process provides the CommonLicService service and SSLManageService service. The CommonLicService service manages the information about NE license files, such as invalidity, export, and adjustment information. The SSLManageService service manages the SSL connections between the M2000 and NEs. It also manages the SSL certificates used by the SSL connections. During the operation of the M2000, ensure that this service is running properly. Required service: none.
7.1.31 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. Required services: none
7.1.32 manager_agent Process

This section 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. Required services: none
7.1.33 medXXXX_agent Process

This section describes the services and functions provided by the medXXXX_agent process. The medXXXX_agent process provides the MediationServiceXXXX service. The medXXXX_agent is a multi-instance process, and XXXX refers to the instance number. When the M2000 is running, the system dynamically generates new processes and services based on NE types and NE quantity. Some typical process names are med0101_agent, med0102_agent, and med0103_agent, and the names of the corresponding services are MediationService0101, MediationService0102, and MediationService0103. The MediationServiceXXXX service creates, deletes, and obtains the NE engines mirrored to the network devices from the M2000 system and also manages the related event interceptors. NEs of different types communicate with the M2000 system by using the corresponding NE engines through various network management protocols. In addition, the MediationServiceXXXX service can export performance result files on the basis of NEs. During the operation of the M2000, ensure that this service is running properly. Dependent services: PartitionService, UdpDispatchService, and PartitionService
7.1.34 nelicense_agent Process

This section 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. Required services: CMEngine.
7.1.35 neuser_agent Process

This section 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. Required services: none
7.1.36 ngnffs_agent Process

This section describes the NGNFullFillService service and dependent services. The ngnffs_agent process provides the NGNFullFillService. The NGNFullFillService service provides functions of the management domain and the subscriber number management. Required services: none
7.1.37 ngnnis_agent Process

This section describes the NGNNIService service and dependent services. The ngnnis_agent process provides the NGNNIService. The NGNNIService service provides functions of the north interface operation management. Required services: none
7.1.38 ngnni112_agent Process

This section describes the services and functions provided by the ngnni112_agent process. The ngnni112_agent process provides the NGNNI112Service service. The NGNNI112Service provides the NBI for the subscriber line test system. Required services: NGNTestManageService.
7.1.39 ngntestmanage_agent Process

This section describes the services and functions provided by the ngntestmanage_agent process. The ngntestmanage_agent process provides the NGNTestManageService service. The NGNTestManageService provides the fix access network test management function. Required services: none.
7.1.40 nhcservice_agent Process

This section describes the services and functions provided by the nhcservice_agent process. The nhcservice_agent process provides the NHCService service. The NHCService service provides the network health check function. The nhcservice_agent process is available only after you have installed the network health check components. If you plan to perform a heath check task, you must ensure this service is running properly. Required service: ITMService and EAMService.
7.1.41 nicservice_agent Process

This section describes the services and functions provided by the nicservice_agent process. The nicservice_agent process provides the NICService service.
The NICService service provides the network information collecting function. The nicservice_agent process is available only after you have installed the network information collecting components. If you plan to perform a network information collecting task, you must ensure this service is running properly. Required service: ITMService and EAMService.
7.1.42 nimserver_agent Process

This section 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. Required services: CmDcService, FaultService, and PMMonService.
7.1.43 nms_mml_agent Process

This section 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. Required service: LogService.
7.1.44 partition_agent Process

This section 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. Required services: none.
7.1.45 pm_agent Process

This section 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. Required services: none.
7.1.46 pmexp_agent Process

This section 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. Required services: LicenseService.
7.1.47 pmmon_agent Process

This section 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. Required services: PMService
7.1.48 pmncdXX01_agent Process

This section describes the services and functions provided by the pmncdXX01_agent process. The pmncdXX01_agent process provides the PMNCDServiceXX01 service. The pmncdXX01_agent is a multi-instance process and XX01 refers to the instance number. Generally, the process name is pmncd0101_agent and the name of the corresponding service is PMNCDService0101. By default, the system saves the performance data of the neighboring cells of the RNC and BSC in files. The database does not hold the data. To view the data of the neighboring cells, you need to import the data from the files to the database and then query the results. The PMNCDServiceXX01 service imports the performance data of the neighboring cells from the files to the database. When the M2000 is running, ensure that this service functions properly. Required services: PMService.
7.1.49 porttrunk_agent Process

This section 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.
7.1.50 proxy_agent Process

This section 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. Required services: none.
7.1.51 PRSAssistantService_agent Process

This section describes the services and functions provided by the PRSAssistantService_agent process. The PRSAssistantService_agent process provides the PRSAssistantService service. The PRSAssistantService service provides the function of generating reports in .html, .csv or .xls format. It also provides the function of transferring result files by email or through the FTP. After restarting the PRSAssistantService service, you need to restart the PRSReportService service. If you need to run the PRS module, the PRSReportService service cannot be stopped. Required services: none
7.1.52 prsdc_agent Process

This section describes the services and functions provided by the prsdc_agent process. The prsdc_agent process provides the PRSDcService service. The PRSDcService service provides the function of obtaining configuration data files and performance data files on schedule. Keep the service running during the operation of the PRS module. Required service: none.
7.1.53 prsfs_agent Process

This section describes the services and functions provided by the prsfs_agent process. The prsfs_agent process provides the PRSFsService service. That is, it provides the service for importing report data. The PRSFsService service provides the function of parsing configuration data files and performance data files on schedule. Keep the service running during the operation of the PRS module. Required service: none.
7.1.54 prsreport_agent Process

This section 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. Required services: none
7.1.55 prssum_agent Process

This section 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 (Performance Report Suite) 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. Required services: CMServer.
7.1.56 rn_agent Process

This section describes the services and functions provided by the rn_agent process. The rn_agent process provides the RNService service. The RNService service provides the user with the function of sending notifications by email or short message. Required service: LicenseService.
7.1.57 ScriptModuleService_agent Process

This section describes the services and functions provided by the ScriptModuleService_agent process. The ScriptModuleService_agent process provides the ScriptModuleService service. The ScriptModuleService service provides the function of managing applications. Required services: ItmService and LicenseService.
7.1.58 scriptserver_agent Process

This section 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. Required services: ItmService
7.1.59 sm_agent Process

This section 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. Required services: EAMService and LicenseService
7.1.60 snmp_agent Process

This section 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 data, through the SNMP protocol. Required services: LogService and LicenseService.
7.1.61 son_agent Process

This section describes the services and functions provided by the son_agent process. The son_agent process provides the SONService service. The SONService service provides a series functions for automatically managing networks, such as automatically detecting, configurating, and optimizing NEs. The DHCP module provides the function of automatically detecting the eNodeB, BWA, pBTS3701, NodeB, GSM Pico, PICO BTS, and TGW. The Easy Deployment System (EDS) module provides the function of automatically creating an LTE site. The Auto Neighbor Relation (ANR) module provides the functions of automatically detecting the neighboring cells of the LTE, querying neighboring cell parameters across cells, and modifying neighboring cell parameters. If the functions for automatically managing networks are not required, this service can be stopped. Required service: PMService
7.1.62 swm_agent Process

This section describes the services and functions provided by the swm_agent process. The swm_agent process provides the SWMService service. The SWMService manages the versions, configuration data, NE logs, and other files of some NEs. It also provides the download, upload, activation, and rollback functions. Ensure that this service works properly during the M2000 operation. Required services: none
7.1.63 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. Required services: PMService, SecurityService, and FaultService.
7.1.64 uap_agent Process

This section describes the services and functions provided by the uap_agent process. The uap_agent process provides the UAPService service. The UAPService service provides the Sock5 agent function on the M2000 server. Thus, when users cannot access the BAM server (make sure that the M2000 server normally connects to the BAM), the M2000 client can be started through the agent. The uap_agent process also provides the function of authenticating user operations to meet the requirement of authority and domain based management on the M2000. Required service: none.
7.1.65 udpdispatch_agent Process

This section 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. Required services: PartitionService
7.1.66 umgupdsvr_agent Process

This section describes the services and functions provided by the umgupdsvr_agent process. The umgupdsvr_agent process provides the UMGUpgradeService service. UMGUpgradeService provides the UMG upgrade function. Required service: none.
7.1.67 xftpXX01_agent Process

This section describes the services and functions provided by the xftpXX01_agent process.
The xftpXX01_agent process provides the XFTPServiceXX01 service. Through the XFTPServiceXX01 service, the M2000 actively uploads exported files through the northbound interface to the FTP server on the NMS side. The XFTPServiceXX01 service actively checks the alarms, configurations, performance files generated by the PMExport service or the pmexp_agent process. Based on the settings of the FTP server on the NMS side, the XFTPService service uploads the northbound alarm files, configuration files, performance files to the specified FTP server. The files that can be exported by the XFTPServiceXX01 are as follows:
l l l l l l
Northbound alarm file Northbound configuration file Northbound inventory file Northbound performance file CME northbound configuration file NodeB license file
Through the M2000 client, you can set the FTP server on the NMS side. When the M2000 is running, ensure that the xftpXX01_agent process works properly. Required services: none
7.1.68 Processes and Services Related to Each Northbound Interface

This section describes the processes and services related to each northbound interface. Table 7-1 describes the relations between northbound interfaces and their corresponding processes and services. Table 7-1 Relations between northbound interfaces and their corresponding processes and services Process irp_agent Service IRPService Northbound Interface
l
CORBA configuration interface CORBA alarm interface CORBA security interface Configuration database Performance database
l l l l
ifms_agent pmexp_agent
FaultService PMExport
Northbound alarm file interface Northbound performance file interface (measurement unitbased) Northbound performance file interface (NE-based)
Issue 10 (2010-09-06)
medXXXX_agent
MediationServiceXXXX
7-22
Process snmp_agent fmnotify_agent nms_mml_agent cmserver_agent cmexp_agent
Service SnmpAgent FMNotify NMSMMLServer CMServer CMExport
Northbound Interface Northbound SNMP interface Northbound alarm streaming interface Northbound MML interface Northbound inventory file interface Northbound configuration file interface
7.1.69 Checking the Status of the M2000 Processes

This section describes how to check the status of the M2000 processes. When the M2000 processes are not running normally, you need to locate faults and log in to the server to rectify the faults in time.
Prerequisite
l l
Context
Checking the states of the M2000 processes on the M2000 client requires only a few system resources and does not affect system performance.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on the M2000 server. See Figure 7-1.
Issue 10 (2010-09-06)
7-23
Figure 7-1 Process Monitor tab page
7.2 Managing M2000 Services

This section describes how to view, start, and stop M2000 system services. 7.2.1 Checking the M2000 Services This section describes how to check the M2000 services. When the M2000 services are not running normally, you need to locate faults and log in to the server to rectify the faults in time. 7.2.2 Viewing the States of M2000 Services This section 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.2.3 Starting the M2000 System Services This section describes how to start the M2000 system services. After you run the start_svc command, all the M2000 services are started. The system ignores the service that is already started and starts only the inactive services. 7.2.4 Stopping the M2000 Services After the M2000 system services are stopped, the performance data and alarm data of the managed NEs cannot be processed. After the M2000 services are resumed, the M2000 updates the data with the NEs and processes the data.
7.2.1 Checking the M2000 Services

This section describes how to check the M2000 services. When the M2000 services are not running normally, you need to locate faults and log in to the server to rectify the faults in time.
Prerequisite
l l
Context
Checking the M2000 services on the M2000 client requires only a few system resources and does not affect system performance.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Service Monitor tab to check the M2000 services. See Figure 7-2. Figure 7-2 Service Monitor tab page
NOTE
In the Status column, the green icon indicates that the corresponding process is normal; the red icon indicates the corresponding process is abnormal.
7.2.2 Viewing the States of M2000 Services

This section 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
l
In the displayed information, if the state of the service is running, you can infer that the service operate properly. In the displayed information, if the state of the service is not running, you can infer that the service is abnormal.
Service Agent: 3rdTool_agent [1 service(s)] pid: 15490 3rdToolService [running ] ... [All Services: 51 ] [Running: 51 ] [Not Running: 0 ]
NOTE
Host: 10.121.71.242
At the end of the displayed information, if the value of Not Running : is 0, you can infer that all the M2000 services operate properly. If another value is displayed, contact Huawei technical support engineers for assistance. The M2000 system generates processes and services dynamically during operation. Accordingly, the number of processes and services changes dynamically.
----End
7.2.3 Starting the M2000 System Services

This section describes how to start the M2000 system services. After you run the start_svc command, all the M2000 services are started. The system ignores the service that is already started and starts only the inactive services.
Prerequisite
Context
NOTE
The time required for starting M2000 system services is related to the actual environment. Generally, it takes about 20 minutes.
7-26
Issue 10 (2010-09-06)
Procedure
Step 1 Navigate to the installation directory of the M2000 server. The default installation directory of the M2000 server software is /opt/OMC. # cd /opt/OMC Step 2 Run the following commands: # . ./svc_profile.sh # start_svc
NOTE
l l
Before starting the M2000 server, ensure that the Sybase service is started. For details about how to start the Sybase service, see 14.2.2 How to Start the Sybase. When you start M2000 system services, the status of each service is displayed. If the status of a service is failed, it indicates that the service fails to be started. In this case, you can locate the fault by viewing the iMAP.troubleshooting.trace log. # more /export/home/omc/var/logs/iMAP.troubleshooting.trace
----End
7.2.4 Stopping the M2000 Services

After the M2000 system services are stopped, the performance data and alarm data of the managed NEs cannot be processed. After the M2000 services are resumed, the M2000 updates the data with the NEs and processes the data.
Prerequisite
Context
NOTE
The time required for stopping M2000 system services is related to the actual environment. Generally, it takes about 20 minutes.
Procedure
Step 1 Go 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 commands to stop the M2000 services: # . ./svc_profile.sh # stop_svc Step 3 Run the following command to check whether there is any output. # svc_ps

l
If no output exists, it indicates that the M2000 service processes are stopped. Perform Step 5 directly. If any output exists, proceed with Step 4.
Step 4 If some services continue running, run the following command to forcibly stop them: # kill_svc Step 5 Run the following command to terminate the M2000 daemon process. # stop_daem Step 6 Run the following command to check whether there is any output. # daem_ps
l
If no output exists, it indicates that the M2000 daemon process is stopped. Perform Step 8 directly. If any output exists, proceed with Step 7.
Step 7 If the daemon process continues running, run the following command to forcibly stop it: # kill_daem Step 8 Run the ps -ef |grep 9999 |grep -v grep command to check whether there is any output.
l l
If no output exists, it indicates that the M2000 services are stopped. If any output exists, run the stop_tao_services command to stop the TAO process.
----End
7-28
Issue 10 (2010-09-06)
8 Managing the M2000 Databases
Managing the M2000 Databases
About This Chapter

This chapter describes how to manage the M2000 databases. 8.1 M2000 Database The M2000 databases consist of the Sybase database and the M2000 server database. This chapter describes only the M2000 server database. After the installation of the M2000 server application software, the size of the M2000 server database is fixed. You can use Sybase commands to operate the M2000 server database. 8.2 Viewing the States of M2000 Databases This section 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 section describes how to dump the data in the M2000 databases. The data includes the performance data, NE operation logs, NE system logs, NE security logs, alarm data, NM operation logs, NM system logs, and NM security logs. You can configure an integrated task for dumping the data in the M2000 databases. 8.4 Backing Up M2000 Databases This section describes how to back up the M2000 databases. The M2000 databases are categorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb, sumdb, farsdb and omceamdb.
Issue 10 (2010-09-06)
8-1
8.1 M2000 Database

The M2000 databases consist of the Sybase database and the M2000 server database. This chapter describes only the M2000 server database. After the installation of the M2000 server application software, the size of the M2000 server database is fixed. You can use Sybase commands to operate the M2000 server database. The function of each M2000 server database is as follows:
l
omcdb: stores the configuration data of the M2000 and the data related to internal feature implementation. The omcdb database must exist in the M2000 system. omclogdb: stores log management data. The omclogdb database must exist in the M2000 system. omcsmdb: stores security management data. The omcsmdb database must exist in the M2000 system. omctmdb: stores topology management data. The omctmdb database must exist in the M2000 system. fmdb: stores the alarm data of the M2000 and NEs. The fmdb database must exist in the M2000 system. pmdb: stores the performance structure tables and performance measurement results of NEs. The pmdb database must exist in the M2000 system. swmdb: stores the files managed by the software management module and the configuration data related to NE versions. The swmdb database must exist in the M2000 system. pmcomdb: stores the static performance measurement data of NEs. The pmcomdb database must exist in the M2000 system. sumdb: stores the summary data of NEs. If the M2000 system is not configured with the PRS, the sumdb database does not exist. itfndb: When installing northbound components, you must create the itfndb database for storing the northbound configuration data, performance tasks, and performance threshold data. The itfndb database must exist in the M2000 system. farsdb: stores the signaling data of all the NEs managed by the M2000. If the M2000 system is not configured with the tracing function, the farsdb database does not exist. omctempdb: stores the buffer data required for internal implementation of the DesktopServiceXXXX service. The omctempdb database must exist in the M2000 system. omceamdb: stores the data of network management objects, such as NEs, subnets, and links. The omceamdb database must exist in the M2000 system.
8.1.1 farsdb Database The farsdb database stores the signaling data of all the NEs managed by the M2000. 8.1.2 fmdb Database This section describes the fmdb database, which stores the alarm data of the M2000 and the managed NEs. 8.1.3 itfndb Database This section describes the itfndb database, which stores the northbound configuration data, performance tasks, and performance threshold data. 8.1.4 omcdb Database
This section describes the omcdb database. The omcdb database stores the M2000 configuration data, security data, and internal data. 8.1.5 omceamdb Database This section describes the omceamdb database. The omceamdb database is used to store the data of network management objects, such as NEs, subnets, and links. 8.1.6 omclogdb Database This section describes the omclogdb database, which stores the M2000 log management data. 8.1.7 omcsmdb Database This section describes the omcsmdb database, which stores the security management data. 8.1.8 omctempdb Database This section describes the omctempdb database. The omctempdb database is used to store the buffer data required for internal implementation of the DesktopServiceXXXX service. 8.1.9 omctmdb Database This section describes the omctmdb database, which stores the topology management data. 8.1.10 pmcomdb Database The pmcomdb database is used for storing the static performance measurement data of NEs. 8.1.11 pmdb Database This section describes the pmdb database, which stores the performance structure tables and performance measurement results of NEs. 8.1.12 sumdb Database The sumdb database stores the summarized performance data of NEs for performance reports. 8.1.13 swmdb Database This section describes the swmdb database, which stores the file information about the software management module and the configuration data of NE versions.
8.1.1 farsdb Database

The farsdb database stores the signaling data of all the NEs managed by the M2000. The farsdb database requires at least 10 GB data space and 3 GB log space. If the M2000 system is not configured with the tracing function, the farsdb database is not available. The farsdb database consists of the following types of tables:
l l l
Static configuration data table Task table Task data table
Table 8-1 describes the name and function of each table in the farsdb database. Table 8-1 Tables of the farsdb database and the corresponding functions Table Name tbl_ProcessorInfo
Issue 10 (2010-09-06)
Function Static service configuration table

8-3
Table Name tbl_Field tbl_TaskInfo tbl_TaskNE Message type name_task ID
Function Static field configuration table Dynamic task record table Table recording the tasks reported to NEs Task data table created dynamically, which records the signaling data of the message type corresponding to a task
8.1.2 fmdb Database

This section describes the fmdb database, which stores the alarm data of the M2000 and the managed NEs. The space of the fmdb database must be greater than 3,700 MB. Table 8-2 lists the names and functions of tables in the fmdb database. Table 8-2 Tables of the fmdb database and the corresponding functions Table Name tbl_alm_log tbl_event_log Other tables Function Records alarm logs. Records event logs. Record the internal processing data of alarms.
NOTE
The system automatically divides the tbl_alm_log and tbl_event_log tables according to the size of alarms and events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1 and tbl_alm_log_2.
8.1.3 itfndb Database

This section 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-3 lists the name and function of each table. Table 8-3 Tables of the itfndb database and the corresponding functions Table Name tbl_JGeneralInfo tbl_JMoInstance tbl_JStatusRecord
8-4
Function Records the general information about tasks. Records the instances of tasks. Records the Status of tasks.
Issue 10 (2010-09-06)
Table Name tbl_JMeasurementCategory tbl_JSchedule tbl_MGeneralInfo tbl_MMoInstance tbl_MMeasurementCategory tbl_MThresholdPackElemen tbl_MAlarmRecord tbl_MStatusRecord Other tables
Function Records the measurement categories of tasks. Records the task scheduling. Records the general information about thresholds. Records the instances of thresholds. 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.1.4 omcdb Database

This section describes the omcdb database. The omcdb database stores the M2000 configuration data, security data, and internal data. The omcdb database requires at least 1,000 MB data space. Table 8-4 lists the names and functions of the tables in the omcdb database. Table 8-4 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 ne2_ as the prefix Tables with omc_ as the prefix Tables with rel_ as the prefix tbl_ADAllNeList tbl_ADNeStatus Function Records the information about MO examples. Records the information about versions. Records the information about the format of messages transferred between the and the NEs. Records the information about NE models. Records the data about network management. Records the associations between MOs. Records the information about the NodeBs to be commissioned. Records the information about the statuses of the NodeBs to be commissioned.
8-5
Issue 10 (2010-09-06)
Table Name tbl_AllNeInfo tbl_IPExg tbl_OmcSslOption tbl_nelicBaseInfo tbl_nelicTask tbl_nelicTaskEnv tbl_test_task_property tbl_test_local_path tbl_test_other_path tbl_test_log_result tbl_test_ping_report tbl_test_audit_result tbl_test_nblink_result tbl_test_ping_address tbl_SubareaInfo tbl_SubareaRes session_SessionEntity session_SessionMoc session_SessionOpInfo Other tables
Function Records the network management data. It is created to ensure that the M2000 is compatible with earlier versions. Records the IP configuration information about the NAT translation table. Records the SSL connection policy of the OMC for NEs. Records the basic information about NEs. Records the information about operation tasks. Records the information flow interacted between the M2000 server and client. Records the properties of the IPQoS test task. Records the intra-office test path. Records the inter-office test path. Records the test task logs. Records the signaling parameters on the bearer network. Records the audit results of calling and called parties on the bearer network. Records the audit result of the call completion rate on the bearer network. Records the information about address pairs sent by the host. Refers to the partition information table, which records the information about each node. Refers to the partition resource table, which records the resources of each node. Records the information about the operated NEs during a session. Records the information about the operated MOCs during a session. Records the information about the user operations during a session. Records other configuration data of the M2000.
8.1.5 omceamdb Database

This section describes the omceamdb database. The omceamdb database is used to store the data of network management objects, such as NEs, subnets, and links. The omceamdb database requires more than 500 MB disk space.
Table 8-5 lists the name and function of each table in the omceamdb database. Table 8-5 Name and function of each table in the omceamdb database Table Name tbl_sn tbl_ne tbl_nefeature tbl_link tbl_idresource tbl_sntype tbl_netype tbl_linktype tbl_sync tbl_nerelation tbl_maintenanceinfo tbl_locationinfo tbl_negroup tbl_negroupclass tbl_negroup2ne tbl_negrouptype tbl_devsnmppara tbl_dftsnmppara tbl_autodiscfilter tbl_autodischistory tbl_eamschedule tbl_autodiscresult Function Subnet information table NE information table NE feature table Link information table NMS object identification management table Subnet type table NE type table Link type table Data synchronization table NE relation table Maintenance personnel information table Device maintenance information table NE group information table NE group mode table NE group and NE relation table NE group type table SNMP device parameter table Default SNMP parameter table Auto-search IP filter table Auto-search history record table Scheduled-search parameter table Auto-search result table
8.1.6 omclogdb Database

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

This section describes the omcsmdb database, which stores the security management data. Table 8-7 lists the names and functions of the tables in the omcsmdb database. Table 8-7 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 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.
8-8
Issue 10 (2010-09-06)
Table Name tbl_SMUserNEUserMap tbl_SMUserTerminalMap tbl_SecurityObjectTable tbl_SessionIDTable tbl_StaticTypeRelationTable tbl_StaticTypeTable tbl_StaticTypeViewTable
Function Records the binding relations between users and NE users. Records the binding relations between users and terminals. 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.8 omctempdb Database

This section describes the omctempdb database. The omctempdb database is used to store the buffer data required for internal implementation of the DesktopServiceXXXX service. The omctempdb database requires more than 500 MB disk space. Table 8-8 lists the name and function of each table in the omctempdb database. Table 8-8 Name and function of each table in the omctempdb database Table Name tbl_instance name_subsystem name_function name Function Stores the buffer data required for internal implementation of the DesktopServiceXXXX service.
8.1.9 omctmdb Database

This section describes the omctmdb database, which stores the topology management data. The omctmdb database requires a disk space of more than 550 MB. Table 8-9 lists the names and functions of the tables in the omctmdb database. Table 8-9 Names and functions of the tables in the omctmdb database Table Name MOTSConfig MOTSDomain
Issue 10 (2010-09-06)
Function Records the topology configuration values, including the initial value and the maximum value assigned by ObjID. Records the information on topology domains.
8-9
Table Name MOTSLink MOTSNode MOTSSubnet MOTSSubtree MOTSVSubnet MOTSView MOTSViewObj TSTempLoc TSTempPos
Function 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.10 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. 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 l
Counter tables Template Tables Function Subsets and Period Tables
Counter tables
Compared with the data in other types of tables, the data in these tables is stable. Table 8-10 lists the name and function 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 systbl_Counters
8-10
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.
Issue 10 (2010-09-06)
Table Name systbl_Counter_Unit systbl_AllCounterCategory systbl_ComputeCounters
Function Records the units of all counters. Records the service features of each version. Records only the counters involved in calculation.
Template Tables
Template tables contain several tables that 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 tbl_CounterCategory tbl_CounterLevel tbl_FeatureStatus Function Records measurement objects. Records measurement periods. Records measurement counters. Records the information on suspended tasks. Records the status of each service feature. Records the status of each service counter. Records the status of all the service features on the M2000 operating environment.
Function Subsets and Period Tables

The measurement results are saved according to the function subset and period. Table 8-12 lists the name and function of each subset and table.
Issue 10 (2010-09-06)
8-11
Table 8-12 Function subsets and period tables in the pmcomdb database and their functions Table Name tbl_MeasObject_XXX_Y Function In the table name, XXX refers to the function subset ID and Y refers to the period index that ranges from 0 to 4. By comparing the tbl_MeasObject_XXX_Y with the result table named tbl_Result_XXX_Y, you can check the loss status and integrity of the results. Each time when the measured object changes, a message is recorded in the list.
8.1.11 pmdb Database

This section describes the pmdb database, which stores the performance structure tables and performance measurement results of NEs. 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
Template Tables Function Subsets and Period Tables
Template Tables
Template tables record measurement information. Table 8-13 lists the name and function of the table.
8-12
Issue 10 (2010-09-06)
Table 8-13 Template tables in the pmdb database and their functions Table Name tbl_SyncInfo Function Records the supplementary collection queues of performance results.
Function Subsets and Period Tables

The pmdb database stores the tables of measurement results categorized by function subsets and periods. Table 8-14 lists the name and function of the table. Table 8-14 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.
8.1.12 sumdb Database

The sumdb database stores the summarized performance data of NEs for performance reports. The size of the sumdb database equals to one thirds of the size of the pmdb database. That is, at least 4,500 MB database space is required. If the M2000 system is not configured with the PRS, the sumdb database is not available. The sumdb database consists of the following types of tables:
l l l l
Object type information table System setting information table Report information table Performance result table
Object Type Information Table

The object type information table consists of 12 tables, which save a group of relatively stable information. Table 8-15 lists the name and function of each table. Table 8-15 Name and function of each object type information table in the sumdb database Table Name t_NeType Function Records the NE type and manages the relevant information.
Issue 10 (2010-09-06)
Table Name t_PRSObjectType t_GroupObjType t_AttrObjType t_ConfigObjType t_ConfigObjTypeAttr t_CombObjType t_PmObjType t_CombTable t_FSS t_Item t_ObjTypeAggrRelation
Function Records the information about object types of each class. Records the information about object types of object groups. Records the information about object types of attribute classes. Records the information about object types of configuration classes. Records the attribute information about the configuration object type. Records the information about object types of combination classes. Records the relation between the PRS object type and the performance object type. Records the rule information about the combination table. Records the information about the extracted function subsets. Records counter information. Records the summarization relation between objects.
System Setting Information Table

The system setting information consists of 15 tables that record information related to system setting. Table 8-16 lists the name and function of each table. Table 8-16 Name and function of each system setting information table in the sumdb database Table Name t_Week t_SpecialDate t_BusyRule t_BusyTime t_BusyTimeArith Function Records the start date of a week. Records the definition information about special dates. Records the information about busy-hour planning. Records the information about busy hours. Records the information about the statistics on monthly busy hours.
Issue 10 (2010-09-06)
8-14
Table Name t_DefaultPeriod t_RawPeriod t_DefaultStorage t_CustomStorag t_LoadFlag t_MaxItemId t_RawHistoryInf t_RawResultNo t_SumHistoryInfo t_BusyHistoryInfo
Function Records the information about default periods. Records the information about the extraction period of original results. Records the default storage duration of results. Records the storage duration of results. Records the information about the summarization and extraction. Records the IDs of maximum available counters of NEs. Records the history of extracting original result tables. Records the result numbers of original result tables. Records the history of extracting summarization result tables. Records the information about busy-hour summarization result tables.
Report Information Table

The report information table consists of eight tables that record the information about the queried tables. Table 8-17 lists the name and function of each table. Table 8-17 Name and function of each report information table in the sumdb database Table Name t_Report t_Sheet t_SheetItem t_SheetFilter t_ItemFormat t_RelateReport t_TemplateInfo Function Records the information about reports. Records the information about the sheets. Records the counters of sheets. Records filtering information. Records the counter format information. Records the relation between reports. Records the basic information about the templates.
Issue 10 (2010-09-06)
8-15
Table Name t_TemplateObjInfo
Function Records the basic information about the templates and the objects.
Performance Result Table

The performance result table consists of multiple tables, which records the performance measurement results based on the function subset and the measurement period. Table 8-18 lists the name and function of each table. In Table 8-18, fssName, ObjLevel, and XXX in the tables whose names begin with d_ can be configured in the configuration file.
l l l
fssName refers to the name of a function subset. ObjLevel refers to the dimension of an object. In the tables whose names begin with d_, XXX refers to the ID of an object type.
Table 8-18 Name and function of each performance result table in the sumdb database Table Name f_fssName_Raw Function Indicates original result serial tables which record the original results. If the function subset is not extracted internally, the administration tool (AT) automatically names the function subset in the following format: F _ ID of the function subset. f_fssName_ObjLevel_H Indicates hourly serial tables which records the result information at hour dimension. The hourly summarization is based on the original results. Indicates daily serial tables which record the result information at day dimension. The hourly summarization is based on hourly summarization. Indicates daily serial tables which record the result information at week dimension. The weekly summarization is based on daily summarization. Indicates monthly serial tables which record the result information at month dimension. The monthly summarization is based on weekly summarization. Indicates the weekly busy-hour serial tables which record the weekly busy-hour results.
Issue 10 (2010-09-06)
f_fssName_ObjLevel_D
f_fssName_ObjLevel_W
f_fssName_ObjLevel_M
f_fssName_ObjLevel_WH
8-16
Table Name f_fssName_ObjLevel_MH d_XXX d_XXXGrp d_XXXGrpObject
Function Indicates the monthly busy-hour serial tables which record the monthly busy-hour results. Records the information about the objects to be configured. Records the information about the type of object groups. Records the information about object instances of object groups.
8.1.13 swmdb Database

This section 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-19 lists the name and function of each table. Table 8-19 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.2 Viewing the States of M2000 Databases

This section 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 Checking the Database Usage Information About the M2000 Server Through the M2000 Client This section describes how to check the database status through the M2000 client to know the usage of the databases. 8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands This section 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 Checking the Database Usage Information About the M2000 Server Through the M2000 Client
This section describes how to check the database status through the M2000 client to know the usage of the databases.
Prerequisite
l l
Context
This operation requires only a few system resources and does not affect system operation.
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Database Monitor tab to check the database status of the M2000 server. See Figure 8-1. Figure 8-1 Database Monitor tab page
NOTE
In the Status column, the green icon indicates that the usage of the corresponding database is normal; the red icon indicates that the usage of the corresponding database is abnormal. If the usage of a database exceeds the preset threshold, the icon in this column changes from green to red.
8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands
This section 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 Checking the Database Usage Information About the M2000 Server Through 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
After the Sybase server is started, run the following command to view the name of the database server: -bash-3.00$ ps -ef | grep RUN_ | grep -v grep In the command result, the value after the RUN_ 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 17046 dbuser 17050 1 1 0 0 Dec 11 ? Dec 11 ? 0:00 /bin/sh ./RUN_SYB 0:00 /bin/sh ./RUN_SYB_back
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
Issue 10 (2010-09-06)
8-19
(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. In the 10,000 MB data space, the free space is 10,193,312 KB. Therefore, the usage is 0.46%. In the 3,000 MB log space, the free space is 3,059,992 KB. Based on the database usage and the preset threshold, you can determine whether the database status is normal. Run the following command to exit: 1>exit ----End
8.3 Clearing M2000 Databases

This section describes how to dump the data in the M2000 databases. The data includes the performance data, NE operation logs, NE system logs, NE security logs, alarm data, NM operation logs, NM system logs, and NM 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
l
Dump conditions can be set according to the following aspects: execution type, execution time, and file saving format. After the data is dumped, the following data is saved in the default directory of the M2000 server and removed from the databases:

The performance data in the pmdb database The NE operation logs, NE system 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-20
Issue 10 (2010-09-06)
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 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 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 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 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 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 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 Task Management window, select NE System Log under the node Database Capacity Management from the Task Type navigation tree. Select a task in the right part of the 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 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 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 NE system logs in the swmdb database.
Step 5 Dump the alarm data in the fmdb database.
Issue 10 (2010-09-06)
4. 1. 2. 3. 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 Task Management window, select NM Operation Log Dump under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the 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 Task Management window, select NM System Log Dump under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the 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 Task Management window, select NM Security Log Dump under the Database Capacity Management node from the Task Type navigation tree. Select a task in the right part of the Task Management window, and then click Attribute. In the Attribute dialog box, set the dump parameters. Then, click OK.
Step 6 Dump the NM operation logs in the omclogdb database.
Step 7 Dump the NM system logs in the omclogdb database.
Step 8 Dump the NM security logs in the omclogdb database.
----End
8.4 Backing Up M2000 Databases

This section describes how to back up the M2000 databases. The M2000 databases are categorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb, pmcomdb, sumdb, farsdb and omceamdb.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to back up the M2000 system.
8-22
Issue 10 (2010-09-06)
Context
NOTE
The time required for backing up data is related to the actual environment. Generally, it takes about five hours. Do not suspend a periodic backup task. The reasons are as follows:
l l
The latest data fails to be restored after data lost caused by an accident, for example, the power-off of the server. The database logs dumped by the Sybase database are not cleared in time, which causes /export/ home to be used up.
Procedure
Step 1 On the main window, choose Maintenance > Task Management. The Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup from the navigation tree, and then double-click the Server Backup node. The Attribute dialog box is displayed, as shown in Figure 8-2. Figure 8-2 Periodic backup
Step 3 Click the Common Parameters tab, and then set Task Name and Start Time. Step 4 Click the Extended Parameters tab, and then set Server Full Backup Date, as shown in Figure 8-3.
Figure 8-3 Periodic backup
Step 5 Click OK. The system periodically backs up data. Step 6 If data is backed up on a tape and the tape is fully written during the backup, perform following operations to replace the tape with a new one. 1. The system automatically ejects the fully written tape and waits for you to replace the tape with a new one. As shown in Figure 10-5 of 10.2.5 Manually Backing Up the M2000 Dynamic Data, the Message 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. 2. Insert a new tape into the tape drive. The Message 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-24
Issue 10 (2010-09-06)

NOTE
If you do not replace the fully written tape within the wait time preset in the configuration file, the Message 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 perform a new full backup.
l l
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. After backing up the dynamic data on the tape, you can run the following command to view the contents of the tape: # gtar tf /dev/rmt/0
----End
Issue 10 (2010-09-06)
8-25
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 section describes how to manage the file systems and disks on the M2000 clients. 9.2 Managing Files and Disks on the M2000 Server This section describes how to manage the file systems and disks on the M2000 server.
Issue 10 (2010-09-06)
9-1
9.1 Managing Files and Disks on M2000 Clients

This section 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. 9.1.2 Clearing the Disk Space of an M2000 Client This section 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.
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. Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size of the initial version, that is, about 300 MB; T refers to the temporary space for saving patches, which is less than 20 MB; S refers to the size of mediation files, which ranges from 3 MB to 10 MB; N refers to the number of NE versions, which depends on the actual situation. Table 9-1 describes the parameters specified in the equations. Table 9-1 M2000 client software directory Directory client installation path 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 M2000 client installation path. The default path is C:\iManagerM2000Client. Refers to the directory for saving client programs. Refers to directory where executable files are located. 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 diagnosis tool.
M2000 client installation path\client \ext_runcfg M2000 client installation path\client\dtd
Refers to the directory where the files related to integrated components are located. Refers to the directory for saving the Dtd files.
9-2
Issue 10 (2010-09-06)
Directory M2000 client installation path\client\help M2000 client installation path\client \IDAPI32 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\client \update M2000 client installation path\client\cbb M2000 client installation path\client \configuration M2000 client installation path\client \features M2000 client installation path\client \plugins M2000 client installation path\uninstall M2000 client installation path\script M2000 client installation path\client\bin \run
Description Refers to the directory for saving the online help files. Refers to the directory for saving the localWS dynamic link libraries. 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 upgrade files. Stores the CBB files of the M2000 client. Stores the configuration files of the M2000 client. Stores the feature configuration files of the subsystems of the M2000 client. Stores the configuration files of the subsystems of the M2000 client as plug-ins. Refers to the directory for saving the uninstaller. Refers to the root directory of the iSStar script. Refers to the directory in which the files for configuring the startup parameters of the client and components are located.
Issue 10 (2010-09-06)
9-3
Directory M2000 client installation path\cau
Description Refers to the installation directory of the cau (Client Auto Upgrade) client software and the directory in which the version, document abstract, and group information about the M2000 client are located.
NOTE
l The cau(Client Auto Upgrade) client software
provides an upgrade detection mechanism that is based on the document abstract. It also compares the document abstract of the server with that of the client. If the document abstracts are not consistent, you need to upgrade the client.
l Based on the group information, the server groups
and packs all the client documents deployed on the server for the client to download, install, and upgrade. Based on the group information, the client also groups and packs all client files. Thus, when these files are being downloaded, they can be compared with those files grouped and packed by the server.
M2000 client installation path\jre M2000 client installation path\lib
Stores the Java virtual machine of the M2000. Stores the library files of M2000 client, remote notification client, script framework tool client and datamanager client.
9.1.2 Clearing the Disk Space of an M2000 Client

This section 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
9-4
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 section 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 operation and maintenance data of the NEs, and provides an interface to the NMS. 9.2.2 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client This section describes how to check the disk usage information about the M2000 server through the system monitor browser of the M2000 client. 9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands This section 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 section 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.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 operation and maintenance data of the NEs, and provides an interface to the NMS. The M2000 server runs on the Solaris platform. The M2000 system operation requires the following software:
l l l
Sybase database 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-2 lists the directories related to the M2000 server software.
Issue 10 (2010-09-06)
9-5
Table 9-2 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 third-party software is located. Refers to the directory where the log files, the performance files, and the files recording exported alarms are located. Refers to the directory where the compressed component files are located. Refers to the directory where the initialization script file that should be executed during the M2000 installation is located. Refers to the directory where the script file used for uninstalling the M2000 is located. Refers to the directory where the script files used for installing the M2000 are located. Refers to the directory for saving the webpage service files. Refers to the directory for saving the mediation files generated during the operation. Refers to the directory for saving resource monitoring files. Refers to the directory for saving the configuration data of the webpage server. Refers to the PRS control directory.
M2000 server installation directory/ bin M2000 server installation directory/etc
M2000 server installation directory/lib M2000 server installation directory/ lbin M2000 server installation directory/ 3rdTools M2000 server installation directory/ var M2000 server installation directory/ data M2000 server installation directory/ init M2000 server installation directory/ uninstall M2000 server installation directory/ install M2000 server installation directory/ webapps M2000 server installation directory/ med M2000 server installation directory/ resourcemonitor M2000 server installation directory/ tomcat M2000 server installation directory/ components
9-6
Issue 10 (2010-09-06)
Directory M2000 server installation directory/ medshare M2000 server installation directory/ sacscript M2000 server installation directory/ds M2000 server installation directory/ plugin M2000 server installation path/ upgrade M2000 server installation directory/res M2000 server installation directory/ hascript M2000 server installation directory/ tools /export/home/omc/var /export/home/omc/var/syslog /export/home/backup /export/home/sysm/ftproot/pm
Description Refers to the directory for saving the mediation files. Refers to the directory for saving the script files provided by the NIC module. Refers to the directory for saving the files related to the DesktopService service. Refers to the directory for saving the dynamic library files and configuration files related to plugin. Refers to the directory for saving the upgrade scripts. Refers to the directory where resource files are located. Refers to the directory for saving the platform script files. Refers to the directory where the script tools often used by the M2000 are located. Refers to directory where the M2000 operation data is located. 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.
M2000 server installation path/var/ itf_n/FileTransferIRP/PM /export/home/omc/var/fileint/cm /export/home/omc/var/fileint/pm /export/home/sysm/ftproot/NE name/ Software
Issue 10 (2010-09-06)
9-7
Directory /export/home/sysm/ftproot/NE name/ Data/NE fdn
Description Refers to the directory where the NE data backup is located.

NOTE
l The NE fdn is a code representing an NE sample in
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 on the Netra 240 server in the M2000 system should be configured with two 146 GB hard disks and partitioned according to Table 9-3. Table 9-3 Planning of the server disk partitions (Netra 240) Hard Disk No. 1 Partiti on No. 0 1 2 3 4 5 Partition Name / swap overlap /data /log /export/home Size (MB) 25000 8192 39000 14000 50000 Description Root partition Data exchange partition Disk mapping. Retain the default size. Application database partition Application database partition M2000 operation data partition
9-8
Issue 10 (2010-09-06)
Hard Disk No.
Partiti on No. 6 7
Partition Name /globaldevices -
Size (MB) 1024 10 to 260
Description Reserved Used for disk mirroring. You need not set the partition name and size. The system assigns the partition size automatically.
Used as the mirrored disk for the first hard disk
Sun Fire V890 Disk Partition and Disk Array Partition

A standard disk on the V890 in the M2000 system should be configured with six 146GB hard disks and one 6140 disk array. Two of the local disks are partitioned according to Table 9-4. The other four disks are idle. Table 9-4 Planning for disk partitioning on the server (V890) Hard Disk No. Partitio n No. 0 1 2 3 4 1 5 6 7 Partition Name / swap overlap /globaldevices Size (MB) 110000 20000 1024 10 to 260 Description Root partition Data exchange partition Disk mapping. Retain the default size. Reserved Used for disk mirroring. You need not set the partition name and size. The system assigns the partition size automatically.
The disk array consists of sixteen 146 GB hard disks. Two disks on the disk array are used for hot spares, and the remaining 14 disks are used for RAID5. Hot spares are used to replace the
faulty disks in the disk array. Two volumes are created on the 6140 disk array, and their size are the same. For details on how to plan volumes on the disk array, see Table 9-5. Table 9-5 Planning for the 6140 disk array Disk Array No. 1 Volume Name oss_v0 oss_v1 Size (GB) 810 810
Sun Fire E4900 Disk Partition and Disk Array Partition

A standard disk on E4900 server in the M2000 system is configured with two 146 GB hard disks and one 6140 disk array. Table 9-6 lists the partitions of local disks. Table 9-6 Planning for disk partitioning on the server (E4900) Hard Disk No. 1 Partiti on No. 0 1 2 3 4 5 6 7 Partition Name Size (MB) Description
/ swap overlap /globaldevices -
110000 20000 1024 10 to 260
Root partition Data exchange partition Disk mapping. Retain the default size. Reserved Used for disk mirroring. You need not set the partition name and size. The system assigns the partition size automatically.
The 6140 disk array consists of sixteen 146 GB hard disks. Two disks on the disk array are used for hot spares, and the remaining 14 disks are used for RAID5. Hot spares are used to replace the faulty disks in the disk array. Two volumes are created on the 6140 disk array, and their size are the same. For details on how to plan volumes on the disk array, see Table 9-7.
9-10
Issue 10 (2010-09-06)
Table 9-7 Planning for the 6140 disk array Disk Array No. 1 Volume Name oss_v0 oss_v1 Size (GB) 810 810
Sun T5220 Disk Partition

The Sun T5220 server is configured with four 146 GB disks, you can see Table 9-8 for the planning of the disk partitions. Table 9-8 Planning of the Sun T5220 server disk partitions Hard Disk No. 1 Partition No. 0 1 2 Partition Name / swap overlap Size (MB) 25600 16384 Description Root partition Data exchange partition Disk mapping. Keep the default size. M2000 operation data partition. No partition name is needed. Reserved Used for disk mirroring. You need not set the partition name.
3 4 5
96256
6 7
/globaldevices -
1024 10 to 260
2 3
Used as the mirroring disk for the first hard disk 0 1 2 overlap Disk mapping. Keep the default size. Sybase data
9-11
3
Issue 10 (2010-09-06)
102400
Hard Disk No.
Partition No. 4 5 6 7
Partition Name -
Size (MB) 35840 10 to 260
Description Sybase log Used for disk mirroring. You need not set the partition name.
The third and the fourth hard disks serve as hardware RAID1 for the M2000 operation data.
Sun M4000/M5000 Disk Partition and Disk Array Partition

A standard disk in the M4000/M5000 system should be configured with two 146 GB hard disks and one S3200 or S2600 disk array. The S3200 disk array consists of 16 x 146 GB hard disks and the S2600 disk array consists of 12 x 450 GB hard disks. The two local hard disks are partitioned according to Table 9-9. Table 9-9 Partitioning of the local server disks (M4000/M5000) Hard Disk No. Partitio n No. 0 1 2 Partition Name / swap overlap Size (MB) 110000 20000 Description Root partition Swapping partition Used for disk mapping. Fixed to the default size. Reserved Used for disk mirroring. You need not set the name or size of the partition. The partition size is allocated automatically by the system.
3 4 1 5 6 7
/globaldevices -
1024 10 to 260
9-12
Issue 10 (2010-09-06)
Hard Disk No. 2
Partitio n No.
Partition Name
Size (MB)
Description
Used as the mirroring disk for hard disk 1.
Partition the disks of the disk array according to Table 9-10 or Table 9-11. Table 9-10 Disk partitions of the S3200 disk array Hard Disk Seven hard disks act as RAID 5. Seven hard disks act as RAID 5. Two disks Size (GB) 800 800 Act as the hotspare disk Description Volume name oss_v0 Volume name oss_v1
Table 9-11 Disk partitions of the S2600 disk array Hard Disk Ten hard disks act as RAID 10. Size (GB) 671 671 671 Two disks Act as the hotspare disk Description Volume name oss_app0 Volume name oss_app1 Volume name oss_app2
9.2.2 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client
This section describes how to check the disk usage information about the M2000 server through the system monitor browser of the M2000 client.
Prerequisite
l l
Context
Checking the disk usage information about the M2000 server requires only a few system resources and does not affect system operation.
Issue 10 (2010-09-06)
9-13
Procedure
Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browser window is displayed. Step 2 Click the Hard Disk Monitor tab to check disk usage information about the M2000 server. See Figure 9-1. Figure 9-1 Hard Disk Monitor tab page
NOTE
In the Status column, the green icon indicates that the usage of the corresponding disk is normal; the red icon indicates that the usage of the corresponding disk is abnormal. If the usage of a disk exceeds the preset threshold, the icon in this column changes from green to red.
9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands
This section 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 to viewing the disk usage of the M2000 server.
-bash-3.00$ df -k The system displays the following information:

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 l
File system name File size (unit: KB) Used space Free space Disk usage Capacity percentage of the filled file system and the mounting point
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 section 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 about NEs and the M2000 server. Back up the files on a tape. The files are divided into the following types:
Files generated during alarm auto-dump Alarm dump files are stored in the /export/home/omc/var/ThresholdExport/FM 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 upgrade 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.
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:
<?xml version="1.0" encoding="iso-8859-1"?> <tracemonitor name="tracemonitor" mount="/imap/common/tracemonitor"> <strategy name="imap">  <param name="checktracetime">300</param>  <param name="tracebackupnum">50</param> </strategy> <strategy name="other"> <filename name="tao.trace"> <param name="filesize">200</param> <param name="tracebackupnum">20</param> </filename> </strategy> </tracemonitor>
In checktracetime, you can set the trace log monitor period. The system checks the trace file at the regular interval of 300s. In tracebackupnum, you can set the number of backup trace files for each process in the /opt/OMC/var/logs/tracebak directory. For a process, if the number of trace file backups in the tracebak folder exceeds the preset value, the system automatically deletes the oldest trace files in sequence.
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 Log Information Collector dialog box, select Core files in server. Click Collect. Save the collected core files to the path C:\iManagerM2000Client\client\diagnosis \collected files. C:\iManagerM2000Client is the default installation path of the M2000 client software.
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 technical support engineers. Because the size of the core files is large, you must compress the core files before sending them.
4. 5. 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. Stop the M2000 server. Delete the files in the /var/tmp directory. Delete other files that are no longer in use. 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
Clear up disks regularly. 1. 2.
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
Issue 10 (2010-09-06)
9-17

NOTE
5.
Switch to log in as user omcuser. 1> exit -bash-3.00$ su - omcuser Password: Password of omcuser
6.
Change to the directories /export/home/sysm/ftproot/CmSync/ and /export/home/ sysm/ftproot/pm/ to delete the folders of associated FDNs that are not listed in the database. -bash-3.00$ rm -r /export/home/sysm/ftproot/CmSync/neNE fdn -bash-3.00$ rm -r /export/home/sysm/ftproot/pm/neNE fdn
7.
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 folders of associated FDNs that are not listed in the database. # rm -r /opt/OMC/var/med/neNE fdn
----End
9-18
Issue 10 (2010-09-06)
10 Backing Up and Restoring the M2000
10
Context
Backing Up and Restoring the M2000
About This Chapter

This chapter describes how to back up and restore M2000 data.
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. Static data backup and system data backup are implemented by the Backup & Restore Tools (BRT). For details, see M2000 Backup and Restore Guide (BRT-Based, Sun). 10.1 M2000 Backup and Restore Solutions This section describes the backup scheme, backup strategy, and restore scenarios of M2000 dynamic data. 10.2 Backing Up and Restoring M2000 Dynamic Data This section describes how to back up and restore M2000 dynamic data.
Issue 10 (2010-09-06)
10-1
10.1 M2000 Backup and Restore Solutions

This section describes the backup scheme, backup strategy, and restore scenarios of M2000 dynamic data. 10.1.2 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.3 Scenarios of M2000 Data Restoration This section describes the dynamic data restore for typical scenarios.
10.1.1 Backup of M2000 Dynamic Data

This section 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 or the static data restoration is complete. 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, omctmdb, farsdb and omceamdb. 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/
CAUTION omc/var directory. Thus, do not delete the directory and the files in 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.
10-2
Issue 10 (2010-09-06)
Item
Contents Manual backup

l
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 When storage media is the hard disk in the M2000 server, the directory of the backup files is: /export/home/backup/omc. When storage media is the tapes in the M2000, the directory of backup files is:/dev/rmt/0.
CAUTION If a system has more than one tape drives, the directory of the backup files is the same as that of the tape drive, which is specified when backing up dynamic data on a tape.
The directory of backup files
When storage media is the hard disk in the NetBackup server, the directory of the backup files is: /export/home/backup/omc.
CAUTION Dynamic data of the M2000 is backed up to the directory:/export/home/ backup/omc. Then the system automatically packs the backup data and moves the backup data to the storage media on the NetBackup server.
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 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

Dynamic data backup is applicable to routine maintenance.
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 or allYYYYMMDDhhmmss.tar file, and the inc-YYYYMMDDhhmmss 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)", it indicates that the static data backup is performed on November 28, 2007.
10.1.3 Scenarios of M2000 Data Restoration

This section describes the dynamic data restore for typical scenarios. The M2000 system runs normally or the static data restoration is complete. It needs to roll back to the historical operational status such as the operational status of the last week.
10.2 Backing Up and Restoring M2000 Dynamic Data

This section describes how to back up and restore M2000 dynamic data. 10.2.1 Setting the Storage Device of Backup Data Using Solaris Commands This section describes how to set the storage device of backup data. 10.2.2 Setting the Storage Device of Backup Data Through the Client You can set the storage device for backup data through the client. 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 for you to replace it. By modifying the configuration file, you can set the wait time.
10.2.4 Periodically Backing Up the M2000 Dynamic Data This section describes how to periodically back up the M2000 dynamic data. 10.2.5 Manually Backing Up the M2000 Dynamic Data This section describes how to manually back up the M2000 dynamic data. 10.2.6 Restoring the M2000 Dynamic Data This section describes how to restore the M2000 dynamic data.
10.2.1 Setting the Storage Device of Backup Data Using Solaris Commands
This section describes how to set the storage device of backup data.
Prerequisite
Context
By default, 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 /export/home/omc/var/ etc/conf/maintainsvc.xml and /opt/OMC/tools/Backup/config/generalbus.cfg files. You can set the storage device for backup data when the M2000 is running.
CAUTION
l l
Do not modify the configuration files of storage devices when the backup is in process. When you perform a full backup, the new backup files replace 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 fail to be restored owing to the loss of certain backup data. If you set the backupMedia parameter to tape or all, label the tapes after the backup is complete. Do not replace the storage device when the backup is in process. For data security, back up the dynamic data to a tape. When recovering the static data and restoring the system, use the dynamic data backup files stored on the tape to recover the latest service data.
l l l
Procedure
Step 1 Ensure that the M2000 daemon is started. Run the following commands to check whether the M2000 daemon is started: # . /opt/OMC/svc_profile.sh # daem_ps
If ... There is any output after you run the daem_ps command There is no output after you run the daem_ps command
Then ... The M2000 daemon is started. Proceed with the next step. The M2000 daemon is not started. Run the following command to start the daemon: # 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 Find the line <param name="backupMedia">, and change the disk for the full and incremental backups to the actual storage device. The storage media of both full and incremental backup must be identical. Otherwise, the incremental backup fails.
<module name="all"> <param name="backupMedia">disk</param>
and
<module name="inc"> <param name="backupMedia">disk</param>
Table 10-2 lists the values of the backupMedia parameter. Table 10-2 Values of backup media Storage Media Hard disks on the M2000 server 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 device of the NetBackup server. After the operation, the M2000 server does not hold the backup data that is moved to the storage device. The storage device of the NetBackup server is determined by the Veritas backup and restore solution. The storage device is a tape drive, a tape library, or a disk.
Step 4 Save the file and quit. Step 5 To back up dynamic data on a tape, specify the path of the tape drive. Otherwise, go to Step 6.
1.
Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfg file by running the vi command. # cd /opt/OMC/tools/Backup/config # vi generalbus.cfg
2.
Search for the [STEP_TRANSFERTOMEDIA] area, and then set the value of tapepath_sun to the directory of the tape drive.
[STEP_TRANSFERTOMEDIA] ...... tapepath_sun=/dev/rmt/0 ......
NOTE
l l
This section takes /dev/rmt/0 as an example. Replace /dev/rmt/0 with actual directory of the tape drive during actual operations. If multiple tape drives are installed on the server, select a tape drive by referring to 14.1.4 How Do I Select the Tape Drive?.
3.
Save the file and quit.
Step 6 Load the configuration files of all the processes again. # SettingTool -cmd reload maintainsvc.xml ----End
10.2.2 Setting the Storage Device of Backup Data Through the Client
You can set the storage device for backup data through the client.
Prerequisite
l l
The M2000 server is running properly. The connection between the M2000 client and server is normal.
Context
You can set the storage device for backup data when the M2000 is running.
Issue 10 (2010-09-06)
10-7
CAUTION
l l
Do not modify the configuration files of storage devices when the backup is in process. When you perform a full backup, the new backup files replace the backup files that already exist on the disk. After you change the current storage device, for example, from Disk to Tape, you need to perform a full backup again. Otherwise, the dynamic data may fail to be recovered due to the loss of some backup data. Set the storage device to Tape or Disk and Tape, remove and label the tape when the backup is complete. Do not replace the storage device when the backup is in process. For data security, back up the dynamic data to a tape. When recovering the static data and restoring the system, use the dynamic data backup files stored on the tape to recover the latest service data.
l l l
Procedure
Step 1 Start the M2000 client and log in to the M2000 server. Step 2 Click Maintenance > Backup Management. The Backup Management interface is displayed, as shown in Figure 10-1. Figure 10-1 Setting the storage device (I)
Step 3 Click Reset. The Medium Type Setting dialog box is displayed. Set the storage device in the dialog box, and then click OK, as shown in Figure 10-2.
10-8
Issue 10 (2010-09-06)
Figure 10-2 Setting the storage device (II)
NOTE
l l
The parameter Veritas refers to the storage device of the NetBackup server. If the storage device is set to Veritas, the system automatically packs the backup data and moves the backup data to the storage device of the NetBackup server. After the operation, the M2000 server does not hold the backup data that is moved to the storage device. The storage device of the NetBackup server is determined by the Veritas backup and restore solution. The storage device is a tape drive, a tape library, or a disk.
Step 4 The Confirm dialog box is displayed, prompting you for a full backup after you modify the storage device. Click Yes. Step 5 When the change of storage device is complete, the Message dialog box is displayed. Click OK. Step 6 Perform a full backup. For details, see 10.2.5 Manually Backing Up the M2000 Dynamic Data. ----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 for you to replace it. By modifying the configuration file, you can set the wait time.
Prerequisite
Context
If multiple tapes are required for data backup, you can modify the relevant contents in the /opt/ OMC/tools/Backup/config/generalbus.cfg file to set the wait time for replacing a tape. By default, the wait time is set to 120 minutes. You can configure the wait time for replacing a tape when the M2000 is running.
Issue 10 (2010-09-06)
10-9
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 is started. Run the following commands to check whether the M2000 daemon is started: # . /opt/OMC/svc_profile.sh # daem_ps If ... There is any output after you run the daem_ps command There is no output after you run the daem_ps command Then ... The M2000 daemon is started. Proceed with the next step. The M2000 daemon is not started. Run the following command to start the daemon: # start_daem Step 2 Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfg file by running the vi command. # cd /opt/OMC/tools/Backup/config # vi generalbus.cfg Step 3 Search for the [STEP_TRANSFERTOMEDIA] area, and then set the value of changetape_timeout to the wait time for replacing a tape.
[STEP_TRANSFERTOMEDIA] ...... changetape_timeout=120 ......
NOTE
l l
The value of the changetape_timeout 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 Load the configuration files of all the processes again. # SettingTool -cmd reload maintainsvc.xml ----End
10.2.4 Periodically Backing Up the M2000 Dynamic Data

This section describes how to periodically back up the M2000 dynamic data.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized to perform relevant operations. The tape drive is connected properly, and 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
l
Generally, the M2000 dynamic data is backed up periodically. The periodic backup of the dynamic data is performed in full backup mode.
NOTE
The time required for backing up M2000 dynamic data is related to the actual environment. Generally, it takes about five hours. Do not suspend a periodic backup task. The reasons are as follows:
l l
Procedure
Step 1 On the main window, choose Maintenance > Task Management. The Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup from the navigation tree, and then double-click the Server Backup node. The Attribute dialog box is displayed, as shown in Figure 10-3.
Issue 10 (2010-09-06)
10-11
10-12
Issue 10 (2010-09-06)
Issue 10 (2010-09-06)
10-13

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

This section describes how to manually back up the M2000 dynamic data.
Prerequisite
l l l
You have logged in to the M2000 client. You are authorized with the relevant operation rights. The tape drive is connected properly, and 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
l
Manual backup is required in special or emergency situations such as the loss of backup tapes and the failure of the M2000 system. Manual backup can be full backup or incremental backup.
NOTE
The time required for backing up M2000 dynamic data is related to the actual environment. Generally, it takes about five hours.
Procedure
Step 1 In the main window, choose Maintenance > Backup Management. The Backup Management dialog box is displayed.
10-14
Issue 10 (2010-09-06)
Figure 10-5 Manual backup
If Backup Medium in Figure 10-5 does not meet the actual requirement, you can click Reset to change the backup medium before data backup. For details, see 10.2.2 Setting the Storage Device of Backup Data Through the Client. Step 2 On the Server Backup List tab page shown in Figure 10-5, click Full Backup to perform full backup. Click Incremental Backup to perform incremental backup. If the Status displays Succeeded, you can infer that the backup is successful.
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 following operations to replace the tape with a new one. 1. The system automatically ejects the fully written tape and waits for you to replace the tape with a new one. As shown in Figure 10-5, the Message 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. 2. Insert a new tape into the tape drive. The Message 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.
Issue 10 (2010-09-06)
10-15

NOTE
l l
----End
10.2.6 Restoring the M2000 Dynamic Data

This section describes how to restore the M2000 dynamic data.
Prerequisite
l l l
You have logged in to the system as user root. You have obtained the backup files for restoring the dynamic data. The Sybase database service is running properly.
Context
You can restore the M2000 based on the latest full backup and incremental backup files. After you restore the M2000, all the contents in the backup file package are restored. If certain data generated after the backup start time, such as the NE performance data or alarm data, is not compressed in the backup file package, the M2000 enables the automatic synchronization function to obtain data from NEs and process the data. During the restoration of the dynamic data, the M2000 services are stopped, and thus the performance data and alarm data of the managed NEs cannot be processed.
NOTE
The time required for restoring M2000 dynamic data is related to the actual environment. Generally, it takes about six hours.
Procedure
Step 1 If the backup files are stored on tapes of the tape drives connected to the M2000 server, perform the following steps to decompress the contents on the tape to a hard disk. Otherwise, go to Step 3. Insert the first tape that stores the dynamic data and run the following command: # /usr/sfw/bin/gtar xvPfM /dev/rmt/0
10-16
Issue 10 (2010-09-06)
CAUTION
l
If multiple tape drives are available in the system, you need to type the name of the tape drive that is used for backing up the dynamic data. The decompressed file is stored in the same path as the compressed file. It is not related to the path where you perform the decompression.
Step 2 If all the data is stored on one tape, perform Step 3 after the previous command is executed. Otherwise, decompress the data on other tapes to a hard disk. 1. Press the button on the tape drive to remove the tape when the following message is displayed. For details, see the manual delivered with the tape drive. Prepare volume #2 for '/dev/rmt/0' and hit return:
NOTE
You can also remove 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 the data on the second tape to a hard disk.
CAUTION
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: # /usr/sfw/bin/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 prompted. Prepare volume #3 for '/dev/rmt/0' and hit return: After all data on the tapes is decompressed to a hard disk, perform Step 3. Step 3 Change the right and owner of the /export/home/backup directory. # chmod -R 770 /export/home/backup # chown -R omcuser:omcsysm /export/home/backup Step 4 Restore the M2000 dynamic data. 1. Decompress the backup file that stores the to-be-restored dynamic data. # cd /export/home/backup/omc # tar xf backup file that stores dynamic data For example, if you need to restore the full backup file generated on 18:06:22 2008-01-30, decompress the relevant package.
# tar xf all-20080130180622.tar
NOTE
You need to decompress the relevant package regardless of the full backup file or the incremental backup file that is to be restored. For example, there are two decompressed files: all-20080130180622.tar and inc-20080131180622.tar. If you need to restore the system to the running state on 18:06:22 2008-01-30, decompress all-20080130180622.tar. If you need to restore the system to the running state on 18:06:22 2008-01-31, decompress inc-20080131180622.tar. You need not decompress all-20080130180622.tar.
2.
Navigate to the path after the decompression. # cd name of the backup file that stores dynamic data For example, # cd all-20080130180622
3.
Run the following script to restore the dynamic data: # ./restore.sh
4.
When the system displays the following prompt, type the password of user sa of the database.
Note: Enter q/Q to exit this tool. Please input the supperuser's password of database[default:emsems]:
NOTE
You can type q or Q to quit the script.
5.
When the system displays the following prompt, type 1 to start restoring the dynamic data. Please make a choice[1-2]:
NOTE
Restoring data takes a long time. Wait with patience.
After the restoration is complete, the system displays Operation succeeds.
CAUTION
If you have rebuilt the user database by using the BRT before restoring the dynamic data, you need to set the parameters of the user database by referring to the BRT backup and restore guide and then start the M2000 services. The reason of the previous operation is that the direct startup of the M2000 services may fail because the parameters of the rebuilt M2000 database are not set. Step 5 Run the following commands to restart the M2000 services: # . /opt/OMC/svc_profile.sh # cd /opt/OMC/tools/common # ./commonop.sh -ostartsvc
l
If the system displays the following information, it indicates that the M2000 service is started. In such a case, proceed with Step 6.
Operation succeeds
10-18
Issue 10 (2010-09-06)

l
If the system displays the following information, it indicates that the M2000 service fails to be started. In such a case, do not proceed with Step 6. Instead, contact Huawei technical support engineers for assistance.
Performing Start OMC services failed
NOTE
Starting the M2000 service takes a long time. Wait with patience.
Step 6 Run the following commands to delete the decompressed backup files: # cd /export/home/backup/omc # rm -rf directory for storing the decompressed backup files For example: # rm -rf all-20080130180622 ----End
Issue 10 (2010-09-06)
10-19
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. Specific maintenance items are required in real applications. 11.1 M2000 Routine Maintenance Items This section describes the recommended maintenance items of the M2000. 11.2 Daily Maintenance Operations This section describes the daily maintenance operations that need to be performed on the M2000. 11.3 Weekly Maintenance Operations This section describes the weekly maintenance operations that need to be performed on the M2000. 11.4 Monthly Maintenance Operations This section describes the monthly maintenance operations that need to be performed on the M2000.
Issue 10 (2010-09-06)
11-1
11.1 M2000 Routine Maintenance Items

This section describes the recommended maintenance items of the M2000. Table 11-1 lists the recommended maintenance items of the M2000. You can add or delete maintenance items according to the actual requirement. Table 11-1 List of maintenance items No. Item Mai nten ance Peri od Daily Daily Daily Daily Daily Daily Daily Reference
1 2 3 4 5 6 7
Check the status of performance measurement. Check the loss of performance results. Check the status of alarm reception. Check the status of the NMS connection. Check the status of the alarm box. Check OMC alarms or events. Check the connection between the M2000 and NEs. Check the M2000 logs. Check the error logs of the Solaris operating system. Check the hard disk usage of the M2000 server. Check the status of the M2000 database. Check the status of the M2000 services. Check the core file of the server.
All measurement counters and measurement objects are being measured. No performance result is 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 report the M2000 alarms in real time. No OMC alarm or event is generated. The connection between the M2000 and NEs is normal. The system runs properly. No abnormal or malicious operations are performed. No error log is generated. The usage of each disk is less than 90%. The database runs properly and its usage is less than 80%. All the services run properly, and no service is in not running state. No core file exists in the /export/home/ omc/var/logs directory.
8 9 10 11 12 13
Daily Daily Daily Daily Daily Daily
11-2
Issue 10 (2010-09-06)
No.
Item
Mai nten ance Peri od Daily Daily Wee kly
Reference
14 15 16
Check the hardware of the M2000 server. Check the results collected by the SMC. Check the configuration of alarm timing tasks.
The hardware of the M2000 server is not damaged. The operating environment of the M2000 server is normal. The time of alarm timing tasks is set properly. This prevents the time conflict with background tasks. The conflict may result in heavy CPU load. The time of automatic log dump is set properly. This prevents the time conflict with background tasks. The conflict may result in heavy CPU load. The time of NE log synchronization is set properly. This prevents the time conflict with background tasks. The conflict may result in heavy CPU load. The file server is configured properly. The time for automatically and periodically backing up the M2000 server and NEs is set properly. Backup files are generated in disks. The threshold of system monitoring is set properly. The time of NE configuration synchronization is set properly. The number of equivalent NEs managed by the M2000 does not exceed the management capability of the M2000. The M2000 routes are configured correctly. Back up the M2000 database and system files. View the backup files on disks and tapes. The time of the M2000 server is correct.
17
Check the configuration of automatic log dump.
Wee kly
18
Check the configuration of NE log synchronization time. Check the configuration of the file server. Check the configuration of the system backup.
Wee kly
19 20
Wee kly Wee kly
21 22
Check the configuration of system monitoring. Check the configuration of NE configuration synchronization time. Check the management capability of the M2000. Check the status of the M2000 routes. Back up the M2000.
Wee kly Wee kly Wee kly Wee kly Wee kly Wee kly
23
24 25
26
Check the time of the M2000 server.
Issue 10 (2010-09-06)
11-3
No.
Item
Mai nten ance Peri od Wee kly
Reference
27
Check the disk status of the M2000.
All the disks that are in use are online, the KSTATE columns of pl, sd, and v are ENABLED, and the STATE columns are ACTIVE. The usage of each partition is less than 80%. The power supply is normal. For details about how to check whether the CD-ROMs and tape drives run properly, see the related operating system administrator manuals. The disk array is not damaged.
28 29
Check the power supply of the M2000 server. Check the peripherals of the M2000 server.
Mont hly Mont hly
30
Check the front panel of a disk array.
Mont hly
For details about how to operate and maintain NEs, see the M2000 Online Help.
11.2 Daily Maintenance Operations

This section describes the daily maintenance operations that need to be performed on the M2000. 11.2.1 Checking the Status of Performance Measurement This section describes how to check the performance measurement state. You must ensure that all the required measurement counters and measurement objects are in proper status. 11.2.2 Checking the Missing Performance Result To ensure that no result is lost, you must check that the missing performance result exists. 11.2.3 Checking the Alarm Reception Check the alarm reception and ensure that the M2000 can receive alarms from NEs in real time. 11.2.4 Checking the NMS Connection This section describes how to check the NMS connection and to ensure that the NMS connection is normal. 11.2.5 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.2.6 Check OMC Alarms/Events This section describes how to check whether the M2000 system is normal. This section also describes how to check whether the alarms and events of the M2000 are generated. 11.2.7 Checking Connections Between the M2000 and NEs
This section describes how to check the connections between the M2000 and NEs. 11.2.8 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.2.9 Checking the Error Log of the Solaris This section describes how to check the error logs of the Solaris operating system. 11.2.10 Checking the Disk Usage of the M2000 Server This section 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.2.11 Checking the States of M2000 Databases This section 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.2.12 Checking the States of M2000 Services This section describes how to check the states of M2000 services. This operation requires very few system resources and does not affect system operation. 11.2.13 Checking the Core Files on the Server This section describes how to check the /export/home/omc/var/logs directory and to ensure that core files do not exist. 11.2.14 Checking the Hardware of the M2000 Server This section describes how to check the M2000 server hardware. 11.2.15 Checking the SMC Collection Results This section describes how to check the SMC collection results and to ensure that the M2000 server environment is normal.
11.2.1 Checking the Status of Performance Measurement

This section describes how to check the performance measurement state. You must ensure that all the required measurement counters and measurement objects are in proper status.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to perform performance management.
Procedure
Step 1 Choose Performance > Measure Management > Status Browser. The Measure Management window is displayed. Step 2 Ensure that all the required measurement counters and the measurement objects are in proper status. If there is any exception, contact Huawei technical support engineers for assistance. ----End
Issue 10 (2010-09-06)
11-5
11.2.2 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 > Status Browser. Step 2 From the navigation tree of the Measure Management window, right-click a node and then choose Missing Result from the shortcut menu. Step 3 In the displayed Query Missing Result dialog box, set the related parameters. Default end time = Current time. Default start time = Current time - Time range of the missing results in the preference settings. Step 4 Click OK. Any measurement result that is missing within the time range is listed in a table in the displayed dialog box. The first column of the table displays the object information. The second column displays the corresponding time range. ----End
Postrequisite
If missing measurement results exist, synchronize the results. 1. 2. 3. 4. Right-click a node in the navigation tree, and then choose Missing Result from the shortcut menu. In the Query Missing Result window, select an NE and a function subset whose missing results you want to query, and then click OK. In the dialog box of missing results, click Synchronize Result. In the Prompt dialog box, click OK. After the synchronization command is issued to the NE, it takes some time for the NE to report the performance measurement data. You can check whether the data is successfully reported by viewing whether the missing results disappear.
11.2.3 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.
11-6
Procedure
Step 1 Choose Monitor > Browse Alarm List. The Filter window is displayed. Step 2 Set filter condition, then click OK. Step 3 Ensure that the M2000 can receive the alarms reported by NEs in real time. ----End
11.2.4 Checking the NMS Connection

This section describes how to check the NMS connection and to ensure that the NMS connection is normal.
Procedure
Step 1 Ensure that the NMS can collect the alarms and performance data reported from the M2000 . ----End
11.2.5 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 Setting > Options. The Alarm Option 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
11.2.6 Check OMC Alarms/Events

This section describes how to check whether the M2000 system is normal. This section also describes how to check whether the alarms and events of the M2000 are generated.
Prerequisite
l l
You have logged in to the M2000 client. You are authorized to query alarms and events.
Issue 10 (2010-09-06)
Procedure
Step 1 Check whether the Local NM icon is colored or an alarm is displayed on it in the topology view. If the system is operational, no alarm is generated. That is, the Local NM icon is not colored or no alarm balloon is displayed. Step 2 Right-click the Local NM icon, and then choose Query Alarm/Event > Alarm List. The Browse Alarm List window is displayed.
l
If the alarms listed in Table 11-2 are generated, handle the alarms immediately. Table 11-2 Alarms that need to be handled immediately Alarm Name The OMC Service Is Terminated Abnormally The Disk Usage Is Too High (Critical) Power Failure Fan Failure CPU Temperature Is Abnormal Hard Disk Failure Disk Array Failure Power or Fan Failure To the Disk Array Cabinet Failure To the Devices in the Disk Array Cabinet A Disk on the Array Is Faulty Memory Failure CPU Failure Alarm ID 4 37 101 102 103 104 105 106 107 108 110 112
If the alarms listed in Table 11-3 are generated, you need to clear them within one day. Table 11-3 Alarms that need to be handled within one day Alarm Name NE Mediation Layer Version Unmatched Insufficient Free Space of the Performance Database License Invalid License Expired License On Trail Server Backup Unsuccessful Alarm ID 303 405 501 505 506 512
Issue 10 (2010-09-06)
11-8
During network expansion, multiple alarms listed in Table 11-4 are generated. In such a case, you can export the alarm statistical files every day and check the information in the Location Information column in the exported files. If the alarms are generated on the required NEs, you need to clear the alarms. Table 11-4 Alarms to be focused on during network expansion Alarm Name NE Is Disconnected Alarm ID 301
If the alarms listed in Table 11-5 are generated many times, you need to locate the user who has not obtained the M2000 login password and tries to log in to the M2000 to prevent malicious operations. Table 11-5 Alarms about malicious operations Alarm Name The Number of Login Attempts Reaches the Maximum Alarm ID 11
Step 3 Right-click the Local NM icon, and then choose Query Alarm/Event > Event Logs from the shortcut menu. The Query Event Logs window is displayed.
l
If the events listed in Table 11-6 occur, you need to handle them within one day. Table 11-6 Events that need to be handled within one day Event Name SMC Alarm Event ID 1099
During network expansion, multiple events listed in Table 11-7 occur. In such a case, you can export the event statistical files every day and check the information in the Location Information column in the exported files. If the events occur on the required NEs, you need to handle them. Table 11-7 Events that need to be focused on during network expansion Event Name Performance Result Loss Event ID 407
----End
Postrequisite
To handle alarms and events, perform the following steps:
1. 2.
In the Browse Alarm List or Query Event Logs window, select a specific alarm or event. In the Process Advice area, click Click here to show detail Information. Then, you can obtain the detailed information and troubleshooting suggestions from the displayed alarm or event online help. (Optional) When handling alarms, you also need to acknowledge uncleared alarms, and analyze and acknowledge the alarms that are automatically cleared. The acknowledged and cleared alarms do not exist in the window any longer. The cleared but not acknowledged alarms are displayed in a different color.
3.
4. 5. 6.
Double-click an alarm or event. The Detail Information dialog box is displayed. In the Experience area, click Modify. The Experience dialog box is displayed. In the Experience dialog box, type the information such as the symptom, cause, and recommended handling advice. The typed information is saved in the Experience area. Repeat 1 to 6 to handle each alarm or event. Ensure that the M2000 system is operational. No alarms or events occur if the M2000 system is operational.
7. 8.
11.2.7 Checking Connections Between the M2000 and NEs

This section 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 System > NE Monitor. The NE Monitor dialog box is displayed. You can check the connection status of NEs. There are three connection statuses: Connected, Break, and NA. Step 2 Handle exceptions. For the Break status, you must obtain and analyze system information in time and solve the problem. 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 3 Check whether the NEs are connected correctly. The status of all NEs is Connected. ----End
11.2.8 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 Query Operation Logs window is displayed. By default, the system opens the Filter window automatically. Step 2 Set query conditions in the Filter 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 3 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 4 Confirm that no error information exists in M2000 logs. The system works properly. No abnormal or unfriendly operations are performed. ----End
11.2.9 Checking the Error Log of the Solaris

This section describes how to check the error logs of the Solaris operating system.
Prerequisite
Before checking error logs of the Solaris, ensure that you have logged in to the M2000 server as user omcuser.
Context
l
Viewing the Solaris error logs occupies few system resources and does not affect system operation. The record format of the /var/adm/messages file and the /var/log/syslog file is as follows: date and time-hostname-description
NOTE
The /var/adm/messages file is the core system log file. It contains the boot information about system startup and other status information about system operation. The /var/log/syslog file records the messages exported to the system console and the messaged generated by the syslog system service.
Issue 10 (2010-09-06)
11-11

l
Generally, the messages such as err or failed are not displayed. If such messages are displayed, contact Huawei technical support engineers for assistance.
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
11.2.10 Checking the Disk Usage of the M2000 Server

This section 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 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.2.11 Checking the States of M2000 Databases

This section 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.2.12 Checking the States of M2000 Services

This section 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 System Monitor Browser window is displayed. Step 2 Click the Service Monitor or Process Monitor 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. If a certain process is still inactive, contact Huawei technical support engineers for assistance. Step 4 Check whether the M2000 works properly. The Status of all M2000 services is Running. ----End
11.2.13 Checking the Core Files on the Server

This section describes how to check the /export/home/omc/var/logs directory and to ensure that core files do not exist.
Prerequisite
You have logged in to the server as user omcuser.
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. -bash-3.00$ ls -ltr core* The core files are sorted by time. The file at the top is the earliest one. Delete the core files generated one week earlier. Contact Huawei technical support engineers to deal with the core files generated within the week. ----End
11.2.14 Checking the Hardware of the M2000 Server

This section 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.
NOTE
You can also run the prtdiag command to view the server type, which is contained in the system output.
Step 2 Check the server hardware based on the server model according to the delivery-attached manual of the server. 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 server. 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.2.15 Checking the SMC Collection Results

This section describes how to check the SMC collection results and to ensure that the M2000 server environment is normal.
Prerequisite
l l l
The SMC server software runs properly. The SMC client software runs properly. 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 operations, see the relevant manual of the SMC. You can obtain the relevant SMC manual at the Sun website. ----End
11.3 Weekly Maintenance Operations

This section describes the weekly maintenance operations that need to be performed on the M2000. 11.3.1 Checking the Configuration of Alarm Timing This section describes how to check whether the policy on automatic dumping alarm data from the alarm database is reasonable. 11.3.2 Checking the Configuration of Automatic Log Dump This section describes how to check whether the system of automatic dumping alarm data from the alarm database is satisfactory. 11.3.3 Checking the Synchronization Time of NE Log This section 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.3.4 Checking the Configuration of the File Server This section describes how to check whether the configuration of the file server is appropriate. 11.3.5 Checking the Configuration of System Backup This section 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 section also describes how to check whether backup files are generated in the disk.
11.3.6 Checking the Configuration of System Monitoring This section describes how to check the configuration of system monitoring. 11.3.7 Checking the Synchronization Time of NE Configuration This section 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 is performed simultaneously with other tasks on the server. 11.3.8 Checking the Threshold of Network Management Capability This section 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.3.9 Checking the Status of the M2000 Routes This section describes how to check the configuration of the M2000 routes. 11.3.10 Backing Up the M2000 This section 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, farsdb and omceamdb. The M2000 system files refer to those files in the directories /export/home/omc/var and / export/home/sysm. 11.3.11 Checking the Time of the M2000 Server This section describes how to check the time of the M2000 server. 11.3.12 Checking the States of M2000 Disks This section 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.3.1 Checking the Configuration of Alarm Timing

This section 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.
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 Attribute. Step 4 In the Attribute 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.2 Checking the Configuration of Automatic Log Dump

This section 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. 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 NE operation log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 3 Check the configuration of automatic log dump of NE security logs. 1. 2. 3. 4. 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 NE security log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 4 Check the configuration of automatic log dump of NE system logs. 1. 2. 3. 4. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select NE System Log. Choose the task in the right pane. Click Attribute. Check the configuration of auto NE system log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 5 Check the configuration of automatic log dump of NM operation logs. 1. 2. 3. 4. Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select NM Operation Log Dump. Choose the task in the right pane. Click Attribute. Check the configuration of auto NM operation log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 6 Check the configuration of automatic log dump of NM system logs. 1. 2.

Issue 10 (2010-09-06)
Under the Database Capacity Management node in the Task Type navigation tree in the left pane, select NM System Log Dump. Choose the task in the right pane. Click Attribute.
3. 4. 1. 2. 3. 4.
Check the configuration of auto NM 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 NM Security Log Dump. Choose the task in the right pane. Click Attribute. Check the configuration of auto NM security log dump in the Attribute window. Ensure that the configuration is reasonable.
Step 7 Check the configuration of automatic log dump of NM security logs.
----End
11.3.3 Checking the Synchronization Time of NE Log

This section 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.3.4 Checking the Configuration of the File Server

This section 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.
11-18
Procedure
Step 1 Choose Software > File Server Setting. The File Server Setting window is displayed. Step 2 Select the NE type in the ROOT 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.3.5 Checking the Configuration of System Backup

This section 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 section 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. 5. 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. 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.3.6 Checking the Configuration of System Monitoring

This section describes how to check the configuration of system monitoring.
Context
The recommended thresholds of the CPU usage, memory usage, and database usage are 80%.
Procedure
Step 1 Choose Monitor > System Monitor > Configurations. The System Monitor Settings dialog box is displayed. Step 2 Click the Server Monitor tab to check whether the settings of the CPU usage and memory usage thresholds are appropriate. Step 3 Click the Hard Disk Monitor tab to check whether the settings of the disk usage thresholds are appropriate. Step 4 Click the Database Monitor tab to check whether the settings of the database usage thresholds are appropriate. Step 5 Click the Service Monitor tab to check whether the settings of the service status refresh interval thresholds are appropriate. ----End
Example
For details about the parameters for monitoring the server, see Table 11-8.
11-20
Issue 10 (2010-09-06)
l
Server status refresh interval (seconds)
Description: Refresh interval for server monitoring, that is, the CPU usage is sampled every x seconds. Description: Used to set Threshold for Alarm Generation, Threshold for Alarm Clearance for the CPU usage alarm and whether to enable the bubble.
Value: Value range: 2-60. Default value: 15.
CPU used rate (%)
Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50.
Issue 10 (2010-09-06)
11-21
Name Memory used rate (%)
Description Used to set Threshold for Alarm Generation and Threshold for Alarm Clearance for the memory usage alarm.
l
Settings Value: Value range: 1-99. Default value: 60. Offset value range: 1-99. Default value: 50.
Table 11-9 describes the parameters for monitoring the disks of the server. Table 11-9 Hard Disk Monitor Name Disk Monitor Parameter Settings Hard disk status refresh interval (seconds) Description Description: Refresh interval for hard disk monitoring. Settings Value: Value range: 60-3600 Default value: 60
11-22
Issue 10 (2010-09-06)
l

l l l l
Issue 10 (2010-09-06)
11-23
l
l If you select
l If you select
11-24
Issue 10 (2010-09-06)
Table 11-10 describes the parameters for monitoring the database of the server. Table 11-10 Database Monitor Name Database Monitor Parameter Settings Database status refresh interval (seconds) Description Description: Interval of database refreshing. Settings Value: Value range: 300-3600 Default value: 300 Database Monitor Threshold Settings Default Value Setting (%) Description: All default thresholds of database usage on the M2000 server.
l

l l l l
Issue 10 (2010-09-06)
11-25
l
l

Table 11-11 describes the parameters for monitoring the server services. Table 11-11 Service Monitor Name Services Monitor Parameter Settings Service status refresh interval (seconds) Description Description: Interval of service refreshing. Settings Value: Value range: 60-3600 Default value: 60
11-26
Issue 10 (2010-09-06)
l if a monitored

l You can double-
11.3.7 Checking the Synchronization Time of NE Configuration

This section 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 is performed simultaneously with other 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 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.3.8 Checking the Threshold of Network Management Capability

This section 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
Step 1 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.3.9 Checking the Status of the M2000 Routes

This section describes how to check the configuration of the M2000 routes.
Prerequisite
You have logged in the M2000 server as user root.
Procedure
Step 1 Check the configuration of the current route. # netstat -rnv ----End
11.3.10 Backing Up the M2000

This section 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, farsdb and omceamdb. 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.
11-28
Issue 10 (2010-09-06)
Context
NOTE
The time required for backing up data is related to the actual environment. Generally, it takes about five hours. Do not suspend a periodic backup task. The reasons are as follows:
l l
Procedure
Step 1 On the main window, choose Maintenance > Task Management. The Task Management dialog box is displayed. Step 2 Choose Task Type > Backup > Server Backup from the navigation tree, and then double-click the Server Backup node. The Attribute dialog box is displayed, as shown in Figure 11-1. Figure 11-1 Periodic backup
11-30
Issue 10 (2010-09-06)

NOTE
l l
----End
11.3.11 Checking the Time of the M2000 Server

This section describes how to check the time of the M2000 server.
Prerequisite
You have logged in to the M2000 as user root.
Procedure
Step 1 Check the time of the M2000 server. # 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.5.7 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 Setting the M2000 Time. If the M2000 is configured with the NTP service and the NTP service is not running properly, handle the problem according to 2.5 Configuring the NTP Service of the M2000.
Step 4 Check whether the M2000 works properly. Ensure that the server time is correct. ----End
11.3.12 Checking the States of M2000 Disks

This section 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 server 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 group 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.4 Monthly Maintenance Operations

This section describes the monthly maintenance operations that need to be performed on the M2000. 11.4.1 Checking the Power Supply of the M2000 Server This section describes how to check the power supply of the M2000 server. 11.4.2 Checking the Peripherals of the M2000 Server This section describes how to check the peripherals of the M2000 server, such as the CD-ROM drive and the tape drive. 11.4.3 Checking the Front Panel of a Disk Array This section describes how to check the front panel of each disk array to determine whether a disk array is damaged.
11.4.4 Querying the M2000 License This topic describes how to query the license file on the M2000 server through the M2000 client.
11.4.1 Checking the Power Supply of the M2000 Server

This section 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. 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 delivery-attached manual of the server. 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.4.2 Checking the Peripherals of the M2000 Server

This section 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.4.3 Checking the Front Panel of a Disk Array

This section describes how to check the front panel of each disk array to determine whether a disk array is damaged.
Procedure
Step 1 Check whether the LED indicator of the front panel of a disk array is yellow. If the LED indicator is yellow, you can infer that a configuration or hardware fault occurs on the power supply, controller, or disk array. In this case, contact Huawei technical support engineers for assistance. ----End
11.4.4 Querying the M2000 License

This topic describes how to query the license file on the M2000 server through the M2000 client.
Procedure
Step 1 Choose Help > License Information from the main menu. Step 2 In the License Information dialog box, query the license information about resources and functions on the Resource control item and Function control item tabs. ----End
11-34
Issue 10 (2010-09-06)
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 section 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 section 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 10 (2010-09-06)
12-1
12.1 Guide to Emergency Maintenance of the M2000 Server

This section 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 the BRT tool You can use the BRT tool to back up operating system data on a tape. To restore system data, you need to boot the server by using the installation CD-ROM of the operating system, restore the BRT tool from the tape, and then restore the system data by using the script in the BRT tool.
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.
12.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure
This section 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 section 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 section 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 section 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 section 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 section 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/RSC/XSCF 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 section 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/RSC/XSCF 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/ASE-15_0/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 section describes how to handle the loss of database device files after the file system is restored.
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 section describes how to handle the failure to restore the database though the file system is intact.
Symptom
After the server is shut down exceptionally, the operating system can be restarted normally. The file system can work normally, and the database service can be started. Part of databases, however, are in the suspect status and cannot be started. After checking the application database, find that the application database is in the offline status. To check whether a database is in the offline status, run the following commands: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_helpdb 2> go The database log file /opt/sybase/ASE-15_0/install/database server name.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.
Issue 10 (2010-09-06)
12-5

NOTE
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 For details on how to stop the database service, see 14.2.3 How Do I Stop the Sybase?. -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/ASE-15_0/database server name.cfg are changed to the default values. If all the values are changed to the default values, restore the database by using the history file. (1) Run the following commands to query the last history file: # cd /opt/sybase/ASE-15_0 # ls -l database server name.* The command result is similar with the following information:
-rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r-1 1 1 1 1 dbuser dbuser dbuser dbuser dbuser staff staff staff staff staff 9620 9690 9696 9690 9696 Jun Jun Jun Jun Jun 24 24 24 24 24 16:26 16:26 16:26 16:26 16:27 SYB.001 SYB.002 SYB.003 SYB.004 SYB.005
12-6
Issue 10 (2010-09-06)

-rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rwxrwxrwx -rw------1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser dbuser staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff staff 9690 9696 9690 9696 9690 9696 9690 9696 9690 9696 9690 9696 9690 9696 9695 9694 9693 9801 9797 9794 9792 9790 9785 9780 9779 9778 9772 9770 9764 9758 9756 9753 9752 9753 9752 59

Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun Jul Aug Jul Aug 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 9 6 9 6 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:27 16:34 16:34 16:34 16:34 16:34 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 16:35 09:51 11:25 09:51 11:25 SYB.006 SYB.007 SYB.008 SYB.009 SYB.010 SYB.011 SYB.012 SYB.013 SYB.014 SYB.015 SYB.016 SYB.017 SYB.018 SYB.019 SYB.020 SYB.021 SYB.022 SYB.023 SYB.024 SYB.025 SYB.026 SYB.027 SYB.028 SYB.029 SYB.030 SYB.031 SYB.032 SYB.033 SYB.034 SYB.035 SYB.036 SYB.037 SYB.038 SYB.bak SYB.cfg SYB.krg
As indicated in the command result, SYB.038 is the last history file. (2) Run the following command to use the last history file to restore /opt/sybase/ ASE-15_0/Database server name.cfg. This takes SYB and SYB.038, which are the database server name and the last history file respectively, as an example. # cp SYB.038 SYB.cfg # chown dbuser:staff SYB.cfg 4. Start the Sybase. # su - dbuser For details about how to start the Sybase, see 14.2.2 How to Start the Sybase. -bash-3.00$ exit 5. Run the environment variable script as user root. # 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. 6.
Issue 10 (2010-09-06)
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 7. Restart the Sybase. For details on how to stop the database service, see 14.2.3 How Do I Stop the Sybase?. For details about how to start the Sybase, see 14.2.2 How to Start the Sybase.
12-8
Issue 10 (2010-09-06)
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 section 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 section describes how to collect the M2000 site and software information. 13.3 Collecting Fault Data Using the Log Information Collector This section describes how to collect fault data by using the M2000 log information collector.
Issue 10 (2010-09-06)
13-1
13.1 Procedure for Troubleshooting the M2000

This section 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
Logs are categorized into user logs, system logs, and trace files. For details on viewing database deadlock information, refer to 14.2.6 How to View Database Deadlock Information.
Locating Faults
This section 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 section 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. 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.
13-2
Issue 10 (2010-09-06)
For details on the server faults, refer to the 14.4 About Server Software.
l
Faults of the Solaris operating system Refer to the Solaris System Administrator Guide. You can download the Solaris System Administrator Guide at the website of the Sun corporation.
Sybase faults Refer to the Sybase System Administrator Guide. The Sybase System Administrator Guide can be obtained from the CD delivered with the server.
Uncleared faults For the uncleared faults, collect all the information related to the faults by referring to Collecting Data and contact Huawei technical support engineers for assistance.
13.2 Collecting M2000 Site and Software Information

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

This section describes how to collect the M2000 site information.
Procedure
Step 1 Collect the M2000 site information. Collect the following site information:
l l l l
Site name Customer contact details Hardware model Date and time when a fault occurs
Issue 10 (2010-09-06)

l
Fault description
----End
13.2.2 Collecting the Time of M2000 Fault Occurrence

This section describes how to find out the time when M2000 faults occur.
Procedure
Step 1 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 section describes how to obtain the IP address of the M2000 server.
Procedure
Step 1 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 section describes how to obtain the version information about the Solaris.
Procedure
Step 1 Run the uname -aX command to find out the version information about the Solaris operating system. ----End
Example
# uname -aX
A message similar to the following message is displayed:

SunOS BackupServer 5.10 Generic_138888-07 sun4u sparc SUNW,Netra-240System = SunO S Node = BackupServer Release = 5.10 KernelID = Generic_138888-07 Machine = sun4u BusType = <unknown> Serial = <unknown> Users = <unknown> OEM# = 0 Origin# = 1 NumCPU = 2
In the system output, Release specifies the version of the operating system and its value is 5.10; KernelID specifies version ID of the kernel and its value is Generic_118833-36, Generic_127111-09, Generic_138888-07 , Generic_141414-07 or a value indicating a later version.
13.2.5 Collecting Sybase Version Information

This section describes how to collect the version information about the Sybase.
Procedure
Step 1 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 The system output is similar to the following information:
Adaptive Server Enterprise/15.0.2/EBF 15162 ESD#1 ONE-OFF/P/Sun_svr4/OS 5.8/ ase1502/2493/64-bit/FBO/Mon Oct 15 16:15:21 2007
In the system output, 15.0.2 is the current version number of the Sybase and 15162 is the version number of the patch that is installed.
When the version number of the Sybase is 15.0.2, the version number of the patch must be 15162 or 15679. When the version number of the Sybase is 15.0.3, the version number of the patch must be 16548.
13.2.6 Collecting the M2000 Version

This section describes how to obtain the version information about the M2000.
Procedure
Step 1 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: iManagerM2000V200R009ENGC00SPC805 Release Date: 06/09/09 ...
13.3 Collecting Fault Data Using the Log Information Collector

This section 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.
Procedure
Step 1 On the client, choose Start > Program > iManager M2000 Client > M2000 Log Information Collector .
The Log Information Collector dialog box is displayed, as shown in Figure 13-1. Figure 13-1 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.

l l
Trace files in Local Host: collects the trace files of the local client. Trace files in server: collects the trace files of the login server.
Issue 10 (2010-09-06)

l l l
Core files in server: collects the core files of the login server. LMT trace file in server: collects the trace files of the LMT. Standby Collection: collects the logs of the active node and the standby node at the same time. In the M2000 single-server system, do not select Standby Collection.
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 10 (2010-09-06)
14 FAQs (Sun)
14
About This Chapter
This chapter describes FAQs and solutions related to the M2000.
FAQs (Sun)
14.1 About Solaris This section describes some FAQs and solutions related to the Solaris. 14.2 About Sybase This section describes the FAQs and solutions related to the Sybase. 14.3 About TCP/IP Network This section describes some FAQs and solutions related to the TCP/IP network. 14.4 About Server Software This section describes some FAQs and solutions related to the M2000 server software.
Issue 10 (2010-09-06)
14-1
14 FAQs (Sun)
14.1 About Solaris

This section describes some FAQs and solutions related to the Solaris. 14.1.1 How Do I Log In to the M2000 Server as User root Through Telnet? This section describes how to log in as user root through Telnet. 14.1.2 How to Log In the M2000 Server as the root User Through FTP This section describes how to log in as user root through the FTP. 14.1.3 How to Check the Status of the Tape Drive This section describes how to check the status of the tape drive. 14.1.4 How Do I Select the Tape Drive? The types of servers that are not equipped with an internal tape drive, such as Netra 240 and T5220, 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, M4000, M5000 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, M4000, M5000 and E4900, are equipped with an external tape drive, which tape drive should the backup data be save on? 14.1.5 What are the files in the etc/rc2.d Folder of Solaris This section describes the definition of the files in the /etc/rc2.d folder of the Solaris. 14.1.6 How to View the Hardware Settings of the M2000 Server This section describes how to view the hardware settings of the M2000 server. 14.1.7 How to Check the Device Status of the M2000 Server This section describes the common commands used to check the device status of the M2000 server. 14.1.8 Why Unable to Enter the Domain Console of Fire E4900 This section describes the solutions to the failure to enter the domain console of the Sun Fire E4900. 14.1.9 How to Modify 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. 14.1.10 How to Query the Time Zone Name This section 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. 14.1.11 How Do I Stop the NTP Service on the M2000 Server This section describes how to stop the NTP service on the M2000 server. 14.1.12 How Do I Change the IP Address of the S3200 Disk Array (Command Mode) This section describes how to change the IP address of the S3200 disk array in command mode. The disk array is connected to the server directly through optical fibers. Changing IP addresses does not affect data read operations on the disk array. Therefore, you are advised to use the factory-delivered default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation. 14.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)?
14 FAQs (Sun)
This section describes how to change the IP address of the S2600 disk array in command mode. The disk array is connected to the server directly through optical fibers. Therefore, the change of the IP address of the disk array does not affect data read operations on the disk array. You are advised to retain the factory default IP address of the disk array. If the IP address of the disk array needs to be changed, change it according to the actual situation. 14.1.14 How Do I Change the IP Address of the 6140 Disk Array (Command Mode) This section describes how to modify the IP address of the 6140 disk array in command mode. To modify the IP address of the 6140 disk array, the server must be installed with the 6140 management host software. 14.1.15 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROM? This section describes why the CD-ROM drive cannot read the CD-ROM and provides the solution to this problem. 14.1.16 How to Handle the corrupt label - wrong magic number Message? This section describes how to handle the corrupt label - wrong magic number message. 14.1.17 What Should I Do When the Server Disk Space Is Insufficient? This section describes what to do when the server disk space is insufficient. 14.1.18 How to Configuring the Monitoring Function of the S2600 Disk Array This section describes how to configure the monitoring function of the S2600 disk array. 14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays This section describes how to configure the monitoring function for the S3000 series disk arrays, such as S3100 and S3200. 14.1.20 How Should I Uninstall the OceanStor Monitoring Software This section describes how to uninstall the OceanStor monitoring software. 14.1.21 How Should I Check the Running Status of the FTP Service on the M2000 Server? This section describes how to check the running status of the FTP service on the M2000 server. 14.1.22 How Should I Start the FTP Service on the M2000 Server? This section describes how to start the FTP service on the M2000 server. 14.1.23 How Should I Check the Running Status of the SFTP Service on the M2000 Server? This section describes how to check the running status of the SFTP on the M2000 server. 14.1.24 How Should I Start the SFTP Service on the M2000 Server? This section describes how to start the SFTP service on the M2000 server.
14.1.1 How Do I Log In to the M2000 Server as User root Through Telnet?
This section describes how to log in as user root through Telnet.
Question
How do I log in as user root through Telnet?
Answer
If you fail to log in to the M2000 server as user root through Telnet, you can use the following method to obtain the rights.
14 FAQs (Sun)
1. 2.
Log in to the server through the system controller (SC), remote system controller (RSC), or extended system controller facility (XSCF) as user root. Open /etc/default/login. # TERM=vt100; export TERM # vi /etc/default/login
3. 4. 5.
Find CONSOLE=/dev/console. Comment this line off by adding # at the beginning of the line. Save the changes and then exit the file. Check whether the Telnet service is started. # svcs -l telnet
l
If the system output contains disable, you can infer that the Telnet service is not started. Perform 6 again. If the system output contains enabled, you can infer that the Telnet service is started successfully.
6.
Start the Telnet service. # svcadm enable telnet
14.1.2 How to Log In the M2000 Server as the root User Through FTP
This section describes how to log in as user root through the FTP.
Question
How to log in as the root user through FTP?
Answer
If you fail to use the FTP service as user root, use the following method to obtain the permission. 1. 2. Log in as user root. Open /etc/ftpd/ftpusers. # TERM=vt100; export TERM # vi /etc/ftpd/ftpusers 3. 4. Find root. Comment this line off by adding # at the beginning of the line. Save, and then exit the file.
14.1.3 How to Check the Status of the Tape Drive

This section 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:
14 FAQs (Sun)
1. 2. 3. 4. 5. 6.
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. 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: This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example. # mt -f /dev/rmt/0n status The commands mentioned earlier can be briefly written as mt status. Table 14-1 lists the output. Table 14-1 Tape drive status No. 1 Output Certance Ultrium 3 tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file no= 0 block no= 0 2 /dev/rmt/0n: no tape loaded or drive offline /dev/rmt/0n: No such file or directory The tape is not inserted or not identified correctly, or the inserted tape is a cleaning tape. The previous message indicates that the operating system does not detect the tape drive. Tape Drive Status The tape drive works normally. A tape is loaded and rewound.
7.
Configure the tape drive. # drvconfig # tapes
8.
Load a tape and then check the status of the tape drive. # mt status
14.1.4 How Do I Select the Tape Drive?

The types of servers that are not equipped with an internal tape drive, such as Netra 240 and T5220, 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, M4000, M5000 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, M4000, M5000 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?
14 FAQs (Sun)
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, it indicates that only one tape drive is connected. If the command result also shows the logical device files that are preceded by 1, it indicates 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, it indicates that the tape drive 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 inserted or not identified correctly, or the inserted tape is a cleaning tape, the system displays the following information:
/dev/rmt/0n: no tape loaded or drive offline
14.1.5 What are the files in the etc/rc2.d Folder of Solaris

This section 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?
14 FAQs (Sun)
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.
The M2000 server installer creates three start files in the folder /etc/rc2.d/:
l l l l
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
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.
14.1.6 How to View the Hardware Settings of the M2000 Server

This section 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 14-2.
Table 14-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.
Issue 10 (2010-09-06)
14-7
14 FAQs (Sun)
14.1.7 How to Check the Device Status of the M2000 Server

This section 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 14-3 lists the commands often used for checking the device status. Table 14-3 Commands for checking the device status N Item o . 1 Hard ware Confi gurati on Description Hardware configuration
Check the disk status. Check the CPU status. Check the device tree. Check the power supply.
# iostat -E # psrinfo -v # prtconf -D # prtdiag -v # ifconfig -a # kstat -p ce:0:ce0: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. Check MAC settings for the IPMP technology.
# eeprom local-mac-address?
File syste m and disk
Check the file system.
# more /etc/vfstab
14-8
Issue 10 (2010-09-06)
14 FAQs (Sun)
N Item o . partit ionin g
Description
Hardware configuration
Check disk partitioning.
# format Specify disk (enter its number): number of the disk partition to be checked format> p partition> p
Check system error logs. 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. 4 Volu me and mirro r Check volume information. Check volume information.
# more /var/adm/messages | grep err 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 step is applicable for only the server with a disk array. # vxdisk list All hard disks are online. This step is applicable for only the server with a disk array.
Check volume information.
# vxprint -th -g ossdg The KSTATE column of pl, sd, and v is displayed ENABLED, and the STATE column is displayed ACTIVE. This step is applicable for only the server with a disk array. # cd /etc/vx/bin # vxlicrep
Check the license of Volume Manager. Check the mirror status.
# metastat
NOTE
l This command is applicable for only the servers that use SUN
DiskSuite (SDS) or Solaris Volume Manager (SVM) for encapsulating root disks.
l When the M2000 uses the T5220 server, run the raidctl command
to view the mirroring status.
Issue 10 (2010-09-06)
14-9
14 FAQs (Sun)
N Item o . 5 Tape drive
Description
Check the tape drive status. Rewind the tape. Forward one step. Forward two steps. Backward two steps. Check the tape content.
# mt stat # mt rewind # mt fsr # mt fsr 2 # mt bsr 2 This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # gtar tf /dev/rmt/0
Copy files to the tape.
This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # gtar cvf /dev/rmt/0n file name
Restore files from the tape to the disk. Check the Solaris system backup. Back up the Solaris to the tape.
This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # gtar xvPfM /dev/rmt/0 This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # ufsrestore -t /dev/rmt/0n This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # 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 Configure the CD-ROM.
This part takes the the logical device of the tape drive, that is, / dev/rmt/0, for example. # ufsdump rvf /dev/rmt/0n # drvconfig # tapes # mount -F hsfs -o ro /dev/rdsk/c0t6d0s0 /cdrom
14-10
Issue 10 (2010-09-06)
14 FAQs (Sun)
N Item o . 7 Flopp y disk Ether net port log
Description
Configure the floppy disk. Locate the fault and export the log.
# volcheck # mount -F pcfs /dev/diskette/floppy # /opt/SUNWexplo/bin/explorer Obtain the output log in the following path: /opt/SUNWexplo/output For example:
explorer.83bbbcad.osssvr-2005.08.15.02.05 explorer.83bbbcad.osssvr-2005.08.15.02.05.tar.gz
14.1.8 Why Unable to Enter the Domain Console of Fire E4900

This section 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 Hostname Idle Time Connected On Connected To --- ----------------------------- --------- -------------- -------------1 Localhost 00:01 Aug 26 17:13 Platform
Issue 10 (2010-09-06)
14-11
14 FAQs (Sun)
11 10.0.119.150 -

Aug 30 15:10 Platform
osssvr-1-sc0:SC>
14.1.9 How to Modify 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
5. 6.
On the PC, switch to the command mode and run the ftp command. Run the following command to connect to the server through FTP. ftp> open IP address of the server 1234 Type the user name and password of user root to log in to the server.
14.1.10 How to Query the Time Zone Name

This section 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 ...
14 FAQs (Sun)
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 14-4. Table 14-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
Issue 10 (2010-09-06)
Remarks Brazil/ DeNoronha Atlantic islands Amapa, E Para NE Brazil (MA, PI, CE, RN, PB) Pernambuco Tocantins Alagoas, Sergipe
14-13
Brazil
14 FAQs (Sun)
Coun try
Time Zone Name 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 Brazil/East Brazil/West Brazil/Acre Chile/ Continental Chile/ EasterIsland -
Remarks 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
Most locations Easter Island & Sala y Gomez -
Chile
China
PRC
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.
14.1.11 How Do I Stop the NTP Service on the M2000 Server

This section describes how to stop the NTP service on the M2000 server.
Prerequisite
Procedure
Step 1 Run the following command to check whether the NTP service is running: # svcs svc:/network/ntp:default
STATE online STIME FMRI 16:41:28 svc:/network/ntp:default
14-14
Issue 10 (2010-09-06)
14 FAQs (Sun)
In the system output, if STATE is online, you can infer that the NTP service is running. Step 2 If the NTP service is running, run the following command to stop it: # svcadm disable svc:/network/ntp:default
NOTE
You need to run this command only once. After you run this command, the NTP service does not automatically start whenever the system is restarted.
Step 3 Run the following command to check whether the NTP service is stopped: # svcs svc:/network/ntp:default
STATE disabled STIME FMRI 16:41:28 svc:/network/ntp:default
In the system output, if STATE is disabled, you can infer that the NTP service is stopped.
NOTE
Stopping the NTP service takes about one minute.
----End
14.1.12 How Do I Change the IP Address of the S3200 Disk Array (Command Mode)
This section describes how to change the IP address of the S3200 disk array in command mode. The disk array is connected to the server directly through optical fibers. Changing IP addresses does not affect data read operations on the disk array. Therefore, you are advised to use the factory-delivered default IP address of the disk array. If the IP address of a disk array needs to be changed, change the IP address according to the actual situation.
Prerequisites
l l
You have logged in to the server as user root. The server communicates properly with the S3200 disk array.
Background
l
Before changing IP addresses, you must familiarize yourself with the default IP address planning at delivery. Then, determine whether to reconfigure IP addresses based on the actual situation. The IP address mentioned here is only an example. Replace it with the actual IP address. If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a disk array. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must be on the same network segment. If you have changed the IP address of the disk array on a different segment, you need to change the IP address of the corresponding Ethernet port nxge3 to ensure that both changed IP addresses are on the same network segment.
l l
Procedure
This takes the following change as an example to describe how to change the IP address of the disk array.
14 FAQs (Sun)
l
Before the change: IP address of controller A: 192.168.8.39 IP address of controller B: 192.168.8.40
After the change: IP address of controller A: 10.10.10.39 IP address of controller B: 10.10.10.40
1.
Set the temporary subnet of the server to enable the server to access the controllers. # ifconfig bge0:1 plumb # ifconfig bge0:1 192.168.8.100 netmask 255.255.255.0 up
2.
Check whether the temporary subnet is configured properly. # ping 192.168.8.40 If the system displays the following information, then the temporary subnet is configured properly:
PING 192.168.8.40 (192.168.8.40) 56(84) bytes of data. 64 bytes from 192.168.8.40: icmp_seq=1 ttl=64 time=0.326 ms
3.
Change the IP address of controller B. # SMcli IP address of controller A -c "set controller [b] ethernetPort [1] ipAddress= New IP address of controller B gatewayIPAddress=New gateway of controller B subnetMask=New subnet mask of controller B;" In this case, IP address of controller A is 192.168.8.39, New IP address of controller B is 10.10.10.40, New gateway for controller B is 0.0.0.0, and New subnet mask of Controller B is 255.255.255.0. Run the following command: # SMcli 192.168.8.39 -c "set controller [b] ethernetPort [1] ipAddress= 10.10.10.40 gatewayIPAddress=0.0.0.0 subnetMask=255.255.255.0;" After the command is successfully executed, the IP address of controller B is 10.10.10.40.
4.
Set the temporary subnet of the server again to enable the server to access the controllers. # ifconfig bge0:1 plumb # ifconfig bge0:1 192.168.8.100 netmask 255.255.255.0 up
5.
Check whether the new IP address of controller B is set successfully. # ping New IP address of controller B In this case, run the following command: # ping 10.10.10.40 If the system displays the following information, then the temporary subnet is configured properly:
6.
Change the IP address of controller A. # SMcli IP address of controller B -c "set controller [a] ethernetPort [1] ipAddress= New IP address of controller A gatewayIPAddress=New gateway of controller A subnetMask=New subnet mask of controller A;" In this case, IP address of controller B is 10.10.10.40, New IP address of controller A is 10.10.10.39, New gateway for controller A is 0.0.0.0, and New subnet mask of Controller B is 255.255.255.0. Run the following command:
14-16
Issue 10 (2010-09-06)
14 FAQs (Sun)
# SMcli 10.10.10.40 -c "set controller [a] ethernetPort [1] ipAddress= 10.10.10.39 gatewayIPAddress=0.0.0.0 subnetMask=255.255.255.0;" After the command is successfully executed, the IP address of controller A is 10.10.10.39. 7. Check whether the new IP address of controller A is set successfully. # ping New IP address of controller A In this case, run the following command: # ping 10.10.10.39 If the system displays the following information, then the temporary subnet is configured properly:
8.
(Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file.

NOTE
(1) Log in to server as user root. (2) Perform the following operations on the server to modify the /etc/hosts file and to replace the existing IP address of the disk array with a new one. # vi /etc/hosts After the modification, press Esc and then run the :wq! command to save the modification and exit. (3) Perform the following operations on the server to modify the /etc/inet/ipnodes file. # vi /etc/inet/ipnodes
l
14.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)?
This section describes how to change the IP address of the S2600 disk array in command mode. The disk array is connected to the server directly through optical fibers. Therefore, the change of the IP address of the disk array does not affect data read operations on the disk array. You are advised to retain the factory default IP address of the disk array. If the IP address of the disk array needs to be changed, change it according to the actual situation.
Prerequisites
l l
You have logged in to the server as user root. The communication between the server and the two management Ethernet ports on the S2600 disk array is normal.
Issue 10 (2010-09-06)
14-17
14 FAQs (Sun)
Contexts
l
Each S2600 disk array has an active controller and a standby controller. Each controller has one management Ethernet port. Before changing the IP address of the disk array, you must familiarize yourself with the default IP address planning at delivery. Then, determine whether to reset the IP address according to the actual situation. The IP address mentioned here is only an example. Replace it with the actual IP address. If you change the IP address of the disk array on different network segments, continue to change the IP address of the maintenance Ethernet port on the corresponding server to ensure that the two changed IP addresses are on the same network segment.
l l
Procedure
1. Run the following command to log in to controller A of the S2600 disk array in ssh mode: # ssh admin@IP address of controller A
CAUTION
The initial user name and password of the administrator are admin and 123456, respectively. To ensure the system security, you need to change the password after the initial login. 2. Run the following command to change the IP address of controller B: OceanStor: admin> chgctrlip -c b -a new IP address of controller B -s subnet mask -g gateway For example, to change the IP address of the management Ethernet port on controller B to 10.71.15.21, run the following command: OceanStor: admin> chgctrlip -c b -a 10.71.15.21 -s 255.255.255.0 -g 10.71.15.1 When the system displays the following prompt, type y.
3.
Run the following command to check whether the changed IP address is correct: OceanStor: admin> showctrlip
IP Address A 192.168.8.39 00:18:82:e2:01:57 B 10.71.15.21 00:18:82:e2:00:fb Controller Subnet Mask 255.255.255.0 255.255.255.0 Gateway 192.168.8.1 10.71.15.1 MAC Address
4. 5.
Run the following command to exit from controller A: OceanStor: admin> exit Run the following command to log in to controller B of the S2600 disk array in ssh mode: # ssh admin@new IP address of controller B
14-18
Issue 10 (2010-09-06)
14 FAQs (Sun)
CAUTION
The initial user name and password of the administrator are admin and 123456, respectively. To ensure the system security, you need to change the password after the initial login. 6. Run the following command to change the IP address of controller A: OceanStor: admin> chgctrlip -c a -a IP address of controller A -s subnet mask -g gateway For example, to change the IP address of the management Ethernet port on controller A to 10.71.15.20, run the following command: OceanStor: admin> chgctrlip -c a -a 10.71.15.20 -s 255.255.255.0 -g 10.71.15.1 When the system displays the following prompt, type y.
7.
Run the following command to check whether the changed IP address is correct: OceanStor: admin> showctrlip
IP Address A 10.71.15.20 00:18:82:e2:01:57 B 10.71.15.21 00:18:82:e2:00:fb Controller Subnet Mask 255.255.255.0 255.255.255.0 Gateway 10.71.15.1 10.71.15.1 MAC Address
8.
Run the following command to exit from controller B: OceanStor: admin> exit
14.1.14 How Do I Change the IP Address of the 6140 Disk Array (Command Mode)
This section describes how to modify the IP address of the 6140 disk array in command mode. To modify the IP address of the 6140 disk array, the server must be installed with the 6140 management host software.
Prerequisite
You have ensure that the network connection between the server and the 6140 disk array is normal.
Procedure
1. Perform the following steps on the server to set the temporary subnet. (1) 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. (2) Check whether the server can communicate with controller A of the 6140 disk array.
14 FAQs (Sun)
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.8.39 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.8.39 If the system output contains 192.168.8.39 is alive after you run the above command, then the IP address of the server is on the same network segment as the IP address of controller A. Proceed with 3. Otherwise, you need to perform 1.3 through 1.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.11 netmask ffffff00 broadcast 192.168.8.255 ether 0:3:ba:bb:bc:ad bge0: 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 nxge0: 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 nxge3: 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 two or multiple IP addresses are bound to the network port, the name of the network port is displayed as bge0:X after you run the previous command. X is a number starting from 1. The displayed network port name cannot be used for setting the temporary subnet. When the X following bge0: is null, use bge0:1 as the name of the network port. In this example, the X following bge0: is null. Thus, you can use bge0:1 as the name of the network port to set the temporary subnet. (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.8.39 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.8.100 netmask 255.255.255.0 up
14 FAQs (Sun)
(5) Check the setting of the temporary subnet. In the following commands, the default IP address 192.168.8.39 of the 6140 disk array is taken as an example. Replace it with the actual IP address of controller A. # ping 192.168.8.39 If the system output contains 192.168.8.39 is alive, then the setting is correct. Otherwise, perform 2 to check whether the IP address of the controller A on the 6140 disk array is correct and to set the temporary subnet again. 2. If you fail to set a temporary subnet, perform the following steps to check whether the IP address of the controller A on the 6140 disk array is correct:
NOTE
Perform the same procedure to check the IP address of controller B on the 6140 disk array.
(1) Connect the six-pinned mini DIN connector of the basic cable to the serial port connector of the controller.
NOTE
Two serial port cables are attached to the pallet of each controller.
l l
One end is the six-pinned mini DIN connector, and the other end is the basic cable of the standard 9-pinned serial port connector. Extended cables of the standard 9-pinned serial port connector are attached to both ends.
(2) Connect the nine-pinned serial extended cable from the nine-pinned connector of the basic cable to the serial port connector of the PC. (3) Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on the PC. (4) In the Connection Description dialog box, enter the name of the new connection. (5) Choose the PC serial port that connects to the connector, for example, COM1. (6) Set the properties of the serial port. For details about how to set properties of a serial port, refer to Table 14-5. Then, click OK. Table 14-5 Setting the properties of the serial port Attribute Bit rate Data bit Parity check Stop bit Streaming control Attribute Value 38400 8 none 1 none
Thus, a physical connection between the PC and the 6140 disk array is set up. (7) Press Break. The serial port responds the request to synchronize the baud rate with the terminal.
Set baud rate: press <space> within 5 seconds
Issue 10 (2010-09-06)
14-21
14 FAQs (Sun)
NOTE
The serial ports on the disk array request that the Break character be accepted. Set the corresponding escape sequence for the terminal, and then send the essential Break character to the controller. For instance, press Ctrl and Break at the same time to generate the Break character on certain terminal.
(8) Press the spacebar within five seconds. The serial port defines the baud rate for setup.
Baud rate set to 38400
(9) Press Break. The serial port responds with the following messages:
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
(10) Press S. The serial port prompts you to enter the password.
Enter Password to access Service Interface (60 sec timeout): - >
(11) Enter the password kra16wen, and then press Enter. (12) If the following message is displayed, enter 1.
(13) If the following message is displayed, enter 1.

The configuration of the IP address for the selected Ethernet port is displayed. (14) If the following message is displayed, enter Q to exit.
(15) Perform 1.4 and 1.5 by using the IP address of controller A to reset a temporary subnet. 3. 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. 4. 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, then the 6140 disk is registered. Otherwise, the 6140 disk array is not registered.
14 FAQs (Sun)
(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.8.39 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.8.39 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. 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 netmask 255.255.0.0 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, then the setting is correct. Otherwise, perform 4.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 4.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.
14 FAQs (Sun)
# /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 5. (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file.
NOTE
(1) Log in to server as user root. (2) Perform the following operations on the server to modify the /etc/hosts file and to replace the existing IP address of the disk array with a new one. # vi /etc/hosts After the modification, press Esc and then run the :wq! command to save the modification and exit. (3) Perform the following operations on the server to modify the /etc/inet/ipnodes file. # vi /etc/inet/ipnodes
l
14.1.15 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROM?
This section describes why the CD-ROM drive cannot read the CD-ROM and provides the solution to this problem.
Question
After the CD-ROM is inserted into the CD-ROM drive, it fails to be read. After the command df -k is executed, no contents exist in the /cdrom directory. In the system output, the value of the capacity column corresponding to the /cdrom directory is not 100%.
Cause
The system cannot identify the partitioning of the CD-ROM drive.
Solution
To rectify the fault, perform the following steps: 1. 2. Log in to the server as user root. Run the following commands to identify the partitioning of the CD-ROM drive again: # /etc/init.d/volmgt stop # /etc/init.d/volmgt start 3. Run the following command to check whether the CD-ROM drive can read the CD-ROM. # df -k
14 FAQs (Sun)
In the system output, if the value of the capacity column corresponding to the /cdrom directory is 100%, you can infer that the CD-ROM drive can read the CD-ROM now. Otherwise, contact Huawei technical support engineers for assistance.
14.1.16 How to Handle the corrupt label - wrong magic number Message?
This section describes how to handle the corrupt label - wrong magic number message.
Question
When the format command is executed, the system output contains the corrupt label - wrong magic number message. This problem occurs in newly mounted disk arrays. The cause is lack of disk labels.
Solution
Label the disks. 1. 2. 3. Log in to the server as user root. Run the following command to refresh the system hardware. # devfsadm -C Run the following command to check the disk information. # format The system output contains the corrupt label - wrong magic number message. 4. Perform the following operations to label logic disk partitions: (1) After you run the format command, the system displays the following information. Enter the sequence number corresponding to the logical partition on the disk array. In this example, the sequence number is 2.
Specify disk (enter its number):2
(2) Label the logical disk partitions.

l
If the logical partitions are not labeled, the system displays the following information. Enter y.
Disk not labeled. Label it now?
If the logical partitions are already labeled, the system displays the format> prompt. After you run the label command, enter y at the following prompt:
Ready to label disk, continue?
(3) After running the following command, repeat 4.1 and 4.2 to label the other logical partitions. format> disk 5. Exit format. format> q
14.1.17 What Should I Do When the Server Disk Space Is Insufficient?

This section describes what to do when the server disk space is insufficient.
14 FAQs (Sun)
Question
You can use any of the following methods to check the server disk space:
l
View the message output area at the bottom of the M2000 client. If the disk partition usage reaches the threshold, you need to clear the disk space immediately. View the disk partition usage in the Hard Disk Monitoring window on the M2000 client. Run the df -k command to check the disk partition usage.
l l
How do I do when the server disk space is insufficient?
Solution
l
If the system notifies you of the high disk space usage of the partition where the /data directory is located, do not delete or transfer any files. In this case, contact Huawei technical support engineers for assistance. If the system notifies you of the high disk space usage of the /export/home partition, see 9.2.4 Clearing the Disk Space of the M2000 Server to troubleshoot. If the system notifies you of the high disk space usage of the root partition / or /opt, perform as follows: 1. 2. 3. Log in to the server as user root. Run the following command to collect related information: # du -akd / | sort -nr > /tmp/du.out Transfer the information from the server to the client. (1) Switch to the command mode on the PC and run the ftp command. ftp IP address of the server (2) Enter the user name and password of user root. (3) Run the following commands to set the file paths on both the PC and the server:
CAUTION
If the filepath contains a space, you need to use the DBC quotation marks to enclose the filepath. Otherwise, the system fails to identify this filepath, and accordingly, the file cannot be uploaded or downloaded. The filepath on the Windows desktop contains space characters. Therefore, do not save files on the desktop. ftp> lcd save path of the collected information on the PC ftp> cd /tmp (4) Set the transfer mode to ASCII. ftp> asc (5) Transfer the collection results. ftp> get du.out After the uploading is complete, the system switches to the ftp> state. (6) Quit the ftp> state.
14 FAQs (Sun)
ftp> bye 4. Send the collection results to Huawei technical support engineers.
14.1.18 How to Configuring the Monitoring Function of the S2600 Disk Array
This section describes how to configure the monitoring function of the S2600 disk array.
Question
How should I configure the monitoring function of the S2600 disk array?
Answer
Perform the following operations to configure the monitoring function of the S2600 disk array: 1. Log in to controller A of the S2600 disk array in SSH mode. # ssh admin@IP address of controller A
CAUTION
The initial name and password of the administrator user is admin and 123456, respectively. For security considerations, you are advised to change the password after you log in to the system for the first time. 2. Run the following command to check whether the disk array is set with a Trap IP address: OceanStor: admin> showtrapip
Index S26000 l IP Address 192.168.8.241 Port ID 162 Version 2
If there is no system output, you can infer that no Trap IP address is set. In this case, perform 3 to set a Trap IP address. If the system output is similar to the previous information, check whether the configurations in the system output are correct. If they are incorrect, perform 4 to modify the configurations.
3.
Run the following command to set a Trap IP address of the disk array: For example, set the Trap IP address of the disk array to 192.168.8.241. OceanStor:admin> addtrapip -a 192.168.8.241 -v 2 -p 162
NOTE
In the single-server system, you need to set only one Trap IP address. Repeat 3 if another Trap IP addresses need to set.
4.
Run the following command to change the Trap IP address of the disk array: For example, change the Trap IP address of the disk array to 10.10.10.10. OceanStor:admin> chgtrapip -i S26000 -a 10.10.10.10 Run the following command to check whether the Trap IP address is successfully changed: OceanStor:admin> showtrapip
Issue 10 (2010-09-06)
14-27
14 FAQs (Sun)
Index S26000 IP Address 10.10.10.10 Port ID 162 Version 2
5.
Run the following command to change the system time of the disk array: For example, change the system time to 2008-12-17/11:05:00. OceanStor: admin> chgsystime -t 2008-12-17/11:05:00
NOTE
l l
The system time of the disk array must be the same as that of the connected M2000 server. The command chgsystime is used to change the system time. The time ranges from 1970-01-01 00:00:00 to 2069-12-31 23:59:00.
6. 7. 8.
Run the following command to log out of controller A: OceanStor: admin> exit Log in to the M2000 server as user root. Add the IP address of the disk array controller to the SANtricty_config.xml file. # cd /opt/OMC/resourcemonitor # vi SANtricty_config.xml
<config> <src name iorstring <src name iorstring </config> = = = = "trapsender" ip = "IP address of controller A" port = "23001" ""/> "trapsender" ip = "IP address of controller B" port = "23001" ""/>
If the IP address of the controller is incorrect in the file, replace the existing IP address with a new IP address. Then, press Esc and run the :wq command to save the modification and quit. 9. Run the following command to view the user.xml file: # vi user.xml
<snmp name = "trap"> <instance name = "san" run = "true" filepath = "SANtricty_config.xml"/> <instance name = "vcs" run = "true" filepath = "vcs_config.xml"/> <loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/> </snmp> l
If the status of san in the file is true, do not modify the file. Press Esc and run the :q command to quit. Otherwise, change the status of san to true. Then, press Esc and run the :wq command to save the modification and quit.
10. Run the following commands to restart the ResourceMonitor process: # ps -ef | grep "ResourceMonitor"
root 10256 884 0 10:57:58 ? 0:55 /opt/OMC/bin/ResourceMonitor cmd start -ipaddr 10.71.15.31 >/dev/null 2>&1 root 20762 26443 0 16:54:48 pts/4 0:00 grep ResourceMonitor
# kill -9 10256
NOTE
In the previous command, replace the ResourceMonitor process ID 10256 with the actual value.
11. Run the following commands to restart the UdpDispatchService service:

NOTE
You need to restart the UdpDispatchService service on only active server.
# . /opt/OMC/svc_profile.sh
14 FAQs (Sun)
# svc_adm -cmd restartsvc UdpDispatchService
14.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays
This section describes how to configure the monitoring function for the S3000 series disk arrays, such as S3100 and S3200.
Question
How should I configure the monitoring function for the S3000 series disk arrays?
Answer
1. 2. Log in to the server that is to be installed with the OceanStor as user root by using the WinaXe software. Install the OceanStor.
NOTE
l l
If the M2000 is configured with the management console, the OceanStor is installed on the management console. If the M2000 is not configured with the management console and port 162 on the M2000 server is not occupied, the OceanStor is installed on the M2000 server.
(1) Log in to http://support.huawei.com to download the OceanStor to the PC.

NOTE
l l
The version of the OceanStor is OceanStor S3100 S3200 S6800 Storage Manager for Solaris V200R002C01B024. The path for downloading the OceanStor is Software Download > Version Software > Outsourcing Product Line > IT Integrated Product > OceanStor.
(2) Decompress the SMIA-SOL-09.19.04.07.bin file in the OceanStor installation package. (3) Upload the decompressed file to the /opt directory in binary mode. ftp server IP address ftp> lcd path of the file on the PC ftp> cd /opt ftp> bin ftp> put /opt/SMIA-SOL-09.19.04.07.bin ftp> bye (4) Create a directory for saving the OceanStor installation package. # cd /opt # mkdir SMIADIR (5) Move the OceanStor installation package to the /opt/SMIADIR directory. # mv /opt/SMIA-SOL-09.19.04.07.bin /opt/SMIADIR/SMIASOL-09.19.04.07.bin.zip (6) Decompress the OceanStor installation package. # cd /opt/SMIADIR
14 FAQs (Sun)
# unzip SMIA-SOL-09.19.04.07.bin.zip (7) Change the folder name. # mv \$BASE_DIR\$/ BASE_DIR (8) Install the SMruntime, SMclient, and SMutil software in sequence. # cd BASE_DIR/Resources/Platforms/SOL # pkgadd -d /opt/SMIADIR/BASE_DIR/Resources/Platforms/SOL/ SMruntime-SOL.pkg SMruntime # pkgadd -d /opt/SMIADIR/BASE_DIR/Resources/Platforms/SOL/SMclientSOL.pkg SMclient When the system displays the following prompt, type y:
Do you want to continue with the installation of <SMclient> [y,n?] y
# pkgadd -d /opt/SMIADIR/BASE_DIR/Resources/Platforms/SOL/SMutilSOL.pkg SMutil 3. Add the disk array to be monitored to the OceanStor. (1) Run the following commands to start the OceanStor management program: # cd /opt/SM9/client # ./SMclient (2) In the Select Addition Method dialog box, select Manual. (3) Click OK. (4) In the Add Storage Array dialog box, select Out-of-band management. Type the IP addresses of the two controllers of the disk array in First Controller and Second Controller, respectively. (5) Click Add to add the disk array. (6) After the disk array is added, click Out-of-band Storage Arrays. (7) Choose Edit > Configure Alerts. (8) Click the SNMP tab, as shown in Figure 14-1.
14-30
Issue 10 (2010-09-06)
14 FAQs (Sun)
Figure 14-1 SNMP tab page
(9) Type the IP address of the M2000 server in Trap destination. (10) Click Add. (11) Wait until the typed IP address is added to the Configured SNMP addresses area in Figure 14-1, and then click OK. (12) If the Configure Mail Server dialog box is displayed, click Yes. 4. Modify the M2000 configuration file to set the monitoring parameters of the OceanStor. (1) Log in to the M2000 server as user root. (2) Run the following command to run the environment variables of the M2000: # . /opt/OMC/svc_profile.sh (3) Run the following commands to run the monitoring script: # cd /opt/OMC/bin # ./deployHDMonitor.sh
14 FAQs (Sun)
When the system displays the following prompt, type 2, and then press Enter.
============================================================= Please Select the Monitor Type: 1)--Sun Management Center(SMC) Monitor 2)--Sun ST6140/OceanStor S3000 Monitor Q|q)--Exit ============================================================= Please make a choice : 2
(4) When the system displays the following prompt, type the IP address of the server installed with the OceanStor.
Please input the IP of SANtricty server [default:127.0.0.1]: 192.168.1.1
(5) When the system displays the following prompt, type true.
Please set the flag to start SANtricty service [default:false]: true
(6) When the system displays the following prompt, type false.
Please set the flag to start VCS service [default:false]: false
When the system displays Finish to deploy Sun ST6140/OceanStor S3000 Monitor, it indicates that the monitoring parameters of the disk array are set.
NOTE
The configuration takes effect after about 15 minutes.
5.
Check whether the monitoring of the disk array is enabled. (1) Log in to the server installed with the OceanStor as user root by using the WinaXe software. (2) Run the following commands to start the OceanStor management program: # cd /opt/SM9/client # ./SMclient (3) In the displayed dialog box, click Out-of-band Storage Arrays. (4) Choose Edit > Configure Alerts. (5) Click the SNMP tab, as shown in Figure 14-1. (6) In the Configured SNMP addresses area, select the configured IP address, and then click Validate. (7) Switch to the fault alarm page of the M2000 client to view the alarm list. (8) Log in to the M2000 client. (9) Choose Monitor > Browse Alarm List to view the alarm list. If the information about the alarm whose ID is 1042 or the location information whose Description is Alert Test Message is available in the alarm list, it indicates that the monitoring of the disk array is enabled.
NOTE
Alternatively, you can check whether the monitoring of the disk array is enabled in the following way: 1. Remove the power supply cable from any disk array to be monitored. 2. Switch to the fault alarm page of the M2000 client to view the alarm list. If the information about the alarm whose ID is 1042 or the location information whose Description is Controller tray component failed is available in the alarm list, it indicates that the monitoring of the disk array is enabled.
14.1.20 How Should I Uninstall the OceanStor Monitoring Software

This section describes how to uninstall the OceanStor monitoring software.
14 FAQs (Sun)
Question
How should I uninstall the OceanStor monitoring software?
Answer
1. 2. Log in to the server installed with the OceanStor as user root. Run the following command to uninstall the OceanStor: # pkgrm SMutil When the system displays the following prompt, type y.
Do you want to remove this package? [y,n,?,q] y
# pkgrm SMclient When the system displays the following prompt, type y.
Do you want to remove this package? [y,n,?,q] y Do you want to continue with the removal of this package [y,n,?,q] y
# pkgrm SMruntime When the system displays the following prompt, type y.
Do you want to remove this package? [y,n,?,q] y
14.1.21 How Should I Check the Running Status of the FTP Service on the M2000 Server?
This section describes how to check the running status of the FTP service on the M2000 server.
Prerequisites
Context
l l
You can use the traditional plain text mode or FTPS as the FTP transfer policy. As an FTP application based on the SSL protocol, the FTPS protocol encrypts data during FTP login connection and data transmission. The FTP service on the M2000 server adopts the self-adaptive mode. It can determine whether to use the FTPS mode or the FTP mode based on the encryption mode adopted by the FTP client. FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to 500 must be open.
Procedure
1. Run the following command to check the running status of the FTP service: # ps -ef | grep ftpd | grep -v grep If the following information is displayed, it indicates that the FTP service on the M2000 server is started. If there is no system output, start the FTP service by referring to 14.1.22 How Should I Start the FTP Service on the M2000 Server?.
root 26510 22906 0 19:53:39 pts/1 0:00 /usr/sbin/ftpd
In the system output, the value in the second line refers to the process ID of the FTP service on the M2000 server.
14 FAQs (Sun)
14.1.22 How Should I Start the FTP Service on the M2000 Server?
This section describes how to start the FTP service on the M2000 server.
Prerequisites
Context
l l
You can use the traditional plain text mode or FTPS as the FTP transfer policy. As an FTP application based on the SSL protocol, the FTPS protocol encrypts data during FTP login connection and data transmission. The FTP service on the M2000 server adopts the self-adaptive mode. It can determine whether to use the FTPS mode or the FTP mode based on the encryption mode adopted by the FTP client. FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to 500 must be open.
Procedure
1. Run the following command to start the FTP service: # /usr/sbin/ftpd & The system displays the process ID of the FTP service. 2. Run the following command to check the running status of the FTP service: # ps -ef | grep ftpd | grep -v grep The system displays the following information:
root 26510 22906 0 19:53:39 pts/1 0:00 /usr/sbin/ftpd
In the system output, the value in the second line is the process ID of the FTP service on the M2000 server. This value must be the same as the process ID displayed in step 1.
14.1.23 How Should I Check the Running Status of the SFTP Service on the M2000 Server?
This section describes how to check the running status of the SFTP on the M2000 server.
Prerequisites
Context
l
SSH FTP (SFTP), is an FTP transfer mode based on the SSH protocol. SFTP uses a mature public key mechanism or private key mechanism to encrypt the data in the network. This ensures that the data communication between two ends can be performed in an encrypted channel. SFTP is supported between the M2000 server and the M2000 client, and also between the M2000 and an NMS.
14-34
14 FAQs (Sun)
Procedure
1. Run the following command to check the running status of the SFTP service: # svcs -a | grep ssh The system displays the following information:
online 18:46:13 svc:/network/ssh:default
If online is displayed in the system output, it indicates that the SFTP service on the M2000 server is started. If disabled is displayed in the system output, it indicates that the SFTP service on the M2000 server is not started. For details about how to start the SFTP service, see 14.1.24 How Should I Start the SFTP Service on the M2000 Server?.
14.1.24 How Should I Start the SFTP Service on the M2000 Server?
This section describes how to start the SFTP service on the M2000 server.
Prerequisites
Context
l
SFTP is an FTP transfer mode based on the SSH protocol. SFTP uses a mature public key mechanism or private key mechanism to encrypt the data in the network. This ensures that the data communication between two ends can be performed in an encrypted channel. SFTP is supported between the M2000 server and the M2000 client, and also between the M2000 and an NMS.
Procedure
1. 2. Run the following command to start the SFTP service on the M2000 server: # svcadm enable svc:/network/ssh:default Run the following command to check the running status of the SFTP service: # svcs -a | grep ssh online is displayed in the system output. That is, the SFTP service on the M2000 server is started.
14.2 About Sybase

This section describes the FAQs and solutions related to the Sybase. 14.2.1 How Do I Check Whether the Sybase Is Started? This section describes how to check whether the Sybase is started. 14.2.2 How to Start the Sybase This section describes how to start the Sybase service. 14.2.3 How Do I Stop the Sybase? This section describes how to stop the Sybase. 14.2.4 How to View the Name of the Sybase Server This section describes how to view the name of the Sybase server when the Sybase database is running.
14 FAQs (Sun)
14.2.5 How to Handle Database Alarms This section describes why database alarms are generated and how to handle these database alarms. 14.2.6 How to View Database Deadlock Information This section describes how to check the deadlock information about the Sybase database. 14.2.7 Why the Sybase Is Not Started After the Server Restarted This section describes why the Sybase is not started after the M2000 is restarted. 14.2.8 Why the Sybase Is Not Started After Run svc_profile.sh This section describes why the Sybase is not started after the execution of the script svc_profile.sh. 14.2.9 Why the Sybase Backup Database Abort This section describes how to solve the Sybase backup abort. 14.2.10 Why the Mouse Pointer Changes into an Hourglass upon History Alarm Query This section describes how to handle the problem that the mouse pointer changes into an hourglass upon history alarm query. 14.2.11 What Should I Do When the Database Cannot Be Started Properly? This section describes what to do when the database cannot be started properly. 14.2.12 What Should I Do When the Client Is Disconnected Due to Damaged System Tables in the Database? This section describes what to do when the client is disconnected due to damaged system tables in the database. 14.2.13 What Should I Do When the Number of Database Connections Is Insufficient? This section describes what to do when the number of database connections is insufficient. 14.2.14 How to Handle the '/export/home/sybdev/master.dat' already in use Message? This section describes how to handle the '/export/home/sybdev/master.dat' already in use message. 14.2.15 What Should I Do to Handle Database Startup Failure Due to Incorrect User Type? This section describes how to handle database startup failure due to incorrect user type.
14.2.1 How Do I Check Whether the Sybase Is Started?

This section describes how to check whether the Sybase is started.
Question
How do I check the startup status of the Sybase?
Answer
Perform the following steps to check the status of Sybase: 1. Switch to user dbuser.
l l
Log in to the server as dbuser and switch to dbuser state. Run the su - dbuser command as user root. You can switch to user dbuser.
2.
Run the following commands: -bash-3.00$ cd /opt/sybase/ASE-15_0/install
14-36
Issue 10 (2010-09-06)
14 FAQs (Sun)
-bash-3.00$ ./showserver
UID PID PPID C STIME TTY TIME CMD dbuser 341 339 0 Oct 21 ? 0:01 /opt/sybase/ASE-15_0/bin/ backupserver -SSYB_back -e/opt/sybase/ASE-15_0/install dbuser 3104 3103 1 Oct 25 ? 312:20 /opt/sybase/ASE-15_0/bin/ dataserver -sSYB -d/data/master_dev.dat -e/opt/sybase/
If the output includes dataserver and backupserver, it indicates that the data service process and the backup service process of the database are already started.
NOTE
Switch to user dbuser from user root. After you check the Sybase status, run the exit to roll back to user root.
14.2.2 How to Start the Sybase

This section describes how to start the Sybase service.
Question
How to start the Sybase service?
Answer
To start the Sybase service, perform the following steps: 1. Switch to user dbuser.
l l
2. 3.
Check whether the Sybase is started by referring to 14.2.1 How Do I Check Whether the Sybase Is Started?. Start the Sybase. (1) Run the following commands: -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.
(2) When the following output is displayed, press Enter.

00:00000:00001:2008/12/11 10:53:50.71 server Recovery complete. 00:00000:00001:2008/12/11 10:53:50.71 server ASE's default unicode sort order is 'binary'. 00:00000:00001:2008/12/11 10:53:50.71 server ASE's default sort order is: 00:00000:00001:2008/12/11 10:53:50.71 server 'bin_iso_1' (ID = 50) 00:00000:00001:2008/12/11 10:53:50.71 server on top of default character set: 00:00000:00001:2008/12/11 10:53:50.71 server 'iso_1' (ID = 1). 00:00000:00001:2008/12/11 10:53:50.71 server Master device size: 400 megabytes, or 204800 virtual pages. (A virtual page is 2048 bytes.)
(3) Run the following commands: -bash-3.00$ nohup ./startserver -f ./RUN_SYB_back

14 FAQs (Sun)
NOTE
l l
In the previous command, SYB is the name of the database server. In actual situations, replace this name with the real name. Switch to user dbuser from user root. After the Sybase is started, run the exit to roll back to user root.
14.2.3 How Do I Stop the Sybase?

This section describes how to stop the Sybase.
Question
How do I stop the Sybase service?
Answer
To stop the Sybase, perform the following steps: 1. Switch to user dbuser.
l l
2.
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 database is stopped. If no command result exists, it indicates that the Sybase database is stopped. If any command result exists, run the kill -9 PID of Sybase command to forcibly stop the Sybase process. Switch to user dbuser from user root. After you stop the Sybase, run the exit to roll back to user root. If the M2000 server is installed, the Sybase starts automatically upon a restart of the operating system.
l l
14.2.4 How to View the Name of the Sybase Server

This section 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 RUN_ | grep -v grep In the command result, the value after the RUN_ 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:
14-38
Issue 10 (2010-09-06)
14 FAQs (Sun)
14.2.5 How to Handle Database Alarms

This section 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

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.
Solution

Issue 10 (2010-09-06)
14 FAQs (Sun)
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.
14.2.6 How to View Database Deadlock Information

This section 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
The class column will display the cursor name for locks associated with a cursor for the current user and the cursor id for other users. fid spid loid locktype table_id page 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.
14-40
Issue 10 (2010-09-06)

NOTE
14 FAQs (Sun)
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.
14.2.7 Why the Sybase Is Not Started After the Server Restarted
This section describes why the Sybase is not started after the M2000 is restarted.
Question
Why does the Sybase not start after the M2000 server restarts? This takes SYB, which is the name of the database server, as an example. Open the Sybase system log SYB.log. Find that the record similar with the following contents is available:
kernel Configuration Error: Configuration file, '/opt/sybase/ASE-15_0/SYB.cfg', does not exist. kernel Warning: A configuration file was not specified and the default file '/opt/sybase/ASE-15_0/SYB.cfg' does not exist. SQL Server creates the default file with the default configuration. kernel Configuration file '/opt/sybase/ASE-15_0/SYB.cfg' has been written and the previous version has been renamed to '/opt/sybase/ASE-15_0/SYB.076'
NOTE
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.
14 FAQs (Sun)
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.*. The specific file name is recorded in the system log of the Sybase, that is, SYB.log. In this example,SYB.cfg is renamed as 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/ASE-15_0 # cp SYB.076 SYB.cfg # chown -R dbuser:staff /opt/sybase/ASE-15_0 # su - dbuser 2. Start the Sybase. For details, see 14.2.2 How to Start the Sybase. To avoid this problem, start the Sybase as user dbuser.
14.2.8 Why the Sybase Is Not Started After Run svc_profile.sh

This section 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
14 FAQs (Sun)
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/.
14.2.9 Why the Sybase Backup Database Abort

This section 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 In the previous command, SYB is the name of the database server. In actual situations, replace this name with the real name.
NOTE
14.2.10 Why the Mouse Pointer Changes into an Hourglass upon History Alarm Query
This section describes how to handle the problem that the mouse pointer changes into an hourglass upon history alarm query.
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.
14 FAQs (Sun)
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">SYB</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.
14.2.11 What Should I Do When the Database Cannot Be Started Properly?

This section describes what to do when the database cannot be started properly.
14 FAQs (Sun)
Question
How do I do when the database cannot be started properly?
Cause
l
The information about server shared memory information is not set in /etc/system. The value of the set shmsys:shminfo_shmmax field in /etc/system is the server shared memory information. The value of the shared memory is x1024x1024/2, and the unit is MB. If the shared memory is not correctly set, installing the Sybase fails. Thus, the system displays a message, indicating that memory is incorrect, during the startup of the Sybase.
In the file system database, the owner of the files under the /data directory is changed. The correct owner of the database files under the /data directory is dbuser, and the user group is staff.
The owner of the /opt/sybase/ASE-15_0/SYB.cfg configuration file of the Sybase database is incorrect. The correct owner of the /opt/sybase/ASE-15_0/SYB.cfg configuration file is dbuser, and the user group is staff. # ls -l /opt/sybase/ASE-15_0/SYB.cfg
-rwxrwxrwx SYB.cfg 1 dbuser staff 9926 Sep 2 10:50 /opt/sybase/ASE-15_0/
After the Sybase database is stopped, the /opt/sybase/SYB.krg file is not successfully deleted. After you change the IP address of the server, the IP address information recorded in the / opt/sybase/interfaces file is not changed.
NOTE
l l
SYB in the /opt/sybase/ASE-15_0/SYB.cfg and /opt/sybase/SYB.krg files is the name of the Sybase database server. Replace SYB in actual situations. On the server, run the following command. Based on the system output, obtain the name of the database server. -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ls | grep RUN_SYB If the system displays the following information, you can infer that the name of the database server is SYB1:
RUN_SYB1 RUN_SYB1_back
Solution
contact Huawei technical support engineers for assistance.
14.2.12 What Should I Do When the Client Is Disconnected Due to Damaged System Tables in the Database?
This section describes what to do when the client is disconnected due to damaged system tables in the database.
Issue 10 (2010-09-06)
14-45
14 FAQs (Sun)
Question
The client is disconnected from the server. When viewing the /opt/sybase/ASE-15_0/install/ SYB.log log file, the following message is displayed:
02:00000:00344:2008/05/27 14:14:38.84 kernel infected with signal 11 (SIGSEGV) 02:00000:00344:2008/05/27 14:14:38.84 kernel Address 0x0000000080998990 Current process (0xfee0214)
(tmp_alldrop+0x84), siginfo (code, address) = (1, 0x000120003fdaa478) 02:00000:00344:2008/05/27 14:14:38.84 kernel ************************************ 02:00000:00344:2008/05/27 14:14:38.84 kernel
NOTE
pc: 0x0000000080f4e7b8
l l
SYB in the /opt/sybase/ASE-15_0/install/SYB.log files is the name of the Sybase database server. Replace SYB in actual situations. On the server, run the following command. Based on the system output, obtain the name of the database server. -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ls | grep RUN_SYB If the system displays the following information, you can infer that the name of the database server is SYB1:
Solution
The infected with signal 11 (SIGSEGV) message is in the database log file, which indicates that the system table in the master database is damaged. In this case, you need to recover the database. 1. 2. Log in to the server as user root. Check whether the M2000 services are running. If the M2000 services are running, stop them. Check the operation status of the M2000 services. For details, see 7.2.2 Viewing the States of M2000 Services. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. 3. Check whether the Sybase service is running. If the Sybase service is running, stop it. # su - dbuser For details about how to view the Sybase service, see 14.2.1 How Do I Check Whether the Sybase Is Started?. For details about how to stop the Sybase services, see 14.2.3 How Do I Stop the Sybase?. 4. Run the following command to start the data service process of the database: -bash-3.00$ cd /opt/sybase/ASE-15_0/install -bash-3.00$ ./startserver -f ./RUN_SYB -m

NOTE
14 FAQs (Sun)
The startup of the database services takes about 30 seconds. Wait until the database service is started. In the previous command, SYB refers to the name of the database server. Replace SYB with the actual server name.
If the following output is displayed, press Enter.

00:00000:00001:2008/12/11 10:53:50.71 server Recovery complete. 00:00000:00001:2008/12/11 10:53:50.71 server ASE's default unicode sort order is 'binary'. 00:00000:00001:2008/12/11 10:53:50.71 server ASE's default sort order is: 00:00000:00001:2008/12/11 10:53:50.71 server 'bin_iso_1' (ID = 50) 00:00000:00001:2008/12/11 10:53:50.71 server on top of default character set: 00:00000:00001:2008/12/11 10:53:50.71 server 'iso_1' (ID = 1). 00:00000:00001:2008/12/11 10:53:50.71 server Master device size: 400 megabytes, or 204800 virtual pages. (A virtual page is 2048 bytes.)
5.
Run the installmaster script to recover the master database. -bash-3.00$ isql -Sname of the database server -Usa -Ppassword of user sa -i $SYBASE/ASE-15_0/scripts/installmaster When the system displays the following message, you can infer that the database is successfully recovered. Loading of master database is complete.
NOTE
Recovering the database takes about 14 minutes. Wait until the database is recovered.
6.
Run the following command to stop the data service process of the database: -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> shutdown 2> go
7. 8.
Start the Sybase database. Restart the Sybase. For details, see 14.2.2 How to Start the Sybase. Start the M2000 services. For details about how to start the M2000 services, see 7.2.3 Starting the M2000 System Services.
14.2.13 What Should I Do When the Number of Database Connections Is Insufficient?

This section describes what to do when the number of database connections is insufficient.
Question
The client is disconnected from the server, and the isql is disconnected from the database. When viewing the /opt/sybase/ASE-15_0/install/SYB.log log file, the following message is displayed:
01:00000:00012:2008/05/28 01:34:38.12 server 01:00000:00012:2008/05/28 01:34:38.12 server Error: 1601, Severity: 17,State: 3 There are not enough 'user
connections' available to start a new process. Retry when there are fewer active users, or ask your System Administrator to reconfigure ASE with more
Issue 10 (2010-09-06)
14-47
14 FAQs (Sun)
user connections.
NOTE
l l
Solution
The database log file contains the Error: 1601 message, which indicates that the number of database connections is insufficient. You need to modify the number of database connections. 1. 2. Log in to the server as user root. If the M2000 services are running, stop them. For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services. 3. 4. Switch to user dbuser. # su - dbuser Run the following commands to change the maximum number of connections to 800. -bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa 1> sp_configure "number of user connections", 800 2> go
l
When the system displays the following message, you can infer that the modification succeeds. Run the exit command to exit isql.
Parameter Name Default Memory Used Config Value Run Value Unit Type ------------------------------ ----------- ----------- ----------------------- -------------------- ---------number of user connections 25 350538 800 800 number dynamic (1 row affected) Resulting configuration value and memory use have not changed from previous values: new configuration value 800, previous value 800. (return status = 0)
If the system displays the following message, you can infer that the system has insufficient memory. In this case, proceed with 5.
Msg 5861, Level 16, State 1: Server 'SYB', Procedure 'sp_configure', Line 860: The current 'max memory' value '845536', is not sufficient to change the parameter 'number of user connections' to '32766'. 'max memory' should be greater than 'total logical memory' '845328' required for the configuration. (return status = 1)
5.
Run the following command to check the database memory: 1> sp_configure "max memory"
14-48
Issue 10 (2010-09-06)
14 FAQs (Sun)
2> go Then, contact Huawei technical support engineers for assistance.
14.2.14 How to Handle the '/export/home/sybdev/master.dat' already in use Message?

This section describes how to handle the '/export/home/sybdev/master.dat' already in use message.
Question
The database log file /opt/sybase/ASE-15_0/install/SYB.log records the following message:
00:00000:00000:2009/10/24 23:43:08.24 kernel basis_dlock: file '/export/home/sybdev/master.dat' already in use by an ASE 00:00000:00000:2009/10/24 23:43:08.24 kernel kdconfig: unable to read primary master device 00:00000:00000:2009/10/24 23:43:08.24 server kiconfig: read of config block failed
NOTE
l l
Solution
The database log file records the '/export/home/sybdev/master.dat' already in use message, which indicates that the database is started during it is running. You can ingnore the problem. Before you start the database, check whether it is already started. For details, see 14.2.1 How Do I Check Whether the Sybase Is Started?.
14.2.15 What Should I Do to Handle Database Startup Failure Due to Incorrect User Type?
This section describes how to handle database startup failure due to incorrect user type.
Question
When the database is started, the system displays the following message:
00:00000:00000:2007/11/20 06:37:27.28 kernel 3rdTools/sybase/SYSAM-2_0/licenses SySAM: Using licenses from: /opt/OMC/
00:00000:00000:2007/11/20 06:37:27.31 kernel SySAM: Failed to get status of file / opt/OMC/3rdTools/sybase/ASE-15_0/sysam/SYB.properties. errno=2 No such file or directory. 00:00000:00000:2007/11/20 06:37:27.31 kernel SySAM: Failed to get status of file /
Issue 10 (2010-09-06)
14-49
14 FAQs (Sun)

opt/OMC/3rdTools/sybase/ASE-15_0/sysam/sysam.properties.template. errno=2 No such file or directory. 00:00000:00000:2007/11/20 06:37:27.31 kernel SySAM: Failed to get status of file / opt/OMC/3rdTools/sybase/ASE-15_0/sysam/SYB.properties. errno=2 No such file or directory. 00:00000:00000:2007/11/20 06:37:27.31 kernel SySAM: Failed to open /opt/OMC/ 3rdTools/sybase/ASE-15_0/sysam/SYB.properties file: errno=2 No such file or directory. 00:00000:00000:2007/11/20 06:37:27.31 kernel SySAM: Failed to get status of file / opt/OMC/3rdTools/sybase/ASE-15_0/sysam/SYB.properties. errno=2 No such file or directory. 00:00000:00000:2007/11/20 06:37:27.31 kernel fails. License manager initialization
00:00000:00000:2007/11/20 06:37:27.31 kernel There is no valid license for ASE server product. Installation date is not found or installation grace period has expired. Server will not boot
Solution
The database startup failure is caused by incorrect user type. The user who starts the database uses the environment variables of the M2000. The correct method is to use the environment variables of the Sybase to start the database. 1. 2. Log in to the server as user root. Run the following commands: # chown -R dbuser:staff /opt/Sybase # chown -R dbuser:staff /export/home/sybdev # su - dbuser -bash-3.00$ . /opt/sybase/SYBASE.sh 3. Start the Sybase database. For details, see 14.2.2 How to Start the Sybase.
14.3 About TCP/IP Network

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

This section describes how to handle the problem of the abnormal network port.
14-50
Issue 10 (2010-09-06)
14 FAQs (Sun)
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.
14.3.2 How to Connect the Client to the Server with More than One IP Address
This section 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.2.4 Stopping the 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 14.2.3 How Do I Stop the Sybase?. 4. Switch back to user root. -bash-3.00$ exit
14 FAQs (Sun)
5.
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.
14.4 About Server Software

This section describes some FAQs and solutions related to the M2000 server software. 14.4.1 Why M2000 Services Restart Abnormally This section describes how to handle the problem of the abnormal restart of the M2000 services. 14.4.2 Why M2000 Services Stop Abnormally This section describes how to handle the problem of abnormal stop of the M2000 services. 14.4.3 What Should I Do When I Fail to Start the M2000 Services? This section describes how to handle the failure to start the M2000 services. 14.4.4 What Should I Do When I Fail to Stop the M2000 Services? This section describes how to handle the failure to stop the M2000 services. 14.4.5 Why M2000 Dynamic Data Backup Fails This section describes how to handle the failure to back up the dynamic M2000 data. 14.4.6 How to Set the M2000 Administration Console as the Intermediary-Layer NTP Server (In Encryption Mode) This section describes how to set the M2000 administration console to synchronize time with the upper-layer server in encryption mode. After the setting, the M2000 administration console can function as the time source of the lower-layer server, and the M2000 server and NEs can synchronize time with the administration console in encryption mode. 14.4.7 How Do I Check the Running Status of the NTP Services on the Administration Console (In Encryption Mode)? After setting the administration console as the intermediary-layer NTP server in encryption mode, you need to check the running status of the NTP services on the administration console to ensure that they are running properly. 14.4.8 How to Set the M2000 Server as the NTP Client (In Encryption Mode) This section describes how to set the M2000 server as the NTP client to synchronize time with the upper-layer server in encryption mode.
14 FAQs (Sun)
14.4.9 How Should I Check the Running Status of the NTP Services on the M2000 Server (In Encryption Mode)? After setting the M2000 server as the NTP client in encryption mode, you need to check the running status of the NTP services on the server to ensure that the NTP services are running properly. 14.4.10 How Should I Handle an Incremental Backup Failure? This section describes the causes of the failure to back up the M2000 dynamic data incrementally. This section also describes how to solve this problem. 14.4.11 How Should I 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. 14.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SC This section describes how to power on the T5220 server through the serial port of the SC.
14.4.1 Why M2000 Services Restart Abnormally

This section 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.2.4 Stopping the 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 14.2.3 How Do I 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 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit 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.2.3 Starting the M2000 System Services.
14 FAQs (Sun)
7.
Check system logs. Check system logs. For details, see 6.2 Querying the System Logs of the M2000.
14.4.2 Why M2000 Services Stop Abnormally

This section 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 any service is not started, run the following command to start it: # svc_adm -cmd restartsvc name of the service that is not started
NOTE
If the service fails to be started, contact Huawei technical support engineers for support.
14.4.3 What Should I Do When I Fail to Start the M2000 Services?

This section describes how to handle the failure to start the M2000 services.
Question
The M2000 services fail to be started.
Causes
l
Cause 1: You run the start_svc command directly to start the M2000 services without running the environment script. The system output is as follows:
14-54
Issue 10 (2010-09-06)
14 FAQs (Sun)
command not found

l
Cause 2: The system file is damaged due to reasons such as upgrade, abnormal power-off, and changes on the server configuration. Therefore, the TAO process fails when you start the M2000 services. The system output is as follows:
starting TAO Naming Service [FAIL ] starting TAO Notification Service [FAIL]
Cause 3: The port is occupied, and therefore the M2000 services fail to be started. The system output is similar to the following information:
============================ Starting System ... failed to start KernelMonitor,maybe KernelMonitor is already running. TAO Naming Service is running TAO Notification Service is running port is in use 31019, maybe ServiceManager is running. sysagent port is in use 31000, maybe imapsysd is running.
Solution to Cause 1
To rectify this fault, perform the following steps: 1. 2. Log in to the server as user root. Run the environment script. # . /opt/OMC/svc_profile.sh
NOTE
The default installation directory of the M2000 server is /opt/OMC. Replace the directory according to the actual situation.
3.
Run the following commands to start the M2000 services: # start_svc
Solution to Cause 2 and Cause 3

To rectify the fault, perform the following steps: 1. 2. 3. Log in to the server as user root. Run the following command to terminate the daemon process. # kill_daem Run the following command to delete the old system files: # cd $IMAP_ROOT/var/share # rm *ior* 4. Run the following commands to restart the M2000 services: # start_svc
14.4.4 What Should I Do When I Fail to Stop the M2000 Services?

This section describes how to handle the failure to stop the M2000 services.
14 FAQs (Sun)
Question
Why is that the following commands fail to be executed?
l l
stop_svc kill_svc
Answer
If the system output is command not found, the possible cause is that you do not run the environment script before running these commands. To rectify this fault, perform the following steps: 1. 2. Log in to the server as user root. Run the environment script. For details, see M2000 Command Reference.
14.4.5 Why M2000 Dynamic Data Backup Fails

This section 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
14-56
Issue 10 (2010-09-06)

NOTE
14 FAQs (Sun)
Collation Name Collation ID ------------------------------ -----------Loadable Sort Table Name -----------------------------Sort Order Description -----------------------------------------------------------------Character Set = 1, iso_1 ISO 8859-1 (Latin-1) - Western European 8-bit character set. Sort Order = 50, bin_iso_1 Binary ordering, for the ISO 8859/1 or Latin-1 character set ( iso_1). Characters, in Order
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 are the same as the settings on the server.
[sun_svr4] ; from Solaris International Developer's Guide ; ISBN 0-13-031063-8 ; refer to "man setlocale()" locale = C, us_english, iso_1 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
Issue 10 (2010-09-06)
14-57
14 FAQs (Sun)
4.
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
5.
Delete manually the other processes in the database except backupserver. In this example, delete the processes titled 6217 and 6218. # kill -96217 6218
14.4.6 How to Set the M2000 Administration Console as the Intermediary-Layer NTP Server (In Encryption Mode)
This section describes how to set the M2000 administration console to synchronize time with the upper-layer server in encryption mode. After the setting, the M2000 administration console can function as the time source of the lower-layer server, and the M2000 server and NEs can synchronize time with the administration console in encryption mode.
Prerequisite
l l
You have configured the upper-layer NTP server in encryption mode. You have obtained the identifier, key type, and authentication code of the upper-layer NTP server. The time zone, date, and time of the M2000 administration console are correctly set. You have logged in to the M2000 administration console as user root.
l l
Context
l l
Normally, the M2000 server is set as the NTP client. If no server is available to be set as the intermediary-layer time server, set the administration console of the M2000 system, that is, the Netra 240 server, to be the intermediary-layer time server. The upper-layer time server of the M2000 administration console requires that the NTP protocol must be used. The server running on the Windows operating system uses the SNTP protocol. Thus, it cannot be used as the upper-layer time server of the M2000 administration console.
Procedure
1. Run the following commands to edit the /etc/inet/ntp.keys file: # TERM=vt100; export TERM # vi /etc/inet/ntp.keys Add the identifier, key type, and authentication code of the upper-layer NTP server to the file according to the following syntax: At the same time, you can define the authentication code required for synchronizing the time between a lower-layer NTP client and the current server. Write only one data item in each line. identifier key type authentication code

NOTE
14 FAQs (Sun)
l l
An identifier refers to a positive integer ranging from 1 to 4294967295. Each line in the file must contain one unique identifier. A key type is a character and refers to the encryption algorithm for calculating NTP services. S refers to the DES algorithm in standard format, N refers to the DES algorithm in NTP format, A refers to the ASCII algorithm, and M refers to the MD5 algorithm. An authentication code is used as the input parameter corresponding to an algorithm. The format of an authentication code depends on the corresponding algorithm.
2. 3.
Save the ntp.keys file and exit the vi editor. After editing the file, press Esc, and then run the :wq! command to save the file and exit. Run the following commands to open the /etc/inet/ntp.conf file: # cp /etc/inet/ntp.server /etc/inet/ntp.conf # TERM=vt100; export TERM # vi /etc/inet/ntp.conf
4.
In front of server 127.127.XType.0, add server IP address of the upper-layer NTP server key identifier prefer to specify the IP address and identifier of the upper-layer NTP server.
NOTE
prefer indicates that the IP address of the NTP server is synchronized preferentially. If multiple upper-level NTP servers exist, add multiple lines. Ensure that each line maps to one NTP server. For example,
server IP address of upper-layer NTP server 1 key identifier 1 prefer server IP address of upper-layer NTP server 2 key identifier 2
5.
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 functions as the standard time source. Delete stratum 0 from fudge 127.127.1.0 stratum 0. In front of broadcast 224.0.1.1 ttl 4, add # to comment out this line to disable the broadcast mode. Delete 0 from trustedkey 0 to add the identifier of the upper-layer NTP server and the identifier used by the NTP client for synchronizing time with the current server. Separate the two identifiers with a space. Add enable auth to the file. After editing the file, press Esc, and then run the :wq! command to save the file and exit.
6. 7. 8.
9.
10. Save the ntp.conf file and exit the vi editor. 11. Run the following command to modify the rights of the ntp.keys file and the ntp.conf file: # chmod 400 /etc/inet/ntp.keys # chmod 400 /etc/inet/ntp.conf
Task Instance
Assume that the administration console synchronizes the upper-layer time servers whose IP addresses are 10.161.94.212 and 10.161.94.214, the upper-layer time server uses the MD5 algorithm, the identifiers are 5 and 3, and the corresponding authentication codes are tPol3kRS and l2082skt. Assume that the MD5 algorithm is used, the identifier is 12, and the authentication code is k0ssL09a during the synchronization of the time between the client and the current server.
14 FAQs (Sun)
The contents of the created /etc/inet/ntp.keys file are as follows:

5 M tPol3kRS 3 M l2082skt 12 M k0ssL09a
The contents of the /etc/inet/ntp.conf file before the modification are as follows:
server 127.127.XType.0 fudge 127.127.XType.0 stratum 0 broadcast 224.0.1.1 ttl 4 keys /etc/inet/ntp.keys trustedkey 0
The contents of the /etc/inet/ntp.conf file after the modification are as follows:
server 10.161.94.212 key 5 prefer server 10.161.94.214 key 3 server 127.127.1.0 fudge 127.127.1.0 #broadcast 224.0.1.1 ttl 4 keys /etc/inet/ntp.keys enable auth trustedkey 5 3 12
Postprocessing
After setting the M2000 administration console as the intermediary-layer NTP server, you need to start the NTP services on the administration console. For details, see 2.5.3 Starting the NTP Service on the M2000 Administration Console.
14.4.7 How Do I Check the Running Status of the NTP Services on the Administration Console (In Encryption Mode)?
After setting the administration console as the intermediary-layer NTP server in encryption mode, you need to check the running status of the NTP services on the administration console to ensure that they are running properly.
Context
After the NTP server and client are started, the system requires five minutes for system test. Wait for about five minutes, and then run the ntpq -p command and the ntptrace command to query the status of the NTP services. During system test, if you run the ntpq -p command, the displayed address of the remote time source does not contain *. If you run the ntptrace command, the system displays Timeout or Not Synchronized.
Procedure
1. 2. You have logged in to the M2000 administration console as user root. Run the following command to view the information about the time source: # ntpq -p In the result of the ntpq -p command, the remote field shows the address and status of the time source of the M2000 server. 3. Run the following command to check the information about the clock synchronization path: # ntptrace
14 FAQs (Sun)
The ntptrace command traces the NTP synchronization path from the host to the top-layer NTP server. For details, run the ntptrace -v command. 4. Run the following command to check the status of NTP authentication: # ntpq ntpq> as The system output is similar to the following information:
ind assID status conf reach auth condition last_event cnt =========================================================== 1 28852 f614 yes yes ok sys.peer reachable 1
In the system output, if auth is ok, it indicates that the NTP services are successfully authenticated. ntpq> exit
Task Instance
The administration console functions as the intermediary-layer NTP server. # ntpq -p
remote refid st t when poll reach delay offset disp ============================================================================== *10.71.15.69 .LCL. 1 u 13 64 377 0.56 -0.730 0.06 LOCAL(0) LOCAL(0) 3 l 12 64 377 0.00 0.000 10.01
# ntptrace
localhost: stratum 2, offset 0.000043, synch distance 0.02032 10.71.15.69: stratum 1, offset -0.000714, synch distance 0.01007, refid 'LCL'
# ntpq ntpq> as
ind assID status conf reach auth condition last_event cnt =========================================================== 1 15820 f614 yes yes ok sys.peer reachable 1 2 15821 9014 yes yes none insane reachable 1
ntpq> exit *10.71.15.69 in the result of the ntpq -p command indicates that the IP address of the NTP server that the host is synchronized with is 10.71.15.69. The value 1 in the st column indicates that the host is located at stratum 1. The symbol * indicates that the NTP services are running properly. The result of the ntptrace command indicates that the host is located at stratum 2, that the IP address of the upper-level server is 10.71.15.69, and that the upper-level server is at stratum 1. Run the ntpq command, and then type as. If auth is ok, it indicates that the authentication between the host and the upper-layer NTP server is successful.
14.4.8 How to Set the M2000 Server as the NTP Client (In Encryption Mode)
This section describes how to set the M2000 server as the NTP client to synchronize time with the upper-layer server in encryption mode.
14 FAQs (Sun)
Prerequisite
l l
You have configured the upper-layer NTP server in encryption mode. You have obtained the identifier, key type, and authentication code of the upper-layer NTP server. The time zone, date, and time of the M2000 server are set correctly. You have logged in to the server as user root.
l l
Context
The upper-layer time server of the M2000 server requires that the NTP protocol must be used. The server running on the Windows operating system uses the SNTP protocol. Thus, it cannot be used as the upper-layer time server of the M2000 server.
Procedure
1. 2. If any M2000 service is running, stop it. For details, see 7.2.4 Stopping the M2000 Services. If any Sybase service is running, run the following command to stop it: # su - dbuser For details about how to stop the Sybase services, see 14.2.3 How Do I Stop the Sybase?. -bash-3.00$ exit 3. Run the following commands to edit the /etc/inet/ntp.keys file: # TERM=vt100; export TERM # vi /etc/inet/ntp.keys Add the identifier, key type, and authentication code of the upper-layer NTP server to the file according to the following syntax: Write only one data item in each line. identifier key type authentication code
NOTE
l l
An identifier refers to a positive integer ranging from 1 to 4294967295. Each line in the file must contain one unique identifier. A key type is a character and refers to the encryption algorithm for calculating NTP services. S refers to the DES algorithm in standard format, N refers to the DES algorithm in NTP format, A refers to the ASCII algorithm, and M refers to the MD5 algorithm. An authentication code is used as the input parameter corresponding to an algorithm. The format of an authentication code depends on the corresponding algorithm.
4. 5.
Save the ntp.keys file and exit the vi editor. After editing the file, press Esc, and then run the :wq! command to save the file and exit. Run the following commands to 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
6.
Add server IP address of the upper level NTP server key identifier at the end of the file to specify the IP addresses and identifiers of upper-layer NTP servers. Each line maps to one NTP server.
14-62
14 FAQs (Sun)
7.
Add the following contents to the file:

enable auth keys /etc/inet/ntp.keys trustedkey N
N in the last line refers to the identifier used for NTP authentication. If multiple upper-layer NTP servers exist, write the identifiers of these servers in one line. Separate the identifiers with spaces. For example, trustedkey 3 4 8. In front of multicastclient 224.0.1.1, add # to comment out the line to disable the multicast client.
NOTE
Either the multicast client or the upper-lay NTP server takes effect.
9.
Save the ntp.conf file and exit the vi editor. After editing the file, press Esc, and then run the :wq! command to save the file and exit.
10. Run the following commands to modify the rights of the ntp.keys file and the ntp.conf file: # chmod 400 /etc/inet/ntp.keys # chmod 400 /etc/inet/ntp.conf 11. If the Sybase services are stopped in 2, run the following command to start them: # su - dbuser For details about how to start the Sybase services, see 14.2.2 How to Start the Sybase. -bash-3.00$ exit 12. If the M2000 services are stopped in 1, start them. For details, see 7.2.3 Starting the M2000 System Services.
Task Instance
Assume that the M2000 server is set to synchronize the time of the upper-layer time server whose IP address is 10.71.15.97, the upper-layer time server uses the MD5 algorithm, the identifier is 12, and the key type is k0ssL09a. The contents of the created /etc/inet/ntp.keys file are as follows:
12 M k0ssL09a
The contents of the /etc/inet/ntp.conf file before the modification are as follows:
multicastclient 224.0.1.1
The contents of the /etc/inet/ntp.conf file after the modification are as follows:
server 10.71.15.97 key 12 enable auth keys /etc/inet/ntp.keys trustedkey 12 #multicastclient 224.0.1.1
Postprocessing
After setting the M2000 server as the NTP client, you need to start the NTP services on the server. For details, see 2.5.6 Starting the NTP Service on the M2000 Server.
14 FAQs (Sun)
14.4.9 How Should I Check the Running Status of the NTP Services on the M2000 Server (In Encryption Mode)?
After setting the M2000 server as the NTP client in encryption mode, you need to check the running status of the NTP services on the server to ensure that the NTP services are running properly.
Context
After the NTP server and client are started, the system requires five minutes for system test. Wait for about five minutes, and then run the ntpq -p command and the ntptrace command to query the status of the NTP services. During system test, if you run the ntpq -p command, the displayed address of the remote time source does not contain *. If you run the ntptrace command, the system displays Timeout or Not Synchronized.
Procedure
1. 2. You have logged in to the server as user root. Run the following command to view the information about the time source: # ntpq -p In the result of the ntpq -p command, the remote field shows the address and status of the time source of the M2000 server. 3. Run the following command to check the information about the clock synchronization path: # ntptrace The ntptrace command traces the NTP synchronization path from the host to the top-layer NTP server. For details, run the ntptrace -v command. 4. Run the following command to check the status of NTP authentication: # ntpq ntpq> as The system output is similar to the following information:
In the system output, if auth is ok, it indicates that the NTP services are successfully authenticated. ntpq> exit
Task Instance
The M2000 server functions as the NTP client. # ntpq -p
remote refid st t when poll reach delay offset disp ============================================================================== *10.71.15.97 10.71.15.69 2 u 29 64 377 0.44 -0.428 0.09
# ntptrace
14 FAQs (Sun)
localhost: stratum 3, offset 0.000040, synch distance 0.89705 10.71.15.97: stratum 2, offset 0.000008, synch distance 0.02142 10.71.15.69: stratum 1, offset -0.000024, synch distance 0.01059, refid 'LCL'
# ntpq ntpq> as
ntpq> exit *10.71.15.97 in the result of the ntpq -p command indicates that the IP address of the NTP server that the host is synchronized with is 10.71.15.97. The value 2 in the st column indicates that the host is located at stratum 2. The symbol * indicates that the NTP services are running properly. The result of the ntptrace command indicates that the host is located at stratum 3, that the IP address of the stratum-2 server is 10.71.15.97, and that the IP address of the stratum-1 server is 10.71.15.69. Run the ntpq command, and then type as. If auth is ok, it indicates that the authentication between the host and the upper-layer NTP server is successful.
14.4.10 How Should I Handle an Incremental Backup Failure?

This section describes the causes of the failure to back up the M2000 dynamic data incrementally. This section also describes how to solve this problem.
Problem
The M2000 dynamic data fails to be backed up incrementally.
Cause
The causes of the incremental data backup failure are as follows:
l l
The database logs are not consecutive. The disk space is insufficient.
Solution
l
The database logs are not consecutive. 1. Check the backup and restore log. # more /opt/OMC/var/logs/backup.log If the log contains truncate-only transaction dump has been performed, it indicates that the database logs are truncated manually. If the log contains non-logged operation, it indicates that a manual operation is performed on the database so that the database does not record event logs. 2. Perform a full backup again. For details, see 10.2.5 Manually Backing Up the M2000 Dynamic Data.
The disk space is insufficient.

Issue 10 (2010-09-06)
14 FAQs (Sun)
1.
Check the backup and restore log. # more /opt/OMC/var/logs/backup.log If the log contains the following information, it indicates that the backup space is insufficient.
The free disk space is low ,give up buck! The free disk space of /export/home/ is low. Give up backup!
2.
Clear the disk space of the M2000 server. For details, see 14.1.17 What Should I Do When the Server Disk Space Is Insufficient?.
3.
Perform a full backup again. For details, see 10.2.5 Manually Backing Up the M2000 Dynamic Data.
14.4.11 How Should I 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
You have logged in to the M2000 server as user root.
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
The CPU and the memory performance report file records performance reports in the following format:
Hostname, Time, CPU Occupancy(%), MEM Occupancy(%), Physical Memory(KB), Remaining Physical Memory(KB), Swap Memory(KB), Remaining Swap Memory(KB)
The disk usage report file records disk usage reports in the following format:
Hostname, Time, Partition Name, Total Size(KB), Used Size(KB), Remaining Size(KB), Used Rate(%), IO 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.

l
14 FAQs (Sun)
Enable the function of exporting a performance report. # svc_monitor -cmd start -type system Enable the function of exporting a disk usage report. # svc_monitor -cmd start -type disk
The performance report is saved as a .csv file in M2000 server installation path/var/monitor/ sysinfo. The default file name is sysinfo. The disk usage report is saved as a .csv file in M2000 server installation path/var/monitor/diskinfo. The default file name is diskinfo. Step 4 View the exported reports.
l
View the performance report. # cd M2000 server installation path/var/monitor/sysinfo # more Performance report file name
Check the report about disk usage. # cd M2000 server installation path/var/monitor/diskinfo # more Disk usage report file name
----End
14.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SC
This section describes how to power on the T5220 server through the serial port of the SC.
Question
How should I power on the T5220 server through the serial port of the SC?
Answer
Before powering on the server, ensure that the following conditions are met:
l l l
The SC of the server is configured. The communication between the PC and the Ethernet port on the server SC is normal. The password of user admin of the SC is available.
Perform the following steps: 1. Start the PuTTY on the PC terminal and set up the connection between the PC and the SC based on the SSH protocol. In the PuTTY Configuration window, select SSH, enter IP address of the SC in Host Name (or IP Address), and then click Open to log in to the SC.
NOTE
l l
Log in to the http://support.huawei.com to download the PuTTY to the PC. If the PC and SC cannot be connected through the PuTTY, connect them by using a serial port cable. For details, see the corresponding software initial installation guide.
2.
Enter the user name admin and the password to log in to the SC. The sc> prompt is displayed.
Issue 10 (2010-09-06)
14-67
14 FAQs (Sun)
3. 4.
Run the following command to power on the server: sc> poweron Run the console command, and then press Enter to connect the server.
NOTE
After the console command is executed, if the system displays Console session already in use. [view mode], it indicates that you have not logged out of the console last time. In this case, run the console -f command to connect the server. When the system displays a confirmation message, type y, and then press Enter.
If the Solaris operating system is not installed, the system is switched to the ok state after the T5220 is started. If the Solaris, Sybase, or M2000 server software is correctly installed, the system automatically starts the Solaris, Sybase, or M2000 server software after the T5220 is started.
14-68
Issue 10 (2010-09-06)

M2000 Administrator Guide (Sun, S10) (V200R009 - 10)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

M2000 Administrator Guide (Sun, S10) (V200R009 - 10)

Hochgeladen von

Copyright:

Verfügbare Formate

M2000 V200R009

Administrator Guide (Sun, S10)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.