This document is used to guide the maintenance personnel in performing preventive maintenance on the UniSystem system. Maintenance personnel carry out regular system inspections and maintenance work to promptly identify and address potential faults in the UniSystem system.

Restrictions and guidelines

To fully utilize the performance and functions of UniSystem, ensure its long-term safe, stable, and reliable operation, prevent accidents, and reduce maintenance costs, the maintenance personnel must carefully read and strictly adhere to the relevant restrictions and guidelines before performing maintenance operations.

Network security

· Make sure only personnel with maintenance privileges can access devices deployed with UniSystem.

· The installation or running of non-standard software (such as firewall, antivirus, gaming, or pirated software) on devices equipped with UniSystem is strictly prohibited.

· Do not directly connect storage media such as laptops, personal drives, and testing instruments to the local area network.

System security

· Strictly control the activation of network services.

· Regularly monitor the network connection status to ensure that access is authorized.

· Safely store the administrator password and regularly change user passwords.

· Strictly limit user roles to ensure that users of different roles have only the minimum operation permissions to access resources.

· Fully appreciate the importance of routine maintenance, strictly follow the manual to perform routine inspections and tests, and keep records.

· All major operations, such as service restarting, server switching, and software loading, must be strictly controlled.

· Before the operation, carefully confirm its feasibility, prepare the necessary backups, contingency and safety measures, and have it executed by experienced personnel. Do not power off or restart the system unnecessarily.

· If you encounter difficult problems, thoroughly record all original information and promptly contact Technical Support.

· In case of an emergency, maintenance personnel must follow the emergency procedure and immediately contact Technical Support.

Data security

Modifications to critical data must be authorized and controlled. Maintenance personnel must perform data backup before any changes and keep complete operation records.

High-risk operations

Apply a server template to set up RAID or install the OS

About this task

Perform this task to apply a server configuration template to set up RAID or install an OS.

Possible risks

Setting up RAID or installing an OS through a server configuration template cleans the original system disk, resulting in the loss of system data.

Precautions

Apply server configuration templates cautiously.

Procedure

1. Log in to UniSystem, and access the Menu > Templates > Server Templates page to enter the server configuration template page, as shown in Figure 1.

Figure 1 Server configuration template page

2. Click the name link to enter the server configuration template details page, as shown in Figure 2. Check the configuration items in the template, including RAID setup and system configuration. Confirm that the configuration is as expected and apply the template.

IMPORTANT:

· If the retaining feature is not enabled in the RAID settings or the RAID settings are incorrect, it might lead to the loss of relevant storage data.

· Even with the retaining feature enabled, if the member drives and RAID levels configured in RAID settings differ from the original RAID, data loss can still occur.

Figure 2 Server configuration template details page

Enable the PXE feature

About this task

Perform this task to enable the Preboot Execution Environment (PXE) feature of UniSystem. Only the AE version of UniSystem supports the PXE feature.

Possible risks

After you enable PXE, if a server in the same LAN accidentally restarts and is set to boot preferentially from the network adapter, the server will automatically enter the PXE installation process, causing loss of original system data.

Suggestion

As a best practice, do not keep the PXE feature enabled for a long term when you are not deploying the system.

Procedure

1. Log in to UniSystem, and access the Menu > Tools > PXE Deployment page.

2. After completing the operating system deployment through PXE, promptly shut down the PXE server.

Figure 3 PXE deployment page

Apply a server configuration template to configure connection configuration

About this task

Perform this task to apply the connection configuration of a server configuration template to set up switch VLAN settings.

NOTE:

The connection configuration feature only supports H3C S6850-56HF and H3C S6800-54QF switches, and only supports setting the link type of ports to access.

Possible risks

Incorrect VLAN settings on switches that interact with external networks might lead to server disconnection from the Internet if the switch and server network adapters are not on the same network, posing a risk of service interruption.

Suggestion

Before applying the server configuration template, make sure the connection configuration for the switch and the actual server ports connected to the switch ports are on the same VLAN.

Procedure

1. Log in to UniSystem, and access the Menu > Templates > Server Templates page to enter the server configuration template page, as shown in Figure 4.

Figure 4 Server configuration template page

2. Click the name link to access the server configuration template details page. As shown in Figure 5, check the connection configuration in the configuration template. Applying the connection configuration will set the corresponding network port to access type and set the VLAN ID of the switch port to the one specified in the configuration.

Figure 5 Connection configuration

3. Check the VLAN settings of the server's service port connected to the switch port under the operating system, and apply the server configuration template only after confirming that the VLAN settings meet expectations.

User permissions

UniSystem divides user operational permissions into the following types:

· Users with the admin role have administrative privileges to perform all functional operations, such as adding, editing, and deleting other users, as well as adding, editing, removing, copying configurations, installing operating systems, and updating components.

· Users with the guest role can only view interface information and cannot perform related functional operations.

UniSystem supports adding up to 10 users, including the default user admin, and prohibits the addition of a user named System since the system operations use this username by default. An admin user with the same permissions can log in multiple times, with a maximum of 30 users online at the same time, including multiple logins by the same user.

Commonly used operations

Add a server

UniSystem manages servers through HDM or FIST SMS (installed on the target servers). Using FIST SMS requires the IP address of the operating system with FIST SMS installed.

NOTE:

· When adding FIST SMS, disable the firewall of the operating system on the server where FIST SMS is located or add port 12580 to the allowlist in the firewall, turn off SELinux, and make sure HDM is present on the server and is not being updated.

· When adding an HDM server, connect to the HDM management interface (either the HDM dedicated network port or the HDM shared network port). When adding a FIST SMS server, make sure the IP address of the UniSystem service side and the operating system where FIST SMS resides can ping each other successfully.

· After adding a device to UniSystem, do not change the device port number. If you do so, you must re-add the device or wait up to half an hour for the port number to recover automatically.

UniSystem communicates with HDM using the services shown in the following table when managing servers. To use UniSystem features normally, make sure the relevant HDM ports of the managed servers are available.

Do not change the default port number of the IPMI protocol. If you do so, it will prevent normal communication between UniSystem and HDM.

Table 1 Communication port

Service	Default port number
Service	Insecure port number	Secure port number
CD-Media	5120	5124
IPMI	623	623
KVM	7578	7582
SNMP Trap	162	N/A
Web	80	443

Manual adding

About this task

Perform this task to add a single server to UniSystem to be managed by UniSystem.

Procedure

1. In the navigation pane, select Menu > Devices > Server List.

2. Click Add, as shown in Figure 6. Select Add Manually to enter the manual addition page.

Figure 6 Selecting the addition method

3. Enter device information, and select a static group (optional).

¡ If the added device is an HDM device, select HDM as the device type, as shown in Figure 7. Enter the management IP address, username, and password for the HDM device. As a best practice, specify an administrator's username and password. If you specify a non-administrator's username, some functionality will not be available. The HDM of the same server can be managed by multiple UniSystem servers simultaneously.

Figure 7 Manually adding an HDM server

¡ If the added device is a FIST SMS device, select FIST SMS as the device type. As shown in Figure 8, enter the system IP address of the device.

Figure 8 Manually adding a FIST SMS server

4. Click OK to complete the operation.

Import servers

About this task

Perform this task to add multiple servers at once using a template.

Procedure

1. In the navigation pane, select Menu > Devices > Server List.

2. Click Add, and then select Bulk Import as shown in Figure 9.

Figure 9 Importing servers

3. Click to download the device template. The device list file supports .txt, .xlsx, and .xls formats as detailed in Table 2.

Table 2 Template file description

Template	Description
template-1.txt	Each line represents a device and specifies the device IP address, username, password, and name in sequence. To add HDM devices, you must specify the IP addresses, usernames, and passwords. To add FIST SMS devices, you must specify the IP addresses. The device name is optional.
template-2.xlsx	Each row represents a device and specifies the device type, IP address, username, password, and device name in sequence. To add HDM devices, you must specify the device types, IP addresses, usernames, and passwords. To add FIST SMS devices, you must specify the device types and IP addresses. The device name is optional.
template-3.xls	Each row represents a device and specifies the device type, IP address, username, password, and device name in sequence. To add HDM devices, you must specify the device types, IP addresses, usernames, and passwords. To add FIST SMS devices, you must specify the device types and IP addresses. The device name is optional.

4. Fill in the device information in the template form. Make sure the IP addresses are correct and valid, as incorrect addresses will affect the efficiency of bulk addition.

5. Click ... and select the device list file.

6. Click Upload. After the uploading, you can view the pending devices in the device list.

7. (Optional.) Select a static group.

8. Select the devices to be added and click OK. The system then starts to add the devices.

Discover devices

About this task

This feature discovers and adds servers in bulk by using SSDP or scanning the IP address range of all devices. Then scanning method can be used to identify all devices, assisting users in adding servers to the management system when the precise IP addresses are unknown, but the subnet is known. When adding a device of type HDM, you must also obtain the HDM username and password.

The SSDP method supports only devices of G6 and later generations.

· UniSystem and the server cannot communicate across routers. Make sure they operate within a Layer 2 network.

· You must enable IPv6 for UniSystem and HDM, enable the SSDP function of HDM, and set the listening port to port 1900.

Procedure

1. In the navigation pane, select Menu > Devices > Server List.

2. Click Add, and then select Auto Discovery to enter the device discovery page.

3. Select the device type and the search method.

¡ When the search type is All or HDM and IP subnet scanning is used, you must enter both the start and end IP addresses, as well as the username and password of the device to be searched. When you choose to search using SSDP, you must enter the username and password of the device to be searched.

¡ When the search type is FIST SMS, the search method only supports using IP subnet scanning. Enter the start and end IP addresses of an IP address range.

4. Select whether to add the discovered servers automatically. If you select Use SSDP for Search Method, the discovered servers will be added automatically by default. If you select Use IP Subnet Scanning for Search Method and select Yes for Auto Add After Searching, enter the number of search cycles.

5. (Optional.) Select a static group.

6. Click Search.

¡ If you select No for Auto Add After Searching, select servers to be added from the discovered server list, and then click Add.

Figure 10 Adding selected servers to UniSystem

¡ If you select Yes for Auto Add After Searching, UniSystem automatically adds a server once it discovers the server. To abort the process, click Abort at the upper right corner of the discovered server list.

Figure 11 Stopping the discovery and adding process

7. To go back to the Server List page and view the newly added servers, click Back in the upper left corner of the page.

Add a CDU device

Procedure

1. In the navigation pane, select Menu > Devices > CDU Devices List.

2. Click Add CDU Device. In the dialog box that opens, specify the device information, and then click OK.

Parameters

· Device Name: Specify the device name, a case-sensitive string of 1 to 30 characters. Only Chinese characters, digits, letters, underscores (_), and hyphens (-) are allowed.

· Device Vendor: CDU device vendor.

· Model: CDU device model.

· IP Address: IP address of the management port of the CDU device. Only IPv4 addresses are supported.

· Port Number: TCP port number of the CDU device. The port number range is 1-65535 and the default port number is 502.

· Description: Description of the CDU device, a case-sensitive string of up to 64 characters. This field is optional. Only Chinese characters, digits, letters, underscores (_), and spaces are allowed. The string cannot start or end with a space.

Restrictions and guidelines

· In the current software version, the system supports only the 5204 CDU. The vendor of the 5204 CDU is Avvid and the model is CDU-AVVID-373314-41.5KW. You cannot modify the vendor or model.

· The device name is case-sensitive. Make sure the device name is unique in the CDU device list, and make sure devices in the list have different IP address and port number combinations. If the device name or IP address and port number combination already exists, the device adding operation fails.

Modify the UniSystem access address and port

Installation-free UniSystem

The default access address for UniSystem is the local IP address, with the default HTTP port set to 80 and the default HTTPS port set to 443. You can change the access ports using the following method:

1. Enter the UniSystem software directory, select the UniSystemLaunch_x64 file, select the .bat script file for Windows systems, or the .sh script file for Linux systems, and run as an administrator by right-clicking.

2. Modify the port in the pop-up UniSystem console as shown in Figure 12.

Figure 12 Port modification

UniSystem of the OVA VM version

· Method one: Enter the VM interface. After UniSystem starts, click the icon at the top right corner, then modify the UniSystem login IP address in the dialog box that appears, as shown in Figure 13.

Figure 13 Changing the login IP address of UniSystem

· Method two: See "Configure the network adapter mode and IP address."

UniSystem of the ISO image version

See "Configure the network adapter mode and IP address."

Modify the UniSystem network

NOTE:

This feature is only available when UniSystem is running on a VM or an AE module.

Set the host name

Procedure

1. In the navigation pane, select Menu > System > Network.

2. Enter the host name as shown in Figure 14.

Figure 14 Entering the host name

3. Click Save.

Configure the network adapter mode and IP address

Perform this task to configure the network adapter mode and IP address for the UniSystem server.

Procedure

1. In the navigation pane, select Menu > System > Network.

2. Click the icon for the network adapter mode information. Modify the network adapter mode in the pop-up dialog. Click OK to complete the network adapter mode settings.

3. Click Add New IP of a network port, enter the subinterface IP address and subnet mask, and click OK.

Configure DNS

About this task

Perform this task to configure the Domain Name Server (DNS) servers for the UniSystem server, enabling UniSystem to access the Internet through domain names. You can configure IPv4 and IPv6 DNS servers simultaneously.

To access websites or servers on the Internet through domain names, you must configure DNS for address resolution. Access to Internet is required for some features of UniSystem. To use such features, configure DNS as required.

Procedure

1. In the navigation pane, select Menu > System > Network.

2. Click DNS. In the dialog box that opens, configure DNS servers. First configure the primary DNS servers.

3. Click OK.

Configure proxy settings

This module allows you to configure a proxy server. Thus, UniSystem can use the HTTP or HTTPS protocol for external communication.

Proxy servers support configuring IPv4, IPv6, and domain name addresses. To use a domain name address, configure DNS settings for UniSystem in advance. For more information, see "Configure DNS."

1. In the navigation pane, select Menu > System > Proxy Settings, as shown in Figure 15.

Figure 15 Proxy settings page

2. Select whether to enable proxy.

3. Enter the proxy server parameters.

4. (Optional.) Select HTTP to enable HTTP proxy.

5. (Optional.) Select HTTPS to enable HTTPS proxy.

6. Click Save.

Configure NTP time servers

NOTE:

This feature is only available when UniSystem is running on a VM or an AE module.

You can configure UniSystem to synchronize the system time with an NTP server or manually set the system time.

1. In the navigation pane, select Menu > System > System Time. Select Sync with NTP Server, as shown in Figure 16.

Figure 16 NTP setup

2. Enable the Auto Sync option.

3. Enter the IP addresses of the primary NTP server and the secondary NTP server.

4. Click Save.

Register UniSystem to vCenter

About this task

Perform this task to register UniSystem as a plugin to the vCenter Server, allowing UniSystem to be managed by the open-source vCenter Server and accessible through the vSphere Client. vSphere Client is the main interface for managing vCenter Server.

Prerequisites

Data Preparation: IP address, username, and password of the vCenter Server client.

Procedure

1. After logging into UniSystem at https://UniSystem ip_address:https_port, enter https://UniSystem ip_address:https_port/server/0/register-plugin in your browser to access the plugin registration page, as shown in Figure 17.

Figure 17 Registering a plugin

IMPORTANT:

Log in to UniSystem via the HTTPS protocol to register the plugin. If you do not use HTTPS, you will not be able to access the plugin after registration.

2. Enter the IP address, username, and password for the vCenter Server.

3. Click OK.

4. After registration, log in to the vSphere Client and click the UniSystem icon on the Shortcuts page to access UniSystem via the vSphere Client.

Software installation

Install UniSystem

Obtain the UniSystem installation package

The following types of UniSystem server installation packages are available:

· .tar.gz file: A UniSystem server installation package that is ready to run without installation after extraction.

· .iso file: An automatically installable ISO image. After being installed and starting from the image, UniSystem will automatically run in the background.

· .ova file: A VM file for the VMware ESXi operating system. After you create a VM with the VM file, UniSystem will run automatically.

Install and start UniSystem through VM files under the VMware ESXi operating system

IMPORTANT:

Before installation, check the CPU, memory, and drive resources on the host to ensure they are sufficient for the VM to start successfully.

1. Right-click virtual machine in the navigator on the left, and then select to create or register a VM.

2. As shown in Figure 18, select the VM deployment through OVF or OVA file method as the creation type, and then click Next.

Figure 18 Selecting the creation type

3. As shown in Figure 19, enter the name of the newly created VM as the OVF and VMDK file, upload the .ova UniSystem installation file saved locally, and then click Next.

Figure 19 Selecting OVF and VMDK files

4. As shown in Figure 20, select the target data storage, and then click Next.

Figure 20 Selecting storage

5. As shown in Figure 21, select the network mapping and disk provisioning configuration options in the Deployment Options dialog box, and then click Next.

Figure 21 Deployment options

6. As shown in Figure 22, verify that the information is correct, and then click Finish.

Figure 22 Ready to Complete

As shown in Figure 23, upon installation completion, the VM will automatically start and finish installing and running UniSystem.

Figure 23 Installation completed

7. (Optional.) On the VM interface, after UniSystem starts up, click the icon at the top right corner. In the dialog box that opens, edit the UniSystem login IP address, as shown in Figure 24.

Figure 24 Network settings

Install and launch UniSystem using the TAR package on the Windows operating system

IMPORTANT:

Under the Windows system, image files uploaded without administrator privileges cannot be used normally.

1. Unzip the downloaded UniSystem installation package. The unzipped folder appears. Right-click UniSystemLaunch_x64.bat and select to run the file as an administrator.After a few seconds, the UniSystem Console window opens as shown in Figure 25.

2. After checking and configuring the interface parameters, click the START to launch UniSystem.

Figure 25 UniSystem Console window

NOTE:

· The range for the server HTTP and HTTPS port numbers is from 1 to 65535, with the default HTTP port being 80. If the HTTP and HTTPS ports are the same or occupied by other services, it will prevent UniSystem from starting. In this case, change the server port number.

· Session Timeout: The session timeout range is 600 to 1800 seconds, with a default value of 1800 seconds.

· Front Display: The UniSystem Console window stays on top of the interface if YES is selected.

3. Click DETAILS to view the operating information and confirm that UniSystem has started, as shown in Figure 26.

Figure 26 DETAILS page

Install and launch UniSystem under a Linux operating system with a graphical interface

NOTE:

· Before proceeding, make sure you have obtained the root access.

· Make sure you run UniSystem as an administrator.

1. Copy the downloaded UniSystem installation package (for example, the UniSystem-2.59.tar.gz file) to the UniSystem server directory, using the root directory as an example in this case.

2. Open the terminal window.

3. As shown in Figure 27, enter the tar -xf UniSystem-2.59.tar.gz command and press Enter to extract the UniSystem installation package.

Figure 27 Unzip the UniSystem installation package.

4. As shown in Figure 28, enter the cdcd UniSystem/ to access the extracted UniSystem folder.

Figure 28 Enter the UniSystem folder.

5. Enter UniSystemLaunch_x64.sh and press Enter. The UniSystem Console window opens as shown in Figure 29.

Figure 29 Run UniSystem.

IMPORTANT:

Do not close the terminal window while running the UniSystem console, or it will cause an interruption of the UniSystem service.

6. As shown in Figure 30, click START to launch UniSystem. Click DETAILS to view the operating information and confirm that UniSystem has started.

Figure 30 Starting UniSystem

NOTE:

· Session Timeout: The session timeout range is 600 to 1800 seconds, with a default value of 1800 seconds.

· Front Display: The UniSystem Console window stays on top of the interface if YES is selected.

Install and launch UniSystem on a Linux operating system without a graphical interface

1. Copy the downloaded UniSystem installation package (UniSystem-2.59.tar.gz) to the root directory of the UniSystem server.

2. As shown in Figure 31, enter the tar -xf UniSystem-2.59.tar.gz command and press Enter to extract the UniSystem installation package.

Figure 31 Unzip the UniSystem installation package.

3. As shown in Figure 32, enter the cdcd UniSystem/ to access the extracted UniSystem folder.

Figure 32 Enter the UniSystem directory.

4. As shown in Figure 33, enter the ./run.sh 80 443 1800 command (the default value for the HTTP port is 80, the HTTPS port is 443, and the default session timeout is 1800), press Enter. UniSystem starts to run.

NOTE:

· The 80 in the command represents the HTTP port number, and 443 represents the HTTPS port number, ranging from 1 to 65535. 1800 is the timeout duration, ranging from 600 to 1800 seconds. In this example, the values used are all default values. You can set the values as needed.

· As a best practice, launch the console in only one way under the same path.

Figure 33 Running UniSystem

Install and start UniSystem through an ISO image

The installation process is automatic and requires no manual intervention, allowing UniSystem to run in the background upon completion.

The following example demonstrates how to install and start UniSystem using an ISO image on the AE module.

1. Mount the ISO image through the AE module's HDM KVM remote console.

2. Click Virtual Media to bring up the interface.

3. On the CD/DVD tab, browse to the ISO image and connect to complete the image mounting.

4. Restart the server. The server will automatically boot from the virtual optical drive.

5. Begin installation, the installation process will proceed automatically without any manual intervention. The installation process takes about 30 minutes.

6. After installation, UniSystem will automatically run in the background of the AE module. If a black screen appears during the installation interface, it might be due to the excessive network traffic causing the KVM to not respond promptly to process data. Check your local PC's connection speed and duplex mode, and set it according to actual needs or to auto-detect as follows:

a. Open network & Internet settings.

b. Select to change adapter options and select the network in use.

c. Select properties, click Configure, click the Advanced tab, select the link speed and duplex mode from the property list, and set the value to auto detection.

View UniSystem status

View UniSystem startup status

Procedure

1. Start up UniSystem. For more information, see "Install UniSystem."

2. Enter the ..\UniSystem\configuration path.

3. Open the activebundle.txt file to view the startup information of submodule bundle, as shown in Figure 34.

Figure 34 bundle startup information

4. If the startup fails, a .log file named with the current timestamp will be generated in the current directory, as shown in Figure 35, and the activebundle.txt file lacks startup information for submodule bundle.

Figure 35 Log file

View UniSystem server status

Procedure

1. Identify the IP address of the UniSystem server.

2. Open the command prompt and use the ping command to ping the corresponding IP address to identify whether it can be accessed normally.

First setup for UniSystem

Prepare for a UniSystem login

Connect the UniSystem server to the network

To log in to UniSystem running on a PC or a server, make sure the UniSystem client can reach the UniSystem server.

To log in to UniSystem running on an AE module, complete the following tasks first:

1. Make sure the enclosure has a minimum of one AE module present.

An enclosure supports a maximum of two AE modules, as shown in Figure 36.

Figure 36 AE module slots

1: Slot E1

2: Slot E2

2. Connect the Ethernet port on the UniSystem client host to the MGMT port on the primary or standby OM module over the LAN, as shown in Figure 37.

Figure 37 Connecting to the OM module

3. On the UniSystem client, specify an IP address that resides on the same network segment as the UniSystem server. See Table 3 for the default IP address of the UniSystem server.

Obtain the UniSystem server IP address

IMPORTANT:

After logging in to UniSystem running in an AE module by using the default IP address, change the UniSystem IP address to avoid IP address conflicts in the future. For how to change the UniSystem IP address, see "Modify the UniSystem network."

Table 3 shows the default settings for UniSystem running in an AE module.

Table 3 Default UniSystem settings

Parameter	UniSystem server location	Parameter value
Username	N/A	admin
Password	N/A	Password@_
UniSystem login IP address	AE module slot E1	192.168.0.100/24
	AE module slot E2	192.168.0.101/24
	VM	192.168.0.100/24
	Non-AE environment	System IP address of the device where UniSystem resides.

UniSystem client requirements

Users can access UniSystem from a Web browser directly. See Table 4 for the supported Web browsers and recommended resolution.

Table 4 Client requirements

Browser	Resolution
· Google Chrome 66.0 or later · Mozilla Firefox 60.0 or later	1600 × 900 or higher

Browser

Resolution

· Google Chrome 66.0 or later

· Mozilla Firefox 60.0 or later

1600 × 900 or higher

Log in to UniSystem

1. Enter http://UniSystem ip address in the address bar of the browser, where UniSystem_ip_address represents the system IP address of the UniSystem server.

Figure 38 UniSystem login page

2. On the UniSystem login page, enter the username and password of a UniSystem user.

3. Click Log In.

The UniSystem Web interface opens, as shown in Figure 39.

NOTE:

The content of the UniSystem Web interface depends on the installation environment.

· If the UniSystem server is installed on the AE module, you can all UniSystem features.

· If the UniSystem server is installed in a non-AE environment, some features might not be available.

Figure 39 UniSystem Web interface

IMPORTANT:

· By default, the system timeout is set to 30 minutes. If no functional operations are performed within this timeout, the system will automatically log out. Then, you need to re-enter your username and password.

· If you use a disabled user account to log in to UniSystem, the system will prompt that this user activation status is invalid.

· If the port number of UniSystem has changed, enter http://UniSystem_ip_address:port, where the port number is the changed one, for example, http://192.168.0.175:8080.

UniSystem Web interface

The UniSystem Web interface can be divided into two areas, as shown in Figure 40.

Figure 40 UniSystem Web interface

Table 5 UniSystem Web interface design description

Area

Description

Header section

· —Click the button to view the username, login time, and IP address. If you are a local user, you can edit the password, role, and status.

· —Click the button to view the online help.

· —Click the button to view the UniSystem version information.

· —Click the button to change the display language.

Work pane

Displays operation information and function links.

Access by shortcut

On the top navigation bar, you can use Shortcuts to access a specified menu directly. To add a menu to Shortcuts, click Menu and then click for the menu. To remove a menu from Shortcuts, click Menu and then click for the menu. You can add a maximum of 10 menus to Shortcuts.

Figure 41 Adding menus to shortcuts

View UniSystem version info

Click the Version Info button in the top right corner to check the UniSystem version information, as shown in Figure 42.

Figure 42 UniSystem version information

Modify the login password

After UniSystem is installed, to modify the login password, log in the UniSystem Web interface and perform the following steps:

1. In the navigation pane, select Menu > System > User List.

2. Click Edit in the Actions column for a user. In the dialog box that opens, edit the user, as shown in Figure 43.

Figure 43 Editing user information

Backup and restoration

Manage a cluster

About this task

Cluster management allows you to create or manage a cluster of AE modules to implement high availability. UniSystem automatically monitors the status of the primary node. When the primary node fails, UniSystem will switch to run on the secondary node, which avoids service interruption caused by the failure of the primary AE module.

Prerequisites

Cluster creation requires data synchronization. For correct data synchronization, make sure the time difference between the primary and secondary nodes is shorter than 10 seconds. For more information about how to set the system time, see "Configure NTP time servers."

If a cluster is created, make sure the following conditions are met:

· Make sure the primary and secondary nodes can reach each other. As a best practice, assign static IP addresses to ports for the primary and secondary nodes to communicate with each other and make sure the ports have the same subnet mask.

· Make sure the primary and secondary nodes each have a unique host name for UniSystem access. Do not set the host name to localhost or a string of all digits.

· Do not configure multiple IP addresses on the same subnet for each network port.

For more information about how to set the host name and the network settings, see "Modify the UniSystem network."

Restrictions and guidelines

· The secondary UniSystem node in the cluster will be stopped during cluster creation.

· During cluster creation, do not power off the AE modules or disconnect the network. Data synchronization will take a long time, please wait till the whole progress finishes.

· During cluster creation, do not perform any other operations on UniSystem of the primary node.

· After the cluster is created, do not edit the host name, network, or system settings of UniSystem.

· UniSystem cannot be reverted from cluster mode to standalone mode.

· The host name of an AE module used in a cluster cannot be localhost or all digits.

· As a best practice, use a static IP address for the port on the primary and secondary node used for communication.

· Cluster creation failure will cause the unavailability of UniSystem. Please try again to create the cluster.

Procedure

1. In the navigation pane, select Menu > System > Cluster

2. Click the Create Cluster link.

3. On the page that opens, configure the following parameters of the cluster to be created.

¡ Secondary Node Address—IP address used by the secondary node to communicate with the primary node. As a best practice, use the IP address of network port vmng.om or the 10-GE network port of the secondary AE module.

¡ UniSystem Virtual IP Address—Virtual IP address for users to access UniSystem after the cluster is created.

¡ iSCSI Virtual IP Address—IP address used to configure the iSCSI service. Make sure the entered iSCSI virtual IP address is on the same network segment as an IP address of the 10-GE network port on the primary AE module.

Figure 44 Creating a cluster

4. Click OK. You can see the progress of the creation from the progress bar. To view detailed information about the cluster creation, click View Log.

5. UniSystem will automatically restart after the cluster is successfully created. Log in to UniSystem by using the virtual IP address of UniSystem.

6. View information about the primary and secondary nodes on the Cluster page.

Figure 45 Cluster Info page

7. Click the Edit icon next to the secondary node. In the dialog box that opens, enter the IP address of the node to replace the current secondary node. Then, click OK.

8. You can see the progress of the replacement from the progress bar. To view detailed information about the cluster replacement, click View Log.

Back up and restore UniSystem data

About this task

This feature allows you to back up and restore UniSystem data, download system operation logs, and restore the default UniSystem settings.

The UniSystem data that can be backed up or restored includes the device information, component update task information, configuration template or file information, address pool information, and user information. The following data cannot be backed up: Repositories, image files uploaded to the image list, cloned images, diskless boot volumes, listening settings, DHCP settings, and the version update file uploaded on the UniSystem version update page.

After you restore the default settings, the information that can be backed up on the UniSystem server is cleared and the user settings are restored to the default.

Restrictions and guidelines

· Before you restore the UniSystem data or restore the default settings of UniSystem, back up the current UniSystem data.

· To avoid restoration failure, do not perform any operations that might affect the restoration during UniSystem data restoration or default UniSystem setting restoration.

· To ensure that UniSystem operates properly, you must manually reboot UniSystem after you restore the UniSystem data or restore the default settings of UniSystem.

· To avoid configuration file verification failure during data restoration, do not make any changes to the backup configuration file.

· A server template or server configuration file becomes invalid after backup or restoration if it contains an image file or repository in the system settings. You must reconfigure the template or file before applying it to a server.

Procedure

1. In the navigation pane, select Menu > System Maintain and Upgrade. Click the Backup and Restore tab.

Figure 46 Backup & Restore page

2. To back up the running configuration, click Backup. The system will export the running configuration to a compressed file.

3. To restore the configuration in a configuration file, click … next to Restore, select the target configuration file, and then click Restore.

Figure 47 Restoring the configuration in a configuration file

4. To download UniSystem system operation logs in a compressed file to the local host, click Download.

5. To restore the default settings, click Restore Default. In the dialog box that opens, click OK.

Firmware update

About this task

This feature allows you to upgrade or downgrade the UniSystem software version. UniSystem software upgrade will not cause UniSystem data loss. However, as a best practice, back up the critical data before upgrading UniSystem.

The UniSystem upgrade interface is available only for UniSystem running on a VM or AE module. UniSystem of the package version does not need installation. To upgrade UniSystem of the package version, replace the new package with the old package.

Restrictions and guidelines

· To ensure that UniSystem can be upgraded normally, first stop the other UniSystem operations in progress before upgrading UniSystem.

· Upgrading UniSystem will log out all logged-in users except the current user. Additionally, other users cannot log in during the UniSystem upgrade process.

· Upgrading UniSystem will interrupt or restart related processes in the system where UniSystem is installed. If these processes are being used, related services might be interrupted.

Procedure (for UniSystem on a VM or AE module)

1. In the navigation pane, select Menu > System > Maintain and Upgrade. Click the UniSystem Software Upgrade tab.

Figure 48 UniSystem Software Upgrade page

2. (Optional.) Click Obtain Latest UniSystem Image to download the needed UniSystem software upgrade package from the official website.

3. Click the … button for the software upgrade operation, select the UniSystem upgrade package, and click Upload to upload the upgrade package.

4. Click Start Upgrade. In the dialog box that opens, click OK to start upgrading UniSystem.

After the upgrade is finished, UniSystem will automatically restart and return to the login page. After UniSystem is restarted, refresh the page, and log in to use the new UniSystem version.

Procedure (for UniSystem of the package version)

IMPORTANT:

After the upgrade, the port configuration cannot be retained.

1. Obtain the UniSystem upgrade package from the official website, and then click STOP to stop UniSystem, as shown in Figure 49.

Figure 49 UniSystem console

2. Select the new UniSystem upgrade package, decompress the package, and override the original UniSystem directory. Then, choose to replace all files as instructed.

3. Restart UniSystem.

Security maintenance

Overview

This module performs security maintenance on the system, helping prevent management interruptions, system crashes, and other issues in UniSystem. You need to build and maintain security barriers for the entire management system at multiple levels, proactively identifying and addressing any potential security issues.

Configure security policies

UniSystem security policies typically include user policies and session policies.

Table 6 Security policies

Module	Parameter	Description
User policy	Maximum number of users in the system	Maximum number of users supported in the system, in the range of 1 to 10. The default is 10.
	Account lockout duration (min)	Amount of time before a locked account can be used again, in the range of 1 to 5. The default is 1.
	Username length limit	Maximum length of a username, in the range of 1 to16 characters.
	Disable history passwords	Number of unique passwords that a user must create before an old password can be reused, in the range of 0 to 5. The default is 5.
	Account lockout threshold	Number of consecutive login failures that will cause a user account to be locked, in the range of 1 to 5. The default is 5.
	Password validity (days)	Maximum number of days that a password can be used, in the range of 0 to 365. When a password is about to expire, UniSystem prompts the user to change the password. The default is 180.
Session policy	Session idle timeout (seconds)	Idle timeout time of the user session, in the range of 300 to 1800. The default is 1800. A user session automatically disconnects when it times out.
Session policy	Maximum number of sessions in the system	The system allows multiple logins for users with the same admin privileges, with support for up to 30 simultaneous online users.

Configure whitelist rules

About this task

Perform this task to configure login rules to control UniSystem login. If information of a user login matches a login rule, the login is allowed. If information of a user login does not match any login rule, the login is denied. By default, no login rules are configured, and all logins are allowed.

Restrictions and guidelines

Configure login rules with caution because a user is allowed to log in to UniSystem only when a matching login rule is found.

Procedure

To create a login rule:

1. In the navigation pane, select Menu > System > User List.

2. On the Local Users tab, click Login Rules.

3. In the Login Rules dialog box that opens, click Create Login Rule, and then perform the following steps:

¡ Enter the start date & time and end time date & time of the time range during which users can log in to UniSystem.

¡ Enter the start IP address and end IP address.

¡ Check the box in the Enable column to activate the rule.

Figure 50 Login Rules dialog box

4. Click OK.

To edit login rules:

1. In the navigation pane, select Menu > System > User List.

2. On the Local Users tab, click Login Rules.

3. In the Login Rules dialog box that opens, edit the login rule settings.

4. Click OK.

To delete a login rule:

1. In the navigation pane, select Menu > System > User List.

2. On the Local Users tab, click Login Rules.

3. In the Login Rules dialog box that opens, click Delete in the Actions column for the login rule you want to delete.

4. Click OK.

Configure the security tip for login

About this task

UniSystem supports multi-user management, allowing multiple users to operate on the same device. Users can customize a prompt message on the UniSystem login page to reduce the risk of accidental operations.

Procedure

1. In the navigation pane, select Menu > System > Security Tip for Login.

Figure 51 Configuring the security tip for login

2. Select to enable Display security tip at login.

3. Enter a security tip or leave the security tip field empty.

4. Click Save.

After you save the security tip successfully, you can view the configured security tip on the login page.

Routine maintenance

View LDAP server information

If LDAP user groups are configured in UniSystem, for LDAP users to access the UniSystem Web interface correctly, make sure the connectivity between the LDAP server and the UniSystem client is normal.

To view the LDAP server:

1. In the navigation pane, select Menu > System > LDAP Management.

The LDAP Settings tab displays information about the LDAP servers configured in the system, each on a separate card.

Figure 52 LDAP Management page

2. (Optional.) To test connectivity to an LDAP server, click in the top right corner of the LDAP server card. For an LDAP server that uses the User Account directory binding type, you will be prompted to enter the username and password for connectivity test.

View operation logs

About this task

The operation log feature logs operations that a user performs on the UniSystem Web interface. By reviewing the operation logs, you can understand the impact of user actions on the operation and security of UniSystem, allowing timely measures to be taken to ensure the normal operation of UniSystem.

You can set filters to view only operation logs that match the filters.

Procedure

1. In the navigation pane, select Menu > Monitor > Operation Logs.The Operation Logs page displays all operation logs.

2. To filter operation logs, set the filter items.

¡ To filter operation logs by user role, select a role.

¡ To filter operation logs by module, select a module.

¡ To filter operation logs by time, select a time range.

3. Click Search. This page displays only operation logs that match all the specified filter items.

4. To clear the search criteria and display all logs, click Reset.

5. Click Export to download all operation logs in CSV format to the device.

View system operation logs

1. In the navigation pane, select Menu > System > Maintain and Upgrade. Click the Backup and Restore tab.

2. To download a compressed log file of the current UniSystem operation to the local, click Download in the Download System Operation Logs area.

Figure 53 Downloading logs

The log file is saved to the logs file in the compressed package, as shown in Figure 54.

Figure 54 Saving logs

3. After the system logs are downloaded, contact Technical Support to locate and resolve issues.

Troubleshooting

Restrictions and guidelines

Follow these restrictions and guidelines for troubleshooting issues:

· Keep all records of the fault scene and do not delete data or logs arbitrarily.

· Before making any modifications, back up the configuration information and data.

· Make sure the troubleshooting operations on UniSystem do not impact the operation of the server's operating system.

Troubleshooting flowchart

This section mainly introduces the basic process of handling UniSystem faults, including failure handling preparation, information collection, diagnostic location, and failure handling steps. The troubleshooting principle is to preliminarily determine all possible causes based on symptoms, and combine software and hardware log diagnosis and test verification results to ultimately identify the root cause and take corresponding actions to resolve the issue.

Figure 55 Troubleshooting flow

Table 7 Troubleshooting flow description

Step	Description
Troubleshooting preparation	Prepare software and hardware utilities and documentations required for troubleshooting.
Collect troubleshooting information	· Collect troubleshooting information, for example, symptom, device model, OS, and operations that have been performed. You can contact Technical Support to determine which information you need to collect. · Collect log information that helps troubleshooting.
Identify whether the issue is a product-related issue	Identify whether the issue is a product-related issue. · If the issue is a product-related issue, locate the issue. · If the issue is not a product-related issue, for example, an upper layer software failure or OS failure, contact the vendor first.
Locate issues	Locate the issues based on the collected troubleshooting information.
Troubleshoot issues	Take troubleshooting actions based on failure causes.
Contact Technical Support	If any issue persists after you troubleshoot the issues by following the guidelines in this document, contact Technical Support for help.

Troubleshooting preparation

Collect basic information

Collect basic server information as shown in Table 8.

Table 8 Basic server information

Item	Description
Product model	For example, H3C UniServer R4900 G5
Product serial number	For example, 210235A3THH19A000123
Hardware configuration	If you have changed the processor, memory, drive, or storage controller configuration, make that clear.
OS and application software versions	Determine whether to collect OS and application software versions as needed.
UniSystem version	For example, UniSystem-2.59
Issue occurrence time	For example, 14:31:57 Tue Feb 10 2021
Symptom	For example, login failed.
Operation before an issue occurs	For example, edit network settings.
Operation and result after an issue occurs and the result	For example, the issue persists after a UniSystem reset.

Collect troubleshooting related manuals

Obtain H3C Servers Troubleshooting Guide and H3C Servers Safety & Configuration Cautions and Guidelines from the H3C official website or Technical Support.

Collect troubleshooting information

For information about how to download UniSystem system operation logs, see "View system operation logs."

Locate issues

Contact Technical Support to analyze the logs to locate issues.

Troubleshoot issues

After issue location, contact Technical Support to complete the troubleshooting procedure.

FAQs

Failed to save the configuration after you add and edit a custom infrastructure monitoring template.

If an error message is displayed, edit the template settings as prompted. If no error message is displayed, sequentially identify whether the independent power sensors are correctly configured.

· Identify whether the health sensor in the combined status sensor is configured correctly.

· Identify whether the basic information of the template is correct.

· Identify whether the power sensor is configured correctly and operating correctly. If this power sensor is operating correctly, record the value of this sensor.

Failed to delete a custom monitoring template that has been created.

A monitoring template bound to a predefined device cannot be deleted.

UniSystem failed to display liquid-cooled module information when you view hardware information of the liquid-cooled server.

Only a liquid-cooled server supports displaying liquid-cooled module information. Verify that the server is a liquid-cooled server.

UniSystem can communicate with a managed CDU correctly but failed to obtain detailed CDU information.

Verify that the custom monitoring template used by the current custom Modbus device is configured correctly.

When FIST SMS is normal and you add a FIST SMS server, the system prompts a message sending failure.

To add a FIST SMS server, disable the firewall for the server OS where FIST SMS resides and make sure the target server for the add operation has HDM and is not during an update.

When you inventory or deploy a task, the system prompts that the selected nodes are not available.

If no selected nodes in a task are connected correctly or all nodes are being used, the system will prompt that the nodes are not available during inventory or deployment.

During the component update, after a task is deployed, the deployment log shows that the component deployment has failed.

During the deployment process, component deployment failure can be caused by network disconnection, FIST SMS termination, FIST SMS restart, or HDM termination. Sequentially identify these causes to locate the failure cause, and then proceed with the component update again.

After the deployment finishes, some nodes have no log information.

To resolve the issue:

· Check the network status between these nodes and UniSystem to ensure a normal network connection.

· Identify whether these nodes are being used by other users, as nodes cannot be simultaneously operated by multiple users.

· Refresh the task page, click View Logs. If the logs display normally, the issue is resolved. If the logs still appear abnormal, re-inventory and redeploy these nodes.

After a task is inventoried, the node list still has nodes not in ready for deployment state.

To resolve the issue:

· Check the network status between these nodes and UniSystem to ensure a normal network connection.

· Identify whether these nodes are being used by other users, as nodes cannot be simultaneously operated by multiple users.

· Redeploy the task.

Operation failed because UniSystem or FIST SMS is in a Chinese path.

This issue occurs because the system does not support Chinese paths. A Chinese path will cause a path transcoding error.

To resolve the issue, install UniSystem or FIST SMS in a language environment supported by the system.

Acronyms

Table 9 Acronyms

Term	Definition
CDU	Cooling Dispensing Unit
CPU	Central Processing Unit
DHCP	Dynamic Host Configuration Protocol
FIST SMS	Fast Intelligent Scalable Toolkit System Management Service
GUI	Graphical User Interface
HDM	Hardware Device Management
IPMI	Intelligent Platform Management Interface
LDAP	Lightweight Directory Access Protocol
NTP	Network Time Protocol
OS	Operating System
PXE	Preboot Execute Environment
RAID	Redundant Arrays of Independent Disks

H3C Servers UniSystem Maintenance Gudie-6W100

About this task

Possible risks

Precautions

Procedure

Enable the PXE feature

About this task

Possible risks

Suggestion

Procedure

About this task

Possible risks

Suggestion

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

Procedure

Parameters

Restrictions and guidelines

Procedure

Procedure

About this task

Procedure

Configure proxy settings

Configure NTP time servers

Register UniSystem to vCenter

Install and launch UniSystem using the TAR package on the Windows operating system

Install and start UniSystem through an ISO image

Procedure

Procedure

First setup for UniSystem

UniSystem client requirements

UniSystem Web interface

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure (for UniSystem on a VM or AE module)

Procedure (for UniSystem of the package version)

Restrictions and guidelines

Procedure

Procedure

Procedure

Failed to save the configuration after you add and edit a custom infrastructure monitoring template.

Failed to delete a custom monitoring template that has been created.

UniSystem failed to display liquid-cooled module information when you view hardware information of the liquid-cooled server.

UniSystem can communicate with a managed CDU correctly but failed to obtain detailed CDU information.

When FIST SMS is normal and you add a FIST SMS server, the system prompts a message sending failure.

When you inventory or deploy a task, the system prompts that the selected nodes are not available.

During the component update, after a task is deployed, the deployment log shows that the component deployment has failed.

After the deployment finishes, some nodes have no log information.

After a task is inventoried, the node list still has nodes not in ready for deployment state.

Operation failed because UniSystem or FIST SMS is in a Chinese path.

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program