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, STM, NSM, ODA, and APA components. It supports standalone deployment on one master node and cluster deployment on three master nodes and N worker nodes (N ≥ 0).

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.
	Configure cluster parameters.	Required. 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 U-Center 2.0.	Deploy various components of U-Center 2.0.	Convergence deployment is supported. For more information, see “Installing U-Center 2.0.”

Preparing for deployment

IP address assignment

IMPORTANT:

External DM database does not support IPv6 or dual-stack deployment.

IMPORTANT:

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

· Before deploying, upgrading, or rebuilding a cluster, make sure all 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 NICs not the members of the bonding interface have IPs assigned or the ONBOOT value set to no.

Table 2 shows the single-stack IP address assignment for U-Center 2.0 deployment. Table 3 shows the dual-stack IP address assignment U-Center 2.0 deployment.

Single-stack IP address assignment

The IP addresses can be IPv4 or IPv6 addresses.

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.

Dual-stack IP address assignment

Table 3 Networking details

IP address	Description	Remarks
Master node 1 IP	IPv4 and IPv6 addresses 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	IPv4 and IPv6 addresses assigned to the master node installed with an operating system.
Master node 3 IP	IPv4 and IPv6 addresses assigned to the master node installed with an operating system.
Northbound service VIP (IPv4 or IPv6)	The unified external access address for all applications deployed through Matrix.	Required. The northbound service VIPs must be on the same subnet as the master nodes, and are assigned IPv4 and IPv6 addresses separately. For the northbound service VIPs, you must specify a minimum of one IPv4 address or IPv6 address. You cannot configure two IP addresses of the same IP version.
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 4 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.

A required application package must be installed for U-Center 2.0 to operate normally. An optional application package can be installed if you need the corresponding function.

NOTE:

Support for the x86 and ARM installation packages varies by component and version. For more information, see the release notes.

Table 4 Installation packages

Name	Description	Product package	Remarks	Dependencies
common_Linux-version_platform.iso	H3C Linux OS installation package	N/A	Required.	N/A
UDTP_Middle_version_platform.zip	Middleware image repository, including databases and message queues.	PLAT	Required. Deployed on Matrix.	N/A
UDTP_GlusterFS_version_platform.zip	Provides local shared storage functionalities: · Provides a universal tool for creating storage volumes. · Automatically repairs GFS anomalies caused by node anomalies and brain splits.	PLAT	Required. Deployed on Matrix.	N/A
UDTP_Core_version_platform.zip	Provides portal, unified authentication, user management, service gateway, service data backup & restoration, application deployment management (installation, upgrade, expansion, and uninstallation), help center, permissions, operation groups, roles, role groups, unified resource UUIDs, license query and display, configuration center, and log service.	PLAT	Required. Deployed on Matrix.	Middle, GlusterFS
BMP_IMonitor_version_platform.zip	Provides self-monitoring services, including: · Monitors hosts and containers, monitors the indexes of multiple middleware products, including etcd, GlusterFS, and MySQL, and provides a visual interface. · Provides the index alarm function. After you configure the level 1 and level 2 thresholds of the specified index, an alarm will be sent when the level 1 or level 2 threshold is reached. · Displays the list of K8s workloads, allows you to view basic information of the workloads, and supports multiple search options.	PLAT	Optional. Deployed on Matrix. The host and container monitoring function provided by the component corresponds to the host and pod monitoring function of Matrix versions earlier than Unified Platform E0713.	Core
BMP_Report_version_platform.zip	Provides the IAR report function, allows other components to register report templates, and adds report tasks: · Report templates · Report tasks	PLAT	Optional. Deployed on Matrix. Corresponds to the report function in the general_PLAT_kernel-base_2.0_<version>.zip package for versions earlier than Unified Platform E0713.	N/A
BMP_QuickReport_version_platform.zip	Provides more convenient report customization functions, allows service components to register data sources, and generates charts based on data source configuration. Including: · Data source management · Template management · Task management	PLAT	Optional. Deployed on Matrix. Corresponds to Unified Platform E0721 and earlier versions.	N/A
U-Center_Report _version_platform.zip	Provides more comprehensive fast report functions, adding features such as datasets and charts: · Dataset management · Chart management · Custom inquiry · Report templates · Report tasks	REPORT	Optional. Deployed on Matrix. Corresponds to Unified Platform E0721 and later versions.	UDTP_Middle_version_platform.zip UDTP_GlusterFS_version_platform.zip UDTP_Core_version_platform.zip
BMP_Alarm_version_platform.zip	Provides basic alarm services, including receiving traps, upgrading to alarms, and forwarding alarms via SMS, email, WeChat, and WeCom.	PLAT	Optional. Deployed on Matrix. Corresponds to the alarm function in the general_PLAT_kernel-base_2.0_<version>.zip package for versions earlier than Unified Platform E0713.	Report (BMP_Report_version_platform.zip)
BMP_Certificate_version_platform.zip	Provides the certificate management services, including: · Requesting certificates · Uploading certificates · Downloading certificates	PLAT	Optional. Deployed on Matrix.	Alarm
BMP_Dashboard_version_platform.zip	Provides the dashboard framework capabilities, including: · Dashboard management · Dashboard settings · Area dashboard · Default dashboard · Service component management	PLAT	Optional. Deployed on Matrix.	The dashboard application requires installation of both the dashboard and widget packages, with the dashboard installed before the widget.
BMP_Widget_version_platform.zip	Provides Unified Platform dashboard- and alarm-related widgets, and backend data interfaces	PLAT	Optional. Deployed on Matrix.	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	Provides NETCONF channel services, including NETCONF connection maintenance for Unified Platform systems and devices, and NETCONF message issuing and subscriptions.	PLAT	Optional. Deployed on Matrix.	N/A
BMP_OneClickCheck_version_platform.zip	· Provides the one-click check function to check the basic CPU, memory, database status, and process service status of the operating system, the operation status of the basic services (such as cluster) on which the controller depends, and the operating status of user services such as network elements and vNetworks, and generate relevant check reports. · Supports setting the time for scheduled check and setting the thresholds for check items.	PLAT	Not supported in the current software version.	Alarm
BMP_RDR_version_platform.zip	Remote disaster recovery system (RDRS), which provides primary/secondary disaster recovery between two remote sites located in different areas. The components in the primary and secondary sites back up each other. When the RDRS is operating properly, it synchronizes data from the in-service site to the remote site in real time. This ensures data consistency between the two sites. You can configure the switchover mode as manual switchover or auto switchover with arbitration. When the in-service site encounters failures (for example, power interruption, network failure, or link failure), the other site takes over to ensure service continuity and reduce losses.	PLAT	Not supported in the current software version.	Alarm
BMP_Snapshot_version_platform.zip	· Snapshot management, which allows you to configure snapshots for tenant-specific or network-wide services, and compare and roll back snapshots. · Enables quick, fine-grained repairs during the configuration change process in case of configuration errors or omissions.	PLAT	Optional. Deployed on Matrix.	N/A
BMP_Subscription_version_platform.zip	Subscription service, which provides capabilities of forwarding via SMS, email, WeChat, and WeCom.	PLAT	Optional. Deployed on Matrix. Corresponds to the forwarding function in the general_PLAT_kernel-base_2.0_<version>.zip package for versions earlier than Unified Platform E0713.	Alarm
BMP_Suspension_version_platform.zip	Adds maintenance tags to resources, including network devices, servers, storage devices, virtualization systems, containers, operating systems, databases, middleware products, and other resources. Allows you to configure relevant parameters to enable the system to perform related operations on resources.	PLAT	Optional.	Alarm
BMP_Template_version_platform.zip	· Monitor template feature, which provides monitor setting management and template-based monitor index selection, threshold settings, and collection interval settings. You can select monitor templates in the monitor and auto discovery components. · Access parameter template feature, which provides template-based management of the parameters used by the system to access networks, servers, storage devices, virtualization systems, containers, operating systems, databases, middleware products, or other resources.	PLAT	Optional. Deployed on Matrix. Corresponds to the template function in the general_PLAT_kernel-base_2.0_<version>.zip package for versions earlier than Unified Platform E0713.	N/A
BMP_WebSocket_version_platform.zip	Southbound WebSocket channel service: · Manages the establishment, authentication, and termination of device WebSocket connections. · Delivers, responds to, and subscribes to messages.	PLAT	Optional. Deployed on Matrix.	N/A
BMP_RDRArbitrator_version_platform.zip	Third-party arbitration system installation package for RDRS, which provides automatic primary/secondary switchover in the RDRS scenario.	PLAT	Optional. Deployed on Matrix.	For the procedure of deploying the arbitration service, see H3C Unified Platform Deployment Guide.
BMP_Region_version_platform.zip	Provides hierarchical site management and hub channel service.	PLAT	Optional. Deployed on Matrix.	For the module to send alarms, you need also install Alarm.
BMP_Syslog_version_platform.zip	Receives, parses, stores, and generates alarms for Syslog data from network devices.	PLAT	Optional. Deployed on Matrix.	Alarm
BMP_Incident_version_platform.zip	Provides the alarm aggregation feature, including: · Configuring alarm aggregation rules: The system aggregates alarms according to the configured rules to generate aggregate alarms. · Viewing aggregate alarms: Displays aggregate alarms on the active alarms page.	PLAT	Optional. Deployed on Matrix.	Alarm
BMP_AIOPS_version_platform.zip	Installation package for the time-series data trend prediction and anomaly detection services.	PLAT	Optional. Deployed on Matrix.	N/A
GAP_version_platform.zip	Implements data transmission from the lower-level node to the upper-level node in a two-level network environment.	PLAT	Optional. For the installing procedures, see H3C GAP Component Deployment Guide.	Region
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	Optional.	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	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · accesstemp, monitortemp (BMP_Template_version_platform.zip) · alarm (BMP_Alarm_version_platform.zip) · register, etcd (U-Center_UCP_version_platform.zip)
U-Center_IOM_version_platform.zip	Installation package for the application monitoring 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) · glusterfs (UDTP_GlusterFS_version_platform.zip) · collectplat (U-Center_COLLECTPLAT_version_platform.zip)
U-Center_ADDM_version_platform.zip	Installation package for the auto-discovery service.	IOM	Optional.	register, etcd(U-Center_UCP_version_platform.zip)
U-Center_AGENT_version_platform.zip	Installation package for the agent service.	IOM	Optional.	· U-Center_COLLECTPLAT_version_platform.zip · register, etcd(U-Center_UCP_version_platform.zip)
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_LEARNWARE_version_platform.zip	Provides management of dynamic threshold and capacity prediction tasks.	IOM	Optional.	BMP_AIOPS_version_platform.zip
U-Center_CMDB_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) · BMP_Report_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 service dialing test 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)
U-Center_STM_Collector_version_platform.zip	Installation package for the service dialing test collector	STM	Optional.	· glusterfs (UDTP_GlusterFS_version_platform.zip) · portal, kernel (UDTP_Core_version_platform.zip) · kernel-base (BMP_Template_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 NQA dialing test 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_NQA_Collector_version_platform.zip	Installation package for the NQA dialing test collector.	STM	Optional.	· glusterfs (UDTP_GlusterFS_version_platform.zip) · portal, kernel (UDTP_Core_version_platform.zip) · kernel-base (BMP_Template_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_PLAT_version_platform.zip	Installation package for the basic function service.	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)
U-Center_AOM_CCMS_version_platform.zip	Installation package for CCMS.	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) · U-Center_AOM_PLAT_version_platform.zip
U-Center_AOM_INI_version_platform.zip	Installation package for INI.	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) · U-Center_AOM_PLAT_version_platform.zip
U-Center_AOM_IPMS_version_platform.zip	Installation package for IPMS.	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) · U-Center_AOM_PLAT_version_platform.zip
U-Center_AOM_PROBE_version_platform.zip	Installation package for the collection client Web service	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) · U-Center_AOM_PLAT_version_platform.zip (not dependent on this installation package for deployment through application deployment)
U-Center_AOM_SFTP_version_platform.zip	Installation package for the SFTP file server.	AOM	Optional.	· ucp (U-Center_UCP_version_platform.zip)
U-Center_ODA_Trino_version_platform.zip	Installation package for the operation data analysis query federation component.	ODA	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · ucp (U-Center_UCP_version_platform.zip) · metasevice (U-Center_ODA_MetaService_version_platform.zip)
U-Center_ODA_Alarmize_version_platform.zip	Installation package for the operation data analysis alarm generation service.	ODA	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · ucp (U-Center_UCP_version_platform.zip) · alarm (BMP_Alarm_version_platform.zip)
U-Center_ODA_Capacity_version_platform.zip	Installation package for the operation data analysis capacity management component.	ODA	Optional.	· 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) · learnware (U-Center_LEARNWARE_version_platform.zip) · alarmize (U-Center_ODA_Alarmize_version_platform.zip)
U-Center_ODA_Scheduler_version_platform.zip	Installation package for the operation data analysis scheduling engine.	ODA	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · ucp (U-Center_UCP_version_platform.zip)
U-Center_ODA_Flink_version_platform.zip	Installation package for the operation data analysis computing engine.	ODA	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · ucp (U-Center_UCP_version_platform.zip) · alarm (BMP_Alarm_version_platform.zip)
U-Center_ODA_Studio_version_platform.zip	Installation package for the operation data analysis data development platform.	ODA	Optional.	· portal, kernel (UDTP_Core_version_platform.zip) · ucp (U-Center_UCP_version_platform.zip) · metasevice (U-Center_ODA_MetaService_version_platform.zip) · scheduler (U-Center_ODA_Scheduler_version_platform.zip) · clickhouse (U-Center_CLICKHOUSE_version_platform.zip)
U-Center_APA_version_platform.zip	Installation package for the application performance monitoring service.	APA	Optional.	· ucp (U-Center_UCP_version_platform.zip) · collectplat (U-Center_COLLECTPLAT_version_platform.zip) · clickhouse (U-Center_CLICKHOUSE_version_platform.zip)

Server requirements

Hardware requirements

You can contact Technical Support for hardware configuration evaluation.

Software requirements

Table 5 Available Operating systems

Architecture	Operating system
x86	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
ARM	H3Linux V2.0.2
ARM	Kylin-Server-10-SP2

IMPORTANT:

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

· Support for the x86 and ARM installation packages varies by component and version. For more information, see the release notes.

Disk partitioning

The following disk partitioning configuration is for illustration only. Configure disk partitioning based on the actual situation.

Table 6 Disk partitioning configuration

Mount point	Preset capacity	Boot mode	File system	Description
/var/lib/docker	400 GiB	BIOS/UEFI	xfs	· Determine the capacity based on Docker operation. Expand or reduce the capacity based on the incremental disk capacity occupied by deploying components in the actual service scenario. · If the disk space is sufficient, you can expand the capacity appropriately.
/boot	1024 MiB	BIOS/UEFI	xfs	N/A
swap	1024 MiB	BIOS/UEFI	swap	N/A
/var/lib/ssdata	450 GiB	BIOS/UEFI	xfs	· This partition is for PXC, Kafka, and ZooKeeper. Theoretically, only Unified Platform uses this partition. For other components to use it, expand or reduce the capacity. · If the disk space is sufficient, you can expand the capacity appropriately.
/	400 GiB	BIOS/UEFI	xfs	· This partition is for Matrix, including K8s, Harbor, and installation packages of other components. Expand or reduce the capacity based on the size of component images. · If the disk space is sufficient, you can expand the capacity appropriately. As a best practice, do not store service data in the root directory.
/opt/matrix/app/data/base-service/backupRecovery	The backup directory size requirements for U-Center components vary by deployment scale, as shown in Table 7.	BIOS/UEFI	xfs	This partition is for service backup data. Expand or reduce the capacity based on the service backup data size of components.
/boot/efi	200 MiB	UEFI	EFI System Partition	This partition is required in UEFI mode.
/var/lib/etcd	50 GiB	BIOS/UEFI	xfs	· As a best practice to ensure successful manual partitioning, mount this partition on a separated disk with the capacity of 51 GB or more. · This partition is required for master nodes but not for worker nodes.
Reserved disk space	N/A	N/A	N/A	· This partition is for GlusterFS. Unified Platform in standard mode requires 140 GB. Make sure the preserved capacity is greater than 140 GB. For other components to use it, expand or reduce the capacity based on the disk size required for the components. This partition must be a standard partition. · This partition is required for master nodes but not for worker nodes.

Table 7 Size requirements for backup directories of components

Component	Default scale	Large scale	Medium scale	Small scale
CMDB	10 GiB	10 GiB	10 GiB	10 GiB
IOM	400 GiB*6	400 GiB*6	100 GiB*6	20 GiB*6
STM	8 GiB*6	8 GiB*6	3 GiB*6	1 GiB*6
AOM	-	40 GiB*6	10 GiB*6	3 GiB*6
ITSM	40 GiB*6	40 GiB*6	10 GiB*6	3 GiB*6
BSM	10 GiB*6	10 GiB*6	5 GiB*6	2 GiB*6
NTA	5 GiB*6	5 GiB*6	2 GiB*6	1 GiB*6
UEM	10 GiB*6	10 GiB*6	5 GiB*6	2 GiB*6
QuickReport	20 GiB*6	20 GiB*6	15 GiB*6	10 GiB*6
ODA	5 GiB*6	5 GiB*6	2 GiB*6	1 GiB*6
APA	N/A	N/A	N/A	N/A

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 8 shows the check list for the installation requirements. Make sure the U-Center 2.0 installation requirements are met.

Table 8 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.

· To ensure successful installation, do not press Scroll Lock during the installation.

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

1. Identify the uploaded installation packages.

[root@node1~]# cd /opt/matrix/app/install/packages/

[root@node1~]# ls

BMP_Report_E0722_x86.zip UDTP_Core_E0722_x86.zip

…

2. Obtain the MD5 value of an installation package, for example, UDTP_Core_E0722_x86.zip.

[root@node1~]# md5sum UDTP_Core_E0722_x86.zip

2b8daa20bfec12b199192e2f6e6fdeac UDTP_Core_E0722_x86.zip

3. Compare the obtained MD5 value with the MD5 value released with the software. If they are the same, the installation package is correct.

Installing Unified Platform

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

To deploy Unified Platform:

1. Install the operating system and dependencies.

2. Install Matrix.

3. Create a cluster and configure cluster parameters.

4. Deploy Unified Platform components.

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

Installing U-Center 2.0

CAUTION:

U-Center 2.0 components (IOM, CMDB, BSM, STM, ITSM, AOM, NTA, NSM, ODA, APA, and QuickReport) of version E0715 or later must be installed on the convergence deployment page.

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix.

The default username is admin and the default password is Pwd@12345. If the operating system password has been set, enter the set password. The ip_address parameter specifies the northbound service VIP.

2. On the top navigation bar, click DEPLOY.

3. From the navigation pane, select Convergence Deployment.

4. Click Packages Management to access the page for uploading installation packages. On this page, you can upload and delete installation packages for convergence deployment.

5. Click Upload. In the window that opens, click Select Files, and upload installation packages.

You can bulk upload application installation packages.

When you install U-Center 2.0, follow these restrictions and guidelines:

· After uploading the installation package, see the following sections for the specific deployment procedures of each component in U-Center 2.0.

· On the convergence deployment page, you can view, expand, upgrade, and perform other operations on the specified applications.

· Registration of configuration data carried in the installation packages is required in the following scenarios:

¡ If you upload the installation packages without using the Web interface, select the packages and then click Register Data.

¡ If multiple versions exist for an installation package, register data for the version to be deployed.

· If the components that have been installed through application deployment do not support convergence deployment, perform the following tasks before performing operations such as viewing details, expanding, and upgrading:

a. Upload the convergence deployment packages of the related application components.

b. After the upload is completed, click Data Synchronization to synchronize the data from the Applications page to the Convergence Deployment page.

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

· 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 in convergence mode

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

NOTE:

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

To deploy the IOM component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_IOM_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

5. On the application selection page, all scenarios are selected by default. If you select some scenarios, the page displays only applications for the selected scenarios and Unified Platform, and applications required for the selected scenarios are selected.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

If you select an application with dependent applications, its dependent applications will be automatically selected. If a dependent application is not deployed or not included in the current installation package, the system will prompt relevant information.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page.

Configure predefined parameters, and select nodes for deployment.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the CMDB component in convergence mode

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

To deploy the CMDB component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_CMDB_2.0_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page.

Configure predefined parameters, and select nodes for deployment.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the BSM component in convergence mode

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

NOTE:

You can select and install all of the following packages simultaneously: BSM, UEM, STM, and NQA.

To deploy the BSM component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_BSM_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for BSM.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the ITSM component in convergence mode

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

NOTE:

Deploy the ITSM component separately. Do not select ITSM together with other installation packages.

To deploy the ITSM component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_ITSM_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for ITSM.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the NTA component in convergence mode

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

NOTE:

NTA depends on NTA, NSM_FCAPS-Res, UCP, and CLICKHOUSE installation packages. You must deploy them in the following order: NSM_FCAPS-Res, UCP, CLICKHOUSE, NTA.

To deploy the NTA component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_NTA_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for NTA.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the AOM component in convergence mode

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

NOTE:

· To install AOM, first install the AOM_PLAT component, and then install the other components in any order. IPMS, INI, CCMS, 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 400 devices.

· U-Center_AOM_JOB_version_platform.zip depends on U-Center_IOM_version_platform.zip, U-Center_AOM_SFTP_version_platform.zip and other installation packages, as described in "Installation packages." Deploy the JOB package together with its dependent packages.

To deploy the AOM component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_AOM_PLAT_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page.

Configure predefined parameters, and select nodes for deployment.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the STM component in convergence mode

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

NOTE:

You can select and install all of the following packages simultaneously: BSM, UEM, STM, and NQA.

To deploy the STM component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_STM_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for STM.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the QuickReport component in convergence mode

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

To deploy the QuickReport component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_Report_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the Unified Platform scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. You do not need to configure the resource scale for QuickReport.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for QuickReport.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the ODA component in convergence mode

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

To deploy the NTA component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_ ODA _version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for ODA.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

(Optional.) Deploying the APA component in convergence mode

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

To deploy the APA component:

1. Upload the convergence deployment packages to be deployed. Take U-Center_APA_version_platform.zip as an example.

2. Verify the package information in the package management list.

3. Click Back.

4. Click Install.

¡ All: Related applications of Unified Platform and all other components.

¡ U-Center Scenario: Related applications of Unified Platform and U-Center components.

6. In the U-Center scenario area, select the applications to be deployed.

7. Click Next to access the package selection page, and select the convergence deployment packages to be installed.

The system will verify the packages.

8. After verification, click Next to access the resource configuration page. Select the resource scale for components based on the planned network and service scales.

9. Click Next to access the parameter configuration page. You do not need to configure any parameter for APA.

10. Click Deploy. In the dialog box that opens, confirm the applications to be installed.

11. After confirmation, click OK to start deployment.

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 9 describes the licenses for each component of U-Center 2.0.

Table 9 NSM licenses

Component	License description	Product code	Product description
NSM	Network basic license	LIS-IMC9-NSM	H3C U-Center2.0, NSM Network Device Management License
	Network quantity license	LIS-IMC9-NSMA-25	H3C U-Center2.0, NSM Network Device Management, 25 Licenses
		LIS-IMC9-NSMB-50	H3C U-Center2.0, NSM Network Device Management, 50 Licenses
		LIS-IMC9-NSMC-100	H3C U-Center2.0, NSM Network Device Management, 100 Licenses
		LIS-IMC9-NSMD-200	H3C U-Center2.0, NSM Network Device Management, 200 Licenses
		LIS-IMC9-NSME-500	H3C U-Center2.0, NSM Network Device Management, 500 Licenses
		LIS-IMC9-NSMF-1K	H3C U-Center2.0, NSM Network Device Management, 1000 Licenses

Table 10 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
	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
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
CM	Capacity management	LIS-UCENTER2-CM	H3C U-Center2.0 CM, Capacity Management 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
	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
	Job platform	LIS-UCENTER2-AOM-JOB	H3C U-Center2.0 AOM-Job Platform License
		LIS-UCENTER2-AOM-JOB-1	H3C U-Center2.0 AOM-Job Platform, 1 License
		LIS-UCENTER2-AOM-JOB-25	H3C U-Center2.0 AOM-Job Platform, 25 Licenses
		LIS-UCENTER2-AOM-JOB-50	H3C U-Center2.0 AOM-Job Platform, 50 Licenses
		LIS-UCENTER2-AOM-JOB-100	H3C U-Center2.0 AOM-Job Platform, 100 Licenses
		LIS-UCENTER2-AOM-JOB-200	H3C U-Center2.0 AOM-Job Platform, 200 Licenses
		LIS-UCENTER2-AOM-JOB-500	H3C U-Center2.0 AOM-Job Platform, 500 Licenses
		LIS-UCENTER2-AOM-JOB-1K	H3C U-Center2.0 AOM-Job Platform, 1000 Licenses
APA	Application performance analytics	LIS-UCENTER2-APA	H3C U-Center2.0 APA-Application Performance Analytics License
		LIS-UCENTER2-APA-1	H3C U-Center2.0 APA-Application Performance Analytics, 1 License
		LIS-UCENTER2-APA-25	H3C U-Center2.0 APA-Application Performance Analytics, 25 Licenses
		LIS-UCENTER2-APA-50	H3C U-Center2.0 APA-Application Performance Analytics, 50 Licenses
		LIS-UCENTER2-APA-100	H3C U-Center2.0 APA-Application Performance Analytics, 100 Licenses
		LIS-UCENTER2-APA-200	H3C U-Center2.0 APA-Application Performance Analytics, 200 Licenses
		LIS-UCENTER2-APA-500	H3C U-Center2.0 APA-Application Performance Analytics, 500 Licenses
		LIS-UCENTER2-APA-1K	H3C U-Center2.0 APA-Application Performance Analytics, 1000 Licenses
ODA	Operational data analytics	LIS-UCENTER2-ODA	H3C U-Center2.0 ODA-Operational Data Analytics License
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.

NOTE:

When you install the license server in H3Linux 2.0, you can install it on the same node as U-Center 2.0 or install it on a separate node. As a best practice, install them on different nodes. For more information about installing the license server, see H3C License Server Installation Guide.

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.

Rebuilding and recovering the cluster from failures

When a cluster node server operates abnormally and cannot recover due to hardware failures, replace the server. When the operating system of a node server is abnormal, reinstall the operating system and Matrix on the server. 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

CAUTION:

U-Center 2.0 components (IOM, CMDB, BSM, STM, ITSM, AOM, NTA, and NSM, ODA, APA, and QuickReport) of version E0715 or later must be upgraded on the convergence deployment page.

Restrictions and guidelines

· Before upgrade, you must back up your data.

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

· Before upgrade, first clear the browser cache and sessions.

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

Upgrading U-Center 2.0 through convergence deployment

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix.

2. On the top navigation bar, click DEPLOY.

3. From the navigation pane, select Convergence Deployment.

4. Click Install. The installation package-uploading page opens.

5. Click Upload, select Choose File in the pop-up window, and then upload the installation packages for convergence deployment. You can upload multiple application packages in bulk.

6. After the uploading is complete, click Cancel to return to the convergence deployment page.

7. Click Data Synchronization. The components to be upgraded are displayed in the list.

8. Click the icon in the Actions column for a component to be upgraded to access the upgrade page.

9. Select the installation packages to be upgraded.

If a selected installation package does not meet the dependencies and version verification of the current application, the system will prompt an error.

10. After selecting the installation packages that comply with the upgrade rules, click Upgrade to proceed with upgrade and deployment.

Uninstalling U-Center 2.0

Restrictions and guidelines

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

Uninstalling U-Center 2.0 through convergence deployment

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix.

2. On the top navigation bar, click DEPLOY.

3. From the navigation pane, select Convergence Deployment.

4. Select the applications to be uninstalled in the list, and click Uninstall.

NOTE:

· The system supports bulk uninstallation.

· If other applications depend on the application to be uninstalled, the system will also select all applications that depend on the application to ensure the integrity of the application operation. In this case, you cannot uninstall the application separately.

· If no application depends on the selected application, you can uninstall the application separately.

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

Uninstalling U-Center 2.0 through application deployment

CAUTION:

Uninstalling a single component or application might affect the operation of other components or applications. Uninstall applications with caution. For the application dependencies, see "Installation packages."

To uninstall an application through application deployment:

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.

Shutting down and powering off servers

Backing up the configuration

1. In the address bar of the browser, enter http://ip_address:30000. Then, enter the username and password.

¡ Both HTTP and HTTPS are supported. The default protocol is HTTP and the default port number is 30000. If the protocol and port number have been set, enter the set protocol and port number.

¡ The default username and password are admin and Pwd@12345, respectively. If the username and password have been set, enter the set username and password.

2. Navigate to the System > Backup & Restore page.

3. Manually back up the configuration and save the backup files locally.

For more information about the backup procedure and restrictions and guidelines, see the online help and configuration backup and restoration in H3C Unified Platform Deployment Guide.

Shutting down and powering off part of nodes

Perform this task to shut down and power off one or multiple nodes to ensure that the system is still operating correctly when U-Center is deployed in cluster mode. This task applies to scenarios such as software upgrade and hardware replacement for nodes and routine inspection.

To shut down and power off part of nodes:

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix. Then, enter the username, password, and verification code.

The default username and password are admin and Pwd@12345, respectively. If the Matrix username and password has been set, enter the set username and password.

2. Navigate to the DEPLOY > Clusters > Deploy Cluster page, select a node. To shut down and power off multiple nodes, disable these nodes one by one. That is, perform operations on a node only after the operations such as backup and restoration have been completed on another node.

3. To disable a node, click the set icon in the upper right corner of the node and click Disable.

4. After a node is disabled, execute the shutdown -h now command to shut down the node.

5. Before you power off a node, make sure the node power status is off on HDM or the power LED of the node indicates that the node is in standby state.

Shutting down and powering off all nodes

Perform this task to shut down and power off the system. This task applies to scenarios such as emergency power outages and equipment room relocations.

To shut down and power off all nodes:

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui to log in to Matrix. Then, enter the username, password, and verification code.

The default username and password are admin and Pwd@12345, respectively. If the Matrix username and password has been set, enter the set username and password.

2. Navigate to the DEPLOY > Clusters > Deploy Cluster page. Disable all master nodes in the cluster.

3. To disable a node, click the set icon in the upper right corner of the node and click Disable.

4. After a node is disabled, execute the shutdown -h now command to shut down the node.

5. Before you power off a node, make sure the node power status is off on HDM or the power LED of the node indicates that the node is in standby state.

Starting servers

Starting servers and checking the network

1. Power on and start up servers.

2. After the servers start up, execute the ip addr command to verify that the nodes and the service networks are up.

3. Verify network connectivity. Make sure a node can reach the other nodes in different network segments and the client can reach the service networks of all nodes in the cluster.

Starting the system service

1. Access Matrix from the browser.

2. Navigate to the DEPLOY > Clusters > Deploy Cluster page, and then enable nodes.

Wait for about 30 minutes. The actual waiting time might vary by data volume being processed.

3. On the top navigation pane, click DASHBOARD to view system operation statistics to identify whether the system service has started up.

4. On the top navigation pane, click OBSERVE to view workload information about Pods.

Verifying licenses and service functionalities

1. Access U-Center from the browser.

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

3. Verify that the license information is synchronized from the license server and the authorization status is normal.

4. Verify that the features of U-Center are operating correctly.

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

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

2. 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 11 shows only some parameters in the RAID configuration. In the actual configuration, see the storage controller user guide for the corresponding server model.

Table 11 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 E0722)-5W100

Preparing for deployment

IP address assignment

Software requirements

Pre-installation checklist

(Optional.) Deploying the CMDB component in convergence mode

Logging in to U-Center 2.0

Creating a license client

Configuring the client connection

Viewing the license usage

Backing up and restoring the configuration

Uninstalling U-Center 2.0

Manually create a new disk partition

Use an existing disk partition

Prepare an independent disk for GlusterFS

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us