M2000 Administrator Guide (Sun, S10)(V200R009_10)

M2000V200R009

Administrator Guide (Sun, S10)

Issue 10

Date 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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 10 (2010-09-06) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document provides the system administration tasks, the related concepts, the detailedoperation procedures of the system administration tasks, the routine maintenance, and thetroubleshooting and emergency maintenance. The document is used in the following situations:l The operating system is Solaris 10.

l The database device is a bare device.

l The database is Sybase15.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

M2000 V200R009

Intended AudienceThe 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.

M2000Administrator Guide (Sun, S10) About This Document


iii

Content Description

14.1.19 How Should I Configure theMonitoring Function for the S3000 SeriesDisk Arrays

New added.

14.1.20 How Should I Uninstall theOceanStor Monitoring Software

New added.

09 (2010-07-30)Formal release for the ninth time.


Content Description

7.2.3 Starting the M2000 System Services The content descriptions are changed.

7.2.4 Stopping the M2000 Services The content descriptions are changed.

8.4 Backing Up M2000 Databases The content descriptions are changed.

10.2.4 Periodically Backing Up theM2000 Dynamic Data

The content descriptions are changed.

10.2.6 Restoring the M2000 DynamicData


11.3.10 Backing Up the M2000 The content descriptions are changed.

08 (2010-06-15)Formal release for the eighth time.


Content Description

2.5.8 Setting the NTP Service on theM2000 Client


5.2.5 Changing the Password of Userftpuser


5.3.2 Changing the Password of User sa The content descriptions are changed.

7.1.61 son_agent Process The content descriptions are changed.

7.1.62 swm_agent Process The content descriptions are changed.

About This DocumentM2000


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Content Description

10.2.6 Restoring the M2000 DynamicData


07 (2010-03-30)Formal release for the seventh time.


Content Description

3.2.3 Changing the IP Address ofEthernet Port nxge3 on the M2000 Server


14.1.13 How Do I Change the IP Addressof the S2600 Disk Array (CommandMode)?


14.1.21 How Should I Check the RunningStatus of the FTP Service on the M2000Server?

New added.

14.1.22 How Should I Start the FTPService on the M2000 Server?

New added.

14.1.23 How Should I Check the RunningStatus of the SFTP Service on the M2000Server?

New added.

14.1.24 How Should I Start the SFTPService on the M2000 Server?

New added.

14.4.10 How Should I Handle anIncremental Backup Failure?

New added.

06 (2010-01-20)Sixth commercial release.

Compared with V200R009 05 issued on December 10 of 2009, this version has the followingmodifications:

The content descriptions are optimized in 3 Setting the Host Name and IP Address for theM2000 Server.



v

05 (2009-12-10)Fifth commercial release.

Compared with V200R009 04 issued on October 31 of 2009, this version has the followingmodifications:

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 followingmodifications:

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 followingmodifications:

The content descriptions are optimized in 7.1 Introduction to M2000 Processes andServices.

02 (2009-07-25)Second commercial release.

Compared with V200R009 01 issued on June 30 of 2009, this version has the followingmodifications:

The content descriptions are optimized in 7.1 Introduction to M2000 Processes andServices.

01 (2009-06-30)Initial release. Also, the first formal release.

Organization1 Powering the M2000 On or Off

This chapter describes how to power on and power off the M2000 server.



vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

2 Setting the M2000 Time

This chapter describes how to set the M2000 time. To enable the M2000 time to meet the timerequirements, you must synchronize the time of the M2000 with the time of the other Huaweidevices 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, accordingto field requirements.

4 Managing the M2000 Clients

This chapter describes how to manage the M2000 clients. The graphic user interface (GUI) onthe M2000 client supports the O&M for the NEs and enables you to monitor the M2000. Youmust 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 themanagement 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 viewingNE partitioning, managing the M2000 license, monitoring the M2000 server, integrated taskmanagement, 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 theM2000 routine maintenance. These items are, however, only for reference. Specific maintenanceitems are required in real applications.

12 M2000 Emergency Maintenance

This chapter describes the emergency maintenance in the case of a critical fault in the M2000server or client. This chapter covers the server emergency maintenance, client emergencymaintenance, and emergency maintenance for the server power-off.

13 Troubleshooting the M2000

This chapter describes the procedures for troubleshooting the M2000.

14 FAQs (Sun)



vii

This chapter describes FAQs and solutions related to the M2000.

ConventionsSymbol 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 notavoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided,could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.



viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)


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

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare 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 Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.



ix

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.



x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Contents

About This Document...................................................................................................................iii

1 Powering the M2000 On or Off...............................................................................................1-11.1 Powering the M2000 On or Off (Netra240)....................................................................................................1-2

1.1.1 Powering On the M2000 (Netra240)......................................................................................................1-21.1.2 Powering Off the M2000 (Netra 240)....................................................................................................1-3

1.2 Powering the M2000 On or Off (V890)..........................................................................................................1-41.2.1 Powering On the M2000 (V890)............................................................................................................1-41.2.2 Powering Off the M2000 (V890)...........................................................................................................1-6

1.3 Powering the M2000 On or Off (E4900)........................................................................................................1-81.3.1 Powering On the M2000 (E4900)..........................................................................................................1-81.3.2 Powering Off the M2000 (E4900).......................................................................................................1-12

1.4 Powering the M2000 On or Off (T5220)......................................................................................................1-141.4.1 Powering On the M2000 (T5220)........................................................................................................1-151.4.2 Powering Off the M2000 (T5220).......................................................................................................1-16

1.5 Powering the M2000 On or Off (M4000/M5000)........................................................................................1-161.5.1 Powering On the M2000 (M4000/M5000)..........................................................................................1-161.5.2 Powering Off the M2000 (M4000/M5000)..........................................................................................1-20

2 Setting the M2000 Time............................................................................................................2-12.1 Time Management for the Huawei Mobile Network......................................................................................2-2

2.1.1 Introduction to Time Synchronization................................................................................................... 2-22.1.2 Introduction to the NTP/SNTP...............................................................................................................2-32.1.3 Time Synchronization Modes of Huawei Mobile Network...................................................................2-62.1.4 Introduction to the DST........................................................................................................................2-12

2.2 Modifying the Date and Time on the M2000 Server....................................................................................2-122.3 Changing the Time Zone of the M2000 Server Without Using DST...........................................................2-142.4 Modifying the Date, Time, and Time Zone on the M2000 Client................................................................2-152.5 Configuring the NTP Service of the M2000.................................................................................................2-16

2.5.1 Checking the Time Settings of the M2000 Server...............................................................................2-172.5.2 Setting the M2000 Administration Console as the Secondary NTP Server.........................................2-172.5.3 Starting the NTP Service on the M2000 Administration Console.......................................................2-192.5.4 Checking the Running Status of the NTP Service on the M2000 Administration Console.................2-192.5.5 Setting the M2000 Server as the NTP Client.......................................................................................2-20

M2000Administrator Guide (Sun, S10) Contents


xi

2.5.6 Starting the NTP Service on the M2000 Server...................................................................................2-212.5.7 Checking the Running Status of the NTP Service on the M2000 Server............................................2-222.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-13.1 Changing the Host Name of the M2000 Server..............................................................................................3-23.2 Modifying the IP Address of the M2000 Server.............................................................................................3-5

3.2.1 Adding or Deleting Routes on the M2000 Server..................................................................................3-53.2.2 Changing the IP Address of the M2000 Server......................................................................................3-63.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-153.3.1 Modifying the IP Address of the SC on the Netra 240 Server.............................................................3-163.3.2 Changing the IP Address of the RSC on the V890 Server...................................................................3-173.3.3 Modifying the IP Address of the SC on the E4900 Server..................................................................3-173.3.4 Modifying the IP Address of the SC on the T5220 Server..................................................................3-203.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-233.4.1 Modifying the IP Address of the 3320 Disk Array..............................................................................3-233.4.2 Changing the IP Address of the S3200 Series Disk Array (Serial Port Mode)....................................3-243.4.3 Changing the IP Address of the S2600 Disk Array (Serial Port Mode)..............................................3-273.4.4 Changing the IP Address of the 6140 Disk Array (Serial Port Mode).................................................3-31

4 Managing the M2000 Clients...................................................................................................4-14.1 Managing Files and Disks on M2000 Clients.................................................................................................4-2

4.1.1 Introduction to the M2000 Client File System.......................................................................................4-24.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................4-4

4.2 Monitoring the Login Status of the M2000 Clients........................................................................................4-54.3 Setting the Number of Clients Accessible on a PC.........................................................................................4-54.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-74.4.2 Setting the NTP Service on the M2000 Client.......................................................................................4-7

5 Managing the M2000 Users......................................................................................................5-15.1 Types of M2000 Users....................................................................................................................................5-2

5.1.1 Introduction to Solaris Users..................................................................................................................5-25.1.2 Introduction to Sybase Users..................................................................................................................5-45.1.3 NE Users................................................................................................................................................5-45.1.4 Principles of NM User Authorization....................................................................................................5-65.1.5 Principles of NE User Authorization.....................................................................................................5-7

5.2 Managing Solaris Users..................................................................................................................................5-75.2.1 Introduction to Solaris Users..................................................................................................................5-85.2.2 Changing the Password of User root....................................................................................................5-105.2.3 Changing the Password of User dbuser................................................................................................5-11

ContentsM2000


xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

5.2.4 Changing the Password of User omcuser.............................................................................................5-115.2.5 Changing the Password of User ftpuser...............................................................................................5-125.2.6 Creating a Solaris User.........................................................................................................................5-145.2.7 Deleting a Solaris User.........................................................................................................................5-14

5.3 Managing Sybase Users................................................................................................................................5-155.3.1 Introduction to Sybase Users................................................................................................................5-155.3.2 Changing the Password of User sa.......................................................................................................5-155.3.3 Changing the Name of the Database Server.........................................................................................5-17

5.4 Managing OM Users.....................................................................................................................................5-19

6 Managing OSS System..............................................................................................................6-16.1 Monitoring the M2000 Server.........................................................................................................................6-3

6.1.1 Refreshing the Monitoring Information.................................................................................................6-46.1.2 Checking the CPU and Memory Usage Information About the M2000 Server....................................6-46.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client..............6-56.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000 Client.........................................................................................................................................................................6-66.1.5 Checking the M2000 Services................................................................................................................6-76.1.6 Checking the Status of the M2000 Processes.........................................................................................6-86.1.7 Viewing the Information about M2000 Server Components.................................................................6-96.1.8 Saving the Monitoring Information......................................................................................................6-106.1.9 Setting Alarm Thresholds for the M2000............................................................................................6-10

6.2 Querying the System Logs of the M2000.....................................................................................................6-186.3 Collecting NM Log Files...............................................................................................................................6-196.4 Querying NE Subareas..................................................................................................................................6-216.5 Managing the M2000 License.......................................................................................................................6-21

6.5.1 Querying the M2000 License...............................................................................................................6-226.5.2 Updating the M2000 License...............................................................................................................6-22

6.6 Check OMC status........................................................................................................................................6-226.7 Integrated Task Management........................................................................................................................6-23

6.7.1 Basic Knowledge..................................................................................................................................6-246.7.2 Customizing the Interface for Managing Timing Tasks......................................................................6-366.7.3 Creating a User Timing Task...............................................................................................................6-376.7.4 Modifying a Timing Task....................................................................................................................6-386.7.5 Managing Timing Tasks.......................................................................................................................6-396.7.6 Browsing the Information of Timing Tasks.........................................................................................6-426.7.7 Viewing the Task Execution................................................................................................................6-426.7.8 Downloading Result Files....................................................................................................................6-436.7.9 Technical Specifications of Centralized Task Management................................................................6-46

6.8 Reference of the OSS Management GUI......................................................................................................6-476.8.1 Interface Description: Managing Timing Tasks...................................................................................6-496.8.2 Interface Description: M2000 Log Information Collector...................................................................6-516.8.3 Parameters for the NE Partitioning Information..................................................................................6-51



xiii

6.8.4 Parameters for Querying the M2000 License ......................................................................................6-526.8.5 Parameters for Setting Monitoring Parameters of the M2000 Server..................................................6-536.8.6 Parameters for Monitoring the M2000 Server Service Status..............................................................6-596.8.7 Parameters for Monitoring the M2000 Server Process Status............................................................. 6-606.8.8 Parameters for Monitoring the M2000 Server Hard Disk Status.........................................................6-606.8.9 Parameters for Monitoring the M2000 Server Database Status...........................................................6-616.8.10 Parameters for Setting Task Filter Conditions...................................................................................6-626.8.11 Parameters for Setting the Common Information About Timing Tasks............................................6-646.8.12 Parameters for Modifying Database Capacity....................................................................................6-656.8.13 Parameters for Modifying File interface Task................................................................................... 6-696.8.14 Parameters for Modifying Synchronization task................................................................................6-776.8.15 Parameters for Modifying NE Basic Information Export Task......................................................... 6-776.8.16 Parameters for Modifying Alarm Timing Acknowledgement...........................................................6-786.8.17 Parameters for Modifying Data Backup Task....................................................................................6-786.8.18 Parameters for Creating/Modifying/Copying MML Command Script..............................................6-806.8.19 Parameters for Creating/Modifying/Copying RAN Report Task...................................................... 6-826.8.20 Parameters for Creating, Viewing, or Modifying a Scheduled Report Task..................................... 6-826.8.21 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top Power..............6-866.8.22 Parameters for Creating/Modifying/Copying an RSSI Test Task......................................................6-876.8.23 Parameters for Creating/Modifying/Copying Software Download....................................................6-876.8.24 Parameters for Creating/Modifying/Copying Dual-Home Management...........................................6-886.8.25 Parameters for Creating/Modifying/Copying iSStar Script...............................................................6-886.8.26 Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log..................................6-896.8.27 Parameters for Creating/Modifying/Copying a CME Upload Task...................................................6-896.8.28 Parameters for Creating/Modifying/Copying Cell Parameters Compare Task..................................6-906.8.29 Parameters for Creating/Modifying/Copying Cell Consistency Check Task.................................... 6-916.8.30 Parameters for Creating/Modifying/Copying a CME Current Area Export Task..............................6-916.8.31 Parameters for Setting Time of Timing Tasks...................................................................................6-926.8.32 Parameters for Selecting Objects for Device Check..........................................................................6-936.8.33 Parameters for Collecting NM Logs Parameters................................................................................6-93

7 Managing M2000 Processes and Services..............................................................................7-17.1 Introduction to M2000 Processes and Services...............................................................................................7-2

7.1.1 3rdTool_agent Process...........................................................................................................................7-57.1.2 adn_agent Process..................................................................................................................................7-57.1.3 adss_agent Process.................................................................................................................................7-67.1.4 antenna_agent Process............................................................................................................................7-67.1.5 ce_agent Process....................................................................................................................................7-67.1.6 cmdc_agent Process...............................................................................................................................7-67.1.7 cmengine_agent Process........................................................................................................................7-67.1.8 cmeserver_agent Process........................................................................................................................7-77.1.9 cmexp_agent Process.............................................................................................................................7-77.1.10 cmserver_agent Process.......................................................................................................................7-7

ContentsM2000


xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

7.1.11 cnnhc_agent Process............................................................................................................................7-87.1.12 corba_agent Process.............................................................................................................................7-87.1.13 cpm_agent Process...............................................................................................................................7-87.1.14 devdoc_agent Process..........................................................................................................................7-87.1.15 dsXXXX agent Process..........................................................................................................................7-87.1.16 eam_agent Process...............................................................................................................................7-97.1.17 fars_agent Process................................................................................................................................7-97.1.18 fmnotify_agent Process........................................................................................................................7-97.1.19 FMPreServiceXXXX_agent Process...................................................................................................7-107.1.20 fnlicense_agent Process......................................................................................................................7-107.1.21 glmssyn_agent Process.......................................................................................................................7-107.1.22 ifms_agent Process.............................................................................................................................7-107.1.23 ipqdt_agent Process............................................................................................................................7-117.1.24 ipm_agent Process..............................................................................................................................7-117.1.25 irp_agent Process................................................................................................................................7-117.1.26 itm_agent Process...............................................................................................................................7-127.1.27 lcsserver_agent Process......................................................................................................................7-127.1.28 lic_agent Process................................................................................................................................7-137.1.29 log_agent Process...............................................................................................................................7-137.1.30 lte_agent Process................................................................................................................................7-137.1.31 maintain_agent Process......................................................................................................................7-137.1.32 manager_agent Process......................................................................................................................7-137.1.33 medXXXX_agent Process...................................................................................................................7-147.1.34 nelicense_agent Process.....................................................................................................................7-147.1.35 neuser_agent Process..........................................................................................................................7-147.1.36 ngnffs_agent Process..........................................................................................................................7-157.1.37 ngnnis_agent Process.........................................................................................................................7-157.1.38 ngnni112_agent Process.....................................................................................................................7-157.1.39 ngntestmanage_agent Process............................................................................................................7-157.1.40 nhcservice_agent Process...................................................................................................................7-157.1.41 nicservice_agent Process....................................................................................................................7-157.1.42 nimserver_agent Process....................................................................................................................7-167.1.43 nms_mml_agent Process....................................................................................................................7-167.1.44 partition_agent Process......................................................................................................................7-167.1.45 pm_agent Process...............................................................................................................................7-167.1.46 pmexp_agent Process.........................................................................................................................7-177.1.47 pmmon_agent Process........................................................................................................................7-177.1.48 pmncdXX01_agent Process................................................................................................................7-177.1.49 porttrunk_agent Process.....................................................................................................................7-177.1.50 proxy_agent Process...........................................................................................................................7-187.1.51 PRSAssistantService_agent Process..................................................................................................7-187.1.52 prsdc_agent Process...........................................................................................................................7-18



xv

7.1.53 prsfs_agent Process............................................................................................................................7-187.1.54 prsreport_agent Process......................................................................................................................7-197.1.55 prssum_agent Process........................................................................................................................ 7-197.1.56 rn_agent Process.................................................................................................................................7-197.1.57 ScriptModuleService_agent Process..................................................................................................7-197.1.58 scriptserver_agent Process................................................................................................................. 7-197.1.59 sm_agent Process............................................................................................................................... 7-207.1.60 snmp_agent Process........................................................................................................................... 7-207.1.61 son_agent Process.............................................................................................................................. 7-207.1.62 swm_agent Process............................................................................................................................ 7-207.1.63 threshold_agent Process.....................................................................................................................7-217.1.64 uap_agent Process..............................................................................................................................7-217.1.65 udpdispatch_agent Process.................................................................................................................7-217.1.66 umgupdsvr_agent Process..................................................................................................................7-217.1.67 xftpXX01_agent Process.....................................................................................................................7-217.1.68 Processes and Services Related to Each Northbound Interface.........................................................7-227.1.69 Checking the Status of the M2000 Processes.....................................................................................7-23

7.2 Managing M2000 Services............................................................................................................................7-247.2.1 Checking the M2000 Services..............................................................................................................7-247.2.2 Viewing the States of M2000 Services................................................................................................7-257.2.3 Starting the M2000 System Services................................................................................................... 7-267.2.4 Stopping the M2000 Services.............................................................................................................. 7-27

8 Managing the M2000 Databases..............................................................................................8-18.1 M2000 Database..............................................................................................................................................8-2

8.1.1 farsdb Database......................................................................................................................................8-38.1.2 fmdb Database........................................................................................................................................8-48.1.3 itfndb Database.......................................................................................................................................8-48.1.4 omcdb Database.....................................................................................................................................8-58.1.5 omceamdb Database...............................................................................................................................8-68.1.6 omclogdb Database................................................................................................................................8-78.1.7 omcsmdb Database.................................................................................................................................8-88.1.8 omctempdb Database.............................................................................................................................8-98.1.9 omctmdb Database.................................................................................................................................8-98.1.10 pmcomdb Database............................................................................................................................8-108.1.11 pmdb Database...................................................................................................................................8-128.1.12 sumdb Database..................................................................................................................................8-138.1.13 swmdb Database.................................................................................................................................8-17

8.2 Viewing the States of M2000 Databases ......................................................................................................8-178.2.1 Checking the Database Usage Information About the M2000 Server Through the M2000 Client.......................................................................................................................................................................8-188.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands................................... 8-19

8.3 Clearing M2000 Databases........................................................................................................................... 8-20

ContentsM2000


xvi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

8.4 Backing Up M2000 Databases......................................................................................................................8-22

9 Managing the M2000 Files and Disks ...................................................................................9-19.1 Managing Files and Disks on M2000 Clients.................................................................................................9-2

9.1.1 Introduction to the M2000 Client File System.......................................................................................9-29.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................9-4

9.2 Managing Files and Disks on the M2000 Server............................................................................................9-59.2.1 Introduction to the M2000 Server File System......................................................................................9-59.2.2 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client............9-139.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris Commands...........................................9-149.2.4 Clearing the Disk Space of the M2000 Server.....................................................................................9-15

10 Backing Up and Restoring the M2000................................................................................10-110.1 M2000 Backup and Restore Solutions........................................................................................................10-2

10.1.1 Backup of M2000 Dynamic Data.......................................................................................................10-210.1.2 Policies of M2000 Data Backup.........................................................................................................10-310.1.3 Scenarios of M2000 Data Restoration...............................................................................................10-4

10.2 Backing Up and Restoring M2000 Dynamic Data......................................................................................10-410.2.1 Setting the Storage Device of Backup Data Using Solaris Commands.............................................10-510.2.2 Setting the Storage Device of Backup Data Through the Client........................................................10-710.2.3 Setting the Wait Time for Replacing a Tape......................................................................................10-910.2.4 Periodically Backing Up the M2000 Dynamic Data........................................................................10-1010.2.5 Manually Backing Up the M2000 Dynamic Data............................................................................10-1410.2.6 Restoring the M2000 Dynamic Data................................................................................................10-16

11 M2000 Routine Maintenance...............................................................................................11-111.1 M2000 Routine Maintenance Items............................................................................................................11-211.2 Daily Maintenance Operations....................................................................................................................11-4

11.2.1 Checking the Status of Performance Measurement...........................................................................11-511.2.2 Checking the Missing Performance Result........................................................................................11-611.2.3 Checking the Alarm Reception..........................................................................................................11-611.2.4 Checking the NMS Connection..........................................................................................................11-711.2.5 Checking the Functionality of Alarm Box.........................................................................................11-711.2.6 Check OMC Alarms/Events...............................................................................................................11-711.2.7 Checking Connections Between the M2000 and NEs.....................................................................11-1011.2.8 Checking M2000 Logs.....................................................................................................................11-1111.2.9 Checking the Error Log of the Solaris.............................................................................................11-1111.2.10 Checking the Disk Usage of the M2000 Server.............................................................................11-1211.2.11 Checking the States of M2000 Databases......................................................................................11-1311.2.12 Checking the States of M2000 Services.........................................................................................11-1311.2.13 Checking the Core Files on the Server...........................................................................................11-1411.2.14 Checking the Hardware of the M2000 Server................................................................................11-1411.2.15 Checking the SMC Collection Results...........................................................................................11-15

11.3 Weekly Maintenance Operations..............................................................................................................11-15



xvii

11.3.1 Checking the Configuration of Alarm Timing.................................................................................11-1611.3.2 Checking the Configuration of Automatic Log Dump.....................................................................11-1711.3.3 Checking the Synchronization Time of NE Log..............................................................................11-1811.3.4 Checking the Configuration of the File Server ...............................................................................11-1811.3.5 Checking the Configuration of System Backup...............................................................................11-1911.3.6 Checking the Configuration of System Monitoring.........................................................................11-2011.3.7 Checking the Synchronization Time of NE Configuration..............................................................11-2711.3.8 Checking the Threshold of Network Management Capability.........................................................11-2811.3.9 Checking the Status of the M2000 Routes.......................................................................................11-2811.3.10 Backing Up the M2000 .................................................................................................................11-2811.3.11 Checking the Time of the M2000 Server.......................................................................................11-3111.3.12 Checking the States of M2000 Disks.............................................................................................11-31

11.4 Monthly Maintenance Operations.............................................................................................................11-3211.4.1 Checking the Power Supply of the M2000 Server...........................................................................11-3311.4.2 Checking the Peripherals of the M2000 Server...............................................................................11-3311.4.3 Checking the Front Panel of a Disk Array.......................................................................................11-3411.4.4 Querying the M2000 License...........................................................................................................11-34

12 M2000 Emergency Maintenance..........................................................................................12-112.1 Guide to Emergency Maintenance of the M2000 Server............................................................................12-212.2 Guide to Emergency Maintenance of the M2000 Client.............................................................................12-212.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-312.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You to Run fsckManually........................................................................................................................................................12-412.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System..............12-412.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact........................12-5

13 Troubleshooting the M2000.................................................................................................13-113.1 Procedure for Troubleshooting the M2000 ................................................................................................13-213.2 Collecting M2000 Site and Software Information......................................................................................13-3

13.2.1 Collecting the M2000 Site Information.............................................................................................13-313.2.2 Collecting the Time of M2000 Fault Occurrence..............................................................................13-413.2.3 Collecting the IP Address of the M2000 Server................................................................................13-413.2.4 Collecting the Solaris Version............................................................................................................13-413.2.5 Collecting Sybase Version Information.............................................................................................13-513.2.6 Collecting the M2000 Version...........................................................................................................13-6

13.3 Collecting Fault Data Using the Log Information Collector.......................................................................13-6

14 FAQs (Sun)..............................................................................................................................14-114.1 About Solaris...............................................................................................................................................14-2

14.1.1 How Do I Log In to the M2000 Server as User root Through Telnet?..............................................14-314.1.2 How to Log In the M2000 Server as the root User Through FTP.....................................................14-414.1.3 How to Check the Status of the Tape Drive.......................................................................................14-414.1.4 How Do I Select the Tape Drive?......................................................................................................14-5

ContentsM2000


xviii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

14.1.5 What are the files in the etc/rc2.d Folder of Solaris...........................................................................14-614.1.6 How to View the Hardware Settings of the M2000 Server................................................................14-714.1.7 How to Check the Device Status of the M2000 Server......................................................................14-814.1.8 Why Unable to Enter the Domain Console of Fire E4900...............................................................14-1114.1.9 How to Modify the Port Number of the FTP Server?......................................................................14-1214.1.10 How to Query the Time Zone Name..............................................................................................14-1214.1.11 How Do I Stop the NTP Service on the M2000 Server.................................................................14-1414.1.12 How Do I Change the IP Address of the S3200 Disk Array (Command Mode)...........................14-1514.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)?.........................14-1714.1.14 How Do I Change the IP Address of the 6140 Disk Array (Command Mode).............................14-1914.1.15 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROM?.................................14-2414.1.16 How to Handle the corrupt label - wrong magic number Message?..........................................14-2514.1.17 What Should I Do When the Server Disk Space Is Insufficient?...................................................14-2514.1.18 How to Configuring the Monitoring Function of the S2600 Disk Array.......................................14-2714.1.19 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays..................14-2914.1.20 How Should I Uninstall the OceanStor Monitoring Software.......................................................14-3214.1.21 How Should I Check the Running Status of the FTP Service on the M2000 Server?...................14-3314.1.22 How Should I Start the FTP Service on the M2000 Server?.........................................................14-3414.1.23 How Should I Check the Running Status of the SFTP Service on the M2000 Server?.................14-3414.1.24 How Should I Start the SFTP Service on the M2000 Server?.......................................................14-35

14.2 About Sybase.............................................................................................................................................14-3514.2.1 How Do I Check Whether the Sybase Is Started?............................................................................14-3614.2.2 How to Start the Sybase...................................................................................................................14-3714.2.3 How Do I Stop the Sybase?..............................................................................................................14-3814.2.4 How to View the Name of the Sybase Server..................................................................................14-3814.2.5 How to Handle Database Alarms.....................................................................................................14-3914.2.6 How to View Database Deadlock Information................................................................................14-4014.2.7 Why the Sybase Is Not Started After the Server Restarted..............................................................14-4114.2.8 Why the Sybase Is Not Started After Run svc_profile.sh................................................................14-4214.2.9 Why the Sybase Backup Database Abort.........................................................................................14-4314.2.10 Why the Mouse Pointer Changes into an Hourglass upon History Alarm Query..........................14-4314.2.11 What Should I Do When the Database Cannot Be Started Properly?............................................14-4414.2.12 What Should I Do When the Client Is Disconnected Due to Damaged System Tables in the Database?.....................................................................................................................................................................14-4514.2.13 What Should I Do When the Number of Database Connections Is Insufficient?..........................14-4714.2.14 How to Handle the '/export/home/sybdev/master.dat' already in use Message?......................14-4914.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-5014.3.1 Why the Network Port Is Abnormal................................................................................................14-5014.3.2 How to Connect the Client to the Server with More than One IP Address......................................14-51

14.4 About Server Software..............................................................................................................................14-5214.4.1 Why M2000 Services Restart Abnormally......................................................................................14-5314.4.2 Why M2000 Services Stop Abnormally..........................................................................................14-54



xix

14.4.3 What Should I Do When I Fail to Start the M2000 Services?.........................................................14-5414.4.4 What Should I Do When I Fail to Stop the M2000 Services?.........................................................14-5514.4.5 Why M2000 Dynamic Data Backup Fails.......................................................................................14-5614.4.6 How to Set the M2000 Administration Console as the Intermediary-Layer NTP Server (In EncryptionMode)..........................................................................................................................................................14-5814.4.7 How Do I Check the Running Status of the NTP Services on the Administration Console (In EncryptionMode)?........................................................................................................................................................14-6014.4.8 How to Set the M2000 Server as the NTP Client (In Encryption Mode)........................................14-6114.4.9 How Should I Check the Running Status of the NTP Services on the M2000 Server (In EncryptionMode)?........................................................................................................................................................14-6414.4.10 How Should I Handle an Incremental Backup Failure?.................................................................14-6514.4.11 How Should I Periodically Monitoring the CPU, Memory, and Disk...........................................14-6614.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SC.............................14-67

ContentsM2000


xx Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Figures

Figure 1-1 Netra 240 server..................................................................................................................................1-3Figure 1-2 6140 disk array...................................................................................................................................1-5Figure 1-3 V890 server.........................................................................................................................................1-5Figure 1-4 6140 disk array (I)..............................................................................................................................1-7Figure 1-5 6140 disk array (II).............................................................................................................................1-7Figure 1-6 Netra 240 server..................................................................................................................................1-9Figure 1-7 6140 disk array................................................................................................................................. 1-10Figure 1-8 E4900 server.....................................................................................................................................1-11Figure 1-9 6140 disk array (I)............................................................................................................................ 1-13Figure 1-10 6140 disk array (II).........................................................................................................................1-14Figure 1-11 T5220 server...................................................................................................................................1-15Figure 1-12 S2600 disk array.............................................................................................................................1-17Figure 1-13 S3200 disk array.............................................................................................................................1-18Figure 1-14 The front operation panel of SPARC Enterprise M4000/M5000...................................................1-19Figure 1-15 Disk array (I).................................................................................................................................. 1-21Figure 1-16 Disk array (II).................................................................................................................................1-21Figure 2-1 NTP rationale......................................................................................................................................2-4Figure 2-2 NTP layered architecture....................................................................................................................2-5Figure 2-3 Schematic diagram of time synchronization for device A..................................................................2-7Figure 2-4 Directly connecting device A and the NTP server.............................................................................2-9Figure 2-5 Networking of device A and the intermediate-layer NTP server.....................................................2-10Figure 2-6 Directly connecting device A to the highest layer NTP server........................................................ 2-11Figure 3-1 Serial ports of the S3X00..................................................................................................................3-25Figure 3-2 Serial ports provided by the S2600 disk array..................................................................................3-28Figure 3-3 Successful connection interface........................................................................................................3-29Figure 3-4 Successful login dialog box..............................................................................................................3-29Figure 3-5 Serial ports of the 6140 disk array....................................................................................................3-31Figure 6-1 Server Monitor tab page.....................................................................................................................6-5Figure 6-2 Hard Disk Monitor tab page...............................................................................................................6-6Figure 6-3 Database Monitor tab page.................................................................................................................6-7Figure 6-4 Service Monitor tab page....................................................................................................................6-8Figure 6-5 Process Monitor tab page...................................................................................................................6-9Figure 6-6 System Monitor Settings dialog box................................................................................................ 6-11

M2000Administrator Guide (Sun, S10) Figures


xxi

Figure 6-7 State transition of a scheduled task...................................................................................................6-35Figure 6-8 Timing Task Management interface.................................................................................................6-50Figure 6-9 M2000 Log Information Collector interface....................................................................................6-51Figure 7-1 Process Monitor tab page.................................................................................................................7-24Figure 7-2 Service Monitor tab page..................................................................................................................7-25Figure 8-1 Database Monitor tab page...............................................................................................................8-18Figure 8-2 Periodic backup................................................................................................................................8-23Figure 8-3 Periodic backup................................................................................................................................8-24Figure 9-1 Hard Disk Monitor tab page.............................................................................................................9-14Figure 10-1 Setting the storage device (I)..........................................................................................................10-8Figure 10-2 Setting the storage device (II).........................................................................................................10-9Figure 10-3 Periodic backup............................................................................................................................10-12Figure 10-4 Periodic backup............................................................................................................................10-13Figure 10-5 Manual backup.............................................................................................................................10-15Figure 11-1 Periodic backup............................................................................................................................11-29Figure 11-2 Periodic backup............................................................................................................................11-30Figure 13-1 Log Information Collector dialog box............................................................................................13-7Figure 14-1 SNMP tab page............................................................................................................................14-31

FiguresM2000


xxii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Tables

Table 3-1 Adding or deleting a route....................................................................................................................3-6Table 3-2 Parameters for the standby controller.................................................................................................3-18Table 3-3 Parameters for the standby controller.................................................................................................3-19Table 3-4 Setting properties of the serial port....................................................................................................3-26Table 3-5 Setting the properties of a serial port.................................................................................................3-28Table 3-6 Setting properties of the serial port....................................................................................................3-32Table 4-1 M2000 client software directory..........................................................................................................4-2Table 5-1 Solaris user accounts............................................................................................................................5-3Table 5-2 Privileges of M2000 users....................................................................................................................5-6Table 5-3 Solaris user accounts............................................................................................................................5-9Table 6-1 Server Monitor...................................................................................................................................6-12Table 6-2 Hard Disk Monitor.............................................................................................................................6-13Table 6-3 Database Monitor...............................................................................................................................6-16Table 6-4 Service Monitor..................................................................................................................................6-17Table 6-5 Tasks grouped according to execution periods..................................................................................6-25Table 6-6 Tasks grouped according to functions................................................................................................6-25Table 6-7 Tasks grouped according to task features..........................................................................................6-29Table 6-8 Description of system timing tasks....................................................................................................6-29Table 6-9 Description of user timing tasks.........................................................................................................6-32Table 6-10 Description of the task description parameters................................................................................6-34Table 6-11 Allowable operations for different task types..................................................................................6-43Table 6-12 Description of the Timing Task Management interface...................................................................6-50Table 6-13 Server Monitor.................................................................................................................................6-53Table 6-14 Hard Disk Monitor...........................................................................................................................6-54Table 6-15 Database Monitor.............................................................................................................................6-57Table 6-16 Service Monitor................................................................................................................................6-58Table 6-17 Common Parameters........................................................................................................................6-64Table 6-18 Parameters of alarm database capacity management tasks..............................................................6-65Table 6-19 Parameters of performance database capacity management tasks...................................................6-66Table 6-20 Parameters of NE log database capacity management tasks............................................................6-68Table 6-21 Parameters of M2000 log database capacity management tasks......................................................6-68Table 6-22 Parameters for Modifying an Alarm Data Export Task...................................................................6-70Table 6-23 Parameters for Modifying the Export of Performance Data............................................................6-72

M2000Administrator Guide (Sun, S10) Tables


xxiii

Table 6-24 Parameters for Modifying the Export of Inventory Data.................................................................6-74Table 6-25 Parameters for Modifying the Export of NE Logs...........................................................................6-74Table 6-26 Parameters for Modifying the Export of M2000 Logs.....................................................................6-75Table 6-27 Extension parameters of Configuration Data Export tasks..........................................................6-76Table 6-28 Parameters for Modifying the Synchronization of NE Configuration Data.....................................6-77Table 6-29 Parameters for Modifying the Synchronization of Inventory Data..................................................6-77Table 6-30 Parameters for Modifying Data Backup in the M2000....................................................................6-79Table 6-31 Parameters for Creating/Modifying/Copying NE Backup...............................................................6-79Table 6-32 Predefined Macros...........................................................................................................................6-84Table 6-33 Description of extended parameters.................................................................................................6-89Table 6-34 Descriptions of parameters for setting timing task time..................................................................6-92Table 7-1 Relations between northbound interfaces and their corresponding processes and services..............7-22Table 8-1 Tables of the farsdb database and the corresponding functions...........................................................8-3Table 8-2 Tables of the fmdb database and the corresponding functions............................................................8-4Table 8-3 Tables of the itfndb database and the corresponding functions...........................................................8-4Table 8-4 Names and functions of tables in the omcdb database.........................................................................8-5Table 8-5 Name and function of each table in the omceamdb database..............................................................8-7Table 8-6 Names and functions of the tables in the omclogdb database..............................................................8-8Table 8-7 Tables of the omcsmdb database and the corresponding functions.....................................................8-8Table 8-8 Name and function of each table in the omctempdb database.............................................................8-9Table 8-9 Names and functions of the tables in the omctmdb database...............................................................8-9Table 8-10 Counter information tables in the pmcomdb database and the corresponding functions.................8-10Table 8-11 Template information tables in the pmcomdb database and the corresponding functions..............8-11Table 8-12 Function subsets and period tables in the pmcomdb database and their functions..........................8-12Table 8-13 Template tables in the pmdb database and their functions...............................................................8-13Table 8-14 Function subset tables and period tables in the pmdb database and the corresponding functions.............................................................................................................................................................................8-13Table 8-15 Name and function of each object type information table in the sumdb database...........................8-13Table 8-16 Name and function of each system setting information table in the sumdb database......................8-14Table 8-17 Name and function of each report information table in the sumdb database...................................8-15Table 8-18 Name and function of each performance result table in the sumdb database..................................8-16Table 8-19 Tables of the swmdb database and the corresponding functions.....................................................8-17Table 9-1 M2000 client software directory..........................................................................................................9-2Table 9-2 Directories related to the M2000 server software................................................................................9-6Table 9-3 Planning of the server disk partitions (Netra 240)...............................................................................9-8Table 9-4 Planning for disk partitioning on the server (V890)............................................................................9-9Table 9-5 Planning for the 6140 disk array........................................................................................................9-10Table 9-6 Planning for disk partitioning on the server (E4900).........................................................................9-10Table 9-7 Planning for the 6140 disk array........................................................................................................9-11Table 9-8 Planning of the Sun T5220 server disk partitions..............................................................................9-11Table 9-9 Partitioning of the local server disks (M4000/M5000)......................................................................9-12Table 9-10 Disk partitions of the S3200 disk array............................................................................................9-13Table 9-11 Disk partitions of the S2600 disk array............................................................................................9-13

TablesM2000


xxiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Table 10-1 Introduction to dynamic data backup...............................................................................................10-2Table 10-2 Values of backup media...................................................................................................................10-6Table 11-1 List of maintenance items................................................................................................................11-2Table 11-2 Alarms that need to be handled immediately...................................................................................11-8Table 11-3 Alarms that need to be handled within one day...............................................................................11-8Table 11-4 Alarms to be focused on during network expansion........................................................................11-9Table 11-5 Alarms about malicious operations..................................................................................................11-9Table 11-6 Events that need to be handled within one day................................................................................11-9Table 11-7 Events that need to be focused on during network expansion.........................................................11-9Table 11-8 Server Monitor...............................................................................................................................11-21Table 11-9 Hard Disk Monitor.........................................................................................................................11-22Table 11-10 Database Monitor.........................................................................................................................11-25Table 11-11 Service Monitor............................................................................................................................11-26Table 14-1 Tape drive status..............................................................................................................................14-5Table 14-2 Checking the server configuration...................................................................................................14-7Table 14-3 Commands for checking the device status.......................................................................................14-8Table 14-4 Example of the matching table between countries and time zone names......................................14-13Table 14-5 Setting the properties of the serial port..........................................................................................14-21

M2000Administrator Guide (Sun, S10) Tables


xxv

1 Powering the M2000 On or Off

About This Chapter

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 240minicomputer 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 minicomputerserves 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 minicomputerserves 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 specificoperation 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 specificoperation sequence to guarantee the system security.

M2000Administrator Guide (Sun, S10) 1 Powering the M2000 On or Off


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 240minicomputer 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 asthe 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 servesas 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 asthe M2000 server.

PrerequisiteThe M2000 system is already shut down. For details, see1.1.2 Powering Off the M2000 (Netra240).

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. Set the power switch of the cabinet to ON.

Step 2 Power on the Netra240 server.1. Turn the rotary switch beside the power supply to the normal position (I), as shown in

Figure 1-1.

1 Powering the M2000 On or OffM2000


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 10 (2010-09-06)

Figure 1-1 Netra 240 server

1 Power switch 2 Rotary switch 3 Forced turn-off

4 Normal position 5 Lock position 6 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 stateafter the Netra240 server is powered on.

l If the Solaris operating system, Sybase, and M2000 server applications are successfullyinstalled, 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 Sybaseand 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 servesas 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



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 minicomputerserves 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 theM2000 server.

1.2.2 Powering Off the M2000 (V890)This section describes how to power off the M2000 when the V890 minicomputer serves as theM2000 server.

1.2.1 Powering On the M2000 (V890)This section describes how to power on the M2000 when the V890 minicomputer serves as theM2000 server.

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


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 inFigure 1-2.

CAUTIONEach disk array has two power switches and their directions are opposite.




Issue 10 (2010-09-06)

Figure 1-2 6140 disk array

1 Off 2 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



2. Press down the power switch to start the V890 server.



1-5

l If the Solaris operating system is not installed, the system is switched to the ok stateafter the V890 server is powered on.

l If the Solaris operating system, Sybase, and M2000 server applications are successfullyinstalled, 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 Sybaseand 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 theM2000 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


-bash-3.00$ exit

Step 3 Switch to user root and power off the V890 server.



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 cachedoes not hold data. Figure 1-4 shows the 6140 disk array.




Issue 10 (2010-09-06)

Figure 1-4 6140 disk array (I)

1 Off 2 On

2. Ensure that all the LEDs of all the disk drives at the front of controller stop blinking, asshown 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.



1-7

NOTE

Each disk array has two power switches and their directions are opposite.

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 minicomputerserves 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 theM2000 server.

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

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

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


Step 2 Start the administration console Netra 240.1. Turn the rotary switch beside the power supply to the normal position (I), as shown in

Figure 1-6.




Issue 10 (2010-09-06)

Figure 1-6 Netra 240 server



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.

l If the Solaris operating system is installed on the M2000 server, the M2000 systemautomatically starts the Solaris operating system. If the M2000 system is switched tothe ok state, enter boot to start the Solaris operating system.

3. Turn the rotary switch to the locked position.4. 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 inFigure 1-7.




1-9

Figure 1-7 6140 disk array

1 Off 2 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. Thefront indicators of the three power boards remain at steady blue.




Issue 10 (2010-09-06)

Figure 1-8 E4900 server

1 Off 2 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 theSC. Select 0 to open the Platform Shell interface. Run the following command to enablethe 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 SoftwareInitialization Installation Guide (Sun,S10).

3. To power on all boards, run the poweron all command. All the boards are powered onwhen all domains are closed.

4. On the Platform Shell interface, run the console -d a command to switch to domain A, andthen run the setkeyswitch on command to start domain A. This process lasts for about 20minutes.



1-11

l If the enter to domain A fails because the system is busy, troubleshoot the fault byreferring to 14.1.8 Why Unable to Enter the Domain Console of Fire E4900.

l If the Solaris operating system is not installed, the system is switched to the ok stateafter the E4900 server is powered on.

l If the Solaris operating system, Sybase, and M2000 server applications are installedsuccessfully, the system automatically starts these operations. If the system is switchedto the ok state, enter boot to start the operating system. The system automatically startsthe 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 theM2000 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


-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:


# /usr/sbin/shutdown -y -g0 -i52. 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 If the IP address of the SC is not assigned, use the HyperTerminal to log in from the serial portof the SC. Use the Huawei 04042025 serial port cable to connect the SC and the PC.

l One end of the Huawei 04042025 serial port cable uses the DB-25 interface, which is insertedinto the serial port of the SC. The other end uses the DB-9 interface, which is inserted into oneCOM port of the PC. The port properties of the HyperTerminal must be restored to the defaultvalues. 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 A keyswitch is: onDomain B keyswitch is: offDomain C keyswitch is: offDomain D keyswitch is: off




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 boardsincluding 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 offRP0: is already offRP2: is already offPS0: powered offPS1: powered offPS2: powered offosssvr-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 controllergo out.

If all the LEDs go out, it indicates that all the data is written into the disk and that the cachedoes not hold data. Figure 1-9 shows the 6140 disk array.

Figure 1-9 6140 disk array (I)

1 Off 2 On

2. Ensure that all the LEDs of all the disk drives at the front of controller stop blinking, asshown in Figure 1-10.



1-13

Figure 1-10 6140 disk array (II)


NOTE


Step 5 Power off the Netra 240 console.1. Log in to the Netra 240 console as user root.2. Run the following commands to power off the Netra 240 console:



Step 6 Set the power switch of the E4900 server to OFF. Set the power switches of the cabinet andother 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 specificoperation 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 whenthe M2000 is installed on the T5220 server.

1.4.2 Powering Off the M2000 (T5220)




Issue 10 (2010-09-06)

This section describes how to power off the M2000 by following a specific operation sequencewhen 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 whenthe M2000 is installed on the T5220 server.

Prerequisitel The M2000 system is powered off. For details, see 1.4.2 Powering Off the M2000

(T5220).l 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 LEDindicator 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 HowShould I Power On the T5220 Server Through the Serial Port of the SC.

Figure 1-11 T5220 server

l If the Solaris operating system is not installed, the system is switched to the ok state after theT5220 is started.

l If the Solaris, Sybase, and M2000 server software are correctly installed, the systemautomatically starts the Solaris, Sybase, and M2000 services after the T5220 is started. If thesystem is switched to the ok state, type boot to start the operating system. The systemautomatically starts the Sybase and the M2000.

----End



1-15

1.4.2 Powering Off the M2000 (T5220)This section describes how to power off the M2000 by following a specific operation sequencewhen the M2000 system is installed on the T5220 server.

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



NOTE

Shutting down the server takes a long time. Wait for 30 minutes before performing the subsequentoperations.

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 specificoperation 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/M5000server 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 specificoperation 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/M5000server when the M2000 is installed on the M4000/M5000 server.




Issue 10 (2010-09-06)

Prerequisitel The M2000 is stopped. For details, see 1.5.2 Powering Off the M2000 (M4000/M5000).

l The communication between the PC and the port 0 on the XSCF of the server is normal.

Contextl 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.l 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 M2000system.

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 Description

S2600 disk array Perform Step 2.1.

S3200 disk array or 6140 disk array 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 startedsuccessfully.

CAUTIONl Each disk array has two plugs. Ensure that both plugs are inserted into the socket.

l The S2600 disk array does not have a power switch. After you insert the plug into thesocket, the S2600 disk array is automatically powered on.

Figure 1-12 S2600 disk array



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.


Figure 1-13 S3200 disk array

1 OFF 2 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.




Issue 10 (2010-09-06)

NOTE

l The XSCF of the M4000/M5000 server functions as the system console.

l Log in to the XSCF of the M4000/M5000 server through the IP address of port 0 on the XSCF.

l Log in to the http://support.huawei.com to download the PuTTY to the PC.

l For details about how to log in to the XSCF through the PuTTY, see M2000 SoftwareInitialization Installation Guide (T5220&M4000&M5000, S10)

l If the XSCF of the M4000/M5000 server is not configured yet, configure the XSCF by referringto 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 2 LED of available XSCF 3 LED of check status

4 Power button 5 Locked 6 Maintenance

7 Mode switch - - - -

4. Run the following command to power on domain 0.

XSCF> poweron -d 0

DomainIDs to power on: 00Continue? [y|n] :y

The server automatically starts and performs self-check. This process lasts about 20minutes.

5. Run the following command to switch to area 0:

XSCF> console -d 0



1-19

When the system displays the following information, enter y to confirm the information.Connect to DomainID 0? [y|n] :yl If the Solaris operating system is not installed on the server, the server switches to the

ok state.l 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 tothe ok state, type boot to start the operating system. Then, the system automaticallystarts the Sybase and the M2000.

6. Ensure that the LED of available XSCF on the operation panel is in green.7. On the front panel of the M2000 server, switch the key to the position for Locked.

----End

1.5.2 Powering Off the M2000 (M4000/M5000)This section describes how to power off the M4000/M5000 server according to a specificoperation sequence when the M2000 system is installed on the M4000/M5000 server.

Prerequisitel You have logged in to the M2000 server as user root.l The communication between the PC and the server is normal.

Contextl 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.l 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.

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



Step 4 Power off the disk array.

Option Description

S2600 disk array Perform Step 4.1 and Step 4.2.

S3200 disk array or 6140 disk array Perform Step 4.3 and Step 4.4.




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 indicatesthat 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 bewritten to the disk.

c. Ensure that the LEDs of all the drive and caches stop blinking.

2. Remove the two plugs at the rear of the disk array from the socket.

3. 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 iswritten into the disk and that the cache does not hold data. See Figure 1-15

.

Figure 1-15 Disk array (I)

1 OFF 2 ON

b. 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)



1-21


NOTE


Step 5 If required, shut down the cabinet and other devices.

----End




Issue 10 (2010-09-06)

2 Setting the M2000 Time

About This Chapter

This chapter describes how to set the M2000 time. To enable the M2000 time to meet the timerequirements, you must synchronize the time of the M2000 with the time of the other Huaweidevices in the Huawei mobile network.

2.1 Time Management for the Huawei Mobile NetworkThis section describes the time synchronization solution of the Huawei mobile network. By usingthe time synchronization solution, you can synchronize time between the M2000 and otherHuawei mobile network devices. In addition, the M2000 supports the setting of DST and theautomatic change according to the preset DST rules.

2.2 Modifying the Date and Time on the M2000 ServerThe server time is associated with NE data collection, timing task handling, and databaseinformation dump. Therefore, you must set the server time correctly.

2.3 Changing the Time Zone of the M2000 Server Without Using DSTThis 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 displayand NTP service. You need to change the time zone of the M2000 server to ensure that the timezone meets the requirement.

2.4 Modifying the Date, Time, and Time Zone on the M2000 ClientThis section describes how to modify the date, time, and time zone on the M2000 client that isbased on the Windows operating system. Modifying the date, time, and time zone on theM2000 client means modifying the date, time, and time zone of Windows.

2.5 Configuring the NTP Service of the M2000This section describes how to set the M2000 server as the NTP client and synchronize time withthe upper-layer server and how to set the M2000 client as the NTP client and synchronize timewith the M2000 server.

2.6 Setting DST for the M2000This section describes how to set the time zone of the M2000 server to enable the M2000 supportDST. If DST change occurs on an NE, ensure that the M2000 can handle the data reported bythe NE and that no reported data is missing.

M2000Administrator Guide (Sun, S10) 2 Setting the M2000 Time


2-1

2.1 Time Management for the Huawei Mobile NetworkThis section describes the time synchronization solution of the Huawei mobile network. By usingthe time synchronization solution, you can synchronize time between the M2000 and otherHuawei mobile network devices. In addition, the M2000 supports the setting of DST and theautomatic change according to the preset DST rules.

2.1.1 Introduction to Time SynchronizationThis section describes the purpose and definition of time synchronization, the elements of thetime synchronization solution, and the impact on system performance and other OM featuresafter the time synchronization solution is implemented.

2.1.2 Introduction to the NTP/SNTPThis introduces the rationale of time synchronization and the layered architecture of the NetworkTime Protocol (NTP) and the Simple Network Time Protocol (SNTP).

2.1.3 Time Synchronization Modes of Huawei Mobile NetworkThis section describes the modes of time synchronization and how to deploy the timesynchronization network for the M2000 and NE devices in Huawei mobile network.

2.1.4 Introduction to the DSTThis section describes the daylight saving time (DST) and the DST impact on the M2000 system.

2.1.1 Introduction to Time SynchronizationThis section describes the purpose and definition of time synchronization, the elements of thetime synchronization solution, and the impact on system performance and other OM featuresafter the time synchronization solution is implemented.

Purpose of Time SynchronizationTime 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 betweenNEs. This ensures that the M2000 correctly manages the alarms and performance data reportedby 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 alarmgeneration and alarm reporting, and the associations between alarms may be misjudged.

l When the M2000 collects the statistics of performance data, the statistics are incorrectowing to inaccurate time.

Therefore, time synchronization enables the system to automatically adjust the OM time of NEs.

Definition of Time SynchronizationTime synchronization is the synchronization of absolute time. The start time of a signal shouldbe consistent with the universal coordinated time (UTC).

Time synchronization aims to adjust the time of devices according to the received time.

2 Setting the M2000 TimeM2000



Issue 10 (2010-09-06)

Elements of the Time Synchronization Solution

At least two elements are involved in the time synchronization solution, namely, the method oftime synchronization and the choice of time reference sources.

l In the architecture of the current time synchronization networking, the common method isto implement time synchronization according to the Network Time Protocol (NTP) and theSimple Network Time Protocol (SNTP).

l Time reference sources aim to provide the standard reference time for the timesynchronization network. This ensures the accuracy of the time reference in the entirenetwork. 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, themessage frame between the NTP client and the NTP server is 128 bytes. Therefore, timesynchronization does not affect the performance of network transmission. If a great number ofNTP clients request to connect to the NTP server at the same time, these connections consumemass resources, such as the CPU and the memory of the NTP server. As a result, the performanceof the NTP server is affected.

Therefore, if you use the NTP protocol to construct a time synchronization network, the numberof NTP nodes under an NTP server should not exceed 300. If the number exceeds 300, theperformance of the NTP server may be affected. The interval for the time synchronization requestof an NTP client should be 30 minutes or longer. In addition, you need to reduce the probabilityof concurrent requests.

Impact on OM

The time synchronization feature is vital for the OM of the mobile network. It has the followingimpacts on the other features:

l Ensures the accuracy and consistency of the time on the M2000 and NEs in a mobilenetwork. Time synchronization plays a key role in timely fault reporting, informationaccuracy, and fault correlation analysis in fault management. If the NE time is inaccurateor inconsistent with the M2000 time, a mistake may be made during the fault identificationand handling.

l 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 logrecord is incorrect and the log audit is also affected.

l Has a significant impact on recording, collecting, and analyzing performance data inperformance management. If the time is inaccurate or the time of NEs in the entire networkis 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.

l Has a significant impact on services such as call tracing and problem locating. If the timeis inaccurate or the time of NEs in the entire network is not the same, the call tracing servicemay fail.

2.1.2 Introduction to the NTP/SNTPThis introduces the rationale of time synchronization and the layered architecture of the NetworkTime Protocol (NTP) and the Simple Network Time Protocol (SNTP).



2-3

Rationale of NTP Time SynchronizationNTP is used to synchronize the time between the distributed time server and the client. It definesthe structure, algorithm, entity, and protocols in the process of time synchronization. Based onthe IP and UDP stack protocol in the TCP/IP protocols, NTP can also be used by other protocolgroups. 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 systemtime. 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.l Device B is configured as the NTP server. That is, you need synchronize the time on device

A with that on device B.l 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 informationis available:l Offset, which is the time difference between device A and device B

l 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 tosynchronize with device B. The NTP protocol stipulates the method for calculating the valuesof the offset and delay between device A and device B.

The time synchronization process is as follows:

1. Device A sends an NTP message to device B. The message records the stamp of the leavingtime from device A, which is 10:00:00am (T1).

2. When the NTP message reaches device B, device B adds its own time stamp, which is11:00:01am (T2).




Issue 10 (2010-09-06)

3. When the NTP message leaves device B, device B adds its own time stamp again, whichis 11:00:02am (T3).

4. When device A receives the response message, it adds a new time stamp, which is10:00:03am (T4).

After that, device A can calculate the two parameters using the following method:

l Delay of a NTP message delivering circle: delay = (T4 - T1) - (T3 - T2).

l 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 issynchronized with device B.

Rationale of NTP Layered Architecture

From the origin and purpose of the time synchronization mechanism, you can infer that fewerclock sources enables more uniform time. If a network has a large scale and is very complex, itis time-consuming to connect each device to the same time server if the time of each deviceneeds 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, ormore than 16 levels on the basis of accuracy and importance. In practice, the number of levelsdoes not exceed six.

The device at level 0 is located at the special position of the subnetwork. It provides the referenceclock for time synchronization. On the top of the subnet, the device at level 0 uses UTC timecodes broadcast by the global positioning system (GPS).

The devices in the subnet can play multiple roles. For example, a device on the second layermay 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 forlower level servers (Stratum-1).



2-5

l Medium level NTP server: level 1 and level 2 servers, which acquires time from the upperlevel server and provides the time for the lower level servers.

l 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 formultiple hosts. Hosts on the same level can exchange time. The NTP protocol supports amaximum of 15 clients.

NOTE

Port 123 is used by NTP during communication through the User Datagram Protocol (UDP). Ensure thatall the IP links between the nodes are functional.

Comparison of SNTP and NTPSNTP is a simplified policy for the NTP server and the NTP client. The difference betweenSNTP and NTP is that SNTP has disadvantages in the following aspects:

l Handling errors

l Filtering of multiple servers

l Choosing among multiple clock sources, that is, acquiring the most accurate clock resourceafter using an algorithm to analyze multiple connected NTP servers.

2.1.3 Time Synchronization Modes of Huawei Mobile NetworkThis section describes the modes of time synchronization and how to deploy the timesynchronization network for the M2000 and NE devices in Huawei mobile network.

Time Synchronization Modes of the M2000The 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 protocolversions. 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 forthe NTP server that the M2000 server gains access to, the M2000 server can obtain the timesynchronization information from the specified NTP server. In addition, you can configure theM2000 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 addressof the NTP server. Then, the M2000 client can obtain the time synchronization information fromthe specified NTP server.

NOTE

The upper-level time servers of the M2000 server and the administration console require to use the NTPprotocol. The server running the Windows operating system uses the SNTP protocol, and thus it cannotfunction as the upper-level time server of the M2000 server and the administration console.

Time Synchronization Modes of NEsl 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 withthe NTP server.




Issue 10 (2010-09-06)

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 NEnode and each module of device A, as shown in Figure 2-3. After the active BAM of deviceA obtains the reference time from the specified NTP server, the BAM delivers the time toeach 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 BAMprogram of device A, an NTP client process automatically starts after the BAM programand always runs on the active BAM server.

By running MML commands, you can specify the upper-layer NTP server as the activeBAM server of device A. Then, the NTP client process running on the active BAMautomatically 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 activeBAM of device A can perform the synchronization from the preferred time source. If anNTP time source does not work properly, the active BAM can use a new NTP time sourceto ensure the continuity of the NTP service.



2-7

When the BAM of device A experiences active and standby switching, the NTP clientprocess is automatically switched to the new active BAM to ensure the continuity of theNTP service.

l Time synchronization for each internal module of device AIn addition to running the NTP client to synchronize with the external time sources, theactive BAM of device A has an SNTP server module for time synchronization between theinternal 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 theactive BAM of device A.

l Time synchronization for the standby BAM of device AIf 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 timewith the active BAM. That is, when the active and standby BAMs are operational, the timeof the active BAM is regarded as the reference time.During the time synchronization of the active and standby BAMs, the SNTP client of thestandby BAM requests for time synchronization, the SNTP server of the active BAMreturns a response message. Then, the standby BAM adjusts the time of the applicationsand 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 asa single entity to provide services.

l Time synchronization between device B and the BAM of device AThe SNTP server of the active BAM provides both the time synchronization service andthe time comparison service for the host. The SNTP server of the active BAM periodicallybroadcasts time synchronization messages to device B and receives the requests for timesynchronization from device B.Device B runs an SNTP process and sends requests for time synchronization to the activeBAM of device A.

Network of NTP Time SynchronizationThe NTP time synchronization network determines the reference time for the network and usesthe 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 NTPtime synchronization network.

l Using the NTP server specified by the carrierIf the established time synchronization network provides the NTP server that can act as thereference time source, prefer to use the existing NTP server as the time reference sourceof the RAN network.In this case, the M2000 and the BAM server of device A need to directly communicatewith the specified NTP server to obtain standard time signals, as shown in Figure 2-4.




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 timesynchronization server. The NTP server that can serve as the reference time may bedeployed in other subnets. Therefore, the communication between the M2000 and deviceA may involve the policy of traversing the firewall. In such a case, you need to modify theconfiguration of the firewall.

l Deploying the intermediate-layer NTP serverAccording to the principle of layered NTP, when constructing an RAN network, you candeploy a dedicated intermediate-layer NTP server in the RAN-OM network to serve as thetime reference for the internal RAN devices. The intermediate-layer NTP server obtainsthe reference time from the upper-layer server, synchronizes its own time, and serves asthe NTP server of the RAN network. In such a case, the intermediate-layer NTP server canreceive the request on time synchronization from the internal NE devices in the RAN, suchas device A and the M2000, and provides standard time, as shown in Figure 2-5.



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 thetime synchronization network. It can also prevent too many NEs from directly connectingthe highest layer NTP server, thus reducing the risks to the highest layer NTP server. Inaddition, 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 ofdevice A network. Complying with the NTP V3 protocols, this device can provide twochannels of NTP service units and lock multiple upper-layer NTP servers to realize NTPpriority. The intermediate-layer NTP server provides two channels of NTP service outputthat are mutually backed up.




Issue 10 (2010-09-06)

NOTE

l The M2000 server uses the Solaris operating system where you can configure the M2000 serveras the intermediate-layer NTP server. With regard to that the time synchronization server for theRAN 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 serverfor the RAN network.

l When a system using the V890 or E4900 server, the Netra 240 server is integrated as anadministration console by default. In this case, the Netra 240 acts as the intermediate-layer NTPserver for the RAN network.

l Obtaining reference time from the GPSIf the upper-layer time synchronization server that can provide the reference time is notavailable, you should deploy the highest layer NTP server, that is, the NTP server providingthe reference time in the RAN-OM network to ensure time synchronization. The highestlayer NTP server obtains the reference time from the GPS or other satellite systems andsynchronizes time on all the RAN NEs and the M2000. Figure 2-6 shows the networkingof device A and the highest layer NTP server.

Figure 2-6 Directly connecting device A to the highest layer NTP server



2-11

You can use the dedicated BITS SYNCLOCK V5 as the highest layer NTP server of deviceA. Complying with the NTP V3 protocol, this device can provide two channels of thesatellite access system and two channels of NTP service units. It also provides two channelsof 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 twochannels of the NTP service are available.

l If the stratum 1 NTP server is deployed, it obtains reference time directly from the GPS satellite. Insuch a case, the stratum 1 NTP server should provide two channels of satellite interfaces.

2.1.4 Introduction to the DSTThis section describes the daylight saving time (DST) and the DST impact on the M2000 system.

IntroductionThe DST is one hour earlier than the standard time. For example, during the DST, 10:00 am inUS east standard time is 11:00 am in US east DST.

Impact on the M2000 Systeml 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. TheM2000 log management and trace management uses the local time. Therefore, one-hourrecords are missing in trace files.

l When the DST ends, generally one hour is automatically reduced from the local time ofthe operating system. This change does not affect the system clock. Thus, time storage andexchange are not affected. This change, however, affects the time display. During theoperation of the M2000, some modules in the M2000 generate some files whose names areidentified by time stamps. When the DST ends, files that are generated later overwrite theearlier ones.

NOTE

l The local time is the time displayed on the computer. It varies according to the time zone.

l The system clock indicates the GMT. The NTP synchronization uses the GMT, which does not affectthe local time. The DST does not affect the NTP service.

2.2 Modifying the Date and Time on the M2000 ServerThe server time is associated with NE data collection, timing task handling, and databaseinformation dump. Therefore, you must set the server time correctly.


ContextIf the M2000 server acts as the NTP server of network equipment, the network equipment timeis updated when you modify the M2000 server time.




Issue 10 (2010-09-06)

CAUTIONl 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 thefunction failures resulting from invalid timers, stop the M2000 and the Sybase first. Duringthis process, the performance data and alarm data of managed NEs are not processed inreal time. After the Sybase and M2000 services are restarted, the M2000 collects theperformance data and alarm data through automatic synchronization and then processesthe data. Therefore, the data is not lost.

l 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 mm indicates a month.

l dd indicates a day.

l HH indicates an hour.

l MM indicates a minute.

l YYYY indicates a year.

l 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.43Mon 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



2-13

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 WithoutUsing 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 displayand NTP service. You need to change the time zone of the M2000 server to ensure that the timezone meets the requirement.


Contextl 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 timezones.

l The GMT format can be used by the countries and regions that do not use DST. The timezone code format must be used by the countries and regions that use DST. Otherwise, theoperating system does not support the automatic DST change.

l 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 andSybase services before you change the server time zone. During this period, theperformance data and alarm data of the managed NEs cannot be handled in time. After theM2000 and Sybase services are restored, the M2000 starts the automatic synchronizationfunction, and collects and handles the missing performance data and alarm data from themanaged NEs.

l If you need to change both the time and the time zone, change the time zone first.

l If the M2000 does not use DST, you need to change the time zone of the server byperforming the following operations. Otherwise, you need to change the time zone of theserver by referring to 2.6 Setting DST for the M2000.

l Coordinated Universal Time, which is referred to as Greenwich Mean Time (GMT), istaken as a reference. The time zone of the region to the east of the GMT region is representedby GMT+N. That is, the time of the region is N hours earlier than the GMT. The time zoneof the region to the west of the GMT region is represented by GMT-N. That is, the time ofthe region is N hours later than the GMT. For example, GMT+08:00 is eight hours earlierthan the GMT and GMT-08:00 is eight hours later than the GMT. When you modify thetime zone configuration file /etc/TIMEZONE of the Solaris, GMT+N refers to the timezone that is N hours later than the GMT and GMT-N refers to the time zone that is N hoursearlier than the GMT.




Issue 10 (2010-09-06)

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 nameof the required local time zone:

# TERM=vt100; export TERM

# vi /etc/TIMEZONE

For example, set TZ to GMT+8.

NOTE

l In this case, GMT+N indicates that the local time is N hours later than the GMT. GMT-N indicatesthat the local time is N hours earlier than the GMT. Before the change, ensure that the binary time zonefile corresponding to the GMT time zone exists in the /usr/share/lib/zoneinfo directory. Otherwise,the change fails.

l The /etc/TIMEZONE file is read-only. Save the file after modification.

Step 4 Restart the server.


# /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 theM2000 Client

This section describes how to modify the date, time, and time zone on the M2000 client that isbased on the Windows operating system. Modifying the date, time, and time zone on theM2000 client means modifying the date, time, and time zone of Windows.

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



2-15

Step 3 In the Date and Time Properties dialog box, select the items to be modified.

Item Operation

Hour Set the required hour on the Time tab page.

Minute Set the required minute on the Time tab page.

Second 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 zonefrom the drop-down list.

Step 4 Click Apply.

----End

2.5 Configuring the NTP Service of the M2000This section describes how to set the M2000 server as the NTP client and synchronize time withthe upper-layer server and how to set the M2000 client as the NTP client and synchronize timewith the M2000 server.

2.5.1 Checking the Time Settings of the M2000 ServerThis section describes how to check the time settings of the M2000 server. Before configuringthe NTP service, you need to ensure that the time zone, date, and time are set correctly on theM2000 server.

2.5.2 Setting the M2000 Administration Console as the Secondary NTP ServerThis 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 standardtime source for a lower-level server.In the single-server system, the administration console isconfigured only for the E4900 server.

2.5.3 Starting the NTP Service on the M2000 Administration ConsoleThis section describes how to start the NTP service on the M2000 administration console tosynchronize the system.

2.5.4 Checking the Running Status of the NTP Service on the M2000 Administration ConsoleThis section describes how to check the operational status of the NTP service.

2.5.5 Setting the M2000 Server as the NTP ClientThis section describes how to configure the NTP service to set the M2000 server as the NTPclient, which is synchronized with the upper level server.

2.5.6 Starting the NTP Service on the M2000 ServerThis section describes how to start the NTP service on the M2000 server to synchronize thesystem.

2.5.7 Checking the Running Status of the NTP Service on the M2000 ServerThis section describes how to check the operational status of the NTP service.

2.5.8 Setting the NTP Service on the M2000 Client




Issue 10 (2010-09-06)

This section describes how to set the M2000 client as the NTP client. This task enables you tosynchronize the client with the NTP server through the NTP service of the Windows operatingsystem.

2.5.1 Checking the Time Settings of the M2000 ServerThis section describes how to check the time settings of the M2000 server. Before configuringthe NTP service, you need to ensure that the time zone, date, and time are set correctly on theM2000 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 byreferring 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 twominutes, change the date and time by referring to 2.2 Modifying the Date and Time on theM2000 Server.

----End

2.5.2 Setting the M2000 Administration Console as the SecondaryNTP 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 standardtime source for a lower-level server.In the single-server system, the administration console isconfigured only for the E4900 server.

Prerequisitel The top layer NTP server has been configured in the mobile network.

l The time zone, date, and time of the administration console are set correctly.

l You have logged in to the administration console as user root.

ContextNormally, 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 administrationconsole 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 NTPprotocol. The server running the Windows operating system uses the SNTP protocol, and thusit cannot function as the the upper-level time server of the M2000 administration console.



2-17

Procedure

Step 1 Open the file ntp.conf.

# cp /etc/inet/ntp.server /etc/inet/ntp.conf


# vi /etc/inet/ntp.conf

Step 2 In front of server 127.127.XType.0, add server IP address of the upper-level NTPserver 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 preferserver IP address of the upper-level NTP server

Step 3 Change XType in server 127.127.XType.0 and fudge 127.127.Xtype.0stratum 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 prohibitthe 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 thefollowing contents in the file ntp.conf:server 127.127.XType.0fudge 127.127.XType.0 stratum 0

broadcast 224.0.1.1 ttl 4with:server 10.161.94.212 preferserver 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 startthe NTP service on the administration console. For details, see 2.5.3 Starting the NTP Serviceon the M2000 Administration Console.




Issue 10 (2010-09-06)

2.5.3 Starting the NTP Service on the M2000 AdministrationConsole

This section describes how to start the NTP service on the M2000 administration console tosynchronize the system.

Prerequisitel The time zone, date, and time of the administration console are correctly set.

l You have logged in to the administration console as user root.

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

l In the system output, if STATE is online or maintenance, run the following commandto 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 theM2000 Administration Console

This section describes how to check the operational status of the NTP service.

ContextAfter the NTP server and the NTP client are started, the system requires five minutes for thesystem test. Wait for five minutes, and then run the commands ntpq -p and ntptrace to viewthe status of the NTP service.

During the system test, if you run the ntpq -p command, the displayed address of theremote clock source does not contain *. If you run the ntptrace command during the systemtest, the system displays Timeout or Not Synchronized.

ProcedureStep 1 View the information about the time source.

# ntpq -p



2-19

In the result of the command ntpq -p, the remote field shows the address and status of thereference 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 # ntptracelocalhost: stratum 2, offset 0.000039, synch distance 0.0764010.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 theNTP server that the host is synchronized with is 10.161.94.212. The value 1 in the column stindicates that the host is located at stratum 1. The symbol * indicates that the NTP is runningproperly.

The result of the command ntptrace shows that the host is located at stratum 2, that the IP addressof 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 ClientThis section describes how to configure the NTP service to set the M2000 server as the NTPclient, which is synchronized with the upper level server.

Prerequisitel The time zone, date, and time of the server are correctly set.

l 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 serverrunning the Windows operating system uses the SNTP protocol, and thus it cannot function asthe 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.




Issue 10 (2010-09-06)

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


# 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 IPaddresses 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

ExampleIf the server with the IP address of 10.161.94.214 is the upper-layer NTP server of the M2000server, replace the following contents of the ntp.conf file:multicastclient 224.0.1.1with:server 10.161.94.214#multicastclient 224.0.1.1

PostrequisiteAfter setting the M2000 server as the Network Time Protocol (NTP) client, you need to start theNTP service on the server. For details, see 2.5.6 Starting the NTP Service on the M2000Server.

2.5.6 Starting the NTP Service on the M2000 ServerThis section describes how to start the NTP service on the M2000 server to synchronize thesystem.



2-21

Prerequisitel The time zone, date, and time of the server are correctly set.


Procedure

Step 1 Check whether any NTP service is running.


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.

l In the system output, if STATE is online or maintenance, run the following commandto 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

PostrequisiteIf the administration console is configured as the medium-level NTP server, you must start theNTP service on the administration console at the same time.

2.5.7 Checking the Running Status of the NTP Service on theM2000 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 thesystem test. Wait for five minutes, and then run the commands ntpq -p and ntptrace to viewthe status of the NTP service.

During the system test, if you run the ntpq -p command, the displayed address of theremote clock source does not contain *. If you run the ntptrace command during the systemtest, the system displays Timeout or Not Synchronized.

Procedure

Step 1 View the information about the time source.

# ntpq -p




Issue 10 (2010-09-06)

In the result of the command ntpq -p, the remote field shows the address and status of thereference 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.05root@osssvr #root@osssvr # ntptracelocalhost: stratum 3, offset 0.000035, synch distance 0.0885510.161.94.214: stratum 2, offset 0.000224, synch distance 0.0786010.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 theNTP server that the host is synchronized with is 10.161.94.214. The value 2 in the column stindicates that the host is located at level 2. The symbol * indicates that the NTP is runningproperly.

The result of the command ntptrace indicates that the host is located at level 3, that the IP addressof the stratum-2 server is 10.161.94.214, and that the IP address of the stratum-1 server is10.161.94.212.

2.5.8 Setting the NTP Service on the M2000 ClientThis section describes how to set the M2000 client as the NTP client. This task enables you tosynchronize the client with the NTP server through the NTP service of the Windows operatingsystem.

Prerequisitel You have logged in to the Windows operating system. The Windows operating system is

running properly.l The M2000 client and the M2000 server communicate normally.

l The clock source of the server is operational.

Context

When the M2000 client is configured as the NTP client, synchronize the time of the M2000client 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.



2-23

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 RegistryEditor window.

In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet >Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to0, which is the default value. If the parameter LocalNTP does not exist, it indicates that thevalue 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 ofEnable 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 takeseffect 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 theServices 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 serverby /setsntp, the NTP server time is the local time of the PC.

Step 5 Perform operations based on operating systems.l If the M2000 client runs on Windows 2000 operating system, perform Step 6.

l If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vistaoperating 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 localtime 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




Issue 10 (2010-09-06)


c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly

The system displays the following information, including the local time of the client anddeviation 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.9881239s10:05:11, +04.9814570s10:05:13, +04.9740897s10:05:15, +04.9589559s10:05:17, +04.9449507s...

In the system output, the first column displays the local time of the client, and the second columndisplays the deviation between the local time and the server time. + indicates that the client timeis earlier than the server time. - indicates that the client time is later than the server time. Youcan press Ctrl+C to exit the browse window.

----End

2.6 Setting DST for the M2000This section describes how to set the time zone of the M2000 server to enable the M2000 supportDST. If DST change occurs on an NE, ensure that the M2000 can handle the data reported bythe NE and that no reported data is missing.


Contextl 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 timezones.

l The GMT format can be used by the countries and regions that do not use DST. The timezone code format must be used by the countries and regions that use DST. Otherwise, theoperating system does not support the automatic DST change.

l 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 thetime zone code before setting DST. This ensures that the DST rule defined by the time zonecode is consistent with the actual DST rule.

l When the DST rule of a time zone are adjusted, the Sun may release the code patch of thistime zone. You can install the code patch to obtain the latest time zone code and DST rule.

l 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. Toavoid the function failure caused by invalid timers, you need to stop the M2000 and Sybaseservices before you set the M2000 DST. During this period, the performance data and alarmdata of the managed NEs cannot be handled in time. After the M2000 and Sybase servicesare restored, the M2000 starts the automatic synchronization function, and collects andhandles the missing performance data and alarm data from the managed NEs.



2-25

l If you need to set DST and change time, set DST first.

ProcedureStep 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 theTime 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 DSTperiod.

l If specified year does not refer to the current year:– 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– The UTC time is the GMT.

– isdst=0 stands for being not in the DST period. isdst=1 stands for being in the DSTperiod.

NOTE

l If you do not add | grep specified year to the previous command, the system displays the DST rulesof the time zone in all years.

l The DST rule of a time zone stipulates the day, week, and month when DST starts and ends in eachyear. 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 onthe first Sunday of November in each year.

l You can run the zdump command to query the DST rules in the three successive years, that is, the lastyear, this year, and the next year. Based on the system output, you can infer the universal change rulesof DST.

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




Issue 10 (2010-09-06)

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 nameof the required local time zone:


# vi /etc/TIMEZONE

For example, set TZ to PRC.

NOTE

l Query the required time zone in the /usr/share/lib/zoneinfo/src directory. Ensure that the relevantbinary time zone file exists in the /usr/share/lib/zoneinfo directory. For example, if you find the localtime zone name PRC in the asia file in the /usr/share/lib/zoneinfo/src directory, you need to checkwhether the binary time zone file /usr/share/lib/zoneinfo/PRC exists.

l The /etc/TIMEZONE file is read-only. Save the file after modification.

Step 7 Restart the server.



The Sybase and M2000 services automatically start after the operating system is restarted.

----End

ExampleThe 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 Mon Sep 17 06:09:56 2007 UTC = Sun Sep 16 22:09:56 2007 AKDT isdst=1US/Alaska Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST isdst=0US/Alaska Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT isdst=1US/Alaska Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT isdst=1US/Alaska Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 AKST isdst=0



2-27

– Based on isdst=1 contained in the information in the first row, you can infer thatDST is used in US/Alaska. The local time, that is, the DST time, is Sep 1622: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 thatDST starts after Mar 11 02:00:00 2007 changes to Mar 11 03:00:002007.

– Based on the information in the fourth row and the fifth row, you can infer that DSTends 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 Sun Mar 11 10:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 AKST isdst=0US/Alaska Sun Mar 11 11:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 AKDT isdst=1US/Alaska Sun Nov 4 09:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 AKDT isdst=1US/Alaska Sun Nov 4 10:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 AKST isdst=0– 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:002007.

– Based on the information in the third row and the fourth row, you can infer that DSTends after Nov 4 02:00:00 2007 changes to Nov 4 01:00:00.




Issue 10 (2010-09-06)

3 Setting the Host Name and IP Address forthe M2000 Server

About This Chapter

This chapter describes how to set the host name and the IP address of the M2000 server, accordingto field requirements.

3.1 Changing the Host Name of the M2000 ServerThis section describes how to change the host name of the M2000. During the modification ofthe host name, the M2000 cannot handle the performance data and alarm data of the managedNEs. After the modification, the M2000 implements automatic synchronization to collect andhandle the missing performance data and alarm data.

3.2 Modifying the IP Address of the M2000 ServerThis section describes how to modify the IP address of the M2000 server in common mode andmaintenance 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 ServerThis 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 ArrayThis section describes how to modify the IP address of the disk array. By modifying the IPaddress of the disk array, you can maintain the disk array easily.

M2000Administrator Guide (Sun, S10) 3 Setting the Host Name and IP Address for the M2000 Server


3-1

3.1 Changing the Host Name of the M2000 ServerThis section describes how to change the host name of the M2000. During the modification ofthe host name, the M2000 cannot handle the performance data and alarm data of the managedNEs. After the modification, the M2000 implements automatic synchronization to collect andhandle the missing performance data and alarm data.

Context

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

l The network adapter type varies with the model of the server. The network adapter of theNetra 240 is bge, the network adapter of the V890 or E4900 is ce, the type of the networkadapters used by the T5220 servers is e1000g. When the M4000/M5000 server is used, runthe following command:# ifconfig -a | grep e1000gIf there is any system output, it indicates that the M4000/M5000 server uses the nxge0 ande1000g0 Ethernet ports. The function of port nxge0 is similar to that of port bge0 of the Netra240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of porte1000g0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, andport e1000g2 of the T5220.If there is no system output, it indicates that the M4000/M5000 server uses the bge0 andnxge0 Ethernet ports. The function of port bge0 is similar to that of port bge0 of the Netra240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of portnxge0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, andport e1000g2 of the T5220.

l If the file to be modified is read-only, run the wq! command to save the file forcibly afterthe modification.

l The following procedure takes the ce as an example. Change the network adapter typeaccording to actual situations.

Procedure

Step 1 Log in to the system controller (SC), remote system controller (RSC) or eXtended SystemController 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 If the host name is incorrect, proceed with the next step.

l If the host name is correct, do not proceed with the next step.

3 Setting the Host Name and IP Address for the M2000 ServerM2000



Issue 10 (2010-09-06)

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

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


# 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 modifythe corresponding file.

Maintenance dual plane is configured? Step

Yes Edit the files /etc/hostname.ce0 and /etc/hostname.ce2 to change the existing hostnames to new ones.

# vi /etc/hostname.ce0


No Modify only the /etc/hostname.ce0 file.


NOTE

l If the /etc/hostname.ce0 and /etc/hostname.ce2 files record IP addresses, you need not modify thetwo files.

l In the files /etc/hostname.ce0 and /etc/hostname.ce2, no space is allowed at the beginning of eachline of content.

l For the /etc/hostname.ce0 and /etc/hostname.ce2 files, ce in the file names refers to the networkadapter type. Thus, the names of the two files vary with the network adapter type. For example, whenthe 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, seethe 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.



3-3

# ls -al /etc/inet/ipnodes

l If the command result contains /etc/inet/ipnodes -> ./hosts, it indicatesthat the two files are correlated. Then, go to Step 8.2.

l If the command result does not contain /etc/inet/ipnodes -> ./hosts, itindicates 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 thatthe /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.

l If the command result does not contain /etc/hosts -> ./inet/hosts, itindicates 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 hostname 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 newhost name. Then, press Esc and run the :wq command to save the modification and exit.

l If the file does not record host names, do not modify the file. Press Esc and run the :qcommand 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.

CAUTIONIf the Sybase and M2000 services are exceptional after the server is restarted, contact Huaweitechnical support engineers for assistance.

1. Run the following command to restart the server.






Issue 10 (2010-09-06)

After the server is restarted, both of the Sybase and M2000 services are automaticallyrestarted.

2. Log in to the server as user root.3. 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 CheckWhether 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 ServerThis section describes how to modify the IP address of the M2000 server in common mode andmaintenance dual-plane mode. In common mode, the maintenance dual-plan is not configured.

ContextIf you set the function of dumping the alarms on the disk array to M2000 server logs, you mustmodify the IP address of the M2000 server in the array configuration file.

3.2.1 Adding or Deleting Routes on the M2000 ServerThis section describes how to add or delete routes from the current network to several destinationnetworks.

3.2.2 Changing the IP Address of the M2000 ServerThis section describes how to change the IP address of the M2000 server based on the actualrequirements.

3.2.1 Adding or Deleting Routes on the M2000 ServerThis section describes how to add or delete routes from the current network to several destinationnetworks.




3-5

Context

CAUTIONRun the following command to add a route. After you restart the server, the added route isautomatically 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 Table3-1.

Table 3-1 Adding or deleting a route

Operations

Command Example

Adding aroute

# route add Destination address/maskgatewayl Destination address: a network

address or a PC addressl Mask: The number of digit 1 in the

subnet mask is binary. For example, 24means 255.255.255.0.

# route add 129.8.0.0/2410.12.8.1

Deleting aroute

# route delete Destination address/mask gateway

# route delete 129.8.0.0/2410.12.8.1

Viewing aroute

# netstat -rv -

Adding arouteautomatically onsystemrestart

Create the /etc/rc2.d/S97route file.

# vi /etc/rc2.d/S97route

Write one or more route add Destinationaddress/mask gateway commands intothe file.

route add 129.9.0.1/24 10.12.8.1route add 129.8.0.0/16 10.12.8.1

----End

3.2.2 Changing the IP Address of the M2000 ServerThis section describes how to change the IP address of the M2000 server based on the actualrequirements.




Issue 10 (2010-09-06)

Contextl 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 isout of service, the system switches the IP address from the previous active port to the currentactive port. This ensures continuity in the communication between the server and theexternal 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 maskto the IP address and subnet mask of the restored port.

l The M2000 client, NEs, and network management system (NMS) set up communicationwith the M2000 server through the IP address of the server. Thus, functions such as datatransfer, operation, and maintenance are implemented. Allocate physical IP addresses tothe Ethernet ports of the server and configure the maintenance dual plane to implement theredundancy backup of Ethernet ports. In this case, the communication between the serverand external devices is secure and reliable.

l 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 serverto meet the requirements for network reparenting and adjustment. In this case, the OMnetwork is easily managed and maintained and is more open and flexible. In addition, thescalability and evolution of the network are improved.

l During the change of the server IP address, the performance data and alarm data of themanaged NEs cannot be processed. If the IP address of the M2000 server are recorded inthe NE database, changing the IP address of the M2000 server leads to the disconnectionbetween 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 plansand update the IP address of the M2000 server recorded in the NE database. After youchange the IP address of the server, the M2000 collects performance data and alarm dataagain through automatic synchronization and then processes the data.

l The IP addresses are stored in the relevant configuration files of the operating system, thedatabase, and the M2000. You can run the modify.sh script to modify the IP addressinformation in these configuration files and change the IP address of the server.

l The M2000 supports both LAN and WAN networking modes. For details, see the M2000Commissioning Guide (Sun, S10).



3-7

CAUTIONl 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 networkadapters used by the T5220 servers is e1000g. When the M4000/M5000 server is used, runthe following command:

# ifconfig -a | grep e1000g

If there is any system output, you can infer that the M4000/M5000 server uses the nxge0 ande1000g0 Ethernet ports. The function of port nxge0 is similar to that of port bge0 of the Netra240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of porte1000g0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, andport e1000g2 of the T5220.

If there is no system output, you can infer that the M4000/M5000 server uses the bge0 andnxge0 Ethernet ports. The function of port bge0 is similar to that of port bge0 of the Netra240, port ce0 of the V890 or E4900, and port e1000g0 of the T5220; the function of portnxge0 is similar to that of port bge2 of the Netra 240, port ce2 of the V890 or E4900, andport e1000g2 of the T5220.

l For example, the model of the server is V890. If the maintenance dual plane is configuredon the system, the ce0 and ce2 network ports on the server are used to configure themaintenance 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 V890except the network adapter type. The network adapter type varies with the model of the server.For their relation, see the previous information.

l If the maintenance dual plane is configured on the system, the server IP address and thephysical IP addresses of network ports must be set in the same network segment. If youchange the IP addresses on different network segments, you need to plan and change theM2000 server IP address, and the physical IP addresses of network ports at the same time.

l In this case, run the modify.sh script to change the IP address of the M2000 server, modifythe IP address information in routing devices, and then restart the M2000 server.

l This assumes that the system is configured with the maintenance dual plane and describeshow to change the IP address of the server and the physical IP addresses of two Ethernetports. If you need to change only some IP addresses of the system, perform operations tochange only these IP addresses in the relevant steps. If the system is not configured with themaintenance dual plane, perform operations to change only the IP address of the server inthe relevant steps.

l The following procedure takes the ce as an example. Change the network adapter typeaccording 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.




Issue 10 (2010-09-06)

Step 3 View the /etc/hosts file to obtain the host name of the server and the IP addresses correspondingto 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 osssvr-1 loghost omc.com192.168.8.18 osssvr-1-ce0192.168.8.19 osssvr-1-ce2

#6140192.168.8.39 ST6140-1192.168.8.40 ST6140-1

According to the system output, the IP address corresponding to osssvr-1 is 192.168.8.11, thatof 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 varieswith the Ethernet adapter type. When the Ethernet adapter type is bge, the corresponding parameter isosssvr-1-bge0 and osssvr-1-bge2. The Ethernet adapter type varies with the server type. For theircorrespondence, 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 meetthe site requirements.

l If the IP addresses do not meet the requirements, perform the following steps to change them.

l 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 to10.10.10.10, the physical IP addresses of the two Ethernet ports from 192.168.8.18 and192.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, openthe DOS command window and then run the ping 10.10.10.10, ping 10.10.10.18, ping10.10.10.19 commands.

l If the IP address can be successfully pinged, you can infer that this new IP address is alreadyused and you need to use another one.

l If the IP address cannot be pinged, you can infer that this new IP address is idle and can beused.

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 ofM2000 Services.

For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000 Services.



3-9

Step 7 Check whether the Sybase services are running. If not, run the following command to start theSybase services:

# su - dbuser

For details about how to check and start the Sybase services, see 14.2.1 How Do I CheckWhether 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.

CAUTIONAfter being used to change the IP address of the server, the modify script can not be usedimmediately to modify parameters. You can use the modify script only when the IP address takeseffect after the restart of the server.

1. Run the modify script.

The default installation directory of the M2000 server software is /opt/OMC.


# cd /opt/OMC/tools/config

# ./modify.sh

2. Choose 1--Single system > 1--IP.3. 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. Thedefault 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 IPaddress 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 addresscorresponding 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 IPaddress corresponding to the previous IP address in 8.3.c.Please input the new ip[default 192.168.8.18]: 10.10.10.18

e. When the system output is similar to the following information, enter the old IP addresscorresponding to osssvr-1-ce2.




Issue 10 (2010-09-06)

Please input the old ip: 192.168.8.19f. 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.Please input the new ip[default 192.168.8.19]: 10.10.10.19

g. When the system output is similar to the following information, enter f or F. Then, goto the next step.Please input the old ip: f

NOTE

l When running the modify script to change the IP address of the server, if you need to changemultiple IP addresses, enter all previous addresses to be changed and their new IP addresses here.

l If the maintenance dual-plane is not configured, enter f or F when Please input the oldip: is displayed in 8.3.c. Then, go to the next step.

l If you need not change a certain IP address, press Enter when you are prompted for a new IPaddress. Then, the default value is used.

l Enter p or P. The system displays the function menu of the modify script, prompting you toperform operations such as changing the IP address or user password.

l Enter q or Q to exit the modify script.

l When the system prompts you to enter the previous IP address, enter f or Fto finish entering IPaddress 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. Thedefault 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 subnetmask. 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. Thedefault 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 defaultroute.Please input the new router ip address[default 192.168.8.1]: 10.10.10.1

NOTE

l Enter p or P to return to the previous step. Then, you can perform this step again to change thesettings of the relevant parameters.


l 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 applythe changes.



3-11

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 Enter Q to exit the script without performing any operations.

l Enter R to return to Step 8.3. You can reconfigure the relevant parameters.

l Enter P. The system displays the function menu of the modify script, prompting you to performoperations such as changing the IP address or user password.

l You need to wait for about three minutes if you run the modify script to change the IP addressof the server.

6. When the change is successful, the system displays the following information and exits themodify script.------------------------------------------------------------------ Operator complete!

If the system output contains failed, you can infer that the change fails.Contact Huaweitechnical support engineers for assistance.

Step 9 Based on the application scenario, perform the relevant operations.

Whether to Change the Server IP Address onDifferent Network Segments

Procedure

No Perform Step 10.

Yes Perform Step 11 through Step 14.

Step 10 After restarting the server, check the status of the Sybase and M2000 services.

CAUTIONIf 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:



2. Restart the server, and then log in to the server as user root through the new IP addresses.3. 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 CheckWhether the Sybase Is Started?.

-bash-3.00$ exit




Issue 10 (2010-09-06)



Step 11 Modify the gateway address information about the original network segment configured on theroute switching device.

Step 12 Log in to the server through the system controller (SC), remote system controller (RSC), orextended 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:



Step 14 Use the new IP addresses to log in to the server as user root and check the status of the Sybaseand M2000 services.

CAUTIONIf 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 CheckWhether the Sybase Is Started?.

-bash-3.00$ exit



----End

Postrequisitel (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 themonitoring 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 DiskArray.

l (Optional) If the S3000 series disk array is configured, you need to reconfigure themonitoring 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 SeriesDisk Arrays.



3-13

3.2.3 Changing the IP Address of Ethernet Port nxge3 on theM2000 Server

This section describes how to change the IP address of Ethernet port nxge3 on the M2000 serverto meet the site requirement.

PrerequisiteLog in to the server as user root.

Context

CAUTIONl 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 arraymust be on the same network segment.

l If you have changed the IP address of Ethernet port nxge3 on a different segment, you needto change the IP address of the corresponding disk array to ensure that both changed IPaddresses are on the same network segment.

l Changing the IP address of Ethernet port nxge3 does not affect the database services and theM2000 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 IPaddress meets the site requirements.

l If the IP address does not meet the requirements, you need to perform the following steps tochange it.

l 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.241as an example.

On the client PC whose IP address is on the same network segment as the new IP address, openthe 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 alreadyused. In this case, use another IP address.

l 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 portnxge3 to a new IP address.




Issue 10 (2010-09-06)

1. Modify the /etc/hosts file to change the existing IP address of Ethernet port nxge3 to a newIP address.

# TERM=vt100; export=TERM

# vi /etc/hosts2. 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, itindicates that the two files are linked. Then, proceed with Step 3.3.

l If /etc/inet/ipnodes -> ./hosts is not contained in the system output, itindicates 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 indicatesthat the two files are linked, that is, the /etc/hosts file and the /etc/inet/ipnodes file arelinked. Then, perform Step 4.

l If /etc/hosts -> ./inet/hosts is not contained in the system output, itindicates 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 nxge3to a new IP address.


Step 4 Modify the /etc/hostname.nxge3 file to change the existing IP address of Ethernet port nxge3to a new IP address.

# vi /etc/hostname.nxge3

NOTE

l If this file records the information about host names, do not modify this file.

l 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 onthe 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-15

3.3.1 Modifying the IP Address of the SC on the Netra 240 ServerThis section describes how to modify the IP address of the SC on the Netra 240 server to complywith the specification.

3.3.2 Changing the IP Address of the RSC on the V890 ServerThis 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 ServerThis section describes how to modify the IP address of the SC on the E4900 server so that thenew IP address complies with the specification. The IP address of the SC on the E4900 servercan 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 ServerThis section describes how to change the IP address of the SC on the T5220 server to ensurethat the IP address meet the requirement.

3.3.5 Changing the IP Address of the XSCF on the M4000/M5000 ServerThis section describes how to change the IP address of the XSCF on the M4000/M5000 serverto meet the actual requirements.

3.3.1 Modifying the IP Address of the SC on the Netra 240 ServerThis section describes how to modify the IP address of the SC on the Netra 240 server to complywith the specification.

Prerequisitel The PC terminal and the interface of the SC on the server communicate normally.

l The password for user admin of the SC is available.

l 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 andthe 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 portcable. 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




Issue 10 (2010-09-06)

3.3.2 Changing the IP Address of the RSC on the V890 ServerThis section describes how to change the IP address of the RSC on the V890 server.

Prerequisitel The network communication between the PC terminal and the RSC server is normal.

l You have obtained the password of the RSC user admin.

l 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 andthe 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 In ip_addr X.X.X.X, X.X.X.X indicates a new IP address planned for the RSC.

l In ip_netmask X.X.X.X, X.X.X.X indicates a new subnet mask planned for the RSC.

l 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 ServerThis section describes how to modify the IP address of the SC on the E4900 server so that thenew IP address complies with the specification. The IP address of the SC on the E4900 servercan be the IP address of the standby SC1 or the IP address of the active SC0.

Prerequisitel The PC terminal communicates normally with the ports of the standby SC1 and the active

SC0.l The two new IP addresses of the SC are planned.



3-17

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 thePC 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 portcable. For details, refer to M2000 Software Initialization Installation Guide (M4000/M5000, S10).

2. Log in to the SC as user admin.

3. 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 enterparameters such as the host name of SC1. If you need to modify only the IP address of the SC1, retainthe original settings of other parameters.

4. Change the IP address of SC1 according to Table 3-2. When the system displays anyparameter that is not listed in Table 3-2, press Enter to continue.

Table 3-2 Parameters for the standby controller

Parameter Value

Use DHCP or static network settings? [DHCP]: static

Hostname Retain the host name of SC1

IP Address Enter the new IP address ofSC1

Netmask Enter the actual subnetmask, if required

Gateway Enter the IP address of theactual gateway, if required

Enable SC Failover? [no]: yes

5. Restart the backup SC1.

:sc> reboot

When the system prompts the following message, enter y, and then press Enter.

Are you sure you want to reboot the system controller now? [no]

NOTE

l When the system prompts other messages, retain the default settings and press Enter.

l Restarting SC1 takes some time. You need to wait for a while.




Issue 10 (2010-09-06)

When the system displays osssvr-1-sc1:sc>, you can infer that the controller isrestarted. 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 thePC 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 portcable. 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 enterparameters such as the host name of SC0. If you need to modify only the IP address of the SC0, retainthe original settings of other parameters.

3. Change the IP address of SC0 according to Table 3-3. When the system prompts anyparameter that is not listed in Table 3-3, press Enter to continue.

Table 3-3 Parameters for the standby controller

Parameter Value

Use DHCP or static network settings? [DHCP]: static

Hostname Retain the host name ofSC0

IP Address Enter the new IP address ofSC0

Netmask Enter the actual subnetmask, if required

Gateway Enter the IP address of theactual gateway, if required

Enable SC Failover? [no]: yes

Connection type (ssh, telnet, none) [telnet]: telnet

Logical Hostname or IP Address [ ]: Retain the logical hostname of the SC

4. Restart the backup SC0.

:SC> reboot

When the system prompts the following message, enter y, and then press Enter.

Are you sure you want to reboot the system controller now? [no]



3-19

NOTE

l When the system prompts other messages, keep the default settings and press Enter.

l 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 isrestarted. 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 ServerThis section describes how to change the IP address of the SC on the T5220 server to ensurethat the IP address meet the requirement.

Prerequisitel The PC terminal and the network port of the SC on the server communicate well.

l The password for user admin of the SC is available.

l The new IP address of the SC is planned.

ProcedureStep 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 HostName (or IP Address), and click Open to log in to the SC.

NOTE


l 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/M5000Server

This section describes how to change the IP address of the XSCF on the M4000/M5000 serverto meet the actual requirements.




Issue 10 (2010-09-06)

Prerequisitel The communication between the PC and port 0 on the XSCF is normal.

l The password of user adminuser is available.

l A new IP address of the XSCF is planned.

Contextl Port 0 and port 1 on the XSCF are independent of each other.

l When the M4000/M5000 server is used as the M2000 server, port 0 on the XSCF is usedfor 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 To log in to the XSCF of the M4000/M5000 server, use the IP address of port 0 on the XSCF.


l For details about how to log in to the XSCF through the PuTTY, see M2000 Software InitializationInstallation Guide (T5220&M4000&M5000, S10)

l If the PC and XSCF cannot be connected by running the telnet command, connect them through aserial 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]:, typen, 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 networkinterfaces? [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. When the system displays Do you want to configure xscf#0-lan#0? [y|n]:, type y.

2. When the system displays the following prompt, enter the IP address, subnet mask, andgateway 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.Xxscf#0-lan#0 netmask: X.X.X.Xxscf#0-lan#0 default gateway: X.X.X.XAre these settings correct? [y|n]: y



3-21

NOTE

l In xscf#0-lan#0 ip address: X.X.X.X, X.X.X.X indicates a new IP address plannedfor port 0 on the XSCF.

l In xscf#0-lan#0 netmask: X.X.X.X, X.X.X.X indicates a new subnet mask planned forport 0 on the XSCF.

l In xscf#0-lan#0 default gateway: X.X.X.X, X.X.X.X indicates a new gateway IPaddress 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 timeprotocol? [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, youneed 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 :xscf#0-lan#0 status :up IP address :X.X.X.X netmask :X.X.X.X route :-n 0.0.0.0 -m 0.0.0.0 -g X.X.X.X

interface :xscf#0-lan#1 status :up IP address :192.168.9.141 netmask :255.255.255.0 route :-n 0.0.0.0 -m 0.0.0.0 -g 192.168.9.254

Continue? [y|n] :y

Step 19 When the system displays Do you want to reboot the XSCF now? [y|n]:, typey. Then, the XSCF automatically restarts.

----End




Issue 10 (2010-09-06)

3.4 Modifying the IP Address of the Disk ArrayThis section describes how to modify the IP address of the disk array. By modifying the IPaddress of the disk array, you can maintain the disk array easily.

3.4.1 Modifying the IP Address of the 3320 Disk ArrayThis describes how to modify the IP address of the 3320 disk array. To perform this task, youneed to log in to the 3320 disk array through PC or administration console. Normally, you neednot change the IP address of the disk array because the disk array is connected to the serverdirectly through optical fibers. In addition, change of IP addresses does not affect data read andwrite 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 theactual 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 theserver directly through optical fibers. In addition, change of IP addresses does not affect dataread and write operations on the disk array. Generally, use the factory default IP address of thedisk array. If the IP address of a disk array needs to be changed, change the IP address accordingto 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 theIP address of the disk array does not affect data read operations on the disk array. It is stronglyrecommended that you retain the default IP address of the disk array. If you need to change theIP address of the disk array, change it according to the actual situation. You need to configureeach 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 neednot change the IP address of the disk array because the disk array is connected to the serverdirectly through optical fibers. In addition, change of IP addresses does not affect data readoperations on the disk array. Generally, use the factory default IP address of the disk array. Ifthe IP address of a disk array needs to be changed, change the IP address according to the actualsituation.

3.4.1 Modifying the IP Address of the 3320 Disk ArrayThis describes how to modify the IP address of the 3320 disk array. To perform this task, youneed to log in to the 3320 disk array through PC or administration console. Normally, you neednot change the IP address of the disk array because the disk array is connected to the serverdirectly through optical fibers. In addition, change of IP addresses does not affect data read andwrite 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 theactual situation.

Prerequisitel The SUNWsscs software has been installed on the server.

l All the IO operations related to the disk array have been stopped.



3-23

ProcedureStep 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 maskgateway 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 thefollowing command:

sccli > configure network-interface lan0 ip-address 192.168.8.39 netmask255.255.255.0 gateway 192.168.8.1

Then, the following message is displayed:sccli changes will not take effect until controlleris 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 neednot stop the M2000 services and the database services. After the modification, you need not restart theserver either.

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 modificationand exit.

3. Perform the following operations on the server to modify the /etc/inet/ipnodes file.


l If the file records the existing IP address of the disk array, replace the existing IP addresswith the new one. After the modification, press Esc and then run the :wq command tosave the modification and exit.

l If the file records the new IP address of the disk array, you need not perform anymodification. Press Esc and then run the :q command to exit.

----End

3.4.2 Changing the IP Address of the S3200 Series Disk Array (SerialPort 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




Issue 10 (2010-09-06)

server directly through optical fibers. In addition, change of IP addresses does not affect dataread and write operations on the disk array. Generally, use the factory default IP address of thedisk array. If the IP address of a disk array needs to be changed, change the IP address accordingto the actual situation.

Context

The S3200 disk array has two controllers. Each controller has two Ethernet ports. When changingthe IP address of a controller, only Ethernet port 1 needs to be modified. Ethernet port 2 isreserved for maintenance.

If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a diskarray. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must beon the same network segment.

If you have changed the IP address of the disk array on a different segment, you need to changethe IP address of the corresponding Ethernet port nxge3 to ensure that both changed IP addressesare 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 ofthe 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 ofother devices. The serial port cable delivered with the disk array is special for the storage device. If youdo not use this serial port, the communication may fail. A DB-9 connector at one end of the serial portcable is connected to the serial port on the PC. A 6-thread round connector at the other end is connectedto 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.



3-25

Table 3-4 Setting properties of the serial port

Property Value

Bits per second 9600/38400

Data bits 8

Parity Null

Stop bits 1

Data stream control 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 fiveseconds. 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 tolog 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 ofthe 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 afterIP Address if0. To change the subnet mask, enter 192.168.8.39 after Subnet Maskif0.

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 changethe 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




# vi /etc/hosts






Issue 10 (2010-09-06)




----End

Postrequisite(Optional) After changing the IP address of the S3200 disk array, you need to reconfigure themonitoring function of the disk array. For details, see 14.1.19 How Should I Configure theMonitoring Function for the S3000 Series Disk Arrays in the corresponding AdministratorGuide. You need to reconfigure the two series disk arrays.

3.4.3 Changing the IP Address of the S2600 Disk Array (Serial PortMode)

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 theIP address of the disk array does not affect data read operations on the disk array. It is stronglyrecommended that you retain the default IP address of the disk array. If you need to change theIP address of the disk array, change it according to the actual situation. You need to configureeach S2600 disk array.

Contextl Each S2600 disk array has an active controller and a standby controller. Each controller

has a CLI serial port.l 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 ofremote operations, use the command mode. For details, see 14.1.13 How Do I Change theIP Address of the S2600 Disk Array (Command Mode)?.

l Before changing the IP address, you must familiarize yourself with the default IP addressplanning at delivery. Then, determine whether to re-set the IP address according to theactual situation.

l The IP address mentioned here is only an example. Replace it with the actual IP address.

l If you change the IP addresses of disk arrays on different network segments, change the IPaddress of the maintenance Ethernet port on the corresponding server to ensure that twochanged IP addresses are on the same network segment.

Procedure

Step 1 Use the serial port cable to connect any serial port on the controller of the disk array and that ofthe PC. Figure 3-2 shows the disk array.



3-27

Figure 3-2 Serial ports provided by the S2600 disk array

NOTE

l You need to use the serial port cable that is delivered with the disk array. Otherwise, the disk arraymay fail to be connected.

l When using the serial port cable to connect a control to the maintenance terminal, you must use theserial port cable to connect the maintenance terminal first. When disconnecting the control from themaintenance terminal, you must remove the serial port cable from the control first.

l After using the serial port cable to connect a controller to the maintenance terminal, do not enable thecontrol and the maintenance terminal at the same time.

l After using the DB9-RJ45 serial port cable to connect a controller and the maintenance terminal, youneed to use the HyperTerminal or any other program provided by the Windows operating system tolog in to the CLI serial port.

Step 2 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on thePC.

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 Property Value

Bits per second 115200

Data bits 8

Parity check None

Stop bits 1

Flow control None

Step 6 Press Enter. If the connection is successful, a dialog box is displayed, as shown in Figure3-3.




Issue 10 (2010-09-06)

Figure 3-3 Successful connection interface

Step 7 In the successful connection interface, type the user name and password. Then the successfullogin success dialog box is displayed, as shown in Figure 3-4.

CAUTIONThe initial name and password of the administrator is admin and 123456, respectively. To ensurethe system security, you need to change the password after the initial login.

Figure 3-4 Successful login dialog box



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 -ggateway

For example, to change the IP address of the Ethernet port that is managed by controller A to10.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.0This operation will change your controller's IP configuration. if you want to change the IP of the controller you logged in, you will log out after you set thenew 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 Subnet Mask Gateway MAC Address A 10.71.15.20 255.255.255.0 10.71.15.1 00:18:82:e2:00:fb

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 -ggateway

For example, to change the IP address of the Ethernet port that is managed by controller B to10.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 change the IP of the controller you logged in, you will log out after you set thenew 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

Controller IP Address Subnet Mask Gateway MAC Address B 10.71.15.21 255.255.255.0 10.71.15.1 00:18:82:e2:01:57

----End

PostrequisiteDuring commissioning, you need to configure the monitoring function of the S2600 disk arrayafter you install and configure the M2000 client application. For details, see section "Configuringthe Monitoring Function of the S2600 Disk Array".

During maintenance, if the monitoring function of the S2600 disk array is configured, you needto 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 correspondingadministrator manual.




Issue 10 (2010-09-06)

3.4.4 Changing the IP Address of the 6140 Disk Array (Serial PortMode)

This section describes how to change the IP address of the 6140 disk array. Normally, you neednot change the IP address of the disk array because the disk array is connected to the serverdirectly through optical fibers. In addition, change of IP addresses does not affect data readoperations on the disk array. Generally, use the factory default IP address of the disk array. Ifthe IP address of a disk array needs to be changed, change the IP address according to the actualsituation.

Context

The 6140 disk array has two controllers. Each controller has two Ethernet ports. When changingthe IP address of a controller, only Ethernet port 1 needs to be modified. Ethernet port 2 isreserved for maintenance.

If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server and a diskarray. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk array must beon the same network segment.

If you have changed the IP address of the disk array on a different segment, you need to changethe IP address of the corresponding Ethernet port nxge3 to ensure that both changed IP addressesare 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 controllerA. 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 One end is the 6-pin mini DIN connector, and the other end is the basic cable of the standard 9-pinserial port connector.

l 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 serialport connector of the PC.



3-31

Step 3 Choose Start > Programs (P) > Accessories > Communications > HyperTerminal on thePC.

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 Value

Bits per second 38400

Data bits 8

Parity Null

Stop bits 1

Data stream control Null

After the connection is complete, a physical connection between the PC and the 6140 disk arrayis set up.

Step 7 Press Ctrl+Break. The serial port responses with a request so that the baud rate can besynchronized 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 sequencefor the terminal configuration, and then send the essential Break to the controller of the disk array. Forinstance, 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 upfor 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.

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




Issue 10 (2010-09-06)

Service Interface Main Menu==============================1) Display IP Configuration2) Change IP Configuration3) Reset Storage Array (SYMbol) PasswordQ) Quit MenuEnter Selection:

Step 13 If the following information is displayed, type 1.Select Ethernet Port==============================1) Ethernet Port: 02) Ethernet Port: 1Q) QuitEnter Selection: 1

Step 14 If the following information is displayed, type n. The DHCP function is not used to configurethe 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 subnetmask.

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 ConfigurationIP Address if1 : 192.168.128.101 IP-addressSubnet 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.Service Interface Main Menu==============================1) Display IP Configuration2) Change IP Configuration3) Reset Storage Array (SYMbol) PasswordQ) Quit MenuEnter Selection:

Step 17 If the following information is displayed, type 1.Select Ethernet Port==============================1) Ethernet Port: 02) Ethernet Port: 1Q) QuitEnter Selection: 1

The IP address of the selected Ethernet port is displayed. Check whether the modified IP addressis correct again. If the modified IP address is incorrect, perform operations Step 12 through Step17 to configure the IP address of the controller again.

Step 18 If the following information is displayed, enter Q to exit.Service Interface Main Menu==============================1) Display IP Configuration2) Change IP Configuration3) Reset Storage Array (SYMbol) PasswordQ) Quit MenuEnter Selection:



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




# vi /etc/hosts






----End




Issue 10 (2010-09-06)

4 Managing the M2000 Clients

About This Chapter

This chapter describes how to manage the M2000 clients. The graphic user interface (GUI) onthe M2000 client supports the O&M for the NEs and enables you to monitor the M2000. Youmust manage the M2000 clients to ensure their normal operation.

ContextThe requirements of the M2000 client for operation rights are as follows:l The users who are authorized to install, upgrade, and uninstall the M2000 client are

Windows users. They belong to the user group Administrators.l 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 installationdirectory.

4.1 Managing Files and Disks on M2000 ClientsThis section describes how to manage the file systems and disks on the M2000 clients.

4.2 Monitoring the Login Status of the M2000 ClientsThis section describes how to monitor the login status of the M2000 clients (including theLMTs which access NEs through the M2000 proxy). When the number of login clients exceedsthe preset maximum number of M2000 threads, you must force a user out to establish a newconnection.

4.3 Setting the Number of Clients Accessible on a PCThis section describes how to edit the configuration file on the M2000 client for setting thenumber of clients of the same version (excluding the LMTs that gain access to NEs through theM2000 proxy) that can be started on a PC.

4.4 Setting the Time Information on the M2000 ClientThis section describes how to set the time information on the M2000 client.

M2000Administrator Guide (Sun, S10) 4 Managing the M2000 Clients


4-1


4.1.1 Introduction to the M2000 Client File SystemThis introduces the M2000 client file system.

4.1.2 Clearing the Disk Space of an M2000 ClientThis section describes how to clear the disk space of an M2000 client. Before performing thisoperation, ensure that the files to be deleted are not required for future operations. Deleting auseful file by mistake may lead to a system operation error.


The client software runs on the Windows operating system and is based on the JAVA virtualmachine. The installation package of the M2000 client software includes the JAVA virtualmachine supported by Windows.

Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size ofthe 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 10MB; 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 Description

client installation path Refers to the M2000 client installation path. Thedefault path is C:\iManagerM2000Client.

M2000 client installation path\client Refers to the directory for saving clientprograms.

M2000 client installation path\client\bin Refers to directory where executable files arelocated.

M2000 client installation path\client\Data

Refers to the directory for saving the NEconfiguration files.

M2000 client installation path\client\diagnosis

Refers to the directory for saving theinformation that is used for locating problems.NOTE

This directory appears only after you run theM2000 diagnosis tool.

M2000 client installation path\client\ext_runcfg

Refers to the directory where the files related tointegrated components are located.

M2000 client installation path\client\dtd Refers to the directory for saving the Dtd files.

4 Managing the M2000 ClientsM2000



Issue 10 (2010-09-06)


M2000 client installation path\client\help Refers to the directory for saving the online helpfiles.

M2000 client installation path\client\IDAPI32

Refers to the directory for saving the localWSdynamic link libraries.

M2000 client installation path\client\lib Refers to the directory for saving the libraryfiles.

M2000 client installation path\client\localWs

Refers to the directory for saving LocalShellthat is used to start the 2G LMT.

M2000 client installation path\client\style

Refers to the directory for saving theconfiguration files of client.

M2000 client installation path\client\Templates

Refers to the directory for saving the mappingbetween administrative regions and their IDs.

M2000 client installation path\client\tmp Refers to the directory for saving temporaryfiles during the upgrade.

M2000 client installation path\client\tracefile

Refers to the directory for saving the trace files.

M2000 client installation path\client\update

Refers to the directory for saving the upgradefiles.

M2000 client installation path\client\cbb Stores the CBB files of the M2000 client.

M2000 client installation path\client\configuration

Stores the configuration files of the M2000client.

M2000 client installation path\client\features

Stores the feature configuration files of thesubsystems of the M2000 client.

M2000 client installation path\client\plugins

Stores the configuration files of the subsystemsof the M2000 client as plug-ins.

M2000 client installation path\uninstall Refers to the directory for saving the uninstaller.

M2000 client installation path\script Refers to the root directory of the iSStar script.

M2000 client installation path\client\bin\run

Refers to the directory in which the files forconfiguring the startup parameters of the clientand components are located.



4-3


M2000 client installation path\cau Refers to the installation directory of the cau(Client Auto Upgrade) client software and thedirectory in which the version, documentabstract, and group information about theM2000 client are located.NOTE

l The cau(Client Auto Upgrade) client softwareprovides an upgrade detection mechanism that isbased on the document abstract. It also comparesthe document abstract of the server with that of theclient. If the document abstracts are not consistent,you need to upgrade the client.

l Based on the group information, the server groupsand packs all the client documents deployed on theserver for the client to download, install, andupgrade. Based on the group information, theclient also groups and packs all client files. Thus,when these files are being downloaded, they canbe compared with those files grouped and packedby the server.

M2000 client installation path\jre Stores the Java virtual machine of the M2000.

M2000 client installation path\lib Stores the library files of M2000 client, remotenotification client, script framework tool clientand datamanager client.


Context

CAUTIONYou 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 Trace logs

l Temporary files after the running of the M2000 log collector

Procedurel Delete the trace logs.




Issue 10 (2010-09-06)

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

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 collectorand are saved in the directory M2000 client installation path\client\diagnosis.

----End

4.2 Monitoring the Login Status of the M2000 ClientsThis section describes how to monitor the login status of the M2000 clients (including theLMTs which access NEs through the M2000 proxy). When the number of login clients exceedsthe preset maximum number of M2000 threads, you must force a user out to establish a newconnection.

PrerequisiteBefore 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 PCThis section describes how to edit the configuration file on the M2000 client for setting thenumber of clients of the same version (excluding the LMTs that gain access to NEs through theM2000 proxy) that can be started on a PC.

Prerequisitel You have logged in to the PC as a user in the user group Users.

l The M2000 client is running properly.



4-5

Context

Ideally, a maximum of 31 M2000 clients of the same version can be started on a PC. The numberof clients of the same version connected to a PC depends on the configuration of the PC and thatof 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 theport range that the client attempts to occupy. The minimum port number is separated from themaximum number by "-". The client tests the port from the minimum number to the maximumnumber. If all the ports are occupied, the system displays an Error message. You can set themaximum number of clients of the same version started on a PC by modifying the value ofcorba_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 The ports after modification cannot exceed the range from 30500 to 30699.

l Ensure that the ports in the modified range on the firewall are enabled when you modify the port range.

l The ports may be used by other applications. Perform the following substeps to check the occupationof 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 ClientThis 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 ClientThis section describes how to modify the date, time, and time zone on the M2000 client that isbased on the Windows operating system. Modifying the date, time, and time zone on theM2000 client means modifying the date, time, and time zone of Windows.

4.4.2 Setting the NTP Service on the M2000 Client




Issue 10 (2010-09-06)

This section describes how to set the M2000 client as the NTP client. This task enables you tosynchronize the client with the NTP server through the NTP service of the Windows operatingsystem.

4.4.1 Modifying the Date, Time, and Time Zone on the M2000 ClientThis section describes how to modify the date, time, and time zone on the M2000 client that isbased on the Windows operating system. Modifying the date, time, and time zone on theM2000 client means modifying the date, time, and time zone of Windows.

PrerequisiteThe 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 Operation

Hour Set the required hour on the Time tab page.

Minute Set the required minute on the Time tab page.

Second 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 zonefrom the drop-down list.

Step 4 Click Apply.

----End

4.4.2 Setting the NTP Service on the M2000 ClientThis section describes how to set the M2000 client as the NTP client. This task enables you tosynchronize the client with the NTP server through the NTP service of the Windows operatingsystem.

Prerequisitel You have logged in to the Windows operating system. The Windows operating system is

running properly.

l The M2000 client and the M2000 server communicate normally.

l The clock source of the server is operational.



4-7

ContextWhen the M2000 client is configured as the NTP client, synchronize the time of the M2000client 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 RegistryEditor window.

In the registry, choose HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet >Services > W32Time > Parameters. Then, change the value of the parameter LocalNTP to0, which is the default value. If the parameter LocalNTP does not exist, it indicates that thevalue 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 ofEnable 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 takeseffect 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 theServices 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 serverby /setsntp, the NTP server time is the local time of the PC.

Step 5 Perform operations based on operating systems.l If the M2000 client runs on Windows 2000 operating system, perform Step 6.

l If the M2000 client runs on Windows 2003, Windows 2008, Windows XP or Windows Vistaoperating system, perform Step 7 through Step 8.





Issue 10 (2010-09-06)

c:\>w32tm -once -v -test

The system displays the host name of the connected NTP server, deviation between the localtime 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


c:\>w32tm /stripchart /computer:IP address of the M2000 server /dataonly

The system displays the following information, including the local time of the client anddeviation 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.9881239s10:05:11, +04.9814570s10:05:13, +04.9740897s10:05:15, +04.9589559s10:05:17, +04.9449507s...

In the system output, the first column displays the local time of the client, and the second columndisplays the deviation between the local time and the server time. + indicates that the client timeis earlier than the server time. - indicates that the client time is later than the server time. Youcan press Ctrl+C to exit the browse window.

----End



4-9

5 Managing the M2000 Users

About This Chapter

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 themanagement and monitoring operations related to the types of users and M2000 user groups.

5.1 Types of M2000 UsersThis 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 themapping between the network manager user and NE user and the principle for assigning theirrights.

5.2 Managing Solaris UsersThis section describes how to manage the Solaris users. The four types of Solaris users involvedin running the M2000 server are: root, dbuser, omcuser, and ftpuser. In addition, it describeshow to create a user, remove a user, and modify a password.

5.3 Managing Sybase UsersThis chapter describes how to manage the Sybase user that is required for the operation of theM2000. This chapter also describes how to change the password of the Sybase user.

5.4 Managing OM UsersOM users operate and maintain the entire network or specified NEs through the M2000. TheM2000 provides the user management function. By using this function, you can manage userinformation and user rights. You can also monitor user sessions and operations. This helps toprevent unauthorized operations and ensure system security.

M2000Administrator Guide (Sun, S10) 5 Managing the M2000 Users


5-1

5.1 Types of M2000 UsersThis 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 themapping between the network manager user and NE user and the principle for assigning theirrights.

5.1.1 Introduction to Solaris UsersThis introduces the Solaris users involved in the operation of the M2000 server.

5.1.2 Introduction to Sybase UsersThis introduces the Sybase user accounts used by the M2000 and the mapping authorities.

5.1.3 NE UsersNE users refer to the users accounts that can log in to and operate and maintain NEs through theLMT 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 tooperate and maintain NEs as NE users. NE users can also perform operations such astroubleshooting at the near ends of NEs.

5.1.4 Principles of NM User AuthorizationThis section describes various privileges of the M2000 NM users and the principles for userauthorization. The M2000 assigns privileges to user groups. The privileges assigned to a groupare passed on to individual users based on the binding between the user group and the users inthe user group. The privileges can also be assigned to users directly.

5.1.5 Principles of NE User AuthorizationThis section describes the principles of NE user authorization. The M2000 supports theauthorization of operation privileges provided to NE user accounts.


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 musthave the three manually created user accounts: dbuser, omcuser, and ftpuser. You must also haveone manually created user group: omcsysm.

Table 5-1 describes the Solaris user accounts.

5 Managing the M2000 UsersM2000



Issue 10 (2010-09-06)

Table 5-1 Solaris user accounts

AccountName

Usage Authority Group ShellResolutionProgram

Directory

root User root is thedefault useraccount of thesystem. User rootis authorized tocontrol allresources, createother useraccounts, assignauthorities toother users, andperform allsystemoperations.

User root ownsthe highestauthority of thesystem.User root isauthorized toinstall anduninstall M2000serverapplications andto start and stopM2000 services.

Other,bin, sys,adm,uucp,mail, tty,lp,nuucp,daemon,anduser.root

/bin/bash /

dbuser User dbuser is theadministrator ofthe databasesoftware. Userdbuser isresponsible forthe O&M of thedatabasesoftware.Before installingthe Sybase, youmust manuallycreate userdbuser.

User dbuser isauthorized toperform alloperations on thedatabase. Forexample, userdbuser isauthorized to useisql to interactwith thedatabase.

Staff andomcsysm

/bin/bash /opt/sybase



5-3

AccountName


Directory

omcuser User omcuser isthe operator of theM2000. Useromcuser isresponsible forthe O&M of theM2000 system,such as systemstatus inquiry,system backup,and systemrestoration.Before installingthe M2000applications, youmust create useromcuser.

User omcuser isauthorized toaccess thedatabase andperform theO&Moperations.User omcuser isnot allowed toinstall oruninstall M2000serverapplications andto start or stopM2000 services.

Staff(primarygroup),sys, root,andomcsysm(secondarygroup)

/bin/bash /export/home/omc

ftpuser User ftpuser isused by theM2000applications toperform softwaremanagement andfile transmission.Before installingthe M2000applications, youmust create userftpuser.

User ftpuser isauthorized toperformsoftwaremanagement andfiletransmissionsfor NEs.

omcsysm

/bin/bash /export/home/sysm


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 defaultuser 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 UsersNE users refer to the users accounts that can log in to and operate and maintain NEs through theLMT 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




Issue 10 (2010-09-06)

operate and maintain NEs as NE users. NE users can also perform operations such astroubleshooting at the near ends of NEs.

Types of NE UsersNE 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. NEsprovide several default local users.

CAUTIONNodeBs have only default local users because they do not have the BAM and cannot createany 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 UsersMode 1 NEs of centralized user management support local and non-local NE users. If an OMuser is granted with the MML authority of a mode 1 NE, the OM user becomes a non-local userof this NE. You can log in to the M2000 as a non-local NE user to operate and maintain themode 1 NEs. For details about mode 1 NEs, see NEs Corresponding to Different CentralizedUser 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 enableNE local users to log in to and manage NEs on the M2000.

Management of Mode 2 NE UsersMode 2 NEs of centralized user management support only local NE users. For the list of mode2 NEs, see NE Types.

To perform centralized management on mode 2 NEs, you can create an NE User account foreach local NE user (with the same user name and password) in the NE User Managementwindow on the M2000 and correlate the accounts to the corresponding OM users. You can login to the M2000 as a non-local OM user that is correlated to a local NE user to operate andmaintain 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 informationabout the NE user on the M2000 according to the information about the local NE user.

Management of Optical Transmission NE UsersOptical transmission NEs support only local NE users. For details about optical transmissionNEs, see NE Types.

In the NE User Management window on M2000, you can create NE users for the opticaltransmission NEs. In the Main Topology window on the M2000, you can use a created or default



5-5

NE user as a parameter for creating an optical transmission NE and then log in to the NE tooperate and maintain it.

5.1.4 Principles of NM User AuthorizationThis section describes various privileges of the M2000 NM users and the principles for userauthorization. The M2000 assigns privileges to user groups. The privileges assigned to a groupare passed on to individual users based on the binding between the user group and the users inthe 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 usergroups: Administrators, Operators, Guests and SMManagers.

Table 5-2 describes the M2000 user privileges.

Table 5-2 Privileges of M2000 users

Privileges Description Related Operations

Operation period Period during which M2000 userscan log in to and operate theM2000 or NEs.If the current time is not within theperiod, M2000 users cannot log in.

Setting the operation periodwhen creating a user accountChanging the operationperiod by modifying theattributes of a user account

Validity of a useraccount

Check the validity of a useraccount. Generally, the status of auser account is valid. If the statusof a user account is invalid, theuser cannot log in to or operate theM2000.

If a user account is locked fora period greater than the timeset by the system, the systemautomatically unlocks theuser account. The system alsoallows you to manuallyunlock a user account.

Locking status If the number of login failures of auser account during the specifiedperiod reaches the preset value, thesystem locks the user account.The user, whose account is invalid,cannot log in to or operate theM2000.

Modifying user validity bymodifying the attributes of auser account

Binding IP address The M2000 does not restrict the IPaddress of the client using whichusers log in.After a M2000 user is bound to anIP address, the IP address of theclient using which the user logs inmust exist in the list of bound IPaddresses.

Setting the list of bound IPaddresses when creating auser accountChanging the list of bound IPaddresses by modifying theattributes of a user account




Issue 10 (2010-09-06)

Privileges Description Related Operations

M2000 operation rights A user has the authority to performrelevant operations on the M2000.After the privileges of users arebound, private privileges foroperating the M2000 can beallocated to users directly. Thepublic privileges for operating theM2000 can be allocated first touser groups and then to users basedon the binding relations betweenthe user groups and the users.Private privileges refer to theprivileges enjoyed by privateusers.Public privileges are the privilegesenjoyed by all the users in a usergroup.With regard to convenience andefficiency, the recommendedprivileges are public privileges.

Private privileges indicatethat the privileges foroperating the M2000 areallocated to users after theirprivileges are bound.Public privileges indicate thatthe privileges for operatingthe M2000 can be allocatedfirst to user groups and thento users based on the bindingrelations between user groupsand users.

5.1.5 Principles of NE User AuthorizationThis section describes the principles of NE user authorization. The M2000 supports theauthorization of operation privileges provided to NE user accounts.

Each type of NEs provide certain default MML command group. In addition, you can customizenew 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.l Use the principles of NE user authorization for assigning the privileges that are commonly

used by NE users and certain NE types.l 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 thecommand groups of these NEs.

NOTE

l Superuser admin can run NE MML commands on the M2000 even without authorization.

l For details on the authority to manage an NE, refer to the M2000 Online Help.

5.2 Managing Solaris UsersThis section describes how to manage the Solaris users. The four types of Solaris users involvedin running the M2000 server are: root, dbuser, omcuser, and ftpuser. In addition, it describeshow to create a user, remove a user, and modify a password.



5-7


5.2.2 Changing the Password of User rootThis section describes how to change the password of user root.

5.2.3 Changing the Password of User dbuserThis section describes how to change the password of user dbuser when you log in to the systemas user root.

5.2.4 Changing the Password of User omcuserThis section describes how to change the password of user omcuser when you log in to the systemas user root.

5.2.5 Changing the Password of User ftpuserThis section describes how to change the password of user ftpuser when you log in to the systemas user root.

5.2.6 Creating a Solaris UserThis section describes how to create a Solaris user. The Solaris user can operate and maintainthe Solaris system.

5.2.7 Deleting a Solaris UserThis section describes how to delete a Solaris user. You can manually delete the Solaris userthat is not required.


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 musthave the three manually created user accounts: dbuser, omcuser, and ftpuser. You must also haveone manually created user group: omcsysm.

Table 5-3 describes the Solaris user accounts.




Issue 10 (2010-09-06)

Table 5-3 Solaris user accounts

AccountName


Directory

root User root is thedefault useraccount of thesystem. User rootis authorized tocontrol allresources, createother useraccounts, assignauthorities toother users, andperform allsystemoperations.

User root ownsthe highestauthority of thesystem.User root isauthorized toinstall anduninstall M2000serverapplications andto start and stopM2000 services.

Other,bin, sys,adm,uucp,mail, tty,lp,nuucp,daemon,anduser.root

/bin/bash /

dbuser User dbuser is theadministrator ofthe databasesoftware. Userdbuser isresponsible forthe O&M of thedatabasesoftware.Before installingthe Sybase, youmust manuallycreate userdbuser.

User dbuser isauthorized toperform alloperations on thedatabase. Forexample, userdbuser isauthorized to useisql to interactwith thedatabase.

Staff andomcsysm

/bin/bash /opt/sybase



5-9

AccountName


Directory

omcuser User omcuser isthe operator of theM2000. Useromcuser isresponsible forthe O&M of theM2000 system,such as systemstatus inquiry,system backup,and systemrestoration.Before installingthe M2000applications, youmust create useromcuser.

User omcuser isauthorized toaccess thedatabase andperform theO&Moperations.User omcuser isnot allowed toinstall oruninstall M2000serverapplications andto start or stopM2000 services.

Staff(primarygroup),sys, root,andomcsysm(secondarygroup)

/bin/bash /export/home/omc

ftpuser User ftpuser isused by theM2000applications toperform softwaremanagement andfile transmission.Before installingthe M2000applications, youmust create userftpuser.

User ftpuser isauthorized toperformsoftwaremanagement andfiletransmissionsfor NEs.

omcsysm

/bin/bash /export/home/sysm

5.2.2 Changing the Password of User rootThis section describes how to change the password of user root.

Prerequisitel The old password of user root is available.

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




Issue 10 (2010-09-06)

# 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 dbuserThis section describes how to change the password of user dbuser when you log in to the systemas user root.

Prerequisitel The new password for dbuser is available.

l You have logged in to the M2000 server as user root.

Procedure

Step 1 Run the following command to change the password:

# passwd dbuser



passwd: password successfully changed for dbuser

----End

5.2.4 Changing the Password of User omcuserThis section describes how to change the password of user omcuser when you log in to the systemas user root.

Prerequisitel The new password for omcuser is available.

l You have logged in to the M2000 server as user root.

ContextNOTE

The provided password must meet the policy of minimum complexity. That is, the password comprises ofat 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




5-11


passwd: password successfully changed for omcuser

----End

5.2.5 Changing the Password of User ftpuserThis section describes how to change the password of user ftpuser when you log in to the systemas user root.

Prerequisitel The new password of user ftpuser is available.

l You have logged in to the system as root.

Context

CAUTIONThe special characters '"$ cannot be contained in the password of user ftpuser. To improve thepassword security, you are advised to use the following policies to set the password:l The password length ranges from 8 to 30 characters.

l At least one uppercase is contained in the password.

l At least one lowercase is contained in the password.

l At least one digit is contained in the password.

l At least one special character is contained in the password.

l No user name is contained in the password.

Procedure

Step 1 If the M2000 services are running, stop them.



Step 2 Check whether the Sybase services are started. For details, see 14.2.1 How Do I Check Whetherthe Sybase Is Started?.

If the Sybase services are not started, start them first. For details, see 14.2.2 How to Start theSybase.

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.





Issue 10 (2010-09-06)



# ./modify.sh

2. Choose 1--Single system > 4--Password of ftpuser.

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



4. When the system displays the following information, enter Y to apply the change.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 You need to wait for about one minute if you run the modify script to change the password ofuser ftpuser.

5. When the system displays the following information, it indicates that the change issuccessful.------------------------------------------------------------------ Operator complete!

If the system output contains failed, it indicates that the change fails. Contact Huaweitechnical support engineers for assistance.

6. When the system displays the function menu, enter q to exit.




Step 5 Start the M2000 services.

For details, see 7.2.3 Starting the M2000 System Services.

----End



5-13

5.2.6 Creating a Solaris UserThis section describes how to create a Solaris user. The Solaris user can operate and maintainthe Solaris system.

PrerequisiteKeep 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 useraccounts: dbuser, omcuser, and ftpuser. For details, see the software installation manual relatedto 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 ofthe 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 maindirectory /home1 is automatically created. The template files ensure a unified operatingenvironment for all the users. The template files are located in the /etc/skel directory with userID 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



passwd: password successfully changed for omc1

----End

5.2.7 Deleting a Solaris UserThis section describes how to delete a Solaris user. You can manually delete the Solaris userthat is not required.

PrerequisiteThe account of the user to be deleted is available.




Issue 10 (2010-09-06)

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 UsersThis chapter describes how to manage the Sybase user that is required for the operation of theM2000. This chapter also describes how to change the password of the Sybase user.


5.3.2 Changing the Password of User saThis section describes how to change the password of user sa.

5.3.3 Changing the Name of the Database ServerThis section describes how to change the name of the database server based on the actualrequirements.


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 defaultuser 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 saThis section describes how to change the password of user sa.

PrerequisiteYou have logged in to the system as user root.



5-15

Context

CAUTIONTo improve the password security, you are advised to use the following policies to set thepassword:l The valid password ranges from 8 to 30 characters.

l The special characters '"$ cannot be contained in the password. Instead, the password cancontain only 0 to 9, a to z, A to Z, and special characters ~!@#%^&*()_-+=|\/<>,.;:[]{}.

Procedure







Step 3 Run the modify script to change the password of user sa.1. Run the modify script.




# ./modify.sh2. Choose 1--Single system > 3--Database password.3. 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:




Issue 10 (2010-09-06)

NOTE




l 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.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 You need to wait for about 12 minutes if you run the modify script to change the password ofuser sa.



6. When the function menu is displayed again, enter q to exit.



----End

5.3.3 Changing the Name of the Database ServerThis section describes how to change the name of the database server based on the actualrequirements.


Contextl 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 changethe name of the database server.

l When the data is transferred between two M2000 servers, the database server names of thetwo servers must be consistent. You can change the database server name of one of theservers for implementing the data transfer.



5-17

l This takes the change of the database server name from SYB to SYB1 as an example.

l The format of the database server name is SYB or SYBX where X is a numeral. Forexample, SYB, SYB2, and SYB3 are names of database servers.

Procedure







Step 3 Run the modify script to change the name of the database server.

1. Run the modify script.




# ./modify.sh

2. Choose 1--Single system > 2--Database password.

3. Based on the system prompts, enter the previous and new name of the database server andthe 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 Enter q or Qto exit the modify script.


4. When the system displays the following information, enter Y to apply the change.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




Issue 10 (2010-09-06)

NOTE




l You need to wait for about 15 minutes if you run the modify script to change the IP address ofthe server.



6. When the system displays the function menu again, enter q to exit.



----End

5.4 Managing OM UsersOM users operate and maintain the entire network or specified NEs through the M2000. TheM2000 provides the user management function. By using this function, you can manage userinformation and user rights. You can also monitor user sessions and operations. This helps toprevent unauthorized operations and ensure system security.

Managing OM users, see M2000 User Management User Guide.



5-19

6 Managing OSS System

About This Chapter

The M2000 provides the OSS management function. By using this function, you can viewingNE partitioning, managing the M2000 license, monitoring the M2000 server, integrated taskmanagement, check OMC status, collecting NM log files.

6.1 Monitoring the M2000 ServerYou 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 performedon the system monitor client.

6.2 Querying the System Logs of the M2000This section introduces the M2000 system log. System logs record the operation of theM2000 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 FilesWhen the M2000 system fails, you can run the diagnostic tool to collect all the related diagnosticinformation from the M2000 Server and Client through the FTP protocol. When the M2000client or server cannot run properly, you can collect all the operational information from theM2000 client or server to locate faults.

6.4 Querying NE SubareasThis section describes how to query NE subareas. An NE subarea refers to the M2000 serverthat manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed bydifferent servers (subareas). On the M2000 client, you can query different NE subareas.

6.5 Managing the M2000 LicenseM2000 licenses can restrict the number of manageable devices, and the availability duration ofthe M2000. You need to manage the licenses periodically.

6.6 Check OMC statusOMC check is used to check the status of the M2000. This check also exports check reportsin .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 ManagementThe M2000 provides the function of integrated management of scheduled tasks. Thus, you canbrowse information such as the task status and the progress. You can also create, modify, and

M2000Administrator Guide (Sun, S10) 6 Managing OSS System


6-1

delete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, andsave task result files to the client.

6.8 Reference of the OSS Management GUIThis part describes the OSS management interfaces and related information such as theparameters used in the OSS management. This helps you understand the functions of OSSmanagement easily.

6 Managing OSS SystemM2000



Issue 10 (2010-09-06)

6.1 Monitoring the M2000 ServerYou 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 performedon the system monitor client.

Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browserwindow is displayed.

The system monitor browser consists of the following items:

l Service Monitor:Monitors information about services, such as status and start time.

l Process Monitor:Monitors information about processes, such as number of used handles, CPU usage,memory usage, number of database connections, and number of threads.

l Hard Disk Monitor:Monitors information about the disks in the system, such as total capacity, used space, freespace, usage, and status.

l Database Monitor:Monitors information about the databases in the system, such as status, space, usage, andlog space.

l Server Monitor:Monitors information about the services, such as status, operating system, memorycapacity, CPU usage, and memory usage.

l Component Information:Provides information about server components, such as name, version, and description.

6.1.1 Refreshing the Monitoring InformationTo know the latest running status of the M2000 server, you need to refresh the monitoringinformation.

6.1.2 Checking the CPU and Memory Usage Information About the M2000 ServerThis 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 login to the server to rectify the faults in time.

6.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 ClientThis section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client.

6.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000ClientThis section describes how to check the database status through the M2000 client to know theusage of the databases.

6.1.5 Checking the M2000 ServicesThis section describes how to check the M2000 services. When the M2000 services are notrunning 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



6-3

This section describes how to check the status of the M2000 processes. When the M2000processes are not running normally, you need to locate faults and log in to the server to rectifythe faults in time.

6.1.7 Viewing the Information about M2000 Server ComponentsThis function enables you to view the information of the components installed on the M2000server that you log in to.

6.1.8 Saving the Monitoring InformationFor the convenience of future analysis of the information that is monitored at certain time, youcan save the required monitoring information to the server.

6.1.9 Setting Alarm Thresholds for the M2000This section describes how to set the alarm thresholds for the M2000. On the M2000 client, youcan set the alarm thresholds to monitor the server status. The monitoring of system status consistsof server monitoring, disk monitoring, databases monitoring, and service monitoring. if the valueof a parameter exceeds the threshold, the system generates the corresponding alarm.

6.1.1 Refreshing the Monitoring InformationTo know the latest running status of the M2000 server, you need to refresh the monitoringinformation.

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.

l 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 berefreshed.

Step 3 click Refresh.

----End

6.1.2 Checking the CPU and Memory Usage Information About theM2000 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 login to the server to rectify the faults in time.

Prerequisitel You have logged in to the M2000 client.

l You have the relevant operation rights.




Issue 10 (2010-09-06)

Procedure

Step 1 Choose Monitor > System Monitor > Monitor Browser. The System Monitor Browserwindow 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 CPUusage or memory usage of the corresponding server is normal; the red icon indicates that the CPU usageor memory usage of the corresponding server is abnormal. In the case that you have set the performancemonitoring threshold for an item, the icon corresponding to the item changes from green to red when thevalue 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 ServerThrough the M2000 Client

This section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client.





6-5

ContextChecking the disk usage information about the M2000 server requires only a few systemresources and does not affect system operation.

Procedure


Step 2 Click the Hard Disk Monitor tab to check disk usage information about the M2000 server. SeeFigure 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 redicon indicates that the usage of the corresponding disk is abnormal. If the usage of a disk exceeds the presetthreshold, the icon in this column changes from green to red.


----End

6.1.4 Checking the Database Usage Information About the M2000Server Through the M2000 Client

This section describes how to check the database status through the M2000 client to know theusage of the databases.




Issue 10 (2010-09-06)



ContextThis operation requires only a few system resources and does not affect system operation.

Procedure


Step 2 Click the Database Monitor tab to check the database status of the M2000 server. See Figure6-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; thered icon indicates that the usage of the corresponding database is abnormal. If the usage of a databaseexceeds the preset threshold, the icon in this column changes from green to red.


----End




6-7



ContextChecking the M2000 services on the M2000 client requires only a few system resources anddoes not affect system performance.

Procedure


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 iconindicates the corresponding process is abnormal.


----End

6.1.6 Checking the Status of the M2000 ProcessesThis section describes how to check the status of the M2000 processes. When the M2000processes are not running normally, you need to locate faults and log in to the server to rectifythe faults in time.




Issue 10 (2010-09-06)



ContextChecking the states of the M2000 processes on the M2000 client requires only a few systemresources and does not affect system performance.

Procedure


Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on theM2000 server. See Figure 6-5.

Figure 6-5 Process Monitor tab page


----End

6.1.7 Viewing the Information about M2000 Server ComponentsThis function enables you to view the information of the components installed on the M2000server that you log in to.

Procedure




6-9

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 InformationFor the convenience of future analysis of the information that is monitored at certain time, youcan save the required monitoring information to the server.

Procedure


Step 2 In the System Monitor Browser window, click the tab of the monitoring information, and thenclick Save As.

NOTE

l The monitoring information can be saved in the format of TXT, HTML, CSV, or XML.

l 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 M2000This section describes how to set the alarm thresholds for the M2000. On the M2000 client, youcan set the alarm thresholds to monitor the server status. The monitoring of system status consistsof server monitoring, disk monitoring, databases monitoring, and service monitoring. if the valueof a parameter exceeds the threshold, the system generates the corresponding alarm.



ContextOn the M2000, you can set the thresholds of certain parameters for the purpose of systemmonitoring. When the value of a parameter exceeds the threshold, the relevant record in theSystem Monitor Browser window is displayed in red. In addition, the corresponding alarm isgenerated.

Procedure

Step 1 In the main window, choose Monitor > System Monitor > Configurations. The SystemMonitor Settings dialog box is displayed, as show in Figure 6-6.




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.



6-11

Table 6-1 Server Monitor

Name Description Settings

ServerMonitorParameterSettings

CPU sustainedoverload times(times)

Description:l If the CPU usage is larger

than Threshold forAlarm Generation ofCPU used rate forconsecutive x times, theM2000 generates a highCPU usage alarm.

l If the CPU usage issmaller than Thresholdfor Alarm Clearance ofCPU used rate forconsecutive x times, theM2000 generates analarm, prompting that thehigh CPU usage alarm iscleared.

Value:Value range: 10-400Default value: 40

Server statusrefresh interval(seconds)

Description:Refresh interval for servermonitoring, that is, the CPUusage is sampled every xseconds.

Value:Value range: 2-60.Default value: 15.

ServerMonitorThresholdSettings

CPU used rate(%)

Description:Used to set Threshold forAlarm Generation,Threshold for AlarmClearance for the CPU usagealarm and whether to enablethe bubble.

Value:Value range: 1-99.Default value: 60.Offset value range:1-99. Default value:50.




Issue 10 (2010-09-06)


Memory used rate(%)

Used to set Threshold forAlarm Generation andThreshold for AlarmClearance for the memoryusage alarm.l If the memory usage is

larger than Threshold forAlarm Generation ofMemory used rate, theM2000 generates a highmemory usage alarm.

l If the memory usage issmaller than Thresholdfor Alarm Clearance ofMemory used rate, theM2000 generates analarm, prompting that thehigh memory usage alarmis cleared.

l When the function ofbubble information isenabled, if the server isfaulty, the system displaysa bubble information.


Table 6-2 describes the parameters for monitoring the disks of the server.

Table 6-2 Hard Disk Monitor


Disk MonitorParameter Settings

Hard disk statusrefresh interval(seconds)

Description:Refresh interval forhard diskmonitoring.

Value:Value range:60-3600Default value: 60



6-13


Disk MonitorThreshold Settings

Default value setting(%)

Description:All defaultthresholds of harddisk usage on theM2000 server.l When the hard

disk usage islarger thanThreshold forAlarmGeneration of analarm severitylevel, the M2000generates a highhard disk usagealarm of thisseverity level.

l When the harddisk usage issmaller thanThreshold forAlarmClearance of analarm severitylevel, the M2000clears the highhard disk usagealarm of thisseverity level.

l When the functionof bubbleinformation isenabled, if thehard disk is faulty,the systemdisplays a bubbleinformation.

Value:Value range: 1-99Default value:l Warning: 60

l Minor: 70

l Major: 80

l Critical: 90




Issue 10 (2010-09-06)


Advanced Setting(%)

Description:Thresholds of all thehard disk usage onthe M2000 server.l When the hard




NOTE

l If you selectDefault Value, theM2000 uses thethreshold specifiedin Default ValueSetting.

l If you selectCustomize Value,the M2000 usescustomizedthresholds ofalarms.

Value:Value range: 1-99



6-15

Table 6-3 describes the parameters for monitoring the database of the server.

Table 6-3 Database Monitor


Database MonitorParameter Settings

Database statusrefresh interval(seconds)

Description:Interval of databaserefreshing.


Database MonitorThreshold Settings

Default ValueSetting (%)

Description:All defaultthresholds ofdatabase usage on theM2000 server.l When the

database usage islarger thanThreshold of analarm severitylevel, the M2000generates a highdatabase usagealarm of thisseverity level.

l When thedatabase usage issmaller thanThreshold of analarm severitylevel, the M2000clears the highdatabase usagealarm of thisseverity level.


l Minor: 90

l Major: 95

l Critical: 98




Issue 10 (2010-09-06)


Advanced Setting(%)

Description:Thresholds for thedatabase usagealarms of differentseverities. You needto set thesethresholds separatelyfor each database onthe M2000 server.l When the



Setting method:Set the followingparameters for eachdatabase:l Default Value:

use defaultthresholds for thedatabase usagealarms of differentseverities.

l CustomizeValue: customizethresholds for thedatabase usagealarms of differentseverities.Value range:1-100Default value:– Warning: 85

– Minor: 90

– Major: 95

– Critical: 98

l DisabledMonitoring:Disable thedatabasemonitoring.

Table 6-4 describes the parameters for monitoring the server services.

Table 6-4 Service Monitor


Services MonitorParameter Settings

Service status refreshinterval (seconds)

Description:Interval of servicerefreshing.




6-17


Service MonitorScreen Tip Settings

Default Group Description:Set whether todisplay the servicestatus at the lowerright corner of theM2000 system

monitor client by

or .NOTE

l If all the monitoredservices are

running, isdisplayed.

l if a monitoredservice is stopped,

is displayed.

l You can double-

click or toaccess the ServiceMonitor tab.

Setting method:Select a service fromthe Service Namedrop-down list.Select enable ordisable in thecorresponding ShowScreen Tips drop-down list.

Step 3 Click OK.

----End

6.2 Querying the System Logs of the M2000This section introduces the M2000 system log. System logs record the operation of theM2000 system. System logs also record the files and data tables of various types of information,which can be queried by the M2000 administrator.



Contextl Querying the system logs requires only a few system resources and does not affect the

system operation.

l 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




Issue 10 (2010-09-06)

If the log data in the database exceeds a preset threshold, the system exports the log datato 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 SystemLogs 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 operationor 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 FilesWhen the M2000 system fails, you can run the diagnostic tool to collect all the related diagnosticinformation from the M2000 Server and Client through the FTP protocol. When the M2000client or server cannot run properly, you can collect all the operational information from theM2000 client or server to locate faults.

ContextBy using this information, you can locate faults. The collected information includes:l Trace files on the client, for example, Client_DebugTrace.

l Java virtual machine thread stack and lock state in client, for example,Client_ThreadStackDump.txt

l 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 collectedbefore the NM log files)

l Core files on the server, for example, core.imapsvcd.0.21221.1170824184.stack

l File of alarm NE synchronization number, for example, FMSyncNo

l The pstack file, for example, imap_stacks.20070207.155817.trace.



6-19

l Information about the Sybase, for example, SybaseConfig.zip, SybaseVersion.zip, andSYBLog.20070206.171040.zip.

By default, the collected files are saved in M2000 client\client\diagnosis\collected files. Youcan change the save path.

l The information collection progress is displayed in the Collection Details area of the LogInformation Collector window.

l The M2000 diagnostic tool automatically collects diagnostic information from the clientand 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 alist in the Port Select window. By performing this step, you can specify the client from whichthe diagnostic information is collected.

TIP

By comparing whether the process IDs in the PID column of the list with the progress ID of the targetclient, 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 displayedin the PID column.

Step 3 Configure the FTP server.1. Enter the IP address of the M2000 server.2. Enter the port number.3. 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 LogsParameters.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 informationwithin the specified time range.

l To collect alarm localization information, you need to enter the name of the NE whose alarmlocalization 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.




Issue 10 (2010-09-06)

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.l If you click Stop when collecting the diagnostic information from the M2000 server, the

diagnostic information about the server cannot be obtained.l To view the collected diagnostic information, you can click Browse to navigate the directory

of the collected files.

----End

6.4 Querying NE SubareasThis section describes how to query NE subareas. An NE subarea refers to the M2000 serverthat manages the NE. If the M2000 server adopts the SLS solution, NEs can be managed bydifferent servers (subareas). On the M2000 client, you can query different NE subareas.

PrerequisiteYou 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 theselected NE subarea are displayed. In the Statistic dialog box, the subarea information suchas host names, IP addresses, and database instance names are displayed.

l Querying NE subareas based on NE names: In the Query Result dialog box, the NEdistributions and NE information such as NE types, NE names, and NE versions on theselected NE subarea are displayed. In the Statistic dialog box, the subarea information suchas 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 PartitioningInformation.

----End

6.5 Managing the M2000 LicenseM2000 licenses can restrict the number of manageable devices, and the availability duration ofthe M2000. You need to manage the licenses periodically.

6.5.1 Querying the M2000 LicenseThis topic describes how to query the license file on the M2000 server through the M2000 client.

6.5.2 Updating the M2000 License



6-21

This section describes how to replace the M2000 license file on the M2000 server through theclient.


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 andfunctions on the Resource control item and Function control item tabs.

----End

6.5.2 Updating the M2000 LicenseThis section describes how to replace the M2000 license file on the M2000 server through theclient.

Prerequisite

When updating a license, delete the license files that are not in use from the server directorieslicense and licensebak, and then update the license.

Contextl The type of the license applied for must be consistent with the version type.

l Before the licenses expire, the M2000 displays a warning periodically.

l 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 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 clickOK.

----End

6.6 Check OMC statusOMC check is used to check the status of the M2000. This check also exports check reportsin .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.




Issue 10 (2010-09-06)

Prerequisitel You have logged in to the M2000 successfully.

l 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. In the Task Name field, enter the name of the task.2. 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 In the Start Time field, enter the start time.

l Click or to adjust the time.

l Click . In the displayed Date/Time Selection dialog box, set the start time.

NOTE

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 newdevice check task is displayed on the task list.

----End

6.7 Integrated Task ManagementThe M2000 provides the function of integrated management of scheduled tasks. Thus, you canbrowse information such as the task status and the progress. You can also create, modify, anddelete user-scheduled tasks. In addition, you can suspend, restore, cancel scheduled tasks, andsave task result files to the client.

6.7.1 Basic Knowledge



6-23

The integrated task management integrates the concepts such as types of integrated tasks, taskscheduling parameters, states of timing tasks. The knowledge of integrated task managementhelps you perform the operations related to the integrated task management.

6.7.2 Customizing the Interface for Managing Timing TasksThis describes how to customize the interface for managing timing tasks. The system can displaytiming tasks of the specified function type in the navigation tree or display the timing tasksmeeting the condition in the task list.

6.7.3 Creating a User Timing TaskThis section describes how to create a user timing task. Parameter setting varies according todifferent tasks.

6.7.4 Modifying a Timing TaskThis section describes how to modify the attributes of a user timing task or a system timing task.

6.7.5 Managing Timing TasksUser 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 TasksIn 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 ExecutionYou can view the last execution results of a timing task.

6.7.8 Downloading Result FilesThis describes how to download the results of timing tasks. You can save the results of timingtasks on the server to the local client in .txt format.

6.7.9 Technical Specifications of Centralized Task ManagementThe technical specifications of centralized task management refer to the limitations on thecentralized task management.

6.7.1 Basic KnowledgeThe integrated task management integrates the concepts such as types of integrated tasks, taskscheduling parameters, states of timing tasks. The knowledge of integrated task managementhelps you perform the operations related to the integrated task management.

Types of Integrated TasksThe M2000 divides timing tasks into different types according to execution periods, functions,and task features.

Tasks Grouped According to Execution PeriodsAccording to the execution periods of tasks, the M2000 divides the managed timing tasks intotwo types, that is, one-time tasks and periodic tasks. Table 6-5 provides the meaning of eachtask type.




Issue 10 (2010-09-06)

Table 6-5 Tasks grouped according to execution periods

Types of Integrated Tasks Description

Once Refers to a task that is performed only once at a specifictime.

Period Refers to a task that is performed periodically since aspecific time.

Tasks Grouped According to FunctionsAccording 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 Only BSC6000, BSC6900GSM, BSC6900UMTS, BSC6900GU, RNCs and NodeBs support CMEtasks. CME tasks are available only after you install the CME software that maps with the NE version.

l Network health check tasks are available only after you purchase and install the relevant components.

Table 6-6 Tasks grouped according to functions


Database capacity management The system periodically deletes the data that reaches thespecified Save Days from the database. Through databasecapacity management tasks, the database capability ismaintained in a proper range to avoid database faultscaused by large amount of data.By default, Save Days is set to the maximum value, thatis, 90. The custom value cannot exceed 90.The databases that can be managed consists of theoperation log database, system log database, security logmanagement database, NE operation log database, NEsecurity log database, alarm database, and performancedatabase.

File interface Various types of data can be periodically exported to aspecified directory on the server. Through this function,you can save the data outside the system. The exporteddata is still saved in the database.The exported data consists of performance data,configuration data, NE license allocation information, NEoperation logs, NE security logs, NE inventory data, alarmdata, network management operation logs, networkmanagement system logs, and network managementsecurity logs.



6-25


NIC NIC tasks provide NE data to the Nastar for performanceanalysis, configuration data query and check, uplinkinterference analysis, and neighboring cell analysis.l 2G/3G neighboring cells optimization: collecting

information about neighboring GSM cells foranalyzing the relation between neighboring 3G cells.

l CHR data collection: provides CHR data to the Nastarfor abnormal calls analysis.

l GSM MR data collection: provides MR data to theperformance analysis tool for network optimizationanalysis.

l NIC configuration export: provides NE configurationdata to the Nastar for NE configuration data query andcheck.

l RTWP data collection: provides NodeB interferencedata to the Nastar.

l Deamon collection: provides the Nastar with varioustypes of data, such as the interference data, co-channelneighboring cell optimization data, complaint handlingdata of CDMA networks and the co-channelneighboring cell optimization data and coverageanalysis data of UMTS networks.

l NE basic information export: provides NE basicinformation to the Nastar.

l Uplink frequency scanning: provides uplink frequencydata to the Nastar for uplink interference analysis.

l Neighboring cell optimization: Provides neighboringcell optimization data to the Nastar for neighboring cellanalysis.




Issue 10 (2010-09-06)


Others The other tasks consist of MML script tasks, PRS timingtasks, dual-home management tasks, alarm timingacknowledgement tasks, NE license sharing managementtasks, NE software timing download tasks, and HSL scripttasks .l MML script: After an MML script is configured, the

M2000 can issue the commands contained in the scriptin batches. You need not manually issue the commandsone by one.

l PRS timing task: You can set PRS timing tasks for theperformance tables that you require on the M2000. Theperformance data is collected periodically to generateperformance tables.

l Dual-home management: The system checks the dataof dual-home NE pairs periodically or on schedule sothat you can check whether the data is consistent. Thus,you can ensure that an softswitch can take over someor all data on the other softswitch after dual-homeswitchover.

l PM object synchronization: Maintains the dataconsistency between the PM objects on the M2000 andthe actual NE objects by synchronizing NE objectsregularly.

l Alarm timing acknowledgement: Helps you minimizeoperations by periodically acknowledging the faults orevent alarms that meet the user-defined conditions.

l NE software timing download: enables you to specifyan interval or the time to download NE mediationsoftware from the M2000 server to a specified NE. Inthis case, NE version files can be delivered to the NEon time.

l HSL script: By running the preset HSL scripts, you canperform operations such as modifying NE parametersand obtaining alarm data.

l NE upgrade log export: Exports NE upgrade logs to thespecified directory on the server periodically or onschedule.

l Upgrade Checking: After an NE is upgraded, you canuse this function to verify whether the NE issuccessfully upgraded by collecting some KPIs.

Synchronization Certain data may be missing due to reasons such ascommunication interruption. The synchronizationfunction enables the M2000 to obtain the latest data fromNEs. Through the synchronization function, the NEconfiguration data, NE logs, NE inventory data, and alarmtiming data can be synchronized.



6-27


Backup The M2000 allows you to save the server data and NE dataas backup files to a specified directory on the server. Thesaved system data and NE data can be used to restore thesystem and NEs in case of missing data or abnormality ofthe system and NEs. Backup tasks consist of NE timingbackups and server timing backups.The data that can be backed up on the M2000 consists ofconfiguration data and log data. The system files andoperating system cannot be backed up.

Report The file export function enables you to periodically exportvarious types of data as files to a specified directory of theserver. By using this function, you can save the dataoutside the system. The exported data is still saved in thedatabase.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 thetime to upload the data to the CME server. In this case,the CME can obtain the latest data of the NEs andconfigure the data.

l Cell Parameters Compare: compares the parameters inthe Current area with the default parameters in the CMEconfiguration template and then exports the results tothe specified path.

l Cell Consistency Check: checks that the data in theCurrent area complies with the selected check rules.Currently, both unidirectional neighboring cell checkrules and cell consistency check rules are provided.

l Current Area Export: exports the data in the Currentarea for Northbound to facilitate you manage theCurrent area.

Network health check The network health check task checks the status of NEdevices and the M2000, the performance of NE devices,and the alarm information. The health check report isgenerated in .html format.Through the network health check, you can detect thehidden problems of devices in time. Thus, severeaccidents are avoided and proper operation of currentdevices is ensured.For details, see the Help related to network health check.




Issue 10 (2010-09-06)

Tasks Grouped According to Task FeaturesAccording to different task features, the M2000 divides the managed tasks into two types, thatis, 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


System timing tasks System timing tasks are the tasks required for the normaloperation of the M2000 system. They consist of databasecapacity management tasks, NIC tasks, synchronizationtasks, file interface tasks, alarm timing acknowledgementtasks, and backup tasks (excluding NE backup tasks). Fordetails, see System Timing Tasks.

User timing task User timing tasks are the user-defined tasks created to meetthe requirements of network maintenance. User timing tasksconsist of MML script tasks, PRS timing tasks, uplinkfrequency scanning tasks, dual-home management tasks,NE software timing download tasks, NE timing backuptasks, configuration report export tasks, HSL script tasks,NE upgrade log export tasks, neighboring cell optimizationtasks, CME tasks, and network health check tasks. Fordetails, see User Timing Tasks.

System Timing TasksA system timing task is created during the installation or upgrade of the M2000 system. TheCreator of a system timing task is omc. System timing tasks consist of database capacitymanagement tasks, some NIC tasks, synchronization tasks, file interface tasks, alarm timingacknowledgement tasks, and backup tasks (excluding NE backup tasks).

The M2000 uses to identify system timing tasks.

NOTE

l Only users in the administrator group can manage and view system timing tasks.

l System timing tasks cannot be copied. Only some parameters of system timing tasks can be modified.These parameters, however, cannot be deleted.

l System timing tasks consist of multiple types of tasks. Database capacity management tasks cannotbe 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 Task Name Remarks

Database capacitymanagement

Performance data For details, see 6.8.12 Parameters forModifying Database Capacity.

NE operation logs



6-29


NE security logs

Alarm data

NM Operation LogDump

NM System LogDump

NM Security LogDump

File interface Performance dataexport

For details, see 6.8.13 Parameters forModifying File interface Task and 6.8.11Parameters for Setting the CommonInformation About Timing Tasks.Configuration data

export

NodeB License DataExport

NE operation logexport

NE system log export

NE security log export

NE inventory dataexport

Alarm data export

NM Operation LogExport

NM System LogExport

NM Security LogExport

NIC CHR data collection For details, see Modifying a CHR DataCollection Task.

EAM export For details, see 6.8.15 Parameters forModifying NE Basic Information ExportTask.

NIC configurationexport

For details, see Parameters for Modifying theExport of NIC CMExport Data.

Others Alarm timingacknowledgement

For details, see 6.8.16 Parameters forModifying Alarm TimingAcknowledgement.




Issue 10 (2010-09-06)


Performance objectsynchronization

For details, see 6.8.11 Parameters for Settingthe Common Information About TimingTasks.

Synchronization NE configuration datasynchronization

For details, see 6.8.14 Parameters forModifying Synchronization task and 6.8.11Parameters for Setting the CommonInformation About Timing Tasks.NE log

synchronization

NE inventory datasynchronization

Alarm timingsynchronization

NE upgrade logsynchronization

Maintance Modesynchronization

Backup Server timing backup For details, see 6.8.17 Parameters forModifying Data Backup Task.

User Timing TasksA 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 scanningtasks, dual-home management tasks, NE software timing download tasks, NE timing backuptasks, configuration report export tasks, iSStar script tasks, neighboring cell optimization tasks,CME tasks, and network health check tasks.

l You can create, modify, delete, copy, suspend, or restore user timing tasks.

l The M2000 uses to identify user timing tasks.

For details about user timing tasks, see Table 6-9.

NOTE

l Only BSC6000, BSC6900GSM, BSC6900UMTS, BSC6900GU, RNCs and NodeBs support CMEtasks. CME tasks are available only after you install the CME software that maps with the NE version.

l Network health check tasks are available only after you purchase and install the relevant components.



6-31

Table 6-9 Description of user timing tasks

TaskType

Task Name Description Remarks

Backup NE timingbackup

To store NE data, you canregularly save NE data as backupfiles to a specified directory onthe server. Thus, data loss can beavoided. After any error occurson NEs, you can restore the dataof NEs. You can back up all NEson the entire network, the NEs ofa certain type, or only some NEs.

For details, see 6.8.17Parameters forModifying Data BackupTask.

Report RAN reportexport

You can set the RAN reportexport task on the M2000 toexport the RAN report of aspecified NE to a specifieddirectory on the server.

For details, see 6.8.19Parameters for Creating/Modifying/Copying RANReport Task.

NIC Uplinkfrequencyscanning task

Provides uplink frequency data tothe Nastar for uplink interferenceanalysis.

For details, see Parametersfor Creating a Task ofCollecting the UplinkARFCN Data.

Neighboringcelloptimization

Provides neighboring celloptimization data to the Nastarfor neighboring cell analysis.

For details, see Creating aData Collection Task forNeighbor CellOptimization.

Others MML script You can run an MML scriptbased on the interval or based onthe time to issue commands in thescript in batches. Thus, you neednot manually issue thecommands one by one.

For details, see 6.8.18Parameters for Creating/Modifying/CopyingMML Command Script.

PRS timingtask

You can set PRS timing tasks forthe performance tables that yourequire on the M2000. Theperformance data is collectedperiodically to generateperformance tables.

For details, see 6.8.20Parameters for Creating,Viewing, or Modifying aScheduled Report Task.

NE softwaretimingdownload

After you set a specified intervalor a time to download NEmediation software from theM2000 server to specified NEs,NE versions can be delivered toNEs in time.

For details, see 6.8.23Parameters for Creating/Modifying/CopyingSoftware Download.




Issue 10 (2010-09-06)

TaskType


Dual-homemanagementtask

The system checks the data ofdual home pair NE periodicallyor on schedule so that you candetermine whether the data isconsistent. Thus, you can ensurethat an softswitch can take oversome or all data on the othersoftswitch.

For details, see 6.8.24Parameters for Creating/Modifying/CopyingDual-HomeManagement.

iSStar scripttask

By running the preset HSLscripts, you can performoperations such as modifying NEparameters and obtaining alarmdata.

For details, see 6.8.25Parameters for Creating/Modifying/CopyingiSStar Script.

UpgradeChecking

After an NE is upgraded, you canuse this function to verifywhether the NE is successfullyupgraded by collecting someKPIs.

For details, see Parametersfor Creating an NEUpgrade VerificationTask.

Fileinterface

NE upgrade logexport

Exports NE upgrade logs to thespecified directory of the serverperiodically or on schedule.

For details, see 6.8.26Parameters for Creating/Modifying/Copying theExport of NE UpgradeLog.

CME CME Upload After you set a specified intervalor a time to upload the selectedNE configuration data to theCME server side, the CME canobtain the latest NE data for dataconfiguration. Only RNCs andNodeBs support CME uploadtasks.

For details, see 6.8.27Parameters for Creating/Modifying/Copying aCME Upload Task.

CellParametersCompare

Compares the parameters in theCurrent area with the defaultparameters in the CMEconfiguration template and thenexports the results to the specifiedpath.

For details, see 6.8.28Parameters for Creating/Modifying/Copying CellParameters CompareTask.

CellConsistencyCheck

Checks that the data in theCurrent area complies with theselected check rules. Currently,both unidirectional neighboringcell check rules and cellconsistency check rules areprovided.

For details, see 6.8.29Parameters for Creating/Modifying/Copying CellConsistency Check Task.



6-33

TaskType


Current AreaExport

Exports the data in the Currentarea for Northbound to help youmanage the Current area.

For details, see 6.8.30Parameters for Creating/Modifying/Copying aCME Current AreaExport Task.

Network health check The network health checkenables you to check the NEdevice, check alarms, checkperformance, and compare resultfiles. The network health checkenables you to find the hiddenproblems of devices. Thus,severe accidents are avoided andproper operation of currentdevices is ensured.For details, see the Help relatedto network health check.

For details, see the Helprelated to network healthcheck.

Task Scheduling ParametersThe task scheduling parameters are the parameters related to the task execution type, task starttime, task execution period, and execution times.

Table 6-10 describes the task scheduling parameters.

Table 6-10 Description of the task description parameters

Parameter Description

Task Type According to different task execution periods, the M2000 divides theexecution types of the managed timing tasks into two types: periodicexecution and one-time execution. The execution type of the systemtiming tasks is periodic execution. The execution type of user timingtasks can be periodic execution or one-time execution.

Start Time Indicates start time of periodic tasks and one-time tasks set duringtask creation, including date and time. The start time of tasks shouldbe later than the current server time.

Period l Interval between periodic tasks. It has two enlistments: unit andduration.

l The task execution period can be represented by month, week, day,hour, and minute. Second is not supported.

l The period interval range is as follows: 1 to 12 for month, 1 to 52for week, 1 to 366 for day, 1 to 366x24 for hour and 1 to 366x24x60for minute.




Issue 10 (2010-09-06)


Run Times Indicates execution times of a periodic task. The execution timesrange 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 Execution type = Periodicity

l Start time = 2006-10-21 09:07:28

l Execution period = 1 day

l Period execution times = 0

The preceding information indicates that the system executes the entire network NE backup task at 09:07:28every day from 09:07:28 on Oct. 21, 2006.

States of a Timing TaskA 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

Idle

AnotherScheduling?

CancelScheduling

Finish

No

Yes

Scheduling

Del

etin

g a

timin

g ta

sk

Deletin

g

a tim

ing ta

sk

Sus

pend

a ti

min

g ta

skR

esto

re a

tim

ing

task

Creating a timing task

Deleting a timing task

Suspend

Archived

Finished

Running

Term

inat

e a

CM

E ta

sk

Terminate a CME task

Term

inat

e a

CM

E ta

sk

Delete

a CME task

Start

End

State transition of a scheduled task is as follows:l A scheduled task is in the idle state after it is initially created.



6-35

l An idle task is changed to the running state after being scheduled.

l An idle task is changed to the suspended state after being suspended.

l A running task is changed to the idle state after being cancelled.

l A suspended task is changed to the idle state after being resumed.

l If a task need not be scheduled after being performed, it is in the finished state. If it needsto 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 archivingstate.

When a timing task is in the idle, suspended, or finished state and a CME task is in the archivingstate, you can delete the timing task.

6.7.2 Customizing the Interface for Managing Timing TasksThis describes how to customize the interface for managing timing tasks. The system can displaytiming tasks of the specified function type in the navigation tree or display the timing tasksmeeting the condition in the task list.

PrerequisiteYou 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 differentcustomized requirement.

Customized Requirement Operation

Customize the navigation tree 1. Right-click in the navigation tree and choose FilterType from the shortcut menu. The Filter Type dialog boxis displayed.

2. Select the timing task type to be displayed. By default, allthe timing task types that the current user is authorized tobrowse are displayed.

Customize the task list 1. Right-click the task list and select Filter Task. The TaskFilter Setting dialog box is displayed.

2. Set the User Name, Category, Task State, and Last RunResult as the filtering conditions. For detailed parameterdescription, refer to 6.8.10 Parameters for Setting TaskFilter Conditions.

Step 3 Click OK.

----End




Issue 10 (2010-09-06)

6.7.3 Creating a User Timing TaskThis section describes how to create a user timing task. Parameter setting varies according todifferent tasks.

PrerequisiteYou have logged in to the M2000 client successfully.

Contextl To quickly create a task, you can copy a multi-instance user timing task of user and then

modify its parameters.l 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 orcopy a timing task of this type.

Procedure


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 In general, click New.

l To quickly create a task of the specified type, double-click a user timing task in the TaskType navigation tree.

l To quickly create a multi-instance user timing task whose parameter settings are similar tothose of the specified task, select the specified multi-instance user timing task, and then clickCopy.

NOTE

l If the Copy button is gray, it indicates that the user timing task does not support multiple instances orthe number of instances reaches the maximum.

l When you create a task, the task types for which the number of user timing task instances reaches themaximum 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 Description

Parameter Setting



6-37

Option Description

CommonParameters

1. Set Task Name, Task Type, and Run Type. Do as follows:l Task Name: Enter the task name in Task Name.

l Task Type: Select the type of the task to be created in the Task Typenavigation tree.

l 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 oftheir task types.

2. Click Next.3. Set Start Time and Period Setting. Do as follows:l Start Time: In the Time Setting area, set Start Time.

l Period Setting: In the Period Setting area, set Period and RunTimes.

NOTE

l For a one-time task, you can select Run at Once. After the task is created, it runsat once.

l For a periodic task, you need to set the parameters in the Period Setting area.

ExtendedParameters

Set extended parameters according to the task requirements.

Step 4 Click Finish.

The created user timing task is displayed in the task list.

----End

6.7.4 Modifying a Timing TaskThis section describes how to modify the attributes of a user timing task or a system timing task.

PrerequisiteYou have logged in to the M2000 client successfully.

ContextTiming tasks are classified into System Timing Tasks and User Timing Tasks.

Procedure


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:

NOTEParameter modification varies according to the task type.




Issue 10 (2010-09-06)

l Select a task from the task list, and then click Attribute. In the Attribute dialog box, modifycommon and extended parameters.

l Double-click a task in the task list. In the displayed Attribute dialog box, modify commonand extended parameters.

Step 3 Click Finish.

----End

6.7.5 Managing Timing TasksUser 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 issuspended, it is changed to the suspended state.


l At least one idle timing task exists.

ContextThe M2000 can execute the tasks that are not suspended only through scheduling.

Procedure


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 theConfirm dialog box, click Yes.

l Automatic suspending

Select a task in the task list. Right-click the task and select Timely Suspend/Resume. In theTimely Suspend/Resume dialog box, select Suspend Time and then specify the time. ClickOK.

----End

Resuming Timing Tasks

You can resume a suspended task. After that, the task becomes idle and is ready to be dispatchedby the system.



6-39


l At least one suspended scheduled task exists.

ContextOnly idle tasks can wait to be used.

Procedure



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 selectResume. In the Confirm dialog box, click Yes.

l Automatic resumingSelect 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 specifythe time. Click OK.

----End

Setting Time of Timing TasksYou can set an automatic suspend time or an automatic restore time for a scheduled task. In thissituation, the M2000 automatically suspends the task or restores the task.


l At least one suspended or idle timing task exists.

Contextl 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.l 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 specifiedtime, it fails to be suspended.

l You are not allowed to set auto-suspend or resume a Running timing task.

Procedure


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.




Issue 10 (2010-09-06)

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 ResumeTime 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.31Parameters for Setting Time of Timing Tasks.

----End

Cancelling Timing TasksYou can cancel a running task. The task status is changed to idle after being cancelled.


l At least one Running timing task exists.

ContextA user in the common user group can cancel only the tasks created by himself. A admin cancancel the timing tasks created by all users.

Procedure



Step 3 Select one or more running tasks in the task list in the right pane. Right-click the task and selectCancel.

Step 4 In the Confirm dialog box, click Yes.Then the status of the task is changed from running to idle.

----End

Deleting Timing TasksYou can delete the tasks created by yourself according to the actual requirements to save systemresources.


l At least one timing task exists.

Contextl Users can delete only the tasks created by themselves. The admin can delete the tasks

created by all users.l System tasks cannot be deleted.



6-41

l Running tasks cannot be deleted.

l You can delete only an Archived CME download task.

Procedure



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



Procedure



NOTE

l The task list area on the right displays the information about the tasks that can be viewed by the currentuser.

l 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 ExtendedParameter tab, you can view the task details.

NOTE

l If State of a task is Finished, you can view the task information only.

l If State of a task is Idle, Suspend, or Running, you can modify the task details in the Attribute dialogbox.

----End

6.7.7 Viewing the Task ExecutionYou can view the last execution results of a timing task.




Issue 10 (2010-09-06)



Contextl During the creation of CME tasks, sub-tasks are created, which are executed in different

phases.l You can browse the execution progress of subtasks of CME tasks.

Procedure


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.l You can check the result details in the Result Info area.

----End

6.7.8 Downloading Result FilesThis describes how to download the results of timing tasks. You can save the results of timingtasks on the server to the local client in .txt format.


l The timing task that is used for downloading the result files exists and it is run for at leastonce.

ContextThe 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 Allowable Operation

CME and iSStar ScriptExecutor task

The task result are saved on the server in logs. The Result Info areadisplays only the information about the last task execution. Theresult logs are not displayed.You can download all the result files to the local client. Result filesof multiple tasks can be downloaded concurrently.

MML Script task You can download the latest result file to the local client. Resultfiles of multiple tasks can be downloaded concurrently.

Network Health Checktask

You can download the result file of the selected task. Result filesof multiple tasks can be downloaded concurrently.



6-43

Task Type Allowable Operation

Dual HomeManagement task

You can view the latest consistency check result on line.

Timing task, NESoftware Downloadtask, and NE Backuptask

If a task is performed at least once, you can save the messages inthe Result Info area to a local path.

Procedure


Step 2 In the navigation tree, select the type of the task that is used to download the result files. Selectthe specific tasks in the right pane.

Step 3 Perform the following operations according to the task type.

Task Type Procedure

CME or iSStar Script Executor task 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 path3. Click OK.

NOTEThe system generates a folder for the log file generatedeach time and saves the folder to the specified path.The result log file is named in the format YYYY-MM-DD_HH-MM-SS, for example,2008-04-18_10-27-53.




Issue 10 (2010-09-06)

Task Type Procedure

MML Script task To download the result files of a single task, do asfollows: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, youcan right-click the Result Info field and chooseSave AS on the shortcut menu.

3. Set the save path in the displayed Save dialogbox, and then click Save.

To download the result files of multiple tasks, do asfollows: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 executionresults of multiple MML script tasks to the samefile.

Network Health Check task 1. Select the task whose result files you plan todownload.

2. Right-click a task and choose NHC Report onthe shortcut menu.

3. In the displayed NHC Report dialog box, selectthe check report based on Report Nameand thenclick Save.NOTE

You can click Open to view the contents of the checkreport and decide whether the report needs to bedownloaded.

4. Set the save path in the displayed Please selecta directory dialog box.

5. Click OK.

Dual Home Management task Right-click a task and choose Checked Resultfrom the shortcut menu.NOTE

If data inconsistency exists, you need to generate a scriptto adjust the data difference and synchronize the data.



6-45

Task Type Procedure

Timing task, NE Software Downloadtask, and NE Backup task

To download the result information about adownload 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 ManagementThe technical specifications of centralized task management refer to the limitations on thecentralized task management.

Function Specification Value

Centralizedtask interface

Maximum size of theexecution results ofMML tasks can bedisplayed on theM2000 client(MBytes).

2

Maximum size ofscript files uploadedfor MML tasks(MBytes).

1

User task Maximum number ofscheduled NE backuptasks

50

Maximum number oftasks configured withMML scripts(including the dual-home consistencycheck task)

50

Maximum number ofscheduled softwaredownload tasks

50

Maximum number ofiSStar script tasks

500

Maximum number ofCME upload tasks

50




Issue 10 (2010-09-06)

Function Specification Value

Maximum number ofCME download tasks

50

Maximum number ofdual-homemanagement tasks

50

Maximum number ofTMO configurationimport tasks

100

6.8 Reference of the OSS Management GUIThis part describes the OSS management interfaces and related information such as theparameters used in the OSS management. This helps you understand the functions of OSSmanagement easily.

6.8.1 Interface Description: Managing Timing TasksThis section describes the Task Management interface and relevant parameters, which helpsyou perform the related operations.

6.8.2 Interface Description: M2000 Log Information CollectorWhen the log information collector on the M2000 client or server is faulty, you can collect allrelated log files through FTP from the M2000 client or server to locate faults.

6.8.3 Parameters for the NE Partitioning InformationThis topic describes the related parameters in the Query NE Subarea dialog box. You can referto the these parameters when you check the NE partitioning information.

6.8.4 Parameters for Querying the M2000 LicenseThis section describes the parameters in the License Information dialog box. You can refer tothese parameters when you view M2000 licenses information.

6.8.5 Parameters for Setting Monitoring Parameters of the M2000 ServerThis section describes the parameters of system monitor settings. You can use these parameterswhen you set the server thresholds.

6.8.6 Parameters for Monitoring the M2000 Server Service StatusThis 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 StatusThis 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 StatusThis section describes the parameters of the query result displayed in the Hard Disk Monitortab. You can use these parameters when you monitor the M2000 server hard disk status.

6.8.9 Parameters for Monitoring the M2000 Server Database StatusThis section describes the parameters of the query result displayed in the Database Monitortab. You can use these parameters when you monitor the M2000 server database status.



6-47

6.8.10 Parameters for Setting Task Filter ConditionsThis section describes the parameters in the Task Filter Setting dialog box. When you set filterconditions for a task list, you can refer to this section.

6.8.11 Parameters for Setting the Common Information About Timing TasksThis 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 CapacityThis section describes the parameters of database capacity management tasks. When modifyingdatabase management tasks, you can set the parameters by referring to the information describedin this section.

6.8.13 Parameters for Modifying File interface TaskThis 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 taskThis section describes the parameters of Synchronization task. When modifying Synchronizationtask, you can set the parameters by referring to the information described in this section.

6.8.15 Parameters for Modifying NE Basic Information Export TaskThis section describes the parameters involved in the NE basic information export task. Whenmodifying an NE basic information export task, you can refer to this part and perform relevantoperations.

6.8.16 Parameters for Modifying Alarm Timing AcknowledgementThis part describes the parameters in the alarm acknowledgement. When modifying alarmacknowledgement, you can set the parameters in the alarm acknowledgement by referring to theinformation described in this section.

6.8.17 Parameters for Modifying Data Backup TaskThis 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 ScriptThis section describes the parameters of MML command script tasks. When creating ormodifying MML command script tasks, you can refer to this part.

6.8.19 Parameters for Creating/Modifying/Copying RAN Report TaskThis describes the parameters involved in the RAN report task. When creating, modifying, orcopying 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 TaskThis section describes the parameters for setting a scheduled report task. You can refer to thispart when you create, query, or modify a scheduled task.

6.8.21 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top PowerThis section describes the parameters of a task for testing BTS cabinet-top power. You can referto this section when creating or modifying such a task.

6.8.22 Parameters for Creating/Modifying/Copying an RSSI Test TaskThis section describes the parameters of an RSSI test task. You can refer to this section whencreating or modifying an RSSI test task.

6.8.23 Parameters for Creating/Modifying/Copying Software Download




Issue 10 (2010-09-06)

This section describes the parameters in the software download task. When creating or modifyingsoftware download task, you can set the parameters for software download task by referring theinformation described in this section.

6.8.24 Parameters for Creating/Modifying/Copying Dual-Home ManagementThis describes the parameters used in dual-homing management. You can refer to theseparameters when creating, modifying, or copying dual-home management.

6.8.25 Parameters for Creating/Modifying/Copying iSStar ScriptThis section describes the parameters in the iSStar script task. When creating or modifying iSStarscripts, you can set the parameters in the iSStar tasks by referring to the information describedin this section.

6.8.26 Parameters for Creating/Modifying/Copying the Export of NE Upgrade LogThis describes the parameters for exporting NE logs and can be taken as reference during theparameter modification.

6.8.27 Parameters for Creating/Modifying/Copying a CME Upload TaskThis describes the parameters of a CME upload task. When creating or modifying a CME uploadtask, you can refer to the parameter description and perform relevant operations.

6.8.28 Parameters for Creating/Modifying/Copying Cell Parameters Compare TaskThis describes the parameters involved in the CME cell algorithm comparison task. Whencreating or modifying a CME cell algorithm comparison task, you can refer to this part andperform relevant operations.

6.8.29 Parameters for Creating/Modifying/Copying Cell Consistency Check TaskThis describes the parameters involved in the CME cell consistency check task. When creatingor modifying a CME cell consistency check task, you can refer to this part and perform relevantoperations.

6.8.30 Parameters for Creating/Modifying/Copying a CME Current Area Export TaskThis describes the parameters of CME Current Area Export tasks. When creating or modifyinga CME Current Area Export task, you can refer to the information described in this part.

6.8.31 Parameters for Setting Time of Timing TasksThis section describes the parameters of time for automatic suspending and automatic resumingtiming tasks

6.8.32 Parameters for Selecting Objects for Device CheckThis part describes the extended parameters for selecting objects for device check. You can referto this part when creating device check tasks.

6.8.33 Parameters for Collecting NM Logs ParametersThis describes the parameters of the M2000 log information collecting tool dialog box. Whencollecting NMS log files, refer to the information described here for parameter setting.

6.8.1 Interface Description: Managing Timing TasksThis section describes the Task Management interface and relevant parameters, which helpsyou perform the related operations.

After you log in to the server, the Timing Task Management interface is displayed, as shown inFigure 6-8. Table 6-12 describes each element displayed in Figure 6-8.



6-49

Figure 6-8 Timing Task Management interface

Table 6-12 Description of the Timing Task Management interface

No. Name Description

(1) Navigation tree You can precisely locate a timing taskthrough the navigation tree.

(2) Task result informationpanel

After a task is carried out, the task result isdisplayed. On the task result informationpanel, you can browse the result of the tasklast carried out. Only the result of thecurrently selected task is displayed on thetask result information panel. If multipletasks are selected in the task list, only theresult of the firstly selected task isdisplayed.

(3) Button panel The buttons used for carrying out centraltask management are available on thebutton panel.

(4) Task list You can browse the timing tasks that existon the server side and the detailedinformation. In the task list, different colorsare used to indicate different states of tasks:Gray: complete; Orange: suspended;Blue: active; White: idle. The selectedcolor of the task is darker than the previouscolor of the task.




Issue 10 (2010-09-06)

6.8.2 Interface Description: M2000 Log Information CollectorWhen the log information collector on the M2000 client or server is faulty, you can collect allrelated 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.l 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 Timeof a specific time segment. To collect the alarm location information, enter an NE name inNE Name.

l Directory: This area shows the path for saving the diagnosis information. You can changethe path.

l Collected Information Details: In this area, you can view the information collectionprocess and progress.

Figure 6-9 shows the interface.

Figure 6-9 M2000 Log Information Collector interface

6.8.3 Parameters for the NE Partitioning InformationThis topic describes the related parameters in the Query NE Subarea dialog box. You can referto the these parameters when you check the NE partitioning information.



6-51



Query Condition NE Subarea Host Name of the NE Partitioning When youquery the specific partitioning information,you can select names of all partitions or thename of a specific partition from the drop-down list.

NE Name indicates the NE Name.

Query Result No. indicates the serial number of the NE.

NE Name indicates the NE Name.

NE Version indicates the version of the NE.

Number of NEs indicates the number of the NEs that belong tothe NE Partitioning.

Statistic indicates the partitioning information aboutthe NE, including the IP address and theinstance name of the database.

6.8.4 Parameters for Querying the M2000 LicenseThis section describes the parameters in the License Information dialog box. You can refer tothese parameters when you view M2000 licenses information.

Parameters for Resource Control Item Tab


License name 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 afteryou click Server ID




Issue 10 (2010-09-06)


Update License Description:Click the button to update license.

Parameters for Function Control Item Parameters Tab


License name Description:Names of authorization items.

License capacity Description:Number of the license of the devices authorized to bemanaged.

6.8.5 Parameters for Setting Monitoring Parameters of the M2000Server

This section describes the parameters of system monitor settings. You can use these parameterswhen you set the server thresholds.

Parameters











6-53






CPU used rate(%)



Memory used rate(%)















Issue 10 (2010-09-06)









l Minor: 70

l Major: 80

l Critical: 90



6-55


Advanced Setting(%)





NOTE







Issue 10 (2010-09-06)













l Minor: 90

l Major: 95

l Critical: 98



6-57


Advanced Setting(%)







– Minor: 90

– Major: 95

– Critical: 98











Issue 10 (2010-09-06)




monitor client by

or .NOTE




is displayed.

l You can double-



6.8.6 Parameters for Monitoring the M2000 Server Service StatusThis 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

ParametersName Description

Service Name 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.



6-59

Name Description

Startup Mode Description:Service start mode, including Automatic, Manual, andDisable. The Disable mode is available only for stoppedservices.

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 StatusThis 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 Description

Process Name 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 StatusThis section describes the parameters of the query result displayed in the Hard Disk Monitortab. You can use these parameters when you monitor the M2000 server hard disk status.




Issue 10 (2010-09-06)


File System Description:Hard disk partitions and their paths.

Total Size(MB) Description:Total space of a specific partition, equals to the sum of UsedSize 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 andabnormal. 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 StatusThis section describes the parameters of the query result displayed in the Database Monitortab. You can use these parameters when you monitor the M2000 server database status.


Database Name 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.



6-61

Name Description

Data Space Usage (%) Description:Usage rate of the used data space and total data space.NOTE

The Oracle database occupies the table space in a greedymanner. The high-water mark determines the used andunused blocks in a segment. The high-water mark increasesafter data is added, but does not decrease after data is deleted.The M2000 calculates the Oracle data usage by monitoringthe high-water mark. Therefore, the Oracle data usagemonitored by the M2000 does not decrease after datadeletion.

Total Log Space (MB) Description:It refers to the space allocated to each database log ofthe M2000.

Free Log Space (MB) Description:It refers to the unused disk space allocated to databaselogs.

Log Space Usage (%) Description:It is calculated by the following formula: Log UsedRate = (Total Log Space - Free Log Space)/Total LogSpace x 100%.

Status Description:Database status, including normal and abnormal. If thedatabase usage is more than or equal to the threshold,the system displays Abnormal.

6.8.10 Parameters for Setting Task Filter ConditionsThis section describes the parameters in the Task Filter Setting dialog box. When you set filterconditions for a task list, you can refer to this section.

ParametersParameter Description

UserName

Current User Description:Indicates the user that operates the client.

Other Users Description:Indicates other users except the current user.

Category

User Task Description:Indicates the task created by users.




Issue 10 (2010-09-06)


System Task Description:Indicates the task created by OMC during the system installationor 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. Onlywhen the task is in the archived state, the task can be deleted.

LastRunResult

Success Description:Indicates that the task is successfully carried out.

Processing Description:Indicates that the task is being processed by the system.

PartlySuccess

Description:Indicates that the task is partly successfully carried out.

Failed Description:Indicates that the task fails to carry out.

Miss RunTime

Description:Indicates that the task misses the previous performed time. If theserver is not running properly or the task is suspended before theexecution, the task may miss the previous execution.

Unknown Description:Indicates that the previous execution result in the server is lost dueto improper service or sudden power cut. Thus, after recovery, theprevious execution result cannot be determined.



6-63

6.8.11 Parameters for Setting the Common Information AboutTiming 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 Description Settings

Task Name Description:Refers to the name of a timing task.

Value:l A maximum of 60 characters

l Unique and not null

l Case sensitive

Run Type Description:l Once: If you select this option,

the system runs the created taskonce at the defined time point.

l Period: If you select this option,the system runs the created taskperiodically.

Value:l Once

l Period

Start time Description:This parameter sets the time forstarting a task.

Value:The start time should be later thanthe time displayed on the server.NOTE

For a one-time timing task, if you haveselected Run At Once, the StartTime parameter is invalid. The task isperformed immediately after therelated settings are complete.

Task Type Description:

Refers to the type of a timing task.

-




Issue 10 (2010-09-06)

Parameter Description Settings

Period Description:Interval between periodic tasks. Ithas two enlistments: unit andduration.

Value:l The period can be represented in

either of the following units:minutes, hours, days, weeks,months. The period, however,cannot be represented inseconds.

l The value range for periodshould be as follows: Minute (1- 366 x 24 x 60), Hour (1 - 366x 24), Day (1 - 366), Week (1 -52), Month (1 - 12).

Run Times Description:This parameter indicates the timesthat a periodic task is executed.

Value:0 - 65535NOTE

l 0 indicates that the number of timesfor executing periodic tasks is notrestricted.

l This parameter is displayed in theAttribute dialog box only afteryou set it when creating andcopying a periodic task.

6.8.12 Parameters for Modifying Database CapacityThis section describes the parameters of database capacity management tasks. When modifyingdatabase management tasks, you can set the parameters by referring to the information describedin this section.

Parameter Descriptionl Parameters of Alarm Database Capacity Management Tasks

l Parameters of Performance Database Capacity Management Tasks

l Parameters of NE Log Database Capacity Management Tasks

l Parameters of M2000 Log Database Capacity Management Tasks

Table 6-18 Parameters of alarm database capacity management tasks

Parameter Value Range Description

Compress FileAfter Export

Selected from thedrop-down list

When the data in the database expires, thesystem can choose whether to compress filesafter the export. You can select either Yes orNo in this field. Yes is selected by default.



6-65


File Format Selected from thedrop-down list

Refers to the format of the file that saves theexported data. Alarm database capacitymanagement tasks support .txt, .csv, .html,and .xml files.

Save File Path None. Refers to the path for saving exported data. Thesave path is specified by the server and cannotbe modified. Alarm database capacitymanagement tasks: /export/home/omc/var/ThresholdExport/FM.

Hold Days in theDatabase

Unit: dayValue range: 1-90

Refers to the storage duration of data in thedatabase. The default storage duration is 90days.

File Size Unit: MBDefault value: 1,024Value range: 200-2048

Refers to the upper threshold of the file dumpspace. When you export files, the earliestdumped files are replaced if the total size of thefiles in the specified path exceeds the presetupper threshold.NOTE

When setting the upper threshold of dump space,you need to task the space of the partition to whichthe save path of files belongs into consideration. Theset upper threshold cannot exceed the size of thepartition.

File Hold Days Unit: dayDefault value: 15Value range: 3-30

Refers to the storage duration of dumped files.The system automatically deletes the fileswhose storage duration exceeds the presetdays.

File Sum Number of filesDefault value: 1,000Value range: 200-2000

Refers to the upper threshold of the files in thefile dump space. When you export files, theearliest dumped files are replaced if the totalnumber of the files in the specified pathexceeds the preset upper threshold.

Table 6-19 Parameters of performance database capacity management tasks


Export Data Selected from thedrop-down list

If you select No, the system automaticallydeletes the expired performance data, and theparameters related to file export becomeinvalid. If you select Yes, the system exportsthe expired performance data according to thepreset file export parameters.




Issue 10 (2010-09-06)






Refers to the format of the file that saves theexported data. Performance database capacitymanagement tasks support .csv files.

Save File Path None. Refers to the path for saving exported data. Thesave path is specified by the server and cannotbe modified. Performance database capacitymanagement tasks: /export/home/omc/var/ThresholdExport/PM.











Hold DaysSetting

Select CommonMode orConfiguration Mode.

l Common Mode: You need to manuallyenter a value in Hold Days in theDatabase. The value range is 1-90. Thedefault value is 30.

l Configuration Mode: You need to specifyConfiguration File. The system uses thestorage duration specified in theconfiguration file.



6-67

Table 6-20 Parameters of NE log database capacity management tasks






Refers to the format of the file that saves theexported data. NE log database capacity taskssupport .txt and .csv files.

Save File Path None. Refers to the path for saving exported data. Thesave path is specified by the server and cannotbe modified. NE log database capacitymanagement tasks: /export/home/omc/var/ThresholdExport/NeLog.











Table 6-21 Parameters of M2000 log database capacity management tasks








Issue 10 (2010-09-06)



Refers to the format of the file that saves theexported data. M2000 log database capacitymanagement tasks support .xml and .csv files.

Save File Path None. Refers to the path for saving exported data. Thesave path is specified by the server and cannotbe modified. The M2000 log database capacitymanagement tasks: /export/home/omc/var/ThresholdExport/Log.











6.8.13 Parameters for Modifying File interface TaskThis 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.

Parameter Descriptionl Parameters for Modifying an Alarm Data Export Task

l Parameters for Modifying the Export of Performance Data

l Parameters for Modifying the Export of Inventory Data

l Parameters for Modifying the Export of NE Logs

l Parameters for Modifying the Export of M2000 Logs



6-69

l Parameters for Modifying the Export of Configuration Data

Table 6-22 Parameters for Modifying an Alarm Data Export Task

Parameter Description Value Range

File type Description:The format of theexported files.

Value:You can select the following file types:l CSV

l XML

l TXT

l HTML

Compressionformat

Description:l If you select zip or

gzip, it indicatesthatthe .csv, .xml, .txtor .html files aredecompressed andthen exported.

l If you select Notcompress, itindicates thatthe .csv, .xmlfile, .txt or .html isexported.

Value:You can select one of the following items.l Not compress

l zip

l gzip

Export To Description:The save path ofexported alarm data.

Value:The default value is used and cannot bechanged.The default path is /export/home/omc/var/fileint/fm/.

File prefix Description:Prefix of export filenames. Export files arenamed in the exportpath in the format ofprefix-export time-data type. Forexample, assume thatthe prefix is abc. Thegenerated file namesareabc-20090928104022-alarm-log-auto-1.zipandabc-20090928104022-event-log-auto-1.zip.

Value:The value contains 0-30 characters.




Issue 10 (2010-09-06)

Parameter Description Value Range

Export Mode ofAlarm Logs

Description:l Export all

unacknowledgedand unclearedalarms indicatesthat allunacknowledgedand unclearedalarms are exportedbased on the exportconditions.

l Exportincrementalalarms indicatesthat only the alarmsthat are generatedfrom the time of lastexport to now areexported based onthe same exportconditions. If thecurrent exportconditions aredifferent from theprevious exportconditions, allalarms that meet thecurrent conditionsare exported.

Value:-

Alarm Severity,Category, andType

Description:Select the severity,category, and type ofthe alarm to beexported.

Value:You can select the following values:l Alarm severities: critical, major, minor, and

warning.l Alarm categories: current alarm, event

alarm, history alarm, and shielded alarm.l Alarm types: Power system, Environment

system, Signaling system, Trunk system,Hardware system, Software system,Running system, Communication system,QoS, Processing error, Internal, Integrityviolation, Operational violation, Physicalviolation, Security service or mechanismviolation, Time domain violation.

Alarm Name Description:List the alarms that canbe exported currently.

Value:Select Alarm Name tab, and then click

to select the alarm name.



6-71

Table 6-23 Parameters for Modifying the Export of Performance Data


File Format You can choose:l CSV.

l XML.

l TXT.

Performance measurementresults are exported as a .csvor .xml file.

Hold Days Enter as required.The default value is 90.

The data of a task is deleted fromthe server after the storageduration expires.

File Path Default value. No change.The default path is /export/home/omc/var/fileint/pm/.

By default, the exported data issaved in the /export/home/omc/var/fileint/pm/ path. The defaultvalue cannot be changed.

Period You can click differentmeasurement period tabs.

You can set the measurementperiod for an export task byclicking different measurementperiod tabs.

Export Period Options in the drop-down list. This parameter is used to set theexecution period of an exporttask. The available values of thisparameter depend on the selectedNE type.NOTE

The export period and measurementperiod of performance data must beconsistent.

Delay Time The value must be multiples of 5minutes.Value range: 5 to 1440.The unit is minute.

The parameter specifies thedelay time for running a task.The value must be an integralmultiple of 5 minutes and shouldnot be null.




Issue 10 (2010-09-06)


Function Subsets You can select function subsetsfrom the navigation tree.

You can control the functionsubset navigation tree in the leftpane by selecting Show Been SetMeasuring Function Subsetsand Show All FunctionSubsets.In the navigation tree in the leftpane, you can select the functionsubset whose performancemeasurement results are to beexported and then click

or to add thefunction subset to the area on theright so that the performancemeasurement results of theselected function subset can beperiodically exported accordingto the task settings.

Template You can select templates fromthe navigation tree.

After a result query template isselected, query results areperiodically exported accordingto the settings of the template.CAUTION

l If the result query templateshaving the same name exist onone measurement period tabpage, and if the performancemeasurement results are to beexported by template nameaccording to the setting in theconfiguration file of the tool forexporting performancemeasurement results collectedby the M2000, the result files thatare exported on the basis of thetemplates sharing the same namewill replace each other when youselect a template sharing thesame name with other templates.To avoid file replacement, youneed to change the names of theresult query templates or modifythe setting in the configurationfile so that performancemeasurement results areexported by template ID.

l If the result query templateshaving the same template IDexist on one measurement periodtab page, only one displayed.



6-73


Filter Search None The system searches for resultsby the name of a function subset.The searching condition is caseinsensitive. In addition, the fuzzysearch is supported, whereas thewildcard search is not supported.

Table 6-24 Parameters for Modifying the Export of Inventory Data


File Format Exports the operation logs to a .txt file, csv file or .txt file.

File Path Indicates the path to save the exported inventory data.Default value: /export/home/omc/var/fileint/cm/InvtTimerExport.

All NE If you select this option, the system exports the inventory data ofall NEs on the network. This option is selected by default.

Please Select NE Indicates all the NEs in the entire network. Multiple NEs aresupported. You can select the specific NEs in Please Select NEonly after you deselect All NE.

Table 6-25 Parameters for Modifying the Export of NE Logs


File Format You can select .txt or .csv. Exports the operation logs to a .txtfile or .csv file.

File Path Default value: No change.The default path is: /export/home/omc/var/fileint/nelogs/.

Saves NE logs.

File Size Unit: MBDefault value: 1024

Refers to the threshold of thespace for dumping log files.During the export of log files, ifthe size of the files existing in thespecified path exceeds the presetthreshold, the earliest files arereplaced.NOTE

When setting the threshold of dumpspace, the size of the partition that thepath for saving log files belongs tomust be taken into account. Thethreshold cannot exceed the size ofthe partition.




Issue 10 (2010-09-06)


File Hold Days Unit: dayDefault value: 15

Refers to the number of the dayswithin which the dump files can besaved. After these days, the filesare automatically deleted.

File Sum Number of filesDefault value: 1000

Refers to the maximum number offiles in the dump space. During theexport of log files, if the numberof the files existing in the specifiedpath exceeds the preset threshold,the earliest files are replaced.

Table 6-26 Parameters for Modifying the Export of M2000 Logs


Compress ExportedFile

l Yes.

l No.

l If you select Yes, the .csv filesor .xml files are compressed toa packet and exported.

l If you select No, the .csv filesor .xml files are directlyexported.

Exported File Format You can select .csv or .xml. Exports operation logs to a .csvfile or .xml file.

Save File Path Default value. No change.The default path is:/export/home/omc/var/fileint/***logs/, where *** stands forthe log type.

Saves the exported logs.

File Size Unit: MBDefault value: 1024

Refers to the threshold of thespace for dumping log files.During the export of log files, ifthe size of the files existing in thespecified path exceeds the presetthreshold, the earliest files arereplaced.NOTE

When setting the threshold of dumpspace, the size of the partition that thepath for saving log files belongs tomust be taken into account. Thethreshold cannot exceeds the size ofthe partition.



6-75


File Hold Days Unit: dayDefault value: 15

Refers to the number of the dayswithin which the dump files can besaved. After these days, the filesare automatically deleted.

File Sum Number of filesDefault value: 1000

Refers to the maximum number offiles in the dump space. During theexport of log files, if the numberof the files existing in the specifiedpath exceeds the preset threshold,the earliest files are replaced.

Table 6-27 Extension parameters of Configuration Data Export tasks


File Format Two formats areavailable, thatis, .xml and .csv.You can selectfrom the drop-down list.

Refers to the format in which the exported data filesare saved.

File Path Default value. Nochange.The default pathis: /export/home/omc/var/fileint/cm/autoExport.

Refers to the path to save the exported configurationdata.

Please SelectNE

You can select therequired NEs inPhysicalTopology Tree.If All NEConfigurationData is selected,the PhysicalTopology Treebecomesunavailable. Thenthe M2000 exportsthe configurationdata of all NEs.

l Click to expand all the sub nodes.

l Click to collapse all the sub nodes.

l refers to cascading select. That is, by selectinga parent node, all the subnodes under it areselected.




Issue 10 (2010-09-06)

6.8.14 Parameters for Modifying Synchronization taskThis section describes the parameters of Synchronization task. When modifying Synchronizationtask, you can set the parameters by referring to the information described in this section.

Parameter descriptionl Parameters for Modifying the Synchronization of NE Configuration Data

l Parameters for Modifying the Synchronization of Inventory Data

Table 6-28 Parameters for Modifying the Synchronization of NE Configuration Data


All NE ConfigurationData

If All NE Configuration Data is selected, the systemsynchronizes the configuration data of all existing NEs in thenetwork.

Please Select NE Select existing NEs in the entire network. Multiple NEs aresupported.

Table 6-29 Parameters for Modifying the Synchronization of Inventory Data


All NE If you select this option, the system synchronizes the inventorydata of all NEs on the network.

Please Select NE Indicates all the NEs in the entire network. Multiple NEs aresupported. You can select the specific NEs in Please Select NEonly after you clear All NE.

6.8.15 Parameters for Modifying NE Basic Information Export TaskThis section describes the parameters involved in the NE basic information export task. Whenmodifying an NE basic information export task, you can refer to this part and perform relevantoperations.

Parameter description

The M2000 provides the function of exporting NE basic information. Thus, it can provide datato the Nastar for performance analysis. You can modify the common parameters and extendedparameters of the task according to the actual requirement.


Exported File Export the file containing NE basic information tothe /export/home/omc/var/fileint/network/EAMInfo.xml path on the M2000 server.



6-77


Export All NE The NE navigation tree is unavailable. You need notspecify the NEs to be exported. The M2000 exports theinformation about all NEs.

Export By NE Type After you select a certain NE type from the NEnavigation tree, the M2000 exports the informationabout all NEs of this type.

Export By NE After you select some NEs from the NE navigationtree, the M2000 exports the information about allselected NEs.

6.8.16 Parameters for Modifying Alarm Timing AcknowledgementThis part describes the parameters in the alarm acknowledgement. When modifying alarmacknowledgement, you can set the parameters in the alarm acknowledgement by referring to theinformation described in this section.

Parameter DescriptionParameter Value Range Description

Alarm Level l Critical

l Major

l Minor

l Warning

Indicates the level of alarms. Multiple choicesare supported.

Alarm State l Unacknowledgeand unclear Fault

l Unacknowledgeand clear Fault

Indicates the alarm states. Multiple choices aresupported.

6.8.17 Parameters for Modifying Data Backup TaskThis 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.

Parameter Descriptionl parameters for Modifying Data Backup in the M2000

l Parameters for Creating/Modifying/Copying NE Backup




Issue 10 (2010-09-06)

Table 6-30 Parameters for Modifying Data Backup in the M2000


Server Full BackupDay

Form Monday to Sunday The full backup is executed each week.If you set to Monday, the full backupis performed each Monday.

File Path Default value. No change.The default path is: /export/home/backup/omc.

The path to save the backup M2000system data.

Table 6-31 Parameters for Creating/Modifying/Copying NE Backup


File Path Refers to the path to save NE data backup files. It is specified by the system.

Backup AllNE

If you select this parameter, the system backs up the data of all NEs availablein the current network. By default, the system backs up the data of all NEs inthe entire network.

By NE Type If this option is selected, you should specify the NE type in the NE Typenavigation tree.1. Select By NE Type.

2. Click proceeded by By NE Type. The By NE Type dialog box isdisplayed.

3. In the navigation tree in the left pane, select one or multiple NE types.

4. Click to add the selected NE types to the valid domain at the rightside.NOTE

l Click to delete the selected NE types from the valid domain at the rightside.

l Click and to collapse and expand nodes in the navigation tree.

l Enter filtering conditions in Name, and then click to filter nodes in thenavigation tree.

5. Click Apply.



6-79


By NE 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 to add the selected NEs to the valid domain at the right side.NOTE

l Click to delete the selected NEs from the valid domain at the right side.

l Click and to collapse and expand nodes in the navigation tree.

l Enter filtering conditions in Name, and then click to filter nodes in thenavigation tree.

5. Click Apply.

6.8.18 Parameters for Creating/Modifying/Copying MMLCommand Script

This section describes the parameters of MML command script tasks. When creating ormodifying MML command script tasks, you can refer to this part.


Script file The script fileis in .txtformat. Themaximum sizeis 1 MB.

The MML script file is a text file that records MMLcommands for one NE or multiple NEs of the same type.You can enter the path of an MML script file in the textbox, or click . In the displayed Open dialog box, selectthe MML script file.




Issue 10 (2010-09-06)


Select NE None. After you select this option, you can change the NE of ascript command by selecting the NE in the NE tree insteadof modifying the script file. After the NE is selected, theoriginal NE information in the script file is invalid, andall the commands are issued to the newly selected NE.The NE tree displays all the NEs in a physical topologytree. The function buttons for selecting NEs are describedas follows:

l : You can click this button to expand the NE tree.

l : You can click this button to collapse the NE tree.

l : You can click this button to use the SingleSelect mode. That is, if you select a node, the subnodesare not selected. You can click this button to switch tothe Recursive Select mode.

l : to use the Recursive Select mode. That is, if youselect a node, the subnodes are also selected. You canclick this button to switch to the Single Select mode.

NOTEWhen creating MML script tasks, you must select Select NE tochoose NE objects if certain command lines in the script file doesnot contain object information.

ExecutionMode

Parallel orSerial.

Two modes for issuing MML commands are available:l Parallel: indicates that the MML commands are issued

to the NE concurrently.l Serial: indicates that the MML commands are issued

to the NE in sequence.

Error-ExecuteMode

Ignore orStop.

Refers to the mode of handling the errors that occur whenyou run the MML commands in the MML script file.l Ignore: ignores the MML commands where errors

occur and continues running other MML commands.l Stop: stops running other MML commands.

ExecutionResult

None. If the type of a created task is Once, you can select SaveAs and specify the path for adding the execution result ofthe task to a certain redirection file. If the specifiedredirection file does not exist, you can create the file. Ifthe specified redirection file exists, the new informationwritten into the file does not overwrite the originalinformation.If you have set task result redirection, the path specifiedin Save As cannot be changed after a task is created.



6-81

6.8.19 Parameters for Creating/Modifying/Copying RAN ReportTask

This describes the parameters involved in the RAN report task. When creating, modifying, orcopying a RAN report task, you can refer to this part and perform relevant operations.

Parameter description

You can set the RAN report export task on the M2000 to export the RAN report of a specifiedNE to a specified directory on the server. You can set a report task to export the MBTS, WCDMA,CDMA, or GSM reports.


File Path Refers to the default path for saving the file. The pathcannot be changed.

Ne Type You can select MBTS, WCDMA, CDMA,or GSM.After you select the NE type, you also need to selectthe NEs whose reports are to be exported from the NEnavigation tree.

Selected You can select Selected to specify Report Type.

Report Type

6.8.20 Parameters for Creating, Viewing, or Modifying a ScheduledReport Task

This section describes the parameters for setting a scheduled report task. You can refer to thispart when you create, query, or modify a scheduled task.

Common Parameters


BasicInformation

Task Name Indicates the name of a scheduled report task.The value range is as follows:l A maximum of 64 characters

l The following characters except ' are allowed: Englishcharacters, numbers, and other special characters.

l 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 thedisplayed Date/Time Selection dialog box.The start time must be later than the current time of the server.




Issue 10 (2010-09-06)


ExecutionType

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.l Once: indicates that the system performs a created task once

at a specific time.If you select this option, the parameters in ExecutionPeriod become unavailable.

ExecutionPeriod

Indicates the interval between periodic tasks. Setting thisparameter involves setting the unit and duration.The unit can be hour, day, week, or month.

ExecutionTimes

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.l Limited: indicates that the system runs this task N times. N

represents a specific number.

Extended ParametersParameter Description

ExtendedParameter

Report Name Indicates the name of a scheduled report task.

Save Path Indicates the path for saving the generated reports.For example, /report/$ReportOwner$/$TaskName$$Date$. For the description of each field in the path, see Table6-32.

File Name Indicates the name of a generated report.For example, $reportname$-$date$. For the description ofeach 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 Excel

l HTML

l CSV



6-83


Compress Indicates whether to compress the report files that aregenerated periodically.The value range is as follows:l Selected

l Not selected

The system selects Compress by default. In this case, files arecompressed in .zip format.

MaximumFile Number

Indicates that the report files of a scheduled task that aregenerated in the latest N times are saved. N represents aspecific number.The value range is as follows:l Unlimited: indicates that the system saves all the report files

of the task.l 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 Meaning

$ReportOwner$ Indicates the creator of a report.

$TaskType$ Indicates the type of a periodic task.The values are once, hour, daily, weekly, andmonthly.

$Time$ Indicates the generation time of a periodicreport.

$DateTime$ Indicates the generation date and time of aperiodic report.

$Format$ Indicates the format of a periodic report.

$TaskOwner$ Indicates the creator of a scheduled reporttask.

$ReportName$ Indicates the name of a report.

$TaskName$ Indicates the name of a scheduled task.

$Date$ Indicates the generation date.

$Index$ Indicates the times of performing a scheduledtask.




Issue 10 (2010-09-06)

Predefined Macro Meaning

$yy$ Indicates a year.It supports simple expressions.For example, $yy-1$ indicates the year beforethe current year; $yy+1$ indicates the yearafter the current year.

$mm$ Indicates a month.It supports simple expressions.For example, $mm-1$ indicates the monthbefore the current month; $mm+1$ indicatesthe month after the current month.

$dd$ Indicates a day.It supports simple expressions.For example, $dd-1$ indicates the day beforethe current day; $dd+1$ indicates the dayafter the current day.

$hh$ Indicates an hour.It supports simple expressions.For example, $hh-1$ indicates the hourbefore the current hour; $dd+1$ indicates thehour after the current hour.

$Moh$ Indicates a minute.It can be represented in a simple format.For example, $Moh-1$ indicates the minutebefore the current minute; $Moh+1$indicates the minute after the current minute.

NOTE

The naming convention for scheduled task files is as follows:

l The name of the performance report file in Excel format is specified by File Name.

l 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-definedreport name, and report_1 is the subreport name.



6-85

Distribution Parameters


EmailDistribution

To Indicates the recipient of emails. Use semicolons to separaterecipient names.Click Email Boxes. The Select the distributing email boxdialog box is displayed. Select one or multiple mailboxes, andthen click OK.TIP

You can also right-click any row and choose Select All or Clear Allfrom the shortcut menu.

The system can send scheduled report files to a maximum of64 mailboxes simultaneously.

Email Subject Indicates the subject of an email.If you have set To, you need to set the subject.

EmailContents

Indicates the contents of an email.

FTPDistribution

FTP Server Indicates the IP address of the FTP server.Click FTP Server. The Select the distributing FTP serverdialog box is displayed. Select one or multiple servers, andthen click OK.TIP

You can also right-click any row and choose Select All or Clear Allfrom the shortcut menu.

The system can send scheduled report files to a maximum ofeight 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 manuallyperform a scheduled report task to generate a report file at a specific time and distribute the report file toan email or FTP server.

6.8.21 Parameters for Creating/Modifying/Copying a Task forTesting BTS Cabinet-Top Power

This section describes the parameters of a task for testing BTS cabinet-top power. You can referto this section when creating or modifying such a task.



ExecutionDuration

3-120 minutes Maximum execution duration of a task




Issue 10 (2010-09-06)


NE None Existing NE that supports cabinet-top powertest.

6.8.22 Parameters for Creating/Modifying/Copying an RSSI TestTask

This section describes the parameters of an RSSI test task. You can refer to this section whencreating or modifying an RSSI test task.



ExecutionDuration

3-120 minutes Maximum execution duration of a task

NE None Existing NE that supports RSSI test.

Frequency 0-2047The default value is null,which indicates that allfrequencies are tested.

Frequency to be tested in an RSSI task.

6.8.23 Parameters for Creating/Modifying/Copying SoftwareDownload

This section describes the parameters in the software download task. When creating or modifyingsoftware download task, you can set the parameters for software download task by referring theinformation described in this section.



NE Type Select the value from thedrop-down list.

Indicates all of the NE types available in thecurrent network.

Edition List None. Indicates the editions of all NEs that can bedownloaded from the server. These NEs are ofthe same type. Multiple choices are not allowed.

NE List None. Indicates all of the NEs of an NE type availablein the current network. Multiple choices aresupported.



6-87

6.8.24 Parameters for Creating/Modifying/Copying Dual-HomeManagement

This describes the parameters used in dual-homing management. You can refer to theseparameters when creating, modifying, or copying dual-home management.

Parameter DescriptionParameter Description Setting

Dual Homing Pairs Indicates the dual-homingpairs. For detailed informationabout dual homing, refer to LNDomain Management.

Select from the drop-down list.

Resource Type Indicates the data resourcetype of the dual homing pairsto be checked.Data resource types varydepending on the version ofdual-homing pair NE.

l Select the item in theResource Type navigationtree.

l Enter the data resource type orkey word in the Search box.Then the related resourcetypes are listed under theSearch box. You can double-click resource type to bechecked.

Search Use to search for the type of thedata resource to be checked.The search conditions supportcase insensitive fuzzy search.Wildcard search is notsupported.

Enter the data resource type ofkey word in the Search box.

6.8.25 Parameters for Creating/Modifying/Copying iSStar ScriptThis section describes the parameters in the iSStar script task. When creating or modifying iSStarscripts, you can set the parameters in the iSStar tasks by referring to the information describedin this section.


Main File The main file is in .hslformat. The main file hasa maximum size of 1MB.

The main file is the entry file for the executionof script files.




Issue 10 (2010-09-06)


Assistant File The assistant file has amaximum size of 1 MB.

When the script files are being executed, themain file selects from assistant files if the mainfile need to invoke other script files.

NE Selection None. You need to select NEs when script files containoperations on several NEs. Multiple choices aresupported.

6.8.26 Parameters for Creating/Modifying/Copying the Export ofNE Upgrade Log

This describes the parameters for exporting NE logs and can be taken as reference during theparameter modification.

Table 6-33 lists the extended parameters.

Table 6-33 Description of extended parameters


NE None. Refers to all the NEs on the entirenetwork.

Start Time The start time must meet therequirement of time format.

All NE upgrade logs within thetime range specified by the starttime and end time are to bequeried.

End Time The end time must meet therequirement of time format.

All NE upgrade logs within thetime range specified by the starttime and end time are to bequeried.

File Format The default file format must beretained.

Operation logs are exportedto .xml files.

File Path The default file path must beretained.The default path is /export/home/omc/var/field/UpgradeHistory/.

Refers to the path for saving NElogs.

6.8.27 Parameters for Creating/Modifying/Copying a CME UploadTask

This describes the parameters of a CME upload task. When creating or modifying a CME uploadtask, you can refer to the parameter description and perform relevant operations.



6-89

Parameter DescriptionParameter Description

All NE After you select this option, the system uploads the configuration dataof all the existing RNCs and NodeBs on the network.

All NodeBs UnderRNC

After you select this option, the system uploads the configuration dataof all the NodeBs under the selected RNCs.

6.8.28 Parameters for Creating/Modifying/Copying Cell ParametersCompare Task

This describes the parameters involved in the CME cell algorithm comparison task. Whencreating or modifying a CME cell algorithm comparison task, you can refer to this part andperform relevant operations.

A CME cell algorithm comparison task can be performed to compare the parameters in theCurrent area with the default parameters in the CME configuration template and then export thecomparison results to the specified path.


Cell Input Mode Select the NE of a Cell After you select this mode, you canspecify the NEs of a cell whoseparameters are to be compared.

Import Cell After you select this mode, you canimport the list of cells whoseparameters are to be compared.

Select the NE of a Celland the Template

NE Select the name of the controllermanaging the cell. The M2000automatically compares theparameters of all the cells managed bythe selected controller.

Template Select the template to be compared.The M2000 automatically comparesthe cell parameters with the defaultconfiguration parameters of theselected template. For example, youcan select Default 2G CellTemplate.




Issue 10 (2010-09-06)

6.8.29 Parameters for Creating/Modifying/Copying CellConsistency Check Task

This describes the parameters involved in the CME cell consistency check task. When creatingor modifying a CME cell consistency check task, you can refer to this part and perform relevantoperations.

Parameter descriptionA cell consistency check task can be performed to check that the data in the Current area complieswith the selected check rules.


NE Select the name of the controller managing the cell.The M2000 automatically compares the parameters ofall the cells managed by the selected controller.

Rule Select check rules.

6.8.30 Parameters for Creating/Modifying/Copying a CME CurrentArea Export Task

This describes the parameters of CME Current Area Export tasks. When creating or modifyinga CME Current Area Export task, you can refer to the information described in this part.

Parameter DescriptionTo manage the current data area, you can perform a CME data export task to export the datafrom the current data area for Northbound.


Select Export Type Select the data to be exported and its file format. Theparameter values are as follows:l XML format:

– radio parameter

– transmission parameter

– radio and transmission parameter

l CSV format:– radio parameter

– transmission parameter

– radio and transmission paramete



6-91


Select NE Select one or multiple controllers of the cell to whichthe data to be exported belongs. If you select AllNEs, the data in the current data areas under all thecontrollers is to be exported.

6.8.31 Parameters for Setting Time of Timing TasksThis section describes the parameters of time for automatic suspending and automatic resumingtiming 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


Suspend Time The system suspends an idle task and delay the time forusing this task. If the timing task is not in the Idle stateat the specified time, it fails to be suspended.You can set the value manually. Alternatively, you canclick and select the time from the time select panel.The time format is DD/MM/YYYY HH:MM:SS.l YYYY stands for the year.

l MM stands for the month.

l DD stands for the date.

l HH stands for the hour.

l MM stands for the minute.

l SS stands for the second.

Resume Time In the specified time, the system resume a suspended taskand then the task is in the idle state and wait to bedispatched. If the timing task is not in the Idle state at thespecified time, it fails to be suspended.You can set the value manually. Alternatively, you canclick and select the time from the time select panel.The time format is DD/MM/YYYY HH:MM:SS.l YYYY stands for the year.

l MM stands for the month.

l DD stands for the date.

l HH stands for the hour.

l MM stands for the minute.

l SS stands for the second.




Issue 10 (2010-09-06)

6.8.32 Parameters for Selecting Objects for Device CheckThis part describes the extended parameters for selecting objects for device check. You can referto this part when creating device check tasks.



Device Check Displays the type of the NE that supports device check, such asRNC, NodeB, eNodeB, BSC6000, and OMC.

NE Displays the specific NE. Grouped by topology or type.

Device Check Item Displays the device check items supported by NEs.CAUTION

l Check items vary according to NE versions. For detailed meaningof each check item, refer to NE Reference Information.

l For the BSC6000, the device check enables you to perform updatecheck to ensure that the check items related to device update arenormal.

6.8.33 Parameters for Collecting NM Logs ParametersThis describes the parameters of the M2000 log information collecting tool dialog box. Whencollecting NMS log files, refer to the information described here for parameter setting.



Serverinformation

Server address Complies with the principles of IP address rules.Cannot be null.

Port Number Indicates the port of the server. Value range: 1-65,536 Thedefault value is 10119.Cannot be null.

FTP User name Indicates a valid name that the user already registered to theM2000.Cannot be null.

password Indicates the password that is used to log in to the targetserver.Cannot be null.

Itemsselection

Trace files inLocal Host

Collects the trace files from the M2000 client.

Trace files inserver

Collects the trace files from the M2000 server.



6-93


Core files inserver

Collects the core files from the server.

LMT trace filesin server

Collects the trace files from the local maintenanceterminal (LMT).

Start Time Indicates the start time for collecting trace files and corefiles.

End Time Indicates the end time for collecting trace files and core files.

Alarm diagnosticdata

Collects the alarm synchronization signals of NEs.

NE Name Collects the NEs involved in alarm diagnostic data.

SavePositions

Save Positions Indicates the directory for the collected diagnostic data.




Issue 10 (2010-09-06)

7 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 ServicesWhen the M2000 is running, the M2000 server automatically starts the processes related to theM2000 system. Each process provides different services and functions.

7.2 Managing M2000 ServicesThis section describes how to view, start, and stop M2000 system services.

M2000Administrator Guide (Sun, S10) 7 Managing M2000 Processes and Services


7-1

7.1 Introduction to M2000 Processes and ServicesWhen the M2000 is running, the M2000 server automatically starts the processes related to theM2000 system. Each process provides different services and functions.

7.1.1 3rdTool_agent ProcessThis section describes the 3rdToolService service and dependent services.

7.1.2 adn_agent ProcessThis section describes the services and functions provided by the adn_agent process.

7.1.3 adss_agent ProcessThis section describes the services and functions provided by the adss_agent process.

7.1.4 antenna_agent ProcessThis section describes the services and functions provided by the antenna_agent process.

7.1.5 ce_agent ProcessThis section describes the services and functions provided by the ce_agent process.

7.1.6 cmdc_agent ProcessThis section describes the CmDcService service and dependent services. CmDcService isprovided by the cmdc_agent process.

7.1.7 cmengine_agent ProcessThis section describes the services and functions provided by the cmengine_agent process.

7.1.8 cmeserver_agent ProcessThis section describes the services and functions provided by the cmeserver_agent process.

7.1.9 cmexp_agent ProcessThis section describes the service and functions provided by the cmexp_agent process.

7.1.10 cmserver_agent ProcessThis section describes the services and functions provided by the process cmserver_agent.

7.1.11 cnnhc_agent ProcessThis section describes the services and functions provided by the cnnhc_agent process.

7.1.12 corba_agent ProcessThis section describes the services and functions provided by the corba_agent process.

7.1.13 cpm_agent ProcessThis section describes the services and functions provided by the cpm_agent process.

7.1.14 devdoc_agent ProcessThis section describes the DevDocService service provided by the devdoc_agent process.

7.1.15 dsXXXX agent ProcessThis section describes the services and functions provided by the dsXXXX_agent process.

7.1.16 eam_agent ProcessThis section describes the services and functions provided by the eam_agent process.

7.1.17 fars_agent ProcessThis section describes the service and function provided by the fars_agent process.

7.1.18 fmnotify_agent Process

7 Managing M2000 Processes and ServicesM2000



Issue 10 (2010-09-06)

This section describes the services and functions provided by the fmnotify_agent process.

7.1.19 FMPreServiceXXXX_agent ProcessThis section describes the services and functions provided by the FMPreServiceXXXX_agentprocess.

7.1.20 fnlicense_agent ProcessThis section describes the services and functions provided by the fnlicense_agent process.

7.1.21 glmssyn_agent ProcessThis section describes the services and functions provided by the glmssyn_agent process.

7.1.22 ifms_agent ProcessThis section describes the service and functions provided by the ifms_agent process.

7.1.23 ipqdt_agent ProcessThis section describes the services and functions provided by the ipqdt_agent process.

7.1.24 ipm_agent ProcessThis section describes the services and functions provided by the ipm_agent process.

7.1.25 irp_agent ProcessThis section describes the functions provided by the irp_agent process.

7.1.26 itm_agent ProcessThis section describes the ItmService service and the dependent services by the itm_agentprocess.

7.1.27 lcsserver_agent ProcessThis section describes the services and functions provided by the lcsserver_agent process.

7.1.28 lic_agent ProcessThis chapter describes the services and functions provided by the process lic_agent.

7.1.29 log_agent ProcessThis section describes the LogService service and dependent services. LogService is providedby the log_agent process.

7.1.30 lte_agent ProcessThis section describes the services and functions provided by the lte_agent process.

7.1.31 maintain_agent ProcessThis topic describes the function of the MaintenanceService service, which is provided by themaintain_agent process.

7.1.32 manager_agent ProcessThis section describes the services and functions provided by the manager_agent process.

7.1.33 medXXXX_agent ProcessThis section describes the services and functions provided by the medXXXX_agent process.

7.1.34 nelicense_agent ProcessThis section describes the services and functions provided by the nelicense_agent process.

7.1.35 neuser_agent ProcessThis section describes the NeUserService service. NeUserService is provided by theneuser_agent process.

7.1.36 ngnffs_agent ProcessThis section describes the NGNFullFillService service and dependent services.



7-3

7.1.37 ngnnis_agent ProcessThis section describes the NGNNIService service and dependent services.

7.1.38 ngnni112_agent ProcessThis section describes the services and functions provided by the ngnni112_agent process.

7.1.39 ngntestmanage_agent ProcessThis section describes the services and functions provided by the ngntestmanage_agent process.

7.1.40 nhcservice_agent ProcessThis section describes the services and functions provided by the nhcservice_agent process.

7.1.41 nicservice_agent ProcessThis section describes the services and functions provided by the nicservice_agent process.

7.1.42 nimserver_agent ProcessThis section describes the NIMServer service and the dependent service. NIMServer is providedby the nimserver_agent process.

7.1.43 nms_mml_agent ProcessThis section describes the services and functions provided by the process nms_mml_agent.

7.1.44 partition_agent ProcessThis section describes the services and functions provided by the partition_agent process.

7.1.45 pm_agent ProcessThis section describes the services and functions provided by the process pm_agent.

7.1.46 pmexp_agent ProcessThis section describes the services and functions provided by the process pmexp_agent.

7.1.47 pmmon_agent ProcessThis section describes the services and functions provided by the process pmmon_agent.

7.1.48 pmncdXX01_agent ProcessThis section describes the services and functions provided by the pmncdXX01_agent process.

7.1.49 porttrunk_agent ProcessThis section describes the services and functions provided by the porttrunk_agent process.

7.1.50 proxy_agent ProcessThis section describes the services and functions provided by the proxy_agent process.

7.1.51 PRSAssistantService_agent ProcessThis section describes the services and functions provided by the PRSAssistantService_agentprocess.

7.1.52 prsdc_agent ProcessThis section describes the services and functions provided by the prsdc_agent process.

7.1.53 prsfs_agent ProcessThis section describes the services and functions provided by the prsfs_agent process.

7.1.54 prsreport_agent ProcessThis section describes the services and functions provided by the prsreport_agent process.

7.1.55 prssum_agent ProcessThis section describes the services and functions provided by the prssum_agent process.

7.1.56 rn_agent ProcessThis section describes the services and functions provided by the rn_agent process.




Issue 10 (2010-09-06)

7.1.57 ScriptModuleService_agent ProcessThis section describes the services and functions provided by the ScriptModuleService_agentprocess.

7.1.58 scriptserver_agent ProcessThis section describes the services and functions provided by the process scriptserver_agent.

7.1.59 sm_agent ProcessThis section describes the services and functions provided by the process sm_agent.

7.1.60 snmp_agent ProcessThis section describes the SnmpAgent service and the dependent services. The SnmpAgentservice is provided by the snmp_agent process.

7.1.61 son_agent ProcessThis section describes the services and functions provided by the son_agent process.

7.1.62 swm_agent ProcessThis section describes the services and functions provided by the swm_agent process.

7.1.63 threshold_agent ProcessThis topic describes the function of the ThresholdService service provided by thethreshold_agent process and the service that the threshold_agent process depends on.

7.1.64 uap_agent ProcessThis section describes the services and functions provided by the uap_agent process.

7.1.65 udpdispatch_agent ProcessThis section describes the services and functions provided by the udpdispatch_agent process.

7.1.66 umgupdsvr_agent ProcessThis section describes the services and functions provided by the umgupdsvr_agent process.

7.1.67 xftpXX01_agent ProcessThis section describes the services and functions provided by the xftpXX01_agent process.

7.1.68 Processes and Services Related to Each Northbound InterfaceThis section describes the processes and services related to each northbound interface.


7.1.1 3rdTool_agent ProcessThis 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 datacenter.

Required services: none

7.1.2 adn_agent ProcessThis section describes the services and functions provided by the adn_agent process.

The adn_agent process provides the ADNService service.



7-5

The ADNService service supports the NodeB plug-and-play function. It provides variousfunctions for newly constructed NodeBs, such as remote automatic activation and automaticfault 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 ProcessThis 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 securityof 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 ProcessThis 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 thefaults related to GBSS antennas.

Required service: EAMService.

7.1.5 ce_agent ProcessThis 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 NMSto 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 ProcessThis section describes the CmDcService service and dependent services. CmDcService isprovided by the cmdc_agent process.

The cmdc_agent process provides the CmDcService service.

The CmDcService service provides the functions such as data access interface, synchronizationmanagement, and session management.

Required services: TopoAdapterService.

7.1.7 cmengine_agent ProcessThis section describes the services and functions provided by the cmengine_agent process.




Issue 10 (2010-09-06)

The cmserver_agent process provides the CMEngine service.

CMEngine manages the configuration of the network manager. Configuration management isindependent of NEs or managed objects.

When the M2000 is running, ensure that this service functions properly.

Required services: TopoService.

7.1.8 cmeserver_agent ProcessThis 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 ProcessThis 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 theconfiguration 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 byusing 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 ProcessThis 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 managementis independent of NEs or managed objects.

The CMServer provides channels for issuing MML commands and helps to receive thesupplementary messages reported automatically by NEs.

The CMServer provides the function of managing object groups and enables the M2000 toautomatically and remotely commission the NodeB upgrade.


Required services: TopoService.



7-7

7.1.11 cnnhc_agent ProcessThis 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.


7.1.12 corba_agent ProcessThis 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 ProcessThis section describes the services and functions provided by the cpm_agent process.

The cpm_agent process provides the CPMService service, that is, the pool configurationmanagement service.

The Pool configuration management service provides users with the following functions:

l Creating a pool

l Checking pool alarms

l Measuring the performance of a pool

l Monitoring the load of a pool in real time

l Displaying the pool topology

l Setting pool parameters

l Checking the NE data in a pool

l Checking the MSC Server or MSCe of a specific user


7.1.14 devdoc_agent ProcessThis 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.


7.1.15 dsXXXX agent ProcessThis section describes the services and functions provided by the dsXXXX_agent process.

The dsXXXX_agent process provides the DesktopServiceXXXX service.




Issue 10 (2010-09-06)

Some typical process names are ds0101_agent and ds0102_agent. The corresponding servicenames 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 asthe 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 ProcessThis section describes the services and functions provided by the eam_agent process.

The eam_agent process provides the EAMService, TopoAdapterService, and TopoServiceservices.

The EAMService service provides the function of NE access management and maintains aglobally 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 userswho use the earlier versions can use the topology function. The TopoAdapterService servicedepends on the EAMService, TopoService, LogService, SecurityService, and LicenseServiceservices.

The TopoService service can maintain the relation between the devices in the subnet, create anddelete subnets, nodes, and topology node, and move nodes among subnets. The TopoServiceservice depends on the EAMService services.

7.1.17 fars_agent ProcessThis 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 datacollection management.

To enable the tracing function, you need to ensure that the FarsService is running normallyduring the operation of the M2000.

Dependent service: MediationServiceXXXX, and XXXX refers to the instance number.

7.1.18 fmnotify_agent ProcessThis 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-9

7.1.19 FMPreServiceXXXX_agent ProcessThis section describes the services and functions provided by the FMPreServiceXXXX_agentprocess.

The FMPreServiceXXXX_agent process provides the FMPreServiceXXXX service.

The FMPreServiceXXXX_agent process is a multi-instance process. XXXX refers to the processnumber.

The FMPreServiceXXXX service provides the function of prehandling faults.

In an SLS system, you can deploy the FMPreServiceXXXX_agent process on the master nodeand several slave nodes. You can also deploy multiple FMPreServiceXXXX_agent processes onone node. For example, you can deploy the FMPreService0101_agent,FMPreService0102_agent, and FMPreService0103_agent processes on the master node forproviding the FMPreService0101, FMPreService0102, and FMPreService0103 servicesseparately. You can also deploy the FMPreService0201_agent, FMPreService0202_agent, andFMPreService0203_agent processes on a slave node for providing the FMPreService0201,FMPreService0202, and FMPreService0203 services separately.

Required service: FaultService.

7.1.20 fnlicense_agent ProcessThis 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 licenseauthorization information about EMS. The number of purchased licenses determines the numberof available resources and whether the user can use a specific functional component.

Required services: LicenseService.

7.1.21 glmssyn_agent ProcessThis 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 communicationchanges from the Group and List Management Server (GLMS) and then applies the informationto CBSCs.

You can stop this process if the QChat cluster communication is not required.

Required services: CMServer

7.1.22 ifms_agent ProcessThis 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 functionsof querying, dumping, and analyzing the fault data.

You can disable the service when fault management is not required.




Issue 10 (2010-09-06)


7.1.23 ipqdt_agent ProcessThis 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 ahigh 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 ProcessThis 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 runningcorrectly during the operation of the M2000.


7.1.25 irp_agent ProcessThis section describes the functions provided by the irp_agent process.

EPIRPThe EPIRP is subject to the entry point object. The entry point object is the first object that theNMS (Manager) accesses when the NMS interacts with the M2000 (Agent). The Agent providesa reference of an entry point object to the Manager, and the Manager obtains the reference ofthis entry point object in some way, for example, from the stored file. If the interface fornorthbound network management is not required, disable the EPIRP.

Basic IRP: None.

NotificationIRPNotificationIRP is used for subscribing to notifications and encapsulating notificationsubscription. If the function of subscription through the interface of northbound networkmanagement is not required, disable the NotificationIRP.

Basic IRP: EPIRP.

CSIRPCSIRP provides an interface for link monitoring.

The link monitoring enables you to supervise the status of links between the Manager and theAgent. In this way, the potential exceptions can be detected at the first time. If the function of



7-11

monitoring through the interface of northbound network management is not required, disablethe CSIRP.

Basic IRP: EPIRP, and NotificationIRP.

KernelCMIRPKernelCMIRP provides an interface for public configuration management.

The public configuration management uses KernelCMIRP to carry out some common tasksduring the configuration, such as sending configuration objects, or adding, removing andmodifying notifications. If the function of public configuration management through theinterface of northbound network management is not required, disable the kernelCMIRP.

Basic IRP: EPIRP, and NotificationIRP.

BasicCMIRPBasicCMIRP controls the configuration management. BasicCMIRP is used for querying,modifying, adding, or removing network resource objects. If the function of configurationmanagement through the interface of northband network management is not enabled, disablethe BasicCMIRP.

Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, and KernelCMIRP.

AlarmIRPAlarmIRP is used for managing fault data. If the function of fault data management through theinterface of northbound network management is not required, disable the AlarmIRP.

Basic IRP: EPIRP, NotificationIRP, FileTransferIRP, KernelCMIRP, and BasicCMIRP.

Required ServicesThe required service is the LicenseService.

7.1.26 itm_agent ProcessThis section describes the ItmService service and the dependent services by the itm_agentprocess.

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




Issue 10 (2010-09-06)


7.1.28 lic_agent ProcessThis 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.


7.1.29 log_agent ProcessThis section describes the LogService service and dependent services. LogService is providedby the log_agent process.

The log_agent process provides the LogService service.

The LogService service enables other services to save the system-related operation informationto files. It also enables the client to query log records of the operating system and to set andquery the parameters for dumping system logs.


7.1.30 lte_agent ProcessThis 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 asinvalidity, export, and adjustment information.

The SSLManageService service manages the SSL connections between the M2000 and NEs. Italso manages the SSL certificates used by the SSL connections.



7.1.31 maintain_agent ProcessThis topic describes the function of the MaintenanceService service, which is provided by themaintain_agent process.

The maintain_agent process provides the MaintenanceService service.

The MaintenanceService service enables the periodic backup of the important systemconfiguration files, database data, and real-time data of MOs.

During the M2000 operation, ensure that the maintain_agent process is operational.


7.1.32 manager_agent ProcessThis section describes the services and functions provided by the manager_agent process.



7-13

The manager_agent process provides the SystemService service.

SystemService enables you to query the M2000 version information such as the version of theoperating system, software version of the client, software version of the server, client softwareversion matching the server software, and client upgrade information.



7.1.33 medXXXX_agent ProcessThis 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 basedon 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 thenetwork devices from the M2000 system and also manages the related event interceptors. NEsof different types communicate with the M2000 system by using the corresponding NE enginesthrough various network management protocols. In addition, the MediationServiceXXXX servicecan export performance result files on the basis of NEs.


Dependent services: PartitionService, UdpDispatchService, and PartitionService

7.1.34 nelicense_agent ProcessThis 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 licensebetween the NEs of the same type.

Required services: CMEngine.

7.1.35 neuser_agent ProcessThis section describes the NeUserService service. NeUserService is provided by theneuser_agent process.

The neuser_agent process provides the NeUserService service.

The NeUserService service enables you to manage NE users. When the M2000 and NEs areconnected properly, you can manage NE users through the M2000. For example, you canauthenticate the login of NE users, deliver command rights and command group rights, andcustomize command groups.





Issue 10 (2010-09-06)

7.1.36 ngnffs_agent ProcessThis 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 thesubscriber number management.


7.1.37 ngnnis_agent ProcessThis 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.


7.1.38 ngnni112_agent ProcessThis 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 ProcessThis 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.


7.1.40 nhcservice_agent ProcessThis 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_agentprocess 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 ProcessThis section describes the services and functions provided by the nicservice_agent process.

The nicservice_agent process provides the NICService service.



7-15

The NICService service provides the network information collecting function. Thenicservice_agent process is available only after you have installed the network informationcollecting components.

If you plan to perform a network information collecting task, you must ensure this service isrunning properly.

Required service: ITMService and EAMService.

7.1.42 nimserver_agent ProcessThis section describes the NIMServer service and the dependent service. NIMServer is providedby 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 onlyprovides the functions to some WRAN configuration objectssuch as alarm statistics, query ofbasic configuration information, query of configuration link constitution and basic configurationinformation, and query of adjacent cells and channel assignment.

Required services: CmDcService, FaultService, and PMMonService.

7.1.43 nms_mml_agent ProcessThis 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 issuesMML commands through the northbound MML transmission interface to managed NEs.

If the northbound MML transmission interface is used when the M2000 is running, ensure thatthe NMSMMLServer is running correctly. When the northbound MML transmission interfaceis not used, the NMSMMLServer is not disruptive to other services.

Required service: LogService.

7.1.44 partition_agent ProcessThis 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 ismanaged by its own process. In the presence of a large quantity of objects, the partitions aremanaged by various processes on different servers to balance the load.



7.1.45 pm_agent ProcessThis section describes the services and functions provided by the process pm_agent.

The pm_agent process provides the PMService service.




Issue 10 (2010-09-06)

PMService monitors performance management on all NEs. The performance management isindependent of NEs or objects. Stop PMService if the performance management function is notrequired.


7.1.46 pmexp_agent ProcessThis 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 isindependent 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 ProcessThis 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 figuresand tables.

Required services: PMService

7.1.48 pmncdXX01_agent ProcessThis 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 isPMNCDService0101.

By default, the system saves the performance data of the neighboring cells of the RNC and BSCin files. The database does not hold the data. To view the data of the neighboring cells, you needto import the data from the files to the database and then query the results. ThePMNCDServiceXX01 service imports the performance data of the neighboring cells from thefiles to the database.


Required services: PMService.

7.1.49 porttrunk_agent ProcessThis 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 theM2000 client through a specified port. You need not configure multiple ports on the firewall forcommunication.



7-17


7.1.50 proxy_agent ProcessThis 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 runapplications of the NEs on the LMT .

Stop Proxyserver when the proxy function is not required.


7.1.51 PRSAssistantService_agent ProcessThis section describes the services and functions provided by the PRSAssistantService_agentprocess.

The PRSAssistantService_agent process provides the PRSAssistantService service.

The PRSAssistantService service provides the function of generating reports in .html, .csv or .xlsformat. 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 PRSReportServiceservice.

If you need to run the PRS module, the PRSReportService service cannot be stopped.


7.1.52 prsdc_agent ProcessThis 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 andperformance data files on schedule.

Keep the service running during the operation of the PRS module.


7.1.53 prsfs_agent ProcessThis 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 forimporting report data.

The PRSFsService service provides the function of parsing configuration data files andperformance data files on schedule.

Keep the service running during the operation of the PRS module.





Issue 10 (2010-09-06)

7.1.54 prsreport_agent ProcessThis 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.


7.1.55 prssum_agent ProcessThis 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 andscheduling the data.

If you need to run the PRS module, the PRSSumService service cannot be stopped.

Required services: CMServer.

7.1.56 rn_agent ProcessThis 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 orshort message.

Required service: LicenseService.

7.1.57 ScriptModuleService_agent ProcessThis section describes the services and functions provided by the ScriptModuleService_agentprocess.

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


Required services: ItmService



7-19

7.1.59 sm_agent ProcessThis 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 authorizedusers can gain access to sensitive resources.


Required services: EAMService and LicenseService

7.1.60 snmp_agent ProcessThis section describes the SnmpAgent service and the dependent services. The SnmpAgentservice is provided by the snmp_agent process.

The snmp_agent process provides the SnmpAgent service, that is, the northbound interfaceservice complying with the SNMP protocol.

The SnmpAgent service enables the upper-level NMS to obtain the information on the M2000such as alarm data, through the SNMP protocol.

Required services: LogService and LicenseService.

7.1.61 son_agent ProcessThis 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, suchas automatically detecting, configurating, and optimizing NEs. The DHCP module provides thefunction of automatically detecting the eNodeB, BWA, pBTS3701, NodeB, GSM Pico, PICOBTS, and TGW. The Easy Deployment System (EDS) module provides the function ofautomatically creating an LTE site. The Auto Neighbor Relation (ANR) module provides thefunctions of automatically detecting the neighboring cells of the LTE, querying neighboring cellparameters across cells, and modifying neighboring cell parameters.

If the functions for automatically managing networks are not required, this service can bestopped.

Required service: PMService

7.1.62 swm_agent ProcessThis 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 someNEs. It also provides the download, upload, activation, and rollback functions.






Issue 10 (2010-09-06)

7.1.63 threshold_agent ProcessThis topic describes the function of the ThresholdService service provided by thethreshold_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, thisservice allows you to add, generate, and change a threshold. In addition, this service can generatethreshold alarms.

During the M2000 operation, ensure that the threshold_agent process is operational.

Required services: PMService, SecurityService, and FaultService.

7.1.64 uap_agent ProcessThis 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, whenusers cannot access the BAM server (make sure that the M2000 server normally connects to theBAM), the M2000 client can be started through the agent. The uap_agent process also providesthe function of authenticating user operations to meet the requirement of authority and domainbased management on the M2000.


7.1.65 udpdispatch_agent ProcessThis 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 arereported by NEs monitored by the M2000. The UdpDispatchService service forwards the SnmpTrap 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 ProcessThis 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.


7.1.67 xftpXX01_agent ProcessThis section describes the services and functions provided by the xftpXX01_agent process.



7-21

The xftpXX01_agent process provides the XFTPServiceXX01 service. Through theXFTPServiceXX01 service, the M2000 actively uploads exported files through the northboundinterface to the FTP server on the NMS side.

The XFTPServiceXX01 service actively checks the alarms, configurations, performance filesgenerated by the PMExport service or the pmexp_agent process. Based on the settings of theFTP 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 Northbound alarm file

l Northbound configuration file

l Northbound inventory file

l Northbound performance file

l CME northbound configuration file

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


7.1.68 Processes and Services Related to Each Northbound InterfaceThis section describes the processes and services related to each northbound interface.

Table 7-1 describes the relations between northbound interfaces and their correspondingprocesses and services.

Table 7-1 Relations between northbound interfaces and their corresponding processes andservices

Process Service Northbound Interface

irp_agent IRPService l CORBA configurationinterface

l CORBA alarm interface

l CORBA security interface

l Configuration database

l Performance database

ifms_agent FaultService Northbound alarm fileinterface

pmexp_agent PMExport Northbound performance fileinterface (measurement unit-based)

medXXXX_agent MediationServiceXXXX Northbound performance fileinterface (NE-based)




Issue 10 (2010-09-06)

Process Service Northbound Interface

snmp_agent SnmpAgent Northbound SNMP interface

fmnotify_agent FMNotify Northbound alarm streaminginterface

nms_mml_agent NMSMMLServer Northbound MML interface

cmserver_agent CMServer Northbound inventory fileinterface

cmexp_agent CMExport Northbound configuration fileinterface




ContextChecking the states of the M2000 processes on the M2000 client requires only a few systemresources and does not affect system performance.

Procedure


Step 2 Click the Process Monitor tab to check the monitoring data of the processes running on theM2000 server. See Figure 7-1.



7-23

Figure 7-1 Process Monitor tab page


----End

7.2 Managing M2000 ServicesThis section describes how to view, start, and stop M2000 system services.


7.2.2 Viewing the States of M2000 ServicesThis section describes how to view the states of M2000 services on the M2000 server. Thisoperation consumes a few system resources and does not affect system performance.

7.2.3 Starting the M2000 System ServicesThis section describes how to start the M2000 system services. After you run the start_svccommand, all the M2000 services are started. The system ignores the service that is alreadystarted and starts only the inactive services.

7.2.4 Stopping the M2000 ServicesAfter the M2000 system services are stopped, the performance data and alarm data of themanaged NEs cannot be processed. After the M2000 services are resumed, the M2000 updatesthe data with the NEs and processes the data.





Issue 10 (2010-09-06)



ContextChecking the M2000 services on the M2000 client requires only a few system resources anddoes not affect system performance.

Procedure


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 iconindicates the corresponding process is abnormal.


----End

7.2.2 Viewing the States of M2000 ServicesThis section describes how to view the states of M2000 services on the M2000 server. Thisoperation consumes a few system resources and does not affect system performance.



7-25

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 theservice operate properly.

l In the displayed information, if the state of the service is not running, you can infer thatthe service is abnormal.

Host: 10.121.71.242

Service Agent: 3rdTool_agent [1 service(s)] pid: 15490 3rdToolService [running ]

...

[All Services: 51 ] [Running: 51 ] [Not Running: 0 ]

NOTE

At the end of the displayed information, if the value of Not Running : is 0, you can infer that all theM2000 services operate properly. If another value is displayed, contact Huawei technical supportengineers for assistance.

The M2000 system generates processes and services dynamically during operation. Accordingly, thenumber of processes and services changes dynamically.

----End

7.2.3 Starting the M2000 System ServicesThis section describes how to start the M2000 system services. After you run the start_svccommand, all the M2000 services are started. The system ignores the service that is alreadystarted and starts only the inactive services.


ContextNOTE

The time required for starting M2000 system services is related to the actual environment. Generally, ittakes about 20 minutes.




Issue 10 (2010-09-06)

Procedure

Step 1 Navigate to the installation directory of the M2000 server.


# cd /opt/OMC

Step 2 Run the following commands:

# . ./svc_profile.sh

# start_svc

NOTE

l Before starting the M2000 server, ensure that the Sybase service is started. For details about how tostart the Sybase service, see 14.2.2 How to Start the Sybase.

l When you start M2000 system services, the status of each service is displayed. If the status of a serviceis failed, it indicates that the service fails to be started. In this case, you can locate the fault by viewingthe iMAP.troubleshooting.trace log.

# more /export/home/omc/var/logs/iMAP.troubleshooting.trace

----End

7.2.4 Stopping the M2000 ServicesAfter the M2000 system services are stopped, the performance data and alarm data of themanaged NEs cannot be processed. After the M2000 services are resumed, the M2000 updatesthe data with the NEs and processes the data.


ContextNOTE

The time required for stopping M2000 system services is related to the actual environment. Generally, ittakes 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:


# stop_svc

Step 3 Run the following command to check whether there is any output.

# svc_ps



7-27

l If no output exists, it indicates that the M2000 service processes are stopped. Perform Step5 directly.

l 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 8directly.

l 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 If no output exists, it indicates that the M2000 services are stopped.

l If any output exists, run the stop_tao_services command to stop the TAO process.

----End




Issue 10 (2010-09-06)

8 Managing the M2000 Databases

About This Chapter

This chapter describes how to manage the M2000 databases.

8.1 M2000 DatabaseThe M2000 databases consist of the Sybase database and the M2000 server database. Thischapter describes only the M2000 server database. After the installation of the M2000 serverapplication software, the size of the M2000 server database is fixed. You can use Sybasecommands to operate the M2000 server database.

8.2 Viewing the States of M2000 DatabasesThis section describes how to view the states of M2000 databases. You can run Sybasecommands on the server to view the states of M2000 databases. Alternatively, you can view thedatabase states using the system monitor browser.

8.3 Clearing M2000 DatabasesThis section describes how to dump the data in the M2000 databases. The data includes theperformance data, NE operation logs, NE system logs, NE security logs, alarm data, NMoperation logs, NM system logs, and NM security logs. You can configure an integrated taskfor dumping the data in the M2000 databases.

8.4 Backing Up M2000 DatabasesThis section describes how to back up the M2000 databases. The M2000 databases arecategorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb,pmcomdb, sumdb, farsdb and omceamdb.

M2000Administrator Guide (Sun, S10) 8 Managing the M2000 Databases


8-1

8.1 M2000 DatabaseThe M2000 databases consist of the Sybase database and the M2000 server database. Thischapter describes only the M2000 server database. After the installation of the M2000 serverapplication software, the size of the M2000 server database is fixed. You can use Sybasecommands 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 featureimplementation. The omcdb database must exist in the M2000 system.

l omclogdb: stores log management data. The omclogdb database must exist in the M2000system.

l omcsmdb: stores security management data. The omcsmdb database must exist in theM2000 system.

l omctmdb: stores topology management data. The omctmdb database must exist in theM2000 system.

l fmdb: stores the alarm data of the M2000 and NEs. The fmdb database must exist in theM2000 system.

l pmdb: stores the performance structure tables and performance measurement results ofNEs. The pmdb database must exist in the M2000 system.

l swmdb: stores the files managed by the software management module and the configurationdata related to NE versions. The swmdb database must exist in the M2000 system.

l pmcomdb: stores the static performance measurement data of NEs. The pmcomdb databasemust exist in the M2000 system.

l sumdb: stores the summary data of NEs. If the M2000 system is not configured with thePRS, the sumdb database does not exist.

l itfndb: When installing northbound components, you must create the itfndb database forstoring the northbound configuration data, performance tasks, and performance thresholddata. The itfndb database must exist in the M2000 system.

l farsdb: stores the signaling data of all the NEs managed by the M2000. If the M2000 systemis not configured with the tracing function, the farsdb database does not exist.

l omctempdb: stores the buffer data required for internal implementation of theDesktopServiceXXXX service. The omctempdb database must exist in the M2000 system.

l 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 DatabaseThe farsdb database stores the signaling data of all the NEs managed by the M2000.

8.1.2 fmdb DatabaseThis section describes the fmdb database, which stores the alarm data of the M2000 and themanaged NEs.

8.1.3 itfndb DatabaseThis section describes the itfndb database, which stores the northbound configuration data,performance tasks, and performance threshold data.

8.1.4 omcdb Database

8 Managing the M2000 DatabasesM2000



Issue 10 (2010-09-06)

This section describes the omcdb database. The omcdb database stores the M2000 configurationdata, security data, and internal data.

8.1.5 omceamdb DatabaseThis section describes the omceamdb database. The omceamdb database is used to store the dataof network management objects, such as NEs, subnets, and links.

8.1.6 omclogdb DatabaseThis section describes the omclogdb database, which stores the M2000 log management data.

8.1.7 omcsmdb DatabaseThis section describes the omcsmdb database, which stores the security management data.

8.1.8 omctempdb DatabaseThis section describes the omctempdb database. The omctempdb database is used to store thebuffer data required for internal implementation of the DesktopServiceXXXX service.

8.1.9 omctmdb DatabaseThis section describes the omctmdb database, which stores the topology management data.

8.1.10 pmcomdb DatabaseThe pmcomdb database is used for storing the static performance measurement data of NEs.

8.1.11 pmdb DatabaseThis section describes the pmdb database, which stores the performance structure tables andperformance measurement results of NEs.

8.1.12 sumdb DatabaseThe sumdb database stores the summarized performance data of NEs for performance reports.

8.1.13 swmdb DatabaseThis section describes the swmdb database, which stores the file information about the softwaremanagement module and the configuration data of NE versions.

8.1.1 farsdb DatabaseThe 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 notavailable.

The farsdb database consists of the following types of tables:

l Static configuration data table

l Task table

l 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 Function

tbl_ProcessorInfo Static service configuration table



8-3

Table Name Function

tbl_Field Static field configuration table

tbl_TaskInfo Dynamic task record table

tbl_TaskNE Table recording the tasks reported to NEs

Message type name_taskID

Task data table created dynamically, which records the signalingdata of the message type corresponding to a task

8.1.2 fmdb DatabaseThis section describes the fmdb database, which stores the alarm data of the M2000 and themanaged 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 Function

tbl_alm_log Records alarm logs.

tbl_event_log Records event logs.

Other tables 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 alarmsand events. For example, the fmdb database may contain multiple alarm log tables such as tbl_alm_log_1and tbl_alm_log_2.

8.1.3 itfndb DatabaseThis 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 thename and function of each table.

Table 8-3 Tables of the itfndb database and the corresponding functions

Table Name Function

tbl_JGeneralInfo Records the general information about tasks.

tbl_JMoInstance Records the instances of tasks.

tbl_JStatusRecord Records the Status of tasks.




Issue 10 (2010-09-06)

Table Name Function

tbl_JMeasurementCategory Records the measurement categories of tasks.

tbl_JSchedule Records the task scheduling.

tbl_MGeneralInfo Records the general information about thresholds.

tbl_MMoInstance Records the instances of thresholds.

tbl_MMeasurementCategory Records the measurement categories of thresholds.

tbl_MThresholdPackElemen Records the details of thresholds.

tbl_MAlarmRecord Records the alarm records of thresholds.

tbl_MStatusRecord Records the status of thresholds.

Other tables Records the information about northboundimplementation.

8.1.4 omcdb DatabaseThis section describes the omcdb database. The omcdb database stores the M2000 configurationdata, 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 Function

Tables with moi_ as theprefix

Records the information about MO examples.

Tables with mos_ver_ asthe prefix

Records the information about versions.

Tables with nbmmlNe_as the prefix

Records the information about the format of messages transferredbetween the and the NEs.

Tables with ne2_ as theprefix

Records the information about NE models.

Tables with omc_ as theprefix

Records the data about network management.

Tables with rel_ as theprefix

Records the associations between MOs.

tbl_ADAllNeList Records the information about the NodeBs to be commissioned.

tbl_ADNeStatus Records the information about the statuses of the NodeBs to becommissioned.



8-5

Table Name Function

tbl_AllNeInfo Records the network management data. It is created to ensure thatthe M2000 is compatible with earlier versions.

tbl_IPExg Records the IP configuration information about the NATtranslation table.

tbl_OmcSslOption Records the SSL connection policy of the OMC for NEs.

tbl_nelicBaseInfo Records the basic information about NEs.

tbl_nelicTask Records the information about operation tasks.

tbl_nelicTaskEnv Records the information flow interacted between the M2000server and client.

tbl_test_task_property Records the properties of the IPQoS test task.

tbl_test_local_path Records the intra-office test path.

tbl_test_other_path Records the inter-office test path.

tbl_test_log_result Records the test task logs.

tbl_test_ping_report Records the signaling parameters on the bearer network.

tbl_test_audit_result Records the audit results of calling and called parties on the bearernetwork.

tbl_test_nblink_result Records the audit result of the call completion rate on the bearernetwork.

tbl_test_ping_address Records the information about address pairs sent by the host.

tbl_SubareaInfo Refers to the partition information table, which records theinformation about each node.

tbl_SubareaRes Refers to the partition resource table, which records the resourcesof each node.

session_SessionEntity Records the information about the operated NEs during a session.

session_SessionMoc Records the information about the operated MOCs during asession.

session_SessionOpInfo Records the information about the user operations during asession.

Other tables Records other configuration data of the M2000.

8.1.5 omceamdb DatabaseThis section describes the omceamdb database. The omceamdb database is used to store the dataof network management objects, such as NEs, subnets, and links.

The omceamdb database requires more than 500 MB disk space.




Issue 10 (2010-09-06)

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 Function

tbl_sn Subnet information table

tbl_ne NE information table

tbl_nefeature NE feature table

tbl_link Link information table

tbl_idresource NMS object identification management table

tbl_sntype Subnet type table

tbl_netype NE type table

tbl_linktype Link type table

tbl_sync Data synchronization table

tbl_nerelation NE relation table

tbl_maintenanceinfo Maintenance personnel information table

tbl_locationinfo Device maintenance information table

tbl_negroup NE group information table

tbl_negroupclass NE group mode table

tbl_negroup2ne NE group and NE relation table

tbl_negrouptype NE group type table

tbl_devsnmppara SNMP device parameter table

tbl_dftsnmppara Default SNMP parameter table

tbl_autodiscfilter Auto-search IP filter table

tbl_autodischistory Auto-search history record table

tbl_eamschedule Scheduled-search parameter table

tbl_autodiscresult Auto-search result table

8.1.6 omclogdb DatabaseThis 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.



8-7

Table 8-6 Names and functions of the tables in the omclogdb database

Table Name Function

tbl_Audit Records the logs of user operations.

tbl_SysLog Records the logs of system operations.

tbl_SysLogResultDef Records the result information about system logs.

tbl_SysLogStaticInfo Records the static information about system logs.

Other tables Records the information about other logs.

8.1.7 omcsmdb DatabaseThis 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 Function

tbl_AccessTable Records the binding relations between usergroups and privileges.

tbl_AccessViewNodeRelTable Records the relations between the privilegedisplay nodes.

tbl_AccessViewNodeTable Records the privilege display nodes.

tbl_IDTable Records the reclaimed IDs.

tbl_SMAccessPolicyItem Records the privilege statistics for binding usergroups.

tbl_SMGroup Records the basic information about user groups.

tbl_SMGroupUserMap Records the binding relations between usergroups and users.

tbl_SMLoginRec Stores the history records on user login.

tbl_SMNEUser Records the basic information about NE users.

tbl_SMPrivateGroupUserMap Records the binding relations between privategroups and users.

tbl_SMSecurityPolicy Records the security policy.

tbl_SMTerm Records the basic information about terminals.

tbl_SMUser Records the basic information about users.

tbl_SMUserHistoryRec Records history user passwords.




Issue 10 (2010-09-06)

Table Name Function

tbl_SMUserNEUserMap Records the binding relations between users andNE users.

tbl_SMUserTerminalMap Records the binding relations between users andterminals.

tbl_SecurityObjectTable Records security objects.

tbl_SessionIDTable Records session IDs.

tbl_StaticTypeRelationTable Records the relations between privileges.

tbl_StaticTypeTable Records the static security information aboutobject types, privileges, and operations.

tbl_StaticTypeViewTable Records the static security information.

8.1.8 omctempdb DatabaseThis section describes the omctempdb database. The omctempdb database is used to store thebuffer 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 Function

tbl_instancename_subsystemname_function name

Stores the buffer data required for internal implementation of theDesktopServiceXXXX service.

8.1.9 omctmdb DatabaseThis 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 Function

MOTSConfig Records the topology configuration values, including the initialvalue and the maximum value assigned by ObjID.

MOTSDomain Records the information on topology domains.



8-9

Table Name Function

MOTSLink Records the information on topology links.

MOTSNode Records the information on topology NEs.

MOTSSubnet Records the information on topology subnets.

MOTSSubtree Records the information on the topology tree.

MOTSVSubnet Records the information on topology logical subnets.

MOTSView Records the information on topology views.

MOTSViewObj Records the information on topology view objects.

TSTempLoc Records the temporary table that stores the longitude and latitudecoordinates of the e-map.

TSTempPos Records the temporary table that stores the x-axis and y-axiscoordinates of common physical topology.

8.1.10 pmcomdb DatabaseThe 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 Counter tables

l Template Tables

l 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-10lists the name and function of each table.

Table 8-10 Counter information tables in the pmcomdb database and the correspondingfunctions

Table Name Function

systbl_NeType Records all possible NE types in M2000.

systbl_FunctionSet Records the function sets of all NEs.

systbl_FunctionSubSet Records the measurement units of allfunction sets.

systbl_Counters Records all measurement counters.




Issue 10 (2010-09-06)

Table Name Function

systbl_Counter_Unit Records the units of all counters.

systbl_AllCounterCategory Records the service features of eachversion.

systbl_ComputeCounters Records only the counters involved incalculation.

Template TablesTemplate tables contain several tables that record measurement information. Table 8-11 liststhe name and function of each table.

Table 8-11 Template information tables in the pmcomdb database and the correspondingfunctions

Table Name Function

tbl_ObjectInstance Records measurement objects.

tbl_MeasurementPeriod Records measurement periods.

tbl_MeasurementCounter Records measurement counters.

tbl_MeasurementSuspendInfo Records the information on suspendedtasks.

tbl_CounterCategory Records the status of each service feature.

tbl_CounterLevel Records the status of each service counter.

tbl_FeatureStatus Records the status of all the servicefeatures on the M2000 operatingenvironment.

Function Subsets and Period TablesThe measurement results are saved according to the function subset and period. Table 8-12 liststhe name and function of each subset and table.



8-11

Table 8-12 Function subsets and period tables in the pmcomdb database and their functions

Table Name Function

tbl_MeasObject_XXX_Y In the table name, XXX refers to the functionsubset ID and Y refers to the period index thatranges from 0 to 4. By comparing thetbl_MeasObject_XXX_Y with the resulttable named tbl_Result_XXX_Y, you cancheck the loss status and integrity of theresults.Each time when the measured object changes,a message is recorded in the list.

8.1.11 pmdb DatabaseThis section describes the pmdb database, which stores the performance structure tables andperformance measurement results of NEs.

The pmdb database stores the NE performance measurement data. A disk space of more than13,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 dataoverwrites 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 mustchange the number of days till when the data can be stored. Otherwise, the pmdb database issuspended and it cannot process any performance data from the NEs. Change the number ofsaving 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. Observe the usage of the pmdb database when the M2000 runs for half a month.2. Calculate the space of the pmdb database used a day.3. Calculate the number of days that the pmdb database lasts.

The pmdb database consists of the following types of tables:

l Template Tables

l Function Subsets and Period Tables

Template TablesTemplate tables record measurement information. Table 8-13 lists the name and function of thetable.




Issue 10 (2010-09-06)

Table 8-13 Template tables in the pmdb database and their functions

Table Name Function

tbl_SyncInfo Records the supplementary collection queues ofperformance results.

Function Subsets and Period Tables

The pmdb database stores the tables of measurement results categorized by function subsets andperiods. 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 correspondingfunctions

Table Name Function

tbl_Result_XXX_Y Records periodic results. In the table name, XXX isthe ID of the function subset and Y is the period indexbetween 0 and 4.

8.1.12 sumdb DatabaseThe 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, atleast 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 Object type information table

l System setting information table

l Report information table

l Performance result table

Object Type Information Table

The object type information table consists of 12 tables, which save a group of relatively stableinformation. 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 Function

t_NeType Records the NE type and manages therelevant information.



8-13

Table Name Function

t_PRSObjectType Records the information about object typesof each class.

t_GroupObjType Records the information about object typesof object groups.

t_AttrObjType Records the information about object typesof attribute classes.

t_ConfigObjType Records the information about object typesof configuration classes.

t_ConfigObjTypeAttr Records the attribute information about theconfiguration object type.

t_CombObjType Records the information about object typesof combination classes.

t_PmObjType Records the relation between the PRS objecttype and the performance object type.

t_CombTable Records the rule information about thecombination table.

t_FSS Records the information about the extractedfunction subsets.

t_Item Records counter information.

t_ObjTypeAggrRelation Records the summarization relation betweenobjects.

System Setting Information Table

The system setting information consists of 15 tables that record information related to systemsetting. 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 Function

t_Week Records the start date of a week.

t_SpecialDate Records the definition information aboutspecial dates.

t_BusyRule Records the information about busy-hourplanning.

t_BusyTime Records the information about busy hours.

t_BusyTimeArith Records the information about the statisticson monthly busy hours.




Issue 10 (2010-09-06)

Table Name Function

t_DefaultPeriod Records the information about defaultperiods.

t_RawPeriod Records the information about the extractionperiod of original results.

t_DefaultStorage Records the default storage duration ofresults.

t_CustomStorag Records the storage duration of results.

t_LoadFlag Records the information about thesummarization and extraction.

t_MaxItemId Records the IDs of maximum availablecounters of NEs.

t_RawHistoryInf Records the history of extracting originalresult tables.

t_RawResultNo Records the result numbers of original resulttables.

t_SumHistoryInfo Records the history of extractingsummarization result tables.

t_BusyHistoryInfo Records the information about busy-hoursummarization result tables.

Report Information TableThe report information table consists of eight tables that record the information about the queriedtables. 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 Function

t_Report Records the information about reports.

t_Sheet Records the information about the sheets.

t_SheetItem Records the counters of sheets.

t_SheetFilter Records filtering information.

t_ItemFormat Records the counter format information.

t_RelateReport Records the relation between reports.

t_TemplateInfo Records the basic information about thetemplates.



8-15

Table Name Function

t_TemplateObjInfo Records the basic information about thetemplates and the objects.

Performance Result TableThe performance result table consists of multiple tables, which records the performancemeasurement results based on the function subset and the measurement period. Table 8-18 liststhe name and function of each table.

In Table 8-18, fssName, ObjLevel, and XXX in the tables whose names begin with d_ can beconfigured in the configuration file.

l fssName refers to the name of a function subset.

l ObjLevel refers to the dimension of an object.

l 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 Function

f_fssName_Raw Indicates original result serial tables whichrecord the original results.If the function subset is not extractedinternally, the administration tool (AT)automatically names the function subset inthe following format: F _ ID of the functionsubset.

f_fssName_ObjLevel_H Indicates hourly serial tables which recordsthe result information at hour dimension.The hourly summarization is based on theoriginal results.

f_fssName_ObjLevel_D Indicates daily serial tables which record theresult information at day dimension. Thehourly summarization is based on hourlysummarization.

f_fssName_ObjLevel_W Indicates daily serial tables which record theresult information at week dimension. Theweekly summarization is based on dailysummarization.

f_fssName_ObjLevel_M Indicates monthly serial tables which recordthe result information at month dimension.The monthly summarization is based onweekly summarization.

f_fssName_ObjLevel_WH Indicates the weekly busy-hour serial tableswhich record the weekly busy-hour results.




Issue 10 (2010-09-06)

Table Name Function

f_fssName_ObjLevel_MH Indicates the monthly busy-hour serial tableswhich record the monthly busy-hour results.

d_XXX Records the information about the objects tobe configured.

d_XXXGrp Records the information about the type ofobject groups.

d_XXXGrpObject Records the information about objectinstances of object groups.

8.1.13 swmdb DatabaseThis section describes the swmdb database, which stores the file information about the softwaremanagement module and the configuration data of NE versions.

The swmdb database stores the files managed by the software management module and the NEversion configuration data. A disk of more than 3,000 MB is required for storage. Table 8-19lists the name and function of each table.

Table 8-19 Tables of the swmdb database and the corresponding functions

Table Name Function

tbl_FTPFileSet Records the files managed by the software managementmodule.

tbl_VersionRelation Records the information about version relations.

tbl_NELogTable Records the NE operation logs.

8.2 Viewing the States of M2000 DatabasesThis section describes how to view the states of M2000 databases. You can run Sybasecommands on the server to view the states of M2000 databases. Alternatively, you can view thedatabase states using the system monitor browser.

8.2.1 Checking the Database Usage Information About the M2000 Server Through the M2000ClientThis section describes how to check the database status through the M2000 client to know theusage of the databases.

8.2.2 Viewing the Database Usage of the M2000 Server Using Sybase CommandsThis section describes how to view the database status of the M2000 server by using Sybasecommands. This operation requires very few system resources and does not affect systemoperation.



8-17

8.2.1 Checking the Database Usage Information About the M2000Server Through the M2000 Client

This section describes how to check the database status through the M2000 client to know theusage of the databases.



ContextThis operation requires only a few system resources and does not affect system operation.

Procedure


Step 2 Click the Database Monitor tab to check the database status of the M2000 server. See Figure8-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; thered icon indicates that the usage of the corresponding database is abnormal. If the usage of a databaseexceeds the preset threshold, the icon in this column changes from green to red.


----End




Issue 10 (2010-09-06)

8.2.2 Viewing the Database Usage of the M2000 Server UsingSybase Commands

This section describes how to view the database status of the M2000 server by using Sybasecommands. This operation requires very few system resources and does not affect systemoperation.

Prerequisitel You have logged in to the M2000 server as user dbuser.

l The Sybase service is running.

ContextIn addition to the method described in 8.2.1 Checking the Database Usage Information Aboutthe M2000 Server Through the M2000 Client, you can use the Sybase commands to view thedisk 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 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB dbuser 17050 1 0 Dec 11 ? 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 owner dbid created status

------------ ------------- ------ ------ ------------------ ------------------------------------------------------------------------------------------------------------------------- pmdb 13000.0 MB sa 9 Mar 13, 2007 select into/bulkcopy/pllsort, trunc log on chkpt



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,000MB, where 10,000 MB is used for storing performance data and 3,000 MB is used for storingthe 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. Basedon the database usage and the preset threshold, you can determine whether the database statusis normal.

Run the following command to exit:

1>exit

----End

8.3 Clearing M2000 DatabasesThis section describes how to dump the data in the M2000 databases. The data includes theperformance data, NE operation logs, NE system logs, NE security logs, alarm data, NMoperation logs, NM system logs, and NM security logs. You can configure an integrated taskfor dumping the data in the M2000 databases.

Prerequisitel You have logged in to the M2000.

l You are authorized to clear the M2000 databases.

Contextl Dump conditions can be set according to the following aspects: execution type, execution

time, and file saving format.

l After the data is dumped, the following data is saved in the default directory of theM2000 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




Issue 10 (2010-09-06)

Procedure

Step 1 Dump the performance data in the pmdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. In the left part of the Task Management window, select Performance Data under the

Database Capacity Management node from the Task Type navigation tree.3. Select a task in the right part of the Task Management window, and then click

Attribute.4. In the Attribute dialog box, set the dump parameters. Then, click OK.

Step 2 Dump the NE operation logs in the swmdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. 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.3. Select a task in the right part of the Task Management window, and then click


Step 3 Dump the NE security logs in the swmdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. 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.3. Select a task in the right part of the Task Management window, and then click


Step 4 Dump the NE system logs in the swmdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. 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.3. Select a task in the right part of the Task Management window, and then click


Step 5 Dump the alarm data in the fmdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. In the left part of the Task Management window, select Alarm Data under the node

Database Capacity Management from the navigation tree Task Type.3. Select a task in the right part of the Task Management window, and then click

Attribute.



8-21

4. In the Attribute dialog box, set the dump parameters. Then, click OK.

Step 6 Dump the NM operation logs in the omclogdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. 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.3. Select a task in the right part of the Task Management window, and then click


Step 7 Dump the NM system logs in the omclogdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. In the left part of the Task Management window, select NM System Log Dump under



Step 8 Dump the NM security logs in the omclogdb database.1. On the GUI of the M2000 client, choose Maintenance > Task Management.

The Task Management window is displayed.2. In the left part of the Task Management window, select NM Security Log Dump under



----End

8.4 Backing Up M2000 DatabasesThis section describes how to back up the M2000 databases. The M2000 databases arecategorized into omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb, omcsmdb, omctmdb,pmcomdb, sumdb, farsdb and omceamdb.


l You are authorized to back up the M2000 system.




Issue 10 (2010-09-06)

ContextNOTE

The time required for backing up data is related to the actual environment. Generally, it takes about fivehours.

Do not suspend a periodic backup task. The reasons are as follows:

l The latest data fails to be restored after data lost caused by an accident, for example, the power-off ofthe server.

l 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-clickthe 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 Figure8-3.



8-23


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 followingoperations 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 withanother 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 thebackup operation.After you insert a new tape, the system continues to back up the M2000 dynamic data.




Issue 10 (2010-09-06)

NOTE

l 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 If the newly inserted tape is fully written again, you need to insert another tape for backup. Inthis way, change tapes until all the data is backed up.

l After backing up the dynamic data on the tape, you can run the following command to view thecontents of the tape:

# gtar tf /dev/rmt/0

----End



8-25

9 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.2 Managing Files and Disks on the M2000 ServerThis section describes how to manage the file systems and disks on the M2000 server.

M2000Administrator Guide (Sun, S10) 9 Managing the M2000 Files and Disks


9-1





The client software runs on the Windows operating system and is based on the JAVA virtualmachine. The installation package of the M2000 client software includes the JAVA virtualmachine supported by Windows.

Required client disk space (only for reference): F = I + T + (S x N), where I refers to the size ofthe 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 10MB; 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


client installation path Refers to the M2000 client installation path. Thedefault path is C:\iManagerM2000Client.

M2000 client installation path\client Refers to the directory for saving clientprograms.

M2000 client installation path\client\bin Refers to directory where executable files arelocated.

M2000 client installation path\client\Data

Refers to the directory for saving the NEconfiguration files.

M2000 client installation path\client\diagnosis

Refers to the directory for saving theinformation that is used for locating problems.NOTE

This directory appears only after you run theM2000 diagnosis tool.

M2000 client installation path\client\ext_runcfg

Refers to the directory where the files related tointegrated components are located.

M2000 client installation path\client\dtd Refers to the directory for saving the Dtd files.

9 Managing the M2000 Files and DisksM2000



Issue 10 (2010-09-06)


M2000 client installation path\client\help Refers to the directory for saving the online helpfiles.

M2000 client installation path\client\IDAPI32

Refers to the directory for saving the localWSdynamic link libraries.

M2000 client installation path\client\lib Refers to the directory for saving the libraryfiles.

M2000 client installation path\client\localWs

Refers to the directory for saving LocalShellthat is used to start the 2G LMT.

M2000 client installation path\client\style

Refers to the directory for saving theconfiguration files of client.

M2000 client installation path\client\Templates

Refers to the directory for saving the mappingbetween administrative regions and their IDs.

M2000 client installation path\client\tmp Refers to the directory for saving temporaryfiles during the upgrade.

M2000 client installation path\client\tracefile

Refers to the directory for saving the trace files.

M2000 client installation path\client\update

Refers to the directory for saving the upgradefiles.

M2000 client installation path\client\cbb Stores the CBB files of the M2000 client.

M2000 client installation path\client\configuration

Stores the configuration files of the M2000client.

M2000 client installation path\client\features

Stores the feature configuration files of thesubsystems of the M2000 client.

M2000 client installation path\client\plugins

Stores the configuration files of the subsystemsof the M2000 client as plug-ins.

M2000 client installation path\uninstall Refers to the directory for saving the uninstaller.

M2000 client installation path\script Refers to the root directory of the iSStar script.

M2000 client installation path\client\bin\run

Refers to the directory in which the files forconfiguring the startup parameters of the clientand components are located.



9-3


M2000 client installation path\cau Refers to the installation directory of the cau(Client Auto Upgrade) client software and thedirectory in which the version, documentabstract, and group information about theM2000 client are located.NOTE

l The cau(Client Auto Upgrade) client softwareprovides an upgrade detection mechanism that isbased on the document abstract. It also comparesthe document abstract of the server with that of theclient. If the document abstracts are not consistent,you need to upgrade the client.

l Based on the group information, the server groupsand packs all the client documents deployed on theserver for the client to download, install, andupgrade. Based on the group information, theclient also groups and packs all client files. Thus,when these files are being downloaded, they canbe compared with those files grouped and packedby the server.

M2000 client installation path\jre Stores the Java virtual machine of the M2000.

M2000 client installation path\lib Stores the library files of M2000 client, remotenotification client, script framework tool clientand datamanager client.


Context

CAUTIONYou 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 Trace logs

l Temporary files after the running of the M2000 log collector

Procedurel Delete the trace logs.




Issue 10 (2010-09-06)

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

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 collectorand are saved in the directory M2000 client installation path\client\diagnosis.

----End

9.2 Managing Files and Disks on the M2000 ServerThis section describes how to manage the file systems and disks on the M2000 server.

9.2.1 Introduction to the M2000 Server File SystemThis introduces the structure of the M2000 server files and the planning of disk partition forvarious server types. The server communicates with the NEs, stores the operation andmaintenance 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 ClientThis section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client.

9.2.3 Viewing the Disk Usage of the M2000 Server Using Solaris CommandsThis section describes how to use Solaris commands for viewing the disk usage of the M2000server. This task uses very few system resources and does not affect the system operation.

9.2.4 Clearing the Disk Space of the M2000 ServerThis section describes how to clear the disk space of the M2000 server. Before clearing diskspace, ensure that the files to be deleted are useless. Deleting a useful file by mistake may leadto a system failure.

9.2.1 Introduction to the M2000 Server File SystemThis introduces the structure of the M2000 server files and the planning of disk partition forvarious server types. The server communicates with the NEs, stores the operation andmaintenance data of the NEs, and provides an interface to the NMS.

The M2000 server runs on the Solaris platform. The M2000 system operation requires thefollowing software:

l Sybase database

l CORBA supporting software

l FTP supporting software

The installation package of the M2000 server software includes the software providing the FileTransfer Protocol (FTP) and Common Object Request Broker Architecture (CORBA) functions.

Table 9-2 lists the directories related to the M2000 server software.



9-5

Table 9-2 Directories related to the M2000 server software


M2000 server installation directory M2000 server installation directory is theinstallation directory of the M2000 serversoftware. By default, the installation directory is /opt/OMC.

M2000 server installation directory/bin

Refers to directory where executable files arelocated.

M2000 server installation directory/etc Refers to the directory where the systemconfiguration files and structured query language(SQL) scripts are located.

M2000 server installation directory/lib Refers to the directory where library files arelocated.

M2000 server installation directory/lbin

Refers to the directory where the systemadministration commands are located.

M2000 server installation directory/3rdTools

Refers to the directory where third-party softwareis located.

M2000 server installation directory/var

Refers to the directory where the log files, theperformance files, and the files recording exportedalarms are located.

M2000 server installation directory/data

Refers to the directory where the compressedcomponent files are located.

M2000 server installation directory/init

Refers to the directory where the initializationscript file that should be executed during theM2000 installation is located.

M2000 server installation directory/uninstall

Refers to the directory where the script file usedfor uninstalling the M2000 is located.

M2000 server installation directory/install

Refers to the directory where the script files usedfor installing the M2000 are located.

M2000 server installation directory/webapps

Refers to the directory for saving the webpageservice files.

M2000 server installation directory/med

Refers to the directory for saving the mediationfiles generated during the operation.

M2000 server installation directory/resourcemonitor

Refers to the directory for saving resourcemonitoring files.

M2000 server installation directory/tomcat

Refers to the directory for saving the configurationdata of the webpage server.

M2000 server installation directory/components

Refers to the PRS control directory.




Issue 10 (2010-09-06)


M2000 server installation directory/medshare

Refers to the directory for saving the mediationfiles.

M2000 server installation directory/sacscript

Refers to the directory for saving the script filesprovided by the NIC module.

M2000 server installation directory/ds Refers to the directory for saving the files relatedto the DesktopService service.

M2000 server installation directory/plugin

Refers to the directory for saving the dynamiclibrary files and configuration files related to plug-in.

M2000 server installation path/upgrade

Refers to the directory for saving the upgradescripts.

M2000 server installation directory/res Refers to the directory where resource files arelocated.

M2000 server installation directory/hascript

Refers to the directory for saving the platformscript files.

M2000 server installation directory/tools

Refers to the directory where the script tools oftenused by the M2000 are located.

/export/home/omc/var Refers to directory where the M2000 operationdata is located.

/export/home/omc/var/syslog Refers to the directory where system logs arelocated.

/export/home/backup Refers to the directory where backup files arelocated.

/export/home/sysm/ftproot/pm Refers to the directory where the trafficmeasurement data of each NE, which is reportedas files, is located.

M2000 server installation path/var/itf_n/FileTransferIRP/PM

Refers to the directory where the northboundCORBA interface performance files are located.

/export/home/omc/var/fileint/cm Refers to the directory where the configurationdata files that are periodically exported are located.

/export/home/omc/var/fileint/pm Refers to the directory where the exportedperformance result files are located.

/export/home/sysm/ftproot/NE name/Software

Refers to the directory where the NE versionpackage is located.



9-7


/export/home/sysm/ftproot/NE name/Data/NE fdn

Refers to the directory where the NE data backupis located.NOTE

l The NE fdn is a code representing an NE sample inthe program.

l The data generated for manual backup is located inthe BAKDATA****** directory. The data generatedfor automatic backup is located in theAUTOBAKDATA****** directory.

/export/home/omc/var/logs Refers to the directory where M2000 log files arelocated.

/opt/sybase/ASE-15_0/install Refers to the directory where Sybase log files arelocated.

/var/adm Refers to the directory where Solaris log files arelocated.

/export/home/backup/omc Refers to the directory where the backup files ofdynamic data are located.

/export/home/omc/var/etc/conf/license

Refers to the directory where the license file of theM2000 is located.

Sun Netra 240 Disk PartitionA standard disk on the Netra 240 server in the M2000 system should be configured with two146 GB hard disks and partitioned according to Table 9-3.

Table 9-3 Planning of the server disk partitions (Netra 240)

HardDisk No.

Partition No.

Partition Name Size (MB) Description

1 0 / 25000 Root partition

1 swap 8192 Data exchangepartition

2 overlap - Disk mapping. Retainthe default size.

3 /data 39000 Application databasepartition

4 /log 14000 Application databasepartition

5 /export/home 50000 M2000 operation datapartition




Issue 10 (2010-09-06)

HardDisk No.

Partition No.


6 /globaldevices 1024 Reserved

7 - 10 to 260 Used for diskmirroring. You neednot set the partitionname and size. Thesystem assigns thepartition sizeautomatically.

2 Used as the mirrored disk for the first hard disk

Sun Fire V890 Disk Partition and Disk Array PartitionA standard disk on the V890 in the M2000 system should be configured with six 146GB harddisks 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 DiskNo.

Partition No.


1

0 / 110000 Root partition



3 - - -

4 - - -

5 - - -


7 - 10 to 260 Used for diskmirroring. You neednot set the partitionname and size. Thesystem assigns thepartition sizeautomatically.


The disk array consists of sixteen 146 GB hard disks. Two disks on the disk array are used forhot spares, and the remaining 14 disks are used for RAID5. Hot spares are used to replace the



9-9

faulty disks in the disk array. Two volumes are created on the 6140 disk array, and their size arethe 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. Volume Name Size (GB)

1 oss_v0 810

oss_v1 810

Sun Fire E4900 Disk Partition and Disk Array PartitionA standard disk on E4900 server in the M2000 system is configured with two 146 GB hard disksand one 6140 disk array. Table 9-6 lists the partitions of local disks.

Table 9-6 Planning for disk partitioning on the server (E4900)

HardDiskNo.

Partition No.



1 swap 20000 Data exchange partition


3 - - -

4 - - -

5 - - -


7 - 10 to 260 Used for disk mirroring.You need not set thepartition name and size.The system assigns thepartition sizeautomatically.


The 6140 disk array consists of sixteen 146 GB hard disks. Two disks on the disk array are usedfor hot spares, and the remaining 14 disks are used for RAID5. Hot spares are used to replacethe faulty disks in the disk array. Two volumes are created on the 6140 disk array, and their sizeare the same. For details on how to plan volumes on the disk array, see Table 9-7.




Issue 10 (2010-09-06)

Table 9-7 Planning for the 6140 disk array

Disk Array No. Volume Name Size (GB)

1 oss_v0 810

oss_v1 810

Sun T5220 Disk Partition

The Sun T5220 server is configured with four 146 GB disks, you can see Table 9-8 for theplanning of the disk partitions.

Table 9-8 Planning of the Sun T5220 server disk partitions

Hard Disk No. Partition No. PartitionName

Size (MB) Description



2 overlap - Disk mapping.Keep thedefault size.

3 - - -

4 - - -

5 - 96256 M2000operation datapartition. Nopartition nameis needed.


7 - 10 to 260 Used for diskmirroring. Youneed not set thepartition name.

2 Used as the mirroring disk for the first hard disk

3 0 - - -

1 - - -

2 overlap - Disk mapping.Keep thedefault size.

3 - 102400 Sybase data



9-11

Hard Disk No. Partition No. PartitionName

Size (MB) Description

4 - 35840 Sybase log

5 - - -

6 - - -

7 - 10 to 260 Used for diskmirroring. Youneed not set thepartition name.

4 The third and the fourth hard disks serve as hardware RAID1 for theM2000 operation data.

Sun M4000/M5000 Disk Partition and Disk Array PartitionA standard disk in the M4000/M5000 system should be configured with two 146 GB hard disksand one S3200 or S2600 disk array. The S3200 disk array consists of 16 x 146 GB hard disksand the S2600 disk array consists of 12 x 450 GB hard disks. The two local hard disks arepartitioned according to Table 9-9.

Table 9-9 Partitioning of the local server disks (M4000/M5000)

Hard DiskNo.

Partition No.


1

0 / 110000 Root partition

1 swap 20000 Swapping partition

2 overlap - Used for diskmapping. Fixed to thedefault size.

3 - - -

4 - - -

5 - - -


7 - 10 to 260 Used for diskmirroring. You neednot set the name or sizeof the partition. Thepartition size isallocatedautomatically by thesystem.




Issue 10 (2010-09-06)

Hard DiskNo.

Partition No.


2 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 Size (GB) Description

Seven hard disksact as RAID 5.

800 Volume name oss_v0

Seven hard disksact as RAID 5.

800 Volume name oss_v1

Two disks Act as the hotspare disk

Table 9-11 Disk partitions of the S2600 disk array

Hard Disk Size (GB) Description

Ten hard disksact as RAID 10.

671671671

Volume name oss_app0Volume name oss_app1Volume name oss_app2

Two disks Act as the hotspare disk

9.2.2 Checking the Disk Usage Information About the M2000 ServerThrough the M2000 Client

This section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client.



ContextChecking the disk usage information about the M2000 server requires only a few systemresources and does not affect system operation.



9-13

Procedure


Step 2 Click the Hard Disk Monitor tab to check disk usage information about the M2000 server. SeeFigure 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 redicon indicates that the usage of the corresponding disk is abnormal. If the usage of a disk exceeds the presetthreshold, the icon in this column changes from green to red.


----End

9.2.3 Viewing the Disk Usage of the M2000 Server Using SolarisCommands

This section describes how to use Solaris commands for viewing the disk usage of the M2000server. This task uses very few system resources and does not affect the system operation.

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




Issue 10 (2010-09-06)

-bash-3.00$ df -k

The system displays the following information:

Filesystem kbytes used avail capacity Mounted on/dev/dsk/c0t0d0s0 2053605 997684 994313 51% //proc 0 0 0 0% /procfd 0 0 0 0% /dev/fd/dev/dsk/c0t1d0s7 35009161 2562019 32097051 8% /export/homeswap 3431792 6664 3425128 1% /tmp

The command result contains the following information:

l File system name

l File size (unit: KB)

l Used space

l Free space

l Disk usage

l 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 than90% in the output.

----End

9.2.4 Clearing the Disk Space of the M2000 ServerThis section describes how to clear the disk space of the M2000 server. Before clearing diskspace, ensure that the files to be deleted are useless. Deleting a useful file by mistake may leadto a system failure.

ContextDuring the routine O&M, back up and clear the following files:l Files storing information about NEs and the M2000 server

l Software upgrade package and decompressed files

l Trace logs

l Backup files

l Temporary files created during the system operation

CAUTIONYou can delete files when the server is running. Before deleting files, run the command ls -l tocheck the files generated on that day. Do not delete the files generated on the very day.

Procedurel 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:



9-15

– Files generated during alarm auto-dumpAlarm dump files are stored in the /export/home/omc/var/ThresholdExport/FMdirectory.

– User log filesUser log dump files are stored in the /opt/OMC/var/userlogs directory.

– System generated core filesCore files refer to the files in the /export/home/omc/var/logs/ directory.

– Trace history filesTrace history files are stored in the /export/home/omc/var/logs/tracebak/ directory.

l Delete the software upgrade package and the decompressed files.

After the upgrade, delete the original upgrade package and the decompressed files. Theupgrade package and decompressed files are stored in the folder named after the upgradepatch in the path /export/home.

CAUTIONGenerally, the decompressed upgrade files are saved in the /export/home directory. Thefolder name of the upgrade files is created according to the upgrade patch name. The actualsaving 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 thenumber of trace backup files.

Edit the tracemonitor_svc_ex.xml file in the /opt/OMC/etc/conf/ directory to set the tracelog monitor period, size limit, and number of backup files. /opt/OMC is the defaultinstallation 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 tracefile at the regular interval of 300s. In tracebackupnum, you can set the number of backuptrace files for each process in the /opt/OMC/var/logs/tracebak directory. For a process, ifthe number of trace file backups in the tracebak folder exceeds the preset value, the systemautomatically deletes the oldest trace files in sequence.




Issue 10 (2010-09-06)

l Clear the backup files.– After the upgrade, delete the backup files for the upgrade or copy them to tapes.

– Back up all the files in the /export/home/backup/omc directory to tapes.

l 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. Choose Start > Program > iManager M2000 Client > M2000 Log Information

Collector.2. In the displayed Log Information Collector dialog box, select Core files in server.3. Click Collect.

Save the collected core files to the path C:\iManagerM2000Client\client\diagnosis\collected files. C:\iManagerM2000Client is the default installation path of theM2000 client software.

CAUTIONl The M2000 log information collector collects the stack information from the core

files. In addition to the stack information, the core files also include otherinformation. Therefore, before deleting the core files, confirm the deletion withHuawei technical support engineers.

l Because the size of the core files is large, you must compress the core files beforesending them.

4. After sending all the core files and the stack files to Huawei for confirmation, deletethe core files and stack files that are no longer required.

5. Stop the M2000 server. Delete the files in the /var/tmp directory. Delete other filesthat are no longer in use.

l Clear up disks regularly.1. Log in to the M2000 server as user dbuser.2. Change to the Sybase installation directory.

By default, the installation directory is /opt/sybase.

-bash-3.00$ cd /opt/sybase

3. Run the environment variable.

-bash-3.00$ . .profile

4. Access the Sybase database and run the following commands:


1> use omcdb

2> go

1> select fdn,neName from tbl_AllNeInfo

2> go



9-17

NOTE

After the Sybase server is started, run the following command to view the name of the databaseserver:



As shown in the following command result, the name of the database server in this example isSYB: dbuser 17046 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB dbuser 17050 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB_back

5. Switch to log in as user omcuser.

1> exit

-bash-3.00$ su - omcuser

Password: Password of omcuser6. 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 thedatabase.

-bash-3.00$ rm -r /export/home/sysm/ftproot/CmSync/neNE fdn

-bash-3.00$ rm -r /export/home/sysm/ftproot/pm/neNE fdn7. Switch to log in as user root.

-bash-3.00$ su - root

Password: Password of root8. 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




Issue 10 (2010-09-06)

10 Backing Up and Restoring the M2000

About This Chapter

This chapter describes how to back up and restore M2000 data.

ContextDepending on the data to be backed up, three data backup solutions are provided for theM2000.

Dynamic data backup: backs up the dynamic service data of the M2000 system. Static databackup: 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 systemdata, database application data, M2000 server application data. Static data backup and systemdata backup are implemented by the Backup & Restore Tools (BRT). For details, see M2000Backup and Restore Guide (BRT-Based, Sun).

10.1 M2000 Backup and Restore SolutionsThis section describes the backup scheme, backup strategy, and restore scenarios of M2000dynamic data.

10.2 Backing Up and Restoring M2000 Dynamic DataThis section describes how to back up and restore M2000 dynamic data.

M2000Administrator Guide (Sun, S10) 10 Backing Up and Restoring the M2000


10-1

10.1 M2000 Backup and Restore SolutionsThis section describes the backup scheme, backup strategy, and restore scenarios of M2000dynamic data.

10.1.2 Policies of M2000 Data BackupBased 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 RestorationThis section describes the dynamic data restore for typical scenarios.

10.1.1 Backup of M2000 Dynamic DataThis 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 torestore the history data when the M2000 is running properly or the static data restoration iscomplete. For details about the backup contents, backup modes, and storage media of thedynamic data backup, see Table 10-1.

Table 10-1 Introduction to dynamic data backup

Item Contents

Backup Contents l Database data: omcdb, fmdb, pmdb, swmdb, itfndb, omclogdb,pmcomdb, sumdb, omcsmdb, omctmdb, farsdb and omceamdb.

l M2000 system files: files under the /export/home/omc/var, /export/home/sysm/devdoc, and /export/home/sysm/ftproot directories.

CAUTION

l The configuration files related to the static data are stored in the /export/home/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 notexist.

l When backing up the M2000 system files, the system does not back up the logfiles and Trace files in the previous directories.

Backup modes Periodic backup After the periodic backup is activated, perform theperiodic backup once every day. Perform the fullbackup on the specified day of each week. On theother six days, automatically perform incrementalbackup at the same time. After a new round ofperiodic backup is performed, all the backup files ofthe previous round are deleted automatically.NOTE

Backing up dynamic data consumes system resources.Thus, the time set for backup should be at night when thesystem traffic is light.

10 Backing Up and Restoring the M2000M2000



Issue 10 (2010-09-06)

Item Contents

Manual backup l Full backup: backs up all the dynamic data. Whena new full backup is performed, all the backup filesin the backup directory are deleted automatically.Perform full backup according to yourrequirements.

l Incremental backup: backs up the dynamic datathat has changed since the last full backup. Theincremental backup is saved in another file,without overwriting the file of full backup.Perform incremental backup according to yourrequirements.

Storage device l Tape

l Hard disk

l Tape and hard disk

l Storage device of the NetBackup server

The directory ofbackup files

l When storage media is the hard disk in the M2000 server, the directoryof the backup files is: /export/home/backup/omc.

l When storage media is the tapes in the M2000, the directory of backupfiles is:/dev/rmt/0.CAUTION

If a system has more than one tape drives, the directory of the backup files isthe same as that of the tape drive, which is specified when backing up dynamicdata on a tape.

l When storage media is the hard disk in the NetBackup server, thedirectory 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 movesthe 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 DynamicData.

NOTE

When the M2000 system performs the dynamic data backup, do not perform operations such as modifyingthe configuration database.

10.1.2 Policies of M2000 Data BackupBased 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 BackupDynamic data backup is applicable to routine maintenance.



10-3

Rules for Naming Backup Files of Dynamic DataWhen 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 forincremental backup.

For example:

l The file name all-20040601042002.tar refers to a full backup file generated on 2004-06-0104:20:02.

l The file name inc-20040602042001.tar refers to an incremental backup file generated on2004-06-02 04:20:01.

NOTE

l The latest backup information is recorded in the /export/home/backup/omc/backup.log file.

l During the backup process, the inc-YYYYMMDDhhmmss or all-YYYYMMDDhhmmss folder isgenerated in the /export/home/backup/omc path for storing backup files. When the backup iscomplete, the folder is packed as the inc-YYYYMMDDhhmmss.tar or all-YYYYMMDDhhmmss.tar file, and the inc-YYYYMMDDhhmmss or all-YYYYMMDDhhmmssfolder is automatically deleted.

Rules for Naming the Tapes That Store the Backup DataThe rule for naming a backup tape is as follows: *backup tape (backup date). The character *stands for the following data:l Dynamic data

l Static data

l Data of the operating system

For example, if a tape is labeled "static data backup tape (2007-11-28)", it indicates that the staticdata backup is performed on November 28, 2007.

10.1.3 Scenarios of M2000 Data RestorationThis 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 backto the historical operational status such as the operational status of the last week.

10.2 Backing Up and Restoring M2000 Dynamic DataThis section describes how to back up and restore M2000 dynamic data.

10.2.1 Setting the Storage Device of Backup Data Using Solaris CommandsThis section describes how to set the storage device of backup data.

10.2.2 Setting the Storage Device of Backup Data Through the ClientYou can set the storage device for backup data through the client.

10.2.3 Setting the Wait Time for Replacing a TapeYou can store the dynamic data on multiple tapes. If the current tape is fully written, the systemautomatically ejects the tape and waits for you to replace it. By modifying the configuration file,you can set the wait time.




Issue 10 (2010-09-06)

10.2.4 Periodically Backing Up the M2000 Dynamic DataThis section describes how to periodically back up the M2000 dynamic data.

10.2.5 Manually Backing Up the M2000 Dynamic DataThis section describes how to manually back up the M2000 dynamic data.

10.2.6 Restoring the M2000 Dynamic DataThis section describes how to restore the M2000 dynamic data.

10.2.1 Setting the Storage Device of Backup Data Using SolarisCommands

This section describes how to set the storage device of backup data.

PrerequisiteYou have logged in to the system as user root.

ContextBy default, the backup files for the dynamic data backup are stored on hard disks. To store thebackup 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.

CAUTIONl Do not modify the configuration files of storage devices when the backup is in process.

l When you perform a full backup, the new backup files replace the backup files that alreadyexist on the disk.

l After you change the current storage device, for example, from a disk to a tape, you mustperform a full backup again. Otherwise, dynamic data may fail to be restored owing to theloss of certain backup data.

l If you set the backupMedia parameter to tape or all, label the tapes after the backup iscomplete.

l Do not replace the storage device when the backup is in process.

l For data security, back up the dynamic data to a tape.

l When recovering the static data and restoring the system, use the dynamic data backup filesstored on the tape to recover the latest service data.

Procedure

Step 1 Ensure that the M2000 daemon is started.

Run the following commands to check whether the M2000 daemon is started:


# daem_ps



10-5

If ... Then ...

There is any output after you run thedaem_ps command

The M2000 daemon is started. Proceed with thenext step.

There is no output after you run thedaem_ps command

The M2000 daemon is not started. Run thefollowing 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 viewthe 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 andincremental backups to the actual storage device. The storage media of both full and incrementalbackup 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 Value

Hard disks on the M2000 server disk

Tapes tape

Hard disks and tapes all

Storage device of the NetBackup server veritas

NOTE

l If backupMedia is set to veritas, the system automatically packs the backup data and moves the backupdata to the storage device of the NetBackup server. After the operation, the M2000 server does nothold the backup data that is moved to the storage device.

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




Issue 10 (2010-09-06)

1. Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfgfile by running the vi command.

# cd /opt/OMC/tools/Backup/config

# vi generalbus.cfg2. 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 This section takes /dev/rmt/0 as an example. Replace /dev/rmt/0 with actual directory of the tapedrive during actual operations.

l If multiple tape drives are installed on the server, select a tape drive by referring to 14.1.4 HowDo 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 theClient

You can set the storage device for backup data through the client.

Prerequisitel The M2000 server is running properly.

l The connection between the M2000 client and server is normal.

ContextYou can set the storage device for backup data when the M2000 is running.



10-7

CAUTIONl Do not modify the configuration files of storage devices when the backup is in process.

l When you perform a full backup, the new backup files replace the backup files that alreadyexist on the disk.

l After you change the current storage device, for example, from Disk to Tape, you need toperform a full backup again. Otherwise, the dynamic data may fail to be recovered due tothe loss of some backup data.

l Set the storage device to Tape or Disk and Tape, remove and label the tape when thebackup is complete.

l Do not replace the storage device when the backup is in process.

l For data security, back up the dynamic data to a tape.

l When recovering the static data and restoring the system, use the dynamic data backup filesstored on the tape to recover the latest service data.

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 thedialog box, and then click OK, as shown in Figure 10-2.




Issue 10 (2010-09-06)

Figure 10-2 Setting the storage device (II)

NOTE

l The parameter Veritas refers to the storage device of the NetBackup server.

l If the storage device is set to Veritas, the system automatically packs the backup data and moves thebackup data to the storage device of the NetBackup server. After the operation, the M2000 server doesnot hold the backup data that is moved to the storage device.

l 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 thestorage device. Click Yes.

Step 5 When the change of storage device is complete, the Message dialog box is displayed. ClickOK.

Step 6 Perform a full backup. For details, see 10.2.5 Manually Backing Up the M2000 DynamicData.

----End

10.2.3 Setting the Wait Time for Replacing a TapeYou can store the dynamic data on multiple tapes. If the current tape is fully written, the systemautomatically ejects the tape and waits for you to replace it. By modifying the configuration file,you can set the wait time.

Prerequisite

You have logged in to the system as user root.

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. Bydefault, the wait time is set to 120 minutes.

You can configure the wait time for replacing a tape when the M2000 is running.



10-9

CAUTIONDo 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:


# daem_ps

If ... Then ...

There is any output after you run thedaem_ps command

The M2000 daemon is started. Proceed with thenext step.

There is no output after you run thedaem_ps command

The M2000 daemon is not started. Run thefollowing command to start the daemon:

# start_daem

Step 2 Navigate to the /opt/OMC/tools/Backup/config directory and open the generalbus.cfg file byrunning 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 ofchangetape_timeout to the wait time for replacing a tape.[STEP_TRANSFERTOMEDIA]......changetape_timeout=120......

NOTE

l The value of the changetape_timeout parameter indicates the wait time, which is represented inminutes.

l 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 DataThis section describes how to periodically back up the M2000 dynamic data.




Issue 10 (2010-09-06)


l You are authorized to perform relevant operations.

l The tape drive is connected properly, and it holds a tape if you plan to back up data on thetape.

l A hard disk has sufficient free space if you plan to back up data on the hard disk.

Contextl 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, ittakes about five hours.




Procedure





10-11







Issue 10 (2010-09-06)


Step 5 Click OK.



with a new one.








10-13

NOTE





----End

10.2.5 Manually Backing Up the M2000 Dynamic DataThis section describes how to manually back up the M2000 dynamic data.


l You are authorized with the relevant operation rights.

l The tape drive is connected properly, and it holds a tape if you plan to back up data on thetape.

l A hard disk has sufficient free space if you plan to back up data on the hard disk.

Contextl Manual backup is required in special or emergency situations such as the loss of backup

tapes and the failure of the M2000 system.l 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, ittakes about five hours.

Procedure

Step 1 In the main window, choose Maintenance > Backup Management. The BackupManagement dialog box is displayed.




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 Resetto change the backup medium before data backup. For details, see 10.2.2 Setting the StorageDevice 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 fullbackup. 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 basedon full backup.


with a new one.

As shown in Figure 10-5, the Message field in the Backup Management dialog boxdisplays the following message:







10-15

NOTE





----End

10.2.6 Restoring the M2000 Dynamic DataThis section describes how to restore the M2000 dynamic data.

Prerequisitel You have logged in to the system as user root.

l You have obtained the backup files for restoring the dynamic data.

l The Sybase database service is running properly.

ContextYou can restore the M2000 based on the latest full backup and incremental backup files. Afteryou restore the M2000, all the contents in the backup file package are restored. If certain datagenerated after the backup start time, such as the NE performance data or alarm data, is notcompressed in the backup file package, the M2000 enables the automatic synchronizationfunction to obtain data from NEs and process the data.

During the restoration of the dynamic data, the M2000 services are stopped, and thus theperformance 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, ittakes about six hours.

Procedure

Step 1 If the backup files are stored on tapes of the tape drives connected to the M2000 server, performthe following steps to decompress the contents on the tape to a hard disk. Otherwise, go to Step3.

Insert the first tape that stores the dynamic data and run the following command:

# /usr/sfw/bin/gtar xvPfM /dev/rmt/0




Issue 10 (2010-09-06)

CAUTIONl 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.l 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 followingcommand:# mt -f /dev/rmt/0 offline

2. After replacing the first tape with the second tape, press Enter to decompress the data onthe second tape to a hard disk.

CAUTIONPress Ctrl+C to exit if the following message is displayed:gtar:'export/home/backup/omc/all-20080130180622.tar' is notcontinued on this volumeThen, 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.



10-17

# tar xf all-20080130180622.tar

NOTE

You need to decompress the relevant package regardless of the full backup file or the incrementalbackup 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 runningstate on 18:06:22 2008-01-30, decompress all-20080130180622.tar. If you need to restore the systemto the running state on 18:06:22 2008-01-31, decompress inc-20080131180622.tar. You need notdecompress 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-200801301806223. Run the following script to restore the dynamic data:

# ./restore.sh4. 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.

CAUTIONIf 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 andrestore guide and then start the M2000 services. The reason of the previous operation isthat the direct startup of the M2000 services may fail because the parameters of the rebuiltM2000 database are not set.

Step 5 Run the following commands to restart the M2000 services:


# 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




Issue 10 (2010-09-06)

l If the system displays the following information, it indicates that the M2000 service fails tobe started. In such a case, do not proceed with Step 6. Instead, contact Huawei technicalsupport 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



10-19

11 M2000 Routine Maintenance

About This Chapter

This chapter describes the maintenance items and the procedures required to conduct theM2000 routine maintenance. These items are, however, only for reference. Specific maintenanceitems are required in real applications.

11.1 M2000 Routine Maintenance ItemsThis section describes the recommended maintenance items of the M2000.

11.2 Daily Maintenance OperationsThis section describes the daily maintenance operations that need to be performed on theM2000.

11.3 Weekly Maintenance OperationsThis section describes the weekly maintenance operations that need to be performed on theM2000.

11.4 Monthly Maintenance OperationsThis section describes the monthly maintenance operations that need to be performed on theM2000.

M2000Administrator Guide (Sun, S10) 11 M2000 Routine Maintenance


11-1

11.1 M2000 Routine Maintenance ItemsThis section describes the recommended maintenance items of the M2000.

Table 11-1 lists the recommended maintenance items of the M2000. You can add or deletemaintenance items according to the actual requirement.

Table 11-1 List of maintenance items

No. Item MaintenancePeriod

Reference

1 Check the status ofperformance measurement.

Daily All measurement counters and measurementobjects are being measured.

2 Check the loss ofperformance results.

Daily No performance result is lost.

3 Check the status of alarmreception.

Daily The alarms reported by NEs are received inreal time.

4 Check the status of the NMSconnection.

Daily The NMS can collect the alarms andperformance data reported by the M2000.

5 Check the status of the alarmbox.

Daily The alarm box can report the M2000 alarmsin real time.

6 Check OMC alarms orevents.

Daily No OMC alarm or event is generated.

7 Check the connectionbetween the M2000 andNEs.

Daily The connection between the M2000 andNEs is normal.

8 Check the M2000 logs. Daily The system runs properly. No abnormal ormalicious operations are performed.

9 Check the error logs of theSolaris operating system.

Daily No error log is generated.

10 Check the hard disk usage ofthe M2000 server.

Daily The usage of each disk is less than 90%.

11 Check the status of theM2000 database.

Daily The database runs properly and its usage isless than 80%.

12 Check the status of theM2000 services.

Daily All the services run properly, and no serviceis in not running state.

13 Check the core file of theserver.

Daily No core file exists in the /export/home/omc/var/logs directory.

11 M2000 Routine MaintenanceM2000



Issue 10 (2010-09-06)


Reference

14 Check the hardware of theM2000 server.

Daily The hardware of the M2000 server is notdamaged.

15 Check the results collectedby the SMC.

Daily The operating environment of the M2000server is normal.

16 Check the configuration ofalarm timing tasks.

Weekly

The time of alarm timing tasks is setproperly. This prevents the time conflictwith background tasks. The conflict mayresult in heavy CPU load.

17 Check the configuration ofautomatic log dump.

Weekly

The time of automatic log dump is setproperly. This prevents the time conflictwith background tasks. The conflict mayresult in heavy CPU load.

18 Check the configuration ofNE log synchronizationtime.

Weekly

The time of NE log synchronization is setproperly. This prevents the time conflictwith background tasks. The conflict mayresult in heavy CPU load.

19 Check the configuration ofthe file server.

Weekly

The file server is configured properly.

20 Check the configuration ofthe system backup.

Weekly

The time for automatically and periodicallybacking up the M2000 server and NEs is setproperly. Backup files are generated indisks.

21 Check the configuration ofsystem monitoring.

Weekly

The threshold of system monitoring is setproperly.

22 Check the configuration ofNE configurationsynchronization time.

Weekly

The time of NE configurationsynchronization is set properly.

23 Check the managementcapability of the M2000.

Weekly

The number of equivalent NEs managed bythe M2000 does not exceed the managementcapability of the M2000.

24 Check the status of theM2000 routes.

Weekly

The M2000 routes are configured correctly.

25 Back up the M2000. Weekly

Back up the M2000 database and systemfiles. View the backup files on disks andtapes.

26 Check the time of theM2000 server.

Weekly

The time of the M2000 server is correct.



11-3


Reference

27 Check the disk status of theM2000.

Weekly

All the disks that are in use are online, theKSTATE columns of pl, sd, and v areENABLED, and the STATE columns areACTIVE. The usage of each partition is lessthan 80%.

28 Check the power supply ofthe M2000 server.

Monthly

The power supply is normal.

29 Check the peripherals of theM2000 server.

Monthly

For details about how to check whether theCD-ROMs and tape drives run properly, seethe related operating system administratormanuals.

30 Check the front panel of adisk array.

Monthly

The disk array is not damaged.

For details about how to operate and maintain NEs, see the M2000 Online Help.

11.2 Daily Maintenance OperationsThis section describes the daily maintenance operations that need to be performed on theM2000.

11.2.1 Checking the Status of Performance MeasurementThis section describes how to check the performance measurement state. You must ensure thatall the required measurement counters and measurement objects are in proper status.

11.2.2 Checking the Missing Performance ResultTo ensure that no result is lost, you must check that the missing performance result exists.

11.2.3 Checking the Alarm ReceptionCheck the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.

11.2.4 Checking the NMS ConnectionThis section describes how to check the NMS connection and to ensure that the NMS connectionis normal.

11.2.5 Checking the Functionality of Alarm BoxCheck the function of generating visual and audible alarms for the alarm box and ensure thatthe alarm box can indicate the alarms on the M2000 in real time.

11.2.6 Check OMC Alarms/EventsThis section describes how to check whether the M2000 system is normal. This section alsodescribes how to check whether the alarms and events of the M2000 are generated.

11.2.7 Checking Connections Between the M2000 and NEs




Issue 10 (2010-09-06)

This section describes how to check the connections between the M2000 and NEs.

11.2.8 Checking M2000 LogsM2000 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 SolarisThis section describes how to check the error logs of the Solaris operating system.

11.2.10 Checking the Disk Usage of the M2000 ServerThis section describes how to check the disk usage and clean up the expired log files, temporaryfiles, and other files that are no longer in use. This operation requires very few system resourcesand does not affect the system operation.

11.2.11 Checking the States of M2000 DatabasesThis 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 thesystem operation.

11.2.12 Checking the States of M2000 ServicesThis section describes how to check the states of M2000 services. This operation requires veryfew system resources and does not affect system operation.

11.2.13 Checking the Core Files on the ServerThis section describes how to check the /export/home/omc/var/logs directory and to ensurethat core files do not exist.

11.2.14 Checking the Hardware of the M2000 ServerThis section describes how to check the M2000 server hardware.

11.2.15 Checking the SMC Collection ResultsThis section describes how to check the SMC collection results and to ensure that the M2000server environment is normal.

11.2.1 Checking the Status of Performance MeasurementThis section describes how to check the performance measurement state. You must ensure thatall the required measurement counters and measurement objects are in proper status.


l 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 properstatus. If there is any exception, contact Huawei technical support engineers for assistance.

----End



11-5

11.2.2 Checking the Missing Performance ResultTo ensure that no result is lost, you must check that the missing performance result exists.


l 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 thenchoose 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 missingresults 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 displayeddialog box. The first column of the table displays the object information. The second columndisplays the corresponding time range.

----End

PostrequisiteIf missing measurement results exist, synchronize the results.

1. Right-click a node in the navigation tree, and then choose Missing Result from the shortcutmenu.

2. In the Query Missing Result window, select an NE and a function subset whose missingresults you want to query, and then click OK.

3. In the dialog box of missing results, click Synchronize Result.

4. In the Prompt dialog box, click OK.

After the synchronization command is issued to the NE, it takes some time for the NE toreport the performance measurement data. You can check whether the data is successfullyreported by viewing whether the missing results disappear.

11.2.3 Checking the Alarm ReceptionCheck the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.

Prerequisitel You have logged in to the M2000 .

l You are authorized to perform fault management.




Issue 10 (2010-09-06)

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 ConnectionThis section describes how to check the NMS connection and to ensure that the NMS connectionis 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 BoxCheck the function of generating visual and audible alarms for the alarm box and ensure thatthe alarm box can indicate the alarms on the M2000 in real time.


l 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, canbe indicated on the alarm box in real time.

----End

11.2.6 Check OMC Alarms/EventsThis section describes how to check whether the M2000 system is normal. This section alsodescribes how to check whether the alarms and events of the M2000 are generated.


l You are authorized to query alarms and events.



11-7

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 orno 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 Alarm ID

The OMC Service Is Terminated Abnormally 4

The Disk Usage Is Too High (Critical) 37

Power Failure 101

Fan Failure 102

CPU Temperature Is Abnormal 103

Hard Disk Failure 104

Disk Array Failure 105

Power or Fan Failure To the Disk Array Cabinet 106

Failure To the Devices in the Disk Array Cabinet 107

A Disk on the Array Is Faulty 108

Memory Failure 110

CPU Failure 112

l 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 Alarm ID

NE Mediation Layer Version Unmatched 303

Insufficient Free Space of the PerformanceDatabase

405

License Invalid 501

License Expired 505

License On Trail 506

Server Backup Unsuccessful 512




Issue 10 (2010-09-06)

l 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 theLocation Information column in the exported files. If the alarms are generated on therequired NEs, you need to clear the alarms.

Table 11-4 Alarms to be focused on during network expansion

Alarm Name Alarm ID

NE Is Disconnected 301

l 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 preventmalicious operations.

Table 11-5 Alarms about malicious operations

Alarm Name Alarm ID

The Number of Login Attempts Reaches the Maximum 11

Step 3 Right-click the Local NM icon, and then choose Query Alarm/Event > Event Logs from theshortcut 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 Event ID

SMC Alarm 1099

l 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 LocationInformation column in the exported files. If the events occur on the required NEs, you needto handle them.

Table 11-7 Events that need to be focused on during network expansion

Event Name Event ID

Performance Result Loss 407

----End

PostrequisiteTo handle alarms and events, perform the following steps:



11-9

1. In the Browse Alarm List or Query Event Logs window, select a specific alarm or event.2. 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 alarmor event online help.

3. (Optional) When handling alarms, you also need to acknowledge uncleared alarms, andanalyze 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.

4. Double-click an alarm or event. The Detail Information dialog box is displayed.5. In the Experience area, click Modify. The Experience dialog box is displayed.6. 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.

7. Repeat 1 to 6 to handle each alarm or event.8. Ensure that the M2000 system is operational.

No alarms or events occur if the M2000 system is operational.

11.2.7 Checking Connections Between the M2000 and NEsThis section describes how to check the connections between the M2000 and NEs.

PrerequisiteBefore checking connections between the M2000 and NEs, ensure that:l You have logged in to the M2000 .

l 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 theproblem.

The NA status is caused by an unmatched NE version. Check the NE version and then installthe 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




Issue 10 (2010-09-06)

11.2.8 Checking M2000 LogsM2000 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.


l 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 Filterwindow 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 clientfor 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 SolarisThis section describes how to check the error logs of the Solaris operating system.

PrerequisiteBefore checking error logs of the Solaris, ensure that you have logged in to the M2000 serveras user omcuser.

Contextl Viewing the Solaris error logs occupies few system resources and does not affect system

operation.l The record format of the /var/adm/messages file and the /var/log/syslog file is as follows:

date and time-hostname-descriptionNOTE

The /var/adm/messages file is the core system log file. It contains the boot information about systemstartup and other status information about system operation. The /var/log/syslog file records themessages exported to the system console and the messaged generated by the syslog system service.



11-11

l Generally, the messages such as err or failed are not displayed. If such messages aredisplayed, 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 ServerThis section describes how to check the disk usage and clean up the expired log files, temporaryfiles, and other files that are no longer in use. This operation requires very few system resourcesand does not affect the system operation.

Prerequisitel You have logged in to the M2000 system.

l 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 The disk usage is smaller than 90%.

l View the partition with the largest remaining space. The remaining space must be sufficientto 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 DiskSpace of the M2000 Server.

Step 4 Check whether the disk usage of the M2000 server is within the normal range.

----End




Issue 10 (2010-09-06)

11.2.11 Checking the States of M2000 DatabasesThis 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 thesystem operation.



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.


If the database usage is greater than 90%, clear some data space by dumping alarm data and userlogs. 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 ServicesThis section describes how to check the states of M2000 services. This operation requires veryfew 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 Service Monitor or Process Monitor tab to monitor the processes running on theM2000 server.


In case a process is running improperly or a process is terminated exceptionally, log in to theM2000 server as user root. Run the command kill -9 pid to forcibly kill the process, where pidindicates the process No.. The start_svc command is used to start all the M2000 services. If



11-13

some sessions are not started, run the command start_svc again. If a certain process is stillinactive, 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 ServerThis section describes how to check the /export/home/omc/var/logs directory and to ensurethat core files do not exist.

PrerequisiteYou 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 filesgenerated one week earlier. Contact Huawei technical support engineers to deal with the corefiles generated within the week.

----End

11.2.14 Checking the Hardware of the M2000 ServerThis section describes how to check the M2000 server hardware.

PrerequisiteThe 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 manualof 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 themanual mapping to the model of disk array.





Issue 10 (2010-09-06)

If the hardware incurs a fault, locate the fault by referring to related manuals of the disk arrayand 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 ResultsThis section describes how to check the SMC collection results and to ensure that the M2000server environment is normal.

Prerequisitel The SMC server software runs properly.

l The SMC client software runs properly.

l You have the password of user root to log in to the M2000 server.

Procedure

Step 1 On the SMC client, log in to the server as user root.

Step 2 Enter Sun Management Center and check the SMC collection results.

For detailed operations, see the relevant manual of the SMC. You can obtain the relevant SMCmanual at the Sun website.

----End

11.3 Weekly Maintenance OperationsThis section describes the weekly maintenance operations that need to be performed on theM2000.

11.3.1 Checking the Configuration of Alarm TimingThis section describes how to check whether the policy on automatic dumping alarm data fromthe alarm database is reasonable.

11.3.2 Checking the Configuration of Automatic Log DumpThis section describes how to check whether the system of automatic dumping alarm data fromthe alarm database is satisfactory.

11.3.3 Checking the Synchronization Time of NE LogThis section describes how to check whether the configuration of synchronization time of theNE log is correct. The purpose is to avoid the server overload owing to the conflict of time whenyou perform tasks on the server.

11.3.4 Checking the Configuration of the File ServerThis section describes how to check whether the configuration of the file server is appropriate.

11.3.5 Checking the Configuration of System BackupThis section describes how to check whether the periodic backup of the M2000 server and NEsare started and whether the start time is correct. The purpose is to avoid the server overloadowing to the conflict of time when you perform tasks on the server. This section also describeshow to check whether backup files are generated in the disk.



11-15

11.3.6 Checking the Configuration of System MonitoringThis section describes how to check the configuration of system monitoring.

11.3.7 Checking the Synchronization Time of NE ConfigurationThis section describes how to check whether the time for synchronizing NE configuration datais appropriate. The purpose is to avoid the server overload. The server overload may occur whenthe synchronization is performed simultaneously with other tasks on the server.

11.3.8 Checking the Threshold of Network Management CapabilityThis section describes how to check whether the M2000 management capability exceeds thethreshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceedthe capability limit.

11.3.9 Checking the Status of the M2000 RoutesThis section describes how to check the configuration of the M2000 routes.

11.3.10 Backing Up the M2000This section describes how to back up the M2000 . The M2000 backup refers to the backup ofM2000 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 ServerThis section describes how to check the time of the M2000 server.

11.3.12 Checking the States of M2000 DisksThis section describes how to check all the disks in the Vxvm, the logical volumes of the localdisk in the Vxvm, and the logical volumes of the disk array in the Vxvm.

11.3.1 Checking the Configuration of Alarm TimingThis section describes how to check whether the policy on automatic dumping alarm data fromthe alarm database is reasonable.


l 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 leftpane, 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




Issue 10 (2010-09-06)

11.3.2 Checking the Configuration of Automatic Log DumpThis section describes how to check whether the system of automatic dumping alarm data fromthe alarm database is satisfactory.


l You are authorized to check the configuration of M2000 integrated task management.

Procedure



Step 2 Check the configuration of automatic log dump of NE operation logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NE Operation Log.2. Choose the task in the right pane. Click Attribute.3. Check the configuration of auto NE operation log dump in the Attribute window.4. Ensure that the configuration is reasonable.

Step 3 Check the configuration of automatic log dump of NE security logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NE Security Log.2. Choose the task in the right pane. Click Attribute.3. Check the configuration of auto NE security log dump in the Attribute window.4. Ensure that the configuration is reasonable.

Step 4 Check the configuration of automatic log dump of NE system logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NE System Log.2. Choose the task in the right pane. Click Attribute.3. Check the configuration of auto NE system log dump in the Attribute window.4. Ensure that the configuration is reasonable.

Step 5 Check the configuration of automatic log dump of NM operation logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NM Operation Log Dump.2. Choose the task in the right pane. Click Attribute.3. Check the configuration of auto NM operation log dump in the Attribute window.4. Ensure that the configuration is reasonable.

Step 6 Check the configuration of automatic log dump of NM system logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NM System Log Dump.2. Choose the task in the right pane. Click Attribute.



11-17

3. Check the configuration of auto NM system log dump in the Attribute window.4. Ensure that the configuration is reasonable.

Step 7 Check the configuration of automatic log dump of NM security logs.1. Under the Database Capacity Management node in the Task Type navigation tree in the

left pane, select NM Security Log Dump.2. Choose the task in the right pane. Click Attribute.3. Check the configuration of auto NM security log dump in the Attribute window.4. Ensure that the configuration is reasonable.

----End

11.3.3 Checking the Synchronization Time of NE LogThis section describes how to check whether the configuration of synchronization time of theNE log is correct. The purpose is to avoid the server overload owing to the conflict of time whenyou perform tasks on the server.


l You are authorized to check the configuration of the M2000 integrated task management.

ContextYou need to run the operation only if the NE supporting this function exists.

Procedure



Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select NELog 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 operationis performed at night when no other tasks are performed.

----End

11.3.4 Checking the Configuration of the File ServerThis section describes how to check whether the configuration of the file server is appropriate.


l You are authorized to check the configuration of the M2000 file server.




Issue 10 (2010-09-06)

ProcedureStep 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 BackupThis section describes how to check whether the periodic backup of the M2000 server and NEsare started and whether the start time is correct. The purpose is to avoid the server overloadowing to the conflict of time when you perform tasks on the server. This section also describeshow to check whether backup files are generated in the disk.


l You are authorized to check the configuration of the M2000 integration task.

ProcedureStep 1 Choose Maintenance > Task Management.


Step 2 Check whether the periodic backup of the M2000 server is started and whether the start time iscorrect.1. Under the Backup node in the Task Type navigation tree in the left pane, select the Server

Backup node.2. View Last Run Time and State in the right pane. Ensure that the task is running in the

execution time.3. Select the task in the right pane. Click Attribute.4. View the configuration of periodic backup time for the M2000 server in the Attribute

dialog box.5. 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.1. Under the Backup node in the Task Type navigation tree in the left pane, select the NE

Backup node.2. View Last Run Time and State in the right pane. Ensure that the task is running in the

execution time.3. Select the task in the right pane. Click Attribute.4. View the configuration of periodic backup time for NEs in the Attribute dialog box.

Ensure that the configuration is correct.

Step 4 Log in to the M2000 server as user omcuser. Check whether backup files exist in the backupdirectory of both the M2000 server and NEs.



11-19

You can specify the backup directory for the M2000 server and NEs based on the attributeinformation.

----End

11.3.6 Checking the Configuration of System MonitoringThis section describes how to check the configuration of system monitoring.

ContextThe 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 usagethresholds are appropriate.

Step 3 Click the Hard Disk Monitor tab to check whether the settings of the disk usage thresholds areappropriate.

Step 4 Click the Database Monitor tab to check whether the settings of the database usage thresholdsare appropriate.

Step 5 Click the Service Monitor tab to check whether the settings of the service status refresh intervalthresholds are appropriate.

----End

ExampleFor details about the parameters for monitoring the server, see Table 11-8.




Issue 10 (2010-09-06)













CPU used rate(%)





11-21


Memory used rate(%)






Table 11-9 describes the parameters for monitoring the disks of the server.










Issue 10 (2010-09-06)









l Minor: 70

l Major: 80

l Critical: 90



11-23


Advanced Setting(%)





NOTE







Issue 10 (2010-09-06)

Table 11-10 describes the parameters for monitoring the database of the server.













l Minor: 90

l Major: 95

l Critical: 98



11-25


Advanced Setting(%)







– Minor: 90

– Major: 95

– Critical: 98


Table 11-11 describes the parameters for monitoring the server services.










Issue 10 (2010-09-06)




monitor client by

or .NOTE




is displayed.

l You can double-



11.3.7 Checking the Synchronization Time of NE ConfigurationThis section describes how to check whether the time for synchronizing NE configuration datais appropriate. The purpose is to avoid the server overload. The server overload may occur whenthe synchronization is performed simultaneously with other tasks on the server.


l You are authorized to check the configuration of the M2000 integrated task management.

ContextYou need to run the operation only if the NE supporting this function exists.

Procedure



Step 2 Under the Synchronization node in the Task Type navigation tree in the left pane, select theNE Configuration Data Synchronization node.

Step 3 Select the task in the right pane. Click Attribute.



11-27

Step 4 View the setting of the time for synchronizing NE configuration data in the Attribute dialogbox.

Step 5 Ensure that the configuration is correct.

----End

11.3.8 Checking the Threshold of Network Management CapabilityThis section describes how to check whether the M2000 management capability exceeds thethreshold. Ensure that the number of equivalent NEs managed by the M2000 does not exceedthe capability limit.

Procedure

Step 1 Check whether the M2000 management capability exceeds the threshold. Ensure that the numberof 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 managementcapability, refer to the M2000 Product Description.

----End

11.3.9 Checking the Status of the M2000 RoutesThis section describes how to check the configuration of the M2000 routes.

PrerequisiteYou 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 M2000This section describes how to back up the M2000 . The M2000 backup refers to the backup ofM2000 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.


l You are authorized to back up the M2000 system.




Issue 10 (2010-09-06)

ContextNOTE

The time required for backing up data is related to the actual environment. Generally, it takes about fivehours.




Procedure








11-29


Step 5 Click OK.



with a new one.









Issue 10 (2010-09-06)

NOTE





----End

11.3.11 Checking the Time of the M2000 ServerThis section describes how to check the time of the M2000 server.

PrerequisiteYou 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 startedand check the service status according to 2.5.7 Checking the Running Status of the NTPService 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 M2000Time.

l 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 DisksThis section describes how to check all the disks in the Vxvm, the logical volumes of the localdisk in the Vxvm, and the logical volumes of the disk array in the Vxvm.



11-31

PrerequisiteYou have logged in to the M2000 server as user root.

ContextThe 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 TYPE DISK GROUP STATUS c4t2d1s2 auto:cdsdisk ossdisk-1 ossdg 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 thevalues 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 partitionis 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 OperationsThis section describes the monthly maintenance operations that need to be performed on theM2000.

11.4.1 Checking the Power Supply of the M2000 ServerThis section describes how to check the power supply of the M2000 server.

11.4.2 Checking the Peripherals of the M2000 ServerThis section describes how to check the peripherals of the M2000 server, such as the CD-ROMdrive and the tape drive.

11.4.3 Checking the Front Panel of a Disk ArrayThis section describes how to check the front panel of each disk array to determine whether adisk array is damaged.




Issue 10 (2010-09-06)


11.4.1 Checking the Power Supply of the M2000 ServerThis section describes how to check the power supply of the M2000 server.

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


The Solaris system log records the faults of the power supply housed in the Sun cabinet. For theexternal power supply, that is, the power supply outside the Sun cabinet, check the power supplyand 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 ServerThis section describes how to check the peripherals of the M2000 server, such as the CD-ROMdrive and the tape drive.

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



11-33

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 indicatorof system faults is off. In the middle of the front panel, there is one hard disk indicatoravailable in both upper line and lower line. The green light of the hard disk indicators are onor blinking.

l 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 powerinput is on.


For details on how to handle the faults of the CD-ROM drive and the tape drive, refer to theSolaris 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 SolarisAdministrator Guide.

----End

11.4.3 Checking the Front Panel of a Disk ArrayThis section describes how to check the front panel of each disk array to determine whether adisk array is damaged.

Procedure

Step 1 Check whether the LED indicator of the front panel of a disk array is yellow. If the LED indicatoris 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


Procedure


Step 2 In the License Information dialog box, query the license information about resources andfunctions on the Resource control item and Function control item tabs.

----End




Issue 10 (2010-09-06)

12 M2000 Emergency Maintenance

About This Chapter

This chapter describes the emergency maintenance in the case of a critical fault in the M2000server or client. This chapter covers the server emergency maintenance, client emergencymaintenance, and emergency maintenance for the server power-off.

12.1 Guide to Emergency Maintenance of the M2000 ServerThis section describes the guide to emergency maintenance of the M2000 server.

12.2 Guide to Emergency Maintenance of the M2000 ClientThis section provides guidance for emergency maintenance of the M2000 client.

12.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power FailureThis section describes the guide to emergency maintenance of the M2000 server in the case ofpower failure. The abnormal power-off of the M2000 server forces the Solaris and the M2000application to exit, thereby causing severe faults in the Solaris. In the case of abnormal power-off, you need to reset the M2000 server and take measures to restore the system based on thesymptoms.

M2000Administrator Guide (Sun, S10) 12 M2000 Emergency Maintenance


12-1

12.1 Guide to Emergency Maintenance of the M2000 ServerThis 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 serverbreaks down or a fault occurs in the server, restore the server in the following ways:

l Through the BRT toolYou can use the BRT tool to back up operating system data on a tape. To restore systemdata, 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 inthe BRT tool.

l Through the backup serverRestore the Solaris from the backup server if a full system backup is created through theVeritas software.

l By reinstalling the SolarisIf the system is not backed up, all the user data will be lost if the system crashes owing toa fatal error.

12.2 Guide to Emergency Maintenance of the M2000 ClientThis 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 thefollowing ways:

l Reinstall the operating system on the M2000 client.

l Reinstall the M2000 system.

12.3 Guide to Emergency Maintenance of the M2000 Serverin Case of Power Failure

This section describes the guide to emergency maintenance of the M2000 server in the case ofpower failure. The abnormal power-off of the M2000 server forces the Solaris and the M2000application to exit, thereby causing severe faults in the Solaris. In the case of abnormal power-off, you need to reset the M2000 server and take measures to restore the system based on thesymptoms.

12.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss of System FilesThis section describes how to handle the failure to start the Solaris operating system owing tothe loss of system files.

12.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You toRun fsck ManuallyThis 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 SystemThis section describes how to handle the loss of database device files after the file system isrestored.

12 M2000 Emergency MaintenanceM2000



Issue 10 (2010-09-06)

12.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is IntactThis section describes how to handle the failure to restore the database though the file systemis intact.

12.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss ofSystem Files

This section describes how to handle the failure to start the Solaris operating system owing tothe loss of system files.

SymptomThe 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 pingthe 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 HandlingUnexpected power-off of the server damages the Solaris operating system. As a result, the systemfile path_to_inst is lost. The Solaris operating system, therefore, fails to start.

1. Press Stop+a or Ctrl+Break to exit the startup and switch to the ok status. Only thekeyboard delivered with the server has the stop key.

2. Insert the boot disk of the Solaris operating system, that is, the first of the two installationdisks, 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 tothe system root folder:# cd /dev/dsk# ls

4. Mount this basic device to the /mnt mount point. Assume that the name of the basic devicecorresponding to the root folder is c0t0d0s0. Run the mount /dev/dsk/c0t0d0s0 /mntcommand to switch to /mnt to restore the Solaris operating system.

CAUTIONIf the /etc/path_to_inst file is lost, restore it using the path_to_inst-INSTALL templatestored 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



12-3

# /usr/sbin/shutdown -g0 -y -i6After the system starts, run the fsck -y command to restore the system file. Start the Sybaseand M2000 application manually.

12.3.2 Troubleshooting: System Switched into the MaintenanceMode and Prompting You to Run fsck Manually

This section describes how to manually run the fsck command in maintenance mode.

SymptomThe server cannot be started and can be switched only to the maintenance mode. The systemdisplays 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 aserial 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 toother partitions.

Fault HandlingThe exceptional server power-off damages the Solaris. You must restore the Solaris manually.

1. Log in to the server as user root.2. Modify the file system.

# fsck -y3. 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 filesare complete.

4. After the file system is restored, switch to the /export/home/sybdev folder and checkwhether the database device files are complete. The database device files are as follows:master.dat sysproce.dat tmp_dev.dat

5. Ensure that the SYB.krg file is deleted. When the server powers off abnormally, the Sybasealso exits abnormally and the /opt/sybase/ASE-15_0/SYB.krg file is not deleted. The filedisables the startup of the Sybase. Therefore, delete the file if it still exists after you resetthe Solaris.If any database device files are lost, refer to 12.3.3 Troubleshooting: Loss of DatabaseDevice Files After the Restoration of the File System.

12.3.3 Troubleshooting: Loss of Database Device Files After theRestoration of the File System

This section describes how to handle the loss of database device files after the file system isrestored.




Issue 10 (2010-09-06)

SymptomAfter 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, thedatabase fails to start.

If the device file related to certain application database is lost, the corresponding applicationdatabase and the services related to this database fail to start.

Fault HandlingThe 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 /opt/sybase/interfaces

l /export/home/sybdev/master.dat

l /export/home/sybdev/sysprocs.dat

2. When installing the database, select reinstall to re-establish the application databases ofM2000. For details on the installation of the Sybase and M2000, see the software installationmanual related to each server type.

3. Perform the full backup and the incremental backup to restore the data in the database andthe M2000 configuration files.For details, refer to 10 Backing Up and Restoring the M2000.

12.3.4 Troubleshooting: Failure to Restore the Database Though theFile System Is Intact

This section describes how to handle the failure to restore the database though the file systemis intact.

SymptomAfter the server is shut down exceptionally, the operating system can be restarted normally. Thefile 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:


1> sp_helpdb

2> go

The database log file /opt/sybase/ASE-15_0/install/database server name.log records thefollowing error information:

00:00000:00001:2005/07/24 18:56:29.08 server Error: 926, Severity: 14, State: 100: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.



12-5

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



Fault HandlingThe database is processing transactions when the server is switched off abnormally. Theabnormal exit leads to an exception in the database. To handle the fault, perform the followingsteps:

1. Log in to the M2000 installation directory as user root and run the environment variablescript. 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 followingcommands:# su - dbuser-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> sp_configure "allow updates", 12> go1> update master..sysdatabases set status =-327682> where name="database_name"3> goFor details on how to stop the database service, see 14.2.3 How Do I Stop the Sybase?.-bash-3.00$ exit

CAUTIONThe 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/databaseserver name.cfg are changed to the default values. If all the values are changed to the defaultvalues, 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-- 1 dbuser staff 9620 Jun 24 16:26 SYB.001-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:26 SYB.002-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:26 SYB.003-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:26 SYB.004-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.005




Issue 10 (2010-09-06)

-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.006-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.007-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.008-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.009-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.010-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.011-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.012-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.013-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.014-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.015-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.016-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.017-rw-r--r-- 1 dbuser staff 9690 Jun 24 16:27 SYB.018-rw-r--r-- 1 dbuser staff 9696 Jun 24 16:27 SYB.019-rw-r--r-- 1 dbuser staff 9695 Jun 24 16:34 SYB.020-rw-r--r-- 1 dbuser staff 9694 Jun 24 16:34 SYB.021-rw-r--r-- 1 dbuser staff 9693 Jun 24 16:34 SYB.022-rw-r--r-- 1 dbuser staff 9801 Jun 24 16:34 SYB.023-rw-r--r-- 1 dbuser staff 9797 Jun 24 16:34 SYB.024-rw-r--r-- 1 dbuser staff 9794 Jun 24 16:35 SYB.025-rw-r--r-- 1 dbuser staff 9792 Jun 24 16:35 SYB.026-rw-r--r-- 1 dbuser staff 9790 Jun 24 16:35 SYB.027-rw-r--r-- 1 dbuser staff 9785 Jun 24 16:35 SYB.028-rw-r--r-- 1 dbuser staff 9780 Jun 24 16:35 SYB.029-rw-r--r-- 1 dbuser staff 9779 Jun 24 16:35 SYB.030-rw-r--r-- 1 dbuser staff 9778 Jun 24 16:35 SYB.031-rw-r--r-- 1 dbuser staff 9772 Jun 24 16:35 SYB.032-rw-r--r-- 1 dbuser staff 9770 Jun 24 16:35 SYB.033-rw-r--r-- 1 dbuser staff 9764 Jun 24 16:35 SYB.034-rw-r--r-- 1 dbuser staff 9758 Jun 24 16:35 SYB.035-rw-r--r-- 1 dbuser staff 9756 Jun 24 16:35 SYB.036-rw-r--r-- 1 dbuser staff 9753 Jun 24 16:35 SYB.037-rw-r--r-- 1 dbuser staff 9752 Jul 9 09:51 SYB.038-rw-r--r-- 1 dbuser staff 9753 Aug 6 11:25 SYB.bak-rwxrwxrwx 1 dbuser staff 9752 Jul 9 09:51 SYB.cfg-rw------- 1 dbuser staff 59 Aug 6 11:25 SYB.krgAs 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 thedatabase 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 - dbuserFor 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 theM2000 installation directory with the actual installation directory.

6. Switch to user dbuser and log in as user sa. Then, run the following commands:



12-7

# su - dbuser-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> update master..sysdatabases set status =02> where name="database_name"3> go1>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.




Issue 10 (2010-09-06)

13 Troubleshooting the M2000

About This Chapter

This chapter describes the procedures for troubleshooting the M2000.

13.1 Procedure for Troubleshooting the M2000This section describes the procedure for troubleshooting the M2000. The procedure usuallyconsists of three phases: collecting data, locating faults, and handling faults.

13.2 Collecting M2000 Site and Software InformationThis section describes how to collect the M2000 site and software information.

13.3 Collecting Fault Data Using the Log Information CollectorThis section describes how to collect fault data by using the M2000 log information collector.

M2000Administrator Guide (Sun, S10) 13 Troubleshooting the M2000


13-1

13.1 Procedure for Troubleshooting the M2000This section describes the procedure for troubleshooting the M2000. The procedure usuallyconsists of three phases: collecting data, locating faults, and handling faults.

Collecting DataWhen a fault occurs, collect the following data:l Time when the fault has occurred

l Place where the fault has occurred

l Measures taken and the results

l Version information

l IP addresses

l Alarm information

l Logs

l Internal fault locating information

l Database deadlock information

NOTE

l Logs are categorized into user logs, system logs, and trace files.

l For details on viewing database deadlock information, refer to 14.2.6 How to View DatabaseDeadlock Information.

Locating FaultsThis section describes the procedure for locating faults. The collection and analysis of faultshelp 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 networkdevices. The appearance of the hardware and indicators indicate the hardware faults clearly.

l Software faultsSoftware faults are the faults that occur in the M2000 software, Solaris, and Sybase.

Handling FaultsThis section describes how to handle faults based on different fault causes:l Hardware faults

Refer to the manuals delivered with the associated hardware.l 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 thesoftware installation manual related to each server type.For details on the client faults, refer to the M2000 Online Help.

13 Troubleshooting the M2000M2000



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

l Sybase faults

Refer to the Sybase System Administrator Guide.

The Sybase System Administrator Guide can be obtained from the CD delivered with theserver.

l Uncleared faults

For the uncleared faults, collect all the information related to the faults by referring toCollecting Data and contact Huawei technical support engineers for assistance.

13.2 Collecting M2000 Site and Software InformationThis section describes how to collect the M2000 site and software information.

13.2.1 Collecting the M2000 Site InformationThis section describes how to collect the M2000 site information.

13.2.2 Collecting the Time of M2000 Fault OccurrenceThis section describes how to find out the time when M2000 faults occur.

13.2.3 Collecting the IP Address of the M2000 ServerThis section describes how to obtain the IP address of the M2000 server.

13.2.4 Collecting the Solaris VersionThis section describes how to obtain the version information about the Solaris.

13.2.5 Collecting Sybase Version InformationThis section describes how to collect the version information about the Sybase.

13.2.6 Collecting the M2000 VersionThis section describes how to obtain the version information about the M2000.

13.2.1 Collecting the M2000 Site InformationThis section describes how to collect the M2000 site information.

Procedure

Step 1 Collect the M2000 site information.

Collect the following site information:

l Site name

l Customer contact details

l Hardware model

l Date and time when a fault occurs



13-3

l Fault description

----End

13.2.2 Collecting the Time of M2000 Fault OccurrenceThis 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 ServerThis 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 theM2000 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 VersionThis 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 operatingsystem.

----End

Example# uname -aX




Issue 10 (2010-09-06)

A message similar to the following message is displayed:

SunOS BackupServer 5.10 Generic_138888-07 sun4u sparc SUNW,Netra-240System = SunOSNode = BackupServerRelease = 5.10KernelID = Generic_138888-07Machine = sun4uBusType = <unknown>Serial = <unknown>Users = <unknown>OEM# = 0Origin# = 1NumCPU = 2

In the system output, Release specifies the version of the operating system and its value is5.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 laterversion.

13.2.5 Collecting Sybase Version InformationThis section describes how to collect the version information about the Sybase.

Procedure

Step 1 Run the following commands:


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 theversion number of the patch that is installed.



13-5

When the version number of the Sybase is 15.0.2, the version number of the patch must be15162 or 15679.

When the version number of the Sybase is 15.0.3, the version number of the patch must be16548.

13.2.6 Collecting the M2000 VersionThis 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

ExampleChange to /opt/OMC, which is the default installation path of the M2000 server software. Runthe following commands:

# cd /opt/OMC


# displayVersion

------------------------OMC Version--------------------------Product Name: iManagerM2000Version: iManagerM2000V200R009ENGC00SPC805Release Date: 06/09/09

...

13.3 Collecting Fault Data Using the Log InformationCollector

This section describes how to collect fault data by using the M2000 log information collector.

Contextl The start_collector process and the start_collector_agent process provide the service of the

log collector.l 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.l To start the service, run the /opt/OMC/bin/start_collector command and the /opt/OMC/

bin/start_collector_agent command.l 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 InformationCollector .




Issue 10 (2010-09-06)

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 isiManager M2000 Client.

Step 2 In the Server Information area, enter the following information:

l Server Address: IP address of the server.

l 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 serveras user root. Run the stop_collector -port old port number command to shut down theoriginal port. Then, run the start_collector -port new port number command.

l FTP User Name: ftpuser.

l Password: password of the Solaris user, such as ftpuser.

Step 3 In Items Selection, select time and the information to be collected.

l Trace files in Local Host: collects the trace files of the local client.

l Trace files in server: collects the trace files of the login server.



13-7

l Core files in server: collects the core files of the login server.

l LMT trace file in server: collects the trace files of the LMT.

l Standby Collection: collects the logs of the active node and the standby node at the sametime. In the M2000 single-server system, do not select Standby Collection.

NOTE

l Run the M2000 log information collector to collect fault information. Ensure that both thestart_collector process and the start_collector_agent process are running on the server.

l To check whether the log information collector is running, you can run the ps -ef | grepstart_collector | grep -v grep command. Check whether the start_collector process and thestart_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

ResultBy default, the collected information is saved as a package in the path M2000 client installationdirectory\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.




Issue 10 (2010-09-06)

14 FAQs (Sun)

About This Chapter

This chapter describes FAQs and solutions related to the M2000.

14.1 About SolarisThis section describes some FAQs and solutions related to the Solaris.

14.2 About SybaseThis section describes the FAQs and solutions related to the Sybase.

14.3 About TCP/IP NetworkThis section describes some FAQs and solutions related to the TCP/IP network.

14.4 About Server SoftwareThis section describes some FAQs and solutions related to the M2000 server software.

M2000Administrator Guide (Sun, S10) 14 FAQs (Sun)


14-1

14.1 About SolarisThis 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 FTPThis section describes how to log in as user root through the FTP.

14.1.3 How to Check the Status of the Tape DriveThis 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 andT5220, are equipped with an external tape drive. By default, the external tape drive of theseserver 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 internaltape drive of these server types is also /dev/rmt/0. If the servers with an internal tape drive, suchas V890, M4000, M5000 and E4900, are equipped with an external tape drive, which tape driveshould the backup data be save on?

14.1.5 What are the files in the etc/rc2.d Folder of SolarisThis 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 ServerThis section describes how to view the hardware settings of the M2000 server.

14.1.7 How to Check the Device Status of the M2000 ServerThis section describes the common commands used to check the device status of the M2000server.

14.1.8 Why Unable to Enter the Domain Console of Fire E4900This section describes the solutions to the failure to enter the domain console of the Sun FireE4900.

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 theFTP server according to the actual requirement.

14.1.10 How to Query the Time Zone NameThis section describes how to query a time zone name. Before querying the DST rules of a timezone, you must know the name of the time zone. Based on the time zone name, you can querythe corresponding DST rules.

14.1.11 How Do I Stop the NTP Service on the M2000 ServerThis 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 addressesdoes not affect data read operations on the disk array. Therefore, you are advised to use thefactory-delivered default IP address of the disk array. If the IP address of a disk array needs tobe 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)M2000



Issue 10 (2010-09-06)

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 changeof the IP address of the disk array does not affect data read operations on the disk array. Youare advised to retain the factory default IP address of the disk array. If the IP address of the diskarray 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 6140management 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 thesolution 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 ArrayThis 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 ArraysThis 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 SoftwareThis 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 ThroughTelnet?

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 followingmethod to obtain the rights.



14-3

1. Log in to the server through the system controller (SC), remote system controller (RSC),or extended system controller facility (XSCF) as user root.

2. Open /etc/default/login.# TERM=vt100; export TERM# vi /etc/default/login

3. Find CONSOLE=/dev/console. Comment this line off by adding # at the beginning of theline.

4. Save the changes and then exit the file.5. Check whether the Telnet service is started.

# svcs -l telnetl If the system output contains disable, you can infer that the Telnet service is not started.

Perform 6 again.l 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 FTPThis section describes how to log in as user root through the FTP.

QuestionHow to log in as the root user through FTP?

AnswerIf you fail to use the FTP service as user root, use the following method to obtain the permission.

1. Log in as user root.2. Open /etc/ftpd/ftpusers.

# TERM=vt100; export TERM# vi /etc/ftpd/ftpusers

3. Find root. Comment this line off by adding # at the beginning of the line.4. Save, and then exit the file.

14.1.3 How to Check the Status of the Tape DriveThis section describes how to check the status of the tape drive.

QuestionHow do I check the server tape drive status?

AnswerIf a built-in tape drive is installed, the server identifies the tape drive upon startup. For an externaltape drive, you must install it. To install an external Sun tape drive, such as Ultra 60, performthe following steps:

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

1. Power off the server and all the peripherals.2. Set the ID switch on the tape drive to 4 or 5.3. If you use SCSI interface, connect the SCSI cable to the IN port on the tape drive.4. Switch on the server and all the peripherals and start the system.5. Log in as user root.6. 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 statusThe commands mentioned earlier can be briefly written as mt status.Table 14-1 lists the output.

Table 14-1 Tape drive status

No. Output Tape Drive Status

1 Certance Ultrium 3 tape drive:sense key(0x6)= Unit Attentionresidual= 0 retries= 0file no= 0 block no= 0

The tape drive works normally.A tape is loaded and rewound.

2 /dev/rmt/0n: no tape loaded ordrive offline

The tape is not inserted or notidentified correctly, or theinserted tape is a cleaning tape.

3 /dev/rmt/0n: No such file ordirectory

The previous message indicatesthat the operating system doesnot detect the tape drive.

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 andT5220, are equipped with an external tape drive. By default, the external tape drive of theseserver 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 internaltape drive of these server types is also /dev/rmt/0. If the servers with an internal tape drive, suchas V890, M4000, M5000 and E4900, are equipped with an external tape drive, which tape driveshould the backup data be save on?

QuestionIf the system has multiple tape drives, which tape drive should be used for storing the backupdata?



14-5

Answer1. Check for the number of tape drives in the system.

# ls /dev/rmt0 0bn 0cb 0cn 0hb 0hn 0lb 0ln 0mb 0mn 0u 0ubn0b 0c 0cbn 0h 0hbn 0l 0lbn 0m 0mbn 0n 0ub 0unl If the command result shows only the logical device files that are preceded by 0, it

indicates that only one tape drive is connected.l 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 configDetermine 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. Thistype 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 CertanceUltrium 3. This type of tape drive supports the 400 or 800 GB tape. This tape drivematches 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 statusIf the command results are similar to the following information, it indicates that the tapedrive is functioning well:HP DAT-72 tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file no= 0 block no= 0If 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 SolarisThis section describes the definition of the files in the /etc/rc2.d folder of the Solaris.

QuestionWhat do the files in the /etc/rc2.d folder of the Solaris mean?

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

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 inalphabetical order.

l When the Solaris stops, the Solaris runs the files starting with K in the folder /etc/rc2.d inalphabetical order.

The M2000 server installer creates three start files in the folder /etc/rc2.d/:

l S98sybase: for starting the Sybase

l S98TAO: for starting the TAO service

l S99IMAP: for starting the M2000 service program

l S99Collector: for starting the M2000 Diagnosis

NOTE

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, phase3, and single user phase in the start process respectively.

l The Solaris completes different tasks in different phases. For example, the Solaris checks the memoryin 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 ServerThis 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. Log in as user root.

2. Check different items by running the commands listed in Table 14-2.

Table 14-2 Checking the server configuration

No. Command Output

1 # uname -aX Server model and number ofCPUs

2 # prtconf|grep Memory Memory size

3 # psrinfo -v CPU status

4 # prtdiag Check the status of thehardware.



14-7

14.1.7 How to Check the Device Status of the M2000 ServerThis section describes the common commands used to check the device status of the M2000server.

QuestionWhich commands are often used to check the device status?

AnswerTable 14-3 lists the commands often used for checking the device status.

Table 14-3 Commands for checking the device status

No.

Item Description Hardware configuration

1 HardwareConfiguration

Check the diskstatus.

# iostat -E

Check the CPUstatus.

# psrinfo -v

Check thedevice tree.

# prtconf -D

Check thepower supply.

# prtdiag -v

2 Networkconnection andconfiguration

Check networkconfiguration.

# ifconfig -a

Check networkport speed.

# kstat -p ce:0:ce0:ifspeedThe network port name varies according to the configuration.

Check routeinformation.

# netstat -r

Locate faultsand checknetwork portmessages.

# snoop -d ce0The network port name varies according to the configuration.

Check MACsettings for theIPMPtechnology.

# eeprom local-mac-address?

3 Filesystemanddisk

Check the filesystem.

# more /etc/vfstab

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

No.


partitioning

Check diskpartitioning.

# formatSpecify disk (enter its number): number ofthe disk partition to be checkedformat> ppartition> p

Check systemerror logs.

# more /var/adm/messages | grep err

Check systemerror logsettings.Redirect logsfrom T3/SC/Domain toBlade 150.

Add the contents below to /etc/syslog.conf on the Blade 150:local7.notice /var/adm/messages.t3 local0.notice /var/adm/messages.SC local1.notice /var/adm/messages.DomainA Check messages in /var/adm.

Check for theSolaris versionand patch.

# uname -a

Check allSolaris patches.

# showrev -p

4 Volumeandmirror

Check volumeinformation.

# vxdg listThis step is applicable for only the server with a disk array.


# vxdisk listAll hard disks are online.This step is applicable for only the server with a disk array.


# vxprint -th -g ossdgThe KSTATE column of pl, sd, and v is displayedENABLED, and the STATE column is displayed ACTIVE.

This step is applicable for only the server with a disk array.

Check thelicense ofVolumeManager.

# cd /etc/vx/bin# vxlicrep

Check themirror status.

# metastatNOTE

l This command is applicable for only the servers that use SUNDiskSuite (SDS) or Solaris Volume Manager (SVM) forencapsulating root disks.

l When the M2000 uses the T5220 server, run the raidctl commandto view the mirroring status.



14-9

No.


5 Tapedrive

Check the tapedrive status.

# mt stat

Rewind thetape.

# mt rewind

Forward onestep.

# mt fsr

Forward twosteps.

# mt fsr 2

Backward twosteps.

# mt bsr 2

Check the tapecontent.

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

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 filesfrom the tape tothe disk.

This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example.# gtar xvPfM /dev/rmt/0

Check theSolaris systembackup.

This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example.# ufsrestore -t /dev/rmt/0n

Back up theSolaris to thetape.

This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example.# ufsdump 0ucf /dev/rmt/0n backup folderFor example:# ufsdump 0ucf /dev/rmt/0n backuprestore# ufsdump 0ucf /dev/rmt/0n /dev/vx/rdsk/rootvol

Restoreoperatingsystem fromtape.

This part takes the the logical device of the tape drive, that is, /dev/rmt/0, for example.# ufsdump rvf /dev/rmt/0n

Configure thetape drive.

# drvconfig# tapes

6 CDdriver

Configure theCD-ROM.

# mount -F hsfs -o ro /dev/rdsk/c0t6d0s0 /cdrom

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

No.


7 Floppy disk

Configure thefloppy disk.

# volcheck# mount -F pcfs /dev/diskette/floppy

8 Ethernetportlog

Locate the faultand export thelog.

# /opt/SUNWexplo/bin/explorerObtain the output log in the following path:/opt/SUNWexplo/outputFor example:explorer.83bbbcad.osssvr-2005.08.15.02.05explorer.83bbbcad.osssvr-2005.08.15.02.05.tar.gz

14.1.8 Why Unable to Enter the Domain Console of Fire E4900This section describes the solutions to the failure to enter the domain console of the Sun FireE4900.

QuestionWhen you attempt to enter the domain console, the system displays the message that the systemis busy.

AnswerThe domain console allows for only one connection. If a user is already connected to the domainconsole, the system displays the message that the system is busy. To enter the domain console,perform the following steps:

1. Enter the platform shell.2. Run the connections command to view the connection results.3. Run the disconnect id command to disconnect the console.4. Enter the console.

Exampleosssvr-1-sc0:SC> connections

ID Hostname Idle Time Connected On Connected To--- ----------------------------- --------- -------------- -------------- 1 Localhost 00:01 Aug 26 17:13 Platform 8 Localhost 00:01 Aug 30 13:51 Domain A 11 10.0.119.150 - Aug 30 15:10 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



14-11

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 theFTP server according to the actual requirement.

QuestionHow to Change the Port Number of the FTP Server?

AnswerThis part takes the change of the port number from 21 to 1234 as an example. To change theport number of the FTP server, perform the following steps:

1. Log in to the server as user root.2. Run the following command to modify the /etc/services file:

# vi /etc/services3. 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. On the PC, switch to the command mode and run the ftp command.6. Run the following command to connect to the server through FTP.

ftp> open IP address of the server 1234Type the user name and password of user root to log in to the server.

14.1.10 How to Query the Time Zone NameThis section describes how to query a time zone name. Before querying the DST rules of a timezone, you must know the name of the time zone. Based on the time zone name, you can querythe corresponding DST rules.

QuestionHow to query the name of a time zone?

AnswerTo query the name of a time zone, perform the following steps:

1. Log in to the Solaris server as user root.2. Obtain the information on the country code of the time zone.

# more /usr/share/lib/zoneinfo/tab/country.tabA part of the content to be obtained from the file is as follows:

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

...BR BrazilCL ChileCN 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 + timezone name + comments.

l The north latitude and the east longitude are considered to be positive. The south latitudeand 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 commentsBR -0351-03225 America/Noronha Brazil/DeNoronha Atlantic islandsBR -0127-04829 America/Belem - Amapa, E ParaBR -0343-03830 America/Fortaleza - NE Brazil (MA, PI, CE, RN, PB)BR -0803-03454 America/Recife - PernambucoBR -0712-04812 America/Araguaina - TocantinsBR -0940-03543 America/Maceio - Alagoas, SergipeBR -1259-03831 America/Bahia - BahiaBR -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 SulBR -1535-05605 America/Cuiaba - Mato GrossoBR -0846-06354 America/Porto_Velho - W Para, RondoniaBR +0249-06040 America/Boa_Vista - RoraimaBR -0308-06001 America/Manaus Brazil/West E AmazonasBR -0640-06952 America/Eirunepe - W AmazonasBR -0958-06748 America/Rio_Branco Brazil/Acre AcreCL -3327-07040 America/Santiago Chile/Continental most locationsCL -2709-10926 Pacific/Easter Chile/EasterIsland Easter Island & Sala y GomezCN +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

Country

Time ZoneName Remarks

Brazil

America/Noronha

Brazil/DeNoronha

Atlantic islands

America/Belem - Amapa, E Para

America/Fortaleza

- NE Brazil (MA, PI, CE, RN, PB)

America/Recife - Pernambuco

America/Araguaina

- Tocantins

America/Maceio - Alagoas, Sergipe



14-13

Country

Time ZoneName Remarks

America/Bahia - Bahia

America/Sao_Paulo

Brazil/East S & SE Brazil (GO, DF, MG, ES, RJ,SP, PR, SC, RS)

America/Campo_Grande

- Mato Grosso do Sul

America/Cuiaba - Mato Grosso

America/Porto_Velho

- W Para, Rondonia

America/Boa_Vista

- Roraima

America/Manaus Brazil/West E Amazonas

America/Eirunepe

- W Amazonas

America/Rio_Branco

Brazil/Acre Acre

Chile

America/Santiago

Chile/Continental Most locations

Pacific/Easter Chile/EasterIsland Easter Island & Sala y Gomez

China PRC - -

NOTE

The time zone names of Europe are special. All the European countries are geographically locatedin the east Europe, middle Europe, and west Europe. The corresponding time zone names of the eastEurope, middle Europe, and west Europe are EET, MET, and WET respectively.

14.1.11 How Do I Stop the NTP Service on the M2000 ServerThis section describes how to stop the NTP service on the M2000 server.


Procedure

Step 1 Run the following command to check whether the NTP service is running:


STATE STIME FMRIonline 16:41:28 svc:/network/ntp:default

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

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 notautomatically start whenever the system is restarted.

Step 3 Run the following command to check whether the NTP service is stopped:


STATE STIME FMRIdisabled 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 addressesdoes not affect data read operations on the disk array. Therefore, you are advised to use thefactory-delivered default IP address of the disk array. If the IP address of a disk array needs tobe changed, change the IP address according to the actual situation.

Prerequisitesl You have logged in to the server as user root.

l The server communicates properly with the S3200 disk array.

Backgroundl 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 theactual situation.


l If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect the server anda disk array. Thus, the IP address of Ethernet port nxge3 and the IP address of the disk arraymust be on the same network segment.

l If you have changed the IP address of the disk array on a different segment, you need tochange the IP address of the corresponding Ethernet port nxge3 to ensure that both changedIP addresses are on the same network segment.

ProcedureThis takes the following change as an example to describe how to change the IP address of thedisk array.



14-15

l Before the change:IP address of controller A: 192.168.8.39IP address of controller B: 192.168.8.40

l After the change:IP address of controller A: 10.10.10.39IP 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 configuredproperly: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= NewIP address of controller B gatewayIPAddress=New gateway of controller BsubnetMask=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 is10.10.10.40, New gateway for controller B is 0.0.0.0, and New subnet mask of ControllerB is 255.255.255.0. Run the following command:# SMcli 192.168.8.39 -c "set controller [b] ethernetPort [1] ipAddress= 10.10.10.40gatewayIPAddress=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


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


6. Change the IP address of controller A.# SMcli IP address of controller B -c "set controller [a] ethernetPort [1] ipAddress= NewIP address of controller A gatewayIPAddress=New gateway of controller AsubnetMask=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 is10.10.10.39, New gateway for controller A is 0.0.0.0, and New subnet mask of ControllerB is 255.255.255.0. Run the following command:

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

# SMcli 10.10.10.40 -c "set controller [a] ethernetPort [1] ipAddress= 10.10.10.39gatewayIPAddress=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


8. (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, youneed not stop the M2000 services and the database services. After the modification, you need notrestart the server either.

(1) Log in to server as user root.

(2) Perform the following operations on the server to modify the /etc/hosts file and toreplace 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 themodification and exit.

(3) Perform the following operations on the server to modify the /etc/inet/ipnodes file.


l If the file records the existing IP address of the disk array, replace the existing IPaddress with the new one. After the modification, press Esc and then runthe :wq command to save the modification and exit.


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 changeof the IP address of the disk array does not affect data read operations on the disk array. Youare advised to retain the factory default IP address of the disk array. If the IP address of the diskarray needs to be changed, change it according to the actual situation.

Prerequisitesl You have logged in to the server as user root.

l The communication between the server and the two management Ethernet ports on theS2600 disk array is normal.



14-17

Contextsl Each S2600 disk array has an active controller and a standby controller. Each controller

has one management Ethernet port.l 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 addressaccording to the actual situation.


l If you change the IP address of the disk array on different network segments, continue tochange the IP address of the maintenance Ethernet port on the corresponding server toensure that the two changed IP addresses are on the same network segment.

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

CAUTIONThe 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 theinitial 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 gatewayFor example, to change the IP address of the management Ethernet port on controller B to10.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 change the IP of the controller you logged in, you will log out after you set thenew 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

3. Run the following command to check whether the changed IP address is correct:OceanStor: admin> showctrlip Controller IP Address Subnet Mask Gateway MAC Address A 192.168.8.39 255.255.255.0 192.168.8.1 00:18:82:e2:01:57 B 10.71.15.21 255.255.255.0 10.71.15.1 00:18:82:e2:00:fb

4. Run the following command to exit from controller A:OceanStor: admin> exit

5. 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 FAQs (Sun)M2000



Issue 10 (2010-09-06)

CAUTIONThe 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 theinitial 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 -ggatewayFor example, to change the IP address of the management Ethernet port on controller A to10.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.1When the system displays the following prompt, type y.This operation will change your controller's IP configuration. if you want to change the IP of the controller you logged in, you will log out after you set thenew 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

7. Run the following command to check whether the changed IP address is correct:OceanStor: admin> showctrlip Controller IP Address Subnet Mask Gateway MAC Address A 10.71.15.20 255.255.255.0 10.71.15.1 00:18:82:e2:01:57 B 10.71.15.21 255.255.255.0 10.71.15.1 00:18:82:e2:00:fb

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 6140management host software.

PrerequisiteYou have ensure that the network connection between the server and the 6140 disk array isnormal.

Procedure1. 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 serverEnter 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-19

If the server requires to communicate with the 6140 disk array, you need to ensurethat the IP address of the network port is on the same network segment as the IP addressof controller A on the disk array.In the following commands, the default IP address 192.168.8.39 of the 6140 disk arrayis 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 abovecommand, then the IP address of the server is on the same network segment as the IPaddress of controller A. Proceed with 3. Otherwise, you need to perform 1.3 through1.5 to set the temporary subnet to ensure that the two IP addresses are on the samenetwork 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 tothe last IP address bound to this network port.# ifconfig -alo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000bge0: 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:adbge0: flags=1000842<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 0.0.0.0 netmask 0 ether 0:3:ba:bb:bc:aenxge0: 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:afnxge3: 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 thenetwork port is displayed as bge0:X after you run the previous command. X is a numberstarting from 1. The displayed network port name cannot be used for setting thetemporary subnet. When the X following bge0: is null, use bge0:1 as the name of thenetwork port.In this example, the X following bge0: is null. Thus, you can use bge0:1 as the nameof the network port to set the temporary subnet.

(4) When setting the temporary subnet, ensure that the IP address of the server is on thesame network segment as the IP address of controller A.

CAUTIONThe IP address of the server must be on the same network segment as the IP addressof 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 arrayis taken as an example. Replace it with the actual IP address of controller A.# ifconfig bge0:1 plumb


14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

(5) Check the setting of the temporary subnet.

In the following commands, the default IP address 192.168.8.39 of the 6140 disk arrayis 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 iscorrect. Otherwise, perform 2 to check whether the IP address of the controller A onthe 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 IPaddress 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 portconnector of the controller.

NOTE

Two serial port cables are attached to the pallet of each controller.

l One end is the six-pinned mini DIN connector, and the other end is the basic cable of thestandard 9-pinned serial port connector.

l 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 thebasic 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 serialport, refer to Table 14-5. Then, click OK.

Table 14-5 Setting the properties of the serial port

Attribute Attribute Value

Bit rate 38400

Data bit 8

Parity check none

Stop bit 1

Streaming control 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 withthe terminal.Set baud rate: press <space> within 5 seconds



14-21

NOTE

The serial ports on the disk array request that the Break character be accepted. Set thecorresponding escape sequence for the terminal, and then send the essential Break characterto the controller. For instance, press Ctrl and Break at the same time to generate the Breakcharacter 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.Select Ethernet Port==============================1) Ethernet Port: 02) Ethernet Port: 1Q) QuitEnter Selection: 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-systemArray: array.no.name

In the system output, array.no.name is the default name of the registered 6140disk 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)M2000



Issue 10 (2010-09-06)

(2) If the 6140 disk array is not registered, run the following command to register the diskarray to the management host software through controller A.In the following commands, the default IP address 192.168.8.39 of the 6140 disk arrayis 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-1is taken as an example. Replace the parameters in the commands with the actualparameters 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 6140disk array -m subnet mask controller A

(4) Set the temporary subnet again to make the IP address of the server be on the samenetwork segment as the IP address of controller A.

CAUTIONThe IP address of the server must be on the same network segment as the modified IPaddress 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 diskarray 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 diskarray 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 userroot.

(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 mustbe 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-1is taken as an example. Replace the parameters in the commands with the actualparameters when modifying the IP addresses of other 6140 disk arrays.



14-23

# /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 6140disk array -m subnet mask controller B

5. (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, youneed not stop the M2000 services and the database services. After the modification, you need notrestart the server either.

(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/hostsAfter the modification, press Esc and then run the :wq! command to save themodification and exit.

(3) Perform the following operations on the server to modify the /etc/inet/ipnodes file.# vi /etc/inet/ipnodesl 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 runthe :wq command to save the modification and exit.


14.1.15 What Should I Do When the CD-ROM Drive Cannot Readthe CD-ROM?

This section describes why the CD-ROM drive cannot read the CD-ROM and provides thesolution to this problem.

QuestionAfter the CD-ROM is inserted into the CD-ROM drive, it fails to be read. After the commanddf -k is executed, no contents exist in the /cdrom directory. In the system output, the value ofthe capacity column corresponding to the /cdrom directory is not 100%.

CauseThe system cannot identify the partitioning of the CD-ROM drive.

SolutionTo rectify the fault, perform the following steps:

1. Log in to the server as user root.2. 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)M2000



Issue 10 (2010-09-06)

In the system output, if the value of the capacity column corresponding to the /cdromdirectory 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 numberMessage?

This section describes how to handle the corrupt label - wrong magic number message.

QuestionWhen the format command is executed, the system output contains the corrupt label - wrongmagic number message. This problem occurs in newly mounted disk arrays. The cause is lackof disk labels.

SolutionLabel the disks.

1. Log in to the server as user root.2. Run the following command to refresh the system hardware.

# devfsadm -C

3. 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. Inthis 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?

l 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 logicalpartitions.format> disk

5. Exit format.format> q

14.1.17 What Should I Do When the Server Disk Space IsInsufficient?

This section describes what to do when the server disk space is insufficient.



14-25

QuestionYou 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 usagereaches the threshold, you need to clear the disk space immediately.

l View the disk partition usage in the Hard Disk Monitoring window on the M2000 client.

l Run the df -k command to check the disk partition usage.

How do I do when the server disk space is insufficient?

Solutionl 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 technicalsupport engineers for assistance.

l If the system notifies you of the high disk space usage of the /export/home partition, see9.2.4 Clearing the Disk Space of the M2000 Server to troubleshoot.

l If the system notifies you of the high disk space usage of the root partition / or /opt, performas follows:

1. Log in to the server as user root.2. Run the following command to collect related information:

# du -akd / | sort -nr > /tmp/du.out3. 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:

CAUTIONIf the filepath contains a space, you need to use the DBC quotation marks toenclose the filepath. Otherwise, the system fails to identify this filepath, andaccordingly, the file cannot be uploaded or downloaded. The filepath on theWindows desktop contains space characters. Therefore, do not save files on thedesktop.

ftp> lcd save path of the collected information on the PCftp> cd /tmp

(4) Set the transfer mode to ASCII.ftp> asc

(5) Transfer the collection results.ftp> get du.outAfter the uploading is complete, the system switches to the ftp> state.

(6) Quit the ftp> state.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

ftp> bye

4. Send the collection results to Huawei technical support engineers.

14.1.18 How to Configuring the Monitoring Function of the S2600Disk Array

This section describes how to configure the monitoring function of the S2600 disk array.

QuestionHow should I configure the monitoring function of the S2600 disk array?

AnswerPerform 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

CAUTIONThe 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 thesystem for the first time.

2. Run the following command to check whether the disk array is set with a Trap IP address:OceanStor: admin> showtrapipIndex IP Address Port ID VersionS26000 192.168.8.241 162 2

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

l If the system output is similar to the previous information, check whether theconfigurations in the system output are correct. If they are incorrect, perform 4 to modifythe 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



14-27

Index IP Address Port ID VersionS26000 10.10.10.10 162 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 The system time of the disk array must be the same as that of the connected M2000 server.

l The command chgsystime is used to change the system time. The time ranges from 1970-01-0100:00:00 to 2069-12-31 23:59:00.

6. Run the following command to log out of controller A:OceanStor: admin> exit

7. Log in to the M2000 server as user root.

8. 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 = "trapsender" ip = "IP address of controller A" port = "23001" iorstring = ""/><src name = "trapsender" ip = "IP address of controller B" port = "23001" iorstring = ""/></config>If the IP address of the controller is incorrect in the file, replace the existing IP address witha new IP address. Then, press Esc and run the :wq command to save the modification andquit.

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


14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

# svc_adm -cmd restartsvc UdpDispatchService

14.1.19 How Should I Configure the Monitoring Function for theS3000 Series Disk Arrays

This section describes how to configure the monitoring function for the S3000 series disk arrays,such as S3100 and S3200.

QuestionHow should I configure the monitoring function for the S3000 series disk arrays?

Answer1. Log in to the server that is to be installed with the OceanStor as user root by using the

WinaXe software.2. Install the OceanStor.

NOTE

l If the M2000 is configured with the management console, the OceanStor is installed on themanagement console.

l If the M2000 is not configured with the management console and port 162 on the M2000 serveris 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 The version of the OceanStor is OceanStor S3100 S3200 S6800 Storage Manager forSolaris V200R002C01B024.

l 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 installationpackage.

(3) Upload the decompressed file to the /opt directory in binary mode.ftp server IP addressftp> lcd path of the file on the PCftp> cd /optftp> binftp> put /opt/SMIA-SOL-09.19.04.07.binftp> 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/SMIA-SOL-09.19.04.07.bin.zip

(6) Decompress the OceanStor installation package.# cd /opt/SMIADIR



14-29

# 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/SMclient-SOL.pkg SMclientWhen 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/SMutil-SOL.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 andSecond 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 FAQs (Sun)M2000



Issue 10 (2010-09-06)

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-31

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 serverinstalled 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]: falseWhen the system displays Finish to deploy Sun ST6140/OceanStor S3000Monitor, 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 WinaXesoftware.

(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 whoseDescription is Alert Test Message is available in the alarm list, it indicates that themonitoring of the disk array is enabled.

NOTE

Alternatively, you can check whether the monitoring of the disk array is enabled in the followingway:

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 whoseDescription is Controller tray component failed is available in the alarm list, it indicates thatthe monitoring of the disk array is enabled.

14.1.20 How Should I Uninstall the OceanStor Monitoring SoftwareThis section describes how to uninstall the OceanStor monitoring software.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

QuestionHow should I uninstall the OceanStor monitoring software?

Answer1. Log in to the server installed with the OceanStor as user root.2. 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] yDo 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 Serviceon the M2000 Server?

This section describes how to check the running status of the FTP service on the M2000 server.

PrerequisitesYou have logged in to the server as user root.

Contextl You can use the traditional plain text mode or FTPS as the FTP transfer policy.

l As an FTP application based on the SSL protocol, the FTPS protocol encrypts data duringFTP login connection and data transmission.

l The FTP service on the M2000 server adopts the self-adaptive mode. It can determinewhether to use the FTPS mode or the FTP mode based on the encryption mode adopted bythe FTP client.

l FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to500 must be open.

Procedure1. 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 M2000server is started. If there is no system output, start the FTP service by referring to 14.1.22How 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 serviceon the M2000 server.



14-33

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

You have logged in to the server as user root.

Contextl You can use the traditional plain text mode or FTPS as the FTP transfer policy.

l As an FTP application based on the SSL protocol, the FTPS protocol encrypts data duringFTP login connection and data transmission.

l The FTP service on the M2000 server adopts the self-adaptive mode. It can determinewhether to use the FTPS mode or the FTP mode based on the encryption mode adopted bythe FTP client.

l FTPS can be used between the M2000 and NEs. When FTPS is used, firewall ports 0 to500 must be open.

Procedure1. 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 onthe 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 Serviceon the M2000 Server?

This section describes how to check the running status of the SFTP on the M2000 server.

Prerequisites

You have logged in to the server as user root.

Contextl 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. Thisensures that the data communication between two ends can be performed in an encryptedchannel.

l SFTP is supported between the M2000 server and the M2000 client, and also between theM2000 and an NMS.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

Procedure1. Run the following command to check the running status of the SFTP service:

# svcs -a | grep sshThe system displays the following information:online 18:46:13 svc:/network/ssh:defaultIf online is displayed in the system output, it indicates that the SFTP service on theM2000 server is started. If disabled is displayed in the system output, it indicates that theSFTP service on the M2000 server is not started. For details about how to start the SFTPservice, 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.

PrerequisitesYou have logged in to the server as user root.

Contextl 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 thatthe data communication between two ends can be performed in an encrypted channel.

l SFTP is supported between the M2000 server and the M2000 client, and also between theM2000 and an NMS.

Procedure1. Run the following command to start the SFTP service on the M2000 server:

# svcadm enable svc:/network/ssh:default2. Run the following command to check the running status of the SFTP service:

# svcs -a | grep sshonline is displayed in the system output. That is, the SFTP service on the M2000 server isstarted.

14.2 About SybaseThis 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 SybaseThis 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 ServerThis section describes how to view the name of the Sybase server when the Sybase database isrunning.



14-35

14.2.5 How to Handle Database AlarmsThis section describes why database alarms are generated and how to handle these databasealarms.

14.2.6 How to View Database Deadlock InformationThis section describes how to check the deadlock information about the Sybase database.

14.2.7 Why the Sybase Is Not Started After the Server RestartedThis 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.shThis section describes why the Sybase is not started after the execution of the scriptsvc_profile.sh.

14.2.9 Why the Sybase Backup Database AbortThis section describes how to solve the Sybase backup abort.

14.2.10 Why the Mouse Pointer Changes into an Hourglass upon History Alarm QueryThis section describes how to handle the problem that the mouse pointer changes into anhourglass 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 inthe Database?This section describes what to do when the client is disconnected due to damaged system tablesin 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 usemessage.

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.

QuestionHow do I check the startup status of the Sybase?

AnswerPerform the following steps to check the status of Sybase:

1. Switch to user dbuser.l Log in to the server as dbuser and switch to dbuser state.

l 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 FAQs (Sun)M2000



Issue 10 (2010-09-06)

-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 dataservice 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 userroot.

14.2.2 How to Start the SybaseThis section describes how to start the Sybase service.

QuestionHow to start the Sybase service?

AnswerTo start the Sybase service, perform the following steps:



2. Check whether the Sybase is started by referring to 14.2.1 How Do I Check Whether theSybase Is Started?.

3. 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-37

NOTE

l In the previous command, SYB is the name of the database server. In actual situations, replace thisname with the real name.

l 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:



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

l 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 resultexists, run the kill -9 PID of Sybase command to forcibly stop the Sybase process.

l Switch to user dbuser from user root. After you stop the Sybase, run the exit to roll back to user root.

l If the M2000 server is installed, the Sybase starts automatically upon a restart of the operating system.

14.2.4 How to View the Name of the Sybase ServerThis section describes how to view the name of the Sybase server when the Sybase database isrunning.

1. Log in to the server as user dbuser.2. Run the following command to view the name of the Sybase server:



As shown in the following command result, the name of the database server in this exampleis SYB: dbuser 17046 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB dbuser 17050 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB_back

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

14.2.5 How to Handle Database AlarmsThis section describes why database alarms are generated and how to handle these databasealarms.

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

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 whichthe alarm data is not dumped immediately. Alarms are generated due to lack of alarmdatabase space.

Solution

Check and modify the settings for alarm data dump on the M2000 client. For details abouthow to check and modify the settings for alarm data dump, refer to 8.3 Clearing M2000Databases.

l Alarms are generated in the pmdb alarm database.

Cause analysis

The pmdb alarm database does not delete the outdated performance data in time, whichleads to a scenario in which the outdated performance data is not dumped. Alarms aregenerated 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 theM2000 client.

– Check and modify the settings for performance data dump. For details on how to checkand modify the settings for performance data dump, refer to 8.3 Clearing M2000Databases.

l 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 ofdatabase space.

Solution

– Modify the alarm threshold on the M2000 client.

– Decrease the number of the NEs under the management of the M2000.



14-39

– Check and modify the settings for data dump on the M2000 client. For details abouthow to check and modify the settings for data dump, refer to 8.3 Clearing M2000Databases.

14.2.6 How to View Database Deadlock InformationThis section describes how to check the deadlock information about the Sybase database.

QuestionHow to check the deadlock information about the Sybase database when a fault occurs?

AnswerTo view the database deadlock information, perform the following steps:

1. Log in to the Solaris as user dbuser.2. Run the following commands:

-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> sp_lock

2> go

NOTE





The class column will display the cursor name for locks associated with a cursorfor 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 ismaster,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 withSystem Administrator (SA) role.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

NOTE

The command output displays the traced information on the monitor.

1> use master

2> go

1> select object_name(464004684)

2> go

------------------------------ spt_values

(1 row affected)

1> dbcc sqltext(10)

2> go

DBCC execution completed. If DBCC printed error messages, contact a user withSystem 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 RestartedThis section describes why the Sybase is not started after the M2000 is restarted.

QuestionWhy 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 Sybasesystem 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





CausesThe file SYB.cfg records the settings of the Sybase. If the system cannot find SYB.cfg, it createsnew SYB.cfg for storing the default settings of the Sybase.



14-41

The major cause is that the default values in SYB.cfg are not consistent with those required bythe M2000 system.

The file SYB.cfg is generated once the Sybase is installed, and this file cannot be deleted. TheSybase 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 useraccount dbuser, however, is not authorized to read SYB.cfg.

SYB.cfg OwnershipAfter the Sybase is installed, the owner of SYB.cfg is the user who has installed the Sybase, thatis, dbuser in the M2000 system.

If user root starts the Sybase and changes Sybase settings through isql, root becomes the ownerof 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 theSybase settings through isql.

SolutionWhen the Sybase creates SYB.cfg, the Sybase renames the existing SYB.cfg as SYB.*. Thespecific file name is recorded in the system log of the Sybase, that is, SYB.log. In thisexample,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.shThis section describes why the Sybase is not started after the execution of the scriptsvc_profile.sh.

DescriptionAfter you run the script svc_profile.sh in M2000 Installation Directory, the Sybase service isnot started. The M2000 server default installation path is /opt/OMC.

AnalysisThe 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 serverinstallation 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)M2000



Issue 10 (2010-09-06)

Sybase service. The two settings conflict. In this case, if you set the value of $SYBASE insvc_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 Sybasedefault installation path is /opt/sybase/.

14.2.9 Why the Sybase Backup Database AbortThis 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. Log in to the Solaris as user dbuser.

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




As shown in the following command result, the name of the database server in this example isSYB:

dbuser 17046 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB dbuser 17050 1 0 Dec 11 ? 0:00 /bin/sh ./RUN_SYB_back

14.2.10 Why the Mouse Pointer Changes into an Hourglass uponHistory Alarm Query

This section describes how to handle the problem that the mouse pointer changes into anhourglass upon history alarm query.

Question

After you view the query results of history alarms by using the up and down arrows or scrollbar, the cursor indicates every 125 records that the system is busy. Each busy interval lasts about10 seconds.



14-43

AnswerThe 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 installtionpath/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 <param name="dbservername">SYB</param>: Sybase database server name.

l <param name="dbusername">sa</param>: Sybase user name.

l <param name="dbuserpasswd" type="encrypt">f4310554853445</param>: Encypted Sybase user password.

l <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 fmdb is the alarm database name. obtain the name from ifmssvc.xml.

l tbl_his_alm is the history database table name.

14.2.11 What Should I Do When the Database Cannot Be StartedProperly?

This section describes what to do when the database cannot be started properly.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

Question

How do I do when the database cannot be started properly?

Causel 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 sharedmemory information. The value of the shared memory is x1024x1024/2, and the unit isMB. If the shared memory is not correctly set, installing the Sybase fails. Thus, the systemdisplays a message, indicating that memory is incorrect, during the startup of the Sybase.

l 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 usergroup is staff.

l The owner of the /opt/sybase/ASE-15_0/SYB.cfg configuration file of the Sybase databaseis incorrect.

The correct owner of the /opt/sybase/ASE-15_0/SYB.cfg configuration file is dbuser, andthe user group is staff.

# ls -l /opt/sybase/ASE-15_0/SYB.cfg-rwxrwxrwx 1 dbuser staff 9926 Sep 2 10:50 /opt/sybase/ASE-15_0/SYB.cfg

l After the Sybase database is stopped, the /opt/sybase/SYB.krg file is not successfullydeleted.

l 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 SYB in the /opt/sybase/ASE-15_0/SYB.cfg and /opt/sybase/SYB.krg files is the name of the Sybasedatabase server. Replace SYB in actual situations.

l On the server, run the following command. Based on the system output, obtain the name of the databaseserver.

-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 isSYB1:RUN_SYB1RUN_SYB1_back

Solution

contact Huawei technical support engineers for assistance.

14.2.12 What Should I Do When the Client Is Disconnected Due toDamaged System Tables in the Database?

This section describes what to do when the client is disconnected due to damaged system tablesin the database.



14-45

QuestionThe 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 Current process (0xfee0214)

infected with signal 11 (SIGSEGV)

02:00000:00344:2008/05/27 14:14:38.84 kernel Address 0x0000000080998990

(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 pc: 0x0000000080f4e7b8

NOTE

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.

l On the server, run the following command. Based on the system output, obtain the name of the databaseserver.

-bash-3.00$ cd /opt/sybase/ASE-15_0/install



SolutionThe infected with signal 11 (SIGSEGV) message is in the database log file, which indicatesthat the system table in the master database is damaged. In this case, you need to recover thedatabase.

1. Log in to the server as user root.2. 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 Statesof M2000 Services.For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000Services.

3. Check whether the Sybase service is running. If the Sybase service is running, stop it.# su - dbuserFor details about how to view the Sybase service, see 14.2.1 How Do I Check Whetherthe Sybase Is Started?.For details about how to stop the Sybase services, see 14.2.3 How Do I Stop theSybase?.

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

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

NOTE

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 theactual 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/installmasterWhen the system displays the following message, you can infer that the database issuccessfully 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 sa1> shutdown

2> go

7. Start the Sybase database.Restart the Sybase. For details, see 14.2.2 How to Start the Sybase.

8. Start the M2000 services.For details about how to start the M2000 services, see 7.2.3 Starting the M2000 SystemServices.

14.2.13 What Should I Do When the Number of DatabaseConnections Is Insufficient?

This section describes what to do when the number of database connections is insufficient.

QuestionThe client is disconnected from the server, and the isql is disconnected from the database. Whenviewing the /opt/sybase/ASE-15_0/install/SYB.log log file, the following message isdisplayed:

01:00000:00012:2008/05/28 01:34:38.12 server Error: 1601, Severity: 17,State: 3

01:00000:00012:2008/05/28 01:34:38.12 server 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



14-47

user connections.

NOTE


l On the server, run the following command. Based on the system output, obtain the name of the databaseserver.-bash-3.00$ cd /opt/sybase/ASE-15_0/install



SolutionThe database log file contains the Error: 1601 message, which indicates that the number ofdatabase connections is insufficient. You need to modify the number of database connections.

1. Log in to the server as user root.2. If the M2000 services are running, stop them.

For details about how to stop the M2000 services, see 7.2.4 Stopping the M2000Services.

3. Switch to user dbuser.# su - dbuser

4. Run the following commands to change the maximum number of connections to 800.-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> sp_configure "number of user connections", 8002> gol 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 previousvalues: new configuration value 800, previous value 800.(return status = 0)

l If the system displays the following message, you can infer that the system hasinsufficient 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 theparameter 'number of user connections' to '32766'. 'max memory' should begreater 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 FAQs (Sun)M2000



Issue 10 (2010-09-06)

2> goThen, 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 usemessage.

QuestionThe 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 ASE00:00000:00000:2009/10/24 23:43:08.24 kernel kdconfig: unable to read primary master device00:00000:00000:2009/10/24 23:43:08.24 server kiconfig: read of config block failed

NOTE


l On the server, run the following command. Based on the system output, obtain the name of the databaseserver.-bash-3.00$ cd /opt/sybase/ASE-15_0/install



SolutionThe 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 HowDo I Check Whether the Sybase Is Started?.

14.2.15 What Should I Do to Handle Database Startup Failure Dueto Incorrect User Type?

This section describes how to handle database startup failure due to incorrect user type.

QuestionWhen the database is started, the system displays the following message:

00:00000:00000:2007/11/20 06:37:27.28 kernel SySAM: Using licenses from: /opt/OMC/3rdTools/sybase/SYSAM-2_0/licenses

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 /



14-49

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 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 License manager initialization fails.

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

SolutionThe database startup failure is caused by incorrect user type. The user who starts the databaseuses the environment variables of the M2000. The correct method is to use the environmentvariables of the Sybase to start the database.

1. Log in to the server as user root.2. 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 NetworkThis section describes some FAQs and solutions related to the TCP/IP network.

14.3.1 Why the Network Port Is AbnormalThis 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 AddressThis section describes how to set up the connection between the client and the server usingmultiple IP addresses.

14.3.1 Why the Network Port Is AbnormalThis section describes how to handle the problem of the abnormal network port.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

QuestionDuring the login from the Sun Netra 240 console through telnet, why does the Sun Fire E4900server respond slowly?

AnswerThe cause is that the two ports have the same MAC address. To solve the problem, perform thefollowing 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?"=true3. Restart the Solaris.

14.3.2 How to Connect the Client to the Server with More than OneIP Address

This section describes how to set up the connection between the client and the server usingmultiple IP addresses.

QuestionWhy cannot the client set up a connection with the server?

AnswerIf the server has multiple IP addresses, specify one for M2000 services. Otherwise, the clientcannot set up a connection with the server.

Stop M2000 services and the Sybase before you change the IP address of the M2000 server. Noperformance data or alarm data is processed during the process where you change the server IPaddress. After the services are resumed, the M2000 updates the data with the NEs and processesthe data.

To specify an IP address for M2000 services, perform the following steps:

1. Log in to server as user root.2. 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.3. Switch to dbuser and run the following commands to stop the Sybase.

# su - dbuserTo 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-51

5. Edit /etc/hosts. The host name corresponds to one IP address for connecting clients andNEs.

For example, the server is configured with two IP addresses: 10.161.70.200 and10.121.5.208. The later one is used for connecting clients. In M2000 server installationpath/etc/conf/tao.cfg, the host name is aries. Open /etc/hosts, and then add # on the left of10.161.70.200 to comment off this line.## Internet host table#127.0.0.1 localhost#10.161.70.200 aries loghost10.121.5.208 aries loghost

6. Restart the Solaris.

# sync; sync; sync; sync; sync; sync;


If the M2000 software is installed, the Sybase and the M2000 services restart automaticallyafter the Solaris restarts.

14.4 About Server SoftwareThis section describes some FAQs and solutions related to the M2000 server software.

14.4.1 Why M2000 Services Restart AbnormallyThis section describes how to handle the problem of the abnormal restart of the M2000 services.

14.4.2 Why M2000 Services Stop AbnormallyThis 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 FailsThis 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 withthe upper-layer server in encryption mode. After the setting, the M2000 administration consolecan function as the time source of the lower-layer server, and the M2000 server and NEs cansynchronize 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 encryptionmode, you need to check the running status of the NTP services on the administration consoleto 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 withthe upper-layer server in encryption mode.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

14.4.9 How Should I Check the Running Status of the NTP Services on the M2000 Server (InEncryption Mode)?After setting the M2000 server as the NTP client in encryption mode, you need to check therunning status of the NTP services on the server to ensure that the NTP services are runningproperly.

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 DiskThe M2000 periodically exports the report of system performance, such as CPU usage, memoryusage, and disk usage. Based on the report, you can analyze the load and performance of thehardware system.

14.4.12 How Should I Power On the T5220 Server Through the Serial Port of the SCThis section describes how to power on the T5220 server through the serial port of the SC.

14.4.1 Why M2000 Services Restart AbnormallyThis section describes how to handle the problem of the abnormal restart of the M2000 services.

QuestionWhy do M2000 services restart abnormally?

AnswerThe possible causes are as follows:l The Sybase is faulty.

l The M2000 system is faulty.

To solve the problem, perform the following steps:

1. Log in to the server as user root.2. 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.3. Switch to dbuser and run the following commands to stop the Sybase.

# su - dbuserTo 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. Fordetails, 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 theM2000 services.To know how to start the M2000 services, refer to 7.2.3 Starting the M2000 SystemServices.



14-53

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 AbnormallyThis section describes how to handle the problem of abnormal stop of the M2000 services.

QuestionRun the following command:


When the value of not running in the command result is greater than 0, the service is stoppedabnormally. How to solve this problem?

AnswerThe possible causes are as follows:

l An error occurs during program running

l The startup is stopped manually.

To solve this problem, perform the following steps:

1. Log in to the server as user root.2. 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_svcDo 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.

QuestionThe M2000 services fail to be started.

Causesl 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 FAQs (Sun)M2000



Issue 10 (2010-09-06)

command not foundl 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 startthe M2000 services.The system output is as follows:starting TAO Naming Service [FAIL ]

starting TAO Notification Service [FAIL]

l 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 1To rectify this fault, perform the following steps:

1. Log in to the server as user root.2. Run the environment script.


NOTE

The default installation directory of the M2000 server is /opt/OMC. Replace the directory accordingto the actual situation.

3. Run the following commands to start the M2000 services:# start_svc

Solution to Cause 2 and Cause 3To rectify the fault, perform the following steps:

1. Log in to the server as user root.2. Run the following command to terminate the daemon process.

# kill_daem3. 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-55

QuestionWhy is that the following commands fail to be executed?

l stop_svc

l kill_svc

AnswerIf the system output is command not found, the possible cause is that you do not run theenvironment script before running these commands.

To rectify this fault, perform the following steps:

1. Log in to the server as user root.2. Run the environment script.

For details, see M2000 Command Reference.

14.4.5 Why M2000 Dynamic Data Backup FailsThis section describes how to handle the failure to back up the dynamic M2000 data.

QuestionDuring system backup, the progress bar stops at 30%. Why does the system backup fail?

Causesl The character set settings for the server and the client are not consistent.

l The Sybase backupserver process is executed during system backup. It generates severalsub-processes during the backup. If the backupserver process is stopped abnormally, thesub-processes keep running. Thus, the system backup fails.

Solution for Cause 1The solution for cause 1 is to unify the character settings of the server and client. Perform thefollowing steps:

1. Check character set of the server.# su - dbuser-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> sp_helpsort2> go

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

NOTE





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 $LANGC

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 settingson 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. Log in to the server as user root.2. Run the following command for process query.

# ps -ef | grep svc_backuprestore root 3486 1318 0 08:42:17 pts/8 0:00 grep svc_backuprestore root 3270 18934 0 08:41:19 ? 0:00 sh -c /opt/OMC/bin/svc_backuprestore -cmd backup -m all 2> /dev/null root 3271 3270 4 08:41:19 ? 0:08 /opt/OMC/bin/svc_backuprestore -cmd backup -m all

3. Delete manually other processes except grep svc_backuprestore. In this example,delete the processes titled 3270 and 3271.

# kill -93270 3271



14-57

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 thisexample, delete the processes titled 6217 and 6218.

# kill -96217 6218

14.4.6 How to Set the M2000 Administration Console as theIntermediary-Layer NTP Server (In Encryption Mode)

This section describes how to set the M2000 administration console to synchronize time withthe upper-layer server in encryption mode. After the setting, the M2000 administration consolecan function as the time source of the lower-layer server, and the M2000 server and NEs cansynchronize time with the administration console in encryption mode.

Prerequisitel You have configured the upper-layer NTP server in encryption mode.

l You have obtained the identifier, key type, and authentication code of the upper-layer NTPserver.

l The time zone, date, and time of the M2000 administration console are correctly set.

l You have logged in to the M2000 administration console as user root.

Contextl Normally, the M2000 server is set as the NTP client.

l If no server is available to be set as the intermediary-layer time server, set the administrationconsole of the M2000 system, that is, the Netra 240 server, to be the intermediary-layertime server.

l The upper-layer time server of the M2000 administration console requires that the NTPprotocol must be used. The server running on the Windows operating system uses the SNTPprotocol. Thus, it cannot be used as the upper-layer time server of the M2000 administrationconsole.

Procedure1. Run the following commands to edit the /etc/inet/ntp.keys file:


# vi /etc/inet/ntp.keys

Add the identifier, key type, and authentication code of the upper-layer NTP server to thefile according to the following syntax: At the same time, you can define the authenticationcode required for synchronizing the time between a lower-layer NTP client and the currentserver. Write only one data item in each line.identifier key type authentication code

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

NOTE

l An identifier refers to a positive integer ranging from 1 to 4294967295. Each line in the file mustcontain one unique identifier.

l A key type is a character and refers to the encryption algorithm for calculating NTP services. Srefers to the DES algorithm in standard format, N refers to the DES algorithm in NTP format, Arefers to the ASCII algorithm, and M refers to the MD5 algorithm.

l An authentication code is used as the input parameter corresponding to an algorithm. The formatof an authentication code depends on the corresponding algorithm.

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

3. 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 NTPserver key identifier prefer to specify the IP address and identifier of the upper-layer NTPserver.

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 NTPserver. For example,server IP address of upper-layer NTP server 1 key identifier 1 preferserver 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.0stratum 0 to 1.

The value 1 indicates that the local host functions as the standard time source.6. Delete stratum 0 from fudge 127.127.1.0 stratum 0.

7. In front of broadcast 224.0.1.1 ttl 4, add # to comment out this line to disablethe broadcast mode.

8. Delete 0 from trustedkey 0 to add the identifier of the upper-layer NTP server andthe identifier used by the NTP client for synchronizing time with the current server. Separatethe two identifiers with a space.

9. Add enable auth to the file.

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

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 InstanceAssume that the administration console synchronizes the upper-layer time servers whose IPaddresses are 10.161.94.212 and 10.161.94.214, the upper-layer time server uses the MD5algorithm, the identifiers are 5 and 3, and the corresponding authentication codes are tPol3kRSand l2082skt. Assume that the MD5 algorithm is used, the identifier is 12, and the authenticationcode is k0ssL09a during the synchronization of the time between the client and the current server.



14-59

The contents of the created /etc/inet/ntp.keys file are as follows:

5 M tPol3kRS3 M l2082skt12 M k0ssL09a

The contents of the /etc/inet/ntp.conf file before the modification are as follows:

server 127.127.XType.0fudge 127.127.XType.0 stratum 0broadcast 224.0.1.1 ttl 4keys /etc/inet/ntp.keystrustedkey 0

The contents of the /etc/inet/ntp.conf file after the modification are as follows:

server 10.161.94.212 key 5 preferserver 10.161.94.214 key 3server 127.127.1.0fudge 127.127.1.0#broadcast 224.0.1.1 ttl 4keys /etc/inet/ntp.keysenable authtrustedkey 5 3 12

PostprocessingAfter setting the M2000 administration console as the intermediary-layer NTP server, you needto start the NTP services on the administration console. For details, see 2.5.3 Starting the NTPService on the M2000 Administration Console.

14.4.7 How Do I Check the Running Status of the NTP Services onthe Administration Console (In Encryption Mode)?

After setting the administration console as the intermediary-layer NTP server in encryptionmode, you need to check the running status of the NTP services on the administration consoleto ensure that they are running properly.

ContextAfter 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 toquery the status of the NTP services.

During system test, if you run the ntpq -p command, the displayed address of the remote timesource does not contain *. If you run the ntptrace command, the system displays Timeout orNot Synchronized.

Procedure1. You have logged in to the M2000 administration console as user root.2. Run the following command to view the information about the time source:

# ntpq -pIn the result of the ntpq -p command, the remote field shows the address and status ofthe time source of the M2000 server.

3. Run the following command to check the information about the clock synchronization path:# ntptrace

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

The ntptrace command traces the NTP synchronization path from the host to the top-layerNTP 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 successfullyauthenticated.ntpq> exit

Task InstanceThe 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.0203210.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 NTPserver that the host is synchronized with is 10.71.15.69. The value 1 in the st column indicatesthat the host is located at stratum 1. The symbol * indicates that the NTP services are runningproperly.

The result of the ntptrace command indicates that the host is located at stratum 2, that the IPaddress 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 authenticationbetween the host and the upper-layer NTP server is successful.

14.4.8 How to Set the M2000 Server as the NTP Client (In EncryptionMode)

This section describes how to set the M2000 server as the NTP client to synchronize time withthe upper-layer server in encryption mode.



14-61

Prerequisitel You have configured the upper-layer NTP server in encryption mode.

l You have obtained the identifier, key type, and authentication code of the upper-layer NTPserver.

l The time zone, date, and time of the M2000 server are set correctly.


ContextThe 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 cannotbe used as the upper-layer time server of the M2000 server.

Procedure1. If any M2000 service is running, stop it.

For details, see 7.2.4 Stopping the M2000 Services.2. If any Sybase service is running, run the following command to stop it:

# su - dbuserFor details about how to stop the Sybase services, see 14.2.3 How Do I Stop theSybase?.-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.keysAdd the identifier, key type, and authentication code of the upper-layer NTP server to thefile according to the following syntax: Write only one data item in each line.identifier key type authentication code

NOTE

l An identifier refers to a positive integer ranging from 1 to 4294967295. Each line in the file mustcontain one unique identifier.

l A key type is a character and refers to the encryption algorithm for calculating NTP services. Srefers to the DES algorithm in standard format, N refers to the DES algorithm in NTP format, Arefers to the ASCII algorithm, and M refers to the MD5 algorithm.

l An authentication code is used as the input parameter corresponding to an algorithm. The formatof an authentication code depends on the corresponding algorithm.

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

5. 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 fileto specify the IP addresses and identifiers of upper-layer NTP servers. Each line maps toone NTP server.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

7. Add the following contents to the file:enable authkeys /etc/inet/ntp.keystrustedkey N

N in the last line refers to the identifier used for NTP authentication. If multiple upper-layerNTP servers exist, write the identifiers of these servers in one line. Separate the identifierswith spaces. For example,trustedkey 3 4

8. In front of multicastclient 224.0.1.1, add # to comment out the line to disablethe 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.conffile:# 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 InstanceAssume that the M2000 server is set to synchronize the time of the upper-layer time server whoseIP address is 10.71.15.97, the upper-layer time server uses the MD5 algorithm, the identifier is12, 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 12enable authkeys /etc/inet/ntp.keystrustedkey 12#multicastclient 224.0.1.1

PostprocessingAfter setting the M2000 server as the NTP client, you need to start the NTP services on theserver. For details, see 2.5.6 Starting the NTP Service on the M2000 Server.



14-63

14.4.9 How Should I Check the Running Status of the NTP Serviceson the M2000 Server (In Encryption Mode)?

After setting the M2000 server as the NTP client in encryption mode, you need to check therunning status of the NTP services on the server to ensure that the NTP services are runningproperly.

ContextAfter 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 toquery the status of the NTP services.

During system test, if you run the ntpq -p command, the displayed address of the remote timesource does not contain *. If you run the ntptrace command, the system displays Timeout orNot Synchronized.

Procedure1. You have logged in to the server as user root.2. 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 ofthe 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-layerNTP 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 successfullyauthenticated.ntpq> exit

Task InstanceThe 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)M2000



Issue 10 (2010-09-06)

localhost: stratum 3, offset 0.000040, synch distance 0.8970510.71.15.97: stratum 2, offset 0.000008, synch distance 0.0214210.71.15.69: stratum 1, offset -0.000024, synch distance 0.01059, refid 'LCL'

# ntpq

ntpq> as

ind assID status conf reach auth condition last_event cnt=========================================================== 1 30140 f614 yes yes ok sys.peer reachable 1

ntpq> exit

*10.71.15.97 in the result of the ntpq -p command indicates that the IP address of the NTPserver that the host is synchronized with is 10.71.15.97. The value 2 in the st column indicatesthat the host is located at stratum 2. The symbol * indicates that the NTP services are runningproperly.

The result of the ntptrace command indicates that the host is located at stratum 3, that the IPaddress of the stratum-2 server is 10.71.15.97, and that the IP address of the stratum-1 server is10.71.15.69.

Run the ntpq command, and then type as. If auth is ok, it indicates that the authenticationbetween 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.

ProblemThe M2000 dynamic data fails to be backed up incrementally.

CauseThe causes of the incremental data backup failure are as follows:

l The database logs are not consecutive.

l The disk space is insufficient.

Solutionl The database logs are not consecutive.

1. Check the backup and restore log.# more /opt/OMC/var/logs/backup.logIf the log contains truncate-only transaction dump has beenperformed, it indicates that the database logs are truncated manually.

If the log contains non-logged operation, it indicates that a manual operationis 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.

l The disk space is insufficient.



14-65

1. Check the backup and restore log.# more /opt/OMC/var/logs/backup.logIf the log contains the following information, it indicates that the backup space isinsufficient.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 IsInsufficient?.

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, memoryusage, and disk usage. Based on the report, you can analyze the load and performance of thehardware system.

PrerequisiteYou have logged in to the M2000 server as user root.

ContextThe 3-second period is used for sampling the CPU and the memory and the 1-minute period isused for monitoring disks.

The difference between the monitoring of the clients and the monitoring of the server is that themonitoring on the client can export the usage of the CPU, memory, and disks only at certaintime. The monitoring on the server, however, can export the periodically sampled usage of theCPU, memory, and disks.

l The CPU and the memory performance report file records performance reports in thefollowing format:Hostname, Time, CPU Occupancy(%), MEM Occupancy(%), Physical Memory(KB), Remaining Physical Memory(KB), Swap Memory(KB), Remaining Swap Memory(KB)

l 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 installationpath of the M2000 server software is /opt/OMC.

# cd /opt/OMC

Step 2 Run the environment variant commands.


Step 3 Enable the function of exporting reports.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

l Enable the function of exporting a performance report.# svc_monitor -cmd start -type system

l 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 inM2000 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

l 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 SerialPort of the SC

This section describes how to power on the T5220 server through the serial port of the SC.

QuestionHow should I power on the T5220 server through the serial port of the SC?

AnswerBefore powering on the server, ensure that the following conditions are met:

l The SC of the server is configured.

l The communication between the PC and the Ethernet port on the server SC is normal.

l 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 SCbased on the SSH protocol.In the PuTTY Configuration window, select SSH, enter IP address of the SC in HostName (or IP Address), and then click Open to log in to the SC.

NOTE


l If the PC and SC cannot be connected through the PuTTY, connect them by using a serial portcable. 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.



14-67

3. Run the following command to power on the server:sc> poweron

4. 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. [viewmode], 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, andthen press Enter.

If the Solaris operating system is not installed, the system is switched to the ok state afterthe 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 theT5220 is started.

14 FAQs (Sun)M2000



Issue 10 (2010-09-06)

Date post:	21-Jan-2016
Category:	Documents
Upload:	barkah-yanuar
View:	249 times
Download:	17 times

M2000 Administrator Guide (Sun, S10)(V200R009_10)

Documents