HA System (Veritas) Software Installation and Commissioning Guide (Solaris)

11/5/2014 HA System (Veritas) Software Installation and Commissioning Guide (Solaris)

http://localhost:7890/printtopics.html?time=Wed%20Nov%2005%202014%2017:20:50%20GMT+0300%20(Arab%20Standard%20Time) 1/302

HA System (Veritas) Software Installation and Commissioning Guide(Solaris)Contents

1 HA System (Veritas) Software Installation and Commissioning Guide (Solaris)1.1 Installation Overview1.1.1 Networking Structure1.1.2 Configuration Requirements1.1.3 Restrictions on Installation and Commissioning1.2 Installation and Commissioning Process1.3 Installing the U20001.3.1 Installation Preparations1.3.1.1 Collecting Installation Information1.3.1.2 Checking Required Software1.3.1.3 Checking Hardware Connections1.3.1.4 Applying for a U2000 License1.3.1.5 Applying for the Veritas License1.3.2 Configuring Controller IP Addresses1.3.2.1 Configuring Controller IP Addresses for Workstation1.3.2.1.1 Configuring the IP Address for a System Controller on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server1.3.2.1.2 Configuring the IP Address for a System Controller on an M4000/M5000 Server1.3.2.2 Configuring Controller IP Addresses for Disk Arrays1.3.2.2.1 Setting the SC IP Address for the OceanStor S3900 Disk Array1.3.2.2.2 Setting the SC IP Address for the OceanStor S2600 Disk Array1.3.2.2.3 Setting the SC IP Address for the StorageTek 2540 Disk Array1.3.3 Powering On a Server1.3.4 Installing a Solaris 10 OS Using a Quick Installation DVD1.3.5 Installing the U2000 Software1.3.5.1 Preparing Software Packages1.3.5.2 Pre-configuring the U20001.3.5.3 Starting the U2000 Installation Program1.3.5.3.1 Installing the U2000 on the GUI1.3.5.3.2 Installing the U2000 Through the CLI1.3.6 Configuring a Route1.3.7 Connecting the Primary and Secondary Sites1.3.8 Loading or Updating a License File1.3.8.1 Loading a U2000 License1.3.8.2 Updating a Veritas License1.3.9 Checking System Installation1.4 Separating the Primary Site from the Secondary Site1.5 Commissioning the U20001.5.1 Commissioning Preparation1.5.1.1 Obtaining Commissioning Parameters1.5.1.2 Checking Hardware Connections1.5.2 Performing Commissioning1.5.2.1 Powering On a Server1.5.2.2 Commissioning System Parameters1.5.2.3 Connecting the Primary and Secondary Sites1.5.2.4 Commissioning U2000 Parameters1.6 FAQs1.6.1 Solaris OS1.6.1.1 Network Configurations of the Workstation1.6.1.1.1 How to Add the Default Route1.6.1.1.2 How to Add a Static Route1.6.1.1.3 How to Query the Gateway of a Sun Workstation1.6.1.1.4 How to Check the NIC Type of a Server1.6.1.1.5 How to Check Whether an NIC Has Multiple IP Addresses on Solaris1.6.1.1.6 How to Delete Excess IP Addresses of an NIC on Solaris1.6.1.1.7 How to Set IP Addresses for Unused NICs on a Workstation1.6.1.1.8 How to Enable IPv4 Forwarding Between NICs1.6.1.1.9 How to Configure a Workstation NIC to Work in Full-Duplex Mode1.6.1.2 System Settings of the Workstation1.6.1.2.1 How to Boot Up the Workstation from the CD-ROM Drive1.6.1.2.2 How to Set the Interface Language of Solaris OS1.6.1.2.3 How to Call the GUI Management Tool in Solaris 10 OS1.6.1.2.4 How to Switch to the Multi-user Mode or Single-user Mode1.6.1.2.5 How to Open the Terminal Window on the Desktop in the Java Desk System1.6.1.2.6 How to Query the Drive of the Default Startup Disk of the Workstation1.6.1.2.7 How to Operate the CD-ROM1.6.1.2.8 How to Solve the Problem that the Current File System Is Not in the UFS Format1.6.1.2.9 How to Use the VNC to Remotely Access a Workstation1.6.1.3 FTP and Telnet Service Configuration1.6.1.3.1 How to Start/Stop the SSH Service1.6.1.3.2 How to Start/Stop the FTP, SFTP, and Telnet Services1.6.1.3.3 How to Enable and Disable the FTP/Telnet Authority of user root on Solaris OS1.6.1.4 Usage and Maintenance of Workstation



1.6.1.4.1 How to View the Versions and its patches of the Solaris OS1.6.1.4.2 How to Change the System Time and Time Zone of Solaris OS1.6.1.4.3 How to View Hardware Configurations for the Sun Workstation1.6.1.4.4 How to Check Whether the Hard Disk of the Sun Workstation Is Damaged1.6.1.4.5 How to Check the Partition of Solaris OS1.6.1.4.6 How to Check the Remaining Space of a Disk1.6.1.4.7 How to Check the IP Address and Routing Information for a Workstation1.6.1.4.8 How to View the Controller IP Addresses for the Sun Workstation1.6.1.4.9 How to Decompress Files1.6.1.4.10 How to Remotely Log In to the System as User root1.6.1.4.11 How to Access the OS from the Controller1.6.1.4.12 How to Switch Between the Console, OK Prompt, and # Prompt1.6.1.4.13 How to Use the vi Editor1.6.1.4.14 How to Use the Text Editor1.6.1.4.15 How to Forcibly End a Process1.6.1.4.16 How to Upgrade the System Controller Firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server1.6.1.4.17 How Do I Upgrade the System Controller Firmware of the T5220 Server in CLI Mode1.6.1.4.18 How to Solve the Problem Where the OS Fails to Start After the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server Is Abnormally Powered Off1.6.1.4.19 How to Solve the Problem Where the Monitor or KVM Cannot Access the GUI After the OS Is Installed on the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server1.6.1.4.20 How Do I Enable the SSH Service for the XSCF on the M4000/M5000 Server1.6.1.4.21 How to Obtain Packet Headers on Solaris1.6.1.4.22 Mappings Between Physical and Logical Network Interfaces on Server Running Solaris1.6.1.4.23 Description About Interfaces Connecting to Disk Arrays1.6.2 Veritas HA System1.6.2.1 License Management1.6.2.1.1 Applying for a Veritas License1.6.2.1.2 How to Check the Veritas License1.6.2.2 System Settings1.6.2.2.1 How to Log in and Exit the VCS (Veritas Cluster Server)1.6.2.2.2 How to Query the RVG Status1.6.2.2.3 How to Query the Rlink Status1.6.2.2.4 How to Query the VVR Status1.6.2.2.5 How to check whether the VCS service has been started1.6.2.2.6 How to Manually Start the VCS Service1.6.2.2.7 How to Manually Start the VVR1.6.2.2.8 How to Manually Stop the VCS Service1.6.2.2.9 How to Start/Stop the NMS Before Synchronizing the Primary and Secondary Sites (Solaris, PC Linux)1.6.2.2.10 How to Ensure Proper Connection of VVR Ports on Primary and Secondary Sites1.6.2.2.11 How to Change the admin User Password for Logging In to the VCS Client1.6.3 Sybase Database1.6.3.1 Startup and Shutdown of the Sybase Database1.6.3.1.1 How to Disable the Sybase Database Service1.6.3.1.2 How to Start the Sybase Database Service1.6.3.1.3 How to Verify That the Sybase Database Is Running1.6.3.2 Sybase Database Maintenance1.6.3.2.1 How to Verify That the Sybase Database Has Been Installed1.6.3.2.2 How to Check the Sybase Database Version1.6.3.2.3 How to View the Server Name of the Sybase Database1.6.3.2.4 How to Change the sa User Password for the Sybase Database If the U2000 Is Not Installed1.6.3.2.5 How to Change the sa User Password for the Sybase Database If the U2000 Is Installed1.6.3.2.6 How to View the Bit Number of the Sybase Database1.6.3.2.7 How to View the Details of the Sybase Database1.6.3.2.8 How to Change the Server Name of the Sybase Database to DBSVR1.6.3.2.9 How to Delete Redundant Database Items1.6.4 U2000 System1.6.4.1 Failure to Start Certain Processes of the U2000 Server1.6.4.2 How to Start the MSuite Client1.6.4.3 Changing the Password of the MSuite1.6.4.4 How to Check Whether the U2000 Processes of the High Availability System (Solaris, PC Linux) Are Started1.6.4.5 How to Start the U2000 Processes of the High Availability System (Solaris, PC Linux)1.6.4.6 How to End the U2000 Processes of the High Availability System (Solaris, PC Linux)1.6.4.7 How to Determine Which Types of Software Are Preinstalled1.6.4.8 Which Installation Packages Are Required for U2000 Installation1.6.4.9 How to Rectify the Application GUI Startup Failure Caused by User Switching1.6.4.10 How to View the U2000 and Sybase Database Installation Paths1.6.4.11 How to View Network Configurations for the Primary Site or Secondary Site Installed with a HA System (Solaris)1.6.4.12 How to Check Downloaded Software Packages by Using HashMyFiles Software1.6.4.13 How to Set the Communication Mode of the Server in a High Availability System (Solaris, SUSE Linux)1.6.4.14 How to Confirm the Encoding Format of the U2000 License File1.6.4.15 How to Solve the Instance Inconsistency Problem During Connection Between the Primary and Secondary Sites in a Solaris High Availability System1.6.4.16 How to Change the OS User Password1.6.4.17 How to Restore the OSSENGR and OSSICMR Directories Which Are Misoperated (Solaris/SUSE Linux)1.6.4.18 How to Use the FileZilla to Transfer Files by SFTP1.6.4.19 How to Transfer Files by Means of FTP1.6.4.20 How to Check and Change an OS User ID1.6.4.21 How to Deal with an Automatically Configured Temporary IP Address1.6.4.22 How to Burn the ISO File to DVD1.6.4.23 How to Address the Failure to Download JNLP Files After the Download File Option Is Clicked on the Address Bar of the Internet Explorer Browser1.6.5 Install the U2000 Software Exception Processing1.6.5.1 How to Address an OS Installation Failure Caused by Incorrect Hard Disk Format



1.6.5.2 How to Rectify the OS Installation Failure that Occurs Because a Hard Disk Is Not Labeled1.6.5.3 How to Solve the Problem Where the Amount of Remaining Data Keeps 99% During Data Synchronization in a High Availability System1.6.5.4 How do I solve the problem where a failure message is displayed during the installation or the installation is abnormally interrupted1.6.5.5 How to Handle Messages Indicating That the Port Is Occupied During Installation or Uninstall1.6.5.6 How to Rectify the Failure to Connect to the Sybase Database During U2000 Installation1.6.5.7 Failure to Log In to the U2000 Server from a U2000 Client1.6.5.8 How to Resolve the Problem that the License Does Not Take Effect1.6.5.9 How to Solve Common Problems About Using the Network Mode to Installing a U2000 Client1.6.5.10 How to Rectify the Failure to Open the CAU Download Web Page Because the Port Is Used1.6.5.11 How to Address the Problem Where the Sapce of the OS Patch Directory tmp Is Insufficient1.7 Uninstalling the U2000 Software1.7.1 Uninstall Preparations1.7.2 Uninstalling U2000 Software1.7.3 Verifying the Uninstall Status of the Server Software1.8 Manual Commissioning Task1.8.1 Configuring a Digital Certificate1.8.1.1 Deploying the SSL Trust Certificate on the Internet Explorer1.8.2 Setting Hardware Alarm Monitoring1.8.2.1 Setting Servers for Monitoring (M4000/M5000)1.8.2.2 Configuring the Monitoring Function for an S2600 Disk Array1.8.2.3 Configuring the Monitoring Function for an S3900 Disk Array1.9 Starting the U2000 Server in a Solaris High Availability System1.9.1 Powering On the Server Safely1.9.2 Starting the Database1.9.3 Starting the U2000 Server Processes1.10 Shutting Down the U2000 Server in a High Availability System (Solaris)1.10.1 Stopping the U2000 Server Processes1.10.2 Shutting Down the Database1.10.3 Stopping the VCS Service1.10.4 Power Off the Server Safely1.11 Getting Started1.12 Manually Installing the Solaris OS and Its Patches1.12.1 Installing the OS Through the GUI1.12.2 Installing the OS Through the CLI1.12.3 Installing the Solaris OS Patches1.13 Planning Disk Partitions1.14 Configuring Disk Arrays1.14.1 Configuring the OceanStor S2600 Disk Array by Using the ISM1.14.2 Configuring the OceanStor S3900 Disk Array by Using the ISM1.14.3 Configuring the StorageTek 2540 Disk Array Through the Web Browser1.14.4 Configuring the OceanStor S3100 Disk Array1.14.4.1 Configuring the SC IP Address of the OceanStor S3100 Disk Array1.14.4.2 Using the Manager Suite to Configure the OceanStor S3100 Disk Array1.15 Glossary and Abbreviations

1 HA System (Veritas) Software Installation and Commissioning Guide(Solaris)

This document describes how to install the U2000 High Availability System (Veritas) on Soalris and obtain the reference information required during theinstallation.

Installation OverviewBefore installing and commissioning the U2000, you must get an understanding of the software and hardware configuration requirements andnetworking requirements of the U2000 as well as the restrictions on installing and commissioning the U2000.

Installation and Commissioning ProcessThis topic describes the processes for installing and commissioning the High Availability System (Solaris) as well the time required for every operation.

Installing the U2000This topic describes how to obtain the required reference information about U2000 installation and how to install the U2000. If the U2000 has beenpreinstalled, skip this topic and directly commission the U2000. For details about how to commission the U2000, see Commissioning the U2000.

Separating the Primary Site from the Secondary SiteThis topic describes how to separate the primary site from the secondary site. Separating the primary site from the secondary site refers to disconnectingthe primary site and the secondary site.

Commissioning the U2000This topic describes how to commission the U2000. Usually, the server delivered by Huawei has been preinstalled, the primary and secondary sites havebeen separated, and you do not need to reinstall the U2000 on the server. You can directly commission the U2000 and modify the system and U2000parameters according to on-site requirements to allow for the normal use of the U2000.If the server has not been preinstalled by Huawei, install theU2000 and commission the system. To allow the U2000 to manage the network, you must commission the U2000 before using the U2000 to manageNEs and configuring services.

FAQsThis topic provides answers to the most frequent questions concerning the installation.



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

Manual Commissioning TaskSome commissioning tasks need to be manually executed during U2000 system parameter commissioning. This topic describes how to execute a manualcommissioning task.

Starting the U2000 Server in a Solaris High Availability SystemThe U2000 server can be started in three steps: power on the server safely, start the database, and start the U2000 server processes.

Shutting Down the U2000 Server in a High Availability System (Solaris)Four steps are required to shut down the U2000 server in a high availability system (Solaris): stop the U2000 server processes, shut down the database,stop the VCS service, and power off the server safely.

Getting StartedThis topic describes certain common operations that can be performed on the Solaris workstation. After learning this topic, you can improve theefficiency of the operations on the Solaris OS.

Manually Installing the Solaris OS and Its PatchesThis topic describes how to manually install the OS by using the Solaris installation DVD delivered with the product and how to install patches by usingthe patch package.

Planning Disk PartitionsThis topic describes the disk partitioning scheme that is determined according to the sizes and quantities of the server hard disks.

Configuring Disk ArraysThis topic describes how to configure the OceanStor S3900, OceanStor S2600, OceanStor S3100, and StorageTek 2540 disk arrays.

Glossary and Abbreviations

Parent topic: Installation and Commissioning

1.1 Installation OverviewBefore installing and commissioning the U2000, you must get an understanding of the software and hardware configuration requirements and networkingrequirements of the U2000 as well as the restrictions on installing and commissioning the U2000.

Networking StructureThis topic describes the solutions that the U2000 supports as well as the networking of the High Availability System (Solaris) solution.

Configuration RequirementsThis topic describes hardware and software requirements for the high availability system (Solaris).

Restrictions on Installation and CommissioningYou must learn about the restrictions of the U2000 during the U2000 installation and commissioning.

Parent topic: HA System (Veritas) Software Installation and Commissioning Guide (Solaris)

1.1.1 Networking StructureThis topic describes the solutions that the U2000 supports as well as the networking of the High Availability System (Solaris) solution.

The solutions can be classified into the following types based on OS type of the U2000 and whether the U2000 supports a high availability system.

Single-Server System (Windows)

Single-Server System (Solaris)

Single-Server System (SUSE Linux)

Single-Server System (VMware, PC Server)

High Availability System (Solaris)

Local SUSE Linux High Availability System (SUSE Linux, PC server)

Remote SUSE Linux High Availability System (SUSE Linux, PC server)

This manual describes the installation and commissioning of the High Availability System (Solaris). Figure 1 shows the networking of the High AvailabilitySystem (Solaris).

Figure 1 Network diagram for a High Availability System (Solaris)



Terms

To ensure the U2000 install successfully, definitions for terms as used in this document before introducing the U2000 scheme:

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 tohardware when used in reference to a computer where a server program runs.

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 serverapplication or on a separate computer. The term refers to hardware when used in reference to the computer where a client application runs.

Workstation and host: A workstation functions the same as a host. Generally, a workstation or host refers to the computer where services run in aSolaris OS.

Primary (Secondary) site: Used for the high availability system, the primary (secondary) site refers to the physical primary (secondary) site. Whethera 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. Inmost 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.

Active (Standby) site: It is used for the high availability system. The active (standby) site refers to the site in the active (standby) state. The site in thestandby state protects the site in the active state.

Active (Standby) state: It is used for the high availability system. The active (standby) state refers to the working (protection) state. For example, if allthe relevant applications on a site run normally, this site is in the active state.

Networking Description:

The following describes the deployment of the U2000 server, U2000 client, switch, router, disk array, and gateway NEs, as well as the communicationrelationships.

The U2000 client communicates with the server using a DCN(Data Communication Network).

NEs and the OSS communicate using a DCN.

The disk array stores data to improve database performance. The server must be configured with a disk array if the U2000 manages a moderateamount of network elements (NEs).

Parent topic: Installation Overview

1.1.2 Configuration RequirementsThis topic describes hardware and software requirements for the high availability system (Solaris).

Requirements for Hardware Configuration

The high availability system (Solaris) is deployed on the Solaris platform and requires hardware configurations listed in the Table 1, Table 2 shows therequirements for disk array configurations.

Table 1 Configuration requirements on the hardware for the U2000 serverNetwork Scale Oracle Server (Solaris-Supported)

Small-scale network: less than 2000 equivalentNEs

Netra SPARC T4-1CPU: 1 CPU (4-core) x 2.85 GHz or aboveMemory: 32 GB or aboveHard disk: 4 x 600 GB or above

Medium-scale network: 2000-6000 equivalentNEs

Netra SPARC T4-1CPU: 1 CPU (4-core) x 2.85 GHz or aboveMemory: 32 GB or aboveHard disk: 4 x 600 GB or above

Oracle SPARC T4-1



CPU: 1 CPU (8-core) x 2.85 GHz or aboveMemory: 64 GB or aboveHard disk: 2 x 600 GB or above

Large-scale network: 6000-15000 equivalent NEs Oracle SPARC T4-1CPU: 1 CPU (8-core) x 2.85 GHz or aboveMemory: 64 GB or aboveHard disk: 2 x 600 GB or abovedisk array

Super-large-scale network: 15000-20000equivalent NEs

Oracle SPARC T4-2CPU: 2 CPU (8-core) x 2.85 GHz or aboveMemory: 128 GB or aboveHard disk: 2 x 600 GB or abovedisk array

Table 2 Recommended configurations of the disk arrayHardware Configuration Item Disk Array Hardware Version Capacity

Delivered software platform: OceanStorS3900

NOTE:An M200 controller enclosure is deliveredwith disk arrays.

V100R002C00 16 GB memory, 12 x 600 GB

NOTE:

The preceding table shows the recommended delivery configuration. The compatible configuration varies according to managed NEs and network size. For details, see chapterManagement Capabilities of the U2000 on Different Hardware Platforms in the U2000 Planning Guide.

U2000 installation, deployment, or running may fail on incompatible servers or servers with non-recommended configurations.

If the configured disk array does not conform to the preceding standard configuration, contact Huawei engineers to check whether such disk arrays are applicable to the highavailability system (Solaris).

If the core network component needs to be installed, the U2000 must be equipped with the disk array.

Requirements for Software Configuration

The Table 3 lists the software configuration requirements for the high availability system (Solaris).

Table 3 Configuration requirements on the server softwareSoftware Description

OS Solaris 10 (8/11)+Patch 20.0.0

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 requiredversion is recommended to ensure that the U2000 runs properly.

Veritas software Veritas 6.0.1 + 6.0.3.100

Database SYBASE 15.5 with EBF21258+ESD#5.3

NMS software U2000 software


1.1.3 Restrictions on Installation and CommissioningYou must learn about the restrictions of the U2000 during the U2000 installation and commissioning.

Read carefully the following restrictions before installation and commissioning:

To prevent program conflict, it is recommended that other unnecessary software not be installed on the U2000 server.

Only one U2000 can be installed on a server.

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.

A virtual machine supports the installation only of a single-server U2000 running on the SUSE Linux OS. The U2000 using other solutions cannot beinstalled on the virtual machine.




1.2 Installation and Commissioning ProcessThis topic describes the processes for installing and commissioning the High Availability System (Solaris) as well the time required for every operation.

NOTE:If this is the first time you perform operations on the Solaris OS or you are not familiar with the Solaris OS, see Getting Started to get an overall understanding of the basic operations on theSolaris OS.

Usually, the server delivered by Huawei has been preinstalled and you do not need to reinstall the U2000 on the server. You can directly commission theU2000 and modify the system and U2000 parameters according to on-site requirements to allow for the normal use of the U2000.If the server has not been preinstalled by Huawei, install the U2000 and commission the system. A series of parameters need to be modified duringcommissioning. You must ensure that on-site parameters have been planned based on the U2000 Planning Guide before commissioning is performed. Figure 1shows the installation commissioning process.

Figure 1 Installation and commissioning flowchart for the High Availability System (Solaris)

NOTE:The installation time varies according to the server model and installation components.


1.3 Installing the U2000This topic describes how to obtain the required reference information about U2000 installation and how to install the U2000. If the U2000 has beenpreinstalled, skip this topic and directly commission the U2000. For details about how to commission the U2000, see Commissioning the U2000.

Installation PreparationsThis topic describes how to prepare for installation. Before you install a high availability system (Veritas hot standby), ensure that the preparations for



the software, hardware, and environment are ready.

Configuring Controller IP AddressesController IP addresses are used to manage and maintain servers remotely. Configure controller IP addresses for servers before installing the operatingsystem (OS).

Powering On a ServerThis topic describes how to power on a server. The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server, M4000/M5000 server, and disk array are used asexamples to explain how to power on a server based on the server type and disk array type.

Installing a Solaris 10 OS Using a Quick Installation DVDThis topic describes how to install a Solaris 10 OS for the primary and secondary sites using a quick installation DVD.

Installing the U2000 SoftwareThis topic describes how to install the U2000 software on the primary and secondary sites. You must start the U2000 installation program after theU2000 is preconfigured using a DVD or software package.

Configuring a RouteThis topic describes how to use the MSuite to configure a route. Before connecting the primary and secondary sites, you must ensure that the heartbeatand replication routes between the primary and secondary sites are reachable.

Connecting the Primary and Secondary SitesThis topic describes how to connect the primary and secondary sites using the MSuite. After the U2000 is installed on the primary and secondary sites,you must connect the primary and secondary sites to establish a high availability system.

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

Checking System InstallationThis topic describes how to check the installation of a high availability system (Solaris).


1.3.1 Installation PreparationsThis topic describes how to prepare for installation. Before you install a high availability system (Veritas hot standby), ensure that the preparations for thesoftware, hardware, and environment are ready.

Collecting Installation InformationThis topic describes how to collect installation information. Before installing the high availability system (Solaris), collect required information,including the host name, IP address, route, time zone and time, user password, and disk partition.

Checking Required SoftwareThis topic describes the software required to be checked. Ensure that the required software is on-hand and meets the installation requirements beforeinstalling the U2000.

Checking Hardware ConnectionsThis topic describes how to check hardware installation and cable connections before installing a U2000. If hardware is improperly installed or cable isimproperly connected, unexpected error may occur during installation of the U2000.

Applying for a U2000 LicenseThe 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 tothe U2000 client, but can log in to the System Monitor client and the MSuite.

Applying for the Veritas LicenseThis topic describes how to apply for a formal Veritas license. The Veritas license used in NMS installation is a demo license. After the server isdelivered to the installation site, the demo license must be replaced with a formal Veritas license in time.

Parent topic: Installing the U2000

1.3.1.1 Collecting Installation InformationThis topic describes how to collect installation information. Before installing the high availability system (Solaris), collect required information, including thehost name, IP address, route, time zone and time, user password, and disk partition.

Complete planning for the information listed in the following tables according to the U2000 Planning Guide.

NOTE:Print the following tables and fill in the blanks with the site-specific planning information.

Examples provided in the tables are the default values of servers that come pre-installed with software from Huawei.

Host Name Planning



NOTICE:

To ensure that the NMS can run properly, host name planning must comply with the following rules and restrictions:

The host name of the U2000 server must be unique on the network.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 (-).The first character must be a letter and the last character cannot be a hyphen.The host name cannot contain --.The host name must be case-sensitive.The host name cannot be empty or contain spaces.The host name cannot contain only one character.The host name cannot be any of the following keywords in the high availability system.action false keylist static after firm local stop requires remoteclustersystem group resource global Start str temp set heartbeat ArgListValuesSystem Group boolean hard Name soft before online condition MonitorOnlyremote start cluster event VCShm type Path offline Signaled HostMonitorProbed state Cluster IState int Type State VCShmg NameRule ConfidenceLevel

Table 1 Host name listSite Item Example Plan

Primary Site Host name Primaster

Secondary Site Host name Secmaster

IP Address Planning

If the high availability (HA) system is installed in the Solaris OS, you need to plan the following types of IP addresses:

IP address for the workstation controller: This IP address can be used to remotely log in to a workstation to manage and maintain workstationhardware. For example, you can use this IP address for remote OS installation, or use it to maintain the workstation if the OS fails to start properly.

IP address for the disk array controller: This IP address is used to remotely manage and maintain disk 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.

IP address of the heartbeat network service: This type of IP address is used to detect status of the network connection between the primary andsecondary sites.

IP address of the replication network service: This type of IP address is used to replicate data between Primary and secondary sites.

NMS application IP address: This IP address is used for external NMS services such as communication between the NMS server and clients orbetween the NMS server and NEs.

IPMP is short for IP network multipathing. In this mode, two NICs work in 1+1 backup mode. During configuration, an IP address is assigned to eachof the NICs and a floating IP address is also set. When the active NIC is faulty, services can be switched to the standby NIC. Configuring IPMPrequires two NICs and three IP addresses, and the three IP addresses must be on the same network segment.

NOTE:During the network planning:

The heartbeat network, replication network, and NMS application network can be planned separately or in reuse mode. Planning the heartbeat network, replication network, andNMS application network separately is not recommended.The heartbeat network, replication network, and NMS application network can be configured with network protection, that is, IPMP. It is not recommended that IPMP beconfigured.

NOTICE:To ensure that the NMS can run properly, IP addresses planning must comply with the following rules and restrictions:

The IP addresses must be unique on the network.The servers communicate with the managed equipment in the normal state.The U2000 servers communicate with U2000 clients in the normal state.If the server has multiple NICs and IP Network Multipathing (IPMP) is not configured, IP addresses of these NICs cannot be on the same networksegment.You can plan only one IP address for one network interface. It is not allowed to plan or set multiple IP addresses for the same network interface.It is not allowed to plan or set multiple default router for the U2000 server.You need to plan the equipment controller IP address according to the selected NMS server hardware.You need to plan the NMS IP address according to the deployment scheme of the NMS.

In a high availability system, the bandwidth between the primary and secondary sites directly affects data consistency between the primary and secondary sitesas well as the normal running of the system.If the bandwidth does not meet requirements for a high availability system, the following problems may occur: The SRL volume accumulates a lot of datawhen performs involving a great amount of data are performed, for example, synchronizing or uploading NE data and browsing E2E paths. After the SRLoverflows, data replication between the primary and secondary sites is interrupted and the protection function of the high availability system becomesunavailable. When an error occurs on the high availability system at the primary site, U2000 applications will not be automatically switched to the secondarysite.For bandwidth planning details, see chapter Bandwidth Planning of the Primary and Secondary Sites in the HA System in the U2000 Planning Guide.



NOTE:The IP address used after preinstallation is the same as that in the example. After the disk array is preinstalled, only the IP address of the primary controller needs to be configured. You canchoose to configure the IP address of the secondary controller as required.

According to the number of required NICs, function types of configured IP addresses, and whether IPMP is configured, multiple IP address planning schemesare available for the HA system (Solaris). The typical IP address planning schemes are as follows.

NOTE:In the HA system, the primary and secondary sites can be deployed either in the same place (local deployment) or in different cities (remote deployment). The following uses localdeployment as an example to describe IP address planning. If remote deployment is required, ensure that routes between the primary and secondary sites are reachable, the bandwidth ofcommunication between the primary and secondary sites meet the requirement, and the network is stable.

Single-NIC Scheme

Single-NIC scheme: Figure 1 shows the networking diagram. The single-NIC scheme is recommended.

Figure 1 Networking example (single-NIC scheme)

IP planning description: Only the System IP address needs to be planned. Heartbeat detection, data replication, and external NMS services betweenprimary and secondary sites are all implemented through NIC 1.

Advantage: The networking is simple and IP addresses can be saved.

Disadvantage: All data is transmitted over one link and faults cannot be isolated.

IP planning example: Table 2 shows the planning example.

Table 2 Example of IP address planning of the single-NIC schemeSite Item Example (IP Address/Subnet Mask/Gateway) Description

Primary site IP address for theworkstation controller

Netra T4-1/Oracle T4-1/Oracle T4-2/T5220workstation: 10.9.1.20/255.255.255.0/10.9.1.254

Planned according to the workstation model.The M4000 has two control interfaces. IP addresses ofthe control interfaces must be on different networksegments. You can use only one control interface tomanage the workstation. If only one control interface isused, plan an IP address for one control interface.

M4000/M5000 workstation:Controller 1:10.9.1.21/255.255.255.0/10.9.1.254Controller 2:10.9.2.21/255.255.255.0/10.9.2.254

IP address for the diskarray controller

OceanStor S2600/S3900:Primary controller:10.9.1.22/255.255.255.0/10.9.1.254Secondary controller:10.9.1.23/255.255.255.0/10.9.1.254

-

System IP address 10.9.1.1/255.255.255.0/10.9.1.254 T5220 Network interface:e1000g0Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Networkinterface:igb0M4000/M5000 Network interface:bge0

Secondarysite

IP address for theworkstation controller






-

System IP address 10.9.1.2/255.255.255.0/10.9.1.254 T5220 Network interface:e1000g0



Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Networkinterface:igb0M4000/M5000 Network interface:bge0

Double-NIC Scheme (Without IPMP)

Double-NIC scheme (without IPMP): Two NICs are required. Figure 2 shows the networking diagram.

Figure 2 Networking example (double-NIC scheme (without IPMP))

IP planning description: Only the System IP address and IP address of the heartbeat network service need to be planned.

OS management and NMS application are implemented through NIC 1.

Heartbeat services and data replication services between primary and secondary sites are implemented through NIC 2, with the replication IPaddress the same as the heartbeat IP address.

NOTE:It is recommended that IP addresses of NIC 1 and NIC 2 are on different network segments.

Advantage: NMS management and HA system application are implemented through different routes, and thus faults can be isolated.

Disadvantage: Configurations are complex.


Table 3 Example of IP address planning of the double-NIC scheme (without IPMP)Site Item Example (IP Address/Subnet Mask/Gateway) Description







-


IP address of theheartbeat networkservice

10.9.2.3/255.255.255.0/10.9.2.254 T5220 Network interface: e1000g1Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Networkinterface: igb1M4000/M5000 Network interface: bge1

Secondarysite





IP address for the disk OceanStor S2600/S3900: -





-


IP address of theheartbeat networkservice


Double-NIC Scheme (with IPMP)

Double-NIC scheme (with IPMP): Two NICs are required. Figure 3 shows the networking diagram.

Figure 3 Networking example (double-NIC scheme (with IPMP))

IP planning description: The System IP address, IP address of the active heartbeat NIC, and IP address of the standby heartbeat NIC need to beplanned.

NIC 1 and NIC 2 work in 1+1 backup mode.

The system IP address is a floating IP address. If the NICs are running properly, the System IP address maps to the IP address of the activeheartbeat NIC. Heartbeat detection, data replication, and external NMS services between primary and secondary sites are all implementedthrough the System IP address. If the active NIC is faulty, the System IP address automatically maps to the IP address of the standbyheartbeat NIC. Heartbeat detection, data replication, and external NMS services between primary and secondary sites are still implementedthrough the System IP address, thereby implementing NIC protection.

NOTICE:The System IP address, IP address of the active heartbeat NIC, and IP address of the standby heartbeat NIC must be on the same network segment.

Advantage: The NICs work in 1+1 backup mode and network security is high.

Disadvantage: The networking is complicated and many IP addresses are required. Future maintenance is complex and switch performancemust be high.


Table 4 Example of IP address planning of the two-NIC scheme (with IPMP)Site Item Example (IP Address/Subnet Mask/Gateway) Description







-

System IP address 10.9.1.1/255.255.255.0/10.9.1.254 -



IP address of the activeheartbeat NIC

10.9.1.2/255.255.255.0/10.9.1.254 T5220 Network interface:e1000g0Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Networkinterface:igb0M4000/M5000 Network interface:bge0

IP address of the standbyheartbeat NIC


Secondarysite







-

System IP address 10.9.1.4/255.255.255.0/10.9.1.254 -

IP address of the activeheartbeat NIC

10.9.1.5/255.255.255.0/10.9.1.254 T5220 Network interface:e1000g0Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Networkinterface:igb0M4000/M5000 Network interface:bge0

IP address of the standbyheartbeat NIC


Other SchemesContact Huawei engineers for scheme design.

Route Planning

Table 5 Route listItem Example Plan

Routing network segment 1 10.9.10.0/255.255.255.0

Routing network segment 2 10.71.6.0/255.255.255.0

... ...

Routing network segment N 10.121.124.0/255.255.255.0

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

Time Zone and Time Planning

Table 6 Time zone and time listItem Example Plan

Time zone PRC

Time 14:00

User Name and Password Planning

NOTICE:The passwords are examples only. Change the passwords after completing the installation. The default password indicates the initial password used when theU2000 is installed for the first time. Production preinstallation indicates the U2000 software has been installed initially.

NOTE:This manual describes only the disk array users used during the U2000 installation. To obtain information about more disk array users, parameters, and operations, see the product manual of



the specific disk array.

Table 7 User and password listUser Default Password Password Set After Preinstallation Planned Password

Netra T4-1/Oracle T4-1/Oracle T4-2/T5220controller (ILOM) user root

changeme Changeme_123

M4000/M5000 controller(XSCF) monitoring user eis-installer

None

NOTE:The password is configured during creation of theeis-installer user.

Changeme_123

OceanStor S2600 user admin 123456 Changeme_123

OceanStor S3900 user admin Admin@storage Changeme_123

OS user root Changeme_123 Changeme_123

OS user ossuser Changeme_123 Changeme_123

OS user dbuser Changeme_123

NOTE:You must change the default password duringfirst-time login.

Changeme_123

Database user sa Changeme_123 Changeme_123

NMS Database user dbuser None.

NOTE:The dbuser user does not have a defaultpassword. The password of the dbuser user mustbe configured during U2000 installation.

Changeme_123

U2000 user admin Changeme_123

NOTE:You must change the default password duringfirst-time login.

Admin_123

network management systemmaintenance suite user admin

Changeme_123 Changeme_123

VCS Client User admin Changeme_123 Changeme_123The admin user password for the VCS clientmust meet the following requirements:

Consists of 8 to 30 characters.Contains at least two types of thefollowing characters:

At least one lower-caseletterAt least one upper-caseletterAt least one digitAt least one specialcharacter ~!@#$%^&*()-_=+\|[{}];:'",<.>/? anda space

Cannot be the same as the username or the mirror writing of theuser name.

Disk Partition SchemeIf a quick installation DVD is used to install an OS, the installation software automatically partitions disks according to the disk size. Before manually installan OS, determine the disk partitioning scheme. For details about disk partitioning planning, see Planning Disk Partitions.

Parent topic: Installation Preparations

1.3.1.2 Checking Required SoftwareThis topic describes the software required to be checked. Ensure that the required software is on-hand and meets the installation requirements before installingthe U2000.



Installation engineers can install the U2000 in either of the following ways:

Using software packages: Required software packages must be on-hand. Only Huawei engineers have the permissions to download softwarepackages. If the installation using software packages is required, contact Huawei engineers to obtain software packages.

Using DVDs: Required DVDs must be on-hand. The DVDs are delivered along with the product.

Using Software PackagesBefore installing the U2000, ensure that the Solaris OS installation DVD and software packages are available.

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) fileis stored in the same path as software packages.

Do as follows:

1. Access http://support.huawei.com and choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManagerU2000 > iManager U2000 > iManager U2000 V200R001.

2. Select the version to be installed.

3. Download required software packages listed in Table 1. It is recommended that installation engineers use the download tool (for example, NetAnts).If they use Windows Internet Explorer, some software packages may be renamed automatically after being downloaded to the local computer. In thiscase, change the software package names to the same as those on the http://support.huawei.com.

4. Use the HashMyFiles to verify correctness of the software packages. For details, see How to Check Downloaded Software Packages by UsingHashMyFiles Software.

5. http://support.huawei.com can store files with a maximum size of 1.8 GB. The file with the size larger than 1.8 GB will be separated into differentsoftware 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 ReadMe 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 sitehttp://downloads.sourceforge.net/sevenzip and install the tool.For more information about software operation, see the software Help or go to the official website of the software for technical support.

NOTE:

The Solaris OS can be installed only by using DVDs. Therefore, if you install the U2000 by using software packages, ensure that the Solaris OS installation DVD is available.In an installation DVD or installation package, version indicates the detailed version number of the software.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 theVerify data on disc after burning check box. For details, see How to Burn the ISO File to DVD.

Table 1 Software package listSoftware Medium Name Description

Security hardeningpackage

Installation package:U2000version_VPPSetsolarisV300R003C20SPC100.tar

It must be available.It is used to enhance the security of Solaris system.

Solaris OS installationDVD

You can install the Solaris 10 OS by using the quick installation DVD isrecommended. Quick installation DVD:

Ensure that the quick installation DVDU2000version_server_os_solaris_SPARC_U10_sun4v_dvd2 isavailable if the hardware type of the selected server is sun4v(the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server forexample).Ensure that the quick installation DVDU2000version_server_os_solaris_SPARC_U10_sun4u_dvd1 isavailable if the hardware of the selected server is sun4u (theM4000/M5000 server for example).

NOTE:If the server has been configured with an OS, log in to the OS as the root user andrun the uname -m command to view the hardware type of the server.

It must be available.It is used to install Solaris OS.

Database softwarepackage

Installation package: U2000version_server_db_solaris_SPARC.tar It must be available. It is used to install the database.

Veritas softwarepackage

Make the following software available:1. Veritas software installation package:

U2000version_veritas6.0.1_solaris.tar.gz2. Veritas patch package:

U2000version_server_veritas603100_patch_solaris_SPARC.tar

It must be available. It is used to install the Veritas.

U2000 server softwarepackage

Basic component: U2000version_server_nmsbase_solaris_SPARC.tar It must be available. It is used to install the U2000.

Core component: U2000version_server_nmscore_solaris_SPARC.tar It must be available. It is used to install the U2000.

Transport component: U2000version_server_nmstrans_solaris_SPARC.tar It is required only if the U2000 needs to manage Huaweitransport equipment. Huawei transport equipment includes:

MSTP equipment



WDM equipmentNA WDM equipmentSubmarine equipmentRTN equipmentPTN equipment

NOTE:Software packages for the transport and IP components must beavailable so as to manage PTN 6900 series NEs.

IP component: U2000version_server_nmsip_solaris_SPARC.tar It is required only if the U2000 needs to manage Huawei IPequipment. Huawei IP equipment includes:

ATN Series EquipmentRoutersSwitchesMetro service equipmentBroadband access equipmentVoIP gatewaysFirewallsService inspection gatewaySVN equipmentInternet Cache System

Access component: U2000version_server_nmsaccess_solaris_SPARC.tar It is required only if the U2000 needs to manage Huawei accessequipment. Huawei access equipment includes:

FTTx equipmentMSAN equipmentDSLAM equipmentBITS equipment

CMC component: U2000version_server_nmscmc_solaris_SPARC.tar It is required only if the U2000 needs to manage Huawei CMCequipment.

OS patch softwarepackage

OS patch software package:U2000version_server_ospatch_solaris_SPARC.tar

Select this software package when installing the OS patch orconfiguring the StorageTek 2540 disk array.

ESN tool ESN tool: U2000version_ESN_solaris_SPARC.tar The ESN tool is required only when you apply for the U2000License 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 U2000installation path. Therefore, to apply for the U2000 license after the U2000is installed, use the ESN tool in this path directly.

Using DVDs

Ensure that the following DVDs are on-hand before installing the U2000 by using DVDs.

NOTE:The disk label delivered with the server is 1/5 if the mantissa of the disk name is dvd1; the disk label delivered with the server is 2/5 if the mantissa of the disk name is dvd2, and so on.

Table 2 DVD listSoftware DVD Name

Solaris OS installation DVD You can install the Solaris 10 OS by using the quick installation DVD is recommended. Quick installation DVD:Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4v_dvd2 is available ifthe hardware type of the selected server is sun4v (the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server forexample).Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4u_dvd1 is available ifthe hardware of the selected server is sun4u (the M4000/M5000 server for example).

NOTE:If the server has been configured with an OS, log in to the OS as the root user and run the uname -m command to view the hardware typeof the server.

Database software DVD U2000version_server_db_solaris_SPARC_dvd4

Veritas software DVD 1. Veritas software installation DVD: Solaris_Veritas6.0.12. Veritas patch installation DVD: U2000version_server_patch_solaris_SPARC_dvd3

U2000 server software U2000version_server_nms_solaris_SPARC_dvd5

NOTE:U2000 server software include SetSolaris software package, it is used to enhance the security of Solaris system.

OS patch software package (Optional. U2000version_server_patch_solaris_SPARC_dvd3



Select this software package wheninstalling the OS patch or configuring theStorageTek 2540 disk array.)

ESN tool U2000version_ESN_solaris_SPARC.tarThe 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 theU2000 installation path. Therefore, to apply for the U2000 license after the U2000 is installed, use the ESN tool in this path directly.

Obtaining ToolsTable 3 shows the tools required to be available before the U2000 is installed.

Table 3 Tool listNo. Tool Usage Description

1 PuTTY The software usescommands (telnet andSSH) to log in to theserver.

Refer to http://www.putty.org to download the latest version.For more information about software operation,see the software Help or go to the official website of the software for technical support.

2 FileZilla tool The FileZilla is used totransfer files by SFTP.

You can go to http://filezilla-project.org to download the latest version of FileZilla. For more informationabout software operation, see the software Help or go to the official website of the software for technicalsupport.

3 7-zip tool For extracting files. Refer to http://downloads.sourceforge.net/sevenzip to download the latest version.For more information about software operation, see the software Help or go to the official website of thesoftware for technical support.

4 HashMyFiles tool Download softwarecompression packageused to verify thecorrectness.

Refer to http://www.nirsoft.net to download the latest version.For more information about software operation, see the software Help or go to the official website of thesoftware for technical support.

5 ESN tool The tool is used toquery ESNs. ESNs areused to apply for U2000licenses.

The ESN tool name is U2000version_ESN_solaris_SPARC.tar.The tool is delivered with the U2000. Go to http://support.huawei.com to download the tool. Accesshttp://support.huawei.com and choose Software Center > Version Software > Network OSS&Service >iManager U2000 > iManager U2000 > iManager U2000 > iManager U2000 V200R001, select the versionto be installed.

NOTE:The tool is a software package. It will not be delivered as a DVD-ROM. After the U2000 is installed, the ESN tool isavailable in the U2000 installation path. Therefore, to apply for the U2000 license after the U2000 is installed, use theESN tool in this path directly.


1.3.1.3 Checking Hardware ConnectionsThis topic describes how to check hardware installation and cable connections before installing a U2000. If hardware is improperly installed or cable isimproperly connected, unexpected error may occur during installation of the U2000.

Prerequisites

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

Procedure

1. Ensure that the power cables and ground wires for all components are tightly connected and in good contact and that the polarities are properlyplaced.

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, seeU2000 Hardware Installation Guide (Huawei N610E cabinet).

2. Ensure that all cables are bundled and free of visible damage.

3. Check hardware connections and network cable connections according to the hardware connection diagram.

NOTE:Configuring disk arrays is optional.

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 thenetwork, the U2000 fails to synchronize network configurations or be started. Configuring the system IP address for the network interface with the smallest interfaceserial number is preferred. For example, network interface bge0 with the serial number of 0 can be used for the M5000 server.



The following hardware connection diagrams are based on a single-NIC network configuration scheme. For details about a single-NIC network configuration scheme,see Collecting Installation Information. The hardware connections based on other network configuration schemes are similar.

The following figure shows the hardware connection of the Netra T4-1 server.

Figure 1 Hardware connection for the Netra T4-1 server that is not connected to disk arrays

Figure 2 Hardware connection for the Netra T4-1 server that is connected to the OceanStor S3900

NOTE:If you need to connect Netra T4-1server to a disk array, you need to prepare HBA cards.

The following figure shows the hardware connection of the Oracle T4-1 server.

Figure 3 Hardware connection for the Oracle T4-1 server that is not connected to disk arrays

Figure 4 Hardware connection for the Oracle T4-1 server that is connected to the OceanStor S3900






The following figure shows the hardware connection of the T5220 server.

NOTE:If you need to connect T5220 server to a disk array, you need to prepare HBA cards.

Figure 7 Hardware connection for the T5220 server that is not connected to disk arrays



Figure 8 Hardware connection for the T5220 server that is connected to the OceanStor S2600


Figure 10 Hardware connection for the T5220 server that is connected to the StorageTek 2540



The following figure shows the hardware connection of the M4000 server.

Figure 11 Hardware connection for the M4000 server that is not connected to disk arrays

Figure 12 Hardware connection for the M4000 server that is connected to the OceanStor S2600




Figure 14 Hardware connection for the M4000 server that is connected to the StorageTek 2540










4. Check the plugs and sockets.

a. Ensure that the latches of cable plugs are locked fast.

b. Ensure that the pins in each socket are complete and in good order. Curved pins may cause short circuits.

5. Ensure that the connections between the server and disk arrays and between switches and routers are correct.

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.


1.3.1.4 Applying for a U2000 License



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

Context

The license file is not delivered to customers along with the U2000 installation DVD. Contact Huawei engineers to apply for the licenses according tothe contract number and the equipment serial numbers (ESNs) of the oss server.

To prevent the failure in finding the license file for possible U2000 reinstallation, save the license application email and the license file properly.

Before using the U2000, apply for a formal U2000 license (recommended) or a temporary U2000 license. The application of a U2000 license takes along time. Therefore, apply for it in advance.

An ESN is a string consisting of 40-digit numerals or letters obtained by encrypted calculation on the MAC addresses of the U2000 server networkinterface. 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 toreplacing 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 andcontact Huawei technical support engineers.

In a high availability system (Veritas hot standby) scheme, the primary and secondary sites share a U2000 license. The U2000 license file is bound tothe ESNs of the primary and secondary sites. When applying for a U2000 license, you must save the ESNs of the primary and secondary sitesseparately.

Procedure

1. Obtain the project contract number.

2. View ESNs of the primary and secondary sites by the following methods.Mode 1: Use the ESN tool to generate ESNs before installing the U2000.

NOTE:Make the following preparations:

Contact Huawei engineers to obtain the ESN tool package. Huawei engineers can go to http://support.huawei.com to download the ESN tool delivered with theversion. The ESN tool name is U2000version_ESN_solaris_SPARC.tar.

version indicates the detailed version number of the U2000. For example, V200R001C00SPCxxx.

Copy the ESN tool package to the computer.

a. 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, seeHow to Use the FileZilla to Transfer Files by SFTP.

b. Run the following commands to decompress the ESN tool package:# cd /opt# tar xvf U2000version_ESN_solaris_SPARC.tar

c. Run the following command to view the ESN:# ./esn

Information similar to the following is displayed:ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4ESN1:BDA706C825FE0543DC028209778AA66396545412ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BDESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4...

Mode 2: View the ESN using the ESN tool of the NMS after installing the U2000.

a. Log in to the OSs of the primary and secondary sites as the root user.

b. Run the following commands to view the ESN:# cd /opt/oss/server/platform/bin# ./esn

Information similar to the following is displayed:ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4ESN1:BDA706C825FE0543DC028209778AA66396545412ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BDESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4...

3. After the ./esn command is executed, the system automatically generates the Esn.txt path. Send the contract number and the ESNs of the primaryand secondary sites to the related Huawei engineer or the local office of Huawei.

NOTE:Huawei engineers access http://license.huawei.com to obtain the license based on the contract number and ESNs.

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.




1.3.1.5 Applying for the Veritas LicenseThis topic describes how to apply for a formal Veritas license. The Veritas license used in NMS installation is a demo license. After the server is delivered tothe installation site, the demo license must be replaced with a formal Veritas license in time.

Prerequisites

GTS rights for ESDP login are available.

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

1. Obtain information used for license download.

If the license confirmation form has been obtained, send the information to related Huawei engineers or the local office of Huawei.

If the license confirmation form has not been obtained, obtain the contract number and send it to related Huawei engineers or the localoffice of Huawei.

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 theobtained information.

3. In Carrier Navigation, select the ESDP product module.

4. Choose Order Management > Entitlement Management from the left-hand navigation tree. The Entitlement Management page is displayed.

5. On the Entitlement Management page, enter the following conditions and click Search.

Entitlement Type: Select The 3rd Party Software.

Huawei Contract No.: Enter the 14-digit Huawei Contract No..

6. View license information, select the required license, and click Download The 3rd Party License.

7. Download the license according to the right-hand button status.

If the Download License button is orange, the license can be downloaded.

If the Download License button is gray, the requirement has not been confirmed, and you must wait for a period of time to download thelicense.

If the Download License button is unavailable, the license cannot be downloaded.

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 downloadthe license.

8. After clicking the download button, verify that the information is consistent with information about installed software. Select I have read alreadyand enter Receiving E-mail address. Then click Sure to Download.

9. The related Huawei engineer sends the Veritas 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.

TroubleshootingIf the license cannot be obtained using the preceding method, see Applying for a Veritas License.


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

Configuring Controller IP Addresses for WorkstationThis topic describes how to configure controller IP addresses for the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 and M4000/M5000 servers. Systemcontroller IP addresses are used to install, manage, and maintain servers remotely. After servers are powered on, installation engineers can set systemcontroller IP addresses.

Configuring Controller IP Addresses for Disk ArraysThis topic describes how to configure controller IP addresses for the OceanStor S3900, OceanStor S2600, and StorageTek 2540 disk array.




1.3.2.1 Configuring Controller IP Addresses for WorkstationThis topic describes how to configure controller IP addresses for the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 and M4000/M5000 servers. System controllerIP addresses are used to install, manage, and maintain servers remotely. After servers are powered on, installation engineers can set system controller IPaddresses.

Configuring the IP Address for a System Controller on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 ServerThis topic describes how to configure the IP address for a system controller on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server. After the IPaddresses are configured, installation engineers can install operating systems and manage and maintain servers remotely by using this IP address.

Configuring the IP Address for a System Controller on an M4000/M5000 ServerThis topic describes how to configure the IP address for a system controller on an M4000/M5000 server. After the IP addresses are configured,installation engineers can install operating systems and manage and maintain servers remotely by using this IP address.

Parent topic: Configuring Controller IP Addresses

1.3.2.1.1 Configuring the IP Address for a System Controller on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server

This topic describes how to configure the IP address for a system controller on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server. After the IP addresses areconfigured, installation engineers can install operating systems and manage and maintain servers remotely by using this IP address.

Prerequisites

The controller IP addresses are obtained.

The server is powered on.

Context

Set connection parameters on a controller before you remotely control or maintain an Oracle server. The following operations can be skipped if the currentserver configurations are inconsistent with the collected controller IP addresses. For details about how to view the controller IP addresses, see How to View theController IP Addresses for the Sun Workstation.In the high availability (HA) system, operations must be performed at the primary and secondary sites.

Procedure

1. Connect the computer and the server physically.

a. Use a serial port (DB9-RJ45) to connect the serial port of the local console and the serial port (SERIAL MGT) of the server.Use an RJ-45 connector at one end of the serial port cable to connect to the serial port (SERIAL MGT) of the server and use a DB-9connector at the other end of the cable to connect to the serial port (COM1 or COM2) of the computer.

b. Use a network cable to connect the network management port (NET MGT) of the system controller and the switch.

NOTE:When configuring a controller, you can choose to connect the network interface to the DCN or not.

Figure 1 Connections between the Netra T4-1 server and the controller

Figure 2 Connections between the Oracle T4-1 server and the controller




Figure 4 Connections between the T5220 server and the controller

2. Set up a logical connection between the computer and the server.

a. Start the PC and log in to the Windows OS.

b. Run the PuTTY tool. In the dialog box that is displayed, choose Serial from the navigation tree.

c. In the right-hand pane, set parameters as follows for an interface, such as COM1:

Serial line to connect to: COM1

Speed(baud): 9600

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None

d. Choose Session from the navigation tree. In the right-hand pane, set Connection type to Serial and use the default values for otherparameters.

e. Click Open.

3. Enter the user name and password. The default user name is root and the default password is changeme.

NOTE:



The operating system (OS) will be started after this step is complete if the OS is installed on the workstation. Run the #. command to display the prompt of the controller.

After login, change the password immediately and keep the password confidential.

4. Perform the following operations to change the login password at the -> prompt:-> set /SP/users/root password

A message similar to the following is displayed:Enter new password:

Enter a new password, for example, Changeme_123. A message similar to the following is displayed to prompt you to enter the new passwordagain:Enter new password again:

NOTE: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 charactersare digits, letters, and special characters. Remember to change passwords regularly.

5. Perform the following operations to configure hardware at the -> prompt:

a. Enter cd /SP/network.The following message will be displayed:/SP/network

b. Enter set pendingipaddress=controller IP address.The following message will be displayed:Set 'pendingipaddress' to 'controller IP address'

c. Enter set pendingipdiscovery=static.The following message will be displayed:Set 'pendingipdiscovery' to 'static'

d. Enter set pendingipnetmask=controller subnet mask.The following message will be displayed:Set 'pendingipnetmask' to 'controller subnet mask'

e. Enter set pendingipgateway=gateway IP address of controller.The following message will be displayed:Set 'pendingipgateway' to 'gateway IP address of controller'

f. Enter set state=enabled.The following message will be displayed:Set 'state' to 'enabled'

g. Enter set commitpending=true.The following message will be displayed:Set 'commitpending' to 'true'

h. Enter exit to complete configuration.

6. If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used, run the following commands to configure hardware at the -> prompt:

a. Enter cd /SP/network/interconnect.The following message will be displayed:/SP/network/interconnect

b. Enter set hostmanaged=false.The following message will be displayed:Set 'hostmanaged' to 'false'

c. Enter set state=disabled.The following message will be displayed:Set 'state' to 'disabled'

d. Enter set commitpending=true.The following message will be displayed:Set 'commitpending' to 'true'

e. Enter exit to complete configuration.

7. After the configurations are performed, view the controller IP addresses. For details, see How to View the Controller IP Addresses for the SunWorkstation.

8. Disconnect the serial port of the system controller from the PuTTY. Configuration is complete.



Parent topic: Configuring Controller IP Addresses for Workstation

1.3.2.1.2 Configuring the IP Address for a System Controller on anM4000/M5000 Server

This topic describes how to configure the IP address for a system controller on an M4000/M5000 server. After the IP addresses are configured, installationengineers can install operating systems and manage and maintain servers remotely by using this IP address.

Prerequisites


The server is powered on.

Context

Set connection parameters on a controller before you remotely control or maintain an Oracle server. The following operations can be skipped if the currentserver configurations are inconsistent with the collected controller IP addresses. For details about how to view the controller IP addresses, see How to View theController IP Addresses for the Sun Workstation.In the high availability (HA) system, operations must be performed at the primary and secondary sites.

Procedure


a. Use a serial port (DB9-RJ45) to connect the serial port of the local console and the serial port (SERIAL MGT) of the server.Use an RJ-45 connector at one end of the serial port cable to connect to the serial port (SERIAL MGT) of the server and use a DB-9connector at the other end of the cable to connect to the serial port (COM1 or COM2) of the computer.


NOTE:When configuring a controller, you can choose to connect the network interface to the DCN or not.

Figure 1 Connections between the M4000 server and the controller

Figure 2 Connections between the M5000 server and the controller








Speed(baud): 9600

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None


e. Click Open.

3. Enter the user name. Enter the default user name (default) if the system is being logged in to for the first time.login: default

A message similar to the following will be displayed:Change the panel mode switch to Service and press return...

4. Within 5 to 10 seconds, insert the key into the key slot in the front panel of the M4000/M5000. Turn the switch to Service labeled with and pressEnter.A message similar to the following will be displayed:Leave it in that position for at least 5 seconds. Change the panel mode switch to Locked, and press return...

5. Within 5 to 10 seconds, turn the switch to Locked labeled with and press Enter.A message similar to the following will be displayed:XSCF>

NOTE:If the event that XSCF> is not displayed (which means that login has failed), attempt to log in again.

6. Run the following commands to create a monitor user:XSCF> adduser eis-installerXSCF> setprivileges eis-installer platadm useradm auditadm fieldengXSCF> password eis-installerNew XSCF password: Retype new XSCF password:

NOTE:The password must contain the following:

At least two lettersAt least one number or one special characterThe password contains a minimum of 8 characters and a maximum of 16 characters.

The eis-installer user has complete access rights and can run all commands after the password is set.

To ensure the security of the U2000, passwords must be complex enough. For example, set the password to Changeme_123. Remember to change passwords regularly. Keepyour password secure.

7. Run the following commands to log in to the system as the new user:XSCF> exit



logoutlogin: eis-installer

8. Enter the password.

9. Run the following command to set the time for automatic logout:XSCF> setautologout -s 6060min

10. Run the following command to set the time zone:XSCF> settimezone -c settz -s name_of_the_time_zone

NOTE:

Run the following command to query the name of the time zone:XSCF> settimezone -c settz -a -M

11. Run the following command to set the time:XSCF> setdate -s time

NOTE:

System time is entered in year.month.date-hour:minute:second (for example, 2008.03.25-17:13:00). System time will be displayed in the following format:Tue Mar 25 17:13:00 CST 2008

A message similar to the following will be displayed:The XSCF will be reset. Continue? [y|n]:

12. Enter n.

13. Run the following command to set the altitude:XSCF> setaltitude -s altitude=1000

A message similar to the following will be displayed:1000m

14. Run the following command to enable SSH:XSCF> setssh -c enable

A message similar to the following will be displayed:Continue? [y|n]:

15. Enter y. A message similar to the following will be displayed:Please reset the XSCF by rebootxscf to apply the ssh settings.

16. Run the following command to enable the Telnet function:XSCF> settelnet -c enable

17. Run the following command to configure the DSCP of the controller:XSCF> setdscpDSCP network [0.0.0.0] > 192.168.224.0DSCP netmask [255.255.255.0] > Press Enter to continue.XSCF address [192.168.224.1] > Press Enter to continue.Domain #00 address [192.168.224.2] > Press Enter to continue.Domain #01 address [192.168.224.3] > Press Enter to continue.

NOTE:If the configuration is being performed for the first time, the following message will be displayed: Commit these changes to the database? [y|n]. Enter y to accept the settings.

The Domain to Service Processor Communications Protocol (DHCP) is used to ensure the communication between the controller and domain. Both the controller and domainrequire an IP address for network connection. After the OS is installed, you can run the ifconfig -a command to view the IP addresses for a PPP connection.

The IP address of the DSCP must be configured as a private IP address and cannot be on the same network segment with the controller IP address.

18. Run the following commands to set the IP addresses of the controllers:XSCF> setnetwork -c up xscf#0-lan#0XSCF> setnetwork -c up xscf#0-lan#1XSCF> setnetwork xscf#0-lan#0 -m Subnet_mask IP_address_of_the_primary_controllerXSCF> setnetwork xscf#0-lan#1 -m Subnet_mask IP_address_of_the_secondary_controllerXSCF> sethostname -d huawei.comXSCF> setroute -c add -n 0.0.0.0 -g IP_address_of_the_network_gateway_of_the_primary_controller xscf#0-lan#0XSCF> setroute -c add -n 0.0.0.0 -g IP_address_of_the_network_gateway_of_the_secondary_controller xscf#0-lan#1

19. Run the following command:XSCF> sethostname xscf#0 sc

20. Run the following command to apply network settings:XSCF> applynetwork



A message similar to the following will be displayed:The following network settings will be applied: xscf#0 hostname :sc DNS domain name :huawei.com

interface :xscf#0-lan#0 status :up IP address :IP_address_of_the_primary_controller netmask :255.255.255.0 route :-n 0.0.0.0 -m 0.0.0.0 -g IP_address_of_the_network_gateway_of_the_primary_controller

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

Continue? [y|n]

21. Enter y. A message similar to the following will be displayed:Please reset the XSCF by rebootxscf to apply the network settings.Please confirm that the settings have been applied by executingshowhostname, shownetwork, showroute and shownameserver after rebootingthe XSCF.

22. Run the following command to restart the system controller so that the settings take effect:XSCF> rebootxscf

A message similar to the following will be displayed:The XSCF will be reset. Continue? [y|n]:

23. Enter y to restart the controller. A message similar to the following will be displayed:XSCF> Mar 25 09:13:02 localhost XSCF[105]: XSCF shutdown sequence start execute K000end -- completeexecute K100end -- completeexecute K101end -- complete......login:

Restarting the system controller takes about three minutes. Wait patiently.

24. After the configurations are performed, view the controller IP addresses. For details, see How to View the Controller IP Addresses for the SunWorkstation.

25. Optional: Perform the following to test the connection of the network management port of the primary controller.

NOTE:

The port of the primary controller on the M4000/M5000 server is on the right.Before the test, the console must communicate properly with the primary controller on the M4000/M5000 server. If the console is directly connected to the primarycontroller of the M4000/M5000 server by a network cable, you must change the IP address of the console to ensure that the IP addresses of the console and the primarycontroller are on the same network segment. For example, if the IP address of the primary controller is 10.9.1.21, the IP address of the console must be changed to10.9.1.121.

a. Run the following command on the console:# telnet IP_address_of_the_primary_controller

A message similar to the following will be displayed:login:

b. Enter the user name eis-installer. A message similar to the following will be displayed:password:

c. Enter the password of user eis-installer.

d. Run the following command to exit the connection to the primary controller:XSCF> exit

If installation engineers cannot log in to the network management port (NET MGT), check the network cable and the IP address settingson the console. If the problem persists, configure the server through the serial port cable of the local console again.

26. Optional: Perform the following to test the connection of the network management port of the secondary controller.

NOTE:

The port of the secondary controller on the M4000/M5000 server is on the left.Before the test, the console must communicate properly with the secondary controller on the M4000/M5000 server. If the console is directly connected to thesecondary controller of the M4000/M5000 server by a network cable, you must change the IP address of the console to ensure that the IP addresses of the console andthe secondary controller are on the same network segment. For example, if the IP address of the secondary controller is 10.9.2.21, the IP address of the console must bechanged to 10.9.2.121.

a. Run the following command on the console:# telnet IP_address_of_the_secondary_controller



A message similar to the following will be displayed:login:

b. Enter the user name eis-installer. A message similar to the following will be displayed:password:

c. Enter the password of user eis-installer.

d. Run the following command to exit the connection to the primary controller:XSCF> exit

If you cannot log in to the network management port (NET MGT), check the network cable and the IP address settings on the console. Ifthe problem persists, configure the server through the serial port cable of the local console again.

27. Disconnect the serial port of the system controller from the PuTTY. Configuration is complete.

Parent topic: Configuring Controller IP Addresses for Workstation

1.3.2.2 Configuring Controller IP Addresses for Disk ArraysThis topic describes how to configure controller IP addresses for the OceanStor S3900, OceanStor S2600, and StorageTek 2540 disk array.

Setting the SC IP Address for the OceanStor S3900 Disk ArrayThis 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 addresshas been set, you can use the Web browser to remotely access and control the disk array.

Setting the SC IP Address for the OceanStor S2600 Disk ArrayThis topic describes how to set the SC IP address for the OceanStor S2600 disk array before using OceanStor S2600 disk array. After the SC IP addresshas been set, you can use the Web browser to remotely access and control the disk array.

Setting the SC IP Address for the StorageTek 2540 Disk ArrayThis topic describes how to set the SC IP address for the StorageTek 2540 disk array before using the StorageTek 2540 disk array. After the SC IPaddress has been set, you can use the Web browser to remotely access and control the disk array.

Parent topic: Configuring Controller IP Addresses

1.3.2.2.1 Setting the SC IP Address for the OceanStor S3900 Disk ArrayThis 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 hasbeen set, you can use the Web browser to remotely access and control the disk array.

Prerequisites


The power cable of the disk array is connected.

Context

The OceanStor S3900, a disk array, has two controllers. The IP addresses configured in this section are examples only. For example, set the IP address ofcontroller A to 192.168.128.203 and the IP address of controller B to 192.168.128.204.

Procedure

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 computer to the serial port of the disk array (SERIAL MGT).Use an RJ45 connector at one end of the serial port cable to connect to the serial port of the disk array (SERIAL MGT) and a DB-9 connector at theother end of the cable to connect to the serial port of the computer (COM1 or COM2).



2. Set up a logical connection between the PC and disk array controller A.





Speed(baud): 115200

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None


e. Click Open.The following message will be displayed on the Windows management terminal if the connection was established:Storage login:

f. Enter the user name and password to log in.

NOTE:The default user name and password of the system administrator are admin and [email protected] ensure the security of the U2000, passwords must be complexenough. For example, a password must contain eight or more characters of two types. The allowed characters are digits, letters, and special characters. Remember tochange passwords regularly.

After login authentication, the system will display the CLI.

g. Run the following command to change the default password:admin:/>chguserpwdOld password:New password:Re-enter new password:

NOTE:Change the password as prompted. For example, change the password to Changeme_123. To ensure the security of the U2000, passwords must be complex enough.For example, a password must contain eight or more characters of two types. The allowed characters are digits, letters, and special characters. Remember to changepasswords regularly.

3. In the CLI, run the chgctrlip command to configure the IP address for the network interface of controller A. See Table 1.

Table 1 Command format and parameter description of the chgctrlip commandCommand Format Parameter Description



Command Format Parameter Description

chgctrlip -c controller ID { -ip IP address | -mask subnet mask | -gwgateway }

-c controller ID: Indicates the controller ID. The value of this parameter isa or b, where, a represents controller A and b represents controller B.-ip IP address: Indicates the IP address of the management networkinterface of the controller.-mask subnet mask: Indicates the subnet mask.-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 is255.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

4. Disconnect the serial port from controller A.

a. In the CLI, run the logout command.

b. On the computer, exit the PuTTY software.

c. Remove the serial port cable on the disk array.

5. Repeat Step 1 to Step 4 to configure the network interface of controller B.

a. Connect the computer and controller B physically.

b. Establish a logical connection between the computer and controller B.

c. Configure the IP address of the network interface of controller B on the local console.Configure the IP address for the management network interface of controller B. Specifically, the IP address is 192.168.128.204, the subnetmask 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

6. Disconnect the serial port from controller B.




Parent topic: Configuring Controller IP Addresses for Disk Arrays

1.3.2.2.2 Setting the SC IP Address for the OceanStor S2600 Disk ArrayThis topic describes how to set the SC IP address for the OceanStor S2600 disk array before using OceanStor S2600 disk array. After the SC IP address hasbeen set, you can use the Web browser to remotely access and control the disk array.

Prerequisites



Context

The OceanStor S2600, a disk array, has two controllers. The IP addresses configured in this section are examples only. For example, set the IP address ofcontroller A to 192.168.128.203 and the IP address of controller B to 192.168.128.204.

Procedure

1. Connect the computer and controller A of the disk array physically.Use a serial port cable (DB9-RJ45) to connect the serial port of the local controller to the serial port of the disk array (SERIAL MGT).Use an RJ-45 connector at one end of the serial port cable to connect to the serial port of the disk array (SERIAL MGT) and a DB-9 connector at theother end of the cable to connect to the serial port of the computer (COM1 or COM2).








Speed(baud): 115200

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None


e. Click OK.The following message will be displayed on the Windows management terminal if the connection was established:Login:

f. Enter the user name and password to log in.

NOTE:The default user name and password of the system administrator are admin and 123456.

After login authentication, the system will display the CLI.

g. Run the following command to change the default password:admin:/>chgpasswdplease input old password:please input new password:please input new password again:

NOTE:Change the password as prompted. For example, change the password to Changeme_123. To ensure the security of the U2000, passwords must be complex enough.For example, a password must contain eight or more characters of two types. The allowed characters are digits, letters, and special characters. Remember to changepasswords regularly.

3. In the CLI, run the chgctrlip command to configure the IP address for the network interface of controller A. See Table 1.

Table 1 Command format and parameter description of the chgctrlip commandCommand Format Parameter Description

chgctrlip -c controller ID { -a IP address | -s subnet mask | -g gateway}

-c controller ID: Indicates the controller ID. The value of this parameter isa or b, where, a represents controller A and b represents controller B.-a IP address: Indicates the IP address of the management networkinterface of the controller.-s subnet mask: Indicates the subnet mask.-g 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 is255.255.255.0, and the gateway IP address is 192.168.128.1. Run the following command:OceanStor: admin> chgctrlip -c a -a 192.168.128.203 -s 255.255.255.0 -g 192.168.128.1

4. Disconnect the serial port from controller A.






5. Repeat Step 1 to Step 4 to configure the network interface of controller B.

a. Connect the computer and controller B physically.


c. Configure the IP address of the network interface of controller B on the local console.

OceanStor: admin> chgctrlip -c b -a 192.168.128.204 -s 255.255.255.0 -g 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 format of the showctrlip command: showctrlip [ -c controller ID ]

Parameter Description: -c controller ID: Indicates the controller ID. The value of this parameter is a or b, where, a represents controller A and b represents controller B.

Precautions for running the showctrlip command are as follows:

Run the showctrlip command to query the IP addresses of the management network interfaces of all controllers.Run the showctrlip -c controller ID command to query the IP address of the management network interface of a specified controller.

The following is an example for querying the IP addresses of the management network interfaces of all controllers:

OceanStor: admin> showctrlip Controller IP Address Subnet Mask Gateway MAC Address A 192.168.128.203 255.255.255.0 192.168.128.254 00:12:34:56:70:46 B 192.168.128.204 255.255.255.0 192.168.128.254 00:12:34:56:79:92

6. Disconnect the serial port from controller B.





1.3.2.2.3 Setting the SC IP Address for the StorageTek 2540 Disk ArrayThis topic describes how to set the SC IP address for the StorageTek 2540 disk array before using the StorageTek 2540 disk array. After the SC IP address hasbeen set, you can use the Web browser to remotely access and control the disk array.

Prerequisites



Context

Each StorageTek 2540 disk array has two controllers that need to be configured separately.

Procedure

1. Connect the computer and controller A of the disk array physically.Use a serial port cable (DB9-PS/2) to connect the serial port of the local controller to the serial port of the disk array (SERIAL MGT).Use a PS/2 connector at one end of the serial port cable to connect to the serial port of the disk array (SERIAL MGT) and a DB-9 connector at theother end of the cable to connect to the serial port of the computer (COM1 or COM2).

Figure 1 Connections between the local console and the controller on the StorageTek 2540 disk array








Speed(baud): 38400

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None


e. Click Open.

3. Configure the IP address of the network interface of controller A of the disk array on the local console.

NOTE:Each StorageTek 2540 disk array has two controllers that need to be configured separately.

a. Send a break signal from the computer by pressing Ctrl+Pause Break. Press within 5 seconds: <S> for Service In press <space> within 5 seconds Baud rate set to 38400

b. Enter S to open the service window. 03/28/08-05:21:18 (GMT) (utlTimer): WARN: Extended Link Down Timeout on channel 203/28/08-05:21:18 (GMT) (utlTimer): WARN: Extended Link Down Timeout on channel 3Current date: 03/28/08 time: 05:22:11Enter Password to access Service Interface (60 sec timeout):

c. Enter a password. Enter the default password kra16wen to access the disk array if the configuration is being performed for the first time.

NOTE:In the default password, 1 is the number one and not the letter l. To ensure system security, change the default password in time. For details, press 3 in the ServiceInterface Main Menu dialog box. To ensure the security of the U2000, passwords must be complex enough. For example, a password must contain eight or morecharacters of two types. The allowed characters are digits, letters, and special characters. Remember to change passwords regularly.

-> Service Interface Main Menu==============================

1) Display IP Configuration 2) Change IP Configuration 3) Reset Storage Array (SYMbol) Password Q) Quit Menu

Enter Selection:

d. Enter 2 to set the IP address of the first controller. Enable IPv4? (Y/N):

e. Enter y to enable IPv4. Configure using DHCP? (Y/N): n

f. Enter n to disable DHCP. Press '.' to clear the field; Press '-' to return to the previous field; Press <ENTER> and then ^D to quit (Keep Changes)

Current Configuration New ConfigurationIP Address if0 : Subnet Mask if0 : Gateway IP Address if0 :

g. Enter the IP address, subnet mask, and gateway IP address of the controller. The IP Configuration is getting changed to:

IP Address : IP address of the controller Subnet Mask : Subnet mask of the controller Gateway IP Address : Gateway IP address of the controller

Are you sure that you want to change IP Configuration ? (Y/N): y

h. Enter y if you want to modify the IP address. Network Configuration successfully changed.

Enable IPv6? (Y/N):

i. Enter n to disable IPv6. Change port configuration (speed & duplex) ? (Y/N):

j. Enter n so that the port configuration will not be modified.



Reboot to have the settings take effect? (Y/N)

k. Enter y to restart the system and make the configuration take effect. ...Send <BREAK> for Service Interface or baud rate change

4. Disconnect the serial port cable from controller A.

a. On the computer, exit the PuTTY software.

b. Remove the serial port cable on the disk array.

5. Repeat Step 1 to Step 4 to configure the network port of controller B.

a. Establish a physical connection between the computer and controller B.



d. Disconnect the serial port from controller B.


1.3.3 Powering On a ServerThis topic describes how to power on a server. The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server, M4000/M5000 server, and disk array are used asexamples to explain how to power on a server based on the server type and disk array type.

Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server

1. Power on a Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server.

NOTICE:

Oracle SPARC T4-2 workstations support only 200 ~ 240 VAC input voltage and do not support 100 ~ 120 VAC input voltage.Netra T4-1/Oracle T4-1/T5220/M4000/M5000 server supports 200 to 240 VAC and 100 to 120 VAC input voltage.Configure power supply based on the rated system power requirement, see U2000 Hardware Installation Guide (Huawei N610E cabinet).If the power supply is insufficient, the server automatically stops and the high availability system fails to trigger an active/standbyswitchover.

2. Wait about 2 or 3 minutes. Then switch on the power of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 workstation to start the server.

3. After the server is started, check indicators on the front panel. If the power indicator is steady green, the server is powered on. If another indicator ison or blinks, the server does not function properly. Contact the server maintenance engineers to solve the problem. The following figure shows thepositions of the power switch and power indicator.

Figure 1 Power switch and power indicator on the Netra T4-1 server

Figure 2 Power switch and power indicator on the Oracle T4-1 server




Figure 4 Power switch and power indicator on the T5220 server

NOTE:

If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.If the server displays the OK prompt, enter boot. If the server does not respond, no Solaris OS has been installed on the server.

M4000/M5000 Server

1. Power on an M4000/M5000 server.

NOTE:Configure power supply based on the rated system power requirement, see U2000 Hardware Installation Guide (Huawei N610E cabinet). If the power supply is insufficient, theserver automatically stops and the high availability system fails to trigger an active/standby switchover.

This issue occurs frequently for the M4000/M5000 with high power consumption.

2. Insert the key delivered with the server into the key slot in the front panel of the M4000/M5000 server, and turn the rotary switch to the Locked

position labeled with , as shown in the following figure.

Figure 5 Power button on the M4000/M5000 server

3. Press the power switch of the workstation, which is identified by . Wait 2 to 3 minutes. If front indicator of the server is on (changes to steadygreen), the server starts up and performs self-diagnosis.

NOTE:Ensure that the green LED power indicator on the operation panel is lit.During the power-on process, it is recommended that you use a PC to log in to the controller on an M4000/M5000 server through a serial interface and enter console -d 0 -f to view the server start status.If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.

If turn the rotary switch to the Service position labeled with , the server cannot access the OS automatically, the server displays the ok prompt. Enter boot. If theserver does not respond, no Solaris OS has been installed on the server.

Disk Array

NOTICE:

To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables, or serial cables when powering on a disk array.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, waitat least 1 minute before turning it on.

Power on a disk array.Power-on SequenceFor OceanStor S3900:



Normal power-on sequence: switch on the power switches of the external power supplies connected to all the devices → press the power button oneither controller → switch on the LAN switch or FC switch (if any LAN switch or FC switch is deployed but is not powered on) → switch on theapplication server (if the application server is not powered on).

Normal power-down sequence: stop the services of the application server → hold the power button for 5 seconds on either controller → disconnectthe controller enclosure and disk enclosures from the external power supplies.

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:Power supply must be provided for the two power modules of the OceanStor S2600 and OceanStor S3900; otherwise, the OceanStor S2600 and OceanStor S3900 fail to be used. Then pressthe power switch on the controller A/B to wait 5 to 10 minutes until the power indicator is steady green, no longer flashing, indicating the success of the power-on.

Physical indications that the storage system is up and running without error:

The power indicators of the controllers, controller enclosure, and disk enclosures are steady green.

The alarm indicators of the controllers, controller enclosure, and disk enclosures are off.

The running indicators of the coffer disks are steady green, and their alarm/location indicators are off.


1.3.4 Installing a Solaris 10 OS Using a Quick Installation DVDThis topic describes how to install a Solaris 10 OS for the primary and secondary sites using a quick installation DVD.

Prerequisites

Ensure that the server DVD-ROM drive is available and can read DVD-ROM data.

Ensure that the used disks are inserted in sequence from the first slot.

The quick installation DVD.

Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4v_dvd2 is available if the hardware type of theselected server is sun4v (the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server for example).

Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4u_dvd1 is available if the hardware of theselected server is sun4u (the M4000/M5000 server for example).

NOTE:If the server has been configured with an OS, log in to the OS as the root user and run the uname -m command to view the hardware type of the server.

Obtain the following information:

Host name

Network interface

System IP address

Subnet mask

Route

The IP address of the system controller is configured. For details about how to configure the IP address, see Configuring Controller IP Addresses forWorkstation.

Context

NOTE:The operations mentioned in this topic must be performed on all the servers of the primary and secondary sites.

If no quick installation DVD is available on site, manually install an OS using the Solaris installation DVD delivered along with equipment. For details abouthow to manually install an OS, see Manually Installing the Solaris OS and Its Patches.

Procedure

1. Optional: If two or more servers are located on the same LAN and the quick installation DVD-ROM is used to install the OS, remove the cablesconnected to the server interfaces, and leave only the cable connected to the NET MGT interface on the system controller to install the Solaris OS,Otherwise, IP conflict will occur during OS installation. For locations of the server interfaces and the NET MGT interface on the system controller,see the diagram in Configuring Controller IP Addresses for Workstation.

2. Optional: Display the ok prompt using the controller.

If the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server is used, perform the following operations to display the OK prompt:

a. Log in to the system controller in SSH mode.



NOTE:The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server does not support login through Telnet. Log in to the system controller performing the following:

Install the tool software of the SSH client on the Windows terminal to log in to the system controller, for example: Putty.Run the ssh SC_IP_Address command on the terminals of other Sun servers. If the following message is displayed, enter yes:The authenticity of host '10.9.1.20 (10.9.1.20)' can't be established.RSA key fingerprint is 0b:23:07:0c:27:72:44:3f:d1:aa:12:99:ed:dd:c0:5a.Are you sure you want to continue connecting (yes/no)?

b. In the CLI, enter the user name and password of the system controller. The default user name and password are root andchangeme.

NOTE:To ensure system security, change the default password in time. If the default password has been changed, enter the new password.

c. Optional:Perform the following operations to check whether the system controller of the server needs to be upgraded:

-> cd /HOST-> ls

T5220 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware7.1.6.j 2008/11/25 11:12.If sysfw_version shows that the version is 7.4.6.c or later, perform the next step. If sysfw_version shows that theversion is earlier than 7.4.6.c, you must upgrade the system controller. For details, see How to Upgrade the SystemController Firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server.

Netra T4-1/Oracle T4-1/Oracle T4-2 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware8.2.1.b 2012/08/03 11:58.If sysfw_version shows that the version is 8.3.0 or later, perform the next step. If sysfw_version shows that the versionis earlier than 8.3.0, you must upgrade the system controller. For details, see How to Upgrade the System ControllerFirmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server.

d. Run the following command:-> set /HOST/bootmode state=reset_nvram script="setenv auto-boot? false"

NOTE:There must be a space between ? and false.

The following message will be displayed:Set 'state' to 'reset_nvram'Set 'script' to 'setenv auto-boot? false'

e. Run the following command:-> start /SYS

The following message will be displayed:Are you sure you want to start /SYS (y/n)?

f. Enter y to start the server.If the message start: Target already started is displayed, the system is running. Perform the following operations:

Run the following command:-> stop /SYSThe following message will be displayed:Are you sure you want to stop /SYS (y/n)?

Enter y. The following message will be displayed:Stopping /SYS

Enter show /HOST status repeatedly to check the system status. After a message containing status = Powered off is displayed,proceed with the next step.

Run the following command:-> start /SYSThe following message will be displayed:Are you sure you want to start /SYS (y/n)?

Enter y to start the server.

g. Run the following command to display the ok prompt:-> start /SP/console

The following message will be displayed:Are you sure you want to start /SP/console (y/n)?

h. Enter y and press Enter.

NOTE:If a prompt is displayed, enter y and press Enter.



If the following information is displayed, the EEPROM Password policy in SetSolaris security hardening has been enabled.

Firmware Password:Enter the Firmware Password, The default password is sek12345.

The following message will be displayed:Serial console started. To stop, type #....Setting NVRAM parameters to default values.

SPARC Enterprise T5220, No KeyboardCopyright 2008 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.28.0, 8064 MB memory available, Serial #85369820.Ethernet address 0:21:28:16:a3:dc, Host ID: 8516a3dc.

auto-boot? = false{0} ok

If the M4000/M5000 server is used, perform the following to display the OK prompt:

a. Log in to the system controller through Telnet. Run the telnet Controller IP Address command on the controller.The following message will be displayed:Login:

b. Enter eis-installer as the user name.The following message will be displayed:Password:

c. Enter the password of user eis-installer.The following message will be displayed:XSCF>

d. Enter showdomainmode -d 0.The following message will be displayed:Host-ID : 8501c2deDiagnostic Level : minSecure Mode : off (host watchdog: unavailable Break-signal: receive) Autoboot : on CPU Mode : auto

NOTE:If the Secure Mode item is in the on state, perform the following:

a. Enter setdomainmode -d 0 -m secure=off.

The following message will be displayed:

Diagnostic Level :min -> -Secure Mode : on -> off Autoboot : on -> -CPU Mode : auto The specified modes will be changed.Continue? [y|n]

b. Enter y.


configured.Diagnostic Level : minSecure Mode : off (host watchdog: unavailable Break-signal: receive)Autoboot : on (autoboot:on)CPU Mode : auto

e. Enter showdomainstatus -a.The following message will be displayed:DID Domain Status00 Running01 -

If the command output contains running, enter sendbreak -d 0.The following information will be displayed:Send break signal to DomainID 0?[y|n]

If the command output shows that the status is not running, the system is normal and you need to enter reset -d 0 xir.The following message will be displayed:DomainID to reset:00Continue? [y|n]

f. Enter y.

g. Enter console -d 0 -f.The following message will be displayed:Connect to DomainID 0? [y|n]




NOTE:If the following information is displayed, the EEPROM Password policy in SetSolaris security hardening has been enabled.

Firmware Password:Enter the Firmware Password. The default password is sek12345.

OK

3. Insert the quick installation DVD of the server into the DVD drive of the server.

4. Run the following command to enable the system to boot from the DVD-ROM and open the single-user installation window. Press Enter.

If the server model is Netra T4-1/Oracle T4-1/T5220/M4000/M5000, run the following command:ok boot cdrom - install

If the server model is Oracle T4-2, run the following command:ok boot dvd - install

NOTE:There must be a space between - and install.Wait about ten minutes. The single-user installation window will be displayed.

Please select the install type for the server:--------------------------------------------------------------- 1 Standard type 2 Silent type---------------------------------------------------------------Please enter [1,2]:>

NOTE:In the preinstallation scenario, select Silent type. In other scenarios, select Standard type.

5. Enter 1 to select the install type for server. Press Enter.The following install type for the server is selected:---------------------------------------------------------------1 Standard type---------------------------------------------------------------Enter 'y' to apply the configuration and continue the restoration, or enter 'n' to return and make changes (y/n):>

6. Confirm the configurations. Enter y and press Enter.Please select the server mode:--------------------------------------------------------------- 1 Single Server System 2 High Availability System (Veritas Hot Standby)---------------------------------------------------------------Please enter [1,2]:>

7. Enter 2 to select the Veritas high availability system. Then, press Enter.Please confirm the configuration...The server mode is as follows:---------------------------------------------------------------2 High Availability System (Veritas Hot Standby)---------------------------------------------------------------Enter 'y' to apply the configuration and continue the restoration, or enter 'n' to return and make changes (y/n):>

8. Confirm the configurations. Enter y and press Enter.If the server will use a disk array:--------------------------------------------------------------- 1 Yes 2 No---------------------------------------------------------------Please enter [1,2]:>

9. Enter 1 or 2 according to conditions at your site. For example, if a disk array is not connected, select 2.The choice is as follows:--------------------------------------------------------------- 2 No---------------------------------------------------------------Enter 'y' to apply the configuration and continue therestoration, or enter 'n' to return and make changes (y/n):>

10. Enter y after you confirm that the configuration is correct and press Enter.Please configure the network information on the server.Please enter a new host name for the server:>

11. Enter the planned host name of the server and press Enter.

NOTE:If the OS is installed at the primary site, enter the host name planned for the primary site, such as primaster; if the OS is installed at the secondary site, enter the host nameplanned for the secondary site, such as secmaster.

Please enter a new IP address for the server:



>

12. Enter the system IP address of the server and press Enter.

NOTE:If the OS is installed at the primary site, enter the system IP address of the primary site; if the OS is installed at the secondary site, enter the system IP address of the secondarysite.

Please enter a new subnet mask for the server:>

13. Enter the system IP address mask of the server and press Enter.

NOTE:If the OS is installed at the primary site, enter the system IP address mask of the primary site; if the OS is installed at the secondary site, enter the system IP address mask of thesecondary site.

Confirm the configuration of the server.The configuration of the server is as follows:--------------------------------------------------------------- Hostname Primaster IP address 10.9.1.1 Netmask 255.255.255.0---------------------------------------------------------------Enter 'y' to apply the configuration and continue therestoration, or enter 'n' to return and make changes [y/n]:>

14. Enter y after you confirm that the configuration is correct and press Enter.The configuration of the server is confirmed.The NICs available in the local server are as follows:------------------------------------------- 1 e1000g0 2 e1000g1 3 e1000g2 4 e1000g3-------------------------------------------Please enter a number to select the system NIC[1-4]:>

NOTE:The mappings Between Physical and Logical Network Interfaces on an Oracle Server Running Solaris see Mappings Between Physical and Logical Network Interfaces onServer Running Solaris.

15. Enter 1 or another number to select the correct network interface of the system IP address and press Enter.NIC e1000g0 is selected!Enter 'y' to confirm the selection of NIC e1000g0 and continue,or enter 'n' to return and make changes [y/n]:>

16. Enter y after you confirm that the configuration is correct and press Enter. The system automatically starts to import data.

NOTE:The workstation automatically restarts after the system data is imported.It takes about 60 minutes to import the system data from the DVD to the workstation. The time required depends on the workstation model.

17. Optional: If # appears after the message "Solaris installation program completed" is displayed, enter reboot and press Enter to restart the OS.

18. Optional: If information similar to the following is displayed during the workstation restart, enter 3 to select DEC VT100 and press Enter.What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 3) DEC VT100 4) Heathkit 19 5) Lear Siegler ADM31 6) PC Console 7) Sun Command Tool 8) Sun Workstation 9) Televideo 910 10) Televideo 925 11) Wyse Model 50 12) X Terminal Emulator (xterms) 13) CDE Terminal Emulator (dtterm) 14) OtherType the number of your choice and press Return:

19. Optional: If the Configure Keyboard Layout window is displayed, press F2 or Esc + 2 to continue.

20. Log in to the Solaris OS as user root.

NOTE:The default login password is Changeme_123. To ensure the system security, run the passwd command to change the password immediately after you log in to thesystem for the first time.By default, the system enables the root user to perform remote login.

If login to Solaris OS as user root is possible, Solaris OS is successfully installed. Otherwise, install the OS again.

21. Ensure that the time zone and time of the OS are consistent with the local time zone and time. Run the date command to view the current time andtime zone. For details, see How to Change the System Time and Time Zone of Solaris OS.

22. Run the following command to eject the DVD:



# 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 thedrive mounting position.

# df -h.../vol/dev/dsk/c2t6d0/solaris 2.8G 2.8G 0k 100% /cdrom/solarisThe drive mounting position is solaris. Run the eject solaris command to eject the DVD.

23. 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 How to Add the Default Route.

a. Log in to the server as the root user and run the following command to add a static route:# route -p add destination network segment address -netmask destination network segment subnet mask gateway IP address

NOTE:destination network segment address: network segment on which the IP address of the computer connecting to the U2000 server is locateddestination network segment subnet mask: subnet mask of the network segment on which the IP address of the computer connecting to the U2000 serveris locatedgateway IP address: gateway IP address of the network on which the U2000 server is located

For example, add a static route from the U2000 server (IP address: 10.9.1.1; subnet mask: 255.255.255.0; gateway IP address: 10.9.1.254)to a remote computer (IP address: 10.67.56.226; subnet mask: 255.255.254.0; gateway IP address: 10.67.56.1).# route -p add 10.67.56.0 -netmask 255.255.254.0 10.9.1.254

b. Run the following command in the CLI to check that the route has been added:# netstat -nrRouting Table: IPv4 Destination Gateway Flags Ref Use Interface-------------------- -------------------- ----- ----- ---------- ---------10.67.56.0 10.9.1.254 UG 1 61

If the preceding information is displayed, the static route has been added. Otherwise, add a static route again.

24. If 1 is performed, connect network cables to all NICs on the servers to ensure smooth network communication.

Follow-up Procedure

1. Run the following command to view the version of the system:# more /etc/release

A message similar to the following will be displayed: Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Assembled 23 August 2011

If the Solaris version is Solaris 10 8/11 if the following message is displayed. The OS and patches are successfully installed. Otherwise, use a correctinstallation DVD-ROM to reinstall the OS.

2. Run the following command to view the version of the system and its patches:# uname -rv

A message similar to the following will be displayed:5.10 Generic_150400-11If the core patch version is 5.10 Generic_150400-11, the OS and the sparc_patch_20.0.0 patch have been installed. If another version is displayed,install the OS patch. For details, see Installing the Solaris OS Patches.


1.3.5 Installing the U2000 SoftwareThis topic describes how to install the U2000 software on the primary and secondary sites. You must start the U2000 installation program after the U2000 ispreconfigured using a DVD or software package.

Preparing Software PackagesThe U2000 can be installed using a software package or a DVD. If the U2000 is installed using a software package, the software package needs to beuploaded to the server and decompressed. If the U2000 is installed using a DVD, you can skip the operations mentioned in this topic.

Pre-configuring the U2000Before starting the U2000 installation program, you must configure the OSs of the primary and secondary sites. Preconfigure the system by using a DVDor software package.



Starting the U2000 Installation ProgramThis topic describes how to start the U2000 installation program. Install the U2000 software through the GUI (recommended) or CLI. If the GUI cannotbe logged in to, install the U2000 software through the CLI. GUI is short for graphical user interface and CLI for command line interface.


1.3.5.1 Preparing Software PackagesThe U2000 can be installed using a software package or a DVD. If the U2000 is installed using a software package, the software package needs to be uploadedto the server and decompressed. If the U2000 is installed using a DVD, you can skip the operations mentioned in this topic.

Context

NOTICE:

Do not decompressing the U2000version_client_solaris_SPARC.tar and the following software packages into the same directory will cause theU2000 installation to fail.All software packages must be uploaded to the specified directories at the primary and secondary sties.

Procedure

1. Upload the Veritas software package U2000version_veritas6.0.1_solaris.tar.gz to the /opt/vrtstmp path on the workstation and then decompress it:

a. Log in to the Solaris OS as user root.

b. Run the following command to create the /opt/vrtstmp directory:# mkdir /opt/vrtstmp

c. Use SFTP/FTP to upload the U2000version_veritas6.0.1_solaris.tar.gz file to the /opt/vrtstmp directory of the server as the root user.Using SFTP is recommended because SFTP provides higher security than FTP. For details about the method of using SFTP to upload thesoftware package, see How to Use the FileZilla to Transfer Files by SFTP. For details about the method of using FTP to upload thesoftware package, see How to Transfer Files by Means of FTP.

d. Run the following command to view the MD5 code in the uploaded software package and check whether the uploaded software package isappropriate.# cd /opt/vrtstmp# digest -v -a md5 U2000version_veritas6.0.1_solaris.tar.gz

A message similar to the following will be displayed:md5 (U2000version_veritas6.0.1_solaris.tar.gz) = XXXXXXXXXXXXXXXXXXXXX

NOTE:Here, XXXXXXXXXXXXXXXXXXXXX specifies the MD5 code of the software package. The actual output may be different from the example. Checkwhether the MD5 code is the same as the counterpart in the iManager U2000 version MD5 CODE(English) file as required. If they are the same, theuploaded software package is appropriate.For details about how to obtain the iManager U2000 version MD5 CODE(English) file:

a. Access http://support.huawei.com.b. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManager U2000 > iManager U2000 >

desired U2000 version.c. Download the file in the Release Document column.

e. Run the following commands to switch to the directory where the software packages reside. Decompress the uploaded Veritas softwarepackage and assign executable rights to the directory where the software packages reside.# cd /opt/vrtstmp# gzcat U2000version_veritas6.0.1_solaris.tar.gz | tar -xvBpf -# chmod -R +x /opt/vrtstmp

2. Upload all software packages except the Veritas software to the /opt/install path on the server and then decompress them.


b. Run the following command to create the /opt/install directory:# mkdir /opt/install

c. Use SFTP/FTP to upload the software packages to the /opt/install directory on the server as the root user. Using the FileZilla to transferfiles by means of SFTP is recommended. For details about how to use SFTP to transfer files, see How to Use the FileZilla to TransferFiles by SFTP. Alternatively, use FTP to transfer files. For details about how to use FTP to transfer files, see How to Transfer Files byMeans of FTP.

NOTE:Ensure that all mandatory software packages are uploaded. If a software package is not uploaded, the U2000 installation may be interrupted because a file is lacked.Selecting the components of the transport, IP, and access domains is recommended. So that, you only need to deploy instances when adding domains, instead ofdownloading software again. In this situation, only the disk space, not the database space, is occupied.Software packages for the transport and IP components mustbe uploaded so as to manage PTN 6900 series NEs. The installation packages to be uploaded are as follows:

a. Security enhancement software SetSolaris (Mandatory): U2000version_VPPSetsolarisV300R003C20SPC100.tar.



b. Veritas patch (Mandatory): U2000version_server_veritas603100_patch_solaris_SPARC.tarc. Database software (Mandatory): U2000version_server_db_solaris_SPARC.tar.d. Basic components (Mandatory): U2000version_server_nmsbase_solaris_SPARC.tare. Core components (Mandatory): U2000version_server_nmscore_solaris_SPARC.tarf. Components of the transport domain (Select it if you want to manage transport or PTN equipment): U2000version_server_nmstrans_solaris_SPARC.targ. Components of the IP domain (Select it if you want to manage routers, switches, or security equipment):

U2000version_server_nmsip_solaris_SPARC.tarh. Components of the access domain (Select it if you want to manage access equipment): U2000version_server_nmsaccess_solaris_SPARC.tari. Components of the CMC domain (Select it if you want to manage CMC equipment): U2000version_server_nmscmc_solaris_SPARC.tarj. StorageTek 2540 disk array manager CAM (Select it when you configure the StorageTek 2540 disk array. The software package does not need to be

uploaded for the S9300 and S2600 disk arrays.): U2000version_server_ospatch_solaris_SPARC.tar.

Run the following commands to view the uploaded software packages:

# cd /opt/install# ls -l

d. Run the following command to view the MD5 code in the uploaded software package and check whether the uploaded software package isappropriate.# cd /opt/install# digest -v -a md5 filename

A message similar to the following will be displayed:md5 (U2000version_server_db_solaris_SPARC.tar) = XXXXXXXXXXXXXXXXXXXXX

NOTE:Here, XXXXXXXXXXXXXXXXXXXXX specifies the MD5 code of the software package. The actual output may be different from the example. Checkwhether the MD5 code is the same as the counterpart in the iManager U2000 version MD5 CODE(English) file as required. If they are the same, theuploaded software package is appropriate.For details about how to obtain the iManager U2000 version MD5 CODE(English) file:

a. Access http://support.huawei.com.b. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManager U2000 > iManager U2000 >

desired U2000 version.c. Download the file in the Release Document column.

e. Run the following commands to switch to the directory where the software packages reside, and then run the /usr/sfw/bin/gtar commandto decompress the uploaded software packages on the server.# cd /opt/install

NOTE:Decompressing the Veritas patch package is optional. It is recommended that the Veritas patch package not be decompressed.The other software packages must be decompressed one by one. There is no specific decompression sequence.

To view information about software packages in the /opt/install directory, run the command ls -la.

# /usr/sfw/bin/gtar xvf Name_of_software_package

For example, /usr/sfw/bin/gtar xvf U2000version_server_nmscore_solaris_SPARC.tar.

NOTICE:The security hardening software SetSolaris is used to enhance Solaris security. Be sure to decompress this package. If the softwarepackage is not decompressed, preconfiguration fails.

Parent topic: Installing the U2000 Software

1.3.5.2 Pre-configuring the U2000Before starting the U2000 installation program, you must configure the OSs of the primary and secondary sites. Preconfigure the system by using a DVD orsoftware package.

Prerequisites

Installation engineers are familiar with the IP address planning scheme of the U2000. For more information, see Collecting Installation Information.

The hardware is properly connected. For more information, see Checking Hardware Connections.

The primary and secondary power supplies of the disk array have been powered on. For more information, see Powering On a Server.

The Solaris version must be 5.10 Generic_150400-11. For details, see the follow-up procedure in Installing a Solaris 10 OS Using a Quick InstallationDVD.

One NIC must have only one IP address. For details, see How to Check Whether an NIC Has Multiple IP Addresses on Solaris and How to DeleteExcess IP Addresses of an NIC on Solaris

Ensure that the current OS does not use the ID of a U2000 user. For details, see How to Check and Change an OS User ID.

IP addresses have been assigned to disk array controllers if automatic disk array configuration by means of the OSSICMR is required.

For information about how to configure the SC IP of OceanStor S3900 disk array, see Setting the SC IP Address for the OceanStor S3900Disk Array.



For information about how to configure the SC IP of OceanStor S2600 disk array, see Setting the SC IP Address for the OceanStor S2600Disk Array.

For information about how to configure the SC IP of StorageTek 2540 disk array, see Setting the SC IP Address for the StorageTek 2540Disk Array.

For information about how to configure the SC IP of OceanStor S3100 disk array, see Configuring the SC IP Address of the OceanStor S3100 DiskArray.

If the U2000 is installed using software packages, the installation software must have been prepared. For more information, see Preparing SoftwarePackages.

Context

NOTICE:

Configure the OSs on the servers of the primary and secondary sites.Do not adjust the size of the CLI when performing the operations described in this topic.After the system is preconfigured, the command association function using the up and down arrows is disabled in the Solaris operating system.

The topic mainly describes the following configurations:

Set the shared system memory parameters: Modify the /etc/system file to set the shared system memory parameters.

Configure a disk array: Configuring a disk array automatically verifies that the disk array is connected and then it mounts the disk array onthe server.

Modify service network settings, including the server IP address, server host name, and IPMP feature.

Install the Veritas software and patches.

Configure disk mirroring.

Install Sysbase software.

Establish the database server and database backup server.

A scenario where the disk array is mounted is mainly described in this section, while a scenario where a disk array is not mounted is also addressed.

Procedure

1. Log in to the OS as user root.

2. Start copying software.

Mode one: If installation is performed using a software package, do as follows:Run the following commands to switch to the directory where the pre_install.sh file is stored and run the pre_install.sh file to startcopying software:# cd /opt/install/engineering/OSSICMR# ./pre_install.sh

NOTE:If the following information is displayed, enter 1 as prompted to copy the Veritas software.

The required OS patch is installed.============================================= System pre-configuration=============================================......=============================================Skip copy Database software ...If you want to install the NMS high availability system (Veritas hot standby), enter "1" to copy the Veritas software.If you do not want to install the NMS high availability system (Veritas hot standby), enter "2".

The preceding information is displayed because the High Availability System (Solaris) OS is installed using a common installation DVD.

It takes approximately one minutes to complete system pre-configuration.The pre-configuration includes copying the OSSICMR.A message similar to the following will be displayed:============================================= System pre-configuration =============================================

Copying the OSS ICMR directory to /opt/OSSICMR... Finished

=============================================Configuring OSS ICMR... Finished

=============================================Skipping the database software copying task...

============================================= * OSS Software Lib Directory: /opt/install/

Processing the Veritas installation package... Veritas already exists in /opt/vrtstmp. Skipping the Veritas installation package...Checking the Veritas patch installation package...



Processing Veritas software's patches...

Finished

Mode two: If installation is performed using a DVD, do as follows:

a. Insert the installation DVD of the U2000 server software into the server DVD-ROM.

b. Run the following commands to switch to the directory where the pre_install.sh file is stored and run the pre_install.sh file tostart copying software:

If the server model is Netra T4-1/Oracle T4-1/T5220/M4000/M5000, run the following command:# bash# cd /cdrom/cdrom0/engineering/OSSICMR# . ./pre_install.sh

If the server model is Oracle T4-2, run the following command:# bash# cd /cdrom/cdrom1/engineering/OSSICMR# . ./pre_install.sh

NOTE:You must run the bash command in the root directory before navigating to the OSSICMR directory. Otherwise, the DVD-ROM cannotautomatically eject the DVD.There must be a space between the dot (.) and the command ./pre_install.sh.

It takes approximately one minutes to complete system pre-configuration.The pre-configuration includes copying the OSSICMR.A message similar to the following will be displayed:============================================= System pre-configuration =============================================

Copying the OSS Engineering directory to /opt/install... Finished

=============================================

Copying the OSS ICMR directory to /opt/OSSICMR... Finished

=============================================Configuring OSS ICMR... Finished

============================================= Please insert the database installation DVD.Can not find database installation package. Please choose your operation: 1. Please insert the installation DVD #4 2. Extract database compress package to /opt/install 3. Input another path that contains database installation package 4. Skip the installation of database if you had installed or you choose slave installation

c. The DVD-ROM will eject the installation DVD for the U2000 server software after configuration is complete. Insert theinstallation DVD for the database software into the server DVD-ROM.Input 1, click Enter. The system will automatically copy the database installation software to the server.A message similar to the following will be displayed:Deal with Database installation file to /opt/install ...> Finish

============================================= * OSS Software Lib Directory : /opt/install

Processing the Veritas installation package... Failed to find the Veritas installation file. Perform one of the following operations:1. Insert the Veritas DVD and press Enter.2. Enter 2 if you do not want to install the OSS high availability system (Veritas hot standby), and press Enter.3. Extract the Veritas compress package to /opt/vrtstmp and press Enter.4. Enter another path that contains the Veritas installation file and press Enter.

d. The DVD-ROM automatically ejects the installation DVD of the database software. Insert the installation DVD of the Veritassoftware into the DVD-ROM of the server, and then input 1, press Enter. The process takes about five minutes. Wait patiently.A message similar to the following will be displayed:

NOTE:If the following information is displayed, enter 1 as prompted to copy the Veritas software.

The required OS patch is installed.============================================= System pre-configuration=============================================......=============================================Skip copy Database software ...If you want to install the NMS high availability system (Veritas hot standby), enter "1" to copy the Veritas software.



If you do not want to install the NMS high availability system (Veritas hot standby), enter "2".


Processing Veritas installation file to /opt/vrtstmp...FinishedChecking the Veritas patch installation package...Fail to find Veritas patch package file.Please insert the Veritas patch DVD or extract Veritas patch compress package to /opt/vrtstmp, or input another path that contains Veritas patch file , then press Enter to continue

e. The DVD-ROM automatically ejects the installation DVD of the Veritas software. Insert the installation DVD of system patchesinto the DVD-ROM of the server, and then press Enter.A message similar to the following will be displayed:Processing with Veritas software's patches... Deal with Veritas software's patches finished Finished

3. Optional: Perform this step when the disk array is configured for the first time. Otherwise, skip this step.

NOTE:The automatic configuration scripts of OSSICMR support only the disk arrays with the following configurations:

12 x 600 GB OceanStor S39006 x 300 GB OceanStor S26006 x 300 GB StorageTek 2540

If a disk array whose configurations are out of the preceding range, contact Huawei technical support engineers.

The OceanStor S3100 disk array does not support automatic script configuration. For details about how to configure the OceanStor S3100 disk array, see Using theManager Suite to Configure the OceanStor S3100 Disk Array.

To configure the OceanStor S3900 disk array using the automatic configuration script, perform the following operations:

a. Run the following commands to switch to the directory where the script for configuring the OceanStor S3900 disk array is stored, and runthe AutoSetupS3900.sh script to start configuring the OceanStor S3900 disk array:# cd /opt/OSSICMR/bin/array# ./AutoSetupS3900.sh

A message similar to the following will be displayed: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.

b. Enter the IP address of the primary controller of the disk array, such as 10.9.1.10 and press Enter.A message similar to the following will be displayed:Please enter the admin user password of the array:

c. Enter the user password of the disk array and press Enter. It is normal that no echo information is displayed after the user password isentered.The default user name and password of the system administrator are admin and Admin@storage. Changing the password afteryou 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]

d. Enter y and press Enter. The script clears the configurations of the disk array.A message similar to the following will be displayed: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 isconfigured successfully. If the configuration fails again, use the ISM to configure the OceanStor S3900 disk array. For more information, see Configuring theOceanStor S3900 Disk Array by Using the ISM.

e. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

f. Press Enter to restart the OS.

g. After the OS restarts, log in to the OS as user root.

NOTE:

If the following alarm information is generated, labels are not configured for the disk array. Ignore the alarm information and continue.



Oct 10 17:00:00 Primaster scsi: WARNING: /pci@400/pci@1/pci@0/pci@6/SUNW,qlc@0,1/fp@0,0/ssd@w2018200bc798692b,0 (ssd1):Oct 10 17:00:00 Primaster Corrupt label; wrong magic numberOct 10 17:00:00 Primaster scsi: WARNING: /pci@400/pci@1/pci@0/pci@6/SUNW,qlc@0,1/fp@0,0/ssd@w2018200bc798692b,0 (ssd1):Oct 10 17:00:00 Primaster Corrupt label; wrong magic numberOct 10 17:00:00 Primaster scsi: WARNING: /pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0/ssd@w2008200bc798692b,0 (ssd0):Oct 10 17:00:00 Primaster Corrupt label; wrong magic numberOct 10 17:00:00 Primaster scsi: WARNING: /pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0/ssd@w2008200bc798692b,0 (ssd0):Oct 10 17:00:00 Primaster Corrupt label; wrong magic number

h. Run the following command to scan the LUN that maps the OceanStor S3900 disk array:# formatThe following message will be displayed:Searching for disks...done

c1t2200662233556653d0: configured with capacity of 999.97GBc2t2210662233556653d0: configured with capacity of 999.97GB

AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c1t2200662233556653d0 <HUAWEI-S3900-M200-2 cyl 63998 alt 2 hd 128 sec 256> /pci@2,600000/SUNW,qlc@0/fp@0,0/ssd@w20100022a10b0c81,0 3. c2t2210662233556653d0 <HUAWEI-S3900-M200-2 cyl 63998 alt 2 hd 128 sec 256> /pci@3,700000/SUNW,qlc@0/fp@0,0/ssd@w20000022a10b0c81,0Specify disk (enter its number):

NOTE:The displayed disk size varies according to the actual size of the disk.The disk identified with < HUAWEI-S3900- .... > indicates the LUN that maps the OceanStor S3900 disk array.The scanned number of disks is the product of: the number of local disks, the number of LUNs that map the OceanStor S3900 disk array, and the numberof fiber paths. After the MPxIO multipathing is enabled, the number of disks scanned by the format command is equal to the number of LUNs that mapthe OceanStor S3900 disk array.If the disk that maps the OceanStor S3900 has been located, press CTRL+C to stop the scanning.If the disks that map the OceanStor S3900 disk array fail to be scanned, press CTRL+C to stop the scanning, run the devfsadm -C command first and theformat command to scan the required disks. If the disks still cannot be scanned, ensure that the fiber is properly connected.

To configure the OceanStor S2600 disk array by using an automatic configuration script, perform the following operations:

a. Run the following commands to switch to the directory where the script for configuring the OceanStor S2600 disk array is stored, and runthe AutoSetupS2600.sh script to start configuring the OceanStor S2600 disk array:# cd /opt/OSSICMR/bin/array# ./AutoSetupS2600.sh

A message similar to the following will be displayed:Please enter the IP address of array controller:

b. Enter the IP address of the primary controller of the disk array, such as 10.9.1.10 and press Enter.A message similar to the following will be displayed:Please enter the admin user password of the array :

c. Enter the user password of the disk array and press Enter. It is normal that no echo information is displayed after the user password isentered. The default user name and password of the system administrator are admin and 123456..A message similar to the following will be displayed:============= Excute this script at: Tue Jan 10 23:51:35 CST 2012 =============---------------------------------------------------------------------------------------------- Configure OceanStor S2600 DiskArray --------------------------- !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! -------------------- This script will destroy all the data of the array!! ----------------------------------------------------------------------------------------Are you sure to continue? [y/n]

d. Enter y and press Enter. The script clears the configurations of the disk array.A message similar to the following will be displayed:Configured the disk array successfully.

NOTE:Wait about five minutes. The configuration result will be displayed. If the configuration fails, run the AutoSetupS2600.sh script again. If the configuration failsagain, use the ISM to configure the OceanStor S2600 disk array. For more information, see Configuring the OceanStor S2600 Disk Array by Using the ISM.

e. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

f. Press Enter to restart the OS.

g. After the OS restarts, log in to the OS as user root.

h. Run the following command to scan the LUN that maps the OceanStor S2600 disk array:# formatThe following message will be displayed:Searching for disks...done

c1t2200662233556653d0: configured with capacity of 999.97 GBc2t2210662233556653d0: configured with capacity of 999.97 GB



AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SEAGATE-ST973402SSUN72G-0400 cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c1t2200662233556653d0 <HUAWEI-S2600-1 cyl 19198 alt 2 hd 64 sec 256> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0/ssd@w2200662233556653,0 3. c2t2210662233556653d0 <HUAWEI-S2600-1 cyl 19198 alt 2 hd 64 sec 256> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0/ssd@w2210662233556653,0Specify disk (enter its number):

NOTE:The displayed disk size varies according to the actual size of the disk.The disk identified with < HUAWEI-S2600-1 .... > indicates the LUN that maps the OceanStor S2600 disk array.The scanned number of disks is the product of: the number of local disks, the number of LUNs that map the OceanStor S2600 disk array, and the numberof fiber paths. After the MPxIO multipathing is enabled, the number of disks scanned by the format command is equal to the number of LUNs that mapthe OceanStor S2600 disk array.If the disk that maps the OceanStor S3900 has been located, press CTRL+C to stop the scanning.If the disks that map the OceanStor S2600 disk array fail to be scanned, press CTRL+C to stop the scanning, run the devfsadm -C command first and theformat command to scan the required disks. If the disks still cannot be scanned, ensure that the fiber is properly connected.

To configure the StorageTek 2540 disk array using the automatic configuration script, perform the following operations:

a. Install the CAM. For details, see Step 1 in Configuring the StorageTek 2540 Disk Array Through the Web Browser.

b. Run the following commands to navigate to the directory where the script for configuring the StorageTek 2540 disk array is stored. Runthe AutoSetup2540.sh file to start configuring the StorageTek 2540 disk array:# cd /opt/OSSICMR/bin/array# ./AutoSetup2540.sh dmp

A message similar to the following will be displayed:Please input "y" to go on or "n" to quit:

c. Enter y and press Enter.A message similar to the following will be displayed:Please input the IP address of the array:

d. Enter the IP address of a disk array controller, such as the IP address of the primary controller 10.9.1.10, and press Enter.A message similar to the following will be displayed:Please input the password of user root...Type your password:

e. Enter the password of user root of the OS and press Enter. The default password is root.A message similar to the following will be displayed:...Succeeded to configure disk array!...

NOTE:Wait about 10 minutes. The result of the configuration will be displayed. If the configuration fails, run the AutoSetup2540.sh script and configure the StorageTek2540 disk array again. If the configuration fails again, configure the StorageTek 2540 disk array through the Web browser. For more information, see Configuringthe StorageTek 2540 Disk Array Through the Web Browser.

f. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

g. Press Enter to restart the OS.

h. After the OS restarts, log in to the OS as user root.

4. Optional: f the system preconfiguration terminates, you must perform the preconfiguration again, which consumes time. To prevent systempreconfiguration termination caused by an unexpected disconnection between the PC or laptop and the server, the GUI software VNC isrecommended for remotely logging in to the SUSE Linux operating system as the root user. For details about the procedure, see Configure the VNCservice as the root user.

NOTE:After logging in to the OS GUI, right-click and choose Open Terminal from the shortcut menu. You can perform the follow-up system preconfiguration in the displayed CLI.

5. Run the following commands to switch to the directory where the OSSICMR is stored, and run the install.sh script to start the OSSICMR for systempre-configuration:

NOTE:

If the system has been preconfigured and the IPMP has been configured for the network or an incorrect host name or IP address is entered during OS configuration and thenetwork need to be reconfigured, perform the following operations to reconfigure the OS:

a. Press Ctrl+C to stop the program for configuring the OS.b. Run the following commands to restart the OS and clear the network configuration environment:

# sync;sync;sync;sync# shutdown -y -g0 -i6

c. Run the following commands to reconfigure the OS:# cd /opt/OSSICMR/bin



# ./install.sh -rThe information displayed is different from that displayed after the install.sh script is run for the first time. Perform operations by following the prompts and payattention to the configuration items whose configuration results are Failed.

# cd /opt/OSSICMR/bin# ./install.sh -r

NOTE:

If the following information is displayed, enter 2 and select High Availability System (Solaris). ======= Installation Type =======Select the installation type. The installation wizard will guide you through the rest of the installation process according to the installation type you selected. 1. Single-Server System (Solaris) 2. High Availability System (Solaris) Select[1]:


A message similar to the following will be displayed:======OS's language======

The current OS language is English, choose a correct language to set OS: 1.Chinese 2.English please select[2]:

6. Enter 2, and press Enter to select the English OS.A message similar to the following will be displayed: ======= 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]:

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 defaultinstallation path is recommended. When using a self-defined path, ensure that the path has enough space for installation.

A message similar to the following will be displayed:

NOTE:If the database has been installed on the system, a message is displayed asking you whether to reuse database information.If the database has not been installed on the system, enter the U2000 installation path.

If need to reuse the sybase

1. yes 2. no

Select[1]:

Choose whether to reuse the database as required.

To reuse the database, perform the following operations:

a. If the database must be reused, enter 1 and press Enter.A message similar to the following will be displayed:Please input the database administrator account[sa] :

b. Enter the user name of the database administrator, such as sa. Press Enter.A message similar to the following will be displayed: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 asdbadmin.

c. Enter the password of the database administrator and press Enter. The system automatically checks whether the password iscorrect. If the password is incorrect, perform this step again. If the password is correct, information similar to the following isdisplayed:==== OSS path =======

Enter the OSS path in which to install the OSS software.

Enter the path and press Enter, or press Enter to use the default directory[/opt/oss]:

If the database does not need to be used, enter 2 and press Enter. The system automatically checks whether the current database installationpath 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, informationsimilar to the following is displayed:



==== OSS path =======



A message similar to the following will be displayed:==== OSS path =======



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 installationpath is recommended. When using a self-defined path, ensure that the path has enough space for installation.

A message similar to the following will be displayed:Trying to backup the current network configurations...

Please input the system ip[10.9.1.1]:>

9. Set IP addresses according to different NIC schemes.

NOTE:If an incorrect characters is entered and the character cannot be deleted after Backspace is pressed, hold downCtrl+Backspace to delete the characters and then enter a correctcharacter.

NIC Scheme Operation

Single scheme 1. Enter a planned system IP address, for example, 10.9.1.1. Then, press Enter.Please input the system hostname[primaster]:

2. Enter a planned host name. For example, enter Primaster when configuring the OS of the primary site or Secmaster whenconfiguring the OS of the secondary site. Here, configuration of the primary site is taken as an example. Then, pressEnter.

NOTICE:To ensure that the NMS can run properly, host name planning must comply with the following rules and restrictions:

The host name of the U2000 server must be unique on the network.

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 to9) and hyphen (-).The first character must be a letter and the last character cannot be a hyphen.The host name cannot contain --.The host name must be case-sensitive.The host name cannot be empty or contain spaces.The host name cannot contain only one character.The host name cannot be any of the following keywords in the high availability system.action false keylist static after firm local stop requires remoteclustersystem group resource global Start str temp set heartbeat ArgListValuesSystem Group boolean hard Name soft before online condition MonitorOnlyremote start cluster event VCShm type Path offline Signaled HostMonitorProbed state Cluster IState int Type State VCShmg NameRule ConfidenceLevel

Please input the system netmask[255.255.254.0]:3. Enter a planned subnet mask. Then, press Enter.

Please confirm the following configurations4. Enter y to confirm configurations. Then, press Enter. To modify a configuration, enter n.

Will the heartbeat network reuse the system IP address[y/n]?5. Enter y to set the system network IP address as the heartbeat network IP address. Then, press Enter.

Do you want to configure IPMP for the heartbeat network service[y/n]?6. Enter n to choose not to configure IPMP. Then, press Enter.

Will the replication network reuse the heartbeat network[y/n]?7. Enter y to reuse the heartbeat network as the replication network. Then, press Enter.

Will the OSS application network reuse the network[y/n]?8. Enter y to reuse the network as the NMS application network. Then, press Enter.

======= Select the network type ======= Please choose one network type to reuse 1. Reuse the System network 2. Reuse the Heartbeat network Select[1]:

9. Enter 1 to reuse network configurations of the system. Then, press Enter.

Double-NIC scheme(without IPMP)

1. Enter a planned system IP address, for example, 10.9.1.1. Then, press Enter.Please input the system hostname[primaster]:


NOTICE:



To ensure that the NMS can run properly, host name planning must comply with the following rules and restrictions:


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 to9) and hyphen (-).The first character must be a letter and the last character cannot be a hyphen.The host name cannot contain --.The host name must be case-sensitive.The host name cannot be empty or contain spaces.The host name cannot contain only one character.The host name cannot be any of the following keywords in the high availability system.action false keylist static after firm local stop requires remoteclustersystem group resource global Start str temp set heartbeat ArgListValuesSystem Group boolean hard Name soft before online condition MonitorOnlyremote start cluster event VCShm type Path offline Signaled HostMonitorProbed state Cluster IState int Type State VCShmg NameRule ConfidenceLevel



Will the heartbeat network reuse the system IP address[y/n]?5. Enter n to choose not to reuse the system network as the heartbeat network. Then, press Enter.

Please select a NIC to be used for the master NIC for the heartbeat network service ip [1,2,...]:6. Enter the serial number of an idle NIC. For example, 2. Then, press Enter.

Please input the heartbeat network service ip[]:7. Enter a planned service IP address of the heartbeat network. Then, press Enter.

Please input the hostname for the heartbeat network service ip[HBService]:8. Press Enter.

Please input the netmask for the heartbeat network service ip[255.255.255.0]:9. Enter a planned subnet mask. Then, press Enter.

Do you want to configure a router for the heartbeat IP address?Please input your choice 1. yes 2. no

10. Enter 1 to configure route for the heartbeat IP address. Then, press Enter.Please input the heart beat network IP address for the remote host[]:>

11. Enter the network segment address for heartbeat on the peer site. Then, press Enter.Please input the heart beat netmask for the remote host[]:>

12. Enter the subnet mask for heartbeat on the peer site. Then, press Enter.Please input the heart beat network gateway IP address for the remote host[]:>

13. Enter the gateway IP address for heartbeat. Then, press Enter.Please confirm the following configurations

14. Enter y to confirm configurations. Then, press Enter. To modify a configuration, enter n.Do you want to configure the heartbeat network service as IPMP[y/n]?

15. Enter n to choose not to configure IPMP. Then, press Enter.Will the replication network reuse the heartbeat network[y/n]?

16. Enter y to reuse the heartbeat network as the replication network. Then, press Enter.Will the OSS application network reuse the network[y/n]?

17. Enter y to reuse the network as the NMS application network. Then, press Enter.======= Select the network type ======= Please choose one network type to reuse 1. Reuse the System network 2. Reuse the Heartbeat network Select[1]:

18. Enter 1, NMS application network reuse the System IP. Then, press Enter.

Double-NIC scheme(with IPMP)

1. Enter a planned system IP address, for example, 10.9.1.1. Then, press Enter.Please input the system hostname[primaster]:


NOTICE:To ensure that the NMS can run properly, host name planning must comply with the following rules and restrictions:


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 to9) and hyphen (-).The first character must be a letter and the last character cannot be a hyphen.The host name cannot contain --.The host name must be case-sensitive.The host name cannot be empty or contain spaces.The host name cannot contain only one character.The host name cannot be any of the following keywords in the high availability system.action false keylist static after firm local stop requires remoteclustersystem group resource global Start str temp set heartbeat ArgListValuesSystem Group boolean hard Name soft before online condition MonitorOnly



remote start cluster event VCShm type Path offline Signaled HostMonitorProbed state Cluster IState int Type State VCShmg NameRule ConfidenceLevel



Will the heartbeat network reuse the system IP address[y/n]?5. Enter y to set the system network IP address as the heartbeat network IP address. Then, press Enter.

Do you want to configure IPMP for the heartbeat network service[y/n]?6. Enter y to configure IPMP for the heartbeat network. Then, press Enter.

Please input the base ip for the heartbeat master NIC[]:7. Enter a planned IP address for the active NIC of the heartbeat network. Then, press Enter.

Please input the hostname for the heartbeat master base ip[HBMaster]:8. Press Enter.

Please input the netmask for the heartbeat master base ip[255.255.255.0]:9. Enter a planned subnet mask.

Please confirm the following configurations10. Enter y. Then, press Enter. To modify a configuration, enter n.

Please select a NIC to be used for the standby NIC for the heartbeat network service ip [1,2,...]:11. Enter a serial number for an idle NIC. For example, 2. Then, press Enter.

Please input the base ip for the heartbeat standby NIC[]:12. Enter a planned IP address for the standby NIC of the heartbeat network. Then, press Enter.

Please input the hostname for the heartbeat standby base ip[HBSlave]:13. Press Enter.

Please input the netmask for the heartbeat standby base ip[255.255.255.0]:14. Enter a planned subnet mask. Then, press Enter.

Please confirm the following configurations15. Enter y. Then, press Enter. To modify a configuration, enter n.

Will the replication network reuse the heartbeat network[y/n]?16. Enter y to reuse the heartbeat network as the replication network. Then, press Enter.

Will the OSS application network reuse the network[y/n]?17. Enter y to reuse the network as the NMS application network. Then, press Enter.

======= Select the network type ======= Please choose one network type to reuse 1. Reuse the System network 2. Reuse the Heartbeat network Select[1]:

18. Enter 1 to reuse network configurations of the system. Then, press Enter.

Other schemes Contact Huawei engineers for scheme design.

After the network configuration is compete, information similar to the following is displayed. It takes about 45 minutes to complete the process.Please wait patiently. Modifying the system parameters................................................................................ Installing veritas volume manager................................................................................ Installing veritas extra patches...................................................................................................................

The system restarts twice automatically.

10. After the system is restarted, the installation continues. Run the following command to view the installation progress. Pre-configuring the U2000takes about 120 minutes:# tail -f /var/ICMR/install.log

A message similar to the following will be displayed: Set OS's language............................................... Modifying the system parameters............................................... Installing veritas volume manager................................................... Installing veritas extra patches.................................................. Encapsuling diskgroup............................................................... Create volumesRC It will take 3-5 minute(s) to execute this task. Please wait............................................................................................ Mirroring disksRC It will take 60-120 minute(s) to execute this task. Please wait............................................................................................ Configuring the vcs It will take 3-5 minute(s) to execute this task. Please wait.... Install SYBASE Software........................................... Build database server and backup server...........................................................................................................

All operations defined in the task flow have been completed.All operation logs are saved in: /var/ICMR/ICMR_20130325024631.log

If All operations defined in the task flow have been completed is displayed, the configuration is successful. Press Ctrl+C to stop viewing logs.If Failed is returned, the configuration fails. In this case, press Ctrl+C to stop viewing logs, save the operation log, and contact Huawei engineersfor fault locating.

11. Do as follows to check the Veritas version and patch information:

a. To check the VxVM version, run the following command:



# pkginfo -l VRTSvxvmIf the VxVM version is correct, information similar to the following is displayed: PKGINST: VRTSvxvm NAME: Binaries for VERITAS Volume Manager by Symantec CATEGORY: system ARCH: sparc VERSION: 6.0.100.000,REV=08.01.2012.11.13 BASEDIR: / VENDOR: Symantec Corporation DESC: Virtual Disk Subsystem PSTAMP: 6.0.300.100-2013-09-02-148490-03 INSTDATE: Mar 10 2013 20:27 HOTLINE: http://www.symantec.com/business/support/assistance_care.jsp STATUS: completely installed FILES: 854 installed pathnames 41 shared pathnames 118 directories 359 executables 421772 blocks used (approx)

b. To check the VCS version, run the following command:# pkginfo -l VRTSvcsIf the VCS version is correct, information similar to the following is displayed: PKGINST: VRTSvcs NAME: Veritas Cluster Server by Symantec CATEGORY: system ARCH: sparc VERSION: 6.0.100.000 BASEDIR: / VENDOR: Symantec Corporation DESC: Veritas Cluster Server by Symantec PSTAMP: 6.0.300.000-GA-2013-01-17-16.00.00 INSTDATE: Mar 10 2013 20:19 STATUS: completely installed FILES: 280 installed pathnames 27 shared pathnames 56 directories 117 executables 450908 blocks used (approx)

Pay attention to information to the right of PSTAMP.

PSTAMP information for the vxvm software version: 6.0.300.000-2013-01-17-148490-02

PSTAMP information for the vcs software version: 6.0.300.000-GA-2013-01-17-16.00.00

If the information displayed to the right of PSTAMP does not meet the preceding conditions, install Veritas software or contact Huawei engineers.


1.3.5.3 Starting the U2000 Installation ProgramThis topic describes how to start the U2000 installation program. Install the U2000 software through the GUI (recommended) or CLI. If the GUI cannot belogged in to, install the U2000 software through the CLI. GUI is short for graphical user interface and CLI for command line interface.

Installing the U2000 on the GUIThis topic describes how to install the U2000 software on the GUI. In comparison with the CLI, the installation on the GUI is clear and easy to operate.It is recommended that you install the U2000 on the GUI if you are not familiar with the common commands of the Solaris OS.

Installing the U2000 Through the CLIThis topic describes how to install the U2000 software through the CLI. Installation engineers are recommended to install the U2000 through the CLI ifthey cannot log in to the GUI.


1.3.5.3.1 Installing the U2000 on the GUIThis topic describes how to install the U2000 software on the GUI. In comparison with the CLI, the installation on the GUI is clear and easy to operate. It isrecommended that you install the U2000 on the GUI if you are not familiar with the common commands of the Solaris OS.

Prerequisites

If the U2000 is not pre-configured, see Pre-configuring the U2000. The U2000 will fail to install if it is not pre-configured.

Ensure that the size of the installation directory of the server meets the requirement. For example, if all domains need to be deployed, the remainingspace of the installation directory must be larger than 30 GB. If the server is configured with only two 73 GB hard disks, deploying only a singledomain is recommended.

NOTE:Run the df -hk /opt command to view the remaining space of the /opt directory.



The remote desktop control software is ready. For details, see How to Use the VNC to Remotely Access a Workstation.

At least one NIC has been started.

NOTE:Run the ifconfig -a command to view the NIC running status. Ensure that the NIC status is UP and RUNNING.

If the NIC running status is abnormal, perform the following operations:

Check network cable connections on the NIC. Ensure that the network cables are connected properly.Run the ifconfig NIC name up to enable the specified NIC.

Verify that the database has been started. For details about how to check whether the database has been started, see How to Verify That the SybaseDatabase Is Running. If the database has not been started, see How to Start the Sybase Database Service to start it.

Context

NOTICE:If the server on which the steps described in this topic must be performed is not specified, perform the steps on the primary and secondary sites.

Procedure

1. Log in to the server OS as user root using the remote desktop control software. For details, see How to Use the VNC to Remotely Access aWorkstation.

2. On the desktop, right-click and choose Open Terminal from the shortcut menu to display a CLI.

3. Run the following command to temporarily freeze the AppService resource group:# hagrp -freeze AppService

4. Run the following command to check whether the AppService resource group has been frozen:# hastatus -sum

If information similar to the following is displayed, the AppService resource group has been frozen:-- SYSTEM STATE-- System State Frozen

A mastar-22450 RUNNING 0

-- GROUP STATE-- Group System Probed AutoDisabled State

B AppService mastar-22450 Y N PARTIAL B ClusterService mastar-22450 Y N ONLINE B VVRService mastar-22450 Y N OFFLINE

-- GROUPS FROZEN-- Group...

5. Run the following command to check whether the system character set is correct:# locale -a

If the following message is displayed, the character set of Solaris OS is correct. Otherwise, reinstall the OS.Cen_US.UTF-8

6. Run the following commands to go to the path where the install.sh file is stored and run the install.sh file:# cd /opt/install# ./install.sh

A message similar to the following will be displayed:Backup the /opt/OSSENGR.Copying the JRE to /opt/OSSJRE...FinishedCopying the installation files to /opt/OSSENGR...FinishedStarting 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.

7. Click I accept the terms, and click Next to continue. The Select Language dialog box will be displayed.

NOTE: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. Forexample, /opt/install.

8. Select the language according to the conditions at your site, such as English. Then, click Next. The Select Installation Type dialog box will bedisplayed.



NOTE:If Automatically configure OSS license file during installation needs to be selected, upload the license file to the server before selecting it.

9. If the License file has been uploaded to the server, click Next. Otherwise, clear the selection of Automatically configure OSS license file duringinstallation, and then click Next. The Configure Database dialog box will be displayed.

The following table shows the basic settings of the database server and NMS database user.

Parameter Description

Server Address The default value is the IP address of the current OS.

Server Name The default value is DBSVR.

Server Port The default value is 4100.

Administrator Password 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 forthe newly installed database. The default value is Changeme_123.If a database is reused in the system preconfiguration procedure and the database administrator passwordmeet 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 passworddoes not meet the following requirements, change the password. For details, see How to Change the saUser Password for the Sybase Database If the U2000 Is Not Installed.The password of the database administrator at the primary site must be consistent with that at thesecondary site.

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:

At least one lower-case letter



At least one upper-case letterAt least one digit

At least one special character ~@#^*-_+[{}]:./?

Other special characters are not supported. Do not include other special characters, such as ()|<>&`!$\"%'=;,space in passwords.

The password cannot be the same as the user name written in either the forward or backward format.

The default value is Changeme_123 .

OSS Database User Password The OSS database user password must meet the requirements:The password contains a minimum of eight characters and a maximum of 30 characters.The password must contain at least four of the following combinations:

At least one lower-case letterAt least one upper-case letterAt least one digitAt least one special character ~@#^*-_+[{}]:./?Other special characters are not supported. Do not include other special characters, such as ()|<>&`!$\"%'=;,space in passwords.

The password cannot be the same as the user name written in either the forward or backward format.Set a new password for OSS database user. For example, Changeme_123 .

NOTICE:The password of the database user at the primary site must be consistent with that at the secondary site.Plan and enter a new password according to the preceding password rules to ensure system security. Make a note ofyour password and keep it in a safe place. Do not share your password with anyone.

Confirm OSS Database User Password Confirms the password of the NMS database user. If the database user password has been changed, enter the newpassword.

10. Click Next. The Configure Server dialog box will be displayed.

11. 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 displayAccess domain alone. Select the domain where instances need to be deployed based on the managed devices. By default, an instance is deployed for every component in theselected domain. Components instead of deployment instances are by default installed for the deployment domains that are not selected. Selecting all the displayed domains isrecommended. After a domain is selected, deploying instances for the domain is not required. The instances that are deployed by default occupy database space and the defaultstartup of processes occupies resources. To add other domains, upload and decompress the corresponding packages and perform the installation again. Software packages for thetransport and IP components must be selected so as to manage PTN 6900 series NEs.

12. Click Next. The Preinstallation Check will be displayed.

NOTE:

a. If the uploaded and decompressed package involves the transport domain, the Version Style dialog box is displayed.

The following is an example of the differences between the two styles:

For the Default style, alarms come in the following descending order of severity: Critical, Major, Minor, and Warning.For the North American version style, alarms come in the following descending order of severity: Critical, Major, Minor, Not Alarmed, and NotReported.

b. Click Next. The Version Timeslot Mode will be displayed.c. Select the time slot mode as required, such as Sequential mode. The Sequential mode, a timeslot numbering policy recommended by the ITU-T.

13. Click Next. The installation information will be displayed.

14. Click Next. A progress bar will be displayed. The time required for the installation depends on the number of components to be installed and theserver configuration. The entire process takes about 90 minutes. Wait patiently.

NOTE: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 installingthe 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 inred. The U2000 can manage the maximum number of NEs as supported by the server model.

If a message indicating an installation failure or interruption is displayed during installation, see How do I solve the problem where a failure message is displayedduring the installation or the installation is abnormally interrupted to solve the problem.

The system will display a prompt indicating that installation was successfully completed.

15. Click Finish to complete the U2000 installation.

16. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

Parent topic: Starting the U2000 Installation Program

1.3.5.3.2 Installing the U2000 Through the CLIThis topic describes how to install the U2000 software through the CLI. Installation engineers are recommended to install the U2000 through the CLI if theycannot log in to the GUI.

Prerequisites

If the U2000 is not pre-configured, see Pre-configuring the U2000. The U2000 will fail to install if it is not pre-configured.

Ensure that the size of the installation directory of the server meets the requirement. For example, if all domains need to be deployed, the remainingspace of the installation directory must be larger than 30 GB. If the server is configured with only two 73 GB hard disks, deploying only a singledomain is recommended.



NOTE:Run the df -hk /opt command to view the remaining space of the /opt directory.

At least one NIC has been started.

NOTE:Run the ifconfig -a command to view the NIC running status. Ensure that the NIC status is UP and RUNNING.

If the NIC running status is abnormal, perform the following operations:

Check network cable connections on the NIC. Ensure that the network cables are connected properly.Run the ifconfig NIC name up to enable the specified NIC.

Verify that the database has been started. For details about how to check whether the database has been started, see How to Verify That the SybaseDatabase Is Running. If the database has not been started, see How to Start the Sybase Database Service to start it.

Context

NOTICE:If the server on which the steps described in this topic must be performed is not specified, perform the steps on the primary and secondary sites.

After a CLI is opened, modify the CLI attributes to prevent garbled images caused by the issue that the size of the output character is larger than the screenwidth. 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 aftercommands are executed.

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.

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

1. Log in to the OS of the server as user root.

2. Run the following command to temporarily freeze the AppService resource group:# hagrp -freeze AppService

3. Run the following command to check whether the AppService resource group has been frozen:# hastatus -sum

If information similar to the following is displayed, the AppService resource group has been frozen:-- SYSTEM STATE-- System State Frozen

A mastar-22450 RUNNING 0

-- GROUP STATE-- Group System Probed AutoDisabled State

B AppService mastar-22450 Y N PARTIAL B ClusterService mastar-22450 Y N ONLINE B VVRService mastar-22450 Y N OFFLINE

-- GROUPS FROZEN-- Group...

4. Run the following command to verify that the character set of the system is correct:# locale -a


5. Run the following commands to switch to the path where the install.sh file is stored and run the install.sh script:# cd /opt/install# ./install.sh -cmd

A message similar to the following will be displayed:Copying the JRE to /opt/OSSJRE...FinishedCopying the installation files to /opt/OSSENGR...FinishedStarting the OSS engineering CMD installation server...

===============< Copyright Notice >===============Copyright Notice...



I accept these terms [y:Yes, n:No, n]:

NOTE:Read the terms of the software license agreement carefully. Enter y if the terms are accepted.

6. Enter y and press Enter.

NOTE: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. Forexample, /opt/install.

A message similar to the following will be displayed:Install [c:Cancel, <p:Previous, n:Next>, n]:

7. Enter n and press Enter.A message similar to the following will be displayed:===============< Language >===============

Language [1:Chinese, 2:English, 2]:

8. Enter 2 and then press Enter to select the English version.A message similar to the following will be displayed:Install [c:Cancel, <p:Previous, n:Next>, n]:

9. Enter n and press Enter.A message similar to the following will be displayed:===============< Configure the license file required for OSS (If no license file is available, enter "n" to continue). >===============Automatically configure the OSS license file during the installation[y:Yes, n:No, y]:

10. If the license file is available, enter y and press Enter. If the license file is not available, enter n and press Enter. Entering n and pressing Enter areused as an example.

NOTE:If y is entered, enter the license file path (including the file name) as prompted and press Enter.

A message similar to the following will be displayed:Install [c:Cancel, <p:Previous, n:Next>, n]:

11. Enter n and press Enter.A message similar to the following will be displayed:===============< Configure Database >===============Server Address:[10.9.1.1]:

12. Press Enter to use the default IP address.A message similar to the following will be displayed:===============< Configure Database >===============Server Address:[10.9.1.1]: Server Name:[DBSVR]Server Port:[4100]Administrator Password:[]:**********

13. Configure database parameters..A message similar to the following will be displayed:===============< Configure Database >===============Server Address:[10.9.1.1]: Server Name:[DBSVR]Server Port:[4100]Administrator Password:[]:**********OSS Database User Password:[]:**********Confirm OSS Database User Password:[]:**********Install [c: Cancel, <p:Previous, n:Next>, n]:

When configuring the information about the database service, you can press Ctrl+H to delete incorrectly entered information.

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 installeddatabase. The default value is Changeme_123.

If a database is reused in the system preconfiguration procedure and the database administrator password meet the followingrequirements, 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 thefollowing requirements, change the password. For details, see How to Change the sa User Password for the Sybase Database If theU2000 Is Not Installed.

The password of the database administrator at the primary site must be consistent with that at the secondary site.

NOTE:

The database administrator password must meet the requirements:

The password contains a minimum of eight characters and a maximum of 30 characters.



The password must contain at least four of the following combinations:

At least one lower-case letterAt least one upper-case letterAt least one digit




The default value is Changeme_123 .

The OSS database user password must meet the requirements:

The password contains a minimum of eight characters and a maximum of 30 characters.

The password must contain at least four of the following combinations:

At least one lower-case letter

At least one upper-case letter

At least one digit

At least one special character ~@#^*-_+[{}]:./?Other special characters are not supported. Do not include other special characters, such as ()|<>&`!$\"%'=;,space inpasswords.


Set a new password for OSS database user. For example, Changeme_123 .

NOTICE:

The password of the database user at the primary site must be consistent with that at the secondary site.Plan and enter a new password according to the preceding password rules to ensure system security. Make a note of yourpassword and keep it in a safe place. Do not share your password with anyone.

14. Enter n and press Enter.A message similar to the following will be displayed:===============< Deploy Server >===============

Server IP Address:[0:10.9.1.1, 0]:

15. Confirm the Server IP Address and then press Enter.A message similar to the following will be displayed:===============< Deploy Server >===============

Server IP Address:[0:10.9.1.1, 0]:Installation Path:[/opt/oss]

Install [c:Cancel, <p:Previous, n:Next>, n]:

16. Enter n and press Enter.A message similar to the following will be displayed:===============< 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 displayAccess domain alone. Select the domain where instances need to be deployed based on the managed devices. By default, an instance is deployed for every component in theselected domain. Components instead of deployment instances are by default installed for the deployment domains that are not selected. Selecting all the displayed domains isrecommended. After a domain is selected, deploying instances for the domain is not required. The instances that are deployed by default occupy database space and the defaultstartup of processes occupies resources. To add other domains, upload and decompress the corresponding packages and perform the installation again. Software packages for thetransport and IP components must be selected so as to manage PTN 6900 series NEs.

17. 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.A message similar to the following will be displayed:Install [c:Cancel, <p:Previous, n:Next>, n]:

NOTE:

a. If the uploaded and decompressed package involves the transport domain, choose for the Version Style and press Enter.

The following is an example of the differences between the two styles:

For the Default style, alarms come in the following descending order of severity: Critical, Major, Minor, and Warning.For the North American version style, alarms come in the following descending order of severity: Critical, Major, Minor, Not Alarmed, and NotReported.

b. Enter n and press Enter.c. Select the time slot mode as required, such as Sequential mode. The Sequential mode, a timeslot numbering policy recommended by the ITU-T.

18. Enter n and press Enter.



A message similar to the following will be displayed:===============< Preinstallation Check >===============

Check whether the "/opt/sybase" directory and the respective group are consistent with configurations in the global configuration file "sysconfigure_install.xml" ( OK )Check the validity of the hosts file in the /etc path ( OK )Check IP address settings for the OS ( OK )Check loopback IP address settings for the OS ( OK )Check the network configuration file interfaces in the Sybase database path /opt/sybase ( OK )Check whether a user can be added for the OS ( OK )Check whether the OSS user is normal ( OK )Check the maximum shared memory of the OS ( OK )Check the available space of the OS path ( OK )Check whether the backup service of the Sybase database has been started ( OK )Check that the user database is not occupied ( OK )Check database commands, such as isql, bcp, osql, and sqlplus ( OK )Check the Sybase version ( OK )

Install [c: Cancel, <p:Previous, n:Next>, n]:

19. Enter n and press Enter.A message similar to the following will be displayed:===============< Confirm Installation Information >===============... ... Install[c:Cancel,<p:Previous, n:Next>, n]:

20. Confirm that the installation information is correct, enter n and press Enter.A message similar to the following will be displayed:===============< Show Installation Progress >===============

Initializing the data model... Please wait.: 0%

NOTE: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 installingthe database must be greater than the maximum size to which the file is permitted to grow. If the disk space is insufficient, the system displays a prompt message inred. The management capability of the U2000 after the installation cannot reach the associated maximum value of this model.If a message indicating installation failure or abnormal interruption is displayed during installation, For details, see How do I solve the problem where a failuremessage is displayed during the installation or the installation is abnormally interrupted.

21. After the installation, the message similar to the following will be displayed:===============< Installation Completed >===============FinishThe U2000 has been installed in the directory /opt/oss....

22. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

Parent topic: Starting the U2000 Installation Program

1.3.6 Configuring a RouteThis topic describes how to use the MSuite to configure a route. Before connecting the primary and secondary sites, you must ensure that the heartbeat andreplication routes between the primary and secondary sites are reachable.

Prerequisites

If the heartbeat route has been configured during system preconfiguration, this operation can be skipped. If the heartbeat route has not beenconfigured during system preconfiguration, configure the heartbeat route when the heartbeat IP addresses of the primary and secondary sites areunreachable.

U2000 processes must have been stopped. For how to stop the U2000 processes, see How to Start/Stop the NMS Before Synchronizing the Primaryand Secondary Sites (Solaris, PC Linux).

The remote desktop control software is ready. For details, see How to Use the VNC to Remotely Access a Workstation.

Procedure

1. Log in to the Java Desktop System, Release 3 session of the server as user ossuser using the remote desktop control software, such as VNC. Fordetails, see Configure the VNC service as the ossuser user.

NOTE:The initial password of the ossuser user is Changeme_123. The password needs to be changed during the first login to ensure system security. Change the password in time,regularly update it, and keep it safe. For details, see How to Change the OS User Password.

2. Double-click the U2000 NMS Maintenance Suite shortcut icon on the desktop and then wait about one minute. The Login dialog box is displayed.



NOTE:

In Solaris or SUSE Linux OS, log in to the Java desktop system as user ossuser. Otherwise, the U2000 NMS Maintenance Suite shortcut icon is not displayed on the desktop.To start the MSuite client by running commands, log in to the OS in GUI mode and run the following commands as user ossuser. If you have logged in as the root user, youcannot run the su - ossuser command to switch to the ossuser user to run the following command. You must log out of the root user and then log in to the system as the ossuseruser.$ cd /opt/oss/client/engineering $ ./startclient.sh

3. Set the login parameters.The login parameters are described as follows:

IP Address: Log in to the local MSuite server, use the default IP address 127.0.0.1.

NOTE:The Login dialog box of the MSuite server has the function to keep the login list. Selecting an IP address from the IP Address drop-down list is recommended. If thedesired 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.

Password: The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The passwordmust be changed during the first login to ensure system security. Keep the password confidential and change it regularly. For details, seethe MSuite help.

4. Click Login.

NOTE:When you log in to the MSuite client, a progress bar is displayed showing the progress of querying components and instances. 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.Change the initial password upon your first login to ensure U2000 system security and remember the new password.

5. On the MSuite client, click the Server tab.

6. Right-click the target server and choose Configure Route from the shortcut menu. The Configure Route dialog box is displayed.

7. In the dialog box that is displayed, click Add or Delete according to actual route conditions to configure the route.

NOTICE:Before adding a route, ensure that the server and the router are directly connected. Otherwise, the route cannot be added.

For example, the procedure for adding a route from a client (IP address: 10.70.73.77) to a server (IP address: 10.71.224.12) is as follows, with the IPaddress of the intermediate router being 10.71.224.1:

a. Ensure that the server and the router are directly connected.

b. Click Add. Set Destination to 10.70.73.0, Subnet Mask to 255.255.255.0, and Gateway to 10.71.224.1.



8. Click OK.

9. After the configurations are complete, run the netstat -nr command to view route configurations.


1.3.7 Connecting the Primary and Secondary SitesThis topic describes how to connect the primary and secondary sites using the MSuite. After the U2000 is installed on the primary and secondary sites, youmust connect the primary and secondary sites to establish a high availability system.

Prerequisites

The preceding steps for installing the primary and secondary sites must be complete.

Database sa user password, and database NMS user password must be the same on the primary and secondary sites.

The installed components and deployed instances must be the same on the primary and secondary sites.

The operations on the primary and secondary sites must be the same. For example, if instances are added on the primary site and then deleted,instances must be added on the secondary site and then deleted.

Ensure that the network between the primary and secondary sites is smooth.

All VCS clients on the primary and secondary sites must be logged out of.

MSuite client on the secondary site must be logged out of.

Ensure that the host names of primary and secondary sites are different.

Ensure that VVR ports can be connected.

Context

Connect the primary and secondary sites in either of the following modes:

Mode 1 (recommended): GUI mode. If you are not familiar with common commands of the Solaris OS, connecting the primary and secondary sitesin GUI mode is recommended.

Mode 2: CLI mode. If you fail to log in to the OS in GUI mode, using primary and secondary sites the CLI mode is recommended.

Procedure

Mode 1 (recommended): Connect the primary and secondary sites in GUI mode.

1. 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:...root 5694 1 0 19:47:23 ? 61:16 /opt/OSSJRE/jre_sol/bin/java -server -Dlanguage=en -Xverify:none -Xmx256m -Xm

NOTE:If the displayed information contains /opt/OSSJRE/jre_sol/bin/java -server, the MSuite servers have been started.

If the MSuite servers have not been started, run the following commands as the root user to start the MSuite servers:# cd /opt/OSSENGR/engineering# ./startserver.sh

2. Log in to the Java Desktop System, Release 3 session of the OS of the primary site as the ossuser user. For details, see Configure theVNC service as the ossuser user.

NOTE:The initial password of the ossuser user is Changeme_123. The password needs to be changed during the first login to ensure system security. Change the passwordin time, regularly update it, and keep it safe. For details, see How to Change the OS User Password.

3. On the primary site, start up the MSuite client.Double-click the shortcut icon of the U2000 NMS Maintenance Suite or run the following commands:$ cd /opt/oss/client/engineering$ ./startclient.sh

Wait for about one minute. A dialog box is displayed, as shown in the following figure.



Then, set the related parameters according to the following table.

Parameter Settings

IP Address If the Network Management System Maintenance Suite client and the Network Management SystemMaintenance Suite server are on the same computer, you must enter 127.0.0.1 or the application IPaddress on the primary site.If the Network Management System Maintenance Suite client and the Network Management SystemMaintenance Suite server are on different computers, enter only the application IP address on theprimary site.

Port Specifies the port number. The default value is 12212.

User Name Specifies the user name. The default value is admin.

Password The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comespreinstalled). The password must be changed during the first login to ensure system security. Keep thepassword confidential and change it regularly. For details, see the MSuite help.

4. Click Login to access the Network Management System Maintenance Suite window.

NOTE:When you log in to the MSuite client, a progress bar showing the progress of querying subsystems and instances is displayed. Wait until the operation is complete.

5. Choose Deploy > Synchronize Primary and Secondary Sites.

6. Enter the application IP address and the MSuite password of the remote site, and click OK. A progress bar is displayed, indicating theprogress of synchronizing the primary and secondary sites. It takes about 150 minutes to complete the process. Wait patiently until thedialog box indicating the successful of synchronizing the primary and secondary sites is displayed.

7. Click OK. Wait patiently until the dialog box shown in the following figure is displayed.

NOTE:The duration of data replication depends on the stability of the network bandwidth and the volume of the data to be replicated.In the lower-left corner of the MSuite, refresh the data replication status of the primary and secondary sites. If the MSuite prompts Replication status:100%, Finished., data replication is complete.If the status keeps Replication status: 99% remain for a long time, see How to Solve the Problem Where the Amount of Remaining Data Keeps 99%During Data Synchronization in a High Availability System to solve the problem. Then use the MSuite to check the replication status.

Mode 2: Connect the primary and secondary sites in CLI mode.



1. Ensure that the primary and secondary sites on the MSuite server have been started. For details, see 1 in mode 1.

2. Log in to the OS of the primary site as the ossuser user and run the following commands:


$ cd /opt/oss/client/engineering$ ./startclient.sh deploy -ip 127.0.0.1 -port 12212 -username admin buildHA -secondaryip Application_IP _address _of _the _peer _siteEnter the MSuite login password[]:Enter the remote node maintenance suite password[]:

3. On the primary site, check data replication status as the root user.# vradmin -g datadg repstatus datarvg

NOTE:To save time, running the preceding command every half an hour is recommended to check the data replication status.

A message similar to the following will be displayed:Replicated Data Set: datarvgPrimary: Host name: 10.9.1.1 RVG name: datarvg DG name: datadg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_vol SRL size: 1.00 G Total secondaries: 1

Secondary: Host name: 10.9.1.2 RVG name: datarvg DG name: datadg Data status: consistent, up-to-date Replication status: replicating (connected) Current mode: asynchronous Logging to: SRL Timestamp Information: behind by 0h 0m 0s

NOTE:If Replication status is displayed as resync in progress (autosync), Data status is displayed as inconsistent, and the value of Logging to is becomingsmaller, data is being duplicated between primary and secondary sites.If Replication status is displayed as replicating (connected) and Data status is displayed as consistent, up-to-date, data duplication of the high availabilitysystem (Veritas hot standby) is complete.If Replication status is displayed as logging to DCM (needs dcm resynchronization), you must run the vradmin -g datadg resync datarvg command onthe primary site as the root user to perform manual synchronization.The duration of data replication depends on the stability of the network bandwidth and the volume of the data to be replicated.


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

Loading a U2000 LicenseThis topic describes how to load a U2000 license. Before using a U2000, you must load a U2000 license.

Updating a Veritas LicenseThis topic describes how to update a Veritas License. The Veritas License used in the NMS installation is a demo License. After the server is deliveredto the installation site, the demo License must be replaced with the formal Veritas License in time.


1.3.8.1 Loading a U2000 LicenseThis topic describes how to load a U2000 license. Before using a U2000, you must load a U2000 license.

Prerequisites

The U2000 license file must be ready.



NOTICE:The license file name can contain digits, letters, and special characters excluding the space or \ /:*?"<>|.

Ensure that the primary and secondary sites have been connected and data has been synchronized between the primary and secondary sites.

Context

The U2000 license only need to be loaded on the primary site. It will be synchronized to the secondary site automatically after the U2000 license has beenloaded on the primary site.

Two methods are available for loading a U2000 license.

Method one: Load the license in the GUI. This method is applicable to users who are not familiar with common commands of the Solaris OS.

Method two: Use commands to load the license. This method is applicable to users who cannot log in to GUI OSs.

Procedure

1. Send the license file to the U2000 installation path /export/home/ossuser of the primary site by SFTP as the ossuser user. For details, see How toUse 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 bythe ossuser user.

2. Log in to the Java Desktop System, Release 3 session of the server OS as user ossuser using the remote desktop control software.

NOTE:The initial password of the ossuser user is Changeme_123. The password needs to be changed during the first login to ensure system security. Change the password in time,regularly update it, and keep it safe. For details, see How to Change the OS User Password.

3. On the primary site, do as follows to start U2000 processes:GUI mode:

a. Run the following command to start the VCS client:$ hagui&

b. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.

NOTE:If you are not logging in to the VCS client for the first time, click a server record in the information list in the Cluster Monitor window.

c. Enter the IP address for the Heartbeat network service of the primary site. Then, click OK.

d. Enter the user name and password for VCS login.

NOTE:The default VCS user name is admin and the default password is Changeme_123. To ensure system security, change the default password in time. For details, seeHow to Change the admin User Password for Logging In to the VCS Client. If the default password has been changed, enter the new password.

e. Right-click AppService in the navigation tree and choose Online > host_name from the shortcut menu.

f. In the dialog box that is displayed, click Yes.



If all resources, including NMSServer, BackupServer, DatabaseServer, DataFilesystem, RVGPrimary and appNIC, are in the Online on Primasterstate, the U2000 server is started successfully.

NOTE:High availability system resources displayed in the resource tree vary according to network configuration schemes. The differences can be ignored. If an independent NMSapplication IP address without IPMP has been configured, the VCS monitors appNIC resource. If the system IP address wihtouth IPMP is used as the NMS application IPaddress, not the heartbeat or replication IP address, the VCS monitors appNIC resource.

CLI mode:

$ su - rootPassword: root user password# hagrp -online AppService -sys hostname

4. On the primary and secondary sites, check whether a license file already exists in the license path. If a license file already exists, back it up.$ su - rootPassword: root user password# cd /opt/oss/server/etc/conf/license# ls

If the folder contains any other license file, run the following commands to back up the any other license file to the/opt/oss/server/etc/conf/license_backup path.# mkdir -p /opt/oss/server/etc/conf/license_backup# cd /opt/oss/server/etc/conf/license# cp license_file_name /opt/oss/server/etc/conf/license_backup

5. On the primary site, load the U2000 license.

NOTE:To make both the U2000 commercial and temporary licenses take effect, use the GUI mode.

Method one: Load the license in the GUI.

a. Log in to the OS where the U2000 client is installed.

In Windows, log in to the OS as the administrator user.

In Solaris, log in to the OS as the ossuser user.

b. On the desktop, double-click U2000 Client. The Login dialog box is displayed.

c. In the Server drop-down list, select the server (server on the primary site) to be logged in to. Then, set User Name and Password to thevalid values, and click Login. The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comespreinstalled). The password must be changed during the first login to ensure system security. Keep the password confidential and changeit regularly.

NOTE:If a message indicating that no license is available is displayed when you log in to the U2000 client.

a. In the Confirm dialog box, click Yes. The Open dialog box will be displayed.b. 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.c. Click OK.d. Click Yes and confirm the loaded license.e. Click OK.

If U2000 license is loaded before.

a. Choose Help > License Management > License Information from the main menu (traditional style); alternatively, double-click SystemManagement in Application Center and choose License Management > Licenes Information from the main menu (application style).

b. In the License Information dialog box, click Update License.

c. Select the new license file and click Open.

d. Click Next.e. 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. Ifthe in-use U2000 license has a commercial license and a temporary license, the new license will replace the license of the sametype. For example, if the new license is a commercial license, the commercial license in the in-use U2000 license will be replaced.

f. Click Finish.g. Click Yes and confirm the updated license.h. Click Yes to close all windows.i. Click Yes to log out of the system.

Method two: Use commands to load the license.

a. Do as follow to make the license take effect:

i. log in to the OS of the U2000 server as the ossuser user on the primary site.

ii. To update the U2000 license file, run the following commands:$ cd /export/home/ossuser$ updateLicense -file License_file_name



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. Usethe license uploaded by the ossuser user.

Information similar to the following is displayed:state product feature item name old value new valueno change: U2000 COMMON LSW1CAPA01 Client 500 500no change: U2000 COMMON LSW1CAPA01 Client 1 1no change: U2000 COMMON LSW1FMCLT01 Alarm Export 1 1no change: U2000 COMMON LSW1RENOTI01 Client 1 1

Are you sure to update the license?(Y/N)

iii. Enter Y, and then press Enter.

Parent topic: Loading or Updating a License File

1.3.8.2 Updating a Veritas LicenseThis topic describes how to update a Veritas License. The Veritas License used in the NMS installation is a demo License. After the server is delivered to theinstallation site, the demo License must be replaced with the formal Veritas License in time.

Prerequisites

The formal Veritas License must be obtained.

Context

You need to replace the demo licenses on the NMS servers at both the primary and secondary sites with formal Veritas licenses. Replace the Veritas licenses atthe secondary site, perform a primary/secondary switchover, and then replace the Veritas licenses at the primary site.

Procedure

Through the GUI:

1. Log in to the MSuite client.

2. Choose Deploy > Update VRTS Licenses.

3. In the Update VRTS Licenses dialog box, enter the new licenses.

NOTE:The licenses that are newly applied for include VRTS STORAGE FOUNDATION, VRTS REPLICATOR, and VRTS CLUSTER SERVER.

4. Click OK.

NOTE:A message asking you to restart the OS and indicating that the Veritas licenses must be updated at both the primary and secondary sites is displayed.

5. Click OK.

6. Choose System > Exit from the main menu. The Exit dialog box is displayed.

7. Click OK.

8. Log in to the OS as the root user.

a. Run the following command to shut down the U2000:

# hares -offline NMSServer -sys hostname

b. Run the following command to disable the Sybase database service:# hares -offline BackupServer -sys hostname# hares -offline DatabaseServer -sys hostname

NOTE:hostname specifies the server name. You can run the hostname command to view the server name.

9. To stop the VCS service, run the following commands:# cd /opt/VRTSvcs/bin# hastop -local -force

10. To check whether the VCS service is stopped, run the following command:# ps -ef|grep had

Information similar to the following is displayed:



root 27663 17299 0 00:31:00 pts/2 0:00 grep had

NOTE:If the had and hadshadow processes are not displayed, the VCS service is successfully stopped; otherwise, run the kill -9 process ID command to stop the associatedprocesses.

11. To restart the OS, run the following commands:# sync;sync;sync;sync# shutdown -y -g0 -i6

12. After the secondary site is restarted, perform a primary/secondary switchover, and repeat the preceding operations at the primary site toreplace the Veritas licenses at the primary site.

13. Perform a primary/secondary switchover to restore the normal primary/secondary relationship.

Through the CLI:


2. To back up all the License files in the /etc/vx/licenses/lic path, run the following commands:# mkdir /export/home/licenses# mv /etc/vx/licenses/lic/*.vxlic /export/home/licenses

3. Run the following commands to clear the temporary license:# vxkeyless set NONE

4. Run the following commands to switch to the directory where the vxlicinst file is stored.# cd /opt/VRTS/bin

5. Run the following commands to update the VxVM License.# ./vxlicinstThe following information is displayed:Symantec License Manager vxlicinst utility version 3.02.61.004Copyright (C) 1996-2007 Symantec Corporation. All rights reserved.

Enter your license key :

6. Enter the new License key of VRTS STORAGE FOUNDATION. The new License key is in the format of XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-X. Then, press Enter.

NOTE:X indicates the a letter or digit of a License key.The information about the demo or formal License that is newly obtained is contained in the License file.The new Licenses include VRTS STORAGE FOUNDATION, VRTS REPLICATOR, and VRTS CLUSTER SERVER.

7. Repeat 5, and then enter the new License key of VRTS REPLICATOR.

8. Repeat 5, and then enter the new License key of VRTS CLUSTER SERVER.

9. Check whether the updated License takes effect. For details, see How to Check the Veritas License.

10. Run the following command to change the permission of the license file:# chmod -R 640 /etc/vx/licenses/lic


a. Run the following command to shut down the U2000:


b. Run the following command to disable the Sybase database service:# hares -offline BackupServer -sys hostname# hares -offline DatabaseServer -sys hostname


12. To stop the VCS service, run the following commands:# cd /opt/VRTSvcs/bin# hastop -local -force

13. To check whether the VCS service is stopped, run the following command:# ps -ef|grep had

Information similar to the following is displayed:root 27663 17299 0 00:31:00 pts/2 0:00 grep had

NOTE:If the had and hadshadow processes are not displayed, the VCS service is successfully stopped; otherwise, run the kill -9 process ID command to stop the associatedprocesses.



14. To restart the OS, run the following commands:# sync;sync;sync;sync# shutdown -y -g0 -i6

15. After the secondary site is restarted, perform a primary/secondary switchover, and repeat the preceding operations at the primary site toreplace the Veritas licenses at the primary site.

16. Perform a primary/secondary switchover to restore the normal primary/secondary relationship.

Parent topic: Loading or Updating a License File

1.3.9 Checking System InstallationThis topic describes how to check the installation of a high availability system (Solaris).

Context

During installation of the U2000 software, the OS user ossuser is created automatically. The ossuser user is used to regularly maintain a U2000.

The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password must be changedduring the first login to ensure system security. Keep the password confidential and change it regularly.

Procedure

1. Log in to the OSs of the servers of the primary and secondary sites as the root user.

2. Check the installation path.After the U2000 server software is installed, the following directories will be generated automatically. Do not delete these directories at random;otherwise, the U2000 server software cannot be used properly.

/opt/OSSENGR

/opt/OSSICMR

/opt/OSSJRE

/opt/oss

/opt/sybase

/opt/OSSICMR/OSSApp

/etc/ICMR

/var/ICMR

3. To check the U2000 version, run the following commands:# cd /opt/oss/server/etc/conf# cat imap.cfg

Information similar to the following is displayed:...VER = U2000V200R001C00SPCxxx...

The last line of the displayed information shows the U2000 version. If the version information does not meet the actual requirement, uninstall theU2000 and obtain the correct software version to install the U2000 again.

4. Optional: To check whether disk arrays are properly mounted, run the following command:

NOTE:If no disk array has been configured, skip this step.

# df -h

Information similar to the following is displayed:Filesystem Size Used Avail Use% Mounted on/dev/sda1 50G 583M 47G 2% /udev 7.9G 200K 7.9G 1% /dev/dev/sda8 20G 173M 19G 1% /export/home/dev/sda7 119G 9.7G 103G 9% /opt/dev/sda5 20G 2.4G 17G 13% /usr/dev/sda6 20G 290M 19G 2% /vartmpfs 8.0G 92K 8.0G 1% /dev/shmtmpfs 4.0K 0 4.0K 0% /dev/vx/dev/vx/dsk/datadg/lvdatabase 148G 5.9G 135G 5% /opt/sybase/dev/vx/dsk/datadg/lv_backup 394G 199M 374G 1% /opt/backup/dev/vx/dsk/datadg/lvapp 197G 7.9G 179G 5% /opt/oss/dev/vx/dsk/datadg/lvdata 89G 29G 56G 34% /opt/sybase/data

Pay attention to the lines that contain datadg.



If the values of Mounted on for the lines that contain datadg are the same as the preceding command output, disk arrays are properlymounted.

If the values of Mounted on for the lines that contain datadg are different from the preceding command output, disk arrays are notproperly mounted. Contact Huawei engineers to locate the fault.

5. To check disk group status, run the following command:# vxdg list

Information similar to the following is displayed:vxdg list

NAME STATE IDrootdg enabled 1281152223.12.primasterdatadg enabled 1281151979.10.primaster

If the value of STATE is enabled, the disk group status is correct.

If the value of STATE is not enabled, the disk group does not function properly. Contact Huawei engineers to locate the fault.

6. To check disk status, run the following command:# vxdisk list

Information similar to the following is displayed:DEVICE TYPE DISK GROUP STATUSc1t0d0s2 auto:sliced disk01 rootdg onlinec1t1d0s2 auto:sliced disk02 rootdg onlinec1t2d0s2 auto:sliced disk03 datadg onlinec1t3d0s2 auto:sliced disk04 rootdg onlinec1t4d0s2 auto:sliced disk05 rootdg onlinec1t5d0s2 auto:sliced disk06 datadg online

NOTE:The equipment names in the DEVICE column may be different from those displayed on the terminal according to the actual situation of the workstation. Here, six hard disks aretaken as an example.

If the value of STATUS is online, the disk status is correct.

If the value of STATUS is not online, the disk does not function properly. Contact Huawei engineers to locate the fault.

7. To check disk volume status, run the following command:# vxprint -v

Information similar to the following is displayed:Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0v backup fsgen ENABLED 161493120 - ACTIVE - -v home fsgen ENABLED 4212864 - ACTIVE - -v opt fsgen ENABLED 283116672 - ACTIVE - -v rootvol root ENABLED 41945472 - ACTIVE - -v swapvol swap ENABLED 33560448 - ACTIVE - -v var fsgen ENABLED 41945472 - ACTIVE - -

Disk group: datadg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0v lv_nms_data datarvg ENABLED 83886080 - ACTIVE - -v srl_vol datarvg ENABLED 2097152 SRL ACTIVE - -

NOTE:The preceding disk volume status information uses the 6 x 146 GB hard disk as an example. The actual information varies according to hard disk configuration.

If more than two hard disks are configured, the two disk groups (rootdg and datadg) are available.If only two disks are configured, only one disk group (datadg) is available.

Reference Standards

The value of KSTATE must be ENABLED for all disk volumes.

The value of STATE must be ACTIVE for all disk volumes.

If disk volume status does not meet the preceding requirements, run the following command to record details about all disk volumes, and contactHuawei local office or customer service center in time according to warranty information.# vxprint -l disk_volume_name

8. To check whether the replication between the primary and secondary sites is normal, run the following command on the primary site:# vradmin -g datadg repstatus datarvg

Information similar to the following is displayed:Replicated Data Set: datarvgPrimary: Host name: 10.9.1.1 RVG name: datarvg DG name: datadg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_vol SRL size: 1.00 G Total secondaries: 1




If the value of Replication status is replicating (connected), the replication is normal.

9. Do as follows on the primary site to start the U2000 server:

NOTE:By default, the U2000 starts along with the OS.

GUI mode:

a. To start the VCS client, run the following command:# hagui&

b. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.


c. Enter the IP address of the Heartbeat network service of the primary site. Then, click OK.

d. Enter the user name and password for VCS login.

NOTE:The default VCS user name is admin and the default password is Changeme_123. To ensure system security, change the default password in time. If the defaultpassword has been changed, enter the new password.

e. Right-click AppService and choose Online > host_name from the shortcut menu.

NOTE:If a fault has occurred when the AppService process was started before, right-click AppService and choose clear fault from the shortcut menu. Then, choose Online> host_name to start the AppService process.


If all resources, including NMSServer, BackupServer, DatabaseServer, DataFilesystem, RVGPrimary and appNIC, are in the Online on Primasterstate, the U2000 server is started successfully.

NOTE:High availability system resources displayed in the resource tree vary according to network configuration schemes. The differences can be ignored. If an independent NMSapplication IP address without IPMP has been configured, the VCS monitors appNIC resource. If the system IP address wihtouth IPMP is used as the NMS application IPaddress, not the heartbeat or replication IP address, the VCS monitors appNIC resource.

CLI mode:

# hagrp -online AppService -sys hostname

NOTE:



If a fault has occurred when the AppService process was started before, run the following command to rectify the fault before starting the AppService process:

# hagrp -clear AppService

10. Log in to the active site server GUI as the ossuser user. Then, start the System Monitor to view the running status of each process.

NOTICE:

If you cannot log in to the GUI of the server OS, do as follows to view the process status:

a. Run the su - ossuser command to switch to the ossuser user.b. Check the shortcut icons. The following shortcut icons are displayed on the desktop:

U2000 ClientU2000 System MonitorU2000 NMS Maintenance SuiteNE Software Management

c. Run the following command to view the process status.$ svc_adm -cmd status

a. On the desktop of the OS, double-click the U2000 System Monitor shortcut icon.

NOTE:The default ACL range is the entire network segment. It is recommended that you set the ACL restriction range based on the security requirements. .

b. In the dialog box that is displayed, enter the U2000 user name and password (to open the System Monitor window). The initial passwordof the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password must be changed during thefirst login to ensure system security. Keep the password confidential and change it regularly.

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 on the U2000 server for the HA system (Solaris), see How to Set the Communication Mode of the Server in aHigh Availability System (Solaris, SUSE Linux).

The U2000 is functioning properly if it can initiate in automatic startup mode, indicating that the U2000 is functioning properly.If a process cannot start, right-click the process and choose Start the Process from the shortcut menu.If the U2000 works properly, contact Huawei engineers.

11. Start the U2000 client as user ossuser to log in to the server GUI.

NOTICE:The U2000 should be logged in to through a standalone client in the event that login to the server through the GUI fails and login to the client on theserver is not possible.

a. On the desktop of the OS, double-click the U2000 Client shortcut icon.

b. In the dialog box that is displayed, enter the U2000 user name and password to open the main window of the client. The initial passwordof the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password must be changed during thefirst login to ensure system security. Keep the password confidential and change it regularly.

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 on the U2000 server for the HA system (Solaris), see How to Set the Communication Mode of the Server in aHigh Availability System (Solaris, SUSE Linux).

Follow-up Procedure

Before synchronizing the primary and secondary sites, start the NMS to manage NEs. For details about how to start the NMS, see How to Start/Stopthe NMS Before Synchronizing the Primary and Secondary Sites (Solaris, PC Linux).

To save the server disk space, run the following commands to delete software packages in the /opt/install and /opt/vrtstmp directories.# rm -r /opt/vrtstmp# cd /opt/install# rm Name_of_software_package

For example, rm U2000version_server_nmscore_solaris_SPARC.tar.

NOTICE:

You can not delete the compressed files in the /opt/install, or security enhancement service can not be started.After installation, do not change the installation directory. If the installation directory is changed, the U2000 fails to work properly oruninstalled.

If login to a U2000 client fails, see Failure to Log In to the U2000 Server from a U2000 Client to resolve the problem.




1.4 Separating the Primary Site from the Secondary SiteThis topic describes how to separate the primary site from the secondary site. Separating the primary site from the secondary site refers to disconnecting theprimary site and the secondary site.

Prerequisites

Ensure the installation directory has enough available space. In the Solaris or SUSE Linux OS, you can run the df -hk /opt command to view theremaining space of the /opt directory.

On Solaris or SUSE Linux OS, you must ensure that the U2000 and the database have been shut down.

NOTE:In the VCS client at the primary site, choose AppService from the navigation tree. If the value of State for the active site is Offline in the Group Status on Member Systems areaon the Status tab page, and the value of Status is Offline on primary in the Resource Status area, the U2000 and database are shut down. Otherwise, in the Cluster Explorerwindow, select the AppService resource group in the navigation tree, right-click, and choose Offline > host name from the shortcut menu to stop the Sybase process and U2000server processes.

No data duplication between the primary or secondary site in the high availability system.

On the primary or secondary site, run the following command to check the system status:# vradmin -g datadg repstatus datarvg

If Replication status is displayed as replicating (connected) and Data status is displayed as consistent, , data duplication of the high availabilitysystem (Veritas hot standby) is complete.

If separation operations need to be performed only on the primary site, ensure that the MSuite server on the primary site has started and starting theMSuite server on the secondary site is not required, and vice versa.

Context

If either the primary or secondary site needs to be restored as an independent one, start the MSuite server only on the involved site and then perform theseparation operation.The following procedure uses the primary site as example.

Procedure

Mode 1 (recommended): Separate the primary site from secondary site in GUI mode.

1. Ensure that the MSuite servers have been started.Run the following command as the root user to check whether the MSuite servers are started:













Parameter Settings







5. Choose Deploy > Separate Primary Site from Secondary Site. The Warning dialog box is displayed.

6. Click Yes. Then click Yes in the Warning dialog boxes displayed. The progress bar is displayed indicating the status of separating theprimary and secondary sites. Wait until the dialog box is displayed indicating that the separation is complete.

7. Click OK.

Mode 2: Separate the primary site from secondary site in CLI mode.

1. Ensure that the MSuite servers have been started. For details, see 1 in mode 1.

2. Log in to the OS of the primary site as the ossuser user and run the following commands:$ cd /opt/oss/client/engineering$ ./startclient.sh deploy -ip 127.0.0.1 -port 12212 -username admin splitHAEnter the MSuite login password[]:

NOTE:The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password must be changed duringthe first login to ensure system security. Keep the password confidential and change it regularly. For details, see the MSuite help.

Perform the following operations as prompted.

Reference standardRun the vradmin -g datadg repstatus datarvg command as user root to check whether the data replication relationship has been deleted.

If the information only about one site (similar to the following) is displayed, the data replication relationship between the primary and secondary siteshas been deleted, and the primary and secondary sites have been separated.Replicated Data Set: datarvgPrimary: Host name: 10.168.1.10 RVG name: datarvg DG name: datadg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_vol SRL size: 1.00 G Total secondaries: 0

Follow-up Procedure

To re-establish the high availability system, you must perform synchronization between the primary and secondary sites. For details, see Connecting thePrimary and Secondary Sites.




1.5 Commissioning the U2000This topic describes how to commission the U2000. Usually, the server delivered by Huawei has been preinstalled, the primary and secondary sites have beenseparated, and you do not need to reinstall the U2000 on the server. You can directly commission the U2000 and modify the system and U2000 parametersaccording to on-site requirements to allow for the normal use of the U2000.If the server has not been preinstalled by Huawei, install the U2000 andcommission the system. To allow the U2000 to manage the network, you must commission the U2000 before using the U2000 to manage NEs and configuringservices.

Commissioning PreparationThis topic describes the preparations for the commissioning of the U2000.

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


1.5.1 Commissioning PreparationThis topic describes the preparations for the commissioning of the U2000.

Obtaining Commissioning ParametersPlanning commissioning parameters is a prerequisite to U2000 commissioning. For details about the method of planning commissioning parameters, seethe associated section in U2000 Planning Guide and fill in the commissioning parameter table.

Checking Hardware ConnectionsThis topic describes how to check hardware installation and cable connections before installing a U2000. If hardware is improperly installed or cable isimproperly connected, unexpected error may occur during installation of the U2000.

Parent topic: Commissioning the U2000

1.5.1.1 Obtaining Commissioning ParametersPlanning commissioning parameters is a prerequisite to U2000 commissioning. For details about the method of planning commissioning parameters, see theassociated section in U2000 Planning Guide and fill in the commissioning parameter table.

System Commissioning Parameters

Table 1 System commissioning parametersItem Parameter Parameter Remarks

Set Controller For details, see section IP Address Planning of the HA System(Solaris) in U2000 Planning Guide..

For details, see section Configuring Controller IPAddresses in U2000 HA System Software Installationand Commissioning Guide (Solaris).

Set HardwareAlarm

For details, see section IP Address Planning for the Single-Server System (Solaris) in U2000 Planning Guide.

See section Setting Hardware Alarm Monitoring inU2000 HA System Software Installation andCommissioning Guide (Solaris) to perform manualconfiguration. Then enter the IP addresses of thecontrol card and disk array controllers A and B, andclick Apply.

If disk arrays have beenconfigured for the server orthe server model isM4000/M5000, hardwarealarm configuration isrequired.

Veritas License VRTS STORAGE FOUNDATION: For details, see section Applying for a VeritasLicense in U2000 HA System Software Installationand Commissioning Guide (Solaris).

VRTS REPLICATOR:

VRTS CLUSTER SERVER:

Adding Instances TransmissionNetworkElementManagement

Instance Count: For details, see section NMS Deployment PackageList in U2000 Planning Guide.

Deployment packages fallinto three types: single-server single-instance,single-server multi-instance, and systemsingle-instance. Instancescan be added only for asingle-server multi-instancedeployment package.

MarineNetworkElementManagement

Instance Count:

ConfigureCORBA NBIInstance

Naming service host address:

It is recommended that all IP addresses be theapplication IP addresses used on the U2000. If the IPaddresses to be changed are in Configure Network,the commissioning tool automatically changes the IPaddresses. Manual operations are not required. The IPaddresses for the notification service and CORBAagent are the same. The naming service may bedeployed in centralized mode. You must confirm the



Notify service host address:

deployment mode with upper-layer OSS.This IP address is used to interconnect with the upper-layer OSS. It can be different from the U2000application IP address. It must allow the upper-layerOSS to use the IP address and port number to accessthe U2000.If address translation exists, host names can be used.However, if host names are used, you must modify thehost files on the U2000 and upper-layer OSS serverand provide the mappings between host names and IPaddresses. For details, see U2000 CORBA NBI UserGuide.

CORBA Agent Host Address:

Naming Service Port:

Specifies the port used by the upper-layer OSS toobtain the naming service and to use CORBA NBIs toaccess the U2000. If this port is shielded on thefirewall between the upper-layer OSS and U2000, thenaming service may become unavailable. This portcannot conflict with ports used by other services onthe U2000 server.Default value: 12001 for the non-SSL mode and 22001for the SSL mode

Notify Service Port:

Specifies the port used by CORBA NBIs to sendnotifications to the upper-layer OSS. If this port isshielded on the firewall between the upper-layer OSSand U2000, no notification is received. This portcannot conflict with ports used by other services onthe U2000 server.Default value: 12002 for the non-SSL mode and 22002for the SSL mode

CORBA Agent Port:

Specifies the port used by the CORBA service. Thisport cannot conflict with ports used by other serviceson the U2000 server.Default value: 12003 for the non-SSL mode and 22003for the SSL mode

Character Set: □UTF-8 □GBK □ISO8859-1

Specifies the encoding format of the informationreported by CORBA NBIs. This parameter must beset according to the on-site situations of the upper-layer OSS. If the character set used by the upper-layerOSS is different from that used by CORBA NBIs,garbled characters may exist on the upper-layer OSS.Default value: UTF-8

Set EMSName Set EMS Name:

Specifies the identifier used by the upper-layer OSS todistinguish different sets of U2000. If multiple sets ofU2000 are integrated into the same upper-layer OSS,this parameter must be set based on carriers' NMSplanning.Default value: Huawei/U2000

Maximum Capacity of a Log File

Specifies the maximum size of a log file, ranging from1 MB to 20 MB. Keeping the default value isrecommended.Default value: 4 MB

Log OutputMode

Log periodicallyLog immediately

Specifies the mode of generating logs. Keeping thedefault value is recommended.Default value: Log immediately

Log Level

Assertion/Internal Error LogEnableDisable

External Error LogEnableDisable

I/O Error LogEnableDisable

Runtime Trace LogEnableDisable

Specifies the level of generating logs. This parameteris used for troubleshooting. Keeping the default valueis recommended.

Assertion/Internal Error Log: EnableExternal Error Log: EnableI/O Error Log: EnableRuntime Trace Log: Disable

Specifies the type of an NE ID. If the NE ID type isincorrect, the upper-layer OSS fails to be parsedcorrectly. Configure this parameter after confirmingwith the upper-layer OSS. Only transport NEs havephysical IDs.

Physical ID: is expressed in dotted decimal



NE ID NE ID TypeLogical IDPhysical ID

notation and equals to the NE ID x 65536 +extended ID. For example, if the NE ID is 1and the extended ID is 9 for NE(9-1), thephysical ID is 65545.Physical ID: is expressed in dotted decimalnotation and is automatically assigned by theU2000 to NEs. For example, 3145765.

Default value: Logical ID

Virtual NEEnabling

Specifies whetherthe query resultscontain virtual SDHNes:

EnableDisable

Specifies whether virtual NEs are enabled whilequerying NEs, SDH paths, routes, and fibers. If theupper-layer OSS uses virtual NEs or manages devicesfrom other vendors, enable this function. Otherwise,disable this function.Default value: Enable

EnablingCorrelativeAlarm

AllRoot

Specifies whether CORBA NBIs are enabled withalarm correlative analysis so that correlative alarmsare reported in alarm update mode.Default value: All

EngineeringAlarm

DisableEnable

Specifies whether CORBA NBIs report maintenancealarms and need to be used along with the U2000engineering task. By default, all alarms are reported.

Disable: specifies that all alarms are queriedand reported.Enable: specifies that all alarms excludingengineering alarms are queried and reported.

Default value: Disable

ObjectIdentifier

Internal IDObject name

Specifies the rule for identifying objects reported fromCORBA NBIs to the U2000.

Internal ID: specifies that the ID assigned bythe U2000 is the unique identifier of anobject.Object name: specifies that the object namedisplayed on the U2000 is the uniqueidentifier of an object. The object name onthe U2000 client must be the same as that onthe U2000 server. Otherwise, data conflictsmay occur.

Default value: Internal ID

Alarm-affectedObjectReporting

DisableEnable

Specifies whether information about the fibers andpaths affected by alarms is reported.

Enable: specifies that the names of the pathsand fibers affected by alarms are queriedand reported.Disable: specifies that the names of thepaths and fibers affected by alarms are notreported.


Configure SNMPNBI Instance

SNMP Agent

Trap Sending Address/Port:

Specifies the IP address and port number used by theU2000 to interconnect with the upper-layer OSS.Ensure that SNMP NBIs can use the IP address andport number to send trap messages to the upper-layerOSS.Ensure that this port is not shielded by the firewallbetween the upper-layer OSS and U2000 and the portdoes not conflict with other ports used by the servicesof the upper-layer OSS.Default value of port: 6666

Request Receiving Address/Port:

Specifies the IP address and port number used by theU2000 to interconnect with the upper-layer OSS.Ensure that upper-layer OSS can use the IP addressand port number to send trap messages to the U2000.Ensure that this port is not shielded by the firewallbetween the upper-layer OSS and U2000 and the portdoes not conflict with other ports used by the servicesof the upper-layer OSS.Default value of port: 9812

Security Model

USM SNMPv3 applies user-based security mechanism, andUSM is such a security mechanism. Currently, onlyUSM is supported.Default value: USM

Withoutauthentication and



SNMPv3Parameters

Security Level

encryptionWithauthentication,withoutencryptionWithauthentication andencryption

Specifies the security level of SNMPv3. After thesecurity level is configured, you must selected arequired protocol and set the password. The securitylevel configured must be the same as that used for theinterconnection with the upper-layer OSS.Default value: Without authentication and encryption

Authentication

HMACMD5HMACSHA

Specifies the authentication protocol used for users toaccess SNMP NBIs. The value of this parameter mustbe the same as the authentication protocol used for theinterconnection with the upper-layer OSS.The authentication protocol can be set when thesecurity level is With authentication, withoutencryption or With authentication and encryption.

Data Encryption

DESAES

Specifies the protocol used for encryptingcommunication data. The value of this parameter mustbe the same as the data encryption protocol used forthe interconnection with the upper-layer OSS.The data encryption protocol must be set when thesecurity level is With authentication andencryption. The AES protocol is recommendedbecause it provides better security.

Third-PartyNMS

Trap Destination Address/Port: Specifies the IP address or port number of the upper-layer OSS. This parameter is used to receive trapmessages sent by SNMP NBIs.Ensure that this port is not shielded by the firewallbetween the upper-layer OSS and U2000 and the portdoes not conflict with other ports used by the servicesof the upper-layer OSS.Default value of port: 6666

SNMP Version v1v2cv3

Specifies the protocol version used by SNMP NBIs.SNMPv3 is recommended because it is more securethan SNMPv1 and SNMPv2c.Default value: v3

Read/Write Community Specifies the password used for the upper-layer OSSto access the U2000 when the SNMPv1 and SNMPv2cuse read and write community names. If thisparameter is set incorrectly, the upper-layer OSScannot obtain U2000 information from SNMP NBIs.Default value of Read Community: Changeme_123Default value of Write Community: Changeme_123

v3 User Name Specifies the user name and password used forSNMPv3–based security mechanism. If this parameteris not set, the upper-layer OSS cannot obtain U2000information from SNMP NBIs.Default value: admin

v3 Authentication Password The authentication password must be set when thesecurity level is set to With authentication, withoutencryption or With authentication and encryption.This parameter is used for the upper-layer OSS toaccess the U2000 using SNMP NBIs.

v3 Privacy Password The communication encryption password must be setif the security level is With authentication andencryption.

Alarm Severity CriticalMajorMinorWarning

Specifies the levels of the alarms reported by SNMPNBIs.The U2000 reports all alarms by default.

Alarm Category FaultAcknowledgedUnacknowledgedChanged

Specifies the types of alarms reported by SNMPNBIs.

Fault: An alarm is generated when a faultoccurs.Acknowledged: After an alarm is confirmed,SNMP NBIs report an acknowledged alarm.Unacknowledged: After an alarm isreversely confirmed, SNMP NBIs report anunacknowledged alarm.Changed: If alarm information is changed,SNMP NBIs report a changed alarm whichcontains the alarm level change, alarminfluence path, and alarm root causeidentifier.



Default value: Fault

Heartbeatsettings

Heartbeat period Specifies the period of transmitting heartbeatmessages. When the U2000 MIB is used, SNMP NBIsreport heartbeat messages within the specified period.Default value: 60s

Whether to enableheartbeat messages

EnableDisable

Specifies whether to report heartbeat messages.U2000 MIB, instead of U2000–T MIB, supports thereporting of heartbeat messages.Default value: Enable

Alarm report field Specifies the binding variables contained in the alarminformation reported by SNMP NBIs. This parametermust be set according to the alarm planning for theupper-layer OSS. For details, see U2000 SNMP NBIUser Guide.By default, all fields are reported.

Reportsettings

Report mode TrapInform

Specifies the mode of reporting trap messages bySNMP NBIs. Keeping the default value isrecommended.

Trap: After trap messages are reported, thesystem does not need to report the next trapmessage until a response is received fromthe upper-layer OSS.Inform: After trap messages are reported,the system starts to report the next trapmessage until a response is received fromthe upper-layer OSS or the number ofattempts exceeds the threshold.

Default value: Trap

Whether to useX.733

YesNo

Specifies whether trap messages use the event typeand level defined by X.733.Default value: No

Trap sending interval Specifies the interval for sending messages in Trapmode.Default value: 0

Inform delay Specifies the delay for sending the next packet inInform mode.Default value: 5

Inform retry attempts Specifies the number of allowed re-connection timesin Inform mode upon a connection failure.Default value: 3

Report timeformat

Alarm Time Format UTC TimeLocal Time(without timezone)Local Time (withtime zone)

Specifies the format of the time used by the upper-layer OSS.Default value: UTC Time

EncodingFormat

Alarm EncodingFormat:

UTF-8GBK

Set this parameter based on the planning for the upper-layer OSS.Default value: UTF-8

Filteringcorrelativealarm

AllRoot

All: specifies that all alarms, including the root andcorrelative alarms, are queried and reported.Root: specifies that only root alarms and commonalarms that have no correlative relationship arequeried and reported.Default value: All

Filteringengineeringalarm

EnableDisable

Default value: DisableDisable: specifies that all alarms are queried andreported.Enable: specifies that all alarms except forengineering alarms are queried and reported.

MIB Frame MIB U2000 MIBU2000-T MIB

Set this parameter based on the MIB file used for theintegration of the upper-layer OSS.T2000-NETMANAGEMENT-MIB.mib: U2000-TMIB HW-IMAPV1NORTHBOUND-TRAP-MIB.mibor HW-IMAPV2NORTHBOUND-TRAP-MIB.mib:U2000-T MIB

Others Whether to recordlogs

EnableDisable

Specifies whether to record logs.Default value: Disable



Real-time alarm cache size Specifies the size of the cache for real-time alarms.Every upper-layer OSS user is assigned with anindependent cache.If the alarm generation rate is larger than the alarmreport rate, NBI interfaces save alarm information tothe cache.Default value: 10000

Configure XMLNBI Instance

JMS Use SSL Specifies whether to use the common or SSL mode.The default port used varies according to the mode.The SSL mode is recommended because it enablesbetter security.Default value: Select the Use SSL check box.

Type activeMQ Specifies the middleware type of teh JMS service.Currently, the activeMQ middleware is supported.

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

Port Specifics the number of the port used by the JMSmiddleware. This parameter is usedfor sendingnotifications to the upper-layer OSS.Default value: 13171 for the non-SSL mode and 13172for the SSL mode

JMS User Name/JMS Password Specifies the user name and password used when anupper-layer OSS accesses JMS middleware. Confirmwith the upper-layer OSS before setting thisparameters.

Web Service IP Address Specifies the IP address of the Web service. Set thisparameter to the IP address of the U2000 server.Ensure that the upper-level OSS can use this IPaddress to access the U2000.

HTTPS Port Specifies the number of the port used by XML NBIs.The upper-layer OSS uses this port to obtain Webservice data from XML NBIs.Default value: 9997

Register JMS service When the upper-layer OSS needs to use AFB-basedinterface (such as getInventory), the JMS serviceneeds to be registered. If only the synchronizationmode (such as SIT or SRR) is used, do not register theJMS service in order to save system resources.Default value: Select the Register JMS servicecheck box.

HTTP Protocol HttpHttps

Specifies the protocol type of the Web service. Thisparameter is set based on the protocol selected by theupper-layer OSS. HTTPS is recommended because itis more secure than HTTP.Default value: Https

Product loglevel

DebugWarnError

Specifies the level of the logs generated by XMLNBIs. This parameter is used for troubleshooting.Default value: Warn

Filteringcorrelativealarm

AllRoot

All: specifies that all alarms, including the root andcorrelative alarms, are queried and reported.Root: specifies that only root alarms and commonalarms that have no correlative relationship arequeried and reported.Default value: All

Encoding format:UTF-8GBK


Managementdomain

Domain Name: These parameters are used to distinguish different setsof U2000 when they are managed by the same upper-layer OSS. Set the parameters according to carriers'NMS planning.Default value: Huawei/U2000

WDM routereturn order

NoneForward

When XML NBIs are used to query WDM routes,WDM routes are returned based on a specified order,which is convenient for the analysis of the upper-layerOSS.None: specifies that WDM routes are sent randomly.Forward: specifies that WDM routes are sent from the



Backward source to the sink.Backward: specifies that WDM routes are sent fromthe sink to the source.Default value: None

Filternotificationtheme

Filter Out Alarm NotificationEnableDisable

Filter Out Inventory NotificationEnableDisable

Filter Out Protection NotificationEnableDisable

Filter Out Performance NotificationEnableDisable

Filter Out Maintenance NotificationEnableDisable

Specifies whether to filter out the notifications forthese themes.Default value: The notification for all these themesare filtered out.

Filteringengineeringalarm

EnableDisable

Specifies whether XML NBIs report maintenancealarms and the alarm reporting works along withU2000 engineering tasks. By default, all alarms arereported.Default value: Disable

Objectidentifier

Internal IDObject name

Specifies the rule for identifying objects.Internal ID: specifies that the IDs assignedby the U2000 uniquely identify objects.Object name: specifies that the U2000 clientnames are used to identify objects. TheU2000 client names must be unique in orderto prevent data conflicts.

Default value: Internal ID

Alarm andserviceassociation

EnableDisable

Specifies whether to report the names of the paths orservices affected by the alarms.

Enable: specifies that if an alarm affectspaths or fibers, the names of the affectedpaths and the fibers are contained in thealarm information during alarm query andreport.Disable: specifies that the names of theaffected paths and fibers are not reported.


ConfigurePerformance TextNBI Instance

Single-periodMulti-period

Set this parameter to the collection period forperformance data. The U2000 can be used to exportperformance data generated during one or moreperiods.

Duration SettingsAutoManual

Specifies the delay mode for exporting files. The valueof this parameter for different device types varies. Ifthe value of this parameter is the same for differentdevice types, the performance data fail fails to beexported. The Auto mode is recommended. Fordetails, see U2000 Performance Text NBI UserGuide.Default value: Auto

Collection Period(min)

5101530601440

Specifies the period of collecting performance datausing performance text NBIs. The performance datacan be exported based on the collection period.

Data Export Period(min)

5101530601440

Specifies the interval for generating performance textfiles. This parameter can be customized. It isrecommended to set this parameter to a value thesame as the collection period.

Specifies the difference between the timeperformance data is generated on NEs and the time



Performancedataexportingsettings

Data Export Duration (min) the performance text file is exported.You must configure Data Export Duration (min)according to on-site requirements when DurationSettings is set to Manual. For details, see U2000Performance Text NBI User Guide.

Export Start Time

Specifies the time the startup file is exported for thefirst time. This parameter cannot be set to a valueranging from 23:00:00 to 01:00:00. If the value of thisparameter ranges from 23:00:00 to 01:00:00, a dataerror occurs during DTS switching.yyyy-mm-dd hh:mm:ssFor example, 2009-09-01 01:00:00

Indicator

Specifies the performance indicators that theperformance text file can export. Performanceindicators can be configured in two modes: template—based or manual configuration

Template-based configuration: Beforecommissioning, you must confirm theperformance indicators to be monitored andconfigure a performance indicator templateand use the following operations to configurethe performance indicators. For details, seeU2000 Performance Text NBI User Guide.Full Import: specifies that performanceindicators are fully imported to theperformance indicator template to overwritethe original indicator template. IncrementalImport: specifies that performance indicatorsare incrementally imported to theperformance indicator template and onlynew indicators are added to the originalindicator template. Export: The performanceindicator template is exported, backed up, orprovided to another U2000 server.Manual configuration: Beforecommissioning, you must confirm theperformance indicators to be monitored andprint the performance data. Modify: In thedialog box that is displayed, configure theindicators as required.

Fileexportingsettings

□Exporting to thelocal server

Exporting directory Set this parameter to the directory where theperformance data file is saved. The upper-layer OSSaccesses this directory to obtain performance data.

□Exporting to aremote FTP server

FTP Mode:FTPSFTP

FTP/SFTP ServerIP:FTP/SFTP Port:FTP/SFTP User:FTP/SFTPPassword:FTP/SFTPDirectory:SFTP Certificate:

The U2000 uploads performance data to the FTPserver. You must create an FTP user and configure theFTP user password on the U2000.Using SFTP is recommended because SFTP provideshigher security than FTP.

Log filesettings

Maximum number of backup product logs Specifies the maximum number of output logs.Default value: 10

Maximum size of product logs Specifies the maximum size of output logs.Default value: 5 M

Product log level DebugInfoWarnError

Specifies the lowest level of generating logs. The logswith the level lower than the value cannot berecorded.Default value: debug

Encoding format:UTF-8GBK


Time formatfor fileexport

UTC timeLocal time

Specifies the time format encoding for theperformance text NBI file.Default value: UTC time

Others Maximum number of records in a file Specifies the maximum number of records in a file.If the value exceeds the threshold, the extra records



are stored in another file whose serial number isincreased by 1.Default value: 100000

Number of days to save exported files Specifies the period during which files can be storedon the local server. The system automatically deletesthe files generated after the period elapses.Default value: 3 days

Start time for file deletion Specifies the start time for deleting files in ascheduled task. The value of this parameter is thesame as the server time.Format: yyyy-mm—dd hh:mm:ss

XML NBICertificate

IdentityCertificate

Certificate Type Default certificate Type: P12.For details, see section Security CertificateDescription.

File Name

TrustCertificate File Name

CRL File Name

CORBA NBICertificate Identity

Certificate

Certificate Type Default certificate Type: P1.For details, see section SSL Principle andConfiguration.

File Name

KDC File

TrustCertificate File Name

CRL File Name

Set Date Timezone

Time zone: For details, see section Time and Time ZonePlanning in U2000 Planning Guide.

Time zone:Set this parameter to the local time zone,such as Asia/Beijing.Date Time:Set this parameter to the local time.

If only the timezone needs to bemodified, restartthe operatingsystem after themodification sothat the time isautomaticallyadjusted based onthe new timezone.If the time zoneand time bothneed to bechanged, changethe time first andthen the timezone. After theoperating systemis restarted, thenew time isautomaticallyadjusted based onthe new timezone.

Date Time:

Set Password OS user root OldPassword:

New Password: For details, see section U2000 User PasswordPlanning in U2000 Planning Guide.

After security hardening isenabled, you cannot use thecommissioning tool tochange the OS userpassword. For details aboutthe method of changing apassword, see section Howto Change the OS UserPassword in U2000 Single-Server System SoftwareInstallation andCommissioning Guide(Solaris).

OS userossuser

OldPassword:

New Password:

OS userdbuser

OldPassword:

New Password:

Databaseuser sa

OldPassword:

New Password:

Databaseuser dbuser

OldPassword:

New Password:

NetworkManagementSystemMaintenanceSuite useradmin

OldPassword:

New Password:

VCS ClientUser admin

OldPassword:

New Password:



Set SSLCertificate

Apply for the SSL client and SSL server certificates andpasswords for the MSuite server and client.

The SSL certificatepreconfigured by Huawei isused only forcommissioning. If the SSLmode is used, apply to theofficial institute for thecertificate to replace thepreconfigured certificatewith the newly obtainedone.

Internal NMSCertificate

Certificate List Include two Certificates:Trust Certificate.CRL.

Set SBICertificate

Certs folder Default folder:default.Defaultpath:D:\oss\server\etc\ssl\nemanager\default.

Certs Path

Set U2100Certificate

Identity Certificate File Name:

PFX Password:

Trust Certificate File Name:

Set OtherCertificate

SSL Client Certificate File Name:

PFX Password:

SSL Server Certificate File Name:

PFX Password:

SecurityHardening

Whether to enable security hardening For details, see section Selecting the SecurityHardening Tool in U2000 Planning Guide.

Set NTP Configuring the server asan NTP client

NTP server IP address: For details, see section NTP Service Planning inU2000 Planning Guide.

Select one from the threeparameters.

Configuring the server asthe intermediate-levelNTP time server

Upper-layer NTP server IP address:

Configuring the server asthe highest-level NTPtime server

-

Set Route Routenetworksegment 1

Destinationnetwork :

Subnetmask:

Gateway: For details, see section Route Planning in U2000Planning Guide.

Routenetworksegment 2


Subnetmask:

Gateway:

... Destinationnetwork :

Subnetmask:

Gateway:

Routenetworksegment N


Subnetmask:

Gateway:

Set Network Single-NIC Logicalnetworkinterfacesname:

IP Address: Netmask For details, see section IP Address Planning for aLocal HA System (Solaris) in U2000 Planning Guide.

Other parameters usedefault values. Select anetworking solution.

Double-NICscheme(withoutIPMP)

Logicalnetworkinterfacesname:

IP Address: Netmask

Double-NICScheme(with IPMP)

Logicalnetworkinterfacesname:

IP Address: Netmask

Set Host Name Host Name: For details, see section Host Name Planning inU2000 Planning Guide.

Parent topic: Commissioning Preparation



1.5.1.2 Checking Hardware ConnectionsThis topic describes how to check hardware installation and cable connections before installing a U2000. If hardware is improperly installed or cable isimproperly connected, unexpected error may occur during installation of the U2000.

Prerequisites

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

Procedure

1. Ensure that the power cables and ground wires for all components are tightly connected and in good contact and that the polarities are properlyplaced.

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, seeU2000 Hardware Installation Guide (Huawei N610E cabinet).

2. Ensure that all cables are bundled and free of visible damage.

3. Check hardware connections and network cable connections according to the hardware connection diagram.

NOTE:Configuring disk arrays is optional.

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 thenetwork, the U2000 fails to synchronize network configurations or be started. Configuring the system IP address for the network interface with the smallest interfaceserial number is preferred. For example, network interface bge0 with the serial number of 0 can be used for the M5000 server.

The following hardware connection diagrams are based on a single-NIC network configuration scheme. For details about a single-NIC network configuration scheme,see Collecting Installation Information. The hardware connections based on other network configuration schemes are similar.

The following figure shows the hardware connection of the Netra T4-1 server.

Figure 1 Hardware connection for the Netra T4-1 server that is not connected to disk arrays

Figure 2 Hardware connection for the Netra T4-1 server that is connected to the OceanStor S3900

NOTE:If you need to connect Netra T4-1server to a disk array, you need to prepare HBA cards.











The following figure shows the hardware connection of the T5220 server.

NOTE:If you need to connect T5220 server to a disk array, you need to prepare HBA cards.

Figure 7 Hardware connection for the T5220 server that is not connected to disk arrays





Figure 10 Hardware connection for the T5220 server that is connected to the StorageTek 2540



















4. Check the plugs and sockets.

a. Ensure that the latches of cable plugs are locked fast.

b. Ensure that the pins in each socket are complete and in good order. Curved pins may cause short circuits.

5. Ensure that the connections between the server and disk arrays and between switches and routers are correct.

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.

Parent topic: Commissioning Preparation

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

Powering On a ServerThis topic describes how to power on a server. The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server, M4000/M5000 server, and disk array are used asexamples to explain how to power on a server based on the server type and disk array type.

Commissioning System ParametersAfter the U2000 is installed initially, you must use the commissioning tool to adjust system parameters, such as the instance name, IP address, and hostname. You do not need to modify parameters that do not require adjustment.

Connecting the Primary and Secondary SitesThis topic describes how to connect the primary and secondary sites using the MSuite. After the U2000 is installed on the primary and secondary sites,you must connect the primary and secondary sites to establish a high availability system.

Commissioning U2000 ParametersThis topic describes how to commission U2000 Client parameters after the U2000 is installed.

Parent topic: Commissioning the U2000

1.5.2.1 Powering On a ServerThis topic describes how to power on a server. The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server, M4000/M5000 server, and disk array are used asexamples to explain how to power on a server based on the server type and disk array type.





NOTICE:








NOTE:


M4000/M5000 Server









3. Press the power switch of the workstation, which is identified by . Wait 2 to 3 minutes. If front indicator of the server is on (changes to steadygreen), the server starts up and performs self-diagnosis.



Disk Array

NOTICE:













Parent topic: Performing Commissioning

1.5.2.2 Commissioning System ParametersAfter the U2000 is installed initially, you must use the commissioning tool to adjust system parameters, such as the instance name, IP address, and host name.You do not need to modify parameters that do not require adjustment.

Prerequisites

A PC or laptop must be obtained.

A network cable must be obtained.



The remote command login software, such as PuTTY, has been obtained.

Commissioning parameters have been planned and a commissioning parameter table is obtained. For details, see Obtaining CommissioningParameters.

The server has been powered on. For details, see Powering On a Server.

The primary and secondary sites have been separated. See Separating the Primary Site from the Secondary Site.

Context

For the High Availability System (Solaris), you must perform the following operations to commission system parameters on both the primary andsecondary sites.

The commissioning tool is used only after the initial installation of the U2000 is complete. Do not use the commissioning tool after the U2000 hasrunning for a period of time. If system parameters need to be commissioned, see section MSuite in the U2000 Administrator Guide.

Procedure

1. On the back panel of the U2000 server, select a port configured with a system IP address and use a network cable to connect the port and the PC orlaptop.

NOTE:The preinstallation by default considers the ports marked as NET0 on the back panel of the server configured with system IP addresses.

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

NOTE:The preinstallation by default configures the system IP address as 10.9.1.1 and the subnet mask as255.255.255.0.

3. On the PC or laptop, use the remote GUI login software (such as VNC) to log in to the OS GUI desktop as the root user. For details, see Configurethe VNC service as the root user.

4. Log in to the VCS client of the server. For details, see How to Log in and Exit the VCS (Veritas Cluster Server).

5. On the VCS client, choose AppService > Resources and ensure that the NMSServer resource of the server is in the offline state and other resourcesare in the online state.

Figure 1 High Availability System (Solaris) resources (server is not connected to disk arrays)

Figure 2 High Availability System (Solaris) resources (server is connected to disk arrays)



NOTE:The resources of a high availability system vary according to the network configuration solution. Items displayed in the resource tree varies accordingly. For example,the appNIC resource is displayed only when a U2000 application IP address is set and IPMP is not configured for the application IP address, or the U2000 applicationIP address instead of the heartbeat or replication IP address reuses the system IP address and the IPMP is not configured for the system. You do not need to focus on thedifferences.If a resource icon is grayed out, the resource is in the offline state. If a resource icon is not grayed out, the resource is in the online state. As shown in Figure 1, theNMSServer resource is in the offline state and the BackupServer resource is in the online state.Check the status of all resources. Ensure that the NMSServer resource is in the offline state and other resources are in the online state.To check the status of the online resource, right-click the resource and choose online > Host Name from the shortcut menu. In the Question dialog box, click Yes.To check the status of the offline resource, right-click the resource and choose offline > Host Name from the shortcut menu. In the Question dialog box, click Yes.

6. Run the following command to check the running status of the U2000 process:$ daem_ps

NOTE:The process is stopped if the displayed information is empty.

7. Perform the following operations to commission system parameters:

a. On the PC or laptop, use the remote GUI login software to log in to the U2000 OS server as the ossuser user. For details, see Configurethe VNC service as the ossuser user.

b. Double-click the U2000 MSuite icon on the desktop. Wait about 1 minute. The Login dialog box is displayed.

c. Set login paremeters.

IP address: Use the default value 127.0.0.1.

Port : Use the default value 12212.

User name: Use the default value admin.

Password: Use the default value Changeme_123.

d. Click Login.

NOTE:When accessing Client of NMS maintenance suite, a progress indicating the progress of querying components and instances is displayed. Wait patiently.NMS maintenance suite is in single-user mode. Only one Client of NMS maintenance suite can perform login at a time.

8. Perform the following operations to implement system commissioning:

a. Choose Tools > Commissioning Tool from the MSuite client main menu to access the Information dialog box.

b. Read the information carefully and click Start to access the system commissioning window.

9. Configure the commissioning items based on the planned commissioning parameter table. For details about the commissioning parameters, seeObtaining Commissioning Parameters.

NOTICE:

If a message asking you to refer to the associated section in the installation guide is displayed during system commissioning, the systemneeds to be manually commissioned.The number of instances of every deployment package on the primary and secondary sites must be the same. Otherwise, the primary and



secondary sites cannot be connected properly.The passwords of the database user sa on the primary and secondary sites and the password of the U2000 database user dbuser must be thesame.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.After security hardening is enabled, you cannot use the commissioning tool to change the password of the OS user. For details about themethod of changing a password, see How to Change the OS User Password.

Figure 3 Adding Instance

10. After system parameters are commissioned.

11. Run the following command to shut down the U2000, see Stopping the U2000 Server Processes.

12. Run the following command to disable the Sybase database service, see Shutting Down the Database.

13. To stop the VCS service, see Stopping the VCS Service.

14. Run the following commands to restart the OS to make the modifications take effect:$ su - root# sync;sync;sync;sync# shutdown -y -g0 -i6

NOTE:Enter the root user password as prompted. The default password is Changeme_123 . For system security, modify the default password and remember the new password. Fordetails, see How to Change the OS User Password.

15. Disconnect the PC or laptop from the U2000 server and connect the U2000 to the network.

Follow-up Procedure

If the server IP address is changed during commissioning, you must manually configure the hardware alarm monitoring function. For details about thereplacement procedure, see Configuring the Monitoring Function for an S3900 Disk Array and Configuring the Monitoring Function for an S2600Disk Array.

If the M4000/M5000 server controller IP addresses is changed during commissioning, you must manually configure the hardware alarm monitoringfunction. For details about the replacement procedure, see Setting Servers for Monitoring (M4000/M5000).


1.5.2.3 Connecting the Primary and Secondary SitesThis topic describes how to connect the primary and secondary sites using the MSuite. After the U2000 is installed on the primary and secondary sites, youmust connect the primary and secondary sites to establish a high availability system.

Prerequisites

The preceding steps for installing the primary and secondary sites must be complete.

Database sa user password, and database NMS user password must be the same on the primary and secondary sites.

The installed components and deployed instances must be the same on the primary and secondary sites.

The operations on the primary and secondary sites must be the same. For example, if instances are added on the primary site and then deleted,instances must be added on the secondary site and then deleted.

Ensure that the network between the primary and secondary sites is smooth.

All VCS clients on the primary and secondary sites must be logged out of.

MSuite client on the secondary site must be logged out of.

Ensure that the host names of primary and secondary sites are different.

Ensure that VVR ports can be connected.

Context

Connect the primary and secondary sites in either of the following modes:

Mode 1 (recommended): GUI mode. If you are not familiar with common commands of the Solaris OS, connecting the primary and secondary sitesin GUI mode is recommended.

Mode 2: CLI mode. If you fail to log in to the OS in GUI mode, using primary and secondary sites the CLI mode is recommended.

Procedure

Mode 1 (recommended): Connect the primary and secondary sites in GUI mode.

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










Parameter Settings







5. Choose Deploy > Synchronize Primary and Secondary Sites.

6. Enter the application IP address and the MSuite password of the remote site, and click OK. A progress bar is displayed, indicating theprogress of synchronizing the primary and secondary sites. It takes about 150 minutes to complete the process. Wait patiently until thedialog box indicating the successful of synchronizing the primary and secondary sites is displayed.

7. Click OK. Wait patiently until the dialog box shown in the following figure is displayed.

NOTE:The duration of data replication depends on the stability of the network bandwidth and the volume of the data to be replicated.In the lower-left corner of the MSuite, refresh the data replication status of the primary and secondary sites. If the MSuite prompts Replication status:100%, Finished., data replication is complete.If the status keeps Replication status: 99% remain for a long time, see How to Solve the Problem Where the Amount of Remaining Data Keeps 99%During Data Synchronization in a High Availability System to solve the problem. Then use the MSuite to check the replication status.



Mode 2: Connect the primary and secondary sites in CLI mode.

1. Ensure that the primary and secondary sites on the MSuite server have been started. For details, see 1 in mode 1.

2. Log in to the OS of the primary site as the ossuser user and run the following commands:


$ cd /opt/oss/client/engineering$ ./startclient.sh deploy -ip 127.0.0.1 -port 12212 -username admin buildHA -secondaryip Application_IP _address _of _the _peer _siteEnter the MSuite login password[]:Enter the remote node maintenance suite password[]:

3. On the primary site, check data replication status as the root user.# vradmin -g datadg repstatus datarvg

NOTE:To save time, running the preceding command every half an hour is recommended to check the data replication status.

A message similar to the following will be displayed:Replicated Data Set: datarvgPrimary: Host name: 10.9.1.1 RVG name: datarvg DG name: datadg RVG state: enabled for I/O Data volumes: 1 VSets: 0 SRL name: srl_vol SRL size: 1.00 G Total secondaries: 1


NOTE:If Replication status is displayed as resync in progress (autosync), Data status is displayed as inconsistent, and the value of Logging to is becomingsmaller, data is being duplicated between primary and secondary sites.If Replication status is displayed as replicating (connected) and Data status is displayed as consistent, up-to-date, data duplication of the high availabilitysystem (Veritas hot standby) is complete.If Replication status is displayed as logging to DCM (needs dcm resynchronization), you must run the vradmin -g datadg resync datarvg command onthe primary site as the root user to perform manual synchronization.The duration of data replication depends on the stability of the network bandwidth and the volume of the data to be replicated.




1.5.2.4 Commissioning U2000 ParametersThis topic describes how to commission U2000 Client parameters after the U2000 is installed.

Prerequisites

If the delivered server has been preinstalled, ensure that system commissioning is complete. For details, see Commissioning System Parameters.

If the delivered server has not been preinstalled, ensure that the U2000 is installed. For details, see Installing the U2000.

Ensure that the U2000 license has been loaded. For details, see Loading a U2000 License.

The remote command login software, such as PuTTY, has been obtained.

NOTE:The standard resolution of 1024 x 768 is recommended. Otherwise, the U2000 client page may not be displayed completely. If the page contains a lot of contents, use a higher resolutionwith the same ratio, such as 1152 x 864.

Context

The U2000 commissioning parameters cover communication security, U2000 user security policy, communication between the U2000 and NEs, alarmfunction, and common U2000 configurations.

Procedure

1. Use the PuTTY to enable the VNC service for the ossuser user. Log in to the primary site GUI desktop as the ossuser user. For details, seeConfigure the VNC service as the ossuser user.

2. On the GUI desktop, right-click and choose Open Terminal from the shortcut menu.

3. Run the following command to check whether the U2000 is started:$ daem_ps

Information similar to the following is displayed: ossuser 27069 1 0 10:31:39 ? 1:39 imapmrb ossuser 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start ossuser 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start ossuser 27086 1 0 10:31:39 ? 0:09 imapeventmgr ossuser 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start ossuser 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start

NOTE:If the command output contains imap_sysmonitor -cmd start, the U2000 is started.

4. If the U2000 process is not started, run the following commands to start it:$ hagrp -online AppService -sys hostname

Enter the user name and password of the VCS client.


5. Log in to U2000 client.

a. Log in to the OS where the client program is installed.

In Windows, log in to the OS as a user with the administrator rights.

In Solaris, log in to the OS as the ossuser user.

b. On the OS desktop, double-click the U2000 Client shortcut icon. The Login dialog box is displayed.

c. 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 clickLogin. The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The passwordmust be changed during the first login to ensure system security. Keep the password confidential and change it regularly.

6. Perform the following operations to change the display style to the traditional style for the client:

a. Choose File > Preferences from the U2000 Client main menu.

b. Choose Client Display Style from the navigation tree on the Preferences page.

c. Select Traditional style and click OK.

d. Re-log in to the U2000 client.

7. Choose Administration > NMS Commissioning Wizard from the U2000 Client main menu, as shown in Figure 1.

Figure 1 NMS Commissioning Wizard



8. Commission U2000 parameters as prompted.

Result

After U2000 parameters are commissioned, the U2000 and NEs can communicate with each other properly, and the U2000 works properly.


1.6 FAQsThis topic provides answers to the most frequent questions concerning the installation.

Solaris OSThis topic provides answers to FAQs about clients installed on Solaris OS.

Veritas HA SystemThis topic covers FAQs about the Veritas HA system.

Sybase DatabaseThis topic covers FAQs about the Sybase database.

U2000 SystemThis topic covers FAQs about the U2000 system.

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


1.6.1 Solaris OSThis topic provides answers to FAQs about clients installed on Solaris OS.

Network Configurations of the WorkstationThis topic provides answers to FAQs about the network configurations of the workstation.

System Settings of the WorkstationThis topic covers FAQs about workstation system settings.

FTP and Telnet Service ConfigurationThis topic covers the FAQs about the FTP and Telnet service configuration.



Usage and Maintenance of WorkstationThis topic covers the FAQs about the usage and maintenance of the workstation.

Parent topic: FAQs

1.6.1.1 Network Configurations of the WorkstationThis topic provides answers to FAQs about the network configurations of the workstation.

How to Add the Default Route

How to Add a Static Route

How to Query the Gateway of a Sun Workstation

How to Check the NIC Type of a Server

How to Check Whether an NIC Has Multiple IP Addresses on Solaris

How to Delete Excess IP Addresses of an NIC on Solaris

How to Set IP Addresses for Unused NICs on a Workstation

How to Enable IPv4 Forwarding Between NICs

How to Configure a Workstation NIC to Work in Full-Duplex Mode

Parent topic: Solaris OS

1.6.1.1.1 How to Add the Default RouteQuestion

How do I add the default route?

Answer

1. Log in the OS as user root.

2. Open a terminal window in the Solaris OS.

3. Run the following command:# vi /etc/defaultrouter

4. Enter an IP address as the default route in the file, for example, 10.9.1.254.

5. Press Esc. Then, run the :wq command to save the file and exit the vi editor.

6. Run the following commands to restart the server:# sync;sync;sync;sync# shutdown -y -g0 -i6

7. Log in to the Solaris OS as the root user. Run the netstat -nr command to view the default route of the system.

Parent topic: Network Configurations of the Workstation

1.6.1.1.2 How to Add a Static RouteQuestion

How do I add a static route?

Answer

1. Log in to the server as the root user and run the following command to add a static route:# route -p add destination network segment address -netmask destination network segment subnet mask gateway IP address

NOTE:destination network segment address: network segment on which the IP address of the computer connecting to the U2000 server is locateddestination network segment subnet mask: subnet mask of the network segment on which the IP address of the computer connecting to the U2000 server is locatedgateway IP address: gateway IP address of the network on which the U2000 server is located

For example, add a static route from the U2000 server (IP address: 192.168.1.1; subnet mask: 255.255.255.0; gateway IP address: 192.168.1.254) to



a remote computer (IP address: 10.67.56.226; subnet mask: 255.255.254.0; gateway IP address: 10.67.56.1).# route -p add 10.67.56.0 -netmask 255.255.254.0 192.168.1.254

2. Run the following command in the CLI to check that the route has been added:# netstat -nrRouting Table: IPv4 Destination Gateway Flags Ref Use Interface-------------------- -------------------- ----- ----- ---------- ---------10.67.56.0 192.168.1.254 UG 1 61

If the preceding information is displayed, the static route has been added. Otherwise, add a static route again.


1.6.1.1.3 How to Query the Gateway of a Sun WorkstationQuestion

How do I query the gateway of a Sun workstation?

Answer

1. Log in to the OS as user root and open the terminal window.

2. Run the following command to query the workstation:# netstat -nr

The following message will be displayed:Routing Table: IPv4 Destination Gateway Flags Ref Use Interface-------------------- -------------------- ----- ----- ------ ---------10.71.224.0 10.71.225.24 U 1 1006 bge0224.0.0.0 10.71.225.24 U 1 0 bge0default 10.71.224.1 UG 1 114902127.0.0.1 127.0.0.1 UH 6 25558 lo0

NOTE:The contents displayed on the terminal will vary according to the route configuration.The gateway with UG listed in the Flags is the gateway of the workstation. In this example, the IP address of the workstation gateway is 10.71.224.1. There are fiveflags (UGHDM) for a specified route.


1.6.1.1.4 How to Check the NIC Type of a ServerQuestion

How do I check the NIC type of a server?

Answer

You can run the more /etc/path_to_inst | grep network command as user root to check the NIC type of a server.


1.6.1.1.5 How to Check Whether an NIC Has Multiple IP Addresses onSolarisQuestion

How to check whether an NIC has multiple IP addresses on Solaris?

Answer

1. Log in to the Solaris OS as the root user.

2. To check whether an NIC has multiple IP addresses, run the following command:# ifconfig -a

Information similar to the following is displayed:lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>mtu 8232 index 1 inet 127.0.0.1 netmask ff000000bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>mtu 1500 index 2



inet 10.71.210.182 netmask fffffe00 broadcast 10.71.211.255 ether 0:b:5d:e5:10:8bge0: 1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>mtu 1500 index 2 inet 192.168.0.22 netmask fffffe00 broadcast 192.168.0.255 ether 0:3:ba:be:b3:59

NOTE:In NIC name: x, NIC name specifies the name of an NIC and x is a digit. If x is 1, the NIC has 2 IP addresses; if x is n, the NIC has n+1 addresses. NIC name and x vary accordingto the machine model and IP addresses. In this example, the NIC has two IP addresses, and bge0 and bge0:1 specify two IP addresses.


1.6.1.1.6 How to Delete Excess IP Addresses of an NIC on SolarisQuestion

How to delete excess IP addresses of an NIC on Solaris?

Answer

If an NIC has multiple IP addresses, run the following command to delete excess IP addresses. For details about how to check whether excess IP addresseshave been set for an NIC, see How to Check Whether an NIC Has Multiple IP Addresses on Solaris.# ifconfig NIC name:x unplumb

NOTE:In the command, NIC name and x vary according to the machine model and set IP addresses.

For example, if NIC name is bge0 and x is 1, run the following command to delete IP addresses corresponding to bge0: 1: # ifconfig bge0:1 unplumb


1.6.1.1.7 How to Set IP Addresses for Unused NICs on a WorkstationQuestion

How do I set IP addresses for unused NICs on a workstation after a Solaris OS is installed?

Answer

On Solaris, the common method of setting IP addresses is to modify the following files:

/etc/hostname.NIC name

/etc/hosts

/etc/inet/ipnodes

/etc/netmasks

1. Log in to Solaris as the root user.

2. Perform the following operations to configure the /etc/hostname.NIC name file:

a. Run the following command to add and edit the /etc/hostname.NIC name file:# vi /etc/hostname.NIC name

NOTE:NIC name indicates the name of an NIC for which an IP address is to be set, for example. e1000g1.

b. Enter a host name, for example, NMSserver, in the file.

NOTICE:If multiple network interfaces need to be configured, host names for the network interfaces must be different.

c. Save and exit the file.

3. Perform the following operations to configure the /etc/hosts file:

NOTICE:If the IP addresses of multiple network interfaces must be configured, ensure that the IP addresses of different network interfaces must be located ondifferent network segments.

a. Run the following command to edit the /etc/hosts file:# vi /etc/hosts

b. Add a line to the file, and enter an IP address and host name, for example, 10.9.9.1 NMSserver.




4. Perform the following operations to configure the /etc/inet/ipnodes file:

NOTICE:The host names and IP addresses configured in the /etc/inet/ipnodes and /etc/hosts files must be the same.

a. Run the following command to edit the /etc/inet/ipnodes file:# vi /etc/inet/ipnodes

b. Add a line to the file, and enter an IP address and host name, for example, 10.9.9.1 NMSserver.


5. Perform the following operations to configure the /etc/netmasks:

a. Run the following command to edit the /etc/netmasks file:# vi /etc/netmasks

b. Add a line to the file and enter a routing segment, for example, 10.9.9.0 255.255.255.0.

NOTE:10.9.9.0 is the network segment of 10.9.9.1 and 255.255.255.0 is the subnet mask.


6. Run the following commands to restart the workstation:# sync;sync;sync;sync# shutdown -y -g0 -i6

7. After the workstation is restarted, log in to Solaris as the root user and run the ifconfig -a command to view the configured IP addresses.


1.6.1.1.8 How to Enable IPv4 Forwarding Between NICsQuestion

How do I enable IPv4 forwarding between NICs after Solaris is installed?

Answer


2. Run the following command to configure IPv4 forwarding:# routeadm -e ipv4-forwarding -u

3. Run the following command to check whether the configuration is successful:# routeadm

If the IPv4 configurations are displayed and the system status is enabled, the configuration is successful.


1.6.1.1.9 How to Configure a Workstation NIC to Work in Full-Duplex ModeQuestion

On Solaris 10, how do I configure a workstation NIC to work in full-duplex mode?

Answer

1. Run the following command to get in the directory by root user.# cd /etc/rc3.d

2. Run the vi editor create the S99setbge file, input the following commands and save it:# vi S99setbgendd -set /dev/bge0 adv_1000fdx_cap 0ndd -set /dev/bge0 adv_1000hdx_cap 0ndd -set /dev/bge0 adv_100fdx_cap 1ndd -set /dev/bge0 adv_100hdx_cap 0ndd -set /dev/bge0 adv_10fdx_cap 0ndd -set /dev/bge0 adv_10hdx_cap 0ndd -set /dev/bge0 adv_autoneg_cap 0ndd -set /dev/bge0 adv_pause_cap 0ndd -set /dev/bge0 adv_asym_pause_cap 0



NOTE:The meanings of the preceding commands are as follows:ndd -set /dev/bge0 adv_1000fdx_cap 0 (off 1000M Full Duplex)ndd -set /dev/bge0 adv_1000hdx_cap 0 (off 1000M Half Duplex)ndd -set /dev/bge0 adv_100fdx_cap 1 (on 100M Full Duplex)ndd -set /dev/bge0 adv_100hdx_cap 0 (off 100M Half Duplex)ndd -set /dev/bge0 adv_10fdx_cap 0 (off 10M Full Duplex)ndd -set /dev/bge0 adv_10hdx_cap 0 (off 10M Half Duplex)ndd -set /dev/bge0 adv_autoneg_cap 0 (off Auto-negotiation)

NOTICE:Here, bge0 indicates the name of the NIC to be configured. Enter a value as required.

3. Run the following command to modify the S99setbge file attribute:# chmod 744 S99setbge# chgrp sys S99setbge

4. Run the following command to check the S99setbge file attribute:# ls -l S99setbge

5. Run the following command to restart the system, make the configuration be succeed:# sync;sync;sync;sync;# shutdown -y -g0 -i6

6. Run the following command to check the network card attribute:# kstat -p bge | grep link_

If the following information is displayed, the 100M full-duplex mode has been successfully configured for bge0:......bge:0:parameters:link_duplex 2......bge:0:parameters:link_speed 100......

Here, the mappings between link_duplex values and attributes are as follows:

The value 0 indicates Down.

The value 1 indicates Half Duplex.

The value 2 indicates Full Duplex.


1.6.1.2 System Settings of the WorkstationThis topic covers FAQs about workstation system settings.

How to Boot Up the Workstation from the CD-ROM Drive

How to Set the Interface Language of Solaris OS

How to Call the GUI Management Tool in Solaris 10 OS

How to Switch to the Multi-user Mode or Single-user Mode

How to Open the Terminal Window on the Desktop in the Java Desk System

How to Query the Drive of the Default Startup Disk of the Workstation

How to Operate the CD-ROM

How to Solve the Problem that the Current File System Is Not in the UFS Format

How to Use the VNC to Remotely Access a Workstation


1.6.1.2.1 How to Boot Up the Workstation from the CD-ROM DriveQuestion

How do I boot up the workstation from the CD-ROM drive?

Answer

1. At the # prompt, run the following command to display the OK prompt (OK>):



# init 0

2. After the OK prompt is displayed, insert the installation DVD of Solaris OS into the CD-ROM drive.

3. Run the following command and press Enter. The workstation starts from the CD-ROM drive.

If the server model is Netra T4-1/Oracle T4-1/T5220/M4000/M5000, run the following command:ok boot cdrom

If the server model is Oracle T4-2, run the following command:ok boot dvd

Press Enter. The system will restart. After five minutes, the system will prompt you to select the language for the installation program.

Parent topic: System Settings of the Workstation

1.6.1.2.2 How to Set the Interface Language of Solaris OSQuestion

How do I set the interface language of Solaris OS?

Answer

1. Power on the workstation, and start Solaris OS.

2. Choose Options > Language. A dialog box will be displayed prompting you to select a language.

3. Select the system language from the list box according to the conditions at your site.

4. Click OK.If you want to save the setting of the system language, select Set selected language as default.


1.6.1.2.3 How to Call the GUI Management Tool in Solaris 10 OSQuestion

How do I call the GUI management tool in Solaris 10 OS?

Answer

Log in to Solaris 10 OS through the GUI. Then, run the following command to call the GUI management tool:# smc &


1.6.1.2.4 How to Switch to the Multi-user Mode or Single-user ModeQuestion

How do I switch to the multi-user mode or single-user mode?

Answer











-> cd /HOST-> ls





















SPARC Enterprise T5220, No Keyboard



Copyright 2008 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.28.0, 8064 MB memory available, Serial #85369820.Ethernet address 0:21:28:16:a3:dc, Host ID: 8516a3dc.











b. Enter y.






f. Enter y.





OK

2. Run the following command to switch to the Multi-user Mode or Single-user Mode.



Run the following command to switch to the multi-user mode:ok boot

Run the following command to switch to the single-user mode:ok boot -s


1.6.1.2.5 How to Open the Terminal Window on the Desktop in the JavaDesk SystemQuestion

How do I open the terminal window on the desktop in the Java Desk System (JDS)?

Answer

1. Open the desktop in the JDS.

a. Enter the user name for login, such as root.

b. Choose Options > Session > Java Desktop System to select the JDS.

c. Click OK. Enter the password for the user.

d. Click OK to log in to the desktop in the JDS.

2. Right-click on the desktop in the JDS and choose Open Terminal from the shortcut menu to open a terminal window.


1.6.1.2.6 How to Query the Drive of the Default Startup Disk of theWorkstationQuestion

On the Netra T4-1/Oracle T4-1/Oracle T4-2 server, the system starts from hard disk PhyNum 0 by default. How do I query the drive of hard disk PhyNum 0?

Answer

After the system enters the OK mode, run the following command to query the drive of the startup disk:{0} ok probe-scsi-all

Information similar to the following is displayed:/pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00

/pci@400/pci@2/pci@0/pci@c/LSI,sas@0

FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00

/pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0,1 QLogic QLE2562 Host Adapter FCode(SPARC): 2.03 06/30/08 Firmware version 4.03.02 Fibre Channel Link down Possible causes: No cable, incorrect connection mode or data rate SFP state: 8Gb Present

/pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0 QLogic QLE2562 Host Adapter FCode(SPARC): 2.03 06/30/08 Firmware version 4.03.02 Fibre Channel Link down Possible causes: No cable, incorrect connection mode or data rate SFP state: 8Gb Present

/pci@400/pci@2/pci@0/pci@4/scsi@0 FCode Version 1.00.61, MPT Version 2.00, Firmware Version 9.00.00.00

Target 9 Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB SASDeviceName 5000cca0253b71ac SASAddress 5000cca0253b71ad PhyNum 0 Target a Unit 0 Removable Read Only device TEAC DV-W28SS-V 1.0B SATA device PhyNum 6

/pci@400/pci@1/pci@0/pci@8/SUNW,qlc@0,1 QLogic QLE2562 Host Adapter FCode(SPARC): 2.03 06/30/08 Firmware version 4.03.02



Fibre Channel Link down Possible causes: No cable, incorrect connection mode or data rate SFP state: 8Gb Present

/pci@400/pci@1/pci@0/pci@8/SUNW,qlc@0 QLogic QLE2562 Host Adapter FCode(SPARC): 2.03 06/30/08 Firmware version 4.03.02 Fibre Channel Link down Possible causes: No cable, incorrect connection mode or data rate SFP state: 8Gb Present

/pci@400/pci@1/pci@0/pci@4/scsi@0 FCode Version 1.00.61, MPT Version 2.00, Firmware Version 9.00.00.00

Target 9 Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB SASDeviceName 5000cca0253d1400 SASAddress 5000cca0253d1401 PhyNum 0

NOTE:

pci@1 specifies the first controller and pci@2 specifies the second controller.If PhyNum 0 is available on the first controller but not on the second controller, the system by default starts from the hard disk of the first controller. Record 5000cca0253d1400corresponding to PhyNum 0 on the first controller as the drive of the startup disk.If PhyNum 0 is available on the second controller but not on the first controller, the system by default starts from the hard disk of the second controller. Record5000cca0253b71ac corresponding to PhyNum 0 on the second controller as the drive of the startup disk.If PhyNum 0 is available on both the first and second controllers, the system by default starts from the hard disk of the first controller. Record 5000cca0253d1400 correspondingto PhyNum 0 on the first controller as the drive of the startup disk.

The preceding command output is used as an example. In this example, 5000cca0253d1400 corresponding to PhyNum 0 on the first controller is the drive ofthe startup disk. Before disk partition, select the drive of the startup disk as the first hard disk.


1.6.1.2.7 How to Operate the CD-ROMQuestion

How do I operate the CD-ROM?

Answer

1. If the Sun workstation has a built-in CD-ROM drive, perform the following operation:The system automatically installs the CD-ROM to the /cdrom directory after startup. If there is a CD-ROM in the CD-ROM drive, view the contentsof the CD-ROM after accessing the /cdrom directory.

2. If the Sun workstation has an external CD-ROM drive, perform the following operation:Power on the CD-ROM drive after the SCSI wire is connected. Then, power on the workstation. The system automatically identifies and installs theCD-ROM to the /cdrom directory after startup.

3. Use appropriate commands to open the CD-ROM drive.If there is a CD-ROM in the CD-ROM drive, run appropriate commands to open the CD-ROM drive.Verify that the CD-ROM is not being used by any program and exit the directory for the CD-ROM. Run the following command as user root:# 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 thedrive mounting position.

# df -h.../vol/dev/dsk/c2t6d0/solaris 2.8G 2.8G 0k 100% /cdrom/solarisThe drive mounting position is solaris. Run the eject solaris command to eject the DVD.

Open the CD-ROM drive and take out the CD-ROM.

NOTE:If the system prompts "Device busy" and the CD-ROM cannot be ejected, run the following command as user root:

# svcadm disable volfs

Press the eject button on the drive panel to take out the CD-ROM.

The drive becomes unavailable in this situation. Run the following command:

# svcadm enable volfs

The CD-ROM drive can then be used.

4. Install or start the system from the CD-ROM.Insert the CD-ROM to the drive, and then run the following command at the ok prompt on the workstation:





Press Enter. The system will restart. After five minutes, the system will prompt you to select the language for the installation program.By doing this, you can install or start the system from the CD-ROM.

5. Check the SCSI device mounted on the workstation.Enter the following command at the ok prompt:

ok probe-scsi

By doing this, you can check the SCSI device mounted on the workstation. This command is usually used to verify that the CD-ROM drive iscorrectly mounted.


1.6.1.2.8 How to Solve the Problem that the Current File System Is Not in theUFS FormatQuestion

In Solaris 10, the Hard Disk Monitor tab page is empty if the file system is not in the UFS format. How to solve this problem?

Answer

Contact Huawei technical support engineers to assist in reinstalling the operating system and U2000. Change the file system format to UFS duringreinstallation of the operating system.

If the live network does not allow reinstallation of the operating system or U2000, perform the following operations:

1. Log in to the operating system of the server as the ossuser user.

2. Run the following command to view the current file system format:$ cat /etc/vfstab

Information similar to the following is displayed:#device device mount FS fsck mount mount#to mount to fsck point type pass at boot options#fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/md/dsk/d31 - - swap - no -/dev/md/dsk/d30 /dev/md/rdsk/d30 / ufs 1 no -/dev/md/dsk/d36 /dev/md/rdsk/d36 /var ufs 1 no -/dev/md/dsk/d37 /dev/md/rdsk/d37 /export/home ufs 2 yes -/dev/md/dsk/d65 /dev/md/rdsk/d65 /opt ufs 2 yes -/dev/md/dsk/d35 /dev/md/rdsk/d35 /opt/backup ufs 2 yes -/dev/md/dsk/d95 /dev/md/rdsk/d95 /opt/sybase ufs 2 yes -/devices - /devices devfs - no -sharefs - /etc/dfs/sharetab sharefs - no -ctfs - /system/contract ctfs - no -objfs - /system/object objfs - no -swap - /tmp tmpfs - yes -

NOTE:The column to which FS type belongs indicates the format of the current file system. In this example, the file system is in the UFS format.

3. Run the following commands to add the type of disks to be monitored:$ SettingTool -cmd setparam -path /imap/common/monitor/monitorgroup/SupportFS -value "zfs;vxfs;ufs"

NOTE:The following disk types are supported: VxFS, UFS, and ZFS.Different disk types are separated by columns (;).The default disk type is UFS.

4. Run the following command to check whether desired disks are added:$ SettingTool /imap/common/monitor/monitorgroup/SupportFS

If the following information is displayed, the desired disks have been successfully added.zfs;vxfs;ufs

5. Restart the ResourceMonitor process.

a. Run the following command to obtain the ID of the ResourceMonitor process:$ ps -ef | grep ResourceMonitor

Information similar to the following is displayed:ossuser 9252 1 0 15:41:58 ? 0:00 /opt/oss/server/platform/bin/ResourceMonitor -cmd start >/dev/null 2>&1ossuser 9268 9130 0 15:42:06 pts/1 0:00 grep ResourceMonitor

b. Run the following command to shut down the ResourceMonitor process:



$ kill -9 process ID

In this example, run the kill -9 9252 command to shut down the ResourceMonitor process.

6. Wait about 1 minute. The ResourceMonitor process automatically starts.

7. After the preceding configurations have been performed, wait 5 minutes. Then relog in to the System Monitor. The associated diskinformation will be displayed on the Hard Disk Monitor tab page.


1.6.1.2.9 How to Use the VNC to Remotely Access a WorkstationQuestion

How do I use the VNC to remotely access a workstation?

Answer

The VNC is a component of Solaris. It is a typical thin client software. The graphics processor service runs on the server and multiple instances can be created.The VNC advantage is that a remote computer can access the server using the Internet Explorer. If the connection is torn down, the desktop can be held bylogging in with the same user name and port number. The remotely run applications will not be interrupted due to the network disconnection.

NOTICE:

After the following operations are performed, you can remotely log in to Solaris as a specified OS user and retain the session. If the connection is torndown and you log in using the same port as the same user, the session will be retained.If the use of the VNC to remotely log in to the Solaris OS needs to be performed as the root user, the login user must be root. If the use of the VNC toremotely log in to the Solaris OS needs to be performed as the ossuser user, log in to the Solaris OS as the ossuser user after the U2000 is installed.Do not use the Java desktop mode to log in to the OS. Using Telnet/SSH (more secure, recommended) to log in to the OS is recommended. Afterlogin succeeds, run the associated commands to start the VNC service.

Run the following command to check the svc:/milestone/network:defaultstatus:# svcs |grep svc:/milestone/network:default

Information similar to the following is displayed:online 20:17:02 svc:/milestone/network:default

If the command output contains online, you do not need to run the following commands. If the command output contains maintenance or offline, run thefollowing commands to change the status of svc:/milestone/network:default to online.# svcadm clear svc:/milestone/network:default# svcadm enable svc:/milestone/network:default# svcs |grep svc:/milestone/network:default

If the status of svc:/milestone/network:default is online, perform the following operations to configure the VNC service for the root or ossuser user:

Configure the VNC service as the root user.

1. Use the PuTTY tool to log in to the server as a root user.

2. Optional: Run the following command to set the password for user root to log in to the VNC. If the VNC login password for user rootalready exists, skip this step.# vncpasswd

A message similar to the following is displayed:Password:

An example password is Admin123. A password must consist of 6 to 8 characters. All characters entered using the keyboard, except theEnter key, will be considered as password components. Excessive characters will be automatically discarded. Passwords must be complexenough to ensure the security of the U2000. For example, a password must contain six or more characters of two types. The allowedcharacters are digits, letters, and special characters. Remember to use the vncpasswd command to change passwords regularly and keep thepasswords well.

a. Enter the password and press Enter.Verify:

b. Enter the password again 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.Remember the password that will be used for VNC login as user root.If the password is forgotten, log in to the OS as user root, run the vncpasswd command, and set a new password according to the message.

3. Run the following commands to enable the VNC services.# cd /opt/OSSICMR/tools/VNC# sh stop_vnc_root.sh

If the command output contains successfully, the VNC service corresponding to the root user is stopped. Run the following command:# 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 rootuser.

NOTE:If a message is displayed asking you to set the password, run the vncpasswd password as the root user to set the password.

4. Perform the following operations to create an SSH tunnel so that the communication between the server and VNC client is more secure. Ifthe PuTTY is stored in the D:\PuTTY path, the IP address of server 1 is 10.9.1.1, and the IP address of server 2 is 10.9.1.2, the VNCservice can be implemented as the root user for the two servers. You must ensure that the VNC service corresponding to the root user hasbeen started for both of the two servers.

a. On a PC or laptop, choose Start > Run. In the dialog box that is displayed, enter cmd to open a CLI.

b. Run the following command to navigate to the path where the PuTTY is located:C:\>cd /d D:\PuTTY\

c. Run the following command to create an SSH tunnel for the root user:D:\PuTTY>putty -L 5902:localhost:5902 -L 5802:localhost:5802 10.9.1.1D:\PuTTY>putty -L 5904:localhost:5902 10.9.1.2

NOTE:If the VNC needs to be connected to only one server, only the first command needs to be executed. If the VNC needs to be connected to twoservers, both of the two commands need to be executed.

Establish a connection with the server. In the PuTTY Security Alert dialog box, click Yes to confirm the connection to the server.

10.9.1.1 and 10.9.1.2 specify the IP addresses of server 1 and server 2.

d. In the PuTTY dialog box, enter the user name and password of the root user. The SSH tunnel for the root user is created.

NOTE:During operations on the GUI, do not shut down the PuTTY dialog box. Otherwise, the connection to the VNC client becomes abnormal.

If the security hardening policy is enabled on the system, enter the user name and password of the ossuser user in the PuTTY window tocomplete the creation of the SSH tunnel.

5. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5802 in the address bar. Then press Enter.

6. Perform the following operations to access the Solaris OS of the two servers:

Ensure that the value of Server in the VNC Viewer dialog box is localhost:2. Click OK. In the dialog box that is displayed, entera password and click OK to access the Solaris OS of server 1.

Repeat 5 and change the value of Server to localhost:4 in the VNC Viewer dialog box. Click OK. In the dialog box that isdisplayed, enter a password and click OK to access the Solaris OS of server 2.

NOTICE:

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.If the VNC needs to be used again, refer to this document to configure the VNC.If you need to use the VNC again after logging in to the server through the VNC and logging out of the root user in the GUI, referto this document to configure the VNC.

Configure the VNC service as the ossuser user.



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

2. Optional: Run the following command to set the password for user ossuser to log in to the VNC. If the VNC login password for userossuser already exists, skip this step.$ vncpasswd


An example password is Admin123. A password must consist of 6 to 8 characters. All characters entered using the keyboard, except theEnter key, will be considered as password components. Excessive characters will be automatically discarded. Passwords must be complexenough to ensure the security of the U2000. For example, a password must contain six or more characters of two types. The allowedcharacters are digits, letters, and special characters. Remember to use the vncpasswd command to change passwords regularly and keep thepasswords well.

a. Enter the password and press Enter.Verify:

b. Enter the password again 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.Remember the password that will be used for VNC login as user ossuser.If the password is forgotten, log in to the OS as user ossuser, run the vncpasswd command, and set a new password according to the message.

3. Run the following commands to enable the VNC services.$ su - rootpassword: password_of_root_user# cd /opt/OSSICMR/tools/VNC# sh stop_vnc_oss.sh# 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 userossuser

NOTE:If a message is displayed asking you to set the password, run the vncpasswd password as the ossuser user to set the password.

4. Perform the following operations to create an SSH tunnel for the ossuser user so that the communication between the server and VNCclient is more secure. If the PuTTY is stored in the D:\PuTTY path, the IP address of server 1 is 10.9.1.1, and the IP address of server 2 is10.9.1.2, the VNC service can be implemented as the ossuser user for the two servers. You must ensure that the VNC servicecorresponding to the ossuser user has been started for both of the two servers.

a. On a PC or laptop, choose Start > Run. In the dialog box that is displayed, enter cmd to open a CLI.

b. Run the following command to navigate to the path where the PuTTY is located:C:\>cd /d D:\PuTTY\

c. Run the following command to create an SSH tunnel for the ossuser user:D:\PuTTY>putty -L 5903:localhost:5903 -L 5803:localhost:5803 10.9.1.1D:\PuTTY>putty -L 5905:localhost:5903 10.9.1.2




d. In the PuTTY dialog box, enter the user name and password of the ossuser user. The SSH tunnel for the ossuser user is created.


5. Open the Internet Explorer of a PC or laptop. Enter http://localhost:5803 in the address bar. Then press Enter.



6. Perform the following operations to access the Solaris OS of the two servers:

Ensure that the value of Server in the VNC Viewer dialog box is localhost:3. Click OK. In the dialog box that is displayed, entera password and click OK to access the Solaris OS of server 1.

Repeat 5 and change the value of Server to localhost:5 in the VNC Viewer dialog box. Click OK. In the dialog box that isdisplayed, enter a password and click OK to access the Solaris OS of server 2.

NOTICE:

After the GUI process is completed, run the following command to shut down the VNC service in order to ensure security:# sh stop_vnc_oss.sh

If the command output contains successfully, the VNC service corresponding to the ossuser user is stopped.If the VNC needs to be used again, refer to this document to configure the VNC.If you need to use the VNC again after logging in to the server through the VNC and logging out of the ossuser user in the GUI,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 tolocate the fault:

a. On a PC or laptop, check whether the VNC port is used on Windows.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 |findstr5802 command to check whether the VNC port is occupied. If an ossuser user cannot use the VNC to log in to the server, run thenetstat -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 ossuser user, check whether thecommand 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 thePC 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 todefault configurations, choose Tools > Internet Options > Advanced > Restore Defaults. If the Internet Explorer cannot bereconfigured, try another browser, PC, or laptop.

Table 1 Usage of commonly seen shortcut options in the VNC windowScenario Availability Shortcut Option/Operation Description

Shortcut optionson the VNC CLI

Unavailable The Tab key cannot be used forthe path association function. NOTE:

If the Tab key is incorrectly used, no information can be entered in the CLI. You mustclick in the CLI before entering information.

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 shutdown

Ctrl + l Clearing the screen

Shift + Home Copying characters in the selected area

Shift + Insert Pasting the content in the VNC window

Shortcut optionsfor operations noton the VNC CLI,such asoperations on thefile, window, andmenu

Unavailable Contents outside the VNCwindow cannot be copied orpasted into the VNC window.

You can only enter information in the VNC window or upload it to the VNCwindow.

The Ctrl + Alt + U combinationcannot be used to unlock aclient.

You can only click the button on the left-right corner to unlock a client.

Available Alt + F1 Opening the main menu

Alt + F9 Minimizing the current window

Alt + F10 Maximizing the current window

Ctrl + c Copying the content

Ctrl + v Pasting the content in the VNC window


1.6.1.3 FTP and Telnet Service ConfigurationThis topic covers the FAQs about the FTP and Telnet service configuration.

How to Start/Stop the SSH Service

How to Start/Stop the FTP, SFTP, and Telnet Services

How to Enable and Disable the FTP/Telnet Authority of user root on Solaris OS


1.6.1.3.1 How to Start/Stop the SSH ServiceQuestion

How do I start/stop the SSH service?

Answer

Use the following methods to start/stop the SSH service.

Start the SSH service as follows:

1. Log in to Solaris OS as user root.

2. Run the following command to start the SSH service:

a. # vi /etc/ssh/sshd_config

b. Modify the "PermitRootLogin no" to "PermitRootLogin yes", and run the :wq! command to save the settings and exit.

c. # svcadm restart ssh

d. # svcadm enable ssh

Stop the SSH service as follows:


2. Run the following command to stop the SSH service:# svcadm disable ssh

Parent topic: FTP and Telnet Service Configuration

1.6.1.3.2 How to Start/Stop the FTP, SFTP, and Telnet ServicesQuestion



How do I start/stop the FTP, SFTP, and Telnet services?

NOTE:Using SFTP is recommended.

Answer

Use the following methods to start/stop the FTP, SFTP, and Telnet services. You are recommended to restore the original settings afterwards.

Start the FTP, SFTP, and Telnet services as follows:

when NMS is not installed, starting the FTP service


2. Run the following command to start the FTP service:# svcadm enable ftp

when NMS is installed, starting the FTP service

1. Use the PuTTY to log in to the iMAP server as user ossuser in SSH mode.

2. Run the following command to switch to user root.

$ su - rootPassword: Password of root

3. Run . /opt/oss/server/svc_profile.sh to set environment variables.

4. Run the following command to disable plaintext file transfer over FTP:

# /opt/oss/server/3rdTools/ftp/files/setSSLForFtpSvr.sh enablePlainFtp

5. Run the following command to check whether the enabling is successful:

# grep force_local /etc/vsftpd.conf

Plaintext file transfer over FTP is enabled if the following information is displayed:force_local_logins_ssl=NOforce_local_data_ssl=NO

Starting the SFTP service (The default installation starts and OpenSSH (recommended) is enabled.)

Use the OpenSSH.


2. Run the following commands to enable OpenSSH:# cd /opt/oss/server/common/dc/3rdTool/openssh

# ./chroot_ssh.sh enable

# ./ssh_adm.sh start

3. Run the following command to check whether OpenSSH has been started:# ./check_ssh.sh

A message similar to the following will be displayed:System SSH : [ not running ]New SSH : [ running ][ chroot ]

Use the SFTP service carried by the system.


2. Run the following command to start the SFTP service:# vi /etc/ssh/sshd_config

Modify the "PAMAuthenticationViaKBDInt yes" to "PAMAuthenticationViaKBDInt no", and run the :wq! command tosave the settings and exit.# svcadm restart network/ssh

# svcadm enable network/ssh

Starting the Telnet service


2. Run the following command to start the Telnet service:# svcadm enable telnet

Stop the FTP, SFTP, and Telnet services as follows:

when NMS is not installed, stopping the FTP service


2. Run the following command to stop the FTP service:



# svcadm disable ftp

when NMS is installed, stopping the FTP service

1. Use the PuTTY to log in to the iMAP server as user ossuser in SSH mode.

2. Run the following command to switch to user root.

$ su - rootPassword: Password of root

3. Run . /opt/oss/server/svc_profile.sh to set environment variables.

4. Run the following command to disable plaintext file transfer over FTP:

# /opt/oss/server/3rdTools/ftp/files/setSSLForFtpSvr.sh disablePlainFtp

5. Run the following command to check whether the disabling is successful:

# grep force_local /etc/vsftpd.conf

Plaintext file transfer over FTP is disabled if the following information is displayed:force_local_logins_ssl=YESforce_local_data_ssl=YES

Stopping the SFTP service

Shut down the OpenSSH.


2. Run the following commands to shut down the OpenSSH:# cd /opt/oss/server/common/dc/3rdTool/openssh

# ./chroot_ssh.sh disable

# ./ssh_adm.sh stop

3. Run the following command to check whether OpenSSH has been stopped:# ./check_ssh.sh

A message similar to the following will be displayed:System SSH : [ not running ]New SSH : [ not running ][ not chroot ]

Shut down the SFTP service carried by the system.


2. Run the following command to stop the SFTP service:# svcadm disable network/ssh

Stopping the Telnet service


2. Run the following command to stop the Telnet service:# svcadm disable telnet


1.6.1.3.3 How to Enable and Disable the FTP/Telnet Authority of user root onSolaris OSQuestion

How do I enable and disable the FTP/Telnet authority for user root on Solaris OS?

Answer

1. Enable or disable the FTP authority for user root as follows:

Enabling the FTP authority for user root

a. Log in to Solaris OS as user root.

b. Run the following commands to enable the FTP authority for user root:

# svcadm enable ftp# sed "/^root/s//#root/g" /etc/ftpd/ftpusers > /tmp/ftpusers# cp /tmp/ftpusers /etc/ftpd/ftpusers

Disabling the FTP authority for user root




b. Run the following commands to enable the FTP authority for user root:# echo "root" >> /etc/ftpd/ftpusers

2. Enable or disable the Telnet authority for user root as follows:

Enabling the Telnet authority for user root


b. Run the following commands to enable the Telnet authority of user root:

# svcadm enable telnet# sed "/^CONSOLE/s//#CONSOLE/g" /etc/default/login > /tmp/login# cp /tmp/login /etc/default/login

Disabling the Telnet authority for user root


b. Run the following commands to disable the Telnet authority of the root user:# sed "/^#CONSOLE/s//CONSOLE/g" /etc/default/login > /tmp/login# cp /tmp/login /etc/default/login


1.6.1.4 Usage and Maintenance of WorkstationThis topic covers the FAQs about the usage and maintenance of the workstation.

How to View the Versions and its patches of the Solaris OS

How to Change the System Time and Time Zone of Solaris OS

How to View Hardware Configurations for the Sun Workstation

How to Check Whether the Hard Disk of the Sun Workstation Is Damaged

How to Check the Partition of Solaris OS

How to Check the Remaining Space of a Disk

How to Check the IP Address and Routing Information for a Workstation

How to View the Controller IP Addresses for the Sun Workstation

How to Decompress Files

How to Remotely Log In to the System as User root

How to Access the OS from the Controller

How to Switch Between the Console, OK Prompt, and # Prompt

How to Use the vi Editor

How to Use the Text Editor

How to Forcibly End a Process

How to Upgrade the System Controller Firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server

How Do I Upgrade the System Controller Firmware of the T5220 Server in CLI Mode

How to Solve the Problem Where the OS Fails to Start After the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server Is Abnormally Powered Off

How to Solve the Problem Where the Monitor or KVM Cannot Access the GUI After the OS Is Installed on the Netra T4-1/Oracle T4-1/OracleT4-2/T5220 Server

How Do I Enable the SSH Service for the XSCF on the M4000/M5000 Server

How to Obtain Packet Headers on Solaris

Mappings Between Physical and Logical Network Interfaces on Server Running SolarisThis topic describes the mappings between physical and logical network interfaces on server running Solaris.

Description About Interfaces Connecting to Disk ArraysThis topic describes the interfaces connecting to disk arrays.




1.6.1.4.1 How to View the Versions and its patches of the Solaris OSQuestion

How do I view the versions and its patches of the Solaris OS?

Answer

1. Open a terminal window on Solaris OS.



If the Solaris version is Solaris 10 8/11 if the following message is displayed. The OS and patches are successfully installed. Otherwise, use a correctinstallation DVD-ROM to reinstall the OS or the OS patch.


A message similar to the following will be displayed:5.10 Generic_150400-11If the core patch version is 5.10 Generic_150400-11, the OS and the sparc_patch_20.0.0 patch have been installed. If another version is displayed,install the OS patch.

Parent topic: Usage and Maintenance of Workstation

1.6.1.4.2 How to Change the System Time and Time Zone of Solaris OSQuestion

How do I to change the system time and time zone of Solaris OS?

Answer

To change the time zone of Solaris OS, perform the following operations:

1. Run the following command, according to the interface prompts to select your local time zone, TZ values recorded.# tzselect

2. Run the following command to modify the /etc/TIMEZONE file:# vi /etc/TIMEZONE

3. Change the value of TZ to the local time zone. For example, set TZ to PRC.

4. Press Esc. Press Shift+; and enter wq!. Then, press Enter to forcibly save and close the file.


6. Run the following command to verify that the time zone is correct:# echo $TZ

If the time zone is incorrect, verify that the /etc/TIMEZONE file and GMT are set properly.

To change the system time of Solaris OS, perform the following operations:Run the date command to set the system date and time.For example, to set the system date and time to 2005-11-17 16:30:43, run the following command:# date 111716302005.43

The following message will be displayed:Mon Nov 17 16:30:43 CST 2005


1.6.1.4.3 How to View Hardware Configurations for the Sun WorkstationQuestion

How do I view hardware configurations for the Sun workstation?



Answer

Log in to the Sun workstation as the root user. Then, run the following commands:# cd /usr/platform/`uname -i`/sbin

# ./prtdiag

A message similar to the following is displayed:System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M4000 ServerSystem clock frequency: 1012 MHzMemory size: 32768 Megabytes

==================================== CPUs ====================================

CPU CPU Run L2$ CPU CPULSB Chip ID MHz MB Impl. Mask--- ---- ---------------------------------------- ---- --- ----- ---- 00 0 0, 1, 2, 3 2150 5.0 6 147 00 1 8, 9, 10, 11 2150 5.0 6 147 00 2 16, 17, 18, 19 2150 5.0 6 147 00 3 24, 25, 26, 27 2150 5.0 6 147

============================ Memory Configuration ============================

Memory Available Memory DIMM # of Mirror InterleaveLSB Group Size Status Size DIMMs Mode Factor--- ------ ------------------ ------- ------ ----- ------- ---------- 00 A 16384MB okay 2048MB 8 no 4-way 00 B 16384MB okay 2048MB 8 no 4-way

========================= IO Cards =========================

LSB Name Model--- -------------- ------------ 00 scsi LSI,1064 00 network N/A 00 network N/A 00 network SUNW,pcie-qg 00 network SUNW,pcie-qg 00 network SUNW,pcie-qg 00 network SUNW,pcie-qg 00 SUNW,qlc QLE2460 00 SUNW,qlc QLE2460

==================== Hardware Revisions ====================

System PROM revisions:----------------------

OBP 4.24.10 2008/08/12 19:52

=================== Environmental Status ===================

Mode switch is in UNLOCK mode

Details about the message are as follows:

The following information indicates a workstation model. In this example, the workstation model is Sun SPARC Enterprise M4000 Server.System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M4000 Server

The following information indicates the system clock frequency. In this example, the workstation clock frequency is 1012 MHZ.System clock frequency: 1012 MHz

The following information indicates the memory configuration for the workstation. In this example, the memory configuration for the workstation is32 GB.Memory size: 32768 Megabytes

The following information indicates the CPU configuration for the workstation. In this example, four CPUs are configured for the workstation, eachCPU has four threads, and the workstation has 16 threads in total.==================================== CPUs ====================================

CPU CPU Run L2$ CPU CPULSB Chip ID MHz MB Impl. Mask--- ---- ---------------------------------------- ---- --- ----- ---- 00 0 0, 1, 2, 3 2150 5.0 6 147 00 1 8, 9, 10, 11 2150 5.0 6 147 00 2 16, 17, 18, 19 2150 5.0 6 147 00 3 24, 25, 26, 27 2150 5.0 6 147

NOTE:Hardware configurations for a workstation vary according to the workstation model.


1.6.1.4.4 How to Check Whether the Hard Disk of the Sun Workstation Is



DamagedQuestion

How do I check whether the hard disk of the Sun workstation is damaged?

Answer

During the operation of the Sun workstation, inappropriate powering-off usually causes damage to the hard disk and even renders the Sybase databaseunavailable. Run the iostat -E command to check whether the hard disk of the OS is damaged.Log in to the Sun workstation as user root and run the following command:# iostat -En

A message similar to the following will be displayed:c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MAY2073RCSUN72G Revision: 0501 Serial No: 0742S0EPT7 Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive FailureAnalysis: 0 c0t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MAY2073RCSUN72G Revision: 0501 Serial No: 0742S0EPL9 Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MBB2073RCSUN72G Revision: 0505 Serial No: 0805A011C0 Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0Illegal Request: 0 Predictive Failure Analysis: 0 c1t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 1 Vendor: TSSTcorp Product: CD/DVDW TS-T632A Revision: SR03 Serial No: Size: 0.00GB <0 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0Illegal Request: 1 Predictive Failure Analysis: 0 c0t3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MBB2073RCSUN72G Revision: 0505 Serial No: 0805A011DH Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0

NOTE:The hard disk is damaged if the information to the rights of Hard Errors is not 0. Send the message series files in the /var/adm directory to Huawei engineers so that they can apply for aspare part to replace the hard disk on site.


1.6.1.4.5 How to Check the Partition of Solaris OSQuestion

How do I check the partition of Solaris OS?

Answer


2. Run the following command to check all disks of the server:# format

The following message will be displayed:Searching for disks...done

AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@0,0 1. c0t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@1,0 2. c0t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@2,0 3. c0t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@3,0 4. c0t4d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@4,0 5. c0t5d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@5,0Specify disk (enter its number):

3. Enter 0 and press Enter to view the information about the c1t0d0 disk. The following message will be displayed:selecting c0t0d0 [disk formatted]



/dev/dsk/c0t0d0s1 is in use by dump. Please see dumpadm(1M). FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute<cmd>, then return quit format>

4. Enter p and press Enter to select the partition list. The following message will be displayed:PARTITION MENU: 0 - change `0' partition 1 - change `1'partition 2 - change `2' partition 3 - change `3' partition 4 - change `4' partition 5 - change `5' partition 6 - change `6' partition 7 - change `7' partition select - select a predefined table modify -modify a predefined partition table name - name the current tableprint - display the current table label - write partition map and label to the disk !<cmd> - execute<cmd>, then return quitpartition>

5. Enter p and press Enter to view the partition information of disk c1t0d0, including the raw partition information. The following message will bedisplayed:Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 3091 30.01GB (3092/0/0) 62928384 1 swap wu 3092 - 6389 32.01GB (3298/0/0) 67120896 2 backup wm 0 - 14086 136.71GB (14087/0/0) 286698624 3 - wu 0- 14086 136.71GB (14087/0/0) 286698624 4 - wu 14083 - 14086 39.75MB (4/0/0) 81408 5 unassigned wm 6390 - 10511 40.00GB (4122/0/0) 83890944 6 var wm 10512 - 13603 30.01GB (3092/0/0) 629283847 unassigned wm 0 0 (0/0/0) 0 partition>

6. Enter q to exit the c1t0d0 disk directory. The following message will be displayed:FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label -write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute<cmd>, then return quit format>

7. Enter q and exit the format command.

8. Repeat Step 2 to Step 7, and select other disks to check the partitions.


1.6.1.4.6 How to Check the Remaining Space of a DiskQuestion

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.


1.6.1.4.7 How to Check the IP Address and Routing Information for aWorkstationQuestion

How to check the IP address and routing information for a workstation?

Answer


2. Run the following command to view the IP address of the host:# ifconfig -a

Information similar to the following is displayed:lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232inet 127.0.0.1 netmask ff000000hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu 1500 inet 10.9.169.143 netmask ffff0000 broadcast 10.9.255.255hme0:1:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.6.253.136 netmask ffff0000 broadcast 10.6.255.255

NOTE:In the previous output, the IP address of the displayed host is 10.9.169.143, and the logical IP address is 10.6.253.136. In the Solaris or system, a network adapter can bindseveral logical IP addresses, which realizes communications between different network segments.

3. Run the following command to view the information about the routing tables:# netstat -rn

Information similar to the following is displayed:Routing Table:Destination Gateway Flags Ref Use Interface10.105.28.0 10.105.28.202 U 4 2 hme010.0.0.0 10.105.31.254 UG 0 0 127.0.0.1 127.0.0.1 UH 0 896 lo0

A router can be in any of the following five different flags: U, G, H, D, and M, as described in Table 1.

Table 1 Description of routing flagsFlag Description

U U indicates that a route is currently available.

G G indicates that a route is destined for a gateway such as a router.If this flag is not set, you can infer that the destination is connected directly. Flag G distinguishes between direct and indirect routes.Flag G is unnecessary for direct routes. The difference is that the packet sent through a direct route carries both the destination IPaddress and the link-layer address. In the packet sent through an indirect route, however, the IP address points to the destination andthe link layer address points to the gateway (for example, the next router).

H H indicates a route destined for a host. That is, the destination address is a complete host address.

NOTE:If this flag is not set, you can infer that the route leads to a network and that the destination address is a network address: either a networknumber or a network. The part in the address for the host is 0.When you search the routing table for an IP address, the host address must exactly match the destination address.The network address, however, is required to match only the network number and subnet number of the destination address.

D D indicates that a route is created by a redirected packet.

M M indicates that a route is modified by a redirected packet.

The Ref (Reference count) column lists the number of routing progresses. The protocol for connection, such as TCP, requires a fixed route when aconnection is established. If the telnet connection is established between the host svr4 and the host slip, the Ref is 1. If another telnet connection isestablished, its value is changed to 2.The next column (Use) displays the number of packets sent through a specified route. After you run the ping command as the unique user of thisroute, the program sends five groups and the number of packets is displayed as 5. The last column (Interface) indicates the name of the localinterface.The name of the loop-back interface is permanent set to lo0. Flag G is not set because the route is not destined for a gateway. Flag H indicates thatthe destination address, 127.0.0.1, is a host address and not a network address. Because flag G is not set, the route here is a direct route and thegateway column shows the outgoing IP address.Each host has one or multiple default routes. That is, if a particular route is not found in the table, the packet is sent to the router. In addition, thecurrent host can access other systems through the Sun router (and the slip link) on the internet, based on the settings of the routing table. The flagUG refers to the gateway.




1.6.1.4.8 How to View the Controller IP Addresses for the Sun WorkstationQuestion

How to view the controller IP addresses for the Sun workstation?

Answer

Check the controller IP address for the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server.


a. Use a serial port (DB9-RJ45) to connect the serial port of the local console and the serial port (SERIAL MGT) of the server.Use an RJ-45 connector at one end of the serial port cable to connect to the serial port (SERIAL MGT) of the server and use aDB-9 connector at the other end of the cable to connect to the serial port (COM1 or COM2) of the computer.


Figure 1 Connections between the Netra T4-1 server and the controller



Figure 4 Connections between the T5220 server and the controller




a. Start the computer and enter Windows OS.



Serial line to connect to COM1

Speed(baud) 9600

Data bits 8

Stop bits 1

Parity None

Flow Control None

d. Choose Session from the navigation tree. In the right-hand pane, set Connection type to Serial and use the default values forother parameters.

e. Click Open.

3. Enter the user name and password. The default user name is root and the default password is changeme.

NOTE:The OS will be started after this step is complete if the OS is installed on the workstation. Run the #. command to display the prompt of the controller.

4. Perform the following operations to configure hardware at the -> prompt:

a. Enter cd /SP/network.The following message will be displayed:/SP/network

b. Enter showThe following message will be displayed:/SP/network Targets:

Properti commitpending = (Cannot show property) dhcp_server_ip = none ipaddress = 10.9.1.20 ipdiscovery = static ipgateway = 10.9.1.1 ipnetmask = 255.255.255.0 macaddress = 00:21:28:3F:9F:E9 pendingipaddress = 10.9.1.20 pendingipdiscovery = static pendingipgateway = 10.9.1.1 pendingipnetmask = 255.255.255.0 state = enabled

Commands: cd set show

NOTE:In the preceding message, the controller IP address is 10.9.1.20, corresponding to pendingipaddress; the controller gateway address is 10.9.1.1,corresponding to pendingipgateway; the controller subnet mask is 255.255.255.0, corresponding to pendingipnetmask.

c. Enter exit to close the serial port-based login window.

Check the controller IP address for the M4000/M5000 server.




a. Use a serial port (DB9-RJ45) to connect the serial port of the local console and the serial port (SERIAL MGT) of the server.Use an RJ45 connector at one end of the serial port cable to connect to the serial port (SERIAL MGT) of the server and use aDB-9 connector at the other end of the cable to connect to the serial port (COM1 or COM2) of the computer.


Figure 5 Controller connection of the M4000 server






Speed(baud) 9600

Data bits 8

Stop bits 1

Parity None

Flow Control None

d. Choose Session from the navigation tree. In the right-hand pane, set Connection type to Serial and use the default values forother parameters.

e. Click Open.

3. Enter the user name. Enter the default user name (default) if the system is being logged in to for the first time.login: default

A message similar to the following will be displayed:Change the panel mode switch to Service and press Return.

4. Within 5 to 10 seconds, insert the key into the key slot in the front panel of the M4000/M5000. Turn the switch to Service labeled with and press Enter.A message similar to the following will be displayed:Leave it in that position for at least 5 seconds. Change the panel mode switch to Locked, and press return...

5. Within 5 to 10 seconds, turn the switch to Locked labeled with and press Enter.A message similar to the following will be displayed:XSCF>

NOTE:If the event that XSCF> is not displayed (which means that login has failed), attempt to log in again.

6. Run the following command to check the controller IP address:XSCF>shownetwork -a

A message similar to the following will be displayed:xscf#0-lan#0 Link encap:Ethernet HWaddr 00:21:28:A7:70:5A inet addr:10.9.1.21 Bcast:10.9.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28675336 errors:0 dropped:0 overruns:0 frame:0 TX packets:175477 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1936471239 (1.8 GiB) TX bytes:12527755 (11.9 MiB)



Base address:0xe000

xscf#0-lan#1 Link encap:Ethernet HWaddr 00:21:28:A7:70:5B BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

NOTE:In the preceding information, the controller IP address is 10.9.1.21, which is shown to the right of inet addr. The controller broadcast address is 10.9.1.255, which isshown to the right of Bcast. The controller subnet mask is 255.255.255.0, which is shown to the right of Mask.

7. Enter exit to close the serial port-based login window.


1.6.1.4.9 How to Decompress FilesQuestion

Compressed files are usually in *.tar, *.tar.gz, or *.zip format. How do I decompress these files?

Answer

To decompress a *.tar file, perform the following operation:The following uses the abc.tar file as an example. Run the following command:# tar xvf abc.tar

To decompress a *.tar.gz file, perform the following operation:

The following uses the abc.tar.gz file as an example. Run the following commands:# gunzip abc.tar.gz

# tar xvf abc.tar

The following uses the solaris10_HuaweiPatch9.0.tar.gz file as an example. Run the following command:# gzcat solaris10_HuaweiPatch9.0.tar.gz | tar xBpf -

To decompress a *.zip file, perform the following operation:The following uses the abc.zip file as an example. Run the following command:# unzip abc.zip


1.6.1.4.10 How to Remotely Log In to the System as User rootQuestion

Remote login fails after the system is restarted. How do I remotely log in to the system as user root?

Answer

1. Log in to the server from the controller. Ensure that the server is running.

2. Check whether user root has rights to log in to the server. Ensure that user root has rights to log in to the server.

3. Verify the routing information about the server. Ensure that the route is reachable.


1.6.1.4.11 How to Access the OS from the ControllerQuestion

How to use a controller to access the OS when login to the OS from the system IP address fails or security hardening does not take effect and remote login tothe OS as the root user fails?

Answer

1. Log in to the controller.



For M4000/M5000 servers, log in to the controller by means of Telnet or SSH (more secure, recommended).

NOTE:Using SSH (more secure, recommended) to log in to the server is recommended.

For Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 servers, log in to the controller in SSH mode.

2. Access the OS.

For M4000/M5000 servers, run the console -d 0 command to access the OS.

For Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 servers, run the start /SP/console command to access the OS.


1.6.1.4.12 How to Switch Between the Console, OK Prompt, and # PromptQuestion

How do I switch between the console, OK prompt, and # prompt?

NOTE:The switching method varies based on the type of the Sun server used.

Answer

Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Servers

Switch from the console to the OK prompt.

NOTE:When you switch from the console to the OK prompt, the OS will be shut down. If the U2000 is already running during switching, ensure that the U2000 and databasehave been shut down.

1. Log in to the IP address of the system controller in Secure Shell (SSH) mode. Perform the following operations to display the OKprompt:

NOTE:The Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server does not support the login to the system controller in Telnet mode. Log in to the system controllerby performing the following operation:

Install the SSH client tool, such as the PuTTY, in the console on Windows. Then, you can log in to the system controller through the tool.Run the ssh IP address of the system controller command on the terminal console of another Sun server to log in to the system controller. If amessage similar to the following is displayed, enter yes to continue:The authenticity of host '10.71.35.12 (10.71.35.12)' can't be established.RSA key fingerprint is 0b:23:07:0c:27:72:44:3f:d1:aa:12:99:ed:dd:c0:5a.Are you sure you want to continue connecting (yes/no)?

2. In the command line interface (CLI) that is displayed, enter the user name and password of the system controller. By default, theuser name is root and the default password is changeme.

3. Run the following command:-> set /HOST/bootmode state=reset_nvram script="setenv auto-boot? false"



4. Run the following command:-> show /HOST status

If status = Solaris running is displayed in the command output, run the start /SP/console command to enter the OS, and run theshutdown -y -g0 -i0 command as the root user to display the OK prompt. Skip the following steps.If status = Solaris running is not displayed in the command output, perform the following operations.

5. Run the following command:-> start /SYS


6. Enter y to start the server.If the message start: Target already started is displayed, the system is running. Perform the following operations:

Run the following command:-> stop /SYSThe following message will be displayed:



Are you sure you want to stop /SYS (y/n)?





7. Run the following command to display the OK prompt:-> start /SP/console


8. Enter y and press Enter.The following message will be displayed:Serial console started. To stop, type #....Setting NVRAM parameters to default values.



Switch from the OK prompt to the # prompt.Run the following command:

ok setenv auto-boot? true

NOTE:There must be a space between ? and true.

If the message auto-boot? = true is displayed, the setting succeeds.

Run the following command to verify that the parameter settings have taken effect:

ok printenv

NOTE:If the message auto-boot? true is displayed, the parameters have taken effect.

Variable Name Value Default Value... auto-boot? true true...

Run the following command to enable the system to perform another self-check:

ok reset-all

The system will display the OK prompt. Enter boot. If # is displayed, the system has successfully switched to the # prompt.

ok boot

Switch from the # prompt to the console.Run the following command:

# #.

NOTE:Enter # and ..

Switch from the # prompt to the OK prompt.Run the following command:

# init 0

Switch from the console prompt to the #.

The system will start running. Run the following command to change the status from the console prompt to the # prompt.-> start /SP/console

M4000/M5000 Servers




NOTE:When you switch from the console to the OK prompt, the OS will be shut down. If the U2000 is already running during switching, ensure that the U2000 and databasehave been shut down.

1. Run the telnet IP address of the controller command on the console to log in to the controller IP address by means of Telnet.The following message will be displayed:Login:

2. Enter the user name, that is, eis-installer.The following message will be displayed:Password:

3. Enter the password of the eis-installer user.The following message will be displayed:XSCF>

4. Run the following command:XSCF> showdomainmode -d 0

The following message will be displayed:Host-ID :8501c2deDiagnostic Level :minSecure Mode :off (host watchdog: unavailable Break-signal:receive) Autoboot :on CPU Mode :auto

NOTE:If Secure Mode is on, perform the following:

a. Run the following command:XSCF> setdomainmode -d 0 -m secure=offThe following message will be displayed:

Diagnostic Level :min -> -Secure Mode :on -> off Autoboot :on -> -CPU Mode :auto The specified modes will be changed.Continue? [y|n]

b. Enter y.


configured.Diagnostic Level :minSecure Mode :off (host watchdog: unavailable Break-signal:receive)Autoboot :on (autoboot:on)CPU Mode :auto

5. Run the following command:XSCF> showdomainstatus -a

The following message will be displayed:DID Domain Status00 Running01 -

If runningis displayed in the command output, run the console -d 0 -f command to enter the OS, and run the shutdown -y -g0 -i0 command as the root user to display the OK prompt. Skip the following steps.

If running is not displayed in the command output, run the reset -d 0 xir.The following message will be displayed:DomainID to reset:00Continue? [y|n]

6. Enter y.

7. Run the following command:XSCF> console -d 0 -f

The following message will be displayed:Connect to DomainID 0? [y|n]

8. Enter y and press Enter.OK







ok printenv


ok reset-all

The system will display the OK prompt. Enter boot to display the # prompt.

ok boot


# #.

NOTE:Enter # and ..


# init 0

Switch from the console prompt to the #.Run the following command:

The system will start running. Run the following command to change the status from the console prompt to the # prompt.-> console -d 0 -f

V240 and V440 Server


1. Run the telnet IP address of the controller command on the console to log in to the controller IP address by means of Telnet.The following message will be displayed:Login:

2. Enter the user name and password.

3. Run the following command to display the OK prompt.sc> console -f

NOTE:In certain conditions, the following message will be displayed:

Warning: User < > currently has write permission to this console andforcibly removing them will terminate any current write actionsand all work will be lost.Would you like to continue? [y/n]

Enter y.

If the intended server is used for the first time, the system will display the OK prompt.

If the server is installed with the OS, the system will display the # prompt. Perform the following operations to display the OK prompt:

Enter #. to display the ALOM prompt. (If the RSC control board is used, enter ~..)

Run the following command at the ALOM prompt:

sc> break


Are you sure you want to send a break to the system [y/n]?

Enter y.

sc> console -f





ok printenv


ok reset-all

The system will display the OK prompt. Enter boot to display the # prompt.

ok boot




# #.

NOTE:Enter # and ..


# init 0

Switch from the console prompt to the #.Run the following command:

The system will start running. Run the following command to change the status from the console prompt to the # prompt.-> console -f


1.6.1.4.13 How to Use the vi EditorQuestion

How do I use the vi editor?

Answer

Run the following command to open the vi editor:vi file name

If a file with the same filename exists, run the vi command to open and edit the file.

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:

The command for opening the vi editor is as follows:vi file name

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.

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.

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.

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.

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 anycommand listed in Table 1.

Table 1 Commands for quitting the vi editorCommand 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.


1.6.1.4.14 How to Use the Text EditorQuestion

How do I use the text editor?

NOTE:Use the text editor only through the GUI.

The text editor is recommended because it is easier to use than the vi editor.

Answer

Run the following command to open the text editor:dtpad file name

If a file with the same filename exists, run the dtpad command to open and edit the file.

If a file with the same filename does not exist, run the dtpad command to create and edit a file.


1.6.1.4.15 How to Forcibly End a ProcessQuestion

How do I forcibly end a process?

Answer

Run the kill -9 process ID command to forcibly end a process.


1.6.1.4.16 How to Upgrade the System Controller Firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 ServerQuestion

How do I upgrade the version of the system controller firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server?

Answer

1. Log in to the website http://support.huawei.com. Choose Software Center > Controlled Tool (Mini-tool Software) > Network OSS&Service >Universal OS & Patches > Solaris and download patch packages based on the server type. Only Huawei engineers have the permissions todownload software packages. If the installation using software packages is required, contact Huawei engineers to obtain software packages.

T5220 server:T5220_SC_patch-7_4_6_c_solaris_SPARC.zip



Netra T4-1 server:Netra_T4-1_SC_patch-8_3_0_solaris_SPARC.zip

Oracle T4-1 server:T4-1_SC_patch-8_3_0_solaris_SPARC.zip

Oracle T4-2 server:T4-2_SC_patch-8_3_0_solaris_SPARC.zip

2. Log in to the system controller.

3. Run the following command to start the HTTP service of the system controller firmware:-> cd /SP/services/https-> set servicestate=enabled

If information similar to the following is displayed, the HTTP service is started successfully.Set 'servicestate' to 'enabled'

4. On the computer where the Windows OS has been installed, open the Internet Explorer.

5. On the address bar, enter the IP address of the workstation controller.

6. In the login dialog box that is displayed, enter the user name and password of the controller and click Log In.

NOTE:A message indicating an issue about the security certificate may be displayed. Ignore the message.The default user name of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 controller is root.The default password of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 controller is changeme.

7. After successful login to the server, power off the server. If the server has been powered off, skip the following operations:T5220 server:

a. Choose Remote Control > Remote Power Control.

b. On the Server Power Control page, select Immediate Power Off and click Save.

Netra T4-1/Oracle T4-1/Oracle T4-2 Server:

a. Choose Host Management > Power Control.

b. On the Server Power Control page, select Immediate Power Off and click Save.

8. Upgrade the system controller firmware.

a. Copy the obtained patch package to a PC directory and decompress it.

b. After the copying is complete, view the MD5 code in the uploaded software package and check whether the uploaded software packagesare appropriate. For details, see How to Check Downloaded Software Packages by Using HashMyFiles Software.

c. Choose Maintenance > Firmware Upgrade. Then click Enter Upgrade Mode.

d. A confirmation dialog box will be displayed. Click OK in the dialog box.

e. Click Browse and select the patch package based on the server type.

T5220 server: Navigate to the 147307-09 directory in the decompression directory of the patch package. Select theSun_System_Firmware-7_4_6_c-SPARC_Enterprise_T5120+T5220.pkg patch package.

Netra T4-1 server: Navigate to the 150417-02 directory in the decompression directory of the patch package. Select theSun_System_Firmware-8_3_0_c-Netra_SPARC_T4-1.pkg patch package.

Oracle T4-1 server: Navigate to the 150413-02 directory in the decompression directory of the patch package. Select theSun_System_Firmware-8_3_0_c-SPARC_T4-1.pkg patch package.

Oracle T4-2 server: Navigate to the 150414-02 directory in the decompression directory of the patch package. Select the



Sun_System_Firmware-8_3_0_c-SPARC_T4-2.pkg patch package.

f. Click Upload to upload the patch package of the system controller firmware. Then click Start Upgrade to start upgrading the systemcontroller firmware.

NOTE:During the upgrade process, do not turn off the controller page on the browser, and do not switch to another tab page.The check-box Preserve Configuration is recommended to be checked.

g. A confirmation dialog will be displayed. Click OK in the dialog box.

h. If information similar to the following is displayed, the upgrade is complete.

9. Log in to the controller of the server as the root user. Run the following command to view the version of the system controller firmware:-> cd /HOST-> ls

View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware 7.4.6.c 2012/03/14 10:49.If sysfw_version = Sun System Firmware 7.4.6.c is displayed, the version of sysfw_version is later than 7.2 and the system controller firmware isupgraded successfully.

T5220 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware 7.4.6.c 2012/03/1410:49.If sysfw_version = Sun System Firmware 7.4.6.c is displayed, the version of sysfw_version is later than 7.4.6.c and the system controllerfirmware is upgraded successfully.

Netra T4-1/Oracle T4-1/Oracle T4-2 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware 8.3.0.b 2012/08/0311:58.If sysfw_version = Sun System Firmware 8.3.0 is displayed, the version of sysfw_version is later than 8.3.0 and the system controllerfirmware is upgraded successfully.

NOTE:If an OS has been installed, access the OS and restart it after the system controller firmware is upgraded.

T5220 server:

Perform Step4 to Step6 to login to the server.Choose Remote Control > Remote Power Control.On the Server Power Control page, select Power On and click Save.

Netra T4-1/Oracle T4-1/Oracle T4-2 Server:

Perform Step4 to Step6 to login to the server.Choose Host Management > Power Control.On the Server Power Control page, select Power On and click Save.


1.6.1.4.17 How Do I Upgrade the System Controller Firmware of the T5220Server in CLI ModeQuestion



How do I upgrade the system controller firmware of the T5220 server in CLI mode?

Answer

1. Log in to http://support.huawei.com and choose Software Center > Controlled Tool (Mini-tool Software) > Network OSS&Service > UniversalOS & Patches > Solaris. Then download the desired software package according to the server type. Only Huawei engineers have the right todownload software packages. If customers require software packages, contact Huawei engineers.T5220 server: T5220_SC_patch-7_4_6_c_solaris_SPARC.zip

2. Upload the software package to the /tmp directory and decompress it.

a. Use the controller to access the operating system. For details, see How to Access the OS from the Controller.

b. Run the following command to create the /tmp directory:# mkdir /tmp

c. Use SFTP/FTP to upload the software package to the /tmp directory as the root user. SFTP, which is securer than FTP, is recommendedfor you to upload the software package. For details about how to use SFTP, see How to Use the FileZilla to Transfer Files by SFTP. If youwant to use FTP, see How to Transfer Files by Means of FTP.

d. Run the following commands on the server to switch to the directory where the software package is stored. Then decompress the package.# cd /tmp# unzip T5220_SC_patch-7_4_6_c_solaris_SPARC.zip

3. Run the following commands to download the image file to the control card.

NOTE:Before upgrade the system controller firmware in CLI mode, ensure that the U2000 and the database is not running.

# cd /tmp/# mv 147307-09/ 14730709/# cd /tmp/14730709/# ./sysfwdownload Sun_System_Firmware-7_4_6_c-SPARC_Enterprise_T5120+T5220.pkg

NOTE:If the message Download completed successfully. is displayed, the image file is successfully downloaded.

4. Run the following commands to enter the OK mode:# sync;sync;sync;sync;# init 0

NOTE:If the OK prompt is displayed after 5 to 10 minutes, the system enters the OK mode.

5. After the system enters the OK mode, log in to the server controller as the admin user and shut down the server.login as: adminPassword: admin user password

NOTE:The default password of the admin user is admin123.

sc> poweroff

NOTE:If the message Host has been powered off is displayed, the server is successfully shut down.

6. Verify that the Keyswitch is in the NORMAL state.sc> showkeyswitch

NOTE:If the message Keyswitch is in the NORMAL position. is displayed, the Keyswitch is already in the NORMAL state. If the Keyswitch is not in the NORMAL state, run thefollowing command to switch it to the NORMAL state:sc> setkeyswitch –y normal

7. Run the following command to upgrade the flash:sc> flashupdate -s 127.0.0.1

NOTE:The following information is displayed:

NOTE: A flashupdate takes about 6 minutes to load a new file.

Some commands are disabled until the file load is complete.

The SC will be reset to complete the upgrade.

Are you sure you want to load the specified file (y/n)?

8. Enter y and press Enter to start the firmware upgrade.

NOTE:The following information is displayed:



.........................................................................................................................New firmware images were loaded. The SC will reset now to complete the upgrade.

Connection closed by foreign host.After the upgrade is complete, the system automatically restarts the SC.

9. After the SC is restarted, power on the server and start the operating system.

a. Log in to the controller as the root user.

b. Run the following command to start the operating system:-> start /SYS

The following information is displayed:Are you sure you want to start /SYS (y/n)?


c. Run the following command to access the OS:-> start /SYS

The following information is displayed:Are you sure you want to start /SP/console (y/n)?

Enter y to access the OS.


1.6.1.4.18 How to Solve the Problem Where the OS Fails to Start After theNetra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server Is Abnormally Powered OffQuestion

After the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server is abnormally powered off, the control card displays the message "System faults or hardwareconfiguration prevents power on" during OS startup. How do I address this problem?

Answer

1. On the computer where the Windows OS has been installed, open the Internet Explorer.

2. On the address bar, enter the IP address of the workstation controller.

3. In the login dialog box that is displayed, enter the user name and password of the controller and click Log In.

NOTE:A message indicating an issue about the security certificate may be displayed. Ignore the message.The default user name of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 controller is root.The default password of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 controller is changeme.

4. Click the Components tab.

5. Perform the following operations to start components in the Disabled state:

a. Select Component State: Disabled from Filter to filter out components in the Disabled state.



b. Select all the components in the Disabled state.

c. Select Enable Component from Actions to start the components.

NOTE:If components in the Disabled state are unavailable, all components are normal.If the components still fail to be started after Enable Component is selected, a hardware fault occurs. Contact Oracle engineers to address the issue.

6. Perform the following operations to restore faulty components:

a. Select Fault Status: Faulted from Filter to filter out components in the Faulted state.

b. Select all the components in the Faulted state.

c. Select Clear Faults from Actions.

NOTE:If the fault persists after Clear Faults is selected, a hardware fault occurs. Contact Oracle engineers to address the issue.

7. After the preceding operations are complete, shut down the Internet Explorer.

8. Perform the following operations to restart the workstation:

a. If the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server is used, perform the following operations to display the OK prompt:

i. Log in to the system controller in SSH mode.



ii. In the CLI, enter the user name and password of the system controller. The default user name and password are root andchangeme.

iii. Enter set /HOST/bootmode state=reset_nvram script="setenv auto-boot? false".





iv. Enter start /SYS.The following message will be displayed:Are you sure you want to start /SYS (y/n)?

v. Enter y to start the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220.

The system is running if the following message is displayed:start: Target already startedPerform the following operations:If the message is not displayed, go to the step 8.a.vi.

a. Enter stop /SYS.The following message will be displayed:Are you sure you want to stop /SYS (y/n)?

b. Enter y.The following message will be displayed:Stopping /SYS

c. Enter show /HOST status repeatedly to check the system status.

Proceed with the subsequent operations until the following message is displayed:status = Powered off

d. Enter start /SYS.The following message will be displayed:Are you sure you want to start /SYS (y/n)?

e. Enter y to start the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220.

vi. Enter start /SP/console.The following message will be displayed:Are you sure you want to start /SP/console (y/n)?

vii. Enter y and press Enter.





SPARC Enterprise T5220, No KeyboardCopyright 2008 Sun Microsystems, Inc. All rights reserved.OpenBoot 4.28.0, 8064 MB memory available, Serial #85369820.Ethernet address 0:21:28:16:a3:dc, Host ID: 8516a3dc..............


1.6.1.4.19 How to Solve the Problem Where the Monitor or KVM CannotAccess the GUI After the OS Is Installed on the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 ServerQuestion

The OS was installed by using the quick installation DVD. After the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 is connected to the KVM, the GUI cannot beopened. How do I rectify this fault?

Answer



1. To set the I/O mode, run the following commands:# eeprom output-device=screen

# eeprom input-device=keyboard

2. To set the screen resolution and refresh rate, perform the following operations:

a. To view information about the current video board, run the following command:# fbconfig -list


Device File Name Device Model Config Program ---------------- ------------ -------------- /dev/fbs/ast0 display fbconf_xorg

NOTE:The value of /dev/fbs/ast0 differs according to on-site requirements.

b. Optional: If Config Program is displayed as program not available, run the following commands:# ln -s /dev/fbs/ast0 /dev/fb

# fbconfig -xserver Xorg

c. To view the screen resolution and refresh rate supported for the current video board, run the following command:# fbconfig -dev /dev/fbs/ast0 -res \?


Valid values for -res option are: ... ...VESA_STD_640x480x60[1] Resolution is supported by monitor[2] Preferred resolution for monitorNo EDID data for monitor. Can not determine supported resolutions.

Use of an unsupported resolution can render the video display unusable.

Abbreviations such as "1280x1024x75" may also be used.

d. To view the current configurations for the video board, run the following command:# fbconfig -dev /dev/fbs/ast0 -propt


--- Graphics Configuration for /dev/fbs/ast0 ---xorg.conf: machine -- /etc/X11/xorg.conf Screen section: "ast0" Device section: "ast0" Monitor section: none

Video Mode: Not set

Screen Information: Remote Screen: Not set

e. The screen resolution and refresh rate are not set if Video Mode is set to not set. To set the screen resolution and refresh rate, run thefollowing commands:# fbconfig -dev /dev/fbs/ast0 -res 1024x768x60 now


fbconf_xorg: Unrecognized video mode, "1024*768*60"fbconf_xorg: Use "1024*768*60" anyway (yes/no) ?

Enter y, and then press Enter. A message similar to the following will be displayed:Setting 1024x768x60

f. To view the current configurations for the video board, run the following command:# fbconfig -dev /dev/fbs/ast0 -propt

The setting has taken effect if a message similar to the following is displayed.

--- Graphics Configuration for /dev/fbs/ast0 ---

xorg.conf: machine -- /etc/X11/xorg.conf Screen section: "ast0" Device section: "ast0" Monitor section: "ast0"

Video Mode: "VESA_STD_1024x768x60"

Screen Information: Remote Screen: Not set

3. To restart the OS, run the following command. After the OS is restarted, connect the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 to the KVM.

NOTE:If a message asking you to enter a user name is displayed on the monitor or KVM during the restart of the OS, ignore the message. The OS automatically accesses the login



window.

# sync;sync;sync;sync

# shutdown -y -g0 -i6


1.6.1.4.20 How Do I Enable the SSH Service for the XSCF on theM4000/M5000 ServerQuestion

How do I enable the SSH service for the XSCF?

Answer

1. Use the serial port cable to connect the serial port of the XSCF to that of the PC.Insert the RJ-45 connector of the serial port cable into the XSCF serial port; then insert the DB-9 connector into a serial port on the PC (COM1 orCOM2), as shown in Figure 1 and Figure 2.

Figure 1 Serial port connection between the M4000 server and the PC

1 Serial port of the XSCF 2 Ethernet port 1 of the XSCF 3 Ethernet port 0 of the XSCF

4 XSCF unit - -

Figure 2 Serial port connection between the M5000 server and the PC

1 Serial port of the XSCF 2 Ethernet port 1 of the XSCF 3 Ethernet port 0 of the XSCF

4 XSCF unit - -

For details about the cable sequence of the serial port cables and related signals, see Table 1.

Table 1 Wire sequence standards for the serial port cables between the XSCF and the PCRJ-45 Signal DB-9 Socket

3 TXD/RXD 2

4 REF/GND 5

5 REF/GND 5

6 RXD/TXD 3



After the PC and the XSCF are connected, the physical connection between the PC and the Sun M4000/M5000 server is set up.

2. Set up a logical connection between the computer and the server




Attribute Attribute Value


Speed(baud) 9600

Data bits 8

Stop bits 1

Parity None

Flow Control None


e. Click Open.

3. If the following information is displayed in the PuTTY window, enter the user name eis-installer and the password.login: eis-installerPassword:

4. Run the following command to enable the SSH service for the XSCF:XSCF> setssh -c enable

5. When the system displays the following message, type y and press Enter:Continue? [y|n] :y

6. When the system displays Please reset the XSCF by rebootxscf to apply the ssh settings., run the following command to restart the XSCF for thesettings to take effect:XSCF> rebootxscf

7. When the system displays the following message, type y and press Enter:The XSCF will be reset. Continue? [y|n] :y

NOTE:The XSCF restart takes about 5 minutes.


1.6.1.4.21 How to Obtain Packet Headers on SolarisQuestion

Packet headers obtain may be required for fault locating. How do I obtain packet headers on Solaris?

Answer

NOTICE:To ensure security of customers' networks, obtain customers' written authorization before you obtain packet headers. In addition, comply with laws ofassociated countries or user privacy policies of Huawei and take effective measures to ensure that personal data is fully protected.


2. Run the snoop command to obtain packet headers. The common format of the snoop command is snoop -d NIC name -o Generated file name IPaddress.

NOTE:snoop is a command provided by Solaris. For more information about how to use this command, run the man snoop command.To stop capturing packets, press Ctrl+C.

Command description:

NIC name: name of the NIC communicating with the destination IP address.

Generated file name: usually in the format of xxxx.cap.

IP address: IP address of the packet headers obtain target. It is usually the IP address of an NE.

Command use example: For example, it is assumed that the IP address of an NE is 10.71.212.13, the name of the NIC that the server uses



to communicate with the NE is bge0, and the name of the file generated after packet headers obtain is complete is /opt/123.cap.

Run the following command to obtain packet headers:# snoop -d bge0 -o /opt/123.cap 10.71.212.13


1.6.1.4.22 Mappings Between Physical and Logical Network Interfaces onServer Running Solaris

This topic describes the mappings between physical and logical network interfaces on server running Solaris.

Example 1: In Figure 1, the mappings between the physical and logical network interfaces for the Netra T4-1 are described as follows:

The Netra T4-1 is integrated with one NIC. The associated logical network interfaces on the integrated NIC are named igb0, igb1, igb2, and igb3.

If an NIC is inserted to the PCI slot, the logical network interfaces on the NIC are numbered from right to left in ascending order.

Figure 1 Mappings between physical and logical network interfaces on the Netra T4-1

Example 2: In Figure 2, the mappings between the physical and logical network interfaces for the Oracle T4-1 are described as follows:

The Oracle T4-1 is integrated with one NIC. The associated logical network interfaces on the integrated NIC are named igb0, igb1, igb2, and igb3.


Figure 2 Mappings between physical and logical network interfaces on the Oracle T4-1

Example 3: In Figure 3, the mappings between the physical and logical network interfaces for the Oracle T4-2 are described as follows:

One NIC is integrated to the Oracle T4-2. The four logical network interfaces on the NIC are identified as follows from left to right and from top tobottom:igb2, igb3, igb0, and igb1.

If an NIC is inserted to the PCI slot, the logical network interfaces on the NIC are numbered from top to bottom in descending order.

Figure 3 Mappings between physical and logical network interfaces on the Oracle T4-2



Example 4: In Figure 4, the mappings between the physical and logical network interfaces for the T5220 are described as follows:

The T5220 is integrated with one NIC. The associated logical network interfaces on the integrated NIC are named e1000g0, e1000g1, e1000g2, ande1000g3.


Figure 4 Mappings between physical and logical network interfaces on the T5220


1.6.1.4.23 Description About Interfaces Connecting to Disk ArraysThis topic describes the interfaces connecting to disk arrays.Figure 1 is an example of the interfaces connecting to the S3900 disk array.

Figure 1 Description about the interfaces connecting to the S3900 disk array.


1.6.2 Veritas HA SystemThis topic covers FAQs about the Veritas HA system.

License ManagementThis topic describes the FAQs about license management.

System SettingsThis topic describes the FAQs about the system settings in the HA system.

Parent topic: FAQs

1.6.2.1 License ManagementThis topic describes the FAQs about license management.

Applying for a Veritas LicenseThis topic describes how to apply for a formal Veritas license. The Veritas license used during U2000 installation is a demo license. After the U2000server is delivered to the installation site, you must replace the demo license with a formal one in time.

How to Check the Veritas License



Parent topic: Veritas HA System

1.6.2.1.1 Applying for a Veritas LicenseThis topic describes how to apply for a formal Veritas license. The Veritas license used during U2000 installation is a demo license. After the U2000 server isdelivered to the installation site, you must replace the demo license with a formal one in time.

Context

The Veritas licenses for the primary and secondary sites are different and thus must be applied for separately.

Procedure

1. Collect the following information according to the Veritas license application form:

Serial number of the license confirmation form

Contract number

Software item

License item quantity

NOTICE:

The license confirmation form is delivered together with the DVD. The license confirmation form is in paper format and equals the licensefile. It must be properly stored on site.If there are multiple serial numbers and the software items are the same, you must fill in Software Item Qty with the total number oflicense confirmation forms.The license confirmation form is not delivered along with the product for the license whose Veritas software BOM starts with 9904. Enter aslash (\) in the license confirmation form column before contacting Huawei engineers to apply for the Veritas license.

2. Send the information to the related Huawei engineer or the local office of Huawei.

3. With the provided information, the related Huawei engineer accesses http://support.huawei.com and chooses Software Center > Software License> Outsourcing License > License Application. The page for applying for purchased software licenses is displayed.

4. Huawei engineer enters the license application information to apply for a Veritas license.

5. Huawei engineer sends you the Veritas license.

Parent topic: License Management

1.6.2.1.2 How to Check the Veritas LicenseQuestion

How to check the Veritas license?

Answer

1. Run the following commands as root user to query the details about the Veritas license.# vxlicrep -e|egrep 'Global|VVR|Product Name|KEYLESS|VxVM'




NOTE:Red characters indicate the VCS license. If Global Cluster Option (GCO) is Enabled and VXKEYLESS is Disabled, the formal VCS license is used.Blue characters indicate the VxVM license. If VxVM is Enabled and VXKEYLESS is Disabled, the formal VxVM license is used.Green characters indicate the VVR license. If VVR is Enabled and VXKEYLESS is Disabled, the formal VVR license is used.The value of VXKEYLESS is Disabled.

If the preceding four conditions are met, the license is a permanent formal license.

Parent topic: License Management

1.6.2.2 System SettingsThis topic describes the FAQs about the system settings in the HA system.

How to Log in and Exit the VCS (Veritas Cluster Server)

How to Query the RVG Status

How to Query the Rlink Status

How to Query the VVR Status

How to check whether the VCS service has been started

How to Manually Start the VCS Service

How to Manually Start the VVR

How to Manually Stop the VCS Service

How to Start/Stop the NMS Before Synchronizing the Primary and Secondary Sites (Solaris, PC Linux)

How to Ensure Proper Connection of VVR Ports on Primary and Secondary Sites

How to Change the admin User Password for Logging In to the VCS Client

Parent topic: Veritas HA System

1.6.2.2.1 How to Log in and Exit the VCS (Veritas Cluster Server)Question

How do I log in to and exit the VCS?

Answer

1. Log in to the VCS.

a. Open the Cluster monitor.



i. Log in to the OS as user root.

ii. Open a terminal window and run the following command:# hagui&

NOTE:If the login dialog box is not displayed and a message appears indicating that the current status is STALE_ADMIN_WAIT, run the # hasys -force host name ofnode command.

b. Click Connect to Cluster name.

NOTE:If you are logging in to the VCS for the first time, create a new cluster.

a. Click File > New Cluster.b. Enter the IP address of application network.c. Click OK.

c. Enter the user name and password for VCS login.


d. Click OK.

2. Exit the VCS:Choose File > Log Out to exit the VCS.

NOTICE:If the configuration changes, click Yes in the Confirmation dialog box when exiting the VCS. Otherwise, logging in to the VCS fails after theserver is restarted.

Parent topic: System Settings

1.6.2.2.2 How to Query the RVG StatusQuestion

How do I query the RVG status?

Answer

1. Log in to the primary site as user root.

2. Run the following command to view the RVG status of the active site:# vxprint -Vl


Disk group: datadg Rvg: datarvg info: rid=0.1269 version=4 rvg_version=30 last_tag=3state: state=ACTIVE kernel=ENABLED assoc: datavols=lv_nms_data srl=srl_vol rlinks=datarlk exports=(none)



vsets=(none) att: rlinks=datarlk flags: closed primary enabled attached attached device: minor=31004 bdev=315/31004 cdev=315/31004 path=/dev/vx/dsk/datadg/datarvg perms: user=root group=root mode=0600

Table 1 describes the RVG status of the primary site.

Table 1 RVG status of the primary siteField Description

Disk group Indicates the disk group where the RVG is located.

Rvg Indicates the name of the RVG.

info Indicates the information about the RVG.

state Indicates the status of the RVG. In normal cases, the situations are as follows:state is set to ACTIVE.kernel is set to ENABLED.

assoc Indicates the association information about the RVG.datavols indicates the data disk volume that the RVG contains.srl indicates the SRLog disk volume that the RVG contains.rlinks indicates the RLink that the RVG contains.

att Indicates the activated Rlink of the RVG.

flags Indicates the flag of the RVG. In normal cases, the value is closed primary enabled attached.

device Indicates the device information of the RVG, including the device ID and path.

perms Indicates the right information about the RVG.

3. Log in to the secondary site as user root.

4. Run the following command to view the RVG status at the secondary site:# vxprint -Vl

The following message will be displayed:Disk group: datadg

Rvg: datarvg info: rid=0.1269 version=4 rvg_version=30 last_tag=3state: state=ACTIVE kernel=ENABLED assoc: datavols=lv_nms_data srl=srl_vol rlinks=datarlk exports=(none) vsets=(none) att: rlinks=datarlk flags: closed secondary enabled attached device: minor=31004 bdev=315/31004 cdev=315/31004 path=/dev/vx/dsk/datadg/datarvg perms: user=root group=root mode=0600

For the description of the RVG status on the secondary site, see Table 1. Normally, flags on the secondary site is closed secondary enabledattached.


1.6.2.2.3 How to Query the Rlink StatusQuestion

How do I query the Rlink status?

Answer

1. Log in to the primary site as the root user.

2. Run the following command to view Rlink names:# vxprint -PlInformation similar to the following is displayed:Disk group: datadg

Rlink: datarlkinfo: timeout=500 packet_size=8400 rid=0.1113 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=nonestate: state=ACTIVE



synchronous=off latencyprot=off srlprot=autodcmassoc: rvg=datarvg remote_host=192.168.10.82 IP_addr=192.168.10.82 port=4145 remote_dg=datadg remote_dg_dgid=1356843347.7 remote_rvg_version=30 remote_rlink=datarlk remote_rlink_rid=0.1113 local_host=192.168.10.137 IP_addr=192.168.10.137 port=4145protocol: UDP/IPflags: write enabled attached consistent connected

NOTE:The datarlk in Rlink is an Rlink name.

3. Run the following command to query the RLink status:# vxprint -Pl <rlinkName>For example, run the following command to query the status of datarlk:# vxprint -Pl datarlk


Disk group: datadg Rlink: datarlk info: timeout=500 rid=0.1414 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none checksum=onstate: state=ACTIVE synchronous=off latencyprot=off srlprot=autodcmassoc: rvg=datarvg remote_host=192.168.1.11 IP_addr=192.168.1.11 port=4145 remote_dg=datadg remote_dg_dgid=1160936796.6.T522022456 remote_rvg_version=30 remote_rlink=datarlk remote_rlink_rid=0.1405 local_host=192.168.1.10 IP_addr=192.168.1.10 port=4145 protocol: UDP/IP flags: write enabled attached consistent connected asynchronousTable 1 describes the Rlink status on the primary site.

Table 1 Rlink status on the primary siteField Description

Disk group Indicates the disk group where the Rlink is located.

Rlink Indicates the name of the Rlink.

info Indicates the information about the Rlink.timeout indicates the timeout period.rid indicates the ID of the Rlink.latency_high_mark indicates the highest delay flag.latency_low_mark indicates the lowest delay flag.bandwidth_limit indicates the bandwidth limit.

state Indicates the status of the Rlink. In normal cases, the situations are as follows:state is set to ACTIVE.synchronous is set to off.latencyprot is set to off.srlprot is set to autodcm.

assoc rvg Indicates the RVG where the Rlink is located.

remote_host Indicates the name of the remote host.

IP_addr Indicates the IP address of the remote host.

remote_dg Indicates the remote disk group.

port Indicates the port number of the remote host.

remote_dg_dgid Indicates the ID of the remote disk group.

remote_rvg_version Indicates the RVG version of the remote host.

remote_rlink Indicates the Rlink name of the remote host.

remote_rlink_rid Indicates the Rlink ID of the remote host.

local host Indicates the name of the local host.

protocol Indicates the protocol for synchronizing data. The protocols configured on the primary and secondary sites must be the same.

flags Indicates the flag of the Rlink. Normally, the value is write enabled attached consistent connected asynchronous.

4. Log in to the secondary site as user root.



5. Run the following command to query the Rlink status:# vxprint -Pl <rlinkName>For example, run the following command to query the datarlk status:# vxprint -Pl datarlk


Disk group: datadg

Rlink: datarlk info: timeout=500 rid=0.1405 latency_high_mark=10000 latency_low_mark=9950 bandwidth_limit=none checksum=on state: state=ACTIVE synchronous=off latencyprot=off srlprot=autodcm assoc: rvg=datarvg remote_host=192.168.1.10 IP_addr=192.168.1.10 port=4145 remote_dg=datadg remote_dg_dgid=1160936853.6.T522022448 remote_rvg_version=30 remote_rlink=datarlk remote_rlink_rid=0.1414 local_host=192.168.1.11 IP_addr=192.168.1.11 port=4145 protocol: UDP/IP flags: write enabled attached consistent connected

For the description of the Rlink status on the secondary site, see Table 1.


1.6.2.2.4 How to Query the VVR StatusQuestion

How do I query the VVR status during the maintenance of the Veritas HA system?

Answer

1. Run the following command to view the rvg name of the replication system:# vradmin printrvgA message similar to the following will be displayed:Replicated Data Set: datarvgPrimary: HostName: 10.71.224.48 RvgName: datarvg DgName: datadgSecondary: HostName: 10.71.224.50 RvgName: datarvg DgName: datadg

In the preceding message, the rvg name (RvgName) is datarvg.

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

Rvg: datarvginfo: rid=0.1451 version=5 rvg_version=30 last_tag=4state: state=ACTIVE kernel=ENABLEDassoc: datavols=lv_nms_data srl=srl_vol rlinks=datarlk exports=(none) vsets=(none)att: rlinks=datarlkflags: closed primary enabled attacheddevice: minor=129007 bdev=309/129007 cdev=309/129007 path=/dev/vx/dsk/datadg/datarvgperms: user=root group=root mode=0600

In the preceding message, the Rlink name (Rlink) is datarlk.

3. Run the following commands to view other status information of the replication system. The parameters datarvg and datarlk are obtained in Step 1and Step 2.

Run the # vxdisk list command to query the disk status.

Run the # vxdg list command to query the status of the disk group.

Run the # vxprint -ht command to query the information about the disk volume.

Run the # vxprint -l datarvg command to query the RVG status.

Run the # vxprint -l datarlk command to query the Rlink status.



Run the # vxrlink -g datadg status datarlk command at the primary site to query the replication cache status.

Save the response to the preceding commands.


1.6.2.2.5 How to check whether the VCS service has been startedQuestion

How to check whether the VCS service has been started?

Answer

1. Run the following command to check whether the VCS service has been started:# ps -ef | grep had

The following information is displayed:root 5852 1 0 07:14:51 ? 0:00 /opt/VRTSvcs/bin/hashadow root 5842 1 0 07:14:45 ? 1:36 /opt/VRTSvcs/bin/had -onenode

NOTE:If the displayed information contains /opt/VRTSvcs/bin/hashadow and /opt/VRTSvcs/bin/had -onenode, the VCS service has been started.


1.6.2.2.6 How to Manually Start the VCS ServiceQuestion

How do I manually start the VCS service?

Answer


2. Run the following command to start the VCS processes:# hastart -onenode


1.6.2.2.7 How to Manually Start the VVRQuestion

How do I manually start the VVR?

Answer


2. Run the following commands to start the VVR:# cd /etc/init.d# ./vras-vradmind.sh start


1.6.2.2.8 How to Manually Stop the VCS ServiceQuestion

How do I manually stop the VCS service?

Answer




2. Run the following command to check whether the VCS service has been started:# ps -ef | grep had

The following information is displayed:root 5852 1 0 07:14:51 ? 0:00 /opt/VRTSvcs/bin/hashadowroot 5842 1 0 07:14:45 ? 1:36 /opt/VRTSvcs/bin/had -onenode

NOTE:If the displayed information contains /opt/VRTSvcs/bin/hashadow and /opt/VRTSvcs/bin/had -onenode, the VCS service has been started. Perform 3. Otherwise, the follow-upoperation is not required.

3. Optional: Run the following command to stop the VCS service:# hastop -all -force


1.6.2.2.9 How to Start/Stop the NMS Before Synchronizing the Primary andSecondary Sites (Solaris, PC Linux)Question

How to start/stop the NMS before synchronizing the primary and secondary sites of a high availability system (Solaris, PC Linux)?

Answer

GUI mode:


2. Open a CLI.

3. Run the following command to start the VCS client:# hagui&

NOTE:If the OS was just restarted, wait 10 to 15 minutes. After the process starts, run the hagui& command.

4. Choose File > New Cluster. Then, enter the server IP address and click OK.


5. Enter the user name and password for VCS login.


6. Ensure that the datarvg resource in the VVRService resource group has been enabled.Right-click the datarvg resource and check whether the Enabled option is selected. If this option is selected, it has been enabled.



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

7. Ensure that the VVRService resource group has been started.Select the VVRService resource group, click the Status tab, and check whether the value in the State column is Online. If Online isdisplayed as shown in the following figure, the VVRService resource group has been started.

If the VVRService resource group has not been started, do as follows to start it:

a. Right-click the VVRService resource group and choose Online > host name from the shortcut menu.

b. In the dialog box that is displayed, click Yes to make the resource group online.

8. Ensure that all resources in the AppService resource group have been enabled.Right-click a resource in the AppService resource group and check whether the Enabled option is selected. If this option is selected, theresource has been enabled. If this option is not selected, you must select it. Repeat this operation on every resource in the AppServiceresource group.

9. Optional: Ensure that Autoenable of the AppService resource group has been grayed out, as shown in the following figure.



If Autoenable has been grayed out, no action is required.

If Autoenable has not been grayed out, click Autoenable to gray it out.

10. Click File > Save Configuration to save the settings.

11. Start the AppService resource group.

a. Right-click the AppService resource group and choose Online > host name from the shortcut menu.

b. In the dialog box that is displayed, click Yes to start the AppService resource group.Select the AppService resource group and click the Status tab to view the status for the resource group in the State column. Ifthe resource group is in the Online state, it AppService has started.

NOTICE:If an exclamation mark is displayed for the NMSServer icon, restart the VCS client several times until the exclamation mark disappears.For details about how to restart the VCS client, see Step 2 to 5.

NOTE:To stop the AppService resource group, perform the following steps:

a. Right-click the AppService resource group and choose Offline > host name from the shortcut menu.b. In the dialog box that is displayed, click Yes to stop the AppService resource group.

CLI mode:


2. Run the following commands to start the U2000 server:# haconf -makerw > /dev/null 2>&1# hares -modify datarvg Enabled 1# hares -modify DatabaseServer Enabled 1# hares -modify BackupServer Enabled 1# haconf -dump -makero# hagrp -online AppService -sys hostname

NOTE:To stop the U2000 service, run the following command:# hagrp -offline AppService -sys hostname


1.6.2.2.10 How to Ensure Proper Connection of VVR Ports on Primary andSecondary SitesQuestion

How to ensure proper connection of VVR ports on primary and secondary sites?



Answer

1. Log in to the OSs of the primary and secondary sites of as the root user.

2. Run the following commands on the primary and secondary sites to check whether the VVR ports used by the peer site can be connected properly:

NOTE:The numbers of the ports to be checked are 4145, 8199, and 8989.

# cd /opt/OSSICMR/bin# chmod 750 Hacheck.sh# ./Hacheck.sh Peer site system IP address

Peer ossuser user password.If the command output indicates that the ports with the numbers of 4145, 8199, and 8989 are used correctly, the VVR ports are connected properly.


1.6.2.2.11 How to Change the admin User Password for Logging In to theVCS ClientQuestion

How to I change the admin user password for logging in to the VCS client?

Answer

1. Log in to the server OS as the root user.

2. Ensure that the VCS service has started. If the VCS service is not started, run the following command to start it:# hastart -onenode

3. Run the following command to enable the VCS to be configurable:# haconf -makerw > /dev/null 2>&1

4. Run the following commands to change the admin user password:# /opt/VRTSvcs/bin/hauser -update admin# Enter Password:

Enter a new password.# Enter Again:

Enter the new password again.# haconf -dump -makero


1.6.3 Sybase DatabaseThis topic covers FAQs about the Sybase database.

Startup and Shutdown of the Sybase DatabaseThis topic describes the FAQs about the startup and shutdown of the Sybase database.

Sybase Database MaintenanceThis topic describes the FAQs about the Sybase database maintenance.

Parent topic: FAQs

1.6.3.1 Startup and Shutdown of the Sybase DatabaseThis topic describes the FAQs about the startup and shutdown of the Sybase database.

How to Disable the Sybase Database Service

How to Start the Sybase Database Service

How to Verify That the Sybase Database Is Running

Parent topic: Sybase Database



1.6.3.1.1 How to Disable the Sybase Database ServiceQuestion

How do I disable the Sybase database service?

Answer

1. Perform the following operations to disable the Sybase database service at the primary site in the HA system:

NOTE:By default, the Sybase database service at the secondary site is not running.

GUI mode:

a. Log in to the primary site as user root.

b. Run the following command to start the VCS client at the primary site:# hagui&

c. Choose File > New Cluster from the main menu. In the window that is displayed, enter the IP address of the server and clickOK.


d. Enter the default user name admin and the initial password Changeme_123 for the VCS client. For system security, modify thedefault password and remember the new password. For detail, see How to Change the admin User Password for Logging In tothe VCS Client. Then click OK.

e. On the VCS client of the primary site, right-click the NMSServer node and choose Offline > hostname from the shortcut menu.

f. In the confirmation dialog box, click Yes.

g. After the NMSServer node is dimmed, right-click the BackupServer node and choose Offline > hostname from the shortcutmenu.

h. In the confirmation dialog box, click Yes.

i. After the BackupServer node is dimmed, right-click the DatabaseServer node and choose Offline > hostname from theshortcut menu.

j. In the confirmation dialog box, click Yes.

CLI mode:


b. Run the following command to shut down the U2000:# hares -offline NMSServer -sys hostname

c. Run the following command to disable the Sybase database service:# hares -offline BackupServer -sys hostname

# hares -offline DatabaseServer -sys hostname


Run the following command to check whether the Sybase database service is disabled:# ps -ef | grep sybaseIf 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

Parent topic: Startup and Shutdown of the Sybase Database

1.6.3.1.2 How to Start the Sybase Database ServiceQuestion

How do I start the Sybase database service?

Answer

Perform the following operations to start the Sybase database service in the HA system:

GUI mode:

1. Log in to the active site as the root user.



2. Run the following command to start the VCS client:

# hagui&

3. Choose File > New Cluster from the main menu. In the dialog box that is displayed, enter the server IP address and click OK.


4. Enter the default user name admin and the initial password Changeme_123 for the VCS client. For system security, modify thedefault password and remember the new password. For detail, see How to Change the admin User Password for Logging In to theVCS Client. Then click OK.

5. Ensure that all Veritas resources are in Enabled state. Use the BackupServer resource as an example. Perform the followingoperations:Expand the AppService node and then the SybaseBk node in the navigation tree, right-click BackupServer, and check whetherEnabled has been selected in the shortcut menu. If Enabled has not been selected, select it.

6. Right-click BackupServer and choose Online > host name from the shortcut menu.

7. In the dialog box that is displayed, click Yes.Wait until the BackupServer and DatabaseServer resource icons on the Resources tab page are bright, which indicates that theSybase database service has started.

CLI mode:

1. Log in to the active site as the root user.

2. Run the following commands to query Veritas resource names:# haconf -makerw# hares -list

Information similar to the following is displayed:BackupServer PrimaryDataFilesystem PrimaryDatabaseServer PrimaryNMSServer PrimaryRVGPrimary Primarydatarvg Primarywac Primary

3. Run the hares -modify resource name Enabled 1 command to change the status of all Veritas resources to Enabled. Use theresource names displayed in the previous command output as an example. Run the following commands to change the status of allthe Veritas resources to Enabled:

# hares -modify BackupServer Enabled 1# hares -modify DataFilesystem Enabled 1# hares -modify DatabaseServer Enabled 1# hares -modify NMSServer Enabled 1# hares -modify RVGPrimary Enabled 1# hares -modify datarvg Enabled 1# hares -modify wac Enabled 1

4. Run the following command to start the Sybase database service:# hares -online BackupServer -sys hostname



1.6.3.1.3 How to Verify That the Sybase Database Is RunningQuestion

How do I verify that the Sybase database is running?

Answer


2. Enter the CLI and run the following commands to check the Sybase process status:# su - dbuser$ cd /opt/sybase/ASE*/install$ ./showserver

A message similar to the following will be displayed: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 dbuser 4563 4559 0 18:42:50 ? 0:00 /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install dbuser 4170 4168 0 18:42:00 ? 546:12 /opt/sybase/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 has been started.


1.6.3.2 Sybase Database MaintenanceThis topic describes the FAQs about the Sybase database maintenance.

How to Verify That the Sybase Database Has Been Installed

How to Check the Sybase Database Version

How to View the Server Name of the Sybase Database

How to Change the sa User Password for the Sybase Database If the U2000 Is Not Installed

How to Change the sa User Password for the Sybase Database If the U2000 Is Installed

How to View the Bit Number of the Sybase Database

How to View the Details of the Sybase Database

How to Change the Server Name of the Sybase Database to DBSVR

How to Delete Redundant Database Items

Parent topic: Sybase Database

1.6.3.2.1 How to Verify That the Sybase Database Has Been InstalledQuestion

How do I verify that the Sybase database has been installed?

Answer

NOTE:

The Sybase database will be automatically installed when the U2000 is installed if the Sybase database does not exist on the system.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 theSybase database if it is reused (saves time, but not recommended).

Consult with the computer administrator to see if the Sybase database has been installed.

Verify that the installation directory and file of the Sybase database exist. A sample directory is /opt/sybase.

Verify that the version of the Sybase database is correct. For details, see How to Check the Sybase Database Version.

Verify that the Sybase database is running. For details, see How to Verify That the Sybase Database Is Running. For details about how to start theSybase database, see How to Start the Sybase Database Service.

Parent topic: Sybase Database Maintenance

1.6.3.2.2 How to Check the Sybase Database VersionQuestion

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

1. Log in to the OS as user dbuser.

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 detail, see How to Change the OS User Password.

2. Run the following commands:$ cd /opt/sybase/OCS*/bin



$ ./isql -SDBSVR -Usa

NOTE:Enter the database sa user password as prompted.

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.

A message similar to the following will be displayed:-----------------------

Adaptive Server Enterprise/15.5/EBF 21258 SMP ESD#5.3/P/Sun_svr4/OS 5.8/asear15 5/2613/64-bit/FBO/Wed Jul 24 10:35:03 2013

(1 row affected)

The preceding message indicates that Sybase database version is SYBASE 15.5.

NOTE:EBF 21258 indicates the latest Sybase patch. The earlier Sybase patches are not displayed.


1.6.3.2.3 How to View the Server Name of the Sybase DatabaseQuestion

How do I view the server name of the Sybase database?

Answer



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

A message similar to the following will be displayed:DBSVR master tcp ether 10.71.225.89 4100 query tcp ether 10.71.225.89 4100 master tcp ether 10.71.225.89 4100 query tcp ether 10.71.225.89 4100 master tcp ether 127.0.0.1 4100 query tcp ether 127.0.0.1 4100

DBSVR_back master tcp ether 10.71.225.89 4200 query tcp ether 10.71.225.89 4200 master tcp ether 10.71.225.89 4200 query tcp ether 10.71.225.89 4200 master tcp ether 127.0.0.1 4200 query tcp ether 127.0.0.1 4200

NOTE:DBSVR and DBSVR_back is server name of the Sybase database.


1.6.3.2.4 How to Change the sa User Password for the Sybase Database Ifthe U2000 Is Not Installed



QuestionHow to change the sa user password for the Sybase database if the U2000 is not installed?

Answer



2. Run the following commands:$ cd /opt/sybase/OCS*/bin$ ./isql -SDBSVR -Usa


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:

Be sure to remember the password of user sa. If this password is missed, database-related operations may fail to be performed.The database sa user password must meet the following requirements, please set the new password as required:

The OSS database user password must meet the requirements:

The password contains a minimum of eight characters and a maximum of 30 characters.The password must contain at least four of the following combinations:

At least one lower-case letterAt least one upper-case letterAt least one digitAt least one special character ~@#^*-_+[{}]:./?Other special characters are not supported. Do not include other special characters, such as ()|<>&`!$\"%'=;,space inpasswords.


The default value is Changeme_123.Leave a space between sp_password and old password.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>

4. Run the quit command to exit.


1.6.3.2.5 How to Change the sa User Password for the Sybase Database Ifthe U2000 Is InstalledQuestion

How to change the sa user password for the Sybase database if the U2000 is installed?

NOTICE:

In the high availability system (Veritas hot standby), change the password of the user sa of the database only on the MSuite server at the primary site.The passwords of the user sa of the databases at both the primary and secondary sites are changed.After the U2000 is installed, using the MSuite to change the password of the sa user is recommended. Do not manually change the password.Otherwise, the U2000 may fail to be started properly. If the password of the sa user is changed manually, you must use the MSuite to change thepassword again to ensure the normal operation of the U2000.

Answer



1. Shut down the NMS server and client.Log in to the primary site and run the following command to start the VCS client:# hagui&

Choose File > New Cluster from the main menu. In the window that is displayed, enter the IP address of the server and click OK.


Enter the user name and password for VCS login.

NOTE:The default VCS user name is admin and the default password is Changeme_123. To ensure system security, change the default password in time. If the default password hasbeen changed, enter the new password.

Right-click NMSServer and choose Offline > Host name from the shortcut menu.In the confirmation dialog box, click Yes.

NOTE:Ensure that the database is running.


3. On the MSuite client, choose Deploy > Change Database Administrator Password. The Change Password dialog box is displayed.

4. Enter the old password and new password.

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





5. Click OK. The password is changed.

NOTE:If the following information is displayed, the database sa user password has been changed successfully.

Succeeded in changing the password.After changing the database sa user password, start U2000 server processes.


1.6.3.2.6 How to View the Bit Number of the Sybase DatabaseQuestion

How do I view the bit number of the Sybase database?

Answer



2. Run the following commands:$ cd /opt/sybase/OCS*/bin$ ./isql -SDBSVR -Usa


3. Run the following commands to view the bit number of the Sybase database:1>select @@version2>go




There must be a space between select and @ in the select @@version command.

The following message will be displayed on the Solaris OS: Adaptive Server Enterprise/15.5/EBF 21258 SMP ESD#5.3/P/Sun_svr4/OS 5.8/asear15 5/2613/64-bit/FBO/Wed Jul 24 10:35:03 2013

(1 row affected)

64-bit indicates the bit number of the Sybase database.


1.6.3.2.7 How to View the Details of the Sybase DatabaseQuestion

How do I view the details about the Sybase database during routine maintenance?

Answer


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 thedefault password and remember the new password. For detail, see How to Change the OS User Password.

2. Run the following commands to view the details of all databases:$ cd /opt/sybase/OCS*/bin$ ./isql -SDBSVR -Usa


1>sp_helpdb

2>go

The information about the Sybase database will be displayed, including the name, size, owner, and status.ason_otn_db 200.0 MB sa 38 Nov 01, 2013 full select into/bulkcopy/pllsort, trunc log on chkpt, abort tran on log ful l ason_sdh_db 200.0 MB sa 40 Nov 01, 2013 full select into/bulkcopy/pllsort, trunc log on chkpt, abort tran on log ful l

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.


1.6.3.2.8 How to Change the Server Name of the Sybase Database to DBSVRQuestion

If the OS is configured and the NMS installation needs to reuse the installed database, the database server name needs to be changed to DBSVR. How do Ichange the server name?

Answer




2. Run the following commands to view the server name of the Sybase database:# more /opt/sybase/interfaces

Information similar to the following is displayed:DBSVR master tcp ether 10.71.225.89 4100 query tcp ether 10.71.225.89 4100 master tcp ether 10.71.225.89 4100 query tcp ether 10.71.225.89 4100 master tcp ether 127.0.0.1 4100 query tcp ether 127.0.0.1 4100


3. Run the following commands to change the database server name to DBSVR if the name is not DBSVR:# . /opt/sybase/SYBASE.sh# cd /opt/OSSENGR/upgrade/scripts/solaris# ./_modifyInterfaces.sh old_main_DBServer_name DBSVR# ./_modifyCfgFile.sh old_main_DBServer_name DBSVR# ./_modifyLogFile.sh old_main_DBServer_name DBSVR# ./_modifyRunFile.sh old_main_DBServer_name DBSVR

In the preceding command, old_main_DBServer_name indicates the name of the server to be reused.


1.6.3.2.9 How to Delete Redundant Database ItemsQuestion

If the NMS installation needs to reuse the installed database, redundant database items need to be deleted. How do I delete redundant database items?

Answer


2. Run the following commands to view databases:# su - dbuser$ . /opt/sybase/SYBASE.sh$ cd /opt/sybase/OCS*/bin$ ./isql -SDBSVR -Usa


1> sp_helpdb2> go

Information similar to the following is displayed: name db_size owner dbid created durability status ... smdb 250.0 MB sa 8 Jan 21, 2013 full select into/bulkcopy/pllsort, trunc log on chkpt master 474.0 MB sa 1 Jan 21, 2013 full mixed log and data model 12.0 MB sa 3 Jan 21, 2013 full select into/bulkcopy/pllsort, trunc log on chkpt, mixed log and data sybsystemdb 12.0 MB sa 31513 Jan 21, 2013 full



mixed log and data tempdb 2060.0 MB sa 2 Jan 21, 2013 no_recovery select into/bulkcopy/pllsort, trunc log on chkpt, ddl in tran

(1 row affected)(return status = 0)1>

Look over the displayed message and delete any redundant databases other than master, model, sybsystemdb, sybsystemprocs, tempdb exist.

NOTE:If the NMS of Chinese edition is installed, illegible characters may be displayed when you log in to the system using the remote terminal login tool (CLI-based). If thishappens, set the encoding scheme of the remote terminal login tool to UTF-8.If the remote terminal login tool does not support the ability to set the encoding scheme, log in to the system by using the GUI.

3. Perform the following operations to delete the information about the redundant databases: (The following uses the smdb as an example.)

a. Run the following commands to view the device information in the smdb database:1> sp_helpdb smdb2> go

Information similar to the following is displayed: name db_size owner dbid created durability status ---------------- ---------------------------------------------------- -------------------- ---------------- ------------------------------------------------ ---------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ smdb 250.0 MB sa 8 Jan 21, 2013 full select into/bulkcopy/pllsort, trunc log on chkpt

(1 row affected) device_fragments size usage created free kbytes ------------------------------ ------------- -------------------- ------------------------- ---------------- smdbdata 100.0 MB data only Jan 21 2013 5:36PM 59808 smdblog 100.0 MB log only Jan 21 2013 5:36PM not applicable smdbdata 50.0 MB data only Jan 21 2013 6:06PM 51000 ----------------------------------------------------------------------------------------------------------------- log only free kbytes = 101944 (return status = 0)1>

b. Run the following commands to delete the smdb database and the smdbdata and smdblog items in the smdbdata database:1> drop database smdbdata2> go1> sp_dropdevice smdbdata2> go1> sp_dropdevice smdblog2> go

c. Run the following commands to exit the SQL and log out as user dbuser:1> exit$ exit

d. Run the following commands to go to the sybase directory and delete the associated files of the device information from the smdbdatabase:# cd /opt/sybase/data# rm smdbdata.dat# rm smdblog.dat


1.6.4 U2000 SystemThis topic covers FAQs about the U2000 system.

Failure to Start Certain Processes of the U2000 Server



How to Start the MSuite Client

Changing the Password of the MSuiteThis topic describes how to change the password of the MSuite. To ensure the security of the U2000, change the password of the MSuite immediatelyand record the password after installing the U2000 server.

How to Check Whether the U2000 Processes of the High Availability System (Solaris, PC Linux) Are Started

How to Start the U2000 Processes of the High Availability System (Solaris, PC Linux)

How to End the U2000 Processes of the High Availability System (Solaris, PC Linux)

How to Determine Which Types of Software Are Preinstalled

Which Installation Packages Are Required for U2000 Installation

How to Rectify the Application GUI Startup Failure Caused by User Switching

How to View the U2000 and Sybase Database Installation Paths

How to View Network Configurations for the Primary Site or Secondary Site Installed with a HA System (Solaris)

How to Check Downloaded Software Packages by Using HashMyFiles Software

How to Set the Communication Mode of the Server in a High Availability System (Solaris, SUSE Linux)

How to Confirm the Encoding Format of the U2000 License File

How to Solve the Instance Inconsistency Problem During Connection Between the Primary and Secondary Sites in a Solaris High AvailabilitySystem

How to Change the OS User Password

How to Restore the OSSENGR and OSSICMR Directories Which Are Misoperated (Solaris/SUSE Linux)

How to Use the FileZilla to Transfer Files by SFTP

How to Transfer Files by Means of FTP

How to Check and Change an OS User ID

How to Deal with an Automatically Configured Temporary IP Address

How to Burn the ISO File to DVD

How to Address the Failure to Download JNLP Files After the Download File Option Is Clicked on the Address Bar of the Internet ExplorerBrowser

Parent topic: FAQs

1.6.4.1 Failure to Start Certain Processes of the U2000 ServerSymptom

On the System Monitor client, certain processes of the U2000 server are not running.

Possible Causes

The server IP address is changed incorrectly. As a result, the configuration of IP addresses in certain processes is not refreshed accordingly.

The password of the sa user is incorrect or not changed properly; as a result, some processes fail to be started.

User root is used to start these processes but exits abnormally before the processes are started.

These processes are not configured properly. For example, the NBI processes are not configured in advance.

Licenses are not obtained and updated for the relevant functions.

Ports are occupied.

The memory configurations of the U2000 server do not meet running requirements. As a result, some processes fail to start. For example, if thememory of the T5220 workstation is smaller than 8 GB, the desktop server process may fail to start.

If 360 software has been installed in the environment, some U2000 files will be deleted; as a result, the process cannot be started.

Procedure

1. On the System Monitor client, manually start the processes that are currently not started to check whether the failure recurs or whether relevantmessages are displayed.

2. Restart the U2000 and check whether the processes are started.

3. Check whether the server IP address is changed. If the IP address is changed, ensure that it is changed according to the related operation guide. If theIP address is changed incorrectly, restore to the previous setting and then change the IP address again. For details, see section "Changing the System



IP Address and Host Name" in the U2000 Administrator Guide.

4. Check whether the password of the sa user has been manually changed. If so, use the MSuite to change the password again.

5. Ensure that licenses are obtained and updated for the relevant functions.

6. If the account root has been used to start these processes but exits abnormally before the processes are started, perform the following steps:

a. Start the processes as the root user and exit after the processes are started.

b. Restart the OS.

7. If a process, such as the CORBA NBI process, fails to be started, check the NBI settings or re-configure the NBI.

8. Check whether the ports used by these processes are occupied.

9. If the server is switched off illegally or powered off or the database has been restored, it is recommended that you initialize the database and restoredata. Then, restart the U2000 server.

10. Check whether the hardware configurations of the U2000 server meet requirements. For the requirements, see the U2000 Planning Guide. If thehardware configurations do not meet requirements, replace the U2000 server.

11. If the 360 software does not function properly, uninstall the 360 software and re-install the U2000.

12. If this problem persists after the preceding operations, contact Huawei engineers.

Suggestion and Summary

When changing the IP address, follow the related operation guide. Otherwise, the U2000 may malfunction.

Starting or stopping the U2000 as the ossuser user is recommended.

Parent topic: U2000 System

1.6.4.2 How to Start the MSuite ClientQuestion

How do I start the NMS maintenance suite client?

Answer

It must meet the following requirements for starting the NMS maintenance suite client:

The MSuite server must be started.

Port 12212 on the MSuite server is enabled.

The MSuite client and the server communicate with each other properly.

The MSuite server process is started on both the primary and secondary sites during some operations in the high availability system, and the MSuiteclient can properly communicate with the MSuite server on both the primary and secondary sites.

1. Ensure that the MSuite server has been started.

In Solaris OS, run the following command as user root to verify that the MSuite server is running:# ps -ef | grep java

The MSuite server is running if /opt/OSSJRE/jre_sol/bin/java -server is displayed. Run the following commands to start the MSuite server if it isnot running:# cd /opt/OSSENGR/engineering# ./startserver.sh

2. On a computer where the MSuite client is installed, double-click the U2000 NMS Maintenance Suite shortcut icon on the desktop and then waitabout one minute. The Login dialog box is displayed.

NOTE:In Solaris or SUSE Linux OS, log in to the Java desktop system as user ossuser. Otherwise, the U2000 NMS Maintenance Suite shortcut icon is not displayed on thedesktop. To start the MSuite client by running commands, run the following commands as user ossuser. If you have logged in as the root user, relog in to the OS asuser 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.shIf 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 byusing the CAU is as follow:

a. Install the U2000 client software in network mode: Enter https://server_IP_address/cau/ (more secure, recommended) or http://server_IP_address/cau/ inthe address box of the Internet Explorer, and press Enter to access the Web installation page. For details, see U2000 Client Software Installation Guide inthe U2000 Client Software Installation Guide.

b. If you upgrade the U2000 client software using the CAU, the MSuite client is also upgraded.

3. Set the login parameters.

IP Address:

To log in to the local MSuite server, use the default IP address 127.0.0.1.

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

Password: The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The passwordmust be changed during the first login to ensure system security. Keep the password confidential and change it regularly. For details, seethe MSuite help.

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


1.6.4.3 Changing the Password of the MSuiteThis topic describes how to change the password of the MSuite. To ensure the security of the U2000, change the password of the MSuite immediately andrecord the password after installing the U2000 server.

Context

In the high availability system, you only need to log in to the MSuite server on the primary site and change the password of the MSuite. The password of theMSuite on the secondary site is then automatically changed.

Procedure


2. On the MSuite client, choose System > Change Password from the main menu. The Change Password dialog box is displayed.

3. Click OK. The Change Password dialog box is displayed.

4. Enter the old password and new password.

NOTE:The initial password is Changeme_123.

The rules for modifying a password are as follows:

The password contains a minimum of 8 characters and a maximum of 30 characters.The password must contain four of the following combinations:




If the password does not meet requirements, an error message will be displayed.

5. Click OK. The password is changed.


1.6.4.4 How to Check Whether the U2000 Processes of the High AvailabilitySystem (Solaris, PC Linux) Are StartedQuestion

How to check whether the U2000 processes of the high availability system (Solaris, PC Linux) are started?

Answer

1. Log in to the OS of the active site as the ossuser user.

2. Check the U2000 processes.Run the following command to check whether the U2000 is running:



$ daem_ps


NOTE:The U2000 is running if the displayed information contains imap_sysmonitor -cmd start. If no introduction is displayed, the U2000 processes have been stopped.


1.6.4.5 How to Start the U2000 Processes of the High Availability System(Solaris, PC Linux)Question

How do I start the U2000 processes of the high availability system (Solaris, PC Linux)?

Answer

1. Log in to the OS on the active site as the root user.

2. Start the U2000 server processes.

GUI mode:

a. Open a terminal window and run the following command:

# hagui&

NOTE:If the login dialog box is not displayed and a message appears indicating that the current status is STALE_ADMIN_WAIT, run the # hasys -force hostname of node command.

b. Choose Connect to cluster name.


a. Choose File > New Cluster.b. Enter an application network IP address.c. Click OK.


NOTE:The default VCS user name is admin and the default password is Changeme_123. To ensure system security, change the default password in time. If thedefault password has been changed, enter the new password.

d. Click OK.

e. In the Cluster Explorer window, select the NMSServer resource group in the navigation tree, right-click, and choose Online >primary from the shortcut menu to start the U2000 server processes.

NOTE:Click the Resources tab to view the start status of each resource.

Normally, the value of State for the active site is Online in the Group Status on Member Systems area on the Status tab page,and the value of Status is Online on primary in the Resource Status area.

NOTE:



Use the actual host name for real-world configuration.If a fault has occurred during the start of the AppService process, right-click AppService and choose clear fault from the shortcut menu torectify the fault. Then choose Online > host name to start the process.


CLI mode:

# hares -online NMSServer -sys hostname


1.6.4.6 How to End the U2000 Processes of the High Availability System(Solaris, PC Linux)Question

How do I end the U2000 processes of the high availability system (Solaris, PC Linux)?

Answer

1. Log in to the OS of the active site as the root user.

2. Stop the U2000 server processes.

GUI mode:

a. Open a terminal window, run the following command:

# hagui&



NOTE:If you are logging in to the VCS for the first time, you need to create a new Cluster.




d. Click OK.

e. Choose AppService from the navigation tree.

f. Click the Resources tab. Right-click NMSServer and choose Offline > Host name from the shortcut menu.Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes have been stopped.

CLI mode:# hares -offline NMSServer -sys hostname




1.6.4.7 How to Determine Which Types of Software Are PreinstalledQuestion

Servers come preinstalled with software from Huawei. The U2000 servers come preinstalled to different extents according to the scheme and softwarepurchased. How do I determine which types of software are preinstalled?

Answer

The U2000 is installed based on the BOM.

If the U2000 license BOM is available, the U2000 HA system needs to be installed according to the license BOM while the primary site andsecondary site are separated as much as possible. Technical support engineers need to change the IP address, check that the network between theprimary site and secondary site is functioning properly, and then connect the two sites.

If the U2000 license BOM is unavailable, only the OS needs to be installed.


1.6.4.8 Which Installation Packages Are Required for U2000 InstallationQuestion

Which installation packages are required for U2000 installation?

Answer

Prepare installation packages according to the U2000 installation scheme.

Table 1 Software required for installationSoftware Medium Description

Solaris 10 OS You can install Solaris 10 OS by using the quick installation DVD.The quick installation DVD.

Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4v_dvd2 isavailable if the hardware type of the selected server is sun4v (the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server for example).Ensure that the quick installation DVD U2000version_server_os_solaris_SPARC_U10_sun4u_dvd1 isavailable if the hardware of the selected server is sun4u (the M4000/M5000 server for example).

NOTE:If the server has been configured with an OS, log in to the OS as the root user and run the uname -m command to view thehardware type of the server.

SetSolaris software package Installation package: U2000version_VPPSetsolarisV300R003C20SPC100.tarIt is used to enhance the security of Solaris system.

Database Installation DVD or installation packageInstallation DVD: U2000version_server_db_solaris_SPARC_dvd4Installation software package: U2000version_server_db_solaris_SPARC.tar

Veritas software Veritas software installation DVD or installation packageVeritas software installation DVD: Solaris_Veritas6.0.1Veritas software installation package: U2000version_veritas6.0.1_solaris.tar.gzVeritas patch installation DVD: U2000version_server_patch_solaris_SPARC_dvd3Veritas patch Installation package: U2000version_server_veritas603100_patch_solaris_SPARC.tar

U2000 server software Installation DVD or installation packageInstallation DVD: U2000version_server_nms_solaris_SPARC_dvd5Installation package:

NOTE:Prepare software packages required by the components to be installed.

Do not prepare U2000version_client_solaris_SPARC.tar software packages. If the U2000version_client_solaris_SPARC.tar andthe following software packages are decompressed into the same path, the U2000 installation will fail.

Basic component: U2000version_server_nmsbase_solaris_SPARC.tarIt must be available. It is used to install the U2000.Core component: U2000version_server_nmscore_solaris_SPARC.tarIt must be available. It is used to install the U2000.Transport domain component: U2000version_server_nmstrans_solaris_SPARC.tarIt is required only if the U2000 needs to manage Huawei transport equipment. Huawei transportequipment includes:

MSTP equipment



WDM equipmentNA WDM equipmentSubmarine equipmentRTN equipmentPTN equipment

NOTE:Software packages for the transport and IP components must be available so as to manage PTN 6900 seriesNEs.

IP domain component: U2000version_server_nmsip_solaris_SPARC.tarIt is required only if the U2000 needs to manage Huawei IP equipment. Huawei IP equipment includes:

ATN Series EquipmentRoutersSwitchesMetro service equipmentBroadband access equipmentVoIP gatewaysFirewallsService inspection gatewaySVN equipmentInternet Cache System

Access domain component: U2000version_server_nmsaccess_solaris_SPARC.tarIt is required only if the U2000 needs to manage Huawei access equipment. Huawei access equipmentincludes:

FTTx equipmentMSAN equipmentDSLAM equipmentBITS equipment

CMC domain component:U2000version_server_nmscmc_solaris_SPARC.tarIt is required only if the U2000 needs to manage Huawei access equipment.StorageTek 2540 disk array manager CAM (optional). Prepare this component if the StorageTek 2540 diskarray is configured: U2000version_server_ospatch_solaris_SPARC.tar

ESN tool ESN tool: U2000version_ESN_solaris_SPARC.tarThe 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 U2000installation path. Therefore, to apply for the U2000 license after the U2000 is installed, use the ESN tool in this path directly.


1.6.4.9 How to Rectify the Application GUI Startup Failure Caused by UserSwitchingQuestion

After a user logs in to the graphical desktop system as user root and runs the su - ossuser command to switch to user ossuser, applications such as the NMSmaintenance suite client, U2000 client, and U2000 System Monitor client fail to start. How do I rectify this fault?

Answer

Use either of the following methods to rectify the fault.Log out of the graphical desktop system and then log in as user ossuser. Then, start an application in the desktop system.


1.6.4.10 How to View the U2000 and Sybase Database Installation PathsQuestion

How do I view the U2000 and Sybase database installation paths?

Answer

Generally, the U2000 installation path is /opt/oss and the Sybase database installation path is /opt/sybase.To view the installation paths, perform the following steps:




2. Check the ICMR_conf.xml configuration file to confirm the installation paths.Run the following commands to check the ICMR_conf.xml configuration file:# cd /etc/ICMR# more ICMR_conf.xml

A message similar to the following will be displayed:<CONFIGITEMS> <SYBASEUSERNAME>dbuser</SYBASEUSERNAME> <DBDEVICEPATH>/opt/sybase/data</DBDEVICEPATH> <IFCONFIGSYSNET>no</IFCONFIGSYSNET> <INSTALLTYPE>1</INSTALLTYPE> <SYBASEDBSERVERNAME>DBSVR</SYBASEDBSERVERNAME> <LANG>C</LANG> <DEBUGLEVEL>9</DEBUGLEVEL> <SYBASEBACKUPSERVERPORT>4200</SYBASEBACKUPSERVERPORT> <DATABASEINSTALLPATH>/opt/sybase</DATABASEINSTALLPATH> <SYBASEBACKUPSERVERNAME>DBSVR_back</SYBASEBACKUPSERVERNAME> <REUSEDB>no</REUSEDB> <NMSINSTALLPATH>/opt/oss</NMSINSTALLPATH> <FINISHTASKLIST>tasks::installtype_request,tasks::instSybase_request,tasks::instNMS_request,tasks::single_network_request,tasks::modify_sys_paras,tasks::enable_multipath,tasks::mirrorDisk,tasks::mount_array_disks,tasks::install_sybase,tasks::build_server</FINISHTASKLIST> <NETCONFIGFILE>/etc/ICMR/netCfg/OS/os_net_config.cfg</NETCONFIGFILE> <SYBASEGROUPNAME>dbgroup</SYBASEGROUPNAME> <SYBASEDBSERVERPORT>4100</SYBASEDBSERVERPORT>

Confirm the installation paths according to the preceding message:

The Sybase database installation path is /opt/sybase if <DATABASEINSTALLPATH>/opt/sybase</DATABASEINSTALLPATH> isdisplayed.

The U2000 installation path is /opt/oss if <NMSINSTALLPATH>/opt/oss</NMSINSTALLPATH> is displayed.


1.6.4.11 How to View Network Configurations for the Primary Site orSecondary Site Installed with a HA System (Solaris)Question

How do I view network configurations for the primary site or secondary site installed with a high availability (HA) system?

Answer

NOTE:The following uses viewing configurations for the primary site as an example. Viewing configurations for the secondary site is similar to that for the primary site.

1. Log in to the OS of the primary site as user root.

2. View the vcs_net_config.cfg file. Saving this file to a local disk is recommended.Run the following commands to view the vcs_net_config.cfg file:# cd /etc/ICMR/netCfg/VCS/# more vcs_net_config.cfg

A message similar to the following will be displayed:...

#The following are meanings of configuration item ClearFlag=yesSystemIP=10.78.218.52SystemHostname=primarySystemNetmask=255.255.255.0SystemNic=bge0SystemRouter=10.78.218.1

...HBCFG=noHBIP=10.78.218.52HBHostname=primaryHBNetmask=255.255.255.0...# To use another NIC to back up PHBNic, configure the following parameters. HBIsIPMP=no HBStandbyNic=HBStandbyIP=HBStandbyNetmask=255.255.255.0HBStandbyHostname=HBSlave

#VVR network configure, support the IPMPVVRCFG=no



VVRIP=VVRHostname=VVRServiceVVRNetmask=255.255.255.0

VVRMasterNic=VVRMasterIP=VVRMasterHostname=VVRMasterVVRMasterNetmask=255.255.255.0

# To use another NIC to back up PHBNic, configure the following parameters. VVRIsIPMP= VVRStandbyNic=VVRStandbyIP=VVRStandbyHostname=VVRSlaveVVRStandbyNetmask=255.255.255.0

#APP network configure, support the IPMPAPPCfg=yes

APPIP=10.78.218.52APPHostname=primaryAPPNetmask=255.255.255.0APPMasterNic=bge0

APPMasterIP=APPMasterHostname=APPMasterAPPMasterNetmask=255.255.255.0 # To use anther NIC to back up the HBNic, configure the following parameters. APPIsIPMP=no APPStandbyNic= APPStandbyIP= APPStandbyNetmask=255.255.255.0 APPStandbyHostname=APPSlave

The preceding information shows the system IP address, the host name, the subnet mask, the default route, and the relationships between the systemIP address and the heartbeat network, replication network, and NMS application network. Details are as follows:

SystemIP=10.78.218.52: The system IP address is 10.78.218.52.

SystemHostname=primary: The system host name is primary.

HBCFG=no: The system IP address is used as the heartbeat IP address (there is no need to set a heartbeat IP address).

HBIsIPMP=no: IPMP is not configured for the heartbeat IP address.

VVRCFG=no: The heartbeat IP address is used as the replication IP address (there is no need to set a replication IP address).

APPCfg=yes: The application IP address needs to be set.

3. Run the following command to view and record routing information:# netstat -rn

A message similar to the following will be displayed:Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ---------- --------- default 10.78.218.1 UG 1 129077 10.78.218.0 10.78.218.52 U 1 1776 bge0 224.0.0.0 10.78.218.52 U 1 0 bge0 127.0.0.1 127.0.0.1 UH 12 1243318 lo0


1.6.4.12 How to Check Downloaded Software Packages by UsingHashMyFiles SoftwareQuestion

How do I check downloaded software packages by using HashMyFiles software?

Answer

1. Download the iManager U2000 version MD5 CODE(English) file from http://support.huawei.com. The iManager U2000 version MD5CODE(English) file contains MD5 code information after all software and document packages are decompressed.

NOTE:Take the following method to obtain the iManager U2000 version MD5 CODE(English) file. Only Huawei engineers can download the file. If the customer requires using thefile, please contact Huawei engineers for help.

a. Access http://support.huawei.com.b. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManager U2000 > iManager U2000 > desired U2000 version.c. Download the file in the Release Document column.

2. Optional: If the U2000 is installed on Huawei RH series rack server, download the Tecal ServiceCD V100R001C00SPC700.part1.rar.sha256 andTecal ServiceCD V100R001C00SPC700.part2.rar.sha256 files from the Support website. The files contain informationa bout the sha256 codes ofthe ServiceCD software compression package.



NOTE:The sha256 code file of the ServiceCD software compression package can be obtained using the following method:

a. Log in to http://enterprise.huawei.com.b. Choose SUPPORT > Software Downloads > Cloud Computing & Data Centers > Software > IT > Server > APP Server > FusionServer Tools >

V100R001C00SPC300.c. Download the Tecal ServiceCD V100R001C00SPC700.part1.rar.sha256 and Tecal ServiceCD V100R001C00SPC700.part2.rar.sha256 files.

3. Navigate to http://www.nirsoft.net and download the HashMyFiles. For more information about software operation, see the software Help or go tothe official website of the software for technical support.

4. Run the HashMyFiles.

5. Drag the compression files downloaded from the local PC to the HashMyFiles tool. Compare the password information contained in the compressionpackage automatically generated and downloaded by the tool and the verification information in the password file downloaded from the Supportwebsite.

NOTE:For the Tecal ServiceCD V100R001C00SPC700.part1.rar and Tecal ServiceCD V100R001C00SPC700.part2.rar software packages, the sha256 codes in theTecal ServiceCD V100R001C00SPC700.part1.rar.sha256 and Tecal ServiceCD V100R001C00SPC700.part2.rar.sha256 files need to be compared. For othersoftware packages, the MD5 code informoation in the iManager U2000 version MD5 CODE(English) file needs to be compared.You can use the following method to obtain the MD5 code information in the compression packages:

a. Choose Files > Add Folder from the main menu to access the Select Folder dialog box.b. Select the folder in which the compression packages are stored and click OK.c. After the MD5 code information is loaded, the tool automatically generates the password information of the comparession package downloaded from the

local PC. Choose View > HTML Report All Items to export the password information and compare the exported information with the verificationinformation downloaded from the Support website.

If they are the same, the downloaded file is correct.

If they are different, re-download the software package.


1.6.4.13 How to Set the Communication Mode of the Server in a HighAvailability System (Solaris, SUSE Linux)Question

The server in a high availability system (Solaris, SUSE Linux) has two communication modes, namely, common and Security Socket Layer (SSL). How to setthe common or SSL mode?

Answer

1. Log in to the OS on the servers of the primary and secondary sites as the ossuser user and run the following commands to query the communicationmode in use:$ ssl_adm -cmd query

2. Stop U2000 processes.

a. Access the OS of the server on the Active Site as the ossuser user.

b. To start the VCS client, run the following command:$ hagui&

c. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.




d. Enter the IP address for the Heartbeat network service on the primary site. Then, click OK.

e. Enter the user name and password for VCS login.


f. Select the AppService > Application resource from the navigation tree, click the Status tab, and then view the status of the U2000processes.

If the value of State is Offline on all systems, the U2000 processes are stopped.

If the value of State is Online on hostname, the U2000 processes are started. Do as follows to stop U2000 processes: chooseAppService from the navigation tree. Click the Resources tab. Right-click NMSServer and choose Offline > Host name fromthe shortcut menu.Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes have been stopped.

3. Run the following commands on the servers of the primary and secondary sites to set the communication mode of the server:$ ssl_adm -cmd setmode mode parameter

NOTE:

The available options for mode parameter are common, ssl, and both.

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 usedto download the U2000 client in CAU mode.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 downloadthe U2000 client in CAU mode. The security mode is recommended to ensure security for communication between the U2000 server and client.both: indicates that the U2000 server and client can communicate with each other in either common or SSL mode.

If the following information is displayed, the communication mode of the server has been set successfully.Operation succeeded. Please restart all services for the settings to take effect.

NOTE:Ignore information that is displayed before this information because the operation result is not be impacted.

4. In the Cluster Explorer window, right-click the AppService resource group in the navigation tree and choose Online > hostname from the shortcutmenu to start the U2000 server process.


Normally, on the Status tab page, Online is displayed for State in the Group Status on Member Systems area on the Active Site, and Online onprimary is displayed for Status in the Resource Status area.

NOTE:In actual configuration, use the actual host name.If a fault has occurred during start of the AppService process, right-click AppService and choose clear fault from the shortcut menu to clear the fault. Then, chooseOnline > host_name to start the AppService process.

5. In the dialog box that is displayed, click Yes.


1.6.4.14 How to Confirm the Encoding Format of the U2000 License FileQuestion

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.

If the Solaris OS is used, perform the following operations to confirm the encoding format for the U2000 license file:


2. Run the vi command to open the U2000 license file. For example, assume that the U2000 license file name is license.dat.

3. # vi license.dat



Normally, the U2000 license file is in UNIX format and information similar to the following is displayed:Huawei Technologies Co., Ltd.All rights reserved.

LicenseSerialNo=LIC2011083100E710Creator=Huawei Technologies Co., Ltd.CreatedTime=2011-08-31 15:03:05

Country=China

In some special cases (for example, the U2000 license file has an error during file transfer), the encoding format of the U2000license file is changed to DOS.Huawei Technologies Co., Ltd.^MAll rights reserved.^M^MLicenseSerialNo=LIC2011083100E710^MCreator=Huawei Technologies Co., Ltd.^MCreatedTime=2011-08-31 15:03:05^M^MCountry=China^M

Run the dos2unix command to change the encoding format of the U2000 license file from DOS to UNIX.# dos2unix license.dat license.dat

NOTE:The U2000 license file is properly displayed after the format conversion.


1.6.4.15 How to Solve the Instance Inconsistency Problem DuringConnection Between the Primary and Secondary Sites in a Solaris HighAvailability SystemQuestion

Before connecting the primary and secondary sites, you must ensure that the deployed instances on the primary and secondary sites are the same. If instanceshave been deployed on one server, the system may display an instance inconsistency message. As a result, the connection between the primary and secondarysites fails. How do I solve this problem?

Answer

1. Log in to the server on which instances have been added and back up U2000 data to the local server. For details, see chapter Backing Up U2000Data to a Local Server in the U2000 Administrator Guide.

2. Log in to another server and restore backup data on the server, ensuring that the data on the primary server is consistent with data on the secondaryserver. For details, see chapter Restoring U2000 High Availability System (Solaris) Data from a Remote Server in the U2000 Administrator Guide.

3. After data restoration is complete, reconnect the primary and secondary sites.


1.6.4.16 How to Change the OS User PasswordQuestion

How to change the OS user password?

Answer

Method 1:

1. Log in to the OS.

NOTE:The login user is the user whose password needs to be changed.

2. Open the command terminal, run the following command to set the OS user password:passwd

3. Enter a new password as prompted, for example, Changeme_123.To ensure the security of the U2000, passwords must be complex enough. For example, a password must contain eight or more charactersof 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 stringcBackspaceChangeme_123, the password is cBackspaceChangeme_123, but not Changeme_123.

4. Enter the new password again as prompted. Press Enter to make the change take effect.

NOTICE:After the new password takes effect, do not close the CLI.Open another CLI and log in using the new password to verify the new password. If the new password is correct, close all the CLIs. If thenew password is incorrect, repeat the preceding steps to change the password again.

Method 2: (used when the ossuser or dbuser user fails to log in to the OS because the user password is forgotten or the user password expires)


2. Open the command terminal, run the following command to set the OS user password:# passwd OS user

For example, passwd ossuser.

3. Enter a new password as prompted, for example, Changeme_123.To ensure the security of the U2000, passwords must be complex enough. For example, a password must contain eight or more charactersof 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 stringcBackspaceChangeme_123, the password is cBackspaceChangeme_123, but not Changeme_123.

4. Enter the new password again as prompted. Press Enter to make the change take effect.

NOTICE:After the new password takes effect, do not close the CLI.Open another CLI and log in using the new password to verify the new password. If the new password is correct, close all the CLIs. If thenew password is incorrect, repeat the preceding steps to change the password again.


1.6.4.17 How to Restore the OSSENGR and OSSICMR Directories Which AreMisoperated (Solaris/SUSE Linux)Question

After the OSSENGR and OSSICMR directories are mistakenly deleted, the MSuite cannot be used and the database fails to be backed up. How do I restorethe OSSENGR and OSSICMR directories?

Answer

1. Log in to the OS of the server as the ossuser user.

NOTE:If security hardening is enabled, disable it before restoring the OSSENGR and OSSICMR directories that are mistakenly deleted. For details about how to enable or disablesecurity hardening, see the security hardening manuals of all solutions.

2. Ensure that the U2000 is not running.To check the running status of U2000 processes, run the following command:$ daem_ps



If the U2000 is still running, run the following commands to stop it:$ cd /opt/oss/server/platform/bin$ ./stopnms.sh

NOTE:In the HA system, if this command is executed to stop the U2000, a red cross is displayed on the NMSServer icon in the VCS window. In this situation, right the icon andchoose clear fault from the shortcut menu to clear the fault.




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

Information similar to the following is displayed:ossuser 6552 1065 0 16:27:58 ? 0:00 iiimd -nodaroot 10815 10804 0 16:27:58 pts/2 0:00 grep ossuserossuser 3930 1065 0 16:26:58 ? 0:00 iiimd -nodaossuser 16123 1065 0 16:11:18 ? 0:00 iiimd -noda

b. Run the following command to stop all the processes used by the ossuser user:# kill -9 process ID

NOTE:In the preceding command, process ID maps the second and third columns in the displayed information.

For example, to stop process 6552 used by the ossuser user, run the following command:

# kill -9 6552After the kill is run several times and information similar to the following is displayed, all the processes used by the ossuser are stopped:

root 10815 10804 0 16:27:58 pts/2 0:00 grep ossuser

5. Configure the VNC service as the root user.

a. Run the following command to check the svc:/milestone/network:defaultstatus:# svcs |grep svc:/milestone/network:default

Information similar to the following is displayed:online 20:17:02 svc:/milestone/network:default

If the command output contains online, you do not need to run the following commands. If the command output contains maintenance oroffline, run the following commands to change the status of svc:/milestone/network:default to online.# svcadm clear svc:/milestone/network:default# svcadm enable svc:/milestone/network:default# svcs |grep svc:/milestone/network:default

If the status of svc:/milestone/network:default is online, perform the following operations to configure the VNC service for the rootuser:

b. Optional: Run the following command to set the password for user root to log in to the VNC. If the VNC login password for user rootalready exists, skip this step.# vncpasswd


An example password is Admin123. A password must consist of 6 to 8 characters. All characters entered using the keyboard, except theEnter key, will be considered as password components. Excessive characters will be automatically discarded. Passwords must be complexenough to ensure the security of the U2000. For example, a password must contain six or more characters of two types. The allowedcharacters are digits, letters, and special characters. Remember to use the vncpasswd command to change passwords regularly and keepthe passwords well.

i. Enter the password and press Enter.Verify:

ii. Enter the password again 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.Remember the password that will be used for VNC login as user root.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.# cd /opt/install/engineering/OSSICMR/solaris/tools/VNC/# sh stop_vnc_root.sh# 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 rootuser.

NOTE:If a message is displayed asking you to set the password, run the vncpasswd password as the root user to set the password.

d. Perform the following operations to create an SSH tunnel so that the communication between the server and VNC client is more secure. Ifthe PuTTY is stored in the D:\PuTTY path, the IP address of server 1 is 10.9.1.1, and the IP address of server 2 is 10.9.1.2, the VNCservice can be implemented as the root user for the two servers. You must ensure that the VNC service corresponding to the root user hasbeen started for both of the two servers.

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.1D:\PuTTY>putty -L 5904:localhost:5902 10.9.1.2




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.


If the security hardening policy is enabled on the system, enter the user name and password of the ossuser user in the PuTTY window tocomplete 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.

f. Click OK. In the dialog box that is displayed, enter a password and click OK to access the Solaris OS.

NOTICE:

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.If the VNC needs to be used again, refer to this document to configure the VNC.If you need to use the VNC again after logging in to the server through the VNC and logging out of the root user in the GUI,refer to this document to configure the VNC.

6. Right-click in the blank area of the desktop and choose Open Terminal from the shortcut menu to open the CLI.

7. Run the following commands to switch to the directory where the restoreENGR.sh file is stored and run the restoreENGR.sh file to start copyingsoftware:# cd /opt/oss/server/tools/restoreENGR/# ./restoreENGR.sh

Information similar to the following is displayed:Backup the /opt/OSSENGR.Copying the JRE to /opt/OSSJRE...FinishedCopying the installation files to /opt/OSSENGR...Finished

NOTICE:

If the following command output is displayed, enter 2 and press Enter.If you want to install an HA system (Veritas hot standby), enter "1".If you do not want to install an HA system (Veritas hot standby), enter "2".

8. Perform the following operations to add environment variables to the engr_profile.sh file:

a. Use the cd command to navigate to the /opt/OSSENGR/engineering/conf directory.# cd /opt/OSSENGR/engineering/conf

b. Use the vi command to open the engr_profile.sh file.# vi engr_profile.sh

c. In command mode, enter G to move the cursor to the end of the file and enter o to move the cursor to the next line. Copy the followingcontents to the end of the engr_profile.sh file.



OSS_ROOT=/opt/oss;export OSS_ROOT

NOTE:The /opt/oss is the U2000 installation path. Change it as required.

After the copy is complete, information similar to the following is displayed:... ... . $OSSENGRROOT/engineering/tool/sybaseclienttool/SYBASE.sh fifiOSS_ROOT=/opt/oss;export OSS_ROOT

d. In command mode, run the :wq! command to save the file and exit.

e. Run the following command to assign executable rights to the engr_profile.sh file:# chmod 750 engr_profile.sh

9. Optional: If the U2000 patch has been installed, perform the following operations:# cd /opt/nmspatch/patch# ./pre_patch.sh

Information similar to the following is displayed:Installing the MSuite patch. Please wait...The MSuite patch installed successfully.Copying the patch package to the /opt/OSSENGR directory. Please wait...The patch package copied successfully.

NOTE:The /opt/nmspatch directory stores the latest decompressed U2000 patch package. Use the on-site directory as this one is an example.

10. Run the following operations to assign rights to the /opt/oss, /opt/sybase and /opt/backup/ftpboot directories:

For the Linux OS, run the following commands:# cd /opt/oss/server/common/customize/share/permission# ./post_nw_permission_linux.sh "/opt/oss" "/opt/sybase" "/opt/backup/ftpboot" "U2000"

For the Solaris OS, run the following commands:# cd /opt/oss/server/common/customize/share/permission# ./post_nw_permission_solaris.sh "/opt/oss" "/opt/sybase" "/opt/backup/ftpboot" "U2000"

NOTE:The /opt/oss is the U2000 installation path. The /opt/sybase is the database installation path. Change it as required.

11. Ensure that the MSuite server has been started.Run the following command as the root user to check whether the MSuite servers are started:






12. Log in to the MSuite client, and choose System > Synchronize NMS information. Otherwise, the process page will be empty after you log in to theMSutie client.

NOTE:To log in to a newly installed U2000, use the initial password Changeme_123 . To ensure system security, change the password in time, update it periodically, andkeep it well.If a U2000 patch has been installed, log in to the U2000 using the password that is used during patch installation.

13. After the OSS information is synchronized, do as follows to restart the MSuite server.

a. Run the following commands as user root to end the process of the MSuite server.# cd /opt/OSSENGR/engineering# ./stopserver.sh

b. Run the following command as user root to verify that the MSuite server is running:# cd /opt/OSSENGR/engineering# ./startserver.sh




1.6.4.18 How to Use the FileZilla to Transfer Files by SFTPQuestion

How do I use the FileZilla to transfer files by SFTP?

Answer

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 officialwebsite of the software for technical support.

2. Create a site.

a. Choose File > Site Manager from the main menu to access the Site Manager window.

b. Click New site.

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

Figure 1 Create a site

d. 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 defaultAutodetect is used. For example, a software installation package or license file.

e. Click Connect. And the Enter password dialog box is displayed, as shown in Figure 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 thecache and click OK.

Figure 2 Enter password

f. 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 3, SFTP connection is successful.

Figure 3 Successful SFTP connection



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 containspaces, brackets, or Chinese characters. Need to refresh before uploading package under the server is file directory.

a. 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 inFilename under Local site.

b. 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 bedisplayed in Filename under Remote site.

c. Click a file to be uploaded and hold down to drag the file to the folder on the Remote site node.

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

Figure 4 Uploading files

4. After the file is successfully uploaded, a success message is displayed, as shown in Figure 5.

Figure 5 Successful file uploading


1.6.4.19 How to Transfer Files by Means of FTPQuestion

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.

Generally, license files are transferred in ASCII mode.

Before the U2000 is installed, you can upload the U2000 license file as the root user.After the U2000 is installed, you must upload the U2000 license file as the ossuser user. Otherwise, the U2000 license file will be invalid.

Binary files, such as the U2000 installation program and database interfaces file, are transferred in binary mode.

Answer

1. Run the following command to connect to the server by means of FTP:ftp server IP addressEnter the user name and password of the server.

2. Set the FTP transfer mode.



To use the ASCII mode, run the ascii command.

To use the binary mode, run the bin command.

3. Go to the path to files to be transferred.lcd path of files to be transferred

4. Go to the path where the files are to be transferred.cd path to which the files are to be transferred

5. Optional: Run the hash command to view the file uploading progress.hash

6. Run the following put command to transfer files:put names of files to be transferred

7. After the files are transferred, run the quit command to break the FTP connection.


1.6.4.20 How to Check and Change an OS User IDQuestion

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


2. Run the following commands to query the database user ID and U2000 user ID in the system:

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

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

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 aU2000 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 testuseruser 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:# 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 beingused.

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


1.6.4.21 How to Deal with an Automatically Configured Temporary IPAddressQuestion

After the U2000 is installed on the Netra T4-1/Oracle T4-1/Oracle T4-2 server, a user uses the ifconfig -a command to find that the system containsinformation about usbecm0, an extra NIC, and a temporary IP address is automatically configured for the NIC. How do I deal with the temporary IP address?

Answer

1. Log in to the system controller IP address

2. At the -> prompt, run the following commands to configure hardware:



3. Enter cd /SP/network/interconnect.The following message will be displayed:/SP/network/interconnect

4. Enter set hostmanaged=false.The following message will be displayed:Set 'hostmanaged' to 'false'

5. Enter set state=disabled.The following message will be displayed:Set 'state' to 'disabled'

6. Enter set commitpending=true.The following message will be displayed:Set 'commitpending' to 'true'

7. Enter exit to complete configuration.

8. Log in to the OS as the root user. Run the following command to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6


1.6.4.22 How to Burn the ISO File to DVDQuestion

How do I burn the ISO file to DVD?

Prerequisites

The desired ISO file is obtained.

The DVD recorder has been installed on a Windows PC.

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.

An empty DVD is available.

Answer

1. Check whether the contents of the obtained ISO file are the same as those of the source ISO file.

a. Download the iManager U2000 version MD5 CODE(English) file from the Support website. The downloaded file contains the MD5code information about all software compression packages.

NOTE:Take the following method to obtain the iManager U2000 version MD5 CODE(English) file. Only Huawei engineers can download the file. If the customerrequires using the file, please contact Huawei engineers for help.

a. Access http://support.huawei.com.b. Choose Software Center > Version Software > Network OSS&Service > iManager U2000 > iManager U2000 > iManager U2000 > desired U2000

version.c. Download the file in the Release Document column.

b. Log in to http://www.nirsoft.net to download the HashMyFiles software.

NOTE:For more information about the software, see the software Help or log in to the official website of the software for technical support.

c. After the HashMyFiles software is downloaded, run the software.

d. Drag the ISO file to be burnt to DVD to the HashMyFiles tool window. The HashMyFiles tool automatically generates the MD5 code forthe ISO file and compares the generated MD5 code with that of the ISO file in the iManager U2000 version MD5 CODE(English) file.

NOTE:

Perform the following operations to obtain the MD5 code of the ISO file:

a. Choose File > Add Files from the main menu to access the Select one or more filenames to add dialog box.b. Select the ISO file to be burnt to DVD and click Open.c. After the ISO file is loaded, the HashMyFiles tool automatically generates the MD5 code of the ISO file. Chooses View > HTML Report All Items to

export the MD5 code and compare it with that of the ISO file in the iManager U2000 version MD5 CODE(English) file.

If the two MD5 codes are the same, the contents of the obtained ISO file are the same as those in the source ISO.



If the two MD5 codes are different, the obtained ISO file is damaged and you must re-download the ISO file.

2. Execute the Nero software.

3. Click the Image, Project, Copy button.The Copy Entire CD, Copy Entire DVD, and Disc Image or Saved Project dialog box is displayed.

4. Click Disc Image or Saved Project.The Open dialog box is displayed.

5. Select the ISO file to be burnt to DVD and click Open.The Final Burn Settings dialog box is displayed.

6. Insert the empty DVD to the DVD-ROM.

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.

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 isdisplayed, and a message about the printing result is displayed.

9. Click OK.

10. Click Next.

11. Click to close the program.


1.6.4.23 How to Address the Failure to Download JNLP Files After theDownload File Option Is Clicked on the Address Bar of the Internet ExplorerBrowserQuestion

How to address the failure to download JNLP files after the Download File option is clicked on the address bar of the Internet Explorer browser?

Answer

1. Open Internet Explorer.

2. Go to Tools > Internet Options.

3. In the Internet Options dialog box, click the Security tab. Under Internet option, choose Custom level.

4. In the Security Settings - Internet Zone dialog box, scroll down to the Downloads section.



5. Under Automatic prompting for file downloads option, select Enable.

6. Click OK.

7. Click Yes on the warning pop-up.

8. In the Internet Options dialog box, click OK.

9. Restart the IE Browser.


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

How to Address an OS Installation Failure Caused by Incorrect Hard Disk Format

How to Rectify the OS Installation Failure that Occurs Because a Hard Disk Is Not Labeled

How to Solve the Problem Where the Amount of Remaining Data Keeps 99% During Data Synchronization in a High Availability System

How do I solve the problem where a failure message is displayed during the installation or the installation is abnormally interrupted

How to Handle Messages Indicating That the Port Is Occupied During Installation or Uninstall

How to Rectify the Failure to Connect to the Sybase Database During U2000 Installation

Failure to Log In to the U2000 Server from a U2000 Client

How to Resolve the Problem that the License Does Not Take Effect

How to Solve Common Problems About Using the Network Mode to Installing a U2000 Client

How to Rectify the Failure to Open the CAU Download Web Page Because the Port Is Used

How to Address the Problem Where the Sapce of the OS Patch Directory tmp Is Insufficient

Parent topic: FAQs

1.6.5.1 How to Address an OS Installation Failure Caused by Incorrect HardDisk FormatQuestion

How do I address the problem where a message similar to the following is displayed when the quick installation DVD is used to install the OS?

igb0 will be used as the system NIC



All the selections are confirmed.Formatting all the local disks......Failed!Begin script 600g failed with return value "1".Aborting install.

Information similar to the following is displayed:Begin script install_begin execution completed .--Warning---------------------------------

One or more disks are found , but one of the following problems exists:>Hardware failure>Unformatted disk.

Answer

Perform the following operations to configure the format of all hard disks:









-> cd /HOST-> ls


































b. Enter y.








f. Enter y.





OK

2. Enter the singl user mode.

If a system has been installed, run the boot -s command.

If a system has not been installed, insert the system disk and run the boot cdrom -s command.

3. Run the following command to view disk information:# format -e

Information similar to the following is displayed:Searching for disks...done


4. Enter 0 to manage the disk with the serial number of 0.

Information similar to the following is displayed:selecting c1t0d0[disk formatted]Warning: Current Disk has mounted partitions./dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M)./dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M)./dev/dsk/c1t0d0s5 is currently mounted on /opt/backup. Please see umount(1M)./dev/dsk/c1t0d0s6 is currently mounted on /var. Please see umount(1M)./dev/dsk/c1t0d0s7 is currently mounted on /export/home. Please see umount(1M).

FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit



a. Enter label to configure the format for the disk with the serial number of 0.format > label

Information similar to the following is displayed:[0] SMI Label[1] EFI LabelSpecify Label type[0]:

b. Enter 0 to select the SMI Label format. Then press Enter.

Information similar to the following is displayed:Auto configuration via format.dat[no]?

c. Enter y and press Enter.

d. Enter p to check whether the hard disk format is correct.

Information similar to the following is displayed:Current partition table (original):Total disk cylinders available: 14087 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks 0 root wm 1649 - 3709 20.00GB (2061/0/0) 41945472 1 swap wu 0 - 1648 16.00GB (1649/0/0) 33560448 2 backup wm 0 - 14086 136.71GB (14087/0/0) 286698624 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 13913 - 13919 69.56MB (7/0/0) 142464 5 unassigned wm 3710 - 11644 77.01GB (7935/0/0) 161493120 6 var wm 11645 - 13705 20.00GB (2061/0/0) 41945472 7 home wm 13706 - 13912 2.01GB (207/0/0) 4212864

If the 2 backup directory is displayed, the hard disk format is configured successfully.

5. Repeatedly perform Steps 3 and 4 to configure the format for all the hard disks.

Parent topic: Install the U2000 Software Exception Processing

1.6.5.2 How to Rectify the OS Installation Failure that Occurs Because aHard Disk Is Not LabeledQuestion

If the following information is displayed during OS installation, how do I deal with it?

Checking rules.ok file...c0t5000CCA025A50D50d0 doesn't have a VTOC labelc0t5000CCA025AB923Cd0 doesn't have a VTOC labelc0t5000CCA025761E50d0 doesn't have a VTOC labelc0t5000CCA0259768B0d0 doesn't have a VTOC label

Answer


2. Run the following command to view the disk information:# format

Information similar to the following is displayed:Searching for disks...done


3. Enter 0 to manage disk 0.

Information similar to the following is displayed:selecting c1t0d0[disk formatted]Warning: Current Disk has mounted partitions./dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M)./dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M)./dev/dsk/c1t0d0s5 is currently mounted on /opt/backup. Please see umount(1M)./dev/dsk/c1t0d0s6 is currently mounted on /var. Please see umount(1M)./dev/dsk/c1t0d0s7 is currently mounted on /export/home. Please see umount(1M).



FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit

NOTE:If multiple disks are installed, repeat the format command and enter desired numbers to label each disk.

4. Enter label to label disk 0.format > label

Information similar to the following is displayed:Ready to label disk, continue?

5. Enter y.


1.6.5.3 How to Solve the Problem Where the Amount of Remaining DataKeeps 99% During Data Synchronization in a High Availability SystemQuestion

During data synchronization in a high availability system, the amount of data to be synchronized keeps high for several hours. The use of the MSuite showsthat the amount of remaining data keeps 99%. How do I solve this problem?

Answer

1. Log in to the secondary site as the root user.

2. Run the following command to query the transmission protocol for the secondary site:# vxprint -VPl |grep protocol

Information similar to the following is displayed:protocol: UDP/IP

3. Log in to the primary site as the root user.

4. Run the following command to query the transmission protocol for the primary site:# vxprint -VPl |grep protocol

Information similar to the following is displayedprotocol: UDP/IP

5. On the primary site, change the transmission protocol and ensure that the primary and secondary sites use the same transmission protocol.

If the transmission protocol of the primary site is UDP/IP but the transmission protocol of the secondary site is TCP/IP, run thefollowing command to change the transmission protocol of the primary site to TCP/IP:# vradmin -g datadg set datarvg protocol=TCP

If the transmission protocol of the primary site is TCP/IP but the transmission protocol of the secondary site is UDP/IP, run thefollowing command to change the transmission protocol of the primary site to UDP/IP:# vradmin -g datadg set datarvg protocol=UDP


1.6.5.4 How do I solve the problem where a failure message is displayedduring the installation or the installation is abnormally interruptedSymptom

How do I solve the problem where a failure message is displayed during the installation or the installation is abnormally interrupted?



Procedure


2. Run the following commands to use the environment clean-up tool to clear the installation environment:# cd /opt/OSSENGR/engineering/tool/OSSEnvCleaner# ./OSSEnvCleaner.sh

A message similar to the following will be displayed:......Clean OSS directory:1.The directory has been deleted,skip this step2.The directory has never been deleted,execute cleaning directoryPlease selected:

3. Enter a value based on whether the U2000 directory /opt/oss is deleted. For example, enter 2.

4. Enter the U2000 directory /opt/oss as prompted.

5. Enter yes to confirm the database deletion operation.

6. Enter the Sybase database path as prompted, or press Enter to automatically enter /opt/sybase.A message similar to the following will be displayed:Input administrator user name: saInput 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

7. Enter the user name and password of the database administrator and the server name. Then press Enter.

8. After the cleanup operation is performed as prompted, run the following commands to reinstall the U2000, see Starting the U2000 InstallationProgram.


1.6.5.5 How to Handle Messages Indicating That the Port Is OccupiedDuring Installation or UninstallQuestion

How do I handle messages indicating that the port is occupied during use of the NMS Maintenance Suite, installation, or uninstall?

NOTE:

In the Solaris OS, the message is as follows:The communication port (12212,12213,12214,12215) of the installation framework is used.Run the "/usr/bin/netstat -an -P tcp" command to query the usage status of the port, or try later.

Answer

Wait about one minute and try again after the port is released automatically.

Run the following command to view process IDs:# cd /opt/OSSENGR/engineering/tool/# ./FindProcessOnPort.shSearching for process running on port 12212 ......-------------------------------------------------------------------------Port: 12212 is being used by PID: root 19983 1 6 308119 296292 29 10:15 ? Sl 2:37 /opt/OSSJRE/jre_sol/bin/java -server -Dlanguage=en -Xverify:none -Xms64m -Xmx512m -XX:MaxPermSize=256m -XX:MinHeapFreeRatio=10 -X...Locate all processes that contain port (12212,12213,12214,12215) and end these processes by running the kill command. The following is a samplekill command:# kill -9 19983


1.6.5.6 How to Rectify the Failure to Connect to the Sybase Database DuringU2000 InstallationQuestion

How to rectify the failure to connect to the Sybase database during U2000 installation?

Answer

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. Torectify this fault, modify the IP address recorded in the interfaces file.



2. To modify the interfaces file, run the following command:# vi /opt/sybase/interfaces

Information similar to the following is displayed:DBSVR master tcp ether 10.9.1.20 4100 query tcp ether 10.9.1.20 4100 master tcp ether 10.9.1.20 4100 query tcp ether 10.9.1.20 4100 master tcp ether 127.0.0.1 4100 query tcp ether 127.0.0.1 4100


Change the IP address (for example, 10.9.1.20) recorded in the interfaces file to the IP address of the U2000 server.


1.6.5.7 Failure to Log In to the U2000 Server from a U2000 ClientSymptom

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:

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 theU2000 server is high because many processes are started.

The network between the client and server does not function properly.

The IP address used for login is incorrect.

The license file is a temporary one or is damaged.

The number of clients allowed in the license is restricted.

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 isused by default.

The version of the client is inconsistent with that of the server.

The communication protocol used by the client is inconsistent with that used by the server.

The user that logs in to the client is locked. This may be caused by too many times of login failures.

The IP address of the computer where the client is installed is not listed in the ACL.

The OS time on the client is set incorrectly and the ILOG JTGO license is expired.

The DCN is faulty.

The server memory is less than 32 GB, which makes the number of server connections reaching the threshold.

The client on the primary site fails to log in to the server after a service switchover.

Procedure

1. If an error message is displayed, locate and rectify the fault as prompted.

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 manyprocesses are started on the server. If many processes are started on the server, the memory usage is high.

a. Ensure that the server has been started properly.You can log in to the U2000 System Monitor to view server information. If the server startup fails, see Failure to Start Certain Processesof the U2000 Server to address the issue.

b. 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 following operations: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.

c. 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). Startthe U2000 in CLI mode.

3. Check whether the login IP address is the one used for the login server.

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 How to Resolve theProblem that the License Does Not Take Effect and log in to the U2000 client.

5. Choose Help > License Management > License Information from the main menu (traditional style); alternatively, double-click SystemManagement 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 U2000license file.

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 upgradethe client. In this case, try to upgrade or reinstall the client.

7. Check whether the communication protocols used by the client and the server are consistent. If the protocols are inconsistent, modify the protocolsso 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 How to Set the Communication Mode of theServer in a High Availability System (Solaris, SUSE Linux).

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

To check the network between the client and server, run the following command on Windows:> ping -t IP_address_of_the_NMS

To check the network between the client and server, run the following command on Solaris:# ping -s IP_address_of_the_NMS

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 removeviruses. 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 theport has been added to the Windows firewall. If not, perform the following operations to add the port to the Windows firewall:

NOTE:Windows 2008 is used as an example to describe the procedures for adding a port to a firewall. The procedures vary according to OSs. For specific procedures, see the Windowshelp.

a. Choose Start > Control Panel.

b. In the Control Panel window, click windows Firewall.

c. In the windows Firewall window, click Advanced Setting.

d. In the Windows Firewall with Advanced Security dialog box, choose Inbound Rules from the left navigation tree and from New Rulethe right navigation tree.

e. In the New Inbound Pule Wizard dialog box, select Port and click Next.

f. In Specific local ports, set Ports and click Next.

g. Select Allow the connection and click Next.

h. Click Next, set Name, and click Finish.

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 cannotaccess the server. For details, see "Setting the Access Control List" in Chapter "Security Management" in the U2000 Administrator Guide. If NAT isused for IP address translation for communication between the client and server, ensure that the translated IP address is permitted in the ACL.

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.

12. Check whether the system time is the current time. If not, modify the system time.

13. A minimum of 32 GB is recommended for the server memory. If the server memory is less than 32 GB, the number of server connections mayexceed the threshold, and the U2000 client fails to connect to the U2000 server. If such a fault occurs, expand the server memory or contact Huaweitechnical support engineers.

14. If a service switchover results in a client login failure, you can temporarily log in to the client on the secondary site and then re-log in to the client onthe primary site after the fault is rectified.

15. If the fault persists, restart the server.


1.6.5.8 How to Resolve the Problem that the License Does Not Take EffectQuestion



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:

The license item is incorrect.

The time setting of the OS is incorrect.

Check and rectify the fault on Solaris or SUSE Linux based on the following items:

1. The date of the OS is the current date.

2. Check whether the ESN is correct.You can obtain the ESN tool according to the U2000 License Usage Guide to check the ESN.

3. A unique license file exists in the /opt/oss/server/etc/conf/license path. If more than one license files exist in the path, you must delete redundant license files manually.

4. The NIC used during license application must be the NIC actually used on the server. If the NICs are different, you must apply for a new license.

5. The license file must be transferred in the ASCII format.

NOTE:You can check the license file by running the vi command. If each line of the license file ends with the ^M symbol, the license file is uploaded in binary mode. Youmust re-upload the license file.

6. The license file must comply with the U2000 version.

7. Check whether an error has occurred during the license file transfer.If an error has occurred, transfer the license file again or download the license file to the /opt/oss/server/etc/conf/license directory. Restartthe U2000 and check whether the license takes effect.


1.6.5.9 How to Solve Common Problems About Using the Network Mode toInstalling a U2000 ClientQuestion

How to solve common problems about using the network mode to install a U2000 client?

Answer

The following table shows the problems that may occur while using the network mode to install a U2000 client and the associated solutions.

Serial Number Problem Solution

1 After the U2000 patch is installed and a U2000 client is installed using thenetwork mode, the U2000 client version is different from the serverversion.

Delete the %OSS_ROOT%\cau\history directory on the server.Execute the %OSS_ROOT%\cau\bin\cau.bat file. Use the CAUmode to install a U2000 client.

2 During installation of a U2000 client in CAU mode, a message is displayedindicating a failure to start the CAU.

Choose Start > Run. In the dialog box that is displayed, enter cd%USERPROFILE%\Application Data\Sun\Java\Deployment\. Inthe CLI, run the del deployment.properties and delete thedeployment.properties.

3 During installation of a U2000 client in CAU mode, a message is displayedindicating that the JRE server settings are incorrect and the installationfails.

Choose Tools > Internet Options > Connections > LAN Settingsfrom the Internet Explorer. Clear the Proxy server check box. Selectthe Automatically detect settings check box. Use the CAU mode toinstall the U2000 client again.

4 The U2000 client fails to enter the CAU installation window, or a messageis displayed indicating a failure to start the application after Install isclicked. The failure information shows that the JAR signature certificate inthe JNLP file is different from the actual signature certificate.

1. Choose Start > Run. Enter the cmd command and pressEnter.

2. Run the rd %userprofile%/ApplicationData\Sun\Java\Deployment\cache command to delete the%userprofile%/ApplicationData\Sun\Java\Deployment\cache folder.

3. Run the rd %allusersprofile%/cache command to deletethe %allusersprofile%/cache folder. If the folder does notexist, skip this step.

4. Run the rd %allusersprofile%/.cau command to delete the%allusersprofile%/.cau folder.

5 The JNLP file fails to be downloaded after download file is selected on

the Internet Explorer browser.

For details about how to address the issue, see How to Address the

Failure to Download JNLP Files After the Download File Option Is



Clicked on the Address Bar of the Internet Explorer Browser.


1.6.5.10 How to Rectify the Failure to Open the CAU Download Web PageBecause the Port Is UsedQuestion

How do I rectify the failure to open the CAU download web page because the port is used?

Answer


2. Run the following commands to view the PID of the process that uses the port:# cd /proc# pfiles * > /tmp/proc.txt# more /tmp/proc.txt

A message similar to the following will be displayed:979: /opt/oss/server/conf/../bin/DmsSyslogCollector

Current rlimit: 4096 file descriptors

13: S_IFREG mode:0644 dev:32,88 ino:52929 uid:0 gid:0 size:892888

O_WRONLY|O_CREAT|O_TRUNC

/opt/oss/server/conf/log/DmsSyslogCollector20080226_133400.log

14: S_IFSOCK mode:0666 dev:323,0 ino:22704 uid:0 gid:0 size:0

O_RDWR

SOCK_DGRAM

SO_SNDBUF(57344),SO_RCVBUF(57344)

sockname: AF_INET 0.0.0.0 port: 80Port 80 is used by the process with the PI of 979.

3. View the process.# ps -ef |grep 979

A message similar to the following will be displayed:root 20161 2440 0 14:56:37 pts/1 0:00 grep 979root 979 25685 0 February 20 ? 8:17 /opt/oss/server/conf/../bin/DmsSyslogCollectorThe process with the PID of 979 is DmsSyslogCollector.

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.


6. Run the following commands to restart the tomcat process.$ /opt/oss/server$ ./svc_profile.sh$ apachectl stop$ apachectl start


1.6.5.11 How to Address the Problem Where the Sapce of the OS PatchDirectory tmp Is InsufficientQuestion

The message The space of '/tmp' is less than 10G is displayed during the installation of the Solaris OS patch, indicating that the space of the tmp directory isinsufficient. How do I expand the capacity of the tmp directory?

Answer

1. When such a message is displayed, run the following command to expand the capacity of the tmp directory:



# mkfile 10g /tmpvol# swap -a /tmpvol

2. Run the following command to switch to the path where the QuickSetup.sh file is stored and execute the file. Then re-install the OS patch.# cd /opt/patches/sun/sun# sh QuickSetup.sh


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

Uninstall PreparationsThis topic describes the preparations for uninstalling the U2000 software.

Uninstalling U2000 SoftwareThis topic describes how to uninstall U2000 software.

Verifying the Uninstall Status of the Server SoftwareThis topic describes how to verify that the U2000 server software is uninstalled.


1.7.1 Uninstall PreparationsThis topic describes the preparations for uninstalling the U2000 software.

Procedure

1. Optional: If the SetSolaris policy is enabled on the live network, choose whether to disable the policy according to network conditions.

If the SetSolaris policy cannot be disabled on the live network, skip this step.

NOTE:If the SetSolaris policy is disabled on the live network, skip this step.

If the SetSolaris policy can be disabled on the live network, run the following command to cancel the SetSolaris policy.

a. Log in to the OS as the ossuser user.

NOTE:After the SetSolaris policy has been enabled, the Telnet service is stopped.You can log in to the OS only by means of SSH. The PuTTY is recommended.

b. Run the following command to cancel the SetSolaris policy.$ su - rootpassword: password_of_root_user# sek -r all

c. Run the following commands to disable security hardening on openssh:# cp /opt/oss/server/common/dc/3rdTool/openssh/openssh-setup/normal_sshd_config /usr/local/etc/sshd_config# chown root:root /usr/local/etc/sshd_config# chmod 664 /usr/local/etc/sshd_config

d. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

2. Log out of all running U2000 clients.

NOTE:You can log in to the U2000 client and choose Administration > NMS Security > User Session Monitor (traditional style) from the main menu to check whether user sessioninformation exists. If not, all users have logged out of the U2000 client. If yes, contact maintenance engineers and shut down the U2000 client.

3. Log in to the OS of the primary site as the ossuser user by using the remote GUI software. Such as VNC.

4. Disconnect the primary site from the secondary site.

a. Make that all servers on the primary and secondary sites must be started on the MSuite server side.

b. On the server on the active site, run the following commands to start the MSuite client:Double-click the shortcut icon of the U2000 NMS Maintenance Suite or run the following commands:$ cd /opt/oss/client/engineering$ ./startclient.sh





Parameter Settings





c. Click Login to access the Network Management System Maintenance Suite window.


d. Choose Deploy > Separate Primary Site from Secondary Site. The Warning dialog box is displayed.

e. Click Yes. Then click Yes in the Warning dialog boxes displayed. The progress bar is displayed indicating the status of separating theprimary and secondary sites. Wait until the dialog box is displayed indicating that the separation is complete.

f. Click OK.

g. Choose System > Log Out from the main menu. The Log Out dialog box is displayed.

h. Click OK.

5. Ensure that the U2000 is not running.To check the running status of U2000 processes, run the following command:$ daem_ps



If the U2000 is still running, see Stopping the U2000 Server Processes to stop it.

6. Ensure that the Network Management System Maintenance Suite is not running.

Run the following command to verify that the Network Management System Maintenance Suite is not running:$ ps -ef | grep javaInformation similar to the following is displayed: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/OSSJRE/jre_sol/bin/java -server -Dequinox.conf=engineering/conf/installE

NOTE:If the displayed information does not contain /opt/OSSJRE/jre_sol/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 - rootpassword: password_of_root_user# cd /opt/OSSENGR/engineering# ./stopserver.sh



NOTE:It takes about 3 minutes to stop the U2000. Perform follow-up operations only after Successful is displayed.

# exit

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

Information similar to the following is displayed:dbuser 4989 1 0 Sep20 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/RUN_DBSVRdbuser 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_0dbuser 5012 1 0 Sep20 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/RUN_DBSVR_backdbuser 5016 5012 0 Sep20 ? 00:00:00 /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install/DBSVR_back.log -N25 -C20 -M/opt/sybase/ASE-15_0/bin/sybmultbuf...

NOTE:The database is running if the displayed information contains /opt/sybase/ASE-15_0/bin/dataserver -sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back.

If the Sybase database is not running, see Starting the Database to start it.

Parent topic: Uninstalling the U2000 Software

1.7.2 Uninstalling U2000 SoftwareThis topic describes how to uninstall U2000 software.

Prerequisites

All servers on the primary and secondary sites must be started on the MSuite server side.

Context

After the U2000 is uninstalled, uninstalling the database and Veritas software is not recommended. If the database and Veritas software is damaged, re-installthe OS.

NOTE:After SetSolaris is enabled, only the SSH service for the ossuser user has the login right. The SSH login mode is recommended for your system security. To use another login mode such asTelnet, you must enable the access right for the Telnet service and the login user. For details, see How to Start/Stop the FTP, SFTP, and Telnet Services and How to Enable and Disable theFTP/Telnet Authority of user root on Solaris OS.

Procedure

1. Re-log in to the GUI of the OS as the root user on the primary and secondary sites.

2. Run the following commands on the server on the primary and secondary sites to stop the MSuite server:# cd /opt/OSSENGR/engineering# ./stopserver.sh

3. Run the following command on the servers at the primary and secondary sites to go to the path where the uninstall.sh script is stored and run thescript:

NOTE:Two modes are available to uninstall the U2000. One is the GUI mode and the other is the CLI mode. The procedure for uninstalling the U2000 in GUI mode is described in thefollowing sections. Installation engineers are recommended to uninstall the U2000 through the CLI if they cannot log in to the GUI of the OS.

Run the ./uninstall.sh -cmd command to uninstall the U2000 in the /opt/OSSENGR path through the CLI.

# cd /opt/OSSENGR# ./uninstall.sh

The Confirm Uninstallation dialog box will be displayed.

4. Click OK. A dialog box showing the progress of the uninstall will be displayed.

NOTE:The duration of the uninstall depends on the quantity of installed components. Wait patiently.

5. After the uninstall is complete, the Uninstallation Complete dialog box is displayed.

6. Click Finish.

Follow-up Procedure

If the U2000 is installed using software packages, run the following command to delete the decompressed software packages:# rm -rf /opt/install/install# rm -rf /opt/install/thirdparty



If the SetSolaris policy is enabled during uninstallation or the ossuser user is being used, log in to the OS as the dbuser user. Run the followingcommand to switch to the root user and then delete the ossuser user and the ossuser directory.Run the following command on the primary and secondary sites:

$ su - rootPassword: root user password# userdel ossuser# rm -rf /export/home/ossuser


1.7.3 Verifying the Uninstall Status of the Server SoftwareThis topic describes how to verify that the U2000 server software is uninstalled.

Procedure


2. Confirm that the installation path is correct during the uninstall.

If the server is not mounted with disk arrays, the NMS installation path/opt/oss will be deleted.

If the server is mounted with disk arrays, the NMS installation path /opt/oss will be empty.

The installation paths /opt/OSSENGR, /opt/OSSICMR and /opt/OSSJRE, are deleted.

3. Confirm the ossuser user that must be deleted during the uninstall.Run the following command to switch to user ossuser:# su - ossuser

If information similar to the following is displayed, the ossuser user does not exist.su: Unknown id: ossuser


1.8 Manual Commissioning TaskSome commissioning tasks need to be manually executed during U2000 system parameter commissioning. This topic describes how to execute a manualcommissioning task.

Configuring a Digital CertificateThe 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.

Setting Hardware Alarm MonitoringThis section describes the settings of monitoring the U2000 server (M4000/M5000) hardware and the S2600 disk array hardware.


1.8.1 Configuring a Digital CertificateThe U2000 supports security encryption to ensure the communication security for the DCN and the confidentiality and integrity for the transmitted data. Adigital certificate is also used to distribute public keys.

Deploying the SSL Trust Certificate on the Internet ExplorerWhen 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, somefunctions of the NE Explorer must be opened through an Internet Explorer. In this case, the SSL trust certificate of the Internet Explorer must bedeployed.

Parent topic: Manual Commissioning Task

1.8.1.1 Deploying the SSL Trust Certificate on the Internet ExplorerWhen 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 ofthe 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 procedure for deploying an SSL certificate preconfigured by Huawei is used as an example. The procedures for deploying other SSL certificatesare similar.

The trust certificate preconfigured by Huawei consists of the root certificate huaweiossCA.crt and intermediate certificate networkossCA.crt. Bothof the two certificates need to be deployed on the Internet Explorer.

Procedure

1. Open the Internet Explorer of the U2000 client and choose Tool > Internet Options from the main menu.

2. In the Internet Options dialog box, select Content tab and click Certificates.

3. In the Certificates dialog box, deploy the root certificate huaweiossCA.crt.

a. Select the Trusted Root Certification Authorities tab and click Import.

b. In the Certificate Import Wizard dialog box, click Next.

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

d. Click Next, and then click Finish.

e. In the Security Warning dialog box that is displayed, click Yes.

f. In the Certificate Import Wizard dialog box, click OK.

4. Deploy the intermediate certificate networkossCA.crt.

a. Select the Intermediate Certification Authorities tab and click Import.

b. In the Certificate Import Wizard dialog box, click Next.

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

d. Click Next, and then click Finish.

e. In the Certificate Import Wizard dialog box that is displayed, click OK.

5. Click Close.

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 certificateaddress mismatch*.

7. Click OK.

8. Restart the Internet Explorer.

Follow-up Procedure

If the U2000 GUI is displayed abnormally, the SSL certificate fails to be uploaded. Refer to the preceding operations to redeploy a digital certificate.

If the dialog which prompted you need trusted certification is displayed in the U2000 NE management, right-click Continue to this website (notrecommended), and then click Open in the New Window. In the dialog box that is displayed, click OK. If the Security Alert dialog box for theinstallation certificate is displayed, click OK to display the current function GUI. After finish the operation, the U2000 GUI will display normally.

Parent topic: Configuring a Digital Certificate

1.8.2 Setting Hardware Alarm MonitoringThis section describes the settings of monitoring the U2000 server (M4000/M5000) hardware and the S2600 disk array hardware.

Setting Servers for Monitoring (M4000/M5000)This section describes how to set the U2000 servers for monitoring. The server hardware that can be set for monitoring includes hard disks, fans, networkports, and power supply units. After the monitoring takes effect, if any hardware is faulty or abnormal, the system reports an alarm to the U2000.

Configuring the Monitoring Function for an S2600 Disk ArrayThis section describes how to configure the monitoring function for an S2600 disk array. After you configure the monitoring function, the U2000automatically reports an alarm if the S2600 disk array becomes faulty or fails to work.

Configuring the Monitoring Function for an S3900 Disk ArrayThis section describes how to configure the monitoring function for an S3900 disk array. After you configure the monitoring function, the U2000automatically reports an alarm if the S3900 disk array becomes faulty or fails to work.

Parent topic: Manual Commissioning Task



1.8.2.1 Setting Servers for Monitoring (M4000/M5000)This section describes how to set the U2000 servers for monitoring. The server hardware that can be set for monitoring includes hard disks, fans, network ports,and power supply units. After the monitoring takes effect, if any hardware is faulty or abnormal, the system reports an alarm to the U2000.

Prerequisites

The PC is connected properly to the XSCF network port of the server.

You have obtained the IP address of network port 0 of the XSCF and this IP address can be pinged on the server.

You have obtained the password of user eis-installer.

Context

If any monitored server hardware is faulty or abnormal, the system reports an alarm about the server hardware to the U2000. When setting a server formonitoring, you need to configure the trust relationship between the server to be monitored and the related XSCF network port.For example, when setting the server osssvr-1 for monitoring, you need to configure the trust relationship between osssvr-1 and osssvr-1-xscf0.

Procedure

1. Log in to the U2000 server as user ossuser.

2. Run the following command to query the public key file of user ossuser:-bash-3.00$ cd /export/home/ossuser/.ssh/

If the system displays cd: /export/home/ossuser/.ssh/: No such file or directory, the .ssh directory does not exist in the root directory.Run the mkdir -p /export/home/ossuser/.ssh/ command and perform 2 again.

If the system displays no information, the .ssh directory exists in the root directory. Run the following command to query the public keyfile:-bash-3.00$ ls id_rsa.pub

If the system displays id_rsa.pub: No such file or directory, proceed to 3.

If the system displays id_rsa.pub, go to 4.

3. Run the following command to create the public key file of user ossuser:-bash-3.00$ ssh-keygen -t rsa -b 2048 -f id_rsa -N ""

A message similar to the following will be displayed:Generating public/private rsa key pair. Your identification has been saved in id_rsa. Your public key has been saved in id_rsa.pub.

4. Run the following command to log in to the XSCF as user eis-installer:-bash-3.00$ ssh -l eis-installer IP address of network port 0 of the XSCF

NOTE:Assume that IP address of network port 0 of the XSCF is 192.168.8.141 in the following operations. You need to replace 192.168.8.141 with the actual IP address onsite.

If the system displays Are you sure you want to continue connecting (yes/no)?, type yes and press Enter.

If the system displays [email protected]'s password:, type the password of user eis-installer and press Enter.

If the system displays ssh: connect to host 192.168.8.141 port 22: Connection refused, logging in to the XSCF in SSH mode fails. Thismay be because the SSH service for the XSCF has not been enabled. You can enable the SSH service by referring to How Do I Enable theSSH Service for the XSCF on the M4000/M5000 Server and then perform 4 again to log in to the XSCF. If the problem persists, contactHuawei technical support.

5. Run the following command to configure the trust relationship between the server to be monitored and the related XSCF network port:XSCF> setssh -c addpubkey -u eis-installer

a. Copy the content in the public key file id_rsa.pub after Please input a public key: and press Enter.

NOTE:You can log in to the same server as user ossuser using another PuTTY and run the following command to obtain the content in the id_rsa.pub file:

-bash-3.00$ cd /export/home/ossuser/.ssh/

-bash-3.00$ cat id_rsa.pub

b. Press Ctrl+D.Wait for about 5 seconds until the system returns to the XSCF> prompt.

NOTE:When the system displays the following information, run the XSCF> setssh -c delpubkey -a -u eis-installer command to delete the configured public keyinformation and perform 5 again:

Size of the public key is exceeded.Please try again after deleting unnecessary public keys.

c. Run the following command to exit the XSCF:



XSCF> exit

6. Run the following command to check whether the trust relationship has been configured successfully:-bash-3.00$ ssh -l eis-installer IP address of network port 0 of the XSCF

If the system displays the XSCF> prompt, the trust relationship has been configured successfully. Run the exit command to exit the XSCF.

If the system displays [email protected]'s password:, the trust relationship fails to be configured. Contact Huawei technicalsupport.

7. Perform the following operations to configure the monitoring script:

a. Run the following command to navigate to the directory where the preInstallPower.sh script is stored:-bash-3.00$ cd /opt/oss/server/platform/resourcemonitor/

b. Run the following command to grant execute permission on the preInstallPower.sh script:-bash-3.00$ chmod u+x ./preInstallPower.sh

c. Run the following command to run the monitoring script:-bash-3.00$ ./preInstallPower.sh

d. When the system displays the following information, type the IP address of network port 0 of the XSCF and press Enter:Please input the IP of XSCF:

e. When the system displays the following information, enter the user name (eis-installer by default) of the XSCF and press Enter:Please input the user of XSCF [default 'eis-installer']

f. When the system displays the following information, type y and press Enter:Are you sure to continue[y/n]:y

A message similar to the following will be displayed:Generate file "checkStatusM.sh"

8. Run the following commands as user root to configure the monitoring task:-bash-3.00$ su - root

Password: password of user root

# cd /opt/oss/server/platform/resourcemonitor/

# ./confDiskM.sh

9. Run the following command to check whether the monitoring task has been configured successfully:# crontab -l

If the last line in the command output displays information similar to the following, the monitoring task has been configured successfully. Otherwise,the monitoring task fails to be configured. Contact Huawei technical support.0-59 * * * * /opt/OSSENGR/engineering/alarmmonitor/for_checkDiskM.sh 2>&1

Parent topic: Setting Hardware Alarm Monitoring

1.8.2.2 Configuring the Monitoring Function for an S2600 Disk ArrayThis section describes how to configure the monitoring function for an S2600 disk array. After you configure the monitoring function, the U2000 automaticallyreports an alarm if the S2600 disk array becomes faulty or fails to work.

Prerequisites

The U2000 services are running properly.

The U2000 server communicates properly with the optical fiber of the S2600 disk array.

The IP network between the U2000 server and the S2600 disk array is normal.

Log in to the U2000 server as user ossuser.

Context

The monitoring software OceanStor Integrated Storage Management (ISM) monitors the hardware status of an S2600 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.

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, thealarms generated on the disk array cannot be handled in time. After the system restores, the historical alarms will not be reported to the U2000.

OceanStor ISM, an integrated storage management platform provided by Huawei, can manage multiple sets of disk arrays. You do not need todownload or install OceanStor ISM because it has been installed on the disk array before delivery.

NOTE:



To configure the monitoring function for the disk array, ensure that the IP address of the disk array and the IP addresses of service network ports or IP addresses of maintenance network portsof the server are on the same network segments. That is, the IP addressed can be pinged. Otherwise, the disk array may fail to report alarms to the U2000.

Procedure

1. Run the following command to log in to controller A of the S2600 disk array in SSH mode:-bash-3.00$ ssh admin@IP address of controller A

NOTICE:The initial user name for the administrator user is admin, and the password is 123456. To ensure system security, change the password after you login 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.

2. Run the following command to check whether the disk array has been assigned Trap IP, namely, the server IP address.OceanStor: admin> showtrapip

Index IP Address Port ID VersionS26000 192.168.9.251 23001 2

If the system does not display any command output, the disk array has not been assigned Trap IP. Perform 3.

If the system displays any command output, the disk array has been assigned Trap IP. In the command output, check whether IP Addressis correct.

If IP Address is correct, go to 4.

If IP Address is incorrect, run the following command to change Trap IP. Then perform 4.OceanStor: admin> chgtrapip -i Index -a Trap IP

NOTE:The value of Index in the preceding command corresponds to Trap IP. You need to type it as required.

Use the preceding command output as an example. If you need to change Trap IP of the disk array from 192.168.9.251 to192.168.9.241, run the following command:OceanStor: admin> chgtrapip -i S26000 -a 192.168.9.241

After the modification is complete, run the showtrapip command to check whether Trap IP is successfully changed.

3. Run the following command to assign Trap IP to the disk array:This section uses 192.168.9.241 as an example. For a single-server system, you need to assign one Trap IP to the disk array. For a HA system, youneed to assign two Trap IP to the disk array.OceanStor: admin> addtrapip -a 192.168.9.241 -v 2 -p 23001

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 arrayconnects.OceanStor: admin> showsys

The system time of the disk array must be consistent with that of the U2000 server to which the disk array connects. If they are inconsistent, run thefollowing command to change the system time of the disk array:OceanStor: admin> chgsystime -t 2011-04-20/11:05:00

NOTE:This section assumes that you change the system time of the disk array to 2011-04-20/11:05:00.

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.

5. Run the following commands to exit controller A:OceanStor: admin> exit

6. Perform the following steps to assign IP addresses to the disk array:

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.

a. Log in to the U2000 server as user ossuser.

b. Run the following command to add the IP address of the disk array controller to the SANtricty_config.xml file:-bash-3.00$ cd /opt/oss/server/platform/resourcemonitor/

-bash-3.00$ vi SANtricty_config.xml

<config><src name = "trapsender" ip = "IP address of controller A" port = "23001" iorstring = ""/><src name = "trapsender" ip = "IP address of controller B" port = "23001" iorstring = ""/></config>

If the controller IP address recorded in this file is incorrect, change the IP address to the new controller IP address. After you change thevalues, press Esc. Then, run the :wq command to save the changes and exit the vi editor.

c. Run the following command to view the user.xml file:-bash-3.00$ vi user.xml



<snmp name = "trap">......<instance name = "san" run = "true" filepath = "SANtricty_config.xml"/>......<loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/></snmp>

If the value of san in the user.xml file is true, press Esc. Then, run the :q command to exit the vi editor.

If the value of san in the user.xml file is not true, change it to true. After you change the values, press Esc. Then, run the :wqcommand to save the changes and exit the vi editor.

d. Run the following commands to restart the ResourceMonitor process:-bash-3.00$ 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. This section usesID 13382 as an example.-bash-3.00$ kill -9 13382

NOTE:In the preceding command, 13382 is the process ID of ResourceMonitor. Replace it with the actual value.

e. Run the following commands to restart the trapdispatcher service:-bash-3.00$ svc_adm -cmd restartsvc trapdispatcher


1.8.2.3 Configuring the Monitoring Function for an S3900 Disk ArrayThis section describes how to configure the monitoring function for an S3900 disk array. After you configure the monitoring function, the U2000 automaticallyreports an alarm if the S3900 disk array becomes faulty or fails to work.

Prerequisites

The U2000 services are running properly.

The U2000 server communicates properly with the optical fiber of the S3900 disk array.

The IP network between the U2000 server and the S3900 disk array is normal.

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.

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, thealarms generated on the disk array cannot be handled in time. After the system restores, the historical alarms will not be reported to the U2000.

OceanStor ISM, an integrated storage management platform provided by Huawei, can manage multiple sets of disk arrays. You do not need todownload or install OceanStor ISM because it has been installed on the disk array before delivery.

NOTE:

To configure the monitoring function for the disk array, ensure that the IP address of the disk array and the IP addresses of service network ports or IP addresses of maintenancenetwork ports of the server are on the same network segments. That is, the IP addressed can be pinged. Otherwise, the disk array may fail to report alarms to the U2000.Configure disk array monitoring on either controller A or B. The following example describes how to configure disk array monitoring on controller A.

Procedure

1. Run the following command on the U2000 server to log in to controller A of the S3900 disk array in SSH mode:$ 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 passwordafter 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.

2. Run the following command to check whether the disk array has been assigned Trap IP, namely, the server IP address.admin:/>showtrapip

============================================================ Trap IP Information------------------------------------------------------------



Server ID Server IP Server Port Trap Version------------------------------------------------------------ 0 10.168.9.251 23001 SNMPv3============================================================

If the system does not display any command output, the disk array has not been assigned Trap IP. Perform 3.

If the system displays any command output, the disk array has been assigned Trap IP. In the command output, check whether IP Addressis correct.

If IP Address is correct, go to 4.

If IP Address is incorrect, run the following command to change Trap IP. Then perform 4.admin:/>chgtrapip -server service ID -ip IP address -port service port number-ver SNMP version

NOTE:service ID specifies the service ID corresponding to the Server ID whose trap IP address needs to be modified.IP address specifies the actual trap IP address.service port number specifies the service port number corresponding to the Server Port whose trap IP address needs to be modified.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.

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

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 10.168.9.241 as an example. For a single-server system, you need to assign one Trap IP to the disk array. For a HA system, youneed to assign two Trap IP to the disk array.

admin:/> addtrapip -ip 10.168.9.241 -port 23001 -ver 3

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 arrayconnects.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 areinconsistent, 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.

5. Run the following commands to exit controller A:admin:/> exit

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.

a. Log in to the U2000 server as user ossuser.

b. Run the following command to add the IP address of the disk array controller to the SANtricty_config.xml file:$ cd /opt/oss/server/platform/resourcemonitor/$ vi SANtricty_config.xml<config><src name = "trapsender" ip = "IP address of controller A" port = "23001" iorstring = ""/><src name = "trapsender" ip = "IP address of controller B" port = "23001" iorstring = ""/></config>

<traps name = "snmptraps"><trap oid = "1.3.6.1.4.1.2011" name = "DiskarrayStatusAlarm" 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 = "0" description = "" maxlen = "50"/></trap></traps>

If the controller IP address recorded in this file is incorrect, change the IP address to the new controller IP address. After you change thevalues, press Esc. Then, run the :wq command to save the changes and exit the vi editor.

NOTE:If the login controller is controller A, Trap IP is the IP address of controller A.If the login controller is controller B, Trap IP is the IP address of controller B.



c. Run the following command to view the user.xml file:$ vi user.xml<snmp name = "trap">......<instance name = "san" run = "true" filepath = "SANtricty_config.xml"/><instance name = "vcs" run = "true" filepath = "vcs_config.xml"/><loginfo name = "debug" run = "false" filepath = "HDMonitor.debug"/></snmp>

If the value of san in the user.xml file is true, press Esc. Then, run the :q command to exit the vi editor.

If the value of san in the user.xml file is not true, change it to true. After you change the values, press Esc. Then, run the :wqcommand to save the changes and exit the vi editor.

d. Run the following commands to restart the ResourceMonitor process:$ ps -ef | grep "ResourceMonitor"ossuser 21579 1 0 20:15:05 ? 4:43 ResourceMonitor -cmd startossuser 23892 13957 0 10:43:05 pts/2 0:00 grep ResourceMonitor

In the command output, the second row of the ResourceMonitor -cmd start line displays the ID of ResourceMonitor. This section usesID 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.


1.9 Starting the U2000 Server in a Solaris High Availability SystemThe U2000 server can be started in three steps: power on the server safely, start the database, and start the U2000 server processes.

Powering On the Server SafelyThis topic describes how to power on the server in a HA system (Solaris) safely. The procedure for powering on a server varies according to the servertype and disk array type.

Starting the DatabaseThis topic describes how to start the database in a Solaris high availability system. The U2000 can start properly only after the database is started.

Starting the U2000 Server ProcessesThis topic describes how to start the U2000 server processes in a Solaris high availability system. You can log in to the U2000 to manage a network onlyafter starting the U2000 server processes on the computer on which the U2000 is installed.


1.9.1 Powering On the Server SafelyThis topic describes how to power on the server in a HA system (Solaris) safely. The procedure for powering on a server varies according to the server typeand disk array type.



NOTICE:










NOTE:


M4000/M5000 Server







3. Press the power switch of the workstation, which is identified by . Wait 2 to 3 minutes. If front indicator of the server is on (changes to steady



green), the server starts up and performs self-diagnosis.



Disk Array

NOTICE:













Parent topic: Starting the U2000 Server in a Solaris High Availability System

1.9.2 Starting the DatabaseThis topic describes how to start the database in a Solaris high availability system. The U2000 can start properly only after the database is started.

Prerequisites

The OS has been started.

The server is properly connected to the network.

The VCS service must be properly started. The VCS service has started along with the OS and the disk is functioning properly. For details about howto check the server disk status, see Checking Server Disks in the U2000 Administrator Guide.

Procedure

1. Perform the following operations to start the Sybase database:

GUI mode:

a. Log in to the active site as the root user.

b. Run the following command to start the VCS client:

# hagui&

c. Choose File > New Cluster from the main menu. In the dialog box that is displayed, enter the server IP address and click OK.





e. Ensure that all Veritas resources are in Enabled state. Use the BackupServer resource as an example. Perform the followingoperations:Expand the AppService node and then the SybaseBk node in the navigation tree, right-click BackupServer, and check whetherEnabled has been selected in the shortcut menu. If Enabled has not been selected, select it.

f. Right-click BackupServer and choose Online > host name from the shortcut menu.

g. In the dialog box that is displayed, click Yes.Wait until the BackupServer and DatabaseServer resource icons on the Resources tab page are bright, which indicates that theSybase database service has started.

CLI mode:

a. Log in to the active site as the root user.

b. Run the following commands to query Veritas resource names:# haconf -makerw# hares -list

Information similar to the following is displayed:BackupServer PrimaryDataFilesystem PrimaryDatabaseServer PrimaryNMSServer PrimaryRVGPrimary Primarydatarvg Primarywac Primary

c. Run the hares -modify resource name Enabled 1 command to change the status of all Veritas resources to Enabled. Use theresource names displayed in the previous command output as an example. Run the following commands to change the status ofall the Veritas resources to Enabled:

# hares -modify BackupServer Enabled 1# hares -modify DataFilesystem Enabled 1# hares -modify DatabaseServer Enabled 1# hares -modify NMSServer Enabled 1# hares -modify RVGPrimary Enabled 1# hares -modify datarvg Enabled 1# hares -modify wac Enabled 1

d. Run the following command to start the Sybase database service:# hares -online BackupServer -sys hostname


Result

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

Information similar to the following is displayed:dbuser 4664 1 0 Apr15 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/RUN_DBSVRdbuser 4675 4664 32 Apr15 ? 2-22:42:47 /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_0dbuser 4688 1 0 Apr15 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/RUN_DBSVR_backdbuser 4692 4688 0 Apr15 ? 00:00:00 /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install/DBSVR_back.log -N25 -C20 -M/opt/sybase/ASE-15_0/bin/sybmultbuf...

NOTE:If the displayed information contains /opt/sybase/ASE-15_0/bin/dataserver -sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back, the Sybase process is running.


1.9.3 Starting the U2000 Server ProcessesThis topic describes how to start the U2000 server processes in a Solaris high availability system. You can log in to the U2000 to manage a network only afterstarting the U2000 server processes on the computer on which the U2000 is installed.

Prerequisites

The OS on the computer on which the U2000 server processes are installed is running properly, and the database has been started.

Procedure

1. Log in to the OS on the active site as the root user.



2. Start the U2000 server processes.

GUI mode:

a. Open a terminal window and run the following command:

# hagui&


b. Choose Connect to cluster name.


a. Choose File > New Cluster.b. Enter an application network IP address.c. Click OK.

c. Set User Name and Password.


d. Click OK.

e. In the Cluster Explorer window, select the AppService resource group in the navigation tree, right-click, and choose Online >host name from the shortcut menu to start the Sybase process and U2000 server processes.


Normally, the value of State for the active site is Online in the Group Status on Member Systems area on the Status tab page,and the value of Status is Online on host name in the Resource Status area.

NOTE:Use the actual host name for real-world configuration.If a fault has occurred during the start of the AppService process, right-click AppService and choose clear fault from the shortcut menu torectify the fault. Then choose Online > host name to start the AppService process.


CLI mode:# hagrp -online AppService -sys hostname

NOTE:Use the actual host name for real-world configuration.If a fault has occurred during the start of the AppService process, run the

# hagrp -clear AppService -sys hostname

command to rectify the fault. Then run the

# hagrp -online AppService -sys hostname

command to start the AppService process.

Result

1. Log in to the OS of the active site as the ossuser user.

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

Information similar to the following is displayed: 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 imap_sysmonitor -cmd start.


1.10 Shutting Down the U2000 Server in a High Availability System (Solaris)Four steps are required to shut down the U2000 server in a high availability system (Solaris): stop the U2000 server processes, shut down the database, stop theVCS service, and power off the server safely.

Stopping the U2000 Server ProcessesDo not stop the U2000 server processes when the U2000 server is managing NEs. Stop the U2000 server processes only for some special purposes, forexample, changing the system time of the computer where the server is installed or upgrading the version. This topic describes how to stop the U2000server processes on the Solaris HA system.

Shutting Down the DatabaseThe U2000 can start properly only after the database is started. Before shutting down the database, stop the U2000 server processes. This topic describeshow to shut down the database on the HA system.

Stopping the VCS ServiceThis topic describes how to stop the VCS service.

Power Off the Server SafelyBefore shutting down the U2000 server, stop the U2000 server processes and the database. This topic describes how to power off the Solaris HA systemsafely.


1.10.1 Stopping the U2000 Server ProcessesDo not stop the U2000 server processes when the U2000 server is managing NEs. Stop the U2000 server processes only for some special purposes, forexample, changing the system time of the computer where the server is installed or upgrading the version. This topic describes how to stop the U2000 serverprocesses on the Solaris HA system.

Prerequisites

Exit all running U2000 clients.

Procedure

1. Log in to the OS of the active site as the root user.

2. Stop the U2000 server processes.

GUI mode:

a. Open a terminal window, run the following command:

# hagui&



NOTE:



If you are logging in to the VCS for the first time, you need to create a new Cluster.




d. Click OK.

e. Choose AppService from the navigation tree.

f. Click the Resources tab. Right-click NMSServer and choose Offline > Host name from the shortcut menu. In the Questiondialog box, click Yes.Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes have been stopped.

CLI mode:


3. Ensure that the U2000 is not running.

a. Log in to the OS of the active site as the ossuser user.

b. Run the following command to check the running status of the U2000 process:$ daem_ps

Information similar to the following is displayed:ossuser 26225 1 0 09:16:02 ? 0:00 imapwatchdog -cmd start -type standbyossuser 26225 1 0 09:16:03 ? 0:01 ResourceMonitor -cmd start

c. Run the following commands to stop the U2000 processes:$ su - rootPassword: root user password# hares -offline NMSServer -sys hostname# exit

d. Run the following command to check the running status of the U2000 process:$ daem_ps

NOTE:The process is stopped if the displayed information is empty.

Parent topic: Shutting Down the U2000 Server in a High Availability System (Solaris)

1.10.2 Shutting Down the DatabaseThe U2000 can start properly only after the database is started. Before shutting down the database, stop the U2000 server processes. This topic describes howto shut down the database on the HA system.

Prerequisites

The U2000 server processes must have been stopped.

Procedure

1. Perform the following operations to disable the Sybase database service at the primary site in the HA system:

NOTE:By default, the Sybase database service at the secondary site is not running.

GUI mode:


b. Run the following command to start the VCS client at the primary site:# hagui&

c. Choose File > New Cluster from the main menu. In the window that is displayed, enter the IP address of the server and clickOK.





e. On the VCS client of the primary site, right-click the NMSServer node and choose Offline > hostname from the shortcut menu.

f. In the confirmation dialog box, click Yes.

g. After the NMSServer node is dimmed, right-click the BackupServer node and choose Offline > hostname from the shortcutmenu.

h. In the confirmation dialog box, click Yes.

i. After the BackupServer node is dimmed, right-click the DatabaseServer node and choose Offline > hostname from theshortcut menu.

j. In the confirmation dialog box, click Yes.

CLI mode:


b. Run the following command to shut down the U2000:# hares -offline NMSServer -sys hostname

c. Run the following command to disable the Sybase database service:# hares -offline BackupServer -sys hostname

# hares -offline DatabaseServer -sys hostname


Run the following command to check whether the Sybase database service is disabled:# ps -ef | grep sybaseIf 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


1.10.3 Stopping the VCS ServiceThis topic describes how to stop the VCS service.

Prerequisites

The U2000 and database must have been shut down.

Context

Before powering off the server safely, manually stop the VCS service; otherwise, the server may fail to shut down properly.

Procedure

1. Log in to the OS on the server as the root user.

2. Run the following command to stop the VCS service:# hastop -all -force


1.10.4 Power Off the Server SafelyBefore shutting down the U2000 server, stop the U2000 server processes and the database. This topic describes how to power off the Solaris HA system safely.

Prerequisites

The U2000 server processes must have been stopped.

The database must have been shut down.

The VCS services must have been shut down.

Procedure




2. Run the following commands to power off the server:# sync;sync;sync;sync# shutdown -y -g0 -i5

3. If a KVM is equipped, power off the KVM switcher.


1.11 Getting StartedThis topic describes certain common operations that can be performed on the Solaris workstation. After learning this topic, you can improve the efficiency ofthe operations on the Solaris OS.

Syntax Structure of Command LinesOn the desktop of the GUI OS, right-click in the blank area and choose Open Terminal from the shortcut menu to access the CLI.The syntax structure of command lines is as follows:command option parameter

The Solaris commands are case-sensitive. That is, the OS considers an uppercase letter and its corresponding lowercase letter two different letters. Forexample, 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 Lscommand because the Ls command is considered as an invalid system command. The options in the Solaris commands are used to change the commandexecution 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

Switching to the bash ModeIt is recommended that you switch the system to the bash mode after logging in to the OS to reduce the period used for entering commands. Generally, afterlogging in to the OS, you can run the bash command to switch to the bash mode, as shown in the following figure.

The following basic features of the bash mode help you interact with the system better:

Command line editing: enables you move the cursor among command lines or edit text.

History command: allows you to edit or restore the command that has been entered in command lines.

For example, if you enter the first two or three letters of a command or a file and then press Tab, the system automatically fills in the desired command or file.

Switching UsersThe Solaris OS has strict user management rules. Different OS users can access only associated applications.

To switch OS users, run the following command:su - OS user nameLeave 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:

After the su - ossuser user is switched to the ossuser user, both the operational permissions and environmental variables of the ossuser user are obtained.After the su ossuser user is switched to the ossuser user, only operational permissions and not environmental variables of the ossuser user are obtained.

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.

Logging in to the Solaris OS Through Remote Login SoftwareThere 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 froma remote site through command lines.

NOTE:The PuTTY is a free software used to log in to the UNIX OS by commands. You can access http://www.putty.org to download the PuTTY. For more information about software operation,see the software Help or go to the official website of the software for technical support.

1. Double-click the shortcut icon of the PuTTY software on the desktop. The following dialog box is displayed.

The following table shows the login configurations.

Parameter Description

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 asrequired. Generally, select SSH (more secure, recommended) or Telnet.

NOTE:If the operating system is not enabled with security hardening, thisparameter can be set to either Telnet or SSH. SSH is recommended becauseit is more secure than Telnet.If the operating system is enabled with security hardening or the Telnetservice 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 Solaris OS Using Remote GUI SoftwareThere is various remote GUI software, for example, VNC. For details about how to configure and use the VNC, see How to Use the VNC to Remotely Accessa Workstation.

Logging in to the Solaris OS Through the Windows OS CLI

1. Choose Start > Run on the Windows OS desktop.

2. In the Run dialog box, enter cmd, and then click OK. The CLI is displayed.

3. In the CLI, enter telnet IP address of the server to be logged in to, and then press Enter.Login:

NOTE:In Windows 7, if the telnet command fails, choose Start > Control Panel > Programs > Programs and Features > Turn Windows features on or off and select Telnet Client.

4. Enter the name of the user who logs in to the OS of the server, for example, root. Then, press Enter.Password:



5. Enter the login password of the user. Press Enter to log in to the OS.

Restarting the Solaris OS

Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

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 theserver by referring to the preceding login method.

Shutting down the Solaris OS

Run the following commands to shut down the OS:# sync;sync;sync;sync# shutdown -y -g0 -i5

Difference Between Command Operations on the Solaris and SUSE Linux OSs

Table 1 Difference between command operations on the Solaris and SUSE Linux OSsCommand operation On Solaris On SUSE Linux

Restart the OS. Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -y -g0 -i6

Run the following commands to restart the OS:# sync;sync;sync;sync# shutdown -r now

Shut down the OS. Run the following commands to shut down the OS:# sync;sync;sync;sync# shutdown -y -g0 -i5

Run the following commands to shut down the OS:# sync;sync;sync;sync# shutdown -h now

Disable system hardening. Run the following command to disable systemhardening for the SetSolaris system:# sek -r all

Run the following command to disable systemhardening for the SetSuse system:# sek -b all

Table 2 Difference between common operations on the Solaris and SUSE Linux OSsCommon operation On Solaris On SUSE Linux

U2000 client Supported Not supported


1.12 Manually Installing the Solaris OS and Its PatchesThis topic describes how to manually install the OS by using the Solaris installation DVD delivered with the product and how to install patches by using thepatch package.

Installing the OS Through the GUIThis topic describes how to install Solaris 10 OS through the GUI if the server is connected to the KVMS or monitor.

Installing the OS Through the CLIThis topic describes how to install Solaris 10 OS through the CLI if the server is not connected to the KVMS or monitor.

Installing the Solaris OS PatchesThis topic describes how to install the Solaris OS patches. To ensure the reliable system performance, the sparc_patch_20.0.0 patch must be installedimmediately after the Solaris OS is installed.


1.12.1 Installing the OS Through the GUIThis topic describes how to install Solaris 10 OS through the GUI if the server is connected to the KVMS or monitor.

Prerequisites

The Solaris 10 OS disk, that is, Solaris 10 Operating System (10/08 SPARC Platform Edition), is on-hand.


Host name

Network interface

System IP address

Subnet mask



Route

The server is connected to the keyboard, video, mouse, switch (KVMS) or monitor.

Context

The system will go straight to the OK prompt if Solaris OS has not been installed on the server.

The system will go to the OK prompt if Solaris OS is installed on the server when user root runs the init 0 command.

Procedure

1. Power on the Sun server and insert the Solaris 10 OS installation DVD into the DVD-ROM drive.

2. Press STOP+A. At the OK prompt, run the following command:



3. Optional: If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used, query and record the drive of the startup disk. If another type of server isused, ignore this step. For details about the method for querying the drive of the startup disk, see How to Query the Drive of the Default StartupDisk of the Workstation.

NOTICE:If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used, you must query and record the drive of the startup disk and the system must be installed onthe startup disk. Otherwise, the OS fails to be restarted properly.

4. Run the following command to start the installation program:




5. Move the pointer to the text box. Enter 0 to select English and press Enter.

6. In the Welcome dialog box, click Next.

7. In the Network Connectivity dialog box, select Networked and click Next.

8. Optional: In the Configure Multiple Network Interfaces dialog box, select a primary network interface such as e1000g0, and click Next.

NOTE:If the server contains only one network interface, the Configure Multiple Network Interfaces dialog box will not be displayed.

You are recommended to select the first network interface in scenarios where the server contains multiple network interfaces (the Configure Multiple NetworkInterfaces dialog box will be displayed).

The network interface name is related to the network adapter type. The common types of network adapters are e1000g, bge, and ce.The mappings Between Physical and Logical Network Interfaces on an Oracle Server Running Solaris see Mappings Between Physical and Logical NetworkInterfaces on Server Running Solaris.

9. In the DHCP for e1000g0 dialog box, select No and click Next.

10. In the Host Name for e1000g0 dialog box, enter the planned host name and click Next.

11. In the IP Address for e1000g0 dialog box, enter the planned IP address and click Next.

12. In the Netmask for e1000g0 dialog box, enter the planned subnet mask and click Next.

13. In the IPv6 for e1000g0 dialog box, select No and click Next.

14. In the Set the Default Route for e1000g0 dialog box, select Specify one and click Next.

NOTICE:The default route is not recommended if the NMS security policies are used. After installing the NMS, manually configure the static route. Fordetails about how to manually configure the static route, see How to Add a Static Route.

15. In the Set the Default Route for e1000g0 dialog box, enter the route IP address and click Next.

16. In the Kerberos dialog box, select No for the Kerberos security and click Next.

17. In the Name Service dialog box, select None for the name service and click Next.

18. In theNFSv4 Domain Name dialog box, select Use the NFSv4 domain derived by the system and click Next.

19. In the Time Zone dialog box, select Geographic Continent/Country/Region and click Next.

20. In the Country or Region dialog box, select the appropriate country and region. For example, select Asia and China. Then, click Next.

21. In the Date and Time dialog box, set the time and click Next.

NOTICE:



In the OS, the system time must be set correctly according to the specified format. Stable system time is of vital importance to the system. Hence, donot modify the system time while the server is running.

22. In the Enabling Remote Services dialog box, select Yes and click Next.

23. In the Confirm Information dialog box, confirm that the configuration is correct and click Confirm; click Back to modify the configuration.

24. In the Welcome dialog box, click Next.

25. In the Installer Options dialog box, select Yes for Reboot automatically after software installation and Eject CD/DVD automatically aftersoftware installation. Then, click Next.

26. In the Specify Media dialog box, select CD/DVD and click Next.

27. In the License dialog box, select Accept and click Next.

NOTE:If the Select Upgrade or Initial Install dialog box is displayed during installation, the system can be upgraded. You can select Initial Install if the original system configurationis not required.

28. In the Select Type of Install dialog box, select Custom Install and click Next.

29. In the Select Software Localizations dialog box, select English (United States) (en_US) and English (United States, UTF-8) (en_US.UTF-8) forNorth America and click Next.

30. In the Select System Locale dialog box, select POSIX C (C) and click Next.

31. In the Additional Products dialog box, select None and click Next.

32. In the Select Solaris Software Group dialog box, select Default Packages for Entire Group Plus OEM and click Next.

33. In the Disk Selection dialog box, select all disks and click Next.

34. In the Preserve Data dialog box, select No and click Next.

35. In the Lay Out File Systems dialog box, select the desired disks to lay out file systems, and click Modify to partition the disks.

NOTICE:

Select a disk to be partitioned based on disk planning. For details about partition planning, see Planning Disk Partitions. The T5220 serveris used as an example. If disks c1t0d0 and c1t1d0 need to be partitioned, you must select the two disks in this step. The disks that are notselected cannot be partitioned. Note that this step cannot be rolled back. Select disks correctly.If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used for partition, select c0drive of the startup diskd0 as the first hard disk. Fordetails about the method for obtaining the drive of the startup disk, see 4.

NOTE:The sector names shown as 0, 1, 3, 4, 5, 6, and 7 respectively refer to c1t0d0s0, c1t0d0s1, c1t0d0s3, c1t0d0s4, c1t0d0s5, c1t0d0s6, and c1t0d0s7. The size of theoverlap partition corresponding to the c1t0d0s2 disk is the same size as the entire disk. Therefore, there is no need to set the size.The disk names vary according to device model.

36. Click OK. In the Lay Out File Systems dialog box, click Next.

37. In the Ready to Install dialog box, click Install Now.A dialog box will be displayed that shows the progress of the installation. The duration of the installation process depends on the serverconfiguration. Generally, the installation lasts 60 minutes.

NOTE:Click Continue each of the three times that the Pause dialog box is displayed during installation. The system will automatically restart and the installation willcontinue if this operation is not performed.

After the installation is complete, the DVD-ROM door will automatically open. Take out the DVD.

38. After the system restarts, In the Root Password dialog box, enter the password of user root twice and click Next.

NOTE:Do not forget the password of user root.

39. Log in to the Solaris OS as user root.If login to Solaris OS as user root is possible, Solaris OS is successfully installed. Otherwise, install the OS again.

Follow-up Procedure

After the Solaris OS is installed, verify that the system character set is correct, and enable user root to remotely log in to the system and use the SFTP tool.

1. Run the following command to verify that the system character set is correct:# bash# locale -a

If the following information is included in the command output, the character set of Solaris OS is correct. Otherwise, reinstall the OS.Cen_US.UTF-8

2. Run the following commands to set the language environment variable of the system:# export LANG=C

3. Configure to allow the root user to start the FTP/SFTP/Telnet/SSH service. For details, see How to Start/Stop the FTP, SFTP, and Telnet Servicesand How to Enable and Disable the FTP/Telnet Authority of user root on Solaris OS and How to Start/Stop the SSH Service.



4. After logging in to the OS as the root user, install the OS patch. Otherwise, the U2000 software cannot be installed. For details about the method ofinstalling the OS patch, see Installing the Solaris OS Patches.


Parent topic: Manually Installing the Solaris OS and Its Patches

1.12.2 Installing the OS Through the CLIThis topic describes how to install Solaris 10 OS through the CLI if the server is not connected to the KVMS or monitor.

Prerequisites

The Solaris 10 OS disk, that is, Solaris 10 Operating System (10/08 SPARC Platform Edition), is on-hand.


Host name

Network interface

System IP address

Subnet mask

Route


Procedure









-> cd /HOST-> ls




































b. Enter y.






f. Enter y.





OK

2. Insert the Solaris 10 installation DVD into the DVD-ROM drive.

3. Run the following command at the OK prompt to set the OS automatic startup and press Enter:ok setenv auto-boot? true


If the following message is displayed, the configuration is complete:auto-boot? = true

4. Optional: If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used, query and record the drive of the startup disk. If another type of server isused, ignore this step. For details about the method for querying the drive of the startup disk, see How to Query the Drive of the Default StartupDisk of the Workstation.

NOTICE:If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used, you must query and record the drive of the startup disk and the system must be installed onthe startup disk. Otherwise, the OS fails to be restarted properly.

5. Run the following command to boot the system for installation preparation:




6. In the Select a Language dialog box, the system prompts "Please make a choice (0-9), or press h or ? for help:." Enter 0 and select English. Then,press Enter.



NOTE:The language selected in this step only applies to the language environment of this installation process. It is irrelevant to the languages supported by the Solaris OS afterinstallation.

7. In the What type of terminal are you using? dialog box, the system prompts "Type the number of your choice and press Return:". Enter 3 and setthe type of the terminal used during OS installation to DEC VT100. Then, press Enter.

8. In the The Solaris Installation Program dialog box, press F2.

NOTE:If F2 does not function, press Esc+2 instead.If ↑ or ↓ does not function, use Ctrl+B or Ctrl+N instead.

9. In the Identify This System dialog box, press F2.

10. Optional: In the Network Connectivity dialog box, click Yes to connect the network. Then, press F2.

NOTE:You can use ↑ and ↓ to move the cursor to the required bracket. Then, press Enter. The selection is complete if X is displayed in the bracket.

11. Optional: In the Configure Multiple Network Interfaces dialog box, select a primary network interface, such as e1000g0. Then, press F2.

NOTE:If the server contains only one network interface, skip this step.If the server contains multiple network interfaces, the Configure Multiple Network Interfaces dialog box will be displayed. In this scenario, you are recommendedthat you select the first network interface as the primary network interface for connecting to the public network.The network interface name is related to the network adapter type. The common types of network adapters are e1000g, bge, and ce.The mappings Between Physical and Logical Network Interfaces on an Oracle Server Running Solaris see Mappings Between Physical and Logical NetworkInterfaces on Server Running Solaris.

12. Optional: In the DHCP for e1000g0 dialog box, select No to disable DHCP and press F2.

13. Optional: In the Host Name for e1000g0 dialog box, enter the planned host name and press F2.

14. Optional: In the IP Address for e1000g0 dialog box, enter the planned server IP address and press F2.

15. In the Subnet for e1000g0 dialog box, select Yes and press F2.

16. In the Netmask for e1000g0 dialog box, enter the planned subnet mask and press F2.

17. In the IPv6 for e1000g0 dialog box, select No to disable IPv6 and press F2.

18. In the Set the Default Route for e1000g0 dialog box, select Specify one and press F2.

NOTICE:The default route is not recommended if the NMS security policies are used. After installing the NMS, manually configure the static route. Fordetails about how to manually configure the static route, see How to Add a Static Route.

19. In the Set the Default Route for e1000g0 dialog box, enter the default gateway IP address. Then, press F2.

20. In the Confirm Information for e1000g0 dialog box, confirm that the configuration is correct and press F2.

NOTE:If any information is incorrect, you can press F4 to return to the Network Connectivity dialog box, and modify the settings of the network connection.

21. In the Configure Security Policy dialog box, select No to skip the configuration of Kerberos security. Then, press F2.

22. In the Confirm Information dialog box, confirm that the security configuration is correct and press F2.

NOTE:If any information is incorrect, press F4 to return to the Configure Security Policy dialog box, and modify the settings of security policies.

23. In the Name Service dialog box, select None to skip the configuration of the name server. Then, press F2.

24. In the Confirm Information dialog box, confirm that the name server configuration is correct and press F2.

NOTE:If any information is incorrect, press F4 to return to the Name Service dialog box, and modify the settings of the name server.

25. In the NFSv4 Domain Name dialog box, select Use the NFSv4 domain derived by the system. Then, press F2.

26. In the Confirm Information for NFSv4 Domain dialog box, ensure that NFSv4 Domain Name: Value to be derived dynamically is displayed.Then, press F2.

27. In the Time Zone dialog box, select the appropriate geographical area, such as Asia, according to your location. Then, press F2.

NOTICE:Do not select other - offset from GMT or other - specify time zone file. Otherwise, a system time error may occur.

28. In the Country or Region dialog box, select the appropriate country or region, such as China, according to your location. Then, press F2.

29. In the Date and Time dialog box, set precise system time. Then, press F2.

NOTICE:



In the OS, the system time must be set correctly according to the specified format. Stable system time is of vital importance to the system. Hence, donot modify the system time while the server is running.

30. In the Confirm Information dialog box, confirm that the preceding configuration is correct and press F2.

31. Optional: In the Identify This System dialog box, confirm that the configuration is correct and press F2.

32. Optional: In the Enabling remote services dialog box, select Yes and press F2.

33. In the Provide Solaris Auto Registration Info dialog box, select I would like to register using My Oracle Support information and press F2.

34. In the Provide Solaris Auto Registration Info dialog box, do not enter registration information and press F2 to continue.

35. In the Solaris Interactive Installation dialog box, press F2 to select the Standard installation.

36. In the Eject a CD/DVD Automatically? dialog box, select Automatically eject CD/DVD to automatically install the software through the drive.Then, press F2.

37. In the Reboot After Installation? dialog box, select Auto Reboot to set the restart mode to automatic restart. Then, press F2.

38. In the Solaris Interactive Installation dialog box, press F4 to start initial installation.

39. In the License dialog box, press F2 to continue.

40. In the Select Geographic Regions dialog box, press Enter to expand the Asia list. Select Simplified Chinese EUC, Simplified Chinese GB18030,Simplified Chinese GBK, and Simplified Chinese UTF-8. Expand the North America list. Select U.S.A.(UTF-8) and U.S.A. (en_US.ISO8859-1). Then, press F2.

NOTE:The selections in this step determine the languages supported by the Solaris OS to be installed. Use ↑ and ↓ to move the cursor to the selected list. Then, press Enter. Thesubitems will be displayed. Use ↑ and ↓, or ← and → to move the cursor to the required bracket. Press Enter. If X is displayed in the bracket, the language is selected.

41. In the Select System Locale dialog box, select POSIX C (C) and press F2.

42. In the Additional Products dialog box, select None and press F2.

43. In the Choose Filesystem Type dialog box, select UFS and press F2.

44. In the Select Software dialog box, select Entire Distribution plus OEM support and press F2.

45. In the Select Disks dialog box, select all disks and press F2.

46. In the Preserve Data? dialog box, press F2. The data on the disk is not preserved.

47. In the Automatically Layout File Systems? dialog box, press F4 to manually partition disks and plan the file system.

48. In the File System and Disk Layout dialog box, select the disk to be partitioned, and press F4 to manually define disk partitions.

NOTICE:

Select a disk to be partitioned based on disk planning. For details about partition planning, see Planning Disk Partitions. The T5220 serveris used as an example. If disks c1t0d0 and c1t1d0 need to be partitioned, you must select the two disks in this step. The disks that are notselected cannot be partitioned. Note that this step cannot be rolled back. Select disks correctly.If the Netra T4-1/Oracle T4-1/Oracle T4-2 server is used for partition, select c0drive of the startup diskd0 as the first hard disk. Fordetails about the method for obtaining the drive of the startup disk, see 4.

NOTE:The sector names shown as 0, 1, 3, 4, 5, 6, and 7 respectively refer to c1t0d0s0, c1t0d0s1, c1t0d0s3, c1t0d0s4, c1t0d0s5, c1t0d0s6, and c1t0d0s7. The size of theoverlap partition corresponding to the c1t0d0s2 disk is the same size as the entire disk. Therefore, there is no need to set the size.The disk names vary according to device model.

49. In the Select Disk to Customize dialog box, perform the following to partition the selected disks, and then press F2 to continue.

a. Select the first disk. Move the cursor to the line of the c1t0d0 disk and press F4. The Customize Disk: c1t0d0 dialog box will bedisplayed.

NOTICE:

The disk drive for the Netra T4-1/Oracle T4-1/Oracle T4-2 server is long and cannot be completely displayed on the Select Diskto Customize page. Select the disk in the Select Disk to Customize dialog box according to the order shown in the File Systemand Disk Layout dialog box.In the Customize Disk: c1t0d0 dialog box, ensure that the disk drive of Customize Disk: is the current disk to be configured. Ifnot, press F2 to return to the Select Disk to Customize dialog box and select another disk.

b. Define the partition and press F2. The Select Disk to Customize dialog box will be displayed.

c. Select other disks. For details, see the preceding steps for disk partitioning.

NOTE:You do not need to perform this step if the server is equipped with two disks or four disks without any disk array.

50. In the File System and Disk Layout dialog box, confirm that the disk partition plan is correct and press F2.

51. In the Mount Remote File Systems? dialog box, press F2 to continue without installing the distributed file system.

52. In the Profile dialog box, confirm that the preceding configuration is correct and press F2.

NOTE:If the Solaris OS has been installed on the server and the currently planned boot partition is not on the disk where the original boot partition is located, a warning will indicate



that the default boot device changed. In the Warning dialog box, press F2 to ignore the warning and proceed with the following steps.

53. The duration of the installation process will vary according to the server configuration. Generally, the installation lasts 60 minutes.

NOTE:During system installation, a progress bar will be displayed.

When the following message is displayed, enter c:Pausing for 30 seconds at the "Summary" screen. The wizard will continue to the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to continue.

The system will continue the installation.When the following message is displayed, enter c:Pausing for 90 seconds at the "Reboot" screen. The wizard will continue to the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to continue.

The system will restart automatically.If no operation is performed, the OS will automatically restart after 90 seconds.

NOTICE:After the installation, the DVD-ROM door will automatically open. Take out the disk.

54. Optional: In the Configure Keyboard Layout dialog box that is displayed after system restart, select US-English. Then, press F2 to complete allconfigurations and access the Root Password dialog box.

55. In the Root Password dialog box, enter the password of the root user twice to set the password. Then, press F2.

NOTE:Do not forget the password of user root.

If login to Solaris OS as user root is possible, Solaris OS is successfully installed. Otherwise, install the OS again.

Follow-up Procedure

After the Solaris OS is installed, verify that the system character set is correct, and enable user root to remotely log in to the system and use the SFTP tool.

1. Run the following command to verify that the system character set is correct:# bash# locale -a

If the following information is included in the command output, the character set of Solaris OS is correct. Otherwise, reinstall the OS.Cen_US.UTF-8

2. Run the following commands to set the language environment variable of the system:# export LANG=C

3. Configure to allow the root user to start the FTP/SFTP/Telnet/SSH service. For details, see How to Start/Stop the FTP, SFTP, and Telnet Servicesand How to Enable and Disable the FTP/Telnet Authority of user root on Solaris OS and How to Start/Stop the SSH Service.

4. After logging in to the OS as the root user, install the OS patch. Otherwise, the U2000 software cannot be installed. For details about the method ofinstalling the OS patch, see Installing the Solaris OS Patches.



1.12.3 Installing the Solaris OS PatchesThis topic describes how to install the Solaris OS patches. To ensure the reliable system performance, the sparc_patch_20.0.0 patch must be installedimmediately after the Solaris OS is installed.

Prerequisites

The installation package for Solaris 10 OS patches is on-hand. The installation package is U2000version_server_ospatch_solaris_SPARC.tar. Orinstallation DVD: U2000version_server_patch_solaris_SPARC_dvd3.

The system allows user root to log in remotely and use the SFTP tool.


Context

NOTICE:



OS patches must be installed in the single-user mode. Otherwise, the OS will crash.When the OS patch is installed in single-user mode, do not power off the server, run the stop /SYS command to forcibly shut down the server, or runthe reboot command to forcibly restart the server. Otherwise, the OS may crack down.You cannot log in to the OS remotely to perform any operation after you switch to the single-user mode.Before performing the following steps, ensure that you can perform operations on the workstation remotely by using the control card, use the KVM inthe telecommunications room to connect to the server, or use serial ports to connect to the workstation.Do not login to controller when installing the OS patch. Otherwise, the patch will fail to be installed.

Procedure

1. Upload the OS patch software package.

The installation software package must be uploaded to the /opt path of the server through SFTP. Run the tar xvfname_of_installation_software_package command to decompress the installation package. For details about how to use SFTP to uploadfiles, see How to Use the FileZilla to Transfer Files by SFTP.

Before you install the OS patches, please copy the software package Solaris10_sparc_patch_20.0.0.tar.gz from the DVDU2000version_server_patch_solaris_SPARC_dvd3 to a computer. Then, SFTP the software package to the /opt/patches/sun path of theserver in binary mode. If the /opt/patches/sun directory does not exist, create the directory and then uploadSolaris10_sparc_patch_20.0.0.tar.gz to this directory.

2. Log in to the system controller.

If the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 server is used, perform the following operations to display the system controller:






If the M4000/M5000 server is used, perform the following to display the system controller:




3. Optional: Perform the following operations to check whether the system controller of the server needs to be upgraded:

-> cd /HOST-> ls

T5220 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware 7.1.6.j 2008/11/2511:12.If sysfw_version shows that the version is 7.4.6.c or later, perform the next step. If sysfw_version shows that the version is earlier than7.4.6.c, you must upgrade the system controller. For details, see How to Upgrade the System Controller Firmware of the Netra T4-1/OracleT4-1/Oracle T4-2/T5220 Server.

Netra T4-1/Oracle T4-1/Oracle T4-2 server:View the sysfw_version information in the command output. For example, sysfw_version = Sun System Firmware 8.2.1.b 2012/08/0311:58.If sysfw_version shows that the version is 8.3.0 or later, perform the next step. If sysfw_version shows that the version is earlier than 8.3.0,you must upgrade the system controller. For details, see How to Upgrade the System Controller Firmware of the Netra T4-1/Oracle T4-1/Oracle T4-2/T5220 Server.

4. Change the prompt to #. For details, see How to Switch Between the Console, OK Prompt, and # Prompt.

5. Ensure that the sparc_patch_20.0.0 patch and the system patch do not conflict.Run the following command to check whether the IDR143236-01 patch exists:# showrev -p | grep IDR143236-01



If a command output is displayed, run the following command to delete the patch. If no command output is displayed, proceed with the next step.# patchrm IDR143236-01

6. Ensure that the disk partitioning of the system is correct.

a. Run the following command to check the disk partitioning of the system:# format

Partitioned disks and their serial numbers will be displayed.

b. Enter the serial number of a disk to be checked, such as 0, and press Enter. The format menu will be displayed.

c. Run the partition command and press Enter. The partition menu will be displayed.

d. Run the print command and press Enter. The disk partitioning information will be displayed.According to the displayed disk partitioning information, check whether the current disk partitioning of the system is consistent with thePlanning Disk Partitions. If they are inconsistent, reinstall the OS and then partition disks according to the disk partition plan.

NOTE:As the format command query result varies according to the disk partition scheme, the following uses only the information about the 2*300GB disk partition as anexample.

A message similar to the following will be displayed:Part Tag Flag Cylinders Size Blocks 0 root wm 2685 - 6040 20.00GB (3356/0/0) 41950000 1 swap wu 0 - 2684 16.00GB (2685/0/0) 33562500 2 backup wm 0 - 46872 279.38GB (46873/0/0) 585912500 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 46643 - 46653 67.14MB (11/0/0) 137500 5 unassigned wm 6041 - 41440 211.00GB (35400/0/0) 442500000 6 var wm 41441 - 46474 30.00GB (5034/0/0) 62925000 7 home wm 46475 - 46642 1.00GB (168/0/0) 2100000

NOTE:The Part column lists fragments. The Tag column lists the partitions. The Size column lists the partition sizes.

e. Run the quit command and press Enter to exit the partition menu.

f. Run the quit command and press Enter to exit the format menu.

7. Run the following commands to display the OK prompt:# sync;sync;sync;sync;# init 0

NOTE:About 5 to 10 minutes later, the OK prompt will be displayed.

8. Run the following commands to enter the single-user mode:ok boot -s

NOTE:About 5 to 10 minutes later, a message is displayed asking you to enter the password of the OS user root. Enter the password of the OS user root. The # prompt is displayedindicating that you have entered the single-user mode.

9. Run the following commands to mount on the file system:# mountall > /dev/null 2>&1

10. Run the following commands to decompress the Solaris10_sparc_patch_20.0.0.tar.gz file:# cd /opt/patches/sun# gzcat Solaris10_sparc_patch_20.0.0.tar.gz | tar xvf -

11. Run the following commands to switch to the path where the QuickSetup.sh file is stored and then run the QuickSetup.sh file:# cd /opt/patches/sun/sun# sh QuickSetup.sh

12. The system will start installing patches. The entire installation process takes about 120 minutes.The patch installation is complete if the following message is displayed:Success! <install_all_patches> OK!*************************************************************************Setting system parameters**************************************************************************************************************************************************Restart the operation system*************************************************************************Are you sure to restart the operation system right now?<y/n>

NOTE:During installation of a Solaris patch, the following error message will be displayed but not impact the installation.

ERROR: The following patches were not able to be installed: 118705-02 - Synopsis: SunOS 5.10: XVR-1000 GFB Graphics Patch 118706-01 - Synopsis: SunOS 5.10: Creator and Creator3D: FFB Graphics Patch



...For more installation messages refer to the installation logfile: /var/sadm/install_data/Solaris_10_Extra_log

13. Enter y and press Enter, restart the OS manually.

NOTE:If the OS does not automatically restart because this step is not performed, restart the OS manually. For commands used to restart the Solaris OS, see Getting Started.

14. After the system restarts, log in to the OS as user root.

Follow-up Procedure



If the Solaris version is Solaris 10 8/11 if the following message is displayed. The OS and patches are successfully installed. Otherwise, use a correctinstallation DVD-ROM to reinstall the OS.


A message similar to the following will be displayed:5.10 Generic_150400-11If the core patch version is 5.10 Generic_150400-11, the OS and the sparc_patch_20.0.0 patch have been installed. If another version is displayed,install the OS patch. For details, see Installing the Solaris OS Patches.

3. Run the following command to verify that the system character set is correct:# locale -a


4. Ensure that the expect plug-in was installed on the server.

a. Log in to the server OS as user root.

b. Run the following command to verify that the expect plug-in has been installed:# which expect

If the expect plug-in installation path is displayed. The following is an example path:/usr/bin/expectThe expect plug-in has been installed and you do not need to run the autoinstall.sh script.

If the expect plug-in installation path is not displayed, run the autoinstall.sh script to install the expect plug-in.

i. Run the following commands to go to the installation path of the Solaris patch and decompress the expect.tar.gz file:# cd /opt/patches/expect# gzcat expect.tar.gz | tar xvf -

ii. Run the following commands to install the expect plug-in:# ./autoinstall.sh

5. If the patches are successfully installed, perform the following operations to delete the patch package to free up disk space:

a. Run the following commands to delete the OS patch package:# cd /opt# rm U2000version_server_ospatch_solaris_SPARC.tar

b. Run the following command to delete the OS patch path:# rm -rf /opt/patches


1.13 Planning Disk PartitionsThis topic describes the disk partitioning scheme that is determined according to the sizes and quantities of the server hard disks.

Specify the disk partitioning plan before manually installing the OS. This part can be skipped if the OS is installed with the quick installation DVD because theinstallation software automatically partitions disks according to the disk size.

NOTICE:

The second slice (overlap) represents the total capacity of the hard disk. Do not change it during the partitioning process. Otherwise, the OS may not



function properly.Partition 3 and partition 4 are reserved for disk mirroring. During the partitioning process, do not enter the name or size of the partition.The following table lists only the slices for partitioning. In the case of the slices that do not need to be partitioned, you do not need to enter theassociated name or size during the partitioning process. For example, in the case of 2 x 73 GB disks, do not enter partition names /usr and /var in thepartitioning process.

The following section provides example disk partitioning schemes for the primary and secondary sites.

If a server is equipped with two hard disks, the first hard disk must be partitioned regardless of whether a disk array is connected. The secondhard disk does not require partitioning because it serves as a mirror disk for the first hard disk. Table 1 and Table 2 show the partitioningscheme for the first hard disk of a two-disk server.

Table 1 Partitioning scheme for a two-disk server without any disk arrayHard Disk Fragment Partition 2 x 600 GB Hard Disk

(MB)2 x 300 GB Hard Disk(MB)

2 x 146 GB Hard Disk(MB)


First harddisk

0 / 50000 20000 12000 15000

1 swap 32000 16000 8000 6000

5 /opt 380000 120000 65000 29000

6 /var 20000 20000 8000 The /var partition is notrequired.

7 /export/home 20000 1000 1000 The /export/homepartition is not required.

Table 2 Partitioning scheme for a two-disk server with a disk arrayHard Disk Fragment Partition 2 x 600 GB Hard Disk




First harddisk

0 / 50000 30000 30000 15000

1 swap 32000 16000 16000 16000

5 /opt 400000 172000 30000 20000

6 /var 50000 30000 30000 15000

7 /export/home 20000 30000 29000 1000

If a server is equipped with four hard disks and is not connected to any disk array, only the first hard disk needs to be partitioned. The thirdand fourth hard disks do not require partitioning because they serve as mirror disks for the first and second hard disks. Table 3 shows thepartitioning scheme for the first hard disk of a four-disk server when the server is not connected to any disk array.

Table 3 Partitioning scheme for a four-disk server without any disk arrayHardDisk

Fragment Partition 4 x 600 GB Hard Disk(MB)




First harddisk

0 / 100000 50000 12000 15000

1 swap 32000 16000 8000 6000

5 /opt 300000 152000 104000 46000

6 /var 50000 50000 10000 The /var partition is notrequired.

7 /export/home 50000 10000 1000 The /export/homepartition is not required.

If a server is equipped with four hard disks and is connected to a disk array, the first and second hard disks need to be partitioned. The thirdand fourth hard disks do not require partitioning because they serve as mirror disks for the first and second hard disks. Table 4 shows thepartitioning scheme for the first and second hard disks of a four-disk server when the server is connected to a disk array.

Table 4 Partitioning scheme for a four-disk server with a disk arrayHardDisk

Fragment Partition 4 x 600 GB Hard Disk(MB)




First harddisk

0 / 300000 132000 50000 20000

1 swap 32000 16000 16000 16000

6 /var 100000 100000 40000 20000

7 /export/home 100000 30000 29000 11000

Secondhard disk

5 /opt 600000 278000 135000 67000

If a server is equipped with six hard disks and is not connected to any disk array, only the first and second hard disks need to be partitioned.The fourth, fifth, and sixth hard disks do not require partitioning because they serve as mirror disks for the first, second, and third hard disks.



Table 5 shows the partitioning scheme for the first and second hard disks of a six-disk server when the server is not connected to any diskarray.

Table 5 Partitioning scheme for a six-disk server without any disk arrayHard Disk Fragment Partition 6 x 600 GB Hard Disk




First hard disk 0 / 100000 50000 20000 12000

1 swap 32000 16000 16000 16000

5 /opt/backup 200000 142000 77000 18000

6 /var 120000 50000 20000 20000

7 /export/home 100000 20000 2000 1000

Second harddisk

5 /opt 550000 278000 135000 67000

If a server is equipped with six hard disks and is connected to a disk array, the first, second, and third hard disks need to be partitioned. Thefourth, fifth, and sixth hard disks do not require partitioning because they serve as mirror disks for the first, second, and third hard disks.Table 6 shows the partitioning scheme for the first, second, and third hard disks of a six-disk server when the server is connected to a diskarray.

Table 6 Partitioning scheme for a six-disk server with a disk arrayHard Disk Fragment Partition 6 x 600 GB Hard Disk




First hard disk 0 / 400000 162000 79000 21000

1 swap 32000 16000 16000 16000

6 /var 120000 100000 40000 30000

Second harddisk

5 /opt 550000 278000 135000 67000

Third hard disk 7 /export/home 550000 278000 135000 67000


1.14 Configuring Disk ArraysThis topic describes how to configure the OceanStor S3900, OceanStor S2600, OceanStor S3100, and StorageTek 2540 disk arrays.

Configuring the OceanStor S2600 Disk Array by Using the ISMThis topic describes how to configure the OceanStor S2600 disk array using the ISM.

Configuring the OceanStor S3900 Disk Array by Using the ISMThis topic describes how to configure the OceanStor S3900 disk array using the ISM.

Configuring the StorageTek 2540 Disk Array Through the Web BrowserThis topic describes how to configure the StorageTek 2540 disk array through the Web browser.

Configuring the OceanStor S3100 Disk ArrayThis topic describes how to configure the OceanStor S3100 disk array.


1.14.1 Configuring the OceanStor S2600 Disk Array by Using the ISMThis topic describes how to configure the OceanStor S2600 disk array using the ISM.

Prerequisites

The IP addresses for both controllers of the OceanStor S2600 disk array are configured. For details about how to set and view the IP addresses forcontrollers of the OceanStor S2600, see Setting the SC IP Address for the OceanStor S2600 Disk Array.


The Window management terminal must communicate properly with the disk array controller.

Users are logged in to the ISM from the Windows management terminal by using Internet Explorer 6.0, Internet Explorer 7.0, or Internet Explorer8.0.



Context

NOTE:The ISM software will lock up if an operation is not performed within 10 minutes after login. Enter the password again to log in if lock up occurs.

You need to respectively configure the disk arrays on the primary site and secondary site. The following takes the configuration of the disk array on the primary site as an example.

The following table shows the configuration requirements on the OceanStor S2600 disk array.

NOTICE:The following requirements are for the OceanStor S2600 (6 x 300 GB) disk arrays only. A OceanStor S2600 disk array (6 x 300 GB) is equipped with six harddisks, each of which is 300 GB in size. If the selected disk arrays are not the OceanStor S2600 disk arrays (6 x 300 GB), contact Huawei engineers for detailsabout how to configure the disk arrays.

Configure Item Settings

Hot-spare disk The sixth disk is designated as the global hot-spare disk.

Host group and host Set the host group name to HostGroup001.Set the host name to . For the primary site, the host name is set to Primaster; for the secondary site, the host name is set to Secmaster.

RAID group Set the RAID group name to RAID001.Set the RAID Level to RAID5.Set the disk type to SAS.The first five disks serve as the RAID group.

LUN Configure one LUN as follows:LUN information

Name: LUN001Capacity: 1000 GBStripe unit size: 32 KBHome controller: controller A

Cache strategyPrefetch strategy: intelligentWrite strategy: write back (mirroring)

Mapping modeMapping object: host group name HostGroup001

Port Set the type to FC.Set the name associated with the first identifier to port1.Set the name associated with the second identifier to port2.

Procedure

1. Log in to the ISM.

a. Open the Internet Explorer on the Windows management terminal.

b. Enter https://XXX.XXX.XXX.XXX (more secure, recommended) or http://XXX.XXX.XXX.XXX in the address bar of the InternetExplorer (where XXX.XXX.XXX.XXX indicates the IP address of the management network port of the storage array controller). Such ashttps://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 witheach other. Check the network connection.

The system will navigate to the default login window of the ISM, as shown in the following figure.



c. Click Click Here to Launch OceanStor ISM. The system will check whether the ISM is installed on the Windows managementterminal.

NOTICE:

Before installing the ISM, install the Java runtime environment (JRE). The JRE version must be 1.5.0 or later (excluding version1.5.0.16). In the CLI, run the java -version command to view the JRE version. If the JRE is not installed, click Please SetupJRE.Do not use JRE 1.5.0.16. Downloading the ISM may fail due to the bugs in JRE 1.5.0.16.

If the ISM is not installed on the Windows management terminal, the system will automatically download and install the ISM by means ofthe Java web start (JWS). If the ISM is installed on the Windows management terminal, the system will automatically check the softwareversion. If the version of the ISM is not the latest version, the system will automatically upgrade the software to the latest version.

d. In the Warning - Security dialog box, select Always trust content from this publisher and click Run.

e. Decide whether or not to create an ISM shortcut on the desktop and in the Start menu.The system will open the login window of the ISM, as shown in the following figure.

f. Select the required language from the Language drop-down list. Then, enter the user name in User Name and the user password inPassword.

NOTE:A disk array can be discovered only when the entered user name and password are the same as those of the disk array.The default user name for logging in to the ISM is admin and the login password is the one set for 2.g.

g. Click Login to access the Welcome window, as shown in the following figure:



2. Discover disk arrays.

a. In the Welcome window of the ISM, click Discover array.The Discover array dialog box will be displayed, as shown in the following figure.

b. Select a mode for discovering disk arrays according to the conditions at your site. Table 1 describes the parameters for discovering diskarrays.

Table 1 Parameters for discovering disk arraysParameter Description

Specify IP Address Indicates that disk arrays are discovered according to the IP address of the management network port on thespecified disk array.When you specify the IP address, the first field on the left ranges from 1 to 223 (except 127), the last fieldranges from 1 to 254, and the other fields range from 0 to 255.

Specify IP Address Range Indicates that disk arrays are discovered according to the IP address segment of the management network porton the specified disk array. Start IP Address and End IP Address indicate the start and end IP addresses ofdisk 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, andthe other fields range from 0 to 255.The start IP address must be smaller than or equal to the end IP address.

Same Subnet Indicates that the discovery range is the IP subnet segment of the ISM client. This mode is the defaultdiscovery mode of the system.

c. Click OK. After disk arrays are discovered, the Info dialog box will be displayed, prompting an operation success.

d. Click OK. The Warning dialog box will be displayed.



3. Initialize the configuration.

a. In the Warning dialog box, click OK to initialize the disk array.The Initial Configuration dialog box will be displayed, as shown in the following figure.

b. Select the disk array to be configured and click Initial Configuration. The Initial Configuration Wizard: Welcome dialog box will bedisplayed.

c. Click Next. The Initial Configuration Wizard: Modify Array dialog box will be displayed.



d. Enter the name of the disk array in the Name text box and the location information in the Location text box. Table 2 describes theparameters for modifying a disk array.

Table 2 Parameters for modifying a disk arrayParameter Description

Name Specifies the name of the OceanStor S2600 disk array to be configured. When setting this parameter, notethat:

This parameter contains only the characters and numerals in DBC case, underscores (_), en-dashsymbols (-), 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 S2600 disk array to be configured. When setting this parameter, notethat:

This parameter contains only the characters and numerals in DBC case, underscores (_), en-dashsymbols (-), and simplified Chinese characters.This parameter consists of 1 to 32 characters. A Chinese character counts for two DBC characters.

e. Click Next. The Initial Configuration Wizard: Modify Array Clock dialog box will be displayed.

f. Select the required date and time, and then click Next. The Initial Configuration Wizard: Modify User Password dialog box will bedisplayed.



g. Change the login password of the user. Table 3 describes the parameters for changing the user password.

Table 3 Parameters for changing the user passwordParameter Description

Old Password Specifies the original password. The default password is 123456.

New Password Specifies the new password. It ranges from 6 to 16 characters.

Confirm Password Confirms the new password. When setting this parameter, pay attention to the following points:This parameter ranges from 6 to 16 characters.This parameter value must be the same as the value of New Password.

h. Click Next. The Initial Configuration Wizard: Modify FC Host Port dialog box will be displayed.

NOTE:Click Modify Speed if the port rate needs to be changed. The default rate of an online port is 4 Gbit/s.

i. Click Finish to complete the initial configuration.

j. Click Close to exit.

4. Configure the hot-spare disk.

a. Click the Physical View tab in the navigation tree, and then select the OceanStor S2600 disk array to be configured.

b. Choose Configuration > Hot-Spare Disk Management from the main menu. The Hot-Spare Disk Management dialog box will bedisplayed.



c. Select disk location (00,05) from the free disk list and click the third button ( ) in the middle portion of the dialog box to add theselected disk to the hot spare disk list.



d. Click OK to close the Hot-Spare Disk Management dialog box. Click OK in the Warning dialog box. Then, click OK in the Infodialog box.

5. Create a host group and host.

a. Choose Logical View from the navigation tree and select the OceanStor S2600 disk array to be configured.

b. Choose Configuration > Create Host Group from the main menu. The Create Host Group dialog box will be displayed.

c. Select Solaris, and then click OK.The Info dialog box is displayed indicating that the operation was completed.

NOTE:In this step, the selected OS corresponds to the OS of the server connected to the disk array.

d. Click OK to complete creating the host group.

e. Choose the host group from the navigation tree, and then choose Configuration > Create Host from the main menu. The Create Hostdialog box will be displayed.

f. Enter the host name and click OK to continue.

NOTE:It is recommended to enter the host name of the server connected to the disk array so that the host name is easy to remember.

The Info dialog box will be displayed indicating that the operation was completed.

g. Click OK to complete creating the host.

6. Create a RAID group.

a. Choose Logical View from the navigation tree and select the OceanStor S2600 disk array to be configured.

b. Choose Configuration > Create RAID Group from the main menu. In the Create RAID Group dialog box, modify the settings, asshown in the following figure.



c. Click OK. The Info dialog box will be displayed indicating that the operation was completed.

d. Click OK. Creation of the RAID group is completed.

7. Create Lun001.

a. Click the Logical View tab in the navigation tree and select the RAID group where the new Lun001 locates.

b. Choose Configuration > Create LUN from the main menu. The Create LUN Step 5-1: RAID Group Information dialog box will bedisplayed.

c. Click Next. The Create LUN Step 5-2: Type LUN Information dialog box will be displayed.Configure the settings as shown in the following figure.

NOTICE:Ensure that the LUN size is set to 1000 GB. If the LUN size is larger than 1000 GB, an OS identification error occurs.



d. Click Next. The Create LUN Step 5-3: Select Cache Strategy dialog box will be displayed.Configure the settings as shown in the following figure.

e. Click Next. The Create LUN Step 5-4: Select Mapping Mode dialog box will be displayed.Configure the settings as shown in the following figure.



f. Click Next. The Create LUN Step 5-5: Confirm dialog box will be displayed.Configure the settings as shown in the following figure.

g. Click Finish. The Info dialog box will be displayed indicating that the operation was completed.

h. Click OK. Creation of Lun001 is complete.

8. Add a port.

a. Choose Host from the navigation tree, and then choose Configuration > Host Port Management from the main menu. The PortManagement dialog box will be displayed.



b. Click Add. The Add Port dialog box will be displayed.

c. Select the first available option from the WWN drop-down list, enter port1 in Name, and then click Apply. In the dialog box that will bedisplayed, click OK.

d. Click Add again. The Add Port dialog box will be displayed.

e. Enter port2 in the Name text box, and click OK. In the dialog box that will be displayed, click OK.

NOTE:One WWN maps one physical port. For example, if two physical ports are available, there are only two WWNs. If a WWN has been selected for port 1, select thedefault WWN for port 2.

9. Check the connection of the fiber card.


b. Run the following command to check the connection status of the port on the fiber card:# luxadm -e portThe following message will be displayed:/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0:devctl CONNECTED/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0:devctl CONNECTED

NOTE:If the fiber card is not in the CONNECTED 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.

c. Run the following commands to restart the OS of the server and refresh the disk status:# sync;sync;sync;sync# shutdown -y -g0 -i6

d. Run the following command to scan the LUN that maps the OceanStor S2600 disk array:# formatThe following message will be displayed:



Searching for disks...done


AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SEAGATE-ST973402SSUN72G-0400 cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c1t2200662233556653d0 <HUAWEI-S2600-1 cyl 19198 alt 2 hd 64 sec 256> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0/ssd@w2200662233556653,0 3. c2t2210662233556653d0 <HUAWEI-S2600-1 cyl 19198 alt 2 hd 64 sec 256> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0/ssd@w2210662233556653,0Specify disk (enter its number):

NOTE:The displayed disk size varies according to the actual size of the disk.The disk identified with < HUAWEI-S2600-1 .... > indicates the LUN that maps the OceanStor S2600 disk array.The scanned number of disks is the product of: the number of local disks, the number of LUNs that map the OceanStor S2600 disk array, and the numberof fiber paths. After the MPxIO multipathing is enabled, the number of disks scanned by the format command is equal to the number of LUNs that mapthe OceanStor S2600 disk array.If the disk that maps the OceanStor S3900 has been located, press CTRL+C to stop the scanning.If the disks that map the OceanStor S2600 disk array fail to be scanned, press CTRL+C to stop the scanning, run the devfsadm -C command first and theformat command to scan the required disks. If the disks still cannot be scanned, ensure that the fiber is properly connected.

Parent topic: Configuring Disk Arrays

1.14.2 Configuring the OceanStor S3900 Disk Array by Using the ISMThis topic describes how to configure the OceanStor S3900 disk array using the ISM.

Prerequisites

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 forcontrollers of the OceanStor S3900, see Setting the SC IP Address for the OceanStor S3900 Disk Array.


The Window management terminal must communicate properly with the disk array controller.

Users are logged in to the ISM from the Windows management terminal by using Internet Explorer 6.0, Internet Explorer 7.0, Internet Explorer 8.0,or Internet Explorer 9.0.

Context

NOTE:The ISM software will lock up if an operation is not performed within 10 minutes after login. Enter the password again to log in if lock up occurs.

You need to respectively configure the disk arrays on the primary site and secondary site. The following takes the configuration of the disk array on the primary site as an example.

The following table shows the configuration requirements on the OceanStor S3900 disk array.

NOTICE:If the selected disk arrays are not the OceanStor S3900 disk arrays (12x600 GB), contact Huawei engineers for details about how to configure the disk arrays.


Hot-spare disk The sixth disks act as hot backup disks.

Host group and host Set the host group name to HostGroup001.For the primary site, the host name is set to Primaster; for the secondary site, the host name is set to Secmaster.

RAID group Set the RAID group name to RAID001.Set the RAID Level to RAID10.Set the disk type to SAS.The first ten disks serve as the RAID group.

LUN Configure one LUN as follows:LUN information

Name: LUN001Capacity: 1000 GBStripe unit size: 32 KBHome controller: controller A

Cache strategyPrefetch strategy: intelligent

Write strategy: write back (mirroring)



Mapping modeMapping object: host group name HostGroup001

Port Set the type to FC.Set the name associated with the first identifier to port1.Set the name associated with the second identifier to port2.

Procedure

1. Log in to the ISM.

a. Open the Internet Explorer on the Windows management terminal.

b. Enter https://XXX.XXX.XXX.XXX (more secure, recommended) or http://XXX.XXX.XXX.XXX in the address bar of the InternetExplorer (where XXX.XXX.XXX.XXX indicates the IP address of the management network port of the storage array controller). Such ashttps://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 witheach other. Check the network connection.

The system will navigate to the default login window of the ISM, as shown in the following figure.

c. Click Click Here to Launch OceanStor ISM. The system will check whether the ISM is installed on the Windows managementterminal.

NOTICE:Before installing the ISM, install the Java runtime environment (JRE). The JRE version must be 1.6.0 or later (excluding version1.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 ofthe Java web start (JWS). If the ISM is installed on the Windows management terminal, the system will automatically check the softwareversion. If the version of the ISM is not the latest version, the system will automatically upgrade the software to the latest version.

d. In the Warning - Security dialog box, select Always trust content from this publisher and click Run.

2. Discover disk arrays.

a. In the Welcome window of the ISM, click Discover array. The Discover array dialog box will be displayed, as shown in the followingfigure.



b. Select a mode for discovering disk arrays according to the conditions at your site. Table 1 describes the parameters for discovering diskarrays.

Table 1 Parameters for discovering disk arraysParameter Description

Authentication The associated disk arrays can be found only when the entered user name and password are the same as those of the diskarrays.

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.

Authentication Mode Select a desired authentication mode. Choose Local Device from the drop-down list.

Device Type Select a desired device type. Choose Storage Unit from the drop-down list.

Discovery Modes Indicates that the discovery range is the IP address subnet segments on which the ISM client resides. The mode is bydefault selected.

Specify IP address Indicates that disk arrays are discovered according to the IP address of the management network port on the specified diskarray.When you specify the IP address, the first field on the left ranges from 1 to 223 (except 127), the last field ranges from 1to 254, and the other fields range from 0 to 255.

Specify IP Segment Indicates that disk arrays are discovered according to the IP address segment of the management network port on thespecified disk array. Start IP Address and End IP Address indicate the start and end IP addresses of disk arrays to bediscovered. 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 otherfields range from 0 to 255.The start IP address must be smaller than or equal to the end IP address.

Local sub-network Indicates that the discovery range is the IP subnet segment of the ISM client. This mode is the default discovery mode ofthe system.

c. Click OK. After the system successfully discovers storage arrays, the message Discover device succeed. is displayed on Task Manager.



3. Initialize configurations.

a. In the left -hand navigation tree, click the Assistant tab for the current device to perform initialize configurations.Display the initialization page.

b. Click Initial Configuration to initialize disk arrays.The Initial Configuration dialog box is displayed.

c. In the Device Basic Information text box, enter the desired device name. In the Device Name text box, enter the desired position andchange the login password. Table 2 shows the parameter description.

Table 2 Parameters for modifying a disk arrayParameter Description

Device Name Specifies the name 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 (-), andsimplified 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 (-), andsimplified Chinese characters.This parameter consists of 1 to 32 characters. A Chinese character counts for two DBC characters.

Old Password Specifies the original password.

NOTE:The default user name and password of the system administrator are admin and [email protected] 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 charactersare digits, letters, and special characters. Remember to change passwords regularly.

New Password Specifies the new password. It ranges from 6 to 16 characters.

Confirm Password Confirms the new password. When setting this parameter, pay attention to the following points:This parameter ranges from 6 to 16 characters.This parameter value must be the same as the value of New Password.

d. Click Next. The Device Time Management dialog box is displayed. Table 3 shows the parameter description.

Table 3 Description about device time management parametersParameter Description

Synchronize ClientTime

Specifies that the time or time zone of the current client has been synchronized to the device side. Ensure that timesettings are correct before performing synchronization.

NTP Automaticsynchronizing

Specifies that the time settings on the NTP server are automatically synchronized to the device side. Note that Server IPaddress and Synch Schedule(number of hours) must be set.

Manual Modification Specifies a manual modification of the time and time zone of the device. Click Modify. In the Modify Time dialog box,set the time and time zone of the device.

Not Modify DeviceTime

Specifies that the current device or time zone is not modified.

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



f. Click Next to access the Event Notification dialog box. By default, no settings are performed. To perform settings, select the Enablecheck box. Table 4 shows the description about all the associated parameters. Click Apply.

Table 4 Description about event notification parametersParameter Description

Email Notification The following parameters must be set if the notification is sent through emails.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 asemicolon to separate them.

SMS Notification The following parameters must be set if notifications are sent through SMS:



Level settings: Select the level at which users can receive fault 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 asemicolon to separate them.

System StatusNotification

The notifications are sent based on the system status.

NOTE:This parameter is available only when the configurations for email notification and SMS notification are correct.

Syslog Notification The following parameters must be set if notifications are sent through syslogs:Level settings: Select the level at which users can receive fault information.Receive IP address: Specifies the IP address for receiving fault information. You can add multiple IP addressesand use the semicolon to separate them.

g. Click Next to access the License Management dialog box. No license needs to be selected. Click Finish to complete systeminitialization.

4. Assign storage space.

a. Click the All Devices tab in the navigation tree. Select OceanStor S3900 to be configured.

b. Click the Assistant tab in the navigation tree. Click Allocate Storage Space. The Allocate Storage Space Wizard dialog box.

c. Select a value from the Block Storage Pool Type drop-down list in Select Block Storage Pool.

d. Click Create. The Create RAID Group dialog box is displayed. Table 5 shows the description about all the associated parameters. Afterthe parameter settings are complete, click OK. In the dialog box that is displayed, click OK.



Table 5 Description about parameters for creating a RAID groupParameter Description

Name Specifies the name of a RAID. The default value is RAID001.

Disk Type Specifies the type of a disk. The default value is SAS.

Level The default value is RAID 10.

Select Disks In the area, set Sub-Group Disks and Available Disks.

Sub-Group Disks Specifies the number of sub-hard disks to be configured. The default value is 2.

Manual Set this parameter to Manual to select all hard disks.

i. After all configurations are performed based on Table 5, click OK.

ii. In the Information dialog box, click OK.

iii. In the dialog box indicating successful creation, click Finish as prompted.

e. Click Next to access the Create LUN dialog box. Table 6 shows the description about all the associated parameters.



Table 6 Description about parameters for creating a LUNParameter Description

Name Specifies the name of the LUN to be configured. The default value is LUN001.

Number Specifies the number of LUNs to be configured. Set this parameter to 1.

Capacity Specifies the capacity of the LUN to be configured. Set this parameter to 1000GB.

Stripe Depth (KB) The default value is 64 KB. Set this parameter to 32 KB.

Owning Controller Specifies the controller to which the LUN to be configured belongs. Set this parameter to Controller A.

f. Click Next to access the Mapping dialog box. Select the mapping host.

i. Click Create Host Group. The default host group name is HostGroup001. Click OK.

ii. Click Create Host. Select HostGroup001 as the host group. Keep the default host name Host001 and set the OS type toSolaris.

iii. Click Next. Select already connected on the FC initiator.

iv. Click Next. No configuration is required.

v. Click Next. Confirm the parameter settings. Click Finish.

vi. After the configuration succeeds, click Close.

g. Select Host001. Click Next. In the Summary dialog box, confirm configurations.



h. Click Finish to view the execution result.

5. Check the connection of the fiber card.


b. Run the following command to check the connection status of the port on the fiber card:# luxadm -e portThe following message will be displayed:/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0:devctl CONNECTED/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0:devctl CONNECTED

NOTE:If the fiber card is not in the CONNECTED state, check and ensure the following aspect:


c. Run the following commands to restart the OS of the server and refresh the disk status:# sync;sync;sync;sync# shutdown -y -g0 -i6

d. Run the following command to scan the LUN that maps the OceanStor S3900 disk array:# formatThe following message will be displayed:Searching for disks...done




AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c1t2200662233556653d0 <HUAWEI-S3900-M200-2 cyl 63998 alt 2 hd 128 sec 256> /pci@2,600000/SUNW,qlc@0/fp@0,0/ssd@w20100022a10b0c81,0 3. c2t2210662233556653d0 <HUAWEI-S3900-M200-2 cyl 63998 alt 2 hd 128 sec 256> /pci@3,700000/SUNW,qlc@0/fp@0,0/ssd@w20000022a10b0c81,0Specify disk (enter its number):

NOTE:The displayed disk size varies according to the actual size of the disk.The disk identified with < HUAWEI-S3900- .... > indicates the LUN that maps the OceanStor S3900 disk array.The scanned number of disks is the product of: the number of local disks, the number of LUNs that map the OceanStor S3900 disk array, and the numberof fiber paths. After the MPxIO multipathing is enabled, the number of disks scanned by the format command is equal to the number of LUNs that mapthe OceanStor S3900 disk array.If the disk that maps the OceanStor S3900 has been located, press CTRL+C to stop the scanning.If the disks that map the OceanStor S3900 disk array fail to be scanned, press CTRL+C to stop the scanning, run the devfsadm -C command first and theformat command to scan the required disks. If the disks still cannot be scanned, ensure that the fiber is properly connected.


1.14.3 Configuring the StorageTek 2540 Disk Array Through the WebBrowser

This topic describes how to configure the StorageTek 2540 disk array through the Web browser.

Prerequisites

The cables between the server and the disk array are connected properly.

The IP addresses for both controllers of the StorageTek 2540 disk array are configured.

The OS of the server is installed.

The U2000version_server_patch_solaris_SPARC_dvd3 or installation package U2000version_server_ospatch_solaris_SPARC.tar are on-hand. TheDVD or installation package contains the StorageTek 2540 disk array manager.The installation software package is uploaded to the /tmp path of the server through SFTP. Run the command tar xvfname_of_installation_software_package to decompress the installation package.

Context

The /tmp path is the temporary system path. After restart, the system will automatically clear the files in the /tmp path.

NOTE:Configure disk arrays separately at the primary and secondary sites. The following uses the configuration of the disk array at the primary site as an example.

The following table describes the configuration requirements on the StorageTek 2540 disk array.


RAID group The first five disks serve as the RAID group named RAID5.

LUN Configure one LUN and name it disk1; set the capacity to 1000 GB.


Procedure

1. Install the StorageTek 2540 disk array manager CAM on the server.

a. Log in to the OS of the server as user root.

b. To navigate to the directory of the installation files, perform the following operations:

If the disk array manager was installed by using an installation DVD, perform the following operations:

i. Insert U2000version_server_patch_solaris_SPARC_dvd3 into the DVD-ROM drive.

ii. Run the following command to navigate to the /tmp path:# cd /tmp

iii. Run the following command to copy the files from the /cdrom/cdrom0/patches directory to the /tmp path:# cp -r /cdrom/cdrom0/patches /tmp



iv. Run the following command to navigate to the /tmp/patches/sun directory where the installation files are saved:# cd /tmp/patches/sun

If the disk array manager was installed by using an installation package, perform the following operations:

i. Run the following command to navigate to the /tmp path:# cd /tmp

ii. Run the following tar command to decompress the installation package:# tar xvf U2000version_server_ospatch_solaris_SPARC.tar

iii. Run the following command to navigate to the /tmp/patches/sun directory where the installation files are saved:# cd /tmp/patches/sun

c. Run the following command to decompress the CAM installation file:# gzcat host_sw_solaris_6.6.0.11.tar.gz | tar xf -

d. Run the following commands to install the CAM software:# cd /tmp/patches/sun/HostSoftwareCD_6.6.0.11# ./RunMe.bin -c

Follow the screen prompts and proceed with the installation of the StorageTek 2540 disk array manager.

NOTE:

During the installation, enter 1 and select I accept the terms of the license agreement in the license agreement window, and press Enter in the otherwindows.During the CAM installation, some OS patches may fail to be installed, but the failure does not affect the use of the CAM software; therefore, you canignore these occurrences.

e. Run the following commands to enable the Internet Explorer login rights of other IP addresses:# svccfg -s svc:/system/webconsole:console setprop options/local=false# svccfg -s svc:/system/webconsole setprop options/tcp_listen=true# svcadm restart svc:/system/webconsole

NOTE:Run the netstat -an | grep 6789 command to verify that the login rights of other IP addresses are enabled. Information similar to the following will be displayed ifrights are enabled. If no, run the preceding commands again. *.6789 *.* 0 0 49152 0 LISTEN

2. Start the disk array manager.

a. Log in to the OS of the Windows management terminal as an administrator.

b. Open the IE, enter the local IP address of the management terminal in the Address bar, and then press Enter. The IP address is in anhttps://127.0.0.1:6789/.

NOTE:You can also access the management terminal where the disk array manager is installed by using the IE on other Windows management terminals. In this scenario,enter the actual IP address of the management terminal where the disk array manager is installed.

c. The Security Alert dialog box is displayed. Click Yes.

d. In the login window, enter the user name and password, for example, root, and click Log In.

NOTE:If the security warning information is displayed, click Confirm.



3. Configure the StorageTek 2540 disk array by using the disk array manager.

a. On Java Web console, click Sun Storage Tek(TM) Common Array Manager in Storage.

b. In the Common Array Manager, choose General Configuration from the navigation tree to set the station information. Then, click Saveand Continue Setup.



c. Choose General Configuration > Auto Service Request (ASR) Setup from the navigation tree and click Decline in the Auto ServiceRequest (ASR) Setup window.

d. Choose Storage Systems from the navigation tree and click Register.



e. In the Register Storage System window, select Enter IP address or hostname, enter the IP address of disk array controller A in theaddress bar, and then click Next.

f. View the storage system list, select the system that you want to register right now, and click Finish.



g. The system will display a progress bar. After the registration is complete, click Close.

h. Under Storage Systems in the navigation tree, select the disk system to be configured and click Install Firmware Baseline.



i. In the Analyze and Install Array Firmware Baseline window, click Next.

j. Analyze the firmware of the storage system and click Next.

NOTE:If the components are not at the baseline (Health is displayed as Degraded), select Install baseline, All in Storage Systems (1).If the components are at the baseline (Health is displayed as OK), select Do not install baseline in Storage Systems (1).Options vary with CAM software versions. Select the appropriate option according to the conditions at your site.

k. Verify the array password and click Next.

l. View the current selection and click Finish to install the specified firmware. After the installation is complete, click Close.

m. Select the storage system to be set from the navigation tree and set the detailed information in Administration. Then, click Save.

NOTE:Set Array Hot-Spares to 1.Set Default Host Type to Solaris (with Veritas DMP or other).Use default values for other parameters.



n. In the storage system to be configured, choose unamed > Physical Device > Disks. Then, on the Disk Summary on Storage Systemunlabeled tab page, click the name of the last disk.

o. On the Disk Details tab page, click Assign Hot-Standby Disk. The Succeeded in operating the hot-standby disk message will bedisplayed.

p. In the storage system to be set, choose Physical Device > Disks from the navigation tree. In the Role column, ensure that the disk for hotbackup has been allocated.

NOTE:Repeat 3.n to 3.o to set and save the information again if a disk for hot backup has not been allocated.

q. Delete the default mapping. In the navigation tree on the left, choose Storage Systems > unnamed > Mappings. Select the existingmapping Access and click Delete.

r. In the storage system to be configured, choose Profiles and click New.

s. Configure the configuration file and click Confirm.

NOTE:Set Storage Profile to NMS_Profile.Set Raid Level to Raid5.Set Segment Size to 512KB.Set No. of Disks to 5.Set Disk Type to SAS.

t. In the storage system to be set, choose Pools from the navigation tree. In the windows that is displayed, click New.



u. Set the storage pool and click OK to complete the settings.

NOTE:Set Name to NMSPool.Set Storage Profile to NMS_Profile.

v. Create a volume. In the storage system to be set, choose Volumes from the navigation tree and click New.



w. Select Use Existing Storage Pool, select the storage pool NMSPool, and then click Next.

x. Set the storage characteristics. Specifically, select Storage Selected Automatically by CAM and click Next.



y. Configure the volume.

NOTE:Set the volume name to disk1.Set the number of volumes to be created to 1.Set the size of the volume to 1000 GB.Set the controller to Any.

NOTICE:Ensure that the LUN size is set to 1000 GB. If the LUN size is larger than 1000 GB, an OS identification error occurs.

z. Select mapping. Specifically, select Map to an Existing Host/Host Group or the Default Storage Domain and click Next.



aa. Select the host or host group. Specifically, select Default Storage Domain and click Next.

ab. Check the settings and click Finish.



ac. View the progress of the current job. Specifically, choose Jobs > Current Job to view the progress of the current job and wait until it iscompleted.

4. Update disk information.

a. Run the following command to view connections to the ports of the fiber cards:# luxadm -e port

The following message will be displayed:/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0:devctl CONNECTED/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0:devctl CONNECTED

NOTE:If the fiber card is not in the CONNECTED state, check and ensure the following items:


b. Run the following commands to update the disk information:# devfsadm -C# devfsadm

c. Run the following command to check the disk information:# formatThe following message will be displayed:



Searching for disks...done


AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SEAGATE-ST973402SSUN72G-0400 cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c3t2d0 <SUN-LCSM100_F-0670 cyl 38398 alt 2 hd 128 sec 64> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0/ssd@w202300a0b85a4d21,0 3. c3t2d1 <SUN-LCSM100_F-0670 cyl 38398 alt 2 hd 128 sec 64> /pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0/ssd@w202300a0b85a4d21,1Specify disk (enter its number):

NOTE:SUN-LCSM100_F indicates the new volumes that are configured for the StorageTek 2540 disk array.If two controllers are properly connected to the server, the information about the volumes of the two StorageTek 2540 disk arrays will be displayed.Otherwise, check the connections of the disk arrays and run the reboot -- -r command to restart the server.

5. Label the unlabeled disks.

a. Select the disk to be labeled.The following message will be displayed:selecting c1t600A0B80005A4D2100000E6D4AFB1E2Cd0[disk formatted]Disk not labeled. Label it now?

b. Enter y to label the disk.The following message will be displayed:FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quitformat>

c. Enter disk.The following message will be displayed:AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0 1. c0t1d0 <SEAGATE-ST973402SSUN72G-0400 cyl 14087 alt 2 hd 24 sec 424> /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0 2. c1t600A0B80005A4D2100000E6D4AFB1E2Cd0 <SUN-LCSM100_F-0670 cyl 38398 alt 2 hd 128 sec 64> /scsi_vhci/ssd@g600a0b80005a4d2100000e6d4afb1e2cSpecify disk (enter its number):

d. Repeat 5.a to 5.c for the other unlabeled disks.

e. Press Ctrl+D to exit.


1.14.4 Configuring the OceanStor S3100 Disk ArrayThis topic describes how to configure the OceanStor S3100 disk array.

Configuring the SC IP Address of the OceanStor S3100 Disk ArrayThis topic describes how to configure the SC IP address of the OceanStor S3100 disk array.

Using the Manager Suite to Configure the OceanStor S3100 Disk ArrayThis topic describes how to use the Manager Suite to configure the OceanStor S3100 disk array.




1.14.4.1 Configuring the SC IP Address of the OceanStor S3100 Disk ArrayThis topic describes how to configure the SC IP address of the OceanStor S3100 disk array.

Prerequisites



Context

Each disk array OceanStor S3100 has two controllers that need to be configured separately.

Procedure

1. Connect the computer and controller A of the disk array physically.Use a serial port cable (DB9-PS/2) to connect the serial port of the local controller to the serial port of the disk array (SERIAL MGT).Use an PS/2 connector at one end of the serial port cable to connect to the serial port of the disk array (SERIAL MGT) and a DB-9 connector at theother end of the cable to connect to the serial port of the computer (COM1 or COM2).

Figure 1 Connections between the controllers of the OceanStor S3100 disk array






Speed(baud): 9600

Data bits: 8

Stop bits: 1

Parity: None

Flow Control: None


e. Click Open.

3. Configure the IP address of the network interface of controller A of the disk array on the local console.

NOTE:One OceanStor S3100 disk array has two controllers. You need to configure them separately.

a. Send a break signal from the computer by pressing Ctrl+Pause Break.

b. Press ESC within five seconds according to the prompt to access the shell login window.

c. Enter infiniti as the password and press Enter. If a dialog box shown in the following figure is displayed, the login to the configurationshell of the controller succeeds.



d. At the prompt, enter netCfgShow and press Enter. The information about the configuration network interface of the controller that youhave logged in to is displayed.

e. At the prompt, enter netCfgSet.The following message will be displayed:

NOTE:There are three subcolumns in the CURRENT NETWORK CONFIGURATION column.

The first subcolumn displays the name of the information about this row.The second subcolumn displays the current values.The third subcolumn displays a flashing cursor.

f. Enter information about the network card to be modified at the flashing cursor, which includes the IP address, gateway, and subnet maskof the network card.

NOTE:Select a network interface of the controller for configuration according to the actual connection condition. The following takes the configuration of if0 asan example.If there is no special requirement, keep the default settings of the other network interface of the controller unchanged.If you press Enter, the current values in the second subcolumn remain unchanged. If you enter the desired characters and then press Enter, the values inthe second subcolumn are changed to the new values.If you need to restore a value to the default factory setting, enter ..if0 indicates to network interface 1 of the disk array; if1 indicates network interface 2 of the disk array. Generally, it is recommended that you use networkinterface 1. You need to set only IP Address if0, Subnet Mask if0, and Gateway IP Address rather than My Host Name, Server Host Name, Server IPAddress, Network Init Flags, User Name, and User Password.




NOTE:Here, Network Configuration successfully written to NVSRAM indicates that the modification is successful.

4. Disconnect the serial port cable from controller A.

a. On the computer, exit the PuTTY software.

b. Remove the serial port cable on the disk array.

5. Repeat Step 1 to Step 4 to configure the network port of controller B.

a. Establish a physical connection between the computer and controller B.



d. Disconnect the serial port from controller B.

Parent topic: Configuring the OceanStor S3100 Disk Array

1.14.4.2 Using the Manager Suite to Configure the OceanStor S3100 DiskArray

This topic describes how to use the Manager Suite to configure the OceanStor S3100 disk array.

Prerequisites

The cables between the server and the disk array are connected properly.

The IP addresses for both controllers of the OceanStor S3100 disk array are configured.

The operating system (OS) of the server is installed.

Before installing the Manager Suite, ensure that there is at least 140 MB of available disk space for full installation.

Context

NOTE:Configure disk arrays separately at the primary and secondary sites. The following uses the configuration of the disk array at the primary site as an example.

The following table describes the configuration requirements on the OceanStor S3100 disk array.


RAID group The first five disks serve as the RAID group named RAID5.

LUN Configure one LUN and name it disk1; set the capacity to 500 GB.


Procedure

1. Install the Manager Suite.

a. Log in to the server as user root.

b. Insert the OceanStor Manager Suite 9.19 for S3000/S6000 installation DVD or prepare the SMruntime-SOL.pkg, SMclient-SOL.pkg,and SMutil-SOL.pkg installation packages.



NOTE:Use SFTP to upload the installation packages to the /tmp directory on the server as the root user. For details, see How to Use the FileZilla to Transfer Files by SFTP.

c. In the terminal window, run the following command to go to the destination directory:

If the server model is Netra T4-1/Oracle T4-1/T5220/M4000/M5000, run the following command:# cd /cdrom/cdrom0/Solaris/native

If the server model is Oracle T4-2, run the following command:# cd /cdrom/cdrom1/Solaris/native

NOTE:When installing from the hard disk, run the following command to go to the destination directory:

# cd /tmp

d. Run the following commands to install the Manager Suite. Follow the screen prompts and determine the appropriate action specific to sitescenarios:# pkgadd -d /tmp/SMruntime-SOL.pkg SMruntime# pkgadd -d /tmp/SMutil-SOL.pkg SMutil# pkgadd -d /tmp/SMclient-SOL.pkg SMclient

Installation of the Manager Suite is complete.

e. Run the following commands to check the installation of the Manager Suite:# pkginfo -l SMruntime# pkginfo -l SMutil# pkginfo -l SMclient

The Manager Suite was successfully installed if the information about the corresponding installation package is displayed after eachcommand is run. Otherwise, perform the following to reinstall the Manager Suite:

i. Uninstall the Manager Suite.

a. Run the following command:# pkgrm SMutil

b. Enter y.

c. Run the following command:# pkgrm SMclient

d. Enter y.

e. Enter y.

f. Run the following command:# pkgrm SMruntime

g. Enter y.

ii. Reinstall the Manager Suite.

2. Log in to the server as user root through the GUI.

3. Use the Manager Suite to configure the OceanStor S3100 disk array.

a. In the terminal window, enter SMclient to start the Manager Suite.



b. Click . In the dialog box that is displayed, enter the IP addresses of controller A and controller B to log in to the local console.

NOTE:The IP addresses in the preceding figure are used as examples. Enter an appropriate IP address according to the conditions at your site. Before entering the IPaddresses, ensure that you can ping through the IP addresses. Enter the IP addresses and click Add to add the disk array to the Manager Suite.

c. Double-click the storage equipment. The storage equipment management window will be displayed.



d. Usually, a new disk array has disk RAID0. The system automatically creates disk RAID0 by using a hard disk. Disk RAID0 has a volumeof 0.01 GB. Right-click the volume group and choose Delete from the shortcut menu.



e. Enter yes and click OK to delete the volume group.

f. Right-click Total Unconfigured Capacity and choose Create Volume from the shortcut menu.



g. Click Next to open the dialog box for creating the volume group. Set the parameters as follows:

RAID level: RAID 5 (minimum 3 drives)

Drives selection choices: Manual-select drives to obtain volume group capacity



h. Select five disks from Unselection drives in the left pane and add them to Selection drives in the right pane, as shown in the followingfigure.

i. Click Calculate Capacity.

j. Click Next>. In the confirmation dialog box, click OK.

k. Set the volume as follows:



New volume capacity: 500 GB

Name (30 characters maximum): disk1

Advanced volume parameters: Use recommended settings

l. Click Next.

m. Click the Default mapping option button and set Host type (operating system) to Solaris.



n. Click Finish.The following dialog box will be displayed indicating that volume disk 1 has been created.

o. Click No.The S3100 - Completed (Create Volume) dialog box will be displayed.

p. Click OK.

q. Right-click the sixth disk and choose Hot Spare Coverage from the shortcut menu, as shown in the following figure.



r. Click the Manually assign individual drives option button, and click OK.Configuring the hot-spare disk was successful if a red cross is displayed below the hard disk icon.



s. Click the Mappings View tab.

t. In the Mapping start-up Help dialog box, click Close.

u. Optional: If there is a volume named Access in the right pane, right-click the volume and choose Remove Mapping from the shortcutmenu to delete the volume. The configuration is complete.



4. Configure the LUN that maps disk array S3100 on the server.

a. Check the connection of the HBA card.

i. Run the following command to check the connection of the port on the HBA card:# luxadm -e port

The following message will be displayed:/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1/fp@0,0:devctl CONNECTED/devices/pci@0,600000/pci@0/pci@8/pci@0,1/SUNW,qlc@1,1/fp@0,0:devctl CONNECTED

NOTE:

If the HBA card does not work in the connected state, check and ensure the following items:

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 HBA card.The indicator of the HBA card is functioning properly.

ii. Run the following commands to restart the OS of the server and refresh the disk status:# sync;sync;sync;sync# shutdown -y -g0 -i6

iii. Run the following command to scan the LUNs that map the S3100 disk array:# format

The following message will be displayed:Searching for disks...done


AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@0,0 1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@1,0 2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@2,0 3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@3,0 4. c2t5d0 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w200500a0b8423e19,0 5. c2t5d1 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w200500a0b8423e19,1 6. c3t1d0 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w200400a0b8423e19,0 7. c3t1d1 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w200400a0b8423e19,1Specify disk (enter its number):

NOTE:The displayed disk size varies according to the actual size of the disk.The disks identified with <ENGENIO-INF-01-00-0619 .... > are the LUNs that map the S3100 disk array.The scanned number of disks is the product of: the number of local disks, the number of LUNs that map the S3100 disk array, and the numberof fiber paths. After the MPxIO multipathing is enabled, the number of disks scanned by the format command is equal to the number ofLUNs that map the S3100 disk array.



If the disks that map the S3100 disk array fail to be scanned, run the devfsadm -C command first, and the format command to scan therequired disks. If the disks still cannot be scanned, ensure that the fiber is properly connected.Press Ctrl+D to exit.

5. Label the required disks.

a. Select the disk to be labeled.

NOTE:

The disk is not labeled if the message "Searching for disks...done" is displayed. In this case, enter the corresponding disk number. For example, enter 4 when thec2t5d0 disk needs to be labeled. The following uses the c2t5d0 disk as an example.c2t5d0: configured with capacity of 349.99GBc2t5d1: configured with capacity of 349.99GB

The following message will be displayed:Specify disk (enter its number): 4selecting c2t5d0[disk formatted]Disk not labeled. Label it now?

b. Enter y to label the disk.The following message will be displayed:FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quitformat>

c. Enter disk.The following message will be displayed:AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@0,0 1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@1,0 2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@2,0 3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0/pci@0/pci@2/scsi@0/sd@3,0 4. c2t5d0 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w200500a0b8423e19,0 5. c2t5d1 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w200500a0b8423e19,1 6. c3t1d0 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w200400a0b8423e19,0 7. c3t1d1 <ENGENIO-INF-01-00-0619 cyl 51198 alt 2 hd 128 sec 64> /pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w200400a0b8423e19,1Specify disk (enter its number):

d. Perform 5.a to 5.c to label the rest of the disks.

e. Press Ctrl+D to exit.

Parent topic: Configuring the OceanStor S3100 Disk Array

1.15 Glossary and AbbreviationsA

access control listA list of entities, together with their access rights, which are authorized to have access to a resource.

access control rightThe level of right granted to a user for his access to certain items.

ACLSee access control list

advanced telecom application environment



A platform that is used by the hardware of the N2510. To expand the system capacity smoothly, you only need to add certain boards to the shelf andneed not replace the server. This helps reduce the investments of the customer.

AISSee Alarm Indication Signal

AlarmA message reported when a fault is detected by a device or by the network management system during the process of polling devices. Each alarmcorresponds to a recovery alarm. After a recovery alarm is received, the status of the corresponding alarm changes to cleared.

alarm acknowledgementAn operation performed on an alarm. Through this operation, the status of an alarm is changed from unacknowledged to acknowledged, which indicatesthat the user starts handling the alarm. The process during which when an alarm is generated, the operator needs to acknowledge the alarm and take theright step to clear the alarm.

alarm correlation rule analyzingA process of analyzing the alarms that meet alarm correlation rules. If alarm 2 is generated within 5 seconds after alarm 1 is generated and meets thealarm correlation analysis rules, the EMS masks alarm 2 or improves its severity level according to the alarm correlation rules.

alarm delay timeThe 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 jitterscan be avoided by setting the delay time.

alarm indicationOn 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 indicatesthat 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 amajor 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 aboard indicates the current status of the board. (Metro)

Alarm Indication SignalA code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multipletransport layers. Note: See ITU-T Rec. G.707/Y.1322 for specific AIS signals.

alarm maskOn 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 alarminformation meeting the conditions.

alarm reporting to the EMS immediatelyOn a device, an alarm is reported to the EMS at once after the alarm is generated. On the EMS client, the corresponding alarm information is displayedon the alarm panel.

alarm severityThe significance of a change in system performance or events. According to ITU-T recommendations, an alarm can have one of the followingseverities:Critical, Major, Minor, Warning.

alarm statusThe 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 synchronizationWhen alarm synchronization is implemented, the EMS checks the alarm information in its database and on the NEs. If the alarm information on the twolocations is inconsistent, the alarm information on the NEs is synchronized to the EMS database to replace the original records.

ALC linkA piece of end-to-end configuration information, which exists in the equipment (single station) as an ALC link node. Through the ALC function of eachnode, it fulfils optical power control on the line that contains the link.

ARP ProxyWhen 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 inthe networking of layer 2 isolation.

Asynchronous Transfer ModeA data transfer technology based on cell, in which packets allocation relies on channel demand. It supports fast packet switching to achieve efficientutilization of network resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte header.

ATAESee advanced telecom application environment

ATMSee Asynchronous Transfer Mode

Authority and Domain Based ManagementThe function of the NMS for authority management. With this function, you can:

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

B

bandwidthA 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 lowestfrequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate.

BASEA kind of bus or plane used to load software, transmit alarms and maintain information exchange.

basic input/output systemA firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, andsystem setting information. The BIOS provides hardware setting and control functions for the computer.

BFDSee Bidirectional Forwarding Detection

Bidirectional Forwarding DetectionA simple Hello protocol, similar to the adjacent detection in the route protocol. Two systems periodically send BFD detection messages on the channelbetween 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 isfaulty. Under some conditions, the TX and RX rates between systems need to be negotiated to reduce traffic load.

BIOSSee basic input/output system

boardBoard refers to an electronic part that can be plugged in to provide new capability. It comprises chips and electronic components and these componentsare always on a flat and hard base and connected through conductive paths. A board provides ports for upstream connections or service provisioning.

BondBond: 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 technologyallows 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 oneMAC address. In this manner, a virtual NIC is formed. The bond technology supports two modes: double-live and primary/secondary. In double-livemode, after receiving request data from a remote server, the virtual NIC on the server determines data transmission based on an algorithm, improvingnetwork throughput and usability of the server. In primary/secondary mode, if an NIC does not function properly, services will be automatically switchedto the other NIC, ensuring service protection. The SUSE Linux OS supports the binding of NICs in primary/secondary mode.

C

C/SSee client/server software architecture

CARSee committed access rate

CAUSee Client Auto Update

CDESee Common Desktop Environment

CIRSee Committed Information Rate

clientA device that sends requests, receives responses, and obtains services from the server.

Client Auto UpdateThis 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 asthat of the server.

Client/ServerThe 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. Therequesting program is called a client. The program satisfying the request is called the server. It is usually easier to build client software than build theserver software.

client/server software architectureA message-based and modular software architecture that comprises servers and clients. Compared with the centralized, mainframe, and time sharingcomputing, the client/server software architecture improves the usability, flexibility, interoperability, and scalability. In this architecture, a client isdefined as the party that requires services and a server is defined as the party that provides services. The client/server architecture reduces network trafficby providing a query response rather than transferring all files.

clusterA 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 kindof equipment. In the interior of a cluster, the nodes share the load.

committed access rateA 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 outgoingpackets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined.

Committed Information Rate



The rate at which a frame relay network agrees to transfer information in normal conditions. Namely, it is the rate, measured in bit/s, at which the tokenis transferred to the leaky bucket.

Common Desktop EnvironmentThe Common Desktop Environment (CDE) is an integrated graphical user interface for open systems desktop computing. It delivers a single, standardgraphical 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 computersas easy to use as PCs, but with the added power of local and network resources available at the click of a mouse.

Common Object Request Broker ArchitectureA specification developed by the Object Management Group in 1992 in which pieces of programs (objects) communicate with other objects in otherprograms, even if the two programs are written in different programming languages and are running on different platforms. A program makes its requestfor 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. CORBAis designed to work in object-oriented environments. See also IIOP, object (definition 2), Object Management Group, object-oriented.

Common Object Request Broker ArchitectureA specification developed by the Object Management Group in 1992 in which pieces of programs (objects) communicate with other objects in otherprograms, even if the two programs are written in different programming languages and are running on different platforms. A program makes its requestfor 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. CORBAis designed to work in object-oriented environments. See also IIOP, object (definition 2), Object Management Group, object-oriented.

CORBASee Common Object Request Broker Architecture

CORBASee Common Object Request Broker Architecture

D

Data Communication ChannelData Communications Channel. The data channel that uses the D1-D12 bytes in the 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/sDCC-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 networkA communication network used in a TMN or between TMNs to support the data communication function.

data replication linkA link used for data replication between the production machine and redundancy machine. It is separated from the network of the primary links.

DCCSee Data Communication Channel

DCNSee data communication network

DDNSee digital data network

DelayAn average time taken by the service data to transmit across the network.

DGdisk group

DHCPSee Dynamic Host Configuration Protocol

digital data networkA high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and thecross multiplex technology.

disk mirroringA 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 orcorrupted, the mirror disks will contain a current, undamaged collection of the data from the original disk.

Dynamic Host Configuration ProtocolA client-server networking protocol. A DHCP server provides configuration 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

E1A European standard for high-speed data transmission at 2.048 Mbit/s. It provides 32 x 64 kbit/s channels.

ECCSee embedded control channel

embedded control channelA logical channel that uses a data communications channel (DCC) as its physical layer, to enable transmission of operation, administration, andmaintenance (OAM) information between NEs.



Equipment Serial NumberA 32-bit number assigned by the mobile station manufacturer, uniquely identifying the mobile station equipment.

ESNSee Equipment Serial Number

F

FabricA kind of bus/plane used to exchange system service data.

File Transfer ProtocolA member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTProles: one must be an FTP client and the other an FTP server.

FTPSee File Transfer Protocol

G

gatewayA device to connect two network segments which use different protocols. It is used to translate the data in the two network segments.

gateway network elementA network element that is used for communication between the NE application layer and the NM application layer

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

GMTSee Greenwich Mean Time

GNESee gateway network element

graphical user interfaceA visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen.

Greenwich Mean TimeThe mean solar time at the Royal Greenwich Observatory in Greenwich near London in England, which by convention is at 0 degrees geographiclongitude.

GUISee graphical user interface

H

HASee High Availability

HA systemSee high availability system

half-duplexA 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 AvailabilityThe ability of a system to continuously perform its functions during a long period, which may exceeds the suggested working time of the independentcomponents. You can obtain the high availability (HA) by using the error tolerance method. Based on learning cases one by one, you must also clearlyunderstand the limitations of the system that requires an HA ability and the degree to which the ability can reach.

high availability systemThe high availability system (HA) system indicates that two servers are adopted by a same computer. When the primary server is faulty, the secondaryserver provides the environment on which the software runs through the related technology.

History alarmThe confirmed alarms that have been saved in the memory and other external memories.

hostThe 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 alarge computer, server, workstation, PC, multiprocessor computer, and computer cluster system.

I

IANASee Internet assigned numbers authority

ICA



See independent computing architectureICMP

See Internet Control Message ProtocolIE

See Internet ExplorerIEEE

See Institute of Electrical and Electronics EngineersiMAP

See integrated management application platformindependent computing architecture

An architecture that logically separates application execution from user interfaces to transmit only keyboard actions, mouse responses, and screenupdates on the network.

Institute of Electrical and Electronics EngineersA society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEEfocuses on electrical, electronics, computer engineering, and science-related matters.

integrated management application platformN/A

International Standard OrganizationOne of two international standards bodies responsible for developing international data communications standards. International Organization forStandardization (ISO) works closely with the International Electro- technical Commission (IEC) to define standards of computing. They jointlypublished the ISO/IEC SQL-92 standard for SQL.

International Telecommunication Union Telecommunication StandardizationAn organization that establishes recommendations and coordinates the development of telecommunication standards for the entire world.

Internet assigned numbers authorityThe organization operated under the IAB. IANA delegates authority for IP address-space allocation and domain-name assignment to the NIC and otherorganizations. IANA also maintains a database of assigned protocol identifiers used in the TCP/IP suite, including autonomous system numbers.

Internet Control Message ProtocolA network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, itcan let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSIreference model, packet (definition 1).

Internet ExplorerMicrosoft's Web browsing software. Introduced in October 1995, the latest versions of Internet Explorer include many features that allow you tocustomize your experience on the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.

Internet ProtocolThe 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 asTCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791.

Internet Protocol Version 6A update version of IPv4. It is also called IP Next Generation (IPng). The specifications and standardizations provided by it are consistent with theInternet Engineering Task Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the Internet Protocol, designed as thesuccessor to IPv4. The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF).The differencebetween IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits.

inventoryA physical inventory in the U2000, that is, a physical resource such as a telecommunications room, rack, NE, subrack, board, subboard, port, opticalmodule, fiber/cable, fiber and cable pipe, link resource, interface resource, access service, ONU, or NE e-label that can be managed on the U2000, andthe relationship between resources.

IPSee Internet Protocol

IPv4The 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 networknumber, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, and the host number isused to address an individual host within the network or subnetwork. IPv4 addresses may also be represented using CIDR (Classless Inter DomainRouting).

IPv6See Internet Protocol Version 6

ISOSee International Standard Organization

ITU-TSee International Telecommunication Union Telecommunication Standardization

J



Java Virtual MachineThe environment in which Java programs run. The Java Virtual Machine gives Java programs a software-based computer they can interact with. Becausethe Java Virtual Machine is not a real computer but exists in software, a Java program can run on any physical computing platform.

JREJava runtime environment

JVMSee Java Virtual Machine

K

keyboard, video, and mouseA hardware device installed in the integrated configuration cabinet. KVM serves as the input and output device for the components inside the cabinet. Itconsists of a screen, a keyboard, and a mouse.

KVMSee keyboard, video, and mouse

L

LANSee Local Area Network

LCTSee Local Craft Terminal

LDAPSee Lightweight Directory Access Protocol

LicenseA 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 serialnumber. Usually the license consists of encrypted codes, and the operation authority varies with different level of license.

Lightweight Directory Access ProtocolAn TCP/IP based network protocol that enables access to a DSA. It involves some reduced functionality from X.500 DAP specification.

Link Layer Discovery ProtocolThe Link Layer Discovery Protocol (LLDP) is an L2D protocol defined in IEEE 802.1ab. Using the LLDP, the NMS can rapidly obtain the Layer 2network topology and changes in topology when the network scales expand.

LLDPSee Link Layer Discovery Protocol

load balancingThe 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 NetworkA network formed by the computers and workstations within the coverage of a few square kilometers or within a single building. It features high speedand low error rate. Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs are generally based on switchedEthernet or Wi-Fi technology and running at 1,000 Mbit/s (that is, 1 Gbit/s).

Local Craft TerminalLocal Craft Terminal. The terminal software that is used for local maintenance and the management of NEs in the singer-user mode, to realize integratedmanagement of multi-service transmission network. See also U2000.

M

MANSee Metropolitan Area Network

MD5See Message-Digest Algorithm 5

MDPSee message dispatch process

message dispatch processN/A

Message-Digest Algorithm 5A one-way hashing algorithm that produces a 128-bit hash. Both MD5 and Secure Hash Algorithm (SHA) are variations on MD4 and are designed tostrengthen the security of the MD5 hashing algorithm.

Metropolitan Area NetworkA metropolitan area network (MAN) is a network that interconnects users with computer resources in a geographic area or region larger than thatcovered 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 theinterconnection 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 usedto mean the interconnection of several local area networks by bridging them with backbone lines. The latter usage is also sometimes referred to as acampus network.



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

MSManual Switch

MSTPSee multi-service transmission platform

MSuiteNMS maintenance suite

multi-service transmission platformA platform based on the SDH platform, capable of accessing, processing and transmitting TDM services, ATM services, and Ethernet services, andproviding unified management of these services.

N

NBISee northbound interface

NESee network element

network elementA network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control board whichmanages and monitors the entire network element. The NE software runs on the system control board.

network layerThe network layer is layer 3 of the seven-layer OSI model of computer networking. The network layer provides routing and addressing so that twoterminal systems are interconnected. In addition, the network layer provides congestion control and traffic control. In the TCP/IP protocol suite, thefunctions of the network layer are specified and implemented by IP protocols. Therefore, the network layer is also called IP layer.

Network Management SystemA system in charge of the operation, administration, and maintenance of a network.

Network Time ProtocolThe Network Time Protocol (NTP) defines the time synchronization mechanism. It synchronizes the time between the distributed time server and theclient.

new technology file systemAn advanced file system designed for use specifically with the Windows NT operating 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-orientedapplications by treating all files as objects with user-defined and system-defined attributes.

NMSSee Network Management System

northbound interfaceThe interface that connects to the upper-layer device to realize service provisioning, report alarms and performance statistics.

NTFSSee new technology file system

NTPSee Network Time Protocol

O

OAMSee operation, administration and maintenance

Object SetA collection of managed objects. Object sets are established to facilitate the user right management. If a user (or user group) is authorized with theoperation 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 youthe trouble of setting the management rights for each NE one by one. Object sets can be created by geographical area, network layer, equipment type andso on.

OMCSee Operation and Maintenance Center

ONUSee Optical Network Unit

Operation and Maintenance CenterAn Operations and Maintenance Centre is an element within a network management system responsible for the operations and maintenance of a specificelement or group of elements. For example an OMC-Radio may be responsible for the management of a radio subsystem where as an OMC-Switch maybe 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 tomanage one device, he or she cannot operate the device.

Operation SetA collection of operations. Classifying operations into operation sets helps to manage user operation rights. Operations performed by different users havedifferent impacts on system security. Operations with similar impacts are classified into an operation set. Users or user groups entitled to an operation setcan perform all the operations in the operation set. The NMS provides some default operation sets. If the default operation sets cannot meet therequirements for right allocation, users can create operation sets as required.

Operation SystemOperation System is abbreviated to OS. OS is the interface between users and computers. It manages all the system resources of the computer, and alsoprovides an abstract computer for users. With the help of OS, users can use the computers without any direct operation on hardware. For the computersystem, 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, administration and maintenanceA group of network support functions that monitor and sustain segment operation, activities that are concerned with, but not limited to, failure detection,notification, location, and repairs that are intended to eliminate faults and keep a segment in an operational state and support activities required toprovide the services of a subscriber access network to users/subscribers.

Operations Support SystemA system whose main function is to run applications that manage network elements, networks and services.

Optical Network UnitA form of Access Node that converts optical signals transmitted via fiber to electrical signals that can be transmitted via coaxial cable or twisted paircopper wiring to individual subscribers.

OSSee Operation System

OSSSee Operations Support System

P

packet loss ratioThe ratio of total lost packet outcomes to total transmitted packets in a population of interest.

packet transport networkN/A

PCSee Personal Computer

Peak Information RatePeak Information Rate . A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate.

Personal ComputerA computer used by an individual at a time in a business, a school, or at home.

PIRSee Peak Information Rate

PMUThe unit that is used to monitor power supply in the equipment.

Point-to-Point Protocol over EthernetPPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating PPP frames in Ethernet frames. It is used mainly with DSLservices. 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 beobserved or measured. (188)

2. In a communications network, a point at which signals can enter or leave the network en

Power and environment monitoring unitThe power and environment monitoring unit is installed at the top of the cabinet of the SDH equipment and is used to monitor the environment variables,such as the power supply and temperature. With external signal input through the relay, fire alarm, smoke alarm, burglary alarm, etc. can be monitored aswell. 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 alarmsetting, query of DIP switch status, etc.

PPPoESee Point-to-Point Protocol over Ethernet

private networkA network which provides services to a specific set of users only (see Recommendation I.570).

PSTNSee public switched telephone network

PTN



See packet transport networkpublic switched telephone network

Public Switched Telephone Network. A telecommunications network established to perform telephone services for the public subscribers. Sometimescalled POTS.

R

RADIUSSee remote authentication dial-in user service

RADIUSSee Remote Authentication Dial in User Service

RAIDSee Redundant Arrays of Independent Disks

Redundant Arrays of Independent DisksA data storage scheme that allows data to be stored and replicated in a hardware disk group (logical hard disk) consisting of multiple hard disks (physicalhard 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 arrayprovides higher data reliability and input/output performance. There are various defined levels of RAID, each offering differing trade-offs among accessspeed, 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 toform new RAID levels, such as RAID 10 (a combination of RAID 0 and RAID 1).

Remote Authentication Dial in User ServiceRADIUS was originally used to manage the scattered users who use the serial interface and modem, and it has been widely used in NAS. NAS deliversthe information of users on authentication, authorization and accounting to the RADIUS server. RADIUS stipulates how the user and accountinginformation is transferred between NAS and RADIUS. The RADIUS server is responsible for receiving the connection request from users to completeauthentication, and returning the configurations of the users to NAS.

remote authentication dial-in user serviceA security service that authenticates and authorizes dial-up users and is a centralized access control mechanism. RADIUS uses the User DatagramProtocol (UDP) as its transmission protocol to ensure real-time quality. RADIUS also supports the retransmission and multi-server mechanisms to ensuregood reliability.

replicated volume groupN/A

replication linkA link used for data replication between the production machine and redundancy machine. It is physically separated from the network of the primarylinks.

RlinkSee data replication link

RTNRadio Transmission Node

RVGSee replicated volume group

S

Script fileIt is the text file describing the physical information and configuration information of the entire network, including the NE configuration file, portnaming file, end-to-end configuration file, NE physical view script file, NMS information file and service implementation data script file.

SDHSee Synchronous Digital Hierarchy

Secure File Transfer Protocol (SFTP)A network protocol designed to provide secure file transfer over SSH.

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 toprotect information and provide powerful authentication function for a network when a user logs in to the network through an insecure network. Itprevents IP addresses from being deceived and plain text passwords from being captured.

Secure Sockets LayerA protocol for ensuring security and privacy in Internet communications. SSL supports authentication of client, server, or both, as well as encryptionduring a communications session.

Security LogSecurity 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 ProtocolSerial Line Interface Protocol, defines the framing mode over the serial line to implement transmission of messages over the serial line and provide theremote 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 anarchive 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-serverarchitecture for a LAN.

SFTPSee Secure File Transfer Protocol (SFTP)

SSHSee Secure Shell (SSH)

shelf management moduleThe shelf management board of the ATAE server.

Signal Noise RatioThe 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 isexpressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel).

Signal to Noise Ratio MarginThe signal-to-noise ratio margin represents the amount of increased received noise (in dB) relative to the noise power that the system is designed totolerate and still meet the target BER of accounting for all coding gains included in the design.

Simple Mail Transfer ProtocolThe TCP/IP (Transmission Control Protocol/Internet Protocol) protocol which facilitates the transfer of electronic-mail messages, specifies how twosystems are to interact, and the format of messages used to control the transfer of electronic mail.

Simple Network Management ProtocolA network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. Thisprotocol 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 theseactivities to the network console workstation. Control information about each device is maintained by a management information block.

Simple Network Time ProtocolA protocol that is adapted from the Network Time Protocol (NTP) and synchronizes the clocks of computers over the Internet.

SLIPSee Serial Line Interface Protocol

SMMSee shelf management module

SMTPSee Simple Mail Transfer Protocol

SNMPSee Simple Network Management Protocol

SNRSee Signal Noise Ratio

SNRMSee Signal to Noise Ratio Margin

SNTPSee Simple Network Time Protocol

SONETSee Synchronous Optical Network

SQLSee structured query language

SSLSee Secure Sockets Layer

static routeA route that cannot adapt to the change of network topology. Operators must configure it manually. When a network topology is simple, the network canwork in the normal state if only the static route is configured. It can improve network performance and ensure bandwidth for important applications. Itsdisadvantage is as follows: When a network is faulty or the topology changes, the static route does not change automatically. It must be changed by theoperators.

StelnetSecure Shell Telnet

structured query languageA database query and programming language widely used for accessing, querying, updating, and managing data in relational database systems.

SVMSolaris Volume Manager

Switching restoration time



It refers to the period of time between the start of detecting and the moment when the line is switched back to the original status after protectionswitching occurs in the MSP sub-network.

Synchronous Digital HierarchySDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as framestructure, 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 thefiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure.

Synchronous Optical NetworkSynchronous Optical Network, is a method for communicating digital information using lasers or light-emitting diodes (LEDs) over optical fiber. Themethod was developed to replace the Plesiochronous Digital Hierarchy (PDH) system for transporting large amounts of telephone and data traffic and toallow for interoperability between equipment from different vendors. SONET defines interface standards at the physical layer of the OSI seven-layermodel. 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).

SYSLOGSyslog is an industry standard protocol for recording device logs.

T

TCPSee Transmission Control Protocol

TCP/IPSee Transmission Control Protocol/Internet Protocol

Telecommunication Management NetworkThe Telecommunications Management Network is a protocol model defined by ITU-T for managing open systems in a communications network. Anarchitecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunicationsequipment, networks and services.

TelnetStandard terminal emulation protocol in the TCP/IP protocol stack. Telnet is used for remote terminal connection, enabling users to log in to remotesystems and use resources as if they were connected to a local system. Telnet is defined in RFC 854.

TFTPSee Trivial File Transfer Protocol

Time zoneA 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 thecentre of the zone.

timing task managementThe system can create a timing task (such as backing up, loading and recovering a task), run a timing task automatically, and suspend or resume a timingtask.

TMNSee Telecommunication Management Network

Transmission Control ProtocolOne of the core protocols of the Internet protocol suite. Using TCP, applications on networked hosts can create connections to one another, over whichthey can exchange streams of data. TCP guarantees reliable and in-order delivery of data from the sender to the receiver. TCP also distinguishes data formultiple connections by concurrent applications running on the same host.

Transmission Control Protocol/Internet ProtocolCommon name for the suite of protocols developed to support the construction of worldwide internetworks.

Trivial File Transfer ProtocolA small and simple alternative to FTP for transferring files. TFTP is intended for applications that do not need complex interactions between the clientand server. TFTP restricts operations to simple file transfers and does not provide authentication. TFTP is small enough to be contained in ROM to beused for bootstrapping diskless machines.

U

UDPSee User Datagram Protocol

UPSUninterruptible Power Supply

User Datagram ProtocolA TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User DatagramProtocol (UDP) uses IP to deliver datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDPmessages 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 notactively confirm whether the correct data packet is received.

V

VCSSee Veritas Cluster Server



Veritas Cluster ServerA High-availability cluster software, for Unix, Linux and Microsoft Windows computer systems, created by Veritas Software. It provides applicationcluster capabilities to systems running Databases, file sharing on a network, electronic commerce websites or other applications.

Veritas Volume ManagerA software product from veritas Inc.. The Veritas Volume Manager is used to manage disk storage.

Veritas Volume ReplicatorA wide area network data replication solution offered by VERITAS for multiple operating systems. These include. AIX, HPUX, Solaris and Windows2000.

Virtual Local Area NetworkA logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number.This is often associated with switched Ethernet.

Virtual Router Redundancy ProtocolA protocol used for multicast or multicast LANs such as an Ethernet. A group of routers (including an active router and several backup routers) in a LANis 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 withother networks through this virtual router. If the active router in the backup group fails, one of the backup routers become the active one and providesrouting service for the host in the network.

VLANSee Virtual Local Area Network

volumeA logical unit for disk virtualization management, and basic object for host applications.

VRRPSee Virtual Router Redundancy Protocol

VVMSee Veritas Volume Manager

W

WANSee Wide Area Network

wavelength division multiplexingA technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, uses multiple wavelengths as carriers,and allows multiple channels to transmit simultaneously in a single fiber.

WDMSee wavelength division multiplexing

Wide Area NetworkA network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broadarea, such as a province, a state or even a country.

Wireless Local Area NetworkA generic term covering a multitude of technologies providing local area networking via a radio link. Examples of WLAN technologies include WiFi(Wireless Fidelity), 802.11b and 802.11a, HiperLAN, Bluetooth, etc.

WLANSee Wireless Local Area Network

work stationA terminal or microcomputer, usually one that is connected to a mainframe or to a network, at which a user can perform applications.

WSSee work station


Date post:	26-Dec-2015
Category:	Documents
Upload:	ghallab-alsadeh
View:	282 times
Download:	7 times

HA System (Veritas) Software Installation and Commissioning Guide (Solaris)

Documents