With an advanced containerized microservice architecture, U-Center 2.0 provides clustering and high availability capabilities, features easy deployment, and supports large-scale data storage. Based on the architecture, U-Center 2.0 integrates the monitoring, CMDB, automation, IT process management, and service management components to form a unified operations and maintenance (O & M) platform.

In the containerized microservice architecture, the installation and deployment of different components might vary. This document provides streamlined installation and deployment guidelines for correct deployment of U-Center 2.0.

U-Center 2.0 deployment procedure at a glance

U-Center 2.0 contains CMDB, IOM, BSM, ITSM, NTA, AOM, and STM components. It supports standalone deployment on one master node and cluster deployment on three master nodes and N worker nodes (N ≥ 0).

NOTE:

All components of U-Center 2.0 support small-, medium-, and default-scale deployment. To deploy these components in small scale, make sure the Unified Platform is in simplified mode (lite mode). For more information about the lite deployment mode, see H3C Unified Platform Deployment Guide.

Table 1 shows the U-Center 2.0 deployment workflow.

Table 1 U-Center 2.0 deployment workflow

Step	Description	Remarks
Prepare servers.	· The standalone mode requires one server. · The cluster mode requires a minimum of three servers.	Required. For hardware and software requirements, see "Server requirements."
Deploy Unified Platform.	Install an operating system and dependencies.	Required. For more information, see H3C Unified Platform Deployment Guide.
	Install Matrix.	Required if a non-H3Linux 1.0 operating system is used. For more information, see H3C Unified Platform Deployment Guide.
	Create a cluster.	Required. For more information, see H3C Unified Platform Deployment Guide.
	Deploy Unified Platform installation packages.	Required. For more information, see H3C Unified Platform Deployment Guide.
Deploy IOM.	Deploy IOM installation packages.	Optional. For more information, see "(Optional.) Deploying the IOM component."
Deploy CMDB.	Deploy CMDB installation packages.	Optional. For more information, see "(Optional.) Deploying the CMDB component."
Deploy BSM.	Deploy BSM installation packages.	Optional. For more information, see "(Optional.) Deploying the BSM component."
Deploy ITSM.	Deploy ITSM installation packages.	Optional. For more information, see "(Optional.) Deploying the ITSM component."
Deploy NTA.	Deploy NTA installation packages.	Optional. For more information, see "(Optional.) Deploying the NTA component."
Deploy AOM.	Deploy AOM installation packages.	Optional. For more information, see "(Optional.) Deploying the AOM component."
Deploy STM.	Deploy STM installation packages.	Optional. For more information, see "(Optional.) Deploying the STM component."

Preparing for deployment

IP address assignment

IMPORTANT:

Deploy the environment and make sure that:

· The IP addresses of all the nodes can communicate with the internal virtual IP address of the cluster or northbound service virtual IP address.

· The internal IP addresses of all the nodes can communicate with one another, including the IP addresses in the service IP pool and content IP pool.

IMPORTANT:

Follow these restrictions and guidelines when deploying, upgrading, or rebuilding a cluster in a scenario where multiple NICs exist:

· Make sure all physical NICs before the NIC whose IP is used as the node IP in the Matrix cluster have IPs assigned or the ONBOOT value set to no. For example, if the node uses the IP of NIC ens191 as the node IP in the Matrix cluster, and ens190 is before ens191 in order, make sure ens190 has an IP assigned.

· You must use the ifconfig command to view the NIC order.

· Make sure no abnormal NIC configuration file exists in the cluster. For example, the ONBOOT value is yes when the NIC is not connected or not configured with an IP.

· If the cluster uses a bonding interface as the node IP in the Matrix cluster, make sure all physical NICs not the members of the bonding interface have IPs assigned or the ONBOOT value set to no.

Table 2 shows the IP address assignment for U-Center 2.0 deployment. Only IPv4 addresses are supported.

Table 2 Networking details

IP address	Description	Remarks
Master node 1 IP	IP address assigned to the master node installed with an operating system.	Required. (Only one master node is required in standalone mode.) IP addresses of master nodes in one cluster must be on the same subnet.
Master node 2 IP	IP address assigned to the master node installed with an operating system.
Master node 3 IP	IP address assigned to the master node installed with an operating system.
Northbound service VIP	The unified external access address for all applications deployed through Matrix.	Required. The northbound service VIP must be on the same subnet as the subnet of the master nodes.
Worker node IP addresses	IP address assigned to a worker node.	Optional. This IP address must be on the same subnet as those of the master nodes.

Installation packages

Table 3 describes the U-Center 2.0 installation packages when the H3C Linux operating system is used. If another operating system is used, H3Linux ISO files are not necessarily required. In this table, version indicates the version number and platform represents the CPU architecture type.

Table 3 Installation packages

Name	Description	Product package	Remarks	Dependencies
common_Linux-version_platform.iso	H3Linux OS installation package	PLAT	Required	N/A
UDTP_Middle_version_platform.zip	Middleware images installation package	PLAT	Required.	N/A
UDTP_GlusterFS_version_platform.zip	Installation package for the local shared storage.	PLAT	Required.	Middle
UDTP_Core_version_platform.zip	Installation package for the portal, unified authentication, user management, service gateway, help center, permission, resource identity, license, configuration center, resource group, and log services.	PLAT	Required.	Middle, GlusterFS
UDTP_IMonitor_version_platform.zip	Installation package for the self-monitoring service.	PLAT	Required.	Middle, GlusterFS, Core
BMP_Report_version_platform.zip	Installation package for the report service.	PLAT	Optional.	N/A
BMP_QuickReport_version_platform.zip	Installation package for the quick report service.	PLAT	Optional.	Report
BMP_Alarm_version_platform.zip	Installation package for the alarm service.	PLAT	Optional.	Report
BMP_Certificate_version_platform.zip	Installation package for the certificate management service.	PLAT	Optional.	N/A
BMP_Dashboard_version_platform.zip	Installation package for the dashboard framework.	PLAT	Optional.	The dashboard application requires installation of both the dashboard and widget packages, with the dashboard installed before the widget.
BMP_Widget_version_platform.zip	Installation package for the dashboard widget service.	PLAT	Optional.	Dashboard The dashboard application requires installation of both the dashboard and widget packages, with the dashboard installed before the widget.
BMP_NETCONF_version_platform.zip	Installation package for the NETCONF channel service and NETCONF configuration invalidity check service.	PLAT	Optional.	N/A
BMP_OneClickCheck_version_platform.zip	Installation package for the one-click inspection service.	PLAT	Optional.	Report, Alarm
BMP_RDR_version_platform.zip	Installation package for the disaster recovery service.	PLAT	Optional.	Report, Alarm
BMP_Snapshot_version_platform.zip	Installation package for the snapshot management service.	PLAT	Optional.	N/A
BMP_Subscription_version_platform.zip	Installation package for the subscription service.	PLAT	Optional.	Report, Alarm
BMP_Suspension_version_platform.zip	Installation package for the resource maintenance tag service.	PLAT	Optional.	Report, Alarm
BMP_Template_version_platform.zip	Installation package for the access parameter templates and monitoring templates.	PLAT	Optional.	N/A
BMP_WebSocket_version_platform.zip	Installation package for the southbound WebSocket service.	PLAT	Optional.	N/A
BMP_RDRArbitrator_version_platform.zip	Installation package for the arbitration service.	PLAT	Optional.	For the procedure of deploying the arbitration service, see H3C Unified Platform Deployment Guide.
BMP_Region_version_platform.zip	Installation package for hierarchical management.	PLAT	Optional.	For the module to send alarms, you need also install Report and Alarm.
BMP_Syslog_version_platform.zip	Installation package for the syslog service.	PLAT	Optional.	Report, Alarm
BMP_Aggregation_version_platform.zip	Installation package for alarm aggregation.	PLAT	Optional.	Report, Alarm
BMP_AIOPS_version_platform.zip	Installation package for the time-series data trend prediction and anomaly detection services.	PLAT	Optional. Matrix converged deployment does not support installation of this package. You can install this package on Unified Platform.	N/A
NSM_FCAPS-Res_version_platform.zip	Installation package for discovery, incorporation, and basic information management of network devices.	NSM	Optional.	· portal(UDTP_Core_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · report(BMP_Report_version_platform.zip) · suspension(BMP_Suspension_version_platform.zip) · template(BMP_Template_version_platform.zip)
NSM_FCAPS-Perf_version_platform.zip	Installation package for network device performance monitoring and display.	NSM	Optional.	· portal(UDTP_Core_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · report(BMP_Report_version_platform.zip) · res(NSM_FCAPS-Res_version_platform.zip) · template(BMP_Template_version_platform.zip)
U-Center_UCP_version_platform.zip	Installation package for the U-Center public platform component service.	IOM	Required.	N/A
U-Center_CLICKHOUSE_version_platform.zip	Installation package for the ClickHouse database service.	IOM	Optional.	N/A
U-Center_COLLECTPLAT_version_platform.zip	Installation package for the collection platform service.	IOM	Required.	N/A
U-Center_IOM_version_platform.zip	Installation package for the application monitoring service.	IOM	Required.	· portal · kernel(UDTP_Core_version_platform.zip) · accesstemp, monitortemp(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · dashboard(BMP_Dashboard_version_platform.zip)
U-Center_ADDM_version_platform.zip	Installation package for the auto-discovery service.	IOM	Optional.	N/A
U-Center_AGENT_version_platform.zip	Installation package for the agent service.	IOM	Optional.	N/A
U-Center_VKVM_2.0_version_platform.zip	Installation package for the server virtual remote console service.	IOM	Optional.	· Portal, kernel(UDTP_Core_version_platform.zip) · accesstemp, monitortemp(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · dashboard(BMP_Dashboard_version_platform.zip) · kernel-base(BMP_Template_version_platform.zip) · U-Center_COLLECTPLAT_version_platform.zip · U-Center_IOM_version_platform.zip
U-Center_CMDB_2.0_version_platform.zip	Installation package for the configuration management database.	CMDB	Optional.	· glusterfs(UDTP_GlusterFS_version_platform.zip) · common(UDTP_Middle_version_platform.zip) · UDTP_Core_version_platform.zip · alarm(BMP_Alarm_version_platform.zip)
U-Center_BSM_version_platform.zip	Installation package for the service health analysis service.	BSM	Optional.	· glusterfs(UDTP_GlusterFS_version_platform.zip) · portal, kernel(UDTP_Core_version_platform.zip) · kernel-base(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · cmdb(U-Center_CMDB_version_platform.zip) · ucp(U-Center_UCP_version_platform.zip) · collectplat(U-Center_COLLECTPLAT_version_platform.zip) · iop, iom(U-Center_IOM_version_platform.zip)
U-Center_UEM_version_platform.zip	Installation package for the user experience analysis service.	BSM	Optional.	N/A
U-Center_ITSM_version_platform.zip	Installation package for the process management service.	ITSM	Optional.	· glusterfs(UDTP_GlusterFS_version_platform.zip) · portal, kernel(UDTP_Core_version_platform.zip) · common(UDTP_Middle_version_platform.zip)
U-Center_NTA_version_platform.zip	Installation package for the traffic monitoring service.	NTA	Optional.	· portal, kernel(UDTP_Core_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · accesstemp(BMP_Template_version_platform.zip) · network(NSM_FCAPS-Res_version_platform.zip) · zookeeper, clickhouse(U-Center_CLICKHOUSE_version_platform.zip) · etcd(U-Center_UCP_version_platform.zip)
U-Center_STM_version_platform.zip	Installation package for simulation polling test management (STM).	STM	Optional.	· glusterfs(UDTP_GlusterFS_version_platform.zip) · portal, kernel(UDTP_Core_version_platform.zip) · kernel-base(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · ucp(U-Center_UCP_version_platform.zip) · collectplat(U-Center_COLLECTPLAT_version_platform.zip) · iom(U-Center_IOM_version_platform.zip)
U-Center_NQA_version_platform.zip	Installation package for STM task management.	STM	Optional.	· glusterfs(UDTP_GlusterFS_version_platform.zip) · portal, kernel(UDTP_Core_version_platform.zip) · kernel-base(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · ucp(U-Center_UCP_version_platform.zip) · collectplat(U-Center_COLLECTPLAT_version_platform.zip) · iom(U-Center_IOM_version_platform.zip) · network(NSM_FCAPS-Res_version_platform.zip) · network(NSM_FCAPS-Perf_version_platform.zip)
U-Center_AOM_2.0_version_platform.zip	Installation package for automated operation and maintenance management.	AOM	Optional.	· gluster(UDTP_GlusterFS_version_platform.zip) · common(UDTP_Middle_version_platform.zip) · portal, kernel(UDTP_Core_version_platform.zip) · kernel-base(BMP_Template_version_platform.zip) · alarm(BMP_Alarm_version_platform.zip) · network(NSM_FCAPS-Res_version_platform.zip) · network(NSM_FCAPS-Perf_version_platform.zip) · ucp(U-Center_UCP_version_platform.zip)

Server requirements

Hardware requirements

You can go to http://iservice.h3c.com to obtain the hardware configuration evaluation result. The evaluation result can be used as a reference. You can also contact Technical Support for an evaluation.

Software requirements

Table 4 Available Operating systems

Architecture	Operating system
x86	H3Linux V1.1.2
	H3Linux V2.0.2
	Red Hat Enterprise Linux 7.6
	Community Enterprise Operating System 7.6
	Red Hat Enterprise Linux 8.4
	Red Hat Enterprise Linux 8.6
	Kylin-Server-10-SP2-x86-RC01-Build09-20210524.iso

IMPORTANT:

· You must install the same operating system version on all nodes in a cluster.

· For the support of an operating system for the ARM and x86 architecture, see the release notes for the operating system.

Client requirements

You can use a browser to access U-Center 2.0 without installing client software. As a best practice, use Google Chrome 70 or Firefox 78 or higher with a minimum resolution width of 1600 pixels.

Pre-installation checklist

Table 5 shows the check list for the installation requirements. Make sure the U-Center 2.0 installation requirements are met.

Table 5 Pre-installation checklist

Item		Requirements
Server or VM	Hardware	The CPU, memory, disk, and NIC settings are as required.
Server or VM	Software	· The operating system meets the requirements. · The system time settings are configured correctly. As a best practice, configure NTP on each node to ensure time synchronization on the network, and make sure the NTP server time is the same as the current time. · RAID is configured.
Client		Make sure the browser version meets the requirement.

CAUTION:

· During the U-Center 2.0 deployment process, do not enable or disable firewall services.

· To avoid exceptions, do not modify the system time after cluster deployment.

IMPORTANT:

· As a best practice, set the mode to UEFI for the next startup of the server or VM. Select EFI from the boot firmware list. Do not select Enable UEFI secure boot for the VM.

· Do not use KVM to install the same image for multiple servers when installing an operating system.

· H5 KVM is unstable in performance and issues such as slow or unsuccessful image loading might occur during installation. As a best practice, use Java KVM to mount the image and install the operating system.

· A power failure during the installation process might cause installation failure of some service components. For function integrity, perform a reinstallation when a power failure occurs during installation.

· Do not enable or disable firewalls during the U-Center 2.0 deployment.

· To avoid cluster exceptions, do not edit the system time after the completion of cluster deployment.

Software package verification

Before installing the software, first perform MD5 verification on each software package to ensure its integrity and correctness.

Installing Unified Platform

Before deploying U-Center 2.0, first deploy Unified Platform and then deploy U-Center 2.0 components on Unified Platform.

1. Install the operating system and dependencies.

2. Install Matrix (required for a non-H3Linux 1.0 operating system).

3. Create a Matrix cluster.

4. Deploy PLAT components.

For more information about the deployment procedure, see H3C Unified Platform Deployment Guide.

Installing U-Center 2.0

1. Enter https://ip_address:8443/matrix/ui in your browser and then enter the username and password to log in to the Matrix. ip_address represents the IP of the node.

The default username is admin and the default password is Pwd@12345. If a password has been set during the installation of the operating system, enter the set password.

2. On the top navigation bar, click DEPLOY.

3. From the navigation pane, select Applications. The application list page opens.

4. Click Deploy Applications.

5. Click Upload. In the windows that opens, upload the application installation packages.

After installing the required packages, install optional packages as needed. Before installing a package, install its dependencies first. For the dependency relations between installation packages, see Table 3.

IMPORTANT:

· Middle, GlusterFS, Core, and IMonitor are required installation packages for Unified Platform. If the packages have been installed during Unified Platform deployment, you do not need to install them again.

· If you want to use the upper-level and lower-level functions, install BMP_Region_version_platform.zip.

· You can select and install all of the following packages simultaneously: UCP, COLLECTPLAT, IOM, ADDM, and AGENT.

· You can select and install all of the following packages simultaneously: BSM, UEM, ITSM, and VDI. NTA and ITSM require a separate installation and cannot be selected simultaneously with other packages.

· NTA requires installation of the NTA, NSM_FCAPS-Res, UCP, and CLICKHOUSE packages, which must be installed in the following order: NSM_FCAPS-Res, UCP, CLICKHOUSE, and NTA.

· To install AOM, first install the AOM_PLAT component, and then install the other components in any order. IPMS, INI, CCMS, OMTS, and PROBE can be installed at different steps. In a scenario with low performance or low disk read or write speed, install them in multiple steps.

· You can select the number of probes for AOM as needed. Select a minimum of one collector. As a best practice, add one collector for every 1,000 devices.

· To use HTTPS, log in to Unified Platform after the applications and components are installed and then select System > System Settings > Security Settings to enable HTTPS.

· After completing installation package upload, the system automatically synchronizes the installation packages to the following directory of each node: /opt/matrix/app/install/packages/

(Optional.) Deploying the IOM component

The installation packages listed as IOM in the Product Package column in Table 3 are IOM component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the IOM component:

1. On the Select Installation Package page, select U-Center_IOM_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the CMDB component

The installation packages listed as CMDB in the Product Package column in Table 3 are CMDB component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the CMDB component:

1. On the Select Installation Package page, select U-Center_CMDB_2.0_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the BSM component

The installation packages listed as BSM in the Product Package column in Table 3 are BSM component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the BSM component:

1. On the Select Installation Package page, select U-Center_BSM_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the ITSM component

The installation packages listed as ITSM in the Product Package column in Table 3 are ITSM component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the ITSM component:

1. On the Select Installation Package page, select U-Center_ITSM_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the NTA component

The installation packages listed as NTA in the Product Package column in Table 3 are NTA component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the NTA component:

1. On the Select Installation Package page, select U-Center_NTA_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the AOM component

The installation packages listed as AOM in the Product Package column in Table 3 are AOM component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the NTA component:

1. On the Select Installation Package page, select U-Center_AOM_2.0_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

(Optional.) Deploying the STM component

The installation packages listed as STM in the Product Package column in Table 3 are STM component-related installation packages. You can deploy the installation package as needed.

IMPORTANT:

Before installing the component, install its dependencies. For the dependency relations of the installation packages, see Table 3.

To deploy the NTA component:

1. On the Select Installation Package page, select U-Center_STM_version_platform.zip, and then click Next.

2. Select applications and click Next.

All applications are selected by default.

3. On the Configure Shared Storage page, click Next.

4. On the Configure Database page, click Next.

5. On the Configure Params page, click Next.

6. Click Deploy.

Logging in to U-Center 2.0

1. Enter the URL of U-Center 2.0 http://ip_address:30000 in your browser. Replace ip_address with the northbound service VIP. The default port number is 30000. Figure 1 shows the login page.

Figure 1 U-Center 2.0 login page

2. Enter the username and password, and then click Login.

The default username is admin and the default password is Pwd@12345. If you have set the password when installing the operating system, enter the set password.

Registering the software

After you deploy U-Center 2.0, you must obtain licenses to use it. If you have purchased the product, obtain the relevant license key to complete the consequent registration process. To obtain a trial license, contact relevant H3C marketing personnel.

For more information about requesting and installing licenses, see H3C Software Products Remote Licensing Guide.

License support

NOTE:

The license server and U-Center 2.0 are one-to-one related. A license server can be used by only one U-Center 2.0.

Table 6 describes the licenses for each component of U-Center 2.0.

Table 6 NSM licenses

Component	License description	Product code	Product description
NSM	Network basic license	LIS-IMC9-NSM	H3C iMC9.0, Intelligent Management Center License
	Network quantity license	LIS-IMC9-NSMA-25	H3C iMC9.0, Intelligent Management Platform (Network Management), 25 Licenses
		LIS-IMC9-NSMB-50	H3C iMC9.0, Intelligent Management Platform (Network Management), 50 Licenses
		LIS-IMC9-NSMC-100	H3C iMC9.0, Intelligent Management Platform (Network Management), 100 Licenses
		LIS-IMC9-NSMD-200	H3C iMC9.0, Intelligent Management Platform (Network Management), 200 Licenses
		LIS-IMC9-NSME-500	H3C iMC9.0, Intelligent Management Platform (Network Management), 500 Licenses
		LIS-IMC9-NSMF-1K	H3C iMC9.0, Intelligent Management Platform (Network Management), 1000 Licenses

Table 7 U-Center 2.0 licenses

Component	License description	Product code	Product description
CMDB	U-Center basic license	LIS-UCENTER2-IOP	H3C U-Center2.0, Intelligent Operations Platform Software
	CMDB basic license	LIS-UCENTER2-CMDB	H3C U-Center2.0, CMDB License
	Auto discovery basic license	LIS-UCENTER2-CMDB-DDM	H3C U-Center2.0, CMDB, Discovery and Dependency Mapping License
	CMDB quantity license	LIS-UCENTER2-CMDB-25	H3C U-Center2.0, CMDB, 25 Licenses
		LIS-UCENTER2-CMDB-50	H3C U-Center2.0, CMDB, 50 Licenses
		LIS-UCENTER2-CMDB-100	H3C U-Center2.0, CMDB, 100 Licenses
		LIS-UCENTER2-CMDB-200	H3C U-Center2.0, CMDB, 200 Licenses
		LIS-UCENTER2-CMDB-500	H3C U-Center2.0, CMDB, 500 Licenses
		LIS-UCENTER2-CMDB-1K	H3C U-Center2.0, CMDB, 1000 Licenses
		LIS-UCENTER2-CMDB-1	H3C U-Center2.0, CMDB, 1 License
		LIS-UCENTER2-CMDB-100-A	H3C U-Center2.0, CMDB, 100 Licenses
Report	Report	LIS-UCENTER2-IOM-IAR	H3C U-Center2.0, IOM, Intelligent Analysis Report License
IOM	IOM basic license	LIS-UCENTER2-IOM	H3C U-Center2.0, IOM Licenses
	IOM quantity license	LIS-UCENTER2-IOM-25	H3C U-Center2.0, IOM, 25 Licenses
		LIS-UCENTER2-IOM-50	H3C U-Center2.0, IOM, 50 Licenses
		LIS-UCENTER2-IOM-100	H3C U-Center2.0, IOM, 100 Licenses
		LIS-UCENTER2-IOM-200	H3C U-Center2.0, IOM, 200 Licenses
		LIS-UCENTER2-IOM-500	H3C U-Center2.0, IOM, 500 Licenses
		LIS-UCENTER2-IOM-1K	H3C U-Center2.0, IOM, 1000 Licenses
		LIS-UCENTER2-IOM-1	H3C U-Center2.0, IOM, 1 License
		LIS-UCENTER2-IOM-100-A	H3C U-Center2.0, IOM, 100 Licenses
BSM	BSM basic license	LIS-UCENTER2-BSM	H3C U-Center2.0, BSM License
	BSM quantity license	LIS-UCENTER2-BSM-1	H3C U-Center2.0, BSM, 1 License
		LIS-UCENTER2-BSM-5	H3C U-Center2.0, BSM, 5 Licenses
		LIS-UCENTER2-BSM-10	H3C U-Center2.0, BSM, 10 Licenses
	UEM quantity license	LIS-UCENTER2-BSM-UEM-1-B	H3C U-Center2.0, BSM, UEM, 1 License
		LIS-UCENTER2-BSM-UEM-1	H3C U-Center2.0, BSM, UEM, 1 License
		LIS-UCENTER2-BSM-UEM-2	H3C U-Center2.0, BSM, UEM, 2 License
		LIS-UCENTER2-BSM-UEM-5	H3C U-Center2.0, BSM, UEM, 5 License
NTA	NTA basic license	LIS-UCENTER2-IOM-NTA	H3C U-Center2.0, IOM, Network Traffic Analyzer License
	NTA quantity license	LIS-UCENTER2-IOM-NTA-1-B	H3C U-Center2.0, IOM, Network Traffic Analyzer, 1 License
		LIS-UCENTER2-IOM-NTA-1	H3C U-Center2.0, IOM, Network Traffic Analyzer, 1 License
		LIS-UCENTER2-IOM-NTA-2	H3C U-Center2.0, IOM, Network Traffic Analyzer, 2 License
		LIS-UCENTER2-IOM-NTA-5	H3C U-Center2.0, IOM, Network Traffic Analyzer, 5 License
	NTA probe quantity license	LIS-UCENTER2-IOM-NTA-DIG-1	H3C U-Center2.0, IOM, DIG Probe, 1 License
	NTA probe license	LIS-UCENTER2-IOM-NTA-DIG	H3C U-Center2.0, IOM, DIG Probe License
ITSM	ITSM basic license	LIS-UCENTER2-ITSM	H3C U-Center2.0, ITSM License
	ITSM quantity license	LIS-UCENTER2-ITSM-1	H3C U-Center2.0, ITSM, 1 License
		LIS-UCENTER2-ITSM-5	H3C U-Center2.0-ITSM-5 License
		LIS-UCENTER2-ITSM-10	H3C U-Center2.0-ITSM-10 License
		LIS-UCENTER2-ITSM-20	H3C U-Center2.0-ITSM-20 License
		LIS-UCENTER2-ITSM-50	H3C U-Center2.0-ITSM-50 License
		LIS-UCENTER2-ITSM-100	H3C U-Center2.0-ITSM-100 License
	ITSM change release management license	LIS-UCENTER2-ITSM-CRM	H3C U-Center2.0, ITSM, Change and Release Management License
	ITSM service level management basic license	LIS-UCENTER2-ITSM-SLM	H3C U-Center2.0, ITSM, Service Level Management License
	ITSM knowledge base license	LIS-UCENTER2-ITSM-KB	H3C U-Center2.0, ITSM, Knowledge Base License
	ITSM self-service platform license	LIS-UCENTER2-ITSM-SSD	H3C U-Center2.0, ITSM, Self-Service Desk License
AOM	IP address management	LIS-UCENTER-AOM-IPMS-50	H3C UCenter, AOM, IP Address Management System, 50 Licenses
		LIS-UCENTER-AOM-IPA-100	H3C UCenter, AOM, IP Address Management System, 100 Licenses
		LIS-UCENTER-AOM-IPA-200	H3C UCenter, AOM, IP Address Management System, 200 Licenses
		LIS-UCENTER-AOM-IPA-500	H3C UCenter, AOM, IP Address Management System, 500 Licenses
		LIS-UCENTER-AOM-IPA-1000	H3C UCenter, AOM, IP Address Management System, 1000 Licenses
		LIS-UCENTER2-AOM-IPA-1	H3C U-Center2.0, AOM, IP Address Management System, 1 License
		LIS-UCENTER2-AOM-IPA-100-A	H3C U-Center2.0, AOM, IP Address Management System, 100 Licenses
	Operation and maintenance troubleshooting license	LIS-UCENTER-AOM-TS-50	H3C U-Center, AOM, Operation and Maintenance Troubleshooting Software, 50 Licenses
		LIS-UCENTER-AOM-TS-100	H3C U-Center, AOM, Operation and Maintenance Troubleshooting Software, 100 Licenses
		LIS-UCENTER-AOM-TS-200	H3C U-Center, AOM, Operation and Maintenance Troubleshooting Software, 200 Licenses
		LIS-UCENTER-AOM-TS-500	H3C U-Center, AOM, Operation and Maintenance Troubleshooting Software, 500 Licenses
		LIS-UCENTER-AOM-TS-1000	H3C U-Center, AOM, Operation and Maintenance Troubleshooting Software, 1000 Licenses
		LIS-UCENTER2-AOM-TS-1	H3C U-Center2.0, AOM, Operation and Maintenance Troubleshooting Software, 1 License
		LIS-UCENTER2-AOM-TS-100-A	H3C U-Center2.0, AOM, Operation and Maintenance Troubleshooting Software, 100 Licenses
	Configuration and compliance intelligent management license	LIS-UCENTER-AOM-CCI-50-2	H3C UCenter, AOM, Configuration And Compliance Intelligent Management, 50 Licenses
		LIS-UCENTER-AOM-CCI-100-2	H3C UCenter, AOM, Configuration And Compliance Intelligent Management, 100 Licenses
		LIS-UCENTER-AOM-CCI-200-2	H3C UCenter, AOM, Configuration And Compliance Intelligent Management, 200 Licenses
		LIS-UCENTER-AOM-CCI-500-2	H3C UCenter, AOM, Configuration And Compliance Intelligent Management, 500 Licenses
		LIS-UCENTER-AOM-CCI-1000-2	H3C UCenter, AOM, Configuration And Compliance Intelligent Management, 1000 Licenses
		LIS-UCENTER2-AOM-CCI-1	H3C U-Center2.0, AOM, Configuration And Compliance Intelligent Management, 1 License
		LIS-UCENTER2-AOM-CCI-100-A	H3C U-Center2.0, AOM, Configuration And Compliance Intelligent Management, 100 Licenses
	Intelligent inspection	LIS-UCENTER-AOM-IIE-50	H3C U-Center, AOM, Intelligent Inspection Expert Provider Edition, 50 Licenses
		LIS-UCENTER-AOM-IIE-100	H3C U-Center, AOM, Intelligent Inspection Expert Provider Edition, 100 Licenses
		LIS-UCENTER-AOM-IIE-200	H3C U-Center, AOM, Intelligent Inspection Expert Provider Edition, 200 Licenses
		LIS-UCENTER-AOM-IIE-500	H3C U-Center, AOM, Intelligent Inspection Expert Provider Edition, 500 Licenses
		LIS-UCENTER-AOM-IIE-1000	H3C U-Center, AOM, Intelligent Inspection Expert Provider Edition, 1000 Licenses
		LIS-UCENTER2-AOM-IIE-1	H3C U-Center2.0, AOM, Intelligent Inspection Expert Provider Edition, 1 License
		LIS-UCENTER2-AOM-IIE-100-A	H3C U-Center2.0, AOM, Intelligent Inspection Expert Provider Edition, 100 Licenses
STM	STM quantity license	LIS-UCENTER2-IOM-STM-1	H3C U-Center2.0, IOM, STM, 1 License
STM	STM license	LIS-UCENTER2-IOM-STM	H3C U-Center2.0, IOM, STM License

Installing and obtaining licenses

For more information about license request and installation, see H3C Software Products Remote Licensing Guide. After importing a license file to the H3C license management system, configure U-Center 2.0 as the license client to access the license server.

Creating a license client

1. Log in to the license server, and navigate to the Configuration > License Clients page.

2. Click Add. On the page that opens, configure the client name and password.

3. Click OK.

Configuring the client connection

This function allows you to connect the client to the license server to obtain licenses.

1. Log in to U-Center 2.0.

2. Navigate to the System > License Management > License Information page.

3. In the License Server Info area, configure the following parameters of the license server, and then click Connect:

¡ Address—Specify the IP address of the license server.

¡ Port Number—Enter the service port number of the license server. The default value is 5555.

¡ Username—Enter the client name configured on the license server.

¡ Password—Enter the client password configured on the license server.

4. You can obtain the license if the client is connected to the license server. When the connection status is Connected, click Refresh in 5 minutes to view the latest license information.

IMPORTANT:

· To avoid failure to connect to the license server, make sure the firewall is disabled for the license server when you start the client service.

· To obtain licenses successfully, make sure the license server has available licenses when you start the client service.

Viewing the license usage

1. Log in to the license server.

2. Navigate to the Clients > Client Connections page.

On the page that opens, you can view and manage clients connected to the license server.

To bulk disconnect clients from the license server, select them and then click Bulk Disconnect. To disconnect all clients, click Disconnect All.

To reclaim all licenses from a client, click Details in the Actions column for the client and then click Reclaim All on the page that opens. To reclaim a license from the client, click Reclaim for the license.

Backing up and restoring the configuration

You can back up and restore configuration for U-Center 2.0 components on Unified Platform. For more information, see H3C Unified Platform Deployment Guide.

Recovering the cluster from failures

On Unified Platform, you can recover the cluster when a failure occurs. For more information, see H3C Unified Platform Deployment Guide.

Upgrading U-Center 2.0

TIP:

· Before upgrading U-Center 2.0, upgrade Matrix and Unified Platform to the corresponding version. For more information about upgrading Matrix and Unified Platform, see H3C Unified Platform Deployment Guide.

· Follow the installation sequence of application packages to upgrade the applications.

U-Center 2.0 (E07xx) supports rolling update. You can upgrade U-Center 2.0 directly by deploying the latest version of the U-Center 2.0 application package. The upgrade upgrades U-Center 2.0 only with configuration retained and does not affect any installed components. If the U-Center 2.0 upgrade fails, uninstall and reinstall it.

To upgrade U-Center 2.0:

1. Enter https://ip_address:8443/matrix/ui in your browser to log in to Matrix. ip_address represents the configured northbound service VIP.

2. On the top navigation bar, select the Deploy tab.

3. From the left navigation tree, select Application to enter the application list page.

4. Click Deploy Applications.

5. Click Upload and upload the application installation packages in the pop-up window. After the upload is complete, the application software packages will be displayed in the list.

6. Deploy the application installation packages. For more information, see "Installing U-Center 2.0."

Uninstalling U-Center 2.0

IMPORTANT:

· The uninstallation of a single component or application will affect the use of other components or applications. Please uninstall a component or application with caution.

· After you uninstall and reinstall U-Center 2.0, you must clear the content in the /var/lib/ssdata/ directory on each node.

To retain the component configuration and data, use the backup function before uninstallation. For more information about the backup function, see "Backing up and restoring the configuration."

To uninstall the applications in the revered order they are installed.

To uninstall a single application:

1. Enter https://ip_address:8443/matrix/ui in the browser to log in to Matrix. Replace ip_address with the northbound service VIP.

2. On the top navigation bar, click DEPLOY.

3. From the navigation pane, select Applications.

4. Click the icon in the Actions column for an application.

5. In the dialog box that opens, click OK.

FAQ

How can I prepare a disk partition for GlusterFS on a node?

Prepare a disk partition for GlusterFS on each node in the cluster, and record the disk partition name for future use.

To prepare a disk partition for GlusterFS on a node, perform one of the following tasks:

Manually create a new disk partition.

a. Reserve sufficient disk space for GlusterFS when you install the operating system.

b. After the operating system is installed, execute the fdisk command to create a disk partition.

Figure 2 gives an example of how to create a 250 GB disk partition /dev/sda7 on disk sda. If the system fails to obtain the partition list, execute the reboot command to restart the node.

Figure 2 Creating a disk partition

Use an existing disk partition.

If an existing disk partition with 250 GB or more capacity has not been used or mounted, you can clear the disk partition and use it for GlusterFS, for example, /dev/sda7 as shown in Figure 3. To clear the disk partition, execute the wipefs -a /dev/sda7 command.

Figure 3 Disk partition information

Prepare an independent disk for GlusterFS.

Execute the wipefs -a command to clear the disk before using it for GlusterFS.

Figure 4 Clearing disk

I have activated IOM basic and quantity licenses, but the application incorporation fails. An error massage is displayed that the number of monitors exceeds license limit. Why does this happen?

IOM depends on COLLECTPLAT. You need to activate CMDB quantity license of COLLECTPLAT.

Is there any additional information that I should pay attention to?

After the IOP license (H3C U-Center2.0, Intelligent Operations Platform Software) is registered, two license names, UCENTER-UCENTER-UCD and UCENTER-UCENTER2, are generated.

How can I manually modifying the ES values in the back end?

1. Execute the kubectl edit sts elasticsearch-node-1 -n service-software command.

2. Locate ES_JAVA_OPTS in the env entry, and change its value to -Xms8g -Xmx8g, where 8g can be adjusted as needed. Make sure the value following Xms is the same as that following Xmx.

3. Locate memory in the limits entry, and change its value from 2G to 12G. You can adjust the value 12G as needed. Make sure the value is at least 3G greater than the value following Xms or Xmx.

4. Save the configuration and exit.

5. Execute the kubectl edit sts elasticsearch-node-2 -n service-software command. Repeat steps 2 through 4.

6. Execute the kubectl edit sts elasticsearch-node-3 -n service-software command. Repeat steps 2 through 4.

7. After modification, enter any elasticsearch pod, and execute the curl ‘elasticsearch-http-service:9200/_cat/health?v’ command to view the cluster state. When the status is green or yellow in the returned value, the cluster is available. If a large amount of data exist, ES takes a certain period of time to restore data after you complete the preceding steps.

How can I identify the enabling status for the RAID controller cache policies when configuring a RAID array for servers if the IOPS of a disk is as low as 1k?

When configuring a RAID array for servers, you must enable the RAID controller cache policies. Table 8 shows only some parameters in the RAID configuration. In the actual configuration, see the storage controller user guide for the corresponding server model.

Table 8 Parameters

Parameter	Description
Array Label	Name of the RAID array. The default is DefaultValue0.
Stripe Size	Strip size, which determines the data block size of a stripe on each drive.
Array Size Selection	RAID array capacity.
Read Cache	Read cache policy status. Options include Enabled and Disabled.
Write Cache	Write cache policy status. Options include: · Enable Always—Always enables the write cache. Without a supercapacitor installed, this status might cause data loss if power supply fails. · Enable With Backup Unit—Disables the write cache when the supercapacitor is absent or not ready. · Disabled—Disables the write cache.
Create RAID via	Operation after the RAID array is created. Options include Quick Init, Skip Init, Build/Verify, and Clear.

H3C U-Center 2.0 Deployment Guide(on Unified Platform E0713)-5W102

Preparing for deployment

IP address assignment

Software requirements

Pre-installation checklist

(Optional.) Deploying the CMDB component

Creating a license client

Configuring the client connection

Viewing the license usage

Backing up and restoring the configuration

Uninstalling U-Center 2.0

I have activated IOM basic and quantity licenses, but the application incorporation fails. An error massage is displayed that the number of monitors exceeds license limit. Why does this happen?

Is there any additional information that I should pay attention to?

How can I identify the enabling status for the RAID controller cache policies when configuring a RAID array for servers if the IOPS of a disk is as low as 1k?

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us