Imanager U2000 V200R016C60 Cold Standby & Single-Server System Software Installation and Commissioning Guide (SUSE Linux) 13 (PDF) - C

iManager U2000 Unified Network Management
System
V200R016C60
Cold Standby & Single-Server

System Software Installation and
Commissioning Guide (SUSE Linux)
Issue 13
Date 2018-08-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. 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 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. i

iManager U2000 Unified Network Management System
Cold Standby & Single-Server System Software Installation
and Commissioning Guide (SUSE Linux) About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V200R016C60
Intended Audience
This document describes how to install the U2000 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 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. 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.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. iii

> 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 13 (2018-08-31) Based on Product Version V200R016C60

The thirteenth commercial release has the following updates:
Fixed some bugs.

The twelfth commercial release has the following updates:
Fixed some bugs.

The eleventh commercial release has the following updates:
Fixed some bugs.

The tenth commercial release has the following updates:
Fixed some bugs.

The ninth commercial release has the following updates:
Fixed some bugs.

The eighth commercial release has the following updates:
Fixed some bugs.

The seventh commercial release has the following updates:
l Changed the document content and name.
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. iv

– Added the cold standby delivery scenario and single-server delivery scenario.
– Changed the document name to iManager U2000 V200R016C60 Cold Standby &
Single-Server System Software Installation and Commissioning Guide (SUSE
Linux).
l Fixed some bugs.

The sixth commercial release has the following updates:
Fixed some bugs.

The fifth commercial release has the following updates:
Fixed some bugs.

The fourth commercial release has the following updates:
Fixed some bugs.

The third commercial release has the following updates:
Fixed some bugs.

The second commercial release has the following updates:
Fixed some bugs.

Initial release.
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. v

and Commissioning Guide (SUSE Linux) Contents
Contents
About This Document.....................................................................................................................ii

1 Installation Overview................................................................................................................... 1
1.1 Networking Structure..................................................................................................................................................... 1
1.2 Configuration Requirements...........................................................................................................................................4
1.3 Restrictions on Installation and Commissioning............................................................................................................ 6
2 Installing and Commissioning the U2000 (Factory Installation of the Cold Standby
Solution)............................................................................................................................................. 8
2.1 Solution Description....................................................................................................................................................... 9
2.2 Commissioning Process................................................................................................................................................12
2.3 Preparing for Commissioning.......................................................................................................................................13
2.3.1 Collecting Commissioning Information.................................................................................................................... 14
2.3.2 Checking Required Software.....................................................................................................................................22
2.3.3 Applying for a U2000 License.................................................................................................................................. 23
2.3.4 Applying for the SSR License................................................................................................................................... 24
2.4 Checking Hardware Connections................................................................................................................................. 25
2.5 Powering On a Server...................................................................................................................................................28
2.6 Configuring Controller IP Addresses........................................................................................................................... 30
2.6.1 Configuring the iMana/iBMC IP Address of Huawei server.................................................................................... 31
2.6.1.1 Configuring the iMana IP Address Through iMana Management Interface (HUAWEI RH5885H V3 and
HUAWEI RH2288H V2)....................................................................................................................................................31
2.6.1.2 Configuring the iBMC IP Address Through iBMC Management Interface(HUAWEI RH2288H V3 and
HUAWEI RH5885H V3)....................................................................................................................................................34
2.6.1.3 Configuring the iMana/iBMC IP Address Through BIOS..................................................................................... 37
2.6.2 Setting the SC IP Address for the OceanStor 5500 V3 Disk Array.......................................................................... 38
2.7 Commissioning the U2000........................................................................................................................................... 42
2.7.1 Obtaining Commissioning Parameters...................................................................................................................... 43
2.7.2 Configuring System Commissioning Parameters......................................................................................................81
2.7.3 Loading a U2000 License..........................................................................................................................................85
2.7.4 Commissioning U2000 Parameters........................................................................................................................... 89
2.7.5 Checking the Installation of the U2000..................................................................................................................... 91
2.8 Configuring the Cold Standby Solution....................................................................................................................... 94
2.8.1 Configuring Automatic Backup Tasks on the Primary Site.......................................................................................94
2.8.2 Configuring Automatic Restoration on the Secondary Site...................................................................................... 97
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. vi

3 Installing and Commissioning the U2000 (Factory Installation of the Single-Server

System)........................................................................................................................................... 101
3.1 Solution Description................................................................................................................................................... 102
3.2 Commissioning Process..............................................................................................................................................102
3.3 Commissioning Preparation....................................................................................................................................... 103
3.3.1 Collecting Commissioning Information.................................................................................................................. 103
3.3.2 Checking Required Software................................................................................................................................... 111
3.3.3 Applying for a U2000 License.................................................................................................................................112
3.3.4 Applying for the SSR License................................................................................................................................. 113
3.4 Checking Hardware Connections............................................................................................................................... 114
3.5 Powering On a Server................................................................................................................................................. 117
3.6 Configuring Controller IP Addresses......................................................................................................................... 119
3.6.1 Configuring the iMana/iBMC IP Address of Huawei server.................................................................................. 120
HUAWEI RH2288H V2)..................................................................................................................................................120
HUAWEI RH5885H V3)..................................................................................................................................................123
3.6.1.3 Configuring the iMana/iBMC IP Address Through BIOS................................................................................... 126
3.6.2 Setting the SC IP Address for the OceanStor 5500 V3 Disk Array........................................................................ 127
3.7 Commissioning the U2000......................................................................................................................................... 131
3.7.1 Obtaining Commissioning Parameters.................................................................................................................... 132
3.7.2 Configuring System Commissioning Parameters....................................................................................................170
3.7.3 Loading a U2000 License........................................................................................................................................174
3.7.4 Commissioning U2000 Parameters......................................................................................................................... 178
3.7.5 Checking the Installation of the U2000................................................................................................................... 180
4 Installing and Commissioning the U2000 (Fresh Installation).........................................184

4.1 Solution Description................................................................................................................................................... 185
4.2 Installation and Commissioning Process.................................................................................................................... 185
4.2.1 Installation and Commissioning Process (Single-Server System).......................................................................... 185
4.2.2 Installation and Commissioning Process (Cold Standby Solution).........................................................................188
4.3 Preparing for Installation............................................................................................................................................ 188
4.3.1 Collecting Installation Information......................................................................................................................... 189
4.3.1.1 Collecting Installation Information (Single-Server System)................................................................................ 189
4.3.1.2 Collecting Installation Information (Cold Standby)............................................................................................. 196
4.3.2 Checking Required Software...................................................................................................................................205
4.3.3 Applying for a U2000 License................................................................................................................................ 213
4.3.4 Applying for the SSR License................................................................................................................................. 214
4.4 Checking Hardware Connections............................................................................................................................... 215
4.5 Powering On a Server.................................................................................................................................................222
4.6 Configuring Controller IP Addresses......................................................................................................................... 226
4.6.1 Configuring the iMana/iBMC IP Address of Huawei server.................................................................................. 226
HUAWEI RH2288H V2)..................................................................................................................................................227
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. vii

HUAWEI RH5885H V3)..................................................................................................................................................229
4.6.1.3 Configuring the iMana/iBMC IP Address Through BIOS................................................................................... 232
4.6.2 Configuring the IMM IP Address............................................................................................................................233
4.6.2.1 Configuring the IMM IP Address Through IMM Management Interface(IBM X3650 M4)...............................234
4.6.2.2 Configuring the IMM IP Address Through IMM Management Interface (IBM X3850 X5 and IBM X3650 M3)
.......................................................................................................................................................................................... 237
4.6.2.3 Configuring the IMM IP Address Through BIOS................................................................................................240
4.6.3 Configuring Controller IP Addresses for Disk Arrays............................................................................................ 245
4.6.3.1 Setting the SC IP Address for the OceanStor 5500 V3 Disk Array..................................................................... 245
4.6.3.2 Setting the SC IP Address for the OceanStor S3900 Disk Array......................................................................... 249
4.7 Configuring RAID...................................................................................................................................................... 254
4.7.1 Configuring the RAID in Remote Mode (Huawei RH2288H V3 and Huawei RH5885H V3, ISO)......................254
4.7.2 Configuring the RAID in Remote Mode (Huawei RH5885H V3 or Huawei RH2288H V2, ISO)........................ 259
4.7.3 Configuring the RAID in Local Mode (IBM X3850 X5 and IBM X3650 M3, Manually).................................... 265
4.7.4 Configuring the RAID in Local Mode (IBM X3650 M4, Manually)..................................................................... 274
4.8 Installing the SUSE Linux OS by Using the Quick Installation CD-ROM................................................................283
4.8.1 Remotely Installing the SUSE Linux Operating System (Huawei RH series rack server, DVD/ISO)................... 284
4.8.2 Remotely Installing the SUSE Linux Operating System (IBM X3650 M4, DVD/ISO).........................................291
4.8.3 Remotely Installing the SUSE Linux Operating System (IBM X3850 X5 and IBM X3650 M3, DVD/ISO)........299
4.8.4 Locally Installing the SUSE Linux Operating System (IBM Server, DVD)...........................................................307
4.8.5 Locally Installing the SUSE Linux Operating System (Huawei RH series rack server, DVD)..............................312
4.9 Installing the U2000 Software.................................................................................................................................... 317
4.9.1 Preparing Software Packages.................................................................................................................................. 317
4.9.2 Preconfiguring the OS ............................................................................................................................................ 319
4.9.3 Starting the U2000 Installation Program................................................................................................................. 330
4.9.3.1 Installing the U2000 on the GUI.......................................................................................................................... 330
4.9.3.2 Installing the U2000 Through the CLI................................................................................................................. 336
4.10 Commissioning the U2000....................................................................................................................................... 341
4.10.1 Obtaining Commissioning Parameters.................................................................................................................. 341
4.10.2 Configuring System Commissioning Parameters..................................................................................................379
4.10.3 Loading a U2000 License......................................................................................................................................383
4.10.4 Commissioning U2000 Parameters....................................................................................................................... 387
4.10.5 Checking the Installation of the U2000................................................................................................................. 389
4.11 Configuring the Cold Standby Solution (Cold Standby Solution)........................................................................... 392
4.11.1 Configuring Automatic Backup Tasks on the Primary Site...................................................................................392
4.11.2 Configuring Automatic Restoration on the Secondary Site...................................................................................395
A FAQs............................................................................................................................................399
A.1 SUSE Linux OS......................................................................................................................................................... 399
A.1.1 How to Change the OS User Password.................................................................................................................. 399
A.1.2 How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS.............................................................. 401
A.1.3 How to Enable and Disable the FTP Authority of the root User in the SUSE Linux OS...................................... 402
A.1.4 How to manually Add the Default Route (SUSE Linux)....................................................................................... 403
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. viii

A.1.5 How to manually Add a Static Route (SUSE Linux)............................................................................................. 404

A.1.6 How to Add a Static Route If the U2000 Is Installed............................................................................................. 404
A.1.7 How to Check Disk Partitions................................................................................................................................ 406
A.1.8 How to Check the Remaining Space of a Disk.......................................................................................................407
A.1.9 How to Monitor System Processes and Application Ports..................................................................................... 407
A.1.10 How to Enable Remote GUI Logins.....................................................................................................................407
A.1.11 How to Query the Process Status..........................................................................................................................408
A.1.12 How to Forcibly End a Process............................................................................................................................ 408
A.1.13 How to Use the vi Editor...................................................................................................................................... 408
A.1.14 How to Change the Time and Time Zone of the SUSE Linux OS....................................................................... 410
A.1.15 How to Use the VNC to Remotely Log In to SUSE Linux by Retaining the Session......................................... 412
A.1.16 How to Set IP Addresses for Unused NICs on SUSE Linux................................................................................421
A.1.17 How to Capture Snapshots on SUSE Linux......................................................................................................... 424
A.1.18 How to Check Whether Bond Is Configured........................................................................................................424
A.1.19 How to Configure the Resolution on SUSE Linux...............................................................................................425
A.1.20 How to Install the 7-zip Software on the SUSE Linux OS...................................................................................429
A.1.21 How to Enable the File Change Audit Function on SUSE Linux OS.................................................................. 430
A.1.22 How Do I Set an Encryption Algorithm for OpenSSH (SUSE Linux)................................................................ 435
A.1.23 How to Check Downloaded Software Packages Using HashMyFiles Software.................................................. 437
A.1.24 How Do I Verify Downloaded Software Packages Using the PGPVerify Software............................................ 438
A.1.25 How to Fix Garbled Characters in the SUSE Linux Command Output............................................................... 442
A.1.26 Checking the NTP Service on Linux.................................................................................................................... 443
A.1.27 How to Use the FileZilla to Transfer Files by SFTP............................................................................................ 446
A.1.28 What Can I Do If Logging In to the GUI Desktop Fails in SUSE Linux.............................................................449
A.2 System Settings of the Huawei RH series rack server...............................................................................................451
A.2.1 How Do I Use iMana/iBMC IP to Log In to a Remote Huawei RH series rack server......................................... 452
A.2.2 How to View the IP Address of the iMana/iBMC on the Huawei RH series rack server...................................... 454
A.2.3 How to Change the Password of iMana/iBMC User Root..................................................................................... 458
A.2.4 How to Solve iMana/iBMC Problems.................................................................................................................... 461
A.2.5 Mappings Between Physical and Logical Network Interfaces on an Huawei RH series rack server Running SUSE
Linux.................................................................................................................................................................................464
A.2.6 Formatting disks (Huawei RH5885H V3 or Huawei RH2288H V2).....................................................................466
A.2.7 Formatting disks (Huawei RH2288H V3 or Huawei RH5885H V3).....................................................................470
A.2.8 Viewing Hard Disk Information (Huawei RH5885H V3 or Huawei RH2288H V2).............................................472
A.2.9 Viewing Hard Disk Information (Huawei RH2288H V3 or Huawei RH5885H V3).............................................475
A.2.10 How to Upgrade the System Controller Firmware Version for Huawei RH5885H V3 and RH2288H V2 Servers?
.......................................................................................................................................................................................... 477
A.2.11 How to Upgrade the System Controller Firmware Version for Huawei RH2288H V3 server and Huawei
RH5885H V3 server?....................................................................................................................................................... 477
A.3 System Settings of the IBM Server........................................................................................................................... 478
A.3.1 How to Solve the Problem Where the Remote Control Desktop Appears and Then Disappears Immediately..... 478
A.3.2 How do I use an IMM IP address to remotely log in to an IBM server (IBM X3650 M4)....................................480
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). 482
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. ix

A.3.4 How to View the IMM IP Address on the IBM Server.......................................................................................... 484
A.3.5 How to Change the Password of the IMM User USERID(IBM X3650 M4).........................................................488
A.3.6 How to Change the Password of the IMM User USERID(IBM X3850 X5 and IBM X3650 M3)........................491
A.3.7 How to Solve IMM Problems.................................................................................................................................492
A.3.8 Mappings Between Physical and Logical Network Interfaces on an IBM Server Running SUSE Linux............. 494
A.3.9 Viewing Hard Disk Information in Local Mode (IBM Server).............................................................................. 495
A.3.10 Viewing Hard Disk Informationin Remote Mode (IBM X3650 M4)...................................................................497
A.3.11 Viewing Hard Disk Informationin Remote Mode (IBM X3850 X5 and IBM X3650 M3)..................................501
A.3.12 Formatting disks in Local Mode (IBM Server).................................................................................................... 504
A.3.13 Formatting the disks in Remote Mode (IBM X3650 M4).................................................................................... 510
A.3.14 Formatting the disks in Remote Mode (IBM X3850 X5 and IBM X3650 M3)...................................................517
A.3.15 How to Configure the HTTPS on the IMM(IBM X3650 M4)............................................................................. 523
A.3.16 How to Configure the HTTPS on the IMM(IBM X3850 X5 and IBM X3650 M3)............................................ 526
A.4 Sybase Database........................................................................................................................................................ 528
A.4.1 Startup and Shutdown of the Sybase Database.......................................................................................................528
A.4.1.1 How to Disable the Sybase Database Service..................................................................................................... 528
A.4.1.2 How to Start the Sybase Database Service.......................................................................................................... 529
A.4.1.3 How to Verify That the Sybase Database Is Running..........................................................................................529
A.4.2 Sybase Database Maintenance................................................................................................................................530
A.4.2.1 How to Verify That the Sybase Database Has Been Installed............................................................................. 530
A.4.2.2 How to Check the Sybase Database Version....................................................................................................... 530
A.4.2.3 How to View the Server Name of the Sybase Database...................................................................................... 531
A.4.2.4 How to Change the sa User Password for the Sybase Database If the U2000 Is Not Installed...........................532
A.4.2.5 How to Change the Database Administrator Password for the Sybase Database If the U2000 Is Installed....... 533
A.4.2.6 How to View the Bit Number of the Sybase Database........................................................................................ 535
A.4.2.7 How to View the Details of the Sybase Database................................................................................................536
A.4.2.8 How to Create a Replacement User for the Sybase Database Administrator sa User......................................... 537
A.5 U2000 System............................................................................................................................................................539
A.5.1 How to Start the MSuite Client.............................................................................................................................. 539
A.5.2 How to End Processes on the MSuite Server......................................................................................................... 541
A.5.3 Changing the Password of the MSuite....................................................................................................................541
A.5.4 Starting the Process of the MSuite Server.............................................................................................................. 542
A.5.5 How to Verify That the Processes of the U2000 Single-Server System Are Running on SUSE Linux.................543
A.5.6 How to Start the Processes of the U2000 Single-Server System on SUSE Linux................................................. 543
A.5.7 How to End the Processes of the U2000 Single-Server System on (SUSE Linux)................................................544
A.5.8 How to Determine Which Types of Software Are Preinstalled..............................................................................544
A.5.9 Which Installation Packages Are Required for U2000 Installation........................................................................545
A.5.10 How to Set the Communication Mode on the U2000 server for the Single-Server System (SUSE Linux).........547
A.5.11 How to Confirm the Encoding Format of the U2000 License File.......................................................................548
A.5.12 How to Transfer Files by Means of FTP.............................................................................................................. 548
A.5.13 How to Check and Change an OS User ID...........................................................................................................549
A.5.14 How to Burn the ISO File to DVD....................................................................................................................... 550
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. x

A.5.15 How to Check the U2000 Version........................................................................................................................ 551

A.5.16 How to Resolve the U2000 SyslogCollectorDM Service Startup Failure Due to a Port Conflict....................... 552
A.5.17 How Do I Obtain Third-Party Software and Hardware Materials........................................................................554
A.5.18 How Do I Adjust the System Networking Solution............................................................................................. 557
A.5.19 Starting or Stopping the NTP Service on SUSE Linux........................................................................................ 560
A.5.20 How to Query Information About the Software and Hardware Installation and ESNs of a Huawei Rack Server
.......................................................................................................................................................................................... 560
A.5.21 How to Change the Private Key of the SNMPv3 User Between U2000 and the Disk Array.............................. 562
A.5.22 How Can I Change the Password of the H2 Database .........................................................................................566
A.5.23 How Can I Change the Password of the H2 Database File.................................................................................. 568
A.5.24 How Do I Change an H2 Database User's Password for the U2000 Guard......................................................... 569
A.5.25 How Do I Import a U2000 Key Store...................................................................................................................570
A.5.26 How Do I Disable the U2000 from Monitoring the All-Zero IP Address............................................................571
A.5.27 How Do I Perform a Rollback After the H2 Key Replacement Fails...................................................................578
A.5.28 How to Configure Deletion Protection for Non-Dynamic Files on the Linux U2000?........................................578
A.5.29 How to Change the Password for the User ftpuser..............................................................................................579
A.6 Install the U2000 Software Exception Processing ....................................................................................................580
A.6.1 How do I solve the problem where a failure message is displayed during the installation or the installation is
abnormally interrupted..................................................................................................................................................... 580
A.6.2 How to Handle Messages Indicating That the Port Is Occupied During Installation or Uninstall.........................581
A.6.3 How to Rectify the Failure to Connect to the Sybase Database During U2000 Installation..................................582
A.6.4 Failure to Log In to the U2000 Server from a U2000 Client..................................................................................583
A.6.5 How to Resolve the Problem that the License Does Not Take Effect.................................................................... 585
A.6.6 How to Rectify the Failure to Open the CAU Download Web Page Because the Port Is Used.............................586
A.6.7 How to Resolve the Problem that the Database Installation File Is Not Found During Installation...................... 587
A.6.8 How to Address the U2000 Installation or Uninstallation Failure......................................................................... 587
B Uninstalling the U2000 Software........................................................................................... 590

B.1 Uninstall Preparations................................................................................................................................................ 590
B.2 Uninstalling a U2000................................................................................................................................................. 593
B.3 Verifying the Uninstall Status of the Server Software............................................................................................... 596
C Manual Commissioning Task................................................................................................ 597

C.1 Replacing Storage Keys for a Single-Server System (Linux)....................................................................................597
C.2 Configuring a Digital Certificate............................................................................................................................... 600
C.2.1 Replacing SSL Certificates Used for the U2000 Server......................................................................................... 600
C.2.2 Replacing SSL Certificates Used for the Communication Between the U2000 and uTraffic................................ 604
C.2.3 Deploying the SSL Trust Certificate on the Internet Explorer............................................................................... 608
C.3 Setting Hardware Alarm Monitoring......................................................................................................................... 609
C.3.1 Configuring the Monitoring Function for an OceanStor 5500 V3 Disk Array.......................................................609
C.3.2 Configuring the Monitoring Function for an S3900 Disk Array............................................................................ 614
C.3.3 Configuring Hardware Alarms for Huawei RH Series Rack Servers (RH5885H V3 and RH2288H V2, iMana).618
C.3.4 Configuring Hardware Alarms for Huawei RH Series Rack Servers (RH2288H V3 and RH5885H V3, iBMC).622
C.4 Configuring and Testing the FTP Service..................................................................................................................627
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. xi

C.4.1 Overview of the FTP Service Used by the U2000..................................................................................................627

C.4.2 Procedure for Configuring and Testing the FTP Service on the U2000................................................................. 635
C.4.3 Checking the Startup Status of FTP Servers (Linux)..............................................................................................636
C.4.4 Creating an FTP User..............................................................................................................................................637
C.4.5 Creating an FTP Account and Adding it to an FTP Application............................................................................ 640
C.4.6 Testing the FTP Service.......................................................................................................................................... 645
D Starting the U2000 Server....................................................................................................... 647

D.1 Powering On the Server Safely..................................................................................................................................647
D.2 Starting the Database................................................................................................................................................. 649
D.3 Starting the U2000 Server Processes......................................................................................................................... 651
E Shutting Down the U2000 Server...........................................................................................653

E.1 Stopping the U2000 Server Processes........................................................................................................................653
E.2 Shutting Down the Database...................................................................................................................................... 654
E.3 Powering Off the Server Safely................................................................................................................................. 655
F Getting Started...........................................................................................................................657
G Planning Disk Partitions........................................................................................................ 662
H Configuring Disk Arrays........................................................................................................ 666
H.1 Configuring the OceanStor 5500 V3 Disk Array Using the OceanStor DeviceManager......................................... 666
H.2 Configuring the OceanStor S3900 Disk Array by Using the ISM............................................................................ 673
I Glossary and Abbreviations.................................................................................................... 688
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. xii

and Commissioning Guide (SUSE Linux) 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 networking of the single-server system (SUSE Linux) solution and
the cold standby 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.
1.1 Networking Structure

This topic describes the networking of the single-server system (SUSE Linux) solution and
the cold standby solution.
Networking of the cold standby solution

Figure 1-1 shows the networking of the cold standby solution.
Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. 1

Figure 1-1 Networking of the cold standby solution
Terms
To ensure the U2000 install successfully, definitions for terms as used in this document before
introducing the installation 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: 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: 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: The active (standby) state refers to the working (protection) state.
For example, when a site is currently responsible for network management, this site is in
the active state.
Networking Description:

l The U2000 client communicates with the server using a DCN.

l NEs and the OSS communicate using a DCN.
Networking structure of single-server system

Figure 1-2 shows the networking of the single-server system (SUSE Linux).
Figure 1-2 Networking structure of Single-Server System (SUSE Linux)
Terms
To ensure the U2000 install successfully, definitions for terms as used in this document before
introducing the installation 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.

Networking Description:
l The U2000 client communicates with the server using a DCN.
l NEs and the OSS communicate using a DCN.
1.2 Configuration Requirements

This topic describes the configuration requirements on the hardware and software of the
server before installing the U2000.
For the cold standby solution, ensure that the U2000 version, deployment domain, language,
OS type, server time zone, and time are the same on the primary and secondary sites.
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 RH2288H V3

than 500 equivalent NEs l CPU: 2 x Xeon 6-core 2.4 GHz
l Memory: 64 GB
l Hard disk: 8 x 600 GB
Common-scale network: RH2288H V3

500-2000 equivalent NEs l CPU: 2 x Xeon 6-core 2.4 GHz
l Memory: 64 GB
NOTE
When only access-domain NEs are managed, the server also supports
management of a medium-scale network.
Medium-scale network: RH5885H V3

2000-6000 equivalent l CPU: 4 x Xeon 10-core 2.0 GHz
NEs
l Memory: 64 GB
NOTE
When only access-domain NEs are managed, the server also supports
management of a large-scale network.
Large-scale network: RH5885H V3+disk array

6000-15000 equivalent l CPU: 4 x Xeon 10-core 2.0 GHz
NEs
l Memory: 128 GB
NOTE
When only access-domain NEs are managed, the server also manages
20000 equivalent NEs.

Network Scale Server Description
Super-large-scale RH5885H V3 + disk array

network: 15000-30000 l CPU: 4 x E7-8860 18-Core 2.2 GHz
equivalent NEs
l Memory: 256 GB
Table 1-2 Configurations of physical machine disk array

Hardware Disk Array Hardware Capacity
Configuration Item Version
Delivered: OceanStor - 48 GB memory, 12 x 600 GB

5500 V3
Compatible: OceanStor V100R005C02 16 GB memory, 12 x 600 GB

S3900 V100R002C00
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 11 SP3

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 in
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 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3
l Run the following command to view the OS kernel version:
# uname -rv
The information similar to 3.0.101-0.47.105-default is displayed.
Here, 3.0.101-0.47.105-default indicates the kernel version of the
OS.
If the kernel version is 3.0.101-0.47.105-default , the kernel
version is correct.
Database SYBASE 15.7 with EBF26397 + SP138
NMS software U2000 software
NOTE
The preceding table shows the recommended delivery configuration. Compatible software platform:
SUSE Linux Enterprise Server 10 SP4 + SYBASE 15.5, and SYBASE 15.7 with EBF23724 + SP131
cannot be installed on SUSE Linux Enterprise Server 10 SP4 OS. For details about compatible
configuration, see chapter Software Configuration Planning for the NMS Server in the U2000
Planning Guide.
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, do not install the software that fails to pass the verification
test in Huawei Lab 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.

Cold Standby & Single-Server System Software Installation 2 Installing and Commissioning the U2000 (Factory
and Commissioning Guide (SUSE Linux) Installation of the Cold Standby Solution)
2 Installing and Commissioning the U2000

(Factory Installation of the Cold Standby
Solution)
About This Chapter
This topic describes how to collect information required for commissioning the cold standby
solution with factory installation information and how to commission the primary and
secondary sites.
2.1 Solution Description
This topic briefly describes the cold standby solution with factory installation information.
2.2 Commissioning Process
This topic describes the process and required time for commissioning primary and secondary
sites in the cold standby solution with factory installation information.
2.3 Preparing for Commissioning
This topic describes the preparations to be made before the primary and secondary sites of the
cold standby solution with factory installation information is commissioned, including
collecting commissioning information, checking mandatory software, and applying for the
U2000 and SSR licenses.
2.4 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.
2.5 Powering On a Server
This topic describes how to power on a server and the position of the power button.
2.6 Configuring Controller IP Addresses
Controller IP addresses are used to manage and maintain servers remotely. Configure
controller IP addresses for servers before commissioning the operating system (OS).
2.7 Commissioning the U2000
This topic describes how to commission the cold standby solution with factory installation
information. In the cold standby solution with factory installation information, the U2000 has
been installed on the servers before delivery. In this manner, you do not need to install the

U2000 again but commission it directly. Specifically, you can use the U2000 normally only
after changing system and U2000 parameters to meet site requirements. To allow the U2000
to manage your network, you must commission the U2000 before using the U2000 to manage
NEs and configure services.
2.8 Configuring the Cold Standby Solution
The U2000 cold standby solution supports manual and automatic backup and restore. If
manual backup and restore is used, you need to manually start the backup or restoration task
each time. If automatic backup and restore is used, you only need to configure a scheduled
backup task and a scheduled restoration task. Automatic backup and restore is recommended.
In automatic backup and restore mode, you need to configure a scheduled backup task on the
primary site and a scheduled restoration task on the secondary site to implement fast
restoration with cold backup data. For specific operations of manual backup and restore, see
the Manually Execute Backup and Restoration Tasks section of the U2000 Administrator
Guide.

This topic briefly describes the cold standby solution with factory installation information.
In the cold standby solution with factory installation information, the U2000 has been
installed on the primary and secondary servers before delivery. In this manner, you do not
need to install the U2000 again but commission it directly. Specifically, you can use the
U2000 normally only after changing system and U2000 parameters to meet site requirements.
The following describes the background, usage restrictions, and implementation process of
the U2000 cold standby solution in detail.
Context
If only one single server U2000 is deployed at a site, network management functions will
become unavailable if the U2000 fails. To implement fast restoration when the U2000 single-
server system fails, Huawei launches the cold standby solution.
In the cold standby solution, two single server U2000 systems with the same version,
deployment domain, language, OS type, server time, and time zone are deployed. One system
is run on the primary site and the other is run on the secondary site.
l In normal conditions, the primary site provides the network management functions. The
network management process and maintenance tool on the secondary site are stopped
while the database is running. The primary site backs up the network management data
periodically, and the secondary site obtains the backup file from the primary site at
regular intervals.
l If the U2000 on the primary site fails, the U2000 on the secondary site starts
immediately to provide network management functions.

NOTE
l The backup object is the entire database, including the custom data at the U2000 side (excluding the
custom options of the system), network layer trail data, NE-side configuration data, alarm data and
performance data. In addition, a backup is created for the structure of the entire database, all
database tables (including the system tables and the user tables), table structure, and stored
procedures. The personal information (including personal name, phone numbers and addresses) on
the U2000 and all user names and passwords are also backed up. Therefore, you are obligated to
take considerable measures, in compliance with the laws of the countries concerned and the user
privacy policies of your company, to ensure that the personal data of users is fully protected.
l The following data is not backed up when you back up the U2000 database:
l The data that is not saved at the NE side, that is, the data that cannot be uploaded.
l The custom options of the system. For example, font, color setting, and audio setting.
l The function of the fast restoration scheme for the cold standby system and the scheduled tasks on
the U2000 MSuite or U2000 overlaps. You are recommended to execute those tasks at different
time.
Restriction
l Before starting the secondary site, ensure that the license of the U2000 has been loaded
on the secondary site.
NOTE
Please refer 3.3.3 Applying for a U2000 License to generate both the primary and secondary sites
ESNs and send the contract number and the server ESNs to Huawei engineers or the local Huawei
office to apply for a U2000 license.
The U2000 license is loaded at both sites.
l If the database at the primary site has been expanded, the database at the secondary site
must be expanded to the same size; otherwise, restoration may fail.
l If cold standby is performed for the first time in an upgrade scenario, back up data at the
primary site and restore data at the secondary site using the MSuite before configuring a
cold standby task. This prevents a restoration failure due to inconsistent database sizes.
l Automatic backup and restoration scenario:
The OSs of the primary and secondary sites must be the same. That is, if the OS of the
primary site is SUSE Linux, the OS of the secondary site is also SUSE Linux.
Process Introduction to Fast Restoration Scheme for the U2000 Cold Standby
System
backup and a scheduled restoration task. Automatic backup and restore is recommended.
l Automatic backup and restoration scheme: To automatically back up and restore data,
you need to configure scheduled backup tasks on the primary site and automatic
restoration tasks on the secondary site. The process is as follows:
a. On the secondary site, install a single server U2000 whose version, deployment
domain, language and database username are the same as those on the primary site.
b. Configure scheduled backup tasks on the primary site. The backup files are
generated through backup modules and stored on the primary site.
c. Configure scheduled restoration tasks on the secondary site. Obtain the backup files
through SFTP from the primary site and restore the files on the secondary site.

d. When the primary site malfunctions, start the U2000 on the secondary site to fast
restore the U2000.
Figure 2-1 Automatic backup and restoration scheme
l Manual backup and restoration scheme: The manual backup and restoration scheme
requires a cold standby tool to back up and restore data. The process is as follows:
a. On the secondary site, install a single server U2000 whose version, deployment
domain, language and database username are the same as those on the primary site.
b. Use a cold standby tool to back up the U2000 data on the primary site as backup
files and store the files on the primary site.
c. Copy the backup files from the primary site to the secondary site, and use the cold
standby tool to restore the files on the secondary site.
d. Start the U2000 on the secondary site.

Figure 2-2 Manual backup and restoration scheme

This topic describes the process and required time for commissioning primary and secondary
sites in the cold standby solution with factory installation information.
NOTE
If this is the first time you perform operations on the SUSE Linux OS or you are not familiar with the
SUSE Linux OS, see F Getting Started to get an overall understanding of the basic operations on the
SUSE Linux OS.
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-3 shows the installation commissioning process.

Figure 2-3 Commissioning process of the cold standby solution
2.3 Preparing for Commissioning

This topic describes the preparations to be made before the primary and secondary sites of the
cold standby solution with factory installation information is commissioned, including
collecting commissioning information, checking mandatory software, and applying for the
U2000 and SSR licenses.

2.3.1 Collecting Commissioning Information

This topic describes how to collect commissioning information. Before commissioning
primary and secondary sites with factory installation information of the cold standby solution,
collect required information, including the host name, IP address, route, time zone and time,
user password, installation path, component quantity, and instance quantity.
Complete planning for the information listed in the following tables according to the U2000
Planning Guide. Collect and record the commissioning information in the tables.
NOTE
Print the following tables and fill in the blanks with the site-specific planning information.
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 On Solaris/SUSE Linux OS.
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 cannot contain only one character.
l The host name must be case-sensitive.
l The host name cannot be empty or contain spaces.
Table 2-1 Host name list

Site Item Example Plan
Primary site Host name Primaster
Secondary site Host name Secmaster

IP Address Planning
Table 2-2 IP Address Type

IP Address Description
IP address of the For Huawei RH series rack server, IP address of the iMana can be
iMana on the PC used to remotely log in to a PC server to manage and maintain PC
server 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.
IP address for the This IP address is used to remotely manage and maintain disk
disk array controller arrays.
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.
NMS application IP This IP address is used for external NMS services such as
address communication between the NMS server and clients or between the
NMS server and NEs.
l The 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:
– The IP addresses must be unique on the network.
– The NMS application IP address communicates with the managed equipment in the
normal state.
– The NMS application IP address communicates with the OSS in the normal state.
– The NMS application IP address communicates with U2000 clients in the normal
state.
NOTE
Log in to the server OS as user root, run the command ping -S NMS_application_IP
Destination_IP to ensure that NMS application IP address can be normally communicated.
l Single-NIC Scheme
Only one network interface is required and bond cannot be configured.
– Advantage: NIC resources are saved.
– Disadvantage: NIC protection is unavailable.
Table 2-3 shows a planning example.
Table 2-3 Example of IP address planning of the single-NIC scheme

Site Item Example (IP Address/ Description
Subnet Mask/Gateway)
Primary iMana IP 10.9.1.20/255.255.255.0/1 The iMana IP address and

site address 0.9.1.254 system IP address can be


System 10.9.1.2/255.255.255.0/10. located either on the same

IP 9.1.254 network segment or on
address different network segments.
IP l Primary controller: -
address 10.9.1.10/255.255.255.
for the 0/10.9.1.254
disk array l Secondary controller:
controller 10.9.1.11/255.255.255.
0/10.9.1.254
Secondar iMana IP 10.9.1.21/255.255.255.0/1 The iMana IP address and

y site address 0.9.1.254 system IP address can be
located either on the same
System 10.9.1.2/255.255.255.0/10. network segment or on
IP 9.1.254 different network segments.
address
address 10.9.1.12/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.13/255.255.255.
0/10.9.1.254
l Double-NIC Scheme
Two network interfaces are required for configuring bond.
– Advantage: NIC protection is available. If one NIC is faulty, data processing is
switched to the other NIC.
– Disadvantage: One more NIC is used than the single-NIC scheme.
NOTE
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.

Table 2-4 Example of IP address planning of the double-NIC scheme

Primary iMana IP 10.9.1.20/255.255.255.0/1 l The iMana IP address and

site address 0.9.1.254 system IP address can be
address
l The system IP address
corresponds to two NICs
configured with bond. If
eth0 and eth2 interfaces are
selected during system
reconfiguration to configure
bond, the system IP address
corresponds to both the
eth0 and eth2 interfaces.
address 10.9.1.10/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.11/255.255.255.
0/10.9.1.254
Secondar iMana IP 10.9.1.21/255.255.255.0/1 l The iMana IP address and

y site address 0.9.1.254 system IP address can be
address
address 10.9.1.12/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.13/255.255.255.
0/10.9.1.254

Route Planning
Table 2-5 Route list
Item Example Plan
Routing network 10.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

For the cold standby solution, ensure that the time zone and time are the same on the primary
and secondary sites.
Table 2-6 Time zone and time list
Item Example Plan
Time zone Asia > Beijing
Time 14:00
External clock source - -

IP address
User Name and Password Planning
NOTICE
The passwords are examples only. To ensure system security, change the password promptly,
update it periodically, and save it properly. 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.

Table 2-7 User and password list

User Default Password Password Set After Planned Password
Preinstallation
iMana user Huawei12#$ Huawei12#$

root
OS user root Changeme_123 Changeme_123

NOTE
For system security,
modify the default
password and
remember the new
password. For details,
see A.1.1 How to
Change the OS User
Password.
OS user Changeme_123 Changeme_123

ossuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ftpuser NOTE
modify the default
password and
remember the new
see A.5.29 How to
Change the Password
for the User ftpuser.

dbuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.


Preinstallation
H2 database Changeme_123 Changeme_123

user dbuser NOTE
H2 database is used to
store U2000 Guard
alarm information. To
modify a database
password, seeA.5.24
How Do I Change an
H2 Database User's
Password for the
U2000 Guard.

webuser NOTE
l An independent
account used to run
Tomcat and Apache
services.
l For system security,
modify the default
password and
remember the new
password. For
details, see A.1.1
How to Change
the OS User
Password.
OceanStor Admin@storage Changeme_123

5500 V3 user
admin
Kaimse l authenticate l authenticate

NOTE password: password:
Account for ism@Storage ism@Storage
Trap
l private password: l private password:
authenticating
the device ism@Storage ism@Storage
alarms
reported by an
5500 V3 disk
array. The
account
cannot be used
for login.
Database user Changeme_123 Changeme_123

sa


Preinstallation

user ossuser NOTE
The H2 database is
mainly used to store
data of NBI
configuration items.
The default password of
H2 database is
Changeme_123, if you
need to change the
password, see A.5.22
How Can I Change
the Password of the
H2 Database .
H2 database file is
need to change the
How Can I Change
the Password of the
H2 Database File.
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.
U2000 user Changeme_123 Admin_123

admin NOTE
You must change the
default password during
first-time login.


Preinstallation
Network Changeme_123 Changeme_123

Management NOTE
System You must change the
Maintenance default password during
Suite user first-time login.
admin
2.3.2 Checking Required Software

This topic describes how to verify that the software meets U2000 installation requirements.
Table 2-8 Tool list

N Tool Usage Description
o
.
1 7-Zip For Refer to http://downloads.sourceforge.net/sevenzip to

tool extracting download the latest version.
files. For more information about software operation, see the
software Help or go to the official website of the software
http://www.7-zip.org/support.html for technical support.
2 PuTTY The Download the latest version from official websites http://
software www.chiark.greenend.org.uk/~sgtatham/putty/
uses download.html of the third-party software.
commands For more information about software operation, see the
(telnet and software Help or go to the official website of the software
SSH) to log http://www.chiark.greenend.org.uk/~sgtatham/putty/
in to the docs.html for technical support.
server.
Using SSH
(more
secure,
recommend
ed) to log
in to the
server is
recommend
ed.
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
files by http://filezilla-project.org for technical support.
SFTP.

2.3.3 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 the cold standby solution, the primary and secondary sites share the same U2000
license. The U2000 license is bound to the ESNs of the primary and secondary sites at
the same time. When applying for a license, you need to obtain 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 can go to http://support.huawei.com/carrier or http://support.huawei.com/
enterprise to download the ESN tool delivered with the version.
l The ESN tool name is U2000version_ESN_sles_x64.tar.
version indicates the detailed version number of the U2000.
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.1.27 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:****************************************
ESN1:****************************************
ESN2:****************************************
ESN3:****************************************
...
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:****************************************
ESN1:****************************************
ESN2:****************************************
ESN3:****************************************
...
Mode 3: Query information about the software and hardware installation and ESNs of a
Huawei rack server at http://texpert.huawei.com/TExpert/Pages/PageContainer.htm. For
details, see A.5.20 How to Query Information About the Software and Hardware
Installation and ESNs of a Huawei Rack Server.
Step 3 After the esn command is executed, the Esn.txt file is automatically generated in the current
path. Send the contract number and the server ESNs to Huawei engineers or the local Huawei
office.
NOTE
Huawei engineers access http://w3.huawei.com/sdp/ 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
2.3.4 Applying for the SSR License

This topic describes how to apply for a formal SSR license. The SSR license used in NMS
installation is a demo license. After the server is delivered to the installation site, the demo
license must be replaced with a formal SSR license in time.
Prerequisites
l GTS rights for ESDP login are available.
l The license confirmation form or contact number has been obtained.
NOTE
The license confirmation form is delivered in paper format along with the DVD. The license
confirmation form functions as the license file and should be kept properly on site.

Procedure
Step 1 Obtain information used for license download.
l If the license confirmation form has been obtained, send the information to related
Huawei engineers or the local office of Huawei.
l If the license confirmation form has not been obtained, obtain the contract number and
send it to related Huawei engineers or the local office of Huawei.
Step 2 Huawei engineers log in to the ESDP website http://w3.huawei.com/sdp/ (Huawei intranet)
or http://app.huawei.com/isdp/ (Internet) according to the obtained information.
Step 3 In Carrier Navigation, select the ESDP product module.
Step 4 Choose Order Management > Entitlement Management from the left-hand navigation tree.
The Entitlement Management page is displayed.
Step 5 On the Entitlement Management page, enter the following conditions and click Search.
l Entitlement Type: Select The 3rd Party Software.
l Huawei Contract No.: Enter the 14-digit Huawei Contract No..
Step 6 View license information, select the required license, and click Download The 3rd Party
License.
Step 7 Download the license according to the right-hand button status.
l If the Download License button is orange, the license can be downloaded.
l If the Download License button is gray, the requirement has not been confirmed, and
you must wait for a period of time to download the license.
l If the Download License button is unavailable, the license cannot be downloaded.
l If the Reapply button is available, the license has been downloaded, and you can re-
apply for license download. After clicking this button, enter the approver and application
reason and sign a letter of commitment on the Reapply page. Then click Sure to
Download to download the license.
Step 8 After clicking the download button, verify that the information is consistent with information
about installed software. Select I have read already and enter Receiving E-mail address.
Then click Sure to Download.
Step 9 The related Huawei engineer sends the SSR license obtained by email to the user.
NOTE
Keep the license properly. If the license is lost, you can re-download it only after being approved.
----End

Prerequisites
The server hardware must have been installed and equipment cables must have been
connected, for details, see U2000 Hardware Installation Guide (N610E).

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 according to the hardware connection diagram.

NOTE
Connect the network interface that is configured with a system IP address during pre-installation to the
network. If the network interface is not connected to the network, the U2000 fails to synchronize
network configurations or be started. Configuring the system IP address for the network interface with
the smallest interface serial number is preferred. For example,the network interface eth0 with serial
number of 1 can be used for the Huawei RH5885H V3, Huawei RH2288H V3 and Huawei RH2288H
V2 servers.
l Figure 2-4 shows hardware connections for the Huawei RH5885H V3 server.
Figure 2-4 Hardware connection for the Huawei RH5885H V3 server
NOTE
For the mappings between physical and logical network interfaces on a Huawei server, see A.2.5
Mappings Between Physical and Logical Network Interfaces on an Huawei RH series rack
server Running SUSE Linux.
l Figure 2-5 show the hardware connections between the Huawei RH5885H V3 server
and the OceanStor 5500 V3 disk array.

Figure 2-5 Hardware connections between the Huawei RH5885H V3 server and the
OceanStor 5500 V3 disk array
NOTE

NOTE
NOTE
For details about the mapping between physical network interfaces and logical network interfaces,
see A.2.5 Mappings Between Physical and Logical Network Interfaces on an Huawei RH
series rack server 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.


Server
1. Power on a Huawei RH2288H V2/Huawei RH2288H V3/Huawei RH5885H V3 server.
NOTICE
l Huawei RH2288H V2/Huawei RH2288H V3/Huawei RH5885H V3 server supports
100 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 Single-Server System (SUSE Linux), if the power supply is insufficient, the
server automatically stops.
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. For official websites of software and hardware documents, see A.5.17 How Do I
Obtain Third-Party Software and Hardware Materials.
The red boxes in the following figures show the positions of power buttons on Huawei
RH2288H V2, Huawei RH5885H V3, IBM X3650 M4, IBM X3650 M3 and, IBM
X3850 X5.
Figure 2-8 Position of the power button on Huawei RH5885H V3 server
Figure 2-9 Position of the power button on RH2288H V3 server

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.

For OceanStor 5500 V3:
l Normal power-on sequence: 1. Turn on the power switches of the external power
supplies connected to all the devices. 2. Press the power button on either controller. 3.
Turn on the LAN switch or FC switch (if any LAN switch or FC switch is deployed but
is not powered on). 4. Turn on the application server (if the application server is not
powered on).
l Normal power-down sequence: 1. Stop the services of the application server. 2. Hold the
power button for 5 seconds on the controller enclosure. 3. Disconnect the controller
enclosure and disk enclosures from the external power supplies.
NOTE
Power supply must be provided for the two power modules of the OceanStor 5500 V3; otherwise, the
OceanStor 5500 V3 fails to be used. Press the power button on controller A/B. Wait 5 to 10 minutes
until the power indicator is steady green and no longer flashing, indicating the power-on success.
Physical indications that the storage system is up and running without error:
l The power indicators of the controllers, controller enclosure, and disk enclosures are
steady green.
l The alarm indicators of the controllers, controller enclosure, and disk enclosures are off.
l The running indicators of the coffer disks are steady green, and their alarm/location
indicators are off.


2.6.1 Configuring the iMana/iBMC IP Address of Huawei server

The iMana/iBMC is integrated with the Huawei RH series rack server. RH5885H V3 and
RH2288H V2 servers use iMana whereas RH2288H V3 servers use iBMC. It is used to
remotely manage the server. IP address of the iMana/iBMC 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/iBMC IP address are available: through
iMana/iBMC management interface and through BIOS.
If a server is not equipped with the KVM, the mode through iMana/iBMC management
interface is recommended.
l Through iMana/iBMC 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:
i. 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.
ii. 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/iBMC management interface.
NOTE
l For more operations on the Huawei RH5885H V3 server, log in to the server's official website at
http://support.huawei.com/enterprise/productsupport?
lang=en&pid=9768163&idAbsPath=7919749|9856522|9856792|9768163.
2.6.1.1 Configuring the iMana IP Address Through iMana Management Interface

(HUAWEI RH5885H V3 and HUAWEI RH2288H V2)
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 Internet Explorer browsers do not support a proxy server.

l A network cable is available. As network interfaces on a Huawei RH series rack 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/iBMC
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 2-11 Huawei RH5885H V3 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/
iBMC 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 Optional: If the Warning dialog box displayed, 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/iBMC 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
2.6.1.2 Configuring the iBMC IP Address Through iBMC Management

Interface(HUAWEI RH2288H V3 and HUAWEI RH5885H V3)
After an iBMC IP address is set for a Huawei RH2288H V3 server and Huawei RH5885H V3
server, you can remotely manage the server in Web mode. This topic describes how to
configure the iBMC IP address through iBMC management interface.
Prerequisites
l A network cable is available. As network interfaces on a 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 iBMC, see A.2.4 How to Solve iMana/iBMC
Context

in again.
Procedure
Step 1 View the position of the iBMC interface on the Huawei RH2288H V3 server and Huawei
RH5885H V3 server.
A management network port for iBMC is at the end of the Huawei RH2288H V3 server and
Huawei RH5885H V3 server. You can visit iBMC through this port, as shown in the
following figure.
Figure 2-13 Huawei RH2288H V3 server
Step 2 Use a network cable to connect the PC and the iBMC management interface of the server.

address of the iBMC must be in the same network segment.
NOTE
The default IP address of the iBMC is 192.168.2.100 and the default subnet mask is 255.255.255.0. If
the default IP address of the iBMC is changed, see A.2.2 How to View the IP Address of the iMana/
NOTE
The ipaddress is the IP address of the iBMC management network interface.
Step 5 Optional: If the Warning dialog box displayed , click Yes.

NOTE

Step 7 In the upper corner of the iBMC home page, click the Config tab. On the displayed page,
choose NetWork Settings from the navigation tree.
Step 8 In the IPv4 area in Select IP Version and Set IP, select Manually set IP address and set the
iBMC IP address, subnet mask, and default gateway based on actual requirements.
Step 9 Click Save in the IPv4 area. In the Confirm dialog box, click OK.
NOTE
l Type the new iBMC IP in the address bar of Internet Explorer. The Web management page of iBMC
is displayed.

Step 10 Disconnect the iBMC management interface of the server from the PC and connect the iBMC
----End
2.6.1.3 Configuring the iMana/iBMC IP Address Through BIOS

After an iMana/iBMC 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/iBMC 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/iBMC 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/iBMC).

l If log in to the Huawei RH5885H V3 server through iMana, perform the following
operations:
a. Choose Server Mgmt > BMC network configuration, and press Enter. The
BMC network configuration page is displayed.
b. Select IPv4 IP Source, and press Enter. The menu dialog box is displayed.
operations:
a. Choose Advanced > IPMI BMC Configuration, and press Enter. The IPMI
BMC Configuration page is displayed.
l If log in to the Huawei RH5885H V3 server through iBMC, perform the following
operations:
operations:
a. Choose Advanced > IPMI iBMC Configuration, and press Enter. The IPMI
iBMC Configuration page is displayed.
b. Select iBMC Configuration, and press Enter. The iBMC Configuration page is
displayed.

c. Select IP Source under IPV4 Configuration, 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 Set the IP address, subnet mask, and gateway.
l For Huawei RH5885H V3 or Huawei RH2288H V2 server, enter the planned iMana IP
address, subnet mask, and gateway in IPv4 IP Address, IPv4 Subnet Mask, and IPv4
Gateway Address respectively.
l For Huawei RH2288H V3 server, enter the planned iBMC IP address, subnet mask, and
gateway in IP Address, Subnet Mask, and Gateway Address on the IPV4
Configuration tab respectively.
Step 7 Press Enter to accomplish the IP configuration of the iMana/iBMC management module.
Step 8 Press F10 and select Yes from the dialog box to save the configurations and quit the
configuration page.
----End
2.6.2 Setting the SC IP Address for the OceanStor 5500 V3 Disk

Array
This topic describes how to set the SC IP address for the OceanStor 5500 V3 disk array
before using OceanStor 5500 V3 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.
l Optional: For a PC without a DB-9 port, a USB-DB-9 serial cable is available, and the
USB serial port drive has been installed.
l Perform the following operations to query the communication port number on the PC's
serial port:
NOTE
For the laptop, connect the serial port of the local controller to the serial port of the disk array (SERIAL
MGT) first, or can not query the communication port number on the laptop.
a. Right-click Computer on the PC desktop and choose Manage from the shortcut
menu.
b. In the Computer Manage window, choose Computer Manage (local) > System
Tools > Device Manager.
c. Choose ports (COM&LPT) in the right pane of Device Manager to check the
communication port on the PC's serial port, such as COM1.
Context
The OceanStor 5500 V3, a disk array, has two controllers. The IP addresses configured in this
section are examples only. For example, set the IP address of the management network of

controller A to 10.9.1.10 and the IP address of the management network of controller B to

10.9.1.11.
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 ( ).
Use an RJ45 connector at one end of the serial port cable to connect to the serial port of the
disk array ( ) and a DB-9 connector at the other end of the cable to connect to the serial
port of the computer.
Step 2 Log in to a disk array controller.

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:
– Serial line to connect to: COM1
– Speed(baud): 115200
– Data bits: 8
– Stop bits: 1
– Parity: None
– 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.
If the connection succeeds, the following information will be displayed:
Storage login:
6. Enter the user name and password.

NOTE
– The default administrator name is admin and the initial password of the admin user is
Admin@storage. If the U2000 is preinstalled before being delivered, the password has been
changed to Changeme_123. After the initial login, change the default password immediately. 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 an admin user enters an incorrect password for three consecutive times, the admin user will
be locked and therefore cannot be used to log in to the disk array controller. The admin account
will be automatically unlocked after 15 minutes.
– Run the following command to change the password for the current user.
admin:/>change user_password
Old password:old password
New password:new password
Reenter password:new password
Command executed successfully.
If the login succeeds, the following information will be displayed:

Authorized users only. All activity may be monitored and reported.
WARNING: You have accessed the system.

You are required to have a personal authorisation from the system
administrator before you use this computer. Unauthorised access to or misuse
of this system is prohibited.

System Name : xxxx

Health Status : Normal
Running Status : Normal
Total Capacity : 20.241TB
SN : xxxx
Location :
Product Model : xxxx
Product Version : xxxx
Time : xxxx-xx-xx/16:13:47 UTC+08:00
Step 3 Configure the IP address for the management interface of controller A.

1. Run the show system management_ip command to check the port ID of management
ports on each controller.
admin:/> show system management_ip

Port ID : CTE0.A.MGMT
IPv4 Address : 192.168.128.101
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Prefix Length : --
IPv6 Gateway :
--------------------------------------
Port ID : CTE0.B.MGMT
IPv4 Address : 192.168.128.102
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Gateway :
For example, the port ID is CTE0.A.MGMT on controller A and the port ID is

CTE0.B.MGMT on controller B.
2. Run the change system management_ip command to set an IP address for the
management interface on controller A.
Table 2-9 lists the change system management_ip command format and parameter
descriptions.
Table 2-9 Command format and parameter description
Format Parameter Description
change system management_ip – eth_port_id: Indicates a port ID, which

eth_port_id ip_type mask [gateway] can be obtained using the show system
management_ip command.
– ip_type: Indicates an IP address type,
which is ipv4_address or ipv6_address.
– mask: Indicates a management port's
subnet mask.
– gateway: Indicates a management port's
gateway.
Set an IP address for the management port on controller A.

For example, if the configured IP address is 10.9.1.10, subnet mask is 255.255.255.0,

and gateway's IP address is 10.9.1.254, run the following command:
admin:/> change system management_ip eth_port_id=CTE0.A.MGMT
ip_type=ipv4_address ipv4_address=10.9.1.10 mask=255.255.255.0
gateway_ipv4=10.9.1.254

WARNING: You are going to modify the network address of network port. If you
enter an unavailable network address, the O&M interface of the storage system
is inaccessible.
Suggestion: Before you perform this operation, ensure that you have entered
an available network address.
Have you read warning message carefully?(y/n)
Enter y and press Enter.

Are you sure you really want to perform the operation?(y/n)

The IP address is successfully configured for the management port on controller A.

Step 4 See Step 3 to configure the IP address for the management interface of controller B.
Step 5 Run the show system management_ip command to check the IP addresses of management
ports on both controllers.

IPv4 Address : 10.9.1.10
Subnet Mask : 255.255.255.0
IPv4 Gateway : 10.9.1.254
IPv6 Address : --
IPv6 Gateway :
--------------------------------------
Subnet Mask : 255.255.254.0
IPv6 Address : --
IPv6 Gateway :
Step 6 Run the following command to exit the controller of the disk array.
admin:/> exit
Are you sure to exit?(y/n):y
----End

This topic describes how to commission the cold standby solution with factory installation
information. In the cold standby solution with factory installation information, the U2000 has

been installed on the servers before delivery. In this manner, you do not need to install the
NOTE
This topic applies only to the U2000 server in the cold standby solution with factory installation
information.
2.7.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 2-10 U2000 commissioning parameters

Item Parameter Planning Method Remarks
Access - As some of
the domains
Transport may not be
deployed
during
U2000
installation,
you can use
the domain
deployment
function to
deploy a
Deploy new domain
as needed so
IP that the
U2000 can
manage NEs
in this
domain.
NOTE
If some
domains are
gray, the
domains
have been
deployed.
Access - To disable
the U2000
Undeploy from
Transport managing
NEs in a

domain,
undeploy
the domain
to improve
system
operation
efficiency.
Do not
select all the
domains
because
IP
there must
be at least
one domain
deployed.
NOTE
If some
domains are
gray, the
domains
have not
been
deployed.
For details, see

section Configuring
Controller IP
Set Address in U2000
IMM IP address:
Controller Single-Server System
Software Installation
and Commissioning
Guide (SUSE Linux).
- This
commissioni
ng item is
available for
a Linux
single-
server
system
Set SSR without the
SSR License
License disk array.
The SSR
license must
be set for
full system
backup
configuratio
n.

See section Setting If disk

Hardware Alarm arrays have
Monitoring in been
U2000 Single-Server configured
System Software for the
Installation and server,
For details, see section IP Address
Commissioning hardware
Set Planning for the IP Address
Guide (SUSE Linux) alarm
Hardware Planning for a Single-Server
to perform manual configuratio
Alarm System (SUSE Linux) in U2000
configuration. Then n is
Planning Guide.
enter the IP required.
addresses of the
control card and disk
array controllers A
and B, and click
Apply.
Configure CORBA NBI Instance
Configure SNMP NBI Instance
Configure XML NBI Instance

For details, see Table
NBI Configure Performance Text NBI 2-11.
Instance
XML NBI Certificate
CORBA NBI Certificate
l If only
the time
zone
needs to
For details, see be
section Time and modified
Time Zone , restart
Planning in U2000 the
Planning Guide. operatin
g system
l Time zone: Set
Set Date after the
Time Zone: this parameter to
Time Zone modifica
the local time
tion so
zone, such as
that the
Asia/Beijing.
time is
l Time: Set this automati
parameter to the cally
local time. 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.
Time:
After the
operatin
g system
is
restarted,
the new
time is
automati
cally
adjusted
based on
the new
time
zone.
Old New After

OS root User Passwo Password security
rd: : hardening is
enabled, you
Old New cannot use
OS OSS
Passwo Password the
User
rd: : commissioni
Old New ng tool to
OS DB User Passwo Password For details, see change the
rd: : section U2000 OS user
Set Server User password.
Password DataBase Old New Password Planning For details
Administrato Passwo Password in U2000 Planning about the
r rd: : Guide. method of
changing a
password,
see section
Old New How to
DataBase
Passwo Password Change the
User
rd: : OS User
Password
in U2000

Single-
Server
System
Software
MSuite Old New
Installation
Administrato Passwo Password
and
r rd: :
Commission
ing Guide
(SUSE
Linux).
Include two
Internal Certificates:
NMS Certificate List
l Trust Certificate.
Certificate
l CRL.
Certs folder l Default

folder:default.
Set SBI l Default
Certificate path: /opt/oss/
Certs Path server/etc/ssl/
nemanager/
default.
Identity File Name:
Set U2100 Certificate PFX Password:

Certificate
Trust
File Name:
Certificate
SSL Client File Name:

Certificate PFX Password:
Set Other
Certificate File Name:
SSL Server
For details, see

section OS Security
Security Whether to enable security
Hardening
Hardening hardening
Planning in U2000
Planning Guide.
For details, see

section NTP Service
Configuring Planning in U2000 Select one
the server as NTP server IP Planning Guide. from the
Set NTP
an NTP address: three
client l If a standard parameters.
external clock
source is

Configuring available, select

the server as Configuring the
the Upper-layer NTP server as the
intermediate- server IP address: intermediate-
level NTP level NTP time
time server server and set
Upper-layer
NTP server IP
address to the
system IP address
of the standard
external clock
Configuring
source.
the server as
the highest- - l If no external
level NTP clock source is
time server available, select
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
Single-NIC
networ Address/
Scheme
k Netmask
interfa For details, see
ces section IP Address
Other
name): Planning for a
parameters
Set Network Single-Server
Networ use default
System (SUSE
k card values.
Linux) in U2000
(Logic Planning Guide.
al IP
Two-NIC
networ Address/
Scheme
k Netmask
interfa
ces
name):


NOTE
You can
select a
networking
solution
only when
Networ
the single-
k card NIC scheme
(Logic is used. If
al the two-
networ NIC scheme
k is used, you
can modify
interfa
only
ces Logical
name): network
interfaces
name, IP
Address,
and
Netmask.
For details, see

Set Host section Host Name
Host Name:
Name Planning in U2000
Planning Guide.
NIC:
IP Address:
Active NIC
Netmask:
Host Name:
Table 2-11 NBI commissioning parameters

Item Parameter Parameter Remarks
Configure Naming service host address: It is recommended -

CORBA NBI that all IP addresses
Instance Notify service host address: be the application IP
addresses used on
the U2000. If the IP
addresses to be
changed are in
Configure
Network, the
commissioning tool
automatically
changes the IP
addresses. Manual
operations are not

CORBA Agent Host Address: required. The IP

addresses for the
notification service
and CORBA agent
are the same. The
naming service may
be deployed in
centralized mode.
You must confirm
the deployment
mode with upper-
layer OSS.
This IP address is
used to interconnect
with the upper-layer
OSS. It can be
different from the
U2000 application
IP address. It must
allow the upper-
layer OSS to use the
IP address and port
number to access the
U2000.
If address translation
exists, host names
can be used.
However, if host
names are used, you
must modify the host
files on the U2000
and upper-layer OSS
server and provide
the mappings
between host names
and IP addresses.
For details, see
U2000 CORBA NBI
User Guide.

Naming Service Port: Specifies the port

used by the upper-
layer OSS to obtain
the naming service
and to use CORBA
NBIs to access the
U2000. If this port is
shielded on the
firewall between the
upper-layer OSS and
U2000, the naming
service may become
unavailable. This
port cannot conflict
with ports used by
other services on the
U2000 server.
Default value: 12001
for the non-SSL
mode and 22001 for
the SSL mode.
Notify Service Port: Specifies the port

used by CORBA
NBIs to send
notifications to the
upper-layer OSS. If
this port is shielded
on the firewall
between the upper-
layer OSS and
U2000, no
notification is
received. This port
cannot conflict with
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22002 for
the SSL mode.

CORBA Agent Port: Specifies the port

used by the CORBA
service. This port
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22003 for
the SSL mode.
Character Set: Specifies the

l UTF-8 encoding format of
the information
l GBK reported by CORBA
l ISO8859-1 NBIs. This
parameter must be
set according to the
on-site situations of
the upper-layer OSS.
If the character set
used by the upper-
layer OSS is
different from that
used by CORBA
NBIs, garbled
characters may exist
on the upper-layer
OSS.
Default value:
UTF-8.
Set Set EMS Name: Specifies the

EMS identifier used by the
Name upper-layer OSS to
distinguish different
sets of U2000. If
multiple sets of
U2000 are integrated
into the same upper-
layer OSS, this
parameter must be
set based on carriers'
NMS planning.
Default value:
Huawei/U2000.

Maximum Capacity of a Log Specifies the

File maximum size of a
log file, ranging
from 1 MB to 20
MB. Keeping the
default value is
recommended.
Default value: 20
MB.
Log l Log periodically Specifies the mode

Output l Log of generating logs.
Mode immediately Keeping the default
value is
recommended.
Default value: Log
immediately.
Log l Assertion/ Specifies the level of

Level Internal Error generating logs. This
Log parameter is used for
– Enable troubleshooting.
Keeping the default
– Disable value is
l External Error recommended.
Log l Assertion/
– Enable Internal Error
– Disable Log: Enable
l I/O Error Log l External Error
Log: Enable
– Enable
l I/O Error Log:
– Disable Enable
l Runtime Trace l Runtime Trace
Log Log: Disable.
– Enable
– Disable

NE ID NE ID l Logic Specifies the type of

Type al ID an NE ID. If the NE
l Physi ID type is incorrect,
cal the upper-layer OSS
ID fails to be parsed
correctly. Configure
this parameter after
confirming with the
upper-layer OSS.
Only transport NEs
have physical IDs.
l Physical ID: is
expressed in
dotted decimal
notation and
equals to the NE
ID x 65536 +
extended ID. For
example, if the
NE ID is 1 and
the extended ID
is 9 for NE(9-1),
the physical ID is
65545.
l Physical ID: is
expressed in
dotted decimal
notation and is
automatically
assigned by the
U2000 to NEs.
For example,
3145765.
Default value:
Logical ID.

Virtual Specifie l Enabl Specifies whether

NE s e virtual NEs are
Enablin whether l Disab enabled while
g the le querying NEs, SDH
query paths, routes, and
results fibers. If the upper-
contain layer OSS uses
virtual virtual NEs or
SDH manages devices
Nes: from other vendors,
enable this function.
Otherwise, disable
this function.
Default value:
Enable.
Enablin l All Specifies whether

g l Root CORBA NBIs are
Correla enabled with alarm
tive correlative analysis
Alarm so that correlative
alarms are reported
in alarm update
mode.
Default value: All.
Engine l Enable Specifies whether

ering l Disable CORBA NBIs report
Alarm maintenance alarms
and need to be used
along with the
U2000 engineering
task. By default, all
alarms are reported.
l Disable: specifies
that all alarms are
queried and
reported.
l Enable: specifies
that all alarms
excluding
engineering
alarms are
queried and
reported.
Default value:
Disable.

Object l Internal ID Specifies the rule for

Identifi l Object name identifying objects
er reported from
CORBA NBIs to the
U2000.
l Internal ID:
specifies that the
ID assigned by
the U2000 is the
unique identifier
of an object.
l Object name:
specifies that the
object name
displayed on the
U2000 is the
unique identifier
of an object. The
object name on
the U2000 client
must be the same
as that on the
U2000 server.
Otherwise, data
conflicts may
occur.
Default value:
Internal ID.
Alarm- l Disable Specifies whether

affecte l Enable information about
d the fibers and paths
Object affected by alarms is
Reporti reported.
ng l Enable: specifies
that the names of
the paths and
fibers affected by
alarms are
queried and
reported.
that the names of
the paths and
fibers affected by
alarms are not
reported.
Default value:
Disable.

Configure SNMP Trap Sending Specifies the IP -

SNMP NBI Agent Address/Port: address and port
Instance number used by the
U2000 to
interconnect with the
upper-layer OSS.
Ensure that SNMP
NBIs can use the IP
address and port
number to send trap
messages to the
upper-layer OSS.
Ensure that this port
is not shielded by the
upper-layer OSS and
U2000 and the port
does not conflict
with other ports used
by the services of the
upper-layer OSS.
Default value of
port: 6666.
Request Receiving Specifies the IP

Address/Port: address and port
number used by the
U2000 to
upper-layer OSS.
Ensure that upper-
layer OSS can use
the IP address and
port number to send
trap messages to the
U2000.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 9812.

SNMP Security USM SNMPv3 applies

v3 Model user-based security
Parame mechanism, and
ters USM is such a
security mechanism.
Currently, only USM
is supported.
Default value: USM.
Security l With Specifies the

Level out security level of
authe SNMPv3. After the
nticat security level is
ion configured, you
and must selected a
encry required protocol
ption and set the
l With password. The
authe security level
nticat configured must be
ion, the same as that used
witho for the
ut interconnection with
encry the upper-layer OSS.
ption Default value:
l With Without
authe authentication and
nticat encryption.
ion
and
encry
ption

Authent l HMA Specifies the

ication CMD authentication
5 protocol used for
l HMA users to access
CSH SNMP NBIs. The
A value of this
parameter must be
the same as the
authentication
protocol used for the
interconnection with
The authentication
protocol can be set
when the security
level is With
authentication,
without encryption
or With
authentication and
encryption.
Data l DES Specifies the

Encrypt l AES protocol used for
ion encrypting
communication data.
The value of this
parameter must be
the same as the data
encryption protocol
used for the
The data encryption
protocol must be set
when the security
level is With
authentication and
encryption. The
AES protocol is
recommended
because it provides
better security.

Third- Trap Destination Specifies the IP

Party Address/Port: address or port
NMS number of the upper-
layer OSS. This
parameter is used to
receive trap
messages sent by
SNMP NBIs.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 6666.
SNMP l v1 Specifies the

Version l v2c protocol version
used by SNMP
l v3 NBIs. SNMPv3 is
recommended
because it is more
secure than SNMPv1
and SNMPv2c.
Default value: v3.

Read/Write Specifies the

Community password used for
the upper-layer OSS
to access the U2000
when the SNMPv1
and SNMPv2c use
read and write
community names.
If this parameter is
set incorrectly, the
upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value of
Read Community:
Changeme_123.
Default value of
Write Community:
Changeme_123.
v3 User Name Specifies the user

name and password
used for SNMPv3–
based security
mechanism. If this
parameter is not set,
the upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value:
admin.
v3 Authentication The authentication

Password password must be
set when the security
level is set to With
authentication,
without encryption
or With
authentication and
encryption. This
parameter is used for
the upper-layer OSS
to access the U2000
using SNMP NBIs.
Default value:
Changeme_123.

v3 Privacy The communication

Password encryption password
must be set if the
security level is
With
authentication and
encryption.
Default value:
Changeme_123.
Alarm l Critic Specifies the levels

Severity al of the alarms
l Majo reported by SNMP
r NBIs.
l Mino The U2000 reports
r all alarms by default.
l Warn
ing

Alarm l Fault Specifies the types

Categor l Ackn of alarms reported
y owle by SNMP NBIs.
dged l Fault: An alarm
l Unac is generated
know when a fault
ledge occurs.
d l Acknowledged:
l Chan After an alarm is
ged confirmed,
SNMP NBIs
report an
acknowledged
alarm.
l Unacknowledged
: After an alarm
is reversely
confirmed,
SNMP NBIs
report an
unacknowledged
alarm.
l Changed: If
alarm
information is
changed, SNMP
NBIs report a
changed alarm
which contains
the alarm level
change, alarm
influence path,
and alarm root
cause identifier.
Default value: Fault
Heartb Heartbeat period Specifies the period

eat of transmitting
settings heartbeat messages.
When the U2000
MIB is used, SNMP
NBIs report
heartbeat messages
within the specified
period.
Default value: 60s

l Enabl Specifies whether to

e report heartbeat
l Disab messages. U2000
le MIB, instead of
U2000–T MIB,
supports the
reporting of
heartbeat messages.
Default value:
Enable
Alarm report field Specifies the binding

variables contained
in the alarm
information reported
by SNMP NBIs.
This parameter must
be set according to
the alarm planning
for the upper-layer
OSS. For details, see
U2000 SNMP NBI
User Guide.

Report Report l Trap Specifies the mode

settings mode l Infor of reporting trap
m messages by SNMP
NBIs. Keeping the
default value is
recommended.
l Trap: After trap
messages are
reported, the
system does not
need to report the
next trap message
until a response
is received from
the upper-layer
OSS.
l Inform: After
trap messages are
reported, the
system starts to
report the next
trap message
until a response
is received from
the upper-layer
OSS or the
number of
attempts exceeds
the threshold.
Default value: Trap
Whethe l Yes Specifies whether

r to use l No trap messages use
X.733 the event type and
level defined by X.
733.
Default value: No
Trap sending Specifies the interval

interval for sending
messages in Trap
mode.
Default value: 0
Inform delay Specifies the delay

for sending the next
packet in Inform
mode.
Default value: 5

Inform retry Specifies the number

attempts of allowed re-
connection times in
Inform mode upon a
connection failure.
Default value: 3
Report Alarm l UTC Specifies the format

time Time Time of the time used by
format Format l Local the upper-layer OSS.
Time Default value: UTC
(with Time
out
time
zone)
l Local
Time
(with
time
zone)
Encodi Alarm l UTF- Set this parameter

ng Encodin 8 based on the
Format g l GBK planning for the
Format: upper-layer OSS.
Default value:
UTF-8
Filterin l All All: specifies that all

g l Root alarms, including the
correlat root and correlative
ive alarms, are queried
alarm and reported.
Root: specifies that
only root alarms and
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All

Filterin l Enable Default value:

g l Disable Disable
enginee Disable: specifies
ring that all alarms are
alarm queried and
reported.
Enable: specifies
that all alarms
except for
engineering alarms
are queried and
reported.
MIB MIB l U200 Set this parameter

Frame 0 based on the MIB
MIB file used for the
l U200 integration of the
0-T upper-layer OSS.
MIB T2000-
NETMANAGEME
NT-MIB.mib:
U2000-T MIB HW-
IMAPV1NORTHBO
UND-TRAP-
MIB.mib or HW-
IMAPV2NORTHBO
UND-TRAP-
MIB.mib: U2000
MIB
Others Whethe l Enabl Specifies whether to

r to e record logs.
record l Disab Default value:
logs le Disable

Real-time alarm Specifies the size of

cache size the cache for real-
time alarms. Every
upper-layer OSS
user is assigned with
an independent
cache.
If the alarm
generation rate is
larger than the alarm
report rate, NBI
interfaces save alarm
information to the
cache.
Configure JMS Use SSL Specifies whether to -

XML NBI use the common or
Instance SSL mode. The
default port used
varies according to
the mode. The SSL
mode is
recommended
because it enables
better security.
Default value: Select
the Use SSL check
box.
Type activeM Specifies the

Q middleware type of
teh JMS service.
Currently, the
activeMQ
middleware is
supported.
IP Address Specifies the IP

address of the JMS
service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
use this IP address to
access the U2000.

Port Specifics the number

of the port used by
the JMS
middleware. This
parameter is usedfor
sending notifications
to the upper-layer
OSS.
Web IP Address Specifies the IP

Service address of the Web
service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
access the U2000.
HTTPS Port Specifies the number

of the port used by
XML NBIs. The
upper-layer OSS
uses this port to
obtain Web service
data from XML
NBIs.
Default value: 9997
Register JMS When the upper-

service layer OSS needs to
use AFB-based
interface (such as
getInventory), the
JMS service needs to
be registered. If only
the synchronization
mode (such as SIT
or SRR) is used, do
not register the JMS
service in order to
save system
resources.
Default value: Yes.

HTTP l Http Specifies the

Protocol l Https protocol type of the
Web service. This
parameter is set
based on the
protocol selected by
HTTPS is
recommended
because it is more
secure than HTTP.
Default value: Https
Product l Debug Specifies the level of

log l Warn the logs generated
level by XML NBIs. This
l Error parameter is used for
troubleshooting.
Default value: Warn

alarm and reported.
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All
Encoding format: Set this parameter

l UTF-8 based on the
planning for the
l GBK upper-layer OSS.
Default value:
UTF-8

Manag Domain Name: These parameters are

ement used to distinguish
domain different sets of
U2000 when they
are managed by the
same upper-layer
OSS. Set the
parameters
according to carriers'
NMS planning.
Default value:
Huawei/U2000
WDM l None When XML NBIs

route l Forward are used to query
return WDM routes, WDM
order l Backward routes are returned
based on a specified
order, which is
convenient for the
analysis of the
upper-layer OSS.
None: specifies that
WDM routes are
sent randomly.
Forward: specifies
that WDM routes are
sent from the source
to the sink.
Backward: specifies
that WDM routes are
sent from the sink to
the source.
Default value: None

Filter l Filter Out Alarm Specifies whether to

notifica Notification filter out the
tion – Enable notifications for
theme these themes.
– Disable
Default value: The
l Filter Out notification for all
Inventory these themes are
Notification filtered out.
– Enable
– Disable
l Filter Out
Protection
Notification
– Enable
– Disable
l Filter Out
Performance
Notification
– Enable
– Disable
l Filter Out
Maintenance
Notification
– Enable
– Disable

Authen l Enable After this parameter

tication l Disable is set to Enable,
Switch only users that have
related operation
rights can invoke the
XML NBI.
l Installation: By
default, this
parameter is set
to Enable.
l Version upgrade:
It is
recommended
that the value of
this parameter be
retained the same
before and after
the upgrade.
Perform
automatic
upgrades with the
NMS upgrade
tool if possible. If
the manual
upgrade mode is
used, change this
parameter
manually to keep
consistency.
Default value:
Enable
Filterin l Internal ID Specifies whether

g l Object name XML NBIs report
enginee maintenance alarms
ring and the alarm
alarm reporting works
along with U2000
engineering tasks.
By default, all
Default value:
Disable

Object l Enable Specifies the rule for

identifi l Disable identifying objects.
er l Internal ID:
specifies that the
IDs assigned by
the U2000
uniquely identify
objects.
l Object name:
specifies that the
U2000 client
names are used to
identify objects.
The U2000 client
names must be
unique in order to
prevent data
conflicts.
Default value:
Internal ID
Alarm l Enable Specifies whether to

and l Disable report the names of
service the paths or services
associa affected by the
tion alarms.
l Enable: specifies
that if an alarm
affects paths or
fibers, the names
of the affected
paths and the
fibers are
contained in the
alarm
information
during alarm
query and report.
that the names of
the affected paths
and fibers are not
reported.
Default value:
Disable

Configure Perfor l Single-period Set this parameter to -

Performance mance l Multi-period the collection period
Text NBI data for performance
Instance exporti data. The U2000 can
ng be used to export
settings performance data
generated during one
or more periods.
Duratio l Auto Specifies the delay

n l Manu mode for exporting
Settings al files. The value of
this parameter for
different device
types varies. If the
value of this
parameter is the
same for different
device types, the
performance data
fail fails to be
exported. The Auto
mode is
recommended. For
details, see U2000
Performance Text
NBI User Guide.
Default value: Auto
Collecti l 5 Specifies the period

on l 10 of collecting
Period performance data
(min) l 15 using performance
l 30 text NBIs. The
l 60 performance data
can be exported
l 1440 based on the
collection period.
Data l 5 Specifies the interval

Export l 10 for generating
Period performance text
(min) l 15 files. This parameter
l 30 can be customized. It
l 60 is recommended to
set this parameter to
l 1440 a value the same as
the collection period.

Data Export Specifies the

Duration (min) difference between
the time
performance data is
generated on NEs
and the time the
performance text file
is exported.
You must configure
Data Export
Duration (min)
according to on-site
requirements when
Duration Settings is
set to Manual. For
details, see U2000
Performance Text
NBI User Guide.
Export Start Time Specifies the time

the startup file is
exported for the first
time. This parameter
cannot be set to a
value ranging from
23:00:00 to
01:00:00. If the
value of this
parameter ranges
from 23:00:00 to
01:00:00, a data
error occurs during
DTS switching.
yyyy-mm-dd
hh:mm:ss
For example,
2009-09-01 01:00:00

Indicator Specifies the

performance
indicators that the
can export.
Performance
indicators can be
configured in two
modes: template—
based or manual
configuration
l Template-based
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
configure a
performance
indicator
template and use
the following
operations to
configure the
performance
indicators. For
details, see
U2000
Performance Text
NBI User Guide.
Full Import:
specifies that
performance
indicators are
fully imported to
the performance
indicator
template to
overwrite the
original indicator
template.
Incremental
Import: specifies
that performance
indicators are
incrementally
imported to the
performance

indicator
template and only
new indicators
are added to the
original indicator
template. Export:
The performance
indicator
template is
exported, backed
up, or provided to
another U2000
server.
l Manual
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
print the
performance
data. Modify: In
the dialog box
that is displayed,
configure the
indicators as
required.
File □Export Exportin Set this parameter to

exporti ing to g the directory where
ng the directory the performance data
settings local file is saved. The
server upper-layer OSS
accesses this
directory to obtain
performance data.

□Export l FTP The U2000 uploads

ing to a Mode performance data to
remote : the FTP server. You
FTP –F must create an FTP
server T user and configure
P the FTP user
password on the
–S U2000.
F
T Using SFTP is
P recommended
because SFTP
l FTP/ provides higher
SFTP security than FTP.
Serve
r IP:
l FTP/
SFTP
Port:
l FTP/
SFTP
User:
l FTP/
SFTP
Pass
word:
l FTP/
SFTP
Direc
tory:
l SFTP
Certif
icate:
Log Maximum number Specifies the

file of backup product maximum number of
settings logs output logs.
Default value: 20
Maximum size of Specifies the

product logs maximum size of
output logs.
Default value: 20

Product l Debu Specifies the lowest

log g level of generating
level l Info logs. The logs with
the level lower than
l Warn the value cannot be
l Error recorded.
Default value: Info

planning for the
Default value:
UTF-8
Time Specifies the time

format format encoding for
for file the performance text
export NBI file.
Default value: UTC
time
Others Maximum number Specifies the

of records in a file maximum number of
records in a file.
If the value exceeds
the threshold, the
extra records are
stored in another file
whose serial number
is increased by 1.
Default value:
100000
Number of days to Specifies the period

save exported files during which files
can be stored on the
local server. The
system automatically
deletes the files
generated after the
period elapses.
Default value: 3
days

Start time for file Specifies the start

deletion time for deleting
files in a scheduled
task. The value of
this parameter is the
same as the server
time.
Format: yyyy-mm—
dd hh:mm:ss
XML NBI Identity Certificate Type Default certificate -

Certificate Certific Type: P12.
ate File Name
For details, see
section Security
Trust File Name
Certificate
Certific
Description.
ate
CRL File Name
CORBA NBI Identity Certificate Type Default certificate -

ate For details, see
section SSL
Principle and
Configuration.
2.7.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
NOTICE
l Manually changing the system IP address causes a failure to use the commissioning tool.
Therefore, configure the system IP address through the commissioning tool.
l All network information will be cleared when you adjust the networking by using the Set
Network commissioning item of the Commissioning Tool. If southbound and northbound
IP addresses are configured independently on the customer's network, reconfigure them
after the networking is adjusted.
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 2.7.1 Obtaining Commissioning Parameters.
l The server has been powered on.
Context
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 192.168.128.110 and the subnet mask
as255.255.255.0.
Step 3 On the PC or laptop, use the remote GUI login software, such as VNC, to log in to the SUSE
Linux OS GUI as the ossuser user. For details, see Configure the VNC service as the
ossuser user.
NOTE
The default password of the ossuser user is Changeme_123. The default password is not changed
during preinstallation.
Step 4 Right-click the blank area of the desktop and choose Open in Terminal from the shortcut
menu to open the CLI.
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
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
The U2000 is running if the displayed information contains imapmrb, imapwatchdog -cmd start,
imapsysd -cmd start, imapeventmgr, imap_sysmonitor -cmd start, ResourceMonitor -cmd start.
The process is stopped if the displayed information is empty.
If the U2000 is still running, run the following commands to stop it:

$ cd /opt/oss/server/platform/bin
$ ./stopnms.sh
Step 6 Ensure that the database is running.

Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase

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
install/RUN_DBSVR_back
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 start the Sybase database if it is not running:
$ su - dbuser
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/ASE*/install
$ ./startserver -f ./RUN_DBSVR &
$ ./startserver -f ./RUN_DBSVR_back &
$ exit
NOTE
l Enter the dbuser user password as prompted. The default password is Changeme_123. For system
security, modify the default password and remember the new password. For details, see A.1.1 How
to Change the OS User Password.
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l DBSVR is the name of the database server and DBSVR_back is the name of the database backup
server. These names must be consistent with the actual database names.
l View the database name and database backup server name by running the more /opt/sybase/
interfaces command.
Step 7 Ensure that the MSuite servers on the primary and secondary sites have 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 7593 7130 0 06:31 pts/7 00:00:00 grep java
ossuser 8937 12803 0 04:13 pts/8 00:00:42 /opt/oss/OSSJRE/jre_linux/bin/
java -Dprocname=AgentIntegrate -Dfile.encoding=UTF8 -Xmx1024m -
XX:MetaspaceSize=16m -XX:MaxMetaspaceSize=256m -XX:+UseCompressedClassPointers -
XX:+UseCompressedOops -XX:CompressedClassSpaceSize=128m -XX:
+HeapDumpOnOutOfMemoryError -DabsCfgPath=/opt/oss/server/etc/oss_cfg/frame -cp
nbi/agentintegrate/thirdparty/*:3rdlib/*:common/uflightdispatcher/lib/
jdom.jar:cbb/qasn/lib/*:common/uflight/frame_app/plugins/
com.huawei.uflight.platformadapter/*:common/uflight/web_app/plugins/pax-web-

runtime-2.1.2.jar:common/uflight/web_app/plugins/web_app/plugins/pax-web-
spi-2.1.2.jar:nbi/agentintegrate/lib/*:nbi/agentintegrate/bin/*
com.huawei.u2000.inventory.webserver.JettyStarter
...
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, switch to the ossuser and run the following
commands as the root user to start the MSuite servers:
# su - ossuser
$ cd /opt/oss/engr/engineering
$ ./startserver.sh
Step 8 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.
– IP Address: Use the default value 127.0.0.1.
– Port: Use the default value 12212.
– User Name: Use the default value admin.
– Password: The initial password of the admin user is Changeme_123. 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
– 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.
– The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the
MSuite at one time.
Step 9 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 10 Configure the commissioning items based on the planned commissioning parameter table. For
details about the commissioning parameters, see 2.7.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 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.1.1
How to Change the OS User Password.
Step 11 Click Finish on the Finsh window, the Commissioning finished successfully, please use
UEasy tool to perform routine inspection. information is displayed. Click OK and perform
routine inspection if needed.
Step 12 After system parameters are commissioned, run the following commands to restart the OS as
the root user to make the modification take effect:
# sync;sync;sync;sync
# shutdown -r now
Step 13 Disconnect the PC or laptop from the U2000 server and then see 4.4 Checking Hardware
Connections to connect the U2000 server to the network.
----End
Follow-up Procedure
l If the server IP address is changed during commissioning, you must manually configure
the hardware alarm monitoring function. For details about the replacement procedure,
see C.3.1 Configuring the Monitoring Function for an OceanStor 5500 V3 Disk
Array and C.3.2 Configuring the Monitoring Function for an S3900 Disk Array.
l If NTP is configured during commissioning, check whether NTP service configurations
are correct. For details, see A.1.26 Checking the NTP Service on Linux.
l If you want to stop the NTP, see A.5.19 Starting or Stopping the NTP Service on
SUSE Linux.
2.7.3 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 client is installed by referring to iManager U2000 version Client Software
Installation Guide.
l The U2000 license file must be ready.

NOTICE
The license file name can contain digits, letters, and special characters excluding the
space or \ /:*?"<>|.
Context
l During installation of the U2000 software, the OS user ossuser is created automatically.
The ossuser user is used to regularly maintain a U2000.
l Two methods are available for loading a U2000 license.
– 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.
– Method two:
Load the license in the GUI. This method is applicable to users who are not familiar
with common commands of the SUSE Linux OS.
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 In the SUSE Linux OS, See How to Fix Garbled Characters in the SUSE Linux Command
Output to fix garbled characters if the SUSE Linux command output displays garbled characters.
You can select a method as required. No matter which method is selected, ensure that the U2000 server
process has been started.
Procedure
Step 1 Log in to the OS as the ossuser user.
NOTE
The initial password of the ossuser user is Changeme_123. For details about For system security,
modify the default password and remember the new password., see A.1.1 How to Change the OS User
Password.


install/RUN_DBSVR


...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.
Step 3 Ensure that the U2000 is running.

Run the following command to check whether the U2000 is running:
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
imapsysd -cmd start, imapeventmgr, imap_sysmonitor -cmd start, ResourceMonitor -cmd start. If
no introduction is displayed, the U2000 processes have been stopped.
To start the U2000 if it is not running, run the following commands:

$ ./startnms.sh
Step 4 Run the following commands to check whether a license file exists. If a license file exists,
back it up. If the license file does not exist, skip this step.
$ 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
$ cp license_file_name /opt/oss/server/etc/conf/license_backup
NOTE
If the name of the license file contains a space, add quotation marks for license_file_name in the above
command.

Step 5 The encoding format of the U2000 license file must be UNIX, not DOS. For details about
how to confirm the encoding format of the U2000 license file, see A.5.11 How to Confirm
the Encoding Format of the U2000 License File.
Step 6 Do as follows to load the U2000 license:

NOTE
To make both the U2000 commercial and temporary licenses take effect, use the GUI mode.
Method one: Use commands to load the license.
1. Use SFTP to upload the license file to the /export/home/ossuser directory on the server
as the ossuser user. For details, see A.1.27 How to Use the FileZilla to Transfer Files
by SFTP.
NOTE
If the license file uploaded by the root user is used, the ossuser user may not have the read
permission and therefore the license fails to be updated. Use the license uploaded by the ossuser
user. If security hardening is performed on the OS, FTP/SFTP rights of ossuser will be disabled.
In this case, you need to upload files to the backup directory in the FTP root directory as the
ftpuser user (the FTP root directory of ftpuser is /opt/backup/ftpboot).
2. To activate the license file, run the following commands:
a. Log in to the OS of the server as the ossuser user.
b. Run the following commands to update the U2000 license file:
$ cd /export/home/ossuser
$ updateLicense -file License_file_name.dat

state product feature item name
old value new value
no change: U2000 COMMON LSW1CAPA01 Client
500 500
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 press Enter.
Method two: Load the license in the GUI.
1. Save the license to be loaded to the server where the U2000 client is located.
2. Log in to the OS as a user with the administrator rights where the client program is
installed.
3. On the OS desktop, double-click the U2000 Client shortcut icon. The Login dialog box
is displayed.
4. 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. The password must be changed during the first login to ensure
system security. Keep the password confidential and change it regularly.
– If a message indicating that no license is available is displayed when you log in to
the U2000 client.
i. In the Confirm dialog box, click Yes. The Open dialog box will be displayed.

ii. 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.
iii. Click OK.
iv. Click Yes and confirm the loaded license.
v. Click OK.
– If U2000 license is loaded before.
i. 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).
ii. In the License Information dialog box, click Update License.
iii. Select the new license file and click Open.
iv. Click Next.
v. Select a scenario and perform the associated operations as required:
○ If Incremental is unavailable, click Next.
○ If Incremental is available and only the new U2000 license needs to be
effective, select Full and click Next.
○ 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.
vi. Click Finish.
vii. Click Yes and confirm the updated license.
viii. Click Yes to close all windows.
ix. Click Yes to log out of the system.
----End
Result
After the preceding operations are performed, the license file is automatically loaded to
the /opt/oss/server/etc/conf/license path.
2.7.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 2.7.2 Configuring System Commissioning Parameters.
l Ensure that the U2000 license has been loaded. For details, see 2.7.3 Loading a U2000
License.

NOTE
The recommended resolution range is 1024 * 768 to 1920 * 1080.
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 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 in 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
NOTE
Step 4 If the U2000 process is not started, run the following commands to start it:
$ ./startnms.sh
Step 5 Log in to U2000 client.

1. Log in to the Windows OS as a user with the administrator rights where the client
program is installed.
is displayed.
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.
2.7.5 Checking the Installation of the U2000

This topic describes how to check the installation of the U2000. Ensure that the U2000 was
properly installed before using it to manage a network.
Context
l During installation of the U2000 software, only one default NMS user, that is, user
admin, is provided. The admin user is the administrator of the U2000 and has the
highest rights of the U2000.
Procedure
Step 1 Log in to the server OS as user ossuser.
NOTE
Password.
Step 2 Check the shortcut icons.
NOTICE
A U2000 client does not support the Linux OS. Manually starting a U2000 client and running
a script on the Linux OS may bring risks. Therefore, exercise caution when performing these
operations.
The following shortcut icons are displayed on the desktop:
l U2000 NMS Maintenance Suite

l U2000 Server
Step 3 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 /etc/ICMR
l /var/ICMR
Step 4 To check the U2000 version, run the following commands:
$ cd /opt/oss/engr/install/etc/conf
$ cat MacroFileNW.properties
A message similar to the following will be displayed:

...
@{U2000Product_Server_VersionName}=V200R016C60SPCxxx
...
The preceding displayed information shows the U2000 version. If the version information
does not meet the actual requirement, uninstall the U2000 and install the U2000 again.

install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb

NOTE

$ ./startnms.sh
Step 7 Log in to the U2000 client.

installed.
NOTE
Use the CAU mode to install a U2000 client in Windows for convenient installation. In the address
bar, enter https://server's IP address/cau/ (recommended for higher security) or http://server's IP
address/cau/ to install a U2000 client. For details about the method of installing a U2000 client,
see U2000 Client Software Installation Guide.
is displayed.
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 for the U2000 server in a SUSE Linux
single-server system, see A.5.10 How to Set the Communication Mode on the U2000 server for
the Single-Server System (SUSE Linux).
----End
Follow-up Procedure
l To save the server disk space, run the following command to delete /opt/install
directory.
$ su - root
Password: root user password
# rm -r /opt/install
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 login to a U2000 client fails, see A.6.4 Failure to Log In to the U2000 Server from a
U2000 Client to resolve the problem.
l The installation is not complete if any of the preceding checks are not passed. For
details, see A.6.8 How to Address the U2000 Installation or Uninstallation Failure.
2.8 Configuring the Cold Standby Solution

Guide.
2.8.1 Configuring Automatic Backup Tasks on the Primary Site

This topic describes how to create a scheduled backup task on the primary site. After a
scheduled backup task is created, the data of the primary site can be automatically backed up.
Prerequisites
l A single server U2000 system whose version, deployment domain, language, OS type,
server time, and time zone are the same as those on the primary site is installed on the
secondary site.
l The U2000 processes and the database are running on the primary site.
l Network communication between the primary site and the secondary site is normal, and
the minimum bandwidth is 10 Mbit/s.
l The SFTP Server service has been activated on the primary site, and related ports
(including the SFTP service port 22) have been enabled.
NOTE
For details on enabling the SFTP Server service on a SUSE Linux operating system, see A.1.2
How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS.
l If a firewall is deployed between the primary site and the secondary site, the SFTP
service port (by default, port 22) on the firewall must be enabled. For details on enabling
the SFTP service port on a firewall, see the firewall user guide.
l Only one scheduled backup or restoration task is allowed on a single server. For
example, if you create a new automatic backup task on the primary site, the old backup
task on the primary site will become invalid and only the new one will be retained.
Context
In upgrade, reconstruction, and data migration scenarios, you may need to back up or restore
U2000 data manually. For details, see the Manually Execute Backup and Restoration
Tasks section of the U2000 Administrator Guide.

Procedure
Step 1 Run the following steps to execute the configuration script.
NOTE
If execution of the configuration script fails, apply troubleshooting as prompted or contact Huawei
technical support engineers.
1. Log in to the OS as the ossuser user through SSH by using PuTTY.

2. Run the following command to switch to the root user and run the userconfig.sh script.
$ su - root
Password: Password of the root user
# cd /opt/oss/engr/tools/coldbackuptool
# ./userconfig.sh

Select a task type (1: backup, 2: restoration):
NOTE
The preceding directory is true only if the U2000 is installed in /opt/oss. If the U2000 is not
installed in partition /opt, change the partition in the directory accordingly.
Step 2 Enter a node for backup, such as 1 and press Enter.

Set the interval of the scheduled task (1: daily, 2: weekly, 3: monthly)|1:
Step 3 Enter the backup interval, such as 1 and press Enter.

Set execution time (0-23)|1:
NOTE
The time configured for the cold backup task does not overlap with the time when data is being restored
using the MSuite. Cold backup may fail if the MSuite is restoring data.
Step 4 Enter the backup frequency, for example, if the frequency is 2:00 every day, enter 2 and press
Enter.

Set the maximum number of backup files|30:
NOTE
l The maximum number of backup files must match the size of disk that will hold the backup files,
and is recommended to be 30.
l It is recommended that you set the scheduled backup time to the time when network service traffic is
light, such as at midnight (00:00 to 06:00).
Step 5 Enter the maximum number of backup files, such as 30, and press Enter.
The scheduled task is successfully created if the following information is displayed.
Scheduled task created successfully.
NOTE
After the maximum number of backup files is configured, check it as follows:

Navigate to the path /opt/oss/engr/tools/coldbackuptool/conf, and run the cat mark.inf command to
view content in the mark.inf file. Information similar to maxbackupfiles=30 will be displayed.
----End

Result
After a backup task is created on the primary site, use one of the following methods to verify
whether the configuration of backup task is successful:
l Using query commands
– Check the backup task.
i. Log in to the OS as the ossuser user through SSH by using PuTTY.
ii. Run the following command to switch to the root user and run the
coldbackupInfo.sh script.
$ su - root
# ./coldbackupInfo.sh -task

cycle time Command Line
daily 0:00 su - ossuser -c "cd /opt/oss/engr/tools/
coldbackuptool; ./coldbackup.sh -silent " > /dev/null 2>&1
NOTE
The displayed value of cycle varies depending on the backup interval. For example:
l If the configured backup interval is daily, the displayed value of Day is similar to
daily.
l If the configured backup interval is weekly, the displayed value of Day is similar
to weekly: Sunday.
l If the configured backup interval is monthly, the displayed value of Day is similar
to monthly: 22.
– Check the backup result.
$ su - root
# ./coldbackupInfo.sh -result

2015-07-28 21:20:29;Successful;backupDB;20150728211943.7z
NOTE
The fields in the command output indicate the backup date and time, operation result
(Successful/Failure), operation type (backupDB/restoreDB), and backup package (the
timestamp in the file name indicates the backup time).
NOTE
The directory /opt/oss/engr/tools/coldbackuptool in the preceding command assumes that the
U2000 is installed in the default directory /opt/oss. If the U2000 is not installed in the default
directory, replace the directory in the command accordingly.
l Check the log.
When the scheduled time of the backup task is reached, run tail -f /opt/oss/engr/tools/
coldbackuptool/silent/coldbackupresult.txt to check the backup log.
l Check the backup files.
The backup directory is /opt/backup/ftpboot/coldbackupdata and the backup files are
in the 7z format.

Follow-up Procedure
For how to end the backup task, run the following steps.
2. Run the following commands to switch to the root user and end the backup task on the
secondary site:
$ su - root
# ./stopCron.sh
2.8.2 Configuring Automatic Restoration on the Secondary Site

This topic describes how to create a scheduled restoration task on the secondary site. After the
scheduled restoration task is created, the U2000 data can be automatically restored on the
secondary site.
Prerequisites
secondary site. For details about the installation procedure, see the U2000 Single-Server
System Software Installation and Commissioning Guide.
l On the secondary site, network management process and the maintenance tool are
standby and the database is running. If the U2000 has started when the restoration task is
performed, the U2000 process is automatically stopped.
l The primary site is running correctly. (If the primary site becomes faulty before
automatic restoration starts, data cannot be restored on the secondary site.)
Context
Procedure
Step 1 Run the configuration script on the secondary site.
NOTE

$ su - root
# ./userconfig.sh


NOTE
Step 2 Enter a node for restoration, such as 2 and press Enter.

Set the interval of the scheduled task(1:daily,2:weekly,3:monthly)|1:
Step 3 Enter the automatic restoration interval, for example, if the automatic restoration task is
performed once every day, enter 1 and press Enter.
Step 4 Enter the time to start the automatic restoration task, such as 5 and press Enter.
>>>>>Enter the peer SFTP user<<<<<
Enter the peer SFTP IP address:
Enter the password for SFTP user:
NOTE
l The interval between the automatic restoration time and the automatic backup time is fixed at 3
hours. For example, if the automatic backup time is 2 a.m., set the automatic restoration time to 5
a.m.
l If connection to the primary site fails due to Primary Site Authentication Error when you enter
the primary site's SFTP information, see How Do I Handle the Failure to Connect Two Servers Due
to a Mutual Trust Authentication Error? for troubleshooting.
l Reconfigure the automatic restoration task if the SFTP user's password is changed.
Step 5 Enter the IP address and SFTP user name of the primary site, and press Enter. In this
example, IP address is 192.168.0.0 and default password of the SFTP user is
Changeme_123. The information is used by the secondary site to obtain the backup file from
the primary site by using the SFTP.
Scheduled restoration will automatically shut down the U2000 and MSuite.
----End
Result
After an automatic restore task is created on the secondary site, use one of the following
methods to verify whether the configuration of restore task is successful:
– Check the restoration task.
$ su - root


coldbackuptool; ./coldrestore.sh -silent " > /dev/null 2>&1
NOTE
The displayed value of cycle varies depending on the restoration interval. For example:
l If the configured restoration interval is daily, the displayed value of Day is similar
to daily.
l If the configured restoration interval is weekly, the displayed value of Day is
similar to weekly: Sunday.
l If the configured restoration interval is monthly, the displayed value of Day is
similar to monthly: 22.
– Check the restoration result.
$ su - root

2015-07-28 21:48:56;Successful;restoreDB;20150728211943.7z
NOTE
The fields in the command output indicate the restoration date and time, operation
result (Successful/Failure), operation type (backupDB/restoreDB), and backup
package (the timestamp in the file name indicates the backup time of the data to be
restored).
NOTE
l Checking the log
coldbackuptool/silent/coldrestoreresult.txt to check the restore log.
Follow-up Procedure
l For how to end the restoration task, run the following steps.
a. Log in to the OS as the ossuser user through SSH by using PuTTY.
b. Run the following commands to switch to the root user and end the restoration task
on the secondary site:
$ su - root
# ./stopCron.sh
l After automatic restoration is implemented for the first time, stop the U2000 process on
the primary site and start the U2000 process on the secondary site to ensure that the
process can function properly.
– If the U2000 process runs properly on the secondary site, stop the U2000 process on
the secondary sites start the U2000 process on the primary site.
– If the U2000 process not runs properly on the secondary site, re-execute the restore
task on the secondary sites or contact Huawei technical support personnel.

NOTE
After data restoration fails, if the missing database files fault is found in the log file, rectify the
fault by following the instructions provided in How to Rectify the Data Restoration Failure on a
Secondary Site Because of Missing Databases.
NOTE
l If the CORBA NBI, XML NBI, SNMP NBI, or text NBI is configured for the U2000, you must
reconfigure the IP address used by the NBI to interconnect with the upper-layer OSS after
successfully restoring the database. For details, see the related NBI user manual.
l After the preceding operations are complete, login passwords for the U2000 client and NE Software
Management are restored to be consistent with the U2000 data.

and Commissioning Guide (SUSE Linux) Installation of the Single-Server System)

(Factory Installation of the Single-Server
System)
About This Chapter
This topic describes how to collect information required for commissioning the Single-Server
System (SUSE Linux) with factory installation information and how to commission the
Single-Server System (SUSE Linux).
This topic briefly describes the single-server solution with factory installation information.
This topic describes the commissioning process and required time of the Single-Server
System (SUSE Linux) with factory installation installation.
3.3 Commissioning Preparation
This topic describes the preparations to be made before the Single-Server System (SUSE
Linux) with factory installation information is commissioned, including collecting
commissioning information, checking mandatory software, and applying for the U2000 and
SSR licenses.
This topic describes how to commission the single-server system with factory installation
information. In the single-server solution with factory installation information, the U2000 has
been installed on the server before delivery. In this manner, you do not need to install the


This topic briefly describes the single-server solution with factory installation information.
In the single-server solution with factory installation information, the U2000 has been
installed on the server before delivery. In this manner, you do not need to install the U2000
again but commission it directly. Specifically, you can use the U2000 normally only after
changing system and U2000 parameters to meet site requirements.

This topic describes the commissioning process and required time of the Single-Server
System (SUSE Linux) with factory installation installation.
NOTE
SUSE Linux OS.
is performed.

Figure 3-1 Single-Server System (SUSE Linux) commissioning process
3.3 Commissioning Preparation

This topic describes the preparations to be made before the Single-Server System (SUSE
Linux) with factory installation information is commissioned, including collecting
commissioning information, checking mandatory software, and applying for the U2000 and
SSR licenses.
3.3.1 Collecting Commissioning Information

This topic describes how to collect commissioning information. Before commissioning the
single-server system with factory installation information, collect required information,
including the host name, IP address, route, time zone and time, user password, installation
path, component quantity, and instance quantity.
Planning Guide. Collect and record the commissioning information in the tables.

NOTE
Host Name Planning
NOTICE
Item Example Plan
Server NMSserver
IP Address Planning

NMS server and NEs.
l The iMana IP address and system IP address can be located either on the same network
segment or on different network segments.
normal state.
state.
NOTE
l Single-NIC Scheme

Item Example (IP Address/ Description
iMana IP 10.9.1.20/255.255.255.0/10.9.1. The iMana IP address and system IP

address 254 address can be located either on the
same network segment or on
System IP 10.9.1.2/255.255.255.0/10.9.1.2 different network segments.
address 54
IP address l Primary controller: -

for the disk 10.9.1.10/255.255.255.0/10.
array 9.1.254
controller l Secondary controller:
10.9.1.11/255.255.255.0/10.
9.1.254
l Double-NIC Scheme


NOTE

iMana IP 10.9.1.20/255.255.255.0/10.9.1. l The iMana IP address and system

address 254 IP address can be located either
on the same network segment or
System IP 10.9.1.2/255.255.255.0/10.9.1.2 on different network segments.
address 54
configured with bond. If eth0 and
eth2 interfaces are selected
during system reconfiguration to
configure bond, the system IP
address corresponds to both the

for the disk 10.9.1.10/255.255.255.0/10.
array 9.1.254
10.9.1.11/255.255.255.0/10.
9.1.254
Route Planning

Item Example Plan
Routing network 10.9.10.0/255.255.255.0

segment 1
Routing network 10.71.6.0/255.255.255.0

segment 2
... ...

Item Example Plan
Routing network 10.121.124.0/255.255.255.0

segment N
NOTE
network.

Item Example Plan
Time 14:00

IP address
NOTICE

Preinstallation

root


Preinstallation

NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ossuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ftpuser NOTE
modify the default
password and
remember the new
see A.5.29 How to
Change the Password

dbuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

user dbuser NOTE
store U2000 Guard
modify a database
password, seeA.5.24
How Do I Change an
H2 Database User's
Password for the
U2000 Guard.


Preinstallation

webuser NOTE
l An independent
account used to run
Tomcat and Apache
services.
modify the default
password and
remember the new
password. For
details, see A.1.1
How to Change
the OS User
Password.

5500 V3 user
admin
Kaimse l authenticate l authenticate

NOTE password: password:
Account for ism@Storage ism@Storage
Trap
l private password: l private password:
authenticating
the device ism@Storage ism@Storage
alarms
reported by an
5500 V3 disk
array. The
account
cannot be used
for login.

sa


Preinstallation

user ossuser NOTE
The H2 database is
data of NBI
H2 database is
need to change the
How Can I Change
the Password of the
H2 Database .
H2 database file is
need to change the
How Can I Change
the Password of the
H2 Database File.

database NOTE
after the U2000 is
may be manually
with a customized
administrator name,
such as dbadmin.

Database user NOTE
not have a default
password. The
during U2000
installation.

admin NOTE
You must change the
first-time login.


Preinstallation

Management NOTE
admin

Table 3-8 Tool list

o
.

server.
Using SSH
(more
secure,
recommend
ed) to log
in to the
server is
recommend
ed.
SFTP.


Context
support engineers.
Procedure
NOTE

# cd /opt
# ./esn

ESN0:****************************************
ESN1:****************************************

ESN2:****************************************
ESN3:****************************************
...
# ./esn

ESN0:****************************************
ESN1:****************************************
ESN2:****************************************
ESN3:****************************************
...
office.
NOTE
and ESNs.
NOTE
----End

Prerequisites
NOTE
Procedure

License.
NOTE
----End

Prerequisites
Procedure
NOTE


NOTE
number of 1 can be used for the Huawei RH5885H V3, Huawei RH2288H V3 and Huawei RH2288H
V2 servers.
NOTE

NOTE

NOTE
NOTE

----End
Follow-up Procedure


Server
1. Power on a Huawei RH2288H V2/Huawei RH2288H V3/Huawei RH5885H V3 server.
NOTICE
NOTE
RH2288H V2, Huawei RH5885H V3, IBM X3650 M4, IBM X3650 M3 and, IBM
X3850 X5.
Figure 3-7 Position of the power button on RH2288H V3 server

Disk Array
NOTICE
it on.

For OceanStor 5500 V3:
l Normal power-on sequence: 1. Turn on the power switches of the external power
supplies connected to all the devices. 2. Press the power button on either controller. 3.
Turn on the LAN switch or FC switch (if any LAN switch or FC switch is deployed but
is not powered on). 4. Turn on the application server (if the application server is not
powered on).
l Normal power-down sequence: 1. Stop the services of the application server. 2. Hold the
power button for 5 seconds on the controller enclosure. 3. Disconnect the controller
enclosure and disk enclosures from the external power supplies.
NOTE
Power supply must be provided for the two power modules of the OceanStor 5500 V3; otherwise, the
OceanStor 5500 V3 fails to be used. Press the power button on controller A/B. Wait 5 to 10 minutes
until the power indicator is steady green and no longer flashing, indicating the power-on success.
steady green.
indicators are off.




mode of using BIOS.
l Through BIOS:
NOTE

Prerequisites


used.
NOTE
Context
in again.
Procedure

NOTE
NOTE
NOTE



NOTE
is displayed.
----End

Prerequisites
NOTE
Context

in again.
Procedure
RH5885H V3 server.
following figure.

NOTE
NOTE

NOTE

NOTE
is displayed.

----End

Prerequisites
of the server.
Procedure
started.
NOTE

operations:
operations:
operations:
operations:
displayed.

box is displayed.
configuration page.
----End
3.6.2 Setting the SC IP Address for the OceanStor 5500 V3 Disk

Array
Prerequisites
serial port:
NOTE
menu.
Context


10.9.1.11.
Procedure

navigation tree.
– Data bits: 8
– Stop bits: 1
– Parity: None

5. Click Open.
Storage login:

NOTE



System Name : xxxx

SN : xxxx
Location :


IPv4 Address : 192.168.128.101
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Gateway :
--------------------------------------
IPv4 Address : 192.168.128.102
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Gateway :

descriptions.

subnet mask.
gateway.



is inaccessible.




Subnet Mask : 255.255.255.0
IPv6 Address : --
IPv6 Gateway :
--------------------------------------
Subnet Mask : 255.255.254.0
IPv6 Address : --
IPv6 Gateway :
admin:/> exit
----End

This topic describes how to commission the single-server system with factory installation
information. In the single-server solution with factory installation information, the U2000 has

been installed on the server before delivery. In this manner, you do not need to install the
NOTE
This topic applies only to the U2000 server in the single-server solution with factory installation
information.


Access - As some of
the domains
Transport may not be
deployed
during
U2000
installation,
you can use
the domain
deployment
function to
deploy a
Deploy new domain
as needed so
IP that the
U2000 can
manage NEs
in this
domain.
NOTE
If some
domains are
gray, the
domains
have been
deployed.
Access - To disable
the U2000
Undeploy from
Transport managing
NEs in a

domain,
undeploy
the domain
to improve
system
operation
efficiency.
Do not
select all the
domains
because
IP
there must
be at least
one domain
deployed.
NOTE
If some
domains are
gray, the
domains
have not
been
deployed.
For details, see

section Configuring
Controller IP
IMM IP address:
and Commissioning
Guide (SUSE Linux).
- This
commissioni
ng item is
available for
a Linux
single-
server
system
Set SSR without the
SSR License
License disk array.
The SSR
license must
be set for
full system
backup
configuratio
n.


Monitoring in been
Planning Guide.
addresses of the
array controllers A
and B, and click
Apply.
Configure XML NBI Instance

NBI Configure Performance Text NBI 3-11.
Instance
XML NBI Certificate
l If only
the time
zone
needs to
For details, see be
section Time and modified
Time Zone , restart
Planning in U2000 the
Planning Guide. operatin
g system
l Time zone: Set
Set Date after the
Time Zone modifica
the local time
tion so
zone, such as
that the
Asia/Beijing.
time is
l Time: Set this automati
parameter to the cally
local time. 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.
Time:
After the
operatin
g system
is
restarted,
the new
time is
automati
cally
adjusted
based on
the new
time
zone.
Old New After

rd: : hardening is
enabled, you
Old New cannot use
OS OSS
Passwo Password the
User
rd: : commissioni
Old New ng tool to
OS DB User Passwo Password For details, see change the
rd: : section U2000 OS user
Set Server User password.
Password DataBase Old New Password Planning For details
Administrato Passwo Password in U2000 Planning about the
r rd: : Guide. method of
changing a
password,
see section
Old New How to
DataBase
Passwo Password Change the
User
rd: : OS User
Password
in U2000

Single-
Server
System
Software
MSuite Old New
Installation
Administrato Passwo Password
and
r rd: :
Commission
ing Guide
(SUSE
Linux).
Include two
Certificate
l CRL.

folder:default.
Set SBI l Default
nemanager/
default.
Identity File Name:

Certificate
Trust
File Name:
Certificate

Set Other
SSL Server
For details, see

section OS Security
Hardening
Hardening hardening
Planning in U2000
Planning Guide.
For details, see

section NTP Service
Configuring Planning in U2000 Select one
the server as NTP server IP Planning Guide. from the
Set NTP
an NTP address: three
client l If a standard parameters.
external clock
source is

Configuring available, select

the server as Configuring the
the Upper-layer NTP server as the
intermediate- server IP address: intermediate-
level NTP level NTP time
time server server and set
Upper-layer
NTP server IP
address to the
system IP address
of the standard
external clock
Configuring
source.
the server as
the highest- - l If no external
level NTP clock source is
time server available, select
Configuring the
server as the
highest-level
NTP time
server.
Route network segment 1

For details, see
Set Route
Planning Guide.
Route network segment N
Networ
k card
(Logic
al IP
Single-NIC
networ Address/
Scheme
k Netmask
interfa For details, see
ces section IP Address
Other
name): Planning for a
parameters
Set Network Single-Server
Networ use default
System (SUSE
k card values.
Linux) in U2000
(Logic Planning Guide.
al IP
Two-NIC
networ Address/
Scheme
k Netmask
interfa
ces
name):


NOTE
You can
select a
networking
solution
only when
Networ
the single-
k card NIC scheme
(Logic is used. If
al the two-
networ NIC scheme
k is used, you
can modify
interfa
only
ces Logical
name): network
interfaces
name, IP
Address,
and
Netmask.
For details, see

Host Name:
Planning Guide.
NIC:
IP Address:
Active NIC
Netmask:
Host Name:


addresses used on
addresses to be
changed are in
Configure
Network, the
commissioning tool
automatically
changes the IP
addresses. Manual
operations are not

CORBA Agent Host Address: required. The IP

addresses for the
and CORBA agent
are the same. The
naming service may
be deployed in
centralized mode.
You must confirm
the deployment
mode with upper-
layer OSS.
This IP address is
OSS. It can be
different from the
U2000 application
IP address. It must
allow the upper-
IP address and port
U2000.
exists, host names
can be used.
However, if host
names are used, you
files on the U2000
and upper-layer OSS
server and provide
the mappings
between host names
and IP addresses.
For details, see
U2000 CORBA NBI
User Guide.


used by the upper-
layer OSS to obtain
the naming service
and to use CORBA
NBIs to access the
shielded on the
upper-layer OSS and
U2000, the naming
service may become
unavailable. This
with ports used by
U2000 server.
for the non-SSL
mode and 22001 for
the SSL mode.

used by CORBA
NBIs to send
upper-layer OSS. If
on the firewall
between the upper-
layer OSS and
U2000, no
notification is
received. This port
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22002 for
the SSL mode.


used by the CORBA
service. This port
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22003 for
the SSL mode.

the information
parameter must be
used by the upper-
layer OSS is
different from that
used by CORBA
NBIs, garbled
on the upper-layer
OSS.
Default value:
UTF-8.

sets of U2000. If
multiple sets of
layer OSS, this
parameter must be
NMS planning.
Default value:
Huawei/U2000.


log file, ranging
from 1 MB to 20
MB. Keeping the
default value is
recommended.
Default value: 20
MB.

value is
recommended.
Default value: Log
immediately.

Keeping the default
Log l Assertion/
Log: Enable
– Enable
l I/O Error Log:
– Disable Enable
Log Log: Disable.
– Enable
– Disable


confirming with the
upper-layer OSS.
Only transport NEs
have physical IDs.
l Physical ID: is
expressed in
dotted decimal
notation and
equals to the NE
ID x 65536 +
extended ID. For
example, if the
NE ID is 1 and
the extended ID
is 9 for NE(9-1),
the physical ID is
65545.
l Physical ID: is
expressed in
dotted decimal
notation and is
automatically
assigned by the
U2000 to NEs.
For example,
3145765.
Default value:
Logical ID.


SDH manages devices
Otherwise, disable
this function.
Default value:
Enable.

alarms are reported
in alarm update
mode.
Default value: All.

and need to be used
along with the
U2000 engineering
that all alarms are
queried and
reported.
l Enable: specifies
that all alarms
excluding
engineering
alarms are
queried and
reported.
Default value:
Disable.


er reported from
CORBA NBIs to the
U2000.
l Internal ID:
specifies that the
ID assigned by
the U2000 is the
unique identifier
of an object.
l Object name:
specifies that the
object name
displayed on the
U2000 is the
unique identifier
of an object. The
object name on
the U2000 client
must be the same
as that on the
U2000 server.
Otherwise, data
conflicts may
occur.
Default value:
Internal ID.

Reporti reported.
that the names of
the paths and
fibers affected by
alarms are
queried and
reported.
that the names of
the paths and
fibers affected by
alarms are not
reported.
Default value:
Disable.


U2000 to
upper-layer OSS.
Ensure that SNMP
NBIs can use the IP
address and port
number to send trap
messages to the
upper-layer OSS.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 6666.

number used by the
U2000 to
upper-layer OSS.
Ensure that upper-
layer OSS can use
the IP address and
port number to send
U2000.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 9812.


ters USM is such a
security mechanism.
Currently, only USM
is supported.
Default value: USM.

ion configured, you
and must selected a
ption and set the
witho for the
l With Without
nticat encryption.
ion
and
encry
ption


5 protocol used for
CSH SNMP NBIs. The
A value of this
parameter must be
the same as the
authentication
The authentication
protocol can be set
when the security
level is With
authentication,
without encryption
or With
authentication and
encryption.

ion encrypting
communication data.
The value of this
parameter must be
encryption protocol
used for the
The data encryption
when the security
level is With
authentication and
encryption. The
AES protocol is
recommended
because it provides
better security.


layer OSS. This
receive trap
messages sent by
SNMP NBIs.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 6666.

used by SNMP
recommended
because it is more
secure than SNMPv1
and SNMPv2c.
Default value: v3.


the upper-layer OSS
to access the U2000
when the SNMPv1
and SNMPv2c use
read and write
community names.
upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value of
Read Community:
Changeme_123.
Default value of
Write Community:
Changeme_123.

name and password
used for SNMPv3–
based security
mechanism. If this
the upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value:
admin.

authentication,
without encryption
or With
authentication and
encryption. This
the upper-layer OSS
to access the U2000
using SNMP NBIs.
Default value:
Changeme_123.


must be set if the
security level is
With
authentication and
encryption.
Default value:
Changeme_123.

r NBIs.
l Warn
ing


l Unac is generated
know when a fault
ledge occurs.
d l Acknowledged:
ged confirmed,
SNMP NBIs
report an
acknowledged
alarm.
l Unacknowledged
: After an alarm
is reversely
confirmed,
SNMP NBIs
report an
unacknowledged
alarm.
l Changed: If
alarm
information is
changed, SNMP
NBIs report a
changed alarm
which contains
the alarm level
change, alarm
influence path,
and alarm root
cause identifier.

eat of transmitting
When the U2000
MIB is used, SNMP
NBIs report
heartbeat messages
period.
Default value: 60s


e report heartbeat
le MIB, instead of
U2000–T MIB,
supports the
reporting of
heartbeat messages.
Default value:
Enable

variables contained
in the alarm
by SNMP NBIs.
This parameter must
be set according to
the alarm planning
for the upper-layer
U2000 SNMP NBI
User Guide.


m messages by SNMP
NBIs. Keeping the
default value is
recommended.
l Trap: After trap
messages are
reported, the
system does not
need to report the
next trap message
until a response
is received from
the upper-layer
OSS.
l Inform: After
trap messages are
reported, the
system starts to
report the next
trap message
until a response
is received from
the upper-layer
OSS or the
number of
attempts exceeds
the threshold.
Default value: Trap

level defined by X.
733.
Default value: No

messages in Trap
mode.
Default value: 0

packet in Inform
mode.
Default value: 5


connection times in
Inform mode upon a
connection failure.
Default value: 3

(with Time
out
time
zone)
l Local
Time
(with
time
zone)

Default value:
UTF-8

alarm and reported.
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All


g l Disable Disable
alarm queried and
reported.
Enable: specifies
that all alarms
except for
engineering alarms
are queried and
reported.

MIB T2000-
NETMANAGEME
NT-MIB.mib:
U2000-T MIB HW-
IMAPV1NORTHBO
UND-TRAP-
MIB.mib or HW-
IMAPV2NORTHBO
UND-TRAP-
MIB.mib: U2000
MIB

r to e record logs.
logs le Disable


time alarms. Every
upper-layer OSS
an independent
cache.
If the alarm
generation rate is
report rate, NBI
information to the
cache.

default port used
varies according to
the mode. The SSL
mode is
recommended
because it enables
better security.
the Use SSL check
box.

teh JMS service.
Currently, the
activeMQ
middleware is
supported.

address of the JMS
service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
access the U2000.


of the port used by
the JMS
middleware. This
to the upper-layer
OSS.

service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
access the U2000.

of the port used by
XML NBIs. The
upper-layer OSS
uses this port to
obtain Web service
data from XML
NBIs.
Default value: 9997

use AFB-based
interface (such as
getInventory), the
the synchronization
mode (such as SIT
or SRR) is used, do
service in order to
save system
resources.
Default value: Yes.


Web service. This
parameter is set
based on the
HTTPS is
recommended
because it is more
secure than HTTP.

troubleshooting.
Default value: Warn

alarm and reported.
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All

planning for the
Default value:
UTF-8


U2000 when they
are managed by the
same upper-layer
OSS. Set the
parameters
NMS planning.
Default value:
Huawei/U2000

order, which is
convenient for the
analysis of the
upper-layer OSS.
WDM routes are
sent randomly.
Forward: specifies
that WDM routes are
to the sink.
Backward: specifies
that WDM routes are
the source.
Default value: None


theme these themes.
– Disable
Default value: The
– Enable
– Disable
l Filter Out
Protection
Notification
– Enable
– Disable
l Filter Out
Performance
Notification
– Enable
– Disable
l Filter Out
Maintenance
Notification
– Enable
– Disable


related operation
XML NBI.
l Installation: By
default, this
parameter is set
to Enable.
l Version upgrade:
It is
recommended
that the value of
this parameter be
retained the same
before and after
the upgrade.
Perform
automatic
upgrades with the
NMS upgrade
the manual
upgrade mode is
used, change this
parameter
manually to keep
consistency.
Default value:
Enable

ring and the alarm
along with U2000
engineering tasks.
By default, all
Default value:
Disable


er l Internal ID:
specifies that the
IDs assigned by
the U2000
uniquely identify
objects.
l Object name:
specifies that the
U2000 client
names are used to
identify objects.
The U2000 client
names must be
unique in order to
prevent data
conflicts.
Default value:
Internal ID

tion alarms.
l Enable: specifies
that if an alarm
affects paths or
fibers, the names
of the affected
paths and the
fibers are
contained in the
alarm
information
during alarm
query and report.
that the names of
the affected paths
and fibers are not
reported.
Default value:
Disable


or more periods.

this parameter for
different device
value of this
parameter is the
same for different
device types, the
performance data
fail fails to be
exported. The Auto
mode is
recommended. For
details, see U2000
Performance Text
NBI User Guide.
Default value: Auto

l 30 text NBIs. The
can be exported
l 1440 based on the
collection period.



the time
performance data is
generated on NEs
and the time the
is exported.
You must configure
Data Export
Duration (min)
requirements when
set to Manual. For
details, see U2000
Performance Text
NBI User Guide.

the startup file is
cannot be set to a
value ranging from
23:00:00 to
01:00:00. If the
value of this
parameter ranges
from 23:00:00 to
01:00:00, a data
error occurs during
DTS switching.
yyyy-mm-dd
hh:mm:ss
For example,
2009-09-01 01:00:00


performance
indicators that the
can export.
Performance
indicators can be
configured in two
modes: template—
based or manual
configuration
l Template-based
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
configure a
performance
indicator
template and use
the following
operations to
configure the
performance
indicators. For
details, see
U2000
Performance Text
NBI User Guide.
Full Import:
specifies that
performance
indicators are
fully imported to
the performance
indicator
template to
overwrite the
original indicator
template.
Incremental
Import: specifies
that performance
indicators are
incrementally
imported to the
performance

indicator
template and only
new indicators
are added to the
original indicator
template. Export:
The performance
indicator
template is
exported, backed
up, or provided to
another U2000
server.
l Manual
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
print the
performance
data. Modify: In
the dialog box
that is displayed,
configure the
indicators as
required.

accesses this
directory to obtain
performance data.


P the FTP user
password on the
–S U2000.
F
T Using SFTP is
P recommended
because SFTP
Serve
r IP:
l FTP/
SFTP
Port:
l FTP/
SFTP
User:
l FTP/
SFTP
Pass
word:
l FTP/
SFTP
Direc
tory:
l SFTP
Certif
icate:

Default value: 20

output logs.
Default value: 20


l Error recorded.
Default value: Info

planning for the
Default value:
UTF-8

export NBI file.
Default value: UTC
time

records in a file.
the threshold, the
extra records are
whose serial number
is increased by 1.
Default value:
100000

local server. The
deletes the files
generated after the
period elapses.
Default value: 3
days


task. The value of
same as the server
time.
Format: yyyy-mm—
dd hh:mm:ss

ate File Name
For details, see
section Security
Trust File Name
Certificate
Certific
Description.
ate
CRL File Name

section SSL
Principle and
Configuration.

Prerequisites
NOTICE


Context
Procedure
NOTE
NOTE
as255.255.255.0.
ossuser user.
NOTE
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE

$ ./stopnms.sh


install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.
NOTE
...

...
NOTE
been started.
# su - ossuser
$ ./startserver.sh

3. Click Login.
NOTE
MSuite at one time.

window.
Parameters.

NOTICE
# shutdown -r now
----End
Follow-up Procedure
SUSE Linux.

U2000 license.
Prerequisites
Installation Guide.

NOTICE
space or \ /:*?"<>|.
Context
– Method one:
log in to GUI OSs.
– Method two:
NOTE
Procedure
NOTE
Password.


install/RUN_DBSVR


...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE

$ ./startnms.sh
$ ls
NOTE
command.


NOTE
by SFTP.
NOTE

old value new value
500 500
1 1
Export 1 1
Client 1 1
installed.
is displayed.
the U2000 client.

iii. Click OK.
v. Click OK.
iv. Click Next.
vi. Click Finish.
----End
Result

installed.
Prerequisites
License.

NOTE
Context
configurations.
Procedure
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
$ ./startnms.sh

is displayed.
client:
menu.

----End
Result

Context
Procedure
NOTE
Password.
NOTICE
operations.

l U2000 Server

l /opt/oss/engr
l /opt/oss/OSSJRE
l /opt/oss
l /opt/sybase

l /etc/ICMR
l /var/ICMR

...
...

install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb

NOTE

$ ./startnms.sh

installed.
NOTE
is displayed.
NOTE
----End
Follow-up Procedure
directory.
$ su - root
NOTICE


Cold Standby & Single-Server System Software Installation 4 Installing and Commissioning the U2000 (Fresh
and Commissioning Guide (SUSE Linux) Installation)

(Fresh Installation)
About This Chapter
This topic describes how to collect information required for installation and commissioning
and how to install and commission the U2000, including Single-Server System (SUSE Linux)
and cold standby solutions.
This topic briefly describes the fresh installation scenario.
4.2 Installation and Commissioning Process
This topic describes the process and required time for installing and commissioning the
Single-Server System (SUSE Linux) and the cold standby solution.
4.3 Preparing for Installation
This topic describes the preparations to be made before the single-server system (SUSE
Linux) or the cold standby solution is installed, including collecting installation information,
checking mandatory software and hardware connections, and applying for the U2000 and SSR
licenses.
controller IP addresses for servers before installing the operating system (OS).
4.7 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.
4.8 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.
4.9 Installing the U2000 Software
This topic describes how to start the U2000 installation.
This topic describes how to commission the U2000. To allow the U2000 to manage your
network, you must commission the U2000 before using the U2000 to manage NEs and
configure services.
4.11 Configuring the Cold Standby Solution (Cold Standby Solution)
Guide. This topic applies only to the cold standby solution. If the cold standby solution is not
required, skip this topic.

This topic briefly describes the fresh installation scenario.
In the fresh installation scenario, no pre-installation is performed on servers delivered by
Huawei. Instead, you need to install and commission the U2000 on site.
l For a single-server system, you only need to install and commission one set of U2000.
l For the cold standby solution, you need to install and commission two sets of U2000,
one is for the primary site and the other is for the secondary site. The U2000 version,
deployment domain, language, OS type, server time zone, and time must be the same on
the primary and secondary sites.
For details about the background, usage restrictions, and implementation process of the
cold standby solution, see 2.1 Solution Description in Factory Installation of the Cold
Standby Solution.
4.2 Installation and Commissioning Process

Single-Server System (SUSE Linux) and the cold standby solution.
4.2.1 Installation and Commissioning Process (Single-Server

System)
Single-Server System (SUSE Linux).

NOTE
SUSE Linux OS.
is performed.
Figure 4-1 shows the installation and commissioning process of the Single-Server System
(SUSE Linux).

Figure 4-1 Installation and commissioning process of the Single-Server System (SUSE
Linux)

4.2.2 Installation and Commissioning Process (Cold Standby

Solution)
This topic describes the process and required time for installing and commissioning the cold
standby solution.
NOTE
SUSE Linux OS.
is performed.
Figure 4-2 shows the installation and commissioning process of the cold standby solution.
Figure 4-2 Installation and commissioning process of the cold standby solution
4.3 Preparing for Installation

This topic describes the preparations to be made before the single-server system (SUSE
Linux) or the cold standby solution is installed, including collecting installation information,

checking mandatory software and hardware connections, and applying for the U2000 and SSR
licenses.
4.3.1 Collecting Installation Information

This topic describes information to be collected for installing the single-server system and the
cold standby solution.
4.3.1.1 Collecting Installation Information (Single-Server System)

This topic describes how to collect installation information. Before installing a single-server
system (SUSE Linux), collect required information, including the host name, IP address,
route, time zone and time, user password, installation path, component quantity, and instance
quantity.
Planning Guide. Collect and record the installation information in the tables.
NOTE
Host Name Planning
NOTICE
Item Example Plan
Server NMSserver

IP Address Planning
IP address of the IP address of the IMM can be used to remotely log in to a PC

IMM (Integrated server to manage and maintain PC server in Web mode. For
Management example, you can use this IP address for remote OS installation, or
Module) on the PC use it to maintain the PC server if the OS fails to start properly.
server
NMS server and NEs.
l The IMM/iMana IP address and system IP address can be located either on the same
network segment or on different network segments.
– The NMS application IP address communicate with the managed equipment in the
normal state.
– The NMS application IP address communicate with the OSS in the normal state.
– The NMS application IP address communicate with U2000 clients in the normal
state.
NOTE
Destination_IP to ensure that NMS application IP address can be normal communicated.
l Single-NIC Scheme


IMM/ 10.9.1.20/255.255.255.0/10.9.1. The IMM/iMana IP address and

iMana IP 254 system IP address can be located
address either on the same network segment
or on different network segments.
System IP 10.9.1.2/255.255.255.0/10.9.1.2
address 54

for the disk 10.9.1.10/255.255.255.0/10.
array 9.1.254
10.9.1.11/255.255.255.0/10.
9.1.254
l Double-NIC Scheme
NOTE

IMM/ 10.9.1.20/255.255.255.0/10.9.1. l The IMM/iMana IP address and

iMana IP 254 system IP address can be located
address either on the same network
segment or on different network
segments.
configured with bond. If eth0 and
eth2 interfaces are selected


System IP 10.9.1.2/255.255.255.0/10.9.1.2 during system reconfiguration to

address 54 configure bond, the system IP
address corresponds to both the

for the disk 10.9.1.10/255.255.255.0/10.
array 9.1.254
10.9.1.11/255.255.255.0/10.
9.1.254
Route Planning

Item Example Plan
Routing network 10.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
network.

Item Example Plan
Time 14:00

IP address

NOTICE

Preinstallation
IMM user PASSW0RD PASSW0RD

USERID NOTE
The sixth character is
digit 0 but not letter O.

root

NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ossuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ftpuser NOTE
modify the default
password and
remember the new
see A.5.29 How to
Change the Password


Preinstallation

dbuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

user dbuser NOTE
store U2000 Guard
modify a database
password, seeA.5.24
How Do I Change an
H2 Database User's
Password for the
U2000 Guard.

webuser NOTE
l An independent
account used to run
Tomcat and Apache
services.
modify the default
password and
remember the new
password. For
details, see A.1.1
How to Change
the OS User
Password.

5500 V3 user
admin
OceanStor Admin@storage Admin@storage

S3900 user
admin


Preinstallation
Kaimse l 5500 V3: l 5500 V3:

NOTE – authenticate – authenticate
Account for password: password:
Trap
ism@Storage ism@Storage
authenticating
the device – private – private
alarms password: password:
reported by an ism@Storage ism@Storage
5500 V3,
S3900 or l S3900/S2600: l S3900/S2600:
S2600 disk Kaimse@storage Kaimse@storage
array. The
account
cannot be used
for login.

sa

user ossuser NOTE
The H2 database is
data of NBI
H2 database is
need to change the
How Can I Change
the Password of the
H2 Database .
H2 database file is
need to change the
How Can I Change
the Password of the
H2 Database File.

database NOTE
after the U2000 is
may be manually
with a customized
administrator name,
such as dbadmin.


Preinstallation

Database user NOTE
not have a default
password. The
during U2000
installation.

admin NOTE
You must change the
first-time login.

Management NOTE
admin
A quick installation DVD is used to install an OS, the installation software automatically
partitions disks according to the disk size. For details about disk partitioning planning, see G
Planning Disk Partitions.
4.3.1.2 Collecting Installation Information (Cold Standby)

This topic describes how to collect installation information. Before installing the cold standby
solution, collect required information, including the host name, IP address, route, time zone
and time, user password, installation path, component quantity, and instance quantity.
Planning Guide. Collect and record the installation information in the tables.
NOTE

Host Name Planning
NOTICE
Site Item Example Plan
Primary site Host name Primaster
Secondary site Host name Secmaster
IP Address Planning
IP address of the IP address of the IMM can be used to remotely log in to a PC

IMM (Integrated server to manage and maintain PC server in Web mode. For
Management example, you can use this IP address for remote OS installation, or
Module) on the PC use it to maintain the PC server if the OS fails to start properly.
server

NMS server and NEs.
l The IMM/iMana IP address and system IP address can be located either on the same
network segment or on different network segments.
normal state.
state.
NOTE
l Single-NIC Scheme

Primary IMM/ 10.9.1.20/255.255.255.0/1 The IMM/iMana IP address

site iMana IP 0.9.1.254 and system IP address can be
address located either on the same
network segment or on
System 10.9.1.2/255.255.255.0/10. different network segments.
IP 9.1.254
address
address 10.9.1.10/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.11/255.255.255.
0/10.9.1.254


Secondar IMM/ 10.9.1.21/255.255.255.0/1 The IMM/iMana IP address

y site iMana IP 0.9.1.254 and system IP address can be
address located either on the same
network segment or on
System 10.9.1.2/255.255.255.0/10. different network segments.
IP 9.1.254
address
address 10.9.1.12/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.13/255.255.255.
0/10.9.1.254
l Double-NIC Scheme
NOTE

Primary IMM/ 10.9.1.20/255.255.255.0/1 l The IMM/iMana IP address

site iMana IP 0.9.1.254 and system IP address can
address be located either on the
same network segment or
on different network
segments.


System 10.9.1.2/255.255.255.0/10. selected during system

IP 9.1.254 reconfiguration to configure
address bond, the system IP address
address 10.9.1.10/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.11/255.255.255.
0/10.9.1.254
Secondar IMM/ 10.9.1.21/255.255.255.0/1 l The IMM/iMana IP address

y site iMana IP 0.9.1.254 and system IP address can
address be located either on the
same network segment or
System 10.9.1.2/255.255.255.0/10. on different network
IP 9.1.254 segments.
address
address 10.9.1.12/255.255.255.
for the 0/10.9.1.254
controller 10.9.1.13/255.255.255.
0/10.9.1.254
Route Planning

Item Example Plan
Routing network 10.9.10.0/255.255.255.0

segment 1
Routing network 10.71.6.0/255.255.255.0

segment 2

Item Example Plan
... ...
Routing network 10.121.124.0/255.255.255.0

segment N
NOTE
network.

For the cold standby solution, ensure that the time zone and time are the same on the primary
and secondary sites.
Item Example Plan
Time 14:00

IP address
NOTICE

Preinstallation
IMM user PASSW0RD PASSW0RD

USERID NOTE
The sixth character is
digit 0 but not letter O.


Preinstallation

root

NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ossuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.

ftpuser NOTE
modify the default
password and
remember the new
see A.5.29 How to
Change the Password

dbuser NOTE
modify the default
password and
remember the new
see A.1.1 How to
Change the OS User
Password.


Preinstallation

user dbuser NOTE
store U2000 Guard
modify a database
password, seeA.5.24
How Do I Change an
H2 Database User's
Password for the
U2000 Guard.

webuser NOTE
l An independent
account used to run
Tomcat and Apache
services.
modify the default
password and
remember the new
password. For
details, see A.1.1
How to Change
the OS User
Password.

5500 V3 user
admin
OceanStor Admin@storage Admin@storage

S3900 user
admin
Kaimse l 5500 V3: l 5500 V3:

NOTE – authenticate – authenticate
Account for password: password:
Trap
ism@Storage ism@Storage
authenticating
the device – private – private
alarms password: password:
reported by a ism@Storage ism@Storage
5500 V3,
S3900 or l S3900/S2600: l S3900/S2600:
S2600 disk Kaimse@storage Kaimse@storage
array. The
account
cannot be used
for login.

sa


Preinstallation

user ossuser NOTE
The H2 database is
data of NBI
H2 database is
need to change the
How Can I Change
the Password of the
H2 Database .
H2 database file is
need to change the
How Can I Change
the Password of the
H2 Database File.

database NOTE
after the U2000 is
may be manually
with a customized
administrator name,
such as dbadmin.

Database user NOTE
not have a default
password. The
during U2000
installation.

admin NOTE
You must change the
first-time login.


Preinstallation

Management NOTE
admin
A quick installation DVD is used to install an OS, the installation software automatically
partitions disks according to the disk size. For details about disk partitioning planning, see G
Planning Disk Partitions.

If the cold standby solution is used, ensure that the U2000 version, deployment domain,
language, OS type, server time zone, and time are the same on the primary and secondary
sites.
U2000 Installation Methods

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.
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. Contact a Huawei engineer to download the software packages.

– For carrier, Log in to http://support.huawei.com/carrier. Search for U2000 and
select iManager U2000 in the search box on the Software tab. Select the
corresponding version of U2000 to download the U2000 install software package,
for example, iManager U2000 version. Select the corresponding version of U2000
to download the server install software package (such as the OS, OS preconfigured
component, and Quick RAID configuration DVD), for example, iManager U2000-
Tool(Server_Install_X.0) version.
– For enterprise, Log in to http://support.huawei.com/enterprise. Search for U2000
and select iManager U2000 in the search box on the Support tab. Then, click
Downloads and select a desired version.

2. Download required software packages listed in Table 4-15. 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 website.
NOTE
The PGP verification file of the software file in the .asc format must be obtained by clicking the
in the Operation column at the same time. For example, the software package is
U2000version_server_nmsbase_sles_x64.7z, the corresponding PGP verification file is
U2000version_server_nmsbase_sles_x64.7z.asc.
3. Use the PGPverify to verify correctness of the software packages. For details, see A.1.24
How Do I Verify Downloaded Software Packages Using the PGPVerify Software.
4. http://support.huawei.com can store files with a maximum size of 8 GB. The file with
the size larger than 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.
– 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.
– 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 http://www.7-zip.org/support.html for technical
support.
NOTE
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 4-15 Software package list
Software Software Medium Name Description

Type
Server SUSE Quick OS installation DVD It must be available. It is used

install Linux OS U2000version_server_os_sles to install the SUSE Linux OS.
software Disk 11_x64_dvd1 or ISO image
package file of the quick installation
DVD
U2000version_server_os_sles
11_x64_dvd1.iso.
Quick For Huawei RH series rack It must be available. It is used

RAID server, the to configure RAID.
configurat Sles_server_raid_x64_for_Hu
ion DVD awei_dvd.iso file must be
ready.


Type
OS U2000version_server_ICMR_ It must be available. It is used

preconfig sles_x64.tar to install the U2000.
ured
componen
t
U2000 U2000 Basic component: It must be available. It is used

software server U2000version_server_nmsbas to install the U2000.
package software e_sles_x64.7z
Core component: It must be available. It is used

U2000version_server_nmscor to install the U2000.
e_sles_x64.7z
Transport component: It is required only if the

U2000version_server_nmstra U2000 needs to manage
ns_sles_x64.7z Huawei transport equipment.
Huawei transport equipment
includes:
l MSTP equipment
l WDM equipment
l NA WDM equipment
l Submarine equipment
l RTN equipment
l PTN equipment
NOTE
Software packages for the
transport and IP components
must be available so as to
manage PTN 6900 and PTN
7900 series NEs.


Type
IP component: It is required only if the

U2000version_server_nmsip_ U2000 needs to manage
sles_x64.7z Huawei IP equipment.
Huawei IP equipment includes:
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 is required only if the

U2000version_server_nmsacc U2000 needs to manage
ess_sles_x64.7z Huawei access equipment.
Huawei access equipment
includes:
l FTTx equipment
l MSAN equipment
l DSLAM equipment
l BITS equipment
ESN tool ESN tool: The ESN tool is required only

U2000version_ESN_sles_x64. when you apply for the U2000
tar 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.
SetSuse Installation package: It must be available. It is used

software U2000version_VPPSetSuse11 to enhance the security of
package V300R003C22SPC200.tar SUSE Linux OS.


Type
Database Database software package: It must be available. It is used

software U2000version_server_db_linu to install the database.
package x_sybase.tar
Using DVDs
Before installing the U2000 by using DVDs, ensure that the following DVDs are available.
Table 4-16 DVD list

DVD Name Software
Terminal Physical Software, Quick installation DVD:

iManager U2000, iManager U2000version_server_os_sles11_x64_dvd1
U2000 version_server_sles,
Physical Software Package For
Linux Network Management
System, CD 1/4
Terminal Physical Software, Patch DVD. Optional. Select this software package
iManager U2000, iManager when installing the OS patch.
U2000 version_server_sles, U2000version_server_patch_sles11_x64_dvd2
System, CD 2/4
Terminal Physical Software, Database software DVD:

iManager U2000, iManager U2000version_server_db_sles_x64_dvd3
System, CD 3/4
Terminal Physical Software, U2000 server software DVD:

iManager U2000, iManager U2000version_server_nms_sles_x64_dvd4
NOTE
Physical Software Package For U2000 server software include SetSuse software package, it
Linux Network Management is used to enhance the security of SUSE Linux system.
System, CD 4/4
Terminal Physical Software, Quick RAID configuration DVD

iManager U2000, NSDRCFI04, For Huawei RH series rack server, the
HUAWEI RAID Configuration, Sles_server_raid_x64_for_Huawei_dvd.iso file must
Physical Software Package For be ready.
SUSE Linux, CD

DVD Name Software
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 4-17 shows the tools required to be available before the U2000 is installed using
software packages or DVDs.
Table 4-17 Tool list

o
.



o
.
2 For IBM On the PC l If a JRE has been installed, run the java -version
server, or laptop, command in the CLI to view the JRE version. If a JRE
JRE with JRE is used has not been installed, running the command fails.
the to access l If the version of the installed JRE is not 1.8.0_101,
version the remote downloading and installing JRE 1.8.0_101 is
of control recommended. You can uninstall the existing JRE in
1.8.0_10 desktop Control Panel.
1. 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.8.0_101 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. For more information
about software operation, see the software Help or go to
the official website of the software http://
www.java.com/en/download/help/ for technical support.
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.


o
.
server.
Using SSH
(more
secure,
recommend
ed) to log
in to the
server is
recommend
ed.
SFTP.
5 PGPverif The Download the latest version.

y tool PGPverify 1. Download and decompress the PGPverify tool.
tool is used
to verify l For carrier: visit http://support.huawei.com/carrier/
the digitalSignatureAction to download the OpenPGP
correctness Signature Verification Guide package and
of the decompress it to obtain the OpenPGP Signature
downloade Verification Guide.pdf, VerificationTools.zip and
d software KEYS. Continue to decompress the
compressio VerificationTools.zip package in the current folder.
n package. l For enterprise: visit http://support.huawei.com/
enterprise/en/tool/software-digital-signature-
validation-tool--pgp-verify--TL1000000054 to
download the OpenPGP Signature Verification
Guide.pdf, VerificationTools.zip and KEYS and
decompress the VerificationTools.zip package.
2. Go to the VerificationTools folder that is generated after
decompression and obtain the PGPVerify software
PGPVerify-x86_64.tar.gz for Linux OS in linux
\X86\bit64\PGPVerify TOOL folder.
3. KEYS is the public key file.


Context
support engineers.
l In the cold standby solution, the primary and secondary sites share the same U2000
license. The U2000 license is bound to the ESNs of the primary and secondary sites at
the same time. When applying for a license, you need to obtain the ESNs of the primary
and secondary sites separately.
Procedure

NOTE

# cd /opt


# ./esn

ESN0:****************************************
ESN1:****************************************
ESN2:****************************************
ESN3:****************************************
...
# ./esn

ESN0:****************************************
ESN1:****************************************
ESN2:****************************************
ESN3:****************************************
...
Mode 3: Query information about the software and hardware installation and ESNs of a
Huawei rack server at http://texpert.huawei.com/TExpert/Pages/PageContainer.htm. For
details, see A.5.20 How to Query Information About the Software and Hardware
Installation and ESNs of a Huawei Rack Server.
office.
NOTE
and ESNs.
NOTE
----End

Prerequisites
NOTE

Procedure
License.
NOTE
----End

Prerequisites

Procedure
NOTE

NOTE
number of 1 can be used for the Huawei RH5885H V3, Huawei RH2288H V3, Huawei RH2288H V2,
IBM X3650 M4, IBM X3650 M3 and IBM X3850 X5 servers.
NOTE
and the OceanStor S3900 disk array.

OceanStor S3900 disk array
NOTE

NOTE

NOTE
NOTE
l Figure 4-8 shows hardware connections for the IBM X3650 M4 server.
Figure 4-8 Hardware connection for the IBM X3650 M4 server
NOTE
For the mappings between physical and logical network interfaces on an IBM server, seeA.3.8
Mappings Between Physical and Logical Network Interfaces on an IBM Server Running
SUSE Linux.

l Figure 4-9 shows hardware connections for the IBM X3650 M3 server.
Figure 4-9 Hardware connection for the IBM X3650 M3 server
NOTE
For 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 Figure 4-10 shows hardware connections for the IBM X3850 X5 server.
Figure 4-10 Hardware connection for the IBM X3850 X5 server
NOTE
Running SUSE Linux.

l Figure 4-11 show the hardware connections between the IBM X3850 X5 server and the
OceanStor S3900 disk array.
Figure 4-11 Hardware connections between the IBM X3850 X5 server and the
OceanStor S3900 disk array
NOTE
Running SUSE Linux.
l Figure 4-12 show the hardware connections between the IBM X3850 X5 server and the
OceanStor 5500 V3 disk array.

Figure 4-12 Hardware connections between the IBM X3850 X5 server and the
NOTE
Running SUSE Linux.

----End
Follow-up Procedure

Server
1. Power on a Huawei RH2288H V2/Huawei RH2288H V3/Huawei RH5885H V3/IBM
X3650 M4/IBM X3650 M3/IBM X3850 X5 server.

NOTICE
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC
and 200 to 240 VAC input voltage.
NOTE
RH2288H V2, Huawei RH2288H V3, Huawei RH5885H V3, IBM X3650 M4, IBM
X3650 M3 and, IBM X3850 X5.

Figure 4-16 Position of the power button on IBM X3650 M4
Figure 4-17 Position of the power button on IBM X3650 M3
Figure 4-18 Position of the power button on IBM X3850 X5

Disk Array
NOTICE
it on.

l For OceanStor 5500 V3:
– Normal power-on sequence: 1. Turn on the power switches of the external power
supplies connected to all the devices. 2. Press the power button on either controller.
3. Turn on the LAN switch or FC switch (if any LAN switch or FC switch is
deployed but is not powered on). 4. Turn on the application server (if the
application server is not powered on).
– Normal power-down sequence: 1. Stop the services of the application server. 2.
Hold the power button for 5 seconds on the controller enclosure. 3. Disconnect the
controller enclosure and disk enclosures from the external power supplies.
l For OceanStor S3900:
– Normal power-on sequence: 1. Turn on the power switches of the external power
supplies connected to all the devices. 2. Press the power button on either controller.
3. Turn on the LAN switch or FC switch (if any LAN switch or FC switch is
deployed but is not powered on). 4. Turn on the application server (if the
application server is not powered on).
– Normal power-down sequence: 1. Stop the services of the application server. 2.
Hold the power button for 5 seconds on either controller. 3. Disconnect the
controller enclosure and disk enclosures from the external power supplies.
l For OceanStor S2600:
– Power-on sequence: cabinet → disk enclosures → controller enclosure → switch (if
has) → application server.
– Power-off sequence: application server → switch (if has) → controller enclosure →
disk enclosures → cabinet.
NOTE
l 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.
l Power supply must be provided for the two power modules of the OceanStor 5500 V3; otherwise,
the OceanStor 5500 V3 fails to be used. Press the power button on controller A/B. Wait 5 to 10
minutes until the power indicator is steady green and no longer flashing, indicating the power-on
success.
steady green.

indicators are off.

controller IP addresses for servers before installing the operating system (OS).


mode of using BIOS.
l Through BIOS:
NOTE


Prerequisites
used.
NOTE
Context
in again.
Procedure

NOTE
NOTE

NOTE



NOTE
is displayed.
----End

Prerequisites
NOTE
Context

in again.
Procedure
RH5885H V3 server.
following figure.

NOTE
NOTE

NOTE

NOTE
is displayed.

----End

Prerequisites
of the server.
Procedure
started.
NOTE

operations:
operations:
operations:
operations:
displayed.

box is displayed.

configuration page.
----End
4.6.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
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.
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.

NOTE
l For more operations on the IBM X3650 M4 server, log in to the server's official website at http://
www-947.ibm.com/support/entry/portal/product/system_x/system_x3650_m4?
productContext=1128598353.
l For more operations on the IBM X3850 X5 server, log in to the server's official website at http://
www-947.ibm.com/support/entry/portal/documentation_expanded_list/hardware/systems/
system_x/system_x3850_x5.
4.6.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
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
4.6.2.2 Configuring the IMM IP Address Through IMM Management Interface

(IBM X3850 X5 and IBM X3650 M3)
server in Web mode. This topic describes how to configure the IMM IP address through IMM
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
IBM 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

3.6 How to 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
4.6.2.3 Configuring the IMM IP Address Through BIOS

server in Web mode. This topic describes how to configure the IMM IP address through
BIOS.
Prerequisites
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.
l For IBM X3850 X5, show as follows:

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
4.6.3 Configuring Controller IP Addresses for Disk Arrays

This topic describes how to configure controller IP addresses for the OceanStor 5500 V3,
OceanStor S3900 disk array.
4.6.3.1 Setting the SC IP Address for the OceanStor 5500 V3 Disk Array
Prerequisites
serial port:
NOTE
menu.
Context
10.9.1.11.
Procedure


navigation tree.
– Data bits: 8
– Stop bits: 1
– Parity: None

5. Click Open.
Storage login:

NOTE



System Name : xxxx

SN : xxxx
Location :


IPv4 Address : 192.168.128.101
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Gateway :
--------------------------------------
IPv4 Address : 192.168.128.102
Subnet Mask : 255.255.255.0
IPv4 Gateway : 192.168.128.254
IPv6 Address : --
IPv6 Gateway :

descriptions.

subnet mask.
gateway.



is inaccessible.




Subnet Mask : 255.255.255.0
IPv6 Address : --
IPv6 Gateway :
--------------------------------------
Subnet Mask : 255.255.254.0
IPv6 Address : --
IPv6 Gateway :
admin:/> exit
----End
4.6.3.2 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
serial port:
NOTE
menu.
Context
The OceanStor S3900, a disk array, has two controllers. The IP addresses configured in this
controller A to 192.168.128.203 and the IP address of the management network of controller
B to 192.168.128.204.
Procedure


navigation tree.
– Data bits: 8
– Stop bits: 1
– Parity: None

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
After an admin user enters an incorrect password for three consecutive times, the admin user will be
locked and therefore cannot be used to log in to the disk array controller. The admin account will be
automatically unlocked after 15 minutes.
The default user name and password of the system administrator are admin and Admin@storage. 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
Step 3 In the CLI, run the chgctrlip command to configure the IP address for the network interface
of controller A. See Table 4-19.
Table 4-19 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
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 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.
----End
4.7 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.
4.7.1 Configuring the RAID in Remote Mode (Huawei RH2288H

V3 and Huawei RH5885H V3, 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 version of the Internet Explorer browser must be 9.0 or above and the Internet
Explorer cannot be configured with a proxy server.
l The IP address of the iBMC is available. For details about how to set the IP address of
the iBMC, see 4.6.1.2 Configuring the iBMC IP Address Through iBMC
Management Interface(HUAWEI RH2288H V3 and HUAWEI RH5885H V3).
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 (if a disk array is configured,
ensure that the two hard disks of the server are available). Otherwise, RAID
configuration fails. For details, see A.2.9 Viewing Hard Disk Information (Huawei
RH2288H V3 or Huawei RH5885H V3).
Context
protection.

NOTICE
Ensure that the server has two or eight hard disks, otherwise, automatically configuring a
RAID using the ISO image file may fail. If the server has over eight hard disks, manually
configure a RAID using the controller card.
l If the delivered server is not connected to a disk array, ensure that the Huawei
RH2288H V3 server and Huawei RH5885H V3 server for standard delivery have
eight 600G hard disks, and the RAID level plan and partition plan are as follows.
– The first and second hard disks are configured as RAID 1 for installing OS software
and data.
– The third, fourth, fifth, and sixth hard disks are configured as RAID 10 for storing
service data and software.
– The seventh hard disk is used to system back up. It is configured as RAID 0.
– The eighth hard disk is configured as RAID 0 to back up the database.
l If the delivered server is connected to a disk array, ensure that the Huawei
RH5885H V3 server for standard delivery has two 600G hard disks, the disk array
OceanStor 5500 V3 or OceanStor S3900 have 12 hard disks, and the RAID level
plan and partition plan are as follows.
– Configure the two hard disks on the server as RAID 1. Install the OS software and
U2000 project-related software and configure OS data.
– 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 iBMC, see A.
2.4 How to Solve iMana/iBMC 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.7 Formatting disks
(Huawei RH2288H V3 or Huawei RH5885H V3).
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/iBMC IP to Log In to a
Remote Huawei RH series rack server.
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.

NOTE
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 Reset or
Forced System 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.

operations:
a. After the server is started, press F11 or F3 (on Remote Keyboard). Wait about 3
minutes, the Please select boot device: window is displayed.
NOTE
If a dialog box asking you to enter a password displayed during startup, enter the required
password. The default password is 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.
b. Boot from a DVD driver.

n Boot from a virtual drive: Select Virtual DVD-ROM VM 1.1.0 225, and press
Enter.
n Boot from a physical drive: Select P5: Slimtype DVD A DS8ACSH, and
press Enter.
operations:
a. After the server is started, press F11 to access the Boot Manager window.
NOTE


n Boot from a virtual drive: Select Virtual DVD-ROM VM 1.1.0, and press
Enter.
n Boot from a physical drive: Select SATA P5 Slimtype DVD A DS8ACSH,
and press Enter.
Step 11 Select RAID Config V600 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 Disconnect.

NOTICE
If you don't click Disconnect, 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+R the moment you see Ctrl+R on the
screen. If Ctrl+R is not pressed, restart the system.
2. Press Ctrl+R as prompted to access the window of RAID card.

3. Click Start to access the WebBIOS window of the RAID card.
Place the cursor over all Drives by using up and down arrow keys on the keyboard and
display the information of Drives by using right arrow key on the keyboard.
– If log in to the Huawei RH2288H V3 server through iBMC, with eight hard disks:
If the BIOS window displays information as four Virtual Drives, Drive Group: 0
is RAID 1, Spanned Drive Group: 0 is RAID 10, Drive Group: 1 is RAID 0,
Drive Group: 2 is RAID 0, the RAID configurations are correct. Otherwise,
configure the RAID card again.
– If log in to the Huawei RH5885H V3 server through iBMC:
n With eight hard disks:
If the BIOS window displays information as four Virtual Drives, Drive
Group: 0 is RAID 1, Spanned Drive Group: 0 is RAID 10, Drive Group: 1
is RAID 0, Drive Group: 2 is RAID 0, the RAID configurations are correct.
Otherwise, configure the RAID card again.
n With two hard disks:
If the BIOS window displays information as one Virtual Drives, Drive
Group: 0 is RAID 1, the RAID configurations are correct. Otherwise,
configure the RAID card again.
Step 16 Restart the server.
1. Click on the toolbar which is right above Remote Virtual Console and select Reset
or Forced System Reset.
2. In the dialog box that is displayed, click Yes to restart the server.
----End

4.7.2 Configuring the RAID in Remote Mode (Huawei RH5885H

V3 or Huawei RH2288H V2, ISO)
Prerequisites
l The IP address of the iMana is available. For details about how to set the IP address of
the iMana, see 4.6.1.1 Configuring the iMana IP Address Through iMana
Management Interface (HUAWEI RH5885H V3 and HUAWEI RH2288H V2).
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 (if a disk array is configured,
configuration fails. If a disk array is available, ensure that two hard disks of the server
are available. For details, see A.2.8 Viewing Hard Disk Information (Huawei
RH5885H V3 or Huawei RH2288H V2).
Context
protection.
NOTICE
Ensure that the server has two or eight hard disks, otherwise, automatically configuring a
RAID using the ISO image file may fail. If the server has over eight hard disks, manually
configure a RAID using the controller card.
l If the delivered server is not connected to a disk array, ensure that the Huawei
RH5885H V3 or Huawei RH2288H V2 server for standard delivery have eight
300G hard disks, and the RAID level plan and partition plan are as follows.
and data.
– •The seventh hard disk functions as a standby disk that substitutes for a damaged
hard disk. It is configured as RAID 0.
l If the delivered server is connected to a disk array, ensure that the Huawei
RH5885H V3 server for standard delivery has two 300G hard disks, the disk array

NOTE
l If an Internet Explorer, two pointers, or Remote Virtual Console fault occurs in the iMana, see A.
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
installation will fail because the old data is not clear. For details, see A.2.6 Formatting disks
(Huawei RH5885H V3 or Huawei RH2288H V2).
Step 2 Save the ISO mirroring file to any directory on the PC or laptop.
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 Cold
Reset.

operations:
After the server is started, press F11 or F3 (on Remote Keyboard). Wait about 3
NOTE
If a dialog box asking you to enter a password displayed during startup, enter the required password.
The default password is Huawei12#$, if the password has been changed, enter the new password. If the
new password.
a. Due to different BIOS versions, the content display and operations on the Please
select boot device: page may be different, as follows:

n If the BIOS is a new version, the following page is displayed.
n If the BIOS is an old version, the following page is displayed.

n If the BIOS is a new version: Select HUAWEI DVD-ROM VM 1.1.0 225 to
start from the virtual drive and press Enter.
n If the BIOS is an old version: Select P5: TSSTcorp CDDVDW SN-208DB to
operations:
a. After the server is started, press F11. Wait about 3 minutes, the Boot Manager
window is displayed.
NOTE

b. Select HUAWEI DVD-ROM VM 1.1.0 to start from the virtual drive and press
Enter.
Step 11 Select RAID Config V600 and press Enter.
Step 12 On Huawei RH5885H V3 server, wait about 5 minutes. On Huawei RH2288H V2 server, wait
about 20 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 Disconnect.
NOTICE
If you don't click Disconnect, it will configure the RAID repeatedly.
Step 15 Check whether RAID configurations are correct.

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.

NOTE
Two pointers will be displayed. 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 Remote Virtual Console, click Ctrl+Alt+Shift. To exit from the single-pointer mode,
click and clear the Single Mouse check box.

– On Huawei RH2288H V2 server, the following window is displayed.
3. Click Start to access the WebBIOS window of the RAID card.

If a message displayed in the WebBIOS window indicates that the status of four virtual
drives is Optimal and shown in the following figure, the RAID configurations are
correct; otherwise, the RAID card needs to be re-configured.
– On Huawei RH2288H V2 server, with eight hard disks, the following window is
displayed.
– On Huawei RH5885H V3 server.

n With eight hard disks, the following window is displayed.

n With two hard disks, the following window is displayed.
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.
1. Click on the toolbar which is right above Remote Virtual Console and select Cold
Reset.
2. In the dialog box that is displayed, click Yes to restart the server.
----End

4.7.3 Configuring the RAID in Local Mode (IBM X3850 X5 and

IBM X3650 M3, Manually)
Prerequisites
l If configure the RAID in local mode, you must ensure that the server is connected to the
KVM.
l If configure the RAID in remote mode, you must ensure that the following preparations
are ready:
– The IP address of the IMM is available. For details about how to set the IP address
of the IMM, see 4.6.2.2 Configuring the IMM IP Address Through IMM
Management Interface (IBM X3850 X5 and IBM X3650 M3).
– A PC or laptop on which the Internet Explorer browser is installed is ready.
– Internet Explorer browsers do not support a proxy server.
– Ensure that eight hard disks of the server are available (if a disk array is configured,
configuration fails. For details, see A.3.9 Viewing Hard Disk Information in
Local Mode (IBM Server) or A.3.11 Viewing Hard Disk Informationin Remote
Mode (IBM X3850 X5 and IBM X3650 M3).
Context
l If the delivered server is not connected to a disk array, ensure that the IBM servers
(IBM X3850 X5 and IBM X3650 M3) for standard delivery have eight 300G hard
disks, and the RAID level plan and partition plan are as follows.
and data.
– •The seventh hard disk functions as a standby disk that substitutes for a damaged
hard disk. It is configured as RAID 0.
l If the delivered server is connected to a disk array, ensure that the IBM server
(IBM X3850 X5) for standard delivery has two 300G hard disks, the disk array

NOTE
l If an Internet Explorer, two pointers, or Remote Virtual Console fault occurs in the iMana, see A.
Procedure
installation will fail because the old data is not clear. For details, see A.3.12 Formatting
disks in Local Mode (IBM Server) or A.3.14 Formatting the disks in Remote Mode (IBM
X3850 X5 and IBM X3650 M3).
Step 2 Start or restart the IBM server.

l If you configure RAID in local mode, press the power button on the chassis panel of the
server to start the IBM server.
l If you configure RAID in remote mode, perform the following operations:
a. Log in to the server. For details, see 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).
b. Choose Tools > Power > Reboot from the main menu to reboot the system.
NOTE
n If a message asking you whether to continue is displayed, click Yes.

n If Reboot is unavailable, choose Tools > Power > On and then choose Tools > Power >
Reboot to restart the system.
Step 3 Perform the following operations to access the manual RAID configuration window:
1. After the system BIOS self-check is complete, the BIOS information about the RAID
card is displayed, as shown in the following figure.
2. Press Ctrl+H to access the WebBIOS configuration window for the RAID card. The
following dialog box is played.

3. Select the RAID card adapter to be configured and click Start to access the
configuration window. The following dialog box is played.
4. Click Configuration Wizard, Select New Configuration, as shown in the following

figure.

5. Click Next to access the RAID configuration wizard window. The following dialog box
is played.
6. Click Yes. The following dialog box is played.
7. Select Manual Configuration and click Next.

Step 4 Perform the following operations to add slots 0 to 7 to Drive Groups:

1. Select Slot 0 and Slot 1, and click Add To Array to add them to Drive Groups. Then
click Accept DG, as shown in the following figure.
click Accept DG to complete the Drive Group configuration.
click Accept DG to complete the Drive Group configuration.
4. Select Slot 6, and click Add To Array to add them to Drive Groups. Then click Accept
DG to complete the Drive Group configuration.
5. Select Slot 7, and click Add To Array to add them to Drive Groups. Then click Accept
DG to complete the Drive Group configuration.
Step 5 Add virtual drives.

1. Click Next. Select the two created Drive groups and click Add to SPAN to add DG to
Span.
2. Click Next.
3. Set Select Size as prompted. Keep default settings for other options, as shown in the
following figure.
NOTE
– If the number pad is unavailable, press Num Lock or use the main keyboard.
– If the Update Size button is unavailable, enter a value in Select Size as prompted.
4. Click Accept. The following dialog box is played.

6. Click Back to return to Span Definition. Then, add another virtual drive.
7. In Array With Free Space, select Drive Group:1 and Drive Group:2 and click Add to
SPAN to add DG to Span in the right pane.
8. Repeat Step 5.2 to Step 5.5 to configure Drive Group:1 and Drive Group:2 as a virtual
drive.
10. In Array With Free Space, select Drive Group:3 and click Add to SPAN to add DG to
Span in the right pane.
11. Repeat Step 5.2 to Step 5.5 to configure Drive Group:3 as a virtual drive.

14. Repeat Step 5.2 to Step 5.5 to configure Drive Group:4 as a virtual drive.
15. Add Virtual Drives by using the default settings for all parameters. Click Next. The
17. Click Yes.

18. Optional: If the following dialog box is displayed, click Cancel.

19. The following dialog is played, click Yes to initialize the created virtual drives.
20. Complete the RAID 10 configuration. Click Home and check that the status of the
virtual drives is Optimal and the status of the four hard disks is Online, as shown in the
following figure.

Step 6 Complete the RAID configuration. Click Home and check that the status of the four virtual
drives is Optimal and the status of the eight hard disks is Online, as shown in the following
figure.
Step 7 After the configuration is complete, click Exit. The Exit Application dialog box is displayed.

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.
----End
4.7.4 Configuring the RAID in Local Mode (IBM X3650 M4,

Manually)
Prerequisites
l If configure the RAID in local mode, you must ensure that the server is connected to the
KVM.
l If configure the RAID in remote mode, you must ensure that the following preparations
are ready:
– The IP address of the IMM is available. For details about how to set the IP address
of the IMM, see 4.6.2.1 Configuring the IMM IP Address Through IMM
Management Interface(IBM X3650 M4).
– Ensure that eight hard disks of the server are available. Otherwise, RAID
configuration fails. For details, see A.3.9 Viewing Hard Disk Information in
Local Mode (IBM Server) or A.3.10 Viewing Hard Disk Informationin Remote
Mode (IBM X3650 M4).

Context
If the delivered server is not connected to a disk array, ensure that the IBM servers
(IBM X3650 M4) for standard delivery have eight 300G hard disks, and the RAID level
l The first and second hard disks are configured as RAID 1 for installing OS software and
data.
l The third, fourth, fifth, and sixth hard disks are configured as RAID 10 for storing
l •The seventh hard disk functions as a standby disk that substitutes for a damaged hard
disk. It is configured as RAID 0.
l The eighth hard disk is configured as RAID 0 to back up the database.
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.
Procedure
installation will fail because the old data is not clear. For details, see A.3.12 Formatting
disks in Local Mode (IBM Server) orA.3.13 Formatting the disks in Remote Mode (IBM
X3650 M4).
Step 2 Start or restart the IBM server.

l If you configure RAID in local mode, press the power button on the chassis panel of the
server to start the IBM server.
l If you configure RAID in remote mode, perform the following operations:
a. Log in to the server. For details, see A.3.2 How do I use an IMM IP address to
remotely log in to an IBM server (IBM X3650 M4).
b. Choose Tools > Power > Reboot from the main menu to reboot the system.
NOTE
n If a message asking you whether to continue is displayed, click Yes.

n If Reboot is unavailable, choose Tools > Power > On and then choose Tools > Power >
Step 3 Perform the following operations to access the manual RAID configuration window:
1. After the system BIOS self-check is complete, the BIOS information about the RAID
card is displayed.

2. Press Ctrl+H to access the WebBIOS configuration window for the RAID card.
3. Select the RAID card adapter to be configured and click Start to access the
configuration window.
4. Click Configuration Wizard. The following dialog box is played.

5. Select New Configuration and click Next to access the RAID configuration wizard
window. The following dialog box is played.
7. Select Manual Configuration and click Next.

Step 4 Perform the following operations to add slots 0 to 7 to Drive Groups:
1. Select Slot 0 and Slot 1, and click Add To Array to add them to Drive Groups, as
shown in the following figure.

2. Click Accept DG, click Next. The following dialog box is played.
3. Click Yes.
4. Select Slot 2 and Slot 3, and click Add To Array to add them to Drive Groups. Click
Accept DG to complete the Drive Groups configuration. Click Next.
5. Click Yes.
6. Select Slot 4 and Slot 5, and click Add To Array to add them to Drive Groups. Click
Accept DG to complete the Drive Groups configuration. Click Next.
7. Click Yes.
8. Select Slot 6, and click Add To Array to add them to Drive Groups. Click Accept DG
to complete the Drive Groups configuration. Click Next.
9. Click Yes.
10. Select Slot 6, and click Add To Array to add them to Drive Groups. Click Accept DG
to complete the Drive Groups configuration. Click Next.
11. Click Yes. Click Next.
Step 5 Add virtual drives.

1. Select the two created drive group and click Add to SPAN to add DG to Span, as shown
in the following figure.

2. Click Next.
3. Click Update Size as prompted. Keep default settings for other options, as shown in the
following figure.
NOTE
If the number pad is unavailable, press Num Lock or use the main keyboard.
NOTE
If the Update Size button is unavailable, enter a value in Select Size as prompted.

6. Click Back to return to Span Definition.

9. Repeat Step 5.2 to Step 5.5.
16. Add Virtual Drives by using the default settings for all parameters. Click Next. The

18. Click Yes.

19. Optional: If the following dialog box is displayed. Click Cancel.
20. The following dialog box is played. Click Yes to initialize the created virtual drives.

Step 6 Complete the RAID configuration. Click Home. Return to the Home window and check that
the status of the four virtual drives is Optimal and the status of the eight hard disks is Online.
Step 7 After the configuration is complete, click Exit. The Exit Application dialog box is displayed.
Step 9 Choose Tools > Power > Reboot from the main menu to reboot the IBM server.

NOTE

restart the system.
----End
4.8 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/iBMC 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.
4.8.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\iBMC is available. In Huawei RH5885H V3 or Huawei
RH2288H V2 server, for details about how to set the IP address of the iMana, see 4.6.1.1
Configuring the iMana IP Address Through iMana Management Interface
(HUAWEI RH5885H V3 and HUAWEI RH2288H V2). In Huawei RH2288H V3
server and Huawei RH5885H V3 server, for details about how to set the IP address of
the iBMC, see 4.6.1.2 Configuring the iBMC IP Address Through iBMC
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_sles11_x64_dvd1 or ISO image
file of the quick installation DVD U2000version_server_os_sles11_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/iBMC Problems.
Procedure
Step 1 Insert the quick installation DVD-ROM (Terminal Physical Software, iManager U2000,
iManager U2000 version_server_sles, Physical Software Package For Linux Network
Management System, CD) 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 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 the drive has successfully connected to the server, the Connect changes to
Disconnect.
l If the ISO file is used, perform the following operations:
a. In the virtual disk dialog box, select Image File and click Browse.
b. In the Open dialog box, select the ISO file of the quick RAID configuration DVD
U2000version_server_os_sles11_x64_dvd1.iso and click Open.
c. In the virtual disk dialog box, click Connect. If the virtual drive has successfully
connected to the server, the Connect changes to Disconnect.
Step 5 Click on the toolbar which is right above Remote Virtual Console and select Reset,
Cold Reset or Forced System Reset.
operations:
After the server is started, press F11 or F3 (on Remote Keyboard). Wait about 3
NOTE
If a dialog box asking you to enter a password displayed during startup, enter the required password.
The default password is Huawei12#$, if the password has been changed, enter the new password. If the
new password.
a. Due to different BIOS versions, the content display and operations on the Please
select boot device: page may be different, as follows:
n If the BIOS is a new version, the following page is displayed.

n If the BIOS is an old version, the following page is displayed.

n If the BIOS is a new version: Select HUAWEI DVD-ROM VM 1.1.0 225 to
n If the BIOS is an old version: Select P5: TSSTcorp CDDVDW SN-208DB to
operations:
a. After the server is started, press F11. Wait about 3 minutes, the Boot Manager
NOTE
n Boot from a virtual drive: Select HUAWEI DVD-ROM VM 1.1.0, and press
Enter.
n Boot from a physical drive: Select SATA P5 TSSTcorp CDDVDW
SN-208DB, and press Enter.
operations:
NOTE


n Boot from a virtual drive: Select Virtual DVD-ROM VM 1.1.0 225, and press
Enter.
n Boot from a physical drive: Select P5: Slimtype DVD A DS8ACSH, and
press Enter.
operations:
NOTE
n Boot from a virtual drive: Select Virtual DVD-ROM VM 1.1.0, and press
Enter.
n Boot from a physical drive: Select SATA P5 Slimtype DVD A DS8ACSH,
and press Enter.
Step 8 Wait about two minutes, the system restarts and the SUSE Linux Enterprise Server window
is displayed.
NOTICE
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--Single-Server 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
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.1.1

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.
– On the desktop, right-click in the blank area and choose Open in Terminal from the shortcut
menu to access the CLI.
– Run the following command to view the OS version:
If the following information is displayed, the SUSE Linux version is correct:
VERSION = 11
PATCHLEVEL = 3
– Run the following command to view the OS kernel version:
# uname -rv
The information similar to 3.0.101-0.47.105-default is displayed. Here, 3.0.101-0.47.105-
default indicates the kernel version of the OS.
If the kernel version is 3.0.101-0.47.105-default , 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 Settings.
3. In the Network Settings dialog box, select Overview.
4. Select the network port whose Device is eth0 and click Edit.
NOTE
– Select the network port whose Device is eth0 and connect network interfaces identified as 1 to
the network.
– 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 Card Setup dialog box, select Address.
6. Select Statically assigned IP Address. Set system IP address and subnet mask, and
click Next.
NOTICE
Hostname can not be null.

7. Add a static route.

NOTE
A route must be added if a user needs to connect to the network. A static route is recommended.
– If network connection security is highly required, add a static route and allow users on some
IP network segments to connect to the server.
– 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.4 How to manually Add the Default Route
(SUSE Linux).
a. In the Network Settings window, select Routing.

b. Click Add in the Routing Table area. The following dialog box for configuring a
static route is displayed.
NOTE
Set the following parameters:
n Destination: An IP address on the network segment of the computer connected to the
U2000 server.
n Device: use the default value. The default value is eth0.
n Gateway: network management IP address for the network on which the U2000 server
is located.
n Netmask: subnet mask of the network segment on which the computer connected to the
U2000 server is located.
Leave other parameters empty.
c. Click OK.
d. Click OK.
8. 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.6 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.
# shutdown -r now
----End

Follow-up Procedure
If a host name needs to be changed, enter the new host name during system preconfiguration.
4.8.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
l The IP address of the IMM is available. For details about how to set the IP address of the
IMM, see 4.6.2.1 Configuring the IMM IP Address Through IMM Management
Interface(IBM X3650 M4).
file of the quick installation DVD U2000version_server_os_sles11_x64_dvd1.iso must
be ready.
been planned.
Context
NOTICE
Procedure
Step 2 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
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

Step 4 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.
l If a message is displayed indicating that the application is prohibited to run, choose Start > Control
Panel and click Java. In the Java Control Panel dialog box, click the Security tab, Edit Site List,
and Add, enter an iMana/iBMC IP address, such as http://192.168.2.100, and click OK. Click OK,
restart the IE Explorer, and log in to iMana/iBMC again.
Step 5 The desktop windows Video Viewer is displayed. Choose Tools > Launch Virtual Media
from the main menu. The virtual media window is displayed.
Step 6 Load the installation DVD-ROM or ISO mirroring file. 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 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.
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.
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.
Step 11 Use arrow keys to select Legacy Only and press Enter. Then use arrow keys to select
CD/DVD and press Enter to start the system from the DVD-ROM.
is displayed.
NOTICE

NOTE
l If the operation fails to be performed using the up and down arrow keys, choose Macros > Soft Key >
Down, select Installation--Single-Server 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.
again.
VERSION = 11
PATCHLEVEL = 3
# uname -rv

# yast2
NOTE
the network.

click Next.
NOTICE

NOTE
(SUSE Linux).
NOTE
U2000 server.
is located.
c. Click OK.
d. Click OK.
NOTE

the system.
# shutdown -r now
----End
Follow-up Procedure
4.8.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
l The IP address of the IMM is available. For details about how to set the IP address of the
IMM, see 4.6.2.2 Configuring the IMM IP Address Through IMM Management
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.
file of the quick installation DVD U2000version_server_os_sles11_x64_dvd1.iso must
be ready.
been planned.
Context
NOTICE
Procedure

NOTE
IBM Server.
NOTE

M3).
NOTE
Step 5 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
trust this site.
solve the problem.
l If Use the ActiveX Client with Microsoft Internet Explorer is unavailable, just click Start
be displayed.
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.

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.
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.
Step 8 Click Mount Selected to mount the SUSE Linux operating system DVD-ROM file to the
IMM.
Step 9 Choose Tools > Power > Reboot from the main menu to reboot the system.
NOTE

restart the system.
Step 10 After the IBM System X window is displayed, wait for about 2 minutes until <F12> Select

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 Rom and press Enter to start the system from the DVD-
ROM.
is displayed.
NOTICE

NOTE
l If the operation fails to be performed using the up and down arrow keys, choose Macros > Soft Key >
Down, select Installation--Single-Server 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.
l When the Video Viewer window is used, contents outside the Video Viewer window cannot be
copied and pasted into the Video Viewer window.
again.
VERSION = 11
PATCHLEVEL = 3
# uname -rv

# yast2
NOTE
the network.

click Next.
NOTICE

NOTE
(SUSE Linux).
NOTE
U2000 server.
is located.
c. Click OK.
d. Click OK.
NOTE

the system.
# shutdown -r now
----End
Follow-up Procedure
4.8.4 Locally Installing the SUSE Linux Operating System (IBM

Server, DVD)
If the IBM 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_sles11_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
Procedure
Step 1 Insert the operating system DVD-ROM (Terminal Physical Software, iManager U2000,
Management System, CD) to the IBM server drive.
Step 3 After the IBM System X window is displayed, wait for about 2 minutes until <F12> Select

Step 4 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 5 Start the system from the DVD-ROM.
l For IBM X3850 X5 or IBM X3650 M3, use arrow keys to select CD/DVD and press
Enter to start the system from the DVD-ROM. See the following figure:
l For IBM X3650 M4, use arrow keys to select Legacy Only and press Enter. Then use
arrow keys to select CD/DVD and press Enter to start the system from the DVD-ROM.
See the following figure:

is displayed.
NOTICE

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

VERSION = 11
PATCHLEVEL = 3

# 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
NOTE
the network.
click Next.
NOTICE

NOTE
(SUSE Linux).


NOTE
U2000 server.
is located.
c. Click OK.
d. Click OK.
NOTE
the system.
# shutdown -r now
----End
Follow-up Procedure
4.8.5 Locally Installing the SUSE Linux Operating System

(Huawei RH series rack server, DVD)
If the Huawei RH series rack 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_sles11_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
Procedure
Step 1 Insert the operating system DVD-ROM (Terminal Physical Software, iManager U2000,
Management System, CD) to the Huawei RH series rack server drive.
operations:
NOTE
b. Select P5: TSSTcorp CDDVDW SN-208DB to start from the drive and press
Enter.
operations:
b. Select SATA P5 TSSTcorp CDDVDW SN-208DB to start from the virtual drive
and press Enter.
operations:
b. Select P5: Slimtype DVD A DS8ACSH to start from the virtual drive and press
Enter.
operations:
b. Select SATA P5 Slimtype DVD A DS8ACSH 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
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
again.
VERSION = 11
PATCHLEVEL = 3
# uname -rv

# yast2
NOTE
the network.
click Next.
NOTICE


NOTE
(SUSE Linux).

NOTE
U2000 server.
is located.
c. Click OK.
d. Click OK.
NOTE
the system.
# shutdown -r now
----End

Follow-up Procedure
4.9 Installing the U2000 Software

This topic describes how to start the U2000 installation.
4.9.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 packages and the PGP verification files of the software
file in the .asc format need 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 Checking Required Software.
l Make sure that the SFTP (more secure, recommended) services are enabled. For details,
see A.1.2 How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS.
Procedure
Step 1 Perform the following operations to upload software packages and the mappings PGP
verification files (the file format is .asc) to the /opt/install path on the server.
1. Log in to the SUSE Linux OS as user root through remote login software or the
Windows OS CLI.
2. Run the following command to create the /opt/install directory:
# mkdir /opt/install
NOTICE
If the /opt/install directory already exists, ensure that it is empty; otherwise, the newly
installed U2000 may be abnormal.
3. Use SFTP to upload the software packages and the mappings PGP verification files (the
file format is .asc) to the /opt/install directory on the server as the root user. FileZilla
tool is recommended to transfer files. For details about how to use FileZilla to transfer
files, see A.1.27 How to Use the FileZilla to Transfer Files by SFTP.

NOTE
The installation packages to be uploaded are as follows:
1. Database software (Mandatory): U2000version_server_db_linux_sybase.tar
2. Security enhancement software SetSuse (Mandatory):
U2000version_VPPSetSuse11V300R003C22SPC200.tar
3. Preconfigured component(Mandatory):U2000version_server_ICMR_sles_x64.tar
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 (Select it if you want to manage transport or PTN
equipment): U2000version_server_nmstrans_sles_x64.7z
7. Components of the IP domain (Select it if you want to manage routers, switches, or security
equipment): U2000version_server_nmsip_sles_x64.7z
8. Components of the access domain (Select it if you want to manage access equipment):
U2000version_server_nmsaccess_sles_x64.7z
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.
Step 2 Use the PGPverify software to verify the uploaded software packages.
NOTE
Download the latest version.

1. Download and decompress the PGPverify tool.
– For carrier: visit http://support.huawei.com/carrier/digitalSignatureAction to download the
OpenPGP Signature Verification Guide package and decompress it to obtain the OpenPGP
Signature Verification Guide.pdf, VerificationTools.zip and KEYS. Continue to decompress the
VerificationTools.zip package in the current folder.
– For enterprise: visit http://support.huawei.com/enterprise/en/tool/software-digital-signature-
validation-tool--pgp-verify--TL1000000054 to download the OpenPGP Signature Verification
Guide.pdf, VerificationTools.zip and KEYS and decompress the VerificationTools.zip package.
2. Go to the VerificationTools folder that is generated after decompression and obtain the PGPVerify
software PGPVerify-x86_64.tar.gz for Linux OS in linux\X86\bit64\PGPVerify TOOL folder.
3. KEYS is the public key file.
1. Use SFTP as the root user to upload the obtained PGPverify software PGPVerify-
x86_64.tar.gz and public key file KEYS to the /opt directory on the server. For details
about the SFTP transfer method, see A.1.27 How to Use the FileZilla to Transfer Files
by SFTP.
2. Run the following commands to verify the installation software packages:
# cd /opt
# tar xvfz PGPVerify-x86_64.tar.gz
# ./PGPVerify -k KEYS -d install
NOTE
l For a certain file, if the command output does not contain "WARN" or "FAIL", the signature file is valid.
l If a version has multiple signature files to be verified, the version is secure only when the verification
results of all files are "PASS". If the verification results contain "WARN" or "FAIL", the verification is
not passed and security risks exist. In that event, re-download the software packages.
Step 3 Run the following commands to switch to the directory where the software packages are
stored, and run the tar command to decompress Preconfigured component on the server.
# cd /opt/install
# tar xvf U2000version_server_ICMR_sles_x64.tar

NOTE
Only the preconfigured component package needs to be decompressed here. The .7z packages will be
decompressed automatically during follow-up system preconfiguration.
----End
4.9.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, modify network settings for the system.
Prerequisites
l Installation engineers are familiar with the IP address planning scheme of the U2000. For
more information, see 4.3.1.1 Collecting Installation Information (Single-Server
System).
l The hardware is properly connected. For more information, see 4.4 Checking Hardware
Connections.
l If the U2000 is installed using software packages, the installation software must have
been prepared. For more information, see 4.9.1 Preparing Software Packages.
l The SUSE Linux version must be SUSE Linux Enterprise Server 11 SP3, and the OS
kernel version must be 3.0.101-0.47.105-default . For more information, see
Configuration requirements.
l Ensure that the current OS does not use the ID of a U2000 user. For details, see A.5.13
How to Check and Change an OS User ID.
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.
Context
The following operations are involved:
l Install OSSICMR.
l Install database.
l Modify the network settings of the system: You can modify the network settings of the
system, including the system IP address, the system host name, the subnet mask of the
system IP address, the default gateway IP address, and choose whether to configure
bond.

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 the system is preconfigured, the command association function using the up and down arrows
is disabled in the Linux operating system.
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 Optional: If the U2000 is installed using the software package, run the following commands
to switch to the directory where OSSICMR is located and assign permissions.
# cd /opt/install/OSSICMR
# chmod -R 750 /opt/install/OSSICMR
Step 3 Optional: If the disk array 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
configurations:
l 12 x 600 GB OceanStor 5500 V3
If a disk array whose configurations are out of the preceding range, contact Huawei technical support
engineers.
To configure the OceanStor 5500 V3 disk array using the automatic configuration script,
perform the following operations:
1. Switch to the directory where the AutoSetup5500.sh file is located. Execute the
AutoSetup5500.sh file to start OceanStor 5500 V3 disk array configuration.
– If the U2000 is installed using the installation package, run the following
commands:
# cd /opt/install/OSSICMR/bin/array
# ./AutoSetup5500.sh
– If the U2000 is installed using the installation DVD, run the following commands:

i. Insert the installation DVD of the U2000 server (Terminal Physical Software,
iManager U2000, iManager U2000 version_server_sles, Physical Software
Package For Linux Network Management System, CD 4/4) to the DVD-ROM
drive.
ii. Run the following commands and execute the AutoSetup5500.sh file to start
the OceanStor 5500 V3 disk array configuration.
# bash
# cd /media/CDROM/OSSICMR/bin/array
# . ./AutoSetup5500.sh
NOTE
○ You must run the bash command in the root directory before navigating to the
OSSICMR directory. Otherwise, the DVD-ROM cannot automatically eject the
DVD.
○ There must be a space between the dot (.) and the command ./AutoSetup5500.sh.

============= Excute this script at: Mon Dec 28 13:04:09 CST 2015
=============
------------------------------------------------------------------------------
-
--------------- Configure OceanStor 5500 V3 DiskArray
---------------
------------------ !!WARNING!! !!WARNING!! !!WARNING!!
------------------
------------ This script will destroy the data of the array!!
-----------
------------------------------------------------------------------------------
-
Are you sure to continue? [y/n]:
2. Enter y and press Enter.

Please enter the IP address of array controller:
3. Enter the IP address of the primary controller of the disk array, such as 10.9.1.10 and
press Enter.
Please enter the admin user password of the array:
4. Enter the user password of the disk array and press Enter. The default password is
Admin@storage. If the disk array is preinstalled, the password is Changeme_123. (If
the password has already been changed, enter the new password. If the password is never
changed, refer 4.6.3.1 Setting the SC IP Address for the OceanStor 5500 V3 Disk
Array to change it regularly and keep it privately.)
===========================================
Installing the disk array...
.............................................
.............................................
.............................................
.............................................
.............................................
.............................................
.............................................
.............................................
.............................................
.............................................
The disk array has not been completed started. The system will automatically
retry 10 seconds later.
Disk array installed 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 5500 V3 disk array. For more
information, see H.1 Configuring the OceanStor 5500 V3 Disk Array Using the OceanStor
DeviceManager.
5. Run the following commands to restart the OS:
# shutdown -r now
NOTE
The automatic configuration scripts of OSSICMR support only the disk arrays with the following
configurations:
l 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. Switch to the directory where the AutoSetupS3900.sh file is located. Execute the
AutoSetupS3900.sh file to start OceanStor S3900 disk array configuration.
– If the U2000 is installed using the installation package, run the following
commands:
# cd /opt/install/OSSICMR/bin/array
# ./AutoSetupS3900.sh
– If the U2000 is installed using the installation DVD, run the following commands:
i. Insert the installation DVD of the U2000 server (Terminal Physical Software,
iManager U2000, iManager U2000 version_server_sles, Physical Software
Package For Linux Network Management System, CD 4/4) to the DVD-ROM
drive.
ii. Run the following commands and execute the AutoSetupS3900.sh file to start
the OceanStor S3900 disk array configuration.
# bash
# cd /media/CDROM/OSSICMR/bin/array
# . ./AutoSetupS3900.sh
NOTE
○ You must run the bash command in the root directory before navigating to the
OSSICMR directory. Otherwise, the DVD-ROM cannot automatically eject the
DVD.
○ There must be a space between the dot (.) and the command ./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 10.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.2 Configuring the OceanStor S3900 Disk Array by Using the ISM.
# 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 in 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.
l If the U2000 is installed using the installation package, run the following commands:
# ./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]:

l If the U2000 is installed using the installation DVD, run the following commands:
a. Insert the installation DVD of the U2000 server (Terminal Physical Software,
iManager U2000, iManager U2000 version_server_sles, Physical Software Package
For Linux Network Management System, CD 4/4) to the DVD-ROM drive.
b. Run the following commands and execute the install.sh file to start OSSICMR to
perform system configuration.
# bash
# cd /media/CDROM/OSSICMR/
# . ./install.sh

Copying the OSS Engineering directory to /opt/install...
> Finished
Can not find database installation package.

Please insert the database installation DVD.
NOTE
n You must run the bash command in the root directory before navigating to the
OSSICMR directory. Otherwise, the DVD-ROM cannot automatically eject the DVD.
n There must be a space between the dot (.) and the command ./install.sh.
c. The DVD-ROM will eject the installation DVD for the U2000 server software after
configuration is complete. Insert the installation DVD for the database software
(Terminal Physical Software, iManager U2000, iManager U2000
version_server_sles, Physical Software Package For Linux Network Management
System, CD 3/4) into the server DVD-ROM, and then press Enter.
Deal with Database installation file to /opt/install ...
> Finish
Skipping Veritas software for this single-server system...
............
======OS's language======
The current OS language is English, choose a correct language to

set OS:
1.Chinese
2.English
please select[2]:
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 not been installed on the system, enter the U2000 installation path.
==== OSS path =======
Enter the OSS path in which to install the OSS software.
default directory[/opt/oss]:
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]:
– To reuse the database, perform the following operations:
NOTE
Before perform the following operations make sure the database is running, or start a new Putty
session and refer to A.4.1.2 How to Start the Sybase Database Service to start the database.
i. If the database must be reused, enter 1 and press Enter.
Please input the database administrator account[sa] :
ii. 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.
iii. 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 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 =======
default directory[/opt/oss]:
NOTE
n 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
n After the database file is deleted, ensure that the /opt/sybase directory contains only one
empty /opt/sybase/data folder.
n After the database file is deleted, you do not need to install the Sybase again. The Sybase
will be automatically installed when the U2000 is installed.
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.

======= Network Configuration Mode =======
Do you want to configure the OS network?

If yes, delete the original network configurations and reconfigure the
network.
If no, the original network configurations will be reused.
1. Yes
2. No
Select[2]:
Step 9 According to the conditions at your site, determine if the system network needs to be
reconfigured.
NOTE
System network settings include: the system IP address, the system host name, the subnet mask of the
system IP address, the default gateway IP address, and bond. 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.
The displayed configuration result depends on the configurations of the disk array and the configurations
of the system network. Watch out for failed configurations.
l If the system network does not need to be reconfigured, do as following.
NOTE
If the system network is not reconfigured, bond cannot be configured and redundancy protection is
not available between network interfaces.
a. Enter 2 and press Enter.

...
Modifying the system
parameters.................................................
Modifying system network
configuration..........................................
Mounting
diskarray.............................................................
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_20130409223933.log
NOTE
n If All operations defined in the task flow have been completed is displayed, it
indicates that the system is successfully configured. If the system configuration fails,
send the operation log to Huawei engineers for fault locating.
n When one or more of the following conditions are met, the OS automatically restarts.
If the OS does not automatically restart, restart is not required in this scenario. You can
directly perform the subsequent operations.
○ The OS language is changed.
○ A disk array is connected.
○ The system network settings are changed, including reusing system network
settings.
l If the system network needs to be reconfigured, do as following.
NOTE
If the system network is reconfigured, bond can be configured and redundancy protection is
available between network interfaces.
a. Enter 1 and press Enter.
======= Host Name =======
Host name is the only ID of the host. It is the name used

to indicate the host in the network. Host name for each host is unique
in the network.
Press Enter to use the current host name, or enter a new host name. The
new host name will take into effect after the host reboots.
Please see the user manual for legal host name detail.
Enter[linux]:
b. Enter the planned host name. Then, press Enter.

======= IP Address of the Master NIC of bond =======
Enter an IP address for the master NIC.

You need to configure the IP address for the NIC before the server can
communicate with other devices in the network.
The IP address must be unique and not be occupied by any other equipment
in the network. Otherwise, the IP address conflict may cause abnormal
communication.
Press Enter to use the default value (The default is the current IP

address. If no default is displayed, you need to enter a valid IP

address.)
Enter[10.9.1.1]:
c. Enter the planned system IP address. Then, press Enter.

======= Subnet Mask of the Master NIC =======
Enter a subnet mask for the master NIC.

The subnet mask is a 32-digit value. It defines the network ID and the
host ID. A network can be divided into several subnet by subnet masks.
The subnet masks of different hosts in one subnet are consistent.
Press Enter to use the default value. (The default is the subnet mask
configured for the current system. If no default is displayed, you need
to enter a valid subnet mask.)
Enter[255.255.255.0]:
d. Enter the planned subnet mask for the system IP address. Then, press Enter.
======= Configure 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. eth0
2. eth1
3. eth2
4. eth3
5. eth4
6. eth5
7. eth6
8. eth7
Please select nic or Press Enter to use the default

value[1,2]:
NOTE
n As the interface eth0 has been connected to the network and the system IP address has been
set during the installation of the OS, select another network interface. Recommended that the
selected network interface and eth0 are not located on the same NIC before connecting the
interface to the network.
n View information about the connection of the physical network interface of the server. For
details, see A.3.8 Mappings Between Physical and Logical Network Interfaces on an IBM
Server Running SUSE Linux.
n 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.
e. Enter NIC IDs. The NIC IDs need to be separated by comma. Then press Enter.
Please confirm the following configurations...
******************************************************************
system IP
10.9.1.1

system hostname
linux
system netmask
255.255.255.0
bond member NIC
eth0 eth1
******************************************************************
Enter 'y' to apply these values and proceed to the next step, or 'n' to
return to make any changes (y/n):
>
f. Enter y after you confirm that the information is correct and press Enter.
...
parameters..............................................
configuration............................................
The configurations take effect only after the system is restarted. The
system will restart.
...
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_VPPSetSuse11V300R003C22SPC200.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.
g. After the configuration is finished, the OS restarts automatically and after the restart
is completed, the installation program automatically runs.It takes approximately 5
to 8 minutes to restart the system.
NOTE
n During the wait, run the ping system IP address command to check whether the server
is restarted. If the system IP address can be pinged, the server is successfully restarted.
n When one or more of the following conditions are met, the OS automatically restarts.
If the OS does not automatically restart, restart is not required in this scenario. You can
directly perform the subsequent operations.
○ The OS language is changed.
○ A disk array is connected.
○ The system network settings are changed, including reusing system network
settings.
h. After the OS restarts, log in to the OS as user root.
i. To check the installation progress after the system restarts, run the following
command. If All operations defined in the task flow have been completed. is
displayed, the configuration is successful. It takes approximately 60 minutes to
complete the configuration.
# tail -f /var/ICMR/install.log
...
parameters.................................................
configuration..........................................

Mounting
diskarray.............................................................
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_20130409223933.log
Press Ctrl+C to stop viewing the log.

NOTE
n If All operations defined in the task flow have been completed is displayed, the
configuration is successful.
n If Failed is displayed, the configuration fails. Save the operation logs and contact
Huawei engineers for fault location.
n If no Checking the system info information, after the configuration is complete, run the
command cat /var/ICMR/install.log to view all contents of install.log.
----End
Follow-up Procedure
If the OS must be reconfigured because of incorrect parameter settings (such as incorrect IP
addresses), perform the following operations:
1. Press Ctrl+C to stop the program from configuring the OS.
2. Run the following commands to reconfigure the OS:
# ./install.sh -r
For more information, refer to the procedures described above.
4.9.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.
4.9.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 installationon 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
U2000 software and engineering-related software stores at /opt directory, 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.4.1.3 How to Verify That the Sybase Database Is
Running. If the database is not started, refer to A.4.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 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.
l During the U2000 installation, the FTP service will be disabled for the root and ossuser users. To
transfer files as the root or ossuser user after installing the U2000, you need to use the SFTP
service.
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 in 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.
NOTE
l If a dialog box is displayed prompting you to select the directory of the installation package, enter
the directory where the installation files were uploaded to the server. For example, /opt/install.
l In a Chinese OS, the language can be set to Chinese or English. In an English OS, the language can
be set only to English.
Step 6 Select the language according to the conditions at your site, such as English. 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.
NOTICE
update it periodically, and save it properly.
Parameter Description
Server Address The default value is 127.0.0.1.
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.4.2.4 How to Change the
sa User Password for the Sybase Database If the
U2000 Is Not Installed.
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:
– 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 must be different from the user name or the
user name in reverse order and cannot contain the complete
user name (case-insensitive).
The default value is Changeme_123.

OSS Database User Password Set a new password for OSS database user. For example,
Changeme_123.
NOTE
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 special character ~@#^*-_+[{}]:./?
Other special characters are not supported. Do not include
other special characters, such as ()|<>&`!$\"%'=;,space
in passwords.
l The password must be different from the user name or the
user name in reverse order and cannot contain the complete
user name (case-insensitive).
NOTE
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 7 Click Next. The Configure Server dialog box will be displayed.
NOTE
Server IP Address is set to the U2000's application IP address, which is used for external services, such
as communication between the U2000 server and clients as well as communication between NEs.

Step 8 Click Next. The Select Domain dialog box will be displayed.
NOTE
This section assumes that the access, IP, and transport packages are uploaded and decompressed. If only
the access package is uploaded and decompressed, the page will display Access domain alone. Select the
domain need to be deployed based on the managed devices. Selecting all the displayed domains is
recommended. To add other domains, upload and decompress the corresponding packages and perform
the installation again. Software packages for the transport and IP components must be selected so as to
manage PTN 6900 and PTN 7900 series NEs.
Step 9 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. Select the Version Style as required.
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 10 Click Next. The installation information will be displayed.
Step 11 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.
6.1 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 12 Click Finish to complete the U2000 installation.

Step 13 Run the following commands to restart the OS. It takes approximately 5 to 8 minutes to
restart the system.
# shutdown -r now
Step 14 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.4.2.8 How to Create a Replacement User for the Sybase
Database Administrator sa User.
----End
4.9.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. The
U2000 software and engineering-related software stores at /opt directory. 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.4.1.3 How to Verify That the Sybase Database Is
Running. If the database is not started, refer to A.4.1.2 How to Start the Sybase
Database Service to start the database.
Context
NOTICE
During the U2000 installation, the FTP service will be disabled for the root and ossuser
users. To transfer files as the root or ossuser user after installing the U2000, you need to use
the SFTP service.

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:
a. Right-click the title bar of the CLI of the PuTTY and choose Change Settings from
the shortcut menu.
b. 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:
a. Right-click the title bar of the CLI and choose Properties from the shortcut menu.
The Properties dialog box will be displayed.
b. On the Option tab page, set Buffer Size to 100 in the Command History area.
c. 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.

Step 7 Enter n.
===============< Configure Database >===============
Server Address:[127.0.0.1]:
Server Name:[DBSVR]
Server Port:[4100]
Administrator Name:[sa]:
Step 8 Configure the information about the database service.
NOTICE
update it periodically, and save it properly.
Server Address:[127.0.0.1]:
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.4.2.4 How to Change the sa User Password for the
Sybase Database If the U2000 Is Not Installed.

NOTE
The database administrator 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:
n At least one lower-case letter
n At least one upper-case letter
n At least one digit
n At least one special character ~@#^*-_+[{}]:./?
Other special characters are not supported. Do not include other special characters, such as
()|<>&`!$\"%'=;,space in passwords.
– The password must be different from the user name or the user name in reverse order and cannot
contain the complete user name (case-insensitive).
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.
Other special characters are not supported. Do not include other special
characters, such as ()|<>&`!$\"%'=;,space in passwords.
– The password must be different from the user name or the user name in reverse
order and cannot contain the complete user name (case-insensitive).
===============< Deploy Server >===============
The system partition of the OS is not recommended.Server IP Address:[0:10.9.1.1,
0]:
NOTE
Server IP Address is set to the U2000's application IP address, which is used for external services, such
as communication between the U2000 server and clients as well as communication between NEs.
Step 10 Confirm the Server IP Address and then press Enter.

===============< Deploy Server >===============
The system partition of the OS is not recommended.Server IP Address:[0:10.9.1.1,
0]:
Installation Path:[/opt/oss]

===============< Select Deployment Domain >===============
[1:Access domain, 2:IP domain, 3:Transport domain, 1,2,3]:

NOTE
This section assumes that the access, IP, and transport packages are uploaded and decompressed. If only
the access package is uploaded and decompressed, the page will display Access domain alone. Select the
domain need to be deployed based on the managed devices. Selecting all the displayed domains is
recommended. To add other domains, upload and decompress the corresponding packages and perform
the installation again. Software packages for the transport and IP components must be selected so as to
manage PTN 6900 and PTN 7900 series NEs.
Step 12 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, the Version Style dialog
box is displayed. Select the Version Style as required.
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.

===============< Preinstallation Check >=============== host10_9_1_1 (Master
Host) : 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 ) Test a's
Check Info ( OK ) Test c's Check Info ( 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 )

===============< Confirm Installation Information >===============
[Basic Information]
...
Install[c:Cancel, <p:Previous, n:Next>, n]:
Step 15 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.
===============< Installation. >===============
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.
6.1 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.

Step 16 After the installation, the message similar to the following will be displayed:
===============< Installation Finished >===============
Network Management System Installation succeeded.

10.9.1.1 host has been installed successfully at /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.
restart the system.
# shutdown -r now
Step 18 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.4.2.8 How to Create a Replacement User for the Sybase
Database Administrator sa User.
----End

This topic describes how to commission the U2000. To allow the U2000 to manage your
network, you must commission the U2000 before using the U2000 to manage NEs and
configure services.
NOTE
This topic applies only to the U2000 server that is newly installed.


Access - As some of
the domains
may not be
deployed
during
Deploy
Transport U2000
installation,
you can use
the domain
deployment

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

For details, see

section Configuring
Controller IP
IMM IP address:
and Commissioning
Guide (SUSE Linux).
- This
commissioni
ng item is
available for
a Linux
single-
server
system
Set SSR without the
SSR License
License disk array.
The SSR
license must
be set for
full system
backup
configuratio
n.

Monitoring in been
Planning Guide.
addresses of the
array controllers A
and B, and click
Apply.

NBI Configure XML NBI Instance 4-21.
Configure Performance Text NBI
Instance

XML NBI Certificate
l If only
the time
zone
needs to
be
modified
, restart
the
operatin
g system
after the
modifica
tion so
that the
time is
automati
For details, see cally
section Time and adjusted
Time Zone based on
Planning in U2000 the new
Planning Guide. time
zone.
l Time zone: Set
Set Date l If the
Time Zone time
the local time
zone, such as zone and
Asia/Beijing. time
both
l Time: Set this need to
parameter to the be
local time. changed,
change
the time
first and
then the
time
zone.
After the
operatin
g system
is
restarted,
the new
time is
automati
cally
adjusted

based on
the new
Time:
time
zone.
Old New After

rd: : hardening is
enabled, you
Old New cannot use
OS OSS
Passwo Password the
User
rd: : commissioni
Old New ng tool to
OS DB User Passwo Password change the
rd: : OS user
password.
DataBase Old New For details
Administrato Passwo Password about the
r rd: : For details, see method of
section U2000 changing a
Set Old New Server User password,
DataBase
Password Passwo Password Password Planning see section
User
rd: : in U2000 Planning How to
Guide. Change the
OS User
Password
in U2000
Single-
Server
MSuite Old New System
Administrato Passwo Password Software
r rd: : Installation
and
Commission
ing Guide
(SUSE
Linux).
Include two
Certificate
l CRL.

folder:default.
Set SBI l Default
nemanager/
default.

Identity File Name:

Certificate
Trust
File Name:
Certificate

Set Other
SSL Server
For details, see

section OS Security
Hardening
Hardening hardening
Planning in U2000
Planning Guide.
Configuring For details, see

the server as NTP server IP section NTP Service
an NTP address: Planning in U2000
client Planning Guide.
l If a standard
Configuring
external clock
the server as
source is
the Upper-layer NTP
available, select
intermediate- server IP address:
Configuring the
level NTP
server as the
time server
intermediate-
level NTP time
server and set Select one
Upper-layer from the
Set NTP
NTP server IP three
address to the parameters.
system IP address
Configuring of the standard
the server as external clock
the highest- - source.
level NTP l If no external
time server clock source is
available, select
Configuring the
server as the
highest-level
NTP time
server.
Route network segment 1 For details, see

Set Route


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

Host Name:
Planning Guide.
NIC:
IP Address:
Active NIC
Netmask:
Host Name:


addresses used on
addresses to be
changed are in
Configure
Network, the
commissioning tool
automatically
changes the IP
addresses. Manual
operations are not
required. The IP
addresses for the
and CORBA agent
are the same. The
naming service may
be deployed in
centralized mode.
You must confirm
the deployment
mode with upper-
layer OSS.
This IP address is
OSS. It can be
different from the
U2000 application
IP address. It must
allow the upper-
IP address and port
U2000.
exists, host names
can be used.
However, if host
names are used, you
files on the U2000
and upper-layer OSS
server and provide
the mappings
between host names

CORBA Agent Host Address: and IP addresses.

For details, see
U2000 CORBA NBI
User Guide.

used by the upper-
layer OSS to obtain
the naming service
and to use CORBA
NBIs to access the
shielded on the
upper-layer OSS and
U2000, the naming
service may become
unavailable. This
with ports used by
U2000 server.
for the non-SSL
mode and 22001 for
the SSL mode.

used by CORBA
NBIs to send
upper-layer OSS. If
on the firewall
between the upper-
layer OSS and
U2000, no
notification is
received. This port
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22002 for
the SSL mode.


used by the CORBA
service. This port
ports used by other
services on the
U2000 server.
for the non-SSL
mode and 22003 for
the SSL mode.

the information
parameter must be
used by the upper-
layer OSS is
different from that
used by CORBA
NBIs, garbled
on the upper-layer
OSS.
Default value:
UTF-8.

sets of U2000. If
multiple sets of
layer OSS, this
parameter must be
NMS planning.
Default value:
Huawei/U2000.


log file, ranging
from 1 MB to 20
MB. Keeping the
default value is
recommended.
Default value: 20
MB.

value is
recommended.
Default value: Log
immediately.

Keeping the default
Log l Assertion/
Log: Enable
– Enable
l I/O Error Log:
– Disable Enable
Log Log: Disable.
– Enable
– Disable


confirming with the
upper-layer OSS.
Only transport NEs
have physical IDs.
l Physical ID: is
expressed in
dotted decimal
notation and
equals to the NE
ID x 65536 +
extended ID. For
example, if the
NE ID is 1 and
the extended ID
is 9 for NE(9-1),
the physical ID is
65545.
l Physical ID: is
expressed in
dotted decimal
notation and is
automatically
assigned by the
U2000 to NEs.
For example,
3145765.
Default value:
Logical ID.


SDH manages devices
Otherwise, disable
this function.
Default value:
Enable.

alarms are reported
in alarm update
mode.
Default value: All.

and need to be used
along with the
U2000 engineering
that all alarms are
queried and
reported.
l Enable: specifies
that all alarms
excluding
engineering
alarms are
queried and
reported.
Default value:
Disable.


er reported from
CORBA NBIs to the
U2000.
l Internal ID:
specifies that the
ID assigned by
the U2000 is the
unique identifier
of an object.
l Object name:
specifies that the
object name
displayed on the
U2000 is the
unique identifier
of an object. The
object name on
the U2000 client
must be the same
as that on the
U2000 server.
Otherwise, data
conflicts may
occur.
Default value:
Internal ID.

Reporti reported.
that the names of
the paths and
fibers affected by
alarms are
queried and
reported.
that the names of
the paths and
fibers affected by
alarms are not
reported.
Default value:
Disable.


U2000 to
upper-layer OSS.
Ensure that SNMP
NBIs can use the IP
address and port
number to send trap
messages to the
upper-layer OSS.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 6666.

number used by the
U2000 to
upper-layer OSS.
Ensure that upper-
layer OSS can use
the IP address and
port number to send
U2000.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 9812.


ters USM is such a
security mechanism.
Currently, only USM
is supported.
Default value: USM.

ion configured, you
and must selected a
ption and set the
witho for the
l With Without
nticat encryption.
ion
and
encry
ption


5 protocol used for
CSH SNMP NBIs. The
A value of this
parameter must be
the same as the
authentication
The authentication
protocol can be set
when the security
level is With
authentication,
without encryption
or With
authentication and
encryption.

ion encrypting
communication data.
The value of this
parameter must be
encryption protocol
used for the
The data encryption
when the security
level is With
authentication and
encryption. The
AES protocol is
recommended
because it provides
better security.


layer OSS. This
receive trap
messages sent by
SNMP NBIs.
upper-layer OSS and
U2000 and the port
does not conflict
upper-layer OSS.
Default value of
port: 6666.

used by SNMP
recommended
because it is more
secure than SNMPv1
and SNMPv2c.
Default value: v3.


the upper-layer OSS
to access the U2000
when the SNMPv1
and SNMPv2c use
read and write
community names.
upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value of
Read Community:
Changeme_123.
Default value of
Write Community:
Changeme_123.

name and password
used for SNMPv3–
based security
mechanism. If this
the upper-layer OSS
cannot obtain U2000
information from
SNMP NBIs.
Default value:
admin.

authentication,
without encryption
or With
authentication and
encryption. This
the upper-layer OSS
to access the U2000
using SNMP NBIs.
Default value:
Changeme_123.


must be set if the
security level is
With
authentication and
encryption.
Default value:
Changeme_123.

r NBIs.
l Warn
ing


l Unac is generated
know when a fault
ledge occurs.
d l Acknowledged:
ged confirmed,
SNMP NBIs
report an
acknowledged
alarm.
l Unacknowledged
: After an alarm
is reversely
confirmed,
SNMP NBIs
report an
unacknowledged
alarm.
l Changed: If
alarm
information is
changed, SNMP
NBIs report a
changed alarm
which contains
the alarm level
change, alarm
influence path,
and alarm root
cause identifier.

eat of transmitting
When the U2000
MIB is used, SNMP
NBIs report
heartbeat messages
period.
Default value: 60s


e report heartbeat
le MIB, instead of
U2000–T MIB,
supports the
reporting of
heartbeat messages.
Default value:
Enable

variables contained
in the alarm
by SNMP NBIs.
This parameter must
be set according to
the alarm planning
for the upper-layer
U2000 SNMP NBI
User Guide.


m messages by SNMP
NBIs. Keeping the
default value is
recommended.
l Trap: After trap
messages are
reported, the
system does not
need to report the
next trap message
until a response
is received from
the upper-layer
OSS.
l Inform: After
trap messages are
reported, the
system starts to
report the next
trap message
until a response
is received from
the upper-layer
OSS or the
number of
attempts exceeds
the threshold.
Default value: Trap

level defined by X.
733.
Default value: No

messages in Trap
mode.
Default value: 0

packet in Inform
mode.
Default value: 5


connection times in
Inform mode upon a
connection failure.
Default value: 3

(with Time
out
time
zone)
l Local
Time
(with
time
zone)

Default value:
UTF-8

alarm and reported.
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All


g l Disable Disable
alarm queried and
reported.
Enable: specifies
that all alarms
except for
engineering alarms
are queried and
reported.

MIB T2000-
NETMANAGEME
NT-MIB.mib:
U2000-T MIB HW-
IMAPV1NORTHBO
UND-TRAP-
MIB.mib or HW-
IMAPV2NORTHBO
UND-TRAP-
MIB.mib: U2000
MIB

r to e record logs.
logs le Disable


time alarms. Every
upper-layer OSS
an independent
cache.
If the alarm
generation rate is
report rate, NBI
information to the
cache.

default port used
varies according to
the mode. The SSL
mode is
recommended
because it enables
better security.
the Use SSL check
box.

teh JMS service.
Currently, the
activeMQ
middleware is
supported.

address of the JMS
service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
access the U2000.


of the port used by
the JMS
middleware. This
to the upper-layer
OSS.

service. Set this
parameter to the IP
address of the
U2000 server.
Ensure that the
upper-level OSS can
access the U2000.

of the port used by
XML NBIs. The
upper-layer OSS
uses this port to
obtain Web service
data from XML
NBIs.
Default value: 9997

use AFB-based
interface (such as
getInventory), the
the synchronization
mode (such as SIT
or SRR) is used, do
service in order to
save system
resources.
Default value: Yes.


Web service. This
parameter is set
based on the
HTTPS is
recommended
because it is more
secure than HTTP.

troubleshooting.
Default value: Warn

alarm and reported.
common alarms that
have no correlative
relationship are
queried and
reported.
Default value: All

planning for the
Default value:
UTF-8


U2000 when they
are managed by the
same upper-layer
OSS. Set the
parameters
NMS planning.
Default value:
Huawei/U2000

order, which is
convenient for the
analysis of the
upper-layer OSS.
WDM routes are
sent randomly.
Forward: specifies
that WDM routes are
to the sink.
Backward: specifies
that WDM routes are
the source.
Default value: None


theme these themes.
– Disable
Default value: The
– Enable
– Disable
l Filter Out
Protection
Notification
– Enable
– Disable
l Filter Out
Performance
Notification
– Enable
– Disable
l Filter Out
Maintenance
Notification
– Enable
– Disable


related operation
XML NBI.
l Installation: By
default, this
parameter is set
to Enable.
l Version upgrade:
It is
recommended
that the value of
this parameter be
retained the same
before and after
the upgrade.
Perform
automatic
upgrades with the
NMS upgrade
the manual
upgrade mode is
used, change this
parameter
manually to keep
consistency.
Default value:
Enable

ring and the alarm
along with U2000
engineering tasks.
By default, all
Default value:
Disable


er l Internal ID:
specifies that the
IDs assigned by
the U2000
uniquely identify
objects.
l Object name:
specifies that the
U2000 client
names are used to
identify objects.
The U2000 client
names must be
unique in order to
prevent data
conflicts.
Default value:
Internal ID

tion alarms.
l Enable: specifies
that if an alarm
affects paths or
fibers, the names
of the affected
paths and the
fibers are
contained in the
alarm
information
during alarm
query and report.
that the names of
the affected paths
and fibers are not
reported.
Default value:
Disable


or more periods.

this parameter for
different device
value of this
parameter is the
same for different
device types, the
performance data
fail fails to be
exported. The Auto
mode is
recommended. For
details, see U2000
Performance Text
NBI User Guide.
Default value: Auto

l 30 text NBIs. The
can be exported
l 1440 based on the
collection period.



the time
performance data is
generated on NEs
and the time the
is exported.
You must configure
Data Export
Duration (min)
requirements when
set to Manual. For
details, see U2000
Performance Text
NBI User Guide.

the startup file is
cannot be set to a
value ranging from
23:00:00 to
01:00:00. If the
value of this
parameter ranges
from 23:00:00 to
01:00:00, a data
error occurs during
DTS switching.
yyyy-mm-dd
hh:mm:ss
For example,
2009-09-01 01:00:00


performance
indicators that the
can export.
Performance
indicators can be
configured in two
modes: template—
based or manual
configuration
l Template-based
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
configure a
performance
indicator
template and use
the following
operations to
configure the
performance
indicators. For
details, see
U2000
Performance Text
NBI User Guide.
Full Import:
specifies that
performance
indicators are
fully imported to
the performance
indicator
template to
overwrite the
original indicator
template.
Incremental
Import: specifies
that performance
indicators are
incrementally
imported to the
performance

indicator
template and only
new indicators
are added to the
original indicator
template. Export:
The performance
indicator
template is
exported, backed
up, or provided to
another U2000
server.
l Manual
configuration:
Before
commissioning,
you must confirm
the performance
indicators to be
monitored and
print the
performance
data. Modify: In
the dialog box
that is displayed,
configure the
indicators as
required.

accesses this
directory to obtain
performance data.


P the FTP user
password on the
–S U2000.
F
T Using SFTP is
P recommended
because SFTP
Serve
r IP:
l FTP/
SFTP
Port:
l FTP/
SFTP
User:
l FTP/
SFTP
Pass
word:
l FTP/
SFTP
Direc
tory:
l SFTP
Certif
icate:

Default value: 20

output logs.
Default value: 20


l Error recorded.
Default value: Info

planning for the
Default value:
UTF-8

export NBI file.
Default value: UTC
time

records in a file.
the threshold, the
extra records are
whose serial number
is increased by 1.
Default value:
100000

local server. The
deletes the files
generated after the
period elapses.
Default value: 3
days


task. The value of
same as the server
time.
Format: yyyy-mm—
dd hh:mm:ss

ate File Name
For details, see
section Security
Trust File Name
Certificate
Certific
Description.
ate
CRL File Name

section SSL
Principle and
Configuration.

Prerequisites
NOTICE


Context
Procedure
NOTE
NOTE
as255.255.255.0.
ossuser user.
NOTE
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE

$ ./stopnms.sh


install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.
NOTE
...

...
NOTE
been started.
# su - ossuser
$ ./startserver.sh

3. Click Login.
NOTE
MSuite at one time.

window.
Parameters.

NOTICE
# shutdown -r now
----End
Follow-up Procedure
SUSE Linux.

U2000 license.
Prerequisites
Installation Guide.

NOTICE
space or \ /:*?"<>|.
Context
– Method one:
log in to GUI OSs.
– Method two:
NOTE
Procedure
NOTE
Password.


install/RUN_DBSVR


...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE

$ ./startnms.sh
$ ls
NOTE
command.


NOTE
by SFTP.
NOTE

old value new value
500 500
1 1
Export 1 1
Client 1 1
installed.
is displayed.
the U2000 client.

iii. Click OK.
v. Click OK.
iv. Click Next.
vi. Click Finish.
----End
Result

installed.
Prerequisites
License.

NOTE
Context
configurations.
Procedure
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
$ ./startnms.sh

is displayed.
client:
menu.

----End
Result

Context
Procedure
NOTE
Password.
NOTICE
operations.

l U2000 Server

l /opt/oss/engr
l /opt/oss/OSSJRE
l /opt/oss
l /opt/sybase

l /etc/ICMR
l /var/ICMR

...
...

install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit
NOTE
interfaces command.

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb

NOTE

$ ./startnms.sh

installed.
NOTE
is displayed.
NOTE
----End
Follow-up Procedure
directory.
$ su - root
NOTICE

4.11 Configuring the Cold Standby Solution (Cold

Standby Solution)
Guide. This topic applies only to the cold standby solution. If the cold standby solution is not
required, skip this topic.
4.11.1 Configuring Automatic Backup Tasks on the Primary Site

This topic describes how to create a scheduled backup task on the primary site. After a
scheduled backup task is created, the data of the primary site can be automatically backed up.
Prerequisites
secondary site.
l The U2000 processes and the database are running on the primary site.
l The SFTP Server service has been activated on the primary site, and related ports
(including the SFTP service port 22) have been enabled.
NOTE
For details on enabling the SFTP Server service on a SUSE Linux operating system, see A.1.2
How to Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS.
l If a firewall is deployed between the primary site and the secondary site, the SFTP
service port (by default, port 22) on the firewall must be enabled. For details on enabling
the SFTP service port on a firewall, see the firewall user guide.
Context

Procedure
Step 1 Run the following steps to execute the configuration script.
NOTE

$ su - root
# ./userconfig.sh

NOTE
Step 2 Enter a node for backup, such as 1 and press Enter.

Set the interval of the scheduled task (1: daily, 2: weekly, 3: monthly)|1:
Step 3 Enter the backup interval, such as 1 and press Enter.

NOTE
The time configured for the cold backup task does not overlap with the time when data is being restored
using the MSuite. Cold backup may fail if the MSuite is restoring data.
Step 4 Enter the backup frequency, for example, if the frequency is 2:00 every day, enter 2 and press
Enter.

Set the maximum number of backup files|30:
NOTE
l The maximum number of backup files must match the size of disk that will hold the backup files,
and is recommended to be 30.
l It is recommended that you set the scheduled backup time to the time when network service traffic is
light, such as at midnight (00:00 to 06:00).
Step 5 Enter the maximum number of backup files, such as 30, and press Enter.
NOTE
After the maximum number of backup files is configured, check it as follows:

Navigate to the path /opt/oss/engr/tools/coldbackuptool/conf, and run the cat mark.inf command to
view content in the mark.inf file. Information similar to maxbackupfiles=30 will be displayed.
----End

Result
After a backup task is created on the primary site, use one of the following methods to verify
whether the configuration of backup task is successful:
– Check the backup task.
$ su - root

coldbackuptool; ./coldbackup.sh -silent " > /dev/null 2>&1
NOTE
The displayed value of cycle varies depending on the backup interval. For example:
l If the configured backup interval is daily, the displayed value of Day is similar to
daily.
l If the configured backup interval is weekly, the displayed value of Day is similar
to weekly: Sunday.
l If the configured backup interval is monthly, the displayed value of Day is similar
to monthly: 22.
– Check the backup result.
$ su - root

2015-07-28 21:20:29;Successful;backupDB;20150728211943.7z
NOTE
The fields in the command output indicate the backup date and time, operation result
(Successful/Failure), operation type (backupDB/restoreDB), and backup package (the
timestamp in the file name indicates the backup time).
NOTE
l Check the log.
coldbackuptool/silent/coldbackupresult.txt to check the backup log.
l Check the backup files.
The backup directory is /opt/backup/ftpboot/coldbackupdata and the backup files are
in the 7z format.

Follow-up Procedure
For how to end the backup task, run the following steps.
2. Run the following commands to switch to the root user and end the backup task on the
secondary site:
$ su - root
# ./stopCron.sh
4.11.2 Configuring Automatic Restoration on the Secondary Site

This topic describes how to create a scheduled restoration task on the secondary site. After the
scheduled restoration task is created, the U2000 data can be automatically restored on the
secondary site.
Prerequisites
secondary site. For details about the installation procedure, see the U2000 Single-Server
System Software Installation and Commissioning Guide.
l On the secondary site, network management process and the maintenance tool are
standby and the database is running. If the U2000 has started when the restoration task is
performed, the U2000 process is automatically stopped.
l The primary site is running correctly. (If the primary site becomes faulty before
automatic restoration starts, data cannot be restored on the secondary site.)
Context
Procedure
Step 1 Run the configuration script on the secondary site.
NOTE

$ su - root
# ./userconfig.sh


NOTE
Step 2 Enter a node for restoration, such as 2 and press Enter.

Set the interval of the scheduled task(1:daily,2:weekly,3:monthly)|1:
Step 3 Enter the automatic restoration interval, for example, if the automatic restoration task is
performed once every day, enter 1 and press Enter.
Step 4 Enter the time to start the automatic restoration task, such as 5 and press Enter.
>>>>>Enter the peer SFTP user<<<<<
Enter the peer SFTP IP address:
Enter the password for SFTP user:
NOTE
l The interval between the automatic restoration time and the automatic backup time is fixed at 3
hours. For example, if the automatic backup time is 2 a.m., set the automatic restoration time to 5
a.m.
l If connection to the primary site fails due to Primary Site Authentication Error when you enter
the primary site's SFTP information, see How Do I Handle the Failure to Connect Two Servers Due
to a Mutual Trust Authentication Error? for troubleshooting.
l Reconfigure the automatic restoration task if the SFTP user's password is changed.
Step 5 Enter the IP address and SFTP user name of the primary site, and press Enter. In this
example, IP address is 192.168.0.0 and default password of the SFTP user is
Changeme_123. The information is used by the secondary site to obtain the backup file from
the primary site by using the SFTP.
Scheduled restoration will automatically shut down the U2000 and MSuite.
----End
Result
After an automatic restore task is created on the secondary site, use one of the following
methods to verify whether the configuration of restore task is successful:
– Check the restoration task.
$ su - root


coldbackuptool; ./coldrestore.sh -silent " > /dev/null 2>&1
NOTE
The displayed value of cycle varies depending on the restoration interval. For example:
l If the configured restoration interval is daily, the displayed value of Day is similar
to daily.
l If the configured restoration interval is weekly, the displayed value of Day is
similar to weekly: Sunday.
l If the configured restoration interval is monthly, the displayed value of Day is
similar to monthly: 22.
– Check the restoration result.
$ su - root

2015-07-28 21:48:56;Successful;restoreDB;20150728211943.7z
NOTE
The fields in the command output indicate the restoration date and time, operation
result (Successful/Failure), operation type (backupDB/restoreDB), and backup
package (the timestamp in the file name indicates the backup time of the data to be
restored).
NOTE
l Checking the log
coldbackuptool/silent/coldrestoreresult.txt to check the restore log.
Follow-up Procedure
l For how to end the restoration task, run the following steps.
a. Log in to the OS as the ossuser user through SSH by using PuTTY.
b. Run the following commands to switch to the root user and end the restoration task
on the secondary site:
$ su - root
# ./stopCron.sh
l After automatic restoration is implemented for the first time, stop the U2000 process on
the primary site and start the U2000 process on the secondary site to ensure that the
process can function properly.
– If the U2000 process runs properly on the secondary site, stop the U2000 process on
the secondary sites start the U2000 process on the primary site.
– If the U2000 process not runs properly on the secondary site, re-execute the restore
task on the secondary sites or contact Huawei technical support personnel.

NOTE
After data restoration fails, if the missing database files fault is found in the log file, rectify the
fault by following the instructions provided in How to Rectify the Data Restoration Failure on a
Secondary Site Because of Missing Databases.
NOTE
l If the CORBA NBI, XML NBI, SNMP NBI, or text NBI is configured for the U2000, you must
reconfigure the IP address used by the NBI to interconnect with the upper-layer OSS after
successfully restoring the database. For details, see the related NBI user manual.
l After the preceding operations are complete, login passwords for the U2000 client and NE Software
Management are restored to be consistent with the U2000 data.

and Commissioning Guide (SUSE Linux) 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 Sybase Database
This topic covers FAQs about the Sybase database.
A.5 U2000 System
This topic covers FAQs about the U2000 system.
A.6 Install the U2000 Software Exception Processing
This topic describes how to uninstall the U2000 software. Before reinstalling the U2000
software, you must uninstall U2000.
A.1 SUSE Linux OS

This topic provides the FAQs occurred in the SUSE Linux OS.
A.1.1 How to Change the OS User Password
Question
How to change the OS user password?
Answer
l Method 1:
a. Log in to the OS as the user whose password needs to be changed, for example,
root, ossuser, or webuser.

NOTE
Method 1 uses the ossuser user as an example.

The root/dbuser/webuser user cannot use SSH to log in to the OS. After security hardening
is enabled, change the root/dbuser/webuser user password by using Method 2.
b. Open the command terminal, run the following command to set the OS user
password:
$ passwd
c. Enter the current ossuser user password as prompted, the default password is
Changeme_123.
d. 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.
e. 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.
l Method 2 (Change the passwords for other OS users, as the root user):
a. Log in to the OS as the root user.
b. Open the command terminal, run the following command to set the OS user
password:
# passwd OS user
For example, passwd ossuser.

c. 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.
d. 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.1.2 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:
n Run the following command to start the FTP service:
# service vsftpd start
n Run the following command to stop the FTP service:

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

n Run the following command to start the FTP service:
1) Use the PuTTY to log in to the server as user ossuser in SSH mode.
2) Run the following command to set environment variables.
$ . /opt/oss/server/svc_profile.sh
3) Run the following command to switch to user root.

$ su - root
Password: Password of root
4) Run the following command to enable the FTP service:

# /opt/oss/server/3rdTools/ftp/files/vsftpd_adm.sh enableFTP
FTP service is enabled if the following information is displayed:

Operation succeeded.
n Run the following command to stop the FTP service:

1) Use the PuTTY to log in to the server as user ossuser in SSH mode.
2) Run the following command to set environment variables.
3) Run the following command to switch to user root.

$ su - root
4) Run the following command to disable the FTP service:

# /opt/oss/server/3rdTools/ftp/files/vsftpd_adm.sh disableFTP
FTP service is disabled if the following information is displayed:

Operation succeeded.
l Starting and stopping the SFTP (more secure, recommended) service:

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

it to change it to #PAMAuthenticationViaKBDInt yes.
n Ensure that # is not 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.3 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:
a. Log in to the SUSE Linux OS as the root user.
b. 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
c. 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:
a. Log in to the SUSE Linux OS as the root user.
b. 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
c. Run the command wq! to save and close the ftpusers file.
----End
A.1.4 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 10.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.5 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.
NOTE
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:

# 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
– destination network segment address: The network segment of the IP address of the computer
connected to the U2000 server.
– gateway IP address: network management IP address for the network on which the U2000
server is located.
– destination network segment subnet mask: subnet mask of the network segment on which the
computer connected to the U2000 server is located.
l Example:
10.16.1.0 10.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.6 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
NOTE
...
...
NOTE
been started.
# su - ossuser
$ ./startserver.sh
Step 2 Log in to the MSuite client.
Step 3 On the MSuite client, click the Server tab.
Step 4 Right-click the target server and choose Configure Route from the shortcut menu. The
Configure Route dialog box is displayed.
Step 5 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 took effect immediately.
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 6 Click OK.

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

Question
How do I check disk partitions?

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

d. Select Partitioner on the right.
e. Carefully read the information in the Warning dialog box, and then click Yes.
f. 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.8 How to Check the Remaining Space of a Disk
Question
How do I check the remaining space of a disk?
Answer
Run the df -hk command to check the remaining space of a disk.
For example, run the df -hk /opt command to check the remaining space of the /opt partition.
A.1.9 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.10 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
A.1.11 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.12 How to Forcibly End a Process

Question
How do I forcibly end a process?
Answer
Run the kill -9 process ID command to forcibly end a process.
A.1.13 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.
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.
A.1.14 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.

Step 5 To change the time, click Change. In the dialog box that is displayed, set the date and time,
and then click Accept.
Step 6 Click OK.
restart the system.
# shutdown -r now
Step 8 Optional: For Suse 11 OS, ensure that the time and time zone has been correctly modified
after restart the OS, or run the following commands.
1. Run the following commands to synchronize the hardware time.
# . /etc/sysconfig/clock
# /sbin/hwclock --systohc $HWCLOCK
2. Run the following commands to synchronize time zone information to initrd.

# mkinitrd
3. Run the following commands to restart the OS. It takes approximately 5 to 8 minutes to
restart the system.
# shutdown -r now
----End
A.1.15 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 It is recommended that you log in to the OS in SSH (recommended) or Telnet mode, instead of the
Java desktop mode. Then run the commands to enable the VNC services.
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 After installing U2000, the scripts to enable and disable VNC is in the in the /opt/oss/engr/
tools/VNC directory. Before installing U2000, the scripts to enable and disable VNC is in the in
the /opt/install/OSSICMR/tools/VNC directory. The following example describes how to use the
VNC after installing U2000.
l Configure the VNC service as the root user.
a. Use the PuTTY tool to log in to the server as a root user.
b. 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
i. 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.
ii. 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)?
iii. 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.
c. Run the following commands to enable the VNC services.

NOTICE
After uploading and decompressing the preconfigured component package and
before running the script to preconfigure the OS, the scripts to enable and disable
VNC is in the in the /opt/install/OSSICMR/tools/VNC directory.
After preconfiguring the OS, the scripts to enable and disable VNC is in the in
the /opt/oss/engr/tools/VNC directory.
# cd /opt/oss/engr/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 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 command
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 -ef |grep vnc 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 3 to start the VNC service for the root user.
l If information is displayed, the VNC service corresponding to the root user has
started.
d. 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
10.9.1.1.
i. On a PC or laptop, choose Start > Run. In the dialog box that is displayed,
enter cmd to open a CLI.

ii. Run the following command to navigate to the path where the PuTTY is
located:
C:\> cd /d D:\PuTTY\
iii. Run the following command to create an SSH tunnel for the root user:
D:\PuTTY> putty -L 5902:localhost:5902 -L 5802:localhost:5802
10.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 10.9.1.1 specifies the server IP address.
iv. 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.
e. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5802 in the
address bar. Then press Enter.
NOTE
If a message is displayed indicating that the application is prohibited to run, choose Start >
Control Panel and click Java. In the Java Control Panel dialog box, click the Security tab,
Edit Site List, and Add, and enter http://localhost:5802. Click OK, Continue, and then
OK. Restart the Internet Explorer and enter http://localhost:5802 in the address bar.
f. 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.

a. Use the PuTTY tool to log in to the server as an ossuser user.

b. 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
i. 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.
ii. 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)?
iii. 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.
c. Run the following commands to enable the VNC service for the ossuser user.
$ su - root
# 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.

NOTE
l If a message is displayed asking you to set the password, run the vncpasswd command
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 -ef |grep vnc 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 3 to start the VNC service for the ossuser user.
l If information is displayed, the VNC service corresponding to the ossuser user has
started.
d. 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 10.9.1.1.
i. On a PC or laptop, choose Start > Run. In the dialog box that is displayed,
enter cmd to open a CLI.
ii. Run the following command to navigate to the path where the PuTTY is
located:
C:\> cd /d D:\PuTTY\
iii. Run the following command to create an SSH tunnel for the ossuser user:
D:\PuTTY> putty -L 5903:localhost:5903 -L 5803:localhost:5803
10.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 10.9.1.1 specifies the server IP address.
iv. 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.
e. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5803 in the
address bar. Then press Enter.
NOTE
If a message is displayed indicating that the application is prohibited to run, choose Start >
Control Panel and click Java. In the Java Control Panel dialog box, click the Security tab,
Edit Site List, and Add, and enter http://localhost:5803. Click OK, Continue, and OK,
restart the Internet Explorer, and enter http://localhost:5803 in the address bar.
f. 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:
a. 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.
b. If the problem persists, close all IE web browsers and restart the IE.
c. 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.
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
options for the path
must click in the CLI before entering
on the association information.
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 You can only enter information in the

t e outside the VNC window or upload it to the VNC
options VNC window window.
for cannot be
operatio copied or pasted
ns not into the VNC
on the window.
VNC
CLI, The Ctrl + Alt You can only click the button on the left-
such as +U right corner to unlock a client.
operatio combination
ns on cannot be used
the file, to unlock a
window client.
Available Alt + F1 Opening the main menu

Scenar Availabil Shortcut Description

io ity Option/
Operation
, 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
Table A-3 VNC FAQs and solutions

No. Description Solution
1 A user fails to run The VNC has been running for a long time
commands in the without being restarted, resulting in environment
CLI after logging variable failures. To resolve this problem, restore
in to the GUI the environment variables and run the related
through the VNC. commands.
Restore the environment variables:
1. Log in to the GUI as the root user.
2. Run the following commands to restore
environment variables:
# . /.profile-EIS
2 If the VNC service There is a low probability that this issues occurs
has been running if the VNC service has been running for a certain
for a long period period of time. If this issue occurs, restart the
of time, the GUI VNC service as the root or ossuser user.
desktop may stop
responding when a
user logs in to the
GUI desktop in
vnc mode.

No. Description Solution
3 A JRE version's Perform the following operations to rectify the

upgrade to 1.8 fault:
triggers a Linux 1. Delete the VNC cache.
OS bug, causing a
failure to access a. Choose Start > Control Panel and click
the VNC. Java.
b. In the Java Control Panel window, click
shows the the General tab.
displayed c. Click View. In the Java Cache Viewer
message. dialog box, click Resources in the
Display area.
d. Delete all records with the name of
VncViewer.jar.
e. Log in to the VNC again.
2. Optional: If the login still fails, the mapping
Linux OS patch is not installed after an
U2000 upgrade. In this case, perform either
of the following operations to avoid this
issue:
l Install the mapping Linux OS patch on the
U2000 server.
l Uninstall JRE 1.8, install JRE 1.6 or 1.7
on a windows computer, and see Step 1 to
delete the VNC cache.
4 A message is Uninstall JRE 1.8, install JRE 1.6 or 1.7 on a

displayed windows computer.
indicating that
application
blocked for
security. Failed to
validate
certificate,the
application will
not be executed.
----End
A.1.16 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-eth0 if-up.d
ifcfg-bond0 ifcfg-lo providers
ifroute-lo ifcfg.template routes
ifcfg-eth1 if-down.d routes.YaST2save
ifroute-lo scripts
NOTE
– If the command output contains information similar to ifcfg-bond0, bond has been configured
for the network interface. Perform Step 2.2 to view the IP address of the used network
interface.
– If the command output contains information similar to ifcfg-eth0, bond has not been
configured for the network interface. Perform Step 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='10.9.1.255'
IPADDR='10.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'
BONDING_SLAVE0='eth3'
PREFIXLEN='24'
NOTE
The value 10.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 Step 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-eth0

BOOTPROTO='static'
BROADCAST=''

ETHTOOL_OPTIONS=''
IPADDR='10.9.1.2/24'
MTU=''
NETWORK=''
REMOTE_IPADDR=''
NOTE
The value 10.9.1.2/24 of the IPADDR parameter is the IP address of network interface eth0.
Record the value. If information similar to ifcfg-eth0 is displayed, repeatedly perform Step 2.3
and record the IP address.
Step 3 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:

# cd /opt/sudobin/engr/engineering/tool/OSSICMR/tools
# ./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 AddIPForSuse.sh stores at /opt/oss/engr/engineering/tool/OSSICMR/tools before

R016C60 CP2025. While R016C60 CP2025 and later version stores at /opt/sudobin/engr/
engineering/tool/OSSICMR/tools.
– 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.
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 3.

Step 4 Run the following commands to restart the OS to make the configurations take effect.
# shutdown -r now
----End
A.1.17 How to Capture Snapshots on SUSE Linux
Question
How do I capture snapshot on SUSE Linux?
Answer
l Method 1: Use the keyboard.
a. Press Print Screen.
b. Rename the file and click Save.
l Method 2: Use commands.

a. In the CLI, run the gnome-panel-screenshot command.
b. Rename the file and click Save.
----End
A.1.18 How to Check Whether Bond Is Configured
Question
How do I check whether bond is configured?

Answer
l Method 1:
a. Use the remote GUI software to log in to the server as the root user.
b. On the desktop, right-click and choose Open Terminal from the shortcut menu to
display a CLI.
c. Run the following command to log in to the YaST2 Control Center.
# yast2
d. In the YaST2 Control Center dialog box, choose Network Devices > Network
Card.
e. In the Network Setup Method dialog box, select Traditional Method with ifup
and click Next.
f. The Network Card Configuration Overview dialog box is displayed.
NOTE
If bond is configured, the Bond Network option is available. If bond is not configured, the Bond
Network is unavailable.
l Method 2:
a. On the CLI, run the following command:
# ifconfig -a

bond0 Link encap:Ethernet HWaddr 5C:F3:FC:09:24:DC
inet addr:10.71.224.142 Bcast:10.71.225.255 Mask:
255.255.254.0
inet6 addr: fe80::5ef3:fcff:fe09:24dc/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:3385744 errors:0 dropped:0 overruns:0 frame:0
TX packets:3303126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3205764595 (3057.2 Mb) TX bytes:3327903135 (3173.7
Mb)
NOTE
If bond is configured, the command output contains bond0.
----End
A.1.19 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.
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.
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.20 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 to upload the 7-zip software package to the /opt directory on the server as the root
user. For details about how to use SFTP to upload the software package, see A.1.27 How to
Use the FileZilla to Transfer Files by SFTP.
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.13 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.1.21 How to Enable the File Change Audit Function on SUSE

Linux OS
Question
To ensure system security, the SUSE Linux OS supports the file change audit function that
can record relevant file change information. How do I enable the file change audit function on
SUSE Linux OS?
Answer
NOTICE
Enabling the file change audit function of the SUSE Linux OS may affect the system space
occupation and system performance. It is advised not to enable the function.
l If no security hardening is performed on the OS, perform the following operations:

b. Run the following command to query whether the auditd service is running:
# service auditd status

Checking for service auditd running
NOTE
l If information like running is displayed, the auditd service is running.

l If no information like running is displayed, the auditd service is not running. Contact
Huawei engineers for a solution.
c. Run the following command to query the configured audit rules of the system:
# auditctl -l

No rules
NOTE
The preceding information indicates that no audit rules have been configured.
d. Run the following command to create audit rules for the relevant U2000 directory
or file to be audited. The following uses the /opt/oss/engr directory as an example:
# auditctl -w /opt/oss/engr -p wa

NOTE
l /opt/oss/engr is the directory to be audited.

l The directory and file to be audited must be minimized.
e. Run the following command to query whether the audit rules of the /opt/oss/engr
directory are created:
# auditctl -l

LIST_RULES: exit,always dir=/opt/oss/engr (0x8) perm=wa
NOTE
The preceding information indicates that the audit rules of the /opt/oss/engr directory have
been created. The OS will audit the permission changes of files in the /opt/oss/engr
directory.
f. Run the following command to enable the creation of the audit rules of the /opt/oss/
engr directory to take effect:
# auditctl -e 1

AUDIT_STATUS: enabled=1 flag=1 pid=4091 rate_limit=0 backlog_limit=320
lost=7 backlog=0
NOTE
To query the audit log and learn the detailed file change information, run the ausearch -
f /opt/oss or /var/log/audit/audit.log command. For details, see the SUSE Linux OS
documentation. For example, https://www.suse.com/documentation/sles11/.
g. Optional: To delete the audit rules of the /opt/oss/engr directory, perform the
following operations:
i. Run the following command to delete the audit rules of the /opt/oss/engr
directory:
# auditctl -W /opt/oss/engr -p wa
NOTE
/opt/oss/engr is the directory to be audited.
ii. Run the following command to query whether the audit rules of the /opt/oss/
engr directory are deleted:
# auditctl -l

No rules
NOTE
If no information like LIST_RULES: exit,always dir=/opt/oss/engr (0x8) perm=wa
is displayed, the audit rules of the /opt/oss/engr directory have been deleted.
iii. Run the following command to enable the deletion of the audit rules of
the /opt/oss/engr directory to take effect:
# auditctl -e 1
The displayed information is similar to the following:

AUDIT_STATUS: enabled=1 flag=1 pid=4091 rate_limit=0
backlog_limit=320 lost=7 backlog=0
l If security hardening is performed on the OS, perform the following operations:

a. Log in to the OS as the ossuser user.
b. Run the following command to switch to the root user:
$ su - root
Enter the password for the root user.

c. Run the following command to query whether the auditd service is running:
# service auditd status

Checking for service auditd running
NOTE
l If information like running is displayed, the auditd service is running.

l If no information like running is displayed, the auditd service is not running. Contact
Huawei engineers for a solution.
d. Run the following command to query existing audit rules:
# auditctl -l

LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=time-change
syscall=adjtimex,settimeofday
LIST_RULES: exit,always arch=1073741827 (0x40000003) key=time-change
syscall=stime,settimeofday,adjtimex
syscall=clock_settime
LIST_RULES: exit,always watch=/etc/localtime perm=wa key=time-change
LIST_RULES: exit,always watch=/etc/group perm=wa key=identity
LIST_RULES: exit,always watch=/etc/passwd perm=wa key=identity
......
LIST_RULES: exit,always watch=/etc/sudoers perm=wa key=scope
LIST_RULES: exit,always watch=/var/log/sudo.log perm=wa key=actions
LIST_RULES: exit,always watch=/sbin/insmod perm=x key=modules
LIST_RULES: exit,always watch=/sbin/rmmod perm=x key=modules
LIST_RULES: exit,always watch=/sbin/modprobe perm=x key=modules
LIST_RULES: exit,always arch=3221225534 (0xc000003e) key=modules
syscall=init_module,delete_module
NOTE
Some audit rules are enabled by default after OS security hardening.
e. Perform the following operations to create audit rules for the relevant U2000
directory or file to be audited. The following uses the /opt/oss/engr directory as an
example:
i. Run the vi command to open the audit.rules file.
# vi /etc/audit/audit.rules

# This file contains the auditctl rules that are loaded
......
-w /var/log/sudo.log -p wa -k actions
-w /sbin/insmod -p x -k modules
-w /sbin/rmmod -p x -k modules
-w /sbin/modprobe -p x -k modules
-a always,exit -F arch=b64 -S init_module -S delete_module -k modules
-e 2
ii. Add the audit rules of the /opt/oss/engr directory to the audit.rules file, as
follows:
......

-w /opt/oss/engr -p a
-e 2
NOTE
l /opt/oss/engr is the directory to be audited.

l The directory and file to be audited must be minimized.
iii. Run the :wq command to save the modification and exit the vi editor.
f. Powering off the U2000 and the database.
g. Run the following commands to restart the OS:

# shutdown -r now
h. Log in to the OS as the ossuser user.

i. Run the following command to switch to the root user:
$ su - root
Enter the password for the root user.

j. Run the following command to query whether the audit rules of the /opt/oss/engr
directory are created:
# auditctl -l

......
LIST_RULES: exit,always dir=/opt/oss/engr (0x8) perm=wa
NOTE
l The preceding information indicates that the audit rules of the /opt/oss/engr directory
have been created. The OS will audit the permission changes of files in the /opt/oss/engr
directory.
l To query the audit log and learn the detailed file change information, run the ausearch -
f /opt/oss or /var/log/audit/audit.log command. For details, see the SUSE Linux OS
documentation. For example, https://www.suse.com/documentation/sles11/.

k. Optional: To delete the audit rules of the /opt/oss/engr directory, perform the
i. Run the vi command to open the audit.rules file.
# vi /etc/audit/audit.rules

......
-w /opt/oss/engr -p a
-e 2
NOTE
/opt/oss/engr is the directory to be audited.
ii. Delete the audit rules of the /opt/oss/engr directory from the audit.rules file,
as follows:
......
-e 2
iii. Run the :wq command to save the modification and exit the vi editor.
iv. Powering off the U2000 and the database.
v. Run the following commands to restart the OS:
# shutdown -r now
vi. Run the following command to query whether the audit rules of the /opt/oss/
engr directory are deleted:
# auditctl -l

......


NOTE
If no information like LIST_RULES: exit,always dir=/opt/oss/engr (0x8) perm=wa
is displayed, the audit rules of the /opt/oss/engr directory have been deleted.
----End
A.1.22 How Do I Set an Encryption Algorithm for OpenSSH

(SUSE Linux)
Question
How do I set an encryption algorithm for OpenSSH?
Answer
Step 1 Log in to the SUSE Linux OS as the ossuser user through SSH by using PuTTY.
Step 2 Run the following command to switch to the root user.

$ su - root
Password: password of root user
Step 3 Run the following command to access the directory /opt/oss/engr/engineering/script/.

# cd /opt/oss/engr/engineering/script/
Step 4 Perform the following operations to set an encryption algorithm for OpenSSH.
1. Run the following command:
# python modifysshdalg.py
The command output is as follows:

Start modify OpenSSH algorithms ......
System environment is : linux
uid=0(root) gid=0(root) groups=0(root),105(sfcb)
All mac_algorithms:
1: hmac-md5-etm@openssh.com 2:hmac-sha1-etm@openssh.com
3: umac-64-etm@openssh.com 4:umac-128-etm@openssh.com
5: hmac-sha2-256-etm@openssh.com 6:hmac-sha2-512-
etm@openssh.com
7: hmac-ripemd160-etm@openssh.com 8:hmac-sha1-96-
etm@openssh.com
9: hmac-md5-96-etm@openssh.com 10:hmac-md5
11: hmac-sha1 12:umac-64@openssh.com
13: umac-128@openssh.com 14:hmac-sha2-256
15: hmac-sha2-512 16:hmac-ripemd160
17: hmac-ripemd160@openssh.com 18:hmac-sha1-96
19: hmac-md5-96
All cipher_algorithms:
1: aes128-cbc 2:3des-cbc
3: blowfish-cbc 4:cast128-cbc
5: arcfour128 6:arcfour256
7: arcfour 8:aes192-cbc
9: aes256-cbc 10:rijndael-cbc@lysator.liu.se
11: aes128-ctr 12:aes192-ctr
13: aes256-ctr

All Kex_algorithms:
1: ecdh-sha2-nistp256 2:ecdh-sha2-nistp384
3: ecdh-sha2-nistp521 4:diffie-hellman-group-
exchange-sha256
5: diffie-hellman-group-exchange-sha1 6:diffie-hellman-group14-sha1
7: diffie-hellman-group1-sha1
Input Y or y to modify mac_algorithms, otherwise,exit the modification of

mac_algorithms.
:
2. Enter Y or y and press Enter.

Please input numbers of mac_algorithms separated by a ',' . For example: 2,3
3. Select the secure MACs algorithm for OpenSSH based on actual situations and press
Enter. It is recommended that 11 be entered.
NOTE
– The new algorithm will replace the previous OpenSSH algorithm, you need to ensure that the
new algorithm contains all the algorithms that OpenSSH needs to use. Otherwise, some
connected systems cannot connect to the U2000 server through OpenSSH.
– Before selecting a secure algorithm, ensure that the system interconnected to the U2000
supports this algorithm; otherwise, this system cannot connect to the U2000 server over
OpenSSH.
– If need support multi secure algorithms, select the number before the secure algorithms and
separate them with commas (,).
Input Y or y to modify cipher_algorithms,otherwise,exit the modification of
cipher_algorithms.

Please input numbers of cipher_algorithms separated by a ',' . For example:
11,12,13
5. Select the secure Ciphers algorithm for OpenSSH based on actual situations and press
Enter. It is recommended that 11,12,13 be entered.
NOTE
OpenSSH.
Input Y or y to modify kex_algorithms,otherwise,exit the modification of
kex_algorithms.
:

Please input numbers of kex_algorithms separated by a ',' . For example: 4,5,6
:
7. Select the secure Kex algorithm for OpenSSH based on actual situations and press
Enter. It is recommended that 4 be entered.

NOTE
OpenSSH.
Operation succeeded. Please restart Openssh for the settings to take effect.
Please input Y or y to restart OpenSSH,inputing others will exit directly and
no restart OpenSSH!
input :

Shutting down SSH daemon done
Starting SSH daemon done
Restarting OpenSSH is successful.
End modify OpenSSH algorithm ......
NOTE
If the message "Restarting OpenSSH is successful." is displayed, the OpenSSH encryption
algorithm is successfully set.
----End
A.1.23 How to Check Downloaded Software Packages Using

HashMyFiles Software
Question
How do I check downloaded software packages using HashMyFiles software?
Answer
Step 1 Obtain the MD5 code or SHA information that is used to check the downloaded software
package integrity.
l Download the iManager U2000 version MD5 CODE(English) file from http://
support.huawei.com/carrier. The iManager U2000 version MD5 CODE(English) file
contains MD5 code information after all software and document packages are
decompressed. Please contact a Huawei engineer to download the file.
– For carrier, log in to http://support.huawei.com/carrier. Search for U2000 and
select iManager U2000 in the search box on the Software tab. Then select a
desired version. Download the file in the Version Documentation column.
– For enterprise, log in to http://support.huawei.com/enterprise. Search for U2000
and select iManager U2000 in the search box on the Support tab. Then click
Documentation tab. Select a desired version and download the file.
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.

l The files in the ServiceCD of the Huawei RH series rack server are archived in Support
website. Perform the following operations to obtain the ISO files:
a. Log in to http://enterprise.huawei.com.
b. Choose Support > Server.
c. Choose Server Management Software > FusionServer Tools > Downloads >
V100R002C00 > V100R002C00SPC300.
d. Download the FusionServer Tools-ServiceCD2.0-V109.zip software packages.
e. Use the PGPverify to verify correctness of the software packages. For details, see
A.1.24 How Do I Verify Downloaded Software Packages Using the PGPVerify
Software.
l For other third-party software, obtain the MD5 code or SHA information from the
corresponding official websites.
Step 2 Navigate to http://www.nirsoft.net/utils/hash_my_files.html and download the

HashMyFiles. For more information about software operation, see the software Help or go to
the official website of the software http://www.nirsoft.net/utils/hash_my_files.html for
technical support.
Step 3 Run the HashMyFiles.
Step 4 Choose Files > Add Folder from the main menu to access the Select Folder dialog box.
NOTE
You can also drag each local downloaded software package to the running window of the HashMyFiles.
Step 5 Select the folder in which the compression packages are stored and click OK.
Step 6 After uploading is complete, the MD5 code information of the local downloaded packages is
automatically generated. Choose View > HTML Report All Items to export the MD5 code
information and compare it with that in the MD5 code file obtained from Step 1.
Option Description
If the exported MD5 code information is the same as that in packages are correctly
the MD5 code file obtained from Step 1, downloaded.
If the exported MD5 code information is the different from download software
that in the MD5 code file obtained from Step 1, packets again.
----End
A.1.24 How Do I Verify Downloaded Software Packages Using

the PGPVerify Software
Question
How do I verify downloaded software packages using the PGPVerify software?
Answer
l Software packages and signature files correspond to each other and are stored in the
same directory. A software package corresponds to a signature file. Signature files are
released with products and their software packages.

l The extension of signature files is .asc. Generally, the names of signature files are the
same as the names of software packages. That is, when the software package name is
V200R016C60.zip, the corresponding signature file name is V200R016C60.zip.asc.
NOTE
The asc files will need to click the PGP after software packages to
download.
l Obtain the PGPVerify tool that is used to verify the completeness of downloaded
software packages and its public key file KEYS.
a. Download and decompress the PGPVerify tool.
n For carrier: visit http://support.huawei.com/carrier/digitalSignatureAction
to download the OpenPGP Signature Verification Guide package and
decompress it. Continue to decompress the VerificationTools.zip package in
the current folder.
n For enterprise: visit http://support.huawei.com/enterprise/en/tool/software-
digital-signature-validation-tool--pgp-verify--TL1000000054 to download
and decompress the VerificationTools.zip package.
b. Go to the VerificationTools folder that is generated after decompression and obtain
different versions of PGPVerify software for different OSs.
n Windows: PGPVerify.exe (in the Windows directory)
n Solaris: PGPVerify-sparc.tar.bz2 (in the solaris\PGPVerify TOOL directory)
n Linux: PGPVerify-x86_64.tar.gz (in the linux\X86\bit64\PGPVerify TOOL
directory)
c. On Solaris/Linux OSs, use SFTP as the root user to upload the obtained PGPverify
software and public key file KEYS to the server. For details about the SFTP transfer
method, see A.1.27 How to Use the FileZilla to Transfer Files by SFTP.
d. Windows OS supports GUI-based verification and CLI-based verification. Solaris
and Linux OSs support CLI-based verification only.
e. KEYS is the public key file.
l PGPVerify is a digital signature verification tool released by Huawei. Users can select
third-party openPGP verification tools based on actual needs.
Tool OS Tool Description
PGPVerify Windows/Solaris/Linux It is a simple PGP

verification tool released
by Huawei.
GNU Privacy Guard for Windows It is an official version of

Windows (Gpg4Win) GnuPG for Windows.
Official website: http://
www.gpg4win.org/
Recommended version:
2.2.1

Tool OS Tool Description
The GNU Privacy Guard Linux It is a free and source-open

(GnuPG) GNU tool that implements
the OpenPGP standard
defined by the RFC4880
protocol. This tool is pre-
installed on most Linux
OSs.
Official website: http://
www.gnupg.org
Recommended version:
2.0.9
l GUI-based verification on Windows OS:
Files to be prepared before verification:

– PGPVerify software: PGPVerify.exe
– Public key file corresponding to the PGPVerify software: KEYS
– U2000 software package
– Signature file corresponding to the U2000 software package
a. Double-click PGPVerify.exe to start the PGPVerify tool.

b. Click Select Public Key, select the obtained public key file KEYS, and load it.
c. Click Multiple Verify and select the D:\oss\ directory to verify all files in it.
NOTE
l D:\oss\ indicates the directory that stores the signature file. Change it based on site
requirements. The signature file and software package must be stored in the same
directory.
l To verify a single file, click Single Verify and select the file to be verified.
n The green item indicates passed verification, that is, [PASS].
n The yellow item indicates unsupported verification, that is, [WARN]. For
example, the signature file or software version does not exist.
n The red item indicates failed verification, that is, [FAIL].
If no "WARN" or "FAIL" character is displayed, the signature file is valid. All items
are displayed in green.
NOTICE
If a version has multiple signature files to be verified, the version is secure only
when the verification results of all files are "PASS". If the verification results
contain "WARN" or "FAIL", the verification is not passed and security risks exist.
In that event, re-download the software package.
l CLI-based verification on Windows OS:

a. Open the CLI and run the following command to verify the signature file:

> "C:\PGPVerify.exe" -k "C:\KEYS" -d "D:\oss"
NOTE
l Assume that the signature file and software package are stored in the D:\oss\ directory, and
the PGPVerify tool and public key file are stored in the C:\ directory.
l To verify a single file, run the C:\PGPVerify.exe" -k "C:\KEYS" -f "D:\oss
\V200R016C60.zip.asc command.

[INFO]:Filter file in directory, please wait...
[WARN]:Can't find signature file, signed file position: D:\oss
\V200R016C60.zip.
[WARN]:Can't find signed file, signature file position: D:\oss
\V200R015C51.zip.asc.
[FAIL]:Invalid Signature. File path: D:\oss\V200R015C52.zip.
[PASS]:Good Signature. File path: D:\oss\V200R015C53.zip, Public key
fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824
[INFO]: Verify Complete.
NOTE
In the preceding characters in bold, the RSA key ID is consistent with the public key ID. For a
certain file, if no "WARN" or "FAIL" character is contained in other information, the signature
file is valid.
NOTICE
l CLI-based verification on Solaris and Linux OSs:

Files to be prepared before verification:
– PGPVerify software:
n Solaris: PGPVerify-sparc.tar.bz2
n Linux: PGPVerify-x86_64.tar.gz
– Public key file corresponding to the PGPVerify software: KEYS
– U2000 software package
– Signature file corresponding to the U2000 software package
b. Run the following command to decompress the PGPVerify software.
NOTE
Assume that the PGPVerify tool and public key file are stored in the /opt directory and the
signature file and software package are stored in the /opt/install.
Solaris:
# cd /opt
# bzip2 -d PGPVerify-sparc.tar.bz2
# tar xvf PGPVerify-sparc.tar
Linux:
# cd /opt
# tar xvfz PGPVerify-x86_64.tar.gz

c. Run the following commands to verify the signature file:

# ./PGPVerify -k KEYS -d install
NOTE
To verify a single file, run the following commands:
# cd /opt
# ./PGPVerify -k KEYS -f install/plugins-cloudtask-C01.zip.asc

[INFO]:Filter file in directory, please wait...
[PASS]:Good Signature. File path: install/plugins-cloudtask-C01.zip.asc,
Public key fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824.
[PASS]:Good Signature. File path: install/twain.dll.asc, Public key
fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824.
[PASS]:Good Signature. File path: install/buildcloud-proxy.zip.asc,
[PASS]:Good Signature. File path: install/buildcloud_pvmtrans.zip.asc,
[PASS]:Good Signature. File path: install/plugins-cicloud-C01.zip.asc,
[PASS]:Good Signature. File path: install/ConfigCenter.war.asc, Public
key fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824.
[PASS]:Good Signature. File path: install/watcher-wrapper.zip.asc,
[PASS]:Good Signature. File path: install/watcher.zip.asc, Public key
[PASS]:Good Signature. File path: install/rpm.war.asc, Public key
[PASS]:Good Signature. File path: install/buildcloud-rpm.zip.asc, Public
key fingerprint: B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824.
[INFO]: Verify Complete.
NOTE
In the preceding characters in bold, the RSA key ID is consistent with the public key ID. For a
certain file, if no "WARN" or "FAIL" character is contained in other information, the signature
file is valid.
NOTICE
----End
A.1.25 How to Fix Garbled Characters in the SUSE Linux

Command Output
Question
How do I fix garbled characters in the SUSE Linux command output?

NOTE
l Using the PuTTY or the server terminal window is recommended because local terminals that do not
support the character set configuration. For example, the CLI window of a Windows OS does not support
handling of garbled characters in a command output.
l If the ls command output contains garbled characters, the directory that contains the garbled characters is
created using another type of character set. After the character set is modified, the directory that contains
the garbled characters is normally displayed. Directories that do not contain garbled characters may
include garbled characters after the character set is modified. This does not affect operations on the
U2000. You need to pay attention only to the directory displayed in the current character set.
l If the length of displayed Chinese characters exceeds the CLI window width, garbled characters may
occur.
Answer
l Scenario 1: If you use PuTTY to fix the garbled characters, perform the following
operations to set the PuTTY character set.
a. Right-click on the PuTTY toolbar in the CLI window, choose Change Settings.
The PuTTY Reconfiguration window is displayed.
b. Choose Window > Translation to view the set from the Received data assumed
to be in which character set drop-down list.
NOTE
For PuTTY, a root user should use the Use font encoding character set, and an ossuser
should use the UTF-8 character set. If the current user uses the mapping character set but the
garbled characters are displayed, perform the following operations to modify the character se
l If the current character set is Use font encoding, change it to UTF-8.
l If the current character set is UTF-8, change it to Use font encoding.
l Scenario 3: If you fix the garbled characters using the server terminal window, perform
the following operations to modify the character set in the server terminal window:
Choose Terminal > Set Character Encoding in the server terminal window to view the
character set.
NOTE
For the SUSE Linux OS, a root user should use the GB2312 character set, and an ossuser should
use the Unicode(UTF-8) character set.
If the current user uses the mapping character set but the garbled characters are displayed, perform
the following operations to modify the character set:
For the SUSE Linux OS:
l If the current character set is GB2312, change it to Unicode(UTF-8).
l If the current character set is Unicode(UTF-8), change it to GB2312.
If the used OS has no mapping character set, choose Terminal > Set Character Encoding to add
the mapping character set and select it.
----End
A.1.26 Checking the NTP Service on Linux

This topic describes how to check the NTP service on Linux. Two commands are available to
query the NTP status: ntpq -p and rcntp status. The command outputs help you determine
whether NTP synchronization is normal.

Context
l You can run the rcntp status command as user root to check the running status of the
NTP service.
– If the command output contains running, the NTP service has started.
Checking for network time protocol daemon (NTPD):
running
NOTE
l If the NTP service has been started, port 123 corresponding to the service will also be
enabled. Run the netstat -an |grep 10.185.166.48:123 command to check whether port
123 used by the NTP service has been enabled on the current U2000 server.
10.185.166.48 is the ip address of the current U2000 server.
Information similar to the following is displayed means the port 123 has been enabled.
udp 0 0 10.185.166.48:123
0.0.0.0:* 5695/ntpd
l If no information displayed, means the port 123 has not been enabled. Run the service
ntp restart command to restart the NTP service and port 123 corresponding to the
service will also be enabled.
– If unused is displayed, the NTP service is not started.
unused
NOTE
If the NTP service is not started, run the service ntp start command to start the NTP service.
l You can run the date command as user root.
– Check whether the medium-level NTP server time and the upper-level NTP
server time are the same.
– Check whether the NTP client time and the upper-level NTP server time are the
same.
If they are the same, the NTP service is in the normal state.
l In the ntpq -p command output, the remote field specifies the address of the reference
clock source. in the return message of the ntpq -p command is the IP address of the
reference time source. It indicates the status of the reference time source.
l The ntptrace command traces the entire NTP synchronization link from the local
machine to the NTP server at the highest level.
Procedure
Step 1 Log in to OS as user root.
Step 2 In a command line interface (CLI), run the ntpq -p command to view the NTP clock source.
Step 3 Run the ntptrace command to view the NTP synchronization link.
----End
Result
l If the server has been configured as the NTP server with the highest stratum, information
similar to the following is displayed.
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .LOCL. 10 l 1 64 1 0.000 0.000 0.001

NOTE
l The preceding information indicates that the current server is the NTP server with the highest
stratum and is tracing the local time.
l The check of the NTP service takes about 5 minutes after the NTP server and NTP clients have
been started. In the ntpq -p command output, the remote field is not marked with an asterisk
(*). In the ntptrace command output, Timeout or Not Synchronized is displayed. Wait
5 minutes and then run the ntpq -p command or ntptrace command.
l If the server running on SUSE Linux is configured as the medium-level NTP server,
information similar to the following is displayed.
# ntpq -p
==============================================================================
*10.71.224.140 .LOCL. 16 u - 64 0 0.000 0.000
0.000
+LOCAL(0) 10 l 6 64 1 0.000 0.000
0.001
# ntptrace
localhost: stratum 2, offset 0.000049, synch distance 0.02863
10.71.224.140: stratum 1, offset -0.001166, synch distance 0.01024
NOTE
l In the ntpq -p command output, *10.71.224.140 specifies that the IP address of the NTP
server on which the host performs time synchronization is 10.71.224.140. The asterisk (*)
indicates that the status is normal. The value in the st column indicates that 10.71.224.140 is at
stratum 1.
l In the ntptrace command output, localhost: stratum 2 specifies that the host is at
stratum 2, and the IP address of the host at the upper level is 10.71.224.140 at stratum 1.
l If the server running on SUSE Linux is configured as an NTP client, information similar
to the following is displayed.
# ntpq -p
==============================================================================
*10.71.224.140 LOCAL(0) 2 u - 64 0 0.000 0.000
0.000
# ntptrace
localhost:stratum 3, offset 0.000035, sycnh distance 0.08855
10.71.224.140: stratum 2, offset 0.000224, synch distance 0.07860
10.161.94.212: stratum 1, offset 0.060569, synch distance 0.01036,
refid 'LCL'
NOTE
l In the ntpq -p command output, *10.71.224.140 specifies that the IP address of the NTP
server on which the host performs time synchronization is 10.71.224.140. The asterisk (*)
indicates that the status is normal. The value in the st column indicates that 10.71.224.140 is at
stratum 2.
l In the ntptrace command output, localhost: stratum 3 specifies that the host is at
stratum 3, the IP address of the host at stratum 2 is 10.71.224.140, and the IP address of the
host at stratum 1 is 10.161.94.212.

A.1.27 How to Use the FileZilla to Transfer Files by SFTP

Question
How do I use the FileZilla to transfer files by SFTP?
NOTE
l Before the U2000 is installed, use SFTP as the root user to transfer files.
l If the U2000 has been installed without security hardening, use SFTP as the ftpuser, ossuser, root
or another OS user to transfer files. This topic uses the root user as an example.
l If the U2000 has been installed with security hardening, use SFTP as the ftpuser user to upload files
to the /opt/backup/ftpboot directory under the root directory of the ftpuser user and then copy the
files to the specified directory. The operations of downloading files are similar.
Answer
Step 1 On a PC or laptop, double-click the shortcut icon of FileZilla client to open the FileZilla.
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
https://wiki.filezilla-project.org/Documentation 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.
– Enter a server IP address in the Host text box.
– Enter 22 in the Port text box.
– Select SFTP from the Server Type drop-down list.
– Select Ask for password from the Logon Type drop-down list.
– 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-1.

Figure A-1 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-2.
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-2 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-3, SFTP

connection is successful.
Figure A-3 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-4.
Figure A-4 Uploading files
Step 4 After the file is successfully uploaded, a success message is displayed, as shown in Figure
A-5.

Figure A-5 Successful file uploading
----End
A.1.28 What Can I Do If Logging In to the GUI Desktop Fails in

SUSE Linux
Question
What can I do if logging in to the GUI desktop fails in SUSE Linux?
The following error messages is displayed:
Answer
Step 1 Log in to the real-time desktop of a blade.
1. Logging in to the GUI of the MM910 management module.
2. Click KVM via MM. The Security Warning dialog box is displayed.

NOTE
– This step needs to be performed in an environment with JRE 1.7 or later installed.
– A 32-bit browser uses the 32-bit JRE, and a 64-bit browser uses the 64-bit JRE; otherwise, the
KVM window fails to be accessed through a browser.
– If the next page cannot be displayed on the Internet Explorer, switch to another browser or
close the current browser and log in to the controller card.
3. Click Yes. The blade management window is displayed.
4. Click to refresh the window.

5. Click the slot number where the blade resides, such as blade1. Choose Private Mode,
the real-time desktop of a blade is displayed.
NOTE
– Private Mode allows only one user to access and perform operations on the server.
– Shared Mode allows two users to access and perform operations on the server simultaneously.
One user can view the operations performed by the other user.
1. Click in the menu bar of the server real-time window.

2. Select Forced Power Cycle. Are you sure to perform this operation? is displayed.
3. Click Yes. The server is restarted. The startup takes about 3 to 5 minutes.
Step 3 Perform the following operations to log in to the SUSE Linx GUI Desktop:
1. When the start window is displayed, move the cursor to Failsafe - SUSE Linux
Enterprise Server 11 SP3 - 3.0.101-0.47.105-default .
2. Press Esc. The Exiting… dialog box is displayed.
3. Press Tab to select OK and press Enter to enter the GRUB window.
4. Press c to enter the CLI window.
5. Enter the following commands that the system is started in CLI mode.
grub> root (hd0,0)
grub> cat /grub/menu.lst
grub> kernel /vmlinuz-3.0.101-0.47.105-default root=/dev/vg_root/lv_root
vga=0x314 3
grub> initrd /initrd-3.0.101-0.47.105-default
grub> boot
6. When the following information is displayed, enter the root user name and password to
log in to the operating system.
Float166251 login: root
Password:
7. 7 Run the following command to start the GUI on a terminal:

# startx

Step 4 Optional: Re-install the login server.

NOTE
If an ISO installation disk that contains the same SP version as the SUSE Linux is available, perform the
following sub-steps to re-instasll the login server. If such an ISO installation disk is unavailable, you can
only perform Step 1 to Step 3 to log in to the SUSE Linux GUI through the text mode interface.
1. Click the icon in the tool bar on the blade desktop to mount the same ISO installation
disk as that for the operating system with the SP version.
If Low Disk Space is warned, please run the following commands to remove log files.
# cd /var/log
# rm –rf messages
2. Enter the YaST window.

3. Choose Software > Software Repositories to enter the Software Repositories window.
Ensure that the following information is displayed.
4. Exit the Software Repositories window. Choose Software > Software Management to
enter the Software Management window.
5. Enter login into the text box on the Search tab. The list of related software packages will
be displayed in the right pane. Click the login software package to reinstall the login
service.
6. Run the following command to check runlevel. Ensure that its value is 5.
# cat /etc/inittab
The default runlevel is defined here
Id:5:initdefault:
7. Restart the operating system.

# shutdown -r now
----End
A.2 System Settings of the Huawei RH series rack server

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

A.2.1 How Do I Use iMana/iBMC IP to Log In to a Remote

Huawei RH series rack server
Question
How do I use iMana/iBMC 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/iBMC module in the address
bar. The iMana/iBMC 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/iBMC 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/iBMC on the Huawei RH series rack server if the default
IP of iMana/iBMC changes.
Step 2 Enter the user name and the password of iMana/iBMC 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/iBMC User Root. )
l If log in to the Huawei RH5885H V3 or Huawei RH2288H V2 server through iMana,
display the following page:
l If log in to the Huawei RH5885H V3 server through iBMC, display the following page:

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.
display the following page:

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
l If the Safe warning dialog box is displayed, click Permission.

l If a message is displayed indicating that the application is prohibited to run, choose Start >
Control Panel and click Java. In the Java Control Panel dialog box, click the Security tab, Edit
Site List, and Add, enter an iMana/iBMC IP address, such as http://192.168.2.100, and click OK.
Click OK, restart the IE Explorer, and log in to iMana/iBMC again.
----End
A.2.2 How to View the IP Address of the iMana/iBMC on the

Huawei RH series rack server
Question
How do I view the IP address of the iMana/iBMC 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/iBMC.

operations:
a. Choose Server Mgmt tab.
b. Choose BMC network configuration, and press Enter to access the BMC
network configuration window to view the IP address.
operations:

b. Select BMC Configuration, and press Enter to access the BMC Configuration
window to view the IP address.
operations:
a. Choose Server Mgmt tab.
b. Choose BMC network configuration, and press Enter to access the BMC
network configuration window to view the IP address.

operations:
b. Select iBMC Configuration, and press Enter to access the iBMC Configuration
window to view the IP address.

----End
A.2.3 How to Change the Password of iMana/iBMC 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/iBMC module in the address bar.
The window for logging in to iMana is displayed.
NOTE
The default IP address of iMana/iBMC 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/iBMC on the Huawei RH series rack server if the default
IP of iMana/iBMC changes.
Step 2 Enter the user name and the password of iMana/iBMC 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 Open the configuration page of the root user.

choose Configuration > User from the navigation tree. Click corresponding to the
root user.

l If log in to the Huawei RH5885H V3 server through iBMC, choose Config > Local
User from the navigation tree. Click corresponding to the root user.
l If log in to the Huawei RH2288H V3 server through iBMC, choose Config > User
Settings from the navigation tree. Click corresponding to the root user.
Step 4 Change the password for the root user.

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:
– The password contains a minimum of 8 characters and a maximum of 20 characters.
– At least one space or one special character: `~!@#$%^&*()-_=+\|[{}];:'",<.>/?
– At least two of the following combinations: lowercase letters a to z, uppercase letters A to Z, and
digits 0 to 9.
– The password cannot be the same as the user name or the reverse of the user name.
the Modify User Information page is displayed. Enter the modification information and
click OK.
l If log in to the Huawei RH5885H V3 server through iBMC, enter the current password
for the root user in the Current User Password text box. Select You can change the
password only after selecting the check box. Enter the new password for the root user
in the Password and Confirm text boxes. Click Save.
l If log in to the Huawei RH2288H V3 server through iBMC, enter the current password
for the root user in the Current User Password text box. Select You can change the
password only after selecting the check box. Enter the new password for the root user
in the Password and Confirm text boxes. Click Save.

----End
A.2.4 How to Solve iMana/iBMC Problems

Question
How do I solve iMana/iBMC problems?
Answer
The following problems may exist on the iMana/iBMC and you must take measures to these
problems:
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/iBMC page and
l After a user closes the Internet open the Remote Virtual Console
Explorer and Remote Virtual window. The original session is still
Console windows, the user cannot there.
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/iBMC
page.

3 The Caps indicator on the keyboard is Press Caps Lock.

on, but the entered letter is a lower-case The indicator on the right of caps above
letter. 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.
4 The Num indicator on the key board is Press Num Lock.

on, 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 Remote Virtual Console,
click Ctrl+Alt+Shift. To exit from
the single-pointer mode, click

and clear theSingle 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.
6 No operation is performed on the server Enter the iMana/iBMC address in the

for more than 5 minutes after a login to address bar of the Internet Explorer.
the iMana/iBMC management window. Then enter the user name and password
The system then automatically displays in the iMana/iBMC login winidow.
an error message indicating session The cause of the fault is that the default
timeout and exits from the login. period for the iMana/iBMC 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/iBMC management window
according to on-site requirements and
choose Configuration > Service > Web
Server to set Timeout Period.
7 After the iMana/iBMC login window is Enter the iMana/iBMC address in the
accessed and login is not yet performed, address bar of the Internet Explorer to
the system automatically enters the re-open it.
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 Virtual Console to exit from the
perform 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-6, the mappings between the physical and logical network interfaces
for the Huawei RH2288H V2 server are described as follows:
l The Huawei 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.
Figure A-6 Mappings between physical and logical network interfaces on the Huawei
RH2288H V2 server
l eth0, eth1, eth2, and eth3 are network interfaces on the integrated NIC. The associated

NOTE
The Huawei RH5885H V3 server supports twelve extended NICs with four interfaces. For the six NICs
on the right, the mapping logical interfaces from top down are: eth8 to eth11, eth4 to eth7, eth12 to
eth15, eth16 to eth19, eth20 to eth23, and eth24 to eth27. For the six NICs in the middle, the mapping
logical interfaces from top down are: eth28 to eth31, eth32 to eth35, eth36 to eth39, eth40 to eth43,
eth44 to eth47, and eth48 to eth51.
RH5885H V3 server
l The Huawei RH2288H V3 server is integrated with one NIC. The associated logical
network interfaces on the integrated NIC are named eth0, eth1, eth2, and eth3.
RH2288H V3 server

A.2.6 Formatting disks (Huawei RH5885H V3 or Huawei

RH2288H V2)
This topic describes how to formatting disks.
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:
– The IP address of the iMana is available. For details about how to set the IP address
of the iMana, see 4.6.1.1 Configuring the iMana IP Address Through iMana
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:
a. Log in to the server. For details, see A.2.1 How Do I Use iMana/iBMC IP to Log
In to a Remote Huawei RH series rack server.
b. Click on the toolbar which is right above Remote Virtual Console and select
Cold Reset.
c. In the dialog box that is displayed, click Yes to restart the server.
Step 2 On Huawei RH5885H V3 server, ignore the following operations; If log in to the Huawei
RH2288H V2 server through iMana, 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.

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.

l On Huawei H2288H V2 server, the following window is displayed.
l On Huawei RH5885H V3 server, the following window is displayed.

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.
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.
– On Huawei H2288H V2 server, the following window is displayed.


l In local mode, press Ctrl+Alt+Delete to restart the server.
a. Click on the toolbar which is right above Remote Virtual Console and select
Cold Reset.
b. In the dialog box that is displayed, click Yes to restart the server.
----End

A.2.7 Formatting disks (Huawei RH2288H V3 or Huawei

RH5885H V3)
This topic describes how to formatting disks.
Prerequisites
– The IP address of the iBMC is available. For details about how to set the IP address
of the iBMC, see 4.6.1.2 Configuring the iBMC IP Address Through iBMC
Procedure
Reset or Forced System Reset.
NOTE
This screen stays for a short period of time. Press Ctrl+R the moment you see Ctrl+R on the screen. If
Ctrl+R is not pressed, restart the system.
Step 3 Press Ctrl+R as prompted to access the BIOS window.
Step 4 Place the cursor over SAS3108 (Bus 0x01, Dev 0x00) by using up and down arrow keys and
press F2. The configuration tab is displayed.

Step 5 Select the Clear Configuration tab by using up and down arrow keys and press Enter. A
page asking whether to clear configurations is displayed.
NOTICE
Clear Configuration will clear the previous RAID configurations, resulting in data damage
or loss in hard disks. Therefore, before performing this operation, determine whether the data
in hard disks can be cleared.
Step 6 Select YES and press Enter. The following page is displayed after RAID configurations are
cleared.


----End
A.2.8 Viewing Hard Disk Information (Huawei RH5885H V3 or

Huawei RH2288H V2)
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:
– The IP address of the iMana is available. For details about how to set the IP address
of the iMana, see 4.6.1.1 Configuring the iMana IP Address Through iMana
Procedure

Cold Reset.
NOTE


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:
– IDs of eight slots from Slot: 0 to Slot: 7 are displayed.
– 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.



Cold Reset.
----End
A.2.9 Viewing Hard Disk Information (Huawei RH2288H V3 or

Huawei RH5885H V3)
This topic describes how to view hard disk information.
Prerequisites
– The IP address of the iBMC is available. For details about how to set the IP address
of the iBMC, see 4.6.1.2 Configuring the iBMC IP Address Through iBMC
Procedure

NOTE
This screen stays for a short period of time. Press Ctrl+R the moment you see Ctrl+R on the screen. If
Ctrl+R is not pressed, restart the system.
Step 3 Press Ctrl+R as prompted to access the BIOS window.

NOTE
The following figure assumes that RAID is not configured for hard disks. The actual screen may be
different due to the RAID configuration. You only need to focus on the hard disk information on the
page. A total of 8 hard disks numbered from 00 to 07 are displayed.

----End

A.2.10 How to Upgrade the System Controller Firmware Version

for Huawei RH5885H V3 and RH2288H V2 Servers?
Question
This topic describes how to upgrade the controller iMana fireware version of Huawei
RH5885H V3 and RH2288H V2 servers. When the controller iMana firmwave version of
Huawei RH5885H V3 or Huawei RH2288H V2 is so early that alarms fail to be reported. A
controller has to be closed during an upgrade.
Answer
Step 1 Download the patch package.
NOTE
The following uses Huawei RH5885H V3 server as an example (The method of downloading the patch
package and upgrading the firmware version for Huawei RH5885H V3 server is the same as that for
Huawei RH2288H V2 server):
1. Log in to http://support.huawei.com/carrier. Enter RH5885H V3 in the search box on
the Product Support to access the Search Results page.
2. Choose Carrier IT > Server > Fusion Server > Rack Server > RH5885H V3 from
Filter by Product in the navigation tree. Click Software to access the Software page.
3. Select the firmware upgrade package RH5885H V3-iMana-V722.zip to download it and
the mapping PGP file.
4. Use the PGPverify to verify correctness of the firmware upgrade package. For details,
see A.1.24 How Do I Verify Downloaded Software Packages Using the PGPVerify
Software.
5. Decompress the firmware upgrade package.
Step 2 Open the Internet Explorer of a PC. Enter the iMana IP address in the address bar to access
the iMana login page. Enter the user name and password to log in to the control card page.
Step 3 Choose Configuration > Firmware Upgrade to access the Firmware Upgrade page.
Step 4 On the Firmware Upgrade tab, click Browse of Upgrade File Name and select the local
directory where the firmware upgrade package is stored.
NOTE
The firmware upgrade package to be uploaded must be an *.hpm file.
Step 5 Set Take-effect Mode to Restart Immediately.

Step 6 Click Upgrade and click Yes. The system starts to upload the firmware upgrade package to
the server and then starts to perform the upgrade.
After the upgrade is complete, the server automatically restarts.
----End
A.2.11 How to Upgrade the System Controller Firmware Version

for Huawei RH2288H V3 server and Huawei RH5885H V3 server?
Question
This topic describes how to upgrade the controller fireware version of Huawei RH2288H V3
server and Huawei RH5885H V3 server. When the controller iBMC firmwave version of

Huawei RH2288H V3 server and Huawei RH5885H V3 server is so early that alarms fail to
be reported. A controller has to be closed during an upgrade.
Answer
Step 1 Download the patch package.
NOTE
The following uses Huawei RH2288H V3 server as an example (The method of downloading the patch
package and upgrading the firmware version for Huawei RH5885H V3 server is the same as that for
Huawei RH2288H V3 server server):
1. Log in to http://support.huawei.com/carrier. Enter RH2288H V3 in the search box on
the Product Support to access the Search Results page.
2. Choose Carrier IT > Server > Fusion Server > Rack Server > RH2288H V3 from
Filter by Product in the navigation tree. Click Software to access the Software page.
3. Select the firmware upgrade package RH2288H V3-iBMC-V206.zip to download it and
the mapping PGP file.
4. Use the PGPverify to verify correctness of the firmware upgrade package. For details,
see A.1.24 How Do I Verify Downloaded Software Packages Using the PGPVerify
Software.
5. Decompress the firmware upgrade package.
Step 2 Open the Internet Explorer of a PC. Enter the iMana IP address in the address bar to access
the iBMC login page. Enter the user name and password to log in to the control card page.
Step 3 Choose System > Firmware Upgrade to access the Firmware Upgrade page.
Step 4 On the Firmware Upgrade tab, click Browse of Upgrade File Name and select the local
directory where the firmware upgrade package is stored.
NOTE
The firmware upgrade package to be uploaded must be an *.hpm file.
Step 5 Set Select iBMC Boot Mode Used After the iBMC Firmware of the Target Version Is
Uploaded to Immediately restart automatically.
Step 6 Click Start Upgrade and click Yes. The system starts to upload the upgrade package to the
server and then starts to perform the upgrade.
After the upgrade is complete, the server automatically restarts.
----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.
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)?
Answer
NOTE
IBM Server.
NOTE

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


NOTE
trust this site.
be displayed.
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.
----End
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
IBM Server.
NOTE

M3).
NOTE
Step 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
The remote control desktop consists of two parts: virtual media window and desktop display
window.

NOTE
trust this site.
solve the problem.
l If Use the ActiveX Client with Microsoft Internet Explorer is unavailable, just click Start
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 IBM server.
NOTE
A common monitor is enough.
Step 2 Press the power button of the IBM server to restart it.
Step 3 Wait about 1 minute after the IBM System X window is displayed. The <F1> Setup option is
displayed.

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

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

Step 7 Use arrow keys to select Network Configuration press Enter and access the page for
modifying the IMM IP address.
l For IBM X3850 X5, show as follows:

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
IBM Server.
NOTE

system security, modify the default password and remember the new password.
Step 3 Click IMM Management > Users.
Step 4 In the displayed User Accounts page, click Global Login Settings. Select Custom security
settings from Account security level, and set the Password expiration period (days)to 0
and other parameters to the maximum value. Then click OK.
Step 5 In the User Accounts page, click USERID.

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

Step 7 Click OK.
----End

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
IBM Server.
NOTE

password has been changed, enter the new password.
NOTE
Step 4 Choose Login Profiles from the navigation tree and click Global Login Settings. Select
Custom security settings from Account security level, and set the Maximum Password
Age to 0 and other parameters to the maximum value. Then click Save.
Step 5 Choose Login Profiles from the navigation tree and click USERID.
Step 6 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.

Step 7 Enter the password again in Confirm password.
Step 8 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 The procedure is as follows:

respond. 1. Right-click the Internet Explorer icon
l After a user clicks the Internet Explorer on the taskbar to close the Internet
or Video Viewer icon on the taskbar, Explorer. If the Internet Explorer is
the Internet Explorer or Video Viewer still open, stop the iexplore.exe
window is not displayed. process on the Processes tab page in
l The Internet Explorer closes the Task Manager.
automatically. 2. Open the Internet Explorer.
l After a user closes the Internet 3. Access the IMM page and open the
Explorer and Video Viewer windows, Video Viewer window. The original
the user cannot open the Video Viewer session is still there.
window.
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.

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 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 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
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.
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 or laptop. Open the Video Viewer
that the Video Viewer window does not window on a PC or laptop for each server
respond. when you operate multiple servers.

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-9 Mappings between physical and logical network interfaces on the IBM X3650
M4
Example 2: In Figure A-10, the mappings between the physical and logical network
interfaces 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.
X5

Example 3: In Figure A-11, the mappings between the physical and logical network
interfaces 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.
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


NOTE
If MegaRAID BIOS Config Utility Foreign Configuration window is displayed, click Clear.
NOTE
– 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.
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 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.
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
– The default user name is USERID.

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

NOTE
– 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.
– Do not close the ActiveX KVM Client dialog box. Otherwise, the Video Viewer dialog box
cannot be displayed.
– 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.
– If Use the ActiveX Client is unavailable, just click Start remote control in single-user mode
to access the remote control desktop.
– Keep the default values of other parameters unchanged.
– 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.
– 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.
NOTE
– If a message asking you whether to continue is displayed, click Yes.

– If Reboot is unavailable, choose Tools > Power > On and then choose Tools > Power >
5. Start the IBM server. After the basic input/output system (BIOS) check is completed, the

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.
7. Click Start to access the WebBIOS window.

NOTE
NOTE
– IDs of eight slots from Slot: 0 to Slot: 7 are displayed.
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
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.
Prerequisites
Context
NOTE
again.

Procedure
NOTE

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.
The remote control desktop consists of two parts: virtual media window and desktop
display window.
NOTE
– If a dialog box is displayed asking you to install plug-in, click Install.

– 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
NOTE

NOTE
habits.

NOTE

NOTE
– 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.
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
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.
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.
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.
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.

NOTICE

NOTE
5. Click Accept.
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
NOTE

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.

NOTE
– 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.
– Do not close the ActiveX KVM Client dialog box. Otherwise, the Video Viewer dialog box
cannot be displayed.
– If Use the ActiveX Client is unavailable, just click Start remote control in single-user mode
to access the remote control desktop.
– Keep the default values of other parameters unchanged.
– 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.
– 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.
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.
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

NOTE
– Wait about 5 minutes until BIOS information about the RAID is displayed. Do not perform
any operation when the IBM System X window is displayed.
– 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.

NOTE
habits.

NOTE
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.
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
Context
NOTE
again.
Procedure
NOTE

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.
The remote control desktop consists of two parts: virtual media window and desktop
display window.
NOTE
– If a dialog box is displayed asking you to install plug-in, click Install.

– 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.
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.
15. Press Enter. Select Commit Changes using the arrow keys and press Enter to save the
settings.
NOTE


NOTE

NOTE
habits.

NOTE

NOTICE

NOTE
5. Click Accept.

Step 6 Click Exit to exit the WebBIOS window. The Exit Confirmation dialog box is displayed,
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.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
– Set parameters in the Required SSL Certificate Data area as prompted. The following figure
shows examples of the parameter settings.
– The Optional SSL Certificate Data parameter does not need to be set.

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
l If HTTPS needs to be disabled and HTTP needs to be used, clear the selection of the select Enabled
HTTPS server. Then execute Step 4.2 through Step 4.3.

login window.
NOTE
If a security certificate error is displayed when HTTPS is used for web page access, ignore it and
continue the operation.
----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

M3).
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:
1. Click Generate a New Key and a Self-signed Certificate.
2. Set the related parameters.
NOTE
– Set parameters in the Certificate Data area as prompted. The following figure shows
examples of the parameter settings.
– 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.

NOTE
l During restart of the IMM, run the ping IMM IP address -t command on the CLI of the PC or
l If HTTPS needs to be disabled and HTTP needs to be used, select Disabled from the HTTPS
Server drop-down list. Then execute Step 5.2 through Step 5.7.
login window.
NOTE
If a security certificate error is displayed when HTTPS is used for web page access, ignore it and
continue the operation.
----End
A.4 Sybase Database

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

This topic describes the FAQs about the startup and shutdown of the Sybase database.
A.4.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 in the single-server
system:
1. Log in to the OS as user ossuser.
2. Run the following commands to disable the Sybase database service:
# su - dbuser
$ 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.
1> shutdown SYB_BACKUP 2> go 1> shutdown 2> go
3. 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.4.1.2 How to Start the Sybase Database Service
Question
How do I start the Sybase database service?
Answer
l Perform the following operations to start the Sybase database service in the single-server
system:
a. Log in to the OS as user ossuser.
b. Run the following commands to start the Sybase database service:
# su - dbuser
c. Run the following command to check whether the Sybase database service is
running:
$ ./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
ASE-15_0/bin/backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install
ASE-15_0/bin/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 service is running.
----End
A.4.1.3 How to Verify That the Sybase Database Is Running
Question
How do I verify that the Sybase database is running?
Answer
Step 1 Log in to the OS as user ossuser.
Step 2 Enter the CLI and run the following commands to check the Sybase process status:
# su - dbuser
$ ./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
l when NMS is not installed: If the displayed information contains /opt/sybase/ASE-15_0/bin/

backupserver -SDBSVR_back, and /opt/sybase/ASE-15_0/bin/dataserver -sDBSVR, the Sybase
database has been started.
l when NMS is installed: 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.4.2 Sybase Database Maintenance

This topic describes the FAQs about the Sybase database maintenance.
A.4.2.1 How to Verify That the Sybase Database Has Been Installed
Question
How do I verify that the Sybase database has been installed?
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.4.2.2 How to
Check the Sybase Database Version.
l Verify that the Sybase database is running. For details, see A.4.1.3 How to Verify That
the Sybase Database Is Running. For details about how to start the Sybase database,
see A.4.1.2 How to Start the Sybase Database Service.
----End
A.4.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.1.1 How to
Change the OS User Password.
Step 2 Run the following commands:

NOTE

In order to enhance the security of the database after the U2000 is installed, the sa user may be manually
Step 3 Run the following commands to check the Sybase database version:
1> use master
2> go
1> select @@version
2> go
NOTE
There must be a space between select and @ in the select @@version command.

-----------------------
Adaptive Server Enterprise/15.7/EBF 26397 SMP SP138 /P/x86_64/Enterprise Linux/

ase157sp138x/4002/64-bit/FBO/Mon Aug 29 20:46:15
2016
(1 row affected)
The preceding message indicates that Sybase database version is SYBASE 15.7.
NOTE
EBF 26397 indicates the latest Sybase patch. The earlier Sybase patches are not displayed.
----End
A.4.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
A.4.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
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:
– The password contains a minimum of eight characters and a maximum of 30
characters.
Other special characters are not supported. Do not include other special
characters, such as ()|<>&`!$\"%'=;,space in passwords.
– The password must be different from the user name or the user name in reverse order
and cannot contain the complete user name (case-insensitive).
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.4.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?

NOTICE
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 system as user ossuser and run the following commands to end the U2000
processes:
$ ./stopnms.sh
NOTE
...
...
NOTE
been started.
# su - ossuser
$ ./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. 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.
– The password must be different from the user name or the user name in reverse order and
cannot contain the complete user name (case-insensitive).
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
A.4.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.7/EBF 26397 SMP SP138 /P/x86_64/Enterprise Linux/
ase157sp138x/4002/64-bit/FBO/Mon Aug 29 20:46:15
2016
(1 row affected)
64-bit indicates the bit number of the Sybase database.
----End
A.4.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
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.4.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 MSuite is stopped. For details about how to end processes on the MSuite server, see
How to End Processes on the How to End Processes on the MSuite Server.
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.
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.
Procedure
Step 1 Log in to the server as the root user.
NOTE
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
– 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 length of the
customized user name must be less than 17 characters.
– 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.

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.
– The password must be different from the user name or the user name in reverse order and
cannot contain the complete user name (case-insensitive).
The following is displayed:
Warning: After this operation is successfully performed, the current database
administrator account fails.
To continue, enter "yes". To exit, enter other characters:
6. Input yes.
If the following information is displayed, the replacement user for the sa user is created
successfully.
The command is executed successfully.
Success to modify dba user.
NOTE
If the information Success to modify dba user. is displayed, the automatic database growth parameter
is set successfully.
----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.
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.5 U2000 System

This topic covers FAQs about the U2000 system.
A.5.1 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.
1. Ensure that the MSuite server has been started.
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. Switch to the ossuser user and run the following commands to start the
MSuite server if it is not running:
# su - ossuser
$ ./startserver.sh
NOTE
l 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 as user ossuser through VNC.
$ cd /opt/oss/client/engineering
$ ./startclient.sh
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's IP address/cau/
(recommended for higher security) or http://server's IP address/cau/ in the address box of
the Internet Explorer, and press Enter to access the Web installation page. For details, see
Installing a U2000 Client in CAU ModeInstalling a U2000 Client in CAU Mode in the
U2000 Client Software Installation Guide.
2. If you upgrade the U2000 client software using the CAU, the MSuite client is also
upgraded.
– IP Address:
n To log in to the local MSuite server, use the default IP address 127.0.0.1.
n 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.
– 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.
– User Name: The default user name is admin.
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.5.2 How to End Processes on the MSuite Server
Question
How do I end processes on the NMS maintenance suite server?
Answer
Run the following commands as the ossuser user:
$ ./stopserver.sh
A.5.3 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.
Prerequisites
MSuite processes are running. If they are not running, start them by following the steps
provided in A.5.4 Starting the Process of the MSuite Server.
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.

NOTE
The initial password is Changeme_123.

The rules for modifying a password are as follows:
l The password contains a minimum of 8 characters and a maximum of 30 characters.
l The password must contain four of the following combinations:
– At least one special character ~!@#$%^&*()-_=+\|[{}];:"',<.>/?
l The password cannot be the same as the user name written in either the forward or backward
format.
If the password does not meet requirements, an error message will be displayed.
Step 5 Click OK. The password is changed.
----End

Operations Through the CLI

On Solaris or SUSE Linux OS, if you fail to log in to the MSuite GUI desktop system, change
the password of the administrator of the database through the CLI.
The operations in CLI mode are as follows:
On Solaris or SUSE Linux OS, run the following commands as user ossuser (If you have
logged in as the root user, relog in to the OS as user ossuser, you cannot run the su - ossuser
command to switch to the ossuser user to run the following command.):
$ cd /opt/oss/client/engineering
$ ./startclient.sh deploy
-ip 127.0.0.1 -port 12212 -username admin changemsuitepassword
Enter the MSuite login password[]:
Enter the old MSuite server password[]:
Enter the new MSuite server password[]:Enter the new MSuite server password
according to the prompted password rule.
Enter the confirm MSuite server password[]:
NOTE
l username: the user name of the MSuite.

l The default user name of the MSuite is admin and the default password is Changeme_123. If the
system security, modify the default password and remember the new password. For details, see the
MSuite help.
l If the new MSuite password does not meet the verification rules, a message will be displayed asking
you whether to continue. If you want to continue, enter Y. If you do not want to continue, enter N.
l If the following information is displayed, the MSuite password has been changed successfully.
Succeeded in changing the password.
After changing the MSuite password, start U2000 server processes.
A.5.4 Starting the Process of the MSuite Server

This topic describes how to start the process of the MSuite server.
Context
Generally, the process of the MSuite server is not started with the OS startup. If the process is
not started, perform the following operations to start it.
Procedure
l Run the following command as user ossuser to verify that the MSuite server is running:
$ ps -ef | grep java
The MSuite server is running if /opt/oss/OSSJRE/jre_sol/bin/java -server or /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
----End

A.5.5 How to Verify That the Processes of the U2000 Single-Server

System Are Running on SUSE Linux
Question
How do I verify that the processes of the U2000 single-server system are running on SUSE
Linux?
Answer
Step 1 Log in to the server as user ossuser.
Step 2 Check the U2000 processes.
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
----End
A.5.6 How to Start the Processes of the U2000 Single-Server

System on SUSE Linux
Question
How do I start the processes of the U2000 single-server system on SUSE Linux?
Answer
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb

NOTE

$ ./startnms.sh
----End
A.5.7 How to End the Processes of the U2000 Single-Server

System on (SUSE Linux)
Question
How do I end the processes of the U2000 single-server system on (SUSE Linux)?
Answer

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
$ ./stopnms.sh
----End
A.5.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
In the single-server system: The U2000 is installed based on the bill of material (BOM).
l If the U2000 license BOM is available, the U2000 needs to be installed according to the
license BOM. Technical support engineers should change the IP address, install the
license on the U2000, and then use the U2000.
l If the U2000 license BOM is unavailable, only the OS needs to be installed.
A.5.9 Which Installation Packages Are Required for U2000

Installation
Question
Which installation packages are required for U2000 installation?
Answer
Prepare installation packages according to the U2000 installation scheme.
Table A-4 Software required for installation

Software Medium Description
SUSE Linux OS You can install the SUSE Linux OS by using the quick installation
DVD.
Quick installation DVD:
U2000version_server_os_sles11_x64_dvd1
Quick RAID You can configure RAID by using the quick RAID configuration
configuration DVD DVD.
Quick RAID configuration DVD: Sles_server_raid_x64_dvd1
SetSuse software Installation package:

package U2000version_VPPSetSuse11V300R003C22SPC200.tar
It is used to enhance the security of SUSE Linux OS.
Database Installation DVD or installation package

l Installation DVD: U2000version_server_db_sles_x64_dvd3
l Installation package:
U2000version_server_db_linux_sybase.tar

U2000 server Installation DVD or installation package

software l Installation DVD: U2000version_server_nms_sles_x64_dvd4
l Installation package:
NOTE
Prepare software packages required by the components to be installed.
– Basic component:
U2000version_server_nmsbase_sles_x64.7z
It must be available. It is used to install the U2000.
– Core component:
U2000version_server_nmscore_sles_x64.7z
It must be available. It is used to install the U2000.
– Transport domain component:
U2000version_server_nmstrans_sles_x64.7z
It is required only if the U2000 needs to manage Huawei
transport equipment. Huawei transport equipment
includes:
– MSTP equipment
– WDM equipment
– NA WDM equipment
– Submarine equipment
– RTN equipment
– PTN equipment
NOTE
Software packages for the transport and IP components must
be available so as to manage PTN 6900 and PTN 7900 series
NEs.
– IP domain component:
U2000version_server_nmsip_sles_x64.7z
IP equipment. Huawei IP equipment includes:
– ATN Series Equipment
– Routers
– Switches
– Metro service equipment
– Broadband access equipment
– VoIP gateways
– Firewalls
– Service inspection gateway
– SVN equipment
– Internet Cache System
– Access domain component:
U2000version_server_nmsaccess_sles_x64.7z


access equipment. Huawei access equipment includes:
– FTTx equipment
– MSAN equipment
– DSLAM equipment
– BITS equipment
A.5.10 How to Set the Communication Mode on the U2000 server

for the Single-Server System (SUSE Linux)
Question
The U2000 server and client can communicate with each other in common or Security Socket
Layer (SSL) mode. How to set the common or SSL mode?
Answer
Step 1 Log in to the OS on the U2000 server as ossuser user and do as follows to query the
communication mode in use:
$ ssl_adm -cmd query
Step 2 Run the following command to stop U2000 processes.

$ ./stopnms.sh
Step 3 Set the communication mode for the U2000 server and client.
$ ssl_adm -cmd setmode mode parameter
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 is successful.

Operation succeeded. Please restart all services for the settings to take effect.
NOTE
You can ignore messages displayed before this message because they do not affect the operation result.
Step 4 If you need to install the client in CAU mode after the server communication mode is set, you
must perform the following operations as the ossuser user:
$ cd /opt/oss/cau/bin

$ bash cau.sh
Step 5 Run the following command to start U2000 processes.

$ cd
/opt/oss/server/platform/bin
$ ./startnms.sh
----End
A.5.11 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:
b. Run the cd License file save path command to access the path where the license file
is stored.
c. 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.
n 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
n 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.5.12 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, if no security hardening is performed on the OS, you must upload
the U2000 license file as the ossuser user. Otherwise, the U2000 license file will be invalid. If
security hardening is performed on the OS, FTP/SFTP rights of ossuser will be disabled. In
this case, you need to upload files to the backup directory in the FTP root directory as the
l Binary files, such as the U2000 installation program and database interfaces file, are transferred in
binary mode.
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.5.13 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:
# 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:

# 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.5.14 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. For more information
about the software, see the software Help or log in to the official website http://
www.nero.com/enu/support/ of the software for technical support.

l An empty DVD is available.
Answer
Step 1 See A.1.24 How Do I Verify Downloaded Software Packages Using the PGPVerify
Software to verify correctness of the obtained 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.
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.5.15 How to Check the U2000 Version

Question
How to check the U2000 version?
Answer
l In Solaris and Linux, run the following commands as the ossuser user:


...
...
The preceding displayed information shows the U2000 version.
NOTE
Only the U2000 SPC version number can be viewed on this way. If the version has been installed
with a CP patch, perform View the CP version of the U2000 to view more version information
about the U2000 software.
l If the version has been installed with a CP patch, you can use the following method to
view the CP version of the U2000.
The version information is stored on the U2000 server as a configuration file named the
version number. Access the following directory to view all version information:
In Solaris and Linux: $IMAP_ROOT/patch, such as /opt/oss/server/patch.
NOTE
The CP version number can be obtained only by accessing the directory. One version can have
either 0 patch or multiple CP patches.
For example, if the directory contains the V100R009C00CP3011.cfg,

V100R009C00CP3013.cfg, and V100R009C00SPC301.cfg files, the version has been
installed with two CP patches and one SPC patch.
----End
A.5.16 How to Resolve the U2000 SyslogCollectorDM Service

Startup Failure Due to a Port Conflict
Question
The UDP port 514 is used by the syslog service in the SUSE Linux OS to receive remote logs.
After you install the U2000 on the operating system, the SyslogCollectorDM service of the
U2000 also uses port 514 to receive remote logs. If the syslog service is enabled in the SUSE
Linux OS before an upgrade, a port conflict occurs after the upgrade. As a result, the
SyslogCollectorDM service is disabled and the attempt to start the SyslogCollectorDM
service fails.
Answer
To ensure that the NE logs are properly displayed on the U2000 client, disable the remote log
receiving function for the syslog service in the SUSE Linux OS, and allow the U2000
SyslogCollectorDM service instead of the OS receives the remote logs. Perform the following
operations on the nodes where the SyslogCollectorDM service has been deployed to ensure
that UDP port 514 is not used by the OS.
1. Use the PuTTY to log in to the U2000 server as user ossuser in SSH mode.
2. Run the following command to set environment variables.

3. Run the following command to enable the U2000 SyslogCollectorDM service:

$ svc_adm -cmd enable -svcname SyslogCollectorDM
– If the SyslogCollectorDM service is started, the problem is not caused by the port
conflict. The procedure ends.
– If the SyslogCollectorDM service is not started, perform .4.
4. Run the following command to switch to user root.
$ su - root
5. Run the following command to view the usage of port UDP 514:
# lsof -i:514
If the following information is displayed, port UDP 514 has been occupied by the syslog
service of the OS:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
syslog-ng 8786 root 5u IPv4 8511952 UDP *:syslog
6. Disable the remote log receiving function for the syslog service in the SUSE Linux OS.
a. Run the following command to stop the syslog service on the OS:
# service syslog stop
b. Run vi to modify the /etc/syslog-ng/syslog-ng.conf file.
Comment on the udp<ip<"0.0.0.0"> port<514>> line. Run :wq! to save
the file and exit.
unix-dgram("/dev/log");
#
# uncomment to process log messages from network:
#
# udp<ip<"0.0.0.0"> port<514>>;
c. Run the following command to restart the syslog service:

# service syslog start
7. Run the following command to switch to user ossuser.
# su - ossuser
8. Run the following command to set environment variables.
9. Run the following command to check whether the U2000 SyslogCollectorDM service is
running.
$ svc_adm -cmd status
If the service is not running, run the following command to start the SyslogCollectorDM
service:
$ svc_adm -cmd startsvc SyslogCollectorDM
$ su - root
11. Run the following command to view the usage of port UDP 514 again:
# lsof -i:514
If the following information is displayed, the U2000 SyslogCollectorDM service has
occupied this port.

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME

SyslogCol 11101 root 31u IPv4 8519207 UDP *:syslog
A.5.17 How Do I Obtain Third-Party Software and Hardware

Materials
Question
How do I obtain third-party software and hardware materials?
Answer
The U2000 running depends on third-party software and hardware. To help you better
maintain third-party software and hardware, handle related faults, and acquire knowledge, you
can obtain corresponding materials from third-party websites. Table A-5 lists the URLs of
commonly seen third-party software and hardware.
NOTE
Websites of third-party materials may vary with different reasons. The correct URLs are subject to the
official release.
Table A-5 Websites for obtaining software and hardware materials

Type Category Model Website URL
Operating system Operating system Solaris 10 http://www.oracle.com/

technetwork/
documentation/
solaris-10-192992.html
SUSE Linux 10 https://www.suse.com/

documentation/sles10/
SUSE Linux 11 https://www.suse.com/

documentation/sles11/
Windows 10 http://
windows.microsoft.com/en
-us/windows/windows-
help#windows=windows-1
0
Database Sybase 15 http://help.sap.com
SQL Server 2008 http://

msdn.microsoft.com/en-us/
library/bb545450.aspx
Two-node cluster Veritas http://www.symantec.com/

software business/support/index?
page=products

Antivirus OfficeScan 11 http://

docs.trendmicro.com/en-
us/enterprise/
officescan.aspx
Virtual machine VMware http://pubs.vmware.com/

software vsphere-55/index.jsp?
lang=en
FusionSphere l FusionSphere OpenStack

OM: http://
support.huawei.com/
carrier/
navi#col=product&allP
roduct=true&path=PBI
1-21430725/
PBI1-21430806/
PBI1-21431666/
PBI1-21778697
l ServiceCenter: http://
support.huawei.com/
carrier/
navi#allProduct=true&
col=product&path=PBI
1-21430725/
PBI1-21430806/
PBI1-21431666/
PBI1-21782552/
PBI1-21270651
HaneWIN NFS haneWIN NFS http://www.hanewin.net/

Server 1.2.18 nfs-e.htm
Adobe Flash Adobe Flash https://get2.adobe.com/cn/

Player Player23 flashplayer/
Third-party PC server X3650 M4 http://www-947.ibm.com/

hardware support/entry/portal/
product/system_x/
system_x3650_m4?
productContext=11285983
53
X3850 X5 http://www-947.ibm.com/
support/entry/portal/
documentation_expanded_
list/hardware/systems/
system_x/system_x3850_x5

RH2288H V2 http://support.huawei.com/
enterprise/
productsupport?
lang=en&pid=9581539&id
AbsPath=7919749|
9856522|9856792|9581539
enterprise/
productsupport?
AbsPath=7919749|
9856522|9856792|9901881
enterprise/
productsupport?
AbsPath=7919749|
9856522|9856792|9768163
Midrange M4000 http://www.oracle.com/

computer/ technetwork/
Workstation documentation/sparc-
mseries-
servers-252709.html
M5000 http://www.oracle.com/
technetwork/
documentation/sparc-
mseries-
servers-252709.html
Netra T4-1 http://docs.oracle.com/cd/

E23203_01/index.html
Netra T4-2 http://docs.oracle.com/cd/

T4-1 http://docs.oracle.com/cd/
T4-2 http://docs.oracle.com/cd/
Blade server E9000 http://support.huawei.com/

enterprise/
productsupport?
lang=en&pid=19961380&i
dAbsPath=7919749|
9856522|9856786|
19955022|19961380

Tape drive SUN LTO4 http://www.oracle.com/

technetwork/
documentation/tape-
storage-curr-187744.html
Small software FTP tool Filezilla https://wiki.filezilla-

project.org/Documentation
SSH/Telnet tool PuTTY http://

www.chiark.greenend.org.
uk/~sgtatham/putty/
download.html
PGPverify tool PGPverify For carrier: http://

support.huawei.com/
carrier/digitalSignature-
Action
For enterprise: http://
support.huawei.com/
enterprise/en/tool/
software-digital-signature-
validation-tool--pgp-
verify--TL1000000054
Desktop Citrix http://support.citrix.com/

virtualization proddocs/topic/
tool infocenter/ic-how-to-
use.html
FTP server Apache FTP http://mina.apache.org/

Server ftpserver-project/
documentation.html
SFTP server minasshd http://mina.apache.org/

sshd-project/
documentation.html
Decompression 7-Zip http://www.7-zip.org/

tool support.html
IE plug-in JRE http://www.java.com/en/

download/help/
Disk burning Nero http://www.nero.com/enu/

software support/
A.5.18 How Do I Adjust the System Networking Solution

Question
How do I manually adjust the system networking solution after installing the U2000?

Answer
Linux OS GUI as the ossuser user. see Configure the VNC service as the ossuser user.
NOTE
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
$ ./stopnms.sh


install/RUN_DBSVR
...
NOTE

$ su - dbuser


$ exit
NOTE
interfaces command.
The MSuite server is running if /opt/oss/OSSJRE/jre_sol/bin/java -server or /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

1. On a computer where the U2000 is installed, double-click the U2000 NMS
3. Click Login.
NOTE
MSuite at one time.
Step 7 Perform the following operations to adjust the system networking solution.
1. Choose Tools > Commissioning Tool from the MSuite client main menu. The
Information dialog box is displayed.
2. Read the information displayed and click Start. The system commissioning window is
displayed.
3. Deselect all options and do not set any parameter. Click Next several times until the
Configure Network window is displayed.
4. Select a system networking solution as needed, and set parameters, such as the IP
address and subnet mask.
5. Click Next several times to exit the commissioning tool.

Step 8 Run the following commands to restart the OS so that the new configurations can take effect:
# shutdown -r now
----End
A.5.19 Starting or Stopping the NTP Service on SUSE Linux

This topic describes how to start or stop the NTP service on SUSE Linux.
Context
If the NTP service is stopped, the U2000 server fails to synchronize the time with that of the
NTP server. This may result in a time deviation.
Procedure
Step 1 Use the PuTTY to log in to the SUSE Linux OS as user ossuser in SSH mode.
Step 2 Run the following command to switch to user root.

$ su - root
Step 3 Run the following command to check the running status of the NTP service.
# rcntp status
NOTE
l If the command output contains running, the NTP service has started.
running
If the NTP service has been started, port 123 corresponding to the service will also be enabled. Run
the netstat -an |grep 123 command to check whether port 123 used by the NTP service has been
enabled on the current server.
l If unused is displayed, the NTP service is not started.
Checking for network time protocol daemon (NTPD): unused
Step 4 Run the following command to start or stop the NTP service.
l Run the following command to start the NTP service.
# service ntp start
l Run the following command to stop the NTP service.
# service ntp stop
----End
A.5.20 How to Query Information About the Software and

Hardware Installation and ESNs of a Huawei Rack Server
Question
How do users query the software and hardware installation and equipment serial numbers
(ESNs) after they obtain the contract number?

Answer
Step 1 Log in to http://texpert.huawei.com/TExpert/Pages/PageContainer.htm.
NOTE
l The following assumes that an engineer queries and installs a server on which the SUSE Linux OS is
installed.
l Only Huawei engineers have permission to log in to the system. Customers can contact Huawei
engineers to obtain information as needed.
Step 2 In the HUMEP iTestCommander page that is displayed, set Domain to FT and FT Data
Browse to By SN.
Step 3 Enter the obtained bar code number next to the Serial Number text box and click Search.
NOTE
You can obtain the bar code number from the server shelf.
Step 4 On the tab that is displayed, select the row whose SubSequence is 5 and has the latest
TransactionTime. Click SerialNumber.

Step 5 The query result page is displayed. View information about the software and hardware
installation and ESNs on the Result Two tab.
Step 6 Close the page.
----End
A.5.21 How to Change the Private Key of the SNMPv3 User

Between U2000 and the Disk Array
Question
How to change the private key of the SNMPv3 user(Kaimse) between U2000 and the disk
array?
Answer
Step 1 Change the private key of the SNMPv3 user in disk array.

NOTICE
If multiple disk arrays are configured, you need to perform the operation on every disk array
and ensure that the private keys for the disk arrays are the same.
1. Use PuTTY to log in to U2000 server in SSH mode as user ossuser.

2. Run the following command to log in to controller A or controller B of the disk array as
user admin in SSH mode.
$ ssh admin@@IP address of controller A or controller B
Password: password of user admin
NOTE
The default password for the user admin is Admin@storage and password set after
preinstallation is Changeme_123.
3. Run the following command to change the password for the default user Kaimse of the
disk array SNMP service.
– OceanStor 5500 V3 disk array:
> change snmp usm user_name=Kaimse authenticate_protocol=SHA
private_protocol=AES
Enter the old and new passwords for user Kaimse according to the system prompt.
Please input your authenticate password: new authenticate password
Please input your authenticate password again: new authenticate password
Please input your private password: new private password
Please input your private password again: new private password
NOTE
The default password and password set after preinstallation for the user Kaimse is
ism@Storage.
The new authenticate password and the new private password must be different.
The private key can contain 6 to 32 characters, including digits 0 to 9, lowercase letters a to
z, uppercase letters A to Z, and special characters @%-=_.]{}. To improve private key
security, please use the following private key policies:
n Must contain special characters and at least two types of following characters:
uppercase letters, lowercase letters and digits when password complex is normal.
n Must contain special characters, uppercase letters, lowercase letters and digits when
password complex is high.
n Must contain any types of the following characters: special characters, uppercase
letters, lowercase letters and digits when password complex is low.
n Be different from the user name or reversed used name.
n Repeated character strings whose unit length is common fractor of 64 (1, 2, 4, 8, etc.)
are not allowed in the passwords, for example, abab and abcdabcd.
To enhance the system security, periodically update the key.
The system displays the following information:
CAUTION: You are advised to set the USM account using secure
authentication protocol SHA and data encryption protocol AES.
Do you wish to continue?(y/n)
Enter y and press Enter. When the system displays the following information, the
password of user Kaimse has been changed successfully:
– OceanStor S3900 disk array:

> chgusmpasswd -u Kaimse

Enter the old and new passwords for user Kaimse according to the system prompt.
Old password: old key
New password: new key
Re-enter new password: new key
NOTE
The default password and password set after preinstallation for the user Kaimse is
Kaimse@storage.
The private key can contain 6 to 32 characters, including digits 0 to 9, lowercase letters a to
z, uppercase letters A to Z, and special characters @%-=_.]{}. To improve private key
security, please use the following private key policies:
n Must contain special characters and at least two types of following characters:
uppercase letters, lowercase letters and digits when password complex is normal.
n Must contain special characters, uppercase letters, lowercase letters and digits when
password complex is high.
n Must contain any types of the following characters: special characters, uppercase
letters, lowercase letters and digits when password complex is low.
n Be different from the user name or reversed used name.
n Repeated character strings whose unit length is common fractor of 64 (1, 2, 4, 8, etc.)
are not allowed in the passwords, for example, abab and abcdabcd.
When the system displays the following information, enter y and press Enter to
restart the SNMP service of the disk array.
This operation will lead to reboot the snmp service!
Do you want to continue? y or n: y
When the system displays the following information, the password of user Kaimse
has been changed successfully:
command operates successfully
4. Run the following command to log out of the disk array.

> exit
If the system displays the following information, type y to log out of the disk array.
Are you sure to exit?(y/n): y
Step 2 Change the private key of the SNMPv3 user in U2000 server.
1. Use PuTTY to log in to U2000 server in SSH mode as user ossuser.
$ su - root
Password:password of user root
3. Run the following commands to start the tool for changing the private key.
# cd /opt/oss/engr/engineering/tool/
# ./modifyUSMvalue.sh
The system displays the following information.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ +
+ Welcome to use SnmpV3 key modify tools +
+ +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
=============================================================
Please select a operation type
1--S2600/S3900
2--5500v3
Q--Exit
=============================================================
Please make a choice : 1

4. Type 1 or 2 to choose S2600/S3900 or 5500v3 and then press Enter.

=============================================================
1--authpasswd
2--privpasswd
R--Return
=============================================================
Please make a choice :
5. Type 1 to choose authpasswd and then press Enter.

Old key: old key
New key: new key
Re-enter new Key: new key
NOTE
For OceanStor 5500 V3 disk array, the default password and password set after preinstallation is
ism@Storage.
For OceanStor S3900 disk array, the default password and password set after preinstallation is
Kaimse@storage.
The private key can contain 8 to 30 characters, including digits 0 to 9, lowercase letters a to z,
uppercase letters A to Z, and special characters @%-=_.]{}. To improve private key security,
please use the following private key policies:
– The private key contains at least one uppercase letter.
– The private key contains at least one lowercase letter.
– The private key contains at least one digit.
– The private key contains at least one special character.
– The key cannot be composed of duplicate character strings, for example, Te_1Te_1.
6. Change the key of the SNMPv3 to the new authenticate password you have set in Step
1.3 as prompted.
When the system displays the
Operation succeeded...,
message, the private key of the SNMPv3 user is changed successfully.
Operation succeeded...
=============================================================
1--authpasswd
2--privpasswd
R--Return
=============================================================
Please make a choice : r
7. If the 5500 V3 disk array is used, privpasswd needs to be modified. If the other disk
array is used, please ignore this step to perform Step 2.8.
Type 2 to choose privpasswd and press Enter.
Old key: old key
New key: new key
Re-enter new Key: new key
Change the key of the SNMPv3 to the new private password you have set in Step 1.3 as
prompted.

When the system displays the

Operation succeeded...,
message, the private key of the SNMPv3 user is changed successfully.
Operation succeeded...
=============================================================
1--authpasswd
2--privpasswd
R--Return
=============================================================
Please make a choice :
8. Type r to choose Return and press Enter to back to the previous menu.
=============================================================
1--S2600/S3900
2--5500v3
Q--Exit
=============================================================
Please make a choice : q
9. Type q to choose Exit and press Enter to exit the tool for changing the private key.
Goodbye!
10. Run the following commands to restart the ResourceMonitor process:

# ps -ef | grep ResourceMonitor
ossuser 13382 1 0 07:13:20 ? 0:38 /opt/oss/server/
platform/bin/ResourceMonitor -cmd start >/dev/null 2>&1
ossuser 17176 16883 0 15:32:15 pts/2 0:00 grep ResourceMonitor
In the command output, the second row of the ResourceMonitor -cmd start line
displays the ID of ResourceMonitor.
# kill -9 13382
NOTE
In the preceding command, 13382 is the process ID of ResourceMonitor. Replace it with the
actual value.
# su - ossuser
$ exit
# ResourceMonitor -cmd start
----End
A.5.22 How Can I Change the Password of the H2 Database
Question
How can I change the password of the H2 database?
Answer
Step 1 Use PuTTY to log in to the OS as the ossuser user in SSH mode.
Step 2 Run the following commands to ensure the isdb is running.

$ svc_adm -cmd startsvc isdb

Step 3 Run the following commands to start the H2 user management tool.
$ cd /opt/oss/server/tools/h2UserManager
$ ./H2SqlExecTool.sh
Information similar to the following is displayed.

Please input your DB user:
Step 4 Enter the database user name and press Enter. The default user name is ossuser.

Please input your user password:
Step 5 Enter the database user password and press Enter. The default password is Changeme_123.

Please input your file password:
Step 6 Enter the database file password and press Enter. The default password is Changeme_123.
NOTE
This script can be used to modify the database user password but not the database file password.

Please input your operation mode : If you want to add a user : -a
If you want to change current user's password : -c
Step 7 Enter -c and press Enter.

NOTE
To add a database user, enter -a and perform operations according to prompts.

The password of the database user must meet the following requirements:
At least one lowercase letter
At least one uppercase letter
At least one digit
At least one special character: ~@#^*--+[{}]:./?
Other special characters, such as \()|<>&`!$"%'=;, and space, are not supported
Please input your new password:
Step 8 Enter the new planned database user password according to the prompted password rule and
press Enter.

Please confirm your new user password:
Step 9 Enter the new planned database user password according to the prompted password rule again
and press Enter.
If "success" is displayed similar to the following, the password is changed successfully.

User: Modify password success.
Step 10 Run the following commands to restart isdb and is_server.

$ svc_adm -cmd restartsvc isdb
$ svc_adm -cmd restartsvc is_server
----End

A.5.23 How Can I Change the Password of the H2 Database File

Question
How can I change the password of the H2 database file?
Answer
Step 1 Use PuTTY to log in to the OS as the ossuser user in SSH mode.
Step 2 Run the following commands to stop isdb and is_server.
$ svc_adm -cmd stopsvc isdb
$ svc_adm -cmd stopsvc is_server
Step 3 Run the following command to set environment variables.

Step 4 Run the following commands to start the tool to change the H2 database file password.
$ cd /opt/oss/server/tools/h2UserManager
$ ./H2FilePWDChange.sh
NOTE
This script can be used to modify the database file password but not the database user password.

Please input your DB user:
Step 5 Enter the database user name and press Enter. The default user name is ossuser.
Please input your user password:
Step 6 Enter the database user password and press Enter. The default password is Changeme_123.
Please input your old file password:
Step 7 Enter the old database file password and press Enter. The default password is
Changeme_123.
The password of the database must meet the following requirements:
At least one lowercase letter
At least one uppercase letter
At least one digit
At least one special character: ~@#^*--+[{}]:./?
Other special characters, such as \()|<>&`!$"%'=;, and space, are not
supported
Please input your new file password:
Step 8 Enter the new planned database user password according to the prompted password rule and
press Enter.
Please input your new file password again:
Step 9 Enter the new planned database user password according to the prompted password rule again
and press Enter.

If "success" is displayed similar to the following, the password is changed successfully.

Test DB success. The file password write to file success.
Step 10 Run the following commands to start isdb and is_server.

$ svc_adm -cmd startsvc isdb
$ svc_adm -cmd startsvc is_server
----End
A.5.24 How Do I Change an H2 Database User's Password for the

U2000 Guard
Question
How do I change an H2 database user's password for the U2000 Guard?
Answer
NOTE
Stop the Sysguard process on the U2000 before changing the password of the U2000 Guard's H2
database.
l Perform the following operations to change the password of an H2 database user on the
Solaris/SUSE Linux-based U2000:
a. Log in to the OS as the ossuser user over SSH using the PuTTY.
b. Run the following command to start the tool used to manage passwords of H2
database users:
$ cd /opt/oss/server/base_service/sysguard/H2Manager
$ ./H2Manager.sh

please input dbuser's password:
c. Enter the password of the database user dbuser and press Enter. The default
password is Changeme_123. The password must be changed during the first login
to ensure system security. Keep the password confidential and change it regularly.
if you want to change the password,please input the old password:
--------------------------------password
requirements---------------------------------------
--1: Length between 8 to 30. --
--2: At least one lowercase letter. --
--3: At least one uppercase letter. --
--4: At least one digit. --
--5: At least one special character: ~@#^-_+[{}]:./? --
--6: Other special characters, such as ()|<>&\`!$"%'=;, and space, are
not supported. --
-------------------------------------------------------------------------
-------------------

please input the new password:
d. Enter a planned database user password and press Enter.

please input the new password again:

e. Enter the planned database user password again and press Enter.
If the last line of the command output is as follows, the password has been
successfully changed:
Changing the dbuser's password succeeded.
l Perform the following operations to change the password of a H2 database user on the
Windows-based U2000:
a. Log in to the Windows OS as a user with the administrator rights.
b. Assess the D:\oss\server\base_service\sysguard\H2Manager directory where the
tool used to manage H2 database user passwords resides.
NOTE
The tool resides in the U2000 installation directory, which may be different from the
preceding directory. You can modify the U2000 installation directory based on actual
situations.
c. Double-click H2Manager.bat to start the tool.
please input dbuser's password:
d. Enter the password of the database user dbuser and press Enter. The default
password is Changeme_123.
if you want to change the password,please input the old password:
--------------------------------password
requirements---------------------------------------
--1: Length between 8 to 30. --
--2: At least one lowercase letter. --
--3: At least one uppercase letter. --
--4: At least one digit. --
--5: At least one special character: ~@#^-_+[{}]:./? --
--6: Other special characters, such as ()|<>&\`!$"%'=;, and space, are
not supported. --
-------------------------------------------------------------------------
-------------------

Please input your new password:
e. Enter a planned database user password and press Enter.

please input the new password again:
f. Enter the planned database user password again and press Enter.
If the following information is displayed, the password has been successfully
changed.
Changing the dbuser's password succeeded.
A.5.25 How Do I Import a U2000 Key Store

This topic describes how to manually import a U2000 key store.
Question
How do I import a U2000 key store?

Answer
l For the Windows OS:
b. Run the following command to import the key store.
> cd /d D:\oss\engr\tools\crypto
> import.bat import_path
NOTE
l import_path is the directory that stores the backup key store, for example, the backup
file path is D:\oss\engr\tools\crypto\cryptoInfo.zip.
l By default, the U2000 is installed in the D:\oss directory. If the U2000 is not installed in
this directory, replace the directory in the preceding command with the actual installation
directory.
If information similar to the following is displayed, the import succeeds.

Operations are successful.
l For the SUSE Linux or Solaris OS:

a. Log in to the OS as the ossuser user over SSH using the PuTTY.
b. Run the following command to import the key store.
$ cd /opt/oss/engr/tools/crypto
$ ./import.sh import_path
NOTE
l import_path is the directory that stores the backup key store, for example, the backup
file path is /opt/oss/engr/tools/crypto/cryptoInfo.zip.
l By default, the U2000 is installed in the /opt/oss directory. If the U2000 is not installed
in this directory, replace the directory in the preceding command with the actual
installation directory and navigate to the actual installation directory to execute the
mapping script.
If information similar to the following is displayed, the import succeeds.

Operations are successful.
----End
A.5.26 How Do I Disable the U2000 from Monitoring the All-Zero

IP Address
When the U2000 is upgraded, many services on the old version listen the all-zero IP address
by default. To enhance U2000 security, all-zero IP address listening needs to disabled, and the
U2000 service has to configured to listen a specified IP address.
Prerequisites
l The U2000 application and southbound IP addresses have been obtained.

NOTE
l To query the U2000 server IP address, run the # ifconfig -a command for the SUSE Linux and
Solaris OSs and the > ipconfig command for a Windows OS.
l To query the U2000 southbound IP address.
l SUSE Linux or Solaris OS:
Log in the OS as the ossuser user.
$ cd /opt/oss/server/tools/configSouthIP
$ ./configsouthip.sh -get
By default, the U2000 is installed in the /opt/oss directory. If the U2000 is not installed
in this directory, replace the directory in the preceding command with the actual
installation directory and navigate to the actual installation directory to execute the
mapping script.
l Windows OS:
Log in the OS as the ossuser user.
> cd /d D:\oss\server\tools\configSouthIP
> configsouthip.bat -get
By default, the U2000 is installed in the D:\oss directory. If the U2000 is not installed in
directory.
l If the southbound IP address is configured:
– If the device is connected to the network through the server's application IP address,
the server's application IP address should add to the southbound IP address list, see
How Can I Configure an IP Address for the Communication Between the U2000
and Southbound NEs.
– The southbound IP addresses should communicate normally with their
interconnected devices. If the device is connected to the network through the
server's application IP address, the application IP addresses should communicate
normally with their interconnected devices.
– The server's application IP address should communicate normally with all client
networks.
– On the NBI Config Tools query the North IP address which the upper-layer OSS
connected to the network management server, the North IP address should
communicate normally with the upper-layer OSS.
l If the southbound IP address is not configured:
– The server's application IP address should communicate normally with all client
networks.
– The server's application IP address should communicate normally with managed
devices.
– On the NBI Config Tools query the North IP address which the upper-layer OSS
connected to the network management server, the North IP address should
communicate normally with the upper-layer OSS.
NOTE
Log in to the server OS as user root, run the command ping -S NMS_application_IP Destination_IP to
ensure that NMS application IP address can be normal communicated.
Context
l For a distributed system, the operations need to be performed only on the NM and EM
nodes.

l For a HA system, the operations need to be performed only on the primary site. Related
data will be automatically synchronized to the secondary site using the VCS.
NOTE
In a HA system, after data is synchronized to the secondary site, the NMS process at the secondary site
has to be restarted to enable all-zero IP address monitoring.
Procedure
l For the Windows OS:
a. Log in the OS as the ossuser user.
b. Stop the U2000 process.
c. Run the following command to disable all-zero IP address monitoring on the CML:
> cd /d D:\oss\server\platform\bin\special > sec_adm -cmd
disableListenAllIP
NOTE
By default, the U2000 is installed in the D:\oss directory. If the U2000 is not installed in this
directory, replace the directory in the preceding command with the actual installation
directory.
If information similar to the following is displayed, all-zero IP address monitoring
is successfully disabled:
Operation succeeded. Please restart all services for the settings to
take effect.
d. Start the U2000 process.

l For the SUSE Linux or Solaris OS:
a. Log in the OS as the ossuser user.
b. Stop the U2000 process.
c. Run the following command to disable all-zero IP address monitoring on the CML:
$ ./opt/oss/server/svc_profile.sh
$ cd /opt/oss/server/platform/bin/special
$ sec_adm -cmd disableListenAllIP
NOTE
By default, the U2000 is installed in the /opt/oss directory. If the U2000 is not installed in
directory and navigate to the actual installation directory to execute the mapping script.
If information similar to the following is displayed, all-zero IP address monitoring
is successfully disabled:
Operation succeeded. Please restart all services for the settings to
take effect.
d. Start the U2000 process.

----End
Follow-up Procedure
When the U2000 server functions as an SNMP client and assesses devices, the specified IP
address and interface must be configured on the firewall to reduce attacks because the
interfaces on the SNMP client monitor only the all-zero IP address. The following describes
how to configure the firewall embedded in the Linux OS:
NOTE
For details about the interfaces in the following tables, see iManager U2000 Communication Port
Matrix.

Table A-6 IP addresses and interfaces configured on the firewall in a centralized system
Scenar Configur Interface Description
io ation Number
Item
Perfor U2000 14001 to Used by the PMSDm and BULKCollectorDm

mance SBI IP 14101 processes.
Manag address
ement 14421 to Used by the SNMPCollectorDm process.
14520
Access U2000 14347 Used by the BmsCommon process.

device SBI IP
manag address 14348 to Used by the BmsAccess process.
ement 14355
14356 Used by the BmsTest process.
14357 Used by the BmsAtur process.
14358 Used by the nemgr_bits process.
14359 Used by the profile process.
14367 Used by the MSOService process.
NE U2000 14360 Used by the EnpowerDm process.

Softwa SBI IP
re address
Manag
ement
Transp U2000 8001 Used by the Eml_PubSvr process to receive response

ort NE southboun packets from NEs.
search d Ethernet
(IP port
auto
discove
ry)
Public U2000 14901 to Used by the U2000 to communicate with NEs over
SBI IP 15900 SNMP.
address
Table A-7 IP addresses and interfaces configured on the firewall in a distributed system
Object Configur Interface Description
ation Number
Item
NM U2000 14001 to Used by the PMSDm and BULKCollectorDm

SBI IP 14101 processes.
address

Object Configur Interface Description

ation Number
Item
14421 to Used by the SNMPCollectorDm process.

14520
PM U2000 14901 to Used by the SNMPCollector, BulkCollector, and

SBI IP 15650 RTPCollector processes.
address
15661 to Used by the InstanceManager process.
15670
EM U2000 14347 Used by the BmsCommon process.

SBI IP
address 14348 to Used by the BmsAccess process.
14355
14356 Used by the BmsTest process.
14357 Used by the BmsAtur process.
14358 Used by the nemgr_bits process.
14359 Used by the profile process.
14360 Used by the EnpowerDm process.
14901 to Used by the U2000 to communicate with NEs over

15900 SNMP.
U2000 8001 Used by the Eml_PubSvr process to receive response

southboun packets from NEs.
d Ethernet
port
The following describes how to configure the specified IP address and interface for the
centralized performance management system (the configuration methods in other scenarios
are similar):
1. Log in to the U2000 OS as the root user.
2. For the NM node in a distributed system or a centralized NMS, run the following
command to set service_ip1 and the interface
NOTE
l For the Solaris OS, the configuration command is ipf, for details, see http://
docs.oracle.com/cd/E19253-01/816-5166/ipf-1m/index.html.
l In the following command, service_ip1 indicates the U2000 SBI IP address, which should be
replaced with the mapping U2000 IP address in the preceding tables.
l The following describes how to open the access to the IP address specified for service_ip1.
l For transport NE search (IP auto discovery), the command used to open the access to
Ethernet ports is similar to the following:# iptables -A INPUT -i eth0 -p udp --dport 8001 -j
ACCEPT. eth0 corresponds to the Configuration Item column in 1 and 2.
a. Open the access to the related interfaces.

i. Run the following command to open the access to interfaces 14001 to 14101:
# iptables -A INPUT -p udp -d service_ip1 --dport 14001:14101 -j
ACCEPT
ii. Run the following command to open the access to interfaces 14421:
# iptables -A INPUT -p udp -d service_ip1 --dport 14421 -j ACCEPT
b. Restrict the access to the related interfaces.

i. Run the following command to restrict the access to interfaces 14001 to
14101:
# iptables -A INPUT -p udp --dport 14001:14101 -j DROP
ii. Run the following command to restrict the access to interfaces 14421:
# iptables -A INPUT -p udp --dport 14421 -j DROP
c. Run the following command to view the configuration result:

# iptables -L -n
NOTE
For transport NE search (IP auto discovery), the command is # iptables -L -nv.
If information similar to the following is displayed, the configuration succeeds:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- 0.0.0.0/0 10.67.172.24 udp dpts:
14001:14101
14421
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14001:14101
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14421
Chain FORWARD (policy ACCEPT)

Chain OUTPUT (policy ACCEPT)

3. Optional: For the NM node in a distributed system or a centralized NMS, to open the
access to the IP address specified for service_ip2 (U2000 server's another IP address),
delete the DROP rules, add the IP address specified for service_ip2, and add DROP
rules again.
NOTE
l For the Solaris OS, the configuration command is ipf, for details, see http://
docs.oracle.com/cd/E19253-01/816-5166/ipf-1m/index.html.
l In the following command, service_ip2 indicates the U2000 SBI IP address, which should be
replaced with the mapping U2000 IP address in the preceding tables.
l The following describes how to open the access to the IP address specified for service_ip2:
l If an interface has multiple IP addresses, open the access to the interfaces mapping to the IP
addresses one by one. Then, restrict the access to them one by one. For example, open the
access to the interfaces mapping to service_ip1 and service_ip2 values and then restrict the
access to these interfaces one by one.
l For transport NE search (IP auto discovery), the command used to open the access to
Ethernet ports is similar to the following:# iptables -A INPUT -i eth1 -p udp --dport 8001 -j
ACCEPT. eth0 corresponds to the Configuration Item column in 1 and 2.
a. Run the following command to check the line numbers of DROP rules:
# iptables -L -n
NOTE


14001:14101
14421
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14001:14101
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14421

b. According to the command output, the DROP rules exist in lines 3 and 4. Run the
following command to delete the DROP rules starting from line 4:
# iptables -D INPUT 4
# iptables -D INPUT 3
c. Run the following command to open the access to service_ip2:

i. Run the following command to open the access to interfaces 14001 to 14101:
# iptables -A INPUT -p udp -d service_ip2 --dport 14001:14101 -j
ACCEPT
ii. Run the following command to open the access to interfaces 14421:
# iptables -A INPUT -p udp -d service_ip2 --dport 14421 -j ACCEPT
iii. Run the following command to restrict the access to interfaces 14001 to
14101:
# iptables -A INPUT -p udp --dport 14001:14101 -j DROP
iv. Run the following command to restrict the access to interfaces 14421:
# iptables -A INPUT -p udp --dport 14421 -j DROP
d. Run the following command to view the configuration result:

# iptables -L -n
NOTE
If information similar to the following is displayed, the configuration succeeds:
14001:14101
14421
14001:14101
14421
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14001:14101
DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:
14421



A.5.27 How Do I Perform a Rollback After the H2 Key

Replacement Fails
Question
How do I perform a rollback after the H2 key replacement fails?
Answer
Step 2 Run the following commands to perform a rollback:
l SUSE Linux or Solaris OS:
$ rm -rf /opt/oss/server/etc/oss_cfg/frame/is_server/data/isdb.h2.db $
cp /opt/oss/server/etc/oss_cfg/frame/is_server/data/isdb.h2.db.bak /opt/oss/
server/etc/oss_cfg/frame/is_server/data/isdb.h2.db $ rm -rf /opt/oss/
server/etc/oss_cfg/frame/is_server/data/isdb.h2.db.bak
NOTE
l Windows OS:
a. Go to the D:\oss\server\etc\oss_cfg\frame\is_server\data directory and delete the
isdb.h2.db file.
b. Rename the isdb.h2.db.bak file to isdb.h2.db.
NOTE
The preceding directory is true only if the U2000 is installed in D:\oss. If the U2000 is not
installed in partition D, change the partition in the directory accordingly.
----End
A.5.28 How to Configure Deletion Protection for Non-Dynamic

Files on the Linux U2000?
Question
How to configure deletion protection for non-dynamic files on the Linux U2000?
Answer
Step 1 Log in to the server as the ossuser user using the PuTTY.
Step 2 Run the following command to check whether deletion protection is configured for non-
dynamic files.
$ lsattr file name

----i-------- file name
NOTE
If i is displayed in the file attributes, the file has deletion protection.

To check whether all non-dynamic files in a folder have deletion protection, run the lsattr -R folder
directory command.

Step 3 Add the file to be protected to any configuration file.

NOTE
Configuration files, with the extension of conf, are stored in the /opt/oss/engr/install/etc/config
directory.
A file path can be either an absolute path or a relative path. The relative path is relative to the U2000
installation path. The format of a relative path is as follows:
/etc/a.log @{OSS_ROOT}/engr/b.log
Step 4 Specify whether non-dynamic files need deletion protection.

Configure guardFile.ini in the /opt/oss/engr/engineering/script/guardFile/ directory as the
configuration file for the desired non-dynamic file. If guardFile in the guardFile.ini file is
set to yes, the non-dynamic file needs deletion protection; if guardFile is set to no or has no
value, the non-dynamic file does not need deletion protection.
Step 5 Run the following command to enable file deletion protection:
$ cd /opt/oss/engr/engineering/script/guardFile
$ ./chattr_add.sh
NOTE
To cancel file deletion protection please run chattr_delete.sh.
----End
A.5.29 How to Change the Password for the User ftpuser

Describes how to change the password for the user ftpuser.
Question
How to change the password for the user ftpuser?
Answer
l For the SUSE Linux or Solaris OSs:
NOTE
l Run modify_ftp_setting.sh to change the password of the user ftpuser on U2000 server and
OS.
l The following command output is displayed on a Linux OS (used as an example).
l The rules for modifying a password are as follows:
l The password must contain 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 ~!@#$%^&*()-_=+\|[{}];:"',<.>/?
l The password cannot be the same as the user name written in either the forward or
backward format.
l If security hardening is performed on the OS, set the password by referring to the
password policies in Security Hardening Guide.
a. Use the PuTTY tool to log in to the server as a root user.
b. Run the following commands to change the password for the user ftpuser as
prompted.

n SUSE Linux:
# cd /opt/sudobin/imap/ftp/files
# bash modify_ftp_setting.sh -i /opt/oss -u ftpuser -l false
n Solaris:
# cd /opt/oss/server/3rdTools/ftp/files
# bash modify_ftp_setting.sh -i /opt/oss -u ftpuser -l false
Changing the password of user ftpuser...
Changing password for ftpuser.
New password: new password for the ftpuser
Retype new password: new password for the ftpuser
Password changed.
Modifying FTP configurations of OSS...
The password of user ftpuser is required.
Please enter the changed password of user ftpuser: new password for the
ftpuser
If the following message displayed, the password for the user ftpuser modified
successfully.
FTP configurations modified successfully.
----End
A.6 Install the U2000 Software Exception Processing

A.6.1 How do I solve the problem where a failure message is

displayed during the installation or the installation is abnormally
interrupted
Symptom
How do I solve the problem where a failure message is displayed during the installation or the
installation is abnormally interrupted?
NOTICE
This operation will uninstall the U2000. Specifically, this operation will cause NEs fail to be
managed and monitored and cause the U2000 database information to be deleted.
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

......
Are you sure you want to clean this environment using this tool?[yes/no]:
Step 3 Enter yes as prompted and press Enter.

......
Clean database will delete all the databases EXCEPT system databases!
Are you sure you want to execute this clean database action[yes/no]:
Step 4 Enter yes as prompted to confirm database deletion and press Enter.

...........Cleaning OSS database......................................
Input sybase directory[/opt/sybase]:
Step 5 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
password timely after the U2000 is installed.
Input database server name: DBSVR
Step 6 Enter the user name and password of the database administrator and the server name. Then
press Enter.
Step 7 After the cleanup operation is performed as prompted, run the following commands to
reinstall the U2000, see 4.9.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:
# su - ossuser
$ ./stopserver.sh
----End
A.6.2 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.6.3 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?
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, 10.9.1.20) recorded in the interfaces file to the IP
address of the U2000 server.
----End

A.6.4 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 An incorrect user name or password has been entered for logging in to the U2000 client.
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.
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.
l The dfwModule fails to be loaded.
l The maximum client login limit has been reached.
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 disk space of the server is not used up.
– To troubleshoot the full disk space on the server on Windows, perform the
Check that disk C is fully used, delete log files, and restart the U2000.
– To troubleshoot the full disk space on the server on Solaris or SUSE Linux, perform
the following operations:
i. Check that the space usage of the /opt directory reaches 100%.
ii. 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.
2. 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 Verify that the entered user name and password are correct.
Step 4 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.6.5 How to Resolve the Problem that the License
Does Not Take Effect and log in to the U2000 client.
Step 5 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 6 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 7 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.
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.5.10 How to Set the Communication Mode on the U2000 server for
Step 8 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
SUSE Linux:
# ping -s IP_address_of_the_NMS
Step 9 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
In common mode, port 31037 is used by default. In SSL mode, port 31039 is used by default.
Windows Server 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 10 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 11 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 12 Check whether the system time is the current time. If not, modify the system time.
Step 13 Create a user and use it to log in. For details, see "Setting the Maximum Number of Sessions"
in U2000 Administrator Guide.
----End
A.6.5 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:
a. The date of the OS is the current date.
b. Check whether the ESN is correct.
You can obtain the ESN tool according to the U2000 License Usage Guide to check
the ESN.

c. 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.
d. 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.
e. 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.
f. The license file must comply with the U2000 version.
g. 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.6.6 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?
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.6.7 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.
Step 3 Check whether the database installation package matches the OS.
----End
A.6.8 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.
# ps -ef | grep sybase

install/RUN_DBSVR
...
NOTE

Run the following commands to stop the Sybase database if it is running:

# su - dbuser
NOTE

1> shutdown SYB_BACKUP
2> go
1> shutdown
2> go
$ exit
NOTE
l Information similar to the following is displayed. The error message does not affect the shutdown of
the database.
Server SHUTDOWN by request.
ASE is terminating this process.
CT-LIBRARY error:
ct_results(): network packet layer: internal net library error:
Net-Library operation terminated due to disconnect
NOTE
l Enter the database administrator user password as prompted. The initial password of the database
administrator user is Changeme_123.
the database.
CT-LIBRARY error:
Step 3 Ensure that the Network Management System Maintenance Suite is not running.

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:
# cd /opt/oss/engr/engineering
# ./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, dbuser and webuser:
# userdel ossuser
NOTE
The message no crontab for ossuser is displayed, indicating that the ossuser user is successfully
deleted.
# userdel dbuser
# userdel webuser
Step 6 Run the following command to delete user group ossgroup, dbgroup and webgroup:
# groupdel ossgroup
# groupdel dbgroup
# groupdel webgroup
Step 7 Run the following command to delete user directory:

# rm -rf /export/home/ossuser
# rm -rf /export/home/dbuser
# rm -rf /export/home/webuser
Step 8 Reinstall the U2000 software. For details, see 4.9 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.6.2 How to Handle
Messages Indicating That the Port Is Occupied During Installation or Uninstall.
----End

and Commissioning Guide (SUSE Linux) 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 a U2000
This topic describes how to uninstall a U2000. A U2000 can be uninstall on the GUI or CLI.
Uninstallation on the GUI is recommended. If the GUI method does not work, use the CLI
method.
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 security hardening policy is enabled on the live network, choose
whether to disable the policy according to network conditions.
l If the SetSuse security hardening policy cannot be disabled on the live network, skip this
step.
NOTE
If the SetSuse security hardening policy is enabled, you cannot directly log in to the OS IP address
as the root user after uninstalling the U2000. Instead, you have to log in through the server
controller.
If the SetSuse security hardening policy is disabled on the live network, skip this step.
l If the SetSuse security hardening policy can be disabled on the live network, run the
following command to cancel the SetSuse security hardening 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:
– If the OS version is Suse 11, run the following command:
# cd /opt/SEK
# ./rollbackSEK.sh
– If the OS version is Suse 10, run the following command:

# sek -b all
5. Run the following commands to roll back the password policy:

# cd /opt/SEK/policies
# ./SEKRevertcorrectPAMForCracklib.sh

# su - ossuser
$ ./stopnms.sh
$ su - dbuser
Password: dbuser user password
NOTE
Enter the database administrator user password as prompted. The initial password of the database
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.
2> go
1> shutdown
2> go
$ su - root
# 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 server as the ossuser user.
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE

$ ./stopnms.sh
Step 5 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:
root 11758 1 1 Nov06 ? 03:24:40 /opt/oss/OSSJRE/jre_linux/bin/
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 - ossuser
$ ./stopserver.sh
$ exit


install/RUN_DBSVR
...
NOTE

$ su - dbuser
$ exit

NOTE
interfaces command.
----End
B.2 Uninstalling a U2000

This topic describes how to uninstall a U2000. A U2000 can be uninstall on the GUI or CLI.
Uninstallation on the GUI is recommended. If the GUI method does not work, use the CLI
method.
Prerequisites
l Uninstallation preparations have been completed.
l The ossuser user has logged out.
a. 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
b. 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
l Forcibly stopping a process may cause disconnection between the command terminal
and the OS. If the connection is disconnected and you cannot log in to the OS from the
command terminal, restart the OS through the control card.
Context
l This operation uninstalls only the U2000. The Sybase database will not be uninstalled.

l 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.
NOTE
If uninstallation fails, see A.6.8 How to Address the U2000 Installation or Uninstallation Failure to
completely uninstall the U2000.
NOTICE
Uninstalling a U2000 will cause NEs fail to be managed and monitored and cause the U2000
database information to be deleted.
Procedure
l Through the GUI
a. Log in to the OS as the root user through the GUI.
NOTE
If the SetSuse policy is enabled, log in to the OS as the root user through the control card.
Right-click in the blank area and choose Open in Terminal from the shortcut menu to
access the CLI.
b. Run the following command to go to the path where the uninstall.sh script is stored
and run the script:
# cd /opt/oss/engr
# ./uninstall.sh
The Confirm Uninstallation dialog box will be displayed.

c. Click Next. The Warning dialog box is displayed.
NOTE
If a message is displayed indicating that the database is already in use, stop the database and
then restart it. Uninstall the database after it is successfully restarted.
d. Click OK. A dialog box showing the progress of the uninstall will be displayed.
NOTE
l The duration of the uninstall depends on the quantity of installed components. Wait
patiently.
l If the SetSuse security hardening policy is enabled during uninstallation or the ossuser
user is being used, log in to the OS as the root user from IMM of the workstation and
then delete the ossuser user and the ossuser directory.
# userdel ossuser
e. After the uninstall is complete, the Uninstallation Complete dialog box is

displayed.
f. Click Finish.
g. Wait 1 minute. Run the following commands to ensure that engr, OSSICMR, and
OSSJRE directories do not exist and complete uninstallation.

Run the cd command, for example, cd /opt/install/OSSICMR, to check whether

the preceding directories have been deleted. If the command output indicates that
the directories do not exist, they have been successfully deleted.
l Through the CLI
a. Log in to the OS as the root user through the CLI.
NOTE
If the SetSuse policy is enabled, log in to the OS as the root user through the control card.
Right-click in the blank area and choose Open in Terminal from the shortcut menu to
access the CLI.
b. Run the following commands to switch to the path where the uninstall.sh file is
stored and run the uninstall.sh script:
# cd /opt/oss/engr
# ./uninstall.sh -cmd
NOTE
After the message Starting OSS Engineering Uninstall Server... is

displayed, wait about two minutes.

===============< Confirm Uninstallation >===============
[Component to uninstall:]
...
...
Uninstall[c:Cancel, <p:Previous, n:Next>, n]:
NOTE
If the message Warning: The database is in use. Stop all processes

manually, or restart the database service manually is displayed, stop
the database and then restart it. Uninstall the database after it is successfully restarted.
c. Enter n and press Enter.
===============< Uninstalling >===============
Warning:The system will start the uninstallation. Are you sure you want
to continue?[y:Yes, n:No, n]:
d. Enter y and press Enter.

NOTE
l The duration of the uninstall depends on the quantity of installed components. Wait
patiently.
l If the SetSuse security hardening policy is enabled during uninstallation or the ossuser
user is being used, log in to the OS as the root user from IMM of the workstation and
then delete the ossuser user and the ossuser directory.
# userdel ossuser
e. After the uninstallation, the message similar to the following will be displayed:
===============< Uninstallation Complete >===============
Finish
The U2000 is uninstalled successfully.
f. Wait 1 minute. Run the following commands to ensure that engr, OSSICMR, and
OSSJRE directories do not exist and complete uninstallation.

Run the cd command, for example, cd /opt/install/OSSICMR, to check whether

the preceding directories have been deleted. If the command output indicates that
the directories do not exist, they have been successfully deleted.
----End
Follow-up Procedure
l /opt/backup/dbbackup and /opt/backup/ftpboot folders can be deleted based on actual
situations.
NOTE
If the /opt/backup/dbbackup and /opt/backup/ftpboot folders were not deleted during
uninstallation, they are renamed to /opt/backup/dbbackup_baktimestamp and /opt/backup/
ftpboot_baktimestamp while reinstall the U2000.
a. Log in to the OS as the root user from the server controller.

b. Run the following commands to delete all files in the /opt/backup/dbbackup
and /opt/backup/ftpboot folders, respectively.
# rm -rf /opt/backup/dbbackup
# rm -rf /opt/backup/ftpboot
l If you do not cancel the SetSuse security hardening policies during U2000 uninstallation
but need to directly log in to the OS IP address as the root user, follow Security
Hardening Guide to roll back the SetSolaris security hardening policies.
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.
l If the server is not mounted with disk arrays, the NMS installation path/opt/oss will be
deleted.
l If the server is mounted with disk arrays, the NMS installation path /opt/oss will be
empty.
The installation paths /opt/oss/engr and /opt/oss/OSSJRE, are 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

and Commissioning Guide (SUSE Linux) 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 Replacing Storage Keys for a Single-Server System (Linux)
This topic describes how to replace the storage keys for a U2000 single-server system running
the Linux OS. Data stored on the U2000 is all encrypted. If the system key store is lost or
damaged, related data will fail to be encrypted. Therefore, it is recommended that storage
keys including the root key and working key on the U2000 server be periodically replaced. A
replacement period must be shorter than 1 year.
C.2 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.3 Setting Hardware Alarm Monitoring
This section describes the settings of monitoring the 5500 V3 disk array, S3900 disk array
hardware.
C.4 Configuring and Testing the FTP Service
During data synchronization, upgrade, backup, and patch installation of NEs, you need to
configure and test the FTP and SFTP service to ensure that the FTP services work properly
between NE software, the U2000, and NEs. This topic describes how to configure and test the
FTP and SFTP services on the U2000.
C.1 Replacing Storage Keys for a Single-Server System

(Linux)
This topic describes how to replace the storage keys for a U2000 single-server system running
the Linux OS. Data stored on the U2000 is all encrypted. If the system key store is lost or
damaged, related data will fail to be encrypted. Therefore, it is recommended that storage
keys including the root key and working key on the U2000 server be periodically replaced. A
replacement period must be shorter than 1 year.
Prerequisites
l Ensure that the NMS process is stopped. To check whether it is stopped, see A.5.5 How
to Verify That the Processes of the U2000 Single-Server System Are Running on

SUSE Linux. If the NMS process is not stopped, see A.5.7 How to End the Processes
of the U2000 Single-Server System on (SUSE Linux).
l Ensure that the database is running properly. To check the database status, see A.4.1.3
How to Verify That the Sybase Database Is Running. If the database is stopped, see
A.4.1.2 How to Start the Sybase Database Service to start it.
l Ensure that the MSuite server process is stopped. For details, see How to End Processes
on the MSuite Server.
l Ensure that the key store is backed up.
Procedure
Step 1 Log in to the OS as the ossuser user over SSH using the PuTTY.
Step 2 Run the following command to back up the key store:
$ ./export.sh export_path
NOTE
l The preceding directory is true only if the U2000 is installed in /opt/oss. If the U2000 is not installed
in partition /opt, change the partition in the directory accordingly.
l In the preceding command, export_path indicates the key store's backup directory, for
example, /opt/oss/engr/tools/crypto.
If information similar to the following is displayed, the backup succeeds:

Operations are successful,Backup File is:opt/oss/engr/tools/crypto/cryptoInfo.zip
NOTE
In the preceding displayed message, /opt/oss/engr/tools/crypto indicates the key store's backup
directory. The backup file cryptoInfo.zip contains both the working key and root key.
Step 3 Run the following command to replace a root key:

$ crypto_cfgtool -cmd modifyRootKey
If information similar to the following is displayed, the replacement succeeds:

Root material updated successfully.
Step 4 Replace a working key.

1. Run the following command to replace a working key:
$ crypto_cfgtool -cmd modify
The following information is displayed:

Warning: Make sure that OSS data (data in the database and files in OSS
directories) has been fully backed up.
You can use the backup to restore the data if the command fails to be run.
To continue, enter "yes". To exit, enter other characters:
2. Ensure that all keys are backed up and enter yes.

The following information is displayed:
Cipher materials checked successfully.
Configuration information modified successfully.
NOTE
Replacing a working key may take a long period of time, usually less than 4 hours.
3. Run the following command to replace the H2 working key.
$ cd /opt/oss/server/tools/h2CryptoCfgTool
$ ./H2CryptoCfgTool.sh

NOTE
If the following information is displayed, the replacement succeeds.
operation start.
...
operation success.
NOTE
If the preceding command fails to be executed, perform rollback. For details, see A.5.27 How Do I
Perform a Rollback After the H2 Key Replacement Fails.
4. Run the following command to delete the isdb.h2.db.bak file.
$ rm -rf /opt/oss/server/etc/oss_cfg/frame/is_server/data/isdb.h2.db.bak
NOTE
Step 5 Optional: If the MSO Web system has been installed on the U2000, run the following
commands to re-encrypt data:
NOTE
Run the following command to check whether the MSO Web system is installed on the U2000:
$ ps -ef
The MSO Web system has been installed on the U2000 if the following information is displayed:
java -Dprocname=MSOService -Dfile.encoding=UTF-8 -DappName=MSOService -
Dfile.encoding=utf-8 -Xms4g -Xmx4g -Xmn3g -Xss256k -XX:ParallelGCThreads=20 -
XX:+UseC
$ cd /opt/oss/server/tools/msoCryptoCfgTool
$ sh MsoCryptoCfgTool.sh
The data is re-encrypted successfully if the following information is displayed:

Start operation...
operation Success!
Step 6 See A.5.6 How to Start the Processes of the U2000 Single-Server System on SUSE Linux
to start the NMS process.
Step 7 See How to Start the Process of the MSuite Server to start the Process of the MSuite Server.
----End
Follow-up Procedure
1. Delete the exported key store.
a. Log in to the OS as the ossuser user using the PuTTY.
b. Run the following command to delete the key store exported before key
replacement:
$ rm -rf opt/oss/engr/tools/crypto/cryptoInfo.zip
NOTE
2. Back up the new key store.
a. Log in to the OS as the ossuser user using the PuTTY.
b. Run the following command to back up the new key store:

$ ./export.sh export_path
NOTE
l The preceding directory is true only if the U2000 is installed in /opt/oss. If the U2000 is
not installed in partition /opt, change the partition in the directory accordingly.
l In the preceding command, export_path indicates the key store's backup directory, for
example, /opt/oss/engr/tools/crypto.
If information similar to the following is displayed, the backup succeeds:
Operations are successful,Backup File is:opt/oss/engr/tools/crypto/
cryptoInfo.zip
NOTE
In the preceding displayed message, /opt/oss/engr/tools/crypto indicates the key store's
backup directory. The backup file cryptoInfo.zip contains both the working key and root
key.
c. Save the exported backup key store after encryption to a storage unit with a higher
level of confidentiality, and delete it locally.
C.2 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.2.1 Replacing SSL Certificates Used for the U2000 Server

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, to improve the
communication security of U2000. This topic describes how to replace the Security Socket
Layer (SSL) certificates used by the U2000 server.
Prerequisites
l You have obtained the trust certificate (rootCA.cer, subCA1.cer) and identity certificate
(server.p12) used by the server and the encryption password for the identity certificate.
l The SSL certificates have been backed up.
l Use the FTP to upload the new SSL certificate files (server.p12, rootCA.cer and
subCA1.cer) to the following directory on the U2000 server as the ossuser user before
you replace the SSL certificate of server.
– Solaris/SUSE Linux: /opt/oss/server/certs.
NOTE
l The directory is true only if the U2000 on Solaris or SUSE Linux OS is installed in /opt/
oss. If the U2000 is not installed in partition /opt, change the partition in the directory
accordingly.
l If security hardening is performed, ossuser FTP/SFTP rights will be disabled. In this
case, you need to upload files to the backup directory in the FTP root directory as the
ftpuser user (the FTP root directory of ftpuser is /opt/backup/ftpboot) and then copy
files to the target directory as the ossuser user.
– Windows: D:\oss\server\certs.

NOTE
The directory is true only if the U2000 on Windows OS is installed in D:\oss. If the U2000 is
not installed in partition D, change the partition in the directory accordingly.
NOTICE
Place only the certificate files server.p12, rootCA.cer and subCA1.cer in this directory.
Do not place other files in it. Otherwise, the certificate replacement script will fail to be
executed.
l The U2000 processes have been shutdown.
Context
l By default, the U2000 client authenticates the U2000 server, but the U2000 server does
not authenticate the U2000 client.
l The Huawei-predefined SSL certificates used to safeguard communication between the
U2000 server and client are located in the following directory:
– On Solaris or SUSE Linux OS: /opt/oss/server/etc/ssl.
– On Windows OS: D:\oss\server\etc\ssl.
l The MSuite and the U2000 use the same SSL certificates.
l The following script-based replacement procedure assumes that your OS is Solaris or
SUSE Linux OS. If your OS is Windows, replace the certificates for the U2000 server in
a similar way.
NOTICE
After SSL Certificates for the U2000 server have been replaced, you may fail to log in to
the MSuite.
Procedure
l Replace SSL certificates for the U2000 server through the GUI.
a. Ensure that the MSuite servers on the primary and secondary sites have 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.
...
ossuser 8937 12803 0 04:13 pts/8 00:00:42 /opt/oss/OSSJRE/
jre_linux/bin/java -Dprocname=AgentIntegrate -Dfile.encoding=UTF8 -
Xmx1024m -XX:MetaspaceSize=16m -XX:MaxMetaspaceSize=256m -XX:
+UseCompressedClassPointers -XX:+UseCompressedOops -

XX:CompressedClassSpaceSize=128m -XX:+HeapDumpOnOutOfMemoryError -
DabsCfgPath=/opt/oss/server/etc/oss_cfg/frame -cp nbi/agentintegrate/
thirdparty/*:3rdlib/*:common/uflightdispatcher/lib/jdom.jar:cbb/qasn/lib/
*:common/uflight/frame_app/plugins/com.huawei.uflight.platformadapter/
*:common/uflight/web_app/plugins/pax-web-runtime-2.1.2.jar:common/
uflight/web_app/plugins/web_app/plugins/pax-web-spi-2.1.2.jar:nbi/
agentintegrate/lib/*:nbi/agentintegrate/bin/*
...
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, switch to the ossuser and run the
following commands as the root user to start the MSuite servers:
# su - ossuser
$ ./startserver.sh
b. Log in to the MSuite client from the U2000 server.

c. Choose Certificate File Management > Internal NMS Certificate.
d. In the Certificate Configuration dialog box, select the SSL certificates to be
replaced and click ReplaceAll.
e. In the Information Confirmation dialog box, enter the PFX password.
NOTE
The new encryption password for the identity certificate must meet the following
requirements:
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.
f. Click OK.
g. Because the MSuite reuses the U2000 digital certificates, restart the MSuite server
for the certificates to take effect.
l Replace SSL certificates for the U2000 server using a script.
a. Use the PuTTY to log in to the U2000 server in SSH mode as the ossuser user.
b. Run the following command to end the U2000 processes:
Single-Server System:
$ ./stopnms.sh
c. Use the FileZilla to upload certificates to /opt/oss/server/certs on the U2000 server.

d. Run the following command to back up the certificates (as the root user):
$ ssl_adm -cmd backup -backpath /opt/backup/dbbackup/ssl
NOTE
The certificates can be backed up to an absolute or relative directory. The following steps
assume that the certificates are backed up to /opt/backup/dbbackup/ssl.
e. Run the following command to replace the certificates used by the U2000 server (as
the root user):
$ ssl_adm -cmd replace_certs -dir /opt/oss/server/certs

NOTE
/opt/oss/server/certs is the path for saving certificates.
Information similar to the following is displayed by order:

Enter the old identity certificate password:
Enter the new identity certificate password:
Reenter the old identity certificate password:
f. Enter the new identity certificate old password, the new identity certificate new
password and reenter the new identity certificate new password, press Enter.
NOTE
l Two formats are available for the identity certificate.

l If the identity certificate is server.p12 of the PKCS#12 type (single file in PFX
format), enter the certificate password obtained together with the certificate after
Enter the old identity certificate password:, because the password is verified
during command execution.
l If the identity certificate file is server.cer, password is user-defined. The command
is run to convert the server.cer file into the server.p12 file of the PKCS#12 type.
l The new encryption password for the identity certificate 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.
l If the certificates fail to be replaced, resolve the problem based on the prompt and run
the following command to restore the certificates before replacing them again:
$ ssl_adm -cmd restore -backpath /opt/backup/dbbackup/ssl
The certificates are successfully replaced if the following information is displayed:

SSL certificates are deployed successfully
g. Optional: If you need to use the iNBIXMLSoapAgent process, run the following
commands to change the certificate password for the process:
$ cd /opt/oss/server/nemgr/nemgr_access/scriptsinstall
$ ./postRepalceCert.sh
The certificate password is successfully changed if the following information is

displayed:
The database already has this configuration item, and the value of the
configuration file is different from the value of this configuration
item.
The value of this configuration item is updated to the database in /imap/
inbxmlsoapagent/soapxml/soapsecuremode/SOAPServerCertkey
The database already has this configuration item, and the value of the
configuration file is different from the value of this configuration
item.
The value of this configuration item is updated to the database in /imap/
inbxmlsoapagent/notification/authinfo/WSNOTIFYBrokerCertkey
svc_adm : info : reload successfully.
NOTE
If you do not perform this step, the iNBIXMLSoapAgent process will fail to start up after
certificates are replaced on the U2000 server.

h. After the certificates are successfully replaced, run the following commands to
import environment variables and update the CAU configuration data (as the
ossuser user).
$ cd /opt/oss/cau/bin/
$ ./cau.sh
i. Run the following commands to start U2000 processes for the replacement to take
effect:
Single-Server System (as the ossuser user):

$ ./startnms.sh
----End
Follow-up Procedure
l After the SSL digital certificates on the server and clients are replaced, delete the
webrenderer cache directory C:\Users\%username%\thirdparty\webrender manually
on all clients and restart the client processes. Otherwise, functions depending on
webrenderer may fail.
NOTE
If the C:\Users\%username%\thirdparty\webrender directory does not exist, skip this step.
l After the trust and identity certificates used by the U2000 server are successfully
replaced, delete certificate files from /opt/oss/server/certs on the U2000 server.
l After the trust and identity certificates used by the U2000 server are successfully
replaced, replace the trust and identity certificates used by the U2000 client as well.
C.2.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, to improve the
communication security of U2000. 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
encrypting the file needs to be obtained.
– The server.p12 contains the server certificate file and key file. The password for
encrypting the file needs to be obtained.
– The rootCA.cer and subCA1.cer contains the files issued by the client, server, and
upper-layer system.
l Use the FTP to upload the new SSL certificate to the following directory on the U2000
server as the ossuser user before you replace the SSL certificate.
– Solaris/SUSE Linux: /opt/oss/server/certs.

NOTE
l The directory is true only if the U2000 on Solaris/SUSE Linux OS is installed in /opt/
oss. If the U2000 is not installed in partition /opt, change the partition in the directory
accordingly.
l If security hardening is performed, ossuser FTP/SFTP rights will be disabled. In this
case, you need to upload files to the backup directory in the FTP root directory as the
ftpuser user (the FTP root directory of ftpuser is /opt/backup/ftpboot) and then copy
files to the target directory as the ossuser user.
– Windows: D:\oss\server\certs.
NOTE
The directory is true only if the U2000 on Windows OS is installed in D:\oss. If the U2000 is
not installed in partition D, change the partition in the directory accordingly.
l The SSL certificates have been 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/common/pms/share/
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.

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 Example:
l ./replace_certs.sh -type 1 -file client.p12 -pfxpass
l ./replace_certs.sh -type 2 -file server.p12 -pfxpass
l ./replace_certs.sh -type 3 -file trust.cer
l ./replace_certs.sh -type 4 -file revoke.crl
l To ensure the security of the system, remember to change passwords regularly and passwords
must be complex enough.
l A password cannot be short and a password is recommended containing eight or more
characters.
l At least two types of the following characters: digits, letters, and special characters
Procedure
l Replace an SSL certificate for the U2000 and uTraffic using a script.
b. Start the identity certificate replacement script.
n Solaris or SUSE Linux :
$ cd /opt/oss/server/common/pms/share/tools/ssl
$ ./replace_certs.sh -type certificate type -file certificate file -pfxpass
NOTE
l The identify certificates on the server and client must be replaced separately. For
example:
l replace_certs.bat -type 1 -file client.p12 -pfxpass
l replace_certs.bat -type 2 -file server.p12 -pfxpass
l To ensure the security of the system, remember to change passwords regularly and
passwords must be complex enough.
l A password cannot be short and a password is recommended containing
eight or more characters.
l At least two types of the following characters: digits, letters, and special
characters
n Windows:
>cd /d d:
> cd \oss\server\common\pms\share\tools\ssl
> replace_certs.bat -type certificate type -file certificate file -pfxpass

NOTE
l The identify certificates on the server and client must be replaced separately. For
example:
l replace_certs.bat -type 1 -file client.p12 -pfxpass
l replace_certs.bat -type 2 -file server.p12 -pfxpass
l To ensure the security of the system, remember to change passwords regularly and
passwords must be complex enough.
l A password cannot be short and a password is recommended containing
eight or more characters.
l At least two types of the following characters: digits, letters, and special
characters
c. Start the trust certificate replacement script.
n Solaris or SUSE Linux (as the ossuser user):
$ ./replace_certs.sh -type certificate type -file certificate file
NOTE
For information about variables, see the background information. For example, ./
replace_certs.sh -type 3 -file trust.cer.
n Windows:
>cd /d d:
> replace_certs.bat -type certificate type -file certificate file
NOTE
For information about variables, see the background information. For example,
replace_certs.bat -type 3 -file trust.cer.
d. Optional: Start the CRL configuration script.
n Solaris or SUSE Linux (as the ossuser user):
$ ./replace_certs.sh -type certificate type -file certificate file
NOTE
For information about variables, see the background information. For example, ./
replace_certs.sh -type 4 -file revoke.crl.
n Windows:
>cd /d d:
> replace_certs.bat -type certificate type -file certificate file
NOTE
For information about variables, see the background information. For example,
replace_certs.bat -type 4 -file revoke.crl.
e. Restart the U2000 service.
----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.
NOTE
l The directory is true only if the U2000 on Solaris/SUSE Linux OS is installed in /opt/oss. If
the U2000 is not installed in partition /opt, change the partition in the directory accordingly.
l If security hardening is performed, ossuser FTP/SFTP rights will be disabled. In this case, you
need to upload files to the backup directory in the FTP root directory as the ftpuser user (the
FTP root directory of ftpuser is /opt/backup/ftpboot) and then copy files to the target
directory as the ossuser user.
l Windows: D:\oss\server\certs.
NOTE
The directory is true only if the U2000 on Windows OS is installed in D:\oss. If the U2000 is not
installed in partition D, change the partition in the directory accordingly.
C.2.3 Deploying the SSL Trust Certificate on the Internet Explorer

When the U2000 uses Hedex Help or 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 trust certificate of the Internet
Explorer must be deployed.
Context
The trust certificate preconfigured by Huawei consists of the root certificate
huaweiossCA.crt and intermediate certificate networkossCA.crt. All of the certificates need
to be deployed on the Internet Explorer.
Procedure
Step 1 Open the Internet Explorer of the U2000 client and choose Tool > Internet Options from the
main menu.
Step 2 In the Internet Options dialog box, select Content tab and click Certificates.
Step 3 In the Certificates dialog box, deploy the root certificate huaweiossCA.crt.
1. Select the Trusted Root Certification Authorities tab and click Import.
2. In the Certificate Import Wizard dialog box, click Next.
3. Click Browse..., select the trusted root certificate huaweiossCA.crt, and click Next.

NOTE
The trust root certificate preconfigured by Huawei, huaweiossCA.crt , is stored in the oss\client
\client\style\defaultstyle\conf\ssl\trust\PEM directory.
4. Click Next, and then click Finish.
5. In the Security Warning dialog box that is displayed, click Yes.
6. In the Certificate Import Wizard dialog box, click OK.
Step 4 Deploy the intermediate certificate networkossCA.crt.
1. Select the Intermediate Certification Authorities tab and click Import.
2. In the Certificate Import Wizard dialog box, click Next.
3. Click Browse..., select the trusted intermediate certificate networkossCA.crt, and click
Next.
NOTE
The trust intermediate certificate preconfigured by Huawei, networkossCA.crt, is stored in the

oss\client\client\style\defaultstyle\conf\ssl\trust\PEM diectory.
4. Click Next, and then click Finish.
5. In the Certificate Import Wizard dialog box that is displayed, click OK.
Step 5 Click Close.
Step 6 In the Internet Options dialog box, select the Advanced tab. Drag the scroll bar to Security
and clear the selection of the Warn about certificate address mismatch*.
Step 7 Click OK.
Step 8 Restart the Internet Explorer.
----End
Follow-up Procedure
l If the U2000 GUI is displayed abnormally, the SSL certificate fails to be uploaded. Refer
to the preceding operations to redeploy a digital certificate.
l If the dialog which prompted you need trusted certification is displayed in the U2000 NE
management, right-click Continue to this website (not recommended), and then click
Open in the New Window. In the dialog box that is displayed, click OK. 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.
C.3 Setting Hardware Alarm Monitoring

This section describes the settings of monitoring the 5500 V3 disk array, S3900 disk array
hardware.
C.3.1 Configuring the Monitoring Function for an OceanStor 5500

V3 Disk Array
This section describes how to configure the monitoring function for an OceanStor 5500 V3
disk array. After you configure the monitoring function, the U2000 automatically reports an
alarm if the OceanStor 5500 V3 disk array becomes faulty or fails to work.

Prerequisites
l The U2000 services are running properly.
l The U2000 server communicates properly with the optical fiber of the OceanStor 5500
V3 disk array.
l The IP network between the U2000 server and the OceanStor 5500 V3 disk array is
normal.
l Log in to the U2000 server as user ossuser.
Context
The monitoring software OceanStor Device Manager monitors the hardware status of an
OceanStor 5500 V3 disk array, including the hard disks, controllers, power supplies, fans,
optical ports, and batteries. If the hardware becomes faulty or fails to work, the U2000 reports
an alarm.
l While the U2000 is being upgraded, a patch is being installed on the U2000, or the
network between the server and the disk array becomes faulty, the alarms generated on
the disk array cannot be handled in time. After the system restores, the historical alarms
will not be reported to the U2000.
l Device Manager, an integrated storage management platform provided by Huawei, can
manage multiple sets of disk arrays. You do not need to download or install Device
Manager because it has been installed on the disk array before delivery.
NOTE
l Configure disk array monitoring on either controller A or B. The following example describes how
to configure disk array monitoring on controller A.
l To configure the monitoring function for the disk array, ensure the network communication
between the IP address of the disk array controller set in the following steps and the NMS
application IP address is normal. Otherwise, the disk array may fail to report alarms to the U2000.
Procedure
Step 1 Run the following command on the U2000 server to log in to controller A of the OceanStor
5500 V3 disk array in SSH mode:
$export LD_LIBRARY_PATH=/usr/sfw/lib
$ ssh admin@IP address of controller A
NOTICE
The default administrator name is admin and the initial password of the admin user is
changed to Changeme_123. To ensure system security, change the password after you log in
to the system for the first time and the password must be complex enough.
If the system displays Are you sure you want to continue connecting (yes/no)?, type yes
and press Enter.
Step 2 Optional: If monitoring is configured for the OceanStor 5500 V3 disk array for the first time,
change the Kaimse password of the SNMP user. For details, see A.5.21 How to Change the
Private Key of the SNMPv3 User Between U2000 and the Disk Array.

Step 3 Run the following command to check whether the disk array has been assigned Trap IP,
namely, the NMS application IP address.
admin:/> show notification trap
Server ID Server IP Server Port Trap Version Trap Type

--------- ------------- ----------- ------------ ---------
0 10.168.9.251 23001 v3 All
l If the system does not display any command output, the disk array has not been assigned
Trap IP. Perform Step 4.
l If the system displays any command output, the disk array has been assigned Trap IP. In
the command output, check whether IP Address is correct.
– If IP Address is correct, go to Step 5.
– If IP Address is incorrect, run the following command to change Trap IP. Then
perform Step 5.
admin:/> change notification trap server_id=service ID trap_version=SNMP
version server_ip=IP address server_port=service port number
NOTE
n service ID specifies the service ID corresponding to the Server ID whose trap IP

address needs to be modified.
n SNMP version specifies the SNMP version corresponding to the Trap Version whose
trap IP address to be modified.
When Trap Version is v3, SNMP version is 3. When Trap Version is v2, SNMP
version is 2. Setting the Trap Version to SNMPv3 (more secure) is recommended.
n IP address specifies the actual trap IP address.
n service port number specifies the service port number corresponding to the Server
Port whose trap IP address needs to be modified.
Set the preceding parameters according to on-site requirements.
Use the preceding command output as an example. If you need to change Trap IP
of the disk array from 10.168.9.251 to 10.168.9.241, run the following command:
admin:/> change notification trap server_id=0 trap_version=v3
server_ip=10.168.9.241 server_port=23001
After the modification is complete, run the show notification trap command to
check whether Trap IP is successfully changed.
Step 4 Optional: If the trap IP address for disk array has not bee configured, run the following
command to set the trap IP address:
This section uses 192.168.9.241 as an example. In a single-server system, set the Trap IP of
the disk array to the U2000 application IP address. In an HA system, set the Trap IP of the
disk array to the primary U2000 application IP address.
admin:/> add notification trap trap_version=v3 server_ip=10.168.9.241
server_port=23001
Step 5 Run the following command to check whether the system time of the disk array is consistent
with that of the U2000 server to which the disk array connects.
admin:/> show system general
System Name : XXX.Storage

SN : 210235G6EHZ0CX0000XX
Location :
Product Model : XXXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 30
WWN : XXXX
Time : 2015-07-07/15:34:05 UTC+08:00
Please check the system time after Time.

The system time of the disk array must be the same as that of the U2000 server to which the
disk array is connected. If the system times are inconsistent, run the following commands:
admin:/> change system time time=2014-04-06/11:22:05
NOTE
This section assumes that you change the system time of the disk array to 2014-04-06/11:22:05, with the
precision comes to minutes.
The change system time command is used to change the system time. The system time ranges from
1970-01-01/00:00:00 to 2069-12-31/23:59:00.
Step 6 Run the following commands to exit controller A:

admin:/> exit
Step 7 Perform the following operations to update information in the disk array-related configuration
file on the U2000 server:
NOTE
If the IP addresses of controllers A and B have been configured in the Set Hardware Alarm dialog box
of the commissioning tool, set the device to the correct device style.
1. Log in to the U2000 server as user ossuser.
2. Run the following command to add the device style and the IP address of the disk
array controller to the SANtricty_config.xml file:
$ cd /opt/oss/server/platform/resourcemonitor/
$ cat SANtricty_config.xml
<config>
<src name = "trapsender" ip = "IP address of controller A" port = "23001"
iorstring = ""/>
<src name = "trapsender" ip = "IP address of controller B" port = "23001"
iorstring = ""/>
</config>
<traps name = "snmptraps">

<trap oid = "1.3.6.1.4.1.2011" name = "DiskarrayStatusAlarm" device =
"5500v3" alarmid = "1043" type = "1" trapip = "IP address of controller A"
description = "Disk Arrays status alarm">
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.2.0" name = "" datatype = "1"
description = "LocationInfo" maxlen = "50"/>
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.4.0" name = "FaultTitle" datatype =
"1" description = "" maxlen = "50"/>
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.11.0" name = "FaultCategory"
datatype = "0" description = "" maxlen = "50"/>
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.6.0" name = "FaultLevel" datatype =
</trap>
</traps>
– If the device style recorded in this file is incorrect, run the following commands:
$ cd /opt/oss/engr/install/scripts/commission

$ ./setDevice.sh oldDevice newDevice

NOTE
n OldDevice: If no disk array is configured, OldDevice is left blank. Run the $ ./

setDevice.sh '' newDevice command. If a disk array has been configured, OldDevice is
the model of the configured disk array.
n newDevice is the model of the disk array to be configured.
– If the controller IP address recorded in this file is incorrect, run the following
commands to replace the IP address of the old controller with that of the new
controller:
$ ./setTrapIP.sh trapType newTrapIP
NOTE
n If the login controller is controller A, trapType is trapA, that is, the IP address of
controller A is configured.
n If the login controller is controller B, trapType is trapB, that is, the IP address of
controller B is configured.
n newTrapIP indicates the IP address of the new controller.
3. Run the following command to view the user.xml file:
$ cat user.xml
<snmp name = "trap">
......
<instance name = "san" run = "true" filepath = "SANtricty_config.xml"/>
<instance name = "vcs" run = "true" filepath = "vcs_config.xml"/>
<loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/>
</snmp>
– If the value of san in the user.xml file is true, perform step Step 7.4.
– If the value of san in the user.xml file is not true, run the following commands to
change the value of san to true:
$ bash user.sh
$ ps -ef | grep "ResourceMonitor"

ossuser 21579 1 0 20:15:05 ? 4:43 /opt/oss/server/
platform/bin/ResourceMonitor -cmd start
In the command output, the second row of the /opt/oss/server/platform/bin/

ResourceMonitor -cmd start line displays the ID of ResourceMonitor. This section
uses ID 21579 as an example.
$ kill -9 21579
NOTE
– In the preceding command, 21579 is the process ID of ResourceMonitor. Replace it with

the actual value.
– After the preceding commands are used to stop the ResourceMonitor process, the system
automatically starts the process.
----End

C.3.2 Configuring the Monitoring Function for an S3900 Disk

Array
This section describes how to configure the monitoring function for an S3900 disk array.
After you configure the monitoring function, the U2000 automatically reports an alarm if the
S3900 disk array becomes faulty or fails to work.
Prerequisites
l The U2000 services are running properly.
l The U2000 server communicates properly with the optical fiber of the S3900 disk array.
l The IP network between the U2000 server and the S3900 disk array is normal.
l Log in to the U2000 server as user ossuser.
Context
The monitoring software OceanStor Integrated Storage Management (ISM) monitors the
hardware status of an S3900 disk array, including the hard disks, controllers, power supplies,
fans, optical ports, and batteries. If the hardware becomes faulty or fails to work, the U2000
reports an alarm.
l While the U2000 is being upgraded, a patch is being installed on the U2000, or the
network between the server and the disk array becomes faulty, the alarms generated on
the disk array cannot be handled in time. After the system restores, the historical alarms
will not be reported to the U2000.
l OceanStor ISM, an integrated storage management platform provided by Huawei, can
manage multiple sets of disk arrays. You do not need to download or install OceanStor
ISM because it has been installed on the disk array before delivery.
NOTE
l Configure disk array monitoring on either controller A or B. The following example describes how
to configure disk array monitoring on controller A.
l To configure the monitoring function for the disk array, ensure the network communication
between the IP address of the disk array controller set in the following steps and the NMS
application IP address is normal. Otherwise, the disk array may fail to report alarms to the U2000.
Procedure
Step 1 Run the following command on the U2000 server to log in to controller A of the S3900 disk
array in SSH mode:
$export LD_LIBRARY_PATH=/usr/sfw/lib
$ ssh admin@IP address of controller A

NOTICE
The initial user name for the administrator user is admin, and the password is
Admin@storage. To ensure system security, change the password after you log in to the
system for the first time and the password must be complex enough.
If the system displays Are you sure you want to continue connecting (yes/no)?, type yes
and press Enter.
Step 2 Run the following command to check whether the disk array has been assigned Trap IP,
namely, the NMS application IP address.
admin:/> showtrapip
============================================================
Trap IP Information
------------------------------------------------------------
Server ID Server IP Server Port Trap Version
------------------------------------------------------------
0 10.168.9.251 23001 SNMPv3
============================================================
l If the system does not display any command output, the disk array has not been assigned
Trap IP. Perform Step 3.
l If the system displays any command output, the disk array has been assigned Trap IP. In
the command output, check whether IP Address is correct.
– If IP Address is correct, go to Step 4.
– If IP Address is incorrect, run the following command to change Trap IP. Then
perform Step 4.
admin:/> chgtrapip -server service ID -ip IP address -port service port
number-ver SNMP version
NOTE
n service ID specifies the service ID corresponding to the Server ID whose trap IP

address needs to be modified.
n IP address specifies the actual trap IP address.
n service port number specifies the service port number corresponding to the Server
Port whose trap IP address needs to be modified.
n SNMP version specifies the SNMP version corresponding to the Trap Version whose
trap IP address to be modified.
When Trap Version is SNMPv3, SNMP version is 3. When Trap Version is SNMPv2,
SNMP version is 2. Setting the Trap Version to SNMPv3 (more secure) is
recommended.
Set the preceding parameters according to on-site requirements.
Use the preceding command output as an example. If you need to change Trap IP
of the disk array from 10.168.9.251 to 10.168.9.241, run the following command:
admin:/> chgtrapip -server 0 -ip 10.168.9.241 -port 23001 -ver 3
After the modification is complete, run the showtrapip command to check whether
Trap IP is successfully changed.
Step 3 Optional: If the trap IP address for disk array has not bee configured, run the following
command to set the trap IP address:

This section uses 192.168.9.241 as an example. In a single-server system, set the Trap IP of
the disk array to the U2000 application IP address. In an HA system, set the Trap IP of the
disk array to the primary U2000 application IP address.
admin:/> addtrapip -ip 10.168.9.241 -port 23001 -ver 3
Step 4 Run the following command to check whether the system time of the disk array is consistent
with that of the U2000 server to which the disk array connects.
admin:/> showsys
The system time of the disk array must be the same as that of the U2000 server to which the
disk array is connected. If the system times are inconsistent, run the following commands:
admin:/> chgsystime -time 2012-11-21/11:05:00
NOTE
This section assumes that you change the system time of the disk array to 2012-11-21/11:05:00, with the
precision comes to minutes.
The chgsystime command is used to change the system time. The system time ranges from
1970-01-01/00:00:00 to 2069-12-31/23:59:00.
Step 5 Run the following commands to exit controller A:
admin:/> exit
Step 6 Perform the following operations to update information in the disk array-related configuration
file on the U2000 server:
NOTE
If the IP addresses of controllers A and B have been configured in the Set Hardware Alarm dialog box
of the commissioning tool, skip the following steps.
1. Log in to the U2000 server as user ossuser.
2. Run the following command to add the device style and the IP address of the disk
array controller to the SANtricty_config.xml file:
$ cd /opt/oss/server/platform/resourcemonitor/
$ cat SANtricty_config.xml
<config>
<src name = "trapsender" ip = "IP address of controller A" port = "23001"
iorstring = ""/>
<src name = "trapsender" ip = "IP address of controller B" port = "23001"
iorstring = ""/>
</config>
<traps name = "snmptraps">

<trap oid = "1.3.6.1.4.1.2011" name = "DiskarrayStatusAlarm" device = "S3900"
alarmid = "1043" type = "1" trapip = "IP address of controller A" description
= "Disk Arrays status alarm">
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.2.0" name = "" datatype = "1"
description = "LocationInfo" maxlen = "50"/>
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.4.0" name = "FaultTitle" datatype =
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.11.0" name = "FaultCategory"
datatype = "0" description = "" maxlen = "50"/>
<vb oid = "1.3.6.1.4.1.2011.2.91.10.3.1.1.6.0" name = "FaultLevel" datatype =
</trap>
</traps>

– If the device style recorded in this file is incorrect, run the following commands:
$ ./setDevice.sh oldDevice newDevice
NOTE
n OldDevice: If no disk array is configured, OldDevice is left blank. Run the $ ./

setDevice.sh '' newDevice command. If a disk array has been configured, OldDevice is
the model of the configured disk array.
n newDevice is the model of the disk array to be configured.
– If the controller IP address recorded in this file is incorrect, run the following
commands to replace the IP address of the old controller with that of the new
controller:
$ ./setTrapIP.sh trapType newTrapIP
NOTE
n If the login controller is controller A, trapType is trapA, that is, the IP address of
controller A is configured.
n If the login controller is controller B, trapType is trapB, that is, the IP address of
controller B is configured.
n newTrapIP indicates the IP address of the new controller.
3. Run the following command to view the user.xml file:
$ cat user.xml
<snmp name = "trap">
......
<instance name = "san" run = "true" filepath = "SANtricty_config.xml"/>
<instance name = "vcs" run = "true" filepath = "vcs_config.xml"/>
<loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/>
</snmp>
– If the value of san in the user.xml file is true, perform step Step 7.4.
– If the value of san in the user.xml file is not true, run the following commands to
change the value of san to true:
$ bash user.sh
$ ps -ef | grep "ResourceMonitor"
In the command output, the second row of the ResourceMonitor -cmd start line
displays the ID of ResourceMonitor. This section uses ID 21579 as an example.
$ kill -9 21579
NOTE
– In the preceding command, 21579 is the process ID of ResourceMonitor. Replace it with

the actual value.
– After the preceding commands are used to stop the ResourceMonitor process, the system
automatically starts the process.
----End

C.3.3 Configuring Hardware Alarms for Huawei RH Series Rack

Servers (RH5885H V3 and RH2288H V2, iMana)
Hardware alarm configuration allows server hardware alarms to be uploaded to the U2000
server for monitoring.
Prerequisites
l The U2000 service is running properly.
l The alarm service is running properly.
NOTE
Log in to the server of the alarm service as the ossuser and run the following commands to view,
start or stop the alarm service.
l View the status of the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm
status
l Start the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm start
l Stop the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm stop
l iMana Version
– RH 2288HH V2: (U1029)6.0 or above
– RH 5885HH V3: (U6)5.97 or above
NOTE
To upgrade the system controller firmware version, see A.2.10 How to Upgrade the System
Controller Firmware Version for Huawei RH5885H V3 and RH2288H V2 Servers?.
Context
The purpose of configuring server hardware alarms is to enable uploading of theses alarms to
the U2000 for monitoring. If another system is already available for monitoring these alarms
or they do not need to be monitored by the U2000, such configuration is not required.
Procedure
Step 1 Configure U2000 information.
1. Log in to the U2000 server as the ossuser user using the PuTTY.
2. Run the following command to configure U2000 information:
$ cd /opt/oss/manager/alarmmonitor/bin
$ ./alarm_receiver_mgr.sh add -emsip=192.168.128.158
NOTE
– add indicates data adding.

– delete indicates data deletion.
– modify indicates data modification.
– query indicates data query.
-emsip: Set to U2000 application IP address.

The current user is ossuser.
The IP address<192.168.128.158> is reachable!
NOTICE: Enter a SNMP type.(As a SNMP type,must be north or heart)

=================================================================

1--north
2--heart
=================================================================
Select a SNMP type :
3. Enter a SNMP type, enter 1.

INFO: Succeeded in adding alarm receiving client 192.168.128.158.
Step 2 Set SNMP communication parameters on the server's controller card.

1. Refer A.2.1 How Do I Use iMana/iBMC IP to Log In to a Remote Huawei RH series
rack server to log in to the control card window.
2. Optional: Choose Configuration > User to access the Local User window and add
SNMP communication users.
NOTICE
Choose User Group to Administrator.
3. Choose Configuration > Log and Alarm to access the Trap window.
4. Select Trap State in Common Attributes.

5. In the SNMP Trap Attributes area, set Version to V3, Choose Username to the user
that server's control card uploads the alarms to the alarm service, and Trap Mode to
OID.
6. Select Enabled on the right of Trap 1, set Trap IP Address to the IP address of the
alarm service, and set Trap Port to 30085.

7. Click OK.
8. Choose Configuration > Service, click SNMP Configurations to access the SNMP
Configurations window.
Ensure that the SNMP Service is set to SNMP V3, SNMP V3 Authentication Protocol
is set to SHA and SNMP V3 Privacy Protocol is set to AES.
Step 3 Register the server to the alarm service.
1. Log in the OS with the alarm service as the ossuser user using the PuTTY.
2. Run the following command to configure use information:
$ ./user_mgr.sh

===============================================================
1--Add User
2--Delete User
3--Query User
E--Exit
===============================================================
Select an operation type :
3. Enter 1 to add a user account.

NOTICE: : Enter a user name.(The user name must contain 1 to 16 characters.)
NOTICE:
* A user name must contain 1 to 16 characters.
* A user name can not start with #
* A user name cannot contain special character : \ , .
Enter a user name:
4. Enter a user name.

NOTE
The entered user name is an SNMP user name for communication and is the same as the user
name set in Step 2.5.

NOTICE:
* A password must contain 8 to 30 characters.
* A password must contain at least one uppercase letter.
* A password must contain at least one lowercase letter.
* A password must contain at least one digit.
* A password must contain at least one special character ~ ! @ # $ % ^ &
* ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ?
* A password cannot contain three or more consecutive characters that are
the same(for example, AAA and 111).
Enter the authpassword:
5. Enter the user password.

Are you sure you want to add the user <admin99>? [Y/N]
NOTE
The entered password of the SNMP user name for communication and is the same as the password
of the user name set in Step 2.5.
6. Enter Y to confirm user adding.
If information similar to the following is displayed, the user account is successfully
added. In this case, press Enter.

INFO: Succeeded in adding the user .

===============================================================
NOTICE: Press Enter to return to the home page.
7. Run the following command to configure the server information.

$ ./node_mgr.sh

===============================================================
1--Add Node
2--Delete Node
3--Query Node
E--Exit
===============================================================
8. Enter 1 to add a node.

Select one user
===============================================================
1--User name: admin88
B--Back
===============================================================
Please input selections:
9. Select the mapping user and enter 1.

Enter the IP address of the Control Card:
10. Enter the node IP address.

NOTE
The entered IP address is the control card's IP address on the server with the alarm service. The
hardware server reports alarms over SNMP using the preceding configured user name and
password.

NOTICE: Enter a PCServer type.(As a PCServer type,must be RH2288H V2/RH2288H
V3 or RH5885H V3)
===============================================================
1--RH2288H V2/RH2288H V3
2--RH5885H V3
===============================================================
Select an PCServer type :
11. Select a hardware server type.

Are you sure you want to add the node < 10.67.145.231>? [Y/N]
12. Check that the hardware server information is successfully added.
If information similar to the following is displayed, the hardware server information is

successfully added.
INFO: Succeeded in adding the node test.
===============================================================
Step 4 Synchronize alarms.


2. Run the following command to synchronize alarms.

$ ./syncalarm.sh
If information similar to the following is displayed, the alarms are successfully

synchronized.
Begin to sync alarm.
INFO: Succeeded to sync alarm.

===============================================================
----End
C.3.4 Configuring Hardware Alarms for Huawei RH Series Rack

Servers (RH2288H V3 and RH5885H V3, iBMC)
Hardware alarm configuration allows server hardware alarms to be uploaded to the U2000
server for monitoring.
Prerequisites
l The U2000 service is running properly.
l The alarm service is running properly.
NOTE
Log in to the server of the alarm service as the ossuser and run the following commands to view,
start or stop the alarm service.
l View the status of the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm
status
l Start the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm start
l Stop the alarm service: /opt/oss/manager/alarmmonitor/bin/rcuniep_alarm stop
l iBMC Version:
– RH 2288HH V3: (U25)2.06 or above
– RH 5885HH V3: (U6)5.97 or above
NOTE
To upgrade the system controller firmware version, see A.2.11 How to Upgrade the System
Controller Firmware Version for Huawei RH2288H V3 server and Huawei RH5885H V3
server?.
Context
The purpose of configuring server hardware alarms is to enable uploading of theses alarms to
the U2000 for monitoring. If another system is already available for monitoring these alarms
or they do not need to be monitored by the U2000, such configuration is not required.
Procedure
Step 1 Configure U2000 information.
1. Log in to the U2000 server as the ossuser user using the PuTTY.
2. Run the following command to configure U2000 information:
$ ./alarm_receiver_mgr.sh add -emsip=192.168.128.158

NOTE
– add indicates data adding.

– delete indicates data deletion.
– modify indicates data modification.
– query indicates data query.
-emsip: Set to U2000 application IP address.

The current user is ossuser.
The IP address<192.168.128.158> is reachable!
NOTICE: Enter a SNMP type.(As a SNMP type,must be north or heart)

=================================================================
1--north
2--heart
=================================================================
Select a SNMP type :
3. Enter a SNMP type, enter 1.

INFO: Succeeded in adding alarm receiving client 192.168.128.158.
Step 2 Set SNMP communication parameters on the server's controller card.

1. Log in to the control card window.
2. Optional: Choose Configuration > User to access the Local User window and add
SNMP communication users.
NOTICE
Choose User Group to Administrator.
3. Choose Configuration > System Settings to access the System Settings window.
Ensure that the Set SNMP Version is set to V3, SNMP V3 AuthProtocol is set to
SHA1 and SNMP V3 PrivProtocol is set to AES.
4. Choose Alarm & SEL > Alarm Setting to access the Alarm Setting window.

5. In the Alarm Trap Notification Settings area, set Trap Function to ON.
6. In Set Trap Properties, set Trap Version to V3. Choose Trap V3 User to the user that
is configured to report alarms from the control card to the alarm server, and Trap Mode
to OID.
7. In Select Alarm Severities, select All and click Save.
8. In Configure Trap Server and Packet Format, click in a record to specify a trap
server and a packet format.
– Set Current Status to ON.

– Set Trap Server IP Address to the U2000 server IP address with the alarm service
configured.
– Set Trap Port to 30085.
– Set Packet Delimiter to ;.
– Select Time, Sensor Name, Severity, Event Code, and Event Description for
Select Packet Content.
– Select Display Keyword in Packet.
9. Click Save.
Step 3 Register the server to the alarm service.

2. Run the following command to configure use information:
$ ./user_mgr.sh

===============================================================
1--Add User
2--Delete User
3--Query User
E--Exit
===============================================================
3. Enter 1 to add a user account.

NOTICE: : Enter a user name.(The user name must contain 1 to 16 characters.)
NOTICE:
* A user name must contain 1 to 16 characters.
* A user name can not start with #
* A user name cannot contain special character : \ , .
Enter a user name:
4. Enter a user name.

NOTE
The entered user name is an SNMP user name for communication and is the same with the user
name set in Step 2.6.

NOTICE:
* A password must contain 8 to 30 characters.
* A password must contain at least one uppercase letter.
* A password must contain at least one lowercase letter.
* A password must contain at least one digit.
* A password must contain at least one special character ~ ! @ # $ % ^ &
* ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ?
* A password cannot contain three or more consecutive characters that are
the same(for example, AAA and 111).
Enter the authpassword:
5. Enter the user password.

Are you sure you want to add the user <admin99>? [Y/N]
NOTE
The entered password of the SNMP user name for communication and is the same with the
password of the user name set in Step 2.6.
6. Enter Y to confirm user adding.
If information similar to the following is displayed, the user account is successfully
added. In this case, press Enter.
INFO: Succeeded in adding the user .
===============================================================
7. Run the following command to configure the server information.

$ ./node_mgr.sh

===============================================================
1--Add Node
2--Delete Node
3--Query Node
E--Exit
===============================================================

8. Enter 1 to add a node.

Select one user
===============================================================
1--User name: admin88
B--Back
===============================================================
Please input selections:
9. Select the mapping user and enter 1.

Enter the IP address of the Control Card:
10. Enter the node IP address.

NOTE
The entered IP address is the control card's IP address on the server with the alarm service. The
hardware server reports alarms over SNMP using the preceding configured user name and
password.

NOTICE: Enter a PCServer type.(As a PCServer type,must be RH2288H V2/RH2288H
V3 or RH5885H V3)
===============================================================
1--RH2288H V2/RH2288H V3
2--RH5885H V3
===============================================================
Select an PCServer type :
11. Select a hardware server type.

Are you sure you want to add the node < 10.67.145.231>? [Y/N]
12. Check that the hardware server information is successfully added.
If information similar to the following is displayed, the hardware server information is

successfully added.
INFO: Succeeded in adding the node test.
===============================================================
Step 4 Synchronize alarms.

2. Run the following command to synchronize alarms.
$ ./syncalarm.sh
If information similar to the following is displayed, the alarms are successfully

synchronized.
Begin to sync alarm.
INFO: Succeeded to sync alarm.

===============================================================
----End

C.4 Configuring and Testing the FTP Service

During data synchronization, upgrade, backup, and patch installation of NEs, you need to
configure and test the FTP and SFTP service to ensure that the FTP services work properly
between NE software, the U2000, and NEs. This topic describes how to configure and test the
FTP and SFTP services on the U2000.
C.4.1 Overview of the FTP Service Used by the U2000

This topic describes the protocol mode, operation mode, and usage scenarios of the FTP
service used by the U2000.
FTP Service Protocol Mode

The U2000 supports two protocol modes for transferring FTP files: FTP and SFTP. In
comparison with FTP, SFTP is more secure and therefore is recommended to enhance system
security. For details about close insecure protocols, see A.1.2 How to Start/Stop the FTP/
SFTP/Telnet Service in the SUSE Linux OS.
NOTE
According to security requirements, the FTP service at the secondary site in an HA system is disabled by
default so that the site cannot be connected through FTP. You can use SFTP instead.
FTP Service Operation Mode

The U2000 supports two operation modes for using the FTP service: local FTP service mode
and third-party FTP service mode.
Figure C-1 FTP Service Operation Mode
l Local FTP service mode: The U2000 server functions as the FTP server. During the
U2000 installation, an FTP/SFTP user is created by default to implement file transfer
among the client, NEs, and U2000 server.
l Third-party FTP service mode: A computer is configured as the FTP server. In this case,
the FTP/SFTP service must be installed on the computer and an FTP/SFTP user must be
created to implement file transfer among the client, NEs, and U2000 server.

FTP Service Usage Scenario

After the U2000 is installed, four FTP accounts and eight FTP applications are provided by
default. Figure C-2 shows the default FTP accounts used by default FTP applications.
Figure C-2 Default FTP accounts used by default FTP applications
After the U2000 is installed, one default local FTP account and three default third-party FTP
accounts are available. Each FTP account is a combination of the FTP service mode, FTP user
account, and main directory. FTP applications can directly use the FTP accounts without
requiring the input of FTP user names or other information. The default local FTP account has
a default local FTP user named ftpuser. Information about the default local FTP account has
been configured and therefore can be directly used. However, the default third-party FTP
accounts can be properly used only after their information is configured on the third-party
FTP server. The following table lists information about the default FTP accounts.

Table C-1 Information about the default FTP accounts

Account Accoun Account Server Server FTP Main Path
Name t Type Function Name IP User Direct
s Address Name ory
Default Local l By U2000 Local ftpuser /opt/ ftproot

local FTP FTP default Server server NOTE backup NOTE
account account , this The / The
accou defaul ftpboot relati
nt can t ve
passw path
be
ord of and
used the the
by ftpuse main
multip r user direct
le FTP is ory
applic Chan form
geme the
ations,
_123. defau
such To lt
as ensure absol
ONT the ute
loadin syste path
g, NE m wher
securit e
softwa
y, run files
re the are
manag passw store
ement, d d by
batch comm the
perfor and to FTP
chang user.
mance
e the For
statisti passw exam
cs ord ple, /
collect imme opt/
ion, diatel back
NE y after up/
you ftpbo
license
log in ot/
manag to the ftpro
ement, syste ot is
and m for the
NE the defau
fault first lt
time. path
diagno
wher
sis e the
inform ftpus
ation er
collect stores
ion. files.
l This
accou
nt is
used
for file


s Address Name ory
transfe
r
betwe
en the
U2000
and
NEs.
It is
autom
aticall
y
create
d
during
U2000
install
ation
and
can be
directl
y
used.


s Address Name ory
Default Third- l This TL1 FTP/ FTP/ FTP/

access TL1 party accou SFTP SFTP SFTP
account FTP nt is server's user user
account used IP name passwo
to address provide rd
transfe provided d by an provid
r by an upper- ed by
access upper- layer an
- layer OSS upper-
domai OSS for for layer
n managin managi OSS
servic g the ng the for
e TL1 TL1 managi
provisi service service ng the
oning TL1
(xDSL service
,
xPON,
broadb
and,
and
narro
wband
servic
es),
invent
ory
query,
and
servic
e
provisi
oning
files to
an
upper-
layer
OSS.
l This
accou
nt can
be
used
only
after
being
config
ured.


s Address Name ory
Default Third- l This OSS_NBI FTP/ FTP/ FTP/

OSS PMS party accou SFTP SFTP SFTP
Account FTP nt is server's user user
upload provided d by an provid
an by an upper- ed by
IPMS upper- layer an
perfor layer OSS upper-
mance OSS for for layer
file managin managi OSS
collect g the ng the for
ed by IPMS IPMS managi
the performa perfor ng the
U2000 nce file mance IPMS
to an collected file perfor
upper- by the collecte mance
layer U2000 d by file
OSS. the collect
l This U2000 ed by
accou the
nt can U2000
be
used
only
after
being
config
ured.


s Address Name ory
uTrafficPf Third- l This uTraffic FTP/ FTP/ FTP/

mFTP party accou Server SFTP SFTP SFTP
FTP nt is server's user user
upload provided d by an provid
a by an upper- ed by
perfor upper- layer an
mance layer OSS upper-
file OSS for for layer
collect managin managi OSS
ed by g the ng the for
the IPMS perfor managi
uTraffi performa mance ng the
c to an nce file file perfor
upper- collected collecte mance
layer by the d by file
OSS. uTraffic the collect
l This uTraffi ed by
accou c the
nt can uTraffi
be c
used
only
after
being
config
ured.
After the U2000 is installed, eleven default FTP applications are available. The following
table lists information about the default FTP applications.
Table C-2 Information about the default FTP applications

Application Name Default FTP Account Description
Access System Default local FTP account The FTP service is used to verify
the dump command, NE
synchronization, exported
hardware reports, support for
board decoupling, and distributed
NE migration.

ONT LOAD Default local FTP account The FTP service is configured and
tested to ensure the normal
operation of the ONT automatic
upgrade tasks or value-added
services.
PMS BulkCollector FTP Default local FTP account The FTP service is used to collect
Account NE performance data in batches
for analysis and statistics
collection on the U2000.
MSO System Default local FTP account The FTP service is configured to
ensure that the PNM, real-time
spectrum scanning, and historical
spectrum scanning functions of
the MSO system can be properly
used to collect device data for the
MSO system to analyze and
display.
This application applies only to
the access domain U2000 where
the MSO component is installed.
NE Software Default local FTP account The FTP service is configured and
Management(Client) tested to ensure normal
transmission of xFTP files
between the U2000 server and
client. This allows NE data
backup, NE data recovery, and
software library import from the
client.
NE Software Default local FTP account The FTP service is configured and
Management(NE) tested to ensure normal
transmission of xFTP files
between the U2000 server and
client. This helps implement
functions such as NE data backup,
recovery and software library
importing from the server.
NE License Management Default local FTP account The FTP service is configured and
tested to ensure normal license
file transmission between the
U2000 and NEs and implement
NE license upload and
management.
Information Collection Default local FTP account The FTP service is used to collect
of Device Fault NE fault diagnosis data for
Diagnosis analysis and statistics collection
on the U2000.

IP Common Default local FTP account FTP account isolation ensures

Management (NE) normal network-wide data
backup, fault information
collection, NE replacement, and
script delivery. Binding a third-
party FTP account to IP
Common Management (NE) is
not supported.
TL1 Default access TL1 The FTP service is used to

account transfer access-domain service
provisioning (xDSL, xPON,
broadband, and narrowband
services), inventory query, and
service provisioning files to an
upper-layer OSS for analysis and
statistics collection.
Perf-FTP/SFTP Default OSS PMS The FTP service is used to upload

Account a performance file collected by
the U2000 to an upper-layer OSS
collection.
TransNetwork Perf-FTP/ uTrafficPfmFTP The FTP service is used to upload

SFTP a performance file collected by
the uTraffic to an upper-layer OSS
collection.
C.4.2 Procedure for Configuring and Testing the FTP Service on

the U2000
This topic describes the procedure for configuring and testing the FTP service on the U2000.
After the U2000 is installed, each application of the FTP service obtains a default FTP
account that is bound to a default FTP user. To enable an application to use the FTP service
with its own FTP account, create an FTP user and an FTP account mapped to the user, and
then add the FTP account to the application. You are advised to use the default FTP account,
without adding any new FTP user. Figure C-3 shows the procedure for configuring and
testing the FTP service.

Figure C-3 Procedure for configuring and testing the FTP service on the U2000
C.4.3 Checking the Startup Status of FTP Servers (Linux)

This topic describes how to check the startup status of local FTP servers. If the involved FTP
server has not been started, start it manually.
Prerequisites
FTP servers are functioning properly, and the FTP/SFTP service has been installed.
Context
The U2000 supports both local and third-party FTP servers. If over 5,000 NEs are managed,
you are advised to use third-party FTP servers to transfer files between the U2000 and NEs.
This topic focuses on how to check the startup status of a local FTP server.
If a local FTP server is used (SFTP is recommended because it provides better security.), the
FTP/SFTP service is automatically installed.
l The ftpuser user is automatically created during U2000 installation. The ftpuser user is
a default user of the FTP service that is enabled by default.
l the OpenSSH software is automatically installed during U2000 installation. In addition,
the SFTP service is automatically installed, and the ftpuser and sshd users are
automatically created.
– sshd: user of the SSH service that is disabled by default. This user is automatically
created during OpenSSH installation.
– ftpuser: default user of the SFTP service that is enabled by default. This user is
created by the U2000.

NOTE
According to security requirements, the FTP service at the secondary site in an HA system is disabled by
default so that the site cannot be connected through FTP. You can use SFTP instead.
Procedure
Step 1 Log in to the operating system as a user with ossuser rights.
Step 2 Use the FTP software (for example, FileZilla) to connect to the U2000 server. If the
connection is successful, the FTP service has started. If the connection fails, the FTP service
has not started.
----End
Follow-up Procedure
How Do I Manually Enable and Disable the FTP Service on a Server, see A.1.2 How to
Start/Stop the FTP/SFTP/Telnet Service in the SUSE Linux OS.
C.4.4 Creating an FTP User

This topic describes how to create an FTP user on the local FTP server and specify a
password for the user.
Context
l After the U2000 is installed, each FTP service application has a default FTP account that
is bound to a default FTP user. An FTP user must be created only when an application
requires an independent account.
l A newly created user can be an FTP or SFTP user.
l This topic only describes how to create an FTP user on the local FTP server. If a third-
party FTP user is required for an application, the user must have been created and the
user account is valid.
l The procedure below instructs you how to create the FTP user neftpuser, assuming that
the main FTP directory is /opt/backup/neftpboot/ and the user's files need to be saved
to /opt/backup/neftpboot/ftproot/.
Procedure
Step 1 Log in to the local FTP server as the root user root using SSH.
Step 2 Run the following command to create the FTP user named neftpuser:
# useradd -d /opt/backup/neftpboot -g ossgroup -G ossgroup -m -k /etc/skel -
s /bin/bash neftpuser
NOTE
l neftpuser is the newly created FTP user.

l /opt/backup/neftpboot is the main path for the newly created FTP user and must be unique.
Step 3 Set a password for the newly created FTP user as follows:
1. Run the following command to set a password for the FTP user.
# passwd FTP user name
For example, passwd neftpuser.

2. 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.
3. Enter the new password again as prompted. Press Enter to make the change take effect.
NOTE
In addition, you can perform the preceding steps to change the default FTP user password.
Step 4 Run the following command to assign rights to the main path of the newly created FTP user:
# chmod 755 /opt/backup/neftpboot
# chown root:ossgroup /opt/backup/neftpboot
Step 5 Run the following commands to create the directory to which the new FTP user's files will be
saved to and assign rights to the directory:
# mkdir -p /opt/backup/neftpboot/ftproot
# chmod 771 /opt/backup/neftpboot/ftproot
# chown ossuser:ossgroup /opt/backup/neftpboot/ftproot
NOTE
l /opt/backup/neftpboot is the main path for the newly created FTP user.
l FTP root directory/ftproot/ is the directory where files are saved.
Step 6 Perform the following operations so that the newly created FTP user can access only the
directory for the FTP user neftpuser and files:
NOTE
After this step is performed, the newly created FTP user neftpuser can access only the directory for the
FTP user neftpuser (/ftproot) and files.
l Perform the following operations so that the newly created FTP user can access only the
main directory, sub-directories, and files:
a. Log in to the local FTP server as the root user root using SSH.
b. Run the vi command to open the vsftpd.chroot_list file.
# vi /etc/vsftpd.chroot_list

ftpuser
c. Add the newly created FTP user neftpuser to the vsftpd.chroot_list file as follows:
ftpuser
neftpuser
d. Run the :wq command to save the configuration and exit the vi editor.
l Perform the following operations so that the newly created FTP user can access only the
main directory, sub-directories, and files:
b. Run the vi command to open the sshd_config file.
n On Solaris:
# vi /usr/local/etc/sshd_config
n On Linux:
# vi /etc/ssh/sshd_config

............
Match User ftpuser
ChrootDirectory %h
ForceCommand internal-sftp
............

c. Add the newly created FTP user neftpuser to the Match User ftpuser line.
............
Match User ftpuser,neftpuser
ChrootDirectory %h
ForceCommand internal-sftp
............
Step 7 Optional: Perform the following operations so that SFTP logs of a newly created FTP user
are recorded:
NOTICE
l If the main directory of an FTP user changes, re-perform the following operations so that
the FTP user's SFTP logs are recorded:
l A newly created FTP user neftpuser and the user's main directory (/opt/backup/
neftpboot) are used as an example.
l On Linux:
b. Run the vi command to open the sbin.syslog-ng file.
# vi /etc/apparmor.d/sbin.syslog-ng
/sbin/syslog-ng {
............
/sbin/syslog-ng mr,
# chrooted applications
/var/lib/*/dev/log w,
/var/log/** w,
............}
c. Add /opt/backup/neftpboot/dev/logw to the sbin.syslog-ng file as follows:
/sbin/syslog-ng {
............
/sbin/syslog-ng mr,
# chrooted applications
/var/lib/*/dev/log w,
/var/log/** w,
/opt/backup/neftpboot/dev/log w,
}
e. Run the vi command to open the syslog-ng.conf file.
# vi /etc/syslog-ng/syslog-ng.conf
............
source src {
............
#
#
#udp(ip("0.0.0.0") port(514));
};
f. Add unix-dgram("/opt/backup/neftpboot/dev/log") to the syslog-ng.conf file as
follows:

............
source src {
............
unix-dgram("/opt/backup/neftpboot/dev/log");
#
#
#udp(ip("0.0.0.0") port(514));
};
g. Run the :wq command to save the configuration and exit the vi editor.
h. Run the following commands to create a directory for the FTP user's logs and
assign rights to the directory:
# mkdir /opt/backup/neftpboot/dev
# chmod 700 /opt/backup/neftpboot/dev
# chown neftpuser:ossgroup /opt/backup/neftpboot/dev
i. Run the following command to restart the syslog-ng:

# rcsyslog restart
j. Change the /opt/backup/neftpboot/dev/log rights.

# chmod 600 /opt/backup/neftpboot/dev/log
# chown neftpuser:ossgroup /opt/backup/neftpboot/dev/log
l On Solaris:
b. Run the following commands to create a directory for the FTP user's logs and
assign rights to the directory:
# mkdir /opt/backup/neftpboot/dev
# chmod 755 /opt/backup/neftpboot/dev
# chown root:sys /opt/backup/neftpboot/dev
c. Run the following command to check file attributes of the log and conslog:
# ls -lL /dev/ |grep log

crw-rw-rw- 1 root sys 21, 0 May 28 15:32 conslog
crw-r----- 1 root sys 21, 5 Aug 13 10:50 log
............
NOTE
In the preceding information, 21 and 0 are file attributes of the conslog, and 21 and 5 are file
attributes of the log.
d. Run the following commands to create the /opt/backup/neftpboot/dev/log
and /opt/backup/neftpboot/dev/conslog devices:
# mknod /opt/backup/neftpboot/dev/conslog c 21 0
# mknod /opt/backup/neftpboot/dev/log c 21 5
NOTE
In the preceding two commands, 21 0 and 21 5 are file attributes of the conslog and log.
e. Run the following command to restart the syslog:
# svcadm restart svc:/system/system-log:default
----End
C.4.5 Creating an FTP Account and Adding it to an FTP

Application
This topic describes how to create an FTP account on a U2000 client and add the account to
the associated FTP application. If no new FTP account is required, skip this topic.

Prerequisites
l You are an NMS user with Operator Group authority or higher.
l On the FTP server, create an FTP user for the associated FTP application.
Context
l By default, the local FTP account and associated FTP application have been configured
after a U2000 client is installed. Do not modify the default settings.
l Multiple FTP applications can share one FTP account.
l The procedure for creating new account NE Management FTP Account to be used for
the NE Software Management(NE) application and binding the neftpuser user is used
as an example.
Procedure
Step 1 Choose Administration > Settings > FTP Account Information Management from the
main menu (traditional style); alternatively, double-click System Management in
Application Center and choose Settings > FTP Account Information Management from
the main menu (application style).
Step 2 In the FTP Account Information Management dialog box, click the Configure FTP
Account tab.
Step 3 On the Configure FTP Account tab, add account NE Management FTP Account for the
NE Software Management(NE) application.
1. Right-click in a blank area and choose Add from the shortcut menu.
2. In the Add FTP User dialog box, set parameters such as FTP Account, Server Name,
and Server IP Address.
– FTP Account: name of the new account, for example, NE Management FTP
Account
– Server Type: running mode of the FTP service, for details, see Table C-3
Table C-3 Server Type
Serve Parameter Description

r
Type
local Server Name Indicates the FTP server name.
User Name Indicates the user name for logging in to the FTP
server.


r
Type
FTP Port Indicates the port used for FTP transmission between
an FTP client and the FTP server.
SFTP Port Indicates the port used for SFTP transmission between
Password Indicates the password for logging in to the FTP

server.
Home Indicates the work directory of an FTP user.

Directory
Path n Relative path such as ftproot/ where the neftpuser

user stores files.
n The relative path and the home directory form the
absolute path, such as /opt/backup/neftpboot/
ftproot/, where the neftpuser user stores files by
default.
Third Server Name Indicates the FTP server name.

Party
Server IP Indicates the IP address of the FTP server.
Address
User Name Indicates the user name for logging in to the FTP
server.
Protocol Indicates the protocol used for data transmission

between NEs on the FTP server.
SFTP Port Indicates the port used for SFTP transmission between
Check Public Check whether the public key entered by users is the
Key same as that of the third-party FTP server public key.
NOTE
The Check Public Key can be selected only when Server
Type is Third Party and Protocol is SFTP.
Public Key Format of the third-party FTP server public key.

Format
Public Key Content of the public key.

Content


r
Type
Authenticatio Indicates the authentication mode for logging in to the

n Mode FTP server.
NOTE
n The Authentication Mode can be selected only when
Server Type is Third Party and Protocol is SFTP.
n The Password can be set only when Authentication
Mode is Password.
n The Private key file path and Private key file
passwordcan be selected only when Authentication
Mode is Public key .
Password Indicates the password for logging in to the FTP

server.
Path n Relative path such as ftproot/ where the neftpuser

user stores files.
n The relative path and the home directory form the
absolute path, such as /opt/backup/neftpboot/
ftproot/, where the neftpuser user stores files by
default.
Private key Indicates the local path to the private key file.
file path
Private key Indicates the password of the private key file.

file password
NOTE
– The account is created only for registration. The FTP user used for the account must be created
on the FTP server before account creation; otherwise, the FTP account cannot be properly used
after being created.
– FTP user information configured in this step must be the same as that on the FTP server.
– As SFTP is securer than FTP, SFTP is recommended when Server Type is set to Third Party.
3. Click OK.
4. In the Result dialog box, click Close.
Application tab.

NOTE
l The FTP applications Information Collection of Device Fault Diagnosis and Access System applies
only to the access domain.
l The FTP application IP Common Management(NE) applies only to the IP domain. Binding a third-
party FTP account to the FTP application is not supported.
Step 5 On the Configure FTP Application tab, add NE Management FTP Account to the NE
Software Management(NE) application.
1. Right-click the NE Software Management(NE) application and choose Modify from
the shortcut menu.
2. In the Modify FTP Application dialog box, select NE Management FTP Account.
3. Click OK.
4. In the Result dialog box, click Close.
NOTE
l One FTP application can use only one local FTP account, and one FTP account can be bound to only
one FTP user.
l After NE Management FTP Account is added to the NE Software Management(NE) application,
the default local FTP account is no longer used when NE Management FTP Account is used to
transfer files.
----End
Follow-up Procedure
l If FTP account information on the FTP server changes, perform the following operations
to modify FTP accounts on a U2000 client to keep consistency with those on the FTP

server. Consistent FTP information ensures normal FTP services. Only the FTP accounts
on a client are modified and the modifications do not affect FTP accounts on the FTP
server.
a. Right-click a desired FTP account and choose Modify from the shortcut menu.
b. In the Modify FTP User dialog box, modify parameters except FTP Account
based on site requirements.
c. Click OK.
d. In the Result dialog box, click Close.
l Perform the following operations to delete unused FTP accounts from a client, which
does not affect FTP accounts on the FTP server:
a. Right-click a desired FTP account and choose Delete from the shortcut menu.
b. Click OK when the Warning dialog box is displayed indicating that the selected
account will be deleted.
c. In the Result dialog box, click Close.
C.4.6 Testing the FTP Service

After configuring FTP accounts used by FTP applications, you need to test the accounts to
ensure that the FTP function operates properly on an FTP server. A normal FTP function
ensures normal communication and file transfer between the FTP server and FTP client.
Prerequisites
l The FTP service on an FTP server has been enabled.
l The FTP user used for an FTP application has been created, and user information has
been configured on the FTP server.
Procedure
Step 1 Choose Administration > Settings > FTP Account Information Management from the
main menu (traditional style); alternatively, double-click System Management in
Application Center and choose Settings > FTP Account Information Management from
the main menu (application style).
Account tab.
Step 3 On the Configure FTP Account tab, right-click a desired FTP account and choose Test from
the shortcut menu to test whether the FTP function is available.
Step 4 In the dialog box that is displayed, click Test FTP or Test SFTP to test the FTP or SFTP
function of the FTP server.

l If the test succeeds, click Close in the Result dialog box.

l If the test fails, verify that the FTP user exists on the server, the FTP user name and
password are correct, the FTP service has been started, and the directory rights are
correct. Then test the FTP service again.
NOTE
l When adding or modifying an FTP account, you can click Test to test the new or modified FTP
account.
l If the test succeeds, the FTP user information on the client is the same as that on the server, and the
client can properly communicate with the server.
----End

and Commissioning Guide (SUSE Linux) D Starting the U2000 Server
D Starting the U2000 Server
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. The U2000 can start properly only after the
database is started.
D.3 Starting the U2000 Server Processes
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
1. Power on a Huawei RH2288H V2/Huawei RH2288H V3/Huawei RH5885H V3/IBM
X3650 M4/IBM X3650 M3/IBM X3850 X5 server.
NOTICE
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC
and 200 to 240 VAC input voltage.

NOTE
RH2288H V2, Huawei RH2288H V3, Huawei RH5885H V3, IBM X3650 M4, IBM
X3650 M3 and, IBM X3850 X5.
Figure D-1 Position of the power button on Huawei RH5885H V3 server
Figure D-4 Position of the power button on IBM X3650 M4

Figure D-5 Position of the power button on IBM X3650 M3
Figure D-6 Position of the power button on IBM X3850 X5
Disk Array
NOTICE
it on.
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.
D.2 Starting the Database

This topic describes how to start the database. The U2000 can start properly only after the
database is started.

Prerequisites
The OS has been started.
Context
Generally, the database starts along with the OS.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. 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 details, see A.1.1 How to Change the OS User Password.
Step 2 Run the following command to check whether the Sybase database is running.

install/RUN_DBSVR
...
NOTE

Step 3 Run the following commands to start the Sybase database if it is not running.
NOTE
interfaces command.
----End
Result
Run the following command to check whether the Sybase process is running:


install/RUN_DBSVR
...
NOTE

D.3 Starting the U2000 Server Processes

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 PC server on which the U2000 server processes are installed is running
properly, and the database has been started.
Context
Generally, the U2000 server processes start along with the OS.
Procedure

$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb
NOTE
Run the following command to start the U2000 if it is not running:

$ ./startnms.sh
----End

Result
l If the U2000 services with the startup type of Automatic have started properly, the
U2000 runs properly.
l If some services have not started, select them, right-click, and choose Start the Service
from the shortcut menu.
l If the U2000 does not run properly, contact Huawei engineers.

and Commissioning Guide (SUSE Linux) E Shutting Down the U2000 Server
E Shutting Down the U2000 Server
Three steps are required to shut down the U2000 server: stop the U2000 server processes, shut
down the database, 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.
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 SUSE Linux single-server system.
E.3 Powering 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 single-server system (SUSE Linux) .
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.
Prerequisites
All running U2000 clients have been stopped.
Procedure
Step 2 To check the running status of the U2000 process, run the following command:
$ daem_ps

ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb


NOTE
Step 3 Run the following commands to stop U2000 if it is running:

$ ./stopnms.sh
----End
Result
Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
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 SUSE Linux single-server system.
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. 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 details, see A.1.1 How to Change the OS User Password.
Step 2 Run the following command to check whether the Sybase database is running.

install/RUN_DBSVR
...

NOTE

Step 3 Run the following commands to stop the Sybase database if it is running:
NOTE
Enter the database administrator user password as prompted. The initial password of the database
2> go
1> shutdown
2> go
NOTE
the database.
CT-LIBRARY error:
----End
Result
NOTE
The database is stopped if the displayed information does not contain /opt/sybase/ASE-15_0/bin/
dataserver -sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back.
E.3 Powering 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 single-server system (SUSE Linux) .
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 1 Log in to the OS as the ossuser user. Run the following command to switch to the root user.
$ su - root
Password: password for the root user

Step 2 Run the following commands to shut down the OS.

# shutdown -h now
NOTE
If you do not want to power off the server, you can run the following commands to restart the OS:
# shutdown -r now
----End

and Commissioning Guide (SUSE Linux) 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 in 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.chiark.greenend.org.uk/~sgtatham/putty/download.html to download the PuTTY. For more
information about software operation, see the software Help or go to the official website of the software
http://www.chiark.greenend.org.uk/~sgtatham/putty/docs.html 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.15 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 SSH IP address of the server to be logged in to, and then press Enter.
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 Run the following

commands to restart the OS: commands 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 Run the following
commands to shut down the commands to shut down the
OS: 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:
# cd /opt/SEK
# ./rollbackSEK.sh l If the OS version is Suse
11, run the following
command:
# cd /opt/SEK
# ./rollbackSEK.sh
l If the OS version is Suse

10, run the following
command:
# sek -b all

and Commissioning Guide (SUSE Linux) 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

An Huawei RH series rack server (RH2288H V3 and RH5885H V3) for standard delivery is
equipped with eight hard disks (600G), with six for current use and two for further use.
Details about the planning for the RAID level and partition are as follows:
data.
l The seventh hard disk is used to system back up. It is configured as RAID 0.
An Huawei RH series rack server (RH5885H V3 and RH2288H V2) for standard delivery is
equipped with eight hard disks (300G), with six for current use and two for further use.
Details about the planning for the RAID level and partition are as follows:
data.
l •The seventh hard disk functions as a standby disk that substitutes for a damaged hard
disk. It is configured as RAID 0.
NOTE
l If the size and the number of hard disks to be configured for the server are not standard, contact
Huawei engineers to obtain the hard disk partitioning solution.
l You can run the df -h command to check disk partitions.

Table G-1 Partitioning solution

Hard Disk Load Point Size( Description
GB)
First hard disk / 20 It is the root partition.

NOTE
Partitioning is performed
swap 32 It is used for switching data in the
only on the first hard disk and system.
the second hard disk is used NOTE
as a mirroring disk. Run cat /proc/swaps command as
root user to view the information of
swap.
/usr 20 It is used for storing programs or

files of users.
/var 16 It is used for storing system logs.
/var/log 10 -
/var/log/ 4 -
audit
/opt 120 It is used for storing U2000

software and engineering-related
software.
/tmp 20 It is used for storing temporary

files.
/export/ 20 It is the main user directory.

home
Third and fourth hard disk /opt/sybase/ 100 It is used to store database data.
NOTE data
only on the third and fourth /opt/backup 400 It is used to store backup data.
hard disks and the fifth and
sixth hard disks are used as
the mirroring disks.
The seventh hard disk /opt/ 300 It is used to system back up.
ssrbackup_l
ocal
The eighth hard disk /opt/backup/ 300 It is used to back up the database.
forDBSVRB
CK
Server Connecting to a Disk Array

Configure two hard disks for the Huawei server (RH5885H V3) with standard delivery
configurations. Configure 12 hard disks for the OceanStor 5500 V3 or OceanStor S3900 disk
array. The RAID and partition planning is as follows:

l Configure the two hard disks on the server as RAID 1. Install the OS software and
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 If the size and the number of hard disks to be configured for the server are not standard, contact
Huawei engineers to obtain the hard disk partitioning solution.
l You can run the df -h command to check disk partitions.
Table G-2 Hard disk partition planning for the server

Hard Disk Load Point Size(GB) Description
First hard disk / 20 It is the root partition.

NOTE
swap 32 It is used for switching data in
only on the first hard disk the system.
and the second hard disk is NOTE
used as a mirroring disk. Run cat /proc/swaps command as
root user to view the information
of swap.
/usr 20 It is used for storing programs

or files of users.
/var 16 It is used for storing system

logs.
/var/log 10 -
/var/log/audit 4 -
/opt 120 It is used for storing U2000

software and engineering-
related software.
/tmp 20 It is used for storing temporary

files.
/export/home 20 It is the main user directory.
Table G-3 Disk array partition planning

Partition Name Load Point Size (GB) Remarks
sdb1 /opt/Sybase 400 It is used for storing

database software
and database.
sdb2 /opt/oss 200 It is used for storing

U2000 software.

Partition Name Load Point Size (GB) Remarks
sdb3 /opt/backup 400 It is used for storing

backup files.
sdb4 /opt/backup/ 400 It is used to back up

forDBSVRBCK the database.

and Commissioning Guide (SUSE Linux) H Configuring Disk Arrays
H Configuring Disk Arrays
This topic describes how to configure the OceanStor 5500 V3, OceanStor S3900 disk arrays.
H.1 Configuring the OceanStor 5500 V3 Disk Array Using the OceanStor DeviceManager
This topic describes how to configure the OceanStor 5500 V3 disk array using the OceanStor
DeviceManager
H.2 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 5500 V3 Disk Array Using

the OceanStor DeviceManager
This topic describes how to configure the OceanStor 5500 V3 disk array using the OceanStor
DeviceManager
Prerequisites
l The IP addresses for both controllers of OceanStor 5500 V3 the disk array are
configured. For details about how to set and view the IP addresses for controllers of the
OceanStor 5500 V3, see 4.6.3.1 Setting the SC IP Address for the OceanStor 5500 V3
Disk Array.
l The primary and secondary power supplies of the disk array have been powered on. For
more information, see 4.5 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 9.0, Internet Explorer 10, or Internet Explorer 11.
Context
The OceanStor DeviceManager will lock up if an operation is not performed within 10
minutes after login. Enter the password again to log in if a lockup occurs.

NOTICE
If the selected disk arrays are not the OceanStor 5500 V3 disk arrays (12x600 GB), contact
Huawei engineers for details about how to configure the disk arrays.
Procedure
Step 1 Log in to the OceanStor DeviceManager.
1. Open the Internet Explorer on the Windows management terminal.
2. Enter https://XXX.XXX.XXX.XXX:8088 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://10.9.1.10:8088.
NOTE
– XXX.XXX.XXX.XXX indicates the IP address of the management network port of the storage
array controller.
– Port 8088 needs to be enabled when the system provides the web service externally in an
environment with the firewall deployed.
– A message may be displayed indicating that the security certificate of the website brings risks.
In this case, ignore the message and continue to visit the disk array as long as the IP address is
correct.
The OceanStor DeviceManager login window is displayed.

3. Enter the user name and password and click Log in to log in to the OceanStor
DeviceManager.
NOTE
– Username: The default user name is admin.

– Password: The default password is Admin@storage. If the disk array is preinstalled, the
password is Changeme_123. (If the password has already been changed, enter the new
password. If the password is never changed, refer 4.6.3.1 Setting the SC IP Address for the
OceanStor 5500 V3 Disk Array to change it regularly and keep it privately.)
In the Welcome to OceanStor DeviceManager dialog box, click Close.
Step 2 Create a disk domain.

1. Log in to the Create Disk Domain dialog box.
a. Click in the navigation bar on the right.

b. Click Disk Domain.
The Disk Domain page is displayed.
c. Click Create.
The Create Disk Domain dialog box is displayed.
2. Set disk domain parameters.
The following table shows the parameter description.

Name Indicates the new disk domain's name such as

DISKDOMAIN001.
Select Disk Indicates all available disks.
3. Click OK.
A message is displayed indicating an operation success.
4. Click OK.
Step 3 Create a storage pool.

1. Log in to the Create Storage Pool dialog box

b. Click Storage Pool.
The Storage Pool page is displayed.
c. Click Create.
The Create Storage Pool dialog box is displayed.
2. Set storage pool parameters.
Name Indicates the new storage pool's name such as

STORAGEPOOL001.
Usage Block Storage Service
Disk Domain DISKDOMAIN001
RAID Policy RAID 10
Capacity Indicates the available capacity such as 8674 GB.
3. Click OK.
The Execution Result dialog box is displayed.
4. When State is Succeeded, click Close. Storage pool creation completes.
Step 4 Create LUN.

1. Log in to the Create LUN dialog box.

b. Click LUN.
The LUN page is displayed.
c. Click Create.
The Create LUN dialog box is displayed.
2. Set LUN parameters.
Name Indicates the new LUN name such as LUN001.
Capacity 1500
Quantity 1
Owning Storage Pool STORAGEPOOL001
Owning Controller CETO.A
3. Click OK.
4. When State is Succeeded, click Close. LUN creation completes.
Step 5 Create LUN group.

1. The Create LUN Group dialog box is displayed.

b. Click LUN.
The LUN page is displayed.
c. Click Create.
The Create LUN Group dialog box is displayed.
2. Set LUN group parameters.
a. In the Name text box, enter the name of the LUN group to be created, such as
LUNGROUP001.
b. Optional: In the Description text box, enter information such as the purpose and
attributes of the LUN group to be created, helping identify the LUN group.
c. Select LUN001 created in Step 4 in the Available LUNs area and click to
move it to the Selected LUNs area.
3. Click OK.
4. When State is Succeeded, click Close. LUN group creation completes.
Step 6 Create a host.

1. Log in to the Create Host Wizard dialog box is displayed.

b. Click Host.
The Host page is displayed.
c. Click Create and choose Manually Create.
The Create Host Wizard dialog box is displayed.
2. Set host parameters.
Name Indicates the new host's name such as HOST001.
OS Linux
3. Set host initiator parameters.

a. Click Next.
The Configure Initiator dialog box is displayed.
b. In the Available Initiators area, set Initiator Type to FC. All initiators will be
selected. Then click to move the selected initiators to the Selected Initiators
area.
4. Confirm the creation.
a. Click Next.
The Summary dialog box is displayed.
b. Click Finish to confirm created host's information.
The Warning dialog box is displayed.
c. Read the displayed message carefully and select I have read and understood the
consequences associated with performing this operation..
d. Click OK.
The Execution Result dialog box is displayed, indicating an operation success.
e. Click Close. Host creation completes.
Step 7 Create host group.
1. Log in to the Create Host Group dialog box.

b. Click Host.
The Host page is displayed.

c. Click Create.
The Create Host Group dialog box is displayed.
2. Set host group parameters.
Name Indicates the new host group's name such as

HOSTGROUP001.
3. Select one or more hosts to be added to the host group.

a. In the Available Hosts area, select hosts created in Step 6.
b. Click to move the selected ones to the Selected Hosts area.

a. Click OK.
b. When State is Succeeded, click Close. Host group creation completes.
Step 8 Create a mapping view.
1. Log in to the Create Mapping View dialog box.

b. Click Mapping View.
The Mapping View page is displayed.
c. Click Create.
The Create Mapping View dialog box is displayed.
2. Set mapping view parameters.
a. In the Name text box, enter the mapping view name such as MappingView001.
b. Optional: In the Description text box, enter the mapping view description.
3. Add a host group to the mapping view.
a. Click .
The Select Host Group dialog box is displayed.
b. Select the host group created in Step 7 from the list.
c. Click OK.
4. Add a LUN group to the mapping view.
a. Click .
The Select LUN Group dialog box is displayed.
b. Select the LUN group created in Step 5 from the list.

c. Click OK.
a. Click OK.
b. Read the displayed message carefully and select I have read and understood the
c. Click OK.
d. When State is Succeeded, the mapping view is successfully created. In this case,
click Close.
Step 9 Restart device.
1. Click in the navigation bar on the right.

2. Click Restart Device.
3. Read the displayed message carefully and select I have read and understood the
4. Click OK. The Succeeded dialog box is displayed.
5. Click OK to restart the disk array.
Step 10 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:2:0:0] disk LSI LSI 3.19 /dev/sda
[6:0:0:0] cd/dvd TSSTcorp CDDVDW SN-208DB CH00 /dev/sr0
[7:0:0:0] disk HUAWEI XSG1 4302 -
[7:0:0:1] disk HUAWEI XSG1 4302 /dev/sdb
[8:0:0:0] disk HUAWEI XSG1 4302 -
[8:0:0:1] disk HUAWEI XSG1 4302 /dev/sdc
Find the last two lines containing 4302 in the fourth column. Information in the first columns
([7:0:0:0] and [8:0:0:0]) indicates that the OceanStor 5500 V3 disk array connects to the server
through port 7 and port 8.
The following message will be displayed:
running

NOTE
If the fiber card is not in the running state, check and ensure the following aspect:
– The fiber is properly connected to the optical module.
– There is not any damage to the fiber.
– The optical module is properly connected to the fiber card.
– 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
H.2 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 4.6.3.2 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 4.5 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 7.0, Internet Explorer 8.0, or Internet Explorer 9.0.
Context
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.
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

Configure Settings
Item
Host group Set the host group name to HostGroup001.

and host Set the host name to Host001.
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: 1500 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://10.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
on name 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 Select a desired device type. Choose Storage Unit from the drop-down
Type 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:
– The discovery range is the IP subnet segment of the ISM client.
– 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.
– 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:
– This parameter contains only the characters and numerals in DBC
case, underscores (_), en-dash symbols (-), and simplified Chinese
characters.
– 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:
– This parameter contains only the characters and numerals in DBC
case, underscores (_), en-dash symbols (-), and simplified Chinese
characters.
– 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
After an admin user enters an incorrect password for three consecutive times, the
admin user will be locked and therefore cannot be used to log in to the disk array
controller. The admin account will be automatically unlocked after 15 minutes.
The default user name and password of the system administrator are admin and
Admin@storage. 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:
– This parameter ranges from 6 to 16 characters.
– 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
synchronizi Synch Schedule(number of hours) must be set.
ng
Manual Specifies a manual modification of the time and time zone of the
Modificatio device. Click Modify. In the Modify Time dialog box, set the time and
n time zone 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 – Level settings: Select the level at which users can receive fault
information.
– Outbox settings: Set Sender Email, SMTP Server, and SMTP
Port.
– 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.
– SMS center service number: Enter a desired SMS center service
number as prompted.
– 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
n and SMS notification are correct.

Syslog The following parameters must be set if notifications are sent through
Notificatio syslogs:
information.
– 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 1500 GB.
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.
The following message will be displayed:
Link Up - Loop
NOTE
If the fiber card is not in the Link Up state, check and ensure the following aspect:
– The fiber is properly connected to the optical module.
– There is not any damage to the fiber.
– The optical module is properly connected to the fiber card.
– 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

and Commissioning Guide (SUSE Linux) 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
environment server. 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
EMS immediately the 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
architecture clients. 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
Environment for 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
Request Broker of programs (objects) communicate with other objects in other programs, even if the
Architecture two 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
Request Broker of programs (objects) communicate with other objects in other programs, even if the
Architecture two 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
Configuration Protocol parameters 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
channel layer, 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

F
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
G
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
element and 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 A visual computer environment that represents programs, files, and options with
interface 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
H
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 The high availability system (HA) system indicates that two servers are adopted by a
system 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 transmit only keyboard actions, mouse responses, and screen updates on the network.
architecture
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
Organization data 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-
numbers authority space 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
Version 6 specifications 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
J
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
K
keyboard, video, and A hardware device installed in the integrated configuration cabinet. KVM serves as
mouse the 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
Protocol 802.1ab. 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
Algorithm 5 Hash 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
Network computer 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
transmission platform transmitting 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 The Network Time Protocol (NTP) defines the time synchronization mechanism. It
Protocol 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
Dial in User Service interface 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
Protocol implement 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
Protocol facilitates 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
Management Protocol modify 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
Protocol the 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
Network using 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.
T
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
management task), 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.
U
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
Protocol a 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.
V
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 and Solaris .

Virtual Local Area A logical grouping of two or more nodes which are not necessarily on the same
Network physical 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
Redundancy Protocol routers (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
multiplexing of 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
Network via 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 V200R016C60 Cold Standby & Single-Server System Software Installation and Commissioning Guide (SUSE Linux) 13 (PDF) - C

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Imanager U2000 V200R016C60 Cold Standby & Single-Server System Software Installation and Commissioning Guide (SUSE Linux) 13 (PDF) - C

Hochgeladen von

Copyright:

Verfügbare Formate

iManager U2000 Unified Network Management

Cold Standby & Single-Server

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Product Name Version

iManager U2000 V200R016C60

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 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a potentially hazardous situation

Calls attention to important information,

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

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

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. iii

> Multi-level menus are in boldface and separated by the ">"

Changes in Issue 13 (2018-08-31) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 12 (2018-06-30) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 11 (2018-04-28) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 10 (2018-02-24) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 09 (2017-12-15) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 08 (2017-11-13) Based on Product Version V200R016C60

Fixed some bugs.

Changes in Issue 07 (2017-09-27) Based on Product Version V200R016C60

l Changed the document content and name.

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. iv

Changes in Issue 06 (2017-07-28) Based on Product Version V200R016C60

Changes in Issue 05 (2017-05-25) Based on Product Version V200R016C60

Changes in Issue 04 (2017-04-15) Based on Product Version V200R016C60

Changes in Issue 03 (2017-03-10) Based on Product Version V200R016C60

Changes in Issue 02 (2017-01-26) Based on Product Version V200R016C60

Changes in Issue 01 (2016-10-31) Based on Product Version V200R016C60

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. v

About This Document.....................................................................................................................ii

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. vi

3 Installing and Commissioning the U2000 (Factory Installation of the Single-Server

4 Installing and Commissioning the U2000 (Fresh Installation).........................................184

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. vii

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. viii

A.1.5 How to manually Add a Static Route (SUSE Linux)............................................................................................. 404

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. ix

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. x

A.5.15 How to Check the U2000 Version........................................................................................................................ 551

B Uninstalling the U2000 Software........................................................................................... 590

C Manual Commissioning Task................................................................................................ 597

Issue 13 (2018-08-31) Copyright © Huawei Technologies Co., Ltd. xi

C.4.1 Overview of the FTP Service Used by the U2000..................................................................................................627