M2000 HA System Administrator Guide (Sun, S10)

M2000V200R010

HA System Administrator Guide (Sun,S10)

Issue 03

Date 2010-08-31

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 03 (2010-08-31) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document is applicable to the M2000 HA system based on the Solaris 10 and Sybase 15.It describes the concepts related to system management tasks, procedures for performing suchtasks, routine and emergency maintenance of the system, usage of common commands and tools,and troubleshooting.

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

Product Name Version

M2000 V200R010

Intended AudienceThe intended audiences of this document are network administrators.

Revision History

03 (2010-08-31)

The third formal release.

Compared with 02 (2010-08-05), the following content is modified.

Content Description

2.4.1 Powering On the M2000 (HA,T5220)

The content descriptions are changed.

HA System Administrator Guide (Sun, S10) About This Document


iii

Content Description

9.1 Introduction to M2000 Processes andServices

The content descriptions are changed.

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

New added.

16.1.19 How Should I Uninstall theOceanStor Monitoring Software

New added.

02 (2010-08-05)

The second formal release.

01 (2010-07-10)

Initial release. Also, the first formal release.

Organization1 M2000 High Availability System

This chapter describes the features, working principles, logical architecture, and softwarearchitecture of the M2000 HA system.

2 Powering the M2000 On or Off (HA)

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

3 Managing Cluster Resources of the M2000 (HA)

This chapter describes how to manage the cluster resources of the M2000 HA system.

4 Setting the M2000 Time (HA)

This chapter describes how to set the server time and the client time to ensure that the specifiedtime meets the requirements and is synchronized with the Huawei mobile equipment.

5 Configuring the IP Address of the M2000 Server (HA)

This chapter describes how to set the host name and IP address of the server in the M2000 HAsystem.

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

7 Managing the M2000 Users (HA)

About This Document HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)

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.

8 Managing OSS System (HA)

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.

9 Managing the M2000 Processes and Services (HA)

This chapter describes how to manage the processes and services of the M2000 HA system. Themanagement of the processes and services ensures the smooth operation of the M2000 HAsystem.

10 Managing the M2000 Databases

This chapter describes how to manage the M2000 databases.

11 Managing the M2000 Files and Disks (HA)

This chapter describes how to manage the file systems and disks on the M2000 server and client.

12 Backing Up and Restoring the M2000 (HA)

This chapter describes how to back up and restore the M2000 HA system.

13 M2000 Routine Maintenance (HA)

This chapter lists the maintenance items and provides guidance for the routine maintenance ofthe M2000 HA system. You can add or delete the maintenance items based on requirements.

14 M2000 Emergency Maintenance (HA)

This chapter describes the emergency maintenance procedures for serious faults in the serverand clients of the M2000 HA system. These procedures include the emergency maintenance forthe server in the M2000 HA system and the M2000 clients, and the procedure for powering offthe M2000 server in exceptional situations.

15 Troubleshooting the M2000

This chapter describes the procedures for troubleshooting the M2000.

16 FAQs (HA, Sun)

This chapter describes some frequently asked questions (FAQs) and the answers regarding theM2000 HA system.

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.



v

Symbol Description

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.

[ ] 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.

About This Document HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)


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

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.



vii

Contents

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

1 M2000 High Availability System............................................................................................1-11.1 Features and Working Principles of the HA System.......................................................................................1-21.2 Logical Architecture of the HA System..........................................................................................................1-31.3 Software Architecture of the HA System........................................................................................................1-3

2 Powering the M2000 On or Off (HA).....................................................................................2-12.1 Powering the M2000 On or Off (HA, Netra 240)...........................................................................................2-2

2.1.1 Powering On the M2000 (HA, Netra 240).............................................................................................2-22.1.2 Powering Off the M2000 (HA, Netra 240)............................................................................................2-4

2.2 Powering the M2000 On or Off (HA, V890)..................................................................................................2-62.2.1 Powering On the M2000 (HA, V890)....................................................................................................2-62.2.2 Powering Off the M2000 (HA, V890)...................................................................................................2-9

2.3 Powering the M2000 On or Off (HA, E4900)..............................................................................................2-122.3.1 Powering On the M2000 (HA, E4900)................................................................................................2-122.3.2 Powering Off the M2000 (HA, E4900)................................................................................................2-16

2.4 Powering the M2000 On or Off (HA, T5220)..............................................................................................2-182.4.1 Powering On the M2000 (HA, T5220)................................................................................................2-192.4.2 Powering Off the M2000 (HA, T5220)................................................................................................2-21

2.5 Powering the M2000 On or Off (HA, M4000/M5000) ................................................................................2-232.5.1 Powering On the M2000 (HA, M4000/M5000)...................................................................................2-242.5.2 Powering Off the M2000 (HA, M4000/M5000)..................................................................................2-27

3 Managing Cluster Resources of the M2000 (HA).................................................................3-13.1 Introduction to Cluster Resources of the M2000 (HA)...................................................................................3-2

3.1.1 Work Principle of the Sun Cluster......................................................................................................... 3-23.1.2 Resource Planning for the M2000 (HA)................................................................................................3-33.1.3 Automatic Switchover Conditions of Active and Standby Nodes.........................................................3-3

3.2 Switching Over Active and Standby Nodes....................................................................................................3-43.2.1 Automatic Switchover Conditions of Active and Standby Nodes.........................................................3-43.2.2 Manually Switching Over Active and Standby Nodes (HA).................................................................3-5

3.3 Registering the resource of the Sybase........................................................................................................... 3-73.3.1 Installing the Sybase Agent (HA).......................................................................................................... 3-83.3.2 Modifying the File sybase_stop_servers in the Folder /opt/SUNWscsyb/bin....................................... 3-9

HA System Administrator Guide (Sun, S10) Contents


ix

3.3.3 Modifying the File sybase_start in the Folder /opt/SUNWscsyb/bin..................................................3-103.3.4 Registering the Sybase to the Sun Cluster...........................................................................................3-103.3.5 Checking the Register of the Sybase Resource....................................................................................3-113.3.6 Activating sybase_rs............................................................................................................................3-12

3.4 Registering the resource of the M2000.........................................................................................................3-133.4.1 Installing the M2000 Registration Package.........................................................................................3-133.4.2 Registering the M2000 Server Application to the Sun Cluster(Netra240&V890&E4900).................3-143.4.3 Registering the M2000 Server Application to the Sun Cluster (T5220&M4000&M5000)................3-153.4.4 Checking the Register of the M2000 Server Application....................................................................3-153.4.5 Activating M2000 Resources...............................................................................................................3-16

3.5 Managing Cluster Resources.........................................................................................................................3-183.5.1 Viewing Configured Resources...........................................................................................................3-193.5.2 Starting Cluster Monitoring on Resources...........................................................................................3-193.5.3 Stopping Cluster Monitoring on Resources.........................................................................................3-193.5.4 Starting the M2000 Services (HA).......................................................................................................3-203.5.5 Stopping M2000 Services (HA)...........................................................................................................3-213.5.6 Starting the Sybase (HA)......................................................................................................................3-213.5.7 Stopping the Sybase (HA)....................................................................................................................3-22

4 Setting the M2000 Time (HA)..................................................................................................4-14.1 Time Management for the Huawei Mobile Network......................................................................................4-2

4.1.1 Introduction to Time Synchronization...................................................................................................4-24.1.2 Introduction to the NTP/SNTP...............................................................................................................4-34.1.3 Time Synchronization Modes of Huawei Mobile Network...................................................................4-64.1.4 Introduction to the DST........................................................................................................................4-12

4.2 Modifying the Date and Time on the M2000 Server (HA)...........................................................................4-124.3 Changing the Time Zone of the M2000 Server Without Using DST (HA)..................................................4-144.4 Modifying the Date, Time, and Time Zone on the M2000 Client................................................................4-164.5 Configuring the NTP Service of the M2000 (HA)........................................................................................4-17

4.5.1 Checking the Time Settings of the M2000 Server (HA)......................................................................4-184.5.2 Setting the M2000 Administration Console as the Secondary NTP Server.........................................4-184.5.3 Starting the NTP Service on the M2000 Administration Console.......................................................4-204.5.4 Checking the Running Status of the NTP Service on the M2000 Administration Console.................4-204.5.5 Setting the M2000 Server as an NTP Client (HA system)...................................................................4-214.5.6 Starting the NTP Service on the M2000 Server (HA).........................................................................4-234.5.7 Checking the Running Status of the NTP Service on the M2000 Server (HA)...................................4-244.5.8 Setting the NTP Service on the M2000 Client.....................................................................................4-25

4.6 Setting DST for the M2000 (HA).................................................................................................................4-27

5 Configuring the IP Address of the M2000 Server (HA)......................................................5-15.1 Adding or Deleting a Route of the M2000 Server..........................................................................................5-25.2 Changing the IP Address of the M2000 Server (HA).....................................................................................5-35.3 Changing the IP Address of Ethernet Port nxge3 on the M2000 Server (HA).............................................5-125.4 Modifying the IP Address of the SC or RSC or XSCF on the M2000 Server..............................................5-14

Contents HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)

5.4.1 Modifying the IP Address of the SC on the Netra 240 Server.............................................................5-145.4.2 Changing the IP Address of the RSC on the V890 Server...................................................................5-155.4.3 Modifying the IP Address of the SC on the E4900 Server..................................................................5-165.4.4 Modifying the IP Address of the SC on the T5220 Server..................................................................5-185.4.5 Changing the IP Address of the XSCF on the M4000/M5000 Server.................................................5-19

5.5 Modifying the IP Address of the Disk Array................................................................................................5-215.5.1 Modifying the IP Address of the 3320 Disk Array..............................................................................5-225.5.2 Changing the IP Address of the S3X00 Series Disk Array (Serial Port Mode)...................................5-235.5.3 Changing the IP Address of the 6140 Disk Array (Serial Port Mode).................................................5-285.5.4 Changing the IP Address of the S2600 Disk Array (Serial Port Mode)..............................................5-32

6 Managing the M2000 Clients...................................................................................................6-16.1 Managing Files and Disks on M2000 Clients.................................................................................................6-2

6.1.1 Introduction to the M2000 Client File System.......................................................................................6-26.1.2 Clearing the Disk Space of an M2000 Client.........................................................................................6-4

6.2 Monitoring the Login Status of the M2000 Clients........................................................................................ 6-56.3 Setting the Number of Clients Accessible on a PC.........................................................................................6-56.4 Setting the Time Information on the M2000 Client........................................................................................6-6

6.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client.........................................................6-76.4.2 Setting the NTP Service on the M2000 Client.......................................................................................6-7

7 Managing the M2000 Users (HA)............................................................................................7-17.1 Types of M2000 Users....................................................................................................................................7-2

7.1.1 Introduction to Solaris Users..................................................................................................................7-27.1.2 Introduction to Sybase Users..................................................................................................................7-47.1.3 NE Users................................................................................................................................................ 7-47.1.4 Principles of NM User Authorization.................................................................................................... 7-67.1.5 Principles of NE User Authorization..................................................................................................... 7-7

7.2 Managing Solaris Users (HA).........................................................................................................................7-77.2.1 Introduction to Solaris Users..................................................................................................................7-87.2.2 Changing the Password of User root...................................................................................................7-107.2.3 Changing the Password of User dbuser..............................................................................................7-117.2.4 Changing the Password of User omcuser............................................................................................7-117.2.5 Changing the Password of the User ftpuser (HA)................................................................................7-127.2.6 Creating a Solaris User.........................................................................................................................7-147.2.7 Deleting a Solaris User.........................................................................................................................7-15

7.3 Managing Sybase Users (HA).......................................................................................................................7-167.3.1 Introduction to Sybase Users................................................................................................................7-167.3.2 Changing the Password of the User sa (HA)........................................................................................7-16

7.4 Managing OM Users.....................................................................................................................................7-19

8 Managing OSS System (HA)...................................................................................................8-18.1 Monitoring the M2000 Server (HA)............................................................................................................... 8-3

8.1.1 Refreshing the Monitoring Information.................................................................................................8-4



xi

8.1.2 Checking the CPU and Memory Usage Information About the M2000 Server (HA)...........................8-48.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client (HA).........................................................................................................................................................................8-58.1.4 Checking the Database Usage Information About the M2000 Server Through the M2000 Client.......8-78.1.5 Checking the M2000 Services................................................................................................................8-88.1.6 Checking the Status of the M2000 Processes.........................................................................................8-98.1.7 Viewing the Information about M2000 Server Components...............................................................8-108.1.8 Saving the Monitoring Information......................................................................................................8-108.1.9 Setting Alarm Thresholds for the M2000............................................................................................8-10

8.2 Querying the System Logs of the M2000.....................................................................................................8-188.3 Collecting NM Log Files...............................................................................................................................8-198.4 Querying NE Subareas..................................................................................................................................8-218.5 Managing the M2000 License.......................................................................................................................8-21

8.5.1 Querying the M2000 License...............................................................................................................8-228.5.2 Updating the M2000 License...............................................................................................................8-22

8.6 Check OMC status........................................................................................................................................8-228.7 Integrated Task Management........................................................................................................................8-23

8.7.1 Overview of Integrated Task Management..........................................................................................8-248.7.2 Customizing the Interface for Managing Timing Tasks......................................................................8-398.7.3 Creating a User Timing Task...............................................................................................................8-408.7.4 Modifying a Timing Task....................................................................................................................8-418.7.5 Managing Timing Tasks.......................................................................................................................8-428.7.6 Browsing the Information of Timing Tasks.........................................................................................8-458.7.7 Viewing the Task Execution................................................................................................................8-468.7.8 Viewing the Task History....................................................................................................................8-468.7.9 Downloading Task Execution Tasks....................................................................................................8-478.7.10 Downloading Result Files..................................................................................................................8-47

8.8 Reference of the OSS Management GUI......................................................................................................8-508.8.1 Interface Description: Managing Scheduled Tasks..............................................................................8-538.8.2 Interface Description: M2000 Log Information Collector...................................................................8-558.8.3 Parameters for the NE Partitioning Information..................................................................................8-558.8.4 Parameters for Querying the M2000 License ......................................................................................8-568.8.5 Parameters for Setting Monitoring Parameters of the M2000 Server..................................................8-578.8.6 Parameters for Monitoring the M2000 Server Service Status..............................................................8-648.8.7 Parameters for Monitoring the M2000 Server Process Status.............................................................8-658.8.8 Parameters for Monitoring the M2000 Server Hard Disk Status.........................................................8-668.8.9 Parameters for Monitoring the M2000 Server Database Status...........................................................8-668.8.10 Parameters for Monitoring the M2000 Server Status.........................................................................8-678.8.11 Parameters for Viewing the Information about M2000 Server Components.....................................8-688.8.12 Parameters for Setting Task Filter Conditions...................................................................................8-698.8.13 Parameters for Setting the Common Information for Creating or Replicating a Task.......................8-708.8.14 Parameters for Setting Common Parameters for Timing Tasks.........................................................8-718.8.15 Parameters for Setting the Time When a Periodic Task Is Created or Copied..................................8-73


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

Issue 03 (2010-08-31)

8.8.16 Parameters for Setting the Time When a One-Time Task Is Created or Copied...............................8-748.8.17 Parameters for Modifying a Database Capacity Management Task..................................................8-758.8.18 Parameters for Modifying the Export of Performance Data..............................................................8-798.8.19 Parameters for Modifying a Configuration Data Export Task...........................................................8-818.8.20 Parameters for Modifying the Export of NE Logs.............................................................................8-838.8.21 Parameters for Modifying the Export of Inventory Data...................................................................8-848.8.22 Parameters for Modifying an Alarm/Event Log Export Task............................................................8-858.8.23 Parameters for Modifying the Export of M2000 Logs.......................................................................8-868.8.24 Parameters for Modifying NE Basic Information Export Task.........................................................8-878.8.25 Parameters for Modifying the Synchronization of NE Configuration Data ......................................8-888.8.26 Parameters for Modifying the Synchronization of Inventory Data....................................................8-888.8.27 Parameter Description: Modifying a Data Backup Task of the M2000.............................................8-898.8.28 Parameters for Creating/Modifying/Copying NE Backup.................................................................8-898.8.29 Parameters for Creating/Modifying/Copying MML Command Script..............................................8-908.8.30 Parameters for Creating, Modifying, or Copying a Configuration Report Export Task....................8-928.8.31 Parameter Description: Creating, Viewing, or Modifying a Scheduled Report Task........................8-938.8.32 Parameters for Creating/Modifying/Copying Scheduled NodeB License Allocation Tasks.............8-978.8.33 Parameters for Creating/Modifying/Copying Scheduled BSC or RNC License Allocation Tasks.......................................................................................................................................................................8-988.8.34 Parameters for Creating/Modifying/Copying a Task for Testing BTS Cabinet-Top Power..............8-998.8.35 Parameters for Creating/Modifying/Copying an RSSI Test Task......................................................8-998.8.36 Parameters for Creating/Modifying/Copying Software Download..................................................8-1008.8.37 Parameters for Creating/Modifying/Copying a Dual-Homing Auto Consistency Check Task.......8-1008.8.38 Parameters for Creating/Modifying/Copying an HSL Script Task..................................................8-1018.8.39 Parameters for Creating/Modifying/Copying the Export of NE Upgrade Log................................8-1028.8.40 Parameters for Creating/Modifying/Copying a CME Upload Task.................................................8-1028.8.41 Parameters for Creating/Modifying/Copying Cell Parameters Compare Task................................8-1038.8.42 Parameters for Creating/Modifying/Copying Cell Consistency Check Task..................................8-1038.8.43 Parameters for Creating/Modifying/Copying a CME Current Area Export Task............................8-1048.8.44 Parameters for Setting Time of Timing Tasks.................................................................................8-1048.8.45 Parameters for Selecting Objects for OMC Check..........................................................................8-1058.8.46 Parameters for Collecting NM Logs Parameters..............................................................................8-106

9 Managing the M2000 Processes and Services (HA).............................................................9-19.1 Introduction to M2000 Processes and Services...............................................................................................9-2

9.1.1 3rdTool_agent Process...........................................................................................................................9-59.1.2 adn_agent Process..................................................................................................................................9-59.1.3 adss_agent Process.................................................................................................................................9-69.1.4 antenna_agent Process............................................................................................................................9-69.1.5 ce_agent Process....................................................................................................................................9-69.1.6 cmdc_agent Process...............................................................................................................................9-69.1.7 cmengine_agent Process........................................................................................................................9-69.1.8 cmeserver_agent Process........................................................................................................................9-7



xiii

9.1.9 cmexp_agent Process.............................................................................................................................9-79.1.10 cmserver_agent Process.......................................................................................................................9-79.1.11 cnnhc_agent Process............................................................................................................................9-89.1.12 corba_agent Process.............................................................................................................................9-89.1.13 cpm_agent Process...............................................................................................................................9-89.1.14 devdoc_agent Process..........................................................................................................................9-89.1.15 dsXXXX agent Process..........................................................................................................................9-89.1.16 eam_agent Process...............................................................................................................................9-99.1.17 fars_agent Process................................................................................................................................9-99.1.18 fmnotify_agent Process........................................................................................................................9-99.1.19 FMPreServiceXXXX_agent Process...................................................................................................9-109.1.20 fnlicense_agent Process......................................................................................................................9-109.1.21 glmssyn_agent Process.......................................................................................................................9-109.1.22 ifms_agent Process.............................................................................................................................9-109.1.23 ipqdt_agent Process............................................................................................................................9-119.1.24 ipm_agent Process..............................................................................................................................9-119.1.25 irp_agent Process................................................................................................................................9-119.1.26 itm_agent Process...............................................................................................................................9-129.1.27 lcsserver_agent Process......................................................................................................................9-129.1.28 lic_agent Process................................................................................................................................9-139.1.29 log_agent Process...............................................................................................................................9-139.1.30 necomm_agent Process......................................................................................................................9-139.1.31 maintain_agent Process......................................................................................................................9-139.1.32 manager_agent Process......................................................................................................................9-149.1.33 medXXXX_agent Process................................................................................................................... 9-149.1.34 nelicense_agent Process.....................................................................................................................9-149.1.35 neuser_agent Process..........................................................................................................................9-149.1.36 ngnffs_agent Process..........................................................................................................................9-159.1.37 ngnnis_agent Process......................................................................................................................... 9-159.1.38 ngnni112_agent Process.....................................................................................................................9-159.1.39 ngntestmanage_agent Process............................................................................................................9-159.1.40 nhcserver_agent Process.................................................................................................................... 9-159.1.41 nicserver_agent Process..................................................................................................................... 9-159.1.42 nimserver_agent Process....................................................................................................................9-169.1.43 nms_mml_agent Process....................................................................................................................9-169.1.44 partition_agent Process...................................................................................................................... 9-169.1.45 pm_agent Process...............................................................................................................................9-169.1.46 pmexp_agent Process.........................................................................................................................9-179.1.47 pmmon_agent Process........................................................................................................................9-179.1.48 pmncdXX01_agent Process................................................................................................................9-179.1.49 porttrunk_agent Process.....................................................................................................................9-179.1.50 proxy_agent Process...........................................................................................................................9-18


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

Issue 03 (2010-08-31)

9.1.51 PRSAssistantService_agent Process..................................................................................................9-189.1.52 prsdc_agent Process...........................................................................................................................9-189.1.53 prsfs_agent Process............................................................................................................................9-189.1.54 prsreport_agent Process......................................................................................................................9-199.1.55 prssum_agent Process........................................................................................................................9-199.1.56 rn_agent Process.................................................................................................................................9-199.1.57 ScriptModuleService_agent Process..................................................................................................9-199.1.58 scriptserver_agent Process.................................................................................................................9-199.1.59 sm_agent Process...............................................................................................................................9-209.1.60 snmp_agent Process...........................................................................................................................9-209.1.61 son_agent Process..............................................................................................................................9-209.1.62 swm_agent Process............................................................................................................................9-209.1.63 threshold_agent Process.....................................................................................................................9-219.1.64 uap_agent Process..............................................................................................................................9-219.1.65 udpdispatch_agent Process.................................................................................................................9-219.1.66 umgupdsvr_agent Process..................................................................................................................9-219.1.67 xftpXX01_agent Process.....................................................................................................................9-219.1.68 Processes and Services Related to Each Northbound Interface.........................................................9-229.1.69 Checking the Status of the M2000 Processes.....................................................................................9-23

9.2 Managing M2000 Services (HA)..................................................................................................................9-249.2.1 Checking the M2000 Services..............................................................................................................9-249.2.2 Viewing the States of M2000 Services (HA).......................................................................................9-259.2.3 Starting the M2000 Services (HA).......................................................................................................9-269.2.4 Stopping M2000 Services (HA)...........................................................................................................9-27

10 Managing the M2000 Databases..........................................................................................10-110.1 M2000 Database..........................................................................................................................................10-2

10.1.1 cmedb Database..................................................................................................................................10-310.1.2 farsdb Database..................................................................................................................................10-410.1.3 fmdb Database....................................................................................................................................10-410.1.4 itfndb Database...................................................................................................................................10-510.1.5 omcdb Database.................................................................................................................................10-510.1.6 omceamdb Database...........................................................................................................................10-710.1.7 omclogdb Database............................................................................................................................10-810.1.8 omcsmdb Database.............................................................................................................................10-910.1.9 omctempdb Database.......................................................................................................................10-1010.1.10 omctmdb Database.........................................................................................................................10-1010.1.11 pmcomdb Database........................................................................................................................10-1110.1.12 pmdb Database...............................................................................................................................10-1310.1.13 sumdb Database..............................................................................................................................10-1410.1.14 swmdb Database.............................................................................................................................10-17

10.2 Viewing the States of M2000 Databases ..................................................................................................10-18



xv

10.2.1 Checking the Database Usage Information About the M2000 Server Through the M2000 Client.....................................................................................................................................................................10-1810.2.2 Viewing the Database Usage of the M2000 Server Using Sybase Commands...............................10-19

10.3 Clearing M2000 Databases.......................................................................................................................10-2110.4 Backing Up M2000 Databases..................................................................................................................10-23

11 Managing the M2000 Files and Disks (HA)......................................................................11-111.1 Managing Files and Disks on M2000 Clients.............................................................................................11-2

11.1.1 Introduction to the M2000 Client File System...................................................................................11-211.1.2 Clearing the Disk Space of an M2000 Client.....................................................................................11-4

11.2 Managing Files and Disks on the M2000 Server (HA)...............................................................................11-511.2.1 Introduction to the M2000 Server File System (HA).........................................................................11-511.2.2 Viewing the Disk Usage of the M2000 Server Using Solaris Commands.......................................11-1411.2.3 Clearing the Disk Space of the M2000 Server.................................................................................11-14

12 Backing Up and Restoring the M2000 (HA)......................................................................12-112.1 M2000 Backup and Restore Solutions........................................................................................................12-2

12.1.1 Backup of M2000 Dynamic Data.......................................................................................................12-212.1.2 Policies of M2000 Data Backup.........................................................................................................12-412.1.3 Scenarios of M2000 Data Restoration............................................................................................... 12-4

12.2 Backing Up and Restoring M2000 Dynamic Data (HA)............................................................................12-512.2.1 Setting a Storage Device of Backup Data Through the Client (HA)................................................. 12-512.2.2 Periodically Backing Up the M2000 Dynamic Data (HA)................................................................ 12-712.2.3 Manually Backing Up the M2000 Dynamic Data (HA)....................................................................12-912.2.4 Restoring the M2000 Dynamic Data (HA)......................................................................................12-10

13 M2000 Routine Maintenance (HA).....................................................................................13-113.1 M2000 Routine Maintenance Items (HA)...................................................................................................13-213.2 Daily Maintenance Operations (HA).......................................................................................................... 13-4

13.2.1 Checking the Cluster Status (HA)......................................................................................................13-613.2.2 Checking the Status of Performance Measurement........................................................................... 13-713.2.3 Checking the Missing Performance Result........................................................................................13-713.2.4 Checking the Alarm Reception..........................................................................................................13-813.2.5 Checking the NMS Connection..........................................................................................................13-813.2.6 Checking the Functionality of Alarm Box.........................................................................................13-813.2.7 Checking the Owner of the M2000 File System................................................................................13-913.2.8 Check OMC Alarms/Events...............................................................................................................13-913.2.9 Checking Connections Between the M2000 and NEs.....................................................................13-1313.2.10 Checking M2000 Logs...................................................................................................................13-1313.2.11 Checking the Error Log of the Solaris...........................................................................................13-1413.2.12 Checking the Disk Usage of the M2000 Server.............................................................................13-1513.2.13 Checking the States of M2000 Databases......................................................................................13-1513.2.14 Checking the States of M2000 Services.........................................................................................13-1613.2.15 Checking the Core Files on the Server...........................................................................................13-1613.2.16 Checking the Hardware of the M2000 Server................................................................................13-17


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

Issue 03 (2010-08-31)

13.2.17 Checking the SMC Collection Results...........................................................................................13-1713.3 Weekly Maintenance Operations (HA).....................................................................................................13-18

13.3.1 Checking the Configuration of Alarm Timing.................................................................................13-1913.3.2 Checking the Configuration of Automatic Log Dump.....................................................................13-1913.3.3 Checking the Synchronization Time of NE Log..............................................................................13-2113.3.4 Checking the Configuration of the File Server ...............................................................................13-2113.3.5 Checking the Configuration of System Backup...............................................................................13-2213.3.6 Checking the Configuration of System Monitoring.........................................................................13-2213.3.7 Checking the Synchronization Time of NE Configuration..............................................................13-3013.3.8 Checking the Threshold of Network Management Capability.........................................................13-3113.3.9 Checking the Status of the M2000 Routes.......................................................................................13-3113.3.10 Backing Up the M2000..................................................................................................................13-3113.3.11 Checking the Time of the M2000 Server (HA)..............................................................................13-3313.3.12 Checking the States of M2000 Disks.............................................................................................13-34

13.4 Monthly Maintenance Operations (HA)...................................................................................................13-3513.4.1 Checking the Power Supply of the M2000 Server...........................................................................13-3513.4.2 Checking the Peripherals of the M2000 Server...............................................................................13-3613.4.3 Checking the Timeout for Stopping the M2000 Application Resources.........................................13-3713.4.4 Checking the Trust Between Two Servers in an HA System..........................................................13-3813.4.5 Checking the Version of the Sun Cluster Software..........................................................................13-3913.4.6 Checking the Global Devices of an HA System..............................................................................13-3913.4.7 Checking the Logical Host of an HA System..................................................................................13-4013.4.8 Checking the Right and Owner of the /opt/SUNWscsyb/bin/sybase_stop_servers File..................13-4013.4.9 Checking the Front Panel of a Disk Array.......................................................................................13-4113.4.10 Querying the M2000 License.........................................................................................................13-41

14 M2000 Emergency Maintenance (HA)................................................................................14-114.1 Guide to Emergency Maintenance of the M2000 Server............................................................................14-214.2 Guide to Emergency Maintenance of the M2000 Client.............................................................................14-214.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure (HA)..........................14-2

14.3.1 Troubleshooting: Failure to Start the Solaris Due to Loss of System Files.......................................14-314.3.2 Troubleshooting: System Switched into the Maintenance Mode and Prompting You to Run fsckManually........................................................................................................................................................14-414.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System (HA).......................................................................................................................................................................14-514.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact (HA)..............14-5

15 Troubleshooting the M2000.................................................................................................15-115.1 Procedure for Troubleshooting the M2000 ................................................................................................15-215.2 Collecting M2000 Site and Software Information......................................................................................15-3

15.2.1 Collecting the M2000 Site Information.............................................................................................15-315.2.2 Collecting the Time of M2000 Fault Occurrence..............................................................................15-415.2.3 Collecting the IP Address of the M2000 Server................................................................................15-415.2.4 Collecting the Solaris Version............................................................................................................15-4



xvii

15.2.5 Collecting Sybase Version Information.............................................................................................15-515.2.6 Obtaining the Version Information About the M2000.......................................................................15-6

15.3 Collecting Fault Data Using the Log Information Collector.......................................................................15-7

16 FAQs (HA, Sun)......................................................................................................................16-116.1 About Solaris (HA, Sun).............................................................................................................................16-2

16.1.1 How Do I Log In to the M2000 Server as User root Through Telnet................................................16-316.1.2 How to Log In the M2000 Server as the root User Through FTP.....................................................16-416.1.3 How to Check the Status of the Tape Drive.......................................................................................16-516.1.4 How Should I Select a Tape Drive.....................................................................................................16-616.1.5 How to View the Hardware Settings of the M2000 Server................................................................16-716.1.6 How to Check the Device Status of the M2000 Server......................................................................16-716.1.7 Why Unable to Enter the Domain Console of Fire E4900...............................................................16-1116.1.8 How to Modify the Port Number of the FTP Server........................................................................16-1216.1.9 How to Query the Time Zone Name................................................................................................16-1216.1.10 How Should I Stop the NTP Service on the M2000 Server (HA).................................................16-1416.1.11 How Do I Change the IP Address of the S3X00 Disk Array (Command Mode)..........................16-1516.1.12 How Should I Change the IP Address of the 6140 Disk Array (Command Mode).......................16-1716.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)...........................16-2216.1.14 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROM..................................16-2416.1.15 How to Handle the corrupt label - wrong magic number Message...........................................16-2516.1.16 What Should I Do When the Server Disk Space Is Insufficient....................................................16-2616.1.17 How to Configuring the Monitoring Function of the S2600 Disk Array.......................................16-2716.1.18 How Should I Configure the Monitoring Function for the S3000 Series Disk Arrays..................16-2916.1.19 How Should I Uninstall the OceanStor Monitoring Software.......................................................16-3316.1.20 How Should I Check the Running Status of the FTP Service on the M2000 Server.....................16-3316.1.21 How Should I Start the FTP Service on the M2000 Server...........................................................16-3416.1.22 How Should I Check the Running Status of the SFTP Service on the M2000 Server...................16-3416.1.23 How Should I Start the SFTP Service on the M2000 Server.........................................................16-3516.1.24 How Do I Log In to the Server in SSH Mode................................................................................16-35

16.2 About Sybase (HA, Sun)...........................................................................................................................16-3716.2.1 How Do I Check Whether the Sybase Is Started..............................................................................16-3816.2.2 How to Start the Sybase (HA, Sun)..................................................................................................16-3816.2.3 How to Stop the Sybase (HA, Sun)..................................................................................................16-3916.2.4 How to View the Name of the Sybase Server..................................................................................16-3916.2.5 How to Handle Database Alarms.....................................................................................................16-3916.2.6 How to View Database Deadlock Information................................................................................16-4016.2.7 Why the Sybase Is Not Started After the Server Restarted..............................................................16-4216.2.8 Why Is the Sybase Not Started After Run svc_profile.sh................................................................16-4316.2.9 Why the Sybase Backup Database Abort.........................................................................................16-4416.2.10 What Should I Do When the Database Cannot Be Started Properly..............................................16-4416.2.11 What Should I Do When the Client Is Disconnected Due to Damaged System Tables in the Database(HA)............................................................................................................................................................16-45


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

Issue 03 (2010-08-31)

16.2.12 What Should I Do When the Number of Database Connections Is Insufficient............................16-4716.2.13 How to Handle the '/export/home/sybdev/master.dat' already in use Message........................16-48

16.3 About Server Software (HA, Sun)............................................................................................................16-4916.3.1 Why M2000 Services Restart Abnormally (HA, Sun).....................................................................16-5016.3.2 Why M2000 Services Stop Abnormally (HA, Sun).........................................................................16-5116.3.3 Why M2000 Services Fail to Start After the Server Restarts (HA, Sun).........................................16-5116.3.4 How Do I Copy the Backup Dynamic Data from a Hard Disk to a Tape (HA, Sun)......................16-5216.3.5 How Do I Copy the Backup Dynamic Data from a Tape to a Hard Disk (HA, Sun)......................16-5316.3.6 How Do I Verify the Dynamic Data Backed Up on a Tape.............................................................16-5416.3.7 How to Set the M2000 Administration Console as the Intermediary-Layer NTP Server (In EncryptionMode)..........................................................................................................................................................16-5516.3.8 How Do I Check the Running Status of the NTP Services on the Administration Console (In EncryptionMode)..........................................................................................................................................................16-5716.3.9 How to Set the M2000 Server as the NTP Client (HA, in Encryption Mode).................................16-5816.3.10 How to Check the Running Status of the NTP Service on the M2000 Server (HA, in Encryption Mode).....................................................................................................................................................................16-6116.3.11 How Should I Handle an Incremental Backup Failure...................................................................16-6116.3.12 How Should I Periodically Monitoring the CPU, Memory, and Disk...........................................16-6216.3.13 How Should I Power On the T5220 Server Through the Serial Port of the SC.............................16-63



xix

Figures

Figure 1-1 Logical architecture of the M2000 HA system...................................................................................1-3Figure 1-2 Software architecture of the HA system.............................................................................................1-4Figure 2-1 Netra 240 server..................................................................................................................................2-3Figure 2-2 3320 disk array...................................................................................................................................2-3Figure 2-3 3320 disk array...................................................................................................................................2-5Figure 2-4 Closing the 3320 disk array................................................................................................................2-6Figure 2-5 Netra 240 server..................................................................................................................................2-7Figure 2-6 6140 disk array...................................................................................................................................2-8Figure 2-7 V890 server.........................................................................................................................................2-9Figure 2-8 Rotary switch at the position Force off............................................................................................ 2-10Figure 2-9 6140 disk array (I)............................................................................................................................ 2-11Figure 2-10 6140 disk array (II).........................................................................................................................2-11Figure 2-11 Netra 240 server..............................................................................................................................2-13Figure 2-12 6140 disk array............................................................................................................................... 2-14Figure 2-13 E4900 server...................................................................................................................................2-15Figure 2-14 6140 disk array (I).......................................................................................................................... 2-17Figure 2-15 6140 disk array (II).........................................................................................................................2-18Figure 2-16 S2600 disk array.............................................................................................................................2-19Figure 2-17 S3200 disk array.............................................................................................................................2-20Figure 2-18 T5220 server...................................................................................................................................2-21Figure 2-19 T5220 server...................................................................................................................................2-22Figure 2-20 Disk array (I).................................................................................................................................. 2-23Figure 2-21 Disk array (II).................................................................................................................................2-23Figure 2-22 S2600 disk array.............................................................................................................................2-25Figure 2-23 S3200 disk array.............................................................................................................................2-25Figure 2-24 SPARC Enterprise M4000/M5000 front operation panel.............................................................. 2-26Figure 2-25 Disk array (I).................................................................................................................................. 2-29Figure 2-26 Disk array (II).................................................................................................................................2-29Figure 4-1 NTP rationale......................................................................................................................................4-4Figure 4-2 NTP layered architecture....................................................................................................................4-5Figure 4-3 Schematic diagram of time synchronization for device A..................................................................4-7Figure 4-4 Directly connecting device A and the NTP server.............................................................................4-9Figure 4-5 Networking of device A and the intermediate-layer NTP server.....................................................4-10

HA System Administrator Guide (Sun, S10) Figures


xxi

Figure 4-6 Directly connecting device A to the highest layer NTP server........................................................ 4-11Figure 4-7 Status of NTP service on node 1......................................................................................................4-24Figure 4-8 Status of NTP service on node 2......................................................................................................4-25Figure 5-1 Serial ports of the S3X00..................................................................................................................5-24Figure 5-2 Checking the port configuration.......................................................................................................5-25Figure 5-3 Port configuration (I)........................................................................................................................5-26Figure 5-4 Port configuration (II).......................................................................................................................5-26Figure 5-5 Port configuration (III).....................................................................................................................5-27Figure 5-6 Port configuration (IV).....................................................................................................................5-27Figure 5-7 Serial ports of the 6140 disk array....................................................................................................5-29Figure 5-8 Serial ports provided by the S2600 disk array..................................................................................5-33Figure 5-9 Successful connection interface........................................................................................................5-34Figure 5-10 Successful login dialog box............................................................................................................5-34Figure 8-1 Server Monitor tab page.....................................................................................................................8-5Figure 8-2 Hard Disk Monitor tab page...............................................................................................................8-6Figure 8-3 Database Monitor tab page.................................................................................................................8-7Figure 8-4 Service Monitor tab page....................................................................................................................8-8Figure 8-5 Process Monitor tab page...................................................................................................................8-9Figure 8-6 System Monitor Settings dialog box................................................................................................8-11Figure 8-7 State transition of a scheduled task...................................................................................................8-39Figure 8-8 Task Management window...............................................................................................................8-54Figure 8-9 M2000 Log Information Collector interface....................................................................................8-55Figure 9-1 Process Monitor tab page.................................................................................................................9-24Figure 9-2 Service Monitor tab page..................................................................................................................9-25Figure 10-1 Database Monitor tab page...........................................................................................................10-19Figure 10-2 Periodic backup............................................................................................................................10-24Figure 10-3 Periodic backup............................................................................................................................10-25Figure 12-1 Setting a storage device (I).............................................................................................................12-6Figure 12-2 Setting a storage device (II)............................................................................................................12-6Figure 12-3 Periodic backup..............................................................................................................................12-8Figure 12-4 Periodic backup..............................................................................................................................12-9Figure 12-5 Manual backup.............................................................................................................................12-10Figure 13-1 Periodic backup............................................................................................................................13-32Figure 13-2 Periodic backup............................................................................................................................13-33Figure 15-1 Log Information Collector dialog box............................................................................................15-8Figure 16-1 SNMP tab page............................................................................................................................16-31Figure 16-2 PuTTY Configuration...................................................................................................................16-36Figure 16-3 PuTTY Security Alert...................................................................................................................16-37

Figures HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)

Tables

Table 3-1 Factory settings of the Sun Cluster......................................................................................................3-3Table 5-1 Adding or deleting a route....................................................................................................................5-2Table 5-2 Correspondence between the previous and new IP addresses..............................................................5-5Table 5-3 Parameters for the standby controller.................................................................................................5-17Table 5-4 Parameters for the standby controller.................................................................................................5-18Table 5-5 Setting properties of the serial port....................................................................................................5-24Table 5-6 Configuration items of the controller port.........................................................................................5-25Table 5-7 Setting properties of the serial port....................................................................................................5-30Table 5-8 Setting the properties of a serial port.................................................................................................5-33Table 6-1 M2000 client software directory..........................................................................................................6-2Table 7-1 Solaris user accounts............................................................................................................................7-3Table 7-2 Privileges of M2000 users....................................................................................................................7-6Table 7-3 Solaris user accounts............................................................................................................................7-9Table 8-1 Server Monitor...................................................................................................................................8-12Table 8-2 Hard Disk Monitor.............................................................................................................................8-14Table 8-3 Database Monitor...............................................................................................................................8-15Table 8-4 Service Monitor..................................................................................................................................8-17Table 8-5 Tasks grouped according to the execution period..............................................................................8-25Table 8-6 Tasks grouped according to the function...........................................................................................8-25Table 8-7 Tasks grouped according to the feature..............................................................................................8-29Table 8-8 Description of system scheduled tasks...............................................................................................8-30Table 8-9 Description of user scheduled tasks...................................................................................................8-32Table 8-10 Description of the task description parameters................................................................................8-38Table 8-11 Allowable operations for different task types..................................................................................8-48Table 8-12 Description of the Task Management window................................................................................8-54Table 8-13 Server Monitor.................................................................................................................................8-58Table 8-14 Hard Disk Monitor...........................................................................................................................8-60Table 8-15 Database Monitor.............................................................................................................................8-61Table 8-16 Service Monitor................................................................................................................................8-63Table 8-17 Parameters of Alarm/Event Log Dump Tasks.................................................................................8-75Table 8-18 Parameters of Performance Data Tasks...........................................................................................8-76Table 8-19 Parameters of NE Log Tasks............................................................................................................8-78Table 8-20 Parameters of NM Log Dump Tasks...............................................................................................8-78

HA System Administrator Guide (Sun, S10) Tables


xxiii

Table 8-21 Description of extended parameters.................................................................................................8-79Table 8-22 Extended parameters of NIC Configuration Data Export tasks...................................................8-82Table 8-23 Extended parameters of Configuration Data Export tasks...........................................................8-82Table 8-24 Descriptions of extended parameters...............................................................................................8-83Table 8-25 Extended parameters........................................................................................................................8-85Table 8-26 Descriptions of extended parameters...............................................................................................8-86Table 8-27 Extended Parameters........................................................................................................................8-89Table 8-28 Predefined macros............................................................................................................................8-94Table 8-29 Description of extended parameters...............................................................................................8-102Table 8-30 Descriptions of parameters for setting timing task time................................................................ 8-105Table 9-1 Relations between northbound interfaces and their corresponding processes and services..............9-22Table 10-1 Names and functions of tables in the cmedb database.....................................................................10-3Table 10-2 Tables of the farsdb database and the corresponding functions.......................................................10-4Table 10-3 Tables of the fmdb database and the corresponding functions........................................................10-4Table 10-4 Tables of the itfndb database and the corresponding functions.......................................................10-5Table 10-5 Names and functions of tables in the omcdb database.....................................................................10-6Table 10-6 Name and function of each table in the omceamdb database..........................................................10-8Table 10-7 Names and functions of the tables in the omclogdb database..........................................................10-9Table 10-8 Tables of the omcsmdb database and the corresponding functions.................................................10-9Table 10-9 Name and function of each table in the omctempdb database.......................................................10-10Table 10-10 Names and functions of the tables in the omctmdb database.......................................................10-10Table 10-11 Counter information tables in the pmcomdb database and the corresponding functions.............10-11Table 10-12 Template information tables in the pmcomdb database and the corresponding functions.......... 10-12Table 10-13 Function subsets and period tables in the pmcomdb database and their functions......................10-13Table 10-14 Template tables in the pmdb database and their functions...........................................................10-14Table 10-15 Function subset tables and period tables in the pmdb database and the corresponding functions...........................................................................................................................................................................10-14Table 10-16 Name and function of each object type information table in the sumdb database.......................10-14Table 10-17 Name and function of each system setting information table in the sumdb database..................10-15Table 10-18 Name and function of each report information table in the sumdb database...............................10-16Table 10-19 Name and function of each performance result table in the sumdb database..............................10-17Table 10-20 Tables of the swmdb database and the corresponding functions.................................................10-18Table 11-1 M2000 client software directory......................................................................................................11-2Table 11-2 Directories for storing the M2000 server software..........................................................................11-6Table 11-3 Planning of the server disk partitions (HA, V890)..........................................................................11-9Table 11-4 Planning for the 6140 disk array......................................................................................................11-9Table 11-5 Planning of the server disk partitions (HA, E4900).......................................................................11-10Table 11-6 Planning for the 6140 disk array....................................................................................................11-10Table 11-7 Disk partition planning of the T5220 server..................................................................................11-11Table 11-8 Planning for the S3100 disk array..................................................................................................11-11Table 11-9 Planning for the S2600 disk array..................................................................................................11-12Table 11-10 Disk partition planning of the M4000/M5000 server.................................................................. 11-12Table 11-11 Planning for the S3200/6140 disk array.......................................................................................11-13

Tables HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)

Table 11-12 Planning for the S2600 disk array................................................................................................11-13Table 12-1 Introduction to dynamic data backup...............................................................................................12-2Table 13-1 List of maintenance items................................................................................................................13-2Table 13-2 Result of the scstat command..........................................................................................................13-6Table 13-3 Alarms that need to be handled immediately.................................................................................13-10Table 13-4 Alarms that need to be handled within one day.............................................................................13-11Table 13-5 Alarms to be focused on during network expansion......................................................................13-11Table 13-6 Alarms about malicious operations................................................................................................13-11Table 13-7 Events that need to be handled immediately..................................................................................13-12Table 13-8 Events that need to be handled within one day..............................................................................13-12Table 13-9 Events that need to be focused on during network expansion.......................................................13-12Table 13-10 Server Monitor.............................................................................................................................13-24Table 13-11 Hard Disk Monitor.......................................................................................................................13-26Table 13-12 Database Monitor.........................................................................................................................13-27Table 13-13 Service Monitor............................................................................................................................13-29Table 16-1 Tape drive status..............................................................................................................................16-5Table 16-2 Checking the server configuration...................................................................................................16-7Table 16-3 Commands for checking the device status.......................................................................................16-8Table 16-4 Example of the matching table between countries and time zone names......................................16-13Table 16-5 Setting the properties of the serial port..........................................................................................16-19

HA System Administrator Guide (Sun, S10) Tables


xxv

1 M2000 High Availability System

About This Chapter

This chapter describes the features, working principles, logical architecture, and softwarearchitecture of the M2000 HA system.

1.1 Features and Working Principles of the HA SystemThis section describes the features and working principles of the HA system.

1.2 Logical Architecture of the HA SystemThis section describes the logical architecture of the HA system.

1.3 Software Architecture of the HA SystemThis section describes the software architecture of the HA system.

HA System Administrator Guide (Sun, S10) 1 M2000 High Availability System


1-1

1.1 Features and Working Principles of the HA SystemThis section describes the features and working principles of the HA system.

Features

CAUTIONThe active and standby nodes stand for the active and standby servers respectively.

In the HA system, the Sun Cluster manages the active and standby nodes to provide a secureand reliable network management system.

The HA system has the following features:

l Reduces the risk of system breakdown caused by software or hardware faults

l Supports online maintenance, during which the ongoing services are not disrupted

The high availability of the HA system is achieved through the combination of software andhardware. Redundant interconnected clusters, memory storage, and public network preventsingle-point failures. The HA system continuously monitors the hardware and software. The HAsystem switches between the active and standby servers or restarts the network managementsystem when a fault occurs.

Working Principles

The M2000 HA system has two connected Sun servers that are managed by the Sun Cluster.One is the active server and the other is the standby server. The system switches to the standbyserver when the active server is faulty.

The Solaris, Cluster, Volume Manager, Sybase, and M2000 applications run on the active server,where the Solaris, Cluster, and Volume Manager also run on the standby server.

NOTE

l The M2000 HA system performs the active/standby server switchover.

l The time required for the active/standby server switchover is equal to the sum of the following time:

l Time for stopping the M2000 on the active server

l Time for stopping the Sybase on the active server

l Time for stopping the disk array and the other resources on the active server

l Time for starting the disk array and the other resources on the standby server

l Time for starting the Sybase on the standby server

l Time for starting the M2000 on the standby server

l The time required for the active/standby server switchover is determined by the sum of the time forstopping the M2000 services and the time for starting the M2000 services.

1 M2000 High Availability System HA System Administrator Guide (Sun, S10)

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

Issue 03 (2010-08-31)

1.2 Logical Architecture of the HA SystemThis section describes the logical architecture of the HA system.

Figure 1-1 shows the logical architecture of the M2000 HA system.

Figure 1-1 Logical architecture of the M2000 HA system

l Active and standby servers: the servers of the M2000 . They operate the M2000 serverapplication and NE mediation software. The two servers are monitored and switched overby the SUN Cluster.

l Disk arrays: protect the data of active and standby servers. They also synchronize the dataon the two servers.

l Cluster console: provides single-point management for the Cluster and the databases. Ithandles faults occurring in the Cluster.

1.3 Software Architecture of the HA SystemThis section describes the software architecture of the HA system.

Figure 1-2 shows the software architecture of the HA system.

The two servers are installed with the same software. The server that provides services is theactive server. The Cluster manages the Sybase, the M2000 server applications, and the disk arrayinstalled on the active server.

NOTE

If you log in using a user account of the operating system, you must perform the same operations on theactive and standby servers. If you log in using a user account of the Sybase or M2000 , you can operateonly on the active server.

HA System Administrator Guide (Sun, S10) 1 M2000 High Availability System


1-3

Figure 1-2 Software architecture of the HA system

The HA system requires a physical IP address and a logical IP address.

l The physical IP address is set on the Ethernet adapter of the server.

l The logical IP address is provided by the HA system to the public. It is dynamically assignedby the HA system.

l The logical IP address is assigned to the active server, which provides services for thepublic.

l The client can access only the logical IP address for maintenance in case of not knowingthe internal implementation of the HA system.

Configure the same IP address for the active and standby servers during the networkconfiguration. For details, refer to chapter 5 Configuring the IP Address of the M2000 Server(HA).

1 M2000 High Availability System HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

2 Powering the M2000 On or Off (HA)

About This Chapter

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

2.1 Powering the M2000 On or Off (HA, Netra 240)This section describes how to power on and power off the M2000 HA system when the Netra240 server is used as the M2000 server.

2.2 Powering the M2000 On or Off (HA, V890)This section describes how to power on and power off the M2000 HA system when the V890server is used as the M2000 server.

2.3 Powering the M2000 On or Off (HA, E4900)This section describes how to power on and power off the M2000 HA system when the E4900server is used as the M2000 server.

2.4 Powering the M2000 On or Off (HA, T5220)This section describes how to power on and power off the M2000 HA system when the T5220server is used as the M2000 server.

2.5 Powering the M2000 On or Off (HA, M4000/M5000)This section describes how to power on and power off the M2000 HA system when the M4000/M5000 server is used as the M2000 server.

HA System Administrator Guide (Sun, S10) 2 Powering the M2000 On or Off (HA)


2-1

2.1 Powering the M2000 On or Off (HA, Netra 240)This section describes how to power on and power off the M2000 HA system when the Netra240 server is used as the M2000 server.

2.1.1 Powering On the M2000 (HA, Netra 240)This section describes how to power on the M2000 HA system when the Netra 240 minicomputeris used as the M2000 server.

2.1.2 Powering Off the M2000 (HA, Netra 240)This section describes how to power off the M2000 HA system when the Netra 240minicomputer is used as the M2000 server.

2.1.1 Powering On the M2000 (HA, Netra 240)This section describes how to power on the M2000 HA system when the Netra 240 minicomputeris used as the M2000 server.

PrerequisiteThe M2000 system is already shut down. For details, see2.1.2 Powering Off the M2000 (HA,Netra 240).

Procedure

Step 1 Make preparations for powering on the M2000.1. Ensure that the power switch of each device in the cabinet are in the OFF state. If any power

switch is ON, set it to OFF.

NOTE

The devices to be checked include the M2000 server, Netra 240 administration console, KVM,networking devices, and cabinet.

2. Set the power switch of the cabinet to ON.

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

2 Powering the M2000 On or Off (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

Figure 2-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 down the On/Standby button on the power switch of the Netra 240 server to start theM2000 system.

l If the Solaris operating system is not installed on the M2000 server, the M2000 systemis 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 two disk arrays 3320.The procedures for powering on two disk arrays are the same.The 3320 disk array is closed, as shown in Figure 2-2.

Figure 2-2 3320 disk array



2-3

Step 4 Power on the two Netra 240 servers.

CAUTIONThe procedures for powering on the two Netra 240 servers are consistent. Power on the osssvr-l first. After three minutes, power on the osssvr-2.

1. Turn the rotary switch beside the power supply to the normal position (I), as shown inFigure 2-1.

2. Press down the On/Standby button on the power switch of the Netra 240 server to start theM2000 system.l If the Solaris operating system is not installed on the M2000 server, the system is

switched to the ok state.

l If the Solaris, Cluster, Sybase, and M2000 server applications are installed on theM2000 server, the system automatically starts the Solaris, Cluster, Sybase, andM2000 applications. If the system is switched to the ok state, enter boot to start theoperating system. After that, the system automatically starts the Cluster, Sybase, andM2000 applications.


----End

2.1.2 Powering Off the M2000 (HA, Netra 240)This section describes how to power off the M2000 HA system when the Netra 240minicomputer is used as the M2000 server.

Procedure

Step 1 Switch the two Netra 240 servers to the ok state.

1. On the administration console, log in to the two nodes as user root through thecorresponding physical IP addresses, and then run the following command, respectively.

# sync; sync; sync; sync; sync; sync

2. On node 1 or node 2, switch the system to the ok state.

# /usr/cluster/bin/scshutdown -y -g0

NOTE

If the Cluster, Sybase, and M2000 applications are installed in the HA system, the systemautomatically terminates the M2000 applications and Sybase.

Step 2 Power off the two Netra 240 servers.The procedures for powering off the two Netra 240 servers are the same.1. Turn the rotary switch to the normal position (I).2. Press down the On/Standby button on the power switch of the server and then release the

button. The system performs a soft switch-off. Wait until the indicator on the front panelis turned off.



Issue 03 (2010-08-31)

CAUTIONIf you press down the On/Standby button and hold for four seconds, the system performsa hard switch-off. The hard switch-off may damage disk drives, thus resulting in data loss.

Step 3 Power off the two disk arrays 3320.The procedures for powering off the two disk arrays are the same.The disk array is shown in Figure 2-3.


1. Check whether the I/O activities of the server and the disk array are stopped.

NOTE

a. Wait for two minutes. Check whether the LEDs of the cache on the rear of the controller go out.If all the LEDs go out, you can infer that all the data is written into the disk and that the cachedoes not hold data.

b. Ensure that all the LEDs of all the disk drives at the front of controller stop blinking.

2. Run the telnet command to log in to the 3320 disk array.

telnet IP address of the 3320 disk array

NOTE

l If an IP address is not assigned to the 3320 disk array, use the DB9-DB9 serial port cable attachedto the 3320 disk array to connect the 3320 disk array and a PC. Log in to the system through theHyperTerminal.

l After restoring the default settings of the HyperTerminal port, set the baud rate to 38400.

l If a password is required, keep the password field blank, and then press Enter.

3. Select Terminal (VT100 Mode), and then press Enter.4. On the main interface, choose system Functions > Shutdown controller, and then press

Enter.The 3320 disk array is closed, as shown in Figure 2-4.



2-5

Figure 2-4 Closing the 3320 disk array

5. Power off the two groups of power supply and fan modules.

Step 4 Power off the Netra 240 administration console.1. Log in to the Netra 240 administration console as user root through SSH mode.2. Close the Netra 240 administration console.


# /usr/sbin/shutdown -y -g0 -i5

Step 5 Shut down the power module of the server and the disk array.

Step 6 If required, set the power switches of the cabinet and the other devices in the cabinet to OFF.

----End

2.2 Powering the M2000 On or Off (HA, V890)This section describes how to power on and power off the M2000 HA system when the V890server is used as the M2000 server.

2.2.1 Powering On the M2000 (HA, V890)This section describes how to power on the M2000 HA system when the V890 minicomputeris used as the M2000 server.

2.2.2 Powering Off the M2000 (HA, V890)This section describes how to power off the M2000 HA system when the V890 minicomputeris used as the M2000 server.

2.2.1 Powering On the M2000 (HA, V890)This section describes how to power on the M2000 HA system when the V890 minicomputeris used as the M2000 server.

PrerequisiteThe M2000 system is already shut down. For details, see2.2.2 Powering Off the M2000 (HA,V890).



Issue 03 (2010-08-31)

Procedure

Step 1 Make preparations for powering on the M2000.1. Ensure that the power switch of each device in the cabinet are in the OFF state. If any power

switch is ON, set it to OFF.

NOTE

The devices to be checked include the M2000 server, disk array, Netra 240 administration console,KVM, networking devices, and cabinet.



Figure 2-5.




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.


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 two disk arrays 6140. The procedures for powering on the two disk arrays are thesame.Set the two power switches on the rear of the 6140 disk array to ON. The disk array is shown inFigure 2-6.



2-7

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


1 Off 2 On

Step 4 Power on the two V890 servers.

CAUTIONThe procedures for powering on the two V890 servers are consistent. Power on the osssvr-l first.After three minutes, power on the osssvr-2.

1. Turn the rotary switch to the normal position (I), as shown in Figure 2-7.



Issue 03 (2010-08-31)

Figure 2-7 V890 server



2. Press down the power switch of the V890 server.

l If the Solaris operating system is not installed on the M2000 server, the system isswitched to the ok state.

l If the Solaris, Cluster, Sybase, and M2000 server applications are installed, the systemautomatically starts them. If the system is switched to the ok state, type boot to startthe operating system. Then the system automatically starts the Cluster, Sybase, andM2000 applications.


----End

2.2.2 Powering Off the M2000 (HA, V890)This section describes how to power off the M2000 HA system when the V890 minicomputeris used as the M2000 server.

ProcedureStep 1 Switch the two V890 servers to the ok state.


# sync; sync; sync; sync; sync; sync2. On node 1 or node 2, switch the system to the ok state.




2-9

NOTE


Step 2 Power off two V890 servers.The procedures for powering off two V890 servers are the same.1. Turn the rotary switch beside the power supply to the normal position (I).2. Press down the power switch of the server and then release the switch. The system performs

soft switch-off. Wait until the indicator on the front panel is turned off.

CAUTIONIf you press down the power switch and hold it for five seconds, the system performs hardswitch-off. Hard switch-off may damage disk drives, thus resulting in data loss.

3. Turn the rotary switch beside the power supply to the position Force off, as shown in Figure2-8.

Figure 2-8 Rotary switch at the position Force off



Step 3 Power off the two disk arrays 6140. The procedures for powering off the two disk arrays are thesame.1. Wait for two minutes. Check whether the LEDs of the cache on the rear of the controller

go out.



Issue 03 (2010-08-31)

If all the LEDs go out, you can infer that all the data is written into the disk and that thecache does not hold data. Figure 2-9 shows the 6140 disk array.

Figure 2-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, as

shown in Figure 2-10.

Figure 2-10 6140 disk array (II)



2-11

3. Set the two power switches at the rear of the controller to OFF.

NOTE

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





----End

2.3 Powering the M2000 On or Off (HA, E4900)This section describes how to power on and power off the M2000 HA system when the E4900server is used as the M2000 server.

2.3.1 Powering On the M2000 (HA, E4900)This section describes how to power on the M2000 when the E4900 minicomputer is used asthe M2000 server.

2.3.2 Powering Off the M2000 (HA, E4900)This section describes how to power off the M2000 HA system with the E4900 servers.

2.3.1 Powering On the M2000 (HA, E4900)This section describes how to power on the M2000 when the E4900 minicomputer is used asthe M2000 server.

PrerequisiteThe M2000 system is already shut down. For details, see2.3.2 Powering Off the M2000 (HA,E4900).

Procedure

Step 1 Prepare for powering on the M2000 HA system.1. Before powering on the M2000, ensure that the power switches of all devices are set to

OFF. If any power switch is ON, set it to OFF.

NOTE

The devices to be checked include the M2000 server, disk array, Netra 240 administration console,KVM, networking devices, and cabinet.



Figure 2-11.



Issue 03 (2010-08-31)




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.


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 2-12.




2-13


1 Off 2 On

Step 4 Power on the E4900 server,namely, the osssvr-1.1. Set the power switches of the E4900 server to ON.

The E4900 server has three power switches, as shown in Figure 2-13. Currently, only twoSCs are powered on. The front indicators of the three power boards remain at steady blue.



Issue 03 (2010-08-31)

Figure 2-13 E4900 server

1 Off 2 On

NOTE

The SC of the E4900 server acts as the console.

2. Run the telnet logical IP address of the SC of the E4900 server command to log in to theSC and choose 0 to enter the Platform shell. Run the following command to enable thefailover function of the SC:

sc> setfailover on

NOTE

If the SC of the E4900 server is not configured yet, configure the SC by referring to M2000 HASystem Software Initialization Installation Guide (Sun,S10).

3. Run the poweron all command to switch on all the boards when all the domains are stillin the Off state.

4. In Platform shell, run the console -d a command to switch to domain A. Run thesetkeyswitch on command to start domain A. This process takes about 20 minutes.



2-15

l If the system is not installed with the Solaris, it enters the ok status on startup.

l If the system is installed with the Solaris, Cluster, Sybase, and M2000 software, thesystem starts them automatically. When the system enters the ok state, type bootto start the Cluster, Sybase, and M2000 .

NOTE

If domain A cannot be accessed because the system is occupied, refer to 16.1.7 Why Unable to Enterthe Domain Console of Fire E4900.

Step 5 Repeat Step 4 to start the other E4900 server, namely, the osssvr-2.

----End

2.3.2 Powering Off the M2000 (HA, E4900)This section describes how to power off the M2000 HA system with the E4900 servers.

Procedure

Step 1 Switch the E4900 HA system to the ok status.


# sync; sync; sync; sync; sync; sync2. On node 1 or node 2, switch the system to the ok state.


NOTE


Step 2 Switch off the two E4900 servers.The procedures for powering off the two E4900 servers are the same.1. Run the telnet Server SC IP command to log in to the SC. Select 0 to enter Platform shell.

NOTE

If the server SC is not configured with an IP address, log in to the SC from HyperTerminal.

Use the Huawei 04042025 serial port cable to connect the server SC and the PC. The DB-25 connectorat one end of the serial port cable is connected to the serial port on the server SC. The DB-9 connectorat the other end of the serial port cable is connected to the COM port on the PC. Restore the attributesof the port on the HyperTerminal to default values. This means that baud rate is set to 9600, data bitto 8, parity check to none, stop bit to 1, and data stream control to none.

2. Run the showkeyswitch command to check which domains are switched on.

osssvr-sc0:SC> showkeyswitch

Domain A keyswitch is: onDomain B keyswitch is: offDomain C keyswitch is: offDomain D keyswitch is: off

3. Run the setkeyswitch -d domainID off command to stop domain A.

osssvr-sc0:SC> setkeyswitch -d a off

Powering boards off ...



Issue 03 (2010-08-31)

NOTE

If some domain is on, run the corresponding command to close the domain.

4. Run the poweroff all command to stop all systems. All the boards in the system (includingthe three power boards) except the two SCs are switched 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 3 Switch 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, you can infer that all the data is written into the disk and that thecache does not hold data. Figure 2-14 shows the 6140 disk array.

Figure 2-14 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, as




2-17

Figure 2-15 6140 disk array (II)


NOTE





Step 5 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

2.4 Powering the M2000 On or Off (HA, T5220)This section describes how to power on and power off the M2000 HA system when the T5220server is used as the M2000 server.

2.4.1 Powering On the M2000 (HA, T5220)This section describes how to power on the M2000 HA system when the M2000 is installed onthe T5220 server.

2.4.2 Powering Off the M2000 (HA, T5220)



Issue 03 (2010-08-31)

This section describes how to power off the M2000 HA system when the M2000 is installed onthe T5220 server.

2.4.1 Powering On the M2000 (HA, T5220)This section describes how to power on the M2000 HA system when the M2000 is installed onthe T5220 server.

Prerequisitel The M2000 is already powered off. For details, see 2.4.2 Powering Off the M2000 (HA,

T5220).l The client PC communicates with the server well.

ProcedureStep 1 Prepare for powering on the server.

1. Before powering on the M2000, ensure that the power switches of all devices are set toOFF. If any power switch is ON, set it to OFF.

NOTE

The devices that need to be checked include the M2000 server, disk array, network devices, andcabinet.


Step 2 Power on two disk arrays. The procedures for powering on the two disk arrays are the same.

Option Description

S2600 disk array Perform Step 2.1.

S3100 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 2-16.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 the

socket, the S2600 disk array is automatically powered on.

Figure 2-16 S2600 disk array



2-19

(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

2-17.



1 OFF 2 ON

Step 3 Power on two T5220 servers.

CAUTIONThe procedures for powering on the two T5220 servers are consistent. Power on the osssvr-lfirst. After three minutes, power on the osssvr-2.You can also power on the T5220 server through the serial port of the SC. For details, see 16.3.13How Should I Power On the T5220 Server Through the Serial Port of the SC.



Issue 03 (2010-08-31)

After set the power switch of the cabinet to ON, waiting for 3 minutes, press the power switchto power on the T5220 server when the LED indicator is lighted, as shown in Figure 2-18.

Figure 2-18 T5220 server

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

l If the Solaris, Cluster, Sybase, and the M2000 software are installed, the system starts themautomatically. If the server is switched to the ok state, enter boot to start the operating system.Then, the system automatically starts the Cluster software. The Sybase and theM2000software are also started at the active node.

----End

2.4.2 Powering Off the M2000 (HA, T5220)This section describes how to power off the M2000 HA system when the M2000 is installed onthe T5220 server.

PrerequisiteLog in to the two nodes as user root through SSH mode by using the corresponding physical IPaddresses.

Procedure

Step 1 Switch two T5220 servers to the ok state.1. Run the following commands at the two nodes.


2. Run the following command at either of the nodes to switch the two nodes to the ok state.


NOTE


Step 2 Power off the two T5220 servers. The procedures for powering off the two T5220 servers areconsistent.

Press the power switch of the T5220 server and then release. The system performs soft switch-off, as shown in Figure 2-19. Wait until the indicator on the front panel turns off.



2-21

CAUTIONIf you hold down the power switch for five seconds, the system performs hard switch-off. Hardswitch-off may damage disk drives and cause data loss.

Figure 2-19 T5220 server

Step 3 Power off two disk arrays. The procedures for powering off the two disk arrays are consistent.

Option Description

S2600 disk array Perform Step 3.1 and Step 3.2.

S3100 disk array or 6140 disk array Perform Step 3.3 and Step 3.4.

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, you caninfer that the read and write operations of the disk array are stopped.

b. Check the cache LED on the controller and determine whether any data on the cache needs to 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, you can infer that all the data iswritten into the disk and that the cache does not hold data. See Figure 2-20.



Issue 03 (2010-08-31)

Figure 2-20 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 2-21.

Figure 2-21 Disk array (II)


NOTE



----End

2.5 Powering the M2000 On or Off (HA, M4000/M5000)This section describes how to power on and power off the M2000 HA system when the M4000/M5000 server is used as the M2000 server.

2.5.1 Powering On the M2000 (HA, M4000/M5000)



2-23

This section describes how to power on the M2000 HA system when the M2000 is installed onthe M4000/M5000 server.

2.5.2 Powering Off the M2000 (HA, M4000/M5000)This section describes how to power off the M2000 HA system when the M2000 is installed onthe M4000/M5000 server.

2.5.1 Powering On the M2000 (HA, M4000/M5000)This section describes how to power on the M2000 HA system when the M2000 is installed onthe M4000/M5000 server.

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

(HA, M4000/M5000).

l The client PC communicates with the server well.

Procedure

Step 1 Prepare for powering on the server.

1. Before powering on the M2000, ensure that the power switches of all devices are set toOFF. If any power switch is ON, set it to OFF.

NOTE

The devices that need to be checked include the M2000 server, disk array, network devices, andcabinet.


Step 2 Power on two disk arrays. The procedures for powering on the two disk arrays are consistent.

Option Description



1. Insert the two plugs at the rear of the disk array into the socket, as shown in Figure 2-22.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.



Issue 03 (2010-08-31)


(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

2-23.



1 OFF 2 ON

Step 3 Power on the M2000 server, namely, the osssvr-1.



2-25

1. Enable the PuTTY on the PC. Use the Telnet command to log in to the XSCF of the server.

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 by using the IP address of the network port 0of the XSCF.

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

l Log in to the XSCF of the M4000/M5000 through the PuTTY. For details, see M2000 HA SystemSoftware Initialization Installation Guide (T5220&M4000&M5000, S10).

l If the XSCF of the M4000/M5000 is not configured yet, configure the XSCF by referring toM2000 HA System Software Initialization Installation Guide (T5220&M4000&M5000, S10).

2. Log in to the XSCF as user adminuser.

Huawei recommends that you use adminuser as the password of the adminuser account.3. Set the key on the front operation panel of the Huawei server to maintenance position, as


Figure 2-24 SPARC Enterprise M4000/M5000 front operation panel

1 Power indicator 2 XSCF state indicator 3 Check indicator

4 Power supply 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:



Issue 03 (2010-08-31)

XSCF> console -d 0

When the system displays the following information, enter y to confirm the information.

Connect to DomainID 0? [y|n] :y

l If the Solaris operating system is not installed on the server, the server switches to theok state.

l If the Solaris, Cluster, Sybase, and the M2000 software are installed, the system startsthem automatically. If the system is switched to the ok state, enter boot to start theCluster, 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.

Step 4 Repeat Step 3 to start the other Huawei server, namely, the osssvr-2.

----End

2.5.2 Powering Off the M2000 (HA, M4000/M5000)This section describes how to power off the M2000 HA system when the M2000 is installed onthe M4000/M5000 server.

Prerequisitel Log in to the two nodes as user root through SSH mode by using the corresponding physical

IP addresses.l The PC correctly communicates with the servers.

Contextl When the M2000 HA system is installed on the M4000/M5000 server, the S3200 disk array,

the 6140 disk array or the S2600 disk array can be configured.l The procedures for shutting down the S3200 disk array or the 6140 disk array are consistent.

This takes the S3200 disk array as an example to describe the procedures.

Procedure

Step 1 Switch two M4000/M5000 servers to the ok state.1. Run the following commands at the two nodes.


2. Run the following command at either of the nodes to switch the two nodes to the ok state.


NOTE


Step 2 Power off two M2000 servers. The procedures for powering off the two M2000 servers areconsistent.1. Enable the PuTTY on the PC. Use the Telnet command to log in to the XSCF of the server.



2-27

NOTE

l Log in to the XSCF of the M4000/M5000 server by using the IP address of the network port 0of the XSCF.


l Log in to the XSCF of the M4000/M5000 through the PuTTY. For details, see M2000 SoftwareInitialization Installation Guide (T5220&M4000&M5000, S10).

l If the IP address of the XSCF is not assigned, use the HyperTerminal to log in from the serialport of the XSCF.

l Use the serial port cable to connect the serial port of the XSCF and the COM port of the PC. Oneend of the cable uses the RJ-45 connector, which is inserted into the serial port of the XSCF. Theother end uses the DB-9 connector, which is inserted into the COM port of the PC. The portproperties of the HyperTerminal must be restored to the default values. This means that you mustset the bit rate to 9600, data digit to 8, parity check to none, stop bit to 1, and data stream controlto none.

2. Type the adminuser account and the password to enter the Platform shell.

Huawei recommends that you use adminuser as the password of the adminuser account.3. Run the following command to close domain 0. Then, only the XSCF board is running. All

other boards are powered off.

XSCF> poweroff -d 0

Step 3 Power off two disk arrays. The procedures for powering off the two disk arrays are consistent.

Option Description



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, you caninfer that the read and write operations of the disk array are stopped.

b. Check the cache LED on the controller and determine whether any data on the cache needs to 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, you can infer that all the data iswritten into the disk and that the cache does not hold data. See Figure 2-25.



Issue 03 (2010-08-31)

Figure 2-25 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 2-26.

Figure 2-26 Disk array (II)


NOTE



----End



2-29

3 Managing Cluster Resources of the M2000(HA)

About This Chapter

This chapter describes how to manage the cluster resources of the M2000 HA system.

3.1 Introduction to Cluster Resources of the M2000 (HA)This section describes the cluster resources of the M2000 HA system. The resources consist ofworking principles of the Sun Cluster, resource planning of the M2000 HA system, andautomatic switching of active and standby nodes.

3.2 Switching Over Active and Standby NodesThis lists the conditions for switching over active and standby nodes and describes how to switchover the active and standby nodes.

3.3 Registering the resource of the SybaseAfter the Sybase is registered in the Sun Cluster, the Sun Cluster can monitor the operating statusof the Sybase in real time. when the Sybase is registered, modify the file /opt/SUNWscsyb/bin/sybase_stop_servers on both Node1 and Node2. When the Sybase is registered on the SunCluster, the file is required to be modified only on Node1.

3.4 Registering the resource of the M2000After the M2000 server application is registered on the Cluster, the M2000 server application ismanaged by the Cluster as the resource. The operation is executed only on Node1.

3.5 Managing Cluster ResourcesThis section describes how to manage the cluster resource of the M2000 HA system. The processfor managing the cluster resource involves starting and stopping the Cluster monitoringresources, the M2000 system service, and the Sybase.

HA System Administrator Guide (Sun, S10) 3 Managing Cluster Resources of the M2000 (HA)


3-1

3.1 Introduction to Cluster Resources of the M2000 (HA)This section describes the cluster resources of the M2000 HA system. The resources consist ofworking principles of the Sun Cluster, resource planning of the M2000 HA system, andautomatic switching of active and standby nodes.

3.1.1 Work Principle of the Sun ClusterThis section describes the working principle of the Sun Cluster and defines the switchmechanism, resource group, and resource. For details, refer to the user manual of the Sun Cluster.

3.1.2 Resource Planning for the M2000 (HA)This section describes the resource planning for the M2000 HA system. The resources consistof the Cluster, resource group, and detailed resource planning.

3.1.3 Automatic Switchover Conditions of Active and Standby NodesThis section describes the resource monitoring mechanism, principle of switching active orstandby nodes, and automatic switching conditions for the M2000 HA system.

3.1.1 Work Principle of the Sun ClusterThis section describes the working principle of the Sun Cluster and defines the switchmechanism, resource group, and resource. For details, refer to the user manual of the Sun Cluster.

Introduction to the Sun Cluster

The Sun Cluster promotes the Solaris operating environment to a cluster operating system. Asa collection of loose coupling computing nodes, the cluster provides a single customer view fornetwork services or applications such as database, web service, and file service. The clustersupports the applications with high availability and flexibility.

Switching Mechanism

The cluster can automatically relocate the applications from a faulty active node to a specifiedstandby node, and thus the Sun Cluster features high availability.

If the active node, that is, the node running services, is faulty, the Cluster restarts the serviceson the same node. If the restart fails, the service is switched to the other node automatically.There may be a temporary interruption during the switchover and you may need to reconnectthe two nodes after the switchover. The physical server that provides the applications and data,however, is visible.

Resource

Resource is the instance of the resource type defined in the cluster range. The same resourcetype may contain many resources and each resource has a name and an attribute group. In thiscase, instances of the basic applications can run on the cluster.

Resource Group

A resource group is a group of resources that are associated with each other. These resourcesdepend on each other.

3 Managing Cluster Resources of the M2000 (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

3.1.2 Resource Planning for the M2000 (HA)This section describes the resource planning for the M2000 HA system. The resources consistof the Cluster, resource group, and detailed resource planning.

Table 3-1 lists the factory settings of the Sun Cluster in the M2000 HA system.

Table 3-1 Factory settings of the Sun Cluster

Item Name Description

Cluster osscluster The Cluster name is unique inthe entire network.

Resource group oss_rg Refer to the resource group ofthe system.

Resource osssvr_rs Refers to the name of the hostresource.

ossdg_rs Refer to the resource name ofthe disk array.

sybase_rs Refer to the resource name ofthe Sybase.

ossapp_rs Refer to the applicationresource name of theM2000 .

The relations among the resources ossapp_rs, sybase_rs, ossdg_rs and osssvr_rs are as follows:

l The ossapp_rs resource depends on the sybase_rs resource.

l The sybase_rs resource depends on the ossdg_rs resource and osssvr_rs resource.

3.1.3 Automatic Switchover Conditions of Active and StandbyNodes

This section describes the resource monitoring mechanism, principle of switching active orstandby nodes, and automatic switching conditions for the M2000 HA system.

M2000 Resource Monitoring Mechanism and Switchover PrincipleThe monitoring function of the M2000 monitors the M2000 janitor processes through themonitoring mechanism, and thus ensures the system security. When the system is faulty, thesystem can detect the fault and restart the application services quickly.

The monitoring script monitors the imapsysd and imapwatchdog of the M2000 . The two janitorprocesses monitor other M2000 service progresses. In addition, the two janitor processes areresponsible for automatic restart when the system is faulty.

The Cluster of the HA system runs the monitoring script at intervals. The interval is the attributevalue of Thorough_probe_interval of the M2000 resource ossapp_rs. The interval is set to



3-3

60 by default. If the script output is correct, the monitoring continues. If the script output isincorrect, the system invokes the script stop_OMC.sh and stops the M2000 services. Themonitoring pauses during the period of stopping the service. When the services are stopped, thesystem invokes the script start_OMC.sh to start the M2000 services and counts the time at thatpoint. After the interval of Thorough_probe_interval, the system starts the next monitoringservice.

If the services imapsysd and imapwatchdog are restarted successfully, the Cluster regards theM2000 as normal and thus continues the monitoring.

If the services fail to restart, the system tries to restart the services for the times as given byRetry_count of ossapp_rs. The default value is 2. After the retry completes, the system countsthe time from the restart time point and begins the next monitoring after the intervalThorough_probe_interval. If the output of monitoring script is still incorrect, the system startsthe switchover and switches the resource from the active node to the standby node.

M2000 Switching ConditionsThe Cluster switches the Sybase, M2000 server application, and disk array resources to the otherserver in the following cases:l CPU faults

l Memory faults

l Disk access faults

l Main board faults

l Disconnection between the host Ethernet adapter and the LAN switch

l Operating system faults

l Database faults

3.2 Switching Over Active and Standby NodesThis lists the conditions for switching over active and standby nodes and describes how to switchover the active and standby nodes.

3.2.1 Automatic Switchover Conditions of Active and Standby NodesThis section describes the resource monitoring mechanism, principle of switching active orstandby nodes, and automatic switching conditions for the M2000 HA system.

3.2.2 Manually Switching Over Active and Standby Nodes (HA)This section describes how to switch over active and standby nodes.

3.2.1 Automatic Switchover Conditions of Active and StandbyNodes

This section describes the resource monitoring mechanism, principle of switching active orstandby nodes, and automatic switching conditions for the M2000 HA system.



Issue 03 (2010-08-31)

M2000 Resource Monitoring Mechanism and Switchover PrincipleThe monitoring function of the M2000 monitors the M2000 janitor processes through themonitoring mechanism, and thus ensures the system security. When the system is faulty, thesystem can detect the fault and restart the application services quickly.

The monitoring script monitors the imapsysd and imapwatchdog of the M2000 . The two janitorprocesses monitor other M2000 service progresses. In addition, the two janitor processes areresponsible for automatic restart when the system is faulty.

The Cluster of the HA system runs the monitoring script at intervals. The interval is the attributevalue of Thorough_probe_interval of the M2000 resource ossapp_rs. The interval is set to60 by default. If the script output is correct, the monitoring continues. If the script output isincorrect, the system invokes the script stop_OMC.sh and stops the M2000 services. Themonitoring pauses during the period of stopping the service. When the services are stopped, thesystem invokes the script start_OMC.sh to start the M2000 services and counts the time at thatpoint. After the interval of Thorough_probe_interval, the system starts the next monitoringservice.

If the services imapsysd and imapwatchdog are restarted successfully, the Cluster regards theM2000 as normal and thus continues the monitoring.

If the services fail to restart, the system tries to restart the services for the times as given byRetry_count of ossapp_rs. The default value is 2. After the retry completes, the system countsthe time from the restart time point and begins the next monitoring after the intervalThorough_probe_interval. If the output of monitoring script is still incorrect, the system startsthe switchover and switches the resource from the active node to the standby node.

M2000 Switching ConditionsThe Cluster switches the Sybase, M2000 server application, and disk array resources to the otherserver in the following cases:l CPU faults

l Memory faults

l Disk access faults

l Main board faults

l Disconnection between the host Ethernet adapter and the LAN switch

l Operating system faults

l Database faults

3.2.2 Manually Switching Over Active and Standby Nodes (HA)This section describes how to switch over active and standby nodes.

ContextTake the switchover from osssvr-1 to osssvr-2 as an example to describe the procedures formanual switchover.

Procedure

Step 1 Run the scstat command to check whether the system status is normal.



3-5

The online state means that the resource group is activated on the server.

# scstat

------------------------------------------------------------------

-- Cluster Nodes --

Node name Status --------- ------ Cluster node: osssvr-1 Online Cluster node: osssvr-2 Online

------------------------------------------------------------------

-- Cluster Transport Paths --

Endpoint Endpoint Status -------- -------- ------ Transport path: osssvr-1:ce3 osssvr-2:ce3 Path online Transport path: osssvr-1:ce1 osssvr-2:ce1 Path online

------------------------------------------------------------------

-- Quorum Summary --

Quorum votes possible: 3 Quorum votes needed: 2 Quorum votes present: 3

-- Quorum Votes by Node --

Node Name Present Possible Status --------- ------- -------- ------ Node votes: osssvr-1 1 1 Online Node votes: osssvr-2 1 1 Online

-- Quorum Votes by Device --

Device Name Present Possible Status ----------- ------- -------- ------ Device votes: /dev/did/rdsk/d4s2 1 1 Online

------------------------------------------------------------------

-- Device Group Servers --

Device Group Primary Secondary ------------ ------- --------- Device group servers: ossdg osssvr-1 osssvr-2

-- Device Group Status --

Device Group Status ------------ ------ Device group status: ossdg Online

-- Multi-owner Device Groups --

Device Group Online Status ------------ -------------

------------------------------------------------------------------

-- Resource Groups and Resources --



Issue 03 (2010-08-31)

Group Name Resources ---------- --------- Resources: oss_rg osssvr_rs ossdg_rs sybase_rs ossapp_rs

-- Resource Groups --

Group Name Node Name State ---------- --------- ----- Group: oss_rg osssvr-1 Online Group: oss_rg osssvr-2 Offline

-- Resources --

Resource Name Node Name State Status Message ------------- --------- ----- -------------- Resource: osssvr_rs osssvr-1 Online Online - LogicalHostname online. Resource: osssvr_rs osssvr-2 Offline Offline - LogicalHostname offline.

Resource: ossdg_rs osssvr-1 Online Online Resource: ossdg_rs osssvr-2 Offline Offline

Resource: sybase_rs osssvr-1 Online Online Resource: sybase_rs osssvr-2 Offline Offline - Adaptive_server: STOPPED backup_server: STOPPED

Resource: ossapp_rs osssvr-1 Online Online Resource: ossapp_rs osssvr-2 Offline Offline

Step 2 Log in as user root to perform the switchover on the active or standby node.

# scswitch -z -g oss_rg -h host name of Node2

Step 3 Check whether the switchover is successful.

# scstat

----End

3.3 Registering the resource of the SybaseAfter the Sybase is registered in the Sun Cluster, the Sun Cluster can monitor the operating statusof the Sybase in real time. when the Sybase is registered, modify the file /opt/SUNWscsyb/bin/sybase_stop_servers on both Node1 and Node2. When the Sybase is registered on the SunCluster, the file is required to be modified only on Node1.

3.3.1 Installing the Sybase Agent (HA)This section describes how to install the Sybase Agent on both node 1 and node 2.

3.3.2 Modifying the File sybase_stop_servers in the Folder /opt/SUNWscsyb/binThis task is performed to add user information about sa in the file /opt/SUNWscsyb/bin/sybase_stop_servers. The task ensures that the Cluster passes verification when the Clusterstarts the Sybase. You need to perform this operation on both Node1 and Node2.

3.3.3 Modifying the File sybase_start in the Folder /opt/SUNWscsyb/binThis section describes how to modify the startup waiting time of the Sybase in the /opt/SUNWscsyb/bin/sybase_start file. This ensures that the Sybase database has enough time forstartup and guarantees the correctness of sequent operations. Perform this operation on Node1and Node2.



3-7

3.3.4 Registering the Sybase to the Sun ClusterThis section describes how to register the Sybase system type and resource on the Sun Clusterthrough the regcluster.sh scripts after the M2000 server software is installed. When the activenode has faults, the Sybase resource is automatically switched over to the standby node. Performthe task only on the active node.

3.3.5 Checking the Register of the Sybase ResourceThis section describes how to check whether the Sybase resource has been successfullyregistered on the Sun Cluster. Perform this task only on Node1.

3.3.6 Activating sybase_rsAfter the Sybase is registered and activated in the Cluster, the Cluster can monitor and managethe Sybase. This operation is performed only on Node1.

3.3.1 Installing the Sybase Agent (HA)This section describes how to install the Sybase Agent on both node 1 and node 2.

Prerequisitel Log in to node 1 and node 2 as user root through SSH mode.

l The M2000 server software has been correctly installed on Node1 and Node2.

Procedure

Step 1 Type the path of the Sybase Agent installation package.l To install the Sybase Agent installation package on node 1, run the following command:

# cd /opt/OMC/etc/duall To install the Sybase Agent installation package on node 2, transfer the registration

package /opt/OMC/etc/dual/SUNWscsyb.tar.gz in bin mode from node 1 to the path /tmp on node 2 through the FTP.Run the command ftp IP address of node 1 on node 2 and log in to node 1 as user root. Runthe following commands:ftp> lcd /tmpftp> cd /opt/OMC/etc/dualftp> bin

ftp> get SUNWscsyb.tar.gz

ftp> bye

After the files are transferred, run the following command to navigate to the installationdirectory of node 2:# cd /tmp

Step 2 Extract the package SUNWscsyb.tar.gz on node 1 and node 2.

# gunzip SUNWscsyb.tar.gz

# tar xvf SUNWscsyb.tar

# pkgadd -d .

Step 3 At the following prompt, press Enter.



Issue 03 (2010-08-31)

The following packages are available: 1 SUNWscsyb Sun Cluster HA Sybase data service (sparc) 3.1.0,REV=2005.07.18.10.43

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]:

Step 4 At the following prompt, press Enter:Do you want to continue with the installation of <SUNWscsyb> [y,n,?]

The system prompts the following information after the installation of Sybase Agent.

Installation of <SUNWscsyb> was successful.

----End

3.3.2 Modifying the File sybase_stop_servers in the Folder /opt/SUNWscsyb/bin

This task is performed to add user information about sa in the file /opt/SUNWscsyb/bin/sybase_stop_servers. The task ensures that the Cluster passes verification when the Clusterstarts the Sybase. You need to perform this operation on both Node1 and Node2.

PrerequisiteLog in to Node1 and Node2 as root through SSH mode.

Procedure

Step 1 Open /opt/SUNWscsyb/bin/sybase_stop_servers and run the following commands:

# cd /opt/SUNWscsyb/bin

# TERM=vt100; export TERM

# vi sybase_stop_servers

Step 2 Find the following contents in two different places in the file.${SYBASE}/${SYBASE_OCS}/bin/isql -Usa -S${ADAPTIVE_SERVER_NAME}<<SVR_EOF

Step 3 Add the password of the sa user into the contents mentioned previously in the two differentplaces.

The modified contents is shown as follows:

${SYBASE}/${SYBASE_OCS}/bin/isql -Usa -S${ADAPTIVE_SERVER_NAME} -Pemsems<<SVR_EOF

NOTE

The file sybase_stop_servers is read-only. To modify it, run wq! to write this file effectively, and thenexit.

Step 4 Modify the file right of sybase_stop_servers.

# chmod 500 sybase_stop_servers

# chown dbuser:staff sybase_stop_servers

----End



3-9

3.3.3 Modifying the File sybase_start in the Folder /opt/SUNWscsyb/bin

This section describes how to modify the startup waiting time of the Sybase in the /opt/SUNWscsyb/bin/sybase_start file. This ensures that the Sybase database has enough time forstartup and guarantees the correctness of sequent operations. Perform this operation on Node1and Node2.

PrerequisiteLog in to Node1 and Node2 as user root through SSH mode.

Procedure

Step 1 Open the /opt/SUNWscsyb/bin/sybase_start file.

# cd /opt/SUNWscsyb/bin


# vi sybase_start

Step 2 Search the following line in the file and change 30 in this line to 120.let ase_sleep_time=30

Step 3 Run the : wq! to forcibly exit.

----End

3.3.4 Registering the Sybase to the Sun ClusterThis section describes how to register the Sybase system type and resource on the Sun Clusterthrough the regcluster.sh scripts after the M2000 server software is installed. When the activenode has faults, the Sybase resource is automatically switched over to the standby node. Performthe task only on the active node.

Prerequisitel Log in to the active node as user root through SSH mode.


l The Sybase service has been started.

Procedure

Step 1 Run the following commands to add the operation right to reg_syb.sh.

# cd /opt/OMC/etc/dual

# chmod 544 reg_syb.sh

Step 2 Run the registration script reg_syb.sh.

# . /opt/OMC/svc_profile.sh

# ./reg_syb.sh SYB sa password of user sa



Issue 03 (2010-08-31)

Step 3 When the system displays the following prompt, type the name of the resource according to3.1.2 Resource Planning for the M2000 (HA).

Please input Resource Group name [default:oss_rg]:

Please input Disk Group Resource name [default:ossdg_rs]:

Please input Sybase Resource name [default:sybase_rs]:

NOTE

In case a failure occurs, you can directly run the following command and enter information as prompted:

# ./reg_syb.sh

Step 4 When the system displays the following prompt, enter y to continue.Are you sure to continue? [y/n]:

----End

3.3.5 Checking the Register of the Sybase ResourceThis section describes how to check whether the Sybase resource has been successfullyregistered on the Sun Cluster. Perform this task only on Node1.

PrerequisiteLog in to Node1 as user root through SSH mode.

Procedure

Step 1 Run the following command to check the status of the resource.

# scstat -g-- Resource Groups and Resources --

Group Name Resources ---------- --------- Resources: oss_rg osssvr_rs ossdg_rs sybase_rs



-- Resources --

Resource Name Node Name State Status Message ------------- --------- ----- -------------- Resource: osssvr_rs osssvr-1 Online Online - LogicalHostname online. Resource: osssvr_rs osssvr-2 Offline Offline


Resource: sybase_rs osssvr-1 Offline Offline Resource: sybase_rs osssvr-2 Offline Offline



3-11

If the system output contains sybase_rs, you can infer that the registration is successful.

----End

3.3.6 Activating sybase_rsAfter the Sybase is registered and activated in the Cluster, the Cluster can monitor and managethe Sybase. This operation is performed only on Node1.

Prerequisitel Log in to Node1 as root through SSH mode.

l Stop the Sybase service.

Procedure

Step 1 Run the following command to start the monitoring of the Sybase by the Sun Cluster.

# scswitch -e -j sybase_rs

The Cluster starts the Sybase.

Step 2 Run the following command. The Sybase starts.

# scstat -g


Group Name Resources ---------- --------- Resources: oss_rg osssvr_rs ossdg_rs sybase_rs



-- Resources --



Resource: sybase_rs osssvr-1 Online Online Resource: sybase_rs osssvr-2 Offline Offline

In this case, the Cluster ensures that the Sybase starts, and that the Sybase can be switched tothe entire M2000 resource group. In the output, if the State of sybase_rs is Online onNode1(osssvr-1), infer that Sybase is running.

If you do not want the Cluster to monitor the Sybase, run the scswitch -n -j sybase_rs commandto stop the monitoring. The Sybase service is also stopped.

# scswitch -n -j sybase_rs



Issue 03 (2010-08-31)

CAUTIONIn Cluster-managed HA mode, sybase_rs is monitored by the Cluster. Do not stop the Sybaseserver using isql.

----End

3.4 Registering the resource of the M2000After the M2000 server application is registered on the Cluster, the M2000 server application ismanaged by the Cluster as the resource. The operation is executed only on Node1.

3.4.1 Installing the M2000 Registration PackageThis section describes how to install the M2000 registration package on node 1 and node 2.

3.4.2 Registering the M2000 Server Application to the Sun Cluster(Netra240&V890&E4900)This section describes how to register the server software on the Sun Cluster after the M2000server software is installed. When the active node has faults, the M2000 resource is automaticallyswitched over to the standby node. Perform the operation only on Node1.

3.4.3 Registering the M2000 Server Application to the Sun Cluster (T5220&M4000&M5000)This section describes how to register the server software on the Sun Cluster after the M2000server software is installed. When the active node has faults, the M2000 resource is automaticallyswitched over to the standby node. Perform the operation only on Node1.

3.4.4 Checking the Register of the M2000 Server ApplicationThis section describes how to check that the M2000 server software has been successfullyregistered on the Sun Cluster. Perform this task only on Node1.

3.4.5 Activating M2000 ResourcesThis section describes how to activate the M2000 resources. After registering these resourceson the Cluster, activate them so that the Cluster can monitor and manage them. You need toperform this operation on only Node 1.

3.4.1 Installing the M2000 Registration PackageThis section describes how to install the M2000 registration package on node 1 and node 2.

Prerequisitel Log in to node 1 and node 2 as user root through SSH mode.


Procedure

Step 1 Type the path of the M2000 registration package.l To install the M2000 registration package on node 1, run the following command:

# cd /opt/OMC/etc/dual# cp M2kPkg.tar /tmp# cd /tmp



3-13

l To install the M2000 registration package on node 2, transfer the registration package /opt/OMC/etc/dual/M2kPkg.tar in bin mode from node 1 to the path /tmp on node 2 throughthe FTP.Run the command ftp IP address of node 1 on node 2 and log in to node 1 as user root. Runthe following commands:ftp> lcd /tmpftp> cd /opt/OMC/etc/dualftp> binftp> get M2kPkg.tarftp> byeAfter the files are transferred, run the following command to go to the installation directoryof node 2.# cd /tmp

Step 2 Extract the package M2kPkg.tar on node 1 and node 2.

# tar xvf M2kPkg.tar

# cd ./M2kPkg/HWM2000/pkg

# pkgadd -d .

At the following prompt: Select package(s) you wish to process (or 'all'to process all packages). (default: all) [?,??,q]: during theextraction, type all, and then press Enter to continue.

At the following prompt: Do you want to continue with the installationof <HWM2000> [y,n,?] during the extraction, type y, and then press Enter to continue.

When the system prompts # , you can infer that the extraction is completed

----End

3.4.2 Registering the M2000 Server Application to the Sun Cluster(Netra240&V890&E4900)

This section describes how to register the server software on the Sun Cluster after the M2000server software is installed. When the active node has faults, the M2000 resource is automaticallyswitched over to the standby node. Perform the operation only on Node1.

Prerequisitel Log in to Node1 as user root through SSH mode.

l The M2000 registration package has been installed.

Procedure

Step 1 Run the following command to register the M2000 server software.

# scrgadm -a -t HW.M2000

# scrgadm -a -j ossapp_rs -g oss_rg -t HW.M2000 -y Scalable=false -yResource_dependencies=sybase_rs



Issue 03 (2010-08-31)

If no information or the following information is displayed, you can infer that the registrationis successful.

osssvr-1 - Current setting of Retry_interval = 300, might prevent failover on repeated probe failures.It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count].Current values are (Thorough_probe_interval = 60,Retry_count = 2,Probe_timeout = 30).osssvr-2 - Current setting of Retry_interval = 300, might prevent failover on repeated probe failures.It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count].Current values are (Thorough_probe_interval = 60,Retry_count = 2,Probe_timeout = 30).

----End

3.4.3 Registering the M2000 Server Application to the Sun Cluster(T5220&M4000&M5000)

This section describes how to register the server software on the Sun Cluster after the M2000server software is installed. When the active node has faults, the M2000 resource is automaticallyswitched over to the standby node. Perform the operation only on Node1.

Prerequisitel You have logged in to Node1 as user root through SSH mode.

l The M2000 registration package has been installed.

Procedure

Step 1 Run the following command to register the M2000 server software.

# scrgadm -a -t HW.M2000

# scrgadm -a -j ossapp_rs -g oss_rg -t HW.M2000 -y Scalable=false -yResource_dependencies_offline_restart=sybase_rs

If no information or the following information is displayed, then the registration is successful.

osssvr-1 - Current setting of Retry_interval = 300, might prevent failover on repeated probe failures.It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count].Current values are (Thorough_probe_interval = 60,Retry_count = 2,Probe_timeout = 30).osssvr-2 - Current setting of Retry_interval = 300, might prevent failover on repeated probe failures.It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count].Current values are (Thorough_probe_interval = 60,Retry_count = 2,Probe_timeout = 30).

----End

3.4.4 Checking the Register of the M2000 Server ApplicationThis section describes how to check that the M2000 server software has been successfullyregistered on the Sun Cluster. Perform this task only on Node1.

PrerequisiteLog in to Node1 as user root through SSH mode.



3-15

ProcedureStep 1 Run the following command to check the status of the resource.

# scstat -g-- Resource Groups and Resources --




-- Resources --




Resource: ossapp_rs osssvr-1 Offline Offline Resource: ossapp_rs osssvr-2 Offline Offline

If the system output contains ossapp_rs, you can infer that the registration is successful.

----End

3.4.5 Activating M2000 ResourcesThis section describes how to activate the M2000 resources. After registering these resourceson the Cluster, activate them so that the Cluster can monitor and manage them. You need toperform this operation on only Node 1.

Prerequisitel Log in to Node1 as user root through SSH mode.

l The sybase_rs resource has been activated.

ProcedureStep 1 Run the following commands to check all the M2000 services.

# cd /opt/OMC

# . ./svc_profile.sh

# svc_ps

If some services are running, run the following commands to stop all the M2000 services.



Issue 03 (2010-08-31)

# stop_svc

Step 2 Run the following commands to start the monitoring of the M2000 services by the Cluster.

# scswitch -e -j ossapp_rs

The Cluster starts the M2000 services.

Step 3 Check whether the M2000 services are started.1. Run the following command to check whether the M2000 services are started.

# scstat -g





-- Resources --




Resource: ossapp_rs osssvr-1 Online Online Resource: ossapp_rs osssvr-2 Offline Offline

The Cluster monitors the operating status of the M2000 in real time. In the outputinformation, if the State of ossapp_rs on Node 1 is Online, you can infer that theM2000 services are started.

During the startup of the M2000 services, you can run the following command on the Node1 to view the startup logs of the M2000 services.

# tail -f /opt/OMC/startsvc.log

When the output information is similar to the following message, you can infer that theM2000 services are started.

============================ Finished Starting System.

Starting resource monitor on osssvr-2Starting resource monitor on osssvr-2 OKFri Aug 1 08:41:47 GMT 2008

If you do not need the Cluster to monitor the M2000 server, run the following commandto stop the monitoring. The M2000 services, however, are also stopped.



3-17

# scswitch -n -j ossapp_rs

CAUTIONl In Cluster-managed HA mode, do not run the stop_svc command to stop the M2000

server except that the ossapp_rs resources are not monitored by the Cluster.l After registering the Sybase software and the M2000 resources on the Cluster, you must

run the following commands to stop the M2000 and Sybase monitoring before stoppingthe server.# scswitch -n -j ossapp_rs# scswitch -n -j sybase_rs# scshutdown -g0 -y

2. Run the following command to check the operating status of the M2000 services. Ensurethat all the M2000 services are started.

# svc_adm -cmd status

In the output information, if the value of Not Running : is 0, you can infer that allthe M2000 services are started. Otherwise, perform Step 1 through Step 3 to activate theM2000 resources again.

----End

3.5 Managing Cluster ResourcesThis section describes how to manage the cluster resource of the M2000 HA system. The processfor managing the cluster resource involves starting and stopping the Cluster monitoringresources, the M2000 system service, and the Sybase.

3.5.1 Viewing Configured ResourcesThis section describes how to view the configured resources.

3.5.2 Starting Cluster Monitoring on ResourcesThis section describes how to start Cluster monitoring on resources.

3.5.3 Stopping Cluster Monitoring on ResourcesThis section describes how to stop Cluster monitoring on resources.

3.5.4 Starting the M2000 Services (HA)This section describes how to start the M2000 system services. After you run the command, allthe M2000 services are started. The system ignores the service that is already started and startsonly the inactive services.

3.5.5 Stopping M2000 Services (HA)This section describes how to run the command scswitch to stop all the M2000 services. Afterall the M2000 services are stopped, NE performance data and alarm data cannot be processed.After the M2000 services are resumed, the M2000 updates data with the NEs and processes theupdated data.

3.5.6 Starting the Sybase (HA)This section describes how to start the Sybase for the HA system.



Issue 03 (2010-08-31)

3.5.7 Stopping the Sybase (HA)This section describes how to stop the Sybase in the HA system.

3.5.1 Viewing Configured ResourcesThis section describes how to view the configured resources.

PrerequisiteLog in to the server as user root through SSH mode.

ProcedureStep 1 Run the scstat -g command to view the resources in the oss_rg resource group.

# scstat -g

The oss_rg resource group contains osssvr_rs, ossdg_rs, sybase_rs, and ossapp_rs.

----End

3.5.2 Starting Cluster Monitoring on ResourcesThis section describes how to start Cluster monitoring on resources.


ProcedureStep 1 If a resource is not monitored by the Cluster, run the following command to start the Cluster

monitoring on the resource.

# scswitch -e -j resource name

Run the following command to enable the Cluster monitoring on the Sybase:


Run the following command to enable the Cluster monitoring on the M2000:


NOTE

After running the scswitch -e -j command, you can enable the monitoring of a resource and start theresource. For example, after you run the scswitch -e -j ossapp_rs command to enable the monitoring ofM2000 resources, the cluster also starts the M2000 system service.

----End

3.5.3 Stopping Cluster Monitoring on ResourcesThis section describes how to stop Cluster monitoring on resources.




3-19

ContextThe Cluster monitors all the resources in the resource group. If a resource is faulty, the Clusterattempts to restart the resource. The Cluster switches oss_rg to the standby node if the numberof restart attempts reaches the preset value.

Procedure

Step 1 Stop Cluster monitoring on the resources.

# scswitch -n -j resource name

Run the following command to stop Cluster monitoring on the Sybase:


Run the following command to stop Cluster monitoring on the M2000:


NOTE

l The scswitch -n -j command helps you stop a resource. For example, after you run the scswitch -n -j sybase_rs command, the Sybase is stopped.

l The stopped resource cannot restart automatically after the server restarts. In this situation, you muststart the resource manually.

----End



l The Sybase services are running properly. For details about how to start the Sybase services,see 16.2.2 How to Start the Sybase (HA, Sun).

ContextNOTE

The time required for starting M2000 system services is related to the actual environment. Generally, ittakes about 20 minutes.

Procedurel 1. Run the following command:




Issue 03 (2010-08-31)

NOTE

l In the HA system, starting services requires some time. Wait about 10 minutes until allservices are started and then you can perform operations on the HA system.

l When you start M2000 system services, the status of each service is displayed. If the statusof a service is failed, you can infer that the service fails to be started. In this case, you canlocate the fault by viewing the iMAP.troubleshooting.trace log on the active node.

# more /export/home/omc/var/logs/iMAP.troubleshooting.trace

----End


PrerequisiteLog in to the M2000 as user root through SSH mode.

ContextNOTE

The time required for stopping M2000 system services is related to the actual environment. Generally, ittakes about 20 minutes.

Procedurel 1. Run the command:


NOTE

The HA system takes some time to stop the services. Wait for ten minutes after you run thecommand. Run the command svc_ps to monitor the service stopping progress.

----End

3.5.6 Starting the Sybase (HA)This section describes how to start the Sybase for the HA system.

Prerequisitel Log in to the server as user root through SSH mode.

l The osssvr_rs resource and ossdg_rs resource are already activated on the active node.

Contextl Run the following command to check the status of each resource on the active and standby

nodes of the HA system:# scstat



3-21

The online status means that the resource group is activated on the server.l On the active node, run the following command to activate the osssvr_rs resource:

# scswitch -e -j osssvr_rsl On the active node, run the following command to activate the ossdg_rs resource:

# scswitch -e -j ossdg_rs

Procedure

Step 1 Run the following command to start the Sybase:


----End

3.5.7 Stopping the Sybase (HA)This section describes how to stop the Sybase in the HA system.

Prerequisitel Log in to the server as user root through SSH mode.

l The M2000 service is already stopped. For details about how to stop the M2000 service,see 3.5.5 Stopping M2000 Services (HA).

Procedure

Step 1 Run the following command to stop the Sybase:


----End



Issue 03 (2010-08-31)

4 Setting the M2000 Time (HA)

About This Chapter

This chapter describes how to set the server time and the client time to ensure that the specifiedtime meets the requirements and is synchronized with the Huawei mobile equipment.

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

4.2 Modifying the Date and Time on the M2000 Server (HA)This section describes how to modify the data and time on the M2000 server. The correct servertime is important for collecting NE data, handling real-time tasks, and dumping the databaseinformation.

4.3 Changing the Time Zone of the M2000 Server Without Using DST (HA)This section describes how to change the time zone of the M2000 server in an HA system. Thecorrect server time zone is closely associated with collecting NE data, handling timing tasks,and dumping database information. Therefore, you need to set the server time zone correctly toensure the normal operation of the system.

4.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 runningthe Windows operating system. You can modify the date, time, and time zone on the M2000client by modifying the date, time, and time zone of the Windows.

4.5 Configuring the NTP Service of the M2000 (HA)This section describes how to set the M2000 server in an HA system as the NTP client andsynchronize time with the upper-layer server and how to set the M2000 client as the NTP clientand synchronize time with the M2000 server.

4.6 Setting DST for the M2000 (HA)This section describes how to set the time zone of the M2000 server to ensure that DST issupported in an HA system. If DST change occurs on an NE, ensure that the M2000 can handlethe data reported by the NE and that no reported data is missing.

HA System Administrator Guide (Sun, S10) 4 Setting the M2000 Time (HA)


4-1

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

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

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

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

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

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

4 Setting the M2000 Time (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

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.

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



4-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 4-1 shows the rationale of NTP time synchronization.

Figure 4-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 03 (2010-08-31)

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 4-2 NTP layered architecture

As shown in Figure 4-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).



4-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 NTP

SNTP is a simplified policy for the NTP server and the NTP client. The difference betweenSNTP and NTP is that SNTP has disadvantage over 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.

4.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 M2000

The time synchronization of a mobile network is implemented through the NTP/SNTP protocols.

The M2000 server uses Solaris 10 and supports the NTP features based on NTPV3 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 03 (2010-08-31)

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



4-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, it is preferred to use the existing NTP server as the time referencesource of 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 4-4.



Issue 03 (2010-08-31)

Figure 4-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 4-5.



4-9

Figure 4-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 03 (2010-08-31)

NOTE

l The M2000 server uses the Solaris operating system where you can configure the M2000 serveras the intermediate-layer NTP server. The time synchronization server for the RAN networkplays a special role and requires an independent and stable operating environment.Therefore,Huawei recommends that the M2000 server should not serve as the intermediate-layerNTP server for the RAN network.

l When a system using the Netra 240, V890 or E4900 server, the Netra 240 server is integrated asan administration console by default. In this case, the Netra 240 acts as the intermediate-layerNTP server 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 4-6 shows the networkingof device A and the highest layer NTP server.

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



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

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

Introduction

The DST is one hour earlier than the standard time. For example, during the DST, 10:00 am 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.

4.2 Modifying the Date and Time on the M2000 Server (HA)This section describes how to modify the data and time on the M2000 server. The correct servertime is important for collecting NE data, handling real-time tasks, and dumping the databaseinformation.

Prerequisitel Log in to the two nodes as user root through SSH mode by using the corresponding physical

IP addresses.l The Sybase and the M2000 services are stopped.



Issue 03 (2010-08-31)

ContextThe Sun Cluster uses the NTP to synchronize the time among the Cluster nodes.

CAUTIONl Modifying the server time results in a change in the Solaris lower layer time. This may

further result in the reset or failure of the timer that relies on the Solaris operating system.Thus, to avoid the timer failure, you must first stop the M2000 and Sybase services beforechanging the server time. During the period when you change the server time, theperformance data and alarm data of the managed NEs cannot be handled in time. After theSybase and the M2000 services are restored, the M2000 enables the automaticsynchronization function to recollect and handle the missing performance data and alarmdata.

l When the M2000 serves as the clock source of the NTP service, the time on the NEs issynchronized automatically after the server is modified. Adjusting the cluster date involvesusing the commands date, rdate, or xntpdate interactively or using these commands inthe cron script.

l The modified server time takes effect immediately. The changed time zone of the servertakes effect only after you restart the server. If you need to modify both the time zone andthe time, change the time zone first.

l When modifying the server time, ensure that the changed server time is within the validityperiod of the license. If the server time exceeds the license validity period, certain servicescannot be enabled.

ProcedureStep 1 Check the system date and time on node 1 and node 2.

# date

If the system date and time are incorrect, perform the subsequent steps to correct the date andtime.

Step 2 Shut down the cluster on the active node.

# /usr/cluster/bin/scshutdown -g0 -y

Step 3 Log in to both servers through the SC, RSC, or XSCF, switches to the ok state.

For details, see the M2000 HA System Software Initial Installation Guide (Sun, S10).

Step 4 Run the following commands at the two nodes, start node 1 and node 2 in non-cluster mode.

ok boot -x

Step 5 Log in to node 1 and node 2 as user root.

Step 6 On node 1, run the date command to set the system date and time.

# date mmddHHMMYYYY.SS

Set the system date and time to 2005-11-17 16:30:43.# date 111716302005.43



4-13

Mon Nov 17 16:30:43 CST 2005

You must set a correct date. Otherwise, the modification of the M2000 server date and time fails.

NOTE

If the GMT time is used, run the date -u mmddHHMMYYYY.SS command.

Step 7 Run the following command on node 1 and node 2 to start network time:

# svcadm enable svc:/network/time:stream

Step 8 On node 2, run the command rdate to synchronize the time with node 1.

# rdate host name of node 1

Step 9 Verify the new time on both node 1 and node 2.

# date

Step 10 Restart the server on node 1 and node 2.

# /usr/sbin/shutdown -i6 -g0 -y

----End

4.3 Changing the Time Zone of the M2000 Server WithoutUsing DST (HA)

This section describes how to change the time zone of the M2000 server in an HA system. Thecorrect server time zone is closely associated with collecting NE data, handling timing tasks,and dumping database information. Therefore, you need to set the server time zone correctly toensure the normal operation of the system.

Prerequisite

Log in to both nodes as user root through SSH mode by using the corresponding physical IPaddresses.

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 synchronization



Issue 03 (2010-08-31)

function, 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 HA system does not use DST, you need to change the time zone of the serverby performing the following operations. Otherwise, you need to change the time zone ofthe server by referring to 4.6 Setting DST for the M2000 (HA).

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.

Procedure

Step 1 Run the following command on both node 1 and node 2 to check the time zone of the server:

# echo $TZ

If the time zone of the server is incorrect, perform the following steps to change it:

Step 2 If the M2000 services are running, run the following command on the active node to stop them:


Step 3 Run the following command on the active and standby nodes and check whether there is anycommand result: If no system output is displayed, you can infer that the M2000 daemon isterminated.


# daem_ps

Step 4 If the daemon process is still running, run the following command to forcibly stop it:

# kill_daem

Step 5 If the Sybase services are running, run the following command on the active node to stop theSybase services:


Step 6 On node 1 and node 2, modify the /etc/TIMEZONE file and change the value of TZ to thename of the required time zone.


# vi /etc/TIMEZONE

For example, set TZ to GMT+8.



4-15

NOTE

l The time zone configurations of the active and standby nodes must be the same.

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 7 Run the following command on the active node to stop the cluster system:




Step 9 Run the following command to restart the server:

ok boot

NOTE

Start node 1 first. Wait for three minutes, and then start node 2.

Step 10 Log in to node 1 and node 2 as user root through SSH mode.

Step 11 If the Sybase services are stopped in Step 5, run the following command on node 1 or node 2to start the Sybase services:


Step 12 If the M2000 services are stopped in Step 2, run the following command on node 1 or node 2to start the M2000 services:


Step 13 Run the following command on the standby node to check whether there is any output:


# daem_ps

l If any output exists, you can infer that the daem process is started.

l If no output exists, you can infer that the daem process is not started. Run the followingcommands to start the daem process:# start_daem -type standby

----End

4.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 runningthe Windows operating system. You can modify the date, time, and time zone on the M2000client by modifying the date, time, and time zone of the Windows.



Issue 03 (2010-08-31)

PrerequisiteThe Windows operating system is operational.

Procedure

Step 1 Open the Control Panel.This section 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.5 Configuring the NTP Service of the M2000 (HA)This section describes how to set the M2000 server in an HA system as the NTP client andsynchronize time with the upper-layer server and how to set the M2000 client as the NTP clientand synchronize time with the M2000 server.

4.5.1 Checking the Time Settings of the M2000 Server (HA)This section describes how to check the time settings of the M2000 server in an HA system.Before configuring the NTP service of the server, you need to ensure that the time zone, date,and time on node 1 and node 2 are correct.

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

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

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

4.5.5 Setting the M2000 Server as an NTP Client (HA system)



4-17

This section describes how to set the M2000 HA server as an NTP client to synchronize theclock time with the upper-level server.

4.5.6 Starting the NTP Service on the M2000 Server (HA)This section describes how to start the NTP services on the servers of the M2000 HA system.By performing this task, you can synchronize the server time.

4.5.7 Checking the Running Status of the NTP Service on the M2000 Server (HA)This section describes how to check the running status of the NTP service on the servers of theM2000 HA system. By performing this task, you can ensure that the NTP service is functional.

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

4.5.1 Checking the Time Settings of the M2000 Server (HA)This section describes how to check the time settings of the M2000 server in an HA system.Before configuring the NTP service of the server, you need to ensure that the time zone, date,and time on node 1 and node 2 are correct.

Procedure

Step 1 Run the following command on both nodes to check the time zone of the system:

# echo $TZ

If the time zone is set incorrectly on the system that does not use DST, change the time zone byreferring to 4.3 Changing the Time Zone of the M2000 Server Without Using DST (HA).Otherwise, change the time zone by referring to 4.6 Setting DST for the M2000 (HA).

Step 2 Run the following command on both nodes to check the system date and time:

# date

If the date is incorrect or the time difference between the clock resource and node 1 or node 2exceeds two minutes, change the date by referring to 4.2 Modifying the Date and Time on theM2000 Server (HA).

----End

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

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 Log in to the administration console as user root through SSH mode.



Issue 03 (2010-08-31)

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.

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

ExampleTo 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



4-19

PostrequisiteAfter setting the M2000 administration console as the secondary NTP server, you need to startthe NTP service on the administration console. For details, see 4.5.3 Starting the NTP Serviceon the M2000 Administration Console.

4.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 Log in to the administration console as user root through SSH mode.

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

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



Issue 03 (2010-08-31)

Procedure

Step 1 View the information about the time source.

# ntpq -p

In the result of the command ntpq -p, the remote field shows the address and status of 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.

4.5.5 Setting the M2000 Server as an NTP Client (HA system)This section describes how to set the M2000 HA server as an NTP client to synchronize theclock time with the upper-level server.

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

l Log in to the active and standby nodes as user root through SSH mode.

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.



4-21

Procedure

Step 1 If the M2000 is running, stop the service on the active server.




# daem_ps


# kill_daem

Step 4 If the Sybase is running, stop the Sybase service on the active node.


Step 5 Run the following commands on both the active and standby nodes to check whether thentp.conf.cluster file is correct:


# vi /etc/inet/ntp.conf.cluster

The correct ntp.conf.cluster file should contain the following contents:

peer clusternode1-priv preferpeer clusternode2-priv

If using the NTP server specified by the operator, add a line server XXX.XXX.XXX.XXX beforeserver 127.127.1.0 in the file ntp.conf.cluster. If multiple NTP servers exist, addmultiple lines. XXX.XXX.XXX.XXX is the IP address of the NTP server specified by the operator.Replace XXX.XXX.XXX.XXX with the actual IP address.

Step 6 If the Sybase is stopped in Step 4, run the following command on either the active node or thestandby node to start the Sybase service.


Step 7 If the M2000 is stopped in Step 1, run the following command on either the active node or thestandby node to start the M2000 service.




# daem_ps





Issue 03 (2010-08-31)

Step 9 On both the active and standby nodes, check system time and date.

# date

If system time and date of the two nodes are not consistent, contact Huawei technical supportengineers for assistance.

----End

Postrequisite

After setting the M2000 server as the NTP client, you need to start the NTP service on the server.For details, see 4.5.6 Starting the NTP Service on the M2000 Server (HA).

4.5.6 Starting the NTP Service on the M2000 Server (HA)This section describes how to start the NTP services on the servers of the M2000 HA system.By performing this task, you can synchronize the server time.

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

l Log in to node 1 and node 2 as user root through SSH mode.

Procedure

Step 1 On node 1 and node 2, check whether the NTP service is running.

# ps -ef | grep ntp

l If a message similar to the following message is displayed, you can infer that the NTP serviceis running, perform Step 2 through Step 3 to stop the NTP service.root 24097 1 0 14:38:26 ? 0:00 /usr/lib/inet/xntpd -c /etc/inet/ntp.conf.cluster

l If a message similar is not displayed, you can infer that the NTP service is stopped.

Step 2 Run the following command on node 1 and node 2, stop the NTP service.

# kill -9 Process ID

From Step 1, you can determine that the process ID is 24097. To stop the NIP service, run thefollowing command on node 1 and node 2:# kill -9 24097

Step 3 Run the following command on node 1 and node 2 to check whether the NIP service is stopped:

# ps -ef | grep ntp

If the NTP service is started, repeat Step 2 to Step 3.

Step 4 On node 1 and node 2, run the following command to start the NTP service:

# /etc/rc2.d/S74xntpd.cluster start

----End



4-23

4.5.7 Checking the Running Status of the NTP Service on theM2000 Server (HA)

This section describes how to check the running status of the NTP service on the servers of theM2000 HA system. By performing this task, you can ensure that the NTP service is functional.

Context

The system check requires about five minutes after the NTP server and client are started. Afterthe system check, run the commands ntpq -p and ntptrace to check the status of the NTP service.

During this period, run ntpq -p and the displayed address of the remote clock source has no* identifier. Run ntptrace and the system displays Timeout or Not Synchronized.

Procedure

Step 1 Run the following commands on node 1 and node 2 to check the running status of the NTPservice.

# ntpq -p

# ntptrace

Step 2 View the results.

l The remote field in the ntpq -p is the address of the M2000 clock source and displays thestatus of the clock source.

l The ntptrace command traces the whole NTP synchronization link to the highest layer fromthis server. For details, run the command ntptrace -v.

As shown in Figure 4-7, the clock source of the host is a local clock. This host is located in thefourth layer of the NTP. It is normal that Timeout is shown after 127.127.1.0.

Figure 4-7 Status of NTP service on node 1

As shown in Figure 4-8, the clock source of the host is node 1 of the Cluster. This host is locatedin the fifth layer of the NTP and node 1 is located at the fourth layer. It is normal thatTimeout is shown after 127.127.1.0.



Issue 03 (2010-08-31)

Figure 4-8 Status of NTP service on node 2

----End


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.

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.



4-25

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


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 time



Issue 03 (2010-08-31)

is 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.6 Setting DST for the M2000 (HA)This section describes how to set the time zone of the M2000 server to ensure that DST issupported in an HA system. If DST change occurs on an NE, ensure that the M2000 can handlethe data reported by the NE and that no reported data is missing.

PrerequisiteLog in to both nodes as user root through SSH mode by using the corresponding physical IPaddresses.

Contextl In an HA system, the time zone configurations of both nodes must be the same.

l On the Solaris operating system, two time formats are available for the time zone: GMTand 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.

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

Procedure

Step 1 Query the local time zone name.

For details about how to query the name of a time zone name, see 16.1.9 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



4-27

l If specified year refers to the current year:– If DST is not used, only a 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 15 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.





# daem_ps


# kill_daem

Step 7 If the Sybase services are running, run the following command on the active node to stop theSybase services:



Issue 03 (2010-08-31)


Step 8 On node 1 and node 2, modify the /etc/TIMEZONE file and change the value of TZ to thename of the required time zone.


# vi /etc/TIMEZONE

For example, set TZ to PRC.

NOTE

l The time zone configurations of the active and standby nodes must be the same.

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 9 Run the following command on the active node to stop the cluster system:




Step 11 Run the following command to restart the server:

ok boot

NOTE

Start node 1 first. Wait for three minutes, and then start node 2.

Step 12 Log in to node 1 and node 2 as user root through SSH mode.

Step 13 If the Sybase services are stopped in Step 7, run the following command on node 1 or node 2to start the Sybase services:


Step 14 If the M2000 services are stopped in Step 4, run the following command on node 1 or node 2to start the M2000 services:




# daem_ps



----End



4-29

Example

The query of the DST rules of PRC and US/Alaska in 2007 is taken as an example.

l Run the following command to view the DST rule of the RPC time zone in 2007:

# zdump -v PRC|grep 2007

– If the current year is 2007,

the system displays only one row of the following information:PRC Mon Sep 17 06:03:55 2007 UTC = Mon Sep 17 14:03:55 2007 CST isdst=0

– If the current year is not 2007,

the system does not display any information.

Therefore, you can infer that the PRC time zone does not have DST in 2007.

l Run the following command to view the rule of the US/Alaska time zone in 2007:

# zdump -v US/Alaska|grep 2007

– If the current year is 2007,

The system displays the following information:US/Alaska 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

– 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 DSTstarts 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 03 (2010-08-31)

5 Configuring the IP Address of the M2000Server (HA)

About This Chapter

This chapter describes how to set the host name and IP address of the server in the M2000 HAsystem.

5.1 Adding or Deleting a Route of the M2000 ServerThis section describes how to add or delete a route of the M2000 server. This enables you to setup or delete routes from the local network to multiple target networks.

5.2 Changing the IP Address of the M2000 Server (HA)This section describes how to set the IP network multipathing (IPMP) on the active and standbynodes, how to change the physical IP addresses of the active and standby nodes, and how tochange the logical IP address of the HA system. In this case, the IP addresses of the server meetthe actual requirements.

5.3 Changing the IP Address of Ethernet Port nxge3 on the M2000 Server (HA)This section describes how to change the IP address of Ethernet port nxge3 on the M2000 serverin the HA system to meet the site requirement.

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

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

HA System Administrator Guide (Sun, S10) 5 Configuring the IP Address of the M2000 Server (HA)


5-1

5.1 Adding or Deleting a Route of the M2000 ServerThis section describes how to add or delete a route of the M2000 server. This enables you to setup or delete routes from the local network to multiple target networks.

Prerequisite

You have logged in to the server as user root in SSH mode.

Context

To add a route to the M2000 server, you must add the route to both nodes.

CAUTIONRun the following command to add a route. After you restart the server, the added route isautomatically disabled.

# route add Destination network address/mask gateway

For example:

# route add 129.8.0.0/24 10.12.8.1

Procedure

Step 1 Table 5-1 describes how to add, delete, view, or automatically add a route to the M2000 server.

Table 5-1 Adding or deleting a route

Operation Command Example

Adding aroute

# route add Destination networkaddress/mask gatewayl Destination network address: refers to

a network address or a host address.l Mask: refers to the number of binary

digit 1 in the subnet mask. Forexample, if the mask is 24, the IPaddress of the subnet is 255.255.255.0.

# route add 129.8.0.0/2410.12.8.1

Deleting aroute

# route delete Destination networkaddress/mask gateway

# route delete 129.8.0.0/2410.12.8.1

Viewing aroute

# netstat -rv -

5 Configuring the IP Address of the M2000 Server (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

Operation Command Example

Adding arouteautomatically when thesystem isrestarted

Run the following command to createthe /etc/rc2.d/S97route file:# vi /etc/rc2.d/S97routeWrite one or more route add Destinationnetwork address/mask gatewaycommands into the file.

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

----End

5.2 Changing the IP Address of the M2000 Server (HA)This section describes how to set the IP network multipathing (IPMP) on the active and standbynodes, how to change the physical IP addresses of the active and standby nodes, and how tochange the logical IP address of the HA system. In this case, the IP addresses of the server meetthe actual requirements.

Contextl The M2000 HA system provides a logical IP address for the external network. The IP

address is automatically assigned to the active server that provides services to the public.The M2000 clients, NEs, and NMS set up communications with the M2000 HA systemthrough the logical IP address of the server. Thus, functions such as data transfer, operationand maintenance are implemented.

l In the M2000 HA system, the IPMP is already configured before delivery. For example,the model of the server is V890. Network port ce0 is configured as the primary port, andce2 is configured to provide redundancy. The two network ports are added to the IPMPgroup. The physical IP addresses of the two network ports share the same physical IPaddress of the server, thus achieving the redundancy of network ports and guaranteeing thesmooth communication between the server and the external network. When other serversare adapted, the IPMP setting is similar with that of the V890 except the network adaptertype. The network adapter type varies with the model of the server. For their relation, seethe following information.

l When the OM network requires reparenting, adjustment or reallocation of IP addresses,you need to change the IP address of the M2000 server. You can change the IP address ofthe server to meet the requirements for network reparenting and adjustment. In this case,the OM network is easily managed and maintained and is more open and flexible. Inaddition, the scalability and evolution of the network are improved.

l In the M2000 HA system, the logical IP address of the server and the IPMP configurationand physical IP addresses of the active and standby nodes are stored in the systemconfiguration files of the active and standby nodes. You can run the modify script to modifythe relevant configuration files on the active and standby nodes to change the IP addressof the server.

l When you are changing the IP address of the M2000 server, the performance data and alarmdata of the managed NEs cannot be processed. If the IP address of the M2000 servers arerecorded in the NE database, changing the IP address of the M2000 server leads to thedisconnection between the M2000 server and NEs. When changing the IP address of theM2000 server, you need to notify the NE maintenance engineers and ask them to modify



5-3

the relevant plans and update the IP address of the M2000 server recorded in the NEdatabase. After you change the IP address of the server, the M2000 collects performancedata and alarm data again through automatic synchronization and then processes the data.

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

l After the installation and commissioning of the M2000 HA system are complete, osssvr-1acts as the active node and provides services, and osssvr-2 acts as the standby node.

CAUTIONl You can run the modify script to change the IP address of the server only when osssvr-1 is

the active node and osssvr-2 is the standby node. If the server does not meet the requirementof the active/standby relation, you need to manually adjust the relation.

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, 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 Ensure that the IPMP and physical IP addresses of the active and standby nodes and thelogical IP address of the HA system are on the same network segment. If you change the IPaddress of the M2000 server on different network segments, you need to plan and changethe physical IP addresses of the active and standby nodes and the logical IP address of thesystem.

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 Before changing the IP address of the server in the M2000 HA system, ensure that the twoservers are available and reliable. That is, the Oracle and M2000 services can be started orswitched between the active and standby nodes.

l This section describes how to change the IPMP configuration and physical IP addresses ofthe active and standby nodes and the logical IP address of the server all at once. If you needto change only some IP addresses of the HA system, perform operations to change only theseIP addresses in the relevant steps.

l The following operations take Ethernet adapter type ce as an example. Replace the networkadapter type with the actual type in your on-site operations.



Issue 03 (2010-08-31)

Procedure

Step 1 Log in to both nodes as user root through SSH mode.

Step 2 On either node, run the following command to determine the active and standby nodes:

# scstat -D

In the system output, the node corresponding to the Primary column is the active node and thenode corresponding to the Secondary column is the standby node.

This takes osssvr-1 as the active node and osssvr-2 as the standby node as an example.

NOTE

You can run the modify script to change the IP address of the server only when osssvr-1 is the active nodeand osssvr-2 is the standby node. If the server does not meet the requirement of the active/standby relation,you need to manually adjust the relation. For details, see 3.2.2 Manually Switching Over Active andStandby Nodes (HA).

Step 3 On either node, run the following command to view the /etc/hosts file. You can obtain the IPaddresses corresponding to the host names of the two nodes and the IP address correspondingto the name of the logical host in the HA system.

# more /etc/hosts

If the host name of the active node is osssvr-1, the host name of the standby node is osssvr-2,the name of the logical host of the HA system is osssvr, and the Ethernet adapter type is ce, youneed to obtain the IP addresses corresponding to fields osssvr, osssvr-1, osssvr-2, osssvr-1-ce0, osssvr-1-ce2, osssvr-2-ce0, and osssvr-2-ce2.

Step 4 Run the following command on both nodes to check the IP address of the server:

# ifconfig -a

In the system output, the system displays the IP addresses obtained in Step 3. These IP addressesare the logical IP address of the HA system and the physical IP addresses and IPMP configurationof the two nodes. Check whether the IP addresses meet the 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.

NOTE

Run the ifconfig -a command on the active node, the system displays the logical IP address of the HAsystem.

Step 5 Check whether the new IP address is already used.

This takes the IP addresses shown in Table 5-2 as an example.

Table 5-2 Correspondence between the previous and new IP addresses

Host Name Previous IP Address New IP Address

osssvr 192.168.8.31 10.10.10.10

osssvr-1 192.168.8.11 10.10.10.11

osssvr-2 192.168.8.12 10.10.10.12



5-5

Host Name Previous IP Address New IP Address

osssvr-1-ce0 192.168.8.59 10.10.10.40

osssvr-1-ce2 192.168.8.60 10.10.10.42

osssvr-2-ce0 192.168.8.61 10.10.10.41

osssvr-2-ce2 192.168.8.62 10.10.10.43

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

l ping 10.10.10.10

l ping 10.10.10.11

l ping 10.10.10.12

l ping 10.10.10.40

l ping 10.10.10.42

l ping 10.10.10.41

l ping 10.10.10.43

If the IP address can be successfully pinged, you can infer that this IP address is already usedand you need to use another one.

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

NOTE

This section describes how to change the IPMP configuration and the physical IP addresses of the activeand standby nodes and the logical IP address of the system. You need to check these IP addresses fromStep 3 through Step 5. If you need to change only some IP addresses of the HA system, check only the IPaddresses to be changed.



Step 7 Run the following command on both nodes to check whether there is any output. If no outputexists, you can infer that the M2000 daemon process is stopped.


# daem_ps

Step 8 If the daemon process continues running, run the following command to stop it:

# kill_daem

Step 9 Check whether the Sybase services are started. For details, see 16.2.1 How Do I Check Whetherthe Sybase Is Started.

If the Sybase services are not started, start them first. For details, see 16.2.2 How to Start theSybase (HA, Sun).

If the Sybase services are started, perform Step 10.



Issue 03 (2010-08-31)

Step 10 On the active node, namely, osssvr-1, 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 addressestake effect 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.sh2. Choose 1--IP.3. Based on the system prompts, enter the previous and new IP addresses.

a. When the system output is similar to the following information, press Enter. Thedefault value in the system output is 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.31]:

b. When the system output is similar to the following information, enter the new IPaddress corresponding to the previous IP address in 10.3.a.Please input the new ip[default 192.168.8.31]: 10.10.10.10

c. When the system output is similar to the following information, press Enter. Thedefault value in the system output is used.

Please input the old ip[default 192.168.8.11]: d. When the system output is similar to the following information, enter the new IP

address corresponding to the previous IP address in 10.3.c.Please input the new ip[default 192.168.8.11]: 10.10.10.11

e. When the system output is similar to the following information, press Enter. Thedefault value in the system output is used.

Please input the old ip[default 192.168.8.12]: f. When the system output is similar to the following information, enter the new IP

address corresponding to the previous IP address in 10.3.e.Please input the new ip[default 192.168.8.12]: 10.10.10.12

g. 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.59

h. When the system output is similar to the following information, enter the new IPaddress corresponding to the previous IP address in 10.3.g.Please input the new ip[default 192.168.8.59]: 10.10.10.40



5-7

i. When the system output is similar to the following information, enter the old IP addresscorresponding to osssvr-1-ce2.Please input the old ip: 192.168.8.60

j. When the system output is similar to the following information, enter the new IPaddress corresponding to the previous IP address in 10.3.i.Please input the new ip[default 192.168.8.60]: 10.10.10.42

k. When the system output is similar to the following information, enter the old IP addresscorresponding to osssvr-2-ce0.Please input the old ip: 192.168.8.61

l. When the system output is similar to the following information, enter the new IPaddress corresponding to the previous IP address in 10.3.k.Please input the new ip[default 192.168.8.61]: 10.10.10.41

m. When the system output is similar to the following information, enter the old IP addresscorresponding to osssvr-2-ce2.Please input the old ip: 192.168.8.62

n. When the system output is similar to the following information, enter the new IPaddress corresponding to the previous IP address in 10.3.m.Please input the new ip[default 192.168.8.62]: 10.10.10.43

o. 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 When you run the modify script to change the server IP address, the logical IP address of the HAsystem, and the physical IP addresses of the two nodes, these IP addresses are displayed randomly.This takes changing the logical IP address of the HA system first and then changing the physicalIP addresses of the two nodes as an example. During the actual operations, the sequence maydiffer. Perform the operations according to the actual requirements.

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 addresses, enter f or F to finish enteringIP addresses and proceed with the next step.

l This takes changing the logical IP address of the HA system and the physical IP addresses of thetwo nodes, and setting the IPMP of the two nodes as an example. If you need to change some IPaddresses, you need to change the IP addresses to be changed.

4. Based on the system prompts, enter the password of user sa and then change the subnetmask, 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 as an example.------------------------------------------------------------------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.



Issue 03 (2010-08-31)

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 reconfigurethe 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.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 10.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 11 Based on the application scenario, perform the relevant operations.

Whether to Change the Server IP Address onDifferent Network Segments

Procedure

No Perform Step 12.

Yes Perform Step 13 through Step 18.

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



5-9

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. On the active node, run the following commands to stop the Cluster:



2. Log in to both servers through the SC, RSC, or XSCF, switches to the ok state.

For details, see the M2000 HA System Software Initial Installation Guide (Sun, S10).3. Run the following command to restart the servers:

ok boot

NOTE

Start node 1 first. Wait for three minutes and then start node 2.

4. After starting the server, log in to the HA system as user root through SSH mode by usingthe logical IP address and the physical IP addresses of the active and standby nodes,respectively. If the IP addresses are changed, log in to the HA system by using the new IPaddresses.

5. On either node, run the following command to start the Sybase services:


6. On either node, run the following command to start the M2000 services:


7. On the standby node, run the following command to check whether there is any output:


# daem_ps



8. On the active node, check the status of the Sybase and M2000 services.

# su - dbuser

For details about how to check the status of the Sybase services, see 16.2.1 How Do ICheck Whether the Sybase Is Started.

-bash-3.00$ exit





Issue 03 (2010-08-31)

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

Step 14 Log in to both servers through the SC, RSC, or XSCF.


Step 15 On the active node, run the following commands to stop the Cluster:





Step 17 Run the following command to restart the servers:

ok boot

NOTE

Start node 1 first. Wait for three minutes and then start node 2.

Step 18 Run the following command to 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. After starting the server, log in to the HA system as user root through SSH mode by usingthe new logical IP address and the new physical IP addresses of the active and standbynodes, respectively.

2. On either node, run the following command to start the Sybase services:


3. On either node, run the following command to start the M2000 services:


4. On the standby node, run the following command to check whether there is any output:


# daem_ps



5. On the active node, check the status of the Sybase and M2000 services.

# su - dbuser



5-11

For details about how to check the status of the Sybase services, see 16.2.1 How Do ICheck Whether the Sybase Is Started.

-bash-3.00$ exit



----End

Postrequisitel (Optional) If the S2600 disk array is configured and the physical IP addresses of both nodes

are configured as the two Trap IP addresses of the S2600 disk array, you need to reconfigurethe monitoring function of the S2600 disk array after changing the physical IP address ofthe active or standby node. For details, see How to Configuring the Monitoring Functionof the S2600 Disk Array. You need to reconfigure the two disk arrays.

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 16.1.18 How Should I Configure the Monitoring Function for the S3000 SeriesDisk Arrays. You need to reconfigure the two series disk arrays.

5.3 Changing the IP Address of Ethernet Port nxge3 on theM2000 Server (HA)

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

Prerequisite

Log in to the active and standby nodes as user root through SSH mode.

Context

CAUTIONl If the M4000/M5000 server is used, Ethernet port nxge3 is used to connect disk arrays. The

IP address of Ethernet port nxge3 on the active node and the IP address of the disk array mustbe on the same network segment.

l If you have changed the IP address of Ethernet port nxge3 on the active node on a differentsegment, you need to change the IP address of the corresponding disk array to ensure thatboth changed IP addresses are on the same network segment.

l Changing the IP address of Ethernet port nxge3 does not affect the database services and theM2000 services.

l This takes changing the IP address of Ethernet port nxge3 on the osssvr-1 as an example.The method of changing the IP address of nxge3 on the other node is similar.



Issue 03 (2010-08-31)

Procedure

Step 1 Run the following command on osssvr-1 to change the IP address of Ethernet port nxge3:

# ifconfig -a

The IP address of Ethernet port nxge3 on the osssvr-1 is displayed in the system output. Checkwhether it meets the site requirement.

l If it does not meet the requirement, you need to perform the following steps to change it.

l If it meets the requirement, you need not perform the following steps.

Step 2 Check whether the new IP address is use.

This takes changing the IP address of Ethernet port nxge3 on osssvr-1 from 192.168.8.241 to10.10.10.241 as 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, you can infer that this new IP address is alreadyused. In this case, use another IP address.

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

Step 3 Perform the following steps on the active and standby nodes to change the IP address of Ethernetport nxge3 on osssvr-1:1. Modify the /etc/hosts file to change the existing IP address of Ethernet port nxge3 on

osssvr-1 to a new IP address.


# vi /etc/hosts

2. Run the following command to check the link between the /etc/inet/ipnodes file and the /etc/inet/hosts file:

# ls -al /etc/inet/ipnodes

l If /etc/inet/ipnodes -> ./hosts is contained in the system output, you caninfer 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, youcan infer 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, you caninfer that the two files are linked, that is, the /etc/hosts file and the /etc/inet/ipnodesfile are linked. Then, perform Step 4.

l If /etc/hosts -> ./inet/hosts is not contained in the system output, you caninfer 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 nxge3on osssvr-1 to a new IP address.



5-13

# vi /etc/inet/ipnodes

Step 4 On osssvr-1, modify the /etc/hostname.nxge3 file to change the exiting IP address of Ethernetport nxge3 on the active node to 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 on osssvr-1 for the new IP address of Ethernet port nxge3 to takeeffect:

# ifconfig nxge3 10.10.10.241 netmask 255.255.255.0 up

----End

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

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

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

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

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

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

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



Issue 03 (2010-08-31)

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

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



5-15

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

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

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 5-3. When the system displays anyparameter that is not listed in Table 5-3, press Enter to continue.



Issue 03 (2010-08-31)

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

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 5-4. When the system prompts anyparameter that is not listed in Table 5-4, press Enter to continue.



5-17

Table 5-4 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]

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

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



Issue 03 (2010-08-31)

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

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

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.



5-19

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 the corresponding M2000 SoftwareInitialization Installation Guide.

l If the PC and XSCF cannot be connected by running the telnet command, connect them through aserial port cable. For details, see the corresponding M2000 Software Initialization Installation Guide.

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

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.



Issue 03 (2010-08-31)

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

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

5.5.1 Modifying the IP Address of the 3320 Disk ArrayThis section describes how to modify the IP address of the 3320 disk array. To perform this task,you need to log in to the 3320 disk array through PC or administration console. Normally, youneed not 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.



5-21

5.5.2 Changing the IP Address of the S3X00 Series Disk Array (Serial Port Mode)This section describes how to change the IP address of the S3X00 disk array. Normally, youneed not 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.The IP address of each S3X00 disk array needs to be changed.

5.5.3 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, changing IP addresses does not affect data readoperations on the disk array. Generally, you need to use the factory default IP address of the diskarray. If the IP address of a disk array needs to be changed, you need to change the IP addressaccording to the actual situation. You need to configure each 6140 disk array.

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

5.5.1 Modifying the IP Address of the 3320 Disk ArrayThis section describes how to modify the IP address of the 3320 disk array. To perform this task,you need to log in to the 3320 disk array through PC or administration console. Normally, youneed not 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.

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:



Issue 03 (2010-08-31)

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 of the two nodes.

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. You have logged into both the nodes as user root.2. Perform the following operations on both the nodes 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 both the nodes 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

5.5.2 Changing the IP Address of the S3X00 Series Disk Array(Serial Port Mode)

This section describes how to change the IP address of the S3X00 disk array. Normally, youneed not 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.The IP address of each S3X00 disk array needs to be changed.


ContextEach S3X00 disk array has two controllers and each controller has two ports. To change the IPaddress of the controller, you need to change only port 1 on the controller. Retain port 2 forfuture use.



5-23

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 5-1 shows the disk array.

Figure 5-1 Serial ports of the S3X00

NOTE

You must use the serial port cable that is delivered with the disk array rather than 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 need to configure the controller that is connected to the serialport (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 Specify a serial port of the PC terminal to connect to the disk array.

Step 5 Set the properties of the serial port. For details about how to set the properties of a serial port,see Table 5-5. Then, click OK.

Table 5-5 Setting properties of the serial port

Property Value

Bits per second 9600/38400

Data bits 8

Parity Null

Stop bits 1



Issue 03 (2010-08-31)

Property Value

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 port configuration of the controller that you havelogged in to.

-> netCfgShow

Figure 5-2 shows the port configuration of the controller that you have logged in to.

Figure 5-2 Checking the port configuration

Table 5-6 shows the main configuration items in Figure 5-2.

Table 5-6 Configuration items of the controller port

Configuration Item Meaning

IP Address if0 Indicates the IP address of port if0 of thecontroller that you have logged in to.



5-25

Configuration Item Meaning

Subnet Mask if0 Indicates the subnet mask of port if0 of thecontroller.

Gateway IP Address Indicates the gateway IP address.

l If the port configuration of the controller meets the specifications, you need not perform anyoperation.

l If the port configuration of the controller does not meet the specifications, perform thefollowing operation to change it.

Step 10 Run the following command:

-> netCfgSet

The system output is similar to the message shown in Figure 5-3. Press Enter.

Figure 5-3 Port configuration (I)

Step 11 Set the IP address of port if0 of the controller.

This takes 192.168.8.39 as an example to describe how to change the IP address of port if0. Aftertyping the new IP address, press Enter, as shown in Figure 5-4.

Figure 5-4 Port configuration (II)

NOTE

l If you press Enter without typing a new IP address, the original IP address retains.

l To restore the IP address of port if0 to the default value predefined before delivery, enter "." and thenpress Enter.

Step 12 Set the subnet mask of port if0 of the controller.



Issue 03 (2010-08-31)

In the output information shown in Figure 5-5, type the new subnet mask and then pressEnter. If you press Enter without typing a new subnet mask, the original one retains. To restorethe subnet mask of port if0 to the default value predefined before delivery, enter "." and thenpress Enter.

Figure 5-5 Port configuration (III)

Step 13 The output information is similar to the following message. Press Enter. The IP address of portif1 is not changed.IP Address if1 : 192.168.129.101

Step 14 The output information is similar to the following message. Press Enter. The subnet mask ofport if1 is not changed.Subnet Mask if1 : 255.255.255.0

Step 15 The system displays the following message. Press Enter.Server Host Name :

Step 16 The system displays the following message. Press Enter.Server IP Address :

Step 17 Set the gateway IP address.

This takes 192.168.8.39 and 255.255.255.0 as an example to describe how to change the IPaddress and subnet mask of port if0. After typing in the new gateway IP address 192.168.8.1,press Enter, as shown in Figure 5-6.

Figure 5-6 Port configuration (IV)

l If you press Enter without typing a new gateway IP address, the original one retains.

l To restore the gateway IP address to the default value predefined before delivery, enter "."and then press Enter.

Step 18 When the system displays the following message, press Enter.Network Init Flags : 0xA0

Step 19 When the system displays the following message, press Enter.User Name :

Step 20 When the system displays the following message, press Enter.User Password :

Step 21 When the system displays the following message, then the IP address of the controller that youhave logged in to is successfully changed.Network Configuration successfully written to NVSRAM.

Step 22 Run the following command to check whether the information about the port of the disk arrayis correctly changed.

-> netCfgShow



5-27

l If the port information is incorrect, perform the previous steps to change it. Then, performStep 23.

l If the port information is correct, perform Step 23.

Step 23 Check whether the new IP address of the controller takes effect.

On the client PC whose IP address is in the same network segment as the new IP address, openthe DOS command window and then run the ping New IP address of the disk arraycontroller command.

l If you successfully ping the IP address, then the new IP address takes effect.

l If you fail to ping the IP address, contact Huawei technical support engineers for assistance.

Step 24 Connect the serial port cable to the port of controller B. Perform the previous steps to changethe port IP address of the other controller.

Step 25 (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file of the two nodes.NOTE


1. Log into both the nodes as user root through SSH mode.2. Perform the following operations on both the nodes 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 both the nodes 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.


----End

Postrequisite(Optional) After changing the IP address of the S3X00 disk array, you need to reconfigure themonitoring function of the disk array. For details, see 16.1.18 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.

5.5.3 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, changing IP addresses does not affect data read



Issue 03 (2010-08-31)

operations on the disk array. Generally, you need to use the factory default IP address of the diskarray. If the IP address of a disk array needs to be changed, you need to change the IP addressaccording to the actual situation. You need to configure each 6140 disk array.

ContextThe 6140 disk array has two controllers. Each controller has two Ethernet ports. When youchange the IP address of a controller, only Ethernet port 1 needs to be modified. Ethernet port2 is reserved 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 different network segments, you needto change the IP address of the corresponding Ethernet port nxge3 to ensure that both of thechanged IP addresses are on the same network segment.

Procedure

Step 1 Connect the 6-pin mini DIN connector of the basic cable to the serial port connector of controllerA. Figure 5-7 shows the disk array.

Figure 5-7 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.

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 5-7. Then, click OK.



5-29

Table 5-7 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 a 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.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==============================



Issue 03 (2010-08-31)

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 changed IP addressis correct again. If the changed IP address is incorrect, perform Step 12 through Step 17 toconfigure 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:

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 of the two nodes.

NOTE


1. Log in to both nodes as user root.



5-31

2. Perform the following operations on both nodes to modify the /etc/hosts file and to replacethe 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 both nodes 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

5.5.4 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 modeis preferred because it features high success rate in changing IP addresses. In the case ofremote operations, use the command mode. For details, see 16.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 5-8 shows the disk array.



Issue 03 (2010-08-31)

Figure 5-8 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 5-8, and then click OK.

Table 5-8 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 Figure5-9.



5-33

Figure 5-9 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 5-10.

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 5-10 Successful login dialog box



Issue 03 (2010-08-31)

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.



5-35

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

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

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

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

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

HA System Administrator Guide (Sun, S10) 6 Managing the M2000 Clients


6-1


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

6.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 6-1 describes the parameters specified in the equations.

Table 6-1 M2000 client software directory

Directory Description

client installation path Refers to the installation path of the M2000client software. The default path is C:\iManagerM2000ClientClient.

M2000 client installation path\client Refers to the path for saving client programs.

M2000 client installation path\client\bin Refers to the path for saving executable files.

M2000 client installation path\client\Data

Refers to the path for saving NE configurationfiles.

M2000 client installation path\client\diagnosis

Refers to the path for saving the information thatis used for locating problems.NOTE

This path appears only after you run the M2000diagnosis tool.

M2000 client installation path\client\ext_runcfg

Refers to the path for saving the configurationfiles of integrated components.

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

M2000 client installation path\client\IDAPI32

Refers to the path for saving the localWSdynamic link libraries.

6 Managing the M2000 Clients HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)


M2000 client installation path\client\lib Refers to the path for saving the library files.

M2000 client installation path\client\localWs

Refers to the path for saving LocalShell that isused to start the 2G LMT.

M2000 client installation path\client\style

Refers to the path for saving the configurationfiles of the client.

M2000 client installation path\client\Templates

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

M2000 client installation path\client\tmp Refers to the path for saving temporary filesduring the upgrade.

M2000 client installation path\client\tracefile

Refers to the path for saving trace files.

M2000 client installation path\client\update

Refers to the path for saving upgrade files.

M2000 client installation path\client\cbb Refers to the path for saving the CBB files ofthe M2000 client.

M2000 client installation path\client\configuration

Refers to the buffer path of the M2000 client.The path automatically generates when theclient is started.

M2000 client installation path\client\features

Refers to the path for saving the featureconfiguration file of each subsystem of theM2000 client.

M2000 client installation path\client\plugins

Refers to the path for saving the configurationfile of each subsystem of the M2000 client asplug-ins.

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

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

M2000 client installation path\client\bin\run

Refers to the path for saving the startupparameter configuration files of the client andcomponents.



6-3


M2000 client installation path\cau Refers to the path for saving the Client AutoUpgrade (CAU) client software and the version,document abstract, and group information aboutthe M2000 client.NOTE

l The CAU client software provides the upgradedetection mechanism that is based on thedocument abstract for comparing the documentabstract of the server with that of the client. If thedocument abstracts are not consistent, you need toupgrade the client.

l Based on the group information, the server groupsand packs all the client documents deployed on theserver so that the client can download, install, andupgrade these documents. Based on the groupinformation, the client also groups and packs allthe client files. Therefore, these files can becompared with those grouped and packed by theserver after being downloaded.

M2000 client installation path\jre Refers to the path for saving the Java virtualmachine delivered with the M2000 client.

M2000 client installation path\lib Refers to the path for saving the dynamiclibraries shared among the M2000 client,remote alarm notification client, scriptframework client, and data management client.

M2000 client installation path\notify Refers to the path of the remote alarmnotification tool.

M2000 client installation path\TrafficReview

Refers to the path of the trace review tool.


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



Issue 03 (2010-08-31)

l Temporary files after the running of the M2000 log collector

Procedurel Delete the trace logs.

Delete the history trace logs saved in the directory M2000 client installation path\client\tracefile. It is recommended that you preserve the trace logs generated in the latest 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

6.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 > User Session Monitoring. The User Session Monitoring dialog box isdisplayed.

Step 3 Click the User Session Monitoring tab to monitor all the terminals connected to the M2000system.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 Log Out.

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

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



6-5

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

l The M2000 client is running properly.

ContextIdeally, 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.swimap.omc.common\style\productstyle\com.swimap.corba\conf\communicate.xml file, the value of corba_portpoolindicates the port range that the client attempts to occupy. The minimum port number is separatedfrom the maximum number by "-". The client tests the port from the minimum number to themaximum number. If all the ports are occupied, the system displays an Error message. You canset the maximum number of clients of the same version started on a PC by modifying the valueof corba_portpool.

Procedure

Step 1 Open the communicate.xml file in the M2000 client installation path\client\plugins\com.swimap.omc.common\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

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

6.4.1 Modifying the Date, Time, and Time Zone on the M2000 Client



Issue 03 (2010-08-31)

This section describes how to modify the date, time, and time zone on the M2000 client runningthe Windows operating system. You can modify the date, time, and time zone on the M2000client by modifying the date, time, and time zone of the Windows.


6.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 runningthe Windows operating system. You can modify the date, time, and time zone on the M2000client by modifying the date, time, and time zone of the Windows.

PrerequisiteThe Windows operating system is operational.

Procedure

Step 1 Open the Control Panel.This section 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




6-7

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.

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.



Issue 03 (2010-08-31)

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.


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



6-9

7 Managing the M2000 Users (HA)

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.

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

7.2 Managing Solaris Users (HA)This 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.

7.3 Managing Sybase Users (HA)This 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.

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

HA System Administrator Guide (Sun, S10) 7 Managing the M2000 Users (HA)


7-1

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

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

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

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

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

7.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 alsohave one manually created user group: omcsysm.

The default password and user name of each user account are the same.

l The default password of user root is root.

l The default password of user dbuser is dbuser.

l The default password of user omcuser is omcuser.

l The default password of user ftpuser is ftpuser.

Table 7-1 describes the Solaris user accounts.

7 Managing the M2000 Users (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

Table 7-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 isthe administratorof the 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



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

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.

7.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 03 (2010-08-31)

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



7-5

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

7.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 7-2 describes the M2000 user privileges.

Table 7-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 03 (2010-08-31)

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.

7.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 Prefer to use the default command groups provided by NEs. If you have to customize

command groups, customize them 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.

7.2 Managing Solaris Users (HA)This 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.



7-7


7.2.2 Changing the Password of User rootThis section describes how to change the password of user root. The password of user root onthe two nodes must be consistent. Thus, you must change the password of user root on the twonodes to ensure the password consistency.

7.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. The password of user dbuser on the two nodes must be consistent. Thus, you mustchange the password of user dbuser on the two nodes to ensure the password consistency.

7.2.4 Changing the Password of User omcuserThis section describes how to change the password of user omcuser when you log in to thesystem as user root. The password of user omcuser on the two nodes must be consistent. Thus,you must change the password of user omcuser on the two nodes to ensure the passwordconsistency.

7.2.5 Changing the Password of the User ftpuser (HA)This section describes how to change the password of user ftpuser of the Sybase.

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

7.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 alsohave one manually created user group: omcsysm.

The default password and user name of each user account are the same.

l The default password of user root is root.

l The default password of user dbuser is dbuser.

l The default password of user omcuser is omcuser.

l The default password of user ftpuser is ftpuser.

Table 7-3 describes the Solaris user accounts.



Issue 03 (2010-08-31)

Table 7-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 isthe administratorof the 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



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

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

7.2.2 Changing the Password of User rootThis section describes how to change the password of user root. The password of user root onthe two nodes must be consistent. Thus, you must change the password of user root on the twonodes to ensure the password consistency.

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 through SSH mode, and then enter the old password of user root.



Issue 03 (2010-08-31)

Step 2 Change the password.

# passwd root

New password:new password

Re-enter new password:new password

passwd: password successfully changed for root

----End

7.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. The password of user dbuser on the two nodes must be consistent. Thus, you mustchange the password of user dbuser on the two nodes to ensure the password consistency.

Prerequisitel The new password for dbuser is available.

l Log in to the M2000 server as user root through SSH mode.

Procedure

Step 1 Run the following command to change the password:

# passwd dbuser



passwd: password successfully changed for dbuser

----End

7.2.4 Changing the Password of User omcuserThis section describes how to change the password of user omcuser when you log in to thesystem as user root. The password of user omcuser on the two nodes must be consistent. Thus,you must change the password of user omcuser on the two nodes to ensure the passwordconsistency.

Prerequisitel The new password for omcuser is available.

l Log in to the M2000 server as user root through SSH mode.

ContextNOTE

The provided password must meet the policy of minimum complexity. The password comprises of at least6 letters or digits, among which one digit or special character is included.



7-11

Procedure

Step 1 Run the following command to change the password:

# passwd omcuser



passwd: password successfully changed for omcuser

----End

7.2.5 Changing the Password of the User ftpuser (HA)This section describes how to change the password of user ftpuser of the Sybase.

Prerequisitel The new password of user ftpuser is available.

l Log in to both servers as user root through SSH mode.

Context

CAUTIONl After the installation and commissioning of the M2000 HA system are complete, osssvr-1

acts as the active node and provides services, and osssvr-2 acts as the standby node.l You can run the modify script to change the password of user ftpuser only when osssvr-1 is

the active node and osssvr-2 is the standby node. If the server does not meet the requirementof the active/standby relation, you need to manually adjust the relation.

l The special characters '"$ cannot be contained in the password of user ftpuser. To improvethe password 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 On either node, run the following command to determine the active and standby nodes:

# scstat -D




Issue 03 (2010-08-31)


NOTE

You can run the modify script to change the password of user ftpuser only when osssvr-1 is the active nodeand osssvr-2 is the standby node. If the server does not meet the requirement of the active/standby relation,you need to manually adjust the relation. For details, see 3.2.2 Manually Switching Over Active andStandby Nodes (HA).

Step 2 If the M2000 services are running, run the following command on the active node to stop theM2000 services:




# daem_ps


# kill_daem




Step 6 On the active node, run the modify script to change the password of user ftpuser.1. Run the modify script.




# ./modify.sh2. Choose 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.



7-13

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, you can infer that the change issuccessful.------------------------------------------------------------------ Operator complete!


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




Step 8 On the active node, run the following command to start the M2000 services.


Step 9 On the standby node, run the following command to check whether there is any output:


# daem_ps


l If no output exists, you can infer that the daem process is not started. Run the followingcommands to start the daem process:

# start_daem -type standby

----End

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



Issue 03 (2010-08-31)

ContextBefore 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 through SSH mode.

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

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

Procedure

Step 1 Log in to the M2000 server as user root through SSH mode.

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.



7-15

NOTE

Do not delete the users required for the OM of the M2000, such as ftpuser, dbuser, and omcuser.

----End

7.3 Managing Sybase Users (HA)This 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.


7.3.2 Changing the Password of the User sa (HA)This section describes how to change the password of user sa.


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.

7.3.2 Changing the Password of the User sa (HA)This section describes how to change the password of user sa.

Prerequisitel The new password of user sa is available.

l Log in to both servers as user root through SSH mode.



Issue 03 (2010-08-31)

Context

CAUTIONl After the installation and commissioning of the M2000 HA system are complete, osssvr-1

acts as the active node and provides services, and osssvr-2 acts as the standby node.l You can run the modify script to change the password of user sa only when osssvr-1 is the

active node and osssvr-2 is the standby node. If the server does not meet the requirement ofthe active/standby relation, you need to manually adjust the relation.

l To 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 passwordcan contain only 0~9, a~z, A~Z, and special characters ~!@#%^&*()_-+=|\/<>,.;:[]{}.

ProcedureStep 1 On either node, run the following command to determine the active and standby nodes:

# scstat -D



NOTE

You can run the modify script to change the password of user sa only when osssvr-1 is the active node andosssvr-2 is the standby node. If the server does not meet the requirement of the active/standby relation, youneed to manually adjust the relation. For details, see 3.2.2 Manually Switching Over Active and StandbyNodes (HA).

Step 2 If the M2000 services are running, run the following command on the active node to stop theM2000 services:




# daem_ps


# kill_daem





7-17


Step 6 On the active node, run the modify script to change the password of user sa.1. Run the modify script.




# ./modify.sh

2. Choose 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:

NOTE



l Press Enter. The default values in the system output are used.

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.

5. When the system displays the following information, you can infer that the change issuccessful.------------------------------------------------------------------ Operator complete!


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

Step 7 On the active node, run the following command to start the M2000 services.




Issue 03 (2010-08-31)

Step 8 On the standby node, run the following command to check whether there is any output:


# daem_ps



----End

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



7-19

8 Managing OSS System (HA)

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.

8.1 Monitoring the M2000 Server (HA)You can monitor the status (including the status of the service, process, hard disk and database)and the component information of the M2000 server as well as logs of the operations performedon the system monitor client.

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

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

8.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 SUN SLS solution or the ATAE clustersystem solution, NEs can be managed by different servers (subareas). On the M2000 client, youcan query different NE subareas.

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

8.6 Check OMC statusOMC check is used to check the status of the M2000. This check also exports check reportsin .html format. The OMC check enables you to find the hidden problems of devices. Thus,severe accidents are avoided and proper operation of current devices is ensured.

8.7 Integrated Task Management

HA System Administrator Guide (Sun, S10) 8 Managing OSS System (HA)


8-1

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

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

8 Managing OSS System (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

8.1 Monitoring the M2000 Server (HA)You can monitor the status (including the status of the service, process, hard disk and database)and the component information of the M2000 server as well as logs of the operations 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.

8.1.1 Refreshing the Monitoring InformationTo know the latest running status of the M2000 server, you need to refresh the monitoringinformation. The M2000 server also periodically refreshes the monitoring information accordingto the specified monitoring interval.

8.1.2 Checking the CPU and Memory Usage Information About the M2000 Server (HA)This section describes how to check the CPU usage, memory capacity, and free memory space.When the CPU status or memory status of the server is abnormal, you need to locate faults andlog in to the server to rectify the faults in time. The client can monitor the active node and standbynode simultaneously.

8.1.3 Checking the Disk Usage Information About the M2000 Server Through the M2000 Client(HA)This section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client. The client can monitor the active node andstandby node simultaneously.

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

8.1.5 Checking the M2000 Services



8-3

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

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

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

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

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

8.1.1 Refreshing the Monitoring InformationTo know the latest running status of the M2000 server, you need to refresh the monitoringinformation. The M2000 server also periodically refreshes the monitoring information accordingto the specified monitoring interval.

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

Step 2 In the System Monitor Browser window, click the tab of the monitoring information to berefreshed.

Step 3 click Refresh.

----End

8.1.2 Checking the CPU and Memory Usage Information About theM2000 Server (HA)

This section describes how to check the CPU usage, memory capacity, and free memory space.When the CPU status or memory status of the server is abnormal, you need to locate faults andlog in to the server to rectify the faults in time. The client can monitor the active node and standbynode simultaneously.



Issue 03 (2010-08-31)

Prerequisitel You have logged in to the M2000 client.

l You have the relevant operation rights.

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 8-1.

Figure 8-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

8.1.3 Checking the Disk Usage Information About the M2000 ServerThrough the M2000 Client (HA)

This section describes how to check the disk usage information about the M2000 server throughthe system monitor browser of the M2000 client. The client can monitor the active node andstandby node simultaneously.



8-5


l You are authorized with the relevant operation rights.

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 8-2.

Figure 8-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



Issue 03 (2010-08-31)

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



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

Figure 8-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



8-7

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



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 8-4.

Figure 8-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



Issue 03 (2010-08-31)




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 8-5.

Figure 8-5 Process Monitor tab page


----End



8-9

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


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

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

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



Issue 03 (2010-08-31)

Procedure

Step 1 In the main window, choose Monitor > System Monitor > Settings. The System MonitorSettings dialog box is displayed, as show in Figure 8-6.

Figure 8-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 8-1.



8-11

Table 8-1 Server Monitor

Name Description Settings

Server MonitorParameter Settings

CPU sustainedoverload times(10-400 times)

Description:l The number of

consecutivesampling times isequal to CPUsustainedoverload times.The samplinginterval is equal toServer statusrefresh interval.If the CPU usagesampled each timeis larger than thegenerationthreshold, itmeans that theCPU isconsecutivelyoverloaded. Whenthe number ofoverload timesreaches thespecified value, ahigh CPU usagealarm isgenerated.

l If the CPU usagesampled at a timeis smaller than theclearancethreshold, the highCPU usage alarmis cleared.

Value:Value range: 10-400Default value: 40

Server status refreshinterval (2-60seconds)

Description:Refresh interval forserver monitoring,that is, the CPUusage is sampledevery x seconds.




Issue 03 (2010-08-31)


Server MonitorThreshold Settings

CPU usage (%) Description:Used to setThreshold forAlarm Generation,Threshold forAlarm Clearancefor the CPU usagealarm and whether toenable the bubble.

Value:Value range: 1-99.Default value: 90.Offset value range:1-99. Default value:70.

Memory usage (%) Used to setThreshold forAlarm Generationand Threshold forAlarm Clearancefor the memoryusage alarm.l If the memory

usage is largerthan Thresholdfor AlarmGeneration ofMemory usedrate, the M2000generates a highmemory usagealarm.

l If the memoryusage is smallerthan Thresholdfor AlarmClearance ofMemory usedrate, the M2000generates analarm, promptingthat the highmemory usagealarm is cleared.

l When the functionof bubbleinformation isenabled, if theserver is faulty,the systemdisplays a bubbleinformation.


Table 8-2 describes the parameters for monitoring the disks of the server.



8-13

Table 8-2 Hard Disk Monitor


Disk MonitorParameter Settings

Hard disk statusrefresh interval(60-3600 seconds)

Description:Refresh interval forhard diskmonitoring.

Value:Value range:60-3600Default value: 60

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 ofThreshold forAlarm Generation:l Warning: 60

l Minor: 70

l Major: 80

l Critical: 90

Default value ofThreshold forAlarm Clearance:l Warning: 55

l Minor: 65

l Major: 75

l Critical: 85



Issue 03 (2010-08-31)


Advanced Setting(%)

Description:Thresholds of all thehard disk usage onthe M2000 server.l When the hard




Value:l If you select

Default value, theM2000 uses thethresholdspecified inDefault valuesetting.

l If you selectCustomize value,the M2000 usescustomizedthresholds ofalarms. Valuerange: 1-99.

l If you selectDisable alarmgeneration,theM2000 doesn'treport alarms ofthe disk partition.

Table 8-3 describes the parameters for monitoring the database of the server.

Table 8-3 Database Monitor


Database MonitorParameter Settings

Database statusrefresh interval(300-3600 seconds)

Description:Interval of databaserefreshing.




8-15


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.

Value:Value range: 1-100Default value:l Warning: 85

l Minor: 90

l Major: 95

l Critical: 98



Issue 03 (2010-08-31)


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 8-4 describes the parameters for monitoring the server services.

Table 8-4 Service Monitor


Services MonitorParameter Settings

Service status refreshinterval (60-3600seconds)

Description:Interval of servicerefreshing.




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

8.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 by default:

– /opt/OMC/var/fileint/syslogs

The save path of the system logs that are periodically exported is as follows:

– /opt/OMC/var/ThresholdExport/Log



Issue 03 (2010-08-31)

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

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



8-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 03 (2010-08-31)

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

8.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 SUN SLS solution or the ATAE clustersystem solution, NEs can be managed by different servers (subareas). On the M2000 client, youcan query different NE subareas.

PrerequisiteYou have logged in to the M2000 client.

ProcedureStep 1 Choose System > 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 No, NE Name, NE Version, and Number of NEsare displayed. In the Statistic dialog box, the subarea information such as IP addresses anddatabase 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 No, NE Name, NE Version, and Number of NEsare displayed. In the Statistic dialog box, the subarea information such as IP addresses anddatabase instance names are displayed.NOTE

You can click Save to save the query results as a file.

For the detailed parameter description, see 8.8.3 Parameters for the NE PartitioningInformation.

----End

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

8.5.1 Querying the M2000 LicenseThis section describes how to query the license file on the M2000 server through the M2000client.



8-21

8.5.2 Updating the M2000 LicenseThis section describes how to replace the M2000 license file on the M2000 server through theclient.


Procedure

Step 1 Choose License > OMC License Management > License Information.

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

8.5.2 Updating the M2000 LicenseThis section describes how to replace the M2000 license file on the M2000 server through theclient.

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

8.6 Check OMC statusOMC check is used to check the status of the M2000. This check also exports check reportsin .html format. The OMC check enables you to find the hidden problems of devices. Thus,severe accidents are avoided and proper operation of current devices is ensured.

Prerequisitel You have logged in to the M2000 successfully.

l You are authorized to perform associated operations.



Issue 03 (2010-08-31)

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 l In No. of periods and No. of run times fields, enter the associatedinformation. Then, perform Step 7.

l In No. of periods and End time fields, enter the associated information.Then, perform Step 7.

Step 7 Click Next. Then, set the information about OMC 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

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

8.7.1 Overview of Integrated Task ManagementThe 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.



8-23

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

8.7.3 Creating a User Timing TaskThis topic describes how to create a user timing task. Parameter setting varies according todifferent tasks.

8.7.4 Modifying a Timing TaskThis section describes how to modify the attributes of a user timing task or a system timing task.

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

8.7.6 Browsing the Information of Timing TasksOn 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.

8.7.7 Viewing the Task ExecutionYou can view the last execution results of a timing task.

8.7.8 Viewing the Task HistoryYou can view the last execution history of a timing task.

8.7.9 Downloading Task Execution TasksYou can download the execution file of NodeB license allocation tasks to a local PC and thencheck the specific resource allocation information.

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

8.7.1 Overview of Integrated Task ManagementThe 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 Centralized TasksThe M2000 classifies managed scheduled tasks into different types according to the taskexecution period, function, and feature.

Tasks Grouped According to the Execution PeriodAccording to the execution period, the M2000 classifies managed scheduled tasks into one-timetasks and periodic tasks. Table 8-5 describes each type of task.



Issue 03 (2010-08-31)

Table 8-5 Tasks grouped according to the execution period

Types of Centralized Tasks Description

Once Refers to a task that is performed only once at aspecified time.

Period Refers to a task that is performed periodically since aspecified time.

Tasks Grouped According to the FunctionAccording to the task function, the M2000 classifies managed scheduled tasks into databasecapacity management tasks, file interface tasks, manual dump tasks, overflow dump tasks, NEInformation Collector (NIC) tasks, synchronization tasks, backup tasks, CM report tasks, CMEtasks, NE health check (NHC) tasks, and other tasks. Table 8-6 describes each type of task.

NOTE

The NEs that support CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM, BSC6900 UMTS andBSC6900 GU.CME tasks are available only after the CME software corresponding to the NE version isinstalled.

Table 8-6 Tasks grouped according to the function


Database Capacity Management The M2000 periodically deletes the data whose storageduration reaches the specified Save Days from thedatabase. Database capacity management tasks ensurethat the database capacity is maintained within a properrange, thus avoiding database faults caused by insufficientdatabase capacity.By default, the maximum Save Days in the database is 90days. The customized value cannot exceed 90 days.The data that can be managed by the M2000 consists ofM2000 operation logs, M2000 system logs, M2000security logs, NE operation logs, NE system logs, NEsecurity logs, alarm/event logs, and performance data.

File Interface Various types of data is periodically exported to aspecified directory on the server. You can save dataoutside the system by using this function. The exporteddata is still stored in the database.The data that can be exported consists of performancedata, configuration data, alarm/event logs, NodeB licensedata, NE upgrade logs, NE inventory data, NE operationlogs, NE security logs, NE system logs, M2000 operationlogs, M2000 system logs, and M2000 security logs.



8-25


NIC NIC tasks provide the Nastar with the NE data requiredfor analyzing system performance, querying and verifyingconfiguration data, scanning uplink frequencies, andoptimizing neighboring cells. NIC tasks are classified intothe following types:l 2G/3G Neighboring Cell Optimization: These tasks are

used for collecting the information about neighboringGSM cells for 3G neighboring relation analysis.

l GSM MR Data Collection: These tasks provide theperformance analysis tool with MR data for networkoptimization analysis. These tasks are controlled by theM2000 license.

l NIC Configuration Data Export: These tasks providethe Nastar with NE configuration data for NEconfiguration data query and verification.

l RTWP Data Collection: These tasks provide the Nastarwith NodeB interference data.

l Daemon NIC Task: These tasks provide the Nastar withvarious types of data, such as the interference data,intra-frequency neighboring cell optimization data,complaint handling data of the CDMA network, and theintra-frequency neighboring cell optimization data andcoverage analysis data of the UMTS network.

l Network Logs Collection: These tasks are used forcollecting the CHR logs of WiMAX BTSs andeNodeBs and neighboring cell relation logs andinterference logs of WiMAX BTSs, thus providing theNastar with the data about abnormal call events,terminal switch events, and base station frequencyinterference.

l Basic NE Information Export: These tasks are used forcollecting basic NE information for the Nastar.

l Frequency Scan: These tasks provide the Nastar withuplink frequency data for uplink interference analysis.These tasks are controlled by the M2000 license.

l Neighboring Cell Optimization: These tasks providethe Nastar with neighboring cell optimization data forneighboring cell analysis. These tasks are controlled bythe M2000 license.



Issue 03 (2010-08-31)


Others Other tasks are classified into the following types:l MML Script: After an MML script is configured, the

M2000 issues the commands in the script in batches ona scheduled basis. Therefore, you need not manuallyissue the commands one by one.

l NodeB License Timed Distribution: The M2000performs scheduled tasks for allocates NodeB licenseresources at a specified time, thus reducing manualoperations.

l PRS Scheduled Task: You can set PRS scheduled taskson the M2000 for the required performance reports.Then, the M2000 collects performance data andgenerates performance reports on a scheduled basis.

l BSC/RNC License Timed Activation: The M2000performs scheduled tasks for downloading andactivating BSC/RNC license files at a specified time,thus reducing manual operations.

l OMC Check: The M2000 checks its devices andgenerates a check report in .html format on a scheduledbasis. Therefore, hidden problems of devices can beidentified and severe accidents can be avoided.

l RSSI Test: The M2000 collects the RSSI values of basestations in a scheduled basis. Therefore, exceptions inthe base station radio frequency (RF) subsystem can beidentified in time and voice quality can be ensured.Performing an RSSI test task consumes a large numberof system resources. Therefore, you are advised toperform such a task only for batch test. Currently, onlyCBTSs support RSSI test tasks.

l Upgrade Checking: The M2000 checks whether theservices are functioning normally after an NE isupgraded.

l Dual Home Auto Consistency Management: TheM2000 checks the data of NEs that have the dual-homing relation periodically or on a scheduled basis,thus enabling you to check NE data consistency and toensure that an MSC server can take over some or alldata on the other MSC server in case of a dual-homingfailover.

l Alarm Check: The M2000 analyzes NE alarm trends,comparisons between alarms, TopN alarm features,alarm maintenance, and fault alarms and generatescheck reports in .html format on a scheduled basis, thusenabling you to analyze network faults in detail.

l PM Synchronization: The M2000 periodicallysynchronizes NE objects to ensure that the performancemeasurement (PM) objects on the M2000 are consistentwith those on NEs.



8-27


l Top Power Test: The M2000 collects the value of thetransmit power on top of the cabinet on a scheduledbasis. Therefore, exceptions in the base station RFsubsystem can be identified in time and voice qualitycan be ensured. Performing a top power test taskconsumes a large number of system resources.Therefore, you are advised to perform such a task onlyfor batch test. Currently, only CBTSs support top powertest tasks.

l NE Software Download: The M2000 instructs an NEto download the corresponding NE mediation softwarefrom the M2000 server periodically or on a scheduledbasis to ensure that the NE version is delivered to theNE at the specified time.

l Script Timer Task: By running the preset HSL scripts,you can perform operations such as modifying NEparameters and obtaining alarm data.

Synchronization Certain data may be missing due to causes such ascommunication interruption. The synchronizationfunction enables you to ensure that the data on theM2000 is consistent with the data on NEs.l The M2000 obtains the latest data from NEs on a

scheduled basis by performing an NE configurationdata synchronization task, NE log synchronization task,NE upgrade log synchronization task, NE inventorydata synchronization task, or alarm scheduledsynchronization task.

l Through a maintenance mode synchronization task, theNE maintenance mode information stored on theM2000 is delivered to NEs on a scheduled basis.

Backup The M2000 allows you to save server data and NE data inbackup files to a specified directory on the M2000 server.The stored server data and NE data can be used forrestoring the system and NEs in case of any data loss orany exception in the system and NEs.Backup tasks are classified into the following types:l NE Backup: The configuration files stored on NEs and

the files that dynamically change during NE operationcan be backed up.

l Server Backup: The dynamic service data of theM2000 system can be backed up. The operating system,however, cannot be backed up.

l NE License Backup: Only the currently activatedlicense files on NEs can be backed up.



Issue 03 (2010-08-31)


CM Report The M2000 periodically exports configuration reports infiles to a specified directory on the M2000 server. You canuse this function to save data outside the system. Theexported data is still stored in the database.The types of reports that can be exported consist of RANreport, core network resource report, NE report, NEstatistic report, and NE link report.

CME CME tasks are classified into the following types:l CME Upload: The M2000 uploads the selected NE

configuration data to the CME server periodically or ona scheduled basis to ensure that the CME obtains thelatest NE data for data configuration.

l Cell Parameters Compare: The M2000 compares theparameters in the current data area with the defaultparameters in the CME configuration template and thenexports the comparison results to the default path.

l Cell Consistency Check: The M2000 checks whetherthe data in the current data area complies with theselected check rules. Currently, the rules for checkingunidirectional neighboring cells and cell consistencyare provided.

l Current Area Export: The M2000 exports the requireddata from the current data areas through northboundinterfaces, thus facilitating current data areamanagement.

NHC Pre-alarm Handling Task: The M2000 checks whether themediation or the current NE is normal and generates areport on a scheduled basis.

Tasks grouped according to the featureAccording to the task feature, the M2000 classifies managed scheduled tasks into systemscheduled tasks and user scheduled tasks. Table 8-7 describes each type of task.

Table 8-7 Tasks grouped according to the feature


System Scheduled Task System scheduled tasks are the tasks required for the normaloperation of the M2000 system. For details about thesetasks, see System Scheduled Tasks.

User Scheduled Task User scheduled tasks are the tasks customized to meet therequirements of network maintenance. For details aboutthese tasks, see User Scheduled Task.



8-29

System Scheduled Tasks

System scheduled tasks are created during the installation or upgrade of the M2000 system. TheCreator parameter of each system scheduled task is displayed as OMC.

The M2000 uses to identify system scheduled tasks and uses to identify user scheduledtasks.

NOTE

l Only users in the administrator group can manage and view system scheduled tasks.

l System scheduled tasks cannot be copied. Only some parameters of system scheduled tasks can bemodified. These parameters, however, cannot be deleted.

l In system scheduled tasks, database capacity management tasks cannot be suspended or canceled,while synchronization tasks and backup tasks can be suspended or canceled. You can also set thetime when a synchronization task or backup task will be suspended or canceled.

For details about system scheduled tasks, see Table 8-8.

Table 8-8 Description of system scheduled tasks

Task Type Task Name Reference

Database CapacityManagement

Alarm/Event LogDump

For details, see 8.8.17 Parameters forModifying a Database CapacityManagement Task.

Performance Data

NE Operation Log

NE Security Log

NE System Log

NM Operation LogDump

NM System LogDump

NM Security LogDump

File Interface Performance DataExport

For details, see 8.8.18 Parameters forModifying the Export of PerformanceData.

Configuration DataExport

For details, see 8.8.19 Parameters forModifying a Configuration Data ExportTask.

NodeB License DataExport

For details, see 8.8.14 Parameters for SettingCommon Parameters for Timing Tasks.

NE Upgrade LogExport

For details, see 8.8.39 Parameters forCreating/Modifying/Copying the Export ofNE Upgrade Log.



Issue 03 (2010-08-31)


NE Operation LogExport

For details, see 8.8.20 Parameters forModifying the Export of NE Logs.

NE System LogExport

NE Security LogExport

Inventory Data Export For details, see 8.8.21 Parameters forModifying the Export of Inventory Data.

Alarm/Event LogExport

For details, see 8.8.22 Parameters forModifying an Alarm/Event Log ExportTask.

NM Operation LogExport

For details, see 8.8.23 Parameters forModifying the Export of M2000 Logs.

NM System LogExport

NM Security LogExport

Overflow Dump Alarm OverflowDump

For details, see Parameters for Setting Alarm/Event Overflow Dump.

Event Overflow Dump

Manual Dump Alarm Manual Dump For details, see Parameters for DumpingAlarms/Events Manually.

Event Manual Dump

NIC NIC ConfigurationData Export

For details, see 8.8.19 Parameters forModifying a Configuration Data ExportTask.

NE Basic InformationExport

For details, see 8.8.24 Parameters forModifying NE Basic Information ExportTask.

Network LogsCollection

For details, see Parameters for ModifyingNetwork Log Data Collection Tasks.

Other PM ObjectSynchronization


Synchronization NE ConfigurationData Synchronization

For details, see 8.8.25 Parameters forModifying the Synchronization of NEConfiguration Data .

NE LogSynchronization




8-31


Inventory DataSynchronization

For details, see 8.8.26 Parameters forModifying the Synchronization ofInventory Data.

AlarmSynchronization


Maintenance ModeSynchronization


NE Upgrade LogSynchronization


Backup Server Backup For details, see 8.8.27 ParameterDescription: Modifying a Data BackupTask of the M2000.

User Scheduled TaskUser scheduled tasks are tasks customized to meet the requirements of network maintenance.

l You can create, modify, delete, copy, suspend, or restore user scheduled tasks.

l The M2000 uses to identify system scheduled tasks and uses to identify userscheduled tasks.

For details about user scheduled tasks, see Table 8-9.

NOTE

The NEs that support CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM, BSC6900 UMTS andBSC6900 GU. CME tasks are available only after the CME software corresponding to the NE version isinstalled.

Table 8-9 Description of user scheduled tasks

TaskType

Task Name Description Reference

Backup NE Backup The M2000 saves NE data inbackup files to a specifieddirectory on the serverperiodically or on a scheduledbasis. The backup files are usedfor restoring NEs in case of anydata loss or NE exception. Youcan back up the data of the NEson the entire network, NEs of aspecified type, or specified NEs.

For details, see 8.8.28Parameters for Creating/Modifying/Copying NEBackup.



Issue 03 (2010-08-31)

TaskType


NE LicenseBackup

The activated license files on NEsare backed up and uploaded to aspecified directory on theM2000 server on a scheduledbasis. The license files are usedfor restoring NEs in case of anylicense file loss or NE exception.

None.

CMReport

RAN ReportExport

The M2000 periodically exportsconfiguration reports in files to aspecified directory on theM2000 server. You can use thisfunction to save data outside thesystem. The exported data is stillstored in the database.

For details, see 8.8.30Parameters for Creating,Modifying, or Copying aConfiguration ReportExport Task.

Core NetworkResourceReport Export

NE ReportExport

NE StatisticReport Export

Link ReportExport

NIC 2G/3GNeighboringCellOptimization

These tasks are used forcollecting the information aboutneighboring GSM cells for 3Gneighboring relation analysis.This task is created on the Nastar.You only need to view the taskprogress on the M2000.

None.

GSM MR DataCollection

These tasks provide theperformance analysis tool withMR data for networkoptimization analysis. Thesetasks are controlled by theM2000 license.

For details, see Parametersfor Creating a GSM MRData Collection Task.

RTWP DataCollection

These tasks provide the Nastarwith NodeB interference data.This task is created on the Nastar.You only need to view the taskprogress on the M2000.

None.



8-33

TaskType


Daemon NICTask

These tasks provide the Nastarwith various types of data, suchas the interference data, intra-frequency neighboring celloptimization data, complainthandling data of the CDMAnetwork, and the intra-frequencyneighboring cell optimizationdata and coverage analysis dataof the UMTS network.This task is created on the Nastar.You only need to view the taskprogress on the M2000.

None.

FrequencyScan

These tasks provide the Nastarwith uplink frequency data foruplink interference analysis.These tasks are controlled by theM2000 license.

For details, see Parametersfor Creating a Task ofCollecting the UplinkARFCN Data.

NeighboringCellOptimization

These tasks provide the Nastarwith neighboring celloptimization data forneighboring cell analysis. Thesetasks are controlled by theM2000 license.

For details, see Creating aData Collection Task forNeighbor CellOptimization.

Other MML Script After an MML script isconfigured, the M2000 issues thecommands in the script in batcheson a scheduled basis. Therefore,you need not manually issue thecommands one by one.

For details, see 8.8.29Parameters for Creating/Modifying/CopyingMML Command Script.

NodeB LicenseTimedDistribution

The M2000 performs scheduledtasks for allocates NodeB licenseresources at a specified time, thusreducing manual operations.

For details, see 8.8.32Parameters for Creating/Modifying/CopyingScheduled NodeBLicense Allocation Tasks.

PRS ScheduledTask

You can set PRS scheduled taskson the M2000 for the requiredperformance reports. Then, theM2000 collects performance dataand generates performancereports on a scheduled basis.

For details, see 8.8.31Parameter Description:Creating, Viewing, orModifying a ScheduledReport Task.



Issue 03 (2010-08-31)

TaskType


BSC/RNCLicense TimedActivation

The M2000 performs scheduledtasks for downloading andactivating BSC/RNC license filesat a specified time, thus reducingmanual operations.

For details, see 8.8.33Parameters for Creating/Modifying/CopyingScheduled BSC or RNCLicense Allocation Tasks.

OMC Check The M2000 checks its devicesand generates a check reportin .html format on a scheduledbasis. Therefore, hiddenproblems of devices can beidentified and severe accidentscan be avoided.

For details, see 8.8.45Parameters for SelectingObjects for OMC Check.

RSSI Test The M2000 collects the RSSIvalues of base stations in ascheduled basis. Therefore,exceptions in the base stationradio frequency (RF) subsystemcan be identified in time andvoice quality can be ensured.Performing an RSSI test taskconsumes a large number ofsystem resources. Therefore, youare advised to perform such a taskonly for batch test. Currently,only CBTSs support RSSI testtasks.NOTE

The portals of the RSST Test taskare as follows:

l Maintenance > TaskManagement.

l Maintenance > RFPerformance Test > RSSITest.

For details, see 8.8.35Parameters for Creating/Modifying/Copying anRSSI Test Task.

UpgradeChecking

The M2000 checks whether theservices are functioning normallyafter an NE is upgraded.

For details, see Parametersfor Creating an NEUpgrade VerificationTask.

NE SoftwareDownload

NE mediation software isdownloaded from the M2000server to a specified NEperiodically or on a scheduledbasis to ensure that the NEversion can be delivered to theNE at the specified time.

For details, see 8.8.36Parameters for Creating/Modifying/CopyingSoftware Download.



8-35

TaskType


Dual HomeAutoConsistencyCheckManagement

The M2000 checks the data ofNEs that have the dual-homingrelation periodically or on ascheduled basis. Therefore, youcan ensure that an MSC servercan take over some or all data onthe other MSC server in case of adual-homing failover.

For details, see 8.8.37Parameters for Creating/Modifying/Copying aDual-Homing AutoConsistency Check Task.

Alarm Check The M2000 analyzes NE alarmtrends, comparisons betweenalarms, TopN alarm features,alarm maintenance, and faultalarms and generates checkreports in .html format on ascheduled basis, thus enablingyou to analyze network faults indetail.

For details, see Parametersfor Setting Special AlarmCheck Tasks.

Top PowerTest

The M2000 collects the value ofthe transmit power on top of thecabinet on a scheduled basis.Therefore, exceptions in the basestation RF subsystem can beidentified in time and voicequality can be ensured.Performing a top power test taskconsumes a large number ofsystem resources. Therefore, youare advised to perform such a taskonly for batch test. Currently,only CBTSs support top powertest tasks.NOTE

The portals of the Top Power Testtask are as follows:

l Maintenance > TaskManagement.

l Maintenance > RFPerformance Test > Top PowerTest.

For details, see 8.8.34Parameters for Creating/Modifying/Copying aTask for Testing BTSCabinet-Top Power.

Script TimerTask

By running the preset HSLscripts, you can performoperations such as modifying NEparameters and obtaining alarmdata.

For details, see 8.8.38Parameters for Creating/Modifying/Copying anHSL Script Task.



Issue 03 (2010-08-31)

TaskType


CME CME Upload You can set a specified interval ora time to upload user-selected NEconfiguration data to the CMEserver. Therefore, the CME canobtain the latest NE data for dataconfiguration.

For details, see 8.8.40Parameters for Creating/Modifying/Copying aCME Upload Task.

CellParametersCompare

The M2000 compares theparameters in the current dataarea with the default parametersin the CME configurationtemplate and then exports thecomparison results to a specifiedpath.

For details, see 8.8.41Parameters for Creating/Modifying/Copying CellParameters CompareTask.

CellConsistencyCheck

The M2000 checks whether thedata in the current data areacomplies with the selected checkrules. Currently, the rules forchecking unidirectionalneighboring cells and cellconsistency are provided.

For details, see 8.8.42Parameters for Creating/Modifying/Copying CellConsistency Check Task.

Current AreaExport

The M2000 exports the data inthe current data area throughnorthbound interfaces, thusfacilitating the management ofthe current data area.

For details, see 8.8.43Parameters for Creating/Modifying/Copying aCME Current AreaExport Task.

NHC Pre-alarmHandling Task

The M2000 checks whether themediation or the current NE isnormal and exports a report on ascheduled basis.

None.

Task Scheduling ParametersThe task scheduling parameters are the parameters related to the task execution type, task starttime, task execution period, and execution times.

Table 8-10 describes the task scheduling parameters.



8-37

Table 8-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 unit of Period can be month, week, day, hour, or minute.Second is not supported. The supported units of Period varyaccording to the task type.

l The task execution period can be represented by month, week, day,hour, and minute. Second is not supported. The supported unitsvary according to the task type.

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.

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 five states: idle, running, suspend, archived and finished.

The states of a scheduled task change with different operations. For details, see Figure 8-7.



Issue 03 (2010-08-31)

Figure 8-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

skS

uspe

nd a

tim

ing

task

Res

tore

a ti

min

g ta

sk

Creating a timing task

Deleting a timing task

Suspend

Archived

Finished

Running

Term

inat

e a

CM

E ta

skTerminate a CME task

Term

inat

e a

CM

E ta

skDelete

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.

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 user timing task. Users except admin can delete only the tasks createdby themselves. The admin can delete the tasks created by all users.

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



8-39

Procedure

Step 1 Choose Maintenance > Task Management.

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 FilterTask dialog box is displayed.

2. Set the User Name, Category, Task State, and Last RunResult as the filtering conditions. For detailed parameterdescription, refer to 8.8.12 Parameters for Setting TaskFilter Conditions.

Step 3 Click OK.

----End

8.7.3 Creating a User Timing TaskThis topic 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.



Issue 03 (2010-08-31)

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.

Step 3 In the New Task or Copy Task dialog box, set the parameters of the created user timing task.

Option Description

Parameter Setting

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 then selecta periodic execution mode, namely, Run times or End time.

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

8.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 Scheduled Tasks and User Scheduled Task.



8-41

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.

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

8.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 TasksTo 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 suspendingSelect 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



Issue 03 (2010-08-31)

Resuming Timing Tasks

You can resume a suspended task. After that, the task becomes idle and is ready to be dispatchedby the system.


l At least one suspended scheduled task exists.

Context

Only 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 resuming

Select a task in the task list in the right pane. Right-click the task and select Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and then specifythe time. Click OK.

----End

Setting Time of Timing Tasks

You can set an automatic suspend time or an automatic restore time for a scheduled task. In 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 idlestatus 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.



8-43

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.

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 8.8.44Parameters 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.




Issue 03 (2010-08-31)

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.

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

8.7.6 Browsing the Information of Timing TasksOn 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

l Part of periodic tasks support the function of downloading the log file of task execution results fromthe server. The downloaded log file is saved to the client. Thus, the user can view the history executionresults of periodic tasks at any time:

1. Select the tasks that support log file download, and then click Save Log.

2. In the Selecting the Logs to Be Saved dialog box, select the log file to be saved, and then clickOK.

3. In the Select Folder dialog box, select the path for saving the log file, and then click Select.



8-45

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

8.7.7 Viewing the Task ExecutionYou can view the last execution results of a timing task.



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 Information area.

----End

8.7.8 Viewing the Task HistoryYou can view the last execution history of a timing task.



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 sub-tasks of CME tasks.



Issue 03 (2010-08-31)

Procedure



l Select any task displayed on the right pane.

l Right click on the selected task and select View History to view the history information.

NOTE

Only 100 history records can be displayed on the View History Information window.

----End

8.7.9 Downloading Task Execution TasksYou can download the execution file of NodeB license allocation tasks to a local PC and thencheck the specific resource allocation information.


l NodeB license allocation tasks are available in the system.

Procedure


Step 2 In the navigation tree, choose Task Type > Other > NodeB License Timed Distribution.

Step 3 In the task list on the right, right-click a task, and then choose Download Task File from theshortcut menu to download the license resource allocation file set in the task to a local PC.

----End

8.7.10 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 8-11.



8-47

Table 8-11 Allowable operations for different task types

Task Type Allowable Operation

CME , iSStar ScriptExecutor or Pre-alarmHandling 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.

Health Check task You can download the result file of the selected task. Result filesof multiple tasks can be downloaded concurrently.

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, iSStar Script Executor or Pre-alarm Handling 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 03 (2010-08-31)

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.

OMC Check or Alarm 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.



8-49

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

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

8.8.1 Interface Description: Managing Scheduled TasksThis section describes the Task Management window and relevant parameters. You can referto this part when performing related operations.

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

8.8.3 Parameters for the NE Partitioning InformationThis section describes the related parameters in the Query NE Subarea dialog box. You canrefer to the these parameters when you check the NE partitioning information.

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

8.8.5 Parameters for Setting Monitoring Parameters of the M2000 ServerThis topic describes the parameters of system monitor settings. You can use these parameterswhen you set the server thresholds.

8.8.6 Parameters for Monitoring the M2000 Server Service StatusThis topic 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

8.8.7 Parameters for Monitoring the M2000 Server Process StatusThis topic 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.

8.8.8 Parameters for Monitoring the M2000 Server Hard Disk StatusThis topic describes the parameters of the query result displayed in the Hard Disk Monitor tab.You can use these parameters when you monitor the M2000 server hard disk status.

8.8.9 Parameters for Monitoring the M2000 Server Database Status



Issue 03 (2010-08-31)

This topic describes the parameters of the query result displayed in the Database Monitor tab.You can use these parameters when you monitor the M2000 server database status.

8.8.10 Parameters for Monitoring the M2000 Server StatusThis topic describes the parameters of the query result displayed in the Server Monitor tab.You can use these parameters when you monitoring the M2000 server status.

8.8.11 Parameters for Viewing the Information about M2000 Server ComponentsThis topic describes the parameters on the Component Information tab page. You can use theseparameters when you view the information about M2000 server components.

8.8.12 Parameters for Setting Task Filter ConditionsThis topic describes the parameters in the Filter Task dialog box. When you set filter conditionsfor a task list, you can refer to this topic.

8.8.13 Parameters for Setting the Common Information for Creating or Replicating a TaskThis topic describes the parameters on the common information panel in the New Task or CopyTask dialog box. When you create or copy a task, you can refer to this topic.

8.8.14 Parameters for Setting Common Parameters for Timing TasksThis topic describes the parameters on the Common Parameters tab on property panels of alltiming tasks except the CME loading task. When you modify a timing task, you can refer to thistopic.

8.8.15 Parameters for Setting the Time When a Periodic Task Is Created or CopiedThis topic describes the time parameters in the New Task or Copy Task dialog box. When youset the time of a periodic task, you can refer to this topic.

8.8.16 Parameters for Setting the Time When a One-Time Task Is Created or CopiedThis topic describes the time parameter in the New Task Copy Task dialog box. When youmodify the time of a one-time task, you can refer to this topic.

8.8.17 Parameters for Modifying a Database Capacity Management TaskThis section describes the parameters of database capacity management tasks. You can refer tothis part and set relevant parameters when modifying a database capacity management task.

8.8.18 Parameters for Modifying the Export of Performance DataThis section describes the parameters for exporting performance data, which can be yourreference during the parameter modification.

8.8.19 Parameters for Modifying a Configuration Data Export TaskThis section describes the parameters of NIC Configuration Data Export and ConfigurationData Export tasks. You can refer to this part when modifying parameters.

8.8.20 Parameters for Modifying the Export of NE LogsThis section describes the parameters for exporting NE logs and can be taken as reference duringthe parameter modification.

8.8.21 Parameters for Modifying the Export of Inventory DataThis section describes the parameters for exporting inventory data, which can be your referenceduring the parameter modification.

8.8.22 Parameters for Modifying an Alarm/Event Log Export TaskThis describes the parameters for modifying an alarm/event log export task.

8.8.23 Parameters for Modifying the Export of M2000 LogsThis describes the parameters for exporting M2000 logs and can be taken as reference duringthe parameter modification.



8-51

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

8.8.25 Parameters for Modifying the Synchronization of NE Configuration DataThis section describes parameters used for synchronization of NE configuration data. Whenmodifying the parameters, you can set the parameters by referring to the information describedin this section.

8.8.26 Parameters for Modifying the Synchronization of Inventory DataThis section describes parameters used for synchronization of inventory data. When modifyingthe parameters, you can set the parameters by referring to the information described in thissection.

8.8.27 Parameter Description: Modifying a Data Backup Task of the M2000This section describes the parameters related to data backup tasks of the M2000. You can referto the description when modifying a data backup task.

8.8.28 Parameters for Creating/Modifying/Copying NE BackupThis section describes the parameters related to NE backup tasks. You can refer to this part whencreating or modifying NE backup tasks.

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

8.8.30 Parameters for Creating, Modifying, or Copying a Configuration Report Export TaskThis topic describes the parameters involved in the export of RAN reports, CN resource reports,NE reports, NE statistic reports, and NE link reports. When creating, modifying, or copying anexport task of these reports, you can refer to this topic and perform relevant operations.

8.8.31 Parameter Description: Creating, Viewing, or Modifying a Scheduled Report TaskThis section describes the parameters for setting a scheduled report task. You can refer to thedescription in this section when creating, querying, or modifying a scheduled task.

8.8.32 Parameters for Creating/Modifying/Copying Scheduled NodeB License Allocation TasksThis section describes the parameters of scheduled NodeB license allocation tasks. You can referto this section when creating or modifying scheduled NodeB license allocation tasks.

8.8.33 Parameters for Creating/Modifying/Copying Scheduled BSC or RNC License AllocationTasksThis section describes the parameters of scheduled BSC or RNC license allocation tasks. Youcan refer to this section when creating or modifying scheduled BSC or RNC license allocationtasks.

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

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

8.8.36 Parameters for Creating/Modifying/Copying Software DownloadThis 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.



Issue 03 (2010-08-31)

8.8.37 Parameters for Creating/Modifying/Copying a Dual-Homing Auto Consistency CheckTaskThis section describes the parameters for creating, modifying, or copying a dual-homing autoconsistency check task.

8.8.38 Parameters for Creating/Modifying/Copying an HSL Script TaskThis section describes the parameters of HSL script tasks. You can refer to this part and setrelevant parameters when creating or modifying an HSL script task.

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

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

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

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

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

8.8.44 Parameters for Setting Time of Timing TasksThis section describes the parameters of time for automatic suspending and automatic resumingtiming tasks

8.8.45 Parameters for Selecting Objects for OMC CheckThis part describes the extended parameters for selecting objects for OMC check. You can referto this part when creating device check tasks.

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

8.8.1 Interface Description: Managing Scheduled TasksThis section describes the Task Management window and relevant parameters. You can referto this part when performing related operations.

After you log in to the server, the Task Management window is displayed, as shown in Figure8-8. For the description of Figure 8-8, see Table 8-12.



8-53

Figure 8-8 Task Management window

Table 8-12 Description of the Task Management window

No. Name Description

(1) Navigation tree You can locate the object of a scheduledtask through the navigation tree.

(2) Task result informationpanel

After a task is completed, the task result isdisplayed on the task result informationpanel. You can browse through the resultof the latest task on the panel. Only theresult of the currently selected task isdisplayed on the panel. If multiple tasks areselected in the task list, the result of onlythe firstly selected task is displayed.

(3) Button panel The buttons used for performing centraltask management are available on thebutton panel.

(4) Task list You can browse through the scheduledtasks existing on the server and theirdetails. In the task list, different colorsindicate different task statuses. Gray:complete; Orange: suspended; Blue:active; White: idle. After you select a taskin the list, the color of the task becomesdarker than before.



Issue 03 (2010-08-31)

8.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 8-9 shows the interface.

Figure 8-9 M2000 Log Information Collector interface

8.8.3 Parameters for the NE Partitioning InformationThis section describes the related parameters in the Query NE Subarea dialog box. You canrefer to the these parameters when you check the NE partitioning information.



8-55

Parameter DescriptionParameter Description

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.

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

ParametersParameter Description

Find Description:Find the matched license item after you enter

a license name and then click .NOTE

If a matched record is found, the row of the recordis displayed and automatically selected.

Resource ControlItem

Resource Description:Names of authorization items.

License Capacity Description:Capacity defined in the license.

License Consumption Description:Capacity of the licenses consumed.



Issue 03 (2010-08-31)


Time of LicenseConsumptionOverflow

Description:Expiry time of each authorization item.

Detailed Information Description:View details of authorization items.

Server ID Description:Local server ID and authorization server IDdisplayed after you click Server ID

Update License Description:Click the button to update license.

Export License Description:Export a license to a file on the local clientfor future maintenance and browse.

Function ControlItem

Function Description:Names of authorization items.

Supported or Not Description:Whether a function supports license control.

8.8.5 Parameters for Setting Monitoring Parameters of the M2000Server

This topic describes the parameters of system monitor settings. You can use these parameterswhen you set the server thresholds.



8-57

Parameters














Issue 03 (2010-08-31)












8-59














l Minor: 70

l Major: 80

l Critical: 90


l Minor: 65

l Major: 75

l Critical: 85



Issue 03 (2010-08-31)


Advanced Setting(%)

















8-61








l Minor: 90

l Major: 95

l Critical: 98



Issue 03 (2010-08-31)


Advanced Setting(%)







– Minor: 90

– Major: 95

– Critical: 98










8-63




monitor client by

or .NOTE




is displayed.

l You can double-



8.8.6 Parameters for Monitoring the M2000 Server Service StatusThis topic 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:The name of a service.

Process Name Description:The name of a process.

Description Description:The description information of functions and interfacesprovided by a service.

Status Description:The status of a service.



Issue 03 (2010-08-31)

Name Description

Startup Mode Description:The service start mode, including Automatic, Manual, andDisable. The Disable mode is available only for stoppedservices.

Start Time Description:The time that the service is started.

Server Name Description:The name of the server.

8.8.7 Parameters for Monitoring the M2000 Server Process StatusThis topic 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.


Process Name Description:Name of a process.

Process ID Description:ID of a process.

Handle Count 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.This parameter is displayed when the database is theSybase database.

Thread Number Description:Number of threads generated by a process.



8-65

8.8.8 Parameters for Monitoring the M2000 Server Hard Disk StatusThis topic describes the parameters of the query result displayed in the Hard Disk Monitor tab.You can use these parameters when you monitor the M2000 server hard disk status.


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.

8.8.9 Parameters for Monitoring the M2000 Server Database StatusThis topic describes the parameters of the query result displayed in the Database Monitor tab.You can use these parameters when you monitor the M2000 server database status.


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.



Issue 03 (2010-08-31)

Name Description

Data Space Usage (%) Description:Usage rate of the used data space and total data space.This parameter is displayed when the database is theSybase database.

Total Log Space (MB) Description:It refers to the space allocated to each database log ofthe M2000.This parameter is not displayed when the database isthe Oracle database.

Free Log Space (MB) Description:It refers to the unused disk space allocated to databaselogs.This parameter is displayed when the database is theSybase database.

Log Space Usage (%) Description:It is calculated by the following formula: Log UsedRate = (Total Log Space - Free Log Space)/Total LogSpace x 100%.This parameter is displayed when the database is theSybase database.

Total Data Space Usage (%) Description:Usage rate of the used database storage space and totaldatabase space.This parameter is displayed when the database is theOracle database.

Table Space Usage (%) Description:Usage rate of the used table space of the database andtotal table space.This parameter is displayed when the database is theOracle database.

Status Description:Database status, including normal and abnormal. If thedatabase usage is more than or equal to the threshold,the system displays Abnormal.

8.8.10 Parameters for Monitoring the M2000 Server StatusThis topic describes the parameters of the query result displayed in the Server Monitor tab.You can use these parameters when you monitoring the M2000 server status.



8-67


Server Name Description:Name of the M2000 server.

Server Status Description:Status of the M2000 server, including Active, Slave andStandby.

OS Description:Operating system of the server.

Total Physical Memory (MB) Description:Total physical memory space.

Free Physical Memory (MB) Description:Remaining physical memory space.

Total Swap Memory (MB) Description:Total virtual memory space.

Free Swap Memory (MB) Description:Remaining virtual memory space.

CPU Usage (%) Description:CPU usage.

Memory Usage (%) Description:The usage of the total memory space (including physicalmemory and virtual memory).

8.8.11 Parameters for Viewing the Information about M2000 ServerComponents

This topic describes the parameters on the Component Information tab page. You can use theseparameters when you view the information about M2000 server components.


Component Description:Component name of the M2000 server.

Version Description:Component version of the M2000 server.



Issue 03 (2010-08-31)

Name Description

Description Description:Component description of the M2000 server.

8.8.12 Parameters for Setting Task Filter ConditionsThis topic describes the parameters in the Filter Task dialog box. When you set filter conditionsfor a task list, you can refer to this topic.

Parameters


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.

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.



8-69


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 lostcaused by improper service or sudden power cut. Thus, afterrecovery, the previous execution result cannot be determined.

8.8.13 Parameters for Setting the Common Information for Creatingor Replicating a Task

This topic describes the parameters on the common information panel in the New Task or CopyTask dialog box. When you create or copy a task, you can refer to this topic.

ParametersName Description Settings

Task Name Description:Refers to the name of a timing task.

Value:l This parameter

allows a maximumof 60 characters.

l This parameter isexclusive and cannotbe empty.

l These characters arecase sensitive.

Task Type Description:Refers to the task type of a timing task.

Setting method:In the Task Typenavigation tree, selectthe task to be created.

Run Type Once Description:Select this check box and the system runsthe tasks that you create only once at thespecial time.

-



Issue 03 (2010-08-31)


Period Description:Select this check box and the system runsthe tasks that you create periodically.

-

8.8.14 Parameters for Setting Common Parameters for Timing TasksThis topic describes the parameters on the Common Parameters tab on property panels of alltiming tasks except the CME loading task. When you modify a timing task, you can refer to thistopic.

ParametersParameter Description Value Range

Task Name Description:Refers to the name of a timing task

Value:l A maximum of 60

charactersl Unique and not null

l Case sensitive

Run Type Once Description:If you select this option, thesystem runs the created task onceat the defined time point.

-

Period Description:If you select this option, thesystem runs the created taskperiodically.

-

Start time Description:This parameter sets the time forstarting a task. The start timeshould be later than the timedisplayed on the server.

Value:If you have selected RunAt Once, the StartTime parameter isinvalid. The task isperformed immediatelyafter the related settingsare complete.



8-71

Parameter Description Value Range

No. of period Description:Interval between periodic tasks. Ithas two enlistments: unit andduration.

Value:l The period can be

represented in eitherof the following units:minutes, hours, days,weeks, months. Theperiod, however,cannot be representedin seconds. Thesupported units ofPeriod vary accordingto the task type.

l The value range forperiod should be asfollows: Minute (1-366 x 24 x 60), Hour(1 - 366 x 24), Day (1- 366), Week (1 - 52),Month (1 - 12).

No. of run times Description:This parameter indicates the timesthat a periodic task is executed.

Value:0-65535NOTE

l 0 indicates that thenumber of times forexecuting periodictasks is not restricted.

l This parameter isdisplayed in theAttribute dialog boxonly after you set itwhen creating andcopying a periodic task.

End time Description:End time of a periodic task.

Value:Later than Start time,and earlier than12/31/2038 23:59:59.NOTE

This parameter isdisplayed in theAttribute dialog box onlyafter you set it whencreating and copying aperiodic task.



Issue 03 (2010-08-31)

8.8.15 Parameters for Setting the Time When a Periodic Task IsCreated or Copied

This topic describes the time parameters in the New Task or Copy Task dialog box. When youset the time of a periodic task, you can refer to this topic.

ParametersParameter Description Settings

TimeSetting

Start time Description:Start time of a periodictask.

Setting method:You can set this parameterwith the following twomethods:l Enter the time in time

textbox (you can also

use the spin button to adjust the time).

l Click to select thedate and time in theDate/Time Selectiondialog box.

DST Description:This parameter indicateswhether time use DST.This parameter isconfigurable only whenthe current time is DST.

-

PeriodSetting

No. of period Description:Interval of periodic tasks.The value consists ofnumerals and units.

Value:l The period can be

represented in either ofthe following units:minutes, hours, days,weeks, months. Theperiod, however,cannot be representedin seconds. Thesupported units ofPeriod vary accordingto the task type.

l The value range forperiod should be asfollows: Minute (1-366 x 24 x 60), Hour (1- 366 x 24), Day (1 -366), Week (1 - 52),Month (1 - 12).



8-73

Parameter Description Settings

No. of run times Description:Number of times forexecuting periodic tasks.

Value:0 - 65535NOTE

0 indicates that the numberof times for executingperiodic tasks is notrestricted.

End time Description:End time of a periodictask.

Setting method:You can set this parameterwith the following twomethods:l Enter the time in time

textbox (you can also


l Click to select thedate and time in theDate/Time Selectiondialog box.

Value:Later than Start time andearlier than 12/31/203823:59:59.

8.8.16 Parameters for Setting the Time When a One-Time Task IsCreated or Copied

This topic describes the time parameter in the New Task Copy Task dialog box. When youmodify the time of a one-time task, you can refer to this topic.



Issue 03 (2010-08-31)

ParametersName Description Settings

Time Setting Description:Start time of a one-timetask.

Setting method:You can set the time with the following twomethods:l Enter the time in Start Time (you can also


l Click to select the date and time in theDate/Time Selection dialog box.

NOTEIf the Run At Once check box is selected, the taskis performed immediately after you set theparameters.

DST Description:This parameter indicateswhether time use DST.This parameter isconfigurable only whenthe current time is DST.

-

8.8.17 Parameters for Modifying a Database Capacity ManagementTask

This section describes the parameters of database capacity management tasks. You can refer tothis part and set relevant parameters when modifying a database capacity management task.

Parameter Descriptionl Parameters of Alarm/Event Log Dump Tasks

l Parameters of Performance Data Tasks

l Parameters of NE Log Tasks

l Parameters of NM Log Dump Tasks

Table 8-17 Parameters of Alarm/Event Log Dump Tasks

Parameter Value Range Description

File compressionafter 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.



8-75


File type 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.

File path None. Refers to the path for saving exported data. Thesave path is specified by the server and cannotbe modified. Alarm/event log dump tasks: /export/home/omc/var/ThresholdExport/FM.

Storage period indatabase

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 Storageperiod

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 count 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 8-18 Parameters of Performance Data Tasks


Export Data Selected from thedrop-down list

If you select Yes, the system automaticallydeletes the expired performance data, and theparameters related to file export becomeinvalid. If you select No, the system exports theexpired performance data according to thepreset file export parameters.



Issue 03 (2010-08-31)


Compress FileAfter Export



File Format Selected from thedrop-down list

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 Days in theDatabase



File Size Unit: MBDefault value: 1,024Value range: 200-2048



File Hold Days Unit: dayDefault value: 15Value range: 3-30


File Sum Number of filesDefault value: 1,000Value range: 200-2000


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.



8-77

Table 8-19 Parameters of NE Log Tasks


Compress FileAfter Export



File Format Selected from thedrop-down list

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.

Hold Days in theDatabase



File Size Unit: MBDefault value: 1,024Value range: 200-2048



File Hold Days Unit: dayDefault value: 15Value range: 3-30


File Sum Number of filesDefault value: 1,000Value range: 200-2000


Table 8-20 Parameters of NM Log Dump Tasks







Issue 03 (2010-08-31)


File type Selected from thedrop-down list

Refers to the format of the file that saves theexported data. M2000 log database capacitymanagement tasks support .xml and .csv files.

File path Default path: /opt/OMC/var/ThresholdExport/Log

Refers to the path for saving exported data.

Storage period indatabase (days)



Export FileManagement

l Unit: day. Valuerange: 3-30. Defaultvalue: 15

l Unit: file. Valuerange: 200-1000.Default value: 1000

l Unit: M. Valuerange: 200-2048.Default value: 1024

l Only hold XX Day(s): In the dumpdirectory, the log files older than this periodare deleted.

l Only hold XX File(s): In the dumpdirectory, if the number of log files exceedsthe value of this parameter, the M2000deletes the oldest dump files until thenumber of log files in this directory becomesless than the value of this parameter.

l Only hold XX M of file: In the dumpdirectory, if the total size of log files exceedsthe value of this parameter, the M2000deletes the oldest dump files until the totalsize of log files in this directory becomesless than the value of this parameter.

8.8.18 Parameters for Modifying the Export of Performance DataThis section describes the parameters for exporting performance data, which can be yourreference during the parameter modification.

Table 8-21 lists the extended parameters.

Table 8-21 Description of extended parameters


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

The data of a task is deleted fromthe server after the storageduration expires.



8-79


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

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.



Issue 03 (2010-08-31)


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

If the result query templates havingthe same name exist on onemeasurement period tab page, and ifthe performance measurementresults are to be exported bytemplate name according to thesetting in the configuration file ofthe tool for exporting performancemeasurement results collected bythe M2000, the result files that areexported on the basis of thetemplates sharing the same namewill replace each other when youselect a template sharing the samename with other templates. To avoidfile replacement, you need tochange the names of the result querytemplates or modify the setting inthe configuration file so thatperformance measurement resultsare exported by template ID.

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.

8.8.19 Parameters for Modifying a Configuration Data Export TaskThis section describes the parameters of NIC Configuration Data Export and ConfigurationData Export tasks. You can refer to this part when modifying parameters.

Parameter DescriptionFor details about the extended parameters of NIC Configuration Data Export tasks, see Table8-22.



8-81

Table 8-22 Extended parameters of NIC Configuration Data Export tasks


Export Path Default value. Nochange.The default pathis /export/home/omc/var/fileint/cm/GExport.

Refers to the path for saving the exportedconfiguration data files on the M2000 server.

File Save Time Default value. Nochange.The default storageduration is 3 days.

Refers to the storage duration of the exportedconfiguration data files on the M2000 server.

File NeedCompressed

Default value. Nochange.The default valueis Yes.

Determines whether to decompress the exportedconfiguration data files before saving them on theM2000 server.

Export NEs You need to selectNEs in thenavigation treeaccording to theactualrequirement.

l Export All NE:The M2000 will export the configuration data ofall NEs.

l Export By NE Type:After you select the required NE type, the M2000will export the configuration data of all the NEs ofthis type.

l Export By NE:After you select the required NEs, the M2000 willexport the configuration data of all the selectedNEs.

For details about the extended parameters of Configuration Data Export tasks, see Table8-23.

Table 8-23 Extended parameters of Configuration Data Export tasks


File Format Two formats (.xmland .csv) areavailable in thedrop-down list.You need to selecteither of them.

Refers to the file format in which the exported data issaved.



Issue 03 (2010-08-31)


File Path Default value. Nochange.The default pathis /export/home/omc/var/fileint/cm/autoExport.

Refers to the path for saving the exportedconfiguration data.

Please SelectNE

You need to selectNEs in thePhysicalTopology Treenavigation tree.If All NEConfigurationData is selected,the PhysicalTopology Treenavigation treebecomesunavailable, andthe M2000 willexport theconfiguration dataof all NEs.

l : to expand all subnodes.

l : to collapse all subnodes.

l : indicates a cascading selection. That is, afteryou select a certain parent node, all its subnodesare selected accordingly.

8.8.20 Parameters for Modifying the Export of NE LogsThis section describes the parameters for exporting NE logs and can be taken as reference duringthe parameter modification.


Table 8-24 Descriptions of extended parameters


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.



8-83


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.

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.

8.8.21 Parameters for Modifying the Export of Inventory DataThis section describes the parameters for exporting inventory data, which can be your referenceduring the parameter modification.



File Format Refers to the format in which the exported data files are saved. Threeformats are available, that is, .XML, .CSV and .TXT. You can select fromthe drop-down list.

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 of all NEson the network. This option is selected by default.

Please SelectNE

Indicates all the NEs in the entire network. Multiple NEs are supported.You can select the specific NEs in Please Select NE only after you deselectAll NE.



Issue 03 (2010-08-31)

8.8.22 Parameters for Modifying an Alarm/Event Log Export TaskThis describes the parameters for modifying an alarm/event log export task.

Table 8-25 describes the extended parameters for modifying an alarm/event log export task.

Table 8-25 Extended parameters


File type You can select the following filetypes:l CSV.

l XML.

l TXT.

l HTML.

The exported file isin .CSV , .TXT, .HTML or .XMLformat.

Compression format You can select one of thefollowing items.l Not compress

l zip

l gzip

l If you select zip or gzip, itindicates that the .csv, .xml, .txtor .html files are decompressedand then exported.

l If you select Not compress, itindicates that the .csv, .xmlfile, .txt or .html is exported.

Export To The default value is used andcannot be changed.The default path is /export/home/omc/var/fileint/fm/.

The save path of exported alarm/event log.

File prefix The value contains 0-30characters.

Prefix of export file names. Exportfiles are named in the export pathin the format of prefix-exporttime-data type. For example,assume that the prefix is abc. Thegenerated file names areabc-20090928104022-alarm-log-auto-1.zip andabc-20090928104022-event-log-auto-1.zip.



8-85


Alarm Severity,Category, and Type

You can select the followingvalues:l Alarm severities: Critical,

Major, Minor, and Warning.l Alarm Categories: Alarm

Log and Event Log.l Type: Power system,

Environment system,Signaling system, Trunksystem, Hardware system,Software system, Runningsystem, Communicationsystem, QoS, Processingerror, Internal, Integrityviolation, Operationalviolation, Physical violation,Security service ormechanism and Time domainviolation.

Select the severity, category, andtype of the alarm to be exported.

Alarm Name You can select alarm names. List the alarms that can beexported currently.

8.8.23 Parameters for Modifying the Export of M2000 LogsThis describes the parameters for exporting M2000 logs and can be taken as reference duringthe parameter modification.


Table 8-26 Descriptions of extended parameters



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.

Export File Type You can select .csv or .xml. Exports operation logs to a .csvfile or .xml file.

File path The default path is:/export/home/omc/var/fileint/***logs/, where *** stands forthe log type.

Saves the exported logs.



Issue 03 (2010-08-31)


Export FileManagement

l Unit: day. Value range: 3-30.Default value: 15

l Unit: file. Value range:200-1000. Default value:1000

l Unit: M. Value range:200-2048. Default value:1024

l Only hold XX Day(s): In theexport directory, the log filesolder than this period aredeleted.

l Only hold XX File(s): In theexport directory, if the numberof log files exceeds the value ofthis parameter, the M2000deletes the oldest export filesuntil the number of log files inthis directory becomes less thanthe value of this parameter.

l Only hold XX M of file: In theexport directory, if the total sizeof log files exceeds the value ofthis parameter, the M2000deletes the oldest export filesuntil the total size of log files inthis directory becomes less thanthe value of this parameter.

8.8.24 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 descriptionThe 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.

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.



8-87


Export By NE After you select some NEs from the NE navigationtree, the M2000 exports the information about allselected NEs.

8.8.25 Parameters for Modifying the Synchronization of NEConfiguration Data

This section describes parameters used for synchronization of NE configuration data. Whenmodifying the parameters, you can set the parameters by referring to the information describedin this section.

Parameter descriptionParameter Description

All NEConfigurationData

If All NE Configuration Data is selected, the system synchronizes theconfiguration data of all existing NEs in the network.

Please SelectNE

Select existing NEs in the entire network. Multiple NEs are supported.

8.8.26 Parameters for Modifying the Synchronization of InventoryData

This section describes parameters used for synchronization of inventory data. When modifyingthe parameters, you can set the parameters by referring to the information described in thissection.


All NE If you select this option, the system synchronizes the inventory data of allNEs on the network.

Please SelectNE

Indicates all the NEs in the entire network. Multiple NEs are supported.You can select the specific NEs in Please Select NE only after you clearAll NE.



Issue 03 (2010-08-31)

8.8.27 Parameter Description: Modifying a Data Backup Task of theM2000

This section describes the parameters related to data backup tasks of the M2000. You can referto the description when modifying a data backup task.

For description of the extended parameters, see Table 8-27.

Table 8-27 Extended Parameters


Server Full BackupDate

Monday to Sunday The full backup is performed once a week.For example, if this parameter is set toMonday, the full backup is performedevery Monday.

Backup File Path The default path isrecommended andcannot be changed.The default path is /export/home/backup/omc.

Path for saving the backup data of theM2000.

8.8.28 Parameters for Creating/Modifying/Copying NE BackupThis section describes the parameters related to NE backup tasks. You can refer to this part whencreating or modifying NE backup tasks.


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.



8-89


By NE Type If this option is selected, you should specify the NE type in the NE Typenavigation tree.1. Select By NE Type. The By NE Type dialog box is displayed.2. In the navigation tree in the left pane, select one or multiple NE types.

3. Click to add the selected NE types to the valid domain at the rightside. Click to add the all NE types to the valid domain at the rightside.NOTE

l Click to delete the selected NE types from the valid domain at the right

side. Click to delete the all 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.

4. Click Apply.

By NE If this option is selected, you should specify the NE in the NE navigation tree.1. Select By NE. The By NE dialog box is displayed.2. In the navigation tree in the left pane, select one or multiple NEs.

3. Click to add the selected NEs to the valid domain at the right side.Click to add the all 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.

Click to delete the all 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.

4. Click Apply.

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



Issue 03 (2010-08-31)

Parameter DescriptionParameter Value Range Description

Script file The script fileis in .txtformat. Themaximum sizeis 2 MB.

The MML script file is a text file that records MMLcommands for one NE or multiple NEs of the same type.You can click , and then select the MML script file inthe displayed Open dialog box.

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.



8-91

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.

8.8.30 Parameters for Creating, Modifying, or Copying aConfiguration Report Export Task

This topic describes the parameters involved in the export of RAN reports, CN resource reports,NE reports, NE statistic reports, and NE link reports. When creating, modifying, or copying anexport task of these reports, you can refer to this topic and perform relevant operations.

Parameter description

On the M2000, you can set an export task on the configuration reports that you are concernedto export the configuration reports of a specified NE to a specified directory on the server.


File Path Refers to the path for saving a report. The path cannotbe changed.The default path is /export/home/omc/var/fileint/cm/Report.

NE Type In the case of RAN reports, you can choose any one ofMBTS, WCDMA, CDMA, GSM as the NE type.TIP

l In the case of NEs of the WCDMA, CDMA, or GSMtype, you also need to select the NEs whose reports are tobe exported from the NE navigation tree after selecting theNE type.

l In the case of NEs of the MBTS type, you need not selectthe specific NEs. The M2000 automatically exports all theMBTS reports to the specified path.

In the case of NE link reports, you can select any oneof SGSN, RNC, MSCServer, BSC6000(R11+),BSC6810(R11+), BSC6900GSM, BSC6900UMTS,and BSC6900GU as the NE type.

Selected You can select Selected to specify Report Type.

Report Type



Issue 03 (2010-08-31)

8.8.31 Parameter Description: Creating, Viewing, or Modifying aScheduled Report Task

This section describes the parameters for setting a scheduled report task. You can refer to thedescription in this section when creating, querying, or modifying a scheduled task.

Common ParametersParameter Description

Basicinformation

Task Name Indicates the name of a scheduled report task.Value range:l A maximum of 64 characters

l The following characters except the apostrophe character (')are allowed: English characters, Chinese characters,numbers or other special characters. That is, the apostrophecharacter (') is not allowed.

l The value must be unique and cannot be 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.

Run Type Indicates the execution type of a scheduled report task.Value range:l Periodic, which indicates that the system performs a created

task periodically.l Once, which indicates that the system performs a created

task once in a specific time.If you select this option, the parameters in the ExecutionPeriod become unavailable.

ExecutionPeriod

Indicates the interval between periodic tasks. An interval hastwo dimensions: unit and duration.The unit of the period can be hour, day, week, or month.

ExecutionTimes

Indicates the number of times that a periodic task is executed.Value range:l Unlimited, which indicates that the periodic task is executed

for an unlimited number of times.l Limited, which indicates that the periodic task is executed

for N times. N is a specific number.



8-93

Extended ParametersParameter Description

Extendedparameter

Report Name Indicates the name of a scheduled report task.

Save Path Indicates the path for saving the report.For example: /report/$ReportOwner$/$TaskName$$Date$. For details about each field, see Table 8-28.

File Name Indicates the format of the report name.For example: $reportname$-$date$. For details about eachfield, see Table 8-28.

File Format Indicates the format of the report file.Value range:l Excel

l HTML

l CSV

CompressFile

Indicates whether to compress the scheduled report files.Value range:l Selected

l Deselected

Compress File is selected by default. The format of thecompressed file is .zip.

MaximumFile Number

Indicates that the report files of a periodic task generated forthe recent N times are saved on the system. N is a specificnumber.Value range:l Unlimited, which indicates that all the report files of the

periodic task are saved on the system.l Limited, which indicates that the report files of the periodic

task generated for the recent N times are saved on thesystem.

Table 8-28 lists the predefined macros that are supported by the save path and file name.

Table 8-28 Predefined macros

Predefined Macro Meaning

$ReportOwner$ Indicates the creator of a report.

$TaskType$ Indicates the type of a periodic task.Value range: once, hour, weekly, monthly.



Issue 03 (2010-08-31)


$Time$ Indicates the time when a periodic report isgenerated.

$DateTime$ Indicates the date and time when a periodicreport is generated.

$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 date when a periodic report isgenerated.

$Index$ Indicates the number of times that ascheduled task is executed.

$yy$ YearIndicates a year, which supports the simpleexpression.For example, $yy-1$ indicates the yearpreceding the current year, and $yy+1$indicates the year following the current year.

$mm$ MonthIndicates a month, which supports the simpleexpression.For example, $mm-1$ indicates the monthpreceding the current month, and $mm+1$indicates the month following the currentmonth.

$dd$ DayIndicates a day, which supports the simpleexpression.For example, $dd-1$ indicates the datepreceding the current date, and $dd+1$indicates the date following the current date.

$hh$ HourIndicates an hour, which supports the simpleexpression.For example, $hh-1$ indicates the hourpreceding the current hour, and $hh+1$indicates the hour following the current hour.



8-95


$Moh$ MinuteIndicates a minute, which supports the simpleexpression.For example, $Moh-1$ indicates the time thatis one minute earlier than the current time,and $Moh+1$ indicates the time that is oneminute later than the current time.

NOTE

The rules for naming the scheduled report files are as follows:

l A performance report file in the .xls format is named by the value of File name.

l A performance report file in the .html or .csv format is named by File name+Subreport name.

For example, in the name task_120080523151900report_1, task_120080523151900 is namedaccording to a user-defined rule and report_1 is the subreport name.

Distribution ParametersParameter Description

EmailDistribution

To: Indicates the recipient of emails. Use commas to separaterecipient names.Click Email Boxes. The Select the distributing email boxdialog box is displayed. Select one or more mailboxes and thenclick OK.TIP

You can right-click any record and then choose Select All or ClearAll from the shortcut menu to quickly select or clear all the records.

The system can send scheduled report files to a maximum of64 email recipients simultaneously.

Email Subject Indicates the subject of an email.If you have set email recipients in To, you must set the subject.

EmailContents

Indicates the contents of an email.

FTPDistribution

FTP Server Indicates the IP address of the server.Click FTP Server. The Select the distributing FTP serverdialog box is displayed. Select one or more servers and thenclick OK.TIP


The system can send scheduled report files to a maximum ofeight FTP servers simultaneously.



Issue 03 (2010-08-31)


SMSDistribution

Telephone Indicates the number of the SMS recipient.Click SMS Recipient. The Select SMS Recipient Numberdialog box is displayed. Select one or more SMS recipientnumbers and then click OK.TIP


You can add or delete SMS recipient numbers. When youmodify an SMS recipient number, only the remarks can bemodified. The SMS recipient number can only be set to a digitstring.

Rows in SMS Indicates the maximum number of lines in an SMS sent to theSMS recipient.Value range: 1 to 5.

Counters inSMS

Indicates the maximum number of KPIs included in an SMSsent to the SMS recipient.Value range: 1 to 4.

Append Time Indicates whether to include the time information in the SMS.If this option is selected, it indicates that the time informationis included in the SMS.

AppendObject

Indicates whether to include the object information in the SMS.If this option is selected, it indicates that the object informationis included in the SMS.

NOTE

The system adopts a redistribution mechanism. That is, in the case of an email, SMS, or FTP distributionfailure, the system immediately redistributes the email, SMS, or FTP information. A maximum of threeredistributions are provided. In addition, you can manually run a scheduled report task as required. Then,the PRS generates a report file at the task execution time, and then distributes the generated report files toan email recipient, SMS recipient, or an FTP server.

8.8.32 Parameters for Creating/Modifying/Copying ScheduledNodeB License Allocation Tasks

This section describes the parameters of scheduled NodeB license allocation tasks. You can referto this section when creating or modifying scheduled NodeB license allocation tasks.



8-97


Task File l To create a scheduled NodeB license allocation task byallocating a license to NEs on a scheduled basisThe system automatically generates a .csv license resourceallocation file based on the preset license allocationinformation and displays the file in Task File. Manual exportis not required.

l To create a scheduled NodeB license allocation task bycreating a user timing taskClick Import, and then select the NodeB license resourceallocation file to be allocated.You can export NodeB license allocation information throughExporting the Assignment Information About NodeBCommon Licenses in the RAN Subnet and then change theallocation data of the NodeB common license.CAUTION

When modifying the license allocation information, you need to ensurethat the exported file is intact. That is, the information such as NEinformation, telecom operator information, and control iteminformation cannot be deleted. You need to modify only the licenseallocation information.

NOTE

l For details about how to download the task file, see 8.7.9Downloading Task Execution Tasks.

NE In the NE navigation tree, select the NE where the licenseallocation file is to be used.Only one scheduled allocation task can be created for an NE. TheNEs for which tasks are created are not displayed in the NEnavigation tree any longer. The task names corresponding to theseNEs are displayed in the Existed Task Information list.

8.8.33 Parameters for Creating/Modifying/Copying Scheduled BSCor RNC License Allocation Tasks

This section describes the parameters of scheduled BSC or RNC license allocation tasks. Youcan refer to this section when creating or modifying scheduled BSC or RNC license allocationtasks.



Issue 03 (2010-08-31)


NE Select an NE for which you need to download the license file fromthe NE navigation tree.Only one scheduled allocation task can be created for one NE.The NEs for which tasks are created are no longer displayed inthe NE navigation tree. The task names corresponding to theseNEs are displayed in the Created NE Task Information.

License file Select a BSC or an RNC license file to be downloaded from thedrop-down list.NOTE

This drop-down list displays all the NE license files that are uploaded tothe M2000. For details about how to upload a license file, see Uploadingan NE License to the Server.

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

Parameter DescriptionNOTEThe portals of the Top Power Test task are as follows:

l Maintenance > Task Management.

l Maintenance > RF Performance Test > Top Power Test.


ExecutionDuration

3-120 minutes Maximum execution duration of a task

NE None Existing NE that supports cabinet-top powertest.

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



8-99


NOTEThe portals of the RSST Test task are as follows:

l Maintenance > Task Management.

l Maintenance > RF Performance Test > RSSI Test.


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.

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

8.8.37 Parameters for Creating/Modifying/Copying a Dual-HomingAuto Consistency Check Task

This section describes the parameters for creating, modifying, or copying a dual-homing autoconsistency check task.



Issue 03 (2010-08-31)

Parameter DescriptionParameter Description Setting

Dual Homing Pairs Indicates the dual-homingpairs whose data is to bechecked.

-

Resource Type Indicates the data resourcetype of the dual-homing pairsto be checked.Data resource types varyaccording to the version of thedual-homing pair NE.

l Select the corresponding itemin the Resource Typenavigation tree.

l Type a data resource type orkeyword in Search. Then therelated resource types arelisted in the area underSearch. You can double-clicka resource type to be checked.

Search Is used to search for the type ofthe data resource to bechecked. Case-insensitivesearch rather than wildcardsearch is supported.

Type a data resource type orkeyword in Search.

8.8.38 Parameters for Creating/Modifying/Copying an HSL ScriptTask

This section describes the parameters of HSL script tasks. You can refer to this part and setrelevant parameters when creating or modifying an HSL script task.

Parameter DescriptionParameter Value Range Description

Main File The main file is in .hslformat. The maximumsize of the main file is 1MB.

The main file is the entry file for the executionof a script.

Assistant File The maximum size of theassistant file is 1 MB.

During the execution of a script, the main file canselect scripts that need to be invoked fromassistant files.

NE Selection None. You need to specify NEs if the script will beexecuted on certain NEs. You can select multipleNEs.



8-101

8.8.39 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 8-29 Description of extended parameters


Please Select 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.

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


All NE After you select this option, the system uploads the configuration dataof all the NEs that support CME tasks on the network. The NEs thatsupport CME tasks are the RNC, NodeB, BSC6000, BSC6900 GSM,BSC6900 UMTS and BSC6900 GU.

All NodeBs UnderRNC

After you select this option, the system uploads the configuration dataof all the NodeBs under the selected RNCs.



Issue 03 (2010-08-31)


Please Select NE Indicates the NEs of all the existing RNCs and NodeBs in the entirenetwork. Multiple NEs are supported. You can select the specific NEsin Please Select NE only after you clear All NE.

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

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



8-103

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.

8.8.43 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

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.

8.8.44 Parameters for Setting Time of Timing TasksThis section describes the parameters of time for automatic suspending and automatic resumingtiming tasks



Issue 03 (2010-08-31)

Table 8-30 lists the parameters of auto-suspend time and auto-resume time for timing tasks.

Table 8-30 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.

8.8.45 Parameters for Selecting Objects for OMC CheckThis part describes the extended parameters for selecting objects for OMC check. You can referto this part when creating device check tasks.


Device Check OMC

NE OMC



8-105


Health Check Sun Server:Displays the health check items supported byM2000.l Operating System

l Sybase

l VERITAS Volume Manager Software

l Sun Cluster

l Host Hardware

l OMC

HP or ATAE Server:Displays the health check items supportedby M2000.l Operating System

l Oracle

l VERITAS Volume Manager Software

l VCS Cluster

l S3X00 Array

l OMC

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



Issue 03 (2010-08-31)


Trace files inserver

Collects the trace files from the M2000 server.

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.



8-107

9 Managing the M2000 Processes and Services(HA)

About This Chapter

This chapter describes how to manage the processes and services of the M2000 HA system. Themanagement of the processes and services ensures the smooth operation of the M2000 HAsystem.

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

9.2 Managing M2000 Services (HA)This section describes how to check, start, and stop the services of the M2000 HA system.

HA System Administrator Guide (Sun, S10) 9 Managing the M2000 Processes and Services (HA)


9-1

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

9.1.1 3rdTool_agent ProcessThis section describes the 3rdToolService service and dependent services.

9.1.2 adn_agent ProcessThis section describes the services and functions provided by the adn_agent process.

9.1.3 adss_agent ProcessThis section describes the services and functions provided by the adss_agent process.

9.1.4 antenna_agent ProcessThis section describes the services and functions provided by the antenna_agent process.

9.1.5 ce_agent ProcessThis section describes the services and functions provided by the ce_agent process.

9.1.6 cmdc_agent ProcessThis section describes the CmDcService service and dependent services. CmDcService isprovided by the cmdc_agent process.

9.1.7 cmengine_agent ProcessThis section describes the services and functions provided by the cmengine_agent process.

9.1.8 cmeserver_agent ProcessThis section describes the services and functions provided by the cmeserver_agent process.

9.1.9 cmexp_agent ProcessThis section describes the service and functions provided by the cmexp_agent process.

9.1.10 cmserver_agent ProcessThis section describes the services and functions provided by the process cmserver_agent.

9.1.11 cnnhc_agent ProcessThis section describes the services and functions provided by the cnnhc_agent process.

9.1.12 corba_agent ProcessThis section describes the services and functions provided by the corba_agent process.

9.1.13 cpm_agent ProcessThis section describes the services and functions provided by the cpm_agent process.

9.1.14 devdoc_agent ProcessThis section describes the DevDocService service provided by the devdoc_agent process.

9.1.15 dsXXXX agent ProcessThis section describes the services and functions provided by the dsXXXX_agent process.

9.1.16 eam_agent ProcessThis section describes the services and functions provided by the eam_agent process.

9.1.17 fars_agent ProcessThis section describes the service and function provided by the fars_agent process.

9.1.18 fmnotify_agent Process

9 Managing the M2000 Processes and Services (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

This section describes the services and functions provided by the fmnotify_agent process.

9.1.19 FMPreServiceXXXX_agent ProcessThis section describes the services and functions provided by the FMPreServiceXXXX_agentprocess.

9.1.20 fnlicense_agent ProcessThis section describes the services and functions provided by the fnlicense_agent process.

9.1.21 glmssyn_agent ProcessThis section describes the services and functions provided by the glmssyn_agent process.

9.1.22 ifms_agent ProcessThis section describes the service and functions provided by the ifms_agent process.

9.1.23 ipqdt_agent ProcessThis section describes the services and functions provided by the ipqdt_agent process.

9.1.24 ipm_agent ProcessThis section describes the services and functions provided by the ipm_agent process.

9.1.25 irp_agent ProcessThis section describes the functions provided by the irp_agent process.

9.1.26 itm_agent ProcessThis section describes the ItmService service and the dependent services by the itm_agentprocess.

9.1.27 lcsserver_agent ProcessThis section describes the services and functions provided by the lcsserver_agent process.

9.1.28 lic_agent ProcessThis chapter describes the services and functions provided by the process lic_agent.

9.1.29 log_agent ProcessThis section describes the LogService service and dependent services. LogService is providedby the log_agent process.

9.1.30 necomm_agent ProcessThis section describes the services and functions provided by the necomm_agent process.

9.1.31 maintain_agent ProcessThis topic describes the function of the MaintenanceService service, which is provided by themaintain_agent process.

9.1.32 manager_agent ProcessThis section describes the services and functions provided by the manager_agent process.

9.1.33 medXXXX_agent ProcessThis section describes the services and functions provided by the medXXXX_agent process.

9.1.34 nelicense_agent ProcessThis section describes the services and functions provided by the nelicense_agent process.

9.1.35 neuser_agent ProcessThis section describes the NeUserService service. NeUserService is provided by theneuser_agent process.

9.1.36 ngnffs_agent ProcessThis section describes the NGNFullFillService service and dependent services.



9-3

9.1.37 ngnnis_agent ProcessThis section describes the NGNNIService service and dependent services.

9.1.38 ngnni112_agent ProcessThis section describes the services and functions provided by the ngnni112_agent process.

9.1.39 ngntestmanage_agent ProcessThis section describes the services and functions provided by the ngntestmanage_agent process.

9.1.40 nhcserver_agent ProcessThis section describes the services and functions provided by the nhcserver_agent process.

9.1.41 nicserver_agent ProcessThis section describes the services and functions provided by the nicserver_agent process.

9.1.42 nimserver_agent ProcessThis section describes the NIMServer service and the dependent service. NIMServer is providedby the nimserver_agent process.

9.1.43 nms_mml_agent ProcessThis section describes the services and functions provided by the process nms_mml_agent.

9.1.44 partition_agent ProcessThis section describes the services and functions provided by the partition_agent process.

9.1.45 pm_agent ProcessThis section describes the services and functions provided by the process pm_agent.

9.1.46 pmexp_agent ProcessThis section describes the services and functions provided by the process pmexp_agent.

9.1.47 pmmon_agent ProcessThis section describes the services and functions provided by the process pmmon_agent.

9.1.48 pmncdXX01_agent ProcessThis section describes the services and functions provided by the pmncdXX01_agent process.

9.1.49 porttrunk_agent ProcessThis section describes the services and functions provided by the porttrunk_agent process.

9.1.50 proxy_agent ProcessThis section describes the services and functions provided by the proxy_agent process.

9.1.51 PRSAssistantService_agent ProcessThis section describes the services and functions provided by the PRSAssistantService_agentprocess.

9.1.52 prsdc_agent ProcessThis section describes the services and functions provided by the prsdc_agent process.

9.1.53 prsfs_agent ProcessThis section describes the services and functions provided by the prsfs_agent process.

9.1.54 prsreport_agent ProcessThis section describes the services and functions provided by the prsreport_agent process.

9.1.55 prssum_agent ProcessThis section describes the services and functions provided by the prssum_agent process.

9.1.56 rn_agent ProcessThis section describes the services and functions provided by the rn_agent process.



Issue 03 (2010-08-31)

9.1.57 ScriptModuleService_agent ProcessThis section describes the services and functions provided by the ScriptModuleService_agentprocess.

9.1.58 scriptserver_agent ProcessThis section describes the services and functions provided by the process scriptserver_agent.

9.1.59 sm_agent ProcessThis section describes the services and functions provided by the process sm_agent.

9.1.60 snmp_agent ProcessThis section describes the SnmpAgent service and the dependent services. The SnmpAgentservice is provided by the snmp_agent process.

9.1.61 son_agent ProcessThis section describes the services and functions provided by the son_agent process.

9.1.62 swm_agent ProcessThis section describes the services and functions provided by the swm_agent process.

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

9.1.64 uap_agent ProcessThis section describes the services and functions provided by the uap_agent process.

9.1.65 udpdispatch_agent ProcessThis section describes the services and functions provided by the udpdispatch_agent process.

9.1.66 umgupdsvr_agent ProcessThis section describes the services and functions provided by the umgupdsvr_agent process.

9.1.67 xftpXX01_agent ProcessThis section describes the services and functions provided by the xftpXX01_agent process.

9.1.68 Processes and Services Related to Each Northbound InterfaceThis section describes the processes and services related to each northbound interface.


9.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: ScriptServer

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



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

9.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: none

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

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

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

9.1.7 cmengine_agent ProcessThis section describes the services and functions provided by the cmengine_agent process.



Issue 03 (2010-08-31)

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

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

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

9.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: TopoAdapterService



9-7

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


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

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


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


9.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 03 (2010-08-31)

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.


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

9.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: none.

9.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 services: LicenseService.



9-9

9.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 the 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.

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


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


9.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 03 (2010-08-31)


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

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


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



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

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

9.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 03 (2010-08-31)


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


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


9.1.30 necomm_agent ProcessThis section describes the services and functions provided by the necomm_agent process.

The necomm_agent process provides the CommonLicService service and SSLManageServiceservice.

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.



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




9-13

9.1.32 manager_agent ProcessThis section describes the services and functions provided by the manager_agent process.

The manager_agent process provides the SystemService service.

SystemService enables you to query the M2000 version information such as the version of theoperating system, software version of the client, software version of the server, client softwareversion matching the server software, and client upgrade information.



9.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: none

9.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: LogService.

9.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 03 (2010-08-31)


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


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


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

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


9.1.40 nhcserver_agent ProcessThis section describes the services and functions provided by the nhcserver_agent process.

The nhcserver_agent process provides the NHCServer service.

The NHCServer service provides the NE health check function. The nhcserver_agent process isavailable only after you have installed the NE 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.

9.1.41 nicserver_agent ProcessThis section describes the services and functions provided by the nicserver_agent process.



9-15

The nicserver_agent process provides the NICServer service.

The NICServer service provides the network information collecting function. Thenicserver_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.

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


9.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 services: LogService.

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



9.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 03 (2010-08-31)

PMService monitors performance management on all NEs. The performance management isindependent of NEs or objects. Stop PMService if the performance management function is notrequired.


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


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

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

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



9-17


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


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


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


9.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 03 (2010-08-31)

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


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

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

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

9.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 and SecurityService.



9-19

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

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

9.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: none

9.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 03 (2010-08-31)

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

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


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

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


9.1.67 xftpXX01_agent ProcessThis section describes the services and functions provided by the xftpXX01_agent process.



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


9.1.68 Processes and Services Related to Each Northbound InterfaceThis section describes the processes and services related to each northbound interface.

Table 9-1 describes the relations between northbound interfaces and their correspondingprocesses and services.

Table 9-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 03 (2010-08-31)

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 9-1.



9-23

Figure 9-1 Process Monitor tab page


----End

9.2 Managing M2000 Services (HA)This section describes how to check, start, and stop the services of the M2000 HA system.


9.2.2 Viewing the States of M2000 Services (HA)This 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.






Issue 03 (2010-08-31)



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 9-2.

Figure 9-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

9.2.2 Viewing the States of M2000 Services (HA)This 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.



9-25

PrerequisiteLog in to the active node as user omcuser through SSH mode.

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



l The Sybase services are running properly. For details about how to start the Sybase services,see 16.2.2 How to Start the Sybase (HA, Sun).

ContextNOTE

The time required for starting M2000 system services is related to the actual environment. Generally, ittakes about 20 minutes.



Issue 03 (2010-08-31)

Procedurel 1. Run the following command:


NOTE

l In the HA system, starting services requires some time. Wait about 10 minutes until allservices are started and then you can perform operations on the HA system.

l When you start M2000 system services, the status of each service is displayed. If the statusof a service is failed, you can infer that the service fails to be started. In this case, you canlocate the fault by viewing the iMAP.troubleshooting.trace log on the active node.

# more /export/home/omc/var/logs/iMAP.troubleshooting.trace

----End



ContextNOTE

The time required for stopping M2000 system services is related to the actual environment. Generally, ittakes about 20 minutes.

Procedurel 1. Run the command:


NOTE

The HA system takes some time to stop the services. Wait for ten minutes after you run thecommand. Run the command svc_ps to monitor the service stopping progress.

----End



9-27

10 Managing the M2000 Databases

About This Chapter

This chapter describes how to manage the M2000 databases.

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

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

10.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/event logs, NMoperation logs, NM system logs, and NM security logs. You can configure an integrated taskfor dumping the data in the M2000 databases.

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

HA System Administrator Guide (Sun, S10) 10 Managing the M2000 Databases


10-1

10.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 and event logs of the M2000 and NEs. The fmdb database must existin the M2000 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.

10.1.1 cmedb DatabaseThe cmedb database is used to store the NE configuration data on the CME, including theconfiguration data in the current and planned data areas.

10.1.2 farsdb DatabaseThe farsdb database stores the signaling data of all the NEs managed by the M2000.

10.1.3 fmdb DatabaseThis section describes the fmdb database, which stores the alarm and event logs of the M2000and the managed NEs.

10.1.4 itfndb Database

10 Managing the M2000 Databases HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

This section describes the itfndb database, which stores the northbound configuration data,performance tasks, and performance threshold data.

10.1.5 omcdb DatabaseThis section describes the omcdb database. The omcdb database stores the M2000 configurationdata, security data, and internal data.

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

10.1.7 omclogdb DatabaseThis section describes the omclogdb database, which stores the M2000 log management data.

10.1.8 omcsmdb DatabaseThis section describes the omcsmdb database, which stores the security management data.

10.1.9 omctempdb DatabaseThis section describes the omctempdb database. The omctempdb database is used to store thebuffer data required for internal implementation of the DesktopServiceXXXX service.

10.1.10 omctmdb DatabaseThis section describes the omctmdb database, which stores the topology management data.

10.1.11 pmcomdb DatabaseThe pmcomdb database is used for storing the static performance measurement data of NEs.

10.1.12 pmdb DatabaseThis section describes the pmdb database, which stores the performance structure tables andperformance measurement results of NEs.

10.1.13 sumdb DatabaseThe sumdb database stores the summarized performance data of NEs for performance reports.

10.1.14 swmdb DatabaseThis section describes the swmdb database, which stores the file information about the softwaremanagement module and the configuration data of NE versions.

10.1.1 cmedb DatabaseThe cmedb database is used to store the NE configuration data on the CME, including theconfiguration data in the current and planned data areas.

The cmedb database requires at least 10 GB data space.

Table 10-1 lists the names and functions of the tables in the cmedb database.

Table 10-1 Names and functions of tables in the cmedb database

Table Name Function

Utils_TableDef Records the basic information about the MOC.

Utils_FieldDef Records the attribute information about the MOC.

Utils_FieldDefIncludeO-paque

Records the attribute information about the opaque.



10-3

Table Name Function

Utils_ErrMsg Records the correspondence between the error code and errordescription.

10.1.2 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 10-2 describes the name and function of each table in the farsdb database.

Table 10-2 Tables of the farsdb database and the corresponding functions

Table Name Function

tbl_ProcessorInfo Static service configuration table

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

10.1.3 fmdb DatabaseThis section describes the fmdb database, which stores the alarm and event logs of the M2000and the managed NEs.

The space of the fmdb database must be greater than 3,700 MB.

Table 10-3 lists the names and functions of tables in the fmdb database.

Table 10-3 Tables of the fmdb database and the corresponding functions

Table Name Function

tbl_alm_log Records alarm logs.



Issue 03 (2010-08-31)

Table Name Function

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.

10.1.4 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 10-4 lists thename and function of each table.

Table 10-4 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.

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.

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



10-5

Table 10-5 lists the names and functions of the tables in the omcdb database.

Table 10-5 Names and functions of tables in the omcdb database

Table Name Function

Tables with moi_ as the prefix Records the information about MO examples.

Tables with mos_ver_ as theprefix

Records the information about versions.

Tables with nbmmlNe_ as theprefix

Records the information about the format of messagestransferred between the and the NEs.

Tables with sm_ as the prefix Records the information about service data.

Tables with softx3000_ as theprefix

Records dual-homing relationship.

Views with gv_view_cmcyw_as the prefix

Records service Database Central (DC) data.

Views with view_cmcyw_ asthe prefix

Records basic service data.

tbl_AllNeInfo Records information about NEs.

Processes with proc_sm_ as theprefix

Records the processes of service data.

Processes with sm_ as theprefix

Records the processes of service AMG data.

tbl_Resource Records NE resource data.

Tables with ums_ as the prefix Record the information about error codes.

Tables with ne_ as the prefix Records the information about NE models.

Tables with omc_ as the prefix Records the data about network management.

Tables with rel_ as the prefix Records the associations between MOs.

tbl_ADAllNeList Records the information about the NodeBs to becommissioned.

tbl_ADNeStatus Records the information about the statuses of the NodeBsto be commissioned.

tbl_AllNeInfo Records the network management data. It is created toensure that the 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.



Issue 03 (2010-08-31)

Table Name Function

tbl_nelicTask Records the information about operation tasks.

tbl_nelicTaskEnv Records the information flow interacted between theM2000 server 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 thebearer network.

tbl_test_nblink_result Records the audit result of the call completion rate on thebearer network.

tbl_test_ping_address Records the information about address pairs sent by thehost.

tbl_SubareaInfo Refers to the partition information table, which records theinformation about each node.

tbl_SubareaRes Refers to the partition resource table, which records theresources of each node.

session_SessionEntity Records the information about the operated NEs during asession.

session_SessionMoc Records the information about the operated MOCs duringa session.

session_SessionOpInfo Records the information about the user operations during asession.

Other tables Records other configuration data of the M2000.

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

Table 10-6 lists the name and function of each table in the omceamdb database.



10-7

Table 10-6 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

10.1.7 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 10-7 lists the names and functions of the tables in the omclogdb database.



Issue 03 (2010-08-31)

Table 10-7 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.

10.1.8 omcsmdb DatabaseThis section describes the omcsmdb database, which stores the security management data.

Table 10-8 lists the names and functions of the tables in the omcsmdb database.

Table 10-8 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.



10-9

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.

10.1.9 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 10-9 lists the name and function of each table in the omctempdb database.

Table 10-9 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.

10.1.10 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 10-10 lists the names and functions of the tables in the omctmdb database.

Table 10-10 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.



Issue 03 (2010-08-31)

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.

10.1.11 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 10-11lists the name and function of each table.

Table 10-11 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.



10-11

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 10-12 liststhe name and function of each table.

Table 10-12 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 10-13lists the name and function of each subset and table.



Issue 03 (2010-08-31)

Table 10-13 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.

10.1.12 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 10-14 lists the name and function ofthe table.



10-13

Table 10-14 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 10-15 lists the name and function of the table.

Table 10-15 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.

10.1.13 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 10-16 lists the name and function of each table.

Table 10-16 Name and function of each object type information table in the sumdb database

Table Name Function

t_NeType Records the NE type and manages the relevant information.

t_PRSObjectType Records the information about object types of each class.



Issue 03 (2010-08-31)

Table Name Function

t_GroupObjType Records the information about object types of object groups.

t_AttrObjType Records the information about object types of attributeclasses.

t_ConfigObjType Records the information about object types of configurationclasses.

t_ConfigObjTypeAttr Records the attribute information about the configurationobject type.

t_CombObjType Records the information about object types of combinationclasses.

t_PmObjType Records the relation between the PRS object type and theperformance object type.

t_CombTable Records the rule information about the combination table.

t_FSS Records the information about the extracted function subsets.

t_Item Records counter information.

t_ObjTypeAggrRelation Records the summarization relation between objects.

System Setting Information TableThe system setting information consists of 15 tables that record information related to systemsetting. Table 10-17 lists the name and function of each table.

Table 10-17 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 about special dates.

t_BusyRule Records the information about busy-hour planning.

t_BusyTime Records the information about busy hours.

t_BusyTimeArith Records the information about the statistics on monthly busyhours.

t_DefaultPeriod Records the information about default periods.

t_RawPeriod Records the information about the extraction period oforiginal results.

t_DefaultStorage Records the default storage duration of results.

t_CustomStorag Records the storage duration of results.



10-15

Table Name Function

t_LoadFlag Records the information about the summarization andextraction.

t_MaxItemId Records the IDs of maximum available counters of NEs.

t_RawHistoryInf Records the history of extracting original result tables.

t_RawResultNo Records the result numbers of original result tables.

t_SumHistoryInfo Records the history of extracting summarization result tables.

t_BusyHistoryInfo Records the information about busy-hour summarizationresult tables.

Report Information TableThe report information table consists of eight tables that record the information about the queriedtables. Table 10-18 lists the name and function of each table.

Table 10-18 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 the templates.

t_TemplateObjInfo Records the basic information about the templates and theobjects.

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 10-19 liststhe name and function of each table.

In Table 10-19, 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.



Issue 03 (2010-08-31)

l In the tables whose names begin with d_, XXX refers to the ID of an object type.

Table 10-19 Name and function of each performance result table in the sumdb database

Table Name Function

f_fssName_Raw Indicates original result serial tables which record theoriginal results.If the function subset is not extracted internally, theadministration tool (AT) automatically names the functionsubset in the following format: F + ID of the function subset.

f_fssName_ObjLevel_H Indicates hourly serial tables which records the resultinformation at hour dimension. The hourly summarization isbased on the original results.

f_fssName_ObjLevel_D Indicates daily serial tables which record the resultinformation at day dimension. The hourly summarization isbased on hourly summarization.

f_fssName_ObjLevel_W Indicates daily serial tables which record the resultinformation at week dimension. The weekly summarizationis based on daily summarization.

f_fssName_ObjLevel_M Indicates monthly serial tables which record the resultinformation at month dimension. The monthlysummarization is based on weekly summarization.

f_fssName_ObjLevel_WH Indicates the weekly busy-hour serial tables which record theweekly busy-hour results.

f_fssName_ObjLevel_MH Indicates the monthly busy-hour serial tables which recordthe monthly busy-hour results.

d_XXX Records the information about the objects to be configured.

d_XXXGrp Records the information about the type of object groups.

d_XXXGrpObject Records the information about object instances of objectgroups.

10.1.14 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. Table10-20 lists the name and function of each table.



10-17

Table 10-20 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.

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

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

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

10.2.1 Checking the Database Usage Information About theM2000 Server 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 Figure10-1.



Issue 03 (2010-08-31)

Figure 10-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

10.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 Log in to the M2000 server as user dbuser through SSH mode. In the HA system, log in

to the active node.l The Sybase service is running.

ContextIn addition to the method described in 10.2.1 Checking the Database Usage InformationAbout the M2000 Server Through the M2000 Client, you can use the Sybase commands toview the disk usage of the M2000 server.

Procedure

Step 1 Check all the databases of the M2000 server.



10-19

-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

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



Issue 03 (2010-08-31)

1>exit

----End

10.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/event logs, 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 the

M2000 server and removed from the databases:– The performance data in the pmdb database

– The NE operation logs, NE system logs, and the NE security logs in the swmdb database

– The alarm and event logs in the fmdb database

– The operation logs, system logs, and security logs in the omclogdb database

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




10-21

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 and event logs 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/Event Log Dump 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


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





Issue 03 (2010-08-31)

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

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

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 10-2.



10-23

Figure 10-2 Periodic backup

Step 3 Click the Common Parameters tab, and then set Task Name and Start Time.

If the current time zone supports DST, the DST check box is available. The Start Time can becalculated by setting the DST.

Step 4 Click the Extended Parameters tab, and then set Server Full Backup Date, as shown in Figure10-3.



Issue 03 (2010-08-31)


Step 5 Click OK.

The system periodically backs up data.

----End



10-25

11 Managing the M2000 Files and Disks(HA)

About This Chapter

This chapter describes how to manage the file systems and disks on the M2000 server and client.


11.2 Managing Files and Disks on the M2000 Server (HA)This section describes how to manage the file systems and disks on the M2000 server.

HA System Administrator Guide (Sun, S10) 11 Managing the M2000 Files and Disks (HA)


11-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 11-1 describes the parameters specified in the equations.

Table 11-1 M2000 client software directory


client installation path Refers to the installation path of the M2000client software. The default path is C:\iManagerM2000ClientClient.

M2000 client installation path\client Refers to the path for saving client programs.

M2000 client installation path\client\bin Refers to the path for saving executable files.

M2000 client installation path\client\Data

Refers to the path for saving NE configurationfiles.

M2000 client installation path\client\diagnosis

Refers to the path for saving the information thatis used for locating problems.NOTE

This path appears only after you run the M2000diagnosis tool.

M2000 client installation path\client\ext_runcfg

Refers to the path for saving the configurationfiles of integrated components.

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

M2000 client installation path\client\IDAPI32

Refers to the path for saving the localWSdynamic link libraries.

11 Managing the M2000 Files and Disks (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)


M2000 client installation path\client\lib Refers to the path for saving the library files.

M2000 client installation path\client\localWs

Refers to the path for saving LocalShell that isused to start the 2G LMT.

M2000 client installation path\client\style

Refers to the path for saving the configurationfiles of the client.

M2000 client installation path\client\Templates

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

M2000 client installation path\client\tmp Refers to the path for saving temporary filesduring the upgrade.

M2000 client installation path\client\tracefile

Refers to the path for saving trace files.

M2000 client installation path\client\update

Refers to the path for saving upgrade files.

M2000 client installation path\client\cbb Refers to the path for saving the CBB files ofthe M2000 client.

M2000 client installation path\client\configuration

Refers to the buffer path of the M2000 client.The path automatically generates when theclient is started.

M2000 client installation path\client\features

Refers to the path for saving the featureconfiguration file of each subsystem of theM2000 client.

M2000 client installation path\client\plugins

Refers to the path for saving the configurationfile of each subsystem of the M2000 client asplug-ins.

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

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

M2000 client installation path\client\bin\run

Refers to the path for saving the startupparameter configuration files of the client andcomponents.



11-3


M2000 client installation path\cau Refers to the path for saving the Client AutoUpgrade (CAU) client software and the version,document abstract, and group information aboutthe M2000 client.NOTE

l The CAU client software provides the upgradedetection mechanism that is based on thedocument abstract for comparing the documentabstract of the server with that of the client. If thedocument abstracts are not consistent, you need toupgrade the client.

l Based on the group information, the server groupsand packs all the client documents deployed on theserver so that the client can download, install, andupgrade these documents. Based on the groupinformation, the client also groups and packs allthe client files. Therefore, these files can becompared with those grouped and packed by theserver after being downloaded.

M2000 client installation path\jre Refers to the path for saving the Java virtualmachine delivered with the M2000 client.

M2000 client installation path\lib Refers to the path for saving the dynamiclibraries shared among the M2000 client,remote alarm notification client, scriptframework client, and data management client.

M2000 client installation path\notify Refers to the path of the remote alarmnotification tool.

M2000 client installation path\TrafficReview

Refers to the path of the trace review tool.


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



Issue 03 (2010-08-31)

l Temporary files after the running of the M2000 log collector

Procedurel Delete the trace logs.

Delete the history trace logs saved in the directory M2000 client installation path\client\tracefile. It is recommended that you preserve the trace logs generated in the latest 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

11.2 Managing Files and Disks on the M2000 Server (HA)This section describes how to manage the file systems and disks on the M2000 server.

11.2.1 Introduction to the M2000 Server File System (HA)This 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.

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

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

11.2.1 Introduction to the M2000 Server File System (HA)This 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 11-2 lists the directories related to the M2000 server software.



11-5

Table 11-2 Directories for storing the M2000 server software


M2000 server installation directory M2000 server installation directory refers to theinstallation directory of the M2000 server software.By default, the installation directory is /opt/OMC.

M2000 server installation directory/3rdTools

Refers to the directory for storing the third-partysoftware.

M2000 server installation directory/apache2

Refers to the directory for storing the files relatedto the apache httpd.

M2000 server installation directory/bin

Refers to the directory for storing executable files.

M2000 server installation directory/cau

Refers to the directory for storing the CAUcomponents.

M2000 client installation path/client Refers to the directory of the M2000 client that isdeployed on the M2000 server.

M2000 server installation directory/component

Refers to the directory for storing the common filesof the core network.

M2000 server installation directory/components

Refers to the PRS control directory.

M2000 server installation directory/conf

Refers to the directory for storing the configurationfile of universal devices, the configuration file ofengineering documents and the C++ controlprogram of the HedEx.

M2000 server installation directory/data

Refers to the directory for storing the compressedcomponent files.

M2000 server installation directory/ds Refers to the directory for storing the files relatedto the DesktopService service.

M2000 server installation directory/etc

Refers to the directory for storing the systemconfiguration files and structured query language(SQL) scripts.

M2000 server installation directory/hascript

Refers to the directory for storing the platformscript files.

M2000 server installation directory/helper

Refers to the directory for storing the HedExprogram.

M2000 server installation directory/init

Refers to the directory for storing the initializationscript file that should be executed during theM2000 installation.

M2000 server installation directory/install

Refers to the directory for storing the script filesused for installing the M2000.

M2000 server installation directory/lib Refers to the directory for storing library files.



Issue 03 (2010-08-31)


M2000 server installation directory/lbin

Refers to the directory for storing the systemadministration commands.

M2000 server installation directory/jre

Refers to the JRE directory shared by the clientcomponents.

M2000 server installation directory/med

Refers to the directory for storing the mediation-related files generated during the operation.

M2000 server installation directory/medshare

Refers to the directory for storing the mediationfiles.

M2000 server installation directory/nhc

Refers to the directory for storing the key static filesrequired for generating the NHC reports.

M2000 server installation directory/nic

Refers to the directory for storing the key static filesrequired for generating the network informationcollecting reports.

M2000 server installation directory/plugins

Refers to the directory for storing the dynamiclibrary files and configuration files related to plug-ins.

M2000 server installation directory/res

Refers to the directory for storing resource files.

M2000 server installation directory/resourcemonitor

Refers to the directory for storing the resourcemonitoring files.

M2000 server installation directory/sacscript

Refers to the directory for storing the script filesprovided by the NIC module.

M2000 server installation directory/server

Refers to the directory for storing the dynamiclibrary files related to M2000 alarms.

M2000 server installation directory/sso

Refers to the directory for storing the SS0 programfiles.

M2000 server installation directory/swapfiles

Refers to the temporary switch directory.

M2000 server installation directory/tomcat

Refers to the directory for storing the configurationdata of the webpage server.

M2000 server installation directory/tools

Refers to the directory in which the common scripttools of the M2000.

M2000 server installation directory/var

Refers to the directory for storing the log files,performance files, and files recording exportedalarms.

M2000 server installation directory/uninstall

Refers to the directory for storing the script file usedfor uninstalling the M2000.

M2000 server installation directory/upgrade

Refers to the directory for storing the upgradescripts.



11-7


M2000 server installation directory/webapps

Refers to the directory for storing the webpageservice files.

/export/home/omc/var Refers to the directory for storing the M2000operation data.

/export/home/omc/var/syslog Refers to the directory for storing system logs.

/export/home/sysm/ftproot/pm Refers to the directory for storing the trafficmeasurement data of each NE, which is reported asfiles,.

M2000 server installation directory/var/itf_n/FileTransferIRP/PM

Refers to the directory for storing the northboundCORBA interface performance files.

/export/home/omc/var/fileint/cm Refers to the directory for storing the configurationdata files that are periodically exported.

/export/home/omc/var/fileint/pm Refers to the directory for storing the exportedperformance result files.

/export/home/sysm/ftproot/NEname/Software

Refers to the directory for storing the NE versionpackage.

/export/home/sysm/ftproot/NEname/Data/NE fdn

Refers to the directory for storing the NE databackup.NOTE

l The NE FDN is a code representing an NE sample inthe program.

l The data generated for manual backup is located in theBAKDATA****** directory. The data generated forautomatic backup is located in theAUTOBAKDATA****** directory.

/export/home/omc/var/logs Refers to the directory for storing the M2000 logfiles.

/opt/sybase/ASE-15_0/install Refers to the directory for storing the Sybase logfiles.

/var/adm Refers to the directory for storing the Solaris logfiles.

/export/home/backup/omc Refers to the directory for storing the backup filesof dynamic data.

/export/home/omc/var/etc/conf/license

Refers to the directory for storing the license file ofthe M2000.

/export/home/omc/sso Refers to the directory for storing the SSO datafiles.



Issue 03 (2010-08-31)

Sun Fire V890 Disk Planning and Disk Array Planning (HA System)In the HA system, the configuration of local disks on each server and the planning of diskpartitions are the same. Each Sun Fire V890 server is configured with six 146 GB hard disks,two of which are partitioned according to Table 11-3.

Table 11-3 Planning of the server disk partitions (HA, V890)

Hard DiskNo.

Partition No. Partition Name Size (MB) Description

1 0 / 110000 Root partition

1 swap 20000 Data exchangepartition

2 overlap - Disk mapping.Retain the defaultsize.

3 - - -

4 - - -

5 - - -

6 /globaldevices 1024 Reserved

7 - 10 to 260 Used for diskmirroring. Youneed not set thepartition name andsize. The systemassigns thepartition sizeautomatically.

2 Used as the mirrored disk for the first hard disk

Each Sun Fire V890 server is also configured with a 6140 disk array. Each 6140 disk arrayconsists of sixteen 146 GB hard disks. Two disks are used for hot spares, and the remaining 14disks are used for RAID5. Hot spares are used to replace the faulty disks when the disks on thedisk array have faults. Two volumes are created on each 6140 disk array. For details on how toplan volumes on the disk array, see Table 11-4.

Table 11-4 Planning for the 6140 disk array

Disk Array No. Volume Name Size (GB)

1 oss_v0 810

oss_v1 810

2 Used as the mirroring disk array for the first disk array



11-9

Sun Fire E4900 Disk Planning and Disk Array Planning (HA System)In the HA system, the configuration of local disks on each server and the planning of diskpartitions are the same. Each Sun E4900 server is configured with two 146 GB hard disks, whichare partitioned according to Table 11-5.

Table 11-5 Planning of the server disk partitions (HA, E4900)

Hard Disk No. PartitionNo.

PartitionName

Size (MB) Description

1 0 / 110000 Root partition

1 swap 20000 Data exchangepartition

2 overlap - Disk mapping.Retain the defaultsize.

3 - - -

4 - - -

5 - - -


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

Each Sun Fire V890 server is also configured with a 6140 disk array. Each 6140 disk arrayconsists of sixteen 146 GB hard disks. Two disks are used for hot spares, and the remaining 14disks are used for RAID5. Hot spares are used to replace the faulty disks when the disks on thedisk array have faults. Two volumes are created on each 6140 disk array. For details on how toplan volumes on the disk array, see Table 11-6.

Table 11-6 Planning for the 6140 disk array


1 oss_v0 810

oss_v1 810

2 Used as the mirroring disk array for the first disk array



Issue 03 (2010-08-31)

Sun T5220 Disk Planning and Disk Array Planning (HA System)

In the HA system, the configuration and partition planning of the local hard disk on each serverare the same. The T5220 system should be configured with four 146 GB hard disks and oneS3100 or S2600 disk array. The S3100 disk array consists of 16 x 146 GB hard disks and theS2600 disk array consists of 12 x 450 GB hard disks. Two of the six hard disks are partitionedaccording to Table 11-7 while the other two are idle.

Table 11-7 Disk partition planning of the T5220 server

Hard DiskNo.

Partition No.

Partition Name Size (MB) Description

1

0 / 110000 Root partition

1 swap 20000 Swapping partition

2 overlap - Used for diskmapping. Retain thedefault size.

3 - - -

4 - - -

5 - - -



2 Used as the mirror disk of the first hard disk.

Each Sun T5220 server is configured with an S3100 disk array or an S2600 disk array.

l Each S3100 disk array consists of sixteen disks. Two disks are used as hot spares and theother fourteen disks are used as two RAID5s. Hot spares are used to replace the faulty disks.Two volumes of the same size are created on the disk array. For details, see Table 11-8.

l Each S2600 disk array consists of twelve disks. Two disks are used as hot spare disk andthe other ten disks are used as one RAID 10. Hot spares are used to replace the faulty disks.Three volumes of the same size are created on the disk array. For details, see Table 11-9.

Table 11-8 Planning for the S3100 disk array


1 oss_v0 810



11-11


oss_v1 810

2 Used as the mirrored disk array of the first disk array



1 oss_app0 671

oss_app1 671

oss_app2 671


Sun M4000/M5000 Disk Planning and Disk Array Planning (HA System)In the HA system, the configuration and partition planning of the local hard disk on each serverare the same. The M4000/M5000 system should be configured with two 146 GB hard disks andone S3200/6140 or S2600 disk array. The S3200/6140 disk array consists of 16 x 146 GB harddisks and the S2600 disk array consists of 12 x 450 GB hard disks. The two local hard disks arepartitioned according to Table 11-10.

Table 11-10 Disk partition planning of the M4000/M5000 server

Hard DiskNo.

Partition No.


1

0 / 110000 Root partition

1 swap 20000 Swapping partition

2 overlap - Used for diskmapping. Retain thedefault size.

3 - - -

4 - - -

5 - - -




Issue 03 (2010-08-31)

Hard DiskNo.

Partition No.



2 Used as the mirror disk of the first hard disk.

Each Sun M4000/M5000 server is configured with an S3200/6140 disk array or an S2600 diskarray.

l Each S3200/6140 disk array consists of sixteen disks. Two disks are used as hot spares andthe other fourteen disks are used as two RAID5s. Hot spares are used to replace the faultydisks. Two volumes of the same size are created on the disk array. For details, see Table11-11.

l Each S2600 disk array consists of twelve disks. Two disks are used as hot spare disk andthe other ten disks are used as one RAID 10. Hot spares are used to replace the faulty disks.Three volumes of the same size are created on the disk array. For details, see Table11-12.

Table 11-11 Planning for the S3200/6140 disk array


1 oss_v0 810

oss_v1 810




1 oss_app0 671

oss_app1 671

oss_app2 671




11-13

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

Prerequisite

Log in to the server as user omcuser through SSH mode. In the HA system, log in to the twonodes.

Procedure

Step 1 Run the following command to viewing the disk usage of the M2000 server.

-bash-3.00$ df -k

The system displays the following information:

Filesystem 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

11.2.3 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



Issue 03 (2010-08-31)

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:

– 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"?>



11-15

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

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 through SSH mode.2. Change to the Sybase installation directory.



Issue 03 (2010-08-31)

By default, the installation directory is /opt/sybase.

-bash-3.00$ cd /opt/sybase3. Run the environment variable.

-bash-3.00$ . .profile4. Access the Sybase database and run the following commands:


1> use omcdb

2> go

1> select fdn,neName from tbl_AllNeInfo

2> go

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. Change to the /opt/OMC/var/med directory to delete the folders of associated FDNs

that are not listed in the database.

-bash-3.00$ rm -r /opt/OMC/var/med/neNE fdn

----End



11-17

12 Backing Up and Restoring the M2000(HA)

About This Chapter

This chapter describes how to back up and restore the M2000 HA system.

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

12.1 M2000 Backup and Restore SolutionsThis section describes the backup scheme, backup strategy, and restore scenarios of M2000dynamic data.

12.2 Backing Up and Restoring M2000 Dynamic Data (HA)This section describes how to back up and restore the dynamic data in the M2000 HA system.

HA System Administrator Guide (Sun, S10) 12 Backing Up and Restoring the M2000 (HA)


12-1

12.1 M2000 Backup and Restore SolutionsThis section describes the backup scheme, backup strategy, and restore scenarios of M2000dynamic data.

12.1.1 Backup of M2000 Dynamic DataThis section describes the backup of the M2000 dynamic data.

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

12.1.3 Scenarios of M2000 Data RestorationThis section describes the dynamic data restore for typical scenarios.

12.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 12-1.

Table 12-1 Introduction to dynamic data backup

Item Contents

Backup Contents l Database dataFor details see 10.1 M2000 Database.

l M2000 system filesFiles 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.

You need to back up only the active node of the HA system.

12 Backing Up and Restoring the M2000 (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

Item Contents

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.

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.



12-3

NOTE

When the M2000 system performs the dynamic data backup, do not perform operations such as modifyingthe configuration database.

12.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 Backup

Dynamic data backup is applicable to routine maintenance.

Rules for Naming Backup Files of Dynamic Data

When backing up the static data, name the backup files in the following format: /export/home/backup/omc/*-YYYYMMDDhhmmss.tar, where, * indicates all for full backup or inc 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 Data

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

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



Issue 03 (2010-08-31)

12.2 Backing Up and Restoring M2000 Dynamic Data (HA)This section describes how to back up and restore the dynamic data in the M2000 HA system.

12.2.1 Setting a Storage Device of Backup Data Through the Client (HA)This section describes how to set a storage device of backup data through the client.

12.2.2 Periodically Backing Up the M2000 Dynamic Data (HA)This section describes how to periodically back up the M2000 dynamic data.

12.2.3 Manually Backing Up the M2000 Dynamic Data (HA)This section describes how to manually back up the M2000 dynamic data.

12.2.4 Restoring the M2000 Dynamic Data (HA)This section describes how to restore the dynamic data of the M2000 HA system.

12.2.1 Setting a Storage Device of Backup Data Through the Client(HA)

This section describes how to set a storage device of backup data through the client.

Prerequisitel The M2000 server is running properly.

l The connection between the M2000 client and the M2000 server is normal.

ContextYou can set the storage device of backup data when the M2000 services are running. The storagedevices are as follows:

l DiskThe backup files of the dynamic data are stored on a hard disk.

l Tape or Disk and TapeTapes are not easy for future management, and therefore do not use Tape or Disk andTape as a storage device.To copy the dynamic data to a tape, you need to manually copy the backup data from thehard disk to a tape after the dynamic data is backed up on a hard disk. For details, see 16.3.4How Do I Copy the Backup Dynamic Data from a Hard Disk to a Tape (HA, Sun).

l VeritasVeritas refers to the storage device of the NetBackup server. If a storage device is set toVeritas, the system automatically packs the backup data and moves the backup data to thestorage device of the NetBackup server. Then, the M2000 server does not keep any backupdata.



12-5

CAUTIONl Do not modify the configuration files of a storage device when the backup is in process.

l Do not replace a storage device when the backup is in process.

l To prevent the dynamic data backup files that are stored on a local hard disk from missing,you are advised to select Veritas for data backup.

Procedure

Step 1 Start the M2000 client and log in to the M2000 server.

Step 2 Click Maintenance > Backup Management > System Backup. The System Backup interfaceis displayed, as shown in Figure 12-1.

Figure 12-1 Setting a storage device (I)

Step 3 Click Reset. Select a storage device in the displayed Medium Type Setting dialog box, andthen click OK, as shown in Figure 12-2.

Figure 12-2 Setting a storage device (II)

Step 4 The Confirm dialog box is displayed, prompting you for a full backup after you change thestorage device. Click Yes.



Issue 03 (2010-08-31)

Step 5 When the storage device is changed, the Message dialog box is displayed. Click OK.

Step 6 Perform a full backup.

For details, see 12.2.3 Manually Backing Up the M2000 Dynamic Data (HA).

----End

12.2.2 Periodically Backing Up the M2000 Dynamic Data (HA)This section describes how to periodically back up the M2000 dynamic data.


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.

ContextGenerally, the M2000 dynamic data is backed up periodically. The periodic backup of thedynamic data is performed in full backup mode.In an HA system, if you want to copy the dynamicdata to a tape, it is recommended that you manually copy the backup data from the hard disk toa tape after the dynamic data is backed up on a hard disk. For details, see 16.3.4 How Do I Copythe Backup Dynamic Data from a Hard Disk to a Tape (HA, Sun).

NOTE

The time required for backing up M2000 dynamic data is related to the actual environment. Generally, ittakes about five hours.

Do not suspend a periodic backup task. The reasons are as follows:



Procedure

Step 1 On the main window, choose Maintenance > Task Management.The Task Management dialog box is displayed.




12-7







Issue 03 (2010-08-31)


Step 5 Click OK.


----End

12.2.3 Manually Backing Up the M2000 Dynamic Data (HA)This 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.



12-9

l In an HA system, if you want to copy the dynamic data to a tape, it is recommended thatyou manually copy the backup data from the hard disk to a tape after the dynamic data isbacked up on a hard disk. For details, see 16.3.4 How Do I Copy the Backup DynamicData from a Hard Disk to a Tape (HA, Sun).

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 > System Backup. TheSystem Backup dialog box is displayed.

Figure 12-5 Manual backup

If Backup Medium in Figure 12-5 does not meet the actual requirement, you can click Resetto change the backup medium before data backup. For details, see 12.2.1 Setting a StorageDevice of Backup Data Through the Client (HA).

Step 2 In the System Backup dialog box shown in Figure 12-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.

----End

12.2.4 Restoring the M2000 Dynamic Data (HA)This section describes how to restore the dynamic data of the M2000 HA system.



Issue 03 (2010-08-31)

Prerequisitel You have logged in to the active node as user root through SSH mode by using the

corresponding IP address.l You have obtained the backup files for restoring the dynamic data.

l The Sybase database service is running properly on the active node.

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.

After the dynamic data is backed up, the dynamic data backup package is generated on the harddisk. You can copy the backup package to tapes. In this case, you need to copy the backup datato the hard disk before you restore the dynamic data. For details, see 16.3.5 How Do I Copy theBackup Dynamic Data from a Tape to a Hard Disk (HA, Sun).

NOTE

The time required for restoring M2000 dynamic data is related to the actual environment. Generally, ittakes about six hours.

Procedure

Step 1 Perform the following operations on the active node to restore the M2000 data:1. Decompress the backup file that stores the to-be-restored dynamic data.

# cd /export/home/backup/omc

# tar xf backup file that stores dynamic data

For example, if you need to restore the full backup file generated on 18:06:22 2008-01-30,decompress the relevant package.

# tar xf all-20080130180622.tar

NOTE

You need to decompress the relevant package regardless of the full backup file or the incrementalbackup file that is to be restored. For example, there are two packages available:all-20080130180622.tar and inc-20080131180622.tar. If you need to restore the system to the historyoperational status of 18:06:22 2008-01-30, decompress all-20080130180622.tar. If you need torestore the system to the history operational status of 18:06:22 2008-01-31, you need to decompressonly inc-20080131180622.tar. You need not decompress all-20080130180622.tar.

2. Navigate to the path after the decompression.

# cd name of the backup file that stores dynamic data

For example:

# cd all-20080130180622



12-11

3. Run the following script to restore dynamic data:

# ./restore.sh

4. When the system displays the following message, type the password of user sa of thedatabase.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 message, type 1 to start restoring 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 2 Run the following command on the active node to start the M2000 services:


# cd /opt/OMC/tools/common

# ./commonop.sh -ostartsvc

l If the system displays the following information, you can infer that the M2000 service isstarted. In such a case, proceed with Step 3 and Step 4.Operation succeeds

l If the system displays the following information, you can infer that the M2000 service failsto be started. In such a case, do not proceed with Step 3 or Step 4. Instead, contact Huaweitechnical support engineers for assistance.Performing Start OMC services failed

NOTE

Starting the M2000 service takes a long time. Wait with patience.

Step 3 Run the following command on the standby node to check whether there is any system output:


# daem_ps

l If there is any system output, you can infer that the daem process is started.



Issue 03 (2010-08-31)

l If there is no system output, you can infer that the daem process is not started. Run thefollowing commands to start it:# start_daem -type standby

Step 4 Run the following commands on the active node 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



12-13

13 M2000 Routine Maintenance (HA)

About This Chapter

This chapter lists the maintenance items and provides guidance for the routine maintenance ofthe M2000 HA system. You can add or delete the maintenance items based on requirements.

13.1 M2000 Routine Maintenance Items (HA)This section describes the recommended maintenance items of the M2000 HA system.

13.2 Daily Maintenance Operations (HA)This section describes the daily maintenance operations that need to be performed on theM2000 HA system.

13.3 Weekly Maintenance Operations (HA)This section describes the weekly maintenance operations that need to be performed on theM2000 HA system.

13.4 Monthly Maintenance Operations (HA)This section describes the monthly maintenance operations that need to be performed on theM2000 HA system.

HA System Administrator Guide (Sun, S10) 13 M2000 Routine Maintenance (HA)


13-1

13.1 M2000 Routine Maintenance Items (HA)This section describes the recommended maintenance items of the M2000 HA system.

Table 13-1 lists the recommended maintenance items of the M2000. You can add or deletemaintenance items according to the actual requirement.

Table 13-1 List of maintenance items

No. Item MaintenancePeriod

Reference

1 Check the cluster status. Daily The cluster status is normal.

2 Check the status ofperformance measurement.

Daily All measurement counters andmeasurement objects are beingmeasured.

3 Check the loss ofperformance results.

Daily No performance result is lost.

4 Check the status of alarmreception.

Daily The alarms reported by NEs arereceived in real time.

5 Check the status of the NMSconnection.

Daily The NMS can collect the alarms andperformance data reported by theM2000.

6 Check the status of the alarmbox.

Daily The alarm box can report the M2000alarms in real time.

7 Check OMC alarms orevents.

Daily No OMC alarm or event is generated.

8 Check the connectionbetween the M2000 andNEs.

Daily The connection between the M2000 andNEs is normal.

9 Check the M2000 logs. Daily The system runs properly. No abnormalor malicious operations are performed.

10 Check the error logs of theSolaris operating system.

Daily No error log is generated.

11 Check the hard disk usage ofthe M2000 server.

Daily The usage of each disk is less than 90%.

12 Check the status of theM2000 database.

Daily The database runs properly and its usageis less than 80%.

13 Check the M2000 services(HA).

Daily All the services run properly, and noservice is in not running state.

13 M2000 Routine Maintenance (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)


Reference

14 Check the core file of theserver.

Daily No core file exists in the /export/home/omc/var/logs directory.

15 Check the hardware of theM2000 server.

Daily The hardware of the M2000 server is notdamaged.

16 Check the results collectedby the SMC.

Daily The operating environment of theM2000 server is normal.

17 Check the configuration ofalarm timing tasks.

Weekly The time of alarm timing tasks is setproperly. This prevents the time conflictwith background tasks. The conflictmay result in heavy CPU load.

18 Check the configuration ofautomatic log dump.

Weekly The time of automatic log dump is setproperly. This prevents the time conflictwith background tasks. The conflictmay result in heavy CPU load.

19 Check the configuration ofNE log synchronizationtime.

Weekly The time of NE log synchronization isset properly. This prevents the timeconflict with background tasks. Theconflict may result in heavy CPU load.

20 Check the configuration ofthe file server.

Weekly The file server is configured properly.

21 Check the configuration ofthe system backup.

Weekly The time for automatically andperiodically backing up the M2000server and NEs is set properly. Backupfiles are generated in disks.

22 Check the configuration ofsystem monitoring.

Weekly The threshold of system monitoring isset properly.

23 Check the configuration ofNE configurationsynchronization time.

Weekly The time of NE configurationsynchronization is set properly.

24 Check the managementcapability of the M2000.

Weekly The number of equivalent NEs managedby the M2000 does not exceed themanagement capability of the M2000.

25 Check the status of theM2000 routes.

Weekly The corresponding startup files exist inthe /etc/rc2.d directory.

26 Back up the M2000. Weekly Back up the M2000 database andsystem files. View the backup files ondisks and tapes.

27 Check the time of theM2000 server.

Weekly The time of the M2000 server is correct.



13-3


Reference

28 Check the disk status of theM2000.

Weekly All the disks that are in use areonline, the KSTATE columns of pl,sd, and v are ENABLED, and theSTATE columns are ACTIVE. Theusage of each partition is less than 80%.

29 Check the power supply ofthe M2000 server.

Monthly The power supply is normal.

30 Check the peripherals of theM2000 server.

Monthly For details about how to check the CD-ROM drive and the tape drive, refer tothe Solaris Administrator Guide.

31 Check the timeout forstopping the M2000application resources.

Monthly The timeout for stopping the M2000application resources is set correctly.

32 Check the trust between twoservers in an HA system.

Monthly The trust between two servers in an HAsystem is normal.

33 Check the version of the SunCluster software.

Monthly The version number of the Sun Clustersoftware is the same on both nodes.

34 Check the global devices ofan HA system.

Monthly Both the active and standby nodes canidentify the shared disk.

35 Check the logical host of anHA system.

Monthly The active/standby relation of thelogical host of the HA system is normal.

36 Check the right and ownerof the /opt/SUNWscsyb/bin/sybase_stop_serversfile.

Monthly The right and owner of the /opt/SUNWscsyb/bin/sybase_stop_serv-ers file are set correctly.

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

13.2 Daily Maintenance Operations (HA)This section describes the daily maintenance operations that need to be performed on theM2000 HA system.

13.2.1 Checking the Cluster Status (HA)This section describes how to check the cluster status. Checking the cluster status enables youto ensure that the Cluster runs properly.

13.2.2 Checking the Status of Performance Measurement



Issue 03 (2010-08-31)

This section describes how to check the performance measurement state. You must ensure thatall the required measurement counters and measurement objects are in proper status.

13.2.3 Checking the Missing Performance ResultTo ensure that no result is lost, you must check that the missing performance result exists.

13.2.4 Checking the Alarm ReceptionCheck the alarm reception and ensure that the M2000 can receive alarms from NEs in real time.

13.2.5 Checking the NMS ConnectionThis section describes how to check the NMS connection and to ensure that the NMS connectionis normal.

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

13.2.7 Checking the Owner of the M2000 File SystemThis section describes how to check the owner of the M2000 file system. You need to check theowner of the M2000 file system regularly to ensure proper user operations because some toolsor operations may change the owner of the M2000 file system.You need to perform this operationon both node 1 and node 2.

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

13.2.9 Checking Connections Between the M2000 and NEsThis section describes how to check the connections between the M2000 and NEs.

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

13.2.11 Checking the Error Log of the SolarisThis section describes how to check the error logs of the Solaris operating system.

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

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

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

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

13.2.16 Checking the Hardware of the M2000 ServerThis section describes how to check the M2000 server hardware.

13.2.17 Checking the SMC Collection Results



13-5

This section describes how to check the SMC collection results and to ensure that the M2000server environment is normal.

13.2.1 Checking the Cluster Status (HA)This section describes how to check the cluster status. Checking the cluster status enables youto ensure that the Cluster runs properly.

PrerequisiteLog in to the active or standby node as user root through SSH mode.

Procedure

Step 1 Run the scstat command.

# scstat

Step 2 Check the command result. Ensure that the status of the cluster is normal.

The command result is listed in Table 13-2.

Table 13-2 Result of the scstat command

Parameter Description of the Command Result

Cluster Nodes Both nodes are online.

Cluster TransportPaths

Two Transport paths are available, and both areonline.

Quorum Votes by Node Both nodes are online.

Quorum Votes byDevice

The device status is online.

Device GroupServers

The active server configured in ossdg is the active node, andthe backup server is the backup node.

Device GroupStatus

The ossdg device group is online.

Resource Groupsand Resources

The oss_rg resource group includes: osssvr,ossdg_rs,sybase_rs, and ossapp_rs.

Resource Groups The oss_rg is online on the active node, and offlineon the backup node.

Resources All resources are online on the active node, and offlineon the backup node.

If the system is configured with a tape drive, rmt/1 and rmt/2 are displayed and both areoffline.

----End



Issue 03 (2010-08-31)

13.2.2 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 > Measurement Management.

The Measurement Management window is displayed.

Step 2 Ensure that all the required measurement counters and the measurement objects on theMeasurement Status tab page are in proper status. If there is any exception, contact Huaweitechnical support engineers for assistance.

----End

13.2.3 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 > Measurement Management.

Step 2 From the navigation tree of the Measurement Status tab page, 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.



13-7

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.

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

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

13.2.5 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

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



Issue 03 (2010-08-31)

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

13.2.7 Checking the Owner of the M2000 File SystemThis section describes how to check the owner of the M2000 file system. You need to check theowner of the M2000 file system regularly to ensure proper user operations because some toolsor operations may change the owner of the M2000 file system.You need to perform this operationon both node 1 and node 2.

PrerequisiteLog in to the M2000 server as user root through SSH mode.

Procedure

Step 1 Run the following commands to check whether the owner of the M2000 file system is correct:


# . /opt/OMC/lbin/checkOSSRight.sh

If the system output contains the information like Error, run the . /tmp/modifyRight.shcommand to resume the owner of the M2000 file system.

Error: The rights of some OSS files are set incorrectly! You can execute the /tmp/modifyRight.sh script to correct the settings.

If the system output contains the information like OK, you can infer that the owner of theM2000 file system is correct.

OK: No rights of OSS files are assigned to user root.

----End

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

Procedure

Step 1 Check whether the OMC icon is colored or an alarm is displayed on it in the topology view.



13-9

If the system is operational, no alarm is generated. That is, the OMC icon is not colored or noalarm balloon is displayed.

Step 2 Right-click the OMC icon, and then choose Query Alarm/Event > Alarm List.

The Browse Alarm List window is displayed.

l If the alarms listed in Table 13-3 are generated, handle the alarms immediately.

Table 13-3 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

The Cache for the Array Controller Is Faulty 202

Logical Drive Is Offline 203

Array Reconstruction Error 204

Physical Hard Disk Failed 205

Hard Disk Synchronization Error 206

The Temperature of the Disk Cabinet Is Abnormal 207

Fan Failure In The Disk Cabinet 208

Disk Cabinet Power Failed 209

Array Reconstruction 210

Reconstruct The Virtual Disk 212

Disk Cabinet Failure 214

Disk Physical State Is Changed 215



Issue 03 (2010-08-31)

Alarm Name Alarm ID

Host Power Failure 217

Host Power Cable Failure 218

Host Temperature Is Abnormal 219

Host Fan Is Abnormal 220

l If the alarms listed in Table 13-4 are generated, you need to clear them within one day.

Table 13-4 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

l During network expansion, multiple alarms listed in Table 13-5 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 clear the alarms.

Table 13-5 Alarms to be focused on during network expansion

Alarm Name Alarm ID

NE Is Disconnected 301

l If the alarms listed in Table 13-6 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 13-6 Alarms about malicious operations

Alarm Name Alarm ID

The Number of Login Attempts Reaches the Maximum 11

Step 3 Right-click the OMC icon, and then choose Query Alarm/Event > Event Logs from theshortcut menu.



13-11

The Query Event Logs window is displayed.

l If the events listed in Table 13-7 occur, you need to handle the events immediately.

Table 13-7 Events that need to be handled immediately

Event Name Event ID

The Battery for the Array Controller Is Faulty 201

Array Disk Is Offline 213

Disk Logical State Is Changed 216

l If the events listed in Table 13-8 occur, you need to handle them within one day.

Table 13-8 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 13-9 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 13-9 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:

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 Modify Experience dialog box, type the information such as the symptom, cause,

and recommended handling advice.



Issue 03 (2010-08-31)

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.

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

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



13-13

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

13.2.11 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 through SSH mode.

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.

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



Issue 03 (2010-08-31)

-bash-3.00$ more syslog

Step 4 Check the file for error information.

----End

13.2.12 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 11.2.3 Clearing theDisk Space of the M2000 Server.

Step 4 Check whether the disk usage of the M2000 server is within the normal range.

----End

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



13-15

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 10.3 Clearing M2000 Databases.

Step 4 Ensure that the database works properly.

The database usage is smaller than 90%.

----End

13.2.14 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 Monitor Browser window is displayed.

Step 2 Click the Service Monitor or Monitor Browser tab to monitor the processes running on theM2000 server.


If an process is suspended or abnormal, you should log in to the M2000 server as user root, stopit using kill_svc. If a service or process is inactive, start the service or the process usingscswitch -e -j ossapp_rs.

Step 4 Check whether the M2000 works properly.

The Status of all M2000 services is Running.

----End

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

PrerequisiteLog in to the server as user omcuser through SSH mode.

Procedure

Step 1 Go to the /export/home/omc/var/logs directory.



Issue 03 (2010-08-31)

-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

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


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

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



13-17

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

13.3 Weekly Maintenance Operations (HA)This section describes the weekly maintenance operations that need to be performed on theM2000 HA system.

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

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

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

13.3.4 Checking the Configuration of the File ServerThis section describes how to check whether the configuration of the file server is appropriate.

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

13.3.6 Checking the Configuration of System MonitoringThis section describes how to check the configuration of system monitoring.

13.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 together with other tasks on the server is performed at the same time.

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

13.3.9 Checking the Status of the M2000 RoutesThis section describes how to check the configuration of the M2000 routes.

13.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,



Issue 03 (2010-08-31)

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.

13.3.11 Checking the Time of the M2000 Server (HA)This section describes how to check the time of the M2000 server.

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

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


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/Event Log Dump 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

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





13-19

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 theleft 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 theleft pane, select NE Security Log.


3. Check the configuration of auto NE security log dump in the Attribute window.


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 theleft pane, select NE System Log.


3. Check the configuration of auto NE system log dump in the Attribute window.


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 theleft pane, select NM Operation Log Dump.


3. Check the configuration of auto NM operation log dump in the Attribute window.


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 theleft pane, select NM System Log Dump.


3. Check the configuration of auto NM system log dump in the Attribute window.


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 theleft pane, select NM Security Log Dump.


3. Check the configuration of auto NM security log dump in the Attribute window.


----End



Issue 03 (2010-08-31)

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

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

Procedure

Step 1 Choose Software > File Server Setting.

The File Server Setting window is displayed.

Step 2 Select the NE type in the ROOT navigation tree in the left pane.

Step 3 Check the name and IP address of the file server in the right pane.

Step 4 Ensure that the configuration of the file server is appropriate.

----End



13-21

13.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 through SSH mode. Check whether backup filesexist in the backup directory of both the M2000 server and NEs.

You can specify the backup directory for the M2000 server and NEs based on the attributeinformation.

----End

13.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%.



Issue 03 (2010-08-31)

Procedure

Step 1 Choose Monitor > System Monitor > Settings.

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 13-10.



13-23














Issue 03 (2010-08-31)










Table 13-11 describes the parameters for monitoring the disks of the server.



13-25














l Minor: 70

l Major: 80

l Critical: 90


l Minor: 65

l Major: 75

l Critical: 85



Issue 03 (2010-08-31)


Advanced Setting(%)









Table 13-12 describes the parameters for monitoring the database of the server.









13-27








l Minor: 90

l Major: 95

l Critical: 98



Issue 03 (2010-08-31)


Advanced Setting(%)







– Minor: 90

– Major: 95

– Critical: 98


Table 13-13 describes the parameters for monitoring the server services.









13-29




monitor client by

or .NOTE




is displayed.

l You can double-



13.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 together with other tasks on the server is performed at the same time.


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.



Issue 03 (2010-08-31)

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

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

13.3.9 Checking the Status of the M2000 RoutesThis section describes how to check the configuration of the M2000 routes.

PrerequisiteLog in to the M2000 server as user root through SSH mode.

Procedure

Step 1 Check the configuration of the current route.

# netstat -rnv

----End

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



13-31

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:



ProcedureStep 1 On the main window, choose Maintenance > Task Management.

The Task Management dialog box is displayed.








Issue 03 (2010-08-31)


Step 5 Click OK.


----End

13.3.11 Checking the Time of the M2000 Server (HA)This section describes how to check the time of the M2000 server.


Procedure

Step 1 Check the time of the M2000 server.

# date

The server time is displayed, for example:

Tue Mar 29 00:35:24 MEST 2005

Step 2 If the M2000 server is configured with the NTP service, run the command ps -ef | grep ntp |grep -v grep to check whether the NTP service is started. Ensure that the NTP service is started



13-33

and check the service status according to 4.5.7 Checking the Running Status of the NTPService on the M2000 Server (HA).

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 4 Setting the M2000Time (HA).

l If the M2000 is configured with the NTP service and the NTP service is not running properly,handle the problem according to 4.5 Configuring the NTP Service of the M2000 (HA).

Step 4 Check whether the M2000 works properly.

Ensure that the server time is correct.

----End

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

PrerequisiteLog in to the M2000 server as user root through SSH mode. In the HA system, log in to theactive node.

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



Issue 03 (2010-08-31)

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 11.2.3 Clearing the Disk Space of the M2000 Server.

----End

13.4 Monthly Maintenance Operations (HA)This section describes the monthly maintenance operations that need to be performed on theM2000 HA system.

13.4.1 Checking the Power Supply of the M2000 ServerThis section describes how to check the power supply of the M2000 server.

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

13.4.3 Checking the Timeout for Stopping the M2000 Application ResourcesThis section describes how to check the preset timeout for stopping the M2000 applicationresources to ensure that the value is correct.

13.4.4 Checking the Trust Between Two Servers in an HA SystemThis section describes how to check the trust between two servers in an HA system to ensurethat the trust is normal.

13.4.5 Checking the Version of the Sun Cluster SoftwareThis section describes how to check the version of the Sun Cluster software to ensure that theversion number is the same on both nodes.

13.4.6 Checking the Global Devices of an HA SystemThis section describes how to check the global devices of an HA system to ensure that both theactive and standby nodes can identify the shared disk.

13.4.7 Checking the Logical Host of an HA SystemThis section describes the logical host of an HA system to ensure that the active/standby relationis normal.

13.4.8 Checking the Right and Owner of the /opt/SUNWscsyb/bin/sybase_stop_servers FileThis section describes how to ensure that the right and owner of the /opt/SUNWscsyb/bin/sybase_stop_servers file are set correctly.

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


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



13-35

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

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

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.



Issue 03 (2010-08-31)


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

13.4.3 Checking the Timeout for Stopping the M2000 ApplicationResources

This section describes how to check the preset timeout for stopping the M2000 applicationresources to ensure that the value is correct.

PrerequisiteLog in to the active node as user root through SSH mode.

ContextWhen the preset timeout for stopping the M2000 application resources is less than 1,800s, thesystem uses the kill_daem command to forcibly stop the M2000 services if the services are notstopped within 30 min. As a result, the M2000 services are disrupted abnormally.

Procedure

Step 1 Run the following command on the active node to check the timeout for stopping the M2000application resources:

# scha_resource_get -G oss_rs -R ossapp_rs -O STOP_TIMEOUT


1800

The displayed value is the timeout for stopping the M2000 application resources.

l If the displayed value is 1800, you need not perform the following operations.

l If the displayed value is not 1800, proceed with Step 2 through Step 3.

Step 2 Run the following command on the active node to change the timeout for stopping the M2000application resources:

# scrgadm -c -j ossapp_rs -y STOP_TIMEOUT=1800

Step 3 Run the following command on the active node to check whether the timeout for stopping theM2000 application resources is correct:

# scha_resource_get -G oss_rs -R ossapp_rs -O STOP_TIMEOUT

----End



13-37

13.4.4 Checking the Trust Between Two Servers in an HA SystemThis section describes how to check the trust between two servers in an HA system to ensurethat the trust is normal.

PrerequisiteLog in to the active and standby nodes as user root through SSH mode.

ContextTrust is the mutually trustful relation configured for a specified user between two servers. Thespecified user need not type a password when logging in to the mutually trustful server in Rloginmode, and owns all the rights on another server. Trust is required in operations related to versionupgrade and data collection.

Procedure

Step 1 Run the following command on the active and standby nodes to obtain the host name of theserver:

# hostname

Step 2 Run the following command on the active node to log in to the standby node:

# rsh host name of the standby node

l If no password is required for login, you can infer that the trust between the active node andthe standby node is normal. In this case, run the exit command to return to the command linewindow of the active node, and then proceed with Step 3.

l If the system prompts you to type a password, you can infer that the trust between the activenode and the standby node is abnormal. In this case, you need to type a correct password forlogin before running the exit command to return to the command line window of the activenode. Then, proceed with Step 4.

Step 3 Run the following command on the standby node to log in to the active node:

# rsh host name of the active node

l If no password is required for login, you can infer that the trust between the active node andthe standby node is normal, that is, the trust between the two servers in the HA system isnormal. In this case, run the exit command to return to the command line window of thestandby node. You need not perform the following operations.

l If the system prompts you to type a password, you can infer that the trust between the activenode and the standby node is abnormal. In this case, you need to type a correct password forlogin before running the exit command to return to the command line window of the standbynode. Then, proceed with Step 4.

Step 4 Run the following command on the active and standby nodes to modify the /.rhosts file, that is,add the host names of the two nodes to this file:

# TERM=vt100; export=TERM

# vi /.rhosts

After the file is modified, press Esc and then run the :wq! command to save the modificationand exit.



Issue 03 (2010-08-31)

NOTE

If the host names of the two nodes are available in the file, you need not modify the file. Press Esc and runthe :q command to exit.

Step 5 Repeat Step 2 and Step 3 to check the trust between the two servers in the HA system.

If the trust is abnormal, contact Huawei technical support engineers for assistance.

----End

13.4.5 Checking the Version of the Sun Cluster SoftwareThis section describes how to check the version of the Sun Cluster software to ensure that theversion number is the same on both nodes.

Prerequisitel Log in to the active and standby nodes as user root through SSH mode.

l The Sun Cluster software is installed.

Procedure

Step 1 Run the following command on both nodes to check the version of the Sun Cluster software:

# scinstall -pvv


Sun Cluster 3.2 for Solaris 10 sparcAccording to the preceding information, you can infer that the version of the Sun Cluster softwareis 3.2.

If the version number of the Sun Cluster software is different on the two nodes, contact Huaweitechnical support engineers for assistance.

----End

13.4.6 Checking the Global Devices of an HA SystemThis section describes how to check the global devices of an HA system to ensure that both theactive and standby nodes can identify the shared disk.

PrerequisiteLog in to the active node as user root through SSH mode.

Procedure

Step 1 Run the following command to display the information about the current global devices:

# scdidadm -L


1 osssvr-1:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1 2 osssvr-1:/dev/rdsk/c1t0d0 /dev/did/rdsk/d2 3 osssvr-1:/dev/rdsk/c1t1d0 /dev/did/rdsk/d3



13-39

4 osssvr-1:/dev/rdsk/c4t600A0B800048F980000018D749D4539Ed0 /dev/did/rdsk/d4 4 osssvr-2:/dev/rdsk/c4t600A0B800048F980000018D749D4539Ed0 /dev/did/rdsk/d4 5 osssvr-1:/dev/rdsk/c4t600A0B800048F980000018D449D45312d0 /dev/did/rdsk/d5 5 osssvr-2:/dev/rdsk/c4t600A0B800048F980000018D449D45312d0 /dev/did/rdsk/d5 6 osssvr-1:/dev/rdsk/c4t600A0B800048F82C000019E74AAD5AAEd0 /dev/did/rdsk/d6 6 osssvr-2:/dev/rdsk/c4t600A0B800048F82C000019E74AAD5AAEd0 /dev/did/rdsk/d6 7 osssvr-1:/dev/rdsk/c4t600A0B800048F82C000019DA4AAD597Ad0 /dev/did/rdsk/d7 7 osssvr-2:/dev/rdsk/c4t600A0B800048F82C000019DA4AAD597Ad0 /dev/did/rdsk/d7 8 osssvr-2:/dev/rdsk/c0t0d0 /dev/did/rdsk/d8 9 osssvr-2:/dev/rdsk/c1t0d0 /dev/did/rdsk/d9 10 osssvr-2:/dev/rdsk/c1t1d0 /dev/did/rdsk/d10

The information similar to /dev/rdsk/c4t600A0B800048F980000018D749D4539Ed0 /dev/did/rdsk/d4 is theinformation about the logical partitions of the disk array. In the HA system, the disk array isshared by both nodes. Therefore, each logical partition belongs to both nodes, for example:

osssvr-1:/dev/rdsk/c4t600A0B800048F980000018D749D4539Ed0 /dev/did/rdsk/d4 osssvr-2:/dev/rdsk/c4t600A0B800048F980000018D749D4539Ed0 /dev/did/rdsk/d4

If the logical partitions of the disk array in the system output belongs to only one node, you needto contact Huawei technical support engineers for assistance.

----End

13.4.7 Checking the Logical Host of an HA SystemThis section describes the logical host of an HA system to ensure that the active/standby relationis normal.


Procedure

Step 1 Run the following command on either node to determine the active node and the standby node:

# scstat -D

In the system output, the node corresponding to the Primary column is the active node and thenode corresponding to the Secondary column is the standby node. Normally, node 1 is the activenode and node 2 is the standby node. If the active/standby relation is abnormal, contact Huaweitechnical support engineers for assistance.

----End

13.4.8 Checking the Right and Owner of the /opt/SUNWscsyb/bin/sybase_stop_servers File

This section describes how to ensure that the right and owner of the /opt/SUNWscsyb/bin/sybase_stop_servers file are set correctly.



Issue 03 (2010-08-31)


Procedure

Step 1 Run the following command on the active and standby nodes to check whether the right andowner of the sybase_stop_servers file is correct:

# ls -l /opt/SUNWscsyb/bin/sybase_stop_servers

-r-x------ 1 dbuser staff 2180 Oct 15 10:30 /opt/SUNWscsyb/bin/sybase_stop_servers

The owner and right of the sybase_stop_servers file are dbuser and r-x------ (500), respectively.

If the right and owner of the file are correct, you need not perform the following operations.

Otherwise, proceed with Step 2 and Step 3.

Step 2 Run the following commands on the active and standby nodes to change the right and owner ofthe sybase_stop_servers file:

# chmod 500 /opt/SUNWscsyb/bin/sybase_stop_servers

# chown dbuser:staff /opt/SUNWscsyb/bin/sybase_stop_servers

Step 3 Repeat Step 1 to check whether the right and owner of the sybase_stop_servers file are setcorrectly.

----End

13.4.9 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



13-41

14 M2000 Emergency Maintenance (HA)

About This Chapter

This chapter describes the emergency maintenance procedures for serious faults in the serverand clients of the M2000 HA system. These procedures include the emergency maintenance forthe server in the M2000 HA system and the M2000 clients, and the procedure for powering offthe M2000 server in exceptional situations.

14.1 Guide to Emergency Maintenance of the M2000 ServerThis provides guidance for emergency maintenance when serious faults occur in the M2000system.

14.2 Guide to Emergency Maintenance of the M2000 ClientThis section provides guidance for emergency maintenance of the M2000 client.

14.3 Guide to Emergency Maintenance of the M2000 Server in Case of Power Failure (HA)This provides guidance for emergency maintenance of the M2000 client.

HA System Administrator Guide (Sun, S10) 14 M2000 Emergency Maintenance (HA)


14-1

14.1 Guide to Emergency Maintenance of the M2000 ServerThis provides guidance for emergency maintenance when serious faults occur in the M2000system.

The M2000 server emergency maintenance is based on the backup. When serious faults occurin 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 Using the backup serverRestore the operating system from the backup server if a full system backup is made throughthe Veritas software.

l By reinstalling the operating system

NOTE

If the system is not backed up, all user data is lost if the system crashes due to fatal errors. In this case,reinstall the operating system.

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

14.3 Guide to Emergency Maintenance of the M2000 Serverin Case of Power Failure (HA)

This provides guidance for emergency maintenance of the M2000 client.

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

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

14.3.3 Troubleshooting: Loss of Database Device Files After the Restoration of the File System(HA)This section describes how to handle the loss of database device files after the restoration of thefile system.

14 M2000 Emergency Maintenance (HA) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

14.3.4 Troubleshooting: Failure to Restore the Database Though the File System Is Intact (HA)This section describes how to handle the failure to restore the database though the file systemis intact.

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

Symptom

The server cannot be started. The system displays the message Cannot open `/etc/path_to_inst` .

After resetting the server, you are not allowed to log in to the server through the SSH or Telnetand not allowed to ping the server. Use the serial port or the SC/RSC/XSCF port to view thefollowing information:

Cannot open `/etc/path_to_inst`Program terminated

The system stops functioning and is switched to the ok status.

Fault Handling

Unexpected power-off of the server damages the Solaris operating system. As a result, the 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



14-3

5. Run the following commands to reset the Solaris operating system:# sync; sync; sync; sync; sync; sync

# /usr/sbin/shutdown -g0 -y -i6

After the system starts, run the fsck -y command to restore the system file. Start the Sybaseand M2000 application manually.

14.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 SSH or Telnet.Use a serial port or the SC/RSC/XSCF port to view the following information:

WARNING - Unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c*t*d*s*). Exit the shell when done to continue the boot process.Type control-d to proceed with normal startup,(or give root password for system maintenance):

NOTE

The warning shows Unable to repair the / filesystem, where filesystem may refer 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 -y

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

CAUTIONIf the M2000 HA system uses Netra 240 servers, the database device files exist in the /export/home/sybase/data directory.

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 file



Issue 03 (2010-08-31)

disables 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 14.3.3 Troubleshooting: Loss of DatabaseDevice Files After the Restoration of the File System (HA).

14.3.3 Troubleshooting: Loss of Database Device Files After theRestoration of the File System (HA)

This section describes how to handle the loss of database device files after the restoration of thefile system.

SymptomIf a device file related to the system database, such as master.dat or sysprocs.dat, is lost, thedatabase fails to start.

If a device file related to some application database is lost, the corresponding applicationdatabase and the services related to this database fail to start.

Fault HandlingThe abnormal power-off leads to loss of the database device file in 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

CAUTIONWhen the Netra 240 server is used, the master.dat and sysprocs.dat files exist in the /export/home/sybase/data directory.

2. When installing the database, select reinstall to reestablish the application databases ofM2000. For details on the installation of the Sybase and the M2000 , refer to the softwareinstallation manual related to each server type.

3. Perform the full backup and incremental backup to restore the data in the database andM2000 configuration files.

14.3.4 Troubleshooting: Failure to Restore the Database Though theFile System Is Intact (HA)

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,



14-5

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.

NOTE





Fault Handling

The 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 through SSH mode and run theenvironment variable script. The default M2000 installation directory is /opt/OMC.# cd M2000 installation path


2. Switch to user dbuser and log in to the database as user sa. Then, run the followingcommands:# su - dbuser


1> sp_configure "allow updates", 1

2> go

1> update master..sysdatabases set status =-32768

2> where name="database_name"

3> go

1> exit

-bash-3.00$ exit

For details on how to stop the database service, see 16.2.3 How to Stop the Sybase (HA,Sun).



Issue 03 (2010-08-31)

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

As indicated in the command result, SYB.038 is the last history file.(2) Run the following command to use the last history file to restore /opt/sybase/

ASE-15_0/Database server name.cfg. This takes SYB and SYB.038, which are thedatabase server name and the last history file respectively, as an example.# cp SYB.038 SYB.cfg

# chown dbuser:staff SYB.cfg



14-7

4. Start the Sybase.For details about how to start the Sybase, see 16.2.2 How to Start the Sybase (HA,Sun).

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

-bash-3.00$ exit

For details on how to stop the database service, see 16.2.3 How to Stop the Sybase (HA,Sun).

For details about how to start the Sybase, see 16.2.2 How to Start the Sybase (HA,Sun).



Issue 03 (2010-08-31)

15 Troubleshooting the M2000

About This Chapter

This chapter describes the procedures for troubleshooting the M2000.

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

15.2 Collecting M2000 Site and Software InformationThis section describes how to collect the M2000 site and software information.

15.3 Collecting Fault Data Using the Log Information CollectorThis section describes how to collect fault data by using the M2000 log collector. You can alsocollect the information for locating faults by using the Trace Collection function of the OSMUsystem. For details, see the operation guide of the OSMU system.

HA System Administrator Guide (Sun, S10) 15 Troubleshooting the M2000


15-1

15.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 16.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.

15 Troubleshooting the M2000 HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

For details on the server faults, refer to the 16.3 About Server Software (HA, Sun).

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.

15.2 Collecting M2000 Site and Software InformationThis section describes how to collect the M2000 site and software information.

15.2.1 Collecting the M2000 Site InformationThis section describes how to collect the M2000 site information.

15.2.2 Collecting the Time of M2000 Fault OccurrenceThis section describes how to find out the time when M2000 faults occur.

15.2.3 Collecting the IP Address of the M2000 ServerThis section describes how to obtain the IP address of the M2000 server.

15.2.4 Collecting the Solaris VersionThis section describes how to obtain the version information about the Solaris.

15.2.5 Collecting Sybase Version InformationThis section describes how to collect the version information about the Sybase.

15.2.6 Obtaining the Version Information About the M2000This section describes how to obtain the version information about the M2000.

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



15-3

l Fault description

----End

15.2.2 Collecting the Time of M2000 Fault OccurrenceThis section describes how to find out the time when M2000 faults occur.

Procedure

Step 1 Log in to the server as user omcuser through SSH mode.

NOTEIf you fail to log in as user omcuser, log in as user root.

Step 2 Run the date command to check the time.

----End

Example

-bash-3.00$ date

Thu Jul 28 09:56:39 EDT 2005

15.2.3 Collecting the IP Address of the M2000 ServerThis section describes how to obtain the IP address of the M2000 server.

Procedure



Step 2 Run the ifconfig -a command to obtain the IP address, subnet mask, and MAC address of theM2000 server.

----End

Example

-bash-3.00$ 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

15.2.4 Collecting the Solaris VersionThis section describes how to obtain the version information about the Solaris.



Issue 03 (2010-08-31)

Procedure



Step 2 Run the uname -aX command to find out the version information about the Solaris operatingsystem.

----End

Example-bash-3.00$ uname -aX

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.

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



15-5

Example


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.

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.

15.2.6 Obtaining the Version Information About the M2000This section describes how to obtain the version information about the M2000.

Procedure



Step 2 Run the displayVersion command to obtain the version information about the M2000.

----End

Example

Change to /opt/OMC, which is the default installation path of the M2000 server software. Runthe following commands:



-bash-3.00$ displayVersion

------------------------OMC Version--------------------------Product Name: iManagerM2000Version: iManagerM2000V200R009ENGC00SPC805Release Date: 06/09/09

...



Issue 03 (2010-08-31)

15.3 Collecting Fault Data Using the Log InformationCollector

This section describes how to collect fault data by using the M2000 log collector. You can alsocollect the information for locating faults by using the Trace Collection function of the OSMUsystem. For details, see the operation guide of the OSMU system.

Contextl The start_collector process and the start_collector_agent process provide the service of the

log collector. The start_collector process runs on the active node. The start_collector_agentprocess runs on the active node or the standby node.

l The service of the log collector is started upon the startup of the operating system. You canmanually 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 .

The Log Information Collector dialog box is displayed, as shown in Figure 15-1.



15-7

Figure 15-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 active 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.

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.



Issue 03 (2010-08-31)

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 the start_collectorprocess is running on the active node and the start_collector_agent process is running on the node wherefault data collection is required. For example, if you select Standby Collection, the system collectsthe log information about the active and standby nodes. Therefore, you must ensure that thestart_collector process is running on the active node and that the start_collector_agent process isrunning on the active node and the standby node.

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.



15-9

16 FAQs (HA, Sun)

About This Chapter

This chapter describes some frequently asked questions (FAQs) and the answers regarding theM2000 HA system.

16.1 About Solaris (HA, Sun)This section describes some FAQs and their answers regarding the Solaris operating system.

16.2 About Sybase (HA, Sun)This section describes some FAQs and their answers regarding the Sybase.

16.3 About Server Software (HA, Sun)This section describes some FAQs and their answers regarding the M2000 server software.

HA System Administrator Guide (Sun, S10) 16 FAQs (HA, Sun)


16-1

16.1 About Solaris (HA, Sun)This section describes some FAQs and their answers regarding the Solaris operating system.

16.1.1 How Do I Log In to the M2000 Server as User root Through TelnetThis section describes how to log in as user root through Telnet.

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

16.1.3 How to Check the Status of the Tape DriveThis section describes how to check the status of the tape drive.

16.1.4 How Should I Select a Tape DriveIf there are multiple tape drives in the system, you need to select a tape drive for storing backupdata. For the server that is not equipped with an internal tape drive but has an external tape driveand the server that is equipped with an internal tape drive but is not equipped with an externaltape drive, the default tape drive is /dev/rmt/0.

16.1.5 How to View the Hardware Settings of the M2000 ServerThis section describes how to view the hardware settings of the M2000 server.

16.1.6 How to Check the Device Status of the M2000 ServerThis section describes the common commands used to check the device status of the M2000server.

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

16.1.8 How to Modify the Port Number of the FTP ServerBy 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.

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

16.1.10 How Should I Stop the NTP Service on the M2000 Server (HA)This section describes how to stop the NTP service on the M2000 server in an HA system.

16.1.11 How Do I Change the IP Address of the S3X00 Disk Array (Command Mode)This section describes how to change the IP address of the S3X00 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. The IP address of eachS3X00 disk array needs to be changed.

16.1.12 How Should I Change the IP Address of the 6140 Disk Array (Command Mode)This section describes how to change the IP address of the 6140 disk array in command mode.To change the IP address of the 6140 disk array, the server must be installed with the 6140management host software. You need to configure each disk array.

16.1.13 How Do I Change the IP Address of the S2600 Disk Array (Command Mode)

16 FAQs (HA, Sun) HA System Administrator Guide (Sun, S10)


Issue 03 (2010-08-31)

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.

16.1.14 What Should I Do When the CD-ROM Drive Cannot Read the CD-ROMThis section describes why the CD-ROM drive cannot read the CD-ROM and provides thesolution to this problem.

16.1.15 How to Handle the corrupt label - wrong magic number MessageThis section describes how to handle the corrupt label - wrong magic number message.

16.1.16 What Should I Do When the Server Disk Space Is InsufficientThis section describes what to do when the server disk space is insufficient.

16.1.17 How to Configuring the Monitoring Function of the S2600 Disk ArrayThis section describes how to configure the monitoring function of the S2600 disk array.

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

16.1.19 How Should I Uninstall the OceanStor Monitoring SoftwareThis section describes how to uninstall the OceanStor monitoring software.

16.1.20 How Should I Check the Running Status of the FTP Service on the M2000 ServerThis section describes how to check the running status of the FTP service on the M2000 server.

16.1.21 How Should I Start the FTP Service on the M2000 ServerThis section describes how to start the FTP service on the M2000 server.

16.1.22 How Should I Check the Running Status of the SFTP Service on the M2000 ServerThis section describes how to check the running status of the SFTP on the M2000 server.

16.1.23 How Should I Start the SFTP Service on the M2000 ServerThis section describes how to start the SFTP service on the M2000 server.

16.1.24 How Do I Log In to the Server in SSH ModeThis section describes how to log in to the server in SSH mode.

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

QuestionHow do I log in as user root through Telnet?

NOTE

The following operations are only applicable to the non-security hardening system, not applicable to thesecurity hardening system.



16-3

AnswerIf you fail to log in to the M2000 server as user root through Telnet, you can use the followingmethod to obtain the rights.

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. Run the following commands to enter the /opt directory. Then check whether the SEKsubdirectory exists in the directory.# cd /opt# lsIf the SEK subdirectory exists, the current system is a security hardening system, stop doingthe operations; if the SEK subdirectory does not exist, the current system is not a securityhardening system, continue to do the following operations.

3. Open /etc/default/login.# TERM=vt100; export TERM# vi /etc/default/login

4. Find CONSOLE=/dev/console. Comment this line off by adding # at the beginning of theline.

5. Save the changes and then exit the file.6. 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 7 again.l If the system output contains enabled, you can infer that the Telnet service is started

successfully.7. Start the Telnet service.

# svcadm enable telnet

16.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 through SSH mode.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.



Issue 03 (2010-08-31)

16.1.3 How to Check the Status of the Tape DriveThis section describes how to check the status of the tape drive.

Question

How do I check the server tape drive status?

Answer

If a built-in tape drive is installed, the server identifies the tape drive upon startup. For an externaltape drive, you must install it. To install an external Sun tape drive, such as Ultra 60, performthe following steps:

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 through SSH mode.6. Run the following command to check the status of the tape drive:

This part takes the logical device of the tape drive, that is, /dev/rmt/0, for example.# mt -f /dev/rmt/0n status

The commands mentioned earlier can be briefly written as mt status.Table 16-1 lists the output.

Table 16-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



16-5

16.1.4 How Should I Select a Tape DriveIf there are multiple tape drives in the system, you need to select a tape drive for storing backupdata. For the server that is not equipped with an internal tape drive but has an external tape driveand the server that is equipped with an internal tape drive but is not equipped with an externaltape drive, the default tape drive is /dev/rmt/0.

QuestionIf the system has multiple tape drives, which tape drive should be used for storing backup data?

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 system output shows only the logical device files that are preceded by 0, it indicates

that only one tape drive is connected.l If the system output 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 obtained 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 operation takes the logical device of the tape drive, that is, /dev/rmt/0, for example.# mt -f /dev/rmt/0 statusIf the system output is similar to the following information, it indicates that the tape driveis functioning well:HP DAT-72 tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file no= 0 block no= 0



Issue 03 (2010-08-31)

If a tape is not inserted or not identified correctly, or the inserted tape is a cleaning tape,the system displays the following information:/dev/rmt/0n: no tape loaded or drive offline

16.1.5 How to View the Hardware Settings of the M2000 ServerThis section describes how to view the hardware settings of the M2000 server.

QuestionHow to check the Sun server hardware configuration and memory size?

AnswerTo view settings about the server hardware, perform the following steps on the server:

1. Log in as user root through SSH mode.2. Check different items by running the commands listed in Table 16-2.

Table 16-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.

16.1.6 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 16-3 lists the commands often used for checking the device status.



16-7

Table 16-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 Filesystemanddiskpartitioning

Check the filesystem.

# more /etc/vfstab

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



Issue 03 (2010-08-31)

No.


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.

5 Tapedrive

Check the tapedrive status.

# mt stat

Rewind thetape.

# mt rewind

Forward onestep.

# mt fsr



16-9

No.


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

7 Floppy disk

Configure thefloppy disk.

# volcheck# mount -F pcfs /dev/diskette/floppy



Issue 03 (2010-08-31)

No.


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

16.1.7 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 11 10.0.119.150 - Aug 30 15:10 Platform

osssvr-1-sc0:SC>



16-11

16.1.8 How to Modify the Port Number of the FTP ServerBy 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 through SSH mode. In the HA system, you need to log into the two nodes separately.

2. Run the following command to modify the /etc/services file:# vi /etc/services

3. Identify the following line, change 21 to 1234, and then run the wq! command to save andexit 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.

16.1.9 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 through SSH mode.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:...BR Brazil



Issue 03 (2010-08-31)

CL 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 16-4.

Table 16-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

America/Bahia - Bahia



16-13

Country

Time ZoneName Remarks

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.

16.1.10 How Should I Stop the NTP Service on the M2000 Server(HA)

This section describes how to stop the NTP service on the M2000 server in an HA system.

Prerequisite

Log in to the active and standby nodes as user root through SSH mode.

Procedure

Step 1 Run the following command on active and standby nodes to check whether the NTP service isrunning:

# ps -ef | grep ntp



Issue 03 (2010-08-31)

l If the system displays the following information, perform Step 2 through Step 3 to stop theNTP service.root 24097 1 0 14:38:26 ? 0:00 /usr/lib/inet/xntpd -c /etc/inet/ntp.conf.cluster

l If no information is displayed, you can infer that the NTP service is stopped.

Step 2 Run the following command on active and standby nodes to stop the NTP service:

# kill -9 process ID

The example in Step 1 indicates that the process ID is 24097. Run the following command onactive and standby nodes to stop the NTP service:

# kill -9 24097

Step 3 Run the following command on active and standby nodes to check whether the NTP service isstopped:

# ps -ef | grep ntp

If the NTP service is running, perform Step 2 through Step 3 to stop it.

----End

16.1.11 How Do I Change the IP Address of the S3X00 Disk Array(Command Mode)

This section describes how to change the IP address of the S3X00 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. The IP address of eachS3X00 disk array needs to be changed.

Prerequisitesl Log in to the server as user root through SSH mode.

l The server communicates properly with the S3X00 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.



16-15

ProcedureThis takes the following change as an example to describe how to change the IP address of thedisk array.

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 192.168.8.100 up

2. Check whether the temporary subnet is configured properly.# ping 192.168.8.40If 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:2 10.10.10.100 up

5. Check whether the new IP address of controller B is set successfully.# ping New IP address of controller BIn this case, run the following command:# ping 10.10.10.40If the system displays the following information, then the temporary subnet is configuredproperly:PING 10.10.10.40 (10.10.10.40) 56(84) bytes of data.64 bytes from 10.10.10.40: icmp_seq=1 ttl=64 time=0.326 ms

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:



Issue 03 (2010-08-31)

# 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 AIn this case, run the following command:# ping 10.10.10.39If the system displays the following information, then the temporary subnet is configuredproperly:PING 10.10.10.39 (10.10.10.39) 56(84) bytes of data.64 bytes from 10.10.10.39: icmp_seq=1 ttl=64 time=0.326 ms

8. (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file of the two nodes.

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 into both the nodes as user root through SSH mode.(2) Perform the following operations on both the nodes 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 both the nodes to modify the /etc/inet/ipnodesfile.# 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.


16.1.12 How Should I Change the IP Address of the 6140 Disk Array(Command Mode)

This section describes how to change the IP address of the 6140 disk array in command mode.To change the IP address of the 6140 disk array, the server must be installed with the 6140management host software. You need to configure each disk array.

PrerequisiteThe network connection between the server and the 6140 disk array is normal.

ContextTo change the IP address of the 6140 disk array, you need to perform this operation on the serveron which the 6140 management host software is installed. The 6140 management host softwareis generally installed on the M2000 server before delivery. When changing the IP address of the



16-17

6140 disk array, ensure that the server and the 6140 disk array are on the same network segment.Then, you need to change the IP address after logging in to the management host software asuser root.

NOTE

Enter the correct name of the 6140 disk array in name of the 6140 disk array in the following commands.

Procedure1. Perform the following steps on the server to set the temporary subnet:

(1) Log in to the server as user root in SSH mode.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.If the server requires to communicate with the 6140 disk array, you need to ensurethat the IP address of the Ethernet port is on the same network segment as the IPaddress of 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.39If the system output contains 192.168.8.39 is alive after you run theprevious command, it indicates that the IP address of the server is on the same networksegment as the IP address of controller A. Proceed with 3. Otherwise, you need toperform 1.3 through 1.5 to set the temporary subnet to ensure that the two IP addressesare on the same network segment.

(3) Determine the name of the Ethernet port used to set the temporary subnet.When setting the temporary subnet, choose bge0 as the communication Ethernet port.Run the following command to check the name of the Ethernet port corresponding tothe last IP address bound to this Ethernet 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:b0When two or multiple IP addresses are bound to the Ethernet port, the name of theEthernet port is displayed as bge0:X after you run the previous command. X is anumber starting from 1. The displayed Ethernet port name cannot be used for settingthe temporary subnet. When the X following bge0: is null, use bge0:1 as the name ofthe Ethernet port.In this example, the X following bge0: is null. Thus, you can use bge0:1 as the nameof the Ethernet port to set the temporary subnet.



Issue 03 (2010-08-31)

(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 an 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

# ifconfig bge0:1 192.168.8.100 netmask 255.255.255.0 up

(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) Select the PC serial port that is connected to the connector, for example, COM1.

(6) Set the properties of the serial port. For details about how to set properties of a serialport, see Table 16-5. Then, click OK.

Table 16-5 Setting the properties of the serial port

Attribute Attribute Value

Bit rate 38400



16-19

Attribute Attribute Value

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 to the request to synchronize the baud rate with

the terminal.Set baud rate: press <space> within 5 seconds

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.

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

(13) If the following message is displayed, enter 1.Select Ethernet Port==============================1 Ethernet Port: 02 Ethernet Port: 1Q QuitEnter Selection: 1The configuration of the IP address for the selected Ethernet port is displayed.

(14) If the following message 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:

(15) Perform 1.4 and 1.5 by using the IP address of controller A to reset a temporary subnet.



Issue 03 (2010-08-31)

3. Run the following command on the server to log in to the management host software asuser 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.

(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) Change 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 changing 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 changed IPaddress of controller A. Otherwise, the server cannot have an 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 changed IP address 10.70.12.12 of the 6140 disk arrayis 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.



16-21

# /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) Change 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 changing the IP addresses of other 6140 disk arrays.

# /opt/SUNWsesscs/cli/bin/sscs modify -a Name of the 6140 disk array(ST6140-1) -g IP address of the gateway -i IP address of controller B on the 6140disk array -m subnet mask controller B

5. (Optional) Modify the /etc/hosts file and the /etc/inet/ipnodes file of the two nodes.

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 both nodes as user root.

(2) Perform the following operations on both nodes 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 both the nodes to modify the /etc/inet/ipnodesfile:


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.

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.

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



Issue 03 (2010-08-31)

Prerequisitesl Log in to the server as user root through SSH mode.

l The communication between the server and the two management Ethernet ports on theS2600 disk array is normal.

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

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



16-23

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

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

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



Issue 03 (2010-08-31)

SolutionTo rectify the fault, perform the following steps:

1. Log in to the M2000 server as user root through SSH mode.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

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.

16.1.15 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 M2000 server as user root through SSH mode.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?



16-25

(3) After running the following command, repeat 4.1 and 4.2 to label the other logicalpartitions.format> disk

5. Exit format.format> q

16.1.16 What Should I Do When the Server Disk Space IsInsufficient

This section describes what to do when the server disk space is insufficient.

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, see11.2.3 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 M2000 server as user root through SSH mode.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.



Issue 03 (2010-08-31)

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.

ftp> bye

4. Send the collection results to Huawei technical support engineers.

16.1.17 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



16-27

NOTE

In the HA system, you need to set two Trap IP addresses for each disk array. The two Trap IP addressescorrespond to the IP addresses of the two servers.

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.10Run the following command to check whether the Trap IP address is successfully changed:OceanStor:admin> showtrapipIndex 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 through SSH mode.

NOTEIn the HA system, you need to log in to both the active server and standby server of the M2000 asuser root to modify the configuration file.

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 :qcommand to quit.

l Otherwise, change the status of san to true. Then, press Esc and run the :wq commandto save the modification and quit.



Issue 03 (2010-08-31)

10. Run the following commands to restart the ResourceMonitor process:

NOTEIn the HA system, you need to restart the ResourceMonitor process on both the active server andstandby server.

# ps -ef | grep "ResourceMonitor"root 10256 884 0 10:57:58 ? 0:55 /opt/OMC/bin/ResourceMonitor -cmd start -ipaddr 10.71.15.31 >/dev/null 2>&1 root 20762 26443 0 16:54:48 pts/4 0:00 grep ResourceMonitor# kill -9 10256

NOTE

In the previous command, replace the ResourceMonitor process ID 10256 with the actual value.

11. Run the following commands to restart the UdpDispatchService service:

NOTE

You need to restart the UdpDispatchService service on only active server.

# . /opt/OMC/svc_profile.sh# svc_adm -cmd restartsvc UdpDispatchService

16.1.18 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. For an HA system, you need toinstall the OceanStor on the standby node.

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



16-29

ftp server IP addressftp> lcd path of the file on the PC

ftp> cd /opt

ftp> bin

ftp> put /opt/SMIA-SOL-09.19.04.07.bin

ftp> bye

(4) Create a directory for saving the OceanStor installation package.

# cd /opt

# mkdir SMIADIR

(5) Move the OceanStor installation package to the /opt/SMIADIR directory.

# mv /opt/SMIA-SOL-09.19.04.07.bin /opt/SMIADIR/SMIA-SOL-09.19.04.07.bin.zip

(6) Decompress the OceanStor installation package.

# cd /opt/SMIADIR

# 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 16-1.



Issue 03 (2010-08-31)

Figure 16-1 SNMP tab page

(9) Type the IP address of the M2000 server in Trap destination. For an HA system,

type the logical IP address of the M2000 server.(10) Click Add.(11) Wait until the typed IP address is added to the Configured SNMP addresses area in

Figure 16-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.For an HA system, perform the operation on the active and standby nodes.

(1) Log in to the M2000 server as user root.(2) Run the following command to run the environment variables of the M2000:


(3) Run the following commands to run the monitoring script:



16-31

# cd /opt/OMC/bin

# ./deployHDMonitor.sh

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

When 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 16-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.



Issue 03 (2010-08-31)

16.1.19 How Should I Uninstall the OceanStor Monitoring SoftwareThis section describes how to uninstall the OceanStor monitoring software.

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 SMutilWhen the system displays the following prompt, type y.Do you want to remove this package? [y,n,?,q] y# pkgrm SMclientWhen 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 SMruntimeWhen the system displays the following prompt, type y.Do you want to remove this package? [y,n,?,q] y

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

PrerequisitesLog in to the M2000 server as user root through SSH mode.

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 grepIf 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 16.1.21How Should I Start the FTP Service on the M2000 Server.



16-33

root 26510 22906 0 19:53:39 pts/1 0:00 /usr/sbin/ftpdIn the system output, the value in the second line refers to the process ID of the FTP serviceon the M2000 server.

16.1.21 How Should I Start the FTP Service on the M2000 ServerThis section describes how to start the FTP service on the M2000 server.


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 grepThe system displays the following information: root 26510 22906 0 19:53:39 pts/1 0:00 /usr/sbin/ftpdIn 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.

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


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.



Issue 03 (2010-08-31)

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 check the running status of the SFTP service:

# svcs -a | grep ssh

The system displays the following information:online 18:46:13 svc:/network/ssh:default

If online is displayed in the system output, it indicates that the SFTP service on 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 16.1.23 How Should I Start the SFTP Service on the M2000 Server.

16.1.23 How Should I Start the SFTP Service on the M2000 ServerThis section describes how to start the SFTP service on the M2000 server.


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

2. Run the following command to check the running status of the SFTP service:# svcs -a | grep ssh

online is displayed in the system output. That is, the SFTP service on the M2000 server isstarted.

16.1.24 How Do I Log In to the Server in SSH ModeThis section describes how to log in to the server in SSH mode.

QuestionHow should you log in to the server in SSH mode?

Prerequisitesl The Solaris operating system is already installed.



16-35

l You have downloaded the PuTTY tool from http://support.huawei.com to the local PC.

Answer1. Double-click PuTTY.exe. A dialog box is displayed, as shown in Figure 16-2.

Figure 16-2 PuTTY Configuration

2. In the Host Name (or IP address) field, enter the IP address of the server to be logged in

to.3. Select Protocol:SSH.4. Select Close window on exit:Only on clean exit.5. Click Open.

When you open the window for the first time, the following interface is displayed, clickYes.



Issue 03 (2010-08-31)

Figure 16-3 PuTTY Security Alert

6. When the system displays login as:, type a user name and then press Enter.

7. When the system displays [email protected]'s password:, type the password andthen press Enter.When the system displays Last login: Wed Oct 31 11:59:36 2007 from10.10.10.12, then the login is successful.

16.2 About Sybase (HA, Sun)This section describes some FAQs and their answers regarding the Sybase.

16.2.1 How Do I Check Whether the Sybase Is StartedThis section describes how to check whether the Sybase is started.

16.2.2 How to Start the Sybase (HA, Sun)This section describes how to start the Sybase for an HA system.

16.2.3 How to Stop the Sybase (HA, Sun)This section describes how to stop the Sybase.

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

16.2.5 How to Handle Database AlarmsThis section describes why database alarms are generated and how to handle these databasealarms.

16.2.6 How to View Database Deadlock InformationThis section describes how to check the deadlock information about the Sybase database.

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

16.2.8 Why Is the Sybase Not Started After Run svc_profile.shThis section describes why the Sybase is not started after the execution of the scriptsvc_profile.sh.

16.2.9 Why the Sybase Backup Database AbortThis section describes how to solve the Sybase backup abort.

16.2.10 What Should I Do When the Database Cannot Be Started ProperlyThis section describes what to do when the database cannot be started properly.



16-37

16.2.11 What Should I Do When the Client Is Disconnected Due to Damaged System Tables inthe Database (HA)This section describes what to do when the client is disconnected due to damaged system tablesin the database.

16.2.12 What Should I Do When the Number of Database Connections Is InsufficientThis section describes what to do when the number of database connections is insufficient.

16.2.13 How to Handle the '/export/home/sybdev/master.dat' already in use MessageThis section describes how to handle the '/export/home/sybdev/master.dat' already in usemessage.

16.2.1 How Do I Check Whether the Sybase Is StartedThis section describes how to check whether the Sybase is started.

Question

How do I check the startup status of the Sybase?

Answer

Perform the following steps to check the status of Sybase:

1. Switch to user dbuser on the active node.

l Log in to the server as dbuser through SSH mode 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

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

16.2.2 How to Start the Sybase (HA, Sun)This section describes how to start the Sybase for an HA system.

Question

How to start the Sybase?



Issue 03 (2010-08-31)

Answer

To start the Sybase, perform the following steps:

1. logged in to the M2000 as user root through SSH mode.2. Check whether the Sybase service is running.

Check the Sybase service, see 16.2.1 How Do I Check Whether the Sybase Is Started.-bash-3.00$ exit

3. Run the following command:# scswitch -e -j sybase_rs

16.2.3 How to Stop the Sybase (HA, Sun)This section describes how to stop the Sybase.

Question

How should I do to stop the Sybase?

Prerequisites

Please ensure the M2000 services is stopped.

Answer

To stop the Sybase, perform the following steps:

1. logged in to the M2000 as user root through SSH mode.2. Run the following command stop the Sybase.


16.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 through SSH mode.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

16.2.5 How to Handle Database AlarmsThis section describes why database alarms are generated and how to handle these databasealarms.



16-39

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 analysisThe 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.SolutionCheck 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 10.3 Clearing M2000Databases.

l Alarms are generated in the pmdb alarm database.Cause analysisThe 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 10.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.

– 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 10.3 Clearing M2000Databases.

16.2.6 How to View Database Deadlock InformationThis section describes how to check the deadlock information about the Sybase database.



Issue 03 (2010-08-31)

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 through SSH mode.2. Run the following commands:

-bash-3.00$ isql -Sdatabase server name -Usa -Ppassword of user sa1> sp_lock2> go

NOTE

After the Sybase server is started, run the following command to view the name of the databaseserver:-bash-3.00$ ps -ef | grep RUN_ | grep -v grep



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.

NOTE

The command output displays the traced information on the monitor.

1> use master

2> go

1> select object_name(464004684)

2> go



16-41

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

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

Question

Why does the Sybase not start after the M2000 server restarts?

This takes SYB, which is the name of the database server, as an example. Open the 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





Causes

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

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.



Issue 03 (2010-08-31)

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 active and standby nodes as user root through SSH mode.# 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 16.2.2 How to Start the Sybase (HA, Sun).

16.2.8 Why Is the Sybase 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 theSybase 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.

SolutionBefore you start the Sybase service, run SYBASE.sh in Sybase installation path. The Sybasedefault installation path is /opt/sybase/.



16-43

16.2.9 Why the Sybase Backup Database AbortThis section describes how to solve the Sybase backup abort.

QuestionWhy does the Sybase backup database stop abnormally?

AnswerRun the nohup command before you start the Sybase.

1. Log in to the Solaris as user dbuser through SSH mode.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

After the Sybase server is started, run the following command to view the name of the databaseserver:




16.2.10 What Should I Do When the Database Cannot Be StartedProperly

This section describes what to do when the database cannot be started properly.

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



Issue 03 (2010-08-31)

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

Solutioncontact Huawei technical support engineers for assistance.

16.2.11 What Should I Do When the Client Is Disconnected Due toDamaged System Tables in the Database (HA)

This section describes what to do when the client is disconnected due to damaged system tablesin the database.

QuestionThe client is disconnected from the server. When viewing the /opt/sybase/ASE-15_0/install/database server name.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



16-45

NOTE

After starting the Sybase database, run the following command to view the name of the database server.


In the system output, the value next to RUN_ refers to the name of the database server.

According to the following system output, 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

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 active node as user root through SSH mode.2. If the M2000 services are running, stop them.

For details about how to stop the M2000 services, see 9.2.4 Stopping M2000 Services(HA).

3. If the Sybase service is running, stop it.For details about how to stop the Sybase service, see 16.2.3 How to Stop the Sybase (HA,Sun).

4. Run the following command to start the data service process of the database:# su - dbuser-bash-3.00$ cd /opt/sybase/ASE-15_0/install

-bash-3.00$ ./startserver -f ./RUN_SYB -m

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/11/05 22:17:30.83 server Recovery complete.00:00000:00001:2008/11/05 22:17:30.83 server ASE's default unicode sort order is 'binary'.00:00000:00001:2008/11/05 22:17:30.83 server ASE's default sort order is:00:00000:00001:2008/11/05 22:17:30.83 server 'bin_cp936' (ID = 50)00:00000:00001:2008/11/05 22:17:30.83 server on top of default character set:00:00000:00001:2008/11/05 22:17:30.83 server 'cp936' (ID = 171).00:00000:00001:2008/11/05 22:17:30.83 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:



Issue 03 (2010-08-31)


1> shutdown

2> go

-bash-3.00$ exit

7. Start the Sybase database.

For details, see 16.2.2 How to Start the Sybase (HA, Sun).8. Start the M2000 services.

For details about how to start the M2000 services, see 9.2.3 Starting the M2000 Services(HA).

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

Question

The 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

user connections.

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.





Solution

The 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. You have logged in to the active node as user root.2. If the M2000 services are running, stop them.



16-47

For details about how to stop the M2000 services, see 9.2.4 Stopping M2000 Services(HA).

3. Switch to user dbuser.# su - dbuser

4. Run the following commands on the active node to change the maximum number ofconnections 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. Perform 5 to synchronize the modificationto the standby node. 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 6.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 synchronize the modification to the standby node.# rcp /opt/sybase/ASE-15_0/SYB.cfg standby node name:/opt/sybase/ASE-15_0/SYB.cfg

6. Run the following command to check the database memory:1> sp_configure "max memory"2> goThen, contact Huawei technical support engineers for assistance.

16.2.13 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



Issue 03 (2010-08-31)

master device00:00000:00000:2009/10/24 23:43:08.24 server kiconfig: read of config block failed

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.





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 16.2.1 HowDo I Check Whether the Sybase Is Started.

16.3 About Server Software (HA, Sun)This section describes some FAQs and their answers regarding the M2000 server software.

16.3.1 Why M2000 Services Restart Abnormally (HA, Sun)This section describes the solution to abnormal restart of the M2000 service in the M2000 HAsystem.

16.3.2 Why M2000 Services Stop Abnormally (HA, Sun)This section describes the solution to abnormal termination of the M2000 services in theM2000 HA system.

16.3.3 Why M2000 Services Fail to Start After the Server Restarts (HA, Sun)This section describes the solution to the failure to start the M2000 after the server is restarted.

16.3.4 How Do I Copy the Backup Dynamic Data from a Hard Disk to a Tape (HA, Sun)For an HA system, if you want to copy the dynamic data to a tape, it is recommended that youmanually copy the backup data from the hard disk to a tape after the dynamic data is backed upon a hard disk.

16.3.5 How Do I Copy the Backup Dynamic Data from a Tape to a Hard Disk (HA, Sun)In an HA system, if the backup dynamic data is copied to a tape, you need to copy the data fromthe tape to the hard disk before restoring the data.

16.3.6 How Do I Verify the Dynamic Data Backed Up on a TapeThis section describes how to check the validity of the dynamic data backed up on a tape in orderto determine whether the data can be read properly.

16.3.7 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 console



16-49

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

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

16.3.9 How to Set the M2000 Server as the NTP Client (HA, in Encryption Mode)This section describes how to set the M2000 server as the NTP client and synchronize time withthe upper-layer time server in encryption mode in an M2000 HA system.

16.3.10 How to Check the Running Status of the NTP Service on the M2000 Server (HA, inEncryption Mode)This section describes how to check the running status of the NTP service after the M2000 serveris set as the NTP client in encryption mode so that the proper running of the NTP services canbe ensured.

16.3.11 How Should I Handle an Incremental Backup FailureThis section describes the causes of the failure to back up the M2000 dynamic data incrementally.This section also describes how to solve this problem.

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

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

16.3.1 Why M2000 Services Restart Abnormally (HA, Sun)This section describes the solution to abnormal restart of the M2000 service in the M2000 HAsystem.

QuestionWhy does the M2000 service restart abnormally?

AnswerThe possible causes are as follows:

l Sybase fault

l M2000 system fault

To solve this problem, perform the following steps:

1. Log in to the server as user root through SSH mode.2. Run the following command to stop the M2000 service:


3. Run the following command to stop the Sybase:.# scswitch -n -j sybase_rs



Issue 03 (2010-08-31)

4. Set Sybase parameters.

To set the parameter total memory of the database and how to modify the fileRUN_SYB, refer to the software installation manual related to each server type.

5. Restart the Sybase.


6. Start the M2000 service.


7. Check system logs.

Check system logs. For details, see 8.2 Querying the System Logs of the M2000.

16.3.2 Why M2000 Services Stop Abnormally (HA, Sun)This section describes the solution to abnormal termination of the M2000 services in theM2000 HA system.

Question1. Switch to the M2000 installation path. The default M2000 installation path is /opt/OMC.

# cd /opt/OMC

2. Run the following commands:



If the value after not running in the output is greater than 0, the M2000 services stopabnormally.

Answer

The possible causes are as follows:

l An error occurs during the program running.

l Startup is stopped manually.

To solve this problem, perform the following steps:

1. Log in to the server as user root through SSH server.

2. Stop the services and then start the services.



Do not manually stop the startup process.

3. If the problem persists, contact Huawei technical support engineers for assistance.

16.3.3 Why M2000 Services Fail to Start After the Server Restarts(HA, Sun)

This section describes the solution to the failure to start the M2000 after the server is restarted.



16-51

QuestionShut down the HA system by running the command /usr/cluster/bin/scshutdown. After theactive and standby nodes restart, the M2000 services are not started automatically.

AnswerIf the resources are shut down before the server restarts, you must start the resources manually.

To solve this problem, you can perform either of the following steps:

l Set the enabled attribute of the M2000 resources to True before you shut down the servers.

l Run the command scswitch -e -j ossapp_rs to manually restart the M2000 resources afterthe servers restart.

16.3.4 How Do I Copy the Backup Dynamic Data from a Hard Diskto a Tape (HA, Sun)

For an HA system, if you want to copy the dynamic data to a tape, it is recommended that youmanually copy the backup data from the hard disk to a tape after the dynamic data is backed upon a hard disk.

Prerequisitesl The dynamic data is backed up to a hard disk.

l Tapes for saving the dynamic data is available.

l Before using tapes to back up data, ensure that the tapes are writable.

CAUTIONYou need not perform the following steps on the standby node.

Procedure1. Insert a tape into the tape drive.2. Log in to the node where you need to perform the steps as user root through SSH mode.3. Check the status of the tapes. For details, see 16.1.4 How Should I Select a Tape Drive

and 16.1.3 How to Check the Status of the Tape Drive.4. Set the M2000 environment variables.

# . /opt/OMC/svc_profile.sh5. Rewind the tapes.

# mt -f /dev/rmt/0n rewind6. Backup the /export/home/backup/omc directory to a tape.

# gtar cPfM /dev/rmt/0n /export/home/backup/omc

(1) If one tape cannot save all the data, the following message is displayed. In such a case,you need to remove the tape from the tape drive. For details, see the manual deliveredwith the tape drive.



Issue 03 (2010-08-31)

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

# mt -f /dev/rmt/0 offline

(2) After inserting a new tape, press Enter to continue the backup.

7. When the backup is complete, you need to remove the tape from the tape drive. For details,see the manual delivered with the tape drive.

After the tape is ejected, remove it from the tape drive.

8. (Optional) Check the validity of the dynamic data that is backed up on the tapes. For details,see 16.3.6 How Do I Verify the Dynamic Data Backed Up on a Tape.

9. After the check, enable write protection on the tapes, label them, and store them properly.For the naming conventions of backup tapes, see 12.1.2 Policies of M2000 DataBackup.

For details about how to enable the write protection on tapes, see the hardware descriptionof the tapes.

16.3.5 How Do I Copy the Backup Dynamic Data from a Tape to aHard Disk (HA, Sun)

In an HA system, if the backup dynamic data is copied to a tape, you need to copy the data fromthe tape to the hard disk before restoring the data.

Prerequisites

Log in to the M2000 server as user root through SSH mode.

CAUTIONYou need not perform the following steps on the standby node.

Procedure1. Insert the tape that stores dynamic data into the tape drive. If the backup dynamic data is

saved on multiple tapes, insert the first tape into the tape drive.

2. Rewind the tape.

# mt -f /dev/rmt/0n rewind

3. Restore the data from the tape to the hard disk.

# /usr/sfw/bin/gtar xvPfM /dev/rmt/0n

(1) Press the button on the tape drive to remove the tape when the following informationis displayed. For details, see the manual delivered with the tape drive.Prepare volume #2 for '/dev/rmt/0' and hit return:



16-53

NOTE

You can also remove the tape by opening a new remote login window and then running thefollowing command:# mt -f /dev/rmt/0 offline

(2) After inserting a new tape into the tape drive, press Enter to continue the restore.4. When the restore is complete, remove the tape from the tape drive. For details, see the

manual delivered with the tape drive.5. Change the right and owner of the /export/home/backup directory.

# chmod -R 770 /export/home/backup# chown -R omcuser:omcsysm /export/home/backup

16.3.6 How Do I Verify the Dynamic Data Backed Up on a TapeThis section describes how to check the validity of the dynamic data backed up on a tape in orderto determine whether the data can be read properly.

Prerequisitesl The tape drive is operational. If an external tape drive is connected, ensure that the tape

drive is properly connected to the server.l You have logged in to the server as user root through SSH mode.

Background

CAUTIONl When you use the BRT tool to check the validity of data backup, you can check whether the

data in the tapes can be read, but cannot check whether the backup data can be used forrestore. If the original data for backup is faulty, the data may fail to be used for restore evenif it is verified to be valid.

l The type of the server used for data verification can be different from that used for databackup. The tape drives configured on different servers, however, may be different. Thus, itis recommended that you verify the data on the same server where the data is backed up.

Procedure1. Insert the tape storing the dynamic data into the tape drive. If backup data is stored on

multiple tapes, insert the first one.2. Set the environment variables of the M2000.

# . /opt/OMC/svc_profile.sh3. Rewind the tape.

# mt -f /dev/rmt/0n rewind4. Verify the backup data stored on the tape.

# gtar tPfM /dev/rmt/0n

(1) Press the button on the tape drive to remove the tape when similar information isdisplayed. For details, see the manual delivered with the tape drive.



Issue 03 (2010-08-31)

Prepare volume #2for '/dev/rmt/0' and hit return:NOTE

You can also remove the tape by opening a new remote login window and running the followingcommand:

# mt -f /dev/rmt/0 offline

(2) Insert another tape and press Enter to continue the verification.

If the displayed system output contains no error information after the command is executed,it indicates that the dynamic data on the tape is valid.

5. After the verification is complete, press the button on the tape drive to remove the tape.For details, see the manual delivered with the tape drive.

16.3.7 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 through SSH mode.

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:

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



16-55

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.



Issue 03 (2010-08-31)

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 4.5.3 Starting the NTPService on the M2000 Administration Console.

16.3.8 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 through SSH mode.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



16-57

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.

16.3.9 How to Set the M2000 Server as the NTP Client (HA, inEncryption Mode)

This section describes how to set the M2000 server as the NTP client and synchronize time withthe upper-layer time server in encryption mode in an M2000 HA system.



Issue 03 (2010-08-31)

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 active and standby nodes are correct.

l Log in to the active and standby nodes as user root through SSH mode.

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 the M2000 services are running, run the following command on the active node to stop

them:# scswitch -n -j ossapp_rs

2. Run the following command on the active and standby nodes to check whether there is anysystem output: If there is no system output, you can infer that the M2000 daemon processis stopped.# . /opt/OMC/svc_profile.sh

# daem_ps

3. If the daemon process is still running, run the following command to stop it:# kill_daem

4. If the Sybase services are running, run the following command on the active node to stopthem:# scswitch -n -j sybase_rs

5. Run the following commands on the active and standby nodes to edit the /etc/inet/ntp.keys file:# TERM=vt100; export TERM

# vi /etc/inet/ntp.keys

Add the identifier, key type, and authentication code of the upper-layer NTP server to 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.

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



16-59

7. Run the following commands on the active and standby nodes to edit thentp.conf.cluster file:


# vi /etc/inet/ntp.conf.cluster

The correct ntp.conf.cluster configuration file contains the following contents:peer clusternode1-priv preferpeer clusternode2-priv

If you use the NTP server specified by the operator, you need to add server IP address ofthe upper-layer NTP server key identifier next to server 127.127.1.0 in thentp.conf.cluster configuration file. Add multiple lines if multiple NTP servers exist.

8. Add the following contents to the ntp.conf.cluster configuration files of the active andstandby nodes: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

9. Save the ntp.conf.cluster 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. If the Sybase services are stopped in 4, run the following command on any node to startthem:


11. If the M2000 services are stopped in 1, run the following command on any node to startthem:


12. Run the following command on a standby node to check whether there is any system output:


# daem_ps

l If there is any system output, you can infer that the daem process is started.

l If there is no system output, you can infer that the daem process is not started. Run thefollowing commands to start it:

# start_daem -type standby

13. Run the following command on the active and standby nodes to check the system date andtime:

# date

If the system date and time of the two nodes are different, contact Huawei technical supportengineers for assistance.

Postprocessing

After setting the M2000 server as the NTP client, you need to start the NTP services on theserver. For details, see 4.5.6 Starting the NTP Service on the M2000 Server (HA).



Issue 03 (2010-08-31)

16.3.10 How to Check the Running Status of the NTP Service on theM2000 Server (HA, in Encryption Mode)

This section describes how to check the running status of the NTP service after the M2000 serveris set as the NTP client in encryption mode so that the proper running of the NTP services canbe ensured.

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 ntpq -p and ntptrace commands to querythe 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.

Procedure1. Log in to both the nodes as user root through SSH mode.2. Run the following command to query the information about clock source:

# ntpq -pIn the result of the ntpq -p command, the remote field shows the address and status ofthe reference clock source.

3. Run the following command on node 1 to check the NTP synchronization path:# ntptraceThe ntptrace command traces the NTP synchronization path from the host to the top NTPserver. For more information, run the ntptrace -v command.

4. Run the following command on node 1 to check the authentication status of the NTP service:# ntpqntpq> asIn the result, the value ok of auth indicates the NTP service is successfully authenticated.ntpq> exit

5. Repeat 2 to 4 on node 2 to check the running status of the NTP service on node 2.

16.3.11 How Should I Handle an Incremental Backup FailureThis 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.



16-61

l The disk space is insufficient.

Solutionl The database logs are not consecutive.

1. Check the backup and restore log.-bash-3.00$ more /opt/OMC/var/logs/backup.log

If 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 12.2.3 Manually Backing Up the M2000 Dynamic Data (HA).

l The disk space is insufficient.

1. Check the backup and restore log.-bash-3.00$ more /opt/OMC/var/logs/backup.log

If 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 16.1.16 What Should I Do When the Server Disk Space IsInsufficient.

3. Perform a full backup again.For details, see 12.2.3 Manually Backing Up the M2000 Dynamic Data (HA).

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

Prerequisite

Log in to the M2000 server as user omcuser through SSH mode. In the HA system, log in tothe active node.

Context

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



Issue 03 (2010-08-31)

l The CPU and the memory performance report file records performance reports in thefollowing format:Hostname, Time, CPU Occupancy(%), MEM Occupancy(%), Physical Memory(MB), Remaining Physical Memory(MB), Swap Memory(MB), Remaining Swap Memory(MB)

l The disk usage report file records disk usage reports in the following format:Hostname, Time, Partition Name, Total Size(MB), Used Size(MB), Remaining Size(MB), 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.


Step 2 Run the environment variant commands.


Step 3 Enable the function of exporting reports.l Enable the function of exporting a performance report.

-bash-3.00$ svc_monitor -cmd start -type systeml Enable the function of exporting a disk usage report.

-bash-3.00$ 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.-bash-3.00$ cd M2000 server installation path/var/monitor/sysinfo-bash-3.00$ more Performance report file name

l Check the report about disk usage.-bash-3.00$ cd M2000 server installation path/var/monitor/diskinfo-bash-3.00$ more Disk usage report file name

----End

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



16-63

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.

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.



Issue 03 (2010-08-31)

M2000 HA System Administrator Guide (Sun, S10)

Documents

huawei trademarks

huawei proprietary

m2000 ha system

documentpurposethis

huawei industrial basebantian

m2000 hathis chapter

formal release

system management tasks