iManager U2000 Local HA System (Veritas) Software Installation and Commissioning Guide (SUSE Linux, PC Server)-(V200R014C50_01)

iManager U2000 Unified Network Management
System
V200R014C50
Local High Availability System

(Veritas) Software Installation and
Commissioning Guide (SUSE Linux,
PC Server)
Issue 01
Date 2014-05-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2014-05-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
Local High Availability System (Veritas) Software
Installation and Commissioning Guide (SUSE Linux, PC
Server) About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V200R014C50
Intended Audience
This document describes how to install the U2000 HA system on the SUSE Linux OS and obtain
the reference information required during the installation.
This document is intended for:
l Technical support engineers

l Maintenance engineers
l Installation and commissioning engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation

which, if not avoided, will result in death or
serious injury.
Indicates a potentially hazardous situation

which, if not avoided, could result in death or
serious injury.

which, if not avoided, may result in minor or
moderate injury.
Issue 01 (2014-05-20) Huawei Proprietary and Confidential ii

Symbol Description

which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Calls attention to important information, best

practices and tips.
NOTE is used to address information not
related to personal injury, equipment damage,
and environment deterioration.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
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 by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical 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.
Issue 01 (2014-05-20) Huawei Proprietary and Confidential iii

Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01 (2014-05-20) Based on Product Version V200R014C50

Initial release.
Issue 01 (2014-05-20) Huawei Proprietary and Confidential iv

Server) Contents
Contents
About This Document.....................................................................................................................ii

1 Installation Overview...................................................................................................................1
1.1 Networking Structure.....................................................................................................................................................2
1.2 Configuration Requirements...........................................................................................................................................4
1.3 Restrictions on Installation and Commissioning............................................................................................................7
2 Installation Procedure...................................................................................................................8
3 Installing the U2000....................................................................................................................12
3.1 Installation Preparations...............................................................................................................................................14
3.1.1 Collecting Installation Information...........................................................................................................................14
3.1.2 Checking Required Software.....................................................................................................................................24
3.1.3 Checking Hardware Connections..............................................................................................................................30
3.1.4 Applying for a U2000 License..................................................................................................................................39
3.1.5 Applying for a Veritas License..................................................................................................................................41
3.2 Powering On a Server...................................................................................................................................................42
3.3 Configuring Controller IP Addresses...........................................................................................................................44
3.3.1 Configuring the iMana IP Address of Huawei server...............................................................................................44
3.3.1.1 Configuring the iMana IP Address Through iMana Management Interface..........................................................45
3.3.1.2 Configuring the iMana IP Address Through BIOS................................................................................................48
3.3.2 Configuring the IMM IP Address..............................................................................................................................51
3.3.2.1 Configuring the IMM IP Address Through IMM Management Interface(IBM X3650 M4).................................52
3.3.2.2 Configuring the IMM IP Address Through IMM Management Interface (IBM X3850 X5 and IBM X3650 M3)
............................................................................................................................................................................................55
3.3.2.3 Configuring the IMM IP Address Through BIOS..................................................................................................58
3.3.3 Setting the SC IP Address for the OceanStor S3900 Disk Array..............................................................................63
3.4 Configuring RAID........................................................................................................................................................66
3.4.1 Configuring the RAID in Remote Mode (Huawei RH series rack server, ISO).......................................................67
3.4.2 Configuring RAID in Remote Mode (IBM X3650 M4, ISO)...................................................................................71
3.4.3 Configuring RAID in Remote Mode (IBM X3850 X5 and IBM X3650 M3, ISO)..................................................78
3.5 Installing the SUSE Linux OS by Using the Quick Installation CD-ROM..................................................................85
3.5.1 Remotely Installing the SUSE Linux Operating System (Huawei RH series rack server, DVD/ISO).....................86
3.5.2 Remotely Installing the SUSE Linux Operating System (IBM X3650 M4, DVD/ISO)...........................................91
Issue 01 (2014-05-20) Huawei Proprietary and Confidential v

Server) Contents
3.5.3 Remotely Installing the SUSE Linux Operating System (IBM X3850 X5 and IBM X3650 M3, DVD/ISO)........100
3.5.4 Locally Installing the SUSE Linux Operating System (IBM Server, DVD)...........................................................109
3.5.5 Locally Installing the SUSE Linux Operating System (Huawei RH series rack server, DVD)..............................115
3.6 Installing the U2000 Software....................................................................................................................................119
3.6.1 Preparing Software Packages..................................................................................................................................119
3.6.2 Preconfiguring the OS ............................................................................................................................................122
3.6.3 Starting the U2000 Installation Program.................................................................................................................137
3.6.3.1 Installing the U2000 on the GUI..........................................................................................................................137
3.6.3.2 Installing the U2000 Through the CLI.................................................................................................................143
3.7 Configuring a Route...................................................................................................................................................149
3.8 Connecting the Primary and Secondary Sites.............................................................................................................152
3.9 Loading or Updating a License File...........................................................................................................................156
3.9.1 Loading a U2000 License........................................................................................................................................156
3.9.2 Updating a Veritas License......................................................................................................................................161
3.10 Checking System Installation...................................................................................................................................163
4 Separating the Primary Site from the Secondary Site........................................................168

5 Commissioning the U2000.......................................................................................................172
5.1 Commissioning Preparation.......................................................................................................................................173
5.1.1 Obtaining Commissioning Parameters....................................................................................................................173
5.1.2 Checking Hardware Connections............................................................................................................................179
5.2 Performing Commissioning........................................................................................................................................188
5.2.1 Powering On a Server..............................................................................................................................................189
5.2.2 Configuring System Commissioning Parameters....................................................................................................191
5.2.3 Connecting the Primary and Secondary Sites..........................................................................................................195
5.2.4 Commissioning U2000 Parameters.........................................................................................................................199
A FAQs............................................................................................................................................202
A.1 SUSE Linux OS.........................................................................................................................................................203
A.1.1 How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS..............................................................203
A.1.2 How to Enable and Disable the FTP Authority of the root User in the SUSE Linux OS......................................204
A.1.3 How to manually Add the Default Route (SUSE Linux).......................................................................................205
A.1.4 How to manually Add a Static Route (SUSE Linux).............................................................................................205
A.1.5 How to Add a Static Route If the U2000 Is Installed.............................................................................................206
A.1.6 How to Check Disk Partitions................................................................................................................................207
A.1.7 How to Monitor System Processes and Application Ports.....................................................................................208
A.1.8 How to Enable Remote GUI Logins.......................................................................................................................208
A.1.9 How to Query the Process Status............................................................................................................................209
A.1.10 How to Use the vi Editor......................................................................................................................................209
A.1.11 How to Change the Time and Time Zone of the SUSE Linux OS.......................................................................211
A.1.12 How to Use the VNC to Remotely Log In to SUSE Linux by Retaining the Session.........................................213
A.1.13 How to Set IP Addresses for Unused NICs on SUSE Linux................................................................................220
Issue 01 (2014-05-20) Huawei Proprietary and Confidential vi

Server) Contents
A.1.14 How to Capture Snapshots on SUSE Linux.........................................................................................................222

A.1.15 How to Configure the Resolution on SUSE Linux...............................................................................................223
A.1.16 How to Install the 7-zip Software on the SUSE Linux OS...................................................................................225
A.2 System Settings of the Huawei RH series rack server...............................................................................................226
A.2.1 How Do I Use iMana IP to Log In to a Remote Huawei RH series rack server....................................................227
A.2.2 How to View the IP Address of the iMana on the Huawei RH series rack server.................................................228
A.2.3 How to Change the Password of iMana User Root................................................................................................230
A.2.4 How to Solve iMana Problems...............................................................................................................................231
A.2.5 Mappings Between Physical and Logical Network Interfaces on an Huawei RH Series Rack Server Running SUSE
Linux.................................................................................................................................................................................234
A.2.6 Formatting disks (Huawei RH series rack server)..................................................................................................235
A.2.7 Viewing Hard Disk Information (Huawei RH series rack server)..........................................................................240
A.3 System Settings of the IBM Server...........................................................................................................................243
A.3.1 How to Solve the Problem Where the Remote Control Desktop Appears and Then Disappears Immediately
..........................................................................................................................................................................................243
A.3.2 How do I use an IMM IP address to remotely log in to an IBM server (IBM X3650 M4)....................................244
A.3.3 How to Use an IMM IP Address to Remotely Log In to an IBM Server(IBM X3850 X5 and IBM X3650 M3)
..........................................................................................................................................................................................247
A.3.4 How to View the IMM IP Address on the IBM Server..........................................................................................248
A.3.5 How to Change the Password of the IMM User USERID(IBM X3650 M4).........................................................252
A.3.6 How to Change the Password of the IMM User USERID(IBM X3850 X5 and IBM X3650 M3)........................255
A.3.7 How to Solve IMM Problems.................................................................................................................................256
A.3.8 Mappings Between Physical and Logical Network Interfaces on an IBM Server Running SUSE Linux.............258
A.3.9 Viewing Hard Disk Information in Local Mode (IBM Server)..............................................................................259
A.3.10 Viewing Hard Disk Informationin Remote Mode (IBM X3650 M4)..................................................................261
A.3.11 Viewing Hard Disk Informationin Remote Mode (IBM X3850 X5 and IBM X3650 M3).................................265
A.3.12 Formatting disks in Local Mode (IBM Server)....................................................................................................269
A.3.13 Formatting the disks in Remote Mode (IBM X3650 M4)....................................................................................274
A.3.14 Formatting the disks in Remote Mode (IBM X3850 X5 and IBM X3650 M3)...................................................281
A.3.15 How to Configure the HTTPS on the IMM(IBM X3650 M4).............................................................................288
A.3.16 How to Configure the HTTPS on the IMM(IBM X3850 X5 and IBM X3650 M3)............................................290
A.4 Veritas HA System....................................................................................................................................................292
A.4.1 License Management..............................................................................................................................................292
A.4.1.1 Applying for a Veritas License............................................................................................................................292
A.4.1.2 How to Check the Veritas License......................................................................................................................293
A.4.2 System Settings.......................................................................................................................................................294
A.4.2.1 How to Log in and Exit the VCS (Veritas Cluster Server)..................................................................................294
A.4.2.2 How to Query the RVG Status............................................................................................................................296
A.4.2.3 How to Query the Rlink Status............................................................................................................................297
A.4.2.4 How to Query the VVR Status............................................................................................................................300
A.4.2.5 How to check whether the VCS service has been started....................................................................................301
A.4.2.6 How to Manually Start the VCS Service.............................................................................................................301
Issue 01 (2014-05-20) Huawei Proprietary and Confidential vii

Server) Contents
A.4.2.7 How to Manually Start the VVR.........................................................................................................................302

A.4.2.8 How to Manually Stop the VCS Service ............................................................................................................302
A.4.2.9 How to Start/Stop the NMS Before Synchronizing the Primary and Secondary Sites (Solaris, PC Linux).......303
A.4.2.10 How to Ensure Proper Connection of VVR Ports on Primary and Secondary Sites.........................................306
A.4.2.11 How to Change the admin User Password for Logging In to the VCS Client.................................................307
A.5 Sybase Database........................................................................................................................................................307
A.5.1 Startup and Shutdown of the Sybase Database.......................................................................................................307
A.5.1.1 How to Disable the Sybase Database Service.....................................................................................................307
A.5.1.2 How to Start the Sybase Database Service..........................................................................................................308
A.5.1.3 How to Verify That the Sybase Database Is Running.........................................................................................310
A.5.2 Sybase Database Maintenance................................................................................................................................310
A.5.2.1 How to Verify That the Sybase Database Has Been Installed.............................................................................310
A.5.2.2 How to Check the Sybase Database Version.......................................................................................................311
A.5.2.3 How to View the Server Name of the Sybase Database......................................................................................312
A.5.2.4 How to Change the sa User Password for the Sybase Database If the U2000 Is Not Installed...........................313
A.5.2.5 How to Change the Database Administrator Password for the Sybase Database If the U2000 Is Installed.......314
A.5.2.6 How to View the Bit Number of the Sybase Database........................................................................................317
A.5.2.7 How to View the Details of the Sybase Database...............................................................................................317
A.5.2.8 How to Create a Replacement User for the Sybase Database Administrator sa User.........................................318
A.6 U2000 System............................................................................................................................................................321
A.6.1 Failure to Start Certain Processes of the U2000 Server.........................................................................................321
A.6.2 How to Determine Whether an Installed SUSE Linux System is a Local or Remote High Availability System
..........................................................................................................................................................................................322
A.6.3 How to Start the MSuite Client..............................................................................................................................323
A.6.4 Changing the Password of the MSuite....................................................................................................................324
A.6.5 How to Check Whether the U2000 Processes of the High Availability System (Solaris, PC Linux) Are Started
..........................................................................................................................................................................................325
A.6.6 How to Start the U2000 Processes of the High Availability System (Solaris, PC Linux).....................................326
A.6.7 How to End the U2000 Processes of the High Availability System (Solaris, PC Linux)......................................327
A.6.8 How to Determine Which Types of Software Are Preinstalled..............................................................................328
A.6.9 Which Installation Packages Are Required for U2000 Installation........................................................................328
A.6.10 How to View Network Configurations for the Primary Site or Secondary Site Installed with a HA System (SUSE
Linux)...............................................................................................................................................................................331
A.6.11 How to Check Downloaded Software Packages by Using HashMyFiles Software.............................................334
A.6.12 How to Set the Communication Mode of the Server in a High Availability System (Solaris, SUSE Linux)
..........................................................................................................................................................................................335
A.6.13 How to Confirm the Encoding Format of the U2000 License File......................................................................337
A.6.14 How to Change the OS User Password................................................................................................................338
A.6.15 How to Use the FileZilla to Transfer Files by SFTP............................................................................................339
A.6.16 How to Transfer Files by Means of FTP..............................................................................................................342
A.6.17 How to Check and Change an OS User ID...........................................................................................................343
A.6.18 How to Burn the ISO File to DVD.......................................................................................................................344
Issue 01 (2014-05-20) Huawei Proprietary and Confidential viii

Server) Contents
A.7 Install the U2000 Software Exception Processing ....................................................................................................346

A.7.1 How to Solve the Problem Where the Amount of Remaining Data Keeps 99% During Data Synchronization in a
High Availability System.................................................................................................................................................346
A.7.2 How do I solve the problem where a failure message is displayed during the installation or the installation is
abnormally interrupted.....................................................................................................................................................347
A.7.3 How to Handle Messages Indicating That the Port Is Occupied During Installation or Uninstall.........................348
A.7.4 How to Rectify the Failure to Connect to the Sybase Database During U2000 Installation..................................348
A.7.5 Failure to Log In to the U2000 Server from a U2000 Client..................................................................................349
A.7.6 How to Resolve the Problem that the License Does Not Take Effect....................................................................352
A.7.7 How to Solve Common Problems About Using the Network Mode to Installing a U2000 Client........................352
A.7.8 How to Rectify the Failure to Open the CAU Download Web Page Because the Port Is Used............................353
A.7.9 How to Resolve the Problem that the Database Installation File Is Not Found During Installation......................354
A.7.10 How to Address the U2000 Installation or Uninstallation Failure.......................................................................355
A.7.11 How to Troubleshoot the Heartbeat IP Address Unavailability That Causes the Primary and secondary sites
Synchronization Failure....................................................................................................................................................357
B Uninstalling the U2000 Software...........................................................................................361

B.1 Uninstall Preparations................................................................................................................................................362
B.2 Uninstalling U2000 Software....................................................................................................................................365
B.3 Verifying the Uninstall Status of the Server Software...............................................................................................367
C Manual Commissioning Task................................................................................................368

C.1 Configuring a Digital Certificate...............................................................................................................................369
C.1.1 Replacing SSL Certificates Used for the Communication Between the U2000 Server and Client........................369
C.1.2 Replacing SSL Certificates Used for the Communication Between the U2000 and uTraffic................................373
C.1.3 Replacing SSL Certificates Used for the Communication of the Internet Explorer browser.................................377
D Starting the U2000 Server in a SUSE Linux High Availability System.........................379

D.1 Powering On the Server Safely..................................................................................................................................380
D.2 Starting the Database.................................................................................................................................................382
D.3 Starting the U2000 Server Processes.........................................................................................................................384
E Shutting Down the U2000 Server in a High Availability System (PC Linux)...............387
E.1 Stopping the U2000 Server Processes........................................................................................................................388
E.2 Shutting Down the Database......................................................................................................................................389
E.3 Stopping the VCS Service..........................................................................................................................................390
E.4 Power Off the Server Safely......................................................................................................................................391
F Getting Started...........................................................................................................................392
G Planning Disk Partitions........................................................................................................ 397
H Configuring Disk Arrays........................................................................................................400
H.1 Configuring the OceanStor S3900 Disk Array by Using the ISM............................................................................401
I Glossary and Abbreviations....................................................................................................416
Issue 01 (2014-05-20) Huawei Proprietary and Confidential ix

Server) 1 Installation Overview
1 Installation Overview
About This Chapter
Before installing and commissioning the U2000, you must get an understanding of the software
and hardware configuration requirements and networking requirements of the U2000 as well as
the restrictions on installing and commissioning the U2000.
1.1 Networking Structure

This topic describes the solutions that the U2000 supports as well as the networking of the Local
SUSE Linux high availability system (PC server) solution.
1.2 Configuration Requirements

This topic describes the configuration requirements on the hardware and software of the server
before installing the U2000.
1.3 Restrictions on Installation and Commissioning

You must learn about the restrictions of the U2000 during the U2000 installation and
commissioning.
Issue 01 (2014-05-20) Huawei Proprietary and Confidential 1

1.1 Networking Structure

This topic describes the solutions that the U2000 supports as well as the networking of the Local
SUSE Linux high availability system (PC server) solution.
The solutions can be classified into the following types based on OS type of the U2000 and
whether the U2000 supports a high availability system.
l Single-Server System (Windows)
l Single-Server System (Solaris)
l Single-Server System (SUSE Linux, PC Server)
l Single-Server System (SUSE Linux, VMware)
l High Availability System (Solaris)
l Local SUSE Linux High Availability System (PC server)
l Remote SUSE Linux High Availability System (PC server)
This manual describes the installation and commissioning of the Local SUSE Linux high
availability system (PC server). Figure 1-1 and Figure 1-2 show the networking of the Local
SUSE Linux high availability system (PC server).
Figure 1-1 Networking structure of Local SUSE Linux high availability system (PC server) in
a four-NIC solution
Primary Site Secondary Site

Heartbeat/Replication line (Bond protection)
System/Application line (Bond protection)
Switch
Router
DCN
GNE
NMS Client

Figure 1-2 Networking structure of Local SUSE Linux high availability system (PC server) in
a six-NIC solution
Primary Site Secondary Site

Heartbeat/Replication line (Bond protection)
Application line (Bond protection)
Switch
System line (Bond protection)
Router
DCN
GNE
NMS Client
Terms
To ensure the U2000 install successfully, definitions for terms as used in this document before
introducing the U2000 scheme:
l Server: A server can refer to either hardware or software. In the client/server structure, a
server refers to the server program. The term refers to hardware when used in reference to
a computer where a server program runs.
l Client: Refers to the client application of the software in a client/server structure. The client
application can run on a computer along with the server application or on a separate
computer. The term refers to hardware when used in reference to the computer where a
client application runs.
l Workstation and host: A workstation functions the same as a host. Generally, a
workstation or host refers to the computer where services run in a SUSE Linux OS.
l Primary (Secondary) site: Used for the high availability system, the primary (secondary)
site refers to the physical primary (secondary) site. Whether a site is a primary site or a

secondary site is specified when it is installed, and the role does not change when the active/
standby switchover occurs. In most of the time, a primary site is in the active state, whereas
a secondary site is in the standby state for protecting the primary site.
l Active (Standby) site: It is used for the high availability system. The active (standby) site
refers to the site in the active (standby) state. The site in the standby state protects the site
in the active state.
l Active (Standby) state: It is used for the high availability system. The active (standby) state
refers to the working (protection) state. For example, if all the relevant applications on a
site run normally, this site is in the active state.
Networking Description:
The following describes the deployment of the U2000 server, U2000 client, switch, router, disk
array, and gateway NEs, as well as the communication relationships.
l Local SUSE Linux high availability system (PC server) consists of the Primary Site and
the Secondary Site. Each site is composed of one workstation.
l The NMS client and the NMS Maintenance Suite client communicate with the server over
a DCN.
l Network elements (NEs) and the upper-layer NMS (OSS) communicate with the server
over a DCN.
l In a four-NIC solution, heartbeat lines are reused as replication lines and bond needs to be
configured; system lines are reused as application lines and bond and float IP addresses
need to be configured. Replication/Heartbeat lines, application lines, and system lines
recommended located on different network segments. In this solution, the system and
application IP addresses are configured on the same NIC. Select this solution if the system
and application IP addresses do not need to be isolated physically.
l In a six-NIC solution, heartbeat lines are reused as replication lines and bond needs to be
configured; bond needs to be specifically configured for system lines and application lines;
floating IP address must be configured. The replication/heartbeat, application, and system
lines are recommended to be located in different network segments for network fault
isolation. This solution allows for the configuration of the system and application IP
addresses on two network interfaces and different network segments. This solution is used
when the system IP address needs to be isolated from the application IP address.
l The disk array stores data to improve database performance. The server must be configured
with a disk array if the U2000 manages a moderate amount of network elements (NEs).
1.2 Configuration Requirements

This topic describes the configuration requirements on the hardware and software of the server
Hardware Configuration
The following table shows the configuration requirements on the hardware of the U2000 server.

Table 1-1 Configuration requirements on the hardware for the U2000 server
Network Scale Server Description
Small-scale network: less IBM X3650 M4

than 2000 equivalent NEs l CPU: 2*Xeon 6Core 2.5 GHz or above
l Memory: 32 GB or above
l Hard disk: 8 x 300 GB or above
Tecal RH2288H V2
l CPU: 2*Xeon 6Core 2.5 GHz or above
Medium-scale network: IBM X3850 X5

2000-6000 equivalent l CPU: 4*Xeon 8Core 2.0 GHz or above
NEs
Tecal RH5885H V3
NOTE
When only access-domain NEs are managed, the following server also
supports management of a medium-scale network.
IBM X3650 M4
Tecal RH2288H V2
Large-scale network: For access single-domain cases:

6000-15000 equivalent IBM X3850 X5
NEs
Tecal RH5885H V3

Network Scale Server Description
Super-large-scale For access single-domain cases:

network: 15000-20000 IBM X3850 X5+disk array
equivalent NEs
Tecal RH5885H V3+disk array
Table 1-2 Recommended configurations of the disk array
Hardware Disk Array Hardware Capacity

Configuration Version
Item
Delivered software V100R002C00 16 GB memory, 12 x 600 GB

platform: OceanStor
S3900
NOTE
An M200 controller
enclosure is delivered
with disk arrays.
NOTE
l The preceding table shows the recommended delivery configuration. The compatible configuration
varies according to managed NEs and network size. For details, see chapter Management Capabilities
of the U2000 on Different Hardware Platforms in the U2000 Planning Guide.
l U2000 installation, deployment, or running may fail on incompatible servers or servers with non-
recommended configurations.
Software Configuration
The following table shows the configuration requirements on the software of the U2000 server.

Table 1-3 Configuration requirements on the software for the U2000 server
Configuration Item Typical Configuration
OS SUSE Linux Enterprise Server 10 SP4

NOTE
If the OS and patch versions on the live network are earlier or later than
the required version, reinstalling the OS and patches of the required
version is recommended to ensure that the U2000 runs properly.
l On the desktop, right-click in the blank area and choose Open
Terminal from the shortcut menu to access the CLI.
l Run the following command to view the OS version:
# cat /etc/SuSE-release
If the following information is displayed, the SUSE Linux version is
correct:
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 4
l Run the following command to view the OS kernel version:
# uname -rv
The information similar to 2.6.16.60-0.103.1 is displayed. Here,
2.6.16.60-0.103.1 indicates the kernel version of the OS.
If the kernel version is 2.6.16.60-0.103.1, the kernel version is
correct.
Veritas software Veritas 6.0.1+6.0.3
Database SYBASE 15.5 with EBF21264+ESD#5.3
NMS software U2000 software
1.3 Restrictions on Installation and Commissioning

You must learn about the restrictions of the U2000 during the U2000 installation and
commissioning.
Read carefully the following restrictions before installation and commissioning:
l To prevent program conflict, it is recommended that other unnecessary software not be

installed on the U2000 server.
l Only one U2000 can be installed on a server.
l The U2000 can be installed only on an OS with either the simplified Chinese character set
zh_CN or the English character set en_US.
l A virtual machine supports the installation only of a single-server U2000 running on the
SUSE Linux OS. The U2000 using other solutions cannot be installed on the virtual
machine.
l The working temperature of the IBM server cannot exceed 41°C. Otherwise, the IBM server
may be automatically stopped.

Server) 2 Installation Procedure
2 Installation Procedure
This topic describes the processes for installing and commissioning the High Availability System
(SUSE Linux, PC Server) as well the time required for every operation.
NOTE
Installation engineers not familiar with SUSE Linux OS should read F Getting Started to learn about the
basic operations of the system.
U2000 installation and commissioning covers three scenarios: pre-installation, on-site

installation and commissioning, and on-site installation only.
Commissioning Procedure in the Pre-installation Scenario

Usually, the server delivered by Huawei has been preinstalled, the primary and secondary sites
have been separated, and you do not need to reinstall the U2000 on the server. You can directly
commission the U2000 and modify the system and U2000 parameters according to on-site
requirements to allow for the normal use of the U2000.
A series of parameters need to be modified during commissioning. You must ensure that on-site
parameters have been planned based on the U2000 Planning Guide before commissioning is
performed.
Figure 2-1 shows the commissioning procedure in the pre-installation scenario.

Figure 2-1 Commissioning procedure in the pre-installation scenario
Installation and Commissioning Procedure in the On-site Installation Scenario

If the server has not been preinstalled by Huawei, install the U2000 and commission the
system.A series of parameters need to be modified during commissioning. You must ensure that
on-site parameters have been planned based on the U2000 Planning Guide before
commissioning is performed.
Figure 2-2 shows the installation and commissioning procedure in the on-site installation
scenario.

Figure 2-2 Installation and commissioning process in the on-site installation scenario
NOTE
Before configuring routes, install the U2000 software on both the primary and secondary sites. You can
install the U2000 software first on either the primary site or secondary site.
In this scenario, you can connect the primary and secondary sites after basic commissioning is complete.
On-site Installation Only

Figure 2-3 shows the procedure for on-site installation only.

Figure 2-3 On-site installation procedure
NOTE
Before configuring routes, install the U2000 software on both the primary and secondary sites. You can install
the U2000 software first on either the primary site or secondary site.

Server) 3 Installing the U2000
3 Installing the U2000
About This Chapter
This topic describes how to obtain the required reference information about U2000 installation
and how to install the U2000. If the U2000 has been preinstalled, skip this topic and directly
commission the U2000. For details about how to commission the U2000, see Commissioning
the U2000.
3.1 Installation Preparations

This topic describes the information to get familiar with before installing the High Availability
System (SUSE Linux, PC Server). You must collect installation information, check the required
software, check hardware connections, and apply for a U2000 license and a Veritas License.
3.2 Powering On a Server

This topic describes how to power on a server and the position of the power button.
3.3 Configuring Controller IP Addresses

Controller IP addresses are used to manage and maintain servers remotely. Configure controller
IP addresses for servers before installing the operating system (OS).
3.4 Configuring RAID

RAID needs to be configured before an operating system is installed in order to improve the
efficiency and security of using server hard disks.
3.5 Installing the SUSE Linux OS by Using the Quick Installation CD-ROM
This topic describes how to use a quick installation DVD-ROM delivered with Huawei devices
to install the SUSE Linux OS.
3.6 Installing the U2000 Software

This topic describes how to start the U2000 installation program after a U2000 is preconfigured
by using a DVD-ROM or software package.
3.7 Configuring a Route

Before connecting the primary and secondary sites, ensure that the application, heartbeat, and
replication routes are reachable between the primary and secondary sites. If these routes are
unreachable, the primary and secondary sites cannot be connected. If the primary and secondary
sites are on different network segments, refer to this topic to add routes on the other network
segment for the primary and secondary sites. If the U2000 server and client are on different

network segments, you also need to refer to this topic to add routes on the other network segment
for the primary and secondary sites.
3.8 Connecting the Primary and Secondary Sites

This topic describes how to connect the primary and secondary sites using the MSuite. After the
U2000 is installed on the primary and secondary sites, you must connect the primary and
secondary sites to establish a high availability system.
3.9 Loading or Updating a License File

This topic describes how to load or update a license file. After a U2000 is installed, it is
recommended that you update the Veritas license file and load the U2000 license file in time.
You can update the Veritas license before loading the U2000 license file or vice versa.
3.10 Checking System Installation

This topic describes how to check the installation of a high availability system (SUSE Linux,
PC Server).

3.1 Installation Preparations

This topic describes the information to get familiar with before installing the High Availability
System (SUSE Linux, PC Server). You must collect installation information, check the required
software, check hardware connections, and apply for a U2000 license and a Veritas License.
3.1.1 Collecting Installation Information

This topic describes how to collect installation information. Before installing the High
Availability System (SUSE Linux, PC Server), collect required information, including the host
name, IP address, route, time zone and time, user password, and disk partition.
Complete planning for the information listed in the following tables according to the U2000
Planning Guide.
NOTE
Print the following tables and fill in the blanks with the site-specific planning information.
Examples provided in the tables are the default values of servers that come pre-installed with software from
Huawei.
Host Name Planning
NOTICE
To ensure that the NMS can run properly, host name planning must comply with the following
rules and restrictions:
l The host name of the U2000 server must be unique on the network.
l The host name must be a string consisting of no more than 24 characters that can only be
letters (A to Z, a to z), digits (0 to 9) and hyphen (-).
l The first character must be a letter and the last character cannot be a hyphen.
l The host name cannot contain --.
l The host name must be case-sensitive.
l The host name cannot be empty or contain spaces.
l The host name cannot contain only one character.
l The host name cannot be any of the following keywords in the high availability system.
action false keylist static after firm local stop requires
remotecluster
system group resource global Start str temp set heartbeat
ArgListValues
System Group boolean hard Name soft before online condition
MonitorOnly
remote start cluster event VCShm type Path offline Signaled
HostMonitor
Probed state Cluster IState int Type State VCShmg NameRule
ConfidenceLevel

Table 3-1 Host name list
Site Item Example Plan
Primary Site Host name Primaster
Secondary Host name Secmaster

Site
IP Address Planning
You need to plan the following types of IP addresses:
l System IP address: This IP address is the IP address of the OS. You can use it to log in to
the server to manage and maintain the OS.
l IP address of the heartbeat and replication: This type of IP address is used to detect status
of the network connection and replicate data between the primary and secondary sites.
l NMS application IP address: This IP address is used for external NMS services such as
communication between the NMS server and clients or between the NMS server and
NEs.
l Float IP address: The float IP address is used for the communication with NBIs.
l IP address of the IMM on the PC server: It is used to remotely manage the server.
l IP address for the disk array controller: This IP address is used to remotely manage and
maintain disk arrays.
NOTE
l The IMM/iMana IP address and system IP address can be located either on the same network segment
or on different network segments.
l The IP address is in the format of IP address/subnet mask/gateway.
l Planning Principles for IP Addresses are:
l The IP addresses must be unique on the network.
l The U2000 servers communicate with U2000 clients in the normal state.
According to the number of required network interfaces, and function types of configured IP
addresses, multiple IP address planning schemes are available for the high availability system
(SUSE Linux-distributed). The typical IP address planning schemes are as follows.
l Four-Network Interface Solution
Four-network interface solution: Four network interfaces are required. In this solution,
the system and application IP addresses are configured on the same NIC. Select this solution
if the system and application IP addresses do not need to be isolated physically.
IP planning description:
– Select the network scheme based on the planned IP address. It is recommended that the
replication network reuse the heart beat network and the application network reuse the
system network.
– Eth0 is used to configure the system and application IP addresses. The float IP address
also needs to be configured. Configure Bond on eth0 and eth4.

– Eth1 is used to configure the heartbeat and replication IP addresses. Configure Bond
on eth1 and eth5.
– Configuring the replication/heartbeat IP addresses and application/system IP addresses
to different network segments is recommended in order to ensure network fault
isolation.
– A float IP address needs to be set for a U2000 system and application IP address and
the two IP addresses must be on the same network segment. The float IP address is used
for the communication with NBIs. The floating IP address remains unchanged after a
primary/secondary switchover. When the U2000 communicates with NEs, the U2000
application IP addresses are required.
NOTE
If you remotely log in to the U2000 Client or MSuite client, use the application IP address.
– The floating IP addresses for the primary and secondary sites are the same.
IP planning example: Table 3-2 shows the planning example.
Table 3-2 Example of IP address planning of the four-network interface scheme
Site Item Example (IP Remarks

Address/Subnet
Mask/Gateway)
Primary IMM/iMana IP 129.9.1.20/255.255.2 -

site address 55.0/129.9.1.254
IP address for the OceanStor S3900: -

disk array l Controller 1:
controller 129.9.1.22/255.2
55.255.0/129.9.1.
254
l Controller 2:
129.9.1.23/255.2
55.255.0/129.9.1.
254
System IP address l 129.9.1.1/255.25 The U2000 and MSuite

and system bond 5.255.0/129.9.1.2 clients connect to servers
solution 54 using the application IP
Application IP l Bond solution: address. The MSuite tools at
address reusing Configure bond the primary and secondary
system IP address on the eth0 and sites communicate with each
eth4 interfaces. other using the application IP
address. Therefore, ensure
NOTE
To protect
that the application IP
network network between the primary
interfaces, do not and secondary sites functions
configure bond on properly.
network interfaces
that are located on
the same NIC.


Address/Subnet
Mask/Gateway)
Heartbeat IP l 192.168.10.10/25 -
address and 5.255.255.0/192.
heartbeat bond 168.10.254
solution l Bond solution:
Replication IP Configure bond
address reusing on the eth1 and
heartbeat IP eth5 interfaces.
address NOTE
To protect
network
interfaces, do not
configure bond on
network interfaces
that are located on
the same NIC.
Configuring the l 129.9.1.3/255.25 -

float IP address 5.255.0/129.9.1.2
54
l Used network
port: eth0
Secondar IMM/iMana IP 129.9.1.21/255.255.2 -

y site address 55.0/129.9.1.254
IP address for the OceanStor S3900: -

disk array l Controller 1:
controller 129.9.1.24/255.2
55.255.0/129.9.1.
254
l Controller 2:
129.9.1.25/255.2
55.255.0/129.9.1.
254


Address/Subnet
Mask/Gateway)
System IP address l 129.9.1.2/255.25 The U2000 and MSuite

and system bond 5.255.0/129.9.1.2 clients connect to servers
solution 54 using the application IP
Application IP l Bond solution: address. The MSuite tools at
address reusing Configure bond the primary and secondary
system IP address on the eth0 and sites communicate with each
eth4 interfaces. other using the application IP
address. Therefore, ensure
NOTE
To protect
that the application IP
network network between the primary
interfaces, do not and secondary sites functions
configure bond on properly.
network interfaces
that are located on
the same NIC.
Heartbeat IP l 192.168.10.11/25 -
address and 5.255.255.0/192.
heartbeat bond 168.10.254
solution l Bond solution:
Replication IP Configure bond
address reusing on the eth1 and
heartbeat IP eth5 interfaces.
address NOTE
To protect
network
interfaces, do not
configure bond on
network interfaces
that are located on
the same NIC.
IP address of the l 129.9.1.3/255.25 -

floating network 5.255.0/129.9.1.2
service 54
l Used network
port: eth0
l Six-Network Interface Solution

Six-network interface solution: Six network interfaces are required. In this solution, the
system and application IP addresses are configured on two NIC respectively. Select this
solution if the system and application IP addresses do not need to be isolated physically.
IP planning description:
– Select the network scheme based on the planned IP address. It is recommended that the
replication network reuse the heart beat network, the application network is as an
independent network, and the system network is as an independent network.

– Eth0 is used to configure the system IP address. Configure Bond on eth0 and eth4.
– Eth1 is used to configure the heartbeat and replication IP addresses. Configure Bond
on eth1 and eth5.
– Eth2 is used to configure the application IP address and float IP address. Configure
Bond on eth2 and eth6.
– Configuring the replication/heartbeat IP address, application IP address, and system IP
address to different network segments is recommended in order to ensure network fault
isolation.
– A float IP address needs to be set for a U2000 system and application IP address and
the two IP addresses must be on the same network segment. The float IP address is used
for the communication with NBIs. The floating IP address remains unchanged after a
primary/secondary switchover. When the U2000 communicates with NEs, the U2000
application IP addresses are required.
NOTE
If you remotely log in to the U2000 Client or MSuite client, use the application IP address.
– The floating IP addresses for the primary and secondary sites are the same.
Table 3-3 shows a planning example.
Table 3-3 IP address planning for a six-network interface solution
Sit Item Example (IP Address/ Remarks

e Subnet Mask/Gateway)
Pri IMM/iMana 129.9.1.20/255.255.255.0/ -

ma IP address 129.9.1.254
ry
sit IP address OceanStor S3900: -
e for the disk l Controller 1:
array 129.9.1.22/255.255.25
controller 5.0/129.9.1.254
l Controller 2:
129.9.1.23/255.255.25
5.0/129.9.1.254
Configuring l 129.9.1.1/255.255.255. -
the system 0/129.9.1.254
IP address l Network interface: eth0
Configuring l 192.168.10.10/255.255 -
the heartbeat .255.0/192.168.10.254
and l Network interface: eth1
replication
IP addresses


Configuring l 129.9.3.1/255.255.255. The U2000 and MSuite clients

the 0/129.9.3.254 connect to servers using the
application l Network interface: eth2 application IP address. The MSuite
IP address tools at the primary and secondary
sites communicate with each other
using the application IP address.
Therefore, ensure that the
application IP network between the
primary and secondary sites
functions properly.
Configuring l 129.9.3.3/255.255.255. -
the float IP 0/129.9.3.254
address l Network interface: eth2
Configuring Network interface: eth4 -

bond for the
system
network
interface

bond for the
heartbeat
and
replication
network
interfaces

bond for the
application
network
interface
Se IMM/iMana 129.9.1.21/255.255.255.0/ -
co IP address 129.9.1.254
nd
ary IP address OceanStor S3900: -
sit for the disk l Controller 1:
e array 129.9.1.24/255.255.25
controller 5.0/129.9.1.254
l Controller 2:
129.9.1.25/255.255.25
5.0/129.9.1.254
Configuring l 129.9.1.2/255.255.255. -
the system 0/129.9.1.254
IP address l Network interface: eth0


Configuring l 192.168.10.11/255.255 -
the heartbeat .255.0/192.168.10.254
and l Network interface: eth1
replication
IP addresses
Configuring l 129.9.3.2/255.255.255. The U2000 and MSuite clients

the 0/129.9.3.254 connect to servers using the
application l Network interface: eth2 application IP address. The MSuite
IP address tools at the primary and secondary
sites communicate with each other
using the application IP address.
Therefore, ensure that the
application IP network between the
primary and secondary sites
functions properly.
Configuring l 129.9.3.3/255.255.255. -
the float IP 0/129.9.3.254
address l Network interface: eth2

bond for the
system
network
interface

bond for the
heartbeat
and
replication
network
interfaces

bond for the
application
network
interface

Route Planning
Table 3-4 Route list
Item Example Plan
Routing network 129.9.10.0/255.255.255.0

segment 1
Routing network 10.71.6.0/255.255.255.0

segment 2
... ...
Routing network 10.121.124.0/255.255.255.0

segment N
NOTE
Installation engineers need to add routes to the client and management network to ensure communication
between the U2000 and the client, and between the U2000 and the management network.
Time Zone and Time Planning
Table 3-5 Time zone and time list
Item Example Plan
Time zone Asia > Beijing
Time 14:00
User Name and Password Planning
NOTICE
The passwords are examples only. Change the passwords after completing the installation. The
default password indicates the initial password used when the U2000 is installed for the first
time. Production preinstallation indicates the U2000 software has been installed initially.
NOTE
This manual describes only the disk array users used during the U2000 installation. To obtain information
about more disk array users, parameters, and operations, see the product manual of the specific disk array.

Table 3-6 User and password list
User Default Password Password Set After Planned Password

Preinstallation
IMM user PASSW0RD PASSW0RD

USERID NOTE
The sixth character is
digit 0 but not letter O.
iMana user Huawei12#$ Huawei12#$

root
OceanStor Admin@storage Changeme_123

S3900 user
admin
OS user root Changeme_123 Changeme_123
OS user Changeme_123 Changeme_123

ossuser
OS user Changeme_123 Changeme_123

dbuser
Database Changeme_123 Changeme_123

administrator
sa
Customized None. Changeme_123

database NOTE
administrator In order to enhance the
security of the database
after the U2000 is
installed, the sa user may
be manually disabled
and replaced with a
customized
administrator name,
such as dbadmin.
NMS None. Changeme_123

Database user NOTE
dbuser The dbuser user does
not have a default
password. The password
of the dbuser user must
be configured during
U2000 installation.

User Default Password Password Set After Planned Password

Preinstallation
U2000 user Changeme_123 Admin_123

admin NOTE
l You must change the
default password
during first-time
login.
l The password for the
U2000 System
Monitor must be the
same as that for the
U2000 client.
Network Changeme_123 Changeme_123

Management NOTE
System You must change the
Maintenance default password during
Suite user first-time login.
admin
VCS Client Changeme_123 Changeme_123

User admin
Disk Partition Scheme

If a quick installation DVD is used to install an OS, the installation software automatically
partitions disks according to the disk size. Before manually install an OS, determine the disk
partitioning scheme. For details about disk partitioning planning, see G Planning Disk
Partitions.
3.1.2 Checking Required Software

This topic describes how to verify that the software meets U2000 installation requirements.
The U2000 can be installed by using software packages or DVDs, as follows:

l Using software packages: Required software packages must be on-hand. Only Huawei
engineers have the permissions to download software packages. If the installation using
software packages is required, contact Huawei engineers to obtain software packages.
l Using DVDs: Required DVDs must be on-hand. The DVDs are delivered along with the
product.
Using Software Packages

Perform the following operations:
NOTE
If the Read Me_U2000 Version(English) file exists, read the Read Me_U2000 Version(English) file before
downloading the software packages. The Read Me_U2000 Version(English) file is stored in the same path
as software packages.

1. Access http://support.huawei.com and choose Software Center > Version Software >
Network OSS&Service > iManager U2000 > iManager U2000 > iManager U2000 >
iManager U2000 V200R014.
2. Select the version to be installed.
3. Download required software packages listed in Table 3-7. It is recommended that you use
the download tool (for example, NetAnts). If you use Windows Internet Explorer, some
software packages may be renamed automatically after being downloaded to the local
computer. In this case, you must manually change the software package names to the same
as those on the http://support.huawei.com.
4. Use the HashMyFiles to verify correctness of the software packages. For details, see A.
6.11 How to Check Downloaded Software Packages by Using HashMyFiles
Software.
5. http://support.huawei.com can store files with a maximum size of 1.8 GB. The file with
the size larger than 1.8 GB will be separated into different software packages. The file name
extension is zip.001 for the first package, zip.002 for the second, zip.003 for the third, and
so on.
l Download all the required packages. Read the Read Me_U2000 Version(English) file
before downloading the software package. The Read Me file contains key instructions
and restrictions on downloaded files.
l Before selecting the zip.001 file to decompress, obtain the 7-zip tool with the latest
version from Web site http://downloads.sourceforge.net/sevenzip and install the tool.
For more information about software operation, see the software Help or go to the
official website of the software for technical support.
NOTE
l The SUSE Linux OS can be installed only by using DVDs. Therefore, if you install the U2000 by using
software packages, ensure that the SUSE Linux OS installation DVD is available.
l In an installation DVD or installation package, version indicates the detailed version number of the
U2000.
l The commonly used recording software is Nero. Nero 8 is used as an example here. To ensure that the
contents of the burnt DVD are the same as those in the ISO file, select the Verify data on disc after
burning check box. For details, see How to Burn the ISO File to DVD.
Table 3-7 Software package list
Software Medium Name Description
SUSE Linux Quick OS installation DVD It must be available. It is used to

OS Disk U2000version_server_os_sles_x64 install the SUSE Linux OS.
_dvd1 or ISO image file of the quick
installation DVD
U2000version_server_os_sles_x64
_dvd1.iso.

Quick RAID l For Huawei RH series rack It must be available. It is used to

configuratio server, the configure RAID.
n DVD Sles_server_raid_x64_for_Hua
wei_dvd.iso file is must be ready.
l For IBM server, the ISO image
file
Sles_server_raid_x64_for_IBM
_dvd.iso is must be ready.
SetSuse Installation package: It must be available. It is used to

software U2000version_ enhance the security of SUSE Linux
package VPPSetSuseV300R003C20SPC100 OS.
.tar
Database Database software package: It must be available. It is used to

software U2000version_ install the database.
package server_db_linux_sybase.tar
Veritas 1. Veritas software installation It must be available. It is used to

software package: install the Veritas.
U2000version_
veritas6.0.1_sles_x64.tar.gz
2. Veritas patch package:
U2000version_
server_veritas603_patch_sles_x
64.tar
U2000 Basic component: It must be available. It is used to

server U2000version_ install the U2000.
software server_nmsbase_sles_x64.7z
Preconfigured component: It must be available. It is used to

U2000version_ install the U2000.
server_icmr_sles_x64.7z
Core component: It must be available. It is used to

server_nmscore_sles_x64.7z
Transport component: It must be available. Huawei

U2000version_ transport equipment includes:
server_nmstrans_sles_x64.7z l MSTP equipment
l WDM equipment
l NA WDM equipment
l Submarine equipment
l RTN equipment
l PTN equipment

IP component: It must be available. Huawei IP

U2000version_ equipment includes:
server_nmsip_sles_x64.7z l ATN Series Equipment
l Routers
l Switches
l Metro service equipment
l Broadband access equipment
l VoIP gateways
l Firewalls
l Service inspection gateway
l SVN equipment
l Internet Cache System
Access component: It must be available. Huawei access

server_nmsaccess_sles_x64.7z l FTTx equipment
l MSAN equipment
l DSLAM equipment
l BITS equipment
ESN tool ESN tool: The ESN tool is required only when
U2000version_ESN_sles_x64.tar you apply for the U2000 License
NOTE
The tool is a software package. It will not
be delivered as a DVD-ROM. After the
U2000 is installed, the ESN tool is
available in the U2000 installation path.
Therefore, to apply for the U2000 license
after the U2000 is installed, use the ESN
tool in this path directly.
Using DVDs
Before installing the U2000 by using DVDs, ensure that the following DVDs are available.
Table 3-8 DVD list
Software DVD Name
SUSE Linux OS Quick installation DVD 1:

installation DVD U2000version_server_os_sles_x64_dvd1

Software DVD Name
Quick RAID l For Huawei RH series rack server, the

configuration DVD Sles_server_raid_x64_for_Huawei_dvd.iso file is must be
ready.
l For IBM server, the ISO image file
Sles_server_raid_x64_for_IBM_dvd.iso is must be ready.
Database software U2000version_server_db_sles_x64_dvd3

DVD
Veritas software DVD 1. Veritas software installation DVD: Sles_Veritas6.0.1

2. Veritas patch DVD:
U2000version_server_patch_sles_x64_dvd2
U2000 server software U2000version_server_nms_sles_x64_dvd4

DVD NOTE
U2000 server software include SetSuse software package, it is used to
enhance the security of SUSE Linux system.
ESN tool U2000version_ESN_sles_x64.tar

The ESN tool is required only when you apply for the U2000
License before installing the U2000.
NOTE
The tool is a software package. It will not be delivered as a DVD-ROM. After
the U2000 is installed, the ESN tool is available in the U2000 installation
path. Therefore, to apply for the U2000 license after the U2000 is installed,
use the ESN tool in this path directly.
Obtaining Tools
Table 3-9 shows the tools required to be available before the U2000 is installed using software
packages or DVDs.

Table 3-9 Tool list
N Tool Usage Description

o
.
1 For IBM On the PC l If a JRE has been installed, run the java -version command
server, or laptop, in the CLI to view the JRE version. If a JRE has not been
JRE with JRE is used installed, running the command fails.
the to access l If the version of the installed JRE is not 1.7.0_51,
version the remote downloading and installing JRE 1.7.0_51 is recommended.
of control You can uninstall the existing JRE in Control Panel.
1.7.0_51. desktop
through IE. l If a message is displayed asking you to enter a user name
and a password. Enter the user name administrator and
the user password.
If the JRE version does not meet requirements, use any of the
following methods to reinstall the JRE:
l Method one: Download the JRE 1.7.0_51 version from
official websites http://www.java.com/en/download/
ie_manual.jsp?locale=en&host=java.com:80 of the
third-party software and install it.
l Method two: Obtain the latest JRE version from the ISO
image file Sles_server_raid_x64_for_IBM_dvd.iso in the
quick RAID configuration DVD-ROM. The procedure is
as follows:
1. Copy and paste the ISO image file in the quick RAID
configuration DVD-ROM to the PC or laptop.
2. Right-click the ISO image file and choose 7-zip > Open
archive from the shortcut menu.
3. Double-click the executable file in the Java_jre
directory.
2 PuTTY The Download the latest version from official websites http://
software www.putty.org of the third-party software.
uses For more information about software operation, see the
commands software Help or go to the official website of the software for
(telnet and technical support.
SSH) to log
in to the
server.
Using SSH
(more
secure,
recommend
ed) to log in
to the server
is
recommend
ed.

N Tool Usage Description

o
.
3 FileZilla The Download the latest version from official websites http://
tool FileZilla is filezilla-project.org of the third-party software.
used to For more information about software operation, see the
transfer software Help or go to the official website of the software for
files by technical support.
SFTP.
4 7-zip tool The 7-zip Download the latest version from official websites http://
tool is used sourceforge.net/projects/p7zip/ of the third-party software.
to For more information about software operation, see the
decompress software Help or go to the official website of the software for
software technical support.
packages
5 HashMy Download Refer to http://www.nirsoft.net to download the latest

Files tool software version.
compressio For more information about software operation, see the
n package software Help or go to the official website of the software for
used to technical support.
verify the
correctness.
3.1.3 Checking Hardware Connections

This topic describes how to check hardware installation and cable connections before installing
a U2000. If hardware is improperly installed or cable is improperly connected, unexpected error
may occur during installation of the U2000.
Prerequisites
The server hardware must have been installed and equipment cables must have been connected,
for details, see U2000 Hardware Installation Guide (Huawei N610E cabinet).
Procedure
Step 1 Ensure that the power cables and ground wires for all components are tightly connected and in
good contact and that the polarities are properly placed.
NOTE
Generally, the server has two or more power modules which are used to provide power supply protection.
Connect each power module to a specific power input. For details, see U2000 Hardware Installation Guide
(Huawei N610E cabinet).
Step 2 Ensure that all cables are bundled and free of visible damage.
Step 3 Check hardware connections and network cables according to the hardware connection diagram.

NOTE
The two network cables connecting the primary and secondary sites must be super category 5 cables and
less than 60 meters long.
l Four-network interface Solution: Figure 3-1, Figure 3-2, Figure 3-3, Figure 3-4, Figure
3-5, Figure 3-6 and Figure 3-7 shows hardware connections with four network interfaces.
Figure 3-1 Hardware connection for the Huawei Tecal RH5885H V3 server (four network
interface used, with the server connecting to no disk array)

interfaces used, with the server connecting to the disk array OceanStor S3900)
Figure 3-3 Hardware connection for the Huawei Tecal RH2288H V2 server with four
network interfaces

Figure 3-4 Hardware connection diagram of the IBM X3850 X5 server (four network

Figure 3-6 Hardware connection for the IBM X3650 M4 server with four network interfaces

NOTICE
l The system/application network interfaces are connected using a switch to connect the
primary and secondary sites. As shown in the preceding figure, eth0 functions as the
system/application network interface to connect the primary and secondary sites using a
switch.
l The heartbeat/replication network interface is used to connect the primary and secondary
sites. As shown in the preceding figure, eth1 functions as the heartbeat/replication
network interface to connect the primary and secondary sites.
l Two interfaces on another NIC are used to configure bond for the heartbeat/replication
and system/application network interfaces. As shown in the preceding figure, eth4 and
eth5 are used to configure bond.
l The NIC on which the network interfaces used to configure bond reside must be different
from the NIC on which the heartbeat/replication and system/application network
interfaces reside.
l The network cable for configuring Bond must be separately connected to another switch.
l For details about the mappings Between Physical and Logical Network Interfaces on an
IBM Server Running SUSE Linux, see A.3.8 Mappings Between Physical and Logical
Network Interfaces on an IBM Server Running SUSE Linux.
Huawei RH series rack server Running SUSE Linux, see A.2.5 Mappings Between
Physical and Logical Network Interfaces on an Huawei RH Series Rack Server
Running SUSE Linux.
l Six-network interface Solution: Figure 3-8, Figure 3-9, Figure 3-10, Figure 3-11, Figure
3-12, Figure 3-13 and Figure 3-14 shows hardware connections with six network interfaces.
Figure 3-8 Hardware connection diagram of the Huawei Tecal RH5885H V3 server (six
network interface used, with the server connecting to no disk array)

network interfaces used, with the server connecting to the disk array OceanStor S3900)
Figure 3-10 Hardware connection for the Huawei Tecal RH2288H V2 server with six
network interfaces

Figure 3-11 Hardware connection diagram of the IBM X3850 X5 server (six network

Figure 3-13 Hardware connection for the IBM X3650 M4 server with six network interfaces

NOTICE
l The system network interfaces are connected using a switch to connect the primary and
secondary sites. As shown in the preceding figure, eth0 functions as the system network
interface to connect the primary and secondary sites using a switch.
l The application network interfaces are connected using a switch to connect the primary
and secondary sites. As shown in the preceding figure, eth2 functions as the application
network interface to connect the primary and secondary sites using a switch.
l Three interfaces on another NIC are used to configure bond for the system, heartbeat/
replication and application network interfaces. As shown in the preceding figure, eth4,
eth5 and eth6 are used to configure bond.
from the NIC on which the heartbeat/replication and system and application network
interfaces reside.
Running SUSE Linux.
Step 4 Check the plugs and sockets.
1. Ensure that the latches of cable plugs are locked fast.

2. Ensure that the pins in each socket are complete and in good order. Curved pins may cause
short circuits.
----End
Follow-up Procedure
Ensure that all debris (cable straps, stubs, or moisture-absorbent packets) are picked up.
Remove unnecessary items from the telecommunications room. The workbench must be neat
and the movable floor must be level and clean.
3.1.4 Applying for a U2000 License

The U2000 license file is used to control the functions and management capabilities of the
U2000. If the license file is unavailable, you cannot log in to the U2000 client, but can log in to
the System Monitor client and the MSuite.

Context
l The license file is not delivered to customers along with a U2000 installation DVD. Contact
Huawei engineers for the application of a server license according to the contract number
and ESNs of the server.
l To prevent the failure in finding the license file for possible U2000 reinstallation, save the
license application email and the license file properly.
l Before using the U2000, apply for the formal U2000 license in advance because the
U2000 license application goes through a long process.
l An ESN is a string consisting of 40-digit numerals or letters obtained by encrypted
calculation on the MAC addresses of the U2000 server network interface. The number of
ESNs is the same as the number of network interfaces on the U2000 server. To avoid
applying for a new license due to replacing certain network interface cards (NICs), save
all the ESNs to ensure proper use of the U2000 license.
– Generally, the ESN for a server does not change. It can be used for the U2000 license
that is normally applied for.
– If the ESN for a U2000 license is changed due to NIC or server replacement or ESN
application error, apply for a U2000 license again and contact Huawei technical support
engineers.
l In a high availability system (Veritas hot standby) scheme, the primary and secondary
sites share a U2000 license. The U2000 license file is bound to the ESNs of the primary
and secondary sites. When applying for a U2000 license, you must save the ESNs of the
primary and secondary sites separately.
Procedure
Step 1 Obtain the project contract number.
Step 2 View ESNs of the server.
Method 1(Recommended): Use the ESN tool to generate ESNs before installing a U2000.
NOTE
Make the following preparations:

l Huawei engineers have the permission on accessing http://support.huawei.com and download the
official ESN tool.
l The ESN tool name is U2000version_ESN_sles_x64.tar.
version indicates the detailed version number of the U2000. For example, V200R014C50SPCxxx.
l Copy the ESN tool package to the computer.
1. Use SFTP to upload the ESN tool to the U2000 server as the root user. For example, upload
the ESN tool to the /opt path. For details, see A.6.15 How to Use the FileZilla to Transfer
Files by SFTP.
2. Run the following commands to decompress the ESN tool package:
# cd /opt
# tar xvf U2000version_ESN_sles_x64.tar
3. Run the following command to view the ESN:

# ./esn
Information similar to the following is displayed:

ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412

ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
...
Mode 2: View the ESN using the ESN tool of the NMS after installing the U2000.
1. Log in to the OS as user root.
2. Run the following commands to view the ESN:
# cd /opt/oss/server/platform/bin
# ./esn

ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412
ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
...
Step 3 After the esn command is executed, the system automatically generates the Esn.txt path. Send
the contract number and the server ESNs to Huawei engineers or the local Huawei office.
NOTE
Huawei engineers access http://license.huawei.com to obtain the license based on the contract number
and ESNs.
Step 4 Huawei engineers send the license file to you after obtaining it.
NOTE
The license file provided with the U2000 exists as a .dat file.
----End
3.1.5 Applying for a Veritas License

This topic describes how to apply for a formal Veritas license. The Veritas license used during
U2000 installation is a demo license. After the U2000 server is delivered to the installation site,
you must replace the demo license with a formal one in time.
Context
The Veritas licenses for the primary and secondary sites are different and thus must be applied
for separately.
Procedure
Step 1 Collect the following information according to the Veritas license application form:
l Serial number of the license confirmation form
l Contract number
l Software item
l License item quantity

NOTICE
l The license confirmation form is delivered together with the DVD. The license confirmation
form is in paper format and equals the license file. It must be properly stored on site.
l If there are multiple serial numbers and the software items are the same, you must fill in
Software Item Qty with the total number of license confirmation forms.
l The license confirmation form is not delivered along with the product for the license whose
Veritas software BOM starts with 9904. Enter a slash (\) in the license confirmation form
column before contacting Huawei engineers to apply for the Veritas license.
Step 2 Send the information to the related Huawei engineer or the local office of Huawei.
Step 3 With the provided information, the related Huawei engineer accesses http://
support.huawei.com and chooses Software Center > Software License > Outsourcing
License > License Application. The page for applying for purchased software licenses is
displayed.
Step 4 Huawei engineer enters the license application information to apply for a Veritas license.
Step 5 Huawei engineer sends you the Veritas license.
----End
3.2 Powering On a Server

Server
1. Power on a Huawei Tecal RH2288H V2/Huawei Tecal RH5885H V3/IBM X3650 M4/
IBM X3650 M3/IBM X3850 X5 server.
NOTICE
l Huawei Tecal RH2288H V2/Huawei Tecal RH5885H V3 server supports 100 to 240
VAC input voltage.
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC and
200 to 240 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet).
For the High Availability System (SUSE Linux), if the power supply is insufficient, the
server automatically stops and the high availability system fails to trigger an active/
standby switchover.
2. Press the power buttons on the peripherals and monitor connected to a server.
3. Wait 2 to 3 minutes. When the green indicator on the front panel of the server blinks every
1s, press the power button on the shelf of the server.

NOTE
If the power button is steady on, the server has been successfully powered on. For details about IBM
server indicators, see the manual for IBM servers or log in to the official IBM website. For details
about Huawei server indicators, see the manual for Huawei servers or log in to the official Huawei
website.
The red boxes in the following figures show the positions of power buttons on Huawei
Tecal RH2288H V2, Huawei Tecal RH5885H V3, IBM X3650 M4, IBM X3650 M3 and
IBM X3850 X5.
Figure 3-15 Position of the power button on Huawei Tecal RH5885H V3 server
Figure 3-17 Position of the power button on IBM X3650 M4

Figure 3-19 Position of the power button on IBM X3850 X5
Disk Array
NOTICE
l To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables,
or serial cables when powering on a disk array.
l To prevent disk damage and data loss, do not turn on or cut off the power supply when the
disk is accessing data. If the power supply is cut off, wait at least 1 minute before turning it
on.
Power on a disk array.
NOTE
Power supply must be provided for the two power modules of the OceanStor S3900; otherwise, the
OceanStor S3900 fail to be used. Then press the power switch on the controller A / B. Wait 5 to 10 minutes
until the power indicator is steady green, no longer flashing, indicating the success of the power-on.
3.3 Configuring Controller IP Addresses

Controller IP addresses are used to manage and maintain servers remotely. Configure controller
IP addresses for servers before installing the operating system (OS).
3.3.1 Configuring the iMana IP Address of Huawei server

The iMana is integrated with the Huawei RH series rack server. It is used to remotely manage
the server. IP address of the iMana can be used to remotely log in to a PC server to manage and
maintain PC server in Web mode. For example, you can use this IP address for remote OS
installation, or use it to maintain the PC server if the OS fails to start properly. Two modes of
configuring the iMana IP address are available: through iMana management interface and
through BIOS.
If a server is not equipped with the KVM, the mode through iMana management interface is
recommended.

l Through iMana management interface:

– Advantage: The Huawei RH series rack server does not need to be equipped with a
monitor, mouse, or keyboard. Fewer operations are required, compared with the mode
of using BIOS.
– Disadvantage: The Internet Explorer may shut down automatically or not respond. The
troubleshooting procedure is as follows:
1. Right-click the Internet Explorer icon on the taskbar to close the Internet Explorer.
If the Internet Explorer is still open, stop the iexplore.exe process on the
Processes tab page in the Task Manager.
2. Open the Internet Explorer.
l Through BIOS:
– Advantage: No abnormality will occur if operations are performed correctly.
– Disadvantage: The Huawei RH series rack server must be equipped with a monitor,
mouse, and keyboard. More operations are required, compared with the mode of using
the iMana management interface.
3.3.1.1 Configuring the iMana IP Address Through iMana Management Interface

After an iMana IP address is set for a Huawei RH series rack server, you can remotely manage
the server in Web mode. This topic describes how to configure the iMana IP address through
iMana management interface.
Prerequisites
l A PC or laptop on which the Internet Explorer browser is installed is ready.
l The version of the Internet Explorer browser must be 6.0, 7.0, 8.0, or 9.0 and the Internet
Explorer cannot be configured with a proxy server.
l A network cable is available. As network interfaces on an IBM X series server are enabled
with auto-negotiation, either parallel or crossover network cables can be used.
NOTE
If an IE or Remote Virtual Console fault occurs in the iMana, see A.2.4 How to Solve iMana
Problems to rectify the fault.
Context
l The system allows a maximum of four users to log in concurrently, one user to use the
Remote Control function at a time.
l By default, the system timeout period is five minutes. That is, if you do not perform any
operation on the Web UI within five minutes, you are logged out of the Web UI of the
system automatically. In this case, you need to enter the user name and password to log in
again.
l The system locks a user if the user fails to enter a correct password for consecutive five
times. The user is automatically unlocked five minutes later, and the administrator user can
unlock the user in command line.
l To ensure system security, change the initial password after the first login, and then change
your password periodically.

Procedure
Step 1 View the position of the iMana interface on the Huawei RH series rack server.
A management network port for iMana is at the end of the Huawei RH series rack server. You
can visit iMana through this port, as shown in the following figure.
Figure 3-20 Huawei Tecal RH5885H V3 Server
Figure 3-21 Huawei Tecal RH2288H V2 Server
Step 2 Use a network cable to connect the PC and the iMana management interface of the server.
Step 3 Change the IP address and subnet mask of the PC. The IP address of the PC and the default IP
address of the iMana must be in the same network segment.
NOTE
The default IP address of the iMana is 192.168.2.100 and the default subnet mask is 255.255.255.0. If the
default IP address of the iMana is changed, see A.2.2 How to View the IP Address of the iMana on the
Huawei RH series rack server.
Step 4 Run the Internet Explorer, and then enter "https://ipaddress" in the address box.
NOTE
The ipaddress is the IP address of the iMana management network interface.
Step 5 In the displayed Warning dialog box, click Yes.

Step 6 Enter the user name and password, choose whether to log in to the local computer or to the user
domain. Then click Log In.
NOTE
l Default user name: root.

l Default password: Huawei12#$. If the password has been changed, enter the new password. If the
password has not been changed, for system security, modify the default password and remember the
new password. For details, see A.2.3 How to Change the Password of iMana User Root.
Step 7 Click the Network icon in the Common Operations area.
Step 8 Choose Manually Set an IP Address in the IPv4 area. Set the IP, the subnet mask, and the
default gateway of the iMana as required.
Step 9 Click OK in the IPv4 area.

NOTE
l The window stays at the page for changing IP, ignore it.
l Type the new iMana IP in the address bar of Internet Explorer. The Web management page of iMana
is displayed.
Step 10 Disconnect the iMana management interface of the server from the PC and connect the iMana
management interface to the network.
----End
3.3.1.2 Configuring the iMana IP Address Through BIOS

After an iMana IP address is set for a Huawei RH series rack server, you can remotely manage
the server in Web mode. This topic describes how to configure the iMana IP address through
BIOS.
Prerequisites
l You must ensure that the server is connected to the KVM.
l Use a network cable to connect the switch and the iMana management interface of the
server.
Procedure
Step 1 Press the power button to restart the PC server.
Step 2 When the BIOS start page appears, press Delete until the BIOS Setup Utility program is started.
NOTE
If the BIOS password has been modified, a dialog box asking you to enter a password will be displayed
during startup. Enter the required password to access the Setup Utility application.
Step 3 Configure the IP address of the integrated management module (iMana).

l On Huawei Tecal RH5885H V3 server, perform the following operations:
1. Choose Server Mgmt > BMC network configuration, and press Enter. The BMC
network configuration page is displayed.

2. Select IPv4 IP Source, and press Enter. The menu dialog box is displayed.

1. Choose Advanced > IPMI BMC Configuration, and press Enter. The IPMI BMC
Configuration page is displayed.

2. Select BMC Configuration, and press Enter. The BMC Configuration page is
displayed.
3. Select IPv4 IP Source, and press Enter. The menu dialog box is displayed.

Step 4 Select Static, and press Enter.
Step 5 Enter the planned iMana IP, subnet mask, and gateway in IPv4 IP Address, IPv4 Subnet
Mask, and IPv4 Gateway Address respectively.
Step 6 Press Enter to accomplish the IP configuration of the iMana management module.
Step 7 Press F10 and select Yes from the dialog box to save the configurations and quit the configuration
page.
----End
3.3.2 Configuring the IMM IP Address

The IMM (Integrated Management Module) is integrated with the IBM X series servers. It is
used to remotely manage the server. IP address of the IMM can be used to remotely log in to a
PC server to manage and maintain PC server in Web mode. For example, you can use this IP
address for remote OS installation, or use it to maintain the PC server if the OS fails to start
properly. Two modes of configuring the IMM IP address are available: through IMM
management interface and through BIOS.
If a server is not equipped with the KVM, the mode through IMM management interface is
recommended.
l Through IMM management interface:

– Advantage: The IBM server does not need to be equipped with a monitor, mouse, or
keyboard. Fewer operations are required, compared with the mode of using BIOS.
– Disadvantage: The Internet Explorer may shut down automatically or not respond. The
troubleshooting procedure is as follows:
1. Right-click the Internet Explorer icon on the taskbar to close the Internet Explorer.
If the Internet Explorer is still open, stop the iexplore.exe process on the
Processes tab page in the Task Manager.

2. Open the Internet Explorer.

l Through BIOS:
– Disadvantage: The IBM server must be equipped with a monitor, mouse, and keyboard.
More operations are required, compared with the mode of using the IMM management
interface.
3.3.2.1 Configuring the IMM IP Address Through IMM Management Interface

(IBM X3650 M4)
After an IMM IP address is set for an IBM X series server, you can remotely manage the server
in Web mode. This topic describes how to configure the IMM IP address through IMM
management interface.
Prerequisites
NOTE
If an IE or Video Viewer fault occurs in the IMM, see A.3.7 How to Solve IMM Problems to rectify the
fault.
Procedure
Step 1 View the position of the IMM interface on the IBM server.
The management interface SYS MGMT specific to the IMM is available at the rear of the server.
You can use the SYS MGMT interface to access the IMM.
Step 2 Use a network cable to connect the PC and the IMM management interface SYS MGMT of the
server.
address of the IMM must be in the same network segment.
NOTE
The default IP address of the IMM is 192.168.70.125 and the default subnet mask is 255.255.255.0. If the
default IP address of the IMM is changed, see A.3.4 How to View the IMM IP Address on the IBM
Server.

Step 4 Enter the default IMM IP address on the Internet Explorer of the PC to access the IMM Web
login window.
NOTE
The IMM uses HTTP by default. To ensure system security, use HTTPS. For details about how to configure
HTTPS, see A.3.15 How to Configure the HTTPS on the IMM(IBM X3650 M4).
Step 5 Enter an IMM user name and a password, and click Log In.
NOTE
l The default user name is USERID.

l The default password is PASSW0RD. Note that the sixth character is digit 0 but not letter O. If the
password has been changed, enter the new password. If the password has not been changed, for system
security, modify the default password and remember the new password. For details, see A.3.5 How to
Change the Password of the IMM User USERID(IBM X3650 M4).
Step 6 Click IMM Management > Network.
Step 7 In the dialog box, select Use static IP address from the Configure IP address settings drop-
down list, set parameters in the Static IP Address Settings.

Step 8 Click Apply.

Step 9 In the Confirm Apply dialog box, click OK.
Step 10 Click IMM Management > Restart IMM to restart the IMM. After the IMM is restarted, enter
a new IMM IP address on the Internet Explorer address bar to access the IMM management web
page.
NOTE
During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or laptop. If
the IMM IP address can be pinged through, the IMM is successfully restarted. Restarting IMM takes about
3 minutes.
Step 11 Disconnect the IMM management interface of the server from the PC and connect the IMM
----End
3.3.2.2 Configuring the IMM IP Address Through IMM Management Interface

(IBM X3850 X5 and IBM X3650 M3)
in Web mode. This topic describes how to configure the IMM IP address through IMM
management interface.
Prerequisites
NOTE
If an Internet Explorer or Video Viewer fault occurs in the IMM, see A.3.7 How to Solve IMM
Procedure
Step 1 View the position of the IMM interface on the IBM server.
The management interface SYS MGMT specific to the IMM is available at the rear of the server.
You can use the SYS MGMT interface to access the IMM. The following figure uses the IBM
X3650 M3 as an example.

Step 2 Use a network cable to connect the PC and the IMM management interface SYS MGMT of the
server.
address of the IMM must be in the same network segment.
NOTE
Server.
login window.
NOTE
The IMM uses HTTP by default. To ensure system security, use HTTPS. For details about how to configure
HTTPS, see A.3.16 How to Configure the HTTPS on the IMM(IBM X3850 X5 and IBM X3650
M3).
Step 5 Enter an IMM user name and a password, and click Login.
NOTE

Change the Password of the IMM User USERID(IBM X3850 X5 and IBM X3650 M3).
Step 6 Click Continue to access the Integrated Management Module web page.
NOTE
You do not need to set Inactive session timeout value. Keep the default value no timeout.
Step 7 Choose Network Interfaces from the navigation tree. In the right-hand pane, clear the selection
of IPv6 Enabled, select Disabled - Use static IP Configuration from the DHCP drop-down
list, set parameters in the Static IP Configuration area, and click Save.

Step 8 In the Note dialog box, click OK.
Step 9 Restart the IMM to make the changed IP address take effect. Choose Restart IMM from the
navigation tree. In the right-hand pane, click Restart to restart the IMM. After the IMM is
restarted, enter a new IMM IP address on the Internet Explorer address bar to access the IMM
management web page.

NOTE
During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or laptop. If the
IMM IP address can be pinged through, the IMM is successfully restarted. Restarting IMM takes about 3 minutes.
Step 10 Disconnect the IMM management interface of the server from the PC and connect the IMM
----End
3.3.2.3 Configuring the IMM IP Address Through BIOS

in Web mode. This topic describes how to configure the IMM IP address through BIOS.
Prerequisites
l You must ensure that the server is connected to the KVM.
l Use a network cable to connect the switch and the IMM management interface SYS MGMT
of the server. (As network interfaces on an IBM X series server are enabled with auto-
negotiation, either parallel or crossover network cables can be used.)
Procedure
Step 2 After the IBM System X dialog box is displayed, wait about 1 minute until <F1> Setup is
displayed.

Step 3 Press F1 to select Setup, and press Enter.
Step 4 Use arrow keys to select System Settings, and press Enter.
l For IBM X3650 M3 or IBM X3850 X5, show as follows:

l For IBM X3650 M4, show as follows:
Step 5 Use arrow keys to select Integrated Management Module, and press Enter.

Step 6 Use arrow keys to select Network Configuration press Enter and access the page for modifying
the IMM IP address.

Step 7 Select Static IP in DHCP Control and enter the planned IMM IP address, subnet mask, and
gateway address in IP Address, Subnet Mask, and Default Gateway.
Step 8 Optional: For IBM X3650 M3 or IBM X3850 X5, run the following steps.

1. Use arrow keys to select Save Network Settings, and press Enter. The dialog box asking
you to restart the IMM is displayed.
2. Enter Y. The IMM reset command has been sent successfully dialog box is displayed.
3. Press Enter to restart the IMM.
NOTE
During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or laptop.
If the IMM IP address can be pinged through, the IMM is successfully restarted. Restarting IMM
takes about 3 minutes.
4. Press Esc to exit Network Configuration.
5. Press Esc to exit Integrated Management Module.
6. Press Esc to exit System Settings.
7. Press Esc to exit System Configuration and Boot Management. The Do you want to
exit Setup Utility? dialog box is displayed.
8. Enter Y to exit BIOS.
Step 9 Optional: For IBM X3650 M4, run the following steps.
1. Use arrow keys to select Save Network Settings, and press Enter. The Network Settings
have been saved successfully dialog box is displayed.
2. Press Enter. Wait about 3 minutes for the changes to take effect.
NOTE
Run the ping IMM IP address -t command on the CLI of the PC or laptop. If the IMM IP address
can be pinged through, the changes take effect.
3. Press Esc to exit Network Configuration.
4. Press Esc to exit Integrated Management Module.
5. Press Esc to exit System Settings.
6. Press Esc to exit System Configuration and Boot Management. The Do you want to
exit Setup Utility? dialog box is displayed.
7. Enter Y to exit BIOS.
NOTE
This operation takes wait about 30 seconds. Wait patiently.
----End
3.3.3 Setting the SC IP Address for the OceanStor S3900 Disk Array
This topic describes how to set the SC IP address for the OceanStor S3900 disk array before
using OceanStor S3900 disk array. After the SC IP address has been set, you can use the Web
browser to remotely access and control the disk array.
Prerequisites
l The controller IP addresses are obtained.
l The power cable of the disk array is connected.

Context
The OceanStor S3900, a disk array, has two controllers. The IP addresses configured in this
section are examples only. For example, set the IP address of controller A to 192.168.128.203
and the IP address of controller B to 192.168.128.204.
Procedure
Step 1 Connect the computer and controller A of the disk array physically.
Use a serial port cable (DB9-RJ45) to connect the serial port of the local controller to the serial
port of the disk array (SERIAL MGT).
Use an RJ45 connector at one end of the serial port cable to connect to the serial port of the disk
array (SERIAL MGT) and a DB-9 connector at the other end of the cable to connect to the serial
port of the computer (COM1 or COM2).
Step 2 Set up a logical connection between the PC and disk array controller A.
1. Start the PC and log in to the Windows OS.
2. Run the PuTTY tool. In the dialog box that is displayed, choose Serial from the navigation
tree.
3. In the right-hand pane, set parameters as follows for an interface, such as COM1:
l Serial line to connect to: COM1
l Speed(baud): 115200
l Data bits: 8
l Stop bits: 1
l Parity: None
l Flow Control: None
4. Choose Session from the navigation tree. In the right-hand pane, set Connection type to
Serial and use the default values for other parameters.
5. Click Open.
The following message will be displayed on the Windows management terminal if the
connection was established:

Storage login:
6. Enter the user name and password to log in.

NOTE
The default user name and password of the system administrator are admin and Admin@storage. To
ensure system security, log in to the ISM to change the password periodically. To ensure the security of
the U2000, passwords must be complex enough. For example, a password must contain eight or more
characters of two types. The allowed characters are digits, letters, and special characters. Remember to
change passwords regularly.
After login authentication, the system will display the CLI.

7. Run the following command to change the default password:
admin:/>chguserpwd
Old password:
New password:
Re-enter new password:
NOTE
Change the password as prompted. For example, change the password to Changeme_123. To ensure
the security of the U2000, passwords must be complex enough. For example, a password must contain
eight or more characters of two types. The allowed characters are digits, letters, and special characters.
Remember to change passwords regularly.
Step 3 In the CLI, run the chgctrlip command to configure the IP address for the network interface of
controller A. See Table 3-10.
Table 3-10 Command format and parameter description of the chgctrlip command
Command Format Parameter Description
chgctrlip -c controller ID { -ip IP l -c controller ID: Indicates the controller ID.

address | -mask subnet mask | -gw The value of this parameter is a or b, where,
gateway } a represents controller A and b represents
controller B.
l -ip IP address: Indicates the IP address of the
management network interface of the
controller.
l -mask subnet mask: Indicates the subnet
mask.
l -gw gateway: Indicates the gateway.

The following is an example:
Configure the IP address for the management network interface of controller A. Specifically,
the IP address is 192.168.128.203, the subnet mask is 255.255.255.0, and the gateway IP address
is 192.168.128.1. Run the following command:
admin:/>chgctrlip -c a -ip 192.168.128.203 -mask 255.255.255.0 -gw 192.168.128.1
Step 4 Disconnect the serial port from controller A.

1. In the CLI, run the logout command.
2. On the computer, exit the PuTTY software.
3. Remove the serial port cable on the disk array.
Step 5 Repeat Step 1 to Step 4 to configure the network interface of controller B.

1. Connect the computer and controller B physically.
2. Establish a logical connection between the computer and controller B.
3. Configure the IP address of the network interface of controller B on the local console.
Configure the IP address for the management network interface of controller B.

Specifically, the IP address is 192.168.128.204, the subnet mask is 255.255.255.0, and the
gateway IP address is 192.168.128.1. Run the following command:
admin:/>chgctrlip -c b -ip 192.168.128.204 -mask 255.255.255.0 -gw
192.168.128.1
NOTE
Run the showctrlip command to query the IP address of the management network interface of a controller
after the chgctrlip command.
The following is an example for querying the IP addresses of the management network interfaces of all
controllers:
admin:/>showctrlip
Controller IP Address Subnet Mask Gateway MAC Address
A 192.168.128.203 255.255.255.0 192.168.128.1
00:12:34:56:70:46
B 192.168.128.204 255.255.255.0 192.168.128.1
00:12:34:56:79:92
Step 6 Disconnect the serial port from controller B.

1. In the CLI, run the logout command.
2. On the computer, exit the PuTTY software.
3. Remove the serial port cable on the disk array.
----End
3.4 Configuring RAID

RAID needs to be configured before an operating system is installed in order to improve the
efficiency and security of using server hard disks.
RAID is a technology used to combine multiple independent physical hard disks in various
modes to form logical hard disk groups. A logical hard disk group provides storage capacity
greater than that of a single hard disk and allows implementation of data redundancy protection.

3.4.1 Configuring the RAID in Remote Mode (Huawei RH series

rack server, ISO)
The RAID needs to be configured before an operating system is installed in order to improve
the efficiency and security of using server hard disks.
Prerequisites
l The IP address of the iMana is available. For details about how to set the IP address of the
iMana, see 3.3.1.1 Configuring the iMana IP Address Through iMana Management
Interface.
l ISO image file of the quick RAID configuration DVD
Sles_server_raid_x64_for_Huawei_dvd.iso must be ready.
l Ensure that eight hard disks of the server are available. Otherwise, RAID configuration
fails. If a disk array is available, ensure that two hard disks of the server are available. For
details, see A.2.7 Viewing Hard Disk Information (Huawei RH series rack server).
Context
RAID is a technology used to combine multiple independent physical hard disks in various
modes to form logical hard disk groups. A logical hard disk group provides storage capacity
greater than that of a single hard disk and allows implementation of data redundancy protection.
The standard Huawei RH series rack server for delivery is equipped with eight hard disks. The
RAID level planning is as follows:
l The first and second hard disks need to be configured with RAID 1 and are used to install
OS data. Only the first hard disk needs to be partitioned and the second hard disk functions
as the mirroring disk. Table G-1 shows the partitioning details.
l The third, fourth, fifth, and sixth hard disks need to be configured with RAID 10 and are
used to store service data and software. The third and fourth hard disks are used for
partitioning and the fifth and sixth hard disks function as mirroring disks for the third and
fourth hard disks. Table G-2 shows the partitioning details.
l The seventh hard disk need to be configured with RAID 0 and is used to create a SRL
(Storage Replicator Log) volume. Table G-2 shows the partitioning details.
l The eighth hard disk is used to perform hot backup for the previous seven hard disks. Table
G-2 shows the partitioning details.
Configure two hard disks for the Huawei Tecal RH5885H V3 server with standard delivery
configurations. Configure 12 hard disks for the OceanStor S3900 disk array. The RAID and
partition planning is as follows:
l Configure the two hard disks on the IBM server as RAID 1. Install the OS software and
U2000 project-related software and configure OS data.
l Configure the first 10 hard disks of the OceanStor S3900 disk array as RAID 10. The first
10 hard disks are used to store database software, database data, U2000 software, and

backup data. The remaining two hard disks are used for global hot backup for the first 10
hard disks.
NOTE
l Using an ISO image file of the quick RAID configuration DVD to configure a RAID is recommended
because it improves the configuration efficiency and reduces misoperations.
l If an Internet Explorer, two pointers, or Remote Virtual Console fault occurs in the iMana, see A.2.4
How to Solve iMana Problems.
l The procedure for configuring RAID for the server with eight hard disks is the similar to that for the
server with two hard disks. The only difference is the command output. The following uses a server
with eight hard disks as an example.
Procedure
Step 1 Optional: If OS has been installed on the server, manually format disks; otherwise, OS
installation will fail because the old data is not clear. For details, see A.2.6 Formatting disks
(Huawei RH series rack server).
Step 2 Save the ISO mirroring file to any directory on the PC or laptop.
Step 3 Log in to the server. For details, see A.2.1 How Do I Use iMana IP to Log In to a Remote
Step 4 Click on the toolbar which is right above Remote Virtual Console.
Step 5 In the virtual disk dialog box, select Image File and click Browse.
Step 6 In the Open dialog box, select the ISO file of the quick RAID configuration DVD
Sles_server_raid_x64_for_Huawei_dvd.iso and click Open.
Step 7 In the virtual disk dialog box, click Connect. If Connect is displayed as Disconnect, the virtual
disk is connected to the server.
Step 8 Click on the toolbar which is right above Remote Virtual Console and select Gold
Reset.
Step 9 In the dialog box that is displayed, click Yes to restart the server.
Step 10 Configure the server to start from the drive.

1. After the server is started, press F11.
2. Select P5: TSSTcorp CDDVDW SN-208DB to start from the drive and press Enter.
1. After the server is started, press F11 to access the Boot Manager window.

2. Select HUAWEI DVD-ROM VM 1.1.0 to start from the virtual drive and press
Enter.
Step 11 Select Tecal RAID Config Tool and press Enter.
Step 12 Wait about 5 minutes. The RAID configuration is completed, as shown in the following figure.
Step 13 Press Enter. The system will automatically restart.
Step 14 Click on the toolbar which is right above Remote Virtual Console. Click Eject.
NOTICE
If you don't click Eject, it will configure the RAID repeatedly.
Step 15 Check whether RAID configurations are correct.

1. After the basic input/output system (BIOS) check is completed, the BIOS information about
the RAID is displayed, as shown in the following figure.
NOTE
This screen stays for a short period of time. Press Ctrl+H the moment you see Ctrl+H on the screen.
If Ctrl+H is not pressed, restart the system.

2. Press Ctrl+H as prompted to access the Adapter Selection window.

l On Huawei Tecal RH2288H V2 server, the following window is displayed.
3. Click Start to access the WebBIOS window of the RAID card.
If the WebBIOS window displays information as shown in the following figure, the RAID
configurations are correct. Otherwise, configure the RAID card again.

Step 16 Click Exit to exit the WebBIOS window. The Exit Application dialog box is displayed.
Step 17 Click Yes, A dialog box is displayed.
Step 18 Restart the server.
1. Click on the toolbar which is right above Remote Virtual Console and select Gold
Reset.
2. In the dialog box that is displayed, click Yes to restart the server.
----End
3.4.2 Configuring RAID in Remote Mode (IBM X3650 M4, ISO)

This topic describes how to configure the RAID of IBM X3650 M4 in remote mode.
Prerequisites
l The IP address of the IMM is available. For details about how to set the IP address of the
IMM, see 3.3.2.1 Configuring the IMM IP Address Through IMM Management
Interface(IBM X3650 M4).
l ISO mirroring file of the quick RAID configuration DVD
Sles_server_raid_x64_for_IBM_dvd.iso must be ready.

fails. For details, see A.3.10 Viewing Hard Disk Informationin Remote Mode (IBM
X3650 M4).
Context
A standard IBM server to be delivered must be equipped with eight hard disks. The planning
for RAID levels and partitions is as follows:
NOTICE
l Open one Video Viewer window on a PC or laptop. Open the Video Viewer window on a
PC or laptop for each server when you operate multiple servers. Otherwise, the failure to
open multiple Video Viewer windows on a PC or laptop or the failure that the Video
Viewer window does not respond may occur.
l If an Internet Explorer or Video Viewer fault occurs in the IMM, see A.3.7 How to Solve
IMM Problems to rectify the fault.
NOTE
Using ISO mirroring file of the quick RAID configuration DVD to configure a RAID is recommended
because it improves the configuration efficiency and reduces misoperations.
Procedure
Step 1 Optional: If Windows OS has been installed on the server, manually format disks; otherwise,
OS installation will fail because disks are protection. For details, see A.3.13 Formatting the
disks in Remote Mode (IBM X3650 M4).
Step 2 Save the ISO mirroring file to any directory on the PC or laptop.
Step 3 Open the Internet Explorer and enter the IMM IP address of the IMM in the address bar to access
the page for logging into the IMM.
NOTE
Server.

NOTE

Step 5 Click Remote Control, select Use the ActiveX Client > Start remote control in single-user
mode to access the remote control desktop.

NOTE
l When logging in to the IBM server for the first time, perform the following operations:
1. Click Start remote control in single-user mode and wait about 2 minutes. In the dialog box asking
you whether to install the IMM_KVMVM32.cab, click Install.
2. During the installation, click Run in the Warning-Security dialog box asking you whether to trust
this site.
l Do not close the ActiveX KVM Client dialog box. Otherwise, the Video Viewer dialog box cannot
be displayed.
l If the remote control desktop appears and then disappears immediately, see A.3.1 How to Solve the
Problem Where the Remote Control Desktop Appears and Then Disappears Immediately to solve
the problem.
l If Use the ActiveX Client is unavailable, just click Start remote control in single-user mode to
access the remote control desktop.
l Keep the default values of other parameters unchanged.
l For the IBM X3650 M4 server, if CAPS is displayed in the lower right corner of the Video Viewer
window, letters are entered in upper case; if CAPS is not displayed in the lower right corner of the
Video Viewer window, letters are entered in lower case. The Caps indicator on the keyboard cannot
indicate whether letters are entered in upper or lower case.
l For the IBM X3650 M4 server, if NUM is displayed in the lower right corner of the Video Viewer
window, digits can be entered; if NUM is not displayed in the lower right corner of the Video
Viewer window, digits cannot be entered. The Num indicator on the keyboard cannot indicate whether
the number keypad is available.
Step 6 The desktop window Video Viewer is displayed, choose Tools > Launch Virtual Media from
the main menu. The virtual media window is displayed.
Step 7 Load the installation DVD-ROM or ISO mirroring file.
If the ISO mirroring file of the quick RAID configuration DVD-ROM is used, click Add
Image to add the RAID DVD-ROM and select Map.

NOTICE
l Do not close the window Virtual Media Session until the RAID is configured.
l Do not close the desktop display window Video Viewer until all operations in the chapter
are completed. You can operate the server using the desktop display window Video
Viewer.
Step 8 Click Mount Selected to mount the ISO mirroring file of the quick RAID to the IMM. If Mount
Selected changes into Unmount All indicating that the mount is complete.
Step 9 Choose Tools > Power > Reboot from the main menu to reboot the system.
NOTE
l If a message asking you whether to continue is displayed, click Yes.

l If Reboot is unavailable, choose Tools > Power > On and then choose Tools > Power > Reboot to
restart the system.
Step 10 After the IBM System X window is displayed, wait for about 2 minutes until <F12> Select
Boot Device is displayed.

Step 11 Press F12 to choose Select Boot Device. If you miss the F12, choose Tools > Power >
Reboot from the main menu and click Yes in the dialog box that is displayed to reboot the IBM
server.
Step 12 Use arrow keys to select CD/DVD and press Enter to start the system from the DVD-ROM.
Step 13 Wait about 5 minutes. The window for automatic RAID configuration stops, as shown in the
following figure.
NOTE
The RAID solution is configured using the integrated Windows PE. Therefore, a message indicating
Windows loading is displayed during the configuration process. The Windows loading process has no
impact on the use of RAID.


NOTE
When the system is restarting, in the Virtual Media Session window, if the Map for the ISO mirroring
file of the quick RAID configuration DVD-ROM is still selected, clear the selection of Map. And click
Exit to close the virtual media window.

NOTE

NOTE
Two pointers will be displayed. You can choose Tools > Single Cursor from the main menu to
change to the single pointer mode. Select the pointer mode according to individual operation habits.
To quit single pointer mode, press F12.

----End
3.4.3 Configuring RAID in Remote Mode (IBM X3850 X5 and IBM

X3650 M3, ISO)
This topic describes how to configure the RAID of IBM X3850 X5 and IBM X3650 M3 in
remote mode.
Prerequisites
Interface (IBM X3850 X5 and IBM X3650 M3).
l ISO mirroring file of the quick RAID configuration DVD
Sles_server_raid_x64_for_IBM_dvd.iso must be ready .
fails. If a disk array is available, ensure that two hard disks of the server are available. For
details, see A.3.11 Viewing Hard Disk Informationin Remote Mode (IBM X3850 X5
and IBM X3650 M3).

Context
A standard IBM server to be delivered must be equipped with eight hard disks. The planning
for RAID levels and partitions is as follows:
Configure two hard disks for the IBM server (X3850 X5) with standard delivery configurations.
Configure 12 hard disks for the OceanStor S3900 disk array. The RAID and partition planning
is as follows:
hard disks.
Configure two hard disks for the IBM server and Huawei RH series rack server with standard
delivery configurations. Configure 12 hard disks for the OceanStor S3900 disk array. The RAID
and partition planning is as follows:
hard disks.
NOTICE
l If only two hard disks are available, you must place the two hard disks in slot 0 and slot 1.
Otherwise, RAID fails to be configured.
l Open one Video Viewer window on a PC or laptop. Open the Video Viewer window on a
PC or laptop for each server when you operate multiple servers. Otherwise, the failure to
open multiple Video Viewer windows on a PC or laptop or the failure that the Video
Viewer window does not respond may occur.
l If an Internet Explorer or Video Viewer fault occurs in the IMM, see A.3.7 How to Solve
IMM Problems to rectify the fault.

NOTE
Using ISO mirroring file of the quick RAID to configure a RAID is recommended because it improves the
configuration efficiency and reduces misoperations.
The procedure for configuring RAID for the server with eight hard disks is the similar to that for the server
with two hard disks. The only difference is the command output. The following uses a server with eight
hard disks as an example.
Procedure
Step 1 Optional: If Windows OS has been installed on the server, manually format disks; otherwise,
OS installation will fail because disks are protection. For details, see A.3.14 Formatting the
disks in Remote Mode (IBM X3850 X5 and IBM X3650 M3).
Step 2 Sve the ISO mirroring file to any directory on the PC or laptop.
NOTE
Server.
NOTE

NOTE
Step 6 Enable remote control. Choose Tasks > Remote Control from the navigation tree. In the right-
hand pane, click Use the ActiveX Client with Microsoft Internet Explorer > Start Remote
Control in Single User Mode to access the remote control desktop.
The remote control desktop consists of two parts: virtual media window and desktop display
window.

NOTE
this site.
the problem.
l If Use the ActiveX Client with Microsoft Internet Explorer is unavailable, just click Start Remote
be displayed.
Step 8 Load ISO mirroring file of the quick RAID configuration DVD-ROM.
If the ISO mirroring file of the quick RAID configuration DVD-ROM is used, click Add
Image to add the RAID DVD-ROM and select Map.

NOTICE
l Do not close the window Virtual Media Session until the RAID is configured.
are completed. You can operate the server using the desktop display window Video
Viewer.
Step 9 Click Mount Selected to mount the ISO mirroring file of the quick RAID configuration DVD-
ROM to the IMM.
NOTE

restart the system.

server.
Step 13 Use arrow keys to select CD/DVD Rom and press Enter to start the system from the DVD-
ROM.
Step 14 Wait about 5 minutes. The window for automatic RAID configuration stops, as shown in the
following figure.
NOTE
The RAID solution is configured using the integrated Windows PE. Therefore, a message indicating
Windows loading is displayed during the configuration process. The Windows loading process has no
impact on the use of RAID.


NOTE
When the system is restarting, in the Virtual Media Session window, if the Map for the ISO mirroring
file of the quick RAID configuration DVD-ROM is still selected, clear the selection of Map. And click
Exit to close the virtual media window.

NOTE

NOTE


----End
3.5 Installing the SUSE Linux OS by Using the Quick

Installation CD-ROM
This topic describes how to use a quick installation DVD-ROM delivered with Huawei devices
to install the SUSE Linux OS.
NOTE
The installation DVD-ROM delivered with the SUSE Linux OS is used to install the SUSE Linux OS is
unavailable.
A quick installation DVD-ROM can be used to install the OS and patches. During installation,
you do not need to manually partition hard disks, reducing the probability of misoperation and
improves the installation efficiency. Using a quick installation DVD-ROM to install the SUSE
Linux OS is recommended.
You can use a quick installation DVD-ROM to install the OS on the IBM X series servers or
Huawei RH series rack servers in two modes: remote and local. If a server is not configured with
the KVM, using the remote mode is recommended.
l Remote SUSE Linux installation:
– Advantage: The server does not need to be equipped with a monitor, mouse, or keyboard.
Remote operation on the server is allowed.
– Disadvantage: Some faults may occur. For example, the Internet Explorer does not
respond, the Internet Explorer, Video Viewer or Remote Virtual Console icon on the

taskbar does not respond, the Internet Explorer closes automatically, the user cannot
open the Video Viewer or Remote Virtual Console window after a user closes the
Internet Explorer and Video Viewer or Remote Virtual Console windows, the case of
letters reversal, and so on.
When the Video Viewer or Remote Virtual Console window is closed, the original
session is still there.
If an Internet Explorer or Video Viewer fault occurs in the IMM, see A.3.7 How to
Solve IMM Problems to rectify the fault.
If an Internet Explorer, two pointers, or Remote Virtual Console fault occurs in the
iMana, see A.2.4 How to Solve iMana Problems.
l Local SUSE Linux installation:
– Disadvantage: The server must be equipped with a monitor, mouse, and keyboard. Only
local operation on the server is allowed.
3.5.1 Remotely Installing the SUSE Linux Operating System

(Huawei RH series rack server, DVD/ISO)
If the Huawei RH series rack server is not configured with the KVM, use the iMana IP address
to remotely install the server operating system. This topic describes how to remotely install the
SUSE Linux operating system.
Prerequisites
l The IP address of the iMana is available. For details about how to set the IP address of the
iMana, see 3.3.1.1 Configuring the iMana IP Address Through iMana Management
Interface.
l Choose Tool > Internet options. Click Connections tab, you must clear settings for the
proxy server before logging in to the browser.
l Quick OS installation DVD U2000version_server_os_sles_x64_dvd1 or ISO image file of
the quick installation DVD U2000version_server_os_sles_x64_dvd1.iso。
l The system IP addresses including the IP address, subnet mask, and gateway must have
been planned.
Context
NOTE
If an Internet Explorer, two pointers, or Remote Virtual Console fault occurs in the iMana, see A.2.4 How
to Solve iMana Problems.
Procedure
Step 1 Insert the quick installation DVD-ROM to the drive on a PC or laptop. If an ISO mirroring file
is used to install the operating system, save the ISO mirroring file to any directory on the PC or
laptop.

Step 2 Log in to the server. For details, see A.2.1 How Do I Use iMana IP to Log In to a Remote
Step 3 Click on the toolbar which is right above Remote Virtual Console.
Step 4 Load the installation DVD or ISO file.

l If the installation DVD is used, select CD/DVD in the virtual disk dialog box, select the drive
letter of the installation DVD from the drop-down list on the right, and click Connect. If
Connect changes to Disconnect, the virtual drive has successfully connected to the server.
l If the ISO file is used, perform the following operations:
1. In the virtual disk dialog box, select Image File and click Browse.
2. In the Open dialog box, select the ISO file of the quick RAID configuration DVD
U2000version_server_os_sles_x64_dvd1.iso and click Open.
3. In the virtual disk dialog box, click Connect. If Connect is displayed as Disconnect,
the virtual disk is connected to the server.
Step 5 Click on the toolbar which is right above Remote Virtual Console and select Gold
Reset.
Step 6 In the dialog box that is displayed, click Yes to restart the server.

1. After the server is started, press F11 to access the Please select boot device: window.

2. Select HUAWEI DVD-ROM VM 1.1.0 to start from the virtual drive and press
Enter.
Step 8 Wait about two minutes, the system restarts and the SUSE Linux Enterprise Server window
is displayed.
NOTE
Do not perform any operation before the SUSE Linux Enterprise Server page is displayed.
Step 9 Use the up or down arrow key to select Installation--Local HA System and press Enter to
begin to load the Linux core. The system starts the automatic installation of the OS. The
installation of the SUSE Linux kernel is completed until the operating system login window is
displayed. The entire OS installation process lasts approximately 40 minutes.

NOTE
l The installation process and remaining time are displayed in the installation window.
l During installation of the SUSE Linux kernel, do not manually perform any operation until the OS login
window is displayed.
l During installation of the SUSE Linux kernel, the OS automatically restarts. If the Boot from Hard Disk
screen stays for more than 2 minutes, press Enter to go to next window. And press Enter again to continue
automatic restart until the OS login window is displayed.
l If the following window is displayed during OS installation, the sdc hard disk has not been formatted, which
does not affect installation. Click OK directly until the OS login window is displayed.
Step 10 Click on the toolbar which is right above Remote Virtual Console. Click Eject.
Step 11 Log in to the GUI of the OS as the root user.
The default OS user name is root and the default password is Changeme_123. For system
security, modify the default password and remember the new password. For details, see A.6.14
How to Change the OS User Password.
NOTE
l Do not use the integrated number pad keyboards. This is because Num Lock may fail to work when
a SUSE Linux OS is installed on certain machines.
l By default, the system enables the root user to perform remote login and use the SFTP tool.
l If you can log in to the SUSE Linux OS as the root user and the OS version and kernel version are
correct, it indicates that the SUSE Linux OS is successfully installed. Otherwise, install the OS again.
l On the desktop, right-click in the blank area and choose Open Terminal from the shortcut menu
to access the CLI.
If the following information is displayed, the SUSE Linux version is correct:
VERSION = 10
PATCHLEVEL = 4
# uname -rv
The information similar to 2.6.16.60-0.103.1 is displayed. Here, 2.6.16.60-0.103.1 indicates the
kernel version of the OS.
If the kernel version is 2.6.16.60-0.103.1, the kernel version is correct.
Step 12 Set the network of the system.

1. Run the following command to log in to the YaST Control Center:

# yast2
2. In the YaST Control Center dialog box, choose Network Devices > Network Card.
3. In the Network Setup Method dialog box, select Traditional Method with ifup and click
Next.
4. In the Network Card Configuration Overview dialog box, select the first Broadcom and
click Edit.
NOTE
If bond has been configured for multiple network interfaces, only one MAC address is displayed for
these network interfaces. For example, if the server has four network interfaces and bond has not
been configured for them, four MAC addresses will be displayed. If bond has been configured for
two network interfaces, three MAC addresses will be displayed.
5. In the Network Address Setup dialog box, select Static Address Setup and set system
IP address and subnet mask.
6. Add a static route.
NOTE
A route must be added if a user needs to connect to the network. A static route is recommended.
l If network connection security is highly required, add a static route and allow users on some IP
network segments to connect to the server.
l If network connection security is not highly required, add a default route and allow all users to
connect to the server. For details, see A.1.3 How to manually Add the Default Route (SUSE
Linux).
a. Click Routing.
b. In the Routing Configuration window, select Expert Configuration in the Routing
Table area.
c. Click Add. The following dialog box for configuring a static route is displayed.

NOTE
Set the following parameters:
l Destination: An IP address on the network segment of the computer connected to the
U2000 server.
l Gateway: network management IP address for the network on which the U2000 server is
located.
l Netmask: subnet mask of the network segment on which the computer connected to the
U2000 server is located.
l Device: use the default value. The eth is at the beginning of default values.
Leave other parameters empty.
d. Click OK.
e. Click OK.
7. In the Network Address Setup dialog box, click Next return to the Network Card
Configuration Overview dialog box.
8. In the Network Card Configuration Overview dialog box, click Finish to complete the
setting of the IP address.
9. Close the YaST Control Center dialog box.
NOTE
l After the system IP addresses and the routes are set, run the netstat -nr command through the CLI to
check whether the route is successfully added. Wait for about 1 to 2 minutes, then run the ping system
IP address command to check whether the network of the system is set. If the system IP address can
be pinged, the network of the system is successfully set.
l If a static route exists and a new static route needs to be added, use the MSuite to add a static route
after the U2000 is installed, see A.1.5 How to Add a Static Route If the U2000 Is Installed. Using
yast2 to add a static route is prohibited to prevent several-second network disconnection and service
interruption.
Step 13 Run the following command to restart the OS. It takes approximately 5 to 8 minutes to restart
the system.
# sync;sync;sync;sync
# shutdown -r now
----End
Follow-up Procedure
If a host name needs to be changed, enter the new host name during system preconfiguration.
3.5.2 Remotely Installing the SUSE Linux Operating System (IBM

X3650 M4, DVD/ISO)
If the IBM server is not configured with the KVM, use the IMM IP address to remotely install
the server operating system. This topic describes how to remotely install the SUSE Linux
operating system.
Prerequisites
Interface(IBM X3650 M4).


the quick installation DVD U2000version_server_os_sles_x64_dvd1.iso must be ready.
been planned.
Context
NOTICE
Open one Video Viewer window on a PC or laptop. Open the Video Viewer window on a PC
or laptop for each server when you operate multiple servers. Otherwise, the failure to open
multiple Video Viewer windows on a PC or laptop or the failure that the Video Viewer window
does not respond may occur.
Procedure
laptop.
NOTE
l You must clear settings for the proxy server before logging in to the browser.
l The default IP address of the IMM is 192.168.70.125 and the default subnet mask is 255.255.255.0. If
the default IP address of the IMM is changed, see A.3.4 How to View the IMM IP Address on the
IBM Server.
NOTE



NOTE
this site.
be displayed.
the problem.
Step 6 Perform the following operation according to the method used:

l If a burnt quick installation DVD-ROM is used, select Map on the line where G: CD/
DVD is located.

l If the ISO mirroring file of the quick installation DVD-ROM is used, click Add Image to
add the SUSE Linux operating system DVD-ROM and select Map.
NOTICE
l Do not close the virtual media window Virtual Media Session until the SUSE Linux OS is
installed. If Map is not selected, or the virtual media window Virtual Media Session is
closed, the installation fails and the message An error occurred during the installation is
displayed.
are completed. You can operate the server using the desktop display window.
Step 7 Click Mount Selected to mount the SUSE Linux operating system DVD-ROM file to the IMM.
Step 8 Choose Tools > Power > Reboot from the main menu to reboot the IBM server.
NOTE

restart the system.
Step 9 After the IBM System X window is displayed, wait for about 2 minute until <F12> Select Boot
Device is displayed.

Step 10 Press F12 to choose Select Boot Device dialog box. If you miss the F12, choose Tools >
Power > Reboot from the main menu and click Yes in the dialog box that is displayed to reboot
the IBM server.
is displayed.
NOTE

NOTE
l If the operation fails to be performed using the up and down arrow keys, choose Macros > Soft Key >
Down, select Installation--Local HA System in the Video Viewer window. If Down is unavailable for
Soft Key, choose Add > New and press the down arrow key to add Down for Soft Key. Click OK.

Step 14 In the Virtual Media Session window, if the Map for the disk is still selected, clear the selection
of Map. And click Exit to close the virtual media window. If unmap is prompted, click Yes. If
the burnt quick installation DVD-ROM is used, remove the DVD-ROM from the drive on the
PC or laptop.
NOTE
l Two pointers will be displayed. You can choose Tools > Single Cursor from the main menu to change
to the single pointer mode. Select the pointer mode according to individual operation habits. To quit
single pointer mode, press F12.
l When the Video Viewer window is used, contents outside the Video Viewer window cannot be copied
and pasted into the Video Viewer window.
to access the CLI.
VERSION = 10
PATCHLEVEL = 4
# uname -rv

# yast2
Next.
4. In the Network Card Configuration Overview dialog box, select the first Intel Ethernet
controller and click Edit.

NOTE
l The preceding figure is a snapshot for the IBM X3650 M4. The IBM X3650 M4 has eight
Intel interfaces, that is, eight network interfaces. Select the first interface, and connect network
interfaces identified as 1 to the network.
l If bond has been configured for multiple network interfaces, only one MAC address is displayed
for these network interfaces. For example, if the server has four network interfaces and bond has
not been configured for them, four MAC addresses will be displayed. If bond has been configured
for two network interfaces, three MAC addresses will be displayed.
NOTE
Linux).
a. Click Routing.
Table area.
NOTE
U2000 server.
located.
d. Click OK.
e. Click OK.

NOTE
interruption.
the system.
# shutdown -r now
----End
Follow-up Procedure
3.5.3 Remotely Installing the SUSE Linux Operating System (IBM

X3850 X5 and IBM X3650 M3, DVD/ISO)
If the IBM server is not configured with the KVM, use the IMM IP address to remotely install
the server operating system. This topic describes how to remotely install the SUSE Linux
operating system.
Prerequisites
Interface (IBM X3850 X5 and IBM X3650 M3).
l Choose Tool > Internet options. Click Connections tab, you must clear settings for the
proxy server before logging in to the browser.
the quick installation DVD U2000version_server_os_sles_x64_dvd1.iso must be ready.
been planned.

Context
NOTICE
Open one Video Viewer window on a PC or laptop. Open the Video Viewer window on a PC
or laptop for each server when you operate multiple servers. Otherwise, the failure to open
multiple Video Viewer windows on a PC or laptop or the failure that the Video Viewer window
does not respond may occur.
Procedure
laptop.
NOTE
Server.
NOTE

NOTE
window.

NOTE
this site.
the problem.
be displayed.

Step 7 Load the installation DVD-ROM or ISO mirroring file.

l If a burnt quick installation DVD-ROM is used, select Map on the line where G: CD/
DVD is located.
l If the ISO mirroring file of the quick installation DVD-ROM is used, click Add Image to
add the SUSE Linux operating system DVD-ROM and select Map.
NOTICE
l Do not close the virtual media window Virtual Media Session until the SUSE Linux OS is
installed. If Map is not selected, or the virtual media window Virtual Media Session is
closed, the installation fails and the message An error occurred during the installation is
displayed.
are completed. You can operate the server using the desktop display window.
Step 8 Click Mount Selected to mount the SUSE Linux operating system DVD-ROM file to the IMM.

NOTE

restart the system.
server.
Step 12 Use arrow keys to select CD/DVD Rom and press Enter to start the system from the DVD-
ROM.

is displayed.
NOTE

NOTE
l If the operation fails to be performed using the up and down arrow keys, choose Macros > Soft Key >
Down, select Installation--Local HA System in the Video Viewer window. If Down is unavailable for
Soft Key, choose Add > New and press the down arrow key to add Down for Soft Key. Click OK.
Step 15 In the Virtual Media Session window, if the Map for the disk is still selected, clear the selection
of Map. And click Exit to close the virtual media window. If the burnt quick installation DVD-
ROM is used, remove the DVD-ROM from the drive on the PC or laptop.

NOTE
l Two pointers will be displayed. You can choose Tools > Single Cursor from the main menu to change
to the single pointer mode. Select the pointer mode according to individual operation habits. To quit
single pointer mode, press F12.
l When the Video Viewer window is used, contents outside the Video Viewer window cannot be copied
and pasted into the Video Viewer window.
to access the CLI.
VERSION = 10
PATCHLEVEL = 4
# uname -rv

# yast2
Next.
4. In the Network Card Configuration Overview dialog box, select the first Broadcom and
click Edit.

NOTE
l The preceding figure is a snapshot for the IBM X3650 M3. The IBM X3650 M3 has four
Broadcom interfaces and four Intel interfaces, that is, eight network interfaces. Select the first
Broadcom, and connect network interfaces identified as 1 to the network.
l The IBM X3850 X5 has two Broadcom interfaces and six Intel interfaces. Select the first
Broadcom interface, and connect network interfaces identified as 1 to the network.
NOTE
Linux).
a. Click Routing.
Table area.
NOTE
U2000 server.
located.
d. Click OK.

e. Click OK.
NOTE
interruption.
the system.
# shutdown -r now
----End
Follow-up Procedure
3.5.4 Locally Installing the SUSE Linux Operating System (IBM

Server, DVD)
If the IMB server is configured with the KVM, install the SUSE Linux operating system in local
mode.
Prerequisites
l Ensure that the server is connected to the KVM.
l Ensure that server driver is available and can read CDs and DVDs properly.
l U2000version_server_os_sles_x64_dvd1 must be ready.
been planned.
Context
NOTE
unavailable. A quick installation DVD-ROM can be used to install the OS and patches. During installation,
you do not need to manually partition hard disks, reducing the probability of misoperation and improves
the installation efficiency. Using a quick installation DVD-ROM to install the SUSE Linux OS is
recommended.

Procedure
Step 1 Insert the operating system DVD-ROM to the IBM server drive.
server.
l For IBM X3850 X5 or IBM X3650 M3, see the following figure:
l For IBM X3650 M4, see the following figure:

is displayed.
NOTE

NOTE
l Do not manually perform any operation during installation of the SUSE Linux kernel.
l After the SUSE Linux kernel is installed, the OS automatically restarts. If the Boot from Hard Disk
screen stays for more than 2 minutes, press Enter to go to next window. And press Enter again to
continue automatic restart until the OS login window is displayed.
l If the following window is displayed during OS installation, the sdc hard disk has not been formatted,
which does not affect installation. Click OK directly until the OS login window is displayed.
Step 8 Log in to the OS as the root user.

NOTE
to access the CLI.
VERSION = 10
PATCHLEVEL = 4
# uname -rv
Step 9 Run the following command to remove the operating system DVD-ROM:
# eject
NOTE
If the DVD cannot be ejected after the eject command is executed, you must add the drive mounting position
next to the command, You can run the df -h command to query the drive mounting position.
# df -h
...
/dev/dsk/c3t7d0/linux
2.8G 2.8G 0k 100% /cdrom/linux
The drive mounting position is linux. Run the eject linux command to eject the DVD.


# yast2
Next.
4. In the Network Card Configuration Overview dialog box, select the first network
interfaces and click Edit.
NOTE
l The preceding figure is a snapshot for the IBM X3650 M3. The IBM X3650 M3 has four
Broadcom interfaces and four Intel interfaces, that is, eight network interfaces. Select the first
Broadcom, and connect network interfaces identified as 1 to the network.
l The IBM X3850 X5 has two Broadcom interfaces and six Intel interfaces. Select the first
Broadcom interface, and connect network interfaces identified as 1 to the network.
l The IBM X3650 M4 has eight Intel interfaces. Select the first interface, and connect network
interfaces identified as 1 to the network.
NOTE
Linux).
a. Click Routing.
Table area.

NOTE
U2000 server.
located.
d. Click OK.
e. Click OK.
NOTE
l After the system IP addresses and the routes are set, wait for about 1 to 2 minutes, then run the ping
system IP address command to check whether the network of the system is set. If the system IP address
can be pinged, the network of the system is successfully set.
after the U2000 is installed, See A.1.5 How to Add a Static Route If the U2000 Is Installed. Using
interruption.
the system.
# shutdown -r now
----End
Follow-up Procedure

3.5.5 Locally Installing the SUSE Linux Operating System (Huawei

RH series rack server, DVD)
If the IMB server is configured with the KVM, install the SUSE Linux operating system in local
mode.
Prerequisites
l Ensure that the server is connected to the KVM.
l Ensure that server driver is available and can read CDs and DVDs properly.
l U2000version_server_os_sles_x64_dvd1 must be ready.
been planned.
Context
NOTE
unavailable. A quick installation DVD-ROM can be used to install the OS and patches. During installation,
you do not need to manually partition hard disks, reducing the probability of misoperation and improves
the installation efficiency. Using a quick installation DVD-ROM to install the SUSE Linux OS is
recommended.
Procedure
Step 1 Insert the operating system DVD-ROM to the Huawei RH series rack server drive.

1. After the server is started, press F11 to access the Please select boot device: window.

2. Select SATA P5 TSSTcorp CDDVDW SN-208DB to start from the virtual drive and
press Enter.
is displayed.
NOTE
NOTE
l Do not manually perform any operation during installation of the SUSE Linux kernel.
l After the SUSE Linux kernel is installed, the OS automatically restarts. If the Boot from Hard Disk
screen stays for more than 2 minutes, press Enter to go to next window. And press Enter again to
continue automatic restart until the OS login window is displayed.
l If the following window is displayed during OS installation, the sdc hard disk has not been formatted,
which does not affect installation. Click OK directly until the OS login window is displayed.

Step 6 Remove the operating system DVD-ROM.

NOTE
to access the CLI.

VERSION = 10
PATCHLEVEL = 4

# uname -rv


# yast2
Next.
4. In the Network Card Configuration Overview dialog box, select the first network
interfaces and click Edit.
NOTE
If bond has been configured for multiple network interfaces, only one MAC address is displayed for
these network interfaces. For example, if the server has four network interfaces and bond has not
been configured for them, four MAC addresses will be displayed. If bond has been configured for
two network interfaces, three MAC addresses will be displayed.

NOTE
Linux).
a. Click Routing.
Table area.
NOTE
U2000 server.
located.
d. Click OK.
e. Click OK.

NOTE
l After the system IP addresses and the routes are set, wait for about 1 to 2 minutes, then run the ping
system IP address command to check whether the network of the system is set. If the system IP address
can be pinged, the network of the system is successfully set.
after the U2000 is installed, See A.1.5 How to Add a Static Route If the U2000 Is Installed. Using
interruption.
the system.
# shutdown -r now
----End
Follow-up Procedure
3.6 Installing the U2000 Software

This topic describes how to start the U2000 installation program after a U2000 is preconfigured
by using a DVD-ROM or software package.
3.6.1 Preparing Software Packages

The U2000 can be installed using a software package or a DVD. If the U2000 is installed using
a software package, the software package needs to be uploaded to the server and decompressed.
If the U2000 is installed using a DVD, you can skip the operations mentioned in this topic.
Prerequisites
l Installation software is on-hand. For details, see 3.1.2 Checking Required Software.
l Make sure that the SFTP services are enabled. For details, see A.1.1 How to Start/Stop
the FTP/SFTP/Telnet Service in the SUSE Linux OS.
Context
NOTICE
All software packages must be uploaded to the specified directories at the primary and secondary
sties.
Procedure
Step 1 Upload the Veritas software package U2000version_veritas6.0.1_sles_x64.tar.gz to the /opt/
vrtstmp path on the workstation and then decompress it:

1. Log in to the Linux OS as user root using Telnet or SSH (more secure, recommended).
2. Run the following command to create the /opt/vrtstmp directory:
# mkdir /opt/vrtstmp
3. Use SFTP/FTP to upload the U2000version_veritas6.0.1_sles_x64.tar.gz file to the /opt/

vrtstmp directory of the server as the root user. Using SFTP is recommended because
SFTP provides higher security than FTP. For details about the method of using SFTP to
upload the software package, see A.6.15 How to Use the FileZilla to Transfer Files by
SFTP. For details about the method of using FTP to upload the software package, see A.
6.16 How to Transfer Files by Means of FTP.
4. Run the following command to view the MD5 code in the uploaded software package and
check whether the uploaded software package is appropriate.
# cd /opt/vrtstmp
# md5sum U2000version_veritas6.0.1_sles_x64.tar.gz
A message similar to the following will be displayed:

XXXXXXXXXXXXXXXXXXXXX U2000version_veritas6.0.1_sles_x64.tar.gz
NOTE
l Here, XXXXXXXXXXXXXXXXXXXXX specifies the MD5 code of the software package. The
actual output may be different from the example. Check whether the MD5 code is the same as
the counterpart in the iManager U2000 version MD5 CODE(English) file as required. If they are
the same, the uploaded software package is appropriate.
l For details about how to obtain the iManager U2000 version MD5 CODE(English) file:
1. Access http://support.huawei.com.
2. Choose Software Center > Version Software > Network OSS&Service > iManager
U2000 > iManager U2000 > iManager U2000 > desired U2000 version.
3. Download the file in the Release Document column.
5. Run the following commands to switch to the directory where the software packages reside.
Decompress the uploaded Veritas software package and assign executable rights to the
directory where the software packages reside.
# cd /opt/vrtstmp
# tar xvfz U2000version_veritas6.0.1_sles_x64.tar.gz
# chmod -R +x /opt/vrtstmp
Step 2 Upload all software packages except the Veritas software to the /opt/install path on the server
and then decompress preconfigured component, database, and security hardening packages.
1. Log in to the Linux OS as user root using Telnet or SSH (more secure, recommended).
2. Run the following command to create the /opt/install directory:
# mkdir /opt/install
3. Use SFTP/FTP to upload the software packages to the /opt/install directory on the server
as the root user. Using the FileZilla to transfer files by means of SFTP is recommended.
For details about how to use SFTP to transfer files, see A.6.15 How to Use the FileZilla
to Transfer Files by SFTP. Alternatively, use FTP to transfer files. For details about how
to use FTP to transfer files, see A.6.16 How to Transfer Files by Means of FTP.

NOTE
Ensure that all mandatory software packages are uploaded. If a software package is not uploaded,
the U2000 installation may be interrupted because a file is lacked. Selecting the components of the
transport, IP, and access domains is recommended. After the components are selected, you only need
not to download software again when adding domains. In this situation, only the disk space, not the
database space, is occupied. The installation packages to be uploaded are as follows:
1. Veritas patch (Mandatory): U2000version_server_veritas603_patch_sles_x64.tar
2. Database software (Mandatory): U2000version_server_db_linux_sybase.tar
3. Preconfigured component (Mandatory): U2000version_server_icmr_sles_x64.7z
4. Basic components (Mandatory): U2000version_server_nmsbase_sles_x64.7z
5. Core components (Mandatory): U2000version_server_nmscore_sles_x64.7z
6. Components of the transport domain (Mandatory): U2000version_server_nmstrans_sles_x64.7z
7. Components of the IP domain (Mandatory): U2000version_server_nmsip_sles_x64.7z
8. Components of the access domain (Mandatory): U2000version_server_nmsaccess_sles_x64.7z
9. Security enhancement software SetSuse (Mandatory):
U2000version_VPPSetSuseV300R003C20SPC100.tar
Run the following commands to view the uploaded software packages:

# cd /opt/install
# ls -l
4. Run the following command to view the MD5 code in the uploaded software package and
check whether the uploaded software package is appropriate.
# cd /opt/install
# md5sum filename

XXXXXXXXXXXXXXXXXXXXX U2000version_server_db_linux_sybase.tar
NOTE
l Here, XXXXXXXXXXXXXXXXXXXXX specifies the MD5 code of the software package. The
actual output may be different from the example. Check whether the MD5 code is the same as
the counterpart in the iManager U2000 version MD5 CODE(English) file as required. If they are
the same, the uploaded software package is appropriate.
l For details about how to obtain the iManager U2000 version MD5 CODE(English) file:
2. Choose Software Center > Version Software > Network OSS&Service > iManager
U2000 > iManager U2000 > iManager U2000 > desired U2000 version.
5. Run the following commands to switch to the directory where the software packages reside,
and then run the following command to decompress the preconfigured component, database
software, and security hardening packages on the server.
# cd /opt/install
NOTE
l Decompressing the Veritas patch package is optional. It is recommended that the Veritas patch
package not be decompressed.
l There is no specific decompression sequence.
l To view information about software packages in the /opt/install directory, run the command ls
-la.
l To decompress the software package in the 7z format, the 7–zip software must be installed. For
details, see A.1.16 How to Install the 7-zip Software on the SUSE Linux OS.

# tar xvf Name_of_software_package

# 7z x -y Name_of_software_package.7z
For example:
tar xvf U2000version_server_db_linux_sybase.tar
# 7z x -y U2000version_server_icmr_sles_x64.7z
NOTICE
The security hardening software SetSuse is used to enhance SUSE Linux security. Be sure
to decompress this package. If the software package is not decompressed, preconfiguration
fails.
----End
3.6.2 Preconfiguring the OS

This topic describes how to pre-configure the U2000 before installing U2000 programs. Pre-
configure the operating system (OS) using software package, which includes copying the
OSSICMR, Network Management System Maintenance Suite, and Java environment. Start the
OSSICMR to modify system parameters, install the Sybase software, construct a database server
and a database backup server, modify network settings for the system, and configure disk
mirroring.
Prerequisites
l The hardware connection is correct. For details, see 3.1.3 Checking Hardware
Connections.
l The U2000 IP address planning is well understood. For details, see 3.1.1 Collecting
Installation Information.
l Log in to the OS as the root user and run the df -h command to view disk partition
conditions. Ensure that the disk partition conditions are the same as information in G
Planning Disk Partitions. Otherwise, reinstall the OS.
l If the U2000 is installed using software packages, the installation software must have been
prepared. For more information, see 3.6.1 Preparing Software Packages.
l IP addresses have been assigned to disk array controllers if automatic disk array
configuration by means of the OSSICMR is required. For information about how to
configure the SC IP of OceanStor S3900 disk array, see 3.3.3 Setting the SC IP Address
for the OceanStor S3900 Disk Array.
l Ensure that the current OS does not use the ID of a U2000 user. For details, see A.6.17
How to Check and Change an OS User ID.

Context
NOTICE
Pre-configure the U2000 of the primary and secondary sites respectively.
The following operations are involved:

l Install OSSICMR.
l Install the Veritas software and patches.
l Automatically configure disk mirroring.
l Configure a disk array: The OSSICMR automatically verifies that the disk array is
connected and then it mounts the disk array on the server.
l Install the Sybase software.
l Construct a database server and a database backup server.
l Set network parameters for the server, such as host name, IP address, and automatic bond
configuration.
Bond: On the SUSE Linux OS, the bond technology is used to form a virtual layer between
the physical layer and the data link layer. This technology allows two server NICs
connecting to a switch to be bound to one IP address. The MAC addresses of the two NICs
are also automatically bound as one MAC address. In this manner, a virtual NIC is formed.
The bond technology supports two modes: double-live and primary/secondary. In double-
live mode, after receiving request data from a remote server, the virtual NIC on the server
determines data transmission based on an algorithm, improving network throughput and
usability of the server. In primary/secondary mode, if an NIC does not function properly,
services will be automatically switched to the other NIC, ensuring service protection. In
the SUSE Linux OS, the heartbeat lines and the replication lines supports the binding of
NICs in double-live mode, and the system lines and application lines supports the binding
of NICs in primary/secondary mode.

NOTE
l Operations mentioned in this topic can be performed through "Logging in to the SUSE Linux OS
Through Remote Login Software" or "Logging in to the SUSE Linux OS Through the Windows OS
CLI" in F Getting Started.
l After a CLI is opened, modify the CLI attributes to prevent garbled images caused by the issue that
the size of the output character is larger than the screen width. If the size of the CLI is changed after
commands are executed, the information display will be affected. Do not change the size of the CLI
after commands are executed.
l If the PuTTY is used, perform the following operations to modify CLI attributes:
1. Right-click the title bar of the CLI of the PuTTY and choose Change Settings from the shortcut
menu.
2. In the PuTTY Reconfiguration dialog box, select Window from the navigation tree and set
Columns to 120.
l If the system is running Windows, run the following command to modify CLI attributes:
1. Right-click the title bar of the CLI and choose Properties from the shortcut menu. The
Properties dialog box will be displayed.
2. On the Option tab page, set Buffer Size to 100 in the Command History area.
3. On the Layout tab page, set Width to 120 in the Screen Buffer Size area.
Procedure
Step 1 Log in to the OS as user root.
Step 2 Run the following commands to switch to the directory where the OSSICMR is located, and
assign rights to this directory.
# cd /opt/install/OSSICMR
# chmod -R 750 /opt/install/OSSICMR
Step 3 Optional: If the disk array OceanStor S3900 is available, the hardware connections and IP
configuration for the disk array are complete, and the disk array has been powered on, use the
automatic configuration scripts of OSSICMR to configure the disk array.
NOTE
The automatic configuration scripts of OSSICMR support only the disk arrays with the following
configuration:
12 x 600 GB OceanStor S3900
If a disk array whose configurations are out of the preceding range, contact Huawei technical support
engineers.
To configure the OceanStor S3900 disk array using the automatic configuration script,
perform the following operations:
1. Run the following commands to switch to the directory where the script for configuring
the OceanStor S3900 disk array is stored, and run the AutoSetupS3900.sh script to start
configuring the OceanStor S3900 disk array:
# cd /opt/install/OSSICMR/bin/array
# ./AutoSetupS3900.sh

Please enter the IP address of array controller:

NOTICE
Ensure that the entered IP address is correct. Disk partitioning in the next step will use the
IP address.
2. Enter the IP address of the primary controller of the disk array, such as 129.9.1.10 and press
Enter.
Please enter the admin user password of the array:
3. Enter the user password of the disk array and press Enter. The default user name and
password of the system administrator is Admin@storage. Changing the password after
you log in to the IMS for the first time is recommended.
============= Excute this script at: Wed Aug 22 16:01:48 CST 2012
=============
------------------------------------------------------------------------------
-
--------------- Configure OceanStor S3900 DiskArray
---------------
------------ !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!!
-----------
--------- This script will just destroy U2000lun01 the data of the
array!! ---------
------------------------------------------------------------------------------
-
Are you sure to continue? [y/n]
4. Enter y and press Enter. The script clears the configurations of the disk array.
Clear the configuration.
Reseting the arraydisk.Please wait 5 minutes...
Exist 12 free disks.
it will creat a free spare.
All disk size is 5488G.
Setuping the arraydisk... Please wait.
Configured the diskarray successfully.
NOTE
Wait about five minutes. The configuration result will be displayed. If the displayed information
contains “Configured the diskarray successfully”, the diskarray is configured successfully. If the
configuration fails again, use the ISM to configure the OceanStor S3900 disk array. For more
information, see H.1 Configuring the OceanStor S3900 Disk Array by Using the ISM.
5. Run the following commands to restart the OS:
# shutdown -r now
Step 4 Optional: If the system preconfiguration terminates, you must perform the preconfiguration
again, which consumes time. To prevent system preconfiguration termination caused by an
unexpected disconnection between the PC or laptop and the server, the GUI software VNC is
recommended for remotely logging in to the SUSE Linux operating system as the root user. For
details about the procedure, see Configure the VNC service as the root user.
NOTE
After logging in to the OS GUI, right-click and choose Open Terminal from the shortcut menu. You can
perform the follow-up system preconfiguration in the displayed CLI.

Step 5 Run the following commands to switch to the directory where the OSSICMR is located. Then,
run the install.sh file to start the OSSICMR for system preconfiguration. The configuration
process takes about 15 minutes.
# cd /opt/install/OSSICMR
# ./install.sh -r

======OS's language======
The current OS language is English, choose a correct language to set OS:

1.Chinese
2.English
please select[2]:
NOTE
If the bond is configured before or an incorrect host name or IP address is entered during OS configuration
and the network need to be reconfigured, perform the following operations to reconfigure the OS:
1. Press Ctrl+C to stop the program for configuring the OS.
2. Run the following commands to restart the OS and clear the network configuration environment:
# shutdown -r now
3. Run the following commands to reconfigure the OS.
# cd /opt/OSSICMR/bin
# ./install.sh -r
The information displayed is different from that displayed after configure the OS for the first time.
Perform operations by following the prompts and pay attention to the configuration items whose
configuration results are Failed.
Step 6 Configure the language of the operating system as required. To set the language to English, enter
2 and press Enter.
NOTE
If the language is set to English, install the U2000 of the English version.

======= Database path =======
Enter the database path in which to install the database software.
Enter the path and press Enter, or press Enter to use the default
directory[/opt/sybase]:
Step 7 Press Enter.
NOTICE
The database installation path may vary according to disk partitions. By default, the database is
installed in the /opt/sybase path. Using the default installation path is recommended. When
using a self-defined path, ensure that the path has enough space for installation.
l If the database has been installed on the system, a message is displayed asking you whether
to reuse database information.

If need to reuse the sybase
1. yes
2. no
Select[1]:
Choose whether to reuse the database as required.

– To reuse the database, perform the following operations:
1. If the database must be reused, enter 1 and press Enter.
Please input the database administrator account[sa] :
2. Enter the user name of the database administrator, such as sa. Press Enter.
Please input the password of database administrator account :
NOTE
In order to enhance the security of the Sybase database, the sa user may be manually disabled and
replaced with a customized administrator name, such as dbadmin.
3. Enter the password of the database administrator and press Enter. The system
automatically checks whether the password is correct. If the password is incorrect,
perform this step again. If the password is correct, information similar to the
following is displayed:
==== OSS path =======
Enter the OSS path in which to install the OSS software.
Enter the path and press Enter, or press Enter to use the
default directory[/opt/oss]:
– If the database does not need to be used, enter 2 and press Enter. The system automatically
checks whether the current database installation path is empty. If the path is not empty,
manually delete the files in the path and perform this step again. If the path is empty,
information similar to the following is displayed:
==== OSS path =======
directory[/opt/oss]:
NOTE
Run the following command to delete the database file. If the error message rm:cannot remove
directory '/opt/sybase/data': Device or resource busy is displayed during
file deletion, ignore it.
# rm -rf /opt/sybase
After the database file is deleted, ensure that the /opt/sybase directory contains only one empty /
opt/sybase/data folder.
l If the database has not been installed on the system, enter the U2000 installation path.
==== OSS path =======

directory[/opt/oss]:
Step 8 Press Enter.
NOTICE
The OSS installation path may vary according to disk partitions. By default, the OSS is installed
in the /opt/oss path. Using the default installation path is recommended. When using a self-
defined path, ensure that the path has enough space for installation.

Please input the system IP[129.9.1.1]:
Step 9 Set IP addresses according to different network interface solutions.

NOTE
l For details about the mappings Between Physical and Logical Network Interfaces on an IBM Server
Running SUSE Linux, see A.3.8 Mappings Between Physical and Logical Network Interfaces on
an IBM Server Running SUSE Linux.
l If an incorrect characters is entered and the character cannot be deleted after Backspace is pressed,
hold down Ctrl+Backspace to delete the characters and then enter a correct character.

Network Operation
Interface
Solution
Four-network 1. Enter a planned system IP address.

interface Solution Please input the system hostname[linux]:
2. Enter a planned host name. For example, set the primary site name
to Primaster and the secondary site name to Secmaster. The
following example uses the primary site name.
NOTICE
To ensure that the NMS can run properly, host name planning must comply
with the following rules and restrictions:
l The host name must be a string consisting of no more than 24 characters
that can only be letters (A to Z, a to z), digits (0 to 9) and hyphen (-).
l The first character must be a letter and the last character cannot be a
hyphen.
l The host name cannot be any of the following keywords in the high
availability system.
action false keylist static after firm local
stop requires remotecluster
system group resource global Start str temp
set heartbeat ArgListValues
System Group boolean hard Name soft before
online condition MonitorOnly
remote start cluster event VCShm type Path
offline Signaled HostMonitor
Probed state Cluster IState int Type State
VCShmg NameRule ConfidenceLevel
Please input the system netmask[255.255.255.0]:
3. Enter a planned subnet mask.

*********************************
1 eth1
2 eth2
3 eth3
4 eth4
5 eth5
6 eth6
7 eth7
*********************************
Please select a NIC to be used for the system standby NIC
[1,2,...]:
4. According to the planned heartbeat IP addresses and the Bond plan,

select the planned system standby NIC, for example, enter 4.
Please confirm the following configurations...
**********************************************************
********
system NIC
eth0
system IP
129.9.1.1
system hostname

Network Operation
Interface
Solution
secondary
system netmask
255.255.255.0
system standby NIC
eth4
**********************************************************
********
Enter 'y' to apply these values and proceed to the next
step, or 'n' to return to make any changes (y/n):
5. Enter y to confirm the configurations. To modify the configurations,

enter n. Then press Enter.
======= Config heart beat bond =======
Bond detects failures and repairs of network

connectivity for physical interfaces and provides failover
and failback of IP addresses among members of the same
group.
1. eth1
2. eth2
3. eth3
4. eth5
5. eth6
6. eth7
Please select nic or Press Enter to use the

default value[1,2]:
6. Enter the numbers of the two NICs based on the planned heartbeat
bond scheme, such as 1,4. Then press Enter.
Please input the heartbeat network service IP[]:
7. Enter the IP address of the heartbeat network service.

Please input the hostname for the heart beat network
service IP[HBService]:
8. Press Enter to use the default host name of the heartbeat network
service.
Please input the netmask for the heart beat network service
IP[255.255.255.0]:
9. Enter the mask of the IP address of the heartbeat network service.

**********************************************************
********
master NIC for the heart beat network service
IP
eth1
heartbeat network service IP
192.168.100.10
hostname for the heart beat network service IP
HBService
netmask for the heart beat network service IP
255.255.255.0
standby NIC for the heart beat network service
IP
eth5
**********************************************************
********

Network Operation
Interface
Solution
10.Enter y to confirm the configurations. To modify the configurations,

iManager OSS ICMR
******************************************************
1 APP network use standalone network
2 APP network reuse system network
******************************************************
Please select the network scheme [1,2]:
11.Enter the number of the network scheme based on the planned IP

address. It is recommended that enter 2 to enable APP network to
reuse the system network. Press Enter.
Please input the Float Application IP:
12.Enter a float application IP address.

**********************************************************
********
Float Application IP
129.9.1.3
Float Hostname
Primaster
Net mask
255.255.255.0
Float IP NIC
eth0
**********************************************************
********

Network Operation
Interface
Solution
Six-network 1. Enter a planned system IP address.

interface Solution Please input the system hostname[linux]:
2. Enter a planned host name. For example, set the primary site name
to Primaster and the secondary site name to Secmaster. The
following example uses the primary site name.
NOTICE
To ensure that the NMS can run properly, host name planning must comply
with the following rules and restrictions:
l The host name must be a string consisting of no more than 24 characters
that can only be letters (A to Z, a to z), digits (0 to 9) and hyphen (-).
l The first character must be a letter and the last character cannot be a
hyphen.
l The host name cannot be any of the following keywords in the high
action false keylist static after firm local
stop requires remotecluster
system group resource global Start str temp
set heartbeat ArgListValues
System Group boolean hard Name soft before
online condition MonitorOnly
remote start cluster event VCShm type Path
offline Signaled HostMonitor
Probed state Cluster IState int Type State
VCShmg NameRule ConfidenceLevel
Please input the system netmask[255.255.255.0]:
3. Enter a planned subnet mask.

*********************************
1 eth1
2 eth2
3 eth3
4 eth4
5 eth5
6 eth6
7 eth7
*********************************
Please select a NIC to be used for the system standby NIC
[1,2,...]:
4. According to the planned system IP addresses and the Bond plan,

select the planned system standby NIC, for example, enter 4.
**********************************************************
********
system NIC
eth0
system IP
129.9.1.1
system hostname

Network Operation
Interface
Solution
primary
system netmask
255.255.255.0
system standby NIC
eth4
**********************************************************
********
5. Enter y to confirm the configurations. To modify the configurations,

======= Config heart beat bond =======

group.
1. eth1
2. eth2
3. eth3
4. eth5
5. eth6
6. eth7

default value[1,2]:
6. Enter the numbers of the two NICs based on the planned heartbeat
Please input the heartbeat network service IP[]:
7. Enter the IP address of the heartbeat network service.

Please input the hostname for the heart beat network
service IP[HBService]:
8. Press Enter to use the default host name of the heartbeat network
service.
Please input the netmask for the heart beat network service
IP[255.255.255.0]:
9. Enter the mask of the IP address of the heartbeat network service.

**********************************************************
********
master NIC for the heart beat network service
IP
eth1
heartbeat network service IP
192.168.100.10
hostname for the heart beat network service IP
HBService
netmask for the heart beat network service IP
255.255.255.0
standby NIC for the heart beat network service
IP
eth5
**********************************************************
********

Network Operation
Interface
Solution

iManager OSS ICMR
******************************************************
1 APP network use standalone network
2 APP network reuse system network
******************************************************
Please select the network scheme [1,2]:
11.Enter the number of the network scheme based on the planned IP

address. It is recommended that enter 1 to configure the application
network as an independent network. Press Enter.
======= Config application bond =======

group.
1. eth2
2. eth3
3. eth6
4. eth7

default value[1,2]:
12.Enter the numbers of the two NICs based on the planned application
Please input the application network service IP[]:
13.Enter the IP address of the application network service.

Please input the hostname for the application network
service IP[APPService]:
14.Press Enter to use the default host name of the application network
service.
Please input the netmask for the application network
service IP[255.255.255.0]:
15.Enter the mask of the IP address of the application network service.

**********************************************************
********
master NIC for the application network service
IP
eth2
application network service IP
129.9.3.1
hostname for the application network service
IP
APPService
mask
255.255.255.0
standby NIC for the application network service
IP
eth6
**********************************************************
********

Network Operation
Interface
Solution

enter n.
Please input the Float Application IP:
17.Enter a float application IP address.

**********************************************************
********
Float Application IP
129.9.3.3
Float Hostname
APPService
Net mask
255.255.255.0
Float IP NIC
eth2
**********************************************************
********
Step 10 Enter y to confirm the configurations. To modify the configurations, enter n. And then press
Enter.
iManager OSS
ICMR
Modifing the system
parameters........................................................................
.......Done
Installing veritas volume
manager...........................................................................
.Done
Installing veritas extra
patchs............................................................................
..Done
iManager OSS ICMR

The configurations take effect only after the system is restarted. The system will
restart.
Broadcast message from root (pts/0) (Thu Dec 6 17:31:18 2012):
The system is going down for reboot NOW!
The system restarts automatically.

NOTE
If a message is displayed indicating that the security hardening software SetSuse is unavailable, do not shut
down the dialog box but use the FileZilla to transfer the security hardening package
U2000version_VPPSetSuseV300R003C20SPC100.tar to the /opt/install/ directory through SFTP. Then
open another terminal to log in to the OS as root user and decompress the security hardening package to
the /opt/install/ directory. After confirming that the decompression is complete, press Enter to continue
with system preconfiguration.
Step 11 After the system is restarted, the installation continues. Log in the server as the root user and
then run the following command to view the installation progress:
# tail -f /var/ICMR/install.log

Checking the system info...................................................

Set OS's language..........................................................
Modifing the system parameters.............................................
Installing veritas volume manager..........................................
Installing veritas extra patchs............................................
Encapsuling diskgroup......................................................
Create volumes.............................................................
Configuring the vcs........................................................
Install database Software..................................................
Build the database server and install the patches..........................
unpacking NMS packages.....................................................
All operations defined in the task flow have been completed.
All operation logs are saved in:
/var/ICMR/ICMR_20140127112547.log
Press Ctrl+c to stop viewing logs.
NOTE
l If All operations defined in the task flow have been completed is displayed, the configuration is
successful.
l If Failed is returned, the configuration fails. In this case, save the operation log, and contact Huawei
engineers for fault locating.
l If no process information, after the configuration is complete, run the command cat /var/ICMR/
install.log to view all contents of install.log.
l After configuring the OS, apply for the formal Veritas license for the related Veritas version as soon
as possible.
Step 12 Do as follows to check the Veritas version and patch information:

1. To check the VxVM version, run the following command:
# rpm -qa | grep VRTSvxvm
If information similar to the following is displayed, the VxVM version is correct.
VRTSvxvm-6.0.300.000-SLES10
If information to the right of VRTSvxvm is not 6.0.300.000-SLES10, you must reinstall
Veritas 6.0.1 and Veritas patche 6.0.3 or contact Huawei engineers.
2. To check the VCS version, run the following command:
# rpm -qa | grep VRTSvcs
If information similar to the following is displayed, VCS version is correct.
VRTSvcs-6.0.300.000-GA_SLES10
VRTSvcsdr-6.0.100.000-GA_SLES10
VRTSvcsea-6.0.300.000-GA_SLES10
VRTSvcsag-6.0.300.000-GA_SLES10
Pay attention to the information to the right of VRTSvcs. If the information to the right of
VRTSvcs is not 6.0.300.000-GA_SLES10, you must reinstall Veritas 6.0.1 and Veritas
patche 6.0.3 or contact Huawei engineers.
----End
Follow-up Procedure
Disk mirroring is configured during the pre-configuration. To view the disk mirroring
configurations, run the following command:
# vxprint -p


Disk group: datadg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

pl lv_backup-01 lv_backup ENABLED 838860800 - ACTIVE - -
pl lvapp-01 lvapp ENABLED 419430400 - ACTIVE - -
pl lvdata-01 lvdata ENABLED 314572800 - ACTIVE - -
pl lvdata-02 lvdata ENABLED LOGONLY - ACTIVE - -
pl lvdatabase-01 lvdatabase ENABLED 314572800 - ACTIVE - -
pl srl-01 srl ENABLED 20971520 - ACTIVE - -
NOTE
lvapp-01 and lvdatabase-01 is displayed only when the U2000 server is connected to the disk array.
3.6.3 Starting the U2000 Installation Program

This topic describes how to start the U2000 installation program. Install the U2000 software
through the GUI (recommended) or CLI. If the GUI cannot be logged in to, install the U2000
software through the CLI. GUI is short for graphical user interface and CLI for command line
interface.
3.6.3.1 Installing the U2000 on the GUI

This topic describes how to install the U2000 software on the GUI. In comparison with the CLI,
the installation on the GUI is clear and easy to operate. It is recommended that you install the
U2000 on the GUI if you are not familiar with the common commands of the SUSE Linux OS.
Prerequisites
l Ensure that the U2000 is pre-configured. The U2000 will fail to install if it is not pre-
configured.
l Ensure that the size of the installation directory of the server meets the requirement. The
remaining space of the installation directory must be larger than 30 GB.
NOTE
Run the df -h /opt command to view the remaining space of the /opt directory.
l The GUI software VNC is recommended for remotely logging in to the SUSE Linux
operating system, must be ready. For details about how to configure and use the VNC, see
Configure the VNC service as the root user.
l The network interface used in system preconfiguration has been enabled.
NOTE
Run the ifconfig -a command to view the NIC running status. Ensure that the network interface
eth used in system preconfiguration is UP and RUNNING.
If the NIC running status is abnormal, perform the following operations:
l Check network cable connections on the NIC. Ensure that the network cables are connected
properly.
l Run the ifconfig ethX up command to enable the specified NIC.
l Ensure that the database has been started. For details about how to check whether the
database has been started, see A.5.1.3 How to Verify That the Sybase Database Is
Running. If the database is not started, refer to A.5.1.2 How to Start the Sybase Database
Service to start the database.

Context
NOTE
l To prevent the keyboard from being locked, the SCIM process is stopped after the U2000 installation
program is started. After the U2000is installed, the SCIM process starts automatically.
l If the server on which the steps described in this topic must be performed is not specified, perform the
steps on the primary and secondary sites.
l The number pad keyboard is not recommended. This is because Num Lock may fail to work normally
when the OS is installed on certain machines.
Procedure
Step 1 Log in to the server OS as user root using the remote desktop control software.
Step 2 On the desktop, right-click and choose Open Terminal from the shortcut menu to display a
CLI.
Step 3 Run the following commands to assign permissions to the installation directory.
# chmod -R 750 /opt/oss
Step 4 Run the following commands to go to the path where the install.sh file is stored and run the
install.sh file:
# cd /opt/oss
# ./install.sh

exec createlinks.sh script enter...
Running setup initialization...
Starting the OSS engineering installation server...
Start the OSS engineering installation server Successfully.
Wait about one minute. The Copyright dialog box will be displayed.
NOTE
Read the terms of the software license agreement carefully.
Step 5 Click I accept the terms, and click Next to continue. The Select Language dialog box will be
displayed.
Step 6 Select the language according to the conditions at your site, such as English. Then, click
Next. The Select Installation Type dialog box will be displayed.
NOTE
To use the OS of the English version, select English.

NOTE
If Automatically configure the OSS license file during the installation needs to be selected, upload the
license file to the server before selecting it.
Step 7 If the License file has been uploaded to the server, click Next. Otherwise, clear the selection of
Automatically configure the OSS license file during the installation, and then click Next.
The Configure Database dialog box will be displayed.
Set the installation parameters and the following table shows the basic settings of the database
server and NMS database user.
Parameter Description
Server Address The default value is application IP addresses.
Server Name The default value is DBSVR.
Server Port The default value is 4100.

Administrator Name The default value is sa.
Administrator Password Enter a password of the database administrator and refer to

the following operations to verify the password.
l If no database is reused in the system preconfiguration
procedure, enter the administrator password for the
newly installed database. The default value is
Changeme_123.
l If a database is reused in the system preconfiguration
procedure and the database administrator password meet
the following requirements, please enter the
administrator password of reused database.
l If a database is reused in the system preconfiguration
procedure and the database administrator password does
not meet the following requirements, change the
password. For details, see A.5.2.4 How to Change the
sa User Password for the Sybase Database If the
U2000 Is Not Installed.
l The password of the database administrator at the
primary site must be consistent with that at the secondary
site.
NOTE
The database administrator password must meet the requirements:
l The password contains a minimum of eight characters and a
maximum of 30 characters.
l The password must contain at least four of the following
combinations:
l At least one lower-case letter
l At least one upper-case letter
l At least one digit
l At least one special character ~@#^*-_+[{}]:./?
Other special characters are not supported. Do not include
other special characters, such as ()|<>&`!$\"%'=;,space in
passwords.
l The password cannot be the same as the user name written in
either the forward or backward format.
The default value is Changeme_123.

OSS Database User Password The OSS database user password must meet the
requirements:
l The password contains a minimum of eight characters
and a maximum of 30 characters.
l The password must contain at least four of the following
combinations:
– At least one lower-case letter
– At least one upper-case letter
– At least one digit
– At least one special character ~@#^*-_+[{}]:./?
Other special characters are not supported. Do not
include other special characters, such as ()|<>&`!$
\"%'=;,space in passwords.
l The password cannot be the same as the user name
written in either the forward or backward format.
Set a new password for OSS database user. For example,
Changeme_123.
NOTICE
l The password of the database user at the primary site must be
consistent with that at the secondary site.
l Plan and enter a new password according to the preceding
password rules to ensure system security. Make a note of your
password and keep it in a safe place. Do not share your password
with anyone.
Confirm OSS Database User Confirms the password of the OSS database user.
Password
Step 8 Click Next. The Configure Server dialog box will be displayed.

Step 9 Click Next. The Select Domain dialog box will be displayed.
NOTE
Select the domain need to be deployed based on the managed devices.
Step 10 Click Next. The Preinstallation Check will be displayed.

NOTE
1. If the uploaded and decompressed package involves the transport domain, the Version Style dialog
box is displayed.
The following is an example of the differences between the two styles:
l For the Default style, alarms come in the following descending order of severity: Critical,
Major, Minor, and Warning.
l For the North American style, alarms come in the following descending order of severity:
Critical, Major, Minor, Not Alarmed, and Not Reported.
2. Click Next. The Version Timeslot Mode will be displayed.
3. Select the time slot mode as required, such as Sequential mode. The Sequential mode, a timeslot
numbering policy recommended by the ITU-T.

Step 11 Click Next. The installation information will be displayed.
Step 12 Click Next. A progress bar will be displayed. The time required for the installation depends on
the number of components to be installed and the server configuration. The entire process takes
about 90 minutes. Wait patiently.
NOTE
l The OSS can automatically expand the capacity of a database according to the growth parameters
defined when the database is created. The disk space for installing the database must be greater than
the maximum size to which the file is permitted to grow. If the disk space is insufficient, the system
will display a prompt message in red. The U2000 can manage the maximum number of NEs as
supported by the server model.
l If a message indicating an installation failure or interruption is displayed during installation, see A.7.2
How do I solve the problem where a failure message is displayed during the installation or the
installation is abnormally interrupted to solve the problem.
The system will display a prompt indicating that installation was successfully completed.
Step 13 Click Finish to complete the U2000 installation.
Step 14 Run the following commands to restart the OS. It takes approximately 5 to 8 minutes to restart
the system.
# shutdown -r now
Step 15 Optional: In order to enhance the security of the Sybase database after the U2000 is installed,
you need to manually create a user to replace the database administrator sa and assign the user
with same permissions as the sa user. After the permissions are assigned to the user, disable the
sa user. For details, see A.5.2.8 How to Create a Replacement User for the Sybase Database
Administrator sa User.
----End
3.6.3.2 Installing the U2000 Through the CLI

This topic describes how to install the U2000 software through the CLI. This method is
recommended if you cannot log in to the GUI of the OS.
Prerequisites
l Ensure that the U2000 is pre-configured. The U2000 will fail to install if it is not pre-
configured.
l Ensure that the size of the installation directory of the server meets the requirement. For
example, if all domains need to be deployed, the remaining space of the installation
directory must be larger than 30 GB.
NOTE
Run the df -hk /opt command to view the remaining space of the /opt directory.
l The network interface used in system preconfiguration has been enabled.

NOTE
Run the ifconfig -a command to view the NIC running status. Ensure that the network interface
eth used in system preconfiguration is UP and RUNNING.
If the NIC running status is abnormal, perform the following operations:
l Check network cable connections on the NIC. Ensure that the network cables are connected
properly.
l Run the ifconfig ethX up command to enable the specified NIC.
l Ensure that the database has been started. For details about how to check whether the
database has been started, see A.5.1.3 How to Verify That the Sybase Database Is
Running. If the database is not started, refer to A.5.1.2 How to Start the Sybase Database
Service to start the database.
Context
NOTICE
If the server on which the steps described in this topic must be performed is not specified, perform
the steps on the primary and secondary sites.
After a CLI is opened, modify the CLI attributes to prevent garbled images caused by the issue
that the size of the output character is larger than the screen width. If the size of the CLI is
changed after commands are executed, the information display will be affected. Do not change
the size of the CLI after commands are executed.
l If the PuTTY is used, perform the following operations to modify CLI attributes:
1. Right-click the title bar of the CLI of the PuTTY and choose Change Settings from
the shortcut menu.
2. In the PuTTY Reconfiguration dialog box, select Window from the navigation tree
and set Columns to 120.
l If the system is running Windows, run the following command to modify CLI attributes:
1. Right-click the title bar of the CLI and choose Properties from the shortcut menu.
The Properties dialog box will be displayed.
2. On the Option tab page, set Buffer Size to 100 in the Command History area.
3. On the Layout tab page, set Width to 120 in the Screen Buffer Size area.
Procedure
Step 1 Log in to OS as user root.
Step 2 Run the following commands to assign permissions to the installation directory.
# chmod -R 750 /opt/oss
Step 3 Run the following commands to switch to the path where the install.sh file is stored and run the
install.sh script:
# cd /opt/oss
# ./install.sh -cmd

exec createlinks.sh script enter...

Running setup initialization...
Starting the OSS engineering CMD installation server...
===============< Copyright Notice >===============

Copyright Notice
...
I accept the terms [y:Yes, n:No, n]:
NOTE
Read the terms of the software license agreement carefully.
Step 4 Enter y and press Enter.

Install [c:Cancel, <p:Previous, n:Next>, n]:
Step 5 Enter n and press Enter.

===============< Language >===============
Language [1:Chinese, 2:English, 2]:
Step 6 Enter 2 and then press Enter to select the English version.
NOTE
To use the OS of the English version, select English.


===============< Configure the license file required for OSS (If no license file
is available, enter "n" to continue). >===============
Automatically configure the OSS license file during the installation[y:Yes, n:No,
y]:
Step 8 If the license file is available, enter y and press Enter. If the license file is not available, enter
n and press Enter. Entering n and pressing Enter are used as an example.
NOTE
If y is entered, enter the license file path (including the file name) as prompted and press Enter.


===============< Configure Database >===============
Server Address:[129.9.1.1]:
Step 10 Press Enter to use the default IP address.

Server Name:[DBSVR]
Server Port:[4100]
Administrator Name:[sa]:
Step 11 Configure the information about the database service.

Server Name:[DBSVR]
Server Port:[4100]
Administrator Name:[sa]:
Administrator Password:[]:**********
OSS Database User Password:[]:**********
Confirm OSS Database User Password:[]:**********
Install [c: Cancel, <p:Previous, n:Next>, n]:
l When configuring the information about the database service, you can press Ctrl+H to delete
incorrectly entered information.
l The default value of Administrator Name is sa.
l Enter a password of the database administrator and refer to the following operations to verify
the password.
– If no database is reused in the system preconfiguration procedure, enter the administrator
password for the newly installed database. The default value is Changeme_123.
– If a database is reused in the system preconfiguration procedure and the database
administrator password meet the following requirements, please enter the administrator
password of reused database.
– If a database is reused in the system preconfiguration procedure and the database
administrator password does not meet the following requirements, change the password.
For details, see A.5.2.4 How to Change the sa User Password for the Sybase Database
If the U2000 Is Not Installed.
– The password of the database administrator at the primary site must be consistent with
that at the secondary site.
NOTE
The database administrator password must meet the requirements:

l The password contains a minimum of eight characters and a maximum of 30 characters.
l The password must contain at least four of the following combinations:
Other special characters are not supported. Do not include other special characters, such as ()|<>&`!
$\"%'=;,space in passwords.
l The password cannot be the same as the user name written in either the forward or backward format.
The default value is Changeme_123.
l The OSS database user password must meet the requirements:
– The password contains a minimum of eight characters and a maximum of 30 characters.
– The password must contain at least four of the following combinations:
– At least one lower-case letter
– At least one upper-case letter
– At least one digit
– At least one special character ~@#^*-_+[{}]:./?

Other special characters are not supported. Do not include other special characters,
such as ()|<>&`!$\"%'=;,space in passwords.
– The password cannot be the same as the user name written in either the forward or
backward format.
Set a new password for OSS database user. For example, Changeme_123.
NOTICE
l The password of the database user at the primary site must be consistent with that at the
secondary site.
l Plan and enter a new password according to the preceding password rules to ensure system
security. Make a note of your password and keep it in a safe place. Do not share your
password with anyone.

===============< Deploy Server >===============
Server IP Address:[0:129.9.1.1, 0]:
Step 13 Confirm the Server IP Address and then press Enter.

===============< Deploy Server >===============
Server IP Address:[0:129.9.1.1, 0]:

Installation Path:[/opt/oss]

===============< Select Deployment Domain >===============
[1:Access domain, 2:IP domain, 3:Transport domain, 1,2,3]:
NOTE
Select the domain need to be deployed based on the managed devices.
Step 15 Enter the serial number of the domain to be deployed. If multiple serial numbers are to be entered,
use comma (,) to separate them. For example, 1,2,3. Press Enter.


NOTE
1. If the uploaded and decompressed package involves the transport domain, choose for the Version
Style and press Enter.
The following is an example of the differences between the two styles:
l For the Default style, alarms come in the following descending order of severity: Critical,
Major, Minor, and Warning.
l For the North American style, alarms come in the following descending order of severity:
Critical, Major, Minor, Not Alarmed, and Not Reported.
2. Enter n and press Enter.
3. Select the time slot mode as required, such as Sequential mode. The Sequential mode, a timeslot
numbering policy recommended by the ITU-T.

===============< Preinstallation Check >===============
Check whether a user can be added for the OS ( OK )
Check whether the OSS user is normal ( OK )
Check the available space of the OS path ( OK )
Check whether the backup service of the Sybase database has been started ( OK )
Check database commands, such as isql, bcp, osql, and sqlplus ( OK )
Check the Sybase version ( OK )
Calculate the disk space required by the database ( OK )
Install [c: Cancel, <p:Previous, n:Next>, n]:

===============< Confirm Installation Information >===============
...
...
Install[c:Cancel, <p:Previous, n:Next>, n]:
Step 18 Confirm that the installation information is correct, enter n and press Enter. The time required
for the installation depends on the number of components to be installed and the server
configuration. The entire process takes about 90 minutes. Wait patiently.
===============< Show Installation Progress >===============
Initializing the data...Please wait.:0%
NOTE
l The OSS can automatically expand the capacity of a database according to the growth parameters
defined when the database is created. The disk space for installing the database must be greater than
the maximum size to which the file is permitted to grow. If the disk space is insufficient, the system
will display a prompt message in red. The U2000 can manage the maximum number of NEs as
supported by the server model.
l If a message indicating an installation failure or interruption is displayed during installation, see A.7.2
installation is abnormally interrupted to solve the problem.
Step 19 After the installation, the message similar to the following will be displayed:
===============< Installation Finished >===============
Finish
The U2000 has been installed in the directory /opt/oss.

NOTE
If You have new mail is displayed, it belongs to the system message does not affect the oss, please ignore
this message.
the system.
# shutdown -r now
Step 21 Optional: In order to enhance the security of the Sybase database after the U2000 is installed,
you need to manually create a user to replace the database administrator sa and assign the user
with same permissions as the sa user. After the permissions are assigned to the user, disable the
sa user. For details, see A.5.2.8 How to Create a Replacement User for the Sybase Database
Administrator sa User.
----End
3.7 Configuring a Route

Before connecting the primary and secondary sites, ensure that the application, heartbeat, and
replication routes are reachable between the primary and secondary sites. If these routes are
unreachable, the primary and secondary sites cannot be connected. If the primary and secondary
sites are on different network segments, refer to this topic to add routes on the other network
segment for the primary and secondary sites. If the U2000 server and client are on different
network segments, you also need to refer to this topic to add routes on the other network segment
for the primary and secondary sites.
Prerequisites
l U2000 processes must have been stopped. For how to stop the U2000 processes, see A.
4.2.9 How to Start/Stop the NMS Before Synchronizing the Primary and Secondary
Sites (Solaris, PC Linux).
l The GUI software VNC is recommended for remotely logging in to the SUSE Linux
operating system, must be ready. For details about how to configure and use the VNC, see
Configure the VNC service as the ossuser user.
Context
A static route restricts the access to the server at IP addresses within a specified network segment.
Therefore, static routes have higher security than default routes. Perform the following
operations to configure a static route.
Procedure
Step 1 Ensure that the MSuite server has been started.
Run the following command as the root user to check whether the MSuite servers are started:
NOTE
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root command and
enter the root user password to switch to the root user.
# ps -ef | grep java
A message similar to the following will be displayed in the SUSE Linux system:

...
root 19985 1 0 Nov23 ? 00:34:37 /opt/oss/OSSJRE/jre_linux/bin/java
-server -Dlanguage=zh -Xverify:none -Xms512m -Xmx1024m -XX:MaxPermSize=256m -
XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=95 -XX:+UseParNewGC -XX:
+UseConcMarkSweepGC -Dengr.launcher.file=engineering/conf/launch/
deploysever_launcher.xml -Dequinox.conf=engineering/conf/equinox.ini -
Dos.native.path=engineering/lib -DCoreFramework.logFilePath=engineering/conf/
loggerservice_Server.cfg -Djava.library.path=engineering/lib/linux -
Drunway=maintenance -DautoLogin=true -DinstallDiskMode=cmd -DinstallType=server -
classpath engineering/lib/Launcher.jar:engineering/lib/equinox.jar
com.oss.core.launcher.Launcher
NOTE
If the displayed information contains /opt/oss/OSSJRE/jre_linux/bin/java -server, the MSuite servers have
been started.
If the MSuite servers have not been started, run the following commands as the root user to start
the MSuite servers:
# cd /opt/oss/engr/engineering
# ./startserver.sh
Step 2 Log in to the OS in GUI mode as user ossuser using the remote desktop control software, such
as VNC.
NOTE
The initial password of the ossuser user is Changeme_123. The password needs to be changed during the
first login to ensure system security. Change the password in time, regularly update it, and keep it safe. For
details, see A.6.14 How to Change the OS User Password.
Step 3 Double-click the U2000 NMS Maintenance Suite shortcut icon on the desktop and then wait
about one minute. The Login dialog box is displayed.
NOTE
In Solaris or SUSE Linux OS, log in to the Java desktop system as user ossuser. Otherwise, the U2000
NMS Maintenance Suite shortcut icon is not displayed on the desktop. To start the MSuite client by
running commands, log in to the OS in GUI mode and run the following commands as user ossuser. If you
have logged in as the root user, you cannot run the su - ossuser command to switch to the ossuser user to
run the following command. You must log out of the root user and then log in to the system as the
ossuser user.
$ cd /opt/oss/client/engineering
$ ./startclient.sh
Step 4 Set the login parameters.

The login parameters are described as follows:
l IP Address: Log in to the local MSuite server, use the default IP address 127.0.0.1.
NOTE
The Login dialog box of the MSuite server has the function to keep the login list. Selecting an IP
address from the IP Address drop-down list is recommended. If the desired IP address is not displayed
in the drop-down list, enter an IP address.
l Port: The default port ID is 12212. There is no need to change the default value during login
but ensure that the port is not occupied.
l User Name: The default user name is admin.
l Password: The initial password of the admin user is Changeme_123 (It is Admin_123 for
a U2000 that comes preinstalled). The password must be changed during the first login to
ensure system security. Keep the password confidential and change it regularly.
Step 5 Click Login.

NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of querying
components. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the MSuite at one
time.
l Change the initial password upon your first login to ensure U2000 system security and remember the new
password.
Step 6 On the MSuite client, click the Server tab.
Step 7 Right-click the target server and choose Configure Route from the shortcut menu. The
Configure Route dialog box is displayed.
Step 8 In the dialog box that is displayed, click Add or Delete according to actual route conditions to
configure the route.
NOTICE
Before adding a route, ensure that the server and the router are directly connected. Otherwise,
the route cannot be added.
For example, the procedure for adding a route from a client (IP address: 10.70.73.77) to a server
(IP address: 10.78.224.12) is as follows, with the IP address of the intermediate router being
10.78.224.1:
1. Ensure that the server and the router are directly connected.
2. Click Add. Set Destination to 10.70.73.0, Subnet Mask to 255.255.255.0, and Route to
10.78.224.1.

Step 9 Click OK.
Step 10 After the configurations are complete, run the netstat -nr command to view route configurations.
----End
3.8 Connecting the Primary and Secondary Sites

Prerequisites
l The preceding steps for installing the primary and secondary sites must be complete.
l The MSuite client login password, database administrator password, and database NMS
user password must be the same on the primary and secondary sites.
l The installed components must be the same on the primary and secondary sites.
l The operations on the primary and secondary sites must be the same.
l Ensure that the network between the primary and secondary sites is smooth.
l All VCS clients on the primary and secondary sites must be logged out of.
l MSuite client on the secondary site must be logged out of.
l Ensure that the host names of primary and secondary sites are different.
l Ensure that VVR ports can be connected.
Context
Connect the primary and secondary sites in either of the following modes:
l Mode 1 (recommended): GUI mode. If you are not familiar with common commands of
the SUSE Linux OS, connecting the primary and secondary sites in GUI mode is
recommended.
l Mode 2: CLI mode. If you fail to log in to the OS in GUI mode, using primary and secondary
sites the CLI mode is recommended.

Procedure
l Mode 1 (recommended): Connect the primary and secondary sites in GUI mode.
1. Ensure that the MSuite server has been started.
Run the following command as the root user to check whether the MSuite servers are
started:
NOTE
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root
command and enter the root user password to switch to the root user.
...
root 19985 1 0 Nov23 ? 00:34:37 /opt/oss/OSSJRE/jre_linux/
bin/java -server -Dlanguage=zh -Xverify:none -Xms512m -Xmx1024m -
XX:MaxPermSize=256m -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=95 -XX:
+UseParNewGC -XX:+UseConcMarkSweepGC -Dengr.launcher.file=engineering/
conf/launch/deploysever_launcher.xml -Dequinox.conf=engineering/conf/
equinox.ini -Dos.native.path=engineering/lib -
DCoreFramework.logFilePath=engineering/conf/loggerservice_Server.cfg -
Djava.library.path=engineering/lib/linux -Drunway=maintenance -
DautoLogin=true -DinstallDiskMode=cmd -DinstallType=server -classpath
engineering/lib/Launcher.jar:engineering/lib/equinox.jar
NOTE
If the displayed information contains /opt/oss/OSSJRE/jre_linux/bin/java -server, the MSuite
servers have been started.
If the MSuite servers have not been started, run the following commands as the root
user to start the MSuite servers:
# ./startserver.sh
2. Log in to the OS in GUI mode of the primary site as the ossuser user.
NOTE
The initial password of the ossuser user is Changeme_123. The password needs to be changed
during the first login to ensure system security. Change the password in time, regularly update
it, and keep it safe. For details, see A.6.14 How to Change the OS User Password.
3. On the primary site, start up the MSuite client.
Double-click the shortcut icon of the U2000 NMS Maintenance Suite or run the
following commands:
$ ./startclient.sh
Wait for about one minute. A dialog box is displayed, as shown in the following figure.

Then, set the related parameters according to the following table.
Parameter Settings
IP Address l If the Network Management System Maintenance Suite

client and the Network Management System Maintenance
Suite server are on the same computer, you must enter
127.0.0.1 or the application IP address on the primary site.
l If the Network Management System Maintenance Suite
Suite server are on different computers, enter only the
application IP address on the primary site.
Port Specifies the port number. The default value is 12212.
User Name Specifies the user name. The default value is admin.
Password The initial password of the admin user is Changeme_123 (It

is Admin_123 for a U2000 that comes preinstalled). The
password must be changed during the first login to ensure
system security. Keep the password confidential and change
it regularly.
4. Click Login to access the Network Management System Maintenance Suite

window.
NOTE
When you log in to the MSuite client, a progress bar showing the progress of querying subsystems
is displayed. Wait until the operation is complete.
5. Choose Deploy > Synchronize Primary and Secondary Sites.
6. Enter the system IP address and the MSuite password of the remote site, and click
OK. And then click OK in the dialog box that is displayed. A progress bar is displayed,
indicating the progress of synchronizing the primary and secondary sites. It takes about
30 minutes to complete the process. Wait patiently until the dialog box indicating the
successful of synchronizing the primary and secondary sites is displayed.
NOTE
If the primary and secondary sites synchronization fails, click Details. If a message is displayed
indicating a problem like heartbeat IP address unavailability, check the heartbeat network. For
details, see A.7.11 How to Troubleshoot the Heartbeat IP Address Unavailability That
Causes the Primary and secondary sites Synchronization Failure.

7. Click OK. Wait patiently until the dialog box shown in the following figure is
displayed.
NOTE
l The duration of data replication depends on the stability of the network bandwidth and the
volume of the data to be replicated.
l In the lower-left corner of the MSuite, refresh the data replication status of the primary and
secondary sites. If the MSuite prompts Replication status: Finished., data replication is
complete.
l If the status keeps Replication status: 99% remain for a long time, see A.7.1 How to
Solve the Problem Where the Amount of Remaining Data Keeps 99% During Data
Synchronization in a High Availability System to solve the problem. Then use the MSuite
to check the replication status.
l Mode 2: Connect the primary and secondary sites in CLI mode.

1. Ensure that the primary and secondary sites on the MSuite server have been started.
For details, see Step 1 in mode 1.
2. Log in to the OS of the primary site as the ossuser user and run the following
commands:
$ ./startclient.sh deploy -ip 127.0.0.1 -port 12212 -username admin
buildHA -secondaryip System IP address of the peer site
Enter the MSuite login password[]:
Enter the remote node maintenance suite password[]:
3. On the primary site, check data replication status as the root user.
# vradmin -g datadg repstatus datarvg
NOTE
To save time, running the preceding command every half an hour is recommended to check
the data replication status.

Replicated Data Set: datarvg
Primary:
Host name: 129.9.1.1
RVG name: datarvg

DG name: datadg
RVG state: enabled for I/O
Data volumes: 1
VSets: 0
SRL name: srl
SRL size: 100.00 G
Total secondaries: 1
Secondary:
RVG name: datarvg
DG name: datadg
Data status: consistent, up-to-date
Replication status: replicating (connected)
Current mode: asynchronous
Logging to: SRL
Timestamp Information: behind by 0h 0m 0s
NOTE
l If Replication status is displayed as resync in progress (autosync), Data status is

displayed as inconsistent, and the value of Logging to is becoming smaller, data is being
duplicated between primary and secondary sites.
l If Replication status is displayed as replicating (connected) and Data status is displayed
as consistent, up-to-date, data duplication of the high availability system (Veritas hot
standby) is complete.
l If Replication status is displayed as logging to DCM (needs dcm resynchronization),
you must run the vradmin -g datadg resync datarvg command on the primary site as the
root user to perform manual synchronization.
----End
3.9 Loading or Updating a License File

This topic describes how to load or update a license file. After a U2000 is installed, it is
recommended that you update the Veritas license file and load the U2000 license file in time.
You can update the Veritas license before loading the U2000 license file or vice versa.
3.9.1 Loading a U2000 License

This topic describes how to load a U2000 license. Before using a U2000, you must load a
U2000 license.
Prerequisites
l The U2000 license file must be ready.
NOTICE
The license file name can contain digits, letters, and special characters excluding the space
or \ /:*?"<>|.

l Ensure that the primary and secondary sites have been connected and data has been
synchronized between the primary and secondary sites.
Context
The U2000 license only need to be loaded on the primary site. It will be synchronized to the
secondary site automatically after the U2000 license has been loaded on the primary site.
Two methods are available for loading a U2000 license.

l Method one:
Use commands to load the license. This method is applicable to users who cannot log in to
GUI OSs.
Deployment scenario: The GUI is unavailable. Users cannot log in to the U2000 client but
have to use commands for remote operations.
l Method two:
Load the license in the GUI (recommended).
Deployment scenario: Loading the license in the GUI is recommended. If the GUI is
available and the login to the U2000 client is successful, use this method.
NOTE
l You can select a method as required. No matter which method is selected, ensure that the U2000 server
process has been started.
l During installation of the U2000 software, the OS user ossuser is created automatically. The ossuser
user is used to regularly maintain a U2000.
Procedure
Step 1 Log in to the OS as the ossuser user.
Step 2 On the primary site, do as follows to start U2000 processes:

NOTE
By default, the U2000 starts along with the OS.
GUI mode:
1. Run the following command to start the VCS client:

$ hagui&
2. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.

NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information
list in the Cluster Monitor window.
3. Enter the IP address for the Heartbeat network service of the primary site. Then, click
OK.
4. Enter the user name and password for VCS login.

NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure system
security, change the default password in time. If the default password has been changed, enter the
new password.
5. Right-click AppService in the navigation tree and choose Online > host_name from the
shortcut menu.
6. In the dialog box that is displayed, click Yes.
If all resources, including NMSServer, BackupServer, DatabaseServer, mountRes,
RVGPrimary, APPBOND are in the Online on Primaster state, the U2000 server is started
successfully.
CLI mode:
$ su - root
Password: root user password
# hagrp -online AppService -sys hostname
NOTE
hostname specifies the server name. You can run the hostname command to view the server name.
Step 3 On the primary and secondary sites, check whether a license file already exists in the license
path. If a license file already exists, back it up.
$ su - root
# cd /opt/oss/server/etc/conf/license
# ls
If the folder contains any other license file, run the following commands to back up the any other
license file to the /opt/oss/server/etc/conf/license_backup path.

# mkdir -p /opt/oss/server/etc/conf/license_backup
# cd /opt/oss/server/etc/conf/license
# cp license_file_name /opt/oss/server/etc/conf/license_backup
Step 4 On the primary site, load the U2000 license.

NOTE
To make both the U2000 commercial and temporary licenses take effect, use the GUI mode.
Method one: Load the license in the GUI.
NOTE
The Linux operating system does not support the U2000 client. Therefore, you need to log into the Linux
operating system from the U2000 client where the Windows or Solaris operating system is installed.
1. Log in to the OS where the U2000 client is installed.

l In Windows, log in to the OS as the administrator user.
l In Solaris, log in to the OS as the ossuser user.
2. Save the obtained license to the OS directory of the client.
l If the Windows OS is used, copy the license to the OS.
l If the Solaris OS is used, use SFTP to transfer the license file to the OS as the ossuser
user. For details, see A.6.15 How to Use the FileZilla to Transfer Files by SFTP.
3. On the desktop, double-click U2000 Client. The Login dialog box is displayed.
4. In the Server drop-down list, select the server (server on the primary site) to be logged in
to. Then, set User Name and Password to the valid values, and click Login. The initial
password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes
preinstalled). The password must be changed during the first login to ensure system
security. Keep the password confidential and change it regularly.

NOTE
l If a message indicating that no license is available is displayed when you log in to the U2000
client.
1. In the Confirm dialog box, click Yes. The Open dialog box will be displayed.
2. In the Open dialog box that is displayed, select the new license file and click Open. The
License Comparison Results dialog box will be displayed.
3. Click OK.
4. Click Yes and confirm the loaded license.
5. Click OK.
l If U2000 license is loaded before.
1. Choose Help > License Management > License Information from the main menu
(traditional style); alternatively, double-click System Management in Application
Center and choose License Management > Licenes Information from the main menu
(application style).
2. In the License Information dialog box, click Update License.
3. Select the new license file and click Open.
4. Click Next.
5. Select a scenario and perform the associated operations as required:
l If Incremental is unavailable, click Next.
l If Incremental is available and only the new U2000 license needs to be effective, select
Full and click Next.
l If Incremental is available and both the new and in-use U2000 licenses need to be
effective, select Incremental and click Next. If the in-use U2000 license has a
commercial license and a temporary license, the new license will replace the license of
the same type. For example, if the new license is a commercial license, the commercial
license in the in-use U2000 license will be replaced.
6. Click Finish.
7. Click Yes and confirm the updated license.
8. Click Yes to close all windows.
9. Click Yes to log out of the system.
Method two: Use commands to load the license.
1. Send the license file to the U2000 installation path /export/home/ossuser of the primary
site by SFTP as the ossuser user. For details, see A.6.15 How to Use the FileZilla to
Transfer Files by SFTP.
NOTE
You must upload the U2000 license file as the ossuser user. Otherwise, the ossuser user may not
have the read permission and therefore the license fails to be updated.
2. Do as follow to make the license take effect:
a. log in to the OS of the U2000 server as the ossuser user on the primary site.
b. To update the U2000 license file, run the following commands:
$ cd /export/home/ossuser
$ updateLicense -file License_file_name

state product feature item name old
value new value
no change: U2000 COMMON LSW1CAPA01 Client
500 500
no change: U2000 COMMON LSW1CAPA01 Client

1 1
no change: U2000 COMMON LSW1FMCLT01 Alarm Export
1 1
no change: U2000 COMMON LSW1RENOTI01 Client
1 1
Are you sure to update the license?(Y/N)
c. Enter Y, and then press Enter.
----End
Result
After the preceding operations are performed, the license file is automatically loaded to the /opt/
oss/server/etc/conf/license path.
3.9.2 Updating a Veritas License

This topic describes how to update a Veritas License. The Veritas License used in the NMS
installation is a demo License. After the server is delivered to the installation site, the demo
License must be replaced with the formal Veritas License in time.
Prerequisites
The formal Veritas License must be obtained.
Context
NOTE
You need to replace the demo licenses on the NMS servers at both the primary and secondary sites with formal
Veritas licenses. Replace the Veritas licenses at the secondary site, perform a primary/secondary switchover,
and then replace the Veritas licenses at the primary site.
Procedure
l Through the GUI:
started:
NOTE
...

NOTE
# ./startserver.sh
2. Log in to the MSuite client.

3. Choose Deploy > Update VRTS Licenses.
4. In the Update VRTS Licenses dialog box, enter the new licenses.
NOTE
The licenses that are newly applied for include VRTS STORAGE FOUNDATION, VRTS
REPLICATOR and VRTS CLUSTER SERVER.
5. Click OK.
NOTE
A message asking you to restart the OS and indicating that the Veritas licenses must be updated at
both the primary and secondary sites is displayed.
6. Click OK. To restart the OS, run the following commands:
# hastart -onenode
# hagrp -offline AppService -sys hostname
# cd /opt/VRTSvcs/bin
# hastop -local -force
# shutdown -r now
7. After the secondary site is restarted, perform a primary/secondary switchover, and

repeat the preceding operations at the primary site to replace the Veritas licenses at
the primary site.
8. Perform a primary/secondary switchover to restore the normal primary/secondary
relationship.
l Through the CLI:
1. Log in to the OS as the root user.
2. To back up all the License files in the /etc/vx/licenses/lic path, run the following
commands:
# mkdir /export/home/licenses
# mv /etc/vx/licenses/lic/*.vxlic /export/home/licenses
3. Run the following commands to switch to the directory where the vxlicinst file is
stored.
# cd /opt/VRTS/bin
4. Run the following commands to clear the temporary license:

# ./vxkeyless set NONE
5. Run the following commands to update the VxVM License.

# ./vxlicinst
The following information is displayed:
Symantec License Manager vxlicinst utility version 3.02.33.0
Copyright (C) 1996-2007 Symantec Corporation. All rights reserved.
Enter your license key :

6. Enter the new License key of VRTS STORAGE FOUNDATION. The new License
key is in the format of XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-
XXXX-X. Then, press Enter.
NOTE
l X indicates a letter or digit of a License key.

l The information about the demo or formal License that is newly obtained is contained in
the License file.
l The new Licenses include VRTS STORAGE FOUNDATION, VRTS REPLICATOR and
VRTS CLUSTER SERVER.
7. Repeat Step 5, and then enter the new License key of VRTS REPLICATOR.
8. Repeat Step 5, and then enter the new License key of VRTS CLUSTER SERVER.
9. Check whether the updated License takes effect. For details, see A.4.1.2 How to
Check the Veritas License.
10. Run the following command to change the permission of the license file:
# chmod -R 640 /etc/vx/licenses/lic
11. To restart the OS, run the following commands:

# hastart -onenode
# shutdown -r now
12. After the secondary site is restarted, perform a primary/secondary switchover, and
repeat the preceding operations at the primary site to replace the Veritas licenses at
the primary site.
13. Perform a primary/secondary switchover to restore the normal primary/secondary
relationship.
----End
3.10 Checking System Installation

This topic describes how to check the installation of a high availability system (SUSE Linux,
PC Server).
Context
During installation of the U2000 software, the OS user ossuser is created automatically. The
ossuser user is used to regularly maintain a U2000.
Procedure
Step 1 Log in to the OSs of the servers on the primary and secondary sites as the root user.
Step 2 Optional: To check whether disk arrays are properly mounted, run the following command:
NOTE
If no disk array has been configured, skip this step.
# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 50G 583M 47G 2% /
udev 7.9G 200K 7.9G 1% /dev
/dev/sda8 20G 173M 19G 1% /export/home
/dev/sda7 119G 9.7G 103G 9% /opt
/dev/sda5 20G 2.4G 17G 13% /usr
/dev/sda6 20G 290M 19G 2% /var
tmpfs 8.0G 92K 8.0G 1% /dev/shm
tmpfs 4.0K 0 4.0K 0% /dev/vx
/dev/vx/dsk/datadg/lvdatabase
148G 5.9G 135G 5% /opt/sybase
/dev/vx/dsk/datadg/lv_backup
394G 199M 374G 1% /opt/backup
/dev/vx/dsk/datadg/lvapp
197G 7.9G 179G 5% /opt/oss
/dev/vx/dsk/datadg/lvdata
89G 29G 56G 34% /opt/sybase/data
Pay attention to the lines that contain datadg.

l If the values of Mounted on for the lines that contain datadg are the same as the preceding
command output, disk arrays are properly mounted.
l If the values of Mounted on for the lines that contain datadg are different from the preceding
command output, disk arrays are not properly mounted. Contact Huawei engineers to locate
the fault.
Step 3 To check the disk group status, run the following command:
# vxdg list

NAME STATE ID
datadg enabled 1333617787.6.linux
l If the value of STATE is enabled, the disk group status is correct.

l If the value of STATE is not enabled, the disk group does not function properly. Contact
Huawei engineers to locate the fault.
Step 4 To check the disk status, run the following command:
# vxdisk list

DEVICE TYPE DISK GROUP STATUS
sda auto:none - - online invalid
sdb auto:sliced disk02 datadg online
sdc auto:sliced disk03 datadg online
l If the value of STATE of sda is online invalid and the values of STATE of sdb and sdc are
online, the disk group status is correct.
l If the value of STATE is not enabled, the disk group does not function properly. Contact
Huawei engineers to locate the fault.
Step 5 To check the disk volume status, run the following command:
# vxprint -v

Disk group: datadg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0

v lv_backup fsgen ENABLED 838860800 - ACTIVE - -
v lvdata datarvg ENABLED 209715200 - ACTIVE - -
v srl datarvg ENABLED 209715200 SRL ACTIVE - -

Reference Standards
l KSTATE must be ENABLED for all disk volumes.
l STATE must be ACTIVE for all disk volumes.
If disk volume status does not meet the preceding requirements, run the following command to
record details about all disk volumes, and contact Huawei local office or customer service center
in time according to warranty information.
# vxprint -l disk_volume_name
Step 6 To check whether the replication between the primary and secondary sites is normal, run the
following command on the primary site:

Primary:
RVG name: datarvg
DG name: datadg
Data volumes: 1
VSets: 0
SRL name: srl
SRL size: 100.00 G
Secondary:
RVG name: datarvg
DG name: datadg
Logging to: SRL
NOTE
l If Replication status is displayed as resync in progress (autosync), Data status is displayed as

inconsistent, and the value of Logging to is becoming smaller, data is being duplicated between
primary and secondary sites.
l If Replication status is displayed as replicating (connected) and Data status is displayed as
consistent, up-to-date, data duplication of the high availability system (Veritas hot standby) is
complete.
l If Replication status is displayed as logging to DCM (needs dcm resynchronization), you must run
the vradmin -g datadg resync datarvg command on the primary site as the root user to perform
manual synchronization.
l The duration of data replication depends on the stability of the network bandwidth and the volume of
the data to be replicated.
Step 7 Check the shortcut icons.
The following shortcut icons are displayed on the desktop:
l U2000 NMS Maintenance Suite

l U2000 System Monitor
Step 8 Start a System Monitor client to view the running status of each process.
1. On the desktop of the OS, double-click the U2000 System Monitor shortcut icon.

2. In the dialog box that is displayed, enter the U2000 user name and password (The initial
password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes
preinstalled). The password must be changed during the first login to ensure system
security. Keep the password confidential and change it regularly.), to open the System
Monitor window.
NOTE
Two data transmission modes are available: Common and Security(SSL) (more secure,
recommended). The default data transmission mode is Security(SSL). Security(SSL) is
recommended for the high security requirements. You can run a command on the server to query the
data transmission mode.
For details about how to set the communication mode, see A.6.12 How to Set the Communication
Mode of the Server in a High Availability System (Solaris, SUSE Linux).
The U2000 is functioning properly if it can initiate in automatic startup mode, indicating
that the U2000 is functioning properly.
If a process cannot start, right-click the process and choose Start the Service from the
shortcut menu.
If the U2000 works improperly, contact Huawei engineers.
Step 9 Check the installation path.
After the U2000 server software is installed, check the following directories. Note that these
directories cannot be deleted, and the U2000 server software cannot be used properly.
l /opt/oss/engr
l /opt/oss/OSSJRE
l /opt/oss
l /opt/sybase
l /opt/oss/engr/OSSApp
l /etc/ICMR
l /var/ICMR
Step 10 To check the U2000 version, run the following commands:
$ cd /opt/oss/engr/install/etc/conf
$ cat MacroFileNW.properties

...
@{U2000Product_Server_VersionName}=V200R014C50SPCxxx
...
The preceding displayed information shows the U2000 version. If the version does not meet the
actual requirement, uninstall the U2000 and obtain the correct software version to reinstall the
U2000.
----End
Follow-up Procedure
l To save the server disk space, log in to the OSs of the servers on the primary and secondary
sites as the root user and run the following commands to delete software packages in
the /opt/install and /opt/vrtstmp directories.

# rm -r /opt/vrtstmp
# cd /opt/install
# rm Name_of_software_package.tar
# rm Name_of_software_package.7z
For example:
rm U2000version_server_db_linux_sybase.tar
rm U2000version_server_icmr_sles_x64.7z
NOTICE
After installation, do not change the installation directory. If the installation directory is
changed, the U2000 fails to work properly or uninstalled.
l If the login to the U2000 client fails, see A.7.5 Failure to Log In to the U2000 Server
from a U2000 Client.
l After the U2000 is installed, check whether the NBI receives messages properly.
l Before synchronizing the primary and secondary sites, start the NMS to manage NEs. For
details about how to start the NMS, see A.4.2.9 How to Start/Stop the NMS Before
Synchronizing the Primary and Secondary Sites (Solaris, PC Linux).

Server) 4 Separating the Primary Site from the Secondary Site
4 Separating the Primary Site from the

Secondary Site
This topic describes how to separate the primary site from the secondary site. Separating the
primary site from the secondary site refers to disconnecting the primary site and the secondary
site.
Prerequisites
l Ensure the installation directory has enough available space. In the Solaris or SUSE Linux
OS, you can run the df -hk /opt command to view the remaining space of the /opt directory.
l On Solaris or SUSE Linux OS, you must ensure that the U2000 and the database have been
shut down.
NOTE
In the VCS client at the primary site, choose AppService from the navigation tree. If the value of
State for the active site is Offline in the Group Status on Member Systems area on the Status tab
page, and the value of Status is Offline on primary in the Resource Status area, the U2000 and
database are shut down. Otherwise, in the Cluster Explorer window, select the AppService resource
group in the navigation tree, right-click, and choose Offline > host name from the shortcut menu to
stop the Sybase process and U2000 server processes.
l No data duplication between the primary or secondary site in the high availability system.
On the primary or secondary site, run the following command to check the system status:
If Replication status is displayed as replicating (connected) and Data status is displayed

l If separation operations need to be performed only on the primary site, ensure that the
MSuite server on the primary site has started and starting the MSuite server on the secondary
site is not required, and vice versa.
Context
If either the primary or secondary site needs to be restored as an independent one, start the
MSuite server only on the involved site and then perform the separation operation.
The following procedure uses the primary site as example.

Procedure
l Mode 1 (recommended): Separate the primary site from secondary site in GUI mode.
1. Ensure that the MSuite servers have been started.
started:
NOTE
...
NOTE
# ./startserver.sh
NOTE
following commands:
$ ./startclient.sh

Parameter Settings


it regularly.

window.
NOTE
5. Choose Deploy > Separate Primary Site from Secondary Site. The Warning dialog
box is displayed.
6. Click Yes. Then click Yes in the Warning dialog boxes displayed. The progress bar
is displayed indicating the status of separating the primary and secondary sites. Wait
until the dialog box is displayed indicating that the separation is complete.
7. Click OK.
l Mode 2: Separate the primary site from secondary site in CLI mode.
1. Ensure that the MSuite servers have been started. For details, see Step 1 in mode 1.
commands:

splitHA
NOTE
l The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000
that comes preinstalled). The password must be changed during the first login to ensure
system security. Keep the password confidential and change it regularly.
l Perform the following operations as prompted.
Reference standard
Run the vradmin -g datadg repstatus datarvg command as user root to check whether
the data replication relationship has been deleted.
If the information only about one site (similar to the following) is displayed, the data
replication relationship between the primary and secondary sites has been deleted, and the
primary and secondary sites have been separated.
Primary:
Host name: 192.168.1.10
RVG name: datarvg
DG name: datadg
Data volumes: 1
VSets: 0
SRL name: srl_vol
SRL size: 1.00 G
----End
Follow-up Procedure
To re-establish the high availability system, you must perform synchronization between the
primary and secondary sites. For details, see 3.8 Connecting the Primary and Secondary
Sites.

Server) 5 Commissioning the U2000
5 Commissioning the U2000
About This Chapter
This topic describes how to commission the U2000. Usually, the server delivered by Huawei
has been preinstalled, the primary and secondary sites have been separated, and you do not need
to reinstall the U2000 on the server. You can directly commission the U2000 and modify the
system and U2000 parameters according to on-site requirements to allow for the normal use of
the U2000.If the server has not been preinstalled by Huawei, install the U2000 and commission
the system. To allow the U2000 to manage the network, you must commission the U2000 before
using the U2000 to manage NEs and configuring services.
5.1 Commissioning Preparation

This topic describes the preparations for the commissioning of the U2000.
5.2 Performing Commissioning

This topic describes how to commission the U2000 and system parameters. If the system has
been preinstalled, perform U2000 commissioning only.

5.1 Commissioning Preparation

This topic describes the preparations for the commissioning of the U2000.
5.1.1 Obtaining Commissioning Parameters

Planning commissioning parameters is a prerequisite to U2000 commissioning. For details about
the method of planning commissioning parameters, see the associated section in U2000 Planning
Guide and fill in the commissioning parameter table.
System Commissioning Parameters
Table 5-1 System commissioning parameters
Item Parameter Planning Method Remarks
For details, see -

section IP Address
Planning for a
Set
IMM IP address: Remote HA System
Controller
(SUSE Linux, PC
Server) in U2000
Planning Guide.
VRTS STORAGE FOUNDATION: For details, see -

section Applying for
VRTS REPLICATOR: a Veritas License in
U2000 Remote HA
Veritas
System Software
License
Installation and
VRTS CLUSTER SERVER: Commissioning
Guide (SUSE Linux,
PC Server).
l If only
For details, see the time
section Time and zone
Time Zone needs to
Planning in U2000 be
Planning Guide. modified
l Time zone: Set , restart
Set Date
Time Zone: this parameter to the
Time Zone
the local time operatin
zone, such as g system
Asia/Beijing. after the
l Date Time: Set modifica
this parameter to tion so
the local time. that the
time is

automati
cally
adjusted
based on
the new
time
zone.
l If the
time
zone and
time both
need to
be
changed,
change
the time
first and
then the
time
zone.
After the
operatin
g system
Date Time: is
restarted,
the new
time is
automati
cally
adjusted
based on
the new
time
zone.

Old New After

OS user root Passwo Password security
rd: : hardening is
enabled, you
Old New cannot use
OS NMS user
Passwo Password the
ossuser
rd: : commissioni
Old New ng tool to
OS user change the
Passwo Password
dbuser OS user
rd: :
password.
Old New For details
Database
Passwo Password about the
administrator
rd: : For details, see method of
section U2000 changing a
NMS Old New Server User password,
Set Password Database user Passwo Password Password Planning see section
dbuser rd: : in U2000 Planning How to
Network Guide. Change the
Management OS User
Old New Password in
System
Passwo Password U2000
Maintenance
rd: : Remote HA
Suite user
admin System
Software
Installation
and
Old New Commission
VCS Client
Passwo Password ing Guide
User admin
rd: : (SUSE
Linux, PC
Server).
For details, see

section OS Security
Security Whether to enable security
Hardening -
Hardening hardening
Planning in U2000
Planning Guide.
Configuring
NTP server IP
the server as
address:
an NTP client
For details, see Select one
Configuring section NTP Service from the
Set NTP the server as Planning in U2000 three
the Upper-layer NTP Planning Guide. parameters.
intermediate- server IP address:
level NTP
time server

Configuring
the server as
the highest- -
level NTP
time server
Route network segment 1

For details, see
Route network segment 2 section Route
Set Route -
... Planning in U2000
Planning Guide.
Route network segment N
Networ
k card
(Logic
al IP Other
networ Address: parameters
k Netmask use default
interfa values.
ces NOTE
Four-NIC name): You can
select a
Scheme Networ networking
k card For details, see solution
(Logic section IP Address only when
the four-
al IP Planning for a
NIC scheme
Set Network networ Address: Remote HA System is used. If
k Netmask (SUSE Linux, PC the six-NIC
interfa Server) in U2000 scheme is
ces Planning Guide. used, you
name): can modify
only
Networ Logical
k card network
interfaces
(Logic
name, IP
al IP Address,
Six-NIC
networ Address: and
Scheme
k Netmask Netmask.
interfa
ces
name):

Networ
k card
(Logic
al IP
networ Address:
k Netmask
interfa
ces
name):
Networ
k card
(Logic
al IP
networ Address:
k Netmask
interfa
ces
name):
For details, see

Set Host section Host Name
Host Name: -
Name Planning in U2000
Planning Guide.
Access As some of
the domains
may not be
deployed
during
U2000
installation,
you can use
the domain
Deploy - deployment
Transport function to
deploy a
new domain
as needed so
that the
U2000 can
manage NEs
in this
domain.


NOTE
If some
domains are
gray, the
domains
have been
deployed.
IP
Access To disable
the U2000
from
managing
NEs in a
domain,
undeploy the
domain to
improve
system
Undeploy - operation
Transport
efficiency.
Do not select
all the
domains
because
there must
be at least
one domain
deployed.


NOTE
If some
domains are
gray, the
domains
have not
been
deployed.
IP
5.1.2 Checking Hardware Connections

This topic describes how to check hardware installation and cable connections before installing
a U2000. If hardware is improperly installed or cable is improperly connected, unexpected error
may occur during installation of the U2000.
Prerequisites
The server hardware must have been installed and equipment cables must have been connected,
for details, see U2000 Hardware Installation Guide (Huawei N610E cabinet).
Procedure
Step 1 Ensure that the power cables and ground wires for all components are tightly connected and in
good contact and that the polarities are properly placed.
NOTE
Generally, the server has two or more power modules which are used to provide power supply protection.
Connect each power module to a specific power input. For details, see U2000 Hardware Installation Guide
(Huawei N610E cabinet).
Step 2 Ensure that all cables are bundled and free of visible damage.

Step 3 Check hardware connections and network cables according to the hardware connection diagram.
NOTE
The two network cables connecting the primary and secondary sites must be super category 5 cables and
less than 60 meters long.
l Four-network interface Solution: Figure 5-1, Figure 5-2, Figure 5-3, Figure 5-4, Figure
5-5, Figure 5-6 and Figure 5-7 shows hardware connections with four network interfaces.

Figure 5-3 Hardware connection for the Huawei Tecal RH2288H V2 server with four
network interfaces



NOTICE
l The system/application network interfaces are connected using a switch to connect the
primary and secondary sites. As shown in the preceding figure, eth0 functions as the
system/application network interface to connect the primary and secondary sites using a
switch.
l Two interfaces on another NIC are used to configure bond for the heartbeat/replication
and system/application network interfaces. As shown in the preceding figure, eth4 and
eth5 are used to configure bond.
from the NIC on which the heartbeat/replication and system/application network
interfaces reside.
Running SUSE Linux.
l Six-network interface Solution: Figure 5-8, Figure 5-9, Figure 5-10, Figure 5-11, Figure
5-12, Figure 5-13 and Figure 5-14 shows hardware connections with six network interfaces.
network interface used, with the server connecting to no disk array)

network interfaces used, with the server connecting to the disk array OceanStor S3900)
Figure 5-10 Hardware connection for the Huawei Tecal RH2288H V2 server with six
network interfaces



NOTICE
l The system network interfaces are connected using a switch to connect the primary and
secondary sites. As shown in the preceding figure, eth0 functions as the system network
interface to connect the primary and secondary sites using a switch.
l The application network interfaces are connected using a switch to connect the primary
and secondary sites. As shown in the preceding figure, eth2 functions as the application
network interface to connect the primary and secondary sites using a switch.
l Three interfaces on another NIC are used to configure bond for the system, heartbeat/
replication and application network interfaces. As shown in the preceding figure, eth4,
eth5 and eth6 are used to configure bond.
from the NIC on which the heartbeat/replication and system and application network
interfaces reside.
Running SUSE Linux.
Step 4 Check the plugs and sockets.
1. Ensure that the latches of cable plugs are locked fast.

2. Ensure that the pins in each socket are complete and in good order. Curved pins may cause
short circuits.
----End
Follow-up Procedure
Ensure that all debris (cable straps, stubs, or moisture-absorbent packets) are picked up.
Remove unnecessary items from the telecommunications room. The workbench must be neat
and the movable floor must be level and clean.
5.2 Performing Commissioning

This topic describes how to commission the U2000 and system parameters. If the system has
been preinstalled, perform U2000 commissioning only.

5.2.1 Powering On a Server

Server
NOTICE
VAC input voltage.
standby switchover.
NOTE
website.
IBM X3850 X5.

Figure 5-19 Position of the power button on IBM X3850 X5

Disk Array
NOTICE
on.
NOTE
5.2.2 Configuring System Commissioning Parameters

After the U2000 is installed initially, you must use the commissioning tool to adjust system
parameters, such as the IP address and host name. You do not need to modify parameters that
do not require adjustment.
Prerequisites
l A laptop computer or PC is available.
l A network cable is available.
l The remote command login software, such as PuTTY, has been obtained.
l Commissioning parameters have been planned and a commissioning parameter table is
obtained. For details, see 5.1.1 Obtaining Commissioning Parameters.
l The server has been powered on. For details, see 3.2 Powering On a Server.
l The primary and secondary sites have been separated. See 4 Separating the Primary Site
from the Secondary Site.
Context
l For a high availability system running SUSE Linux on a PC server, you must perform the
following operations on both the primary and secondary sites to commission system
parameters:
l The commissioning tool is used only after the initial installation of the U2000 is complete.
Do not use the commissioning tool after the U2000 has running for a period of time. If
system parameters need to be commissioned, see section MSuite in the U2000
Administrator Guide.
Procedure
Step 1 Select the network interface identified as 1 on the server back plane and use a network cable to
connect the network interface to the PC or laptop.

NOTE
During preinstallation, the system IP is configured for network interfaces marked as 1 by default.
Step 2 Modify the IP address and subnet mask of the PC or laptop to be on the same network segment
where the system IP address of the U2000 server is located.
NOTE
The preinstallation by default configures the system IP address as 129.9.1.1 and the subnet mask
as255.255.255.0.
Step 3 On the PC or laptop, use the PuTTY to enable the VNC service for the ossuser user. Log in to
the SUSE Linux GUI desktop as the ossuser user. For details, see Configure the VNC service
as the ossuser user.
Step 4 On the SUSE Linux GUI desktop, right-click and choose Open Terminal from the shortcut
menu. Run the following commands to switch to the root user:
$ su - root
Step 5 Log in to the VCS client of the server. For details, see A.4.2.1 How to Log in and Exit the VCS
(Veritas Cluster Server).
Step 6 On a VCS client, choose AppService > Resources. Ensure that the NMSServer resource of the
server is in the offline state and other resources are in the online state.
NOTE
l Resources whose icons are grayed out are in the offline state. For example, the NMSServer resource
in the Figure 5-20. Resources whose resource icons are not grayed out are in the online state. For
example, the BackupServer resource in the Figure 5-20.
l Check the status of all resources and ensure that the NMSServer resource is in the offline state and
other resources are in the online state. If the state is wrong, make the AppService resource group online,
then make the NMSServer resource offline only after all resources are online.
l To make a resource online, right-click the AppService resource group and choose online >
hostname from the shortcut menu. In the Question dialog box, click Yes.
l To make a resource offline, right-click the NMSServer resource and choose offline > hostname from
the shortcut menu. In the Question dialog box, click Yes.
l The resources of the high availability system varies according to the network configuration solution;
therefore, the elements displayed on the resource tree vary. The difference can be ignored.

Figure 5-20 resources
Step 7 Close the Cluster Explorer window.
NOTICE
If the configuration changes, click Yes in the Confirmation dialog box when exiting the VCS.
Otherwise, logging in to the VCS fails after the server is restarted.
Step 8 Choose File > Logout to exit the VCS.
NOTE
...
NOTE
been started.

the MSuite servers:
# ./startserver.sh
Step 10 Perform the following operations to log in to the MSuite client:

1. On a computer where the MSuite client is installed, double-click the U2000 NMS
Maintenance Suite shortcut icon on the desktop and then wait about one minute. The
Login dialog box is displayed.
2. Set the login parameters.
l IP Address: Use the default value 127.0.0.1.
l Port: Use the default value 12212.
l User Name: Use the default value admin.
l Password: The initial password of the admin user is Changeme_123 (It is Admin_123
for a U2000 that comes preinstalled). The password must be changed during the first
login to ensure system security. Keep the password confidential and change it regularly.
3. Click Login.
NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of Refresh
Deployment Information. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the
MSuite at one time.
Step 11 Perform the following operations to implement system commissioning:

1. Choose Tools > Commissioning Tool from the MSuite client main menu to access the
Information dialog box.
2. Read the information carefully and click Start to access the system commissioning
window.
Step 12 Configure the commissioning items based on the planned commissioning parameter table. For
details about the commissioning parameters, see 5.1.1 Obtaining Commissioning
Parameters.

NOTICE
l If a message asking you to refer to the associated section in the installation guide is displayed
during system commissioning, the system needs to be manually commissioned.
l The deployment packages on the primary and secondary sites must be the same. Otherwise,
the primary and secondary sites cannot be connected properly.
l The passwords of the database administrator on the primary and secondary sites and the
password of the U2000 database user dbuser must be the same.
In order to enhance the security of the database after the U2000 is installed, the sa user may
be manually disabled and replaced with a customized administrator name, such as
dbadmin.
l After the host name is configured, you cannot come back to modify other configuration.
Otherwise, the commissioning may be abnormal. Configure the host name after other
commission items are configured.
l After security hardening is enabled, you cannot use the commissioning tool to change the
password of the OS user. For details about the method of changing a password, see A.6.14
Step 13 After system parameters are commissioned, run the following commands to restart the OS as
the root user to make the modification take effect:
# hastart -onenode
# shutdown -r now
Step 14 Disconnect the PC or laptop from the U2000 server and then connect the U2000 server to the
network.
----End
5.2.3 Connecting the Primary and Secondary Sites

Prerequisites
l The preceding steps for installing the primary and secondary sites must be complete.
l The MSuite client login password, database administrator password, and database NMS
user password must be the same on the primary and secondary sites.
l The installed components must be the same on the primary and secondary sites.
l The operations on the primary and secondary sites must be the same.
l Ensure that the network between the primary and secondary sites is smooth.
l All VCS clients on the primary and secondary sites must be logged out of.
l MSuite client on the secondary site must be logged out of.

l Ensure that the host names of primary and secondary sites are different.
l Ensure that VVR ports can be connected.
Context
Connect the primary and secondary sites in either of the following modes:
l Mode 1 (recommended): GUI mode. If you are not familiar with common commands of
the SUSE Linux OS, connecting the primary and secondary sites in GUI mode is
recommended.
l Mode 2: CLI mode. If you fail to log in to the OS in GUI mode, using primary and secondary
sites the CLI mode is recommended.
Procedure
l Mode 1 (recommended): Connect the primary and secondary sites in GUI mode.
started:
NOTE
...
NOTE
# ./startserver.sh
NOTE
following commands:

$ ./startclient.sh
Parameter Settings


it regularly.

window.
NOTE
5. Choose Deploy > Synchronize Primary and Secondary Sites.
6. Enter the system IP address and the MSuite password of the remote site, and click
OK. And then click OK in the dialog box that is displayed. A progress bar is displayed,
indicating the progress of synchronizing the primary and secondary sites. It takes about
30 minutes to complete the process. Wait patiently until the dialog box indicating the
successful of synchronizing the primary and secondary sites is displayed.

NOTE
If the primary and secondary sites synchronization fails, click Details. If a message is displayed
indicating a problem like heartbeat IP address unavailability, check the heartbeat network. For
details, see A.7.11 How to Troubleshoot the Heartbeat IP Address Unavailability That
Causes the Primary and secondary sites Synchronization Failure.
7. Click OK. Wait patiently until the dialog box shown in the following figure is
displayed.
NOTE
l In the lower-left corner of the MSuite, refresh the data replication status of the primary and
secondary sites. If the MSuite prompts Replication status: Finished., data replication is
complete.
l If the status keeps Replication status: 99% remain for a long time, see A.7.1 How to
Solve the Problem Where the Amount of Remaining Data Keeps 99% During Data
Synchronization in a High Availability System to solve the problem. Then use the MSuite
to check the replication status.
l Mode 2: Connect the primary and secondary sites in CLI mode.

1. Ensure that the primary and secondary sites on the MSuite server have been started.
For details, see Step 1 in mode 1.
commands:
buildHA -secondaryip System IP address of the peer site
Enter the remote node maintenance suite password[]:
3. On the primary site, check data replication status as the root user.
NOTE
To save time, running the preceding command every half an hour is recommended to check
the data replication status.


Primary:
RVG name: datarvg
DG name: datadg
Data volumes: 1
VSets: 0
SRL name: srl
SRL size: 100.00 G
Secondary:
RVG name: datarvg
DG name: datadg
Logging to: SRL
NOTE
l If Replication status is displayed as resync in progress (autosync), Data status is

displayed as inconsistent, and the value of Logging to is becoming smaller, data is being
duplicated between primary and secondary sites.
l If Replication status is displayed as replicating (connected) and Data status is displayed
l If Replication status is displayed as logging to DCM (needs dcm resynchronization),
you must run the vradmin -g datadg resync datarvg command on the primary site as the
root user to perform manual synchronization.
----End
5.2.4 Commissioning U2000 Parameters

This topic describes how to commission U2000 Client parameters after the U2000 is installed.
Prerequisites
l If the delivered server has been preinstalled, ensure that system commissioning is complete.
For details, see 5.2.2 Configuring System Commissioning Parameters.
l If the delivered server has not been preinstalled, ensure that the U2000 is installed. For
details, see 3 Installing the U2000.
l Ensure that the U2000 license has been loaded. For details, see 3.9.1 Loading a U2000
License.
l The remote command login software, such as PuTTY, has been obtained.
NOTE
The standard resolution of 1024 x 768 is recommended. Otherwise, the U2000 client page may not be
displayed completely. If the page contains a lot of contents, use a higher resolution with the same ratio,
such as 1152 x 864.

Context
The U2000 commissioning parameters cover communication security, U2000 user security
policy, communication between the U2000 and NEs, alarm function, and common U2000
configurations.
Procedure
Step 1 Use the PuTTY to enable the VNC service for the ossuser user. Log in to the primary site GUI
desktop as the ossuser user. For details, see Configure the VNC service as the ossuser user.
Step 2 On the GUI desktop, right-click and choose Open Terminal from the shortcut menu.
Step 3 Run the following command to check whether the U2000 is started:
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
ossuser 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start
ossuser 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start
ossuser 27086 1 0 10:31:39 ? 0:09 imapeventmgr
ossuser 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start
ossuser 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start
NOTE
If the command output contains imap_sysmonitor -cmd start, the U2000 is started.
Step 4 If the U2000 process is not started, run the following commands to start it:
$ hagrp -online AppService -sys hostname
Enter the user name and password of the VCS client.
NOTE
Step 5 Log in to U2000 client.

1. Log in to the OS where the client program is installed.
l In Windows, log in to the OS as a user with the administrator rights.
l In Solaris, log in to the OS as the ossuser user.
2. On the OS desktop, double-click the U2000 Client shortcut icon. The Login dialog box is
displayed.
3. In the Server drop-down list, select the server to be logged in to. Then, set User Name and
Password to the valid values, and click Login. The initial password of the admin user is
Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password
must be changed during the first login to ensure system security. Keep the password
confidential and change it regularly.
Step 6 Perform the following operations to change the display style to the traditional style for the client:
1. Choose File > Preferences from the U2000 Client main menu.
2. Choose Client Display Style from the navigation tree on the Preferences page.
3. Select Traditional style and click OK.
4. Re-log in to the U2000 client.

Step 7 Choose Administration > NMS Commissioning Wizard from the U2000 Client main menu.
Step 8 Commission U2000 parameters as prompted.
----End
Result
After U2000 parameters are commissioned, the U2000 and NEs can communicate with each
other properly, and the U2000 works properly.

Server) A FAQs
A FAQs
This topic provides answers to the most frequent questions concerning the installation.
A.1 SUSE Linux OS

This topic provides the FAQs occurred in the SUSE Linux OS.
A.2 System Settings of the Huawei RH series rack server

This topic covers FAQs about Huawei RH series rack server system settings.
A.3 System Settings of the IBM Server

This topic covers FAQs about IBM Server system settings.
A.4 Veritas HA System

This topic covers FAQs about the Veritas HA system.
A.5 Sybase Database

This topic covers FAQs about the Sybase database.
A.6 U2000 System

This topic covers FAQs about the U2000 system.
A.7 Install the U2000 Software Exception Processing

This topic describes how to uninstall the U2000 software. Before reinstalling the U2000
software, you must uninstall U2000. After the primary and secondary sites are separated in a
high availability system, the servers on the primary and secondary sites are working as two
separate single-server systems. Uninstall the U2000 and check the uninstallation separately.

Server) A FAQs
A.1 SUSE Linux OS

This topic provides the FAQs occurred in the SUSE Linux OS.
A.1.1 How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE

Linux OS
Question
How do I start/stop the FTP/SFTP/Telnet service in the SUSE Linux OS?
NOTE
Using SFTP is recommended, operations in this topic applies to the following scenarios:
l See operations in this topic on the U2000 server when files, such as the installation package and license
file, need to be uploaded to the U2000 server during U2000 installation.
l See operations in this topic on the SUSE Linux server before U2000 data is backed up or restored.
Answer
Step 1 Use the remote login software such as PuTTY to log in to the OS by means of SSH as the
root user.
NOTE
If the SetSuse policy has been enabled, you can log in to the OS only by means of SSH. Because after the
SetSuse policy has been enabled, only the SSH service for the ossuser user has the login right. The PuTTY
is recommended.
Run the following command to switch to the root user:
$ su - root
Enter a login password for the root user.
Step 2 Start and stop the FTP/SFTP (more secure, recommended)/Telnet service.
l Starting and stopping the FTP service:
– NMS is not installed, do as the following:
– Run the following command to start the FTP service:
# service vsftpd start
– Run the following command to stop the FTP service:

# service vsftpd stop
– NMS is installed, do as the following:

– Run the following command to start the FTP service:
# /usr/sbin/ftpd &
NOTE
If the command output contains # 500 OOPS: could not bind listening IPv4 socket, the FTP
service is enabled. Press Enter to exit.
– Run the following command to stop the FTP service:
# ps -ef | grep /usr/sbin/ftpd | grep -v grep | awk '{print $2}' | xargs
kill -9
l Starting and stopping the SFTP (more secure, recommended) service:

Server) A FAQs
– Run the following command to start the SFTP (more secure, recommended) service:
# vi /etc/ssh/sshd_config
– If PAMAuthenticationViaKBDInt yes is displayed, add # to the beginning of it to

change it to #PAMAuthenticationViaKBDInt yes.
– Ensure that the value of PasswordAuthentication is yes. That is,
PasswordAuthentication yes is displayed and # does not appear in front of it.
– Ensure that # is displayed in front of UsePAM yes. That is, #UsePAM yes is
displayed.
Run the :wq! command, save the settings, and exit.
# service sshd restart
– Run the following command to stop the SFTP service:

# service sshd stop
l Starting and stopping the Telnet service:

– Run the following command to start the Telnet service:
# chkconfig telnet on
# /etc/init.d/xinetd restart
– Run the following command to stop the Telnet service:

# chkconfig telnet off
# /etc/init.d/xinetd restart
----End
A.1.2 How to Enable and Disable the FTP Authority of the root User
in the SUSE Linux OS
Question
How to enable and disable the FTP authority of the root user in the SUSE Linux OS?
Answer
l The method of enable the FTP authority of the root user is as follow:
1. Log in to the SUSE Linux OS as the root user.
2. Run the vi /etc/ftpusers command to open the ftpusers file in the /etc directory. Add
the comment tag (#) to the beginning of the following line in the ftpusers file to
comment out this line:
root
3. Run the command wq! to save and close the ftpusers file.
l The method of disable the FTP authority of the root user is as follow:
1. Log in to the SUSE Linux OS as the root user.
2. Run the vi /etc/ftpusers command to open the ftpusers file in the /etc directory and
delete the comment tag (#) to the beginning of the following line in the ftpusers file:
root
3. Run the command wq! to save and close the ftpusers file.
----End

Server) A FAQs
A.1.3 How to manually Add the Default Route (SUSE Linux)
Question
How do I add the default route in the SUSE Linux OS?
Answer
Step 1 Log in to the system as user root.
Step 2 Open a terminal window.
Step 3 Run the following command in the CLI:

# vi /etc/sysconfig/network/routes
Step 4 Write the default route configurations into the /etc/sysconfig/network/routes file.
l Format:
default gateway IP address - -
NOTE
gateway IP address: network management IP address for the network on which the U2000 server is
located.
l Example:
default 129.9.1.254 - -
Step 5 Press Esc and run the command :wq to save and close the file.
Step 6 Run the following command to make the route take effect:
# /etc/init.d/network restart
Step 7 Run the netstat -nr command to view the default route of the system.
----End
A.1.4 How to manually Add a Static Route (SUSE Linux)
Question
How do I add a static route in the SUSE Linux OS?
NOTE
If a static route exists and a new static route needs to be added, use the MSuite to add a static route after
the U2000 is installed. Using yast2 to add a static route is prohibited to prevent several-second network
disconnection and service interruption.
Answer
Step 1 Log in to the system as user root.
Step 2 Open a terminal window.
Step 3 Run the following command to view the existing routes in the system:
# netstat -nr
Step 4 Run the following command in the CLI:

Server) A FAQs
# vi /etc/sysconfig/network/routes
Step 5 Write the static route configurations into the /etc/sysconfig/network/routes file.
l Format:
destination network segment address gateway IP address destination network
segment subnet mask
NOTE
l destination network segment address: The network segment of the IP address of the computer
connected to the U2000 server.
l gateway IP address: network management IP address for the network on which the U2000 server
is located.
l destination network segment subnet mask: subnet mask of the network segment on which the
computer connected to the U2000 server is located.
l Example:
128.9.1.0 129.9.1.254 255.255.255.0
Press Esc and run the command :wq to save and close the file.
Step 6 Run the following command to make the route take effect:
# /etc/init.d/network restart
----End
A.1.5 How to Add a Static Route If the U2000 Is Installed
Question
How to add a static route after the U2000 is installed?
NOTE
If a static route exists and a new static route needs to be added, use the MSuite to add a static route after
the U2000 is installed. Using yast2 to add a static route is prohibited to prevent several-second network
disconnection and service interruption.
Answer
Step 1 Log in to the MSuite client.
Step 2 On the MSuite client, click the Server tab.
Step 3 Right-click the target server and choose Configure Route from the shortcut menu. The
Configure Route dialog box is displayed.
Step 4 In the dialog box that is displayed, click Add or Delete according to actual route conditions to
configure the route.

Server) A FAQs
NOTICE
Before adding a route, ensure that the server and the router are directly connected. Otherwise,
the route cannot be added.
For example, the procedure for adding a route from a client (IP address: 10.70.73.77) to a server
(IP address: 10.71.224.12) is as follows, with the IP address of the intermediate router being
10.71.224.1:
1. Ensure that the server and the router are directly connected.
2. Click Add. Set Destination to 10.70.73.0, Subnet Mask to 255.255.255.0, and
Gateway to 10.71.224.1.
Step 5 Click OK.

Step 6 After the configurations are complete, run the netstat -nr command to view route configurations.
----End
A.1.6 How to Check Disk Partitions

Question
How do I check disk partitions?

Server) A FAQs
Answer
l Method one (recommended): Use commands.
1. Log in to the OS as the root user through remote login software.
2. Run the command df -h to check disk partitions.
l Method two: In the GUI.
1. Log in to the GUI of the OS as the root user.
2. Run the following command in the terminal window to open the YaST2 Control
Center window.
# yast2
3. Select System on the left.

4. Select Partitioner on the right.
5. Carefully read the information in the Warning dialog box, and then click Yes.
6. In the Expert Partitioner window, view the disk partition information and check
whether the partitions meet the requirements of the U2000 system software.
----End
A.1.7 How to Monitor System Processes and Application Ports
Question
How to monitor system processes and application ports after the SUSE Linux OS is installed?
Answer
l Choose Computer > More Applications > System > GNOME System Monitor to
manage processes.
l Opens the terminal, use ps -ef | grep process name command to view processes. You can
run the vmstat or top command to view the usage of the CPU, memory, and I/O bus.
A.1.8 How to Enable Remote GUI Logins
Question
What should I do when I fail to log in to the SUSE Linux OS through the remote login tools?
Answer
Step 1 Log in to the SUSE Linux OS as user root through remote login software or the Windows OS
CLI.
Step 2 Run the following command in the terminal window:

# yast remote allow set=yes
# rcxdm restart
Step 3 Use the remote login tools to log in to the U2000 server again.
----End

Server) A FAQs
A.1.9 How to Query the Process Status
Question
How do I query the process status?
Answer
Run the ps -ef | grep process name command to query the process status.
For example, run the ps -ef | grep sysmonitor command to query the status of the
sysmonitor process. The following message will be displayed:
ossuser 17156 17032 0 22:13:59 pts/3 0:00 grep sysmonitor
l imap_sysmonitor indicates information about the process, where 11972 is the process ID.
NOTE
Process information will be displayed if the process is running.

l grep sysmonitor indicates the query operation performed by the user and can be ignored.
A.1.10 How to Use the vi Editor
Question
How do I use the vi editor?
Answer
Run the following command to open the vi editor:
vi file name
l If a file with the same filename exists, run the vi command to open and edit the file.
l If a file with the same filename does not exist, run the vi command to create and edit a file.
The edit commands are as follows:

l The command for opening the vi editor is as follows:
vi file name
l The command for entering the command mode is as follows.
Command Function
ESC Press ESC to exit the text input mode and enter the command
mode.
l The commands for inserting text are as follows (must be run in command mode).
Command Function
a Appends text at the cursor (append).
A Appends text at the end of the line where the cursor locates.

Server) A FAQs
Command Function
i Adds text in front of the cursor (insert).
I Adds text to the front of the first non-null character in the

line where the cursor locates.
o Adds text at the beginning of the next line where the cursor
locates (open).
O Adds text at the beginning of the previous line where the

cursor locates.
l The commands for moving the cursor are as follows (must be run in command mode).
Command Function
h Moves the cursor to the left.
j Moves the cursor downwards.
k Moves the cursor upwards.
l Moves the cursor to the right.
Line number G Moves the cursor to a specified line. For example, 1G moves
the cursor to the first line.
G Moves the cursor to the end of the file.
l The commands for deleting texts are as follows (must be run in command mode).
Command Function
x Deletes the character where the cursor is located.
dd Deletes the line where the cursor is located.
l The commands for quitting the vi editor are as follows and must be run in command mode.
You are recommended to press ESC before running any command listed in Table A-1.
Table A-1 Commands for quitting the vi editor
Command Function
:wq Saves changes and quits the vi editor.
:q Quits the vi editor without saving changes.
:q! Forcibly quits the vi editor without saving changes.
:w Saves changes without quitting the vi editor.

Server) A FAQs
A.1.11 How to Change the Time and Time Zone of the SUSE Linux
OS
Question
How to change the time and time zone of a SUSE Linux OS where the U2000 is not installed
yet?
NOTE
For how to change the time and time zone of a SUSE Linux OS after the U2000 has been installed, see
MSuite > U2000 Deployment > Setting the System Time and Time Zone in the U2000 Administrator
Guide.
Answer
Step 1 Log in to the graphical desktop system of the SUSE Linux OS as the root user.
Step 2 Open the CLI and run the following command to start the YaST2 control center.
# yast2
Step 3 Choose System > Date and Time.
Step 4 In the dialog box that is displayed, set the area and time zone.

Server) A FAQs
Step 5 To change the time, click Change. In the dialog box that is displayed, set the date and time, and
then click Apply.
Step 6 Click Accept.
the system.
# shutdown -r now
----End

Server) A FAQs
A.1.12 How to Use the VNC to Remotely Log In to SUSE Linux by

Retaining the Session
Question
How do I use the VNC to remotely log in to SUSE Linux?
Answer
The virtual network computing (VNC) is a component of SUSE Linux. It is a typical thin client
software. The graphics processor service runs on the server and multiple instances can be created.
l Advantage: A remote computer can access the server using the Internet Explorer. If the
connection is torn down, the desktop can be held by logging in with the same user name
and port number. The remotely run applications will not be interrupted due to the network
disconnection.
l Disadvantage: The shortcut options in the VNC window conflicts with those on the
Windows and applications. As a result, some shortcut options are unavailable in the VNC
window. Table A-2 shows the usage of the commonly seen shortcut options in the VNC
window.
NOTE
l During system preconfiguration, the VNC scripts are generated only after the pre_install.sh command
is executed. Before configuring the VNC service, ensure that the system has been preconfigured.
l Do not use the Java desktop mode to log in to the OS. Using SSH (more secure, recommended)/Telnet
to log in to the OS is recommended. After login succeeds, run the associated commands to start the
VNC service.
l The VNC service is automatically disabled after the OS is restarted to ensure the security of the U2000.
To use the VNC to remotely log in to SUSE Linux, reconfigure the VNC service.
l Configure the VNC service as the root user.
1. Use the PuTTY tool to log in to the server as a root user.
2. Optional: Run the following command as user root to set the password for user
root to log in to the VNC. If the VNC login password for user root already exists or
is known, skip this step.
# vncpasswd
a. Enter the password in Password: as prompted and press Enter.

NOTE
An example password is Admin123. A password must consist of 6 to 8 characters. All

characters entered using the keyboard, except the Enter key, will be considered as
password components. Excessive characters will be automatically discarded. Passwords
must be complex enough to ensure the security of the U2000. For example, a password
must contain six or more characters of two types. The allowed characters are digits,
uppercase and lowercase letters, and special characters. Remember to change passwords
regularly and remember the new password.
b. Enter the password in Verify: as prompted and press Enter.
NOTE
Enter the same password again. The system begins to check whether the passwords are
the same. If so, the password is set successfully. If not, set the password again.
Would you like to enter a view-only password (y/n)?

Server) A FAQs
c. Enter n and press Enter.

NOTE
l Remember the password that will be used for VNC login as user root.
l If the password is forgotten, log in to the OS as user root, run the vncpasswd command,
and set a new password according to the message.
3. Run the following commands to enable the VNC services.
# cd /opt/install/OSSICMR/tools/VNC
# sh start_vnc_root.sh
If the command output contains successfully, the VNC service corresponding to the
root user is started. The port ID is 5802 for the root user.
NOTE
l If the system has been preconfigured, run the sh start_vnc_root.sh command in the /opt/
oss/engr/tools/VNC directory.
l During operations on the GUI, do not close the PuTTY dialog box. Otherwise, the
connection to the VNC client becomes abnormal. If the PuTTY dialog box is closed, refer
to this FAQ to reconfigure the VNC service.
l If a message is displayed asking you to set the password, run the vncpasswd password as
the root user to set the password.
l If information similar to the following is displayed:
The vnc for root is already running and port is 2.
Run the following commands to stop the VNC service and close the port:
# sh stop_vnc_root.sh
# su - ossuser
$ vncserver -kill :2
$ exit
Run command sh start_vnc_root.sh to start the VNC service for the root user.
start vncserver :2 failed
Run the following commands to enable the VNC services.
# vncserver :2
Warning: X3650-SEC1:2 is taken because of /tmp/.X11-unix/X2
Remove this file if there is no X server X3650-SEC1:2
A VNC server is already running as :2
X3650-SEC1 is the server name.
Run ps -o cmd | grep "Xvnc :2" | grep -v grep to check whether the VNC service
corresponding to the root user has started.
l If no information is displayed, the VNC service corresponding to the root user has not
started.
Run cd /tmp. If the .X2-lock file exists, run rm .X2-lock to delete the .X2-lock file.
Run cd /tmp/.X11-unix. If the X2 file exists, run rm X2 to delete the X2 file.
Repeat Step 2 to start the VNC service for the root user.
l If information is displayed, the VNC service corresponding to the root user has started.
4. Perform the following operations to create an SSH tunnel so that the communication
between the server and VNC client is more secure. In the following example, the
PuTTY is saved in the D:\PuTTY path and the server IP address is 129.9.1.1.
a. On a PC or laptop, choose Start > Run. In the dialog box that is displayed, enter
cmd to open a CLI.
b. Run the following command to navigate to the path where the PuTTY is located:

Server) A FAQs
C:\>cd /d D:\PuTTY\
c. Run the following command to create an SSH tunnel for the root user:
D:\PuTTY>putty -L 5902:localhost:5902 -L 5802:localhost:5802 129.9.1.1
NOTE
l Do not replace localhost with an IP address or a host name in the preceding command.
l Establish a connection with the server. In the PuTTY Security Alert dialog box,
click Yes to confirm the connection to the server.
l 129.9.1.1 specifies the server IP address.
d. In the PuTTY dialog box, enter the user name and password of the root user.
The SSH tunnel for the root user is created.
NOTE
l During operations on the GUI, do not close the PuTTY dialog box. Otherwise, the
connection to the VNC client becomes abnormal. If the PuTTY dialog box is closed
or SSH tunnel is disconnected due to an exception, refer to this FAQ to reconfigure
the VNC service.
l If the security hardening policy is enabled on the system, enter the user name and
password of the ossuser user in the PuTTY window to complete the creation of the
SSH tunnel.
5. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5802 in the
address bar. Then press Enter.
6. Enter the password and click OK to access SUSE Linux.
NOTICE
l The VNC cannot be used to connect a PC or laptop to multiple SUSE Linux servers.
If the VNC needs to be used to connect to another server, you must shut down the
server connected to the PuTTY and then refer to the FAQ to reconfigure the VNC
connected to the server. The new VNC connected to the SUSE Linux server
overwrites the previous VNC connected to the SUSE Linux server. To reuse the
previous VNC, refer to this FAQ to reconfigure this VNC.
l After the GUI process is completed, run the following command to shut down the
VNC service in order to ensure security:
# sh stop_vnc_root.sh
If the command output contains successfully, the VNC service corresponding to

the root user is stopped.
l If the VNC needs to be used again, refer to this document to configure the VNC.
l Configure the VNC service as the ossuser user.

1. Use the PuTTY tool to log in to the server as an ossuser user.
2. Optional: Run the following command as user ossuser to set the password for user
ossuser to log in to the VNC. If the VNC login password for user ossuser already
exists or is known, skip this step.
$ vncpasswd
a. Enter the password in Password: as prompted and press Enter.

Server) A FAQs
NOTE
An example password is Admin123. A password must consist of 6 to 8 characters. All

characters entered using the keyboard, except the Enter key, will be considered as
password components. Excessive characters will be automatically discarded. Passwords
must be complex enough to ensure the security of the U2000. For example, a password
must contain six or more characters of two types. The allowed characters are digits,
uppercase and lowercase letters, and special characters. Remember to change passwords
regularly and remember the new password.
b. Enter the password in Verify: as prompted and press Enter.
NOTE
Enter the same password again. The system begins to check whether the passwords are
the same. If so, the password is set successfully. If not, set the password again.
Would you like to enter a view-only password (y/n)?
c. Enter n and press Enter.

NOTE
l Remember the password that will be used for VNC login as user ossuser.
l If the password is forgotten, log in to the OS as user ossuser, run the vncpasswd command,
and set a new password according to the message.
3. Run the following commands to enable the VNC service for the ossuser user.
$ su - root
# cd /opt/oss/engr/tools/VNC
# sh start_vnc_oss.sh
If the command output contains successfully, the VNC service corresponding to the
ossuser user is started. The port ID is 5803 for user ossuser.

Server) A FAQs
NOTE
l If a message is displayed asking you to set the password, run the vncpasswd password as
the ossuser user to set the password.
The vnc for ossuser is already running and port is 3.
Run the following commands to stop the VNC service and close the port:
# sh stop_vnc_oss.sh
# vncserver -kill :3
Run command sh start_vnc_oss.sh to start the VNC service for the ossuser user.
start vncserver :3 failed
Run the following commands to enable the VNC service.
# vncserver :3
Warning: X3650-SEC1:3 is taken because of /tmp/.X11-unix/X3
Remove this file if there is no X server X3650-SEC1:3
A VNC server is already running as :3
X3650-SEC1 is the server name.
Run ps -o cmd | grep "Xvnc :3" | grep -v grep to check whether the VNC service
corresponding to the ossuser user has started.
l If no information is displayed, the VNC service corresponding to the ossuser user has
not started.
Run cd /tmp. If the .X3-lock file exists, run rm .X3-lock to delete the .X3-lock file.
Run cd /tmp/.X11-unix. If the X3 file exists, run rm X3 to delete the X3 file.
Repeat Step 2 to start the VNC service for the ossuser user.
l If information is displayed, the VNC service corresponding to the ossuser user has
started.
4. Perform the following operations to create an SSH tunnel for the ossuser user so that
the communication between the server and VNC client is more secure. In the following
example, the PuTTY is saved in the D:\PuTTY path and the server IP address is
129.9.1.1.
a. On a PC or laptop, choose Start > Run. In the dialog box that is displayed, enter
cmd to open a CLI.
b. Run the following command to navigate to the path where the PuTTY is located:
C:\>cd /d D:\PuTTY\
c. Run the following command to create an SSH tunnel for the ossuser user:
D:\PuTTY>putty -L 5903:localhost:5903 -L 5803:localhost:5803 129.9.1.1
NOTE
l Do not replace localhost with an IP address or a host name in the preceding command.
l Establish a connection with the server. In the PuTTY Security Alert dialog box,
click Yes to confirm the connection to the server.
l 129.9.1.1 specifies the server IP address.
d. In the PuTTY dialog box, enter the user name and password of the ossuser user.
The SSH tunnel for the ossuser user is created.
NOTE
During operations on the GUI, do not close the PuTTY dialog box. Otherwise, the
connection to the VNC client becomes abnormal. If the PuTTY dialog box is closed or
SSH tunnel is disconnected due to an exception, refer to this FAQ to reconfigure the VNC
service.

Server) A FAQs
5. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5803 in the

address bar. Then press Enter.
6. Enter the password and click OK to access SUSE Linux.
NOTICE
l The VNC cannot be used to connect a PC or laptop to multiple SUSE Linux servers.
If the VNC needs to be used to connect to another server, you must shut down the
server connected to the PuTTY and then refer to the FAQ to reconfigure the VNC
connected to the server. The new VNC connected to the SUSE Linux server
overwrites the previous VNC connected to the SUSE Linux server. To reuse the
previous VNC, refer to this FAQ to reconfigure this VNC.
l After the GUI process is completed, run the following command to shut down the
VNC service in order to ensure security:
$ su - root
# sh stop_vnc_oss.sh
If the command output contains successfully, the VNC service corresponding to

the ossuser user is stopped.
l If the VNC needs to be used again, refer to this document to configure the VNC.
If you still cannot use the VNC on a PC or laptop to log in to the server after the VNC is
configured, perform the following operations to locate the fault:
1. Check whether the VNC port is occupied.

For a root user, the VNC port is 5802. For an ossuser user, the VNC port is 5803. For
the U2000 V100R008SPC300 or later, port forwarding must be configured on
Windows. VNC ports may be occupied.
On a PC or laptop running on Windows, if a root user cannot use the VNC to log in
to the server, run the netstat -a |findstr 5802 command to check whether the VNC
port is occupied. If an ossuser user cannot use the VNC to log in to the server, run the
netstat -a |findstr 5803 command to check whether the VNC port is occupied.
The following information is displayed (a root user is used as an example)
TCP 127.0.0.1:5802 SZXY1X001776702:0 LISTENING
If the command output contains 5802 and LISTENING, port 5802 is occupied. For
an osssuer user, check whether the command output contains 5803 and
LISTENING.
If the VNC port is occupied, shut down all in-use VNCs on the current PC or laptop.
Verify that no user is using the VNC on the PC or laptop running on Windows.
2. If the problem persists, close all IE web browsers and restart the IE.
3. If the problem still exists after the IE is restarted, restore the IE to default
configurations, if applicable. To restore the IE to default configurations, choose
Tools > Internet Options > Advanced > Restore Defaults. If the Internet Explorer
cannot be reconfigured, try another browser, PC, or laptop.

Server) A FAQs
Table A-2 Usage of commonly seen shortcut options in the VNC window
Scenar Availabil Shortcut Description

io ity Option/
Operation
Shortcu Unavailabl The Tab key NOTE

t e cannot be used If the Tab key is incorrectly used, no information
can be entered in the CLI. You must click in the
options for the path
CLI before entering information.
on the association
VNC function.
CLI
Available Ctrl + a Start position
Ctrl + e End position
Ctrl + k Deleting all contents from the cursor to the

end
Ctrl + u Deleting all contents from the start to the

cursor
Ctrl + d Deleting a command line. After a common

line is deleted, the CLI will be shut down
Ctrl + l Clearing the screen
Shift + Home Copying characters in the selected area
Shift + Insert Pasting the content in the VNC window
Shortcu Unavailabl Contents outside You can only enter information in the VNC
t e the VNC window or upload it to the VNC window.
options window cannot
for be copied or
operatio pasted into the
ns not VNC window.
on the
VNC The Ctrl + Alt + You can only click the button on the left-
CLI, U combination right corner to unlock a client.
such as cannot be used
operatio to unlock a
ns on client.
the file, Available Alt + F1 Opening the main menu
window
, and Alt + F9 Minimizing the current window
menu
Alt + F10 Maximizing the current window
Ctrl + c Copying the content
Ctrl + v Pasting the content in the VNC window
----End

Server) A FAQs
A.1.13 How to Set IP Addresses for Unused NICs on SUSE Linux
Question
How do I set IP addresses for unused NICs on a workstation after a SUSE Linux OS is installed?
Answer
NOTICE
l Using the Yast2 to set IP addresses is not recommended because intermittent network
disconnection may occur and the NMS may fail to function properly.
l The IP address cannot be located in a network segment on which the IP addresses of some
used network interfaces are located. Otherwise, a network fault occurs.
Step 2 Perform the following operations to query the IP addresses of used network interfaces:
1. Run the following commands to query network interface configurations:

# cd /etc/sysconfig/network
# ls

config ifcfg-eth3 ifcfg.template
dhcp ifcfg-eth-id-34:40:b5:b1:11:08 if-up.d
ifcfg-bond0 ifcfg-lo providers
ifcfg-eth0 ifcfg.template routes
ifcfg-eth1 if-down.d routes.YaST2save
ifcfg-eth2 ifroute-lo scripts
NOTE
l If the command output contains information similar to ifcfg-bond0, bond has been configured
for the network interface. Perform 2.2 to view the IP address of the used network interface.
l If the command output contains information similar to ifcfg-eth-id-34:40:b5:b1:11:08, bond has
not been configured for the network interface. Perform 2.3 to view the IP address of the used
network interface.
2. Optional: If bond has been configured for the network interface, run the following
command to view the IP address of the used network interface:
# cat ifcfg-bond0

BOOTPROTO='static'
BROADCAST='129.9.1.255'
IPADDR='129.9.1.1/24'
NETMASK='255.255.255.0'
STARTMODE='auto'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=1 miimon=100 use_carrier=1'
BONDING_SLAVE0='eth1'
PREFIXLEN='24'

Server) A FAQs
NOTE
The value 129.9.1.1/24 of the IPADDR parameter is the IP address of network interface bond0.
Record the value. If information similar to ifcfg-bond0 is displayed, repeatedly perform 2.2 and
record the IP address.
3. Optional: If bond has not been configured for the network interface, run the following
command to view the IP address of the used network interface:
# cat ifcfg-eth-id-34:40:b5:b1:11:08

BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='129.9.1.2/24'
MTU=''
NETWORK=''
......
NOTE
The value 129.9.1.2/24 of the IPADDR parameter is the IP address of network interface
34:40:b5:b1:11:08. Record the value. If information similar to ifcfg-eth-id-34:40:b5:b1:11:08 is
displayed, repeatedly perform 2.3 and record the IP address.
Step 3 Run the following commands to assign execute rights to the AddIPForSuse.sh file:
# cd /opt/install/OSSICMR/tools
# chmod 750 AddIPForSuse.sh
Step 4 Run the following operation to configure the IP address for the network interfaces that are not
used in the SUSE Linux OS.
Configuring the logical network interface eth2 is used as an example.
1. Run the following command to start the AddIPForSuse.sh script:

# ./AddIPForSuse.sh

The NICs available in the local server are as follows:
-------------------------------------------
1 eth1
2 eth2
3 eth3
-------------------------------------------
Please enter a number to select the system NIC[1-3]:
NOTE
The network interfaces displayed in the preceding command output are not configured.
2. Enter a network interface number. For example eth2, enter 2 and press Enter.
Please input the IP address:
3. Enter an IP address, such as 10.78.225.28, for the network interface eth2. Then press
Enter.
Please input the subnet mask:
NOTE
The IP address cannot be located in the same network segment as a recorded IP address. Otherwise,
a network fault occurs.
4. Enter the subnet mask of the network segment on which the IP address resides, such as
255.255.255.0. Then press Enter.

Server) A FAQs

Please input the hostname:
5. Enter a host name, such as hostname01, for the IP address. The host name must be unique.
Then press Enter.
Configured the NIC successfully.
NOTE
If the preceding information is displayed, the IP address of the eth2 network interface is configured
successfully. To configure IP addresses for other network interfaces, repeat Step 4.
----End
A.1.14 How to Capture Snapshots on SUSE Linux

Question
How do I capture snapshot on SUSE Linux?
Answer
l Method 1: Use the keyboard.
1. Press Print Screen.
2. Rename the file and click Save.
l Method 2: Use commands.

1. In the CLI, run the gnome-panel-screenshot command.
2. Rename the file and click Save.
----End

Server) A FAQs
A.1.15 How to Configure the Resolution on SUSE Linux
Question
How do I configure the resolution on SUSE Linux?
Answer
Step 1 Log in to the GUI of the SUSE Linux OS as the root user.
Step 2 Open a CLI and run the following command to start the YaST2 control center:
# yast2
Step 3 Choose Hardware > Graphics Card and Monitor.
NOTE
If the Automatic Graphics System Setup dialog box is displayed, click Change Configuration.
Step 4 In the SaX2: X11 Configuration dialog box, click Change to modify the monitor properties.
Step 5 In the Monitor Settings dialog box, choose VESA. Select the resolution to be modified based
on the monitor size and individual habit. The commonly used resolution is 1024×768@60HZ.

Server) A FAQs
NOTE
The IBM server does not support the resolution of 16:10, for example, 1440×900.
Step 6 Click OK. The SaX2: X1 Configuration dialog box is displayed.

NOTE
The newly configured resolution is displayed in Resolution. You can click it to modify the resolution too. The
resolution value should be less than or equal to the resolution set for Monitor.
Step 7 Click OK. The Message dialog box is displayed.
Step 8 Click Test. The XFine2 dialog box is displayed.
Step 9 If no error is displayed during the test, click Save. The Message dialog box is displayed.

Server) A FAQs
Step 10 Click Yes.
Step 11 Run the following commands to restart the OS to make the configurations take effect. The restart
process takes about 5 to 8 minutes.
# shutdown -r now
----End
A.1.16 How to Install the 7-zip Software on the SUSE Linux OS

Question
How do I install the 7-zip software on the SUSE Linux OS?
Answer
Step 1 Download the 7-zip software package p7zip_9.20.1_src_all.tar.bz2 from http://
sourceforge.net/projects/p7zip/.
Step 2 Use SFTP/FTP to upload the 7-zip software package to the /opt directory on the server as the
root user. The SFTP mode is recommended because it is more secure. For details about how to
use SFTP to upload the software package, see A.6.15 How to Use the FileZilla to Transfer

Server) A FAQs
Files by SFTP. For details about how to use FTP to upload the software package, see A.6.16
How to Transfer Files by Means of FTP.
Step 3 Use Telnet or SSH to log in to the server as the root user. The SSH mode is recommended
because it is more secure.
Step 4 Switch to the path where the software package is stored and assign permissions to the software
package.
# cd /opt
# chmod 750 /opt/p7zip_9.20.1_src_all.tar.bz2
Step 5 Decompress the 7-zip software package.

# tar jxvf p7zip_9.20.1_src_all.tar.bz2
Step 6 Navigate to the p7zip_9.20.1 directory.

# cd p7zip_9.20.1
Step 7 Compile the software package.

# make && make install
Step 8 Create the 7z link file.

# cd /usr/local/bin
# ln -s 7za 7z
Step 9 Add /usr/local/bin/ to the environment variable PATH.

1. Open the /etc/profile file.
# vi /etc/profile
2. Use up and down arrow keys to search for statements similar to the following:
PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH
3. Add /usr/local/bin/ to the environment variable PATH. For details about using the vi editor,
see A.1.10 How to Use the vi Editor.
After the operation is performed, information similar to the following is displayed:

PATH=/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin/:$PATH
4. Press Esc and run the :wq command to save the /etc/profile file and exit from the Vi editor.
Step 10 Check whether the 7-zip software is installed successfully.
Run the following command:

# 7z
If the 7z Help information is displayed, the 7-zip softawre is installed successfully.
----End
A.2 System Settings of the Huawei RH series rack server

This topic covers FAQs about Huawei RH series rack server system settings.

Server) A FAQs
A.2.1 How Do I Use iMana IP to Log In to a Remote Huawei RH

series rack server
Question
How do I use iMana IP to log in to a remote Huawei RH series rack server?
Answer
Step 1 Open the Internet Explorer and enter the IP address of the iMana module in the address bar. The
iMana login window is displayed.
NOTE
l Choose Tools > Internet option before logging in to the Huawei RH series rack server. Click the
Connection tab to clear settings of the proxy server of the Internet Explorer.
l The default IP of iMana is 192.168.2.100. The subnet mask is 255.255.255.0. See A.2.2 How to View
the IP Address of the iMana on the Huawei RH series rack server if the default IP of iMana changes.
Step 2 Enter the user name and the password of iMana and click Log In.
NOTE
l Default user name: root

l Default password: Huawei12#$ (Enter the new password if the password has been changed. If the
password has not been changed, it is recommended to change the password quickly and keep the new
password safe for the safety of a system. For details, see A.2.3 How to Change the Password of iMana
User Root. )
Step 3 Choose Remote Control from the navigation tree to open the remote control window. The
remote control window displays the KVM property and the virtual media property.

Server) A FAQs
Step 4 Click Remote Virtual Console (shared mode) or Remote Virtual Console (private mode) as
required to enter the virtual console window.
l Remote Virtual Console (shared mode): Two users can log in to the remote virtual console
concurrently. The server responds to commands of each user.
l Remote Virtual Console (private mode): Only one user can log in to the remote virtual
console.
NOTE
If the Safe warning dialog box is displayed, click Permission.
----End
A.2.2 How to View the IP Address of the iMana on the Huawei RH

series rack server
Question
How do I view the IP address of the iMana on the Huawei RH series rack server?
Answer
Step 1 Install the KVM on the server.
Step 2 Press the power button on the server and restart the server.
Step 3 During server restart, press Delete until the BIOS configuration window is displayed.
NOTE
If a dialog box is displayed asking you to enter a password, enter the desired password and then press
Enter.
Step 4 View the IP Address of the iMana.

1. Choose Server Mgmt tab.

Server) A FAQs
2. Choose BMC network configuration, and press Enter to access the BMC network
configuration window to view the IP address.

1. Choose Advanced > IPMI BMC Configuration, and press Enter. The IPMI BMC
Configuration page is displayed.
2. Select BMC Configuration, and press Enter to access the BMC Configuration
window to view the IP address.

Server) A FAQs
----End
A.2.3 How to Change the Password of iMana User Root
Question
How to modify the password of iMana user root?
Answer
Step 1 Open Internet Explorer. Enter the IP address of the iMana module in the address bar. The window
for logging in to iMana is displayed.
NOTE
The default IP address of iMana is 192.168.2.100. The subnet mask is 255.255.255.0. See A.2.2 How to
View the IP Address of the iMana on the Huawei RH series rack server if the default IP of iMana
changes.
Step 2 Enter the user name and the password of iMana and click Log In.
NOTE
l Default user name: root

l Default password: Huawei12#$ (Enter the new password if the password has been changed. If the
password has not been changed, it is recommended to change the password quickly and keep the new
password safe for the safety of a system.)
Step 3 Choose Configuration > User from the left navigation tree, and click the of user root.

Server) A FAQs
Step 4 In the Modify User Information dialog box, enter new user information, and click OK.
NOTE
Requirements on the user password are different when the function of checking the password complexity is
enabled or disabled:
l If the function is disabled, you can leave the password blank or enter a string whose length is shorter than
20 characters.
l If this function is enabled, the password must meet the following requirements:
l The password contains a minimum of 8 characters and a maximum of 20 characters.
l At least one space or one special character: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
l At least two of the following combinations: lowercase letters a to z, uppercase letters A to Z, and digits
0 to 9.
l The password cannot be the same as the user name or the reverse of the user name.
----End
A.2.4 How to Solve iMana Problems
Question
How do I solve iMana problems?
Answer
The following problems may exist on the iMana and you must take measures to these problems:

Server) A FAQs
No. Problem Solution
1 l The Internet Explorer does not The procedure is as follows:

respond. 1. Right-click the Internet Explorer icon
l After a user clicks the Internet on the taskbar to close the Internet
Explorer or Remote Virtual Console Explorer. If the Internet Explorer is
icon on the taskbar, the Internet still open, stop the iexplore.exe
Explorer or Remote Virtual Console process on the Processes tab page in
window is not displayed. the Task Manager.
l The Internet Explorer closes 2. Open the Internet Explorer.
automatically. 3. Access the iMana page and open the
l After a user closes the Internet Remote Virtual Console window.
Explorer and Remote Virtual The original session is still there.
Console windows, the user cannot
open the Remote Virtual Console
window.
2 After the Remote Virtual Console On the taskbar, right-click Remote

window is minimized on the taskbar, the Virtual Console and choose Close
window cannot be restored. window from the shortcut menu to shut
down the Remote Virtual Console
window. Re-open the Remote Virtual
Console window on the iMana page.
3 The Caps indicator on the keyboard is on, Press Caps Lock.

but the entered letter is a lower-case letter. The indicator on the right of caps above
Remote Virtual Console turns green.
NOTE
l On the Remote Virtual Console window,
the Caps indicator in the On state does not
mean that the letter entered is an upper-
case letter.
l For the Huawei RH series rack server, if
the indicator on the right of caps above
Remote Virtual Console is green,
entered letters are uppercase. If the
indicator on the right of the caps is black,
entered letters are lowercase.

Server) A FAQs
4 The Num indicator on the key board is on, Press Num Lock.
but entering a number fails. The indicator on the right of the num
above Remote Virtual Console turns
green.
NOTE
l On the Remote Virtual Console window,
the Num indicator in the On state does not
mean that the number key works.
l For the Huawei RH series rack server, if
the indicator on the right of the num above
Remote Virtual Console is green,
entered letters are digit. If the indicator on
the right of the num is black, the digit
cannot be entered.
5 Two pointers are displayed in the Remote

Virtual Console window. l Method one: You can click on the
toolbar above Remote Virtual
Console and select the Single Mouse
check box to make only one pointer
displayed in the window. To exit from
the single-pointer mode, click

and clear the Single Mouse check box.
l Method two: Because the mouse of
Controller is delay, you can adjust the
mouse speed of your computer to
make two mouses move closer
together.
1. Click Start, and then click
Control Panel. The Adjust you
computer's settings windows is
displayed.
2. Set the value of View by to Small
icons or Large icons.
3. Click Mouse. The Mouse
Properties windows is displayed.
4. Adjust the Speed in the Buttons
tab.

Server) A FAQs
6 No operation is performed on the server Enter the iMana address in the address bar
for more than 5 minutes after a login to the of the Internet Explorer. Then enter the
iMana management window. The system user name and password in the iMana
then automatically displays an error login winidow.
message indicating session timeout and The cause of the fault is that the default
exits from the login. period for the iMana session is 5 minutes.
If no operation is performed on the server
after the period elapses, the session is
disconnected. You can access the iMana
management window according to on-site
requirements and choose Configuration
> Service > Web Server to set Timeout
Period.
7 After the iMana login window is accessed Enter the iMana address in the address bar
and login is not yet performed, the system of the Internet Explorer to re-open it.
automatically enters the window
indicating a connection failure.
8 After Remote Virtual Console is Press Ctrl+Alt+Shift, and then click

maximized, the mouse is displayed on the toolbar above Remote
disorderly and the it is difficult to perform Virtual Console to exit from the
any operation. maximization window.
A.2.5 Mappings Between Physical and Logical Network Interfaces

on an Huawei RH Series Rack Server Running SUSE Linux
This topic describes the mappings between physical and logical network interfaces on an Huawei
RH series rack server running SUSE Linux.
NOTE
l The Ethernet interfaces on an Huawei RH series rack server consist of integrated network interfaces
and extended network interfaces. The integrated network interfaces are recommended.
l An Huawei RH series rack server running SUSE Linux supports only the Broadcom and Intel NICs.
Example 1: In Figure A-1, the mappings between the physical and logical network interfaces
for the Huawei Tecal RH2288H V2 server are described as follows:
l The Huawei Tecal RH2288H V2 server is integrated with one NIC. The associated logical
network interfaces on the integrated NIC are named eth0, eth1, eth2, and eth3.
l eth4, eth5, eth6, and eth7 are network interfaces on the extended NICs. The associated
logical network interfaces are named eth4, eth5, eth6, and eth7.

Server) A FAQs
Figure A-1 Mappings between physical and logical network interfaces on the Huawei Tecal
RH2288H V2 server
for the Huawei Tecal RH5885H V3 server are described as follows:
l eth0 and eth1 are network interfaces on the integrated NIC. The associated logical network
interfaces are named eth0 and eth1.
l eth2, eth3, eth4, eth5, eth6, and eth7 are network interfaces on the extended NICs. The
associated logical network interfaces are named eth2, eth3, eth4, eth5, eth6, and eth7.
Figure A-2 Mappings between physical and logical network interfaces on the Huawei Tecal
RH5885H V3 server
A.2.6 Formatting disks (Huawei RH series rack server)

This topic describes how to formatting disks.

Server) A FAQs
Prerequisites
l If the disks are to be formatted in local mode, you must ensure that the server is connected
to the KVM.
l If the disks are to be formatted in remote mode, you must ensure that the following
preparations are ready:
– A PC or laptop on which the Internet Explorer browser is installed is ready.
– The version of the Internet Explorer browser must be 6.0, 7.0, 8.0, or 9.0 and the Internet
– The IP address of the iMana is available. For details about how to set the IP address of
the iMana, see 3.3.1.1 Configuring the iMana IP Address Through iMana
Management Interface.
Procedure
Step 1 Start the server.
l In local mode, press the power button to restart the PC server.
l In remote mode, perform the following operations:
1. Log in to the server. For details, see A.2.1 How Do I Use iMana IP to Log In to a
Remote Huawei RH series rack server.
2. Click on the toolbar which is right above Remote Virtual Console and select
Gold Reset.
Step 2 On Huawei Tecal RH5885H V3 server, ignore the following operations; On Huawei Tecal
RH2288H V2 server, perform the following operations:
1. When the BIOS start page appears, press Delete until the BIOS Setup Utility program is
started.
NOTE
If the BIOS password has been modified, a dialog box asking you to enter a password will be displayed
during startup. Enter the required password to access the Setup Utility application.
2. Choose Exit > Load Optimal Defaults, and press Enter.

Server) A FAQs
3. In the Load Optimal Defaults? dialog box, click Yes and press Enter.
4. Choose Exit > Exit Saving Changes, and press Enter.
5. In the Exit Saving Changes? dialog box, click Yes and press Enter.
Step 3 After the basic input/output system (BIOS) check is completed, the BIOS information about the
RAID is displayed, as shown in the following figure.
NOTE
This screen stays for a short period of time. Press Ctrl+H the moment you see Ctrl+H on the screen. If
Ctrl+H is not pressed, restart the system.
Step 4 Press Ctrl+H as prompted to access the Adapter Selection window.


Server) A FAQs
Step 5 Click Start to access the WebBIOS window.

NOTE
If window MegaRAID BIOS Config Utility Foreign Configuration is displayed, click Clear.
Step 6 Click Configuration Wizard to access the RAID configuration wizard window, as shown in
the following figure.
Step 7 Select Clear Configuration and click Next.
NOTICE
After you select Clear Configuration, all RAID configurations will be deleted; as a result, hard
disk data will be damaged or lost. Check whether hard disk data can be deleted before selecting
Clear Configuration.
Step 8 Click Yes to clear the configuration, and return to the WebBIOS window.
Step 9 Initialize RAID configurations.

1. Click Configuration Wizard to access the RAID configuration wizard window
2. Select New Configuration and click Next.
3. Click Yes to delete RAID configurations.
4. Select Automatic Configuration and click Next. The Preview dialog box is displayed.
NOTE
Use the default value, Redundancy when possible, for Redundancy.
5. Click Accept.
6. Click Yes to save RAID configurations.

Server) A FAQs
7. Click Yes to initialize RAID configurations.

8. Click Home to return to the WebBIOS window.
After the initialization is complete, the WebBIOS window is displayed. As shown in the
following figure, the eight hard disks are used as an example.

l In local mode, press Ctrl+Alt+Delete to restart the server.

Server) A FAQs
Gold Reset.
----End
A.2.7 Viewing Hard Disk Information (Huawei RH series rack

server)
This topic describes how to view hard disk information.
Prerequisites
l If the hard disk information is to be viewed in local mode, you must ensure that the server
is connected to the KVM.
l If the hard disk information is to be viewed in remote mode, you must ensure that the
following preparations are ready:
– A PC or laptop on which the Internet Explorer browser is installed is ready.
– The version of the Internet Explorer browser must be 6.0, 7.0, 8.0, or 9.0 and the Internet
– The IP address of the iMana is available. For details about how to set the IP address of
the iMana, see 3.3.1.1 Configuring the iMana IP Address Through iMana
Management Interface.
Procedure
Step 1 Start the server.
l In local mode, press the power button to restart the PC server.
1. Log in to the server. For details, see A.2.1 How Do I Use iMana IP to Log In to a
Remote Huawei RH series rack server.
Gold Reset.
NOTE

Server) A FAQs


NOTE
If window MegaRAID BIOS Config Utility Foreign Configuration is displayed, click Clear.
Step 5 Click Physical View to access the Physical View window, as shown in the following figure.
NOTE
l In the navigation tree, the Physical View node automatically changes to Logical View.
l In the following example, RAID has not been configured for hard disks. The displayed information
displayed in the scenario where RAID has been configured is different from that in the scenario where
RAID has not been configured. Pay attention to only slot information in Physical View and check
whether the slot information meets the following conditions:
l IDs of eight slots from Slot: 0 to Slot: 7 are displayed.
l The description for every slot ID has three available options: Unconfigured Good, Online, and
Global Hot Spare.
If any two of the preceding three conditions are met, the eight hard disks on the server are available.
Otherwise, an unavailable hard disk exists on the server.

Server) A FAQs

Server) A FAQs

l In local mode, press Ctrl+Alt+Delete to restart the server.
Gold Reset.
----End
A.3 System Settings of the IBM Server

This topic covers FAQs about IBM Server system settings.
A.3.1 How to Solve the Problem Where the Remote Control Desktop
Appears and Then Disappears Immediately
Question
How do I solve the problem where the remote control desktop appears and then disappears
immediately?
Answer
Step 1 On the Internet Explorer, choose Tools > Internet Options > Security > Trusted sites >
Sites, the Trusted sites dialog is displayed.
Step 2 Clear the selection of the Require server verification (https:) for all sites in this zone check
box.
Step 3 Add website address to the Add this website to the zone.
NOTE
If the Would you like to move it to the Trusted sites zone? dialog is displayed, click Yes.
Step 4 Click Close.
Step 5 Click Custom level.

Server) A FAQs
Step 6 Select Low from the Reset to drop-down list.

NOTE
The IE browser has different versions. Select the lowest level from the Reset to drop-down list.
Step 7 Click Reset.
Step 8 Click OK.
Step 9 Click Apply.
Step 10 Click OK.
Step 11 Press F5 to refresh the Internet Explorer.
----End
A.3.2 How do I use an IMM IP address to remotely log in to an IBM

server (IBM X3650 M4)
Question
How do I use an IMM IP address to remotely log in to an IBM server (IBM X3650 M4)?

Server) A FAQs
Answer
NOTE
Server.
NOTE


Server) A FAQs
NOTE
this site.
be displayed.
the problem.
----End

Server) A FAQs
A.3.3 How to Use an IMM IP Address to Remotely Log In to an IBM

Server(IBM X3850 X5 and IBM X3650 M3)
Question
How do I use an IMM IP address to remotely log in to an IBM server?
Answer
NOTE
Server.
NOTE

NOTE
window.

Server) A FAQs
NOTE
this site.
the problem.
be displayed.
----End
A.3.4 How to View the IMM IP Address on the IBM Server
Question
How do I view the IMM IP address on the IBM server?
Answer
Step 1 Install the KVM on the PC server.
NOTE
A common monitor is enough.
Step 2 Press the power button of the PC server to restart it.
Step 3 Wait about 1 minute after the IBM System X window is displayed. The <F1> Setup option is
displayed.

Server) A FAQs
Step 4 Press F1 to select Setup, and press Enter.
Step 5 Use arrow keys to select System Settings, and press Enter.

Server) A FAQs
Step 6 Use arrow keys to select Integrated Management Module, and press Enter.

Server) A FAQs
Step 7 Use arrow keys to select Network Configuration press Enter and access the page for modifying
the IMM IP address.

Server) A FAQs
Step 8 View the IP address in IP Address.
----End
A.3.5 How to Change the Password of the IMM User USERID(IBM

X3650 M4)
Question
How to change the password of the IMM user USERID?
Answer
login window.
NOTE
Server.

Server) A FAQs
NOTE

security, modify the default password and remember the new password.
Step 3 Click IMM Management > Users.
Step 4 In the User Accounts, click USERID.
Step 5 Enter a new password, such as Changeme_123, in Password. Enter the password again in
Confirm password. To ensure the security of the U2000, passwords must be complex enough.
For example, a password must contain eight or more characters of two types. The allowed
characters are digits, letters, and special characters. Remember to change passwords regularly.

Server) A FAQs
Step 6 Click OK.
----End

Server) A FAQs
A.3.6 How to Change the Password of the IMM User USERID(IBM

X3850 X5 and IBM X3650 M3)
Question
How do I change the password of the IMM user USERID?
Answer
login window.
NOTE
Server.
NOTE

password has been changed, enter the new password.
NOTE
Step 4 Choose Login Profiles from the navigation tree and select USERID.
Step 5 Enter a new password, such as Changeme_123, in Password. To ensure the security of the
U2000, passwords must be complex enough. For example, a password must contain eight or
more characters of two types. The allowed characters are digits, letters, and special characters.
Remember to change passwords regularly.

Server) A FAQs
Step 6 Enter the password again in Confirm password.
Step 7 Click Save. A message indicating that the password will take effect is displayed. Click OK.
----End
A.3.7 How to Solve IMM Problems
Question
How do I solve IMM problems?
Answer
The following problems may exist on the IMM and you must take measures to these problems:
N Problem Solution
o
.
1 l The Internet Explorer does not respond. The procedure is as follows:

l After a user clicks the Internet Explorer 1. Right-click the Internet Explorer icon
or Video Viewer icon on the taskbar, the on the taskbar to close the Internet
Internet Explorer or Video Viewer Explorer. If the Internet Explorer is still
window is not displayed. open, stop the iexplore.exe process on
l The Internet Explorer closes the Processes tab page in the Task
automatically. Manager.
l After a user closes the Internet Explorer 2. Open the Internet Explorer.
and Video Viewer windows, the user 3. Access the IMM page and open the
cannot open the Video Viewer window. Video Viewer window. The original
session is still there.
2 After the Video Viewer window is On the taskbar, right-click Video Viewer
minimized on the taskbar, the window and choose Close window from the
cannot be restored. shortcut menu to shut down the Video
Viewer window. Re-open the Video
Viewer window on the IMM page.

Server) A FAQs
N Problem Solution
o
.
3 The Caps indicator on the keyboard is on, Two methods are available:
but the entered letter is a lower-case letter. l Press Caps Lock.
NOTE
l On the Video Viewer window, the
Caps indicator in the On state does not
mean that the letter entered is an upper-
case letter.
l For the IBM X3650 M4 server, if
CAPS is displayed in the lower right
corner of the Video Viewer window,
letters are entered in upper case; if
CAPS is not displayed in the lower right
letters are entered in lower case. The
Caps indicator on the keyboard cannot
indicate whether letters are entered in
upper or lower case.
l Shut down the Video Viewer window,
press Caps Lock, and open it again.
4 The Num indicator on the key board is on, Two methods are available:
but entering a number fails. l Press Num Lock.
NOTE
l On the Video Viewer window, the
Num indicator in the On state does not
mean that the number key works.
l For the IBM X3650 M4 server, if
NUM is displayed in the lower right
digits can be entered; if NUM is not
displayed in the lower right corner of the
Video Viewer window, digits cannot be
entered. The Num indicator on the
keyboard cannot indicate whether the
number keypad is available.
l Shut down the Video Viewer window,
press Num Lock. Open it again after the
Running ActiveX KVM Client
window is automatically closed.
5 Failure to open multiple Video Viewer Open one Video Viewer window on a PC
windows on a PC or laptop or the failure that or laptop. Open the Video Viewer window
the Video Viewer window does not on a PC or laptop for each server when you
respond. operate multiple servers.

Server) A FAQs
A.3.8 Mappings Between Physical and Logical Network Interfaces

on an IBM Server Running SUSE Linux
This topic describes the mappings between physical and logical network interfaces on an IBM
server running SUSE Linux.
NOTE
l The Ethernet interfaces on an IBM server consist of integrated network interfaces and extended network
interfaces. The integrated network interfaces are recommended.
l An IBM server running SUSE Linux supports only the Broadcom and Intel NICs.
for the IBM X3650 M4 are described as follows:
l The IBM X3650 M4 is integrated with one NIC. The associated logical network interfaces
on the integrated NIC are named eth0, eth1, eth2, and eth3.
Figure A-3 Mappings between physical and logical network interfaces on the IBM X3650 M4
for the IBM X3850 X5 are described as follows:
l eth0 and eth1 are network interfaces on the integrated NIC. The associated logical network
interfaces are named eth0 and eth1.
l eth2, eth3, eth4, eth5, eth6, and eth7 are network interfaces on the extended NICs. The
associated logical network interfaces are named eth2, eth3, eth4, eth5, eth6, and eth7.
Figure A-4 Mappings between physical and logical network interfaces on the IBM X3850 X5

Server) A FAQs
for the IBM X3650 M3 are described as follows:
l The IBM X3650 M3 is integrated with two NICs. The NIC on the right is integrated NIC
1 and the NIC on the left is integrated NIC 2. The associated logical network interfaces are
named eth0, eth1, eth2, and eth3.
Figure A-5 Mappings between physical and logical network interfaces on the IBM X3650 M3
A.3.9 Viewing Hard Disk Information in Local Mode (IBM Server)

This topic describes how to view hard disk information in local mode.
Prerequisites
You must ensure that the server is connected to the KVM.
Context
NOTE
l The operation snapshots in this topic vary according to the IBM WebBIOS versions and do not affect
the RAID configuration. During the RAID configuration, use actual snapshots.
l If no window is displayed after you click a button during the configuration, move the mouse and try
again.
Procedure
Step 1 Start the IBM server. After the basic input/output system (BIOS) check is completed, the BIOS
information about the RAID is displayed, as shown in the following figure.
NOTE

Server) A FAQs

NOTE
If MegaRAID BIOS Config Utility Foreign Configuration window is displayed, click Clear.
NOTE
l If configuring eight hard disks for the IBM server with standard delivery configurations, IDs of
eight slots from Slot: 0 to Slot: 7 are displayed. If configuring two hard disks for the IBM server
(X3850 X5) with standard delivery configurations, IDs of two slots from Slot: 0 to Slot: 1 are
displayed.
Global Hot Spare.
If any two of the preceding three conditions are met, all hard disks on the server are available. Otherwise,
an unavailable hard disk exists on the server. As shown in the following figure, the eight hard disks are
used as an example.

Server) A FAQs
Step 5 Click Exit to exit the WebBIOS window.
Step 6 Click Yes. A dialog box is displayed.
Step 7 Press Ctrl+Alt+Delete to restart the server.
----End
A.3.10 Viewing Hard Disk Informationin Remote Mode (IBM

X3650 M4)
This topic describes how to view hard disk information in remote mode.
Prerequisites
l The IMM IP address has been set.
Context
NOTE
again.

Server) A FAQs
Procedure
Step 1 Perform the following operations to access the RAID configuration window.
1. Open the Internet Explorer and enter the IMM IP address of the IMM in the address bar to
access the page for logging into the IMM.
2. Enter an IMM user name and a password, and click Login.
NOTE

l The default password is PASSW0RD. Note that the sixth character is digit 0 but not letter O. If
the password has been changed, enter the new password. If the password has not been changed,
for system security, modify the default password and remember the new password. For details,
see A.3.5 How to Change the Password of the IMM User USERID(IBM X3650 M4).
3. Click Remote Control and select Use the ActiveX Client > Start remote control in
single-user mode to access the remote control desktop.

Server) A FAQs
NOTE
1. Click Start remote control in single-user mode and wait about 2 minutes. In the dialog box
asking you whether to install the IMM_KVMVM32.cab, click Install.
2. During the installation, click Run in the Warning-Security dialog box asking you whether
to trust this site.
l Do not close the ActiveX KVM Client dialog box. Otherwise, the Video Viewer dialog box
cannot be displayed.
l If the remote control desktop appears and then disappears immediately, see A.3.1 How to Solve
the Problem Where the Remote Control Desktop Appears and Then Disappears
Immediately to solve the problem.
l If Use the ActiveX Client is unavailable, just click Start remote control in single-user mode
to access the remote control desktop.
l For the IBM X3650 M4 server, if CAPS is displayed in the lower right corner of the Video
Viewer window, letters are entered in upper case; if CAPS is not displayed in the lower right
corner of the Video Viewer window, letters are entered in lower case. The Caps indicator on the
keyboard cannot indicate whether letters are entered in upper or lower case.
l For the IBM X3650 M4 server, if NUM is displayed in the lower right corner of the Video
Viewer window, digits can be entered; if NUM is not displayed in the lower right corner of the
Video Viewer window, digits cannot be entered. The Num indicator on the keyboard cannot
indicate whether the number keypad is available.
4. Choose Tools > Power > Reboot from the main menu to reboot the system.

Server) A FAQs
NOTE

l If Reboot is unavailable, choose Tools > Power > On and then choose Tools > Power >
Reboot to restart the system.
5. Start the IBM server. After the basic input/output system (BIOS) check is completed, the
BIOS information about the RAID is displayed, as shown in the following figure.
NOTE

NOTE
7. Click Start to access the WebBIOS window.

NOTE

Server) A FAQs
NOTE
l IDs of eight slots from Slot: 0 to Slot: 7 are displayed.
Global Hot Spare.
If any two of the preceding three conditions are met, the eight hard disks on the server are available.
Otherwise, an unavailable hard disk exists on the server.
Step 3 Click Exit to exit the WebBIOS window. The Exit Application dialog box is displayed, asking
you whether to exit.
Step 4 Click Yes and choose Tools > Power > Reboot to restart the server. It takes approximately 5
to 8 minutes to restart the system.
NOTE
If a message asking you whether to continue is displayed, click Yes.
----End
A.3.11 Viewing Hard Disk Informationin Remote Mode (IBM

X3850 X5 and IBM X3650 M3)
This topic describes how to view hard disk information in remote mode.

Server) A FAQs
Prerequisites
Context
NOTE
again.
Procedure
NOTE

see A.3.6 How to Change the Password of the IMM User USERID(IBM X3850 X5 and IBM
X3650 M3).
3. Click Continue to access the Integrated Management Module web page.
NOTE
4. Enable remote control. Choose Tasks > Remote Control from the navigation tree. In the
right-hand pane, click Use the ActiveX Client with Microsoft Internet Explorer > Start
Remote Control in Single User Mode to access the remote control desktop.
window.

Server) A FAQs
NOTE
l If a dialog box is displayed asking you to install plug-in, click Install.

l If Use the ActiveX Client with Microsoft Internet Explorer is unavailable, just click Start
NOTE

6. Start the IBM server. After the basic input/output system (BIOS) check is completed, the
BIOS information about the RAID is displayed, as shown in the following figure.
NOTE

NOTE

Server) A FAQs

NOTE
NOTE
l If configuring eight hard disks for the IBM server with standard delivery configurations, IDs of
eight slots from Slot: 0 to Slot: 7 are displayed. If configuring two hard disks for the IBM server
(X3850 X5) with standard delivery configurations, IDs of two slots from Slot: 0 to Slot: 1 are
displayed.
Global Hot Spare.
If any two of the preceding three conditions are met, all hard disks on the server are available. Otherwise,
an unavailable hard disk exists on the server. As shown in the following figure, the eight hard disks are
used as an example.
Step 4 Click Yes and choose Tools > Power > Reboot to restart the server. It takes approximately 5
to 8 minutes to restart the system.

Server) A FAQs
NOTE
----End
A.3.12 Formatting disks in Local Mode (IBM Server)

This topic describes how to format disks in local mode.
Prerequisites
You must ensure that the server is connected to the KVM.
Context
NOTE
again.
Procedure
Step 1 After the server is restarted, press F1 to access the BIOS window as prompted.

Server) A FAQs
Step 2 Select Load Default Settings to restore default settings. Press Enter. The following dialog box
is played.
Step 3 Select Boot Manager, press Enter, and then choose Add Boot Option.
Step 4 Optional: For IBM X3650 M3 or IBM X3850 X5, select Legacy Only. Press Enter.

Server) A FAQs
Step 5 Optional: For IBM X3650 M4, select Generic Boot Option and then Legacy Only by arrow
keys. Press Enter.
Step 6 Press Esc to return to Boot Manager.
Step 7 Select Change Boot Order. Press Enter. The following dialog box is played.
Step 8 Press Enter, and select Legacy Only using the arrow key ↓.
Step 9 Press Shift and + to set the startup precedence to Legacy Only.

Server) A FAQs
Step 10 Press Enter. Select Commit Changes using the arrow keys and press Enter to save the settings.
Step 11 Restart the server manually.
NOTE

NOTE
If a window shown in the following figure is displayed, click Clear.

Server) A FAQs
NOTICE

NOTE
5. Click Accept.

Server) A FAQs
Step 19 Click Exit to exit the WebBIOS window.
Step 20 Click Yes. A dialog box is displayed.
Step 21 Press Ctrl+Alt+Delete to restart the server.
----End
A.3.13 Formatting the disks in Remote Mode (IBM X3650 M4)

This topic describes how to format the disks in remote mode.
Prerequisites
Context
NOTE
again.
Procedure

Server) A FAQs
NOTE

see A.3.5 How to Change the Password of the IMM User USERID(IBM X3650 M4).
3. Click Remote Control, select Use the ActiveX Client, and click Start remote control in
single-user mode to access the remote control desktop.

Server) A FAQs
NOTE
1. Click Start remote control in single-user mode and wait about 2 minutes. In the dialog box
asking you whether to install the IMM_KVMVM32.cab, click Install.
2. During the installation, click Run in the Warning-Security dialog box asking you whether
to trust this site.
l Do not close the ActiveX KVM Client dialog box. Otherwise, the Video Viewer dialog box
cannot be displayed.
l If Use the ActiveX Client is unavailable, just click Start remote control in single-user mode
to access the remote control desktop.
l For the IBM X3650 M4 server, if CAPS is displayed in the lower right corner of the Video
Viewer window, letters are entered in upper case; if CAPS is not displayed in the lower right
corner of the Video Viewer window, letters are entered in lower case. The Caps indicator on the
keyboard cannot indicate whether letters are entered in upper or lower case.
l For the IBM X3650 M4 server, if NUM is displayed in the lower right corner of the Video
Viewer window, digits can be entered; if NUM is not displayed in the lower right corner of the
Video Viewer window, digits cannot be entered. The Num indicator on the keyboard cannot
indicate whether the number keypad is available.
NOTE

5. After the IBM System X window is displayed, wait for about 2 minutes until <F1>
Setup is displayed.

Server) A FAQs
6. Press F1 to access the BIOS window.

7. Select Load Default Settings to restore default settings. Press Enter. The following dialog
box is played.
8. Select Boot Manager and press Enter. Then select Add Boot Option and press Enter.
9. Select Generic Boot Option and then select Legacy Only by arrow key ↓. Press Enter.
10. Press Esc to return to Boot Manager.
11. Press Esc twice to return to Boot Manager.
12. Select Change Boot Order. Press Enter. The following dialog box is played.

Server) A FAQs
13. Press Enter, and select Legacy Only using the arrow key ↓.
14. Press Shift and + to set the startup precedence to Legacy Only.
15. Press Enter. Select Commit Changes using the arrow keys and press Enter to save the
settings.
NOTE


Server) A FAQs
NOTE

NOTE

NOTE

Server) A FAQs
NOTICE

4. Select Automatic Configuration and click Next.
NOTE
5. Click Yes in the dialog box showing the message Are you sure you want to disable data
protection?.
6. Click Accept.

Server) A FAQs

8. Click Yes in the dialog box showing the message All data on the new Virtual Drivers
will be lost. Want to Initialize? to initialize RAID configurations.
The following figure shows the WebBIOS window after the initialization is complete.
Step 7 Click Yes, and the following window is displayed.
Step 8 Choose Tools > Power > Reboot to restart the server. It takes approximately 5 to 8 minutes to
restart the system.
NOTE
----End
A.3.14 Formatting the disks in Remote Mode (IBM X3850 X5 and

IBM X3650 M3)
This topic describes how to format the disks in remote mode.
Prerequisites

Server) A FAQs
Context
NOTE
again.
Procedure
NOTE

see A.3.6 How to Change the Password of the IMM User USERID(IBM X3850 X5 and IBM
X3650 M3).
3. Click Continue to access the Integrated Management Module web page.
NOTE
4. Enable remote control. Choose Tasks > Remote Control from the navigation tree. In the
right-hand pane, select Use the ActiveX Client with Microsoft Internet Explorer and
click Start Remote Control in Single User Mode to access the remote control desktop.
window.

Server) A FAQs
NOTE
l If a dialog box is displayed asking you to install plug-in, click Install.

l If Use the ActiveX Client with Microsoft Internet Explorer is unavailable, just click Start
NOTE

6. After the IBM System X window is displayed, wait for about 2 minutes until <F1>
Setup is displayed.
7. Press F1 to access the BIOS window.

8. Select Load Default Settings to restore default settings. Press Enter. The following dialog
box is played.

Server) A FAQs
9. Select Boot Manager and press Enter. Then select Add Boot Option and press Enter.
10. Select Legacy Only. Press Enter.
11. Press Esc to return to Boot Manager.
12. Select Change Boot Order. Press Enter. The following dialog box is played.
13. Press Enter, and select Legacy Only using the arrow key ↓.
14. Press Shift and + to set the startup precedence to Legacy Only.

Server) A FAQs
15. Press Enter. Select Commit Changes using the arrow keys and press Enter to save the
settings.
NOTE

NOTE

Server) A FAQs
NOTE

NOTE
NOTICE

Server) A FAQs

NOTE
5. Click Accept.
Step 6 Click Exit to exit the WebBIOS window. The Exit Confirmation dialog box is displayed,
asking you whether to exit.
Step 7 Click Yes, and the following window is displayed.
Step 8 Choose Tools > Power > Reboot to restart the server. It takes approximately 5 to 8 minutes to
restart the system.
NOTE
----End

Server) A FAQs
A.3.15 How to Configure the HTTPS on the IMM(IBM X3650 M4)
Question
The HTTPS is recommended for remotely accessing the server to ensure system security. How
do I configure the HTTPS on the IMM?
Answer
login window.
NOTE
The default IP address of the IMM is 192.168.70.125. If the default IP address of the IMM has been changed,
see A.3.4 How to View the IMM IP Address on the IBM Server.
NOTE

Step 3 Click IMM Management > Security. Ensure that the value of HTTPS Server certificate
status is A signed certificate is installed. As shown in the following figure.
If the value of HTTPS Server certificate status is not A signed certificate is installed, perform
the following operations to install SSL authentication:
1. Click Generate a New Key and a Self-signed Certificate.

2. Set the related parameters in Generate New Key and Self-signed Certificate dialog box.
NOTE
l Set parameters in the Required SSL Certificate Data area as prompted. The following figure
shows examples of the parameter settings.
l The Optional SSL Certificate Data parameter does not need to be set.

Server) A FAQs
3. Click OK. After automatic authentication is complete, the value of HTTPS Server
certificate status changes to A signed certificate is installed.
Step 4 Ensure that Enabled HTTPS server is selected. As shown in the following figure.
If Enabled HTTPS server is not selected, perform the following operations:

1. Select Enabled HTTPS server.
2. Click Apply. The Confirm Restart dialog is played.
3. Click OK. The IMM restarts automatically.
NOTE
l During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or laptop.
If the IMM IP address can be pinged through, the IMM is successfully restarted. Restarting IMM takes
about 3 minutes.
l If HTTPS needs to be disabled and HTTP needs to be used, clear the selection of the select Enabled
HTTPS server. Then execute 4.2 through 4.3.

Server) A FAQs
login window.
NOTE
If HTTPS is used and a message indicating a security certificate error is displayed, ignore the message and
continue to browse the Web installation page.
----End
A.3.16 How to Configure the HTTPS on the IMM(IBM X3850 X5 and

IBM X3650 M3)
Question
The HTTPS is recommended for remotely accessing the server to ensure system security. How
do I configure the HTTPS on the IMM?
Answer
login window.
NOTE
The default IP address of the IMM is 192.168.70.125. If the default IP address of the IMM has been changed,
see A.3.4 How to View the IMM IP Address on the IBM Server.
NOTE

NOTE
Step 4 Choose Security from the navigation tree. Ensure that the value of HTTPS Server certificate
status is A self-signed Certificate is installed.
If the value of HTTPS Server certificate status is not A self-signed Certificate is installed,
perform the following operations to install SSL authentication:

Server) A FAQs
1. Click Generate a New Key and a Self-signed Certificate.

2. Set the related parameters.
NOTE
l Set parameters in the Certificate Data area as prompted. The following figure shows examples
of the parameter settings.
l The Optional Certificate Data parameter does not need to be set.
3. Click Generate Certificate in the lower-right corner. After automatic authentication is

complete, the value of HTTPS Server certificate status changes to A self-signed
Certificate is installed.
Step 5 Ensure that the value of HTTPS Server is Enabled.
If the value of HTTPS Server is not Enabled, perform the following operations:
1. Select Enabled from the HTTPS Server drop-down list.
2. Click Save. A message asking you to restart the IMM is displayed.
3. Click OK.
4. Choose Restart IMM from the navigation tree.
5. On the Restart IMM page, click Restart. A message indicating that the IMM will be
restarted is displayed.
6. Click OK. A message asking you to shut down the Internet Explorer or tabs is displayed.
7. Click Yes.

Server) A FAQs
NOTE
l During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or laptop.
If the IMM IP address can be pinged through, the IMM is successfully restarted. Restarting IMM takes
about 3 minutes.
l If HTTPS needs to be disabled and HTTP needs to be used, select Disabled from the HTTPS
Server drop-down list. Then execute 5.2 through 5.7.
login window.
NOTE
If HTTPS is used and a message indicating a security certificate error is displayed, ignore the message and
continue to browse the Web installation page.
----End
A.4 Veritas HA System

This topic covers FAQs about the Veritas HA system.
A.4.1 License Management

This topic describes the FAQs about license management.
A.4.1.1 Applying for a Veritas License

This topic describes how to apply for a formal Veritas license. The Veritas license used during
U2000 installation is a demo license. After the U2000 server is delivered to the installation site,
you must replace the demo license with a formal one in time.
Context
The Veritas licenses for the primary and secondary sites are different and thus must be applied
for separately.
Procedure
Step 1 Collect the following information according to the Veritas license application form:
l Serial number of the license confirmation form
l Contract number
l Software item
l License item quantity

Server) A FAQs
NOTICE
l The license confirmation form is delivered together with the DVD. The license confirmation
form is in paper format and equals the license file. It must be properly stored on site.
l If there are multiple serial numbers and the software items are the same, you must fill in
Software Item Qty with the total number of license confirmation forms.
l The license confirmation form is not delivered along with the product for the license whose
Veritas software BOM starts with 9904. Enter a slash (\) in the license confirmation form
column before contacting Huawei engineers to apply for the Veritas license.
Step 2 Send the information to the related Huawei engineer or the local office of Huawei.
Step 3 With the provided information, the related Huawei engineer accesses http://
support.huawei.com and chooses Software Center > Software License > Outsourcing
License > License Application. The page for applying for purchased software licenses is
displayed.
Step 4 Huawei engineer enters the license application information to apply for a Veritas license.
Step 5 Huawei engineer sends you the Veritas license.
----End
A.4.1.2 How to Check the Veritas License
Question
How to check the Veritas license?
Answer
Step 1 Run the following commands as root user to query the details about the Veritas license.
# vxlicrep -e|egrep 'Global|VVR|Product Name|KEYLESS|VxVM'
The following message will be displayed:

Server) A FAQs
NOTE
l Red characters indicate the VCS license. If Global Cluster Option (GCO) is Enabled and
VXKEYLESS is Disabled, the formal VCS license is used.
l Blue characters indicate the VxVM license. If VxVM is Enabled and VXKEYLESS is Disabled, the
formal VxVM license is used.
l Green characters indicate the VVR license. If VVR is Enabled and VXKEYLESS is Disabled, the
formal VVR license is used.
l The value of VXKEYLESS is Disabled.
If the preceding four conditions are met, the license is a permanent formal license.
----End
A.4.2 System Settings

This topic describes the FAQs about the system settings in the HA system.
A.4.2.1 How to Log in and Exit the VCS (Veritas Cluster Server)
Question
How do I log in to and exit the VCS?
Answer
Step 1 Log in to the VCS.

Server) A FAQs
1. Open the Cluster monitor.
a. Log in to the OS as user root.

b. Open a terminal window and run the following command:
# hagui&
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status is
STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Click Connect to Cluster name.
NOTE
If you are logging in to the VCS for the first time, create a new cluster.
1. Click File > New Cluster.
2. Enter the IP address of application network.
3. Click OK.
NOTE
new password.
4. Click OK.
Step 2 Exit the VCS:
Choose File > Log Out to exit the VCS.

Server) A FAQs
NOTICE
If the configuration changes, click Yes in the Confirmation dialog box when exiting the VCS.
Otherwise, logging in to the VCS fails after the server is restarted.
----End
A.4.2.2 How to Query the RVG Status
Question
How do I query the RVG status?
Answer
Step 1 Log in to the primary site as user root.
Step 2 Run the following command to view the RVG status of the active site:
# vxprint -Vl

Disk group: datadg
Rvg: datarvg
info: rid=0.1269 version=4 rvg_version=30 last_tag=3
state: state=ACTIVE kernel=ENABLED
assoc: datavols=lv_nms_data
srl=srl_vol
rlinks=datarlk
exports=(none)
vsets=(none)
att: rlinks=datarlk
flags: closed primary enabled attached
device: minor=31004 bdev=315/31004 cdev=315/31004 path=/dev/vx/dsk/datadg/
datarvg
perms: user=root group=root mode=0600
Table A-3 describes the RVG status of the primary site.
Table A-3 RVG status of the primary site
Field Description
Disk group Indicates the disk group where the RVG is located.
Rvg Indicates the name of the RVG.

Server) A FAQs
Field Description
info Indicates the information about the RVG.
state Indicates the status of the RVG. In normal cases, the situations are as follows:
l state is set to ACTIVE.
l kernel is set to ENABLED.
assoc Indicates the association information about the RVG.

l datavols indicates the data disk volume that the RVG contains.
l srl indicates the SRLog disk volume that the RVG contains.
l rlinks indicates the RLink that the RVG contains.
att Indicates the activated Rlink of the RVG.
flags Indicates the flag of the RVG. In normal cases, the value is closed primary
enabled attached.
device Indicates the device information of the RVG, including the device ID and path.
perms Indicates the right information about the RVG.
Step 3 Log in to the secondary site as user root.

Step 4 Run the following command to view the RVG status at the secondary site:
# vxprint -Vl
Disk group: datadg
Rvg: datarvg
srl=srl_vol
rlinks=datarlk
exports=(none)
vsets=(none)
att: rlinks=datarlk
flags: closed secondary enabled attached
datarvg
For the description of the RVG status on the secondary site, see Table A-3. Normally, flags on
the secondary site is closed secondary enabled attached.
----End
A.4.2.3 How to Query the Rlink Status
Question
How do I query the Rlink status?

Server) A FAQs
Answer
Step 1 Log in to the primary site as the root user.
Step 2 Run the following command to view Rlink names:

# vxprint -Pl

Disk group: datadg
Rlink: datarlk
info: timeout=500 packet_size=8400 rid=0.1113
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=ACTIVE
synchronous=off latencyprot=off srlprot=autodcm
assoc: rvg=datarvg
remote_host=192.168.10.82 IP_addr=192.168.10.82 port=4145
remote_dg=datadg
remote_dg_dgid=1356843347.7.linux
remote_rvg_version=30
remote_rlink=datarlk
remote_rlink_rid=0.1113
local_host=192.168.10.137 IP_addr=192.168.10.137 port=4145
protocol: UDP/IP
flags: write enabled attached consistent connected
NOTE
The datarlk in Rlink is an Rlink name.
Step 3 Run the following command to query the RLink status:
# vxprint -Pl <rlinkName>
For example, run the following command to query the status of datarlk:
# vxprint -Pl datarlk

Disk group: datadg
Rlink: datarlk
info: timeout=500 rid=0.1414
bandwidth_limit=none checksum=on
state: state=ACTIVE
assoc: rvg=datarvg
remote_dg=datadg
remote_dg_dgid=1160936796.6.T522022456
protocol: UDP/IP
flags: write enabled attached consistent connected asynchronous
Table A-4 describes the Rlink status on the primary site.

Server) A FAQs
Table A-4 Rlink status on the primary site
Field Description
Disk group Indicates the disk group where the Rlink is located.
Rlink Indicates the name of the Rlink.
info Indicates the information about the Rlink.

l timeout indicates the timeout period.
l rid indicates the ID of the Rlink.
l latency_high_mark indicates the highest delay flag.
l latency_low_mark indicates the lowest delay flag.
l bandwidth_limit indicates the bandwidth limit.
state Indicates the status of the Rlink. In normal cases, the situations are as follows:
l state is set to ACTIVE.
l synchronous is set to off.
l latencyprot is set to off.
l srlprot is set to autodcm.
assoc rvg Indicates the RVG where the Rlink is located.
remote_host Indicates the name of the remote host.
IP_addr Indicates the IP address of the remote host.
remote_dg Indicates the remote disk group.
port Indicates the port number of the remote host.
remote_dg_dgid Indicates the ID of the remote disk group.
remote_rvg_version Indicates the RVG version of the remote host.
remote_rlink Indicates the Rlink name of the remote host.
remote_rlink_rid Indicates the Rlink ID of the remote host.
local host Indicates the name of the local host.
protocol Indicates the protocol for synchronizing data. The protocols configured on
the primary and secondary sites must be the same.
flags Indicates the flag of the Rlink. Normally, the value is write enabled attached
consistent connected asynchronous.
Step 4 Log in to the secondary site as user root.
Step 5 Run the following command to query the Rlink status:
# vxprint -Pl <rlinkName>
For example, run the following command to query the datarlk status:

Server) A FAQs
# vxprint -Pl datarlk

Disk group: datadg
Rlink: datarlk
info: timeout=500 rid=0.1405
bandwidth_limit=none checksum=on
state: state=ACTIVE
assoc: rvg=datarvg
remote_dg=datadg
remote_dg_dgid=1160936853.6.T522022448
protocol: UDP/IP
flags: write enabled attached consistent connected
For the description of the Rlink status on the secondary site, see Table A-4.
----End
A.4.2.4 How to Query the VVR Status
Question
How do I query the VVR status during the maintenance of the Veritas HA system?
Answer
Step 1 Run the following command to view the rvg name of the replication system:
# vradmin printrvg
Primary:
HostName: 10.71.224.48
RvgName: datarvg
DgName: datadg
Secondary:
HostName: 10.71.224.50
RvgName: datarvg
DgName: datadg
In the preceding message, the rvg name (RvgName) is datarvg.

Step 2 Run the following command to view the Rlink name of the replication system. The parameter
datarvg is obtained in Step 1.
# vxprint -l datarvg
Disk group: datadg
Rvg: datarvg

Server) A FAQs

srl=srl_vol
rlinks=datarlk
exports=(none)
vsets=(none)
att: rlinks=datarlk
flags: closed primary enabled attached
datarvg
In the preceding message, the Rlink name (Rlink) is datarlk.

Step 3 Run the following commands to view other status information of the replication system. The
parameters datarvg and datarlk are obtained in Step 1 and Step 2.
l Run the # vxdisk list command to query the disk status.
l Run the # vxdg list command to query the status of the disk group.
l Run the # vxprint -ht command to query the information about the disk volume.
l Run the # vxprint -l datarvg command to query the RVG status.
l Run the # vxprint -l datarlk command to query the Rlink status.
l Run the # vxrlink -g datadg status datarlk command at the primary site to query the
replication cache status.
Save the response to the preceding commands.
----End
A.4.2.5 How to check whether the VCS service has been started
Question
How to check whether the VCS service has been started?
Answer
Step 1 Run the following command to check whether the VCS service has been started:
# ps -ef | grep had

root 5852 1 0 07:14:51 ? 0:00 /opt/VRTSvcs/bin/hashadow
root 5842 1 0 07:14:45 ? 1:36 /opt/VRTSvcs/bin/had -onenode
NOTE
If the displayed information contains /opt/VRTSvcs/bin/hashadow and /opt/VRTSvcs/bin/had -
onenode, the VCS service has been started.
----End
A.4.2.6 How to Manually Start the VCS Service
Question
How do I manually start the VCS service?

Server) A FAQs
Answer
Step 2 Run the following command to start the VCS processes:

# hastart -onenode
----End
A.4.2.7 How to Manually Start the VVR
Question
How do I manually start the VVR?
Answer
Step 2 Run the following commands to start the VVR:
# cd /etc/init.d
# ./vras-vradmind.sh start
----End
A.4.2.8 How to Manually Stop the VCS Service
Question
How do I manually stop the VCS service?
Answer
Step 2 Run the following command to check whether the VCS service has been started:
# ps -ef | grep had

root 5852 1 0 07:14:51 ? 0:00 /opt/VRTSvcs/bin/hashadow
root 5842 1 0 07:14:45 ? 1:36 /opt/VRTSvcs/bin/had -onenode
NOTE
If the displayed information contains /opt/VRTSvcs/bin/hashadow and /opt/VRTSvcs/bin/had -
onenode, the VCS service has been started. Perform Step 3. Otherwise, the follow-up operation is not
required.
Step 3 Optional: Run the following command to stop the VCS service:
# hastop -all -force
----End

Server) A FAQs
A.4.2.9 How to Start/Stop the NMS Before Synchronizing the Primary and
Secondary Sites (Solaris, PC Linux)
Question
How to start/stop the NMS before synchronizing the primary and secondary sites of a high
availability system (Solaris, PC Linux)?
Answer
l GUI mode:
2. Open a CLI.
# hagui&
NOTE
If the OS was just restarted, wait 10 to 15 minutes. After the process starts, run the hagui&
command.
4. Choose File > New Cluster. Then, enter the server IP address and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the
information list in the Cluster Monitor window.
NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure
system security, change the default password in time. If the default password has been changed,
enter the new password.
6. Ensure that the datarvg resource in the VVRService resource group has been enabled.
Right-click the datarvg resource and check whether the Enabled option is selected.
If this option is selected, it has been enabled.

Server) A FAQs
If this option is not selected, select it.
In the dialog box that is displayed, click Yes.

7. Ensure that the VVRService resource group has been started.
Select the VVRService resource group, click the Status tab, and check whether the
value in the State column is Online. If Online is displayed as shown in the following
figure, the VVRService resource group has been started.
If the VVRService resource group has not been started, do as follows to start it:
a. Right-click the VVRService resource group and choose Online > host name
from the shortcut menu.
b. In the dialog box that is displayed, click Yes to make the resource group online.
8. Ensure that all resources in the AppService resource group have been enabled.
Right-click a resource in the AppService resource group and check whether the
Enabled option is selected. If this option is selected, the resource has been enabled.

Server) A FAQs
If this option is not selected, you must select it. Repeat this operation on every resource
in the AppService resource group.
9. Optional: Ensure that Autoenable of the AppService resource group has been grayed
out, as shown in the following figure.
– If Autoenable has been grayed out, no action is required.

– If Autoenable has not been grayed out, click Autoenable to gray it out.
10. Click File > Save Configuration to save the settings.
11. Start the AppService resource group.
a. Right-click the AppService resource group and choose Online > host name from
the shortcut menu.
b. In the dialog box that is displayed, click Yes to start the AppService resource
group.
Select the AppService resource group and click the Status tab to view the status
for the resource group in the State column. If the resource group is in the
Online state, it AppService has started.

Server) A FAQs
NOTICE
If an exclamation mark is displayed for the NMSServer icon, restart the VCS client
several times until the exclamation mark disappears. For details about how to restart
the VCS client, see Step 2 to 5.
NOTE
To stop the AppService resource group, perform the following steps:
1. Right-click the AppService resource group and choose Offline > host name from the
shortcut menu.
2. In the dialog box that is displayed, click Yes to stop the AppService resource group.
l CLI mode:
2. Run the following commands to start the U2000 server:
# haconf -makerw > /dev/null 2>&1
# hares -modify datarvg Enabled 1
# hares -modify DatabaseServer Enabled 1
# hares -modify BackupServer Enabled 1
# haconf -dump -makero
NOTE
To stop the U2000 service, run the following command:
----End
A.4.2.10 How to Ensure Proper Connection of VVR Ports on Primary and Secondary
Sites
Question
How to ensure proper connection of VVR ports on primary and secondary sites?
Answer
Step 1 Log in to the OSs of the primary and secondary sites of as the root user.
Step 2 Run the following commands on the primary and secondary sites to check whether the VVR
ports used by the peer site can be connected properly:
NOTE
The numbers of the ports to be checked are 4145, 8199, and 8989.
# cd /opt/install/OSSICMR/bin
# chmod 750 Hacheck.sh
# ./Hacheck.sh Peer site system IP address
Peer ossuser user password.
If the command output indicates that the ports with the numbers of 4145, 8199, and 8989 are
used correctly, the VVR ports are connected properly.
----End

Server) A FAQs
A.4.2.11 How to Change the admin User Password for Logging In to the VCS Client
Question
How to I change the admin user password for logging in to the VCS client?
Answer
Step 1 Log in to the server OS as the root user.
Step 2 Ensure that the VCS service has started. If the VCS service is not started, run the following
command to start it:
# hastart -onenode
Step 3 Run the following command to enable the VCS to be configurable:

# haconf -makerw > /dev/null 2>&1
Step 4 Run the following commands to change the admin user password:
# /opt/VRTSvcs/bin/hauser -update admin
# Enter Password:
Enter a new password.

# Enter Again:
Enter the new password again.

# haconf -dump -makero
----End
A.5 Sybase Database

This topic covers FAQs about the Sybase database.
A.5.1 Startup and Shutdown of the Sybase Database

This topic describes the FAQs about the startup and shutdown of the Sybase database.
A.5.1.1 How to Disable the Sybase Database Service
Question
How do I disable the Sybase database service?
Answer
Step 1 Perform the following operations to disable the Sybase database service at the primary site in
the HA system:
NOTE
By default, the Sybase database service at the secondary site is not running.
l GUI mode:

Server) A FAQs
1. Log in to the primary site as user root.

2. Run the following command to start the VCS client at the primary site:
# hagui&
3. Choose File > New Cluster from the main menu. In the window that is displayed, enter
the IP address of the server and click OK.
NOTE
4. Enter the default user name admin and the initial password Changeme_123 for the
VCS client. For system security, modify the default password and remember the new
password. For detail, see A.4.2.11 How to Change the admin User Password for
Logging In to the VCS Client. Then click OK.
5. On the VCS client of the primary site, right-click the NMSServer node and choose
Offline > hostname from the shortcut menu.
6. In the confirmation dialog box, click Yes.
7. After the NMSServer node is dimmed, right-click the BackupServer node and choose
9. After the BackupServer node is dimmed, right-click the DatabaseServer node and
choose Offline > hostname from the shortcut menu.
l CLI mode:
2. Run the following command to shut down the U2000:
# hares -offline NMSServer -sys hostname
3. Run the following command to disable the Sybase database service:
# hares -offline BackupServer -sys hostname
# hares -offline DatabaseServer -sys hostname
NOTE
Run the following command to check whether the Sybase database service is disabled:
# ps -ef | grep sybase
If the following message is displayed, the Sybase database service has been disabled:
root 9629 14603 0 07:46:52 pts/3 0:00 grep sybase
----End
A.5.1.2 How to Start the Sybase Database Service
Question
How do I start the Sybase database service?

Server) A FAQs
Answer
l Perform the following operations to start the Sybase database service in the HA system:
– GUI mode:
1. Log in to the active site as the root user.
# hagui&
3. Choose File > New Cluster from the main menu. In the dialog box that is
displayed, enter the server IP address and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the
information list in the Cluster Monitor window.
4. Enter the default user name admin and the initial password Changeme_123 for
the VCS client. For system security, modify the default password and remember
the new password. For detail, see A.4.2.11 How to Change the admin User
Password for Logging In to the VCS Client. Then click OK.
5. Ensure that all Veritas resources are in Enabled state. Use the BackupServer
resource as an example. Perform the following operations:
Expand the AppService node and then the SybaseBk node in the navigation tree,
right-click BackupServer, and check whether Enabled has been selected in the
shortcut menu. If Enabled has not been selected, select it.
6. Right-click BackupServer and choose Online > host name from the shortcut
menu.
Wait until the BackupServer and DatabaseServer resource icons on the
Resources tab page are bright, which indicates that the Sybase database service
has started.
– CLI mode:
2. Run the following commands to query Veritas resource names:
# haconf -makerw
# hares -list

APPBOND Primaster
BackupServer Primary
DatabaseServer Primary
NMSServer Primary
RVGPrimary Primary
datarvg Primary
mountRes Primary
wac Primary
3. Run the hares -modify resource name Enabled 1 command to change the status
of all Veritas resources to Enabled. Use the resource names displayed in the
previous command output as an example. Run the following commands to change
the status of all the Veritas resources to Enabled:
# hares -modify APPBOND Enabled 1
# hares -modify NMSServer Enabled 1

Server) A FAQs
# hares -modify RVGPrimary Enabled 1

# hares -modify mountRes Enabled 1
# hares -modify wac Enabled 1
4. Run the following command to start the Sybase database service:

# hares -online BackupServer -sys hostname
NOTE
hostname specifies the server name. You can run the hostname command to view the server
name.
----End
A.5.1.3 How to Verify That the Sybase Database Is Running
Question
How do I verify that the Sybase database is running?
Answer
Step 2 Enter the CLI and run the following commands to check the Sybase process status:
# su - dbuser
$ cd /opt/sybase/ASE*/install
$ ./showserver

UID PID PPID C STIME TTY TIME CMD
dbuser 4195 4170 0 18:42:26 ? 70:35 /opt/sybase/ASE-15_0/bin/
dataserver -ONLINE:1,0,0x6505fd2a, 10000000000, 0x18fc
backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install
dataserver -sDBSVR -d/opt/sybase/data/lv_master -e/opt
NOTE
If the displayed information contains /opt/sybase/ASE-15_0/bin/dataserver -ONLINE, /opt/sybase/
ASE-15_0/bin/backupserver -SDBSVR_back, and /opt/sybase/ASE-15_0/bin/dataserver -sDBSVR,
the Sybase database has been started.
----End
A.5.2 Sybase Database Maintenance

This topic describes the FAQs about the Sybase database maintenance.
A.5.2.1 How to Verify That the Sybase Database Has Been Installed
Question
How do I verify that the Sybase database has been installed?

Server) A FAQs
Answer
NOTE
l The Sybase database will be automatically installed when the U2000 is installed if the Sybase database
does not exist on the system.
l If the Sybase database exists on the system, a dialog box will be displayed asking you whether or not
you want to reuse the Sybase database. There is no need to reinstall the Sybase database if it is reused
(saves time, but not recommended).
l Consult with the computer administrator to see if the Sybase database has been installed.
l Verify that the installation directory and file of the Sybase database exist. A sample
directory is /opt/sybase.
l Verify that the version of the Sybase database is correct. For details, see A.5.2.2 How to
Check the Sybase Database Version.
l Verify that the Sybase database is running. For details, see A.5.1.3 How to Verify That
the Sybase Database Is Running. For details about how to start the Sybase database, see
A.5.1.2 How to Start the Sybase Database Service.
----End
A.5.2.2 How to Check the Sybase Database Version
Question
How do I perform the required check on the Sybase database version to see if it is correct after
the Sybase database is installed?
Answer
Step 1 Log in to the OS as user dbuser.
NOTE
l To switch to the dbuser user, run the su - dbuser command.

l After the U2000 is installed, the password for the dbuser user is Changeme_123. For system security,
modify the default password and remember the new password. For detail, see A.6.14 How to Change
the OS User Password.
Step 2 Run the following commands:

$ cd /opt/sybase/OCS*/bin
$ ./isql -SDBSVR -Usa
NOTE
Enter the password of the database administrator as prompted.

In order to enhance the security of the database after the U2000 is installed, the sa user may be manually
disabled and replaced with a customized administrator name, such as dbadmin.
Step 3 Run the following commands to check the Sybase database version:
1> use master
2> go
1> select @@version

Server) A FAQs
2> go
NOTE
There must be a space between select and @ in the select @@version command.

-----------------------
Adaptive Server Enterprise/15.5/EBF 21264 SMP ESD#5.3/P/x86_64/Enterprise Linux/

asear155/2613/64-bit/FBO/Web Jul 24 04:41:50 2013
(1 row affected)
The preceding message indicates that Sybase database version is SYBASE 15.5.
NOTE
EBF 21264 indicates the latest Sybase patch. The earlier Sybase patches are not displayed.
----End
A.5.2.3 How to View the Server Name of the Sybase Database
Question
How do I view the server name of the Sybase database?
Answer
NOTE

Step 2 Run the following command to view the server name of the Sybase database:
$ more /opt/sybase/interfaces

DBSVR
master tcp ether 10.71.225.89 4100
query tcp ether 10.71.225.89 4100
query tcp ether 10.71.225.89 4100
query tcp ether 127.0.0.1 4100
DBSVR_back
query tcp ether 10.71.225.89 4200
query tcp ether 10.71.225.89 4200
----End

Server) A FAQs
A.5.2.4 How to Change the sa User Password for the Sybase Database If the
U2000 Is Not Installed
Question
How to change the sa user password for the Sybase database if the U2000 is not installed?
Answer
NOTE


NOTE
Step 3 Run the following commands to change the sa user password for the Sybase database:
1> sp_password "old password","new password"
2> go

Server) A FAQs
NOTICE
l Be sure to remember the password of user sa. If this password is missed, database-related
operations may fail to be performed.
l The database sa user password must meet the following requirements, please set the new
password as required:
Other special characters are not supported. Do not include other special characters,
such as ()|<>&`!$\"%'=;,space in passwords.
l The password cannot be the same as the user name written in either the forward or
backward format.
l Leave a space between sp_password and old password.
l The "new password" and "old password" must be marked with double quotation marks during
password modification.
Information similar to the following will be displayed:

Setting password succeeded.
(return status=0)
1>
Step 4 Run the quit command to exit.
----End
A.5.2.5 How to Change the Database Administrator Password for the Sybase
Database If the U2000 Is Installed
Question
How to change the database administrator user password for the Sybase database if the U2000
is installed?

Server) A FAQs
NOTICE
l In the high availability system (Veritas hot standby), change the password of the
administrator of the database only on the MSuite server at the primary site. The passwords
of the administrator of the databases at both the primary and secondary sites are changed.
l After the U2000 is installed, using the MSuite to change the password of the database
administrator is recommended. Do not manually change the password. Otherwise, the U2000
may fail to be started properly. If the password of the database administrator is changed
manually, you must use the MSuite to change the password again to ensure the normal
operation of the U2000.
Answer
Step 1 Shut down the NMS server and client.
Log in to the primary site and run the following command to start the VCS client:
# hagui&
Choose File > New Cluster from the main menu. In the window that is displayed, enter the IP
address of the server and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information list in
the Cluster Monitor window.
Enter the user name and password for VCS login.

NOTE
security, change the default password in time. If the default password has been changed, enter the new
password.
Right-click NMSServer and choose Offline > Host name from the shortcut menu.
In the confirmation dialog box, click Yes.
NOTE
Ensure that the database is running.

NOTE
...

Server) A FAQs
NOTE
been started.
the MSuite servers:
# ./startserver.sh
Step 4 On the MSuite client, choose Deploy > Change Database Administrator Password. The
Change Password dialog box is displayed.
Step 5 Enter the old password, new password and confirm password.
NOTE
l The initial password is Changeme_123.

l If Allow using simple passwords is not selected (recommended to ensure the system security, not
selected by default), the password of the Sybase database and the SQL Server database must meet the
following strong password rules:
Other special characters are not supported. Do not include other special characters, such as ()|
<>&`!$\"%'=;,space in passwords.
l If Allow using simple passwords is selected, the password of the Sybase database and the SQL Server
database must meet the following weak password rules:
l The password consists of letters, digits, or underscores (_).
l If the Change Password dialog box is displayed, click OK.
Step 6 Click OK. The password is changed.

NOTE
If the following information is displayed, the password of the database administrator has been changed
successfully.
Succeeded in changing the password.
After changing the password of the database administrator, start U2000 server processes.
----End

Server) A FAQs
A.5.2.6 How to View the Bit Number of the Sybase Database
Question
How do I view the bit number of the Sybase database?
Answer
NOTE


NOTE

Step 3 Run the following commands to view the bit number of the Sybase database:
1>select @@version
2>go
NOTE
There must be a space between select and @ in the select @@version command.
The following message will be displayed on the SUSE Linux OS:

Adaptive Server Enterprise/15.5/EBF 21264 SMP ESD#5.3/P/x86_64/Enterprise Linux
/asear155/2613/64-bit/FBO/Wed Jul 24 04:41:50 2013
(1 row affected)
64-bit indicates the bit number of the Sybase database.
----End
A.5.2.7 How to View the Details of the Sybase Database
Question
How do I view the details about the Sybase database during routine maintenance?
Answer

Server) A FAQs
NOTE

Step 2 Run the following commands to view the details of all databases:
NOTE

1>sp_helpdb
2>go
The information about the Sybase database will be displayed, including the name, size, owner,
and status.
Step 3 Run the following commands to view the details of a specific database:
1>sp_helpdb database_name
2>go
NOTE
In the sp_helpdb database_name command, database_name is the name of the Sybase database.
Database space used can also be viewed.
----End
A.5.2.8 How to Create a Replacement User for the Sybase Database Administrator
sa User
This topic describes how to disable the Sybase database administrator (sa user by default) and
create a replacement user for the database administrator. Disabling the default database
administrator reduces potential security risks.
Prerequisites
l The database administrator sa has exited from the connection.
l The U2000 is stopped. For details about how to check whether the U2000 is stopped, see
E.1 Stopping the U2000 Server Processes.
l The database is started. For details about how to check whether the database is started, see
D.2 Starting the Database.

Server) A FAQs
Context
l To reduce the probability of security threats, you can disable the database administrator,
create a new database user to replace the database administrator, and assign the new user
with the same permissions as the database administrator.
l You can only manually disable the sa user and create a replacement user for the sa user
only after the U2000 is installed or upgraded.
l In a high availability system, you need to perform the following operations on both the
primary and secondary sites. Before the operations are performed, ensure that the primary
and secondary sites are separated.
Procedure
Step 1 Log in to the server as the root user.
Step 2 Perform the following operations to disable the sa user and create a new user to replace the sa
user.
1. Run the following commands to disable the sa user and create a new administrator:
# cd /opt/oss/engr/engineering/tool/modifyDBAUser/
# ./modifyDBAUser.sh
NOTE
The /opt/oss directory is the U2000 installation directory.
Please enter old database administrator account:
2. Enter the database administrator user name sa as prompted.

Please enter password of old database administrator account:
3. Enter the password of the sa user as prompted.

NOTE
The default password of the sa user is Changeme_123.
Please enter new database administrator account:
4. Enter the name of the new administrator as prompted, such as dbadmin.

NOTE
l The dbadmin user is used as an example of the new administrator of the database. The
administrator name can be customized as required. The customized user name must start with a
letter and can contain lower-case letters, digits, and special character _. The customized user
name contains a maximum of 16 characters.
l If the created user dbadmin already exists, this command assigns permissions to the new database
administrator. If the new password is different from the old password, the user password is reset.
Please enter password of new database administrator account:
Please confirm password of new database administrator account:
5. Enter the password of the new administrator as prompted.

Server) A FAQs
NOTE
The password of the new user must comply with the following requirements. To enhance system
security, you need to regularly update the password and keep it well.
Other special characters are not supported. Do not include other special characters, such as
()|<>&`!$\"%'=;,space in passwords.
l The password cannot be the same as the user name written in either the forward or backward
format.
If the following information is displayed, the replacement user for the sa user is created
successfully.
Success to modify dba user.
----End
Result
Check whether the replacement user for the sa user is successful.
1. Log in to the server as the dbuser user.

2. In the CLI, run the following commands to check whether the sa user is disabled.

Password:
Enter the password of the sa user.

If information similar to the following is displayed, the sa user is disabled.
CT-LIBRARY error:
ct_connect(): protocol specific layer: external error: The attempt to
connect to the server failed.
3. In the CLI, run the following commands to check whether the dbadmin user is created
successfully:
$ ./isql -SDBSVR -Udbadmin
If information similar to the following is displayed, enter the password of the dbadmin
user.
Password:
If the database can be connected properly, the dbadmin user is created successfully.
Follow-up Procedure
If the database administrator sa needs to be restored, refer to the preceding operations to disable
the existing database administrator and use the sa user as the new database administrator.

Server) A FAQs
NOTICE
l Enter the existing database administrator name (such as dbadmin) and password and then
the database administrator name sa and the password to be restored.
l The password of the database administrator sa to be restored is the one that is not disabled.
The password cannot be set randomly.
A.6 U2000 System

This topic covers FAQs about the U2000 system.
A.6.1 Failure to Start Certain Processes of the U2000 Server
Symptom
On the System Monitor client, certain processes of the U2000 server are not running.
Possible Causes
l The server IP address is changed incorrectly. As a result, the configuration of IP addresses
in certain processes is not refreshed accordingly.
l The password of the database administrator is incorrect or not changed properly; as a result,
some processes fail to be started.
l These processes are not configured properly. For example, the NBI processes are not
configured in advance.
l Licenses are not obtained and updated for the relevant functions.
l Ports are occupied.
l The memory configurations of the U2000 server do not meet running requirements. As a
result, some processes fail to start. For example, if the memory of the T5220 workstation
is smaller than 8 GB, the desktop server process may fail to start.
l If 360 software has been installed on the site, some U2000 files will be deleted; as a result,
the process cannot be started.
Procedure
Step 1 On the System Monitor client, manually start the processes that are currently not started to check
whether the failure recurs or whether relevant messages are displayed.
Step 2 Restart the U2000 and check whether the processes are started.
Step 3 Check whether the server IP address is changed. If the IP address is changed, ensure that it is
changed according to the related operation guide. If the IP address is changed incorrectly, restore
to the previous setting and then change the IP address again. For details, see section "Changing
the System IP Address and Host Name" in the U2000 Administrator Guide.
Step 4 Check whether the password of the database administrator has been manually changed. If so,
use the MSuite to change the password again.

Server) A FAQs
Step 5 Ensure that licenses are obtained and updated for the relevant functions.
Step 6 If a process, such as the CORBA NBI process, fails to be started, check the NBI settings or re-
configure the NBI.
Step 7 Check whether the ports used by these processes are occupied.
Step 8 If the server is switched off illegally or powered off or the database has been restored, it is
recommended that you initialize the database and restore data. Then, restart the U2000 server.
Step 9 Check whether the hardware configurations of the U2000 server meet requirements. For the
requirements, see the U2000 Planning Guide. If the hardware configurations do not meet
requirements, replace the U2000 server.
Step 10 If this problem persists after the preceding operations, contact Huawei engineers.
Step 11 If the 360 software does not function properly, uninstall the 360 software and re-install the
U2000.
----End
Suggestion and Summary

l When changing the IP address, follow the related operation guide. Otherwise, the U2000
may malfunction.
l Starting or stopping the U2000 as the ossuser user is recommended.
A.6.2 How to Determine Whether an Installed SUSE Linux System

is a Local or Remote High Availability System
Question
How do I determine whether an installed SUSE Linux system is a local or remote high availability
system?
Answer
Step 1 Log in to the SUSE Linux high availability system on the primary or secondary site as the
root user.
Step 2 Run the following command to view the high availability system type on the current server:
# cat /var/ICMR/sles10sp4_sign_file.inf

installtype=3
hatype=2

Server) A FAQs
NOTE
l If the command output contains installtype=1, the system is a single-server system. If the command
output contains installtype=3, the system is a high availability system.
l If the command output contains hatype=1, the system is a local availability system. If the command
output contains hatype=2, the system is a remote system.
For example, if the command output contains installtype=3 and hatype=2, the system is a remote high
----End
A.6.3 How to Start the MSuite Client
Question
How do I start the NMS maintenance suite client?
Answer
It must meet the following requirements for starting the NMS maintenance suite client:
l The MSuite server must be started.

l Port 12212 on the MSuite server is enabled.
l The MSuite client and the server communicate with each other properly.
l The MSuite server process is started on both the primary and secondary sites during some
operations in the high availability system, and the MSuite client can properly communicate
with the MSuite server on both the primary and secondary sites.
In SUSE Linux OS, run the following command as user root to verify that the MSuite
server is running:
The MSuite server is running if /opt/oss/OSSJRE/jre_linux/bin/java -server is displayed.

Run the following commands to start the MSuite server if it is not running:
# ./startserver.sh
2. On a computer where the MSuite client is installed, double-click the U2000 NMS
Maintenance Suite shortcut icon on the desktop and then wait about one minute. The
Login dialog box is displayed.
NOTE
l If a dialog box showing The client and server versions are different. Upgrade the client using
the CAU. is displayed, the method of upgrading the U2000 client by using the CAU is as follow:
1. Install the U2000 client software in network mode: Enter https://server_IP_address/cau/
(more secure, recommended) or http://server_IP_address/cau/ in the address box of the
Internet Explorer, and press Enter to access the Web installation page. For details, see U2000
Client Software Installation Guide in the U2000 Client Software Installation Guide.
2. If you upgrade the U2000 client software using the CAU, the MSuite client is also upgraded.
3. Set the login parameters.
l IP Address:
– To log in to the local MSuite server, use the default IP address 127.0.0.1.

Server) A FAQs
– To log in to the remote MSuite server, enter the IP address of the computer where
the MSuite server is installed. If multiple IP addresses are configured for the
computer, use the NMS application IP address.
NOTE
The Login dialog box of the MSuite client has the function to keep the login list. Selecting an IP
address from the IP Address drop-down list is recommended. If the desired IP address is not
displayed in the drop-down list, enter an IP address.
l Port: The default port ID is 12212. There is no need to change the default value during
login but ensure that the port is not occupied.
l User Name: The default user name is admin.
l Password: The initial password of the admin user is Changeme_123 (It is Admin_123
for a U2000 that comes preinstalled). The password must be changed during the first
login to ensure system security. Keep the password confidential and change it regularly.
4. Click Login.
NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of Refresh
Deployment Information. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the
MSuite at one time.
A.6.4 Changing the Password of the MSuite

This topic describes how to change the password of the MSuite. To ensure the security of the
U2000, change the password of the MSuite immediately and record the password after installing
the U2000 server.
Context
In the high availability system, you only need to log in to the MSuite server on the primary site
and change the password of the MSuite. The password of the MSuite on the secondary site is
then automatically changed.
Procedure
Step 2 On the MSuite client, choose System > Change Password from the main menu. The Change
Password dialog box is displayed.
Step 3 Click OK. The Change Password dialog box is displayed.
Step 4 Enter the old password and new password.

Server) A FAQs
NOTE
The initial password is Changeme_123.

The rules for modifying a password are as follows:
l The password must contain four of the following combinations:
If the password does not meet requirements, an error message will be displayed.
Step 5 Click OK. The password is changed.
----End
A.6.5 How to Check Whether the U2000 Processes of the High

Availability System (Solaris, PC Linux) Are Started
Question
How to check whether the U2000 processes of the high availability system (Solaris, PC Linux)
are started?
Answer
Step 1 Log in to the OS of the active site as the ossuser user.
Step 2 Check the U2000 processes.
Run the following command to check whether the U2000 is running:

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start. If no
introduction is displayed, the U2000 processes have been stopped.
----End

Server) A FAQs
A.6.6 How to Start the U2000 Processes of the High Availability

System (Solaris, PC Linux)
Question
How do I start the U2000 processes of the high availability system (Solaris, PC Linux)?
Answer
Step 1 Log in to the OS on the active site as the root user.
Step 2 Start the U2000 server processes.

l GUI mode:
1. Open a terminal window and run the following command:
# hagui&
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status
is STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Choose Connect to cluster name.
NOTE
1. Choose File > New Cluster.
2. Enter an application network IP address.
3. Click OK.
NOTE
4. Click OK.
5. In the Cluster Explorer window, select the NMSServer resource group in the
navigation tree, right-click, and choose Online > primary from the shortcut menu to
start the U2000 server processes.

Server) A FAQs
NOTE
Click the Resources tab to view the start status of each resource.
Normally, the value of State for the active site is Online in the Group Status on
Member Systems area on the Status tab page, and the value of Status is Online on
primary in the Resource Status area.
NOTE
l Use the actual host name for real-world configuration.

l If a fault has occurred during the start of the AppService process, right-click AppService and
choose clear fault from the shortcut menu to rectify the fault. Then choose Online > host name
to start the process.
l CLI mode:
# hares -online NMSServer -sys hostname
----End
A.6.7 How to End the U2000 Processes of the High Availability

System (Solaris, PC Linux)
Question
How do I end the U2000 processes of the high availability system (Solaris, PC Linux)?
Answer
Step 1 Log in to the OS of the active site as the root user.
Step 2 Stop the U2000 server processes.

l GUI mode:
1. Open a terminal window, run the following command:
# hagui&
NOTE

Server) A FAQs

NOTE
If you are logging in to the VCS for the first time, you need to create a new Cluster.
3. Click OK.
NOTE
4. Click OK.
5. Choose AppService from the navigation tree.
6. Click the Resources tab. Right-click NMSServer and choose Offline > Host name
from the shortcut menu.
Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes
have been stopped.
l CLI mode:
----End
A.6.8 How to Determine Which Types of Software Are Preinstalled
Question
Servers come preinstalled with software from Huawei. The U2000 servers come preinstalled to
different extents according to the scheme and software purchased. How do I determine which
types of software are preinstalled?
Answer
The U2000 is installed based on the BOM.
l If the U2000 license BOM is available, the U2000 HA system needs to be installed
according to the license BOM while the primary site and secondary site are separated as
much as possible. Technical support engineers need to change the IP address, check that
the network between the primary site and secondary site is functioning properly, and then
connect the two sites.
l If the U2000 license BOM is unavailable, only the OS needs to be installed.
A.6.9 Which Installation Packages Are Required for U2000

Installation
Question
Which installation packages are required for U2000 installation?

Server) A FAQs
Answer
Prepare installation packages according to the U2000 installation scheme.
Table A-5 Software package list
SUSE Linux Quick OS installation DVD It must be available. It is used to

OS Disk U2000version_server_os_sles_x64 install the SUSE Linux OS.
_dvd1 or ISO image file of the quick
installation DVD
U2000version_server_os_sles_x64
_dvd1.iso.
Quick RAID l For Huawei RH series rack It must be available. It is used to

configuratio server, the configure RAID.
n DVD Sles_server_raid_x64_for_Hua
wei_dvd.iso file is must be ready.
l For IBM server, the ISO image
file
Sles_server_raid_x64_for_IBM
_dvd.iso is must be ready.
SetSuse Installation package: It must be available. It is used to

software U2000version_ enhance the security of SUSE Linux
package VPPSetSuseV300R003C20SPC100 OS.
.tar
Database Database software package: It must be available. It is used to

software U2000version_ install the database.
package server_db_linux_sybase.tar
Veritas 1. Veritas software installation It must be available. It is used to

software package: install the Veritas.
U2000version_
veritas6.0.1_sles_x64.tar.gz
2. Veritas patch package:
U2000version_
server_veritas603_patch_sles_x
64.tar
U2000 Basic component: It must be available. It is used to

server U2000version_ install the U2000.
software server_nmsbase_sles_x64.7z
Preconfigured component: It must be available. It is used to

server_icmr_sles_x64.7z
Core component: It must be available. It is used to

server_nmscore_sles_x64.7z

Server) A FAQs
Transport component: It must be available. Huawei

U2000version_ transport equipment includes:
server_nmstrans_sles_x64.7z l MSTP equipment
l WDM equipment
l NA WDM equipment
l Submarine equipment
l RTN equipment
l PTN equipment
IP component: It must be available. Huawei IP

server_nmsip_sles_x64.7z l ATN Series Equipment
l Routers
l Switches
l Metro service equipment
l Broadband access equipment
l VoIP gateways
l Firewalls
l Service inspection gateway
l SVN equipment
l Internet Cache System
Access component: It must be available. Huawei access

server_nmsaccess_sles_x64.7z l FTTx equipment
l MSAN equipment
l DSLAM equipment
l BITS equipment
ESN tool ESN tool: The ESN tool is required only when
U2000version_ESN_sles_x64.tar you apply for the U2000 License
NOTE
The tool is a software package. It will not
be delivered as a DVD-ROM. After the
U2000 is installed, the ESN tool is
available in the U2000 installation path.
Therefore, to apply for the U2000 license
after the U2000 is installed, use the ESN
tool in this path directly.

Server) A FAQs
Table A-6 DVD list

Software DVD Name
SUSE Linux OS Quick installation DVD 1:

installation DVD U2000version_server_os_sles_x64_dvd1
Quick RAID l For Huawei RH series rack server, the

configuration DVD Sles_server_raid_x64_for_Huawei_dvd.iso file is must be
ready.
l For IBM server, the ISO image file
Sles_server_raid_x64_for_IBM_dvd.iso is must be ready.
Database software U2000version_server_db_sles_x64_dvd3

DVD
Veritas software DVD 1. Veritas software installation DVD: Sles_Veritas6.0.1

2. Veritas patch DVD:
U2000version_server_patch_sles_x64_dvd2
U2000 server software U2000version_server_nms_sles_x64_dvd4

DVD NOTE
U2000 server software include SetSuse software package, it is used to
enhance the security of SUSE Linux system.
ESN tool U2000version_ESN_sles_x64.tar

The ESN tool is required only when you apply for the U2000
License before installing the U2000.
NOTE
The tool is a software package. It will not be delivered as a DVD-ROM. After
the U2000 is installed, the ESN tool is available in the U2000 installation
path. Therefore, to apply for the U2000 license after the U2000 is installed,
use the ESN tool in this path directly.
A.6.10 How to View Network Configurations for the Primary Site

or Secondary Site Installed with a HA System (SUSE Linux)
Question
How do I view network configurations for the primary site or secondary site installed with a
high availability (HA) system?
Answer
NOTE
The following uses viewing configurations for the primary site as an example. Viewing configurations for the
secondary site is similar to that for the primary site.
Step 1 Log in to the OS of the primary site as user root.

Step 2 View the vcs_net_config.cfg file. Saving this file to a local disk is recommended.
Run the following commands to view the vcs_net_config.cfg file:

Server) A FAQs
# cd /etc/ICMR/netCfg/VCS/
# more vcs_net_config.cfg

...
#The following are config item meannings

ClearFlag=yes
SystemIP=129.9.1.1
SystemHostname=Primary
SystemNetmask=255.255.255.0
SystemNic=eth0
SystemRouter=129.9.1.254
SystemMAC=34:40:b5:b1:11:08
...
HBCFG=yes
HBIP=192.168.10.10
HBNic=eth1
HBHostname=Primary
HBNetmask=255.255.255.0
HBMAC=34:40:b5:b1:11:0a
...
# To use another NIC to back up PHBNic, configure the following parameters.
HBIsIPMP=yes
HBStandbyNic=eth2
HBStandbyIP=129.9.1.2
HBStandbyNetmask=255.255.255.0
HBStandbyHostname=HBSlave
HBStandbyMAC=90:e2:ba:17:94:84
HBBondName=bond1
#VVR network configure, support the ipmp

VVRCFG=yes
VVRIP=192.168.10.10
VVRNic=eth1
VVRHostname=VVRService
VVRNetmask=255.255.255.0
VVRMAC=34:40:b5:b1:11:0a
VVRMasterNic=eth1
VVRMasterIP=192.168.10.10
VVRMasterHostname=VVRMaster
VVRMasterNetmask=255.255.255.0
VVRMasterMAC=34:40:b5:b1:11:0a
VVRMasterRouter=
# To use another NIC to back up PHBNic, configure the following parameters.

VVRIsIPMP=yes
VVRStandbyNic=eth2
VVRStandbyIP=192.168.10.11
VVRStandbyHostname=VVRSlave
VVRStandbyNetmask=255.255.255.0
VVRStandbyMAC=90:e2:ba:17:94:84
VVRBondName=bond1
#APP network configure, support the ipmp
APPCfg=yes
APPIP=129.9.1.1
APPNic=eth0
APPHostname=Primary
APPNetmask=255.255.255.0
APPMAC=34:40:b5:b1:11:08
APPMasterNic=eth0

Server) A FAQs
APPRouter=
APPMasterIP=129.9.1.1
APPMasterHostname=APPMaster
APPMasterNetmask=255.255.255.0
APPMasterMAC=34:40:b5:b1:11:08
# To use anther NIC to back up the HBNic, configure the following parameters.
APPIsIPMP=yes
APPStandbyNic=eth0
APPStandbyIP=129.9.1.2
APPStandbyNetmask=255.255.255.0
APPStandbyHostname=APPSlave
APPStandbyMAC=90:e2:ba:17:94:85
APPBondName=bond0
FLOATAPPIP=129.9.1.3
FLOATIP=129.9.1.3
FLOATHostname=null
FLOATNetmask=255.255.255.0
FLOATMasterNic=34:40:b5:b1:11:08
...
The preceding information shows the system IP address, the host name, the subnet mask, the
default route, and the relationships between the system IP address and the heartbeat network,
replication network, and NMS application network. Details are as follows:
l SystemIP=129.9.1.1: The system IP address is 129.9.1.1.

l SystemHostname=Primary: The system host name is Primary.
l HBCFG=yes: It needs to set a heartbeat IP address. The heartbeat IP address is
192.168.10.10.
l VVRCFG=yes: It needs to set a replication IP address. The replication IP address is
192.168.10.10. The replication IP address is used as the heartbeat IP address.
l VVRBondName=bond1: The bone name of the replication bond solution is bond1.
l APPCfg=yes: The application IP address needs to be set. The application IP address is
129.9.1.1. The application IP address is used as the system IP address (It needs to set an
application IP address). The application IP address is used as the system IP address.
l APPBondName=bond0: The bone name of the application bond solution is bond0.
Step 3 Run the following command to view and record routing information:
# netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
129.9.1.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 bond1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 129.9.1.1 255.255.255.0 UG 0 0 0 bond0
0.0.0.0 192.168.10.1 255.255.255.0 UG 0 0 0 bond1
----End

Server) A FAQs
A.6.11 How to Check Downloaded Software Packages by Using

HashMyFiles Software
Question
How do I check downloaded software packages by using HashMyFiles software?
Answer
Step 1 Download the iManager U2000 version MD5 CODE(English) file from http://
support.huawei.com. The iManager U2000 version MD5 CODE(English) file contains MD5
code information after all software and document packages are decompressed.
NOTE
Take the following method to obtain the iManager U2000 version MD5 CODE(English) file. Only Huawei
engineers can download the file. If the customer requires using the file, please contact Huawei engineers for
help.
2. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManager
U2000 > iManager U2000 > desired U2000 version.
Step 2 Optional: If the U2000 is installed on Huawei RH series rack server, download the Tecal
ServiceCD V100R001C00SPC800.part1.rar.sha256 and Tecal ServiceCD
V100R001C00SPC800.part2.rar.sha256 files from the Support website. The files contain
informationa bout the sha256 codes of the ServiceCD software compression package.
NOTE
The sha256 code file of the ServiceCD software compression package can be obtained using the following
method:
1. Log in to http://enterprise.huawei.com.
2. Choose SUPPORT > Software Downloads > Cloud Computing & Data Centers > Software >
IT > Server > APP Server > FusionServer Tools > V100R001C00SPC600.
3. Download the Tecal ServiceCD V100R001C00SPC800.part1.rar.sha256 and Tecal ServiceCD
V100R001C00SPC800.part2.rar.sha256 files.
Step 3 Navigate to http://www.nirsoft.net and download the HashMyFiles. For more information
about software operation, see the software Help or go to the official website of the software for
technical support.
Step 4 Run the HashMyFiles.
Step 5 Drag the compression files downloaded from the local PC to the HashMyFiles tool. Compare
the password information contained in the compression package automatically generated and
downloaded by the tool and the verification information in the password file downloaded from
the Support website.

Server) A FAQs
NOTE
l For the Tecal ServiceCD V100R001C00SPC800.part1.rar and Tecal ServiceCD

V100R001C00SPC800.part2.rar software packages, the sha256 codes in the Tecal ServiceCD
V100R001C00SPC800.part1.rar.sha256 and Tecal ServiceCD
V100R001C00SPC800.part2.rar.sha256 files need to be compared. For other software packages, the
MD5 code informoation in the iManager U2000 version MD5 CODE(English) file needs to be
compared.
l You can use the following method to obtain the MD5 code information in the compression packages:
1. Choose Files > Add Folder from the main menu to access the Select Folder dialog box.
2. Select the folder in which the compression packages are stored and click OK.
3. After the MD5 code information is loaded, the tool automatically generates the password
information of the comparession package downloaded from the local PC. Choose View > HTML
Report All Items to export the password information and compare the exported information with
the verification information downloaded from the Support website.
l If they are the same, the downloaded file is correct.
l If they are different, re-download the software package.
----End
A.6.12 How to Set the Communication Mode of the Server in a High

Availability System (Solaris, SUSE Linux)
Question
The server in a high availability system (Solaris, SUSE Linux) has two communication modes,
namely, common and Security Socket Layer (SSL). How to set the common or SSL mode?
Answer
Step 1 Log in to the OS on the servers of the primary and secondary sites as the ossuser user and run
the following commands to query the communication mode in use:
$ ssl_adm -cmd query
Step 2 Stop U2000 processes.

1. Access the OS of the server on the Active Site as the ossuser user.
2. To start the VCS client, run the following command:
$ hagui&
3. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.

Server) A FAQs
NOTE
4. Enter the IP address for the Heartbeat network service on the primary site. Then, click
OK.

NOTE
new password.
6. Select the AppService > Application resource from the navigation tree, click the Status
tab, and then view the status of the U2000 processes.
l If the value of State is Offline, the U2000 processes are stopped.
l If the value of State is Online, the U2000 processes are started. Do as follows to stop
U2000 processes: choose AppService from the navigation tree. Click the Resources
tab. Right-click NMSServer and choose Offline > Host name from the shortcut menu.
have been stopped.
Step 3 Run the following commands on the servers of the primary and secondary sites to set the
communication mode of the server:
$ ssl_adm -cmd setmode mode parameter

Server) A FAQs
NOTE
The available options for mode parameter are common, ssl, and both.
l common: common mode. If mode parameter is set to common, the U2000 server and client can
communicate only in common mode, and http protocol must be used to download the U2000 client in
CAU mode.
l ssl: security mode. If mode parameter is set to ssl, the U2000 server and client can communicate only
in security mode, and https protocol must be used to download the U2000 client in CAU mode. The
security mode is recommended to ensure security for communication between the U2000 server and
client.
l both: indicates that the U2000 server and client can communicate with each other in either common
or SSL mode.
If the following information is displayed, the communication mode of the server has been set
successfully.
Operation succeeded. Please restart all services for the settings to take effect.
NOTE
Ignore information that is displayed before this information because the operation result is not be impacted.
Step 4 In the Cluster Explorer window, right-click the AppService resource group in the navigation
tree and choose Online > hostname from the shortcut menu to start the U2000 server process.
NOTE
Normally, on the Status tab page, Online is displayed for State in the Group Status on Member
Systems area on the Active Site, and Online on primary is displayed for Status in the Resource
Status area.
NOTE
l In actual configuration, use the actual host name.

l If a fault has occurred during start of the AppService process, right-click AppService and choose clear
fault from the shortcut menu to clear the fault. Then, choose Online > host_name to start the AppService
process.
Step 5 In the dialog box that is displayed, click Yes.
----End
A.6.13 How to Confirm the Encoding Format of the U2000 License

File
Question
How do I confirm the encoding format of the U2000 license file?
Answer
The encoding format of the U2000 license file must be UNIX, not DOS.
l If the SUSE Linux OS is used, perform the following operations to confirm the encoding
format of the U2000 license file:

Server) A FAQs
2. Run the cd License file save path command to access the path where the license file
is stored.
3. Run the vi License file name.dat command to open the U2000 license file.
For example, assume that the U2000 license file name is license.dat, run the vi
license.dat command.
– If dos is contained in the last line of the window for viewing license.dat, for
example,
"license.dat" [noeol][dos] 163L, 13496C
The file is in the DOS format. Run the :q command and press Enter to exit from
the vi command. Then run the following command to change the format of the
U2000 license file from DOS to UNIX.
# dos2unix license.dat license.dat
– If dos is not displayed in the last line of the license.dat file, for example,
"license.dat" [noeol] 163L, 13496C
The file is in the UNIX format.
----End
A.6.14 How to Change the OS User Password
Question
How to change the OS user password?
Answer
l Method 1:
1. Log in to the OS.
NOTE
The login user is the user whose password needs to be changed.

2. Open the command terminal, run the following command to set the OS user password:
passwd
3. Enter a new password as prompted, for example, Changeme_123.

To ensure the security of the U2000, passwords must be complex enough. For
example, a password must contain eight or more characters of two types. The allowed
characters are digits, letters, and special characters. Remember to change passwords
regularly.
NOTE
Any character that you enter using the keyboard will be considered a password component,
including Backspace. For example, if you enter the string cBackspaceChangeme_123, the
password is cBackspaceChangeme_123, but not Changeme_123.
4. Enter the new password again as prompted. Press Enter to make the change take
effect.

Server) A FAQs
NOTICE
After the new password takes effect, do not close the CLI.
Open another CLI and log in using the new password to verify the new password. If
the new password is correct, close all the CLIs. If the new password is incorrect, repeat
the preceding steps to change the password again.
l Method 2: (used when the ossuser or dbuser user fails to log in to the OS because the user
password is forgotten or the user password expires)
2. Open the command terminal, run the following command to set the OS user password:
# passwd OS user
For example, passwd ossuser.

3. Enter a new password as prompted, for example, Changeme_123.
To ensure the security of the U2000, passwords must be complex enough. For
example, a password must contain eight or more characters of two types. The allowed
characters are digits, letters, and special characters. Remember to change passwords
regularly.
NOTE
Any character that you enter using the keyboard will be considered a password component,
including Backspace. For example, if you enter the string cBackspaceChangeme_123, the
password is cBackspaceChangeme_123, but not Changeme_123.
4. Enter the new password again as prompted. Press Enter to make the change take
effect.
NOTICE
After the new password takes effect, do not close the CLI.
Open another CLI and log in using the new password to verify the new password. If
the new password is correct, close all the CLIs. If the new password is incorrect, repeat
the preceding steps to change the password again.
----End
A.6.15 How to Use the FileZilla to Transfer Files by SFTP
Question
How do I use the FileZilla to transfer files by SFTP?
Answer
Step 1 On a PC or laptop, double-click the shortcut icon of FileZilla client to open the FileZilla.

Server) A FAQs
NOTE
You can go to http://filezilla-project.org to download the latest version of FileZilla. For more information
about software operation, see the software Help or go to the official website of the software for technical
support.
Step 2 Create a site.

1. Choose File > Site Manager from the main menu to access the Site Manager window.
2. Click New site.
3. On the General tab page, set the relevant parameters.
l Enter a server IP address in the Host text box.
l Enter 22 in the Port text box.
l Select SFTP from the Server Type drop-down list.
l Select Ask for password from the Logon Type drop-down list.
l Enter a user name of the server OS in the User text box.
Use the root user as an example to establish a site, as shown in Figure A-6.
Figure A-6 Create a site
4. On the Charset tab, set the character string.

The name of a file to be transferred consists of letters, digits, or underscores (_). No
character string needs to be selected, and the default Autodetect is used. For example, a
software installation package or license file.
5. Click Connect. And the Enter password dialog box is displayed, as shown in Figure
A-7.

Server) A FAQs
NOTE
After the site is connected to the server for the first time, the Unknown host key dialog box will be
displayed. Select Always trust this host, add this key to the cache and click OK.
Figure A-7 Enter password
6. Enter a user password in the Password text box, and ensure Remember password for this
session selected. Click OK.
If message Directory listing successful is displayed, as shown in Figure A-8, SFTP

connection is successful.
Figure A-8 Successful SFTP connection
Step 3 Perform the following operations to upload files:

NOTE
Verify that that the name of the directory where the installation packages are stored can contain only letters,
digits, and underscores (_). The directory name cannot contain spaces, brackets, or Chinese characters.
Need to refresh before uploading package under the server is file directory.
1. In the Local site directory tree, locate the folder in which the files to be uploaded reside
and click it. The folder will be displayed in Filename under Local site.
2. In the Remote site directory tree, locate the folder in which the uploaded files are to be
stored and click it. All files in the folder will be displayed in Filename under Remote
site.
3. Click a file to be uploaded and hold down to drag the file to the folder on the Remote
site node.
4. Release the button. File uploading starts.
For example, upload the 1.txt in the /opt directory in the G:\test1 path, as shown in Figure
A-9.

Server) A FAQs
Figure A-9 Uploading files
Step 4 After the file is successfully uploaded, a success message is displayed, as shown in Figure
A-10.
Figure A-10 Successful file uploading
----End
A.6.16 How to Transfer Files by Means of FTP
Question
How do I transfer files by means of FTP?
NOTE
Using SFTP (more secure) to transfer files is recommended.

The available FTP modes are ASCII (default) and binary. To ensure that files are available after transfer,
determine the FTP transfer mode before transferring files.
l Generally, license files are transferred in ASCII mode.
l Before the U2000 is installed, you can upload the U2000 license file as the root user.
l After the U2000 is installed, you must upload the U2000 license file as the ossuser user. Otherwise,
the U2000 license file will be invalid.
l Binary files, such as the U2000 installation program and database interfaces file, are transferred in
binary mode.

Server) A FAQs
Answer
Step 1 Run the following command to connect to the server by means of FTP:
ftp server IP address
Enter the user name and password of the server.
Step 2 Set the FTP transfer mode.
l To use the ASCII mode, run the ascii command.
l To use the binary mode, run the bin command.
Step 3 Go to the path to files to be transferred.
lcd path of files to be transferred
Step 4 Go to the path where the files are to be transferred.
cd path to which the files are to be transferred
Step 5 Optional: Run the hash command to view the file uploading progress.
hash
Step 6 Run the following put command to transfer files:
put names of files to be transferred
Step 7 After the files are transferred, run the quit command to break the FTP connection.
----End
A.6.17 How to Check and Change an OS User ID

Question
Before the U2000 is installed, you must check whether the OS uses a U2000 user ID. How do
I check and change an OS user ID?
Answer
Step 2 Run the following commands to query the database user ID and U2000 user ID in the system:
l Run the following command to check whether a database user ID exists in the system. 800
specifies a database user ID.
# grep x:800: /etc/passwd
l Run the following command to check whether a U2000 user ID exists in the system. 900
specifies a U2000 user ID.
# grep x:900: /etc/passwd
Step 3 If no command output is displayed, the current system does not use any U2000 user ID. If a
command output is displayed, the current system uses a U2000 user ID, and the installation of
the U2000 may fail. Perform the following operations to back up the user ID and then delete it.
The testuser user ID is used as an example.
Run the following command to query the ID of the testuser user:

Server) A FAQs
# id testuser
If information similar to the following is displayed, the modification succeeds.

uid=1000(testuser) gid=900(testgroup) groups=900(testgroup)
Run the following command to delete the ID of the testuser user and back up the user data:
# userdel testuser
NOTICE
If the user is a login user, the execution of the userdel command fails to delete the user. A
message will be displayed indicating that the user is being used.
Step 4 After the U2000 is installed, create the user and restore the backup user data.
In system, create a new user named testuser. The testuser user belongs to the testgroup user
group.
# useradd -g testgroup testuser
----End
A.6.18 How to Burn the ISO File to DVD
Question
How do I burn the ISO file to DVD?
Prerequisites
l The desired ISO file is obtained.
l The DVD recorder has been installed on a Windows PC.
l The burning software has been obtained and installed.
NOTE
The commonly used burning software is Nero, which is a paid software. Purchase Nero from its
official website and then use it. Nero 8 is used as an example in this topic.
l An empty DVD is available.
Answer
Step 1 Check whether the contents of the obtained ISO file are the same as those of the source ISO file.
1. Download the iManager U2000 version MD5 CODE(English) file from the Support
website. The downloaded file contains the MD5 code information about all software
compression packages.

Server) A FAQs
NOTE
Take the following method to obtain the iManager U2000 version MD5 CODE(English) file. Only
Huawei engineers can download the file. If the customer requires using the file, please contact Huawei
engineers for help.
2. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 >
iManager U2000 > iManager U2000 > desired U2000 version.
2. Log in to http://www.nirsoft.net to download the HashMyFiles software.
NOTE
For more information about the software, see the software Help or log in to the official website of
the software for technical support.
3. After the HashMyFiles software is downloaded, run the software.
4. Drag the ISO file to be burnt to DVD to the HashMyFiles tool window. The HashMyFiles
tool automatically generates the MD5 code for the ISO file and compares the generated
MD5 code with that of the ISO file in the iManager U2000 version MD5 CODE
(English) file.
NOTE
Perform the following operations to obtain the MD5 code of the ISO file:
1. Choose File > Add Files from the main menu to access the Select one or more filenames to
add dialog box.
2. Select the ISO file to be burnt to DVD and click Open.
3. After the ISO file is loaded, the HashMyFiles tool automatically generates the MD5 code of the
ISO file. Chooses View > HTML Report All Items to export the MD5 code and compare it with
that of the ISO file in the iManager U2000 version MD5 CODE(English) file.
l If the two MD5 codes are the same, the contents of the obtained ISO file are the same
as those in the source ISO.
l If the two MD5 codes are different, the obtained ISO file is damaged and you must re-
download the ISO file.
Step 2 Execute the Nero software.
Step 3 Click the Image, Project, Copy button.
The Copy Entire CD, Copy Entire DVD, and Disc Image or Saved Project dialog box is
displayed.
Step 4 Click Disc Image or Saved Project.
The Open dialog box is displayed.
Step 5 Select the ISO file to be burnt to DVD and click Open.
The Final Burn Settings dialog box is displayed.
Step 6 Insert the empty DVD to the DVD-ROM.
Step 7 Choose the desired recorder from the Current Recorder drop-down list and select the Verify
data on disc after burning check box.

Server) A FAQs
NOTICE
This step aims at ensuring that the contents burnt to DVD are the same as those in the ISO file.
Step 8 Click Burn to start burning the ISO file to DVD.

The Burning Process dialog box is displayed, showing the burning progress. After the ISO file
is burnt to DVD, the Nero Express dialog box is displayed, and a message about the printing
result is displayed.
Step 9 Click OK.
Step 10 Click Next.
Step 11 Click to close the program.
----End
A.7 Install the U2000 Software Exception Processing

A.7.1 How to Solve the Problem Where the Amount of Remaining

Data Keeps 99% During Data Synchronization in a High
Availability System
Question
During data synchronization in a high availability system, the amount of data to be synchronized
keeps high for several hours. The use of the MSuite shows that the amount of remaining data
keeps 99%. How do I solve this problem?
Answer
Step 1 Log in to the secondary site as the root user.
Step 2 Run the following command to query the transmission protocol for the secondary site:
# vxprint -VPl |grep protocol

protocol: UDP/IP
Step 3 Log in to the primary site as the root user.

Step 4 Run the following command to query the transmission protocol for the primary site:
# vxprint -VPl |grep protocol
Information similar to the following is displayed

Server) A FAQs
protocol: UDP/IP
Step 5 On the primary site, change the transmission protocol and ensure that the primary and secondary
sites use the same transmission protocol.
l If the transmission protocol of the primary site is UDP/IP but the transmission protocol of
the secondary site is TCP/IP, run the following command to change the transmission
protocol of the primary site to TCP/IP:
# vradmin -g datadg set datarvg protocol=TCP
l If the transmission protocol of the primary site is TCP/IP but the transmission protocol of
the secondary site is UDP/IP, run the following command to change the transmission
protocol of the primary site to UDP/IP:
# vradmin -g datadg set datarvg protocol=UDP
----End
A.7.2 How do I solve the problem where a failure message is

displayed during the installation or the installation is abnormally
interrupted
Symptom
installation is abnormally interrupted?
Procedure
Step 1 Log in to the OS of the server as user root.
Step 2 Run the following commands to use the environment clean-up tool to clear the installation
environment:
# cd /opt/oss/engr/engineering/tool/OSSEnvCleaner
# ./OSSEnvCleaner.sh

......
Clean OSS directory:
1.The directory has been deleted,skip this step
2.The directory has never been deleted,execute cleaning directory
Please selected:
Step 3 Enter a value based on whether the U2000 directory /opt/oss is deleted. For example, enter 2.
Step 4 Enter the U2000 directory /opt/oss as prompted.
Step 5 Enter yes to confirm the database deletion operation.
Step 6 Enter the Sybase database path as prompted, or press Enter to automatically enter /opt/
sybase.

Input administrator user name: sa
Input administrator user password: The default password for the database
administrator sa is Changeme_123. To ensure system security, change the default

Server) A FAQs
password timely after the U2000 is installed.

Input database server name: DBSVR
Step 7 Enter the user name and password of the database administrator and the server name. Then press
Enter.
Step 8 After the cleanup operation is performed as prompted, run the following commands to reinstall
the U2000, see 3.6.3 Starting the U2000 Installation Program.
NOTE
If Installation Process has been started. is displayed when installing the U2000, run the following
commands to stop the MSuite server process and then reinstall the U2000:
# ./stopserver.sh
----End
A.7.3 How to Handle Messages Indicating That the Port Is Occupied

During Installation or Uninstall
Question
How do I handle messages indicating that the port is occupied during use of the NMS
Maintenance Suite, installation, or uninstall?
NOTE
In the SUSE Linux OS, the message is as follows:

The communication port (12212,12213,12214,12215) of the installation framework
is used.
Run the "/bin/netstat -ant" command to query the usage status of the port, or
try later.
Answer
l Wait about one minute and try again after the port is released automatically.
l Run the following command to view process IDs:
# cd /opt/oss/engr/engineering/tool/
# ./FindProcessOnPort.sh
Searching for process running on port 12212 ......
-------------------------------------------------------------------------
Port: 12212 is being used by PID: 25542 /opt/oss/OSSJRE/jre_linux/bin/java -
server -Dequinox.conf=engineering/conf/installE
...
Locate all processes that contain port (12212,12213,12214,12215) and end these processes
by running the kill command. The following is a sample kill command:
# kill -9 25542
----End
A.7.4 How to Rectify the Failure to Connect to the Sybase Database

During U2000 Installation
Question
How to rectify the failure to connect to the Sybase database during U2000 installation?

Server) A FAQs
Answer
Step 1 This fault occurs if the IP address recorded in the interfaces file in the Sybase database is
different from the IP address of the U2000 server. To rectify this fault, modify the IP address
recorded in the interfaces file.
Step 2 To modify the interfaces file, run the following command:
# vi /opt/sybase/interfaces

DBSVR
DBSVR_back
Change the IP address (for example, 129.9.1.20) recorded in the interfaces file to the IP address
of the U2000 server.
----End
A.7.5 Failure to Log In to the U2000 Server from a U2000 Client
Symptom
A user fails to log in to a U2000 client after a user name and a password have been entered in
the login window.
Possible Causes
The possible causes are as follows:
l The U2000 server does not work properly, the U2000 server fails to start properly, the disk
on the U2000 server is full, or the memory usage of the U2000 server is high because many
processes are started.
l The network between the client and server does not function properly.
l The license file is a temporary one or is damaged.
l The number of clients allowed in the license is restricted.
l The port between the client and server is shielded by firewall or viruses. In common mode,
port 31037 is used by default. In SSL mode, port 31039 is used by default.
l The version of the client is inconsistent with that of the server.
l The communication protocol used by the client is inconsistent with that used by the server.

Server) A FAQs
l The user that logs in to the client is locked. This may be caused by too many times of login
failures.
l The IP address of the computer where the client is installed is not listed in the ACL.
l The OS time on the client is set incorrectly and the ILOG JTGO license is expired.
l The DCN is faulty.
Procedure
Step 1 If an error message is displayed, locate and rectify the fault as prompted.
Step 2 Check whether the server has been started properly. Ensure that the server runs properly, the
disk space of the server is not used up, and not many processes are started on the server. If many
processes are started on the server, the memory usage is high.
1. Ensure that the server has been started properly.
You can log in to the U2000 System Monitor to view server information. If the server
startup fails, see A.6.1 Failure to Start Certain Processes of the U2000 Server to address
the issue.
2. Ensure that the disk space of the server is not used up.
l To troubleshoot the full disk space on the server on Windows, perform the following
operations:
Check that disk C is fully used, delete log files, and restart the U2000.
l To troubleshoot the full disk space on the server on Solaris or SUSE Linux, perform
the following operations:
a. Check that the space usage of the /opt directory reaches 100%.
b. Run the following command to check the distribution of files larger than 100 MB.
# find /opt -size +200000 -print
Software runs abnormally because temporary files on the server are improperly
large. Delete temporary files from the /opt directory if they occupy large space.
3. Ensure that not many processes are started on the server.
After the U2000 server is started, do not access the JDE desktop (switch to the CED
environment for the U2000 on the live network). Start the U2000 in CLI mode.
Step 3 If a message indicating that the license file is invalid when you log in to the U2000 client, rectify
the license fault according to A.7.6 How to Resolve the Problem that the License Does Not
Take Effect and log in to the U2000 client.
Step 4 Choose Help > License Management > License Information from the main menu (traditional
style); alternatively, double-click System Management in Application Center and choose
License Management > Licenes Information from the main menu (application style).
If the number of clients to log in exceeds the maximum number of clients allowed in the license,
apply for a new license and update the U2000 license file.
Step 5 Check whether the versions of the client and server are consistent. If the versions are inconsistent,
a message will be displayed asking you to upgrade the client. In this case, try to upgrade or
reinstall the client.
Step 6 Check whether the communication protocols used by the client and the server are consistent. If
the protocols are inconsistent, modify the protocols so that the protocols are consistent.

Server) A FAQs
NOTE
Run the ssl_adm -cmd query command on the U2000 server to view the communication mode of the
U2000 server. For details, see A.6.12 How to Set the Communication Mode of the Server in a High
Availability System (Solaris, SUSE Linux).
Step 7 Check the network between the client and server.

Generally, the communication bandwidth between the client and server is at least 2 Mbit/s and
the packet loss ratio is smaller than 0.1%.
l To check the network between the client and server, run the following command on
Windows:
> ping -t IP_address_of_the_NMS
l To check the network between the client and server, run the following command on Solaris:
# ping -s IP_address_of_the_NMS
Step 8 Check whether the port between the client and server is shielded by firewall or viruses. Install
a virus scanner, scan the entire disk, and remove viruses. If the client installed on the computer
where the server belongs can log in to the server, but other clients cannot log in, check whether
the port has been added to the Windows firewall. If not, perform the following operations to add
the port to the Windows firewall:
NOTE
Windows 2008 is used as an example to describe the procedures for adding a port to a firewall. The
procedures vary according to OSs. For specific procedures, see the Windows help.
1. Choose Start > Control Panel.
2. In the Control Panel window, click windows Firewall.
3. In the windows Firewall window, click Advanced Setting.
4. In the Windows Firewall with Advanced Security dialog box, choose Inbound Rules
from the left navigation tree and from New Rule the right navigation tree.
5. In the New Inbound Pule Wizard dialog box, select Port and click Next.
6. In Specific local ports, set Ports and click Next.
7. Select Allow the connection and click Next.
8. Click Next, set Name, and click Finish.
Step 9 Log in to the U2000 client as the admin user and choose Administration > NMS Security >
ACL.
On the U2000, you can set the client IP addresses that can be accessed. If the IP address of a
client is not in the permitted range, the client cannot access the server. For details, see "Setting
the Access Control List" in Chapter "Security Management" in the U2000 Administrator
Guide. If NAT is used for IP address translation for communication between the client and server,
ensure that the translated IP address is permitted in the ACL.
Step 10 If the number of failed login attempts by using the same user exceeds 3, the login authority of
the user is locked.
You can log in to the client again in 30 minutes (default) or unlock the user as another user that
has the authority, such as user admin.
Step 11 Check whether the system time is the current time. If not, modify the system time.
----End

Server) A FAQs
A.7.6 How to Resolve the Problem that the License Does Not Take
Effect
Question
A message is displayed indicating that the license of the U2000 is invalid. As a result, the
U2000 cannot be started or certain functions cannot be used.
How do I resolve this problem?
Answer
The possible causes are as follows:
l The license item is incorrect.
l The time setting of the OS is incorrect.
l Check and rectify the fault on Solaris or SUSE Linux based on the following items:
1. The date of the OS is the current date.
2. Check whether the ESN is correct.
You can obtain the ESN tool according to the U2000 License Usage Guide to check
the ESN.
3. A unique license file exists in the /opt/oss/server/etc/conf/license path.
If more than one license files exist in the path, you must delete redundant license files
manually.
4. The NIC used during license application must be the NIC actually used on the server.
If the NICs are different, you must apply for a new license.
5. The license file must be transferred in the ASCII format.
NOTE
You can check the license file by running the vi command. If each line of the license file ends
with the ^M symbol, the license file is uploaded in binary mode. You must re-upload the license
file.
6. The license file must comply with the U2000 version.
7. Check whether an error has occurred during the license file transfer.
If an error has occurred, transfer the license file again or download the license file to
the /opt/oss/server/etc/conf/license directory. Restart the U2000 and check whether
the license takes effect.
----End
A.7.7 How to Solve Common Problems About Using the Network

Mode to Installing a U2000 Client
Question
How to solve common problems about using the network mode to install a U2000 client?

Server) A FAQs
Answer
The following table shows the problems that may occur while using the network mode to install
a U2000 client and the associated solutions.
Serial Problem Solution

Number
1 After the U2000 patch is installed Delete the %OSS_ROOT%/cau/

and a U2000 client is installed using history directory on the server. Execute
the network mode, the U2000 client the %OSS_ROOT%/cau/bin/cau.bat
version is different from the server file. Use the CAU mode to install a
version. U2000 client.
2 During installation of a U2000 client Choose Start > Run. In the dialog box
in CAU mode, a message is that is displayed, enter cd %
displayed indicating a failure to start USERPROFILE%\Application Data
the CAU. \Sun\Java\Deployment\. In the CLI, run
the del deployment.properties and
delete the deployment.properties.
3 During installation of a U2000 client Choose Tools > Internet Options >
in CAU mode, a message is Connections > LAN Settings from the
displayed indicating that the JRE Internet Explorer. Clear the Proxy
server settings are incorrect and the server check box. Select the
installation fails. Automatically detect settings check
box. Use the CAU mode to install the
U2000 client again.
4 After Install is clicked, a message is Perform the following operations to

displayed indicating a failure to start delete the following directory:
the application. The failure l Choose Start > Run. In the CLI, enter
information shows that the JAR rd %userprofile%/Application
signature certificate in the JNLP file Data\Sun\Java\Deployment\cache
is different from the actual signature and delete the %userprofile%/
certificate. Application Data\Sun\Java
\Deployment\cache directory.
l Enter rd %allusersprofile%/cache
and delete the %allusersprofile%/
cache directory. If the directory does
not exist, no action is required.
A.7.8 How to Rectify the Failure to Open the CAU Download Web
Page Because the Port Is Used
Question
How do I rectify the failure to open the CAU download web page because the port is used?

Server) A FAQs
Answer
Step 2 Run the following commands to view the PID of the process that uses the port:
# netstat -ntlp | grep -w 80

tcp 0 0 :::80 :::* LISTEN 979/
Port 80 is used by the process with the PI of 979.
Step 3 View the process.

# ps -ef |grep 979

root 20161 2440 0 14:56:37 pts/1 0:00 grep 979
root 979 25685 0 February 20 ? 8:17 /opt/oss/server/conf/../bin/
DmsSyslogCollector
The process with the PID of 979 is DmsSyslogCollector.
Step 4 Run the kill process PID command to stop the process after confirming that it can be stopped.
NOTICE
Stop the process only after you confirm that it can be stopped. Otherwise, the U2000 may fail
to run properly.
Step 6 Run the following commands to restart the tomcat process.

$ /opt/oss/server
$ ./svc_profile.sh
$ apachectl stop
$ apachectl start
----End
A.7.9 How to Resolve the Problem that the Database Installation

File Is Not Found During Installation
Question
During NMS installation, a dialog box for selecting the database path is displayed on the database
service configuration page, indicating that the database installation file is not found. How do I
resolve the problem?
Answer
Step 1 Confirm that this problem occurs because the database installation package is not found.
Step 2 Select the directory where the database installation DVD-ROM is installed or the directory where
the database installation package is decompressed.

Server) A FAQs
Step 3 Check whether the database installation package matches the OS.
----End
A.7.10 How to Address the U2000 Installation or Uninstallation

Failure
This topic describes how to handle the failure to install or uninstall U2000 software. If the
U2000 software fails to be installed or uninstalled, you must handle the failure and then reinstall
the U2000 software.
Context
l During the verification of the U2000 software installation, if a check item does not meet
the requirement, a failure message is displayed.
l During the uninstallation of the U2000 software, if the message indicating a successful
uninstallation is not displayed, the U2000 software fails to be uninstalled.
Procedure
Step 1 Log in to the SUSE Linux OS as the root user.
Step 2 Ensure that the Sybase database is not running.
Run the following command to check whether the Sybase database is running:

dbuser 4989 1 0 Sep20 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/
RUN_DBSVR
dbuser 5003 4989 0 Sep20 ? 00:00:14 /opt/sybase/ASE-15_0/bin/dataserver
-sDBSVR -d/opt/sybase/data/lv_master -e/opt/sybase/ASE-15_0/install/DBSVR.log -c/
opt/sybase/ASE-15_0/DBSVR.cfg -M/opt/sybase/ASE-15_0
RUN_DBSVR_back
dbuser 5016 5012 0 Sep20 ? 00:00:00 /opt/sybase/ASE-15_0/bin/
backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install/DBSVR_back.log -N25 -C20 -
M/opt/sybase/ASE-15_0/bin/sybmultbuf
...
NOTE
The database is running if the displayed information contains /opt/sybase/ASE-15_0/bin/dataserver -

sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back.
Run the following commands to stop the Sybase database if it is running:

Step 3 Ensure that the Network Management System Maintenance Suite is not running.

Server) A FAQs
Run the following command to check whether the network management system maintenance
suite process is started:
root 19913 19907 0 04:04:09 pts/1 0:00 grep java
...
root 18382 18311 0 03:42:33 pts/2 12:20 /opt/oss/OSSJRE/jre_linux/bin/java -
server -Dlanguage=en -Xverify:none -Xmx128m -Xm
NOTE
If the displayed information contains /opt/oss/OSSJRE/jre_linux/bin/java -server, it indicates that the

network management system maintenance suite process is started.
Run the following commands to stop the Network Management System Maintenance Suite if it
is running:
# ./stopserver.sh
Step 4 Run the following commands to delete the installation paths /opt/oss/engr, /opt/install/
OSSICMR, /opt/oss/OSSJRE, /opt/oss and /opt/sybase:
# rm -rf /opt/oss/engr
# rm -rf /opt/install/OSSICMR
# rm -rf /opt/oss/OSSJRE
# rm -rf /opt/oss
# rm -rf /opt/sybase
NOTE
If a message is displayed indicating that the /opt/sybase directory is unable to be removed, /opt/sybase
has been created as a system partition and cannot be deleted.
Run the following command to delete the next-level directories and files in /opt/sybase:
# cd /opt/sybase
# rm -rf *
If a message is displayed indicating that the data directory cannot be deleted, delete all directories except
the data directory in the /opt/sybase path.
Step 5 Run the following commands to delete user ossuser and dbuser:
# userdel ossuser
NOTE
The message no crontab for ossuser is displayed, indicating that the ossuser user is successfully deleted.
# userdel dbuser
Step 6 Run the following command to delete user group dbgroup:

# groupdel dbgroup
Step 7 Run the following command to delete user directory /export/home/ossuser:

# rm -rf /export/home/ossuser
Step 8 Reinstall the U2000 software. For details, see 3.6 Installing the U2000 Software.
During the U2000 reinstallation, a message indicating that a port is being used may be displayed.
If such a message is displayed, wait about 1 minute. After the port is automatically released,
continue the reinstallation. For the detailed solution, see A.7.3 How to Handle Messages
Indicating That the Port Is Occupied During Installation or Uninstall.
----End

Server) A FAQs
A.7.11 How to Troubleshoot the Heartbeat IP Address

Unavailability That Causes the Primary and secondary sites
Synchronization Failure
Symptom
If the Primary and secondary sites synchronization fails, click Details. If a message is displayed
indicating a problem like heartbeat IP address unavailability, check the heartbeat network. How
do I troubleshoot this problem?
Possible Causes
The possible causes for heartbeat IP address unavailability are as follows:
l The heartbeat IP addresses of the Primary Site and Secondary Site are not in the same
network segment, as shown in the preceding figure.
l A network interface to which the heartbeat IP address belongs is faulty on the Primary
Site or Secondary Site.
NOTE
l A bond that works in double-live mode is configured for the heartbeat IP address of the Local
SUSE Linux high availability system (PC server). Primary and secondary sites synchronization
fails if either network interface in a bond is faulty. As shown in the preceding figure, at least one
of network interfaces 1, 2, 3, and 4 is faulty.
l A bond that works in primary/secondary mode is configured for the heartbeat IP address of the
Remote SUSE Linux high availability system (PC server). Primary and secondary sites
synchronization fails only when both network interfaces in a bond are faulty.
Procedure
Step 1 Check whether the Primary and secondary sites' heartbeat IP addresses are in the same network
segment.
1. Log in to the operating systems of the Primary and secondary sites as a root user.
2. Run the following command on the Primary and secondary sites to view the heartbeat IP
addresses:
# ifconfig

bond0 Link encap:Ethernet HWaddr 6C:AE:8B:38:D1:D2
inet addr:10.67.186.228 Bcast:10.67.186.255 Mask:255.255.255.0
inet6 addr: fe80::6eae:8bff:fe38:d1d2/64 Scope:Link

Server) A FAQs
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

RX packets:475571 errors:0 dropped:0 overruns:0 frame:0
TX packets:23010 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38623174 (36.8 Mb) TX bytes:1714514 (1.6 Mb)
bond1 Link encap:Ethernet HWaddr 6C:AE:8B:38:D1:D3

inet addr:192.168.10.255 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::6eae:8bff:fe38:d1d3/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2192705 errors:0 dropped:0 overruns:0 frame:0
TX packets:2115143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2661111799 (2537.8 Mb) TX bytes:267667598 (255.2 Mb)
In the preceding command output, the IP address 192.168.10.255 for bond1 is the heartbeat
IP address.
l If the Primary and secondary sites' heartbeat IP addresses are in different network
segments, use the commissioning tool on the Secondary Site to change the Secondary
Site' heartbeat IP address and Primary Site' heartbeat IP address to the same network
segment. You can refer to Configuring System Commissioning Parameters about
how to access the commissioning tool. In the Set Network window of the
commissioning tool, change the Secondary Site' heartbeat IP address and Primary
Site' heartbeat IP address to the same network segment.
l If the Primary and secondary sites' heartbeat IP addresses are in the same network
segment, go to Step 2.
Step 2 Log in to the operating system of the Secondary Site as a root user. Run the following command
to check whether heartbeat lines are connected between the Primary and secondary sites:
# ping Heartbeat IP address of the primary site
l If no command output is displayed, lines 1 and 2 in the preceding figure are disconnected.
Go to Step 3.
l If a command output is displayed and the icmp_seq values are inconsecutive (as follows),
lines 1 and 2 in the preceding figure are disconnected. Go to Step 3.
PING
192.168.10.86 (192.168.10.86) 56(84) bytes of data. 64 bytes from
192.168.10.86: icmp_seq=2 ttl=64 time=0.173 ms 64 bytes from
192.168.10.86: icmp_seq=12 ttl=64 time=0.140 ms
l If a command output is displayed and the icmp_seq values are consecutive (as follows),
heartbeat lines are connected between the Primary and secondary sites. Go to Step 5.
PING 10.67.165.156 (10.67.165.156) 56(84) bytes of data.
64 bytes from 10.67.165.156: icmp_seq=1icmp_seq=1 ttl=63 time=0.763 ms
64 bytes from 10.67.165.156: icmp_seq=2 ttl=63 time=0.577 ms

Server) A FAQs

Step 3 On the Primary and secondary sites, perform the following steps to locate the faulty network
interface to which the heartbeat IP address belongs:
1. Run the following command to view the logical network interfaces in the bond that is
configured for the heartbeat IP address:
# cat /etc/sysconfig/network/ifcfg-bond1

BOOTPROTO='static'
BROADCAST='192.168.10.255'
IPADDR='192.168.10.228'
NETMASK='255.255.255.0'
NETWORK='192.168.10.0'
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=0 miimon=100 use_carrier=1'
In the preceding command output, eth1 and eth5 are the logical network interfaces bound
to the heartbeat IP address.
2. Run the following command to check whether each logical network interface to which the
heartbeat IP address belongs is functioning properly ( eth1 is used as an example):
# ethtool eth1
The information similar to the following is displayed:

Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
l If the Speed and Duplex values are Unknown, the logical network interface is faulty.
Go to Step 4.
l If the Speed and Duplex values are not Unknown, the logical network interface is
functioning properly. Go to Step 5.
Step 4 Use the commissioning tool to change the faulty network interface to which the heartbeat IP
address belongs to an unused network interface. You can refer to Configuring System
Commissioning Parameters about how to access the commissioning tool. In the Set
Network window of the commissioning too, change the faulty network interface to an unused
normal interface.

Server) A FAQs
Step 5 Resynchronize the Primary and secondary sites.
Step 6 If the problem persists, contact Huawei technical support engineers.
----End

Server) B Uninstalling the U2000 Software
B Uninstalling the U2000 Software
B.1 Uninstall Preparations

This topic describes the preparations for uninstalling the U2000 software.
B.2 Uninstalling U2000 Software

This topic describes how to uninstall U2000 software.
B.3 Verifying the Uninstall Status of the Server Software

This topic describes how to verify that the U2000 server software is uninstalled.

B.1 Uninstall Preparations

This topic describes the preparations for uninstalling the U2000 software.
Procedure
Step 1 Optional: If the SetSuse policy is enabled on the live network, choose whether to disable the
policy according to network conditions.
l If the SetSuse policy cannot be disabled on the live network, skip this step.
NOTE
If the SetSuse policy is disabled on the live network, skip this step.
l If the SetSuse policy can be disabled on the live network, run the following command to
cancel the SetSuse policy.
1. Log in to the OS as the ossuser user.
NOTE
If log in to the server from a remote site, you can perform remote access by means of SSH(putty) as user
ossuser, or by means of VNC as user ossuser.
2. Run the following command to switch to the root user:
$ su - root
3. Enter a login password for the root user.

4. Run the following command to stop the security hardening service:
# sek -b all
5. Run the following commands to restart the OS:

# hastart -onenode
# shutdown -r now
NOTE
If the security hardening service need to be started, see Start the security hardening service.
Step 2 Log out of all running U2000 clients.
Step 3 Log in to the OS of the primary site as the ossuser user by using the remote GUI software. Such
as VNC.
Step 4 Disconnect the primary site from the secondary site.

1. Make sure that all servers on the primary and secondary sites must be started on the
MSuite server side.
started:
NOTE
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root command
and enter the root user password to switch to the root user.

...
root 19985 1 0 Nov23 ? 00:34:37 /opt/oss/OSSJRE/jre_linux/bin/
java -server -Dlanguage=zh -Xverify:none -Xms512m -Xmx1024m -
+UseParNewGC -XX:+UseConcMarkSweepGC -Dengr.launcher.file=engineering/conf/
launch/deploysever_launcher.xml -Dequinox.conf=engineering/conf/equinox.ini -
Drunway=maintenance -DautoLogin=true -DinstallDiskMode=cmd -
DinstallType=server -classpath engineering/lib/Launcher.jar:engineering/lib/
equinox.jar com.oss.core.launcher.Launcher
NOTE
If the displayed information contains /opt/oss/OSSJRE/jre_linux/bin/java -server, the MSuite servers
have been started.
If the MSuite servers have not been started, run the following commands as the root user
to start the MSuite servers:
# ./startserver.sh
2. On the server on the active site, run the following commands to start the MSuite client:
Double-click the shortcut icon of the U2000 NMS Maintenance Suite or run the following
commands:
$ ./startclient.sh
Parameter Settings
IP Address l If the Network Management System Maintenance Suite client

and the Network Management System Maintenance Suite
server are on the same computer, you must enter 127.0.0.1 or
the application IP address on the primary site.
l If the Network Management System Maintenance Suite client
and the Network Management System Maintenance Suite
server are on different computers, enter only the application
IP address on the primary site.

Parameter Settings
Password The initial password of the admin user is Changeme_123 (It is

Admin_123 for a U2000 that comes preinstalled). The password
must be changed during the first login to ensure system security.
Keep the password confidential and change it regularly.
3. Click Login to access the Network Management System Maintenance Suite window.
NOTE
When you log in to the MSuite client, a progress bar showing the progress of querying subsystems is
displayed. Wait until the operation is complete.
4. Choose Deploy > Separate Primary Site from Secondary Site. The Warning dialog box
is displayed.
5. Click Yes. Then click Yes in the Warning dialog boxes displayed. The progress bar is
displayed indicating the status of separating the primary and secondary sites. Wait until the
dialog box is displayed indicating that the separation is complete.
6. Click OK.
7. Choose System > Log Out from the main menu. The Log Out dialog box is displayed.
8. Click OK.
Step 5 Ensure that the U2000 is not running.
To check the running status of U2000 processes, run the following command:
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start. If no
introduction is displayed, the U2000 processes have been stopped.
If the U2000 is still running, see E.1 Stopping the U2000 Server Processes to stop it.
Step 6 Ensure that the Network Management System Maintenance Suite is not running.
Run the following command to verify that the Network Management System Maintenance
Suite is not running:
$ ps -ef | grep java
-server -Dlanguage=zh -Xverify:none -Xms512m ...
ossuser 13005 5087 0 11:37 pts/0 00:00:00 grep java
NOTE
If the displayed information does not contain /opt/oss/OSSJRE/jre_linux/bin/java -server, the Network
Management System Maintenance Suite is stopped.

If the Network Management System Maintenance Suite is still running, run the following
commands to stop it:
$ su - root
password: password_of_root_user
# ./stopserver.sh
# exit
Step 7 Ensure that the database is running.
Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase

RUN_DBSVR
RUN_DBSVR_back
...
NOTE

If the Sybase database is not running, see D.2 Starting the Database to start it.
----End
B.2 Uninstalling U2000 Software

This topic describes how to uninstall U2000 software.
Prerequisites
The ossuser user has logged out.
1. Run the following command to check which processes are being used by the ossuser user:
# ps -ef | grep ossuser

root 17454 17453 0 12:33 ? 00:00:00 login -- ossuser
ossuser 17463 17454 0 12:33 pts/4 00:00:00 -bash
ossuser 17557 17539 0 12:34 ? 00:00:00 /opt/gnome/bin/gnome-session
ossuser 17625 1 0 12:34 ? 00:00:00 /opt/gnome/lib/GConf/2/gconfd-2
10
ossuser 17688 1 0 12:34 ? 00:00:00 gnome-screensaver
root 17810 16473 0 12:35 pts/0 00:00:00 grep ossuser
2. Run the following command to stop all the processes used by the ossuser user:
# kill -9 process ID of the ossuser user

NOTE
l In the preceding command, process ID of the ossuser user maps the second column in the
displayed information. For example, kill -9 17463.
l If there are multiple ossuser users, each process ID of the ossuser user separated by a space. For
example, kill -9 17463 17557 17625 17688.
l Information similar to the following is displayed, no process is being used by the ossuser user,
all the processes used by the ossuser are stopped:
root 18527 16473 0 12:46 pts/0 00:00:00 grep ossuser
Context
In this topic, only the U2000 software is uninstalled. The Veritas and database software is not
installed.
l If the Veritas and database software is not damaged, uninstall the U2000 and execute the
3.6.3 Starting the U2000 Installation Program again to reinstall the U2000.
l If the Veritas and database software is damaged, reinstall the OS of the high availability
system and then execute the 3.6 Installing the U2000 Software to reinstall the high
NOTE
If the SetSuse policy is enabled, log in to the OS as the ossuser user. If the root user must be the login user, run
the su root command to switch the current user to the root user, enter the password according to prompts.
Procedure
Step 1 Log in to the GUI of the OS as the root user on the primary and secondary sites.
Step 2 Run the following command on the servers at the primary and secondary sites to go to the path
where the uninstall.sh script is stored and run the script:
NOTE
Two modes are available to uninstall the U2000. One is the GUI mode and the other is the CLI mode. The
procedure for uninstalling the U2000 in GUI mode is described in the following sections. Installation engineers
are recommended to uninstall the U2000 through the CLI if they cannot log in to the GUI of the OS.
Run the ./uninstall.sh -cmd command to uninstall the U2000 in the /opt/oss/engr path through the CLI.
# cd /opt/oss/engr
# ./uninstall.sh
The Confirm Uninstallation dialog box will be displayed.

Step 3 Click Next. The Warning dialog box is displayed.
Step 4 Click OK. A dialog box showing the progress of the uninstall will be displayed.
NOTE
The duration of the uninstall depends on the quantity of installed components. Wait patiently.
Step 5 After the uninstall is complete, the Uninstallation Complete dialog box is displayed.
Step 6 Click Finish.
Step 7 Wait 1 minute. Run the following commands to ensure that engr, OSSICMR, and OSSJRE
directories do not exist and complete uninstallation.
# rm -rf /opt/oss/engr
# rm -rf /opt/install/OSSICMR
# rm -rf /opt/oss/OSSJRE

If these directories are already unavailable, an error message is displayed. Ignore the error
message.
----End
Follow-up Procedure
If the SetSuse policy is enabled during uninstallation or the ossuser user is being used, log in to
the OS as the dbuser user. Run the following command to switch to the root user and then delete
the ossuser user and the ossuser directory.
Run the following command on the primary and secondary sites:

$ su - root
# userdel ossuser
# rm -rf /export/home/ossuser
B.3 Verifying the Uninstall Status of the Server Software

This topic describes how to verify that the U2000 server software is uninstalled.
Procedure
Step 1 Log in to the OS of the server as user root.
Step 2 Confirm that the installation path is correct during the uninstall.
The installation path /opt/oss is deleted.
Step 3 Confirm the ossuser user that must be deleted during the uninstall.
Run the following command to switch to user ossuser:
# su - ossuser

su: user ossuser does not exist
----End

Server) C Manual Commissioning Task
C Manual Commissioning Task
Some commissioning tasks need to be manually executed during U2000 system parameter
commissioning. This topic describes how to execute a manual commissioning task.
C.1 Configuring a Digital Certificate

The U2000 supports security encryption to ensure the communication security for the DCN and
the confidentiality and integrity for the transmitted data. A digital certificate is also used to
distribute public keys.

C.1 Configuring a Digital Certificate

The U2000 supports security encryption to ensure the communication security for the DCN and
the confidentiality and integrity for the transmitted data. A digital certificate is also used to
distribute public keys.
C.1.1 Replacing SSL Certificates Used for the Communication

Between the U2000 Server and Client
When the U2000 is installed, the SSL certificate developed by Huawei is loaded for temporary
communication. Do not use this certificate commercially. The U2000 supports certificate
replacement. Before enabling SSL communication, apply for a certificate from a CA and use it
to replace the temporary certificate in the commissioning phase. Perform the following
operations to replace Security Socket Layer (SSL) certificates used for the communication
between the server and client.
Prerequisites
l You have obtained the SSL certificates and encryption passwords from a trusted institute.
– The client.p12 contains the client certificate file and key file. The password for
encrypting the file needs to be obtained.
– The server.p12 contains the server certificate file and key file. The password for
– The trust.cer contains the files issued by the client, server, and upper-layer system.
l Save the new SSL certificate to the following directory on the U2000 server before you
replace the SSL certificate.
– Solaris/SUSE Linux: /opt/oss/server/certs
– Windows: D:\oss\server\certs
l Before the replacement operation, ensure the original SSL digital certificates are backed
up.
l The U2000 service of the MSuite and the client use the same SSL certificate.
Context
l The SSL certificates predeployed by Huawei for the communication between the U2000
server and client are stored in the following paths:
– In Solaris or SUSE Linux OS: /opt/oss/server/etc/ssl
– In Windows OS: D:\oss\server\etc\ssl
l Currently, the ssl_adm -cmd replace_certs command can be used in Solaris, SUSE Linux,
and Windows.
l In a high availability system (Veritas hot standby) scheme, perform the following
operations on the servers of the primary and secondary sites.

Procedure
l Replace an SSL certificate for the U2000 server and client through the GUI.
started:
NOTE
...
NOTE
# ./startserver.sh
2. Log in to the MSuite client from the U2000 server.

3. Choose Certificate File Management > Internal NMS Certificate.
4. In the Certificate Configuration dialog box, select the SSL certificate to be replaced
and click ReplaceAll.
5. In the Information Confirmation dialog box, enter the PFX password.
6. Click OK.
l Replace an SSL certificate for the U2000 server and client using a script.
1. Copy the SSL certificate to any path on the server (for example, /opt/oss/server/
certs) and check that the ossuser user has read/write permission on this path.
Perform the following operations to assign read/write permission on /opt/oss/server/

certs to the ossuser user:
a. Log in to the server as the root user.

b. Run the following command to assign read/write permission on /opt/oss/server/
certs:
# chown -R ossuser:ossgroup /opt/oss/server/certs
# chmod -R 750 /opt/oss/server/certs
2. Log in to the U2000 server as the ossuser user.

3. Stop the U2000 process:
NOTICE
In a high availability system (Veritas hot standby) scheme, stop the U2000 process
on the primary site. You do not need to modify the enabling or disabling status of the
database on the primary or secondary site.
For details about how to stop the U2000 server processes, see E.1 Stopping the U2000
Server Processes.
4. Run the following command to deploy SSL certificates:
$ ssl_adm -cmd replace_certs -dir /opt/oss/server/certs -pfxpwd password
NOTE
l /opt/oss/server/certs is the path where the certificates are stored.

l Enter password next to -pfxpwd. password is the password for the identity certificate on
the server.
l If the identity certificate is server.p12 of the PKCS12 type, the certificate password
obtained along with the certificate must be correctly entered. This password will be
verified when the preceding command is run.
l If the identity certificate is server.cer, which has a matched private key file named
server_key.pem, the certificate password must be specified by users. This password
will be used to encrypt the certificate and convert the certificate into a certificate of the
PKCS12 type when the preceding command is run.
l After the command is run, the existing certificates and configurations are automatically
backed up. The files in $IMAP_ROOT/etc/ssl will be backed up to $IMAP_ROOT/var/
backup/deployssl/ssl; all the certificates in the specified path will be converted and
deployed to $IMAP_ROOT/etc/ssl.
l If the command is successfully executed, a message similar to the following will be
displayed:
SSL certificates are deployed successfully
Otherwise, an error message is displayed and rollback operations are automatically
performed without affecting the original SSL certificates and configurations. Deploying
the certificates may fail if the folder specified meets the one of the following conditions:
l The folder has no trust certificate.
l The folder has no identification certificate.
l The certificates have expired.
l The effective time of the certificates is later than the current system time.
l Certificate password is incorrect if the identity certificate is a server.p12 file of the
PKCS12 type.
l The server_key.pem key file does not match the identity certificate if the identity
certificate is a server.cer file.
l In a high availability system (Veritas hot standby) scheme, the following error information
may be displayed if the database on the secondary site is not started. If it is displayed, ignore
it. SSL certificate deployment is not affected.
svc_adm : error : Failed to get sys agent para, please check if
database is correct.
5. Optional: For a server.cer identity certificate, replace the service_key.pem file in the
$IMAP_ROOT/etc/ssl/privatekey/PEM path.

6. Run the following command to set the communication mode of the U2000 server to
SSL:
$ ssl_adm -cmd setmode ssl
NOTE
The available options for mode parameter are common, ssl, and both.
l common: common mode. If mode parameter is set to common, the U2000 server and client
can communicate only in common mode, and http protocol must be used to download the
U2000 client in CAU mode.
l ssl: security mode. If mode parameter is set to ssl, the U2000 server and client can
communicate only in security mode, and https protocol must be used to download the
U2000 client in CAU mode. The security mode is recommended to ensure security for
communication between the U2000 server and client.
l both: indicates that the U2000 server and client can communicate with each other in either
common or SSL mode.
If the following message is displayed, the operation has been successfully performed:
Operation succeeded. Please restart all services for the settings to take
effect.
NOTE
Any error messages displayed before this message can be ignored because these messages do not
affect the operation result.
7. Start the U2000 processes:
For details about how to start the U2000 server processes, see D.3 Starting the U2000
Server Processes.
8. Configure the digital certificate for the U2000 client.
a. Prepare the identification certificate and trust certificate for the U2000 client.
b. Starting the certificate configuration tool.
Double-click client\client\bin\CertConfigurator.bat of the U2000 client to
start the certificate configuration tool.
c. Configuring an identity certificate of U2000 client.
a. On the ID Certificate tab page, click next to File Name, and then select
a .p12 file. The path of this file is displayed in File Name.
b. Enter the password of the certificate in PFX password.
c. Click OK.
– If the certificate configuration tool automatically quits, and the identity
certificate is configured successfully, the certificate is a .p12 file and the
password is correct.
– If "The PFX password is invalid, or the selected file is damaged." is
displayed, the certificate is not a .p12 file or the password is incorrect.
d. Configuring a trust certificate of U2000 client.
a. Click the Trust Certificate tab.
b. On the Trust Certificate tab page, click Add, and then select a .cer file.
– If certificates are displayed, the added certificate is a .cer file.

– If "The selected file is not a certificate of the X509 type." is displayed,

the certificate is not a .cer file.
----End
Result
l If U2000 processes are properly started, SSL certificates have been successfully loaded.
l If some of the U2000 processes fail to be started, SSL certificates have not been successfully
loaded. You must restore the configurations on the U2000 server.
If loading SSL certificates fails on the U2000 server, perform the following operations:
1. Log in to the U2000 server as the ossuser user.
2. Stop the U2000 process:
3. Use the certificates and configuration files in the backup path $IMAP_ROOT/var/
backup/deployssl/ssl to restore the files in $IMAP_ROOT/etc/ssl.
a. Run the following command to delete $IMAP_ROOT/etc/ssl:
$ rm -r $IMAP_ROOT/etc/ssl
b. Use the files in the backup path to restore the files in $IMAP_ROOT/etc/ssl.
$ cp -R $IMAP_ROOT/var/backup/deployssl/ssl $IMAP_ROOT/etc/ssl
4. Start the U2000 processes:

For details about how to start the U2000 server processes, see D.3 Starting the U2000
Server Processes.
Follow-up Procedure
After SSL certificates used for the communication between the U2000 server and client are
successfully replaced, delete certificate files from the following directory on the U2000 server:
l Solaris/SUSE Linux: /opt/oss/server/certs
l Windows: D:\oss\server\certs
C.1.2 Replacing SSL Certificates Used for the Communication

Between the U2000 and uTraffic
When the U2000 is installed, the SSL certificate developed by Huawei is loaded for temporary
communication. Do not use this certificate commercially. The U2000 supports certificate
replacement. Before enabling SSL communication, apply for a certificate from a CA and use it
to replace the temporary certificate in the commissioning phase. Perform the following
operations to replace Security Socket Layer (SSL) certificates used for the communication
between the U2000 and uTraffic.
Prerequisites
l You have obtained the SSL certificates and encryption passwords from a trusted institute.
– The client.p12 contains the client certificate file and key file. The password for
– The server.p12 contains the server certificate file and key file. The password for

– The trust.cer contains the files issued by the client, server, and upper-layer system.
l Save the new SSL certificate to the following directory on the U2000 server before you
replace the SSL certificate.
– Solaris/SUSE Linux: /opt/oss/server/certs
– Windows: D:\oss\server\certs
l Before the replacement operation, ensure the original SSL digital certificates are backed
up.
Context
l The predeployed SSL certificates for the communication between the U2000 and uTraffic
are stored in the following paths:
– Solaris or SUSE Linux: /opt/oss/server/etc/ssl/solution
– Windows: D:\oss\server\etc\ssl\solution
l The certificate replacement script is stored in the /opt/oss/server/tools/ssl path (Use
Solaris/SUSE Linux as an example. The path on Windows is similar.). Run the ./
replace_certs.sh command as the ossuser user in this path. Information similar to the
following is displayed:
NOTE
l -type indicates the certificate type, -file indicates the certificate path, and -pfxpass indicates the
encrypted password for the identity certificate.
l certificate type:
l 1: client identity certificate
l 2: server identity certificate
l 3: trust certificate
l 4: revocation certificate list
l certificate file: path in which the certificate is stored.
l PFX password: encrypted password for the certificate.
l Example:
l replace_certs -type 1 -file client.p12 -pfxpass testpass
l replace_certs -type 2 -file server.p12 -pfxpass testpass
l replace_certs -type 3 -file trust.cer
l replace_certs -type 4 -file revoke.crl

Procedure
l Replace an SSL certificate for the U2000 and uTraffic through the GUI.
started:
NOTE
...
NOTE
# ./startserver.sh
2. Log in to the MSuite client from the U2000 server.

3. Choose Certificate File Management > Other Certificate.
4. Click the Identity Certificate tab and configure the SSL Client and SSL Server
identity certificates.
5. Click the Trust Certificate tab and configure the trust certificate.
NOTE
After adding the new trust certificate, delete the old trust certificate that won't be used.
6. Optional: Click the Certificate Revocation List tab and configure the revocation
certificate.
7. Restart the PMSDm process.
l Replace an SSL certificate for the U2000 and uTraffic using a script.
1. Start the identity certificate replacement script.
– Solaris or SUSE Linux (as the ossuser user):
# cd /opt/oss/server/tools/ssl
# replace_certs -type certificate type -file certificate file -pfxpass PFX password

NOTE
The identify certificates on the server and client must be replaced separately. For example:
– Windows:
>cd /d d:
>cd \oss\server\tools\ssl
>replace_certs -type certificate type -file certificate file -pfxpass PFX password
NOTE
The identify certificates on the server and client must be replaced separately. For example:
2. Start the trust certificate replacement script.
# replace_certs -type certificate type -file certificate file
NOTE
For information about variables, see the background information. For example,
replace_certs -type 3 -file trust.cer.
– Windows:
>cd /d d:
>replace_certs -type certificate type -file certificate file
NOTE
replace_certs -type 3 -file trust.cer.
3. Optional: Start the CRL configuration script.
# replace_certs -type certificate type -file certificate file
NOTE
replace_certs -type 4 -file revoke.crl.
– Windows:
>cd /d d:
>replace_certs -type certificate type -file certificate file
NOTE
replace_certs -type 4 -file revoke.crl.
4. Restart the PMSDm process.
----End

Result
l If U2000 processes are properly started, the U2000 can be connected to uTraffic by means
of Security SSL and SSL certificates have been successfully loaded. You can manually
delete the backup SSL digital certificates for U2000 and uTraffic.
l If the U2000 process fails to start, you must replace backup certificates and save the target
certificates to the default certificates path.
Follow-up Procedure
After SSL certificates used for the communication between the U2000 and uTraffic are
successfully replaced, delete certificate files from the following directory on the U2000 server:
l Solaris/SUSE Linux: /opt/oss/server/certs
l Windows: D:\oss\server\certs
C.1.3 Replacing SSL Certificates Used for the Communication of

the Internet Explorer browser
When the U2000 uses the Web LCT to manage NE series, such as the NG WDM, NG WDM
(NA), RTN, and Marine, some functions of the NE Explorer must be opened through an Internet
Explorer. In this case, the SSL certificate of the Internet Explorer must be deployed.
Context
The procedure for deploying an SSL certificate preconfigured by Huawei is used as an example.
The procedures for deploying other SSL certificates are similar.
Procedure
Step 1 Load the digital certificate HuaWeiCA.crt to the Internet Explorer browser.
1. Open the Internet Explorer of the U2000 client and choose Tool > Internet Options from
the main menu.
2. Click the Content tab and select Certificates.... The Certificates dialog box is displayed.
3. Select Import. In the Certificate Import Wizard dialog box, click Next.
4. Click Browse to select the path in which the digital certificate HuaWeiCA.crt is stored
and click Next.
NOTE
The digital certificate HuaWeiCA.crt is stored in the oss\client\client\plugins\trans_common

\style\conf\ssl\trust\PEM path.
5. Select Place all certificates in the following store and click Browse. In the Select
Certificate Store dialog box, select Trusted Root Certification Authorities and click
OK. Click Next.
6. Click Finish. In the Security Warning dialog box, click Yes.
Information similar to the following is displayed in the Certificate Import Wizard dialog
box:
The import was successful.
Click OK.

7. In the Certificates dialog box, click Trusted Root Certification Authorities. You can
drag the scroll bar to check whether the digital certificate has been successfully loaded.
Then click Close.
Step 2 In the Internet Options dialog box, click the Advanced tab.
Drag the scroll bar to Security and clear the selection of the Warn about invalid site
certificates check box. Then click OK.
Step 3 Optional: If the dialog which prompted you need trusted certification is displayed in the
U2000 NE management, right-click Continue to this website (not recommended). In the dialog
box, click Open in the New Window option.
1. Click OK.
2. If the Security Alert dialog box for the installation certificate is displayed, click OK to
display the current function GUI. After finish the operation, the U2000 GUI will display
normally.
----End
Follow-up Procedure
If the U2000 GUI is displayed abnormally, the SSL certificate fails to be uploaded. Refer to the
preceding operations to redeploy a digital certificate.

Installation and Commissioning Guide (SUSE Linux, PC D Starting the U2000 Server in a SUSE Linux High
Server) Availability System
D Starting the U2000 Server in a SUSE Linux

High Availability System
The U2000 server can be started in three steps: power on the server safely, start the database,
and start the U2000 server processes.
D.1 Powering On the Server Safely
D.2 Starting the Database

This topic describes how to start the database in a PC Linux high availability system. The
U2000 can start properly only after the database is started.
D.3 Starting the U2000 Server Processes

This topic describes how to start the U2000 server processes in a PC Linux high availability
system. You can log in to the U2000 to manage a network only after starting the U2000 server
processes on the computer on which the U2000 is installed.

D.1 Powering On the Server Safely
Server
NOTICE
VAC input voltage.
standby switchover.
NOTE
website.
IBM X3850 X5.
Figure D-1 Position of the power button on Huawei Tecal RH5885H V3 server

Figure D-2 Position of the power button on Huawei Tecal RH2288H V2 server
Figure D-3 Position of the power button on IBM X3650 M4
Figure D-4 Position of the power button on IBM X3650 M3
Figure D-5 Position of the power button on IBM X3850 X5

Disk Array
NOTICE
on.
NOTE
D.2 Starting the Database

This topic describes how to start the database in a PC Linux high availability system. The
U2000 can start properly only after the database is started.
Prerequisites
l The OS has been started.
l The server is properly connected to the network.
l The VCS service must be properly started. The VCS service has started along with the OS
and the disk is functioning properly. For details about how to check the server disk status,
see Checking Server Disks in the U2000 Administrator Guide.
Procedure
Step 1 Perform the following operations to start the Sybase database:
l GUI mode:
# hagui&
3. Choose File > New Cluster from the main menu. In the dialog box that is displayed,
enter the server IP address and click OK.
NOTE

5. Ensure that all Veritas resources are in Enabled state. Use the BackupServer resource
as an example. Perform the following operations:
Expand the AppService node and then the SybaseBk node in the navigation tree, right-
click BackupServer, and check whether Enabled has been selected in the shortcut
menu. If Enabled has not been selected, select it.
6. Right-click BackupServer and choose Online > host name from the shortcut menu.
Wait until the BackupServer and DatabaseServer resource icons on the Resources
tab page are bright, which indicates that the Sybase database service has started.
l CLI mode:
2. Run the following commands to query Veritas resource names:
# haconf -makerw
# hares -list

APPBOND Primaster
BackupServer Primary
DatabaseServer Primary
NMSServer Primary
RVGPrimary Primary
datarvg Primary
mountRes Primary
wac Primary
3. Run the hares -modify resource name Enabled 1 command to change the status of all
Veritas resources to Enabled. Use the resource names displayed in the previous
command output as an example. Run the following commands to change the status of
all the Veritas resources to Enabled:
# hares -modify APPBOND Enabled 1
# hares -modify NMSServer Enabled 1
# hares -modify RVGPrimary Enabled 1
# hares -modify mountRes Enabled 1
# hares -modify wac Enabled 1
4. Run the following command to start the Sybase database service:

# hares -online BackupServer -sys hostname
NOTE
hostname specifies the server name. You can run the hostname command to view the server
name.
----End
Result
Run the following command to check whether the Sybase process is running:
$ ps -ef | grep sybase


RUN_DBSVR
RUN_DBSVR_back
...
NOTE

D.3 Starting the U2000 Server Processes

This topic describes how to start the U2000 server processes in a PC Linux high availability
system. You can log in to the U2000 to manage a network only after starting the U2000 server
processes on the computer on which the U2000 is installed.
Prerequisites
The OS on the computer on which the U2000 server processes are installed is running properly,
and the database has been started.
Procedure
Step 1 Log in to the OS on the active site as the root user.
Step 2 Start the U2000 server processes.

l GUI mode:
1. Open a terminal window and run the following command:
# hagui&
NOTE
2. Click Connect to cluster name.

NOTE
1. Choose File > New Cluster.
2. Enter an application network IP address.
3. Click OK.
3. Set User Name and Password.
NOTE
4. Click OK.
5. In the Cluster Explorer window, select the AppService resource group in the
navigation tree, right-click, and choose Online > host name from the shortcut menu to
start the Sybase process and U2000 server processes.
NOTE
Normally, the value of State for the active site is Online in the Group Status on
Member Systems area on the Status tab page, and the value of Status is Online on
host name in the Resource Status area.
NOTE
l Use the actual host name for real-world configuration.

l If a fault has occurred during the start of the AppService process, right-click AppService and
choose clear fault from the shortcut menu to rectify the fault. Then choose Online > host name
to start the AppService process.
l CLI mode:
NOTE
l hostname specifies the server name. You can run the hostname command to view the server name.
l If a fault has occurred during the start of the AppService process, run the # hagrp -clear AppService
-sys hostname command to rectify the fault. Then run the # hagrp -online AppService -sys hostname
command to start the AppService process.
----End
Result
1. Log in to the OS of the active site as the ossuser user.
2. Run the following command to check whether the U2000 is running:
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
ossuser 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd
start

NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start.

Installation and Commissioning Guide (SUSE Linux, PC E Shutting Down the U2000 Server in a High Availability
Server) System (PC Linux)
E Shutting Down the U2000 Server in a High

Availability System (PC Linux)
Four steps are required to shut down the U2000 server: stop the U2000 server processes, shut
down the database, stop the VCS service, and power off the server safely.
E.1 Stopping the U2000 Server Processes

Do not stop the U2000 server processes when the U2000 server is managing NEs. Stop the
U2000 server processes only for some special purposes, for example, changing the system time
of the computer where the server is installed or upgrading the version. This topic describes how
to stop the U2000 server processes on the SUSE Linux HA system.
E.2 Shutting Down the Database

The U2000 can start properly only after the database is started. Before shutting down the
database, stop the U2000 server processes. This topic describes how to shut down the database
on the HA system.
E.3 Stopping the VCS Service

This topic describes how to stop the VCS service.
E.4 Power Off the Server Safely

Before shutting down the U2000 server, stop the U2000 server processes and the database. This
topic describes how to power off the U2000 HA System (SUSE Linux, PC Server).

E.1 Stopping the U2000 Server Processes

Do not stop the U2000 server processes when the U2000 server is managing NEs. Stop the
U2000 server processes only for some special purposes, for example, changing the system time
of the computer where the server is installed or upgrading the version. This topic describes how
to stop the U2000 server processes on the SUSE Linux HA system.
Prerequisites
Exit all running U2000 clients.
Procedure
Step 1 Log in to the OS of the active site as the root user.
Step 2 Stop the U2000 server processes.

l GUI mode:
1. Open a terminal window, run the following command:
# hagui&
NOTE
NOTE
If you are logging in to the VCS for the first time, you need to create a new Cluster.
3. Click OK.
NOTE

4. Click OK.
5. Choose AppService from the navigation tree.
6. Click the Resources tab. Right-click NMSServer and choose Offline > Host name
from the shortcut menu. In the Question dialog box, click Yes.
have been stopped.
l CLI mode:
NOTE
Step 3 Ensure that the U2000 is not running.

1. Log in to the OS of the active site as the ossuser user.
2. Run the following command to check the running status of the U2000 process:
$ daem_ps

ossuser 26225 1 0 09:16:02 ? 0:00 imapwatchdog -cmd start -type
standby
3. Run the following commands to stop the U2000 processes:

$ su - root
# exit
4. Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
The process is stopped if the displayed information is empty.
----End
E.2 Shutting Down the Database

The U2000 can start properly only after the database is started. Before shutting down the
database, stop the U2000 server processes. This topic describes how to shut down the database
on the HA system.
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Perform the following operations to disable the Sybase database service at the primary site in
the HA system:
NOTE
By default, the Sybase database service at the secondary site is not running.

l GUI mode:
2. Run the following command to start the VCS client at the primary site:
# hagui&
3. Choose File > New Cluster from the main menu. In the window that is displayed, enter
the IP address of the server and click OK.
NOTE
5. On the VCS client of the primary site, right-click the NMSServer node and choose
7. After the NMSServer node is dimmed, right-click the BackupServer node and choose
9. After the BackupServer node is dimmed, right-click the DatabaseServer node and
choose Offline > hostname from the shortcut menu.
l CLI mode:
NOTE
Run the following command to check whether the Sybase database service is disabled:
If the following message is displayed, the Sybase database service has been disabled:
root 9629 14603 0 07:46:52 pts/3 0:00 grep sybase
----End
E.3 Stopping the VCS Service

This topic describes how to stop the VCS service.

Prerequisites
The U2000 and database must have been shut down.
Context
Before powering off the server safely, manually stop the VCS service; otherwise, the server may
fail to shut down properly.
Procedure
Step 1 Log in to the OS on the server as the root user.
Step 2 Run the following command to stop the VCS service:
# hastop -all -force
----End
E.4 Power Off the Server Safely

Before shutting down the U2000 server, stop the U2000 server processes and the database. This
topic describes how to power off the U2000 HA System (SUSE Linux, PC Server).
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
l The VCS services must have been shut down.
Procedure
Step 2 Run the following commands to shut down the OS.

# shutdown -h now
----End

Server) F Getting Started
F Getting Started
This topic describes certain common operations that can be performed on the SUSE Linux
workstation. After learning this topic, you can improve the efficiency of the operations on the
SUSE Linux OS.
Syntax Structure of Command Lines
NOTICE
The number pad keyboard is not recommended. This is because Num Lock may fail to work
normally when the OS is installed on certain machines.
On the desktop of the GUI OS, right-click in the blank area and choose Open Terminal from
the shortcut menu to access the CLI.
The syntax structure of command lines is as follows:

command option parameter
The SUSE Linux commands are case-sensitive. That is, the OS considers an uppercase letter
and its corresponding lowercase letter two different letters. For example, when you want to use
the command for displaying the files in the certain directory, the OS can correctly run the ls
command, but it cannot run the Ls command because the Ls command is considered as an invalid
system command. The options in the SUSE Linux commands are used to change the command
execution method. Generally, the options start with the en-dash (-).
For example, run the following command to display the files and the related details in the /opt
directory:
ls -al /opt
Input Mode for SUSE Linux OS

Click the keyboard icon on the lower-right corner of the desktop and set the input mode to
English/Keyboard.

Switching Users
The SUSE Linux OS has strict user management rules. Different OS users can access only
associated applications.
l To switch OS users, run the following command:

su - OS user name
Leave a space between - and OS user name.
For example, to switch to the ossuser user, run the following command:
su - ossuser
NOTE
The differences between su - ossuser and su ossuser are as follows:

l After the su - ossuser user is switched to the ossuser user, both the operational permissions and
environmental variables of the ossuser user are obtained.
l After the su ossuser user is switched to the ossuser user, only operational permissions and not
environmental variables of the ossuser user are obtained.
l To exit an OS user, run the following command:
exit
NOTE
To switch back to the root user, run the exit command several times until the prompt changes to #.
Directory Browsing and Control Commands

Command/Usage Example Description
cd directory cd /opt Switches to another directory.
ls option file directory ls -al /opt Displays the directory

contents or file information.
mkdir directory mkdir install Creates a directory.
pwd pwd Displays the current directory

of the user.
rm file name rm file.tar Deletes a file.
vi file name vi file Create and modify text a file.
rmdir directory rmdir temp Deletes an empty directory.
fdisk option fdisk -l Views the quantity of disks.
man command man pwd View the online help about a

command.

Logging in to the SUSE Linux OS Through Remote Login Software

There are many remote login software products, such as the PuTTY. This topic takes the PuTTY
as an example. The PuTTY is used to log in to the server from a remote site through command
lines.
NOTE
The PuTTY is a free software used to log in to the UNIX OS by commands. You can access http://
www.putty.org to download the PuTTY. For more information about software operation, see the software
Help or go to the official website of the software for technical support.
1. Double-click the shortcut icon of the PuTTY software on the desktop. The following dialog
box is displayed.
The following table shows the login configurations.
Host Name (or IP address) Specifies the IP address of the server to be

logged in to, for example, 10.71.225.89.

Connection type Specifies the connection type. You need to

select a connection type as required.
Generally, select SSH (more secure,
recommended) or Telnet.
NOTE
l If the operating system is not enabled with
security hardening, this parameter can be
set to either Telnet or SSH. SSH is
recommended because it is more secure
than Telnet.
l If the operating system is enabled with
security hardening or the Telnet service is
disabled, this parameter can be set to SSH
only.
Saved Sessions This parameter cannot be set.
Close window on exit This parameter cannot be set. The default

value is Only on clean exit.
2. Set the parameters for logging in to the server. Then, click Open. The login dialog box is
displayed.
3. Enter the login user name, and then press Enter.
4. Enter the login password, and then press Enter.
Logging in to the SUSE Linux OS Using Remote GUI Software

There is various remote GUI software, for example, VNC. For details about how to configure
and use the VNC, see A.1.12 How to Use the VNC to Remotely Log In to SUSE Linux by
Retaining the Session.
NOTE
l When the remote desktop system is used, choosing Computer > Shutdown or Computer >
Logout > Switch User does not take effect. To shut down the system or switch to another user, run
associated CLI commands.
l If you enter the SUSE Linux login window by the IMM IP address, press Alt+Tab to switch to the
SUSE Linux login window, and characters cannot be entered, press Alt and try again.
Logging in to the SUSE Linux OS Through the Windows OS CLI

1. Choose Start > Run on the Windows OS desktop.
2. In the Run dialog box, enter cmd, and then click OK. The CLI is displayed.
3. In the CLI, enter telnet IP address of the server to be logged in to, and then press Enter.
Login:
NOTE
In Windows 7, if the telnet command fails, choose Start > Control Panel > Programs > Programs and
Features > Turn Windows features on or off and select Telnet Client.
4. Enter the name of the user who logs in to the OS of the server, for example, root. Then,
press Enter.

Password:
5. Enter the login password of the user. Press Enter to log in to the OS.
Restarting the SUSE Linux OS

Run the following commands to restart the OS:
# shutdown -r now
When you restart the OS, the remote login user exits. It takes approximately 5 to 8 minutes to
restart the system. After the OS is restarted, re-log in to the server by referring to the preceding
login method.
Shutting down the SUSE Linux OS

Run the following commands to shut down the OS:
# shutdown -h now
Difference Between Command Operations on the Solaris and SUSE Linux OSs
Table F-1 Difference between command operations on the Solaris and SUSE Linux OSs
Command operation On Solaris On SUSE Linux
Restart the OS. Run the following commands Run the following commands
to restart the OS: to restart the OS:
# sync;sync;sync;sync # sync;sync;sync;sync
# shutdown -y -g0 -i6 # shutdown -r now
Shut down the OS. Run the following commands Run the following commands
to shut down the OS: to shut down the OS:
# sync;sync;sync;sync # sync;sync;sync;sync
# shutdown -y -g0 -i5 # shutdown -h now
Disable system hardening. Run the following command Run the following command
to disable system hardening to disable system hardening
for the SetSolaris system: for the SetSuse system:
# sek -r all # sek -b all
Table F-2 Difference between common operations on the Solaris and SUSE Linux OSs
Common operation On Solaris On SUSE Linux
U2000 client Supported Not supported

Server) G Planning Disk Partitions
G Planning Disk Partitions
This part can be skipped if the OS is installed with the quick installation DVD because the
installation software automatically partitions disks according to the disk size.
Server Not Connecting to a Disk Array

A standard IBM server and Huawei RH series rack server to be delivered must be equipped with
eight hard disks. The planning for RAID levels and partitions is as follows:
NOTE
l For details about the method of checking disk partitions, see A.1.6 How to Check Disk Partitions.
l If the number of hard disks configured for a server and the hard disk size are not standard, contact
Huawei technical support engineers to obtain the hard disk partitioning plan.
Table G-1 Planning for the first and second hard disks for a server with hard disks
Disk Disk RAID Main Exten Logic Partit Size Remarks

Grou Partit ded al ion (GB)
p ion Partit Partit Name
ion ion
- 0 and 1 1 sda1 - - / 50 - Used

to
sda2 swap 32 install

Disk Disk RAID Main Exten Logic Partit Size Remarks

Grou Partit ded al ion (GB)
p ion Partit Partit Name
ion ion
- sda3 sda5 /usr 20 OS

data.
sda6 /var 20
sda7 /opt 120 Used

to
store
the
associ
ated
Sybas
e and
engine
ering
softwa
re.
sda8 / 20 -
export
/home
Table G-2 Planning for the third, fourth, fifth, sixth, seventh, and eighth hard disks for a server
with hard disks
Disk Disk RAID Volum Type Mount Size Remarks

Group e ing (GB)
point
datadg/ 2, 3, 4, 10 lvdata File /opt/ 100 Used to Used to

disk02 and 5 volume sybase/ store store
data databas service
e data. data
and
lv_back /opt/ 400 Used to softwar
up backup store e.
backup
data.
datadg/ 6 0 srl_vol Raw SRL 100 Used to SRL

disk03 volume replication.
- 7 - - - - - Used for hot

backup of service
data and software
disk groups.

Server Connecting to a Disk Array

Configure two hard disks for the IBM server and Huawei RH series rack server with standard
delivery configurations. Configure 12 hard disks for the OceanStor S3900 disk array. The RAID
and partition planning is as follows:
hard disks.
NOTE
l For details about the method of checking disk partitions, see A.1.6 How to Check Disk Partitions.
l If the number of hard disks configured for a server and the hard disk size are not standard, contact
Huawei technical support engineers to obtain the hard disk partitioning plan.
Table G-3 Hard disk partition planning for the IBM server
Disk Disk RA Main Exte Logi Partitio Size Remarks

Group ID Partiti nded cal n Name (GB)
on Parti Part
tion itio
n
- 0 and 1 1 sda1 - - / 50 It is the root

partition.
sda2 swap 32 It is used for

switching data
in the system.
- sda3 sda5 /usr 20 It is used for

storing
programs or
files of users.
sda6 /var 20 It is used for

storing system
logs.
sda7 /opt 120 It is used for

storing U2000
software and
engineering-
related
software.
sda8 /export/ 20 It is the main

home user directory.

Server) H Configuring Disk Arrays
H Configuring Disk Arrays
This topic describes how to configure the OceanStor S3900 disk arrays.
H.1 Configuring the OceanStor S3900 Disk Array by Using the ISM
This topic describes how to configure the OceanStor S3900 disk array using the ISM.

H.1 Configuring the OceanStor S3900 Disk Array by Using

the ISM
This topic describes how to configure the OceanStor S3900 disk array using the ISM.
Prerequisites
l The IP addresses for both controllers of OceanStor S3900 the disk array are configured.
For details about how to set and view the IP addresses for controllers of the OceanStor
S3900, see 3.3.3 Setting the SC IP Address for the OceanStor S3900 Disk Array.
l The primary and secondary power supplies of the disk array have been powered on. For
more information, see 3.2 Powering On a Server.
l The Window management terminal must communicate properly with the disk array
controller.
l Users are logged in to the ISM from the Windows management terminal by using Internet
Explorer 6.0, Internet Explorer 7.0, Internet Explorer 8.0, or Internet Explorer 9.0.
Context
NOTE
The ISM software will lock up if an operation is not performed within 10 minutes after login. Enter the
password again to log in if lock up occurs.
You need to respectively configure the disk arrays on the primary site and secondary site. The following
takes the configuration of the disk array on the primary site as an example.
The following table shows the configuration requirements on the OceanStor S3900 disk array.
NOTICE
If the selected disk arrays are not the OceanStor S3900 disk arrays (12x600 GB), contact Huawei
engineers for details about how to configure the disk arrays.
Configure Settings
Item
Hot-spare The sixth disks act as hot backup disks.

disk
Host group Set the host group name to HostGroup001.

and host For the primary site, the host name is set to Primaster; for the secondary site,
the host name is set to Secmaster.

Configure Settings
Item
RAID group l Set the RAID group name to RAID001.

l Set the RAID Level to RAID10.
l Set the disk type to SAS.
l The first ten disks serve as the RAID group.
LUN Configure one LUN as follows:

l LUN information
– Name: LUN001
– Capacity: 1000 GB
– Stripe unit size: 32 KB
– Home controller: controller A
l Cache strategy
– Prefetch strategy: intelligent
– Write strategy: write back (mirroring)
l Mapping mode
Mapping object: host group name HostGroup001
Port l Set the type to FC.

l Set the name associated with the first identifier to port1.
l Set the name associated with the second identifier to port2.
Procedure
Step 1 Log in to the ISM.
1. Open the Internet Explorer on the Windows management terminal.
2. Enter https://XXX.XXX.XXX.XXX (more secure, recommended) or http://
XXX.XXX.XXX.XXX in the address bar of the Internet Explorer (where
XXX.XXX.XXX.XXX indicates the IP address of the management network port of the
storage array controller). Such as https://129.9.1.10.
NOTE
If "The page cannot be displayed" is displayed on the Internet Explorer, the Windows management
terminal and the disk array controller fail to communicate with each other. Check the network
connection.
The system will navigate to the default login window of the ISM, as shown in the following
figure.
3. Click Click Here to Launch OceanStor ISM. The system will check whether the ISM is
installed on the Windows management terminal.

NOTICE
Before installing the ISM, install the Java runtime environment (JRE). The JRE version
must be 1.6.0 or later (excluding version 1.6.0.20). In the CLI, run the java -version
command to view the JRE version. If the JRE is not installed, click Please Setup JRE.
If the ISM is not installed on the Windows management terminal, the system will
automatically download and install the ISM by means of the Java web start (JWS). If the
ISM is installed on the Windows management terminal, the system will automatically check
the software version. If the version of the ISM is not the latest version, the system will
automatically upgrade the software to the latest version.
4. In the Warning - Security dialog box, select Always trust content from this publisher
and click Run.
Step 2 Discover disk arrays.

1. In the Welcome window of the ISM, click Discover array. The Discover array dialog
box will be displayed, as shown in the following figure.

2. Select a mode for discovering disk arrays according to the conditions at your site. Table
H-1 describes the parameters for discovering disk arrays.
Table H-1 Parameters for discovering disk arrays
Authenticati The associated disk arrays can be found only when the entered user name
on and password are the same as those of the disk arrays.
Username The default user name for logging in to the ISM is admin.
Password The default password is Admin@storage. Change the password after

login and keep it secret.
Authenticati Select a desired authentication mode. Choose Local Device from the
on Mode drop-down list.
Device Type Select a desired device type. Choose Storage Unit from the drop-down
list.

Discovery Indicates that the discovery range is the IP address subnet segments on
Modes which the ISM client resides. The mode is by default selected.
Specify IP Indicates that disk arrays are discovered according to the IP address of
address the management network port on the specified disk array.
When you specify the IP address, the first field on the left ranges from 1
to 223 (except 127), the last field ranges from 1 to 254, and the other
fields range from 0 to 255.
Specify IP Indicates that disk arrays are discovered according to the IP address
Segment segment of the management network port on the specified disk array.
Start IP Address and End IP Address indicate the start and end IP
addresses of disk arrays to be discovered. When setting this parameter,
pay attention to the following points:
l The discovery range is the IP subnet segment of the ISM client.
l The first field on the left ranges from 1 to 223 (except 127), the last
field ranges from 1 to 254, and the other fields range from 0 to 255.
l The start IP address must be smaller than or equal to the end IP
address.
Local sub- Indicates that the discovery range is the IP subnet segment of the ISM
network client. This mode is the default discovery mode of the system.
3. Click OK. After the system successfully discovers storage arrays, the message Discover
device succeed. is displayed on Task Manager.

Step 3 Initialize configurations.

1. In the left -hand navigation tree, click the Assistant tab for the current device to perform
initialize configurations.
Display the initialization page.
2. Click Initial Configuration to initialize disk arrays.

The Initial Configuration dialog box is displayed.
3. In the Device Basic Information text box, enter the desired device name. In the Device
Name text box, enter the desired position and change the login password. Table H-2 shows
the parameter description.
Table H-2 Parameters for modifying a disk array
Paramet
er Description
Device Specifies the name of the OceanStor S3900 disk array to be configured.
Name When setting this parameter, note that:
l This parameter contains only the characters and numerals in DBC case,
underscores (_), en-dash symbols (-), and simplified Chinese characters.
l This parameter consists of 1 to 32 characters. A Chinese character counts
for two DBC characters.
Location Specifies the location of the OceanStor S3900 disk array to be configured.
When setting this parameter, note that:
l This parameter contains only the characters and numerals in DBC case,
underscores (_), en-dash symbols (-), and simplified Chinese characters.
l This parameter consists of 1 to 32 characters. A Chinese character counts
for two DBC characters.

Paramet
er Description
Old Specifies the original password.

Password NOTE
The default user name and password of the system administrator are admin and
Admin@storage. To ensure system security, log in to the ISM to change the password
periodically. To ensure the security of the U2000, passwords must be complex enough.
For example, a password must contain eight or more characters of two types. The
allowed characters are digits, letters, and special characters. Remember to change
passwords regularly.
New Specifies the new password. It ranges from 6 to 16 characters.

Password
Confirm Confirms the new password. When setting this parameter, pay attention to
Password the following points:
l This parameter ranges from 6 to 16 characters.
l This parameter value must be the same as the value of New Password.
4. Click Next. The Device Time Management dialog box is displayed. Table H-3 shows the
parameter description.

Table H-3 Description about device time management parameters
Synchronize Specifies that the time or time zone of the current client has been
Client Time synchronized to the device side. Ensure that time settings are correct
before performing synchronization.
NTP Specifies that the time settings on the NTP server are automatically
Automatic synchronized to the device side. Note that Server IP address and Synch
synchronizi Schedule(number of hours) must be set.
ng
Manual Specifies a manual modification of the time and time zone of the device.
Modificatio Click Modify. In the Modify Time dialog box, set the time and time zone
n of the device.
Not Modify Specifies that the current device or time zone is not modified.
Device
Time
5. Select the desired time and date and click Next to access the FC Host Port dialog box.
NOTE
This operation can modify the port rate. By default, Configuration Rate is set to Auto-Adapt.
6. Click Next to access the Event Notification dialog box. By default, no settings are
performed. To perform settings, select the Enable check box. Table H-4 shows the
description about all the associated parameters. Click Apply.

Table H-4 Description about event notification parameters
Email The following parameters must be set if the notification is sent through
Notificatio emails.
n l Level settings: Select the level at which users can receive fault
information.
l Outbox settings: Set Sender Email, SMTP Server, and SMTP
Port.
l Receive box: Specifies the inbox in which fault information is
received. You can add multiple boxes and use a semicolon to separate
them.
SMS The following parameters must be set if notifications are sent through
Notificatio SMS:
information.
l SMS center service number: Enter a desired SMS center service
number as prompted.
l Receive number: Specifies the number for receiving fault information.
You can add multiple numbers and use a semicolon to separate them.
System The notifications are sent based on the system status.

Status NOTE
Notificatio This parameter is available only when the configurations for email notification and
n SMS notification are correct.

Syslog The following parameters must be set if notifications are sent through
Notificatio syslogs:
information.
l Receive IP address: Specifies the IP address for receiving fault
information. You can add multiple IP addresses and use the semicolon
to separate them.
7. Click Next to access the License Management dialog box. No license needs to be selected.
Click Finish to complete system initialization.
Step 4 Assign storage space.

1. Click the All Devices tab in the navigation tree. Select OceanStor S3900 to be configured.
2. Click the Assistant tab in the navigation tree. Click Allocate Storage Space. The Allocate
Storage Space Wizard dialog box.
3. Select a value from the Block Storage Pool Type drop-down list in Select Block Storage
Pool.
4. Click Create. The Create RAID Group dialog box is displayed. Table H-5 shows the
description about all the associated parameters. After the parameter settings are complete,
click OK. In the dialog box that is displayed, click OK.

Table H-5 Description about parameters for creating a RAID group
Parame
ter Description
Name Specifies the name of a RAID. The default value is RAID001.
Disk Specifies the type of a disk. The default value is SAS.

Type
Level The default value is RAID 10.

Parame
ter Description
Select In the area, set Sub-Group Disks and Available Disks.

Disks
Sub- Specifies the number of sub-hard disks to be configured. The default value
Group is 2.
Disks
Manual Set this parameter to Manual to select all hard disks.
a. After all configurations are performed based on Table H-5, click OK.
b. In the Information dialog box, click OK.
c. In the dialog box indicating successful creation, click Finish as prompted.
5. Click Next to access the Create LUN dialog box. Table H-6 shows the description about
all the associated parameters.
Table H-6 Description about parameters for creating a LUN
Name Specifies the name of the LUN to be configured. The default value is
LUN001.

Number Specifies the number of LUNs to be configured. Set this parameter to

1.
Capacity Specifies the capacity of the LUN to be configured. Set this parameter
to 1000GB.
Stripe Depth The default value is 64 KB. Set this parameter to 32 KB.
(KB)
Owning Specifies the controller to which the LUN to be configured belongs.

Controller Set this parameter to Controller A.
6. Click Next to access the Mapping dialog box. Select the mapping host.
a. Click Create Host Group. The default host group name is HostGroup001. Click
OK.
b. Click Create Host. Select HostGroup001 as the host group. Keep the default host
name Host001 and set the OS type to Linux.
c. Click Next. Select already connected on the FC initiator.
d. Click Next. No configuration is required.
e. Click Next. Confirm the parameter settings. Click Finish.
f. After the configuration succeeds, click Close.
7. Select Host001. Click Next. In the Summary dialog box, confirm configurations.
8. Click Finish to view the execution result.

Step 5 Check the connection of the fiber card.

1. Log in to the server OS as user root.
2. Run the following command to check the connection status of the port on the fiber card:
# cd /sys/class/scsi_host/hostport ID
# cat state
NOTE
In the preceding command, port ID indicates the ports through which the disk array connects to the
server.
You can run the lsscsi command to query port IDs. The first column in the returned message displays
the port IDs of the fiber card. For example, run the following command:
# lsscsi
[0:0:0:0] disk IBM-ESXS CBRBA146C3ETSO N C49B -

[0:0:1:0] disk IBM-ESXS CBRBA146C3ETSO N C49B -
[0:1:0:0] disk LSTLOGIC Logical Volume 3000 /dev/sda
[3:0:0:0] disk HUAWEI S3900 1 /dev/sdb
[4:0:0:0] disk HUAWEI S3900 1 /dev/sdc
Find the last two lines containing OceanStor S3900 in the fourth column. Information in the first
columns ([3:0:0:0] and [4:0:0:0]) indicates that the OceanStor S3900 disk array connects to the
server through port 3 and port 4.
Link Up - Loop
NOTE
If the fiber card is not in the Link Up state, check and ensure the following aspect:
l The fiber is properly connected to the optical module.
l There is not any damage to the fiber.
l The optical module is properly connected to the fiber card.
l The indicator of the fiber card is functioning properly.

3. Run the following commands to restart the OS of the server and refresh the disk status:
# shutdown -r now
----End

Server) I Glossary and Abbreviations
I Glossary and Abbreviations
A
access control list A list of entities, together with their access rights, which are authorized to have access
to a resource.
access control right The level of right granted to a user for his access to certain items.
ACL See access control list
advanced telecom A platform that is used by the hardware of the N2510. To expand the system capacity
application smoothly, you only need to add certain boards to the shelf and need not replace the server.
environment This helps reduce the investments of the customer.
AIS See Alarm Indication Signal
Alarm A message reported when a fault is detected by a device or by the network management
system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm An operation performed on an alarm. Through this operation, the status of an alarm is
acknowledgement changed from unacknowledged to acknowledged, which indicates that the user starts
handling the alarm. The process during which when an alarm is generated, the operator
needs to acknowledge the alarm and take the right step to clear the alarm.
alarm correlation rule A process of analyzing the alarms that meet alarm correlation rules. If alarm 2 is
analyzing generated within 5 seconds after alarm 1 is generated and meets the alarm correlation
analysis rules, the EMS masks alarm 2 or improves its severity level according to the
alarm correlation rules.
alarm delay time The alarm delay time consists of the start delay time and the end delay time. When an
NE detects an alarm for a period, the period is the start delay time. When an NE detects
that the alarm disappears for a period, the period is the end delay time. Unnecessary
alarms that are caused by error reports or jitters can be avoided by setting the delay time.

alarm indication On the cabinet of an NE, there are four indicators in different colors indicating the current
status of the NE. When the green indicator is on, it indicates that the NE is powered on.
When the red indicator is on, it indicates that a critical alarm is generated. When the
orange indicator is on, it indicates that a major alarm is generated. When the yellow
indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on
the front panel of a board indicates the current status of the board. (Metro)
Alarm Indication A code sent downstream in a digital network as an indication that an upstream failure
Signal has been detected and alarmed. It is associated with multiple transport layers. Note: See
ITU-T Rec. G.707/Y.1322 for specific AIS signals.
alarm mask On the host, an alarm management method through which users can set conditions for
the system to discard (not to save, display, or query for) the alarm information meeting
the conditions.
alarm reporting to the On a device, an alarm is reported to the EMS at once after the alarm is generated. On the
EMS immediately EMS client, the corresponding alarm information is displayed on the alarm panel.
alarm severity The significance of a change in system performance or events. According to ITU-T
recommendations, an alarm can have one of the following severities:Critical, Major,
Minor, Warning.
alarm status The devices in the network report traps to the NMS, which displays the alarm statuses
in the topological view. The status of an alarm can be critical, major, minor and prompt.
alarm synchronization When alarm synchronization is implemented, the EMS checks the alarm information in
its database and on the NEs. If the alarm information on the two locations is inconsistent,
the alarm information on the NEs is synchronized to the EMS database to replace the
original records.
ALC link A piece of end-to-end configuration information, which exists in the equipment (single
station) as an ALC link node. Through the ALC function of each node, it fulfils optical
power control on the line that contains the link.
ARP Proxy When a host sends an ARP request to another host, the request is processed by the
DSLAM connected to the two hosts. The process is called ARP proxy. This protocol
helps save the bandwidth in the networking of a low-rate WAN or helps implement the
layer 3 communication between access devices in the networking of layer 2 isolation.
Asynchronous A data transfer technology based on cell, in which packets allocation relies on channel
Transfer Mode demand. It supports fast packet switching to achieve efficient utilization of network
resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte
header.
ATAE See advanced telecom application environment
ATM See Asynchronous Transfer Mode
Authority and Domain The function of the NMS for authority management. With this function, you can:
Based Management
1. Partition and control the management authority
2. Manage device nodes and service data by region
3. Allocate users with different management and operation rights for different regions
auto-negotiation An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to
automatically exchange information over a link about speed and duplex abilities.

bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BASE A kind of bus or plane used to load software, transmit alarms and maintain information
exchange.
basic input/output A firmware stored in the computer mainboard. It contains basic input/output control
system programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
BFD See Bidirectional Forwarding Detection
Bidirectional A simple Hello protocol, similar to the adjacent detection in the route protocol. Two
Forwarding Detection systems periodically send BFD detection messages on the channel between the two
systems. If one system does not receive the detection message from the other system for
a long time, you can infer that the channel is faulty. Under some conditions, the TX and
RX rates between systems need to be negotiated to reduce traffic load.
BIOS See basic input/output system
board Board refers to an electronic part that can be plugged in to provide new capability. It
comprises chips and electronic components and these components are always on a flat
and hard base and connected through conductive paths. A board provides ports for
upstream connections or service provisioning.
Bond Bond: On the SUSE Linux OS, the bond technology is used to form a virtual layer
between the physical layer and the data link layer. This technology allows two server
NICs connecting to a switch to be bound to one IP address. The MAC addresses of the
two NICs are also automatically bound as one MAC address. In this manner, a virtual
NIC is formed. The bond technology supports two modes: double-live and primary/
secondary. In double-live mode, after receiving request data from a remote server, the
virtual NIC on the server determines data transmission based on an algorithm, improving
network throughput and usability of the server. In primary/secondary mode, if an NIC
does not function properly, services will be automatically switched to the other NIC,
ensuring service protection. The SUSE Linux OS supports the binding of NICs in
primary/secondary mode.
C/S See client/server software architecture

CAR See committed access rate
CAU See Client Auto Update
CDE See Common Desktop Environment
CIR See Committed Information Rate
client A device that sends requests, receives responses, and obtains services from the server.
Client Auto Update This function helps you to automatically detect the update of the client version and
upgrade the client. This keeps the version of the client is the same as that of the server.

Client/Server The model of interaction in a distributed system in which a program at one site sends a
request to a program at another site and awaits a response. The requesting program is
called a client. The program satisfying the request is called the server. It is usually easier
to build client software than build the server software.
client/server software A message-based and modular software architecture that comprises servers and clients.
architecture Compared with the centralized, mainframe, and time sharing computing, the client/server
software architecture improves the usability, flexibility, interoperability, and scalability.
In this architecture, a client is defined as the party that requires services and a server is
defined as the party that provides services. The client/server architecture reduces network
traffic by providing a query response rather than transferring all files.
cluster A mechanism adopted to improve the system performance. Several devices of the same
type form a cluster. The exterior of a cluster is some like a kind of equipment. In the
interior of a cluster, the nodes share the load.
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
Committed The rate at which a frame relay network agrees to transfer information in normal
Information Rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common Desktop The Common Desktop Environment (CDE) is an integrated graphical user interface for
Environment open systems desktop computing. It delivers a single, standard graphical interface for
the management of data and files (the graphical desktop) and applications. CDE's
primary benefits -- deriving from ease-of-use, consistency, configurability, portability,
distributed design, and protection of investment in today's applications -- make open
systems desktop computers as easy to use as PCs, but with the added power of local and
network resources available at the click of a mouse.
Common Object A specification developed by the Object Management Group in 1992 in which pieces of
Request Broker programs (objects) communicate with other objects in other programs, even if the two
Architecture programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and thus does not need to know the structure of the program from which the object
comes. CORBA is designed to work in object-oriented environments. See also IIOP,
object (definition 2), Object Management Group, object-oriented.
Common Object A specification developed by the Object Management Group in 1992 in which pieces of
Request Broker programs (objects) communicate with other objects in other programs, even if the two
Architecture programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and thus does not need to know the structure of the program from which the object
comes. CORBA is designed to work in object-oriented environments. See also IIOP,
object (definition 2), Object Management Group, object-oriented.
CORBA See Common Object Request Broker Architecture
CORBA See Common Object Request Broker Architecture

D
Data Communication Data Communications Channel. The data channel that uses the D1-D12 bytes in the
Channel overhead of an STM-N signal to transmit information on operation, management,
maintenance and provision (OAM&P) between NEs. The DCC channels that are
composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other
DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-
M channel.
data communication A communication network used in a TMN or between TMNs to support the data
network communication function.
data replication link A link used for data replication between the production machine and redundancy
machine. It is separated from the network of the primary links.
DCC See Data Communication Channel
DCN See data communication network
DDN See digital data network
Delay An average time taken by the service data to transmit across the network.
DG disk group
DHCP See Dynamic Host Configuration Protocol
digital data network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
disk mirroring A technique in which all or part of a hard disk is duplicated onto one or more other hard
disks, each of which ideally is attached to its own controller. With disk mirroring, any
change made to the original disk is simultaneously made to the other disks so that if the
original disk becomes damaged or corrupted, the mirror disks will contain a current,
undamaged collection of the data from the original disk.
Dynamic Host A client-server networking protocol. A DHCP server provides configuration parameters
Configuration Protocol specific to the DHCP client host requesting, generally, information required by the host
to participate on the Internet network. DHCP also provides a mechanism for allocation
of IP addresses to hosts.
E
E1 A European standard for high-speed data transmission at 2.048 Mbit/s. It provides 32 x
64 kbit/s channels.
ECC See embedded control channel
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer,
channel to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
Equipment Serial A 32-bit number assigned by the mobile station manufacturer, uniquely identifying the
Number mobile station equipment.
ESN See Equipment Serial Number

Fabric A kind of bus/plane used to exchange system service data.

File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
FTP See File Transfer Protocol
gateway A device to connect two network segments which use different protocols. It is used to
translate the data in the two network segments.
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
GE The IEEE standard dubbed 802.3z, which includes support for transmission rates of1
Gbps (gigabit per second)--1,000 Mbps (megabits per second)--over an Ethernet
network.
GMT See Greenwich Mean Time
GNE See gateway network element
graphical user interface A visual computer environment that represents programs, files, and options with
graphical images, such as icons, menus, and dialog boxes, on the screen.
Greenwich Mean Time The mean solar time at the Royal Greenwich Observatory in Greenwich near London in
England, which by convention is at 0 degrees geographic longitude.
GUI See graphical user interface
HA See High Availability

HA system See high availability system
half-duplex A transmitting mode in which a half-duplex system provides for communication in both
directions, but only one direction at a time (not simultaneously). Typically, once a party
begins receiving a signal, it must wait for the transmitter to stop transmitting, before
replying.
High Availability The ability of a system to continuously perform its functions during a long period, which
may exceeds the suggested working time of the independent components. You can obtain
the high availability (HA) by using the error tolerance method. Based on learning cases
one by one, you must also clearly understand the limitations of the system that requires
an HA ability and the degree to which the ability can reach.
high availability system The high availability system (HA) system indicates that two servers are adopted by a
same computer. When the primary server is faulty, the secondary server provides the
environment on which the software runs through the related technology.
History alarm The confirmed alarms that have been saved in the memory and other external memories.

host The computer system that is connected with disks, disk subsystems, or file servers and
on which data is stored and I/Os are accessed. A host can be a large computer, server,
workstation, PC, multiprocessor computer, and computer cluster system.
I
IANA See Internet assigned numbers authority
ICA See independent computing architecture
ICMP See Internet Control Message Protocol
IE See Internet Explorer
IEEE See Institute of Electrical and Electronics Engineers
iMAP See integrated management application platform
independent An architecture that logically separates application execution from user interfaces to
computing architecture transmit only keyboard actions, mouse responses, and screen updates on the network.
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
integrated N/A
management
application platform
International Standard One of two international standards bodies responsible for developing international data
Organization communications standards. International Organization for Standardization (ISO) works
closely with the International Electro- technical Commission (IEC) to define standards
of computing. They jointly published the ISO/IEC SQL-92 standard for SQL.
International An organization that establishes recommendations and coordinates the development of
Telecommunication telecommunication standards for the entire world.
Union
Telecommunication
Standardization
Internet assigned The organization operated under the IAB. IANA delegates authority for IP address-space
numbers authority allocation and domain-name assignment to the NIC and other organizations. IANA also
maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
Internet Control A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
Message Protocol other information relevant to IP packet processing. For example, it can let the IP software
on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Explorer Microsoft's Web browsing software. Introduced in October 1995, the latest versions of
Internet Explorer include many features that allow you to customize your experience on
the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.

Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an Internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part. The
entire protocol suite is often referred to as TCP/IP because TCP and IP are the two
fundamental protocols. IP is standardized in RFC 791.
Internet Protocol A update version of IPv4. It is also called IP Next Generation (IPng). The specifications
Version 6 and standardizations provided by it are consistent with the Internet Engineering Task
Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the
Internet Protocol, designed as the successor to IPv4. The specifications and
standardizations provided by it are consistent with the Internet Engineering Task Force
(IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
inventory A physical inventory in the U2000, that is, a physical resource such as a
telecommunications room, rack, NE, subrack, board, subboard, port, optical module,
fiber/cable, fiber and cable pipe, link resource, interface resource, access service, ONU,
or NE e-label that can be managed on the U2000, and the relationship between resources.
IP See Internet Protocol
IPv4 The abbreviation of Internet Protocol version 4. IPv4 utilizes a 32bit address which is
assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each address consists of a network number, an optional subnetwork
number, and a host number. The network and subnetwork numbers together are used for
routing, and the host number is used to address an individual host within the network or
subnetwork. IPv4 addresses may also be represented using CIDR (Classless Inter
Domain Routing).
IPv6 See Internet Protocol Version 6
ISO See International Standard Organization
ITU-T See International Telecommunication Union Telecommunication Standardization
Java Virtual Machine The environment in which Java programs run. The Java Virtual Machine gives Java
programs a software-based computer they can interact with. Because the Java Virtual
Machine is not a real computer but exists in software, a Java program can run on any
physical computing platform.
JRE Java runtime environment
JVM See Java Virtual Machine
keyboard, video, and A hardware device installed in the integrated configuration cabinet. KVM serves as the
mouse input and output device for the components inside the cabinet. It consists of a screen, a
keyboard, and a mouse.
KVM See keyboard, video, and mouse

L
LAN See Local Area Network
LCT See Local Craft Terminal
LDAP See Lightweight Directory Access Protocol
License A permission that the vendor provides for the user with a specific function, capacity, and
durability of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes, and the operation authority varies with different level of
license.
Lightweight Directory An TCP/IP based network protocol that enables access to a DSA. It involves some
Access Protocol reduced functionality from X.500 DAP specification.
Link Layer Discovery The Link Layer Discovery Protocol (LLDP) is an L2D protocol defined in IEEE 802.1ab.
Protocol Using the LLDP, the NMS can rapidly obtain the Layer 2 network topology and changes
in topology when the network scales expand.
LLDP See Link Layer Discovery Protocol
load balancing The distribution of activity across two or more servers or components in order to avoid
overloading any one with too many requests or too much traffic.
Local Area Network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Local Craft Terminal Local Craft Terminal. The terminal software that is used for local maintenance and the
management of NEs in the singer-user mode, to realize integrated management of multi-
service transmission network. See also U2000.
M
MAN See Metropolitan Area Network
MD5 See Message-Digest Algorithm 5
MDP See message dispatch process
message dispatch N/A
process
Message-Digest A one-way hashing algorithm that produces a 128-bit hash. Both MD5 and Secure Hash
Algorithm 5 Algorithm (SHA) are variations on MD4 and are designed to strengthen the security of
the MD5 hashing algorithm.
Metropolitan Area A metropolitan area network (MAN) is a network that interconnects users with computer
Network resources in a geographic area or region larger than that covered by even a large local
area network (LAN) but smaller than the area covered by a wide area network (WAN).
The term is applied to the interconnection of networks in a city into a single larger
network (which may then also offer efficient connection to a wide area network). It is
also used to mean the interconnection of several local area networks by bridging them
with backbone lines. The latter usage is also sometimes referred to as a campus network.

modem A device or program that enables a computer to transmit data over, for example,
telephone or cable lines. Computer information is stored digitally, whereas information
transmitted over telephone lines is transmitted in the form of analog waves. A modem
converts between these two forms.
MS Manual Switch
MSTP See multi-service transmission platform
MSuite NMS maintenance suite
multi-service A platform based on the SDH platform, capable of accessing, processing and transmitting
transmission platform TDM services, ATM services, and Ethernet services, and providing unified management
of these services.
N
NBI See northbound interface
NE See network element
network element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control board which manages and monitors the
entire network element. The NE software runs on the system control board.
network layer The network layer is layer 3 of the seven-layer OSI model of computer networking. The
network layer provides routing and addressing so that two terminal systems are
interconnected. In addition, the network layer provides congestion control and traffic
control. In the TCP/IP protocol suite, the functions of the network layer are specified
and implemented by IP protocols. Therefore, the network layer is also called IP layer.
Network Management A system in charge of the operation, administration, and maintenance of a network.
System
Network Time Protocol The Network Time Protocol (NTP) defines the time synchronization mechanism. It
synchronizes the time between the distributed time server and the client.
new technology file An advanced file system designed for use specifically with the Windows NT operating
system system. It supports long filenames, full security access control, file system recovery,
extremely large storage media, and various features for the Windows NT POSIX
subsystem. It also supports object-oriented applications by treating all files as objects
with user-defined and system-defined attributes.
NMS See Network Management System
northbound interface The interface that connects to the upper-layer device to realize service provisioning,
report alarms and performance statistics.
NTFS See new technology file system
NTP See Network Time Protocol
O
OAM See operation, administration and maintenance

Object Set A collection of managed objects. Object sets are established to facilitate the user right
management. If a user (or user group) is authorized with the operation rights of an object
set, the user (or user group) can perform all the authorized operations on all the objects
within the object set. This saves you the trouble of setting the management rights for
each NE one by one. Object sets can be created by geographical area, network layer,
equipment type and so on.
OMC See Operation and Maintenance Center
ONU See Optical Network Unit
Operation and An Operations and Maintenance Centre is an element within a network management
Maintenance Center system responsible for the operations and maintenance of a specific element or group of
elements. For example an OMC-Radio may be responsible for the management of a radio
subsystem where as an OMC-Switch may be responsible for the management of a switch
or exchange. However, these will in turn be under the control of a NMC (Network
Management Centre) which controls the entire network.
Operation Rights Operation Rights specify the concrete operation that the user can perform. The operation
right aims at the security objects. If one user has no right to manage one device, he or
she cannot operate the device.
Operation Set A collection of operations. Classifying operations into operation sets helps to manage
user operation rights. Operations performed by different users have different impacts on
system security. Operations with similar impacts are classified into an operation set.
Users or user groups entitled to an operation set can perform all the operations in the
operation set. The NMS provides some default operation sets. If the default operation
sets cannot meet the requirements for right allocation, users can create operation sets as
required.
Operation System Operation System is abbreviated to OS. OS is the interface between users and computers.
It manages all the system resources of the computer, and also provides an abstract
computer for users. With the help of OS, users can use the computers without any direct
operation on hardware. For the computer system, OS is a set of programs used to manage
all system resources; for users, OS provides a simple and abstract method to use the
system resources.
operation, A group of network support functions that monitor and sustain segment operation,
administration and activities that are concerned with, but not limited to, failure detection, notification,
maintenance location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
Operations Support A system whose main function is to run applications that manage network elements,
System networks and services.
Optical Network Unit A form of Access Node that converts optical signals transmitted via fiber to electrical
signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
OS See Operation System
OSS See Operations Support System

P
packet loss ratio The ratio of total lost packet outcomes to total transmitted packets in a population of
interest.
packet transport N/A
network
PC See Personal Computer
Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
Personal Computer A computer used by an individual at a time in a business, a school, or at home.
PIR See Peak Information Rate
PMU The unit that is used to monitor power supply in the equipment.
Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating
over Ethernet PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard
PPP features such as authentication, encryption, and compression.
port 1. Of a device or network, a point of access where signals may be inserted or extracted,
or where the device or network variables may be observed or measured. (188)
2. In a communications network, a point at which signals can enter or leave the
network en
Power and The power and environment monitoring unit is installed at the top of the cabinet of the
environment SDH equipment and is used to monitor the environment variables, such as the power
monitoring unit supply and temperature. With external signal input through the relay, fire alarm, smoke
alarm, burglary alarm, etc. can be monitored as well. With the display on NMS system,
the change of environment can be monitored timely and accurately. For the equipment
installed with a power & environment monitoring board, the following parameters can
be set: relay switch output control, temperature alarm threshold, relay usage and alarm
setting, query of DIP switch status, etc.
PPPoE See Point-to-Point Protocol over Ethernet
private network A network which provides services to a specific set of users only (see Recommendation
I.570).
PSTN See public switched telephone network
PTN See packet transport network
public switched Public Switched Telephone Network. A telecommunications network established to
telephone network perform telephone services for the public subscribers.Sometimes called POTS.
R
RADIUS See remote authentication dial-in user service
RADIUS See Remote Authentication Dial in User Service
RAID See Redundant Arrays of Independent Disks

Redundant Arrays of A data storage scheme that allows data to be stored and replicated in a hardware disk
Independent Disks group (logical hard disk) consisting of multiple hard disks (physical hard disks). When
multiple physical disks are set up to use the RAID technique, they are said to be in a
RAID array. The hard disks in a RAID array provides higher data reliability and input/
output performance. There are various defined levels of RAID, each offering differing
trade-offs among access speed, reliability, and cost. At present, there are seven basic
RAID levels from RAID 0 to RAID 6. These basic RAID levels can be further combined
to form new RAID levels, such as RAID 10 (a combination of RAID 0 and RAID 1).
Remote Authentication RADIUS was originally used to manage the scattered users who use the serial interface
Dial in User Service and modem, and it has been widely used in NAS. NAS delivers the information of users
on authentication, authorization and accounting to the RADIUS server. RADIUS
stipulates how the user and accounting information is transferred between NAS and
RADIUS. The RADIUS server is responsible for receiving the connection request from
users to complete authentication, and returning the configurations of the users to NAS.
remote authentication A security service that authenticates and authorizes dial-up users and is a centralized
dial-in user service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
replicated volume N/A
group
replication link A link used for data replication between the production machine and redundancy
machine. It is physically separated from the network of the primary links.
Rlink See data replication link
RTN Radio Transmission Node
RVG See replicated volume group
S
Script file It is the text file describing the physical information and configuration information of
the entire network, including the NE configuration file, port naming file, end-to-end
configuration file, NE physical view script file, NMS information file and service
implementation data script file.
SDH See Synchronous Digital Hierarchy
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Shell (SSH) A set of standards and an associated network protocol that allows establishing a secure
channel between a local and a remote computer. A feature to protect information and
provide powerful authentication function for a network when a user logs in to the network
through an insecure network. It prevents IP addresses from being deceived and plain text
passwords from being captured.
Secure Sockets Layer A protocol for ensuring security and privacy in Internet communications. SSL supports
authentication of client, server, or both, as well as encryption during a communications
session.
Security Log Security logs record the security operations on the NMS, such as logging in to the server,
modifying the password, and exiting from the NMS server.

Serial Line Interface Serial Line Interface Protocol, defines the framing mode over the serial line to implement
Protocol transmission of messages over the serial line and provide the remote host interconnection
function with a known IP address.
server 1. On a local area network, a computer running administrative software that controls
access to the network and its resources, such as printers and disk drives, and
provides resources to computers functioning as workstations on the network.
2. On the Internet or other network, a computer or program that responds to commands
from a client. For example, a file server may contain an archive of data or program
files; when a client submits a request for a file, the server transfers a copy of the
file to the client.
3. A network device that provides services to network users by managing shared
resources, often used in the context of a client-server architecture for a LAN.
SFTP See Secure File Transfer Protocol (SFTP)

SSH See Secure Shell (SSH)
shelf management The shelf management board of the ATAE server.
module
Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the
amplitude of noise signals at a given point in time. SNR is expressed as 10 times the
logarithm of the power ratio and is usually expressed in dB (Decibel).
Signal to Noise Ratio The signal-to-noise ratio margin represents the amount of increased received noise (in
Margin dB) relative to the noise power that the system is designed to tolerate and still meet the
target BER of accounting for all coding gains included in the design.
Simple Mail Transfer The TCP/IP (Transmission Control Protocol/Internet Protocol) protocol which facilitates
Protocol the transfer of electronic-mail messages, specifies how two systems are to interact, and
the format of messages used to control the transfer of electronic mail.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Simple Network Time A protocol that is adapted from the Network Time Protocol (NTP) and synchronizes the
Protocol clocks of computers over the Internet.
SLIP See Serial Line Interface Protocol
SMM See shelf management module
SMTP See Simple Mail Transfer Protocol
SNMP See Simple Network Management Protocol
SNR See Signal Noise Ratio
SNRM See Signal to Noise Ratio Margin
SNTP See Simple Network Time Protocol
SONET See Synchronous Optical Network

SQL See structured query language

SSL See Secure Sockets Layer
static route A route that cannot adapt to the change of network topology. Operators must configure
it manually. When a network topology is simple, the network can work in the normal
state if only the static route is configured. It can improve network performance and ensure
bandwidth for important applications. Its disadvantage is as follows: When a network is
faulty or the topology changes, the static route does not change automatically. It must
be changed by the operators.
Stelnet Secure Shell Telnet
structured query A database query and programming language widely used for accessing, querying,
language updating, and managing data in relational database systems.
SVM Solaris Volume Manager
Switching restoration It refers to the period of time between the start of detecting and the moment when the
time line is switched back to the original status after protection switching occurs in the MSP
sub-network.
Synchronous Digital SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines
Hierarchy the transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.
Synchronous Optical Synchronous Optical Network, is a method for communicating digital information using
Network lasers or light-emitting diodes (LEDs) over optical fiber. The method was developed to
replace the Plesiochronous Digital Hierarchy (PDH) system for transporting large
amounts of telephone and data traffic and to allow for interoperability between
equipment from different vendors. SONET defines interface standards at the physical
layer of the OSI seven-layer model. The standard defines a hierarchy of interface rates
that allow data streams at different rates to be multiplexed. SONET establishes Optical
Carrier (OC) levels from 51.8 Mbps (OC-1) to 9.95 Gbps (OC-192).
SYSLOG Syslog is an industry standard protocol for recording device logs.
TCP See Transmission Control Protocol

TCP/IP See Transmission Control Protocol/Internet Protocol
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T
Management Network for managing open systems in a communications network.An architecture for
management, including planning, provisioning, installation, maintenance, operation and
administration of telecommunications equipment, networks and services.
Telnet Standard terminal emulation protocol in the TCP/IP protocol stack. Telnet is used for
remote terminal connection, enabling users to log in to remote systems and use resources
as if they were connected to a local system. Telnet is defined in RFC 854.
TFTP See Trivial File Transfer Protocol

Time zone A division of the earth's surface, usually extending across 15 degrees of longitude devised
such that the standard time is the time at a meridian at the centre of the zone.
timing task The system can create a timing task (such as backing up, loading and recovering a task),
management run a timing task automatically, and suspend or resume a timing task.
TMN See Telecommunication Management Network
Transmission Control One of the core protocols of the Internet protocol suite. Using TCP, applications on
Protocol networked hosts can create connections to one another, over which they can exchange
streams of data. TCP guarantees reliable and in-order delivery of data from the sender
to the receiver. TCP also distinguishes data for multiple connections by concurrent
applications running on the same host.
Transmission Control Common name for the suite of protocols developed to support the construction of
Protocol/Internet worldwide internetworks.
Protocol
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication. TFTP is
small enough to be contained in ROM to be used for bootstrapping diskless machines.
UDP See User Datagram Protocol

UPS Uninterruptible Power Supply
User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
VCS See Veritas Cluster Server

Veritas Cluster Server A High-availability cluster software, for Unix, Linux and Microsoft Windows computer
systems, created by Veritas Software. It provides application cluster capabilities to
systems running Databases, file sharing on a network, electronic commerce websites or
other applications.
Veritas Volume A software product from veritas Inc.. The Veritas Volume Manager is used to manage
Manager disk storage.
Veritas Volume A wide area network data replication solution offered by VERITAS for multiple
Replicator operating systems. These include. AIX, HPUX, Solaris and Windows 2000.
Virtual Local Area A logical grouping of two or more nodes which are not necessarily on the same physical
Network network segment but which share the same IP network number. This is often associated
with switched Ethernet.

Virtual Router A protocol used for multicast or multicast LANs such as an Ethernet. A group of routers
Redundancy Protocol (including an active router and several backup routers) in a LAN is regarded as a virtual
router, which is called a backup group. The virtual router has its own IP address. The
host in the network communicates with other networks through this virtual router. If the
active router in the backup group fails, one of the backup routers become the active one
and provides routing service for the host in the network.
VLAN See Virtual Local Area Network
volume A logical unit for disk virtualization management, and basic object for host applications.
VRRP See Virtual Router Redundancy Protocol
VVM See Veritas Volume Manager
W
WAN See Wide Area Network
wavelength division A technology that utilizes the characteristics of broad bandwidth and low attenuation of
multiplexing single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple
channels to transmit simultaneously in a single fiber.
WDM See wavelength division multiplexing
Wide Area Network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
Wireless Local Area A generic term covering a multitude of technologies providing local area networking via
Network a radio link. Examples of WLAN technologies include WiFi (Wireless Fidelity), 802.11b
and 802.11a, HiperLAN, Bluetooth, etc.
WLAN See Wireless Local Area Network
work station A terminal or microcomputer, usually one that is connected to a mainframe or to a
network, at which a user can perform applications.
WS See work station


iManager U2000 Local HA System (Veritas) Software Installation and Commissioning Guide (SUSE Linux, PC Server)-(V200R014C50_01)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

iManager U2000 Local HA System (Veritas) Software Installation and Commissioning Guide (SUSE Linux, PC Server)-(V200R014C50_01)

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management

Local High Availability System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2014-05-20) Huawei Proprietary and Confidential i

About This Document

Product Name Version

iManager U2000 V200R014C50

This document is intended for:

l Technical support engineers

Indicates an imminently hazardous situation

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Issue 01 (2014-05-20) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Calls attention to important information, best

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 by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Issue 01 (2014-05-20) Huawei Proprietary and Confidential iii

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Changes in Issue 01 (2014-05-20) Based on Product Version V200R014C50

Issue 01 (2014-05-20) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

Issue 01 (2014-05-20) Huawei Proprietary and Confidential v

4 Separating the Primary Site from the Secondary Site........................................................168

Issue 01 (2014-05-20) Huawei Proprietary and Confidential vi

A.1.14 How to Capture Snapshots on SUSE Linux.........................................................................................................222

Issue 01 (2014-05-20) Huawei Proprietary and Confidential vii

A.4.2.7 How to Manually Start the VVR.........................................................................................................................302

Issue 01 (2014-05-20) Huawei Proprietary and Confidential viii

A.7 Install the U2000 Software Exception Processing ....................................................................................................346

B Uninstalling the U2000 Software...........................................................................................361

C Manual Commissioning Task................................................................................................368

D Starting the U2000 Server in a SUSE Linux High Availability System.........................379

I Glossary and Abbreviations....................................................................................................416

Issue 01 (2014-05-20) Huawei Proprietary and Confidential ix

About This Chapter

1.1 Networking Structure

1.2 Configuration Requirements

1.3 Restrictions on Installation and Commissioning

Issue 01 (2014-05-20) Huawei Proprietary and Confidential 1

1.1 Networking Structure

Primary Site Secondary Site

System/Application line (Bond protection)

Issue 01 (2014-05-20) Huawei Proprietary and Confidential 2

Primary Site Secondary Site

Application line (Bond protection)

Issue 01 (2014-05-20) Huawei Proprietary and Confidential 3

1.2 Configuration Requirements

Issue 01 (2014-05-20) Huawei Proprietary and Confidential 4

Network Scale Server Description

Small-scale network: less IBM X3650 M4

Medium-scale network: IBM X3850 X5

Large-scale network: For access single-domain cases:

Issue 01 (2014-05-20) Huawei Proprietary and Confidential 5

Network Scale Server Description

Super-large-scale For access single-domain cases: