H3C U-Center 5.0 offers a streamlined enterprise-level O&M solution, integrating monitoring, management, control, service, and analysis. It facilitates unified resource management across all ICT domains, covering cloud, network, endpoint, and security, and supports direct collection and control for large numbers of resources. In addition, it supports integration between H3C operations and management software and third-party ops tools, with a unified portal, alarms, resources, workflows, and analytics. This approach streamlines operations for maintenance personnel, ensuring efficient and comprehensive resource management.

This document provides streamlined installation and deployment guidelines for correct deployment of U-Center 5.0.

Deployment workflow

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

Table 1 shows the U-Center 5.0 deployment workflow.

Table 1 U-Center 5.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 "Software and hardware requirements."
Deploy Unified Platform.	Install an operating system and Matrix.	Required. For more information, see H3C Unified Platform Deployment Guide.
Deploy U-Center 5.0.	Deploy various components of U-Center 5.0.	Convergence deployment is supported. For more information, see "Install U-Center 5.0."

Prepare for installation

Software and hardware requirements

Hardware requirements

You can obtain the related hardware configuration requirements as follows:

· Enter data in the hardware resource calculation tool to obtain an assessment result (for reference only).

· Contact Technical Support for an assessment.

NOTE:

To ensure normal operation of the service, you must set the server's CPU power mode to high performance and disable the Patrol Read (PR) and Consistency Check (CC) features of the RAID controller. If PR and CC are not supported, you do not need to disable them. For specific operation procedures, see the product manuals for the servers and RAID controllers, or contact the technical support of the server/RAID controller vendors.

Operating system requirements

NOTE:

All nodes in the cluster must be installed with the same operating system version.

Table 2 Operating systems supported by U-Center 5.0

Version	Supported operating systems
x86	NingOS V3-1.0.2403
	Red Hat Enterprise Linux 8.8
	Red Hat Enterprise Linux 8.10
	TencentOS-Server-3.1-20240925.0-TK4
	uniontechos-server-20-1050a-amd64-UFU
	Kylin-Server-10-SP2-x86-RC01-Build09-20210524
	Kylin-Server-V10-SP3-General-Release-2303
	Kylin-Server-V10-SP3-2403-Release-20240426
ARM	NingOS V3-1.0.2403
	TencentOS-Server-3.1-20240925.0-TK4
	Kylin-Server-10-SP2-aarch64-RC01-Build09-20210524
	Kylin-Server-V10-SP3-General-Release-2303

Client requirements

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

Obtain software packages

This document uses the NingOS operating system developed by H3C for illustration. If another operating system is used, NingOS ISO files are not required.

Table 3 shows the installation package name formats. The version argument represents the software version number and the platform argument represents the CPU architecture type.

A required application package must be installed for U-Center 5.0 to operate correctly. An optional application package can be installed if you need the corresponding feature.

NOTE:

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

Table 3 Application installation packages

Product package	Installation package name	Feature description	Remarks	Dependencies
N/A	NingOS-version_platform.iso	NingOS developed by H3C	Required	N/A
PLAT	UDTP_Base_version_platform.zip	Basic service component, which provides basic functions such as convergence deployment, user management, permission management, resource management, tenant management, menu management, log center, backup & restoration, and health check.	Required	N/A
	BMP_Common_version_platform.zip	Common service component, which provides dashboard management, alarm, alarm aggregation, and alarm subscription.	Optional	N/A
	BMP_Connect_version_platform.zip	Connection service component: Provides upper- and lower-level site management, WebSocket channel management, and NETCONF channel management.	Optional	N/A
	BMP_Extension_version_platform.zip	Extended service component: Provides remote disaster recovery, snapshot rollback, certificate service, self-monitoring, intelligent algorithm library, single sign-on, and password platform functions.	Optional	BMP_Common
	BMP_Syslog_version_platform.zip	Syslog service component: Provides Syslog packet receiving and sending, Syslog browsing and aggregation, and Syslog-based alarm generation functions.	Optional	BMP_Common
REPORT	U-Center_REPORT _version_platform.zip	Provides comprehensive report functions: · Data source management · Dataset management · Chart management · Self-service query · Template management · Task management	Optional	· UDTP_Base · BMP_Common
NSM	NSM_FCAPS-Res_version_platform.zip	Incorporates network devices and manages their basic information.	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
	NSM_FCAPS-Perf_version_platform.zip	Network device performance monitoring and display	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · NSM_FCAPS-Res
	NSM_FCAPS-ICC_version_platform.zip	· Network device configuration backup · Device configuration restoration · Device software upgrade	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · NSM_FCAPS-Res
	NSM_FCAPS-Topo_version_platform.zip	Network topology display	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · NSM_FCAPS-Res · U-Center_CMDB
UCP	U-Center_UCP_BasePlat_version_platform.zip	Provides U-Center public platform services (ETCD, ops domain menu registration, visualization component).	Optional	· UDTP_Base · BMP_Common
	U-Center_UCP_CollectPlat_version_x86.zip	Provides the template, maintenance tag task, collection platform, unified resource, resource discovery, and file transfer services.	Optional	U-Center_UCP_BasePlat
	U-Center_UCP_Agent_version_platform.zip	Agent collection service	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
	U-Center_UCP_SmartCompute_version_platform.zip	Dynamic threshold and capacity	Optional	· BMP_Extension · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
	U-Center_UCP_ Capacity_version_platform.zip	Provides capacity analysis and capacity prediction based on resource monitoring indexes.	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · U-Center_UCP_SmartCompute
IOM	U-Center_IOM_version_platform.zip	IOM service, JAVA collector, and CPP collector	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
IOM	U-Center_VKVM_version_platform.zip	Server virtual remote console	Optional	U-Center_IOM
CMDB	U-Center_CMDB_version_platform.zip	Configuration management database	Optional	· UDTP_Base · BMP_Common
BSM	U-Center_BSM_version_platform.zip	Service health analysis service	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · U-Center_CMDB
BSM	U-Center_UEM_version_platform.zip	Access experience analysis service	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
ITSM	U-Center_ITSM_version_platform.zip	Process management service	Optional	· UDTP_Base · BMP_Common
NTA	U-Center_NTA_version_platform.zip	Traffic monitoring service.	Optional	· UDTP_Base · BMP_Common · NSM_FCAPS-Res · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
STM	U-Center_STM_version_platform.zip	Service dialing test management	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat
STM	U-Center_NQA_version_platform.zip	NQA dialing test management	Optional	· U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat · NSM_FCAPS-Res
AOM	U-Center_AOM_PYCOLLECTOR_version_platform.zip	AOM collector	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP · NSM_FCAPS-Res
	U-Center_AOM_INI_version_platform.zip	INI service	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP · NSM_FCAPS-Res
	U-Center_AOM_IPMS_version_platform.zip	The IPMS component module is split into two components: PIPM public IP component and IPMS IP scanning component. IPMS installation depends on PIPM.	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP · NSM_FCAPS-Res
	U-Center_AOM_PIPM_version_platform.zip	The IPMS component module is split into two components: PIPM public IP component and IPMS IP scanning component. IPMS installation depends on PIPM.	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP · NSM_FCAPS-Res
	U-Center_AOM_JOB_version_platform.zip	Job platform	Optional	· UDTP_Base · BMP_Common · BMP_Connect · U-Center_UCP · NSM_FCAPS-Res
ODA	U-Center_ODA_DataDevelop_version_platform.zip	Ops data development service	Optional	· U-Center_UCP_BasePlat · U-Center_Report
	U-Center_ODA_DataAnalysis_version_platform.zip	Ops data analysis service	Optional	· U-Center_UCP_BasePlat · U-Center_Report
	U-Center_ODA_Capacity_version_platform.zip	Capacity management	Optional	· BMP_Extension · U-Center_UCP_BasePlat · U-Center_UCP_CollectPlat_version_x86.zip · U-Center_UCP_SmartCompute
AIOps-Copilot	AIOps-Copilot_version_platform.zip	Provide AIOps based on large models.	Optional	· UDTP_Base · BMP_Common

Verify software packages

Before you install the software, execute the following commands to verify the MD5 value of each software package to ensure its integrity and correctness.

1. View the uploaded installation packages.

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

[root@node1~]# ls

U-Center_IOM_E7101_x86.zip U-Center_REPORT_E7101_x86.zip

…

2. View the MD5 values of the installation packages, for example, U-Center_IOM_E7101_x86.zip.

[root@node1~]# md5sum U-Center_IOM_E7101_x86.zip

ea9303af38fc328682816a25e95acaac U-Center_IOM_E7101_x86.zip

3. Compare the MD5 value obtained in the preceding steps with the MD5 value of the released software image file. If they match, the software package is correct.

Plan the installation

Disk partitioning

Configure disk partitions based on the local storage space for a single master node in the result calculated with the hardware resource calculation tool.

Partitioning guidelines for seasqlplus-uc:

· The seasqlplus-uc data disks store historical performance monitoring data.

· The hardware resource calculation tool can automatically determine whether to configure an independent partition for seasqlplus-uc.

¡ When the equivalent NE count is less than 2000 (equivalent NE count = NMS managed NE count + IOM managed resource count + NTA interface count × 10), you do not need to configure an independent seasqlplus-uc partition.

¡ When the equivalent NE count exceeds 2000, you must configure a seasqlplus-uc partition and mount independent disks. The reason is that seasqlplus-uc might cause high disk IO when the service volume is high. If it shares a disk with other services, normal operation of other services might be affected.

· After you mount independent disks for seasqlplus-uc, you cannot allocate the remaining space to other partitions.

· For more information about mounting independent disks for seasqlplus-uc, see "How can I mount independent disks for seasqlplus-uc?"

Plan the network

Network plan

In the Matrix cluster deployment mode, U-Center 5.0 requires a minimum of three master nodes and n worker nodes (where value n is determined by task load and must be greater than or equal to 0). A typical network plan is as shown in the figure below:

Figure 1 Network plan

IP address plan

CAUTION:

In a service scenario where multiple NICs are required, follow these restrictions and guidelines:

· Before you deploy the cluster, make sure the NIC used by the cluster is the first one detected by the ifconfig command.

· If this condition is not met, make sure the cluster uses the previously configured NIC that meets the following conditions:

Condition 1: The NIC is down and the onboot option is set to no.

Condition 2: The NIC is in up state, has an IP configured, and has a security policy configured.

U-Center 5.0 supports IPv4 deployment. Table 4 shows the IP address planning.

Table 4 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 deployment mode.) The IP addresses of all master nodes assigned to the same 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	IP address assigned to a worker node.	Optional The IP addresses of worker nodes must be on the same subnet as the IP addresses of master nodes in the same cluster.

Pre-installation checklist

Table 5 shows the checklist for the installation requirements. Make sure the U-Center 5.0 installation requirements are met.

Table 5 Pre-installation checklist

Item		Requirements
Server or VM	Hardware	Verify that the CPU, memory, disk, and NIC requirements are met.
Server or VM	Software	Please check the following items: · Verify that the operating system version meets the requirements · Verify that the system time settings are configured correctly. As a best practice, configure NTP on each node, specify the same time source for all the nodes, and ensure time consistency with the NTP server. · Verify that the server has disk arrays configured.
Client		Verify that the browser version meets the requirements.
Server and operating system compatibility		To view the compatibility matrix for H3C servers and operating systems, click the following link: http://www.h3c.com/cn/home/qr/default.htm?id=367

CAUTION:

· 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 of VMware. 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. 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 5.0 deployment.

· To avoid cluster exceptions, do not edit the system time after cluster deployment is completed.

Install Unified Platform

CAUTION:

Before you deploy Unified Platform in a non-root (such as the admin) environment, you must execute the following commands to manually create the log directory as the root user and edit the owner:

mkdir -p /var/log/matrix-diag/deploy/ && chown admin:wheel /var/log/matrix-diag/deploy/

ll -d /var/log/matrix-diag/deploy/

If the cluster has multiple nodes, perform this operation on all nodes.

Before deploying U-Center 5.0, first deploy Unified Platform and then deploy U-Center 5.0 components on Matrix of Unified Platform.

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

Install U-Center 5.0

Installation guidelines

· The time taken for installation varies by network scale and component. For a small-scale standalone deployment, the installation typically takes 0.6 to 0.7 hours.

· For standalone Unified Platform deployment, U-Center can be deployed in standard mode or proxy mode. For more information about the installation procedures, see "Install applications (standard mode)" and "Install applications (proxy mode)."

Install applications (standard mode)

Table 3 shows the installation packages for U-Center components. You can deploy the installation packages as needed.

Upload installation packages

NOTE:

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

· You must upload installation packages on the Matrix front end. Upload through the backend is strictly prohibited. If upload through the backend is required in specific network environments, contact the technical support.

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui, and enter the Matrix username and password (the default username is admin) to log in to Matrix. The ip_address parameter specifies the northbound service VIP.

2. Navigate to the DEPLOY > Convergence Deployment page.

Figure 2 Convergence deployment

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

Figure 3 Managing the installation packages

4. Click Upload. In the dialog box that opens, click Select Files, select one or multiple installation package files, and then click Upload. After the upload is complete, the system automatically returns to installation package management page.

Figure 4 Upload installation packages

Start installation

1. After the installation package upload is complete, return to the convergence deployment page.

2. Click Install to access the Select Applications page.

3. Select scenes. The scenes predefined by the system are U-Center Unified Ops, U-Center Basic NMS, and U-Center ICT Monitor. Select one or multiple scenes as needed. The system will automatically select the uploaded installation packages, and the applications recommended for the selected scenes. You can cancel or add other applications as needed.

4. You can select one or multiple applications to install as needed.

NOTE:

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

Figure 5 Select applications

5. Click Next to access the installation package selection page. The system automatically selects the default installation packages. You can also manually select installation packages. After selection, the system will validate the installation packages.

Figure 6 Select installation package

6. After the installation packages pass the validation, click Next to access the resource configuration page, where you can select an appropriate resource level. Select the resource level based on the result calculated with the hardware resource calculation tool.

Figure 7 Configure resources

7. Click Next to access the parameter configuration page. Configure parameters as needed. Some parameters are not required. To configure parameters, you must select nodes for deployment. In the standalone deployment mode, only one node exists, which must be selected.

Figure 8 Configure parameters

8. Click Deploy. In the dialog box that opens, confirm the dependent middleware nodes and the deployed applications. If you have selected nodes for deployment in the previous step, you must also confirm the application nodes. Then click OK to start deployment.

Figure 9 Confirm

Figure 10 Deployment progress

9. After the deployment succeeds, the system automatically returns to the convergence deployment page, where you can view the deployed applications.

Figure 11 View deployed applications

Install applications (proxy mode)

Proxy deployment guidelines

Proxy deployment requires a minimum of two environments: U-Center 5.0 Server (Unified Platform environment deployed in standard mode) and U-Center 5.0 Proxy (Unified Platform environment deployed in proxy mode). As a lower-level environment to the server, the proxy provides a unified operation entry point. All operations are performed on the server side, and the proxy is only responsible for data collection.

The proxy deployment mode supports installing only some of the U-Center components as shown in Table 6. You can deploy the installation packages as needed.

Table 6 Application installation packages in proxy deployment mode

Product package	Installation package name	Version
NSM	NSM_FCAPS-Res_version_platform.zip	E7104 and later versions
	NSM_FCAPS-Perf_version_platform.zip
	NSM_FCAPS-ICC_version_platform.zip
UCP	U-Center_UCP_BasePlat_version_platform.zip	E7104 and later versions
	U-Center_UCP_CollectPlat_version_x86.zip
	U-Center_UCP_Agent_version_platform.zip
IOM	U-Center_IOM_version_platform.zip	E7103 and later versions
STM	U-Center_STM_version_platform.zip	E7103 and later versions
STM	U-Center_NQA_version_platform.zip	E7103 and later versions
AOM	U-Center_AOM_PYCOLLECTOR_version_platform.zip	E7103 and later versions

NOTE:

To use an agent to collect applications in proxy deployment mode, you must install U-Center_UCP_Agent.

Upload installation packages

NOTE:

You must upload installation packages on the Matrix front end. Upload through the backend is strictly prohibited. If upload through the backend is required in specific network environments, contact the technical support.

2. Navigate to the DEPLOY > Applications page.

Figure 12 Application list

3. Click Deploy Applications. On this page, you can upload and delete installation packages.

Figure 13 Managing the installation packages

4. Click Upload. In the dialog box that opens, select one or multiple installation package files, and then click Upload.

Figure 14 Upload installation packages

Start installation

1. After the upload is completed, select the application installation package to install, and click Next to parse the installation package.

Figure 15 Select an installation package

2. After the installation package parsing is completed, access the application selection page to confirm the selected applications.

Figure 16 Select applications

3. Click Next to access the parameter configuration page. View the configuration items and the corresponding parameters of the application software package, and select the resource level based on the actual network and service scale. Select the resource level based on the result calculated with the hardware resource calculation tool.

Figure 17 Configure parameters

4. Click Deploy to start deployment.

Figure 18 Deployment progress

5. After the deployment succeeds, click OK. The system automatically returns to the application list page, where you can view the deployed applications.

Figure 19 View deployed applications

Enable the region application

1. After the application deployment in proxy mode is completed, you must enable the region application to have the Hierarchical Management menu displayed in U-Center.

2. Access the server end in the upper-level environment of the proxy, and navigate to the OBSERVE > Monitor > Application Monitoring page.

3. Expand the applications for the BMP_Connect component, and click in the Actions column for the region application to enable the region.

Figure 20 Enable the region application

Access U-Center 5.0

1. In the address bar of the browser, enter http://ip_address:30000 to enter the page as shown in Figure 21. The ip_address argument represents the northbound service VIP, and the default port number is 30000.

NOTE:

You cannot access U-Center through the IP address of the environment where the proxy resides. You can access U-Center only through the IP address of the server in the upper-level environment.

Figure 21 Log in to U-Center 5.0

2. Enter the username and password (the default username is admin), and then click the Login to access the U-Center 5.0 main page.

3. If region is enabled for the applications deployed in proxy mode, the System Settings > Hierarchical Management menu will appear under the System tab. You can manage stations on this page. For example, you can add a proxy site for use when adding monitored resources. For more information, see the online help.

Figure 22 Hierarchical management menu

Register the software

After you deploy U-Center 5.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.

License support

License support describes licenses required for U-Center 5.0 components and the attributes of licenses. For more information, see the U-Center chapter in the H3C AD-NET&U-Center License Matrixes.

Install and obtain a license

For more information about requesting and installing a license, see H3C Software Product Remote Licensing Guide. After importing the license file into the H3C license server management system, configure the U-Center 5.0 (as the license client) to connect it with the license server.

Create a license client

1. Log in to the H3C license server management system, and navigate to the Dashboard > Clients > Client settings page.

2. Click Add. On the page that opens, configure the username and password for a client.

3. Click OK.

Configure client connection settings

Perform this task to connect the client to the license server to obtain the license.

1. Log in to U-Center 5.0.

2. On the top navigation bar, click System. From the navigation pane, select License Management > License Information.

3. In the License Server Info area, specify the parameters such as IP address, and then click Connect to set up a connection to the license server. Configure the following parameters:

¡ IP Address: Specify the IP address of the server hosting the license server.

¡ Port: The port number is 5555 by default, which is the same as the port number of the license server authorization service.

¡ Username: Client name configured on the license server.

¡ Password: Password for the client name configured on the license server.

4. After the connection is successfully set up, the client can obtain a license from the license server. After the connection state is displayed as successful, wait for a while, and then click to refresh the license information.

NOTE:

· To enable the client service, make sure the firewall is disabled for the license server. If the firewall is enabled, the client might fail to connect to the license server.

· To enable the client service, make sure the license server has licenses that have not been requested. If no licenses are available on the license server, the client might fail to obtain a license.

View license usage

Log in to the license server management system, and navigate to the Clients > Client Connections page. This page displays the client connection information of the license server, and allows for management of client connections, such as forcing them offline.

· You can select clients from the list and bulk force them offline, or force all clients offline.

· Click the Details icon in the Actions column for a client to view its details. You can click the reclaim icon in the Actions column for a license to reclaim that license. Alternatively, you can click Forcibly Disconnect to forcibly reclaim all licenses assigned to the client.

Back up and restore components

You can back up and restore components for Unified Platform 5.0. For more information, see H3C Unified Platform Deployment Guide.

Rebuild and recover a cluster from failure

If the hardware failure of a cluster node server results in operation exceptions that cannot be recovered, replace the node server. If the server's operating system is abnormal, reinstall the operating system and Matrix on the original server. You can restore the cluster on Unified Platform. For more information, see H3C Unified Platform Deployment Guide.

Uninstall U-Center 5.0

NOTE:

· When you uninstall U-Center 5.0 by directly removing Matrix, the uninstallation process of the Unified Platform component will not be triggered, and residual data will occur. Before you reinstall Unified Platform, you must clear contents in the /var/lib/ssdata/ directory of all Matrix nodes.

· To reserve component settings and data, perform the backup operation before uninstallation. For more information, see "Back up and restore components."

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

1. In the address bar of the browser, enter https://ip_address:8443/matrix/ui, and enter the username and password (the default username is admin) to log in to Matrix. The ip_address parameter specifies the northbound service VIP.

2. Access the Deploy > Convergence Deployment page.

3. Select one or multiple applications from the list, and click Uninstall.

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

Figure 23 Uninstall applications

FAQ

How can I mount independent disks for seasqlplus-uc?

1. Prepare an independent disk for each node of seasqlplus-uc. The disk capacity is determined based on the size of the data disk /var/lib/ssdata/middleware/seasqlplus-uc in the result calculated with the hardware resource calculation tool.

Figure 24 Prepare an independent disk

2. When you install the operating system, select the prepared independent disk.

Figure 25 Select a disk

3. Mount an independent disk for partition /var/lib/ssdata/middleware/seasqlplus-uc, with the expected capacity as calculated with the hardware resource calculation tool for this partition. The file system type is ext4. Edit the device, and select the prepared independent disk, and configure mount points.

Figure 26 Manual partitioning

Figure 27 Configure mount points

4. After configuration, proceed with the installation process as described in the deployment guide.

H3C U-Center 5.0 Deployment Guide(on Unified Platform E72xx)-5W200

Prepare for installation

Network plan

Pre-installation checklist

Create a license client

Configure client connection settings

View license usage

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